Deep sleep on Galaxy S3 or Android 4.0.4?

Odpad Issues
1

Hi

I have a rooted Samsung Galaxy S3 running Android 4.0.4. I installed the latest avast! Mobile with AntiTheft. The new web interface and features are great!! The only issue i have is that my phone now stays at 384 MHz at all times and never enters deep sleep. Is there a way to allow the phone to sleep? I see the CPU lock setting for the scanning, but i dont think it affects the AntiTheft feature.

Other than lack of deep sleep and the resulting battery drain, this app and features are fantastic! Thank you for these updates and the help!

2

hm is your device rooted?

3
I have a rooted Samsung Galaxy S3 running Android 4.0.4
4

ok can you please get me adb output of

adb shell

dumpsys power

5

yes sir

Power Manager State:
mIsPowered=false mPowerState=3 mScreenOffTime=282151 ms
mPartialCount=1
mWakeLockState=0x0
mUserState=0x3
mPowerState=0x3
mLocks.gather=0x0
mNextTimeout=283415 now=282163 1s from now
mDimScreen=true mStayOnConditions=0 mPreparingForScreenOn=false mSkippedScreenOn=false
mScreenOffReason=0 mUserState=3
mBroadcastQueue={-1,-1,-1}
mBroadcastWhy={0,0,0}
mPokey=0 mPokeAwakeonSet=false
mKeyboardVisible=false mUserActivityAllowed=true
mKeylightDelay=1500 mDimDelay=51500 mScreenOffDelay=7000
mPreventScreenOn=false mScreenBrightnessOverride=-1 mButtonBrightnessOverride=-1
mScreenOffTimeoutSetting=60000 mMaximumScreenOffTimeout=2147483647
mButtonOffTimeoutSetting=1500
mIsSipVisible=true
mLastScreenOnTime=0
mBroadcastWakeLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)
mStayOnWhilePluggedInScreenDimLock=UnsynchronizedWakeLock(mFlags=0x6 mCount=0 mHeld=false)
mStayOnWhilePluggedInPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)
mPreventScreenOnPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)
mProximityPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)
mProximityWakeLockCount=0
mProximitySensorEnabled=false
mProximitySensorActive=false
mProximityPendingValue=-1
mLastProximityEventTime=0
mLightSensorEnabled=true
mLightSensorValue=38.0 mLightSensorPendingValue=39.0
mLightSensorPendingDecrease=false mLightSensorPendingIncrease=true
mLightSensorScreenBrightness=80 mLightSensorButtonBrightness=255 mLightSensorKeyboardBrightness=0
mLightSensorScreenBrightnessUpperLimit=-1
mLightSensorScreenBrightnessLowerLimit=-1
mUseSoftwareAutoBrightness=true
mAutoBrightessEnabled=true
mMaxBrightness=-1
mScreenBrightness: animating=false targetValue=80 curValue=80.0 delta=-10.294118

mLocks.size=1:
PARTIAL_WAKE_LOCK ‘AWS NW Stats’ activated (minState=0, uid=10100, pid=1415)

mPokeLocks.size=0:

mDVFSLocks.size=1:
type : DVFS_MAX_LIMIT freq : 1134000 elapsed time : 26681 tag : InputManagerService <— mCurrentDVFSMaxLock
mPersistentDVFSLocksInfo=0x0

6

ok will be fixed in next bugfix update (scheduled for approx. 1 week from now).
if you want you can contact me at holzner (at) avast.com and i send you a test build to see if it really works.

7

Will do. Thank you! :slight_smile:

8

I have the same problem
Power Manager State:
mIsPowered=true mPowerState=3 mScreenOffTime=1277498 ms
mPartialCount=1
mWakeLockState=
mUserState=SCREEN_BRIGHT_BIT SCREEN_ON_BIT
mPowerState=SCREEN_BRIGHT_BIT SCREEN_ON_BIT
mLocks.gather=
mNextTimeout=1799109 now=1798183 0s from now
mDimScreen=true mStayOnConditions=0
mScreenOffReason=3 mUserState=3
mBroadcastQueue={-1,-1,-1}
mBroadcastWhy={0,0,0}
mPokey=0 mPokeAwakeonSet=false
mKeyboardVisible=false mUserActivityAllowed=true
mKeylightDelay=6000 mDimDelay=47000 mScreenOffDelay=7000
mPreventScreenOn=false mScreenBrightnessOverride=-1 mButtonBrightnessOverride=-1
mScreenOffTimeoutSetting=60000 mMaximumScreenOffTimeout=2147483647
mLastScreenOnTime=1690139
mBroadcastWakeLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)
mStayOnWhilePluggedInScreenDimLock=UnsynchronizedWakeLock(mFlags=0x6 mCount=0 mHeld=false)
mStayOnWhilePluggedInPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)
mPreventScreenOnPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)
mProximityPartialLock=UnsynchronizedWakeLock(mFlags=0x1 mCount=0 mHeld=false)
mProximityWakeLockCount=0
mProximitySensorEnabled=false
mProximitySensorActive=false
mProximityPendingValue=-1
mLastProximityEventTime=0
mLightSensorEnabled=false
mLightSensorValue=-1.0 mLightSensorPendingValue=-1.0
mLightSensorScreenBrightness=-1 mLightSensorButtonBrightness=-1 mLightSensorKeyboardBrightness=-1
mUseSoftwareAutoBrightness=false
mAutoBrightessEnabled=true
mScreenBrightness: animating=false targetValue=-1 curValue=144.0 delta=9.6

mLocks.size=1:
PARTIAL_WAKE_LOCK ‘PW com.avast.android.antitheft’ activated (minState=0, uid=10116, pid=440)

mPokeLocks.size=0:

Phone: LG Optimus One. CyanogenMod 7

9

It appeared, when I turned on locate phone every hour and switched off 3G/2G Data transfer.
Is this normal behaviour?

10

drop me an email to holzner (at) avast.com, i got a test build for you which fixes a lot of battery issues.

11

Not fixed. :-[

http://dl.dropbox.com/u/13678196/pictures/avast/screenshot-1346685182123.png

http://dl.dropbox.com/u/13678196/pictures/avast/screenshot-1346685203293.png

How Can I Help You? Logs, dumps?

12

please try to update again. reset stats and try again.