Just a quick heads up march up date has been released but the release notes only say that specific fixes are for the pixel 3 and pixel 3 XL. I don't know if there's anything for our OG XL.
ttocs99 said:
Just a quick heads up march up date has been released but the release notes only say that specific fixes are for the pixel 3 and pixel 3 XL. I don't know if there's anything for our OG XL.
Click to expand...
Click to collapse
I'm not certain, but people on reddit claim there won't be any new functional updates for our device :/
"OG Pixel will only receive security patches since Dec 2018. It's EOL for OS updates and functional updates."
Sent from my Pixel XL using XDA Labs
Velfess said:
I'm not certain, but people on reddit claim there won't be any new functional updates for our device :/
"OG Pixel will only receive security patches since Dec 2018. It's EOL for OS updates and functional updates."
Click to expand...
Click to collapse
I would of thought they would of looked in to the pie battery drain people are having but nevermind I'm still enjoying my experience with the OG XL and I'm still stock. I don't know whether to take the plunge and go custom ?
This is the support map for nexus and pixel phones (expand the sections) and yeah, Pixel probably won't get any new major update.
But, we still would receive security patches until october (theorically)
ttocs99 said:
I would of thought they would of looked in to the pie battery drain people are having but nevermind I'm still enjoying my experience with the OG XL and I'm still stock. I don't know whether to take the plunge and go custom ?
Click to expand...
Click to collapse
Well there's really no risk, it's not like something that takes a long time or that you can mess up. You could literally flash any custom ROM for this phone and completely screw everything up to the point where you couldn't use it. Then all you have to do is plug your phone into your computer and flash the latest factory image from Google and everything will be okay. Wiping your phone and flashing a custom rom takes less than 10 minutes and so does flashing the factory image back to the phone if you mess it up. So there's really no downside trying custom firmware on this phone. The only thing that you have to remember is never relock the bootloader. Once it's unlocked never ever ever lock it again. And even that is something that you have to manually do it's not like something you could do by accident.
Phalanx7621 said:
Well there's really no risk, it's not like something that takes a long time or that you can mess up. You could literally flash any custom ROM for this phone and completely screw everything up to the point where you couldn't use it. Then all you have to do is plug your phone into your computer and flash the latest factory image from Google and everything will be okay. Wiping your phone and flashing a custom rom takes less than 10 minutes and so does flashing the factory image back to the phone if you mess it up. So there's really no downside trying custom firmware on this phone. The only thing that you have to remember is never relock the bootloader. Once it's unlocked never ever ever lock it again. And even that is something that you have to manually do it's not like something you could do by accident.
Click to expand...
Click to collapse
I've flashed custom ROMs in the past to Samsung phones old Sony's HTC mtk devices and nexus range I just want a fully blacked out rom for the oled screen with out using substratum as that causes phones to slow down.
ttocs99 said:
I would of thought they would of looked in to the pie battery drain people are having but nevermind I'm still enjoying my experience with the OG XL and I'm still stock. I don't know whether to take the plunge and go custom
Click to expand...
Click to collapse
This! Accubattery reports 70 percent health and I can only barely squeeze 2.5 hours SOT on my phone. :/ This battery life is absolutely atrocious and nothing seems to point at battery drain aside from Android OS and Play Services.
snappycg1996 said:
This! Accubattery reports 70 percent health and I can only barely squeeze 2.5 hours SOT on my phone. :/ This battery life is absolutely atrocious and nothing seems to point at battery drain aside from Android OS and Play Services.
Click to expand...
Click to collapse
Ask the Google assistant for a battery health check it will tell you if it's in good health or not
Phalanx7621 said:
Well there's really no risk, it's not like something that takes a long time or that you can mess up. You could literally flash any custom ROM for this phone and completely screw everything up to the point where you couldn't use it. Then all you have to do is plug your phone into your computer and flash the latest factory image from Google and everything will be okay. Wiping your phone and flashing a custom rom takes less than 10 minutes and so does flashing the factory image back to the phone if you mess it up. So there's really no downside trying custom firmware on this phone. The only thing that you have to remember is never relock the bootloader. Once it's unlocked never ever ever lock it again. And even that is something that you have to manually do it's not like something you could do by accident.
Click to expand...
Click to collapse
Uh.. I'm new here, any side effect if the bootloader is relocked?
dic1911 said:
Uh.. I'm new here, any side effect if the bootloader is relocked?
Click to expand...
Click to collapse
Don't relock bootloader when unlocked unless you have flashed a 100% factory image but I'm going custom ROM soon just haven't got my laptop back from being repaired.and there should be no side effects if you know what you're doing.
dic1911 said:
Uh.. I'm new here, any side effect if the bootloader is relocked?
Click to expand...
Click to collapse
The majority of people who hard brick their devices here are ones that relock their bootloader's and then realize they hadn't wiped and flashed a stock factory image. So they can't use fastboot and end up not having a phone that will boot. There's no reason other than selling the phone you would ever need or want to lock your bootloader after unlocking it. It's just a bad idea all around.
Related
Just did the ota update. Have since rebooted phone twice. Update and phone don't like each other! Chrome keeps auto-closing. And phone is lagging/freezing continuously. Phone was rooted years ago, and never any issues, even upgrading to Kitkat. This one I'm not to sure about!!!!!
Oh, and booting takes about twice looking too!
Keeps getting better...can't download anything from the play store. Says it's downloading, but never goes anywhere.
andygold said:
Just did the ota update. Have since rebooted phone twice. Update and phone don't like each other! Chrome keeps auto-closing. And phone is lagging/freezing continuously. Phone was rooted years ago, and never any issues, even upgrading to Kitkat. This one I'm not to sure about!!!!!
Oh, and booting takes about twice looking too!
Keeps getting better...can't download anything from the play store. Says it's downloading, but never goes anywhere.
Click to expand...
Click to collapse
Were you rooted? The last OTA update tried to take away root and it was really hard getting it back. It's acted strangely ever since.
wildbean98 said:
Were you rooted? The last OTA update tried to take away root and it was really hard getting it back. It's acted strangely ever since.
Click to expand...
Click to collapse
I took the update against my better judgement and sure enough soft bricked and now phone wont go into DL mode...grrrr
Major issues here as well. My SD card is now blank and doesn't want to mount. Big slowdowns as well. Any way to remove this update ?
Sent from my SHIELD Tablet using Tapatalk
Was finally able to DL apps, but at a crawl. I cleared the cache including dalvik, and everything is back to normal. And I'm still rooted!
I used Cache Cleaner NG from the play store
Soft bricked
I have bricked my phone after accidentally accepting it. Got back the phone again with lg flash tool. Once restarted the phone, rooted it, used titanium backup apk to freeze the software updater.
I don't think that it is wise to do a software update while rooted, it usually denies the process anyways.
Actually guys, its most likely that malware piece that was making its way around. Didnt anyone else read about it a few days ago? Let me hunt it down and see if i can post a link here. Standby....
Update: hold the phone, i may have been mistaken. Standby...
Now im soo broke i cant even pay attention!
ThaHawk said:
I don't think that it is wise to do a software update while rooted, it usually denies the process anyways.
Click to expand...
Click to collapse
Hi, rooting a phone does not stop the update anyway since you can unroot very easily, if it is supersu apk. But if a person installed custom recovery, it can brick the phone since the update tries to use the stock recovery. I learnt it in the hard way.
sdivk said:
Hi, rooting a phone does not stop the update anyway since you can unroot very easily, if it is supersu apk. But if a person installed custom recovery, it can brick the phone since the update tries to use the stock recovery. I learnt it in the hard way.
Click to expand...
Click to collapse
I stand corrected, your absolutely right!
ThaHawk said:
I stand corrected, your absolutely right!
Click to expand...
Click to collapse
Thanks. If you have a rooted lg e980 without custom recovery, you can use quickboot apk to enter stock recovery, which has limited features.
The problem with unlocking bootloader and use custom recovery is, if there is an update, there is no way to relock the bootloader and flash stock recovery. If sombody can shed the light on this matter, i really appreciate it.
I am looking for a way to relock the bootloader and install stock recovery without using lg flash tool.
Not that i am expecting an update from AT&T anytime soon.
+1
its better its included on CM based ROMs also
I want to love the OnePlus 3 but I'm not feeling it. I'm unlocked, rooted and running X-Posed framework and gravitybox on the 3.1.2 update.
Things that are really bugging me right now compared to the LG G3 I came from:
Lack of SD card. I thought I wouldn't care but I do. The 64GB of storage is enough but it was kind of safety blanket with flashing ROMs that I miss.
Inability to change out the battery. I know, only LG has that now, but it was so easy to carry an extra battery in my pocket compared to a charger or a some device and a cord and look for someplace to charge it. It was great while traveling on long flights or walking around all day to never have to think about where and when I need to charge my phone. I don't know that I want to carry that Dash charger everywhere with me.
The power button on the side - this is where I grab the phone when putting it in my pocket so it keeps turning on when I actually want the screen to stay off. LG buttons are on the back.
The screen - I'm fine with the 1080p and I don't need Super pixel whatever, but the light reflections in various environments are very annoying compared to an LCD screen.
I knew these trade-offs when I bought the phone but I didn't think through how I would feel about them.
Maybe I'm overplaying these in my head and they aren't as important as I think they are but again, I'm not feeling the love because of these trade-offs.
I think want to return the OnePlus 3 and get an LG 5 which has all of the features I want (at a higher price). Or maybe just go back to the G3.
But two things...
1) Now that I'm unlocked and rooted, how should I go about restoring the phone to factory (or near factory)? Should I just restore the nandroid backup I took? Or does it not matter?
2) I can't start the return process because the One Plus system doesn't show I've received it yet - I'm going to call and see if I can get an RMA over the phone, but probably not.
You have just noted all of my worries.
I have a G3 at the minute and i said id upgrade when i found a phone that had :
1) SD slot
2) Swapable battery
3) NFC
I've ordered the OP3 but 2 out of my 3 reasons i "forgot" about.
Not sure how i will cope with side buttons again, or a fingerprint scanner on the front.
After this post, i will for sure not be rooting for a while just in case i end up in the same boat.
A
So do I just go into TWRP, clear the caches, and then install the stock recovery.img file over the top? Then, by not installing the SU binaries I'm no longer rooted, correct? I don't care if the bootloader remains unlocked because they should take it back even if it is.
Its better whene you relock the bootloader.
I found the link - seems straightforward. I already put in a return request.
http://forum.xda-developers.com/oneplus-3/how-to/how-to-unroot-oneplus-3-to-stock-oxygen-t3403324
I'm still not sure why the bootloader needs to be re-locked. It seems like that's something that could result in bootloops and other problems.
The LG G5 is what I want but even the H860 (LTE) is not yet unlocked, only the H850. So, I would get some of the features I want back, but then I couldn't root. If I can't root, then I'm stuck having to make software trade-offs. I may have to just stick with the OnePlus 3 now.
digger16309 said:
I found the link - seems straightforward. I already put in a return request.
http://forum.xda-developers.com/oneplus-3/how-to/how-to-unroot-oneplus-3-to-stock-oxygen-t3403324
I'm still not sure why the bootloader needs to be re-locked. It seems like that's something that could result in bootloops and other problems.
The LG G5 is what I want but even the H860 (LTE) is not yet unlocked, only the H850. So, I would get some of the features I want back, but then I couldn't root. If I can't root, then I'm stuck having to make software trade-offs. I may have to just stick with the OnePlus 3 now.
Click to expand...
Click to collapse
Did you have any luck with this? I can't find stock recovery anywhere.
I did not. I'm not returning the phone. I would have returned it with TWRP anyway. A bug in the bootloader puts me into stock recovery half the time anyway.
digger16309 said:
I did not. I'm not returning the phone. I would have returned it with TWRP anyway. A bug in the bootloader puts me into stock recovery half the time anyway.
Click to expand...
Click to collapse
Yeah I think I'm just going to have to return mine with TWRP. I can't help that they haven't released OOS or the recovery yet.
The stock recovery appears to be available with one of the toolkits I forgot which one it's the one with the cmd prompts just download and get the file from there or use it
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.
I installed the Oreo ROM on my G5S using fastboot. Everything ran perfectly and the device booted up and I set it up. Everything is great. But I did notice that the screen gets unlocked after touching the fingerprint scanner, little slower than it did on Nougat. And this is considerably slower when compared to Nougat. Anybody else noticed this?
ShattrdChain said:
I installed the Oreo ROM on my G5S using fastboot. Everything ran perfectly and the device booted up and I set it up. Everything is great. But I did notice that the screen gets unlocked after touching the fingerprint scanner, little slower than it did on Nougat. And this is considerably slower when compared to Nougat. Anybody else noticed this?
Click to expand...
Click to collapse
Ya it's somewhat slower than the nougat
I did not notice that slowness, but may be because I don't have any social media apps or games installed, just communication apps.
But I have an issue with play store, app update are painfully slow though it's not the issue with bandwidth, Even 20mb app takes forever. Never had this issue ever in my life.
The battery drains slightly faster and charges slightly slower. The responsiveness is not as good as 7.1. I flashed with Oreo using fastboot, flashed bootloader and gpt too. Is there any way i can go back to nougat?
ShattrdChain said:
The battery drains slightly faster and charges slightly slower. The responsiveness is not as good as 7.1. I flashed with Oreo using fastboot, flashed bootloader and gpt too. Is there any way i can go back to nougat?
Click to expand...
Click to collapse
Maybe you should pm @lohanbarth about downgrading.. Personally I think Oreo is the worst OS ever, and judging from countless other device threads I'm not the only one who passionately hates O. I hope that lineage 14.1 will be kept alive for montana.. (Captain Hindsight says he's afraid you shouldn't have flashed gpt.bin)
ShattrdChain said:
The battery drains slightly faster and charges slightly slower. The responsiveness is not as good as 7.1. I flashed with Oreo using fastboot, flashed bootloader and gpt too. Is there any way i can go back to nougat?
Click to expand...
Click to collapse
Ænimal said:
Maybe you should pm @lohanbarth about downgrading.. Personally I think Oreo is the worst OS ever, and judging from countless other device threads I'm not the only one who passionately hates O. I hope that lineage 14.1 will be kept alive for montana.. (Captain Hindsight says he's afraid you shouldn't have flashed gpt.bin)
Click to expand...
Click to collapse
hello, I flashed oreo with the fastboot on the G5S of my wife and she has no worries of battery or charge, can be that your charger or battery and defective, for the donwgrade you risk losing your imei or to brick your mobile.
Why shouldn't you have flashed gpt.bin?
Quark^2 said:
Why shouldn't you have flashed gpt.bin?
Click to expand...
Click to collapse
You cannot roll back to 7.1 once your flash the oreo gpt.bin and bootloader. If you try to flash 7.1, the phone will hardbrick.
Looks like the data encryption is slowing down things. I too see a lag with oreo. Especially when the device awakes from sleep status. It should be related with wake locks.
I did something.
1) Installed latest TWRP from here https://forum.xda-developers.com/moto-g5s/development/twrp-squid-twrp-moto-g5s-t3700656.
2) Booted straight into TWRP recovery.
3) Did a "Format Data". I repeated this step several times by rebooting to TWRP recovery, untill there was no formatting errors.
4) Then took a Backup of System, Data, Boot.
5) Wiped Dalvik, Cache, Data, System
6) Restored the backup.
7) Rebooted device with fingers crossed.
8) Device booted with no issues.
I don't see much lag now.
Please note that I am not suggesting this procedure.
I am sharing my experience.
If you like to proceed, please do it at your own risk. As it is already mentioned in this thread, it is wise to take a backup of EFS partitions.
Even though not much lag, I still dont like oreo because of its extra work to install substratum themes. Every time I have run the desktop client to install/update substratum theme. I really feel that it is a mistake that I did upgrade to oreo. I could have been happy with nougat. Probem with nougat is most of the custom ROM providers have stopped patching with security updates, except Lineage OS.
Thanks
KS
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