yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] johno168:
Try another kernel, or reflash M3 without any wipe to go back to stock m3 kernel.
[Samsung Galaxy Nexus] ArmanUV:
I have franco's app but problem is does not a set on boot option.

I know franco removed the option so people won't get stuck in a bootloop but why not apply the UV 3-4 minutes after boot so people would have the time to disable it if it causes problems?
[Samsung Galaxy Nexus] WillyWonka23:
My phone keeps rebooting after I sign into Google Voice. I'm on 16. It did this with 15.x as well.

Edit: Also upon reboot Nova Launcher is back to default and a lot of my apps are now not accessible. They won't open.
[Samsung Galaxy Nexus] enori:
I always get 4 hours screen time on wifi and 3 hours on cellular network with various kernels. However, on this on I get the best idle time and about half an hour more of screen time with dynamic hotplug. Thanks Franco!
[Samsung Galaxy Nexus] Helltoupee:
I have seen the NFC wake lock before so I did a few "tests" . I saw it on Francos so I flashed Imos Lean, rebooted and let the phone for a little over an hour and when I checked it there was a NFC wake lock so it is not the kernel directly waking the NFC function. I turned off NFC and rebooted didn't touch the phone for an hour and when I checked the NFC wake lock was once again there.

So I decided to go a little deeper. I went in to Tibu and froze Google Wallet and rebooted and waited. Once again the NFC wake lock was there. So next I froze the NFC apk in system/app, rebooted and waited. Again when I checked the NFC wake lock was there.

So now we can safely assume the wake lock is either not coming directly from the kernel or it is buried deep down in the kernel. Seeing as I know nothing about kernel development I could be completely wrong.

I guess the next logical step would be to ask Chimox or what ever BBS dev goes by and see if he has any insight. I have Googled the wake lock more than once and can't seem to find any info on it.

Finally, I don't know about your BBS numbers but my NFC wake locks seems to usually be under or around a dozen in a 12 hour period which really isn't a huge concern. On the other hand if your count is considerably higher it may be worth investigating more.

Any insight from Franco or any other dev would be greatly appreciated.
[Samsung Galaxy Nexus] djkinetic:
Been using this kernel for a while with aokp...but with milestone 3 and build 16 I was getting excessive battery drain during idle I checked with CPU spy and noticed the phone was not going into deep sleep.. it was completely unused...while the 700 MHz slot was always in use...its not a rogue app as I checked my better battery stats and saw nothing that was holding excessive wake lock times...also I doubt its the rom as I have switched to lean kernel this morning and deep sleep is being used over 60 percent of the time.
[Samsung Galaxy Nexus] franciscofranco:
#16.1 is out :)
[Samsung Galaxy Nexus] ARod111:
It finally reports the data in "running apps" correctly! Great job franco! SUPER SMOOTH!
[Samsung Galaxy Nexus] king23adrianc:
i know! lol finally :p

but francisco made me don't care about ram anyway LOL
[Samsung Galaxy Nexus] Redflea:
Flashed...I'm one of the ones not getting google services over wifi.

Been on 15.2 all day and been good wifi/blue all day, after flashing 16.1 it initially didn't connect to Google services on reboot after the flash.

I rebooted again and it came up blue... :)

I'll see how it goes, and report back.
[Samsung Galaxy Nexus] wallendiaz:
Delete.........
[Samsung Galaxy Nexus] Antob125:
Question. So I know that francogazelle is now the default but for dynamic hotplug I must set governor back to francoturtle correct? Another question is francoturtle with dynamic hotplug still ideal for best battery results?
[Samsung Galaxy Nexus] franciscofranco:
Dynamic hotplug is only for turtle yes.
[Samsung Galaxy Nexus] johno168:
Does this mean that francoTurtle isn't working correctly? Or has the single-core issue been resolved?
[Samsung Galaxy Nexus] franciscofranco:
Are you reading more than I've wrote? I never said it wasn't working correctly, I said I changed to gazelle as default as I could've said ondemand was the default. Just use turtle normally like before, nothing is broken...
[Samsung Galaxy Nexus] wallendiaz:
Now with the version 16.0 and 16.1 I have much lags in some games and Benchmark Antuntu :s
[Samsung Galaxy Nexus] minooch:
facepalm

Seriously, do you not read?

Everything is A OK - Nothing is broken!

---------- Post added at 02:28 PM ---------- Previous post was at 02:27 PM ----------

what gov are you using

what Freqs?

hotplug?
[Samsung Galaxy Nexus] johno168:
oops! Overlooked the cosmetic part so sorry!
[Samsung Galaxy Nexus] yyz71:
16.1 is a lot smoother. Thank you :)
[Samsung Galaxy Nexus] wallendiaz:
This...
[Samsung Galaxy Nexus] Felixpau86:
Just a FYI in the app the changelog isnt showing... no big deal... I can read it here but just a heads up its not showing.
[Samsung Galaxy Nexus] franciscofranco:
You need internet connection.
[Samsung Galaxy Nexus] johno168:
probably haven'd used it for a long time, but hows the battery anyways?
[Samsung Galaxy Nexus] WillyWonka23:
Does Google Voice work with this kernel?
[Samsung Galaxy Nexus] Redflea:
Wifi continues to connect to Google services without any issues...looks like 16.1 fixed the issue I was having.

Thanks very much, Franco.
[Samsung Galaxy Nexus] minooch:
Are you serious? :confused:

---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------

try rebooting into recovery - clearing the cache & then reapply your settings
[Samsung Galaxy Nexus] wallendiaz:
The battery life for me is normal, some 14 hours with 16.0, Now im on 16.1 but I don't know how will be the battery life.
[Samsung Galaxy Nexus] WillyWonka23:
Yes? Post was made couple pages back with issues.
[Samsung Galaxy Nexus] johno168:
GTA 3 10 year anniversary isn't working. Closes on startup. Tried clearing data as well. Ended up reinstalling it, all is well now! Must've been becuase i switched from trinity to franco that casued it!
[Samsung Galaxy Nexus] poopooface:
Unfortunately, with 16.1 I am still experiencing an issue I had with 16.0: The phone is frequently activating the second core and kicking it up to 1GHz. Like once every few seconds. I am pretty sure it's not the fault of a rogue app because the only other thing I changed since 15.2 was swapping out a few icons.

Please see the attached screenshot, but ignore the far right portion of the middle graph as it kept on failing to erase the graph info due to some sort of bug. But you get the point.

Battery is close to stock and atrocious with this build compared to previous Franco - 1-2%/hour, whereas with 15.2 I could go to sleep for 7 hours and not lose a single % with my 3600mAh Chinese aftermarket battery

Anyone have any idea as to what could be causing this? I'm gonna have to go back to 15.2 until this is solved.

Update: I flashed back to 15-test4 just because I really like the concept of dynamic hotplug, and the "bumping to 1GHz every few seconds" problem is gone. It seems like something in the upgrade to 16.0 caused the problem to start.
[Samsung Galaxy Nexus] wallendiaz:
You can send me the kernel 15-test4??? I have some problems and lag with 16.0 and 16.0. Thanks
[Samsung Galaxy Nexus] giangishanghai:
16.1 possible wifi signal drop?

hi all,

i am on 16.1 now, coming from 16

all is fine except wifi signal that is just at the minimum level.

pls notice that my desk is just 2 meter far from wifi modem and normally i can get full range signal.

again, coming from 15.2, than 16, no problem with wifi.

cheers
[Samsung Galaxy Nexus] johno168:
Have you tried using a different radio? My wifi seems to be all good. #16.1 Gazelle with 700/1200
[Samsung Galaxy Nexus] poopooface:
Here you go... apologies in advance if I'm not supposed to post this.

I incidentally had a weird issue whereby flashing test4 coming from 16.1 caused me to go into single processor mode. So back to 15.2 with me until the issues with 16.1 are worked out.
[Samsung Galaxy Nexus] minooch:
OK - Notice how you were ignored? Well, That's because you're barking up the wrong tree - Your Issue with Google Voice is probably ROM related! The Kernel & Google Voice don't share a bed!
[Samsung Galaxy Nexus] flolep:
Ok. Just a follow up.

Build 16, with the same parameters for testing, seems to be more stable. No SOD at all until now.

So I suppose my phone didn't like the default 87% voltage of stock and the default stock values are more stable for my phone...

I will try some custom values (like 95% to begin) and see if I can get some more battery juice without having SOD...

I will now flash 16.1 and will report if I have SOD again.

+ +

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] 2dorr:
Last night with 16 version, while the phone was charging, I got a reboot with boot animation loop. The same that I had with some older versions. I have the last bixie ROM. I hope 16.1 resolves this issue.
[Samsung Galaxy Nexus] danielvc:
Going to check if the Wifi-problem is still here. Getting good reception with my 5/2.4Ghz router, so that's already ok.
[Samsung Galaxy Nexus] WillyWonka23:
I'm on aokp milestone 3. I'm surprised nobody has had the issue. Will check Romans forum.
[Samsung Galaxy Nexus] monkey hung:
My phone is going really slow and lagging since the #16 update. My phone is also getting hotter. Franco gazelle is not speeding things up like they should. How can I send u a log to show you? I just reinstalled aokp milestone 3 after a full data wipe and its already lagging.

After playing around with is some more, it's really lagging when I press buttons and is still blazing hot. 15.2 hasn't given me any problems though. Also, the hot plug or whatever caused my phone not to wake up this having me to pull my battery.
[Samsung Galaxy Nexus] giangishanghai:
thanks for your suggestion.

actually i haven't change my radio so far and with 15.2 and 16 kernel version i had no problem.

as i know kernel is not relatet to radio stuff but i will try some new combinations.

cheers
[Samsung Galaxy Nexus] johno168:
Yeah, then again kernel's have the wifi driver. So you might want to try another kernel. I recommend Trinity, its my 2nd option, after franco.Kernel of course!:D
[Samsung Galaxy Nexus] Tubes6al4v:
Just thought I would note that I used auto update for the first time with no issues. 16.1 is running well on my phone with turtle, dhp, and slight undervolt (1200/1100). Thanks for the great work franco!
[Samsung Galaxy Nexus] crecsky:
I think I may have figured it out. Its your routers group key update interval. I am guessing this kernel doesn't play nice with some people wpa-personal security settings.
[Samsung Galaxy Nexus] krasnoff:
two test with Dynamic Hotplug ON & OFF

Franco, may be this be interested:

initial data - airplane mode: on, auto brightness: off, auto rotate screen: off, kernel: 16.1, governor: f.turtle, min/max: 350/1000, Hotplug Mod (one that is active when the screen is turned off): off, rom: milestone.3;

preparation for the tests - reboot, unlock only after the first screen off, start app franco.Kernel Updater for to check & change the value Dynamic Hotplug;

beginning tests - start antutu test, pressing the home button, start quadrant test, pressing the home button, start smartbench 2012 test, pressing the home button, start app "Video" and play four short videos, pressing the home button, start app "CPU Spy" for taking screenshot. I tried to run tests as maximized identical, I tried to imitate the vigorous activities of the user.

result - with Dynamic Hotplug ON device is more work at higher frequencies of the CPU.

p.s. may be my method of testing is not correct, but the result seemed interesting
[Samsung Galaxy Nexus] MarcLandis:
I know it is a long thread now with quite some pages to read but this has been answered several times already.

Basically with 700MHz the CPU will do its work faster and will go to sleep faster.

"Race to idle" are the magic words. Search for it to get some more information.
[Samsung Galaxy Nexus] CaspaTheGhost:
Thanks Franco, I'll update via my newly purchased app of yours... Wont be till the end of the day mind, using my crappy 'work' BB at the moment!
[Samsung Galaxy Nexus] EsPeHil:
X2

Your kernel has worked nicely for me so I decided to buy the app. :)
[Samsung Galaxy Nexus] apratomo:
happened to me as well, CPU keep bumping to online/offline rapidly and change frequency to higher ones. I'll revert back to #15 test4
[Samsung Galaxy Nexus] giangishanghai:
wifi drivers are not equal to radio stuff.

i prefere to have Franco Kernel cause my device is and was always running good with his package.

anyway thanks for your help and keep in touch for furter news...

cheers

---------- Post added at 06:23 PM ---------- Previous post was at 06:21 PM ----------

thanks mate!

this is something i have to deeply look inside.

will report about this if i can get better performances

cheers
[Samsung Galaxy Nexus] atsavlis:
No problems at all with v16.1

Wifi works flawlessly, dynamic_hotplug works just fine with CPU sleepin... 13hours run time and down to 84% with wifi on and accounts syncing.
[Samsung Galaxy Nexus] Kaboosey:
Kernel is getting better, so do the app!

Don't have regrets buying the app!

Good job franc! Keep up the good work!
[Samsung Galaxy Nexus] ChosSimbaOne:
It completes the computation faster and therefore returns to deep sleep faster.
[Samsung Galaxy Nexus] krasnoff:
When I turn the "Dynamic Hotplug" ON, the processor operates at higher frequencies, even at idle; if the "Dynamic Hotplug" is not enabled, at idle the CPU frequency is always a minimum. Checked after a reboot, without any backround apps.
[Samsung Galaxy Nexus] Vangelis13:
Try putting the minimum on 700?
[Samsung Galaxy Nexus] Mondfahrer:
I am running 16.1 on francoTurtle with 700/1200 MHz and dynamic hotplug. Everything is great on milestone 3 and also I couldn't find any issues yet.

Great work as usual!

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] atsavlis:
Guys, the constant fluctuations we keep getting in the CPU's I dont think has to do with anything Franco is doing, but more to do with Android OS. As we all know, ICS has a small bug that keeps the system awake when the screen is off. Apparently 4.0.4 has "fixed" this, unfortunately we will only know once its out for us GSM users.
[Samsung Galaxy Nexus] tyyau:
Every time I change the CPU settings it reverts back to stock. I did check the "set at boot" option. Help please.
[Samsung Galaxy Nexus] chardd23:
To disable: echo 0 > /sys/module/dsscomp/parameters/hotplug_enabled

To enable: echo 1 > /sys/module/dsscomp/parameters/hotplug_enabled

do i enter this in terminal emulator?
[Samsung Galaxy Nexus] apratomo:
But I noticed on test 4, it doesn't acting up that much. Hopefully someone will come up with some solution or if its true 4.0.4 will fix that
[Samsung Galaxy Nexus] CaspaTheGhost:
Just installed 16.1 and also notice the CPU jumping around a bit whilst the phone is sitting idle. Jumps up to 1ghz and brings CPU1 online more often than I would have thought, and it goes offline again nearly straight away.

Also, the set on boot option doesn't seem to work as it defaults back to Gazelle.
[Samsung Galaxy Nexus] franciscofranco:
Dunno, it works for me just fine.

Ok heres the deal and I will mark this up in the OP pretty clearly when Im back home from the dentist, I'm not going to answer any kind of help from users that dont use 700mhz as minimum frequency, specially with dynamic hotplug enabled. I set it as default for a reason and its been proved countless times to be the best option, but Im starting to get a little tired of issues posts that in the end, what all of them have in comon is having 350mhz as min. I'll end up removing 350mhz all together and decrease 700 to 500 or something in hope this 350mhz thing ends.

About the jumpings between min and max while using dynamic hotplug I'll take a look when I get home, maybe I did something wrong in the function.
[Samsung Galaxy Nexus] nicandris:
am i the only one with this? Cleared market cache and reverted to stock DPI
[Samsung Galaxy Nexus] danielvc:
You need to change DPI to stock [and then reboot] and then clear market cache/data. It is not Franco's app.
[Samsung Galaxy Nexus] Felixpau86:
If you guys cant get the voltages to stick and you're on apex... remove your Franco app UV settings and turn off on boot. Then plug those values into built in apex UV app. Set that to boot and it'll stick.
[Samsung Galaxy Nexus] Stretlow:
Im running GSM 4.0.4 currently ;)

Wanted to test the battery today with the stock kernal before flashing francos over it.
[Samsung Galaxy Nexus] refaa:
Yeah that was it lol i forgot that

Thanks man
[Samsung Galaxy Nexus] qsec:
If you are running aokp look in rom control, performance. Uncheck set at boot. That did the trick for me. If your problem is in Francos kernel app that is.
[Samsung Galaxy Nexus] East_Coast:
When I change the governor from francogazelle to francoturtle it still shows the current governor as francogazelle. Any thoughts?
[Samsung Galaxy Nexus] Guzmanus:
Am I the only one who can't change the hotplug? I change the 0 to 1 onth the files but when I restart it keeps being 0.
[Samsung Galaxy Nexus] macellaio:
I've been using the Franco Kernel for about 2 weeks now and it's been a great experience. A couple thoughts and please forgive me if this has been covered before:

1. I see a lot of folks saying that with dynamic Hotplug CPU0 will jump up and cause CPU1 to come online. Perhaps a counter would temper this behavior? Check to see if CPU0 stays >700 for x milliseconds or cycles before enabling CPU1?

2. I love the Hotplug mod and was a bit disappointed it didn't work in conjunction with dynamic Hotplug, but maybe there's room for compromise. Would there be any benefit to adding another condition to the CPU1 online logic to check the screen state? If current frequency is bigger than the minimum and the number of online cpus is 1

AND screen state is ON

, cpu1 onlines. This is similar to the Hotplug mod in that, if the screen is off do we really care that much how quickly a task gets done?

edit:

3. Forgot a big one. In your app, would it be possible to run the script to bring CPU1 online whenever the governor is changed? Seems like that would solve a lot of headaches for you too.

I really think you're on the right track with dynamic Hotplug and it's great to have such dedicated devs such as yourself. Thanks for everything and keep up the good work.
[Samsung Galaxy Nexus] Elganja:
i was actually really confused too... the part that confused me was

to me, this sounds like the phone was getting stuck in single core mode only and never using the 2nd core. I also don't understand how it is a cosmetic fix only.

either way, I changed it to francoTurtle and selected "set on boot" w/ Dynamic Hotplug selected... hope it powers up and down cores accordingly...
[Samsung Galaxy Nexus] krasnoff:
No, not that

Franco, do not do this, please. The minimum frequency of 350 actively used by many applications such as book & rss readers, music players, mobile forums clients & etc.

Just write in the description that the "dynamic hotplug" works only with 700 MHz minimum.

The idea of ​​energy-efficient "franco.turtle" governor is not compatible with the frequencies close to the maximum. Let it be a slow governor, but really energy efficient governor.

For example, I have worked with my device approximately six hours (except a deep sleep), and at a frequency of 350 MHz processor worked longer 4 (four!) hours:
[Samsung Galaxy Nexus] MarcLandis:
How do you change it?

---------- Post added at 03:59 PM ---------- Previous post was at 03:57 PM ----------

How do you change the hotplug? In the app, in the shell or in an init.d script?
[Samsung Galaxy Nexus] danielvc:
Is accidentaly clicked thanks, but if you have these questions, just buy his app. It's all so simple then.
[Samsung Galaxy Nexus] MarcLandis:
I already have the app and I helped Francisco with the new layout. My questions were directed to the users I quoted.

P.S.: for the fun I clicked Thanks too :D
[Samsung Galaxy Nexus] dajmanjt:
Can someone post the link for 15 test 4 kernel? Thanks :)
[Samsung Galaxy Nexus] Baguett:
If i flash this kernel with GN toolkit v5.2 to my stock, but rooted glaxy nexus, will i still be able to receive and install OTA's? (yakju)
[Samsung Galaxy Nexus] MarcLandis:
You need to have ICS 4.0.3 to use the kernel. Otherwise you will end in a bootloop.
[Samsung Galaxy Nexus] JcMalta:
Sorry ... I read your original post too fast .... I was probably talking out of my wrong end -- MarcLandis' advice is probably more accurate.
[Samsung Galaxy Nexus] loudaccord:
if you're just changing the 0 to 1 with Root Explorer, it's working after you hit save and exit. Once you reboot, it will go back to 0... don't reboot.
[Samsung Galaxy Nexus] Baguett:
Ok thanks, thinking about changing to ARHD or something, but it's so annoying to wipe the phone, and i guess i'd have to do that every tme an update to the custom ROMs comes?
[Samsung Galaxy Nexus] JcMalta:
Not neccesarily ... a full wipe is usually only needed when you completely change ROM ... thereafter you should only need to wipe cache for updates from the same ROM "family" unless the developer advises otherwise or things start going weird...

Kernel changes do not require a wipe at all ... but I generally clear my cache out of habit, since it is quite painless.

Also .. for the first few times you start playing with new kernels and roms ALWAYS take a NANDROID backup and also a Titanium backup (and copy to your PC) before starting. Can make life so much easier should anything can go wrong!
[Samsung Galaxy Nexus] poopooface:
I posted it a few pages back.
[Samsung Galaxy Nexus] Baguett:
Sounds great, thanks!! Seems like the ROM that most people like is Android Open Kang Project, so i think i'll be sticking to that one.
[Samsung Galaxy Nexus] Guzmanus:
Allright i thought the setting was maintained on reboots, i think i'll make a script to load it at boot. Thanks!
[Samsung Galaxy Nexus] East_Coast:
I attempt to change it in the updater app. It just always says gazelle no matter what check box is checked.
[Samsung Galaxy Nexus] MarcLandis:
Make sure that your ROM doesn't have an own settings section where the governor is set on boot.
[Samsung Galaxy Nexus] CaspaTheGhost:
Definitely defaults to Gazelle on reboot after applying the set on boot option in your app. Double checked and both my ROM's performance settings and System Tuner (using it to monitor CPU's only) aren't over riding it either...

Thanks for looking at the jumping CPU...
[Samsung Galaxy Nexus] kin24173493:
it happened to me as well. after reboot it backed to default governor - Gazelle
[Samsung Galaxy Nexus] alec534:
I get amazing drain at idle (<1% per hour), but it seems to drain fairly quickly with the screen on. Any ideas on how I might check out what's doing this?
[Samsung Galaxy Nexus] poopooface:
Go into the stock "settings" app, then under "device", click "battery". It will show you what % of your power drain is coming from which causes. Most likely, the screen is sucking up a lot of juice. This is to be expected, but you can turn down the brightness to lessen the impact.
[Samsung Galaxy Nexus] chirea.mircea:
Hey Franco, what's your opinion on undervolting now that bedalus has proven that on Nexus S it does't help at all to cut the voltage even in half.
[Samsung Galaxy Nexus] East_Coast:
I am running a stock rom other then root/cwm recovery.

My battery life is pretty poor. 2.5hrs off the charger and down to 64% with light usage.