I have two V60s and I noticed that the AOD brightness of one is always bright and the other is always dim no matter what I do. I am running A11 on both phones. I have gone into the AOD display settings and tried to toggle the brighter AOD on and off and it does nothing on both phones. Any one else experience a non-changeable AOD brightness? Any workarounds or solutions?
I solved the problem. It is related to the dreaded fingerprint reader bug. I turned off the fingerprint reader to unlock the screen and all is working perfectly normal.
Really hoping LG fixes the fingerprint issue.
Thank you for coming back to post your solution. It's shocking how many folks will just edit in a "NM I solved it" and not post their solution!
Do you have any more information and the "dreaded fingerprint reader bug?" I've been experiencing some lock screen/AOD issues that actually started maybe a week before Android 11 was deployed by AT&T, and persisted after the A11 upgrade AND a factory reset after that. I haven't had the chance to really troubleshoot it, because it's more of an inconvenience than a dealbreaker, but was eyeballing Nova Launcher or my dynamic live wallpaper as possible trouble points.
Regarding the fingerprint reader bug:
https://www.reddit.com/r/LGV60/comments/m8h4dm
This is upsetting because I sent in a G8 that had some issues for two year warranty and got back a phone that seems crippled by software issues. I really hope LG fixes as they promised support after mobile business shut down.
Interesting, thanks for posting that. I installed the CPU Monitor app that a bunch of users there posted screenshots of, and I'm watching the 8x CPUs update every second or so. Very rarely all 8x spin up to 100% (when I first unlock my phone, for example), but the majority of the time, they hover between 29% - 38%. I have my fingerprint sensor on for both the lock screen and certain apps secured via biometrics (bank, password manager, MFA apps, etc). I'm not sure what "normal" should be, but high 20s to 30s seems reasonable? I've been monitoring on and off for the past few minutes, and at no point did my CPUs remain at a sustained 100%. Not even close.
Then again, the two threads I read through from your link were both from around a month ago, and I think AT&T released an update since then (their second A11 software update, IIRC, bumping the Android security patch up to March 1, 2021). So perhaps the most recent AT&T software update fixed whatever that issue that they were experiencing? It doesn't appear that either thread has seen any new activity in at least a month or so. I believe that the comments in one of the threads also mentioned that this wasn't an issue with T-Mobile or Verizon's version of A11. So if it was an AT&T issue, it's possible that the March 1, 2021 security patch update quietly fixed it.
Edit - I meant to post this earlier, but I have noticed that since the A11 update, that auto-brightness doesn't work as consistently as it used to. The problem, in my experience, is that things remain too dim. My temporary fix has been to pull down the notification shade, toggle auto-brightness off, then turn it right back on. That seems to reset the brightness to a comfortable level and re-enable auto-brightness. At least for a while. The auto-brightness will eventually die again. I usually have to do this once or twice a week. Annoying, for sure, but I don't know of any other solution. I reboot my phone around once a week, and that doesn't seem to help. I also did an immediate factory reset after upgrading to A11, but the problem persists even after a fresh set-up. It definitely was not an issue on A10. I figure it's an A11 bug and hope it'll be quashed eventually.
If your CPU is changing percent loaded then you are good. Temps in the 20s and 30s are also appropriate.
I have two TMobile variants with the fingerprint bug on A11. The latest TMobile update was only a security patch update.
I have reached out to LG on Facebook, Twitter, and Voice of Customer hoping they will address this issue.
Good luck!
Related
My 7.1.1 Pixel wifi hotspot seems to turn itself off every so often. Roughly once a day. Searching tells me that there was a hotspot timeout setting in prior versions of Android, but it seems to not exist in 7.1.1 Nougat.
Does anyone know if it moved, or if there is another way to extend or eliminate this timeout? I wouldn't care that much but I'm kind of forced to use the sim removal trick to activate it currently and it's kind of a pain to do every day.
chili81 said:
My 7.1.1 Pixel wifi hotspot seems to turn itself off every so often. Roughly once a day. Searching tells me that there was a hotspot timeout setting in prior versions of Android, but it seems to not exist in 7.1.1 Nougat.
Does anyone know if it moved, or if there is another way to extend or eliminate this timeout? I wouldn't care that much but I'm kind of forced to use the sim removal trick to activate it currently and it's kind of a pain to do every day.
Click to expand...
Click to collapse
Same issue here.... I've looked everywhere for a timeout setting!
+1
anything new?
No news here. I've been getting used to doing the sim trick every morning - not as bad as I imagined with my Spigen rugged armor case I can just peel back the corner and you don't have to pop the sim out more than a couple mm's. Still kind of sucks though - the setting has got to be in code still somewhere.
Side note, has anyone taken the early feb update yet, and does this trick still work?
Had the phone for about a week now. (Verizon)
Today i tried to activate wifi calling...no good. Factory reset the phone thinking maybe it was an app..still nothing.
I have also noticed that over the past couple of days, the phone has been getting more and more laggy. Not many apps on the phone at all. No different than the apps on my V20 which never really had a lag issue. The phone seems to struggle as well when opening messaging or opening a url from an email...sometimes it will not even load the page. It just stays on the current page that chrome already had open.
Starting to feel like there are some bugs LG needs to fix..
Im swapping the phone out this weekend for another one...Main reason for the swap is the phone not activating wifi calling..that def seems like a hardware issue.
Not sure if anyone else has noticed but if you have the brightness on 100% or any brightness for that matter, if you look at the phone from any angle besides straight at it, it gives the whole screen a blue tint...Samsungs do not do that with their oled panels.
Symptom of the Poled?
Anyone else experiencing annoying bugs with the phone??
Settings/Developer Options/tick on "Force GPU Rendering" should make the beast smoother faster. if root available try L Speed/Entropy/fstrim apps found on Play Store! If LG G6 gets Android 7.1.2 , the performance should improve smoother over Android 7.0 just like the LG V30 is incredibly smooth and fast due to SD 835. Android Oreo 8.0 should have faster boot times on powering up. LG flagships gets Oreo by the end of this year (November or December)
I noticed Wifi calling didn't turn on right away. It said it was working on it and it took a little bit, maybe 10-15 minutes before it actually said it was activated. I have not noticed any tint issue when viewing the phone from an angle
Dump chrome, install Samsung browser apk. With the crystal add blocker. Eliminate animation scale to .5, install a different launcher. Text for me with Verizon message+ works really well, live the pop up window so I can reply without closing the app I'm in. Truly the phones not lagged" me at all. Love the speed, hate the screen protector issues but phones doing great and I got it Oct 5th.
Dont have those issues, but did notice a little process when first booted to get wifi calling settled in. Had to confirm a prompt of some sort and wait a bit.
I havent had any of those issues, mine have been the wifi always dropping at home and my camera seeming like its fuzzy with the pictures I take.
Thanks guys...had developer options opened and changed those settings already...going up the road today to get it switched out so wifi calling can work...hopefully that solves the issue
Wifi calling works fine on mine. Any issues so early, exchange phone
farside420 said:
The phone seems to struggle as well when opening messaging or opening a url from an email...sometimes it will not even load the page. It just stays on the current page that chrome already had open.
Starting to feel like there are some bugs LG needs to fix..
Click to expand...
Click to collapse
Oh, I can bet they sit there lazy and wait for some urgent advices to get starting with Oreo development
farside420 said:
Not sure if anyone else has noticed but if you have the brightness on 100% or any brightness for that matter, if you look at the phone from any angle besides straight at it, it gives the whole screen a blue tint...Samsungs do not do that with their oled panels.
Click to expand...
Click to collapse
Samsung OTOH goes to green or pink tint. You don't fool us.
Hello everyone, I just got this tablet today and I'm having an issue with it. I was trying to play a music game and I noticed that when I touched both extremes of the screen the multitouch would release my fingers for some reason. I've recorded a video of it using a multitouch application just to make sure I wasn't going crazy, here it is:
Link to the Youtube video
Do you think it's defective? If anyone has this M5 10 tablet could you test it for me and see if you also have the same multitouch issue? Since I just got it today, should I return it? Or is it something that can be fixed?
Thank you.
Received mine today from Boulanger in France, i used the same software as you to test it. Everything is working fine, even with 3 or 4 fingers, using the same kind of routine you used. So i suppose that your tablet is faulty. Sorry mate.
RubyRP62 said:
Received mine today from Boulanger in France, i used the same software as you to test it. Everything is working fine, even with 3 or 4 fingers, using the same kind of routine you used. So i suppose that your tablet is faulty. Sorry mate.
Click to expand...
Click to collapse
This stuff happens Thanks for testing it out! This one is going back
I have the same problem bro! You can find my post here: https://forum.xda-developers.com/showthread.php?t=3777471
I have already open a ticket on the support
Sent from my [device_name] using XDA-Developers Legacy app
I have the same issues als well. You can see it very well with the App "Multi touch test" from Spencer Studios.
Has someone more info on this issue as the tablet is useless for me with those touch problems and I will send it back if there is no fix available in the near future.
andrgin said:
I have the same issues als well. You can see it very well with the App "Multi touch test" from Spencer Studios.
Has someone more info on this issue as the tablet is useless for me with those touch problems and I will send it back if there is no fix available in the near future.
Click to expand...
Click to collapse
Hi Andrgin, which is your problem? In my case I have the problem only if I touch the screen with two fingers. In this case seems that the tablet, after 2 sec, can't recognize anymore the touch. I'm waiting the response of the support for the ticket that I opened, hopping that they can tell me that is only a software problem and not an hardware issue, let's see...Anyway I have your idea too, I bought this tablet to play music game and is really useless with this problem.
When I touch the screen with 2 fingers at the same time and do not move them for about 1 second the tablets looses the touch of both fingers. It does not happen if I dont put both fingers down at the same time (more than about 500ms), move the fingers around while they touch the screen. Also it does not happen with 3 or more fingers.
To me it seems like the system treats the as a gesture.
I made a video about it:
youtu.be/PXXakOw_1Hk
I also thinks that the system treats this as some kind of a weird gesture. I don't think it is related to the hardware. I'll ask the Huawei support soonish because it really is annoying with cytus 2 for example or even pdfs when you want to pan soon and have 2 fingers on it and then your touch input gets removed.
This is with the 10 pro
Could it be, I hope that you are right but is really strange that only some devices have this problem, if it is a software problem, all the devices with this software need to have the issue.
I think all have this problem. So far everybody that said he does not have this bug had tested it the wrong way. You have to place both fingers at the same time and do not move them. If you move them while touching the screen it still works.
And no I dont think it is hardware related.
I also experienced this (talked about it in another thread), but it must be more complicated than that.
It's not something that systematically happens whenever i put two fingers down a the same time. It works just fine most of the time, but occasionally notes will drop, always in the same spots, in the same songs. "Pointer location" shows the touch is still being registered, if that's anything to be trusted.
I'll take the occasion to ask again since there seem to be other people who play music games in this thread: beside the touchscreen issues, has anyone noticed a slight delay on the audio feedback? I'm talking about a 100-150 ms delay from the moment i touch the screen to the moment the corresponding sound effect plays. The touch itself is registered correctly, but the audio lags behind for some reason.
Either way, i sent back the 10.8", gonna have the 8.4" here by tomorrow i hope, will update on how this one behaves.
It does not matter where you place your fingers only that it happens at the same time (less than about 500ms) and you dont move them for about 1 second.
About audio I dont know. Most time I had sound off.
It may be a general Android Oreo bug, although the article speaks about Android 8.1, not 8.0:
https://www.xda-developers.com/android-8-1-oreo-multi-touch-bug-fixed-june-update/
Maybe Huawei used parts of Android 8.1 for the M5.
A fix from Google is planned for the June security update.
Just tested the 8.4", after installing the new update. Interestingly enough, it didn't seem to drop any inputs.
The sound delay, however, is exactly the same, and it baffles me no one else seems to notice it.
On top of that, i think i got a defective unit, as the charging speed starts off at 3300-3400 mAh, then drops to 500-600, never to rise again. So much for quickcharge.
Battery also seems to run considerably hotter for no apparent reason: 37 degrees Celsius while charging at that pitiful speed, no other apps running.
For reference, the 10.8" never exceeded 32 degrees, and that's while charging at max speed, with apps running at the same time.
Overall, this tablet has been nothing but a huge disappointment, i'll just refund it and wait for something else to come out at this point.
Edit: it charges normally when the screen is turned off. When the screen is on, the charger seems to provide enough current to offset whatever i'm consuming, plus those 500-600 extra mAh, so no matter what i'm doing that speed doesn't change. The 10.8" was charging normally, full speed minus whatever power i was drawing, so i'm still pretty sure something's not right.
@chris_g I really hope it could be the problem but wait two more months it's really frustrating! For now I haven't received yet one answer from the support...
Not really good news from Italian support, them tell me that no reports was received about our problem, so them suggested me to try to reset the device to the default to see if is a software problem. Did you guys found something else? I'm really thinking to request the replace of the device.
Just to be sure, could someone give me the mail of the international/English support? I want to try to write a mail also to them.
Cheers
I got the M5 Pro from amazon.it and the warranty check showed that I get warranty in most European countries. I opened a ticked with the Austrian support providing all the info they needed. They said they dont know of the problem so far and will forward it. This was over 1 week ago and I did not receive any response yet.
Replacing the tablet will not solve anything because every M5 (at least the 10" versions) have this bug.
And no it is not an Oreo bug because my Mate 10 (also EMUI 8.0) works fine. I guess it is some code Huawei added to support the pen.
Firmware Finder already shows a EMUI 8.1, but it is not approved for installation yet. I guess we will get Oreo 8.1 in a few weeks/months and this bug will hopefully be fixed in the new version.
andrgin said:
Firmware Finder already shows a EMUI 8.1, but it is not approved for installation yet. I guess we will get Oreo 8.1 in a few weeks/months and this bug will hopefully be fixed in the new version.
Click to expand...
Click to collapse
Don't be so optimistic on that one, as Google themselves introduced an all new multi-touch bug in the 8.1 base. Thus one bug will maybe just be replaced by another one, as Google already stated that they'll have the bug fixed in the June update soonest. Let's hope Huawei uses the patched June base to upgrade our tablet to 8.1.
Sent from my HTC U11 using XDA Labs
Huawei already ships Android 8.1 with the P20 so I guess we are getting the same code. I never heard about multi touch problems there so I guess Huawei has already replaced that faulty Google code. With all the people complaining about late Android updates for existing devices, but there is a reason most vendors wait until they release a new Android version for the masses. Google phones are simply beta test devices.
I have the 8.4" wifi model. It suffers the multi-touch problem but not the sound delay problem. I tried the drum pad app, sounds play instantly as soon as I touch them.
I have a bunch of log-cats, but I'm not exactly sure what they mean.
I'm flashed the Chinese dev rom (marshmallow) and run the calibration. The messages I see: https://pastebin.com/i1ZiMQ15
And from when I had AOSPEx 8.1, running logcat during attempts to add a fingerprint: https://pastebin.com/VunWrFhA
I downloaded the source I could find for this phone and ran a file scan from inside notepad ++ to try and find the references to these log entries. Unfortunately they seem to be something automatically generated higher up in the code due to class inheritance/object delegation. I'm not very good at following that sort of thing. I decompiled the QFPservice apk and found code making references to a bunch of the status and enroll results, but again, at this point they're just integers, as I have no idea where the entity defining them is located within source, and Google's source documentation didn't really help.
Does anyone think this is a hardware failure? I just want to know before I go through the trouble of getting the parts to attempt to replace the sensor, and the more definitive an answer I can get the better.
Thank you for any assistance.
Just reflash a ROM, EUI from start and Just try to update the firmware -> https://androidfilehost.com/?fid=818070582850487752
And make a test again on EUI rom.
Is there a guide on the specifics of this? I may just be paranoid as I type this, but I just have a message on TWRP saying "Phone will reboot in 5 seconds" after "Firmware updated". The console on my PC shows only 48% on the sideload though....
Edit: I forced a reboot since things seemed done. No adverse results, but the FP scanner still doesn't work.
Edit2: Tap for photo .... "works", but its random. I suspect the sensor is if not entirely dead, entirely faulty. I bought an FP sensor anyhow, so I guess it's kind of moot to waste time on this now.
I don't believe that you can fix the dead fingerprint sensor with a firmware upgrade. Mine works for only one day when I bought the Le Max2 X820 and then it was death. 100 % shure that this is a hardware issue and can't be fixed without change the fingerprint sensor.
Beackman said:
Just reflash a ROM, EUI from start and Just try to update the firmware -> https://androidfilehost.com/?fid=818070582850487752
And make a test again on EUI rom.
Click to expand...
Click to collapse
shredman said:
I don't believe that you can fix the dead fingerprint sensor with a firmware upgrade. Mine works for only one day when I bought the Le Max2 X820 and then it was death. 100 % shure that this is a hardware issue and can't be fixed without change the fingerprint sensor.
Click to expand...
Click to collapse
It may be coincidental, but I'm virtually certain this was due to a hardware problem I directly caused. It was working quite well, and then I used a qi-receiver tag that I had just ordered from China (one of no particular quality to recommend it) and the sensor failed immediately thereafter. So, in my particular case I think I did it to myself.
In my isolated result however, I am forced to concur. A full restoration from Qualcomm's QFIL flash failed to restore function to the sensor, and at best it shows phantom presses, though these seem to have ceased entirely in favour of total death. I've had the sensor "die" on some ROMs before, but I'm pretty convinced at this point, having loaded every offering I could find, that I have killed it in the purest sense.
However, I was just wondering if anyone knew what those reported values actually meant in the logcats? I guess it's moot now, as I've ordered a new FP scanner from Aliexpress, but we'll see. My hope is that switching out the hardware goes smoothly, particularly considering there only seem to be QFIL available for X820, not for the X829.
TheLastCanadian said:
It may be coincidental, but I'm virtually certain this was due to a hardware problem I directly caused. It was working quite well, and then I used a qi-receiver tag that I had just ordered from China (one of no particular quality to recommend it) and the sensor failed immediately thereafter. So, in my particular case I think I did it to myself.
In my isolated result however, I am forced to concur. A full restoration from Qualcomm's QFIL flash failed to restore function to the sensor, and at best it shows phantom presses, though these seem to have ceased entirely in favour of total death. I've had the sensor "die" on some ROMs before, but I'm pretty convinced at this point, having loaded every offering I could find, that I have killed it in the purest sense.
However, I was just wondering if anyone knew what those reported values actually meant in the logcats? I guess it's moot now, as I've ordered a new FP scanner from Aliexpress, but we'll see. My hope is that switching out the hardware goes smoothly, particularly considering there only seem to be QFIL available for X820, not for the X829.
Click to expand...
Click to collapse
Now you have ordered a new FP sensor, i thinck is better wait and install the new one, before install update the firmware with the file i have posted and replace the FP sensor.
The errors on log maybe is a fault on try to initiate the FP sensor.
I bought this used s9 plus for quite affordable price. Everything looked fine during testing but after sometime, I observed whole screen to be of Greenish shade.
I rebooted and it worked absolutely fine. On searchibg internet, i found threads, yt videos by a number of people, almost all claiming that it is an update consequence. My questions are
1. Is it a software issue? If yes, can I expect some wayto solve - official ota or root and custom or old rom (if possible at all)?
2. If not software issue, is it a software induced hardware issue? Any way to repair without paying full for display?
2.1 If i get it replaced somehow, will itcome back again?
3. In any case, if I don't get it repaired, how long can I expect the deviceto be functional; ie before this green shade becomes permanent instead of being intermittent making device unusable?
I have a similar question for s9 too which ill post in that forum.
Thank you