-
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
turbohobbit
Android Enthusiast
I have to say, I'm very happy with this. I was pondering last night whether or not I miss not being able to overclock, and to be honest I don't think I do. It's not like I play games or anything. I'm just wondering about undervolting by 50 pips at every step to see if I get even better battery out of it - or if I'll brick the handset!
You won't brick it but you might be unable to boot if you undervolt too much and commit the changes, so (a) reduce in 25mV steps (b) one frequency step at a time (c) checking stability between changes and (d) don't "set on boot" until you're confident the CPU is stable in deep sleep, under load and when scaling. Yes it's time-consuming and more than a bit tedious but it will ensure reliability.
Hawker
Android Expert
Its going to be a few days before the highly-anticipated (at least by me) v1.3 hits the streets. 
The NEAR team are developing a ROM for the kernel. I dont think its an actual firmware rom, but from what I can gather, I believe this will be a CWM Manager type of application that will allow NEAK users to perform CWM recovery manager-related tasks.
v1.4 will apparently also be compatible with CWM Manager.
The NEAR team are developing a ROM for the kernel. I dont think its an actual firmware rom, but from what I can gather, I believe this will be a CWM Manager type of application that will allow NEAK users to perform CWM recovery manager-related tasks.
v1.4 will apparently also be compatible with CWM Manager.
Sword Fish
Android Enthusiast
There are many of you here that state you are only loosing about 6-7% battery overnight when using this kernel. I am loosing 10% every 1.5 hour and can't for the life of me figure out why. I have my CPU Manager set to ondemand (100-800), wireless off, gps off. I do have three Exchange email accounts that sync, could that be a culprit? CPU spy shows that 74% of the time, my phone is running <200mhz with most of that in Deep Sleep. Battery Usage shows display as the biggest battery killer but it is usually never on.
I don't want to turn my phone into a "Stone" as it appears some have done but I should be able to get much better battery life then I am. My config show on my profile.
I don't want to turn my phone into a "Stone" as it appears some have done but I should be able to get much better battery life then I am. My config show on my profile.
ironass
Extreme Android User
Luckily, before being whisked away for New Year's Eve, I caught hawker's post about N.E.A.K. v1.2 and copied onto my phone quickly as I was having a rough ride with Siyah 2.6.3.
What can I say... I love it!
Quick and easy to install. Set on lulzactive + v(r)+100->800MHz and that was it. No scripts, 2nd Core, lulzactive app. Just used Voltage Control to knock it down to 800MHz and that was it. Simples!
As I was away I needed something that would not eat my battery and still give me performance... and it did not disappoint.
If I'm being critical, then I must say that perhaps lulzactive was not as smooth as I remembered it on v1.1 and could be a little choppy on slow scrolling in my App Drawer.
I did use the lulzactive app, free from the market, to tweak it and it was fine. I then, eventually, installed Conservative with the Lionheart tweak once I'd worked ot that hawkers kernel cleaner had removed the init.d file that they require. I just used Root Explorer to create the init.d file in system/etc and then booted into Recovery and used the NEAK option to enable Conservative and Lionheart.
Since Lionheart is only a, "tweak" to the Conservative governor, it does not appear in the list of governors as a seperate entity. You either enable, or disable, it in N.E.A.K. options in Recovery.
After 2 days on Conservative + v(r), a very smooth and fast combination, I found that there seemed to be little difference in battery life to lulzactive + v(r) although I did not have the time and wherewithal to test it accurately.
My battery, particularly over New Year's Eve and New Year's Day, was giving me more than enough life and certainly equalled, if not exceeded, my other previous favourite, Siyah v2.6.2, with all its tweaks and use of 2nd Core, (dubious about its need on Siyah now anyway), lulzactive app, Voltage Control and SetCPU... not to mention all the fiddling around with the settings and ThunderBolt scripts.
The Good
Very easy to install and requires the minimum of set-up and ancillary app's.
Depending on your phone, etc; you can use just Voltage Control to select the governor and scheduler of your choice, from a limited list.
Supports BLN (Back Light Notification) and boot animation.
Certainly gave me more than 24 hrs of, "normal", usage... i.e. calls, texts,browsing and playing funny video's and using the camera. Not fiddling, tweaking, rebooting and messing around as I usually do.
The Bad
This very small kernel, about half the size of Siyah, means that you have to enable/disable some features in Recovery, (just the once).
If you use the excellent hawker thermo nuclear kernel cleaner it deletes the init.d file and you have to manually replace it, as described above, although this changes in the next release of N.E.A.K., v1.3, which creates it on reboot.
Is only compatible with Samsung i9100 phone and Samsung based ROM's, (no CM or MIUI or ICS one's for intance).
The Ugly
Sydney99
By that I mean that as it doesn't seem to agree with Syd, the rest of us, particularly me, may have a fighting chance.
N.E.A.K. v1.3 should be out in the next few days and I will certainly be giving it a go.
What can I say... I love it!
Quick and easy to install. Set on lulzactive + v(r)+100->800MHz and that was it. No scripts, 2nd Core, lulzactive app. Just used Voltage Control to knock it down to 800MHz and that was it. Simples!
As I was away I needed something that would not eat my battery and still give me performance... and it did not disappoint.
If I'm being critical, then I must say that perhaps lulzactive was not as smooth as I remembered it on v1.1 and could be a little choppy on slow scrolling in my App Drawer.
I did use the lulzactive app, free from the market, to tweak it and it was fine. I then, eventually, installed Conservative with the Lionheart tweak once I'd worked ot that hawkers kernel cleaner had removed the init.d file that they require. I just used Root Explorer to create the init.d file in system/etc and then booted into Recovery and used the NEAK option to enable Conservative and Lionheart.
Since Lionheart is only a, "tweak" to the Conservative governor, it does not appear in the list of governors as a seperate entity. You either enable, or disable, it in N.E.A.K. options in Recovery.
After 2 days on Conservative + v(r), a very smooth and fast combination, I found that there seemed to be little difference in battery life to lulzactive + v(r) although I did not have the time and wherewithal to test it accurately.
My battery, particularly over New Year's Eve and New Year's Day, was giving me more than enough life and certainly equalled, if not exceeded, my other previous favourite, Siyah v2.6.2, with all its tweaks and use of 2nd Core, (dubious about its need on Siyah now anyway), lulzactive app, Voltage Control and SetCPU... not to mention all the fiddling around with the settings and ThunderBolt scripts.
The Good
Very easy to install and requires the minimum of set-up and ancillary app's.
Depending on your phone, etc; you can use just Voltage Control to select the governor and scheduler of your choice, from a limited list.
Supports BLN (Back Light Notification) and boot animation.
Certainly gave me more than 24 hrs of, "normal", usage... i.e. calls, texts,browsing and playing funny video's and using the camera. Not fiddling, tweaking, rebooting and messing around as I usually do.
The Bad
This very small kernel, about half the size of Siyah, means that you have to enable/disable some features in Recovery, (just the once).
If you use the excellent hawker thermo nuclear kernel cleaner it deletes the init.d file and you have to manually replace it, as described above, although this changes in the next release of N.E.A.K., v1.3, which creates it on reboot.
Is only compatible with Samsung i9100 phone and Samsung based ROM's, (no CM or MIUI or ICS one's for intance).
The Ugly
Sydney99
By that I mean that as it doesn't seem to agree with Syd, the rest of us, particularly me, may have a fighting chance.
N.E.A.K. v1.3 should be out in the next few days and I will certainly be giving it a go.
turbohobbit
Android Enthusiast
I've just "plugged and played". 100-1200 set on boot, and away I go. As I said above, I may fiddle with voltages but that's it. As for battery, I unplugged at 0700 this morning and after "normal" use (a couple of calls, a bit of texting some 'Book and tweeting, and downloading a couple of app updates) I'm still on 85%. The phone has been up for 33hrs 30mins now and 93% of that time has been at 100Mhz or less (62% of that in deep sleep: my phone spent 7hrs at 100Mhz overnight during charge, for some reason, although there are no partial wakeloks to speak of and it always does this so I'm not concerned).
For me this is the new weapon of choice.
For me this is the new weapon of choice.
ironass
Extreme Android User
That does sound very high old son.
To be honest I lose about 2% every hour when my phone is asleep. So about 12% in 6 hours. There are others like hawker who go catatonic and lose only 2% in the same period. It all depends on what you have running and when. I have K-9 email polling every hour. Wi-Fi on 24/7. Weather and news widgets updating. Not that this worries me at night as I usually have it charging.
Culprits for this could be... "Bloatware", particularly Wi-Fi sharing and Wi-Fi manager. Not to mention AP News plus others that may be running that you do not use.
Go to... Settings > Applications > Running Services and see what is running on your phone. You can also select Menu and see what is cached just to make sure that you want them there.
For a step-by-step guide to removing, "Bloatware", see here:-
http://androidforums.com/3213700-post161.html
You could also check that you are not signed into Latitude, another big eater of battery and one that some people do not sign out of properly sometimes.
Also you could possibly dim your screen display by using this method:-
http://androidforums.com/3761592-post1.html
Maybe also look at how often you are polling, say, email or updating your widgets. At hawkers prompting I went from syncing email every 20 min's to once an hour and it made a helluva difference. As did changing a couple of my News and Weather widgets for different one's that offered more control.
I hope this helps.
Hawker
Android Expert
ironass
Extreme Android User
Emilia Fox please!
Seriously, cheers hawker! Just so long as this version nukes as good as the last.
Sword Fish
Android Enthusiast
Do any of you guys use "System Power Saving"? Does it really do anything?
ironass
Extreme Android User
Personally, no.
It does however save you battery but at the expense of features and performance. I have enabled it reluctantly in the past when it has looked like I may not make it through until I can charge but it is something that I do not like to have to use if I can help it.
Hawker
Android Expert
Emilia Fox please!
Seriously, cheers hawker! Just so long as this version nukes as good as the last.
It most certainly does old man!
ironass
Extreme Android User
Ha! Ha! Ha!
Just used it to re-install N.E.A.K. v1.2 after trying the Phenomenal kernel and you little star... it does what it says on the box and left, or created, an empty init.d folder.
Looks like awhile before v1.3 is released as I see that the kernel will now come with all sorts of N.E.A.K. things. I really hope this does not detract from the kernel's development.
(P.S. Where's Emilia Fox?)
Hawker
Android Expert
There is a lot of talk about a NEAK ROM to be released this weekend.
There is not a lot of details about it on the Kernel thread. Firstly I took it as being a ROM-Manager type of application, but the way the thread is progressing it does indeed seem like it is going to be a firmware ROM.
If so, this is going to get VERY interesting!
There is not a lot of details about it on the Kernel thread. Firstly I took it as being a ROM-Manager type of application, but the way the thread is progressing it does indeed seem like it is going to be a firmware ROM.
If so, this is going to get VERY interesting!
Hawker
Android Expert
Ehy guys!!!
As promised to ironass, here i am to see what happens here!! I won't be able to do full support here, there is the Q&A thread on XDA about my kernel so all the questions pls ask them there...
Anyway, many thanks for doing so, i like when people share my work!
Welcome to the forum Simone.
Your kernel is causing quite a stir on here and is going down extremely well with many of us.
Looking forward to v1.3. Any clues on how your ROM is going to take shape?
Keep up the good work.
Sword Fish
Android Enthusiast
Ehy guys!!!
As promised to ironass, here i am to see what happens here!! I won't be able to do full support here, there is the Q&A thread on XDA about my kernel so all the questions pls ask them there...
Anyway, many thanks for doing so, i like when people share my work!
Ehy guys almost sounds Canadian!! Welcome, hope to see you around here going forward, your kernel has a lot of interest on this forum...
simone201
Newbie
For the ROM u should wait just a few days, in the weekend it will be out for sure....
Anyway, 1.3 will be out when the new NEAR ROM is ready, cuz we want to release them bundled....also NEAK kernel will be available separately as usual!
Is someone suffering of the "camera bug" mentioned in my OP on XDA?
@SwordFish:
fortunately i am Italian! XDDD
Hawker
Android Expert
For the ROM u should wait just a few days, in the weekend it will be out for sure....
Anyway, 1.3 will be out when the new NEAR ROM is ready, cuz we want to release them bundled....also NEAK kernel will be available separately as usual!
Any clue as to what version firmware/android OS the NEAR ROM will be based on Simone?
I've had no problems with the camera at all on neither v1.1 and v1.2
simone201
Newbie
Try to do so:
stock camera ---> lock screen ---> wait 30 secs ----> try to unlock
It should go into a SoD
About the ROM it will be KK5 based, and with graphics like MIUI
turbohobbit
Android Enthusiast
I'm happy with CheckROM, but if NEAK 1.3 is as good as the last few iterations have been you've got me for life!*
*(Or until something even better comes along )
*(Or until something even better comes along
)