Unfortunately setup wizard has stopped что делать

Unfortunately setup wizard has stopped что делать

Android в России: Новости, советы, помощь

Что делать unfortunately phone has stopped ?

  • Нравится
  • Не нравится

celtics657 08 Май 2017

До сброса настроек телефона до заводских писало «приносим извинения», а после сброса «unfortunately phone has stopped» и при нажатие «ок» она снова появляется и не убирается. Так же к компу телефон не хочет подключаться из-за этой ошибки. Подскажите что сделать, чтоб решить данную проблему ? Спасибо.

Прикрепленные изображения

Форуматор 10 Авг 2015

  • Нравится
  • Не нравится

gresaggr 09 Май 2017

Попробуйте сделать сброс настроек (с удалением всех данных в памяти):

  1. Когда телефон выключен, нажмите и удерживайте ГромкостьВниз, а затем кратковременно нажмите Включение.
  2. Дождитесь появления экрана с 3 изображениями Android, затем отпустите кнопку ГромкостьВниз.
  3. Нажмите кнопку ГромкостьВниз, чтобы выбрать Сброс настроек, затем нажмите Включение.
  4. При запросе подтверждения нажмите ГромкостьВниз.

  • Нравится
  • Не нравится

celtics657 09 Май 2017

Попробуйте сделать сброс настроек (с удалением всех данных в памяти):

  1. Когда телефон выключен, нажмите и удерживайте ГромкостьВниз, а затем кратковременно нажмите Включение.
  2. Дождитесь появления экрана с 3 изображениями Android, затем отпустите кнопку ГромкостьВниз.
  3. Нажмите кнопку ГромкостьВниз, чтобы выбрать Сброс настроек, затем нажмите Включение.
  4. При запросе подтверждения нажмите ГромкостьВниз.

Не помогло, появляется следующая ошибка и так же при нажатии «ОК» появляется вновь..

Прикрепленные изображения

  • Нравится
  • Не нравится

celtics657 09 Май 2017

После нажатия «ок» на ошибке, что описал сверху, появилась данная ошибка

Прикрепленные изображения

  • Нравится
  • Не нравится

gresaggr 09 Май 2017

Вы сброс сделали, как было указано выше?

  • Нравится
  • Не нравится

celtics657 09 Май 2017

Вы сброс сделали, как было указано выше?

да все сделал по вашим указанием

  • Нравится
  • Не нравится

gresaggr 10 Май 2017

На приложенном скриншоте видна выставленная дата — после Hard Reset такого быть не должно и дату требуется выставлять заново.

Ошибка в Nox App Player: «Unfortunately, Nox Launcher has stopped»

Ранее пользователи данного эмулятора мобильной платформы Андроид могли видеть сбой при его запуске или во время работы. Там сообщалась ошибка Unfortunately, Nox Launcher has stopped, но текст иногда различался. Она гласила о том, что графическая оболочка Нокса прекратила свое функционирование, и программа в итоге закрывалась. Если данный сбой разовый, то волноваться не о чем. Проблемы появляются, когда он отображается постоянно. Но с ними довольно легко разобраться.

Подробности

Ошибка касается только старых версий Нокс и, соответственно, в последних обновлениях возникать не должна. Из этого следует вполне логичное решение – удаление прежнего эмулятора и загрузка нового. Рассмотрим данную процедуру в пошаговом варианте.

Шаг №1: Избавляемся от старой версии

Мы уже разбирали во всех подробностях порядок действий для полного удаления программы. Детальная инструкция изложена в этом материале. А в нынешней статье мы предлагаем упрощенный вариант:

  1. Загрузите утилиту CCleaner, предназначенную для чистки ПК (ссылка ведет на официальный сайт).
  2. Откройте полученный exe-файл и запустите процедуру инсталляции.
  3. Дождитесь ее окончания, а затем кликните на «Запустить…», отключив предварительно показ примечаний.
  4. Отобразится главное окно Сиклинера. Здесь вам нужно открыть вкладку «Сервис».
  5. В списке программ отыщите Nox App Player. Далее, щелкните ЛКМ по соответствующей графе и вызовите опцию деинсталляции.
  6. В новом окне нажмите на «Удалить».
  7. Затем выделите доступные пункты и подтвердите выполнение операции.
  8. Дождитесь завершения, а потом вновь вернитесь к утилите CCleaner.
  9. На этот раз откройте вкладку «Реестр» и запустите процедуру поиска.
  10. Кликните сначала на кнопку «Исправить выбранное..», а потом по пункту подтверждения.
  11. Сохраните в удобный каталог резервную копию для реестра. Она понадобится, если в результате чистки произойдет сбой. Любые изменения получится отменить, если затем открыть reg-файл.
  12. Запустите процедуру исправления.
  13. Теперь нажмите на клавиатуре комбинацию Win + R.
  14. Выполните команду %localappdata%.
  15. В открывшемся каталоге Проводника безвозвратно удалите папку Nox.
  16. Ну и в качестве окончания процесса нужно выполнить перезагрузку ПК или ноутбука.

Шаг №2: «Чистая» установка

Теперь система избавлена от любых упоминаний об эмуляторе. А значит, можно переходить к «чистой» установке. И здесь все предельно просто:

  1. Посетите официальный сайт программы https://ru.bignox.com/.
  2. Загрузите последнюю ее версию, нажав на соответствующую кнопку.
  3. Откройте исполнительный файл с расширением .exe.
  4. Смена настроек в данном случае не требуется, поэтому просто жмите на «Установить».
  5. Дождитесь распаковки компонентов Nox, а затем запустите его кнопкой «Пуск».

How to Fix “Unfortunately, System UI has stopped” Error in Android

“Unfortunately, System UI has stopped” or “com.android.systemui has stopped” is one of the most common error while using the Android smartphone. I got this message every few seconds while using the phone. In this article, I will be sharing on how to fix this error, what is the reason behind the error and which solution helped me in solving the issue.

Reason For “Unfortunately, System UI has stopped”.

Further, I got to know that “Unfortunately, System UI has stopped” Error is a common error among Android users and the reason behind error may differ from phone to phone. Some of the users have reported that the error is caused due to a third-party app, some said the problem in custom ROM while many users said due to the update of Google app.

How to fix “Unfortunately, System UI has stopped” Error in Android

The solution that worked for me was Uninstalling Google App Updates. The solution may not be the same for all the users so try some other solutions which I have mentioned below.

Before going into the actual solution try restarting your device. In most of the cases restarting the device has solved these issues.

Re-start your device

Sometimes just by re-starting your device can solve the issue. So, why not try this once. To restart your device:

  • Unlock the screen of the devices.
  • Press and hold the “Power” button until a menu appears.
  • Select “Power off“.
  • Wait for the device to power off.
  • Wait 10 seconds, then press and hold the “Power” button to power the device back ON.
  • Now see if this fixes your error or not.

Solutions to fix “Unfortunately, System UI has stopped”

Method 1: Uninstall Google App Updates

There are lots of users who fixed their issue by uninstalling the Google app updates. It is said that the error is caused after updating Google App. Try this method to get rid of the error.

  • Go to Setting>> Go to Application Setting (In some devices application setting is named as apps).
  • Go to, All the apps > >Find the Google App >>Uninstall Updates
  • Now Restart your device and try to see if it fixes your error.

Note: You better choose “Do not auto-update app”. So that Google apps won’t be updated automatically and creates the same issue. To choose the option, Go to Google Play Store >> Click on three horizontal lines>> Click on Settings >> Choose the options “Do not auto-update app”.

Method 2: Scan the Phone with CM Security App

Most of the users have fixed “Unfortunately, System UI has stopped” Error simply by scanning their device with CM Security App. This method has got a very good review from the users and I hope you will also be able to fix the issue using this method.

  • First, you need to Download CM Security App in your device
  • Once you have installed the app, Run the app
  • Now scan the phone with CM Security App and you are good to go.

You should be able to fix the error by now. But, if you are still facing the error then try to follow given methods.

Method 3: Reset App Preference

  • Go to Setting>> Go to Application Setting (In some devices application setting is named as Apps).
  • Go to, All the Apps > >Click on Menu Key/button [In some device you can even see three dots on the top right corner of the screen- click on it]
  • You will see different option >> Tap on “Reset app preferences”
  • A dialogue box will appear >> Read the content and Click on RESET APPS
  • Now Restart your device and check if it fixes your error.

Method 4: Use Safe Mode

This method will let you know whether the third-party application is causing the error or not. In the safe mode, all third-party apps are disabled so we can detect the problem is with a third-party app or other.

  • Press and hold the Power button
  • You will see different Power option on your screen
  • Now press and hold the Power Off option continuously
  • After a few seconds, you will get a pop-up box asking you to restart the device in Safe Mode
  • Tap OK

As soon as the device opens in Safe Mode, check whether the error is solved or not. If there is no error then a third-party app may be causing the error. So, try uninstalling the recently downloaded app and see whether the error is fixed or not.

Method 5: Wipe cache partition from Recovery Mode

This has also worked for many of the users. We just need to wipe the cache partition and we can see that the error is fixed. Just follow the step as shown below and you can fix the error.

Phones and their keys/buttons to go in Recovery mode

  • Samsung Galaxy S6: Volume Up + Home + Power
  • Nexus 7: Volume Up + Volume Down + Power
  • Motorola Droid X: Home + Power
  • Devices With Camera Buttons: Volume Up + Camera
  • Most Android Phone: Volume Up + Power
  • First turn off the phone >> Press volume up and power button together to go to Recovery Mode
  • After that Recovery Mode will appear with many options >> use volume up and down to control the screen and power button to press ok.
  • Select wipe cache partition >> press power button and it will then start cleaning the cache.
  • A message will appear after the completion >> Select reboot system now and it will start rebooting your device.

Now your device has wiped the cache and you can use the device like previously without error. This process may erase the save data of the app like the save game, high score etc.

If you are still facing the error then you can try the last solution, Factory Reset. It will fix your error.

Method 6: For Custom ROM users

If you are using custom ROM like CyanogenMod, SlimROM etc and facing some errors whether it is “Unfortunately, settings has stopped” Error or any other than you should know either it is because of compatibility issue or the ROM has not been installed properly. So, it is better you reflash the operating system along with compatible GAPPs (Google Applications) package. If you are still getting the error, try flashing different ROM.

So, these are some of the methods to fix “Unfortunately, System UI has stopped” Error in Android. Hopefully, you have solved the error and won’t face the error in future again. Let us know which method worked for you on comment below.

Quite a few Android users complained that they are facing a problem with their handset when they are trying to open the Settings option. It’s showing “ Unfortunately, Settings has stopped working” . This was a very common issue back in the time when KitKat update was released. However, the problem is not always related to the software update, and if you see this error message on your device try the solutions below and hopefully, you will fix your Android device.

Solutions for “ Unfortunately, Settings has stopped working” problem on Android

Restart the device

‘Unfortunately, settings has stopped working’ is a very annoying issue but you can fix it just by restarting your Android phone or tablet. Press and hold the Power button. When the menu opens, tap Restart. Try to access the settings.

Clear cache of the device

The next step is clearing the cache of your Android device. This will clear cached data for all the apps you have on your smartphone or tablet.

  • Go to settings > Storage
  • Tap Clear cache (on some devices Clean Cache)

Wipe cache partition

In case you are unable to perform the above method, you can enter the Recovery mode and then select the option “Wipe cache partition.” To access the Recovery mode, you have to power off your device and then press a specific combination of keys, which varies from one device to another. Here are some examples (Samsung: Home, Power, and Volume buttons; LG: Power and Volume Down buttons; Nexus: Volume Up, Volume Down, Power button; HTC: Volume Down and Power button;)

  • Power off your phone or tablet
  • Press the combination of keys at the same time
  • After a while, you will see Recovery screen
  • When Recovery menu shows up, use the Volume button to navigate to Wipe cache partition option
  • Select that using the Power button.
  • When this is completed, select reboot option

Uninstall and reinstall Google Play store update

This might sound bit odd but yes, this method can help you in resolving the ‘Unfortunately, settings has stopped working’. What you need to do is clear the cache for Google Play and uninstall the Google Play store update. To do that, go to Settings > Application manager, find Google Play and tap on it. First tap “Clear cache”. Then, tap Uninstall updates. Once you are done, restart your device. Go to Google Play and tap on three horizontal lines. Next, tap Settings. Scroll down, and tap on Build version. You will see the following message: “A new version of Google Play Store will be downloaded and installed”. Tap OK.

Boot the device in safe mode

Many times, a third-party app is the culprit and is causing “ Unfortunately, Settings has stopped working” eroor . You can boot your device to Safe mode. When you do that, you will be able to use your Android without third-party apps, because all of them will be disabled. If your device working normally, and the error message is not showing when you try to acess the settings, a third-party app is to blame. You can uninstall the apps one by one, or you can perform a factory data reset.

  • Press and hold the Power button
  • When the menu appears, press and hold Power off option
  • You will be asked if you want to reboot your device into Safe mode
  • Tap OK

  • You will see Safe mode in the lower-left corner of the screen

If you see that “Unfortunately Settings has stopped working” problem is not occurring in Safe Mode, then a third party app is causing the problem. What you need to do is uninstall third-party apps one by one (start with those recently installed), until the issue is solved or if you have too many apps you can perform a factory data reset.

Factory reset

A Factory reset removes all your phone’s data, so before proceed, back up all your data.

There are several ways to create a backup of your phone. Follow the steps below:

  • The first way to create a backup of the device is with Google account. Head towards Settings > General > Backup & Reset and it will provide two options named as backup my data and automatic restores. Ensure those options are enabled by ticking the checkbox next to them and it will backup details like Wi-Fi password, app data, Google settings, and bookmarks automatically to Google server so that they can be retrieved.
  • In case you are using a Samsung device, create a backup using Samsung account. For that go to Application > Settings> User and backup > Account and check if you are signed in with your Samsung account. If the option is enabled, it will sync the contacts, calendar and internet settings to the Samsung account.

After the backup, go ahead with the factory reset process. Here is how to perform it on your Android phone:

  • Go to Settings
  • Tap Backup & Reset
  • Next, tap Factory data reset
  • Tap Reset phone/tablet

If the error message keeps popping up, and you can’t access Backup & Reset, do the following:

  • Turn off your device
  • Next, hold down the Home, Power, and Volume Up button altogether for few seconds till Android logo appears on the screen (if you are not using Samsung, make sure you are pressing the correct combination of keys).
  • Release the buttons then. Use Volume down button for highlighting any options and Power key to confirm it. Highlight the factory reset option and confirm it using the power button.
  • Next, select ‘Delete all user data’ and confirm it
  • Wait for few seconds to see the ‘reboot system now’ option and select it. The phone will restart and you will have to set it up from scratch again.

How to Fix Setup Wizard has Stopped on Android

Though custom ROMs come with great benefits, however, you can’t even deny the hardships they have to offer. Recently, I flashed the Lineage OS to my OnePlus device, with TWRP recovery installed. As expected, the flashing process went smooth and everything was fine until I was about to set it up. Unfortunately, my OnePlus 2 was stuck in an infinite loop, constantly conveying Setup Wizard has Stopped. That was horrible!

Are you facing the same issue? Ahh! That is why you are here. Here’s a good news, it took me 4 hours to get my device in a working state and luckily, you don’t have to go through all this as I have a precise solution for you. Just be with me for next 3-5 minutes and by the end of this article, you’ll exit with a happy face. Let’s see how you can fix setup wizard has stopped on your Android.

Method 1: Deleting the Setup Wizard

It is the most prominent way to fix the setup wizard has stopped after factory reset. This is the exact solution which has worked for me, and I am damn sure, it’s going to work for you too. Here’s how it’ll work.

Step 1: Turn off your device and boot into the TWRP recovery. In case you don’t know how to boot into recovery:

  • With your device powered off, press the combination of Volume Down and Power button simultaneously. Keep the keys pressed until you see the recovery mode on your device.
  • Booting into recovery mode varies from device to device. If the above is not working for you, press the combination of Volume Up and Power button simultaneously. Keep the keys pressed until you see the recovery mode on your device.

Step 2: From the Recovery menu, tap on Mount and check the option “System“.

Step 3: Now, move one step back to the home screen of TWRP recovery and tap on Advanced -> File Manager.

Step 4: Next, navigate to system -> priv-app -> Setup-Wizard.

Step 5: Finally, delete the Setup-Wizard. Exit the Recovery mode, boot into your device and check if setup wizard keeps on stopping? Most probably, it’ll not show up again.

Method 2: Force Stopping the Setup Wizard

It’s highly unlikely, however, if the above method is not working for you, kindly follow this method.

You need to be patient for this method to work. It’s not like it’ll work the very first time, it may or it may not. Keep on trying the below-mentioned steps, maybe 7-8 times, until you fix the setup wizard has stopped error.

Step 1: Pull down the Notification bar and launch Settings.

Step 2: Scroll down until you see Apps. Tap on it.

Step 3: Tap the vertical-three-dots at the top right corner of the screen and select Show system.

Step 4: There are two Setup Wizards on your system. Scroll down until you see both of them.

Step 5: Select the Setup Wizard with Android Logo and tap on Force Stop.

Step 6: On the same screen, scroll down and tap on Permissions. Subsequently, enable all the permissions.

Step 7: Press the Home button, and check if the error still persists.

Setup Wizard has Stopped

As the permissions required by setup wizard were not fulfilled, it kept on throwing this error on you. I hope by this time you are not seeing any such error.

Which method worked for you? Do let us know in the comment section. If this guide helped you in any way, don’t forget to give us a +1. Also, if you have any issues following the guide, please comment down below. I’ll get back to you asap.

Meanwhile, you can also like us on Facebook or follow us on Instagram. There’s a lot gonna happen out there in coming days.

The Problem

Your application quit because an uncaught RuntimeException was thrown.
The most common of these is the NullPointerException .

How to solve it?

Every time an Android application crashes (or any Java application for that matter), a Stack trace is written to the console (in this case, logcat). This stack trace contains vital information for solving your problem.

Android Studio

In the bottom bar of the window, click on the Logcat button. Alternatively, you can press alt + 6 . Make sure your emulator or device is selected in the Devices panel. Next, try to find the stack trace, which is shown in red. There may be a lot of stuff logged into logcat, so you may need to scroll a bit. An easy way to find the stack trace is to clear the logcat (using the recycle bin on the right), and let the app crash again.

I have found the stack trace, now what?

Yay! You’re halfway to solving your problem.
You only need to find out what exactly made your application crash, by analyzing the stack trace.

I still can’t solve my problem!

If you’ve found your Exception and the line where it occurred, and still cannot figure out how to fix it, don’t hesitate to ask a question on StackOverflow.

Try to be as concise as possible: post the stack trace, and the relevant code (e.g. a few lines up to the line which threw the Exception ).

You can use Google’s ADB tool to get Logcat file to analyze the issue.

open logcat.txt file and search for your application name. There should be information on why it failed, the line number, Class name, etc.

First, you check which point your app has crashed ( Unfortunately, MyApp has stopped. ). For this, you can use Log.e(«TAG», «Message»); , using this line you can see your app log in logcat.

After that, you find which point your app has stopped it’s very easy to solve at your side.

Just check the error in log cat.

You get the log cat option from in eclipse:

Log cat contains error.

Other wise you can also check the error by executing an application in debug mode. Firstly set breakpoint after that by doing:

right click on project->debug as->Android application

Note: This answer is using Android Studio 2.2.2

Note 2: I am considering that your device is successfully connected.

The first thing you do when your application crashes is look into the LogCat, at the bottom of Android Studio there’s a toolbar with a list of menus:

Click on the «Android Monitor» (The one I underlined in the image above. ^)

Now, you’ll get something like this:

Change » Verbose » to » Error » Now it will only show you logged errors. Don’t worry about all these errors (if you got them) now.

Ok. Now, do what you did to crash your app. After your app crashes, go to your logcat. You should find a new crash log that has a lot of at:x.x.x : and Caused by: TrumpIsPresidentException for example. Go to that Caused by: statement in your logcat.

Next to that Caused By: , there should be the Exception that happened. In my case, it’s a RuntimeException and under it there should be a line which contains a blue link such as:

If that Caused by: DOESN’T have a line with a blue text somewhere under it, then look for another Caused by: that does.

Click on that blue link. It should take you to where the problem occured. In my case, it was due to this line:

So, now I know why it’s crashing. It’s because I’m throwing the exception myself. This was an obvious error.

However, let’s say I got another error:

I checked my logcat, I clicked on the blue link it gave me, and it took me here:

So, now I want to debug. According to this StackOverflow question, a NullPointerException says that something is null .

So, let’s find out what is null. There’s two possibilities. Either mTextView is null, or myString is null. To find out, before the mTextView.setText(mString) line, I add these two lines:

Now, like we did previously (We changed Verose to Error), we want to change «Error» to «Debug». Since we’re logging by debugging. Here’s all the Log methods:

So, since we used Log.d , we’re checking in Debug. That’s why we changed it to debug.

Notice Log.d has a first parameter,in our case «AppDebug». Click on the «No Filters» drop down menu on the top-right of the logcat. Select «Edit Filter Configuration», give a name to your filter, and in «Log Tag» put «App Debug». Click «OK». Now, you should see two lines in the logcat:

So now we know that mTextView is null.

I observe my code, now I notice something.

I have private TextView mTextView declared at the top of my class. But, I’m not defining it.

Basically I forgot to do this in my onCreate():

So THAT’S why mTextView is null, because I forgot to tell my app what it is. So I add that line, run my app, and now the app doesn’t crash.

Читать еще:  Best files biz что это
Ссылка на основную публикацию
Adblock
detector