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
Related
Q&A: [ROM-1.2/GRJ90] CM7Tab for the GTab (based on CM7 Nightlies) [Update: 08-15-11]
MOD EDIT: THIS IS THE Q&A SECTION FOR [ROM - 1.2] CyanogenMod 7 nightlies for the GTab
ALL Q&A FOR THIS ROM HAPPENS HERE.
Thanks.
---------------------------------------------------
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.43 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
1) latest version of CM7Tab: CM7Tab build 08082011 (Nightlies changelog)
2) Test CM7Tab with 4950 drivers: Test Build 08152011
Changes in modified version
1- replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2- vold.fstab is setup as sdcard for internal storage & emmc for external card
3- using pershoot's 2.6.32.43 GB kernel for 1.2 bootloader (For more info, check his blog.
4- Read_ahead_kd increased from 128 to 2048.
5- Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6- Replaced Camera libs & apk to stop the 8-bit pixelling.
7- Increased dalvik.vm.heapsize to 64m (07102011)
8- Set some values to improve video playback (07272011)
9- Changed values for lowmemorykiller minfree in init.rc (08072011).
10- changed EMMC to microsd (08072011)
11- updated ROM up to 2.3.5 (08072011)
12- Camera fix (08082011)
To-do list:
1- remove some apks (such as Rom manager) & create a removed apks folder.
--------------------------------
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified): Latest build: Build 07262011 (Changelog)
If you have suggestions/ideas, do not hesitate to share them.
thank you.
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
nelomen said:
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
Click to expand...
Click to collapse
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Icewyng said:
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.42 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified):
Latest build: Nightly build 07112011 (Changelog)
2) Modified version of the ROM: CM7Tab build 07102011
Changes in modified version
1) replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2) vold.fstab is setup as sdcard for internal storage & emmc for external card
3) using pershoot's 2.6.32.42 GB kernel for 1.2 bootloader (For more info, check his blog.
4) Read_ahead_kd increased from 128 to 512.
5) Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6) Replaced Camera libs & apk to stop the 8-bit pixelling.
7) Changed values for lowmemorykiller (07102011).
8- Increased dalvik.vm.heapsize to 64m (07102011)
RC1 version of the rom with changes: 7.1.0 RC1 with Pershoot 42 kernel
(Sorry if this is short but I will improve the thread as it goes)
To-do list:
1) remove some apks (such as Rom manager) & create a removed apks folder.
2) change the EMMC to Sdcard2
If you have suggestions/ideas, do not hesitate to share them.
Click to expand...
Click to collapse
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Icewyng said:
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Click to expand...
Click to collapse
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Edit: have been trying for a couple of hours now but sent me in to boot loop had nvflash back to stock, will give it another shot once this silly Tap n Tap is finished loading.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
rob_z11 said:
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Click to expand...
Click to collapse
Dalingrin was kind enough to provide a fix that seems to resolve most of the problems with market (including buying apps). It was merged in build 07092011+ so give it a try and tell me how it goes.
nelomen said:
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Click to expand...
Click to collapse
The FCs you were getting were probbly from DSPManager. It is a known issue that seems to come from a "broken pipe" in one of the libs. For now, it is best just to remove it.
For the bootup, someone suggested moving apps to the SD card. Apparently, it would speed up the process.
I am conscious that 2.3.4 is made with phones in mind but it is a step up from Froyo and having partial hardware acceleration helps.
Just tried again and got stuck on CM7 logo boot loop, this was with the CM7 tab build. did full wipe of cache, dalvik, and user data. Not sure what happened. Restoring to Illuminate rom if you have some ideas on how or what else I can do to try this rom let me know.
Hey there Ice.
First off, awesome work on this and thank you for taking the time.
I would recommend editing the build.prop file to set the Manufacturer to HTC. This fixes the playback issue with Netflix (Chipmunk). I tested this out fully on my gTab last night and it's the ONLY setting that needs to be modified. Aside from that, everything seems to work.
Good work!
Hi
Has anyone tried installing volume+ on this rom? I'm on BL1.1 CM7 rom but volume+ does not install. If this works, I'll take the bold step to upgrade to BL1.2.
I don't know if it's just my hardware. My gtab's speaker is very soft and I want to try cranking it up with volume+ (which works on my phone running cm7).
thanks a lot.
DroidTV phone size not full screen....Anyone have other apps that did that after....
I was using DroidTV, and it was full-screen and then rebuild my G Tab with the cm7tabl-0710200-1.2 and when I reinstalled DroidTV it is now phone size display on the G Tablet.
I used Titanium Backup to restore the app and the settings. Anyone have issues like this with an app that did that after re-installing after a full rebuild? Any build.prop setting or somewhere I could check?
Thanks. Steve.
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Icewyng said:
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Click to expand...
Click to collapse
Thanks Ice. Other than that I have yet to find any major issues that in the build.
Other than apps that open portrait only with the bottom on the side with the power button. Tried to say to not rotate 90 degrees but they still open that way Apps that open landscape then won't rotate to the 90 degree position but portrait apps still open that way
This is the most stable I have used and performance seems good. A co-workers has the same build, I installed it for them since they are techie-challenged, and theirs is turtle slow because I think they have Skype running all the time.
Icewyng said:
Thanks everyone for your feedback.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
Click to expand...
Click to collapse
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
vhendsume said:
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
Click to expand...
Click to collapse
Actually, I think it has more to do with a problem with one of the audio libraries. I did a logcat and it seems something called AudioFlinger can't set a parameter properly.
If anyone can fix this, I can send the logcat to help out.
I wanted to apologize for not being able to upload the new nightly today. I had to rebuild my computer and took the opportunity to switch to a new Linux distro. Just tested the new system and all is great.
I will post Build 07172011 later this morning.
Where are the nightly's getting posted now? Thanks and this is the most stable MOD I've had on my G Tab.
Do video apps work as far as no rotation with Oovoo, yahoo, reelportal, etc? Audio work okay with chatting?
mirrors:
http://dev-host.org/cops0ujuwmm0/update-cm-7.1.0-smb_a1002-07182011-1.2.zip
http://dev-host.org/8xjvaysomd1i/update-cm7tab-07102011-1.2.zip.zip
-deck
*** CM9 nightlies have been discontinued.. see: http://forum.xda-developers.com/showthread.php?p=29135522#post29135522 ***
For those who have dabbled in the Nook Color or HP TouchPad scenes you may have seen unofficial CM9 nightlies from me.. so in the same fashion here are the Nook Tablet builds - these should be considered in Alpha status.
***The nightly builds are currently for the 1GB "Acclaim" Nook Tablets ONLY***
I take no credit for the work put in to get nook tablet CM9 running - all the credit there goes to chrmhoffmann, fattire, nemith and countless others I may not even know. Please be sure to thank them for their efforts. I'm just building ROMs from their source code.
I *strongly* recommend everyone look over fattire's guide for building and giving it a try to learn a little about how this all works, it's how I got started on the nook color with these unofficial builds. After clearing with fattire and chrmhoffmann I decided to provide these builds for people who don't have the hardware/ability to build themselves.
These builds are all straight sync with CM source along with the nook tablet device and kernel trees. They are *NOT* tested releases (I don't even have a Nook Tablet) so please be aware that the builds could be broken at any time, and are provided as-is. Please be comfortable with adb and/or using recovery to wipe/restore/nuke at any time.
Builds are sync'd at 9am UTC - they will be available to download approx 15 mins after that.
There is no official "changelog" for nightlies, you can reference the commits in the device tree, kernel tree and main CM gerrit. Note that the CM gerrit shows things that are merged for ALL official devices, not all of these will apply to the Nook Tablet, however, anything not referenced by a device name is also included in these builds.
The only addition I have made to these builds is the inclusion of "Goo Manager" as a system app. More on the reasons for this below...
Downloads
There are a few ways to get the builds:
1) Browse the hosted folder here: http://techerrata.com/browse/nightly_kangs/acclaim
2) Follow @CM_Acclaim on twitter for announcements of the builds as they hit the host (PLEASE NOTE: @CM_Acclaim IS A TWITTER BOT - don't bother tweeting at it)
3) Use the Goo Manager app to receive notifications of new builds and download them directly on your device.
Latest ICS gapps can be found here http://goo-inside.me/gapps or mirrored here http://techerrata.com/browse/gapps
Goo Manager - Notable features
1) Notification of new builds and gapps updates with one click - or auto-check frequency in settings. Goo Manager auto-checks the md5 for every download.
2) Automated flashing of downloaded roms/gapps/other files with TWRP
3) Install TWRP 2.1 with one click (menu - install openscript recovery) - TWRP is still experimental and will overwrite ClockworkMod on emmc.
4) *Incremental updates* (experimental) - if you like to stay on the bleeding edge and flash every night. Incremental updates are diff'd server side so you only download the changed files from the build the night before. These downloads average 30-40mb in size (vs ~120mb for the full rom), so you get faster downloads, updates and less wear on your device's flash memory. Incremental updates ONLY work from the previous night's build to the latest. When you check for updates in Goo Manager it will offer you an incremental if applicable.
Updates
For the latest updates/announcements follow me on twitter, or check back here.
Credit and Thanks
Thanks to chrmhoffmann, fattire, nemith and the rest of the CM acclaim team for making this possible. Thanks to fellow TeamWin members Kevank for providing the hosting and to s0up for the Goo Manager app.
Neat.
This should make things easier.
Again though-- until some changes are added to the 3.0 kernel, if you have a newer 512MB NookTablet, the nightlies won't work and you'll probably come up with a blackscreen and have to reflash. Chrmhoffman's latest 2.6.35 build though should work if you have the newer model and/or want the 2.6.35 kernel w/cm9.
* EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL *
Warning: This will overwrite the internal storage with CM9. The instructions below assume you have a rooted NT running stock, CM7, or CM9.
Requirements
1GB NT (the 512MB NTs are not yet supported by the 3.0 kernel.)
Software: Rooted stock, CM7, or CM9
A full battery
a formatted SD card in the slot
wifi connection
(something else?)
To install the experimental CM9 w/3.0 kernel on a 1GB NT:
(steps are from memory and are to be refined soon)
Use the Google Play Market or other method to install Goo Manager to your device.
Run Goo Manager. Select the menu, and chose "install openscript recovery". Click through the options to confirm. At some point you may be asked to give Goo Manager superuser permissions.
The above steps should now cause TWRP2 recovery to be installed to your device. (You only need to do steps 1-3 again when you want to update or reinstall the TWRP2 recovery image.)
Now you can browse compatible roms for your device. Under /devs/eyballer/nightly_kangs/acclaim/ you should see some nightly builds. Choose the one you wish to install. Wait for it to download.
Once it's downloaded successfully, you should be able to select the newly downloaded rom from the notification menu, and then request that it be installed. Alternately, you can go to the Flash ROMS menu to flash previously downloaded ROMS.
See elsewhere in this thread for any other update.zips that you may wish to download and install. You can put more than one update.zip in the queue.
When you are ready, select the order and flash selected button on the bottom right.
It is sometimes preferable to wipe the cache/dalvik cache partition when doing an upgrade. You also have the option to automate a backup (not a bad idea). If you are coming from stock BN software or for any other reason wish to clear all user information, you may also wish to wipe the /data. partition. This is not generally recommended as wiping /data will delete your personal information.
When you're done configuring your flash, choose Flash, and then confirm.
If all goes well, there will be a reboot, your choice(s) will be flashed, and then the system will restart into the new CM9. If it doesn't work (very possible, as this is still experimental), post below and let the devs know what went wrong.
* EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL *
This video has more information about TWRP2 and Goo Manager, although the device discussed is a HP Tablet. Some things like the boot menu will be different, but most other details will apply.
Good luck, and be sure NOT to do this with an 512MB Nook Tablet. If you screw up and do install it, you will need to re-flash a CM9 using 2.6.35.
fattire said:
This should make things easier.
Again though-- if you have a newer 512MB NookTablet, the nightlies won't work.
Click to expand...
Click to collapse
I'm assuming it's because it's using the newer kernel?
Hmmmm, so these will be sorta nice.....
Fattire, did you update the TWRP .zip to a non-totally-messed-up version?
If so I'll jump on these and try them.
Also are these builds the latest 0.04 for our tablet?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Keithn said:
I'm assuming it's because it's using the newer kernel?
Click to expand...
Click to collapse
Yes, the 3.0 kernel has issues with 512MB-- the kindle fire had the same issues, and if you read the latter few posts in the kernel thread, you can read more about it. Hashcode apparently knows how to fix it, but until then, don't install this on a 512MB NT.
SilentStormer said:
Hmmmm, so these will be sorta nice.....
Fattire, did you update the TWRP .zip to a non-totally-messed-up version?
If so I'll jump on these and try them.
Also are these builds the latest 0.04 for our tablet?
Click to expand...
Click to collapse
No guarantees. eyeballer is using the latest experimental one from the twrp thread. It has the fix from arcon and has been successfully used by frustro. I of course have not ever run it, so I can't make any claim of success.... this is all experimental.
The builds are nightly, so right now they're about at par with chrmhoffmann's alpha .04 (which of course uses 2.6.35 kernel), but if I'm not mistaken, eyeballer builds 'em fresh every day from the cm9 repos plus whatever changes are made to the kernel and acclaim-specific repositories. That means they can be total crap in the future, and who knows if twrp2 is even any good either...
This is seriously guinea pig territory. So unless and until you're willing to take some risks, you might want to hold out for what others have to say.
I can confirm that this worked for me.
1. Intall goomanager from play.google.com
2. from menu choose install openrecovery script, it downloaded and installed openrecovery-twrp-2.1.4-acclaim.img
3 browse compatible roms, navigate to /devs/eyballer/nightly_kangs/acclaim/ and choose the first one
4 menu home
5 choose download gapps packages and choose gapps-ics-20120429-signed.zip
I had 2 download failures and had to repeat these steps till the download was correctly completed and then main menu flash roms select the 2 zips and I was done
very nice and smooth.
Can you add tun.ko and cifs.ko to the kernel config please?
Thanks
Do we have to use twrp to install this rom?
meghd00t said:
Can you add tun.ko and cifs.ko to the kernel config please?
Thanks
Click to expand...
Click to collapse
You're requesting tun.ko and cifs.ko compiled as modules?
Used Goo Manager to flash TWRP, had to pull the SD card and install it for it to mount.
Downloaded the first 900 build (I see there is 2 for some reason)
Clean install including /system wipe
Have had 2 or 3 "sleeps of death"
Screen wouldn't turn on with N button or power button.
Had to hold power for 10+ seconds to do a hard shut down.
Cranked my screen off timer to 10 minutes.
Keep up the great work.
Also Netflix loads and has audio no video but I'm sure you're aware of that.
Two other things I've noticed.
Can confirm the SD card mounts every time so far but the SD card did randomly unmount once.
Lastly, when trying to download Atorrent (for watching Game of Thrones) I get an error saying "Can not install to USB mass storage or SD card"
Sent from my Galaxy Nexus
great share!
Fattitire and or Eyeballer I have a very humble request that I think might help us help you.
I have been using Goo Manager for a few weeks and love it. It's a great tool. If you could add just a line or even two words to the Change Log tab in GM like "bug fix" "nothing major" "hardware acceleration working " it would be very helpful for us to decide if we should flash an update or skip it and wait for the next one.
Once again thank you, and great work.
Sent from my Galaxy Nexus
Helltoupee said:
Fattitire and or Eyeballer I have a very humble request that I think might help us help you.
I have been using Goo Manager for a few weeks and love it. It's a great tool. If you could add just a line or even two words to the Change Log tab in GM like "bug fix" "nothing major" "hardware acceleration working " it would be very helpful for us to decide if we should flash an update or skip it and wait for the next one.
Once again thank you, and great work.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
While this seems simple to add, it's not. My build system for these unofficial nightlies is completely automated so adding something to changelog would require me to go through the commits and then manually log into goo.im and update the rom info for every build. I don't do that for the devices I own, let alone the ones I don't
I posted links in the OP to all the source that is used to compile so it's up to the user to read and see if they would like to update. Of course as more people start running the builds, the discussion here usually will give you hints as to what's added too.
Updated the OP with another download notification method. We have a twitter system that will send out a tweet for every new build that hits our server with the link to the download and a QR code. You can follow CM_Acclaim for this.
Thank you for the explanation. I completely understand.
Sent from my Galaxy Nexus
Nighty change log blog thing I found for all CM9 builds. Enjoy.
http://changelog.bbqdroid.org/
Sent from my Galaxy Nexus
Do these nightly builds have an embedded expiration date like the chrmhoffmann's Alpha 0.0x builds?
Also, has anyone tried getting one of these builds to run off an SD card using succulent's method (http://forum.xda-developers.com/showthread.php?t=1545766)?
I kinda have a problem :\ I have lines running across half of my screen and its kinda freaking me out.. I'm not pointing fingers but it did happen after I installed this ROM
---------- Post added at 10:58 PM ---------- Previous post was at 10:52 PM ----------
My problem is solved... Oddly enough installing another rom makes the lines go away. I'm sorry for posting for no reason. lol have a great day
The 3.0 kernel still has problems. Hopefully these will be fixed in a later build.
digixmax said:
Do these nightly builds have an embedded expiration date like the chrmhoffmann's Alpha 0.0x builds?
Also, has anyone tried getting one of these builds to run off an SD card using succulent's method (http://forum.xda-developers.com/showthread.php?t=1545766)?
Click to expand...
Click to collapse
Don't try it. My modifications are for kernel 2.6.x version of CM9 not 3.0.x CM9.
I've build a bootable 3.0.x CM9 on sdcard. I wouldn't recommend this build yet due to LCD brightness and no sleep issue. LCD brightness will take 50% of the battery. This build is mainly testing.
I loaded recovery. Downloaded CM9 ics then gapps. When I go to flash roms nook reboots then I get the cynaboot image then nook boots back to cm7. What am I doing wrong?
The problem I was having is that cm7 did not mount my SD card on reboot. Had to load eyeballers first build through cwm. Then once in cm9 I could load through twrp. Running good so far.
Disclaimer: I will not be responsible if you brick your NT or your significant other leaves you for bricking theirs. As always, flash at your own risk.
Here is a full codefireX (cfX) ROM with 1.2GHz OC that is 5 touch enabled. You can use this with the 2 touch or 5 touch firmware, kudos to mik_os for the driver that does so.
codefireX is sort of a mixture between AOSP, AOKP, and CM10.
Here is their git: https://github.com/codefireX
Here is my kernel git: https://github.com/tonyp23/android_kernel_acclaim
Features:
Click HERE for a full cfX settings feature flowchart by BananaGranola (thank you)
NOT simply a re-named CM build
Built with a custom toolchain, strict aliasing, -O3 completely (including thumb_cflags), and other Linaro optimizations such as OOM/LMK changes.
Lots of extra settings in the codefireX settings panel
Please see this post on how to install the updated firmware if you'd like to have 5-touch. http://forum.xda-developers.com/show...9&postcount=75
With that said, many huge thanks to everyone who has put so much effort into making this awesome. If I forgot you, let me know!
Kuzma30, chrmhoffman, mik_os, fattire, Hashcode, Rebellos, demetris_I, Succulent, CelticWebSolutions, eyeballer, Bauwks, CM team, TWRP team, codefireX team, TI, BN
Here's general instructions on how to proceed
1. Update touch firmware if you choose
2. Install CWM 6.0.1.5 using fastboot
3. Wipe data/factory reset, wipe dalvik cache
4. Install ROM
5. Install newest gapps from goo.im
2012-11-13
First build up
http://celticstorage.co.uk/cm10/cm-cfX-20121113-OFFICIAL-acclaim.zip
http://celticstorage.co.uk/cm10/cm-cfX-20121113-OFFICIAL-acclaim.zip.md5sum
Reserved for future
It has a weird thing with the wifi icon, you may have to play with the codefirex settings and flick the 6 signal bars on then off again.
Nice! I'll give this a try.
Question, though. Any issues with apps disappearing due to sdcard issues? I know other roms have issues. Xda free is one app that I have issues with on the aokp build if I don't move it to internal.
Sent from my CvD Nibbled Skyrocket
Quando Omni Flunkus Moritati
liquidzoo said:
Nice! I'll give this a try.
Question, though. Any issues with apps disappearing due to sdcard issues? I know other roms have issues. Xda free is one app that I have issues with on the aokp build if I don't move it to internal.
Sent from my CvD Nibbled Skyrocket
Quando Omni Flunkus Moritati
Click to expand...
Click to collapse
There's a lot of different code and drivers between this and the sgt7 builds, I have not had any problem with the sd card on it.
Sent from Outer Space
liquidzoo said:
Nice! I'll give this a try.
Question, though. Any issues with apps disappearing due to sdcard issues? I know other roms have issues. Xda free is one app that I have issues with on the aokp build if I don't move it to internal.
Sent from my CvD Nibbled Skyrocket
Quando Omni Flunkus Moritati
Click to expand...
Click to collapse
I haven't seen a single sdcard issue yet
can you show us some pics please?
hi tony,
what is diferrent of this rom with your rom at other thread? thanks
http://forum.xda-developers.com/showthread.php?t=1966894
maxdown said:
hi tony,
what is diferrent of this rom with your rom at other thread? thanks
http://forum.xda-developers.com/showthread.php?t=1966894
Click to expand...
Click to collapse
The other is a build built with the sgt7 changes like demetris_i's builds, and this one is built off of the CodefireX repos with those extras.
Warren87 said:
can you show us some pics please?
Click to expand...
Click to collapse
I don't understand why people want pics so much, it's exactly the same appearance as all the other normal cm10 roms. It has simple multi-dpi interface compared to paranoidandroid, it has a different extra settings interface like aokp, other than those.. Nothing is different
Sent from Outer Space
Got a error message
got a error message "Warning: No file_contexts" when flashing with CWM 6.0.1.5 ,will re-download to see if that is the problem.
update: same error with new download file.
tonyp23 said:
Disclaimer: I will not be responsible if you brick your NT or your significant other leaves you for bricking theirs. As always, flash at your own risk.
Here is a full codefireX (cfX) ROM with 1.2GHz OC that is 5 touch enabled. You can use this with the 2 touch or 5 touch firmware, kudos to mik_os for the driver that does so.
codefireX is sort of a mixture between AOSP, AOKP, and CM10.
Here is their git: https://github.com/codefireX
Here is my kernel git: https://github.com/tonyp23/android_kernel_acclaim
Features:
Click HERE for a full cfX settings feature flowchart by BananaGranola (thank you)
NOT simply a re-named CM build
Built with a custom toolchain, strict aliasing, -O3 completely (including thumb_cflags), and other Linaro optimizations such as OOM/LMK changes.
Lots of extra settings in the codefireX settings panel
Please see this post on how to install the updated firmware if you'd like to have 5-touch. http://forum.xda-developers.com/show...9&postcount=75
With that said, many huge thanks to everyone who has put so much effort into making this awesome. If I forgot you, let me know!
Kuzma30, chrmhoffman, mik_os, fattire, Hashcode, Rebellos, demetris_I, Succulent, CelticWebSolutions, eyeballer, Bauwks, CM team, TWRP team, codefireX team, TI, BN
Here's general instructions on how to proceed
1. Update touch firmware if you choose
2. Install CWM 6.0.1.5 using fastboot
3. Wipe data/factory reset, wipe dalvik cache
4. Install ROM
5. Install newest gapps from goo.im
2012-11-13
First build up
http://celticstorage.co.uk/cm10/cm-cfX-20121113-OFFICIAL-acclaim.zip
http://celticstorage.co.uk/cm10/cm-cfX-20121113-OFFICIAL-acclaim.zip.md5sum
Click to expand...
Click to collapse
Vector2nds said:
got a error message "Warning: No file_contexts" when flashing with CWM 6.0.1.5 ,will re-download to see if that is the problem.
update: same error with new download file.
Click to expand...
Click to collapse
Which file are you downloading?
liquidzoo said:
Which file are you downloading?
Click to expand...
Click to collapse
2012-11-13
First build up
http://celticstorage.co.uk/cm10/cm-c...AL-acclaim.zip
http://celticstorage.co.uk/cm10/cm-c...aim.zip.md5sum
Downloaded both and put in sd. Seems to boot ok, already installed gapps 4.2. Besides the weird error at flash, the rom seem faster in titanium restore.
Vector2nds said:
2012-11-13
First build up
http://celticstorage.co.uk/cm10/cm-c...AL-acclaim.zip
http://celticstorage.co.uk/cm10/cm-c...aim.zip.md5sum
Downloaded both and put in sd. Seems to boot ok, already installed gapps 4.2. Besides the weird error at flash, the rom seem faster in titanium restore.
Click to expand...
Click to collapse
I also got the 'No File Context' warning when I flashed the ROM. I ignored it and it seems to not have caused any problems.
My experience also was that Titanium restore was *much* smoother and quicker with this ROM than with other CM10s for Nook.
It seems to be a nice, stable build so far.
I did get the error where the WiFi signal won't show up in the status bar. I've had no luck getting it to appear, but WiFi works just fine.
timpilcher said:
I also got the 'No File Context' warning when I flashed the ROM. I ignored it and it seems to not have caused any problems.
My experience also was that Titanium restore was *much* smoother and quicker with this ROM than with other CM10s for Nook.
It seems to be a nice, stable build so far.
I did get the error where the WiFi signal won't show up in the status bar. I've had no luck getting it to appear, but WiFi works just fine.
Click to expand...
Click to collapse
Yes you can safely ignore that error, confirmed by the main developer.
Also if you have the bizarre wifi bars bug you can still use the text meter
Sent from my Barnes & Noble Nook Tablet using XDA Premium HD app
Somethings that could interfere or not needed
I notice in settings>codefirex>theme tweaks>status bar ..."Show Brightness Toggleslider" if checked get in the way of status bar view and Show Wifi network is check then that just duplicates AP name what on the bottom of status slide down menu. I don't have Dual-pane view or Force tableUI checked, so it may look different if you have those checked. I didn't get any errors on wifi but I did edit Widget buttons in settings>systems>notification drawer>widget buttons... checked and uncheck the widget I want and don't want. There also a half blue line on right top of the navigation bar.,,strange...sometime there's little dots trailing from the right side of the screen to that blue line.
Update:
Toggle the check box back and forth for "Hide signal bars", this will show the wifi signal in the status bar. Make sure that "Six bar signal icons" check box is not ckecked.
I don't know if this a new feature or an old feature that I just didn't notice is the power button that you can set for on demand deep sleep in Navigation bar; button#, action & icons.
Ok that blue bar on the bottom right corner that I mention earlier that I thought was weird is called the battery bar. Three games that I had no success in the past now two works.
Major heating issue charging while in use (interactive mode) is now controlled where I don't have to change to "conservative mode"while in use. Excellent
I have to say this hybrid ROM is the BOMB!!!!! LUV UV UV it. ...............so far, still testing.
schmooth
How i can flash rom so dont change UDID .
My game online is gone ( . i must play again (
Deep Sleep Results Update
Ok , before anyone of yousse Doctors get snippy at me, I'm not debating if others have different results base on their own findings.
Here my Diagnosee..eee.eeee after deep sleeping the NT16 for more than eight (8) hours using the power button on the navigation bar to deep sleep on demand, it loss one (1) percent or less because I woke it four (4) hours before to check with cpu spy. I screwed up the first video recording and that why you don't see the wifi zero signal to signal on and sd showing mounting in process.
What do you think Doctors?, here the video of the results
Update: There is still a heat issue in interactive mode plugin power while in use but not as extreme where I had to put it in a freezer to cool off. I guess if come with OC territory.
ryan.nguyentran said:
How i can flash rom so dont change UDID .
My game online is gone ( . i must play again (
Click to expand...
Click to collapse
Titanium Backup (as long as it's installed before you change a ROM) will restore the UDID. I know the Pro version does this, not entirely sure about the free version.
App data usage
I notice that gapps was taken alot of the data memory so I froze both gapps and it services in titanium backup then defrost it to clear for more Free RAM showing. I'm hoping this would improve battery if I clear it Settings>Data usage ; apps listed. Is there any utilities in cm10 that would disallow apps to background in memory?
Ok, I found it while typing this message. Settings>Developer option>Background process limit . I wonder if I set it to No background processes would work and check Settings>Developer option>Don't keep activities work. Hopefully this will reduce battery drain.
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.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KK), which is designed to increase performance and reliability over stock Android for your device.
------------THIS IS AN UNOFFICIAL UNSUPPORTED BUILD-----------
This is my attempt at porting CyanogenMod 11 to the Galaxy Tab 4 10.1. I use a SM-T530NU, so that is the only device I have tested.
Any other device variations have not been tested and are at your own risk. I will not be able to support other variations as I don't own them for testing.
Special thanks to MetaIIica - I have been using his Alpha build of PAC-ROM KitKat since December. I studied the code for that, along with stock and some other ROMs before starting this port. This is my first time doing any work with Android, so I'm not sure if I'm technically doing things correctly or not.
I know CyanogenMod 12 is under development already, but I have decided to do a CM11 based build in hopes of a making a stable daily driver offering. I have fixed many of the issues present that were present in the PAC-ROM build. They can probably be backported to PAC-ROM easily if its built with my tree, but I prefer the plain CM-based offering myself.
You may get the source of my changes for this ROM on my github. If you'd like to help and submit a patch, feel free to open a pull request. You will of course be credited accordingly.
See below for instructions, what's working, and issues I fixed over the PAC-ROM Alpha.
For any bug reports or feature requests, please use the appropriate tabs at the top of the thread. Please include as much information as possible and if possible a logcat or other debug information in the case of bugs. Requests for supporting other device variations will not be honored - sorry,
Feedback and constructive criticism is always appreciated. I hope you enjoy using the ROM; if you use the ROM, please consider leaving a thanks, rating, and/or review
CURRENT VERSION:
DOWNLOAD LINK - 04/26/2015
OLD VERSIONS:
DOWNLOAD LINK - 04/20/2015
DOWNLOAD LINK - 04/19/2015
DOWNLOAD LINK - 04/07/2015
DOWNLOAD LINK - 04/05/2015
DOWNLOAD LINK - 04/04/2015
DOWNLOAD LINK - 04/03/2015
DOWNLOAD LINK - 03/29/2015
DOWNLOAD LINK - 03/24/2015
DOWNLOAD LINK - 03/23/2015
DOWNLOAD LINK - 03/22/2015
INSTRUCTIONS
- Install PhilZ Touch Recovery (recommended)
- Copy CM11 & GAPPS (Optional) ZIPs to your SDCard
- Boot into Recovery
- Do "Clean to Install a New ROM" (FULL WIPE REQUIRED INCLUDING SYSTEM, NOT JUST DATA/CACHE - even if coming from another CM-based ROM, as my device tree is different)
- Flash CM11 ZIP
- Flash GApps zip from SDCard
- Reboot
UPGRADING
-In general, you should be able to just flash over the previous build, but if you encounter any weird issues please clean using the steps above
Working that I've tested:
Audio: Speakers, Headphones, Bluetooth
Bluetooth
CIFS/NFS (Network File Systems - see notes below)
Front Camera
GPS
IR Blaster [SM-T530NU Only]
Magnetic Cover Sleep/Wake
MTP
Rear Camera
USB OTG
Video (w/ Hardware Decoding)
WiFi (2.4ghz & 5ghz)
NOTE ON BUTTONS: This ROM is configured to use the hardware buttons-- so you won't see the software buttons taking up space at the bottom of the screen, as they are disabled. This is not a bug. Use the hardware buttons, as they are the same. If you really want the software buttons for some reason, edit /system/build.prop, change qemu.hw.mainkeys to 0, save, and reboot. If you map the menu button to a long press of another button, some apps such as TitaniumBackup will count this as a hardware key and hide their soft menu button - but only after a reboot.
NOTE ON CIFS/NFS: Many of the mounting utilities on the play store are outdated and broken due to changes in the linux kernel. For best luck, mount using the command line. For CIFS, you can tweak CIFSManager into working - see this thread
CHANGELOG:
[04/26/2015]
-Fix reading MAC address from EFS
-Fix suspending charging while the device is off (special thanks to @sub77 for pointing out the right config option)
[04/20/2015]
-Enable physical keyboard menu for use with BT/USB keyboards. Auto hides soft keyboard & allows selection of layout.
[04/19/2015]
-Add support for magnetic cover sleep/wake
[04/07/2015]
-Roll back to using the Non-CAF Display HAL Fixes SurfaceFlinger constantly eating 100% CPU
[04/05/2015]
-Fix issues with reconnecting Bluetooth Devices after a reboot (if upgrading, break pairing and re-pair all devices)
-Fix mounting /efs
-Fix persistant Bluetooth MAC Address
[04/04/2015]
-Fix issues with detecting whether or not the device has a hardware menu button.
[04/03/2015]
-Fix the Time Service, allowing Date & Time to persist during a reboot without a wifi connection. Special Thanks: sub77 for pointing the discussion in the thread in the right direciton on this
[03/29/2015]
-Support Bluetooth Audio & AVRCP
-Support Consumer IR [SM-T530NU Only]
-Upgrade Display HAL to CAF Version
-Misc Bugfixes and Cleanup
[03/24/2015]
-Fix Missing Sensors HAL (Fixes Autorotate regression from the last build)
-Behind the scenes work for IR (need someone to test on plain 530 as IR is NU only). Does not actually work yet because its using the stub HAL, but the kernel drivers are loaded, and the IR service runs.
[03/23/2015]
-Fix lighting issues with rear camera
-Reduce some dependencies on vendor libs.
[03/22/2015]
-Added support for Front/Back Camera
-Added support CIFS/NFS
-Fixed 5 ghz WiFi
-Fixed Duplicate VSYNC spam in logcat
-Fixed issues with video decoding (YouTube HD, MXPlayer HW+ Video, etc)
-Fixed various Bluetooth issues
-Fixed wallpaper issues with Trebuchet
-Identify device correctly as MSM8226 chipset
-Use Hardware Buttons by Default
XDA:DevDB Information
CyanogenMod 11 Unofficial [TM-530NU], ROM for the Samsung Galaxy Tab 4
Contributors
starlightknight
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2015-03-29
Beta Release Date: 2015-03-22
Created 2015-03-29
Last Updated 2015-04-25
Congratulations ! :good:
Nice ROM, it installed fine on my T530 will test some more, thanks for the hard work
I got this installed but the back button and recents button didn't work at all. Its a fast rom though but it would be nice if it was a barebones CyanogenMod without the Pac Rom extras installed too.
Time for a new test, i'll test it in my t530 and report back the results.
Sent from my GT-I9300 using XDA Free mobile app
steve30x said:
I got this installed but the back button and recents button didn't work at all. Its a fast rom though but it would be nice if it was a barebones CyanogenMod without the Pac Rom extras installed too.
Click to expand...
Click to collapse
It is a pure Cyanogenmod without the Pac extras. If you're seeing them, make sure you did a full wipe before flashing as noted in the original post - you may have remnants of PAC-ROM in /system. The best way is to use PhilZ option to "Clean to Install a new ROM" as that wipes everything correctly. That could also be causing your issues with the back button as well. I completely rebuilt the device tree for this rom over the pac build, as that was based on MSM8974 when this is an MSM8226 device. If a full wipe wasn't done, you have stuff for the other device tree in /system that will mess things up. If the issue persists after a full wipe, please let me know what varient of 530 you're using, and pastebin a logcat of what happens when you press the back or recent events buttons.
starlightknight said:
It is a pure Cyanogenmod without the Pac extras. If you're seeing them, make sure you did a full wipe before flashing as noted in the original post - you may have remnants of PAC-ROM in /system. The best way is to use PhilZ option to "Clean to Install a new ROM" as that wipes everything correctly. That could also be causing your issues with the back button as well. I completely rebuilt the device tree for this rom over the pac build, as that was based on MSM8974 when this is an MSM8226 device. If a full wipe wasn't done, you have stuff for the other device tree in /system that will mess things up. If the issue persists after a full wipe, please let me know what varient of 530 you're using, and pastebin a logcat of what happens when you press the back or recent events buttons.
Click to expand...
Click to collapse
I always completely wipe everything before installing a new rom. Never wiping the tablet before installing a new rom might cause problems. I no longer have the rom installed. I will install it again and see if it was just a flike that it didnt work properly the last time. I also have Philz recovery installed because its the only one that has full brightness on the screen.
Simply great. Everything i need works great. Finally a kitkat aosp rom that given me everything i need. Flashed in TWRP on a t530 (wifi only) and running perfectly fine. Good job mate. If you want me to test anything on t530 just tell me.
Btw, otg works, so my usb keyboard is working.
Otg works, YouTube and twitch.tv works, BT works, rotation works, camera works, xposed works, everything i have tested works
Sent from my GT-I9300 using XDA Free mobile app
pirulazul said:
Simply great. Everything i need works great. Finally a kitkat aosp rom that given me everything i need. Flashed in TWRP on a t530 (wifi only) and running perfectly fine. Good job mate. If you want me to test anything on t530 just tell me.
Btw, otg works, so my usb keyboard is working.
Otg works, YouTube and twitch.tv works, BT works, rotation works, camera works, xposed works, everything i have tested works
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks! Glad to hear that it is working well for you. I believe the only difference between the SM-T530 and the SM-T530NU is the the NU has an IR blaster, which I haven't actually enabled yet. I need to figure out how to test that because I never use it. After i do that and post a build with IR, it will be useful if you check and make sure it doesn't break the regular 530. Those two from what I can tell are vary similar, its more of any celluar varients that I would be worried about, because this is build for wifi only..
Let me know if you find anything broken
I got this to work properly. I have one question though. Is there a way to get youtube working without having all the other GAPPS rubbish installed. I noticed that the tablet got slower as soon as I installed GAPPS. The tablet flies along without GAPPS installed and I only want youtube working without all that other rubbish bogging down the tablet.
steve30x said:
I got this to work properly. I have one question though. Is there a way to get youtube working without having all the other GAPPS rubbish installed. I noticed that the tablet got slower as soon as I installed GAPPS. The tablet flies along without GAPPS installed and I only want youtube working without all that other rubbish bogging down the tablet.
Click to expand...
Click to collapse
Glad its working for you now
To be honest, I'm not sure - you could try copying the Youtube APK off of the device and then side-loading it on a fresh install without installing all of GAPPs, but I'm not sure if that will just prompt you to install all of them or not if you do that.
Are there particular use cases you are noticing are slower? I did not really notice any difference with or without GAPPs, other than the initial boot time as they were unpacked and installed. If there are particular situations that cause this, then we could dump some logs to see if there is something that could or needs to be optimized.
starlightknight said:
To be honest, I'm not sure - you could try copying the Youtube APK off of the device and then side-loading it on a fresh install without installing all of GAPPs, but I'm not sure if that will just prompt you to install all of them or not if you do that.
Click to expand...
Click to collapse
I have youtube backed up with all my other apps with Titanium Backup and when I try running youtube without GAPPS it fails and a popup states Youtube has failed to start (or something similar) and if I install the GAPPS I have which is older than the version that is needed it tells me that google needs to be updated. So then I update that and tried freezing the google apps I dont want or use but youtube fails.
starlightknight said:
Are there particular use cases you are noticing are slower? I did not really notice any difference with or without GAPPs, other than the initial boot time as they were unpacked and installed. If there are particular situations that cause this, then we could dump some logs to see if there is something that could or needs to be optimized.
Click to expand...
Click to collapse
The whole tablet is slightly slower with GAPPS installed. I've opened a gapps zip with WINRAR and removed some of what I dont want and only left whats needed for play store to run so it improved a bit.
Hi,
I didn't try it for now...
But thanks for the good work!!
For the Gapps, have you try PAGapps?
It has different package with a lot of options.
The smallest one should be around 136Mo. You can also remove some apk with a config file.
All other apps are available on Play Store...
Gustave17 said:
Hi,
I didn't try it for now...
But thanks for the good work!!
For the Gapps, have you try PAGapps?
It has different package with a lot of options.
The smallest one should be around 136Mo. You can also remove some apk with a config file.
All other apps are available on Play Store...
Click to expand...
Click to collapse
The GAPPS package I modded is only 76MB. Its just the bare essentials
steve30x said:
The GAPPS package I modded is only 76MB. Its just the bare essentials
Click to expand...
Click to collapse
Oh ok, so it's what we need...
Y
steve30x said:
I have youtube backed up with all my other apps with Titanium Backup and when I try running youtube without GAPPS it fails and a popup states Youtube has failed to start (or something similar) and if I install the GAPPS I have which is older than the version that is needed it tells me that google needs to be updated. So then I update that and tried freezing the google apps I dont want or use but youtube fails.
The whole tablet is slightly slower with GAPPS installed. I've opened a gapps zip with WINRAR and removed some of what I dont want and only left whats needed for play store to run so it improved a bit.
Click to expand...
Click to collapse
I used an aroma based gapps. You can install only what you need. About using YouTube without gapps, i dont know if tubemate could do the trick. Use aptoide to install it if you dont like play store. Here is the link for the aroma gapps: http://forum.xda-developers.com/showthread.php?t=2547250
Sent from my GT-I9300 using XDA Free mobile app
---------- Post added at 11:01 PM ---------- Previous post was at 10:45 PM ----------
Oh, forgot one thing, rear camera is too dark but frontal camera is fine.
Sent from my GT-I9300 using XDA Free mobile app
pirulazul said:
Oh, forgot one thing, rear camera is too dark but frontal camera is fine.
Click to expand...
Click to collapse
It has something to do with the lighting detection or some other initial initialization that I haven't figured out yet, but as a workaround if you toggle between camcorder mode and back it'll brighten up.
starlightknight said:
It has something to do with the lighting detection that I haven't figured out yet, but as a workaround if you toggle between camcorder mode and back it'll brighten up.
Click to expand...
Click to collapse
Tested and working fine. Is a nice workaround. I dont mind about this bug as I only use front camera for Skype and such things, but im glad this workaround is pretty easy and fast
Sent from my GT-I9300 using XDA Free mobile app
Hi Everyone,
I updated the original post with a new build. This build should fix the lighting issues with the rear camera the first time it is used. After I debugged the mode switching with logcat I was able to find out what the issue was. I also am working on reducing dependencies on vendor libs where possible by getting more of the modules that can be built from source building from source.
I've started exploring IR blaster support for NU users and I am continuing to look for a solution for bluetooth audio, but I don't have either yet. Stay tuned for future updates
If you already installed the ROM most times you should be able to flash over it, but if you see anything weird after, try wiping to confirm if its a bug or weirdness after upgrading (you can always nandroid before wiping if you're unsure and roll back if its not related to upgrading).
Please let me know if you find any issues. Include model number and if possible a logcat as well.
Enjoy!
Congrats starlightknight!
Anyone tried this on the SM-T530?