Related
NOTE: This will probably no longer be maintained. It was the result of me playing around with the kernel from scratch instead of trying to understand what changes others have made and why they had made them! Now I'm a little more confident I'll probably be using DooMLoRD's kernel as a base for any changes I make to the Ray: [Kernel] [Ray] DooMLoRD's Kernel for Ray
hartej said:
Been playing around with Kernel development and created an overclocked kernel for the 4.0.2.A.0 stock Rom.
There's nothing too speciall in it at the moment, but lets you overclock the Ray to 1.9Ghz using the source released by SE and the modified CPU steps that IF2 posted here: http://forum.xda-developers.com/showthread.php?t=1165355
There's no custom bootloader/Clockwork mod and no additional governers (at the moment) although I may add these in future as I learn more.
It seems to work well enough, and everything seems to be working as standard. I experience random lock-ups at 1.9 and occasionally 1.8Ghz, especially when it goes into/out of sleep when the screen turns off. Lower frequencies seem stable though.
This is released as-is, I'm using it myself but I can't be held responsible for any instabilities or failures you might experience. Just thought it might be of use to some people.
The new .img file can be downloaded from here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-V0.13-2011-12-18.img
Alternatively, I've posted a version of the DooMLoRD kernel for the Ray which has a ton more features. This can be found here: http://forum.xda-developers.com/showthread.php?t=1400121
To install just use fastboot in the usual way. To return to stock, extract kernel.sin from the official update image using WinZip/WinRar etc and flash using fastboot again.
Click to expand...
Click to collapse
I'll post any updates here from now on.
Changelog:
19/12/2011 - V0.13 - As people have quite rightly pointed out, V0.12 boots at 1.8GHz as default, which causes multiple reboots. I hadn't noticed this as I had SetCPU reduce it to 1GHz as soon as the system started. The only change to this version is to have it boot at 1GHz as default, it's up to the user to increase it themselves.
28/10/2011 - V0.12 - Added Clockwork Recovery v5.0.2.6 (Spam Vol[-] when phone starts up, use volume keys to navigate, home to select, back for back)
28/10/2011 - V0.11 - Started playing with the Ramdisk - as a first start I've made it rootable. Things like "Adb remount" work now.
26/10/2011 - V0.1 - intial release
Current version:
~~~~~~~~~
V0.13 can be downloaded here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-V0.13-2011-12-18.img
Older versions:
~~~~~~~~~
V0.12 can be downloaded here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-OverclockV0.12.img
V0.11 can be downloaded here: http://dl.dropbox.com/u/17615284/4.0.2.A.0-OverclockV0.11.img
get new kernel~nice
tested it works really cool
thanks!!!!!
Like it...
thanks
Glad to see the "Recovery option" is available.
I tested v0.11+OC 1.3Ghz -> no problem.
However, v0.12+OC 1.2 or 1.3 -> keep on rebooting.
v0.12+no OC (use default 1Ghz) -> no problem.
im on 012+oc 1.5mhz, still working well....
great works!
great work, thx for your efforts
the included cwm is it dooms latest?
http://forum.xda-developers.com/showthread.php?t=1172885
"[v12 onwards] modified recovery to support /sd-ext backup/restore (remember /sd-ext has to be the 2nd partition on ur sdcard [mmcblk0p2] for this to work)"
if it is not I think that would be usefull with ext support, now you can use a2sd for xperia, bu it is not possible to make nand backup bcs cwm dit not recognize ext partition.
can you add donation possibility, would like to support your work
Thank you a thousand times! :d
2 questions though:
- I have to reroot my phone after this?
- Do I have to rename the download to boot.img?
Thanks 4 sharing!!!
-No
-No
;-)
funiewski said:
great work, thx for your efforts
the included cwm is it dooms latest?
http://forum.xda-developers.com/showthread.php?t=1172885
"[v12 onwards] modified recovery to support /sd-ext backup/restore (remember /sd-ext has to be the 2nd partition on ur sdcard [mmcblk0p2] for this to work)"
if it is not I think that would be usefull with ext support, now you can use a2sd for xperia, bu it is not possible to make nand backup bcs cwm dit not recognize ext partition.
can you add donation possibility, would like to support your work
Click to expand...
Click to collapse
It's not the latest I'm afraid so I doubt the ext backup would work. I'll see what I can do for the next release when I get a chance.
At some point I was also going to see if it's possible to change the MTD partition structure to give more space to /data. At the moment adb reports:
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock0 400.0M 241.8M 158.2M 60% /system
/dev/block/mtdblock3 420.0M 270.3M 149.7M 64% /data
This means that there's over 150MB of 'free' space in system that could be given over to the data partition instead of being effectively lost. May or may not be possible - don't know enough about the system yet.
As for donations - this is as much a learning experience for me than anything else, and at the moment I'm mostly applying things that others have done instead of making any breakthroughs myself so I wouldn't feel happy taking donations, but the thought is appreciated.
Bazonga said:
Thank you a thousand times! :d
2 questions though:
- I have to reroot my phone after this?
- Do I have to rename the download to boot.img?
Click to expand...
Click to collapse
You'll have to put it into fastboot mode by powering on and holding Vol[+], then flash using "Fastboot flash boot <filename>" - you can rename it or not, provided the <filename> part matches. You shouldnt have to reroot.
kkline38 said:
Glad to see the "Recovery option" is available.
I tested v0.11+OC 1.3Ghz -> no problem.
However, v0.12+OC 1.2 or 1.3 -> keep on rebooting.
v0.12+no OC (use default 1Ghz) -> no problem.
Click to expand...
Click to collapse
That's strange, i've got it overclocked to 1.5Ghz and it seems to be really stable. As far as I'm aware the only change I made between the two was adding clockwork - there shouldn't be any other difference... I'll look into it.
Double reboot only 10 min after flashing and without changing frequencies..
Bazonga said:
Double reboot only 10 min after flashing and without changing frequencies..
Click to expand...
Click to collapse
Without having your device in front of me I don't know how much I can do to help, but I'll look into it once I have the time. Unfortunately I have other things on the go at the moment so it probably won't be till next week.
hartej said:
Without having your device in front of me I don't know how much I can do to help, but I'll look into it once I have the time. Unfortunately I have other things on the go at the moment so it probably won't be till next week.
Click to expand...
Click to collapse
Thanks, I flashed the stock kernel back for now, Ray kept rebooting on me for no reason..
hartej said:
That's strange, i've got it overclocked to 1.5Ghz and it seems to be really stable. As far as I'm aware the only change I made between the two was adding clockwork - there shouldn't be any other difference... I'll look into it.
Click to expand...
Click to collapse
Do you use SetCPU ? (I use SetCPU 2.2.4)
What's the parameters did you use to OC 1.5Ghz ?
"ondemand" ? "powersave" ? "performance" ? or ?
Currently I changed back to V0.11. (it's stable for me)
kkline38 said:
Do you use SetCPU ? (I use SetCPU 2.2.4)
What's the parameters did you use to OC 1.5Ghz ?
"ondemand" ? "powersave" ? "performance" ? or ?
Currently I changed back to V0.11. (it's stable for me)
Click to expand...
Click to collapse
Yup, think I'm on 2.14 though - I doubt this would make a difference but its possible I guess.
I leave everything as-is (So ondemand governor) but reduce the min to 122MHz and increase max to 1.5GHz. Still confused as to why the previous version is more stable for some, but I'll have a look at the differences.
hi! thank you for this kernel.
now question. can you include USB_otg into your kernel? it's realised in DooMLorD kernel for arc (link). is it possible to do this feature for our device?
P.S. sorry for my english, i'm from Russia
vdsirotkin said:
hi! thank you for this kernel.
now question. can you include USB_otg into your kernel? it's realised in DooMLorD kernel for arc (link). is it possible to do this feature for our device?
P.S. sorry for my english, i'm from Russia
Click to expand...
Click to collapse
Don't worry about your English - my Russian is much worse!
I'm developing this for my own uses (selfish I know) while I work out how it's all put together. I'll add OTG to my list although I can't promise anything.
thanks
take it
Tried 0.12 and was really happy there´s clockwork for my ray But I have to go back to stock kernel. v0.12 randomly freezes and then reboots (btw. ray gets hot untill reboot).
I didn´t overclock and use rooted 4.0.2.A.0.42.
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.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, we will laugh at you, all, at the same time.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATIONS
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
CHECK KNOWN ISSUES HERE
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
Google Apps: Link 1 Link 2
TWRP Recovery: https://www.androidfilehost.com/?fid=24052804347766143
CHANGELOG
Download
GAPPS for CM-12.1
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
source
https://github.com/cyanogenmod/android_device_htc_enrc2b
https://github.com/cyanogenmod/android_kernel_htc_enrc2b
https://github.com/cyanogenmod/android_device_htc_tegra3-common
Contributors
Lloir, Thomy
Source Code: http://github.com/cyanogenmod
Working Not Working: Eventually Change log
This will be edited and updated as I make progress
Working 7/7/15:
Audio
Touch
Display
Vibrator
WIFI
Bluetooth
DATA/GSM/RIL (except for sim pin)
BATTERY
ROTATION
GPS
Not Working 7/7/14:
Device encryption
CHANGELOG
?/05/16 (well it's finally coming out) in 2017
05/05/17 -- FINAL
cgroups fixed
RIL Fixes (GSM/DATA)
3G Mtu changed, should see an increase in speed.
Security patches, fixes loads of security issues
X+ now shows up instead of the ONE (MTP) (pulled from AndyLavr git)
SElinux fix up (pulled from AndyLavr git)
CM main source update
and a load of other stuff.
------------------------------------------------------
27/11/15 ------ MD5 b9ae858d0a881ae6a24958caa067360e
Sdcard symlink is fixed? it's storage/sdcard0 (for me anyway test it for me)
Added more sepolicies for the ril :silly:
Updated main cm source
FULL WIPE
------------------------------------------------------
5/11/15
CM update which includes Security updates from Google https://groups.google.com/forum/#!topic/android-security-updates/GwZn7sixask
Reverted the changes I made to sdcard, which means /sdcard is now able to be accessed again.
------------------------------------------------------
25/10/15
More selinux denial's fixed thanks to @el-Loko logs
Let me know if the sim card issue still arises.
I've made changes to MTP and the /sdcard /storage area's
------------------------------------------------------
24/10/15
Sepolicies updated, hopfully the no sim issue will be fixed now. https://github.com/Lloir/android_device_htc_enrc2b-2/commits/cm-12.1
No more selinux denial's that I could find. All eliminated.
Source update
Kernel update's thanks to @ntemis https://github.com/Lloir/htc_kernel_oxp/commits/cm-12.1
Sim toolkit now show's and works
GPS lock is oh oh so much quicker
If google maps has a hissy fit let it die and reload it.
------------------------------------------------------
28/8/15
Updated source (Which includes the chrome fix)
------------------------------------------------------
26/8/15
Updated source
Revert my bluetooth breakage change, so BT works as it should.
------------------------------------------------------
7/8/15
http://review.cyanogenmod.org/#/c/93232/
http://review.cyanogenmod.org/#/c/105285/ + http://review.cyanogenmod.org/#/c/105284/
http://review.cyanogenmod.org/#/c/105100/ (This is a security fix hence the build today) Issue with this, currently will get sorted for a future build
Mainline cm update ^^ those changes are not merged into CM but I've picked them to go into this rom for my own personal build. I will share this build
------------------------------------------------------
7/7/2015
CM general update
CVE's patched (security) http://review.cyanogenmod.org/#/c/102586/
NFC Update
Low memory killer updated
USB OTG Enabled
Brightness should be brighter (Should)
Re-implemented the powerhal from CM-10.2 (For those of you who have been around here for ages)
Updated the keymaster file based off of the grouper (Security)
A ton of patches from the grouper kernel http://review.cyanogenmod.org/#/c/102546/
VFS/ Compaction changes http://review.cyanogenmod.org/#/c/102597/
------------------------------------------------------
20/6/2015
CM mainrom update
GPS working in permissive only mode
-----------------------------------------------------
9/4/2015
12.1 update
Chrome/Firefox work
Updated with most recent CM source
------------------------------------------------------
6/4/2015
CM-12.1
DO NOT DIRTY FLASH OVER CM-12.0 IT WILL CRASH
gps is still broken
everything below counts
NEEDS KERNEL FLASH as usual
------------------------------------------------------
6/4/2015
New Kernel, not loaded with crap. This kernel is WIP. NO SMARTMAX on it, No S2W (Let the rage begin)
Might have turned the audio up...Sounds like it, need someone to confirm
Button light stays on when it needs to now.
------------------------------------------------------
3/4/2015
Fixed No Data issue FLASH THE NEW ROM AND BOOTIMG
------------------------------------------------------
2/4/2015 or 3/4/2015 depending on where you live
1st actual working release so lets start the change log
Battery WORKING
Source updated to today's released source
SELINUX DISABLED
Rotating working
GPS broken
regretting this...check the post above this one...
sooooo I know a load of you have downloaded this? Any bugs I've not listed?
Lloir said:
sooooo I know a load of you have downloaded this? Any bugs I've not listed?
Click to expand...
Click to collapse
Sorry man cant use it daily without the battery being fixed! Other than that the camera works? at least for the most part
just installed it and i am suprised...very smooth.
still installing apps for daily use. will of cause report if theres anything to report.
what excactly does not work with cam? i can shoot pics and they look as pretty as they should.
so, happy new year to every1!
el-Loko said:
just installed it and i am suprised...very smooth.
still installing apps for daily use. will of cause report if theres anything to report.
what excactly does not work with cam? i can shoot pics and they look as pretty as they should.
so, happy new year to every1!
Click to expand...
Click to collapse
It wasn't working for me, but yeah, all of you say it works, so I'll take your word. :good:
Lloir said:
It wasn't working for me, but yeah, all of you say it works, so I'll take your word. :good:
Click to expand...
Click to collapse
I'll jump in as soon as builds with proper battery comes up.
And, thank you for being an awesome dev.
Lloir said:
sooooo I know a load of you have downloaded this? Any bugs I've not listed?
Click to expand...
Click to collapse
installing right now, can't wait to test!
i moved on to the OPO as daily driver, so i don't have to care about stability, but also i'm eager to see how the HOX+ runs Android5! Thanks for your awesome work!:good:
reaper90 said:
installing right now, can't wait to test!
i moved on to the OPO as daily driver, so i don't have to care about stability, but also i'm eager to see how the HOX+ runs Android5! Thanks for your awesome work!:good:
Click to expand...
Click to collapse
Yeah, I need to move on soon, so new devs are going to be needed for the X+ by the next major release.
Lloir said:
Yeah, I need to move on soon, so new devs are going to be needed for the X+ by the next major release.
Click to expand...
Click to collapse
This device is more than two years old now, i don't think there will be new devs coming to this device. Although i know not everyone wants to buy or can afford a new device every two years, i think this one has done it's job. while htc dropped support after only one year, i think some quite stable 4.4 roms are more than we could have asked for!
first impression on this build:
runs pretty good so far, camera not working here, kickstarting the battery from TWRP does not really work for me (maybe i'm doing something wrong) and when using adb shell, the charging led stays forever on.
Camera working fine here !
and whats the purpose of turning the battery on..? I could reboot and its working fine. I did not execute any command. But the battery shows 66% even though its lower than that. So the only problem we face if we dont turn it on is that we cant see the real percentage or what....?
backb0ne5p1d0r said:
Camera working fine here !
and whats the purpose of turning the battery on..? I could reboot and its working fine. I did not execute any command. But the battery shows 66% even though its lower than that. So the only problem we face if we dont turn it on is that we cant see the real percentage or what....?
Click to expand...
Click to collapse
Pretty much, not tested to see if it doesn't charge though....it will ALWAYS show 66%
Also are you using a 3rd party app for camera??
I don't mind it showing 66 as it's not my main phone.
And No, but I flashed GApps.
All I did was full wipe, Flash boot.img, flash ROM, flash GApps. Then the ROM booted and had a working camera
I think I found a temporary fix for the battery problem!
Go to the store, download 2 apps.
1) Boot shell
2) sudo for android.
Open sudo for android and click "Install Sudo"
Then open Boot Shell and click add command button. And add the command "sudo /system/bin/htcbatt"
Now reboot your phone and the battery stats will still be there
backb0ne5p1d0r said:
I think I found a temporary fix for the battery problem!
Go to the store, download 2 apps.
1) Boot shell
2) sudo for android.
Open sudo for android and click "Install Sudo"
Then open Boot Shell and click add command button. And add the command "sudo /system/bin/htcbatt"
Now reboot your phone and the battery stats will still be there
Click to expand...
Click to collapse
Yeah, there's that.
I have it fixed here, just not happy with the fix at the moment. IF People want to fix it this temp way do the following :
reboot into TWRP
mount system
adb shell
chmod 777 system/bin/htcbatt
reboot
If your not happy with using a 777 chmod then that's understandable, I'm trying out a 2nd fix as we speak, this will also help me to fix the battery issue in TWRP too
Things that are now working on my local build
Device Encryption
Battery + Battery LED
IF I'm happy with the battery fix, I'll do that release today.
Still broken :
GPS --- Kinda borked.
Rotating
Button lights are a little yeah.
This is going to be replaced with omni-L
Stay tuned, Not releasing ANYTHING until I have a nice working build of a ROM, not going to be releasing half-assed builds anymore.
Ok, after 2 days of daily use i can say that this rom is very stable, no reboots or freezes. Only GPS and auto-rotate is not working for me, but (orig)cam does its job.
One tip for the battety sidekick:
Instead of doing the trick via pc do it in a shell on your phone but dont kill the process with ctrl-c.
[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.
Mod edit: Thread closed on owner's request.
exNoShadez-EAS Kernel
Hey Pixel XL forum. I'm a Pixel/Sailfish owner, who also enjoys hacking on kernel code. I recently released a Kernel in the Google Pixel forum => but we are all using the same kernel, sooo.... I thought after pushing my second stable release, that I should probably post on the XL forum too.
My kernel is a bit different than most kernels available, you will quickly notice. Lots of interesting features and some unique ones too.
FEATURES
- Current LTS release -> Linux-3.18.114
- Energy Aware Scheduling
- Schedutil (default Cpu Governor)
- RCU infrastructure backport (with expert mode enabled)
- Cpu-Boost / Input Boosting (enabled by default)
- BINFMT_MISC support (NOT mounted on boot).
- Kernel Hardening/Protection (CopperheadOS/Grsec/Pax Marlin kernel hardening features)
- leds-qpnp: Notification LED control - V1.1c (Boeffla) - Adapted for Marlin
- Binder_rt = My own re-implementation of AOSP Binder that uses rt_mutexes; supporting priority inheritance
- Improved scheduling/determinism for high priority threads/tasks
- Backported Scheduling, Locking and Workqueue subsystem code from Newer Linux kernels.
- Audio Driver enhancements / backports (from Wahoo/Pixel 2)
- Sound/Audio driver Tweaks (bug fixes, scheduling improvements)
- forced Interrupt threading enabled
- Wifi Mac Address Randomization
- WireGuard (VPN) kernel module support
- KCal Advanced Colour control
- Improved ASLR (in kernel)
- USB Fast Charge
- Wake Gestures
- GCC 6/7+ Fixes
- Built with GCC-8.x-dev
- and more
Contains code from everywhere: Code Aurora, Flar2/Marlin, CopperheadOS, AOSP, Project-EAS, Freak7/Kirisakura, Linaro, Pixel 2 kernel sources, mainline linux and elsewhere. Modifications and backports by me, as well.
BACKGROUND
I wanted a kernel for My Pixel that had 'all of the things', it didn't exist... So I'm working on my own kernel. I try to balance Security/hardening, experimental features with high Performance and battery life. <- not an easy task! ... Some of the security features do come with overhead, but if you use apps that are CPU heavy / processing and/or require low latency - they will perform well (at the cost of chewing some battery life, of course).... Battery life and SOT are very reasonable though.
WARNING / VERY IMPORTANT: This kernel isn't compatible with installing TWRP ~> meaning; you must use the fastboot version of TWRP (used in RAM) , flash the kernel and NOT install TWRP to your system (the kernel is too big for TWRP to co-exist).... This may sound inconvenient, but there are a number of valid reasons to avoid reducing a kernel's size in order to support TWRP installation, in the boot partition.
***Fun facts on not supporting TWRP below => 2nd post: PLEASE READ: to understand my motivation***
TWRP REMOVAL
*To remove TWRP from your system; You need the stock boot.img from your running/current firmware (which is inside of the factory image zips) or use the Nov Stock boot.img provided here. Then it's as simple as flashing the boot.img to wipe TWRP;
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Stock 8.1 July 2018 Boot.img => https://github.com/nine7nine/Apps/raw/master/MarlinStockJulyBoot.img
Now you can proceed with using the TWRP fastboot boot.img to flash my kernel, magisk/supersu or whatever else....
Fastboot twrp boot image => https://dl.twrp.me/marlin/twrp-3.2.2-0-marlin.img
WARNING: This shouldn't need to be said, but we did have someone on the Pixel forum who did this, so I'm adding a sticky/warning here; do NOT EVER re-lock your bootloader after flashing any kind of custom software, kernels, etc to your device - *it will brick your phone*. Meaning you are screwed would need an RMA / replacement device ... everyone in the XDA community should know better, but still; worth mentioning....
IMPORTANT:
Before asking questions; Please read through the thread (starting with the last few pages) - I shouldn't need to be repeatedly answering the same questions over and over again. It's good practice to get into the habit of reading through threads before asking questions in any thread on XDA, as more often then not; you're question has probably been answered. Thanks!
EXNS-EAS KERNEL DOWNLOAD:
JULY 2018 OREO 8.1 RELEASE exNoShades-eas Kernel Flashable zip
https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v2.8.2_f94351f.zip
It is stable, high performance and very responsive...
Important: You will need root; I don't support non-rooted devices && some features require it. I recommend using Magisk; https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 ...
NOTE: Make sure to flash the latest Magisk beta *before* flashing the kernel zip ...
More Background / Important Notes:
Binder_RT:
My own port and re-implementation of the Binder Kernel Driver; a slightly modified version of The AOSP binder.
Binder_RT uses rt_mutexes as oppsed to mutexes for locking in Binder, ion, ashmem, etc... rt_mutexes support priority inheritance and should improve determinism in Binder, speed up IPC, Ion and Ashmem => Allowing applications that require low-latency, tight deadlines, low jitter and deterministic behaviour to perform better ~ This re-implementation is proving to be the great for those types of applications. The goal here is to help ensure that the Kernel and Binder's high priority && time critical threads and tasks are properly prioritized... Example; audio buffers arriving on time / no buffer underruns... *Further development work is planned to research, experiment with and improve Binder_RT.
rt_mutex documentation, for those interested;
https://github.com/nine7nine/Marlin_exns-eas/blob/EXNS_EAS/Documentation/locking/rt-mutex.txt
https://github.com/nine7nine/Marlin_exns-eas/blob/EXNS_EAS/Documentation/locking/rt-mutex-design.txt
CPU-Boost / Input Boosting:
Touch inputs boost CPU frequencies (thus improves performance and responsiveness).
# Cpu-boot / Input boost settings
write /sys/module/cpu_boost/parameters/input_boost_enabled 1
write /sys/module/cpu_boost/parameters/input_boost_freq "0:1363200 1:0 2:1900800 3:0"
write /sys/module/cpu_boost/parameters/input_boost_ms 100
IO/ CPU Governors:
This kernel doesn't include a thousand io/cpu governors. IO-wise; CFQ is the default, but we've got a few in there. chose your poison, but know that the majority of my testing is centered around cfq and deadline. CPU Governor-wise the common Linux CPU governors are there; along with Sched and Schedutil....
Stick with Schedutil - on idle, it draws very little power and in most 'peak performance situations, it should do very well..... I'm getting great battery life, sot and performance.
Managing Kernel Settings:
Get EX Kernel Manager - my original code on github was forked from EX kernel, before rebasing it - but EXKM will give you access to 99% of my kernel's settings.
My 8.1 Kernel Sources: https://github.com/nine7nine/Marlin_exns-eas
Donations via PayPal very much appreciated. I do put a significant amount of energy and time into researching, development, testing / QA and also providing support/help to end-users... It's definitely not mandatory to donate; but If you appreciate the effort, see value or benefits from using my kernel on your device and can afford to; Use the "Donate to me" button or the below link... It makes a big difference. thanks!
https://www.paypal.me/jrdnjhnstn
Why TWRP Installations are NOT supported:
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
(and why I'm not using it!)
Most custom/android kernel devs are using the above configuration in kernel compilation, which is arguably very BAD... I understand that boot partitions are small and the desire to install TWRP to them, thus there is a need to reduce the kernel's size....and yes, this will achieve that - However;
1. SUSE, RedHat, etc (Enterprise linux) disable CONFIG_CC_OPTIMIZE_FOR_SIZE -> it's original use case has proven to be invalid. Even Google (in their own documentation) advise against using this; https://source.android.com/devices/tech/perf/boot-times ....
2. It suppresses useful compiler warnings....
3. As SOCs have become more powerful, google has come to the same conclusion that Enterprise Linux did back in 2012.
4. by turning off CONFIG_CC_OPTIMIZE_FOR_SIZE, we achieve better performance, boot time and better cache utilization.
Clark Williams / Redhat Bugzilla said:
* Cause: CONFIG_CC_OPTIMIZE_FOR_SIZE set with assumption that smaller code would yield hot cache lines and good performance
* Consequence: this config caused gcc to generate jump-to-jump code which causes cache line bouncing, hurting performance
* Fix: turn off CONFIG_CC_OPTIMIZE_FOR_SIZE
* Result:slightly larger kernel but better cache utilization
Click to expand...
Click to collapse
(The Above is quoted from Clark Williams, A Senior Software Architect @ RedHat -> https://bugzilla.redhat.com/show_bug.cgi?id=796297)
I know of no other way to significantly reduce kernel size. Disabling some debugging, unneeded features, etc helps - but not enough.... I am focusing on optimization, using newer builds of GCC/Linaro, performance enhancements, fixing compilation errors, etc, etc -> these things are more important than trying to support TWRP installation.
Therefore; I do NOT support installing TWRP....
This sounds incredible. All those features.. and then some. Hard for me to test as I rarely use my PC but I may have to go and give this a try.
Edit: would it be possible to create a build for those who do want to use TWRP? Would be great to do some benchmarks (real work using DiscoMark and synthetic using geekbench/AnTuTu/etc) to see differences between the two.
All those features are welcome in this poor Oreo pixel community! thanks for your work..
i'll try it as soon as possible!
spr33 said:
This sounds incredible. All those features.. and then some. Hard for me to test as I rarely use my PC but I may have to go and give this a try.
Edit: would it be possible to create a build for those who do want to use TWRP? Would be great to do some benchmarks (real work using DiscoMark and synthetic using geekbench/AnTuTu/etc) to see differences between the two.
Click to expand...
Click to collapse
No. like I said. I don't/won't support installing twrp. it would require reverting a bunch of patches/ work that I've already put in... and also not using linaro GCC 7.2.1 compiler, either...
the time invested would be a complete waste for me and I would have maintain another separate branch. test another build, etc, etc'... i'm not doing it. my current goal is to reduce my branches into one single branch/build;. ... which will end up hopefully being binder_rt... not create more.
feature wise, pretty much a 'best of' what any other custom kernel offers for Marlin, all of the hardening stuff (I think I'm the only Marlin kernel on XDA with that), etc... afaict, I'm the only one rolling in EASv1.4, cpu-boost, dynamic stune boost; all of which I've ported myself... some of the audio driver stuff I personally ported (more coming) and binder_rt is my baby; I ported aosp binder and researched / Inplemented all of the changes to Binder...
in my yet-to-be-released binder builds I also have backported a large chunk of the linux locking, workqueues and scheduling code and some other bits from newer mainline linux kernels (which allow me to pull in some new features and use them).
so I'd rather work on this kind of stuff, over caring about twrp, doubling my workload to support running synthetic benchmarks between gcc's -Os vs. -O2 optimization levels...
Thanks for the new kernel. Sounds very interesting. Can't try it atm because i am on dp1 from 8.1. Hope you gonna also support 8.1 when official sources are out. For me battery life is already great on dp1.
housepabldroid said:
All those features are welcome in this poor Oreo pixel community! thanks for your work..
i'll try it as soon as possible!
Click to expand...
Click to collapse
haha. pixel community isn't too bad. there's just not a lot of custom oreo ROMs.... myself, I wouldn't want to run any of those custom roms anyway. they usually are built without odexing or proper signiture key signing = less secure and way less optimized... Stock ROM is great, just needs root and a few apps to modify / customize it a bit.
for me, the kernel has always been the issue. lol... therefore, roll my own. lol....
ya, for sure give it a try... I honestly would say binder_rt is the best build... the 'stable build' is a bit of a misnomer - all of the builds are stable, just the binder ones are running more experimental code... binder_rt blows the socks off any other Marlin kernel for certain kinds of workloads... I'm aiming fir it to become my default build...
Donric13 said:
Thanks for the new kernel. Sounds very interesting. Can't try it atm because i am on dp1 from 8.1. Hope you gonna also support 8.1 when official sources are out. For me battery life is already great on dp1.
Click to expand...
Click to collapse
yup. I have to wait until kernel sources are released. you got it!. but when they are / 8.1 is released; I will be upgrading to 8.1, so no worries - there will be an 8.1 version...
I've heard heard that battery life is pretty good on 8.1, there's a thread in the pixel forum about it... but by what they were saying, it didn't seem that much better than what I see from my kernel.....
I'm more interested to see what performance improvements are in 8.1 kernel sources... I've found stock kernel to be a bit crappy for some stuff...
well, if at some point you are bored and want to test my kernel on 8.1, go for it. ya never know: maybe it will work. the reason I say that?
IIRC - it was tested with my old kernel / sources build... could've been a bug, not present in the new one.... or something else. IdK.. being as I'm on 8.0 I can't even look into why that might be or have been...
just make sure if u do ever try it, keep the stock boot.IMG for 8.1 around, in case it doesn't work..... and report back, if it does work. lol
Gotta say super smooth. Thanks for sharing. Maybe it's just a glitch in ex kernel manager but zram "stopping..." Or nothing to worry about.
JS.zip said:
Gotta say super smooth. Thanks for sharing. Maybe it's just a glitch in ex kernel manager but zram "stopping..." Or nothing to worry about.
Click to expand...
Click to collapse
Ah yes, I should've mentioned that ~ zram is working fine - but EXKM is being denied permission to read those files on the file system - I think it's due to a change in cgroups code (from merging in EASv1.4), but I haven't gotten to the bottom of it yet....
No worries though ~ I HAVE completely verified that zram is working, mounted swapon and behaving as it should... Honestly, the defaults for zram are fine ~ if they ever weren't; you would have bigger problems on your hands, that changing swapping wouldn't help. lol
Which build are you using? (just curious)
nine7nine said:
Ah yes, I should've mentioned that ~ zram is working fine - but EXKM is being denied permission to read those files on the file system - I think it's due to a change in cgroups code (from merging in EASv1.4), but I haven't gotten to the bottom of it yet....
No worries though ~ I HAVE completely verified that zram is working, mounted swapon and behaving as it should... Honestly, the defaults for zram are fine ~ if they ever weren't; you would have bigger problems on your hands, that changing swapping wouldn't help. lol
Which build are you using? (just curious)
Click to expand...
Click to collapse
Thanks that's what I thought. The bad boy "Binder RT" lol
JS.zip said:
Thanks that's what I thought. The bad boy "Binder RT" lol
Click to expand...
Click to collapse
bad boy eh? haha.
Ya, no worries - I check that sort of stuff, when it crops in... fixing that particular issue just hasn't been a huge priority, over other stuff that I'm working on. (and because I think it's pointless that EXKM even displays it to begin with - it just gives users the false impression that they are tweaking something, that in 99.99999% of cases - is absolutely pointless to touch).
Anyhoo, cool - let me know how things are working out with the binder_rt build, as you get some more use in ~ I really want it to become my main focus / implementation. (I personally won't be going back to using any other build day to day, anyway.)
nine7nine said:
bad boy eh? haha.
Ya, no worries - I check that sort of stuff, when it crops in... fixing that particular issue just hasn't been a huge priority, over other stuff that I'm working on. (and because I think it's pointless that EXKM even displays it to begin with - it just gives users the false impression that they are tweaking something, that in 99.99999% of cases - is absolutely pointless to touch).
Anyhoo, cool - let me know how things are working out with the binder_rt build, as you get some more use in ~ I really want it to become my main focus / implementation. (I personally won't be going back to using any other build day to day, anyway.)
Click to expand...
Click to collapse
I just wanted to point out that I grabbed your stock kernel from the OP and had planned to use that to flash my stock image. However, I happened to have the latest boot.img release decompressed on my drive so I compared it to the one I had on hand.
MD5 for your Stock Image: 7A2D92981FDE96E5D60D806019ACFA0C
MD5 for Google's Stock Image: BF9EDA2888C8C6A1FCD0A7DB6E37F739 (Latest November build)
Now I don't want to sound like the suspicious type, because in reality the stock kernel you provided is just to get TWRP off the device before flashing your kernel, but I'm forced to ask why your stock image is not identical with the main stock image? Unless your stock kernel isn't from the latest release but instead from a prior month or something of that nature (It would take me quite awhile to download the other month's releases just to check so I was hoping to ask you instead)
AlkaliV2 said:
I just wanted to point out that I grabbed your stock kernel from the OP and had planned to use that to flash my stock image. However, I happened to have the latest boot.img release decompressed on my drive so I compared it to the one I had on hand.
MD5 for your Stock Image: 7A2D92981FDE96E5D60D806019ACFA0C
MD5 for Google's Stock Image: BF9EDA2888C8C6A1FCD0A7DB6E37F739 (Latest November build)
Now I don't want to sound like the suspicious type, because in reality the stock kernel you provided is just to get TWRP off the device before flashing your kernel, but I'm forced to ask why your stock image is not identical with the main stock image? Unless your stock kernel isn't from the latest release but instead from a prior month or something of that nature (It would take me quite awhile to download the other month's releases just to check so I was hoping to ask you instead)
Click to expand...
Click to collapse
Easy explanation - I'm on Sailfish, you aren't; so the md5 wouldn't match...
I can do one of two things; you can post a upload/link to your boot.img and I will replace the link for Marlin's nov boot.img (adding it to my github) OR I will remove the link from the post and Marlin users will have to fend for themselves. (have to download 1.8GB firmware themselves for a boot.img... Obviously i'm NOT downloading your guys Nov Firmware images).
nothing suspicious at all here, dude.
EDIT: I've removed the link to the sailfish Nov boot.img, as a sign of good faith; I can replace it with the Marlin Nov boot.img - but that will require you to post a download/link to me, so I can add it in. thx
nine7nine said:
Easy explanation - I'm on Sailfish, you aren't; so the md5 wouldn't match...
I can do one of two things; you can post a upload/link to your boot.img and I will replace the link for Marlin's nov boot.img (adding it to my github) OR I will remove the link from the post and Marlin users will have to fend for themselves. (have to download 1.8GB firmware themselves for a boot.img... Obviously i'm NOT downloading your guys Nov Firmware images).
nothing suspicious at all here, dude.
EDIT: I've removed the link to the sailfish Nov boot.img, as a sign of good faith; I can replace it with the Marlin Nov boot.img - but that will require you to post a downlink to me, so I can add it in. thx
Click to expand...
Click to collapse
No problem, I download every Marlin release so I'll just update my AFH folder to include the monthly kernel release and users can download it from there. You can either link to my folder or download from it to add to your repository; either one is fine with me Thanks, and I do appreciate what you're doing but I have a 'verify first' stance since these devices are a big part of people's lives. I'm going to give your kernel a spin now, I appreciate you getting back to me so quickly. If only AFH was this fast, I just spent 25 minutes trying to get it to create an empty folder...
Link to Marlin Stock Images: https://www.androidfilehost.com/?w=files&flid=231142
Edit: I attempted to flash the "exNoShadez_eas-3.18.83_Binder_b0b66e0.zip" from the fastboot installed version of TWRP after flashing the stock boot to slot_a and slot_b, but it is failing with an error that states, "New image larger than boot partition. Aborting..." Then updater process Error 1. Any idea what would cause that?
AlkaliV2 said:
Edit: I attempted to flash the "exNoShadez_eas-3.18.83_Binder_b0b66e0.zip" from the fastboot installed version of TWRP after flashing the stock boot to slot_a and slot_b, but it is failing with an error that states, "New image larger than boot partition. Aborting..." Then updater process Error 1. Any idea what would cause that?
Click to expand...
Click to collapse
Hey, I added your nov boot.img to the OP. put it on github to save a few clicks for people.
The error you are seeing would suggest that TWRP is installed to the system. That is the only time anyone has ever bumped into that message. So, I'm not sure what's going on with your end but it would seem you have twrp actually installed...?!
the TWRP that you are supposed to use, is this one;
https://dl.twrp.me/marlin/twrp-3.1.1-1-fastboot-marlin.img
that loads and runs from RAM. twrp can't be "installed from fastboot" ~ it installs to the boot partition; leaving not enough room for the kernel.
nine7nine said:
Hey, I added your nov boot.img to the OP. put it on github to save a few clicks for people.
The error you are seeing would suggest that TWRP is installed to the system. That is the only time anyone has ever bumped into that message. So, I'm not sure what's going on with your end but it would seem you have twrp actually installed...?!
the TWRP that you are supposed to use, is this one;
https://dl.twrp.me/marlin/twrp-3.1.1-1-fastboot-marlin.img
that loads and runs from RAM. twrp can't be "installed from fastboot" ~ it installs to the boot partition; leaving not enough room for the kernel.
Click to expand...
Click to collapse
Yeah, that actually explains it. I was using a kernel with TWRP installed last go round and now it seems just flashing the factory boot.img is not getting rid of the installed TWRP. I'll figure out how to get TWRP removed for good this time; thank you for letting me know where to look.
AlkaliV2 said:
Yeah, that actually explains it. I was using a kernel with TWRP installed last go round and now it seems just flashing the factory boot.img is not getting rid of the installed TWRP. I'll figure out how to get TWRP removed for good this time; thank you for letting me know where to look.
Click to expand...
Click to collapse
Yup. TWRP can't be installed along side. Running it from RAM has to be used. ie: I don't support TWRP installations. lol
Flashing the factory boot.img DOES get rid of TWRP for good ~ you just have to make sure to use the TWRP fastboot boot.img for flashing my kernel after (since fastboot/twrp doesn't install to the boot partition)...
I've added a link to the OP to Marlin's twrp fastboot boot.img....
I also updated all of the download links and double-checked to make sure that all of the Marlin zips are packed properly with AnyKernel2 + relabelling every file on my github (by re-packing all of them all... This is mostly just paranoia on my part - but now that I'm supporting 2 devices, best to make sure that nothing gets tangled together.)
@everyone
just a few notes, since you guys are just getting exposure to my kernel, the way I do things; in regards to development, etc.
-> I post test builds (this usually happens when I make big changes.). reports are helpful on these builds.
-> Development happens fast; *I routinely add new features, bug fixes, etc and i'm almost always ahead on LTS updates over the Stock kernel.
examples;
=> lts -3.18.83 build available on the day of release
=> my Binder_rt branch is currently 140+ commits (code changes) ahead of the the other branches.
(changes since in the current downloads/releases)
=> There are a number of bug fixes, a few added features (mostly in-kernel stuff), some optimizations *and* there are massive upgrades to parts of the kernel's subsystems. (100+ commits are related to that)...
(changes since the current downloads/releases)
NOTE: The binder Branch (non-rt) will see the majority of the above changes code, but the Stable branch will only see a subset of these commits + bug fixes.
I probably won't roll out a test build for Binder_rt builds, until I've had the newest code running for a couple of days.... At that point, once things have proven to be stable good ~ i'll roll out a test build for anyone who wants to help out and dogfood test builds....
Then, I will push back changes back into the Binder builds, Stable, etc... I usually try and line up actual releases to LTS and/or => more importantly monthly android security / firmware updates....
**So the gist is; there will be frequent updates. Update as you see fit - anyone who wants to help out - run test builds and report back issues.
So pending a detail or two, I likely will be phasing out my other builds in favor of the Binder_rt build.
- I've had quite a lot of feedback via the Pixel forum, PMs and email (and a couple of friends using it too).
- The Binder_rt build seems to be very stable for everyone.... not too mention just all around better.
- there seem to be no drawbacks and quite a few benefits to that build over the others.
The one thing I'm waiting on is; I've joined the Android Kernel Developers Google Group and am currently waiting to see if I can't get some help with porting a missing Kernel function into Marlin's sources ~ this particular kernel function is what's stopping me from having Binder be sync'd with the AOSP binder implementation.... I'm hoping to resolve this sooner than later, at which point I will be able to merge in those commits (and test them).
In the meantime I'm working on a few backports to the audio driver and a few other bits (taken from Wahoo/Pixel 2 kernel sources). I've also pulled in a few fixes to binder from Wahoo, as well....
So I might post a test build for Binder_rt tomorrow - as it's accumulated a number of changes, bug fixes, etc.... I'm not sure If I will have any resolution to the missing kernel function - but that doesn't affect pushing a test build....