Welcome to CyanogenMod
![]() |
Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
|
Official Faq: Read First!
#1
Posted 03 June 2010 - 10:51 PM
OT/discussion posts WILL BE DELETED
Mod Edit:
=======================
If you would like to add additional answers to common problems/questions, please feel free to do so in a legible manner similar to the format of the posts below (i.e. the question then the answer).
If anyone notices/experiences a problem with a step in the FAQ, please PM me and I will look into it as soon as possible. I just want to make sure this thread doesn't turn into a general "Help" thread and instead remains a place for users to quickly find answers to widely asked questions.
Keep in mind that while many questions below are applicable to all releases of CM on the Droid, many have been here through several major releases and may not be as pertinent to your particular install. One particular instance that I can point out is regarding the Google Apps related questions. Some of those applications have been removed from the newer GApps packages and must be downloaded from Market (or via the one-time initializer that runs after setup).
Thanks,
AbsoluteZero
========================
#2
Posted 03 June 2010 - 11:05 PM
olta777 said:
-What is the base (ie ere27 vs ese81) for Koush ROM? A. It is based off Cyanogen's branch of the AOSP source. It is as new, or newer than any ese or esd out there
-Which OC kernels work? A. P3 and bekit(from rom manager) only at the moment.
-Which themes work for this ROM? A. There are a few...Please check Droid themes section.
-How is battery life on this ROM? A. Battery life is really good, but can be affected by your individual settings/apps and other modifications.
-Does this ROM include WiFi and USB tethering? A. Yes it does include both.
Just for start.
jbernard703 said:
A. Because of legal reasons the google apps cannot be packed together with CyanogenMod, you will need to check the box which says google apps when downloading your ROM and everything will be there.
T-Bucket said:
rockingondrums said:
A: In a way most Windows users will understand, "Root" is like giving you admin privileges on your phone. Naturally, the carrier didn't want you to have this. With Root, you can truly tap the potential of the hardware, because you have the access to it.
BTW, I'm sure someone could provide a much better explanation, but I think anyone who could handle rooting could handle this very simple explanation.
LrdElderon said:
also The forum apparently doesn't like the formatting used in openoffice and some words seem to have been smashed together... sorry about that.
-LrdElderon
Hi folks, I see lots of people withsome common problems popping up over and over again. Some arereal problems that can be fixed, others are just users unfamiliarwith the change in recovery and rom.
First I'm going to go offthe assumption that you are already rooted, have installed the rommanager app and have or tried to flash clockwork recovery. If thereis something that is missing PM me or post and I'll try and find afix or something to help and update as I can.
<Reserved for table of contentslater for easy searching if this gets long>
Issues:
1. ADB is yourfriend.
First thing I'd like to say is that ALL droid users that root and or use other roms SHOULD (emphasizedheavily) install the android SDK so they can use adb terminal commands to help troubleshoot, fix errors, and other handy things. It's the first thing I do and it's saved me many times being able toget into the phone to fix errors when I cannot boot up. The sdkcan be found for whichever os you use athttp://developer.android.com/sdk/index.html. depending on OShelp on installing can be pretty different. I suggest Googlesearch or come into irc or post a thread and one of us I'm sure canhelp you step by step.
2. HELP all my apps are gone!
Neverfear, due to the nature of Google apps (basically they are not opensource) they were separated from the rom so that Google can't throwaround cease and desists at Koush. When installing cyanogen romfrom the Rom manager app make sure you check the box for gapps or youwill not have your basic android apps like market, gmail, gallery,browser....etc. IF you happened to miss the option and ended upinstalling without Google apps, have no worries it's very easy tofix.
Download this filehttp://www.mediafire.com/file/mnzmk1nytt2/gapps-passion-EPE54B-signed.zipthen mount your sdcard on your computer and move the zip file over toyour sdcard in the main dir. unmount on computer and then onphone.
Now for those that listened and installed adb,open a terminal / prompt on the computer and type: adb rebootrecovery otherwise open rom manager and select reboot intoclockwork recovery or turn the phone off open keypad hold the letterx and keep holding while you press power and keep holding xstill while the phone boots and you are at the recovery screen.
Clockwork recovery works almost exactlythe same as sprecovery that most of you are used to does. You caneither slide out the keypad and use the dpad + enter + del forcontrols or use the same controls you do for sprecovery: volume =change options , camera = enter /select power = back. Now what youwant to do is pick -install zip from sdcard, then pick -choose zipfrom sdcard now scroll through the list of folders until you see thegapps-passion-EPE54B-signed.zip file. Highlight the file and enter.
This will install your Google apps backto your phone.
Help I installed an overclock kernel from <insert whichever dev> and I can't boot up!
This is probably the most common issue I seem to see on forums. The Cyanogen/koush rom uses a different type of ramdisk to load kernels. This means that you can't go and just download whatever kernel you used on your old rom and have it boot up. You'll be stuck on M. You have to use kernels that were compiled or “fixed” to be usable on the CM rom. The list of kernels is growing and there are some nice ones to choose from.
I recommend checking the kernel thread, but I will post links later if need be.
If you did install a kernel for a different rom and now you can't boot. You can try two things first. Plug your phone into your computer and you should hear the chime even at the M, in a terminal or prompt keep entering in the command: adb reboot recovery. Hopefully you make it through and you'll be rebooted into the recovery mode. Otherwise turn the phone off. Hold X, power on while holding x until you are at recovery. Then you can use the install zip option and install zip from sdcard and browse to a kernel that is for the CM rom.
If you DON'T have a kernel on your sdcard for the CM rom then download one on your computer and in recovery mode on the phone choose – partitions menu, then mount USB storage and you will have it mount on our computer just as normal. Copy the kernel to the sdcard, unmount as usual, then pick unmount in recovery. Hit the power button to go back a page and then go through the install zip from sdcard....etc and pick the kernel and install it. It will do it automatically you just need to select it and hit enter or click the camera button to choose it. Then hit power until you back up to the page that says reboot and pick that and you are all set.
Abandon ship! The apps are crashing!
If you have issues from either a new install or a backup restore where you have apps that are force closing or crashing on you, you have two possible ways to do the same fix that should hopefully fix the issue. Open rom manager and pick the bottom command for Fix permissions and let it do it's thing (might take a little bit). If Rom manager crashes, try using the terminal emulator and type SU then fix_permissions. One other option is to use adb, adb shell, then type fix_permissions there.
Themes.... Wow everything broke
Themes for the CM rom have to be made just for it. Attempting to use themes from other roms can break things, especially in the framework file. If metamorph doesn't fail on the themeing outright you can lose backlight, auto brightness, perhaps icons in the notify bar...etc Basically Very bad!
There will be themes in Rom manager that you can install as well as a list of themes that should be compatible in threads posted on the cyanogen / droid rom forum.
Just remember to make sure it says it's made for the droid cyanogen koush rom or you will have problems.
Sprecovery, how I miss thee..... just kidding!
Don't fret folks, if for some reasonyou decide you don't like CM rom (gasp) Koush was nice enough toadd the ability to flash sprecovery back to your phone and you canrestore whatever backup you wish. I also hear that I think thenewer sprecovery in testing can flash clockwork (not 100% sure) soit should be easy enough to switch back and forth, or just get rommanager back on the phone and use that =)
I see people posting concerns andfears about using clockwork instead of sprecovery. You can putthose fears away. Rom manager and clockwork have the same functionsand more than sprecovery and you can always flash back if you areuncomfortable.
Cyanogen mod killed the video star, MMS videos not working
More was in another file. I started to go back and add in detail on rooting and whatnot. ill post later....
hopefully my humor was not too painful hahaha. I thought a light hearted goofy faq that had the info would be nice. i know i like reading the silly ones.
T-bucket said:
A. Nothing happens to them. They're associated with your Google Account and you will be able to get them back without paying for them again. Just remember to select the Google Apps check box as part of the installation process so you have the Market to get them from.
2) From Cyanogen mod screenshots I see a system/kernel updater application built into the rom, Will this automatically install updates to Cyanogen and will I no longer receive Verizon OTA updates?
A. No, it will not automatically install Cyanogenmod updates. It will notify you of them, though. It is always your choice when/if to upgrade. A lot of people disable OTA updates as part of the rooting process before installing a rom. But, these roms do disable OTA updates. The "official" updates seem to matter less when you have the new features long before they're released.
Zortec said:
A. It updates the firmware (software that controls the CDMA radio). This can lead to increased call quality, fix connectivity issues, and increase battery life.
There is no official changelog though.
CEnnis said:
A: Reboot, when buying the Rom Manager license key it shows up in the tray, but will be gone (still installed) after a reboot.
#3
Posted 03 June 2010 - 11:26 PM
A:
- If you didn't WIPE, do so! Many changes happen between major versions and many times require you to WIPE data and cache. You will have to do this manually in recovery since you did not do it initially.
- If you wiped data/cache and it's stuck on the CM logo, give it upwards of 7 minutes during the initial boot before worrying (longer if you have a lot of apps on sd). The first boot takes a while. Note: 7 minutes is purely a guesstimation based on personal testing.
- If you have wiped and are still bootlooping, download a different kernel (one that is compatible with your ROM version!), place on your sdcard, boot to recovery (Power+X), and flash that new kernel via "Install zip from sdcard". *Applies mostly to nightlies with borked kernels or problematic custom kernels*
- If everything else fails, jump in #koush and someone will be glad to help you. Keep in mind that the above solutions will solve 95+% of your bootloop problems.
- NOTE: You can always exit a bootloop by pulling your battery.
Q: How do I wipe data/reset manually from recovery?
A:
- While the device is powered OFF, hold the Power and X keys to manually boot to recovery.
- Press the Volume Down button to highlight "Wipe Data" and press the camera button to select.
- Press the Volume Down button to highlight "Yes - wipe user data" and press the camera button to select.
- After it finishes, press the Power Button to go back to the main screen, highlight "reboot system now", then press the camera button to select.
A:
- From a different developer's ROM (including the stock rom) = YES!
- From a previous version of CM = Depends. It is recommended in order to decrease the likelihood of bootloops and Force Closes. Upgrades within major versions *should* be ok if nothing major has changed.
- As ALWAYS, best advice if you really dread a WIPE (which if you're doing it right should be a breeze anyway) is this. Use TitaniumBackup (or something similar) to backup your apps, data, and settings (NOT system apps/settings unless you know what you're doing) then...Make a nandroid backup of your current install (which is easy and ALWAYS suggested). After that, flash your update.
- No problems: You're set.
- Bootloop: boot to recovery WIPE data/cache, reboot, let the phone sit for approximately 30 minutes (sometimes longer) to resync your apps until you get a notification that "XX apps have been successfully installed" (use TitaniumBackup to then restore data and apps that didn't install).
- FC's: clear data for that app. If it's a core app, boot to recovery, and WIPE.
A: You must flash the newest Google Apps Add-on which installs those applications.
Q: There is an update for one of the Google Apps (Youtube, Google Search, VoiceSearch, CarHome, etc) and it will not update through Market (system installed GApps)?
A:
- If you have not flashed the most current GApps then flash them.
- If that doesn't solve your problem, backup/remove the /system installed apk by typing this in terminal (where APKNAME is the name of the /system/app located apk you are trying to update)
su mount -o rw,remount /system mv /system/app/APKNAME.apk /sdcard/APKNAME.apk.bak reboot
*If you'd rather just delete the apk instead of making a backup then replace the line that starts "mv" with "rm /system/app/APKNAME.apk"
**Alternatively some prefer uninstalling the app with TitaniumBackup (may not work on some /system apps) or just removing the apk with Root Explorer.
***If you'd rather not reboot immediately, you can swap "reboot" with "mount -o ro,remount /system" in the above code to mount /system back read-only. - Open Market and install the app.
A: Different kernels have different pros/cons and different reactions with particular phones (some phones just straight-up don't like ulv, lv kerns). The best thing for you guys to do is find the newest kernels that have your required features (i.e. compcache,tempmon,etc) then try each of those at your desired speed (or even several speeds). The only way to tell if it is the best kern for you is for YOU to try it out. Noone has the same exact setup or app combination as you (and each setup will have a different effect on batt life, resources, etc). Try one kernel out for a day or two. If it doesn't suit you, try another. Flashing kernels has been made ridiculously easy so experimentation should not be a hassle.
TL;DR is.....There is no "BEST" kernel, only the best for you in your particular scenario which you can only determine through experimentation. Updates and changes are continuously being made so just keep an eye on updates and try them.
Q: What happens if Market is Force Closing?
A:
- Try Fix Permissions in RM (or terminal)
If that doesn't work - Clear Data/Cache for the "Market" App
If that doesn't work - In the same menu as 2, click Force Stop, then Clear Data/Cache (if available), then Uninstall updates. After that, reopen Market and accept T&C and let it resync.
If that doesn't work - Try the remaining troubleshooting tips: http://wiki.cyanogen...Troubleshooting
- If all else fails, download/redownload the GoogleApps zip file (from RM or links in General Discussion) and reflash from recovery (or RM).
A:
- Sign into your Google Talk account as GTalk service must be running and connected to use Market.
If that doesn't work - Make sure the Google/Gmail account you have linked to Market is the primary account you are signed in under.
- Try installing another app from Market to kickstart the downloads again.
- Open the app you are trying to download and select "Cancel Download" then select "Install" again.
- See items 2 and 3 in the Force Closing question above.
- Try the remaining troubleshooting tips: http://wiki.cyanogen...Troubleshooting
A:
lbpiscool, on 30 June 2010 - 12:38 AM, said:
1)nandroid backup whatever you have
2)wipe data and factory reset your phone from recovery
3)reboot
4)do all the sign in and crap...
5)when you get to the home click on market
6)accept the terms, then try to download something
7)once you see it downloading just cancel and just go to your recovery and wipe and restore your nandroid backup
from Google cache (some of these should apply to 5.0.7.1 with mods...pull from it what you think is applicable
slayer said:
1. 5.0.5.7 is stable. If you are upgrading from .4 or before, it is a good idea to to either wipe data, or at least clear the data and cache for Launcher2 and/or Helix2. If you don't you will get FC's on reboot from the update.
1.5 To Clear the Launcher2 data/cache, From home, press the menu button, and go to settings, -> Applications -> Manage Applications. Then press menu again, hit filter, and select "All". Scroll down, find Launcher2 or HelixLauncher2, touch it, and hit clear defaults, clear cache, and clear data.
2. The Launcher2 in .7 is not the same Launcher from before. The helix code written by someone else was only included in Koush's port of CM. Since ESE81 came out, helix2 has issues with the drivers and will not work. The original Dev must fix that. In the mean time, Koush recompiled the N1 Launcher2 to work with ESE81. THIS IS WHY THERE ARE NOT 4 PERSISTENT BUTTONS/SHORTCUTS ANYMORE.
3. Koush, has decided to no longer provide an Over-clocking capable kernel with the ROM. It is still Bekits kernel, but with 600Mhz being the highest Clock speed. Nothing stops you from downloading any of Bekits or P3droids kernels from Rom Manager and Over-clocking your Droid.
4. This is basically the same as .6 with only minor changes made to support Launcher2. If you want to use a theme that was previously working with CM, make sure you either remove the Launcher2.apk from it first, or be prepared to replace the themed launcher2 with the one from .7 If you don't, you will get FC's upon boot. Use themes at your own risk. It is not Koush's responsibility to ensure themes work with his port.
5. If you are having some other issues, or have more questions prior to the upgrade, try IRC. There are usually several people in the channel at any given time that might be able to help you, and its instant, vice waiting for someone to respond to the 150th "5.0.5.7 Doesn't work thread"
#4
Posted 11 June 2010 - 04:00 PM
A. No. From Wikipedia - Unlike the DROID, the Milestone has a bootloader that only allows signed Firmware to load. This prevents users from booting Custom ROM images not signed by Motorola that have become popular in the Droid modding community. This has caused discontent in the Droid community in markets foreign to the US. Whether the disablement of custom boot loaders is due to retailer, carrier, manufacturer, or legal restrictions is unknown and the primary reason(s) may differ in each individual market.
Mod Edit:
For Milestone Discussion (A853 and A854) please see the pinned topic: http://forum.cyanoge...rola-milestone/
--AbsoluteZero
Edited by AbsoluteZero, 24 May 2011 - 03:54 PM.
#5
Posted 12 July 2010 - 02:38 AM
A: Your phone is not bricked. Plain and simple. Thanks to the magic of SBF flashing, you cannot completely brick you DROID (notice I said Droid specifically). Worse comes to worse, that's what you will have to do, but in a lot of cases you don't need to resort to that.
#6
Posted 24 July 2010 - 05:58 PM
A: The topic you posted is probably in the Experimental section, considering you're asking about something in a ROM that is not specified as Stable yet.
Motorola Droid - Experimental Mod
(This happened alot with CM6 RC# -- if you are reading this in a post-CM6.0 world)
#7
Posted 28 August 2010 - 10:26 PM
A: When it's released. (see also: asking for release dates will give you hair cancer.)
Q: wifi worked fine on all of the RC's, but with the CM6 stable my wifi is dropping all over the place. anyone else having issues?
A: google might of saved your password wrong.....
Balthazar, on 29 August 2010 - 01:09 AM, said:
1) Restart your router.
2) Go into Settings>Wireless & Network Settings>Wi-Fi Settings
3) Long press your stored Wi-Fi network and select "Forget network"
4) Hit Menu>Scan
5) When it finds your home network enter your password
Edited by RiZZ, 29 August 2010 - 04:23 AM.
#8
Posted 09 September 2010 - 12:53 PM
Absolute Zero said "Kernels are flashed the same way as roms whether you did it manaully or via RomManager. If manually, you should already know how to place the file on your card and flash it. If you used RM then find one of the Froyo compatible kernels in RM (premium section for jdlfg and slayher), select the speed you want to try, check "Backup" if you don't know how to manually fix it, then let RM do it's work the same as when you used it to flash the rom. Or if it's on your card, obviously you can use "Install rom from sdcard" in this thread.
Q: How do I flash a new Kernel without loosing my apps/settings?
Using ROM Manager, ensure you find a kernel that will work with your ROM and when you select it, don't check wipe data and cache. That will flash the new kernel only. Be sure to perform a back-up so you can easily recover in the unlikely event of a problem.
#9
Posted 15 September 2010 - 12:38 PM
A: (Possibly) due to an error in one of the nightlies, GPS will fail to lock. The fix is simple however:
Download GPS Status in the market, Settings > GPS & Sensors > Manage A-GPS state > 1) Reset 2) Download
#10
Posted 24 December 2010 - 01:54 PM
A: Go into settings-> ADW settings -> UI settings and scroll down to the Hidden Dockbar sections and deselect the dockbar box.
Q: I was sexting my girlfriend and for reason all of my messages vanished and the pic of my wang went to my mom!? Is this fixable?!
A: For the most part yes. Go to settings-> CyanogenMOD settings-> performance settings, and enable the messaging app to be locked into the memory. For your mom seeing your wang...that just sucks.
#11
Posted 24 May 2011 - 03:24 PM
A: More than likely, at some point you moved that app to your SDCARD which is preventing persistance of these settings. Move the app back to your device's internal storage to fix the issue.
#12
Posted 24 May 2011 - 03:34 PM
A: Your recovery has been damaged and you must reflash it.
- Let the device fully boot into the ROM you have installed.
- Open RomManager...Menu->Settings->Erase Recovery
- Then Menu->Clear DL cache. This will remove everything previously downloaded with RomManager to make sure the img is not corrupt. It does mean, however, that you will need a data connection for the next steps so that it can redownload the images.
- After that, select "Alternate recovery" at the bottom of the list and let if flash SPRecovery.
- After the message indicating that it has successfully flashed, select "Flash ClockworkMod Recovery" at the top and select your device.
- Optional: Repeat Step 5
- After the message indicating that it has successfully flashed, reboot to recovery to see if it works now.
Some of the steps are not necessarily required for your particular scenario but this should be more of a catch-all solution for more people and the extra steps will not damage anything for the others.
I will cover what to do if at any point you receive an error when trying to flash SPRecovery or CWR from RomManager in a post later.
#13
Posted 19 June 2011 - 08:02 PM
A: 5 simple ways to get stock kern back:
- If a standalone stock kernel zip exists: Remove any init files that were added with the custom kern (applies to deprimed) and flash the stock kernel update.zip.
- Flash CM again which will flash the stock kernel along with everything else. Keep in mind that you're reflashing the whole rom here so some customizations you made may be removed.
- Remove any init files that were added with the custom kern (applies to deprimed) then manually boot to CWR. Choose the advanced nandroid section, select the backup you made just before flashing the custom kernel and select to restore just the boot portion.
- Extract boot.img from CM to your sdcard and run "flash_image boot /sdcard/boot.img"
- If linux/osx is accessible: Extract the boot.img from CM, download an of sbf for your device (recovery-only or full), download sbf_flash...Place all in same dir and run "sbf_flash -r --boot boot.img filename.sbf"
#14
Posted 18 October 2011 - 02:22 PM
AbsoluteZero, on 19 June 2011 - 08:02 PM, said:
A: 5 simple ways to get stock kern back:
- Extract boot.img from CM to your sdcard and run "flash_image boot /sdcard/boot.img"
Stock kernel recovery process #4 fails.
#15
Posted 18 October 2011 - 04:55 PM
tkrug, on 18 October 2011 - 02:22 PM, said:
I will put this in the first post above but in the future if anyone notices/experiences a problem with a step in the FAQ, please PM me and I'll look into it. I just want to make sure the thread doesn't turn into a general "Help" thread and instead remains a place for users to check for answers to widely asked questions.
#16
Posted 02 September 2012 - 02:55 AM
AbsoluteZero, on 03 June 2010 - 11:26 PM, said:
A:
- If you didn't WIPE, do so! Many changes happen between major versions and many times require you to WIPE data and cache. You will have to do this manually in recovery since you did not do it initially.
- If you wiped data/cache and it's stuck on the CM logo, give it upwards of 7 minutes during the initial boot before worrying (longer if you have a lot of apps on sd). The first boot takes a while. Note: 7 minutes is purely a guesstimation based on personal testing.
- If you have wiped and are still bootlooping, download a different kernel (one that is compatible with your ROM version!), place on your sdcard, boot to recovery (Power+X), and flash that new kernel via "Install zip from sdcard". *Applies mostly to nightlies with borked kernels or problematic custom kernels*
- If everything else fails, jump in #koush and someone will be glad to help you. Keep in mind that the above solutions will solve 95+% of your bootloop problems.
- NOTE: You can always exit a bootloop by pulling your battery.
A:
- While the device is powered OFF, hold the Power and X keys to manually boot to recovery.
- Press the Volume Down button to highlight "Wipe Data" and press the camera button to select.
- Press the Volume Down button to highlight "Yes - wipe user data" and press the camera button to select.
- After it finishes, press the Power Button to go back to the main screen, highlight "reboot system now", then press the camera button to select.
A:
- From a different developer's ROM (including the stock rom) = YES!
- From a previous version of CM = Depends. It is recommended in order to decrease the likelihood of bootloops and Force Closes. Upgrades within major versions *should* be ok if nothing major has changed.
- As ALWAYS, best advice if you really dread a WIPE (which if you're doing it right should be a breeze anyway) is this. Use TitaniumBackup (or something similar) to backup your apps, data, and settings (NOT system apps/settings unless you know what you're doing) then...Make a nandroid backup of your current install (which is easy and ALWAYS suggested). After that, flash your update.
- No problems: You're set.
- Bootloop: boot to recovery WIPE data/cache, reboot, let the phone sit for approximately 30 minutes (sometimes longer) to resync your apps until you get a notification that "XX apps have been successfully installed" (use TitaniumBackup to then restore data and apps that didn't install).
- FC's: clear data for that app. If it's a core app, boot to recovery, and WIPE.
- No problems: You're set.
A: You must flash the newest Google Apps Add-on which installs those applications.
Q: There is an update for one of the Google Apps (Youtube, Google Search, VoiceSearch, CarHome, etc) and it will not update through Market (system installed GApps)?
A:
- If you have not flashed the most current GApps then flash them.
- If that doesn't solve your problem, backup/remove the /system installed apk by typing this in terminal (where APKNAME is the name of the /system/app located apk you are trying to update)
su mount -o rw,remount /system mv /system/app/APKNAME.apk /sdcard/APKNAME.apk.bak reboot
*If you'd rather just delete the apk instead of making a backup then replace the line that starts "mv" with "rm /system/app/APKNAME.apk"
**Alternatively some prefer uninstalling the app with TitaniumBackup (may not work on some /system apps) or just removing the apk with Root Explorer.
***If you'd rather not reboot immediately, you can swap "reboot" with "mount -o ro,remount /system" in the above code to mount /system back read-only. - Open Market and install the app.
A: Different kernels have different pros/cons and different reactions with particular phones (some phones just straight-up don't like ulv, lv kerns). The best thing for you guys to do is find the newest kernels that have your required features (i.e. compcache,tempmon,etc) then try each of those at your desired speed (or even several speeds). The only way to tell if it is the best kern for you is for YOU to try it out. Noone has the same exact setup or app combination as you (and each setup will have a different effect on batt life, resources, etc). Try one kernel out for a day or two. If it doesn't suit you, try another. Flashing kernels has been made ridiculously easy so experimentation should not be a hassle.
TL;DR is.....There is no "BEST" kernel, only the best for you in your particular scenario which you can only determine through experimentation. Updates and changes are continuously being made so just keep an eye on updates and try them.
Q: What happens if Market is Force Closing?
A:
- Try Fix Permissions in RM (or terminal)
If that doesn't work - Clear Data/Cache for the "Market" App
If that doesn't work - In the same menu as 2, click Force Stop, then Clear Data/Cache (if available), then Uninstall updates. After that, reopen Market and accept T&C and let it resync.
If that doesn't work - Try the remaining troubleshooting tips: http://wiki.cyanogen...Troubleshooting
- If all else fails, download/redownload the GoogleApps zip file (from RM or links in General Discussion) and reflash from recovery (or RM).
A:
- Sign into your Google Talk account as GTalk service must be running and connected to use Market.
If that doesn't work - Make sure the Google/Gmail account you have linked to Market is the primary account you are signed in under.
- Try installing another app from Market to kickstart the downloads again.
- Open the app you are trying to download and select "Cancel Download" then select "Install" again.
- See items 2 and 3 in the Force Closing question above.
- Try the remaining troubleshooting tips: http://wiki.cyanogen...Troubleshooting
A:
from Google cache (some of these should apply to 5.0.7.1 with mods...pull from it what you think is applicable
I installed the apps fix gapps-passion-EPE54B-signed.zip and now I have a bootloop. I did what you said to fix the bootloop and it is still stuck in a bootloop. HELP!
#17
Posted 02 September 2012 - 10:54 PM













