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?
Related
Special thanks to the creator of the item inexus from which inspired me to give a graphic touch to the rom.
This rom (not a mod) has been developed entirely from the source of Google and very little of Cyanogen framework.
Thanks to Cyanogen and all his staff for the contributions received.
Is installed from the recovery, as always, do not worry if it takes a while to leave the first splash is entirely normal and configuration files running on first boot.
I strongly recommend formatting SDCARD total with three partitions, SDCARD 7.4 GB / EXT3 512MB / LinuxSwap 64MB, you can do from the recovery, but remember to keep you before your pictures and music. This is because directories are created in the sdcard called Android which are recorded in the data I have found to negatively affect the rom. PROVEN!,
This is only necessary in case you want to have Apps2sd or Linux Swap, if not going to do any of those things is not necessary to format the Sdcard with three partitions.
WARNING!
Only if you come from different roms (Donut, Eclair, Froyo) is necessary to WIPE, when coding in Gingerbread from this rom will not need to wipe again to install later roms.
This rom installs itself alone, that is completely reconfigures.
Before installing the rom Wipe recommend because it has many changes. When installed and out of recovery by restarting leave untouched while the LED flashes. At this point I recommend you salteis the account settings to skip giving google and once in the launcher and set podreis rom to your liking. This is because otherwise the phone will Autoconnect the market and begin to automatically download all the applications you had installed and it saturates the terminal because it does hit, besides putting the background image that you had prior to the rom and then you ask me that as it is possible that if I install the rom to wipe the bottom appears to me that I had before. In this way you will do a clean install. Then you enter the market and instalais a free application to refresh anyone that you have installed in the terminal.
Very attentive to you to do restorations of any kind against the rom or program that you can have problems. (I mean backups, including their own SupSetup least in the section on applications), special attention to restore configuration data of any kind. Under the best not to doubt.
SupSetup new V16 in all roms, not serve any previous SupSetup for this rom
The new integrated SupSetup activation brings on-demand applications in the applications section extras, you can enable applications that interest you as the Roma comes in "Lite" (without extra applications installed) so that everyone can choose the best configuration.
It is important before you set up Google account to be activated from applications before SupSetup so that when you connect to the servers to configure your Google account, they enter the downloads section.
After entering the market and to display applications install any application downloads for cool downloads.
Apps2sd
Apps2sd is to pass the phone applications both current and future to the ext3 partition, it is imperative not to activate any way to move application to the sd or change from internal to external location application. Simply activate it from the SupSetup without touching any configuration in the Spare Parts or applications from the rom settings.
Apps2sd not activate without at least once you have restarted
General
- Rom in "LITE"
- New graphical look different from SuperGinger's
- All you had the SuperGinger but since source of non-Cyano Google
Added
- Wake & Unlock
- Always visible Bluetooth Settings (tolemaC)
- Hide clock
- Percentage of battery
- It's part of Cyanogen CyanogenModsettings
- Etc ...
A rom much lighter than any other that you were able to prove, you could say that is the Nexus CSDI One (this rom Magic gave a lot to talk), completely stable and trouble-free calls or anything known, at least tests we are doing we have not yet found any fault.
Applications
- You can install more from the extra applications SupSetup
- Google Apps
- Flash Player 10.1
Download:
http://cdn.movilzona.es/repos/superatmel/ROMS/SuperAosp/[email protected]
Changelog:
SuperAosp 2.8.4
- unwonked End calls wonk
- Kernel with HAVS
- incognito mode in browser
- User agent in browser
- Fix wifi suspend
- more stable more battery life
- Very fast
- Recomended Adw Launcher EX in mode new vertical for drawer
SuperAosp 2.6
- New intent for fix black calls & sound
- Add ADWLauncher
- New kernel HAVS
SuperAosp 2.2
- Upgrade to version 2.3.3
- Fixed black calls (supposedly) I have no problems with AMOLED
Captures
Reservated
Looks good. Will be sure to give it a go now. If you want i could also make a video of the rom in action? here is the post. http://forum.xda-developers.com/showthread.php?t=966530 If you want me to i will make a video and put it up for you.
wow thanks been waiting for this.
This looks great! Can't wait to try it on my gf's N1
You are like a Dev God. Thanks.
hey guys here's a preview of this rom http://www.youtube.com/watch?v=RK_lmre2eh0
Stuart.upton666 said:
hey guys here's a preview of this rom http://www.youtube.com/watch?v=RK_lmre2eh0
Click to expand...
Click to collapse
Thanks for the video
I have been running super-ginger and it is an fantastic rom overall. I can't wait to try this new one. Hopefully, the dev will have a 2.3.3 ver once it is out in the wild. Awesome job.
What happened to theme Chooser? WILL It work with this rom?
Sent from my Nexus One using XDA App
robotnoize said:
What happened to theme Chooser? WILL It work with this rom?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Do you mean the theme chooser that's been added specifically to CM and not part of AOSP?
Oops In the version he made before this 2.6.8 he had it so I figured he would keep it. Never mind
Sent from my Nexus One using XDA App
I seem to be having issues with the A2SD. Apps such as Angry Birds won't install, and also, sometimes after rebooting, none of my apps are there.
Anybody else?
Any idea about battery life? Can i flash Wildmonk or IR kernel along with this rom?
chrisvuong said:
Any idea about battery life? Can i flash Wildmonk or IR kernel along with this rom?
Click to expand...
Click to collapse
Im pretty sure you can but it will probably not function the same since super customized the kernel for his rom
N1
is this a spanish rom? any english version? at least on that capture picture its spanish.
dnsmo said:
is this a spanish rom? any english version? at least on that capture picture its spanish.
Click to expand...
Click to collapse
It has option for English, only some supsetup is in Spanish
N1
djmasque said:
I seem to be having issues with the A2SD. Apps such as Angry Birds won't install, and also, sometimes after rebooting, none of my apps are there.
Anybody else?
Click to expand...
Click to collapse
What is problem with Apps2sd?
Installed this rom and have been using it for about an hour an I'm loving it so far! Excellent job. Seems I have found a new daily rom
Sent from my Nexus One using XDA App
superatmel said:
What is problem with Apps2sd?
Click to expand...
Click to collapse
Some apps won't install- Angry Birds, Aldiko eBook Reader. Then sometimes after a reboot, there are no apps installed at all, until I reboot again
CyanogenMod 7 (w/ Gingerbread 2.3.7) for 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: http://download.cyanogenmod.com/?device=galaxys2 (for when nightlies are working normally)
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)?
Only for the International version of the Galaxy S2, US versions like the AT&T have their own device specific builds.
Note: sometimes you need to flash twice back to back without a reboot in the middle. The install should take a little time, if it happens very quickly, flash again.
Install via ClockworkMod (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 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 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 ROM Manager or 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 modes don't work
- TVout, MHL
- FMRadio
- Issues when using the 2G/3G-Switch
- Volume issues (some report too high, others too low)
Q: Where do I see the Changelogs?
A: http://cm-nightlies.appspot.com/?device=galaxys2 - 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: 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 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: 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 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: My Notification 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: 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: 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.
Hi !
Why we don't see Cyanogen Builds in ROM Manager Premium ?
Thanks & sorry for my bad English.
Nice Q&A here. This is a MUST READ before flashing CM7
Q: Why do I not see the nightlies in ROM Manager?
A: Nightly builds are only visible in the premium version of ROM Manager.
Click to expand...
Click to collapse
I have premium rom manager but dont see any cm7 roms in the download section
???
darkevangerion said:
Hi !
Why we don't see Cyanogen Builds in ROM Manager Premium ?
Thanks & sorry for my bad English.
Click to expand...
Click to collapse
They will be there when the CyanogenMod buildbot successfully builds a nightly - hopefully tonight.
Thanks for your fast answer.
And thanks for the rom, obviously
EDIT : Hmmm... "Tonight" = "Tomorrow" for European. :/
They will be there when the CyanogenMod buildbot successfully builds a nightly - hopefully tonight.
Click to expand...
Click to collapse
Thanks.
Why can't i register my device for notification on updates from nightly?
I got rom manager premium
Sent from my GT-I9100 using XDA Premium App
Answered 3 posts above.
Firstly, I love the first release of CM for the S2....very quick.
I have successfully replaced the samsung apps I liked, and i have gapps installed. One question is, now when I go into the market on my PC it says I have no Android devices to send the apps too.
On the S2, the market is fine.
any ideas?
I can see in Rom managet premium only cognition and darks rom. Is it normal? Anyone else witht the same stats?
carda21 said:
Firstly, I love the first release of CM for the S2....very quick.
I have successfully replaced the samsung apps I liked, and i have gapps installed. One question is, now when I go into the market on my PC it says I have no Android devices to send the apps too.
On the S2, the market is fine.
any ideas?
Click to expand...
Click to collapse
It's strange, it's work fine for me.
Hunteres said:
I can see in Rom managet premium only cognition and darks rom. Is it normal? Anyone else witht the same stats?
Click to expand...
Click to collapse
Take a look at the #5 post
No official nightly build has been built yet by the build bot......thats the automated rombuilder witch is used to build the roms.....so if no rom is built no rom in rom manager ......
Sent from my GT-I9100 using Tapatalk
i have just tryed installing an app via the market website to my mobile and its working fine for me....
Hello,
Is there any way I can increase vibration intensity? It is fine when I reboot it but after a minute the vibration becomes very weak to the point where I can barely feel it. (When typing and pressing "menu" or "back button" etc
Sent from my GT-I9100 using XDA App
It's a known issue of this ROM.
There is nothing to do for this time.
Cyanogen #1 !
Issue gonna be FIX, by next build's
i just have one question, someone said they used kg1 modem does that actually stay or would cm7 just overwrite it anyway?
since im too noob to post in development section i want to thank you all at teamhacksung for this
Also...why was the stock camera app replaced with one that is worse? (Camcorder is worse.) Its a great rom. But can someone explain this to me?
Sent from my GT-I9100 using XDA App
Q&A: [ROM-1.2/GRJ90] CM7Tab for the GTab (based on CM7 Nightlies) [Update: 08-15-11]
MOD EDIT: THIS IS THE Q&A SECTION FOR [ROM - 1.2] CyanogenMod 7 nightlies for the GTab
ALL Q&A FOR THIS ROM HAPPENS HERE.
Thanks.
---------------------------------------------------
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.43 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
1) latest version of CM7Tab: CM7Tab build 08082011 (Nightlies changelog)
2) Test CM7Tab with 4950 drivers: Test Build 08152011
Changes in modified version
1- replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2- vold.fstab is setup as sdcard for internal storage & emmc for external card
3- using pershoot's 2.6.32.43 GB kernel for 1.2 bootloader (For more info, check his blog.
4- Read_ahead_kd increased from 128 to 2048.
5- Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6- Replaced Camera libs & apk to stop the 8-bit pixelling.
7- Increased dalvik.vm.heapsize to 64m (07102011)
8- Set some values to improve video playback (07272011)
9- Changed values for lowmemorykiller minfree in init.rc (08072011).
10- changed EMMC to microsd (08072011)
11- updated ROM up to 2.3.5 (08072011)
12- Camera fix (08082011)
To-do list:
1- remove some apks (such as Rom manager) & create a removed apks folder.
--------------------------------
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified): Latest build: Build 07262011 (Changelog)
If you have suggestions/ideas, do not hesitate to share them.
thank you.
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
nelomen said:
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
Click to expand...
Click to collapse
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Icewyng said:
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.42 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified):
Latest build: Nightly build 07112011 (Changelog)
2) Modified version of the ROM: CM7Tab build 07102011
Changes in modified version
1) replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2) vold.fstab is setup as sdcard for internal storage & emmc for external card
3) using pershoot's 2.6.32.42 GB kernel for 1.2 bootloader (For more info, check his blog.
4) Read_ahead_kd increased from 128 to 512.
5) Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6) Replaced Camera libs & apk to stop the 8-bit pixelling.
7) Changed values for lowmemorykiller (07102011).
8- Increased dalvik.vm.heapsize to 64m (07102011)
RC1 version of the rom with changes: 7.1.0 RC1 with Pershoot 42 kernel
(Sorry if this is short but I will improve the thread as it goes)
To-do list:
1) remove some apks (such as Rom manager) & create a removed apks folder.
2) change the EMMC to Sdcard2
If you have suggestions/ideas, do not hesitate to share them.
Click to expand...
Click to collapse
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Icewyng said:
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Click to expand...
Click to collapse
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Edit: have been trying for a couple of hours now but sent me in to boot loop had nvflash back to stock, will give it another shot once this silly Tap n Tap is finished loading.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
rob_z11 said:
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Click to expand...
Click to collapse
Dalingrin was kind enough to provide a fix that seems to resolve most of the problems with market (including buying apps). It was merged in build 07092011+ so give it a try and tell me how it goes.
nelomen said:
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Click to expand...
Click to collapse
The FCs you were getting were probbly from DSPManager. It is a known issue that seems to come from a "broken pipe" in one of the libs. For now, it is best just to remove it.
For the bootup, someone suggested moving apps to the SD card. Apparently, it would speed up the process.
I am conscious that 2.3.4 is made with phones in mind but it is a step up from Froyo and having partial hardware acceleration helps.
Just tried again and got stuck on CM7 logo boot loop, this was with the CM7 tab build. did full wipe of cache, dalvik, and user data. Not sure what happened. Restoring to Illuminate rom if you have some ideas on how or what else I can do to try this rom let me know.
Hey there Ice.
First off, awesome work on this and thank you for taking the time.
I would recommend editing the build.prop file to set the Manufacturer to HTC. This fixes the playback issue with Netflix (Chipmunk). I tested this out fully on my gTab last night and it's the ONLY setting that needs to be modified. Aside from that, everything seems to work.
Good work!
Hi
Has anyone tried installing volume+ on this rom? I'm on BL1.1 CM7 rom but volume+ does not install. If this works, I'll take the bold step to upgrade to BL1.2.
I don't know if it's just my hardware. My gtab's speaker is very soft and I want to try cranking it up with volume+ (which works on my phone running cm7).
thanks a lot.
DroidTV phone size not full screen....Anyone have other apps that did that after....
I was using DroidTV, and it was full-screen and then rebuild my G Tab with the cm7tabl-0710200-1.2 and when I reinstalled DroidTV it is now phone size display on the G Tablet.
I used Titanium Backup to restore the app and the settings. Anyone have issues like this with an app that did that after re-installing after a full rebuild? Any build.prop setting or somewhere I could check?
Thanks. Steve.
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Icewyng said:
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Click to expand...
Click to collapse
Thanks Ice. Other than that I have yet to find any major issues that in the build.
Other than apps that open portrait only with the bottom on the side with the power button. Tried to say to not rotate 90 degrees but they still open that way Apps that open landscape then won't rotate to the 90 degree position but portrait apps still open that way
This is the most stable I have used and performance seems good. A co-workers has the same build, I installed it for them since they are techie-challenged, and theirs is turtle slow because I think they have Skype running all the time.
Icewyng said:
Thanks everyone for your feedback.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
Click to expand...
Click to collapse
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
vhendsume said:
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
Click to expand...
Click to collapse
Actually, I think it has more to do with a problem with one of the audio libraries. I did a logcat and it seems something called AudioFlinger can't set a parameter properly.
If anyone can fix this, I can send the logcat to help out.
I wanted to apologize for not being able to upload the new nightly today. I had to rebuild my computer and took the opportunity to switch to a new Linux distro. Just tested the new system and all is great.
I will post Build 07172011 later this morning.
Where are the nightly's getting posted now? Thanks and this is the most stable MOD I've had on my G Tab.
Do video apps work as far as no rotation with Oovoo, yahoo, reelportal, etc? Audio work okay with chatting?
mirrors:
http://dev-host.org/cops0ujuwmm0/update-cm-7.1.0-smb_a1002-07182011-1.2.zip
http://dev-host.org/8xjvaysomd1i/update-cm7tab-07102011-1.2.zip.zip
-deck
*** CM9 nightlies have been discontinued.. see: http://forum.xda-developers.com/showthread.php?p=29135522#post29135522 ***
For those who have dabbled in the Nook Color or HP TouchPad scenes you may have seen unofficial CM9 nightlies from me.. so in the same fashion here are the Nook Tablet builds - these should be considered in Alpha status.
***The nightly builds are currently for the 1GB "Acclaim" Nook Tablets ONLY***
I take no credit for the work put in to get nook tablet CM9 running - all the credit there goes to chrmhoffmann, fattire, nemith and countless others I may not even know. Please be sure to thank them for their efforts. I'm just building ROMs from their source code.
I *strongly* recommend everyone look over fattire's guide for building and giving it a try to learn a little about how this all works, it's how I got started on the nook color with these unofficial builds. After clearing with fattire and chrmhoffmann I decided to provide these builds for people who don't have the hardware/ability to build themselves.
These builds are all straight sync with CM source along with the nook tablet device and kernel trees. They are *NOT* tested releases (I don't even have a Nook Tablet) so please be aware that the builds could be broken at any time, and are provided as-is. Please be comfortable with adb and/or using recovery to wipe/restore/nuke at any time.
Builds are sync'd at 9am UTC - they will be available to download approx 15 mins after that.
There is no official "changelog" for nightlies, you can reference the commits in the device tree, kernel tree and main CM gerrit. Note that the CM gerrit shows things that are merged for ALL official devices, not all of these will apply to the Nook Tablet, however, anything not referenced by a device name is also included in these builds.
The only addition I have made to these builds is the inclusion of "Goo Manager" as a system app. More on the reasons for this below...
Downloads
There are a few ways to get the builds:
1) Browse the hosted folder here: http://techerrata.com/browse/nightly_kangs/acclaim
2) Follow @CM_Acclaim on twitter for announcements of the builds as they hit the host (PLEASE NOTE: @CM_Acclaim IS A TWITTER BOT - don't bother tweeting at it)
3) Use the Goo Manager app to receive notifications of new builds and download them directly on your device.
Latest ICS gapps can be found here http://goo-inside.me/gapps or mirrored here http://techerrata.com/browse/gapps
Goo Manager - Notable features
1) Notification of new builds and gapps updates with one click - or auto-check frequency in settings. Goo Manager auto-checks the md5 for every download.
2) Automated flashing of downloaded roms/gapps/other files with TWRP
3) Install TWRP 2.1 with one click (menu - install openscript recovery) - TWRP is still experimental and will overwrite ClockworkMod on emmc.
4) *Incremental updates* (experimental) - if you like to stay on the bleeding edge and flash every night. Incremental updates are diff'd server side so you only download the changed files from the build the night before. These downloads average 30-40mb in size (vs ~120mb for the full rom), so you get faster downloads, updates and less wear on your device's flash memory. Incremental updates ONLY work from the previous night's build to the latest. When you check for updates in Goo Manager it will offer you an incremental if applicable.
Updates
For the latest updates/announcements follow me on twitter, or check back here.
Credit and Thanks
Thanks to chrmhoffmann, fattire, nemith and the rest of the CM acclaim team for making this possible. Thanks to fellow TeamWin members Kevank for providing the hosting and to s0up for the Goo Manager app.
Neat.
This should make things easier.
Again though-- until some changes are added to the 3.0 kernel, if you have a newer 512MB NookTablet, the nightlies won't work and you'll probably come up with a blackscreen and have to reflash. Chrmhoffman's latest 2.6.35 build though should work if you have the newer model and/or want the 2.6.35 kernel w/cm9.
* EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL *
Warning: This will overwrite the internal storage with CM9. The instructions below assume you have a rooted NT running stock, CM7, or CM9.
Requirements
1GB NT (the 512MB NTs are not yet supported by the 3.0 kernel.)
Software: Rooted stock, CM7, or CM9
A full battery
a formatted SD card in the slot
wifi connection
(something else?)
To install the experimental CM9 w/3.0 kernel on a 1GB NT:
(steps are from memory and are to be refined soon)
Use the Google Play Market or other method to install Goo Manager to your device.
Run Goo Manager. Select the menu, and chose "install openscript recovery". Click through the options to confirm. At some point you may be asked to give Goo Manager superuser permissions.
The above steps should now cause TWRP2 recovery to be installed to your device. (You only need to do steps 1-3 again when you want to update or reinstall the TWRP2 recovery image.)
Now you can browse compatible roms for your device. Under /devs/eyballer/nightly_kangs/acclaim/ you should see some nightly builds. Choose the one you wish to install. Wait for it to download.
Once it's downloaded successfully, you should be able to select the newly downloaded rom from the notification menu, and then request that it be installed. Alternately, you can go to the Flash ROMS menu to flash previously downloaded ROMS.
See elsewhere in this thread for any other update.zips that you may wish to download and install. You can put more than one update.zip in the queue.
When you are ready, select the order and flash selected button on the bottom right.
It is sometimes preferable to wipe the cache/dalvik cache partition when doing an upgrade. You also have the option to automate a backup (not a bad idea). If you are coming from stock BN software or for any other reason wish to clear all user information, you may also wish to wipe the /data. partition. This is not generally recommended as wiping /data will delete your personal information.
When you're done configuring your flash, choose Flash, and then confirm.
If all goes well, there will be a reboot, your choice(s) will be flashed, and then the system will restart into the new CM9. If it doesn't work (very possible, as this is still experimental), post below and let the devs know what went wrong.
* EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL * EXPERIMENTAL *
This video has more information about TWRP2 and Goo Manager, although the device discussed is a HP Tablet. Some things like the boot menu will be different, but most other details will apply.
Good luck, and be sure NOT to do this with an 512MB Nook Tablet. If you screw up and do install it, you will need to re-flash a CM9 using 2.6.35.
fattire said:
This should make things easier.
Again though-- if you have a newer 512MB NookTablet, the nightlies won't work.
Click to expand...
Click to collapse
I'm assuming it's because it's using the newer kernel?
Hmmmm, so these will be sorta nice.....
Fattire, did you update the TWRP .zip to a non-totally-messed-up version?
If so I'll jump on these and try them.
Also are these builds the latest 0.04 for our tablet?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Keithn said:
I'm assuming it's because it's using the newer kernel?
Click to expand...
Click to collapse
Yes, the 3.0 kernel has issues with 512MB-- the kindle fire had the same issues, and if you read the latter few posts in the kernel thread, you can read more about it. Hashcode apparently knows how to fix it, but until then, don't install this on a 512MB NT.
SilentStormer said:
Hmmmm, so these will be sorta nice.....
Fattire, did you update the TWRP .zip to a non-totally-messed-up version?
If so I'll jump on these and try them.
Also are these builds the latest 0.04 for our tablet?
Click to expand...
Click to collapse
No guarantees. eyeballer is using the latest experimental one from the twrp thread. It has the fix from arcon and has been successfully used by frustro. I of course have not ever run it, so I can't make any claim of success.... this is all experimental.
The builds are nightly, so right now they're about at par with chrmhoffmann's alpha .04 (which of course uses 2.6.35 kernel), but if I'm not mistaken, eyeballer builds 'em fresh every day from the cm9 repos plus whatever changes are made to the kernel and acclaim-specific repositories. That means they can be total crap in the future, and who knows if twrp2 is even any good either...
This is seriously guinea pig territory. So unless and until you're willing to take some risks, you might want to hold out for what others have to say.
I can confirm that this worked for me.
1. Intall goomanager from play.google.com
2. from menu choose install openrecovery script, it downloaded and installed openrecovery-twrp-2.1.4-acclaim.img
3 browse compatible roms, navigate to /devs/eyballer/nightly_kangs/acclaim/ and choose the first one
4 menu home
5 choose download gapps packages and choose gapps-ics-20120429-signed.zip
I had 2 download failures and had to repeat these steps till the download was correctly completed and then main menu flash roms select the 2 zips and I was done
very nice and smooth.
Can you add tun.ko and cifs.ko to the kernel config please?
Thanks
Do we have to use twrp to install this rom?
meghd00t said:
Can you add tun.ko and cifs.ko to the kernel config please?
Thanks
Click to expand...
Click to collapse
You're requesting tun.ko and cifs.ko compiled as modules?
Used Goo Manager to flash TWRP, had to pull the SD card and install it for it to mount.
Downloaded the first 900 build (I see there is 2 for some reason)
Clean install including /system wipe
Have had 2 or 3 "sleeps of death"
Screen wouldn't turn on with N button or power button.
Had to hold power for 10+ seconds to do a hard shut down.
Cranked my screen off timer to 10 minutes.
Keep up the great work.
Also Netflix loads and has audio no video but I'm sure you're aware of that.
Two other things I've noticed.
Can confirm the SD card mounts every time so far but the SD card did randomly unmount once.
Lastly, when trying to download Atorrent (for watching Game of Thrones) I get an error saying "Can not install to USB mass storage or SD card"
Sent from my Galaxy Nexus
great share!
Fattitire and or Eyeballer I have a very humble request that I think might help us help you.
I have been using Goo Manager for a few weeks and love it. It's a great tool. If you could add just a line or even two words to the Change Log tab in GM like "bug fix" "nothing major" "hardware acceleration working " it would be very helpful for us to decide if we should flash an update or skip it and wait for the next one.
Once again thank you, and great work.
Sent from my Galaxy Nexus
Helltoupee said:
Fattitire and or Eyeballer I have a very humble request that I think might help us help you.
I have been using Goo Manager for a few weeks and love it. It's a great tool. If you could add just a line or even two words to the Change Log tab in GM like "bug fix" "nothing major" "hardware acceleration working " it would be very helpful for us to decide if we should flash an update or skip it and wait for the next one.
Once again thank you, and great work.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
While this seems simple to add, it's not. My build system for these unofficial nightlies is completely automated so adding something to changelog would require me to go through the commits and then manually log into goo.im and update the rom info for every build. I don't do that for the devices I own, let alone the ones I don't
I posted links in the OP to all the source that is used to compile so it's up to the user to read and see if they would like to update. Of course as more people start running the builds, the discussion here usually will give you hints as to what's added too.
Updated the OP with another download notification method. We have a twitter system that will send out a tweet for every new build that hits our server with the link to the download and a QR code. You can follow CM_Acclaim for this.
Thank you for the explanation. I completely understand.
Sent from my Galaxy Nexus
Nighty change log blog thing I found for all CM9 builds. Enjoy.
http://changelog.bbqdroid.org/
Sent from my Galaxy Nexus
Do these nightly builds have an embedded expiration date like the chrmhoffmann's Alpha 0.0x builds?
Also, has anyone tried getting one of these builds to run off an SD card using succulent's method (http://forum.xda-developers.com/showthread.php?t=1545766)?
I kinda have a problem :\ I have lines running across half of my screen and its kinda freaking me out.. I'm not pointing fingers but it did happen after I installed this ROM
---------- Post added at 10:58 PM ---------- Previous post was at 10:52 PM ----------
My problem is solved... Oddly enough installing another rom makes the lines go away. I'm sorry for posting for no reason. lol have a great day
The 3.0 kernel still has problems. Hopefully these will be fixed in a later build.
digixmax said:
Do these nightly builds have an embedded expiration date like the chrmhoffmann's Alpha 0.0x builds?
Also, has anyone tried getting one of these builds to run off an SD card using succulent's method (http://forum.xda-developers.com/showthread.php?t=1545766)?
Click to expand...
Click to collapse
Don't try it. My modifications are for kernel 2.6.x version of CM9 not 3.0.x CM9.
I've build a bootable 3.0.x CM9 on sdcard. I wouldn't recommend this build yet due to LCD brightness and no sleep issue. LCD brightness will take 50% of the battery. This build is mainly testing.
I loaded recovery. Downloaded CM9 ics then gapps. When I go to flash roms nook reboots then I get the cynaboot image then nook boots back to cm7. What am I doing wrong?
The problem I was having is that cm7 did not mount my SD card on reboot. Had to load eyeballers first build through cwm. Then once in cm9 I could load through twrp. Running good so far.
Want to update to CM13? Read this first!
Welcome to my upgrade guide that will allow users to painlessly upgrade from an earlier version of android to CM13.
Background info:
Our Cyanogenmod maintainer, Lysergic Acid, started bring alpha builds of Cyanogenmod 13 since October of last year. Now, we have official nightlies on our device which just proves how strong of a device we have and how strong we are as a community on XDA. With all of the exciting new features Marshmallow brings to the table, people have been flashing CM13 without reading any precautions or information about the possible consequences of not doing a particular step or procedure. With this guide, you will learn how to successfully flash CM13 on a device, everytime!
This guide will assume you are on a rooted custom ROM with a working custom recovery. It will not guide users how to update from stock ROM to CM13. If you haven't rooted your phone yet or are on stock ROM, use a different guide to install a rooted custom ROM (KK or LP preferred) then follow this guide.
Another important tip is to read the issues post before flashing the latest build of CM13. There could be issues that you could encounter so make sure to read before flashing!
How to install:
CM13 is available to install for CM12.1 users via the OTA updater. However, updating to CM13 via OTA updater is buggy and will remove gapps and Isorec Recovery. If you receive notifications about the CM13 update, don't use the OTA updater! Use this guide below instead.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the upgrade process or you don't like CM13 in general. If you are using Cyanogen recovery from CM12.1, you should flash a isorec recovery from this thread. TWRP or CWM are both fine. Note: If you are using a build earlier than 20160119 nightly or not using one of Lanchon's isorec kernels, you will not be able to use a isorec recovery. This will not apply to people on older versions of android (for older versions of android, KK compatible recovery or higher is all you need).
If you require to use Gapps, make sure to re-partition your phone now if you haven't done so! This can be done by following one of the guides linked in the Gapps section. It is required for users to re-partition their system partition to 1GB to prevent issues when flashing gapps. Please also note that when upgrading from an older ROM, you must flash a newer Gapps to keep Gapps on your phone.
Download CM13 from the official cyanogenmod downloads page onto your phone. Update: The Cyanogenmod downloads page is gone, instead download from here.
If you are in CWM, while on the main menu, choose factory reset. Then go into mounts and storage and select format system. If you are in TWRP, go into the wipe menu, select advanced wipe, check wipe system, data and cache, then swipe the bar to wipe.
Flash the CM13 zip.
(Optional)Install Gapps (if you've re-partitioned already, if you didn't, you will get errors!).
(Highly recommended)If you don't have isorec recovery already installed, you should flash an isorec recovery here: Thread link
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken.
I will repeat what I said earlier but with more explanation. Why don't I have a guide on how to update to CM13 via OTA? OTA update from CM12.1 to CM13 is broken! You will lose gapps and it will cause a lot of problems to user. Just follow the above guide to flash update manually and no issues will be encountered.
Gapps on Android Marshmallow:
Recommended Gapps: OpenGapps Pico
What to select on OpenGapps page: ARM>6.0>Pico
While flashing Gapps is an optional step during the upgrade process, many people require the Google Play store to install all of their apps. It is required for people who want to flash gapps to increase their system partition to 1GB (or more). Stock partition sizes have a system partition size of about 500MB which is not enough to hold even the smallest gapps packages available!
Re-partition guides
You can re-partition your device by following my guide (Requires PC): http://forum.xda-developers.com/gal...ivatives/mod-increase-partition-size-t3011162 or Lanchon's guide (Doesn't require PC): http://forum.xda-developers.com/android/software-hacking/tool-lanchon-repit-data-sparing-t3358036
If you have working recovery, use Lanchon's guide (second link). Otherwise, my guide (first link) will work for everyone else.
Please note that re-partitioning your device via ODIN (first link) will delete all of your data, including your internal storage which contains all of your personal files. You must backup all of your files to an external sd card or PC if you want to keep them! However Lanchon's guide (second link) keeps all of your personal data but requires a working custom recovery!
Please also note about the naming of the zip/pit files!
If you get error 70 while flashing Gapps, make sure you are using the re-partition guides properly, you may have missed a step or forgot to do something. If you didn't bother reading all of the information I've given and decide to post about your error, you will be told to read the information properly and nothing else. All help was given already If you get some other error, read the OpenGapps FAQ.
Stock Cyanogen Recovery:
CM13 Stock Cyanogen Recovery is a basic recovery that allows you to flash zips from your internal and external sd storages. It provides wipe options and ADB flashing support, but was only designed to provide the basic tools for flashing. Although it works fine in recent builds of CM13, it is highly recommended that you use an Isorec Recovery like TWRP.
Update: Cyanogen recovery has fixed mounting support for internal and external sd as of the 5th of October nightlies. The steps below now only apply to people who want to use older CM13 builds.
If you have build 20161005 or later, you can now easily switch to an Isorec recovery simply by flashing it via Cyanogen recovery. You can not do this in older builds!
Isorec install on builds older than 20161005
1. ADB Sideload Method (requires PC)
This is the easiest and quickest method to restore Isorec Recovery on your device. However it will require ADB/Fastboot tools to be installed on your computer. You also need to enable ADB debugging and enable root access for ADB in the development settings to use this method. If you don't have ADB/Fastboot tools installed, download it from this thread
Download recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip onto your PC
If you haven't enabled ADB debugging and root for ADB, do this now in the development settings menu
Reboot your phone into Cyanogen recovery
Select apply update from ADB sideload
In the ADB/Fastboot folder containing ADB.exe, hold shift + right click the window to open up the folder menu.
Select open command line menu here
Type or copy and paste this command: adb sideload recovery-Lanchon-IsoRec-TWRP-2.8.7.0-20160113-i9100-(by-arnab).zip
Cyanogen recovery should begin flashing TWRP recovery
Once completed, reboot your device
2. ODIN method (requires PC)
This method requires ODIN to be installed on your computer. You will be connecting your phone to the computer which may or may not be a problem for some users.
Put your phone into download mode (Power key, home button, Volume Down button)
Connect your phone to your PC
Open ODIN. Make sure that it detects your device. If it doesn't, check if you have the right drivers installed and if the usb cable/port is damaged
Download ODIN-flashable CM12.1 kernel here: http://forum.xda-developers.com/showpost.php?p=57974756&postcount=4 Don't worry if it isn't CM13 kernel, you will have to reflash CM13 anyway! If you don't know which one to choose, the TWRP CM12.1 kernel is fine.
Select the CM12.1 kernel as PDA (or AP)
Make sure you untick auto-reboot
Start the flash.
Once flash is successful, disconnect your phone from your PC. Remove your phone battery, then reinsert it.
Get into recovery mode (Volume Up, Power Key, Home button)
Repeat CM13 flashing guide above without any backup.
If you have linux, use JOdin instead of ODIN.
3. Terminal method (Doesn't require PC)
This method requires a terminal emulator. Either download one from the google play store or enable the in-built terminal emulator in development settings. Follow the guide carefully. You can use this method if your USB port is broken.
See Lanchon's post: http://forum.xda-developers.com/showpost.php?p=65164875&postcount=1002
As mentioned in Lanchon's post, IF YOU MAKE A MISTAKE IN ONE SINGLE CHARACTER YOU TYPE IN THE TERMINAL, YOU COULD BRICK YOUR PHONE FOREVER!!!
Root on Android Marshmallow
CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for ADB too because this can help you recover from some problems that may occur in the future.
You may be familiar with the root tool, SuperSU, and it may have been installed in CM12.1 or earlier versions of android. Android Marshmallow has a different way of rooting the device. It is not compatible with older versions of root.
Currently, SuperSU doesn't work on CM13. Do not attempt to install it with system method and don't try to install it with systemless method.
How to update to a newer build of CM13
1. OTA Updater method
This method of updating Cyanogenmod is usually preferred by many users because it is ready-to-use and is quite simple to do.
Go into settings>about phone>system updates
If there is a new build available, press the download button. The OTA updater will now download the update to your phone
Once it finishes downloading, it will prompt you if you want to install the update. Confirm that you want to update and your phone should restart
Your phone will reboot into recovery mode. The update process is automated. Once the progress bar is full, your phone should reboot again.
If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
2. CyanDelta Update method (Popular method)
This method of updating Cyanogenmod is most beneficial to people who want to save bandwidth and/or want to download the update via their mobile data. This method typically saves around 200MB of data which makes it a quick way of updating, without sacrificing stability.
Download Cyandelta from the google play store
Download from CyanogenMod website the .zip file of the ROM you are using. Please note that if you haven't saved a copy of your current build onto your phone, the Cyanogenmod Downloads server usually deletes old nightlies. Update: The Cyanogenmod downloads page is gone, instead download from here.
Launch CyanDelta and select the .zip file you just downloaded from CM website. CyanDelta will import them and will create a new bigger zip in “Cyandelta” directory in the root of sdcard.
When an update will be available, a notification will appear. Now you can launch CyanDelta and start the download by simply clicking a button!
The new zip will be placed in “Cyandelta” dir in the root of sdcard. Now you can install it manually from recovery, or you can press “Install zip”. Cyandelta will automatically reboot to recovery, install the zip, wipe cache partition and reboot (this requires root permission).
If you are stuck using the CyanDelta update method, check out their FAQ on their website.
3. Manual method (Recommended)
If you have issues using the other methods to update CM13, you can also install the update manually via recovery. This method usually has the greatest success rate.
Backup your current ROM in TWRP or CWM! You will need to do this just in-case something goes wrong during the update process. If you don't have Isorec TWRP or CWM, use the guide above to reinstall CM13 with a working recovery!
Download newer CM13 build from the official cyanogenmod downloads page onto your phone. Note: Old cyanogenmod nightlies are usually deleted from the Cyanogenmod server if you haven't downloaded your current build onto your phone yet. Update: The Cyanogenmod downloads page is gone, instead download from here.
Flash the CM13 zip
Wipe cache
Reboot your device. If the recovery prompts if you want to fix root, always select NO because root installer is broken. If your phone doesn't bootloop and you get to the android is upgrading screen, you have successfully updated CM13!
New users are encouraged to post questions about CM13 here and not in the CM13 Development thread, this will leave everyone happy and everyone gets what they want
Thanks to Lysergic_Acid for CM13, Cyanogenmod team, CyanDelta team, arnab for his TWRP isorec recovery, Lanchon for his Isorec kernels, repartition script, Isorec recovery and guides.
Updated on 02/02/17
Since the wiki for our device hasn't been updated yet, here are a list of some issues on CM13:
Issues marked with red are recent issues you will experience in any current build of CM13.
Ongoing issues:
MX Player can not use HW+ decoder. Instead, use HW or SW decoder. The developer of MX player is working on a fix.
Cyanogenmod OTA Updater sometimes can be buggy. MD5 errors, download errors, installation errors. Although it is working fine for most people, I still recommend just to flash manually via recovery!!!
Internal storage and external storage is not labelled correctly and has a random name. This is not a bug but a feature of one of the mounting ways of MM.
Screenrecorder works for some users, however it seems that you can not playback them on your phone. Workaround: Play the videos using your PC.
Some apps may have trouble detecting internal/external storage.
Some bluetooth devices may not behave properly or connect
Multiple issues with F2FS. Please note that this FS is still relatively new for our device so bugs are likely to be experience. Stay on ext4 for best stability!
Some people have reported that they have lost connection to their mobile network. This usually can be fixed by resetting APNs. If this doesn't help, you may need to downgrade back to stock 4.1.2 ROM.
MMS video file (.3pg format) will not play on the default video player. Workaround: Play the video through MX Player on SW renderer.
Hardware button is always on until screen is switched off. Workaround: After installing the BLN MOD and synapse, you can control the timeout values.
You may experience reboots when you receive phone calls
More to be added later
Fixed issues:
(from latest issue solved to earliest)
Cyanogen Recovery can not mount internal and external storage. You can not flash zips via internal or external storage. ADB sideload or other methods of flashing can be used instead. Fixed in nightly 20161005
Battery Percentage Incorrect and Causing Constant Low Battery Warnings. Fixed in nightly 20160818
As of the 20160722 nightly, decryption of /data partition is broken. Keyboard can't be switched to enter digits. Fixed in nightly 20160724
As of the 20160722 nightly, setup wizard is broken. When you press next, the notification bar drops down instead of the next screen showing. Fixed in nightly 20160724
Some people have reported that the youtube app (play store version) displays green lines during playback.
Front camera errors in recent builds
Phone dialer is currently broken Workaround: Use google dialer from Google Play Store
Live lockscreen has multiple issues being experienced in recent builds.
Nightly 20160326 is experiencing Google Play Launcher FCs. Please stay on a earlier build until this is fixed. Fixed in nightly 20160329
People who are using a non-english language may experience Clock app FCs. This problem is under investigation. Update: Fixed in nightly 20160325
Doze feature can not optimize any apps. This is not a bug, doze is disabled on our device! Please ignore this menu! Update: Fixed in nightly 20160325. Note: This is the app standby feature that is now working and not motion sensor doze!
Nightly 20160323 is experiencing CM file manager FCs Fixed in nightly 20160325
Nightly build 20160216 is currently affected by the no signal bug and dialer issues. Update: Calling issues have been fixed in nightly builds 20160218 or newer. If you are on build 20160216, you should update immediately to fix this issue.
FAQ
Q: What is cyanogenmod?
A: CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 Marshmallow, which is designed to increase performance and reliability over stock Android for your device. 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. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Q: What version of android is CM13 based on?
A: Android Marshmallow 6.0.1
Q: What is Gapps?
A: Google Apps (Gapps) is an app package containing the Google Framework which is required for most apps from Google to function. This will include the Google Play Store and other Google apps and services depending on what setup you select (it varies on what Gapps package you select, I recommend OpenGapps).
Q: Is this ROM pre-rooted?
A: CM13 has root included, however it is disabled by default. To enable root, you need to enable root for apps in the developer options menu (tap the build number in about phone until it has been enabled). I recommend allowing root access for adb too because this can help you recover from some problems that may occur in the future.
Q: I get error 70 when flashing gapps. What can I do to solve it?
A: Error 70 means that you have insufficient space available in the system partition. Your device does not have sufficient space available in the system partition to install the Open GApps package. As I have said in my guide, you will need to repartition your system partition using one of the links in the gapps installation section of my guide. Then only you will be able to install gapps on your phone.
Q: Help me! My phone says that sdcard0 is corrupted! What can I do to solve it?
A: If you've re-partitioned your device recently using the ODIN method, it is highly likely that you forgot to format your internal sd card. You can do this in the recovery by selecting sdcard0 or internal sd, format as vfat (fat) or default (CWM). Alternatively, you can use your computer to format it manually by mounting your phone's storage via recovery then using a formatting utility such as the built-in windows formatting tool.
Q: Does xyz app work with CM13?
A: I don't know. Check the app's website, check the google play store, check other users comments. Google is your best friend. If not, try it out for yourself! Some apps require selinux to be set to permissive, you can do this in apps like SELinuxModeChanger.
Q: Does SuperSU work on CM13?
A: While there are ways to get SuperSU working, this guide is only here to provide basic procedures. I do not recommend new users to install SuperSU on any Android 6.0 ROM.
Q: My apps that require root say that I need busybox to use the app. What should I do?
A: You do what it tells you to do. Download busybox installer from the app store, install busybox and your app will hopefully work as it should.
Q: What happened to busybox? It was available on older android versions but why do I have to install it myself on CM13?
A: Busybox was replaced with toybox in CM13. As a result, you can not run apps that require busybox so you need to install a busybox installer from the google play store.
Q: Does GPS work well on CM13?
A: Reports have shown that GPS is still not reliable like in CM12.1.
Q: Does CM13 have Isorec Recovery Support?
A: Yes, it does. However CM13 comes with CM recovery as the default recovery.
Q: Does xposed work on CM13?
A: Yes it does. Use the latest installer (xposed-v80-sdk23-arm or newer) and make sure selinux is set to permissive.
Q: Which is better, CM13 or CM12.1?
A: CM13 is still new for our device. Naturally, there will be bugs experienced by users. Over time, the ROM will mature and it will become stable for everyone to use. Try it out for yourself and see which one is best for you
Q: Can I install CM13 on {different S2 model}?
A: If it is just a carrier/region variant of the international s2 i9100, it should work without problems. If it is different physically (hardware), then it will not work!
Q: Battery life sucks on CM13! What happened to doze mode?
A: Our device lacks the (low power) sensors that take advantage of this feature, therefore making it useless so it was disabled. Don't forget our device (s2) is quite old now, it shouldn't be a surprise that we can't take advantage of new features like this.
Q: Battery life sucks on CM13! (General)
A: Download and install betterbatterystats onto your device. Check what app is the culprit to your poor battery life. If there are no apps that are behaving strangely, try reflashing your current ROM and making sure to factory reset and format system partition. A lot of battery problems are created by the user, maybe brightness is set too high, change the screen timeout delay, etc.
Q: Can I update to CM13 without a computer?
A: Yes you can. I have included guides/steps that are not computer dependent if you haven't noticed already. If you have a broken USB port, you need to get it fixed ASAP because if anything happens during the flashing process, your phone is useless!
Q: My device runs slow on CM13. Can I do anything to make it go faster?
A: Make sure to close all apps that are not needed. Change swappiness to a lower value or 0. Change CPU governor parameters: Up threshold, sampling rate. Make these values smaller to give more performance. Remove apps that may be hogging up your CPU/RAM. Reboot, it helps
Q: What does android security patch level mean?
A: Google regularly updates their newer android versions with security fixes. Cyanogenmod will apply those fixes to their ROM so you will stay protected as well.
Q: Why is xyz feature not available in CM13 when it was available in CM12.1?
A: It is a good possibility that Cyanogenmod are not ready to add the feature yet. It could still need more internal testing or other more important features have to be added first for adding it to the ROM.
Q: Why can't I install gapps?
A: Now before you post this, have you read the post given by the users on the CM13 thread? I have said in my guide that in order to flash gapps, you will need a larger system partition. Please re-read the guide and make sure to read carefully before posting questions.
Q: What is BLN?
A: BLN (Backlight Notification) is a feature which uses your phone's hardware button lights to notify you whenever you receive a notification such as SMS, email, etc.
Q: How do I use BLN?
A: BLN is disabled by default. You need to use Synapse to configure it. See this thread
Q: How do I change the behavior of BLN?
A: See this thread
Q: Will BLN drain my battery?
A: BLN (not BLN without wakelock) prevents your CPU from going to deep sleep mode (low power CPU mode to save battery) which will drain your battery quicker versus having it disabled. Lighting up your hardware buttons will also use a little more power, so please take these factors into account before posting about poor battery life.
Q: Why is my button backlight always on?
A: See this thread
Tuning guide
For performance
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Change CPU governor to PegasusQ
Change swappiness to 20
Change I/O scheduler from CFQ to Deadline
Decrease CPU governor sampling rate to 40000
Decrease CPU governor up threshold to 60
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Change entropy read threshold to 512 and write threshold to 256
Disable entropy for internal and external sd
Disable iostats for internal and external sd
For battery life
These changes require an app (e.g. Kernel Adiutor) that can change tune kernel parameters
Kernel Adiutor
Change CPU governor to PegasusQ
Change swappiness to 40
Change I/O scheduler from CFQ to SIO
Increase CPU governor up threshold to 90
Increase internal sd card read-ahead to 1024KB
If you have 8GB/16GB/32GB sd card, set external sd read-ahead to 512/1024/2048 KB respectively (Note: Some lower quality sd cards may not behave well with higher read ahead values)
Decrease vfs cache pressure to 60
Change entropy read threshold to 512 and write threshold to 256.
Disable entropy for internal and external sd
Disable iostats for internal and external sd
Greenify
Enable aggressive doze (beware, you may lose notifications!)
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
rolves1899 said:
Thx a lot for that. There s everything what i need .
---------- Post added at 07:03 AM ---------- Previous post was at 06:24 AM ----------
Finally i flashed everything except gapps. Ty so much. Must i re-partition or can i flash gapp without it ?
Click to expand...
Click to collapse
Repartition is highly recommended, otherwise you will have a hard time finding a gapps package that will work. Use lanchon's guide linked in the OP now that you have a working recovery.
gsstudios
Got it. I'll try as soon as possible . Phone looks smooth atm. thx to u
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Draky50110 said:
Don't have problem to update from CM OTA and didn't lost IsoRec with this method.
Also if you flash VM13 then IsoRec, you don't need to flash IsoRec anymore after next CM13 flash.
Envoyé de mon GT-I9100 en utilisant Tapatalk
Click to expand...
Click to collapse
You have good luck then However, it still needs to be worked on.
Although it is not required to reflash isorec, I include it anyway in the steps to prevent issues that may occur anyway. That way, users are 100% sure that they don't end up with cyanogen recovery.
gsstudios
stylemessiah said:
Good work @gsstudios
I would add that CyanDelta is a valid way of updating, been using it reliably for days, saves 200mb+ downloads every night
http://www.cyandelta.com/index2213.html?q=FAQ
https://play.google.com/store/apps/details?id=com.cyandelta&hl=en
Click to expand...
Click to collapse
Thanks, will add this to the guide soon.
gsstudios
Thanks for your work and this nice guide.
In this guide in the repartition part where is instructed
to flash kernel with ODIN, i would instruct to set the option
for AUTOMATIC RESET after flash to OFF, and pull battery after flash.
Because the flash happens so quickly and its a little difficult to
do the 3-finger boot then.
Best regards.
Thanks for this thread, I wanted to ask questions on the other thread but think the devs are getting overwhelmed by basic questions so this thread is perfect.
I wanted to ask what exact steps I need to take as I am on cm12 with cyan recovery and it's been years since I flashed this phone so I don't want to brick it. I am on the original 512mb system partition.
I have Ubuntu not windows and struggling to get jodin loading and heimdall worries me a bit so I am going to borrow a windows machine later but before I do I want to make sure I have the steps right.
So I figure I need to install Odin, then use this to flash a twrp kernel first to get my recovery is that right? And at the same time I need to repit so I can do both things at once, then reboot my phone into twrp have I got that bit right?
Next I need to format the partitions, then reboot again into twrp? At the next reboot I then can flash cm13 from an external zip file, isorec and gapps all at once, then reboot again and the handset should come up?
I hope I don't upset anyone asking all this and I really appreciate help, for the past 2 weeks I have been googling and reading the other thread to make sure I have understood it right but bit put off from asking questions that might upset others.
OP updated with recommendations from other users. Thanks for the suggestions!
Remember that new users are encouraged to post in this thread as it was specifically created to help new users install/update CM13.
gsstudios
System partition looks risky to me. Is there any other way to flash gapps ? I can format internal memory if it helps. Im using phone to connect internet. If there is something wrong with partition i cannot solve it ..
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
fireburner-de said:
Very nice1! You could add that Lanchons repitting method keeps all data, but nevertheless, a backup is always recommended.
Click to expand...
Click to collapse
Already in the OP. It is the second link for the repartition section
gsstudios
AT LAST ! Now they will not spam the official thread of cm 13!
gsstudios said:
Already in the OP. It is the second link for the repartition section
gsstudios
Click to expand...
Click to collapse
Well I know, that the link is there. Just 2 lines after the links you write in red that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
UsualSuspectReaL said:
AT LAST ! Now they will not spam the official thread of cm 13!
Click to expand...
Click to collapse
I fear, they still will
fireburner-de said:
Well I know, that the link is there. Just 2 lines after the links you write in read that one will loose all data. That is where I meant you could mention that Lanchons script doesn't.
I fear, they still will
Click to expand...
Click to collapse
Yes, I forgot to change that. Updating now... I read your post wrong
gsstudios
Edit: Done. Thanks!