-
Notifications
You must be signed in to change notification settings - Fork 9
Common Problems
- check the installation guide [Installing LX in a Nutshell](Installing LX in a Nutshell)
and try fastboot erase system + userdata
- make sure you flashed the right ROM .zip for your device
- make sure the ROM download is complete and the .zip is not corrupted
- did you flash the kernel (boot.img) from the ROM? Other kernels are not supported.
- did you really extract boot.img from the .zip you installed last, and flash it with fastboot?
You cannot run a kernel from an older build. You must flash the kernel every time you flash a new ROM.
- flash minimal version GApps here: http://forum.xda-developers.com/google-nexus-5/themes-apps/standard-minimal-gapps-t2012857
±10% drain per hour is usually caused by something keeping the CPU awake ("wakelock"). Usual suspects:
-
WiFi
Try Settings > Wifi > Advanced > Keep Wifi on during sleep : never -
GPS
Better do not turn off GPS manually; or reboot after turning off. It works better if GPS turns itself off when no app uses it. -
Bluetooth Often changes. If you have a problem, the only 100% sure way is to reboot after using bluetooth.
-
Google Location Services
Set Settings > Accounts/Google > Location settings : off and see if it solves the battery drain
Change GPS/Wifi in Settings > Location access and see what happens -
Bad apps
If the built-in battery tool does not help you find it, try the BetterBatteryStats (BBS) app. The following two links can help you find the source of your battery problems:- How to Find the Root Cause of Your Android Battery Problems, How-To Geek
- [GUIDE] The Total Newb's Guide to Wakelocks, XDA-Developers
3G data often results in higher drain than 2G, but this is not as bad as wakelocks.
- use Settings > Apps to move apps to the SD card
- use the Link2sd app to move more files to SD
- experiment with int2ext and related scripts: http://forum.xda-developers.com/showthread.php?t=1716124
-
try adding this line to build.prop:
ro.opengles.surface.rgb565=true
- test the headset with some other newer devices
- if its working properly then this article will explain: http://en.wikipedia.org/wiki/Phone_connector_(audio)#TRRS_standards
- solutions: get a OMTP CTIA converter cable or self rewiring on audio jack (exchange wire between mic and ground) or get a OMTP connector standard headset.
- if its still not working properly, your headset might be broken.
- if its working properly then this article will explain: http://en.wikipedia.org/wiki/Phone_connector_(audio)#TRRS_standards