• 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)

KOD Update

Well chaps, after half a day of testing, suddenly got microstutter on launching/closing apps/programs. present on all governor settings. all other scrolling remains silky smooth. not huge stutter, but annoying. bit confused why this would suddenly start - any ideas?? :confused:
 
Sydney99 said:
KOD Update

Well chaps, after half a day of testing, suddenly got microstutter on launching/closing apps/programs. present on all governor settings. all other scrolling remains silky smooth. not huge stutter, but annoying. bit confused why this would suddenly start - any ideas?? :confused:
Click to expand...

I'm assuming Syd that you did a kernel wipe before installing so it's possibly down to your scheduler, as you say it occurs on all governors, or maybe your u/v'ing.

Could I ask you to try the noop or bfq scheduler with sched_mc enabled in NEAK options in Recovery, please, and let me know if you still get a stutter.
 
I just want to make clear some things...

1) CWM Manager is NOT supported and will never be, into 1.4 the new NEAK Configurator App will do same things as that app

2) Brightness curve modding is not supported yet, but i am adding it for 1.4

3) GS2Blitzer will be updated asap

4) I will also add some more infos about manitax battery scripts

Inviato dal mio GT-I9100 usando Tapatalk
 
ironass said:
I'm assuming Syd that you did a kernel wipe before installing so it's possibly down to your scheduler, as you say it occurs on all governors, or maybe your u/v'ing.

Could I ask you to try the noop or bfq scheduler with sched_mc enabled in NEAK options in Recovery, please, and let me know if you still get a stutter.
Click to expand...

thanks badass, i mean ironass.

yup, of course would never think of flashing a new kernel without using hawkers excellent script.

have only used with sched_mc enabled. certainly tried the noop and bfq but still happened.

maybe it's my undervolting then. will try going back to stock settings and work backwards again......
 
Simone.
Will the extras drop down automatically refresh as and when new/updated extras get released or do we have to refresh the list manually in some way?
I'm guessing its automatic, but just making sure. :)

Edit: just seen the check now option under the extras menu key so i'm guessing this needs to be done to bring in any new features
 
Hawker said:
Simone.
Will the extras drop down automatically refresh as and when new/updated extras get released or do we have to refresh the list manually in some way?
I'm guessing its automatic, but just making sure. :)

Edit: just seen the check now option under the extras menu key so i'm guessing this needs to be done to bring in any new features
Click to expand...

Yeah for extras you should check by yourself....;)

Anyway, updated GS2Blitzer script (and modded it a bit) + updated description of Battery Scripts (see changelog)
 
runnin neak 1.3.3 for the past day or so, performance is smooth, and battery life is excellent. but..

went into CWM this evening and it said summat about certain features being disabled due to the kernel. low and behold, my beloved backup and restore had been disabled. went back to latest siyah and all is well.

what am i missing here (apart from a brain)?

re:just noticed simones previous post about cwm not being supported. bah.

re:re: sorted. backup in recovery mode. back to neak :)
 
simes6600 said:
runnin neak 1.3.3 for the past day or so, performance is smooth, and battery life is excellent. but..

went into CWM this evening and it said summat about certain features being disabled due to the kernel. low and behold, my beloved backup and restore had been disabled. went back to latest siyah and all is well.

what am i missing here (apart from a brain)?

re:just noticed simones previous post about cwm not being supported. bah.

re:re: sorted. backup in recovery mode. back to neak :)
Click to expand...

Use CWM Recovery itself and not the app ;);)

It's way safer and better
 
If you have a folder called /clockworkmod/backup in your external_sd, the when you create a backup using NEAK backup to sd card from Recovery menu it will be saved into that folder instead of the internal sd.

At least that happened to me.

Please, try it and let me know if this is right or just my imagination :-)

Thanks.-
 
I'm pretty sure NEAK only performs its CWM backup/restore on internal storage.
I've asked Simone to give the option to select internal/external and he will try to put it in place when 1.4 comes out.
 
Hawker said:
I'm pretty sure NEAK only performs its CWM backup/restore on internal storage.
I've asked Simone to give the option to select internal/external and he will try to put it in place when 1.4 comes out.
Click to expand...

Please, give it a try because that happened to me already twice. And from there on all backups directed to sd card go to my external sd.
 
/clockworkmod/backup is the folder where CWM Recovery stores its backups. The folder name is the same whether your kernel saves to internal or external.
For example, Siyah stores it on external sd card, all other kernels I've ever tried stores them in the internal storage, so I have clockworkmod folders on both.

Perhaps if there is only a clockworkmod folder on external and not internal it will use the external?
 
Hawker said:
/clockworkmod/backup is the folder where CWM Recovery stores its backups. The folder name is the same whether your kernel saves to internal or external.
For example, Siyah stores it on external sd card, all other kernels I've ever tried stores them in the internal storage, so I have clockworkmod folders on both
Click to expand...

I have both folders too /sdcard/clockworkmod and /sdcard/external_sd/clockworkmod.

All the backups I make with neak 1.3.3 (choosing backup to sd card) are saved into the external sd folder. If, instead of that, I choose backup (without ...to sd card) then backup goes to internal sd).

Maybe it has to be with my configuration or something like that but this is what is going on here :-)

Thanks.-
 
To be honest, I've never given it much attention before, but after this discussion I thought I'd investigate further.

In the backup and restore menu, there are standard "backup" and "restore" options. These use the INTERNAL storage.
"backup to internal sd card" and "restore from internal sd card" use the EXTERNAL storage.

Think there is a bit of terminology confusion in NEAK's CWM. Perhaps the options should read "backup to internal storage", "backup to external sd card" etc....

:)
 
Hawker said:
To be honest, I've never given it much attention before, but after this discussion I thought I'd investigate further.

In the backup and restore menu, there are standard "backup" and "restore" options. These use the INTERNAL storage.
"backup to internal sd card" and "restore from internal sd card" use the EXTERNAL storage.

Think there is a bit of terminology confusion in NEAK's CWM. Perhaps the options should read "backup to internal storage", "backup to external sd card" etc....

:)
Click to expand...

You are right! We can tell Simone just to change the terminology then.

thank you!
 
i removed neak 133 (cos it didn't use cwm backup) ran hawkers cleaner 1.3 and reinstalled latest siyah. all fine.

then realised neak backup is in recovery mode, so ran cleaner script again and reflashed neak 133. now im getting force closes on the status bar, and its disappeared. cant access notifications etc.

?
 
simes6600 said:
i removed neak 133 (cos it didn't use cwm backup) ran hawkers cleaner 1.3 and reinstalled latest siyah. all fine.

then realised neak backup is in recovery mode, so ran cleaner script again and reflashed neak 133. now im getting force closes on the status bar, and its disappeared. cant access notifications etc.

?
Click to expand...

It might be worth trying hawkers updated 1.5 blitzer and then reflashing neak.
 
simone201 said:
Yeah for extras you should check by yourself....;)

Anyway, updated GS2Blitzer script (and modded it a bit) + updated description of Battery Scripts (see changelog)
Click to expand...

So the update checking frequency (eg every boot, every hour etc) will only automatically check for updates to the kernel, and not for the extras etc?

@simes:
FC's on your status bar seems to be theme releated to me.
I would try reflashing whatever theme your using too.
 
Noticed a strange wakelock since 1.3.3

I have an AlarmManager wakelock that never used to appear before (certainly not this frequently) It took up 1% of my overnight CPU with a count of 295. I think this is causing my worse overnight battery drain compared to 1.3.2. (0.5% per hour on 1.3.2, its around 0.8% per hour on 1.3.3)

Android OS was at 45% overnight.

Now I remember an old wakelock bug (which I'm not quite sure has even been fixed yet) similar to this that kept a constant wakelock running after an alarm/reminder had been shown, but this is different, as I've not got any reminders set. I've not even got any events in my calendar full stop for this week.

Anyone else getting this?
 
Yeah I've got about 500 counts of that. It didn't seem to effect my battery much though. I took my phone off charge before I went to sleep and about 9 hours later I was still on 100%.
 
I've analysed the wakelock further to see what apps are instigating the AlarmManager service and I got this:


Alarm Stats:
com.google.android.gsf
4011ms running, 78 wakeups
28 alarms: flg=0x4
8 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
42 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4
com.google.android.location
6143ms running, 9 wakeups
9 alarms: act=com.google.android.location.ALARM_WAKEUP_LOCATOR flg=0x4
com.anddoes.fancywidgets
20386ms running, 0 wakeups
19 alarms: act=com.anddoes.fancywidgets.UPDATE_LOCATION flg=0x4 cmp=com.anddoes.fancywidgets/.UpdateService
470 alarms: act=com.anddoes.fancywidgets.UPDATE_ALL flg=0x4 cmp=com.anddoes.fancywidgets/.UpdateService
com.anod.calendar
364ms running, 0 wakeups
1 alarms: act=android.appwidget.action.APPWIDGET_UPDATE dat=com.anod.calendar://widget/id/14 flg=0x4
1 alarms: act=android.appwidget.action.APPWIDGET_UPDATE dat=com.anod.calendar://widget/id/18 flg=0x4
com.android.vending
157ms running, 0 wakeups
3 alarms: act=com.android.vending.FORCE_UPDATE_CHECK flg=0x4
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.mobidia.android.mdm
8097ms running, 99 wakeups
99 alarms: act=com.mobidia.android.mdm.WAKE_SERVICE flg=0x4
com.android.email
115ms running, 4 wakeups
4 alarms: act=com.android.email.intent.action.MAIL_SERVICE_WAKEUP flg=0x4 cmp=com.android.email/.service.MailService
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
com.gau.go.launcherex
1124ms running, 16 wakeups
13 alarms: act=com.jiubang.intent.action.ACTION_TIDY_DATA flg=0x4
2 alarms: act=com.jiubang.intent.action.AUTO_CHECK_UPDATE flg=0x4
1 alarms: act=com.jiubang.intent.action.SCAN_APPS flg=0x4

So it seems like google maps could be the main culprit
NetworkLocationPassiveCollector was at 1% too, but only 31 calls. I've seen this far worse than that before, albeit on older versions
 
Don't appear to be old boy!

Alarmmanager.png
 
Thanks butty.
I'm not sure if this is kernel related or not at the moment, but I have to admit, I've only noticed this since installing 1.3.3.

I assume your on Google Maps 6.2.0?
 
You must log in or register to reply here.
Back
Top Bottom