Dirty Unicorns on LS980 - Sprint LG G2

Has anyone else gone with DU 9.7 on their LS980? Our variant seems to have more obstacles than others so I'd love to compare what I'm seeing vs what others have found.
The original DU thread is found here: http://forum.xda-developers.com/lg-g2/development/rom-dirty-unicorns-5-1-1-t3162408
So far I love this ROM, but here are some things I've found:
1. When the screen has been off for a while, the phone seems sluggish waking up. The screen comes on quick, but after swiping the lock it takes 2 seconds to show the pattern screen.
2. Initially when I was connecting with Sprints LTE and downloading a lot of data, the phone would crash. (Still testing)
3. Audio headphone jack is very loud and has static.
4. Dropped an AT&T sim into the phone to see if it would connect. It did, but data was edge. I didn't have the sim long, so I didn't get to really test it. I'd love to know how to get 3G working on AT&T/Cricket with this ROM.
5. When I'm done with a call and pull the phone away from my face the screen still stays off like the sensor isn't working. I have to push the power button to get the screen to come on.
BTW...if you are having GPS problems with your LS980, I followed the advice in the following link and now it works great:
https://www.reddit.com/r/lgg2/comments/2i12bn/troubleshooting_gps_issues_on_ls980_now_with_some/

i had DU running on my LS980. It worked great overall-biggest thing that worked well was the GPS. shows that the issue really is software related. However, I was forced to go back to stock for the following reasons. If you decide to do it, make a TWRP backup so you can restore back if desired. Best things I liked about it it was razor fast and ability to change screen DPI was cool.
Freedompop messaging did not work for me making phone calls. I could place a call maybe the 1st time after a bootup but every other dial attempt just did not work for me.
Occasionally would lose my APN setting for freedompop and go to Sprint;'s default. Didn;t cause my phone to stop working but didn;t want that to be a cause for issues
Battery drain was bad for me. Kind of mysterious since very little extra bloatware was running. YMMV but I got barely 12 hours of standby. On stock I get 2 days and not alot of drainage overnight. I can;t explain it.....

@tekweezle,
I get very good battery life with DU 9.7. As always I use Clean Master to block most apps from running in the background which always helps.
nobe1976 helped with a workaround for my very loud headphone issue. Use the sound settings in Kernel Aduitor to adjust as needed. The good stuff start at post #703 http://forum.xda-developers.com/lg-g2/development/rom-dirty-unicorns-5-1-1-t3162408/page71
I plan on dropping Sprint in Dec and going with Cricket. I've got some research to do on getting 3G working with their service on this phone.

For some reason I'm getting extra good battery life now. Check out the screen grab.

Ok...over the weekend I tried to install BlissPop to see what it was all about. I had continuous crashing and touch screen issues. I went back to my DU backup and the touchscreen issues continued but not as bad as within BP. I'm going to start from scratch with ZVE and do directly to DU. Hopefully all the issue will be taken care of.

Ok...I'm leaving Sprint no matter what and I can't seem to get a stable GSM rom working with Cricket on my ls980.
I love my G2, but I'm going to have to buy a new phone.
I've narrowed it to the following, but I'm having a hard time with which one to pick.
Nexus 5 = DU is officially supported, oldest of my options: $199 USD
Nexus 6 = DU is officially supported, could be too big: $319 USD
LG Flex 2 = no DU support, no CWM/TWRP yet, newest options: $250 USD
Thanks for any input!

Related

HTC Touch Pro 2 & Standby of Death SOD

I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2 where the resolution was to get a new SIM.
Obviously this only solves the problem when the crash is because of the sim and/or settings which impact the sim. To rule out a software cause its best to start with a hard reset.
had this problem once: I switched on the camera, and then left the device on the table for a long time - so it went to standby.
I could not wake it up by the power button after 20 minutes, but as an incoming call came, it was ringing with a black display, and I could answer the call with my BT headset. screen was still pure black
finally I pushed the reset button and since then everything is fine - I still feel this was connected to the camera.
terta said:
had this problem once: I switched on the camera, and then left the device on the table for a long time - so it went to standby.
I could not wake it up by the power button after 20 minutes, but as an incoming call came, it was ringing with a black display, and I could answer the call with my BT headset. screen was still pure black
finally I pushed the reset button and since then everything is fine - I still feel this was connected to the camera.
Click to expand...
Click to collapse
Yeah if it only happened the once then that was probably the case, if you have the problem on a regular basis and you know its nothing to do with the camera (becuase you never loaded it) then you have the problem I am describing.
I have exactly the same problem has Terta.
I'm 100% sur that it's the camera that make this bug I have tried all my weekend to reproduce the bug a lot of time and it was always the camera...
Hope someone can fix this bug cause now I can't take any photo without soft-reseting my phone. Very, very, very annoying...
I messed around with the sound app SRS WOW HD for a while to get it work on TP2, with this installed, mine did exactly the same thing.
Sometimes it happened straight away (first sleep), other times it happened a day or so later.
Uninstalled, it did not happen again.
(Not the SIM or Camera for me)
Go figure!
Cheers
Jabberoo
Yes I guess there are many reasons for the Standby of Death, if you have ruled out all software causes such as the camera or installed apps then have a think about the SIM and/or the settings that impact the SIM.
Its the last thing most people will think about. It worked for me and got rid of a random SOD problem 2-3 times a week which coinceded with being in weak 3G areas (where the phone might switch bands automatically) although that never occured to me at the time.
You see I haven't installed other applications nor do I load up the camera and leave it running so I couldn't figure out what was causing it, it just happened randomly not connected with anything particular that I was doing.
i hope there is some kind of magical solution for this because i just got my Sprint TP2 today and I have this issue everytime my phone goes into standby. Pushing the power button wont bring it out but every once in a while opening the keyboard does. I have to continually reset my new phone just to use it
PS; beyond this annoyance, I love it!
coppertop24 said:
i hope there is some kind of magical solution for this because i just got my Sprint TP2 today and I have this issue everytime my phone goes into standby. Pushing the power button wont bring it out but every once in a while opening the keyboard does. I have to continually reset my new phone just to use it
PS; beyond this annoyance, I love it!
Click to expand...
Click to collapse
Try taking out the SIM card and see if it still happens everytime the phone goes into standby...
For the past few days I have been restarting my phone thru the soft reset. I think this is a windows issue...it has happened to me even without having the camera app running, and yes I checked the task manager. Hopefully this will be fixed when windows mobile 6.5 comes out, since Im getting frustrated with this phone...I have the phone for about a month now....grrr Stand by of Death!!!
coykiam said:
For the past few days I have been restarting my phone thru the soft reset. I think this is a windows issue...it has happened to me even without having the camera app running, and yes I checked the task manager. Hopefully this will be fixed when windows mobile 6.5 comes out, since Im getting frustrated with this phone...I have the phone for about a month now....grrr Stand by of Death!!!
Click to expand...
Click to collapse
so its not just mine then? this is ridiculous
Right, i had got seriously fed up with the standby of death happending, so i decided to contact HTC Europe directly.
They went over the usual 'factory reset' and 'update' solutions before coming to the conclusion that either there is a loose connection/faulty screen or there is some confiliction between drivers of the pre-installed software.
Because all HTC phones have 2 years warrenty as standard they have asked me to send if off so they can invistigate the problem and send me a replacement.
So if anybody is in the same boat as me a suggest you contact HTC and arrange a fix/replace.
Hope this helps.
nlel said:
Yeah if it only happened the once then that was probably the case, if you have the problem on a regular basis and you know its nothing to do with the camera (becuase you never loaded it) then you have the problem I am describing.
Click to expand...
Click to collapse
Add me to the list, seems to happen when I am charging my phone and it hits 100%
This phone reminds me of all my previous Sony Ericsson phones....very unstable OS' ... Makes me regret of getting this one and should've gotten an iPhone...but then again I'm pretty sure iPhone's have issues that apple fanboys aren't admitting. The reason that made me not get an iphone is because of ATT's ridiculous plan pricing...Its crazy!!!
if you are on sprints network, take out the sim card. This has fixed the issue for me. Used to get SOD a few times a day but opening the keyboard and then pressing the power button used to get me out of it. This was really annoying, and i read that it may be issues with the sim card. Took that out a week ago and havent had a SOD yet
jabberoo said:
I messed around with the sound app SRS WOW HD for a while to get it work on TP2, with this installed, mine did exactly the same thing.
Sometimes it happened straight away (first sleep), other times it happened a day or so later.
Uninstalled, it did not happen again.
(Not the SIM or Camera for me)
Go figure!
Cheers
Jabberoo
Click to expand...
Click to collapse
Jabberoo I can verify that this was caused by the SRS WOW HD program on my touch pro 2 as well. AS SOON as I uninstalled this application, restarted, everything was fine again.
I don't know if this will help anybody but if your phone suffers from SOD and you have TMO put it in airplane mode and see if it still does it.
I did that and it never went into SOD so that lead me to believe that the radio was the culprit. before that I tried everything listed. I don't have the 3G Plan so the 3.45.25.14 (T-Mobile) radio is the only one that worked for me.
I have the same problem.. just have installed spb mobile shell with mskip ultimate. I try to unistall all
I have a question: if I choose the 3G only option (WCDMA + UTMS 2100 in Europe) and the signal strength is low there will not be an automatic switch between 3G and 2G am I right? ...and i'm offline then
jabberoo said:
I messed around with the sound app SRS WOW HD for a while to get it work on TP2, with this installed, mine did exactly the same thing.
Sometimes it happened straight away (first sleep), other times it happened a day or so later.
Uninstalled, it did not happen again.
(Not the SIM or Camera for me)
Go figure!
Cheers
Jabberoo
Click to expand...
Click to collapse
sanjsrik said:
Jabberoo I can verify that this was caused by the SRS WOW HD program on my touch pro 2 as well. AS SOON as I uninstalled this application, restarted, everything was fine again.
Click to expand...
Click to collapse
Confirming this....
I had this issue for a while now...I tried hard resets, ROM flashes etc. It all works fine and was stable until I flash Sps Wow HD (I just realized this). Yesterday I flashed the latest HTC released sense ROM and right now after installing all the softwares I had the SOD again. Fortunately I saw the 2 posts and thought I will give it a try...and guess what?
I uninstalled the Srs Wow HD and phone is back to normal...no issues till now...will report later if I see any.
I am going to tmobile to get the SIM changed anyways hoping that it will fix another issue I am having. Every day I have to turn the airplane mode ON and OFF at least twice to get my data connection back. Mostly after a call and sometimes in random the phone is unable to reconnect to the data, it gives me an error that the epc.tmobile didnt respond or something like that. If any of you know how to fix this issue...plz help
I have been Experiencing this so called "SOD". HTC touch pro 2 sprint. On the 6.5.5 Build 23569 i had MAJOR sod issues. Energyrom , mighty , titanium , you name it. Ive Task 29 and reflashed them all multiple times. Still SOD was there... But i may have found a temp cure for me atleast. This is what i did....
First , i used task29 , next i reflashed the stock 6.1 rom, check for SOD... still had it... i task 29 again. Installed titanium edition , without sense. SOD was cured, phone worked fine, tryed to install sense 2.1, failed, SOD was back. Soo...
Then i task29 again, then repeated task29 a second time at the boot screen.... then i flashed Energyrom GTX themed 21907 build june 27th......Once it was flashed unplugged my USB plug and plugged it into the usb wall plug i have . Installed LUMOS, light sensor still was inactive and no response, could not brighten and still nothing... Installed G-light right after lumos without uninstalling lumos.... Still plugged into the AC wall USB plug....let it sit. Still nothing, couldnt adjust or brighten..... So i task 29 AGAIN... then flashed 21907 build GTX themed again... once flashed, unplugged it & back into wall charger... Installed lumos.... SUDDENLY!!! the sensor worked, and was accepting light AGAIN! ...
So i ran the LUMOS wizard, followed instructions and my phone was SOD FREE!! Let it sit over night, was fine....I wanted to see now if i could overwrite / flash over GTX themed with DiNiK glass cause i liked it better... so i DID NOT USE task29 this time, just reflashed over GTX themed one With DiNiK glass... same build 21907 and followed all my same steps, with wall plug, installed lumos, did the wizard,.... WALAaa.... works still like a charm. Have been using and testing it for 5 days, SOD is gone as far as i know.... ALSO in options, under setting / system / power / batt... i turned off the option to charge it when plugged into PC....Not sure if it helps or not. But Something i did is doing the trick. Seems between the backlight, and something to do with my 2.0 usb cord thats messing it up.
Seems to be cured... Still not sure exactly what fixed my phone. But between all that, IMO i believe installing lumos and glight triggered something also i think not letting it charge thru the PC, and only using a wall plug for charging has something to do with it....Either way . now its back to normal working just great... ONLY running LUMOS cab, and all the games i want. Energyrom Build 21907 DiNiK Glass Themed june 27th.... HOPE this helps!!! Have a wonderful DAY!

Several issues and annoyances with Tilt2

My wife and I each purchased Tilt2's earlier this week. We both come from Windows Mobile 6.1 phones and are generally happy with WinMo products and comfortable with tweaking them.
We're both having some trouble with the Tilt2 and I'm hoping that someone here might be able to help.
1) Bluetooth sound quality - we each use Bluetooth headsets and have noticed lots of crackling unless the phone is turned with the back facing the headset. This didn't happen with our previous phones (same headsets) unless we got 15-20 feet away from the phone.
2) Dropped calls - I've noticed a ton of dropped calls when I'm talking on the phone and driving along my normal work commute. There are 1-2 holes along the route where my previous phone would drop, but this one drops 5-6 times. I found these radio updates in the ROM forum. Would that help?
3) General performance - The phone seems a little bit laggy and slow to react. Nothing like what we saw in demo videos on sites like wmexperts.com. My wife even reports that hers has completely locked up on her before. And I've noticed a severe lag waiting for the phone to come back after I've flipped the keyboard out. I assume that installing a custom ROM would help with this as it's helped on previous phones we've owned. However, there isn't a 100% working AT&T ROM to revert to yet (only one that appears to work is missing radio and bootsplash at this point) in case the custom ROM doesn't perform better, so I'm a little leary of doing it. Should I be worried? Or will the custom ROMs here help get rid of the lagginess.
4) Switching to landscape mode - My wife told me that her phone isn't always switching to landscape mode. She doesn't have any apps installed yet so I'm assuming it's in all of the default screens. Should everything work in landscape mode?
Thanks in advance!
e_dogg said:
My wife and I each purchased Tilt2's earlier this week. We both come from Windows Mobile 6.1 phones and are generally happy with WinMo products and comfortable with tweaking them.
We're both having some trouble with the Tilt2 and I'm hoping that someone here might be able to help.
1) Bluetooth sound quality - we each use Bluetooth headsets and have noticed lots of crackling unless the phone is turned with the back facing the headset. This didn't happen with our previous phones (same headsets) unless we got 15-20 feet away from the phone.
2) Dropped calls - I've noticed a ton of dropped calls when I'm talking on the phone and driving along my normal work commute. There are 1-2 holes along the route where my previous phone would drop, but this one drops 5-6 times. I found these radio updates in the ROM forum. Would that help?
3) General performance - The phone seems a little bit laggy and slow to react. Nothing like what we saw in demo videos on sites like wmexperts.com. My wife even reports that hers has completely locked up on her before. And I've noticed a severe lag waiting for the phone to come back after I've flipped the keyboard out. I assume that installing a custom ROM would help with this as it's helped on previous phones we've owned. However, there isn't a 100% working AT&T ROM to revert to yet (only one that appears to work is missing radio and bootsplash at this point) in case the custom ROM doesn't perform better, so I'm a little leary of doing it. Should I be worried? Or will the custom ROMs here help get rid of the lagginess.
4) Switching to landscape mode - My wife told me that her phone isn't always switching to landscape mode. She doesn't have any apps installed yet so I'm assuming it's in all of the default screens. Should everything work in landscape mode?
Thanks in advance!
Click to expand...
Click to collapse
As for #4: Not all programs have a landscape mode natively.
jlczl said:
As for #4: Not all programs have a landscape mode natively.
Click to expand...
Click to collapse
Thanks. I figured that she might be using an app that doesn't work in landscape since I haven't come across it yet.
Also, regarding #2, I should have mentioned that I have 4.48.25.20 as my current radio.
1) I use Jabra 2nd gen and mine is working great. A little crackling sound but nothing major.
2) Depend on the area you live and coverage, you might want to try different radio. I have stock radio and mine is working great. Better than my fuze was actually. I can get 1 or more bar than Fuze and call quality is super clear. No drop calls yet while I had like 2-3 drop calls with my fuze.
3) I am still running on stock rom and yes indeed it's slow and sluggish. I have to reset the phone physically sometimes. I am not too happy about moving the battery cover just to reset as well. With custom rom, the phone will be snappy since some people are running custom rom with their Tilt2 already. I am in the same boat as you. Waiting for the complete stock rom dump. Until then.
4) Not all the landscape work as you have already found out.
I use a BlueAnt and my BT reception is good.
I thought mine was slow at first but as I tweaked it a bit, turning off alerts and pop ups, it SEEMS to be more of what I expected.
Haven't had a dropped call issue.
But, I am thinking that I will flash the ROM when something comes along.
Thanks for the replies.
FWIW, my wife uses a Jawbone 2 and the crackling is noticable on both ends of the call. I use a first-gen Jawbone and have nocticed the crackling as well. It seems that it works better when the phone is on the same side of my body as the headset. I did not notice this crackling on my Dash and Blackjack 2 nor her Dash.
I think the dropped calls problem is definitely area related. My wife is currently out of town and it hasn't dropped her calls at all that I know of. And when I'm at home, it's no problem. It's just that on my regular commute, it drops 5-6 times where my previous Dash and Blackjack 2 only dropped once or twice occasionally. I've only made my commute once since I got the Tilt2, so maybe there were some coincidental network issues. That said, call quality has been very good.
I just turned off the new SMS notifications. I've also removed a couple of tabs that I know I'm never going to use (stocks, AT&T, and music) at that seems to have made things a little snappier too.
HAH! Not more than 1-2 minutes after I posted my last message (from my laptop), I went to use the internet connection on my Tilt2 and it locked up. A message appeared asking if I wanted to send error details to MS and then my phone turned off.
Another thing I've noticed is that Opera takes a *really* long time to switch from landscape to portrait. And it seems to be significantly slower than Opera Mini was on my Dash and Blackjack 2. Maybe because Opera Mini is Java-based on those platforms?
My wife is now reporting that her Tilt2 won't unlock unless she slides open the keyboard. Her Exchange connection requires the phone to automatically lock and require a PIN entry. I suggested tapping the power button but that doesn't wake it up, either.
Any suggestions? I'm thinking she might have a bum unit since mine isn't having nearly the trouble hers is.
As far as the lockups, I think there was a thread somewhere about that. Mine doesn't actually lock up but it hangs horribly. Give it 5min or so and it figures itself out, usually involves opening the keyboard at the same time it is launching something, sms in my case.
Suggestion? Hard reset hers and if it continues swap it out.
SoapDoctor said:
As far as the lockups, I think there was a thread somewhere about that. Mine doesn't actually lock up but it hangs horribly. Give it 5min or so and it figures itself out, usually involves opening the keyboard at the same time it is launching something, sms in my case.
Suggestion? Hard reset hers and if it continues swap it out.
Click to expand...
Click to collapse
Thanks for the tip. Unfortunately, she's out of town right now so I actually haven't seen the things she's complaining about first-hand (except for a couple of things that have happened on mine too).
I'll send her instructions for a hard reset and see if she's adventurous enough to try it on her own. The AT&T store near where she's at is exceptionally good - they really know Windows Mobile there and were a big help in getting the phone initially set up. So, worst case, she can go there and have them do it.
e_dogg said:
Thanks for the tip. Unfortunately, she's out of town right now so I actually haven't seen the things she's complaining about first-hand (except for a couple of things that have happened on mine too).
I'll send her instructions for a hard reset and see if she's adventurous enough to try it on her own. The AT&T store near where she's at is exceptionally good - they really know Windows Mobile there and were a big help in getting the phone initially set up. So, worst case, she can go there and have them do it.
Click to expand...
Click to collapse
Don't run to fast with my advice, I'm a complete noob but hard reset would be the first thing I would try. It is a microsoft product after all and I'm pretty dman lazy to run to the store first.
FWIW- I have a Jawbone 2 and have cracking in the audio. Had it with my Fuze also and have always wondered if it was the headset or phone. I don't think I could keep my fuze in the holster because of the crackling.
I have some slight performance issues, but it's not to bad. Seems mostly relating to minimizing a program and starting a new one.
I have a strange problem with the TF3D photo tab. It's slow to get the image clear. I select an image and then try to scroll through them. It hangs on one, then flips it's orientation (I haven't moved the phone though). Anyone else have issues with the photo tab?
e_dogg said:
My wife and I each purchased Tilt2's earlier this week. We both come from Windows Mobile 6.1 phones and are generally happy with WinMo products and comfortable with tweaking them.
We're both having some trouble with the Tilt2 and I'm hoping that someone here might be able to help.
3) General performance - The phone seems a little bit laggy and slow to react. Nothing like what we saw in demo videos on sites like wmexperts.com. My wife even reports that hers has completely locked up on her before. And I've noticed a severe lag waiting for the phone to come back after I've flipped the keyboard out. I assume that installing a custom ROM would help with this as it's helped on previous phones we've owned. However, there isn't a 100% working AT&T ROM to revert to yet (only one that appears to work is missing radio and bootsplash at this point) in case the custom ROM doesn't perform better, so I'm a little leary of doing it. Should I be worried? Or will the custom ROMs here help get rid of the lagginess.
4) Switching to landscape mode - My wife told me that her phone isn't always switching to landscape mode. She doesn't have any apps installed yet so I'm assuming it's in all of the default screens. Should everything work in landscape mode?
Thanks in advance!
Click to expand...
Click to collapse
#3 I am running NRG ROM Photon date 10/17 and it is insane on my tilt 2. No radio change either. Stupid fast, eye candy, and never a dropped call or sluggish issues. Link below (5k plus thread, really read the first page to see the versions and Faq's)
http://forum.xda-developers.com/showthread.php?t=553506
I'd like to add that I'm also having some issues with sound and response time.
My phone starts fresh with about 65% of resources used up. After regular phone/contacts usage for an hour I'm at around 70% and after Opera, the phone is done. I can browse or use file explorer or music but there goes the multi-tasking.
I haven't flashed a ROM yet. I just wanted to see what AT&T did with this thing 1st.
One more thing, why did they switch the FN and Shift keys? My brain is having a hard time getting used to it, especially when the shortcuts that require the Fn key are on the bottom row.
I can't really help you out too much, but I haven't been experiencing many of these problems at all, and I'm still on the stock rom, just cleaned it up a bit. Spend some time on the forums and you'll find some good quick hacks to try before you try a new rom.
superrrguy said:
I'd like to add that I'm also having some issues with sound and response time.
My phone starts fresh with about 65% of resources used up. After regular phone/contacts usage for an hour I'm at around 70% and after Opera, the phone is done. I can browse or use file explorer or music but there goes the multi-tasking.
I haven't flashed a ROM yet. I just wanted to see what AT&T did with this thing 1st.
One more thing, why did they switch the FN and Shift keys? My brain is having a hard time getting used to it, especially when the shortcuts that require the Fn key are on the bottom row.
Click to expand...
Click to collapse
Touch FLO 3D uses up quite a bit of RAM. I unloaded it and restarted, and my phone is down from 65% to 49%. Unfortunately, I'm kind of liking Touch FLO 3D
Linear2202 said:
FWIW- I have a Jawbone 2 and have cracking in the audio. Had it with my Fuze also and have always wondered if it was the headset or phone. I don't think I could keep my fuze in the holster because of the crackling.
I have some slight performance issues, but it's not to bad. Seems mostly relating to minimizing a program and starting a new one.
I have a strange problem with the TF3D photo tab. It's slow to get the image clear. I select an image and then try to scroll through them. It hangs on one, then flips it's orientation (I haven't moved the phone though). Anyone else have issues with the photo tab?
Click to expand...
Click to collapse
Good info about your Jawbone issues. I have an old Plantronics headset that I'm not really using anymore. Maybe I'll give that one a try to see if it's just that Jawbones don't like these new versions of HTC phones (it worked great on her Dash).
As for the photos tab, it seems to work ok. Though the first "flip" through the pictures seems to be slower than subsequent flips.
I found that hiding tabs I won't be using like the "AT&T" tab seems to help speed things up. I think I have 3 or 4 hidden.
amurch said:
#3 I am running NRG ROM Photon date 10/17 and it is insane on my tilt 2. No radio change either. Stupid fast, eye candy, and never a dropped call or sluggish issues. Link below (5k plus thread, really read the first page to see the versions and Faq's)
http://forum.xda-developers.com/showthread.php?t=553506
Click to expand...
Click to collapse
Thanks - good to hear of your sucess with the NRG ROM. That's the one I'm planning on trying since I really like the 6.5.1 changes.
redpoint73 said:
Touch FLO 3D uses up quite a bit of RAM. I unloaded it and restarted, and my phone is down from 65% to 49%. Unfortunately, I'm kind of liking Touch FLO 3D
Click to expand...
Click to collapse
Yeah, Touch FLO 3D sure is purty. And, now that I have the tabs sorted and hidden the way I like, it's very easy to use.
Just an update...the Energy ROM seems to have cured the dropped calls. With the stock AT&T ROM, calls dropped about 5-6 times on my regular commute. With the Energy ROM, not a single one!
Something that has happened to me now a few times...I get a call on the phone. Caller ID and picture show up fine. Screen turns off..later i turn the screen on and the phone number is not accurate any longer and the picture is gone..
Anyone had this happen to them?
Linear2202 said:
Something that has happened to me now a few times...I get a call on the phone. Caller ID and picture show up fine. Screen turns off..later i turn the screen on and the phone number is not accurate any longer and the picture is gone..
Anyone had this happen to them?
Click to expand...
Click to collapse
Yep - happened quite often with the stock AT&T ROM. I don't recall seeing it after switching to the Energy ROM.

Build 13.0-20160207 "Unfortunately, Bluetooth Share has stopped."

Is this a known issue with the D851 and CM13? I keep getting a force close over and over and it won't stop unless I reboot the phone witch in turn disables Bluetooth. I can't seem to find anything about it other than one post with no answers. Here is a pic of the build causing the problem. Any way to fix this?
Same issue here. Seems to be caused by a commit to lg g3 update init in the cm changelog.
Interesting. I decided to drop down to 13.0-20160206 and Bluetooth works, however "Unfortunately, Bluetooth Share has stopped." message has only shown up once so far. Bluetooth sound in "Star Trek Timelines" is slowed down, like the bit rate is low or something. Have not tried anything else yet.
SovereignKnight said:
Interesting. I decided to drop down to 13.0-20160206 and Bluetooth works, however "Unfortunately, Bluetooth Share has stopped." message has only shown up once so far. Bluetooth sound in "Star Trek Timelines" is slowed down, like the bit rate is low or something. Have not tried anything else yet.
Click to expand...
Click to collapse
Looking at the changelog for the next potential nightly, it seems like it will be fixed. They added back part of that file.
See http://review.cyanogenmod.org/#/c/132118/
Anyone flash 20160212? I not only have the bluetooth issues, but mobile data regularly drops out, requiring an Airplane Mode cycle to regain.
UPDATE: re-flashed, GPS is working fine.
I dirty flashed 20160212 and now my GPS doesn't work, but the Bluetooth messages have stopped on my D851.
mdphoenix said:
Anyone flash 20160212? I not only have the bluetooth issues, but mobile data regularly drops out, requiring an Airplane Mode cycle to regain.
Click to expand...
Click to collapse
CM maintainers Forget our Device is BCMD unlike their devices.. so they think if it works for them, it must work for all.......
Only the D851/D856/F400/LS990 use BCMD while the others use that wcn crap.
as for data. Leave that to CM to mess that up to............. I had to go and fix my Device tree for PAC that CM totally screwed up.
your data issue is more a apn-cong.xml issue.. if you want a fix to that.. go read the last few pages on my Pac thread. and I listed a fix for data issues..............
Nice. Thanks!
..
Had this issues on an earlier build fixed it by reflashing
MuF123 said:
What was the fix?
Click to expand...
Click to collapse
A long hard road followed all of this. Lessons were learned, and in the end, nothing really gained. Except a working phone.
The entire issue started when I tried to flash SuperSU. Not knowing that CM didn't use SU. That began the decline. I ended up using the LG flash tool to put it back to an older stock version. It worked for a while, then I rebooted and it went to hell. Deader than dead. I shipped it off to a guy in Texas I found on Ebay to JTAG it. Came back just fine. Except I think whatever I did to it before then jacked up the charging. The phone wouldn't charge at all. Sitting on a charger for two days gave it about 5%. Come to find out, it was still under warranty. I shipped it to LG. They fixed it, returned it, and now it's on stock Lollipop, and I have to say - I quite like LG's interface. I've turned off a few things, installed Nova, etc. But at this point I have no reason to root or go custom. I did with my VZ phones because they were such nazis about everything. But I've got free tethering with Tmo. The phone works well. So, I'm sticking with what I have for now.

POLL: How is Oreo working for you now that it's released?

Just curious to see how people are finding the new Oreo for the S7/S7 edge. For me, it's great. Definitely I do see an improvement in performance. Sluggishness is definitely reduced from what I was experiencing in Nougat. Battery life appears to be the same, if not a bit better, but it's hard to tell.
Only issue I've seen is some apps I have are not Oreo ready (such as the previous Power Amp beta, but there is an Alpha out right now that works but is very incomplete in things such as Playlists).
I have noticed that some apps no longer give notifications at all (mainly games with in-app notifications). Not sure if it's because they're not up-to-snuff with Oreo, but the important apps (such as Messenger+) do work just fine in regards to notifications.
Overall, I'm very pleased with this release which in all honesty will probably be the last upgrade for this phone. I still love my S7 and hope it lasts a long time for me.
This update is fantastic as far as I'm concerned. My phone seems to be more responsive and doesn't lag as much as it did on Nougat. Battery life has been better since the update. Somehow my fingerprint scan to unlock is 1,000 times better. Was always having issue with it before this update. I am also getting slightly better reception. I get slightly better reception in my office area where I previously had little to no reception. I like how some of the items in the pull down notification shade are compacted like your Wi-Fi connection, so they don't take up as much room. Feels like I have a new phone, and I also hope this last major update we will get will help my S7 last for a long time.
I agree, much snappier. I not having to keep putting down apps and restarting to keep it that way either. It makes my s7 a keeper for another year at least. None of the new features really apply to the way I use my device, so no difference there for me.
Sent from my SM-G930V using Tapatalk
Adaptive icons suck. Had to download an icon pack to return all of the Google apps to "normal". Bright white circles in my dark theme....
Other than that, I'll have to mess around more before I see if there's been much change. Haven't really noticed more responsiveness.
one word. HORRIBLE! Battery life has literally been cut by 40-60% with the exact same use as before even with power saver on, weird lag issues when I'm trying to multitask, incoming calls wont take precedence over whatever else is currently on screen, screen wont light up on incoming calls when idle, VZW caller id no longer works on unknown calls, fingerprint unlock no longer works just keeps saying "wipe home key and try again", while talking on the phone if the other person gets another call i now hear it ringing on my side and this is just after 2 days...... worst update ever to what was a flawlessly performing device. Wondering if I need to do a factory reset and start fresh
zachjf said:
one word. HORRIBLE! Battery life has literally been cut by 40-60% with the exact same use as before even with power saver on, weird lag issues when I'm trying to multitask, incoming calls wont take precedence over whatever else is currently on screen, screen wont light up on incoming calls when idle, VZW caller id no longer works on unknown calls, fingerprint unlock no longer works just keeps saying "wipe home key and try again", while talking on the phone if the other person gets another call i now hear it ringing on my side and this is just after 2 days...... worst update ever to what was a flawlessly performing device. Wondering if I need to do a factory reset and start fresh
Click to expand...
Click to collapse
A factory reset would be a good place to start, especially after a major update.
I did the full reset with the Odin package and it is very smooth with better battery life, even with battery saver off.
tylerhole said:
A factory reset would be a good place to start, especially after a major update.
Click to expand...
Click to collapse
it took 5 tries but I was finally able to get it to wipe/reset, kept giving me a "system update failed, no recovery package found" error. Resetting it seems to have cured the battery, heat and lag issues and is running smoothly again, only issue I still have is a slight delay in waking the phone on incoming calls but I can live with that
zachjf said:
it took 5 tries but I was finally able to get it to wipe/reset, kept giving me a "system update failed, no recovery package found" error. Resetting it seems to have cured the battery, heat and lag issues and is running smoothly again, only issue I still have is a slight delay in waking the phone on incoming calls but I can live with that
Click to expand...
Click to collapse
Glad to hear it worked. not sure what you can do about the lag when waking, maybe it'll work itself out in time.
Sent from my SM-G935V using Tapatalk
zachjf said:
it took 5 tries but I was finally able to get it to wipe/reset, kept giving me a "system update failed, no recovery package found" error. Resetting it seems to have cured the battery, heat and lag issues and is running smoothly again, only issue I still have is a slight delay in waking the phone on incoming calls but I can live with that
Click to expand...
Click to collapse
Glad it's working now. Were you rooted and/or modified any of the default system apps? That can cause issues as well. I haven't rooted the S7 ever since I first got it over 1.5 years ago because I never had the need to. It's always been pretty good and stable except Nougat. It started out fine, but as time went on it got progressively worse. I didn't have to do a factory reset and so far, Oreo has been a dream come true.
People's mileage will vary depending on their use and any mods they may have done to their phones. Also, remember that not all apps are written to Oreo specs. Whenever there is a major upgrade, certain APIs and other programming techniques that might have worked (or been allowed to happen) under older versions of Android may now be no longer allowed. That can result in apps misbehaving under Oreo and thereby causing the symptoms you see (battery drain, sluggishness, etc). That's why it's always best to see if any apps you have installed have been updated to work correctly with Oreo.
Another option would have been to uninstall apps one by one to see if things improved after they were removed. At that point, you have found your culprit.
I usually do an update of all apps before doing an upgrade because a lot of devs will push out updates to make their apps conform to the next Android version's standards. That has usually allowed me to avoid any issues. Problem is, not all apps are kept up-to-date because the developer has moved on to other things, etc. But, if any apps that haven't been updated in a long time are still on after I upgrade, I usually would remove those first and that usually cured my ills. But, it is rare that I have the problem because I usually don't keep old, stale apps around. I'm a stickler for that for some reason.
In any case, glad you got it working!
iBolski said:
Just curious to see how people are finding the new Oreo for the S7/S7 edge. For me, it's great. Definitely I do see an improvement in performance. Sluggishness is definitely reduced from what I was experiencing in Nougat. Battery life appears to be the same, if not a bit better, but it's hard to tell.
Only issue I've seen is some apps I have are not Oreo ready (such as the previous Power Amp beta, but there is an Alpha out right now that works but is very incomplete in things such as Playlists).
I have noticed that some apps no longer give notifications at all (mainly games with in-app notifications). Not sure if it's because they're not up-to-snuff with Oreo, but the important apps (such as Messenger+) do work just fine in regards to notifications.
Overall, I'm very pleased with this release which in all honesty will probably be the last upgrade for this phone. I still love my S7 and hope it lasts a long time for me.
Click to expand...
Click to collapse
I had no problem at all updating. Went real smooth. My battery has better life and the heat/battery/lag/slow boot are so much betterer. The only things I miss is dolby and viper for sound quality being non rooted. I listen to a lot of music and now have to use an old rooted S5 for my music. Thank you for the release. I've only had it installed for a day and if I notice any issues I will post
samg1958 said:
I had no problem at all updating. Went real smooth. My battery has better life and the heat/battery/lag/slow boot are so much betterer. The only things I miss is dolby and viper for sound quality being non rooted. I listen to a lot of music and now have to use an old rooted S5 for my music. Thank you for the release. I've only had it installed for a day and if I notice any issues I will post
Click to expand...
Click to collapse
Hey mate, did you know that root for Oreo was released recently?
https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616
Bless jkruse, been using his roms / tools since my One+ 1
Awful, but to be fair, the phone has been horrible for several months now. Did the update to Oreo first, but phone was slow. Decided to do a factory data reset and start fresh with Oreo. It was a little bit better, but not great. Then I installed the g930vvrs4crg2 update and it got worse. Last try before smashing this phone is to Odin back to fresh Oreo, then install the latest update. Hopefully that helps.
woodardhsd said:
Awful, but to be fair, the phone has been horrible for several months now. Did the update to Oreo first, but phone was slow. Decided to do a factory data reset and start fresh with Oreo. It was a little bit better, but not great. Then I installed the g930vvrs4crg2 update and it got worse. Last try before smashing this phone is to Odin back to fresh Oreo, then install the latest update. Hopefully that helps.
Click to expand...
Click to collapse
The Verizon firmware is awful. Flashing the unlocked firmware (930U) is miles better. Very little bloat (most can be disabled or uninstalled)

Question A13, another "Am I the only one?" Thread!

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.

Categories

Resources