Hey Guys,
Woke Up this morning and did the usual of checking the time on my phone, to my surprise the screen was on and it seemed to be stuck on 08:31, So I thought oh it's just a crash and pulled the battery out, but now it's just stuck on the CM9 Boot logo (Running Alpha 4), I need my texts and call log and contacts (Can get contacts of Google Mail) But I've tried running logcat while it's in the state and all I'm getting is "09:39:38.124 Debug dalvikvm 1858 GC_CONCURRENT freed 1836K, 37% free 5319K/8323K, paused 2ms+3ms" and Something about Starting service ScreenFlinger, I would rather not wipe it but if I have to I have to.
Any Idea's?
Jamie
Anything anyone?
Related
hi all
ive been having major difficulties controlling batt drain and 100% cpu usage after rooting and then flashing a custom firmware.
it usually...almost always..in fact- happens when i switch on wifi together with auto-sync data.
so i thought it must be one of the sync accounts, plus I'd read a bit about htc sync accounts sucking batt. So I disabled most...and there was improvement. but then it still does happen once in a while..once or twice in the middle of the night, meaning i woke to a dead phone in the morning. every time it gets so bad that I just have to reboot the phone.
when the slow down happens, i open up osmonitor, watched Android's own process log or the HTC launcher's log and i'd usually see a million of these:
gc_for_malloc freed xxxx objects / xxxx bytes in xxx ms
but am unable to troubleshoot further because it seems to be nothing meaningful.
anyone got any ideas?
yellowchilli said:
hi all
ive been having major difficulties controlling batt drain and 100% cpu usage after rooting and then flashing a custom firmware.
it usually...almost always..in fact- happens when i switch on wifi together with auto-sync data.
so i thought it must be one of the sync accounts, plus I'd read a bit about htc sync accounts sucking batt. So I disabled most...and there was improvement. but then it still does happen once in a while..once or twice in the middle of the night, meaning i woke to a dead phone in the morning. every time it gets so bad that I just have to reboot the phone.
when the slow down happens, i open up osmonitor, watched Android's own process log or the HTC launcher's log and i'd usually see a million of these:
gc_for_malloc freed xxxx objects / xxxx bytes in xxx ms
but am unable to troubleshoot further because it seems to be nothing meaningful.
anyone got any ideas?
Click to expand...
Click to collapse
I have the same problem just like yours!
I don't know how it happens?
But I founded a way to solve it temply.
when you saw the CPU load are 100% and system runs lagging.
First, launch the "set CPU" if you had installed.
Than you'll see the frq. Goes to 245 Mhz if you're set profile to "ondemand"
don't need doing anything, At least, you can see that CPU load are back to 5%~15%
As normalized. I don't know how it works? But it works everytime.
I'm using coredroid v3.2 and O/C 1.2G Hz, desire hd.
Can anyone who can tell us how it happend?
I've read that this is a common problem with many custom ROMs. If I remember correctly it had something to do with a file being constantly read. So you have to set permissions for that file which forbid reading. The trouble is that the system changes permissions again, and you have to constantly change the permissions using a sheduled script. It works but doesn't really solve the problem. The solution is to flash a custom ROM which has this fixed. Android Revolution HD 3.2 is one of them. With 3.1 I had this issue, now with 3.2 it's gone for good.
haha i don't know how you managed to get to setcpu..
mine is a near-freeze most of the time and would probably take forever to get there
but if i do get the chance i'll give it a try, thanks.
thanks, am indeed running on 3.0 so i'll give 3.2 a try.
Phone:
T-Mobile G2
CM-7.0.0(full wipe then flashed from Post-OTA Stock ROM)
O/Cd to 1.017 Ghz with SetCPU
.26 Radio
Problems:
- Lockscreen never appears at all. Phone wakes straight into last activity
- Volume Down wakes phone. Not set in settings to do so.
- Home button gives haptic feedback on press, but performs no action on short or long press.
- All calls, whether to T-Mo or GV number go straight to voicemail.
Context:
I had just fixed a boot issue with CM7 by wiping cache and dalvik. I then decided to install Zeam Launcher, which has since been uninstalled. Have used SetCPU to set clock with On Demand governor back to max 800 mhz. No effect.
Also have been testing app on device but only has simple activities with no permissions needed and it runs with no errors or warnings.
Anyone have an answer to any of these issues? I have done a soft reboot and a battery pull. Thanks for the help.
Ok, here's the logcat log when I press the power button to turn the screen off, and the again to unlock it.
04-22 20:04:03.297: INFO/power(1485): *** set_screen_state 0
04-22 20:04:03.347: DEBUG/WifiService(1485): ACTION_SCREEN_OFF
04-22 20:04:03.497: DEBUG/SurfaceFlinger(1485): About to give-up screen, flinger = 0x93b98
04-22 20:04:03.507: DEBUG/AK8975(1385): Compass CLOSE
04-22 20:04:08.167: INFO/power(1485): *** set_screen_state 1
04-22 20:04:08.257: DEBUG/SurfaceFlinger(1485): Screen about to return, flinger = 0x93b98
04-22 20:04:08.327: DEBUG/AK8975(1385): Compass Start
04-22 20:04:08.687: DEBUG/WifiService(1485): ACTION_SCREEN_ON
04-22 20:04:16.267: DEBUG/dalvikvm(2483): GC_EXPLICIT freed 11K, 55% free 2708K/5959K, external 461K/973K, paused 76ms
04-22 20:04:31.247: DEBUG/dalvikvm(2491): GC_EXPLICIT freed <1K, 52% free 2789K/5703K, external 0K/0K, paused 60ms
Click to expand...
Click to collapse
Have you tried to reflash? redownload the rom and then flash.
Sent from my HTC Desire Z/G2 Using XDA Premium App
I was trying to avoid it, but I did a complete wipe(user data, cache, and dalvik) then re-flashed. Everything back to normal. With the calls, is there a known issue with Google Voice hijacking email causing issues on T-Mo in general or with CM7 in specific?
Thanks for the help. Just needed someone to convince me that the wipe-and-flash was what I had to do. Just a time suck.
I'm going through the same exact problem, I tried doing a full wipe, fixing permissions, reflashing, I don't know what else to do?
hey, did you ever get this issue resolved? I'm having a similar issue and my volume key won't respond
I'm facing this problem after going from Jellybean back to Gingerbread. Anyone resolved this?
---------- Post added at 11:44 AM ---------- Previous post was at 11:15 AM ----------
Solved. I flashed ICS gapps instead of GB gapps.
Actually I have this problem with CM7 RC1v2, but in the past I had the same issue with Froyo ROM (Barebones one and if a remember well also official one): before going to sleep I put the phone in aeroplane mode and in the following morning I found it switched off.
This is not systematic, or better, last 3-4 days it happened always but from when I flash CM7 the problem seemed to be solved.
Last night I made a CatLog (attached) and reading it today I have noticed the following lines:
07-13 01:37:01.553 D/dalvikvm( 8555): GC_CONCURRENT freed 421K, 52% free 3204K/6663K, external 898K/1410K, paused 3ms+4ms
07-13 01:52:20.514 E/BATTD ( 1923): unrecoverable_error=AP Panic
07-13 01:52:20.514 I/BATTD ( 1923): SBCM_GLUE: Battery Exhausted, Sending 0 capacity to Power down
07-13 01:52:20.522 I/ActivityManager( 2149): Starting: Intent { act=android.intent.action.ACTION_REQUEST_SHUTDOWN flg=0x10000000 cmp=android/com.android.server.ShutdownActivity (has extras) } from pid 2149
I'm not so skilled in linux/android debuging (what is BATTD? sure something related to the battery...), but I think this is the moment that cause the shutdown of the defy.
Due to the fact that the issue happens both with CM7 than Froyo rom, I (unfortunately) suspect that may be a problem of the battery.
Have someone an idea about the possible cause of the problem? Or could it get more information than me from the catlog?
Many thanks.
EDIT: obviously the battery was charged, during catlog logging was around 60%. If the defy is connect to the power supply the issue seems not happen.
No one can help me to understand the catlog?!
Today happened another time, but I have not the catlog.
Please, no one have any idea? Or the only way is to understand is to buy another battery?
Again...
07-25 00:05:25.366 D/dalvikvm( 2286): GC_FOR_MALLOC freed 358K, 46% free 3720K/6791K, external 0K/512K, paused 57ms
07-25 00:22:46.530 E/BATTD ( 1927): unrecoverable_error=AP Panic
07-25 00:22:46.530 I/BATTD ( 1927): SBCM_GLUE: Battery Exhausted, Sending 0 capacity to Power down
07-25 00:22:46.538 I/SSM ( 1935): UEvent: PA Boost - Battery TOO LOW
Id suggest buying a second battery and see if the problem persists. If it does not, ditch your first battery, if it does hope for help
I would buy a cheap after market battery - they should be avaible on ebay fo less than 10$-
Yes, I just ordered one: 2,27 euro shipped from HK ahahah OK, only to see if it resolves the problem and if it reveals good in all, well I was lucky, otherwise I will buy an original one
Thanks for the reply!
Hi everyone,
I have been having issues lately with the cm10.1 nightlies in which I can be doing anything, or even doing nothing, and my phone randomly crashes and will not work again until the battery is pulled. This prompted me to pull a logcat. The one attached is from when I looked over on my desk and saw it had the issue again. I suspect it rebooted around the time below, based on how long it takes me to remove the cover and turn it back on.
Any ideas? I have no microsd inserted and 7gb free space.
Thanks for any help!
05-22 22:15:17.915 I/Gmail (4741): Not enough free space to download attachments in background
05-22 22:15:18.696 I/Icing (3260): Not enough disk space for indexing
05-22 22:15:18.696 E/Icing (3260): Aborting indexing of corpus E2E6426024ACB643D3653CACACB7F9526B0D3533
05-22 22:18:28.231 D/lights (626): set_light_buttons: color=0xff3d3d3d, tlc=1.
05-22 22:18:28.231 I/PowerManagerService(626): Waking up from sleep...
Sean09 said:
Hi everyone,
I have been having issues lately with the cm10.1 nightlies in which I can be doing anything, or even doing nothing, and my phone randomly crashes and will not work again until the battery is pulled. This prompted me to pull a logcat. The one attached is from when I looked over on my desk and saw it had the issue again. I suspect it rebooted around the time below, based on how long it takes me to remove the cover and turn it back on.
Any ideas? I have no microsd inserted and 7gb free space.
Thanks for any help!
05-22 22:15:17.915 I/Gmail (4741): Not enough free space to download attachments in background
05-22 22:15:18.696 I/Icing (3260): Not enough disk space for indexing
05-22 22:15:18.696 E/Icing (3260): Aborting indexing of corpus E2E6426024ACB643D3653CACACB7F9526B0D3533
05-22 22:18:28.231 D/lights (626): set_light_buttons: color=0xff3d3d3d, tlc=1.
05-22 22:18:28.231 I/PowerManagerService(626): Waking up from sleep...
Click to expand...
Click to collapse
I'm no expert on that matter, but maybe you want to address that trouble to the CM - Nightlies thread in the developer forum. I know that there's a lot of people having RR or SOD on nightlies, and some have found a solution on that thread, like the latest pointed by Mikeyman, being to update the Firmware of your phone...
http://forum.xda-developers.com/showthread.php?t=2138101&page=237
I know this was from a couple days ago, but I'm having some very similar problems even after cleaning up free space on my /data partition. Massive slowdown, frame buffer issues, then clean reboots (or eventual unfreezing).
Hello,
somtime ago I encrypted my G3. I wanted to remove that now. So I started the decryption and everything seemed normal and the decryption went up 17% but not any further. The progressbar was still moving, but didn't gain any percent. That state lasted for about 6 hours, until I last checked the phone one hour ago. When i checked the phone now, the phone still says "ENCRYPTION - wait until your phone is encrypted, 17% done", but the progressbar isn't moving any more.
Any tips, what to do now?
Best regards,
Manfred