I upgraded my Touchpad to Latest version of Nougat yesterday.
However as soon as I started loading a few basic apps it started to not respond at all & ends up having to be continually rebooted. It's slightly better now but still has to be rebooted every so often & very often locks up for 30-60 seconds at a time.
I've checked all available space on storage & appears to be all correct with what was in the instructions, plus this was a clean install (the upgrade from kitkat was even worse!) & was done via TWRP with latest ROM, GAPPS etc. I'm aware Nougat is not the finished article but judging by other comments on the forum their experience is somewhat better than mine (using the TP right now us very frustrating).
This is being installed on a 32mb TP so storage isn't an issue at all. I've done a number of upgrades over the last few years but this is the first time I've run into these sort of problems.
Any help or suggestions would be greatly appreciated.
Thanks
Dellboy17
Exact same issue i am also facing.if somebody installed a fluidic rom means tell me ivwill also follow.
What's a fluidic ROM?
Dellboy17 said:
What's a fluidic ROM?
Click to expand...
Click to collapse
i think they mean 'one that operates in a fluid (smooth) manner'. i also have this problem on most n rom's i've tried, but addmittedly, my touchpad is near nand exhaustion. (and something about the N setups i've tried exacerbates it)
Evervolv 7.1.x lag fix
Dellboy17 said:
I upgraded my Touchpad to Latest version of Nougat yesterday.
However as soon as I started loading a few basic apps it started to not respond at all & ends up having to be continually rebooted. It's slightly better now but still has to be rebooted every so often & very often locks up for 30-60 seconds at a time.
I've checked all available space on storage & appears to be all correct with what was in the instructions, plus this was a clean install (the upgrade from kitkat was even worse!) & was done via TWRP with latest ROM, GAPPS etc. I'm aware Nougat is not the finished article but judging by other comments on the forum their experience is somewhat better than mine (using the TP right now us very frustrating).
This is being installed on a 32mb TP so storage isn't an issue at all. I've done a number of upgrades over the last few years but this is the first time I've run into these sort of problems.
Any help or suggestions would be greatly appreciated.
Thanks
Dellboy17
Click to expand...
Click to collapse
Sivabalan said:
Exact same issue i am also facing.if somebody installed a fluidic rom means tell me ivwill also follow.
Click to expand...
Click to collapse
speakxj7 said:
i think they mean 'one that operates in a fluid (smooth) manner'. i also have this problem on most n rom's i've tried, but addmittedly, my touchpad is near nand exhaustion. (and something about the N setups i've tried exacerbates it)
Click to expand...
Click to collapse
Hey guys install Shumash's SKZ Kernel and apply the following changes below, your user experience should drastically improve.
Extras: SKZ-OC Kernel recommended for Evervolv 7.1.x
[KERNEL]SKZ Overclock Kernel for Evervolv [1836KHz CPU/320MHz GPU]
Install notes:
-Install the SKZ-Kernel by flashing this zip file here through TWRP recovery
-Remove the Kernel by flashing a Evervolv ROM with TWRP recovery
-Enable Root permissions by flashing this Supersu v2.46 zip here with TWRP recovery
-You will need to update the Superuser binaries once your system boots.
-Install the Kernel Adiutor app to Overclock your CPU here
Recommended settings:
Note: These settings should fix the lag and touchscreen issues.
CPU
Set on boot = on
CPU Maximum Frequency = 1728MHz
CPU Minimum Frequency = 648MHz
CPU Governor = smartmax or dancedance
Schedule workqueues on awake CPUs to save power = enabled
CPU Hotplug
IntelliPlug = enabled
GPU
Apply on boot = on
GPU 2D Maximum Frequency = 266MHz
GPU 3D Maximum Frequency = 320MHz
GPU Governor = simple
I/O Scheduler
Scheduler = enabled
Scheduler = tripndroid
Kernel Samepage Merging
Kernel Samepage Merging = enabled
Low Memory Killer
Adaptive Low Memory Killer = enabled
Profile = aggressive
Misc
TCP Congestion Algorithm = sociopath
RolandDeschain79 said:
--SNIP--
[KERNEL]SKZ Overclock Kernel for Evervolv [1836KHz CPU/320MHz GPU]
--SNIP--
Click to expand...
Click to collapse
Note that while you can download the most current kernel from the links given, the thread is no longer being updated.
Devs Base note in the OP
shumash said:
Note that while you can download the most current kernel from the links given, the thread is no longer being updated.
Click to expand...
Click to collapse
Would it be possible to mention this in the OP of your old thread? Every time I add links to devs base the mods remove it here at XDA :silly:
Edit: Also worth mentioning that increasing the min CPU frequency to 600+ will help with the Evervolv lag issues.
Info about the move to Devs base for all those who haven't heard.
RolandDeschain79 said:
Would it be possible to mention this in the OP of your old thread? Every time I add links to devs base the mods remove it here at XDA :silly:
Edit: Also worth mentioning that increasing the min CPU frequency to 600+ will help with the Evervolv lag issues.
Info about the move to Devs base for all those who haven't heard.
Click to expand...
Click to collapse
wilco
speakxj7 said:
i think they mean 'one that operates in a fluid (smooth) manner'. i also have this problem on most n rom's i've tried, but addmittedly, my touchpad is near nand exhaustion. (and something about the N setups i've tried exacerbates it)
Click to expand...
Click to collapse
Yes correct!!
---------- Post added at 11:02 PM ---------- Previous post was at 10:57 PM ----------
RolandDeschain79 said:
Hey guys install Shumash's SKZ Kernel and apply the following changes below, your user experience should drastically improve.
Extras: SKZ-OC Kernel recommended for Evervolv 7.1.x
[KERNEL]SKZ Overclock Kernel for Evervolv [1836KHz CPU/320MHz GPU]
Install notes:
-Install the SKZ-Kernel by flashing this zip file here through TWRP recovery
-Remove the Kernel by flashing a Evervolv ROM with TWRP recovery
-Enable Root permissions by flashing this Supersu v2.46 zip here with TWRP recovery
-You will need to update the Superuser binaries once your system boots.
-Install the Kernel Adiutor app to Overclock your CPU here
Recommended settings:
Note: These settings should fix the lag and touchscreen issues.
CPU
Set on boot = on
CPU Maximum Frequency = 1728MHz
CPU Minimum Frequency = 648MHz
CPU Governor = smartmax or dancedance
Schedule workqueues on awake CPUs to save power = enabled
CPU Hotplug
IntelliPlug = enabled
GPU
Apply on boot = on
GPU 2D Maximum Frequency = 266MHz
GPU 3D Maximum Frequency = 320MHz
GPU Governor = simple
I/O Scheduler
Scheduler = enabled
Scheduler = tripndroid
Kernel Samepage Merging
Kernel Samepage Merging = enabled
Low Memory Killer
Adaptive Low Memory Killer = enabled
Profile = aggressive
Misc
TCP Congestion Algorithm = sociopath
Click to expand...
Click to collapse
Thanks buddy!! Actually fed up with the lag issue I have reverted to milaq's kikat 4.4.4. . Tonight will revert back to evervolv and will update here.
One doubt as the min cpu freq is 648 mhz will it not eat in to the battery??
Thanks,
Sivbal.
Sivabalan said:
Yes correct!!
---------- Post added at 11:02 PM ---------- Previous post was at 10:57 PM ----------
Thanks buddy!! Actually fed up with the lag issue I have reverted to milaq's kikat 4.4.4. . Tonight will revert back to evervolv and will update here.
One doubt as the min cpu freq is 648 mhz will it not eat in to the battery??
Thanks,
Sivbal.
Click to expand...
Click to collapse
Have flashed the latest test build and applied the above settings . its better now . will report after some days of usage.
Thanks for testing
Sivabalan said:
Have flashed the latest test build and applied the above settings . its better now . will report after some days of usage.
Click to expand...
Click to collapse
Thanks for testing it out and reporting back:highfive: I've found the battery drain is only slightly higher but fixing some of the lagging is worth the trade off.
RolandDeschain79 said:
Thanks for testing it out and reporting back:highfive: I've found the battery drain is only slightly higher but fixing some of the lagging is worth the trade off.
Click to expand...
Click to collapse
Also in toolbox if I disable aosp mode,the touchpad become very laggy and YouTube is not at all responding. But if we enbale aosp mode and disable all toolsbox functions...touchpad is useable.
Guys now after a long time I formatted my data and all the partitions then installed the evervolv 7.1.2 test build. Skz kernel overclocked to 1728. Also gpu overcolcked to 320. Kernel samepage killing enabled.cpu profile set to interactive. The rom is performing good. Please try.
Sent from my Touchpad using Tapatalk
---------- Post added at 09:56 AM ---------- Previous post was at 09:49 AM ----------
shumash said:
Note that while you can download the most current kernel from the links given, the thread is no longer being updated.
Click to expand...
Click to collapse
Guys now after a long time I formatted my data and all the partitions then installed the evervolv 7.1.2 test build. Skz kernel overclocked to 1728. Also gpu overcolcked to 320. Kernel samepage killing enabled.cpu profile set to interactive. The rom is performing good. Please try.
Sent from my Touchpad using Tapatalk
Is this much better than the Android 6 builds? The last decent one I had was JCSullins 5.1, my current 6.0.1 (22/08/2016) takes 2-3 longer to start up, is noticeably slow/laggy and has no USB OTG support. I notice that the Android 7 builds have no camera, Bluetooth and I need to overclock to have a good experience? I might go back to 5.1 again...
theronkinator said:
Is this much better than the Android 6 builds? The last decent one I had was JCSullins 5.1, my current 6.0.1 (22/08/2016) takes 2-3 longer to start up, is noticeably slow/laggy and has no USB OTG support. I notice that the Android 7 builds have no camera, Bluetooth and I need to overclock to have a good experience? I might go back to 5.1 again...
Click to expand...
Click to collapse
The newer evervolv builds have both working camera and Bluetooth but yes I'd recommend getting shumash's kernel and overclocking for the best experience. However if you're already using CM12 try updating to Milaqs latest builds here It might fix the issues you're having. I generally find Milaqs CM11 to be the most stable rom for your daily driver. Let me know how the newer builds of CM12 workout for you.
RolandDeschain79 said:
The newer evervolv builds have both working camera and Bluetooth but yes I'd recommend getting shumash's kernel and overclocking for the best experience. However if you're already using CM12 try updating to Milaqs latest builds here It might fix the issues you're having. I generally find Milaqs CM11 to be the most stable rom for your daily driver. Let me know how the newer builds of CM12 workout for you.
Click to expand...
Click to collapse
Thanks, I'm just deciding whether to go with JCSullins 12.1 from Jan 2016 or Milaq's 12.0 from Aug 2017. Tempted to go for 12.1 even though the actual rom is much older, I don't think much could have changed.
RolandDeschain79 said:
Hey guys install Shumash's SKZ Kernel and apply the following changes below, your user experience should drastically improve.
[...]
Misc
TCP Congestion Algorithm = sociopath
Click to expand...
Click to collapse
Thx a lot !! It saved my HPTP.
Yesterday i flashed the last evervolv, and looked for some improvements on xda-dev, and I saw your post. After flashing, I tried to apply these settings.
What a change !! The TouchPad is now usable.
My plan is to use it (with the touchstone) as a screen for my home automation. It was impossible, but now it seems to be responsive enough !
Thanks again.
Related
[GT-i9195][cm11] - [ROM](Feb.2016)&[kernel](ECOACTIVE & ECOPLUG)(OC/UV)(20151210)
This is a GT-I9195 CM11 kernel highly optimized to best possible performance and energy efficiency.
It may work on Slim (confirmed), AICP (confirmed) and Carbon Rom (confirmed) as well.
It will not work on any Samsung Stock based ROM.
- built from latest avalable CM sources
- CPU OC: 1998 Mhz (light: 1782 MHz) (default and max.)
- reworked freq- tables (unique 108 MHz-steps) for fast scaling
- CPU UV: -50mv (light: -25mv) (default, adjustable)
- GPU OC: freq steps changed to 192-400-608 MHz (light: 192-400-554 MHz)
- L2 OC/UV for extra performance (stock setting is a bottleneck, especially with OC)
- improved bus scaling
- RAM UV
- adjusted msm_thermal to prevent too much thermal throttling under heavy load
- added new "ECOACTIVE" governor and set as default
- added new "ECOPLUG" hotplug driver and set as default
- added FIOPS IO Scheduler and set as default
- added some more commonly used IO schedulers
- added fast random (and enabled via init.d)
- built with official gcc 4.8 with -O3 flags
"ECOACTIVE" is the ultimate governor for lag free performance and good battery life at the same time. It's based on interactive governor. It has a special input gain including the menu, home and back buttons. Separate input gain, fullspeed and eco/screen off phases minimize the use of high frequencys whithout slowing down the device noticably. The upscaling is more agressive during the input phase (default 1s). In the following fullspeed phase (default 10s, set to 0 for unlimited) full performance is allowed. The third phase is configured for battery saving usage while reading, watching videos, music listening or when the screen is off. This ensures maximum responsiveness and best gamig experience along with best possible battery life when reading, listening to music etc.
"ECOPLUG" is an alternative hotplug driver based on AutoSMP. It works much snappier on our device than the stock msm-mpdecision. On default setting second core is down when screen is off.
Everything is fully "pretweaked".
Flash from recovery, enyoy... no need to adjust anything via init.d or app.
Dont flash this kernel if you don't know how to fix problems after flashing !
Make a backup before flashing this kernel !
The hardware parameters are adapted near to the limits of my phone. This means this kernel will not work if your devices hardware cannot handle the OC/UV.
If you are lucky you run the fastest kernel available for your phone
If your phone doesn't run with the "lombartz kernel" you may try the "lombartz light kernel" with less agressive OC/UV.
My latest pure CM11 ROM build (Feb. 2016):
https://drive.google.com/open?id=0B-1RyGtdRvCwWEVfc0ZhTTRzdXc
If you use Xposed framework you need to flash XposedFix after ROM.
regards,
lombartz
...updated.
this kernel is amazing but i have a problem when i connect the smartphone at bluetooth radio. In this case my smartphone freeze and always reboot.
sorry for my english
Hi, thanks for yor feedback Have you already checked if you have the same problem with the last official CM11 kernel from 20150105 ?
regards,
lombartz
edit: tested with my laptop as bluetooth- speaker with no problems. My actual Version is heavily tweaked at the Moment but nothing changed with audio or bluetooth.
Anyone else with bluetooth- playback issues out there ?
edit: found a possible reason for the problem. hope it's fixed in new version (see OP)
Thank you for this. Any chance to include f2fs into the kernel?
bongster said:
Thank you for this. Any chance to include f2fs into the kernel?
Click to expand...
Click to collapse
It's already included, I tested it just now with my actual Version via USB OTG a d could read and write. It should also work with the 20150212 Version.
regards,
lombartz
lombartz said:
It's already included, I tested it just now with my actual Version via USB OTG a d could read and write. It should also work with the 20150212 Version.
regards,
lombartz
Click to expand...
Click to collapse
Strange. My data and cache partition are f2fs and with the f4ktion cm11 kernel all is working well, but after installation of your kernel I'm stuck at the boot logo.
bongster said:
Strange. My data and cache partition are f2fs and with the f4ktion cm11 kernel all is working well, but after installation of your kernel I'm stuck at the boot logo.
Click to expand...
Click to collapse
Here is a Version without OC/UV or other tweaks but with all CM Updates. Its about 20% slower than the tweaked Version but more actual than the V20150212.
If this one boots your phone doesn't like my OC/UV settings...
lombartz said:
Here is a Version without OC/UV or other tweaks but with all CM Updates. Its about 20% slower than the tweaked Version but more actual than the V20150212.
If this one boots your phone doesn't like my OC/UV settings...
Click to expand...
Click to collapse
Thank you very much! I will test it and report back! If I understand it right, f2fs support is also in stock cm11 kernel?
I never tried it...
bongster said:
Thank you very much! I will test it and report back! If I understand it right, f2fs support is also in stock cm11 kernel?
I never tried it...
Click to expand...
Click to collapse
Yes.
lombartz said:
Yes.
Click to expand...
Click to collapse
No luck. I also tried flashing the latest cm11 nightly with no luck.
If I remember right I've tried the stock kernel some time ago only formatting the cache partition and this didn't work either.
20150212 working nice with latest Carbon 4.4.4
can you please add option to underclock min CPU to 162/270 MHz?
spixy said:
20150212 working nice with latest Carbon 4.4.4
can you please add option to underclock min CPU to 162/270 MHz?
Click to expand...
Click to collapse
This is a technically useless placebo feature and doesn' t save any energy.
The HFPLL has to be used to get the lower frequencys and this will eat the saved energy.
br,
lombartz
bongster said:
No luck. I also tried flashing the latest cm11 nightly with no luck.
If I remember right I've tried the stock kernel some time ago only formatting the cache partition and this didn't work either.
Click to expand...
Click to collapse
Hmm, the reason is the fstab.qcom, /cache and /data is expexted to be ext4.
Can be changed but I dont know how to allow both fs at the moment.
lombartz said:
This is a technically useless placebo feature and doesn' t save any energy.
The HFPLL has to be used to get the lower frequencys and this will eat the saved energy.
br,
lombartz
Click to expand...
Click to collapse
hi, I dont know what HFPLL is (some high frequency PLL), but I trust you
but still, is more battery efficient to hold wakelock with 162MHz than with 384, no? (see my previous post)
But on theother hand, 50mW diference between 162 and 384 MHz isnt realy so large...
spixy said:
hi, I dont know what HFPLL is (some high frequency PLL), but I trust you
but still, is more battery efficient to hold wakelock with 162MHz than with 384, no? (see my previous post)
But on theother hand, 50mW diference between 162 and 384 MHz isnt realy so large...
Click to expand...
Click to collapse
I suppose you mean 50 mV ? The lower UV limit is reached at about 384 MHz anyway.
Youre right with hfpll. Only at 384 MHz the CPU runs with pll8.
If you undervolt @ 384 manually as much as possible you will find that you cannot go noticeably lower if you clock down further.
At the Moment I am testing other tweaks that should be more effective an give some extra performance.
bongster said:
No luck. I also tried flashing the latest cm11 nightly with no luck.
If I remember right I've tried the stock kernel some time ago only formatting the cache partition and this didn't work either.
Click to expand...
Click to collapse
If you like to you can test this. But please make a full backup before because i did not test it myself. I don't want to reformat my phone for f2fs at the moment.
If it boots you are a tester for all the new changes ...
This Version will not run with ext4 /cache and /data partitions.
lombartz said:
If you like to you can test this. But please make a full backup before because i did not test it myself. I don't want to reformat my phone for f2fs at the moment.
If it boots you are a tester for all the new changes ...
This Version will not run with ext4 /cache and /data partitions.
Click to expand...
Click to collapse
Thank you very much!
After app optimisation the phone reboots and after the reboot it hangs at the Samsung logo. Only recovering the old boot image helps. Don't know if the oc is the reason.
Update:
I've tried oc with f4ction kernel and had also a reboot. I guess my CPU is not the best.
bongster said:
Thank you very much!
After app optimisation the phone reboots and after the reboot it hangs at the Samsung logo. Only recovering the old boot image helps. Don't know if the oc is the reason.
Update:
I've tried oc with f4ction kernel and had also a reboot. I guess my CPU is not the best.
Click to expand...
Click to collapse
I am sorry. Should not publish something I did not test myself...
What OC Values did you use with f4ction ?
lombartz said:
I am sorry. Should not publish something I did not test myself...
What OC Values did you use with f4ction ?
Click to expand...
Click to collapse
No problem. I'm aware of the issues that can happen.
Normally I use f4ction as it is with 50uv. For the test I oc'ed to 1998mhz.
This is a kernel for Cyanogen Mod 12.1, which is based on the EvoMix kernel by Alx31TLse, olivieer and SuperHanss (full credits to them). It is compiled by a Linaro 4.9.3 toolchain, which was optimized for Cortex A9 CPUs (thanks to Christopher83). It has a focus on stability, performance, endurance and overclock-ability (roughly in that order).
It uses the original ramdisk of the installed kernel (thanks to osm0sis), for maximum compatibly in the long run and instant adaptability to most source changes of CM. For now, it probably only works with the very latest unofficial CM12.1 built by qsnc (http://forum.xda-developers.com/showpost.php?p=58006383&postcount=1), due to the introduction of new sensor drivers! It should now works with other CM12.1 based ROMs, like crDroid and PAC, too. Please don't report bugs to qsnc, if you are using this kernel!
Features:
CPU: over/under-clock 1728MHz-192 MHz possible
governors: ondemand(plus), intelliactive, wheatley, ElementalX, ...
GPU: over/under-clock 487MHz-27MHz
governors: simple, performance, powersave, ondemand, conservative
File-systems: ext2/3/4, F2FS, exFAT, NTFS
Schedulers: noob, deadline, row, cfq, bfq, sio, fiops, zen, vr
intelli-plug hot-plugger and power saver (disable MPDecision first!)
Voltage Control (OC/UV)
Sound Control 3.x
poweramp controls (loudness enhancements)
screen colour tweaks
full NEON support
KSM support (Kernel Samepage Merging)
multicore power saver (recommended: enabled)
multirom compatibility
...
Performance: about 10% faster than original CM12.1-kernel with same settings, and some additional 20% speed by using maximum over-clocked frequencies (use at your own risk, every device is different!)
Configuration: Kernel Adiutor (https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor) or PerformanceControl 2.2.6 (http://forum.xda-developers.com/devdb/project/?id=600#downloads)
Install: just flash the attached zip with CyanogenMod Recovery, TWRP (http://forum.xda-developers.com/xpe...very-twrp-2-8-7-0-pollux-polluxwindy-t3187811) or CWM
Install a custom recovery first! The simple CyanogenMod Recovery, which comes with most ROMs, is pretty useless anyway..
Uninstall: re-flash the complete ROM (just re-flashing the original kernel is not enough!)
Sources: https://github.com/EvoMix/kernel_apq8064 (to obtain the defconfig: run "unpigz -cd /proc/config.gz")
Special thanks to Alx31TLse for his help and permission to post it!
Changelog:
2015-08-23:
rebuild using latest optimized Linaro 4.9.4 compiler by Christopher83
re-signed zip-file in order to make it compatible to file signature verification
refuses now to be installed by CyanogenMod Recovery
2015-06-13:
added Pollux version (use official nightly or recent unofficial build)
fixed bug in Sound Control's loudness enhancement, that only one speaker worked
removed inteli-active governor, due to random reboots
2015-05-31:
enhanced boot speed and file-system performance
buggy auto-hotplugger removed
reintroduction of CM's MPDecision (re-flash CM12.1 first, before installation!)
2015-05-28:
initial release
IF INSTALLATION FAILS: If the kernel installation is not working (i.e. installation takes less than 5 seconds and you don't see the new bootlogo), reflash latest ROM, reboot into recovery and try to install the kernel again!
XDA:DevDB Information
EvoMix Kernel for CyanogenMod 12.1, Kernel for the Sony Xperia Tablet Z
Contributors
BlackAfghan, Alx31TLse, olivieer and SuperHanss
Source Code: https://github.com/EvoMix/kernel_apq8064
Kernel Special Features: CM12.1 EvoMix kernel, compiled by a Linaro toolchain, which supports OC/OV, intelli-plug, Sound Control, NTFS, exFAT, F2FS, NEON, KSM, ...
Version Information
Status: Stable
Just installed latest unofficial CM12.1 built by qsnc and this kernel. Seems great so far! Boots a lot faster and kritika plays faster!
I'm trying the overcloacking with Kernel Adiutor set to 1728MHz, I've to 3C widgets installed to monitor temperature and such. Great job!
May seem a bit offtopic but how is the combination intelliplug-ondemandplus?
I think i get some lag with this but it may be a placebo
pangiotis24 said:
May seem a bit offtopic but how is the combination intelliplug-ondemandplus?
I think i get some lag with this but it may be a placebo
Click to expand...
Click to collapse
First, I also used this combination, but experienced some lag, too. It is not necessary to enable intelliplug and I'm not sure if it does any good, since hot-plugging is handled by auto_hotplug. Actually it is not even included in the original EvoMix kernel.
I'm now using only intelliactive, which seems to keep the frequencies low most of the time, while producing only minimal lag.
But maybe it is really a matter of believe..
Teella said:
I'm trying the overcloacking with Kernel Adiutor set to 1728MHz, I've to 3C widgets installed to monitor temperature and such. Great job!
Click to expand...
Click to collapse
The over-clocking capabilities of the EvoMix kernel are rather conservative. I personally use it with maximum CPU and GPU frequencies and even a general -50mV under-voltage, and it seems to be perfectly stable. But no guarantee, every device is different!
Thanks for Kernel !
Multirom Patch inclusive ?
phillipssat said:
Thanks for Kernel !
Multirom Patch inclusive ?
Click to expand...
Click to collapse
Yes, I think so. But please try it out and confirm if it works, since I have not tested it!
BlackAfghan said:
First, I also used this combination, but experienced some lag, too. It is not necessary to enable intelliplug and I'm not sure if it does any good, since hot-plugging is handled by auto_hotplug. Actually it is not even included in the original EvoMix kernel.
I'm now using only intelliactive, which seems to keep the frequencies low most of the time, while producing only minimal lag.
But maybe it is really a matter of believe..
Click to expand...
Click to collapse
Traced the cause.After some time with intelliplug+ondemandplus cores 2,3,4 are permanently disabled.Now i am on intelliactive.Very good so far
I've been using Wheatley and OC 1728 for couple days now. No lag, no heat issues, everything is just peachy!
Hi! Can I use this kernel on my sgp321 Pollux? Tried to flash but get error.
Pollux build will be released later...
New build in first post!
pangiotis24 said:
Traced the cause.After some time with intelliplug+ondemandplus cores 2,3,4 are permanently disabled.Now i am on intelliactive.Very good so far
Click to expand...
Click to collapse
Could you please retry it with the new version?
bgx said:
Hi! Can I use this kernel on my sgp321 Pollux? Tried to flash but get error.
Click to expand...
Click to collapse
If you, or anybody else, is able to re-flash the original CM12.1 kernel via fastboot (in case something goes wrong) and is willing to beta-test, write me a PM!
Yes its kexec patched, but we need to make tab z official to multirom app support, problem is...im running out of time, full time job, 10 months old baby ...kernel is time consumer, thanks to BlackAfgan to maintaining it.
More goodies to come
Tapatatrached from my Yuga
So apparently my tablet hates me. I can't get this kernel to actually flash for ****. I'm using the 5/27 CM 12.1 from the OP. Tried both versions of the kernel. It acts as if it flashes but is much too fast and the kernel version is the same. TWRP 2.8.5.0 from the OP link too.
EDIT: Nevermind I guess. Moved it to the root of the internal and renamed it to a shorter filename and it pushed it properly. No idea what was going on.
DarkStarr said:
So apparently my tablet hates me. I can't get this kernel to actually flash for ****. I'm using the 5/27 CM 12.1 from the OP. Tried both versions of the kernel. It acts as if it flashes but is much too fast and the kernel version is the same. TWRP 2.8.5.0 from the OP link too.
Click to expand...
Click to collapse
Try to format /system, reflash CM 12.1, reboot into recovery again, then flash the latest kernel, please.
Alx31 said:
Yes its kexec patched, but we need to make tab z official to multirom app support, problem is...im running out of time, full time job, 10 months old baby ...kernel is time consumer, thanks to BlackAfgan to maintaining it.
More goodies to come
Tapatatrached from my Yuga
Click to expand...
Click to collapse
Great! Thanks for your excellent work. I wish you all the best for your family! They are more important than any device..
BlackAfghan said:
Try to format /system, reflash CM 12.1, reboot into recovery again, then flash the latest kernel, please.
Click to expand...
Click to collapse
Yea I had done that. It only worked after moving it. I also renamed it at the same time so I dunno which fixed the issue.
DarkStarr said:
Yea I had done that. It only worked after moving it. I also renamed it at the same time so I dunno which fixed the issue.
Click to expand...
Click to collapse
I had the same problem, especially when I flashed an already flashed kernel. I never found the actual reason, but at one point it started to work perfectly all the time..
This is due the pretty complicated process of splitting the original kernel of and recreating the new one in real time, on the device. Normally the developer does this on his PC, and releases a directly flashable combination of the actual kernel and a custom ramdisk.
If other people have the same problem persistently, I may publish an conventional kernel. Please report!
Does this work on "[Rom][UB][5.1.x][SGP311]☆Dirty Unicorns v9.3☆ Unofficial +EvoMix Kernel" rom??
So i tested the latest version.I use intelliplug+intelliactive
No issues so far.Intelliplug is shutting down cores faster which will propably save some juice
Also feels a little colder than before when gaming(asphalt 8)
RealONE Kernel for Moto X 2014!
Only CM or based CM versions like RR,NX...
And only Android M too
Features:
Compiled with UBERTC 4.9.4
Optimized Entropy
FauxSound
Power Suspend
Improved accuracy of MultiCore
CRC disabled by default( 30% extra perfomance on I/O)
Swappiness reduced to 15%
UnderClock CPU (268 Mhz)
Activated Power Eficcient Worqueues
#Governors:
ZZmove
Intellidemand
Smartmax Extreme Power Saver (eps)
Intelliactive
#Hotplugins:
MSM_Hotplug
Intelliplug
Alucard
MSM MP Decision
#I/O Schreduler:
Added Zen
All credits goes to Michel Borges
Thanks Leonardo Augusto
Thanks Faux123
Source of the Kernel on github:
https://github.com/RealOne-Kernel/RealOne-Victara-Kernel
could you give instructions on how to flash a kernel in our device?
marquesini said:
could you give instructions on how to flash a kernel in our device?
Click to expand...
Click to collapse
This is not the place for that.
jlink38 said:
This is not the place for that.
Click to expand...
Click to collapse
oh, ok.
then I dunno, pm me an external link for that ? i really want to try change the kernel, but don't want to mess up the device, i could google it but preffer a recommendation of a tutorial by someone who understands more about it than i dunno.
anyway, thanks.
Hello, your kernel is very good, very fluid and good battery consumption in CM13, it would be possible in the future to add support KCAL?, can change the saturation, contrast, etc., thank you for your work.
[DEV][PATCH] KCAL - Advanced color control for Qualcomm MDSS 8x10/8x26/8974/8084/8939
Great kernel. Has improved battery life quite a bit !
Thanks!! Testing on CM13... Looks good
Good battery consumption.
Sent from my XT1095 using Tapatalk
Great kernel so far, thanks for making a custom kernel for 6.0, I've been waiting for one.
Would it be possible for you to add support for DriveDroid to your kernel?
http://forum.xda-developers.com/showthread.php?t=2196707
https://play.google.com/store/apps/details?id=com.softwarebakery.drivedroid&hl=en
Thxx , give me more feedbackk ! And I'll take a look at suggestions at the weekend guys !!
Can't wait to see what this can do..bout to flash now!!!
some people say they are taking random reboots .. anyone had ? maybe a log for me ?
MichelBorgess said:
some people say they are taking random reboots .. anyone had ? maybe a log for me ?
Click to expand...
Click to collapse
Yes i had that issue, but i reflashed cm, I'll retry tomorrow and get you some logs (hopefully i have time, I'm doing my finals now...).
MichelBorgess said:
some people say they are taking random reboots .. anyone had ? maybe a log for me ?
Click to expand...
Click to collapse
I'll try.its happened a few times to me
---------- Post added at 08:47 AM ---------- Previous post was at 08:39 AM ----------
Where can I post my logcat?
http://pastebin.com/ try this
Your kernel its a dream hahahaha I was waiting for a kernel with fauxsound since I've bought this phone. So, first of all, thank you very much for your kernel and we appreciate your work and your time spent with this kernel. But lets get to the facts:
1) In RR 5.6.0 your kernel cause bootloop;
2) In CM13 (specifically 2015-12-12 build) I had a lot of random reboots and the sound (specifically Play Music and Deezer) sometimes was cracking or just not played;
3) In CrDroid I had the same thing in CM13 but the rom has some serious bugs, so we don't count it;
4) In Nexus Experience 10.0.4 I just had ONE random reboot (take note: the first boot, so lets blame the instability of the rom) and, since then, my phone is working completely perfect.
5) With kernel auditor all of my preferences are saved and sticked after a reboot (in Nexus Experience 10.0.4)
Note: All of the Roms was fresh installed, wiped everything (including internal storage) then installed ROM->GAPPS (NX GApps in Nexus Experience and OpenGApps in the other roms)->KERNEL
Maybe with some work in your kernel and in the newer roms, this phone will gain some fresh air!
Thank you again!
Ps.: not an american guy, so please, I'm sorry for any english mistake
victor19 said:
Your kernel its a dream hahahaha I was waiting for a kernel with fauxsound since I've bought this phone. So, first of all, thank you very much for your kernel and we appreciate your work and your time spent with this kernel. But lets get to the facts:
1) In RR 5.6.0 your kernel cause bootloop;
2) In CM13 (specifically 2015-12-12 build) I had a lot of random reboots and the sound (specifically Play Music and Deezer) sometimes was cracking or just not played;
3) In CrDroid I had the same thing in CM13 but the rom has some serious bugs, so we don't count it;
4) In Nexus Experience 10.0.4 I just had ONE random reboot (take note: the first boot, so lets blame the instability of the rom) and, since then, my phone is working completely perfect.
5) With kernel auditor all of my preferences are saved and sticked after a reboot (in Nexus Experience 10.0.4)
Note: All of the Roms was fresh installed, wiped everything (including internal storage) then installed ROM->GAPPS (NX GApps in Nexus Experience and OpenGApps in the other roms)->KERNEL
Maybe with some work in your kernel and in the newer roms, this phone will gain some fresh air!
Thank you again!
fix in next build
Click to expand...
Click to collapse
Yo guyss ! I redid the kernel, and apparently restarts stopped .. is still simpler, more 'll keep updating
zzmoove
intelliplug
IO Zen
https://www.androidfilehost.com/?fid=24340319927533603
I don't understand this thread. The OP has a different username the one above who has released v2? And why hasn't this been moved to 'original development'?
floepie said:
I don't understand this thread. The OP has a different username the one above who has released v2? And why hasn't this been moved to 'original development'?
Click to expand...
Click to collapse
I just asked for Vinicius post for me , since I had not yet allowed to post in section ...
The ProjectHiSi team with members @spirtix, @T1mb3 and @erayrafet presents you PEAK KERNEL for all devices using the HiSilicon HI3635 platform, e.g. Huawei P8, Honor 7 and more, running CyanogenMod 13, LineageOS 13 and LineageOS 14.1 (EMUI support is coming soon).
Features
Linux Kernel 3.10.108
Boeffla wakelock blocker
Improved headphone volume output
BFQ, FIOPS, Maple and ZEN I/O schedulers
OPTDEMAND and BLU_ACTIVE CPU governors
GPU_SCENE_AWARE governor
More GPU and DDR governors available
Fsync can be toggled on and off
ZRAM and KSM are disabled for better battery life
F2FS
Init.d support
EX Kernel Manager or Kernel Adiutor are recommended for management
Installation & Downloads
Get the latest PEAK build on GitHub: https://github.com/ProjectHiSi/android_kernel_huawei_hi3635/releases
Install the peak-xxx.zip file using TWRP or EX Kernel Manager
XDA:DevDB Information
PEAK KERNEL, Kernel for the Huawei P8
Contributors
erayrafet, T1mb3, spirtix, nexolight, AD2076, Speedo.thc, surdu_petru, haky 86, JBolho
Source Code: [url]https://github.com/ProjectHiSi/android_kernel_huawei_hi3635[/URL]
Status: Beta
Current Beta Version: 0.4
Beta Release Date: 2018-09-02
Created 2018-09-01
Last Updated 2018-09-10
Version 0.4 is up for testing.
What's new?
- OPTDEMAND and BLU_ACTIVE CPU governors
- GPU_SCENE_AWARE governor
- FIOPS and ZEN I/O schedulers
- More volume boost - needs testing
- Workque Power Efficiency on
https://github.com/ProjectHiSi/android_kernel_huawei_hi3635/releases
Version 0.5 is going to come with:
- Optimized MAPLE and GPU_SCENE_AWARE
- Fsync toggled
- General optimizations
Wait for the release.
https://github.com/ProjectHiSi/android_kernel_huawei_hi3635/releases
Hej, thanks for your work!!
I installed your kernel but noticed a faster battery drain. Maybe a point for your next release
Edit: btw, under your posted link is actually no 0.5 version available ?
Is there allready EMUI support? Will it work on P8MAX?
Hirs_E_Fruit said:
Is there allready EMUI support? Will it work on P8MAX?
Click to expand...
Click to collapse
No EMUI support for now.
I guess, it won't work on P8 Max because there isn't a Lineage OS ROM for it.
erayrafet said:
No EMUI support for now.
I guess, it won't work on P8 Max because there isn't a Lineage OS ROM for it.
Click to expand...
Click to collapse
But if there will be EMUI support it should work since its the same SoC?
Hirs_E_Fruit said:
But if there will be EMUI support it should work since its the same SoC?
Click to expand...
Click to collapse
There are plans for it, but I can't say anything concrete for now.
any ETAs of the next version? Its been a dozen days..
thank all devs for your amazing works, you guys are the only reason im still holding this antique device
Hi,
Thank you for this kernel. I have a question, i'm using Huawei P8 and how can i change cpu and gpu settings? I use Ex Kernel Manager but all settings are grayed out Or it's not possible to overclock cpu and gpu?
Hellah said:
Hi,
Thank you for this kernel. I have a question, i'm using Huawei P8 and how can i change cpu and gpu settings? I use Ex Kernel Manager but all settings are grayed out Or it's not possible to overclock cpu and gpu?
Click to expand...
Click to collapse
Do you have root access? Also, no overclocking here.
erayrafet said:
Do you have root access? Also, no overclocking here.
Click to expand...
Click to collapse
Yep, i do. Also i installed CM 13 and thought i will be able to overclock cpu or atleast change cpu profile to make phone a little faster but there is no performance option in setting nor i can change anything under EX Kernel Manager
EDIT: Ha, okay, false information. My phone is not rooted or at least not rooted properly, that's what root check apps say. So hm... i dunno what to do. Could it be because my phone is not properly rooted?
EDIT2: Okay, i solved this thing. Had to install supersu once more to make it work properly. Now under EX Kernel Manager i can change powersave and performance values but again, how to make it to work because cpu profile is still interactive and i dunno where and how to change it
Hellah said:
Yep, i do. Also i installed CM 13 and thought i will be able to overclock cpu or atleast change cpu profile to make phone a little faster but there is no performance option in setting nor i can change anything under EX Kernel Manager
EDIT: Ha, okay, false information. My phone is not rooted or at least not rooted properly, that's what root check apps say. So hm... i dunno what to do. Could it be because my phone is not properly rooted?
EDIT2: Okay, i solved this thing. Had to install supersu once more to make it work properly. Now under EX Kernel Manager i can change powersave and performance values but again, how to make it to work because cpu profile is still interactive and i dunno where and how to change it
Click to expand...
Click to collapse
From the side menu go to the CPU section. There you will have options for governors and CPU frequencies.
Looks like i had to reboot my phone to make advanced settings in EX Kernel Manager to work. Now i see everything. Gonna test it now.
Thank you so much for your help!
hi~ I've been using peak kernel for weeks and I'd say it's stable and great.
The wifi bonding feature seems not working. I don't know if I had misunderstand it,but wouldn't the wifi speed be 144Mbps?The current speed is still 72mbps.
Besides, the frequency of the little cluster is almost always 1516mhz/1209mhz and never runs at 403mhz.
Btw, the current released version is still 0.4 not 0.5 as OP.
Thank you all devs!:good:
TensorLake said:
hi~ I've been using peak kernel for weeks and I'd say it's stable and great.
The wifi bonding feature seems not working. I don't know if I had misunderstand it,but wouldn't the wifi speed be 144Mbps?The current speed is still 72mbps.
Besides, the frequency of the little cluster is almost always 1516mhz/1209mhz and never runs at 403mhz.
Btw, the current released version is still 0.4 not 0.5 as OP.
Thank you all devs!:good:
Click to expand...
Click to collapse
You can't force the phone to use 40 MHz networks. But you can do it from your router settings instead. Also, v0.5 was in testing, but we haven't released it yet. It seemed to be stable, so I will publish it soon.
I did successfully installed LineageOS for P8 on my P8 Max. It boots okay, graphics and touch screen are working. But WiFi and cellular are not. Is it related to kernel driver settings or the android firmware?
is there a way to install the official kernel?
Regards
Stefano
wes93 said:
is there a way to install the official kernel?
Regards
Stefano
Click to expand...
Click to collapse
Recover your backup (only boot)
Or flash stock boot.img (what ever rom you use)
T1mb3 said:
Recover your backup (only boot)
Or flash stock boot.img (what ever rom you use)
Click to expand...
Click to collapse
Thanks a Lot.
Hi everyone
As title shows, this is a WIP project
(I don't own the device, all builds are blind!)
What is EAS?
Energy Aware Scheduling (EAS) is an enhancement to Linux power management, unifying CPU power control under the Linux kernel. EAS extends the Linux kernel scheduler to make it fully aware of the power/performance capabilities of the CPUs in the system, to optimize energy consumption for advanced multi-core SoCs including big.LITTLE. With EAS, the Linux kernel will use the task load and a CPU ‘Energy Model’ to control task placement to select the optimal CPU to run on.
Google thinks, EAS is the way to go for the future. With this kernel you can get pixel (2) experience even before the pixel (2) is released.
Interesting links for further research:
https://www.xda-developers.com/google-pixel-fastest-android-phone-eas/
https://developer.arm.com/open-source/energy-aware-scheduling
Features
- Full EAS 1.3 implementation (based on EAS Project and LineageOS official kernel)
- Works on HMP ROMS too (you need to use sched/schedutil, HMP stuff are removed from kernel, otherwise you'll face freqs stuck at 100%)
- STune Boost for better battery and performance
- F2FS supported
- Tweaks and changes under the hood
Feel free to try and report your feedback (and logs too)
Download here
Installation
- Reboot to TWRP
- Backup your current boot.img
- Flash the kernel
- Reboot!
Sources here
Credits
@OrdenKrieger
@jcadduono
@joshuous (EAS Project)
And everyone worked for this device and LineageOS bring-up
Changelog
04/11
- Initial release
07/11
- Completely rebased over the latest CAF Oreo Tag (LA.UM.6.6, it *should* work on Pie, but not guaranteed!)
- 3.18.124
- Completely re-done EAS
- New LMK for better RAM managment
- Android upstream for AIO (check if MTP works better or worse than before)
- Better battery and performance
EAS - Energy Aware Scheduling
WIP - Work in Progress
HMP - Heterogeneous Multi-Processing
HAL - Hardware abstraction layer
Do you plan to update the kernel on a regular base?
sklaes said:
EAS - Energy Aware Scheduling
WIP - Work in Progress
HMP - Heterogeneous Multi-Processing
HAL - Hardware abstraction layer
Do you plan to update the kernel on a regular base?
Click to expand...
Click to collapse
When there are major changes to be applied - then yes
Otherwise makes no sense to push update with little to no changes at all
You tested it?
Currently testing it on LOS16. Boots just fine, I'm charging the phone to 100% now to give it a go and I'll be back with some feedback tomorrow. So far everything I've tested works fine.
Not jet, but EAS sounds interesting
Update: installed - currently testing
@sys01: You've said that it works on ROMs based on LineageOS. But does it work on ROMs that are based on AOSP? Is F2FS supported for data and cache partitions?
Thanks!
---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------
[/COLOR @sys01: You've said that it works on ROMs based on LineageOS. But does it work on ROMs that are based on AOSP? Is F2FS supported for data and cache partitions?
Thanks!
i use this now on dotos oreo with f2fs data.But on interactive the cpu freq stays on max,whatsup with this?
@Predatorhaze: So, you say this kernel works with F2FS data on DotOS Oreo? I literally just tried that a few days ago, but with Hellsgate/Schwifty kernels, no go. But maybe I'll try again now. Thanks for the heads up!
Predatorhaze said:
i use this now on dotos oreo with f2fs data.But on interactive the cpu freq stays on max,whatsup with this?
Click to expand...
Click to collapse
This is an EAS kernel, you need to use sched/schedutil (interactive gov won't work anymore)
AnonVendetta said:
@sys01: You've said that it works on ROMs based on LineageOS. But does it work on ROMs that are based on AOSP? Is F2FS supported for data and cache partitions?
Thanks!
---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------
[/COLOR @sys01: You've said that it works on ROMs based on LineageOS. But does it work on ROMs that are based on AOSP? Is F2FS supported for data and cache partitions?
Thanks!
Click to expand...
Click to collapse
F2FS is supported, I'll update the thread to explain that better
AnonVendetta said:
@Predatorhaze: So, you say this kernel works with F2FS data on DotOS Oreo? I literally just tried that a few days ago, but with Hellsgate/Schwifty kernels, no go. But maybe I'll try again now. Thanks for the heads up!
Click to expand...
Click to collapse
i have data in f2fs,and yes it boots and everything works till now.
Only is that dolby atmos dont work anymore,dont know why.On previous build with ext4 it worked.
I was confused because the freq on interactive,but already read a answer and that is due its eas kernel.
good we have eas now,i use helix engine also
if anyone got a working dolby atmos,pls let me know
sys01 said:
This is an EAS kernel, you need to use sched/schedutil (interactive gov won't work anymore)
Click to expand...
Click to collapse
ok.untill now everything seems stable.
can you set schedutil as default on next update? and you think about adding kcal feature (saturations etc) and some wakeblocks?
running on dotos 2.5 oreo,magisk 17.3,crimson kernel,f2fs data partition and los universal v2 bootstack
an update to the current lineage OS kernel would be great since September has changed a lot on the go kernel
Your kernel works with AOSP Basis Rom
(have your kernel briefly tested with the havoc 2.0 Rom)
Running this right now on LOS 15, for the entire day, without any issues that I can see. :good:
Used EX Kernel Manager to set governors.
The kernel runs pretty well on Pie, but I think it's pretty aggressively throttled. Once the temp gets to 40°C the LITTLE cores get set to 960 MHz and the big cores to around the same. It's also kind of sluggish when the phone is taken out of deep sleep, and scrolling isn't that great. However, deep sleep works wonders. The discharge rate with screen off is ~0.3% per hour.
Oh, and it may just be me, but playing audio thtough the speakers makes the phone temp get pretty high, which again makes it get throttled and really slow.
Gases said:
The kernel runs pretty well on Pie, but I think it's pretty aggressively throttled. Once the temp gets to 40°C the LITTLE cores get set to 960 MHz and the big cores to around the same. It's also kind of sluggish when the phone is taken out of deep sleep, and scrolling isn't that great. However, deep sleep works wonders. The discharge rate with screen off is ~0.3% per hour.
Oh, and it may just be me, but playing audio thtough the speakers makes the phone temp get pretty high, which again makes it get throttled and really slow.
Click to expand...
Click to collapse
New version coming soon, hopefully this time around should be way more smooth and stable
Also, EAS takes time to make it perfect, but soon or later it will!
Thank you for your work. This kernel is great and really shows the benefits of EAS on an older SOC like the S820. Sure, it needs polishing, but it's a great start
sys01 said:
New version coming soon, hopefully this time around should be way more smooth and stable
Also, EAS takes time to make it perfect, but soon or later it will!
Click to expand...
Click to collapse
For sure, not complaining at all! Just wanted to give some honest feedback in case you wanted to keep tweaking it
sys01 said:
New version coming soon, hopefully this time around should be way more smooth and stable
Also, EAS takes time to make it perfect, but soon or later it will!
Click to expand...
Click to collapse
Thank you very much! Great work