i had an idea just now. i was wandering if there is an easy way to install our gpu drivers in any kernel or rom without messing with decompiling the kernel ( im totally noob in decompiling and recompiling by the way )
once , some weeks ago i tried the gpu tegra 3 drivers from google store but my phone ended in an eternal black screen.
this question came in my mind thinking the cyanogenmod rom for example. its stable enough alright but it hasnt got any gpu drivers. as a result we must rely on cpu for everything. if we tick the use of gpu inside developer options , then the phone super lags, the fps is getting lower.
kessaras said:
i had an idea just now. i was wandering if there is an easy way to install our gpu drivers in any kernel or rom without messing with decompiling the kernel ( im totally noob in decompiling and recompiling by the way )
once , some weeks ago i tried the gpu tegra 3 drivers from google store but my phone ended in an eternal black screen.
this question came in my mind thinking the cyanogenmod rom for example. its stable enough alright but it hasnt got any gpu drivers. as a result we must rely on cpu for everything. if we tick the use of gpu inside developer options , then the phone super lags, the fps is getting lower.
Click to expand...
Click to collapse
Not sure if trolling or serious...
EVERY kernel has included drivers, phone WOULDN'T boot without graphic drivers. And drivers are compiled into kernel, you cannot decompile it, change them, and compile. Unless you build your kernels from source, but thats not the case here
My phone on CM and every other rom is super smooth with ticked GPU rendering. Maybe try wiping your phone. And I recommend using official Vanir ROM, plus Werewolf kernel from AnyKernel thread. Peace !
FunkyRasta said:
Not sure if trolling or serious...
EVERY kernel has included drivers, phone WOULDN'T boot without graphic drivers. And drivers are compiled into kernel, you cannot decompile it, change them, and compile. Unless you build your kernels from source, but thats not the case here
My phone on CM and every other rom is super smooth with ticked GPU rendering. Maybe try wiping your phone. And I recommend using official Vanir ROM, plus Werewolf kernel from AnyKernel thread. Peace !
Click to expand...
Click to collapse
right yea , drivers are already there, i didnt explain it well. i mean , by default our gpu speed is at 520mhz according to wiki. But i cant find that info / setting inside cyanogenmod anywhere. im just testing things, in iodak its easy and obvious where is the gpu clock, in cyanogen there is not even a single file named gpu.
Ahhh so I misunderstood you Use app named tegra overlock to change GPU frequencies. Works for me using werewolf kernel. And you can flash iodak on CM no problem...
Sent from my Optimus 4X HD using xda app-developers app
kessaras said:
right yea , drivers are already there, i didnt explain it well. i mean , by default our gpu speed is at 520mhz according to wiki. But i cant find that info / setting inside cyanogenmod anywhere. im just testing things, in iodak its easy and obvious where is the gpu clock, in cyanogen there is not even a single file named gpu.
Click to expand...
Click to collapse
Let me guess, you were searching in wikipedia for "tegra 3", right?
520MHz is not at all our default GPU speed. It's 416.
Also, sure you can change GPU settings on CM stock kernel, heck, even on stock As long as you are root, you can change most stuff.
And about the drivers... you can't decompile a kernel. Even if you would try to, all you would get would be a bunch of weird symbols and letters
You can make a kernel out of 1GB source code, but you can never make the source code out of 5MB kernel
pffff why did u do this to me... i had quit searching in cm10.2 the gpu settings, now ill have to start searching again hahaha
Related
Hi. The following kernel is presented to you by
vorkKernel Team:
- kiljacken
- Benee
Click to expand...
Click to collapse
This kernel is for Cyanogenmod and Miui. *Could* be incompatible with latest kangs or nightlies (after a kernel update from CM team). No support for stock or mcr...
It's incompatible with MIUI and CM Builds before #177
New vorkKernel Twitter Bot: Here
First I want to make clear that all credit goes to aremcee/arcee/rmcc (man so many nicks ). He did an awesome job with the kernel.
I just tweaked it a little bit to my needs.
Features:
uv/oc support. OC up to 1,5GHz (With E-Peen version)
AVP/System/RAM/GPU OC with E-Peen version
1,2 Ghz for batt safe version.
Special tweaked (working!) Performance and Powersave Govenors which don't lock the freq to one level (they choose between 3-4 Freq steps)
It's even possible to set max/min clock via setcpu or CMSettings!
Voodoo sound. Thanks supercurio! So awesome
Default IO-Sched is Deadline with a special flash storage tweak
Slub allocator
tweaked CFS cpu sched (Low latency)
compiled with a tweaked toolchain (base linaro gcc - optimized for tegra2)
VFP optimizations (vfpv3-d16) and overall compiler optimizations
flags! (more below in the flag section)
A App for easy downloading and configuring. Credits to kiljacken!
Click to expand...
Click to collapse
The standard part:
I'm not responsible for melted phones or something like that...
The camera is unstable with E-Peen mode (due to AVP OC). After a reboot it needs to stabilize a few minutes (so you break it with every reboot again). Same for Bluetooth. Please don't report a problem regarding this. It's known and can't be fixed.
Click to expand...
Click to collapse
And the source code here.
Download (Market)
Credits to kiljacken for this awesome app! You need OI File Manager for the app (Comes with CM)!
(and if you refuse to use the app - or the app is refusing to work with you: here)
Only change something, if you want to enable OC - No need to touch anything else (like govenors, schedulers)
What are flags and how can I use them?
I recommend to use the App kiljacken made, because it's super easy for you guys. If you not want to use the app *sadpanda* then you can click this link. This is the file the app is fetching to generate the UI.
The layout is following:
Available for following device/Element style (more below)/the flag you need to add/Flag name in App/Description for general Flag/Choice name in app/actual value you need to add after flag name
If the last two points are added you first enter the flag name and than the value. For example: density230
You connect the flags with a: -
Example: -camera-ring ...
The script is configured to detect flags after vorkKernel-VERSIONNUMBER. So you can add some flags after this.
Element style
c = Checkbox
l = List you can choose things from
e = you can enter your own value
Click to expand...
Click to collapse
Error Reporting Guide
Start with rebooting, if that doesn't help, reflash CM and then the kernel, and check again. If you're using the updater app (make sure you have the latest version), use the error report function (and describe what you're problem is). If you're not using the app, then post what flags you are using, along with what your problem is.
Click to expand...
Click to collapse
Additionally I just want to point out that I'm not doing this as a fulltime job, so don't expect daily updates or something like that. I will try to fix a problem as fast as possible but in some cases it can take a while.
If you want to support me you can sign up on dropbox via my referral link or just push this nice thanks button .. If you want to donate you can donate to aremcee/arcee/rmcc something. I'm learning C and linux and vorkKernel is my learning project and it is a hobby for me. Anyway if you still want to support a poor student, I have a link in my signature
Thanks to:
arcee + the whole CM Team
morfic for all the avp oc tweaks and other stuff
thalamus (for saving me going crazy with the toolchain )
Erasmux
All guys that made pull request and contributed in any possible way
Donators to our project (app or kiljacken's donate link)
the android community
and a very big thanks to b3ndech0 for his buildbox.
Thanks, this is very much appreciated
This kernel is amazing! Nice work with the filename flags. It's brilliant! This way we don't have to have the same setup, but can enjoy both CM7 and the kernel.
sibbor said:
I'll try this kernel later. Will wait for CM7 getting more optimized for our devices first. 2000 Quadrant scores out of the box just don't cut it - I don't want to overclock to 1.4 GHz just to reach speeds of MCR FR14 ;-)
Planning on including any changes from kholk?
Click to expand...
Click to collapse
More things will be in it soon. And Quadrant doesn't matter. CM feels better in normal use (except a few problems but it is a really good starting point).
Benee said:
More things will be in it soon. And Quadrant doesn't matter. CM feels better in normal use (except a few problems but it is a really good starting point).
Click to expand...
Click to collapse
Yes I know it doesn't really matter. Although, generally speaking, higher scores means the software is more optimized to the hardware; framework, kernel and/or drivers.
CM7 should be able to smash the performance out of the LG stock ROM without problem...
Thanks for you kernel additions! Subscribed to this thread now so I can follow your progress.
is this kernel for a stock rom?
thanks
sibbor said:
Yes I know it doesn't really matter. Although, generally speaking, higher scores means the software is more optimized to the hardware; framework, kernel and/or drivers.
CM7 should be able to smash the performance out of the LG stock ROM without problem...
Thanks for you kernel additions! Subscribed to this thread now so I can follow your progress.
Click to expand...
Click to collapse
Nah. You can boost quadrant to oblivion via data2ext for example on desire/nexus but it didn't helped in real life performance. The sql sync disable doesn't help with real usage, but boost quadrant etc. So many things which doesn't improve real usage, boost quadrant. Like deleting your /system (pro move...).
But yeah in some parts you are right and optimizing drivers boost it too + help real use performance, so I will do this too.
vekkio said:
is this kernel for a stock rom?
thanks
Click to expand...
Click to collapse
Really? Just read the title: vorkKernel-OC/UV Kernel for CM. For Cyanogenmod. Not stock...
seems the IO from quadrant score still low, is it same sqlite hack with paul that one?
emprize said:
seems the IO from quadrant score still low, is it same sqlite hack with paul that one?
Click to expand...
Click to collapse
yup. patched cm, then compiled this and added it to update.zip.
vekkio said:
is this kernel for a stock rom?
thanks
Click to expand...
Click to collapse
Haaahaa yeah u flash away hahahahha
EDIT:- No only joking
DONT PEOPLE READ
ok, flash this kernal and using cm7 oc to 1.4, quadrant get 31xx
edit : fail to exec smartbench
Benee any chance you could add the OC support to the CM settings?
Sent from my LG O2X CM7 Nightly
svceon said:
Benee any chance you could add the OC support to the CM settings?
Sent from my LG O2X CM7 Nightly
Click to expand...
Click to collapse
Yep but this would break pimp my cpu support and I think pimp my cpu is the better deal. A easy user interface with undervolting support. Awesome! .. so no I won't add it to cm settings
Awesome OC in CM7 makes it even better
I know I'm going to get flamed for this but how do you o/c once you have flashed the kernel? when i open setCPU its already at the max 1g when i go to the CM settings there's no frequencies to select in the cpu management option
is it different on the tegra chips as opposed to qualacom?
sibbor said:
Planning on including any changes from kholk?
Click to expand...
Click to collapse
Ok if I understand the changelog from kholk correct, most of the changes are already included (don't know exactly because he didn't copied the commit names and sums the function up). One commit isn't in it because it introduced the graphic glitches. vfp3-d16 support and compiler optimization will be added with next update. Then most things are in it.
spences10 said:
I know I'm going to get flamed for this but how do you o/c once you have flashed the kernel? when i open setCPU its already at the max 1g when i go to the CM settings there's no frequencies to select in the cpu management option
is it different on the tegra chips as opposed to qualacom?
Click to expand...
Click to collapse
Is stated in the OP:
So I compiled it with uv/oc support via pimp my cpu.
Click to expand...
Click to collapse
Pimp My CPU can be downloaded from here: http://forum.xda-developers.com/showthread.php?t=1018411
spences10 said:
I know I'm going to get flamed for this but how do you o/c once you have flashed the kernel? when i open setCPU its already at the max 1g when i go to the CM settings there's no frequencies to select in the cpu management option
is it different on the tegra chips as opposed to qualacom?
Click to expand...
Click to collapse
Nah no flaming . You need pimp my cpu for it. Cpasjute did some kernel hacks to enable oc and add a uv function. That means you can undervolt without compiling the kernel again. Unfortunatly it isn't compatible with setcpu..
The kernel seems ok; I tried OC till 1200 with 50-100 UV (depending on OC).
What's very good with CM7 (and this kernel) is battery life, 30-40% more compared with Modaco ROM (till FR14).
Anybody have tried higher frequencies (1300-1400)?
Thanks a lot.
lukemo said:
The kernel seems ok; I tried OC till 1200 with 50-100 UV (depending on OC).
What's very good with CM7 (and this kernel) is battery life, 30-40% more compared with Modaco ROM (till FR14).
Anybody have tried higher frequencies (1300-1400)?
Thanks a lot.
Click to expand...
Click to collapse
I have been using this all day running 1300Mhz @ 1200mV - normal use with wifi on - 84% battery left after ap. 12 hours
Here are drivers for ICS/JB from the Xperia Play forums.
Can this do any good for games (HD games?) As far now I am on cm10. All is working well . I do not want yo get screwed up now. If this will for sure improve gaming performance I would like to tty. But please advice this will not effect other performance......
Sent from my A99 using Tapatalk 2
leoaeries said:
Can this do any good for games (HD games?) As far now I am on cm10. All is working well . I do not want yo get screwed up now. If this will for sure improve gaming performance I would like to tty. But please advice this will not effect other performance......
Sent from my A99 using Tapatalk 2
Click to expand...
Click to collapse
Backup CWM first
Sent from my Spice Mi-410 using Tapatalk 2
I don't think this will work, because as far as i know these are not actually drivers but shared objects *.so (much like dll files in windows). The gpu drivers are actually compiled within the kernel and the version of these *.so files must match with the version of the gpu drivers compiled within the kernel. So unless those match i don't see these working for us. However i may be wrong, devs can throw more light on this.
nayneshdev said:
I don't think this will work, because as far as i know these are not actually drivers but shared objects *.so (much like dll files in windows). The gpu drivers are actually compiled within the kernel and the version of these *.so files must match with the version of the gpu drivers compiled within the kernel. So unless those match i don't see these working for us. However i may be wrong, devs can throw more light on this.
Click to expand...
Click to collapse
Actually all version of CM7 / CM9 for Motorola Triumph, and edowar's have not been built from source. All files have been copied over and built with the source code. Here is a few examples of the code copying
CM7 MTDEV
https://github.com/MTDEV-CM7/vendor/blob/cm7/motorola/triumph/triumph-vendor-blobs.mk#L82
CM9 MTDEV
https://github.com/MTDEV-CM9/vendor/blob/ics/motorola/triumph/triumph-vendor-blobs.mk#L206
CM9 edowar
https://github.com/edowar/android_device_fb0/blob/ICS/device_fb0.mk#L230
Yes i understand that. But afaik edowar had built a 0.32 kernel with newer gpu drivers which is used in bumblebee rom ported from whyzor's cm7. If u use the same gpu drivers(*.so) in any other 0.32 based rom then they won't work without using the same edowar kernel. And i think the sources for more recent gpu drivers are taken from code aurora forum.
Sent from my FIH-FB0 running fantastic gingermia (which needs an update) using xda app-developers app.
leoaeries said:
Can this do any good for games (HD games?) As far now I am on cm10. All is working well . I do not want yo get screwed up now. If this will for sure improve gaming performance I would like to tty. But please advice this will not effect other performance......
Sent from my A99 using Tapatalk 2
Click to expand...
Click to collapse
Hey leo,
What HD games can you play on our ICS and JB ROMs?
Thanks.
^_^
nayneshdev said:
Yes i understand that. But afaik edowar had built a 0.32 kernel with newer gpu drivers which is used in bumblebee rom ported from whyzor's cm7. If u use the same gpu drivers(*.so) in any other 0.32 based rom then they won't work without using the same edowar kernel. And i think the sources for more recent gpu drivers are taken from code aurora forum.
Sent from my FIH-FB0 running fantastic gingermia (which needs an update) using xda app-developers app.
Click to expand...
Click to collapse
You are correct there is some changes for those specific drivers based on the kernel (forgot to mention that ) here is the commits needed for the kernel
https://github.com/Whyzor/WX_435_Kernel-CM7/commits/master
Look at all the commits from Mar 01, 2012 and that will get you in business with those specific drivers.
Actually these libs work fine. tested in cm10 and cm9 for our device
nachiketa.ramesh said:
Actually these libs work fine. tested in cm10 and cm9 for our device
Click to expand...
Click to collapse
If the libs work fine then, i don't expect any differences, cause the versions will be the same.
We're waiting from a year.I want oc supported kernel.Will it be happen ?
Sorry for English
kilicaslan17 said:
We're waiting from a year.I want oc supported kernel.Will it be happen ?
Sorry for English
Click to expand...
Click to collapse
no, because our device is not OC capable..... some developers said, its too dangerous with our CPU.
aluk4rd said:
no, because our device is not OC capable..... some developers said, its too dangerous with our CPU.
Click to expand...
Click to collapse
Yes but mali400 gpu can be overclock so much.
kilicaslan17 said:
Yes but mali400 gpu can be overclock so much.
Click to expand...
Click to collapse
you seem very knowledgeable on the topic perhaps you should try getting into making an OC kernel
there is a thread that one of the guys started working on an OC kernel
have a search through it and see what you can do
efaustino84 said:
you seem very knowledgeable on the topic perhaps you should try getting into making an OC kernel
there is a thread that one of the guys started working on an OC kernel
have a search through it and see what you can do
Click to expand...
Click to collapse
i've changed the values in the frequency table (the highest frequency i tried to compile was CPU @ 1.1GHz and GPU @ 350mhz or 400Mhz i can remember it was around +50MHz then the stock frequency , go slow, too high values can be very dangerous) on the kernel sources but i had some truble compiling the kernel and even if i compiled the kernel the network drivers wouldnt work...(see the instructions on how to compile and how to fix the drivers in the kernel sources From SAMSUNG).
anyway i discontinued my work due to a certain "comment" i didnt like and i have no intention of start developing a public release.
Good Luck
PTGamer said:
i've changed the values in the frequency table (the highest frequency i tried to compile was CPU @ 1.1GHz and GPU @ 350mhz or 400Mhz i can remember it was around +50MHz then the stock frequency , go slow, too high values can be very dangerous) on the kernel sources but i had some truble compiling the kernel and even if i compiled the kernel the network drivers wouldnt work...(see the instructions on how to compile and how to fix the drivers in the kernel sources From SAMSUNG).
anyway i discontinued my work due to a certain "comment" i didnt like and i have no intention of start developing a public release.
Good Luck
Click to expand...
Click to collapse
Sad to see you stop developing but really just ignore them, just because someone says you suck or whatever and you stop doing it, its really not worth it
Update
Here is an easier solution that doesn't require flashing.
Please use this for any new ROMs from now on.
Old solution ONLY FOR 5.10.8 and 5.10.16
This is a stock miui kernel from 5.10.8, with modified ramdisk to limit CPU frequency.
This is a test I made for myself to see how much it helps in battery time to limit the CPU. I'm sharing this, because others might be interested in it.
You need to have MIUI 5.10.8 or 5.10.16. Older versions are not fully compatible. (Vibration not working)
So, finally we have custom kernels?
No, the proper kernel source is not available yet, the kernel image is still untouched.
Will there be new versions?
Probably, as there are other possible ramdisk tweaks that can achieve better battery life.
How much this can help?
I didn't have the time for a long test yet, I hope there are some users here who are willing to compare the results with the factory kernel.
But I can make some points:
This won't help much with standby time, as the frequency there is already much more limited.
This will help the most in situations where the CPU is the biggest drainer, like games.
Is this going to slow down my phone?
Theoretically, it will be slower. However in real life usage, I can't tell the difference.
Why wouldn't you just use an app like SetCPU?
None of those apps I tried have worked.
Can this be done without flashing a new kernel?
Yes, you only have to update the frequency in KHz in /proc/cpufreq/cpufreq_limited_max_freq_by_user.
For example (with root privileges):
Code:
echo '1500000' > /proc/cpufreq/cpufreq_limited_max_freq_by_user
However, this will reset after a reboot.
The attached file can be flashed under recoveries. TWRP tested.
Or you can extract the boot.img, and flash it in fastboot.
xm_kernel.zip will limit the CPU at 1.5GHz.
xm_kernel_1200 will do 1.2GHz.
Version 2 will do the trick Ched666 suggested, thus reducing the time spent at maxfreq.
Version 3 will not disable the touch boost, instead it will replace perfservscntbl.txt with boost to 1183MHz and 2 cores.
Reserved
Looking forward results and tests.
Flashed on 5.9.24
Work perfect. Only one problem... Vibro is gone Both Incall and feedback
Bakumatsu said:
Flashed on 5.9.24
Work perfect. Only one problem... Vibro is gone Both Incall and feedback
Click to expand...
Click to collapse
Thanks for the heads-up. You probably need 5.10.8 for that to work.
I know. I just a flashagolic
ill be testing this later..nice work buddy
Test on miui 5.10.8, it works!
And later manually change value to 1200000, works without lag. But after reboot maxfreq reset to 1500000.
Can you make the same kernel, but with maxfreq 1200000?
Xmister said:
No, the proper kernel source is not available yet, the kernel image is still untouched.
Click to expand...
Click to collapse
isn't this the kernel source code: https://github.com/BalcanGSM/MediaTek-HelioX10-Kernel
avenant said:
isn't this the kernel source code: https://github.com/BalcanGSM/MediaTek-HelioX10-Kernel
Click to expand...
Click to collapse
That is just a basic MediaTek source, it's missing drivers and configuration for our device.
I think it is more easy to control the value by implement init.d on our device.
Xmister said:
What is this?
This is a stock miui kernel from 5.10.8, with modified ramdisk to limit CPU frequency at 1.5GHz.
This is a test I made for myself to see how much it helps in battery time to limit the CPU. I'm sharing this, because others might be interested in it.
You need to have MIUI 5.10.8. Older versions are not fully compatible. (Vibration not working)
So, finally we have custom kernels?
No, the proper kernel source is not available yet, the kernel image is still untouched.
Will there be new versions?
Probably, as there are other possible ramdisk tweaks that can achieve better battery life.
How much this can help?
I didn't have the time for a long test yet, I hope there are some users here who are willing to compare the results with the factory kernel.
But I can make some points:
This won't help much with standby time, as the frequency there is already much more limited.
This will help the most in situations where the CPU is the biggest drainer, like games.
Is this going to slow down my phone?
Theoretically, it will be slower. However in real life usage, I can't tell the difference.
Why wouldn't you just use an app like SetCPU?
None of those apps I tried have worked.
Can this be done without flashing a new kernel?
Yes, you only have to update the frequency in KHz in /proc/cpufreq/cpufreq_limited_max_freq_by_user.
For example (with root privileges):
Code:
echo '1500000' > /proc/cpufreq/cpufreq_limited_max_freq_by_user
However, this will reset after a reboot.
The attached file can be flashed under recoveries. TWRP tested.
Or you can extract the boot.img, and flash it in fastboot.
Click to expand...
Click to collapse
it show to be on maximum speed on cpu spy...why?
Jo-san said:
it show to be on maximum speed on cpu spy...why?
Click to expand...
Click to collapse
Maybe the flash wasn't successful,or you flashed over something.
This is mine, the 29 sec is during boot, until it activates.
Ched666 said:
Test on miui 5.10.8, it works!
And later manually change value to 1200000, works without lag. But after reboot maxfreq reset to 1500000.
Can you make the same kernel, but with maxfreq 1200000?
Click to expand...
Click to collapse
OP updated with 1.2GHz kernel
Xmister you really do a great job. I renember I used your kernel when my phone was still HTC one x and then I changed to use iPhone 5s ,6, and dropped few weeks ago. And then I am back to android envirnoment and still flashing your modded kernel. Many thanks for your contribution.
And BTW, I think the 1200 kHz really help in get away from the battery draining problems.
4pda users found interesting thing... When touch a screen, frequency increases to maximum.
But if write 0 to the /proc/cpufreq/cpufreq_limited_by_hevc and set read only permissions, this bug disappears. And no maximum freq when touch a screen.
I tried it, and phone is much less heat, and works at a reduced freqs.
ADD: make mod to xm_kernel 1,5 GHz with this tweak
Ched666 said:
4pda users found interesting thing... When touch a screen, frequency increases to maximum.
But if write 0 to the /proc/cpufreq/cpufreq_limited_by_hevc and set read only permissions, this bug disappears. And no maximum freq when touch a screen.
I tried it, and phone is much less heat, and works at a reduced freqs.
Click to expand...
Click to collapse
This seems working too.
OP updated with V2 kernels that do this automatically.
Xmister said:
This seems working too.
OP updated with V2 kernels that do this automatically.
Click to expand...
Click to collapse
Also made modification ))
No need to touch cpufreq_limited_by_hevc.
If you want to control the touch_boost, try this way.
Find the file in system/etc/perfservscntbl.txt
CMD_SET_CPU_CORE, SCN_APP_TOUCH is to control how many cores when touch boost.
CMD_SET_CPU_FREQ, SCN_APP_TOUCH is to set the value when touch boost.
Save after modify and reboot your device.
By @Ched6666 's way is totally disable touch_boost
v2 is compatible with 5.10.16 release?
This is the Q&A thread for Helium.
You don't know where to post something? This schema will help you.
Questions about the kernel (Does it have ****?) > here
Problems you faced, and/or their solutions > here
Weird problems I could be able to solve > the development thread
Things I should read/know > the development thread
Questions that can be answered by any user (not only by me) > here
Miscellaneous posts > here
In a nutshell, if you have to post something that I have to read, post it in the development thread, otherwise use this thread.
I will not read this thread at all. Or maybe I'll check it every now and then
Mention me if I should read something.
Testing helium in temasek, for now all working right and cpu freq. goes to 1728Mhz. Very similar to last stock cm kernel but with usb fast charging :good:
I have a question @tommons (or sombody): Why do you include KSM? In Tangerine kernel it made the device laggy, increasing the power consumption due to the continous work of cpu cores and soon many of us saw that this feature wasn't good to our Xperia Sp. I always leave it off and better overall performance is achieved.
In init.d options of Kernel adiutor we can see the entry 01tangerine. Delete this entry is the same that going to /system/etc/init.d? I suppose that is.
BTW, great work and thanks for your dev time.
Alvichone said:
Testing helium in temasek, for now all working right and cpu freq. goes to 1728Mhz. Very similar to last stock cm kernel but with usb fast charging :good:
I have a question @tommons (or sombody): Why do you include KSM? In Tangerine kernel it made the device laggy, increasing the power consumption due to the continous work of cpu cores and soon many of us saw that this feature wasn't good to our Xperia Sp. I always leave it off and better overall performance is achieved.
In init.d options of Kernel adiutor we can see the entry 01tangerine. Delete this entry is the same that going to /system/etc/init.d? I suppose that is.
BTW, great work and thanks for your dev time.
Click to expand...
Click to collapse
KSM (in v2, UKSM) is there as an option. Nobody forces you to use it It uses more power but the result is a better RAM management.
Yes you can delete 01tangerine from Kernel Adiutor too.
Trying v2 with carbon 5.1.1 seems everything OK..good work man ;D
Sent from my Xperia SP using Tapatalk
Waiting eagerly to have it fully working on CM13.. Please @Tomoms hurry up :silly:
MizoSome said:
Waiting eagerly to have it fully working on CM13.. Please @Tomoms hurry up :silly:
Click to expand...
Click to collapse
Wait more or less 70 hours and you'll have it
I have tangerine 9.1 and CM12.1 on my device. Which steps i need to follow in order to have Helium?
Overclocking?
Can you build a overclocking option from this Kernel, In Tangerine Kernel my Cellphone is stucked on 1444 MHz on all gorvenors, Can you do it? A Overclocking to 1.94 GHz or more ?
pilger said:
I have tangerine 9.1 and CM12.1 on my device. Which steps i need to follow in order to have Helium?
Click to expand...
Click to collapse
Flash the stock boot.img of your CM build (if you have CM+Addons, it would be better if you flashed the boot.img of the Addons you have installed on your device), enter TWRP, install Helium.
Or, in an easier way, next time you update your CM nightly flash Helium instead of Tangerine!
JhonesMillionBR said:
Can you build a overclocking option from this Kernel, In Tangerine Kernel my Cellphone is stucked on 1444 MHz on all gorvenors, Can you do it? A Overclocking to 1.94 GHz or more ?
Click to expand...
Click to collapse
Overclock needs some work and I'm very busy at the moment. Frequency fixes will come very very soon. In the mean time you can flash v2.1, which hasn't got any issues with frequencies.
@Tomoms I am not able to install v2.2 on cm 12.1 using twrp it says unpacking kernel and nothing happens I have to hard reboot.anyone know how to solve this?
Helium Kernel v3
On Helium Kernel v3 the frequency is stucked on 1458 MHz on both cores on all gorvenors and I/O Schedulers.. :crying: :crying:
Image Link: http://tinypic.com/r/vcv2ft/9
JhonesMillionBR said:
On Helium Kernel v3 the frequency is stucked on 1458 MHz on both cores on all gorvenors and I/O Schedulers.. :crying: :crying:
Image Link: http://tinypic.com/r/vcv2ft/9
Click to expand...
Click to collapse
Good! Well, actually that's bad, but I expected it. Will fix ASAP (that is, unfortunately for you, on Sunday/Monday).
Use v2.1, it doesn't have problems.
For the others: I remind you that this doesn't mean v3 is buggy. This bug appears only on certain devices confused and mine is one of the "lucky" ones. So the best thing to do is to try v3 and see if you're lucky or unlucky. Hopefully, the bug will be fixed with v3.1.
JhonesMillionBR said:
On Helium Kernel v3 the frequency is stucked on 1458 MHz on both cores on all gorvenors and I/O Schedulers.. :crying: :crying:
Image Link: http://tinypic.com/r/vcv2ft/9
Click to expand...
Click to collapse
Same here
Sent from my Xperia SP using Tapatalk
Tomoms said:
Good! Well, actually that's bad, but I expected it. Will fix ASAP (that is, unfortunately for you, on Sunday/Monday).
Use v2.1, it doesn't have problems.
For the others: I remind you that this doesn't mean v3 is buggy. This bug appears only on certain devices confused and mine is one of the "lucky" ones. So the best thing to do is to try v3 and see if you're lucky or unlucky. Hopefully, the bug will be fixed with v3.1.
Click to expand...
Click to collapse
It will be that the kernel comes out today ? I'm anxious
JhonesMillionBR said:
It will be that the kernel comes out today ? I'm anxious
Click to expand...
Click to collapse
It's out
Helium Kernel v3.1
Tomoms said:
It's out
Click to expand...
Click to collapse
CPU frequency table finally fixed? Needs testing.
Test: Yes, All gorvernors and I/O Schedulers is working with 1944 MHz, Tested!
Thank you, Tomoms
Is TRIM support planned? I think that it is essential for device with such slow flash memory.
As for now I'm using heavily customized Tangerine 9.2 + last Xenon HD which gives great performance, but has issues (inaccurate GPS, big lag after locking the screen, touchscreen not working couple times a week and a few more). Tested latest CM12.1 + Helium 3.1 for few hours and it looks promising, but feels slower than much more bloated Xenon HD + Tk9.2 (used since September) possibly due lack of TRIM support.
michuroztocz said:
Is TRIM support planned? I think that it is essential for device with such slow flash memory.
As for now I'm using heavily customized Tangerine 9.2 + last Xenon HD which gives great performance, but has issues (inaccurate GPS, big lag after locking the screen, touchscreen not working couple times a week and a few more). Tested latest CM12.1 + Helium 3.1 for few hours and it looks promising, but feels slower than much more bloated Xenon HD + Tk9.2 (used since September) possibly due lack of TRIM support.
Click to expand...
Click to collapse
You can use the command line utility called fstrim or mount the partitions with the "discard" option. The latter way is more difficult because it requires unpacking the kernel, the ramdisk, and then repacking everything.
Swap crashing problem is resolved in v3.2?
Tomoms said:
You can use the command line utility called fstrim or mount the partitions with the "discard" option. The latter way is more difficult because it requires unpacking the kernel, the ramdisk, and then repacking everything.
Click to expand...
Click to collapse
I think that it was my mistake - I cannot remember if I enabled root before issuing TRIM - shame on me
I am using Trimmer utility and running it resulted in instant execution without returning trimmed size in gigabytes pointing that either root was not enabled or TRIM was not supported. Judging by your reply I can assume that TRIM is supported so I think that I'll make second attempt to CM12.1 when touchscreen issue is fixed* or CM13 when camera will be working.
* I just read that @Adrian DC fixes has been merged in 3.2! I will check that kernel as soon as I can! :angel: