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

ironass said:
Well spotted simes6600! ;)

It is indeed the stock ICS font, "Roboto", that I got the .apk for ages ago. Very legible, particularly in texts.
Click to expand...

yup, very cool font (i know i'm off topic here, soz!) but i always thought it looked a tad big in the S2 menus etc. can be resized in go launcher though which is nice.

this made me go search for a smaller version of it, i found one over at XDA shrunk to 85% of the original, just installed it a moment ago, looks lovely.
 
simes6600 said:
yup, very cool font (i know i'm off topic here, soz!) but i always thought it looked a tad big in the S2 menus etc. can be resized in go launcher though which is nice.

this made me go search for a smaller version of it, i found one over at XDA shrunk to 85% of the original, just installed it a moment ago, looks lovely.
Click to expand...

Bet you don't wear reading glasses? ;)
 
hehe, i do, but there summat about the big font which made it look like a nokia 5110 etc. i'd rather have a cooler, smaller font and suffer the squintage. (like marty f in my avatar).
 
I got the small version of it too. Much better than the regular size I think.
Ubuntu is my favourite, with this one and helveticaneues in close second.

Back on topic now please children! :D
 
Hawker said:
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!
Click to expand...


Alright, sold then! (Actually I just check BetterBatteryStats and even on 1.3.2 I'm getting the Alarm Manager wakelock too. My count is about 1600 but 0.01% taken)

So which version of your cleaning script should I use first? Also, the only things I've done are use voltage control to set noop conservative, sched_mc enabled, 100-800 and undervolt a little, saving to init.d.
 
Kuragari said:
Alright, sold then! (Actually I just check BetterBatteryStats and even on 1.3.2 I'm getting the Alarm Manager wakelock too. My count is about 1600 but 0.01% taken)

So which version of your cleaning script should I use first? Also, the only things I've done are use voltage control to set noop conservative, sched_mc enabled, 100-800 and undervolt a little, saving to init.d.
Click to expand...

The only thing different between Blitzer and Wiper is Blitzer also removes all startup scripts from init.d folder, so the choice is yours mate.
Both will remove all previous neak settings, so you would have to re-enable conservative, sched_mc agin
 
Hawker said:
A kernel clean script will often fix a bootloop.
or just try a clear cache+dalvik cache
Click to expand...

Well it was time to try a new kernel so i thought i would try and give this one a whirl again, this time using the script first... Still no joy, bootloop, cant even get recovery, I have to flash a .tar in download mode. Must be something on my phone from somewhere that is conflicting with this kernel. Next time I do a full wipe, ill try it again :/
 
How long did you let it run for before giving up the ghost?
A first run after cache/dalvik clear can take quite a while, particularly if your ROM executes zipalignment.
 
Hawker said:
How long did you let it run for before giving up the ghost?
A first run after cache/dalvik clear can take quite a while, particularly if your ROM executes zipalignment.
Click to expand...

5 mins ish, it wouldn't even get to the boot animation just kept looping the splash screen. Also like i said I cant even enter recovery after flashing. something is not right, not saying its the kernel, could be something on my phone.
CF root KK5 works fine, Siyah works fine, Redpill works fine.
Without a full wipe im not sure what else I can do.
 
What ROM are you using?
Its not CM/MIUI or ICS compatible yet

You flashed Cf-Root KK5, but I seem to remember you being in CM in the past?
Perhaps there is some CM stuff still on your device that wont let it play nicely.
 
Anyone know the directory for brightness settings on neak? I'm trying to reduce the max gamma with an init.d script. With siyah the directory was
/sys/class/misc/brightness_curve
But this doesn't exist on my phone.
 
NEAK doesn't support it butty.
This is why the JKay auto brightness profile option wont work with it.

1.4 will support this apparently
 
Up until the release of CheckROM v6 I would have said that you would be hard pushed to get a cigarette paper between Siyah and N.E.A.K. kernels, in terms of performance and battery. They were so close that I could even interchange my Voltage Control settings between them.

However, since CheckROM v6, that has changed for me. I started off using Siyah 2.6.12 and it was very good but after switching, yesterday, to N.E.A.K. 1.3.3, it's better, for me, in terms of performance. Obviously, it's too early to say about battery on either of them and early indications are that there won't be a lot of difference.

N.E.A.K. 1.3.3 though is, for me, noticeably smoother and faster on this ROM.
 
I'm a neak convert now butty and have been for a few Weeks now. I put 1.3.3 on directly after checkrom v6 and am finding it extremely good. Running my same old vc settings etc. battery drain is excellent under heavy use. The best I've ever seen it. First overnight drain was about 0.8% per hour so not up to my usual 0.5% benchmark standard but it's early days.
 
If u like so much the smoothness of 1.3.3, the next 1.4 (WIP) with BFS will be even faster!! Trust me guyz...

Inviato dal mio GT-I9100 usando Tapatalk
 
simone201 said:
If u like so much the smoothness of 1.3.3, the next 1.4 (WIP) with BFS will be even faster!! Trust me guyz...
Click to expand...

You are tormenting us with 1.4 aren't you?

I know there is no point in asking for an E.T.A. but, if you are looking for testers, you could always PM hawker and myself. We'd be happy to oblige! :D
 
ironass said:
You are tormenting us with 1.4 aren't you?

I know there is no point in asking for an E.T.A. but, if you are looking for testers, you could always PM hawker and myself. We'd be happy to oblige! :D
Click to expand...

Hahaha yeah
Unfortunately first i have to make BFS working properly as it seems a bit difficult to do...then it would be good to have testers

Inviato dal mio GT-I9100 usando Tapatalk
 
Ditto. Neak 1.3.3 rocks. And now gadget check no longer seeming to use his beta testers, life is much less exciting. I'd happily do some testing too to brighten up my life again.
 
You must log in or register to reply here.
Back
Top Bottom