Related
If I try to navigate from the Zenwatch, the phone brings up google navigate even if the phone is sleeping. I would think that might be an issue in a pocket, but that's not the biggest issue.
The destination seems to get set correctly but neither the phone or the watch continues to navigate. They both seem to lock up.
Subsequently any other Nav app (I hope Waze gets Wear support soon) is unable to navigate as they are unable to get GPS lock. Looking at other GPS helper apps shows zero sats in range. Stopping/Restarting location services doesn't solve the problem. Only resetting the phone does.
Maybe it's just me. Sprint HTC One Max, stock. Anybody else?
I noticed this the other day when I was testing out navigation for fun. Once I took my phone out of my pocket, it seemed like it was able to get a lock again and things went more smoothly. I know gps can be a bit sensitive sometimes and maybe having it right next to your leg like that blocks the signal?
When the problem (GPS lockup) manifests there is nothing that will get it going other than a phone reset. I normally have my phone in a holder high on my dash where gets good reception, but when it gets in that state, not even one satellite shows a hint of a signal. Today I even made sure to stand outside holding my phone up in clear sky just to be sure.
Even if I don't access nav Google maps or Micro Maps from the watch it still locks up at some unknown point. I normally keep GPS on all of the time and have a number of apps that store locations from time-to-time. When I get in my car, Waze automatically starts but I can't get any sat signals until I reset my phone.
I'm experimenting with a theory that another member brought up in a different thread that there may be a connection with using a watch face that also includes weather and the number of GPS requests it makes. I've changed to the basic face that is in all of the marketing photos and continuing to test. I guess my next step will be to leave the watch at home :crying: to make sure that something wonky hasn't happened with the phone itself.
Are there any other frequent GPS users out there that can confirm or haven't experienced the problem? It doesn't seem to matter if you use the nav functionality on the watch.
The updates this morning seem to have fixed the problem.
Hello! Firstly I'd like to say thanks to any regular posters, this site helped me root my phone in the first place! I am trying to sort out what might be the cause of this problem and remove it, hopefully without starting over, as it was a pain in the butt to get the phone set up how I wanted and I do not have a full night to commit to it at the moment.
I have a Samsung S2 (the t-mobile branded one, sgh-t989), android 4.1.2 (kernel 3.0.31-1003885). This problem is recent and came on suddenly without changing any settings or installing any new software. The phone behaved normally for the first few months I owned it, it is a used phone, however, and I have no idea how the original owner treated it.
The problem is that brightness becomes tied to one or more of the sensors, and it takes several restarts, or sometimes days of waiting for the problem to go away. The brightness most often becomes tied to the accelerometer, where having the phone pointed at 45 degrees (or 01:30 o'clock), results in near 0% brightness, while returning to full brightness at 90-0 (or 3 through 12 o'clock). Occasionally it ties to another sensor (proximity?) or changes seemingly randomly, and once or twice has tied to the compass, with North being the brightness sink (with a similar 'darkness range' to orientation). The problem starts without a discernable cause.
Whatever the problem is, it also appears to disable, or for the most part inhibit multitouch. Around the time the problem started, tasker disabled and refuses to re-enable, if it is relevant. Shortly after the problem started, any push notification began turning on the screen (with a normal timeout, however). The problem persists through changing of any of the settings, toggling any modules, and through multiple resets, and never resolves itself without a cycle of multiple pulling-outs of the battery. After it is resolved, it usually remains fixed for a day or so before re-appearing.
If anyone has any suggestions for chasing down the problem, or has heard of anything similar, I'm all ears. I would like to avoid doing a factory reset, especially since I have no assurance it will resolve the problem. I'm happy to provide any additional information. Thanks for your help!
So I have noticed when I am going on long trips that my GPS keeps bugging out on google maps. At first I thought it was maps being weird but now I'm starting to think its the GPS in the phone itself. I'll be driving down the highway and it will suddenly start pointing the other direction like i just made a turn. After about a tenth to a quarter of a mile it will correct itself. Over the course of a 200 mile trip it did this every few minutes. Sometimes it would think that I had pulled off the offramp when I was still cruising highway speeds. This and the camera issues are making me seriously consider selling this phone and getting something different...
Krazy_Calvin said:
So I have noticed when I am going on long trips that my GPS keeps bugging out on google maps. At first I thought it was maps being weird but now I'm starting to think its the GPS in the phone itself. I'll be driving down the highway and it will suddenly start pointing the other direction like i just made a turn. After about a tenth to a quarter of a mile it will correct itself. Over the course of a 200 mile trip it did this every few minutes. Sometimes it would think that I had pulled off the offramp when I was still cruising highway speeds. This and the camera issues are making me seriously consider selling this phone and getting something different...
Click to expand...
Click to collapse
In Google maps click your location (little blue dot), then in the bottom left hand side click calibrate compass. I was having the exact same issue until I did this.
I have tried doing the calibration and it still wont get better than "low" accuracy. Do you get better than low?
Mines medium right now. I remember when I was having issues it showed low too. I had to get out of my car and do the compass calibration again as for some reason it wouldn't move off of low every time I tried in my car.
Yeah it's terrible. Hoping someone else has some fixes
Same annoying gps issues here as well
Just happened today for the first time. No clouds or building, I was out in the open. Marker flipped 180° 3-4 times while I approached a stoplight... hard to know which way to turn.
Makes me think this might be related to the recent 10.0.6 update?
skelzer said:
Just happened today for the first time. No clouds or building, I was out in the open. Marker flipped 180° 3-4 times while I approached a stoplight... hard to know which way to turn.
Makes me think this might be related to the recent 10.0.6 update?
Click to expand...
Click to collapse
Yes, that is exactly my lips around a hundred and eighty degrees numerous times. Takes forever for it to get oriented and it still sometimes gets off the kilter. I have noticed this since 10. 0.4
skelzer said:
Just happened today for the first time. No clouds or building, I was out in the open. Marker flipped 180° 3-4 times while I approached a stoplight... hard to know which way to turn.
Makes me think this might be related to the recent 10.0.6 update?
Click to expand...
Click to collapse
The first time I noticed this issue was November the 8th when I was driving north for 3 hours. It was obviously happening where it would do that marker flipping around. This last sunday i went on another trip and was still noticing the issue often. It even caused me problems when I was walking around downtown Kansas City trying to find a venue. I had to ask somebody to point me in the right direction because the thing couldn't decide where i needed to go. I have reached out to the oneplus support and i'm waiting for further instructions from them. ... here... ill copy paste the email.
Thank you for contacting OnePlus Customer Support.
We apologize for the inconvenience that this has caused you. As we understand your concern. Please do not worry, we will surely help you with the best possible ways available.
Kindly help us with the below details:
1. Did the issue start post update?
2. Which is the current OS version on the device?
3. Does the issue occur Randomly or Always?
We request you to follow the below troubleshooting steps so that it could fix your issue:
1. Go to Settings- Location- Mode, select High accuracy, switch GPS on.
2. Check the environment, test the GPS in an open and empty place, because GPS used indoors can be blocked.
3. Use different apps to check whether there is the same problem.
4. Disable or Uninstall Security apps as it may limit the authority of the GPS in some apps.
We would also request you to do a network reset on the device so the issue can be resolved:
Network Reset:
Settings>> Backup and Reset>> Network setting Reset>>Reset setting
To assist you will be our pleasure, help us to help you. Request you to reply within the next 5 days as after that the ticket will be auto-closed".
Regards,
Phillip Smith
OnePlus Customer Support
Click to expand...
Click to collapse
Problem with their instructions is i cant seem to find a way to turn the GPS mode to high accuracy as described. anybody know where it might be?
Thank you for connecting back to us.
I understand that you are not able to find the high accuracy settings on OnePlus 7T. Please do not worry, I request you to clear the device cache to fix this issue.
Please follow below steps to clear the cache:
Clear Cache -
- Power off your device.
- Press the power key + volume down for a few seconds.
- Select English.
- Tap on Wipe data and cache.
- Tap on Wipe Data and cache again.
- Tap on Yes to confirm data and cache wipe.
- Wait for the wipe process to complete.
- Reboot phone.
If you had any further questions please reply to us within the 5 days as after that the ticket will be auto-closed.
Click to expand...
Click to collapse
Will this just completely wipe my phone if i follow the instructions? I seriously don't want to do that especially if it might not even fix anything.
Krazy_Calvin said:
Will this just completely wipe my phone if i follow the instructions? I seriously don't want to do that especially if it might not even fix anything.
Click to expand...
Click to collapse
No, it will not wipe the phone unless you select that option to wipe data or factory reset.
Well i will tell it to just wipe the cache... i am pretty positive whoever was handling the support just gave me instructions to wipe the whole phone though. lol. im not doing that.
Edit:
Wow... so frustrating... When I tried to do those functions the thing asked for a password. It wasn't my pin or my normal password i use. I have no idea what it was asking for but it gave a forgot password option to reset the phone. I reset the phone.
Also... its that easy to reset this phone?
Ok... Well after resetting my phone completely booted up, installed the latest patches and now when I check the accuracy in the maps it checks out high. Hopefully it stays that way.
Krazy_Calvin said:
Ok... Well after resetting my phone completely booted up, installed the latest patches and now when I check the accuracy in the maps it checks out high. Hopefully it stays that way.
Click to expand...
Click to collapse
Did you lose root?
---------- Post added at 03:05 AM ---------- Previous post was at 03:04 AM ----------
Krazy_Calvin said:
Well i will tell it to just wipe the cache... i am pretty positive whoever was handling the support just gave me instructions to wipe the whole phone though. lol. im not doing that.
Edit:
Wow... so frustrating... When I tried to do those functions the thing asked for a password. It wasn't my pin or my normal password i use. I have no idea what it was asking for but it gave a forgot password option to reset the phone. I reset the phone.
Also... its that easy to reset this phone?
Click to expand...
Click to collapse
So, did you end up losing all your data?
I was never root in the first place. All my data is in the google cloud. I just had to go through the annoyance of setting up all my settings and icons since they didn't stick.
Well I know it's not 7T, but I had horrible GPS on the 6T and 7 Pro models both. Neither had ok accuracy, no matter what I did. It would lose GPS signal on street, in car, on foot. OnePlus is just super horrible at GPS, and I have no clue why. Like why it is not acknowledged and why they won't fix it.
My recommendation is to try a reboot and/or use Google Maps when this happens. I am a fan of Waze, I prefer it much over Maps (speed limits). But in Waze and any other 3rd party GPS app - it struggles to find me way more than Maps. That said, your GPS won't magically fix itself in Maps. It will be just a tiny teeny bit better. So like.. from super horrible bad it will go to christ this is a horrible gps. It may still help in a pinch.
GPS issue
h8Aramex said:
Well I know it's not 7T, but I had horrible GPS on the 6T and 7 Pro models both. Neither had ok accuracy, no matter what I did. It would lose GPS signal on street, in car, on foot. OnePlus is just super horrible at GPS, and I have no clue why. Like why it is not acknowledged and why they won't fix it.
My recommendation is to try a reboot and/or use Google Maps when this happens. I am a fan of Waze, I prefer it much over Maps (speed limits). But in Waze and any other 3rd party GPS app - it struggles to find me way more than Maps. That said, your GPS won't magically fix itself in Maps. It will be just a tiny teeny bit better. So like.. from super horrible bad it will go to christ this is a horrible gps. It may still help in a pinch.
Click to expand...
Click to collapse
..in setting, turn off :Google location accuracy - improve location accuracy , and wi-fi and bluetooth scanning. It works for me
(source: https://forums.oneplus.com/threads/gps-issue.1113746/page-2)
georgito said:
..in setting, turn off :Google location accuracy - improve location accuracy , and wi-fi and bluetooth scanning. It works for me
(source: https://forums.oneplus.com/threads/gps-issue.1113746/page-2)
Click to expand...
Click to collapse
Interesting, thank you, I will try that.
I mean in my testing, I actually put different phones next to each other and tested GPS Signal strength.
The 7 Pro basically has a much worse signal than any other phone I tested. It's dark orange/red. Every other phone is at least yellow.
Just install "GPS Status" from Play Store, put your phone besides whatever other phone and prepare to get shocked.
https://forum.xda-developers.com/attachment.php?attachmentid=4938075&stc=1&d=1580304335
https://forum.xda-developers.com/attachment.php?attachmentid=4938077&stc=1&d=1580304335
Hello,
Posting this in case others are still searching for a gps accuracy fix on the Oneplus 7t phone.
I may have found a workaround for the gps accuracy issues on the 7t. Fwiw, I'm using the Verizon version, on a HD1905, with the latest March update 10.0.0.HD65AA. I was experiencing all the same issues, and sadly the March update didn't seem to make any improvement. I've only had the phone for a few days, and was very disappointed w/ the gps performance. Tried everything including wiping the phone clean (I didn't realize the gps was wonky until I spent a couple days migrating everything over), and nothing worked -- it would immediately boot and have wildly wrong gps location, or the lock would seem to phase in an out. If it wasn't for the shelter in place order, I probably would have returned it.
After much trial and error, I found a workaround that seems to work. Even tested on our walk around today with Gaia and it correctly tracked our path.
1) put phone into airplane mode
2) reboot, and leave in airplane mode after reboot
3) run google maps, wait for lock, should be accurate
4) turn off airplane mode
5) test gps -- it should work better
If you reboot while normal networking is enabled, the gps would fail every time -- never accurate. But when networking is completely shutdown when the GPS radio is turned on, it seems to work as expected. Using the 'GPS test' app, my accuracy goes from 100m/ no lock, to approx. 3M 3d-lock, just sitting inside on my desk, and it maintains it. I'd say my old Pixel phone still has slightly better gps accuracy overall, but this is very usable now. And, I don't reboot very often -- phone is always charged, etc, so the workaround is doable for me. If I do need to reboot, just have to remember to use airplane mode first. Otherwise, seems to work as expected now.
Hope that helps someone.
beyondcrazy said:
Hello,
Posting this in case others are still searching for a gps accuracy fix on the Oneplus 7t phone.
I may have found a workaround for the gps accuracy issues on the 7t. Fwiw, I'm using the Verizon version, on a HD1905, with the latest March update 10.0.0.HD65AA. I was experiencing all the same issues, and sadly the March update didn't seem to make any improvement. I've only had the phone for a few days, and was very disappointed w/ the gps performance. Tried everything including wiping the phone clean (I didn't realize the gps was wonky until I spent a couple days migrating everything over), and nothing worked -- it would immediately boot and have wildly wrong gps location, or the lock would seem to phase in an out. If it wasn't for the shelter in place order, I probably would have returned it.
After much trial and error, I found a workaround that seems to work. Even tested on our walk around today with Gaia and it correctly tracked our path.
1) put phone into airplane mode
2) reboot, and leave in airplane mode after reboot
3) run google maps, wait for lock, should be accurate
4) turn off airplane mode
5) test gps -- it should work better
If you reboot while normal networking is enabled, the gps would fail every time -- never accurate. But when networking is completely shutdown when the GPS radio is turned on, it seems to work as expected. Using the 'GPS test' app, my accuracy goes from 100m/ no lock, to approx. 3M 3d-lock, just sitting inside on my desk, and it maintains it. I'd say my old Pixel phone still has slightly better gps accuracy overall, but this is very usable now. And, I don't reboot very often -- phone is always charged, etc, so the workaround is doable for me. If I do need to reboot, just have to remember to use airplane mode first. Otherwise, seems to work as expected now.
Hope that helps someone.
Click to expand...
Click to collapse
thanks for posting this. Wow. That is a lot of headache to run through. I will try that as well. As I absolutely can't stand the GPS on this phone.
I have also found a workaround, although it involves toggling the location settings on and off. IE toggling the Wi-Fi and Bluetooth scanning on and off. Generally this works for me, although sometimes I have to reboot the phone
Just recently over the last couple months, I have been having a problem with getting a good gps signal in programs such as Waze and Google maps. I have done all kinds of searches and many mention to go into settings and in location settings, turn on High Accuracy. That option is bo longer available and not sure if it was eliminated in Pie. I have been doing all the latest updates and believe I am current. The only thing I have been able to find is to go into settings, then Biometrics, and there I found location. The only choices under Improve Accuracy is to turn on Wifi scanning and Bluetooth scanning which I have done. There no longer is a choice of High Accuracy and the ability to turn GPS on or off like I had in previous phones and previous versions of Android. I have even tried turning on High Performance under Battery Power settings and turned off any choices to optimize battery or disable apps. I ended up downloading 2 different GPS apps from Store, GPS Status and GPS Fix/Optimizer. I will normally use Waze or Google maps through Android Auto. I can tell when there is a problem when the position indicator keeps bouncing all over the place in Waze and cant find exactly where I am. When that happens, I will check on GPS Status and it always shows that it is having a problem acquiring the satellite signals. I will then open up GPS Fix/Optimizer and on the home screen, there is a button that will say Service Off. I press it and it will then read Service On. Switching back to GPS Status will now show that it is starting to acquire multiple satellite signals. When I switch back to Waze, now it is able to show my exact location and begins to work properly.
This is driving me nuts. I never had this problem on any other of multiple different phones or Android versions. I can get GPS working but have to jump through all these hoops each time and it sucks. So what other steps can I do to be able to fire up Waze and have it find me right away?
It's not just an Android Auto thing, it happens with GPS in general. There have been many posts about it over on Reddit in the Note 8 Forum dating back to March. The best fix is to just toggle location whenever you notice that GPS isn't working.
The scary thing is not only has Samsung not even acknowledged there is an issue, newer phones are also starting to have the problem. Just saw people complaining about the same thing in a S20 forum. Just like our issues, they started after an update.
mikeyk101 said:
Just recently over the last couple months, I have been having a problem with getting a good gps signal in programs such as Waze and Google maps. I have done all kinds of searches and many mention to go into settings and in location settings, turn on High Accuracy. That option is bo longer available and not sure if it was eliminated in Pie. I have been doing all the latest updates and believe I am current. The only thing I have been able to find is to go into settings, then Biometrics, and there I found location. The only choices under Improve Accuracy is to turn on Wifi scanning and Bluetooth scanning which I have done. There no longer is a choice of High Accuracy and the ability to turn GPS on or off like I had in previous phones and previous versions of Android. I have even tried turning on High Performance under Battery Power settings and turned off any choices to optimize battery or disable apps. I ended up downloading 2 different GPS apps from Store, GPS Status and GPS Fix/Optimizer. I will normally use Waze or Google maps through Android Auto. I can tell when there is a problem when the position indicator keeps bouncing all over the place in Waze and cant find exactly where I am. When that happens, I will check on GPS Status and it always shows that it is having a problem acquiring the satellite signals. I will then open up GPS Fix/Optimizer and on the home screen, there is a button that will say Service Off. I press it and it will then read Service On. Switching back to GPS Status will now show that it is starting to acquire multiple satellite signals. When I switch back to Waze, now it is able to show my exact location and begins to work properly.
This is driving me nuts. I never had this problem on any other of multiple different phones or Android versions. I can get GPS working but have to jump through all these hoops each time and it sucks. So what other steps can I do to be able to fire up Waze and have it find me right away?
Click to expand...
Click to collapse
Did you ever find a fix for this problem ? I am dealing with this too and have been for a while. GPS when using as a phone is no issues at all but, once you connect Android Auto, it's a mess. Very hit or miss and even if I hit where it works, it will drift off and require me to unplug/re-plugin my Note 8..
I posted to a few other places on this issue, nothing has solidly fixed this. Otherwise my note 8 works fine, so I no reason right now to upgrade, till the phone I want drops a little in price.
Reddit post
https://www.reddit.com/r/AndroidAut...ps_on_waze_or_google_maps_gets_randomly_lost/
Android auto site..
https://support.google.com/androidauto/thread/45792804?hl=en
Samsung's site
https://us.community.samsung.com/t5...-GPS-randomly-on-Waze-and-Google/td-p/1332311
And even Ad central.. er...Android Central
https://forums.androidcentral.com/a...-gps-randomly-gets-lost-any-idea.html?mn_qa=1
Anyone else figure this problem out ?
I still havent found a fix. Here is another thread I started on the main Galaxy Note 8 that produced a lot more discussion but sadly, no fix yet.
https://forum.xda-developers.com/galaxy-note-8/help/recent-gps-problems-t4058849
For me at least, it seems like it may be an issue between Android Auto and my Chevrolet. Still not entirely convinced but folks over at Android Auto claim that there is a communication problem with Android Auto trying to communicate with the internal gps on my truck. Supposedly even though I dont have traditional on board navigation, there is still gps communications going on. I believe that with Chevy, it is the onstar system. Android Auto is programmed to utilize vehicle gps because it is supposed to be more accurate. Unfortunately, if that is the case, and there is constant communication error between the Note 8 and vehicle, the result is that the apps in AA like Waze and Google maps continually have location errors. I inquired why AA couldnt just allow users to utilize the phone GPS as an option and was again told that a vehicle gps would be way more accurate so that option isnt available. When unplugging usb from vehicle, it defaults to the phone GPS and begins working again almost immediately. So is the problem with AA programming or communication problems with my Chevy truck? Who knows. Sometimes they communicate just fine from the get go but other times, not so much. I just wish the problem could be fixed. I would be leaning towards AA programming as this does not just happen with Chevy vehicles but AA just passes the buck.
mikeyk101 said:
I still havent found a fix. Here is another thread I started on the main Galaxy Note 8 that produced a lot more discussion but sadly, no fix yet.
https://forum.xda-developers.com/galaxy-note-8/help/recent-gps-problems-t4058849
For me at least, it seems like it may be an issue between Android Auto and my Chevrolet. Still not entirely convinced but folks over at Android Auto claim that there is a communication problem with Android Auto trying to communicate with the internal gps on my truck. Supposedly even though I dont have traditional on board navigation, there is still gps communications going on. I believe that with Chevy, it is the onstar system. Android Auto is programmed to utilize vehicle gps because it is supposed to be more accurate. Unfortunately, if that is the case, and there is constant communication error between the Note 8 and vehicle, the result is that the apps in AA like Waze and Google maps continually have location errors. I inquired why AA couldnt just allow users to utilize the phone GPS as an option and was again told that a vehicle gps would be way more accurate so that option isnt available. When unplugging usb from vehicle, it defaults to the phone GPS and begins working again almost immediately. So is the problem with AA programming or communication problems with my Chevy truck? Who knows. Sometimes they communicate just fine from the get go but other times, not so much. I just wish the problem could be fixed. I would be leaning towards AA programming as this does not just happen with Chevy vehicles but AA just passes the buck.
Click to expand...
Click to collapse
Yep, saw that thread as well and the one on Android Auto's site, I even replied to it. Wishing there was a solid fix here but, no... I have a Lexus LS that I added on a 3rd party Android auto device on. I had this same issue when I had a 2019 Ford with Android Auto as a rental. I figured 6 months later (I just put AA in my car about 2 weeks ago) it would be resolved by now.
Not 100% sure it is the GPS car thing you were told, as other phones plug into Android auto and have a seamless experience if this was the case, all phones would have this issue. We are using the same software. So why is the Note 8 different ? Well, I hear this effects other Samsung phones but, none as bad as the Note 8. Newer Android 10 even Samsung phones do not report this issue, as far as I have heard.
Oh, well the quest goes on... If you find something, please drop me a line....and thanks !
"Me too" - Driving me crazy. Toggling Location services off and on sometimes helps, but not always. I'll be moving, and the map doesn't reflect any movement.
Sengfeng said:
"Me too" - Driving me crazy. Toggling Location services off and on sometimes helps, but not always. I'll be moving, and the map doesn't reflect any movement.
Click to expand...
Click to collapse
Toggling when driving is not a good idea, Normally unplugging and plugging back in works just as well. Funny for the last week, it was working fine (get lost when in a lot of trees and sometimes not recover but, on the highway it was perfect), till this morning and it was a mess.
There was an update for the Note 8 on Verizon a week ago, I need to double check all the power saving features and make sure they are fully disabled...
I had also started a thread on the Google Android Auto community back in May where the developers monitor posts. Just recently (about a week ago) it seems they are acknowledging that there may be a problem and posted they were going to send out emails to several that were affected by this. They gave directions on how to forward a bug report to them when the problem showed up. I was one that received the bug report email. I have since submitted 2 bug reports to them but have not received any kind of reply. Hopefully I hear back sometime soon and they are able to identify exactly what the problem is. If I do, I will post their response...
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.