Question General 12.1 issues, am I the only one? - Google Pixel 6 Pro

Edit: I changed the title of this thread to general 12.1 issues bc I've been noticing more stuff. The list so far is:
1. Vibration strength for notifications is ridiculously weak now
2. Lock screen as detailed below in this post
3. Heating up quite a bit listening to music. Am on wifi, using pixel buds A series
4. Battery drain. Been off charger since about 8:40am 100%, listening to music for just over an hour, now at 80%.
................................................................................
Another weird bug I noticed with 12.1 is that whenever my screen locks, it briefly shows "No notifications" in the middle of the screen before showing the fingerprint icon. This only seems to happen when I disabled the huge 2 line clock.
Just like with the weak notification vibrate strength thread I started, I'm asking if anyone else is seeing this too or if it's just me. Also, anyone on 13 DP2, do you see this?
Trying to work out if I should bite the bullet and do a factory reset or if these are just known things bc if I don't have to reset, I won't.
James

How do you change the huge clock?

I'm speculating a little, but since you say "This only seems to happen when I disabled the huge 2 line clock", I would suggest that a factory reset won't help.
Note, I'm not on the March update yet.

96carboard said:
How do you change the huge clock?
Click to expand...
Click to collapse
Go to settings>display>lock screen>double line clock toggle

roirraW edor ehT said:
I'm speculating a little, but since you say "This only seems to happen when I disabled the huge 2 line clock", I would suggest that a factory reset won't help.
Note, I'm not on the March update yet.
Click to expand...
Click to collapse
This is exactly why I'm asking haha. However, I think a factory reset is getting more and more plausible because now, I am listen to music at work as I usually do and my phone is getting real hot as well as battery draining quick. Unreal that google holds back this specific update to ensure no major bugs and this happens. I had no issues with the December update they actually pulled, no issues with Jan, and only a couple little dumb issues with Feb. Battery, vibration, heat, etc are all major issues. The lock screen thing, not so much but if others aren't having the issue, then I shouldn't be also. I am going to change the title of this thread to general 12.1 issues bc I'm getting off topic from the lock screen question.
James

It's true. The battery is worse than it was. Notification vibration is generally a nightmare. My phone is constantly on silent, so it's important for me to have a strong vibration.By the way, we've added a new fingerprint unlock animation.

jrg67 said:
1. Vibration strength for notifications is ridiculously weak now
Click to expand...
Click to collapse
I am one of those who rely on vibration at work, and I can absolutely confirm that its much weaker after the update that I took mid morning.

dacapho said:
I am one of those who rely on vibration at work, and I can absolutely confirm that its much weaker after the update that I took mid morning.
Click to expand...
Click to collapse
Definitely submit feedback on this through the settings. This is absolutely unacceptable that they totally killed vibration strength on just the 6 series, either by design or a bug.

Can't repeat the screen lock screen error, but this vibration thing is wild.

somethingsomethingroot said:
Can't repeat the screen lock screen error, but this vibration thing is wild.
Click to expand...
Click to collapse
Send feedback! Hopefully if a ton of people complain, Google will actually acknowledge this. Only other thing I can think of is the pixel community and a bug report

I thought I was going crazy because of the vibration. It is noticably weaker. I haven't seen any significant battery drain though. Sorry. Compared to some bugs, this isn't too bad.

I also noticed a much weaker vibration strength after the update. I did a search in Settings for vibration and got a "vibration & haptics" settings. All sliders were on the left. Once I pulled them back to the middle, vibration strength seems to be normal again (as far as I remember).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jrg67 said:
This is exactly why I'm asking haha. However, I think a factory reset is getting more and more plausible because now, I am listen to music at work as I usually do and my phone is getting real hot as well as battery draining quick. Unreal that google holds back this specific update to ensure no major bugs and this happens. I had no issues with the December update they actually pulled, no issues with Jan, and only a couple little dumb issues with Feb. Battery, vibration, heat, etc are all major issues. The lock screen thing, not so much but if others aren't having the issue, then I shouldn't be also. I am going to change the title of this thread to general 12.1 issues bc I'm getting off topic from the lock screen question.
James
Click to expand...
Click to collapse
I never had an issue, even with the December update that was pulled.
I'm beginning to wonder about different production runs of this device.
I missed out on the opening day, nothing but 500 errors trying to order the phone.
I got my 256G jobbie on the next restock and received it in December.
(I originally was going for the 512G but I didn't want to wait until sometime in 2022.)
I couldn't order until November 9, and received my device in th second week of December.
So I hear and read about complaints, and I had none.
Even today, with my phone is on my desk, vibration is just fine.
It gets my attention and I didn't notice a thing.

bleez99 said:
I never had an issue, even with the December update that was pulled.
I'm beginning to wonder about different production runs of this device.
I missed out on the opening day, nothing but 500 errors trying to order the phone.
I got my 256G jobbie on the next restock and received it in December.
(I originally was going for the 512G but I didn't want to wait until sometime in 2022.)
I couldn't order until November 9, and received my device in th second week of December.
So I hear and read about complaints, and I had none.
Even today, with my phone is on my desk, vibration is just fine.
It gets my attention and I didn't notice a thing.
Click to expand...
Click to collapse
I never had a major issue until this 12.1 update as well. This is so weird. I was able to order my phone on announcement day and received it on launch day in October. Phone has literally been as close to perfect as it could be (again just a few minor annoyances but nothing major).
This is making the case for a wipe even stronger. Ugh. Has anyone that has experienced these issues perform a wipe and had it fix these things, especially the weak vibration?
When you say your vibration is fine, I am assuming you updated to 12.1 and the vibration is the same as it was on the Feb 12.0 release and earlier?

jrg67 said:
I never had a major issue until this 12.1 update as well. This is so weird. I was able to order my phone on announcement day and received it on launch day in October. Phone has literally been as close to perfect as it could be (again just a few minor annoyances but nothing major).
This is making the case for a wipe even stronger. Ugh. Has anyone that has experienced these issues perform a wipe and had it fix these things, especially the weak vibration?
When you say your vibration is fine, I am assuming you updated to 12.1 and the vibration is the same as it was on the Feb 12.0 release and earlier?
Click to expand...
Click to collapse
Yes. I haven't noticed a difference, it's still just as strong as it was before March.

stbxxl said:
I also noticed a much weaker vibration strength after the update. I did a search in Settings for vibration and got a "vibration & haptics" settings. All sliders were on the left. Once I pulled them back to the middle, vibration strength seems to be normal again (as far as I remember).
View attachment 5568471
Click to expand...
Click to collapse
Mine are all maxed out. I even put them down to off, restarted the phone both soft and hard (holding the power button what seems like an hour to perform) and moved them all back up to max. No difference.

Vibration hasn't changed for me, still wants to shake the house down.
Not got any of the other issues you have listed either fortunately, not that it helps you though

jrg67 said:
Send feedback! Hopefully if a ton of people complain, Google will actually acknowledge this. Only other thing I can think of is the pixel community and a bug report
Click to expand...
Click to collapse
Been reading that this has been going on since the beta, which makes it sound like a choice.

somethingsomethingroot said:
Been reading that this has been going on since the beta, which makes it sound like a choice.
Click to expand...
Click to collapse
Yes but there is some hope, some say their vibration hasn't changed. Anyone factory reset with weak vibration and the reset fixed it?

I haven't really noticed any change in my vibration strength, for whatever that's worth.

Related

[Q] Battery bug

So my least favorite part about running custom roms on this phone is the "freeze at 45%, reboot to 6%" bug. Does anyone know if this is ever going to be fixed? Or if it is even a real"bug"? Do other phones experience this or just Galaxy S? I don't remember it being an issue when I ran stock, though honestly it was probably only for like a week.
Like this.
Result 1
Result 4​
Been running custom ROMs since December 2010 and never got a freeze ran all the way down to 3%.
Sent from my SPH-D700 using xda premium
RandomKing said:
Like this.
Result 1
Result 4​
Click to expand...
Click to collapse
I think you meant to post this meme..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Because this question does not retain to the Atrix 4G (though I am curious as to whether the flashable in that thread would work on cm9 for our phones.) and the other thread you posted is just more lames like you thinking this problem has been solved for the Epic. Now the whole point of a forum is to be able to ask questions in Q+A because others might know the answer already.. but I HAVE googled this (yes even with the site:xda-developers.com filter) and all I can find as far as the epic goes is people telling others to plug their charger in while its off to calibrate it. That doesn't help if you don't have a charger and it doesn't answer my question about whether or not it will be truly fixed for the epic and not "handy manned".. so basically unless you can post a thread that has a flashable software fix or a thread containing above said fix for this then please don't bother and keep your smart ass responses to yourself.
Edit: gushy apology later in thread.
Sent From My Sprint Galaxy Nexus via XDA Premium
kennyglass123 said:
Been running custom ROMs since December 2010 and never got a freeze ran all the way down to 3%.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Your lucky... I've had it run down to 2-3%. It sucks when your nowhere near a charger.
never had a problem running my battery all the way down to 1% with the stock 1500mah and the et4g 1800mah batteries. I do remember a couple of the GB leaks that would occasionally shutdown before they hit 5% but lets be honest, that was expected of buggy leaks. Since moving to CM7/CM9/AOKP zero battery issues. Sure, some days i barely make it through the day off the charger, but most days i'm good to go. I do on occasion see the "reboot your phone with 40% battery and boots back up at 15%" "bug" but i don't reboot my phone that often like that, normally i'll shut it down and don't have that issue.
pvtjoker42 said:
never had a problem running my battery all the way down to 1% with the stock 1500mah and the et4g 1800mah batteries. I do remember a couple of the GB leaks that would occasionally shutdown before they hit 5% but lets be honest, that was expected of buggy leaks. Since moving to CM7/CM9/AOKP zero battery issues. Sure, some days i barely make it through the day off the charger, but most days i'm good to go. I do on occasion see the "reboot your phone with 40% battery and boots back up at 15%" "bug" but i don't reboot my phone that often like that, normally i'll shut it down and don't have that issue.
Click to expand...
Click to collapse
Yeah I've never had it just die on me because it was reporting juice and was actually dead.. and I'll have to test and see if it does it when I do a complete shutdown cause I almost never shut it down. Almost always involuntary reboots for me that come back up with anywhere from 2%-20% .
kennyglass123 said:
Been running custom ROMs since December 2010 and never got a freeze ran all the way down to 3%.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I've ran mine down to literally 0% it shows an X for battery and it was still on and running but i soon shut it off so i could charge it haha
OP, are you undervolting? If so that is the probable cause of you freezes when your battery gets under 50%. It is not a glass full of energy. Percentage is a direct correlation to voltage. 100% is 4.2V, I believe 0% is 3.7V. As you get below 50% that undervolting will drop even further. As for the percentage fifference it is usually a false reading based on the heat of the battery lowering the voltage reading during the intense drain of rebooting. Usually taking the battery out for a few minutes to cool will bring it back to the 40% or so.
Sent from my PantechP4100 using xda premium
schnowdapowda said:
Because this question does not pertain[fixed for you] to the Atrix 4G (though I am curious as to whether the flashable in that thread would work on cm9 for our phones.) and the other thread you posted is just more lames like you thinking this problem has been solved for the Epic. Now the whole point of a forum is to be able to ask questions in Q+A because others might know the answer already.. but I HAVE googled this (yes even with the site:xda-developers.com filter) and all I can find as far as the epic goes is people telling others to plug their charger in while its off to calibrate it. That doesn't help if you don't have a charger and it doesn't answer my question about whether or not it will be truly fixed for the epic and not "handy manned".. so basically unless you can post a thread that has a flashable software fix or a thread containing above said fix for this then please don't bother and keep your smart ass responses to yourself.
Click to expand...
Click to collapse
First off, I may have misunderstood your question, but I did provide a response, regardless. Responding as an ungrateful tool is unnecessary.
And as to not "pertaining" to the Atrix, you DID ask if other phones were affected.
But to the point, I mistook your question to be simply asking why the phone misreads the battery level upon reboot as mentioned:
pvtjoker42 said:
[...]"reboot your phone with 40% battery and boots back up at 15%" "bug"[...]
Click to expand...
Click to collapse
I see now that you quite literally mean that your phone is failing to report below a certain level until it dies. To answer your question, I've never seen this, but it would help if you would provide basic information.
1. Rom Tested
2. Undervolting/Overclocking settings
3. Any additional changes you've made after installing a rom
This doesn't sound like a typical battery reporting error others have experienced. Are you undervolting?
P.S. Grow a sense of humor. You'll live longer.
RandomKing said:
First off, I may have misunderstood your question, but I did provide a response, regardless. Responding as an ungrateful tool is unnecessary.
And as to not "pertaining" to the Atrix, you DID ask if other phones were affected.
But to the point, I mistook your question to be simply asking why the phone misreads the battery level upon reboot as mentioned:
I see now that you quite literally mean that your phone is failing to report below a certain level until it dies. To answer your question, I've never seen this, but it would help if you would provide basic information.
1. Rom Tested
2. Undervolting/Overclocking settings
3. Any additional changes you've made after installing a rom
This doesn't sound like a typical battery reporting error others have experienced. Are you undervolting?
P.S. Grow a sense of humor. You'll live longer.
Click to expand...
Click to collapse
My bad your right. I never work mornings and am in a horrible mood because I happen to be working with my *****y manager (who never works mornings either) and we are clashing hardcore. Sorry I jumped down your throat. To answer ya'lls question I am on cm9 beta 3, but have always had random reboots once in awhile so honestly while its an experimental build I don't think that's the cause of my reboots I'm on the latest Shadow kernel. No undervolting. But anyway the purpose of this thread isn't really to find out why I'm getting reboots (though I appreciate you guys trying to help me find that out too) but rather to find out why my battery drains so much afterwards. So yes you were correct in your original assumtion.
Edit: my excellent meme reference is proof of my sense of humor.
schnowdapowda said:
Edit: my excellent meme reference is proof of my sense of humor.
Click to expand...
Click to collapse
Fair enough ;-).
All I can say is that with the full battery circle mod, rebooting often shows a really low percentage. If you leave it, it usually slowly rises back to where it should be... not sure that's your problem.
-Sent from my Random Epic.
I understand what the OP is saying, and I too have this problem. Mostly when I go to cwm and return. My battery sometimes goes from a 60 or even 70 to a 5-19%. Its not all that's bad of a problem because I know that I have more than that in my battery. But it makes the phone scary because you never know when it'll blow up on you lol.
Sent from my SPH-D700 using XDA App
lilajrestnom said:
it makes the phone scary because you never know when it'll blow up on you lol.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Exactly. and today I did a little experiment. I drained to 50% percent and did a manual reboot. I did like kenny and random suggested and let it cool down before I rebooted and while it was better.. it was still not correct... I rebooted to around 25%. Now the atrix folks in that forum apparently have a flashable software fix for this that works. Does anyone wanna take that apart and see if they can work for us? Sorry this just seems so fixable I'm honestly surprised that with our kickin dev community nobody's worked on it.
schnowdapowda said:
Exactly. and today I did a little experiment. I drained to 50% percent and did a manual reboot. I did like kenny and random suggested and let it cool down before I rebooted and while it was better.. it was still not correct... I rebooted to around 25%. Now the atrix folks in that forum apparently have a flashable software fix for this that works. Does anyone wanna take that apart and see if they can work for us? Sorry this just seems so fixable I'm honestly surprised that with our kickin dev community nobody's worked on it.
Click to expand...
Click to collapse
Accidentally hit thanks
Sent from my GT-I9300 using Tapatalk 2
I had the same bug when I got my phone. I switched to the epic 4g touch battery and haven't had that issue since. "knock on wood"
Purponic said:
I had the same bug when I got my phone. I switched to the epic 4g touch battery and haven't had that issue since. "knock on wood"
Click to expand...
Click to collapse
Funnily enough that you mention this, I'm not sure that I've ever had a battery misread on my extended batteries. Not %100, as I don't use them as often, but it's a thought.
RandomKing said:
Funnily enough that you mention this, I'm not sure that I've ever had a battery misread on my extended batteries. Not %100, as I don't use them as often, but it's a thought.
Click to expand...
Click to collapse
I need to convince sprint to give me one. Last time they were not being cooperative. I shall look into it. Thanks for the responses guys.
I have had issues with my old extended battery on multiple roms not reading correctly. no matter what i did on both foryo and gb so far have had good luck with the 1800. i have also had issues of rebooting on with my extended.

Deep sleep

I am running stock att Kk rooted. My phone deep sleeps like a baby but when I get on my phone I can watch the battery drain. When I look at the battery graph under battery I can see sleep straight line across then when I get on the phone it goes straight down almost. I could be on it for 20min and it will go down like 8%
I was wondering if it could just be my battery cause I am having problems on all roms. Plus I have Flashed this phone about 30 times and I have had it for over a year
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Forgive the wordiness. I have a typing problem LOL)
I have an E980 too and was using the E980 stock ATT rom and also had issues.
Basically, the phone will work fine for a couple of hours after a reboot, but then all of a sudden, the phone would wake up (exit deep sleep; not screen turn on) and never sleep again.
Whenever this would happen I noticed a number of odd things happening (check to see if these are happening with you too!):
1) In battery usage, Android OS would suddenly consume 50-99% battery!! This is after hours of running the phone too. Usually, Android OS consumes 3-10% battery.
2) In Better Battery Stats, I had a lot of Wlan wakelocks. I use wifi a lot too, but these wakelocks would last for hours as soon as the phone stopped sleeping, whether wifi was connected or not.
3) In Better Battery Stats, there was a process called dhd_dpc that would run for the entire length of time since the phone was booted up
4) Phone would run warm with the screen off. Sometimes, it would get HOT. When you use the phone, it gets REALLY HOT.
5) According to Better Battery Stat's CPU usage history, once the wake occurs, the cpu will remain at 1.7GHz, even with phone asleep. Some roms I tried would have it scale down to 384MHz, but still, phone wouldn't enter Deep Sleep.
I tried everything to fix the issues and finally ended up flashing the E988 Hong Kong (I think) ROM and ALL my problems went away. The ROM works, but isn't designed for USA users. Yes, there's English, etc, but things like the Quick Remote app are meant for Chinese (Again, I think) users. It doesn't have USA cable company set top boxes like Verizon, etc.
Anyway, after having issues every single day since the E980 update, but lasting a full day on the E988 rom problem free (It's now been 2 full days and no issues still!!!!!), I realized that there was a problem greater than "User Error." I called AT&T up, dealt with their troubleshooting bullcrap (factory reset doesn't fix everything! I mean, I did it 4 times this week and the problem kept coming back with no apps installed!!! I didn't tell them this, but I also reflashed the ATT rom 3x too!!!!), and then they simply took a bug report and asked me to contact LG. I stumped them.
So then I called LG and after explaining all my symptoms and again dealing with me having to answer "yes" to all the girl's "Have you done this....?" questions, she put me on hold for a moment. She came back and told me that many issues have been reported by AT&T Optimus G Pro users (E980) and their software development team is already working on a new firmware version for our phone.
So in summary, the issue is due to bugs in the E980 firmware, but not in the other G Pro firmwares. According to LG customer support, they are already working on fixing the problems, but the girl didn't give me an ETA. Once LG finishes the fix, AT&T will have to review it and bloat the crap out of too, so it may take anywhere from a week to a few months before we get the fixed firmware.
Until then, you have two choices:
1) Live with it and pray that the next firmware comes sooner rather than later. I mean, they better be rushing this update!!!!!
2) Install the E988 stock firmware for now and use it until the next firmware comes out. Again, it isn't exactly the same as the E980 version, but it works and your phone won't be sick anymore.
spexwood said:
(Forgive the wordiness. I have a typing problem LOL)
I have an E980 too and was using the E980 stock ATT rom and also had issues.
Basically, the phone will work fine for a couple of hours after a reboot, but then all of a sudden, the phone would wake up (exit deep sleep; not screen turn on) and never sleep again.
Whenever this would happen I noticed a number of odd things happening (check to see if these are happening with you too!):
1) In battery usage, Android OS would suddenly consume 50-99% battery!! This is after hours of running the phone too. Usually, Android OS consumes 3-10% battery.
2) In Better Battery Stats, I had a lot of Wlan wakelocks. I use wifi a lot too, but these wakelocks would last for hours as soon as the phone stopped sleeping, whether wifi was connected or not.
3) In Better Battery Stats, there was a process called dhd_dpc that would run for the entire length of time since the phone was booted up
4) Phone would run warm with the screen off. Sometimes, it would get HOT. When you use the phone, it gets REALLY HOT.
5) According to Better Battery Stat's CPU usage history, once the wake occurs, the cpu will remain at 1.7GHz, even with phone asleep. Some roms I tried would have it scale down to 384MHz, but still, phone wouldn't enter Deep Sleep.
I tried everything to fix the issues and finally ended up flashing the E988 Hong Kong (I think) ROM and ALL my problems went away. The ROM works, but isn't designed for USA users. Yes, there's English, etc, but things like the Quick Remote app are meant for Chinese (Again, I think) users. It doesn't have USA cable company set top boxes like Verizon, etc.
Anyway, after having issues every single day since the E980 update, but lasting a full day on the E988 rom problem free (It's now been 2 full days and no issues still!!!!!), I realized that there was a problem greater than "User Error." I called AT&T up, dealt with their troubleshooting bullcrap (factory reset doesn't fix everything! I mean, I did it 4 times this week and the problem kept coming back with no apps installed!!! I didn't tell them this, but I also reflashed the ATT rom 3x too!!!!), and then they simply took a bug report and asked me to contact LG. I stumped them.
So then I called LG and after explaining all my symptoms and again dealing with me having to answer "yes" to all the girl's "Have you done this....?" questions, she put me on hold for a moment. She came back and told me that many issues have been reported by AT&T Optimus G Pro users (E980) and their software development team is already working on a new firmware version for our phone.
So in summary, the issue is due to bugs in the E980 firmware, but not in the other G Pro firmwares. According to LG customer support, they are already working on fixing the problems, but the girl didn't give me an ETA. Once LG finishes the fix, AT&T will have to review it and bloat the crap out of too, so it may take anywhere from a week to a few months before we get the fixed firmware.
Until then, you have two choices:
1) Live with it and pray that the next firmware comes sooner rather than later. I mean, they better be rushing this update!!!!!
2) Install the E988 stock firmware for now and use it until the next firmware comes out. Again, it isn't exactly the same as the E980 version, but it works and your phone won't be sick anymore.
Click to expand...
Click to collapse
id be shocked if we got anymore updates from lg.
fix-this! said:
id be shocked if we got anymore updates from lg.
Click to expand...
Click to collapse
This came from LG itself. Yeah, it was the customer service, but it was LG too. When the customer service tells you this kind of thing, it's usually true since it says it on their troubleshooting computer prompt.
Plus this isn't an update just in the sake of updating (like going from Jelly Bean to Kitkat), but an update to fix their pretty serious mistakes. They'd be extremely stupid to leave the firmware as it is now since it's currently broken. The KK update broke not only the AT&T OGP, but also every LG phone sold by a US mobile carrier. This includes the AT&T G2 and Verizon G2 as well.
EDIT: Actually, I was wrong. The G2 already received updates to fix issues. If they get updates to fix broken software, I'm sure we will too.
If they left the update as-is, they'd risk pissing off any current customers and driving away any future ones. In fact, they'd risk losing their entire US market. So I'm certain they'll release a "fix" update soon. I know LG has a bad update track record, but as far as I know, the firmwares they leave on their phones at least work. This is different. Nothing works correctly, and they would want to fix it.
EDIT: BTW, if you're using the E988, then yeah, any further updates may not happen. That firmware at least works.

LG G3 Severe annoyances

Hi all, this is my first post here, just thought I would share my experiences with the LG G3 (D855)
...probably the worst phone I have ever owned, so far I have had the Nexus one, Nexus S, Galaxy Nexus, Nexus 4 and a Nexus 5. My nexus 5 got destroyed at work, so took this as an opportunity to upgrade, but didn't want the Nexus 6 due to its size.
Now, where to start with the G3...
Signal- it is unbelievably bad, going from the Nexus where signal was nearly full in my room to barely getting any now. It is impossible to make calls or browse the net with the phone unless connected to the WiFi, I could download on H+ at about 1.2 mB a second, where as the G3 will barely refresh Facebook. My phone gets used at work quite a bit, but the signal isn't the strongest- however, all phones worked there to make call, apart from this one
Keyboard- Who the hell designs a keyboard without the comma on the front of it without having to go into a menu? This is where you tell me to install another one, but seriously?
Battery- yes I can understand it is a big screen etc, but for 3000 mAh it a atrocious.
Airplane mode- yes I know what it does, why the hell does it tell me every time I select it.
McAfee- we have a play store, I am not a chump and don't download from unknown sources, give the option to remove it.
Vibrate- yes it is harsh, but I work in a noisy environment, I need a strong vibrate function, however, one thing I DO NOT NEED is for it to vibrate in my ear when someone texts/whatsapps me during a call. This makes hearing the other person impossible, they can even hear it on the other end of the phone. I see no way of dulling the vibrate but only when in a call?
-Camera lag
-OS lag (Severe)
Yes, they have wowed their customers with a qhd display, but seriously, they need to start spending money on where it matters like antenna research. After a quick Google, it turns out to be a huge problem with this phone. Not just mine personally.
I am returning this phone after 18 hours of having it. Sorry LG, but they have lost me as a customer.
Dave
Looking for your previous phones I still think this "lag" is a placebo.
Came from a GNex and I must say that LG G3 does NOT lags.
Thank you for your judgment on how I percieve lag, my last phone was a Nexus 5 with CM, it did NOT have lag. This phone does.
UPDATE
Ok, after doing some more reading up, I decided to give the phone a bit more of a chance. I was headed on a 60 mile drive with my brother to see my family this Christmas. Before I left, I gave it a factory reset just to make sure I started with a clean slate.
Anyway headed on my way, 85% battery, I sent a friend a whatsapp message that would sit there ready to send and then go when I got signal. 40 miles traveled, checking very often here and there and it still hadn't sent. The battery had dropped to 25% in this time. Rather than waste any more time or battery in the hope that it would eventually get signal, I put airplane mode on. Guess what, I know what airplane mode does, because it told me AGAIN.
Now, I know this journey well, I know where I get signal and where I don't. All previous phones would have worked numerous places where the G3 didn't.
Oddly, instead of getting signal in some of the places around home where it should definately get it, the phone just constantly displayed roaming and wouldn't allow data. This happens with the Three network from time to time, but always happens in certain places where the network isnt available and allows voice calls only, not at home where there IS reception.
UPDATE
Just discovered that the stock charger cannot supply enough current to use the phone at the same time as charging. This phone is just brilliant...
DavidVanstone said:
Hi all, this is my first post here, just thought I would share my experiences with the LG G3 (D855)
Keyboard- Who the hell designs a keyboard without the comma on the front of it without having to go into a menu? This is where you tell me to install another one, but seriously?
-OS lag (Severe)
Dave
Click to expand...
Click to collapse
I understand you are about to return it already, this is more for people who is experiencing your issues.
The 2 issues above can be solved:
-Keyboard: it is configurable. Settings-> Language and input-> Lg Keyboard-> Keyboard height and layout-> Bottom row keys.
-OS lag: I got the phone 2 days ago and I was quite pissed off about the touch panel lag. The issue was the Touch zoom in my case. Go to Settings-> General-> Accessibility and disable Touch zoom.
DavidVanstone said:
UPDATE
Just discovered that the stock charger cannot supply enough current to use the phone at the same time as charging. This phone is just brilliant...
Click to expand...
Click to collapse
I am not sure what do you mean here. I used the phone for a couple of hours yesterday from 0% battery to ~30% while charging.
I hope this helps.
R.
Ok thank you, installed the google keyboard for now, used to it so feel at hone
I can live with all the issues (as I would most probably ROM it if I kept it anyway) but cannot abide the very very poor signal and the charging. It is currently on charge and has dropped 2% in the time I have written this. Screen brightness is on its lowest.
Have raised an RMA, just waiting to hear back. It is such a shame, it has its good points, love the screen, volume isn't as bad as most make out. Just a lot of other issues (mainly software) that seriously need to be addressed.
Did i just read you complaining about LAG comparing the LG OS with a nexus 5 that was on ****ing CYANOGEN?!
Well just install CYANOGEN on your G3 and be done with it....
Pacote-san said:
Did i just read you complaining about LAG comparing the LG OS with a nexus 5 that was on ****ing CYANOGEN?!
Well just install CYANOGEN on your G3 and be done with it....
Click to expand...
Click to collapse
And that will cure my hardware signal issues will it? I think not.
UPDATE
Tried three different chargers tonight, none of which make any difference to its inability to be charging while being used. It just keeps slowly running out.
Yeah I just upgraded from a Nokia Lumia 1020 today, and I have to admit...I am unimpressed. This thing is, on paper, WAY more powerful, so why the hell is it so. goddamn. LAGGY?
The lag, I can live with, as said, if I was keeping it I woukd probably ROM it anyway.
The thing is there are a lot of issues that need to be addressed, and with us all being techy types we could sort most of the issues with some modding, but here is my question, what does the average end user do with the problems? Accept them? Talk to LG and get told that the phone should vibrate like that when getting a notification during a call? Get told that the signal issues are because of the carrier. Get told that the reason their batteriy is going flat is because of apps they have installed? When after all this it is a combination of bad software and hardware that lets this phone down, no one else's fault.
UPDATE
Battery full notification, during writing this, every time I paused for a few seconds the phone vibrated, left a notification and bleeped to tell me the battery was full- this gets highly ***king annoying after a while, can this be turned off?!
Oh, here is the graph of the battery during my drive yesterday that I explained about. The drop is when the phone was looking for signal duringn the journey.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can see at the -5 and -3 hour mark where I put the phone on charge, a small spike in the graph, then immediately while being used, the level continued to drop with it still plugged in.
Yeah, the average user is pretty much ****ed. Thing is, there is NO excuse for it. If Microsoft, the former king of bloat, can make a smooth, fast, stable operating system that flies even on low end hardware, why can't Google make it fly on high end hardware? Why can't LG?
I will keep experimenting with Roms, but right now it's very likely I'll return this and go back to a Windows phone.
Sent from my LG-D850 using XDA Free mobile app
jasongw said:
Yeah, the average user is pretty much ****ed. Thing is, there is NO excuse for it. If Microsoft, the former king of bloat, can make a smooth, fast, stable operating system that flies even on low end hardware, why can't Google make it fly on high end hardware? Why can't LG?
I will keep experimenting with Roms, but right now it's very likely I'll return this and go back to a Windows phone.
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
It is such a shame, the phone does have some good bits going for it, but I am definately returning mine, the RMA has been raised with Ebuyer, just waiting to hear back.
I would have rommed it, but seeing as it's going back I couldn't be doing with the hassle of doing it and putting it back to stock again. Also, not being able to utilise the 4k and other camera features in aosp. Maybe someone can sort that, but either way, a phone not being able to get signal is a big problem for me and for some reason this issue seems to be getting more and more common nowadays (why is this?).
A quick question, which smartphones ACTUALLY have good signal? Once this one has gone, I'll be looking for another phone.
I just bought my G3 Monday, switched from an iPhone 6. The stock rom was slow.
Today rooted and installed Candy5. This phone is a beast. I haven't had one thing today phase this.
You can't compare CM to stock.
Works very well paired the Lg w110 watch.
Also this phone has much much better coverage then my iPhone and has the same that my Note 2 had.
Sent from my LG-D851 using XDA Free mobile app

Phone is now starting to exhibit glitches/problems

So I've had my XL2 for almost a month - original was RMA'd due to poor quality display at the beginning of the month. Anyways, everything has been great up to about the last 3-4 days. In that time I've noticed the following:
1. Phone would not stay on LTE. Only HSPA+ despite 3 other people(who were with me) with the same carrier all having LTE service all day. I restarted my phone 2 times. Toggled airplane mode several time. It only grabbed LTE for a few minutes then reverted back to HSPA+ when I would turn off cellular.
2. Android Auto. My vehicle detects the phone, in-car application launches, but either there is no sound from any song or when I hit play, song is automatically paused everytime. I have to unplug/plug phone for it to all start working. This doesn't happen everytime, but it's done this about a half dozen or so times now.
3. Last but by the far the most annoying and worst. Randomly, when I'm interacting with the Google keyboard or Swiftkey, the phone just starts to spaz out. Random apps open, incorrect text being entered(for example, I type "m" and instead "z" and 3 commas get entered in instead, and just total loss of control on the phone(can't keep anything open or incorrect actions happen).
So I'm the point where either I go for a factory reset(I hate doing this) or I contact support and see about getting an RMA.
FYI: I'm on the November update.
Went through 2 really blue displays to get what I thought was a keeper yesterday, my 3rd device. But now today I noticed the screen flashes bright white when going into always on display. Quality control must be non existent between Google & LG.
It's just unbelievable to me that a $1000 device is so poorly made or passed off as ready to be sold. I've been sticking up for Google during most of the screen blue shift fiasco, but after this last string of incidents, I'm losing faith completely. This is especially apparent when I see that my wife's iPhone X has had nothing to this magnitude.
I've been having major, major problems with SwiftKey myself, to the point where I no longer even want to use this phone until the situation is resolved.
Everything was fine, even on the beta, and then suddenly about a week or so ago - as you mention - SwiftKey just starts going nuts. Incorrect predictions, mistaken input, slow/lag, etc.
I wonder if it's something with the November Security Patch Update or SwiftKey's cloud network or what.
TokyoGuy said:
I've been having major, major problems with SwiftKey myself, to the point where I no longer even want to use this phone until the situation is resolved.
Everything was fine, even on the beta, and then suddenly about a week or so ago - as you mention - SwiftKey just starts going nuts. Incorrect predictions, mistaken input, slow/lag, etc.
I wonder if it's something with the November Security Patch Update or SwiftKey's cloud network or what.
Click to expand...
Click to collapse
Im using an older version of swiftkey without a hiccup
onishchuk4 said:
So I've had my XL2 for almost a month - original was RMA'd due to poor quality display at the beginning of the month. Anyways, everything has been great up to about the last 3-4 days. In that time I've noticed the following:
1. Phone would not stay on LTE. Only HSPA+ despite 3 other people(who were with me) with the same carrier all having LTE service all day. I restarted my phone 2 times. Toggled airplane mode several time. It only grabbed LTE for a few minutes then reverted back to HSPA+ when I would turn off cellular.
2. Android Auto. My vehicle detects the phone, in-car application launches, but either there is no sound from any song or when I hit play, song is automatically paused everytime. I have to unplug/plug phone for it to all start working. This doesn't happen everytime, but it's done this about a half dozen or so times now.
3. Last but by the far the most annoying and worst. Randomly, when I'm interacting with the Google keyboard or Swiftkey, the phone just starts to spaz out. Random apps open, incorrect text being entered(for example, I type "m" and instead "z" and 3 commas get entered in instead, and just total loss of control on the phone(can't keep anything open or incorrect actions happen).
So I'm the point where either I go for a factory reset(I hate doing this) or I contact support and see about getting an RMA.
FYI: I'm on the November update.
Click to expand...
Click to collapse
Seeing as you have to start from scratch anyway, I'd try a factory reset first. You can always RMA it if the problem persists. Why risk losing your "good" Pixel 2 XL for one that may have a crummy screen restarting the RMA cycle?
Also, was Swiftkey recently updated, like in the last 4 days or so?
mlin said:
Seeing as you have to start from scratch anyway, I'd try a factory reset first. You can always RMA it if the problem persists. Why risk losing your "good" Pixel 2 XL for one that may have a crummy screen restarting the RMA cycle?
Also, was Swiftkey recently updated, like in the last 4 days or so?
Click to expand...
Click to collapse
The RMA is a little better than the previous one in terms of how extreme the shift is, but overall it's not anything worth keeping. The bottom firing speaker buzzes like you wouldn't believe at 60% or higher volume. I don't recall the original one doing this although I did read in another thread that pretty much every phone is doing this.
If the replacement is worse, I'll send it back. It's not like it's a hassle for me. It's pretty much the same doing a factory reset.
Sent from my Pixel 2 XL using Tapatalk
onishchuk4 said:
The RMA is a little better than the previous one in terms of how extreme the shift is, but overall it's not anything worth keeping. The bottom firing speaker buzzes like you wouldn't believe at 60% or higher volume. I don't recall the original one doing this although I did read in another thread that pretty much every phone is doing this.
If the replacement is worse, I'll send it back. It's not like it's a hassle for me. It's pretty much the same doing a factory reset.
Click to expand...
Click to collapse
So, I guess the answer you wanted to hear for your either or situation is do an RMA... Good luck with it.
mlin said:
So, I guess the answer you wanted to hear for your either or situation is do an RMA... Good luck with it.
Click to expand...
Click to collapse
I pretty much wanted to hear if anyone else is seeing these issues. Also, this replacement that I have now is a mid October build.
Sent from my Pixel 2 XL using Tapatalk

Colors are suddenly dull/washed out

All the colors are suddenly dull/washed out on my S9 and turning off blue filter seems to make them even more washed out, I checked the Red Green and Blue from *#0*# and Red looks more like orange, Green looks very bright and Blue looks more like indigo. I'm not really sure what happened, I haven't changed anything on my phone, it just suddenly happened while I was using it and noticed all the colors are suddenly washed out. Also I seem to have black crush/gradient banding issues now too.
Does anyone know what could've happened? And is this a software calibration issue or a hardware issue and my display is screwed?
I wish I could test this in recovery mode by viewing images and see if they look good there before I try to do a factory reset but I don't think that is possible, or is it?
Thanks!
I've the same issue. It was all fine and then i had august security patch and it seems to hace caused all the trouble. Still looking for a solution as it's impossible to downgrade which is so annoying
Shabi_Shaw said:
I've the same issue. It was all fine and then i had august security patch and it seems to hace caused all the trouble. Still looking for a solution as it's impossible to downgrade which is so annoying
Click to expand...
Click to collapse
I was running Android 8 when this happened and now I tried factory reset and also updated to the latest Android 10, but no change at all and now I also found out that I cannot downgrade anymore as the bootloader is a newer version now. So now I'm stuck with a bad display and the ****ty sluggish and ugly (One UI stupid rounded borders and cheap looking icons) Android 10. Android 8 was a lot smoother, looked a lot better, had better battery life and more features - now we don't have Power saving mode for Location anymore which was a great feature.
So don't bother with downgrading as that will not fix it (if we are indeed having the same problem), this seems like a hardware issue. Maybe still possible Samsung could have caused this with a sneaky background "update" to force us to buy new phones.
Thank you Samsung, I'll be sure to not buy any of your products anymore.
I have the same problem. Noticed also that encryption was disabled just after the update.
Hope there will be some solution.
MetorYM said:
I have the same problem. Noticed also that encryption was disabled just after the update.
Hope there will be some solution.
Click to expand...
Click to collapse
When did it happen? My issue happened right after august update and colours look horrible.
Shabi_Shaw said:
When did it happen? My issue happened right after august update and colours look horrible.
Click to expand...
Click to collapse
Does your display look like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
xtexistenz said:
Does your display look like this?
Click to expand...
Click to collapse
Literally like this. I don't have another phone at my disposal rn or i'd have taken a picture. When i scroll down the notification bar and whenever i've watching a video or picture with black, it's all messed up and pixelated. And there's a constant greenish tint all the time.
Shabi_Shaw said:
Literally like this. I don't have another phone at my disposal rn or i'd have taken a picture. When i scroll down the notification bar and whenever i've watching a video or picture with black, it's all messed up and pixelated. And there's a constant greenish tint all the time.
Click to expand...
Click to collapse
I don't get it anymore, since I was on Android 8, is this a hardware issue? Or can Samsung still push a sneaky "update" to mess with our screens so we buy new phones? I wonder if this is even legal what they're doing at this point. Maybe we should find out. My phone originally came with Oreo and I was very happy with it, not with this ****ty Android 10 One UI update.
xtexistenz said:
I don't get it anymore, since I was on Android 8, is this a hardware issue? Or can Samsung still push a sneaky "update" to mess with our screens so we buy new phones? I wonder if this is even legal what they're doing at this point. Maybe we should find out. My phone originally came with Oreo and I was very happy with it, not with this ****ty Android 10 One UI update.
Click to expand...
Click to collapse
This tells that it's a software issue and black crush issues have been resolved in the past with software updates. But i just can't seem to get a hold of anyone at customer care and i'm just hoping the september patch fixes this issue.
Shabi_Shaw said:
This tells that it's a software issue and black crush issues have been resolved in the past with software updates. But i just can't seem to get a hold of anyone at customer care and i'm just hoping the september patch fixes this issue.
Click to expand...
Click to collapse
Did the update fix it for you?
xtexistenz said:
Did the update fix it for you?
Click to expand...
Click to collapse
No it did not. I've had september patch after i've had this issue and that just made things worse if anything at all. Now i've greenish tint and screen gets impossible to see at when device has heated up.
Shabi_Shaw said:
No it did not. I've had september patch after i've had this issue and that just made things worse if anything at all. Now i've greenish tint and screen gets impossible to see at when device has heated up.
Click to expand...
Click to collapse
Thanks for letting me know! I haven't tried it yet as my device is rooted and I have to apply the updates manually.. seems unlikely that it will ever be fixed.
I had a problem with the stock rom to.The colors where washed out, especially with high brightenes.Now i installed Evolution X and no more problems
stefano2626 said:
I had a problem with the stock rom to.The colors where washed out, especially with high brightenes.Now i installed Evolution X and no more problems
Click to expand...
Click to collapse
i actually wanted to install evolution or havoc rom but i couldn't just install twrp properly. Would you please guide me how to do it? Display looks horrible on my phone and that pixelated look on black ares just drives me crazy. Plus can you tell how's the battery and all on evolution? Your help will be really appreciated
All you guys have discussed above is matched with me. I am suffering this for 2 months with my 2 years old s9+. What can we do, even what is exactly to do right now, don't know. Maybe it is Samsung's business policy, they are forcing their flagship users to buy a new flagship device. Any of Samsung's low budget or mid-budget device doesn't face this kind of problem. My family members are using Samsung devices for more than 5 years.
I just hate Samsung's policy. I am deciding not to buy any kind of Samsung product anymore, and I'll not recommend Samsung products anymore. I am sure if it is their policy they can't go further because people are so much aware now.
stefano2626 said:
I had a problem with the stock rom to.The colors where washed out, especially with high brightenes.Now i installed Evolution X and no more problems
Click to expand...
Click to collapse
Can you please confirm if the custom rom fixes the black crush/gradient banding? You should be able to see pixelated areas on darker photos/videos.
xtexistenz said:
Can you please confirm if the custom rom fixes the black crush/gradient banding? You should be able to see pixelated areas on darker photos/videos.
Click to expand...
Click to collapse
I did install the havoc rom, that fixed issue initially but the green tint was still there, i then went back to the stock and issue was worse than it was before ny screen gets not useable at all at times. Its horrible
Shabi_Shaw said:
I did install the havoc rom, that fixed issue initially but the green tint was still there, i then went back to the stock and issue was worse than it was before ny screen gets not useable at all at times. Its horrible
Click to expand...
Click to collapse
So, it seems to be permanently "damaged". All of this seems to be hardware, but maybe still caused by a background update from Samsung to make us buy new phones. For me it happened right under my eyes, while I was using the phone, suddenly some kind of app appeared on my screen, then disappeared and all of the colors changed (it was that big of a difference that I noticed it). So, I tried to reboot thinking it must be some Android bug but it has stayed the same since then. The coincidence is just too much, my screen broke right when some kind of app launched by itself under my eyes and I'm not making any of this up. This really seems like some dodgy background update from Samsung.
I really wish there was a way to verify all of this, but it does seem unlikely that the OLED display broke (exactly the same for all of us) and it still seems pretty capable.
xtexistenz said:
So, it seems to be permanently "damaged". All of this seems to be hardware, but maybe still caused by a background update from Samsung to make us buy new phones. For me it happened right under my eyes, while I was using the phone, suddenly some kind of app appeared on my screen, then disappeared and all of the colors changed (it was that big of a difference that I noticed it). So, I tried to reboot thinking it must be some Android bug but it has stayed the same since then. The coincidence is just too much, my screen broke right when some kind of app launched by itself under my eyes and I'm not making any of this up. This really seems like some dodgy background update from Samsung.
I really wish there was a way to verify all of this, but it does seem unlikely that the OLED display broke (exactly the same for all of us) and it still seems pretty capable.
Click to expand...
Click to collapse
And the fact that none of us dropped our phones and the issue started randomly after the security updates tell the story. My issue started to happen the very day i received august security patch i had no issues whatsoever before. And the fact that no one at samsung is paying attention and there deaf ear towards us that tells that they do know what's happening. How is it possible that hundreds of users of note 9 and s9 are having the same apparently hardware malfunction starting out at the same time? Most of the users started having this issue around and after March 2020. Really disappointed in samsung.
Shabi_Shaw said:
And the fact that none of us dropped our phones and the issue started randomly after the security updates tell the story. My issue started to happen the very day i received august security patch i had no issues whatsoever before. And the fact that no one at samsung is paying attention and there deaf ear towards us that tells that they do know what's happening. How is it possible that hundreds of users of note 9 and s9 are having the same apparently hardware malfunction starting out at the same time? Most of the users started having this issue around and after March 2020. Really disappointed in samsung.
Click to expand...
Click to collapse
Check out the comments, so many people have this problem, right after their warranty ended: https://www.youtube.com/watch?v=m0-npdV-U2c

Categories

Resources