Hey.
When I press the power button to wake my screen the backlight seems to start lighting up ( from the center of the screen to the borders) but nothing is shown.
I press the power button again, screen goes completely black, I press it again and the screen wakes as it should.
It seems to me it only happens if the device has been on standby for a longer period of time (1~ hour).
This has been happening on every ROM and kernel I've been using (4.2, 4.2.2, 4.3, 4.3.1, 4.4 and their respective stock kernels as well as NEO and Franco kernel in several revisions).
I've been using lots of different CPU, GPU and voltage settings over time but the issue persists.
Strangely I never had this happen when receiving a call or when the alarm goes off in the morning.
I have no idea what possibly causes this. Maybe anyone has a clue?
Sent from my Nexus 4 using xda app-developers app
Does no one have heard of this issue before? :s
Sent from my Nexus 4 using xda app-developers app
Oxious119 said:
Hey.
When I press the power button to wake my screen the back light seems to start lighting up (from the center of the screen to the borders) but nothing is shown.
I press the power button again, screen goes completely black, I press it again and the screen wakes as it should.
It seems to me it only happens if the device has been on standby for a longer period of time (1~ hour).
This has been happening on every ROM and kernel I've been using (4.2, 4.2.2, 4.3, 4.3.1, 4.4 and their respective stock kernels as well as NEO and Franco kernel in several revisions).
I've been using lots of different CPU, GPU and voltage settings over time but the issue persists.
Strangely I never had this happen when receiving a call or when the alarm goes off in the morning.
I have no idea what possibly causes this. Maybe anyone has a clue?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
OK, so I have been having similar issues, but mine is worse!
When I press the power button to unlock, I get a dim back light but no display. I then press power again and you can see the faint back light turn full black just like when you hit that button to turn your screen off, then I try again to turn on my display and I keep getting the back light on on off cycle. I've tried using my connected bluetooth to make a call to see if the display pops up and nothing.
Eventually, I have to hold the power button down until I force the phone off, and then turn the phone back on in regular mode (not safe mode which maybe I should try even though I have no idea what that allows me to do) and continue with what I was doing. Today is the first time I decided to search this problem. My N4 is about 10 months old, is rooted, no ROM, but Franco Kernel and overclocked to 1512. BTW, I also adjusted the overclock speed and tried plugging in direct charge when I get my no wake up problem.
This has been going on for about a month, has been the only reason a reboot has been needed, and is becoming very annoying. I also use wireless charging. I do not know if a complete wipe of the phone getting it back to stock would help, but I really would like to fix this. I want the N5 but realistically I don't need it yet. The N4 is in perfect physical condition, and until recently, very reliable.
So no, you are not alone!
Need help here though!
Thanks all.
Yeah, I have the exact same problem.
wowduk3 said:
Yeah, I have the exact same problem.
Click to expand...
Click to collapse
When did yours start doing it?
Sent using my etch a sketch: Nexus 4
It's weird. It seems to be totally ROM and kernel independent. It also seems it has nothing to do with the governor or clock speed. Neither with the voltage. It happens while on a/c and while on battery. No matter the temperature, too.
Sent from my Nexus 4 using xda app-developers app
I can't believe this issue is so unknown.
I guess I'll have to figure out how to logcat and see if I can find any hints.
Sent from my Nexus 4 using xda app-developers app
Maybe someone who's good at reading logs can shed some light. This is what my log shows from the first time I press power, over pressing it again to turn the half lit screen off to pressing it a third time so it shows up normally.
I/23:48:39.643 PowerManagerService( 669)
Waking up from sleep...
V/23:48:39.653 KeyguardServiceDelegate( 669)
onScreenTurnedOn(showListener = [email protected])
D/23:48:39.663 SurfaceFlinger( 186)
Screen acquired, type=0 flinger=0x2a007450
V/23:48:39.683 KeyguardServiceDelegate( 669)
**** SHOWN CALLED ****
I/23:48:39.683 WindowManager( 669)
Lock screen displayed!
D/23:48:39.803 SurfaceControl( 669)
Excessive delay in unblankDisplay() while turning screen on: 140ms
D/23:48:39.963 dalvikvm( 7401)
GC_CONCURRENT freed 969K, 19% free 22894K/28196K, paused 17ms+4ms, total 114ms
D/23:48:39.963 dalvikvm( 7401)
WAIT_FOR_CONCURRENT_GC blocked 66ms
D/23:48:40.003 dalvikvm( 9852)
GC_CONCURRENT freed 6287K, 27% free 38663K/52716K, paused 5ms+6ms, total 112ms
D/23:48:40.003 dalvikvm( 9852)
WAIT_FOR_CONCURRENT_GC blocked 107ms
D/23:48:40.153 dalvikvm( 7401)
GC_CONCURRENT freed 959K, 19% free 22907K/28196K, paused 3ms+3ms, total 107ms
D/23:48:40.153 dalvikvm( 7401)
WAIT_FOR_CONCURRENT_GC blocked 23ms
D/23:48:40.183 StatsProvider( 7401)
Added Deep sleep:13 h 26 m 45 s (48405 s) Ratio: 44,8%
I/23:48:40.183 StatsProvider( 7401)
rawRealtime = 108063881000
I/23:48:40.183 StatsProvider( 7401)
whichRealtime = 29772601
I/23:48:40.183 ReferenceStore( 7401)
Retrieved reference from cache: Reference ref_unplugged created 21 h 44 m 51 s (Wl: 0 elements; KWl: 25elements; NetS: 46 elements; Alrm: 20 elements; Proc: 0 elements; Oth: 8 elements; CPU: 13 elements)
I/23:48:40.263 InputReader( 669)
Reconfiguring input devices. changes=0x00000004
I/23:48:40.263 InputReader( 669)
Device reconfigured: id=6, name='touch_dev', size 768x1280, orientation 0, mode 1, display id 0
I/23:48:40.273 WindowManager( 669)
Screen frozen for +50ms due to Window{43214818 u0 Keyguard}
D/23:48:40.783 dalvikvm( 1578)
GC_CONCURRENT freed 432K, 27% free 20753K/28196K, paused 3ms+2ms, total 66ms
D/23:48:40.783 dalvikvm( 1578)
WAIT_FOR_CONCURRENT_GC blocked 34ms
D/23:48:40.864 dalvikvm( 1578)
GC_CONCURRENT freed 655K, 27% free 20602K/28196K, paused 2ms+2ms, total 49ms
I/23:48:41.724 PowerManagerService( 669)
Going to sleep by user request...
D/23:48:42.255 SurfaceFlinger( 186)
Screen released, type=0 flinger=0x2a007450
V/23:48:42.265 KeyguardHostView( 9852)
Initial transport state: 0, pbstate=1
D/23:48:42.285 Cleaner ( 2504)
Cleaner check spent 23ms (7ms)
W/23:48:42.415 AppFlood(24647)
login Failed. code = -1
W/23:48:42.415 AppFlood(24647)
connection failed -1 http://data.appflood.com/get_token?...==&signature=175962a267710799bfb726b898d9b942
D/23:48:42.435 SurfaceControl( 669)
Excessive delay in blankDisplay() while turning screen off: 183ms
V/23:48:42.505 KeyguardHostView( 9852)
hide transport, gen:278
V/23:48:42.505 KeyguardHostView( 9852)
music state changed: 1
D/23:48:42.545 dalvikvm( 669)
GC_EXPLICIT freed 2234K, 26% free 40209K/53684K, paused 5ms+12ms, total 261ms
I/23:48:42.685 PowerManagerService( 669)
Waking up from sleep...
V/23:48:42.695 KeyguardServiceDelegate( 669)
onScreenTurnedOn(showListener = [email protected])
D/23:48:42.705 SurfaceFlinger( 186)
Screen acquired, type=0 flinger=0x2a007450
V/23:48:42.785 KeyguardServiceDelegate( 669)
**** SHOWN CALLED ****
I/23:48:42.785 WindowManager( 669)
Lock screen displayed!
D/23:48:42.926 dalvikvm( 7401)
GC_CONCURRENT freed 953K, 19% free 22932K/28196K, paused 4ms+3ms, total 72ms
D/23:48:42.926 dalvikvm( 7401)
WAIT_FOR_CONCURRENT_GC blocked 48ms
D/23:48:43.116 dalvikvm( 7401)
GC_CONCURRENT freed 1163K, 20% free 22754K/28196K, paused 10ms+3ms, total 101ms
D/23:48:43.116 dalvikvm( 7401)
WAIT_FOR_CONCURRENT_GC blocked 27ms
D/23:48:43.126 StatsProvider( 7401)
Added Deep sleep:13 h 26 m 45 s (48405 s) Ratio: 44,8%
I/23:48:43.126 StatsProvider( 7401)
rawRealtime = 108066826000
I/23:48:43.126 StatsProvider( 7401)
whichRealtime = 29775550
I/23:48:43.136 ReferenceStore( 7401)
Retrieved reference from cache: Reference ref_unplugged created 21 h 44 m 51 s (Wl: 0 elements; KWl: 25elements; NetS: 46 elements; Alrm: 20 elements; Proc: 0 elements; Oth: 8 elements; CPU: 13 elements)
D/23:48:43.566 audio_hw_primary(21128)
select_devices: out_snd_device(2: speaker) in_snd_device(0: )
D/23:48:43.566 ACDB-LOADER(21128)
ACDB -> send_afe_cal
D/23:48:43.606 PhoneStatusBar( 9852)
disable: < expand icons alerts ticker system_info back* home* recent* clock* search >
W/23:48:43.666 InputMethodManagerService( 669)
Window already focused, ignoring focus gain of: [email protected] [email protected], token = [email protected]
D/23:48:43.797 audio_hw_primary(21128)
select_devices: out_snd_device(0: ) in_snd_device(34: voice-rec-mic)
E/23:48:43.797 ACDB-LOADER(21128)
Error: ACDB AudProc vol returned = -8
I/23:48:43.797 MicroHotwordRecognitionRunner(29090)
Starting hotword detection.
D/23:48:43.817 dalvikvm( 1578)
GC_CONCURRENT freed 176K, 26% free 20883K/28196K, paused 2ms+8ms, total 133ms
D/23:48:43.817 dalvikvm( 1578)
WAIT_FOR_CONCURRENT_GC blocked 112ms
I/23:48:43.887 SearchController(29090)
#onHotwordDetectorStarted
D/23:48:43.917 dalvikvm( 1578)
GC_CONCURRENT freed 777K, 27% free 20606K/28196K, paused 2ms+2ms,
Click to expand...
Click to collapse
Sent from my Nexus 4 using XDA Free mobile app
My wife's n4 is having the exact same issue and it's a completely stock phone.
If it's the same issue that used to happen with the HTC HD2, then it's probably the power button.
To test this out, enable the option "Volume button wake". That option allows you to wake up the device using the volume buttons (Please note that I have this option inside Carbon settings > buttons, it might not be in stock or it might be in a different place and name depending on the ROM). Now stop using the power button and use the volume button for a while instead to wake up the device, then see if the problem persists.
Edit: Also try using "double tap status bar to sleep" or set the screen timeout to something short (in short, don't use the power button to put the device to sleep)
I'm already using a mod that turns the back button into a power off button on the home screen.
Please note that this only happens if the device is turned off for a longer period. If the device is awake I can repeatedly press the power button and it will react instantly.
It seems to me it happens when the device is in deep sleep. If I press the power button after the screen has been off for let's say an hour the screens backlight will turn on and show a very light whiteish dim but nothing is shown. So I have to press it again to turn it off (screen goes black) and again to turn it on (instantly works then)
Sent from my Nexus 4 using XDA Free mobile app
Oxious119 said:
I'm already using a mod that turns the back button into a power off button on the home screen.
Please note that this only happens if the device is turned off for a longer period. If the device is awake I can repeatedly press the power button and it will react instantly.
It seems to me it happens when the device is in deep sleep. If I press the power button after the screen has been off for let's say an hour the screens backlight will turn on and show a very light whiteish dim but nothing is shown. So I have to press it again to turn it off (screen goes black) and again to turn it on (instantly works then)
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
that is just a wakelock taking longer to execute/finish, had few of those, not a hardware specific thing(even more that our s4 pro can´t even do a full sleep) some app is causing that,for me happens mostly when I have too much apps that synchronize accounts
I've ready tried waiting after the first press (when the display just has a light dim) but it never fully turns on unless I lock and relock it again.
Sent from my Nexus 4 using XDA Free mobile app
Related
Hi all,
the camera on my Glacier appears to be broken. Any "camera related" app I try to launch force closes after a few seconds. This is true for the built-in camera app, for a barcode scanner app and even for a torch app that would use the flash and not really the camera.
I have already cleared the cache and Davlik and have fixed the permissions to no avail. I ran a logcat from launching the camera app until after I clicked the "force close" button:
Code:
I/ActivityManager( 1351): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.camera/.Camera bnds=[96,721][192,800] } from pid 1702
I/ActivityManager( 1351): Start proc com.android.camera for activity com.android.camera/.Camera: pid=3292 uid=10048 gids={1006, 1015}
I/WindowManager( 1351): Setting rotation to 1, animFlags=1
V/CameraHolder( 3292): open camera 0
W/WindowManager( 1351): App freeze timeout expired.
W/WindowManager( 1351): Force clearing freeze: AppWindowToken{40a23298 token=HistoryRecord{40a230d8 com.android.camera/.Camera}}
I/InputDispatcher( 1351): Application is not responding: AppWindowToken{40a23298 token=HistoryRecord{40a230d8 com.android.camera/.Camera}}. 9279.3ms since event, 5004.2ms since wait started
I/WindowManager( 1351): Input event dispatching timed out sending to application AppWindowToken{40a23298 token=HistoryRecord{40a230d8 com.android.camera/.Camera}}
I/Process ( 1351): Sending signal. PID: 3292 SIG: 3
I/dalvikvm( 3292): threadid=4: reacting to signal 3
I/dalvikvm( 3292): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1351): Sending signal. PID: 1351 SIG: 3
I/dalvikvm( 1351): threadid=4: reacting to signal 3
I/dalvikvm( 1351): Wrote stack traces to '/data/anr/traces.txt'
I/Process ( 1351): Sending signal. PID: 1617 SIG: 3
I/dalvikvm( 1617): threadid=4: reacting to signal 3
I/dalvikvm( 1617): Wrote stack traces to '/data/anr/traces.txt'
W/ActivityManager( 1351): Activity idle timeout for HistoryRecord{40a230d8 com.android.camera/.Camera}
I/Process ( 1351): Sending signal. PID: 1572 SIG: 3
D/dalvikvm( 1351): GC_EXPLICIT freed 732K, 38% free 6779K/10823K, external 1561K/2073K, paused 88ms
E/ActivityManager( 1351): ANR in com.android.camera (com.android.camera/.Camera)
E/ActivityManager( 1351): Reason: keyDispatchingTimedOut
E/ActivityManager( 1351): Load: 3.4 / 3.17 / 2.89
E/ActivityManager( 1351): CPU usage from 5627ms to 1ms ago:
E/ActivityManager( 1351): 4.2% 1351/system_server: 3.1% user + 1% kernel / faults: 796 minor
E/ActivityManager( 1351): 3.5% 3050/adbd: 0.1% user + 3.3% kernel
E/ActivityManager( 1351): 2.3% 1245/mediaserver: 0% user + 2.3% kernel
E/ActivityManager( 1351): 2.1% 1572/com.android.systemui: 1.2% user + 0.8% kernel / faults: 1 minor
E/ActivityManager( 1351): 1.7% 1268/logcat2: 0.1% user + 1.5% kernel
E/ActivityManager( 1351): 1.4% 3071/com.google.android.apps.maps: 1% user + 0.3% kernel / faults: 292 minor
E/ActivityManager( 1351): 1.4% 3290/logcat: 0.3% user + 1% kernel
E/ActivityManager( 1351): 0.8% 1249/akmd: 0.3% user + 0.5% kernel
E/ActivityManager( 1351): 0.7% 1252/htc_ebdlogd: 0% user + 0.7% kernel
E/ActivityManager( 1351): 0.3% 6/events/0: 0% user + 0.3% kernel
E/ActivityManager( 1351): 0.3% 921/emmc-qd: 0% user + 0.3% kernel
E/ActivityManager( 1351): 0% 1184/jbd2/mmcblk0p28: 0% user + 0% kernel
E/ActivityManager( 1351): 0% 1658/wpa_supplicant: 0% user + 0% kernel / faults: 11 minor
E/ActivityManager( 1351): 0% 2310/twc.provider: 0% user + 0% kernel / faults: 43 minor
E/ActivityManager( 1351): 0.1% 3292/com.android.camera: 0.1% user + 0% kernel
E/ActivityManager( 1351): 14% TOTAL: 6.9% user + 7.8% kernel
E/ActivityManager( 1351): CPU usage from 297ms to 819ms later:
E/ActivityManager( 1351): 7.4% 1351/system_server: 0% user + 7.4% kernel
E/ActivityManager( 1351): 5.5% 1528/InputDispatcher: 0% user + 5.5% kernel
E/ActivityManager( 1351): 3% 3050/adbd: 1.5% user + 1.5% kernel
E/ActivityManager( 1351): 3% 3050/adbd: 0% user + 3% kernel
E/ActivityManager( 1351): 1.5% 3055/adbd: 1.5% user + 0% kernel
E/ActivityManager( 1351): 1.3% 1245/mediaserver: 0% user + 1.3% kernel
E/ActivityManager( 1351): 1.3% 2450/Binder Thread #: 0% user + 1.3% kernel
E/ActivityManager( 1351): 1.3% 1252/htc_ebdlogd: 0% user + 1.3% kernel
E/ActivityManager( 1351): 1.3% 1268/logcat2: 0% user + 1.3% kernel / faults: 2 minor
E/ActivityManager( 1351): 1.3% 1572/com.android.systemui: 1.3% user + 0% kernel
E/ActivityManager( 1351): 1.3% 1572/ndroid.systemui: 1.3% user + 0% kernel
E/ActivityManager( 1351): 11% TOTAL: 5.7% user + 5.7% kernel
I/InputDispatcher( 1351): Dropping event because the pointer is not down.
I/InputDispatcher( 1351): Dropping event because the pointer is not down.
W/ActivityManager( 1351): Force finishing activity com.android.camera/.Camera
I/Process ( 1351): Sending signal. PID: 3292 SIG: 9
I/ActivityManager( 1351): Killing com.android.camera (pid=3292): user's request
I/ActivityManager( 1351): Process com.android.camera (pid 3292) has died.
W/InputManagerService( 1351): Window already focused, ignoring focus gain of: [email protected]
My next step now would be a factory reset, but before I do that I'd like to see whether anybody's got a better idea. Any help is appreciated.
Thanks.
---------- Post added at 12:51 PM ---------- Previous post was at 12:35 PM ----------
I just did another reboot and launched the camera app, again. On the first attempt the behavior was the same as before: the app force closed after a while. On any subsequent attempts to launch the camera app I now get the error message "Camera Error / Cannot connect to camera".
We need more info. Are you rooted? What rom? What kernel? Any mods, themes? Things like this can break stuff.
If youre rooted and running a custom rom, just reflash the rom from a full wipe.
Sent from my HTC Glacier using xda premium
I would try full wipe and flash the ROM again.
Sent from my HTC Glacier using XDA App
the device is rooted; I am running CM 7.0.3 with kernel 2.6.35.14 demonspeed v9. It's probably the kernel that causing these problems. After re-flashing CM 7.0.3 (thus going back to the kernel that comes with the ROM), the camera started working again ...
Recently the camera on my z just force closes whenever I try to use it, whether its the camera app, or another app that uses the camera, I.e; barcode scanner, this is fairly recent, and I have tried a few different roms, with no success using my camera again, the roms I tried are miui, cm7, and virtuous unity, so I have no idea what is causing the fc's, and was wondering if there's anyone here who can help me?
Sent from my HTC Desire Z using XDA App
are you restoring system data with TB? are you super wiping and clearing all the caches manually before flashes?
Yeah, I have tried a full wipe (system,cache,dalvik?), and a clean rom without restoring anything with TB and I still get the FC issue.
Sent from my HTC Desire Z using XDA App
i suppose it could be hardware related, have you tried any rooted stock roms with a stock kernal etc? See if that works? I know the wrong kernal with the wrong rom will break camera functionality
I haven't tried that, I'll have a look around for one, any you'd reccomend?
Sent from my HTC Desire Z using XDA App
Update, tried a few stock rooted roms here, with the htc kernel, still no camera :/
Could you do a logcat ? At least you would see whats happening when the camera Force Closes?
Good call lol I always read longcat lol
10-15 14:45:31.513 D/dalvikvm(1190): GC_EXPLICIT freed 11K, 50% free 2699K/5379K, external 0K/0K, paused 73ms
10-15 14:45:31.593 D/dalvikvm(1190): GC_EXPLICIT freed <1K, 50% free 2699K/5379K, external 0K/0K, paused 94ms
10-15 14:45:31.633 V/com.miui.camera.Camera(7315): onCreate
10-15 14:45:31.633 I/com.miui.camera.Global(7315): initialize global variables
10-15 14:45:31.633 I/com.miui.camera.Global(7315): DEVICE: vision
10-15 14:45:31.673 D/dalvikvm(1190): GC_EXPLICIT freed <1K, 50% free 2699K/5379K, external 0K/0K, paused 75ms
10-15 14:45:31.713 I/com.miui.camera.CameraGlobal(7315): initialize global variables
10-15 14:45:31.773 V/com.miui.camera.CameraHolder(7315): open 0
10-15 14:45:31.773 V/com.miui.camera.CameraHolder(7315): open camera 0
10-15 14:45:31.913 D/dalvikvm(1387): GC_EXPLICIT freed 157K, 41% free 4671K/7879K, external 0K/0K, paused 47ms
10-15 14:45:41.333 W/ActivityManager(1279): Launch timeout has expired, giving up wake lock!
10-15 14:45:41.523 W/ActivityManager(1279): Activity idle timeout for HistoryRecord{40d02118 com.miui.camera/.Camera}
10-15 14:45:49.561 D/dalvikvm(7278): GC_EXPLICIT freed 133K, 49% free 4282K/8327K, external 1166K/1218K, paused 65ms
10-15 14:45:54.576 D/dalvikvm(1654): GC_EXPLICIT freed 73K, 45% free 3713K/6727K, external 0K/0K, paused 81ms
10-15 14:46:15.001 I/ActivityManager(1279): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.miui.camera/.Camera bnds=[129,128][239,259] } from pid 1387
10-15 14:46:15.161 I/ActivityManager(1279): Start proc com.miui.camera for activity com.miui.camera/.Camera: pid=7327 uid=10036 gids={1006, 1015}
10-15 14:46:15.291 V/com.miui.camera.Camera(7327): onCreate
10-15 14:46:15.291 I/com.miui.camera.Global(7327): initialize global variables
10-15 14:46:15.291 I/com.miui.camera.Global(7327): DEVICE: vision
10-15 14:46:15.321 I/com.miui.camera.CameraGlobal(7327): initialize global variables
10-15 14:46:15.321 V/com.miui.camera.CameraHolder(7327): open 0
10-15 14:46:15.321 V/com.miui.camera.CameraHolder(7327): open camera 0
10-15 14:46:17.824 D/PowerManagerService(1279): reactivateScreenLocksLocked mProxIgnoredBecauseScreenTurnedOff=false
10-15 14:46:22.839 I/InputDispatcher(1279): Application is not responding: AppWindowToken{40d8da38 token=HistoryRecord{40977b98 com.miui.camera/.Camera}}. 5009.7ms since event, 5009.6ms since wait started
10-15 14:46:22.839 I/WindowManager(1279): Input event dispatching timed out sending to application AppWindowToken{40d8da38 token=HistoryRecord{40977b98 com.miui.camera/.Camera}}
10-15 14:46:22.909 I/Process (1279): Sending signal. PID: 7327 SIG: 3
10-15 14:46:22.909 I/dalvikvm(7327): threadid=4: reacting to signal 3
10-15 14:46:22.909 I/dalvikvm(7327): Wrote stack traces to '/data/anr/traces.txt'
10-15 14:46:22.909 I/Process (1279): Sending signal. PID: 1279 SIG: 3
10-15 14:46:22.909 I/dalvikvm(1279): threadid=4: reacting to signal 3
10-15 14:46:22.929 I/dalvikvm(1279): Wrote stack traces to '/data/anr/traces.txt'
10-15 14:46:22.929 I/Process (1279): Sending signal. PID: 1448 SIG: 3
10-15 14:46:22.929 I/dalvikvm(1448): threadid=4: reacting to signal 3
10-15 14:46:22.929 I/dalvikvm(1448): Wrote stack traces to '/data/anr/traces.txt'
10-15 14:46:22.929 I/Process (1279): Sending signal. PID: 1368 SIG: 3
10-15 14:46:22.929 I/dalvikvm(1368): threadid=4: reacting to signal 3
10-15 14:46:22.929 I/dalvikvm(1368): Wrote stack traces to '/data/anr/traces.txt'
10-15 14:46:23.309 D/dalvikvm(1279): GC_EXPLICIT freed 1277K, 30% free 10605K/15047K, external 0K/0K, paused 120ms
10-15 14:46:23.900 E/ActivityManager(1279): ANR in com.miui.camera (com.miui.camera/.Camera)
10-15 14:46:23.900 E/ActivityManager(1279): Reason: keyDispatchingTimedOut
those are the parts of the logcat i have refering camera, if you'd like anymore of said logcat, lemme know!
I'm having a similar issue, but the camera only force closes if I try to use a shooting mode outside of no effect or black and white. All other modes cause a crash
running insertcoin 1.6
barryweston said:
I'm having a similar issue, but the camera only force closes if I try to use a shooting mode outside of no effect or black and white. All other modes cause a crash
running insertcoin 1.6
Click to expand...
Click to collapse
I'd be happy with that, i only ever used normal mode anyway :/
Helo, my nook color running Phiremod 7.1 Stable release. Before I tryed CM9 -> MIUI -> CM7 Nightly 253m. Before install, I cleared system, data, cache and dalvik cache. In any of this releases I have one bug. Nook drammaticaly drain battery, also in sleep mod (~20% for 8 hours), airplane mod doesn't resolve this problem.
Another bug, that battery indicator doesn't appear in tray, only percentage.
If I boot into recovery, and enter key test, there is spam "key 108 presses" or "key 103"
If I connect to device using adb, in logcat I can see this, than device in sleep mod:
Code:
E/TrackChecker( 2217): NO Network
D/ACRA ( 2217): Preferences changed, check if ACRA configuration must change.
E/TrackChecker( 2217): SCHEDULER: Next scheduled time: 16.02.2012 13:45
I/TrackChecker( 2217): Service is destroyed
D/dalvikvm( 2217): GC_EXPLICIT freed 68K, 47% free 3406K/6407K, external 0K/512K, paused 53ms
D/dalvikvm( 1203): GC_CONCURRENT freed 524K, 52% free 3069K/6279K, external 1524K/1922K, paused 7ms+4ms
D/dalvikvm( 1203): GC_CONCURRENT freed 524K, 52% free 3069K/6279K, external 1524K/1922K, paused 6ms+6ms
D/dalvikvm( 1574): GC_CONCURRENT freed 465K, 50% free 3090K/6151K, external 60K/512K, paused 3ms+4ms
D/dalvikvm( 1574): GC_CONCURRENT freed 469K, 50% free 3095K/6151K, external 283K/512K, paused 4ms+25ms
D/dalvikvm( 1203): GC_CONCURRENT freed 531K, 52% free 3069K/6279K, external 1524K/1922K, paused 6ms+6ms
I/TrackChecker( 2217): Service is created
I/TrackChecker( 2217): Service running command: updateAllAuto
E/TrackChecker( 2217): NO Network
D/ACRA ( 2217): Preferences changed, check if ACRA configuration must change.
E/TrackChecker( 2217): SCHEDULER: Next scheduled time: 16.02.2012 13:46
I/TrackChecker( 2217): Service is destroyed
D/dalvikvm( 1203): GC_CONCURRENT freed 529K, 52% free 3069K/6279K, external 1524K/1922K, paused 6ms+4ms
D/dalvikvm( 1203): GC_CONCURRENT freed 524K, 52% free 3069K/6279K, external 1524K/1922K, paused 6ms+4ms
D/dalvikvm( 2156): GC_EXPLICIT freed 21K, 43% free 3616K/6343K, external 0K/0K, paused 56ms
D/dalvikvm( 1574): GC_CONCURRENT freed 470K, 50% free 3108K/6151K, external 340K/512K, paused 4ms+4ms
D/dalvikvm( 1574): GC_CONCURRENT freed 497K, 50% free 3077K/6151K, external 239K/512K, paused 4ms+4ms
D/dalvikvm( 1574): GC_EXPLICIT freed 46K, 51% free 3055K/6151K, external 283K/512K, paused 73ms
D/dalvikvm( 1203): GC_CONCURRENT freed 526K, 52% free 3069K/6279K, external 1524K/1922K, paused 4ms+4ms
I/TrackChecker( 2217): Service is created
I/TrackChecker( 2217): Service running command: updateAllAuto
E/TrackChecker( 2217): NO Network
D/ACRA ( 2217): Preferences changed, check if ACRA configuration must change.
E/TrackChecker( 2217): SCHEDULER: Next scheduled time: 16.02.2012 13:47
I/TrackChecker( 2217): Service is destroyed
D/dalvikvm( 1203): GC_CONCURRENT freed 530K, 52% free 3069K/6279K, external 1524K/1922K, paused 6ms+4ms
D/dalvikvm( 2217): GC_EXPLICIT freed 68K, 47% free 3406K/6407K, external 0K/512K, paused 71ms
D/dalvikvm( 1146): GC_CONCURRENT freed 1679K, 41% free 6288K/10503K, external 3273K/3379K, paused 9ms+9ms
D/dalvikvm( 1203): GC_CONCURRENT freed 524K, 52% free 3069K/6279K, external 1524K/1922K, paused 6ms+6ms
D/dalvikvm( 1574): GC_CONCURRENT freed 465K, 50% free 3090K/6151K, external 60K/512K, paused 4ms+4ms
D/dalvikvm( 1574): GC_CONCURRENT freed 469K, 50% free 3095K/6151K, external 283K/512K, paused 4ms+13ms
D/dalvikvm( 1673): GC_EXTERNAL_ALLOC freed 227K, 46% free 3364K/6215K, external 4793K/4810K, paused 68ms
D/dalvikvm( 1203): GC_CONCURRENT freed 531K, 52% free 3069K/6279K, external 1524K/1922K, paused 6ms+7ms
I/TrackChecker( 2217): Service is created
I/TrackChecker( 2217): Service running command: updateAllAuto
E/TrackChecker( 2217): NO Network
D/ACRA ( 2217): Preferences changed, check if ACRA configuration must change.
E/TrackChecker( 2217): SCHEDULER: Next scheduled time: 16.02.2012 13:48
I/TrackChecker( 2217): Service is destroyed
D/dalvikvm( 1203): GC_CONCURRENT freed 524K, 52% free 3074K/6279K, external 1524K/1922K, paused 6ms+21ms
D/dalvikvm( 1203): GC_CONCURRENT freed 529K, 52% free 3069K/6279K, external 1524K/1922K, paused 6ms+6ms
D/dalvikvm( 1574): GC_CONCURRENT freed 470K, 50% free 3108K/6151K, external 340K/512K, paused 3ms+4ms
D/dalvikvm( 1574): GC_CONCURRENT freed 481K, 50% free 3093K/6151K, external 239K/512K, paused 4ms+10ms
D/dalvikvm( 1203): GC_CONCURRENT freed 531K, 52% free 3069K/6279K, external 1524K/1922K, paused 7ms+6ms
D/dalvikvm( 1574): GC_EXPLICIT freed 62K, 51% free 3055K/6151K, external 283K/512K, paused 48ms
D/dalvikvm( 1203): GC_CONCURRENT freed 524K, 52% free 3069K/6279K, external 1524K/1922K, paused 6ms+4ms
I/TrackChecker( 2217): Service is created
I/TrackChecker( 2217): Service running command: updateAllAuto
E/TrackChecker( 2217): NO Network
D/ACRA ( 2217): Preferences changed, check if ACRA configuration must change.
E/TrackChecker( 2217): SCHEDULER: Next scheduled time: 16.02.2012 13:49
I/TrackChecker( 2217): Service is destroyed
D/dalvikvm( 2217): GC_EXPLICIT freed 68K, 47% free 3406K/6407K, external 0K/512K, paused 58ms
D/dalvikvm( 1203): GC_CONCURRENT freed 530K, 52% free 3069K/6279K, external 1524K/1922K, paused 6ms+4ms
D/dalvikvm( 1146): GC_CONCURRENT freed 1603K, 41% free 6286K/10503K, external 3273K/3379K, paused 10ms+9ms
D/dalvikvm( 1203): GC_CONCURRENT freed 525K, 52% free 3069K/6279K, external 1524K/1922K, paused 4ms+12ms
D/dalvikvm( 1574): GC_CONCURRENT freed 465K, 50% free 3090K/6151K, external 60K/512K, paused 8ms+4ms
D/dalvikvm( 1574): GC_CONCURRENT freed 469K, 50% free 3095K/6151K, external 283K/512K, paused 4ms+24ms
D/dalvikvm( 1203): GC_CONCURRENT freed 525K, 52% free 3069K/6279K, external 1524K/1922K, paused 6ms+4ms
I/TrackChecker( 2217): Service is created
I/TrackChecker( 2217): Service running command: updateAllAuto
E/TrackChecker( 2217): NO Network
D/ACRA ( 2217): Preferences changed, check if ACRA configuration must change.
E/TrackChecker( 2217): SCHEDULER: Next scheduled time: 16.02.2012 13:50
I/TrackChecker( 2217): Service is destroyed
D/dalvikvm( 1203): GC_CONCURRENT freed 524K, 52% free 3069K/6279K, external 1524K/1922K, paused 6ms+4ms
D/dalvikvm( 1203): GC_CONCURRENT freed 530K, 52% free 3069K/6279K, external 1524K/1922K, paused 6ms+5ms
D/dalvikvm( 1574): GC_CONCURRENT freed 470K, 50% free 3108K/6151K, external 340K/512K, paused 4ms+4ms
D/dalvikvm( 1574): GC_CONCURRENT freed 481K, 50% free 3093K/6151K, external 239K/512K, paused 4ms+4ms
D/dalvikvm( 1574): GC_EXPLICIT freed 62K, 51% free 3055K/6151K, external 283K/512K, paused 48ms
D/dalvikvm( 1203): GC_CONCURRENT freed 525K, 52% free 3069K/6279K, external 1524K/1922K, paused 7ms+4ms
I/TrackChecker( 2217): Service is created
I/TrackChecker( 2217): Service running command: updateAllAuto
E/TrackChecker( 2217): NO Network
Is there hardware error or ... ? Help me please
This probably has something to do with running CM9 and then putting a CM7 build on top. While generally formatting the boot isn't something i'd recommend, i've found it to be useful when switching from CM7 to CM9. I would assume this to be true in the opposite direction, but if you're uncomfortable with taking this risk, perhaps you should wait for a second opinion.
After all I format /boot /system /cache /data, back to stock 1.0.0, than update to 1.4.1, no matter what I do, but the power from battery leaks the same.
Can it be hardware issue? And if it is, what exactly can it be? Bad battery or short circuit in usb port?
How can I help myself. Turn off my nook, disassemble it, take battery out, plug in wall outlet, put battery in. Everything works great.
https://www.youtube.com/watch?v=MtYyEeNjKks&feature=youtube_gdata_player
My mums nexus 4 has been making a weird noise for a couple of days now. She was on paranoid android 2.99 when it started. I wiped data factory reset cache and dalvik then installed pa 3.00 and the noise was still there. I then flashed the backup I had made of stock 4.2 and the noise was still there? Pretty weird stuff like. Anyone any ideas what it could be? That's been 3 different roms!
Cheers
Sent from my Nexus 4 using xda premium
The phone still works perfect it just has this annoying noise all time! Check the video
Sent from my Nexus 4 using xda premium
Log cat.
------ beginning of /dev/log/main
I/dalvikvm( 7760): Turning on JNI app bug workarounds for target SDK version 11...
D/dalvikvm( 7760): GC_CONCURRENT freed 91K, 2% free 9156K/9272K, paused 2ms+3ms, total 24ms
W/InputEventReceiver( 7760): Attempted to finish an input event but the input event receiver has already been disposed.
W/InputEventReceiver( 7760): Attempted to finish an input event but the input event receiver has already been disposed.
W/InputEventReceiver( 7760): Attempted to finish an input event but the input event receiver has already been disposed.
D/dalvikvm( 7760): GC_CONCURRENT freed 192K, 3% free 9349K/9568K, paused 1ms+4ms, total 38ms
W/InputEventReceiver( 7760): Attempted to finish an input event but the input event receiver has already been disposed.
D/dalvikvm( 7760): GC_FOR_ALLOC freed 265K, 5% free 9435K/9836K, paused 16ms, total 17ms
I/dalvikvm-heap( 7760): Grow heap (frag case) to 9.387MB for 159760-byte allocation
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 5% free 9591K/9996K, paused 16ms, total 16ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 5% free 9591K/9996K, paused 16ms, total 16ms
I/dalvikvm-heap( 7760): Grow heap (frag case) to 9.540MB for 159760-byte allocation
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 5% free 9747K/10156K, paused 13ms, total 13ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 5% free 9748K/10156K, paused 14ms, total 14ms
I/dalvikvm-heap( 7760): Grow heap (frag case) to 9.693MB for 159760-byte allocation
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 4% free 9904K/10316K, paused 13ms, total 13ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 4% free 9905K/10316K, paused 14ms, total 14ms
I/dalvikvm-heap( 7760): Grow heap (frag case) to 9.846MB for 159760-byte allocation
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 4% free 10061K/10476K, paused 13ms, total 13ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 4% free 10061K/10476K, paused 13ms, total 13ms
I/dalvikvm-heap( 7760): Grow heap (frag case) to 9.999MB for 159760-byte allocation
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 4% free 10217K/10636K, paused 14ms, total 14ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 4% free 10218K/10636K, paused 13ms, total 13ms
I/dalvikvm-heap( 7760): Grow heap (frag case) to 10.152MB for 159760-byte allocation
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 4% free 10374K/10796K, paused 13ms, total 13ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 153K, 6% free 10243K/10796K, paused 13ms, total 13ms
I/dalvikvm-heap( 7760): Grow heap (frag case) to 10.151MB for 133968-byte allocation
D/dalvikvm( 7760): GC_FOR_ALLOC freed 1K, 6% free 10372K/10928K, paused 14ms, total 14ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 158K, 7% free 10215K/10928K, paused 18ms, total 18ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 158K, 7% free 10188K/10928K, paused 13ms, total 13ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 156K, 7% free 10163K/10928K, paused 14ms, total 14ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 156K, 7% free 10250K/10928K, paused 11ms, total 11ms
I/dalvikvm-heap( 7760): Grow heap (frag case) to 10.268MB for 248784-byte allocation
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 7% free 10493K/11172K, paused 12ms, total 12ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 156K, 8% free 10338K/11172K, paused 11ms, total 11ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 156K, 7% free 10425K/11172K, paused 12ms, total 12ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 156K, 7% free 10400K/11172K, paused 12ms, total 12ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 145K, 6% free 10514K/11172K, paused 16ms, total 16ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 134K, 7% free 10463K/11172K, paused 15ms, total 15ms
I/dalvikvm-heap( 7760): Grow heap (frag case) to 10.391MB for 159760-byte allocation
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 7% free 10619K/11332K, paused 13ms, total 13ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 131K, 8% free 10489K/11332K, paused 13ms, total 13ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 243K, 9% free 10402K/11332K, paused 11ms, total 11ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 486K, 10% free 10229K/11332K, paused 12ms, total 12ms
D/dalvikvm( 7760): GC_CONCURRENT freed 374K, 9% free 10323K/11332K, paused 2ms+2ms, total 14ms
W/IInputConnectionWrapper( 7760): showStatusIcon on inactive InputConnection
D/dalvikvm( 7760): GC_CONCURRENT freed 1200K, 16% free 9520K/11332K, paused 4ms+2ms, total 24ms
D/dalvikvm( 7760): WAIT_FOR_CONCURRENT_GC blocked 11ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 34K, 13% free 9955K/11332K, paused 17ms, total 17ms
D/dalvikvm( 7760): GC_CONCURRENT freed <1K, 9% free 10423K/11332K, paused 2ms+2ms, total 19ms
D/dalvikvm( 7760): WAIT_FOR_CONCURRENT_GC blocked 15ms
D/dalvikvm( 7760): GC_CONCURRENT freed <1K, 4% free 10892K/11332K, paused 3ms+2ms, total 27ms
D/dalvikvm( 7760): WAIT_FOR_CONCURRENT_GC blocked 16ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 4% free 11048K/11492K, paused 19ms, total 19ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 4% free 11361K/11812K, paused 16ms, total 16ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 4% free 11673K/12132K, paused 17ms, total 17ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed <1K, 4% free 12142K/12612K, paused 14ms, total 14ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 476K, 7% free 12403K/13268K, paused 15ms, total 16ms
D/dalvikvm( 7760): GC_FOR_ALLOC freed 513K, 7% free 12615K/13516K, paused 13ms, total 13ms
W/InputEventReceiver( 7760): Attempted to finish an input event but the input event receiver has already been disposed.
Sent from my Nexus 4 using xda premium
Re: Nexus 4 weird noise. Video (Fixed It)
My god I can't believe it. She had gotten a new case for her phone that held credit cards. As soon as she opened it up and the credit card was directly behind the noise happened. It was trying to scan the NFC chip in the credit card. Haha!
Sent from my Nexus 4 using xda premium
shenery said:
https://www.youtube.com/watch?v=MtYyEeNjKks&feature=youtube_gdata_player
My mums nexus 4 has been making a weird noise for a couple of days now. She was on paranoid android 2.99 when it started. I wiped data factory reset cache and dalvik then installed pa 3.00 and the noise was still there. I then flashed the backup I had made of stock 4.2 and the noise was still there? Pretty weird stuff like. Anyone any ideas what it could be? That's been 3 different roms!
Cheers
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Your mom installed paranoid android?? That's one cool mom
Sent from my Nexus 4 using Tapatalk 2
Stocks **** so I taught her how to do it. She said its like the difference between vista and windows 7 haha
Sent from my Nexus 4 using xda premium
Hello everybody,
I got a Nexus 4 with CyanogenMod 10.1.3 RC2.
Recently my system freezes and then reboots on a regular basis. I tried to reproduce the failure and it seems to be related to accessing the sd card. A very reliable way to reproduce the crash is:
Connect the device via USB to the PC
Open the SD Card
Select all entries in the root folder of the sd card
Open properties so that the system calculates the folder / file count and the total size
At some point in this calculation android freezes and reboots
But the system also crashes at other occasions. Today it crashed after I took a screenshot of my device and deleted it afterwards using the Gallery App.
Just before the crash my logcat shows:
Code:
09-18 13:38:02.318 D/dalvikvm( 555): GC_EXPLICIT freed 283K, 24% free 12768K/16768K, paused 8ms+6ms, total 119ms
09-18 13:38:02.798 D/dalvikvm( 774): GC_EXPLICIT freed 822K, 74% free 2900K/10884K, paused 1ms+4ms, total 26ms
09-18 13:38:02.978 D/dalvikvm( 555): GC_EXPLICIT freed 114K, 24% free 12762K/16768K, paused 2ms+6ms, total 88ms
09-18 13:38:03.359 D/dalvikvm( 555): GC_EXPLICIT freed 110K, 24% free 12761K/16768K, paused 3ms+4ms, total 73ms
09-18 13:38:03.579 D/dalvikvm( 774): GC_EXPLICIT freed 826K, 74% free 2900K/10884K, paused 2ms+5ms, total 26ms
09-18 13:38:03.749 D/dalvikvm( 555): GC_EXPLICIT freed 109K, 24% free 12761K/16768K, paused 2ms+6ms, total 76ms
09-18 13:38:04.110 D/dalvikvm( 555): GC_EXPLICIT freed 109K, 24% free 12761K/16768K, paused 3ms+6ms, total 78ms
09-18 13:38:04.330 D/dalvikvm( 774): GC_EXPLICIT freed 826K, 74% free 2896K/10884K, paused 2ms+5ms, total 26ms
09-18 13:38:04.510 D/dalvikvm( 555): GC_EXPLICIT freed 108K, 24% free 12762K/16768K, paused 3ms+7ms, total 80ms
09-18 13:38:04.870 D/dalvikvm( 555): GC_EXPLICIT freed 109K, 24% free 12761K/16768K, paused 3ms+7ms, total 78ms
09-18 13:38:05.121 D/dalvikvm( 774): GC_EXPLICIT freed 822K, 74% free 2896K/10884K, paused 1ms+5ms, total 26ms
09-18 13:38:05.291 D/dalvikvm( 555): GC_EXPLICIT freed 119K, 24% free 12762K/16768K, paused 3ms+6ms, total 77ms
09-18 13:38:05.671 D/dalvikvm( 555): GC_EXPLICIT freed 109K, 24% free 12761K/16768K, paused 3ms+6ms, total 79ms
09-18 13:38:05.881 D/dalvikvm( 774): GC_EXPLICIT freed 822K, 74% free 2895K/10884K, paused 2ms+5ms, total 27ms
09-18 13:38:06.062 D/dalvikvm( 555): GC_EXPLICIT freed 108K, 24% free 12762K/16768K, paused 3ms+7ms, total 77ms
09-18 13:38:06.442 D/dalvikvm( 555): GC_EXPLICIT freed 108K, 24% free 12762K/16768K, paused 3ms+6ms, total 79ms
09-18 13:38:06.662 D/dalvikvm( 774): GC_EXPLICIT freed 822K, 74% free 2897K/10884K, paused 2ms+5ms, total 27ms
09-18 13:38:06.832 D/dalvikvm( 555): GC_EXPLICIT freed 108K, 24% free 12762K/16768K, paused 2ms+6ms, total 77ms
You can find the full logcat for the crash attached to this thread.
Does anybody have an idea what could be wrong here? Do I have a broken sd card? Or is it a bug in CM?
Thanks for your help
BassMonkey
BassMonkey87 said:
Hello everybody,
I got a Nexus 4 with CyanogenMod 10.1.3 RC2.
Recently my system freezes and then reboots on a regular basis. I tried to reproduce the failure and it seems to be related to accessing the sd card. A very reliable way to reproduce the crash is:
Connect the device via USB to the PC
Open the SD Card
Select all entries in the root folder of the sd card
Open properties so that the system calculates the folder / file count and the total size
At some point in this calculation android freezes and reboots
But the system also crashes at other occasions. Today it crashed after I took a screenshot of my device and deleted it afterwards using the Gallery App.
Just before the crash my logcat shows:
Code:
09-18 13:38:02.318 D/dalvikvm( 555): GC_EXPLICIT freed 283K, 24% free 12768K/16768K, paused 8ms+6ms, total 119ms
09-18 13:38:02.798 D/dalvikvm( 774): GC_EXPLICIT freed 822K, 74% free 2900K/10884K, paused 1ms+4ms, total 26ms
09-18 13:38:02.978 D/dalvikvm( 555): GC_EXPLICIT freed 114K, 24% free 12762K/16768K, paused 2ms+6ms, total 88ms
09-18 13:38:03.359 D/dalvikvm( 555): GC_EXPLICIT freed 110K, 24% free 12761K/16768K, paused 3ms+4ms, total 73ms
09-18 13:38:03.579 D/dalvikvm( 774): GC_EXPLICIT freed 826K, 74% free 2900K/10884K, paused 2ms+5ms, total 26ms
09-18 13:38:03.749 D/dalvikvm( 555): GC_EXPLICIT freed 109K, 24% free 12761K/16768K, paused 2ms+6ms, total 76ms
09-18 13:38:04.110 D/dalvikvm( 555): GC_EXPLICIT freed 109K, 24% free 12761K/16768K, paused 3ms+6ms, total 78ms
09-18 13:38:04.330 D/dalvikvm( 774): GC_EXPLICIT freed 826K, 74% free 2896K/10884K, paused 2ms+5ms, total 26ms
09-18 13:38:04.510 D/dalvikvm( 555): GC_EXPLICIT freed 108K, 24% free 12762K/16768K, paused 3ms+7ms, total 80ms
09-18 13:38:04.870 D/dalvikvm( 555): GC_EXPLICIT freed 109K, 24% free 12761K/16768K, paused 3ms+7ms, total 78ms
09-18 13:38:05.121 D/dalvikvm( 774): GC_EXPLICIT freed 822K, 74% free 2896K/10884K, paused 1ms+5ms, total 26ms
09-18 13:38:05.291 D/dalvikvm( 555): GC_EXPLICIT freed 119K, 24% free 12762K/16768K, paused 3ms+6ms, total 77ms
09-18 13:38:05.671 D/dalvikvm( 555): GC_EXPLICIT freed 109K, 24% free 12761K/16768K, paused 3ms+6ms, total 79ms
09-18 13:38:05.881 D/dalvikvm( 774): GC_EXPLICIT freed 822K, 74% free 2895K/10884K, paused 2ms+5ms, total 27ms
09-18 13:38:06.062 D/dalvikvm( 555): GC_EXPLICIT freed 108K, 24% free 12762K/16768K, paused 3ms+7ms, total 77ms
09-18 13:38:06.442 D/dalvikvm( 555): GC_EXPLICIT freed 108K, 24% free 12762K/16768K, paused 3ms+6ms, total 79ms
09-18 13:38:06.662 D/dalvikvm( 774): GC_EXPLICIT freed 822K, 74% free 2897K/10884K, paused 2ms+5ms, total 27ms
09-18 13:38:06.832 D/dalvikvm( 555): GC_EXPLICIT freed 108K, 24% free 12762K/16768K, paused 2ms+6ms, total 77ms
You can find the full logcat for the crash attached to this thread.
Does anybody have an idea what could be wrong here? Do I have a broken sd card? Or is it a bug in CM?
Thanks for your help
BassMonkey
Click to expand...
Click to collapse
GC_EXPLICIT is the garbage collector. It frees memory. More about it:
https://sites.google.com/site/pyximanew/blog/androidunderstandingddmslogcatmemoryoutputmessages
abaaaabbbb63 said:
GC_EXPLICIT is the garbage collector. It frees memory.
Click to expand...
Click to collapse
Thank you. I know that this is the garbage collector. But I wonder why it is so excessively triggered by the VM when accessing the meta data of files on the sd card. Is that normal behaviour? If so, a hardware problem seems to be even more likely. Is there a way to scan my sd card for defects?
Or do you have any other idea what could cause this failure of my device?
Thanks
BassMonkey
BassMonkey87 said:
Thank you. I know that this is the garbage collector. But I wonder why it is so excessively triggered by the VM when accessing the meta data of files on the sd card. Is that normal behaviour? If so, a hardware problem seems to be even more likely. Is there a way to scan my sd card for defects?
Or do you have any other idea what could cause this failure of my device?
Thanks
BassMonkey
Click to expand...
Click to collapse
Does it happen on all the ROMs you try?
abaaaabbbb63 said:
Does it happen on all the ROMs you try?
Click to expand...
Click to collapse
So far I only tried with this ROM. But I already experienced this with prior versions of CM. I had 10.1.2 before.
BassMonkey87 said:
So far I only tried with this ROM. But I already experienced this with prior versions of CM. I had 10.1.2 before.
Click to expand...
Click to collapse
Try other ROMs, like stock 4.2.2 rooted, 4.3. If they all do the same, then it's a hardware fault. If they don't, then you need to reinstall your ROM.