yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] shumash:
[SKZ Update] 14 FEB 2017

Update available.

CHANGELOG

-> 14FEB18
- merge upstream. LZ4 and zram restored.

NOTE: Ability to change the minimum frequency restored. To minimize the lags in the ROM, use the ROW (or deadline or noop) scheduler. I'm looking into other schedulers that might work well in the compressed environment.

Enjoy
[TouchPad Development] garux:
Is it safe to change the sync threshold from 1512 to 1836 in CPU?
[TouchPad Development] shumash:
No way to know; it is for me. Don't ask, do. The worst that will happen is that you'll have to do a hard boot.

https://xdaforums.com/showpost.php?p=70421394&postcount=38

https://xdaforums.com/showpost.php?p=70972471&postcount=105
[TouchPad Development] shumash:
[SKZ Update] 22 FEB 2017

Update available.

CHANGELOG

-> 22FEB18
- Add darkness governor

This governor seems to be a very good selection with the noop scheduler. Very snappy.

NOTE: I've changed the mirror server to MediaFire.

Enjoy
[TouchPad Development] BGrosse:
Shumash,

I have 2 questions:

1.) do you know what will happen to the mobile data module(s), when this your kernel is flashed on a 4G TP running Evervolv's 7.1.1 build? Will 4G service still work?

2.) I have a 32G WiFi TP here, which is not able to run your kernel. It boots (sometimes) to the GUI, but then screen goes blank and it reboots. It's simply not stable. Is there a possibility to have your kernel set to a slightly slower frequency (lets say 1728 or 1782 MHz) and to push it up with Kernel Adiutor to the max frequency whichever it is on a specific TP, so that even "slower" TPs which are not able to get the highest frequencies out of the CPU can also run your kernel?

On my TP 1782MHz with the standard Evervolv kernel is actually OK and stable and I really want to test your kernel but cannot... :(

Thanks for feedback! :highfive:
[TouchPad Development] captainmorris:
Hey Shumash, thanks for your work on the TP. I absolutely love the added options in your kernel, but I'd like to second the request for you to ship your kernel with a lower starting clock speed. My TP as well cannot handle 1836. If I wait for Kernel Adiutor to apply settings, it never happens as the TP locks up before KA can lower the clock speed. If I jump into KA as soon as it appears on my home screen, I will usually get into CPU settings and lower the clock speed manually before things lock up, but it would be nice to not have to worry about it. Other than that one thing, I absolutely love your kernel! Thanks again for your continued support of our TPs.
[TouchPad Development] shumash:
I don't know what you guys are doing, but the default frequencies are1512 max, 384 min, interactive governor, bfq scheduler. Same as ev stock. If you're having problems, make sure you're 'set on boot' kernel settings are off before you flash. Check that Toolbox isn't overriding KA..
[TouchPad Development] captainmorris:
Thank you Shumash. When I jump into KA before my TP locks up, my 'set on boot' settings have not applied yet, which are 1728/384 darkness noop, and what I see going on, pre-'set on boot', is 1836/384 interactive bfq. The next time I update, I'll try it with 'set on boot' turned off and see if that helps. It does seem odd that the max frequency would be the only variable to change during the boot up process, and it's not even to my 'set on boot' settings. I'll check to see if the same is happening with the Evervolv kernel and I just didn't notice because of the lower max frequency. It kind of defeats the purpose of 'set on boot' if this is true though, lol! I'll update you after my next update. Thanks again.
[TouchPad Development] BGrosse:
Hmmm... strange! I just reset'ed every setting in the TP Toolbox to default, disabled every setting in kernel adiutor, rebooted and every time max is 1782, min is 384 with interactiv and BFQ (even if I reduced the max frequency to 1512). I then installed your latest kernel via TWRP and the TP does not boot to the UI. It gets stuck while it is loading (evervolv animation running, then stopping after a while) and thats it. No chance to get into Android and check the settings...

All this is performed with a fresh installation of the latest evervolv build (02-25) & TWRP 3.03 and some apps of course (but nothing special in this concern except kernel adiutor).
[TouchPad Development] captainmorris:
Ok, I turned off all the 'set on boot' in KA. I don't use Toolbox, but I checked it anyway, and no 'set on boot' there either. To make sure I was getting default settings at boot, I set KA to 1728/432, dyninteractive, row, all without 'set on boot', just to see if any settings were being carried over anyway. Then I booted into TWRP 3.0.3.0 and installed Evervolv 2/25, Shumash 2/22 kernel, and OpenGApps pico 2/26. I then wiped cache and dalvik(ART) cache, and rebooted Evervolv. It locked up in the boot animation (which it always has when I've installed your kernel...I forgot to mention that before...I then performed the home/power button reset and it booted up to my home screen. I quickly checked KA, but not quickly enough. My TP locked up. I did the home/power button reset again. When my home screen came up, I opened KA, and these were the settings that were active : 1836/384, interactive, noop. BFQ was not even an option on your latest kernel. I reduced the max to 1728 to prevent another lockup, and let it settle in. Those same settings remained after settling in. When I have time, I'll update my findings with the Evervolv kernel, though I suspect that the post before this answers that question. I hope this helps! Thanks again!
[TouchPad Development] BGrosse:
That is my experience too except that I lately cannot get into the UI - it always stuck at the boot animation sooner or later and I always had to hard reboot. If you can get into UI and the setting is 1836, this means my TP cannot handle this and therefore hangs. Where is the maximum CPU frequency stored? Can it be manually reset'ed to a lower value? As soon as shumash's kernel is installed, the TP wants to run at 1836MHz... :eek:
[TouchPad Development] shumash:
EDIT: I know what it is. It's an ev commit that removed the min/max settings in the defconfig. I'll fix it tomorrow.
[TouchPad Development] shumash:
[SKZ Update] 272 FEB 2017

Update available.

CHANGELOG

-> 27FEB18
- Revert tenderloin: disable CONFIG_MSM_CPU_FREQ_SET_MIN_MAX

This should fix the issues with the kernel starting at max. frequency.

Enjoy
[TouchPad Development] BGrosse:
Thanks shumash! This worked flawlessly. Now we have a new device for playing with... :)
[TouchPad Development] Nomad1600:
[MENTION=1009123]shumash[/MENTION] is there an issue with downloads ? I have struggled to download and flash the 2/27 version of the kernel onto my Touchpad running the latest (3/13) Evervolv using TWRP 3.030. Says zip file is corrupt. Tried both the primary (AndroidHost) and secondary (AndroidFire) and tried both primary and mirror locations.
[TouchPad Development] shumash:
There's 125 total downloads and yours is the only report of corruption. I just downloaded it and checked it for errors with none reported. If you're not already doing it, download it to a PC and copy it to the sdcard on the TP. If you are, try downloading it directly to the TP. FWIW, I always boot into TWRP first, then connect the usb cable and copy it directly from TWRP to my flash directory, then flash it.
[TouchPad Development] Nomad1600:
Ok, i will try that, thanks.

UPDATE: Thanks, that worked. :)
[TouchPad Development] shumash:
SKZ Kernel OC to 1944 KHz

With the help of HP_Touchpad, I've determined that at least his TP will OC reliably to 1890 KHz and semi-reliably to 1944 KHz. Mine won't. I usually won't release anything that I can't test, but I'm willing to post a build with a max frequency of 1944 KHz if most of you want me to. Vote here
[TouchPad Development] shumash:
[SKZ Update] 21 MAR2017

Update available.

CHANGELOG

-> 21MAR17
- Overclock to 1944 KHz

NOTE!: The kernel has the same stability up to 1836 KHz, so if you decide to try the higher frequencies, be sure and UNSET THE 'APPLY AT BOOT' option in your kernel tuner app. If your tablet can't handle the higher frequencies, it will either freeze or reboot. If it freezes, you will have to do a hard boot (hold power and HOME key simultaneously until it reboots). It should revert back to the default frequency of 1512 KHz max, 384 KHz min., but if it doesn't, Kernel Adiutor (KA) has a delay in setting the options. Get into KA as soon as you can after it reboots and set the CPU options to a stable setting.

Due to the generosity of HP_TOUCHPAD, I may be getting a testing TP that can handle higher frequencies. If so, stay tuned for the possibility of OC'ing the tablet to 2160 KHz and possibly higher GPU frequency!

Enjoy
[TouchPad Development] BGrosse:
I would love to vote, but get a page saying

"You've reached the end of the Internet

The page you're looking for can't be found. (404)

Try these:

Make sure the URL is correct.

Has this poll or presenter been deleted?"

BTW, does anybody know what are the default values of the CPU voltage and what are the maximum voltages? I would like to test overclocking with adjusting the voltages for each frequency above what my CPU can work at with no overvoltage, but don't wanna risk a death due to overvolting to hard... :(
[TouchPad Development] shumash:
No need to vote; already posted. You can see and change the voltages at each frequency using the CPU Voltages option in KA. I've set an upper limit of 1450 mV currently, so any setting above that won't take (although it will show as being set.) You will see an error message in the dmesg stating that it couldn't go to that setpoint.
[TouchPad Development] BGrosse:
OK Shumash,

my actual testing TP for Evervolvs 7.1.1 on f2fs can also run 1890MHz stable with no overvolting and runs at 1944MHz also fine while not doing something memory intensive. Running Firefox let it freeze.

As a sidenote: I was not able to let it run better [MENTION=3385213]1944[/MENTION]MHz with several overvolting settings. Are you sure, the voltage settings are really physically applied? If the CPU core is the problem, a higher voltage should help to overcome (at least at 1944MHz, much higher speeds >2GHz may also not be achieved when raising the voltage). But if the problems came more from communication with the flash or RAM which are not affected by the voltage settings, it is clear that raising the voltage does not help anymore.

So can we - with your help - debug, where the freezes may come from? :confused:
[TouchPad Development] shumash:
As I posted, I limited the maximum voltage to 1450 mV, so anything higher won't take. Until I get a tablet that can handle the higher voltages (thanks HP_TOUCHPAD) and can test them, I don't want to be responsible for someone cooking their voltage regulator by allowing voltages beyond a safe point. That said, once I get it, I will appreciate any help I can get.
[TouchPad Development] BGrosse:
OK, thanks for that. Let me know when we can assist you in figure the limits out (even if you need another Touchpad :p). Would be glad to help out! :cowboy:
[TouchPad Development] HP_TOUCHPAD:
I did have the same results with the Touchpad that Shumash will get tomorrow when running at 1944MHz, if possible that the RAM needs to adjusted for a higher frequency as well, just like when you overclock a desktop PC. I did a test of using 384Mhz as the only frequency with 700mV and 1450mV. It works on both settings with no issues, but I am now sure if is really running or using that voltage.
[TouchPad Development] Nomad1600:
Was wondering if there are any guidelines or recommended settings anyone has gook luck with. I am completely stock right now, and while its probably safe to experiment it would also be helpful to see what others have found in their experimentation. If it matters i am on latest Evervolv.
[TouchPad Development] shumash:
[SKZ Update] 27 MAR 2017

Update available.

CHANGELOG

-> 27MAR17
- Adjust overclock and voltage settings

EDIT: I screwed up and failed to change a couple of additional settings to get the 1600 mV max voltage. The 3-27 upload has been deleted and replaced with a 3-29 file that correctly sets the max allowable voltage. And I may have spoken too soon about the 1944 KHz stability; it's starting to become unreliable.

This update has clock speeds up to 2160 KHz enabled and a maximum allowed voltage of 1600 mV. I have reliably run with the preset voltages at 1944 KHz max, 192 KHz using the following settings: dancedance governor, schedule workqueues on awake cpus on, cpu hotplug intelliplug on, GPU 266/320 MHz, tripndroid scheduler, kernel samepage merging on. Note that the latest 3/28 ev update removes superuser from the ROM, so you will lose root and will not be able to use Kernel Adiutor. To fix it, install SuperSu from recovery. If you try out any of the frequencies above 1944 and/or change voltages, report back here.

Thanks to the generosity of HP_TOUCHPAD, I received the tablet I have been using to test higher clock speeds. Thank him a lot.

NOTE!: The kernel has the same stability up to 1836 KHz, so if you decide to try the higher frequencies or change the cpu voltages, be sure and UNSET THE 'APPLY AT BOOT' option in your kernel tuner app. If your tablet can't handle the higher frequencies or voltages, it will either freeze or reboot. If it freezes, you will have to do a hard boot (hold power and HOME key simultaneously until it reboots). It should revert back to the default frequency of 1512 KHz max, 384 KHz min., but if it doesn't, Kernel Adiutor (KA) has a delay in setting the options. Get into KA as soon as you can after it reboots and set the CPU options to a stable setting.

Enjoy
[TouchPad Development] HP_TOUCHPAD:
That was a fast update! I tried it but on my end is shows the maximum voltage at 1450. If I change it to 1600 it only goes to 1450
[TouchPad Development] shumash:
See the update post edit.
[TouchPad Development] HP_TOUCHPAD:
It does go to 1600 voltage at least that is working. I set up CPU to 1890 and 1600 and it works. Is there any App that will show the voltage been use in real time? It will help for the regular user like me to troubleshoot with different settings. Thanks for your work!
[TouchPad Development] BGrosse:
Thanks for that! I just tried the new kernel and it works. Because I know for my actual TP the 1890MHz is the stable limit, 1944MHz is the edge and 1998MHz is a no go, I raised the voltage limit for 1944 to 1600mV and set the max CPU to 1944MHz. Unfortunately this does not really work. After some time it freezes also like with the standard voltage. It seems overvolting does not change the MHz limit we can get.

What about your investigations [MENTION=8005714]HP_TOUCHPAD[/MENTION]? Your tablet was also fine at 1890MHz, but not stable at 1944MHz, right? What does yours at 1944MHz with 1600mV?

Anybody else?
[TouchPad Development] HP_TOUCHPAD:
The Tablet that I was able to set at 1944 and not stable I sent it to Shumash. The Tablet that I am testing currently only goes to 1890. I was setting up to do some testing and came to a surprise, I will try to explain it very simple:

I started testing the Overclock_Version_29 with Ev_Nightly_3_19. I was able to run it at 1890 with the default voltage and even lower to 1290 at 1890. I decided to start testing with the current Ev_nightly_03_29 and using the Overclock_Version_29. Setting the speed to 1890 will reboot immediately or freeze (using the default voltage).

I changed the voltage to 1600 at 1890 speed and works, if I lower the voltage less than 1600 it reboots. I also installed Lineage_14.1_2017_03_29 and try to see the voltage setting using Kernel Adiutor, but is not listed (not available in the settings, also the kernel maximum speed is 1782 and not stable when testing at that speed.

Something is changing in the ROM besides the Kernel that is manipulating something. Why do I need to set the voltage to 1600 to get 1890 to work in the new ROM when it was working at 1375 before?
[TouchPad Development] shumash:
Nothing available to monitor cpu voltage, just frequencies and other stuff.

CpuFloat

I am running 1890 with the preset voltage (1350 mV) without problems on ev 3/28. There are no tenderloin changes in the 3/29 ROM. The only important thing that has changed in 3/28 is the elimination of su requiring that you install SuperSu from the Playstore. I'm playing with the L2 voltages and bandwidths to see what I can make work. The voltages set in invisiblek's kernel are the same as mine up to 1782, but he hasn't implemented a L2 boost in his. You can see those settings here
[TouchPad Development] HP_TOUCHPAD:
In Androidx86 under DEVELOPER OPTIONS --> Monitoring ( Show CPU usage ) Screen overlay ( Showing current CPU usage.

On the two Current Android ROM available for the TOUCHPAD is not available only Strict Mode enable and Profile GPU Rendering. It could probably help see it as an overlay when it freeze, just an idea.

If the voltage for 1890 is set at 1600, does that mean that the CPU will run at that voltage constantly or will it fluctuate depending of its needs for more electricity?
[TouchPad Development] HP_TOUCHPAD:
I am now using CPU Adjuster to set up the CPU speed. I am able to run 1890 at 1359175mV and also at 1450200 mV which is the maximum allow. I do not see the option to increase it until 1600 voltage. The maximum for all the speed is 1450200 mV.
[TouchPad Development] shumash:
The voltage regulator will set the bus voltage for 1600. It will vary slightly as the load changes, but it will be more or less constant. The frequency is what fluctuates. Adding stuff into DEVELOPER OPTIONS is a ROM issue which I don't deal with. It was removed by Google and would have to be restored by the ev team if they so desired. Try the CpuFloat app I suggested; it does the same thing.
[TouchPad Development] shumash:
That's an app problem that I can't fix. Kernel Tuner has the full voltage table, but it should make no difference what app you use to set the voltages.
[TouchPad Development] HP_TOUCHPAD:
From my basic understanding CPU adjuster is pulling all the numbers ( or range of voltage ) from the Kernel settings. To change 1600 in Kernel Audiutor it must be enter manually (override) but there is no guarantee that is running at that voltage as is already preset to a maximum of 1450. CPU adjuster does not allow to enter any numbers, it will only use the ones present from the kernel.
[TouchPad Development] shumash:
I don't know what you're using this app for, but it just reports cpu statistics. If you are using it to see if the changes you are making in Kernel Adiutor take, you have to close CPU adjuster in Recents and restart it to see any changes. You are wasting your time trying to see if the voltage regulator is actually using the voltage setting. Suffice it to say, that the settings you see in either app are reported through an interface between the app through the system to the kernel using what's called a sysfs interface. That's programmed in the kernel and exposed to the "userspace". Unless settings and values are exposed by the kernel, you can't see them. That's why you get a real-time view of the current frequencies; the kernel is passing them through sysfs to the system that then allows apps that have the proper permissions to use them. Voltage settings are passed through sysfs, but not the real time voltage.
[TouchPad Development] HP_TOUCHPAD:
I am using CPU adjuster to select the CPU speed and voltage. It provides very basic settings that is all that is need it to test the CPU speed and fine tune the voltage. You can add profiles and also "Set state on the fly". Kernel Adiutor is great but offers too many options that do not need to be active just to test speed and voltage. When I set the voltage on Kernel Adiutor manually to 1600, it takes it but is not using it since is preset to 1450, so is misleading. I am only using one APP https://play.google.com/store/apps/details?id=com.ryosoftware.cputweaks
[TouchPad Development] shumash:
How do you know that?
[TouchPad Development] HP_TOUCHPAD:
A very simple test, using Kernel Adiutor set both maximum and minimum frequency to 192Mhz and on cpu voltage enter 1600. Now the CPU is working at only 192 speed using 1600 voltage. The system works with no issues even selecting different types of voltage: Example a range from 1600 to 800, everything works. If every speed has its on working voltage range how can it work using any voltage?

Now uninstall Kernel Adiutor and install CPU Adjuster and try to apply the same settings 192 speed and the maximum allow of 1450, when activating the profile a message will come up at the bottom of the screen " A error has occurred while trying to activate the profile. My guess is something is not allowing for the voltage settings to be change. Kernel Adiutor is not showing any error messages and you think all settings are applied, but in reality is not. I am sure you know how to pull out specific errors messages from the OS. I am only reporting why I see, but you can pull out the evidence!
[TouchPad Development] shumash:
I'm still not sure what you're getting at nor am I sure that you are really testing anything. The voltage changes whenever the frequency changes based on the voltage table. The lower the frequency, the less power is required and resultant voltage. If you set the min and max to 192, that's the lowest energy/voltage requirement, so of course it will work when overvolted between its normal and the maximum. Since you've limited the frequency so it can't change with load, the extra energy is just dissipated as heat.
[TouchPad Development] HP_TOUCHPAD:
If the lowest frequency is working at 1600, then the voltage is not an issue and can be raise to allow for testing of higher frequency as it needs more electricity to run. This is not to be implemented generally, only for testing purposes. I just try this APP, Kernel Tuner https://play.google.com/store/apps/details?id=rs.pedjaapps.kt&hl=en There is an option to increase all voltage by 12.5MV or you can do it manually and the cap of 1600 shows. Is impressive you can select minimum and maximum frequency per CPU core and also a governor per core!
[TouchPad Development] shumash:
So are you are asking me to set a high enough voltage limit that you can cook your TP's power supply? If that's what you want, pm me.
[TouchPad Development] Rolfsted:
I installed Kernel Adiuter but when i open it all I see is "no root" and a question mark.
[TouchPad Development] Nomad1600:
If you installed a recent version of Evervolv the ROM is rootless and you need to flash SuperSU.
[TouchPad Development] Rolfsted:
Oh ok....I have a zip file of super user and flashed it, but doesn't seem to take. I can't get adaway to work either
[TouchPad Development] BGrosse:
Which one and from where did you get it? There are many out there... The proven one was already posted (here or in the nightly thread). And you need also the SuperSU app from the play store. Once you have got it working, you need always to reflash the SuperSU zip file along with every new nightly and maybe Shumash's kernel. With that you settings for being root will be kept for all apps and you don't need to do anything else when you switch from one nightly to another.
[TouchPad Development] Rolfsted:
I'm not sure where I got it. I have no clue what I'm doing.....I just read everything I can and go for it.

I know the newest nightly isn't running like the others. I may just start over and stop trying to tweak stuff and just be happy this touchpad is still usable.
[TouchPad Development] shumash:
1944 KHz

FWIW, I have been running at 1944 KHz with the 3-29 update for two days now without problem. I have set my minimum frequency to 384 because I suspect that some of the freezes are display/touch related. Here's the settings that currently work for me:

Max 1944, Min 384

Dancedance governor

1944 KHz voltage set to 1500 mV

Intelliplug enabled

GPU 266/320

Scheduler noop or tripndroid

KSM enabled.