Related
Rom cookers: if you include this module in your ROM, please make a link to this post in your release post, so your users can know how to work with it and update the module themselves
Intro:
Well, it seems that many people don't want to overclock because of heat, stability..., and just want to have benefits of an undervolted cpu. So here it is my friends. Default voltage level of our kernel is 3-4-5-6-7.
Source on github : https://github.com/doixanh/X8Features
Release history
April 20. v001. Undervolted at the level like X8Overclock: 0-2-3-5-7. If you have sudden reboots with out "SD card safe to remove", please report here.
Requirements:
- Rooted
- Baseband x15
Installation:
Manual installation: it will be better if you can do this way. From now on I will not provide update.zip for xRecovery, because there are some different modules now.
- Download appropriate x8uv-vXXX.zip (for X8), or x8uv-vXXX-x10m.zip (for X10 mini), or x8uv-vXXX-x10mp.zip (for x10 mini pro) below, unzip
- Remount /system as rw
- Push x8uv.ko in to /system/lib/modules
- Edit /system/etc/hw_config.sh, add one line at the beginning
Code:
insmod /system/lib/modules/x8uv.ko # x8 undervolt
Disclaimer
This module is dangerous! It may lead to system instability and may damage your hardware. I'm not responsible if this module kills your lovely phone. Use it at your own risk!
Donations are welcome
What about overvolt for x8overclock module it should fix reboots.
I am not able to do overvolt now, if you can, contribute Don't just say obvious things that I've known since the beginning.
Module runs smoothly, without problems.
Man... these modules just keep on coming and coming...
Sent from my X10mini using XDA Premium App
Thats great !
[ 5570.714701] x8uv: Module loaded. Built for target device: X8
[ 5570.863835] x8uv: patching done. enjoy better battery life.
Confirmed, so far no impact on performance or any problems, will see about battery
you're a great guy doixanh.
i want to ask, what sort of problem that COULD occur after installing this module? does this module have anything related to sd card safe to remove problem?
Problems may include : strange behavior, crash, reboot, force close apps... etc...
But because many people are running undervolted with x8overclock with (almost) no problem, you don't have to worry
Which apk can i use to set undervolted performances for X10 mini?
Sorry for my enhlish.
Can be used in combination with x8oc.ko hw_config.sh as I can adjust the combination of the two modules
https://github.com/doixanh/X8Undervolt gives me an 404 Error.
@doixanh
can you explain benefits of using this module in a few words here or up ?
it's maybe usual users don't know what the "under-volt" is .
many thanks in advanced....
[email protected]: I merged all repo into one, and forgot to change here. Thanks.
X1111: it makes your CPU run at lower voltages (compared to default), so it may save battery.
you're really the "Module Man"!
HOOORAH!
no reboots, system stable, smooth and fast as of now,
battery seems normal,
gonna observe more..
I think it isnt compatible with OC module ? A programme which associate undervoltage and cpu freq will be great.. Or an additional profile in setCPU f.e. oc 800, overvolt ; dc 480, undervolt
In dreams maybe
OC module includes this Read carefully...
k, maybe i've got a little pb with english ;p
If it's inclued i dont need this module, thks anyway
tibob77 said:
k, maybe i've got a little pb with english ;p
If it's inclued i dont need this module, thks anyway
Click to expand...
Click to collapse
U obviously miss the point of this module completely... Its made for the ppl who DONT want to overclock their X8, but they WANT to have their CPU run on lower voltages...
Great work man, will flash ASAP.
EDIT: I don't know where to ask this but since you are the "module man" I'll ask you. Can you create a module or something that will have forward/backward features on the volume keys in radio/mp3 playback ? I saw someone on the minicm thread talk about this but can't figure how to do it. This is a very usefull function if you listen to music/radio on your phone, so you just have to hold volume up/down to skip a play or get a new radio station. Will be waiting for an answer, and will be great if someone can get this done.
The idea is good but has nothing to do with modules. The music app already gets the values from volume buttons and cm7 allows it to use them when locked and screen off, now the music app could have an option for skipping on volume.. speak to cyanogen guys
CaptainZap said:
Great work man, will flash ASAP.
EDIT: I don't know where to ask this but since you are the "module man" I'll ask you. Can you create a module or something that will have forward/backward features on the volume keys in radio/mp3 playback ? I saw someone on the minicm thread talk about this but can't figure how to do it. This is a very usefull function if you listen to music/radio on your phone, so you just have to hold volume up/down to skip a play or get a new radio station. Will be waiting for an answer, and will be great if someone can get this done.
Click to expand...
Click to collapse
Sent from my X8 using XDA App
Hey guys! Today I have a quick question regarding scripts.
Happens that I just flashed ICS Stock V2 and noticed that it includes both: TurboBoost and LagFree scripts. Well, I decided to dig into them and I realized that both have many common lines (yes, I know you already know) but they're set to different values. It will be usefull for me to know if this scripts are "really compatible".
I also see that Max Events Per Seconds are set to 60, 55, 60 (those are just some of the lines I saw) instead of 150. I would like to know which value is better wether 60 or 150.
Thanks for your brilliant answers
jrxtepan said:
I also see that Max Events Per Seconds are set to 60, 55, 60 (those are just some of the lines I saw) instead of 150. I would like to know which value is better wether 60 or 150
Click to expand...
Click to collapse
I guess, after reading around, that lower is preferred because in stock roms Android wanted to support lots of apps running together and switching between them but often times more excessively than was required which led to decline in task and battery performance. But if you particularly want 'lots' of apps running at once then more is more...
i have searched and re-searched a lot of times for threads that talk about my same problem, but none of them is related to it in terms of phone, kernel or ROM, and they're all nearly 2 years old
in addition, i am new to this forum, so please don't shoot me
anyway here it is:
i've tried almost every existing method to get governors like smartassV2 and interactive (my favorites) to stick without reverting to ondemand, but none worked
i noticed this:
in the exact moment the screen is locked, something sets the governor to ondemand
in the exact moment the screen is UNlocked, the same thing (i guess) sets it to performance, then to ondemand
since i know a bit about intents and receivers, i can say this behavior is triggered by android.intent.action.SCREEN_OFF/ON intents, so there must be some system apk with a receiver for those which reacts and changes governor accordingly
right now i'm running a modded init.qcom.post_boot.sh that sets back the governor to a custom one (i.e. smartassV2) every 20 seconds, which is the only way i can get it to "stick", however i hate this method 'cause it implies there is a shell running in the background, thus stealing some (yet minimal) resources and battery, and the problem is still there
some info that might come in handy:
phone: Acer Liquid Glow E330
ROM: Glowing Liquid 1.5.2 (ICS)
kernel: Lupo's kernel V3
take a look at the logcat screenshot attached, i think i found something but i have no idea what to do
EDIT: if you can't read what's in the pic, it's saying something about a CpuGovernorService
how is it possible that nobody cares? i've given more info than anyone else on this problem people, experts, devs, anyone, say sumthin'
Maybe try tot set it with an app like trickster mod and set it on boot? Or try another ROM to see if its a system app. Sorry I dont really know the programming part..
Sent from my Galaxy Nexus using XDA Premium HD app
i'll disable my script and give it a shot, however there is no other ROM, only two existing alternatives are stock (which only has crappy ondemand) and glowing liquid by vache
EDIT: didn't work dammit
UPDATE: by raising the log level to 7 in a custom boot.img i can now see PrintK saying this:
cpu_policy->user_policy.governor name interactive, str_governor = ondemand
update_cpufreq_governor cpufreq_update_policy return = 0
as a linux user, i know that PrintK is basically the kernel talking to the user/log daemon, so i am now asking help to kernel developers for any clues about it, and maybe how to change that parameter (or whatever it is) in the kernel to get rid of ondemand
as difficult as this can be to figure out, i'm sure that this would be the end to many headaches, so anyone who knows about how linux kernels work please help me find the solution to this thing
Alright, i give up, ain't no answers here
Somebody close/delete this goddamned thread, please
Sent from my scumbag cheap phone
SuicideFlasher said:
Alright, i give up, ain't no answers here
Somebody close/delete this goddamned thread, please
Sent from my scumbag cheap phone
Click to expand...
Click to collapse
hello , i got the same E330 , stock rom but root and kernel LupoV3 , to set it at 1300 mhz and SmartassV2 , maybe try Android tuner , or some who got possibility to change CPU with screen on/off , i'll try to see ...
Vache did a release 1.6 of this Rom , and Acer too (Acer_AV044_E330_1.041.01_EMEA) you can found them at Acer-club.fr
tchao
Speedo.thc said:
hello , i got the same E330 , stock rom but root and kernel LupoV3 , i set 1300 mhz and SmartassV2 with nofrills CPU , it work well.
Vache did a release 1.6 of this Rom , and Acer too (Acer_AV044_E330_1.041.01_EMEA) you can found them at Acer-club.fr
tchao
Click to expand...
Click to collapse
If you look closely, it resets to ondemand every time the screen changes state
Sent from an utter FAIL phone
EDIT: the thing is, i do have a cpu tuner with wake/sleep profiles, i simply can't seem to have it doing its job
also i stick on stock kernel because the other ones have buffer problems with music, and i'm not sacrificing my flac files for
crappy mp3s
SuicideFlasher said:
If you look closely, it resets to ondemand every time the screen changes state
Sent from an utter FAIL phone
EDIT: the thing is, i do have a cpu tuner with wake/sleep profiles, i simply can't seem to have it doing its job
also i stick on stock kernel because the other ones have buffer problems with music, and i'm not sacrificing my flac files for
crappy mp3s
Click to expand...
Click to collapse
is it this one ? "CPU tuner (Rooted phones)" on play store , i give it a chance yesterday and it looks to do the job, more than nofrill etc .... no easy to set fine but if i see the log file 'journal' it works , i come back to "smartassV2" (wich is "virtuel" gov settings) after wake up and at enter calls ...
Speedo.thc said:
is it this one ? "CPU tuner (Rooted phones)" on play store , i give it a chance yesterday and it looks to do the job, more than nofrill etc .... no easy to set fine but if i see the log file 'journal' it works , i come back to "smartassV2" (wich is "virtuel" gov settings) after wake up and at enter calls ...
Click to expand...
Click to collapse
No, just the setcpu implementation in rom toolbox. anyway i tried that "cpu tuner" and it kept forcing the governor to ondemand despite the "normal" mode being set to interactive (and yes, "normal" was the current setting)
Sent from an utter FAIL phone
AIC Kernelfor LG G Pad 8.3 V500
Compatible with v500 STOCK BASED LG 4.4.2 roms ONLY! The "gamma improvement only" is available for other ROM's in the installer
This was just a private build that seems to have gained some demand to help with the v500 gamma issue. I have been running it the past week and it seems stable enough to share to other v500 users. I'm not a developer, I build and update TWRP for the Nabi tablets, have shared a few windows bat files, have a VB.net app to automate various mods to the Nabi's, and a lot of research of nvflash/APX nand formatting for the Nabi's. My only previous kernel builds were for the HP Touchpad for private use, and my Ubuntu computer. Basically taking what real developers have done and trying to make it work for my own use.
EDIT 5/11/14: I put the gamma improvement fix in just a stock kernel with no other changes, and the changes to CM11 kernel. There are 2 CM kernel version depending on which LG ROM you installed CM over to deal with the dimming issue at boot. Those are available in the new all in one installer.
Disclaimer:
Experimental. Use this at your own risk.
Please Please Please make a full backup of your tablet.
Base:
The starting source is V50020B from LG
Compiled with arm-eabi-4.7
Added features:
Initial
Improved gamma. Using default linear LUT (from 1.8-2.0 to 2.2-2.3 on my screen)
Default overclock from 1.72 to 1.78Ghz (no voltage increase)
Default underclock to 162 Mhz
Sysfs Voltage Table added for undervolting
Allow GPU to manually increase freq from 400Mhz to 487Mhz
Add GPU boost to GPU on demand governor
Add Faux Display interface (gamma control seems broken)
Add NTFS support(untested)
Add SIO Scheduler
Add FIOPS Scheduler
Optimize memcopy, string and square root functions
Add Intelliactive Governor
Download:
BETA: http://nabtabhacks.com/downloads/AICbeta2.zip Very stable but haven't got enough feedback to make it official. See changes here http://forum.xda-developers.com/showpost.php?p=54482330&postcount=229
Installer for all gamma improvement kernels, tested by numerous members(AIC, stock, and CM) http://nabtabhacks.com/downloads.htm
Installer AIC Kernel: http://nabtabhacks.com/downloads.htm
Uninstaller, returns to stock 20B: http://nabtabhacks.com/downloads.htm
Install:
Reboot to recovery(TWRP)
Make a backup, just do it
Install AIC_kernel_flashable.zip
Wipe caches/dalvik if you see fit
Reboot
Source:
AIC: https://github.com/aicjofs/android_kernel_lge_v500
Stock with gamma only: https://github.com/aicjofs/android_kernel_lge_v500_stock
CM: https://github.com/aicjofs/android_kernel_lge_v500_cm
Credits
I need to give some specific acknowledgement to "oubeichen" for sharing his kernel tree, and sharing of information. Also to id10terror's install script was the easiest to use as a template.
Woohoooo, Finally some gamma correction love. Flashing now
ROM: LG-V500_KOT49I.V50020B_US_Stock-BB-Rooted
Working much smoother with your kernel, thank you for sharing!
Tested it yesterday and it made a subtle but noticeable difference to whiteness and brightness. Thanks again
Sent from my LG-V500 using XDA Free mobile app
Am really eager to try! Thx a million times @op!
So only run this if you're on a stock ROM not cm?
Sent from my LG-V500 using XDA Premium 4 mobile app
xyojimbox said:
So only run this if you're on a stock ROM not cm?
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Correct
Sent from my LG-V500 using XDA Free mobile app
tested with LRS ROM (stock based ) , working perfectly!
many thanks!
Gamma has been corrected perfectly. Antutu benchmark increases from 24,631 to 25,669. Two minor issues: 1) a secure boot error message is displayed during every boot though the boot process is fine (signature issue?); the display is dimmer (about 20%) after sleep as compared to that immediately after boot (any workaround?)
Sent from my LG-V500 using Tapatalk
bloommax said:
Gamma has been corrected perfectly. Antutu benchmark increases from 24,631 to 25,669. Two minor issues: 1) a secure boot error message is displayed during every boot though the boot process is fine (signature issue?); the display is dimmer (about 20%) after sleep as compared to that immediately after boot (any workaround?)
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Nice increase on Antutu.
Secure boot error is normal with any custom boot image. Are you saying it stays on the screen once the LG logo starts "shimmering"?
Do you have auto brightness or manual brightness?
I have seen a couple of patches that might address that. I will give them a look next time I build. I want to turn off a debug config that makes the modules larger, intelliactive governor tops out at 1.72 instead of 1.78 by default, add exfat, and look in to replacing mpdecsion, maybe row scheduler. When I do that I will look at the dimming.
Before I do the above I was looking at anykernel script as some people have asked if I could make this work for other ROM's other then stock ROM's.
So anyone else notice anything thats an issue? Gamma decent? Stable? Probably only 3 of you, haha but I still am curious.
aicjofs said:
Nice increase on Antutu.
Secure boot error is normal with any custom boot image. Are you saying it stays on the screen once the LG logo starts "shimmering"?
Do you have auto brightness or manual brightness?
I have seen a couple of patches that might address that. I will give them a look next time I build. I want to turn off a debug config that makes the modules larger, intelliactive governor tops out at 1.72 instead of 1.78 by default, add exfat, and look in to replacing mpdecsion, maybe row scheduler. When I do that I will look at the dimming.
Before I do the above I was looking at anykernel script as some people have asked if I could make this work for other ROM's other then stock ROM's.
So anyone else notice anything thats an issue? Gamma decent? Stable? Probably only 3 of you, haha but I still am curious.
Click to expand...
Click to collapse
It is nice to see you doing some kernel development! Uploading your kernel to XDA will also allow you to keep track of how many users have downloaded your kernel. You may be surprised. I'm guessing more in the 75-150 range so far.
I have been using the kernel all day and it's working great! Thanks!
As I mentioned in the other thread that you first posted this I have been using Infected's build of SimKat and thus this would not have been compatible.
But curiosity got the better of me and so I restored my backup of the stock ROM to install this kernel and see if I too noticed a difference...
Now I'm torn between the obvious advantages of using the stock ROM with this kernel (many thanks for that) or to go back to the preferred SlimKat build of KK and then lose he differences that this kernel brings.
Talk about a rock and a hard place - lol
Many thanks again for the kernel and sharing it with us
sleekmason said:
It is nice to see you doing some kernel development! Uploading your kernel to XDA will also allow you to keep track of how many users have downloaded your kernel. You may be surprised. I'm guessing more in the 75-150 range so far.
Click to expand...
Click to collapse
Thank you good sir! Without SleekAI the 510 users would just have to run stock
I didn't even think to look on Box.net. Says 69 so you were close. I need to swap it over to my NabTabHacks website, I could monitor it there.
vimesUK said:
As I mentioned in the other thread that you first posted this I have been using Infected's build of SimKat and thus this would not have been compatible.
But curiosity got the better of me and so I restored my backup of the stock ROM to install this kernel and see if I too noticed a difference...
Now I'm torn between the obvious advantages of using the stock ROM with this kernel (many thanks for that) or to go back to the preferred SlimKat build of KK and then lose he differences that this kernel brings.
Talk about a rock and a hard place - lol
Many thanks again for the kernel and sharing it with us
Click to expand...
Click to collapse
Well I combed over the anykernel script today. It copies the ramdisk out of whatever ROM you are currently running and then inserts just the kernel then copies modules over. Nothing elaborate but slick in the fact that you don't have to go messing with the ramdisk each time a ROM has an update that effects the ramdisk. I was thinking of doing it manually which would be a huge time sink.
Where the problem could be though is kernel module functionality. Let's take CM for example, I'm not sure the DSP Sound would work if what I describe above was used. Also there is the mobicore modules for example that aren't in this kernel. Speaking of other ROM's another bug would be the screen dimming for those running 4.2.2 base. While changing to 4.4.2 should clear it up it's still not plug and play solution. It's weird I thought I had a good grasp on what was happening with the dimming. If you look at board-palman-display.c(V510 GPE) and board.awfi-display.c(V500) and look at the lm3532 backlight stuff, you can see that values for palman start ridiculous low ~3, where awfi starts at 133 or something I think. Palman uses linear mapping and awifi uses exponential mapping. When I swapped those values I got the screen dimming at boot too. Problem is all that get swapped when installing a ROM and bootimg, so thats not it, or at least not in entirety.
Who knows... I guess in short I might have something to put together for all ROM's but what it breaks is quite unknown.
aicjofs said:
Thank you good sir! Without SleekAI the 510 users would just have to run stock
I didn't even think to look on Box.net. Says 69 so you were close. I need to swap it over to my NabTabHacks website, I could monitor it there.
Well I combed over the anykernel script today. It copies the ramdisk out of whatever ROM you are currently running and then inserts just the kernel then copies modules over. Nothing elaborate but slick in the fact that you don't have to go messing with the ramdisk each time a ROM has an update that effects the ramdisk. I was thinking of doing it manually which would be a huge time sink.
Where the problem could be though is kernel module functionality. Let's take CM for example, I'm not sure the DSP Sound would work if what I describe above was used. Also there is the mobicore modules for example that aren't in this kernel. Speaking of other ROM's another bug would be the screen dimming for those running 4.2.2 base. While changing to 4.4.2 should clear it up it's still not plug and play solution. It's weird I thought I had a good grasp on what was happening with the dimming. If you look at board-palman-display.c(V510 GPE) and board.awfi-display.c(V500) and look at the lm3532 backlight stuff, you can see that values for palman start ridiculous low ~3, where awfi starts at 133 or something I think. Palman uses linear mapping and awifi uses exponential mapping. When I swapped those values I got the screen dimming at boot too. Problem is all that get swapped when installing a ROM and bootimg, so thats not it, or at least not in entirety.
Who knows... I guess in short I might have something to put together for all ROM's but what it breaks is quite unknown.
Click to expand...
Click to collapse
Have you looked at the install script I use for the 510? You have the ability to change ramdisk files on the fly using sed (easiest language I could find), by opening the device ramdisk, insert one liner, close ramdisk, combine into boot.IMG.
I have a couple of simple changes for allowing tethering, and values that I couldn't make without it! This part of it may work for you!
aicjofs said:
Nice increase on Antutu.
Secure boot error is normal with any custom boot image. Are you saying it stays on the screen once the LG logo starts "shimmering"?
Do you have auto brightness or manual brightness?
I have seen a couple of patches that might address that. I will give them a look next time I build. I want to turn off a debug config that makes the modules larger, intelliactive governor tops out at 1.72 instead of 1.78 by default, add exfat, and look in to replacing mpdecsion, maybe row scheduler. When I do that I will look at the dimming.
Before I do the above I was looking at anykernel script as some people have asked if I could make this work for other ROM's other then stock ROM's.
So anyone else notice anything thats an issue? Gamma decent? Stable? Probably only 3 of you, haha but I still am curious.
Click to expand...
Click to collapse
I kept auto brightness disabled. It does not work well for 4.4.2. You may replicate the brightness issue with the following procedure: 1) reboot the tablet; 2) when adjusting the brightness slider, you will find 0% is very (too) bright, and the entire range is high; 3) after sleeping and waking, the brightness is much dimmer, and the entire range from 0% to 100% is lower in brightness. It seems a procedure during wake modified the range of brightness settings.
Sent from my LG-V500 using Tapatalk
Run with stock kernel 20B. I will test urs by now
Well after having to do a complete reinstall due to another issue, I tried this kernel. Man I've only used it for a few hours but color me highly impressed :good: My gamma is almost perfect and it seems noticeably faster and smoother.
Really great job and thanks.
How is the battery life?
aicjofs said:
Thank you good sir! Without SleekAI the 510 users would just have to run stock
I didn't even think to look on Box.net. Says 69 so you were close. I need to swap it over to my NabTabHacks website, I could monitor it there.
Well I combed over the anykernel script today. It copies the ramdisk out of whatever ROM you are currently running and then inserts just the kernel then copies modules over. Nothing elaborate but slick in the fact that you don't have to go messing with the ramdisk each time a ROM has an update that effects the ramdisk. I was thinking of doing it manually which would be a huge time sink.
Where the problem could be though is kernel module functionality. Let's take CM for example, I'm not sure the DSP Sound would work if what I describe above was used. Also there is the mobicore modules for example that aren't in this kernel. Speaking of other ROM's another bug would be the screen dimming for those running 4.2.2 base. While changing to 4.4.2 should clear it up it's still not plug and play solution. It's weird I thought I had a good grasp on what was happening with the dimming. If you look at board-palman-display.c(V510 GPE) and board.awfi-display.c(V500) and look at the lm3532 backlight stuff, you can see that values for palman start ridiculous low ~3, where awfi starts at 133 or something I think. Palman uses linear mapping and awifi uses exponential mapping. When I swapped those values I got the screen dimming at boot too. Problem is all that get swapped when installing a ROM and bootimg, so thats not it, or at least not in entirety.
Who knows... I guess in short I might have something to put together for all ROM's but what it breaks is quite unknown.
Click to expand...
Click to collapse
In my ignorance I was not aware of what could implicate the brightness values and range on this tablet. Having only just bought it, and upgraded to KK right away, I was not aware of how JB performed, in that respect. Prior to your kernel I was using the Screen Adjuster app as a sort of fix to compensate for the comparative (to my other tablets and phones) lackluster screen performance of the tablet. With the SlimKat ROM I was experiencing, but might have overcome them, some dimming issues which I did not understand.
Since restoring the stock KK backup and using your modified kernel I no longer need the screen adjuster app and things do seem to have improved.
I'm not responsible for any damage to your device. So be advised.
Kernel Features:
-CPU Overclocked (BIG cores to 2.01GHz (experimental, i should reduce and / or disable it if too many users notify instability in F5122 (that is my personal device));
-AdrenoBoost;
-Slimbus (Audio bridge) Overclocking;
-WCD9335 HiFi selector and tunnings louder audio at kernel side;
-WSA8810 tunnings for better and louder audio in speaker;
-CRC disabled;
-DTS Eagle sound integration;
-300 Hz instead 1 kHz for kernel timer (saves power);
-Boeffla Wakelock blocker;
-Quick charge tweaks (2100mA constant charging for QC 2.0 / 3.0 enabled chargers, drawing about 1,6 Amps from wall PSU);
-Tunned voltage regulators for CPU and GPU enabling High Power Mode;
-Kernel general optimizations;
-WIP: add klapse and kcal;
-Enable 160 MHz clock in crypto engine for faster crypto operations.
Special thanks to:
@stefanhh0 github user (idk what is the nick here, please, pm me and i add it if you want) for keeping a source with newer mainline (i guess) patches;
@franciscofranco for many commits that help us improving performance and saving power;
Sony AOSP team;
And others that maybe i forgot to tag here but all them are in the github code below:
https://github.com/LuizPauloDamaceno/kernel
Inside the zip that you can download below, you will find the initial release. You should flash it by fastboot and them reinstall magisk if you have it. Also, have two xml files that is a complementing of the audio tweaks in android side, enabling CLSH_LOHIFI mode in the audio processor and tunning volumes. From mic to headphones and speakers. The thermanager is the one that you should install it for improved thermal handle with this kernel. Dont worry, things shouldn't fry, but is not my fault if them fry. As another complemention, i've done a "userdata" partition for users who have 64 GB variants, like me. The AOSP is compilled for 32 GB i guess and we have only half of our full capacity. Flashing userdata (obviously, will erase your data partition and you will loose everything like is done in the first AOSP flashes if you dont do a back-up...) you will also have more free space
Kernel: fastboot flash boot boot.img
Userdata: fastboot flash userdata userdata.img
To copy the below files i like to use root explorer app, you can also do by adb. I'm open for suggestion of better apps too
mixer_paths.xml: copy it to /system/vendor/etc/mixer_paths.xml and change permissions to 0644 octal or rw-r-r.
thermanager.xml: copy it to /system/vendor/etc/thermanager.xml and change permissions to 0644 octal or rw-r-r.
The first versions i will not do the automated flashing because are the initial and testing releases, but if my plans goes ok for the next 15 days or in the worst case next month, i can do a twrp flasheable style to make our lives easier. For me, no random reboots, no overheating for normal use and battery stills ok. Report it your experience, i will appreciate to know! =D
https://androidfilehost.com/?fid=4349826312261806431
Hope you all enjoy this, guys!
Luiz
Download link edited.
LuizPauloDamaceno said:
Download link edited.
Click to expand...
Click to collapse
It's awesome that you still keep these kernels up to date. Really appreciate the work.
I've been switching between v14 and v33 of your extreme kernels today for GPU testing. Didn't expect to see a kernel for Pie. I hope you'll update the one for Oreo as well, it's always great to see new changes. Thanks again!
Could this one be used with LineageOS 16 Custom Rom by chippa?
LOLisLIFE said:
It's awesome that you still keep these kernels up to date. Really appreciate the work.
I've been switching between v14 and v33 of your extreme kernels today for GPU testing. Didn't expect to see a kernel for Pie. I hope you'll update the one for Oreo as well, it's always great to see new changes. Thanks again!
Click to expand...
Click to collapse
I've stopped oreo because I didn't see any advantages to me to keep it updating, i do this for fun and based in my use. Now i'm using pie, so, i think is fare to start a Pie project...
justfun598 said:
Could this one be used with LineageOS 16 Custom Rom by chippa?
Click to expand...
Click to collapse
I dont know, i dont have sure if could be used because maybe the drivers are different. If the LiOs uses 3.10 kernel then dont, you cant, because the drivers of 4.9 kernel is quite different.
justfun598 said:
Could this one be used with LineageOS 16 Custom Rom by chippa?
Click to expand...
Click to collapse
LineageOS 16 by chippa uses 3.10 so no, I'll not boot.
@LuizPauloDamaceno i'll test it on the we with aosp 10 instead (already built against 4.9 kernel) and see how it behaves) thanks for your work.
ParanoidNemo said:
LineageOS 16 by chippa uses 3.10 so no, I'll not boot.
@LuizPauloDamaceno i'll test it on the we with aosp 10 instead (already built against 4.9 kernel) and see how it behaves) thanks for your work.
Click to expand...
Click to collapse
Thank you for the test! I will stay in AOSP Pie for a while since i've built mine one following the sony's tutorial for now. Wainting for the results
So, who tested it the first release? Any observations? soon i will post the second release with some improvements.
I tested the first release on AOSP pie. The battery life is quite good but i needed to set big cores frequency back to 1.8, because the phone heats up a little bit. I also noticed a bug but i don't know if it's due to the rom or to the kernel: sometimes (not too frequently) the system ui force closes without any message. The screen becomes black and after a few seconds it turns on with lockscreen.
Anyway, as wel as in other roms, Whatsapp voice notes are very quiet; can this be solved with mixer path?
Thank you for your effort
Lihxor said:
I tested the first release on AOSP pie. The battery life is quite good but i needed to set big cores frequency back to 1.8, because the phone heats up a little bit. I also noticed a bug but i don't know if it's due to the rom or to the kernel: sometimes (not too frequently) the system ui force closes without any message. The screen becomes black and after a few seconds it turns on with lockscreen.
Anyway, as wel as in other roms, Whatsapp voice notes are very quiet; can this be solved with mixer path?
Thank you for your effort
Click to expand...
Click to collapse
When you say voice notes are not very quiet you say about noise or too loud?
About the frequency, yes, the higher frequencies is intended to who wants to play certain games with higher performance or just perform better other applications, but everything has the "dark side". In some AOSP roms (i think all) you have random reboots because the 1.95 GHz is enabled without any overvoltage, so, the clock cannot be sustained by the system and the CPU crashes. I recommend if you want to use these clocks to have a fan in a joystick for example... And if you use is only the daily, use the stock frequencies. =D
About the lockscreen and sysui stop answering, i've also observed this without kernel modifications. So i think can be something from ROM or kernel that isn't related to hardware changes. Can be investigated. For 3 days now that this problem not showing here...
LuizPauloDamaceno said:
When you say voice notes are not very quiet you say about noise or too loud?
About the frequency, yes, the higher frequencies is intended to who wants to play certain games with higher performance or just perform better other applications, but everything has the "dark side". In some AOSP roms (i think all) you have random reboots because the 1.95 GHz is enabled without any overvoltage, so, the clock cannot be sustained by the system and the CPU crashes. I recommend if you want to use these clocks to have a fan in a joystick for example... And if you use is only the daily, use the stock frequencies. =D
About the lockscreen and sysui stop answering, i've also observed this without kernel modifications. So i think can be something from ROM or kernel that isn't related to hardware changes. Can be investigated. For 3 days now that this problem not showing here...
Click to expand...
Click to collapse
Thanks for the answer. Btw, i meant that voice notes are quiet, so their volume is too low to be heard
Can anyone do a benchmark using antutu and stock 4.9 kernel (not this one) just to compare it? Following screen from next version that I should post soon. With 4.9.224 Linux and many more features.
LuizPauloDamaceno said:
Can anyone do a benchmark using antutu and stock 4.9 kernel (not this one) just to compare it? Following screen from next version that I should post soon. With 4.9.224 Linux and many more features.
Click to expand...
Click to collapse
I took this one a year ago with Omni and 4.9 kernel, I recall performance was terrible on all 4.9 ROMs back then.
On your run I noticed that CPU scores is still lower than stock 8.0 with 3.10 kernel (that one got 46k on CPU and 17k on GPU), but I think it's better than anything we have currently.
By the way @ParanoidNemo how was the kernel running on AOSP 10?
iH8Ecchi said:
By the way @ParanoidNemo how was the kernel running on AOSP 10?
Click to expand...
Click to collapse
Been stuck with a lot of work and not tried yet. Will report as soon as I've time to try it.
iH8Ecchi said:
I took this one a year ago with Omni and 4.9 kernel, I recall performance was terrible on all 4.9 ROMs back then.
On your run I noticed that CPU scores is still lower than stock 8.0 with 3.10 kernel (that one got 46k on CPU and 17k on GPU), but I think it's better than anything we have currently.
By the way @ParanoidNemo how was the kernel running on AOSP 10?
Click to expand...
Click to collapse
Interesting, thank you for feedback. Yes... CPU score in 4.9 kernels is lower than 3.10. I think is something related to KPTI mitigations or something else... Concerning you're using OMINI rom... Is the wifi thetering working well? I have troubles with AOSP related with that and i thinks is not related to kernel. Thank you.
LuizPauloDamaceno said:
Interesting, thank you for feedback. Yes... CPU score in 4.9 kernels is lower than 3.10. I think is something related to KPTI mitigations or something else... Concerning you're using OMINI rom... Is the wifi thetering working well? I have troubles with AOSP related with that and i thinks is not related to kernel. Thank you.
Click to expand...
Click to collapse
I did this run a year ago, haven't tested that yet. I've since switched to Lineage GSI (with Sjll's modified 4.9 kernel), and tethering/hotspot works fine.
Just flashed on latest AOSP pie by vknecht and it's work like a charm. No major bugs by far, rom is stable and fast, phone doesn't get really hot even without underclock. Im staying on it because ViPER4Android working with this setup unlike on LOS 16.
adi_adi said:
Just flashed on latest AOSP pie by vknecht and it's work like a charm. No major bugs by far, rom is stable and fast, phone doesn't get really hot even without underclock. Im staying on it because ViPER4Android working with this setup unlike on LOS 16.
Click to expand...
Click to collapse
Have you some random reboot or not with the aosp9 by vknecht?
ParanoidNemo said:
Have you some random reboot or not with the aosp9 by vknecht?
Click to expand...
Click to collapse
Well, random reebots still occur unfortunately, but most on demanding tasks. I'm not an expert, but I don't think this is a kernel issue.