yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Cybergr:
I noticed a battery drain tonight..I went to sleep at 5 o`clock this morning my battery was at 95% and when i woke up at 10 o`clock my battery was down to 80%..Any one experiencing something similar!??

I was on ondemand governor with defaults cpu clocks..!

Plus i think the wifi signal seems to be a little bit wicker..I will play a lil bit more around and post back..
[Nexus S Android Development] yaronyud:
in this kernel the profiles on SetCPU will work good?

or like all others will crash system and i will have to pull the battery?
[Nexus S Android Development] Cybergr:
I just flashed the latest kernel update 19 oct..and when i tried to play with Proton suggested voltages and i pressed apply my handset freezed and i have had to pull the battery out..!

SetCpu seems to working though, it won`t get an FC when u select the voltages tab..!!So it must be that my handset it can`t handle the suggested voltages from Proton!

PS: I can confirm i have a heavy battery drain..But under battery use all seems to be good except the knwon bug of Android OS and Adroid System..
[Nexus S Android Development] dinuvali:
Flashed 19 oct version and Proton still freezes, no-frills CPU does not.
[Nexus S Android Development] JmPTaz09:
10/19 kernel running great; smooth as can be. It froze upon initial boot up, but the last version did too for some reason... something to do with setcpu I believe... however it seems that I can use setcup now to adjust governor and voltage and all has been running great with no problems for several hours now. Seems that besides the odd initial freeze on boot, this version is running really great for me. One thing though, BLN is not working, I tried with and without the app. I have BLN pro and it gives a lib-light error.
[Nexus S Android Development] brenix:
BLN works here..

Check to see if the cypress-touchkey.bin file is located in /system/vendor/firmware

I believe the installer script accidentally puts it in /system/vendor which supposedly is the incorrect location..

If it isn't in the firmware directory, move it in there with root explorer or something and set the permissions to rw-r-r (chmod 0644) and then reboot... See if that helps... Just a thought though..
[Nexus S Android Development] dimiar:
18/10 works great no sod, smooth, good battery life. 19/10 had sod had to pull battery, so I am back on 18.
[Nexus S Android Development] EdForce1:
I'm on the same rom, but with the latest kernel release. Works great so far!
[Nexus S Android Development] franciscofranco:
Indeed, everything works fine for me too. Pretty awesome battery power, wasn't expecting to be this good.
[Nexus S Android Development] fergie716:
Ditto.. Just flashed on NS Collab and everything is working fine (NS4G). Thank you OP!
[Nexus S Android Development] lukappaseidue:
this is what this kernel do for me (its good or not?)
[Nexus S Android Development] Sputnikk23:
Does that say ONE DAY!?!?!?!
[Nexus S Android Development] DebauchedSloth:
Yeah, it does.

I've pulled 25 hours of pretty solid use (including 6 or so of sleep.)

This kernel is simply amazing.
[Nexus S Android Development] Sputnikk23:
wow. i'm jealous.
[Nexus S Android Development] HeavenlyWinds:
New version make the phone noticably faster and smoother. Great work, now all I have to do is finish tweaking my voltages, finish reconditioning my battery and i'll be set :cool: thanks Franco.
[Nexus S Android Development] got2best:
Anyway to get an explination on tweaking the voltages with nstools.. I would like to make love oc work better..
[Nexus S Android Development] mike216:
Start by raising your regular voltages from + 10 across the board above stock if your getting reboots

You still would be under if your liveoc 110 and above

Sent from my I9020T NSCOLLAB + FRANCO'S 08 BEAST LIVEOC 110
[Nexus S Android Development] Flying Fox:
Sorry to mention it here:

I wanted to be sure, if Deep Idle is really working. So I flashed Ezekeel´s kernel just to take a look at the idle-stats. They all still showed 0ms. I tried to turn on/off the camera (from Brainmaster´s rom) as it should turn on deepidle. But nothing happend. I got a value for "idle", but zero´s for "Deep Idle Top On" and "Top Off". Then I read this:

http://xdaforums.com/showthread.php?t=1336529&page=14

Look at the posts about the app Google talk v1.3. After deinstalling that app, I got values for "Deep Idle Top Off" and was happy to change back to that Kernel. Obviously there is an association between Google Talk an the function of deep idle. But without getting any results in the Idle stats it doesn´t seem to be easy to find out, if deep idle is working or not. For me it´s working now (after throwing Google Talk away).... and was happy to flash Franco back!!!!

Again, thx for this great work!!
[Nexus S Android Development] Yusei:
and how i use it
[Nexus S Android Development] mike216:
Been running 110 and got a reboot while listening to music so I went up 10 across the board on stock, I haven't touched internal yet,if I get another ill go up 10 more across the board.

If I get another then ill raise the internal by 10 across

Could possible help?

Sent from my I9020T NSCOLLAB + FRANCO'S 08 BEAST LIVEOC 110
[Nexus S Android Development] got2best:
I was just about to ask the same thing as Mike216 ... if I still get reboots is it safe and would it help to raise the internal voltages? ..
[Nexus S Android Development] mike216:
Yes but small increases

Sent from my I9020T NSCOLLAB + FRANCO'S 08 BEAST LIVEOC 110
[Nexus S Android Development] franciscofranco:
I don't think you need to increase the internal voltage with just 110, keep bumping in 10 increments the arm voltage until it's rock stable for you ;)
[Nexus S Android Development] mike216:
I was going to say internal might be more towards big OC like 130 and above

Franco, your F;-+ awesome man 110 is sooo fast,loving my phone

Sent from my I9020T NSCOLLAB + FRANCO'S 08 BEAST LIVEOC 110
[Nexus S Android Development] mike216:
Our nscollab is a power hungry SOB

You'll get it

Besides the OC its the buss speed increase that needs more juice

Sent from my I9020T NSCOLLAB + FRANCO'S 08 BEAST LIVEOC 110
[Nexus S Android Development] franciscofranco:
I'm glad you're liking what I've been able to release. Obviously it's not just my work alone, Ezekeels mods are wonderful, and this last update was born because of a discussion between me and morfic where he stated that we needed to modify the ramdisk for rom stock users to run init.d scripts thus using some of our tweaks to improve performance...but as I didn't like that idea I found a way to set those tweaks directly into the kernel source ;) if morfic wasn't there I wouldn't have come across that idea and then the implementation, which morfic like it and he's going to use that code in his future releases. Cooperation between inteligent people is very important, thus my initial statement that not all of this is my work alone, it's a cooperation between my head and experience and other good devs =)

Ahaha I think I wrote too much :p
[Nexus S Android Development] encinocr:
i testing the BFS-Kernel together with Brainmasters ROM.

Why BFS, the Name is so geil :D
[Nexus S Android Development] chinopski:
would like to share my settings:

latest franco kernel - cfs

840 max - 1150mV

420 min- 1000mV

lazy

NSCollab

i9023

awesome ;)
[Nexus S Android Development] mike216:
I know morfic and ezekeel are equally as awesome! I definitely appreciate all you guys for all your late nights and hard work

Sent from my I9020T NSCOLLAB + FRANCO'S 08 BEAST LIVEOC 110
[Nexus S Android Development] HeavenlyWinds:
Totally agree with you. I guess we all appreciate Francos and Ezekeels hard work.
[Nexus S Android Development] stojshic:
I'm not a big fan of overclocking, but after reading so much posts about how good LiveOC is, I decided to give it a try (110) , but I can't make my phone to like it. I raised every arm voltage for +35, but no luck :-( should I try raising it even more, or is it possible that my CPU just won't accept OC?
[Nexus S Android Development] franciscofranco:
Yes, that can happen :(
[Nexus S Android Development] doc_v15:
Could you please share your STEP BY STEP settings?

Like, which one is first, 2nd, and so on..

Plus with the value.. :) Thanks
[Nexus S Android Development] idelgado782:
Running latest 0811 model and it is GREAT!!!!!!!!
[Nexus S Android Development] chinopski:
flashed NSCollab rom months ago

flashed to latest Franco kernel (came from previous franco kernel)

chose lazy governor on set cpu

used Set cpu to set may min/max cpu frequency to 400/800, and to undervolt to -50mv on both cpu frequencies.

downloaded NStools and used it to set live oc to 105 (my phone did not require raising the voltages) :)

i guess that's it ;)
[Nexus S Android Development] Ibn Saeed:
Just installed franco's Kernel with Bugless Beast ROM.

Testing it right now for stabillity.

Got 2377 on Quandrant Standard with stock settings.

Lazy Governor

Live OC 100

---------- Post added at 07:16 AM ---------- Previous post was at 07:09 AM ----------

Whats the benefit of underclocking and undervolting apart from increased battery life ?
[Nexus S Android Development] HeavenlyWinds:
Thanks for the settings share, will try.
[Nexus S Android Development] Ibn Saeed:
Phone hung while browsing. Had to force restart

Settings:

Min/Max: 400/1000

Live OC: 110
[Nexus S Android Development] Ibn Saeed:
Governer: Lazy
[Nexus S Android Development] franciscofranco:
I need tests on this one please: http://androtransfer.com/franciscofranco/Nexus_S/franco.Kernel.09112011-cfs-test.zip

Only cfs and you can monitor idle_stats with nstools. Use it for a while and provide me useful feedback please, thank you.
[Nexus S Android Development] xtracrispy:
i'm on it!
[Nexus S Android Development] dvgrhl:
What specifically are you wanting tested or looked for? Just assuming you have something in mind you're wanting to know about, so we can provide feedback that is useful.
[Nexus S Android Development] afzalarsalan:
Reenable minfree value change

Franco,

Is there a way to reenable change to the minfree values as I am a big fan of the V6 supercharger script.

Thanks
[Nexus S Android Development] doc_v15:
Thanks! ;)

Hmm..thats a bit low..Mine could go to 3470 :D
[Nexus S Android Development] al_madd:
Test what?

Deep idle stats is working for sure...
[Nexus S Android Development] franciscofranco:
Nop, sorry, it's going to stay like that for maximum compatibility.
[Nexus S Android Development] franciscofranco:
Just use it normally, do your real life stuff, bench a bit if you want, then come back reporting if it's better than before or not. I'm not saying what I changed because I don't want placebo effects ;)
[Nexus S Android Development] dvgrhl:
What about the placebo effect of thinking you changed something, so people expect it to be better and then report that it is? Unless this one has nothing changed, and it's just a test for us? :confused:
[Nexus S Android Development] franciscofranco:
Not telling, just use it normally, I'm doing the same ;)
[Nexus S Android Development] mike216:
If your on a cyanogen based rom then go into cyanogen performance settings and make sure the only thing checked is the jit setting " davik just in time compiler " that's it anything else in there checked will cause instability

This is my opinion after much testing

So far I can run 110 liveoc on stock voltages! But if you can't with these settings make sure your minimum is 400 and if your still getting reboots then start by raising your minimum 400 clock voltages up 10

Like I said this has worked great for me on my favorite nscollab power hungry rom! Hope this helps!

Sent from my I9020T NSCOLLAB + FRANCO'S 08 BEAST LIVEOC 110
[Nexus S Android Development] xtracrispy:
pretty smooth so far. Initially I had some boot loops on Oxygen, flashed over from Matr1x. Cleared everything, reflashed the ROM and now it's solid.

Re: The idle, one thing I've noticed from a while ago is that it doesn't deep-sleep while charging. Current from the plug probably overcomes the drain by a significant factor, but technically wouldn't the phone charge faster if it were still enabled?
[Nexus S Android Development] franciscofranco:
****, that's going a little too technical, I don't know exactly how that works and how the charging effects the rest, sorry.
[Nexus S Android Development] mike216:
Yep dude 105 is a nice OC setting if your looking for a good balance between speed and battery! Not that we need the speed on franco's great work but its always nice to have something to tweak lol..

Sent from my I9020T NSCOLLAB + FRANCO'S 08 BEAST LIVEOC 110
[Nexus S Android Development] mike216:
09 testing! will report back after some normal use without OC,thanks

Sent from my I9020T NSCOLLAB + FRANCO'S 08 BEAST LIVEOC 110
[Nexus S Android Development] dvgrhl:
Hmm, well after several runs the Quadrant scores ranged from 5%-10% better than what I typically see, with a high of 3762. Benchmarks don't really mean much though, but it is interesting to note the increase.

I rebooted a couple times to see how long it took to get to a useable state. Not much change here, though it is hard to quantify.

I'm headed to bed soon, so the real test for me will be to see battery drain while I sleep, followed by responsiveness tomorrow when I wake up. Bonus points if there are no sudden reboots. :p But my little bit of playing so far shows the launcher to be responsive as I expect, and apps to load like they should.

I'll respond tomorrow with findings after more hours of usage, but I suspect that outside of a benchmark giving you a number, it will be hard to give a definitive answer for if it is faster or not. You'll certainly hear from everyone if there is problem though. :)
[Nexus S Android Development] darthchilli:
funny how when the phone has 20% battery or less, FC like crazy

live oc 110

deep idle

stock voltage
[Nexus S Android Development] shubu000:
thanks to the new internal voltage control, i think i got a stable liveoc of 125

thanks franco!!!

although i think the heat generated by the unit will be the determining factor to the stability of the clock
[Nexus S Android Development] Abaddon:
same on my phone with MV. deep idle is disabled when charging :)
[Nexus S Android Development] 93ae8074:
I doubt that Francisco is gonna change it. But you can still use V6 SuperCharger script to create a .sh file in /data that can be executed with Script Manager. What I don't really know is if it can cause trouble with Francisco's kernel 'cause V6 SuperCharger script modifies /data/local.prop file.

Cheers.
[Nexus S Android Development] al_madd:
Read deep idle thread...there is a post where ezekeel state that deep idle is disable while charging...
[Nexus S Android Development] zeppelinrox:
It will work fine.

The supercharger tweaks the memory on all fronts (minfree,adj,MEM,ADJ) so there is NEVER a compatibility issue.

The launcher gets supercharged yes?

Then just be sure 99supercharger runs on boot and rock n roll.
[Nexus S Android Development] 93ae8074:
I modified a bit your init.d script to suit my needs and V6 SuperCharger works wonderfully as always.

Cheers! :)
[Nexus S Android Development] stojshic:
I'm on MIUI... Thanks tho...
[Nexus S Android Development] ZeppeMan:
I received my Nexus S an hour ago and i'm allready running my first custom ROM ^^

I flashed Oxygen 2.3.1 together with this kernel, I have to say, that it's way more responsive and more smooth then the stock ROM.
[Nexus S Android Development] Ibn Saeed:
I also tried franco, its good.
[Nexus S Android Development] ro_explorer:
Here I come again, after 2 sets of "regular" usage of my device.

Prerequisites:

- before flashing the kernel I've restaured the original /system partition from the stock 2.3.6 rom.

- after flashing each kernel dalvik and /cache got deleted

- after boot the following values have been used:

_ liveoc 100

_ BLX 100

_ governor conservative

_ freq range 100-1000

Some will jump :"why the hell are you still using 100MHz as min freq?" .. the answer is this one: I'm not using my phone mainly for games but for accesing information like : reading e-mails, using gtalk and web browse. For these activities (especially after a page is loaded on my screen) I don't think that I need 400MHz to read the damn text. So, with this usage profile in mind => 100MHz min freq.

In my opinion a great kernel will provide great performance while awake and great power saving while at sleep.

Starting with the releases AFTER oct 27th, the first requirement is extraordinary being met but the second requirement was sacrificed. I have no idea why, what actually changed that behavior but anyway...

After a full day with Nov2nd release I've switched back to Oct24th release (yesterday).

Attached are the results of my personal usage. I'm not the one entitled to draw conclusions here or to take actions .. I'm just presenting the fatcs as I see them.

You may observe I did not talked about liveOC or UV/OV. My CPU is one of the ones that do not support OC so that area is out of my reach.

Full size picture is this one: http://img197.imageshack.us/img197/6942/shot000001v.png
[Nexus S Android Development] 1PATRIK:
Pretty impressive! Where you can find old releases? Can you provide any links to them, if they're saved to your computer? I always delete old ones when I start testing/using new ones. Your investigation seems to have same results what I have found out myself.
[Nexus S Android Development] ro_explorer:
I have all releases on my phone. Let me know which one would you like and I'll upload the files here on this thread.
[Nexus S Android Development] Flying Fox:
Just flashed 11/9-test and the battery indicator jumped from 22 to 42% :D. Seems that I don´t have to recharge my phone for the next two days :).

Seriously I´m happy to be able to watch the idle stats now. I'll see what else the update brings with it.

One question, sorry for that:

You guys were talking about the need of some complete charging cycles. Seems to be important for callibration. Is it necessary to do so after each update? Or after switching to another kernel? Or only after wiping bat.stat.?

Don´t want to waste your time, franco, maybe someone else has an idea. I thought full charging cycles is a thing of the past as short ones save the battery.....
[Nexus S Android Development] ro_explorer:
Battery stats is just a file generated during the charge and discharge cycles and it helps the battery monitors to accurately report the battery capacity.

With a wrong or none battery stats file your showed capacity may be a little off the actual one.

In cases like yours (huge discrepancies) it is recommended to fully discharge the battery first. From my knowledge, these types of disrepancies are being generated while flashing with the charger plugged in.
[Nexus S Android Development] jhalmeida:
Wird left phoe charging over night and it does not goes over 82%. anyone with this issue? 1st time it happens to me
[Nexus S Android Development] Mecid8:
are there any bugs in BFS version?
[Nexus S Android Development] :
Delete your battery stats in recovery then power off, charge your phone on the AC adaptor, when full, unplug and reboot.

Franco, tested 09 CFS. Scrolling seemed to lag compared to 8 Nov.

Obscurely referenced from the fifth dimension on my Nexus S
[Nexus S Android Development] Mecid8:
franco are you using slqb allocator? if not please add it, this add more smooth.
[Nexus S Android Development] Yusei:
Francisco, with this kernel my phone doesn't catch Hsdpa network.
[Nexus S Android Development] Mecid8:
and please add this tweak for bfs kernel
[Nexus S Android Development] franciscofranco:
Oh really? Why don't you check my sources before wasting your time posting irrevelant stuff?
[Nexus S Android Development] polobunny:
but it adds more smooth!

:rolleyes:
[Nexus S Android Development] Sputnikk23:
all your kernel base belong to franco
[Nexus S Android Development] xtracrispy:
Idle seems to not kick in today, woke up and unplugged the charger. Went to 91% in 20 min
[Nexus S Android Development] roshga:
Having the same thing with test cfs kernel... But I think that deep idle does work, just stats are no good
[Nexus S Android Development] franciscofranco:
http://xdaforums.com/showthread.php?t=1297535

Check bottom of first post.
[Nexus S Android Development] Sputnikk23:
2nd time in past two days that wifi "drops out". Still says connected but no data being passed till reboot. airplane on/off don't help. If it continues, i'll try cfs version.
[Nexus S Android Development] polobunny:
Not wanting to start any false rumors, but I have absolutely no problems with the CFS version. Been running 8 Nov version for 24 hours and I was running 6 Nov for around 12 before.

Not sure why people are ready to go through so much to use a BFS kernel.
[Nexus S Android Development] Sputnikk23:
i hear ya, but initially this was bfs only :)
[Nexus S Android Development] franciscofranco:
Nop, it's been CFS all the way, I only released one bfs-only kernel.
[Nexus S Android Development] stojshic:
Read somewhere to start camera app, and than close it, it will enable deep-idle. It has something to do with Google talk apk... So, on phone restart, just start camera and exit, it will (should) enter deep-idle after that...

EDIT: Late, Franco already answered...
[Nexus S Android Development] rip_noob:
I had the same problem with the cfs 3 or 4 versions before. But since then its fine.

You have to try cfs :)
[Nexus S Android Development] Yusei:
Anyone have the same problem with network?
[Nexus S Android Development] Sputnikk23:
the first one right? thats when i got on board :) sort of stuck w/ bfs since then. always ran cfs on all other kernels but I thought "this franco guy sure seems like he knows wtf hes doing". seems like i was right :)
[Nexus S Android Development] polobunny:
Nothing wrong with BFS in itself, but it seems like most if not all BFS kernels I have tried for the Nexus S bring their own little problems to troubleshoot. Sometimes things just aren't meant to be. :p
[Nexus S Android Development] Mecid8:
i am read 1st post, and there are no this stuff!
[Nexus S Android Development] polobunny:
The source files that he used to compile the kernel, not the first post...

His git

https://github.com/franciscofranco/Nexus-S

On another note, I see why you wanted everyone to delete stuff related to minfree in our init.d franco. I should have a look at the commits more often. :p
[Nexus S Android Development] MultiCulti:
i switched back yesterday from "custom roms" and GlaDOS to Clean CM7.1.0.1 and 11/8 CFS

live OC 110

lazy

deepidle on

stock voltage

NO SetCPU or daemoncontroller

edit: normal use over the day

looks like the best kernel ever, at least for me till now :)

beamed in from my Nexus S on CM7.1.0.1 using my head
[Nexus S Android Development] Mecid8:
I am read 1st post, there are no this stuff. I ask him about it, whats problem?
[Nexus S Android Development] polobunny:
Hey franco, any idea about this?

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

Just a fluke or a mounting problem of some sort? Related to ext4 remount maybe?
[Nexus S Android Development] y3mita:
Using bfs here without a hitch everything works fine. It's been 24 hours and only experienced one reboot!
[Nexus S Android Development] ro_explorer:
Those 2 terms do not get along well. Either everything is fine either you're experiencing reboots.

"only one reboot" is equivalent with "not OK".

It would also help if you will give more details about OC/voltages/governor and what mods do you have active.
[Nexus S Android Development] Cybergr:
I switched from NSCollab 1.0.50 to Oxygen 2.3.1 with 08/11/11 kernel and downloaded Voodoo Control Plus but it doesn`t seems to work!Anyone has a clue on this?!
[Nexus S Android Development] Zorrich:
I do not know, but wanted to confirm that before i flashed Franco recent test build, that is the setup i was using and had no problems with voodoo.
[Nexus S Android Development] franciscofranco:
Yes probably. I'll have a look.