Develop Bugs

[Q] Nexus 7 2013 wifi 4.4kitkat system update problem

So still no lollipop on my nexus 7 2013 wifi, its not rooted, i did a factory reset to start fresh, i did a backup before that. when it finished factory reset backup restored all and it works ok and again still no lollipop but a new problem started to show. Before i did a factory reset my system update automatically checked for updates 2-3 times a day, but now it doesnt do that at all i can check it manually but it doesnt check it automatically. whats the problem? can i fix it somehow? thanks to all who can help
p.s. i can see that my apps wont automatically update like before even tho my play store is set to update automatically

Why not just flash the factory image at this point? I would never wait for the OTA to prompt me. As soon as the factory image was on the Google website, I would be flashing it.

SwoRNLeaDejZ said:
Why not just flash the factory image at this point? I would never wait for the OTA to prompt me. As soon as the factory image was on the Google website, I would be flashing it.
Click to expand...
Click to collapse
Yes that is a good idea if you know what you are doing, and i'm afraid that i'll mess something so i'll wait for OTA but can you help me with this update problem for now?

July Verizon Update running very hot!

Can I just flash the June update and go back?

No issues when I used the July update (non-Verizon), but yes you can go back

If you don't mind setting up your phone again you might want to try a factory reset before going back to June. Sometimes after an OTA update or an accumulation of OTA updates over time something in the phone gets corrupted (cache, old app data, code that isn't properly updated or erased in an update) and the best thing to do is a factory reset to start fresh.

rickysidhu_ said:
No issues when I used the July update (non-Verizon), but yes you can go back
Click to expand...
Click to collapse
Thank you for responding.

jhs39 said:
If you don't mind setting up your phone again you might want to try a factory reset before going back to June. Sometimes after an OTA update or an accumulation of OTA updates over time something in the phone gets corrupted (cache, old app data, code that isn't properly updated or erased in an update) and the best thing to do is a factory reset to start fresh.
Click to expand...
Click to collapse
That's a good suggestion. Thanks for responding.

STraver said:
Can I just flash the June update and go back?
Click to expand...
Click to collapse
Mine did as well, I suspected teh July update.
5 days in though it seems to have cooled off and is working at the temps I am accustomed to ~30c at idle.

parakleet said:
Mine did as well, I suspected teh July update.
5 days in though it seems to have cooled off and is working at the temps I am accustomed to ~30c at idle.
Click to expand...
Click to collapse
Okay thanks. That's good to know. For now I have flashed back to June. I may flash July and factory reset as was suggested above. For the past few months I have been updating by removing the "-w" from the flashall batch file and maybe it's caught up with me. I also tried wiping the davlik cache in twrp but that doesn't seem to work.

STraver said:
Okay thanks. That's good to know. For now I have flashed back to June. I may flash July and factory reset as was suggested above. For the past few months I have been updating by removing the "-w" from the flashall batch file and maybe it's caught up with me. I also tried wiping the davlik cache in twrp but that doesn't seem to work.
Click to expand...
Click to collapse
Try just clearing your cache partition from settings > storage. It may help in some cases too if cache is corrupted.
Factory reset will pretty much guarantee fix.

STraver said:
That's a good suggestion. Thanks for responding.
Click to expand...
Click to collapse
You're welcome.
---------- Post added at 08:07 PM ---------- Previous post was at 08:02 PM ----------
milan187 said:
Try just clearing your cache partition from settings > storage. It may help in some cases too if cache is corrupted.
Factory reset will pretty much guarantee fix.
Click to expand...
Click to collapse
You might be right that adding -w caused your problem. There is always a possibility that some user data in an app that gets saved can cause problems after the phone is updated.

jhs39 said:
You're welcome.
---------- Post added at 08:07 PM ---------- Previous post was at 08:02 PM ----------
You might be right that adding -w caused your problem. There is always a possibility that some user data in an app that gets saved can cause problems after the phone is updated.
Click to expand...
Click to collapse
Well I factory reset and installed the July update. The phone is fine now and not not hot but it seems a lot faster too. The only issue I ran into was that evidently my apps weren't being backed up to my google account, so I had to manually install them again. Thanks for your advice!

STraver said:
Well I factory reset and installed the July update. The phone is fine now and not not hot but it seems a lot faster too. The only issue I ran into was that evidently my apps weren't being backed up to my google account, so I had to manually install them again. Thanks for your advice!
Click to expand...
Click to collapse
I've had that happen after a factory reset or Rom flash in the past too even though I knew my apps were being backed up--they are by default unless you turn the feature off. I don't know why that happens but sometimes it does. I'm glad everything is working fine now. Sometimes giving your phone a fresh start by doing an occasional factory reset or completely clean flash is the best thing you can do. The fact that it seems to be running faster now is very likely true. Again, glad you got it sorted out. I'm actually running the beta of O and if you like how the Pixel runs on Nougat I think you will be even happier when O officially rolls out in August. The boot time on O is almost instant, battery life is slightly better and should improve more if more apps optimize their code for O, and the phone runs very snappy even though O is still in beta.

jhs39 said:
I've had that happen after a factory reset or Rom flash in the past too even though I knew my apps were being backed up--they are by default unless you turn the feature off. I don't know why that happens but sometimes it does. I'm glad everything is working fine now. Sometimes giving your phone a fresh start by doing an occasional factory reset or completely clean flash is the best thing you can do. The fact that it seems to be running faster now is very likely true. Again, glad you got it sorted out. I'm actually running the beta of O and if you like how the Pixel runs on Nougat I think you will be even happier when O officially rolls out in August. The boot time on O is almost instant, battery life is slightly better and should improve more if more apps optimize their code for O, and the phone runs very snappy even though O is still in beta.
Click to expand...
Click to collapse
Interesting. So O is supposed to become available in August. Will my older apps still work or will they all have to be updated by the developers? Also- for future updates would I be better off doing an OTA vs a complete flash (with the -w taken out)? In any case it sounds like at least every other month I should do a reset and reinstall anyway. What is the risk in just not updating every month? Thanks!

STraver said:
Interesting. So O is supposed to become available in August. Will my older apps still work or will they all have to be updated by the developers? Also- for future updates would I be better off doing an OTA vs a complete flash (with the -w taken out)? In any case it sounds like at least every other month I should do a reset and reinstall anyway. What is the risk in just not updating every month? Thanks!
Click to expand...
Click to collapse
I've encountered a handful of apps that don't work on O but they probably will by the official launch date. But an app being optimized to help provide better battery life is something that goes on in the background that you won't notice unless you are a programmer that can analyze code or knowledgeable tech writers shame app devs publicly who don't do it. Android O has the ability to limit an apps background processes so it uses less battery but my understanding is that it only happens if the app developers voluntarily write code that allows O to do that to the app and a lot of devs are probably not going to do that if it is voluntary.
I'm not sure what your setup is but if you are manually flashing updates presumably you have a custom recovery and possibly root. Some Pixel users have reported successfully flashing OTA updates anyway because of the dual partitions on the Pixel but it wipes out your custom recovery and root and returns you to full stock and I'm not sure doing that works reliably. I don't know that the Flashfire/Flashify (I don't remember which app goes with TWRP) works on the Pixel. I don't have any experience flashing OTA updates manually via bootloader rather than the full monthly update. Personally I was never a fan of removing -w from a full flash because it can always lead to potential problems that aren't necessarily completely obvious. I always prefer to clean flash to give the phone a clean start, but that's just my own preference. I didn't like to dirty flash custom Roms either --i would always do a clean flash every month and set up my phone from scratch.

jhs39 said:
I've encountered a handful of apps that don't work on O but they probably will by the official launch date. But an app being optimized to help provide better battery life is something that goes on in the background that you won't notice unless you are a programmer that can analyze code or knowledgeable tech writers shame app devs publicly who don't do it. Android O has the ability to limit an apps background processes so it uses less battery but my understanding is that it only happens if the app developers voluntarily write code that allows O to do that to the app and a lot of devs are probably not going to do that if it is voluntary.
I'm not sure what your setup is but if you are manually flashing updates presumably you have a custom recovery and possibly root. Some Pixel users have reported successfully flashing OTA updates anyway because of the dual partitions on the Pixel but it wipes out your custom recovery and root and returns you to full stock and I'm not sure doing that works reliably. I don't know that the Flashfire/Flashify (I don't remember which app goes with TWRP) works on the Pixel. I don't have any experience flashing OTA updates manually via bootloader rather than the full monthly update. Personally I was never a fan of removing -w from a full flash because it can always lead to potential problems that aren't necessarily completely obvious. I always prefer to clean flash to give the phone a clean start, but that's just my own preference. I didn't like to dirty flash custom Roms either --i would always do a clean flash every month and set up my phone from scratch.
Click to expand...
Click to collapse
Okay that's good to know thank you!

You're welcome.

Pixel xl phone app unresponsive 9.0

Hi, I'm aware that several people have issues with the new pie rom.
Unfortunately, I have a problem that I haven't seen before on the forum:
It takes like a full 5 sec to call somebody and the same to end it.
It's very frustrating because I never know how to react in this situation (did he heard? Etc...)
I don't want to factory reset and I got everything stock.
Anyone has an idea on how to fix this?
Can I wipe cache with the stock recovery? Maybe install an other phone app?
Thx

i am having issues in pie as well. i cant seem to transfer large files to the phone.doing so makes the phone restarts. i tried it 5 times or so. fhis update is not good

Only way to clear up issues is a clean factory image install if this was not done to begin with.

OK thanks...
Though I blindfully hope someone will be get some alternative has I don't want do execute such extreme solution

b4bass said:
OK thanks...
Though I blindfully hope someone will be get some alternative has I don't want do execute such extreme solution
Click to expand...
Click to collapse
It's actually relatively painless. Apps restore automatically when you go through setup, calls and texts are restored, as well as system settings and WiFi networks. Takes me ~30 mins total, and maybe 5 of that is actually looking at the phone, the rest is letting it sync and restore backups automatically.

I was thinking about it doing a factory reset once the final came out but I've heard stories from fellow moviepass owners that are unable to use the app when switching phones. That would make a valid concern for factory resets as well. Not because of lag but I have noticed battery seems worse after the upgrade and wanted to factory reset to rule out. As I ran all the ota betas of pie a factory reset isn't a bad idea anyway.

tiny4579 said:
I was thinking about it doing a factory reset once the final came out but I've heard stories from fellow moviepass owners that are unable to use the app when switching phones. That would make a valid concern for factory resets as well. Not because of lag but I have noticed battery seems worse after the upgrade and wanted to factory reset to rule out. As I ran all the ota betas of pie a factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
Your device ID is tied to the app. When you factory reset and reinstall the app your device ID is reset. You can root using Magisk and then install Titanium Backup to backup the app and data, this will preserve the ID. i had to do this when switching ROMS.

Camera won't open; YouTube doesn't load

My Pixel 2XL is acting up starting this morning
- The camera app won't open, it crashes instantly. Other apps can't access the camera. I tried clearing the data, cache and restarting. Nothing has worked so far.
- YouTube is stuck in a load loop, all is see is the loading circle to infinity. I attempted to clear cache and data and install an older version. Again, nothing works.
- Restarting didn't solve anything.
- Both issues linger in safe mode.
Any ideas on wtf could be going on?

boeder9 said:
My Pixel 2XL is acting up starting this morning
- The camera app won't open, it crashes instantly. Other apps can't access the camera. I tried clearing the data, cache and restarting. Nothing has worked so far.
- YouTube is stuck in a load loop, all is see is the loading circle to infinity. I attempted to clear cache and data and install an older version. Again, nothing works.
- Restarting didn't solve anything.
Any ideas on wtf could be going on?
Click to expand...
Click to collapse
Sounds like you've got an unexplained, interesting and unwanted glitch! Are you full stock, or rooted?
Your only solution will likely be a factory reset, or possibly a dirty fastboot flash of the factory image so as not to wipe your data. You might even get by with just fastbooting the vendor image as well.

Badger50 said:
Sounds like you've got an unexplained, interesting and unwanted glitch! Are you full stock, or rooted?
Your only solution will likely be a factory reset, or possibly a dirty fastboot flash of the factory image so as not to wipe your data. You might even get by with just fastbooting the vendor image as well.
Click to expand...
Click to collapse
Full stock.
I want to avoid any resets tbh.
Could the OTA Monthly Update solve anything?

boeder9 said:
Full stock.
I want to avoid any resets tbh.
Could the OTA Monthly Update solve anything?
Click to expand...
Click to collapse
It's definitely worth a try. Just like fastbooting the factory image without the -w :good:

Badger50 said:
It's definitely worth a try. Just like fastbooting the factory image without the -w :good:
Click to expand...
Click to collapse
I guess I'll wait for the Sept update, if that doesn't work, I'll try the manual flashing
Sent from my Pixel 2 XL using Tapatalk

boeder9 said:
I guess I'll wait for the Sept update, if that doesn't work, I'll try the manual flashing
Click to expand...
Click to collapse
The job of flashing the factory image while saving data is super easy. If you have a pc and a half hour your golden. If you wanna give it a go, let us know and one of us can walk you through it if you have any concerns...
Sent from my Pixel 2 XL using XDA Labs

Even i have the same camera issue. It suddenly stopped working. Some times it does start after a few tries if i hold it in landscape mode. But mostly it keeps crashing and doesn't even allow other apps to access camera.

So a quick follow-up. Here is what i've done so far:
- Cleared storage/cache and uninstalled the camera updates
- Installed Android 10
- Updated to Camera 7.0 Beta
- Booted into safe mode.
None of these actions solved the issue.
I then resetted my phone (2 days ago) and that seemed to have solved the problem. However, starting a few minutes ago and while I was taking photos, I again lost focus in the lens and the app crashed.
What could be the issue? It seems its the focus is problematic though it worked for a good while. Surely it isn't hardware as the camera worked for ~40 hours after resetting.

boeder9 said:
What could be the issue? It seems its the focus is problematic though it worked for a good while. Surely it isn't hardware as the camera worked for ~40 hours after resetting.
Click to expand...
Click to collapse
Just because it worked correctly for around 40 hours after a reset doesn't mean that you can rule out hardware issues as a culprit. Especially since you have done everything you possibly could on the software end and it hasn't helped.

Strephon Alkhalikoi said:
Just because it worked correctly for around 40 hours after a reset doesn't mean that you can rule out hardware issues as a culprit. Especially since you have done everything you possibly could on the software end and it hasn't helped.
Click to expand...
Click to collapse
You're absolutely right. I did another reset (this time without restoring from backup) and the camera doesn't open at all. I'm hoping its a OS bug.
Thank god the Pixel 4 will be released in 4 weeks.

CyberpodS2 said:
The job of flashing the factory image while saving data is super easy. If you have a pc and a half hour your golden. If you wanna give it a go, let us know and one of us can walk you through it if you have any concerns...
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I have exactly the same problem that they report, it does not open cameras or YouTube.
Can you give me the steps to upload a factory image?
Regards

Android 10 - Factory reset needed?

Hello, everyone!
I just installed Android 10 onto my Pixel 3 XL a couple of hours ago and I've noticed battery drain and some lag. Is a factory reset suggested at this point, since I flashed a new Android version?
Edit:
I had animations removed under "Accessibility" and I toggled it back on, then I turned Dev. Options on and switched animations to .5x and the problem seems to have went away. I'll have to update you all on battery life later. Still, the question remains... Is a reset suggested?

I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?

animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good

razrlover said:
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good
Click to expand...
Click to collapse
Were you on the latest beta before the update? My update file was only 5.5mb. Went pretty quickly.

is it worth factory resetting device with this latest update?

Jay01 said:
is it worth factory resetting device with this latest update?
Click to expand...
Click to collapse
No, if you used the ota through phone, google would of already done maintenance before the install, ie, removed incompatible apps settings and features.

Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.

animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.

bobbyphoenix said:
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.
Click to expand...
Click to collapse
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit

animeva said:
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit
Click to expand...
Click to collapse
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.

For small updates like monthly security patches or version increases of 0.1 or 0.0.1 I usually don't worry about doing a clean install since the changes are usually pretty minimal. For large updates I like to do a clean install just for piece of mind that all the crap that built up on my phone over the past year is gone, to eliminate the general issues that pop up with dirty installs, and having a squeaky clean fresh install just feels nice once in a while.

jmartin72 said:
Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.
Click to expand...
Click to collapse
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.

v12xke said:
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.
Click to expand...
Click to collapse
I was doing a complete wipe.
(Update) I finally got it to do a full factory image flash with a complete wipe. The only thing I changed was, I switched from Slot B to Slot A. Not sure if that was even the issue, but It worked, and now My Pixel 3XL is running really well. No issues that are being reported.

bobbyphoenix said:
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.
Click to expand...
Click to collapse
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now

animeva said:
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now
Click to expand...
Click to collapse
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.

v12xke said:
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.
Click to expand...
Click to collapse
if i do a full image, not the OTA version, does that require a factory reset?

animeva said:
if i do a full image, not the OTA version, does that require a factory reset?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader. If you are unlocked go ahead and flash the full image. Be sure to do a version check of your adb/fastboot. Sometimes you can get into trouble if you have old versions in a different location. You need to be sure you are running version 29.0.2 (July 2019). If you did not lose all your user data on past attempts, do a dirty flash (removing the -w flag from the flash-all.bat file). If you already lost your data, then just run the script as-is. GL.
Edit: If you were trying to update 9->10 using an OTA, that is probably your issue. The full image will properly reformat your file system for 10.