Related
Is there a known issue here with newer evo's vs older. Bought hers last december and mine was from the july before. In recovery, it says we have the exact same specs and versions. Her flash is noticeably stronger and takes much clearer pics. Very frustrating. Her screen seems to be a slightly different shade as well. Just wondering if there was anything I can do with the flash. Thanks
Recovery won't tell you anything. In as Sense-based ROM, go to menu > settings > about phone > hardware information to see the differences between yours and your wife's phone.
Honestly, I don't think there's anything you can do about the flash, as I don't have any experience opening up an Evo 4G and tinkering with the parts. Although, I'm sure the devs around here have a solution.
I had a newer evo with the 0004 hardware version and just had to take it to sprint and i got a refurbished Evo 4g with hardware 0002 and i noticed the screen was a different shade as well.
Sent from my PC36100 using xda premium
As far as the flash goes, not sure anything can be done about that. Different hardware versions have different camera hardware.
As far as the screens go, there are two different screen manufacturers, Epson and Novatech. The Nova's tend to be a bit brighter and have a cooler tone to them. The Epson's tend to have a tad lighter brightness, and have a warmer tone to the whites.
The softkey glow animation causes unnecessary lag on pretty much every device other than the transformer prime in my experience and even there its not perfect. I don't get why this animation was added in ICS. I wasn't part of honeycomb. My rom I use on my nexus has it off by default (winner00's cm9 kang) but its fraustrating that stock this phone even has this animation. It causes so much extra lag that the phone doesn't need and the animation looks like crap most of the time anyway. The most obvious times I see this lag are when hitting the back button from the app drawer, and hitting the back button with the notification draw open. With the animation its unsmooth on both things. With the animation off or removed both of those animations are 60fps. Google removed the menu selection fade in 4.04, I think its time that they remove this one as well, or at least make it standard in all cm9 roms as my friends touchpad still has this animation. AOKP has an option to remove it but in my experience that rom has some weird lag issues when closing the app drawer anyway.
The problem with this being standard turned on is the stock roms for many devices like the Asus Tranformer tf101 have this glowing animation and it causes lag. Its a bad precedent to set.
Does it really matter what the default option is? You know there's an option to turn it off, so use it. I personally like the animation, running on AOKP and it's glass smooth all the time.
The point of a custom rom is to give you extra options and performance... not to completely alter the way the phone behaves (unless you're going to MIUI, but if you're doing that you know that you're going to get drastic changes). When i install a custom ROM, i expect that all the defaults will have my phone working just as it did when it was on stock - from there, i can customize to my liking.
I remember when the Nexus One came out, and shortly after that Google decided to implement Live Wallpapers. Every time you enabled a live wallpaper the home screen lagged, and to top it off it would eat your battery life to keep it running. Then a year later the next generation of phones came out and live wallpapers were no longer a problem.
Google always implements unnecessary eye candy that bogs down your phone. It's a way to show people the difference that it makes to upgrade your hardware every one or two years, because you can pretty much guarantee that this year's new phones will have absolutely no difficulty running little touches like this, whereas last year's phones will chug.
Most consumers don't care if it's laggy. They see the glowing buttons and think it's the best thing since sliced bread, since neither the iPhone nor WP7 have it. Then once the next Nexus comes out they'll see even more button effects and spend even more money on it.
Don't get butthurt just because you're not the target audience.
earlyberd said:
I remember when the Nexus One came out, and shortly after that Google decided to implement Live Wallpapers. Every time you enabled a live wallpaper the home screen lagged, and to top it off it would eat your battery life to keep it running. Then a year later the next generation of phones came out and live wallpapers were no longer a problem.
Google always implements unnecessary eye candy that bogs down your phone. It's a way to show people the difference that it makes to upgrade your hardware every one or two years, because you can pretty much guarantee that this year's new phones will have absolutely no difficulty running little touches like this, whereas last year's phones will chug.
Most consumers don't care if it's laggy. They see the glowing buttons and think it's the best thing since sliced bread, since neither the iPhone nor WP7 have it. Then once the next Nexus comes out they'll see even more button effects and spend even more money on it.
Don't get butthurt just because you're not the target audience.
Click to expand...
Click to collapse
The problem is, unlike live wallpapers, unless your rom added an option to turn this off, there is no way to do so. There is no way to turn this option off on the stock rom and many builds of cm9 don't have an option either. If you haven't tried winner00's cm9 if your on the verizon nexus, try it. The difference is hugely noticeable. AOKP in my experience seems to have lag in the app drawer even with the glow animaton off regardless of which launcher you use.
Agreed. The choppy animation drives me crazy. I'm 100% stock and proud but I might go back to the dark side and flash a custom rom because of this.
Surely this is easily fixable for Google and they are aware of the problem.
Sent from my Galaxy Nexus using XDA
No lag at all for me running Apex rom
Sent from my Galaxy Nexus using Tapatalk 2
Lol. I'm on 4.0.4 IMM76I and the animation is completely fluid. Why do you even care about the key glow? I don't even look at the keys when using the phone
Sent from my Galaxy Nexus using XDA
blockbusta said:
Lol. I'm on 4.0.4 IMM76I and the animation is completely fluid. Why do you even care about the key glow? I don't even look at the keys when using the phone
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I want the glow gone lol.
Heres a comparison video of cm9 kang(winner00) which doesn't have the glow and official cm9 build 5-7 that has the glow.
http://www.youtube.com/watch?v=4Y7HwdKmvtk&feature=youtube_gdata
earlyberd said:
I remember when the Nexus One came out, and shortly after that Google decided to implement Live Wallpapers. Every time you enabled a live wallpaper the home screen lagged, and to top it off it would eat your battery life to keep it running. Then a year later the next generation of phones came out and live wallpapers were no longer a problem.
Google always implements unnecessary eye candy that bogs down your phone. It's a way to show people the difference that it makes to upgrade your hardware every one or two years, because you can pretty much guarantee that this year's new phones will have absolutely no difficulty running little touches like this, whereas last year's phones will chug.
Most consumers don't care if it's laggy. They see the glowing buttons and think it's the best thing since sliced bread, since neither the iPhone nor WP7 have it. Then once the next Nexus comes out they'll see even more button effects and spend even more money on it.
Don't get butthurt just because you're not the target audience.
Click to expand...
Click to collapse
i don't agree with anything you said. most consumers do care if it's laggy; that's why the get the iphone. people don't "ooh and ahh" about glowing buttons -- this is not the year 2000.
finally, there is no way in hell that the purpose of google adding "unnecessary eye candy" is to show how much better hardware is getting when the next generation of devices is released.
quit your trolling, pal -- your long-winded response really proved nothing.
thenamesian said:
i don't agree with anything you said. most consumers do care if it's laggy; that's why the get the iphone. people don't "ooh and ahh" about glowing buttons -- this is not the year 2000.
finally, there is no way in hell that the purpose of google adding "unnecessary eye candy" is to show how much better hardware is getting when the next generation of devices is released.
quit your trolling, pal -- your long-winded response really proved nothing.
Click to expand...
Click to collapse
Sheeple do not get the iPhone due to Android lag...
blackhand1001 said:
I want the glow gone lol.
Heres a comparison video of cm9 kang(winner00) which doesn't have the glow and official cm9 build 5-7 that has the glow.
http://www.youtube.com/watch?v=4Y7HwdKmvtk&feature=youtube_gdata
Click to expand...
Click to collapse
i watched ur video, and i see no performance difference in the two. looks/sounds like u just being anal...like 90% of xda. quit crying. u own the best phone out...enjoy it or mod the hell outta it, but dont be mad...
blackhand1001 said:
I want the glow gone lol.
Heres a comparison video of cm9 kang(winner00) which doesn't have the glow and official cm9 build 5-7 that has the glow.
http://www.youtube.com/watch?v=4Y7HwdKmvtk&feature=youtube_gdata
Click to expand...
Click to collapse
If you would like something changed you may submit your ideas to Android's gerrit for review.
Thread Closed.
I was thinking about re-buying it, even though it disappointed me back then when I had it. It was recently updated to ICS and I found it to be laggy, especially in the homescreen and with a livewallpaper, then it had also a bunch of bugs, the most annoying one was the camera button not working all the time when trying to snap a quick photo without turning on the display and everything, and the autofocus being slow and crappy in video recording. There were more bugs but I don't remember them too well.
Also, back then they all had the crappy screen with yellow tints, I got mine replaced but even the replaced screen was rather crappy, with inferior color reproduction, and yellowish whites, in comparison to the old screen which looked AMAZING, except for the dark yellow patches.
Tell me if it has gotten better in these few months, it should have gotten a bunch of updates too.
Also, can you tell me if games run well? My favourite android games that didn't run too well back then were Wind Up Knight, Let's Golf 3, Asphalt 6, and probably a couple more but I don't remember. I'd also like to know benchmark scores in NenaMark2, Antutu and Quadrant, I'm willing to install custom kernel and customized stock based roms.
MarkMRL said:
I was thinking about re-buying it, even though it disappointed me back then when I had it. It was recently updated to ICS and I found it to be laggy, especially in the homescreen and with a livewallpaper, then it had also a bunch of bugs, the most annoying one was the camera button not working all the time when trying to snap a quick photo without turning on the display and everything, and the autofocus being slow and crappy in video recording. There were more bugs but I don't remember them too well.
Also, back then they all had the crappy screen with yellow tints, I got mine replaced but even the replaced screen was rather crappy, with inferior color reproduction, and yellowish whites, in comparison to the old screen which looked AMAZING, except for the dark yellow patches.
Tell me if it has gotten better in these few months, it should have gotten a bunch of updates too.
Also, can you tell me if games run well? My favourite android games that didn't run too well back then were Wind Up Knight, Let's Golf 3, Asphalt 6, and probably a couple more but I don't remember.
Click to expand...
Click to collapse
Its a damn good phone, but if you didnt like it then you probably wont know. Most of those bugs are gone and my screen looks good. I run games just fine, but I am not a major gamer.
Probably should have put which phone you are talking about and put this is the QA section. I assume it is the Xperia S.
Yeah, it's the XS, I'm sorry.
My main problem with it was the disappointing performance. It literally ran less smoothly than my old Xperia Ray, and I tried EVERYTHING except for custom kernels, because there weren't many back then. I'm willing to try them now, if they do make a big difference.
I don't remember on what firmware was I though.
Which bugs still persist?
MarkMRL said:
Yeah, it's the XS, I'm sorry.
My main problem with it was the disappointing performance. It literally ran less smoothly than my old Xperia Ray, and I tried EVERYTHING except for custom kernels, because there weren't many back then. I'm willing to try them now, if they do make a big difference.
I don't remember on what firmware was I though.
Which bugs still persist?
Click to expand...
Click to collapse
Custom roms make a big difference. There really aren't any bugs that bother me that are still around. Its definitely one of the best Sony phones for dev support. On KA20.1 its really fast. I can't say enough positive things about this phone and I have owned one since it first came out. I has its flaws but there are no perfect phones.
mrsatan said:
Custom roms make a big difference. There really aren't any bugs that bother me that are still around. Its definitely one of the best Sony phones for dev support. On KA20.1 its really fast. I can't say enough positive things about this phone and I have owned one since it first came out. I has its flaws but there are no perfect phones.
Click to expand...
Click to collapse
Can you tell me which flaws still remain? The only hardware flaws I found with this phone were the unresponsive dots but I learned to get them to work everytime by swiping them instead of pressing them. I don't really mind non removable battery or no SD (I'll never fill 32Gb). The screen should be good now, I don't know if you had to get yours replaced, but at first they used to replace it with a ****ty screen which had tinted whites and poor contrast.
MarkMRL said:
Can you tell me which flaws still remain? The only hardware flaws I found with this phone were the unresponsive dots but I learned to get them to work everytime by swiping them instead of pressing them. I don't really mind non removable battery or no SD (I'll never fill 32Gb). The screen should be good now, I don't know if you had to get yours replaced, but at first they used to replace it with a ****ty screen which had tinted whites and poor contrast.
Click to expand...
Click to collapse
The software flaws that annouyed me were how slow and stuttery it was (is it still like that on stock?), camera button that worked half the time when going from sleep to snap (that feature was also advertised but it didn't work), terrible autofocus, and there were some bugs with the facebook thingy and some widgets, IIRC.
Also, if you could link me to a changelog of the new firmwares that came out recently I'd appreciate it.
Ah, sorry for the double post.
It's a good phone, but don't ask for miracles.
Buy one. Unlock it and flash a JB rom
Sent from my Jellybean Xperia S
I switched from Galaxy S2 some 3 months ago and really loving this device. The only thing I am missing about S2 is the colour saturation that display provided. OK some poeple hate that level of saturation but I simply loved it. Is there any way we can increase the saturation or make the colours pop a bit??
Lowering the gamma will make a pretty significant difference
Are you rooted or running a custom kernel? This is going to be the best way to customize the colors that you are looking for. Get the trickster app and a kernel like Franco or faux.
Sent from my Google GSM Gnex using Tapatalk 2
Hi all,
TL;DR - My questions can be boiled down to: Is my tablet defective in some physical way, or can I sort it out by rooting, flashing a good custom ROM, and being less picky?
I'm wondering if you can help me decide whether my tab is a defective unit. There's lots of talk in the threads about whether certain problems are by design or by fault, whether hardware or software based, etc. In light of those disagreements, I'm a bit unsure what to do with my GPad.
My situation:
I bought a Grade A refurbished GPad the other day (it's a no fault customer return - as new). Its S/N begins 310, so one of the earlier batches I presume. I'm running Stock 4.4.2, not rooted.
My problems:
Light bleed: I don't have 7 *clearly* defined lights, but I definitely have light from that edge affecting the screen (see attached pics). Most of the time, it's not too annoying, and I can maybe live with it. Seems like more general bleed even at the top of the tab in portrait mode, and on black screens/high brightness.
Yellow tint: My screen is *very* warm, in a colour sense. Again, most of the time I'm not too fussed -- it's only when I see whites alongside my Nexus 4 that I realise how yellow/orange my screen is (unless my Nexus is exceptionally blue, of course).
Dark blacks: When watching TV shows with lots of dark scenes (like Buffy), the display really struggles to show clearly what's going on -- the darks just melt into each other in a black mess.
Netflix: I'm getting pretty noticeable lip-sync issues on even old SD streaming (again, Buffy); I cannot resize the Netflix player without it blocking half the screen off with a grey band; I'm getting lots of skipped frames too -- HD content through Netflix is not what I hoped it would be (and was on the Nexus 7 I sold to buy this).
Questions:
1. Do others have these problems -- do any of them come as a package (as it were)? So, is there a connection between, say, dark blacks and yellow tint, or yellow tint and bleed worries?
2. If so, what S/N do you have? I'm starting to think that later models aren't actually any better, but I'm curious anyway.
3. Do any or all of these things have software fixes? I've got a screen filter running which takes some of the yellow off, but not much. I could go for increasing minimum brightness, but a) I like low brightness settings; b) some of the bleed is on black screens on high brightness settings (watching movies, e.g.). If you're running a custom ROM, do any of them work well with Netflix?
4. Ultimately, is it worth my trouble trying my luck with a new unit?
Any advice you can offer would be much appreciated!
ememeh said:
Hi all,
TL;DR - My questions can be boiled down to: Is my tablet defective in some physical way, or can I sort it out by rooting, flashing a good custom ROM, and being less picky?
I'm wondering if you can help me decide whether my tab is a defective unit. There's lots of talk in the threads about whether certain problems are by design or by fault, whether hardware or software based, etc. In light of those disagreements, I'm a bit unsure what to do with my GPad.
My situation:
I bought a Grade A refurbished GPad the other day (it's a no fault customer return - as new). Its S/N begins 310, so one of the earlier batches I presume. I'm running Stock 4.4.2, not rooted.
My problems:
Light bleed: I don't have 7 *clearly* defined lights, but I definitely have light from that edge affecting the screen (see attached pics). Most of the time, it's not too annoying, and I can maybe live with it. Seems like more general bleed even at the top of the tab in portrait mode, and on black screens/high brightness.
Yellow tint: My screen is *very* warm, in a colour sense. Again, most of the time I'm not too fussed -- it's only when I see whites alongside my Nexus 4 that I realise how yellow/orange my screen is (unless my Nexus is exceptionally blue, of course).
Dark blacks: When watching TV shows with lots of dark scenes (like Buffy), the display really struggles to show clearly what's going on -- the darks just melt into each other in a black mess.
Netflix: I'm getting pretty noticeable lip-sync issues on even old SD streaming (again, Buffy); I cannot resize the Netflix player without it blocking half the screen off with a grey band; I'm getting lots of skipped frames too -- HD content through Netflix is not what I hoped it would be (and was on the Nexus 7 I sold to buy this).
Questions:
1. Do others have these problems -- do any of them come as a package (as it were)? So, is there a connection between, say, dark blacks and yellow tint, or yellow tint and bleed worries?
2. If so, what S/N do you have? I'm starting to think that later models aren't actually any better, but I'm curious anyway.
3. Do any or all of these things have software fixes? I've got a screen filter running which takes some of the yellow off, but not much. I could go for increasing minimum brightness, but a) I like low brightness settings; b) some of the bleed is on black screens on high brightness settings (watching movies, e.g.). If you're running a custom ROM, do any of them work well with Netflix?
4. Ultimately, is it worth my trouble trying my luck with a new unit?
Any advice you can offer would be much appreciated!
Click to expand...
Click to collapse
Obviously some screen questions are subjective but to me:
1. I've never had much of the bleed problem personally, it's there just much smaller. The color(yellow) and gamma(darker darks) on this tab were a big problem on 4.2.2 for me. The 4.4.2 update (20a and 20b) really helped the color, there was a 18 leak that really improved the gamma but was LG unofficial.
2. Don't have it with me but mine was towards the mid lower end of SN.
3. There are a few fixes that help the situation. Run the 18 kernel on 4.4.2(requires tablet software modding of course), I personally built my own kernel based on 20b that boosts the gamma from 1.8-2.0 to 2.2-2.3. The screen looks pretty nice. I was working with changing the LED backlight drive to give a better brightness range but honestly the screen looks really beautiful.
4. If you look at the common complaints with this tablet I'm thinking your chances of getting a better one are not in your favor.
aicjofs said:
Obviously some screen questions are subjective but to me:
1. I've never had much of the bleed problem personally, it's there just much smaller. The color(yellow) and gamma(darker darks) on this tab were a big problem on 4.2.2 for me. The 4.4.2 update (20a and 20b) really helped the color, there was a 18 leak that really improved the gamma but was LG unofficial.
2. Don't have it with me but mine was towards the mid lower end of SN.
3. There are a few fixes that help the situation. Run the 18 kernel on 4.4.2(requires tablet software modding of course), I personally built my own kernel based on 20b that boosts the gamma from 1.8-2.0 to 2.2-2.3. The screen looks pretty nice. I was working with changing the LED backlight drive to give a better brightness range but honestly the screen looks really beautiful.
4. If you look at the common complaints with this tablet I'm thinking your chances of getting a better one are not in your favor.
Click to expand...
Click to collapse
Did you think from my screens that the bleed was particularly bad? It bugs me when watching films; sometimes it's extreme. Thanks for the tip about 18 kernal. I've read about that too. I'm tempted to flash the Mahdi ROM though - does that have gamma fixes, you know?
And yeah, so many complaints about screen issues with this tablet. Such a shame. Think I'll stick for a little longer and mull it over.
Sent from my LG-V500 using XDA Free mobile app
ememeh said:
Did you think from my screens that the bleed was particularly bad? It bugs me when watching films; sometimes it's extreme. Thanks for the tip about 18 kernal. I've read about that too. I'm tempted to flash the Mahdi ROM though - does that have gamma fixes, you know?
And yeah, so many complaints about screen issues with this tablet. Such a shame. Think I'll stick for a little longer and mull it over.
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
Yours looks really noticeable. I felt like mine improved with 18 and my homemade kernel, but it never seemed like it was that bad. I never used Mahdi, just CM11, stock 4.2.2/10b(for a day), stock 18 leak, stock 20 a and b.
aicjofs said:
Yours looks really noticeable. I felt like mine improved with 18 and my homemade kernel, but it never seemed like it was that bad. I never used Mahdi, just CM11, stock 4.2.2/10b(for a day), stock 18 leak, stock 20 a and b.
Click to expand...
Click to collapse
I don't suppose you would be able to make a kernel for cm based roms with the 18 gamma changes?
I reckon you'd have half the forum loving you, including me
Sent from my LG-V500 using XDA Premium HD app
Any chance you could share the kernel please?
Sent from my LG-V500 using XDA Free mobile app
whoamigriffiths said:
I don't suppose you would be able to make a kernel for cm based roms with the 18 gamma changes?
I reckon you'd have half the forum loving you, including me
Sent from my LG-V500 using XDA Premium HD app
Click to expand...
Click to collapse
If it's just the ramdisk that is different it could probably be doable, but I'm not sure the ramification of having the 4.4.2 or 4.2.2 stock as the underlying structure that you have flashed CM over(i.e the other partitions).
LeighR said:
Any chance you could share the kernel please?
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
I'm up in the air over it. I have some other mods to it, including overclocking for CPU and GPU that I wanted to fine tune better. I have been using it for a couple of days without any major issues, but I don't want to damage anyone's device.
I suppose if you are willing to accept the as-is nature of it, and the fact the CPU speed is bumped to 1.78 from 1.72 I can share(check the commits for other changes). At some point we need to see if the gamma is good across other screens...
Only if you are on 20A or B.....not going to work for CM, Mahdi, etc
MAKE A BACKUP FIRST
3 options in the zip(this isn't a flashable zip) If you want to be testing this I expect you know what to do with the one of the 3 files.
-boot.emmc.win, (loki'd for aboot version a/b) put in a TWRP folder and restore
-lok file. (loki'd for aboot version a/b)
-img file (non loki'd if you have a different aboot and need to loki yourself)
https://app.box.com/s/ic5ruxzwjzob3bff9vg9
For GPL purposes https://github.com/aicjofs/android_kernel_lge_v500
Also thank @oubeichen, I had ported the Faux control and couldn't figure out the bootloop issue without his help.
Thanks
For anyone unsure how to flash the kernel, I changed the name of boot.emc.win to boot.img and flashed it with flashify. Seems to be working nicely. I had only just upgraded to v20b, so haven't played around with it too much but this kernel seems white and bright
Sent from my LG-V500 using XDA Free mobile app
LeighR said:
Thanks
For anyone unsure how to flash the kernel, I changed the name of boot.emc.win to boot.img and flashed it with flashify. Seems to be working nicely. I had only just upgraded to v20b, so haven't played around with it too much but this kernel seems white and bright
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
I had time to make a proper flashable zip to "install" in TWRP. This one has quite a few changes committed since the one I posted above. If it continues to work for everyone I can move it to the development section.
https://app.box.com/s/p2adc43p98fmkgjl2aoa
aicjofs said:
I had time to make a proper flashable zip to "install" in TWRP. This one has quite a few changes committed since the one I posted above. If it continues to work for everyone I can move it to the development section.
https://app.box.com/s/p2adc43p98fmkgjl2aoa
Click to expand...
Click to collapse
That would be great.
If you are willing to look at the cm based kernel, I, for one, would be more than happy to test it for you.
I'm sure one or two of the guys would also be happy to test for you too.
As an aside, I am currently running mahdi kernel on infecteds cm11, as some changes cm have made lately, are causing a few issues. So these cm based kernels certainly seem to be swappable.
Thanks again in advance.
Oh and please don't feel that you are obliged to do anything for the cm roms.
I can well appreciate the extra work involved for you. I'm just being a cheeky sod
All the best rich
Sent from my LG-V500 using XDA Premium HD app
aicjofs said:
I had time to make a proper flashable zip to "install" in TWRP. This one has quite a few changes committed since the one I posted above. If it continues to work for everyone I can move it to the development section.
https://app.box.com/s/p2adc43p98fmkgjl2aoa
Click to expand...
Click to collapse
Well done with the sharing of the kernel. I might be tempted to restore my nandroid backup of the rooted stock just to give this a go. But if I did I know that running stock would bother me, after using Infected's build of SlimKat.
To be extra cheeky, could you please post the stock 4.4.2 kernel, so that I can switch between the two for testing? If it's a hassle, I can probably try to extract it from one of the ROMs posted.
I saw that LG have made the 20b kernel public but its 96MB and not downloading.
Sent from my LG-V500 using XDA Free mobile app
LeighR said:
To be extra cheeky, could you please post the stock 4.4.2 kernel, so that I can switch between the two for testing? If it's a hassle, I can probably try to extract it from one of the ROMs posted.
I saw that LG have made the 20b kernel public but its 96MB and not downloading.
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
This will remove the kernel all the modules and install the 20B stock kernel and modules. Should only be used on 20B ROM obviously.
https://app.box.com/s/y6uvvs91w4yjuco4kvyz
Thanks. I did pull the boot.img from the stock ROM and was flashing that back and forth but flashify only allows 3 flashes per day, so this is easier
Definitely more white (stock kernel gives people jaundice in pics) and brighter on dark movies
Sent from my LG-V500 using XDA Free mobile app
LeighR said:
Thanks. I did pull the boot.img from the stock ROM and was flashing that back and forth but flashify only allows 3 flashes per day, so this is easier
Definitely more white (stock kernel gives people jaundice in pics) and brighter on dark movies
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for testing it out, at least I know it's not placebo!
Decided to post it:
http://forum.xda-developers.com/showthread.php?t=2741405
aicjofs said:
Yours looks really noticeable. I felt like mine improved with 18 and my homemade kernel, but it never seemed like it was that bad. I never used Mahdi, just CM11, stock 4.2.2/10b(for a day), stock 18 leak, stock 20 a and b.
Click to expand...
Click to collapse
Thanks for confirming that it is pretty bad. If I keep it, I'll either check out the kernal fix you've now posted (thanks) or flash a custom ROM. I'm swaying towards trying my luck with a replacement though. Cheers