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 ...
Related
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 :/
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
I've been fighting on and off wih horrible battery life with this phone ever since I got it. The past 2 months have been horrific. There's just no way of getting deep sleep not using battery. I usually lose about 30-40% over night. I have no idea what the culprit could be.
I don't have the usual culprits installed; Facebook, Google+, Google Search, etc. I have greenify installed and pretty much hybernating anything that I don't use all the time; Gmail, whatsapp.
I've tried countless factory resets. Something, some app is killing my battery. Gsam battery monitor claims Android OS has been awake the most, sent/received some data. Android System says some 1.5h sensor time was used, out of 8h the phone was sleeping doing nothing.
I am at my wits end here. Running CloudyStock 2.5 with simple kernel V6(tried all kernels there are, always the same thing).
HTML:
GSam Labs - Battery Monitor - Export Data
Kernel (Android OS)
Nov 8, 2014 9:33:58 AM
Usage Details
CPU Usage:24m 57s
CPU Usage (Background Only):24m 57s
Keep Awake:1h 22m 8s
Bytes Sent:147.53 KB
Bytes Received:666.28 KB
App UID:0
Wakelock Detail
Included Packages
Included Processes
kworker/u:2H
irq/289-wcd9xxx
migration/3
kworker/u:30
migration/2
vold
migration/1
file-storage
dhd_rxf
jbd2/mmcblk0p25
kthreadd
irq/170-msm_sdc
jbd2/mmcblk0p21
jbd2/mmcblk0p22
bdi-default
ngd_msm_ctrl_ng
kworker/u:1H
debuggerd
kworker/u:22
kworker/u:21
kworker/u:20
kworker/u:26
kworker/u:25
kworker/u:24
kworker/u:23
mmcqd/1rpmb
mdss_fb0
kworker/u:29
jbd2/mmcblk0p14
system
kworker/u:27
kworker/u:28
wl_event_handle
kworker/0:2H
kswapd0
/init
cfinteractive
irq/315-s3404
kcdrom-storaged
kworker/1:3
kworker/1:2
kworker/1:1
flush-179:0
kworker/1:0
kworker/u:3H
healthd
khubd
kworker/3:0H
kworker/u:4H
kworker/3:1
kworker/3:2
dhd_dpc
kworker/3:0
sync_supers
kworker/u:4
kworker/u:3
kworker/u:6
kworker/u:5
kworker/u:8
kworker/u:7
kworker/u:9
kworker/0:4
kworker/u:0
kworker/0:0
kworker/3:1H
kworker/0:1
kworker/u:2
kworker/0:2
kworker/u:1
kworker/0:3
daemonsu:mount:master
daemonsu:master
kworker/1:1H
bnrd
ueventd
dhd_watchdog_th
kworker/2:1H
ksoftirqd/0
ksoftirqd/1
kworker/1:0H
ksoftirqd/2
flush-0:19
ksoftirqd/3
mmcqd/1
kworker/0:1H
netd
zygote
kworker/2:0H
kworker/u:19
kworker/u:18
kworker/u:17
daemonsu:10109
thermal-engine
kworker/u:16
logwrapper
kworker/u:10
kworker/u:11
jbd2/mmcblk0p31
jbd2/mmcblk0p30
kworker/u:14
kworker/u:15
kworker/u:12
kworker/u:13
kworker/2:1
kworker/u:0H
kworker/2:0
kworker/0:0H
jbd2/mmcblk0p35
jbd2/mmcblk0p34
kworker/2:2
I flashed 20D last weekend. I did absolutely nothing on it, no root, nothing. Only whatsapp installed. For 2 days, my battery was fantastic. 48h, 4h screen time on a single charge. Next charge was again horrible, lost 30% overnight. I charged again and stil the same, deep sleep drain. Like I said I did nothing to the phone, only whatsapp installed and some music downloaded with Play Music. This morning I again went back to full stock and I'm having good battery time(but there's nothing on the phone).
I somehow think my internal memory is messed up. I believe once I download stuff and start filling up my storage, my battery goes to crap.
Got my phone back from the service center. Replaced battery. I'm happy cause know I know, I wasn't crazy.
My Nexus 6P lately has been getting really slow after being on for a few days. I ran:
Code:
adb shell
top -m 20 -s rss
And I think it looks unusual that my 'logd' is spinning out of control like this:
Code:
User 6%, System 48%, IOW 10%, IRQ 1%
User 90 + Nice 28 + Sys 928 + Idle 641 + IOW 193 + IRQ 17 + SIRQ 17 = 1914
PID PR CPU% S #THR VSS RSS PCY UID Name
348 3 0% S 7 1263224K 947564K bg logd /system/bin/logd
4866 3 1% S 110 2439336K 131284K fg system system_server
16227 0 0% S 20 1698620K 124780K fg system com.android.settings
6114 2 0% S 47 1725224K 115604K fg u0_a27 com.android.systemui
19588 0 0% S 33 2253364K 89148K bg u0_a29 com.google.android.googlequicksearchbox
7176 0 0% S 238 1826080K 82560K fg u0_a280 com.fitbit.FitbitMobile
14869 1 0% S 100 1723796K 74144K fg u0_a12 com.google.android.gms.persistent
22388 0 1% S 53 1692288K 64760K bg u0_a175 com.facebook.orca
23633 0 2% S 66 1824088K 61444K bg u0_a79 com.facebook.katana
13291 1 0% S 59 1773460K 57124K fg u0_a12 com.google.android.gms
Code:
logcat -g
main: ring buffer is 256Kb (556Mb consumed), max entry is 5120b, max payload is 4076b
system: ring buffer is 256Kb (33Mb consumed), max entry is 5120b, max payload is 4076b
crash: ring buffer is 256Kb (36Kb consumed), max entry is 5120b, max payload is 4076b
Does anyone knows what this means and how I can stop it from happening? It is ruining an otherwise great phone.
After Android 5.0 update Screen Mirroring started causing serious input lag and temperature rise on the phone. Phone screen is mirrored to one of Samsung's 2015 Tizen-based TVs.
Here are the results of my benchmark showing top processes and CPU usage:
IDLE
SCREEN MIRRORING OFF
Code:
User 6%, System 9%, IOW 0%, IRQ 0%
User 30 + Nice 7 + Sys 58 + Idle 511 + IOW 0 + IRQ 0 + SIRQ 5 = 611
PID PR CPU% S #THR VSS RSS PCY UID Name
776 0 6% S 252 2227568K 134500K fg system system_server
21289 3 2% R 1 3672K 1240K shell top
187 3 1% S 1 0K 0K root irq/626-SSP_Int
151 0 1% S 1 0K 0K root spi32765
1838 0 1% S 66 1209048K 60508K fg u0_a14 com.google.android.gms.persistent
1370 0 0% S 47 1933000K 87768K fg u0_a21 com.android.systemui
2375 0 0% S 6 8480K 556K root /system/bin/mpdecision
2286 3 0% S 1 0K 0K root irq/33-cpubw_hw
8102 3 0% S 1 0K 0K root kworker/u:3
7 0 0% D 1 0K 0K root kworker/u:0H
SCREEN MIRRORING ON
Code:
User 12%, System 17%, IOW 0%, IRQ 4%
User 80 + Nice 6 + Sys 117 + Idle 429 + IOW 5 + IRQ 0 + SIRQ 27 = 664
PID PR CPU% S #THR VSS RSS PCY UID Name
316 0 18% S 60 284820K 14976K fg media /system/bin/mediaserver
776 0 4% S 253 2229172K 134908K fg system system_server
20881 3 1% R 1 3672K 1424K shell top
482 0 1% S 1 0K 0K root dhd_dpc
11622 0 1% S 16 1634280K 33112K bg u0_a22 android.process.acore
74 2 1% S 1 0K 0K root kswapd0
187 0 0% S 1 0K 0K root irq/626-SSP_Int
151 0 0% S 1 0K 0K root spi32765
1838 0 0% S 67 1210112K 60828K fg u0_a14 com.google.android.gms.persistent
18747 0 0% S 1 0K 0K root kworker/u:1
PLAYING MOVIE
SCREEN MIRRORING OFF
Code:
User 8%, System 13%, IOW 0%, IRQ 1%
User 53 + Nice 1 + Sys 82 + Idle 461 + IOW 0 + IRQ 0 + SIRQ 7 = 604
PID PR CPU% S #THR VSS RSS PCY UID Name
316 0 8% S 55 334012K 19324K fg media /system/bin/mediaserver
292 0 6% S 17 131540K 4808K fg system /system/bin/surfaceflinger
776 0 2% S 248 2213124K 143412K fg system system_server
15589 3 2% R 1 3672K 1432K shell top
1370 0 0% S 47 1909488K 83184K fg u0_a21 com.android.systemui
12494 3 0% S 1 0K 0K root kworker/u:4
2375 0 0% S 6 8480K 568K root /system/bin/mpdecision
3 0 0% S 1 0K 0K root ksoftirqd/0
553 3 0% D 1 0K 0K root mdss_fb0
15334 3 0% S 1 0K 0K root ksoftirqd/3
SCREEN MIRRORING ON
Code:
User 18%, System 19%, IOW 0%, IRQ 4%
User 134 + Nice 5 + Sys 141 + Idle 425 + IOW 1 + IRQ 0 + SIRQ 35 = 741
PID PR CPU% S #THR VSS RSS PCY UID Name
316 0 26% S 72 362844K 23872K fg media /system/bin/mediaserver
776 3 5% S 252 2215564K 144548K fg system system_server
292 0 2% S 18 157016K 5048K fg system /system/bin/surfaceflinger
482 0 2% S 1 0K 0K root dhd_dpc
16444 3 1% R 1 3672K 1432K shell top
1370 0 0% R 47 1909576K 88600K fg u0_a21 com.android.systemui
2375 0 0% S 6 8480K 568K root /system/bin/mpdecision
6 0 0% D 1 0K 0K root kworker/u:0
12987 0 0% S 1 0K 0K root kworker/u:6
1671 0 0% S 44 1089704K 38472K fg radio com.android.phone
To sum up:
When idle at home non-mirrored, /system/bin/mediaserver don't use or use little CPU. But uses 18% when mirrored to TV.
When playing video in default player non-mirrored, mediaserver use 8%, but uses 26% when mirrored to TV.
I don't know if this was the case before the update, but now videos started to be choppy when mirrored unlike when I first got my S5.
What do you guys think?
So...
No one uses Screen Mirroring on this phone or what? I'd love if someone with older versions tried SM and write down CPU usage.
The phone lags like hell and no one experienced it except me?
nfsk said:
No one uses Screen Mirroring on this phone or what? I'd love if someone with older versions tried SM and write down CPU usage.
The phone lags like hell and no one experienced it except me?
Click to expand...
Click to collapse
It doest not
fahad√√hacker said:
It doest not
Click to expand...
Click to collapse
How much CPU used by mediaserver? Can you please look?