yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] DarkGruf:
I can also see that in the init.d file i have the good values in 13overclock :

#!/system/bin/sh

echo 70000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo 1350000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo francoGazelle > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

(the one i set with the app) but looks like if the init.d was ignored. Hope that helps to surround the bug :)
[Samsung Galaxy Nexus] franciscofranco:
Yes I thought about that :)

Currently after I release #16 (in a few hours) this will be possible:

1. Normal dual core like it came from Google (dynamic hotplug and hotplug mod are disabled by default)

2. CPU1 down on screen off (works for every governor)

3. Dynamic hotplug, cpu1 off if current_freq = min_freq and num_online_cpus = 2. Only for turtle

A possible "disable cpu1" is very easy and one can do that simply by doing echo 0 > /sys/devices/system/cpu/cpu1/online, but I can add that option to the app in the future, easily.

Sorry, I can't help, something must be broken with your init.d or something :/
[Samsung Galaxy Nexus] neverhappy:
Running Test4 most of the day in turtle. Been using moderate /heavy (by my standards). been using two email sevices, google talk, browser, set to CDMA (LTE disabled), with 4.0.4 radios installed, And WIFI always on. Much beeter than when I first got this phone.
[Samsung Galaxy Nexus] danielvc:
Argh, I must to go to bed now. All excited and **** :-D
[Samsung Galaxy Nexus] jan-willem3:
Will 16 also include linux 3.0.19?
[Samsung Galaxy Nexus] StuMcBill:
Excellent thanks Franco!!
[Samsung Galaxy Nexus] crecsky:
Will build 16 have a fix for the WiFi issues many of us are having?
[Samsung Galaxy Nexus] franciscofranco:
No, nothing important on .19 as far as I could see.

I can't issue a fix on something that ain't broken, I can't fix a problem that I can't reproduce.
[Samsung Galaxy Nexus] king23adrianc:
lol that is no where close to even moderate by my standards! :p

from what u have, i would say extremely light use for me :D

---------- Post added at 12:13 AM ---------- Previous post was at 12:11 AM ----------

very excited to see!!! push it out before i sleep tonight :p
[Samsung Galaxy Nexus] nicandris:
i really wanted to upload this. KUDOS to franco! love it! thanx a lot for your hard effort!
[Samsung Galaxy Nexus] darrendm:
I had test4 and I went on the app to redownload 15.2 and the app/phone locked instantly locked up (didn't even download) and it rebooted and now I apparently have 15.2 kernel. Pretty weird. I just updated the app now so maybe this problem is fixed. I have no clue how I'm back to 15.2.

PS - I'm certain that test 4 said test4 in about info!!!
[Samsung Galaxy Nexus] joelteixeira:
Wow, 34 hours. Amazing. What governor and min/max are you using. 3g, wifi was on?
[Samsung Galaxy Nexus] HideYoKids:
OS is greater than screen time so ST must have been pretty low.
[Samsung Galaxy Nexus] franciscofranco:
It probably flashed the boot.img that is stored in /data/data/com.franco.kernel. That behavior is changing a bit, coding at the moment.
[Samsung Galaxy Nexus] hasnol143:
I've been using the turtle governor now with Max CPU set 1200 and min 700. With normal/heavy use and I got 19hours and 30% battery to go! That's awesome! Thx Franco!

P.s. I have apex 1.0.2 ROM, sick ROM.
[Samsung Galaxy Nexus] vitalero:
I am using AOKP rom with this franco [ THX FRANCO !!!!!!!!]

can someone guide me threw the Set Cpu/Voltage/Governor tab? in privet also is fine

THX :)
[Samsung Galaxy Nexus] nicandris:
cpu can be set up to 1350 for overclock (more MHz more calculations per second) but it drains more battery.

Don't mess with franco's fine tunings on voltages. governor it's up to you (explained a few posts back)

i would also suggest purchasing franco's app from the market (link to OP) as it has more features in there
[Samsung Galaxy Nexus] aimetti:
for those having wifi issues.

Try forgetting network and connecting again and setup as static IP. That solved all my wifi issues.

Was getting grey / blue full bars and no connection . Thankfully no more

Oddly enough I had no issues before I upgraded to m3 aokp and 15.2 kernal. Probably due to rom tho.
[Samsung Galaxy Nexus] vitalero:
Putting it on 1350 max will make the phone more hot while in use?

and what should be the Min in that time?

and 1350 isnt too much? shouldnt i be puting like 1200 to be sure nothing wrong will happen with the device?

Thx
[Samsung Galaxy Nexus] lemmy_0:
Probably due to ROM.

Never had issues on mine.

15.2 and AOKP M3.
[Samsung Galaxy Nexus] franciscofranco:
New nightly #16 is up. Please read the changelog carefully. App update 3.1 is also out.
[Samsung Galaxy Nexus] ARod111:
Great work, this kernel is super slick! Any clue when this bug might get fixed, its the only thing wrong with the kernel and the biggest reason I'm still running 14.2. Please find a fix, please!
[Samsung Galaxy Nexus] franciscofranco:
I couldn't find the reason for that yet and I took a while to search. I'll have to dig again. But I don't see the reason for staying at 14.2 just because of that -.-
[Samsung Galaxy Nexus] ARod111:
16 is much faster, but 14.2 reports the data properly.
[Samsung Galaxy Nexus] dreamhunterr:
Could you implement the same kind of overclock (GPU/bus/RAM) Ezekeel has put in his kernels?

I know that overclocking the GPU per se isn't that effective (it seems to have become some kind of tabu in this thread, lol), but the way Ezekeel implemented it does bring some perceptual performance benefits (it overclocks the GPU/bus/RAM).

I notice it in lots of general UI smoothness aspects (a relatively reliable test I have found is trying to scroll a SMS conversation list in landscape with the keyboard overlay on; it's rather choppy on stock GPU frequencies, but it feels a lot better with the small overclock to 384 mhz). Of course it also bumps up to 10 fps in Nenamark2, but I could care less about that...

Regards,
[Samsung Galaxy Nexus] franciscofranco:
Nop, that won't happen. Ezekeel follows his path and his own code and I'll do the same here, otherwise all the kernels would be equal and I don't want that. I don't think this device needs any kind of overclocking at all.
[Samsung Galaxy Nexus] CaspaTheGhost:
Glad I stayed up late, sounds good, installed...
[Samsung Galaxy Nexus] samizad:
I hope the new updater app fixes some of my problems because, for some reason, my phone does not like your app. I have had to download the last three kernel updates using my PC.

If I still have problems with the latest updater app, I will provide specific details.

Anyway, regarding the kernel, I loved 14.2 and can't imagine how you may have improved it but I'll check now :)
[Samsung Galaxy Nexus] CaspaTheGhost:
Don't have the app, but still download direct to phone...
[Samsung Galaxy Nexus] franciscofranco:
This time I had a fair number or testers during the last 6 days so I'm pretty sure this is bugless or very polished at least.
[Samsung Galaxy Nexus] chardd23:
is the kernelupdater a paid app? no free one ? :(
[Samsung Galaxy Nexus] Jayrod1980:
Anyone know the best gamma settings for those of us with washed out greys? My dads nexus has a little green but amazing smooth rich greys. My screen seems flat and washed out in comparison
[Samsung Galaxy Nexus] samizad:
The kernel is free to download and install (see original post) but Francisco has made the app and put it on the market to allow us to support him a little by buying his app.

---------- Post added at 04:04 AM ---------- Previous post was at 03:58 AM ----------

I am in absolute awe. #16 is soooooooooo smooth I was sure it had overclocked to 1.35Ghz and Performance governor by default. When I checked and see it is still Francoturtle and 1Ghz, I could not believe my eyes.

Here's to a good battery life. Will report back in a couple of days.
[Samsung Galaxy Nexus] johno168:
Anyone noticing any difference battery wise between francoGazelle 350/1200 and 700/1200? I'm getting hisg drain on both. Can't even get 2 hours display time.
[Samsung Galaxy Nexus] aimetti:
Francoturtle very smooth now. Using dynamic hot plug as well.

As far as voltages go. I think I'm just gonna leave it stock for a bit. That the general consensus now? Howevet I have never got any lockups with Franco's voltage changes so i may go back depending on how this runs.

Overall this looks really good so far.
[Samsung Galaxy Nexus] kin24173493:
why dont u just pay for the app to support franco's work:confused:

---------- Post added at 11:41 AM ---------- Previous post was at 11:38 AM ----------

try to install this app https://market.android.com/details?id=com.WazaBe.android.BatteryDrain&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5XYXphQmUuYW5kcm9pZC5CYXR0ZXJ5RHJhaW4iXQ.. to monitor your battery usage
[Samsung Galaxy Nexus] johno168:
Will do thanks! Hows The new 16 working out for you? What settings have you got on with it? i.e. governor and min/max mhz
[Samsung Galaxy Nexus] kin24173493:
i use the default settings: francoturtle governor 700-1000, stock voltage, hotplug enabled.
[Samsung Galaxy Nexus] joeski27:
Just made the purchase...have been rocking your (Franco's) work for a few weeks now, fantastic work. Though as an overall novice I can't say I understand a fraction of the technical stuff that goes into kernel development, I can say that I understand the overall effect it has on the final experience, and all I can say is keep up the good work! :cool:
[Samsung Galaxy Nexus] johno168:
Yeah thats what im trying out now. However i was wondering if bumping the max up to 1200 would do any good/bad?
[Samsung Galaxy Nexus] Antob125:
Do we still have to open camera and force close it?
[Samsung Galaxy Nexus] samizad:
No, that is not necessary.
[Samsung Galaxy Nexus] johno168:
Nope camera and everything working all fine here!
[Samsung Galaxy Nexus] kin24173493:
in my opinion, for daily usage 1000 is enough. better to save battery:D
[Samsung Galaxy Nexus] crecsky:
Just because you personally can't reproduce the problem doesn't mean the issue doesn't exist. I paid for your app because I liked your kernel, but I guess you don't care about the multiple people who are having problems. You can't even offer any possible insight on the issue.

1. Stock rom no wifi issue.

2. Aokp no wifi issue.

3. Build 15.1 no wifi issue.

4. Build 15.2 wifi issue exists.

I know not everyone has the issue and I also know that not everyone who is running milestone 3 has the issue. But many do.

Nonetheless I will try build 16.
[Samsung Galaxy Nexus] johno168:
Have you tried Full wipe then installing kernel? Or maybe new radio? I just flashed the new XXKL1 and its giving me great wifi!
[Samsung Galaxy Nexus] Jrbourque:
He's referring to the gtalk bug that opening and closing the camera fixes. ..which I think is still present as not a kernel issue from my understanding
[Samsung Galaxy Nexus] crecsky:
I've tried a multitude of things. Although build 16 is already working better for me.
[Samsung Galaxy Nexus] franciscofranco:
Hmm I don't care? How in hell can I fix something that I can't reproduce on my working device? If you give me a suggestion I'll see what I can do, but this is common sense...no reproduction, no way to test, no way to fix... But sure I'll look again...
[Samsung Galaxy Nexus] samizad:
I never experienced this bug; which is supposed to keep the camera sensor open all the time.

I get exceptional idle performance without the camera on/off thing.

Just check to ensure you minimize the number of wakelocks and log out and turn off Google Talk if you don't use it.
[Samsung Galaxy Nexus] superbobup:
beat me to it :p

one clarification...i'm guessing stock voltage on the build 16 is quite a bit higher due to dynamic hotplug? it's at 1317 and 1203 for 1000 and 700 repsectively

EDIT:

nvm...just saw OP...-_-
[Samsung Galaxy Nexus] oli20021978:
Try flasing resetkernel from faux then new one from franco.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ArmanUV:
I am still torn between turtle 700/1000 and 350/1000. What would you guys recommend for best battery life especially screen on time?

And what do you guys use to UV now that franco's app removed set to boot? Is using AOKP Rom control for UV in conjunction with franco's app for governer/cpu/hotplug ok?
[Samsung Galaxy Nexus] johno168:
I'm using turtle 700/1200 way better! Plus i'm getting ~3 hours display time! We'll that was on 15.2, 16 feels even better! However if want the most out of your battery 700/1000 or default kernel settings are good.
[Samsung Galaxy Nexus] crecsky:
I know its hard to fix a problem that you don't get on your current system, but I asked if there was anything I could do to help you maybe come to a conclusion.

Build 16 isn't causing me any issues yet so whatever little changes you made might be the fix for some of us.
[Samsung Galaxy Nexus] G-Bus:
Is it normal that everytime I reboot the phone my cpu speeds get ressetted to Franco turtle and 700/1000?

I usually set franco gazelle with 1200 max cpu speed and every time I reboot it gets back to franco turtle, it's really annoying.
[Samsung Galaxy Nexus] FaithCry:
yes unless you tick it off to "set on boot"
[Samsung Galaxy Nexus] flolep:
Hey guys.

Thanks for build 16 Francisco.

I am sorry to report again a black SOD this night with your test 4 kernel, maguro milestone 3.

This time again I was on 350mhz - 1350mhz range and didn't undervolt anything more than your own values.

And this time my GSM phone was plugged to the charger.

And hotplug check box unchecked...

You can see the stop with "missing data" on the attached screenshot...

To stop black SOD, I have to set oc to 700 - 1200. So I suggest the problem is with 350mhz value...

I will now flash your build 16 and install a log application to try to catch the error if it exists again...

Keep up the good work.

P. S. I have the wifi problem some people here report some times too... I have to switch off and on to have it work again... :-(
[Samsung Galaxy Nexus] ArmanUV:
I hit 3h constantly. I think I have never got under 3h ST even with stock kernel.

Theoretically, 350 should be better, right? Or is there some magic going on with francoturtle that makes 700/1000 more efficient?

BTW, I assume there is no need to enable hotplug when dynamic hotplug is enabled?

I would appreciate it if you comment here franco :D!
[Samsung Galaxy Nexus] nikulogical:
I have some questions:

- is there anyway to hotplug without installing the app?

- recommended cpu levels for francogazelle?

- I get a lag when I turn my device's screen on to do my security pattern. This is almost ALWAYS present.

- currently using francoturtle 700/1000. I notice some lag esp in settings menus, multitasking while files are being downloaded/installed, some web browsing, and in some games. It's usually not a huge lag but noticeable. would it be more beneficial for me to simply up the max cpu to 1200, OC to 1300, or to use a different governor like francogazelle?

- can lower cpu levels or different governors hinder game graphics or just cause a lag?

BTW running AOKP M3 + Franco #16
[Samsung Galaxy Nexus] simplistian:
The voltages are just the nominal voltage for the Smartreflex AVS calibration, the calibrated voltages are way lower. Run "dmesg |grep mpu:" when you boot your device to see the calibrated voltages.
[Samsung Galaxy Nexus] superbobup:
thanks. i remember reading about AVS. i'll try it out now

EDIT:

to clarify, is it "adb shell dmesg |grep mpu:"?

I get the error: 'grep' is not recognizable as an internal or external operable program or batch file when using "|grep" but i get the dmesg output without the | symbol

shoot me a PM if it's easier not to crowd the thread/if you're able to :D
[Samsung Galaxy Nexus] sotoskawasaki:
I am using the GSM version with GummyNex 0.7.7 and Franco Kernel #15.1 and I get a great performance and battery life. So thanks to Franco for that. On kernel #16 which one should give better battery life? hotplug mod or dynamic hotplug? Those who tried #16 and reported better performance which one did they use? Thanks in advance!
[Samsung Galaxy Nexus] ArmanUV:
The unlock lag is an AOKP bug. Disabling autobrightness fixes it but for a real fix we have to wait for the next aokp build.
[Samsung Galaxy Nexus] 3c:
Never had SOD issues though I set min = 350 and UV 350Mhz = 825mV. Also on Maguro M3.

As for Wifi, are you using the energy saver from M3? When I tried it on a previous build, if I had Wifi on before switching off screen, then it wouldn't come back after screen-on (wifi being automatically disabled during screen off by M3 energy saver).

Could even the SOD relate to M3 and the energy saver? As I do not use it and don't have issues?
[Samsung Galaxy Nexus] detritu5:
I have an issue with #16.

Device doesn´t wake up when screen is off. With dynamic hotplug enabled

Back to #15.2
[Samsung Galaxy Nexus] sotoskawasaki:
Did you UV? And you make sure you had hotplug mod disabled?
[Samsung Galaxy Nexus] flolep:
Hey 3c. Happy to see you here. I saw you on other device forums :)

Thanks for your answer :)

Strange that you don't have SOD with the same configuration as me :( I really don't know what is the difference between our config (maybe I should try to undervolt lol but normally it shoudn't change anything, or even could be worse...)

Yes I am using M3 power saver (well, it is checked in the parameters) but I don't use it for wifi... I set it to stay as it is when screen is off. I wanted to be able, if I download something, to have it downloading even if I set screen off...

But with your advice I may try to switch power saver off just to see. But here when I switch off my screen and have wifi on, it is still on when I switch on back my screen...

The problem I have with wifi and this kernel is that the wifi icon is blue as if it was connected to the internet but there is no data coming in... I have to switch off wifi, then switch on, the icon becomes grey and then blue again and then I can have data coming in... until I lost data again :)

++
[Samsung Galaxy Nexus] detritu5:
No. I have UV by default. ANd hotplug mod and dynamic hotplug are enabled
[Samsung Galaxy Nexus] simplistian:
grep is a busybox command, do you have busybox installed? try running it inside adb shell, and add busybox before grep, like dmesg |busybox grep mpu:
[Samsung Galaxy Nexus] sotoskawasaki:
Franco said that when dynamic hotplug is enabled, the hotplug mod should be disabled to avoid any conflict. Try that and see if you still have the problem.
[Samsung Galaxy Nexus] detritu5:
Maybe this should be put in the changelog,
[Samsung Galaxy Nexus] minipaolo:
franco updater app doesn't work for me.

What is more I tried unistall it and when I try to redownload it from the market it keeps saying "your device is not compatible with this app".
[Samsung Galaxy Nexus] qsec:
Have you changed screen dpi?

Maybe the app checks that?
[Samsung Galaxy Nexus] minipaolo:
Yes, I did change DPI last night. I'm back to default now.

What can I do to unlock everything again?
[Samsung Galaxy Nexus] qsec:
Not sure what you mean? Could you explain more?
[Samsung Galaxy Nexus] jhericurls:
Go to manage apps and clear the cache on Market app.
[Samsung Galaxy Nexus] minipaolo:
Thank you! It works! :)
[Samsung Galaxy Nexus] qsec:
Is there some free app that could display the cpu's running or not?

Cheers.
[Samsung Galaxy Nexus] atsavlis:
https://market.android.com/details?...ch_result#?t=W251bGwsMSwxLDEsImNjYzcxLnBtdyJd
[Samsung Galaxy Nexus] MarcLandis:
Any app that can show you the "dmesg" log.
[Samsung Galaxy Nexus] clefster:
Hi Franco, my phone is unable to download the zips from your new web hosting provider. I had this issue with test4 and now nightly 16 as well. This is using the phone's stock browser (4.0.3) to browse to the dir listing and then click the zip. It downloads all the way then says 'unsuccessful' at the end. Your old host worked fine.

Just FYI.. not sure if anyone else can reproduce. Thanks.
[Samsung Galaxy Nexus] atsavlis:
Franco, with your v16 kernel, what settings do you suggest we run with, currently I have it on franco_turtle with dynamic hotplug...

What are you running??
[Samsung Galaxy Nexus] cjones1348:
So I need some help......

Running Franco Kernel #15.2 and AOKP M3;

First time this has happened - I went to bed last night and had around 39% charge, didn't plug in - woke up this morning (about 7 hrs later) and the phone was off/dead, I found this odd but plugged it in to give it a quick charge before I left for work.

Unplugged it and headed to work and it showed 2% charge - got to work and it was dead, plugged it in and left it for about 10 mins, turned it on and now its saying 52% charge...how did this happen?

Anyone have this happen or have any ideas as to what could be going on? Other than this issue I've been having fine battery life.

Thanks.
[Samsung Galaxy Nexus] drmason:
@franco or who might know...

Regarding the sdcard binary in the current kernel, I have issues for several time now. GTAIII and my Music Streaming Application (Subsonic) won't work properly with the current Kernel (AOPK M3, Franco #16)

If I extract the sdcard binary from the stock 4.0.2 it's working fine. Are there any dependencies why this might be a bad idea (sdcard corruption?) or can someone point me in the right direction what's the difference here?

I won't mind GTA not working but I heavily depending on my music ;)

TIA!
[Samsung Galaxy Nexus] blackdub370:
GTAIII work fine for me
[Samsung Galaxy Nexus] vitalero:
how can i update without the app? i need to make a clear wipe and then update? wont it delete my rom ? and my apps?
[Samsung Galaxy Nexus] ro_explorer:
If you are booting the phone with the charger plugged in, your battery reading will go berserk until a full charge (which will take as usual, no matter is showing 52%).

---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------

Download kernel, flash from CWM .. reboot.

The kernel has a built-in script that will clear your cache and dalvik. No other steps are required. All your applications, settings, rom and other stuff will remain untouched.
[Samsung Galaxy Nexus] dyndragon:
Franco, just woke up to a SOD. Unfortunately there was no last_kmsg. Running Francoturtle with dynamic hotplug 700/1000, no undervolt.
[Samsung Galaxy Nexus] maisi:
Look for "2nd core " in the market ;)
[Samsung Galaxy Nexus] Elganja:
i may be misunderstanding you, but are you saying that the actual voltages are not the ones set, but they set a base for the calibration to start from?
[Samsung Galaxy Nexus] chardd23:
is dynamic hotplug enabled by default?
[Samsung Galaxy Nexus] MarcLandis:
No - Please read the changelog.
[Samsung Galaxy Nexus] cjones1348:
Thanks, I had no idea that was an issue!

On another note, is anyone else having trouble with the Franco App? When I check for newer versions #16 doesn't show up, just says I'm up to date with #15.2
[Samsung Galaxy Nexus] atsavlis:
Read the OP, if you dont have Francos app from the market, you have to use a script in init.d to activate it at boot the same way we did for the hotplug script.
[Samsung Galaxy Nexus] minipaolo:
I guess it is normal, but with hotplug enabled it sits really often on 1000mhz and it turns to be even more battery hungry than normal.

I might be wrong, but I'm not seeing any positive effect at the moment.

I'll keep it enabled to see how it goes.
[Samsung Galaxy Nexus] loudaccord:
My nightly 16 findings (all good)

Dynamic hotplug is working for me:

It's fast even on turtle with dynamic hotplug enabled if desired(typically keep it on 700/1000 but bumped it up to 1.3ghz just to test):

Battery is good overall for me and everything looks to be working.

A++ Thanks FF!
[Samsung Galaxy Nexus] zerozoneice:
dumb question, does this kernel run on 4.0.2?
[Samsung Galaxy Nexus] loudaccord:
no

10 char
[Samsung Galaxy Nexus] Elganja:
you can read the OP, the title, or numerous posts in this thread...

they all point to NO
[Samsung Galaxy Nexus] nic85:
which app is that?
[Samsung Galaxy Nexus] refaa:
Iam on 4.0.2 where can i download older vers. Of this rom that works with my version of rom?

Peace