[Q] Screen turns on automagically - reasons? - Galaxy S III Mini Q&A, Help & Troubleshooting

Hello every one.
My S3's screen turns on automatically. While charging, while not charging, while off and charging (battery screen).
Things I did:
Factory Reset
Disabled all aps
Disassembled & Cleaned
Installed SlimRom 4.4
Removed Home as wakeup-key
This didn't help. The only thing I can imagine is that the usb port is kind of damaged, but why the hell does the log not say this?
Here's the log excerpt when putting to sleep mode from logcat.
Code:
08-11 21:41:41.179: I/libblt_hw(1660): Library opened (handle = 6, fd = 50)
08-11 21:41:41.199: I/libblt_hw(2097): Library opened (handle = 0, fd = 198)
08-11 21:41:41.890: D/LightsService(2097): Excessive delay setting light: 148ms
08-11 21:41:41.890: D/SurfaceFlinger(1660): Screen released, type=0 flinger=0x40746450
08-11 21:41:41.930: D/ALPS_COMPASS(2097): INV SENSOR ENABLE 0 -0
08-11 21:41:41.930: I/PowerManagerService(2097): Waking up from sleep...
08-11 21:41:41.960: I/sec_anm_ahi(1663): setParameters() - screen_state=off
08-11 21:41:41.960: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Enter
08-11 21:41:41.960: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Exit
08-11 21:41:42.080: I/libblt_hw(2097): Library closed (handle = 0, fd = 198)
08-11 21:41:42.270: D/PowerManagerService-JNI(2097): Excessive delay in autosuspend_enable() while turning screen off: 382ms
08-11 21:41:42.420: D/PowerManagerService-JNI(2097): Excessive delay in autosuspend_disable() while turning screen on: 152ms
08-11 21:41:42.420: D/SurfaceFlinger(1660): Screen acquired, type=0 flinger=0x40746450
08-11 21:41:42.450: W/View(2204): requestLayout() improperly called by android.widget.TextClock{423ab038 V.ED.... ......ID 0,0-229,129 #7f090008 app:id/large_time_component_1} during layout: running second layout pass
08-11 21:41:42.450: W/View(2204): requestLayout() improperly called by android.widget.TextClock{422e39b8 V.ED.... ......ID 0,0-37,29 #7f09000e app:id/date_component_1} during layout: running second layout pass
08-11 21:41:42.450: W/View(2204): requestLayout() improperly called by android.widget.TextClock{42588d88 V.ED.... ......ID 46,0-70,29 #7f09000f app:id/date_component_2} during layout: running second layout pass
08-11 21:41:42.450: W/View(2204): requestLayout() improperly called by android.widget.TextClock{421d8348 V.ED.... ......ID 79,0-125,29 #7f090010 app:id/date_component_3} during layout: running second layout pass
08-11 21:41:42.450: W/View(2204): requestLayout() improperly called by android.widget.TextView{426f5788 V.ED.... ......ID 51,6-81,39 #7f090035 app:id/collapsed_extension_text} during layout: running second layout pass
08-11 21:41:42.520: D/ALPS_COMPASS(2097): INV SENSOR ENABLE 0 -1
08-11 21:41:42.560: I/sec_anm_ahi(1663): setParameters() - screen_state=on
08-11 21:41:42.560: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Enter
08-11 21:41:42.560: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Exit
08-11 21:41:42.801: I/WindowManager(2097): Lock screen displayed!
08-11 21:41:42.801: D/DisplayPowerController(2097): Unblocked screen on after 802704 ms
08-11 21:41:42.821: I/libblt_hw(1660): Library closed (handle = 6, fd = 50)
08-11 21:41:46.774: I/healthd(1654): battery l=15 v=3 t=33.8 h=2 st=2 c=0 chg=u
08-11 21:41:56.804: I/healthd(1654): battery l=15 v=3 t=33.8 h=2 st=2 c=0 chg=u
08-11 21:42:06.856: I/healthd(1654): battery l=15 v=3 t=33.9 h=2 st=2 c=0 chg=u
08-11 21:42:11.920: I/libblt_hw(1660): Library opened (handle = 6, fd = 50)
08-11 21:42:11.920: I/PowerManagerService(2097): Going to sleep due to screen timeout...
08-11 21:42:11.950: I/libblt_hw(2097): Library opened (handle = 0, fd = 220)
08-11 21:42:12.641: D/LightsService(2097): Excessive delay setting light: 149ms
08-11 21:42:12.641: D/SurfaceFlinger(1660): Screen released, type=0 flinger=0x40746450
08-11 21:42:12.671: D/ALPS_COMPASS(2097): INV SENSOR ENABLE 0 -0
08-11 21:42:12.671: I/PowerManagerService(2097): Waking up from sleep...
08-11 21:42:12.701: I/sec_anm_ahi(1663): setParameters() - screen_state=off
08-11 21:42:12.701: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Enter
08-11 21:42:12.701: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Exit
08-11 21:42:13.022: D/PowerManagerService-JNI(2097): Excessive delay in autosuspend_enable() while turning screen off: 376ms
08-11 21:42:13.172: D/PowerManagerService-JNI(2097): Excessive delay in autosuspend_disable() while turning screen on: 154ms
08-11 21:42:13.172: D/SurfaceFlinger(1660): Screen acquired, type=0 flinger=0x40746450
08-11 21:42:13.342: I/libblt_hw(2097): Library closed (handle = 0, fd = 220)
08-11 21:42:13.362: I/Choreographer(2204): Skipped 37 frames! The application may be doing too much work on its main thread.
08-11 21:42:13.382: W/View(2204): requestLayout() improperly called by android.widget.TextClock{421c3888 V.ED.... ......ID 0,0-229,129 #7f090008 app:id/large_time_component_1} during layout: running second layout pass
08-11 21:42:13.382: W/View(2204): requestLayout() improperly called by android.widget.TextClock{42829518 V.ED.... ......ID 0,0-37,29 #7f09000e app:id/date_component_1} during layout: running second layout pass
08-11 21:42:13.382: W/View(2204): requestLayout() improperly called by android.widget.TextClock{42283310 V.ED.... ......ID 46,0-70,29 #7f09000f app:id/date_component_2} during layout: running second layout pass
08-11 21:42:13.382: W/View(2204): requestLayout() improperly called by android.widget.TextClock{422e1ff8 V.ED.... ......ID 79,0-125,29 #7f090010 app:id/date_component_3} during layout: running second layout pass
08-11 21:42:13.382: W/View(2204): requestLayout() improperly called by android.widget.TextView{421e3c20 V.ED.... ......ID 51,6-81,39 #7f090035 app:id/collapsed_extension_text} during layout: running second layout pass
08-11 21:42:13.442: I/InputDispatcher(2097): Dropped event because input dispatch is disabled.
08-11 21:42:13.462: D/ALPS_COMPASS(2097): INV SENSOR ENABLE 0 -1
08-11 21:42:13.502: I/sec_anm_ahi(1663): setParameters() - screen_state=on
08-11 21:42:13.502: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Enter
08-11 21:42:13.502: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Exit
08-11 21:42:13.652: I/WindowManager(2097): Lock screen displayed!
08-11 21:42:13.652: D/DisplayPowerController(2097): Unblocked screen on after 833550 ms
08-11 21:42:13.662: I/libblt_hw(1660): Library closed (handle = 6, fd = 50)
08-11 21:42:16.895: I/healthd(1654): battery l=15 v=3 t=33.9 h=2 st=2 c=0 chg=u
08-11 21:42:26.925: I/healthd(1654): battery l=15 v=3 t=33.8 h=2 st=2 c=0 chg=u
08-11 21:42:29.618: I/PowerManagerService(2097): Going to sleep by user request...
08-11 21:42:29.628: I/libblt_hw(1660): Library opened (handle = 6, fd = 50)
08-11 21:42:29.648: I/libblt_hw(2097): Library opened (handle = 0, fd = 198)
08-11 21:42:30.318: D/LightsService(2097): Excessive delay setting light: 146ms
08-11 21:42:30.318: D/SurfaceFlinger(1660): Screen released, type=0 flinger=0x40746450
08-11 21:42:30.358: D/ALPS_COMPASS(2097): INV SENSOR ENABLE 0 -0
08-11 21:42:30.358: I/PowerManagerService(2097): Waking up from sleep...
08-11 21:42:30.388: I/sec_anm_ahi(1663): setParameters() - screen_state=off
08-11 21:42:30.388: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Enter
08-11 21:42:30.388: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Exit
08-11 21:42:30.729: D/PowerManagerService-JNI(2097): Excessive delay in autosuspend_enable() while turning screen off: 405ms
08-11 21:42:30.789: I/libblt_hw(2097): Library closed (handle = 0, fd = 198)
08-11 21:42:30.899: D/PowerManagerService-JNI(2097): Excessive delay in autosuspend_disable() while turning screen on: 115ms
08-11 21:42:30.899: D/SurfaceFlinger(1660): Screen acquired, type=0 flinger=0x40746450
08-11 21:42:30.949: I/Choreographer(2204): Skipped 32 frames! The application may be doing too much work on its main thread.
08-11 21:42:30.969: W/View(2204): requestLayout() improperly called by android.widget.TextClock{426bc4a8 V.ED.... ......ID 0,0-229,129 #7f090008 app:id/large_time_component_1} during layout: running second layout pass
08-11 21:42:30.969: W/View(2204): requestLayout() improperly called by android.widget.TextClock{427a5bc0 V.ED.... ......ID 0,0-37,29 #7f09000e app:id/date_component_1} during layout: running second layout pass
08-11 21:42:30.969: W/View(2204): requestLayout() improperly called by android.widget.TextClock{427a61c0 V.ED.... ......ID 46,0-70,29 #7f09000f app:id/date_component_2} during layout: running second layout pass
08-11 21:42:30.969: W/View(2204): requestLayout() improperly called by android.widget.TextClock{427a67a8 V.ED.... ......ID 79,0-125,29 #7f090010 app:id/date_component_3} during layout: running second layout pass
08-11 21:42:30.969: W/View(2204): requestLayout() improperly called by android.widget.TextView{427a7e80 V.ED.... ......ID 51,6-81,39 #7f090035 app:id/collapsed_extension_text} during layout: running second layout pass
08-11 21:42:31.169: I/InputDispatcher(2097): Dropped event because input dispatch is disabled.
08-11 21:42:31.229: D/ALPS_COMPASS(2097): INV SENSOR ENABLE 0 -1
08-11 21:42:31.269: I/sec_anm_ahi(1663): setParameters() - screen_state=on
08-11 21:42:31.269: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Enter
08-11 21:42:31.269: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Exit
08-11 21:42:31.399: I/WindowManager(2097): Lock screen displayed!
08-11 21:42:31.399: D/DisplayPowerController(2097): Unblocked screen on after 851295 ms
08-11 21:42:31.419: I/libblt_hw(1660): Library closed (handle = 6, fd = 50)
08-11 21:42:32.791: I/libblt_hw(1660): Library opened (handle = 6, fd = 50)
08-11 21:42:32.791: I/PowerManagerService(2097): Going to sleep by user request...
08-11 21:42:32.831: I/libblt_hw(2097): Library opened (handle = 0, fd = 222)
08-11 21:42:33.502: D/LightsService(2097): Excessive delay setting light: 149ms
08-11 21:42:33.502: D/LightsService(2097): Excessive delay setting light: 149ms
08-11 21:42:33.502: D/SurfaceFlinger(1660): Screen released, type=0 flinger=0x40746450
08-11 21:42:33.532: D/ALPS_COMPASS(2097): INV SENSOR ENABLE 0 -0
08-11 21:42:33.532: I/PowerManagerService(2097): Waking up from sleep...
08-11 21:42:33.562: I/sec_anm_ahi(1663): setParameters() - screen_state=off
08-11 21:42:33.562: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Enter
08-11 21:42:33.562: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Exit
08-11 21:42:33.782: I/libblt_hw(2097): Library closed (handle = 0, fd = 222)
08-11 21:42:33.892: D/PowerManagerService-JNI(2097): Excessive delay in autosuspend_enable() while turning screen off: 383ms
08-11 21:42:34.052: D/PowerManagerService-JNI(2097): Excessive delay in autosuspend_disable() while turning screen on: 163ms
08-11 21:42:34.052: D/SurfaceFlinger(1660): Screen acquired, type=0 flinger=0x40746450
08-11 21:42:34.072: W/View(2204): requestLayout() improperly called by android.widget.TextClock{42941980 V.ED.... ......ID 0,0-229,129 #7f090008 app:id/large_time_component_1} during layout: running second layout pass
08-11 21:42:34.072: W/View(2204): requestLayout() improperly called by android.widget.TextClock{422e16f8 V.ED.... ......ID 0,0-37,29 #7f09000e app:id/date_component_1} during layout: running second layout pass
08-11 21:42:34.072: W/View(2204): requestLayout() improperly called by android.widget.TextClock{422e1cf8 V.ED.... ......ID 46,0-70,29 #7f09000f app:id/date_component_2} during layout: running second layout pass
08-11 21:42:34.072: W/View(2204): requestLayout() improperly called by android.widget.TextClock{422cd3a0 V.ED.... ......ID 79,0-125,29 #7f090010 app:id/date_component_3} during layout: running second layout pass
08-11 21:42:34.072: W/View(2204): requestLayout() improperly called by android.widget.TextView{422ce930 V.ED.... ......ID 51,6-81,39 #7f090035 app:id/collapsed_extension_text} during layout: running second layout pass
08-11 21:42:34.322: I/InputDispatcher(2097): Dropped event because input dispatch is disabled.
08-11 21:42:34.362: D/ALPS_COMPASS(2097): INV SENSOR ENABLE 0 -1
08-11 21:42:34.402: I/sec_anm_ahi(1663): setParameters() - screen_state=on
08-11 21:42:34.402: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Enter
08-11 21:42:34.402: D/tms_audio_hw/AudioTmsIpc(1663): adev_set_parameters : Exit
08-11 21:42:34.492: I/WindowManager(2097): Lock screen displayed!
08-11 21:42:34.492: D/DisplayPowerController(2097): Unblocked screen on after 854388 ms
08-11 21:42:34.512: I/libblt_hw(1660): Library closed (handle = 6, fd = 50)
08-11 21:42:36.975: I/healthd(1654): battery l=15 v=3 t=33.8 h=2 st=2 c=0 chg=u
Help appreciated. Thanks in advance!
//edit, more info
Kernel and Rom:
http://forum.xda-developers.com/showthread.php?t=2557997
Recovery used:
http://forum.xda-developers.com/showthread.php?t=2678274
Logcat done using bash$ android-sdk-linux/tools/monitor -> save as -> while running new rom.
GT-I8190
Android 4.4.4
Baseband I8190XXAMG4
Kernel 3.0.101-novafusion+
SELinux deactivated

Hi,
yesterday I bend the USB connector up slightly to see wether this is the issue. No luck.
I also did a CWM keytest. Also no luck (everything works fine).
I found out it was dunk into water. After disassembly, I found yellowish salt on the back side. I used isopropyl alcohol to clean it, it's drying today. I just cannot get everything clean, of what looks yellowish.
Any other suggestions please?

If the phone has water damage, then I guess that is most likely to be the problem. All you need is for a "normally open" contact to be intermittantly shorted (perhaps in the screen?), and that could cause the screen to switch on/off. It might help to install a "screen check" app (something that shows you where the screen is being pressed) to see if that show "finger presses" that you're not really making. Sorry I can't be of more help.

jt12345 said:
It might help to install a "screen check" app (something that shows you where the screen is being pressed) to see if that show "finger presses" that you're not really making.
Click to expand...
Click to collapse
Wouldn't explain the screen going on while charging, and as mentioned above, I did this test using CWM recovery.

Same problem: solution?
mampfit said:
Wouldn't explain the screen going on while charging, and as mentioned above, I did this test using CWM recovery.
Click to expand...
Click to collapse
Hi, I've got the same problem with my S3 Mini. I read in some sites that the problem could be a broken pin in the micro USB dock.
I already installed CM 11 but it has been useless. The device "feels" the cable going in and out, and for this reason it turns on and off every 5 seconds: that's because of the broken pin.
The best solution would be if someone could edit a kernel in order to stop this command, to let the device switched off even when the usb cable goes in.
Is there someone that can do this alteration? He could let people save a lot of money.

pietro.currao said:
Hi, I've got the same problem with my S3 Mini. I read in some sites that the problem could be a broken pin in the micro USB dock.
I already installed CM 11 but it has been useless. The device "feels" the cable going in and out, and for this reason it turns on and off every 5 seconds: that's because of the broken pin.
The best solution would be if someone could edit a kernel in order to stop this command, to let the device switched off even when the usb cable goes in.
Is there someone that can do this alteration? He could let people save a lot of money.
Click to expand...
Click to collapse
Or just replace the usb connector.

This worked on my Samsung S3 Mini with Cyanogen Mode 12.1 (Android 5.1.1)
Try this:
Settings --> Buttons --> Home Button: here simply disable "Wake up Device"

Thanks for reply on an old thread, but I don't own the device anymore and i tried what you said.

Related

Galaxy Tab randomly turns off when locking device :(

Hey guys,
I've learnt heaps from this forum so far but this is my first thread.
First off, great forum and thanks for the information
I have a problem with my Tab where when you lock it, sometimes when you go to unlock it the Tab has turned itself off and you have to hold the power button for a long while to turn it back on.
I flashed to JM6 using ODIN and am rooted with Superoneclick method.
Any advice would be greatly appreciated, really annoying.
I've had a similar experience a couple of times with my z4root'd US spec vzw tab. All else stock. Battery charged 50% our more.
Sent from my SCH-I800 using XDA App
Yeh forgot to mention my battery is charged when this happens too.
kangfu84 said:
I have a problem with my Tab where when you lock it, sometimes when you go to unlock it the Tab has turned itself off and you have to hold the power button for a long while to turn it back on.
I flashed to JM6 using ODIN and am rooted with Superoneclick method.
Any advice would be greatly appreciated, really annoying.
Click to expand...
Click to collapse
Had the tab turned itself off - or has it frozen? And you're essentially soft reseting it? Could be an app causing it?
Sent from my Galaxy Tab using XDA App
I had this issue only once recently. When I got to work I found out that the tab didn't want to show unlock display. when i looked closely, I saw very light image (almost like ghost image) of samsung logo. I had to hard restart.
Sent from my GT-P1000 using XDA App
I had this issue Also
Repeated frequently
I tried to hard rest
and still the problem persists
There are apps in the market that can display the log output Android and its apps continuously produce "behind the scenes". One of the best is catlog. Install it and take a look at the log when this is happening (don't worry it keeps a history of the log messages).
With this log I think it must be possible to track down the culprit. If you can't find it post a (text) capture of the log on this forum.
Thanks. I've downloaded logcat and will post back when it happens next.
Sent from my GT-P1000 using Tapatalk
Ok i've managed to simulate when the fault occurs. Its when i lock the Tab while another app is open.
Well, at least it happened everytime i locked the Tab when Logcat was open in the foreground.
Here is the log i got, ive only pasted from where i think it logged i pressed the power button:
12-21 02:47:55.213 E/WindowManager( 2498): Power key is pressed up mShouldTurnOffOnKeyUp:true
12-21 02:47:55.213 D/WindowManager( 2498): I'm tired mEndcallBehavior=0x2
12-21 02:47:55.213 E/WindowManager( 2498): pkgName:com.nolanlawson.logcat
12-21 02:47:55.213 E/WindowManager( 2498): className:com.nolanlawson.logcat.LogcatActivity
12-21 02:47:55.217 I/PowerManagerService( 2498): Ulight 3->0|0
12-21 02:47:55.217 I/PowerManagerService( 2498): Setting target 2: cur=41.0 target=0 delta=-2.7333333 nominalCurrentValue=41
12-21 02:47:55.217 I/PowerManagerService( 2498): Scheduling light animator!
12-21 02:47:55.217 D/KeyInputQueue( 2498): screenCaptureKeyFlag setting 0
12-21 02:47:55.443 I/PowerManagerService( 2498): Light Animator Finished curIntValue=0
12-21 02:47:55.443 I/power ( 2498): *** set_screen_state 0
12-21 02:47:55.443 D/PowerManagerService( 2498): enableLightSensor false
12-21 02:47:55.443 E/SensorManager( 2498): unregisterListener: [email protected]
12-21 02:47:55.443 W/SensorManager( 2498): Delay Candidate Listener 0 Sensor:4 delay:2147483647
12-21 02:47:55.443 W/SensorManager( 2498): Delay Candidate Listener 1 Sensor:4 delay:2147483647
12-21 02:47:55.443 I/Sensors ( 2498): sensors_data_delay handle=4 delay=2147483647 mMinDelay=60
12-21 02:47:55.443 D/Sensors ( 2498): sensors_control_activate active=00000012 sensor=00000010 new_sensors=2 changed=10
12-21 02:47:55.443 W/Sensors ( 2498): close Light sensor
12-21 02:47:55.443 I/Sensors ( 2498): set AK daemon delay=60 fd=66
12-21 02:47:55.451 W/PowerManagerService( 2498): CurLockF mPS:0 mUS=0
12-21 02:47:55.451 W/PowerManagerService( 2498): mPokeLocks.size=0:
12-21 02:47:55.451 D/PowerManagerService( 2498): sendNotificationLocked on=false
12-21 02:47:55.451 D/KeyguardViewMediator( 2498): onScreenTurnedOff(2)
12-21 02:47:55.451 D/KeyguardViewMediator( 2498): doKeyguard: IMSI=505023104565981
12-21 02:47:55.451 I/KeyguardUpdateMonitor( 2498): getSimState() : mSimState=READY
12-21 02:47:55.451 D/KeyguardViewMediator( 2498): doKeyguard: showing the lock screen
12-21 02:47:55.451 D/KeyguardViewMediator( 2498): showLocked
12-21 02:47:55.451 E/SensorManager( 2498): unregisterListener: [email protected]82b3300
12-21 02:47:55.451 W/SensorManager( 2498): Delay Candidate Listener 0 Sensor:1 delay:2147483647
12-21 02:47:55.451 I/Sensors ( 2498): sensors_data_delay handle=1 delay=2147483647 mMinDelay=2147483647
12-21 02:47:55.451 D/Sensors ( 2498): sensors_control_activate active=00000002 sensor=00000002 new_sensors=0 changed=2
12-21 02:47:55.451 W/Sensors ( 2498): Accelerometer closed
12-21 02:47:55.451 W/Sensors ( 2498): Accelerometer go to SLEEP
12-21 02:47:55.451 D/KeyguardViewMediator( 2498): handleShow
12-21 02:47:55.455 E/RingtoneManager( 2498): getRingtone : file:///system/media/audio/ui/Lock.ogg, streamType : -1
12-21 02:47:55.455 V/MediaPlayer-JNI( 2498): native_setup
12-21 02:47:55.455 V/MediaPlayer( 2498): constructor
12-21 02:47:55.455 V/MediaPlayer( 2498): setListener
12-21 02:47:55.455 V/MediaPlayer-JNI( 2498): setDataSource: path /system/media/audio/ui/Lock.ogg
12-21 02:47:55.455 V/MediaPlayer( 2498): setDataSource(/system/media/audio/ui/Lock.ogg)
12-21 02:47:55.471 E/FastDormancy( 2573): [SCREEN_OFF] New FD Time: 5000
12-21 02:47:55.471 D/FastDormancy( 2573): [FD] INTENT ACTION android.intent.action.SCREEN_OFF
12-21 02:47:55.471 D/FastDormancy( 2573): [FD] mIsScreenOn: false
12-21 02:47:55.486 I/Ringtone( 2498): openMediaPlayer() mUri: file:///system/media/audio/ui/Lock.ogg
12-21 02:47:55.486 I/Ringtone( 2498): openMediaPlayer() isMidFile: false
12-21 02:47:55.486 V/MediaPlayer-JNI( 2498): setAudioStreamType: 2
12-21 02:47:55.486 V/MediaPlayer( 2498): MediaPlayer::setAudioStreamType
12-21 02:47:55.486 V/MediaPlayer( 2498): prepare
12-21 02:47:55.486 E/MediaPlayerService( 2401): Client::notify In
12-21 02:47:55.486 E/MediaPlayer( 2498): message received msg=1, ext1=0, ext2=0
12-21 02:47:55.486 V/MediaPlayer( 2498): prepared
12-21 02:47:55.486 V/MediaPlayer( 2498): signal application thread
12-21 02:47:55.486 E/MediaPlayer( 2498): callback application
12-21 02:47:55.486 E/MediaPlayer( 2498): back from callback
12-21 02:47:55.486 V/MediaPlayer( 2498): prepare complete - status=0
12-21 02:47:55.486 V/MediaPlayer-JNI( 2498): native_setup
12-21 02:47:55.486 V/MediaPlayer( 2498): constructor
12-21 02:47:55.486 V/MediaPlayer( 2498): setListener
Any ideas?
Are you using setcpu? I had the same problem when trying to use conservitave or set the minimum to 100mhz. Currently I use ondemand with a minimum of 200mhz
Sent from my SCH-I800 using XDA App
Can you create a longer log? I think the beginning is right.
The log you've made is showing roughly the same enties when I put the tab in standby (i don't have.the power off problem). Maybe some more entries will give some more info. The log you posted shows nothing unusual .
Btw i like the 2nd log entry: ' I'm tired.... '
Yes I use setcpu. I changed my screen off profile to on demand instead of conservative and it doesn't turn off when I lock the tab with catalog in the foreground anymore. Lets hope that was the problem. Thanks!
Sent from my GT-P1000 using Tapatalk
All good now.
I love my Tab
Galaxy Tab turns off afler sleep for a long time
Hello guys.
Recently got Galaxy 2 Tablet (P6210) (just wifi, no gsm or cdma) and it has the same bug - it doesn't wake up after sleep more than 5 hours.(needs long press power button, around 10 sec).
It happens only if battery below 40%. If battery more than 40-50% the tablet wakes up normally.
Playing with "custom power save mode" and "Auto ajust screen power" (may be this feature just specifically for P6200 series) didn't bring good results. Tablet anyway didn't wake up quickly after sleep for a long time if battery below 40%. Make sure after long press power button and wake up tablet has the same % of battery as I left it.
Also I didn't find "setcpu" function as advise TheMasterBaron on last page. Possibly not all tablets have it. If all samsung tablets have this feature I will glad to know where it on P6200 series.
But I got kind of solution which helped me though solution is not best. whatever. Actually idea is not mine but a few weeks playing with it looks like this solution works.
If you will turn off Wi-fi and then tablet will go to sleep doesn't matter how much battery % has on this moment (even 5%) the tablet even after 15 hours sleep wake up quickly.
Any ideas how do Wi-fi interfere during sleep and how to fix it?

[Q] Power Off / Reboot Problem - need help troubleshooting

Hello guys,
I've been having this issue with my O4X for a week now where the phone won't turn off or reboot upon pressing the power button. If I tap on either power off or reboot it seems to be turning off nd the screen goes black, but if you tap on any of the navigation buttons they light up again and if you press on the power button the display comes back again with the powering off message. If I press the power button again on this stage, the power off menu shows again and so on, I have to do a long press of the power button to get the phone to hard reset. I have CatLog installed and BetterBatteryStats but I understand their logs just reset on power off so I'm at a loss to identify any culprits.
I installed Vanir ROM 4.3.1 one week prior to the problem starting.
I searched on the forum but can't seem to see any posts describing a similar problem, so any help would be appreciated. :good:
http://forum.xda-developers.com/showthread.php?t=2274119
This guide explains how you can get a logcat via Computer without needing an app like catlog...
Sent from my Nexus 7 2013 using Tapatalk
Thanks for your assistance, I will look into this and get back with any findings. :good::good::good:
Reboot Catlog
Ok guys, so here's a real-time log of me trying to reboot the phone last night:
http : // paste2 . org / p021zXkg (can't post links yet, sorry)
This is a 10k+ lines long log. As it reaches its end, that is, the actual failed reboot moment, it shows lots of errors related to SQLiteDatabase and Java stuff, as this:
Code:
E/SQLiteDatabase(20604): Failed to open database '/data/data/com.bbm/databases/mixpanel'.
E/SQLiteDatabase(20604): android.database.sqlite.SQLiteException: not an error (code 0): Could not open the database in read/write mode.
E/SQLiteDatabase(20604): at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
E/SQLiteDatabase(20604): at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:209)
E/SQLiteDatabase(20604): at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:193)
E/SQLiteDatabase(20604): at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:463)
E/SQLiteDatabase(20604): at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:185)
E/SQLiteDatabase(20604): at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:177)
E/SQLiteDatabase(20604): at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:804)
E/SQLiteDatabase(20604): at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:789)
E/SQLiteDatabase(20604): at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:694)
E/SQLiteDatabase(20604): at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:901)
E/SQLiteDatabase(20604): at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:235)
E/SQLiteDatabase(20604): at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:224)
E/SQLiteDatabase(20604): at android.database.sqlite.SQLiteOpenHelper.getReadableDatabase(SQLiteOpenHelper.java:188)
E/SQLiteDatabase(20604): at com.b.a.a.g.a(Unknown Source)
E/SQLiteDatabase(20604): at com.b.a.a.d.a(Unknown Source)
E/SQLiteDatabase(20604): at com.b.a.a.d.a(Unknown Source)
E/SQLiteDatabase(20604): at com.b.a.a.d.handleMessage(Unknown Source)
E/SQLiteDatabase(20604): at android.os.Handler.dispatchMessage(Handler.java:99)
E/SQLiteDatabase(20604): at android.os.Looper.loop(Looper.java:137)
E/SQLiteDatabase(20604): at com.b.a.a.c.run(Unknown Source)
The phone is running Vanir ROM 4.3.1, Baseband V20b-EUR-XXX-JUL-17-2013 and Kernel version 3.1.10-CM+
I'd really appreciate your help with this one, as it is a real nuisance.
It's your bbm messaging app causing the problem
Try removing it and try
Try factory data reset if that doesn't work try reflashing your phone since its a custom rom its easier.
If you solve the problem please share solution...
Thanx, Bo
p880 - tapatalk 4
I haven't found a solution yet. I disabled BBM but the phone still can't properly reboot/shutdown after a certain uptime. Here's a new log I just grabbed with BBM disabled: http : // paste2 . org / mgUOAzkE
And here's the excerpt from the final lines until I perform a hard reboot:
Code:
E/WriteScreenOffReferenceService(32517): Destroyed at2014-01-31 00:42:37
I/SmallWidgetProvider(32517): onReceive method called, action = 'BBS_WIDGET_UPDATE' at 2014-01-31 00:42:37
E/SQLiteLog(32517): (3850) statement aborts at 26: [INSERT OR REPLACE INTO samples(ref_blob,ref_label,ref_name,time_created,ref_type) VALUES (?,?,?,?,?)] disk I/O error
E/SQLiteDatabase(32517): Error inserting ref_blob=[[email protected] ref_label=Screen Off ref_name=ref_screen_off time_created=180526284 ref_type=2
E/SQLiteDatabase(32517): android.database.sqlite.SQLiteDiskIOException: disk I/O error (code 3850)
E/SQLiteDatabase(32517): at android.database.sqlite.SQLiteConnection.nativeExecuteForLastInsertedRowId(Native Method)
E/SQLiteDatabase(32517): at android.database.sqlite.SQLiteConnection.executeForLastInsertedRowId(SQLiteConnection.java:782)
E/SQLiteDatabase(32517): at android.database.sqlite.SQLiteSession.executeForLastInsertedRowId(SQLiteSession.java:788)
E/SQLiteDatabase(32517): at android.database.sqlite.SQLiteStatement.executeInsert(SQLiteStatement.java:86)
E/SQLiteDatabase(32517): at android.database.sqlite.SQLiteDatabase.insertWithOnConflict(SQLiteDatabase.java:1469)
E/SQLiteDatabase(32517): at android.database.sqlite.SQLiteDatabase.replace(SQLiteDatabase.java:1385)
E/SQLiteDatabase(32517): at com.asksven.betterbatterystats.data.ReferenceDBHelper.addOrUpdateReference(ReferenceDBHelper.java:259)
E/SQLiteDatabase(32517): at com.asksven.betterbatterystats.data.ReferenceStore.serializeRef(ReferenceStore.java:212)
E/SQLiteDatabase(32517): at com.asksven.betterbatterystats.data.ReferenceStore.access$000(ReferenceStore.java:33)
E/SQLiteDatabase(32517): at com.asksven.betterbatterystats.data.ReferenceStore$1.run(ReferenceStore.java:149)
E/SQLiteDatabase(32517): at java.lang.Thread.run(Thread.java:841)
E/ReferenceDBHelper(32517): Error inserting or updating row
I/ReferenceStore(32517): Saved ref ref_screen_off
E/lights ( 520): YJChae write_int set_light_buttons 16777215
V/Sensors ( 520): int poll__activate(sensors_poll_device_t*, int, int)
V/Sensors ( 520): int sensors_poll_context_t::activate(int, int)
D/Sensors ( 520): Sensor_enable:4 1
V/Sensors ( 520): enable - sensor Accelerometer (handle 4) dis -> en
V/Sensors ( 520): enabled_sensors: 16 dmp_started: 0
V/Sensors ( 520): Starting DMP
W/MPL-9_sup( 520): 9 axis sensor fusion not available - No compass detected.
I/Sensors ( 520): Enabled 9 axis sensor fusion
I/PowerManagerService( 520): Waking up from sleep...
I/MPL-mldl_cfg_mpu:( 520): inv_mpu_resume(,,,,0070) -> 0070
V/Sensors ( 520): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
V/Sensors ( 520): int sensors_poll_context_t::setDelay(int, int64_t)
V/Sensors ( 520): setDelay - sensor Accelerometer (handle 4), rate 200 ms (5.00 Hz)
V/Sensors ( 520): set fifo rate - divider : 39, delay : 200 ms (5.00 Hz)
I/MPL-mldl_cfg_mpu:( 520): inv_mpu_suspend(,,,,7fff) -> 0000
I/MPL-fifo( 520): Actual ODR: 5000 mHz
I/MPL-mldl_cfg_mpu:( 520): inv_mpu_resume(,,,,0070) -> 0070
V/Sensors ( 520): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
V/Sensors ( 520): int sensors_poll_context_t::setDelay(int, int64_t)
V/Sensors ( 520): setDelay - sensor Accelerometer (handle 4), rate 66 ms (15.00 Hz)
V/Sensors ( 520): set fifo rate - divider : 12, delay : 66 ms (15.00 Hz)
I/MPL-mldl_cfg_mpu:( 520): inv_mpu_suspend(,,,,7fff) -> 0000
I/MPL-fifo( 520): Actual ODR: 15384 mHz
I/MPL-mldl_cfg_mpu:( 520): inv_mpu_resume(,,,,0070) -> 0070
V/Sensors ( 520): int poll__activate(sensors_poll_device_t*, int, int)
V/Sensors ( 520): int sensors_poll_context_t::activate(int, int)
D/LightSensor( 520): LightSensor-enable EN(1), newState(1),mEnabled(0)
V/LightSensor( 520): [LIGHT]APDS LIGHT SET ENABLE: flags = 1
V/Sensors ( 520): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
V/Sensors ( 520): int sensors_poll_context_t::setDelay(int, int64_t)
V/Sensors ( 520): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
V/Sensors ( 520): int sensors_poll_context_t::setDelay(int, int64_t)
E/audit_log( 147): Error writing to log file
E/gralloc ( 151): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
V/Sensors ( 520): int poll__activate(sensors_poll_device_t*, int, int)
V/Sensors ( 520): int sensors_poll_context_t::activate(int, int)
D/ProximitySensor( 520): ProximitySensor-enable EN(0), newState(0),mEnabled(1)
V/ProximitySensor( 520): [PROX]APDS PROX SET ENABLE: flags = 0
W/ProximitySensor( 520): ProximitySensor-[setInitialState], value(0.000000)
V/Sensors ( 520): int poll__setDelay(sensors_poll_device_t*, int, int64_t)
V/Sensors ( 520): int sensors_poll_context_t::setDelay(int, int64_t)
E/gralloc ( 151): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
D/PhoneApp( 875): mReceiver: ACTION_SCREEN_OFF / ACTION_SCREEN_ON
D/AccelerometerListener( 875): enable(false)
E/gralloc ( 151): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
V/nvaudio_hw( 9467): nvaudio_dev_set_parameters : screen_state=on
E/gralloc ( 151): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
I/ScreenEventHandler(32517): Received Broadcast ACTION_SCREEN_ON
E/gralloc ( 151): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
I/EventWatcherService(32517): Received start id 712: Intent { cmp=com.asksven.betterbatterystats_xdaedition/com.asksven.betterbatterystats.services.EventWatcherService }
D/YouTube MDX( 2434): Recieved intent android.intent.action.SCREEN_ON
I/WindowManager( 520): Lock screen displayed!
E/gralloc ( 151): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
I/SmallWidgetProvider(32517): onReceive method called, action = 'BBS_WIDGET_UPDATE' at 2014-01-31 00:42:38
D/PowerManagerService-JNI( 520): Excessive delay in autosuspend_disable() while turning screen on: 215ms
D/SurfaceFlinger( 151): Screen acquired, type=0 flinger=0x2a007478
W/ViewRootImpl( 520): Dropping event due to no window focus: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_POWER, scanCode=116, metaState=0, flags=0x8, repeatCount=3, eventTime=87470396, downTime=87469843, deviceId=8, source=0x101 }
W/ViewRootImpl( 520): Dropping event due to no window focus: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_POWER, scanCode=116, metaState=0, flags=0x8, repeatCount=4, eventTime=87470446, downTime=87469843, deviceId=8, source=0x101 }
W/ViewRootImpl( 520): Dropping event due to no window focus: KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_POWER, scanCode=116, metaState=0, flags=0x8, repeatCount=5, eventTime=87470502, downTime=87469843, deviceId=8, source=0x101 }
D/Sensors ( 520): * No Motion *
So, factory data reset or can you guys pinpoint something in there?

WiFi does not turn on, WifiStateMachine failed to load driver?

Recently, whenever I turn on the WiFi on my phone, it immediately flips back off. This issue is intermittent and happens seemingly randomly, persisting for a day or two, after which WiFi will work for a few days and then break again.
I'm running 4.4.4, VZW, completely stock, and I've already tried a factory reset and "safe mode" (without any third-party apps). Rebooting will sometimes stop the problem, but then it will come back.
Here's the logcat from flipping on WiFi:
Code:
D/WifiService( 919): setWifiEnabled: true pid=1533, uid=1000
E/WifiService( 919): Invoking mWifiStateMachine.setWifiEnabled
D/Ulp_jni ( 919): JNI:In update_settings:currentContextType 4, currentGpsSetting 0, currentAgpsSetting 0,currentNetworkProvSetting 0,currentWifiSetting 1,currentBatteryCharging 0,currentEnhLocationServicesSetting 0 currentPipUserSetting 0
W/Settings( 1247): Setting wifi_on has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
W/ContextImpl( 1247): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1252 android.content.ContextWrapper.sendBroadcast:365 com.motorola.motocare.internal.settings.SettingsTrigger$1.onChange:395 android.database.ContentObserver.onChange:129 android.database.ContentObserver$NotificationRunnable.run:180
D/WifiStateMachine( 919): setting operational mode to 1
D/WifiStateMachine( 919): handleMessage: E msg.what=131083
D/WifiStateMachine( 919): processMsg: InitialState
W/Settings( 1247): Setting wifi_on has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
W/ContextImpl( 1247): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1252 android.content.ContextWrapper.sendBroadcast:365 com.motorola.motocare.internal.settings.SettingsTrigger$1.onChange:395 android.database.ContentObserver.onChange:129 android.database.ContentObserver$NotificationRunnable.run:180
D/Checkin ( 2607): publish the event [tag = MOT_DEVICE_STATS_L1 event name = SettingLogs]
D/Checkin ( 2607): publish the event [tag = MOT_DEVICE_STATS_L1 event name = SettingLogs]
E/WifiStateMachine( 919): Failed to load driver
D/WifiStateMachine( 919): setWifiState: unknown state
I/SBar.NetworkController( 1069): onReceive: WifiManager.WIFI_STATE_CHANGED_ACTION Received
D/BluetoothAdapter( 1533): 1106862184: getState() : mService = null. Returning STATE_OFF
D/WifiStateMachine( 919): handleMessage: X
D/WifiStateMachine( 919): handleMessage: E msg.what=131144
D/WifiStateMachine( 919): processMsg: InitialState
D/WifiStateMachine( 919): processMsg: DefaultState
D/WifiStateMachine( 919): handleMessage: X
W/Settings( 1247): Setting wifi_on has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
W/ContextImpl( 1247): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1252 android.content.ContextWrapper.sendBroadcast:365 com.motorola.motocare.internal.settings.SettingsTrigger$1.onChange:395 android.database.ContentObserver.onChange:129 android.database.ContentObserver$NotificationRunnable.run:180
W/Settings( 1247): Setting wifi_on has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
W/ContextImpl( 1247): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1252 android.content.ContextWrapper.sendBroadcast:365 com.motorola.motocare.internal.settings.SettingsTrigger$1.onChange:395 android.database.ContentObserver.onChange:129 android.database.ContentObserver$NotificationRunnable.run:180
D/WifiStateMachine( 919): handleMessage: E msg.what=131085
D/WifiStateMachine( 919): processMsg: InitialState
D/WifiStateMachine( 919): processMsg: DefaultState
D/WifiStateMachine( 919): handleMessage: X
D/WifiStateMachine( 919): handleMessage: E msg.what=131149
D/WifiStateMachine( 919): processMsg: InitialState
D/WifiStateMachine( 919): processMsg: DefaultState
D/WifiStateMachine( 919): setSuspendOptimizations: 2 true
D/WifiStateMachine( 919): mSuspendOptNeedsDisabled 4
D/WifiStateMachine( 919): handleMessage: X
D/WifiStateMachine( 919): handleMessage: E msg.what=131084
D/WifiStateMachine( 919): processMsg: InitialState
D/WifiStateMachine( 919): processMsg: DefaultState
D/WifiStateMachine( 919): handleMessage: X
D/Ulp_jni ( 919): JNI:In update_settings:currentContextType 4, currentGpsSetting 0, currentAgpsSetting 0,currentNetworkProvSetting 0,currentWifiSetting 0,currentBatteryCharging 0,currentEnhLocationServicesSetting 0 currentPipUserSetting 0
D/Checkin ( 2607): publish the event [tag = MOT_DEVICE_STATS_L1 event name = SettingLogs]
D/Checkin ( 2607): publish the event [tag = MOT_DEVICE_STATS_L1 event name = SettingLogs]
I/SBar.NetworkController( 1069): onDataActivity: direction=0
I/GCM ( 1412): GCM message com.google.android.talk 0:1406441801764291%5a5392733fb5fb85
D/WifiService( 919): acquireWifiLockLocked: WifiLock{NlpWifiLock type=2 [email protected]}
D/ConnectivityService( 919): handleInetConditionHoldEnd: net=0, condition=100, published condition=100
I/ModemStatsDSDetect( 1287): onReceive() -Intent { act=android.net.conn.INET_CONDITION_ACTION flg=0x4000010 (has extras) }
I/SBar.NetworkController( 1069): onReceive: ConnectivityManager.INET_CONDITION_ACTION Received
I/SBar.NetworkController( 1069): updateConnectivity: NetworkInfo: NetworkInfo: type: mobile[LTE], state: CONNECTED/CONNECTED, reason: linkPropertiesChanged, extra: VZWINTERNET, roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false, inetCondition= 1
I/ModemStatsDSDetect( 1287): INET_CONDITION=100 ,activeNet=NetworkInfo: type: mobile[LTE], state: CONNECTED/CONNECTED, reason: linkPropertiesChanged, extra: VZWINTERNET, roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
I/ModemStatsDSDetect( 1287): onReceive() - done, currentInetCondition=100
Anyone else experiencing this issue and/or have a fix for it?
terabyte128 said:
Recently, whenever I turn on the WiFi on my phone, it immediately flips back off. This issue is intermittent and happens seemingly randomly, persisting for a day or two, after which WiFi will work for a few days and then break again.
I'm running 4.4.4, VZW, completely stock, and I've already tried a factory reset and "safe mode" (without any third-party apps). Rebooting will sometimes stop the problem, but then it will come back.
Here's the logcat from flipping on WiFi:
Code:
D/WifiService( 919): setWifiEnabled: true pid=1533, uid=1000
E/WifiService( 919): Invoking mWifiStateMachine.setWifiEnabled
D/Ulp_jni ( 919): JNI:In update_settings:currentContextType 4, currentGpsSetting 0, currentAgpsSetting 0,currentNetworkProvSetting 0,currentWifiSetting 1,currentBatteryCharging 0,currentEnhLocationServicesSetting 0 currentPipUserSetting 0
W/Settings( 1247): Setting wifi_on has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
W/ContextImpl( 1247): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1252 android.content.ContextWrapper.sendBroadcast:365 com.motorola.motocare.internal.settings.SettingsTrigger$1.onChange:395 android.database.ContentObserver.onChange:129 android.database.ContentObserver$NotificationRunnable.run:180
D/WifiStateMachine( 919): setting operational mode to 1
D/WifiStateMachine( 919): handleMessage: E msg.what=131083
D/WifiStateMachine( 919): processMsg: InitialState
W/Settings( 1247): Setting wifi_on has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
W/ContextImpl( 1247): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1252 android.content.ContextWrapper.sendBroadcast:365 com.motorola.motocare.internal.settings.SettingsTrigger$1.onChange:395 android.database.ContentObserver.onChange:129 android.database.ContentObserver$NotificationRunnable.run:180
D/Checkin ( 2607): publish the event [tag = MOT_DEVICE_STATS_L1 event name = SettingLogs]
D/Checkin ( 2607): publish the event [tag = MOT_DEVICE_STATS_L1 event name = SettingLogs]
E/WifiStateMachine( 919): Failed to load driver
D/WifiStateMachine( 919): setWifiState: unknown state
I/SBar.NetworkController( 1069): onReceive: WifiManager.WIFI_STATE_CHANGED_ACTION Received
D/BluetoothAdapter( 1533): 1106862184: getState() : mService = null. Returning STATE_OFF
D/WifiStateMachine( 919): handleMessage: X
D/WifiStateMachine( 919): handleMessage: E msg.what=131144
D/WifiStateMachine( 919): processMsg: InitialState
D/WifiStateMachine( 919): processMsg: DefaultState
D/WifiStateMachine( 919): handleMessage: X
W/Settings( 1247): Setting wifi_on has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
W/ContextImpl( 1247): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1252 android.content.ContextWrapper.sendBroadcast:365 com.motorola.motocare.internal.settings.SettingsTrigger$1.onChange:395 android.database.ContentObserver.onChange:129 android.database.ContentObserver$NotificationRunnable.run:180
W/Settings( 1247): Setting wifi_on has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
W/ContextImpl( 1247): Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1252 android.content.ContextWrapper.sendBroadcast:365 com.motorola.motocare.internal.settings.SettingsTrigger$1.onChange:395 android.database.ContentObserver.onChange:129 android.database.ContentObserver$NotificationRunnable.run:180
D/WifiStateMachine( 919): handleMessage: E msg.what=131085
D/WifiStateMachine( 919): processMsg: InitialState
D/WifiStateMachine( 919): processMsg: DefaultState
D/WifiStateMachine( 919): handleMessage: X
D/WifiStateMachine( 919): handleMessage: E msg.what=131149
D/WifiStateMachine( 919): processMsg: InitialState
D/WifiStateMachine( 919): processMsg: DefaultState
D/WifiStateMachine( 919): setSuspendOptimizations: 2 true
D/WifiStateMachine( 919): mSuspendOptNeedsDisabled 4
D/WifiStateMachine( 919): handleMessage: X
D/WifiStateMachine( 919): handleMessage: E msg.what=131084
D/WifiStateMachine( 919): processMsg: InitialState
D/WifiStateMachine( 919): processMsg: DefaultState
D/WifiStateMachine( 919): handleMessage: X
D/Ulp_jni ( 919): JNI:In update_settings:currentContextType 4, currentGpsSetting 0, currentAgpsSetting 0,currentNetworkProvSetting 0,currentWifiSetting 0,currentBatteryCharging 0,currentEnhLocationServicesSetting 0 currentPipUserSetting 0
D/Checkin ( 2607): publish the event [tag = MOT_DEVICE_STATS_L1 event name = SettingLogs]
D/Checkin ( 2607): publish the event [tag = MOT_DEVICE_STATS_L1 event name = SettingLogs]
I/SBar.NetworkController( 1069): onDataActivity: direction=0
I/GCM ( 1412): GCM message com.google.android.talk 0:1406441801764291%5a5392733fb5fb85
D/WifiService( 919): acquireWifiLockLocked: WifiLock{NlpWifiLock type=2 [email protected]}
D/ConnectivityService( 919): handleInetConditionHoldEnd: net=0, condition=100, published condition=100
I/ModemStatsDSDetect( 1287): onReceive() -Intent { act=android.net.conn.INET_CONDITION_ACTION flg=0x4000010 (has extras) }
I/SBar.NetworkController( 1069): onReceive: ConnectivityManager.INET_CONDITION_ACTION Received
I/SBar.NetworkController( 1069): updateConnectivity: NetworkInfo: NetworkInfo: type: mobile[LTE], state: CONNECTED/CONNECTED, reason: linkPropertiesChanged, extra: VZWINTERNET, roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false, inetCondition= 1
I/ModemStatsDSDetect( 1287): INET_CONDITION=100 ,activeNet=NetworkInfo: type: mobile[LTE], state: CONNECTED/CONNECTED, reason: linkPropertiesChanged, extra: VZWINTERNET, roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false
I/ModemStatsDSDetect( 1287): onReceive() - done, currentInetCondition=100
Anyone else experiencing this issue and/or have a fix for it?
Click to expand...
Click to collapse
Notice it says "Failed to load driver".
I would suspect a couple possibilities...
1) your 4.4.4 flash could have been corrupt. Check the MD5 of the 4.4.4 file you downloaded and make sure it matches what it is supposed to. Did you use the OTA update, or the recently posted FXZ?
If this is the case (MD5 doesn't match), download the entire FXZ, and re-flash -- see if the problem is resolved.
Even if the MD5s DO match, it's possible you have a corrupted/damaged filesystem, and FXZing will probably fix it. (This is the MOST likely possibility)
2) are you unlocked? If so, check your /persist folder and make sure this file is inside: WCNSS_qcom_wlan_factory_nv.bin
3) this probably isn't relevant at all, since your log says "failed to load driver", but do you have an atheros-based chipset in your wifi router? Does the issue happen on just one wifi access point, or every AP you try to connect to? I have seen conflicts with certain Atheros-based chipsets not playing nice with other clients.
samwathegreat said:
Notice it says "Failed to load driver".
I would suspect a couple possibilities...
1) your 4.4.4 flash could have been corrupt. Check the MD5 of the 4.4.4 file you downloaded and make sure it matches what it is supposed to. Did you use the OTA update, or the recently posted FXZ?
If this is the case (MD5 doesn't match), download the entire FXZ, and re-flash -- see if the problem is resolved.
Even if the MD5s DO match, it's possible you have a corrupted/damaged filesystem, and FXZing will probably fix it. (This is the MOST likely possibility)
2) are you unlocked? If so, check your /persist folder and make sure this file is inside: WCNSS_qcom_wlan_factory_nv.bin
3) this probably isn't relevant at all, since your log says "failed to load driver", but do you have an atheros-based chipset in your wifi router? Does the issue happen on just one wifi access point, or every AP you try to connect to? I have seen conflicts with certain Atheros-based chipsets not playing nice with other clients.
Click to expand...
Click to collapse
Thanks for your reply! I've tried reflashing from the 4.4.4 system.img file that I found on the forums, which works sometimes but only for a short while before the problem begins to occur again. Is it possible that something within the ROM is causing the driver to become corrupted?
At any rate, I spoke to Verizon and they'll send me a replacement phone. Until then.... I'm going to try flashing system again just for kicks, although it didn't work last time.
Might it help to reflash the radios? Seems kinda risky...
terabyte128 said:
Thanks for your reply! I've tried reflashing from the 4.4.4 system.img file that I found on the forums, which works sometimes but only for a short while before the problem begins to occur again. Is it possible that something within the ROM is causing the driver to become corrupted?
At any rate, I spoke to Verizon and they'll send me a replacement phone. Until then.... I'm going to try flashing system again just for kicks, although it didn't work last time.
Might it help to reflash the radios? Seems kinda risky...
Click to expand...
Click to collapse
Hi,
Did you ever figure this out? Having the same problem. Or was getting a new phone the only thing that helped?

[Q&A][ROM][6.0] CyanogenMod 13 - Unofficial CyanogenMod 13

Q&A for [m7] Unofficial CyanogenMod 13 / Official CyanogenMod 12.1 Nightlies
As I have searched Original Android Development and Q&A forums and haven't found nothing about the thread above and questions related to it, so creating this one. Please use search before posting in here.
cm-13.0-20151219-UNOFFICIAL-m7 bugs
Hi,
A few things about "Unofficial CyanogenMod 13" for HTC One M7 Int. (cm-13.0-20151219-UNOFFICIAL-m7)
1. Cannot change preferred network type from "LTE (recommended)" to 3G or 2G. If I try, it just closes the choice window and that's it. Here is logcat for each choice:
a) 3G:
12-21 09:59:24.642 W/InputMethodManagerService( 602): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
12-21 09:59:24.643 D/NetworkSettings( 1354): onPreferenceChange
12-21 09:59:24.643 D/NetworkSettings( 1354): buttonNetworkMode: 0
12-21 09:59:24.643 D/NetworkSettings( 1354): getPreferredNetworkModeForSubId: phoneNwMode = 9 subId = 1
12-21 09:59:24.666 D/NetworkSettings( 1354): handleSetPreferredNetworkTypeResponse: exception in setting network mode.
12-21 09:59:24.666 D/NetworkSettings( 1354): getPreferredNetworkModeForSubId: phoneNwMode = 9 subId = 1
12-21 09:59:24.666 D/NetworkSettings( 1354): updatePreferredNetworkUIFromDb: settingsNetworkMode = 9
12-21 09:59:24.666 D/NetworkSettings( 1354): isWorldMode=false
12-21 09:59:24.723 W/System ( 1088): ClassLoader referenced unknown path: /system/framework/tcmclient.jar
Click to expand...
Click to collapse
b) 2G:
12-21 09:59:30.415 W/InputMethodManagerService( 602): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
12-21 09:59:30.416 D/NetworkSettings( 1354): onPreferenceChange
12-21 09:59:30.419 D/NetworkSettings( 1354): buttonNetworkMode: 1
12-21 09:59:30.420 D/NetworkSettings( 1354): getPreferredNetworkModeForSubId: phoneNwMode = 9 subId = 1
12-21 09:59:30.440 D/NetworkSettings( 1354): handleSetPreferredNetworkTypeResponse: exception in setting network mode.
12-21 09:59:30.440 D/NetworkSettings( 1354): getPreferredNetworkModeForSubId: phoneNwMode = 9 subId = 1
12-21 09:59:30.440 D/NetworkSettings( 1354): updatePreferredNetworkUIFromDb: settingsNetworkMode = 9
12-21 09:59:30.440 D/NetworkSettings( 1354): isWorldMode=false
Click to expand...
Click to collapse
c) LTE (the same as marked):
12-21 09:59:36.671 W/InputEventReceiver( 1354): Attempted to finish an input event but the input event receiver has already been disposed.
12-21 09:59:36.677 W/InputMethodManagerService( 602): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
12-21 09:59:36.678 D/NetworkSettings( 1354): onPreferenceChange
12-21 09:59:36.678 D/NetworkSettings( 1354): buttonNetworkMode: 9
12-21 09:59:36.678 D/NetworkSettings( 1354): getPreferredNetworkModeForSubId: phoneNwMode = 9 subId = 1
Click to expand...
Click to collapse
2. Get random reboots. One thing I noticed, I get rebooted somewhere about the time when "SMS Backup and Restore" runs a scheduled backup. I get somewhere about 1-3 reboots per days as much as I have been using this ROM.
cm-13.0-20151219-UNOFFICIAL-m7 random reboots
A minute ago happened a random reboot, here's the output of logcat:
12-21 12:56:14.583 E/NetlinkEvent( 221): NetlinkEvent::FindParam(): Parameter 'UID' not found
12-21 12:56:26.837 E/NetlinkEvent( 221): NetlinkEvent::FindParam(): Parameter 'UID' not found
12-21 12:56:36.862 E/NetlinkEvent( 221): NetlinkEvent::FindParam(): Parameter 'UID' not found
12-21 12:56:56.846 E/NetlinkEvent( 221): NetlinkEvent::FindParam(): Parameter 'UID' not found
12-21 12:57:07.062 E/NetlinkEvent( 221): NetlinkEvent::FindParam(): Parameter 'UID' not found
12-21 12:58:34.807 I/perfprofd( 233): initiating profile collection
12-21 12:58:34.844 W/perfprofd( 233): type=1400 audit(0.0:9): avc: denied { write } for name="property_service" dev="tmpfs" ino=7181 scontext=u:rerfprofd:s0 tcontext=ubject_rroperty_socket:s0 tclass=sock_file permissive=0
12-21 12:58:34.858 E/perfprofd( 233): setprop ctl.stop mpdecision failed
Click to expand...
Click to collapse
accesspc said:
A minute ago happened a random reboot, here's the output of logcat:
Click to expand...
Click to collapse
As a workaround done this:
Code:
adb shell su -c setenforce 0
And since then - no more reboots. As a result found these AVC message in DMESG:
Code:
adb shell dmesg | grep -i avc
[33691.839812] type=1400 audit(1450776153.729:35): avc: denied { write } for pid=232 comm="perfprofd" name="property_service" dev="tmpfs" ino=7215 scontext=u:rerfprofd:s0 tcontext=ubject_rroperty_socket:s0 tclass=sock_file permissive=1
[33691.840362] type=1400 audit(1450776153.729:36): avc: denied { connectto } for pid=232 comm="perfprofd" path="/dev/socket/property_service" scontext=u:rerfprofd:s0 tcontext=u:r:init:s0 tclass=unix_stream_socket permissive=1
Click to expand...
Click to collapse
Anybody? Help?
accesspc said:
As a workaround done this:
Code:
adb shell su -c setenforce 0
And since then - no more reboots. As a result found these AVC message in DMESG:
Code:
adb shell dmesg | grep -i avc
Anybody? Help?
Click to expand...
Click to collapse
Seems to be this has been fixed in cm-13.0-20151223-UNOFFICIAL-m7.zip build - no more random reboots, but Preferred network type still can't be changed...
Hello
How smooth is it with this rom?
sacaitu said:
How smooth is it with this rom?
Click to expand...
Click to collapse
Hi, the rom is really quite good, only bugs that I have noticed were:
* after fresh install of Facebook and Messenger they force closed - need to start each app at least once, then delete these files:
** /data/data/com.facebook.katana/lib-xzs/libssl*
** /data/data/com.facebook.orca/lib-xzs/libss*
* Still cannot change Preferred network type, either via settings menu, nor via dialpad *#*#4636#*#*. This is set to auto LTE/3G/2G, which drains battery a lot if connection is not stable (many handovers or switching between LTE and 3G)
Other than that - awesome, fast, pretty
Just installed cm-13.0-20160103-UNOFFICIAL-m7 from http://forum.xda-developers.com/showpost.php?p=64632124&postcount=129.
Installation sequence:
1. TWRP -> Wipe -> Advanced: Dalvik Cache, Cache and System
2. Install cm-13.0-20160103-UNOFFICIAL-m7.zip
3. Install open_gapps-arm-6.0-nano-20151225.zip
4. Flash boot.img from cm-13.0-20160103-UNOFFICIAL-m7.zip
Issues that still persist:
* Flashligh FCs after a few seconds from start
* Camera FCs after picture taken, video capture works fine
* Preferred network type cannot be changed, get the same error as before
Haven't tested Facebook and Messenger, as I did not do a full wipe.
How is the battery life? CM is notorious for bad battery life on this device.
With 5.1 GPE ROM, m7 has a very good battery life, with about 2% per hour drain with normal day use and 0.5% per hour drain at idle at night. Does this ROM close to that?
Also, did you collect logcat for those FCs?
I haven't tested the battery life a lot, because before this CM I was using stock latest rom, so the battery drain is about the same, might tell you more tomorrow.
As for Force Closes, here are logcats (to not clutter the forum, put all logs to pastebin:
Flashlight:
1st try: http://pastebin.com/kE1vvdkd
2ndtry: http://pastebin.com/n5WizzmS
Camera:
1st try: http://pastebin.com/HzLXJVKv
Preferred network type change:
To LTE (the same as selected):
Code:
01-05 12:05:53.466 W/InputEventReceiver( 1379): Attempted to finish an input event but the input event receiver has already been disposed.
01-05 12:05:53.467 W/InputMethodManagerService( 620): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
01-05 12:05:53.473 D/NetworkSettings( 1379): onPreferenceChange
01-05 12:05:53.473 D/NetworkSettings( 1379): buttonNetworkMode: 9
To 3G:
Code:
01-05 12:06:04.297 W/InputEventReceiver( 1379): Attempted to finish an input event but the input event receiver has already been disposed.
01-05 12:06:04.298 W/InputMethodManagerService( 620): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
01-05 12:06:04.307 D/NetworkSettings( 1379): onPreferenceChange
01-05 12:06:04.308 D/NetworkSettings( 1379): buttonNetworkMode: 0
01-05 12:06:04.360 D/NetworkSettings( 1379): handleSetPreferredNetworkTypeResponse: exception in setting network mode.
01-05 12:06:04.372 D/NetworkSettings( 1379): updatePreferredNetworkUIFromDb: settingsNetworkMode = 9
01-05 12:06:04.372 D/NetworkSettings( 1379): isWorldMode=false
To 2G:
Code:
01-05 12:06:08.476 W/InputMethodManagerService( 620): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
01-05 12:06:08.476 D/NetworkSettings( 1379): onPreferenceChange
01-05 12:06:08.482 D/NetworkSettings( 1379): buttonNetworkMode: 1
01-05 12:06:08.508 D/NetworkSettings( 1379): handleSetPreferredNetworkTypeResponse: exception in setting network mode.
01-05 12:06:08.521 D/NetworkSettings( 1379): updatePreferredNetworkUIFromDb: settingsNetworkMode = 9
01-05 12:06:08.522 D/NetworkSettings( 1379): isWorldMode=false
devsk said:
How is the battery life? CM is notorious for bad battery life on this device.
With 5.1 GPE ROM, m7 has a very good battery life, with about 2% per hour drain with normal day use and 0.5% per hour drain at idle at night. Does this ROM close to that?
Also, did you collect logcat for those FCs?
Click to expand...
Click to collapse
Now that you asked about battery drain, I measured about 30 % drop (from 100%) in 12 hours (7 normal usage and 5 night time) which equals to 2,5% per hour. That isn't bad, considering that WiFi always on, made a few calls, used GPS for about 15 minutes, Titanium backup ran at night (backing up 5 Apps) and SMS Backup & Restore at night. Oh, and 5 alarms early in the morning.

Touchscreen working, but no display (Android 6.0.1)

I've had many troubles with my m7 (As you can see from my post history) but everything's been running smoothly lately. I'm trying to flash a marshmallow rom, but they all have the same problem. They boot with the screen working fine, but if the display ever turns off, it never comes back on again. The phone wakes up when the power button is pressed, and you can hear it unlock when you swipe up, but the display never turns on.
Also, when flashing 6.0 roms, I've had to edit the partitions in the updater-script file. The partitions are listed there as being in a directory: /dev/block/platform/msm_sdcc.1/by-name/ which doesn't exist on my phone (There is a by-num directory, but no by-name) so I've had to point them to the mmcblk0p* devices directly. I'm wondering if there could be a similar fix for my screen.
Below is the output of logcat when the screen powers off and on (the full log from boot to screen off is attached):
Code:
02-08 13:08:06.244 617 709 I PowerManagerService: Going to sleep due to power button (uid 1000)...
02-08 13:08:06.252 617 672 I PowerManagerService: Sleeping (uid 1000)...
02-08 13:08:06.267 617 672 I Adreno-EGL: <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 09/02/15, 76f806e, Ibddc658e36
02-08 13:08:06.274 222 1263 W AudioPolicyIntefaceImpl: getOutputForAttr uid 10020 tried to pass itself off as 1000
02-08 13:08:06.274 854 918 W AudioTrack: AUDIO_OUTPUT_FLAG_FAST denied by client; transfer 4, track 44100 Hz, output 48000 Hz
02-08 13:08:06.275 222 783 W AudioFlinger: uid 10020 tried to pass itself off as 1000
02-08 13:08:06.276 222 780 D ALSAStreamOps: setParameters(): keyRouting with device 0x2
02-08 13:08:06.276 222 780 D ALSAStreamOps: setParameters(): keyRouting with device 0x2
02-08 13:08:06.276 222 780 D ALSADevice: route: devices 0x2 in mode 0
02-08 13:08:06.276 222 780 D ALSADevice: No valid input device: 0
02-08 13:08:06.277 222 780 I tfa9887 : tfa9887_power: Set amplifier power to 1
02-08 13:08:06.277 222 780 D alsa_ucm: snd_use_case_set(): uc_mgr 0xb604b600 identifier _enadev value Speaker
02-08 13:08:06.277 222 780 D ALSADevice: switchDevice: mCurTxUCMDevivce None mCurRxDevDevice Speaker
02-08 13:08:06.289 222 779 D ALSADevice: route: devices 0x2 in mode 0
02-08 13:08:06.289 222 779 D ALSADevice: No valid input device: 0
02-08 13:08:06.289 222 779 I tfa9887 : tfa9887_power: Set amplifier power to 1
02-08 13:08:06.289 222 779 D alsa_ucm: snd_use_case_set(): uc_mgr 0xb604b600 identifier _enadev value Speaker
02-08 13:08:06.289 222 779 D ALSADevice: switchDevice: mCurTxUCMDevivce None mCurRxDevDevice Speaker
02-08 13:08:06.289 222 779 D alsa_ucm: snd_use_case_set(): uc_mgr 0xb604b600 identifier _verb value HiFi
02-08 13:08:06.289 222 779 D alsa_ucm: Set mixer controls for Speaker enable 1
02-08 13:08:06.289 222 779 D alsa_ucm: acdb_id 15 cap 1 enable 1
02-08 13:08:06.290 222 779 D alsa_ucm: Set mixer controls for HiFiSpeaker enable 1
02-08 13:08:06.290 222 779 D alsa_ucm: Setting mixer control: MI2S_RX Audio Mixer MultiMedia1, value: 1
02-08 13:08:06.290 222 779 D ALSADevice: close: handle 0xb604fa80 h 0x0
02-08 13:08:06.290 222 779 D ALSADevice: open: handle 0xb604fa80, format 0x2
02-08 13:08:06.290 222 779 D ALSADevice: Device value returned is hw:0,0
02-08 13:08:06.294 211 295 D PermissionCache: checking android.permission.READ_FRAME_BUFFER for uid=1000 => granted (152 us)
02-08 13:08:06.297 222 779 D ALSADevice: handle->format: 0x2
02-08 13:08:06.297 222 779 D ALSADevice: setHardwareParams: reqBuffSize 2048 channels 2 sampleRate 48000
02-08 13:08:06.301 222 779 D ALSADevice: setHardwareParams: buffer_size 16384, period_size 2048, period_cnt 8
02-08 13:08:06.826 617 672 V KeyguardServiceDelegate: onScreenTurnedOff()
02-08 13:08:06.834 617 672 E libEGL : call to OpenGL ES API with no current context (logged once per thread)
02-08 13:08:06.854 617 670 I DisplayManagerService: Display device changed state: "Built-in Screen", OFF
02-08 13:08:06.856 211 211 D SurfaceFlinger: Set power mode=0, type=0 flinger=0xb69a4000
02-08 13:08:06.856 211 211 D qdhwcomposer: hwc_setPowerMode: Setting mode 0 on display: 0
02-08 13:08:07.012 211 211 D qdhwcomposer: hwc_setPowerMode: Done setting mode 0 on display 0
02-08 13:08:07.012 617 828 D SurfaceControl: Excessive delay in setPowerMode(): 158ms
02-08 13:08:07.012 617 828 I QCOM PowerHAL: Got set_interactive hint
02-08 13:08:07.023 222 1263 E bt_a2dp_hw: adev_set_parameters: ERROR: set param called even when stream out is null
02-08 13:08:07.075 617 733 E native : do suspend false
02-08 13:08:07.087 617 733 D WifiConfigStore: No blacklist allowed without epno enabled
02-08 13:08:07.097 854 854 D PhoneStatusBar: disable: < expand ICONS* alerts SYSTEM_INFO* back home recent clock search quick_settings >
02-08 13:08:07.202 854 854 D PhoneStatusBar: disable: < expand ICONS alerts SYSTEM_INFO back HOME* RECENT* clock SEARCH* quick_settings >
02-08 13:08:07.220 222 222 E bt_a2dp_hw: adev_set_parameters: ERROR: set param called even when stream out is null
02-08 13:08:07.223 865 3236 D NfcService: Discovery configuration equal, not updating.
02-08 13:08:07.226 617 733 E native : do suspend true
02-08 13:08:07.535 617 733 D WifiStateMachine: L2Connected CMD_START_SCAN source -2 9, 10 -> obsolete
02-08 13:08:09.517 222 780 D ALSADevice: standby: handle 0xb604fa80 h 0x0
02-08 13:08:09.681 222 780 D alsa_ucm: snd_use_case_set(): uc_mgr 0xb604b600 identifier _verb value Inactive
02-08 13:08:09.682 222 780 D alsa_ucm: Set mixer controls for HiFiSpeaker enable 0
02-08 13:08:09.682 222 780 D alsa_ucm: Setting mixer control: MI2S_RX Audio Mixer MultiMedia1, value: 0
02-08 13:08:09.682 222 780 D alsa_ucm: snd_use_case_set(): uc_mgr 0xb604b600 identifier _disdev value Speaker
02-08 13:08:09.682 222 780 D alsa_ucm: Set mixer controls for Speaker enable 0
02-08 13:08:09.688 222 780 I tfa9887 : tfa9887_power: Set amplifier power to 0
02-08 13:08:12.851 617 733 D WifiStateMachine: L2Connected CMD_START_SCAN source -2 7, 10 -> obsolete
02-08 13:08:16.255 217 659 E NetlinkEvent: NetlinkEvent::FindParam(): Parameter 'UID' not found
02-08 13:08:19.289 617 709 I PowerManagerService: Waking up from sleep (uid 1000)...
02-08 13:08:19.290 617 617 V KeyguardServiceDelegate: onStartedWakingUp()
02-08 13:08:19.292 617 672 I DisplayPowerController: Blocking screen on until initial contents have been drawn.
02-08 13:08:19.292 617 672 V KeyguardServiceDelegate: onScreenTurnedOn(showListener = [email protected])
02-08 13:08:19.294 617 828 I QCOM PowerHAL: Got set_interactive hint
02-08 13:08:19.294 617 670 I DisplayManagerService: Display device changed state: "Built-in Screen", ON
02-08 13:08:19.299 211 211 D SurfaceFlinger: Set power mode=2, type=0 flinger=0xb69a4000
02-08 13:08:19.299 211 211 D qdhwcomposer: hwc_setPowerMode: Setting mode 2 on display: 0
02-08 13:08:19.316 617 1522 V KeyguardServiceDelegate: **** SHOWN CALLED ****
02-08 13:08:19.342 222 783 E bt_a2dp_hw: adev_set_parameters: ERROR: set param called even when stream out is null
02-08 13:08:19.381 865 3252 D NfcService: Discovery configuration equal, not updating.
02-08 13:08:19.410 617 733 E native : do suspend false
02-08 13:08:19.419 617 733 D WifiConfigStore: No blacklist allowed without epno enabled
02-08 13:08:19.436 211 211 D qdhwcomposer: hwc_setPowerMode: Done setting mode 2 on display 0
02-08 13:08:19.440 617 828 D SurfaceControl: Excessive delay in setPowerMode(): 146ms
02-08 13:08:19.463 617 672 I DisplayPowerController: Unblocked screen on after 171 ms
02-08 13:08:19.464 617 672 V KeyguardServiceDelegate: onScreenTurnedOn()
02-08 13:08:23.614 212 1936 E QC-NETMGR-LIB: Received nl msg, recvmsg returned 56
02-08 13:08:23.615 212 594 E QC-NETMGR-LIB: Processing RTM_NEWLINK
02-08 13:08:23.615 212 594 E QC-NETMGR-LIB: Metainfo: Index=22 Family=0 Type=0x1 Change=[0x0] Flags=[0x11043]UP BROADCAST RUNNING MULTICAST LOWER_UP
Any help is very much appreciated
Ok, so the partition issue is due to the old version of TWRP I'm using as a result of some issues from this thread. I've installed TWRP 3.0, but I have no GUI and have to use the command line (from ADB shell). The issues with the screen still remain for marshmallow roms however.

Categories

Resources