Troubleshooting

From CyanogenMod Wiki

Jump to: navigation, search

Contents

[edit] G1 root/upgrade problems

  1. If you have issues with the rc29/7 downgrade, reformat the card and re-download the DREAIMG.nbh and try again
  2. If you accidentally let the HTC recovery boot, it will attempt (and probably succeed) to replace your nice shiny CM-1.4 recovery.img with the default HTC ADP1 recovery. You'd see /!\ when booting with home held down. Of course, HTC doesn't let you install custom ROMs, so you'll have to get the custom recovery back. See RE-recovery-img if this happens.

[edit] Magic root/upgrade problems

[edit] App issues

[edit] If an app doesn't work

  1. Try reinstalling (see below if the market doesn't let you)
    • For Google app issues, reinstalling is re-flashing the 1.6 base & CM without a wipe.
  2. Clear data/cache for the app in settings->applications->application management
  3. Try fixing permissions from recovery. Reboot into recovery and type (from ADB shell or 'recovery console'; this is 'Fix UID Mismatches' in AmonRa recovery): 
mount -a
fix_permissions
reboot
    • This can also be run from a Terminal Emulator in a running system


If that doesn't work, wipe the dalvik cache from recovery and reboot. Go to 'console' (ADB shell) and type (Or 'wipe'->'wipe dalvik-cache' in AmonRa):

  • rm /data/dalvik-cache/*
  • reboot
    • The boot after this will take as long as if you'd just upgraded CM, regenerating the dalvik cache is a big part of the upgrade firstboot lag time. The more apps you have, the longer this will take.


You can try reinstalling all your third party apps. Type this to automatically reinstall all the apps you have installed without clearing settings: 

for i in /data/app/*.apk ; do pm install -r $i; done
    • It's recommended to wipe dalvik cache again after doing this.

Ultimately, you probably should get a logcat of the crashing/malfunctioning app and if you can't understand it, ask in the xda-dev thread or #cyanogenmod.

[edit] Maps won't upgrade from market

As of 4.1.99, Maps (and all other Google apps) isn't part of CyanogenMod. But, not every 1.6 base image is created equal, it appears. Also, themes replace the maps and other .apk files, and of course there was much hacking to get Nav working before it was released to everyone. Regardless of the cause, the solution to maps not updating (e.g. bad signature) appears similar for everyone:

Remove all traces of Maps.apk, settings, and dalvik-cache from phone (from terminal, after 'su' or from adb shell): 

# mount -o rw,remount /system
# find /system /data -name \*google\*maps.apk\* -o -name Maps.apk | xargs rm

Open market and upgrade.

If that doesn't work, you can also try removing it from the /data/system/packages.xml file. Be VERY careful of this, though. Mess up the file and you probably broke all your packages!

  1. Boot in recovery mode, because packages.xml is re-written on shutdown
  2. Delete the maps content as documented above!
  3. Grab the package from the phone(eg: adb pull /data/system/packages.xml)
  4. Remove the <package> tag referring to the maps application.
  5. Push the file back to the phone.
  6. Reboot.

After that all traces of the old maps key should be gone, and you will be able to install the new version from the market.

If the above isn't enough, you may have to:

  1. Re-flash a known good 1.6 base ( Defanged DRC83 works on Magic/Dream)
  2. Re-flash the latest stable version of CM.
    • Of course 32A/Rogers Dream users need to flash the EBI1 Kernel
  3. Open market and upgrade.

[edit] Market starts downloading with a delay, or doesn't start downloading at all

The login service that needs to run in the background in order for you to download, sometimes does not start. The service is shared between GTalk and the Market, GTalk being the responsible entity for starting the service. If your download isn't starting, manually login into GTalk, and that should fix the problem.


[edit] Apps don't run and appear in market with greyed out buttons

This typically happens during a ROM upgrade or when moving sdcards with apps2sd or similar. The cause is the application file (.apk) actually goes missing or gets deleted, but the market still thinks it's installed. The easiest solution is to manually remove the market data and let it re-create it from the .apks that are present.

  1. Start by making sure the market isn't running (task manager of your choice, or settings->applications->manage applications, Market, 'Force Stop' button).
  2. Then open a terminal and type 
su
rm -r /data/data/com.android.vending/*

Finally, restart the market (it may take a minute and possibly throw an "Application Not Responding", just press wait)

If Market still shows the Open and Uninstall buttons grayed out, reboot your phone now.

[edit] Other issues

  1. How do I enable the HTC_IME?
    • Go into settings->Locale & test and disable "Android Keyboard" and enable "Touch Input".
  2. I want to switch back to ext2.
    • Reboot into recovery (my recovery image), drop to a console (Alt+X). Remove the journal with "tune2fs -O ^has_journal /dev/block/mmcblk0p2". You should then fsck with "e2fsck /dev/block/mmcblk0p2".
  3. My /system/sd is read only and/or didn't upgrade to ext3!
    • Your filesystem is probably corrupt. Boot into Recovery 1.2+ and run a filesystem check from the menu. If it tells you to run it manually, drop to a console (alt+x) and run "e2fsck /dev/block/mmcblk0p2".
  4. I have problems with force closes and have to reinstall my apps after a no-wipe upgrade!
    • Run the "permission fixer" script. It is included in this build as well as Recovery 1.2+. Just execute "fix_permissions" from a terminal or the recovery console and reboot. IF YOU HAD A THEME INSTALLED AND UPGRADED AND NOW GET FORCE CLOSES- just reflash your theme after upgrading, this will get rid of any issues. If you had a previous ROM installed that copied stuff to your SD card (like most of the Hero ROMs), you'll need to clean that out.
  5. It's taking forever to boot!
    • The first boot will take longer than normal because dexopt needs to run. If you are nervous, connect USB and run "adb logcat" to watch the progress.
  6. My phone rebooted by itself!
    • Possible kernel panic or oops. I'm testing some stuff to get logs of these events so they can be debugged.
  7. My camera is black and white only!
    • You have settings left over from the old Android camera. Just go into the Camera, hit menu, settings, then "reset to defaults".
  8. I used to have 2-10 desktops, and could change them, and also hide apps in the menu. What happened?
  9. My auto-rotate/accelerometer/compass isn't working!
    • Not really the fault of the ROM, but here's how to fix it: Go into recovery, drop to console, "mount /data", then "rm /data/misc/akmd* /data/misc/rild*" and reboot.
    • Sometimes the /data/misc/akmd_set.txt file is not re-created after deletion. The only way to get the sensors working again is to find a akmd_set.txt file from a previous backup where the sensors were working, and manually push that file into the /data/misc directory. The files can be extracted from a nandroid backup by using an application called "unyaffs". I posted the contents of my settings file at http://forum.xda-developers.com/showthread.php?t=547330&page=3. 
Create a text file on your PC in the adb directory called akmd_set.txt, and paste the contents from my post into that file. Run:
push ./akmd_set.txt /data/misc

[edit] Battery recalibration

If you're experiencing higher than normal battery drain, try the following:

  1. Charge the phone to full battery; power off and let it keep charging until the light is green.
  2. Boot to recovery mode and go to console (or adb shell) and type: 
mount -a
rm /data/system/batterystats.bin
  1. Reboot the phone and use it normally, but don't charge until it shuts off.
  2. Recharge the phone completely and then use as you normally would.

Note: Newer Amon_Ra recoveries have an option to delete the battery stats, do this in place of the console commands above, but charge/discharge as stated.

[edit] HTC Magic / Sapphire bad audio (voice/mic) quality after upgrade

Every CM-release after 4.2.11.1 caused major troubles with my audio/mic quality. People I had phonecalls with immediately complained about the audio quality. I could hear them perfectly, but as far as they told me I sounded "far away" or "damped".

I then googled for about a week, read hunreds of articles and posts on the XDA-forum and found nothing but a few hints that the files 

    /system/etc/AudioFilter.csv
    /system/etc/AudioPara4.csv
    /system/etc/AudioPreProcess.csv

are often involved in audio-problems (Mainly in connection with bluetooth-headsets tho). But what I did then, and what solved the problems for me, was the following: 

    Replace the three files in the broken installation with a backup of them from the old (working) ROM!


[edit]
One way to do it


1. Backup the 3 files from your working rom before you upgrade. One way to do it would be via adb. 

    adb remount
    adb pull /system/etc/AudioPreProcess.csv .
    adb pull /system/etc/AudioPara4.csv .
    adb pull /system/etc/AudioFilter.csv .

If you have no chance to access the old files, try mine. I created a small tar-archive here and I THINK that it will also work on different phones. Please document any success here!


2. Upgrade the ROM as usual (via CM-Updater, your recovery-rom, ... etc)

3. Boot your new ROM ( and verify that you still experience the bad voice-quality), then replace the files on your new installation with the ones you saved from your old installation

    adb remount
    adb push AudioPreProcess.csv /system/etc
    adb push AudioPara4.csv /system/etc
    adb push AudioFilter.csv /system/etc
    adb shell reboot

4. The phone will reboot and then the problems were gone!


I also wiped several times and reflashed "from scratch" but I don't think that the wipes were in any way linked to the solution. My phone just got faster because of the general "cleanup" which was a nice side-effect :-)

Retrieved from "http://wiki.cyanogenmod.com/index.php/Troubleshooting"
Personal tools