Android Enthusiasts
Q&A for enthusiasts and power users of the Android operating system
Latest Questions
0
votes
0
answers
217
views
Bypass the Android 8.1.0 Setup and entering the settings
I have a tablet which cannot go past the Android setup, once I complete the steps it says that the app "Android Setup" closed. I need a way to bypass this setup so I can open the Settings menu and unlock the bootloader so that I can install LineageOS. Trying opening the web browser via the google te...
I have a tablet which cannot go past the Android setup, once I complete the steps it says that the app "Android Setup" closed. I need a way to bypass this setup so I can open the Settings menu and unlock the bootloader so that I can install LineageOS.
Trying opening the web browser via the google terms of service button crashes the tablet.
LNLenost
(13 rep)
Aug 27, 2024, 05:37 PM
• Last activity: Aug 29, 2024, 09:40 AM
0
votes
0
answers
170
views
AOSP: What makes LineageOS Setup Wizard run in LockTask mode?
I have noticed that when you flash a device and run it for the first time you get into the setup wizard. I assume that application is being run in so called LockTask mode (Kiosk mode for dedicated devices) because it has only one navbar button (usually **"back"** button is the only displayed button,...
I have noticed that when you flash a device and run it for the first time you get into the setup wizard. I assume that application is being run in so called LockTask mode (Kiosk mode for dedicated devices) because it has only one navbar button (usually **"back"** button is the only displayed button, **"home"** and **"recents"** buttons are hidden).
Here are my questions:
1. Does setup wizard actually run in Kiosk mode? If yes, how to implement this? (I didn't find anything in LineageOS sources)
2. If no, what is the way of partially disabling navbar buttons?
UltrumDev
(1 rep)
Jan 8, 2024, 03:16 PM
1
votes
0
answers
4905
views
"RPC executor service threw an error" when signing in with Google Account on Samsung Galaxy Note 8
I had a Samsung Galaxy Note 8 I purchased a few years ago. I had a GM seizure and my access code was long on my device. So, I figured since I only used the device for a little longer than two weeks, I would just factory reset it as I had my Google emails written down in my book along with other logi...
I had a Samsung Galaxy Note 8 I purchased a few years ago. I had a GM seizure and my access code was long on my device. So, I figured since I only used the device for a little longer than two weeks, I would just factory reset it as I had my Google emails written down in my book along with other logins for stuff and their passwords.
So, now, when I go to boot up my device, I choose my language, then agree to terms, and select to use my Google account used with the device instead of my password. I enter it in, then enter its password. Then I received
> RPC executor service threw an error!
Even though it's the right Google account for the device. I can log into it on other devices and log into its backup email too.
I'm not a tech guy. I need help. How to fix this issue?
Tony Lyman
(11 rep)
Oct 22, 2023, 07:58 AM
• Last activity: Oct 22, 2023, 08:15 AM
3
votes
1
answers
18414
views
Setup new device - old phone won't find the new one
I'm trying to use the Google "setup new device" feature to transfer my SMS, apps etc to my new phone. The old phone however won't recognise the new one. Bluetooth is on on both devices, both are connected to wifi, and Location is enabled. [![enter image description here][1]][1] The old one is a Noki...
I'm trying to use the Google "setup new device" feature to transfer my SMS, apps etc to my new phone. The old phone however won't recognise the new one. Bluetooth is on on both devices, both are connected to wifi, and Location is enabled.
The old one is a Nokia 3 with Android 9 and the new one is an Alcatel 1X with Android 8.1.
I've also tried creating a backup on the old phone and using that to set up the new phone, but the new phone says it can't find any backups.
Is the Android version discrepancy the reason for this? If not is there anything else to check?

aucuparia
(151 rep)
Dec 21, 2021, 06:49 PM
• Last activity: May 27, 2023, 01:08 PM
2
votes
0
answers
1888
views
What is "Service Provider Information" on Samsung devices?
What is the "Service provider information" that this Android 12 Samsung Galaxy phone gathers upon setup? Setup requires connection to a network, then says it needs to gather this info, then restart. The only service provider I have identified on the phone is Wi-Fi.
What is the "Service provider information" that this Android 12 Samsung Galaxy phone gathers upon setup?
Setup requires connection to a network, then says it needs to gather this info, then restart.
The only service provider I have identified on the phone is Wi-Fi.
ChrisJJ
(245 rep)
Oct 26, 2022, 11:25 AM
• Last activity: Mar 11, 2023, 03:26 AM
2
votes
0
answers
63
views
If my LG phone got stuck (as in, did not react to hard reset) in download mode and I had to pull the battery, should I skip attempting to stock flash?
I factory reset my LG k7 phone to help with battery and storage issues, but upon reboot, I found that it was glitching up at the setup screen and says the 'Setup Wizard isn't responding. Would you like to close or wait?" on a black screen. Due to this, I had planned to go ahead and stock flash it, a...
I factory reset my LG k7 phone to help with battery and storage issues, but upon reboot, I found that it was glitching up at the setup screen and says the 'Setup Wizard isn't responding. Would you like to close or wait?" on a black screen.
Due to this, I had planned to go ahead and stock flash it, as I was recommended to do. Before proceeding with this, I decided to test out putting my phone in the required download mode.
But when I tried disconnect it, which, for my phone model, means giving it a forced reset, it didn't respond no matter how long i held the buttons, which left me to assume it was frozen.
I then pulled the battery.
So my question is: should I take this reaction to being put in download mode as a bad sign and skip the stock flash? If the phone were to freeze up like this during the flashing, it would cause an interruption and a likely bricking. What should I do?
Ben Sterec
(21 rep)
Nov 13, 2022, 01:50 AM
1
votes
3
answers
6582
views
Cannot skip WiFi in Google Setup Wizard after Factory Reset
I own a Klipad KL4888 tablet running Android 6.0.1 After a crash, I had to do a factory reset and a wipe cache from the recovery menu. However, when restarting and running the setupWizard, it asks me a Wifi/GSM, but systematically the message "Can't connect to the internet" appears. So I went throug...
I own a Klipad KL4888 tablet running Android 6.0.1
After a crash, I had to do a factory reset and a wipe cache from the recovery menu.
However, when restarting and running the setupWizard, it asks me a Wifi/GSM, but systematically the message "Can't connect to the internet" appears.
So I went through ADB (the device is unfortunately not pre-rooted), and in the logs I noticed this :
02-28 23:03:25.995 2784 2929 I SetupWizard.CheckConnectionTask: connecting to walled garden server. retries=0
02-28 23:03:26.246 970 1174 D WifiService: acquireWifiLockLockLocked: WifiLock{NlpWifiLock type=2 binder=android.os.BinderProxy@52836c}
02-28 23:03:28.123 970 1176 D WifiService: releaseWifiLockLocked: WifiLock{NlpWifiLock type=2 binder=android.os.BinderProxy@52836c}
02-28 23:03:36.239 2784 2929 W SetupWizard.CheckConnectionTask: IOException e=java.net.SocketTimeoutException: failed to connect to status.eqoe.cn/185.234.212.233 (port 80) after 10000ms
02-28 23:03:36.239 2784 2929 I SetupWizard.CheckConnectionTask: connecting to walled garden server. retries=1
02-28 23:03:46.301 2784 2929 W SetupWizard.CheckConnectionTask: IOException e=java.net.SocketTimeoutException: failed to connect to status.eqoe.cn/185.234.212.233 (port 80) after 10000ms
02-28 23:03:46.301 2784 2929 I SetupWizard.CheckConnectionTask: connecting to walled garden server. retries=2
02-28 23:03:56.360 2784 2929 W SetupWizard.CheckConnectionTask: IOException e=java.net.SocketTimeoutException: failed to connect to status.eqoe.cn/185.234.212.233 (port 80) after 10000ms
02-28 23:03:56.360 2784 2929 I SetupWizard.CheckConnectionTask: connecting to walled garden server. retries=3
02-28 23:04:06.421 2784 2929 W SetupWizard.CheckConnectionTask: IOException e=java.net.SocketTimeoutException: failed to connect to status.eqoe.cn/185.234.212.233 (port 80) after 10000ms
I also tried to disable Wifi, in order to be able to choose the "Ignore" option but obviously not enough rights.
The problem is that this famous site that is being tested is obviously no longer reachable.
Is there any way to get out of this situation?
An upgrade, but is the hardware compatible?
Modify the Java sources, in order to ping another site?
Thank you !
Sigri44
(113 rep)
Feb 29, 2020, 10:08 AM
• Last activity: May 20, 2022, 08:24 AM
6
votes
0
answers
680
views
How do I set the default user?
My device (Moto G5 Plus/Android 7.0) has two users: `Foo` and `Bar`. `Foo` is the default one, created when I've setup my phone. How do I set `Bar` as the default one and change `Foo` to be the secondary one?
My device (Moto G5 Plus/Android 7.0) has two users:
Foo
and Bar
.
Foo
is the default one, created when I've setup my phone.
How do I set Bar
as the default one and change Foo
to be the secondary one?
M1288580
(61 rep)
Jul 3, 2018, 10:14 AM
• Last activity: May 6, 2022, 09:57 PM
0
votes
1
answers
1570
views
How can I run SetupWizardTestActivity on a rooted Nougat from the phone?
I'm trying to run `com.google.android.setupwizard/.SetupWizardTestActivity` as a solution to the following... Moto C Plus phone suddenly turns off while in pocket. Turned it on. Turns back off. Plugged it to charger. Battery at %17...hmmm weird. Phone turns on but now I see... 1. The icon size went...
I'm trying to run
com.google.android.setupwizard/.SetupWizardTestActivity
as a solution to the following...
Moto C Plus phone suddenly turns off while in pocket. Turned it on. Turns back off. Plugged it to charger. Battery at %17...hmmm weird.
Phone turns on but now I see...
1. The icon size went to default from the small that I'd set it at. The screen time out went to 30 secs from the 2 mins it was set to.
2. The keyboard went to the phone's default keyboard from the one I'd installed.
3. The home and recent buttons - although they are registering the touch - are not doing anything when I press them.
4. The back button is working and is now the only way I can exit the current screen.
5. The screen lock pattern doesn't come on.
6. The notification bar cannot fully be pulled down.
7. The developer option now says "Developer options are not available for this user". Pressing Build 7 times doesn't activate it.
I came across this (first answer) as a solution in a couple of places. The solution they say is to basically run com.google.android.setupwizard/.SetupWizardTestActivity
through NovaLauncher. But the problem is, I'm not seeing SetupWizardTestActivity where it's supposed to be. I'm guessing perhaps it's because I'm rooted?
So now I'm looking for another way to run it from the phone (because I can't connect the phone to a computer because the data pins in the charger port are missing from a botched charger port replacement job).
I came across this as a way to run SetupWizardTestActivity without NovaLauncher. It's...
>1. adb shell
su
pm enable com.google.android.setupwizard/com.google.android.setupwizard.SetupWizardActivity
>2. adb shell settings put secure user_setup_complete 0
>The first command is case sensitive (SetupWizardActivity)
However, I'm not sure if the above is to be done through a computer or on the phone. If it's through the phone then i need a little help as how to exactly do it.
I'd REALLY appreciate if anyone can guide me through this in layman's terms. A simple step by step on how to go about accomplishing this would be hugely appreciated. Emphasis on "layman's"
Thanks in advance!
JJrussel
(431 rep)
Feb 26, 2022, 05:59 PM
• Last activity: Feb 27, 2022, 11:52 AM
0
votes
1
answers
1566
views
"Unfortunately, Setup Wizard has stopped" after factory resetting Yu Yuphoria
Getting the error message "Unfortunately, Setup Wizard has stopped" repeatedly once after I factory reset my Yu Yuphoria mobile. Tried it many times and sometimes I could able to set up and proceed, but could not find the settings icon in my menu. Can someone help me out of this?
Getting the error message "Unfortunately, Setup Wizard has stopped" repeatedly once after I factory reset my Yu Yuphoria mobile.
Tried it many times and sometimes I could able to set up and proceed, but could not find the settings icon in my menu.
Can someone help me out of this?
Praveen Raj
(1 rep)
Nov 4, 2016, 10:35 AM
• Last activity: Feb 4, 2022, 02:04 PM
1
votes
0
answers
462
views
Mass setup of Android devices
I want to setup **the same account** on 300+ devices. I did that for 4 devices and I am tired. Setting up new device includes: 1. manually doing all ok/next/skip choices 2. connecting to WiFi + installing updates 2. manually typing GMail + password 3. **MOST PROBLEMATIC** confirming new device by ta...
I want to setup **the same account** on 300+ devices. I did that for 4 devices and I am tired.
Setting up new device includes:
1. manually doing all ok/next/skip choices
2. connecting to WiFi + installing updates
2. manually typing GMail + password
3. **MOST PROBLEMATIC** confirming new device by tapping two-digit number on the first device where this account was added.
Questions:
* Is there some automated solution?
* Is it possible to at least **turn off confirmation of new device** completely?
Emil
(111 rep)
May 4, 2021, 10:41 AM
• Last activity: May 4, 2021, 09:09 PM
2
votes
0
answers
3293
views
Unfortunately settings has stopped working, can't get past Welcome setup
In advance, I would like to say sorry for my bad English, and that this is my first time posting here so I'm not sure if I am doing this correctly. If I am, it would be nice for me to know. I have a Alcatel One Touch Fierce, althought I do not know much about it. It is not an XL or a Fierce 2 as far...
In advance, I would like to say sorry for my bad English, and that this is my first time posting here so I'm not sure if I am doing this correctly. If I am, it would be nice for me to know.
I have a Alcatel One Touch Fierce, althought I do not know much about it. It is not an XL or a Fierce 2 as far as I am aware, but it is from T-Mobile. For a while now I have been getting been getting a 'Unfortunately, Settings has stopped.' error, when trying to simply open Settings from the home screen or application drawer. I had then reset the phone to factory settings which after doing so, brings me to a Welcome Setup screen. I will attach what this screen looks like. If you can't read it says:
Welcome Setup
For later reference you can find the Setup application in the main menu.
There is a button that show 'Get Started'.
When I press it, it sends me to a language select menu, between English and Spanish. If i select either and press next, it shows the same error message again: Unfortunately, settings has stopped working. I would like to note that this is error is coming straight from ANDROID'S settings app, not Google Settings.
I have tried powering the phone off and launching it with volume up and power button and in recovery mode. I have tried resetting to factory mode and clearing cache, but nothing seemed to help.
Bottom line - My phone displays Unfortunately settings has stopped working eror and I cannot get past the Setup screen.

Mark Radford
(21 rep)
Dec 6, 2016, 12:29 AM
• Last activity: Dec 21, 2020, 04:30 AM
0
votes
0
answers
69
views
Google Calendar always loads all data each time app is opened
I have a "branded" tablet with an OS derived from Android 9 (Pie). To skip the brand-related stuff like registration, I skipped the setup wizard. The device is not rooted. Debugging (via adb) is enabled, and I could customize the launcher and other settings. Everything works - all apps, all buttons...
I have a "branded" tablet with an OS derived from Android 9 (Pie). To skip the brand-related stuff like registration, I skipped the setup wizard. The device is not rooted. Debugging (via adb) is enabled, and I could customize the launcher and other settings. Everything works - all apps, all buttons - it's almost perfect. Only the Google Calendar starts with no dates and slowly downloads my entire calendar each time the app is opened. This takes a while and only works on WiFi, obviously.
I have tried clearing the storage of the Google Calendar, the in-built calendar app, and the Calendar Storage. I would like to avoid a factory reset.
Googling revealed practically nothing except for one tiny hint in https://android.stackexchange.com/questions/146039/home-screen-and-recent-apps-buttons-dont-work : "Caution: Backup/sync everything before starting the setup wizard, because it might reset various things (e.g. the calendar storage (if syncing stopped before) or wifi passwords)." This mentions the calendar storage explicitly, and I did what was mentioned in the thread to skip the wizard as stated above. I believe that's when the problem started. Here is what I did back then:
I have tried clearing the storage of the Google Calendar, the in-built calendar app, and the Calendar Storage. I would like to avoid a factory reset.
Googling revealed practically nothing except for one tiny hint in https://android.stackexchange.com/questions/146039/home-screen-and-recent-apps-buttons-dont-work : "Caution: Backup/sync everything before starting the setup wizard, because it might reset various things (e.g. the calendar storage (if syncing stopped before) or wifi passwords)." This mentions the calendar storage explicitly, and I did what was mentioned in the thread to skip the wizard as stated above. I believe that's when the problem started. Here is what I did back then:
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
Any ideas on how I can make my Google Calendar data remain on the tablet?
**Edit**:
I tried "adb logcat" and it seems the calendar data wiping/reloading coincides with a crash of the app. It's the latest version and I have been observing this for a long time; any idea how to fix/mitigate this?
10-30 12:00:24.071 11845 11845 E AndroidRuntime: FATAL EXCEPTION: main
10-30 12:00:24.071 11845 11845 E AndroidRuntime: Process: com.google.android.calendar, PID: 11845
10-30 12:00:24.071 11845 11845 E AndroidRuntime: com.google.common.util.concurrent.UncheckedExecutionException: java.lang.NullPointerException: Attempt to invoke interface method 'java.lang.Object java.util.Map.get(java.lang.Object)' on a null object reference
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at cal.mvu.b(PG:18)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at cal.ioz.a(Unknown Source:6)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at cal.das.a(Unknown Source:128)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at cal.eji.run(Unknown Source:30)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at cal.drs.a(PG:2)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at cal.dax.l(PG:6)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at cal.dax.k(PG:5)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at cal.ddv.a(PG:65)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at cal.diq.y(PG:71)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at cal.diq.a(PG:2)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at com.google.android.apps.calendar.timeline.alternate.view.impl.layout.LayoutManagerImpl.e(PG:3)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.support.v7.widget.RecyclerView.ah(PG:5)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.support.v7.widget.RecyclerView.x(PG:10)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.support.v7.widget.RecyclerView.onLayout(PG:2)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.View.layout(View.java:20672)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.View.layout(View.java:20672)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.View.layout(View.java:20672)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.View.layout(View.java:20672)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1812)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1656)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.LinearLayout.onLayout(LinearLayout.java:1565)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.View.layout(View.java:20672)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.View.layout(View.java:20672)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at androidx.drawerlayout.widget.DrawerLayout.onLayout(PG:29)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.View.layout(View.java:20672)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.View.layout(View.java:20672)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1812)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1656)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.LinearLayout.onLayout(LinearLayout.java:1565)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.View.layout(View.java:20672)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.View.layout(View.java:20672)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1812)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1656)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.LinearLayout.onLayout(LinearLayout.java:1565)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.View.layout(View.java:20672)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at com.android.internal.policy.DecorView.onLayout(DecorView.java:763)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.View.layout(View.java:20672)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewRootImpl.performLayout(ViewRootImpl.java:2802)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2329)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1467)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:7202)
10-30 12:00:24.071 11845 11845 E AndroidRuntime: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:961)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at android.view.Choreographer.doCallbacks(Choreographer.java:772)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at android.view.Choreographer.doFrame(Choreographer.java:706)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:947)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:873)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6740)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke interface method 'java.lang.Object java.util.Map.get(java.lang.Object)' on a null object reference
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at cal.jmm.call(Unknown Source:46)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at cal.zly.c(PG:1)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at cal.zla.run(PG:4)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at cal.zlz.run(PG:1)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at cal.ead.run(Unknown Source:4)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at cal.eac.run(Unknown Source:75)
10-30 12:00:24.072 11845 11845 E AndroidRuntime: at java.lang.Thread.run(Thread.java:764)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: Uncaught Android Crash on thread main with tid 2
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: com.google.common.util.concurrent.UncheckedExecutionException: java.lang.NullPointerException: Attempt to invoke interface method 'java.lang.Object java.util.Map.get(java.lang.Object)' on a null object reference
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.mvu.b(PG:18)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.ioz.a(Unknown Source:6)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.das.a(Unknown Source:128)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.eji.run(Unknown Source:30)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.drs.a(PG:2)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.dax.l(PG:6)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.dax.k(PG:5)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.ddv.a(PG:65)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.diq.y(PG:71)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.diq.a(PG:2)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at com.google.android.apps.calendar.timeline.alternate.view.impl.layout.LayoutManagerImpl.e(PG:3)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.support.v7.widget.RecyclerView.ah(PG:5)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.support.v7.widget.RecyclerView.x(PG:10)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.support.v7.widget.RecyclerView.onLayout(PG:2)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.View.layout(View.java:20672)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.View.layout(View.java:20672)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.View.layout(View.java:20672)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.View.layout(View.java:20672)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1812)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1656)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.LinearLayout.onLayout(LinearLayout.java:1565)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.View.layout(View.java:20672)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.View.layout(View.java:20672)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at androidx.drawerlayout.widget.DrawerLayout.onLayout(PG:29)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.View.layout(View.java:20672)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.View.layout(View.java:20672)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1812)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1656)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.LinearLayout.onLayout(LinearLayout.java:1565)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.View.layout(View.java:20672)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.View.layout(View.java:20672)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1812)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1656)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.LinearLayout.onLayout(LinearLayout.java:1565)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.View.layout(View.java:20672)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.widget.FrameLayout.onLayout(FrameLayout.java:261)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at com.android.internal.policy.DecorView.onLayout(DecorView.java:763)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.View.layout(View.java:20672)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewGroup.layout(ViewGroup.java:6194)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewRootImpl.performLayout(ViewRootImpl.java:2802)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:2329)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1467)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:7202)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:961)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.Choreographer.doCallbacks(Choreographer.java:772)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.Choreographer.doFrame(Choreographer.java:706)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:947)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.os.Handler.handleCallback(Handler.java:873)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.os.Handler.dispatchMessage(Handler.java:99)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.os.Looper.loop(Looper.java:193)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at android.app.ActivityThread.main(ActivityThread.java:6740)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at java.lang.reflect.Method.invoke(Native Method)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: Caused by: java.lang.NullPointerException: Attempt to invoke interface method 'java.lang.Object java.util.Map.get(java.lang.Object)' on a null object reference
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.jmm.call(Unknown Source:46)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.zly.c(PG:1)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.zla.run(PG:4)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.zlz.run(PG:1)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.ead.run(Unknown Source:4)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at cal.eac.run(Unknown Source:75)
10-30 12:00:24.072 11845 11845 E CalendarUncaughtExcepti: at java.lang.Thread.run(Thread.java:764)
Hans W. Heckel
(1 rep)
Oct 16, 2020, 12:56 PM
• Last activity: Oct 30, 2020, 11:08 AM
0
votes
1
answers
913
views
Re-run Pixel 4 Setup
My girlfriend just purchased a Pixel 4 from Verizon. Apparently, the Verizon representative rushed through the initial setup flow, and my girlfriend didn't get a chance to configure her phone the way she wanted. Is it possible to re-run the onboarding flow?
My girlfriend just purchased a Pixel 4 from Verizon. Apparently, the Verizon representative rushed through the initial setup flow, and my girlfriend didn't get a chance to configure her phone the way she wanted. Is it possible to re-run the onboarding flow?
JD Reddaway
(1 rep)
Oct 27, 2019, 04:44 AM
• Last activity: Oct 27, 2019, 06:30 AM
1
votes
0
answers
2287
views
Android "Nearby" ( set up nearby device ) - "No devices Found"
trying to migrate over from 1 mobile to other . Older is on 7.0 and newer is 9.x aka `Pie`. Both devices have `bluetooth` and `wi-fi` turned on. In fact one sees the other on a bluetooth scan and they are paired. Its just that the `nearby` service (?) of whatever its called that is used for setting...
trying to migrate over from 1 mobile to other . Older is on 7.0 and newer is 9.x aka
Both devices have
Its just that the
Why is this happening and what does it take for this stuff to run correctly ?
Pie
.
Both devices have
bluetooth
and wi-fi
turned on. In fact one sees the other on a bluetooth scan and they are paired.
Its just that the
nearby
service (?) of whatever its called that is used for setting up a new device just doesn't do its job.
I initiated simultaneously from both phone - the "find nearby devices" beacon...none of the phones "found " each other . I repeated the same separately- No avail.
Why is this happening and what does it take for this stuff to run correctly ?
user1874594
(527 rep)
Aug 9, 2019, 05:42 AM
• Last activity: Sep 13, 2019, 09:27 PM
9
votes
6
answers
34598
views
Trigger Setup Wizard at next boot using command-line
I am looking for a way to use ADB to trigger Setup Wizard at next boot. I know I can run the following command and get it to pop up. However, I can't figure out what triggers it to start at boot. adb shell am start -a android.intent.action.MAIN -n com.google.android.setupwizard/.SetupWizardTestActiv...
I am looking for a way to use ADB to trigger Setup Wizard at next boot. I know I can run the following command and get it to pop up. However, I can't figure out what triggers it to start at boot.
adb shell am start -a android.intent.action.MAIN -n com.google.android.setupwizard/.SetupWizardTestActivity
The phone I am currently using is **stock** and I would like to keep it that way.
I've read the question:
https://android.stackexchange.com/questions/79609/how-to-re-enable-first-time-setup-at-next-boot
AtomicDog
(99 rep)
Feb 17, 2016, 03:52 PM
• Last activity: Jun 27, 2019, 09:52 PM
0
votes
1
answers
70
views
How to get past the Google Assistant screen on languages that are unsupported?
The buttons on the setup wizard screen for Google Assistant (the screen after fingerprint unlocking) do not respond when using Finnish language for the setup.
The buttons on the setup wizard screen for Google Assistant (the screen after fingerprint unlocking) do not respond when using Finnish language for the setup.
peterhil
(111 rep)
Jun 12, 2019, 08:29 PM
0
votes
0
answers
147
views
Is there a way to activate NFC during initial phone setup?
My mdm (Ivanti/Landesk) requires to deploy an APK through NFC during the initial phone setup (and only during this setup, where you need to set the langage, time zone, google account, etc.) . This is part of the Android Entreprise Device Owner Mode process. ( Some mdm can follow this process with QR...
My mdm (Ivanti/Landesk) requires to deploy an APK through NFC during the initial phone setup (and only during this setup, where you need to set the langage, time zone, google account, etc.) .
This is part of the Android Entreprise Device Owner Mode process. ( Some mdm can follow this process with QR codes or afw#codes but mine don't .. )
The thing is the NFC card seems disabled by default at first boot (or after a factory reset), and I can't find a way to either enable it from top quick acess bar or settings pages.
Is there an hidden way to enable some settings at this intial step ?
I'm using Altice S61 in my tests, but I think this may apply to other devices as this is during the android standard setup wizard. ( Android version 8.1 )
Thanks in advance !
Regards
Floy
(1 rep)
Jun 7, 2019, 03:08 PM
6
votes
1
answers
8405
views
Android X86 – No Mouse Cursor in Oracle VirtualBox
I have recently installed **AndroidX86** ([android-x86_64-6.0-r1.iso][1]) in **VirtualBox 5.1.12 r112440 (Qt5.6.2)** following [these instructions][2]. But I see no mouse cursor on the screen. Do I need to set some special preference? [2]: https://www.file-extensions.org/article/how-to-install-andro...
I have recently installed **AndroidX86** (android-x86_64-6.0-r1.iso ) in **VirtualBox 5.1.12 r112440 (Qt5.6.2)** following these instructions .
But I see no mouse cursor on the screen. Do I need to set some special preference?
yucer
(261 rep)
Jan 7, 2017, 02:42 PM
• Last activity: Oct 15, 2018, 01:22 AM
0
votes
0
answers
43
views
Sell a device containing Google apps without very first boot experience?
I bought a Chinese smartphone yesterday in its sealed package, but after powering up the device, It started from Home screen and the SetupWizard was pre-configured by default. **Is it possible for the end user to buy an Android device coming pre-configured without the very first boot screen AKA Setu...
I bought a Chinese smartphone yesterday in its sealed package, but after powering up the device, It started from Home screen and the SetupWizard was pre-configured by default.
**Is it possible for the end user to buy an Android device coming pre-configured without the very first boot screen AKA SetupWizard?**
**Edit:** Does Google prohibit this habit, any sources please!
M. A.
(840 rep)
Mar 15, 2018, 09:08 AM
• Last activity: Mar 15, 2018, 09:47 PM
Showing page 1 of 20 total questions