F2FS would make this tab fly high. Please do...
Sent from my LG-D405 using XDA Free mobile app
[KERNEL][v500][4.4.2] AIC Kernel [MAY-4-2014]
- Thread starter aicjofs
- Start date
F2FS would make this tab fly high. Please do...
Sent from my LG-D405 using XDA Free mobile app
DNS issues with the domain name. Sorry, link should work again.
I'm having a problem, I had tried to install the 2 kernels, pre beta 2 and the beta 2, but none of them appears to be installed properly.
In adiutor and faux123 the values are stock(GPU max 400 and CPU max 1.72 min 384), the schedulers do not appear, voltage neither too.
Any idea what is wrong?
In adiutor and faux123 the values are stock(GPU max 400 and CPU max 1.72 min 384), the schedulers do not appear, voltage neither too.
Any idea what is wrong?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
43AIC Kernelfor LG G Pad 8.3 V500
Compatible with v500 STOCK BASED LG 4.4.2 roms ONLY! The "gamma improvement only" is available for other ROM's in the installer
This was just a private build that seems to have gained some demand to help with the v500 gamma issue. I have been running it the past week and it seems stable enough to share to other v500 users. I'm not a developer, I build and update TWRP for the Nabi tablets, have shared a few windows bat files, have a VB.net app to automate various mods to the Nabi's, and a lot of research of nvflash/APX nand formatting for the Nabi's. My only previous kernel builds were for the HP Touchpad for private use, and my Ubuntu computer. Basically taking what real developers have done and trying to make it work for my own use.
EDIT 5/11/14: I put the gamma improvement fix in just a stock kernel with no other changes, and the changes to CM11 kernel. There are 2 CM kernel version depending on which LG ROM you installed CM over to deal with the dimming issue at boot. Those are available in the new all in one installer.
Disclaimer:
Experimental. Use this at your own risk.
Please Please Please make a full backup of your tablet.
Base:
The starting source is V50020B from LG
Compiled with arm-eabi-4.7
Added features:
Initial
- Improved gamma. Using default linear LUT (from 1.8-2.0 to 2.2-2.3 on my screen)
- Default overclock from 1.72 to 1.78Ghz (no voltage increase)
- Default underclock to 162 Mhz
- Sysfs Voltage Table added for undervolting
- Allow GPU to manually increase freq from 400Mhz to 487Mhz
- Add GPU boost to GPU on demand governor
- Add Faux Display interface (gamma control seems broken)
- Add NTFS support(untested)
- Add SIO Scheduler
- Add FIOPS Scheduler
- Optimize memcopy, string and square root functions
- Add Intelliactive Governor
Download:
BETA: http://nabtabhacks.com/downloads/AICbeta2.zip Very stable but haven't got enough feedback to make it official. See changes here http://xdaforums.com/showpost.php?p=54482330&postcount=229
Installer for all gamma improvement kernels, tested by numerous members(AIC, stock, and CM) http://nabtabhacks.com/downloads.htm
Installer AIC Kernel: http://nabtabhacks.com/downloads.htm
Uninstaller, returns to stock 20B: http://nabtabhacks.com/downloads.htm
Install:
- Reboot to recovery(TWRP)
- Make a backup, just do it
- Install AIC_kernel_flashable.zip
- Wipe caches/dalvik if you see fit
- Reboot
Source:
AIC: https://github.com/aicjofs/android_kernel_lge_v500
Stock with gamma only: https://github.com/aicjofs/android_kernel_lge_v500_stock
CM: https://github.com/aicjofs/android_kernel_lge_v500_cm
Credits
I need to give some specific acknowledgement to "oubeichen" for sharing his kernel tree, and sharing of information. Also to id10terror's install script was the easiest to use as a template.9
I had to take a break with the gamma last week, it was getting me in a rut, and I wasn't working towards anything else. What I did find that was strange is that I do actually get some form of gamma control using the generic MSM color calibration. If I use Faux's kernel enhancement pro app when I set the gamma I do indeed get a change but any further change from that point cannot be achieved with with expected results(its seems chaotic), if however I reset gamma before each adjustment the results do seem consistent. For example on my display with my kernel default lut change I get 2.2 gray, but the red, blue, green, etc are all high(2.3 to 2.6), if I set red 95, green 95, blue 93, I get 2.1 gray and 2.2 for the other 6 colors. All this using display tester.
Now a reply to the rest of the thread:
What I have been doing the last week is checking deeper in to overclocking. Some of you know this and some don't so I will explain it all. Let me preface this with saying I have done extreme desktop overclocking since the 1990's and have had known world records on certain CPU's. For the Gpad it's pretty simple, there just isn't enough thermal headroom here. Most of the people here that want overclocking also do benchmarks, I'm willing to bet your low score in Antutu is a function of thermal throttling. If you let the tablet sit for 10 min and cool down you will get a higher score then if you run the benchmark back to back, and this is at stock speed. Want to test it in Antutu?
Code:adb shell su stop thermald
This will disable the thermal throttling, which doesn't kick in until ~94C. Higher benchmark CPU score?
The other issue is thermald control in general, it has a nasty habit of reseting the max CPU freq in the table after a thermal throttling event occurs. What this means is if I make a kernel that has a highest table freq of 2.1 and someone doesn't want to run that high and limits it to stock speed 1.72, if they have a thermal throttling event it will then take their desired 1.72 max and reset it to 2.1. Not what we want. Thermald on the gpad is qualcomm closed source so we can't edited out the reseting max function. There is another way, you can configure the temps at which the throttling occurs. Take a look at /system/etc/thermald-8064.conf. At the end you will see a section [pa_therm0], you can raise the threshold values 44, 47, 50 etc(doubled they are 88C, 94C, 100C, etc), but do we really want to be taking the throttling temp over the boiling point of water? I think that kind of thermal expansion and contraction is terribly hard on the solder joints.
So what other options do we have? There is open source thermal. We can use one of those, but it's only advantage is it doesnt mess with your desired max freq, do avoid throttling with it you still have to set over 100C. To put it in perspective look at some other devices out there, want to know where they throttle? ~70C-80C
Another option lower the voltage. I was able to shave 25mv off the upper clocks, and it's not enough to get to the next freq step and still be under the thermal throttle.
The only thing that held a little promise was turbo boost. If you use an open source thermal engine, you code it to run at a max freq and when more then 2 cores go active your max CPU speed comes down(Pretty much like Intel turbo). That worked OK, I was having issues with on demand governor and this, but the others worked OK. But 2 cores at 2.1 isn't noticeably faster, and in benchmarks you don't get this when other cores come on line.
It's sad but it's just too hot, my little bump to 1.782 from 1.728 was only because it is free with no increase to voltage. I'm not stepping in to the debate about if CPU overclocking is good, bad, worthless, great or not. I will say that the tablet doesn't feel any different at the elevated speeds(2.1), 1.782 is plenty fast. GPU overclock is another story, there is some measurable gain in the form of frame rate.
If you made it through all that then well you are a swell person and maybe someone that can help me out. I have a new kernel I need some help testing.
20d source
4.9.1 linaro
kernel mode neon
LZ4 compressed kernel
ROW scheduler
Intellidemand gov
init.d support added to your current ramdisk(warning if you have your own init.d folder back it up first and it may mess with your busybox install)
lower the min display brightness(at 0% it should be darker)
change kcal control method(try 95, 95, 93 in Faux app if you have it)
Intelli thermal
GPU overclock to 487 by default(Need gamers to test this)
Intelli plug
exfat-nofuse(replaces LG module)
-12mv on all CPU speeds, -50mv at 162Mhz
Source: https://github.com/aicjofs/android_kernel_lge_v500_20d
Really need to test the governors, schedulers. Turn off mpdecsion and thermal, and use intelli plug and intellithermal. Game on the GPU, check init.d install. Not a requirement as it costs money but the Faux app is the best interface, trickster is OK but missing gamma.
So far just for the stock ROM and compatibles. Sorry I spent too much time on gamma and haven't done CM. But @oubeichen and @ckret are taking care of you there. Same installer for now I'll change it up later, use "AIC kernel for stock"
MAKE A BACK OF SYSTEM AND BOOT FIRST!!! then download and try.
http://nabtabhacks.com/downloads/AICbeta2.zip
Should be safe but this kernel is BETA. I did have a lockup using ART and benchmarking, don't know if that was fluke.9
the v500 is similar to mako
so i used it as a base and substituted qlut
https://github.com/drbeat/v500_cm/commits/cm-11.0 // dont merge or pull ! i did something wrong. guess it was late yesterday
did some typos thats why there are 4 commits
i will try to port francos or fauxs gamma control over to this kernel8Back from vacation in the middle of no where with little to no connection to the outside world for a couple weeks(see attached photo )
Too much trouble with the assert check so I removed it from the installer, and moved things off box.net. Are people that are having troubles using the "installer" version and using the right kernel for the right ROM?
"gboost lowers the up_threshold for ondemand governor when GPU is at max frequency. This helps mostly with graphics intensive games that use gyro controls, such as racing games"
I was hoping everyone would post what was working best for them, I like FIOPS and intelliactive personally.
I have finally put all 3 files on my Nabtabhacks site, should no longer be bandwidth issues or anything else. I just didn't realize the demand for this, there were over 500 downloads and I hit the box limit.
Alot of Android apps can read the kernel date, off the top of my head they are like may 9th, 10th, 11th something like that.
You were using the AIC on stock or something else?
There seems to be a lot of confusion over this, and I am not even sure I fully understand it. LG made a change to the way the lm3532 backlight controller ramps. If you look at the below you can see 2 changes. 1) The range of drive from 0-255 is different starting at 3 for 1, and 119 for the other, partially the reason it can't go as low. 2) You can see the mapping is changed from linear to exponential.
Then there is stuff like infected_ changes to the auto brightness in overlay/frameworks/base/core/res/res/values/config.xml for his CM builds( http://review.cyanogenmod.org/#/c/61551/1/overlay/frameworks/base/core/res/res/values/config.xml ). I don't know if those changes made it to the other ROM's out there, nor have I looked to see the difference LG themselves made from 4.2.2 to 4.4.2.
For 4.2.2
Code:3, 3, 3, 3, 3, 3, 3, 3, 4, 4, 4, 4, 4, 4, 4, // 14 4, 4, 4, 4, 4, 4, 4, 5, 5, 5, 5, 5, 5, 5, 5, // 29 5, 5, 5, 5, 5, 6, 6, 6, 6, 6, 6, 6, 6, 7, 7, // 44 7, 8, 8, 8, 9, 9, 9, 9, 9, 10, 10, 10, 11, 11, 11, // 59 12, 12, 12, 12, 13, 13, 13, 13, 14, 14, 15, 15, 15, 16, 16, // 74 17, 17, 17, 18, 18, 18, 19, 19, 20, 21, 22, 22, 23, 24, 24, // 89 25, 25, 26, 26, 27, 28, 28, 29, 29, 30, 30, 31, 31, 32, 32, // 104 33, 34, 35, 35, 36, 36, 37, 38, 39, 39, 40, 41, 41, 42, 43, // 119 44, 45, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, // 134 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, // 149 73, 74, 75, 76, 76, 77, 78, 80, 81, 82, 83, 85, 86, 87, 88, // 164 89, 90, 91, 93, 95, 96, 97, 99,100,102,103,104,106,107,108, // 199 109,110,112,114,115,117,119,121,123,125,127,128,129,130,132, // 204 133,135,136,138,139,140,142,144,146,148,150,151,153,154,156, // 219 157,158,159,161,163,164,165,167,168,170,173,175,177,180,184, // 224 186,188,191,194,197,199,201,203,205,207,209,211,213,215,217, // 239 219,221,223,225,227,228,230,232,235,238,240,243,246,249,252, // 244 255 and {0x16, [B]0x03[/B], 0xff, "Control A Zone Target 0, [B]Linear Mapping[/B], I2C Current Control"},
For 4.4.2
Code:119,119,119,119,119,119,119,119,124,124,124,124,124,124,124, 124,124,124,124,124,124,124,128,128,128,128,128,128,128,128, 128,128,128,128,128,131,131,131,131,131,131,131,135,135,138, 138,141,141,143,143,146,146,148,148,151,151,151,153,153,153, 153,155,155,155,155,157,157,159,159,159,161,161,162,162,162, 164,164,165,165,166,166,168,168,168,170,170,171,171,172,172, 173,173,174,174,176,176,177,178,179,180,180,181,181,182,183, 183,184,184,185,185,186,186,187,187,188,188,189,189,189,190, 190,190,191,191,192,193,193,194,194,195,195,196,197,197,198, 198,199,200,201,201,202,202,203,203,204,204,205,206,206,207, 208,209,210,211,212,213,214,215,215,215,215,216,216,216,217, 217,218,218,219,219,220,220,220,221,221,222,222,222,223,223, 224,224,225,225,226,226,227,227,228,228,228,229,229,230,230, 231,232,233,233,233,234,234,235,235,236,236,236,237,237,237, 238,238,239,239,240,240,241,241,242,242,243,243,243,244,244, 244,245,245,245,246,246,246,247,247,248,248,248,249,249,249, 250,250,250,251,251,251,252,252,253,253,253,254,254,254,254, 255, and {0x16, [B]0x01[/B], 0xff, "Control A Zone Target 0, [B]Exponential Mapping[/B], I2C Current Control"},
So what I did was make the "installer version". I admit it's a bit confusing, and maybe I should make different threads to keep it more simple(but more complex for me haha). In the installer version you have
the AIC kernel with all the OC, UV, etc (only works for LG based ROM's i.e. stock, LRS)
the stock kernel with just gamma correction
then the 2 custom ROM kernels with gamma correction only.(to work for CM, slimkat, etc, etc)
Back to the brightness discussion. Everyone is saying you need to be on the LG 4.2.2 base for custom ROM's because of a dimming issue at boot, and until the first time you power cycle the display. The 2 custom kernels I put in the install basically have the changes from the code tags above (119,119,119,119,119,119,119,119,124,124,124,124,124,124,124 blah blah blah) so that you can be on 4.2.2 base or 4.4.2 base and not have the brightness boot issue.8
I'm having an issue getting the freq limiter to work it just wont keep the value stored under certain conditions. What this means is that you would have a range of clocks available up to 2.1. Lets say you find 1.9 works so you set that as max freq. However certain operations on the tablet will kick your personal set max freq out and then ramp to highest possible(2.1), and like I said before most peoples tablets could go to 2.1 on a single core, multiple cores at 2.1 will shut the tablet off.
I agree, display is still not perfect, even gamma isn't perfect(which is why I say "improved"). With the Faux app you can change gamma with AIC kernel, but something is broke and it doesn't change it in any meaningful way. I went about trying to set it up similar to the Nexus 4 using Faux method to expose the settings to sysfs. (i.e. get r_gamma, b_gamma, g_gamma as inputs) However the Nexus 4 must have different address because what is output is gibberish. There also is the franco method but I'm pretty sure it's using same addresses. Not sure where to begin yet on saturation. I spent most of my free time last week trying to incorporate gamma to all flavors of v500 ROM's, next week I'm taking the family on vacation, and figured the best use of my time was getting the most people what they wanted, which was gamma improvement for all ROM's.
Glad to hear. I tried to make a short term goal to improve the gamma on any ROM available with the new installer, seems mostly positive results.
