yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] xtracrispy:
I installed the older gapps as per the post above me, so deep idle now registers.

Only problem is, once it's idling, I require precisely 3 clicks of the power button to awake.

No crashes, just needs 3 clicks..
[Nexus S Android Development] roshga:
having same behavior as @xtracrispy

need 2-4 clicks on the power to wake up.

on test 1011 cfs.
[Nexus S Android Development] chinopski:
phone is always awake on nov 10 test kernel as compared to nov 8 official kernel,

same settings used on both kernels

ns collab rom

lazy

840/420
[Nexus S Android Development] ro_explorer:
The first feedback on nov 10 test kernel is that the bluetooth still gets muted/paused when the screen is being turned off. For now I took with me the wired headset ... but only for today. I really need the bluetooth AD2P to work as it should.
[Nexus S Android Development] mike216:
I just tested a couple other kernels and this one at stock 1000 is faster than a couple others at 1100 on one and 1200 at least it feels like it

08 is the best of all releases so far

This was my experience using smartass, simply blazing governor but I use lazy for the great battery life

Sent from my I9020T NSCOLLAB + FRANCO'S 08 BEAST LIVEOC 108
[Nexus S Android Development] mike216:
Franco you really should try nscollab its the fastest rom I've tried, of you haven't already

I dont want to get no **** started guys I'm just giving my opinion, we all have our favorites and no one is better than another! I appreciate all the great developers in this amazing community, thanks to them I know I will without a doubt get the prime as I suspect all the greats here had a nexus one

Sent from my I9020T NSCOLLAB + FRANCO'S 08 BEAST LIVEOC 108
[Nexus S Android Development] Tzorg:
Nov 9 has not given me further problems since tweaking voltages, it was ok this morning after all night.

Trying Nov 10 now, quadrant is back to high performance on the 3500+ on NSC50 1000-200. Nov 9 was stuck on 3400s
[Nexus S Android Development] 1PATRIK:
I just noticed something interesting. I reset my battery stats via CWM, and kernel 08 is working perfectly again, before reset I had huge battery drainage problem.
[Nexus S Android Development] ro_explorer:
Weird thing with this lazy governor ... the cpu states are showing that the 200-400-800 steps are barely used, the extremes being most used all the time. With conservative I see all steps being used with a preference for the lower frequencies.

I'll stick with conservative for now.

Sent from my green robot ...
[Nexus S Android Development] Zorrich:
Lost signal last night for first time on your kernel. Running the 10.11 test build. Actually it showed I had signal, but i did not as i could not load anything.

Using oxygen 2.3.1, radio UCKF1.

EDIT: added more details.
[Nexus S Android Development] roshga:
Thanks, but you uploaded twice the same apk (with video).

The good apk (without video) is attached, flash threw recovery :)
[Nexus S Android Development] Yusei:
even after uninstalling talk my phone takes a long time to enter in deep idle
[Nexus S Android Development] ro_explorer:
More info in nov 10 test kernel: the reboots have gone, the performance is great while using the device, the deep idle is kicking in fast BUT: the drainage with the screen off and deepidle enabled is huge: 3-4% per hour.

The kernels up to oct 27 one had (during the day) a drainage of ~1% per hour with screen off and doing nothing (except syncing e-mails).

Add-on: from time to time I have to press twice the power button to wake the phone. I'm thinking is sleeping too deep :).
[Nexus S Android Development] roshga:
I found something which is kinda weird.

When I try to do something with system app in titanium (like uninstall, convert user-app to system-app or anything like that) I get an approvement by titanium but nothing really happens. I checked maybe the problem was with the rom, but nope. only replacing a kernel fixed it. is there an issue with the mounting ?

btw Im running the 1011 version but tried also 0911 and 0811, they have the same problem.
[Nexus S Android Development] ro_explorer:
I second that issue. Sometimes applications that need to mount /system partition in rw mode (with root permission, of course) can not achieve this task.
[Nexus S Android Development] ellesshoo:
+ 1. I wasn't able to remount /system rw. I never had that issue before and didn't even suspect the kernel. Franco, can you look into this?
[Nexus S Android Development] franciscofranco:
Thank you all for the valuable feedback, keep sending it!!

About the remounting I know what it is, I'll fix it.
[Nexus S Android Development] Abaddon:
yeah especially on superuser for example :)
[Nexus S Android Development] sabaramo:
How did you go with PMEM? Did you find that extra 12.5MB?
[Nexus S Android Development] formula84:
I noticed this yesterday but I thought it was the rom and ignored. Thanks for the info

---------- Post added at 02:31 PM ---------- Previous post was at 02:24 PM ----------

I would think that using NSTools to turn off deep idle when needing to use BT earphones is not that bad.
[Nexus S Android Development] polobunny:
The irony is still making me chuckle a bit.

Deep idle is mostly effective when you need your phone to do work with the screen off (listening to music) but you can't listen to it with your wireless headphones. :p
[Nexus S Android Development] got2best:
I second the Bluetooth problem.. I love using my jf3 but the 1011 kernal does not work well with them.. and with 08 i didn't have the Bluetooth problem.. and I don't want to have to turn deep idle off.. thanks :)

Running nscolleb

I9023
[Nexus S Android Development] MultiCulti:
feedback: day 2 with 11/08 ...

no reboots, no freezes,

very smooth

bluetooth working fine

auto sync on

data always on 3G/2G

live oc 110

stock voltages

clean CM 7.1.0.1

deepidle on

battery on normal use over the day

beamed in from my Nexus S on CM7.1.0.1 using my brain
[Nexus S Android Development] kecinzer:
I'm using latest version (1910) with Oxygen 2.3.1 and I get amazing battery life. I don't believe it - is better than TEUV. And 100% battery charging is simply brilliant.

Thanks for great kernel.
[Nexus S Android Development] Apolyxon:
Few questions:

Is that 100 % charge a physical 100 % charge that kills your battery faster over time?

Do you guys use Lazy governor for awesome battery life?

Anybody here using this kernel with Pete's ROM?
[Nexus S Android Development] kecinzer:
I think, that 100% charge is only for eye :).

No I using default govenor, that came with kernel - ondemand.
[Nexus S Android Development] doc_v15:
+1, same for me too!

Thanks franco!
[Nexus S Android Development] eiabea:
Just flashed this kernel over NSCollab #50, so i can't say much about battery, but deep idle is implemented and did a great job with Matr1x kernel, so i don't worry.

Greatest feature ever: "* WiFi = PM_FAST in standby" !! very nice! :) now i can sync my music with screen off! :) THX!
[Nexus S Android Development] Cybergr:
????? looool
[Nexus S Android Development] martinsjt:
Hello Franco,

I use two tweaks on my Nexus S:

Universal Adrenaline ShotvXIX:

http://xdaforums.com/showthread.php?t=1236779

"Whats inside:

/system/bin - fugu binaries both from honeycomb 3.1(3.2 is on the way)

/system/lib - patched sqlites for better I/O performance

/system/etc/sysctl.conf - systclt.conf allowing compatibility with supercharger script

/system/etc/init.d/:

00remount - ext4 partitions

01acidsysctl - activating sysctl.conf

02kerneltweaks - NO_FAIR_GENTLE_SLEEPERS

03sdcardspeedfix - fixed sdcard read ahead to 3072

04sysctltweaks - tweaks governor, and kernel"

and,

Move dalvik-cache to /cache:

http://xdaforums.com/showthread.php?t=1259217

"Stock and aosp roms don't hold the dalvik-cache in /cache, only cm does (but only system apps).

Putting dalvik on /cache is better for me because it is yaffs2. /data is ext4."

From the kernel improvement list I can’t understand if this tweaks are already applied or if they bring improvements with the tweaks you already made.

Can you please give me your opinion?

Best. :)
[Nexus S Android Development] ragnarokx:
Did you manually undervolt?

Sent from my Google Nexus S
[Nexus S Android Development] JmPTaz09:
10/19 kernel is smooth as a baby's ass; runs great on Brainmaster rom.
[Nexus S Android Development] brenix:
Excited to try the next release, this thing has been running really well! Love the network tweaks, seems a lot more stable than the default..

I think the kernel zip needs to be changed to fix the install path for the cypress-touchkey.bin file... I believe it should be set to install to /system/vendor/firmware rather than /system/vendor.. I'm not 100% sure on this though..
[Nexus S Android Development] aiacone:
I'm on Brainmaster rom. The cypress file is either in /vendor and in /firmware. I left it only in /firmware, but bln doesn't function. It's the only 'bug' for me. Thnx!
[Nexus S Android Development] franciscofranco:
Dunno really, it works fine for me and BLN is obviously activated in the kernel.

A small update should hit sometime in the next hours because of the small bug fix from Ezekeel.
[Nexus S Android Development] EdForce1:
One question, do i need to wipe cache AND dalvik or just dalvik?

When i update from same kernel i mean...
[Nexus S Android Development] franciscofranco:
You don't need to wipe anything, caches are not related to the kernel at all.
[Nexus S Android Development] brainmaster:
@Franco - it should be placed in /system/vendor/firmware/cypress-touchkey.bin in order to work on my ROM.
[Nexus S Android Development] franciscofranco:
Ok, thank you :)
[Nexus S Android Development] damnmisur:
Just flashed. One reboot. Bln working on Brainmasters didn't move anything. Wicked fast so far with ondemand governor .1.44ghz. Everything over 1ghz adjusted higher voltages.
[Nexus S Android Development] franciscofranco:
Small update in the first post, mainly because of the latest deep idle fix from Ezekeel and BLN fix for MIUI brainmaster users.
[Nexus S Android Development] bdpyo:
:sweetjesus:

Are you still running oxygen 2.3?
[Nexus S Android Development] damnmisur:
Freeze. Phone was idle. Reboot and received an email. Not sure if related.

Sent by my Nexus S 9020a on Telus running Brainmaster's MIUI and Talon 3.2.1
[Nexus S Android Development] roshga:
another issue with latest 1011 test kernel:

I was listening to music (no BT this time, plugged) and the music just gets corrupted after a few seconds (like a bad file when playing in the computer) with screen off, need to wake the device to make the song keep going.. but then happens again in a few seconds. imo it happens every time the device goes to deep idle and only waking it up helps.
[Nexus S Android Development] Maximilian Mary:
Maybe not so funny. The battery voltage drops from 4200 to 3700mV as the battery drains. It could be that dvsint drops too low to be be stable when the battery gets down to 3800.

I was playing around with lowering dvsint, and was quite surprised to find it running stable at 950-850 with navigation, streaming, and tethering. When the battery dropped to around 30%, it would instantly reboot at those settings.

I'm not sure how this all works (dvsint/dvsarm as a function of battery voltage) but it's possible that no voltages can be considered stable until they're stable at 5% with all juice suckers running.
[Nexus S Android Development] Ezekeel:
Interesting idea. I never thought about that, but it totally makes sense. I guess to be safe one should test the stability of OC/UV at a low battery level like 5% to make sure it actually is stable.
[Nexus S Android Development] 1PATRIK:
Got just my first radio dump with kernel 08. Airplane mode fixed it. Anybody else having this?
[Nexus S Android Development] waterface:
Don't know if there are workarounds, just wanted to quickly report bluetooth transfer stops with screen off if deep idle is activated (I know it was an issue for others already). Everything else feels pretty good.
[Nexus S Android Development] polobunny:
The only workaround so far is to either disable deep idle or not use bluetooth. :(

---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------

It'll be a b**** to stress test at a low battery % haha.
[Nexus S Android Development] endursa:
i just discovered something

i use the release from 8.11 - when i start the camera, and set the flash to on and take a foto, the phone gets in a SoD state, screen is off and no buttons are working, only pulling the battery works! deepidle is active!

ok funny thing: i just tried the 1011 test kernel, the same thing happens, my i9020 instantly freezes if i take a photo with flash on!

so i thought lets see if my i9023 behaves the same, it doesn't oO when i try to take a photo with flash on, and 1011 kernel nothing freezes!

same rom on both phones, only difference is that the i9023 was on a fresh setup, and my i9020 has apps installed!
[Nexus S Android Development] Ezekeel:
If you can you reproduce this problem with my reference kernel, post this problem in the GLaDOS thread. As soon as someone confirms the problem I will look into it.
[Nexus S Android Development] frutelaken:
^It works fine here on the i9023, but someone with an i9020 should test it too :)

Just want to share my thanks for this kernel, it's really good. Stable, fast, no issues whatsoever so far. Deep Idle is disabled though because I'm scared of it.

Greetz
[Nexus S Android Development] polobunny:
No problem here with lazy, maxfreq off. i9020a

Edit: franco 8 nov kernel
[Nexus S Android Development] franciscofranco:
Yes please try Ezekeels reference kernel and try to reproduce the issue.
[Nexus S Android Development] tatwamasi:
When should I wipe Batstats? At empty of at full? Whenever? Thanks.
[Nexus S Android Development] got2best:
I was told full .. but any1 please verify this?
[Nexus S Android Development] stojshic:
Fully charge your battery, then turn off your phone and wait to till it it vibrates and notifies that battery is full, disconnect charger, and then wipe battery stats... After that, fully discharge battery before next charging...
[Nexus S Android Development] polobunny:
I never really felt the need to wipe the battery stats. That's only necessary to "shortcut" the battery stats, otherwise a few charging cycles, even without letting it drain 100%, work wonderfully. It's not good to have your battery at 100% or 0% all the time too.
[Nexus S Android Development] got2best:
After u fully drain it do u need to charge it back up without any interruption?
[Nexus S Android Development] HeavenlyWinds:
Yes. It's better that you do the complete battery cycle.
[Nexus S Android Development] endursa:
did that, and it happens too, posted ezekeel the bug! thanks :)
[Nexus S Android Development] got2best:
Crazy battery in 1011 test kernal... nscolleb i9023
[Nexus S Android Development] polobunny:
What's keeping your phone awake?
[Nexus S Android Development] got2best:
I am guessing the music player.. but it wasn't in the list of battery use.. I am going back to 08 and see if this continues after battery statts wipe.
[Nexus S Android Development] xtracrispy:
here's a history of my phone. The gap in the middle is when I reflashed and rebooted from Nov 9 to 10, a different drain slope is seen. Doesn't seem to sleep as readily, currently on 400 min
[Nexus S Android Development] franciscofranco:
That's why it's called a testing build, I couldn't test all this **** only by myself ;)
[Nexus S Android Development] got2best:
O am more then happy to test them :) just wanted to report what happened. .. loving the stats working on the test builds tho..
[Nexus S Android Development] casca:
Hey guys, can anyone tell me the stock voltages for nexus s?

i'm seeing different stk voltages between nstools and proton app.

tks
[Nexus S Android Development] y3mita:
well, I am going back to Nov08 BFS build... the testing build Nov09-10 not that great! SOD two times battery drains and have not been using the phone much... I did UV -25 to all frequencies though as I had done with stable NOV08 build.
[Nexus S Android Development] franciscofranco:
Yes. I'm working on it, should deploy a new testing build 11/11 in some hours with the remounting bug fixed and other things that I'm experimenting, thus the need of being labeled testing builds.
[Nexus S Android Development] y3mita:
yep, I understand they're testing builds and no complains here! I do like edge stuff on my phone and try to help as much as I can... but today I needed my phone for traveling GPS/Phone and it went black on me two times! I had to remove battery to power back on! that's why I reverted back to stable Nov08 ;)
[Nexus S Android Development] brainmaster:
I have tested your latest 10.11 CFS Kernel on my MIUI ROM.

Live OC 110 % : 110, 220, 440 and 880 MHz.

Governor: Ondemand 110 - 880.

Voltage: - 25 mV on all values:

110 MHz 925 mV,

220 MHz 925 mV,

440 MHz 1025 mV and

880 MHz 1175 mV.

Result:
[Nexus S Android Development] y3mita:
brainmaster? any hiccups with those settings? GPS/deep_idle/battery... etc.

the performance is great! I guess I should've tried other governors... I had lazy UV-25 which is probably too much for the governor! next test build I will experiment other governors!
[Nexus S Android Development] brainmaster:
Didn't tested GPS, but the rest runs pretty stable for me. Had it only tested for today, no reboots, no freezes.

Usually I'm on Trinity TUV10. But had tested this one for me.
[Nexus S Android Development] italia0101:
Just wondering but what happens if in the ntools app where it says live oc you put. Something under 100% ?
[Nexus S Android Development] Lalaca:
Nothing, probably? Live OC, by name and design, was never made to make your clocks go down, as far as this goes:
[Nexus S Android Development] italia0101:
Yea that's what I figured. Thought I'd ask though. Neva know
[Nexus S Android Development] casca:
Just installed 10-11 test version :-)

Everything working.

What changed from 9 to 10?

Btw, can anyone please check if these voltages are normal for stock?

I think they are higher than they should for stock ...
[Nexus S Android Development] polobunny:
A question like this...

How do you guys test for stability? I'm currently in the process of seeing how much I can undervolt my CPU without losing stability.

My method goes like this (anyone tell me if you see a loophole):

-Airplane mode

-Set my CPU governor to performance

-Maximum frequency set to 200MHz

-Apply undervolt

-Run stress tests/benches (usually a few minutes of SetCPU stress test + some Quadrant passes)

-If no errors, write down voltage values and then undervolt more

-Repeat until error/reboot/FC etc etc

Then I change the frequency to the next one, for this instance 400MHz and do that again. I skip 100MHz as a whole because I imagine if 200MHz runs at a certain voltage 100MHz shall too. Might come back to it later if I feel like it, just for the sake of it.

After I'm done I'll have a good table of what undervolt my phone supports and hopefully it'll make it easier for me to overclock the bus and know how low voltage and how high overclock I can go.

---------- Post added at 06:26 PM ---------- Previous post was at 06:25 PM ----------

I think they're slightly higher than stock. IIRC 100 and 200MHz have 950mv for ARM.
[Nexus S Android Development] Flying Fox:
@polobunny: what is your min.frequency in your stress test, same as max (200/200, 400/400......)?

@franco: Tested 11/10 during the day. Just one reboot, not enough to blame the kernel. Deep Idle is working for me, if I can trust the idle stats (I refer to your post in the GlaDOS-Thread). I changed my settings to 880/440, still lazy, battery drain is amazing, as well as the performance. Couldn´t figure out differences to 11/9.
[Nexus S Android Development] mike216:
There pretty high bud here is stock

100-950

200-950

400-1050

800-1200

1000-1250

Sent from my I9020T NSCOLLAB + FRANCO'S 08 BEAST LIVEOC 108
[Nexus S Android Development] franciscofranco:
I'm not posting changelogs on testing versions because I don't want biased feedbacks and placebo effects. 11/11 should be out soonish.
[Nexus S Android Development] HeavenlyWinds:
Francisco, thanks for sharing your Paypal E-Mail adress. Continue doing what you do, you are a great developper.
[Nexus S Android Development] franciscofranco:
Thank you :)

New testing build 11/11. Remounting bug from last version is fixed along with other stuff. Test and feedback please.
[Nexus S Android Development] polobunny:
It's the same as max, but it doesn't matter since performance governor only makes it run at max.

Funny pic

Yeah, just noticed that performance governor doesn't give a crap about set voltages. Switching to ondemand made that crash. :p
[Nexus S Android Development] doc_v15:
And the battery last for....... :D

Let the stats do the talk :D
[Nexus S Android Development] doc_v15:
Hmm..Thats pretty low for Live OC 110%

Mine is like this

BFS, 8th Nov version. With NO LiveOC,

Only Standard default settings with SmartassV2 governor..

Using KelsMLKing MIUI Rom :D
[Nexus S Android Development] got2best:
Sorry for the off topic... but just really quick please! What theme is that that is causing the blue at the top?
[Nexus S Android Development] polobunny:
Honeycomb Alpha 4 by haxzamatic

for CM7 and any rom supporting theme manager

http://xdaforums.com/showthread.php?t=943423
[Nexus S Android Development] rdallman10:
Getting 4 hours of wakelock from NFC service out of 7 hours of use. Incredibly, I still have over 50% battery. I'm running cm7 latest stable for ns4g and your 11/9 tester build. Can't wait to see what the battery life is like when this thing can sleep. Haven't seen this behavior before so I'm assuming its kernel related. Other than that getting awesome performance with all nstools enabled and liveoc at 110 and no voltage changes. Tried your bfs builds and data dropped usually after an hour or so, I would be connected but Internet wouldn't load... Think you know of that issue though. Love the progress and my phone has never run smoother just reporting to help with tester builds. Appreciate it.
[Nexus S Android Development] some_random:
so this kernel has the max freq tweak enabled, yes?
[Nexus S Android Development] brainmaster:
On 880 MHz like mine?

Edit: Sorry to disappoint you, but the standard setting on KeLMSKing is 1 GHz, mine was achieved with 880 MHz.
[Nexus S Android Development] HeavenlyWinds:
No you have to enable it in terminal by using this code:

echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/lazy/screenoff_maxfreq
[Nexus S Android Development] doc_v15:
Oooops :P

I think I missed that part :P hahaha..

Then Im sorry, for 880mhz, thats fast! :D
[Nexus S Android Development] some_random:
hmmm ok I'm using the latest trinity at the moment but getting a lot of 880mhz according to cpu spy like almost 40% at 880mhz and then like 60% in deep sleep... do you think that this kernel would fix that because the tweak isn't enabled?
[Nexus S Android Development] al_madd:
You have to enable manualy
[Nexus S Android Development] y3mita:
Well decided to use your settings OC 110 your voltages and min 110 max 880 and flashed stable Nov 08 BFS the only difference is t the governor, mine is smartass2. Phone completely charged has dropped 1% in hour and a half with only about 15 minutes of usage.

Loving it now!
[Nexus S Android Development] franciscofranco:
In case someone missed it because of the large screenshot quotes...
[Nexus S Android Development] mike216:
Test kernel 11,Get instant gps lock,nice and quick

Much more testing to do

Sent from my I9020T NSCOLLAB + FRANCO'S 08 BEAST LIVEOC 108
[Nexus S Android Development] ehiggins:
on the 11.11 deep idle doesn't show up in the stats when I have a 4g connection. It works on other data types just fine. I don't know how earlier test builds were.

Actually 4g just needs to be on not actually connected
[Nexus S Android Development] 1PATRIK:
Got 22% battery loss during night..Cell standby usage 44% :O What can I do to fix this? Any recommendations?
[Nexus S Android Development] akshayf:
Try Airplane mode. Or check your gtalk version and open and close the camera accordingly first deep idle to kick in.