yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] :
Here is v3.1: http://d-h.st/4Ms (UNTESTED)

-I haven't tested this one because I'm currently running a battery drain study and can't flash this

-PM_FAST fixed

-CRT animation fixed (???? please report back)

-IDLE2 enabled and fixed at 400
[Nexus S Android Development] noobiekins:
is there any power savings from lcd voltage reduction?
[Nexus S Android Development] alen1901:
working on i9023. crt fixed. didnt try idle2. ;)

EDIT: jellybelly 0.1.5.1
[Nexus S Android Development] :
Yes, but I'm not brave enough to meddle with that yet.

Thanks for reporting back alen1901!

You can see IDLE2 is working at 400MHz if you start a playlist, reset CPUSpy, then turn your screen off. Wait a minute or so... Turn the screen back on, click refresh in CPUSpy, and it'll show you that the frequency used was 400MHz.
[Nexus S Android Development] alen1901:
i know, i just flashed rom and kernel, didnt have time, give me 5minutes. ;)

---------- Post added at 01:19 AM ---------- Previous post was at 01:13 AM ----------

idle2 at 400mhz, tested and working. ;)
[Nexus S Android Development] Articudos:
http://db.tt/TBw0ywGi

Just had a reboot with v3.1, ondemand deadline.

But I dunno why there is kalimochoaz's name, not yours..:confused:
[Nexus S Android Development] 309041291a:
Well Bedalus I HATE to admit I'm wrong but.... After a few charge cycles I'm sitting here with 58%, 3 hours and 14 minutes on-screen time. All thanks to Deadline + Ondemmand. Deadline has never worked for me before even after charge cycles but all of a sudden it's like magic!

Nexus S (GMS i9020a)

Paranoid (1.6 - 4.0.4)

Matrix Kernel (CFS - 20.0)

Ondemmand (800/100)

Deep Idle (On - Deadline)

Live OC - 100 (400/800)

BLX - 98 (Inverted Apps)
[Nexus S Android Development] JokerAce:
If you continue to keep using the battery to such low power, it will reduce greatly the number of cycles you can use the battery for.

May I know what battery are you using? Stock? And the mAh of it.
[Nexus S Android Development] sdhanjal15:
I don't care....I can buy another one??

Sent from my Nexus S
[Nexus S Android Development] simms22:
you use clockwork mod recovery? thats the recoveries kernel. looks like you had a reboot from recovery. try twrp recovery.

---------- Post added at 11:15 PM ---------- Previous post was at 11:14 PM ----------

ive been saying this for years now :p
[Nexus S Android Development] 309041291a:
Stock battery, when I have Deep Idle off my phone actually idles well and has the same battery, I just noticed I had it enabled. I usually have it off, which explains the drain. If I had it off the idle line would be flat, so don't mind the shirt usage time I can always get at least 18 hours total.

Wow. Wouldn't it be crazy if I got 7 hours? WiFi never saves me any more than 2G does. Actually I lie. It saves about half an hour of battery on-screen. 3G drains a lot more.

So yeah, I am on another kernel BUT I'm using the settings bedalus uses as default for ondemmand and I'm using deadline. When I convert to JB I'm going to test bedalus's kernel again.

Nexus S (GMS i9020a)

Paranoid (1.6 - 4.0.4)

Matrix Kernel (CFS - 20.0)

Ondemmand (800/100)

Deep Idle (On - Deadline)

Live OC - 100 (400/800)

BLX - 98 (Inverted Apps)
[Nexus S Android Development] Articudos:
Thanks.I'm using cwm 5.8.0.2, Is it kind of mixing?

So... Do I have to install kernel again using twrp?:)
[Nexus S Android Development] drac0:
Then lets wait for that CM version, maybe I just try ART once more :D
[Nexus S Android Development] leap_ahead:
bln work when I put lights.s5pc110.so from other kernel zip to rom lib
[Nexus S Android Development] :
Sorry yes, I removed it from the old zip while I was cleaning it up. I forgot it was required.

I'll include it in the next version.
[Nexus S Android Development] leap_ahead:
what new is coming ?

also the last work on 4.2.2*need 6 lib files
[Nexus S Android Development] -[-Xehanort-]-:
Welcome back!! :good:

Really miss your kernel on Nexus S! :)

gonna try v10 soon!
[Nexus S Android Development] :
This device is now a classic! Nice to hear from you :)

OC is actually included, I just didn't list it because I hadn't tested it yet, but it appears to be working fine.

I learned a lot from developing my own cpu frequency governor on the nexus 4. In fact, despite being very late to that scene, I developed quite an original tweak allowing the processor to run at lower speeds, with the GPU handling all the graphics smoothly with an increased bus.

I plan to do a similar thing here, and hook into the GPU code to prevent the CPU from scaling down to 100 if the GPU is active. This should improve smoothness, with a minor battery cost.

Perhaps I may even try to have max bus speeds at 200 and up at all times, and aim for lower CPU frequency usage. If it's possible, and I can get the balance right, it should provide an improvement in performance with no battery cost.
[Nexus S Android Development] :
I'm only interested in supporting 4.4.* ROMs.

I've got the lib lights file. I don't think there are any others for 4.4.* ROMs are there?
[Nexus S Android Development] KrisMurdrum:
Yeah it was a resilient little bugger, probably wouldn't have gotten the N⁴ it the screen hadn't met it's maker.

How the bloody hell did miss you making a N⁴ kernel?
[Nexus S Android Development] :
I didn't want the attention. You'll find moob in general, flash it and let me know what you think
[Nexus S Android Development] drac0:
Wow that sounds like science fiction now :D I'm so gonna enjoy this old device even more. Was about to switch to Nexus 5 but this old crespo just refuse to die, incredible device a true classic!

I love your ideas about CPU/GPU scaling, it has so much more potential!

[MENTION=4128576]bedalus[/MENTION] few questions :)

Can you keep CPU at 100 MHz at all times while in deep sleep?

Also, is it possible to kill capacitive buttons and use them only as notification, and start using nav buttons? Saw that with PA ROM but it can be manually triggered in build.prop with "qemu.hw.mainkeys=0" or something like that, this is good now cos we have immersive mode in KK ROMs.

What scheduler do you plan to use with your own governor?

Thanks again for coming back, it feels like I bought this NS one more time! Eager to test baby! :cowboy:
[Nexus S Android Development] KrisMurdrum:
I'll look into it in a bit. Currently I'm taping together boxes

I also have to make sure you've got any kernel[\I] version to minimize interference with the Android L port I'm currently using
[Nexus S Android Development] :
Yep it's any kernel. Good luck with the box taping!?
[Nexus S Android Development] :
1. I did a whole study just on battery use. The most power-saving frequency was 400 or 800 MHz with deep idle, but it wouldn't be stable. It doesn't matter how fast the CPU is going when the screen is off, because as soon as any processing is finished, the processor will essentially be off.

2. May be possible, but I'm not doing it

3. CFQ - I've tested everything every way possible and CFQ consistently wins.
[Nexus S Android Development] :
Warning, flashing this will wipe your init.d scripts

Version 10.1

AOSP: http://d-h.st/PiJ

* * *

CM based: http://d-h.st/PZQ

Changelog: v10.1

- Enable selinux

- Enable zcache

- Remove huge amount of code by disabling tracing and kallsyms

- Build CM version

- Add BLN libs

v10.0

- Samsung jellybean kernel source latest

- BLN/BLD/Fastcharge added

- Voodoo sound/colour added with my colour as default (most stable whitepoint at different brightnesses)

- My ondemand and fixed bus speed at 200 MHz

- Battery 100% fix

- CFQ as default io scheduler

- Extra free memory enabled

- Haptic strength sysfs

- PM fast to fix wifi speeds and bluetooth fix

- MTP
[Nexus S Android Development] Setting.Out:
v10.1 cm

booted to a blank screen, but the buttons were lit up.. I waited for a few minutes and it did a reboot, finished the reboot and I got an error message saying my launcher has stopped, then the screen stayed blank, the launcher finally started super slow then the pin unlock.. It feels very sluggish and unresponsive.. :(

It really feels like I flashed an aosp kernel on cm.. ??

I also did a system check and it completely deleted all my init.d scripts
[Nexus S Android Development] :
WARNING to other users:

Sorry about the scripts. I hope you have backups.

The kernel does support init.d scripts, so I'll have to investigate why that happened.

It might be that CM have made further changes to the display drivers since I last built for them
[Nexus S Android Development] Setting.Out:
No worries.. I always have backups.. :)

I didn't have a logcat app installed, but I tried to pull a log off my performance control app.. I hope this helps.. :)
[Nexus S Android Development] makanorang12:
Our legend is back thanks bedalus
[Nexus S Android Development] DerTeufel1980:
You could take a look at the github of pawitp. There's a branch cma test. With this commits, video driver frees its unused ram, and reallocates it when needed. This gives you about 430mb ram without breaking anything
[Nexus S Android Development] :
That's fantastic!
[Nexus S Android Development] ekerazha:
It looks somewhat tricky to port and maintain, since we have to add the whole CMA system.
[Nexus S Android Development] DerTeufel1980:
That's right. That's what pawitp did for aries as well. Now I guess it's almost only cherry-picking :) maybe copy some stuff from mach-aries to mach-hering
[Nexus S Android Development] ekerazha:
I'm going to try cherry picking every commit since Dec 31, 2013... then we could look upstream if there are additional fixes to CMA.
[Nexus S Android Development] ekerazha:
This Galaxy S kernel http://xdaforums.com/showthread.php?t=2662853 used to have CMA but its developer removed it in the latest release because of stability issues, see: http://xdaforums.com/showpost.php?p=52897298&postcount=253
[Nexus S Android Development] :
We're talking about these commits, right? https://github.com/DerRomtester/android_kernel_samsung_aries/commits/kk-notest/mm?page=1

It does look like code that without full knowledge of the subsystem it could easy wreck. What else is required? Changes in mach-s5pc100?

EDIT: Yeah, here's the commit https://github.com/DerRomtester/and...mmit/5b2812709891c72aefeba59d264ddf8e33316ec8

It looks like it is not water-tight yet.
[Nexus S Android Development] :
You know, I think I got the the AOSP and CM version back-to-front?

Has anyone tested the one I labelled as AOSP on an actual AOSP ROM? Did it work?

(I'm going to push new versions shortly anyway...)
[Nexus S Android Development] drac0:
Tried with cn.fyodor AOSP, couldn boot. Same as with CM on latest CM nightly.
[Nexus S Android Development] Setting.Out:
Any chance at smartassv2 and row?.. And I was curious about bfq, I've seen it has had several updates..

---------- Post added at 07:19 PM ---------- Previous post was at 07:16 PM ----------

Did you try the CM version / AOSP version on both? As in cm on AOSP and AOSP on CM...
[Nexus S Android Development] drac0:
You mean one on another and vice versa, no I didnt. Once i saw it doesnt boot after a few mins I got back to Omni build testing ART :)
[Nexus S Android Development] :
Version 10.2

AOSP: http://d-h.st/MIY

* * *

CM based: http://d-h.st/B43

Changelog: v10.2

- Fix bug where init.d scripts were wiped

- Switch to xz compression for smaller download

- Enable build optimisation flags

- Correct custom IO control patch for CM version

Changelog: v10.1

- Enable selinux

- Enable zcache

- Remove huge amount of code by disabling tracing and kallsyms

- Build CM version

- Add BLN libs

v10.0

- Samsung jellybean kernel source latest

- BLN/BLD/Fastcharge added

- Voodoo sound/colour added with my colour as default (most stable whitepoint at different brightnesses)

- My ondemand and fixed bus speed at 200 MHz

- Battery 100% fix

- CFQ as default io scheduler

- Extra free memory enabled

- Haptic strength sysfs

- PM fast to fix wifi speeds and bluetooth fix

- MTP
[Nexus S Android Development] :
Can someone feed back if the cm version worked this time? If not I believe the answer is in here: https://github.com/SlimRoms/kernel_samsung_crespo/commits/kk4.4/drivers/video

I can pick these commits tomorrow if necessary
[Nexus S Android Development] Setting.Out:
Just booted up, so far, so good... Feels fine, but I'll let it settle and push it around a bit.. ;)

Small question.. The version says 3.0.31 your old kernel was 3.0.89.. Is this an older or newer linux kernel base?
[Nexus S Android Development] :
The CM version is now working yes?

It's the latest samsung kernel base, what's missing is the mainline patches.
[Nexus S Android Development] Setting.Out:
Yes, the CM version..

Just completed some flawed benchmark apps.. lol..

CyanAOSP on quadrant gets 2200 - 2300+ with Devil, and 1800+ Marmite..

With Antutu 5600 - 5700+ with Devil and 5000+ with Marmite..

Minus the benchmark apps, the load time on all apps and overall peppiness does feel a tiny bit slower..

I will see how battery life goes.. :)

Thanks for the build, it is really good to have you back.. :)
[Nexus S Android Development] :
This is with performance governor and same top frequency?

I used to go to town on benchmarks. Back in the ICS days: https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdGpWaWxiUjVMbVFHWU82R0t1bWtHZ1E#gid=0

AnTuTu: RAM; CPU integer

Linpack: multithread

Vellamo: Sun Spider

I've got a post-grad in maths education. I'm pretty good at statistics. I did regression testing to find that the above tests are the give the most representative scores. As with any benchmark, test conditions should be identical, and should be run multiple times to ensure confidence in the results.

Further reading on my early nexus s work can be found here: http://xdaforums.com/nexus-s/general/ref-bedalus-rd-compendium-t1639689
[Nexus S Android Development] drac0:
Latest Omni and latest CM nightly everything working like a charm.

I'm gonna try with your Ondemand/CFQ and see how it goes with smoothness and battery life, I dont know is it some placebo but everything is buttery smooth, thanks for this build and hope you make it even better! Testing time ... :D
[Nexus S Android Development] Setting.Out:
I do multiple tests at full battery, no apps running, but at stock speeds ie 100/1000 because I like to see how it performs as I actually use the ROM.. I know this is less accurate, but I don't rely on the apps as accurate either.. ;)

I was writing this message once already when I had a random reboot.. Only the XDA app was running, no oc'ing stock scheduler/governor.. Couldn't pull a log for you as my scripts apparently cleared them on the reboot.. lol
[Nexus S Android Development] :
Soft or hard reboot?

You really need to set the performance governor to do these tests, and I recommend at least using linpack multithread (the app is free) to ensure a fair comparison.
[Nexus S Android Development] :
I'm just bookmarking some commits I'm going to investigate tomorrow:

https://github.com/bedalus/hxore/commit/b309bd7e474e9802dc446d8df862bd8324100fc8

https://github.com/bedalus/hxore/commit/e9562c7d125c38bdcbfa57f631e6c7a3eba801f3

https://github.com/bedalus/hxore/commit/c89531a941ff05ab3aefdcfa6dbdab120340ee2f

https://github.com/bedalus/hxore/commit/9ade12e75e14b70184be318beab71bcb3777377d
[Nexus S Android Development] Setting.Out:
Soft, I'll run the comparison again.. ;)

---------- Post added at 10:12 PM ---------- Previous post was at 09:46 PM ----------

Okay, Three tests each on Linpack, multi-thread.. Performance/cfq

Marmite:

1st

Mflops: 19.009

Time: 8.87

Norm Res: 3.24

Precision: Inconsistent

2nd

Mflops: 18.739

Time: 9.0

Norm Res: 3.24

Precision: 2.220446049250313E-16

3rd

Mflops: 19.076

Time: 8.84

Norm Res: 3.24

Precision: 2.220446049250313E-16

Devil

1st

Mflops: 16.273

Time: 10.37

Norm Res: 3.24

Precision: Inconsistent

2nd

Mflops: 16.428

Time: 10.27

Norm Res: 3.24

Precision: 2.220446049250313E-16

3rd

Mflops: 16.665

Time: 10.12

Norm Res: 3.24

Precision: 2.220446049250313E-16

---------- Post added at 10:53 PM ---------- Previous post was at 10:12 PM ----------

Just an observation, when I flash your kernel, I get two module files, the original that came with the rom in lib and is still active and yours that is in system.. both have .ko files, could they be conflicting?.. I ask this because, when I reverted back to Devil, it was significantly slower, both in test and in feel.. I proceeded to wipe and reinstall the system, and all was back to normal?.. is it just the duplicate files?
[Nexus S Android Development] :
Firstly, that's a huge win for Marmite. (Don't forget to switch back to ondemand)

The .ko files you're referring to, I'm not sure I'm following you... Can you be more specific about which files?
[Nexus S Android Development] drac0:
Just realized, BLN and BLD not working in CM latest nightly although enabled in settings. Went back to latest Omni to double check and BLN works fine. Both ROMs using CM version of kernel.

Also Omni feels much more snappier with Ondemand/CFQ than CM, but that could be due to ROM polish.
[Nexus S Android Development] ottoemezzo:
I installed 10.2 on top of latest slimkat and although I've only been using it for an hour I have to say my phone feels very snappy. Also no problems with bln here. Thank you bedalus!
[Nexus S Android Development] Setting.Out:
Its the wait to scan ko files.. I moved yours replacing the existing file in system/lib/modules and there's a HUGE difference in the ROM.. It now tests (using prior method) above Devil on Antutu (5700+), but slightly lower still than Devil on Quadrant (2000+)..
[Nexus S Android Development] teoserio:
Those are the kind of posts that i was really missing from you on NS forum. Pure knowledge for our brains [emoji4]
[Nexus S Android Development] :
The results from quadrant were so wildly variable that nobody should be using it for anything!
[Nexus S Android Development] Setting.Out:
Yes, but the difference a file made was significant.. If you repack the .zip with the modules folder moved into (system/lib) instead of just (system) it removes a conflicting duplicate file and then the kernel really perks up..
[Nexus S Android Development] :
Yes, it's a good catch and I see your point. But quadrant is still awful for a benchmark
[Nexus S Android Development] drac0:
There is a strange bug with CM nightly and M8 as well. Once you boot and leave the screen on not touching anything, CPU will burn at max speed you have set, until you turn off the screen. Once you're back its scaling as usual and goes at min. Battery drain while CPU is at max is HUGE, lost 3% in one minute that is set to turn off the screen. Can anybody confirm?

Also now I can confirm BLN and BLD are not working in both stable branch M8 and nightly CM. Guess they altered some settings.

Will test further and paste a log if necessary.
[Nexus S Android Development] Setting.Out:
While using this kernel?..

I was going to do a better report on battery life, but I am in the habit of plugging it in at night.. ;) So after only six hours, one hour of screen time, I'm sitting at 67%.. I don't have any issues on CyanAOSP with frequencies staying at full, and it seems to sleep well using minimal battery.. :)

Also, it seems more stable after fixing the duplicate issue..

---------- Post added at 01:00 PM ---------- Previous post was at 12:54 PM ----------

**

Spoke too soon, as I had another random reboot.. :(

---------- Post added at 01:21 PM ---------- Previous post was at 01:00 PM ----------

**

And another random reboot, the one prior was while typing on the XDA app, the last one was while watching YouTube..
[Nexus S Android Development] drac0:
Yes, while using 10.2 CM version, btw nice habbit :D

Seems its behaving kinda strange with CM cos I havent seen any of these issues with Omni.

As you can see in screenshots, while plugged in USB port without Fastchage, CPU remained at his min settting at 200 MHz, while the screen was off.

Then I thought ok lets change to 100 MHz and see what happens. It remained on 100 MHz again while screen was off.

After that just took it off USB and double check the setting, ONDEMAND/CFQ, default values, turned it off and let it be. Later checked and it was in deep sleep as it should have. Other than that battery life is pretty good.

I'm not sure if this is kernel feature while being on USB to not go into sleep while screen off or its just related to CM like those BLN and BLD broken libs.

Last try gonna test AOSP then see what happens.
[Nexus S Android Development] spider623:
the kernel lives?

how long has it been since i moved to nexus 4?
[Nexus S Android Development] drac0:
Didnt have single reboot, on the contrary not even the wakelock nor the infamous systemui bug with the latest CM nightly, except for these earlier mentioned, but on aosp this kernel is blazing fast with ART :D think im gonna stay that way for a while ...

---------- Post added at 02:52 PM ---------- Previous post was at 02:49 PM ----------

IT LIVES! :laugh: get your crespo back!
[Nexus S Android Development] spider623:
i got it back but there are no lightweight kitkat roms for it!
[Nexus S Android Development] rakeshbro:
M facing problem with da latest version kernel, rom 4.4.3 aosp.

The problem is google play store getting fc and can't access setting>storage.

I thought i did something nasty and this problem start occurring then i wiped rom, flashed rom gapps and kernel same problem.

Can i flash 10.0 over 10.2? i need to setup the device and need to install some apps from gplay.
[Nexus S Android Development] drac0:
Try latest Omni,

http://xdaforums.com/nexus-s/development/rom-crespo-build-11-30-04-2014-t2567919

its very fast and its using CM version of kernel so flash accordingly, was working great with both Dalvik and ART runtime.
[Nexus S Android Development] leap_ahead:
and this one :http://xdaforums.com/nexus-s/general/rom-cyanaosp-04-04-2014-t2634728 CyanAOSP
[Nexus S Android Development] :
Are these soft or hard reboots?
[Nexus S Android Development] :
Yes, phone doesn't sleep while charging. This is normal
[Nexus S Android Development] :
I had the same problem. I don't think it is the kernel, or the problem would affect everybody.
[Nexus S Android Development] Setting.Out:
Soft..
[Nexus S Android Development] :
Can you run another kernel for comparison for a while? Soft reboots should be app or ROM issue. Should happen with any kernel
[Nexus S Android Development] Setting.Out:
I go to a short boot animation, and then straight to the lock screen.. I've used Guru, CM and Devil for days prior without a hiccup.. ??
[Nexus S Android Development] rakeshbro:
Then what should I do? Revert to stock and wait for a fixed build?
[Nexus S Android Development] :
Dirty reflash ROM then wait for a fixed build

Yes it's too much to be a coincidence. I'll investigate if it could be something to do with the task killer.

To help me, if you run marmite, wait for a soft reboot to happen. Then, as soon as you can, perform a manual reboot, then as soon as you are back in, upload /proc/last_kmsg for me to look at.
[Nexus S Android Development] leap_ahead:
to reflash rom do this :format cache ,boot, system ...then wipe cache and dalvic cache and then reflash rom
[Nexus S Android Development] :
That's not a dirty reflash

You're describing a full wipe
[Nexus S Android Development] Setting.Out:
Its a cleaner dirty flash since data still stays intact... ;)
[Nexus S Android Development] drac0:
LOL a bit cleaner :D
[Nexus S Android Development] leap_ahead:
noo full wipe mean format data ..with this u not loose anything
[Nexus S Android Development] :
Sorry yes you are right, but in this case there is no need to wipe anything
[Nexus S Android Development] Setting.Out:
Here's the last_kmsg from the last reboot.. http://www.mediafire.com/view/8nvpcdrf5kbs7z6/last_kmsg
[Nexus S Android Development] :
https://github.com/bedalus/hxore/commit/e9562c7d125c38bdcbfa57f631e6c7a3eba801f3.patch

bookmark for patch I want to try