So yesterday i was just doing some general browsing on my tablet. I received a warning that my battery was low at 11%. A minute or two later it died so I figured the battery percentage was just in accurate. After I plugged it in and let it charge I tried to turn it on and the tablet boots up just fine, but the screen doesnt turn on at all. No backlight, no anything. It boots up ok since i can feel it vibrate, adb works, and i can hear the chimes for new emails and notifications. I pulled a logcat from the boot up process to see if it tells me anything. In the logcat i keep seeing this line of data show up:
E/hwcomposer( 155): /sys/class/graphics/fb0/device/smartdimmer/enable: open failed: Permission denied
E/hwcomposer( 155): Failed to set initial DIDIM status to enable
D/hwcomposer( 155): Display 0: found 2 modes
W/hwcomposer( 155): Skipping mode with invalid timing (1920 x 1200)
D/hwcomposer( 155): unmatched: 1920 x 1200 @ 59.95 Hz
D/hwcomposer( 155): display type 0: vblank period = 16679218 ns
D/hwcomposer( 155): dc_blank: display 0, [-1 -> 0]
So my question is, is there any chance that it is some sort of software issue not allowing the screen to turn on or I just get the errors due to the screen not working?
Wonder if it would help to hook it up HDMI...then maybe you could check the screen settings???
Related
Seriously... does anyone besides me get super irritated when the G1 shuts the screen off during calls? When you are calling automated lines or checking voicemail it's like the biggest pain in the ass... anyone know of a setting or something to stop the phone from turning screen off during calls?
Closes app you can get now is Shake Awake. It won't keep your screen on, but it will turn it on when you move (shake) the phone http://www.cyrket.com/package/com.maplekeycompany.apps.shake
I have been griping about this very problem for almost a year now. Shake awake is nice, but how about just changing a setting so that the phone screen DOES NOT SLEEP during a call? Anyone know where this would be?
There is no such setting. That question has been asked many times before, I'm sure someone would have worked it out if it was possible.
OK. I think I have found the culprit. This is what happens when the screen is shutting itself off during a call:
D/PhoneApp( 185): updateWakeState: keepScreenOn = false (isRinging false, showingDisc false)
D/SurfaceFlinger( 134): About to give-up screen, flinger = 0x17b200
Just a few changes should do the trick. I'll try to work on this.
You'd be a hero for many people if you figured this out
Looking at PhoneApp.java, this seems to be getting closer:
559 /**
560 * Controls how quickly the screen times out.
561 *
562 * The poke lock controls how long it takes before the screen powers
563 * down, and therefore has no immediate effect when the current
564 * WakeState (see {@link PhoneApp#requestWakeState}) is FULL.
565 * If we're in a state where the screen *is* allowed to turn off,
566 * though, the poke lock will determine the timeout interval (long or
567 * short).
568 *
569 * @param shortPokeLock tells the device the timeout duration to use
570 * before going to sleep
571 * {@link com.android.server.PowerManagerService#SHORT_KEYLIGHT_DELAY}.
572 */
573 /* package */ void setScreenTimeout(ScreenTimeoutDuration duration) {
574 if (DBG) Log.d(LOG_TAG, "setScreenTimeout(" + duration + ")...");
575
576 // make sure we don't set the poke lock repeatedly so that we
577 // avoid triggering the userActivity calls in
578 // PowerManagerService.setPokeLock().
579 if (duration == mPokeLockSetting) {
580 return;
581 }
582 mPokeLockSetting = duration;
583
584 // This is kind of convoluted, but the basic thing to remember is
585 // that the poke lock just sends a message to the screen to tell
586 // it to stay on for a while.
587 // The default is 0, for a long timeout and should be set that way
588 // when we are heading back into a the keyguard / screen off
589 // state, and also when we're trying to keep the screen alive
590 // while ringing. We'll also want to ignore the cheek events
591 // regardless of the timeout duration.
592 // The short timeout is really used whenever we want to give up
593 // the screen lock, such as when we're in call.
594 int pokeLockSetting = LocalPowerManager.POKE_LOCK_IGNORE_CHEEK_EVENTS;
595 switch (duration) {
596 case SHORT:
597 // Set the poke lock to timeout the display after a short
598 // timeout (5s). This ensures that the screen goes to sleep
599 // as soon as acceptably possible after we the wake lock
600 // has been released.
601 if (DBG) Log.d(LOG_TAG, "setting short poke lock");
602 pokeLockSetting |= LocalPowerManager.POKE_LOCK_SHORT_TIMEOUT;
603 break;
604
605 case MEDIUM:
606 // Set the poke lock to timeout the display after a medium
607 // timeout (15s). This ensures that the screen goes to sleep
608 // as soon as acceptably possible after we the wake lock
609 // has been released.
610 if (DBG) Log.d(LOG_TAG, "setting medium poke lock");
611 pokeLockSetting |= LocalPowerManager.POKE_LOCK_MEDIUM_TIMEOUT;
612 break;
613
614 case DEFAULT:
615 default:
616 // set the poke lock to timeout the display after a long
617 // delay by default.
618 // TODO: it may be nice to be able to disable cheek presses
619 // for long poke locks (emergency dialer, for instance).
620 if (DBG) Log.d(LOG_TAG, "reverting to normal long poke lock");
621 break;
622 }
623
624 // Send the request
625 try {
626 mPowerManagerService.setPokeLock(pokeLockSetting, mPokeLockToken, LOG_TAG);
627 } catch (RemoteException e) {
628 }
629 }
Click to expand...
Click to collapse
please please get this done... I'm even willing to donate I really want this... soooooooooooooooo tired of pressing MENU every time I need to get anywhere... and with some of these automated lines it can be like 10+ times each call...
Installing it on my phone now and keeping my fingers crossed...
I think there are more crossed fingers than just yours
derfolo said:
Installing it on my phone now and keeping my fingers crossed...
Click to expand...
Click to collapse
That's one long install. I hope you didn't completely trash your phone
I thought the Power Manager app had an option to keep the screen awake during calls...well at least the trial version DID (before it became a trial version)
damn wish i hadnt erased that ASTRO backup file...
I could be wrong but how can i check if I dont wanna buy the app.
dammit I want this!!! baaaaaaaaaaaad!!!
You should really try the power manager app like someone else mentioned. There is an option for keeping the phone awake, albeit only for 2 mins, but it should do the trick.
Hi all,
Sorry for the delay. I had two birthday parties to attend tonight, and my wife was not going to let me get out of it.
The short story is that my original hack did not work correctly. I incorrectly focused on the SHORT_TIMEOUT, when in fact the one that is happening during calls is the MEDIUM. The bonus is that I think I know what is going on at this point. I will keep trying tomorrow. When I am done, I will have a phone.apk that will replace the current one. oooh.
derfolo said:
Hi all,
Sorry for the delay. I had two birthday parties to attend tonight, and my wife was not going to let me get out of it.
The short story is that my original hack did not work correctly. I incorrectly focused on the SHORT_TIMEOUT, when in fact the one that is happening during calls is the MEDIUM. The bonus is that I think I know what is going on at this point. I will keep trying tomorrow. When I am done, I will have a phone.apk that will replace the current one. oooh.
Click to expand...
Click to collapse
I love you man
oneG said:
I thought the Power Manager app had an option to keep the screen awake during calls...well at least the trial version DID (before it became a trial version)
damn wish i hadnt erased that ASTRO backup file...
I could be wrong but how can i check if I dont wanna buy the app.
Click to expand...
Click to collapse
You'd spend a buck on snickers or coke without even thinking - why not buy .99 app?
But if you want to just test it, you can get it and then return it within 24 hours.
I didn't know it had that feature, but even now that I know it, I don't want a full-blown app just to change screen timeout.
exactly... I don't want an application slowing down my phone all the time and also messing with the boot just to have an option that should be on the phone already and most likely can be sorta easily changed...
Send me a patch when you've got it working and I'll add it to my build if you would like!
cyanogen said:
Send me a patch when you've got it working and I'll add it to my build if you would like!
Click to expand...
Click to collapse
EDIT: Got it done! See my post below for the Phone.apk attachment...
Hello everyone,
I’ve been trying to find a solution for this problem but haven’t found a precise/working solution yet so I thought to ask if someone would have solved or encountered this problem with Samsung Galaxy Tab P1000. My problem is as follows:
My phone got water/moist damage (wine to be precise). The phone still worked fine 2 weeks afterwards but then when some rusting started to happen the problem arrived as well. Now when I connect a charger to the phone it tells: “Charging paused. Battery temperature too high or too low”
When I was searching through the web I found than someone had found a solution for other Samsung phone (he did not mention what model it was), and the solution was as follows:
“I noticed there was some internal phone menus dealing with charging temperature. Using this method I was able to resolve my problem for now:
step 1. *#197328640#
step 2. [9] common
step 3. [1] Batt, Temp
-> next to Batt temp ADC it said 254 for me. Obviously it's incorrect, I think the sensor for the battery temp somehow messed up. Take note of that number.
step 4. Go back to the main menu and select [2] Version Information
step 5. [4] Charging Temperature
step 6. I changed [1] high stop to 255 and [2] high recover to 254.
With those changes, my phone now actually charges off the wall and car charger. Anyways hopefully this helps someone.”
I tried to do this but because this was not Galagy Tab (GT-P1000) I could not find settings for charging temperature to change high stop and high recovery values (Of course did found a lot of other options). By going more through the internet I could find list of phone codes for GT-P1000 and with one code: “*#0228#" (ADC Reading) I was able to get info on what my phone “thinks” the values are:
Voltage: 3734.0 (mV)
ADC: 0
Temperature: -21.0 (‘C)
ADC: 800
VF ADC : 0
Level: 29 (%)
Average Value
Voltage: 0.0 (mV)
ADC: 0
Cal.: 0
Temperature: -21.0 (‘C)
ADC: 810
It basically seems that the temperature probe is damaged due to the moist damage (the base value is lost downwards like > 40 degrees).
So the does anyone know how can I change ADC acceptance values in Galaxy Tab? Or any other solutions for the problem like switching off the temperature indicator or change its base value that I can “jump” it to range where my phone will accept charging. Any other solution rather than buying a new phone would be more than appreciated.
For any advice, thank you in advance.
-Antti
AnttiSoininen said:
Hello everyone,
I’ve been trying to find a solution for this problem but haven’t found a precise/working solution yet so I thought to ask if someone would have solved or encountered this problem with Samsung Galaxy Tab P1000. My problem is as follows:
My phone got water/moist damage (wine to be precise). The phone still worked fine 2 weeks afterwards but then when some rusting started to happen the problem arrived as well. Now when I connect a charger to the phone it tells: “Charging paused. Battery temperature too high or too low”
When I was searching through the web I found than someone had found a solution for other Samsung phone (he did not mention what model it was), and the solution was as follows:
“I noticed there was some internal phone menus dealing with charging temperature. Using this method I was able to resolve my problem for now:
step 1. *#197328640#
step 2. [9] common
step 3. [1] Batt, Temp
-> next to Batt temp ADC it said 254 for me. Obviously it's incorrect, I think the sensor for the battery temp somehow messed up. Take note of that number.
step 4. Go back to the main menu and select [2] Version Information
step 5. [4] Charging Temperature
step 6. I changed [1] high stop to 255 and [2] high recover to 254.
With those changes, my phone now actually charges off the wall and car charger. Anyways hopefully this helps someone.”
I tried to do this but because this was not Galagy Tab (GT-P1000) I could not find settings for charging temperature to change high stop and high recovery values (Of course did found a lot of other options). By going more through the internet I could find list of phone codes for GT-P1000 and with one code: “*#0228#" (ADC Reading) I was able to get info on what my phone “thinks” the values are:
Voltage: 3734.0 (mV)
ADC: 0
Temperature: -21.0 (‘C)
ADC: 800
VF ADC : 0
Level: 29 (%)
Average Value
Voltage: 0.0 (mV)
ADC: 0
Cal.: 0
Temperature: -21.0 (‘C)
ADC: 810
It basically seems that the temperature probe is damaged due to the moist damage (the base value is lost downwards like > 40 degrees).
So the does anyone know how can I change ADC acceptance values in Galaxy Tab? Or any other solutions for the problem like switching off the temperature indicator or change its base value that I can “jump” it to range where my phone will accept charging. Any other solution rather than buying a new phone would be more than appreciated.
For any advice, thank you in advance.
-Antti
Click to expand...
Click to collapse
Hi Antti, I am just curious, how do you know your sensor is damaged and it has rusted? It may be caused by malfunction of the processor detecting from the temperature of the battery.
Secondly, your level 29% doesn't tally with 3734.0mV. Theoretically, when battery reaches almost zero, it should read close to 3200mV, fully charge it should be 4200mV. I am assuming that this is the battery percentage indication for your battery, please do a check on by going > Settings=>About Device=>Status and check battery level. If it is 29%, your battery status has gone "crazy" and so does your temperature readings.
Just leave a feedback if you have such an issue.
AnttiSoininen said:
Hello everyone,
I’ve been trying to find a solution for this problem but haven’t found a precise/working solution yet so I thought to ask if someone would have solved or encountered this problem with Samsung Galaxy Tab P1000. My problem is as follows:
My phone got water/moist damage (wine to be precise). The phone still worked fine 2 weeks afterwards but then when some rusting started to happen the problem arrived as well. Now when I connect a charger to the phone it tells: “Charging paused. Battery temperature too high or too low”
When I was searching through the web I found than someone had found a solution for other Samsung phone (he did not mention what model it was), and the solution was as follows:
“I noticed there was some internal phone menus dealing with charging temperature. Using this method I was able to resolve my problem for now:
step 1. *#197328640#
step 2. [9] common
step 3. [1] Batt, Temp
-> next to Batt temp ADC it said 254 for me. Obviously it's incorrect, I think the sensor for the battery temp somehow messed up. Take note of that number.
step 4. Go back to the main menu and select [2] Version Information
step 5. [4] Charging Temperature
step 6. I changed [1] high stop to 255 and [2] high recover to 254.
With those changes, my phone now actually charges off the wall and car charger. Anyways hopefully this helps someone.”
I tried to do this but because this was not Galagy Tab (GT-P1000) I could not find settings for charging temperature to change high stop and high recovery values (Of course did found a lot of other options). By going more through the internet I could find list of phone codes for GT-P1000 and with one code: “*#0228#" (ADC Reading) I was able to get info on what my phone “thinks” the values are:
Voltage: 3734.0 (mV)
ADC: 0
Temperature: -21.0 (‘C)
ADC: 800
VF ADC : 0
Level: 29 (%)
Average Value
Voltage: 0.0 (mV)
ADC: 0
Cal.: 0
Temperature: -21.0 (‘C)
ADC: 810
It basically seems that the temperature probe is damaged due to the moist damage (the base value is lost downwards like > 40 degrees).
So the does anyone know how can I change ADC acceptance values in Galaxy Tab? Or any other solutions for the problem like switching off the temperature indicator or change its base value that I can “jump” it to range where my phone will accept charging. Any other solution rather than buying a new phone would be more than appreciated.
For any advice, thank you in advance.
-Antti
Click to expand...
Click to collapse
so did you fixed it?
AnttiSoininen said:
Hello everyone,
I’ve been trying to find a solution for this problem but haven’t found a precise/working solution yet so I thought to ask if someone would have solved or encountered this problem with Samsung Galaxy Tab P1000. My problem is as follows:
My phone got water/moist damage (wine to be precise). The phone still worked fine 2 weeks afterwards but then when some rusting started to happen the problem arrived as well. Now when I connect a charger to the phone it tells: “Charging paused. Battery temperature too high or too low”
When I was searching through the web I found than someone had found a solution for other Samsung phone (he did not mention what model it was), and the solution was as follows:
“I noticed there was some internal phone menus dealing with charging temperature. Using this method I was able to resolve my problem for now:
step 1. *#197328640#
step 2. [9] common
step 3. [1] Batt, Temp
-> next to Batt temp ADC it said 254 for me. Obviously it's incorrect, I think the sensor for the battery temp somehow messed up. Take note of that number.
step 4. Go back to the main menu and select [2] Version Information
step 5. [4] Charging Temperature
step 6. I changed [1] high stop to 255 and [2] high recover to 254.
With those changes, my phone now actually charges off the wall and car charger. Anyways hopefully this helps someone.”
I tried to do this but because this was not Galagy Tab (GT-P1000) I could not find settings for charging temperature to change high stop and high recovery values (Of course did found a lot of other options). By going more through the internet I could find list of phone codes for GT-P1000 and with one code: “*#0228#" (ADC Reading) I was able to get info on what my phone “thinks” the values are:
Voltage: 3734.0 (mV)
ADC: 0
Temperature: -21.0 (‘C)
ADC: 800
VF ADC : 0
Level: 29 (%)
Average Value
Voltage: 0.0 (mV)
ADC: 0
Cal.: 0
Temperature: -21.0 (‘C)
ADC: 810
It basically seems that the temperature probe is damaged due to the moist damage (the base value is lost downwards like > 40 degrees).
So the does anyone know how can I change ADC acceptance values in Galaxy Tab? Or any other solutions for the problem like switching off the temperature indicator or change its base value that I can “jump” it to range where my phone will accept charging. Any other solution rather than buying a new phone would be more than appreciated.
For any advice, thank you in advance.
-Antti
Click to expand...
Click to collapse
reflash with stock rom and test again for me that is a problem with hardware...
Help
I have the same problem , any one can help me?
Sam
for me i try to buy new charger at first ok. the temp problem gone. but another come out
when it says battery full when i unplug the charger it went down to 65 or 70 then i need to plug it again after few hours say 2 hour it will indicate again battery full
at this time its really full
i am facing the same problem right now.
notification: charging problem. battery temperature too high or too low.
battery status (*#0228):
current value:-
voltage: 3739.0 (mV)
adc: 0
temperature: 7.0 ('C)
adc: 0
vf adc: 0
level: 72%
actually my phone got splashed with water and i found out that the water got into the speaker when i open the back cover, i can see (a little) water.
some suggestion on how to fix this error? maybe some software or hardware modification?
update 26/06/12:
- my gtab haven't charged for 2 days now. last night i power off, then just this afternoon i power on it back to see the status. last night battery level is >20%, when it power on just now, is says only 8%, checking *#0228#
voltage: 3832.0 (mV)
temperature: 41.9 ('C)
level: 10%
- i think the water on the motherboard/battery has dry (remarks, saltwater) and now the circuit/electronic/battery is back to normal.
- if anything wrong again i update it here.
Accessing menus?
Sorry but I must not have seen the correct page or forum yet, but where do you enter this :
battery status (*#0228):
I need to change the battery charging temperature on my gt-p1000r but I don't seem to be able to access any place to do this.
I have rooted it. And I have tried to enter various codes into memo with out any success. Just need a little help or direction with this one.
Thanks,
Need to set my battery charging temperature
jasoncummer said:
Sorry but I must not have seen the correct page or forum yet, but where do you enter this :
battery status (*#0228):
I need to change the battery charging temperature on my gt-p1000r but I don't seem to be able to access any place to do this.
I have rooted it. And I have tried to enter various codes into memo with out any success. Just need a little help or direction with this one.
Thanks,
Click to expand...
Click to collapse
Just a bump I still haven't had a response from any of the forums I've posted on.
any one have a Samsung technical repair line I can call?
A little bump in this old post.
Let me know if anyone had a work around
Sent from my GT-I9300T using Tapatalk 2
Hi,
My proximity sensor of HTC desire Z behaving incorrectly. And I can't make it correct.
Whenever I move my hand over proximity sensor, the screen goes black. I need to push the power button to turn on the screen again. Searched all over the place but found no solution regarding this. Please help.
I've got this log using DDMS.
D/PowerManagerService(1361): setScreenStateLocked++, on: false, err: 0
D/PowerManagerService(1361): mProximityListener.onSensorChanged active: true
D/SensorService(1361): noteStopSensor: uid = 0x3e8, handle = 0x4
D/PowerManagerService(1361): setScreenStateLocked, turn off the button light
D/lights(1361): set_light_buttons_func: on=0 brightness=0
D/PowerManagerService(1361): mProximityListener.onSensorChanged active: false
D/AlarmManager(1361): ACTION_SCREEN_OFF
W/InputManagerService(1361): Receive : Intent.ACTION_SCREEN_OFF
D/UsbnetService(1361): BroadcastReceiver:nReceive+
D/UsbnetService(1361): onReceive SCREEN_OFF
D/Background traffic light(1493): traffic light: GREEN, mBackgroundTrafficLight = false
D/SurfaceFlinger(1361): About to give-up screen, flinger = 0x2f6830
D/AutoSetting(14491): service - mBroadcastReceiver: action = com.htc.content.Intent.ACTION_BACKGROUND_OP_GO
D/AutoSetting(14491): service - mBroadcastReceiver: action = android.intent.action.SCREEN_OFF
Click to expand...
Click to collapse
Hello guys,
I have a problem with my camera.
When i enter camera app or any other camera related app i get:
Warning "Camera auto recovering".
I have no live view, but if i'm quick enough like i have 4 -5 seconds to press record i get image and video is recording.
also i can make pictures in that 4-5 seconds interval.
Sometimes Random I get live preview and everything works normal!
When i go to *#0*# in megacam
i get: Warning "camera failed"
This is what i get in ADB(logcat :*W):
Code:
E/SecCameraHardware( 1912): FimcV4l2 poll: error 0
W/SecCameraHardware( 1912): nativeGetPreview: warning, ESD Shock(0). Reset the camera device (10)
E/ISecCameraHardware( 1912): previewThread: error, nativeGetPreview
E/SecCameraCoreManager( 1912): notifyErrorCallback(1, 1010, 0)
E/SecCamera-JNI-Java(15002): Error 1010
W/SecCameraHardware( 1912): nativeStopPreview ++++++++
W/SecCameraHardware( 1912): nativeStopPreview ---------
W/ISecCameraHardware( 1912): stopPreview: warning, preview has been stopped
E/ISecCameraHardware( 1912): CAMERA power off noti. HAL is completely released
E/ISecCameraHardware( 1912): preview window is NULL!
W/AudioFlinger( 1912): session id 369 not found for pid 1912
W/AudioFlinger( 1912): session id 370 not found for pid 1912
W/AudioFlinger( 1912): session id 371 not found for pid 1912
I appreciate any help.
Device?
As it say in title my N5's Screen Randomly Turn off & Flicker in Dark (any ROM..stock 6.0.1/Pure nexus/AOSPA 7.1)
after sceen goes off it doesn't wake by power button or any other means till either i turn on the light in room or force reboot by holding power button.
Important things to consider :
Random (mostly happens on Browsing, Streaming video in chrome, FB , News apps But never happened in YouTube or MX Player while playing video)
Only happens in Dark (it never happened in Day)
Can easily wake the sceen once i turn on light in room but there is no other way to turns it on in Dark once it goes off.
Some times Screen flickers before going off (not always)
from this points i tend to believe it's related to proximity sensor but tried checking it's working via some apps and they shows it's working perfectly.
even tried resting proximity data via EFS backup still no luck.
if you know something about this issue kindly help
Thanks in advance
i have the same problem.
i onlin turn on the image when disconnect the baterry for 2 or 3 minutes, but nothing resolve the problem.
i chainge the lcd but not resolve the problema.
jineshpatel30 said:
As it say in title my N5's Screen Randomly Turn off & Flicker in Dark (any ROM..stock 6.0.1/Pure nexus/AOSPA 7.1)
after sceen goes off it doesn't wake by power button or any other means till either i turn on the light in room or force reboot by holding power button.
Important things to consider :
Random (mostly happens on Browsing, Streaming video in chrome, FB , News apps But never happened in YouTube or MX Player while playing video)
Only happens in Dark (it never happened in Day)
Can easily wake the sceen once i turn on light in room but there is no other way to turns it on in Dark once it goes off.
Some times Screen flickers before going off (not always)
from this points i tend to believe it's related to proximity sensor but tried checking it's working via some apps and they shows it's working perfectly.
even tried resting proximity data via EFS backup still no luck.
if you know something about this issue kindly help
Thanks in advance
Click to expand...
Click to collapse
@devs Kindly check logs in attachment and help me in finding exact culprit for this problem (with possible solution )
this type of entries are present all over the logs (i don't know if it's relevant to this issue or not)
Code:
07-31 00:19:30.312 I/WindowManager( 752): Screen frozen for +223ms due to Window{1c3e4be u0 NavigationBar}
07-31 00:19:31.630 I/ActivityManager( 752): Waited long enough for: ServiceRecord{834a3ca u0 com.whatsapp/.messaging.MessageService}
07-31 00:21:19.461 I/PowerManagerService( 752): Going to sleep due to power button (uid 1000)...
07-31 00:21:20.088 I/DisplayManagerService( 752): Display device changed state: "Built-in Screen", OFF
07-31 00:21:20.363 I/PowerManagerService( 752): Sleeping (uid 1000)...
07-31 00:21:20.493 I/ActivityManager( 752): Config changes=480 {1.0 404mcc57mnc en_IN ldltr sw360dp w360dp h576dp 480dpi nrml port finger -keyb/v/h -nav/h as.1 s.9}
07-31 00:21:20.573 I/PowerManagerService( 752): Waking up from sleep (uid 1000)...
07-31 00:21:20.589 I/DisplayPowerController( 752): Blocking screen on until initial contents have been drawn.
07-31 00:21:20.668 I/DisplayManagerService( 752): Display device changed state: "Built-in Screen", ON
07-31 00:21:20.865 D/PowerManagerService( 752): acquireWakeLock: ignoring request from com.android.nfc
07-31 00:21:21.021 D/PowerManagerService( 752): acquireWakeLock: ignoring request from com.android.nfc
07-31 00:21:21.050 I/DisplayPowerController( 752): Unblocked screen on after 461 ms
07-31 00:21:22.239 I/PowerManagerService( 752): Going to sleep due to power button (uid 1000)...
07-31 00:21:22.826 I/DisplayManagerService( 752): Display device changed state: "Built-in Screen", OFF
07-31 00:21:23.101 I/PowerManagerService( 752): Sleeping (uid 1000)...
07-31 00:21:23.133 D/PowerManagerService( 752): acquireWakeLock: ignoring request from com.android.nfc
07-31 00:21:34.403 I/PowerManagerService( 752): Waking up from sleep (uid 1000)...
07-31 00:21:34.464 I/DisplayPowerController( 752): Blocking screen on until initial contents have been drawn.
07-31 00:21:34.491 D/PowerManagerService( 752): acquireWakeLock: ignoring request from com.android.nfc
07-31 00:21:34.548 I/DisplayManagerService( 752): Display device changed state: "Built-in Screen", ON
07-31 00:21:34.624 I/DisplayPowerController( 752): Unblocked screen on after 160 ms
@marcomarinho i know you are busy with PA but if you get some time please check this and let me know what you find
i have this issue before when I'm watching youtube vids specially when the phone is in landscape mode, happens also 1 time when i was playing.
Edit: The lcd of my device has already been replaced.
Any input from logs ?
@osm0sis if you get some please take a look at logs and let me know if you find cause of issue in OP.
Thanks in advance
Turning OFF "adaptive (auto) brightness" seems to fix the problem.. atleast for now. Not a ideal solution but still..
So i guess issue is related to light sensor.