Related
The NookieDevs are pleased to announce CyanogenMod 11 nightly builds for the Nook Color!
These experimental builds 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. As CyanogenMod 11 is still under active development, regressions and general breakage are to be expected in nightly builds!
Highlights:
Linux kernel 3.0.101, 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 11, based on Android 4.4. For Nook Color, this brings a reduced memory footprint, which leads to a better all-around user experience.
Full 2D and 3D graphics acceleration using both the GPU and the display subsystem's hardware overlay acceleration (hwcomposer).
Known issues:
Video playback is slower than on previous releases -- this is most noticeable when playing HD 720p video.
Bluetooth is broken at the moment after changes for Qualcomm Bluetooth chipsets were merged into CyanogenMod.
Current releases of Netflix do not work with CM10.2 -- 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.
ART (the experimental Android runtime introduced in 4.4) is not supported -- if you enable it, your system will not boot. (Workarounds may exist, but they are not going to be officially supported either -- use them at your own risk.)
Download:
http://download.cyanogenmod.org/?device=encore&type=nightly
Note that an updated recovery is required to install CM11. ClockworkMod 6.0.4.8 and newer versions should work, as should other recoveries provided the required changes are included. (Ask the maintainer of the recovery if you're not sure.) NOTE: Do not use ClockworkMod 6.0.3.x builds older than 6.0.3.6, as they contain a bug which may brick your device!
Source code:
https://github.com/CyanogenMod/android_device_bn_encore/tree/cm-11.0 (device-specific source)
https://github.com/CyanogenMod/android_kernel_bn_encore (kernel)
https://github.com/CyanogenMod/android/tree/cm-11.0 (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 historically provided excellent support for its embedded platforms to the open-source hacking community.
XDA:DevDB Information
CyanogenMod 11 Nightly Builds, ROM for the Barnes & Noble Nook Color
Contributors
steven676, keyodi, fattire, The CyanogenMod Project, NookieDevs, many others (see post)
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-01-30
Last Updated 2014-05-15
Google Apps; other CyanogenMod builds
Google Apps
http://wiki.cyanogenmod.org/w/Google_Apps
As of 2014/07/25, the latest release for CM11 that is known to work is 20140105. DO NOT use the 20140606 release unless installing to SD card -- it contains over 100 MB of additional bloat and will not fit on an eMMC installation!
If you wish to use another Google apps package, and are installing on eMMC, please note that the Nook Color has what is by modern standards a limited amount of disk space available on /system (440 MB) -- the base system is currently in the neighborhood of 300 MB, so some of the larger packages will not fit. If you're offered different variants, choose the smallest one in order to avoid problems.
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 CM11 nightly builds. There are other official CyanogenMod builds for Nook Color available:
Stable releases of CM10.2 and CM10.1 -- these are the releases to use if you don't want to be on the bleeding edge.
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 install fails with errors from "set_metadata_recursive"!
The installation appears to succeed, but nothing's changed when I reboot!
You'll need an updated recovery to install CM11. For CM11 nightly builds from May 16 and later, any recovery that reports itself as ClockworkMod 6.0.4.8 or later should work; other non-CWM recoveries should work if they incorporate the necessary changes to suppor these builds (you'll have to ask their maintainers for details).
For older CM11 nightlies, any recovery that reports itself as ClockworkMod 6.0.3.6 or later should work; other non-CWM recoveries such as TWRP 2.6.3.0 or later should be fine provided the kernel is sufficiently new (you'll have to ask their maintainers for details). NOTE: Do not use ClockworkMod 6.0.3.x builds older than 6.0.3.6, as they contain a bug which may brick your device!
I installed CM11, wiped /data, and now my tablet's been booting for an awfully long time. Is something wrong?
First boot will take at least five minutes, and the boot animation currently stops many times during this process. If you've been waiting more than 10 minutes and it's still not booted up, you probably have a problem.
The soft keyboard keeps crashing!
The Play Store is acting up!
Did you flash the correct Google Apps? If on an eMMC install, are you sure your Google Apps fit on /system?
How do I install this to an external SD card?
See this excellent guide by leapinlar for instructions. It's reported that Google apps installation is broken in the SD card installer at the moment, so you may need to wait for that to be fixed.
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 CM11 nightlies, it'll be something starting with "cm_encore-userdebug 4.4.2 KOT49H" or "cm_encore-userdebug 4.4.3 KTU84M") seven times.
How do I get the Honeycomb/ICS tablet UI?
You can't -- Google killed it off in Android 4.4.
The lock screen doesn't rotate!
The screen doesn't rotate to the sides I want!
Particularly if you're upgrading from an existing install, you may find that the preferences for screen rotations are incorrectly set. Go to Settings->Display->Rotation and check that "Auto-rotate screen" and (if you want the lock screen to rotate) "Rotate lock screen" are set.
For the allowed screen orientations, selecting 0, 180 and 270 degrees will cover the rotations that you probably want. If you want details:
Android likes to think of the "natural" orientation (0 degrees rotation) as landscape with the N key on the right side of the screen. (This is a change from CM10 and earlier, when we were carrying a hack to change this.) The degrees of rotation are counted in the counterclockwise direction, so in essence, each of the rotation settings allows the following:
0 degrees: landscape orientation with the N key on the right side of the screen
90 degrees: portrait orientation with the N key on top ("upside down")
180 degrees: landscape orientation with the N key on the left side of the screen
270 degrees: portrait orientation with the N key on the bottom ("right side up")
I enabled ART, and now my Nook Color won't boot!
ART isn't supported on Nook Color at the moment due to known issues:
The initial compiling pass that happens the first time you enable ART may cause your tablet to run out of both RAM and disk space.
Many of the Google apps packages for CM11 are incompatible with ART.
If you're currently stuck in a bootloop after enabling ART, boot into recovery and then see this post by fattire for advice on how to restore your system to a working state.
I can't get any of the ROMs or recoveries for Nook Color to boot!
Before you go any further -- are you sure you have a Nook Color and not a Nook Tablet? The two devices look almost identical, but Nook Color (model number BNRV200 -- check the fine print near the speaker grille on the back) has a dark gray bezel, while Nook Tablet (BNTV250) has a light gray or silver bezel. The two devices are not interchangeable -- Nook Color software will not boot on Nook Tablet and vice versa.
If you've got a Nook Tablet, you want to be in the Nook Tablet forums instead.
I'm having a problem with my Nook Color running CM11.
That's not a question
Okay, I'm having a problem with my Nook Color running CM11 -- is there something I can do to troubleshoot?
Glad you asked! Please check the following:
Does the problem occur with a clean install of CM11? 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.
Now that everyone has squared me away (in the 10.2 thread) on the you-need-CWM-6.0.4.5-to-flash-CM11 issue, I hafta say, after 2-3 hrs, this CM11 is quite good! No hard numbers, sorry, but seems reliable, faster than 7.2, and, of course, the UI is vastly better. Waytago steven676, keyodi, fattire! Thanks!
Hello everyone,
To run off of an SD; I created a new SD (sandisk 8gb) with the latest image from Leapilar, the nightly and suggested GAPPS (gapps-kk-20140105-signed.zip). There were some error messages from the GAPPS (they scrolled off before I could really read them). The NC booted to the desktop but there was no play store.
Any ideas?
Thanks,
V
volpo222 said:
Hello everyone,
To run off of an SD; I created a new SD (sandisk 8gb) with the latest image from Leapilar, the nightly and suggested GAPPS (gapps-kk-20140105-signed.zip). There were some error messages from the GAPPS (they scrolled off before I could really read them). The NC booted to the desktop but there was no play store.
Any ideas?
Thanks,
V
Click to expand...
Click to collapse
If your errors match the ones reported on the SD installer thread:
bowguy said:
I then tried to install the 2014/01/05 gapps package using your/verygreen's script and saw this message:
"Hangouts.apk exists but is not a regular file" The script died at this point and shutdown. After booting, you cannot add a google account as it appears it is a very incomplete gapps install.
Click to expand...
Click to collapse
then it's the bug mentioned in the FAQ -- it looks like the SD installer needs an update.
deleted
Just curiuos if anyone has an oppinion to how cm11 is running on the device. I originally flashed cm10.1 when I first rooted and it ran INSANELY slow and laggy, probably due to the low ram etc. But was forced to run CM7 and it ran perfectly and have been running it ever since. I know that 4.4 is supposed to have lower dependencies for running on older/slower devices but anyone got some input on just how good it runs? I am going to probably try it later on tonight, it will just take me a while cause i got to backup my sons game data first or hill kill me.
tp2215 said:
Just curiuos if anyone has an oppinion to how cm11 is running on the device. I originally flashed cm10.1 when I first rooted and it ran INSANELY slow and laggy, probably due to the low ram etc. But was forced to run CM7 and it ran perfectly and have been running it ever since. I know that 4.4 is supposed to have lower dependencies for running on older/slower devices but anyone got some input on just how good it runs? I am going to probably try it later on tonight, it will just take me a while cause i got to backup my sons game data first or hill kill me.
Click to expand...
Click to collapse
Just DOOOO it
(not that I'm encouraging you one way or the other)
steven676 said:
If your errors match the ones reported on the SD installer thread:
then it's the bug mentioned in the FAQ -- it looks like the SD installer needs an update.
Click to expand...
Click to collapse
Yes that's it then.
I hope this gets worked out. 4.4 was very smooth and worked well.
V
Thanks guys just flashed it and so far this looks great, I'd say it's smoother than 10.2 and multitasking is just a bit better. Couple of small issues came across were rebooting to recovery doesn't work for me it just reboots, also had a soft reboot and after it booted up the systemui kept crashing and wouldn't let you do anything, but a regular reboot fixes it.
Just flashed in it looks great! Feels MUCH smoother and snappier then 10.2. Minor issue that boot take a long time. It seems to me like the boot keeps freezing but eventually continues. No force closes or anything. I am trying now to enable ART and play with it a little to see if it drasticaly improves it. It seemed to make a little bit of a difference on my S3.
Edit: You may want to add to the op, DO NOT enable ART. It sends it into a reboot loop.
tp2215 said:
]
Edit: You may want to add to the op, DO NOT enable ART. It sends it into a reboot loop.
Click to expand...
Click to collapse
Yeah, actually steven, if someone has issues with ART you might wanna link here. You can recovery from an ART bootloop w/o reinstalling or anything weird.
tp2215 said:
Just flashed in it looks great! Feels MUCH smoother and snappier then 10.2. Minor issue that boot take a long time. It seems to me like the boot keeps freezing but eventually continues. No force closes or anything. I am trying now to enable ART and play with it a little to see if it drasticaly improves it. It seemed to make a little bit of a difference on my S3.
Edit: You may want to add to the op, DO NOT enable ART. It sends it into a reboot loop.
Click to expand...
Click to collapse
bowguy said:
I found out how to enable ART on the Nook Color. When you select ART as the runtime in Developer options, the tablet reboots but gets stuck in a bootloop. The problem is during bootup, a lot of files are being converted but the Nook runs out of memory. Then it crashes, reboots and tries again and never gets past it. However the boot animation takes a lot of memory during this process.
Solution: Disable boot animation. What you need to do is open the File Manager app. Go to settings (lower right icon) and General Settings. Under Advanced, Access Mode, select either User Prompt or Root Access mode. You need to alter a root file. Any prompts you get make sure to allow superuser access.
Now navigate to /system touch on build.prop and open with "Editor". Add the following line to the end of the file:
debug.sf.nobootanimation=1
Save the file and exit File Manager.
DO NOT ENABLE ART NOW!!
First make sure you did this correctly by rebooting your nook. Make sure you DO NOT see the Cyanogen logo when it boots up - it will take a while with a blank screen and then go to your standard lock screen. If you see the animation logo, you did something wrong, try again.
Now you can enable ART in the Developer Options. When it reboots, wait a while (2 min?) then you should see the optimizing apps display. A basic install with gapps has about 85 apps to convert. This will take a while.
Report back with results!
Click to expand...
Click to collapse
We are working on it. There is a modification pending that might fix this but hasn't been tested yet.
tp2215 said:
Just flashed in it looks great! Feels MUCH smoother and snappier then 10.2. Minor issue that boot take a long time. It seems to me like the boot keeps freezing but eventually continues. No force closes or anything. I am trying now to enable ART and play with it a little to see if it drasticaly improves it. It seemed to make a little bit of a difference on my S3.
Edit: You may want to add to the op, DO NOT enable ART. It sends it into a reboot loop.
Click to expand...
Click to collapse
fattire said:
Yeah, actually steven, if someone has issues with ART you might wanna link here. You can recovery from an ART bootloop w/o reinstalling or anything weird.
Click to expand...
Click to collapse
Yeah, release noted and added to the FAQ. We'd known about this earlier, but it slipped my mind when I was writing up the release notes
bowguy said:
We are working on it. There is a modification pending that might fix this but hasn't been tested yet.
Click to expand...
Click to collapse
Be aware that this may not work for you if you've installed to eMMC on a Nook Color with a 1 GB /data partition -- disabling the boot animation saves RAM, but won't prevent you from running out of disk space to store the ART compiler output (the "oat" files).
bowguy said:
We are working on it. There is a modification pending that might fix this but hasn't been tested yet.
Click to expand...
Click to collapse
If you compiled cm-11.0 with width 480 boot animation, ART will work. Initial boot and optimiziation will be longer than with Dalvik. You also get smoother boot animation. Also, revert boot to landscape in kernel config while you're at it.
tp2215 said:
Just curiuos if anyone has an oppinion to how cm11 is running on the device. I originally flashed cm10.1 when I first rooted and it ran INSANELY slow and laggy, probably due to the low ram etc. But was forced to run CM7 and it ran perfectly and have been running it ever since. I know that 4.4 is supposed to have lower dependencies for running on older/slower devices but anyone got some input on just how good it runs? I am going to probably try it later on tonight, it will just take me a while cause i got to backup my sons game data first or hill kill me.
Click to expand...
Click to collapse
Same here - both 10.1 and now 11.0 are slow. I was hoping a clean install and CM11 would cure the slowness.
I am at work and don't have my nook with me so will have to gather data tonight. its been along time since I even turned on the nook so I am no even sure what my memory config is.
But AWESOME work all you nookie devs!
For those that need them, here are flashable zips of CWM 6.0.4.7:
EMMC Recovery: http://techerrata.com/file/eyeballer/twrp/cwm-6.0.4.7-encore-signed.zip
EMMC AltBoot: http://techerrata.com/file/eyeballer/twrp/cwm-6.0.4.7-encore-ALT-signed.zip
Also, I've built an updated TWRP 2.6.3.0 which is compatible with CM11 and would appreciate some testers to confirm everything is working, please see here and report feedback in that thread only: http://forum.xda-developers.com/showthread.php?p=49886829
wifi bug
Only issue for me so far (on the 1/29) is that if I set settings/wifi/advanced to "keep wifi on during sleep/only while pugged in" it won't re-connect when waking up. Have to re-connect manually. Leaving wifi on permanently for now.
ibilln said:
Only issue for me so far (on the 1/29) is that if I set settings/wifi/advanced to "keep wifi on during sleep/only while pugged in" it won't re-connect when waking up. Have to re-connect manually. Leaving wifi on permanently for now.
Click to expand...
Click to collapse
drmarble posted a patch in the dev thread, so you can fix it if you're building yourself.
Sadly, the official nightlies aren't fixed yet. So I can confirm this known bug
I also had a reboot while displaying a gif in QuickPic. When it came back, the default launcher was reset and its init messages were shown
It's the first reboot I ever had on CM11. I attached the last_kmesg for your troubleshooting pleasure. I hope there's something valuable in there
The NookieDevs are pleased to announce the CyanogenMod 10.2.1 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: (not news if you've been keeping up with CM10.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. (Yes, we went backwards from the last 10.2 nightlies to avoid some rare crashes suspected to be related to the USB/charger port driver.)
All of the features of CyanogenMod 10.2, based on Android 4.3. All of the changes and bugfixes up to our last CM10.2 nightly (20140119) are included in this stable release.
Full 2D and 3D graphics acceleration using the GPU, with improved performance over previous releases.
Known issues:
Current releases of Netflix do not work with CM10.2 -- 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.
This release represents the end of active development on CM10.2 -- future efforts will focus on ROMs based on Android 4.4 and later. Critical bugfixes (for security holes, device-bricking bugs, eat-my-data bugs and the like) may be distributed as point releases (CM10.2.1.x); other important bugfixes (if any) will be distributed as patches on top of the 10.2.1 release.
Download:
https://download.cyanogenmod.org/get/jenkins/57353/cm-10.2.1-encore.zip
After flashing the above package, installing the latest kernel patch for CM10.2.1 is strongly recommended.
Code:
MD5: b4ad9daaf2335b96455795867dd5e667
SHA1: ae30dbc7946dd67a044dc972c8718628046a0c7c
SHA256: 0c35a2ab2592a83fb3b8c376c928ea1f9bb91da996d2928d51c6f9e898c48489
Source code:
https://github.com/CyanogenMod/android_device_bn_encore/tree/cm-10.2.1 (device-specific source)
https://github.com/CyanogenMod/android_kernel_bn_encore/tree/cm-10.2.1 (kernel)
https://github.com/CyanogenMod/android/tree/cm-10.2.1 (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 historically provided excellent support for its embedded platforms to the open-source hacking community.
XDA:DevDB Information
CyanogenMod 10.2 Stable, ROM for the Barnes & Noble Nook Color
Contributors
steven676, keyodi, fattire, The CyanogenMod Project, NookieDevs, many others (see post)
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 10.2.1
Stable Release Date: 2014-02-01
Created 2014-02-01
Last Updated 2014-06-06
Google Apps; other CyanogenMod builds
Google Apps
http://wiki.cyanogenmod.org/w/Google_Apps
As of 2014/02/01, the latest release for CM10.2 is 20130813, 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.2 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.1 stable releases -- while the state of the Nook Color-specific hardware support should be nearly identical to that of CM10.2, you may find this Android 4.2-based release more (or less!) stable than this Android 4.3-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?
How do I install this to an external SD card?
See this excellent guide by leapinlar for instructions.
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.2.1 stable, "cm_encore-userdebug 4.3.1 JLS36I bf3d49df9c test-keys") 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.)
The lock screen doesn't rotate!
The screen doesn't rotate to the sides I want!
Particularly if you're upgrading from an existing install, you may find that the preferences for screen rotations are incorrectly set. Go to Settings->Display->Rotation and check that "Auto-rotate screen" and (if you want the lock screen to rotate) "Rotate lock screen" are set.
For the allowed screen orientations, selecting 0, 180 and 270 degrees will cover the rotations that you probably want. If you want details:
Android likes to think of the "natural" orientation (0 degrees rotation) as landscape with the N key on the right side of the screen. (This is a change from CM10 and earlier, when we were carrying a hack to change this.) The degrees of rotation are counted in the counterclockwise direction, so in essence, each of the rotation settings allows the following:
0 degrees: landscape orientation with the N key on the right side of the screen
90 degrees: portrait orientation with the N key on top ("upside down")
180 degrees: landscape orientation with the N key on the left side of the screen
270 degrees: portrait orientation with the N key on the bottom ("right side up")
I'm having a problem with my Nook Color running CM10.2.
That's not a question
Okay, I'm having a problem with my Nook Color running CM10.2 -- 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.2? 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.
Is there any way to increase touch screen sensitivity?
The app in Google play is not compatible.
Thanks
Just check the Nook Color Dev Page if there are any Development, and Lo and behold! THANK YOU SO MUCH FOR STILL SUPPORTING NOOK COLOR! YOU GUYS REALLY ROCK!
Kernel security patch (upgrade strongly recommended!)
A security bug in the core kernel (CVE-2013-6282) allows users to read and write arbitrary kernel memory on machines with ARMv6k and ARMv7 CPUs -- including the Nook Color -- and is therefore exploitable for privilege escalation (root) by a local attacker on any device with those CPUs.
The attached kernel (source: https://github.com/steven676/ti-omap-encore-kernel3/tree/cm-10.2.1p1) contains a patch for this bug. The CVE entry notes that this bug has been exploited in the wild since October, so it's strongly recommended that you upgrade as soon as possible. (I apologize for this -- this is the sort of thing that I should have picked up much, much earlier than I actually did.)
CM10.1.3 users: you can use this kernel, but it'll break wifi unless you also rebuild the wireless driver modules -- use the kernel on the CM10.1 stable thread instead. CM11 nightly users: upgrade to a nightly from February 19 or later to get this fix. See my post on the dev thread for more information.
(If you're wondering, I am hoping to get a full CM10.2 point release with this fix included, but that may take some time, as a large number of other devices are affected and we should really try to get all of them fixed.)
Hashes for the attached kernel zip:
Code:
MD5: 991fc7c013f72dc950e32a7b08acd652
SHA1: 88664d4783c97184714ff94730546b36d634b40e
SHA256: 8aec80a185aeee358a68cc0f8aea062a56cef8f0a849c2c7382e4e14467d8b97
steven676 said:
A security bug in the core kernel (CVE-2013-6282) allows users to read and write arbitrary kernel memory on machines with ARMv6k and ARMv7 CPUs -- including the Nook Color -- and is therefore exploitable for privilege escalation (root) by a local attacker on any device with those CPUs.
The attached kernel (source: https://github.com/steven676/ti-omap-encore-kernel3/tree/cm-10.2.1p1) contains a patch for this bug. The CVE entry notes that this bug has been exploited in the wild since October, so it's strongly recommended that you upgrade as soon as possible. (I apologize for this -- this is the sort of thing that I should have picked up much, much earlier than I actually did.)
CM10.1.3 users: you can use this kernel, but it'll break wifi unless you also rebuild the wireless driver modules -- use the kernel on the CM10.1 stable thread instead. CM11 nightly users: upgrade to a nightly from February 19 or later to get this fix. See my post on the dev thread for more information.
(If you're wondering, I am hoping to get a full CM10.2 point release with this fix included, but that may take some time, as a large number of other devices are affected and we should really try to get all of them fixed.)
Hashes for the attached kernel zip:
Code:
MD5: 991fc7c013f72dc950e32a7b08acd652
SHA1: 88664d4783c97184714ff94730546b36d634b40e
SHA256: 8aec80a185aeee358a68cc0f8aea062a56cef8f0a849c2c7382e4e14467d8b97
Click to expand...
Click to collapse
Installed kernel could not get wifi working. Reverted to last nightly runs fine.
Both this kernel and the CM10.2.1 do not work with Network Speed Indicator - by fatminmin. http://forum.xda-developers.com/showthread.php?t=2636971 it is something to do with the 3.0.8 kernel build. This works fine with CM 10.2 nightly 1/19 and with CM11.
This ROM does not boot for me.
Full wipe, flash ROM and gapps, reboot, and sticks on black screen. No boot animation or anything.
Do I need the latest TWRP 2.3.6.0 to flash this properly? (On 2.3.1.0 now.)
Firehawk989 said:
This ROM does not boot for me.
Full wipe, flash ROM and gapps, reboot, and sticks on black screen. No boot animation or anything.
Do I need the latest TWRP 2.3.6.0 to flash this properly? (On 2.3.1.0 now.)
Click to expand...
Click to collapse
By full wipe did you mean a factory reset? Also check the md5 on the ROM.
2.3.1.0 works with the CM10.2 ROM. You can get TWRP 2.4.1.0 here :
http://forum.xda-developers.com/showthread.php?t=2653483
pastordl said:
By full wipe did you mean a factory reset? Also check the md5 on the ROM.
2.3.1.0 works with the CM10.2 ROM. You can get TWRP 2.4.1.0 here :
http://forum.xda-developers.com/showthread.php?t=2653483
Click to expand...
Click to collapse
Yea, factory reset. Tried two different downloads on two different computers. I'll try it and see with 2.4.1.0 though.
CM 10.1.3 works fine, and I had some of the January CM 10.2 nightlies running on it fine as well.
This was happening in November nightlies for me and it's still and issue in the stable release.
It's not a huge deal but it can be really annoying.
You know the open recent/open apps button in the bottom navigation bar?
All the other ones work but this button stops functioning relatively frequently, but of a pain because that's my main use for that tablet ui navbar.
By not functioning I just mean it does nothing when you press it, it's just a inactive button so to speak.
I can fix it (temporarily because it stops working again and again) by going into settings > interface > [navigation bar] buttons and layout.
And then just reset it.
Love the rom but this happens too frequently its quite annoying, anyone else have this issue, it's kind of a silly issue I hope there's some fix.
Thanks
Firehawk989 said:
Yea, factory reset. Tried two different downloads on two different computers. I'll try it and see with 2.4.1.0 though.
CM 10.1.3 works fine, and I had some of the January CM 10.2 nightlies running on it fine as well.
Click to expand...
Click to collapse
Try the 1-19 nightly available through this thread:
http://forum.xda-developers.com/showthread.php?t=2653483
Look under "Where can I get older releases" follow the link. You'll have to scroll down quite a bit.
They reverted to an older kernel for the "stable" release. I had some different issues with that kernel (see post 7). I stayed with the 1/19 nightly and have had no issues.
pastordl said:
Try the 1-19 nightly available through this thread:
http://forum.xda-developers.com/showthread.php?t=2653483
Look under "Where can I get older releases" follow the link. You'll have to scroll down quite a bit.
They reverted to an older kernel for the "stable" release. I had some different issues with that kernel (see post 7). I stayed with the 1/19 nightly and have had no issues.
Click to expand...
Click to collapse
Tried with TWRP 2.4.1 that you linked me to and still same problem. Must be the kernel as you say.
Will try the 1/19 nightly. Had they fixed the battery life/wakelock issue at that point? That was my only problem with 10.2. I get no wakelock problems and 4 or 5 days of battery life with CM 10.1, so I'll just stick with that if there are still issues in 10.2.
Thanks for your help!
USB Host Mode - sorry if beating a dead horse here...
I haven't checked back in a long, long time....but are there any kernel patches to enable usb host/peripheral switching?
Firehawk989 said:
This ROM does not boot for me.
Full wipe, flash ROM and gapps, reboot, and sticks on black screen. No boot animation or anything.
Do I need the latest TWRP 2.3.6.0 to flash this properly? (On 2.3.1.0 now.)
Click to expand...
Click to collapse
I was having the same problem with this as well. It wouldn't boot the loading screen. I gave up and settled for CM 10.1.3 which worked just fine. There's an option to update to 10.2 from the OS but I won't be taking that risk.
I was able to install 10.2.1 with no problems on a friend's NC. But with one of my own, the boot leads to a black screen. I did a factory reset, used a fresh download and tried from both TWRP and CWM. I have not yet tried to install on my other NC, whcih I know has different hardware.
Deleted
polymath257 said:
I was able to install 10.2.1 with no problems on a friend's NC. But with one of my own, the boot leads to a black screen. I did a factory reset, used a fresh download and tried from both TWRP and CWM. I have not yet tried to install on my other NC, whcih I know has different hardware.
Click to expand...
Click to collapse
It'd be helpful to know about the hardware on which the boot is failing -- could you fill out the hardware survey for that device?
steven676 said:
It'd be helpful to know about the hardware on which the boot is failing -- could you fill out the hardware survey for that device?
Click to expand...
Click to collapse
Done.
I don't know if this will be helpful or not, but I was able to get CM 10.2.1 to install on my other NC. I did a comparison of the hardware by using the website suggested (I did not file a report for the second NC, though). What I found is interesting:
1. Both devices are using ES1.2
2. Both devices are using ft5x06
3. Both devices have Mainboard serial numbers in the A6 series.
4. The device where the install *works* went thorugh some suspend/resume cycles on ft5x06 and did reset_panel_via_gpio several times
5. The device where the install *fails* did not go the suspend/resume cycles or the resets in 3.
6. The device where the install *works* was made on 09/03/2011
7. The device where the install *fails* was made on 10/09/2011
If there is any more information or help I can provide, let me know.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Current Events
Dodo released! This means this ROM is now extinct. Sorry! If links below fail, try this one!
OTA is in Beta. Will be included in CM 13 release once both are stable. OTA will be available before full-sized versions due to the testing process (updates are tested first).
SnapChat will not work without some help. This is entirely SnapChat's fault for trying to control your device. Please read this thread before flashing and how you can make it work. Or just open Xposed installer, install Snapprefs and reboot.
Introduction
Welcome to the fastest and most stable ROM for your OnePlus. This thread is mainly a support thread for Jgcaap's awesome work, allowing him to spend more time working on "M" and less time answering questions. His latest builds will be tested by me, hand selected for stability, and the best of the crop will be repackaged, enhanced, and placed here. If you are new to this ROM, check the screen shots for benchmark results and battery life screenshots. Be amazed, then download the ROM and be even more amazed! Smooth as glass and flows like water! As one person has said, "Disgustingly Fast!"
Please read this entire post! Check back often for updates. Also, current jgcaap users will get additional information and tips that can be useful. Check out all the links! And if you want to try some Bacon wrapped Marshmallow, click the bent arrow in the Announcement's line.
Wildlife
Each ROM will be named by an animal, starting at A for Aardvark. A picture of the animal will be placed here so you can see at a glance which release is current. The original jgcaap ROMs often have multiple releases in a single day, and every country has a different date format, so the animal names will allow us to represent specific "official" releases with memorable names.
Release (CM 12.1 - jgcaap 11/30): (click image to update)
Downloads | Other Stuff | Links
Features & Changes
The ROM gets repackaged so that new users don't have to go about tracking down which files they need and which order to flash things. The firmware is included and everything is set and ready to go. For legal reasons, just add your own GApps and go. This ROM currently has the following feature's prepackaged and already included with the ROM ...
SuperSU (pre roooted)
Xposed (special jgcaap version)
Moab Ad Blocker
--- ZooKeeper can configure this!
ColorOS Camera
--- with manual focus option
Viper (Audio Eargasm)
Dolby ATMOS! (Dodo+)
Send Reduced (send small pics)
CatLog (for bug reports)
Show On Lockscreen (wallpaper)
OmniSwitcher (optional)
Init.d Support (Badger+)
Governor: blu-active (Badger+)
Low call volume fix
OTA Support (coming soon!)
Support, Questions, Feature Requests and Bugs
Please report all bugs for CM12.1/Lollipop based Jgcaap ROMs to this thread. Even if you didn't download one of the Wildlife pre-packaged ROM sets! Feel free to ask questions. This thread will have the same warm inviting atmosphere that jgcaap's development thread has always had. Newb-friendly and all are welcome!
Getting Started
There will be two ROM images available. The update packages will be designed with a smaller download size with only the files that have actually been changed. The installer will not remove things you have added nor re-install programs you have removed. If you are already using a WildLife ROM, use the Update packages to upgrade. This does not apply to full versions. The full versions should be clean flashed.
The next post will have Step-by-Step instructions telling you exactly what you need to do and how to go about flashing your phone or upgrading. The post after that will have all the tips and tricks for maximum tweaker power. Finally, we'll have instructions on how to rescue your phone when something goes wrong.
Sponsored by Eddon Systems
Additional Downloads at Eddon Systems Download Page
XDA:DevDB Information
Wildlife Android, ROM for the OnePlus One
Contributors
uudruid74, jgcaap, purerawenergy
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: INCLUDED
Source Code: Jgcaap's Github Repo
Based On: CyanogenMod 12.1
Version Information
Status: Stable
Current Stable Version: See Post
Stable Release Date: 2015-11-16
Created 2015-11-16
Last Updated 2015-12-11
Flashing WildLife
Flashing Instructions - Full ROM
Step 1 - Backup
If you don't have a backup program, you can grab a really fast and free one, Backup+. XDA Forum | My Mirror - Direct Download. Be sure you keep the APK on your Internal Storage so you can install it easily and restore the rest of your apps. Also, I strongly recommend you copy your internal storage (or at least the backup directory) onto a PC, a harddrive, a flash drive, or cloud storage such as Google Drive. Get it off your phone and make it safe.
Step 2 - Boot into Recovery
Even if your reboot menu doesn't have a Recovery option, you can always just hold down the Volume Down button when your phone boots and you're good. I recommend Philz Recovery from this XDA thread or you can download the exact ZIP I use.
Step 3 - Wipe Carefully
This step is what is known as a "clean flash". Do not perform this step if you are flashing an upgrade or addition. If this is the first time you've flashed this ROM, you want the full version and you want to do it cleanly. Failure to clean flash leads to odd problems. For example, Agent stopped reading my calendar, or my Camera plugins would start to disappear.
You do not want to do a Factory wipe or anything like that or you'll lose all your data. Do not format /data. Here's where it gets confusing. Many recovery systems treat /data and Internal Storage as if they were separate partitions, but they are not. Your internal storage is on the same partition as /data. If you are from Windows, image your /system is your C: drive, and /data (where your apps are at) and your internal storage are both on D:. Your recovery has a specific wipe designed to safely wipe /data without wiping out your internal storage by erase directories individually, yet automatically.
Philz makes this simple and direct. Select Wipe and Format Options, then select Clean to Install a New ROM. Confirm the wipe, and you are ready to go.
Step 4 - Flash the ZIP
This is pretty easy. Select the option to flash it, find it on your device, and away it goes. If you downloaded the file to your PC (or wiped your internal storage and now have no files on your phone), you can use the "sideload" option you see in the menu. Just plug in a USB cable and type: adb sideload Aardvark.zip This does require that you have adb drivers set up on your PC, but you needed that to unlock your bootloader, right? More tips like this in a later post!
Step 5 - Flash your Gapps
The most important part of Gapps is making sure its for Lollipop. The more up to date, the better. You should download the smallest GApps that fits your needs, just so you don't have to download so much. You can specifically control which Gapps are installed with a config file. Just drop the gapps-config.txt into the same directory as your gapps ZIP file. This file can even delete crufty Cyanogen apps that you don't need or want (you have better ones from Play store right?) and reduce bloat considerably.
About the Gapps Config | OpenGapps is the recommended Gapps package | Newer Sources for Gapps | My gapps-config.txt ... note: you might not want to use my config unless you want almost all your Cyanogen apps to go away. When the system comes up, you won't have a file manager to install Backup+. I install it with "adb install BackupPlus.apk" or if its on the phone, you can log in with adb shell and then install with pm install $PWD/BackupPlus.apk
TIP: If you have Chrome installed from Gapps, you can open it and type "file:///sdcard" in the URL window and then select your Backup+ or Titanium Backup APK to install it. Be sure you have "Install from unknown sources" turned on. Now you can restore your good File Manager (like FX File Manager mentioned in Post #5) from your Backup and don't need Cyanogen's!
NOTE: If you have trouble with OpenGapps, then you can try my stable mirror or SlimGapps (which is now recommended by jgcaap, but I've not tried it myself yet ... but expect it to be the new recommended after I run it through the paces).
Step 6 - Reboot your Phone
After flashing, the first time your phone comes up, its going to optimize itself and you should expect it to take awhile. Don't panic, and wait a few minutes. I refuse the CyanogenMod account (you already have a Google one, and Cyanogen doesn't offer anything extra and defintely do NOT send bug reports or analytics to Cyanogen!). I also go into Settings, About Phone, tap the Build Number like a mad monkey to turn on Developer options, and from there, I enable the Reboot Menu, Fast Boot, Cut the animations down to below 0.5, and turn on ADB since I'll be installing Backup+ over ADB.
Step 7 - Restore your Backup
Use your file manager (or ADB) to install your backup program and then restore the rest of the apps from your backup. I keep my Wifi off so that Google Play won't freak out and try upgrading stuff while its restoring. Do not use ROM Settings Backups to try to move settings from one ROM to another (thats what Update files are for). You can usually restore your Desktop with Backup+ by restoring the data for Trebuchet if you formerly used another Cyanogen release. The next reboot I go to Play Store and upgrade any apps that need it.
Step 8 - Final Config / Updates
I haven't found a perfect way to back up Trebuchet and my desktop ... but Backup+'s system backup tool (paid feature) can be used to restore the Trebuchet data, which gets everything but the widgets. If you use OmniSwitcher, just turn it on. If you use Xposed, it should already be working and active. If you don't use Xposed, jgcaap's version won't slow down your phone or cause glitches. However, if you really don't want it on your phone, you can flash this to deinstall it and can reinstall it without flashing the whole ROM by flashing this file.
MaxxAudio is gone ... use Viper. Set it to Super Audio Quality and reboot when it says to (Aardvark only, no reboot required for Badger and above). More about Viper here. I strongly recommend reading as there are a lot of optional add-ons (convolvers and such for emulating other tones and systems) but many of these will use significant battery power. I don't even use it for the built-in speaker. You can control it per output device, and have different profiles, such as if you have multiple pairs of headphones or different USB Audio devices.
Please Donate to the developers when you use an app. It is only through your support that you get to use high quality apps. This ROM has ads blocked, so developers of free apps will go poor and hungry since they won't be getting any revenue from your ad clicks!
Flashing Instructions - Updates
An update is a slimmed down version without any apps (unless they've been updated), no firmware, no media files, etc. And it avoids flashing over files you may have changed or deinstalled, like the hosts file or various bundled apps. It doesn't touch your settings, you don't need to wipe anything, and it just upgrades in-place. All you need to do is Steps 2 and 4 and 6!! Updates are clearly labelled. Never wipe your phone when installing an update! No OTA yet.
Tweaking
Tweaking, Trimming and Theming
Kernel
There is a UKM for jgcaap's kernel which is in the download area. You'll need Synapse from Play store to use it. I don't recommend tweaking the kernel, but if you want the option it is there. Just download the ZIP, flash it in recovery, and you can start tweaking some kernel parameters! Personally, I use 3C Android Tuner (see below) because it can tune more than just the kernel, but you might find something UKM does that 3C doesn't. As as Badger, you can use the init.d script option for restoring settings imposed by kernel tweakers.,
Governor
Your governor controlls when your CPU is at full blast, when it throttles down, and how quickly it changes and by how much. This will affect battery and performance (and "lag") considerably. As of Badger, the default CPU governor is "blu_active". You won't need to ever change to "Performance" mode to squeeze out more power, its runs even more fluid than before, and battery life is as good as ever. There are a couple ways to select the governor. The one I use is 3C (below). The only source of lag is memory. If you run out and Android has to swap stuff out, there will be a noticeable delay. If you rarely get lag, but get it rather severely, I bet its when you have 20 apps open and a million installed with their own background services and content providers! Suddenly the OOM (Out Of Memory) killer attacks and your phone stops for a second or two. I'm testing a possible solution, but everyone's phone is different.
CPU Temp
How hot does your CPU get? If you run Cardboard like me, you might be concerned. If you have to switch to an app to find out, then your CPU will have already cooled by the time you see the temp. This CPUTemp App displays an overlay anywhere you want that will show you your exact temperature. It can also save the data and give you in-depth graphs of CPU speed, load, and temperature. Alternately, you can just use this Xposed module to always show the CPU temperature in your status bar. (WARNING: I've not tested this Xposed module myself).
Xposed
Wildlife already has Xposed installed. If you have heard of requirements that your ROM must be deodexed or odex or and that you will have compatibility issues or slowdown, the current news is that the latest Xposed works on odexed ROMs and jgcaap has personally blessed some modifications to increase speed and compatibility with this ROM, and final result is packed into Wildlife. However, until you install some Xposed modules, it lies dormant. Fire up the Xposed Installer and you can start searching for tools to tweak how your phone looks, how it acts, how it sounds, and tweak some more battery life. Once you install a module, activate it, and then reboot.
Please be aware that not all Xposed modules are compatible with Lollipop and not all modules are created equal. I have heard mixed reports on GravityBox in particular. If for some reason your phone gets horribly confused and won't boot because of some Xposed module you have installed, or if you just hate the idea of having Xposed and want it gone. There is a solution! Flash this Xposed Uninstaller and if you flash this and want Xposed to come back, just Flash Jgcaap's modified v75 Xposed framework.
Ones I use are the 3C Toolbox helper, Clarity (makes your contacts in better definition), No Device Check (privacy), RootCloak (hides root), Smart Network (auto switches between 3G and LTE to conserve battery).
3C ToolBox
If you like tweaking, this toolbox has a little bit of everything. You can view logs, including last kernel boot log (the one that ran before you crashed), open a terminal, set a firewall, change CPU and GPU governors, disable services, remove programs from the start-up list, change network congestion control ... the list goes on and on!
Here is the XDA thread (with download links) for this tweaker's toolbox.
Battery Extensions
The first step to checking battery problems is Wakelock Detector and Better Battery Stats. These tools will tell you where your juice is going. If an app is holding a wakelock, ditch the app or alert the developer. Once you see what is chewing the most battery you can launch an assault on it with these tools:
Xposed Modules - Again, I'm going to defer to an expert source, @V7 's Extreme Battery Life Thread for all the goodies on PowerNap, Greenify, Amplify, and all the others that you've heard about.
Underclocking - I simply do NOT recommend this. Why? Well I checked Better Battery Stats! And my CPU had only been at full speed for 6% of the time. The next speed was under 2Ghz. So, is it worth slowing down your phone by 20% in order to achieve an overall savings of about 1.2% battery? The reason for this is that your system has what's called a governor that predicts how much CPU you need at any given moment and adjusts accordingly. This means you only use max CPU when you need it! If you underclock, then you are slowing down your phone when you need it most. You might even waste more battery because you'll be keeping your screen on longer waiting for your phone to finish!
Undervolting - I don't like this idea either. Basically, the voltage is how much strength it takes to open the transistor gates, like little doors. When your CPU gets busy, the voltage can fluctuate by small amounts, and if you undervolt your CPU, you can occasionally get a gate that doesn't open, and your get a CPU doing really crazy things and some app with crash or your whole system will crash. Generally, higher speeds require higher voltage to keep your CPU stable, and less voltage at lower speeds. Imagine trying to open and shut a door really fast ... you'll need more force than just shutting the door gently.
Can I get 9hrs SOT? - Sure! See the screen shot, but here's the secret. WASTE battery power! If you have a flip-case, remove it. Take your screen timer and set it REALLY high and don't turn off your screen. Let it BURN! This will ensure that your screen is on for a really long time. Cheating? Well, yes and no. The point is that someone who is chatting on their phone over Wifi and rarely touches it, but leave the screen on while doing so will get great SOT. The guy streaming Bluetooth audio all day long and has their phone tethered to use LTE internet with a low signal will waste tons of battery and may not have the screen on at all. The 9hr screen on time was done while doing all the above, plus some web browsing using ....
Ultimate Browser - This browser is said to use less battery than Chrome and others. You can check it out and see for yourself on The Ultimate Browser XDA thread.
Themes
Many people ask about the themes pictured in the screenshots. This is the Deep Darkness Overhauled Theme but with the thinner fonts from Cosmos CM12. Just select which parts of each theme you like before clicking the Update button.
I'm now using an Add-On package for this theme that gives icons that aren't so dark. It has a cool font, too, but I don't know if I like the Cosmos or Deep Darkness Add-On better. I'm also using a compromise between the 400 DPI (real) and 480 DPI (stock) of 440 DPI. This still gives me 5 icons wide on the home screens without throwing off apps that expect stock DPI (much).
Rescuing Your OnePlus From Disaster
Rescuing Your OnePlus From Disaster
I sure hope you never need any of this information! The following links are from Heisenberg's OnePlus One thread
Device Recovery/Unbrick Tools
[TOOL] One-Click Backup & Restore EFS on OnePlus One
[TOOL] OnePlusRecovery Tool | Restore Stock (CM11S) | Fix Bricks | ETC
[TOOL] OnePlus One Return To Stock - Automated!
[GUIDE] [UNBRICK] Unbrick Oneplus One
I originally intended to post a step-by-step, but instead I'll defer to existing/tested sources. Heisenberg's thread has tons of useful information and is well worth checking out.
More Info
Link Database
Someone has an awesome thread listing all the links you could ever ask for, so I'll defer to those that are already maintaining this. Here you are ...
http://forum.xda-developers.com/showthread.php?t=2843675
Recommended Apps
Please note that these are some of the best of the best, and most of them are not free!
Email - [email protected] Mail This is a fork of K-9, which is the Android Mutt (from Dr Who) .. mutt being a classic Unix mail program. I love Dr Who, but [email protected] was such a big improvement, I had to go with it. If you need full folder support, multiple accounts, and support for email cryptographic signing and encryption, multiple identities, and html editing of email and html signatures!
Music Player - PowerAmp - this is by the best music player I've used, bar none. If you don't want it messing with your custom lockscreen wallpaper, you can tell it not to, or add a whole second/custom lockscreen over the original. It has its own EQ, but I don't need it with Viper. To make PowerAmp compatible with Viper, simply turn off the direct volume control. You can use Xposed to add more volume steps if you like the extra control that PowerAmp's default has.
Video Player - VLC Video Lan Client Plays everything, does everything, streams videos, and has remote control apps to connect to other VLCs anywhere on your network.
QuickPic - QuickPic is a replacement for the stock Cyanogen Gallery. It works and acts much the same only its much much faster. Another good choice is Piktures, but new users may find it a bit more complicated, and it doesn't seem to be nearly as fast.
Agent - While much of what Agent does can be duplicated with other tools, the ease of use and flexibility of this tool can't be beat. It monitors your calendar for meetings and silences your phone, knows when you are driving and responds to your texts (and/or reads them to you), detects when your sleeping and makes your phone quiet (even if you sleep at different times). Has a battery saver mode, and can even remember where you parked. The Meeting agent works best if your calendar supports the "Busy" flag, which Google removed about a year ago, so ...
Today Calendar - The Today Calendar is just a really beautiful app and has some nice widgets (although I just use cLock from Cyanogen to show my calendar and make appointments via Voice commands, so I don't see Today much, I still bought it). It has the Busy flag and all sorts of features. If you want one a little less flashy (and free), try Boxer Calendar.
File Manager - The FX File Manager is by far the greatest file manager. It has everything built in, including SMB to network with Windows and SFTP to network with any machines running SSH. App Management, Media Refresh, and nice clean material design! Bloat free!
FXR Wifi Repair - Get this app and install it NOW! You will thank me the day you end up needing it!
Project Toolbar
For those on Tapatalk that don't get the toolbar, here it is ...
Downloads
ScreenShots
Reviews
Feature Requests
Bug Reports
.
I'm running 12.1-20151030 deodexed version. Could you provide me links to proper Xposed installer? Or is it ok to flash that one package with all that installed?
Sent from my A0001 using XDA Free mobile app
Tyga187 said:
I'm running 12.1-20151030 deodexed version. Could you provide me links to proper Xposed installer and Viper? Or is it ok to flash that one package with all that installed?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Don't know if 10/30 needs deodex or not but if its before jgcaaps hacks you'll need the older Xposed. I have it and Ill upload it for you to my site (Eddon Systems Download Page ... link in first post). Viper is already there (look for LolliViper).
If you don't mind taking the time to do a clean flash, Aardvark is based on the 11/08 build with the Apple code. All works out of the box Dirty flash possible, but can lead to weird problems.
I'll upload Xposed v75 right now
More about me at https://eddon.systems
Ok so it is possible to run odexed version and have Xposed working? I've heard that I need deodexed version for exposed that's why I'm on 20151030.
Thanks a lot for fast response!
Sent from my A0001 using XDA Free mobile app
Deodex and Xposed
The newer builds are made in such a way that you can use them with Odex builds without problems. We even have a special "Hacked" version of Xposed that prevents the possible slowdown issues and bypassing jgcaap's ART improvements.
So yes, use Odex and new builds and preferably the "Hacked ZIP" for the framework, although normal v75 still works. Or flash Aardvark. I've got maybe a dozen Xposed modules active.
The reason you don't see newer Deodex is because they aren't needed anymore
uudruid74 said:
The newer builds are made in such a way that you can use them with Odex builds without problems. We even have a special "Hacked" version of Xposed that prevents the possible slowdown issues and bypassing jgcaap's ART improvements.
So yes, use Odex and new builds and preferably the "Hacked ZIP" for the framework, although normal v75 still works. Or flash Aardvark. I've got maybe a dozen Xposed modules active.
The reason you don't see newer Deodex is because they aren't needed anymore
Click to expand...
Click to collapse
Which build has Apple code ? Normal odexed build , deodexed or bionic build ?
lokesh.3440 said:
Which build has Apple code ? Normal odexed build , deodexed or bionic build ?
Click to expand...
Click to collapse
It varies based on date and jgcaap's whim. The 11/08 builds do. I don't think any deodex builds do because he stopped making those before the Apple assembler code experiments.
Since 11/08 has it, Aardvark has it.
Bionic isn't a ROM build, its the Android low level C library to which the Apple code is being added.
More about me at https://eddon.systems
uudruid74 said:
It varies based on date and jgcaap's whim. The 11/08 builds do. I don't think any deodex builds do because he stopped making those before the Apple assembler code experiments.
Since 11/08 has it, Aardvark has it.
Bionic isn't a ROM build, its the Android low level C library to which the Apple code is being added.
More about me at https://eddon.systems
Click to expand...
Click to collapse
I m downloading latest build now.
Good job Evan. This will definitely help Jorge and the Marshmallow project. Thanks in advance brother.. See you on the testing ground.
Tom 2.0
Purerawenergy said:
Good job Evan. This will definitely help Jorge and the Marshmallow project. Thanks in advance brother.. See you on the testing ground.
Tom 2.0
Click to expand...
Click to collapse
I'm going to be stealing your post you made in the other thread about battery tweaks ... Greenify, Amplify, PowerNap and all that. It will go in the tweaks post. Let me know if that info is changed and if you can remember the date or post number for when I go digging.
More about me at https://eddon.systems
uudruid74 said:
I'm going to be stealing your post you made in the other thread about battery tweaks ... Greenify, Amplify, PowerNap and all that. It will go in the tweaks post. Let me know if that info is changed and if you can remember the date or post number for when I go digging.
More about me at https://eddon.systems
Click to expand...
Click to collapse
You may want to link my buddy @v7 in there somewhere if you want. He's the wake lock master Bro. And his helpfulness is awe inspiring.
Tom 2.0
---------- Post added at 03:36 PM ---------- Previous post was at 02:50 PM ----------
Oh and it's not stealing if you ask someone. Haha
Tom 2.0
Purerawenergy said:
You may want to link my buddy @v7 in there somewhere if you want. He's the wake lock master Bro. And his helpfulness is awe inspiring.
Tom 2.0
---------- Post added at 03:36 PM ---------- Previous post was at 02:50 PM ----------
Oh and it's not stealing if you ask someone. Haha
Tom 2.0
Click to expand...
Click to collapse
Actually, I put your name in as a contributor (and obviously @jgcaap) which gives you a lot more access. That way, if I'm hit by a bus tomorrow, other people can step in (its the admin in me). You might be able to edit the project page and initial reserved posts yourself.
My routed here is getting old so I'm doing a reflash and adding a captive portal to disconnect people when there isn't a human body using it. I need to cut down on everyone's bandwidth usage. So ... gonna be a busy night.
More about me at https://eddon.systems
uudruid74 said:
Flashing Instructions - Full ROM
If you don't have a backup program, you can grab a really fast and free one, Backup+. XDA Forum | My Mirror - Direct Download.
Click to expand...
Click to collapse
Hi,thanks for this thread. I've downloaded aardvark but for the backup+ download from : https://eddon.systems/Download/Backup+_Beta_1_R2.apk I get a 403 forbidden.
Verstuurd vanaf mijn A0001 met Tapatalk
I am going to download your rom and test it in a couple of days
Wysłane z mojego A0001 przy użyciu Tapatalka
Well this came around at a perfect time! I haven't been actively flashing my phone much this year and my current ROM is from July 5th lol. So I'm not really new, but could use something pre made like this. Reading, backing up, and downloading this afternoon, then flash later tonight. Thanks for putting this up.
Is the rom ok to flash on system/data/cache on f2fs ?
In the last few weeks my phone seems to have gotten worse and worse. I have a L24 running LineageOS, and as of late it has gotten laggy doing general tasks. I was wondering what ROM, gapps, and kernel seems to have the best performance?
How far have you gone into the system? It may be that something has changed your performance parameters. I’m sure I’ve had mine as long as yours, and yes, extensive modifications make it keep up with what’s new. Here’s how mine is set up anyway.
Using twrp, aicp nightly rom( June 23, 2017, before radio problems, problems after that date). SE Linux still enforcing. Hotdog kernel( you could use astral too) , kernel aditor for tuning needs( lots of things you can tune, but study first before changing things), magisk with no super su remnants) xposed, etc.. Internal, sdcard, as one, with ability to put some apps on sd. Changing governors(and some parameters of it), I/o , entropy, and low memory killer , keeps it snappy enough, and battery’s still good. There are other things but that’s it. If you have twrp, clear cache, and data before, that may be it too. I use mini gapps.
reggjoo said:
How far have you gone into the system? It may be that something has changed your performance parameters. I’m sure I’ve had mine as long as yours, and yes, extensive modifications make it keep up with what’s new. Here’s how mine is set up anyway.
Using twrp, aicp nightly rom( June 23, 2017, before radio problems, problems after that date). SE Linux still enforcing. Hotdog kernel( you could use astral too) , kernel aditor for tuning needs( lots of things you can tune, but study first before changing things), magisk with no super su remnants) xposed, etc.. Internal, sdcard, as one, with ability to put some apps on sd. Changing governors(and some parameters of it), I/o , entropy, and low memory killer , keeps it snappy enough, and battery’s still good. There are other things but that’s it. If you have twrp, clear cache, and data before, that may be it too. I use mini gapps.
Click to expand...
Click to collapse
Thanks for the response, I'll try out aicp and the various other modifications. I haven't messed around with custom kernels much what would you recommend I focus on?
AICP is a nougat ROM. There's no updates for it, but it's stable. Lineage is good too, and there's still devs on it. Resurrection Remix is another. These are all nougat ROMs. Mostly anything that you flash, except specified, should go to the /data folder.
PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
NOTE: There is no S-pen support. If you need S-pen, DO NOT USE THIS ROM.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom. If you are new to flashing custom roms, do NOT attempt this. If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. camera (selfie photo preview doesn't work), a bit slow to switch from front to back camera and vice versa
9. selinux enforcing
10. DRM level 3
11. deep sleep
What doesn't work/What isn't tested
1. gapps. Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of gapps.
There are various gapps projects (at least 5 in 2022). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours/days doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread.
2. full disk encryption has been deprecated in Android 13 (LineageOS 20).
3. S-pen doesn't work and I have no plans to even try to make it work.
Source Code
The build instructions, source code and manifest are listed in post #2 FAQ #1. The kernel source code is at
https://github.com/retiredtab/android_kernel_samsung_msm8916/tree/lineage-20.0
Thanks
1. LineageOS team for source code.
2. LineageOS-UL team for merging, maintaining the legacy patches needed for old devices into one common repository so everyone can benefit.
https://github.com/orgs/LineageOS-UL/people
3. @lpedia for helping test a msm8916 tablet device.
FAQ - I spent hundreds of hours building this rom. If you think it's unreasonable to read this FAQ, then don't use this rom. Thank you.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
https://github.com/retiredtab/android_kernel_samsung_msm8916/tree/lineage-20.0
The device tree files are at
https://github.com/retiredtab/android_device_samsung_msm8916-common/tree/lineage-20.0
https://github.com/retiredtab/android_device_samsung_gt5note10wifi/tree/lineage-20.0
https://github.com/retiredtab/device_samsung_gte-common/tree/lineage-20
The vendor tree files are at
https://github.com/retiredtab/vendor-samsung-gt5note10wifi/tree/lineage-19.1
https://github.com/retiredtab/vendor_samsung_msm8916-common/tree/lineage-20
The manifest.xml (or roomservice.xml) and build instructions for 20 are at
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/20/msm8916
Q2. Is this ALPHA rom suitable as a daily driver?
A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since mid Jan 2023 with no major issues. I suggest you do a clean install, see FAQ 11, and flash this 20 ROM BY ITSELF (no gapps, magisk, etc) and see if you like it.
Q3. What if my app, xyz, doesn't work?
A3. If your app doesn't work, then go back to your old rom.
Q4. Your rom is laggy and buggy.
A4. If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps. You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.
Q5. What TWRP should I use?
A5. You MUST use TWRP 3.5.2_9. Get it from
https://sourceforge.net/projects/retiredtab/files/SM-P550/TWRP/
Q6. Why should I use this rom?
A6. If you don't like this rom, then don't use it.
Q7. Will you offer monthly updates with security patches?
A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.
Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
A8. I don't have the time to help newbies, so please do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here.
Q9. Can I report a bug with respect to the rom?
A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.
To get a logcat, open up a terminal window.
Code:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occured, then stop trace by hitting ctrl-c
# attach the problem.txt ZIPPED as text files don't seem to get attached properly
Q10. Do I need to erase everything and format my data?
A10. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 19.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.
Q11. What gapps should I use?
A11. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary.
Let me by crystal clear. YOU NEED TO DO YOUR OWN HOMEWORK selecting between the various gapps offered. There are 5: opengapps, nikgapps, mindthegapps, flamegapps and bitgapps. Each one will have it's own installation instructions. The only recommendation I will offer to use the SMALLEST version of gapps.
Don't be surprised that whatever gapps you use might have problems like "Just a sec", voice not working, updating google play store please wait, etc. These are NOT problems of the OS as the OS will run fine without gapps. These are gapps problems and you must ask in the gapps forum why it doesn't work.
Q12. I'm having problems with gapps, can you answer why it's not working?
A12. I WILL NOT answer any questions regarding gapps. This thread is about the rom, not gapps. Android does not depend on gapps in order to work.
Q13. Why isn't my post answered or ignored?
A13. Questions already answered in the FAQ will be completely ignored. Again, I do not use Windows OS or gapps.
Q14. What speed up/optimization tips do you suggest?
A14.
1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
3. Dont' run more than 2 apps at the same time. You can probably listen to music in the background and use a web browser at the same time, but don't expect great performance from a 2015 entry level tablet.
4. Use a web browser like Brave that has built in adblock and privacy features.
5. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
6. Look for apps that are open source, ad free and lightweight.
7. Remove all unused quick setting "bubbles" from the quick pull down menu. I only need and have 6.
Q15. Does this rom support Magisk for root?
A15. I don't use Magisk myself so I don't know and Magisk is always being updated to fool Google's certification process. Others have reported Magisk as working, but I won't answer any questions regarding it.
Q16. Will this rom ever become official?
A16. Starting with 19.1, legacy devices like ours will NEVER be official due to lack of ebpf support. See https://lineageos.org/Changelog-26/
Also, I don't want the responsibilities that come with being an official maintainer.
Q17. What is the difference between this rom and others?
A17. This rom tries to be pure LineageOS with little to no modifications.
Q18. Will there be any major 20 code modifications in the future?
A18. I don't anticipate any major modifications. There may be some small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been done completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 20 is working.
Q19. Why did you fork the device and vendor trees for 20?
A19. The msm8916 repos seem geared towards phones and sometimes do not work or cause boot animation loops for tablets so I decided to fork their repos. In other words, what's deemed as msm8916-common code isn't common to all devices.
In addition, since I'm building SM-T350, SM-T357W, SM-T550, SM-P550 and SM-T560NU (all use the same msm8916 code), it seems easier to maintain all of them if I can control my own code repos and not worry if my changes affects the phones or not.
I have completely decommonized and rearranged the 20 msm8916-common tree so it's easier for me to maintain and build.
Q20. Can you build a variant of this device? For example, a LTE or S-pen version.
A20. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working.
Q21. Can I load this rom on a variant devivce like LTE or S-pen version?
A21. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!
Q22. I don't like the taskbar, how do I turn it off?
A22. Choose settings, type task into the search bar. Choose enable taskbar and disable taskbar. This will leave the on screen nav bar. If you want to disable that, go to settings, system, gestures, system navigation, gesture navigation.
Q23. Okay, I understand the consequences and that this is ALPHA rom and willing to take the risks outlined, now where can I find the rom?
A23. You can download it from https://sourceforge.net/projects/retiredtab/files/SM-P550/20/
Release notes
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.
June 23, 2023
1. Initial 20 ALPHA public release.
2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2023-06"
Reserved.