yashsingh1/xdaforums huggingface dataset:
[G Pad 8.3 Android Development] Canadoc:
Well something is wrong then as my trickster shows still 172and not 156. I have the script unzipped in the init.d folder in system/etc permissions set at owner rwx group and others both at rx.

And have rebooted.

Supersu installed and set to run on boot.

Any ideas why it isn't working.

I flashed Bob's kernel as a recovery restore com back up
[G Pad 8.3 Android Development] sleekmason:
And you do have busybox installed?

I can't know without having your device, but my answer at this point would be to say that Bob's kernel does not currently have init.d support, or you are not successfully using his (Bobs) kernel. It sounds like you have everything from my side of things accurately placed.

to see if you are using his kernel you could go to about tablet / build and see the timestamp on the kernel version.As far as the init.d support, I can only speak for my own kernel build.

It is likely, as most roms do have init.d support, and as he was using a separate rom, that the ROM already had init.d support, and so when he was testing he may have seen it working and the assumption was made that he had enabled it for his kernel as well.

But again, without a device, I don't know that for a fact.

I would report a possible problem in his thread. This is something that probably will need to be addressed if it doesn't work on stock.
[G Pad 8.3 Android Development] Canadoc:
Yes busybox is installed.

Am not using custom rom but rather stock rooted since the custom ones are not based on north american version of the rom rendering the remote control feature useless (does not have cable box control in the european asian models but substitutes bluray player which I don't need as I use a ps3). It is possible he did not include init.d support as he suspected but rather it was built in to the ROM (Malladus ) he was running.

I did go into trickster mod and was able to modify most of the settings in it to mimic what was in your battery saver script. Will see if it helps.
[G Pad 8.3 Android Development] whoamigriffiths:
I've added your tweaks back in to see how it goes.

I'm running infecteds cm11, and I can confirm that it is definitely changing the cpu frequency.

All the best rich
[G Pad 8.3 Android Development] sleekmason:
Update -

Latest build available for download. sleekai5

Sleekai5 allows for tethering your device to other devices using bluetooth and usb. The wifi hotspot does not currently work and probably wont with our wifi card.

The bluetooth however, works flawlessly, having tested by connecting my wifes tablet to mine and being able to use the internet through bluetooth.

After install, look in Settings - Wireless and Networks - More - Tethering and Portable Hotspots

Enjoy!

My new favorite code snippet:

sed -i "/\b\(setprop ro.tether.denied true\)\b/d" init.palman.rc
[G Pad 8.3 Android Development] SCWells72:
Maybe this is already documented in this thread, but what are your ideal settings with this kernel installed to take maximum advantage of it? I've set the CPU governor to ondemand and the IO scheduler to deadline using Trickster Mod. I've also set the minimum CPU frequency to 384000 and frequency lock to ON, and I've set Multicore Power Saving to 2 and Temperature Throttle to ON. Oh, and the GPU governor is ondemand as well. In my case I'm trying for an optimal balance of battery life and performance/smoothness. Any other thoughts on how best to accomplish that?
[G Pad 8.3 Android Development] sleekmason:
I'm not sure I understand, are you using my kernel? Or another. Most of the settings you describe are built into the kernel. Why are you locking the frequency? If you will observe the CPU states you will see that the device uses deep sleep a lot when unused, offering far better battery life.

Every change I've made to the kernel is outlined within the post. All of the changes have been researched by myself to provide what I believe is to be the best optimization for this particular kernel for this particular device. This includes my settings for the use of init.d.

There is of course, always more to do. So far I have been quite pleased with the results.

People have a tendency to change settings on the basis that they CAN change the settings. This won't always give the desired results. I try to keep it simple, so as to create a rock solid kernel with no flaws, only perks. There are ways I could eke out 3 more extra hours of battery instead of the 1extra I have now, but at what cost? I want to be able to enjoy my device as a smooth running tablet, able to do whatever I ask of it.

Using programs like greenify and app ops exposed will do a lot to insure a longer battery life.

In my kernel I also disable certain debugging and logging routines that, while good for the original kernel developer for the device to get feedback, only bog down the end result if not disabled afterwards.

I guess in my long winded way what I'm trying to say is that for each individual this can be different and I would be able to help you further if I knew exactly what you were trying to do for what purpose. Maybe you live in the outback and need to have it on for 5 days of the time. I don't know.

if that is the case, there are threads for init.d tweaks that are extremely severe in limiting the performance of your tablet while providing excellent battery life well in excess of 12 or even 15 hours of on screen time, and over a week easily of tablet on time. for starters, a far better way than locking the frequency would be to simply set the values for the CPU frequency in my init.d script for 384000, (though I wouldnt recommend going quite that low) thereby still allowing for deep sleep while keeping the tablet at a minimum power drain when on.
[G Pad 8.3 Android Development] SCWells72:
Let me clarify. Yes, I'm using your kernel. I'm not locking the CPU frequencies in at those rates. I'm attempting to lock in the minimum frequency of the range allowed by the governor. Here's the description from Trickster:

"Frequency Lock - Try to lock min and max frequencies using permission trick. Might get undone because of other apps/system services."

If I don't do this, the default minimum frequency is ~1.1GHz, and I can observe that in a CPU state monitor. I imagine I could do the same thing via init.d, but I figured I'd use a high-level utility like Trickster (or SetCPU, etc.) to do it instead. If you're saying that I'll see similar battery life by leaving that alone because of the way that the deadline CPU governor works, I'll turn that off. I just assumed that the more time it can spend in a low frequency state while idle before going into deep sleep, the better.

I'm already using Greenify and have set all the apps for which I don't care about reliable notifications to hibernate, and that definitely makes a nice difference.

I'd already seen in your original post that you'd set ondemand and deadline as the CPU governor and IO scheduler defaults respectively, and I was just saying that I'd verified that I'm using those as well in Trickster mod. My question was particularly about taking advantage of things that your kernel unlocks relative to the stock kernel and whether there was anything else I might be not be using, implicitly or explicitly.
[G Pad 8.3 Android Development] sleekmason:
Gotcha, no, what you see is what you get, nothing else to be adjusted as such other than playing with init.d and the like. Occasionally I will search for other settings that will enhance the kernel but have to be careful. The op lists any and all changes I make, mostly to the default defconfig, and a few to the ramdisk.

I had thought to make a custom on-demand specifically for battery savings. Compiled one into the kernel but had problems getting deep sleep to work properly. In the meantime I saw what all init.d could do and decided that was a better route for a lot of the changes because they could be easily changed by anybody wanting to explore the possibilities. This meant that other than the tweaks made to the defconfig, and the tweaks to the ramdisk to allow init.d support and tethering, there was no need to louse up the system with hard changes.

The neat thing is, that if you explore changes by using init.d one at a time to test the results by the user, I would be happy to add them to the script.

There are a whole lot of scripts out there that sound really cool because they change a bunch of values, but wind up crossing their benefits out with all the cruft. So... What I did was make small changes until I found values that allowed excellent performance while saving battery.

There is more to do here, but I find myself being pleased by the extra hour or so of battery life I have been able to aquire , and so am slow to mess with it more.

As far as the CPU goes, for most use, only cpu0 is used, and that includes simple programs like kindle as well. Locking all of them down to 1566000 seems to work best, with little gains in dropping further (without performance issues). Init.d locks them down well. You may see the max freq used a bit at startup because init.d support is almost the last thing added to boot before your lock screen comes on. This means 10-20 seconds at max frequency.

Using another scheduler besides deadline may give you slightly better battery, but for this device, the performance loss is silly. As far as other governors added to the kernel go, I keep coming back to simple on-demand, as governers like smartass2 wind up causing some annoyance for me, and I revert back.

If you are really interested in checking all this out I would install AntiX Linux in Virtual box (if you are using windows), and run through my roll your own kernel guide. I continue to learn new things all the time!
[G Pad 8.3 Android Development] bbubelis:
USB Fast Charge

Is this possible on this device / kernel combination?
[G Pad 8.3 Android Development] mushat3k:
Serious kudos to the Dev. I can't believe what a difference the color correction makes on this device. Also running way smoother, no more jitters!
[G Pad 8.3 Android Development] sleekmason:
I reckon so . . I will have to look into it! If I do incorporate it, I will still put a cap below the ac norm, but at least double what it pulls from usb now. Why they don't put it at a reasonable rate is beyond me. There are a view computers out there you could fry using fast charge at full draw, but why does it have to be a full draw so long as it charges even a litlle while using eh?
[G Pad 8.3 Android Development] sleekmason:
Thank you! Glad you like it!

On the next version I have changed a couple of settings that should help with the ungodly waiting for pages to load on the internet.

I have to wait for xda to fix their upload problems first. Seems you can still upload scripts and the such, but it balks at kernels! Stay tuned!
[G Pad 8.3 Android Development] sleekmason:
Update-

Sleekai5.1 released.

Just a few minor changes to hopefully fix the internet delays people are experiencing.

I would please appreciate some feeback on this particular kernel, for this particular reason. Or anything else you might wish to say regarding performance etc...
[G Pad 8.3 Android Development] bbubelis:
Sleekmason,

Installed new kernel about two hours ago. IMHO, performance has improved dramatically. Great work! Thank you for your continued support of the V510.
[G Pad 8.3 Android Development] SCWells72:
Totally agree. I've only been using it for an hour or so, but I'm seeing a notable improvement across the board! Nice work!
[G Pad 8.3 Android Development] Canadoc:
Sleekmason, Any chance you can send your improvements to Bob to implement in an update of his kernel. I am afraid there had been no updates on that front since initial retrograde and init.d support Does not work.

Thanks!
[G Pad 8.3 Android Development] gunnyman:
Thanks zleekmason. Updated this morning.
[G Pad 8.3 Android Development] sleekmason:
Thank you!

[MENTION=3246437]Canadoc[/MENTION], I was in communication with him when he released his version for the 500, but haven't heard a peep since.

If [MENTION=3210378]id10terror[/MENTION] used my zip script, but only changed the paths in order for the 500 to work, you may already have init.d support using his kernel. I'm not sure if he used mine or someone elses.

I would suggest downloading his kernel and checking.

You can find out by downloading a terminal emulator.

Open and type su to enter root,

su

Then:

grep busybox /init.rc

You will see a line that will have the path to init.d at the end. If there is nothing about init.d, you don't have it, and he will need to incorporate it into the script, or into the boot image itself to be installed using the replacement method in recovery.
[G Pad 8.3 Android Development] id10terror:
[MENTION=5623558]sleekmason[/MENTION], I actually used a different script for my kernel install as I had to incorporate loki patch and loki flash. I'll be adding init.d support in my next release soon, just haven't had the time to do anything these last few days.
[G Pad 8.3 Android Development] sleekmason:
88sleektweaks for init.d updated-

Added

echo 90 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core

echo 90 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load

Increases threshhold for cpu to ramp up when in use. -- better battery savings . . should be anyway, but probably not enough to notice!

That being said, device feels snappier, though it's probably illusion. ;)
[G Pad 8.3 Android Development] sleekmason:
Knock on for the gpe-

Better read all of this.

The location for knock on in the gpe is:

/sys/devices/i2c-3/3-004b/knock_on

You can enable it by adding a 1(on) to the file, and it works.

But I can not incorporate it into the kernel. When I try adding a line to enable it directly using init.rc in the ramdisk, or using init.d,

it freezes up the tablet. Not Good. This may be a case where i need to proxy it through /system to make it work, but then you would think init.d would work.

Iv'e tried using

write /sys/devices/i2c-3/3-004b/knock_on 1

directly in init.rc,

and

echo 1 > /sys/devices/i2c-3/3-004b/knock_on

init.d.

Anyway, there is something I am missing that seems simple but may not be, or maybe it is and somebody can give me a good snippet to make it work somewhere.

If you try this yourself, be aware that you may soft brick your tab and need to get into recovery to first remove the offending file, and /or flash your kernel again using adb.

The zip script uses your existing ramdisk so that wouldn't help you if you mess it up at that level.

So, if you just want to see if it works, you can pop a 1 in there and check it out.

Oh, yeah, no knock off setting found.
[G Pad 8.3 Android Development] SCWells72:
I just tried this and it works for me as well. Weird that you can't find a good place to add this to the device startup, but I'm sure one exists. As for knock off, you can use GravityBox KitKat (Xposed Framework) to enable double-tap on the status bar to turn off the screen, so between the two it's possible to get very close to the stock LG behavior.

Good find!
[G Pad 8.3 Android Development] sleekmason:
This was my thinking as well.

It may be that adding it at the end of init.rc would allow it to work without freezing. I'll try a few other things like that in a day or two.
[G Pad 8.3 Android Development] sleekmason:
Wait,

Did the init.d line work for you? Or did it just get quoted?
[G Pad 8.3 Android Development] SCWells72:
No, I ran that line manually. I just included the exact line that I ran in the quote to clarify what did work for me. Sorry for the confusion.
[G Pad 8.3 Android Development] gunnyman:
Can we edit the database and add the value that way ?
[G Pad 8.3 Android Development] sleekmason:
You can follow the path using root browser, open the file and add a 1 and it will work immediately... I haven't figured out yet how to add it to init without causing a freeze, but then I only tried once and could've put something wrong.

I'll have to try again a couple of different ways. Maybe try init.d again when I get a chance. Seems weird that wouldn't work. If you try that way, be aware you may need to delete or edit the file in init.d through recovery if it doesn't work correctly.
[G Pad 8.3 Android Development] kdog350:
for some reason the file won't open for me :/
[G Pad 8.3 Android Development] sleekmason:
You can also open a terminal, su to root, and enter the command.

su

echo 1 > /sys/devices/i2c-3/3-004b/knock_on
[G Pad 8.3 Android Development] gunnyman:
Good news,

the Xposed Module for Knock Off on LG AOSP works great on the gpad GPE

http://xdaforums.com/showthread.php?t=2563976
[G Pad 8.3 Android Development] sleekmason:
Yep! I was looking in the kernel source but haven't found what I'm looking for yet. I also tried adding a sleep function to an init.d script to start the code later but no go. We'll see!
[G Pad 8.3 Android Development] sleekmason:
Update about knock on,

So, I compiled doubletap2wake, and sweep2wake into my kernel (not released), and though everything compiled fine, everything shows up on the device fine, and trickstermod now shows the wake options, it doesn't work. Very frustrating.

Very very frustrating.

I would settle for the built in knock on feature if I could enable it at boot, but no go there as well. Probably missing something simple. Any ideas about this would be appreciated.

If any devs would like a copy to check out and see what you can do with it, let me know.
[G Pad 8.3 Android Development] sleekmason:
-Kernel added-

sleekai5.2 Just some minor code fixes, though it does seem an improvement for internet. Still trying to get tap2wake working.
[G Pad 8.3 Android Development] bbubelis:
Sleekmason - Any update on USB fastcharge?
[G Pad 8.3 Android Development] sleekmason:
I was hoping for a quick fix, but that won't be the case. I'll have to research it more when I get some time.
[G Pad 8.3 Android Development] cam30era:
Thanks a lot for your work on this. Remarkable how fast and responsive this device/ROM is with your kernel.
[G Pad 8.3 Android Development] sleekmason:
--UPDATE--

And a pretty big one at that!

new kernel sleekai5.3

added row as possible scheduler

added doubletap2wake (not working on mine)

added sweep2wake ( the sweep to sleep works) to enable these options you can use trickster mod - specific settings- wake settings, or go to /sys/android_touch, and enable there or by using your terminal

su

echo 1 > /sys/android_touch/sweep2wake

echo 1 > /sys/android_touch/doubletap2wake

Again, only the option to swipe to sleep works for me, please report if you have more success with the other options, or if you can get them to work. To sweep to sleep, drag from right to left on your screen.

I am using this in conjuction with the native knock_on ability (which also has it's difficulties), and am liking the combination of the two!

To enable knock on in a terminal

echo 1 > /sys/devices/i2c-3/3-004b/knock_on

You can also do it directly by going to the file. DO NOT use the knock on code in an init.d file, or you will be going into recovery to delete said file;)

If somebody would like to make a script/app to turn both of those on at once, it would be greatly appreciated.

Let me know what you guys think of Row, which you can change to using Trickster Mod or other tool. If you like it better, I may make it default.

The other changes are minor, but may have some impact on how smooth the device feels online. Enjoy!
[G Pad 8.3 Android Development] cam30era:
Swipe to sleep works for me, too. None of the other mods, including native knock are working. Thanks for your work on this.
[G Pad 8.3 Android Development] sleekmason:
Have you tried navigating to the file itself for knock_on in the path above, and imputing a "1" and saving? Please try that and let me know! There is no reason it shouldn't work to you...
[G Pad 8.3 Android Development] cam30era:
Yes, that worked. Thank you.
[G Pad 8.3 Android Development] bbubelis:
Excellent Kernel

Sleekmason - excellent kernel. I love Row and Interactive as my scheduler and governor. All we need now is usb fast charge and Faux Sound compatibility to make this kernel really rock!
[G Pad 8.3 Android Development] sleekmason:
Thank you. Row will be default in the next release. I am looking at both the other items you mention, and will let everyone know if I can/will implement them. Still working on sweep2wake as well, but it's looking like a switch to turn on sweep2wake and knock_on at the same time will be the ticket, as at least those are working.

Anybody have a quick solution for a switch in an app?
[G Pad 8.3 Android Development] cforlife:
Gamma

My device is unlocked, and rooted. I used ADB to test out the kernel to see the gamma changes and it looks the same. I do see in the kernel version in about tablet.

I have also tried installing it in the recovery and i still don't see correct gamma. The dark's are way too dark. Is there something I'm missing?
[G Pad 8.3 Android Development] sleekmason:
You can try screen adjuster apps. The correction in this kernel is due to compiling with a newer toolchain, and is not dramatic in it's improvement, just removes the lousy undertones.

Mine looks great. I have absolutely no problems with the screen after changing compilers, and others have reported the same. Maybe your tablet is bad?
[G Pad 8.3 Android Development] sleekmason:
Update- New Kernel Added - Sleekai5.4

Addition of Faux Sound Control - Can be adjusted with trickstermod or Faux sound control from the playstore. Simple options for headphone gain and more.

Changed the default scheduler to Row. Seems smoother, maybe.

Reverted wifi buffer cache back to disabled - couldn't see any difference. If somebody else does let me know and I will re-enable it.

Removed tap2wake as an option to clean it up some. Sweep2wake and knock-on still exist, and can be enabled by methods in the ablove posts

Best Regards, Sleekmason
[G Pad 8.3 Android Development] Niksunen:
Can you make this kernel to work v500? Because there is nobody who make / develop kernel to v500 at the moment and that sucks...
[G Pad 8.3 Android Development] sleekmason:
Sorry, my kernel is only for the V510 GPE. Any questions about other kernels/devices should be addressed in their specific threads. I doubt that [MENTION=3210378]id10terror[/MENTION] has abandoned his kernel.

He has been very busy making ROM updates for the 500.
[G Pad 8.3 Android Development] id10terror:
I haven't abandoned it just yet.. I have just been really busy with work and real life, and my spare time has gone to playing with the Kit Kat leaks\releases. :D

I'll probably discontinue development when the Official US Kit Kat 4.4.2 release gets here and hopefully the LG source drops. Anyways, who knows how much longer we'll have to wait for the source to be released.
[G Pad 8.3 Android Development] sleekmason:
I compiled in Faux sound control for ya, but I'm not going to mess with the fast charge. Too easy to mess up someone's device.

[MENTION=3210378]id10terror[/MENTION], thank you for all your hard work!
[G Pad 8.3 Android Development] bbubelis:
Thank you for Fauxsound update!

Sleekmason - Fauxsound mod works great! Thank you. However, FauxSound interface reports that "kernel sound driver 2.1+ is required" to access new controls that were added.
[G Pad 8.3 Android Development] sleekmason:
Yeah, saw that. The version I compiled in is not his latest, as the latest version isn't supported by our device... But, he may be talking about the driver for the tablet itself (as is implied), in which case, find me the driver and I'll update it!
[G Pad 8.3 Android Development] rebretz000:
Thanks for the kernel.
[G Pad 8.3 Android Development] sleekmason:
NEW​

For those that are interested, I made an application to toggle knock-on and sweep2sleep after bootup or restart.

The apk is in the third post of this thread, located HERE

This is a simple application made so you don't have to edit the files manually.

You will want to install and put the icon somewhere on your homescreen, as it will need to be enabled after each boot.

This is for your protection as kinock-on, if enabled before or during boot will freeze your screen.

To disable, simply restart your device.

Let me know how it works for you!