Related
Hey guys, I have to ask:
- Does this device have a bootloader lock such as sony smartphones when purchased from a carrier?
- Is there any sudden death/current bugs/defects I should look out for? (tinted screen, broken hardware buttons, bad touch controls, anything?)
- I see there's unofficial cyanogenmod support, is there anything not working? (gps, camera, nfc? threads don't seem to mention anything broken, is it omitted or there isn't anything to fix?)
- Anything I should do other than read the stickies? Samsung phones have a very important and easily corrupted EFS folder, so I'm on the lookout for anything like this on my next purchase.
Any answers will be greatly appreciated.
Choristav said:
Hey guys, I have to ask:
- Does this device have a bootloader lock such as sony smartphones when purchased from a carrier?
- Is there any sudden death/current bugs/defects I should look out for? (tinted screen, broken hardware buttons, bad touch controls, anything?)
- I see there's unofficial cyanogenmod support, is there anything not working? (gps, camera, nfc? threads don't seem to mention anything broken, is it omitted or there isn't anything to fix?)
- Anything I should do other than read the stickies? Samsung phones have a very important and easily corrupted EFS folder, so I'm on the lookout for anything like this on my next purchase.
Any answers will be greatly appreciated.
Click to expand...
Click to collapse
If you use autorec it will flash the JB boot loader, and a custom recovery (TWRP) so you can flash ROMs and what not. The only thing I've heard about hardware defects are lines on the screen. Vertical, horizontal and screen spasms altogether. When it comes to cyanogen, I've never used it on this phone. Unless you're one of those must-have-aosp sorta guys, stock ROMs are the way to go. On the other hand, I did use Mahdi for awhile and it was awesome.
Sent From The Trail Of Untold Truths
- Does this device have a bootloader lock such as sony smartphones when purchased from a carrier?
It has a locked bootloader, yes.
- Is there any sudden death/current bugs/defects I should look out for? (tinted screen, broken hardware buttons, bad touch controls, anything?)
Yes there is. Check the screen. On some phones, the digitizer randomly stops working. Often occurs after a drop.
Check for something like this or something like this.
- I see there's unofficial cyanogenmod support, is there anything not working? (gps, camera, nfc? threads don't seem to mention anything broken, is it omitted or there isn't anything to fix?)
I wouldn''t say "Not working" as much as I'd say not working properly. Camera performance on AOSP is generally horrible and more often than not, a Stock based rom would be the way to go =)
- Anything I should do other than read the stickies? Samsung phones have a very important and easily corrupted EFS folder, so I'm on the lookout for anything like this on my next purchase.
The G2 also has an important EFS partition. It's not as easily corrupted, but make sure you have a backup of it at least.
Don't drop the phone, the digitzer is glued to the LCD - if the screen cracks, your digitizer dies.
vPro97 said:
snip
Click to expand...
Click to collapse
Is it possible to unlock the bootloader?
I'm a sucker for AOSP, do you mean the camera has worse quality (as the stock has more options), or does it randomly stop working? Coming from an i9300 I thought this device would have all the necessary sources available for development, or is LG a bad company towards developers?
Also, is anyone compiling AOSP roms with linaro for this phone?
Choristav said:
Is it possible to unlock the bootloader?
I'm a sucker for AOSP, do you mean the camera has worse quality (as the stock has more options), or does it randomly stop working? Coming from an i9300 I thought this device would have all the necessary sources available for development, or is LG a bad company towards developers?
Also, is anyone compiling AOSP roms with linaro for this phone?
Click to expand...
Click to collapse
I'll advise you to go for a Nexus 5, One Plus One or wait for something with tons of development for AOSP ROMs like the two I mentioned.
Also there is a risk of permanent black lines that happens to some G2 owners, its suspected that heat is the cause but if it happens to you while flashing you'll have to RMA the phone.
There is a workaround for the locked bootloader. The camera quality is worse on AOSP cause the drivers for the camera are closed source. Development on AOSP ROMs is slow. Best option is stick to stock or stock based ROMs
Sent from my LG-D802 using Tapatalk
Choristav said:
Hey guys, I have to ask:
- Does this device have a bootloader lock such as sony smartphones when purchased from a carrier?
- Is there any sudden death/current bugs/defects I should look out for? (tinted screen, broken hardware buttons, bad touch controls, anything?)
- I see there's unofficial cyanogenmod support, is there anything not working? (gps, camera, nfc? threads don't seem to mention anything broken, is it omitted or there isn't anything to fix?)
- Anything I should do other than read the stickies? Samsung phones have a very important and easily corrupted EFS folder, so I'm on the lookout for anything like this on my next purchase.
Any answers will be greatly appreciated.
Click to expand...
Click to collapse
thanks for asking this question my friend
i just wanted to add :
- how is the over all experience comparing it with samsung - htc devices , i have been using both of them for a while ( i dont like build material in samsung and update process with htc - i read that lg is making progress in this direction ).
- how does it feel after a while like the size,shape, build quality including overall performance .
im very close to buy one but im afraid a little bit - never owned an lg smartphone.
best regard from me
- Does this device have a bootloader lock such as sony smartphones when purchased from a carrier?
Click to expand...
Click to collapse
yes it does have a locked bootloader but that has not stopped us from getting recovery/roms/kernels/etc; we use a an exploit in the aboot to bypass the locked bootloader so there is nothing to worry about
- Is there any sudden death/current bugs/defects I should look out for? (tinted screen, broken hardware buttons, bad touch controls, anything?)
Click to expand...
Click to collapse
none that I am aware of as a shipping device, but if you are an avid flasher(as in you love to constantly flash something new) than you need to be careful because there is permanent screen damage issue which you can read more about here
- I see there's unofficial cyanogenmod support, is there anything not working? (gps, camera, nfc? threads don't seem to mention anything broken, is it omitted or there isn't anything to fix?)
Click to expand...
Click to collapse
I am not sure which device(different g2 variants get different roms) you may be planning on getting but already have full official support and everything is working; although experience with aosp is not the best if you get use to the lg stock experience there are actually some great aosp roms(better experience than cm anyways)
- Anything I should do other than read the stickies? Samsung phones have a very important and easily corrupted EFS folder, so I'm on the lookout for anything like this on my next purchase.
Click to expand...
Click to collapse
you can check out the g2 help thread second post which I link some very useful threads(including info on backing up efs)
- how is the over all experience comparing it with samsung - htc devices , i have been using both of them for a while ( i dont like build material in samsung and update process with htc - i read that lg is making progress in this direction ).
Click to expand...
Click to collapse
I came from an sgs 3 and in the family my parents always getting a Samsung in overall I prefer the look and feel of the g2 but the screen is one of my bad points, it is full glass and very easy to break so I suggest getting a case as a priority and as one of the members pointed out the lcd/digitizer are glued together and it is pretty much impossible to get them separated so replacing is tedious
- how does it feel after a while like the size,shape, build quality including overall performance .
Click to expand...
Click to collapse
I came from a generation of small devices since before the sgs3(biggest device I had prior to the g2) I had a lot small devices so getting used to a bigger device was little but difficult but rather quickly and the button placement/knock on and knock code is a great feature and before you know it you will be knocking on all your devices(I spent about a month like that)
build quality is okay for a plastic device it feels nice but it definitely needs a cover to maintain it safe
performance is great, I never experienced any lag; camera took some great pics(in the day because low light performance is bad) and after rooting and installing the modded camera you will enjoy all the improvements in day/low light scenarios; and I use the phone for lots of gaming specifically emulators, so I was able to average about 20 hours a day with heavy ppsspp usage so both performance and battery life are killer
these are all a point of view from a zombiepikachu who is a gamer and lg based roms user and my point of view/experience may differ from others
XxZombiePikachu said:
snip
Click to expand...
Click to collapse
Any roms I should look out for, then?
I'm looking for as AOSP-wise as possible, touchwiz left me a horrible taste and now I've seen this LG phone has this huge quick selection thing in the notification area.
Choristav said:
Any roms I should look out for, then?
I'm looking for as AOSP-wise as possible, touchwiz left me a horrible taste and now I've seen this LG phone has this huge quick selection thing in the notification area.
Click to expand...
Click to collapse
well for aosp many users like mahdi-rom but you can also check out the g2 original dev thread(basically everything aosp) like I mentioned I am a stock user so I don't really touch the aosp side of the g2
Choristav said:
Any roms I should look out for, then?
I'm looking for as AOSP-wise as possible, touchwiz left me a horrible taste and now I've seen this LG phone has this huge quick selection thing in the notification area.
Click to expand...
Click to collapse
lots of aosp choices.. AICP, Mahdi, Liquidsmooth, Vanir, Slimkat etc that i can name of ... u'll be ruined with choices mate..
XxZombiePikachu said:
yes it does have a locked bootloader but that has not stopped us from getting recovery/roms/kernels/etc; we use a an exploit in the aboot to bypass the locked bootloader so there is nothing to worry about
none that I am aware of as a shipping device, but if you are an avid flasher(as in you love to constantly flash something new) than you need to be careful because there is permanent screen damage issue which you can read more about here
I am not sure which device(different g2 variants get different roms) you may be planning on getting but already have full official support and everything is working; although experience with aosp is not the best if you get use to the lg stock experience there are actually some great aosp roms(better experience than cm anyways)
you can check out the g2 help thread second post which I link some very useful threads(including info on backing up efs)
I came from an sgs 3 and in the family my parents always getting a Samsung in overall I prefer the look and feel of the g2 but the screen is one of my bad points, it is full glass and very easy to break so I suggest getting a case as a priority and as one of the members pointed out the lcd/digitizer are glued together and it is pretty much impossible to get them separated so replacing is tedious
I came from a generation of small devices since before the sgs3(biggest device I had prior to the g2) I had a lot small devices so getting used to a bigger device was little but difficult but rather quickly and the button placement/knock on and knock code is a great feature and before you know it you will be knocking on all your devices(I spent about a month like that)
build quality is okay for a plastic device it feels nice but it definitely needs a cover to maintain it safe
performance is great, I never experienced any lag; camera took some great pics(in the day because low light performance is bad) and after rooting and installing the modded camera you will enjoy all the improvements in day/low light scenarios; and I use the phone for lots of gaming specifically emulators, so I was able to average about 20 hours a day with heavy ppsspp usage so both performance and battery life are killer
these are all a point of view from a zombiepikachu who is a gamer and lg based roms user and my point of view/experience may differ from others
Click to expand...
Click to collapse
thanks bro for your input
---------- Post added at 12:42 PM ---------- Previous post was at 12:40 PM ----------
zekurosu said:
lots of aosp choices.. AICP, Mahdi, Liquidsmooth, Vanir, Slimkat etc that i can name of ... u'll be ruined with choices mate..
Click to expand...
Click to collapse
whats your opinion my friend ( as it seems you had quite some phones )
my personal choice now would be AICP :good:
hi
i just wanted to add that i bought the phone and im glad i did.
great battery life
the screen is great too
a great idea with knock code and power & volume buttons
camera quality could have been better
i just hope i dont get touch screen issues
even better being in xda-developers community
best regards from me...
Hi Guys,
I noticed that there are more than one threads about this problem so I want to try collecting some information about it and see how many users affected by it. The purpose of this thread and poll is to take the outcome and contact LG and some Tech news websites, making LG respond to this issue ASAP.
If you not sure about having this issue, you can check it as follows (it worked for me) -
1. Open the Dialer and enter 277634#*# to enter the Service Menu.
2. Go to Device Test -> Service Menu - Manual Test -> Touch Draw Test - Manual.
3. Now touch/tap/knock/slide on the test area (all of it) until its almost full and watch for missing registration (you will touch the screen and there will be no red mark). I repeated the test several times and almost every time I had misses.
You can add the device model (H815/H815x/H812/H811/H810/LS991/VS986/US991) and more information in the comments .
I have the international H815 and this issue killing my Knock Code experience (Had the G3 without any issue).
Thanks :good:
Edit:
I found a video that demonstrate the issue (it's not my making, but I do have the same issue) .
The app in the video is Multitouch Test and can be download here -
https://play.google.com/store/apps/details?id=multitouchpro.tests
Another video demonstrating the issue (G4 on the left and G3 on the right) -
Another test by coolmaster121
Edit #2:
I sent emails to some Tech news websites, here is the first reports (thank you Android Authority and GsmArena!) -
http://www.androidauthority.com/lg-g4-touchscreen-issues-616662/
http://www.gsmarena.com/lg_g4_reportedly_facing_touchscreen_issues-news-12651.php
http://www.phonearena.com/news/Issues-with-the-LG-G4-touchscreen-prevent-quick-taps-and-touches-from-registering-on-the-screen_id70436
Update [6/18]:
According to Android Police LG US knows about the problem and they're looking into it.
http://www.androidpolice.com/2015/06/16/having-touchscreen-problems-with-your-lg-g4-lg-knows-and-theyre-looking-into-it/
Keep posting your experience and updates until they will issue a fix. :good:
That service menu option doesn't work for me On the H810 AT&T variant.
I am still getting missed taps. Debating swapping phones when I get back from work travel. It's very random when it will occur.
liamR said:
Hi Guys,
I noticed that there are more than one threads about this problem so I want to try collecting some information about it and see how many users affected by it. The purpose of this thread and poll is to take the outcome and contact LG and some Tech news websites, making LG respond to this issue ASAP.
If you not sure about having this issue, you can check it as follows (it worked for me) -
1. Open the Dialer and enter 277634#*# to enter the Service Menu.
2. Go to Device Test -> Service Menu - Manual Test -> Touch Draw Test - Manual.
3. Now touch/knock/slide on the test area (all of it) until its almost full and watch for missing registration (you will touch the screen and there will be no red mark). I repeated the test several times and almost every time I had misses.
You can add the device model (H815/H815x/H812/H811/H810/LS991/VS986/US991) and more information in the comments .
Thanks :good:
Click to expand...
Click to collapse
Device Test is missing from my Service menu on H811
Maybe you can try 3845#*Model# (ex: 3845#*811#).
I have the VS986 version and I have a Mime tempered glass protector.
Noticing miss taps and the scrolling isn't fluid very choppy.
I've noticed a few missed taps, and I don't have anything on the screen.
it is happening on all lg g4s currently. im sure there will be a bug fix soon. maybe when we move up to 5.1.1
jerflash said:
it is happening on all lg g4s currently. im sure there will be a bug fix soon. maybe when we move up to 5.1.1
Click to expand...
Click to collapse
I don't have any issues on my TMO variant though.
jerflash said:
it is happening on all lg g4s currently. im sure there will be a bug fix soon. maybe when we move up to 5.1.1
Click to expand...
Click to collapse
I really hope so. Maybe if they will see it's a major issue they will come out with a fix asap. For now they're (LG) saying they don't know about it and there aren't complaints from users.
LG will claim they don't know about it until we raise a storm on social media, support cases, etc. So we need to organize an effort to make things happen.
Mine's not severe, on the edges, more than anything. Most noticeable when typing "p". I know it's there so I watch for it. Other pretty solid device for me (other than no Gmail notifications, but I'm not posting about that).
Mine has the problem. About to return it.
I just opened up a case with LG.
You should contact them via their live chat and reference the following case number. The more people report this, the faster we'll hear a response back. I really don't want to return this phone.
CASE# CNM150609024049
http://www.lg.com/us/support
Really annoying..thought it was my screen protector at first
Sent from my VS986 using Tapatalk
I came from the S6 and I have noticed it as well. I really hope its something that LG addresses.. I want to keep this phone, but its pretty annoying when it happens..
I just sent mine back in today for this issue. No screen protector on mine. I have to decide if I want to go buy a replacement G4, or...something else. *dun-dun-duuuuuuunnnnnn*
I have had two G4s so far, both brand new from Tmobile. Both have this issue. I purchased one when it was released and the other one 6/8.
Is it possible that the people who are saying that this is not an issue are not seeing or noticing it, but it is still there?
Because if there is an issue with the display, and not all of the units are having it, then this is a Hardware defect, and cannot fully be fixed with software.
I just came from the s5, before that s4, and i thought i was just not used to an ips touchscreen but then i found this thread so i will try op
coolmaster121 said:
I have had two G4s so far, both brand new from Tmobile. Both have this issue. I purchased one when it was released and the other one 6/8.
Is it possible that the people who are saying that this is not an issue are not seeing or noticing it, but it is still there?
Because if there is an issue with the display, and not all of the units are having it, then this is a Hardware defect, and cannot fully be fixed with software.
Click to expand...
Click to collapse
That's my thoughts exactly. I really like this smartphone, but this issue is a deal breaker for me. I really hope that it's just software fix. I'm not planning to return it for now for replacement as I'm pretty sure that every device is affected (if it's hardware issue, from past experience we need to wait a few weeks or months for fixed batches). I'll give it some time and see what LG doing about it...
I have used a tempered glass on my G4 from minute 1, and i notice a very, very, very slight version of this issue, where taps sometimes dont register. it is very slight however, which makes me wonder maybe LG has set the touchscreen sensitivity a tad bit too low, and it could be fixed with an update. Its definitely not a hardware issue, as so many people are affected, and these screens get tested before production with like 5000 taps per minute by testing machines (seen from youtube videos).
Our axon 7 uses a 240hz pwm to adjust brightness. In the s7 forum a developer solves this by modding the kernel:
https://forum.xda-developers.com/s7-edge/development/amoled-pwm-s7-edge-t3517739/
themostunique said:
Our axon 7 uses a 240hz pwm to adjust brightness. In the s7 forum a developer solves this by modding the kernel:
https://forum.xda-developers.com/s7-edge/development/amoled-pwm-s7-edge-t3517739/
Click to expand...
Click to collapse
I agree. Devs of Lineage OS can perhaps add this?
i Support this idea, we need it.
themostunique said:
Our axon 7 uses a 240hz pwm to adjust brightness. In the s7 forum a developer solves this by modding the kernel:
https://forum.xda-developers.com/s7-edge/development/amoled-pwm-s7-edge-t3517739/
Click to expand...
Click to collapse
I also would like to see such improvement in our device!
+1
maybe @genesixxbf3 could integrate it in Llama Sweet Kernel
and @Unjustified Dev or @OrdenKrieger in LineageOS 14.1. and coming 15 also
Thx for this @themostunique
yeah thats one of the things that always bothered me if it could be implemented not only on LOS or customs ROMs but also on stock ones specially the upcoming oreo
Lets hope LOS 15 will have this thing/improvement&tweak added
I really wish someone could achieve this mod for our Axon 7. The PWM on this device is unbearable and I decided it wasn't worth the constant headaches and eyestrain, so I've kept mine in a drawer for the past 7-8 months and used my ZUK Z2 instead.
I found someone who made this mod for the Samsung Galaxy S8: https://forum.xda-developers.com/galaxy-s8+/development/amoled-pwm-s8-t3716663
P650SE said:
I really wish someone could achieve this mod for our Axon 7. The PWM on this device is unbearable and I decided it wasn't worth the constant headaches and eyestrain, so I've kept mine in a drawer for the past 7-8 months and used my ZUK Z2 instead.
I found someone who made this mod for the Samsung Galaxy S8: https://forum.xda-developers.com/galaxy-s8+/development/amoled-pwm-s8-t3716663
Click to expand...
Click to collapse
I can only support your wish, but few people in custom scene care about health mods... What a pity...
This one needs a talented kernel dev like @Kranoner, who looked into it but found it to lot pf a hassle to do it specially as it needs also some blob stuff... And obviously he left the scene by now like @NFound
Maybe @SaintZ93 can take a look into it and integrate in his Schwifty kernel
Or even @OrdenKrieger and @Unjustified Dev could integrate it into future LOS releases what would have the benefit to have it on all other ROMs bases on LOS right out of the box...
Or maybe @Oki get's enthusiastic about it and takes this as his new challenge after finishing his TWRP mods...
But then again... Who cares about health these days anyway... Really sad that such mods don't have the attention they earn. So let's just hope and be positive!
Legends like @Chainfire used to develop health solutions that even found their way in official releases by now... Like blue light and warm color filters during night time that he pioneered with his cf.lumen that I still use till today as I didn't find anything more advanced and customisable then his tool, altough it became standard in official android releases by now and his tool was last updated 18 months ago
Gachmuret said:
I can only support your wish, but few people in custom scene care about health mods... What a pity...
This one needs a talented kernel dev like @Kranoner, who looked into it but found it to lot pf a hassle to do it specially as it needs also some blob stuff... And obviously he left the scene by now like @NFound
Maybe @SaintZ93 can take a look into it and integrate in his Schwifty kernel
Or even @OrdenKrieger and @Unjustified Dev could integrate it into future LOS releases what would have the benefit to have it on all other ROMs bases on LOS right out of the box...
Or maybe @Oki get's enthusiastic about it and takes this as his new challenge after finishing his TWRP mods...
But then again... Who cares about health these days anyway... Really sad that such mods don't have the attention they earn. So let's just hope and be positive!
Legends as @Chainfire used to develop health solutions that even found their way in official releases by now... Like blue light and warm color filters during night time that he pioneered with his cf.lumen that I still use till today as I didn't find anything more advanced and customisable then his tool, altough it became standard in official android releases by now and his tool was last updated 18 months ago
Click to expand...
Click to collapse
I have looked into this and to me it is not worth all the struggle it really is to implement it into our kernels. Literally have to re-write the entire display files because thats based on samsung files, we would have to convert it to the zte files. Proper blob edits are needed, as well as device tree related files. This is something that could take months to do and no offense but I will pass on that. Maybe some of the other devs might, but they have more important stuff to fix/make.
Edit: However I'll keep an eye on it from time to time and see how it produces.
Gachmuret said:
I can only support your wish, but few people in custom scene care about health mods... What a pity...
Click to expand...
Click to collapse
You really don't need to tag everyone you can think of. The point is to bring a post to someone's attention who might not have a subscription to the thread. Unless you think Chainfire (who has nothing to do with this phone) or NFound (who bailed when he couldn't ransom his ROMs for more money) will do something for you, best not bother them.
Do you know what the default PWM frequency is set to? I don't recall it being looked into yet, but I may have missed it. That Galaxy S8 mod states the default GS8 PWM freq is 240, which is indeed far too low.
If you or anyone else who would like this to be implemented could look into what exactly is going on with the Axon 7 screen currently and what needs to be ported, it might help along your request.
Masterjuggler said:
Do you know what the default PWM frequency is set to? I don't recall it being looked into yet, but I may have missed it. That Galaxy S8 mod states the default GS8 PWM freq is 240, which is indeed far too low.
If you or anyone else who would like this to be implemented could look into what exactly is going on with the Axon 7 screen currently and what needs to be ported, it might help along your request.
Click to expand...
Click to collapse
Well, just look at the OP it says it is also 240:
themostunique said:
Our axon 7 uses a 240hz pwm to adjust brightness. In the s7 forum a developer solves this by modding the kernel:
https://forum.xda-developers.com/s7-edge/development/amoled-pwm-s7-edge-t3517739/
Click to expand...
Click to collapse
But I didn't measure it by myself... So maybe @themostunique can shed some light onto this
---------- Post added at 03:12 AM ---------- Previous post was at 02:38 AM ----------
SaintZ93 said:
I have looked into this and to me it is not worth all the struggle it really is to implement it into our kernels. Literally have to re-write the entire display files because thats based on samsung files, we would have to convert it to the zte files. Proper blob edits are needed, as well as device tree related files. This is something that could take months to do and no offense but I will pass on that. Maybe some of the other devs might, but they have more important stuff to fix/make.
Edit: However I'll keep an eye on it from time to time and see how it produces.
Click to expand...
Click to collapse
Thank you for actually looking at it!
Could it be of any help for any dev that our device has the same display as the Google Pixel XL (Marlin) and is manufactured by Samsung with model nr S6E3HA3
ChazzMatt said:
Same 1440p AMOLED display as Pixel XL
YES, the Pixel XL and the ZTE Axon 7 use the exact same 1440p AMOLED Samsung panel.
New Leaks Highlight Nexus Marlin Details (Pixel XL)
https://www.xda-developers.com/151309-2/
Click to expand...
Click to collapse
I have a v20 h918 running super v20. On the latest update (4.0) im experiencing ghosting on the screen (looks like burn-in but isn't permanent). I'm asking about this issue in general because it isn't an issue specifically related to this rom, but an issue I've seen reported on completely stock Tom's too. I believe it fades to a degree while the phone is still powered on, but a reboot clears it right up. I've seen the people trying to insist it being a hardware issue, but in all cases I've seen, it's been experienced after an update (stock or otherwise). This ghosting occurs after still images are on the screen from 30 seconds to a couple of minutes at most, not the time to cause any real burn-in. I'm just trying to find some real answers from others who have experienced it, not someone taking guesses. It's not hardware related. Its appearance coincides with software updates, and its appearance isn't permanent. But it is annoying as hell. Any help?
Genaugmen101 said:
I have a v20 h918 running super v20. On the latest update (4.0) im experiencing ghosting on the screen (looks like burn-in but isn't permanent). I'm asking about this issue in general because it isn't an issue specifically related to this rom, but an issue I've seen reported on completely stock Tom's too. I believe it fades to a degree while the phone is still powered on, but a reboot clears it right up. I've seen the people trying to insist it being a hardware issue, but in all cases I've seen, it's been experienced after an update (stock or otherwise). This ghosting occurs after still images are on the screen from 30 seconds to a couple of minutes at most, not the time to cause any real burn-in. I'm just trying to find some real answers from others who have experienced it, not someone taking guesses. It's not hardware related. Its appearance coincides with software updates, and its appearance isn't permanent. But it is annoying as hell. Any help?
Click to expand...
Click to collapse
It's been an issue since the phone was released, the best solution is to run a custom kernel that supports kcal and adjusting the screen settings to eliminate it
Sent from my LG-H910 using XDA Labs
cnjax said:
It's been an issue since the phone was released, the best solution is to run a custom kernel that supports kcal and adjusting the screen settings to eliminate it
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Ive tried adjusting screen settings, but it really makes no difference. I can achieve the same amount of improvement but just keeping the brightness minimized. As for it being an issue with the phone itself, I beg to differ. This is the lazy man's answer. It doesn't conform with the fact that it seems to appear with software updates instantly. That's not indicative of a hardware issue. I've never seen it before until immediately after a software update. This isn't a minor problem that got worse, it's an issue which appears instantly, and isn't permanent like burn-in. This is partial retention of previous images on screen which has to be software related because a reboot will remove all signs of it from the screen. I've used my phone at full brightness for extended periods and have never had any sign of this.
Genaugmen101 said:
Ive tried adjusting screen settings, but it really makes no difference. I can achieve the same amount of improvement but just keeping the brightness minimized. As for it being an issue with the phone itself, I beg to differ. This is the lazy man's answer. It doesn't conform with the fact that it seems to appear with software updates instantly. That's not indicative of a hardware issue. I've never seen it before until immediately after a software update. This isn't a minor problem that got worse, it's an issue which appears instantly, and isn't permanent like burn-in. This is partial retention of previous images on screen which has to be software related because a reboot will remove all signs of it from the screen. I've used my phone at full brightness for extended periods and have never had any sign of this.
Click to expand...
Click to collapse
First complaining here about it isn't going to fix it you need to be going to the source.. LG. I simply stated what has been known since the release of the phone and the best resolution agreed on as the best fix by the majority on this forum. My response wasn't lazy, it was reality. Using kcal to set screen settings values I have never seen ghosting or retention on my phone. Therefore you have been given the fix twice now if you don't like it, then take your issue up with LG
Sent from my LG-H910 using XDA Labs
cnjax said:
It's been an issue since the phone was released, the best solution is to run a custom kernel that supports kcal and adjusting the screen settings to eliminate it
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Sir plz m new to flashing LG phones , have developed serious image retention on my lg v20 h91810u ( bootloader locked not rooted) i am ready to flash custom rom with kcal supported kernel , sir plz guide me to the rom and kernel
Also guide me to unlock boot and root my phone
Thanks
Here's link
pawar21 said:
Sir plz m new to flashing LG phones , have developed serious image retention on my lg v20 h91810u ( bootloader locked not rooted) i am ready to flash custom rom with kcal supported kernel , sir plz guide me to the rom and kernel
Also guide me to unlock boot and root my phone
Thanks
Click to expand...
Click to collapse
https://www.google.com/amp/s/amp.re...ile_v20_with_software_h91810u/#ampf=undefined
it is permanent burn in...
Its LG's trash "ips quantum dot" tech. The screen in this phone (display and touch hardware) is a complete poop show.
I bought a refurbished v20 at a lower price from the market. It was working fine until a few days back that image ghosting is becoming quite an issue for me. If ANY app is opened and stays open for 10mins or more, the text and bars of the app starts becoming visible on the home screen. I read many articles for this issue on xda and internet. Some saying to use the sfilter and some suggesting to use a custom rom with KCAL support. Well i am not a custom rom type of person as i am not tech savvy and don't want to mess up with my phone. I tried the sfilter though but it didn't help at all.
The ghosting goes away after i turn off the screen for 10mins or more but this issue is annoying me. I have NOT updated to oreo yet, and it is still running on noughat. I haven't updated anything except the play store apps. Please help me what should i do to get rid of this issue.
(i really love this phone but due to this i am planning to sell it and buy some else brand after being a loyal LG user).
Only way to remove the screen retention is to root the phone. I've had every American variant of the V20 and they all get screen retention but luckily it's easily solvable but you must go through the rooting process. I hope you can find a day off and dedicate it entirely to unlocking bootloader/root/TWRP/Oreo Update your V20. It's definitely worth it and not too hard, hopefully you have the H918 T-Mobile variant... Cuz all the work to solve your problem is very easy but takes time.
Andy Chi said:
Only way to remove the screen retention is to root the phone. I've had every American variant of the V20 and they all get screen retention but luckily it's easily solvable but you must go through the rooting process. I hope you can find a day off and dedicate it entirely to unlocking bootloader/root/TWRP/Oreo Update your V20. It's definitely worth it and not too hard, hopefully you have the H918 T-Mobile variant... Cuz all the work to solve your problem is very easy but takes time.
Click to expand...
Click to collapse
Well its a long story about the phone model/software version. When i got the phone it had h910 rom installed and i thought it is the at&t version. I kept using it and at&t rom has a huge drawback that it shows the carrier name in the taskbar and it covered almost 60% of the space. I searched on xda and everywhere else, and got to know that i can easily convert it to us996 and everything will be solved. I did it but then lost the gsm signals. Finally i gave up, fearing that i might worsen the situation with hard brick. So, i took it to a guy in software market and when he connected the phone with some software, it said that it is not h910 at all but instead an f800k Korean version. He installed the f800k and everything started working perfectly fine.
Now that i have gone through this much problem, i am scared. I have searched for answers about this ghosting everywhere on the web. I found from answers:
1. ghosting can be removed with any custom rom
2. those custom rom which have kcal support will only be able to solve this issue.
3. only lineage os has the oreo version but then they lack second screen support.
please correct me if i am wrong in above 3 things.
Now in light of this all, what do you suggest to do? And please guide me the steps you did to complete the process. I would really be thankful if you post the working links/videos url for the whole process involving unlocking bootloader, rooting, twrp and then custom rom.
I hope i am not being a pain to you. I am sincerely and seriously asking your help.
awaisagha said:
Well its a long story about the phone model/software version. When i got the phone it had h910 rom installed and i thought it is the at&t version. I kept using it and at&t rom has a huge drawback that it shows the carrier name in the taskbar and it covered almost 60% of the space. I searched on xda and everywhere else, and got to know that i can easily convert it to us996 and everything will be solved. I did it but then lost the gsm signals. Finally i gave up, fearing that i might worsen the situation with hard brick. So, i took it to a guy in software market and when he connected the phone with some software, it said that it is not h910 at all but instead an f800k Korean version. He installed the f800k and everything started working perfectly fine.
Now that i have gone through this much problem, i am scared. I have searched for answers about this ghosting everywhere on the web. I found from answers:
1. ghosting can be removed with any custom rom
2. those custom rom which have kcal support will only be able to solve this issue.
3. only lineage os has the oreo version but then they lack second screen support.
please correct me if i am wrong in above 3 things.
Now in light of this all, what do you suggest to do? And please guide me the steps you did to complete the process. I would really be thankful if you post the working links/videos url for the whole process involving unlocking bootloader, rooting, twrp and then custom rom.
I hope i am not being a pain to you. I am sincerely and seriously asking your help.
Click to expand...
Click to collapse
All you need is root to flash a kernel that supports kcal you can then adjust the screen values to lessen and reduce ghosting.
Sent from my LG-H910 using XDA Labs
cnjax said:
All you need is root to flash a kernel that supports kcal you can then adjust the screen values to lessen and reduce ghosting.
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
You mean even with custom rom, this cannot be avoided TOTALLY. It will happen but just because of kcal its effects can be reduced? Am i right?
awaisagha said:
You mean even with custom rom, this cannot be avoided TOTALLY. It will happen but just because of kcal its effects can be reduced? Am i right?
Click to expand...
Click to collapse
A rom has nothing to with kcal, in order to use kcal you have to have a kernel that supports it. Yes otherwise why would we be telling you what to do
Sent from my LG-H910 using XDA Labs
Before going down that road of unlocking and rooting, try installing the sfilter app. Set opacity to like 10% on the color black. Give it a few hours to notice the ghosting to go away. If I don't use the sfilter app I get crazy ghosting on both my V20 and V10.
If you don't believe me just Google sfilter app and lg V20.
It's not fixing the real issue, which is probably the display getting hot from the CPU, but it masks it and makes it not noticable.
After a while you can probably dial down the 10% to like 5. Personally mine is at 3%.
Sent from my LG-H918 using Tapatalk
[/COLOR]Thanks God! It really works, thanks for saving my phone, screen looks great now.
gustav30 said:
Before going down that road of unlocking and rooting, try installing the sfilter app. Set opacity to like 10% on the color black. Give it a few hours to notice the ghosting to go away. If I don't use the sfilter app I get crazy ghosting on both my V20 and V10.
If you don't believe me just Google sfilter app and lg V20.
It's not fixing the real issue, which is probably the display getting hot from the CPU, but it masks it and makes it not noticable.
After a while you can probably dial down the 10% to like 5. Personally mine is at 3%.
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
Try running this video
I don't have a rooted phone but I set the brightness to auto and use the phone in comfort mode.
I use an extended battery (iPosible) which keeps the phone from getting hot. I'll try this sFilter blue screen app too