A lot of folks seem to have that problem; I seem to have lucked out...the solution was mentioned on the first page in getting some video player from Google Play store...
Sent from a Purple LG-LS670 with CM9...the New Wolzard Phone...yes.
hey if i forgot to flash gapps/dl it can i just reboot.. to the ro without gapps. go back nto recovery and flash gapps?
Also, is there any sort of log that's stored for a longer period of time for this ROM? My son managed to cause the latest 16 to spontaneously reboot while playing games while we waited to watch fireworks last night...
========================================
device/lge/thunderc-common ...
========================================
commit 70077436f94636c55b789dcc4751368a6a695857
Author: Xxxxxx Xxxxxxx <tdm.code@gmail.com>
Workaround for mismatched AudioSystemLegacy.h.
========================================
Get a copy of /proc/last_kmsg.
Stole ( )this from quattrimus cm9-nightly-20120705.changelog:
Code:======================================== device/lge/thunderc-common ... ======================================== commit 70077436f94636c55b789dcc4751368a6a695857 Author: Xxxxxx Xxxxxxx <tdm.code@gmail.com> Workaround for mismatched AudioSystemLegacy.h. ========================================
Might this be related to the audio lib boot animation hang some of us are experiencing?
I couldn't find "/proc/last_kmsg"... found /proc/kmsg... but I don't think that would be meaningful...
When I say it rebooted, I saw the "LG logo and the boot animation again...
Not sure this would be of any help, but...
current dmesg -> [DOS] dmesg - Pastebin.com
current logcat -> [DOS] logcat - Pastebin.com
Hmm .. if it reboots to the lg logo you typically get a last_kmsg. That is a recovered copy of the crashed kernel log. It should provide valuable hints on what caused the reboot. The running info won't help, unfortunately.
Wipe system and cache, then delete the bootanimation.zip inside the alpha16 zip. And flash with signature off. There's two settings that preload the bootanimation, but could be filling up the memory unnecessarily. Otherwise, use quattrimus till this gets worked out. At least it narrowed down a bit, and not the latest audio patches, but could be a bad sync on my part when cm9 was in the middle of commits.