Related
What this kernel does is provide slightly less voltage to the processor. This should not be dangerous for anyone to try, however it may be unstable or just result in general weirdness on a few phones. If it does, all you have to do is revert back to the kernel you had before.
The upsides to less voltage are less heat as well as less power consumption. That means battery life
Remember, this one is running at stock speeds.
Get it on Koush's RomManager (download RomManager from the market) I'll post changelogs in this thread from now on, but keep the kernel on RomManager.
Changelog 8/29:
Lots of stuff.. I dunno.. Look at the CM6 kernel changelog (I've been working on that).
Biggest thing IMO is the usleep stuff which lowers CPU usage and therefore increases battery life.
Note: only tested on CM6. Let me know if you try it on any other roms.
Link: http://kanged.net/up/files/5/kernels/signed-August26-UV950.zip
Changelog 6/20:
Ermm.. I've been releasing my kernels on twitter.. but I'm finally happy with this one.
-Latest Cyan commits
-Minor voltage tweaking
-erm... yeah I dunno.
Get it here http://kanged.net/kmobs/signed-619UV-34.zip or from RomManager.
Changelog 5/14:
-Reinstated those commits reverted earlier.
-Updated to .33.4
-Only doing a 925mV kernel due to the results from the blind study
Changelog 5/1:
-Reverted the following commits thanks to intersectRaven. I think they were the reason for the excessive battery drain.
27dd25f80402a13f9d5c381eda07b560e5545fcc
1490683fb851b992722cbd175d3df087df833656
f2513498e961966d3209aacfffc43de4f41f2ece
-Updated to latest CM source (minus those commits)
Changelog 4/21:
Fixed the board-mahimahi.c in the 850mV kernel.
OLD updates and changelog:
http://iq0.org/story/yet-another-nexus-one-kernel-now-battery-saving
Note: Now offering a universal update.zip method for flashing the kernel (big thanks to Koush for this one)
Thank you www.tdrevolution.com for hosting my work.
Does it still have the highmem?
GEtting an access denied message, Seems the post doesnt exist
Great job. Will get you a logcat if I get any random weirdness.
Maybe now my battery can last longer then my G1 battery did when I am at work.
Anyone care to make an update.zip for those of us without computers nearby to check this out?
Tested and functional with Enomther 1.61. Thanks a lot
What is the CPU voltage and is the some app that can show it?
Running this new kernel at 576/245 mHz, wifi off, 3G connection, brightness set to automatic. will report back with battery life as soon as it runs out. lol
Off of charger: 11:34AM , Wednesday, February 17, 2010
Battery completely drained: TBA
DocRambone said:
Tested and functional with Enomther 1.61. Thanks a lot
What is the CPU voltage and is the some app that can show it?
Click to expand...
Click to collapse
Hey do report if there is any improvements... meanwhile can someone make it into to an update.zip for us?
mgear356 said:
Hey do report if there is any improvements... meanwhile can someone make it into to an update.zip for us?
Click to expand...
Click to collapse
I will, phone seem ok so far, BenchmarkPi at 2670
No slowdowns or reboots during benchmarks or gameplay. Phone feel cooler tho
I'll give this a shot.
Mi|enko said:
Does it still have the highmem?
Click to expand...
Click to collapse
just flashed it. yes it does. my phone hasnt exploded yet either...
Mi|enko said:
Does it still have the highmem?
Click to expand...
Click to collapse
Yes
To those asking for an update.zip: I don't to package this into something that will be easily flashable by all, including those that may not understand the risks (I don't think there are any with this kernel, but can't be sure). I want there to be some rudimentary knowledge of android before someone goes and flashes this and potentially messes up their phone.
Does that make sense? I feel that there should be a barrier to entry on kernels that OC and the like.
What voltages is it for different MHz?
great job, really need something like this... im trying it out! thanks
DocRambone said:
What voltages is it for different MHz?
Click to expand...
Click to collapse
Its not across the board, and I'm not home right now to tell you, but 245 is at 1.0 vs 1.05 and 998 is at 1.250 instead of 1.275
persiansown said:
Yes
To those asking for an update.zip: I don't to package this into something that will be easily flashable by all, including those that may not understand the risks (I don't think there are any with this kernel, but can't be sure). I want there to be some rudimentary knowledge of android before someone goes and flashes this and potentially messes up their phone.
Does that make sense? I feel that there should be a barrier to entry on kernels that OC and the like.
Click to expand...
Click to collapse
I do understand what your saying, I don't think its that much of a barrier though. There are many instructions throughout these boards that will let anyone who is even remotely interested flash a new kernel and push a .ko to their phone... The only reason why I want an update.zip is so that I can flash this on my phone to test it while I'm at work, it would also be nice to be able to switch quickly between kernels and whatnot. I don't have a computer that I can connect to via USB to run fastboot/adb so the only way I can get these on my phone is via a zip.
I don't think that a developer/hacker can be held responsible for others not knowing what issues can be caused by a voltage/clock tweak - especially with disclaimers up everywhere.
FettsVett said:
I do understand what your saying, I don't think its that much of a barrier though. There are many instructions throughout these boards that will let anyone who is even remotely interested flash a new kernel and push a .ko to their phone... The only reason why I want an update.zip is so that I can flash this on my phone to test it while I'm at work, it would also be nice to be able to switch quickly between kernels and whatnot. I don't have a computer that I can connect to via USB to run fastboot/adb so the only way I can get these on my phone is via a zip.
I don't think that a developer/hacker can be held responsible for others not knowing what issues can be caused by a voltage/clock tweak - especially with disclaimers up everywhere.
Click to expand...
Click to collapse
Oh I understand where you're coming from, and I would make you a private one, but I'm not home at the moment. However, for the general user, if they can't use fastboot, I don't want them anywhere near this. I hope someone makes you an update.zip!
I await the PM's!
Dear lord what am I going to do with this should I get my 2800mah battery? my phone will never die! lol
-Charlie
FettsVett said:
I await the PM's!
Click to expand...
Click to collapse
you can make one yourself.
grab boot.img from cyanogen's rom.
grab split_bootimg.pl from http://android-dls.com/files/linux/split_bootimg.zip
grab persiansown's zImage.
(in linux)
put all three in a folder. let's call it kernel.
while in the kernel folder:
./split_bootimg.pl boot.img
mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel zImage-persiansown --ramdisk boot.img-ramdisk.gz -o boot-persiansown.img
(in windows)
download this: http://www.sendspace.com/file/kj2wi7
use winrar to open up that up, remove the boot.img in there and replace it with boot-persiansown.img (make sure it is named boot.img)
open up the update-script in META-INF folder (some levels down in there), and remove the format BOOT line (you'll be left with write_raw_image ... line), and save it.
grab this: http://www.relentlessaddictions.com/Androidstuff/signing.zip
unpack to your tools folder in your android-sdk folder distribution, and run autosign.bat. follow the prompts. once setup, you can right click on the .zip file with the boot.img in it to sign it, or you can execute from a cmd prompt: java testsign BOOT-IMG.zip
flash via custom recovery (which can flash .zip's signed with test keys).
you should be all set.
edit: mkbootimg can be found in prebuilt within AOSP distribution, or you can grab this precompiled one: http://forum.xda-developers.com/attachment.php?attachmentid=229872&d=1253485580
This file protects your phone from running below a dangerous level and potentially rendering X10 devices to an unusable or hard brick.
Hello XDA developers
Latest Version 3 :: Please use the latest version and report back the contents of - /data/local/tmp/extract_charger_status.txt - with any issues and state which firmware you were using this with.
I've identified an issue after killing an X10a involving the offline charger. I hope the following can save any further problem's by using the following charger_fix_v3.zip with xRecovery as it is a simple case of rebooting into xRecovery and loading the update. This file is safe for X10 owners as it introduces a stock SE file back to the system, which if not present can render the system a brick.
[ROM] - TripNRaVeR - TripNMiUI - should not be used with this patch as an unknown issue exists with the charger that is currently being researched, until further notice DO NOT apply this update if you are using TripNMiUI or any variant.
There is no SETUID for Android. Android developers state there is no need as Dalvik code will never require elevated or root permissions and hence, it introduces a potential security flaw.
Q: What is it?
A: SE Official charger file - /system/bin/charger - has special permissions which can not be set by root or any other user, the file need's to be moved into place, as it contains setuid or the "Sticky" Unix file system permission.
Wait! How about - chmod 06755 or chmod 04755 - I hear you say? Forget it.. This is not a simple file, it's a Linux binary an ELF Linker file that contains critical system links to (among others//).. the following;
Code:
/sys/class/power_supply/battery/capacity
/sys/devices/platform/msm_pmic_vibrator/enable
/system/bin/chargemon
Nothing special here? Well if you say so! Wait does this look familiar to anyone?
Code:
/sys/class/leds/lv5219lg
RGB LED interface
WLOD (white led of death) issues, or seeing three red blinking led lights
Code:
/sys/class/power_supply/usb/online
/sys/class/power_supply/ac/online
/system/etc/semc/chargemon
This charger file defines the CPU scaling and governor, which is of massive importance to anyone having issues with poor battery life and general performance of their custom rom
For anyone working with customizations around chargemon, you need to include this file and ensure to include - /system/bin/charger - as an entry in any modifications to chargemon right after
#!/system/
It should ALWAYS be the 2nd line in the chargemon file. No questions asked, this file must be optimized and present, it can not be a touch file with any old permission set assigned!
(*ATTN ALL ROM DEVELOPERS*)
Important lesson when handling Android files. You must set the correct permissions and assign the correct security groups - setuid - as they are held in memory. If a part of code executes and is unable to reach the expected memory - WLOD
Not to be patronizing or arrogant, I suspect the issue arrived with Froyo (now in Beta 4), which made it's way via TripNrAvER to a further ROM developers and the issue exists and is present in many (possibly all 2.2.1 Froyo x10 roms) although most user complaint's arrive in strange or hard to understand messages, which is too often interpreted around the forums as just being n00bish and not knowing how to use SEUS or Flashtool...
This thread is specifically for ROM developers and is a deep technical issue. Please do not move this thread to apps or general
/data/local/tmp/charger.tar.gz
Click to expand...
Click to collapse
Thank you DoomLoRD, Androxyde, Bin4y, Zdzihu & Jerpelea for their excellent work and patience, who without their presence and effort on XDA the X10 would never be half of what it is today
EDIT: - v1 was not copying to location correctly - v2 uploaded
updates
Latest! - zdzihu has released a new version which is for Beta 4 variants specifically - http://www.mediafire.com/?5rr5ygl1udldla1
This fix should not be applied on Trip's MIUI ROM until further notice!
Thanks to My_Immortal & kmilof for pointing out that there is an issue with TripNRavER MIUI
Unsure why there was a problem with TripNMui, I will investigate. The permission groups are different and am investigating.
1: Replaces a critical system file with correct system permissions.
How to tell if this exists or if you need this update? It's very easy Using a file explorer (i.e; Root Explorer) also others work, browse to the directory; /system/bin/ <- look for the file charger as @cobrato pointed out, it should be identical.
14356 = Binary file size
-rwsr-xr-x = Unix file permission
The permissions are the important part and during the night it was posed, this could be handled with the following command - busybox chmod u+s - while this is true, it is context sensitive. For example if this command is issued in the context of root, the setuid is included and created for root. This file belongs to a special group which can't be modified. If anything it should reset permissions on a file which exists and enable correct permissions on the charger and enable it to work again.
It appears to have been too late for one x10 last night. I received another P.M of death by USB and the problem is real and has claimed many devices, although I am having a hard time pinpointing what caused it, I'm unable to say that much other than this is potentially a cure if even partial as pointed out by picking up on a modification from DooMLoRD, to optimize offline charging.
To prevent your x10 from battery death after modification, never allow the battery to run below 5% - replacing battery might be the only hope if this happens!
Thanks for your effort in explaining what this zip does.
Not entirely sure what it all means but I understand it to mean everyone on any 2.2 CUSTOM ROM should flash this. I will do so and report back any issues.
PS. I have never had a WLOD FC yet.
BB58 wolfbreak latest update and tweaks test zip. Stock kernal
EDIT: Flashed onto WB ROM...no issues so far.
Sent from my X10i using XDA App
@mrHassell
my question is, do we need to flash this everytime we flash a new rom or is it something that just needs to be done once?
I have said before, but thanks again for your tirelress work, you too give a great deal to our x10 forum, thanks for your hardwork my friend.
smartgardens said:
@mrHassell
my question is, do we need to flash this everytime we flash a new rom or is it something that just needs to be done once?
Click to expand...
Click to collapse
Well if the new Custom Roms that will be developed from now onwards include it you won't need to flash it every time but lets said that you'll be flashing FreeX10Beta4 or WB CM 6 ROMS you'll have to do it every time since those ROMS doesn't include it for now and every time you flash a new ROM it overwrites the existing /system/bin folder...
Jim
not so sure what is the uses.
i flashed this in TripNMiUI FINAL 1.0.63.. after bootanimation screen's turn black, cant do anything =/.
kmilof said:
i flashed this in TripNMiUI FINAL 1.0.63.. after bootanimation screen's turn black, cant do anything =/.
Click to expand...
Click to collapse
I flashed it over Trip's 1.0.2 and everything went fine. Phone booted normally.
I haven't 100% understood what it does, but it certainly did not do me any damage.
Did you make a nandroid before flashing?
My_Immortal said:
I flashed it over Trip's 1.0.2 and everything went fine. Phone booted normally.
I haven't 100% understood what it does, but it certainly did not do me any damage.
Did you make a nandroid before flashing?
Click to expand...
Click to collapse
yup, i did make a nandroid before flashing, i could restore it and the everything went back to normal.
maybe something changed between trip 1.0.2 and 1.0.63
Thank you for this one
I flashed this over reindeiro's scramble ROM without any issues. Thanks for this.
Sent from my X10i using XDA App
Not entiley sure what this is for but still flashed into beta 4 all ok. Thanks
sent from my Z orignal and modded 2.2 powered c64
chiefy009 said:
Not entiley sure what this is for but still flashed into beta 4 all ok. Thanks
sent from my Z orignal and modded 2.2 powered c64
Click to expand...
Click to collapse
Me, too..
Can somebody explain?
Anyways, installed succesfully on Trip's MIUI 0.0.98. (The IRIS one.)
A few people saying their phones have been bricked (thinking they were, you can't brick an x10) and getting either a wlod, or three blinking red led flashes, because their battery level got so low and they were unable to offline charge it.
This fixes it and makes sure that cannot happen.
That is what it is for...
fiscidtox said:
A few people saying their phones have been bricked (thinking they were, you can't brick an x10) and getting either a wlod, or three blinking red led flashes, because their battery level got so low and they were unable to offline charge it.
This fixes it and makes sure that cannot happen.
That is what it is for...
Click to expand...
Click to collapse
I was thinking to be this, I mean not to let the phone to go in soo low battery level.
thats weird, i always drain my battery to completely dead (3 red flashes) when im trying to recalibrate the battery and never ran into this issue. I have however had issues with low battery causing multiple WLOD reboots over and over.
Is this recommended to use for 2.3.3 as well? I will try n flash it now on J's CM7 017 STOCK.
fiscidtox said:
A few people saying their phones have been bricked (thinking they were, you can't brick an x10) and getting either a wlod, or three blinking red led flashes, because their battery level got so low and they were unable to offline charge it.
This fixes it and makes sure that cannot happen.
That is what it is for...
Click to expand...
Click to collapse
I see thanks for explaining.
sent from my Z orignal and modded 2.2 powered c64
flashed fine on Js CM7 017
dunno what's happening, i flashed again in trip 1.0.63, and again black screen after the boot screen. any idea? :E
is it also installed if i include it in a own package who only removes the existing charger in system/bin and then copys the new one or do i have to install the zip you uploaded that it would be installed right?
URGENT UPDATE: THIS KERNEL COULD BREAK YOUR ROM. It re-orders the mtd block order, this causes some custom scripts (e.g. in init.d) to break. Please don't use it for the moment unless the ROM is specifically updated to use it. You are free to test it, but be sure to backup first. Please report if the ROM works, and if possible check if there are any init.d/sh scripts with static mtdblock# mounting too (see post #13 for details).
Info For ROM Devs: To make your ROM compatible with this, any scripts you have that (re)mount partitions need to be updated. Please see post #13 for details.
If you use a ROM and want to use this kernel but it doesn't work, feel free to let me know and I'll see if I can make a patch to update it in case the original ROM builder doesn't for some reason.
----------------
Unlocked Bootloader only obviously, don't ask about locked bootloader support. I don't take any credit for this kernel. This is a mod of Championswimmer's kCernel v01 (the new 'test' ones, which are the best kernel yet IMO), I only started a new thread incase this kernel has issues whereas champs' original one doesn't (you can report them here). Additional credits go to DoomLorD (got some code from his old kernel for FXP, i.e. DoomKernel v05) and of course J and the FXP Team.
Hope you guys don't mind Championswimmer and DooMLorD, you are Gods :highfive:
This kernel is made for CosmicUI ROM but it should work with any FXP-CM7 based ROM. If you are not using CosmicUI, be aware of these two warnings:
1) /system only has 190MB. If your ROM installation is bigger, you can't use this. You can check the size of system with apps like Titanium Backup and Link2SD.
2) /cache only has 8MB (it was 4MB but this ran out of space when doing stuff in Recovery) and as such you will need a 'bind-mount script for download cache' which links /cache/download to /data so that large Play Store downloads will work. All good FXP-based ROM's should already have it since it's been built in to Cyanogenmod for a long time. Check init.d for "06mountdl" file to be sure (might be different name, on CosmicUI it's 05mountdl for example).
Tested ROM's working with this kernel (please report if it works but not in the list):
- CM7-FXP125 and later
- CosmicUI v0.6.x and later
Changelog
Code:
Based directly on championswimmer's kCernel "test-release-v01" (the new one after v05)
v03
- Fixed gradual pixel shift bug in Aroma installer
- Changed handset max-gain to 600 (was 1000). I noticed no difference in volume, this also fixes distortion for some X10's
- Unlocked more mhz (1152, 1190, 1228). Be careful with the higher ones, though CM7/CosmicUI will revert to safe clock if it crashes.
- Compiled a second version with a different "safe" partition map for huge ROM's (system @ 285MB, userdata @ 608MB, cache @ 35MB)
- Optimized smartass governor for better sleep and wake (thanks to DooMLorD and FXP)
- Optimized smartassv2 governor for better sleep and wake (thanks to DooMLorD and FXP)
- Default governor changed to smartassv2 (bit more battery friendly than SavagedZen)
v02
- "kcernel" and "cosmicmod" appended to version string
- custom mtdparts config ( system @ 190MB, userdata @ 730MB, cache @ 8mb )
- compiled with O4 optimization
- (over)clock speeds added (up to 1113) and voltages tweaked (thanks to DooMLorD)
- improved in-call volume (thanks to DooMLorD)
- Default governor set to SavagedZen
- Compiled with performance governor available (useful for stress testing max clock)
v01
- Based on kCernel "test" v01
- Changed bootlogo to CosmicUI one with kCernel for FXP branding
- Removed Bootmanager (I don't use it) and replaced with Doom's Touch Recovery (more stable backup/restore than FXP Recovery)
Installation
1) Make a Nandroid backup (if you want to keep your ROM)
2) Flash the kernel in latest FlashTool
3) Boot to recovery and format cache, data and system
4) Restore Nandroid backup
5) Reboot. Let me know if you have any issues.
6) In my experience I've had to perform a Factory Reset and reinstall the ROM when switching from another kernel.
If you are not already using kCernel, you might need to do a factory reset - I don't know.
Requests
If you want some other partition layout or have any other suggestion please let me know and I'll think about it.
Download
v3 MaxMTD (/data = 730MB version) - recommended for CosmicUI
http://www.mediafire.com/?d4fenoosqeeryyk
v3 SafeMTD (/data = 608MB, /system = 285MB) - recommended for large ROM's
http://www.mediafire.com/?tuu7b07kptb32pb
Source
http://www.mediafire.com/download.php?nunrktw96q58eof
Detailed Info (for devs)
I am surprised how easy it was to create a custom partition map and I have no idea why nobody else has done this before. All I had to do was edit the default build config and edit the CONFIG_CMDLINE value:
Code:
CONFIG_CMDLINE="console=ttyMSM0 mtdparts=msm_nand:[email protected](boot),190m(system),730m(userdata),8m(cache),4m(appslog)"
...the other changes were taken from DoomKernel v05 in a basic tree-diff method.
Special thanks for Championswimmer and his guides, tips, kernels, etc. You are the best
Could you make a version without the volume boost mod? Because the boost mod causes my earpiece to crackle, and there's no ULBL kernel that doesn't have the volume boost mod.
Thanks a bunch
Sent from my X10i using XDA
Prodigy said:
Could you make a version without the volume boost mod? Because the boost mod causes my earpiece to crackle, and there's no ULBL kernel that doesn't have the volume boost mod.
Thanks a bunch
Sent from my X10i using XDA
Click to expand...
Click to collapse
I'm not sure I know what you mean. The "in-call volume enhance" in the changelog was taken from DoomKernel v05, it's not there in kCernel. So it's something different and I don't know where to find that. The change raises the minimum gain value, it doesn't actually "boost" volume but stops it from going too low.
I don't get any crackle on mine, I just tested it. Sounds like (no pun intended) your earpiece is damaged....
...I would be willing to do it, but I don't know where to look. Find me a kernel with public sourcecode without this volume boost for me and I'll check it out.
CosmicDan said:
I'm not sure I know what you mean. The "in-call volume enhance" in the changelog was taken from DoomKernel v05, it's not there in kCernel. So it's something different and I don't know where to find that. The change raises the minimum gain value, it doesn't actually "boost" volume but stops it from going too low.
I don't get any crackle on mine, I just tested it. Sounds like (no pun intended) your earpiece is damaged....
...I would be willing to do it, but I don't know where to look. Find me a kernel with public sourcecode without this volume boost for me and I'll check it out.
Click to expand...
Click to collapse
Hi,
The earpiece crackling started back on wolf's v7b6 doomkernel version, and it wasn't just me, a couple of users reported that their earpiece started crackling as a result of using wolf's rom. IDK what caused it, either a problem with the ROM or doomkernel, but DK seemed fine on any other ROM other than wolf's.
Anyway yeah the crackling was almost non-existent with stock kernels, which by the way, did not conyain the mod. Sorry for confusing you, this mod was incorporated in kernels back when kernel development just started. Tkygmr mentions that he forgot to include the volume boost mod here. That kernel is here. Yeah its for locked bl, I'm not sure if thay helps. But the kernels before that, many did not have the volume boost mod.
Hope this helps, and thanks for your time much appreciated.
Sent from my X10i using XDA
Prodigy said:
Hi,
The earpiece crackling started back on wolf's v7b6 doomkernel version, and it wasn't just me, a couple of users reported that their earpiece started crackling as a result of using wolf's rom. IDK what caused it, either a problem with the ROM or doomkernel, but DK seemed fine on any other ROM other than wolf's.
Anyway yeah the crackling was almost non-existent with stock kernels, which by the way, did not conyain the mod. Sorry for confusing you, this mod was incorporated in kernels back when kernel development just started. Tkygmr mentions that he forgot to include the volume boost mod here. That kernel is here. Yeah its for locked bl, I'm not sure if thay helps. But the kernels before that, many did not have the volume boost mod.
Hope this helps, and thanks for your time much appreciated.
Sent from my X10i using XDA
Click to expand...
Click to collapse
Hmm maybe it was xLoud that damaged the earpiece, who knows.
I checked out that post and crawled their GitHub, unfortunately they didn't use GitHub version management until a few months after adding the call-volume hack he mentions. So I won't be able to find it in that source =\
Guess the only thing to do is PM a veteran x10 kernel dev, but I'm not sure who. They all seem to have moved on since. If there is any other custom kernel (even for stock-based or locked bootloader) that you can find without any volume hacks, do let me know.
Although with the minimum-gain tweak I merged into this (which, as a mentioned, was from DoomKernel and not in original kCernel), I could compare the code from that to the stock kernel sources. But that will take a bit of time and I might not be able to find it, depends how much these custom kernels have changed from stock.
EDIT: Hang on, I just found an older repo from that thread "FreeKernel" (before it was 3Kernel). Maybe I'll find it.
EDIT2: Found it. https://github.com/tkymgr/semc-qsd8x50/commit/6c3c316b69ce7177cd08c73895406c94fd72db32 Yeah, I could have guessed that but now I'm sure so it's OK haha. If you look at that page you can see the ".min_gain = -900" which is what I changed to -400, but the max is changed here too.
OK, so the stock kernel (I think) has max set to 600, in this kernel, kCernel and DK though it's on 1000. I will create a version with 600.
This kernel is made for CosmicUI ROM but it should work with any FXP-CM7 based ROM. If you are not using CosmicUI, be aware of these two warnings:
1) /system only has 190MB. If your ROM installation is bigger, you can't use this. You can check the size of system with apps like Titanium Backup and Link2SD.
2) /cache only has 8MB (it was 4MB but this ran out of space when doing stuff in Recovery) and as such you will need a 'bind-mount script for download cache' which links /cache/download to /data so that large Play Store downloads will work. All good FXP-based ROM's should already have it since it's been built in to Cyanogenmod for a long time. Check init.d for "06mountdl" file to be sure (might be different name, on CosmicUI it's 05mountdl for example).
Tested ROM's working with this kernel (please report if it works but not in the list):
- FXP125 CM7 (official)
- CosmicUI v0.5.x and later
Changelog
Code:
Based directly on championswimmer's kCernel "test-release-v01" (the new one after v05)
- "kcernel" and "cosmicmod" appended to version string
- custom mtdparts config ( system @ 190MB, userdata @ 730MB, cache @ 8mb )
- compiled with O4 optimization
- (over)clock speeds added (up to 1113) and voltages tweaked (thanks to DooMLorD)
- improved in-call volume (thanks to DooMLorD)
- Default governor set to SavagedZen
- Compiled with performance governor available (useful for stress testing max clock)
Installation
1) Make a Nandroid backup (if you want to keep your ROM)
2) Flash the kernel in latest FlashTool
3) Boot to recovery and format cache, data and system
4) Restore Nandroid backup
5) Reboot. Let me know if you have any issues.
If you are not already using kCernel, you might need to do a factory reset - I don't know.
Requests
If you want some other partition layout or have any other suggestion please let me know and I'll think about it.
Hello,
That was a Good Idea of yours. Since many roms are quite a bit larger than 190MB; for instance the one I am using is taking up almost 250MB of system, could you make a version with say 285MB for system and 35MB for cache which would still leave about 609MB for data. And 1190MHz as many X10's will handle it. :good:
Prodigy, give this a try. I tested it and noticed no difference at all? Very strange.... either the max-gain 1000 does nothing (or barely anything) or I did something wrong. Please try it though, if it works this will be included in any future releases.
http://www.mediafire.com/download.php?p8pxnlv658y6bdf
EDIT: For some reason when I flashed this, some of my UI fonts (clock, operator text, some others) turned into italic. Wtf? I actually like it but that makes no sense LOL. Last night during testing, winamp would also skip tracks twice when i only pressed it once (a clear data for the app fixed that). I think a factory reset might be needed if things go strange after flashing a kernel.
TAL333 said:
Hello,
That was a Good Idea of yours. Since many roms are quite a bit larger than 190MB; for instance the one I am using is taking up almost 250MB of system, could you make a version with say 285MB for system and 35MB for cache which would still leave about 609MB for data. And 1190MHz as many X10's will handle it. :good:
Click to expand...
Click to collapse
OK, the clock speeds I can do. Would you prefer a version of 260MB on system? There really is no need whatsoever to have space free on /system, unless you want to integrate some apps with TB for example. But even if you have 249MB on /system, it work work fine with 1MB free on a 250MB size. So having ~10MB free on system should be enough?
Is there a reason you want 35MB on cache? There is no need to have more than 8MB, with the CM7 bind-mount script the only thing that uses cache is CWM-Recovery for log files. I guess some custom scripts might use cache... is that why?
CosmicDan said:
Prodigy, give this a try. I tested it and noticed no difference at all? Very strange.... either the max-gain 1000 does nothing (or barely anything) or I did something wrong. Please try it though, if it works this will be included in any future releases.
http://www.mediafire.com/download.php?p8pxnlv658y6bdf
EDIT: For some reason when I flashed this, some of my UI fonts (clock, operator text, some others) turned into italic. Wtf? I actually like it but that makes no sense LOL. Last night during testing, winamp would also skip tracks twice when i only pressed it once (a clear data for the app fixed that). I think a factory reset might be needed if things go strange after flashing a kernel.
OK, the clock speeds I can do. Would you prefer a version of 260MB on system? There really is no need whatsoever to have space free on /system, unless you want to integrate some apps with TB for example. But even if you have 249MB on /system, it work work fine with 1MB free on a 250MB size. So having ~10MB free on system should be enough?
Is there a reason you want 35MB on cache? There is no need to have more than 8MB, with the CM7 bind-mount script the only thing that uses cache is CWM-Recovery for log files. I guess some custom scripts might use cache... is that why?
Click to expand...
Click to collapse
The reason I thought 285MB would be good was that I remember the last CM7 by Achotjan I used was a big ass rom, around 270 installed as I recall and I'm sure its bigger now. Just in case someone wants to try this with a big rom. The cache suggestion was just for extra margin as the most I've seen used on my phone was a little under 6MB. Back in the day, when I built a 550HP Poncho motor, I made sure the bottom end was good for at least 700HP. Gotta have margin.
TAL333 said:
The reason I thought 285MB would be good was that I remember the last CM7 by Achotjan I used was a big ass rom, around 270 installed as I recall and I'm sure its bigger now. Just in case someone wants to try this with a big rom. The cache suggestion was just for extra margin as the most I've seen used on my phone was a little under 6MB. Back in the day, when I built a 550HP Poncho motor, I made sure the bottom end was good for at least 700HP. Gotta have margin.
Click to expand...
Click to collapse
OK, good call. I don't know why 35MB on cache will be needed with the download cache redirected to /data, but OK I'll do one with 285MB on system and 35MB on cache and that'll be marked as the "safest" mod. Then I might make one in-between if asks for it. But there will be a limit to how many I can maintain
Cheers mate thanks heaps for your effort, that was really quick!
Sent from my X10i using Tapatalk 2
Prodigy said:
Cheers mate thanks heaps for your effort, that was really quick!
Sent from my X10i using Tapatalk 2
Click to expand...
Click to collapse
No worries. Let me know if it helps though? Next version will keep it, as I already mentioned that my test showed that it was not quieter at all putting the gain back to 600.
Info for ROM makers
Code like this in any sh scripts (e.g. init.d, hw_config.sh, etc) will not work with this kernel...
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock2 /system;
...because it assumes a standard MTD map. This kernel has however modified the order. We could just change it to mtdblock1, but then that ROM would only work with this kernel. So, we use a function to parse the /dev/mtd file to find the correct mtd device to be mounted.
Add this helper function to the top of your script(s):
Code:
get_mtd() {
local DEV="$(grep "\"$1\"" /proc/mtd | awk -F: '{print $1}')"
local PATH=/dev/mtdblock
DEV="${DEV##mtd}"
echo "${DEV:+$PATH$DEV}"
}
...then later, when you need to assign the right mtdblock, do this...
Code:
mtd_system="$(get_mtd system)"
...changing 'system' to whatever you want to find. This will populate the variable with /dev/mtdblock1 in kCernel-CosmicMod, or in other kernels with /dev/mtdblock2. All good.
So then after that you can use it in a line like this...
Code:
mount -o rw,remount -t yaffs2 $mtd_system /system;
...and that's pretty much it.
...I realize that I could correct the kernel to use the "original" mtd map order, but this is a good habit for a developer to get in to. A developer should not tie themselves down with device-specific habits. Besides, my changes to the mtd order make more sense and other Android devices that I know of seem to follow this same order.
Hi,
First thanks for this Kernel, i've been looking for a partition table like this forever, and now can take it with the overclock as well, this is awesome, and based on your last comment a just figured out out most scripts doesn't seem to work on my init.d
Well as i'm not that good with Linux scripts, (to not say very bad in this area of expertise), can you help me to translate to a working script the script below:
mount -o noatime,nodiratime,barrior=1 -t ext3 /dev/block/mmcblk0p2 /sd-ext;
I understand that this also should be placed:
chown 1000:1000 /sd-ext;
chmod 771 /sd-ext;
#swap mount:
swapon /dev/block/mmcblk0p3;
My mSD card was formatted using the recovery built in and the mapping is correct as in this way the script is already working but i have to run them from inside script manager app and not from init.d, from init so far nothing seems to work, or it's just me that can't figure how to do it.
TheRuan said:
Hi,
First thanks for this Kernel, i've been looking for a partition table like this forever, and now can take it with the overclock as well, this is awesome, and based on your last comment a just figured out out most scripts doesn't seem to work on my init.d
Well as i'm not that good with Linux scripts, (to not say very bad in this area of expertise), can you help me to translate to a working script the script below:
mount -o noatime,nodiratime,barrior=1 -t ext3 /dev/block/mmcblk0p2 /sd-ext;
I understand that this also should be placed:
chown 1000:1000 /sd-ext;
chmod 771 /sd-ext;
#swap mount:
swapon /dev/block/mmcblk0p3;
My mSD card was formatted using the recovery built in and the mapping is correct as in this way the script is already working but i have to run them from inside script manager app and not from init.d, from init so far nothing seems to work, or it's just me that can't figure how to do it.
Click to expand...
Click to collapse
You are saying this script works with other kernels but not with this one? I don't understand why, the mmc blocks are untouched - only the MTD blocks (internal partitions) have a changed order in this kernel.
Try it with original kCernel, I don't know if it has swap support enabled.
CosmicDan said:
You are saying this script works with other kernels but not with this one? I don't understand why, the mmc blocks are untouched - only the MTD blocks (internal partitions) have a changed order in this kernel.
Try it with original kCernel, I don't know if it has swap support enabled.
Click to expand...
Click to collapse
No no, what i'm saying is that this doesn't work with the Kcernel, i couldn't try your modified one since i've been working a lot this week and didn't have the time to format the phone again, the weird thing is that as far as i know the fxp has a default script in which it should always search the sd-ext partition and mount it, not sure about the swap partition, but pretty sure it would mount it too, but so far everything indicates that nothing inside the init.d directory is running, since i've tried many variations i got from the web and none worked.
I'm using the last 125 FXP and the Kcernel test1.
Will try tonight to format the phone in the work, but can't promise anything since i've almost no tools here and also i'm very sick, shouldn't be working neither, hehehe, but I'm workaholic.
TheRuan said:
No no, what i'm saying is that this doesn't work with the Kcernel
Click to expand...
Click to collapse
Well you should probably ask in original kCernel thread or the thread for your ROM... what is the ROM you are using? I could take a look when I have time if you can't give me a logcat.
TheRuan said:
the weird thing is that as far as i know the fxp has a default script in which it should always search the sd-ext partition and mount it
Click to expand...
Click to collapse
No, it doesn't have any function to mount sd-ext. You have to use a third-party method to get sd-ext access such as A2SD scripts (can be buggy) or the Link2SD app (recommended, most stable and more powerful).
TheRuan said:
but so far everything indicates that nothing inside the init.d directory is running, since i've tried many variations i got from the web and none worked.
I'm using the last 125 FXP and the Kcernel test1.
Click to expand...
Click to collapse
Hmm all I can suggest is to reflash kernel with latest flashtool, factory reset, and reinstall the ROM. If no init.d scripts are running it must be a bad kernel flash, which happens fairly often with the X10.
I reflashed now with your kernel and FXP, and no, init.D isn't working, I think this error is on Kcernel or on last builds from FXP kernel, that, being the source for kcernel could be the reason for the errors, and also I'm pretty sure that no start script are running.
Also for some reason on your kernel i can't undervolt the phone anymore, this was available using Kcernel.
tried to flash original fxp 124 kernel, and i get wlods all the time, it wont boot into recovery, anyone has ideas how to fix?? i saw something about flashing the fxp 124 rom and kernel directly from flashtool but i cant find it cause i forgot the threads name, please help as quickly as possible, cause i was thinking of flashing that, i could boot into recovery and restore my fxp 125 rom that i had now..
TheRuan said:
I reflashed now with your kernel and FXP, and no, init.D isn't working, I think this error is on Kcernel or on last builds from FXP kernel, that, being the source for kcernel could be the reason for the errors, and also I'm pretty sure that no start script are running.
Also for some reason on your kernel i can't undervolt the phone anymore, this was available using Kcernel.
Click to expand...
Click to collapse
Well I don't know what to say, init.d executes fine for FXP kernel, kCernel original and this kCernel mod. I find it hard to believe that init.d isn't working at all, because then sysctl wouldn't even be running. It's more likely that it's crashing out because of something you added or changed. You'll need to logcat it.
And sorry, I was wrong - the 05mountsd script handles sd-ext mounting. But that never did anything in my experience, it depends on your configuration. Link2SD works 100% for me and it creates an init.d script when you first run it and select your sd-ext partition type.
I noticed the undervolt thing and it's the only thing holding me off releasing the next version, I think I need to enable that sysfs interface somewhere. Changing clock voltages is done at /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels - same as every other custom kernel for x10 that has it.
[email protected] said:
tried to flash original fxp 124 kernel, and i get wlods all the time, it wont boot into recovery, anyone has ideas how to fix?? i saw something about flashing the fxp 124 rom and kernel directly from flashtool but i cant find it cause i forgot the threads name, please help as quickly as possible, cause i was thinking of flashing that, i could boot into recovery and restore my fxp 125 rom that i had now..
Click to expand...
Click to collapse
Try flashing stock gingerbread FTF, and please take those questions to the Questions forum - this has nothing to do with this kernel.
Hi guy!
After some days without any answer, i have worked on Kitkat.
It seems that it boots on my tab.... :angel:
Wait the fist release on 2.6.29 kernel
And 2.6.37 for A70S2 (HC and FROYO)
:good::fingers-crossed::good:
Bizcuite
Amazing Biz... you are my hero :good:
airwolf1544 said:
Amazing Biz... you are my hero :good:
Click to expand...
Click to collapse
I will to become all red stop stop please lol
Well it rests a lots of works!!!!
I have just boot logo.
I will try to boot it with 2.6.29 kernel, but it must be ok and have the same result (only BT and upnp should (/could) not worked).
For 4 days i will be at home and works when i have times to work on it.
Bizcuite
bizcuite said:
i will become all red stop stop please lol
well it rests a lots of works!!!!
I have just boot logo.
I will try to boot it with 2.6.29 kernel, but it must be ok and have the same result (only bt and upnp should (/could) not worked).
For 4 days i will be at home and works when i have times to work on it.
Bizcuite
Click to expand...
Click to collapse
ready to test sir!
Wow, just wow. Amazing!
Sharpen you swords (charge your batteries) and get ready for fiiiiiiight (and get ready for teeeeeeeeest)
bizcuite said:
I will to become all red stop stop please lol
Well it rests a lots of works!!!!
I have just boot logo.
I will try to boot it with 2.6.29 kernel, but it must be ok and have the same result (only BT and upnp should (/could) not worked).
For 4 days i will be at home and works when i have times to work on it.
Bizcuite
Click to expand...
Click to collapse
I know its much work.. but you try it..
airwolf1544 said:
I know its much work.. but you try it..
Click to expand...
Click to collapse
Oooooh yes its lots of work. And patience to wait the compilation finish it...
I recompile all atm. I had forgotten to include all device.mk file maybe I will have trebuchet at first start (yes I compile cm11 ).
Gpu driver and libs seems to work... I have the boot logo (and a crash system. Bootloop)
First screenshot is near
Bizcuite
Sent from my GT-N7100 using xda app-developers app
Just a question: Are you gonna make this use ART, cause that's what I guess u will do and that's something that I guess will make the tab faster, but as far as I understand as of now ART makes a lot of apps not work (at least for now till they are updated)?
Ranomez said:
Just a question: Are you gonna make this use ART, cause that's what I guess u will do and that's something that I guess will make the tab faster, but as far as I understand as of now ART makes a lot of apps not work (at least for now till they are updated)?
Click to expand...
Click to collapse
You have the choice. you can choose in dev option dalvik or art.
Or chane an option in buid.prop, set libdvm to libart or inverse.
I have a boot failure at start, i try to fix it.
Bizcuite
Welcome Kitkat
Bizcuite
bizcuite said:
Welcome Kitkat
Bizcuite
Click to expand...
Click to collapse
I would like to try also kitkat on my 101, gen. 8 :good:
greeting
mika67 said:
I would like to try also kitkat on my 101, gen. 8 :good:
greeting
Click to expand...
Click to collapse
It will be possible with 2.6.29 kernel i think.
ATM on A70S2 - Gen9 kernel 2.6.35-7:
-TS working
-3D working
-Soft button activated on my tab (to see on others tabs)
Not working:
-sound (don't know why atm)
-BT (just have to configure init.rc)
-Wifi (recompile all with Wlan option, must work after)
-looooots of thing that i have not tested.
Another thing, Kitkat must have system in a different partition, you will have to install 3 image files in the sdcard (root of system, system and data).
I think that i will use directly the internal sdcard partition and write partitions directly on the sdcard (like a real partition, not an image -> better perf ). BUT a wipe of the sdcard is necessary (one time).
Bizcuite
bizcuite said:
It will be possible with 2.6.29 kernel i think.
ATM on A70S2 - Gen9 kernel 2.6.35-7:
-TS working
-3D working
-Soft button activated on my tab (to see on others tabs)
Not working:
-sound (don't know why atm)
-BT (just have to configure init.rc)
-Wifi (recompile all with Wlan option, must work after)
-looooots of thing that i have not tested.
Another thing, Kitkat must have system in a different partition, you will have to install 3 image files in the sdcard (root of system, system and data).
I think that i will use directly the internal sdcard partition and write partitions directly on the sdcard (like a real partition, not an image -> better perf ). BUT a wipe of the sdcard is necessary (one time).
Bizcuite
Click to expand...
Click to collapse
Send me something to test - I am getting exited!
bizcuite said:
It will be possible with 2.6.29 kernel i think.
Another thing, Kitkat must have system in a different partition, you will have to install 3 image files in the sdcard (root of system, system and data).
I think that i will use directly the internal sdcard partition and write partitions directly on the sdcard (like a real partition, not an image -> better perf ). BUT a wipe of the sdcard is necessary (one time).
Bizcuite
Click to expand...
Click to collapse
Hi biz,
I think that with the first test would be not so bad if the installation only with
3 image file would take place (simpler installation).
If the new system has then beta status could one then the partition
on the internal SD card drove through .
Are already curious on the new system
greeting
mika67 said:
Hi biz,
I think that with the first test would be not so bad if the installation only with
3 image file would take place (simpler installation).
If the new system has then beta status could one then the partition
on the internal SD card drove through .
Are already curious on the new system
greeting
Click to expand...
Click to collapse
Partitions directmy wrote on the internal sdcard will be option at start.
Now. The main PB is the wifi hal. Because wpa supplicant v0.6 and wl1271 driver has been deleted from the code source of Android. I try to compile it for 2.6.35 (more easy because drivers are updated).
Let me see if there is a way to have wifi for 2.6.29 kernel.
Bizcuite
Sent from my GT-N7100 using xda app-developers app
ready to test for 101IT when you have something
Will the touchscreen be as difficult to make work as the last kernel you worked on these last few weeks ?
Cheers!
4qu4rius said:
ready to test for 101IT when you have something
Will the touchscreen be as difficult to make work as the last kernel you worked on these last few weeks ?
Cheers!
Click to expand...
Click to collapse
I don't know
But it will be more easy to fix than with CM9 (first experience in android compilation for remember )
FYI:
I had few time to try the new image that i have compiled.
It's compiled with CM options (wasn't the case in CM9). Bootlogo is CM, themes doesn't crashed, but it lakes a little thing to fix.
I will try to fix wifi this week end if i have more times to dev.
I progress about it, ATM i try with 2.6.35 (only for A70S2), and i hope that it will worked with 2.6.29 (for all others tabs), mac80211 module is included into this kernel, but maybe the driver cannot be compatible
Bizcuite
bizcuite said:
I don't know
But it will be more easy to fix than with CM9 (first experience in android compilation for remember )
FYI:
I had few time to try the new image that i have compiled.
It's compiled with CM options (wasn't the case in CM9). Bootlogo is CM, themes doesn't crashed, but it lakes a little thing to fix.
I will try to fix wifi this week end if i have more times to dev.
I progress about it, ATM i try with 2.6.35 (only for A70S2), and i hope that it will worked with 2.6.29 (for all others tabs), mac80211 module is included into this kernel, but maybe the driver cannot be compatible
Bizcuite
Click to expand...
Click to collapse
Biz
Any progress on this?
Thanks
Mikerla said:
Biz
Any progress on this?
Thanks
Click to expand...
Click to collapse
Yes and no, i work on it when i have times.
I try to find any ways to have a working wifi. I use CM11 wifi drivers but i cannot use it correctly (myukernel or CM11 is not configured properly).
When i have a working wifi i will upload an alpha release.
For screen and navigation button, i think that there will have no pb with it. The managment about this is very different.
To fix:
-Wifi
-external/internal sdcard not seen
-OMX codecs
-Sound HAL
-BT
-ALL
Bizcuite
[kernel][v3.5] leanKernel: minimalistic kernel (1/28/16)
leanKernel is not for everyone.
My philosophy is to keep the kernel footprint as small as possible by trimming as much fat as possible, and at the same time keeping it stable, power efficient, and fast. leanKernel is designed to be a drop in replacement for stock kernel, and so it tries not to deviate too far from stock.
You will find that it's lacking some of the bells and whistles of other custom kernels, so if you like features you came to the wrong thread.
Here's a longer post on what leanKernel is about.
Also folks, please read the FAQ before asking questions.
INSTRUCTIONS
If you like to stay as close to stock as possible: 1) Download and flash the normal leanKernel build here (find the latest zip file) in recovery. 2) Reboot and enjoy better performance and battery life (hopefully). That's it! There's no need to flash stock kernel first, or to wipe caches.
If you like to customize, read through the feature list below, the FAQ (post #2), the changelogs, and optionally the entire thread. Then you'll know what to do.
DOWNLOAD (flash in recovery)
v1.x is for Android 5.0, and v2.x is for Android 5.1
main download
mirror (may need to refresh browser to see latest)
PREREQUISITE
Unlocked bootloader, custom recovery installed
Push bullet channel: imoseyon
FEATURES
custom voltage control - use your favorite app
updated to latest 3.10 Linux
interactiveX - screen_off_maxfreq support (default 2.2Ghz)
sw crypto drivers updated (to use arm NEON instructions) for better encryption/decryption performance. Sequential 180MB/s reads, 60MB/s writes (using dd)
latest Linaro gcc 4.9 toolchain (optimized for a15 - thanks to Christopher83)
fat trimmed and various performance tweaks
f2fs support (updated to latest source from Samsung)
force encryption turned off (changed to encryptable)
overclocked to 2.9ghz (experimental - available as a separate build for now)
underclocked to 223mhz (experimental - available as a separate build for now)
Async Fsync
init.d support
cpu-boost control - enable/disable via lkconfig
lkconfig script for customizing leankernel (open terminal app, become superuser, then type "lkconfig" without quotes)
patched mpdecision to prevent changing min/max freq provided as flashable zip (in util directory)
color control (thanks to @savoca)
charging led support
a lot of unnecessary stuff removed from stock kernel
some components updated to Linux 3.18
random generation optimization including e/frandom support
pc/usb charging with boosted current ~300-400mA
some selinux fixes, selinux is enforced by default - staying true to stock (you can easily disable using lkconfig)
SLUB allocator updated to Linux 3.18
wake gesture control from flar2, modified for leankernel (also disabled in-call)
vibe strength control
much of the code is up to date with latest from CodeAurora
(mostly for devs) /sys/module/selinux/parameters/force_audit sysfs node to audit all/hidden selinux denies.
power aware cpu scheduling
faux sound enable/disable by sysfs (and lkconfig)
wakelock control (smb135x, wlan_rx, msm_hsic and sensor_ind)
leanKernel core control script
user option to prevent mpdecision/msm_thermal from changing min/max frequencies: frequency mitigation preventer
supports kexec for multirom
LKCONFIG
You can use lkconfig script to make custom changes to leanKernel (along with popular apps like Kernel Tweaker and Trickstermod). To run lkconfig, open terminal app, "su" (without quotes) to become superuser, enter, and then type "lkconfig" without quotes, then enter.
Code:
[email protected]:/ $ su
[email protected]:/ # lk
leanKernel configurator
---
0) display current settings
1) cpu frequency control
2) wake gesture control
3) wakelock control
4) charging led
5) rgb/picture control (advanced)
6) rgb/picture control (simple)
7) vibe strength
8) power saving mode for cpu scheduler
9) faux sound control
10) selinux mode
11) min/max freq change prevention
21) check top 10 wake locks (ie. wakeup sources)
please enter a number (or press enter to exit):
CHANGELOG
https://github.com/imoseyon/leanKernel-shamu/wiki/Marshmallow-ChangeLog
Thanks to @guitarshredder87, @Wera750, @akellar, and @grisha1 for testing test builds!
XDA:DevDB Information
Leankernel: Minimalistic Kernel, Kernel for the Nexus 6
Contributors
Imoseyon
Source Code: https://github.com/imoseyon/leanKernel-shamu
Kernel Special Features:
Version Information
Status: Stable
Created 2014-11-26
Last Updated 2016-01-31
FAQ
I'm having trouble waking the phone sometimes. Help!
We haven't really figured out exactly what's causing it - but there seems to be evidence that it's not limited just to leanKernel. One thing to try: if your ROM has a feature that prevents accidental wakeups, disable it!
I can't seem to get min and max freq to stick! What are these mpdecision zip files in the util directory?
* Read this post: http://forum.xda-developers.com/showpost.php?p=58135730&postcount=1474
* Short version: This is actually by design of mpdecision. If you want this behavior to change, I recommend that you 1) flash latest stable leankernel, 2) flash the custom no-freq mpdecision, and then 3) disable cpu-boost via lkconfig. Do not disable mpdecision if you go this route. Also, if you flash ROM, you must re-flash custom mpdecision. To go back to normal, flash the stock mpdecision file.. Launch lkconfig, choose core control, and choose one of the options in core control.
Will flashing leankernel decrypt my phone storage?
If you're already encrypted, then it will stay encrypted after flashing kernel, *until* you format data. Once you format you will stay decrypted until you decide to encrypt again (see below). If you're already decrypted, leanKernel will not force encrypt automatically.
What do I do to encrypt again?
There are several ways to do this. One way (easiest for me at least) is to adb in (or in terminal emulator):
Code:
[email protected]:/ # start encrypt
You will see the phone hot boot and once it comes up you will be encrypted again. Keep in mind that if you want to decrypt again you'll have to wipe.
How do I check the PVS BIN of my cpu?
Code:
[email protected]:/ # cat /proc/cpu/msm_acpu_pvs
The number you get should range between 0 and 15 (inclusive). If you ended up with 15 congratulations. If you ended up with 0, go get it exchanged! Stock frequency/voltage table: http://pastebin.com/ZyGA9Tec
Which kernel control app do you recommend?
When v1.0 gets released it should come with "lkconfig" for tweaking some of the options. Otherwise, I tried Trickster and KernelTweaker, and they both seem to work ok.
What are ondemandX and interactiveX?
ondemandX and interactiveX are very very close to "stock" ondemand and interactive governors, respectively. The only difference is screen_off_maxfreq sysfs support. This means that it gives you the ability to limit phone's max frequency when screen is off. This feature could be effective in reducing battery usage, especially if you have a misbehaving app (or two) that consume cpu cycles while screen is off. The default value is 2265600 - if you change the value to your top speed you're effectively disabling the feature and restoring stock behavior completely. You can use an app like Trickster or Kernel Tweaker to modify screen_off_maxfreq.
HELP! I messed up with lkconfig - how do I go back?
Do not fret. Flash lkconfig_cleaner.zip from the "util" directory.
(If you want to do this manually), reboot the phone into recovery, mount /data, and delete everything in /data/data/leankernel. Once things are back to normal, re-run lkconfig to re-do your settings.
What is cpu-boost?
Read this post: http://forum.xda-developers.com/showpost.php?p=57215289&postcount=535
What is the best RGB setting?
http://forum.xda-developers.com/showpost.php?p=57265483&postcount=620 (old)
http://forum.xda-developers.com/showpost.php?p=59092146&postcount=3017 (new)
What is power aware scheduling?
Read this post: http://forum.xda-developers.com/showpost.php?p=58313978&postcount=1651
I missed your kernel when I switched to N5. Glad to have you here
hmm.. a kernel. since its the first one posted here, im trying it out
Hell yeah. Ready to flash
Sent from my AOSP on Shamu using XDA Free mobile app
If I flash this it will decrypt right cool
digweed4me said:
If I flash this it will decrypt right cool
Click to expand...
Click to collapse
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Imoseyon said:
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Click to expand...
Click to collapse
What app should we use to control? I remember you used to have your app right
holy **** Imoseyon. you made my Thunderbolt usable way back when. so glad to see you developing for the N6 now
digweed4me said:
What app should we use to control? I remember you used to have your app right
Click to expand...
Click to collapse
Flashed it and yes decrypted thanks a lot
IMO!! Good to see ya again man. Can't wait to run your work again.
Appreciate it!
digweed4me said:
What app should we use to control? I remember you used to have your app right
Click to expand...
Click to collapse
You mean lkconfig? Yeah that's coming later (along with a whole lot more).. If you're talking about f2fs, you'd want to use custom recovery but TWRP for shamu doesn't support f2fs yet - i had to do everything manually.
Imoseyon said:
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Click to expand...
Click to collapse
i am still encrypted, and did not decrypt after flashing. so, all worked as it should.
Can we flash on stock ROM or is a custom ROM required?
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
nycdiplomat said:
Can we flash on stock ROM or is a custom ROM required?
Click to expand...
Click to collapse
I'm on a stock ROM.
pathtologos said:
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
Click to expand...
Click to collapse
wipe before flashing, youll be decrypted. if you dont wipe, you stay encrpted.
pathtologos said:
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
Click to expand...
Click to collapse
AFAIK, there's no way to decrypt without having to wipe unfortunately. Going the other way (unencrypted to encrypted) is super easy though, and no data loss.
nycdiplomat said:
Can we flash on stock ROM or is a custom ROM required?
Click to expand...
Click to collapse
im on rastapop, an aosp based custom rom.
simms22 said:
wipe before flashing, youll be decrypted. if you dont wipe, you stay encrpted.
Click to expand...
Click to collapse
Thanks for your quick response. Wipe what tho? Cache, dalvik, and what else? Hope you don't mean all my data.
You don't buy a Mustang for the gas mileage.