yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] chinopski:
openvpn issue

hey franco flashed your latest kernel earlier today, it was fast and i was amazed by the battery life. thank you very much for your effort!

im a regular user of openvpn, and i noticed that i cant connect my openvpn using your latest kernel. (i have the same issue with morfic's kernel). i was able to connect my openvpn using the previous versions of your kernel, that's why i can confirm that the problem im experiencing is because of the kernel.

i am no dev, so i cannot pinpoint the problem in the kernel. could you please help. im a fan of your kernel, especially the latest version but openvpn is really a deal breaker for me.:(
[Nexus S Android Development] al_madd:
not working for me..strange.....110% has been perfect for me....
[Nexus S Android Development] rip_noob:
Same problem here, reverted back to 27/10 and it was fixed.
[Nexus S Android Development] vis80k:
bfs is first for me but it seems to work well as was cfs. what difference should i be looking for between the rwo?

Also, I guess lazy+ will be ciming later~? looking forward to it! :)
[Nexus S Android Development] franciscofranco:
You have to load the module from /system/modules. The module is tun.ko

To everyone with wifi/data issues and USB mounting issues, that will be fixed today.
[Nexus S Android Development] igor.tonky:
i have the same problem - after some screen off time, like an hour or two, data over wifi stop working, with green indicator and 'refreshing' icon in status bar.

it also happened when phone was in the airplane mode overnight, and then i turned on wifi, but it didn't work.

rebooting helps.

cm nigthly 240, 0111 kernel, no di, live_oc to 130. same with di, though.

i can't get logcat to work. what am i doing wrong?

# insmod logger
insmod: can't open 'logger'
# cd /system/modules
# ls
ansi_cprng.ko cifs.ko scsi_wait_scan.ko
bcm4329.ko logger.ko tun.ko
# insmod logger
insmod: can't open 'logger'
[Nexus S Android Development] nickmv:
I'm new to this kernel (usually I use Trinity TEUV's), but anyways, I'm having a few problems, and hoping you can help me franco.

I did cache & dalvik wipe, and flashed the Nov1 kernel. I confirmed that deep idle was active, and from what I could tell from reading this thread, I set setCPU to 400mhz min, since in deep idle it won't matter (is that theory correct?).

Anyways, I woke up in the morning to find my phone had dropped a good 35%.

I double checked batt use, and Beautiful Widgets had suddenly decided to use almost 25% of my batt! I assumed at first that it had a mem leak, but I've never run into this before. I uninstalled, cleared data, reinstalled, restarted, etc, and it still seems to be sucking battery up.

When I switch back to Trinity, everything is fine.

Got any ideas?

Also, what profile should I be setting to in setCPU? I've never noticed a Smartass version 2. I wasn't sure whether I needed to set something for deep idle.
[Nexus S Android Development] franciscofranco:
Small update in the first post.

Dunno. Just use Lazy without profiles and you're good to go.
[Nexus S Android Development] DebauchedSloth:
Thanks!!!

Installed it, giving it a whirl, so far so good.

---------- Post added at 10:28 AM ---------- Previous post was at 10:21 AM ----------

Hmm. Data looks good so far.

Locking the CPU freq at max is a problem here. The audible app, which used to spend virtually all of its time at 100mhz with screen off, is now almost locked to max freq. I'm not shocked, really, since it's decrypting the audio and playing it, it's not getting to idle. Not a good app.

Is there some way to disable the lock-to-max-freq screen off behavior?
[Nexus S Android Development] franciscofranco:
Yes there is, but like I already said in the last pages, disabling that is destroying the whole purpose of racing to idle and saving more battery. Just go to deep idle thread and read about it, Ezekeel explained that, I explained it too...
[Nexus S Android Development] DebauchedSloth:
Yes, I'm pretty clear on why you want to race to idle. The problem here is that this app is waking up so often that idle isn't happening. Previously, it just ran at 100mhz - now it's running at max freq. So the effect, for this app, is to make battery worse.

I'd love to ditch it, but no other way to play audible audiobooks.

Edit: found screenoff_maxfreq. That fixed it.
[Nexus S Android Development] naz78:
Okay, so below are my settings. Can one of you experts tell me if I need to tweak anything to get more out of my battery life? Is there any other setting that I should be checking? Thanks in advance!
[Nexus S Android Development] MultiCulti:
franco ... i have battery drain around ~ 150 mA on sceen off ... its not going into deepidle, or?
[Nexus S Android Development] igor.tonky:
i noticed it's the default now and i immediately knew people will have big drain with it.

while i get all the reasons for this and read ezekeel arguments, i find screenoff_maxfreq == 1 draining too much for light offscreen load(playing mp3 on max frequency? no, thanks!)

so, to anyone experiencing above average battery drain with lazy(should be everyone, i think :-D) - just disable the usage of max frequency:

adb shell 'echo 0 > /sys/devices/system/cpu/cpufreq/lazy/screenoff_maxfreq'

and to verify:

adb shell cat /sys/devices/system/cpu/cpufreq/lazy/screenoff_maxfreq

should be 0.
[Nexus S Android Development] franciscofranco:
Yes exactly, if anyone wants to disable that behavior just use this lines in the terminal on adb.
[Nexus S Android Development] from1989:
e save power?
[Nexus S Android Development] thoth77:
Performance + Powersave

simply for example
[Nexus S Android Development] johoja:
Franco, are the idle_stats working for the latest kernel version Nov2 ?

I'm getting this:

H:\>adb shell cat /sys/class/misc/deepidle/idle_stats

idle state total (average)

===================================================

IDLE 1628459ms (13ms)

DEEP IDLE (TOP=ON) 0ms (0ms)

DEEP IDLE (TOP=OFF) 0ms (0ms)
[Nexus S Android Development] Lazat:
Could you make a 2now edition with the BFS scheduler? Pretty please, your now 1 was awesome on my phone :)
[Nexus S Android Development] mike216:
Deepidle is enabled on 02 release!

Just woke up and flashed so will report back after I put it through another beating

Franco I seen your post that says you will have a small update is 02 the small update? Feels good so far but will report back. Thanks :)

Sent from my NSCOLLAB + FRANCO'S 01 BEAST
[Nexus S Android Development] mike216:
Move your minimum up to 400

And these are my suggestions

And of your getting bad battery life YOU MUST GO THROUGH A FEW CHARGE CYCLES BEFORE YOU KNOW HOW YOUR BATTERY LIFE IS GOING TO BE

Sent from my NSCOLLAB + FRANCO'S 02 BEAST
[Nexus S Android Development] Ezekeel:
Keeping the frequency at a maximum while screen-off is the best way to minimize battery drain as long as two conditions are met.

First, DEEP IDLE needs to be working. Check idle_stats if it really it (remember that DEEP IDLE will not be used while screen-on or while connected to USB). There were some issues with an error in the ROM or some app to activate the CAM module on boot which prevents DEEP IDLE from being used. Opening the camera app once and then closing it, should properly disable this module.

Second, no background process keeps waking up the device at an excessive rate. Check the average time for the DEEP IDLE state with whatever background app you want to use (you can reset the stats with 'echo 1 > reset_stats'). It is hard so say which is an acceptable lower limit, but with wakeups lower than 5ms I would be worried and look out for an alternative for that app. The higher the average times the more efficiently race-to-idle and the DEEP IDLE state will work.
[Nexus S Android Development] coloxim:
Sorry ezekeel..but if i do something while the screen is off for example listening music or downloading some app or charging browser, the CPU is always at Max frequency!?!?

Thanks..and sorry for the doubt..

Inviato dal mio Nexus S
[Nexus S Android Development] beetlo:
Will this kernel work for the 4g model? It has all the features I want and is the only one with up to date Deep Idle. :)
[Nexus S Android Development] mike216:
I know this while listening to music my battery is twice as good as it was yesterday! Extremely great battery life, thanks franco and Ezekeel

Sent from my NSCOLLAB + FRANCO'S 02 BEAST
[Nexus S Android Development] franciscofranco:
Google translate -> translate to italian Ezekeel's explanation, there you have your answer.

Yes :)
[Nexus S Android Development] Lazat:
As you can see, when I play music with spotify it averages to 5ms, should I be worried? :-/ because I can not really change music app..

# echo 1 > /sys/class/misc/deepidle/reset_stats

#cat /sys/class/misc/deepidle/idle_stats

idle state total (average)

===================================================

IDLE 17775ms (3ms)

DEEP IDLE (TOP=ON) 0ms (0ms)

DEEP IDLE (TOP=OFF) 0ms (0ms)

#cat /sys/class/misc/deepidle/idle_stats

idle state total (average)

===================================================

IDLE 38272ms (2ms)

DEEP IDLE (TOP=ON) 0ms (0ms)

DEEP IDLE (TOP=OFF) 105779ms (5ms)

#
[Nexus S Android Development] akshayf:
Hey franco...just want to thank u for this awesome kernel...love it.

Btw, i'm totally a noob when it comes to the technical talk.....just had a question...do i really need to change some settings via adb as mentioned in some above posts or am i good to go after flashing ?
[Nexus S Android Development] nickmv:
I think you misunderstood his question. I think he's asking Ezeekel to confirm that keeping cpu freq at a MAXIMUM minimizes batt drain during screen-off, as you can see in Ezeekel's post:

"Keeping the frequency at a maximum while screen-off is the best way to minimize battery drain as long as two conditions are met. "

This logically makes no sense (higher freq = increased power draw....right?), so I believe he's asking about it. I'm curious too, now.

I think this whole deep idle and race to idle thing is a little over our heads for a lot of us, and isn't something we fully understand at all.
[Nexus S Android Development] DebauchedSloth:
The faster frequency should allow your CPU to finish everything it has to do. Once it has done that, it can go IDLE and draw very, very little power. So you are trading less time at a higher frequency for more time with the CPU effectively off.

It's called race to idle. The CPU races to get to an idle state.

If you are at a lower frequency, it spends more time doing stuff and may never get to idle.

Make sense?
[Nexus S Android Development] nickmv:
OK, I had a feeling that was the reasoning behind that, but I wanted to make sure.

That brings up another question I have though. When I'm playing music, with screen-off, how is this deep idle working? Are we assuming that music requires only 100mhz-worth of freq and power, or what? Is the CPU "racing" to max, and then back to idle constantly while I'm playing tunes?
[Nexus S Android Development] franciscofranco:
Yes I agree it's a little technical for some people..it's ok we are not born taught ;)

That pretty much sums it yes
[Nexus S Android Development] DebauchedSloth:
Yes, it is, if the app is well written and nothing else is going on - it's going straight back to idle. If your app is waking up so constantly it won't let the CPU get to IDLE, then it could be a problem.
[Nexus S Android Development] got2best:
I was wondering if the deep.idle stats are workimg now... because mine still says 0 on both but has a time on the idle one... is it working? :/

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] ellesshoo:
Franco, myself and another user were having an issue where LiveOC would lock in at a high frequency and never use any other stepping (screen on or off). This behavior didn't happen with matrix kernel. At least in my own case I've figured out, finally, what the issue was. I was pushing more voltage values than frequency steps are available in your kernel. I must have written my liveoc scripts while on matrix and had extra voltage values for his oc frequencies. Never occurred to me to delete extra ones when using your kernel (figured they would simply be unused). Anyway, no need to look into this issue further.
[Nexus S Android Development] got2best:
Was this post an answer to my question? .. sorry just a little confused.. and if it was how do I fix it?

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] coloxim:
i Think that franco hate me...

;(

I'm not a developper...and somethings are strnge!!
[Nexus S Android Development] Flying Fox:
Same here. "Deep Idle (Top On) : 0ms, Deep Idle (Top Off): 0ms though echo "1" ........./deepidle/enabled. Screen was off the whole time and USB disconnected.

What can be the reason for that? I´m running 11/2 and KelLMSKing MIUI 2.4.1
[Nexus S Android Development] Cybergr:
The results of Antutu and Quadrant seems really good..I have similar scores with Matr1x Kernel though..I will w8 a lil bit more for those BSODS and minor problems to be fixed and then i will stick with francos kernel too..!!
[Nexus S Android Development] jason62391:
The guys over at trinity kernel seem to have done it. You can tell by running quadrant and qatching the planet spin. It caps at 56. Fps
[Nexus S Android Development] Cybergr:
You mean 65 fps...not 56!!

Trinity is a really nice kernel and pretty fast for me and the only one i can have stable without reboots overclock..I can overclock up to 1440 Ghz and even 1500 Ghz with stock kernels voltages ..Too but though it doesn`t give u the ability to have a wide rage of overclock options!!
[Nexus S Android Development] orrorin:
I love this kernel! It is so quick I can downclock to 800mhz and still feel the speed. However, I get constant reboots.

I guess the challenge is how to fix the errors with all the debug utilities turned off :D
[Nexus S Android Development] franciscofranco:
I didn't know it's possible to increase the 56 fps limit to 65 fps. I know that deleting /lib/egl/libGlES_android.so makes it run with 56 fps, but not 65... Gotta research on that.

@orrorin

That seems more of a rom issue to me, I don't have any reboots and I have my phone undervolted.
[Nexus S Android Development] orrorin:
Hmm, I'll check it out
[Nexus S Android Development] brainmaster:
Kind a slow!

Here is mine @ 1 GHz:
[Nexus S Android Development] simms22:
in the trinity kernels(besides teuv) its about changing the screen refresh rate from 56Hz to 65Hz, there isnt a fps cap lifted. but you do see the fps increase to 65.
[Nexus S Android Development] franciscofranco:
Ok, thanks, that seems reasonable to me, I'll have a look into the files.
[Nexus S Android Development] franciscofranco:
Do you know which file I have to change? I'm still not very familiarized with this phone kernel files.
[Nexus S Android Development] simms22:
now that you would have to talk to morfic about. since he is such the helpful sharing individual, im sure that he would love to help you out :D
[Nexus S Android Development] franciscofranco:
Yes, I sent him an email. I've changed refresh values before but it was in other phones which use a different kernel structure, this Nexus ***** is a little different ;)
[Nexus S Android Development] simms22:
and thats the first step.. the day you realize that shes not really a ***** is the day you smile and realize what you actually have, something special :)
[Nexus S Android Development] morfic:
You senT me an email? Hope your kernel skills are better than your emailing skills. :P

mach-herring.c look for .freq, keep in mind that 60 comes out to 55.55Hz, so you got to have more than 65 to get that, be careful not to go too high, since we don't remove a cap but change things around on panel frequencies, things get ugly if you want more than the setup can handle.

Hope this helps.

Looks like the slcds return 65 as well, based on brainmaster's report, the 68 was a misreport then.
[Nexus S Android Development] brainmaster:
No they return 65. I'm on S-LCD and have 65 frame rate.
[Nexus S Android Development] morfic:
Then i got an incorrect report, thanks.

Ok, both report 65 then.
[Nexus S Android Development] franciscofranco:
Yes I sent an email :( I blame my mail app, or my internet connection, or my computer, it's always machine's fault :p

Thanks, I'll see what I can do!
[Nexus S Android Development] morfic:
you tried morfic AT gmail D0T com right?
[Nexus S Android Development] franciscofranco:
Yes, but np, **** happens.

Your change works fine, can render 65 fps now perfectly fine :)

Going to test this kernel a bit more before releasing an update, but should be out in some hours!
[Nexus S Android Development] morfic:
Here comes the funny math, keep in mind we still are vsync limited

so you can only sync every frame, every other frame, every third and so on.

So, in non demanding games, you will get a nice 65fps.

In mixed demand games you will get 65fps with 33fps mix, if it can reach say 57fps, not enough to sync at 65Hz, but enough to sync at 33Hz (or 65Hz at every other frame, whicever term you prefer).

So based on the games a 65fps or a 56fps kernel will be "better".

Just mentioning it since i considered releasing a 56fps version if enough popular titles indicated they didn't make the 65fps.

But so far the majority of feedback indicates 65fps == "smooth man"

EDIT: Demo, this distinction is for you and inspired by you.
[Nexus S Android Development] polobunny:
I remember reading about opening the cam then closing it, that could fix the problem. Don't take my word for it though, I have been out of the loop for a week. :P
[Nexus S Android Development] got2best:
One thing I an wondering is what's the difference in the stats... like can someone explain what top=on is and what top=off and things like that... I would really appreciate it! :)

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] Ezekeel:
Waking up from DEEP IDLE with TOP=OFF takes about 300µs and that is the only hard data I got. I guesstimated that the whole cycle should not take more than 1ms. Assuming that is correct with an average time of 5ms, the CPU actually spends only 4ms powered down, so it effectively only spends 80% of the time shown in DEEP IDLE. I dunno the exact limit when switching to DEEP IDLE is not efficient anymore, but based on the above ideas 5ms still sounded safe for me. I guess the only thing you can do is try it.
[Nexus S Android Development] Flying Fox:
Now I get values for "Deep Idle Top Off" (not for Top On"). Thx for helping.

I´m still not able getting results after changing liveoc_value in the init.d file. Changing "echo" to 120 has no affects to the frequencies.

Anyway I´m still not sure if it´s better to use 400/1000 freqmin/max or 480/960 after raising the bus-speed concerning performance and battery drain. ...maybe I can do without liveOC. Anyway I´m so corious....
[Nexus S Android Development] invd:
yep, same here, also same rom....

EDIT: after cam open/close DI TOP=OFF works (as it seems).

EDIT2: ok, my bad, did not see what TOP=ON is for:

"The DEEP IDLE with TOP=ON is used while GPS or BT are running." (Ezekeel)

Sorry!
[Nexus S Android Development] polobunny:
980 will be snappier as for battery drain it should be similar.
[Nexus S Android Development] Flying Fox:
But what can be the reason that changing the bus-speed to 120% in the init.d-skript does have no effect. --echo 120 > /sys/class/misc/liveoc/oc_value-- works fine but I´d like my settings keeping after reboot.

Is there anything else to think about after changing the init.d - file? Any ideas? Thx!!
[Nexus S Android Development] awcabdou:
Hello. Thank you for this work. I want to ask you about the compatibility of this kernel with the new ICS SDK 14 Port. Can i install it with this version?
[Nexus S Android Development] Tzorg:
This has done it for me. Running 2/11 and doing the trick gives me finally some deep idle time with screen off, will have to wait and see for the screen on one. Thanks Ezekeel for your great mods!

IDLE 675987ms (1ms)

DEEP IDLE (TOP=ON) 0ms (0ms)

DEEP IDLE (TOP=OFF) 1337108ms (52ms)

Great kernel Francisco, it's the smoothest I've ever run and also got better Quadrant scores than any other one I tried at the same frequency at least with 1/11, hopefully CFS won't have a major impact, will be testing soon :)

Thanks!
[Nexus S Android Development] ragnarokx:
I had a freeze opening the camera and a random reboot today on the latest kernel. BM MIUI, UV -20mV across the board, no overclock. Never had a single problem on 10/27 kernel.

Sent from my Google Nexus S
[Nexus S Android Development] beetlo:
Yep definitely works just fine with the 4g. Going to Deep Idle without issue after cycling the camera app. The battery use line is practically flat now. :)
[Nexus S Android Development] Tzorg:
Not bad, got the following on the 4th test, didn't even bother to force 1000-1000 and run it 400-1000 :D
[Nexus S Android Development] kalinusa:
I am gonna post some screenshots in an hour or so but I can tell you that my CPU is stuck on 1000mhz and NOTHING running. I noticed this the other day because it only occurs when I am on the work WiFi

Home:

Radio OFF

Wifi: ON

nothing running battery is FLAT line and awesome

at Work:

Radio OFF

WiFi: ON, right next to the AP

nothing running, battery is like a steep ski slope in 3-4hours will be dead.

This has been happening for 3-4 days now.

Will try to reboot to see if it helps.

anybody seeing this?
[Nexus S Android Development] FL0OD:
Am I the only one that noticed from his pics that he was running matr1x's kernel?

Sent from my neXus s 4g
[Nexus S Android Development] franciscofranco:
Nop, that's why I didn't answer, I'm not a tech support guy ;)
[Nexus S Android Development] SA-07:
Hahaha franco ;)
[Nexus S Android Development] frenccw:
Does the update add any fixes to stability? I'm still on 27 OCT. If the Ezekeel bug fixes are just battery related i can live with that because they seem fine to me. I've been flashing too much the past week i need a rest lol ;)
[Nexus S Android Development] Lalaca:
Lies. There can never be enough flashing. :P
[Nexus S Android Development] Yusei:
Francisco, tell me plz . What rom are you using?
[Nexus S Android Development] al_madd:
oxygen......:rolleyes:
[Nexus S Android Development] Cybergr:
He is using Oxygen 2.3..
[Nexus S Android Development] Yusei:
thx dude

that rom, exists here in XDA?
[Nexus S Android Development] Cybergr:
If u need it, u can grab it from here:

http://xdaforums.com/showthread.php?t=1285243
[Nexus S Android Development] FL0OD:
This kernel and Oxygen has always rocked ;)

Sent from my neXus s 4g
[Nexus S Android Development] caleb1783:
hey flying fox...

i have ezekeel's mods in one file on my blog...

cant attach here so check it out...

http://caleb1783.tistory.com/218
[Nexus S Android Development] got2best:
I am wondering if anyone van explain what TOP=ON/off is... and if it is working for me.. here is a screenshot of my stats.

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] sixstringsg:
TOP=ON is if Bluetooth/GPS are connected if I'm not mistaken. TOP=OFF is for when they are not.
[Nexus S Android Development] FL0OD:
I'm not smart enough to understand all the technical stuff so my description here is going to be very basic. I noticed after flashing the 02 kernel that my connection and data speeds seemed to have gone down. I flashed back to 01 and I am back running fast again. Again I don't know what may have caused that but I did notice a considerable difference flashing back. Just a observation. I would like to say that overall this kernel just gets better and better in every update. I appreciate all your hard work.

Sent from my neXus s 4g
[Nexus S Android Development] franciscofranco:
Thanks for the report. Can you tell me your rom?
[Nexus S Android Development] doc_v15:
Hello there, I just opened this thread and a bit shocked that the BFS has been replaced by CFS :(

Just my opinion, BFS have been working (24hrs) greatly in my phone using MIUI rom by KelsmKing 2.4.1..Its smoothness like never before! Probably Im gonna keep this BFS kernel for a while until (if franco's will) franco released another BFS kernle in the future.

Thanks franco, you rock!