Question Strange issue related to security - OnePlus 9 Pro

I seem to be having issues occasionally with apps being unable to restore sessions or being able to login into them, often completely loosing logged in sessions and not being able to access it properly until I reboot. I have also seen it let me login with finger print but not with the pin code.
I initially thought it was an issue with the ROM but I have since been on two different ROMs - Paranoid and now NameLess - and have had the same issues on both of those. Sometimes it seems to happen multiple times within a short period and then sometimes days so not sure where to start tracking it down or if there's some hardware issue in my device.
If anyone has any ideas what to try I'm all ears although I'm resigned to it happening now but figured I'd put it out there in case someone else has experienced it

Have you used MSM Tools to reset your phone between your two installations? Maybe it came from the A12 version used by Paranoid and the file concerned remained untouched when you changed for NameLess (which would be strange, considering that a majority of custom ROMs installations processes ask you to factory reset your phone)?

I didn't use MSM tools but I did reset to the original firmware/latest oos11 in between them. But I have just thought that perhaps slot b doesn't have the right stuff in, even though I made sure to do an update it was on slot a till a crash a couple days ago and that's when it started going wrong on nameless. I'm going to try switching it back to slot a later and seeing if it happens again. If so I know it's something on slot b. I'm pretty sure paranoid ended up running in slot b too and the last oxygen I actually used was slot b.
If so I'll try MSM tools to make sure it's got the right stuff in each slot. It's the first time I've done custom ROMs for a long time so probably missed something. Thanks for your suggestion. I'll have a look

Related

Accidentally Botched SW3 Firmware by Flashing TWRP

When I got my SW3 last summer, I stupidly ignored all those warnings about flashing TWRP to recovery, mostly because I didn't see what harm could come of it. However, while investigating a battery drain that's persisted despite multiple flashes to stock and more than a few attempts to use crpalmer's LCA43 kernel, I discovered via my SW3's kernel log that it's got some serious weirdness going on with its firmware.
As it turns out, it's reloading the pedometer firmware every three seconds. This happens because every time it loads the firmware, it promptly encounters some manner of error while running it, which then prompts Android to try to reload the firmware. My first hint that this was a firmware issue came from the fact that I can't access any sensor data via the developer menu. Under 'Manufacturer: Menu-Launcher' at the bottom of Developer Options, the entries for Accelerometer, Gyro, Magnetometer, and Compass are all blank, while Ambient Light Sensor and Step Counter are perpetually stuck at 0.0.
After trying everything I could think of in my attempts to fix this issue, I then began investigating other variations from stock that I'd had over the months that I've had my SW3. Rooting didn't appear to change anything related to the firmware, and crpalmer's LCA43 kernel (and craigcharlie's simple MTP mod and, later on, alex6600's modified version of the kernel itself) didn't appear to cause any of the issues I'd been experiencing for anyone else. Finally, I found a comment somewhere about the fact that flashing TWRP to recovery instead of just booting it would really mess things up because it uses a device tree different from the SW3's stock device tree.
Since then, I've been trying everything I can imagine to fix this, but I haven't had any success thus far. Because of that and a few other reasons, I haven't been able to mess with this since the end of January, but I'm really getting tired of my SW3 only lasting for about 6-8 hours with pretty minimal use. I think the closest I got to any sort of progress was using dd to individually flash partitions that'd been uploaded, but I don't think I was ever able to find an upload of mmcblk0p19, dt-blob.
Does anyone have any ideas about what I might be able to do to fix this? Specifically, I'm curious to know whether or not dding partitions damaged when I flashed TWRP should work; if so, would someone be so kind as to either post or PM me dded copies of the relevant partitions? Thanks in advance for the help!
Repair with PCCompanion. Did that some weeks ago. Version is LCA43.
If pc companion does not work (and it probably wont), hold down the button on boot, and you can force it to usb mode. If that does not work, hit the button twice to go to fastboot and flash the original OS (look for the repair threads).
Good luck.
Sent from my SM-T810 using Tapatalk

Pixel XL - HUGE data usage NOT rooted

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.

Recover, Root disappearing, WiFi breaking.

Ok I am having some serious issues as of late, I am far from an Android expert but have been using and rooting them since Android started, and I am also a Linux user. So as stated in the subject I have been getting these issues (not always together).
Recovery will disappear after a normal reboot.
Root will disappear after a normal reboot.
WiFi is "broken" after a normal reboot (is disabled, and can't be enabled).
My status bar disappears.
This has happened across a few different roms, but my main is Team OctOs Oct-N. This is making no sense to me at all. These things will happen after a ROM has already been setup and working for a time, that is what has me scratching my head. The only thing I can think of is some system has changed in the Pixel XL ROMs that I don't know about or something. I always start from a fresh phone, flashing google images, installing the rom the proper way, I always follow the devs install procedure for the most part (depending on the ROM) it is flash rom, flash vendor, flash twrp, reboot into twrp, flash gapps. Everything goes good it runs fine, and then some time after, sometimes a few days later, sometimes a few hours later, one or a combo of the issues listed above happen. I though maybe there was an issue with the actual rom. So i decided to try 1 or 2 other roms but some issue still arrives. Also when twrp wont boot (because it apparently disappeared) I reinstall it properly, and one would think I would be able to boot back into the existing system, but it don't, it always boots right back into twrp.
I am at a complete loss and the only thing I can think of is something has changed with the Pixel system that I am unaware of. Any info would be great I know that this is not a good description on what is actually happening but that's it I have no idea at all. Have a great day and thanks.
I have found that to get TWRP to stick I have to flash the zip and whatever else I'm flashing, then boot into my rom, then boot back into fastboot TWRP and flash the TWRP zip again, then boot back into the rom.
Root is tricky on this phone. Nobody can really answer what's going on there without knowing what month bootloader you are using, what app and what version of the app you are trying to use to root.
The other problems really sound Rom related. If you want to go from a truly fresh start with no chance of any corruption on either partition you might want to run flash-all.bat of the Google factory image separately to partition a and then to partition b. That cleared up problems for me in the past but I'm not sure why.
You might also consider running stock and seeing if the WiFi or status bar problems persist.
xxxtncxxx said:
Ok I am having some serious issues as of late, I am far from an Android expert but have been using and rooting them since Android started, and I am also a Linux user. So as stated in the subject I have been getting these issues (not always together).
Recovery will disappear after a normal reboot.
Root will disappear after a normal reboot.
WiFi is "broken" after a normal reboot (is disabled, and can't be enabled).
My status bar disappears.
This has happened across a few different roms, but my main is Team OctOs Oct-N. This is making no sense to me at all. These things will happen after a ROM has already been setup and working for a time, that is what has me scratching my head. The only thing I can think of is some system has changed in the Pixel XL ROMs that I don't know about or something. I always start from a fresh phone, flashing google images, installing the rom the proper way, I always follow the devs install procedure for the most part (depending on the ROM) it is flash rom, flash vendor, flash twrp, reboot into twrp, flash gapps. Everything goes good it runs fine, and then some time after, sometimes a few days later, sometimes a few hours later, one or a combo of the issues listed above happen. I though maybe there was an issue with the actual rom. So i decided to try 1 or 2 other roms but some issue still arrives. Also when twrp wont boot (because it apparently disappeared) I reinstall it properly, and one would think I would be able to boot back into the existing system, but it don't, it always boots right back into twrp.
I am at a complete loss and the only thing I can think of is something has changed with the Pixel system that I am unaware of. Any info would be great I know that this is not a good description on what is actually happening but that's it I have no idea at all. Have a great day and thanks.
Click to expand...
Click to collapse
This has been a real challenge with this phone (but I'm enjoying it). Anyway, the way I got a good stable set up is flashing the factory image to both slots (a/b), then adb/fastboot to twrp.img and flash ROM, then boot up. Then again the twrp.img and flash the twrp.zip and boot up. Then do the root and boot up , then go back and do the kernel (since it's EX and I want the gestures, I boot it up rooted before I flash EX). This works for me although I'm using Pure Nexus ROM. Hope this helps you, looks similar to what was posted by jhs39.

Bluetooth App Missing, Random Reboots, Deleted System Partition, No ROM in Storage

I've also posted this on Reddit and the OnePlus forums, but I'm hoping I can find an answer here, too.
Long story short: I really messed up my phone and I'm looking for help getting it to at least boot into the system. Lots of weird, confusing things have happened within the past few days, so bear with me; might be a long story, but I'll try to give you the abridged version.
I run locked and unrooted. I flashed OOS Beta 3 over 4.7.6 on my 5T, wiped my cache, and everything was wonderful for a week. Then one day, I got a system message saying "Bluetooth has stopped". I cleared that and thought nothing of it, but I got another message saying "Bluetooth keeps stopping". This message would actually pop up (with no exaggeration) every second. I could only stop the messages completely after going to the Bluetooth app and clearing the data, then disabling Bluetooth Scanning.
I figured the problem would fix itself, but the next day when I tried to connect to my car via Bluetooth, my phone would freak out again like the previous day. I had to listen to a CD like it was 1996. I thought I could fix the problem with a Factory Reset. As soon as I hit the Welcome screen, "Bluetooth has stopped". When I went to check the Storage section of the Bluetooth app in the Applications list, the app portion read 0 bytes. What? Even when I went into Settings --> Bluetooth and tried to turn it on, nothing would happen. I thought maybe I should revert back to 4.7.4 and start from the very beginning.
That served no purpose. The Bluetooth symbol did show temporarily in the Status bar as I was setting up my phone, but eventually disappeared, with the Bluetooth app once again taking up a whopping 0 bytes. I've done various combinations of installs, but I cannot get Bluetooth to function normally. And at some point, my phone developed a new problem: any time I hit the Bluetooth button in Quick Settings, the phone would eventually reboot on its own. Later, it wouldn't need any input from me at all. It would just be sitting in the Lock screen and reboot.
Icing on the cake: I got desperate, unlocked the bootloader, deleted the system and cache partition in fastboot, then wiped the data in Recovery with the hope that doing a completely fresh install would fix the problem, but at some point my internal storage got wiped and now I have no ROM on my phone to install. Even better: I'm having some real problems trying to install OOS (any version) on my phone via ADB sideload. I keep getting the message "cannot read <filename.zip>", even though it's in the correct folder.
I am currently back on my OnePlus 3 and the proud owner of a very sleek brick. I used to root and unlock Nexus devices and Moto X's, so I'm pretty embarrassed that I managed to ruin my phone while it was running (basically) all stock. It can still boot into Bootloader and stock Recovery. Is there anything at all that I can do to at least load OOS (or any ROM)? Do I have to send it back to OnePlus and beg for a replacement? Will they even take this phone in it's current state? Am I just SOL?
I've run out of ideas and patience. I'm really hoping someone out there can help me. At the very least, thanks for reading my long sob story. Hopefully this never happens to you.
try flash orero based twrp and flahs stock 5.0.3 zip in twrp, see if it works. then figure out the reset.
Why would you delete system from fastboot? Does people not formating partition from recovery more often?
The twrp I use
https://forum.xda-developers.com/oneplus-5t/development/recovery-twrp-3-2-1-0-oreo-8-0-8-1-t3729673
Update: I managed to unbrick my phone using an unbrick tool. The process was pretty painless and it will revert your 5T back to OOS 4.7.4 no matter what you did to it. Props to Drasm19 from the OnePlus forums and the geniuses behind this tool! Funnily enough, I was ultimately led back here:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
You guys more than likely already knew about this tool, but definitely keep this in mind if you manage to brick your phone like I did.
Now I'm back to my original problem: Bluetooth is really messed up. This is what I'm talking about:
https://imgur.com/gallery/eEkbX
No matter what I do, no matter how many times I flash any version of OOS, this is always the result. As you can see, even with the toggle in the "on" position, Bluetooth refuses to do what it's supposed to do and the app takes up 0 bytes. Something is up...
I've searched a lot of threads that reference Bluetooth issues, but it looks like I'm the only one with this problem. I'm open to any and all suggestions that'll help me solve this and get back to using my 5T. I already miss those awesome navigation gestures.
Thanks again for your time and help.
im not really a developer type, but a while back it was easy to root and un root with kingo. and i could put things in the system with FX. please bare with me a sec.. p9's i like, but getting some glitches. when the gboard went byby, on reset, i had to set up my welcome screen by shouting at the phone.. 'at sign' does give you @ but to get capitals you have to trick it, eg. 'USA' to get an upper case 'u'
anyway, i got in, and got gboard from 'my apps' ..fine but of course, wont survive another reset.
so about the missing bluetooth.. iv got the directory info. and the missing files. thanks ..but i didnt want to wipe the phone, it seems rooting has become a can of worms.
wouldnt it be nice if there was a nice (no root) app , to run bluetooth from the apps ? so that 'joe blow' doesnt have to throw his phone away, cos it doesnt work in the car ect.. thanks

constant "Bluetooth keeps stopping"

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

Categories

Resources