Related
The NookieDevs are pleased to announce the CyanogenMod 10.1.3.2 stable release for the Nook Color!
As the "stable" label suggests, all major features of the hardware work and the release should be suitable for day-to-day use on your Nook Color. As the "stable" label also suggests, updates (if any) will be primarily to fix bugs -- new features and big changes should not be expected.
Highlights: (mostly not news if you've been keeping up with CM10/10.1/10.2 nightlies)
Linux kernel 3.0.8, plus hardware support from TI OmapZoom's android-omap3-3.0 branch and board support forward-ported from BN kernel releases.
All of the features of CyanogenMod 10.1, based on Android 4.2.2.
Full 2D and 3D graphics acceleration using the GPU.
Unofficial Bluetooth support, including support for a wider variety of BT peripherals than in previous releases. (The Nook Color lacks a proper Bluetooth antenna, so range will be somewhat limited.)
10.1.3: significantly improved graphics performance and improved battery life over previous CM10.1 releases.
10.1.3: various bug fixes, including fixes for Bluetooth tethering, Adobe Flash Player, and a nasty hardware bug affecting the internal storage of some Nook Colors.
10.1.3.1: fix for a security bug reported upstream which potentially allows an attacker to obtain local root (see the dev thread for details). Thanks to Nico Golde and Fabian Yamaguchi for reporting, Ivaylo Dimitrov and Pavel Machek for working on a fix, and dhiru1602 for reporting a bug in that fix.
10.1.3.2: fix crash when opening "About tablet" in Settings. Thanks to CM's Ricardo Cerqueira for the fix and the rebuild.
Known issues:
Current releases of Netflix do not work with CM10.1 -- version 1.8.1 is the last version known to work. If you want/need a newer release of Netflix, look into the Xposed mod, which provides a workaround for Netflix -- pastordl has done a nice writeup of the process here.
The CyanogenMod Updater app may crash when checking for new updates. Deleting /sdcard/cmupdater and/or clearing the app's data may help.
Download:
https://download.cyanogenmod.org/get/jenkins/51847/cm-10.1.3.2-encore.zip
Code:
MD5: 72d6978a754d5637f28f3c031367781a
SHA1: 316da5997232bb641240c2378fdaa634ce5d50eb
SHA256: b9391d37418322b1960db8edd2a738a44ac2ea12cdeb02a80628c6f95efaa67f
Source code:
https://github.com/CyanogenMod/android_device_bn_encore/tree/cm-10.1.3 (device-specific source)
https://github.com/CyanogenMod/android_kernel_bn_encore/tree/cm-10.1.3 (kernel)
https://github.com/CyanogenMod/android/tree/cm-10.1.3 (manifest for the rest of the CyanogenMod source)
Build instructions (discussion of build issues belongs in the development thread)
This release is the product of much effort by many people over a considerable period: many thanks to fattire, keyodi, eyeballer, krylon360, dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, drmarble, mateor, dhiru1602 and many more. Thanks are also due to the CyanogenMod project, upon which we are building, and Texas Instruments, which provides excellent support for its embedded platforms to the open-source hacking community. (TI's exit from the consumer electronics SOC market is a loss for all of us.)
XDA:DevDB Information
CyanogenMod 10.1 Stable, a ROM for the Barnes & Noble Nook Color
Contributors
steven676, keyodi, fattire, The CyanogenMod Project, NookieDevs, many others (see post)
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 10.1.3.2
Stable Release Date: 2013-12-18
Created 2013-09-05
Last Updated 2013-12-19
Reserved
Google Apps; other CyanogenMod builds
Google Apps
http://goo.im/gapps
As of 2013/10/09, the latest release for CM10.1 is 20130812, but please check the linked page for updates.
Please make sure that you have the correct Google Apps flashed before reporting problems involving the Google Apps (Play Store, Google Keyboard, etc.).
Other CyanogenMod builds
This is the thread for CM10.1 stable releases. There are other official CyanogenMod builds for Nook Color available:
CM11 nightly builds -- these experimental builds, based on Android 4.4, contain the latest changes to CyanogenMod and to hardware support for the Nook Color. As the name suggests, new builds are made and posted (roughly) every day; these builds are fully automatic, with no testing done before posting.
CM10.2 stable releases -- while the state of the Nook Color-specific hardware support should be nearly identical to that of CM10.1, you may find this Android 4.3-based release more (or less!) stable than this Android 4.2-based one.
Archived nightly builds for CM10.2, CM10.1, and CM10. You may find the last CM10 nightly (20130421) faster than the later releases, particularly during playback of HD 720p video.
Please check that your questions are in the appropriate thread. (If you're interested, there's lots of past discussion in those threads, as well as the development thread.)
Frequently Asked Questions and Troubleshooting
The soft keyboard keeps crashing!
The Play Store is acting up!
Did you flash the correct Google Apps?
What happened to the "Developer options" and "Performance" screens in Settings?
They're hidden by default now in CM10.1 and later. To show them, go into "About tablet" and tap the build number (for CM10.1 stable releases, JDQ39) seven times.
How do I get the Honeycomb/ICS tablet UI?
You want to use the Auto-Patcher to modify your ROM for the tablet UI. (Don't forget to thank Caldair for maintaining the Tablet UI mod, and mateorod and the rest of the Auto-Patcher developers for building that tool.)
I'm having a problem with my Nook Color running CM10.1.
That's not a question
Okay, I'm having a problem with my Nook Color running CM10.1 -- is there something I can do to troubleshoot?
Glad you asked! Please check the following:
Does the problem occur with a clean install of CM10.1? This means wiping /data and not restoring a Nandroid backup afterwards. Don't restore system apps and/or their data in Titanium Backup either (user apps/data are okay).
Are you overclocking? If so, does the problem occur when you set the maximum clock speed to 1000 MHz or below? To be clear, we are not interested at this point in bug reports of any kind that happen if you have the maximum CPU speed set above 1000 MHz. If you're experiencing system crashes or "sleep of death" (SOD), you may also wish to try capping the CPU clock speed to 800 MHz (but if this helps, please report your problem here and fill out the hardware survey).
Do you have any patches, custom kernels, or other tweaks applied? If you do, does the problem occur without those applied? (We're not necessarily going to ignore bug reports from patched or tweaked systems outright, but it can make our job harder, and we do need to know what changes you have applied to judge whether or not the change might be relevant to your problem.)
I'm having no luck with the suggestions above. What information should I include with my bug report?
When reporting a problem, please include the following information if at all possible:
Full description of the problem -- "it crashes" doesn't count. How do you trigger the problem (or does it occur by itself)? What exactly happens when the problem occurs? How often does it happen?
For problems with apps or specific pieces of the system software: we'll almost certainly ask for a logcat of the event, so you'll save everyone some time by including it.
For problems involving system freezes, crashes, or SOD: if you can connect to the tablet via adb while it's "unresponsive", please provide dmesg and logcat output from that time. If you cannot, try power-cycling it while it's still plugged into USB, and provide dmesg output from immediately after the reboot, plus the contents of /proc/last_kmsg if that file exists (let us know if it doesn't).
For unexpected reboots: provide the contents of /proc/last_kmsg from after the reboot.
Edit: Used these instructions for installing 10.1 on a SDCard.
http://forum.xda-developers.com/showthread.php?t=1941858
Great thanks!
Sent from my NookColor using Tapatalk 4 Beta
Congrats and thanks again Steven and the other NookieDevs, this is running very well, at least on my NC, somehow seems a little more responsive/smoother (especially when background apps/downloads are running - new WiFi tweak?) than the recent nightlies/RC's. Great job, but, there is a new nightly calling, or I've sort of been wanting to try Mateorod's AOSP, besides, my schedule is beginning to settle back down enough that I will probably try to increase my "Android Ninja" experience, so I probably won't be stable long. Keep up the great work, glad to hear that you will still be tweaking it.
Question, are your latest WiFi and/or Graphics tweaks merged yet?
NC crashing hard with clean CM10.1 install
Hi,
great to see CM10.1 on NC. I have just made a clean install on my Nook and generally impressed. Unfortunately my Nook started crashing hard, something that I never experienced before It seems to be correlated with Gallery application, I can reproduce crash only after I open Gallery and then return to home page. Here is what happens:
open Gallery, look at one or few pictures
go back to Home
wait a bit, one minute or so, maybe go to other app or settings
screen goes blank, navigation buttons and status bar are still visible but display area gets dark
no response to touch or nook button
after ~30 seconds Nook reboots
I managed to catch dmesg output right before reboot, attaching it here, there are two files in archive, first is dmesg output before I run gallery, second is dmesg right before it reboots. Logcat and /proc/last_kmsg are also in the archive. I could get more info if anybody wants to look at it and can tell me how to get it.
I ran CM7.2 on the same device for quite some time and had no troubles with that. CM10.1 install is from final, wiped both data and cache, no google apps installed yet, no other apps restored, virgin clean :angel: No overclocking, and no other settings changed, no patches.
Thanks,
Andy
andy1001 said:
Hi,
great to see CM10.1 on NC. I have just made a clean install on my Nook and generally impressed. Unfortunately my Nook started crashing hard, something that I never experienced before It seems to be correlated with Gallery application, I can reproduce crash only after I open Gallery and then return to home page. Here is what happens:
open Gallery, look at one of few pictures
go back to Home
wait a bit, one minute or so, maybe go to other app or settings
screen goes blank, navigation buttons and status bar are still visible but display area gets dark
no response to touch or nook button
after ~30 seconds Nook reboots
I managed to catch dmesg output right before reboot, attaching it here, there are two files in archive, first is dmesg output before I run gallery, second is dmesg right before it reboots. Logcat and /proc/last_kmsg are also in the archive. I could get more info if anybody wants to look at it and can tell me how to get it.
I ran CM7.2 on the same device for quite some time and had no troubles with that. CM10.1 install is from final, wiped both data and cache, no google apps installed yet, no other apps restored, virgin clean :angel: No overclocking, and no other settings changed, no patches.
Thanks,
Andy
Click to expand...
Click to collapse
I can confirm this - I have been experiencing this for a long time now but since nobody else mentioned it I thought it could be just me (although I was doing clean installs). So this problem really exists.
I cannot reproduce this, but I flash the Picassa compatible gallery app - gapps-jb-picasa-20121011-signed.zip - after GAPPS
andy1001 said:
I managed to catch dmesg output right before reboot, attaching it here, there are two files in archive, first is dmesg output before I run gallery, second is dmesg right before it reboots. Logcat and /proc/last_kmsg are also in the archive. I could get more info if anybody wants to look at it and can tell me how to get it.
Click to expand...
Click to collapse
Mmm, that's pretty spectacular -- the system basically runs out of memory and the kernel goes nuts killing things to try to keep the system alive. It looks like the 720p video codec is eating the memory, and I believe we tracked that one down to the same root cause as the Flash issues. Can you try a CM10.1 nightly from June 25 or later (EDIT: or flash the patch in the next post on top of your existing CM10.1 install) and see if the problem still happens? (That reminds me, I promised to respin the binary patch for CM10.1 stable ... I should really do that when I get a minute.)
Patch for 720p codec issues (Flash, video thumbnailing)
As promised, here's the patch fixing Flash, video thumbnailing in the Gallery app, and potentially other 720p video codec issues for the CM10.1 stable release series. (The previous one I posted works as well, but is missing a couple of other potentially useful bugfixes in libstagefright.)
Usage: flash the attached ZIP file over your CM10.1 build from recovery. CM10 users: do not flash this -- use the patch in this post instead. Note that if you're on the CM10.1 nightlies, this patch was merged and should be included in builds starting from June 25.
(Source code: https://github.com/CyanogenMod/android_frameworks_av/tree/cm-10.1.0/media/libstagefright with https://github.com/CyanogenMod/android_frameworks_av/commit/c58721cbdcbfc46f550954a1c258d9b0529e4d81 applied on top.)
steven676 said:
As promised, here's the patch fixing Flash, video thumbnailing in the Gallery app, and potentially other 720p video codec for the CM10.1.0 stable release. (The previous one I posted works as well, but is missing a couple of other potentially useful bugfixes in libstagefright.)
Usage: flash the attached ZIP file over your CM10.1 build from recovery. CM10 users: do not flash this -- use the patch in this post instead. Note that if you're on the CM10.1 nightlies, this patch was merged and should be included in builds starting from June 25.
(Source code: https://github.com/CyanogenMod/android_frameworks_av/tree/cm-10.1.0/media/libstagefright with https://github.com/CyanogenMod/android_frameworks_av/commit/c58721cbdcbfc46f550954a1c258d9b0529e4d81 applied on top.)
Click to expand...
Click to collapse
It is really a damn shame we got that merged just after 10.1 Final was sent to the servers.
steven676 said:
Mmm, that's pretty spectacular -- the system basically runs out of memory and the kernel goes nuts killing things to try to keep the system alive. It looks like the 720p video codec is eating the memory, and I believe we tracked that one down to the same root cause as the Flash issues. Can you try a CM10.1 nightly from June 25 or later (EDIT: or flash the patch in the next post on top of your existing CM10.1 install) and see if the problem still happens? (That reminds me, I promised to respin the binary patch for CM10.1 stable ... I should really do that when I get a minute.)
Click to expand...
Click to collapse
I have tested both cm-10.1-20130627-NIGHTLY-encore.zip and final CM10.1 with your patch libstagefright-omxcodec-patch-for-cm-10.1.0-encore.zip, they both seems to be working OK, I could not make them crash in the same way as unpatched CM10.1 does :victory: Thanks a lot for the fix, much obliged!
Andy
Still having issues with the nook color.
Check the dmesg file for Cm10.1 stable.
Thanks for the patches <steven> Seems to help.
My stable is still holding up good on my NC.
mhzrus said:
Still having issues with the nook color.
Check the dmesg file for Cm10.1 stable.
Click to expand...
Click to collapse
This is what I encounter with Nook Color CM 10.1.2 stable version.
CMUpdater cannot download new Nightly!!!
Battery went flat no indicator.
Wifi issues, network error! For Nothing!
Touch Screen still having issues. The left hand side and right hand side of the screen cannot response to any touches! (About 2 inches thick!)
I come to know that there is issues with Nook Color Touch screen.
http://forum.xda-developers.com/showthread.php?t=1385896
CM10.1.2
A quick heads-up: CM10.1.2 was released last week (check the links in the first post), including important security fixes. (The Flash fix didn't go in and looks unlikely to go into the 10.1 stable series at this point -- you'll have to continue flashing the patch above for now.)
cm-10.1.2-encore stable vs nightly - Patch for 720p codec issues?
steven676 said:
A quick heads-up: CM10.1.2 was released last week (check the links in the first post), including important security fixes. (The Flash fix didn't go in and looks unlikely to go into the 10.1 stable series at this point -- you'll have to continue flashing the patch above for now.)
Click to expand...
Click to collapse
Thanks for that info steven676; so that patch will work for cm-10.1.2-encore stable?
What's the easiest way to tell if the patch is or isn't working on my NC?
Lastly, is it necessary or included with any of latests cm-10.1.2-encore nightlies?
:good:
eltrkbrd said:
Thanks for that info steven676; so that patch will work for cm-10.1.2-encore stable?
Click to expand...
Click to collapse
Yes, it'll work for CM 10.1.2 stable (or any other CM10.1 release).
eltrkbrd said:
What's the easiest way to tell if the patch is or isn't working on my NC?
Click to expand...
Click to collapse
Install Flash, enable plugins in the browser, then open Flash Player Settings -- if the bug is still present, the page will lock up and you'll eventually be prompted to kill the tab.
eltrkbrd said:
Lastly, is it necessary or included with any of latests cm-10.1.2-encore nightlies?
Click to expand...
Click to collapse
As noted in the post with the patch, the fix should be included in CM10.1 nightlies starting with the June 25 build.
I posted this originally in the E973 forum, but there's no traffic there anymore...
Yet another unofficial Cyanogenmod 11 ROM, this one with working LEDs for Canadian phones.
Sources are mostly chadouming's with haze028's device repo. LED driver is courtesy of paulicat. I've also included an init.d script by paulicat to tweak some governor/audio/video settings.
thanks to mathsz for his support, paulicat for his LED driver, chadouming for his repo's, houstonn for his modified frequency tables and haze for his putting up with my dumb questions.
Sources are here: link
Latest ROM will be on my androidfilehost
I personally use PA stock gapps with the banks camera addon.
I'll try to update this semi-regularly, I'm not a coder but I'll try and fix any bugs that are found.
I know the official nightlies are out, but I'm not happy with them, so here ya go!
CHANGELOG:
12/19/2013 - latest build added 192 MHz min CPU frequency, torch FC's fixed.
12/31/2013 - lockscreen HW button customization is working
01/02/2014 - reverted to stock frequency tables, was seeing some soft reboots on my phone.
01/04/2014 - made a few additional kernel tweaks for stability (explicitly disable modules and gpu overclock), equivalent of M2 build.
01/05/2014 - cherry picked commit for status bar settings, as well as lockscreen hw buttons. At this point, this should have feature parity with any 10.2 build (I think). This build seems to be rock solid stable and snappy.
01/09/2014 - Increase default voltages to be identical to stock, removed a kernel tweak for increased bus speed. Stability is more important than benchmark performance to me. Anyway, very stable now and CM seems to be adding in features/bringing up stuff from 10.2 pretty quickly. I've still just added the HW button cherry pick and everything is working as intended. Give it a try, especially for E971/3.
03/27/2014 - Back to building for geeb... kernel is updated with a lot of linaro patches, ROM and kernel are now built with linaro 4.8 toolchain. Low cpuclocks (162 MHz minimum frequency). I haven't enabled any overclock, but everything is smooth and battery seems to be excellent, at least for my use case. Enjoy!
04/22/2014 - new build is up on androidfilehost, new kernel (thanks mathsz and brothaedhung!) - it's a pretty straight up port from faux's latest with some cherry-picks for battery. low cpu clocks are enabled and battery is amazing. the bootimage blanks out partway through boot, but other than that it's really good. I included the nav bar/hard key disable from official cm, and google camera works perfect
05/28/2014 - So, I've been running builds, but haven't been updating the OP... Anyway, I've got a new kernel and the 0528 build is based on the latest changes to stable/cm-11.0 branch. It's M6 but with any commits CM has made recently, since they're still updating their github apparently. Kernel has fast charge, voltage control, battery life extender, low clocks, sound control. Governor is defaulted to ondemand, scheduler is noop, and hotplug is Qualcomm's mpdecision daemon. You should see battery life in excess of 4 hours SOT, depending on gapps package (I use PA stock, and get 4 hours no problem). Kernel is based on paulicat's port of the google stock kernel. No other frills in the kernel, no intellidemand, intellithermal, intelli*
This one is my DD, it's stable and everything works as intended.
06/22/2014 - Up to 4.4.4, latest nightly is in CM-11.0/Nightlies folder on androidfilehost.
06/30/2014 - Latest nightly has a fix for linaro 4.8 and ART, ART now works fine on this ROM. Battery life is amazing.
07/01/2014 - CM updated the stable/cm-11.0 branch today, so I did a build. ROM is up on androidfilehost, under CM-11.0/Milestones. I updated the kernel with the latest commits from CM as well.
07/08/2014 - Updated based on latest stable/cm-11.0 branch commits.
07/13 - CM keeps updating the stable branch, so I keep cranking out builds
07/15 - The most recent ROM has working storage encryption thanks to a commit by shelnutt. I've also uploaded a flashable zip of the kernel I use for this ROM here
10/07 - New build based off stable/cm-11.0 branch is up. Very stable and smooth so far.
CM-12.0
I've started building unofficial geeb CM-12 builds. They're up on androidfilehost. Starting this coming week, I'll be posting builds with my own kernel, brought up from kitkat. The builds that are currently posted are using a modified version of brothaedhungs lp kernel.
02/03/2015 - Sorry guys, I've been slacking off on updating this post. All current builds are using my KK kernel brought up for LP, with stock frequencies instead of low_cpuclocks. I'll be posting a new build later this morning. As far as I know, this is the only CM build still using mako sources.
02/26/2015 - New build. CM resync.
03/03/2015 - New build. I hacked up sepolicy to allow init.d scripts access to sysfs, and all of my custom tweaks are working. I also cherry picked "launch default music player when headphones connected". Also CM resync.
CM-12.1
04/16/2015 - Started building CM-12.1, using updated mako device and vendor tree.
04/20/2015 - cm re-sync, added some fixes to kernel and device (from cm)
04/23/2015 - posted 04/22 build. cm re-sync, updated to 5.1.1
r.asimi said:
So I see there's a few downloads, but no comments in-thread. I hope that means everything is working well for you guys!
Just a heads up, there's a commit on cyanogenmod's gerrit for hardware buttons on the lockscreen. I'm going to cherry pick it and upload a new build for 12/31 as a New Year's Eve present for everyone!
Click to expand...
Click to collapse
Didn't see this thread, but sometimes a quiet one can mean they have no issues haha. Also Happy New Year to you too!
Sent from my LG Optimus G
Torch issue might be a f up in my device overlay, running a new build and will upload shortly. Torch tile is also missing and I found a commit from shelnutt that *should* fix it.
r.asimi said:
I posted this originally in the E973 forum, but there's no traffic there anymore...
Yet another unofficial Cyanogenmod 11 ROM, this one with working LEDs for Canadian phones.
Sources are mostly chadouming's with haze028's device repo. LED driver is courtesy of paulicat. I've also included an init.d script by paulicat to tweak some governor/audio/video settings.
thanks to mathsz for his support, paulicat for his LED driver, chadouming for his repo's, houstonn for his modified frequency tables and haze for his putting up with my dumb questions.
Sources are here: link
Latest ROM will be on my androidfilehost
I personally use PA stock gapps with the banks camera addon.
I'll try to update this semi-regularly, I'm not a coder but I'll try and fix any bugs that are found.
I know the official nightlies are out, but I'm not happy with them, so here ya go!
CHANGELOG:
12/19/2013 - latest build added 192 MHz min CPU frequency, torch FC's fixed.
12/31/2013 - lockscreen HW button customization is in, but for some reason no option for torch (the reason I cherry picked in the first place)
Click to expand...
Click to collapse
12/31/2013 - fixed the torch issue, torch tile and HW lock screen button is working. Build is uploading now (14:18 EST) and should be done shortly.
Running 31st rom.. Rock solid and stable!! Great battery life and working LEDs!! Awesome job! Thank you and happy new years!
Sent from my Optimus G e973
Who says the LG devices don't have huge choices. ?? Here's one more reason to negate that statement. Thank you , for this rom. Now , we have one more to choose from.
Happy New year.
Hey guys, I just wanted to post an update in-thread. There is a battery drain issue with PA gapps, so what I've been doing personally is flashing the ROM, flashing the PA stock gapps, then flashing banks standard gapps overtop, then flashing the banks camera addon. It's annoying, but it fixes the battery drain.
Also, I f'ed up the 01/02 build by including some stuff in the 99kerneltweaks file in init.d, the problems aren't going to keep you from running the ROM but it makes the min frequency kind of random. I've attached my current 99kerneltweaks, and will include it in builds from now on. Remove the .txt extension, I had to add it because otherwise the forum wouldn't let me upload it.
Removing the 192 MHz setting from the kernel has resolved the soft reboots I was getting, and doesn't seem to impact battery life very much, I was getting way more drain from the PA gapps issue.
Just a heads up for anyone using my ROM, CM merged a lot of features from CM 10.x back in this morning. I'm running a new build now and will post it later today/this evening.
I hope this is a small request, but is it possible to have a flashable version of your kernel?
Mainly because your kernel fixes my problem with wifi tethering on CM11.
btw, love the rom. seems to be more stable than the official nightlies.
sucsss said:
I hope this is a small request, but is it possible to have a flashable version of your kernel?
Mainly because your kernel fixes my problem with wifi tethering on CM11.
btw, love the rom. seems to be more stable than the official nightlies.
Click to expand...
Click to collapse
I'll try and make a zip for you tonight.
I just uploaded a nightly with most of the 10.2 features merged back in. There is a bug w/ emulated storage, after Koush merged in an updated superuser the CM file manager won't see /storage/emulated/0 in root mode. The workaround is to set CM file manager to prompt mode, and then you'll never even see an issue. /storage/emulated/legacy is available in root mode, though I don't know why you'd need root for your internal storage. I think it's an SELinux/zygote conflict but I haven't figured out the fix just yet.
There's a new build up - 20140123, which has a fix for autofocus. I need anyone running it to keep an eye on battery drain and let me know if they see anything out of the usual... I'm running it myself and haven't seen any problem so far, but there's one report of an issue with the patch on geeb.
Thanks!
everything works great!
Thank you very much!
I would like that kernel too please
connect phone to USB. Start adb. Put device in bootloader. Fastboot flash boot. Boot.img
Sent from my Geeb using Tapatalk
I've uploaded a flashable kernel zip to my androidfilehost. Please keep in mind, it's just the zimage, no ramdisk or drivers so LEDs etc will not work the same.
Battery life is still great.
The only minor issue I see is the ambient light sensor dies after awhile. This is the same with official cm11 and the PA 4.0 releases. Not a big issue but it's interesting that it's across 3 roms.
mathsz said:
connect phone to USB. Start adb. Put device in bootloader. Fastboot flash boot. Boot.img
Sent from my Geeb using Tapatalk
Click to expand...
Click to collapse
I'm retarded. I forgot that you can easily do this.
sucsss said:
I'm retarded. I forgot that you can easily do this.
Click to expand...
Click to collapse
nah, it's easy to forget. Unless you play with roms all the time, play in the source a bit or are just flash-happy, it's realllllly easy to forget.
FPBug: Meet the very first stable kernel for the Galaxy S2 i9100, S2 AT&T i777, S2 Epic 4G Touch d710 and Note n7000 since Gingerbread days
Every single Android 4.x kernel for these devices has had a serious bug (FPBug) that randomly corrupts the state of processes, starting with Samsungs's stock ICS and JB and spanning every custom kernel out there newer than Gingerbread.
STATS: 500+ kernel downloads in 2 days, wow!
RELATED: Make sure you check out my TRIM-enabled kernels updated with the FPBug fix.
UPDATE: A fix for FPBug has been merged into CyanogenMod's cm-11.0 branch! The fix has not made it to the stable/cm-11.0 and cm-12.0 branches yet. Changes: this one and the previous 12. Commits: this one and the previous 12. The 20150111 nightlies are the first official CM 11 nightlies to incorporate the fix.
A little bit of history
As Android got more complex, the effects of this bug grew more visible, to the point of making the platform completely unstable for some users. Complex apps would fail for no reason, GSM, 3G and WiFi connectivity would randomly be lost, music playback would stop and require a reboot, camera would fail, internal storage and SD cards would become inaccessible, installed apps would disappear, users would experience battery drain issues ranging from inability to enter deep sleep all the way to phones becoming very hot, and the list goes on and on.
These failures all seemed unrelated and their cause was very hard to track down. Partly because events happened randomly and were not reproducible, but mostly because the bug undermines the very assumptions programmers deal with when creating any kind of code. And so years passed and the common cause of all this pain was never identified. Many ROM developers abandoned the platform out of frustration.
Then finally this past March, when analyzing the random loss of access to storage, user cgx observed a corruption event for the first time, and a connection between all these unrelated issues, sometimes hypothesized, was suddenly found. The corruption seemed to have happened in the stack, but it was later suspected then confirmed that the corruption actually happened directly in the registers of the floating point unit of the CPU. Yet processes that did not use floating point at all were also affected, because the GCC compiler typically spills registers into the FPU and uses FP and NEON instructions for optimization.
These findings allowed the creation of a stopgap fix for the "music bug" that shielded the FUSE process (which manages access to storage) from corruption in the FPU. The fix was widely applied and effectively eliminated all bugs resulting from sudden loss of storage access and returned the platform to pre-Android 4.3 stability levels: ie, sort of stable enough to be used as a daily driver. Later a working detector for the elusive bug was made and it was confirmed that all kernels since Gingerbread were affected (a thing that was already suspected given that the FirefoxOS people had described similar symptoms in 2012 under stock Samsung ICS). Finally enough of a root cause was hypothesized and a fix was worked out. And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
A short description of what the fix does can be found here.
Update
User zeitferne worked non-stop throughout this weekend and made amazing progress. He found a couple of missing commits that are apparently needed for the FPU state tracking to work through power state changes, he discovered that the FPU in CPU0 is the one that actually gets the corruption, he found an explanation why this bug never affected the 4412 platform (Galaxy S3, Note 2, etc), he narrowed down the conditions for the corruption, and finally output an alternative patchset that apparently fixes the FPU state restore optimization rather than just disabling it as mine does.
Kernel developers are encouraged to merge his changes in lieu of mine once enough testing is done and @zeitferne green-lights the patches. This is important as it might fix as-of-yet undetected bugs or prevent bugs arising from future changes. In the meantime, eager maintainers can merge my fix which is by now well tested. Users will only see a small (<< 1% ?) performance increase with zeitferne's patchset and don't really need to bother with this; my advice for them would be to wait for the changes to trickle into their kernel of choice. AMAZING JOB ZEI!!!
2nd UPDATE: @zeitferne has green-lit his patchset! Kernel maintainers merging it please take note: 1) Make sure my fix is removed before applying his, otherwise there will be a small performance hit in the resulting kernel. 2) Both our fixes also affect the 4412 platform (i9300, n7100, etc) in slightly different ways, and the effects of this have not been properly tested. I must recommend that some testing be done before distributing FPBug-fixed 4412 kernels. Please report your test results back to this thread.
WARNING: A problem was reported with zeitferne's patchset.
FOLLOW UP: @zeitferne made some changes to his patchset and initial testing looks good.
AND FINALLY: The patchset was merged into cm-11.0! (See this change and the 12 previous ones.)
Downloads
You will find kernels for various CyanogenMod releases, M-snapshots and nightlies here. These kernels are guaranteed to work only with the exact matching version of CM specified in the last part of their filenames. But in reality they should work with most versions of CM that are close enough. (Don't ask me about this, I don't know, I don't even have any of these phones! Just try them and see for yourself if you are feeling a little adventurous.) For other ROMs i expect this fix to be merged in a matter of days after some more testing is done. Please be patient, and KitKat users can flash my music bug fix in the meantime.
FAQ
Q. I have flashed your music bug fix in the past. Can I flash your kernel?
A. Yes! The music bug fix has no downsides. In fact, as a side effect, that fix makes your phone slightly faster and saves some battery so it should be merged in all ROMs IMHO. If you already have it installed leave it in place, but do not flash it again the next time you upgrade the OS. Please do not flash it just for the sake of optimization: since it is based on CM11 M10, it would actually be a downgrade.
XDA:DevDB Information
FPBug-i9100, Kernel for the Samsung Galaxy S II
Contributors
Lanchon
Source Code: https://www.androidfilehost.com/?w=files&flid=22853
Kernel Special Features:
Version Information
Status: Testing
Created 2014-12-19
Last Updated 2015-01-14
(reserved)
Is the BLN included ?
Lanchon said:
And if this were not good enough news, user Entropy512, the exynos platform hero who saved us all from brickbug, has hinted that official Lollipop from Omni is now a possibility.
Click to expand...
Click to collapse
It's not about i9100 ? Right ?
Can't wait till testing is complete and you merge the fix into your trim kernel for the i9100 lanchon. Thanks to all the programmers, testers and commenters in the bug thread for their hard work.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
yes, he refers to the i9100 and the n7000
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
these are all standard CM kernels. please request features on the CM thread.
Lanchon said:
yes, he refers to the i9100 and the n7000
Click to expand...
Click to collapse
Oh God ! Lollipop
I am anxious
@Lanchon thank you very much for ur hard work [emoji122] [emoji122] [emoji108]
Dammit... Never wanted to use CM again... I think I will have to at least for now until it gets integrated in other kernels
Great Job @Lanchon
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
so no bad battery life any more?
Vidura Dissanayake said:
so no bad battery life any more?
Click to expand...
Click to collapse
Yes exactly. With a little more testing a final version should be coming soon. What an awesome Christmas gift!
Thindboy said:
i never had any GPS problems on my i9100 before ICS. Since JB it has gotten sooooo much worse. I tried atleast 20 different ROMs (JB, KK) and 5 different Navigation Apps. Nothing helps. Currently i am on CM11 M12 Snapshot. Still not better...
Could this kernel also help me with the GPS Problem??
Click to expand...
Click to collapse
No it won't solve gps problems. I've had good luck using GPS status https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2 and Faster GPS https://play.google.com/store/apps/details?id=org.fastergps from the Google play store. GPS status will download assistance data (A-GPS) and faster GPS setups the proper ntp server for your area. I get fixes in about 10 seconds now.
Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
Everything is somehow faster with this kernel. I flashed the music bug fix with this kernel. Waiting for trim kernel, it will further accelerate the phone.
I noticed that the phone is not heated as before.
You're a genius because you've done a lot for us, s2 community ... And we know that you do not own this legendary phone
Thank you @Lanchon
Sent from my GT-I9100 using Tapatalk
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
DarkJohn said:
Is the BLN included ?
It's not about i9100 ? Right ?
Click to expand...
Click to collapse
Cm12 is available?
Alucard said:
I dont understand does this feature going to be added to cm11 or do i have to flash a zip to add it?
Click to expand...
Click to collapse
Waiting for your review for Spirit ROM once you've flashed it.
Lanchon said:
im not part of the cm team and my crystal ball is acting up lately so i cant answer Q1.
this is a kernel, you need to flash it. please read the downloads section.
Click to expand...
Click to collapse
OK so FPBug-V1-src.zip is a flashable zip for fpbug fix for every rom stock jb and kk?And cm-11-M10-i9100-music-bug-fix.zip is for cm11 m10 only?
---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------
x3dnd3x said:
Waiting for your review for Spirit ROM once you've flashed it.
Click to expand...
Click to collapse
Im on neatrom now ,will be on kk once a stable kk apolo kernel comes out!
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Mockingbird said:
What recovery does this kernel has built in? I use 11.15 cm11 custom build my markox and I want to mare sure that I can reflash the rom in a recovery if it screws up. I never used Odin since I got this phone.
Click to expand...
Click to collapse
Lanchon bases his kernel on stock cm kernel, so cwm recovery is built in.
** Note: This kernel is end-of-life and will no more be maintained. There will be no LineageOS 15.1 or newer kernel be available anymore **
Hi all,
some of you know me from the Samsung devices area, where I provide my kernels already for more than two years to Galaxy S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.).
Maybe you also know me from my OnePlus One kernels I added in winter last year to my portfolio.
Finally I got a Samsung Galaxy S5 afew weeks ago and decided to port my kernel also to this device. This is a sponsored device, so I want to say a big thank you to the people that made it possible, namely the ones in the German Smartphone Forum www.hubo.in !!!
Please note:
I am not heading to have as many features as possible implemented, this is not my design goal. If you are more into that, move on to other, good existing kernels. If you are searching for a good mix of improvements and new functions while not sacrificing stability, you are welcome here (see below the history section for more info).
For the Samsung Stock Boeffla-Kernel, please go HERE.
Important notes
When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
Compatibility
Important: This kernel is only meant to be compatible with official LineageOS/Cyanogenmod and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app.
Click here to learn about using the config app.
I will refuse to give support if you do any undervolting and experience freezes or hot reboots.
I will also not provide any support if you do not use Boeffla-Config app to tweak the kernel, other 3rd party tweaking apps are known (and intended) to cause issues.
I will refuse to give support if you have xposed framework installed and reporting any kind of weird issues. My opinion to xposed it quite clear: too powerful for >90% of the users that just mess up their system with it.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for CM14 kernels: CLICK HERE
Change log for CM13 kernels: CLICK HERE
Change log for CM12 kernels: CLICK HERE
Change log for CM11 kernels: CLICK HERE
Features
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Additional governors: zzmoove (Note: not considered stable at the moment, you might face reboots!!!), intelliactive, intellidemand, wheatley, smartmax, slim, intellimm, nightmare, lionheart, pegasusq
Zzmoove supporting native hotplugging profiles
Additional schedulers: fiops, bfq, sio, tripndroid, zen
Many Hotplug tweak profiles (Default, Optimized, 1 core max, 2 cores max, 3 cores max, 2 cores min, 3 cores min, 4 cores min, 2 cores exact, 3 cores exact)
Wake up gestures implemented (double-tap-to-wake, swipe to wake)
Boeffla-Sound engine (Headphones and speaker volume configurable)
Configurable vnswap
True dynamic FSync (activated if screen on, deactived if screen off), configurable
Touch boost frequency configurable, touch boost switch (all boosts removed by Lineage team in December 2016)
CPU Overclocking up to 2.84 GHz
CPU Voltages interface for undervolting/overvolting
GPU idle frequency 27 Mhz added
GPU governor selection support
Show GPU frequency usage per frequency in Boeffla-Config
Color control to adjust RGB color space + inverted mode
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (default to on, can be disabled)
System Tweaks predefined supported (default is off)
Android logger (logcat) configurable
Kernel logger (dmesg) configurable
Charge rates for AC charger, USB and wireless charging separately configurable (set charge rate to 0 to have stock charge logic back)
Charge information display support via Boeffla-Config V2 app
CIFS support (module, do not mount inside /data)
NFS support (module)
NTFS support (module)
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Swap supported (but not recommended, use zRam instead)
init.d support (in /system/etc/init.d - set correct permissions!)
Default entropies increased
Insecure kernel (adb has root privileges)
Automatic EFS backup
Kernel survival mode by Boeffla-Config app to survive CM rom flashes
Full support for mpdecision for best compatibility and smoothness
(Important: use Boeffla-Config to configure min/max CPU frequencies + governors + schedulers only - or explicitely allow other apps/processes to overwrite this in Boeffla-Config settings, but expect weird side effects)
Integrated full busybox 1.23.1 (own compilation)
Auto-Root by kernel possible by request, not recommended for CM however (latest su included)
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Presets supported in Boeffla-Config by kernel (Extreme power, power, normal, battery friendly and battery saving)
Google gcc 4.8 toolchain used for best stability
Always using latest Initramfs
Always based on latest Galaxy S5 sm-g900f kernel sources by CM
Kernel runs with SELinux enforcing by default, just as CM12 stock kernel for S5 - but can be configured to work in permissive mode in Boeffla-Config settings
Note: I do NOT upstream the kernel to higher Linux kernel versions anymore as this usually has zero benefit but likely introduces new issues + is a waste of effort in the end
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
History and design targets
Basically I created my first Boeffla-Kernel in 2012 as there was no kernel for the Samsung Galaxy S3 around that had exactly the mix of functionalities that I wanted. I wanted to have full flexibility in undervolting and charge rates for instance, but did not like the sharpness and/or brightness tweaks many kernels have implemented as per default.
Hence, I began to create my own kernel after a while, adding all the features I like. This is the result of my work, which in the end I decided to share with you. I hope you like it as much as I do.
The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. Also it does not aim to have the broadest feature set available everywhere.
It aims more for a good mix of all, not sacrificing stability and functionality in the end.
And - most important: It aims to stay quite close to stock !!!
These design targets are also valid for the Galaxy S5 kernel here!!!
This said, I will definitely NEVER implement:
things I do personally not need
things I do not like
things that are in any way dangerous
anything which is highly experimental
f2fs - it is known to cause various issues and compatibility problems
a CAF based kernel
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it if it falls into the listed categories. Everything else I am happy to check and decide.
And: I do not really care about benchmark numbers, they say almost nothing as long as something is not completely wrong. Important for me is the feel-good factor.
I am also not interested in gaming at all, so never expect a gamer kernel. It will just not happen...
Compatibility
To reiterate it again: Flash the correct kernel depending on whether you are on Samsung Stock, CM12 or CM11 !!!
Configuration of the kernel
To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from the downloads section on www.boeffla.de.
You need at least version 2.1.72 or higher for the Galaxy S5 Boeffla Kernels.
Donation
If you like my work, feel free to donate: Donation-Link
If you donate at least 2,49 EUR (to be in line with the donation app prices on Google Play store), you will receive a personal donation code which unlocks some nice little comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Github repository: http://github.com/andip71
Credits to developers
Of course, I had never been able to create all that by my own. So I want to give credits to the really good developers around, that have given me all the inspiration and from which I cherry picked lots of the implemented functionalities:
* ZaneZam
* Yank555
* ktoonsez
* Hardcore
* Chainfire
* AndreiLux
* Netarchy
* Gokhanmoral
* Entropy512
* Faux
* Ak
... I just hope I did not forget someone. If so, please let me know and I will add you of course.
Thanks to all of you for your great work !!!
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in your custom recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi
Latest change logs:
LineageOS 14.1
http://kernel.boeffla.de/sgs5/boeffla-kernel-cm/cm14.0/changelog.htm
CM13.0
http://kernel.boeffla.de/sgs5/boeffla-kernel-cm/cm13.0/changelog.htm
Configuration and profile thread
http://forum.xda-developers.com/galaxy-s5/general/unofficial-boeffla-kernel-profile-t3139530
*** You want my support? Then stick to my rules ***
Guys, I am receiving more and more completely useless support requests in different threads. Useless because people provide nothing to be able to help, not even the minimal possible information they could give.
Hence, I will now remind anyone again on the support guide lines stated here:
http://boeffla.de/index.php/support/support
Also you need to ensure you follow the installation guide lines incl. trouble-shooting stated here:
http://boeffla.de/index.php/support/installation-how-to
And to cut a long story short: If you do not at least provide what I request in the support guide lines, I will IGNORE YOUR REQUESTS IN FUTURE.
Straight and simple. I have enough of people wasting my time just because they are too lazy to write details.
Period.
Also as a reminder:
you use xposed? -> no support, everything is your own issue
you use a custom rom and not the official stock or CM one? -> good luck, you are on your own
you undervolt or overclock? -> have fun, but without my support
Sorry, this might sound harsh (and it is meant to sound harsh), but you cannot imagine about how crappy support requests can be. Stating something does not work is just not enough.
Please consider that!!!
Andi
Hi all,
Great kernel
Works very fine
Check this out..
Thanxxxx to the Lord for the hard work in the last week's
Now i love my S5 G900F
[emoji7]
Ive installed on Teamsek CM12 v9.0 and geting self reboot ...
Im waiting for new ver. Always big fan of your krenels
gravis_jg said:
Ive installed on Teamsek CM12 v9.0 and geting self reboot ...
Im waiting for new ver. Always big fan of your krenels
Click to expand...
Click to collapse
Cannot comment for Temasek, as written.. it is for official CM12. And it is only tested by me with official CM12.
If it runs with Temasek - fine. If not, you need to search why it reboots for you. Then Temasek seems not 100% compatible.
Andi
Flashed fine on AICP.
Only heard good things about your kernel!
superleeds27 said:
Flashed fine on AICP.
Only heard good things about your kernel!
Click to expand...
Click to collapse
Thanks.
But also let's be realistic. It is version 1.0-beta1. So for sure some more way to go
Andi
@Lord Boeffla
Hi Andi, a big neverending thanks for providing us with an S5 (G900F/klte) kernel.
Coming from my i9300 which ran the whole time with your wellknown and imho best kernel for the i9300 I am familiar with your fine app and highly appreciate your new work for the S5.
And btw: Due to so far not working TRDS for LP/cm12 I still run kitkat for s5 (same with my i9300) using FusionRom which is mostly based on cm11.
Now with Boeffla-cm11 for G900F based on FusionRom 4.4.4 I feel happy again - fast-stable-easy to handle 1A+++
gravis_jg said:
Ive installed on Teamsek CM12 v9.0 and geting self reboot ...
Im waiting for new ver. Always big fan of your krenels
Click to expand...
Click to collapse
Quick question: Are you coming from another custom kernel?
It might be, some cleanup work is required first.
Just had a user that came from KT kernel and he had to deinstall the two KT apps manually, wipe dalvik and cache. Then it started working.
Andi
CM12 kernel seems to work fine on bliss-pop. At least so far. ?
vulfgar said:
CM12 kernel seems to work fine on bliss-pop. At least so far. ?
Click to expand...
Click to collapse
Fingers crossed it will stay like that
Andi
Lord Boeffla said:
Fingers crossed it will stay like that
Andi
Click to expand...
Click to collapse
Me too. If not I'll have to change rom.
Lord Boeffla said:
Fingers crossed it will stay like that
Andi
Click to expand...
Click to collapse
Just to be tested, my friend thanks for everything
Lord Boeffla said:
Quick question: Are you coming from another custom kernel?
It might be, some cleanup work is required first.
Just had a user that came from KT kernel and he had to deinstall the two KT apps manually, wipe dalvik and cache. Then it started working.
Andi
Click to expand...
Click to collapse
I was the user
You must delete in root/system/app/com.ktoonsez.KTmonitor.apk and com.ktoonsez.KTweaker.apk.
Additionally, in Int SDcard the KTKernel Folder with profiles and scripts.
First, install the Boeffla Config, then go into recovery and flash the kernel. Wipe cash and Dalvik and reboot.
For Viper4android user, first deactivate Viper4Android or use the Beoffla Kernel without Boeffla sound settings.
Sorry for my bad English, with this kernel for lollipop tw viper4android work or not? Now i have flashed this kernel and boeffla apk
gravis_jg said:
Ive installed on Teamsek CM12 v9.0 and geting self reboot ...
Im waiting for new ver. Always big fan of your krenels
Click to expand...
Click to collapse
Hi, I've tested the kernel on Temasek and on a few different Rome.
Bliss Pop Rome, Fusion, Darko ... CM12 unofficial
It's like Horsti G says everything must be deleted from the kernel KT otherwise there are problems. but I have only the KT monitor at run without problems
Especially on the Temasek Rome had 2 people tested the kernel for quite some time without any problems.
Unfortunately the support for other roms is not possible because there are always errors and differences with other roms.
a Idde would make a thread for all other roms. since one could then afford support?
@ cranio84
For Viper4android user, first deactivate Viper4Android or use the Beoffla Kernel without Boeffla sound settings.
sorry for the translation with the googel translator
kind regards
Jakkomo 77
Ok i deactive boeffla sound setting, but where is a guide to install viper4android, because I have tried with more kernel on tw rom and don't work
For sure there are specialised threads for viper4android.
But wrong in this thread to discuss that...
Andi
Ok, i discute un this 3d because your kernel is correlate for me
About SoilWork
SoilWork is a mod created by @RogerF81, originally for the HTC 10, which features a Snapdragon 820. I've ported this mod to work with both OnePlus 3 and 3T devices. While the mod keeps the same name, the scripts used have been modified to best adapt to our devices! All the tweaks used in these scripts are made to work on any android and kernel version. If you are using an HMP kernel or an EAS one, there is no problem, as SoilWork will do the job of identifying your kernel and applying the tweaks accordingly.
Check out RogerF81's original thread here.
How to install/use this mod
If you use any of the Magisk modules provided in the download section, you just need to flash it in TWRP or in Magisk Manager and reboot. All the setting will be applied 30s after boot, to prevent any possible interference. Boosters Disabler is the only one which will run 45s after boot to prevent interference with the other profiles. (They can be installed alongside!)
If you want to use the .sh file provided in the download section, you can simply run it in a terminal emulator with these three simple lines:
Code:
su
cd /path/to/file.sh
sh *name of file*.sh
If you use the terminal method, rename the script, as parentheses aren't recognized from the terminal, use backslashes or the tab button combination (Vol+ and T) to complete the name of the script, which will also correct the name before you make it run. This is an error which won't be needed in the next update as the scripts will have a different name. Guess what? Fixed it.
Alternatively, use any other app which can run the script as root. At every reboot, however, the tweaked tunables will reset to the default values. The scripts already have a sleep time of 30 seconds (45 for Boosters Disabler), so it's not needed to add one. If you, by any means, remove it, please add from the app's settings a delay of at least 30 seconds in order for everything to work as it should.
If you're using a script manager app, as EXKM, please note that these apps seem to have problems in reading large files. Even if the file size has been reduced from the previous release, these apps may have these problems anyway. If that's the case, copy and paste the script to a new file created within the app.
Note: The script will not print anything on the console (it'll print grep checks) or output any file (as the previous versions) this is because all the scripts have been checked and are known to run without problems. If you still want to check if the script runs correctly, check the output from the app you are using to run the script (Magisk users run the script as stated above), since the console will output error messages (if any)
Note for Magisk users: The latest module is compatible with Magisk v15.0. Older versions are not supported anymore and are most likely to be moved to a folder tagged "OLD" in my AFH's Magisk folder.
Known bugs
Some Oreo ROMs seem to not react well under the battery profile (Cardinal Xtended seems to be excluded from this issue)
Available profiles (more to come)
Battery: Enhanches battery life without ruining user experience. It ruins your experience anyway? Try Battery LightWeight!
Battery LW: Also known as Battery LightWeight, this profile is the same as the Battery one, but has less impact than its predecessor.
Balanced: Gives a balanced experience between performance and battery.
Boosters Disabler: Disables any kind of CPU boosters in your kernel (Vox Populi, Input Boost, CPU Boost).
Downloads
MEGA | GDrive
AFH Main Directory
├ Magisk 13.x directory
└ Magisk 14.0 directory
Since AFH doesn't support the sh file extension, the scripts will only be available with GDrive or MEGA.
I'll use AFH as a repository - check it out if you want an older zip. If you search for an older script, just download any of the magisk zip and extract the script under /common/service.sh and you'll get the script.
Changelog
Battery profile
HTML:
v2.0
-Cleaned and fastened the script
-Added smartmax governor as a suggestion of a good tester
Battery LW profile
HTML:
v2.0
-Initial release
-Not bad for a version jump, uh?
Balanced profile
HTML:
v2.0
-Same as battery for this version
Boosters Disabler add-on
HTML:
v2.0
-The only change is the version number. Maybe.
Old changelogs
Battery profile
HTML:
v1.4
- Tweaked some EAS values
- Deadline over noop if maple is not present
v1.4.1 (will still show as 1.4)
- Fixed an error in the code
v1.3:
- Fixed flash problem via TWRP
- Fixed version
- Implemented more tweaks for EAS kernels (HMP too, but little was done)
v1.2:
- Optimised integration with blu_spark kernel
- Squashed some bugs
v1.1:
- Fixed tweaks which caused the device to stutter
- Optimised some tweaks to make the profile even more battery friendly
v1.0:
- Initial release (unavailable)
Balanced profile
HTML:
v1.4
- Tweaked some EAS values - more battery, same performance
- Fixed a GPU code-related problem
v1.3:
- Fixed flash problem via TWRP
- Fixed version
- Implemented more tweaks for EAS kernels (HMP too, but little was done)
v1.2:
- Optimised integration with blu_spark kernel
- Squashed some bugs
v1.1:
- Fixed an error in the code which made GPU values to not apply on OP3
- Optimised some tweaks to make the profile more balanced
v1.0
- Initial release (unavailable)
Boosters Disabler
HTML:
v1.0:
- Initial release
Credits
@RogerF81 for the original script and idea
@joshuous and @RenderBroken for their help with kernel related questions
@boyd95 and @ZeroKool76 for trying the script out before the release
@soniCron @Alcolawl @Freak07 @Asiier
@Mostafa Wael @patalao @Senthil360 @TotallyAnxious @Eliminater74
@ZeroInfinity @Kyuubi10 @ivicask @DeeZZ_NuuZZ
ROMs which include SoilWork (or any of it)
ZeNiTy [EAS] since 30.09.17 build - Thanks to @ZeNiXxX and @SKULSHADY for the inclusion and for their awesome work! Check out the full post here.
Version info
Version: 2.0
Status: stable
Date of creation: 20/09/2017
Date of last update: 29/12/2017
Note for the developers of custom ROMs: Yes, you can use my script in your ROM, but give credits and PM me so I can add your ROM in this OP.
Are you wondering which profile to use? Seek answers no more, here's a detailed (?) insight of them!
Battery: This profile is excellent if you're using Nougat. No one is experiencing lags on Nougat because of this profile, and if anyone is, the wrong kernel is being used (check at the end of the post). The tweaks in this profile tweak almost everything regarding your CPU's governor. Another module (the one below) has been made for you if you don't like this approach (but don't expect the same results). On Oreo, there seems to be a problem, for now, as many kernels doesn't seem to tolerate the tweaks it does. On some ROMs there are no problems, in some there are. Try it yourself and let me know how it goes. If you are experiencing lag on Oreo, please try the module which is described below before posting known issues.
Battery LW: This profile, which full name is "Battery LightWeight" has seen light because the impact on Oreo and some kernels seemed too much. This won't tweak the same amount of things as the one described before, and seems to run better than the Battery profile on Oreo. As for Nougat, consider using this module if you're experiencing lags. This module is also for everyone which runs a kernel with enhanced battery features (see the end of the post). Even if it has been tested on a couple of them, please do note that it's not easy to cover them all. If you're experiencing problems, revert to stock settings.
Balanced: This profile is for everyone who wants some battery tweaks but doesn't want to slow down the phone by any means. On Oreo it doesn't seem to have any problems like the Battery profile has, but it's still a beta on Oreo. On Nougat, it runs smoothly. Use this profile if you want a balanced experience between performance and battery saving options.
Boosters Disabler: This profile is for who wants even more battery. Do you feel like CPU boosters aren't needed in your setup? Use this profile.
Anyway, what's this issue with Oreo ROMs / Battery enhanced Kernels?
Oreo ROMs, being still worked on, change rapidly how they function. This means that some script parts may adapt, may not. Particularly, it has been reported that NitrogenOS may have some problems when the script is used and may not be compatible for the time being. Do note that when all ROMs settle to a stable version, the tweaks will be rewritten and adapted.
Battery enhanced kernels are already optimized by the developers to have the best battery life. Adding custom scripts may ruin your experience.
FAQs
Q: Does this script support the ROM/kernel I'm currently using?
A: Yes. The script supports any kernel, even the one provided with your ROM. This being said, I won't help people using heavily modified kernels, such as Franco kernel or BoefflaKernel. As they state in their threads, modding those kernels with 3rd party app is discouraged. The scripts will work with your kernel anyway, but I can't help anyone facing issue with the mods since it's an incompatibility I can't change.
Q: Apart from flashing the module or using the script, do I need something else to make it work?
A: No, you don't need anything else to make this mod work! Just flash the module or run the script from terminal or other sources. You can, however, use KA, EXKM or open the "soilwork_op3.txt" file on your sdcard root to see if the settings got applied correctly.
Q: This script has overridden my settings! How can I make it not do that?
A: If you think this is an error, please report it to me, so I can change the script. However, if these settings are your personal settings, change them with any kernel manager and set them to apply at boot, setting the delay of the settings higher than 30 seconds (a value equal or higher than 40 seconds is reccomended).
Q: Can you add these settings to the *name of profile* profile?
A: Sure! Make your suggestions in this thread, and if after some testing they prove to be effective, I'll add them in the script. Please test them yourself before posting them.
Q: How can I uninstall the mods I'm currently using?
A: You can uninstall the mods with Magisk Manager if you are using the Magisk module. If you modified system files to make the script run at boot, simply delete the lines you've added. If you are using a third party app... You should know how. Whatever method you use, reboot your phone to see the effects.
Q: My phone's battery stats are the same! What went wrong?
A: If you're using Oreo, that's widely possible. Even if some people got great battery stats on Oreo, Oreo is still being worked on, so don't expect astronomic results. (Plus, these screenshots are also old. If you guy posted some more... )
Q: Can these tweaks make my phone waterproof, make it explode or fix VoLTE?
A: No.
More coming soon... If something is unclear, let me know
Screenshots
Check the attached thumbnails! This section is still a work in progress. Post your best sot and battery stats and they'll be posted here!
Note: If in a screenshot is tagged with the letter "A" the next one tagged with "B" is another screenshot with more detailed battery use.
Screenshots are from: @boyd95 and @Nagi2195. Thank you for the precious help!
I will try it out and tell about the battery life in few days
Can i get the video tutorial on this! Magisk is not available for android 8 so only su i have... How to install?
Gauravlonkar said:
Can i get the video tutorial on this! Magisk is not available for android 8 so only su i have... How to install?
Click to expand...
Click to collapse
Download the .sh file of your preference from the links in the download section, then install a terminal emulator and follow the guide in the op. Alternatively, to have it apply at every reboot, use any app that can run the script at boot, like EXKM, Boot Manager or apps like these ones. You can also append the scripts to your init.d. Check xda for tutorials on this one.
Nice to see your work finally released! Very good work
Great job
VoxPopuli is only for EAS kernels and roms that has it, right?
Can u provide uninstall as sometimes needed for changing profiles.
theduke7 said:
VoxPopuli is only for EAS kernels and roms that has it, right?
Click to expand...
Click to collapse
Yes, you are right
abhi0502 said:
Can u provide uninstall as sometimes needed for changing profiles.
Click to expand...
Click to collapse
You mean an uninstaller for the magisk modules? I could, but it's already a function of Magisk Manager. Go to Magisk Manager>Modules and click the rubbish bin icon to remove it. Since to install another one you have to reboot, simply install it via Magisk Manager, remove the old one and reboot. The new module will be functional at reboot and the old one will be removed. To erase the custom settings, just remove the modules you've applied and they will reset to the default ones -- the ones which came with your ROM.
i added the balanced one to Magisk on Flash kernel using Blu_Active governor and fastlane active on big cluster... so far so good, will report back after the end of this battery cycle.
This mod will work on op5?
is VoxPopuli BFP works with RenderKernel EAS?
morfances said:
This mod will work on op5?
Click to expand...
Click to collapse
Probably not, because op5's paths might differ from the ones op3/t has. You can try, but I can't guarantee that it will work
cet90 said:
is VoxPopuli BFP works with RenderKernel EAS?
Click to expand...
Click to collapse
Yes, it should work. To be sure check if Vox Populi is included in the Kernel, but if you are using a recent version of the kernel, you won't have problems
cet90 said:
is VoxPopuli BFP works with RenderKernel EAS?
Click to expand...
Click to collapse
it should work on RenderZenith (it's essentially the same but with vox), also both projects are now merged i think, both devs will produce 1 kernel from now on
morfances said:
This mod will work on op5?
Click to expand...
Click to collapse
This is written for sd820 and 821, with specifically the 3 and 3t in mind. Since the op5 has sd835 I don't think that will work well.
theduke7 said:
it should work on RenderZenith (it's essentially the same but with vox), also both projects are now merged i think, both devs will produce 1 kernel from now on
Click to expand...
Click to collapse
Hi, thx for your reply. After applying the magisk module. i noticed a slight lag during UI interaction and app launching/switching. Battery still monitoring.
cet90 said:
Hi, thx for your reply. After applying the magisk module. i noticed a slight lag during UI interaction and app launching/switching. Battery still monitoring.
Click to expand...
Click to collapse
Same story, tried battery and balanced versions.
cet90 said:
Hi, thx for your reply. After applying the magisk module. i noticed a slight lag during UI interaction and app launching/switching. Battery still monitoring.
Click to expand...
Click to collapse
yes i noticed the same on an HMP kernel as well with balanced profile.
it does improve battery though, specially when the screen is of , it's almost 0.5% an hour which means last night i lost 4% only while i was asleep (very good) , i think it needs to be optimized for when the screen is on to have less lag (it's more of a stutter)