yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sishgupta:
Dynamic hotplug seems stable for me. I tested it and it is working and its not like crazy erratic or anything.

I did notice on #16 that this morning the kernel wakelock mipi_link kept my phone awake for 25 mintues of the 70 minutes its been on. So my phone has just chugged through 9% battery life where as yesterday on my train ride I was still at 100%.

Only thing diff this morning is I left developer mode on?
[Samsung Galaxy Nexus] poopooface:
I know this is now out of date because you've released 16, but I am noticing on test4 that sometimes it would go all the way up to 1.35 on one processor but not activate the second. I will now upgrade to 16 and see if that still happens.
[Samsung Galaxy Nexus] dyndragon:
Franco, another SOD just now not on the charger. Not sure what's going on. What were the changes between test4 and nightly #16? I did not get any SODs with test4 all day yesterday, but two since I flashed #16 last night and put the phone on the charger.
[Samsung Galaxy Nexus] poopooface:
Hmmm... So I updated to 16 and for some reason I seem to have lost the dynamic hotplug entirely. Both processors stay on at 700 no matter what. Screenshot is attached.
[Samsung Galaxy Nexus] franciscofranco:
Well maybe your device doesn't like the dynamic hotplug. Can you change to Gazelle and see if you get a SoD?

You have to enable dynamic hotplug =)
[Samsung Galaxy Nexus] ro_explorer:
System Tuner

And on-topic: Dynamic hotplug is working fine on my device .. but I can not tell yet if is providing observable battery saving.
[Samsung Galaxy Nexus] refaa:
Try again so iam on 4.0.2 and icant use this karnel is there an older version of this karnel that works with the 4.0.2???

Thanks
[Samsung Galaxy Nexus] joelteixeira:
Confirmed with system tuner here too. :-)
[Samsung Galaxy Nexus] rajones19:
No.

10 char
[Samsung Galaxy Nexus] meilstone:
#16 is working fine right now with dynamic hotplug. So the normal hotplug does not work anymore? Because its not mentioned in the OP. Or is it working on #16? Cause it was disabled in the test kernels
[Samsung Galaxy Nexus] nrgaway:
Correct, the upper limit
[Samsung Galaxy Nexus] poopooface:
OK, I will do that... Could you be so kind as to tell me how to enable this?

Thanks again for all of your work!
[Samsung Galaxy Nexus] meilstone:
Just make a init d script with the parameter mentioned in the OP. Or use his App.
[Samsung Galaxy Nexus] franciscofranco:
Hotplug mod works independently of the governors and only shuts down cpu1 on screen_off.

Dynamic hotplug is for francoTurtle only.

The explanation is in the OP.
[Samsung Galaxy Nexus] poopooface:
OK, could you tell me exactly what filename to make for the init.d script and tell me what folder to put this in? Thanks.
[Samsung Galaxy Nexus] meilstone:
So just to be clear: It wont have any conflict as far as we know?

For Script:

#!/system/bin/sh
echo 1 > /sys/module/cpufreq_franco_turtle/parameters/dynamic_hotplug

I named the file 00hotplugdynamic

It has no file extension. I've also deleted the placeholder script and now it is working fine.

The script should be placed in:

/system/etc/init.d

Be careful with the permissions. Set them like the same way like on the other files in this folder.
[Samsung Galaxy Nexus] poopooface:
OK, so I made a file called "00hotplugdynamic" with no extension, just like yours, placed it in /system/etc/init.d with the same permissions as all the other files in the directory. I also renamed it "50hotplugdynamic" just so there would be no possible conflict between that and the other thing that was prefixed "00". The file consists of only the following text:

#!/system/bin/sh

echo 1 > /sys/module/cpufreq_franco_turtle/parameters/dynamic_hotplug

Yet it still doesn't switch CPU 1 off, ever. When I go and manually change the value of /sys/module/cpufreq_franco_turtle/parameters/dynamic_hotplug to 1, it does switch the second CPU off dynamically until restart.

Could there be anything I'm missing here? And what was the "placeholder script" you were referring to?
[Samsung Galaxy Nexus] meilstone:
Well there was a placeholder script in my folder. Did you reboot after making the script?
[Samsung Galaxy Nexus] poopooface:
I removed "#!/system/bin/sh" from the file, and left myself with a file consisting of ONLY "echo 1 > /sys/module/cpufreq_franco_turtle/parameters/dynamic_hotplug".

It worked! SUCCESS!!!1 Awesome!!!

Thanks for the help, guys.
[Samsung Galaxy Nexus] dyndragon:
I will reflash and try gazelle. Any ideas on the difference between test4 and #16? test4 has actually been running very well for me, presumably with dynamic hotplug turned on.
[Samsung Galaxy Nexus] atsavlis:
Well guys here are my results so far....

I am a moderate/heavy user, mostly calls, whatsapp, browsing, youtube, facebook....

14 hours are on the test v4, and 7 are on v6. Almost 3 hours screen on time, and this is coming from a fresh install rom/kernel and first full charge, so battery still has to "settle".

Wifi is always on including sync with my gmail and whatsapp and I don't switch to flight mode at night... Currently running 700-1000 franco_turtle with dynamic hotplug on.

Hopefully the devs will be able to port 4.0.4 from the CDMA over to our GSM, as reports show major reduction in Android OS awake time.
[Samsung Galaxy Nexus] apratomo:
testing #16, got great battery life on test4. Anyway some comments, why there's no progress bar when downloading kernel? Lastly, I just installed system tuner to see cpu1 online/offline, I noticed it was quite erratic, is there any performance hit if you switch on/off too rapidly? Is there any context switching involved?
[Samsung Galaxy Nexus] franciscofranco:
I only changed the timer that takes care of doing the checks for the dynamic hotplug. Now its way less intrusive on the system. This is a work in progress, the more feedback I get the better I can work on the function itself.

Looks pretty good to me.

In the latest app update there is a dialog when the user clicks to download the kernel. Thats what I'm still trying to find out. I'm pretty sure some context switching is involved, thats why this is still pretty experimental and I'm waiting to see if this dynamic hotplug brings benefits or not, thats where the users feedback come into play.
[Samsung Galaxy Nexus] jhericurls:
I had SOD for the first time last night after flashing test 4. I set the CPU range to 350Mhz - 1000Mhz (Turtle)

I'm right in thinking that 350MHz is not stable and minimum frequency should be 700MHz?
[Samsung Galaxy Nexus] atsavlis:
Franco, why does nfc still register as a kernel wakelock, even tho I have nfc switched off?? I got it showing about 3 minutes in total wakelock :cool:
[Samsung Galaxy Nexus] franciscofranco:
I don't recommend at all 350mhz with dynamic hotplug, and I strongly advise you to flash #16 too.

How would I know, I haven't touched any nfc ****, hell here in Portugal we don't use NFC at all, I always have it disabled :p
[Samsung Galaxy Nexus] Nebucatnetzer:
So I experienced no major issue with dynamic hotplug.

One thing which I noticed like the other guy is that I'm getting an SoD when I'm using the 350MHz frequency this happend as well on the normal hotplug mode. I haven't tested it on test4 and #16 since they came too quickly for me. I will test it now with #16.

However when I'm running it at 700MHz everything is fine and stable.
[Samsung Galaxy Nexus] sishgupta:
My guess is the thing that is toggled off in the options is the NFC service.

NFC is still integrated into the kernel. As for why it is wakelocking? That I don't know.

Maybe it is polling for the wakelock service, not finding it, and then polling again X interval.
[Samsung Galaxy Nexus] nikulogical:
bump. I know the answers to the first and third. Also what's the difference between 1000 and 1200 in terms of performance and battery life?
[Samsung Galaxy Nexus] StuMcBill:
I seem to be having issues with Dynamic Hotplug and a couple of apps.

Words With Friends doesn't seem to like it, it freezes after you have made your move, once you skip the advert.

AOKP T9 dialer freezes with it too.

Reverting to Standard Hot plug solves it though.

Anyone else able to reproduce this?

Sent from my Amiga 500 using Workbench
[Samsung Galaxy Nexus] franciscofranco:
Ok about the antutu scores being low I just found out the issue. Somehow since francoTurtle is the default governor before the init.d script kicks in with the governor change to for example Ondemand, it shuts down cpu1, and it will be a single-core unless echo 1 > /sys/devices/system/cpu/cpu1/online is typed in. Thanks for the bug report, this will be corrected in #16.1.
[Samsung Galaxy Nexus] danielvc:
works fine here with dynamic hot plug
[Samsung Galaxy Nexus] poopooface:
OK, now that I have dynamic hotplug going, I am checking out the CPU usage... It seems to be periodically (like every few seconds) bumping up to 1000, then relaxing back to 700 and cutting out the 2nd processor. I remember that it did this a lot less in the previous test kernels. Can anyone tell me if these CPU loads and periodic blips to 1000 are normal? I am not running any apps other than system tuner pro.
[Samsung Galaxy Nexus] Felixpau86:
Quick question could I and should I use both hot plug mods?
[Samsung Galaxy Nexus] franciscofranco:
No. I guess I'll have to write that in the OP. I don't see how is it hard to read both mods descriptions and see that they shouldn't run together at all =(
[Samsung Galaxy Nexus] nic85:
what app is that in first screen?
[Samsung Galaxy Nexus] franciscofranco:
Erroneous ram used by apps reporting was just fixed, this was causing it:

https://github.com/torvalds/linux/commit/e268337dfe26dfc7efd422a804dbb27977a3cccc#fs/proc/base.c

I changed to fugumod's kernel implementation that fixes the security hole and doesn't **** up Android's ram reporting. Coming also for #16.1.
[Samsung Galaxy Nexus] king23adrianc:
awesome! :p
[Samsung Galaxy Nexus] Redflea:
Having an odd problem...when on wifi on 16 I'm not getting connected to google services...wifi never goes blue, except once briefly. On 3g/4g don't have this issue.

Flashed back to 15.2, and the issue appears to go away, connects up to wifi and google services w/out issues, and things are good again.

Running CM9 Kang ROM (CDMA) from Winner00, 4.0.4 gapps, 4.0.4 props are in ROM, default Franco kernel settings in both cases (15.2 and 16).

Any suggestions, or anyone seen this issue on their setup?
[Samsung Galaxy Nexus] crecsky:
I was having this problem on 15.2 and now on 16 it's fixed. Sorry that my comment doesn't help you but I tried a multitude of things and they didn't help me.
[Samsung Galaxy Nexus] refaa:
6957 how did u get it mine only 4 something
[Samsung Galaxy Nexus] refaa:
And wich rom are you useing???

Thanks
[Samsung Galaxy Nexus] dyndragon:
Been running on 700/1000 francogazelle with hotplug mod (not dynamic) and no sleep of deaths for about 4 hours now. Previously I was SODing within an hour.

Well, probably not much difference between turtle and gazelle right? heh
[Samsung Galaxy Nexus] qvert:
can you give us the UV settings you used in the last version? so that we can set them by ourself?
[Samsung Galaxy Nexus] Tubes6al4v:
1) You can create a script that runs at boot to turn either hotplug on. But seriously, Franco is doing some very cool stuff here. He priced the app at 1 euro to make it relatively 0, but still have us show support for his work. Please just buy the app. It is improving as well!

2) I'd just stick with Franco's preset levels.

3) If you would like less lag, go to FrancoGazelle, but don't expect the same battery as turtle.

4) Yes, lower levels will hinder graphics, but keep in mind what the stock values are, don't just jump to the highest clock expecting the best stability and performance.

5) Turtle comes preset at 1k because it has minimal impact on performance for most people, but a good increase in battery settings. Keep in mind that games are going to be the most intensive for the device, hence where you might experience the performance hit going down from 1200 to 1000

I am running 16 fine with AOKP milestone 3. In your case, there may be some conflicts:

- This is the GSM dev section, you might have downloaded the wrong one for your CDMA version.

- As we do not have 4.0.4 yet, I am not sure if this kernel is compatible
[Samsung Galaxy Nexus] franciscofranco:
It's stock like it comes from TI/Samsung/Google/whatever, open SetCPU or my app and see.

Hoping to see this fixed in #16.1 later today.
[Samsung Galaxy Nexus] loudaccord:
I'm on 16 and can't say that AnTuTu is slow at all. I have dynamic hotplug enabled and I'm getting almost 7000. This is on Turtle.
[Samsung Galaxy Nexus] qsec:
Paul O'brien did a 4.0.4 for GSM and this kernel works on it.

http://android.modaco.com/topic/351...rom-for-the-galaxy-nexus-development-kitchen/
[Samsung Galaxy Nexus] nikulogical:
Thanks for the response. I'm currently trying francogazelle 700/1200 but the battery drain seems to be too high. I guess I'll try turtle 700/1200 and gazelle 700/1000 to find the best medium for performance and battery.
[Samsung Galaxy Nexus] franciscofranco:
Yes, but if you're using turtle + dynamic hotplug then change to, for example, ondemand, most likely cpu1 will be offline and since that governor doesn't have a way to online cpu1 back up you'll be stuck as a single-core unless you online cpu1 back manually. This is fixed in #16.1 as it will come with francoGazelle by default and unless people change to francoTurtle cpu1 will always be online.
[Samsung Galaxy Nexus] Redflea:
Thanks...I'm here 'cause this is where the best discussion of Franco's kernel is...I'm aware I'm in GSM land, but the kernel runs on both GSM/CDMA, and I get my ROM from the CDMA section on Rootz.

The ROM I'm running isn't 4.0.4...it's still 4.0.3, just with 4.0.4 prop files.

Great, thanks, Franco. Appreciate your response and the kernel, of course. :)
[Samsung Galaxy Nexus] qvert:
i know that it is stock now, but it wasn't stock before and it worked fine for me with the UV values before, so maybe you can tell us the old values so that i can keep using them on the new version
[Samsung Galaxy Nexus] loudaccord:
I get it now... brilliant!
[Samsung Galaxy Nexus] MarcLandis:
The previous version had roughly 87% of the stock voltage

Marc
[Samsung Galaxy Nexus] Tubes6al4v:
I've added a bunch of info from this thread and other sources to the XDA Wiki about Franco's kernel. Lets build it more so people don't have to dig through the 300 pages for answers:

http://xdaforums.com/wiki/Samsung_Galaxy_Nexus/GT-I9250/ROMs/FrancoKernel
[Samsung Galaxy Nexus] qsec:
Nice work.

Add a big bold faq: Does this work on 4.0.1, 4.0.2?
[Samsung Galaxy Nexus] oli20021978:
Lol

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] trixnrice:
flashed 16 last night, charged phone to 100%, then took it off the charger. woke up to an SOD this morning. running standard turtle, 15.2 stock voltages, dynamic hotplug enabled, hotplug disabled. battery stats showed deep sleep looking fine until apparently sod occurred. 3 hours later battery went from 96% to 31% (after rebooting). I will try using gazelle (dynamic hotplug disabled) as franco has suggested to see if my phone just doesn't do well with dhp enabled. just thought i'd share my finding, although i'm not too concerned.
[Samsung Galaxy Nexus] Felixpau86:
Anyone have an issue where with the new hot plug that their widgets aren't updating anymore?
[Samsung Galaxy Nexus] laserprom:
Which battery test is better 15.2 or 16?
[Samsung Galaxy Nexus] Redflea:
Franco:

Can you add a confirmation prompt to the Kernel Auto Flash option in your app? I autoflashed last night unintentionally when I hit that option accidentally...be very helpful for those of us with fat/clumsy fingers. :)
[Samsung Galaxy Nexus] mikeandjaimie:
Okay so I don't have the app yet, but plan ok buying it soon.. Right now I use setcpu with profiles.. 700/1200 turtle for screen off & <50%, then gazelle 700/1350 for default and charging.. I don't have the mod or script installed... When I buy the app and enable option, will the profiles mess up turning on/off cpu1? Or will it be fine cause I'm only switching between your governors?
[Samsung Galaxy Nexus] ArmanUV:
Can someone explain what the deal is with UV?

Now that voltages are set to stock do I need to UV manually if I want #15 voltages back?
[Samsung Galaxy Nexus] Tubes6al4v:
Yes, you need to use Franco app, set cpu, etc to adjust the voltages manually. Franco set them back to stock to get the best stability across a wide range of phones (not all Gnexes are created equal).
[Samsung Galaxy Nexus] akalias1981:
I'm not sure if this is a kernel issue but hopefully even if not one of the smart people in here can help. I'm running AOKP M3 with Franco 16 and barely used my phone today and had great idle battery having lost about 7% in about 10 hours. So far so good. Then I started to use Tapatalk and put in about 30 minutes of screen time to use another 8% of battery. Still happy. At this point I'm at 85% left and I exit and kill Tapatalk and turn the screen off. Less than an hour later I turn the screen back on and I've lost another 2%. This is way out of line with the idle drain I had most of the day. What causes this and how do I avoid it? Hopefully you can make out the steeper incline on the idle section between the last two screen on periods. Thanks for any help. If this isn't a kernel thing, apologies for going OT.
[Samsung Galaxy Nexus] refaa:
Where do u get turtle?? From the app???
[Samsung Galaxy Nexus] trixnrice:
also worth mentioning...cpu spy shows me using 7% (~6 minutes out of an 1.5 hours) of the 350Mhz. i have the min freq. set to 700 (standard turtle govenor). i've triple checked 3 times through franco app and set cpu. dynamic hot plut still enabled. very peculiar....anybody have any insight?

---------- Post added at 01:22 PM ---------- Previous post was at 01:20 PM ----------

turtle is the governor setting. its default on version 16 of francos kernel. u can set the governor with his app or set cpu.
[Samsung Galaxy Nexus] refaa:
How do i set it then got set cpu?? Cuz iam getting 4 something not hitting the 6 or 700 like the others
[Samsung Galaxy Nexus] Felixpau86:
16 is killing my battery compared to 15.2... I went back till I can figure how to configure 16 to behave
[Samsung Galaxy Nexus] loudaccord:
if you want a fairly high AnTuTu benchmark, make sure your phone is nice and cool, then make sure no other apps are running... your RAM is literally 1/2 of what mine was.
[Samsung Galaxy Nexus] DaF1974:
Why not make it impossible to tick both boxes at the same time? Show a message that only one can be ticked as soon as the second is ticked.
[Samsung Galaxy Nexus] trixnrice:
go the the "main" tab on the top left there. below the min/max freq will show the governor setting, just press and find franco turtle.
[Samsung Galaxy Nexus] refaa:
This is what i got when i used gazelle
[Samsung Galaxy Nexus] refaa:
Yeah did that too
[Samsung Galaxy Nexus] loudaccord:
reboot then do the benchmark again.
[Samsung Galaxy Nexus] alec534:
Franco, do you see any downside to running Francoturtle at 350-700max and hotplug mod? It seems to be spending 60-70% of the time at 350. Do you think 700-1000 will still be better on battery? I'm testing it myself but would appreciate your opinion.
[Samsung Galaxy Nexus] pmicho:
HI Franco,

With 16, Francoturtle and dynamic hotplug, I get insane battery life. After 10 hours and little use (40 minutes screen on) I still have 80% juice left. I'm on AOSP Milestone 3

Can this get any better? I dont think so.

Thanks man. Much appreciated work.
[Samsung Galaxy Nexus] vitalero:
The ColorControl in the OP is for the 16 or the 15.2 version?
[Samsung Galaxy Nexus] nic85:
I have Better battery life with 15.2

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] MarcLandis:
There have been several reports of crashes while running francoTurtle at 350. The recommended minimum is 700.

Marc
[Samsung Galaxy Nexus] MarcLandis:
Both

Marc
[Samsung Galaxy Nexus] alec534:
I've had no crashes. A bit of lag but it's been minimal. I'll run down the battery tomorrow at 700-1000 and see if it's any better.
[Samsung Galaxy Nexus] crecsky:
Can someone explain how 700 would use less power than 350? Because it doesn't take as much effort to get going again or something?
[Samsung Galaxy Nexus] viskas:
I can't get a fix on gps with AOKP Milestone 3 and Franco 15.2.

is it kernel related?
[Samsung Galaxy Nexus] gn00my:
Yes and running arhd 1.3.2
[Samsung Galaxy Nexus] franciscofranco:
Are you with the GN with USB plugged in? If so, that's absolutely normal.
[Samsung Galaxy Nexus] mike1986.:
@franciscofranco can u please consider using my boot.img as a base for your zImage? It's not much different from stock one, one of the main difference is that it has execution line for my script with all my tweaks in the ROM. With your boot.img this is gone. That wont do any difference for users using other ROMs, but will make a huge one for those using mine :) I will really appreciated it, if you wish I explain this better via pm or irc. Thanks!
[Samsung Galaxy Nexus] gn00my:
Ok, good to know, thanks for the info. Will see how it runs tommorow under normal use.
[Samsung Galaxy Nexus] galinha:
Dear ALL

Why cant i mount USB storage ?

i got an error to :

e:can´t open /cache/recovery/log

Thnks
[Samsung Galaxy Nexus] asko1981:
Changelog:

11th December

* Around 10/15 Power Management patches from the Linux Mainline

* USB HOST disabled as it was the cause of battery drain - more research when I have the device

* Few reverts to make sure the graphic glitch was fixed
[Samsung Galaxy Nexus] samuaz:
OFFTOPIC/

apology for the offtopic, the nexus one need a kernel developer to achieve operating the hardware acceleration, can You help please, Texasice could provide you with the source and others, thank you very much

This its the topic

http://xdaforums.com/showthread.php?t=1366897&page=42

Thanks

/OFFTOPIC
[Samsung Galaxy Nexus] The Gingerbread Man:
Would love to see this as arhd and this kernal seem to run great as it is. I second mikes request!
[Samsung Galaxy Nexus] franciscofranco:
We already spoke and the tweaks that mike enabled I already have them on my kernel source =)
[Samsung Galaxy Nexus] stickjohnonaah:
Do you have anything your working on for lte now that mike has a working kernel?
[Samsung Galaxy Nexus] minooch:
Firstly,

Thanks Francisco, the kernel is fantastic! & you're doing a fantastic job trying to make the best kernel without even having the phone - Cheers

Leading on from above - Francisco is only 86 Euro short of being able to buy a Galaxy Nexus - This is a simple request to donate a little, that way he can make even more progress!

So please my fellow XDAers ;) dig deep & give a little, he really does deserve it for all his hard work.

Cheers,

Minooch
[Samsung Galaxy Nexus] P530Cobra:
Hi, Francis.

Could you include the nls_utf8 option?
[Samsung Galaxy Nexus] dwang:
Doesn't look like the graphic glitches are fixed. I just started experiencing them with the OC kernel.

Will try the non OC version and see if it goes away.
[Samsung Galaxy Nexus] fdxgnd:
I've been on the oc kernel almost nonstop since posted today. Not a single glitch so far.
[Samsung Galaxy Nexus] dwang:
I wasn't having problems for a while either then all of sudden I got the glitches.
[Samsung Galaxy Nexus] beekay201:
Galaxy nexus costs 500€ on vodafone here in Portugal, afaik.
[Samsung Galaxy Nexus] minooch:
he's not only relying on donations - spending some himself
[Samsung Galaxy Nexus] beekay201:
Wasn't aware, I'm sorry. :D

Reached out to him, let's see if he complies (don't have paypal, so I'd rather money transfer). :)
[Samsung Galaxy Nexus] Dmw017:
Anyone notice an improvement in battery yet?

I got 6 hours on battery with 3hrs of screen on and 3hrs of music playing, phone is at 15% atm. No es bueno.

Also, once while in the app drawer, I swear I saw the white text of a row of apps have a graphical glitch for a moment. That's about it though, but maybe the graphic bug is still lurking underneath somewhere lol (Im on non-OC kernel)
[Samsung Galaxy Nexus] GchildT:
Same Here.
[Samsung Galaxy Nexus] Redflea:
GPS problems have mostly been ROM issues in the past for me.