yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] ro_explorer:
Quadrant clasic (the one that is showing a single blue line and a score) will not differentiate the benchmark results made on CPU/GPU from the other components of the system (IO read/write, memory).

Now .. a true benchmark of the IO (disk in other words) will show you the TRUE reading and writing speeds performed on the internal memory (SSD). Unfortunately, quadrant is being fooled very easy using mounting options.

If you mount the disk using the default EXT4 settingd, you will get about 500 quadrant points on it. If you try various tweaks (which most custom roms use by default to create the sensation of speed when working with files) you can get 2000+ poins instead of 500.

This mean that a benchmark that is showing just a number: 3400 for example) is meaningless ... because you have no idea how mani points are created by the CPU and how many by the IO. If the IO tweaks would have influenced about 100 poitns then yes, you know that the difference between a wuadrant score of 1600 and one of 3400 is mainly caused by the great kernel ... but in this case, a "total score" is meaningless. That why I ask you to either use the advanced quadrant and consider only the cpu/gpu scores, or just don't use quadrant. From my point of view, quadrant is just an ego auto massage tool ... not even close to a real benchmark.

I bet that my 1600 standard quadrant points phone (actually this is what I'm getting if I'm not tweaking the mounting options) is as fast and smooth and user friendly as your 3400+ device :) ... why? because the cpus and actual disks are quite the same, they just being reported differently in quadrant.

As per your graph, that sort of usage (awake states and screen on states) should have drawn much less power. That sort of usage should lead to an approxiomate 50 to 60 hours of autonomy on a nexus S ... more on the 50 side with poor GSM signal. In your case, you lost 20% in just 4 hours .. that why I said is terrible .. maybe I've used a too heavy word for it ... what I meant was that the battery can be much better under those usage conditions.

---------- Post added at 04:46 PM ---------- Previous post was at 04:32 PM ----------

If you want to test how fast your cpu is using a dedicated kernel, either consider using quadrant advanced and run just the cpu benchmark) or use other (less popular) benchmarks that will indicate just the CPU (like "linpack" or "CPU benchmark").

You will see that indeed, Franco's work will put our 1GHz CPUs on par with other 1.2GHz or even bigger. But at least those are sterile tests, measuring on MFLOPS.
[Nexus S Android Development] jhalmeida:
Hi Also having some battery issues .... charged only 70 % overnight and after 7 hours only 20 % left!!!! have done a battery reset.

I have latest franco kernel + latest oxygen rom 2.3.2.

Phone is flying but battery is going very fast. Will have to calibrate battery to see if it helps this evening!
[Nexus S Android Development] casca:
Now I understand your point! thanks for the heads up.

No harm done with the words! :)

But now you got me lost...50hours is more than 2 full days.

I can assure you that, at least my Nexus S will never 100% sure, reach that usable time with my usage and settings.

Like I've said, I've got WIFI connected for at least 8hours, and the rest of the day it's also with data ON through 3G, and weak GSM signal.

On your attachment with the screenshot your battery is at 25% left, and you haven't had wifi ON according to it.

And in your case you haven't even reached 24hours yet right?

So at maximum your battery with your settings(just to remind,wifi off!)would go up to a total of 30hours with the same type of usage and and that is nowhere near 50/60hours like you've suggested to me with "wifi drain" enabled.

I'm just trying to be realistic at least about my phone,with oxygen 2.3.2 fresh install+franco kernel+battery stats wipe.

If mine hits 24h with MY normal usage, I am a happy user :)

Just ran Antutu benchmark with cpu+database IO+sdcard IO and this is what I got. Anyone to compare?

( Like I've said, I done yesterday a reset to the battery stats, so I don't know, but maybe the battery will a hold a bit longer with another 1 or 2 full charge cycles. But I am not assuming any miracle! )

BTW: So far the Kernel is BUGLESS :)
[Nexus S Android Development] lukappaseidue:
Franco thank you very much

kernel ver. 8 nov

governor lazy

min freq 400 max 1000

undervolt 400 mhz 950mv

other defalut values

rom STOCK

WOW 2 days and 2 hours and now I0m on 7% :D
[Nexus S Android Development] ro_explorer:
@casca: I have to attach again the best battery using Franco's kernel (an old version but still the best on battery performance):

This is the way a battery should drop if the phone is not used or lightly used. You can see that it will easily go beyong 2 days :).
[Nexus S Android Development] SilverEagle:
Maybe its rom related, with kelmiui i have the same power consume
[Nexus S Android Development] casca:
That is very nice indeed and if we draw a straight line from the beginning untill bed time, it would have been very interesting indeed!

My question, when you went to bed, you turned your phone to airplane mode?

Also, when it was in "before night" mode, what did you have syncing or refreshing?
[Nexus S Android Development] ro_explorer:
When I go to bed I just go to bed. I'm not turning off anything. Airplane mode is for airplanes :).

I would dare to say it is rom+kernel combination.

I might move to miui or something if I'll get better results :)
[Nexus S Android Development] got2best:
So far 13.11 has been working great.. waking on first button press.. only thing was I plugged it in last night and when I woke up I got BSOD idk why.. pulled battery and fixes.. so no complaints :)
[Nexus S Android Development] casca:
so in that case, why has your wifi connection disappeared at "bed time"?

(I'm not trying to be "funny" or ironic, I'm just trying to figure things out)
[Nexus S Android Development] ro_explorer:
I'm sorry guys ... maybe Im the bad wolf here but .. I'm the only one finding weird the fact that you have NO COMPLAINTS over the fact that you had one BSOD ? Comon .. these phones are supposed to be STABLE in the first place. Everything else comes after the stability. What's good a phone that you can not rely on. You may loose your dream-job interview or your life-salary-raise oportunity because your phone went into BSOD. Common ...
[Nexus S Android Development] casca:
I got your back on this one :D
[Nexus S Android Development] ro_explorer:
Because the wifi sleep policy is "never when plugged in" ... so, if the phone is iddling, the wifi will turn itself off allowing the 3G data to be used for background processes (draw less power overall, in my case at least).
[Nexus S Android Development] polobunny:
Got a reboot shortly after switching from ondemand 98% 15000 to lazy with maxfreq off. And it was stuck on the android screen with weird colors.

Guess lazy still isn't perfectly stable. :o
[Nexus S Android Development] SilverEagle:
You got a point. I didnt say a thing about last release because i had a lot of soft reboots, but maybe was the rom, or i exagerated with the UV. This time nothing for now, i'll test for another day or two and i see. Oh and im on lazy 200/1000 with maxfreq on
[Nexus S Android Development] casca:
so on daily usage how do you use your wifi policy?

Mine is always ON, it never sleeps (at least from 8am to 5pm :) )
[Nexus S Android Development] ro_explorer:
Usually is "never when plugged in".

In the last 24 hours test I kept it OFF all the time to see how it behaves on 3G data only (I have unlimited internet over 3G :) ). The conclusion is that is not much difference on my tipical usage (corporate mail, gmail, G+, some browsing).
[Nexus S Android Development] got2best:
That's true I didn't think of it that way.. I don't know what caused it or anyway to fix it.. I am thinking about doing a full wype.. but I hate setting everything up agian..

Anything I can do before a full wype?
[Nexus S Android Development] casca:
not much if in a strong gsm signal coverage, if like me you are on a "bunker", then it's a different story lol

I'll send you a PM, in order not to make any more offtopic ok?

---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------

Yes, do a titanium backup and restore all user apps + data after the fresh install
[Nexus S Android Development] notabene:
Depends on which ROM you are using. For example, in MIUI you can save all settings (system settings, widgets, theme, wifi passwords....) and restoring is very very easy :)
[Nexus S Android Development] got2best:
Is using titanium backup just as good as starting from scratch?
[Nexus S Android Development] polobunny:
No.

(10 chars)
[Nexus S Android Development] ro_explorer:
Yes titanium backup or "My backup root" same stuff ...

You will be able to restore your apps and their settings ...
[Nexus S Android Development] pilsna:
@ro_explorer I'm experiencing the same thing as you with regard to battery life on franco 13. I updated to the latest brainmaster at the same time, so can't say for sure why.

Can I get a hold of franco 11 somewhere, just to see the difference? Or should I wait a couple of charge cycles?
[Nexus S Android Development] casca:
It's better.

It allows you to install all chosen APK's "single click" style without any effort, and with the hability to restore or not the appliation data at the time you made the backup.
[Nexus S Android Development] polobunny:
It's different. ;)

It's a great program, but most will not use it properly and restore/backup stuff they're not supposed to.
[Nexus S Android Development] got2best:
What for example? ... like system apps?
[Nexus S Android Development] casca:
exactly :)
[Nexus S Android Development] got2best:
So lets say I know exactly how to use titanium backup.. is it still better to start from scratch?
[Nexus S Android Development] polobunny:
Mostly. If you backup user apps and data, all should go well on most cases, but be wary of backuping system apps and data.

Some user apps could also cause problem if you're restoring them, if they install drivers, plugins, require device admin or such you're likely gonna run in an unusable app.

Edit: It's always better to start from scratch, you're absolutely sure there's nothing wrong that you've restored. But if used properly Titanium Backup is a great software saving you some time. :) I rarely wipe all just switching kernels, but I always wipe all switching roms. It's up to you.
[Nexus S Android Development] HD2kty.:
Today I unplugged it at 6:00 AM in the morning and when I came home at 5:15 PM i still had 88% battery !!

Amazing Kernel.

Using it with Oxygen.
[Nexus S Android Development] ellesshoo:
Generating additional battery stats might improve the accuracy of the percentage in the middle of the range but it will not affect the total runtime of the battery or change the time your phone reports being full or when it hits 0% and shutdown. The battery's own control circuit prevents "over-charging" once the current drops below a specific threshold and the battery also signals the phone when its voltage reaches the empty voltage value. Increasing the battery stats by cycling won't affect those two thresholds so it won't change the actual time to discharge the battery from 100% to 0%. Just something worth knowing so that you are aware of what you're doing and its limitations.
[Nexus S Android Development] Ezekeel:
Your guess is wrong.
[Nexus S Android Development] polobunny:
Perfectly stable using ondemand or any other governor, crashed in a few minutes using lazy. *shrugs*

maxfreq was off. Guess I'm just unlucky. ;)
[Nexus S Android Development] ro_explorer:
This is it ... let us know the result.

Be aware .. it's just a test kernel so it is not supposed to have everything ok (but for me it does :) ).
[Nexus S Android Development] al_madd:
After get a lots of SOD...

I decided to fresh install oxygen 2.3.2...then flash your kernel...

after an hours..get another SOD...:(:(

after that no more SOD till now...

very smooth...quadrant score get 4000+ LIVEOC 10%,

better data connection, smooth,no lag.....

thanks franco....:):)
[Nexus S Android Development] polobunny:
Were these SOD always with a 10% liveOC? If so, turn it off for a moment and see if you get any.
[Nexus S Android Development] mike216:
Dont quit understand what you mean? All I was saying is I'm not getting good deepidle battery sleep and it might take a charge cycle or two before I notice battery improvement

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] got2best:
Ok I dont know if this is kernal related or not if not just let me know and I apologize.. but I decides to do a fresh install with this kernal. And when I was done.. my internet on 3G is at a crawl! Any help?
[Nexus S Android Development] Ezekeel:
Yes, I am pretty sure that was a coincidence. Lazy is derived from ondemand and I cannot think of any way the extensions and modifications I made could have caused a reboot or some other serious problem.
[Nexus S Android Development] polobunny:
I've never had ANY luck whatsoever with lazy. Never. I might run your kernel though for a while with stock voltages and everything to see if I can have it stable.
[Nexus S Android Development] pilsna:
Thanks, I flashed it. we'll see what happens... Oh and I've got idle_stats and debugging enabled :-)
[Nexus S Android Development] Ezekeel:
I do not have any statistics, but from what I have experienced and read so far, I think OC/UV is the root of most of the issues reported here in this forum in different kernel threads. So this would be my prime suspect. Also I would not be too surprised if another problem with DEEP IDLE would pop up. But lazy... no, that is one of the last tweaks I would suspect to cause any serious issues.
[Nexus S Android Development] y3mita:
Well I can tell something similar happened to me using latest test build by Franco my phone would only take on demand governor and believe me I had been able to use all other governors before with Trinity kernel so I know my phone can handle them.

what I think in my case happened is that the test build was CFS and undervolting too much makes my phone go wack!! I had reboot after reboot until I had to use fastboot and tried Glados 1.5 BFS everything went back to normal.

what I learned on my experience is my phone loves BFS more than CFS I can undervolt up to 50 in the lower frequencies and I can pretty much use all governors!
[Nexus S Android Development] polobunny:
Hm. Deep idle WAS enabled too. That might be something, didn't think about it at first. I haven't used lazy enough without deep idle to say whichever caused problems. My apologies for targeting lazy without grounds.
[Nexus S Android Development] ro_explorer:
Make sure you start and stop camera before using this kernel .. otherwise no deep-idle :)
[Nexus S Android Development] y3mita:
haha you beat me to it... I was going to request this as well....

Franco, I am a fan of your kernel and after trying the test builds I decided to stay with the BFS Nov 13 it is working fine so far.

And as user above me said, what are the odds of adding these functions to your kernel? http://xdaforums.com/showpost.php?p=19346009&postcount=379

If not, we still can do it thru Recovery no biggie :D
[Nexus S Android Development] droidfreak007:
great kernel.

no probs so far and no lag.

also no probs with nstools as other users previously stated.

using oxygen 2.3.2 with the latest update.
[Nexus S Android Development] got2best:
When u use a task killer how much free ram do u get? I feel like I lost a bunch. I have also heard it is bad to use a task killer, is that true?
[Nexus S Android Development] Zorrich:
Did a full wipe and installed the new oxygen update and this kernel and my old problems appear to be gone. Very happy with November 13 update so far.

Thanks!
[Nexus S Android Development] thedudejdog:
Yea, I think it should be a prerequisite that you wipe everything and reflash before posting a bug. 9 times out of 10 it's user error or a rouge app messing with stuff.

/rant
[Nexus S Android Development] FL0OD:
I would guess most people don't use them anymore. They have a tendency to harm more than help since Gingerbread dropped.

Sent from my neXus s 4G
[Nexus S Android Development] franciscofranco:
Don't use task killers for the love of god, it's been stated everywhere that they do more harm than good, google it.
[Nexus S Android Development] FL0OD:
So Franco, any idea of what in store for us with ICS dropping? What's involved? Because you can guess everyone will be asking about that next.

Sent from my neXus s 4G
[Nexus S Android Development] Zorrich:
Agreed, but to be fair the November 8 kernel worked well before and after i tried the November 13. Odd that a rogue app as you say is only an issue in the new version. But whatever, doesn't matter now.
[Nexus S Android Development] Yusei:
I've already use live oc at 110 and never had a bsod

every time I flash a new kernel I wipe dalvik , may be he didn't do that
[Nexus S Android Development] franciscofranco:
There will be a continued support from me as soon as 3.0.1 kernel sources are out and we start having roms with the new ICS source code supporting this newer kernel. There is not much more to say at this time, but I'm sure this new kernel is much better and polished, the changelog is huge I don't know many specifics. We'll see.
[Nexus S Android Development] HeavenlyWinds:
got 15 hours of battery life after heavy usage. (3G on for like 4 hours, wifi on for 10 hours) and around 5 hours of games, facebook, texting and browsing.

Thanks for the amazing kernel.
[Nexus S Android Development] al_madd:
Of course I wipe dalvik..

Just fresh install oxygen 2.3.2...

Wipe dalvik using dalvik.wiper(morfic) , flash 13 nov cfs..

Still get 2 BSOD after 10 hours...

Nevermind...I can live with it...thanx...
[Nexus S Android Development] y3mita:
How about you go to recovery.... wipe cache and dalvik cache and this time flash BFS version of the kernel.
[Nexus S Android Development] Yusei:
Have you wipe data and cache befora flash your rom?

With Matr1x i've same problem as you, but after a clean install everything is fine
[Nexus S Android Development] phone_user:
You're the greatest! :) Thanks
[Nexus S Android Development] al_madd:
Ok...I will try...im avoid using bfs because data connection problems..

Thanx
[Nexus S Android Development] al_madd:
Yes..i did it...

From my opinion..

I dont think it causes by voltage, because previous version I dont have any of this problems..

Min 440, max 1100..

Nstools? Maybe...just reset nstools, so far so good for this 2 hours...hopefully this will fix it..huhu
[Nexus S Android Development] franciscofranco:
New testing version is up. Things to notice:

- Changed colors, courtesy of morfic

- Added Ezekeels "crap cleaner" during kernel flashing
[Nexus S Android Development] tylercarter:
Just wondering. Where are these test versions?
[Nexus S Android Development] franciscofranco:
Everything is in the link in the first post..
[Nexus S Android Development] mike216:
I see interactive is new,did you change your mind about it?

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] tylercarter:
My bad. I overlooked it. Sorry for making you repeat yourself yet again. Thanks for your great work.
[Nexus S Android Development] mike216:
Colors look good! Get back at ya later after some testing

I can confirm about the speed! Very zippy

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] damnmisur:
Feel as though this test version is more speedy. Colours are great.

Sent by my Nexus S 9020a on Telus running the flavour of the day.
[Nexus S Android Development] franciscofranco:
There were a bunch of patches released for interactive. I applied them and thought about enabling it back for some testing.
[Nexus S Android Development] mike216:
Well then thank-you because its pretty f+** awesome on this test build, feels very quick when trying to slow it down

Its bit quicker and more responsize then ondemand

Sent from my I9020T NEXUS S/NSCOLLAB, IS THE BEST PHONE BECAUSE WE HAVE THE BEST DEVELOPERS!
[Nexus S Android Development] ro_explorer:
I'll refrain myself in flashing for few days :) .. I want to put some uptime on my phone before trying new things. So .. I'll stick with one of the old Franco's kernel for about one week or so . I will decide today which one will be.

I don't know why but all the kernels after Oct 27th have bigger drainage in idle/deep idle. Bigger means bigger than 1% per hour (or in that area). Just to make sure I'm not crazy, I flashed (again) the Oct 25th version yesterday evening and indeed .. I lost 3% over 7 hours of sleep (with everything on, as usual).

So .. for me is clear: something dramatic changed in deep idle in the Oct27-Nov1st zone. That something was never brought back and all the enhancements were done in the active mode.

It's time for me to start actually using my phone for a while instead of flashing a new kernel every day or two.
[Nexus S Android Development] Heretic Infidel:
I have to agree with this. With the last couple of kernels i have been seeing a 30 to 35% drop in battery while i sleep +- 7 hours. Mobile Standby being the main power hog even though cpuspy shows the device being asleep.

I guess that this is my radio requesting a reflash? Running kf1.
[Nexus S Android Development] casca:
flashing the test version now. but since minor tweaks were made, I'm not expecting anything noticeable. will report if bugs are found.
[Nexus S Android Development] Cybergr:
Excellent work on your last stable 13.11.11 Kernel CFS as always..

Blazing fast and no problems for the moment in combination with Oxygen 2.3.2 Rom!!I am very happy with the results!!
[Nexus S Android Development] pilsna:
I lost 14% in 8 hours last night running the nov 11 kernel.

Idle stats says: Deep Idle (TOP=OFF) 69278 ms, 74 ms (not sure if that is good or bad)
[Nexus S Android Development] ro_explorer:
See? this is what I was talking about.... too much drain with the phone doing nothing at all.

Compare that with my plot (just took this) and see that gorgeous overnight graph :).

Anyway, there are lots of setups, rom, modems and phones .. is normal not to have 2 phones acting the same.

For me is clear. I'll stick with Oct24 kernel ... this is the best for me. I'll stay with it until I'll get to at least 200 hours uptime :).
[Nexus S Android Development] al_madd:
anyone using oxygen 2.3.2??

have you all having problems while playing video??

my phone freeze while playing video using mobo...

LIVE OC 110%, lazy, enabled screenoff_maxfreq,min 440,max 1100
[Nexus S Android Development] vis80k:
video plays fine. using vital player.
[Nexus S Android Development] franciscofranco:
I'm not worried because overnight drain means nothing to me because overnight I charge my phone, as should everyone. I'm happy with my phone's battery life and there's not much, if anything to do to increase it more.
[Nexus S Android Development] raulillo88:
But there are something wrong in this kernel because in flight mode drians between 13-15% and the stock only 2-3% there are too much difference

Enviado desde mi Nexus S usando Tapatalk
[Nexus S Android Development] franciscofranco:
Then if stock is only 2%-3% use stock.
[Nexus S Android Development] damnmisur:
Bsod on test. Seems to be when I get a notification (email) it happens.

Sent by my Nexus S 9020a on Telus running the flavour of the day.
[Nexus S Android Development] got2best:
Did u get a text or email? Possibly BLN is using up battery.?
[Nexus S Android Development] notabene:
Stucked at bootloop with 15.11 testing kernel, Brainmaster MIUI 11.11. Stock setting, noliveoc, no UV, used NS Tools reset to reset settings, but nothing happened.. Need to restore backup. :)
[Nexus S Android Development] MultiCulti:
I´m running on KelLMSKing MIUI with franco.Kernel since 5 oclock in the morning ... no issues at all, BLN working fine, Signal is also good, BT working well ...

hope it stay´s like this :D