Related
hello
I wanted to know if there have been some bug fixes to the touch?
because it begins to give me a bit of discomfort in games
http://www.youtube.com/watch?v=KsYoxZiBTEA&feature=player_embedded
wave1990 said:
hello
I wanted to know if there have been some bug fixes to the touch?
because it begins to give me a bit of discomfort in games
http://www.youtube.com/watch?v=KsYoxZiBTEA&feature=player_embedded
Click to expand...
Click to collapse
That's my video and no, no fixes yet unfortunately. I spoke to Samsung last week and they were still looking into it. I plan to call them again this week.
Protonus said:
That's my video and no, no fixes yet unfortunately. I spoke to Samsung last week and they were still looking into it. I plan to call them again this week.
Click to expand...
Click to collapse
keep me informed ...... thank you!
do you think is a software problem? or a hardware problem?
wave1990 said:
keep me informed ...... thank you!
do you think is a software problem? or a hardware problem?
Click to expand...
Click to collapse
I am nearly certain that it is a software problem, a bug in the touch controller driver. Famous android Dev supercurio agreed with me, and said tha the touchscreen controller gets recalibrated every time you turn on the screen, which would make sense why the problem goes away when you turn the screen off/on again - yet it affects all apps until you do. It seems like the touchscreen driver is getting a response it can't interpret when playing landscape multitouch games, and it breaks the calibration - and this broken calibration affects everything once it happens. Then you turn the screen off/on again, it recalibrates, and it's fine. For these reasons I believe it's only a software bug, and one they can fix with an OTA update.
If I thought it was a hardware problem, I would have returned the phone. I love the phone otherwise, and I assume they will fix this.
Protonus said:
I am nearly certain that it is a software problem, a bug in the touch controller driver. Famous android Dev supercurio agreed with me, and said tha the touchscreen controller gets recalibrated every time you turn on the screen, which would make sense why the problem goes away when you turn the screen off/on again - yet it affects all apps until you do. It seems like the touchscreen driver is getting a response it can't interpret when playing landscape multitouch games, and it breaks the calibration - and this broken calibration affects everything once it happens. Then you turn the screen off/on again, it recalibrates, and it's fine. For these reasons I believe it's only a software bug, and one they can fix with an OTA update.
If I thought it was a hardware problem, I would have returned the phone. I love the phone otherwise, and I assume they will fix this.
Click to expand...
Click to collapse
I do not know if you develop .... but you could create a fix that recalibrates the driver every tap on the screen!
is an idea =)
New member here, first post.
I had my g4 several weeks ago (uk version). Great phone, however recently the screen seems far too sensitive. Sometimes apps or other features are activating on their own without me pressing on them.
I looked in the settings but havent found a way to resolve this. Can anyone offer any suggestions?
Just to clarify a bit more about my issue.
Its like the "floating touch" some phones have, where i can be an inch or two away from the screen but it still activates. More rarely, it seems as if it was activating by sensing light or movement. Strange. Is the g4 supposed to have this type of function?
pholmes38 said:
Just to clarify a bit more about my issue.
Its like the "floating touch" some phones have, where i can be an inch or two away from the screen but it still activates. More rarely, it seems as if it was activating by sensing light or movement. Strange. Is the g4 supposed to have this type of function?
Click to expand...
Click to collapse
That sounds like a problem. The G4 is actually known for lacking sensitivity and yours is doing the opposite. enable this settings to see if it is actually detecting ghost touches.
Settings, About Phone, Software Info and tap on 'Buidld number' 7 times. Then go back to settings and tap Developer options, enable 'Show Touches'
if the dots show without your intervention, then it's likely due to faulty touchscreen.
Anyways, do a factory reset and see if it helped.
GUGUITOMTG4 said:
That sounds like a problem. The G4 is actually known for lacking sensitivity and yours is doing the opposite. enable this settings to see if it is actually detecting ghost touches.
Settings, About Phone, Software Info and tap on 'Buidld number' 7 times. Then go back to settings and tap Developer options, enable 'Show Touches'
if the dots show without your intervention, then it's likely due to faulty touchscreen.
Anyways, do a factory reset and see if it helped.
Click to expand...
Click to collapse
Thank you. I will give that a try,
As it happens intermittently, i cant say how quick i will find out if that is the solution, but you have been helpful.
:good:
I remember seeing a sensitivity setting somewhere..
Outta said:
I remember seeing a sensitivity setting somewhere..
Click to expand...
Click to collapse
Its under Accessibility
pholmes38 said:
Thank you. I will give that a try,
As it happens intermittently, i cant say how quick i will find out if that is the solution, but you have been helpful.
:good:
Click to expand...
Click to collapse
Does reset solve the issue? , happening on mine right now. Appreciate your feedback. Thanks
Same here, on Imperium and Stock rom, I have the phone since 6 months and it is a really random issue... my bootloader is unlock so I don't know if I can send it to warranty.
For information I have enable the touch "tracing" in developper menu, and when the issue occurred it's getting me perfect vertical line from bottom to top screen, and open a lot of apps..
leclampin said:
Same here, on Imperium and Stock rom, I have the phone since 6 months and it is a really random issue... my bootloader is unlock so I don't know if I can send it to warranty.
For information I have enable the touch "tracing" in developper menu, and when the issue occurred it's getting me perfect vertical line from bottom to top screen, and open a lot of apps..
Click to expand...
Click to collapse
And from the sound of it... Yours pretty much ****ed, at least to my knowledge. Hardware screwed and no warranty. Just bought mine like 3 weeks ago, and hated it so much. So much hyped, but the experienced is so far ****ty at best.
I suspect mine hardware issue. This seems like it's gonna be the first, and the last LG for me. Even mine with warranty still intact. Blackberry used to give this feeling long ago with their ****ty storm. Now, LG and blackberry can share that same ****ed up grave.
As madgibbon indicates, I was on Accessibility / Motricity / Response time (my phone is in french so i'm not sure if it will be exactly like that on yours) and I have set to "Long".
Since that, the issue is no longer appear, I have also switch to rom V20F (Turkey) with still the same setting for accessibility, and I don't have the issue anymore.
I don't know if it is a hardware issue, my phone falls maybe 4 times but with a case and from a little height, no broken glass or something else.
This is all the things I tried before that ;
Using flipcover (QI charge and quick circle), I have tested the "normal" case but same issue
I had a glass protection, I have removed it and cleaned my screen, same issue
I have done lot of hard reset (i'm kind of full wipe addict), same issue
Only the solution of madgibbon works fortunately, thanks mate
I'm also a bit disappointed by this phone, it is great sure I mean fluid, great camera etc... but I have some little issue that ruin the experience unfortunately (this issue with touchscreen, i'm experiencing issue with my Chromecast too that i don't have with other phones, some heating, I don't find the battery usage so good since MM, can't relock bootloader since now). I don't blame LG because i'm using some of their products and I'm / was really satisfied with : Optimus 2x, Nexus 5, TV, Monitor, Sound Bar. Anyway, waiting for 2016's Nexus and I will see if I switch or not.
leclampin said:
As madgibbon indicates, I was on Accessibility / Motricity / Response time (my phone is in french so i'm not sure if it will be exactly like that on yours) and I have set to "Long".
Since that, the issue is no longer appear, I have also switch to rom V20F (Turkey) with still the same setting for accessibility, and I don't have the issue anymore.
I don't know if it is a hardware issue, my phone falls maybe 4 times but with a case and from a little height, no broken glass or something else.
This is all the things I tried before that ;
Using flipcover (QI charge and quick circle), I have tested the "normal" case but same issue
I had a glass protection, I have removed it and cleaned my screen, same issue
I have done lot of hard reset (i'm kind of full wipe addict), same issue
Only the solution of madgibbon works fortunately, thanks mate
I'm also a bit disappointed by this phone, it is great sure I mean fluid, great camera etc... but I have some little issue that ruin the experience unfortunately (this issue with touchscreen, i'm experiencing issue with my Chromecast too that i don't have with other phones, some heating, I don't find the battery usage so good since MM, can't relock bootloader since now). I don't blame LG because i'm using some of their products and I'm / was really satisfied with : Optimus 2x, Nexus 5, TV, Monitor, Sound Bar. Anyway, waiting for 2016's Nexus and I will see if I switch or not.
Click to expand...
Click to collapse
I will try what you suggested, will report back.
Thanks for the tip.
bloodsuckingcomputer said:
I will try what you suggested, will report back.
Thanks for the tip.
Click to expand...
Click to collapse
Nope, doesn't work, it is indeed, a hardware issue.
Thanks anyway. ?
bloodsuckingcomputer said:
Nope, doesn't work, it is indeed, a hardware issue.
Thanks anyway. ?
Click to expand...
Click to collapse
Screen problem after all, just picked my phone up from the place that I bought for under warranty fix, and they told me they did replace for a new screen, and all is looking fine and dandy for now. Hope it stay this way, finger crossed. 3 weeks purchased and already this problem. I doubt this thing will last.
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
You most likely got a bad part. OEM like One plus and xioami are known for using something called product binning. Which means their parts have a higher failure rate then other oems. They also dont make extra parts really so what you got was most likely just a generic screen like you can buy at any shop in China.
Nothing you can really do about it except try a different screen but to be honest I would get a different device and this time dont skip on the price. You get what you pay for and when a good device is cheap there is always a reason. (why do you think most of the owners and mods of XDA run Iphones as their daily drivers and leave android for a hobby)
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
As an experiment, try stock OOS and see whether the issue goes away.
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
ireaper4592 said:
i too have this problem cant find any solution anywhere been trying for about a week now arrggghh
Click to expand...
Click to collapse
tnsmani said:
As an experiment, try stock OOS and see whether the issue goes away.
Click to expand...
Click to collapse
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
gt-kingz said:
Hey there again. I know my answer is kinda late but I wanted to share my experience. So I tried like 10 different custom ROMs with different Android version. The problem got even worse sometimes.
Anyway a few days ago I installed stock OOS and the problem is fixed now. I could not believe at first, but after excessive testing I am 100% sure now.
Anyone can tell why? Is the stock display driver proprietary?
TBH I always used to use custom ROMs (mostly CyanogenMod and now Lineage. Now on stock rom O feel like everything is better than ever before. Battery life, performance. Some features even offer more customization than custom ROMs.
I always thought the opposite is the case since custom roms advertise things like this. I will definitely stick with stock rom for now!
Click to expand...
Click to collapse
Thanks for the confirmation. The cheaper screens seem to have an issue which is not faced by the costlier ones. I have found while roaming the threads that sometimes flashing OOS helps. May be a driver issue.
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
csabatoro said:
Hi!
I'm having a similar issue with my Oneplus 5. Had my screen replaced (new one: OEM) and now it doesn't wake up most of the time either using power button or double tap or fingerprint scanner. I tried everything that I read on forums but nothing worked. Now I seem to have found a solution that I haven't read anywhere yet: I turned off night mode and now it's working as it should. Actually, whenever I want to use any screen adjustment feature like night mode, reading mode etc the screen doesn't wake up. But if I keep the default settings, there is no problem. The issue is definitely the new screen because before that I used night mode all the time (I mean after dark). Now I'm still thinking if I should return the phone to the repair shop and ask for another screen (they offer one year warranty after the repair) or just deal with it... I mean these OEM screen are cheap for a reason (as someone had written here before) and there is no guarantee that the next one will be good, and I don't feel like waiting weeks again for an uncertain outcome, also I can live without said features (gonna miss night mode tho'). Any suggestion? Should I give it a try? Maybe the repair shop made a mistake during assembly? Anyway, I hope this comment will be helpful for those lurking for a solution for a similar problem.
Click to expand...
Click to collapse
Did you try OOS?
OEM screen is not cheap (atleast compared to what is offerred online).
May be you are better off with what you have since you have found a work around. Who knows what you will get next time?
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
skymera said:
My understanding from what I've read, third party displays needed kernel support.
I paid OP to replace mine - no problems.
Click to expand...
Click to collapse
How much plz?
Shreeram02 said:
Yea I have same problem it works totally fine on oos but on custom roms it is ****ed up
Click to expand...
Click to collapse
Thank you also for confirming that on OOS there is no issue. Looks like the cheaper of the online replacements have this issue while the costlier ones don't.
Funniest thing is I have a slim ROM backup on 7.1. and that works fine so like what the f--- any ideas people?
gt-kingz said:
Hey guys,
About 1 month ago the screen of my OP3 broke and I bought a replacement on eBay.
After the replacement I encountered problems, which only occured from time to time. Sometimes when waking up my device the screen stayed black.(Like on every 20th attempt it happened once). After pressing the power button some more times, the device finally unlocked. I am 100% sure that the device always unlocked on uneven attempts which means that the device at least woke up software-side.
I was totally sure that my replacement screen was kinda flawed and it is a not fixable hardware problem.
Then one week ago I switched from official LOS15.1 to the unofficial LOS16 rom and encountered big differences. The problem got noticebly worse. Waking up the device was a pain in the a**, it never worked on the first attempt on this rom. It's not unusual that it takes between 11 and up to 60 tries to wake up the device which makes it nearly impossible to use the phone. As before, the screen at least turns on software-side after every attempt. I can see this because the hardware buttons always light up.
Now after one week I switched back to official LOS15.1 and voilà, out of 20 attempts, the device instantly unlocked 19 times.
I know it is hard to understand and even to analyze such kind of problems, but there must be some solid solution for my problem.
Atm my clue is that original screens always offer more functions (e.g. gestures) than replacement lcd screens. Those functions are always connected to the software(rom). Is it possible that there is any other function (e.g. anything related to tap2wake or deepsleep) which is able to prevent my screen from turning on?
To deliver some more infos:
- I used standard system settings on both roms to test this out.
- "prevent" accitential wake up is turned off
- tried to disable gestures
- I tested my proximity sensor via an app, it seems to work flawless
- waking up screen in twrp is also very difficult and needs around 15-20 tries. Does anyone see any pattern?
Click to expand...
Click to collapse
Yes, I have the same issue and I wanted to revert back to Stock OOS, but I just tried Caesium latest kernel, and the display wakeup issue seems to have gone. I'm using Havoc OS 2.3 based on Android Pie.
Guys the latest mad kernal reborn it wakes up all the time
At least for my screen
It used to be worse on all the other kernals
Finally found a solution
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Mohammed Raihan said:
I had same problem on custom roms after replacement of display of my oneplus3...i was on oos 5.0.8 i had no issues in that but am a custom rom user and now the solution is flash any rom clean flash not dirty flash and flash gapps then flash any module if you want like magisk and then reboot setup the device and after first boot flash mcd custom kernel and yippeee enjoy... Present am on havoc os with no issues... Try and let me know...
Click to expand...
Click to collapse
post link to one u have plz
Mail me i have that file..
[email protected]
There is issue while sending here
Mohammed Raihan said:
[email protected]
There is issue while sending here
Click to expand...
Click to collapse
got anyway working fine cheers dude
Even i have the same problem as mentioned above..even i changed my oneplus 3 display
I always prefer custom roms..but screen wakeup issue had made my phone worse...then i tried oos 5.0.8 and it works like a charm...yeah i know its very old android version but no other option though...
Others who have same problem and have no issues going back to oos oreo then go for it...your problem is solved..
---------- Post added at 01:47 PM ---------- Previous post was at 01:43 PM ----------
ireaper4592 said:
got anyway working fine cheers dude
Click to expand...
Click to collapse
Is this kernel working for you!??
Bought a LG G8S today but have an issue with the always on display there's a faint Grey background that is only on the half of the screen to put it simple the from the top to half of the screen background is not fully black.
http://imgur.com/a/XvYNAlG
https://imgur.com/a/PoSFJep
That's definitely weird, I don't have that issue, but in any case I dont even use aod, i just have it set to display alerts. Aod to me was always a battery drainer.
But that looks like it could possibly be a screen burn, can't say for sure though.
Try searching for a completely black picture online (google or something) and look if it behaves the same when you put that picture in fullscreen
if yes it's an issue with your screen (which is highly possible, it doesn't look like something software-side-y to me)
LG G8S here in UK.
MASSIVE screen burn.
Literally half the screen has gone a VERY dark green.
Any way to fix this?
thanks
Matt
Me too
I have the same problem, but isn't hardware problem, if you put a black image doesn't appear that, I'm sure that is a software problem. Already I contact LG support but they just told me go to the store where you buy it for warranty
Coreinsp said:
Bought a LG G8S today but have an issue with the always on display there's a faint Grey background that is only on the half of the screen to put it simple the from the top to half of the screen background is not fully black.
http://imgur.com/a/XvYNAlG
https://imgur.com/a/PoSFJep
Click to expand...
Click to collapse
I have it too but it's only visible at night in very low light. I suspect it's software related since activating the AOD during the day works as it should.
I'm facing the same issue. I think it's most probably a software or hardware issue which is involving the ambient light sensor. For me, it doesn't occur only while using the AOD feature when the phone is placed within a dark enviroment. It also occurs on the superior half of the screen for a period of one second or so if I cover and then uncover the ambient light sensor or when I use the Brief notifications feature. It is only noticeable in low light conditions.
Also, I have contacted LG Support but unfortunately they were not able to provide any solution.
AlexSTGM said:
I'm facing the same issue. I think it's most probably a software or hardware issue which is involving the ambient light sensor. For me, it doesn't occur only while using the AOD feature when the phone is placed within a dark enviroment. It also occurs on the superior half of the screen for a period of one second or so if I cover and then uncover the ambient light sensor or when I use the Brief notifications feature. It is only noticeable in low light conditions.
Also, I have contacted LG Support but unfortunately they were not able to provide any solution.
Click to expand...
Click to collapse
I think it's a software issue. It's very unlikely to be hardware since we have different hardware by different factories. I have the "Brief Notifications" - "Bubble notifications" feature activated and when a notification comes in it also happens but only in low light environments.
I am also on Android 10 - build V20a
MirceaViP said:
I think it's a software issue. It's very unlikely to be hardware since we have different hardware by different factories. I have the "Brief Notifications" - "Bubble notifications" feature activated and when a notification comes in it also happens but only in low light environments.
I am also on Android 10 - build V20a
Click to expand...
Click to collapse
I see. If it really is a software issue, then it must be a persistent one. I am currently on Android 9 V10r and had this issue from the very beginning. It isn't that annoying but I hope LG will provide a solution.
AlexSTGM said:
I see. If it really is a software issue, then it must be a persistent one. I am currently on Android 9 V10r and had this issue from the very beginning. It isn't that annoying but I hope LG will provide a solution.
Click to expand...
Click to collapse
Strange. I got the answer that some users are not facing the issue. Hope LG can provide an answer.
MirceaViP said:
I think it's a software issue. It's very unlikely to be hardware since we have different hardware by different factories. I have the "Brief Notifications" - "Bubble notifications" feature activated and when a notification comes in it also happens but only in low light environments.
I am also on Android 10 - build V20a
Click to expand...
Click to collapse
I can assure that it is not an a software issue because when I went back to the store to show the problem they replaced my phone right away but I asked the manager to let me compare both phone screens and they confirmed that it is a display defect. Also I gave up on the phone completely since the replacement unit had a defect on the WIFI\SIM module.
Coreinsp said:
I can assure that it is not an a software issue because when I went back to the store to show the problem they replaced my phone right away but I asked the manager to let me compare both phone screens and they confirmed that it is a display defect. Also I gave up on the phone completely since the replacement unit had a defect on the WIFI\SIM module.
Click to expand...
Click to collapse
I understand. Thank you.
I have noticed this problem too today. AOD is grey, it was fine on A9. Hope LG will fix this (..but i doubdt ).
Generally, an AOD is a bad idea for an OLED screen because of its burn-in effect. Active pixels age while others do not or only slowly. Further, some sub-pixels age faster than others, e.g. the blue ones faster than the green ones. Manufacturers spent a lot of time, money and effort to conceal this effect ... because they failed to really avoid it. In fact, sub-pixels, that are not as worn out as others, are artificially aged to get a uniform degradation of the screen.
The phenomenon you described might be a side effect of this „uniform OLED screen degradation technology” (euphemism?).
As a conclusion one could say that some decent LCD is still a good idea, especially Motorola's method to show time and notifications for some seconds whenever you lift your phone from the table or similar.
MirceaViP said:
I think it's a software issue. It's very unlikely to be hardware since we have different hardware by different factories. I have the "Brief Notifications" - "Bubble notifications" feature activated and when a notification comes in it also happens but only in low light environments.
I am also on Android 10 - build V20a
Click to expand...
Click to collapse
It ist not a good idea to post a screenshot with your IMEI. I would blacken the IMEI
Sorry for Off Topic
did someone tried hard reset or flashing the software manually via pc?
lol...it's a hardware issue LG will refuse to own up too.
Ma Kid's phone went so green after only a few months, EVERYTHING was unreadable.
Matt
Any time the screen turns off and I turn it back on, I have to wait 30 seconds to a minute before the touch screen is responsive at all. I've tried using my fingerprint or removing all screen security and that doesn't seem to make a difference. Has anyone else run into a similar issue? Any idea on how to fix it?
zebinadams said:
Any time the screen turns off and I turn it back on, I have to wait 30 seconds to a minute before the touch screen is responsive at all. I've tried using my fingerprint or removing all screen security and that doesn't seem to make a difference. Has anyone else run into a similar issue? Any idea on how to fix it?
Click to expand...
Click to collapse
What android version are you running? Do you have many apps installed? Have you tried restoring back to factory defaults?
I believe it started after upgrading to 9 manually a few weeks ago. But I've tried a few different ROMs with the same situation. I have not rolled back to 8 to test that yet. It happens right out of the gate without installing any additional apps as well. I've done multiple full wipes, including unlocking the bootloader that for sure wiped everything with no change to the situation.
zebinadams said:
I believe it started after upgrading to 9 manually a few weeks ago. But I've tried a few different ROMs with the same situation. I have not rolled back to 8 to test that yet. It happens right out of the gate without installing any additional apps as well. I've done multiple full wipes, including unlocking the bootloader that for sure wiped everything with no change to the situation.
Click to expand...
Click to collapse
Fastboot upgrade? If not, i'd download 9 stock RETAIL and just flash it all with fastboot
Ok, I'll try that when I get a chance. we'll see if it works.
marcost22 said:
Fastboot upgrade? If not, i'd download 9 stock RETAIL and just flash it all with fastboot
Click to expand...
Click to collapse
I just re-flashed via fastboot 9 stock RETAIL found here. Looks like I'm still having the same issue as before with the touch screen not being responsive after turning the screen back on. Even if it's only been off for half a second, it will still not be responsive for a minute
Any further ideas? Or is there a better location to get the RETAIL image for XT1710-01?
zebinadams said:
I just re-flashed via fastboot 9 stock RETAIL found here. Looks like I'm still having the same issue as before with the touch screen not being responsive after turning the screen back on. Even if it's only been off for half a second, it will still not be responsive for a minute
Any further ideas? Or is there a better location to get the RETAIL image for XT1710-01?
Click to expand...
Click to collapse
This is gonna sound weird, but have you changed your screen at all?
marcost22 said:
This is gonna sound weird, but have you changed your screen at all?
Click to expand...
Click to collapse
Actually, yes. Just after getting the phone, it was dropped and the screen had to be replaced. The fingerprint sensor has been loose ever since then too. But this was never an issue until flashing a new ROM
zebinadams said:
Actually, yes. Just after getting the phone, it was dropped and the screen had to be replaced. The fingerprint sensor has been loose ever since then too. But this was never an issue until flashing a new ROM
Click to expand...
Click to collapse
did you have someone else replace your screen? If so, and it might sound weird, they might have installed an LCD screen instead of OLED; and then modified the stock rom for that. You might not know, but OLED and LCD have very different power profiles, so when turning LCD on you can just blast it, meanwhile oled you need to slowly bring the power up. This is what might be causing your issues
marcost22 said:
did you have someone else replace your screen? If so, and it might sound weird, they might have installed an LCD screen instead of OLED; and then modified the stock rom for that. You might not know, but OLED and LCD have very different power profiles, so when turning LCD on you can just blast it, meanwhile oled you need to slowly bring the power up. This is what might be causing your issues
Click to expand...
Click to collapse
Yeah, I had someone else install the screen for me. How would I go about checking if its LCD vs OLED? And do you know what would need to be modified in order to fix it if it is LCD?
zebinadams said:
Yeah, I had someone else install the screen for me. How would I go about checking if its LCD vs OLED? And do you know what would need to be modified in order to fix it if it is LCD?
Click to expand...
Click to collapse
You would need to remove the screen. Otherwise you can use something like AOD and check if the whole display lights up vs only the clock or whatever. On an LCD screen the whole display will light up a tiny bit vs complete black on OLED.
You would need to modifiy the dtb's and kernel, but it's something i would be able to do for you
marcost22 said:
You would need to remove the screen. Otherwise you can use something like AOD and check if the whole display lights up vs only the clock or whatever. On an LCD screen the whole display will light up a tiny bit vs complete black on OLED.
You would need to modifiy the dtb's and kernel, but it's something i would be able to do for you
Click to expand...
Click to collapse
It looks to me like OLED to me with only the clock lighting up. I could still take the screen off at some point to verify if needed.
Thanks for all of your help by the way
zebinadams said:
It looks to me like OLED to me with only the clock lighting up. I could still take the screen off at some point to verify if needed.
Thanks for all of your help by the way
Click to expand...
Click to collapse
I don't know if it's the reflection, but is there some bleed around the clock? Like is the dark areas lighter compared to the rest of the screen?
marcost22 said:
I don't know if it's the reflection, but is there some bleed around the clock? Like is the dark areas lighter compared to the rest of the screen?
Click to expand...
Click to collapse
I think it's just the reflection? Here's a shot of my Nexus 6p right beside it and I think they look basically the same.
The phone is used almost exclusively for kids videos so it's not the end of the world if I never get it fixed, but at the same time, it would alleviate some frustration when I'm helping my daughter turn a show on.
zebinadams said:
I think it's just the reflection? Here's a shot of my Nexus 6p right beside it and I think they look basically the same.
View attachment 5544389
The phone is used almost exclusively for kids videos so it's not the end of the world if I never get it fixed, but at the same time, it would alleviate some frustration when I'm helping my daughter turn a show on.
Click to expand...
Click to collapse
Yeah, to me it still looks significantly brighter around the clock
marcost22 said:
Yeah, to me it still looks significantly brighter around the clock
Click to expand...
Click to collapse
Ok, I'm willing to try modifying the ROM if that'll get rid of the stupid touch screen delay. How difficult is it? I know you said you would be willing to do it for me, but if it's not something that will persist through an update (I had been running AICP) and it's something that I could learn to do, all the better. If that's not realistic, that's fine as well.
zebinadams said:
Ok, I'm willing to try modifying the ROM if that'll get rid of the stupid touch screen delay. How difficult is it? I know you said you would be willing to do it for me, but if it's not something that will persist through an update (I had been running AICP) and it's something that I could learn to do, all the better. If that's not realistic, that's fine as well.
Click to expand...
Click to collapse
[REFERENCE] How to compile an Android kernel
Introduction Hello everyone, I will be going over how to compile a kernel from beginning to end! Prerequisites: A Linux environment (preferably 64-bit) Knowledge of how to navigate the command line Common sense A learning spirit, there will be...
forum.xda-developers.com
Is a great guide, you'd need to follow the clang guide tho, as our kernel IS clang-compiled, and i recommend repacking the boot.img
You'd need to change this line
kernel_motorola_msm8953/msm8953-albus.dtsi at 7befedacd91b84ed737b691671c088c89e394f66 · AICP/kernel_motorola_msm8953
Contribute to AICP/kernel_motorola_msm8953 development by creating an account on GitHub.
github.com
In your source to be
qpnp,qpnp-labibb-mode = "lcd";
If i'm right, after doing that and flashing it the issue will be fixed. Otherwise when you try to turn on the display it will cause a kernel panic
You would need to reflash this boot.img after every update, and redownload sources everytime i do something to kernel.