Development of this kernel was aimed at resolving the I/O issues at the root of the problem, by fixing some improper implementations as well as updating the source code.
I am not a big fan of disabling fsync or modifying SQLite library to disable sync. Both these temporary workarounds will alleviate the problems, however they introduce very real risks of corrupting data or at times corrupting an entire partition, resulting in a brick. As such, I will not be touching these, however the mods needed for dynamic fsync will be included in the kernel.
I have only tested on the stock TF201 bootloader. I have not confirmed if it will work on the HB bootloader (TF300T bootloader), however with build v1.0.1, the bootloader restriction of the installer has been removed for those that are feeling adventurous... however please make sure to have NvFlash enabled first!!
Thanks to Namidairo, Voyager2k, and others for the hard work on the kernel.
Known issues:
Reboot does not work.
Unknown other bugs that are bound to come up, as everything has not been thoroughly tested.
Todo:
Implement other sdhci-tegra specific algorithm. Google/Nvidia seem to be working hard on completely reworking the code from scratch for 3.10 implementation.
Look into adding wake lock for bkops so that bkops can be done when tablet is going idle > this should help reduce overhead when active
Source can be found here.
Notes:
There are bound to be several bugs in the implementation. Use at your own risk.
XDA:DevDB Information
kokoKernel, Kernel for the Asus Eee Pad Transformer Prime
Contributors
kokopuphz
Kernel Special Features: Modifications to mmc drivers to help reduce overhead and streamline mmc usage
Version Information
Status: Testing
Created 2014-04-06
Last Updated 2014-05-14
Downloads
For JellyBean
20140406-v0.1
20140412-v0.2
20140412-v0.2.2
20140416-v0.3
20140418-v1.1
For KitKat
20140418-v1.0
20140418-v1.0.1
20140418-v1.1
Compatibility List
CM 10.2
CM 11
ParanoidAndroid
Change Log
v1.1 changes: (April 18, 2014)
- Bring up wifi drivers from Nexus7 grouper
- Modify for fsync params support in 3.4 fs
- Expose boot/recovery partition properly in 3.4 fs
v1.0.1 changes: (April 18, 2014)
- Bootloader restriction in installer script has been removed, but not guaranteed to work on bootloaders other than tf201!
v1.0 changes: (April 18, 2014)
- Fixed compatibility issue with KitKat (CM11, ParanoidAndroid)
v0.3 changes: (April 16, 2014)
- Fix to use local timer
- Bring up topology/cpuidle from 3.4
- Bring up all fs from 3.4
- Bring up security from 3.4
- Bring up net/netfilter from Nexus 7 KitKat mr1
v0.2.2 changes: (April 12, 2014)
- Fix minor bug in timer-tick
v0.2.1 changes: (April 12, 2014)
- Had forgotten about selinux permissive needed for kitkat... but still does not boot...
v0.2 changes: (April 12, 2014)
- Bring up cpuidle/topology from 3.4
- Fix lag when waking up from sleep
- bring up f2fs that I had forgotten in previous version
v0.1 changes: (April 6, 2014)
- Backport below from Linux 3.4
- mmc (some v4.41 features were not implemented in 3.1, such as determining correct erase_size)
- block
- md
- freezer
- scheduler (however I have left intact the Nvidia cpu scheduling algorithm, as I had read somewhere that this was quite superior to any alternatives from other vendors)
- workqueue
- few others for compatibility issues with above
- Implement background operations (bkops) from Sony Xperia (although Samsung also seems to be trying to push their bkops algorithm into main Linux)
- Reason: The implementation by Nvidia is not that good, and I just happened to use an Xperia that I like...
- Implement high priority interrupts (HPI) algorithm from Sony Xperia
- Disable auto cmd23 as apparently Tegra3 SDHCI does not work well with it (from Nexus 7 Grouper analysis)
Sounds very intriguing. Would love to see something to make the prime leaner and less sluggish. But, I'm a little gun shy for trying out on cm11 - Im not really in a position to spend a lot of time trying to unbrick if things aren't compatible the first go around. I'll be keeping my eye on this, though. Thanks for the work on this!!
kokopuphz said:
Downloads:
Compatible with CM10.2:
http://www.kokopuphz.com/android/kernel/cm10.20140406-1250.KERNEL.zip
Compatible with CM11: (not tested nor confirmed...)
http://www.kokopuphz.com/android/kernel/cm11.20140406-1250.KERNEL.zip
Click to expand...
Click to collapse
Hi
I would like to test your kernels, which boot loader do there work with?, I am using the updated wookie version (10.6.1.27.1) and get an error saying that my prime is a tf300 not an tf201 on flashing your CM 11 version
sent from my TF201
boldnuts said:
Hi
I would like to test your kernels, which boot loader do there work with?, I am using the updated wookie version (10.6.1.27.1) and get an error saying that my prime is a tf300 not an tf201 on flashing your CM 11 version
sent from my TF201
Click to expand...
Click to collapse
Thanks. Currently the kernel will only install on the stock tf201 bootloader.
Sent from my SO-04E using xda app-developers app
Didn t work with paranoidandroid kitkat...
Sent from my Transformer Prime using xda app-developers app
I'm going to try this, currently have cm 10.2
I tried all the cache2sd and data2sd stuff and it didnt seem to help much, further evidence that it might not be a h/w issue
Sent from my EPAD using Tapatalk
worked ok on cm 10.2, cant say I noticed much difference with performance.
I've just flashed cm 11, the tablet is flying again, this is what normally happens with the tf201, when you flash a new rom its fast for a while then it gradually slows down. I did forget to do a wipe so a couple of apps are misbehaving, I juts clear their data or uninstall updates if its a system app.
Now the big question is if I install this kernel now will the tablet not slow down again after a few days/weeks of usage?
I think I'll give it a go, I'm on the verge of recycling this tablet now so if anything can inject some life into it its worth trying.
edit: well I tried it on cm 4.4.2 unofficial thats posted on here and it didnt boot, just got the spinning cm logo, left it for a few minutes.
Sent from my EPAD using Tapatalk
scote said:
Now the big question is if I install this kernel now will the tablet not slow down again after a few days/weeks of usage?
Click to expand...
Click to collapse
This is exactly what should be resolved with this kernel.
An internal mmc usually does automatic maintenance type activities on every write and erase. With emmc 4.41, a new feature called background operations was introduced, which allows for the delay of the maintenance operations.
There are two problems with this. First, it was left up to the kernel developer to implement the algorithm of when to execute the background operations and when to stop them. The second problem is that once the background operation is enabled on an mmc, it can never ever be disabled. Thus, once enabled, the kernel MUST issue the background operation command, or all the necessary maintenance operations will never happen, where as on a card with it not enabled the maintenance activity occurs on all writes.
ASUS has enabled background operations on the mmc, and the simple algorithm implemented by nvidia is causing some lag.
Most custom ROMs are compiled with the background operation logic disabled, thus the algorithm is skipped altogether. This leads to eventual degradation in performance due to the lack of maintenance command being issued.
In the kernel I a working on, I attempt to address this issue by implementing a better algorithm for bkops. With the bkops logic in place, the mmc should work in the way that it was meant to work, and there should be minimal degradation of performance over time.
I'll try to resolve the issue with cm11 soon.
Sent from my SO-04E using xda app-developers app
I dont think there is any way to see real perfomance improvements without formatting to f2fs. trust me i am running this new file system right now with prime, and i dont really care about data corruption (would only happen if the tablet shutsdown by accident of course, i wont allow that!). The i/o perfomance without data2sd is over 3 times faster. Play safe with f2fs and you are never gonna return to ext4. i can only imagine what data2sd plus f2fs can do...
mythoc said:
I dont think there is any way to see real perfomance improvements without formatting to f2fs. trust me i am running this new file system right now with prime, and i dont really care about data corruption (would only happen if the tablet shutsdown by accident of course, i wont allow that!). The i/o perfomance without data2sd is over 3 times faster. Play safe with f2fs and you are never gonna return to ext4. i can only imagine what data2sd plus f2fs can do...
Click to expand...
Click to collapse
My tablet is more or less permantly docked and on ac power and I very rarely get random reboots. Corruption would be of little worry to me. If the mmc maintenance is implemented in the filesystem layer and f2fs currently does a better job of it than ext4 then it may be worth me trying that. If the mmc maint is in a layer below filesys then the work the op is doing will help in either case, is that correct?
Sent from my GT-N7105 using Tapatalk
@scote
You're absolutely right. The changes are on an underlying layer, thus it should help both.
@mythoc
As a reference, could you let us know if you used any benchmark for the comparison between f2fs and ext4?
Sent from my SO-04E using xda app-developers app
I'm thinking about trying f2fs on my cm11 rom. As I have a /data that is ext4 and has been in use for a few months I think it may be good to benchmark that first, then again after conversion to f2fs, and then again when this kernel is fixed for cm11.
I've tried a few storage benchmarks from the play store, is there a good one that has selectable partitions and has random writes?
Sent from my EPAD using Tapatalk
damn my benchmark results from ext4 are gone. i can only test f2fs now with antutu i guess. i remember getting total of 15-16k score, with 1192 storage i/o and and 630* database i/o. I dont really trust benchmarks much, you feel the difference anyway
kokopuphz said:
For JellyBean ROMs (confirmed on CM10.2 by Namidairo)
20140406-v0.1
For KitKat ROMs (not tested nor confirmed, nor working)
20140406-v0.1
Compatibility List
CM 10.2
Not working on
ParanoidAndroid
Click to expand...
Click to collapse
Hello!
I have a TF201 that a year ago I bricked and I fixed the ASUS RMA. After coming from there I could not unlock him. Going to ask what you did without it bricked again? Does her version J.B. 4.1.1 NO-10.4.2.18-JR003C.WW_epad 20121122
Thanks!
If you are asking how I unlocked, I sent numerous emails to asus service until they finally updated the info in their servers, and then I was finally able to.
Sent from my SO-04E using xda app-developers app
I understand! So all ASUS can unlock.
v0.3
v0.3 has been released. Quite stable, but currently only runs in cm10.2 or other non-kitkat roms. This is due to SELinux and the way that I have packaged the kernel. I will work on creating proper release package in the next few days.
v1.0
v1.0 is now available, and is now compatible with CM11 released by Namidairo. I will see if it also works with ParanoidAndroid as well and will update this post.
--update--
I have confirmed, v1.0 works on ParanoidAndroid 4.2 Beta 4
Related
This is an unofficial build of TeamBAKED Blackbean 6 for the new Jelly Bean bootloader for the Transformer Prime.
Unlike the current TeamBaked Jelly Bean builds, this uses a modified version of my Jellybean CM device & vendor tree... including the new 3.1 Jelly Bean kernel and the new Jelly Bean drivers and proprietary files. THIS REQUIRES THE NEW JELLY BEAN BOOTLOADER. I will not release many builds for this unless there are issues or enhancements. This will remain in line with the TeamBAKED official releases, until I merge this to the TeamBAKED repo.
Highlights of this ROM:
1) Android Jelly Bean 4.1.2 JZO54K
2) Built using the latest TeamBAKED Blackbean 6 changes as of 30 Oct 2012 (GitHub) which is a combination of CM10 & AOKP features for the most case
3) Uses the latest a modified version of my TF201 device, vendor and kernel trees (based on the AndroidRoot trees) with the Jelly Bean 10.4.2.15 kernel (3.1) and proprietary files & drivers with some changes and additions by me (GitHub)
4) Needs the new Jelly Bean 10.4.2.15 bootloader [IMPORTANT: Flashing over an incorrect bootloader can permanently brick you device.]
5) HDMI audio/video streaming and bluetooth audio streaming (AVRCP 1.3 ready)
6) Camera and microphone
7) 4-way reboot menu (Reboot, Recovery, Fastboot & APX)
8) Includes all the files and changes need for the Google Widevine DRM [untested!!]
9) CIFS and NTFS (read-only) support
10) Fully functional dock and dock battery display
11) Configurable Navigation Bar, Expanded Desktop, CM & AOKP toggles
11) Removed TeamBAKED OTAUpdater
12) All other features of TeamBAKED Blackbean 6 and Jelly Bean (full hardware acceleration, Project Butter, HD video, customisable notification toggles & many more)
13) Some custom addons and feature ports by me (see the individual build changelogs)...
New in Oct 30 2012 build:
1) BFQ v5, SIO & V(R) I/O schedulers. SIO set as default
2) Lulzactive & Pegasusq CPU frequency governors.
3) Standardise CPU frequency tables' values & disable Asus system mode CPU speed restrictions
4) Enabled zRam/Compcache & KSM (Kernel SamePage Merging) support
5) Fixed model number & LCD density
6) Several device overlay updates and cleanups (bunch of updates for JB)
7) Auto-brightness turned off by default
8) Cleaned-up & updated release tools script (this creates the zip packages)
9) Set correct permission for BtService.sh (Bluetooth DUN) script
10) Force NV_FPS_LIMIT to 60 for all performance modes
11) Device Advanced setting menu to set Asus performance modes (defaulted to Balanced). This is not for the CPU speed, rather the Tegra performance setting (cpuX.sh like functionality)
12) Fixed Torch
13) Updated device power profile based on official JB release
Known issues:
1) Key layouts for certain regional keyboard may not work
2) Auto-brightness is funky [Use the app Lux for auto-brightness]
3) NTFS support is read-only
4) exFAT is not supported
Important:
1) Wipe data/factory reset if coming from any other ROM (icnluding the official TeamBAKED Blackbean ROMs)
2) Wipe cache/dalvik cache for every update
3) After flashing a build, it is a good idea to wait for 5-10 mins after bootup to allows everything to settle in
4) If you have not upgraded to the official Jelly Bean ROM yet, you will need to a JB ROM with the new bootloader first, and then you may flash the latest build here.
5) Once you upgrade to this ROM, you will no longer be able to use the official TeamBAKED Blackbean ROMs till the new Jelly Bean changes are merged
6) Make sure you use a recovery compatible with the new Jelly Bean bootloader after flashing this ROM.
The usual 9 yards:
1) Have you read this post properly. Read it again!!
2) You need to have an unlocked bootloader
3) You need to have a custom recovery (CWM or TWRP)
4) It is a good idea to have enabled nvFlash (thanks to AndroidRoot) so that you can recover from almost any brick
5) Neither I, nor the TeakBAKED team, nor the AndroidRoot team take any responsibility if anythings goes wrong. Use at your own risk
6) Always make sure you create nandroid backups regularly
baked_tf201_blackbean-6-jbbl.zip [IMPORTANT: You need to upgrade to the JB bootloader before flashing this]
Inverted Google Apps Pack - 20121016
OR
Regular Google Apps Pack - 20121011
GitHub Sources:
Device Tree
Kernel
Vendor Tree
Tweaks & Mods:
1. GPS Config Tweaks (Multi-Region):
This has various regionally optimized GPS configuration tweaks to inprove GPS locking.
Download tf201-GPSTweaks.zip and flash using TWRP recovery
tf201-GPSTweaks.zip - Dev-Host
tf201-GPSTweaks.zip - Goo.Im
2. SysCtl And DNS Tweaks:
This has a set of SysCtl tweaks to improve multi-tasking and overall performance as well as makes use of the Google DNS servers which are generally faster.
Download tf201-SysCtlAndDNSTweaks.zip and flash using TWRP recovery
tf201-SysCtlAndDNSTweaks.zip - Dev-Host
tf201-SysCtlAndDNSTweaks.zip - Goo.Im
3. Build.Prop Tweaks:
A compilation of build.prop tweaks tested on the TF201
Read here
4. EXT4 Journaling Tweaks: (Advanced Users Only. Manual Steps Involved)
If you don't understand these commands, you probably should lean more about them before using these tweaks.
Read here
Useful threads:
TF201 NVFlash
TF201 nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]
[ADB/FB/APX Driver] Universal Naked Driver
TWRP Recovery For JB Bootloader
Support the project:
Donate to TeamBAKED
Donate to CyanogenMod
Donate to AOKP
Donate to AndroidRoot
Donate to me (craigacgomez)
Credits:
TeamBAKED, CyanogenMod Team & Contributors, AOKP Team & Contributors, AndroidRoot Team, TeamWin
Google, Asus, nVidia
Goo.im, Dev-Host
Me!!
Reserved for me!
first! this is awesome. downloading now. maybe i wont have anymore random reboots in the keyboard dock... your test build 2 was the most stable for me of all the JB roms (least amount of random reboots). I cant tell if its apps I have installed or the KB dock but i am usual in the dock.
Will report back.
:laugh:
Hi Craig,
What's the best way to install this rom or your cm10 build with data2microsd?
Sent from my Transformer Prime TF201 using xda app-developers app
This is fantastic... but now I have to choose... this ROM or CM10 unofficial? What are the tradeoffs? Feature set vs. performance? Which will you be supporting for longer, Craig?
Where can I donate when PayPal *****es at me with "Sorry — your last action could not be completed"?
bonstio said:
This is fantastic... but now I have to choose... this ROM or CM10 unofficial? What are the tradeoffs? Feature set vs. performance? Which will you be supporting for longer, Craig?
Where can I donate when PayPal *****es at me with "Sorry — your last action could not be completed"?
Click to expand...
Click to collapse
CM10 unofficial)) this has inverted interface that I can't stand)
bonstio said:
This is fantastic... but now I have to choose... this ROM or CM10 unofficial? What are the tradeoffs? Feature set vs. performance? Which will you be supporting for longer, Craig?
Where can I donate when PayPal *****es at me with "Sorry — your last action could not be completed"?
Click to expand...
Click to collapse
This is a mix of CM10 and AOKP... this is not released as frequently as CM10 or AOKP, but I may release a few updates to add some things... as long as I have this tablet, I will support all 3 ROMs...
is there a CWM recovery available for roms with a JB bootloader?
every time I flash using TWRP I get stuck at the asus boot screen...
I tried to flash this twice so far and keep getting stuck.
Just installed with twrp. All is well so far. Thanks for this ROM
Sent from my PC36100 using Tapatalk 2
knucklehead_11 said:
Just installed with twrp. All is well so far. Thanks for this ROM
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
what version of TWRP did you use?
I'm using TWRP 2.2.1. I just have not upgraded yet. If you are having problems with the install, check your md5 sum and make sure that you have a proper ROM download.
So far no force closes or any problems with games or video.
Sent from my Transformer Prime TF201 using Tapatalk 2
Hey Craig i really like this rom, but the only thing keeping me from using it is my GPS isnt working on it or any of your other unofficial ports. I tried flashing. The gps tweaks for the dongle wich i use and and doesn't seeme to make a diff. So i have to keep going back to the hairy been rom wich gps works in. I read that you said you were just starting out but maybe you could pull the gps stuff from HB or something if thats aloud. Also anyone else reading this hows your gps on JB roms(besides HB1.3) with the dongle? Thanks for your work ive flashed all your roms for my tf201 and given you thanks.
why am i getting stuck at the logo screen again....? i was only able to boot in aokp with disabled wifi. CM10 and this rom, i always get stuck at the loading screen
godlyitem said:
why am i getting stuck at the logo screen again....? i was only able to boot in aokp with disabled wifi. CM10 and this rom, i always get stuck at the loading screen
Click to expand...
Click to collapse
Probably a kernel problem, aokp has not the same kernel than the two others.
godlyitem said:
why am i getting stuck at the logo screen again....? i was only able to boot in aokp with disabled wifi. CM10 and this rom, i always get stuck at the loading screen
Click to expand...
Click to collapse
When met with this (as I constantly am while attempting to install HairyBean) I have to re-flash stock ROM, then recovery, then custom ROM. I didn't unlock and NVflash before jellybean so I can't go that route.
Sent from my HTC Vision using xda premium
screen keeps rotating constantly when I long-press to remove an icon or widget...
fully wiped 3 times (factory reset & system)....anyone else having any issues?
broad_st_bully said:
screen keeps rotating constantly when I long-press to remove an icon or widget...
fully wiped 3 times (factory reset & system)....anyone else having any issues?
Click to expand...
Click to collapse
Not having that problem but I'm using Nova launcher.
Very nice rom. Fast , stable and no reboots or hick upps so far.
Only usb ethernet doesnt work.
Man, I just can't find a rom that works with my keyboard that has an sd card in it. When I have a card in the dock, and go to settings/storage, it keeps FC'ing. If I take the card out, I have no problem with settings/storage.
kix08 said:
Hey Craig i really like this rom, but the only thing keeping me from using it is my GPS isnt working on it or any of your other unofficial ports. I tried flashing. The gps tweaks for the dongle wich i use and and doesn't seeme to make a diff. So i have to keep going back to the hairy been rom wich gps works in. I read that you said you were just starting out but maybe you could pull the gps stuff from HB or something if thats aloud. Also anyone else reading this hows your gps on JB roms(besides HB1.3) with the dongle? Thanks for your work ive flashed all your roms for my tf201 and given you thanks.
Click to expand...
Click to collapse
Well, I get very little GPS performance without the dongle even in a stock rom, and that was with UCS. JB stock gives pretty reasonable gps performance with the dongle in, at least if you're on the highway were there are plenty of satellites overhead.
I'm about to flash this and see how it goes. I'll update and let you know how my GPS does.
EDIT: tested GPS, I'm getting the same functionality as in both the ICS and JB stock roms. Which is to say "good enough". It can usually lock on at least 3 satellites.
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.
CyanogenMod 11.0 UNOFFICIAL for LG Optimus L9 p769This is unofficial build. Use at your own risk. I am not responsible for anything that may happen to your phone.
Only for P769 version of the phone. Do not attempt to flash on any other device.
The phone bootloader has to be unlocked and correct recovery installed.
Please avoid discussing general unlocking, rooting, and other unrelated to development issues in this thread.
Features
- Continuation of the CM10.2 and CM 10.1 ROMs
- No emulated internal storage. Single external SD card configuration (read note in this post)
- Apps 2 SD support
- Support for Notification Lights, either native or with BLN (read note in this post)
- Analog amplifier gain control with Voodoo Sound support (read note in this post)
- Microphone preamplifier gain adjustments
- Performance kernel with OC/UV
- Advanced Settings to control kernel clocks
Kernel
- Extended frequency table with 200MHz, 1200MHz, 1350MHz (overclocking doesn't work on some phones)
- Slightly undervolted
- Userspace voltage control. Use SetCPU, VoltageControl, or similar. Warning: Save a recovery script with either of these programs before playing with voltages!
- GPU is extended with 384MHz, IVA with 430 MHz
- Selectable screen-off maximum frequency
- Included SmartassV2 governor, SIO scheduler.
- Few performance tweaks.
Installation
- If going from non-CM ROMs, backup your data and do full reset. If updating from CM it is usually not necessary.
- Make sure you use recent CWM recovery (see 2nd post)
- Copy to SD and flash with CWM.
- Flash correct CM11 version of Gapps
- Clear Dalvik Cache
- If you don't have data connection on the first boot right after flashing, power down and reboot one more time.
Download
cm-11-20160818-UNOFFICIAL-p769.zip (Mega)
cm-11-20160818-UNOFFICIAL-p769.zip (Dropbox)
Sources
Github
History
Upstream merges
[08/18/2016]
- End of life update
- Android Security Patch Level: August 1, 2016
[11/06/2015]
cm-11-20151106-UNOFFICIAL-p769.zip
- GPS LTO fix (see this post)
- Minor fixes to camera
- Increased microphone volume for bluetooth
- Kernel redone from LGE (Dhiru) sources, then lots of patches and cleanups applied, including all my usual tweaks and mods.
- 1080p video recording (thanks to Dhiru)
- Selinux enabled in enforcing mode
- Latest repo with libstagefright security patches
10/10/2014
- Repo synced
09/19/2014
cm-11-20140919-UNOFFICIAL-p769.zip
- Repo synced
- Different way to fix libjhead.so for camera
08/29/2014
cm-11-20140829-UNOFFICIAL-p769.zip
- Repo synced
08/15/2014
cm-11-20140815-UNOFFICIAL-p769.zip
- Repo synced
07/25/2014
cm-11-20140725-UNOFFICIAL-p769.zip
- Repo synced
07/11/2014
- Repo synced, CM 11.0 M8
- Fix RIL audio path for multiple calls (ref)
06/27/2014
cm-11-20140627-UNOFFICIAL-p769.zip
- Repo synced, Android 4.4.4
- More kernel patches
06/13/2014
cm-11-20140613-UNOFFICIAL-p769.zip
- Repo synced, Android 4.4.3
- Some patches to kernel
05/30/2014
cm-11-20140530-UNOFFICIAL-p769.zip
- Repo synced
05/16/2014
cm-11-20140516-UNOFFICIAL-p769.zip
- Kernel patched to 3.0.101
- Repo synced
05/02/2014
cm-11-20140502-UNOFFICIAL-p769.zip
- Repo synced
04/11/2014
cm-11-20140411-UNOFFICIAL-p769.zip
- Enabled Long Term Orbits updater service
- Repo synced
03/21/2014
cm-11-20140321-UNOFFICIAL-p769.zip
- Repo synced
02/28/2014
cm-11-20140228-UNOFFICIAL-p769.zip
- Repo synced
02/20/2014
cm-11-20140220-UNOFFICIAL-p769.zip
- Repo synced
- Enabled MDP swaprect
02/11/2014
cm-11-20140211-UNOFFICIAL-p769.zip
- Repo synced
02/03/2014
cm-11-20140203-UNOFFICIAL-p769.zip
- Repo synced
01/24/2014
cm-11-20140124-UNOFFICIAL-p769.zip
- Original CM11 release, device tree modified for CM11, repo synced
CM 10.2 history here
CM 10.1 history here
Notes
Notes from 10.1 still apply.
Extras
To avoid "set_metadata_recursive" errors during install, update your CWM Recovery if you haven't done so yet. Use either fastboot or Recovery Tools - Flasher to flash recovery.
Download CWM Recovery 6.0.4.9 for p769
T-Mobile V20f radio: Mega, Dropbox. Flash with CWM (I think you'll need an older version, one prior to 6.0.4.7).
I'm starting to build CM11.0 from my device tree. Will probably do a build per week or two depending on the rate of upstream commits.
Kernel is the same as for CM10.2 so we have usual BLN, Voodoo sound, etc.
I've been running it for few days now, seems fine, at least I don't see anything really bad. Watch for battery drain, I may have had a weird issue with some unusual wakelocks but cannot confirm it as today it's not doing it.
On my phone I flashed CM11 on top of CM10.2 with no issues, so it seems like there is no need to do full wipe if you are updating from CM. Just make sure to update recovery.
CRT-off animation is turned on by default but now can be changed to fade-off in Display Settings.
Thanks so much for this
I was using your 10.2 build until BobZhome came out with his cm11 build.
I'll be switching to this build as soon as I can. Your 10.2 kernel worked great so I'm hoping it'll help clear up some of my issues. Do you experience lag when using ART? That's my main problem, as well as poor audio level adjustments.
Sent from my LGMS769 using xda app-developers app
Awesome! ^_^
Is there any guide how to port this to 760?
@Alek5 My rom has the same features and much more. Some features for ex. BLN aren't in my rom, because you can install app from play store.
I know, I'm using your rom right now and it's great. But I really miss BLN because LG notification app never worked reliably on my phone (on any rom), and it's really annoying... is there any way you could add BLN to your rom?
Sent from my LG-P760 using Tapatalk
New build is up, repo synced.
Anyone use a blacklist to block unwanted calls sms/mms? I'm not having any luck with stock dialer/messaging. I even tried enabling wildcards and tried several different number combos. I'm aware that KK has issues with 3rd party msging apps. Can anyone else confirm this blacklist issue?
Sent from my LG-P769 using Tapatalk
New build is up, repo synced.
Thanks Anton. When you did CM10.1 you offered a non-tweaked kernel as an optional download. Any possibility of having the same option for CM11?
First of all thank you VERY MUCH for taking your time to work on this. Will you continue to work on this build until the 1080p issue is fixed and any ETA on that? Does this build correct the fast battery drain problem that Jellybean has?
Sorry for all the questions but I don't believe I am currently unlocked and from what I know I will have to downgrade from Jellybean back to ICS to do it and it is pretty complex. Before I do all that I want to make sure all the details of this KitKat build and wait till everything is fixed. Thanks again!
Blackman75 said:
First of all thank you VERY MUCH for taking your time to work on this. Will you continue to work on this build until the 1080p issue is fixed and any ETA on that? Does this build correct the fast battery drain problem that Jellybean has?
Sorry for all the questions but I don't believe I am currently unlocked and from what I know I will have to downgrade from Jellybean back to ICS to do it and it is pretty complex. Before I do all that I want to make sure all the details of this KitKat build and wait till everything is fixed. Thanks again!
Click to expand...
Click to collapse
I will like to know the 1st question as well, every rom project gets quickly abandoned neither completed.... i will like to have that 1080p
New build, repo synced.
I have enabled swaprect for display processor. By default CM enabled it only on Qualcomm devices but it seems to run fine on ours. If you see any screen artifacts let me know and I will revert. Related upstream commits:
http://review.cyanogenmod.org/#/c/59520/
http://review.cyanogenmod.org/#/c/59524/
http://review.cyanogenmod.org/#/c/59898/
I don't have any plans for 1080p video recording, it's all proprietary with no source code. To say the truth I don't even care about 1080p. The camera itself is not that great, 720p is good enough for it.
Kernel without tweaks is posted in the OP Kernel section.
What's the best CPU settings to get away from this horrible battery drain?
Sent from my LG-P769 using Tapatalk
Friday build
Just flashed CWM from post 2 using the recovery tool and I have below the LG symbol Security Error. Phone will not boot past it.
It had 20H on it, any ideas?
Retiredfinally said:
Just flashed CWM from post 2 using the recovery tool and I have below the LG symbol Security Error. Phone will not boot past it.
It had 20H on it, any ideas?
Click to expand...
Click to collapse
You didn't unlock the boot loader?
Sent from my unlocked LG P769 running BobZhome unofficial CM11
GPS still buggy?
Sent from my LG-P769 using Tapatalk
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.
After maybe a month of working in the kernel.
I guess it's about time to release the kernel for testing.
Downloads in the second post are only there for easy follow ups.
Please read all the sections below before trying out this kernel first.
This kernel comes with absolutely no warranties whatsoever, period.
XDA:DevDB Information
This field is required., Kernel for the Samsung Galaxy Star
Contributors
psych.half
Kernel Special Features:
Version Information
Status: Testing
Created 2016-02-15
Last Updated 2017-10-12
Downloads
Latest : kernel-mint2g-trilogy-stable-r10.zip
The latest version is tested to be booting on :
Stock JB4.1 with CWM 6.0.5.3 by @dabakale
CM-10.1 with Philiz recovery by @medved197938
CM-11 with TWRP 3.0 by me
If you are getting status 7 errors, while flashing.
Try with a different recovery, and if that doesnt help upload the /sdcard/liverepack.log along with recovery.log from your recovery.
Changelog:
Code:
==================================
r10 : Apr 7, 2016
- Added and fixed custom voltage control, It could be errornessly set lesser than 650mV.
- Added underclocking. Needs to be enabled manually, see post #
- Removed 1400Mhz and 1500Mhz frequencies, as it causes crashes on many devices.
- MTP should now work on both Stock/CM rom (needs testing )
- Fixed battery level getting stuck issue.
- Fixed brightness/constrast bug in stock ROM.
- Initial stable* release of trilogy version.
Extra downloads
camctl : script to enable/disable camera for RAM
How this thread is organized.
The OP has been broken down into sections. The first 20 posts reserved for info/wiki sort of.
So when things get updated/added it'll all be in the first few pages for everyone to see.
Each section will be short and to the point so you're having problem with one section.
And you're the type who just has to quote posts you might do so without getting on other people nerves.
And normally I just just ignore the forum's usual craptalks, but at this early stage of development, try to keep the noise minimal
Let's make some things clear first.
This kernel is not for you if you want a stable kernel.
CM11 should already include the stable version of this kernel, so you should just stick to that.
This kernel is only for CM11. No other roms will be supported or even considered.
This kernel is higly experimental. Freshly made, straight from the lab.
So expect some breakage of functionality, random reboots, bootloops and explosions (unlikely, but I gotta cover myself).
Flashing
The zip makes no backup of your current kernel as of now.
So if you wanna go back to shipped CM11 kernel you have two options.
i) Manually move the original modules to system and restore just the boot image from TWRP.
ii) Restore/flash the entire ROM.
As for flashing the zip, you should burn it on a CD, and choose boot from CD in your PC by keep pressing F10/F12 at BIOS screen.
Well no but, you should at least be familiar with flashing and backups.
Breakages
Camera:
Well, it's due to updated ION drivers, which are not compatible.
In the meant time I have disabled memory allocation for camera.
Which should give some extra free memory.
If there's any other stuff broken here but not while using CM11 kernel.
Post it here instead of there. But not the stuff broken in shipped CM11 too.
What are not bugs.
24mb of less RAM:
Linux ate the RAM, no really.. linux eats RAM http://www.linuxatemyram.com
Well it's due to enabling memory cgroups.
Android says keep it enabled for low ram devices.
As per https://source.android.com/devices/tech/config/low-ram.html
Also, see the below sections for frequency scaling
Bug reporting
You know you won't get help the next time from a kernel dev if you give them a logcat.
So get the dmesg or no help for you.
And /proc/last_kmsg is not working due to ram console issues.
So if you're gonna be reporting random reboot issues, make it reproduceable.
And make it precise. If the issue is caused because you have installed, some 10 or 20 other mods.
Good luck solving it.
What are in the kernel.
You get your usual stack of IO schedulers, governors, dynamics and mods. They won't be included in the change log below.
I don't even know what half of those are.
So don't ask me what/which one to use. See them for yourself.
You also get some usual tweaks, which can be changed with any kernel control app you like.
Same don't ask what/how to tweak.
If you want something to be added that you don't find. Let me know, and I'll see what I can do.
Frequency scaling
Frequency scaling is already included from r3 onwards. So the previous instructions no longer applies.
The default min and max frequency is 1Ghz and default governor performance. ie. same as stock.
Any change to that is your own choice.
And your own loss if something goes wrong.
There are some limits to it.
i) It can be only changed 10 times a second, so it might cause lag sometimes.
So choose your governor and scaling wisely. Battery or performance. You decide.
Underclocking has been removed.
Going below 1000Mhz makes no sense, as the core voltage is the same.
There is no point in reducing frequency, if the power consumption is constant.
Overclocking has it's own section. See below
Overclocking
First if you were using the older broken cpufreq driver and were in the impression that you were at 1.6Ghz you're gonna damage your device.
The driver written by me, really overclocks the cpu and the whole system, yeah mines fractured too. Nothing I can do about it.
So use at your own risk. And don't discuss about the safe overclocking frequency. There isn't any.
Issues caused by overclocking are not issues. or bugs.
I won't give you any overclocking advice. But here's one anyway.
Overclock only when necessary and do not keep the values persistent at boot, "Set at boot" in apps.
Changes from stock:
A lot of thing has been updated, changed, modified. I will have to go through source again.
A short list of changes I can think right now will be posted soon.
- The you know, built with some GCC-5 Linaro toolchain and O2.
- Cherry picked upgrades from various kernel sources.
- Disabled a whole lot of Samsung debugging.
But there's more... see the Github repo.
reserved
#Reserved
#Reserved
#Reserved
Source
kernel:
https://github.com/halfpsych/kernel_mint2g
cpufreq-driver: https://github.com/mint2g/kernel_module_cpufreq-driver
Contributing.
Any contributions to both source and wiki are always welcome.
You can help fix typos or better clarify some sections or even help to write new ones.
Credits
For bringing CM11 to this device
- corphish
- Dreamstar
- TeamButter
- All others involved in CM11 mint2g project
Initial testers and bug reports:
- Dark Knight Begins