*** 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.
Related
CyanogenMod is a free, community built distribution of Android 2.3.7 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
Warning : Not for new users, flash this build only if you know what you are doing !!!
What is CyanogenMod (in less terse form - by mad-murdock)?
since i am a bit idle right now, i try to answer this.
cyanogenmod is the only open source rom, that runs on 40+ different devices. we got around 45 devs (people who really write code and tweak things to make it work better - in contrast to cooks, who only use winzip to exchange this vs. that binary thingie) constantly making cyanogenmod better.
as background, you might wanna know, that google usually releases the sourcecode to their products (where honeycomb is the first exception, but thats another matter, ICS will be open source again). but when google releases their source code, you cannot compile it for ANY phone and it runs on it. thats the first part, we jump it - make it compatible with all the phones we support.
once it basicly runs, its time for what we call "cm extras" - we modify a lot on the gui and the system to make it run better. some stuff you as a user will never see involving tweaking libs and kernels, and some stuff you as a user will see a lot, like including theme manager, dsp manager, cm settings (cm settings are about as huge as the normal settings are). those settings range from simple "dont display clock in status bar" to complex profiles (as known from old nokia phones) or remapping of some keys (long press home, remapp search button behavior)
its way to much to list it all here, but i can assure you, cm is fast, usually stable on most devices and VERY VERY customizable - both in grafical ways as also in behavior way.
Click to expand...
Click to collapse
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Installation instructions:
in following post - will move moved to Q&A Forum when that is up.
teamhacksung:
atin - http://gplus.to/atinm
codeworkx - http://gplus.to/codeworkx
coolya - http://gplus.to/coolya
unhelpful - http://twitter.com/unhelpfulone
Changelog:
Generic Changelog CMSRC Twitter
Device specific Changelog by igor.tonky
Modems:
TBD
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
CyanogenMod 7 (w/ Gingerbread 2.3.7) for AT&T Galaxy SII
The only rule of CyanogenMod: you don't ask for ETAs. You install, your warranty is void.
Warning : Not for new users, flash this build only if you know what you are doing !!!
FAQ (Please Read!!)
What is CyanogenMod (by mad-murdock)?
CyanogenMod is the only open source rom, that runs on 40+ different devices. we got around 45 devs (people who really write code and tweak things to make it work better - in contrast to cooks, who only use winzip to exchange this vs. that binary thingie) constantly making cyanogenmod better.
as background, you might wanna know, that google usually releases the sourcecode to their products (where honeycomb is the first exception, but thats another matter, ICS will be open source again). but when google releases their source code, you cannot compile it for ANY phone and it runs on it. thats the first part, we jump it - make it compatible with all the phones we support.
once it basicly runs, its time for what we call "cm extras" - we modify a lot on the gui and the system to make it run better. some stuff you as a user will never see involving tweaking libs and kernels, and some stuff you as a user will see a lot, like including theme manager, dsp manager, cm settings (cm settings are about as huge as the normal settings are). those settings range from simple "dont display clock in status bar" to complex profiles (as known from old nokia phones) or remapping of some keys (long press home, remapp search button behavior)
its way to much to list it all here, but i can assure you, cm is fast, usually stable on most devices and VERY VERY customizable - both in grafical ways as also in behavior way.
Click to expand...
Click to collapse
Q: How do I install this?
A:
Latest version:
Temporarily while buildbot is down:
You can get it from ROM Manager (look for teamhacksung builds for Galaxy SII AT&T) or
http://www.multiupload.com/RT29P7AOFS (md5: c8115d0a01d0a47b286ff5c9cc504175)
Previous kang: http://www.multiupload.com/A30J9DZN37 (md5: a23d1b99ff73da31e5d0421ec18e15e3)
Normally: http://download.cyanogenmod.com/?type=nightly&device=galaxys2att
Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.
- First time flashing CM 7 to your Galaxy S2 (or coming from another ROM)?
Note: You may need to flash twice back to back if the first one goes by too quickly - the actual flash takes a little time and sometimes the first flash doesn't "stick".
Install via ClockworkMod recovery (do not use ROMManager for initial install):
Make sure you're running a rooted device.
Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/showthread.php?t=1118693)
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
Install the ROM from internal sdcard using ClockworkMod Recovery.
Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
Reboot
Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
- Upgrading from earlier CM7?
ROM Manager method:
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Samsung AT&T Galaxy S2.
Choose Download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe cache, dalvik cache.
Let ROMManager finish the installation.
Clockwork Mod method:
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Install the ROM zip from sdcard (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for AT&T Samsung Galaxy S2, choose Download ROMs, and pick Google Apps. Or download and push the gapps zip for CM7 from http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps to the sdcard and flash it via ClockworkMod recovery.
- Going to another ROM from CM7?
You can go back and forth freely between CM7 and other ROMs via ClockworkMod recovery as the file systems are the same and nandroid backup/restore works to go between ROMs.
Q: What are the known issues?
A: Issues that I can remember:
- Video playback - some formats are not recognized, use an alternative app for video playback
- Camera - some video and still modes don't work
- TVout, MHL
- Dock
Q: Where do I see the Changelogs?
A: http://cm-nightlies.appspot.com/?device=galaxys2att - this shows all the changes that have gone into a nightly, including anything that is device specific to Galaxy S2 and anything that has gone into common code that is also included on Galaxy S2. If you see another device sometimes in the Galaxy S2 changelog, it is because the changes were done to common code and the repository is also included on the Galaxy S2.
Q: Can I flash over a previous version of CM7?
A: If updating from an already CM7 running SGSII phone, just flash the latest update zip file as it contains all the fixes from previous updates.
Q: I just installed and I don't see the Marketplace, cannot see GMail, cannot sync Contacts.
Q: I just installed and I don't see any Google Apps.
A: You need to install the Google apps. They are available in ROMManager. ROMManager also asks you if you want to install the Google Apps addon when you install via ROMManager.
Q: Can I run Samsung Applications like Kies, Phone, Email, AllShare?
A: No. Any applications that use special calls into the Samsung TouchWiz framework will not work.
Q: I cannot find my media files that are on my external sd card
A: Look under /mnt/emmc as that is where CM7 mounts the external sd card as opposed to /mnt/sdcard/external_sd that Samsung ROMs use.
Q: My phone is running too hot, my phone is not going into deep sleep
A: Try to isolate which application is using too much CPU. The first thing to try is to remove your media (video, music etc) files. Files recorded using Samsung camera, but other files as well, can frequently cause the stock Media Scanner to fail and go into an infinite loop. Then try to isolate which files are causing problems, and report them to us. If it isn't media, then it is some other application. Try to remove that application if it is a third-party application (and report a bug to them).
Q: I restored from Titanium Backup but my applications are not working
A: Do not restore system data, only restore application+user data. CM7 uses new system data and if you restore on top of it, things will not work.
Q: Your notification toggles are different than mine, how can I change them?
A: Go into Settings, CyanogenMod Settings, Interface, Notification power widget, Widget buttons
Q: I really miss the accurate battery mods, can I flash these?
A: No, but you can go into Settings, CyanogenMod Settings, Interface, Status bar tweaks, "Battery percentage"
Q: Where can I get themes for this?
A: A quick search for "theme engine" on the market will produce a number of results, but there are some in the general Android Themes section
Q: My Status bar Sound widget does not toggle through the options.
A: Settings > CyanogenMod Settings > Interface > Notification Power Widgets > Widget Buttons > Sound Modes and set the modes you want it to toggle through.
Q: Can I use the video player/music player/contacts/phone/launcher from a Samsung ROM?
A: No, anything hooking into Samsung's framework will not work on this ROM, there are plenty of alternatives in the market.
Q: Where can I get the Nexus S drivers?
A: Download and install the Android SDK here then download "Google USB Driver package, revision 4"
Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you installed the SDK
Q: How do I go back to a Samsung stock ROM?
A: Just use ClockworkMod or ROM Manager backup/restore facility to go back and forth between stock (or any other ROM) and CM7.
Q: Can I use ROM Manager to install or back up this ROM?
A: Yes.
Q: Why do I not see the nightlies in ROM Manager?
A: Nightly builds are only visible in the premium version of ROM Manager. Nightly builds should up in ROM Manager when the CyanogenMod buildbot builds the nightly successfully. Every new device needs to also get added to the ROM Manager manifest before it is available. But, the same files are also available at http://download.cyanogenmod.com when the buildbot successfully builds a nightly.
Q: Why can't I play .avi or .mkv files? They worked fine with Samsung's ROM.
A: Due to codec licensing issues, this can't be provided out of the box. Several apps from the marketplace should be able to replicate this feature (such as RockPlayer). We will also try to put these enhancements into CM7 ourselves.
Q: I encountered a bug, how do I find out if it's known and where can I report it?
A: Try to get the logcat output and last_kmsg to your report by:
Code:
desktop$ adb logcat > logcat.txt
desktop$ adb shell
# cat /proc/last_kmsg > /sdcard/last_kmsg (only if you had crash/reboot)
# dmesg > /sdcard/dmesg.txt
# exit
desktop$ adb pull /sdcard/last_kmsg .
desktop$ adb pull /sdcard/dmesg.txt .
Attach the logcat.txt and last_kmsg files to the bug report. Of course, you need to have the android SDK installed to do this.
And one more.
Running very smooth on the sgs2 keep up the great work.
AT&T SGS2 running CM7.
Codeworkx just put up a test build (http://codeworkx.de/download/galaxys2att/cm7-galaxys2att-KANG.zip) - it should work, but right now none of us has an AT&T SGS2, so need someone else to try it. Install it via ClockworkMod recovery as explained in the second post.
Let us know if it basically works.
Yea I've been running that for about an hour no issues.
AT&T SGS2 rooted!
Another Phone gets the best Android ROM ever!!! ;-)
jivy26 said:
Yea I've been running that for about an hour no issues.
AT&T SGS2 rooted!
Click to expand...
Click to collapse
Thanks - excellent! Change your signature to say "AT&T SGS2 CyanogenMod 7!"
Lol already did
Phone: AT&T SGS2
Running: CM7
getting signature verification failed. and yes, i am already rooted.
LOL seriously...already cm7 is here?? Can't wait to get home and throw this on here
Sent from my SAMSUNG-SGH-I777 using xda premium
jivy26 said:
Lol already did
Phone: AT&T SGS2
Running: CM7
Click to expand...
Click to collapse
Are you running the version of CM7 that codeworkx sent to you? No problems with installation?
atinm said:
Are you running the version of CM7 that codeworkx sent to you? No problems with installation?
Click to expand...
Click to collapse
Yea just had to install cm7 let it reboot it won't load passed galaxy s2. Pull battery goo into cwm install again gtg
Sent from my SGH-I777 using xda premium
seattleboi1982 said:
getting signature verification failed. and yes, i am already rooted.
Click to expand...
Click to collapse
Did you follow the instructions in the second post in the thread? As in, did you use the "Harder way" - flash ClockworkMod recovery etc?
I flashed before this thread was started so flashed using Odin and kernel codework released for cwm. Used super one click to root Then flash cm7 in cwm like I posted earlier
Sent from my SGH-I777 using xda premium
jivy26 said:
I flashed before this thread was started so flashed using Odin and kernel codework released for cwm. Then flash cm7 in cwm like I posted earlier
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok, great - the "harder way" (and only way at the moment!). Thanks!
Tried MIUI and CM7...
Obvious bugs are the back button not working.
But the major one is I can't hear anyone on a call and they can't hear me. Complete silence...both MIUI and CM7. Kernel issue? Known issue?
My order is in, should be seeing my Galaxy S II very soon, stoked!
I'll be testing just about everything pushed out once its here, I'll be reporting back as much as possible can't wait!
Drew489 said:
Tried MIUI and CM7...
Obvious bugs are the back button not working.
But the major one is I can't hear anyone on a call and they can't hear me. Complete silence...both MIUI and CM7. Kernel issue? Known issue?
Click to expand...
Click to collapse
I didn't even know there was a MIUI for AT&T Samsung Galaxy SII yet. As far as no sound - we haven't been able to test anything ourselves as we don't have a device to test on yet (maybe in a couple of days). The code itself hasn't changed much, but it is possible you're seeing something valid that we'll have to fix.
jivy26 said:
Running very smooth on the sgs2 keep up the great work.
AT&T SGS2 running CM7.
Click to expand...
Click to collapse
Did you test voice calls? Can you report back?
The NookieDevs are pleased to announce CyanogenMod 11 nightly builds for the Nook Color!
These experimental builds contain the latest changes to CyanogenMod and to hardware support for the Nook Color. As the name suggests, new builds are made and posted (roughly) every day; these builds are fully automatic, with no testing done before posting. As CyanogenMod 11 is still under active development, regressions and general breakage are to be expected in nightly builds!
Highlights:
Linux kernel 3.0.101, plus hardware support from TI OmapZoom's android-omap3-3.0 branch and board support forward-ported from BN kernel releases.
All of the features of CyanogenMod 11, based on Android 4.4. For Nook Color, this brings a reduced memory footprint, which leads to a better all-around user experience.
Full 2D and 3D graphics acceleration using both the GPU and the display subsystem's hardware overlay acceleration (hwcomposer).
Known issues:
Video playback is slower than on previous releases -- this is most noticeable when playing HD 720p video.
Bluetooth is broken at the moment after changes for Qualcomm Bluetooth chipsets were merged into CyanogenMod.
Current releases of Netflix do not work with CM10.2 -- version 1.8.1 is the last version known to work. If you want/need a newer release of Netflix, look into the Xposed mod, which provides a workaround for Netflix -- pastordl has done a nice writeup of the process here.
ART (the experimental Android runtime introduced in 4.4) is not supported -- if you enable it, your system will not boot. (Workarounds may exist, but they are not going to be officially supported either -- use them at your own risk.)
Download:
http://download.cyanogenmod.org/?device=encore&type=nightly
Note that an updated recovery is required to install CM11. ClockworkMod 6.0.4.8 and newer versions should work, as should other recoveries provided the required changes are included. (Ask the maintainer of the recovery if you're not sure.) NOTE: Do not use ClockworkMod 6.0.3.x builds older than 6.0.3.6, as they contain a bug which may brick your device!
Source code:
https://github.com/CyanogenMod/android_device_bn_encore/tree/cm-11.0 (device-specific source)
https://github.com/CyanogenMod/android_kernel_bn_encore (kernel)
https://github.com/CyanogenMod/android/tree/cm-11.0 (manifest for the rest of the CyanogenMod source)
Build instructions (discussion of build issues belongs in the development thread)
This release is the product of much effort by many people over a considerable period: many thanks to fattire, keyodi, eyeballer, krylon360, dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, drmarble, mateor, dhiru1602 and many more. Thanks are also due to the CyanogenMod project, upon which we are building, and Texas Instruments, which historically provided excellent support for its embedded platforms to the open-source hacking community.
XDA:DevDB Information
CyanogenMod 11 Nightly Builds, ROM for the Barnes & Noble Nook Color
Contributors
steven676, keyodi, fattire, The CyanogenMod Project, NookieDevs, many others (see post)
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-01-30
Last Updated 2014-05-15
Google Apps; other CyanogenMod builds
Google Apps
http://wiki.cyanogenmod.org/w/Google_Apps
As of 2014/07/25, the latest release for CM11 that is known to work is 20140105. DO NOT use the 20140606 release unless installing to SD card -- it contains over 100 MB of additional bloat and will not fit on an eMMC installation!
If you wish to use another Google apps package, and are installing on eMMC, please note that the Nook Color has what is by modern standards a limited amount of disk space available on /system (440 MB) -- the base system is currently in the neighborhood of 300 MB, so some of the larger packages will not fit. If you're offered different variants, choose the smallest one in order to avoid problems.
Please make sure that you have the correct Google Apps flashed before reporting problems involving the Google Apps (Play Store, Google Keyboard, etc.).
Other CyanogenMod builds
This is the thread for CM11 nightly builds. There are other official CyanogenMod builds for Nook Color available:
Stable releases of CM10.2 and CM10.1 -- these are the releases to use if you don't want to be on the bleeding edge.
Archived nightly builds for CM10.2, CM10.1, and CM10. You may find the last CM10 nightly (20130421) faster than the later releases, particularly during playback of HD 720p video.
Please check that your questions are in the appropriate thread. (If you're interested, there's lots of past discussion in those threads, as well as the development thread.)
Frequently Asked Questions and Troubleshooting
The install fails with errors from "set_metadata_recursive"!
The installation appears to succeed, but nothing's changed when I reboot!
You'll need an updated recovery to install CM11. For CM11 nightly builds from May 16 and later, any recovery that reports itself as ClockworkMod 6.0.4.8 or later should work; other non-CWM recoveries should work if they incorporate the necessary changes to suppor these builds (you'll have to ask their maintainers for details).
For older CM11 nightlies, any recovery that reports itself as ClockworkMod 6.0.3.6 or later should work; other non-CWM recoveries such as TWRP 2.6.3.0 or later should be fine provided the kernel is sufficiently new (you'll have to ask their maintainers for details). NOTE: Do not use ClockworkMod 6.0.3.x builds older than 6.0.3.6, as they contain a bug which may brick your device!
I installed CM11, wiped /data, and now my tablet's been booting for an awfully long time. Is something wrong?
First boot will take at least five minutes, and the boot animation currently stops many times during this process. If you've been waiting more than 10 minutes and it's still not booted up, you probably have a problem.
The soft keyboard keeps crashing!
The Play Store is acting up!
Did you flash the correct Google Apps? If on an eMMC install, are you sure your Google Apps fit on /system?
How do I install this to an external SD card?
See this excellent guide by leapinlar for instructions. It's reported that Google apps installation is broken in the SD card installer at the moment, so you may need to wait for that to be fixed.
What happened to the "Developer options" and "Performance" screens in Settings?
They're hidden by default now in CM10.1 and later. To show them, go into "About tablet" and tap the build number (for CM11 nightlies, it'll be something starting with "cm_encore-userdebug 4.4.2 KOT49H" or "cm_encore-userdebug 4.4.3 KTU84M") seven times.
How do I get the Honeycomb/ICS tablet UI?
You can't -- Google killed it off in Android 4.4.
The lock screen doesn't rotate!
The screen doesn't rotate to the sides I want!
Particularly if you're upgrading from an existing install, you may find that the preferences for screen rotations are incorrectly set. Go to Settings->Display->Rotation and check that "Auto-rotate screen" and (if you want the lock screen to rotate) "Rotate lock screen" are set.
For the allowed screen orientations, selecting 0, 180 and 270 degrees will cover the rotations that you probably want. If you want details:
Android likes to think of the "natural" orientation (0 degrees rotation) as landscape with the N key on the right side of the screen. (This is a change from CM10 and earlier, when we were carrying a hack to change this.) The degrees of rotation are counted in the counterclockwise direction, so in essence, each of the rotation settings allows the following:
0 degrees: landscape orientation with the N key on the right side of the screen
90 degrees: portrait orientation with the N key on top ("upside down")
180 degrees: landscape orientation with the N key on the left side of the screen
270 degrees: portrait orientation with the N key on the bottom ("right side up")
I enabled ART, and now my Nook Color won't boot!
ART isn't supported on Nook Color at the moment due to known issues:
The initial compiling pass that happens the first time you enable ART may cause your tablet to run out of both RAM and disk space.
Many of the Google apps packages for CM11 are incompatible with ART.
If you're currently stuck in a bootloop after enabling ART, boot into recovery and then see this post by fattire for advice on how to restore your system to a working state.
I can't get any of the ROMs or recoveries for Nook Color to boot!
Before you go any further -- are you sure you have a Nook Color and not a Nook Tablet? The two devices look almost identical, but Nook Color (model number BNRV200 -- check the fine print near the speaker grille on the back) has a dark gray bezel, while Nook Tablet (BNTV250) has a light gray or silver bezel. The two devices are not interchangeable -- Nook Color software will not boot on Nook Tablet and vice versa.
If you've got a Nook Tablet, you want to be in the Nook Tablet forums instead.
I'm having a problem with my Nook Color running CM11.
That's not a question
Okay, I'm having a problem with my Nook Color running CM11 -- is there something I can do to troubleshoot?
Glad you asked! Please check the following:
Does the problem occur with a clean install of CM11? This means wiping /data and not restoring a Nandroid backup afterwards. Don't restore system apps and/or their data in Titanium Backup either (user apps/data are okay).
Are you overclocking? If so, does the problem occur when you set the maximum clock speed to 1000 MHz or below? To be clear, we are not interested at this point in bug reports of any kind that happen if you have the maximum CPU speed set above 1000 MHz. If you're experiencing system crashes or "sleep of death" (SOD), you may also wish to try capping the CPU clock speed to 800 MHz (but if this helps, please report your problem here and fill out the hardware survey).
Do you have any patches, custom kernels, or other tweaks applied? If you do, does the problem occur without those applied? (We're not necessarily going to ignore bug reports from patched or tweaked systems outright, but it can make our job harder, and we do need to know what changes you have applied to judge whether or not the change might be relevant to your problem.)
I'm having no luck with the suggestions above. What information should I include with my bug report?
When reporting a problem, please include the following information if at all possible:
Full description of the problem -- "it crashes" doesn't count. How do you trigger the problem (or does it occur by itself)? What exactly happens when the problem occurs? How often does it happen?
For problems with apps or specific pieces of the system software: we'll almost certainly ask for a logcat of the event, so you'll save everyone some time by including it.
For problems involving system freezes, crashes, or SOD: if you can connect to the tablet via adb while it's "unresponsive", please provide dmesg and logcat output from that time. If you cannot, try power-cycling it while it's still plugged into USB, and provide dmesg output from immediately after the reboot, plus the contents of /proc/last_kmsg if that file exists (let us know if it doesn't).
For unexpected reboots: provide the contents of /proc/last_kmsg from after the reboot.
Now that everyone has squared me away (in the 10.2 thread) on the you-need-CWM-6.0.4.5-to-flash-CM11 issue, I hafta say, after 2-3 hrs, this CM11 is quite good! No hard numbers, sorry, but seems reliable, faster than 7.2, and, of course, the UI is vastly better. Waytago steven676, keyodi, fattire! Thanks!
Hello everyone,
To run off of an SD; I created a new SD (sandisk 8gb) with the latest image from Leapilar, the nightly and suggested GAPPS (gapps-kk-20140105-signed.zip). There were some error messages from the GAPPS (they scrolled off before I could really read them). The NC booted to the desktop but there was no play store.
Any ideas?
Thanks,
V
volpo222 said:
Hello everyone,
To run off of an SD; I created a new SD (sandisk 8gb) with the latest image from Leapilar, the nightly and suggested GAPPS (gapps-kk-20140105-signed.zip). There were some error messages from the GAPPS (they scrolled off before I could really read them). The NC booted to the desktop but there was no play store.
Any ideas?
Thanks,
V
Click to expand...
Click to collapse
If your errors match the ones reported on the SD installer thread:
bowguy said:
I then tried to install the 2014/01/05 gapps package using your/verygreen's script and saw this message:
"Hangouts.apk exists but is not a regular file" The script died at this point and shutdown. After booting, you cannot add a google account as it appears it is a very incomplete gapps install.
Click to expand...
Click to collapse
then it's the bug mentioned in the FAQ -- it looks like the SD installer needs an update.
deleted
Just curiuos if anyone has an oppinion to how cm11 is running on the device. I originally flashed cm10.1 when I first rooted and it ran INSANELY slow and laggy, probably due to the low ram etc. But was forced to run CM7 and it ran perfectly and have been running it ever since. I know that 4.4 is supposed to have lower dependencies for running on older/slower devices but anyone got some input on just how good it runs? I am going to probably try it later on tonight, it will just take me a while cause i got to backup my sons game data first or hill kill me.
tp2215 said:
Just curiuos if anyone has an oppinion to how cm11 is running on the device. I originally flashed cm10.1 when I first rooted and it ran INSANELY slow and laggy, probably due to the low ram etc. But was forced to run CM7 and it ran perfectly and have been running it ever since. I know that 4.4 is supposed to have lower dependencies for running on older/slower devices but anyone got some input on just how good it runs? I am going to probably try it later on tonight, it will just take me a while cause i got to backup my sons game data first or hill kill me.
Click to expand...
Click to collapse
Just DOOOO it
(not that I'm encouraging you one way or the other)
steven676 said:
If your errors match the ones reported on the SD installer thread:
then it's the bug mentioned in the FAQ -- it looks like the SD installer needs an update.
Click to expand...
Click to collapse
Yes that's it then.
I hope this gets worked out. 4.4 was very smooth and worked well.
V
Thanks guys just flashed it and so far this looks great, I'd say it's smoother than 10.2 and multitasking is just a bit better. Couple of small issues came across were rebooting to recovery doesn't work for me it just reboots, also had a soft reboot and after it booted up the systemui kept crashing and wouldn't let you do anything, but a regular reboot fixes it.
Just flashed in it looks great! Feels MUCH smoother and snappier then 10.2. Minor issue that boot take a long time. It seems to me like the boot keeps freezing but eventually continues. No force closes or anything. I am trying now to enable ART and play with it a little to see if it drasticaly improves it. It seemed to make a little bit of a difference on my S3.
Edit: You may want to add to the op, DO NOT enable ART. It sends it into a reboot loop.
tp2215 said:
]
Edit: You may want to add to the op, DO NOT enable ART. It sends it into a reboot loop.
Click to expand...
Click to collapse
Yeah, actually steven, if someone has issues with ART you might wanna link here. You can recovery from an ART bootloop w/o reinstalling or anything weird.
tp2215 said:
Just flashed in it looks great! Feels MUCH smoother and snappier then 10.2. Minor issue that boot take a long time. It seems to me like the boot keeps freezing but eventually continues. No force closes or anything. I am trying now to enable ART and play with it a little to see if it drasticaly improves it. It seemed to make a little bit of a difference on my S3.
Edit: You may want to add to the op, DO NOT enable ART. It sends it into a reboot loop.
Click to expand...
Click to collapse
bowguy said:
I found out how to enable ART on the Nook Color. When you select ART as the runtime in Developer options, the tablet reboots but gets stuck in a bootloop. The problem is during bootup, a lot of files are being converted but the Nook runs out of memory. Then it crashes, reboots and tries again and never gets past it. However the boot animation takes a lot of memory during this process.
Solution: Disable boot animation. What you need to do is open the File Manager app. Go to settings (lower right icon) and General Settings. Under Advanced, Access Mode, select either User Prompt or Root Access mode. You need to alter a root file. Any prompts you get make sure to allow superuser access.
Now navigate to /system touch on build.prop and open with "Editor". Add the following line to the end of the file:
debug.sf.nobootanimation=1
Save the file and exit File Manager.
DO NOT ENABLE ART NOW!!
First make sure you did this correctly by rebooting your nook. Make sure you DO NOT see the Cyanogen logo when it boots up - it will take a while with a blank screen and then go to your standard lock screen. If you see the animation logo, you did something wrong, try again.
Now you can enable ART in the Developer Options. When it reboots, wait a while (2 min?) then you should see the optimizing apps display. A basic install with gapps has about 85 apps to convert. This will take a while.
Report back with results!
Click to expand...
Click to collapse
We are working on it. There is a modification pending that might fix this but hasn't been tested yet.
tp2215 said:
Just flashed in it looks great! Feels MUCH smoother and snappier then 10.2. Minor issue that boot take a long time. It seems to me like the boot keeps freezing but eventually continues. No force closes or anything. I am trying now to enable ART and play with it a little to see if it drasticaly improves it. It seemed to make a little bit of a difference on my S3.
Edit: You may want to add to the op, DO NOT enable ART. It sends it into a reboot loop.
Click to expand...
Click to collapse
fattire said:
Yeah, actually steven, if someone has issues with ART you might wanna link here. You can recovery from an ART bootloop w/o reinstalling or anything weird.
Click to expand...
Click to collapse
Yeah, release noted and added to the FAQ. We'd known about this earlier, but it slipped my mind when I was writing up the release notes
bowguy said:
We are working on it. There is a modification pending that might fix this but hasn't been tested yet.
Click to expand...
Click to collapse
Be aware that this may not work for you if you've installed to eMMC on a Nook Color with a 1 GB /data partition -- disabling the boot animation saves RAM, but won't prevent you from running out of disk space to store the ART compiler output (the "oat" files).
bowguy said:
We are working on it. There is a modification pending that might fix this but hasn't been tested yet.
Click to expand...
Click to collapse
If you compiled cm-11.0 with width 480 boot animation, ART will work. Initial boot and optimiziation will be longer than with Dalvik. You also get smoother boot animation. Also, revert boot to landscape in kernel config while you're at it.
tp2215 said:
Just curiuos if anyone has an oppinion to how cm11 is running on the device. I originally flashed cm10.1 when I first rooted and it ran INSANELY slow and laggy, probably due to the low ram etc. But was forced to run CM7 and it ran perfectly and have been running it ever since. I know that 4.4 is supposed to have lower dependencies for running on older/slower devices but anyone got some input on just how good it runs? I am going to probably try it later on tonight, it will just take me a while cause i got to backup my sons game data first or hill kill me.
Click to expand...
Click to collapse
Same here - both 10.1 and now 11.0 are slow. I was hoping a clean install and CM11 would cure the slowness.
I am at work and don't have my nook with me so will have to gather data tonight. its been along time since I even turned on the nook so I am no even sure what my memory config is.
But AWESOME work all you nookie devs!
For those that need them, here are flashable zips of CWM 6.0.4.7:
EMMC Recovery: http://techerrata.com/file/eyeballer/twrp/cwm-6.0.4.7-encore-signed.zip
EMMC AltBoot: http://techerrata.com/file/eyeballer/twrp/cwm-6.0.4.7-encore-ALT-signed.zip
Also, I've built an updated TWRP 2.6.3.0 which is compatible with CM11 and would appreciate some testers to confirm everything is working, please see here and report feedback in that thread only: http://forum.xda-developers.com/showthread.php?p=49886829
wifi bug
Only issue for me so far (on the 1/29) is that if I set settings/wifi/advanced to "keep wifi on during sleep/only while pugged in" it won't re-connect when waking up. Have to re-connect manually. Leaving wifi on permanently for now.
ibilln said:
Only issue for me so far (on the 1/29) is that if I set settings/wifi/advanced to "keep wifi on during sleep/only while pugged in" it won't re-connect when waking up. Have to re-connect manually. Leaving wifi on permanently for now.
Click to expand...
Click to collapse
drmarble posted a patch in the dev thread, so you can fix it if you're building yourself.
Sadly, the official nightlies aren't fixed yet. So I can confirm this known bug
I also had a reboot while displaying a gif in QuickPic. When it came back, the default launcher was reset and its init messages were shown
It's the first reboot I ever had on CM11. I attached the last_kmesg for your troubleshooting pleasure. I hope there's something valuable in there
The NookieDevs are pleased to announce the CyanogenMod 10.2.1 stable release for the Nook Color!
As the "stable" label suggests, all major features of the hardware work and the release should be suitable for day-to-day use on your Nook Color. As the "stable" label also suggests, updates (if any) will be primarily to fix bugs -- new features and big changes should not be expected.
Highlights: (not news if you've been keeping up with CM10.2 nightlies)
Linux kernel 3.0.8, plus hardware support from TI OmapZoom's android-omap3-3.0 branch and board support forward-ported from BN kernel releases. (Yes, we went backwards from the last 10.2 nightlies to avoid some rare crashes suspected to be related to the USB/charger port driver.)
All of the features of CyanogenMod 10.2, based on Android 4.3. All of the changes and bugfixes up to our last CM10.2 nightly (20140119) are included in this stable release.
Full 2D and 3D graphics acceleration using the GPU, with improved performance over previous releases.
Known issues:
Current releases of Netflix do not work with CM10.2 -- version 1.8.1 is the last version known to work. If you want/need a newer release of Netflix, look into the Xposed mod, which provides a workaround for Netflix -- pastordl has done a nice writeup of the process here.
This release represents the end of active development on CM10.2 -- future efforts will focus on ROMs based on Android 4.4 and later. Critical bugfixes (for security holes, device-bricking bugs, eat-my-data bugs and the like) may be distributed as point releases (CM10.2.1.x); other important bugfixes (if any) will be distributed as patches on top of the 10.2.1 release.
Download:
https://download.cyanogenmod.org/get/jenkins/57353/cm-10.2.1-encore.zip
After flashing the above package, installing the latest kernel patch for CM10.2.1 is strongly recommended.
Code:
MD5: b4ad9daaf2335b96455795867dd5e667
SHA1: ae30dbc7946dd67a044dc972c8718628046a0c7c
SHA256: 0c35a2ab2592a83fb3b8c376c928ea1f9bb91da996d2928d51c6f9e898c48489
Source code:
https://github.com/CyanogenMod/android_device_bn_encore/tree/cm-10.2.1 (device-specific source)
https://github.com/CyanogenMod/android_kernel_bn_encore/tree/cm-10.2.1 (kernel)
https://github.com/CyanogenMod/android/tree/cm-10.2.1 (manifest for the rest of the CyanogenMod source)
Build instructions (discussion of build issues belongs in the development thread)
This release is the product of much effort by many people over a considerable period: many thanks to fattire, keyodi, eyeballer, krylon360, dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, drmarble, mateor, dhiru1602 and many more. Thanks are also due to the CyanogenMod project, upon which we are building, and Texas Instruments, which historically provided excellent support for its embedded platforms to the open-source hacking community.
XDA:DevDB Information
CyanogenMod 10.2 Stable, ROM for the Barnes & Noble Nook Color
Contributors
steven676, keyodi, fattire, The CyanogenMod Project, NookieDevs, many others (see post)
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 10.2.1
Stable Release Date: 2014-02-01
Created 2014-02-01
Last Updated 2014-06-06
Google Apps; other CyanogenMod builds
Google Apps
http://wiki.cyanogenmod.org/w/Google_Apps
As of 2014/02/01, the latest release for CM10.2 is 20130813, but please check the linked page for updates.
Please make sure that you have the correct Google Apps flashed before reporting problems involving the Google Apps (Play Store, Google Keyboard, etc.).
Other CyanogenMod builds
This is the thread for CM10.2 stable releases. There are other official CyanogenMod builds for Nook Color available:
CM11 nightly builds -- these experimental builds, based on Android 4.4, contain the latest changes to CyanogenMod and to hardware support for the Nook Color. As the name suggests, new builds are made and posted (roughly) every day; these builds are fully automatic, with no testing done before posting.
CM10.1 stable releases -- while the state of the Nook Color-specific hardware support should be nearly identical to that of CM10.2, you may find this Android 4.2-based release more (or less!) stable than this Android 4.3-based one.
Archived nightly builds for CM10.2, CM10.1, and CM10. You may find the last CM10 nightly (20130421) faster than the later releases, particularly during playback of HD 720p video.
Please check that your questions are in the appropriate thread. (If you're interested, there's lots of past discussion in those threads, as well as the development thread.)
Frequently Asked Questions and Troubleshooting
The soft keyboard keeps crashing!
The Play Store is acting up!
Did you flash the correct Google Apps?
How do I install this to an external SD card?
See this excellent guide by leapinlar for instructions.
What happened to the "Developer options" and "Performance" screens in Settings?
They're hidden by default now in CM10.1 and later. To show them, go into "About tablet" and tap the build number (for CM10.2.1 stable, "cm_encore-userdebug 4.3.1 JLS36I bf3d49df9c test-keys") seven times.
How do I get the Honeycomb/ICS tablet UI?
You want to use the Auto-Patcher to modify your ROM for the tablet UI. (Don't forget to thank Caldair for maintaining the Tablet UI mod, and mateorod and the rest of the Auto-Patcher developers for building that tool.)
The lock screen doesn't rotate!
The screen doesn't rotate to the sides I want!
Particularly if you're upgrading from an existing install, you may find that the preferences for screen rotations are incorrectly set. Go to Settings->Display->Rotation and check that "Auto-rotate screen" and (if you want the lock screen to rotate) "Rotate lock screen" are set.
For the allowed screen orientations, selecting 0, 180 and 270 degrees will cover the rotations that you probably want. If you want details:
Android likes to think of the "natural" orientation (0 degrees rotation) as landscape with the N key on the right side of the screen. (This is a change from CM10 and earlier, when we were carrying a hack to change this.) The degrees of rotation are counted in the counterclockwise direction, so in essence, each of the rotation settings allows the following:
0 degrees: landscape orientation with the N key on the right side of the screen
90 degrees: portrait orientation with the N key on top ("upside down")
180 degrees: landscape orientation with the N key on the left side of the screen
270 degrees: portrait orientation with the N key on the bottom ("right side up")
I'm having a problem with my Nook Color running CM10.2.
That's not a question
Okay, I'm having a problem with my Nook Color running CM10.2 -- is there something I can do to troubleshoot?
Glad you asked! Please check the following:
Does the problem occur with a clean install of CM10.2? This means wiping /data and not restoring a Nandroid backup afterwards. Don't restore system apps and/or their data in Titanium Backup either (user apps/data are okay).
Are you overclocking? If so, does the problem occur when you set the maximum clock speed to 1000 MHz or below? To be clear, we are not interested at this point in bug reports of any kind that happen if you have the maximum CPU speed set above 1000 MHz. If you're experiencing system crashes or "sleep of death" (SOD), you may also wish to try capping the CPU clock speed to 800 MHz (but if this helps, please report your problem here and fill out the hardware survey).
Do you have any patches, custom kernels, or other tweaks applied? If you do, does the problem occur without those applied? (We're not necessarily going to ignore bug reports from patched or tweaked systems outright, but it can make our job harder, and we do need to know what changes you have applied to judge whether or not the change might be relevant to your problem.)
I'm having no luck with the suggestions above. What information should I include with my bug report?
When reporting a problem, please include the following information if at all possible:
Full description of the problem -- "it crashes" doesn't count. How do you trigger the problem (or does it occur by itself)? What exactly happens when the problem occurs? How often does it happen?
For problems with apps or specific pieces of the system software: we'll almost certainly ask for a logcat of the event, so you'll save everyone some time by including it.
For problems involving system freezes, crashes, or SOD: if you can connect to the tablet via adb while it's "unresponsive", please provide dmesg and logcat output from that time. If you cannot, try power-cycling it while it's still plugged into USB, and provide dmesg output from immediately after the reboot, plus the contents of /proc/last_kmsg if that file exists (let us know if it doesn't).
For unexpected reboots: provide the contents of /proc/last_kmsg from after the reboot.
Is there any way to increase touch screen sensitivity?
The app in Google play is not compatible.
Thanks
Just check the Nook Color Dev Page if there are any Development, and Lo and behold! THANK YOU SO MUCH FOR STILL SUPPORTING NOOK COLOR! YOU GUYS REALLY ROCK!
Kernel security patch (upgrade strongly recommended!)
A security bug in the core kernel (CVE-2013-6282) allows users to read and write arbitrary kernel memory on machines with ARMv6k and ARMv7 CPUs -- including the Nook Color -- and is therefore exploitable for privilege escalation (root) by a local attacker on any device with those CPUs.
The attached kernel (source: https://github.com/steven676/ti-omap-encore-kernel3/tree/cm-10.2.1p1) contains a patch for this bug. The CVE entry notes that this bug has been exploited in the wild since October, so it's strongly recommended that you upgrade as soon as possible. (I apologize for this -- this is the sort of thing that I should have picked up much, much earlier than I actually did.)
CM10.1.3 users: you can use this kernel, but it'll break wifi unless you also rebuild the wireless driver modules -- use the kernel on the CM10.1 stable thread instead. CM11 nightly users: upgrade to a nightly from February 19 or later to get this fix. See my post on the dev thread for more information.
(If you're wondering, I am hoping to get a full CM10.2 point release with this fix included, but that may take some time, as a large number of other devices are affected and we should really try to get all of them fixed.)
Hashes for the attached kernel zip:
Code:
MD5: 991fc7c013f72dc950e32a7b08acd652
SHA1: 88664d4783c97184714ff94730546b36d634b40e
SHA256: 8aec80a185aeee358a68cc0f8aea062a56cef8f0a849c2c7382e4e14467d8b97
steven676 said:
A security bug in the core kernel (CVE-2013-6282) allows users to read and write arbitrary kernel memory on machines with ARMv6k and ARMv7 CPUs -- including the Nook Color -- and is therefore exploitable for privilege escalation (root) by a local attacker on any device with those CPUs.
The attached kernel (source: https://github.com/steven676/ti-omap-encore-kernel3/tree/cm-10.2.1p1) contains a patch for this bug. The CVE entry notes that this bug has been exploited in the wild since October, so it's strongly recommended that you upgrade as soon as possible. (I apologize for this -- this is the sort of thing that I should have picked up much, much earlier than I actually did.)
CM10.1.3 users: you can use this kernel, but it'll break wifi unless you also rebuild the wireless driver modules -- use the kernel on the CM10.1 stable thread instead. CM11 nightly users: upgrade to a nightly from February 19 or later to get this fix. See my post on the dev thread for more information.
(If you're wondering, I am hoping to get a full CM10.2 point release with this fix included, but that may take some time, as a large number of other devices are affected and we should really try to get all of them fixed.)
Hashes for the attached kernel zip:
Code:
MD5: 991fc7c013f72dc950e32a7b08acd652
SHA1: 88664d4783c97184714ff94730546b36d634b40e
SHA256: 8aec80a185aeee358a68cc0f8aea062a56cef8f0a849c2c7382e4e14467d8b97
Click to expand...
Click to collapse
Installed kernel could not get wifi working. Reverted to last nightly runs fine.
Both this kernel and the CM10.2.1 do not work with Network Speed Indicator - by fatminmin. http://forum.xda-developers.com/showthread.php?t=2636971 it is something to do with the 3.0.8 kernel build. This works fine with CM 10.2 nightly 1/19 and with CM11.
This ROM does not boot for me.
Full wipe, flash ROM and gapps, reboot, and sticks on black screen. No boot animation or anything.
Do I need the latest TWRP 2.3.6.0 to flash this properly? (On 2.3.1.0 now.)
Firehawk989 said:
This ROM does not boot for me.
Full wipe, flash ROM and gapps, reboot, and sticks on black screen. No boot animation or anything.
Do I need the latest TWRP 2.3.6.0 to flash this properly? (On 2.3.1.0 now.)
Click to expand...
Click to collapse
By full wipe did you mean a factory reset? Also check the md5 on the ROM.
2.3.1.0 works with the CM10.2 ROM. You can get TWRP 2.4.1.0 here :
http://forum.xda-developers.com/showthread.php?t=2653483
pastordl said:
By full wipe did you mean a factory reset? Also check the md5 on the ROM.
2.3.1.0 works with the CM10.2 ROM. You can get TWRP 2.4.1.0 here :
http://forum.xda-developers.com/showthread.php?t=2653483
Click to expand...
Click to collapse
Yea, factory reset. Tried two different downloads on two different computers. I'll try it and see with 2.4.1.0 though.
CM 10.1.3 works fine, and I had some of the January CM 10.2 nightlies running on it fine as well.
This was happening in November nightlies for me and it's still and issue in the stable release.
It's not a huge deal but it can be really annoying.
You know the open recent/open apps button in the bottom navigation bar?
All the other ones work but this button stops functioning relatively frequently, but of a pain because that's my main use for that tablet ui navbar.
By not functioning I just mean it does nothing when you press it, it's just a inactive button so to speak.
I can fix it (temporarily because it stops working again and again) by going into settings > interface > [navigation bar] buttons and layout.
And then just reset it.
Love the rom but this happens too frequently its quite annoying, anyone else have this issue, it's kind of a silly issue I hope there's some fix.
Thanks
Firehawk989 said:
Yea, factory reset. Tried two different downloads on two different computers. I'll try it and see with 2.4.1.0 though.
CM 10.1.3 works fine, and I had some of the January CM 10.2 nightlies running on it fine as well.
Click to expand...
Click to collapse
Try the 1-19 nightly available through this thread:
http://forum.xda-developers.com/showthread.php?t=2653483
Look under "Where can I get older releases" follow the link. You'll have to scroll down quite a bit.
They reverted to an older kernel for the "stable" release. I had some different issues with that kernel (see post 7). I stayed with the 1/19 nightly and have had no issues.
pastordl said:
Try the 1-19 nightly available through this thread:
http://forum.xda-developers.com/showthread.php?t=2653483
Look under "Where can I get older releases" follow the link. You'll have to scroll down quite a bit.
They reverted to an older kernel for the "stable" release. I had some different issues with that kernel (see post 7). I stayed with the 1/19 nightly and have had no issues.
Click to expand...
Click to collapse
Tried with TWRP 2.4.1 that you linked me to and still same problem. Must be the kernel as you say.
Will try the 1/19 nightly. Had they fixed the battery life/wakelock issue at that point? That was my only problem with 10.2. I get no wakelock problems and 4 or 5 days of battery life with CM 10.1, so I'll just stick with that if there are still issues in 10.2.
Thanks for your help!
USB Host Mode - sorry if beating a dead horse here...
I haven't checked back in a long, long time....but are there any kernel patches to enable usb host/peripheral switching?
Firehawk989 said:
This ROM does not boot for me.
Full wipe, flash ROM and gapps, reboot, and sticks on black screen. No boot animation or anything.
Do I need the latest TWRP 2.3.6.0 to flash this properly? (On 2.3.1.0 now.)
Click to expand...
Click to collapse
I was having the same problem with this as well. It wouldn't boot the loading screen. I gave up and settled for CM 10.1.3 which worked just fine. There's an option to update to 10.2 from the OS but I won't be taking that risk.
I was able to install 10.2.1 with no problems on a friend's NC. But with one of my own, the boot leads to a black screen. I did a factory reset, used a fresh download and tried from both TWRP and CWM. I have not yet tried to install on my other NC, whcih I know has different hardware.
Deleted
polymath257 said:
I was able to install 10.2.1 with no problems on a friend's NC. But with one of my own, the boot leads to a black screen. I did a factory reset, used a fresh download and tried from both TWRP and CWM. I have not yet tried to install on my other NC, whcih I know has different hardware.
Click to expand...
Click to collapse
It'd be helpful to know about the hardware on which the boot is failing -- could you fill out the hardware survey for that device?
steven676 said:
It'd be helpful to know about the hardware on which the boot is failing -- could you fill out the hardware survey for that device?
Click to expand...
Click to collapse
Done.
I don't know if this will be helpful or not, but I was able to get CM 10.2.1 to install on my other NC. I did a comparison of the hardware by using the website suggested (I did not file a report for the second NC, though). What I found is interesting:
1. Both devices are using ES1.2
2. Both devices are using ft5x06
3. Both devices have Mainboard serial numbers in the A6 series.
4. The device where the install *works* went thorugh some suspend/resume cycles on ft5x06 and did reset_panel_via_gpio several times
5. The device where the install *fails* did not go the suspend/resume cycles or the resets in 3.
6. The device where the install *works* was made on 09/03/2011
7. The device where the install *fails* was made on 10/09/2011
If there is any more information or help I can provide, let me know.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.
This rom is for both the Nook Tablet 512M/8GB and 1GB/16GB versions. The device code name is "acclaim".
Prerequisites:
A recovery. To install a recovery when coming from a stock device, you need to prepare a special SD card. Installation instructions can be found here on xda.
Installation:
Grab a new recovery (e.g. here https://dl.dropboxusercontent.com/u...cclaim-eng-recovery-UNOFFICIAL-20150606.0.img) and flash it with fastboot.
If you have a CM 10.1 or CM 11 installed, flash the new recovery and try the updater, otherwise download the zip from nightlies, boot to CWM and flash it.
Once a version is installed (and all bugs fixed), you will be able to use CM Updater
Settings->About tablet->CyanogenMod updates->Refresh
THE NEW NIGHTLIES HAVE EMULATED STORAGE ENABLED. YOU LOOSE ALL YOUR DATA. MAKE SURE YOU BACKUP!!!! THE INTERNAL EMMC 1GB PARTITION IS ALSO NOT ACCESSIBLE ANYMORE. COPY THE CONTENT. THE EXTERNAL SDCARD IS NOT USED ANYMORE AS PRIMARY STORAGE. ALL APP DATA ON THE SDCARD WILL BE LOST. I ALSO RECOMMEND TO WIPE.
BACKUP!
RE-PARTITIONING IS NOT MANDATORY. IF YOU WANT TO RECLAIM THE 1GB PARTITION (called media) YOU CAN TRY TO FOLLOW THE RE-PARTITION GUIDE:
https://docs.google.com/document/d/1wSAaAZfQcnvkiHKlbZ7_H1h67m2kx0mq-p3Wjgue3qA/edit?usp=sharing
PLEASE COMMENT ON THE DOCUMENT IF SOMETHING IS NOT CLEAR.
Building:
The CM wiki explains that here: http://wiki.cyanogenmod.org/w/Build_for_acclaim
Returning to stock BN firmware:
If you have installed above rom and the CWM recovery and you really hate it and want to go back to stock, you may wish to try to flash the original acclaim_update.zip from BN. You have to unzip that file and edit META-INF/com/google/android/updater-script. Drop the first two lines here:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Zip the package again. Then go to recovery, flash the zip, wipe, and reboot.
Support:
For any issues encountered, please post into this forum, but add steps to reproduce and dmesg, logcat and audit.log information. If you don't know what this is or how to get them, try to find that out first before posting here.
Thanks:
hashcode, ntemis, kuzma30, fattire, mik_os, chrmhoffmann, and many others that contribute to cyanogenmod and especially this version.
kuzma30 - great kernel job
hashcode - we have reused lots of your work and effort for the various omap devices (esp kindle fire). It is thanks to you mainly that we are now official CM device. Also many thanks for the L bringup help.
mik_os - great touchscreen firmware flasher and other efforts
fattire - for helping us everywhere he can
ntemis - thanks for giving so much energy to this - esp for 4.4 and L I have copied lots of things from you
DISCLAIMER:
- update the CWM if you come from older versions - otherwise you'll see funny error messages when installing zip
- It is possible that you need to wipe your device. I did not do that, but...
- Also you must flash gapps. It can be found somewhere....
ATTENTION: IT SEEMS THAT DHACKER'S L GAPPS ARE TOO BIG TO FIT INTO THE SYSTEM PARTITION. Try to find a smaller one.
- The SELINUX policies are enforced now.
Known issues:
- system partition is too small for full gapps. use a mini gapp package.
- the touchscreen firmware flasher doesn't work on L. Use CM11 to flash it first.
Recently fixed:
- f2fs
- kernel updated to latest 3.0 stable
- developer settings and setup wizard (if you select backup) crash. that's fixed in nightly from 8-FEB-15.
- device encryption does work now (but who wants to do that? the device is laggy enough already )
- cmupdate / cm recovery: adb reboot recovery and cmupdater and auto install. Hopefully this is fixed now (not in nice way, but...). You need sdcard inserted to make this work (but I guess everybody has that anyway).
Get it from
http://download.cyanogenmod.org/?device=acclaim
Get ENG recovery from here. It allows to adb into recovery even when data is wiped.
File: https://dl.dropboxusercontent.com/u...cclaim-eng-recovery-UNOFFICIAL-20150606.0.img
md5sum: 6136fc49c5e9a32f115d40d762bb6f2d
Reserved
...
Amazing work Chris, Let the flashing begin.
Been waiting for this for quite a while! I can put off learning to build for another few months!
For gapps, I recommend TKRuzze's Gapps. (Just search for them on Google.) His Pico-Gapps package is pretty lightweight.
UPDATE: Couldn't flash with the provided recovery. I was able to flash it successfully using TWRP 2.8.4.0 though.
Hi,
Odd. I flashed the same (before uploading).
Did you upgrade recovery? Did you check md5 of download?
Chris
chrmhoffmann said:
Hi,
Odd. I flashed the same (before uploading).
Did you upgrade recovery? Did you check md5 of download?
Chris
Click to expand...
Click to collapse
ROM: 78f32eb89778b31a569644b21fc1e8f3
Recovery: d37f29808a682e7806fa7b77dc940453
Installed just fine here, even Netflix works!!
thanks for everyone's hard work.
topdawg7793 said:
Been waiting for this for quite a while! I can put off learning to build for another few months!
For gapps, I recommend TKRuzze's Gapps. (Just search for them on Google.) His Pico-Gapps package is pretty lightweight.
UPDATE: Couldn't flash with the provided recovery. I was able to flash it successfully using TWRP 2.8.4.0 though.
Click to expand...
Click to collapse
Can you share where you got the download for twrp 2.8.4.0? Thanks!
Sent from my LG-E970 using XDA Free mobile app
billy8362 said:
Can you share where you got the download for twrp 2.8.4.0? Thanks!
Sent from my LG-E970 using XDA Free mobile app
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/acclaim
Download the latest version, rename it to "recovery.img". Flash it in fastboot.
If you'd rather not go that route, download a flashable of an older version of TWRP, use 7zip to delete the recovery.img in that folder, then move this new TWRP into that folder. Then flash that.
topdawg7793 said:
Been waiting for this for quite a while! I can put off learning to build for another few months!
For gapps, I recommend TKRuzze's Gapps. (Just search for them on Google.) His Pico-Gapps package is pretty lightweight.
UPDATE: Couldn't flash with the provided recovery. I was able to flash it successfully using TWRP 2.8.4.0 though.
Click to expand...
Click to collapse
Hi,
Can you provide /tmp/recovery.log for those who can't flash with that provided recovery?
Chris
Installed with latest TWRP. ROM working fine, no random reboots. Have some troubles with SDcard: unmounting ok, formating, mounting, detecting not working.
Update:
All ok after i format 10+11 partitions.
chrmhoffmann said:
Hi,
Can you provide /tmp/recovery.log for those who can't flash with that provided recovery?
Chris
Click to expand...
Click to collapse
Too busy to play with my Nook this week. I recall it was having issues with signature verification. I wasn't able to locate a way to disable signature verification.
Pepe.II said:
Installed with latest TWRP. ROM working fine, no random reboots. Have some troubles with SDcard: unmounting ok, formating, mounting, detecting not working.
Click to expand...
Click to collapse
Same issue here ... used TWRP ... everything seems to work except I don't have an SD card ... which is a deal breaker for this tablet.
UPDATE: Used the wrong GAPPS the first time ... working fine now ... sluggish, but nothing seems to be broken ... and I didn't do a factory reset ... just cache/davlik cache clear then flash
Get ready for Bexus-L
Kickass! Thank you to every dev who made it possible for Android L to be on NT!
Question: is it absolutely mandatory to install Google's crapware Gapps? I use F-Droid on all my other Android devices. They run much lighter.
---------- Post added at 10:47 PM ---------- Previous post was at 10:23 PM ----------
Edit: It works without Gapps. Also, bug found: if you enable development settings, when you tap on developer options, it says "Unfortunately, Settings has stopped"
Edit2: Kodi (XBMC) for Android does not work. Says "Cannot parse CPU features." Didn't happen on CM11.
Tell me more about this F-Droid ... what does it gain me over GAPPs? Performance?
sagirfahmid3 said:
Kickass! Thank you to every dev who made it possible for Android L to be on NT!
Question: is it absolutely mandatory to install Google's crapware Gapps? I use F-Droid on all my other Android devices. They run much lighter.
---------- Post added at 10:47 PM ---------- Previous post was at 10:23 PM ----------
Edit: It works without Gapps. Also, bug found: if you enable development settings, when you tap on developer options, it says "Unfortunately, Settings has stopped"
Edit2: Kodi (XBMC) for Android does not work. Says "Cannot parse CPU features." Didn't happen on CM11.
Click to expand...
Click to collapse
jerrygarcia4295 said:
Tell me more about this F-Droid ... what does it gain me over GAPPs? Performance?
Click to expand...
Click to collapse
Google's apps come with Google's playstore, sync services, etc, which add overhead to wi-fi and CPU cycles.
F-droid doesn't have those services. It's pretty much like a Linux package manager--you use it to install and keep track of open source packages.
Besides, I only use my phones and tablets for Kodi and phone calls. I'm not into Google Hangouts or YouTube, etc. I don't take pictures, I don't use the GPS...
IMO, I find Android to be completely useless. I wish there was a completely open source and open hardware Linux running phone. With Linux, you can do whatever you want.
I had to go back to CM11 ... superuser appears to be broken when I go to CM12 ... is there a fix for this?
jerrygarcia4295 said:
I had to go back to CM11 ... superuser appears to be broken when I go to CM12 ... is there a fix for this?
Click to expand...
Click to collapse
I haven't installed cm12 on my nook tablet yet, but on other cm12 installs, you have to enable superuser in Settings / Developer options / Root access. Click one of the boxes other than the default "Disabled". If that doesn't work, some folks swear by SuperSU, which you can find in the Play Store
Use https://github.com/yoinx/kernel_adiutor/raw/master/download/app/app-release.apk Warning, you _must_ debloat this rom
Download Rom https://mega.nz/#!QZAHHYzb!lfpF2c_gl5Cfrg93S2Dy6KTIzbnwF7Wb_85LFkzz76s
flash this kernel and reboot recovery before installing rom https://github.com/lgrootnoob/andro...a6d28b7b324d9e4ace9239dbcb5f9d9cd0c7/boot.img
then after installing rom flash the kernel again. its far more updated than whats in the rom zip.
Gapps for the brave(probably still doesnt work) https://www.androidfilehost.com/?w=profile&uid=23060877490004802
Hacks for building, and features included:
ubertc 5.4 and justarchi O3 on the rom, ubertc 6.1.1 and Ofast on the kernel. f2fs is recommended and supported on data and cache
This patch is applied http://review.cyanogenmod.org/#/c/120824/2/build/Android.common_build.mk
https://android-review.googlesource.com/#/c/148147/
http://forum.xda-developers.com/showpost.php?p=67211122&postcount=7
my trees are required for building
Ophidian_DarkCore said:
Use opengapps pico.
Should probably remove some of the crap gapps installs also.
Let me know if this flashes from cm11 recovery, and/or omni 5.1 recovery.
Use https://github.com/yoinx/kernel_adiutor/raw/master/download/app/app-release.apk for control of kernel. set cpu min to 200mhz, max 1400mhz, disable animations and all the live display and ambient display crap. then it should run smooth.
Use this supersu https://mega.nz/#!H5AEyI6Z!2FFd91__n2JVJSh-RidwpkMmYj5bfuQhHHLiEGr2LK4
Download Rom
Experimental Release 6(Skipped releasing small internally tested builds that had few changes. This build has a new kernel with CMA and the rom has justarchi optimizations and ubertc 5.3): https://mega.nz/#!9RpHDDiL!3r0A7ox2Vv864mB7SrRqUSFaKIWoEdjpUUbFnVg27yI
Stable Release 3(Latest Omni r43): https://mega.nz/#!xRoFxYbb!mXTzPPfqErND5pOe_B2XC0cEcKKQ4F4YJVWb_oMNhZQ
Release 2(device tree updates): https://mega.nz/#!ANYRnSbL!jAtYHkOpc1Jg_ULyl4TCVFBZ45lxzSx-7WKWeTYX8GM
Initial Release: https://mega.nz/#!xcg0nZzZ!_zTmgEC4SR4fsPAAAmlcphp72T44lGgBPjgLgXGLrD8
cache and system on ext4, data on f2fs. f2fs is buggy for cache.
mount system in twrp before flashing
thanks to everyone that was thanked in the omni 5.1 thread. source is on xc racer's github.
Hacks:
The zip is debloated.
This patch is applied http://review.cyanogenmod.org/#/c/120824/2/build/Android.common_build.mk
My fascinatemtd and aries-common trees need to be used.
We have a special updater_script
The experimental release has another commit not from the trees on my github: https://android-review.googlesource.com/#/c/148147/
With poweramp 703 alpha this is just a music player rom for my device.
Click to expand...
Click to collapse
Wow. Kudos to @Ophidian_DarkCore for doing a marshmallow build for the venerable old Fascinate! How's it work?
I've got a couple old fascinates in desk docks acting as clocks (cm10.1 with clock daydream most of the time). Wi-Fi access needs to work for a Chromecast remote function now and then.
Sent from my One using XDA-Developers mobile app
bmeek said:
Wow. Kudos to @Ophidian_DarkCore for doing a marshmallow build for the venerable old Fascinate! How's it work?
I've got a couple old fascinates in desk docks acting as clocks (cm10.1 with clock daydream most of the time). Wi-Fi access needs to work for a Chromecast remote function now and then.
Sent from my One using XDA-Developers mobile app
Click to expand...
Click to collapse
wifi works fine on this rom. there is a gapps bug that i cant figure out, all the sudden all of the builds crash setup wizard, and now i cant even get my partitions to setup properly. i think it has to do with something i did when i was reflashing my devices from stock to mm again to test everything out before final release. i just have no clue. but it works great for wifi just install everything without gapps i guess. i really need someone to test this tbh
Ophidian_DarkCore said:
wifi works fine on this rom. there is a gapps bug that i cant figure out, all the sudden all of the builds crash setup wizard, and now i cant even get my partitions to setup properly. i think it has to do with something i did when i was reflashing my devices from stock to mm again to test everything out before final release. i just have no clue. but it works great for wifi just install everything without gapps i guess. i really need someone to test this tbh
Click to expand...
Click to collapse
Like I said, I'm running cm10.1 on the fascinate, do you attempt to change the partition arrangement from what cm uses?
Sent from my One using XDA-Developers mobile app
Ophidian_DarkCore said:
wifi works fine on this rom. there is a gapps bug that i cant figure out, all the sudden all of the builds crash setup wizard, and now i cant even get my partitions to setup properly. i think it has to do with something i did when i was reflashing my devices from stock to mm again to test everything out before final release. i just have no clue. but it works great for wifi just install everything without gapps i guess. i really need someone to test this tbh
Click to expand...
Click to collapse
OK... I just downloaded your experimental ROM and pico gapps. Turns out my Fascinate still has CWM 6.0.3.3 recovery. I'm doing a backup of my cm10.1 and then we will see if your ROM will install...
OK. "some symlinks failed". Guess I need a new recovery. I'm out of date on this old device. What's my best choice of recovery?
Sent from my One using XDA-Developers mobile app
bmeek said:
OK... I just downloaded your experimental ROM and pico gapps. Turns out my Fascinate still has CWM 6.0.3.3 recovery. I'm doing a backup of my cm10.1 and then we will see if your ROM will install...
OK. "some symlinks failed". Guess I need a new recovery. I'm out of date on this old device. What's my best choice of recovery?
Sent from my One using XDA-Developers mobile app
Click to expand...
Click to collapse
zimage in odin from the omnirom 5.1 thread. its the same mtd over bml lvm bs from cm11. but something is wrong with it. like ot was causing the zip not to flash or the partitions would become unmountable. i diffed the scripts and i dont see a difference.. so i removed the script from my zips. no big deal. gapps is what i need tested after you confirm the rom works.
@bmeek here is a full unmodified zip. still ubertc 5.3 with justarchi stuff, has cma kernel, and opticharged. the latest device tree code is used. i cant get gapps to work. they just crash. when the zip install fails, reboot to recovery and install again. then it works https://mega.nz/#!QZAHHYzb!lfpF2c_gl5Cfrg93S2Dy6KTIzbnwF7Wb_85LFkzz76s
its hella fast for me, but i have kernel adiutor stuff changed. like laptop fs mode, less entropy generation, 200-1400mhz, no animations etc. and lots of bloat removed
bmeek said:
Like I said, I'm running cm10.1 on the fascinate, do you attempt to change the partition arrangement from what cm uses?
Sent from my One using XDA-Developers mobile app
Click to expand...
Click to collapse
I run CM10.1 too! With devil Kernel. Max clock set to 1200MHz.
Home button, recent apps button do not work, clicking "more" in settings crashes it, quick settings do not work, notifications do not work. in the R3 build.
Can't get the R6 build to install, "Operation not supported on transport endpoint.".
Erase system partition before you flash this, Or you will have problems! btw, the zip will not install from cm10.1 cwm recovery, I had to flash Omni 5.1.1, reboot recovery, then flash this 6.0.1 build. I am on R6 now.
Finally got the R6 to install lastnight. in fact, I am writing on it write now in chrome (36). chrome is the only browser that works.
cool, use the latest link a couple posts up, and whoever needs gapps, this is the proper link.(xc-racer99 linked it said it was officially supported by omni https://www.androidfilehost.com/?w=profile&uid=23060877490004802 ) i cant be arsed to even edit the op with no one looking. you gotta do your own debloating when installing the full unmodified build(the latest one)
pcwizzy37 said:
Finally got the R6 to install lastnight. in fact, I am writing on it write now in chrome (36). chrome is the only browser that works.
Click to expand...
Click to collapse
webview is probably broken in the rom
kernel update: wayy more updated f2fs, exfat in kernel for exfat of course and also for vfat, which means more stability and recent code. sync with xc-racer99 sources for more cma etc... updates and a radix-tree backport from the 3.4 kernel. thanks arter97, dorimanx, xc and cwof
sauce removed, use link in op for the new boot.img
Ophidian_DarkCore said:
kernel update: wayy more updated f2fs, exfat in kernel for exfat of course and also for vfat, which means more stability and recent code. sync with xc-racer99 sources for more cma etc... updates and a radix-tree backport from the 3.4 kernel. thanks arter97, dorimanx, xc and cwof
sauce https://mega.nz/#!4YwASYhT!X91E-f0i7KOGBYvMjxF1NT4qLSujqYYg6G8s9vnZHVQ
6/13/16 11:06pm: these optimizations are about to make the galaxys devices in all variants sky rocket performance wise
Click to expand...
Click to collapse
is this boot.img in the latest download (omni-6.0.1-20160521-fascinatemtd-HOMEMADE.zip)? My fascinate started getting in a reboot loop last week so I decided to wipe and try this.
---------- Post added at 08:40 PM ---------- Previous post was at 08:35 PM ----------
I wiped (all 3),
installed omni 6.0.1 20160521,
installed BaNkS_Dynamic_GApps
installed SuperSU
I cannot get past the got another device screen in wizard. I eventually get 'Google play services has stopped.' I will try again without GApps. What do you suggest I do?
mswells said:
is this boot.img in the latest download (omni-6.0.1-20160521-fascinatemtd-HOMEMADE.zip)? My fascinate started getting in a reboot loop last week so I decided to wipe and try this.
---------- Post added at 08:40 PM ---------- Previous post was at 08:35 PM ----------
I wiped (all 3),
installed omni 6.0.1 20160521,
installed BaNkS_Dynamic_GApps
installed SuperSU
I cannot get past the got another device screen in wizard. I eventually get 'Google play services has stopped.' I will try again without GApps. What do you suggest I do?
Click to expand...
Click to collapse
We have to bug @xc-racer99 trust me ive spent a couple hours trying to figure this one out, btw the op states to flash the boot.img after flashing the rom zip(which _is_ old). we also gotta do hella debloat because banks doesnt actually fit, it leaves an apk or two unwritten cause running out of space. if you can convince xc to figure this out I'll release a package solution, with the latest rom(reworked optimizations and synced with latest omni source yesterday) and gapps all debloated.
Ophidian_DarkCore said:
We have to bug @xc-racer99 trust me ive spent a couple hours trying to figure this one out, btw the op states to flash the boot.img after flashing the rom zip(which _is_ old). we also gotta do hella debloat because banks doesnt actually fit, it leaves an apk or two unwritten cause running out of space. if you can convince xc to figure this out I'll release a package solution, with the latest rom(reworked optimizations and synced with latest omni source yesterday) and gapps all debloated.
Click to expand...
Click to collapse
I have no idea why you guys are having such problems on the Fascinate: with a freshly synced Omni source, freshly downloaded OpenGapps pico, I had no issues getting through the Setup Wizard (I did skip setting up a Google Account) on my Galaxy S 4G - although it was understandably laggy. The default Browser also works just fine afterwards.
Perhaps the gapps package provided removes some essential file/doesn't overwrite properly?
xc-racer99 said:
I have no idea why you guys are having such problems on the Fascinate: with a freshly synced Omni source, freshly downloaded OpenGapps pico, I had no issues getting through the Setup Wizard (I did skip setting up a Google Account) on my Galaxy S 4G - although it was understandably laggy. The default Browser also works just fine afterwards.
Perhaps the gapps package provided removes some essential file/doesn't overwrite properly?
Click to expand...
Click to collapse
i have it written completely and setup wizard blatantly stops right after boot. Then sometimes setup wizard will work and then google play services will crash incessantly. I think this was the case with the 5.1 builds too. I get issues with "you have tried to change the api from what has been previously released in" while building and i have to manually remove 4 lines from the output folder's api txt file. but i was convinced thats just a part of using lunch instead of brunch. i also jacked around with the fingerprint for no real sane reason but reverted it in my local trees. the latest build is dex preopted but the first builds(generic no changes) arent and they still have this issue
wait, could it be that we dont init gps and ril? https://github.com/lgrootnoob/andro...mmit/9f67333ee281c1b7fcc5c2ae04eb899a14b4b1ee https://github.com/lgrootnoob/andro...mmit/5d8effadf263a8a22809f3d3751245351c2c11eb
im basically at your mercy here. whatever you say to do, ill be ready to build and try it