-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
N.E.A.K. Gingerbread kernel (v1.x)
- Thread starter ironass
- Start date
-
- Tags
- samsung galaxy s2
ironass
Extreme Android User
Since I can't remember it as a problem on those kernels... then I guess I wasn't getting it either.
Good luck with xda!
simone201
Newbie
This is kinda strange, as you're the only one having this...have u installed recently some new apps that may cause this bug?
I am sure that is an app that causes this issue...also try betterbatterystats
Inviato dal mio GT-I9100 usando Tapatalk
Hawker
Android Expert
It was betterbatterystats that I looked at in the first place Simone.
Both Ironass and Shotgun are having it too, albeit a very high count with low %age
No I've not installed any new apps recently.
I've just taken it off full charge so the stats have reset, so i will monitor how this develops....
Both Ironass and Shotgun are having it too, albeit a very high count with low %age
No I've not installed any new apps recently.
I've just taken it off full charge so the stats have reset, so i will monitor how this develops....
simone201
Newbie
Strange thing is that on mine this partial wakelock doesn't exist at all...
Only the GTalk one because i use it a lot, so i am sure there is something related to an app
Inviato dal mio GT-I9100 usando Tapatalk
Hawker
Android Expert
The 2 main culrpits for this are Android OS and google Maps.
Android OS took up 81 CPU seconds (22 wakeups)
Maps took up 11 CPU seconds (208 wakeups)
android
81622ms running, 22 wakeups
1 alarms: act=android.intent.action.DATE_CHANGED flg=0x20000004
19 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x4
470 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
2 alarms: act=com.android.server.WifiManager.action.DEVICE_IDLE flg=0x4
67 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
1 alarms: act=android.app.backup.intent.RUN flg=0x40000004
com.google.android.apps.maps
10969ms running, 208 wakeups
25 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService
9 alarms: act=com.google.android.location.ALARM_WAKEUP_PASSIVE_COLLECTOR flg=0x4
1 alarms: act=com.google.android.location.ALARM_WAKEUP_CACHE_UPDATER flg=0x4
169 alarms: act=com.google.android.location.ALARM_WAKEUP_LOCATOR flg=0x4
3 alarms: act=com.google.android.location.ALARM_WAKEUP_BURST_COLLECTOR flg=0x4
1 alarms: act=com.google.android.location.ALARM_WAKEUP_ACTIVE_COLLECTOR flg=0x4
Simone, could your OTA app be affecting this?
I have my frequency check set to "boot" but I'm at a loss what else this could be
Android OS took up 81 CPU seconds (22 wakeups)
Maps took up 11 CPU seconds (208 wakeups)
android
81622ms running, 22 wakeups
1 alarms: act=android.intent.action.DATE_CHANGED flg=0x20000004
19 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x4
470 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
2 alarms: act=com.android.server.WifiManager.action.DEVICE_IDLE flg=0x4
67 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
1 alarms: act=android.app.backup.intent.RUN flg=0x40000004
com.google.android.apps.maps
10969ms running, 208 wakeups
25 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService
9 alarms: act=com.google.android.location.ALARM_WAKEUP_PASSIVE_COLLECTOR flg=0x4
1 alarms: act=com.google.android.location.ALARM_WAKEUP_CACHE_UPDATER flg=0x4
169 alarms: act=com.google.android.location.ALARM_WAKEUP_LOCATOR flg=0x4
3 alarms: act=com.google.android.location.ALARM_WAKEUP_BURST_COLLECTOR flg=0x4
1 alarms: act=com.google.android.location.ALARM_WAKEUP_ACTIVE_COLLECTOR flg=0x4
Simone, could your OTA app be affecting this?
I have my frequency check set to "boot" but I'm at a loss what else this could be
ironass
Extreme Android User
FYI, mine is set to, "Every day".
Hawker
Android Expert
simone201
Newbie
Yeah...try as example to reinstall GMaps, check again...
Anyway, the good thing of my kernel is that any AOS Bus is not hidden like in other kernels so you can see what's draining ur battery
How about processes in BBS?
Inviato dal mio GT-I9100 usando Tapatalk
Hawker
Android Expert
My BBS stats have reset now since full charge, but AlarmService was top with NetworkLocaionPassiveCollector second.
It was at this stage I did a sumpsys alarm to see what the AlarmService wakelock was comprised of, with the results above.
At this early stage after full charge, AlarmManager is on a count of 80. This is after 40 minutes.
Something is not quite right here. Perhaps it is Google Maps, but like I said, I've had 6.2.0 on for quite a while now, and never noticed this wakelock before 1.3.3.
I'll try uninstalling and reinstalling Google Maps now...
It was at this stage I did a sumpsys alarm to see what the AlarmService wakelock was comprised of, with the results above.
At this early stage after full charge, AlarmManager is on a count of 80. This is after 40 minutes.
Something is not quite right here. Perhaps it is Google Maps, but like I said, I've had 6.2.0 on for quite a while now, and never noticed this wakelock before 1.3.3.
I'll try uninstalling and reinstalling Google Maps now...
simone201
Newbie
simone201
Newbie
Is a bit high anyway, but is not draining ur battery for sure
Inviato dal mio GT-I9100 usando Tapatalk
Hawker
Android Expert
I can confirm I don't get this alarm manager wake lock on siyah.
Edit: after an hour or so, the wakelock has returned.
I'm wondering if this is due to google maps after all.
Can you look if you have a high alarmmanager wakelock count then give your version of maps please.
Edit: its not maps. I uninstalled it and the wakelock count is still creeping up at an alarming rate. (no pun intended!) Its being polled once every 10 seconds.
Edit: after an hour or so, the wakelock has returned.
I'm wondering if this is due to google maps after all.
Can you look if you have a high alarmmanager wakelock count then give your version of maps please.
Edit: its not maps. I uninstalled it and the wakelock count is still creeping up at an alarming rate. (no pun intended!) Its being polled once every 10 seconds.
Shotgun84
Extreme Android User
I've had to jump ship back to siyah. I started getting lots of random freezes without much u/v.
A bit of a shame as apart from that everything was looking good performance and battery wise.
Did you try flashing hawkers cleaning script first? I flashed the kernel a few times while comparing it with siyah and never encountered any bootloops.
A bit of a shame as apart from that everything was looking good performance and battery wise.
Did you try flashing hawkers cleaning script first? I flashed the kernel a few times while comparing it with siyah and never encountered any bootloops.
Hmm...looking at the issues you guys seem to be having, I think I'll still be sticking to 1.3.2 for a while then. I'm loving this kernel more and more. 
Got 4 hours of screen time today (not watching any videos or anything, which tends to augment the screen display time because it drains battery at a slower rate).
Got 4 hours of screen time today (not watching any videos or anything, which tends to augment the screen display time because it drains battery at a slower rate).
simone201
Newbie
Hmm...looking at the issues you guys seem to be having, I think I'll still be sticking to 1.3.2 for a while then. I'm loving this kernel more and more.
Well, trust me, 1.3.3 is a step ahead and only a few people are having some strange issues like wakelocks...
Inviato dal mio GT-I9100 usando Tapatalk
Hawker
Android Expert
Are you still getting a high AlarmManager count butty? I put Siyah back on to test and I still got it.
Hmm...looking at the issues you guys seem to be having, I think I'll still be sticking to 1.3.2 for a while then. I'm loving this kernel more and more.
Its unlikely that this is due to issues with this version of the kernel mate.
1.3.3 is an excellent kernel indeed, and even with this curious AlarmManager wakelock going on, its not hitting the battery in any significant way, so I would still highly recommend it.
Back onto this wakelock. AlarmManager count was on over 2000 when I examined my phone first thing this morning, but had only taken 0.6%. Battery drain was superbly insignificant last night overall too. It was only about 0.3% per hour!
I'm having all sorts of curious things going on with this AlarmManager wakelock.
Last night it was going through the roof. It was being generated once every 10 seconds. Basically each time I went into BBS, the count was going up before my eyes.
I fully charged my phone this morning. I didnt touch it 3 hours, and the AlarmManager wakelock count was only at 110, so roughly one increment in 100 seconds. I've gone in and out of BBS a few times, and its now on 238 after 3 hours 10 minutes, so its back on approx 1 every 10 seconds. I've now fully closed down BBS and will leave it for a while to see what the count will be on.
My first suspicions were Google Maps. I uninstalled it, and the count still crept up.
My next suspicion was My Data Manager, as there is also a MDM wakelock that creeps up along with it. But judging my the MDM wakelock count being only on 99 after 3 hours 10 minutes (1 per 100 secs approx) then I'm not overly suspicious of this now. I've had this app for a long time, and never noticed this wakelock previously.
I'm wondering, bizarrely, if BBS is kicking this thing off in some way? Its only started going up at this rate since I went into it to check the stats!
steslatt
Android Expert
No, as I was coming from KK5 CF-Root. Does this Kernel require a cleaning script before it will work? Got sick of the Siyah bugs, each new version seems to fix something and break something else for me. Tried this Kernel after a full wipe and got bootloop :/
Currently testing Redpill kernel, I'll try the cleaning script next time I flash see if it makes a difference.
Hawker
Android Expert
A kernel clean script will often fix a bootloop.
or just try a clear cache+dalvik cache
Shotgun84
Extreme Android User
Yeah its still quite high but nowhere near yesterday. I'm on about 430 at the moment. Was probably at about 750 this time with neak.
simes6600
Well-Known Member
Don't appear to be old boy!
what's that font yer using ironass, looks a tad like roboto?..anyroads, i like.