- Thread Starter
- #376
No idea. Whenever 4.0.4 source is released and merged into CM9. My guess is a few weeks maybe.I have had like zero problems with .0.2 but apparently im missing stuff. any idea on an eta for a .0.4 build?
No idea. Whenever 4.0.4 source is released and merged into CM9. My guess is a few weeks maybe.I have had like zero problems with .0.2 but apparently im missing stuff. any idea on an eta for a .0.4 build?
Changes in 2/13 build:
- Profiles - Quiet Hours
- move the UAString selection from debug to advanced
- Upgrade kernel to 3.0.20
- AppsCustomizePagedView: Fix slow transition animations
- AppWidget: Use old padding method on 4.0.1
- Display contact name if available in delivery report notifications.
- Battery percentage settings updated.
- gapps updated.
- Blue buttons updated to 2/13 build.
Is anyone else missing apps, particularly the stock video player? I went from stock 4.02 to the 2-6 version. I did factory wipe, data wipe, and Davlik cache (overkill, I know.) After that, Video Player didn't show in Apps. I could play recorded videos and the app would launch fine. Also, the app would show in local search but generate an error, something about not being in the build manifest I think.
I downloaded the 2-13 builds, wiped Davlik cache, and installed but have the same problem except the app doesn't show in the local search. Thanks for any help!
Flashed to 2/15 settings keeps force closing. Fyi
Sent from my Galaxy Nexus using DroidForums
Did anyone else see facial recognition break or battery use increase on the 2/15 build?
If you are having settings FC run this in terminal or adb shell: rm /data/data/com.android.settings/shared_prefs/CMStats.xml
this worked for me. altho i was too lazy to reach for my cable and used Root Explorer instead. I tried using the included Terminal Emulator app, but I'm not sure how to grant it the right permission b/c it doesn't see that set of folders or the file.
My phone is asking whether I would like to turn on CMStats now...should i leave it off? or did deleting/re-creating the file fix the issue...and i can turn on again?