I encrypted my tablet and everything seemed to work without a problem, but every time I restart the tablet, I get a dialog box that says:
Apkinstaller
All pre-installer processes complete!
[OK]
and, more importantly, it's reset my timezone to GMT 0:00.
Anyone come across this issue?
planetfunk said:
I encrypted my tablet and everything seemed to work without a problem, but every time I restart the tablet, I get a dialog box that says:
Apkinstaller
All pre-installer processes complete!
[OK]
and, more importantly, it's reset my timezone to GMT 0:00.
Anyone come across this issue?
Click to expand...
Click to collapse
Yes. Both are known issues I believe. The timezone issue was heavily reported in Xoom forums. Neither affects usage of the device - it's just that you have to set the timezone at every reboot. Since I only reboot if mucking as root in the system and need to make some changes happen... it doesn't bother me.
Related
Every time I reboot my tablet the time zone resets to 0.00. I searched the forum and couldn't find any other threads on this.
Is anyone else having or had this issue?
So far this and the default media player: nemoplayer shutting down randomly are the only issues I have had.
a2drew said:
Every time I reboot my tablet the time zone resets to 0.00. I searched the forum and couldn't find any other threads on this.
Is anyone else having or had this issue?
So far this and the default media player: nemoplayer shutting down randomly are the only issues I have had.
Click to expand...
Click to collapse
Well i am having the same issue that no matter what i do i am not been able to set the correct time zone and this is killing me lol
shutdown issue?
I am starting think the issue may not beee specific to the timezone but more of a shutdown issue. I saw in http://forum.xda-developers.com/showthread.php?p=14545336#post14545336
someone say that after he restarted his pictures taken from his laptop were not saved.
Have you encrypted the tablet I had the same issue only when my tablet was encrypted
Assuming you are running encrypted, it is a bug. From what I have read the xoom has the same issue and was corrected in 3.1... time will tell I suppose
date and time
i posted a thread on here got no answer but try re booting with the charger on if time zone is ok it s a mini battery problem best buy exchanged mine good luck
Another data point...
I am experiencing the same issue here. And yes my tab is also encrypted.
I seem to be able to resolve the issue by deselecting "Automatic date & time" in the "Date & Time" settings area.
Hopefully this is corrected in 3.1
unclear resolution
My tablet was encrypted. I did a factory reset and set the time zone on setup. I have not re-encrypted it yet and the time zone has saved. I'm debating whether or not to encrypt it again.
Anyone tried this on the new 3.1 leaks? I am running picasso but don't want to have to wipe and reset if it isn't fixed...
Sent from my A500 using XDA Premium App
I have noticed some really weird things with my new Nexus 7. First, there has been a few random reboots. Once this morning when I woke the device out of sleep, but after that it has not rebooted. Second, when reloading all my apps after initial setup it would halt the download as soon as the screen turned off. So I thought most of my apps had re-installed so I powered it off for the afternoon. Upon powering it on tonight, my device is downloading and installing everything again! However this time it is doing it even when the screen is turned off.. And finally even though my tablet has 4.3, it says there is an update to 4.3? I haven't tried installing this 'update' yet since I wanted to see how stable the device would be and get all my other apps installed.
Rob
silverball.slayer said:
I have noticed some really weird things with my new Nexus 7. First, there has been a few random reboots. Once this morning when I woke the device out of sleep, but after that it has not rebooted. Second, when reloading all my apps after initial setup it would halt the download as soon as the screen turned off. So I thought most of my apps had re-installed so I powered it off for the afternoon. Upon powering it on tonight, my device is downloading and installing everything again! However this time it is doing it even when the screen is turned off.. And finally even though my tablet has 4.3, it says there is an update to 4.3? I haven't tried installing this 'update' yet since I wanted to see how stable the device would be and get all my other apps installed.
Rob
Click to expand...
Click to collapse
That update to 4.3 is just a... spruce up to say in the simplest way. It's just to fix minor bugs, optimize your tablet etc.
Sounds like you may have an app that isn't agreeing with your tablet. It also sounds like that your tablet is trying to auto-restore apps that you backed up to your Google account.
If you want to disable the auto-restore it is:
Settings > Backup & Reset > Uncheck "Automatic restore"
Also, the apps that are auto downloading might also be from Google play's auto update which they've hid a little bit more in the newer version of Google play. If you want to disable that too it is:
Google Play app > Settings > Auto-update apps > select the radio dot "Do not auto-update apps"
I know downloading a bunch of things in general (i.e., large files, video files etc.) tends to cause most android devices to auto reboot. All these restores might be doing that? I hope someone with more experience will be better to assist you.
Hope that helps some. Good luck :good:
Sounds like a battery saver is killing your WiFi when the screen is off. I think there is even a setting in advanced WiFi options. Android pulls lots of settings from previous devices, perhaps it switched it to turn off when screen is off.
Also, the rebooting initially seems common. Mine rebooted randomly twice that I can tell. I only knew from looking at the Up time in Settings>Status. Since then I'm over 90 hours.
So keep an eye on it if your concerned. It shouldn't turn off the device, just a soft reboot. Googles been updating there core apps, so maybe it was something with old versions of Currents or Maps making it reboot. Mine seems stable after the first couple days. I also unlocked = full wipe, which some say has helped with reboots. If its an ongoing issue, or causing problems, or rebooting frequently during use, I'd exchange it.
Sent from Nexus 7 FHD from XDA Premium HD
After a recent snafu in trying to remove root from my Nexus 7 tablet and installing the 4.3 update I think there are issues with with it's ability to keep a constant wireless connection, Juice Defender be damned as way before root and even during root I was able to maintain a flawless connection although I think the issue may have arisen during my installation of a cracked google play store app.
This was a couple months ago though.
However I decided rooting wasn't worth it and wanted to update to the new 4.3, this is where the snafu occurs, unrooting wasn't a problem at all, nor was flashing stock recovery, but the process of installing 4.3 was since even performing the update in my settings wasn't working, it would download and my tablet would restart and try to apply the update but soon after it would error out and I had to perform a hard shut down.
After that it would boot like normal and there were no issues, other than the update failing to apply.
So I decided to try and apply the update manually and as it turns out, I was attempting to install the update for the mobile version of the tablet instead of the wi-fi only one that I have so it didn't install correctly and simply erased all data on my tablet except luckily for the devices fastboot mode.
Seeing that I installed the correct 4.3 factory image and this is where the wi-fi issues come into play (I wanted to explain in as much detail as I could that might shed light on my current wi-fi situation).
The tablet booted up seemingly normally, taking a bit longer than it should have to me and upon getting to the glowing X before the main screen it suddenly reset it's self and then booted up correctly; so I finished the set up process after linking my wi-fi up but while going through each app that uses wi-fi I started off with games like Happy Street and The Sims Freeplay which worked normally.
Then I got go my Bank of America app and it's the one app (besides the Play Store on occasion), that didn't work at all, instead it just timed out, there's a screenshot so you can verify for yourselves.
You can clearly see I do have an established connection but this is the only app that fails to work after the update, again besides the Play Store but I've removed root and the crack is no longer installed, not that it would work anyway without root access but it doesn't concern me as much since it'll connect after force closing the app and starting it again.
So that's my issue in detail, is there something that I messed up that's preventing the device from maintaining a connection? Or do I simply need to re-install the factory image to restore connections?
Hmm...I've been having some trouble with WiFi as well.
I was running CM10 and then installed the 4.3 factory image over that. That's where the problem started. Since then I've tried the 4.2 factory image, Ubuntu Touch, and I'm now back on CM10, but the issue remains that my WiFi seems to stop working even though the icon in the notification bar says that it's connected.
HawkiesZA said:
Hmm...I've been having some trouble with WiFi as well.
I was running CM10 and then installed the 4.3 factory image over that. That's where the problem started. Since then I've tried the 4.2 factory image, Ubuntu Touch, and I'm now back on CM10, but the issue remains that my WiFi seems to stop working even though the icon in the notification bar says that it's connected.
Click to expand...
Click to collapse
Well the weird thing is, is that every other app seems to work but that one where it just times out, I'm going to try just re-installing the update and see if that helps things.
Edit: After backing everything up I decided to re-install the 4.3 update and after downloading the Bank of America app it started up instantly, froze for a moment and allowed me to sign in.
I closed out of the app and tried again to check and after 3 attempts to sign in it worked each time, I think the re-installation did the trick.
Got a Joying SoFIA head unit, 2GB RAM
The problem I've run into is that every time the head unit restarts it essentially does a factory reset without deleting my apps. All of my login info is gone, my settings reset (which causes problems as I have the google app installed and it resets it to the default launcher #3 that doesn't work with the google app), etc. This isn't a problem as long as it never shuts down completely, but since it only stays in dormancy for a few days and it's not uncommon for me to go longer without driving its a pretty big pain.
I haven't rooted my it yet so I'm not sure if that will help; any suggestions or anyone else with a similar issue?
Have you gone into the setting menu and done a full data wipe/factory reset?
gustden said:
Have you gone into the setting menu and done a full data wipe/factory reset?
Click to expand...
Click to collapse
I haven't. Not sure how that would fix the issue of the settings resetting every time it restarts? I can try it though.
Hey I had the same problem after upgrading from the update 12th May to 25th May. Device started and all settings were gone, Google Account was removed, but my apps was installed - but all savings from the app was removed too. So I hoped to get all settings back If i start the device again. And after that I have the same problem like you. I tried anythinh and one user said I have to try to install the update again. After that it start normally, BUT I have setup all again. I think they have problems with the actual update version.
Jaihoidundso said:
Hey I had the same problem after upgrading from the update 12th May to 25th May. Device started and all settings were gone, Google Account was removed, but my apps was installed - but all savings from the app was removed too. So I hoped to get all settings back If i start the device again. And after that I have the same problem like you. I tried anythinh and one user said I have to try to install the update again. After that it start normally, BUT I have setup all again. I think they have problems with the actual update version.
Click to expand...
Click to collapse
Maybe it's just a bug in the current update. Did it eventually work for you or are you still having the same problem?
Don't waste time searching for a solution.... wipe is the only solution to your problem. It happened to me and many others. Update, without a wipe is not a good option for these units.
I have lost all hope that Google will do anything or I will find a fix by myself with no experience in coding or how android devices work. I've tried my absolute hardest to save my phones photos with no progress. With quarantine happening I've spent a good amount of time looking in to this, here is everything I know.
A simple reboot very rarely fixes it for some people
Rebooting multiple times very rarely fixes it, worked for some people. I've rebooted 100+ times and it didn't
Rebooting to safe mode does nothing, worked in this persons case
You can bypass the lockscreen to another looping screen, shown here, by either brute forcing it, shown in video here. Or by hitting enter and the power button simultaneously when putting in the correct pin, something I found out myself by messing around. From here you can enable USB-Debugging and other settings. Unfortunately, any setting that requires a pin crashes the settings app so you cannot remove the pin from there. In the Google support thread he mentions you can create a new user and control your phone from there but I haven't been able to do it myself
The phone is shown as encrypted in the settings
Other people who were experiencing this issue found a way to replicate it but still no progress from Google has been made
Sideloading the latest OTA does nothing
Phone is only detected in ADB when it is locked, isn't when on the Pixel is starting screen.
Phone is not detected by a PC, shows as MTP USB Device in device manager or another unknown device
Phones storage cannot be accessed in Ubuntu, although it's detected and shown
The confirm prompt that is supposed to show when doing the ADB backup command doesn't show up
ADB pull cannot access the phones files
When on the Pixel is starting screen it's detected as unlocked when using this ADB command
3rd party data recovery softwares successfully install the APK but fail to launch, you can grant app permissions via settings on the phone
Trying to start ANY application with adb commands shows this error message
Uninstalling every app that can be uninstalled from settings does nothing
Disabling/enabling EVERY setting in the settings app did nothing
This bug dates back to FIVE YEARS AGO (Edit: make that seven!)
Deleting locksettings.db or gesture.key on a rooted device with custom recovery or on ADB works, source. REQUIRES AN ALREADY ROOTED DEVICE. Also shown to work here (scroll all the way to the bottom)
Leaving the Pixel is starting screen overnight doesn't work
Leaving the phone on zero battery for multiple days doesn't work
A security update happened the same night the loop started
Locking the phone via Google Find My Device worked for someone in the original support thread which has been locked, multiple threads on the same issue have been made.
Restarting the bootloader in recovery mode worked for someone in the thread too
Disabling live wallpaper in settings does nothing
Someone said that switching to 3 button navigation fixes it, it does not
Could be caused by SoundAssistant/apps with appear on top permissions source
Isn't caused by a wallpaper, i've disabled every wallpaper process and app
Likely caused by corrupt update
Disabling/Force stopping wallpaper related apps changed the wallpaper on the pixel is starting screen to a pink sky with mountain range one
Switching active partitions requires an unlocked device
While on pixel is starting screen, ADB shows the device as unlocked
Aaaand that's all I can remember, there is probably more but these are all that comes to mind. School is starting extremely soon and I am very, very close to taking the hard to swallow factory reset pill but everything I did would've gone to waste, 6 months without a phone I won't get back. So I've come to you guys and am asking if there is ANYTHING I can do that doesn't require a data wipe. Thank you for your time.
For the sources & clickable links, please go to my reddit post (/r/AndroidQuestions/comments/ihcdc0/pixel_4_on_a_lockscreen_loop_for_176_days_what/) add reddit dot com before the link as I cannot post links as a new user.
EDIT: I am now severely ****ed. Sideloaded android 11, didn't fix it. Went to see developper options and fat fingered disable developper options and to re-enable you need your pin which crashes the settings app. Since it wasn't fixed in android 11, september 5 security update AND september 1st google play update I am 100% certain that there will be no fix put out. Resetting later today and never buying a Google phone.
Without flashing a fresh OS I'm not sure if anything can be done. But a clean flash will wipe everything. Google won't help because they don't care.
frankbodyofwater said:
I have lost all hope that Google will do anything or I will find a fix by myself with no experience in coding or how android devices work. I've tried my absolute hardest to save my phones photos with no progress. With quarantine happening I've spent a good amount of time looking in to this, here is everything I know.
A simple reboot very rarely fixes it for some people
Rebooting multiple times very rarely fixes it, worked for some people. I've rebooted 100+ times and it didn't
Rebooting to safe mode does nothing, worked in this persons case
You can bypass the lockscreen to another looping screen, shown here, by either brute forcing it, shown in video here. Or by hitting enter and the power button simultaneously when putting in the correct pin, something I found out myself by messing around. From here you can enable USB-Debugging and other settings. Unfortunately, any setting that requires a pin crashes the settings app so you cannot remove the pin from there. In the Google support thread he mentions you can create a new user and control your phone from there but I haven't been able to do it myself
The phone is shown as encrypted in the settings
Other people who were experiencing this issue found a way to replicate it but still no progress from Google has been made
Sideloading the latest OTA does nothing
Phone is only detected in ADB when it is locked, isn't when on the Pixel is starting screen.
Phone is not detected by a PC, shows as MTP USB Device in device manager or another unknown device
Phones storage cannot be accessed in Ubuntu, although it's detected and shown
The confirm prompt that is supposed to show when doing the ADB backup command doesn't show up
ADB pull cannot access the phones files
When on the Pixel is starting screen it's detected as unlocked when using this ADB command
3rd party data recovery softwares successfully install the APK but fail to launch, you can grant app permissions via settings on the phone
Trying to start ANY application with adb commands shows this error message
Uninstalling every app that can be uninstalled from settings does nothing
Disabling/enabling EVERY setting in the settings app did nothing
This bug dates back to FIVE YEARS AGO (Edit: make that seven!)
Deleting locksettings.db or gesture.key on a rooted device with custom recovery or on ADB works, source. REQUIRES AN ALREADY ROOTED DEVICE. Also shown to work here (scroll all the way to the bottom)
Leaving the Pixel is starting screen overnight doesn't work
Leaving the phone on zero battery for multiple days doesn't work
A security update happened the same night the loop started
Locking the phone via Google Find My Device worked for someone in the original support thread which has been locked, multiple threads on the same issue have been made.
Restarting the bootloader in recovery mode worked for someone in the thread too
Disabling live wallpaper in settings does nothing
Someone said that switching to 3 button navigation fixes it, it does not
Could be caused by SoundAssistant/apps with appear on top permissions source
Isn't caused by a wallpaper, i've disabled every wallpaper process and app
Likely caused by corrupt update
Disabling/Force stopping wallpaper related apps changed the wallpaper on the pixel is starting screen to a pink sky with mountain range one
Switching active partitions requires an unlocked device
While on pixel is starting screen, ADB shows the device as unlocked
Aaaand that's all I can remember, there is probably more but these are all that comes to mind. School is starting extremely soon and I am very, very close to taking the hard to swallow factory reset pill but everything I did would've gone to waste, 6 months without a phone I won't get back. So I've come to you guys and am asking if there is ANYTHING I can do that doesn't require a data wipe. Thank you for your time.
For the sources & clickable links, please go to my reddit post (/r/AndroidQuestions/comments/ihcdc0/pixel_4_on_a_lockscreen_loop_for_176_days_what/) add reddit dot com before the link as I cannot post links as a new user.
Click to expand...
Click to collapse
change your usb default options to "transfer files" in developer options
if you're wanting to connect to adb the way I have been doing it is by setting up adb to connect through wifi. this is the procedure I used to delete digital wellbeing.(improves system performance and battery) Windows 10.
read this thread on how to set up tcpip adb connection
https://developer.android.com/studio/command-line/adb
jalado said:
change your usb default options to "transfer files" in developer options
if you're wanting to connect to adb the way I have been doing it is by setting up adb to connect through wifi. this is the procedure I used to delete digital wellbeing.(improves system performance and battery) Windows 10.
read this thread on how to set up tcpip adb connection
Click to expand...
Click to collapse
I was able to connect to adb via USB but tried connecting through wifi which worked but I dont see why it was needed, deleting digital wellbeing unfortunately didnt do anything. Thanks for replying though
frankbodyofwater said:
I was able to connect to adb via USB but tried connecting through wifi which worked but I dont see why it was needed, deleting digital wellbeing unfortunately didnt do anything. Thanks for replying though
Click to expand...
Click to collapse
what is your issue you're having? you said you weren't able to download your files etc?
what was the problem in the 1st place?