As soon as I upgraded my 2013 Nexus 7 (Wi-Fi) to JSS15R I started having a problem where every time I try to uninstall an app the tablet reboots. It's not a full reboot, however - it just jumps to the Nexus "X" logo and boots from there.
When I originally updated I was rooted, but I've since performed two factory resets and I still have the issue. I've searched and found lots of posts talking about random reboots, but this definitely isn't random. It's recreatable every time and only seems to happen when uninstalling an app. Is anyone else having the same problem?
Here's a vid showing what happens:
http://www.youtube.com/watch?v=yD2fDb4kHsY&feature=youtu.be
I seem to have fixed it. I'll leave the post here in case anyone else runs into the same problem.
A factory reset won't do it. You need to do a full Flash Stock and Unroot. I downloaded the factory JSS15R image from Google, then used the "Flash Stock + Unroot" option in WugFresh's Nexus Root Toolkit. Everything appears to be back to normal now.
Thanks for the thread.
I have the same issue mentioned above and can confirm that I have "never" rooted my new Nexus 7, so this is not likely the cause.
Also, the previous poster found that a full factory reset did not sort the issue, so thanks for this and now I won't lose time trying a reset.
Also, the previous poster pulled a full stock image from Google, which fixed his issue. Therefore, this might imply that the JSS15R incremental [I believe all updates so far for this devices were incremental] does not apply properly [in some or all cases]? and/or some bits were left out of the incremental? Or some errors were encountered while applying the incremental? Logs somewhere?
So, any idea when / if a full image will be rolled out from Google for the Nexus 7 (2013)? Never?
I suppose this is only thing good about the ~200 MB "full" CyanogenMod (CM) 10.2 nightly images I put on my SGS III [no incremental issues].
After owning this tablet for 2 months, I as still hoping for stability and have resisted "rooting it" or "ROMming it" in case I need to send to ASUS against the 1 year USA warranty [purchased from Best Buy in USA - April 2013 manufacture date]. Now in London, UK, so no easy way to return it to Best Buy or ASUS USA.
BTW, my first purchase of this problematic tablet was returned to Google (Play Store) in early August 2013. Most of the sensors did NOT work.
A bit off topic, but I wonder how well CM 10.2 would behave on this tablet? since even the core Android 4.3 software from Google [which CM is based on] is "still" struggling with issues 3 months after launch for so many Nexus 7 (2013) users.
If I have to wipe the device and install a full JSS15R ROM, then I am open to putting a different ROM like CM.
GjT
GJT-UK said:
So, any idea when / if a full image will be rolled out from Google for the Nexus 7 (2013)? Never?
Click to expand...
Click to collapse
Just a quick update to say that when I upgraded my tablet [Nexus 7 (2013)] back in December to Droid 4.4.0, this reboot issue went away.
Hello – does the 5.02 OTA notification pop up right away now for all 2013 Nexus 7s that haven’t yet been updated to Lollipop?
I want to factory reset my wife’s 4.4.4 Nexus 7 before upgrading to 5.02. It currently has the notification to upgrade, but I’ve ignored it (actually I disabled notifications for Google Play Services to avoid the nag for the past several weeks).
I want to avoid doing the factory reset and then not being offered the OTA notification for a day, week, or longer.
Will doing a factory reset right after updating to 5.0.2 make the device just as pristine as doing it just before? Maybe I should avoid worrying about when I’ll get the offer to go to 5.0.2 and do it now while I have it, and then factory reset – if the end results will be the same.
I want to ensure the tablet will work the best it can with 5.0.2. We had some really bad experiences with the original Nexus 7 2012 and I want to avoid having the update from 4.4.4 make things worse. We have a couple Nexus 5s that are working good enough with 5.0.1.
Thanks in advance.
GaryP2 said:
Hello – does the 5.02 OTA notification pop up right away now for all 2013 Nexus 7s that haven’t yet been updated to Lollipop?
I want to factory reset my wife’s 4.4.4 Nexus 7 before upgrading to 5.02. It currently has the notification to upgrade, but I’ve ignored it (actually I disabled notifications for Google Play Services to avoid the nag for the past several weeks).
I want to avoid doing the factory reset and then not being offered the OTA notification for a day, week, or longer.
Will doing a factory reset right after updating to 5.0.2 make the device just as pristine as doing it just before? Maybe I should avoid worrying about when I’ll get the offer to go to 5.0.2 and do it now while I have it, and then factory reset – if the end results will be the same.
I want to ensure the tablet will work the best it can with 5.0.2. We had some really bad experiences with the original Nexus 7 2012 and I want to avoid having the update from 4.4.4 make things worse. We have a couple Nexus 5s that are working good enough with 5.0.1.
Thanks in advance.
Click to expand...
Click to collapse
If you're gonna do a factory reset, you might as well just flash the factory image. That will guarantee that you'll have the possible install.
_MetalHead_ said:
If you're gonna do a factory reset, you might as well just flash the factory image. That will guarantee that you'll have the possible install.
Click to expand...
Click to collapse
Thanks for the advice - that's what I ended up doing this morning and it went well!
Although I had adb working on a Windows box for some time, I hadn't taken the opportunity to flash a factory image until now.
Hey all,
I've done heaps of searching here and the wider web but only found reference to rooted phones failing to take updates.
I can't get a screenshot on here right now as I'm at work so no wifibut:
- Android OS _______________3.04GB :silly:
- Chrome__________________434MB
- Google Services ___________24.13MB
- etc
When I read about the failed update I checked in there and sure enough I have a 2017-5 patches system update sitting there failed, when I retry it it will download successfully then do step 1/2 of the installation then fail.
So it seems this would be the problem but the phone is definitely NOT rooted, any ideas??
thanks
You speak in codes, man. Could you explain your issue simpler? Right now I see an Android OS usage of 3.04GB. That seems abnormally large times 10. No one should have that, really. So it seems like your Android OS process downloaded multiple copies of system updates in error. Is that your problem?
Your post is still largely incomprehensible, so I won't make a final conclusion.
These are just suggestions:
1) If your phone is downloading system updates over and over, just damn update so it stops, or factory reset your phone.
2) If this is some kind of a rogue app, you are literally funked. Good luck trouble shooting it.
In any case, GL!
Yes, android OS used 3.04GB in ~5 days, my best guess is it was due to repeated attempts at '2017-5 patches system update'
Sorry, when I did a search I got heap of references to rooted phones having this issue so I guess I just talked from that reference point? It seemed to be a known issue but for rooted phones.
I just wanted to be clear that my issue matched those symptoms but was not rooted.
1) I've tried a manual update (many times) fails at the same point, I assume this is what is causing the data usage, as mentioned above.
2) Pretty sure it's not a rogue app
I'll try a factory reset, it's only a couple of weeks old (warranty replacement) so I hadn't really thought to reset straight away.
The phone doesn't necessarily need to be rooted to fail the update. A previously rooted phone can also fail to update as described, but typically that would mean an unlocked bootloader. I would have figured that the phone would have been reimaged and the bootloader locked on a refurbished phone, but maybe that doesn't happen. Is the bootloader unlocked? If so you could image the phone yourself to see if that works to fix it. If the bootloader is locked and a reset doesn't work, then I figure you might need to contact support about getting a different phone.
https://developers.google.com/android/images
I think you've gotten good information from everyone so far but just to add some clarity.
I had this exact same issue and was not rooted but did have an unlocked bootloader.
A factory reset did not resolve it. At the time I had issues, there were questions about rooting the stock images so I flashed PureNexus and have never looked back or had the issue again. Also, Verizon did add data to my plan and credit my account for the additional charges to negate the cost. Hope this helps!
It sounds like an issue with your phone that Pixel support might be able to help you with but they will certainly suggest a factory reset so you should do that first. Since you have a refurbished phone you don't know how the previous owner was using it and its possible a modification he made is still on the phone and causing you problems. If the failed system update isn't actually causing the excess data usage it could also be a carrier issue. I know some Project Fi users had that problem and it was related to the service. Google gave people credit for the excess data. You could also have an app that is interfering with the update so a factory reset should definitely be your first step and I'm guessing it's fairly likely to fix your problem.
So, here's the basics:
AT&T Note 4, Official. Never had issues, never needed to root...
Build MMB29M.N910AUCS2EQF1
June 1, 2017 Security Patch Update
6.0.1
All updates have always come OTA.
Here's the issue:
When the MAY security update come out, I updated like I always do. Since then, my phone started locking up, randomly rebooting, all around pissing me off
I read about having Samsung Experience in Best Buy reapply the update, but our Best Buy no longer has Samsung.
So I went to AT&T to see if they had capacity to do it, nope; just a moron sales-boy who was clueless, just wanted me to pay $225 for my deductible and get an S8 (maybe if they offered the + I might have).
Went to a third party mobile repair and they quoted $35 up front but didn't guarantee they'd be able to 'find the update cause they're in China' (true story).
I've uninstalled apps and reinstalled systematically trying to find a culprit (to no avail).
Tried using Kies and Smart Switch and they both error when I enter the model and serial.
I did a factory reset from recovery and wiped caches, but the problem persisted.
So I installed Wake Lock (darken) and that seemed to tide it and 'cure' the problem.
June security update come out and I installed it. I had to remove and re-seat batteries, restart, pray to my fictitious gods and finally it got to the green App Optimizing and finished.
I removed the wake lock but the problems persisted; so I reinstalled it and that's currently where I am...
I have close to 20 years with computers, but am total n00b with Android.
I see there are the security updates here and downloaded the May and June.
At this point, would applying back to the May update have the possibility of helping even though I've now installed the June?
If so, how? I read you copy it to the root of an SD Card and apply update through the recovery screen, is this correct?
Should I factory reset/wipe caches before re-applying the update?
If I need to re-image the phone (another possible fix I read), what file do I need to use to go about doing that?
At this point, I'd like to A) limp by til the Note 8 comes out and B) get this back up and running so my kids can inherit it for their games when I get the 8...
Any help or direction would be greatly appreciated.
(Just noticed this might be more appropriate in the Help section. Mods, please feel free to move this to the correct sub-section. I can't find a way to delete the post and repost it there...)
I just started receiving the error "Bluetooth keeps stopping" on my Pixel 3 XL a week ago. It comes and goes seemingly completely at random, sometimes clicking close app will work and other times it will just keep coming back over and over until I restart my phone. It's a huge problem because it takes my wifi and sometimes I think even my mobile data down with it. I've read a bunch of posts and it seems like many people have been having this issue.
I've tried turning off Wi-fi and Bluetooth scanning.
updating Google Play system update.
Clearing cache and storage of Bluetooth.
resetting every bluetooth device I own
Factory Reset
sideloading an OTA image
Flashing a factory image
I'm all out of ideas. The only thing I can come up with is it's a hardware issue, but generally hardware issues I run into are not so sporadic and random. Usually it's either broke, or not broke. It doesn't seem to correlate to how hot the phone gets. I feel like Google broke something with an Android update. I've tried to warranty it through Google but I purchased it new on Ebay and they want the original purchasers name, email and order number. Anyone know of a way around that for Google's warranty?
As a last ditch effort I just flashed the Sep 18th Android 9 factory image, crossing my fingers that for some reason that does something.
My only other idea is google has driver binaries posted for pixel devices. Do these binaries get written over/rolled back when the factory image is flashed? Or are they isolated and not touched when flashing a factory image? Could flashing new driver binaries fix the problem? If so, does anyone have a guide on how to flash the driver binaries, google gives documentation for sideloading the OTA or flashing factory images, but nothing for how to install the driver binaries.
iwestfall7062 said:
I just started receiving the error "Bluetooth keeps stopping" on my Pixel 3 XL a week ago. It comes and goes seemingly completely at random, sometimes clicking close app will work and other times it will just keep coming back over and over until I restart my phone. It's a huge problem because it takes my wifi and sometimes I think even my mobile data down with it. I've read a bunch of posts and it seems like many people have been having this issue.
I've tried turning off Wi-fi and Bluetooth scanning.
updating Google Play system update.
Clearing cache and storage of Bluetooth.
resetting every bluetooth device I own
Factory Reset
sideloading an OTA image
Flashing a factory image
I'm all out of ideas. The only thing I can come up with is it's a hardware issue, but generally hardware issues I run into are not so sporadic and random. Usually it's either broke, or not broke. It doesn't seem to correlate to how hot the phone gets. I feel like Google broke something with an Android update. I've tried to warranty it through Google but I purchased it new on Ebay and they want the original purchasers name, email and order number. Anyone know of a way around that for Google's warranty?
As a last ditch effort I just flashed the Sep 18th Android 9 factory image, crossing my fingers that for some reason that does something.
My only other idea is google has driver binaries posted for pixel devices. Do these binaries get written over/rolled back when the factory image is flashed? Or are they isolated and not touched when flashing a factory image? Could flashing new driver binaries fix the problem? If so, does anyone have a guide on how to flash the driver binaries, google gives documentation for sideloading the OTA or flashing factory images, but nothing for how to install the driver binaries.
Click to expand...
Click to collapse
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation
billyt1 said:
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation
Click to expand...
Click to collapse
Just a precaution, as soon as you start locking and unlocking bootloader you're going to be doing a complete wipe of your device. So backup before hand. You'll also want to do a complete install of the factory image, with the wipe option, before you attempt to lock the bootloader. If you lock the bootloader and you are not 100% stock of something goes wrong you could end up with an expensive paper weight.
billyt1 said:
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation
Click to expand...
Click to collapse
The error happened once immediately after a full factory image flash before I had downloaded a single program or changed a single setting, so I don't see how it could be bluetooth settings, battery optimization, wifi/bluetooth scanning, or a rogue app. Oddly enough, since posting this last night I've managed to go 12 hours without an errors after flashing the Sept 2018 factory image. buuuuuuuut now I'm afraid to upgrade to Android 10 again.
jd1639 said:
Just a precaution, as soon as you start locking and unlocking bootloader you're going to be doing a complete wipe of your device. So backup before hand. You'll also want to do a complete install of the factory image, with the wipe option, before you attempt to lock the bootloader. If you lock the bootloader and you are not 100% stock of something goes wrong you could end up with an expensive paper weight.
Click to expand...
Click to collapse
Thank you for making sure I understood this. Yeah, I generally factory reset my phone and laptop once a year so I always back everything up before a reset. And yeah, I haven't changed anything from stock on this phone since I've had it, so unlocking and locking the bootloader should never cause any issues. As I told Billy, the Sept 2018 image seems to have fixed the problem, fingers crossed.
Is it probable that upgrading once again to Android 10 will cause the issue to return? The Sept 2018 image must have changed an internal setting or driver that wasn't functioning properly.
iwestfall7062 said:
Is it probable that upgrading once again to Android 10 will cause the issue to return? The Sept 2018 image must have changed an internal setting or driver that wasn't functioning properly.
Click to expand...
Click to collapse
I can't tell you for sure, but i would think the latest firmware should work. There have been a number of Bluetooth fixes since the original firmware, which it appears you're on now. That, and lots of security fixes.
jd1639 said:
I can't tell you for sure, but i would think the latest firmware should work. There have been a number of Bluetooth fixes since the original firmware, which it appears you're on now. That, and lots of security fixes.
Click to expand...
Click to collapse
Yeah, I mean I would much prefer being on Android 10 and having the latest updates, I normally update as soon as they come out. But, given that I flashed the Jan 2020 image and bluetooth was still broken, and then flashed the Sep 2018 which seems to have fixed it, I'm hesitant to go back to the Jan 2020 updates. Kind of tending towards the if it isn't broken, don't fix it philosophy right now. If I had time to monkey around with my phone all the time I wouldn't mind, but the semester just started and I use my phone for everything at school so I don't really have time for it to be not working. >.< Such an odd issue and odd fix.
Looks hardware related, like the cable is loose.
wangdaning said:
Looks hardware related, like the cable is loose.
Click to expand...
Click to collapse
And it's continuing to happen even with the Sept 2018 factory image flash.
Why do you think it's hardware related and that a cable is loose when a reboot fixes it? If the cable is loose a reboot shouldn't fix it.
iwestfall7062 said:
And it's continuing to happen even with the Sept 2018 factory image flash.
Why do you think it's hardware related and that a cable is loose when a reboot fixes it? If the cable is loose a reboot shouldn't fix it.
Click to expand...
Click to collapse
What do you have Bluetooth connected to when it happens?
jd1639 said:
What do you have Bluetooth connected to when it happens?
Click to expand...
Click to collapse
Nothing. It doesn't matter whether anything is connected or not. It literally happened on first boot up of a fresh flashed Jan 2020 factory image, before I had put a single thing on the phone.
Generally I have my Fitbit Versa connected, I got 2 tiles awhile ago, but first troubleshooting thing I did was remove the app and delete those from bluetooth since those were my latest additions to bluetooth. I have backbeat fit headphones I use sometimes, the same with bose soundlink ii headphones, ps4 controllers, a jbl pulse 3, my car radio. But I factory restored all of those items so they weren't trying to connect to my phone, and then flashed the factory image. So I don't see how it has anything to do with an actual bluetooth connection.
Im having this same exact issue. Android 9 was always super smooth. It all started with the Android 10 update. I was having all kinds of Radio related (wifi/bluetooth/data) issues ever since. I noticed sometime in Nov/Dec that google released some kind of radio system app update and things got a little better. But I still have the Bluetooth problem (like today, which prompted me to find this thread) or every once in a while ill lose all data connectivity and have to reboot my phone for everything to come back. I LOVE the dark theme, but this has to be the worst Android update from a stability standpoint ive ever experienced.
Just want you to know it isnt just you. Its something to do with some phones on Android 10
JJT211 said:
Im having this same exact issue. Android 9 was always super smooth. It all started with the Android 10 update. I was having all kinds of Radio related (wifi/bluetooth/data) issues ever since. I noticed sometime in Nov/Dec that google released some kind of radio system app update and things got a little better. But I still have the Bluetooth problem (like today, which prompted me to find this thread) or every once in a while ill lose all data connectivity and have to reboot my phone for everything to come back. I LOVE the dark theme, but this has to be the worst Android update from a stability standpoint ive ever experienced.
Just want you to know it isnt just you. Its something to do with some phones on Android 10
Click to expand...
Click to collapse
Yeah, I wish this thread held a solution for you. I've searched and searched and tried every solution I've found on google and nothing has worked, and really none of the threads I have found have ever had a concrete solution either, just one or two people going "well I did THIS and it worked", and a bunch of people saying it didn't work for them. I just cannot fathom how a full factory flash back to the very first image would not revert the changes that came with Android 10. That's why I was questioning whether or not a factory flash replaces driver binaries. It's the only way I could see the factory flash to Sept 2018 not fixing our issue. (Other than it really being a hardware issue, but that doesn't seem possible to me.)
Oh wow, you're still having same issues on Android 9??
Im still on Android 10, most recent update. I did do a full factory flash a few weeks ago and it was quite the improvement. But I still do have the Bluetooth/radio issue every once in a while, like yesterday.
I wonder if it's a hardware issue and/or substandard hardware performance that Android 10 made more prevalent? That's something we'll probably never know
I only pointed to hardware as I had a similar issue years ago. The radio connections were slightly loose so it would come and go. I do hope you are able to figure out what is wrong, was not trying to be rude.
wangdaning said:
I only pointed to hardware as I had a similar issue years ago. The radio connections were slightly loose so it would come and go. I do hope you are able to figure out what is wrong, was not trying to be rude.
Click to expand...
Click to collapse
Oh no, I didn't think for a second you were being rude. And I appreciate your idea, just with what I'm experiencing with my specific phone it doesn't seem to be a hardware issue.
Strangely enough, the issue has been tapering off as of late, after the factory resets I just continued to use my phone while I wait to figure out if I can get a refund or a warranty replacement, etc. The issue has been occurring with much less frequency since then. Still happens, but not like it was.
Damn, the Bluetooth bug is back again. It was so bad the other day, my phone kept bootlooping for like 20 mins while I was on the road.
I finally just let phone sit for a while and it fixed itself. Man this is completely sporadic.
JJT211 said:
Damn, the Bluetooth bug is back again. It was so bad the other day, my phone kept bootlooping for like 20 mins while I was on the road.
I finally just let phone sit for a while and it fixed itself. Man this is completely sporadic.
Click to expand...
Click to collapse
Yeah, mines been better for like 4 days, and then it just crashed and rebooted by itself earlier today.
has anyone gotten to the bottom of this yet? it seems to be a result of the play store system update being "stuck" on Sept 1st...even if you get it to download to the current version, currently March 1st, after a reboot it will not show the March update has been applied. And should it actually show that the March update has been applies, within a day the phone will reboot and the bluetooth bug will return, strangely the update to the play store system reverts to Sept 1st.
I'm having this issue with my son's phone. I tried unlocking the bootloader and flashing the factory img from April but of course the bug is still there, and after signing in the Play Store system is of course dated Sept 1st
There is no fix. I made an official Android Issue Tracker thread.
https://issuetracker.google.com/issues/151033055
and a Google Pixel Phone Help thread.
https://support.google.com/pixelphone/thread/32828289?hl=en
Google's being ****ty about it. I eventually just bought a new Pixel 4 XL. I needed a functional phone for school and work, and as much as I hate to spend money on another Google product after this mess, they do make the most powerful pure android phones with the best camera. Ebay FTW, $600, never giving them another penny directly.
If you still have warranty, get it warrantied immediately, and don't take no for an answer. I dawdled around thinking it would get fixed and even though I reported that I was having issues with it directly to Google's phone support BEFORE the warranty expired, by the time I called a second time and pushed a manager to see if they could warranty it, my warranty had expired so they told me to go jump in a lake.
to make it worse, Google told me the phone still has an extended warranty but I'm not the original owner and have no way to contact that individual. But you need that person's email address for it to work. So it was purchased but because of this technicality it's null and void. I get the security of it but it's still garbage