Question S22 Exynos 40% Battery drain OVERNIGHT - Possible culprit found - Samsung Galaxy S22

Last night I took my S22 Exynos out of charging before I went to sleep. I woke up in the morning to find 40% of my battery DRAINED.
I'm really frustrated with this S22 as idle battery drain in general with screen off according to Accubattery is 5% PER HOUR. My S22 does not enter deep sleep overnight or during the day.
I opened ADB and looked and noticed a LOT of screen wakeups when I was sleeping and the phone was not charging.
WakeUp History size: 100​
Click to expand...
Click to collapse
[66] 10-01 00:39:53.104 1000 ON WAKE_REASON_PLUGGED_IN com.sec.android.app.launcher
[67] 10-01 00:39:58.396 1000 OFF timeout com.sec.android.app.launcher
[68] 10-01 01:35:49.267 1000 ON WAKE_REASON_PLUGGED_IN com.sec.android.app.launcher
[69] 10-01 01:35:54.511 1000 OFF timeout com.sec.android.app.launcher
[70] 10-01 02:30:22.641 1000 ON WAKE_REASON_PLUGGED_IN com.sec.android.app.launcher
[71] 10-01 02:30:27.906 1000 OFF timeout com.sec.android.app.launcher
[72] 10-01 03:26:12.390 1000 ON WAKE_REASON_PLUGGED_IN com.sec.android.app.launcher
[73] 10-01 03:26:17.682 1000 OFF timeout com.sec.android.app.launcher
[74] 10-01 04:22:27.257 1000 ON WAKE_REASON_PLUGGED_IN com.sec.android.app.launcher
[75] 10-01 04:22:32.541 1000 OFF timeout com.sec.android.app.launcher
[76] 10-01 05:14:56.599 1000 ON WAKE_REASON_PLUGGED_IN com.sec.android.app.launcher
[77] 10-01 05:15:01.874 1000 OFF timeout com.sec.android.app.launcher
[78] 10-01 06:08:14.875 1000 ON WAKE_REASON_PLUGGED_IN com.sec.android.app.launcher
[79] 10-01 06:08:20.123 1000 OFF timeout com.sec.android.app.launcher
[80] 10-01 07:01:28.993 1000 ON WAKE_REASON_PLUGGED_IN com.sec.android.app.launcher
[81] 10-01 07:01:34.263 1000 OFF timeout com.sec.android.app.launcher
[82] 10-01 07:55:50.326 1000 ON WAKE_REASON_PLUGGED_IN com.sec.android.app.launcher
[83] 10-01 07:55:55.596 1000 OFF timeout com.sec.android.app.launcher
[84] 10-01 08:46:50.835 1000 ON WAKE_REASON_PLUGGED_IN com.sec.android.app.launcher
[85] 10-01 08:46:56.102 1000 OFF timeout com.sec.android.app.launcher
[86] 10-01 09:39:54.246 1000 ON WAKE_REASON_PLUGGED_IN com.sec.android.app.launcher
[87] 10-01 09:39:59.484 1000 OFF timeout com.sec.android.app.launcher
[88] 10-01 10:38:42.216 1000 ON WAKE_REASON_PLUGGED_IN com.sec.android.app.launcher
[89] 10-01 10:38:47.477 1000 OFF timeout com.sec.android.app.launcher​
Click to expand...
Click to collapse
It appears the phone keeps thinking it is plugged in when it is clearly not. I wonder if this stops the phone from going into deepsleep?
I have my brightness set manually (20%) and noticed that the wakelock for screen_brightness is running.
Wake Locks History: size=4
09-30 16:31:47.037 (ElapsedTime: 143537ms) SCREEN_BRIGHT_WAKE_LOCK 'WindowManager' ON_AFTER_RELEASE (uid=1000 pid=1264 ws=WorkSource{10315} displayId=-1) [email protected]
09-30 21:04:53.343 (ElapsedTime: 84887ms) SCREEN_BRIGHT_WAKE_LOCK 'WindowManager' ON_AFTER_RELEASE (uid=1000 pid=1264 ws=WorkSource{10364} displayId=-1) [email protected]
09-30 21:12:34.099 (ElapsedTime: 352604ms) SCREEN_BRIGHT_WAKE_LOCK 'WindowManager' ON_AFTER_RELEASE (uid=1000 pid=1264 ws=WorkSource{10364} displayId=-1) [email protected]
10-01 10:53:41.126 (ElapsedTime: 162304ms) SCREEN_BRIGHT_WAKE_LOCK 'WindowManager' ON_AFTER_RELEASE (uid=1000 pid=1264 ws=WorkSource{10364} displayId=-1) [email protected]
Click to expand...
Click to collapse
ADB command: .\adb.exe shell dumpsys power
Please help. I am truly at my wits end with this phone. Battery drain is insane.

I actually got this bug several times, I plug my phone and instead of charging it keeps behaving like if I was plugging it in and out even if I don't touch anything
Restarting the phone fixes it

any news about this?

Related

Need help from fellow ROM developers.

I have been looking into the auto-backlight issue in the 2.1 Eris based ROMs and as posted in my ROM thread, the autobacklight seems to work fine until the screen is turned off (manual or auto).
If I switch auto-backlight off then on, i can cover and uncover the sensor and backlight will change.
BUT, as soon as the screen goes to sleep then wakes again, the backlight sensor no longer affects the backlight but the hardware keys still light and unlight according to it.
logcat shows that the sensor is still working;
Code:
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_START
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_COMPLETE
is the process it goes through when checking backlight, there is no difference here before or after screen off.
I see these possibly relevent lines before screen off:
Code:
I/power ( 107): *** set_screen_state 0
D/Sensors ( 107): using /dev/input/event5 (name=lightsensor-level)
If any devs with a little more experience with the display could possibly point me in the right direction I would really appreciate it, thanks.
Let me know if there is more information I can provide.
alias_neo said:
I have been looking into the auto-backlight issue in the 2.1 Eris based ROMs and as posted in my ROM thread, the autobacklight seems to work fine until the screen is turned off (manual or auto).
If I switch auto-backlight off then on, i can cover and uncover the sensor and backlight will change.
BUT, as soon as the screen goes to sleep then wakes again, the backlight sensor no longer affects the backlight but the hardware keys still light and unlight according to it.
logcat shows that the sensor is still working;
Code:
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_START
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_REQUEST
D/AK8973 ( 94): HRET = AKSC_HOF_DSS_COMPLETE
is the process it goes through when checking backlight, there is no difference here before or after screen off.
I see these possibly relevent lines before screen off:
Code:
I/power ( 107): *** set_screen_state 0
D/Sensors ( 107): using /dev/input/event5 (name=lightsensor-level)
If any devs with a little more experience with the display could possibly point me in the right direction I would really appreciate it, thanks.
Let me know if there is more information I can provide.
Click to expand...
Click to collapse
I was checking logcat after installing an Eris rom to check for certain stuff. I noticed some weird AK8973 spam and couldnt figure it out. Then it dawned on me that there was a magnet near my phone causing those messages. (Magnet from my Hero Sleeve Protector or whatever you call that). This led me to the conclusion that AK8973 is the magnetic field sensor (AKA Compass), not the light sensor.
Hope this helps!
Revoked
I'll have to test further because the output was corresponding to moving a phone flash in front of the sensor then away, admittedly though, the phone speaker was near it with its magnet.
It's still possible though that they just show similar messages.
Hopefully, one of the devs can help.
I also get this strange spam since installation of Legend ROM on my hero.
That is really annoying and doen't allow me to use the logcat as this message is really spamming a lot.
Any news on how to avoid it?
profete162 said:
I also get this strange spam since installation of Legend ROM on my hero.
That is really annoying and doen't allow me to use the logcat as this message is really spamming a lot.
Any news on how to avoid it?
Click to expand...
Click to collapse
It's the compass, it means there is a strong magnet near the phone somewhere.
Do you have one of those cases on your hero with a magnetic shutter? or are you placing it on you laptop when you logcat? (Laptops have a magnet for the reed switch to detect screen close sometimes, like my VAIO for example.)
Hi,
thank you for the answer...
Mu usb cable is 1meter long and i can put my Hero everywhere in my room, 1 meter away for the computer, sound speakers, etc.. I get always this message.
Maybe the magnets of my PC speakers are really strong, but i found no other magnetic sources anywhere
profete162 said:
Hi,
thank you for the answer...
Mu usb cable is 1meter long and i can put my Hero everywhere in my room, 1 meter away for the computer, sound speakers, etc.. I get always this message.
Maybe the magnets of my PC speakers are really strong, but i found no other magnetic sources anywhere
Click to expand...
Click to collapse
Stick it in a lead box

screen doesn't want to switch in standby...

Hi!
here are my stats
bravo pvt1 ship s-off
hboot 0.93.0001
touchpanel synw0101
radio 5.11.05.27
and hboot cm7 alpharev.
I've a problem because the screen doesn't want to switch off when I want to put my Desire in standby or after the standby delay.
I've made a adb logcat of these moments
manually standby
I/power ( 191): *** set_screen_state 0
D/WifiService( 191): ACTION_SCREEN_OFF
D/KeyguardViewMediator( 191): wakeWhenReadyLocked(272)
I/power ( 191): *** set_screen_state 1
D/WifiService( 191): ACTION_SCREEN_ON
D/SurfaceFlinger( 191): About to give-up screen, flinger = 0x90c30
D/SurfaceFlinger( 191): Screen about to return, flinger = 0x90c30
D/AK8973 ( 138): Compass CLOSE
D/AK8973 ( 138): Compass Start
Click to expand...
Click to collapse
and after the delay
I/power ( 191): *** set_screen_state 0
I/power ( 191): *** set_screen_state 1
I/InputDispatcher( 191): Dropped event because input dispatch is disabled.
I/InputDispatcher( 191): Dropped event because input dispatch is disabled.
D/SurfaceFlinger( 191): About to give-up screen, flinger = 0x90c30
D/SurfaceFlinger( 191): Screen about to return, flinger = 0x90c30
D/AK8973 ( 138): Compass CLOSE
D/AK8973 ( 138): Compass Start
W/AudioFlinger( 134): write blocked for 159 msecs, 3 delayed writes, thread 0xe
a90
D/AudioHardwareQSD( 134): AudioHardware pcm playback is going to standby.
Click to expand...
Click to collapse
each time it wants to switch off the screen switch on and volume down on the screen........
what should I do?
in several logs I never saw compass close and compass start... is it the problem?
thanks to help me even if i'm french and my english is.... poor.... sorry
What:
ROM?
Kernel?
Governor?
Set CPU used?
if so, Screen off profile used?
Values of screen off profile?
oh sorry.
I didn't change the kernel.
running CM7.1.0 with ondemand governor and cpu 998 I think.
I didn't channge nothing ant the rom have just been flashed.
same problem under oxygen
screen off profile... where can I find this info?
That would be if you use setCPU.
HMMM odd.
Did you do a full wipe before flash?
yes I did a full wipe and wiped cache and davilk cache too.
I didn't install setCPU.
same problem since yesterday.
do I have to try with another rom/hboot and radio?
up...........
I tried the ROM from this topic and the problem disappeared ... the screen tuns off in standby.
BUT when I try to flash a custom ROM or another ROM I still have this problem. ...
Any idea?

[Q] screen wakes up randomly while locked

While locked, the screen randomly wakes up in the locked mode (it shows you the screen where you can slide to unlock), then it shuts off again, only to light back up again after a couple of seconds. What's possibly causing this?
I'm running the stock rom on a G2.
dartbider said:
While locked, the screen randomly wakes up in the locked mode (it shows you the screen where you can slide to unlock), then it shuts off again, only to light back up again after a couple of seconds. What's possibly causing this?
I'm running the stock rom on a G2.
Click to expand...
Click to collapse
I wnat to know too!
on my dz and on my nexus S.
android related?
light sensor?
Are you rooted or running a non-stock kernel?
I recall this happening on CM, that one time I tried it. Weird that it happened on stock.
I would say to download "alogcat" from the market, enable it, then turn off your screen, wait for it to turn on, and put up here what the logcat puts out.
captainreynolds said:
Are you rooted or running a non-stock kernel?
I recall this happening on CM, that one time I tried it. Weird that it happened on stock.
I would say to download "alogcat" from the market, enable it, then turn off your screen, wait for it to turn on, and put up here what the logcat puts out.
Click to expand...
Click to collapse
Here are the results. Note that From the moment I turned the screen off at around 3:11, the screen woke up around 3 times. Twice at 3:19, and once at 3:20.
-----
-------- beginning of /dev/log/system
08-31 03:10:58.473 1291 1749 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
--------- beginning of /dev/log/main
08-31 03:11:00.685 1291 1328 I power : *** set_screen_state 0
08-31 03:11:00.685 1291 1328 D SensorService: disable: connection.get() = 0x3eb008
08-31 03:11:00.685 1291 1328 D SensorService: disable: get sensor name = CM3602 Light sensor
08-31 03:11:00.695 1291 1328 D SensorService: pid=1291, uid=1000
08-31 03:11:00.695 1291 1328 D SensorService: Active sensors:
08-31 03:11:00.695 1291 1328 D SensorService: BMA150 3-axis Accelerometer (handle=0x00000000, connections=1)
08-31 03:11:00.695 1291 1328 D lights : set_light_keyboard brightness=0
08-31 03:11:00.695 1291 1323 D SensorService: disable: connection.get() = 0x3eb008
08-31 03:11:00.695 1291 1323 D SensorService: disable: get sensor name = BMA150 3-axis Accelerometer
08-31 03:11:00.695 1291 1323 D Sensors : Enable akm: en = 0
08-31 03:11:00.695 1291 1323 D SensorService: pid=1291, uid=1000
08-31 03:11:00.695 1291 1323 D SensorService: Active sensors:
08-31 03:11:00.695 1291 1326 D KeyguardViewManager: show(); mKeyguardView==null
08-31 03:11:00.695 1291 1326 D KeyguardViewManager: keyguard view is null, creating it...
08-31 03:11:00.765 4367 4367 W IInputConnectionWrapper: getExtractedText on inactive InputConnection
08-31 03:11:00.765 4367 4367 W IInputConnectionWrapper: getExtractedText on inactive InputConnection
08-31 03:11:00.845 1404 1404 D Database: dbopen(): path = /data/data/com.google.android.gsf/databases/gls.db, flag = 6, file size = 5120
08-31 03:11:00.845 1404 1404 D Database: dbopen(): path = /data/data/com.google.android.gsf/databases/gls.db, journal mode: wal, storage free size = 885 M
08-31 03:11:00.875 4367 4367 W IInputConnectionWrapper: getExtractedText on inactive InputConnection
08-31 03:11:00.875 4367 4367 W IInputConnectionWrapper: getExtractedText on inactive InputConnection
08-31 03:11:00.885 1291 1299 D SurfaceFlinger: About to give-up screen, flinger = 0x23eb60
08-31 03:11:00.965 1780 1780 D dalvikvm: GC_EXPLICIT freed 294K, 51% free 2998K/6087K, external 1625K/2137K, paused 138ms
08-31 03:11:01.035 1780 1780 D dalvikvm: GC_EXPLICIT freed 303K, 51% free 3003K/6087K, external 1625K/2137K, paused 30ms
08-31 03:11:01.196 1225 1225 D AK8975 : Compass CLOSE
08-31 03:15:38.260 1291 1749 D dalvikvm: GC_EXPLICIT freed 1129K, 38% free 6978K/11143K, external 5168K/5467K, paused 131ms
08-31 03:19:33.610 1780 1780 D dalvikvm: GC_EXPLICIT freed 311K, 51% free 3002K/6087K, external 1625K/2137K, paused 39ms
08-31 03:19:44.930 1291 1291 I power : *** set_screen_state 1
08-31 03:19:44.940 1291 1291 D SensorService: enable: connection.get() = 0x3eb008
08-31 03:19:44.940 1291 1291 D SensorService: enable: get sensor name = CM3602 Light sensor
08-31 03:19:44.940 1291 1291 D SensorService: pid=1291, uid=1000
08-31 03:19:44.940 1291 1291 D SensorService: Active sensors:
08-31 03:19:44.940 1291 1291 D SensorService: CM3602 Light sensor (handle=0x00000004, connections=1)
08-31 03:19:44.950 1291 1323 D PowerManagerService: bl_tmp:80
08-31 03:19:44.950 1291 1323 D PowerManagerService: New lightsensor value:10, lcdValue:160
08-31 03:19:44.950 1291 1323 D PowerManagerService: lightSensorChangedLocked, buttonValue >= 0, mPowerState = 3
08-31 03:19:44.950 1291 1323 D lights : set_light_keyboard brightness=0
08-31 03:19:44.950 1291 1326 D KeyguardViewManager: onScreenTurnedOn()
08-31 03:19:44.960 1291 1323 D SensorService: enable: connection.get() = 0x3eb008
08-31 03:19:44.960 1291 1323 D SensorService: enable: get sensor name = BMA150 3-axis Accelerometer
08-31 03:19:44.960 1291 1323 D Sensors : Enable akm: en = 1
08-31 03:19:44.990 1291 1323 D SensorService: pid=1291, uid=1000
08-31 03:19:44.990 1291 1323 D SensorService: Active sensors:
08-31 03:19:44.990 1291 1323 D SensorService: BMA150 3-axis Accelerometer (handle=0x00000000, connections=1)
08-31 03:19:44.990 1291 1323 D SensorService: CM3602 Light sensor (handle=0x00000004, connections=1)
08-31 03:19:45.000 1225 1225 D AK8975 : Compass Start
08-31 03:19:45.020 1291 1299 D SurfaceFlinger: Screen about to return, flinger = 0x23eb60
08-31 03:19:50.045 1291 1417 I power : *** set_screen_state 0
08-31 03:19:50.045 1291 1417 D SensorService: disable: connection.get() = 0x3eb008
08-31 03:19:50.045 1291 1417 D SensorService: disable: get sensor name = CM3602 Light sensor
08-31 03:19:50.045 1291 1417 D SensorService: pid=1291, uid=1000
08-31 03:19:50.045 1291 1417 D SensorService: Active sensors:
08-31 03:19:50.045 1291 1417 D SensorService: BMA150 3-axis Accelerometer (handle=0x00000000, connections=1)
08-31 03:19:50.045 1291 1417 D lights : set_light_keyboard brightness=0
08-31 03:19:50.055 1291 1323 D SensorService: disable: connection.get() = 0x3eb008
08-31 03:19:50.055 1291 1323 D SensorService: disable: get sensor name = BMA150 3-axis Accelerometer
08-31 03:19:50.055 1291 1323 D Sensors : Enable akm: en = 0
08-31 03:19:50.055 1291 1323 D SensorService: pid=1291, uid=1000
08-31 03:19:50.055 1291 1323 D SensorService: Active sensors:
08-31 03:19:50.055 1291 1326 D KeyguardViewManager: onScreenTurnedOff()
08-31 03:19:50.055 1291 1326 D KeyguardViewManager: reset()
08-31 03:19:50.125 4367 4367 W IInputConnectionWrapper: getExtractedText on inactive InputConnection
08-31 03:19:50.125 4367 4367 W IInputConnectionWrapper: getExtractedText on inactive InputConnection
08-31 03:19:50.205 1780 1780 D dalvikvm: GC_EXPLICIT freed 314K, 51% free 3000K/6087K, external 1625K/2137K, paused 33ms
08-31 03:19:50.225 1291 1299 D SurfaceFlinger: About to give-up screen, flinger = 0x23eb60
08-31 03:19:50.275 1780 1780 D dalvikvm: GC_EXPLICIT freed 306K, 51% free 3001K/6087K, external 1625K/2137K, paused 31ms
08-31 03:19:50.536 1225 1225 D AK8975 : Compass CLOSE
08-31 03:19:59.520 1291 1365 D SntpClient: request time failed: java.net.UnknownHostException: north-america.pool.ntp.org
08-31 03:19:59.560 1291 1365 D SntpClient: request time failed: java.net.UnknownHostException: north-america.pool.ntp.org
08-31 03:19:59.560 1291 1365 D SntpClient: request time failed: java.net.UnknownHostException: north-america.pool.ntp.org
08-31 03:19:59.960 1291 1296 I power : *** set_screen_state 1
08-31 03:19:59.970 1291 1296 D SensorService: enable: connection.get() = 0x3eb008
08-31 03:19:59.970 1291 1296 D SensorService: enable: get sensor name = CM3602 Light sensor
08-31 03:19:59.970 1291 1296 D SensorService: pid=1291, uid=1000
08-31 03:19:59.970 1291 1296 D SensorService: Active sensors:
08-31 03:19:59.970 1291 1296 D SensorService: CM3602 Light sensor (handle=0x00000004, connections=1)
08-31 03:19:59.980 1291 1323 D PowerManagerService: bl_tmp:80
08-31 03:19:59.980 1291 1323 D PowerManagerService: New lightsensor value:10, lcdValue:160
08-31 03:19:59.980 1291 1323 D PowerManagerService: lightSensorChangedLocked, buttonValue >= 0, mPowerState = 3
08-31 03:19:59.980 1291 1323 D lights : set_light_keyboard brightness=0
08-31 03:19:59.980 1291 1326 D KeyguardViewManager: onScreenTurnedOn()
08-31 03:19:59.990 1291 1323 D SensorService: enable: connection.get() = 0x3eb008
08-31 03:19:59.990 1291 1323 D SensorService: enable: get sensor name = BMA150 3-axis Accelerometer
08-31 03:19:59.990 1291 1323 D Sensors : Enable akm: en = 1
08-31 03:20:00.000 1291 1323 D SensorService: pid=1291, uid=1000
08-31 03:20:00.000 1291 1323 D SensorService: Active sensors:
08-31 03:20:00.000 1291 1323 D SensorService: BMA150 3-axis Accelerometer (handle=0x00000000, connections=1)
08-31 03:20:00.000 1291 1323 D SensorService: CM3602 Light sensor (handle=0x00000004, connections=1)
08-31 03:20:00.020 1225 1225 D AK8975 : Compass Start
08-31 03:20:00.050 1291 1299 D SurfaceFlinger: Screen about to return, flinger = 0x23eb60
08-31 03:20:05.014 1291 1401 I power : *** set_screen_state 0
08-31 03:20:05.014 1291 1401 D SensorService: disable: connection.get() = 0x3eb008
08-31 03:20:05.014 1291 1401 D SensorService: disable: get sensor name = CM3602 Light sensor
08-31 03:20:05.034 1291 1401 D SensorService: pid=1291, uid=1000
08-31 03:20:05.034 1291 1401 D SensorService: Active sensors:
08-31 03:20:05.034 1291 1401 D SensorService: BMA150 3-axis Accelerometer (handle=0x00000000, connections=1)
08-31 03:20:05.034 1291 1401 D lights : set_light_keyboard brightness=0
08-31 03:20:05.044 1291 1323 D SensorService: disable: connection.get() = 0x3eb008
08-31 03:20:05.044 1291 1323 D SensorService: disable: get sensor name = BMA150 3-axis Accelerometer
08-31 03:20:05.044 1291 1323 D Sensors : Enable akm: en = 0
08-31 03:20:05.044 1291 1323 D SensorService: pid=1291, uid=1000
08-31 03:20:05.044 1291 1323 D SensorService: Active sensors:
08-31 03:20:05.044 1291 1326 D KeyguardViewManager: onScreenTurnedOff()
08-31 03:20:05.044 1291 1326 D KeyguardViewManager: reset()
08-31 03:20:05.204 1291 1299 D SurfaceFlinger: About to give-up screen, flinger = 0x23eb60
08-31 03:20:05.224 4367 4367 W IInputConnectionWrapper: getExtractedText on inactive InputConnection
08-31 03:20:05.224 4367 4367 W IInputConnectionWrapper: getExtractedText on inactive InputConnection
08-31 03:20:05.555 1225 1225 D AK8975 : Compass CLOSE
08-31 03:20:15.530 1291 1291 I power : *** set_screen_state 1
08-31 03:20:15.530 1291 1291 D SensorService: enable: connection.get() = 0x3eb008
08-31 03:20:15.530 1291 1291 D SensorService: enable: get sensor name = CM3602 Light sensor
08-31 03:20:15.540 1291 1291 D SensorService: pid=1291, uid=1000
08-31 03:20:15.540 1291 1291 D SensorService: Active sensors:
08-31 03:20:15.540 1291 1291 D SensorService: CM3602 Light sensor (handle=0x00000004, connections=1)
08-31 03:20:15.550 1291 1323 D PowerManagerService: bl_tmp:80
08-31 03:20:15.550 1291 1323 D PowerManagerService: New lightsensor value:10, lcdValue:160
08-31 03:20:15.550 1291 1323 D PowerManagerService: lightSensorChangedLocked, buttonValue >= 0, mPowerState = 3
08-31 03:20:15.550 1291 1323 D lights : set_light_keyboard brightness=0
08-31 03:20:15.550 1291 1326 D KeyguardViewManager: onScreenTurnedOn()
08-31 03:20:15.570 1291 1323 D SensorService: enable: connection.get() = 0x3eb008
08-31 03:20:15.570 1291 1323 D SensorService: enable: get sensor name = BMA150 3-axis Accelerometer
08-31 03:20:15.570 1291 1323 D Sensors : Enable akm: en = 1
08-31 03:20:15.570 1291 1323 D SensorService: pid=1291, uid=1000
08-31 03:20:15.570 1291 1323 D SensorService: Active sensors:
08-31 03:20:15.570 1291 1323 D SensorService: BMA150 3-axis Accelerometer (handle=0x00000000, connections=1)
08-31 03:20:15.570 1291 1323 D SensorService: CM3602 Light sensor (handle=0x00000004, connections=1)
08-31 03:20:15.680 1291 1299 D SurfaceFlinger: Screen about to return, flinger = 0x23eb60
08-31 03:20:15.780 1225 1225 D AK8975 : Compass Start
08-31 03:20:20.734 1291 1752 I power : *** set_screen_state 0
08-31 03:20:20.734 1291 1752 D SensorService: disable: connection.get() = 0x3eb008
08-31 03:20:20.734 1291 1752 D SensorService: disable: get sensor name = CM3602 Light sensor
08-31 03:20:20.734 1291 1752 D SensorService: pid=1291, uid=1000
08-31 03:20:20.734 1291 1752 D SensorService: Active sensors:
08-31 03:20:20.734 1291 1752 D SensorService: BMA150 3-axis Accelerometer (handle=0x00000000, connections=1)
08-31 03:20:20.734 1291 1752 D lights : set_light_keyboard brightness=0
08-31 03:20:20.734 1291 1323 D SensorService: disable: connection.get() = 0x3eb008
08-31 03:20:20.734 1291 1323 D SensorService: disable: get sensor name = BMA150 3-axis Accelerometer
08-31 03:20:20.734 1291 1323 D Sensors : Enable akm: en = 0
08-31 03:20:20.734 1291 1323 D SensorService: pid=1291, uid=1000
08-31 03:20:20.734 1291 1323 D SensorService: Active sensors:
08-31 03:20:20.734 1291 1326 D KeyguardViewManager: onScreenTurnedOff()
08-31 03:20:20.734 1291 1326 D KeyguardViewManager: reset()
08-31 03:20:20.804 4367 4367 W IInputConnectionWrapper: getExtractedText on inactive InputConnection
08-31 03:20:20.804 4367 4367 W IInputConnectionWrapper: getExtractedText on inactive InputConnection
08-31 03:20:20.904 1291 1299 D SurfaceFlinger: About to give-up screen, flinger = 0x23eb60
08-31 03:20:20.944 1225 1225 D AK8975 : Compass CLOSE
08-31 03:20:21.430 1291 1328 D KeyguardViewMediator: wakeWhenReadyLocked(26)
08-31 03:20:21.430 1291 1326 D KeyguardViewManager: wakeWhenReady(26)
08-31 03:20:21.440 1291 1326 I power : *** set_screen_state 1
08-31 03:20:21.440 1291 1326 D SensorService: enable: connection.get() = 0x3eb008
08-31 03:20:21.440 1291 1326 D SensorService: enable: get sensor name = CM3602 Light sensor
08-31 03:20:21.440 1291 1326 D SensorService: pid=1291, uid=1000
08-31 03:20:21.440 1291 1326 D SensorService: Active sensors:
08-31 03:20:21.440 1291 1326 D SensorService: CM3602 Light sensor (handle=0x00000004, connections=1)
08-31 03:20:21.440 1291 1323 D SensorService: enable: connection.get() = 0x3eb008
08-31 03:20:21.440 1291 1323 D SensorService: enable: get sensor name = BMA150 3-axis Accelerometer
08-31 03:20:21.440 1291 1323 D Sensors : Enable akm: en = 1
08-31 03:20:21.440 1291 1323 D SensorService: pid=1291, uid=1000
08-31 03:20:21.440 1291 1323 D SensorService: Active sensors:
08-31 03:20:21.440 1291 1323 D SensorService: BMA150 3-axis Accelerometer (handle=0x00000000, connections=1)
08-31 03:20:21.440 1291 1323 D SensorService: CM3602 Light sensor (handle=0x00000004, connections=1)
08-31 03:20:21.440 1291 1326 D KeyguardViewManager: onScreenTurnedOn()
08-31 03:20:21.520 1291 1323 D PowerManagerService: bl_tmp:80
08-31 03:20:21.530 1291 1323 D PowerManagerService: New lightsensor value:10, lcdValue:160
08-31 03:20:21.530 1291 1323 D PowerManagerService: lightSensorChangedLocked, buttonValue >= 0, mPowerState = 3
08-31 03:20:21.540 1291 1323 D lights : set_light_keyboard brightness=0
08-31 03:20:21.560 1291 1299 D SurfaceFlinger: Screen about to return, flinger = 0x23eb60
08-31 03:20:21.670 1225 1225 D AK8975 : Compass Start
08-31 03:20:22.701 1291 1326 D KeyguardViewManager: hide()
08-31 03:20:22.751 1291 1754 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
08-31 03:20:23.201 1291 1326 D KeyguardViewManager: hide(); digitalClock OOM removeViewFromWindow
08-31 03:20:26.184 1291 1750 W InputManagerService: Window already focused, ignoring focus gain of: [email protected]
The answer is simple - your phone is alive and demands attention.
On a serious node: It happend to me on random phones: Xperia Arc S running stock gingerbread, Xperia Arc S after upgrading to 4.0, HTC Desire Z pre and post 4.0, on a number of different ROMs (but all based on CM7 and CM9), also it woke up on a Motorola Milestone using CM7 and CM9 based ROMs. Only thing I can recall is that the motorola NEVER woke up when I was runnning a stock 2.1 Eclair on it. But it did woke up a couple of times on stock 2.2 Froyo. My guess is, google code somewhere when we won't even bother to look. Probably.
I've had this happen and it's always a rogue app. Just an idea
dartbider said:
While locked, the screen randomly wakes up in the locked mode (it shows you the screen where you can slide to unlock), then it shuts off again, only to light back up again after a couple of seconds. What's possibly causing this?
I'm running the stock rom on a G2.
Click to expand...
Click to collapse
I had similar same issue,
in my case, mp3 downloader's ad Notification was waking up my screen,
I found it out by using app "Wakelock detector" WLD at GooglePlay
you need to check for "full wakelocks", check the screenshot

Compass issue.... logcat attached

Hi guys,
Looks like my compass is faulty and is not letting my device sleep. As soon as i lock the device, it wakes it up, then screen sleeps after 15 seconds, and suddenly wakes up, and the cycle goes on and on until battery dies.
See logcat
Code:
10:25:35.286 Verbose TransportControlView 319 Create TCV [email protected]
10:25:35.286 Debug SurfaceFlinger 142 About to give-up screen, flinger = 0x410e0af0
[COLOR="Red"]10:25:35.396 Debug AK8973 149 Compass CLOSE
10:25:35.397 Debug AK8973 149 Compass Start[/COLOR]
10:25:35.397 Debug SurfaceFlinger 142 Screen about to return, flinger = 0x410e0af0
10:25:35.504 Debug dalvikvm 319 GC_CONCURRENT freed 1475K, 34% free 7990K/12099K, paused 15ms+9ms, total 315ms
10:25:35.504 Debug dalvikvm 319 WAIT_FOR_CONCURRENT_GC blocked 46ms
10:25:35.504 Debug dalvikvm 319 WAIT_FOR_CONCURRENT_GC blocked 48ms
10:25:35.614 Verbose LockPatternKeyguardView 319 Set visibility on [email protected]b08 to 8388608
10:25:35.722 Verbose LockPatternKeyguardView 319 Set visibility on [email protected]b08 to 8388608
10:25:35.722 Info WindowManager 319 Lock screen displayed!
10:25:45.566 Verbose TransportControlView 319 Create TCV [email protected]
10:25:45.675 Debug SurfaceFlinger 142 About to give-up screen, flinger = 0x410e0af0
[COLOR="red"]10:25:45.675 Debug AK8973 149 Compass CLOSE
10:25:45.675 Debug AK8973 149 Compass Start[/COLOR]
10:25:45.675 Debug SurfaceFlinger 142 Screen about to return, flinger = 0x410e0af0
10:25:45.786 Verbose LockPatternKeyguardView 319 Set visibility on [email protected]b08 to 8388608
10:25:45.894 Verbose LockPatternKeyguardView 319 Set visibility on [email protected]b08 to 8388608
10:25:45.894 Info WindowManager 319 Lock screen displayed!
10:25:55.828 Verbose TransportControlView 319 Create TCV [email protected]
10:25:55.941 Debug SurfaceFlinger 142 About to give-up screen, flinger = 0x410e0af0
10:25:55.941 Debug SurfaceFlinger 142 Screen about to return, flinger = 0x410e0af0
[COLOR="red"]10:25:56.050 Debug AK8973 149 Compass CLOSE
10:25:56.050 Verbose LockPatternKeyguardView 319 Set visibility on [email protected]b08 to 8388608
10:25:56.050 Debug AK8973 149 Compass Start[/COLOR]
10:25:56.050 Debug PowerManagerService 319 ignoring user activity while turning off screen
10:25:56.050 Debug PowerManagerService 319 ignoring user activity while turning off screen
10:25:56.162 Verbose LockPatternKeyguardView 319 Set visibility on [email protected]b08 to 8388608
10:25:56.266 Verbose TransportControlView 319 Create TCV [email protected]
10:25:56.374 Debug dalvikvm 319 GC_CONCURRENT freed 1857K, 35% free 7976K/12099K, paused 39ms+10ms, total 208ms
10:25:56.374 Debug dalvikvm 319 WAIT_FOR_CONCURRENT_GC blocked 61ms
10:25:56.488 Info WindowManager 319 Lock screen displayed!
10:25:56.488 Verbose LockPatternKeyguardView 319 Set visibility on [email protected]b08 to 8388608
10:25:56.594 Verbose LockPatternKeyguardView 319 Set visibility on [email protected]b08 to 8388608
10:26:06.097 Verbose TransportControlView 319 Create TCV [email protected]
10:26:06.097 Debug SurfaceFlinger 142 About to give-up screen, flinger = 0x410e0af0
10:26:06.202 Debug SurfaceFlinger 142 Screen about to return, flinger = 0x410e0af0
[COLOR="red"]10:26:06.202 Debug AK8973 149 Compass CLOSE
10:26:06.202 Debug AK8973 149 Compass Start[/COLOR]
10:26:06.315 Verbose LockPatternKeyguardView 319 Set visibility on [email protected]b08 to 8388608
10:26:06.421 Verbose LockPatternKeyguardView 319 Set visibility on [email protected]b08 to 8388608
10:26:06.421 Info WindowManager 319 Lock screen displayed!
Any suggessions i can remove the compass altogether???
i dont use it anyways...... just point me to the file i have to remove/modify...... is it 'akmd' in /system/bin or any other....... Appreciate your help...
Regards
Yasir

Xperia M LED control from shell (using files in /sys/class/)

Hello XDA community,
I would like to get some advice at controlling notification LED on my Xperia M dual (C2005) running PecanM's Adnroid 6.0.
"Internet" says it is controlled from /sys/class/led or .../leds.
the /led directory looks like this:
Code:
[email protected]:/sys/class/led # ls
ls
fih_led
the fih_led directory:
Code:
[email protected]:/sys/class/led/fih_led # ls
ls
control
info
power
subsystem
uevent
the info file (green is on because it's charging and battery state > 90%):
Code:
[email protected]:/sys/class/led/fih_led # cat info
cat info
red LED(0), PMIC GPIO-0, LPG-6
On/Off PWM(0), Blinking PWM[0:0], Fade in/out PWM(511)
Blinking Time[0ms:0ms], Interval(500ms)
Frequency[CLK:DIV:EXP]=[2:3:3]
Ramp Generator[Toggle:Loop:Up]=[No:No:Yes]
LUT table[48-63]
Disable invert
Current sink(12mA)
Normal mode
Off state
green LED(1), PMIC GPIO-0, LPG-5
On/Off PWM(510), Blinking PWM[0:0], Fade in/out PWM(511)
Blinking Time[0ms:0ms], Interval(500ms)
Frequency[CLK:DIV:EXP]=[2:3:3]
Ramp Generator[Toggle:Loop:Up]=[No:No:Yes]
LUT table[32-47]
Disable invert
Current sink(12mA)
Normal mode
On state
blue LED(2), PMIC GPIO-0, LPG-4
On/Off PWM(0), Blinking PWM[0:0], Fade in/out PWM(511)
Blinking Time[0ms:0ms], Interval(500ms)
Frequency[CLK:DIV:EXP]=[2:3:3]
Ramp Generator[Toggle:Loop:Up]=[No:No:Yes]
LUT table[16-31]
Disable invert
Current sink(12mA)
Normal mode
Off state
then there is a control file:
Code:
[email protected]:/sys/class/led/fih_led # cat control
cat control
CMD
01 : LED on/off, 1 parameter
02 : LED blinking, 1 parameter
03 : LED fade in/out, 1 parameter
04 : Brightness of LED on, 1 parameter
05 : Brightness of LED blinking, 2 parameter
06 : Interval for LED fade in/out, 1 parameter
07 : Blinking time, 2 parameter
08 : Set mode, 1 parameter
09 : LED on/off in special mode, 1 parameter
10 : LED blinking in special mode, 1 parameter
11 : LED fade in/out in special mode, 1 parameter
12 : Set PMIC GPIO/MPP clock, DIV & EXP, 3 parameter
13 : Set PMIC GPIO/MPP clock, 1 parameter
14 : Set PMIC GPIO/MPP DIV, 1 parameter
15 : Set PMIC GPIO/MPP EXP, 1 parameter
16 : Set PMIC GPIO/MPP toggle, loop & ramp, 3 parameter
17 : Set PMIC GPIO/MPP toggle, 1 parameter
18 : Set PMIC GPIO/MPP loop, 1 parameter
19 : Set PMIC GPIO/MPP ramp, 1 parameter
20 : Set PMIC GPIO invert, 1 parameter
21 : Set PMIC MPP/LPG current sink, 1 parameter
22 : Set LED pin, 1 parameter
23 : Set MSM GPIO on/off level, 2 parameter
24 : Set PMIC GPIO/MPP/LPG, 1 parameter
25 : Brightness of LED fade in/out, 1 parameter
26 : LED SW blinking, 1 parameter
27 : LED SW fade in/out, 1 parameter
28 : LED SW blinking in special mode, 1 parameter
29 : LED SW fade in/out in special mode, 1 parameter
30 : Set range of LUT table, 2 parameter
31 : Set on/off state of LED, 1 parameter
32 : LED fade in/out at different timing (on/off, in time, out time), 3 parameter
33 : LED fade in/out once (on, in/out time, toggle up/down), 3 parameter
34 : LED fade in/out at different timing in special mode, 3 parameter
35 : LED fade in/out once in special mode, 3 parameter
From all this information I am assuming that these numbers are commands for controlling the led and
Code:
echo 21 0 > control
echo 01 1 > control
should set the currently controlled led to pin 0 (the red one) and turn it on (or off depending on type of logic), but that does nothing.
Is there any documentation on how to use this? Or does anybody know how to control the notification led?
Thanks for any useful information.

Categories

Resources