yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Black Coffee:
Hey.. First of all thanks alot for your kind reply.. I have only few apps installed in my phone including Facebook, Twitter apps & couple of messengers + I never use mobile data since most of the time I'm on Wifi & GPS is always off.. Attached is the screenshot for your reference ..Cheers..
[Nexus S Android Development] franciscofranco:
Facebook app is a cancer, I got rid of it as soon as I noticed it to be keeping my phone alive. Try Friendcaster.
[Nexus S Android Development] Black Coffee:
Thanks a lot for showing the courage to help me out.. Please find the attached screenshots in the above post.. This screenshot was taken after a reboot.. Cheers mate ! :)

---------- Post added at 01:03 PM ---------- Previous post was at 01:01 PM ----------

Sure Mate, Will try that.. Thanks !
[Nexus S Android Development] eiabea:
wifi problem was caused by the router :D sry!!

but i mentioned a higher battery drain than in the last release, 10% in 2 hours
[Nexus S Android Development] martinsjt:
Hello,

I use SuperOSR V2 2.2.4 Nexus S por Superteam Gingerbread 2.3.7 with LiveOC at 110, Deep Idle enabled and over night I had a 1% battery drop, amazing.

With Quadrant I get a 4000 score using Lazy gov.

I had some issues turning on the LiveOC and the Deep Idle due to lack of init.d folder so I use Script Manager that run the scripts at boot.

This is the best kernel ever on Nexus S obrigado Franco.

Best
[Nexus S Android Development] skinniezinho:
Great results!

Just one thing.

If Franco says Deep Idle is enabled, why and how did you manage to "enable" it?

Or does it have anything to do with the rom that you use?
[Nexus S Android Development] franciscofranco:
Deep idle is enabled by default in the kernel.
[Nexus S Android Development] skinniezinho:
I know Franco, you said it dozens of time here, but if so, why or how can anyone tell "deep idle enabled" (it should be enable "Stock" right?!).
[Nexus S Android Development] morfic:
<6>[ 3.804298] deepidle_status_write: DEEPIDLE enabled

from desktop:

adb shell dmesg

or just dmesg from terminal emulator

Unless you ask for a way to get to Deep Idle stats, different story then.
[Nexus S Android Development] caleb1783:
if i m not mistaken, init.d folder is named super and super2..

Sent from Divinus Nexus S...
[Nexus S Android Development] caleb1783:
i know fb is cancer but i keep it around for contac picture sync... is there any other way than using fb app?

Sent from Divinus Nexus S...
[Nexus S Android Development] skinniezinho:
FriendCaster as Franco told a couple lines after that post.
[Nexus S Android Development] MultiCulti:
SyncMyPix ;)
[Nexus S Android Development] martinsjt:
Yes my mistake I have been following the Ezekeel thread about the Deep Idle and when sysfs interface was implemented I presumed that Deep Idle was deactivated by default, another case of failure to read the first post ;)

Thank you all :)
[Nexus S Android Development] MultiCulti:
ok, halftime guys :D

still now under heavy usage i got just ~ 3,6% battery drain per hour :D
[Nexus S Android Development] martinsjt:
I never put the time to read the SuperOSR original thread, something about the Spanish ;)

Great Tip, worked.

Best :D
[Nexus S Android Development] caleb1783:
i was talkin about photo sync though.. but i will definitely try friemdcaster..

thanks!

Sent from Divinus Nexus S...
[Nexus S Android Development] caleb1783:
thanks! gonna give it a shot!

Sent from Divinus Nexus S...
[Nexus S Android Development] vis80k:
can't agree more with your signature text! why'd google ever allow the phone to be named Galaxy Nexus?!?! it makes Nexus Prime sound like a series of Galaxy and it is not!
[Nexus S Android Development] EdForce1:
You could use Cpu Spy as well? Lists how long your phone resides in different clock frequencies, including deep sleep. Correct me if im mistaken.
[Nexus S Android Development] ro_explorer:
Another 24 hours have passed. This tine I've started all over again due to the new kernel.

Current setup:

KERNEL: franco's oct 27

ROM: 2.3.6 - stock

DEEPIDLE: enabled

LIVEOC: 110

GOVERNOR: conservative

MIN-MAX FREQ.: 100-1000 MHz (with liveOC the interval is 110-1100)

VOLTAGES: 950 - 960 - 1065 - 1220 - 1275

OTHER: WIFI always ON, 3G/2G auto, Data on, 2x email acounts with push.

With the above settings I've got drainage 4% over 8 hours of night sleep and in general I see ~1% drop every hour during the day (the amount of e-mails received during daytime is hige, especially on the corporate account - about 50 emails each day).

If I'm listening to music using the bluetooth headset, I'm getting about 3-4% drop per hour.

The user experience is fine, everything is smooth and running w/o glitches or delays.

No random reboot until now and I hope it stays that way :)
[Nexus S Android Development] chickelnoodensoup:
Deep sleep is not the same as deep idle.
[Nexus S Android Development] magrejh:
I told you that, deep-idle seems not work

Finally, I got the reason. since 2510 kernel, this kernel drain too much battery on using wi-fi.

I barely use 3G mobile data, and I always keep turn on wi-fi.

below screen shot is today's using.

http://image.kilho.net/?pk=633719

and this one is previous version of this kernel.

(sorry its wrote in korean.. but you understand..? isn't it? haha)

http://image.kilho.net/?pk=633721
[Nexus S Android Development] al_madd:
I have the same problems with you..

right now fresh install CM7.1...flash franco.kernel..

purchased betterbatterystat..

days I searched for culprit drained my battery a lot..because many user have good battery life...

damn!!!:mad::mad::mad:

Edit: right now turn off all sync(check battery use, google services is the main culprit, weird, many of android user sync their data but dont have this problems), airplane mode...

will going to watch movie at cinema,will check after 3 hours, hopefully will get good result...:)
[Nexus S Android Development] v3rk:
can i ask a question? why do you continue using 100min frequency as your baseline to begin testing when it's been said a lot that 400min is recommended to ensure the phone will enter deep idle mode?

appreciate all the info and testing you've provided this thread :D
[Nexus S Android Development] noobhero:
Officially given up hope on liveocing lol.

With either stock or increased voltage, just a 110% liveoc

I faced system freezing.

Alot of times are during scrolling up/down

Sometimes quadrant benchmark wld just freeze also.

With the 21st oct kernel, i use setcpu just fine, tried it on markvis and superosr rom both same result. :(
[Nexus S Android Development] ro_explorer:
I understand that 400 is the minimum recomended. Anyway, from my experience and knowledge, there are no 2 identical devices so, what's recomended for some or most, might not be the ideal setup for me.

When I'm testing a kernel I'm always starting with the widest range of ... well ... everything. In time, usually with 24 hours granularity, I'm adjusting the respective range until I'm getting to the optimal results.

And in the end, even if is taking me one week to reach a certain stable point, others might discover that their devices are behaving well (or better) using the values I'm getting as "ideal".

And one more thing: giving the fact that Franco's kernel is built using pieces of code developed initially by others, there is no way of telling that some bug-fix implemented by someone in their code will not affect other stuff already there ... that why, when I'm starting a new set of tests, I always reset the refference point.

Anyway, as long as my phone doesn't explode and I can use it to complete my daily tasks, I don't see any draw-back in testing all aspects of a new kernel.

For example, my phone doesn't take too well 1200MHz freq. or above. No matter how I'm playing with the voltages, under certain stress the phone will reboot. This is NOT the case for most people out there but it is definitely changing the aproach for me.
[Nexus S Android Development] nazimster:
can this kernel works on ics 4.0
[Nexus S Android Development] franciscofranco:
No idea.

Is anyone interested in a future BFS build? At least for testing.
[Nexus S Android Development] ro_explorer:
From my previous kernel tests is no much difference between a well tuned CFS build and BFS (at least from the end-user "feeling" point of view).

I'll test it if you really want to build one :) but I'm very happy with the current one.

And I have a question for you.

I'm currently building my own "cloud" to say so. Actually, I have a small server at home and I want to use on my NS its 1TB hard drive over VPN using samba (live, no matter where I am). So, both TUNNELING and CIFS support will be used at maximum :). Are you aware of any drawbacks or things that I should be aware of when implementing this structure?
[Nexus S Android Development] franciscofranco:
Nah, everything should work. CIFS and TUN are both included in the kernel!
[Nexus S Android Development] skitapa:
I would like to try out a bfs build. I can report back my experiences :-)
[Nexus S Android Development] ro_explorer:
It happened :( ... sudden reboot .... apparently my phone doesn't take well OC, not even 10%. Back to stock voltages and frequencies.

Sent from my green robot ...
[Nexus S Android Development] skitapa:
I still think you could up the voltages, upping the bus should make cpu and gpu more hungry for power.
[Nexus S Android Development] ro_explorer:
Agree... but I'm afraid that by increasing more the voltages I'll loose the balance between the performance and battery life.

Sent from my green robot ...
[Nexus S Android Development] skitapa:
Why be afraid when you have the opportunity to find out? ;-)
[Nexus S Android Development] :
Yes, for at least testing, and at most, who knows! Is this the brand new BFS?
[Nexus S Android Development] ro_explorer:
I should have started exposing my fears by introducing my job profile :).

I'm working into a high-tech company and I'm used to the testing of the CPUs and GPUs (ARM/MIPS .. whaever :) ) ... We actually produce such things ... starting from a netlist and ending with the actual units. I know quite a lot about the CPU testing procedures over a large variation of voltages, frequencies and temperatures. The goal is to have the whole lot behaving almost identical in certain points. We, of course, are testing also the extreme limits and there are parts that are passing great in those conditions, but the percentage represented by those parts is low compared to the whole production (with luck .... 10%). So you see .. you must be really lucky to have a cpu that can suport everything.

I know for sure that my CPU will not behave on the OC frequencies except if I'm raising the voltages very high. I have done an additional test, different from the last voltages showed few posts back. I actually increased everything more. The phone started to get warm in the CPU area so I concluded that my unit can not perform well in that range.

Anyway .. the phone is blazing fast with stock frequencies also so I don't complain. I'm just a little dissapointed :).
[Nexus S Android Development] ciwek90:
What is the best setting for this kernel for BM MIUI? some times i got random reboot...idk why..maybe i got wrong setting for it...need to know what is the best one..thanks!
[Nexus S Android Development] franciscofranco:
Yes, I got curious as I only used BFS in low end phones and some ugly backports to .32 kernels. At this moment it's running BFS 0.413 on my phone, will test it in the next days.

There is enough information in this thread, use the search function.
[Nexus S Android Development] coloxim:
Now your kernel works very good..deep idle too..I've a good battery...wow..

Inviato dal mio Nexus S
[Nexus S Android Development] khartaras:
Great work Franco. Would you mind making a BFS build?
[Nexus S Android Development] skinniezinho:
I used BM MIUI for a while with various Franco Kernels,no reboots.
[Nexus S Android Development] mixtapes08:
Im gonna test it for now ill report back as soon as possible
[Nexus S Android Development] morfic:
Would be interesting to see if stock rom users then lose /sdcard mounting again.

Cure for it is not using BFS for stock roms.

As much as i love to pimp BFS, not sure what interacts with it, right now BFS builds are not the usual winners amongst blind testers. o_O
[Nexus S Android Development] khartaras:
Or better, don't use stock roms.
[Nexus S Android Development] arshad14:
Franco, love the new kernel. Didn't have this happen with your last update but this one I had a freeze so raised the minimum to 200 with smartassv2 governor. So far its perfect! :-D
[Nexus S Android Development] PLEEZEFRAGME:
for me it says

C:\android\tools>adb shell dmesg

klogctl: Function not implemented
[Nexus S Android Development] mike216:
I was one of the people who got bad battery drain after flashing yesterday at around 90%. After a full charge battery holding up much better ! Battery stats must have been way off or something but it drained like crazy yesterday and today I had 11 missed calls woke up 8 hours later and had 96% so that's not bad and I suspect after another charge it will be even better, thanks

Sent from my G1
[Nexus S Android Development] mike216:
From my experience I like CFS much more thanks BFS,just my op

Sent from my G1
[Nexus S Android Development] skitapa:
You need to load the logcat module. Try using imsmod modulename. Look in a modules dir, don't know where in android.

Good luck :-)
[Nexus S Android Development] brenix:
Been running with the latest BFS commit for a couple hours now... Appears to be running smooth..no issues yet..will test some more..
[Nexus S Android Development] franciscofranco:
Use this settings for extra smoothness and come back to me:

rr_interval = 1

iso_cpu = 100

You can change them in /proc/sys/kernel.

To the rest of you, this is just testing ****, there isn't a BFS avaliable for download. If you want to test it build my kernel from sources and posts feedback.
[Nexus S Android Development] mike216:
Franco I got bored and decided to try liveoc with set cpu removed with stock voltages and just using my rom to control the min and max and I have to say I'm loosing less battery than if I weren't overclocked and using set cpu so dont know if my phone doesn't like set cpu to adjust voltages or what but this is extremely weird rite now?

Could any kind person tell me how I can get liveoc to stick I'm on my favorite nscollab rom so I know I have Inuit.d support,got script manager from the market but have no idea how to use it,thanks

Sent from my G1
[Nexus S Android Development] skitapa:
Start script manager, new script. Tick run as root, dont tick run on boot until you have run it successfully manually. Then edit script, and just enter the text as you would in the terminal.

For example:

echo "110" > /sys/class/misc/liveoc/live_oc (or whatever it is.)

echo "yay, happy me"

And so on...

A shell script or bash script is just an automated version of you typing it :-)

You could also set up init.d scripts but it's simpler using script manager.
[Nexus S Android Development] mike216:
Damnit just got a reboot whats the highest I can go on voltages without being to high

Never mind 20-30 above stock is ok. That's still a slight undervolt

Sent from my G1
[Nexus S Android Development] brenix:
Tested these and it seems to slightly make the UI interaction possibly appear less choppy..Hard to tell when it's already so smooth. I also tried a value of 2 for the rr_interval and it was about the same though.. Also, 3D scores are slightly higher than before..

Was running with wifi etc on with a liveoc value of 110.. No reboots or any issues..
[Nexus S Android Development] PLEEZEFRAGME:
found it but how do i Load it? In terminal "run /system/bin/logcat" ???
[Nexus S Android Development] franciscofranco:
Yes 3D scores are noticeable higher with BFS. I'll keep testing this in the next days.
[Nexus S Android Development] mike216:
I'm running nscollab and ever since I've turned my sync off I'm now down to a very low -2ma battery loss,thanks for this helpful post

Sync is good but ill just turn it on before a flash

Sent from my G1
[Nexus S Android Development] al_madd:
Finally, I solve my problem...

It is whatsapp which drained my battery..for weeks I sreach for this culprit which prevent my phone going to deep sleep...

just remove whatsapp to sdcard: the only con when remove whatsapp to sdcard, a little bit lag and somtimes pending....

finally..I get a better battery life...:D:D
[Nexus S Android Development] chinopski:
status bar icons

may data icons on status bar don't turn blue. always white. anybody having the same issue?
[Nexus S Android Development] roshga:
How did you move it to sd card? When I go I'm the settinga I don't have the option to do do..
[Nexus S Android Development] al_madd:
which ROM do you use??

I use CM7..setting, allow move apps to sd card...;)
[Nexus S Android Development] morfic:
Do you have other apps on sdcard now?
[Nexus S Android Development] al_madd:
does not understand exactly your qeustion actually...

my answer is yes..:)
[Nexus S Android Development] caleb1783:
wow... really?

I am gonna move mine to sdcard as well..

Thanks man..

---------- Post added at 11:35 AM ---------- Previous post was at 11:17 AM ----------

what does moving an app to sd card do?

should i move my facebook/twitter app there as well to prevent staying awake?

Thanks guys.
[Nexus S Android Development] jemping:
Hi, I got a question.

Sorry if this has been answered before, but does this kernel support touchwake/screen dimmer/backlight dimmer mod by Ezekeel?
[Nexus S Android Development] al_madd:
..yes...of course

---------- Post added at 06:38 AM ---------- Previous post was at 06:33 AM ----------

check whether your phone always wake...

if yes..try remove you apps such as YM,Whatsapp,FB,twitter to sd card..

I dont know how..but it helps..
[Nexus S Android Development] mike216:
Al madd has a great find that will help is CM and nscollab rom users!

If your running live oc and getting reboots with stock voltages then go to Cyanogen settings/performance/and uncheck the top setting unable dithering setting and reboot

Every since I did this I can now run liveoc at stock voltages without reboots not that we need to run that high on franco's masterpiece but if your into tinkering with your phone and ran into reboots and on cyanogen based roms please try

Also without unchecking this setting I was able to liveoc with 20 above stock (at stock your still undervolted though ) hope this can help someone and thanks al madd for being the very helpful person who found this helpful setting that alot of us like me overlook when trouble shooting

Sent from my G1
[Nexus S Android Development] skitapa:
There is a missing softlink which can make things easier. Create it with these commands:

$su

#ln -s /system/modules /system/lib/modules

Then you should be able to load the module with the command

#modprobe logger

Then you kan download and run alogcat from market or the binary logcat.

To remove a module use

#rmmod logger

In linux/unix binaries are run like this

#/path/to/binary/logcat

Or if you are standing in the same directory you can use the shortcut

#./logcat

Good luck :-)
[Nexus S Android Development] xXfuzzXx:
Had another curious thing with battery:

Lost 14% over night (8 hours sleep :P ) and had left 6% which i easily killed within 5mins with just WiFi on and browsing the MIUI theme database o_O

I mean, does this kernel use in fact more battery when hitting the 15% line?
[Nexus S Android Development] ro_explorer:
Nope, that issue is related to the calibraion of your battery (actually the phone being able to read correctly the battery levels). This thing will auto-regulate in couple of full charge/discharge cycles.

And my feedback ..... 3% loss over night (54% - 51%).

The battery life is excellent. It will last at least 2 days with my usage (compared to ~30 hours one week ago).

Great job.

Franco ... Monday is my pay day ... I'll be contributing to that prime also :P.
[Nexus S Android Development] mike216:
+1 when I first flashed I had battery drain even though I flashed with 90% battery it still drained then battery got a little better the second charge and now that I'm on my third charge I'm now seeing that extremely great battery life that deepidle brings, curious to see if others have had this experience

Sent from my G1
[Nexus S Android Development] jodtalingchan:
Mike, what's your setting? I'm going to try this too. Heard that franco kernel gives us amazing battery life.. Thank you franco ...
[Nexus S Android Development] caleb1783:
hey mike. did u wipe bat stat after installin da kernel?

and do u go through complete discharge? as in let the phone turn off automatically?

Sent from Divinus Nexus S...
[Nexus S Android Development] roshga:
im on miui, have the option to move other apps to sd, not whatsapp tho...
[Nexus S Android Development] caleb1783:
or u can use titanium...

Sent from Divinus Nexus S...
[Nexus S Android Development] mystraw:
logcat problem (and solution)

I'm not sure if you know this problem (and solution) or not.

First time, after flashing this kernel, I inserted a logger.ko module to kernel, but there's no log message(only few messages, dalvikvm....)

So, I wrote a script inserting the module in /system/etc/init.d/ directory(using CM7 ROM), It works. I'm happy to logcat now :D

(It will be a only problem for stock rom(or some others) users because there's no init.d directory)
[Nexus S Android Development] roshga:
@caleb1783

Thanks a lot mate, titanium worked like a charm :)
[Nexus S Android Development] doc_v15:
Im using the 27th oct update, my setting is:

Conservative ONLY, no volt changes, 100 live oc. Thats all

Been running for 8hrs 39min since full charged

My apps that are active:

Whatsapp

Friendcaster

Yahoo Messenger

Moxier Email (exchange sync)

News app

SMS,

Brightness 15%

3G on for 4 hrs

My battery is 46%!!! :(

Just wondering, is that normal with the kind of setting?
[Nexus S Android Development] ro_explorer:
What have you been doing over these 8 hours?

Can you post a pic with yout battery usage (the android default tool)?

Apparently you're draining about 6% per hour which is quite OK but only IF you are actually using your phone A LOT. I'm getting that king of drainage while watching movies or while I'm browsing or chatting over IM.

I can drain completely the phone in about 5 hours if I'm putting my mind to it but generally, under medium-heavy use I'll get about 16 hours (almost like you have right now).

It is important to tell what have you been doing over those 8 hours :).

As a heads-up .. YM is quite power hungry according to my knowledge .. you might wanna try "Go Chat for Yahoo" .. it is much more batt. friendly compared to yahoo native app.
[Nexus S Android Development] al_madd:
check your running application..

I think google services..

I think thats the main culprit....

post your screenshot here...
[Nexus S Android Development] vis80k:
you get 6% battery an hour from heavy use?! wow! I easily drain 6% when browsing for about 30 minutes! with 3G and GPS ON with brightness at 40%....
[Nexus S Android Development] doc_v15:
here you go
[Nexus S Android Development] franciscofranco:
No wonder you drain 6% an hour, the phone is always awake - it never enters idle it never saves power.
[Nexus S Android Development] doc_v15:
Hmm..It was in sleep mode for 3 hrs...

Honestly, what requires for the deep idle to be activated? :) thanks
[Nexus S Android Development] ro_explorer:
Franco is right .. somehow your phone doesn't go to sleep.

Here is my phone over last few hours:

The vertical lines are hours.

As you can see, the BIG drop of about 7% (just after I took the phone out of charger) was happening while I was browsing and upgrading some of my applications on the phone, having the screen on the entire time. As soon as I finished these tasks, the phone went to sleep so the drop is about 0.5-1% per hour.

See the above picture ...
[Nexus S Android Development] DoktorZero:
I'm testing the new update, and I'm very happy. great job franciscofranco
[Nexus S Android Development] coloxim:
Which program do you use?

Inviato dal mio Nexus S