yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] psycho2097:
check idling. that hotplug is useful only for below 20% load. above 20% , both cpu's kick in. so, screen on and idle.
[Samsung Galaxy Nexus] franciscofranco:
No:

If the frequency is = minimum frequency = cpu0 is online / cpu1 offline

If the frequency is > minimum frequency = cpu0 is online / cpu1 online
[Samsung Galaxy Nexus] king23adrianc:
so hotplug mod should turn off even though sometimes when screen off, cpu might be above people desire minimum frequency?
[Samsung Galaxy Nexus] psycho2097:
oops, my bad. so, in this case, did you confirm that it is working correctly, or as i observed, cpu0 gets kinda kinda unstable and keeps on jumping between frequencies?
[Samsung Galaxy Nexus] franciscofranco:
Yes. Currently this is just a test and only works with turtle governor. I still don't know the cost of onlining/offlining a cpu1 so often

The dynamic hotplug is working correctly, but I need to code a timer so it checks for the frequency change every X ms instead of checking it every damn time, and that costing a bit at the moment. I'm taking the day off from Android today so this is all just theory that I will turn into practical code tomorrow, thats why I released a testing version today, to get feedback =)
[Samsung Galaxy Nexus] loudaccord:
I think it's a hoax and this is actually the stock kernel just to hear people say that battery sucks, reboots, freezes then kills kittens.

:P
[Samsung Galaxy Nexus] psycho2097:
nice....its all well and good then! njoy the evening! go get wasted..! m doing the same after i get off in 3 hrs. day long meeting with french guys really wore me off today.

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

no its not, i tested, cpu1 does go offline.
[Samsung Galaxy Nexus] atsavlis:
Running the test kernel for the past 20 minutes. Everything was running fine and smooth, with only one problem. Received a phone call, and at the end of the call got a SOD. Had to pull the battery...

So far, CPU is running at Deep sleep - 65% 700 - 21% 1000 - 16%

Hope this helps...
[Samsung Galaxy Nexus] franciscofranco:
Ahah this time it ain't... ;)

Are you undervolting? I already done around 10 calls and no problems =(
[Samsung Galaxy Nexus] atsavlis:
Nope, I never undervolt, I always run your kernels as you recomend...
[Samsung Galaxy Nexus] Nebucatnetzer:
+1 on this. I didn't touched anything related to kernel settings I'm testing the kernel not my own settings ;).
[Samsung Galaxy Nexus] poopooface:
GummyNex 0.7.0, Franco 15.2

I actually confirmed with Battery Monitor Widget Pro that not only is the % display going up, but the mV values are going up too.

If it's a simple matter of the software "learning" about the battery capacity, why would the measured mV values be going up instead of down without charging?

Full disclosure: I'm using the 3600mAh HongDa Power chinese battery on like its 4th charge.
[Samsung Galaxy Nexus] Vangelis13:
Ooopsi. Phone was on idle & went SOD. Had to pull battery.. :-\
[Samsung Galaxy Nexus] carloshdez:
Testing the last build, overclock at 1350Mhz

So far, I've had 1 issue, the terminal blocked and had to pull the battery for reboot.

Battery meterings are strange, level goes up without any reason (it 'recharges' itself :confused:)

I'll keep on testing!

Obrigado
[Samsung Galaxy Nexus] Nebucatnetzer:
So this time I caught this little bastard.

kmsg attached. It's quite big since I don't know which part is relevant for you.
[Samsung Galaxy Nexus] ARod111:
Any idea of when the "Running Apps" data will give the proper information regarding how much memory a running app is using? Ever since 14.2 that is broken. It's been driving me nuts! Please fix!
[Samsung Galaxy Nexus] franciscofranco:
Users with SoD's on the test versions have you turned off hotplug mod?

[ 295.509002] L3 CUSTOM SRESP error with SOURCE:L4CFG info=0x84

[ 295.509185] ------------[ cut here ]------------

[ 295.509185] WARNING: at arch/arm/mach-omap2/omap_l3_noc.c:130 0xc007a69c()

[ 295.509185] L3 custom sresp error

Yes, big **** there, I wonder what is it, but I'll check. Thanks for the kmsg :D
[Samsung Galaxy Nexus] atsavlis:
Yup, I removed my init.d script before flashing the test kernel. On a positive note, this is the first time my phone has dropped to 2mA drain in 10 minutes... Keeping a close eye on it, and will post battery stats.
[Samsung Galaxy Nexus] franciscofranco:
That's pretty cool! If you get another SoD maybe try to give it a little more voltage..it's just a wild guess, but the error I've seen in the kmsg wasn't pretty, maybe it's onlining/offlining to frequently =)
[Samsung Galaxy Nexus] psycho2097:
i did turn off hotplug b4 flashing. also, i din stay long enuf to test ma drain over an hour or so. i reverted to 14.4 . i will try tonight.
[Samsung Galaxy Nexus] Vangelis13:
Yep, off. I can't get tge kmsg for some odd reason, root explorer is forde closing as soon as I try to open the kmsg file..
[Samsung Galaxy Nexus] loudaccord:
This is a crazy question, but through the kernel, can I disable 1/2 of my screen? The reason I ask is because 80% of the time I turn my screen on is to look to see what my notification is... usually an email that I just want to ignore. I'd be happy if only the top half of my screen turned on for me to ignore the email then go back off. This would prob have to be done in the ROM though.
[Samsung Galaxy Nexus] franciscofranco:
What? No offense, but that's a pretty stupid idea =( it would probably do more harm to shut half the screen than just turn it on/off to check the notifications ;)

By the way I couldn't resist and I uploaded another version of the test kernel, now it turns cpu1 online/offline much more accurately =)
[Samsung Galaxy Nexus] ARod111:
Love your work franco, but any idea when this is getting fixed?
[Samsung Galaxy Nexus] Vangelis13:
Same link?
[Samsung Galaxy Nexus] franciscofranco:
I don't know what the **** caused that, since it doesn't break anything I'm not really trying to fix it =(

Yes.
[Samsung Galaxy Nexus] atsavlis:
Same link for the last test version?? As for increasing the voltage, should I do that for 700, or for the whole governor range?
[Samsung Galaxy Nexus] ARod111:
If it doesn't report data properly it sure seems broken to me. Other than that the kernel is great, and I appreciate your work. I even bought your kernel updater app from the market. It would just be nice to see how much RAM a particular app is using. I do realize that the OS still runs great, but I like seeing how much resources a particular app uses.
[Samsung Galaxy Nexus] franciscofranco:
Same link. This one shouldn't crash.

Ok, I'll look at it tomorrow.
[Samsung Galaxy Nexus] Brandon3003:
Using the test kernel with turtle gov and 350 as minimum as well as undervolting quite a bit and assuming that CPU1 is shutting down, its running pretty smoothly. So far so good!
[Samsung Galaxy Nexus] poopooface:
FrancoTurtle 350/1350

I just installed the nightly test and it does seem to kill one CPU when my processor goes down to 350. At certain times, when it's on 700, both processors are on, but sometimes at 700 they are off. No noticeable performance hit. Bravo! I will get back to you with battery usage data.

I am curious as to why it's not recommended to go down to 350 or up to 1350? I put it on 700 minimum but couldn't discern any change in performance. And it hardly spends any time at the highest speeds anyway. Doesn't seem like it hurts to use 350/1350, and it might end up gaining speed and saving battery overall.
[Samsung Galaxy Nexus] ARod111:
Awesome, you are the man! =)
[Samsung Galaxy Nexus] jan-willem3:
I think omap should be able to handle that if I need to believe this:

http://www.ti.com/general/docs/wtbu...ateId=6123&navigationId=12846&contentId=53246
[Samsung Galaxy Nexus] atsavlis:
What app are you using to see which cpu's are online or offline?

---------- Post added at 10:58 PM ---------- Previous post was at 10:50 PM ----------

What app are you using to see which cpu's are online or offline?

EDIT - Figured it out...
[Samsung Galaxy Nexus] poopooface:
I am using System Tuner Pro's CPU screen. It is pretty handy at telling you when your CPUs are down.
[Samsung Galaxy Nexus] atsavlis:
As you can see, cpu1 is offline but, cpu0 is very erratic... Usage jumps up and down like crazy. 1, 22, 6, 15, 9, 18 etc....
[Samsung Galaxy Nexus] nikosrs4:
not really, is kinda different though.
[Samsung Galaxy Nexus] psycho2097:
Dude. .u gotta rest...take a night off!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joelteixeira:
Bro, just install Light Flow Lite and you won't need to turn on the screen at all to see what kind of notifications you have.

---------- Post added at 11:03 PM ---------- Previous post was at 10:51 PM ----------

Guys, I bought franco.Kernel Updater yesterday and flashed over a clean install of AOKP M3, if possible, I would like you to give me some info. I did check some pages and used the search this thread function without success.

1 - When I check "franco kernel boot animation" nothing changes, should I do something else to enable it?

2 - When changing between Turtle (battery) and Gazelle (performance) I need to manually change the Max CPU to 1000 or 1350 right?

3 - AOKP have one performance menu to set CPU specific settings, it's ok if I ignore it and use only franco app right?

Sorry if some questions are pretty stupid but I' m just arriving here. Thanks.
[Samsung Galaxy Nexus] psycho2097:
New test works perfectly. As far as 16 mins go lol ...:D

Screen was kept awake the whole time,on system tuner pro.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Nebucatnetzer:
1. No idea sorry I have my own in /local

2. Yes

3. Yes
[Samsung Galaxy Nexus] THE_KINGDOM:
hey guys so i stupidly installed this kernel on my stock ROM 4.0.1.. and phone wont boot, I can only get to my CWM Recovery menu.

so what can i do, i want to put a custom ROM but I dont see how i can connect to my phone at this point... any way to mount it as USB storage, and upload custom ROM, and then install so it will work with this kernel

any advice?
[Samsung Galaxy Nexus] Dr Byte:
Just a thought on turning cpu1 off/on

Perhaps it's easier to code with a simple relation such as "cpu > x%" but it occurs to me that if the phone is running only one thread at the time, starting up the second core isn't going to help performance, and may actually induce delays as the two cores interlock & prepare to share resources.

I haven't looked that deeply at the governors or schedulers' source (especially not with ICS) but on face value, the more relevant metric is not "cpu load" but how many processes/threads are "computable" but not running. ie, waiting for CPU.

My gut feeling says that if there has been at least one thread waiting for the CPU for a few scheduling quanta, another core should be wakened. If the active core hasn't been thrashing between threads for the last half second or so, there is probably no need to add another.

As a general rule, something like "if there has been a choice of two or more threads to run for the last "x" milliseconds AND the CPU load is non-trivial, fire up the second CPU.

Similarly, if there is no contention for the cores, there is no need to run two. So if there are less than three threads running AND neither is over 50%, shut it down.

This presupposes that a) shutting down and starting a core is "free," b) doesn't create any lag; and c) has some measurable benefit to current drain.

This is rather more involved to code, but if (c) is true, could have some benefits. However, we're already down in rounding-error territory... the CPU is one of the most efficient components in the entire phone. The power it drains is dwarfed by the display, radios etc... and only comes into bear when "inadequate" code keeps the phone awake and processing at inappropriate and unnecessary times.

Has anyone characterised the scheduler/governor activity on ICS yet? Do threads often run to the end of their quantum? If so, this could be an input into the decision process to wake the next core; if a thread runs to quantum with another thread waiting for CPU, that is an event towards "waking" - but if there is none waiting at the end, an event towards "shutting down".

In my naiveté, I had assumed that Google (or at least the Linux kernel) would already be doing something like this.

Submitted for consideration.
[Samsung Galaxy Nexus] ARod111:
So you rooted your phone but never installed a custom ROM? Flash stock fastboot images, re-root, this time install a 4.0.3 ROM before installing a custom 4.0.3 kernel.
[Samsung Galaxy Nexus] THE_KINGDOM:
yea because i didn't see a ROM worth putting yet until i recently looked over Kang Open Source which looks decent, and I thought that this kernel worked with all ROMs, didn't realize it was based on 4.0.3.. can i just do a wipe data/factory reset from CWM?
[Samsung Galaxy Nexus] ARod111:
Wait...isn't AOKP also based on 4.0.3. Just make sure you flash the ROM before the kernel!

---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------

NO, a factory reset will keep your kernel in tact, you my friend need to do a complete fastboot image restore.
[Samsung Galaxy Nexus] funkyblue04:
Excellent Work :)
[Samsung Galaxy Nexus] firepacket:
12 > 15.2

I updated to #15.2 from #12 and was sorely dissapointed!

On #15.2 my home screen swipes stutter. Nothing fixes it, I set the governor to default, gazelle, and interactive. I overclocked up to 1300mhz and still the homescreen swipes stutter.

When I flash back #12 the smooth iphone-like swiping comes right back.

What could be causing this? Is everyone so concerned about battery that they're willing to sacrifice interface lag?

Any help would be appreciated
[Samsung Galaxy Nexus] kfluk:
I've encounter tethering problem with 15.2.

GN won't route data after short idle. Have to disable and enable PC's Wi-Fi to reconnect to make it work again.

Using bigxie apex 1.0.2.

revert to kernel comes with apex without problem.

Anyone has que?
[Samsung Galaxy Nexus] chakra:
My tethering is working fine. I do pay for it if that makes a dif?
[Samsung Galaxy Nexus] psycho2097:
Dude, I just adore you now. I always loved your kernel,so fast so smooth,so many experimental features to try out. But I always got a bit of a ****ty battery life after 7.1, kind of like 25-30ma drain,20 in airplane at best. The best I had was on 13,when I lost 1% every hour @18ma on airplane. After 13 I went straight to 15 skipping 14.x altogether(finally did some work for a couple of days :D) 15 was like plain butter,as smooth as anything can possibly get. But ****ty battery again. Yet, I stayed...tried out lean,apex but just couldn't stay away from the smoooooooth f15.

Then today morning you introduced moi to the new test, and god almighty, I am getting 7-8 on data off and 13 on full sync,data,gps and wifi on! I never dreamed this would happen ...again. SNIFF..... You just made a crack flasher seriously consider giving up flashing! :) ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
There is no smooth problem in the latest kernels, in fact they seem to go smoother every release =(
[Samsung Galaxy Nexus] psycho2097:
c'est correct.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dhruvraj:
So does this kernel put a limit on app space to 2 gigs even though nexus doesn't have that limitation?

http://xdaforums.com/showthread.php?t=1478626
[Samsung Galaxy Nexus] franciscofranco:
What does that have to do with the kernel? Userland != kernelspace.
[Samsung Galaxy Nexus] kcokla:
Can someone teach me how to install this?

i did follow the tutorial but after it reboots its stuck on "google" and i have to take the battery out and do a recovery...

not sure what im doing wrong!
[Samsung Galaxy Nexus] opensourcefan:
^^ are you on a 4.0.3 rom?
[Samsung Galaxy Nexus] kin24173493:
The kernel updater is not working quite well in m3 rom. Always get fc or just a blank screen.
[Samsung Galaxy Nexus] Danny80y:
This it on the latest one the fix for graphical users. No OC stock profiles. Interactive Set with setcpu.
[Samsung Galaxy Nexus] DJTaurus:
Franco kernel without OC and only flashed 1.3.2 revolution with brightness patch.No cpu profiles.

Display at 35% (automatic unchecked just setted display at 35%)

No LWP.

No automatic synch

Same sleep mode battery drain when i was in stock kernel...
[Samsung Galaxy Nexus] Danny80y:
From this screenshot and the screen taking 50% looks like your sleep would have too be better than 1% per 15min??

Still this isn't what I had happen because mine drained 40% in 1 hour.....
[Samsung Galaxy Nexus] franciscofranco:
Thanks for the replies. In an hour I will release an update with around 10 power management patches from the linux mainline. Sorry for the battery drain, Im doing all I can.

One more thing can you guys go to setcpu and post me a screenshot of the used frequencies? Id like to see the graphic.
[Samsung Galaxy Nexus] DJTaurus:
Betterbatterystatus says that the problem comes from vbus-tuna_otg which is a usb host feature of francos kernel....franco can you check it out?
[Samsung Galaxy Nexus] DJTaurus:
You mean that?
[Samsung Galaxy Nexus] Danny80y:
Here are mine. I have reflashed it so going to see what happens.

My google talk is kappalubbock@gmail.com if there is anything else I can help with.
[Samsung Galaxy Nexus] DJTaurus:
I have same stats with @Danny80y ;)
[Samsung Galaxy Nexus] rabhw:
Same here. Except I leave "set on boot" unchecked.

Threw a donation your way too, hope you get the device soon :)
[Samsung Galaxy Nexus] dwang:
No battery drain issues during sleep here.

Took my gn off the charger at 9am at 100%. Came back at 9:40am, still at 100%.

Running the latest oc kernel at 1.2ghz with everything else at default.
[Samsung Galaxy Nexus] franciscofranco:
Thanks a lot for that finding. I'll see what I can do.
[Samsung Galaxy Nexus] franciscofranco:
Just invited you to chat on G+, those were not the screens that I wanted :)
[Samsung Galaxy Nexus] Shetlander:
If it is something to do with the USB host that has been added for flash drives etc then I personally would be happy for it to go as its not something I use at the benefit of battery longevity.
[Samsung Galaxy Nexus] franciscofranco:
That's something I'm going to find, and yes I do prefer battery > broken USB OSG functionality hands down.
[Samsung Galaxy Nexus] Dmw017:
Indeed... the usb host thing doesnt even work (except flash drives it seems... and even then....); id put that function on the back burner until you get your own device then fiddle with it to actually get it working. Until then, battery would be much appreciated :)

edit: oh nvm, thats alrdy been addressed above ..heh

Btw any word on when the next update is going to come, and is it going to eradicate the graphical bugs? :D
[Samsung Galaxy Nexus] franciscofranco:
Can you post me a screenshot of that please.
[Samsung Galaxy Nexus] Hayaku:
img.tapatalk.com/cfa44f03-f632-f116.jpg

(Can't post links yet)

Note the other high kernel locks too. Weird.
[Samsung Galaxy Nexus] franciscofranco:
Update coming in one hour.

We'll see a problem at a time :)

Following some other friend dev idea in another phone I'll post my daily Paypal status on the OP, because I believe in transparency and I don't want people that has donated to feel ripped off.
[Samsung Galaxy Nexus] stickjohnonaah:
You guys should set up a screen off profile in setcpu like the one below. That time in state ss is without profile engaged. With if engaged I have 75% time at 350mhz. Saves a lot on battery
[Samsung Galaxy Nexus] stickjohnonaah:
this is what it looks like overnight with profile engaged. Lost 8% over 6 hours. Usual was 21% over 6 hours. Of course this is on the stock kernel
[Samsung Galaxy Nexus] superbobup:
try reinstalling the app
[Samsung Galaxy Nexus] franciscofranco:
I just opened it and got no issues with Milestone 3. Get me a logcat, I can't work without seeing logs...
[Samsung Galaxy Nexus] dhruvraj:
OK Franco, what could it be? Rom? Something has to govern the use of space on my memory

It is 16 gigs gsm phone, shows 500 mb free (screenshots in link) but new apps can't install anymore. What prevents that installation and generates insufficient memory error?
[Samsung Galaxy Nexus] franciscofranco:
I dunno, definitely not kernel related, as far as I know the kernel doesn't control such things. Flash other kernels and see if the problem persist.
[Samsung Galaxy Nexus] kcokla:
Unfortunately not! on 4.0.2.

with Android Revolution HD 2.1.3

what do i have to do to get 4.0.3?
[Samsung Galaxy Nexus] franciscofranco:
Go to a topic with a tag [ROM] and a 4.0.3 in the thread name, download, flash, profit.
[Samsung Galaxy Nexus] opensourcefan:
If you can get to CWR then try and reflash your rom if it's there, if not you have to flash via a fastboot file. You need to study some more my friend otherwise worse things may happen.

---------- Post added at 11:02 PM ---------- Previous post was at 10:40 PM ----------

It's working fine for me as well, also on M3.
[Samsung Galaxy Nexus] chirea.mircea:
I get horrible battery life with Codename Android 1.2 and franco #15.2. This is with the phone doing absolutely nothing - I don't want to know what the battery life would be during moderate use. Turtle governor, 350 min, 1200 max, auto brightness w/ MID mod levels (but a screen on time of 10 min, so it doesn't matter).
[Samsung Galaxy Nexus] franciscofranco:
Define horrible. I see the phone with wifi on for 11 hours with a good bunch of long wakeups, I don't see a problem there.
[Samsung Galaxy Nexus] chirea.mircea:
On ARHD 2.1.4 w/ stock kernel It would drain about 7-8% during a 10-hour sleep, with WiFi on and no apps running. On CNA 1.2 w/ frank 15.2 I just got 15% drain during the same period. I don't know what the wakes are from - they don't show up in the stats, though it wasn't much different on ARHD either.
[Samsung Galaxy Nexus] franciscofranco:
Move to a proper 4.0.3 rom, flash this and do the same test, then come back to me.
[Samsung Galaxy Nexus] kecinzer:
Hi franco.

I have to apologize about battery drain. I tried other kernel and result is the same. So I think, that is something in my AOKP M3 installed. I have to do some research.

I'm sure, that AOKP doesn't do that.
[Samsung Galaxy Nexus] chirea.mircea:
Define proper. AOSP?

Sorry if I seem a bit angry, I'm half-asleep, just woke up.
[Samsung Galaxy Nexus] qsec:
I don't know if this had to I do with kernel at all. But if I call for example my voicemail with the phone to my ear and then take the phone away from my ear the screen lights up as I think should. Then when I press the button to get the dialpad it appears just fine, but when I press some digits to for example delete a voice message the screen flickers and goes on and off. This seems only to be like this if I had my phone to the ear so that the screen goes off once before.

Running 15.2 stock settings with Milestone 3 clean install.

I have never had this issue before. But like a said I don't know if this is even related to kernel.

Thanks for your awesome kernels.
[Samsung Galaxy Nexus] EddieN:
I'm not experiencing the same with AOKP M3 and franco 15.2. Try a wipe and reflash the rom/kernel and restore with TB.

Although what I HAVE been experiencing on ANY kernel/rom is stuttering/lag in the transition animation when opening/closing the app drawer. It's really annoying and God knows how many wipes I've done when reflashing roms /kernels etc.

Anyone else?
[Samsung Galaxy Nexus] franciscofranco:
No need to apologize anything. This just proves, once again, that 99,9% of the battery drain issues people report are caused by **** apps or rom bugs (or unless I really come here and say that I messed somewhere) ;)
[Samsung Galaxy Nexus] nrgaway:
Just try AOKP M3; its a great ROM. You will be happy with that one I'm sure.

The one you were using before was not really a 4.0.3 ROM; it was more of a hybrid. Most the other ones labeled 4.0.3 are properly 4.0.3 and not a mix of 4.0.2.
[Samsung Galaxy Nexus] chirea.mircea:
I flashed AOKP M3, restoring all apps now. How do you suggest I trace the wakelocks (if there are any) during sleep? I will see how the battery life is Sunday morning.