Hawker
Android Expert
Same here butty.
Simone, have you changed anything in this version with regards to this kernels init.d support?
-
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
Same here butty.
Simone, have you changed anything in this version with regards to this kernels init.d support?
simone201
Newbie
As also i am writing on XDA, nothing has changed regarding init.d and for me works flawlessly lol
ironass
Extreme Android User
A few posts back, I said I would be a, "Happy Bunny", if I could get 24 -> 27 hours battery with my usage and set-up on this kernel...
Well, I'm a Happy Bunny!
Before anyone posts that 24 -> 27 hours is nothing because they can get 48 -> 72 hours on their phone... I did say, "with my usage and set-up".
Why 24+ hours you may ask? Don't you just charge it up every night?
Well, the answer is, yes, I do but then I like to have a reserve so that I'm not worried about using my phone if I'm out-and-about or in case I don't make it home until the following morning... it happens!
Personally, I didn't get a top of the range smartphone, that is packed with features, to treat it like a stone. I could have stuck with my very old Nokia 3210 for that.
Neither do I want to become a slave to my phone and have to worry about turning Wi-Fi off every time I leave the house or re-enabling GPS or disabling background data and auto sync or even switching to GSM and fiddling about to manually adjust the brightness.
I want my location based weather widget to update along with my news and calendar widgets and my WhatsApp and email accounts to carry on sync'ing along with my Contacts and Tasks.
Sure, if someone comes up with a suggestion that saves me battery, that doesn't detract from my usage of the phone, I will take it on board. Our very own hawker did that recently by suggesting that I switch clock/weather widgets to a virtually identical one that was more configurable and did not poll when I was asleep.
Which brings me back to the N.E.A.K. v1.3 kernel. It is one of those items that I mentioned that I don't, or shouldn't, have to worry about once it's set up and can potentially save a lot of battery for me without impairing performance.
I'm happy to say simone, that it does. I resisted the temptation to install the latest Siyah 2.6.6 kernel when it came out within hours of the N.E.A.K. v1.3 release as I wanted to give it at least a couple of days trial.
I initially started with Lionheart + v(r) which was very smooth and slick on my phone. After one cycle I then changed to lulzactive + v(r) and after a couple of tweaks with the lulzactive app, it too was running sweetly on the same u/v and u/c for Lionheart. I also used the 2nd Core app for Dynamic hotplug on both, although I'm still not sure if this is needed on the latest kernels!
N.E.A.K. has consistently liked my phone and usage patterns and the v1.2 served me well over the festive holidays after a Siyah kernel had left me with a flat battery at a pre Christmas party and I had to borrow an iPhone, (the shame) to make a call.
I have yet to delve into the world of, "Thunderbolt" scripts for either this or the Siyah kernel and so cannot comment on whether these would improve, what is for me, a really great kernel.
Perhaps someone might like to comment on the use of Thunderbolt with N.E.A.K..
The bottom line is that when I first started using my phone some 8 months ago, I was getting around 10 -> 12 hours battery usage. Now, thanks to developers like simone, as well as rooting, removing bloatware and optimising my app's and settings... I'm getting more than double that.
Well, I'm a Happy Bunny!
Before anyone posts that 24 -> 27 hours is nothing because they can get 48 -> 72 hours on their phone... I did say, "with my usage and set-up".
Why 24+ hours you may ask? Don't you just charge it up every night?
Well, the answer is, yes, I do but then I like to have a reserve so that I'm not worried about using my phone if I'm out-and-about or in case I don't make it home until the following morning... it happens!
Personally, I didn't get a top of the range smartphone, that is packed with features, to treat it like a stone. I could have stuck with my very old Nokia 3210 for that.
Neither do I want to become a slave to my phone and have to worry about turning Wi-Fi off every time I leave the house or re-enabling GPS or disabling background data and auto sync or even switching to GSM and fiddling about to manually adjust the brightness.
I want my location based weather widget to update along with my news and calendar widgets and my WhatsApp and email accounts to carry on sync'ing along with my Contacts and Tasks.
Sure, if someone comes up with a suggestion that saves me battery, that doesn't detract from my usage of the phone, I will take it on board. Our very own hawker did that recently by suggesting that I switch clock/weather widgets to a virtually identical one that was more configurable and did not poll when I was asleep.
Which brings me back to the N.E.A.K. v1.3 kernel. It is one of those items that I mentioned that I don't, or shouldn't, have to worry about once it's set up and can potentially save a lot of battery for me without impairing performance.
I'm happy to say simone, that it does. I resisted the temptation to install the latest Siyah 2.6.6 kernel when it came out within hours of the N.E.A.K. v1.3 release as I wanted to give it at least a couple of days trial.
I initially started with Lionheart + v(r) which was very smooth and slick on my phone. After one cycle I then changed to lulzactive + v(r) and after a couple of tweaks with the lulzactive app, it too was running sweetly on the same u/v and u/c for Lionheart. I also used the 2nd Core app for Dynamic hotplug on both, although I'm still not sure if this is needed on the latest kernels!
N.E.A.K. has consistently liked my phone and usage patterns and the v1.2 served me well over the festive holidays after a Siyah kernel had left me with a flat battery at a pre Christmas party and I had to borrow an iPhone, (the shame) to make a call.
I have yet to delve into the world of, "Thunderbolt" scripts for either this or the Siyah kernel and so cannot comment on whether these would improve, what is for me, a really great kernel.
Perhaps someone might like to comment on the use of Thunderbolt with N.E.A.K..
The bottom line is that when I first started using my phone some 8 months ago, I was getting around 10 -> 12 hours battery usage. Now, thanks to developers like simone, as well as rooting, removing bloatware and optimising my app's and settings... I'm getting more than double that.
turbohobbit
Android Enthusiast
Hear hear! EXACTLY the same for me, even with regards to attitude towards useage and performance - why have a smart phone if you only want it to make calls? I still need to tweak things a bit - I'll have a look at the Lulzactive app - but I've pretty much ditched Siyah now for this. As I've said before, I'm getting excellent performance from N.E.A.K and all the customisations and extra fiddling that Siyah needed to get the best out of it was beginning to do my head in.
Ironass what settings are you using in the Lulzactive app and what undervolting are you employing?
Ironass what settings are you using in the Lulzactive app and what undervolting are you employing?
ironass
Extreme Android User
I'll PM them to you.
Not that it will probably do you any good as different CPU's and usages require different settings.
turbohobbit
Android Enthusiast
Cheers buddy!
ironass
Extreme Android User
Nice one simone!
Look, I don't mean to be pushy mate, but could you release v1.3.1 on, say, Thursday, This would give me a couple of days to try Siyah 2.6.6 or 2.6.6i.
Before you say anything... I am rearranging the words... cheeky, ironass, sod, you.
simone201
Newbie
Nice one simone!
Look, I don't mean to be pushy mate, but could you release v1.3.1 on, say, Thursday, This would give me a couple of days to try Siyah 2.6.6 or 2.6.6i.
Before you say anything... I am rearranging the words... cheeky, ironass, sod, you.
Yeah sure, i think it will be ready on friday
ironass
Extreme Android User
Hawker
Android Expert
Just in time for the NEAR release then Simone!
Or will this come preloaded with NEAK 1.4?
simone201
Newbie
Just in time for the NEAR release then Simone!
Or will this come preloaded with NEAK 1.4?
With NEAR 1.0x it will be preloaded NEAK 1.3.1x-Plus that is a modded version of original neak with some exclusive goodies!
Hawker
Android Expert
If we want to try NEAR with different kernels (eg. Siyah), and decide to go back to the original NEAR/NEAK kernel, will this version of the kernel be downloadable in its own right or would a reflash of the ROM be required?
Sorry for the questions Simone, but if your kernel is anything to go by, NEAR sounds like a mouth watering prospect!
Sorry for the questions Simone, but if your kernel is anything to go by, NEAR sounds like a mouth watering prospect!
steslatt
Android Expert
If we want to try NEAR with different kernels (eg. Siyah), and decide to go back to the original NEAR/NEAK kernel, will this version of the kernel be downloadable in its own right or would a reflash of the ROM be required?
Sorry for the questions Simone, but if your kernel is anything to go by, NEAR sounds like a mouth watering prospect!
If its bundled with the rom you will be able to extract it from the rom zip and flash separately.
simone201
Newbie
Definitely the best kernel out there right now...for a user like me who cannot understand all these tweaking and customisation with scripts....
Meets my requirement of running the whole day without charging without worrying about turning off data or wifi.....running conservative with slight UV ... No lags no sod...just perfect...
Meets my requirement of running the whole day without charging without worrying about turning off data or wifi.....running conservative with slight UV ... No lags no sod...just perfect...
ironass
Extreme Android User
N.E.A.K. 1.3.1 is up!
CHANGELOG (since 1.3):
KERNEL:
- Added support for ARM_ERRATA_754322 & ARM_ERRATA_754327
- Enabled ARM_ERRATA_754322 & ARM_ERRATA_754327
- A bit tweaked conservative gov to be a little more battery friendly
- Added support for vdd_levels (for Tegrak's Overclock)
- Some RAM Undervolt (1.1V)
- nohz: Fix update_ts_time_stat idle accounting
- sched_features: NO_GENTLE_FAIR_SLEEPERS
- cpuidle: Stop spamming the kernel message buffer when enabling AFTR
- Various general patches from upstream
INITRAMFS:
- Unsecured Kernel (adb root in recovery)
- Fixed a few CWM Issues
- Small cleanup file for issues with Thunderbolt!
MISC:
- A lot of compiler warning fixes (really a lot!)
- Added J4FS support (for param.lfs)
- Now supports Hellcat's Bootlogo App (from market)
Default is lulzactive + vr. Will give it the heavy u/v treatment to see if I can break it!
EDIT lulzactive + sio didn't respond well to my heavy u/v. So am on Lionheart + sio with sched_mc enabled.
Very odd! I just flashed Conservative and sched_mc and it's stuck on the yellow triangle. Thinking it,s my heavy u/v I flashed the Voltage Control remove .zip... but still stuck on yellow triangle! Will use hawker's kernel cleaner again.
OK... panic over! I used the kernel cleaner + NEAK's voltage remover and it's booting OK.
PUB!!!
CHANGELOG (since 1.3):
KERNEL:
- Added support for ARM_ERRATA_754322 & ARM_ERRATA_754327
- Enabled ARM_ERRATA_754322 & ARM_ERRATA_754327
- A bit tweaked conservative gov to be a little more battery friendly
- Added support for vdd_levels (for Tegrak's Overclock)
- Some RAM Undervolt (1.1V)
- nohz: Fix update_ts_time_stat idle accounting
- sched_features: NO_GENTLE_FAIR_SLEEPERS
- cpuidle: Stop spamming the kernel message buffer when enabling AFTR
- Various general patches from upstream
INITRAMFS:
- Unsecured Kernel (adb root in recovery)
- Fixed a few CWM Issues
- Small cleanup file for issues with Thunderbolt!
MISC:
- A lot of compiler warning fixes (really a lot!)
- Added J4FS support (for param.lfs)
- Now supports Hellcat's Bootlogo App (from market)
Default is lulzactive + vr. Will give it the heavy u/v treatment to see if I can break it!
EDIT lulzactive + sio didn't respond well to my heavy u/v. So am on Lionheart + sio with sched_mc enabled.
Very odd! I just flashed Conservative and sched_mc and it's stuck on the yellow triangle. Thinking it,s my heavy u/v I flashed the Voltage Control remove .zip... but still stuck on yellow triangle! Will use hawker's kernel cleaner again.
OK... panic over! I used the kernel cleaner + NEAK's voltage remover and it's booting OK.
PUB!!!
ironass
Extreme Android User
Early feedback on N.E.A.K. 1.3.1.
Yesterday evening v1.3.1 was released and I installed it immediately.
I originally used the default lulzactive+vr with the same heavy u/v that I had used on Siyah 2.6.7. However, there seemed to be a bit of a lag on this which was only to be expected as I had used ondemandx+sio on Siyah.
I therefore rebooted and selected Conservative and Lionheart from the NEAK options and installed them but when I came to reboot, my phone hung at the yellow warning triangle and would not budge.
I thought that the Voltage Control settings were the problem and used vcremove.zip to no avail. I then used NEAK's voltage removal option, again, to no avail. Finally I used hawkers, kernel cleaner and reinstalled N.E.A.K. 1.3.1 and it booted up OK but with lulzactive+vr again.
I have, this morning read on the xda forum that there is an issue with rebooting after installing Conservative/Lionheart governor that I was unaware of at the time.
By now I was running out of time as I had to go out and so I threw my Siyah 2.6.7, heavy u/v settings on.
When I got to the party I found that I had the SOD and simply upped my voltage by +25 across the board from 100 -> 800Mhz, the range I was using.
In fairness to simone and N.E.A.K., this was not the most scientific way of doing things and I'm sure I could have improved the u/v if I had more time.
Having said that, I've had no FC's, SOD's and was using the video camera and stills, as well as playback, with no problems. Using lulzactive like this was not as smooth as ondemandx on Siyah and I will be installing Conservative or Lionheart and tweaking the voltages properly.
What follows are 2 screenshots. One of Siyah 2.6.7 and one of N.E.A.K. 1.3.1. Both are taken, roughly, after 12.5 hours in use.
N.E.A.K. 1.3.1
Siyah 2.6.7
Yesterday evening v1.3.1 was released and I installed it immediately.
I originally used the default lulzactive+vr with the same heavy u/v that I had used on Siyah 2.6.7. However, there seemed to be a bit of a lag on this which was only to be expected as I had used ondemandx+sio on Siyah.
I therefore rebooted and selected Conservative and Lionheart from the NEAK options and installed them but when I came to reboot, my phone hung at the yellow warning triangle and would not budge.
I thought that the Voltage Control settings were the problem and used vcremove.zip to no avail. I then used NEAK's voltage removal option, again, to no avail. Finally I used hawkers, kernel cleaner and reinstalled N.E.A.K. 1.3.1 and it booted up OK but with lulzactive+vr again.
I have, this morning read on the xda forum that there is an issue with rebooting after installing Conservative/Lionheart governor that I was unaware of at the time.
By now I was running out of time as I had to go out and so I threw my Siyah 2.6.7, heavy u/v settings on.
When I got to the party I found that I had the SOD and simply upped my voltage by +25 across the board from 100 -> 800Mhz, the range I was using.
In fairness to simone and N.E.A.K., this was not the most scientific way of doing things and I'm sure I could have improved the u/v if I had more time.
Having said that, I've had no FC's, SOD's and was using the video camera and stills, as well as playback, with no problems. Using lulzactive like this was not as smooth as ondemandx on Siyah and I will be installing Conservative or Lionheart and tweaking the voltages properly.
What follows are 2 screenshots. One of Siyah 2.6.7 and one of N.E.A.K. 1.3.1. Both are taken, roughly, after 12.5 hours in use.
N.E.A.K. 1.3.1
Siyah 2.6.7
turbohobbit
Android Enthusiast
I got some fairly heavy-duty SOD this morning after a cold start (powered the phone down overnight to give it a charge and generally let everything wipe and reset - I do that once a week or so). Couldn't get beyond the first Samsung screen so I flipped into Nandroid and reflashed 1.3. To be honest this is the first time I've had a problem with N.E.A.K so fair play, but it did give me a bit of a shiver for a while!
Sydney99
Android Expert
Hawker
Android Expert
After siyah 2.6.8 lost my haptic feedback i thought I'd take the opportunity and Install neak 1.3.2.
I must say it seems excellent so far. Very smooth on defaults (lulz/vr/200/1200).
Now to see if I can push these voltages as much as I could in siyah 2.6.7!...
Edit:
Yup. Seems very stable even with my pretty aggressive under volting.
This seems very good indeed to be honest. Hats off to you Simone. Siyah 2.6.7 has a serious rival.
Obviously I cannot compare it with siyah's very good battery life yet so this shall be a very interesting test tonight.
I must say it seems excellent so far. Very smooth on defaults (lulz/vr/200/1200).
Now to see if I can push these voltages as much as I could in siyah 2.6.7!...
Edit:
Yup. Seems very stable even with my pretty aggressive under volting.
This seems very good indeed to be honest. Hats off to you Simone. Siyah 2.6.7 has a serious rival.
Obviously I cannot compare it with siyah's very good battery life yet so this shall be a very interesting test tonight.
