Related
Well before deciding to root, my phone was freezing when making a call. Sometimes the system would allow a conversation, then all of a sudden I would get a ringing sound followed by frozen software, I read, researched and tried not to bug any of you. I found possible issue with the proximity and light sensor. Also read on a reputable Android website, that Sprint had follied some of the PRLs OTA. So I decided to change the possible hardware flaws and Root. Low and behold it resolved the ringing that followed the freezing, but not the freezing. Was going good with Wicked Sensation 5.0, but could not stand the constant update request. That beloved Rom eventually did the same. So changed to 5 different roms and went from TWRP to Phils recovery since then. I am currently on Static 4.3, all roms worked great until I sent/recieved a call. As soon as I hit talk phone freezes and all audio ceases to function. Sometimes itll tease me after a dalvik wipe, but always after hitting "Talk," everything regarding S3 audio or sound, stops functioning.
Does anybody know about the issue I am describing? I switched the audio components so can this Handset Issue MB related? It is hard for me to rule out software due to the audio coming back after each newly installed rom. Before its demise, Audio sounds great. The audio disappears after a call. Just concerned about going to a Sprint repair center for the wait. If this is software related it highly likely my issues will come back. Not a pro, but well versed in the rooting process. As a ExSprint employee I went through all of Sam's rooted and never been stumped on a "Hardware vs Software" problem like this. If I find out its Knox Im taking a Google Nexus to record me throwin my S3 on the wall and sending it to Samsung....jk lol. (For reals though, the increasing challenges to root for every update pisses me off cause the Samsung always got better hardware then the others, but WTF Sammy?)
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.
nighcore said:
I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.
Click to expand...
Click to collapse
I also use a Huawei watch and the drive safe app. I'm gonna install an older version of the state farm app as it recently was updated now that I think of it.
Sent from my Pixel XL using Tapatalk
thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
FWIW: I've had no Bluetooth issues. Only things I use it for are connecting to my two cars for phone, and Android Auto (which uses USB and Bluetooth connection).
I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.
millerd79 said:
I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.
Click to expand...
Click to collapse
Ever since I got the Gear S3, my Bluetooth will restart every single time I disconnect my Bluetooth headphones. It also never routes calls through my headsets unless I go into Bluetooth settings and uncheck and then recheck the phone audio option of those headphones every time I reconnect them. I've tried maybe 6 different BT headsets and it's the same case with all of them.
I have been having this issue since NMF26U as well. NOF26V actually seems even worse. It doesn't go off immediately upon connection or disconnecting from my car, but then randomly wile the BT lite will disappear while it is disconnected from any devices. Toggling it back on works as does a reboot that comes back on with BT activated even though it was off when rebooting. Hard to believe after this many updates that BT issues continue to be an issue with this phone.
Probably background tasks are getting killed aggressively. Despite being "not battery optimized", my VPN app gets killed too, if I don't touch my phone for too long. E.g. at night. And yes, I'm facing Bluetooth issue too.
Strange, Bluetooth hasn't turned off since my first post. ?
Sent from my Pixel XL using Tapatalk
I've had this issue and I'm not on the latest firmware. It's happened twice now. Very random, a week between. Maybe it was an update with the Google app, I've noticed a bunch of updates recently
I am having the same issue. The only thing I use my bluetooth for is my car. I have to turn it back on everyday when I start my commute.
I think I found a work around....
thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!
Kokopelligod75 said:
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!
Click to expand...
Click to collapse
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!
t3chfaith said:
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!
Click to expand...
Click to collapse
Yeah I would be very curious if it works for you as well and hopefully it does. I was getting very frustrated with it but since I changed those settings it seems to be working fine now and I haven't really noticed any difference in battery performance either.... If you don't mind, keep me posted as I'm curious. Thanks!
Had the Bluetooth turn off on my XL before even entering my car (but I didn't see it happen except when I was about to get in the car and noticed no BT indicator). This was approximately an hour after a reboot and no BT devices had been paired though the indicator was on for some period after the reboot. Pretty hard to believe it was an optimization issue since I had run no apps after the reboot. While typing this, the BT icon disappeared again. Add this to getting a Verizon "Server Unreachable" error on my wife's Pixel yesterday and my XL this morning that both needed reboots to remedy. My frustration with this phone is pretty bad today. Both are unlocked BL, rooted with newest SU, running newest TWRP and newest Google version but otherwise stock. P.S. When you see about 4 Google play updates a day for about 2 weeks (with not very many apps installed other than the base) it is hard to guess what my be causing the issue. OK, rant over.
BT has definitely been a PITA since the latest security update. It's completely ruining the music experience on a car I bought days before the update came out. Since the update I constantly have to toggle bluetooth on then off again to get the phone to connect to the car. Then I have to open Google Play Music and start playback manually. This happens several times a day and is very annoying. Had not a single issue before the update.
I am having issues with Bluetooth disconnecting as well. Was bad on previous build but this most recent update, NOF26V build, is worse. I connect to my truck, watch, and speaker system in home and office. Happens randomly without notice. I have tried to test the "do not distrub" theory, after reboot, etc., so far I have not figured out a root cause or time.
Trying the optimized thing for the heck of it. I noticed that only share was listed and not MDI services. I wonder if that is only available on Google phones and not Verizon somehow or only shows if the BT is connected to the device, but I'm not in the car to check.
I too have a gear 3 frontier and since then I have to reconnect my pixels bluetooth, pretty much once everyday. very frustrating lol
Same BT problem
I have been having the same issue with BT switching itself off for about a week now. Never had any BT issues prior to that. Mine is a Verizon Pixel XL. I noticed it when it wouldn't connect to my car, but I quickly discovered that was because BT was off on the phone. I always leave BT on, so I knew something was funky and paid close attention after that. Once I turn it back on it connects to everything just fine and it stays on for the duration of me using it at that time. But when I go to use it the next time, it is off again. It can be a variable length of time in between when I use it, so I don't know how soon it turns off, but it has to be within just a few hours. This pattern suggests to me that something is turning it off, perhaps to save battery, if it goes without being used for a certain time period. I did not knowingly turn on any setting that does that, so it makes sense that an update changed something. I have not tried the workaround/fix mentioned above; I will do it and report back.
Hi folks,
I frequently stream NPR / This American Life or similar apps in my car (2015 Toyota Highlander), via bluetooth to the car's audio. Until today, the name of whatever title I was streaming would show up on the car's screen. Basically metadata... name of the show, name of the episode, time... that sort of thing.
Today I updated my G3 (D851) from Lollipop (20g) to Marshmallow (30e). Immediately after finishing the update, any streamed content shows on the car screen (head unit) as "Unknown Artist" and similar blank entries instead of the name of whatever is streaming.
That's really annoying. How can I fix this? Again, it's definitely a Marshmallow thing. Never once did this on Lollipop.
TIA!
Frankenscript said:
Hi folks,
I frequently stream NPR / This American Life or similar apps in my car (2015 Toyota Highlander), via bluetooth to the car's audio. Until today, the name of whatever title I was streaming would show up on the car's screen. Basically metadata... name of the show, name of the episode, time... that sort of thing.
Today I updated my G3 (D851) from Lollipop (20g) to Marshmallow (30e). Immediately after finishing the update, any streamed content shows on the car screen (head unit) as "Unknown Artist" and similar blank entries instead of the name of whatever is streaming.
That's really annoying. How can I fix this? Again, it's definitely a Marshmallow thing. Never once did this on Lollipop.
TIA!
Click to expand...
Click to collapse
what app are you using, I think the protocols are set by the app not the OS. I know some of my music players support A2DP and others don't. Try different apps, you can also try forgetting the pair and repairing, or checking the settings of the pair to make sure everything is enabled. I had a giltch once where when i paired my phone to my car it only had a basic connection but nothing else worked and i had to repair. If you are using stock roms then I doubt it's Rom related. Some other things you could try is powering down the phone pull battery and reboot, just to fully reset all hardware, or a hard reset of the rom just incase there was an issue during the update process. Just some thoughts.
The two apps I use are the NPR News app and the This American Life app. Been using them for years. They both fine yesterday morning, but immediately after the update to Marshmallow the car screen reports Unknown Artist etc. Forgetting the connection on both ends and re-pairing doesn't fix it. The ROM is the stock 30e Marshmallow ROM from LG.
I've done a battery pull; didn't help. I heard early Marshmallow builds in general had some bluetooth issues but figured they would be worked out by the time a second release was made for our phones.
I will check the pair settings... haven't actually done that yet. Maybe there's some new option in there that's off by default.
Thanks to all for any other thoughts.
So, for a test I deleted ALL Bluetooth profiles on both the car and the phone, then pulled the battery on the phone, turned off the car, restarted the car, and rebooted the phone. PRior to this I checked the profile settings; all the boxes were checked.
That done, I re-paired the phone to the car.
I then played something from the This American Life app. Blank info showed up on the car screen. Tried the NPR app, playing a story from there. Blank info. In a fit of pique I poked back and forth between the car's home screen and it's audio selection screen, and returning to the home screen lo and behold there was the info about what was playing! How strange.
I switched back to This American Life, and the info on the car screen did not change... it stayed as the info from the program I was playing before. Went into the car's audio settings and back out to home screen. Now the info refreshed.
My current hypothesis is that under Lollipop, the phone "pushes" the metadata to the car, and it picks it up instantly. Under Marshmallow, it seems the car has to pull the data, and the screen gymnastics I was doing accomplished this.
I will test the theory by installing the apps on my Lollipop tablet, and trying to play them on the car, and seeing what the results are.
Marc
Okay. I tested on my now-marshmallow phone and my lollipop tablet.
Anytime I play from an app like this American life which I used as my test platform from my lollipop tablet, it immediately displayed on the cars home screen the metadata for the show.
Anytime I used my marshmallow phone to do the same thing with the exact same version of the app the metadata did not show on the home screen no matter how long I waited, however if I went into the program details on the car by pushing the section on the screen where the details should be it would then display the details. If I back out to the home screen again the metadata remains visible there.
It's very clear because this change in how it works on my phone happened immediately after upgrading to marshmallow that this is a difference between how marshmallow and lollipop handle the data. It seems that under lollipop data is automatically pushed out to the car upon starting playback where as under marshmallow the car seems to have to refresh or pull the data from the phone.
Again, this works the same way for several apps... not just This American Life.
I took delivery of a Tesla Model 3 on March 30 of this year. At the time, it was running Tesla's software 2019.5.15, but within a day it had upgraded to 2019.8.4, then 2019.8.5, then 2019.12.1 a couple of days ago, and finally to 2019.12.1.1 today. Through all of this, I've had no problems with Bluetooth connections to my OnePlus 5t phone for media streaming; however, I have had problems with placing and receiving phone calls, and the problem has gotten worse with Tesla's 2019.12.1 or 2019.12.1.1 (I'm not sure which).
I never tried making phone calls in the day or so I had Tesla's 2019.5.15, but I did with 2019.8.x, with about a 50% success rate. Sometimes it would work fine, but other times I'd get very stuttery sound, as if the connection was cutting in and out about ten times per second. Initially, I was running LineageOS 15.1; however, in part because I hoped to resolve this problem, I updated my phone to LineageOS 16 about two weeks ago. That update did not fix the problem, unfortunately, but it also did not make it any worse.
Since my car has updated to 2019.12.1 or 2019.12.1.1, though, the problem has gotten worse: Now, when I try to place a call, at best I'll hear a brief click, short series of clicks, or beep, and then I get silence. When receiving a call, the phone rings, I hear a ring tone over the Tesla's audio system, and the Tesla's screen shows an incoming call. I can answer the call via the Tesla's screen, but again, I get no audio. Worse than all of this, sometimes, on both incoming and outgoing calls, the Tesla's screen has gone completely blank a few times. This isn't guaranteed to happen, but it's happened at least four times to me today as I've been testing things.
Some of what I've tried, with no success:
Adjusting volume settings on both the car and the phone
De-pairing the phone and the car, rebooting both, and then re-pairing them
Updating the phone to the very latest LineageOS build (lineage-16.0-20190428-nightly-dumpling-signed.zip)
Using "developer mode" Android options to adjust every Bluetooth option I could find (AVRCP version, audio codec, audio sample rate, bits per sample, channel mode [stereo vs. mono], LDAC codec)
Testing with both incoming and outgoing calls
This same phone works fine with a Bluetooth headset. On my previous car (a 2017 Chevy Volt), I had few problems, although on about 5% of the calls, I did experience the stuttering audio problem that kicked up to 50% frequency with the Tesla before it stopped working altogether.
I've gone to Tesla's Web site and used their "contact us" link to file a bug report (although there was no "bug report" option, so it may not get routed correctly).
Does anybody here have any other ideas of what I could do, short of replacing my phone or installing another Android version? (I'm really trying to avoid the pain of setting everything up again!)
srs5694 said:
I took delivery of a Tesla Model 3 on March 30 of this year. At the time, it was running Tesla's software 2019.5.15, but within a day it had upgraded to 2019.8.4, then 2019.8.5, then 2019.12.1 a couple of days ago, and finally to 2019.12.1.1 today. Through all of this, I've had no problems with Bluetooth connections to my OnePlus 5t phone for media streaming; however, I have had problems with placing and receiving phone calls, and the problem has gotten worse with Tesla's 2019.12.1 or 2019.12.1.1 (I'm not sure which).
I never tried making phone calls in the day or so I had Tesla's 2019.5.15, but I did with 2019.8.x, with about a 50% success rate. Sometimes it would work fine, but other times I'd get very stuttery sound, as if the connection was cutting in and out about ten times per second. Initially, I was running LineageOS 15.1; however, in part because I hoped to resolve this problem, I updated my phone to LineageOS 16 about two weeks ago. That update did not fix the problem, unfortunately, but it also did not make it any worse.
Since my car has updated to 2019.12.1 or 2019.12.1.1, though, the problem has gotten worse: Now, when I try to place a call, at best I'll hear a brief click, short series of clicks, or beep, and then I get silence. When receiving a call, the phone rings, I hear a ring tone over the Tesla's audio system, and the Tesla's screen shows an incoming call. I can answer the call via the Tesla's screen, but again, I get no audio. Worse than all of this, sometimes, on both incoming and outgoing calls, the Tesla's screen has gone completely blank a few times. This isn't guaranteed to happen, but it's happened at least four times to me today as I've been testing things.
Some of what I've tried, with no success:
Adjusting volume settings on both the car and the phone
De-pairing the phone and the car, rebooting both, and then re-pairing them
Updating the phone to the very latest LineageOS build (lineage-16.0-20190428-nightly-dumpling-signed.zip)
Using "developer mode" Android options to adjust every Bluetooth option I could find (AVRCP version, audio codec, audio sample rate, bits per sample, channel mode [stereo vs. mono], LDAC codec)
Testing with both incoming and outgoing calls
This same phone works fine with a Bluetooth headset. On my previous car (a 2017 Chevy Volt), I had few problems, although on about 5% of the calls, I did experience the stuttering audio problem that kicked up to 50% frequency with the Tesla before it stopped working altogether.
I've gone to Tesla's Web site and used their "contact us" link to file a bug report (although there was no "bug report" option, so it may not get routed correctly).
Does anybody here have any other ideas of what I could do, short of replacing my phone or installing another Android version? (I'm really trying to avoid the pain of setting everything up again!)
Click to expand...
Click to collapse
Hello again from TMF (turok3000) . Can confirm I see exactly the same as you (lineage 16.0 + tesla 2019.12.1.1).
I would say you're best off posting here: https://forum.xda-developers.com/oneplus-5t/development/rom-lineageos-16-0-pie-oneplus-5t-t3843026
Do you happen to have tried with latest stock oxygenos ? I'm guessing not since you mention not wanting setup hassle (I'm in a similar situation).
Thanks for the suggestion of posting in another thread. I've done so, with a few updates.
I did back up the phone and tried installing stock OxygenOS as a test; however, the installation went badly -- it hung with a spinning logo on first boot. Thus, I restored my (mostly) working configuration. I may give it another try later, but there's only so much time I can invest in this sort of thing each day.
Any luck with this? I also have a Tesla Model 3 and the same exact problem as you. I'm using crDroid but it is largely based on LineageOS.
Maybe there is something I can try? I messed with all the dev options for bluetooth.
I've worked around it by re-installing OnePlus's OxygenOS. I'd prefer LineageOS or something else more open, but for the moment, switching to OxygenOS seems like the only solution. A caveat: I haven't tried any recent build (from the last month or so). It's conceivable it's been fixed and I just don't know it yet. Also, some others, using OnePlus phones other than the 5t (IIRC, the OnePlus 6 and/or 3) report that reverting to OxygenOS does not help them. If you've got a 5t, though, reverting to OxygenOS, although a nuisance, may be worth trying. There's a thread tracking the problem on a Tesla forum here:
https://teslamotorsclub.com/tmc/threads/bluetooth-problems-on-phone-calls-only.150774/
The problem is common on LineageOS for multiple phones, but it also occurs on some other phones, even including some iPhones. At least one unofficial LineageOS build is not affected; but that build may have been tweaked or rely on proprietary drivers. Overall, then, it looks like more of a Tesla problem than a phone problem, but it's hard to be sure without digging into the code and running diagnostics that I'm not competent to do.
srs5694 said:
I've worked around it by re-installing OnePlus's OxygenOS. I'd prefer LineageOS or something else more open, but for the moment, switching to OxygenOS seems like the only solution. A caveat: I haven't tried any recent build (from the last month or so). It's conceivable it's been fixed and I just don't know it yet. Also, some others, using OnePlus phones other than the 5t (IIRC, the OnePlus 6 and/or 3) report that reverting to OxygenOS does not help them. If you've got a 5t, though, reverting to OxygenOS, although a nuisance, may be worth trying. There's a thread tracking the problem on a Tesla forum here:
https://teslamotorsclub.com/tmc/threads/bluetooth-problems-on-phone-calls-only.150774/
The problem is common on LineageOS for multiple phones, but it also occurs on some other phones, even including some iPhones. At least one unofficial LineageOS build is not affected; but that build may have been tweaked or rely on proprietary drivers. Overall, then, it looks like more of a Tesla problem than a phone problem, but it's hard to be sure without digging into the code and running diagnostics that I'm not competent to do.
Click to expand...
Click to collapse
Ah well thanks for getting back. That is disheartening, as I had been using OOS since I got the phone on release day & finally thought I should try something different. It sounds like I'm gonna have to go through all the efforts to revert back to OOS.
For reference, it did not work for me using crDroid builds from 6/23/19 and 6/30/19.
I'll use Tesla's feedback system to put my "vote" in towards fixing these bluetooth issues.
My Model 3 received an update yesterday to 2019.24.4 and the Bluetooth calling works! Just thought you should know. I'll cross post on TMC.
Ok all, I'm getting quite frustrated with my P6P. Was on A12 and sideloaded the OTA for 13 Beta 4.1. I didn't want to lose any data but also didn't want to enroll in the beta program which would have pushed the OTA anyway.
Beta was working but definitely noticed a hit to battery life at first and some weird things like running warmer, phone being warm just sitting on the pixel stand fully charged, just generally not feeling right. The good news was, it seemed to have gotten a little better over the next few days of use but still not great so when I saw stable A13 released last week, instead of going back to 12, I committed to using the Android flash tool and fully flashing A13.
After flash, I chose to restore my Google One / Drive backup and omg the battery life was completely abysmal and running hot. We are talking losing 20% per hour of light usage, standby was losing 10%+ per hour and wasn't going into deep sleep at all. I thought at first it was my Galaxy Watch4 and the Samsung health app causing the majority of the issues but when I disabled "activity tracking" on the app, it didn't fully resolve the issues.
Other issues include: taking phone out of my pocket, screen sometimes doesn't wake up (I remember this was an issue with A12 but G eventually acknowledged and fixed but I guess it's back), connected via Bluetooth to my car (no Android auto) the ring tone is no longer playing when I get a call, generally feeling not as smooth, weird system usages showing up in accubattery and the Android battery manager as using good chunks of battery, etc.
At this point I got another idea: reflash A13 but don't restore from backup (which I hate doing because then I have to go through every single setting to find stuff I changed and set it again both in the system and on apps). It seems like that helped a little with stand by battery drain but still seems to be draining at a higher level while in use. The issue of screen not waking up sometimes is still present and now, I just saw this morning that I tap on the Google Play System Updates within the security menu and it does nothing. I was able to get into it yesterday morning and it found an update (still says July 1 though) but I didn't reboot to complete it until this morning. Now I can't get into it anymore at all. I also found some weird folders in my DCIM folder and another one that referenced icloud and iphone transfers but I've never been an iphone user.
I'm so frustrated with this phone lately and it seems like no matter what I do, I cannot get it to work right with multiple little things as well as battery drain.
Am I the only one? And if not, anyone have any ideas on how to fix my issues? Is it time to contact Google for an RMA? I was one of the launch day orders so I don't know if my specific hardware is the issue. I am now locked in to 13 bc of the bootloader thing, I didn't manually flash the BL to both slots, only used official flash tool which you'd think of this was a critical thing, Google would do that with the flash tool but I guess they can't get their left hand to recognize what the right hand is doing.
Just typing this post on Chrome browser for 10 mins, burned through 4% battery.
You're not the only one...
https://www.reddit.com/r/GooglePixel/comments/wddk1s
nomisunrider said:
You're not the only one...
Click to expand...
Click to collapse
Thanks for that reddit article but that's not exactly answering my questions. Yes I know I'm not the only one who's had battery issues and I've gone through all those steps up to and including reflashing cleanly and wiping.
What about the other stuff I'm having issues with? Anybody else experience any of those issues? Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Essentially I'm debating on wiping again and/or reloading the OS again but if others are having the same or similar issues then it may just be Google being Google and releasing a buggy build (yet again).
Side note, I also just got a notification that Google One backup is currently running and to tap for more info but yet, I don't have it plugged it nor is the phone idle. It is on wifi though but I tapped the notification and nothing was happening. It said the last backup was at 3:37am. Also, I am now down another 10% of battery since posting this with barely any usage.
Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.
jrg67 said:
Is there anyone on 13 stable NOT having some issues with battery or other oddities?
Click to expand...
Click to collapse
I've had no issues with 13 but didn't have any on 12 either. Day one phone too.
roirraW edor ehT said:
Hi, I've been on Android 13 Stable for the past 7+ days, and haven't had any problems.
The only suggestion I have is a start completely fresh type, but there's no guarantee it'll fix anything. Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
^ It's fixed things for many users, including myself, that nothing else including the factory image would fix, but for me, that was six months ago so obviously on Android 12, and it was a different issue than any that you're describing.
Click to expand...
Click to collapse
I did what I thought was starting fresh the last time around (Sunday). Used the official flash tool and didn't restore anything from backup. All I did was add my Gmail accounts and then manually downloaded every app I use and then tried to set all the settings again in both system and apps to how I like them. Is there something I'm missing? Is there a difference between the pixel repair tool and the Android flash tool? What about the settings that are flash tool? I have them set to wipe, lock, and force flash everything. Not sure if that exists on pixel repair tool. I've also noticed a fairly large reduction in size of the backup that occured last night with the apps section showing only 44 apps at about 11.7MB in size when my previous backup was 60 apps at about 48.2MB. I'm thinking of just wiping/reflashing again for the 3rd time but restoring from backup this time since it really didn't make much difference.
How about the Google play system up bug thing? Can someone tap on it and see if it comes up checking for an update or if it does nothing like me. And when I say nothing, just the menu option to tap on just lights up but doesn't open anything. How about the issue with the screen not waking up if taken out of your pocket?
For what it's worth, I haven't started from scratch since I accidentally did last December (after originally setting my phone up in late October or in November). I used the Android 13 factory image over top of my existing install without wiping.
I'm under the impression that yes, there is a difference between the Pixel Repair Tool and the Android Flash Tool, but I've never actually used the Pixel Repair Tool. I know the first several months, at least, the Pixel Repair Tool hadn't yet been updated to work with the Pixel 6 Pro. It may have been updated since then, I just don't know for sure.
When I have wiped/factory reset in the past six years (starting with my Pixel 1), I always restore all or almost all data from Google's backup. I do have Swift Backup do automatic nightly backups as well, but I only restore data (through Swift Backup) for the apps that I really need to - definitely not very many.
Your settings for the Android Flash Tool sound fine.
Is the "Google Play System Up(date) bug where clicking on it doesn't do anything? If so, it doesn't do anything for me, either. Mine doesn't even light up, but I have dark mode on, plus using Pitch Black theme from AOSP mods.
I rarely have my phone in my pocket, so it probably just doesn't come up often enough for me to have noticed, so I can't confirm one way or the other.
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.
Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!
roirraW edor ehT said:
Cool, thanks for sharing the news! I hadn't bothered checking manually in very many months, possibly since late last year or very early this year.
Click to expand...
Click to collapse
jrg67 said:
Well, I found an answer to the Play System Updates "bug". We are not the only ones, road warrior! https://www.google.com/amp/s/9to5google.com/2022/08/20/check-google-play-system-updates-pixel/amp/
Click to expand...
Click to collapse
Google Play Store v31.9.20-21 is rolling out and will fix that Play System Updates "bug".
jrg67 said:
Now, on to the other stuff like no more ring sound over Bluetooth in my car, the screen not waking sometimes, terrible battery life, etc etc. Boy do I love this time of year when new the OS launches, screws up many phones and makes people trade them in for the next version. P7P here I come!
Click to expand...
Click to collapse
Here's another weird one.. apparently now I can't keep my phone on vibrate while in the car. For a test, I turned my ringer on and then tested it again.. low and behold, it rang through the speakers in my car. This is trash. I know Android enabled in-band Bluetooth audio years ago and I recall this same thing happening way back with my nexus 6p and each pixel I've had but this one. There was a setting in developer settings to turn that off which fixed it and allowed it to work correctly but with this phone, it worked out of the box so I never thought twice about it. I just checked the dev settings and it's nowhere to be found. I have no idea what A13 could have done to screw that up nor do I know if the dev setting even existed on this phone prior to A13. I just don't get it. I guess I could see if there's any updates to my car's multimedia system but I have an Audi and any software updates come from the dealer for a price. How dumb. I guess I'll be scouring the Audi forums for a fix on that.
Meh, the Google Play Store updates are irrelevant to me. So no worries there on my part, haha. But this phone's battery life has been rather questionable. I have, however, noticed that after being on the full A13 build for around a week or so and disabling 5G from the get-go that my battery now lasts MUCH longer. My phone does not seem to generate as much heat either - which is always a plus. But I also seem to have more phone/messaging reliability than I have had in the past with this device.
I am beginning to think that the modem and 5G has had the most to do with this phone's imperfections.
Also - for OP - but I have noticed that my phone often doesn't wake up with a single tap either - but only when the gyroscope stays mostly stationary for a longer period of time. When I pull the phone out of my pocket, it usually comes on with one tap. But if it has been sitting on a table or other mostly flat surface for a while, it takes two taps to wake the display.
Ultimately, I won't be getting the Pixel 7 Pro. I will, however, be getting the Pixel Fold which should launch at around the same time =).
I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.
96carboard said:
I can't say too much about the google provided and infiltrated system images, since I only booted it on that image ONCE -- just long enough to flip the "allow OEM unlock" switch so I could flip it to AOSP and then GrapheneOS. But I will say that on GrapheneOS, the update from 12->13 has been pretty seamless. One fairly minor glitch with activating wifi hotspot that was fixed with yesterday's SECOND update, but aside from that, not a single one of the bugs mentioned in this thread.
Click to expand...
Click to collapse
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.
jrg67 said:
This kills me. Why is it that a third party dev can release a stable build with little to no bugs but if bugs are found, a patch is pushed out right away to fix yet Google cannot seem to get it right. Furthermore, if they do fix bugs, they refuse to push them out-of-band. This isn't 2008 anymore, we shouldn't need custom ROMs to get the best performance out of our phones.
Click to expand...
Click to collapse
Well, aside from the bugs issue, as time goes on, more and more you need something besides what it ships with in order to actually have security and privacy. Google has fallen a very long way from the openness and respect that they once promised. The final straw for me was when they started working with governments to include and share covid contact tracing functionality.
Update:
Apparently the 4th complete wipe and OS flash was apparently the trick to fix the majority of my phone's issues. I did restore from my backup this time because the last time that I started from scratch, it made no difference. I figured if it's still going to be buggy, I may as well have all my info and settings correct. It's now been about 24 hours. See below for status of my issues.
1. Massive battery drain - fixed for the most part. Still have to restrict Samsung Health app but for the most part, it seems to be back to normal.
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
3. Play system update button broken - already found this wasn't an A13 bug. I still haven't gotten the fixed update of playstore but before this latest wipe and OS flash, I sideloaded the latest version and it fixed it.
4. Connected to Bluetooth in car no longer plays ringers out loud. - Weird one as I think this is part A13 because Google baked in a new BT stack that's been in development since A11 called gabeldorsche https://www.androidpolice.com/android-gabeldorsche-bluetooth-stack/ and partly my infotainment system in my car. I am not on the current version of the car's infotainment but since my car is a '14 Audi, it doesn't have OTA updates.
5. Heating up during normal use - seems to be fixed
6. Warm while on the pixel stand and fully charged - haven't been able to observe this one bc last night, I put the phone on the stand and by morning it was at 72% and not charging. No clue if that's a new bug or if it was just not sitting on there just right. Didn't really look into it but we'll see what happens tonight.
So that seems to be the majority. Overall the phone doesn't feel "weird" anymore and most things I was having trouble with appear to be resolved. Sort of ridiculous that I had to wipe and reload the OS 4 times though.
jrg67 said:
2. Screen not waking up when pulled from pocket or elsewhere that the proximity sensor activated and screen was off. - Fixed so far
Click to expand...
Click to collapse
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.
96carboard said:
I actually had a similar issue with A12 -- when on a phone call, pull the phone away and it took forever to turn the screen back on. Seems to have been corrected with A13.
Click to expand...
Click to collapse
This one still may be around for me but perhaps not as severe as it was during the first 2 times I loaded 13. I just experienced it about an hour ago. Took phone out of my pocket to place on my desk at work and screen was black but the AOD did eventually come on by itself after about 10 long seconds. We'll see what happens.