yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] rolear8:
I flashed M5 and franco kernel M3 and when I run atuntu benchmark I have a very poor performance, around 3100 points also a very low GPS ~30... Before flashing these I got +6500 points and ~59 fps (I had M4 and franco M2)... Anybody has the same problem?

No body? Also I started to have lag, I remember there was a fix for the.low fps, modifying a file but can't remember.

Any help will be very appreciated
[Samsung Galaxy Nexus] qballe:
Whaaaattt ?????? absolutely not !!! A chip can or cant work on a voltage under reference but MUST work on a frequency under its default !!!
[Samsung Galaxy Nexus] Metallice:
What gave me away? :) I'm trying to remove trimming from Franco's kernel to allow freqs up to like 1.8ghz or so (before melting occurs) . Unfortunately this causes issues with the implementation of custom voltages he's using. Had to use ezeekels newest version. Trying to work through all this while also adding vibration and regulator control.

But there's a reason I'm using Franco Kernel as a base :)
[Samsung Galaxy Nexus] Metallice:
You can go to lean kernel's thread. Some people can run 180mhz, some can't. Some insta-reboot when they try. That's why imoseyon added a 230mhz version for people who couldn't run 180mhz.
[Samsung Galaxy Nexus] Metallice:
Oh and Francisco, I would highly recommend this if you plan on keeping 192 as an option.

https://github.com/imoseyon/leanKernel-galaxy-nexus/commit/ebef68d6e1089a72aff32d84e1e7747099606b69
[Samsung Galaxy Nexus] twissii:
Thanks man :)
[Samsung Galaxy Nexus] Brandon3003:
Awesome kernel. Glad to see undervolting brought back, my battery thanks you.
[Samsung Galaxy Nexus] akellar:
Awesome kernel sir. I have it UV by 225 from your settings and it's running good so far. -250 locked up so hopefully this is my phone's sweet spot.
[Samsung Galaxy Nexus] aron7awol:
Does this apply to all governors or only ondemand? Also, it is my understanding that interactive and ondemand work similarly except interactive is more aggressive and thus has better responsiveness at the expense of some battery life. Is this still true after the tweaks you have made to the two governors? Do you use ondemand as default over interactive to save battery, or because you have tweaked it to actually be more aggressive than interactive?

Also, do you plan on updating your bitbucket repository to reflect the latest changes? I'd like to take a shot at adding the 1.35 GHz speed step to your kernel myself since you don't plan on adding it. I want to see how high I can get on Antutu and Vellamo.

Thanks again for your work on this kernel.
[Samsung Galaxy Nexus] lordofcamster:
Stock voltages are: My voltages are:

1025 850

1203 950

1317 1025

1380 1150

Stable! :)
[Samsung Galaxy Nexus] franciscofranco:
I added that functionality directly into the omap driver, it works independently of the governor. I only tweaked both governors so they would ramp up more frequently. By default they would ramp up if cpu was > 95%, now they do it on 80%. But they work differently, interactive is more agressive indeed.

I plan to update it yes, and I plan to add 1,35ghz next nightly...and actually thinking of getting rid of 350mhz step, it's too low and it causes more wakeup from idle than 700mhz, but I'm still testing.
[Samsung Galaxy Nexus] akellar:
Wouldn't removing the 350 step negatively impact battery life sine 700 generally requires a higher voltage to run stable?
[Samsung Galaxy Nexus] jetrii:
Very nice! What kind of battery life does that translate to?
[Samsung Galaxy Nexus] StuMcBill:
Just flashed this kernel, coming from Paul at MoDaCos latest kernel and straight away the battery drain on this kernel seems much higher.

Seems much, much snappier though.

Keep up the good work.

Sent from my Amiga 500 using Workbench
[Samsung Galaxy Nexus] lordofcamster:
I test until tomorrow!

Runs since 2 Hours
[Samsung Galaxy Nexus] energie:
I font think Uv Will help with battery Life....i men 30 min total? :)
[Samsung Galaxy Nexus] akellar:
False. The only reason to UV is to improve battery life. It definitely improves battery life.
[Samsung Galaxy Nexus] energie:
Yea lets see ho much
[Samsung Galaxy Nexus] taylormadearmy:
OpenVPN

Has anyone got OpenVPN working with this kernel? I had it successfully working on Stock and Modaco kernels using the instructions from here:

http://xdaforums.com/showthread.php?t=1378196&highlight=tun+ko

but on this kernel I get "Fatal:Cannot allocate tun/tap dev dynamically" error.

Can anyone help?

Thanks!
[Samsung Galaxy Nexus] inffy:
My Voltages now are:

1200MHz: 1175mV

920MHz: 1050mV

700MHz: 975mV

350MHz: 850mV
[Samsung Galaxy Nexus] ro_explorer:
I cannot load the module.

// sent from my green robot //
[Samsung Galaxy Nexus] Manafa:
I asked this question twice in this thread and got no answer. I'm not familiar how exactly the kernel works and this is the reason to ask. I read all posts and find no answer. Maybe is very hard to do it, guys, or the question is so stupid, but thanks for nothing. If I asked why having bootloop when install Franko's kernel on 4.0.2 ROM, I will get plenty of replies, instead it is written in the first post. Nevermind, merry Christmas to all of you, I will stay with stock kernel. I hope my modest donation will keep Franco's nice job.
[Samsung Galaxy Nexus] skyhigh2004:
I'm running

1200:1100

920:975

700:875

350:750

Stable for quite some time now. Thanks for the super smooth kernel Franco.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
You don't have to install anything else. If you want to change frequencies and voltages install SetCPU, otherwise you need nothing to have it work, it's all out of the box.
[Samsung Galaxy Nexus] :
Hi,

I'm new with the Galaxy Nexus,after choosing my rom,i chose my kernel :D

Your kernel is awesome:smooth and fast...Especially smooth!!! :eek:

But...Always a "but"...I just flash the last nightly (#6) and ther's no OC?

I run Romanbb's rom,your kernel and System Tuner pro for the cpu tweaks...but i stuck at 1.2Ghz :confused:

It's me,i forget something or...???,i've read your thread but nothing about a "no OC" with your latest kernel...

BTF 5 hours with my new toy...multiples flashing...Your kernel is the winner,smooth like butter!!!

Thanks for your awesome kernel...and thanks for a reply about o/c;)

PS:Antutu give me about 6350/6380 with ondemand/1.2ghz with your last kernel (and with Ram Manager pro set to hard-gaming).
[Samsung Galaxy Nexus] zephiK:
Read before you post,
[Samsung Galaxy Nexus] svan71:
At the "gym"

I just got my latest ear ring and when I left the ear piercer I went to the " gym" and I noticed Franco kernel is working great.... Thanks Franco now back to my squats...at the "gym"
[Samsung Galaxy Nexus] asim0:
AOKP M5... FRANCO M3...

Perfect timing! time for backup and sig update:)
[Samsung Galaxy Nexus] jhericurls:
Looks like 151 doesn't like UV'ing too much, I got a few SoDs.
[Samsung Galaxy Nexus] drawde40599:
while charging

While charging and using phone, temps get over 60°c phone slows to a crawl build 151, 384 gpu

---------- Post added at 03:15 PM ---------- Previous post was at 03:07 PM ----------
[Samsung Galaxy Nexus] spinkick:
What is the default min cpu speed on the Galaxy Nexus?

Found out it was 350
[Samsung Galaxy Nexus] axne1:
Franco thanks for the awesome

Ride! I'm staying on M3 for a month.

Great work!

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] BrUhNiGGs:
I can get my phone to go on deep sleep with 192 min with lazy governor (as told by Franco)

It seems that I get no wakelocks ever since I switched to AOKP from Liquid.
[Samsung Galaxy Nexus] BrUhNiGGs:
I cant seem to find "up_threshold" and "down_threshold" on his governor control app.
[Samsung Galaxy Nexus] asim0:
sorry for noob question, but on M3 IVA voltage is stuck on 1038mV and CORE voltage is stuck on 1063mv. I remember the latter being below 1000mV on M2, don't know if it means anything; and i've never disabled SR or set custom voltages

edit: on aokp m5
[Samsung Galaxy Nexus] Cptsamir:
I would like to see more that say that this is bad for the battery, so far everything I have read suggests that running the battery down the first time, and every once and a while actually helps the battery, and allows you to get a accurate calibration on the battery. But hey, judging but how many people say its wrong, I might be wrong.
[Samsung Galaxy Nexus] drawde40599:
Well I let it die all the time, and I get 4 hours screen on time, with 80% screen brightness,gps,data, sync on, 300+ texts a day, some phone and internet. Been doing it with all my past 12 androids and never have replaced a battery once . Is it bad for it personal experience says NO!!
[Samsung Galaxy Nexus] natious:
Why no OC version for the milestones? Would be nice to have a milestone + 380gpu clock :)
[Samsung Galaxy Nexus] Metallice:
/facepalm
[Samsung Galaxy Nexus] coolzjai:
I had this issue back in M3. Nightly 151 solved most of high temperature issue.

Please note, this doesnt mean M3 has high temperature problem, as you can see some ppl running fine with M3.

This is what you can try (which is what am doing too):-

1. download 【nightly 121 - gpu 384】 and 【nightly 151 - gpu 384】

2. boot into recovery, clean cache, clean dalvik, clean battery stats and

3. flash nightly 121.

4. reboot into normal, and observe the temperature for about 10-15 minutes,

(simply use your phone for anything u like)

5. Reboot into recovery again, and clear cache + clear dalvik

6. Flash latest nightly build 151, and you are set!

I myself after doing the above step, my temperature never go beyond 60 after playing games, no more warm issue at the camera area, and while leave my phone in idle state, the temperature was like 32 - 37.

---------- Post added at 02:31 AM ---------- Previous post was at 02:26 AM ----------

MILESTONES = factory clock!!!

hrrm...... i got slapped for this, and now i pass the slapped-figure print to you, please keep it for the next generation LOL ><
[Samsung Galaxy Nexus] raubkatze:
After some unsuccessful attempts to play with governors and cpu freqs I flashed r151 (384) and found that my device likes it considerably more than 512 gpu oc build.

I really haven't notice any diference in performance and battery life between 512 and 384 gpu oc but on 384 my phone is not heated so hard as on 512. The average temp on 384 is 34-36°C, temp after playing 52-53°C.
[Samsung Galaxy Nexus] drawde40599:
Dude u should go.back and read some, and we will pretend u didn't ask; ). Kidding!! But go back to thread were milesone was released and read u will see y no ......

---------- Post added at 06:30 PM ---------- Previous post was at 06:26 PM ----------

This a.m 151 was running great, now after trying both 384 ans 512 its running hot in the 57+ range, ever since 4.0.4 my phone been pissed off one min its good one min its not. I think ima flash stock image and see what and how that works that way I can have something to compare to
[Samsung Galaxy Nexus] dpaine88:
This is after about an hour and a half of use. Lazy governor with 192 min

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joeyfong:
R151(512) is a bit hot, back to R143
[Samsung Galaxy Nexus] celyst:
Any settings that can help to improve battery life? Is it advised to have generic hotplug, SQlite, logger off and SR on?
[Samsung Galaxy Nexus] raubkatze:
It's so individually... and in the main with rom settings for example brightness, location services, sync etc related on my mind. But for clearness set min cpu freq to minimum, use generic hotplug (but not with hotplug governor), uv cpu and if you do this turn smartreflex off.

Try "search this thread" for information you need - many users have posted their settings here.
[Samsung Galaxy Nexus] schizophrenia:
Smartreflex

a quick question

if I do not have the app, is Smartreflex by default turned off? or on?

I always set UV and is it theoretically Smartreflex will be turned off until i move all Voltage back to default Voltage?
[Samsung Galaxy Nexus] coolzjai:
Switch off mobile will do. :p

With latest nightly build, i get pretty good result in battery life, this is my config, basically all default, item 3 is what u can try for extra. Basically you will get 1-2% battery power drop on every hour.

1. Nightly R151, Interactive governor, 192Min, 1228Max, no UV/OV

2. Turn on SQLite, Turn logger off.

3. Switch ON WIFI / 3G / GPS ONLY whenever you want to use it, and AutoSync set to manual :)

---------- Post added at 05:20 AM ---------- Previous post was at 05:18 AM ----------

Default SmartReflex = Enable

Please get the apps as a supporting signal to our franco-san

---------- Post added at 05:22 AM ---------- Previous post was at 05:20 AM ----------

raub dude, does the generic hotplug mode seriously help in power saving? previous reading that it might use more power to to start up / close down one cpu.

not sure about this, not really experience it before ><
[Samsung Galaxy Nexus] raubkatze:
From app, SR is on by default.
[Samsung Galaxy Nexus] coolzjai:
give this a try

http://xdaforums.com/showpost.php?p=25477757&postcount=14197
[Samsung Galaxy Nexus] raubkatze:
Exactly if you will switch the screen on/off every minute)
[Samsung Galaxy Nexus] heo_con184:
Can someone explain for me what are SQlite and Logger ?

Thanks.
[Samsung Galaxy Nexus] raubkatze:
http://xdaforums.com/wiki/Samsung_Galaxy_Nexus/GT-I9250/ROMs/FrancoKernel
[Samsung Galaxy Nexus] SrTapir:
I've made a test session of the kernel.

My intention is to make the same test for every release in order to compare battery life between releases.

This test is not made to give a real battery life of the GNex, it's based on a stress test of the CPU (changing continuously the freqs) and GPU, and with the screen always ON. It's made to notice the differences between every new version of the kernel.

I began with the well known #r133, first of all because I wanted to try before a 2.x release (nightly before Milestone 3), then the Milestone 3 (to see stock GPU batt diffs.) and begin with new 3.x nightlies (after Milestone 3).

I took a base configuration that i will repeat from now on, this is:

- Liquidsmooth 1.3

- Stock Franco Kernel app configuration (if not's Milestone I'll use 512 GPU conf.)

- Only 384-1344 Mhz and Interactive Governor changes.

- Airplane Mode (no WIFI, no BT).

- Brightness set to minimum (Liquidsmooth "Dim Level" to 2).

I used this apps:

- franco.kernel updater

- Stability Test

- CPU Spy

- BetterBatteryStats

- AnTuTu Benchmark

- Quadrant Standard Edition

#r133

For this first time I've made 3 tests to look for the differences between different configurations.

The first test is with the upper specifications and will be the base for every new test for every new version from now on.

The second test is the one with the UnderVolted values of the CPU, GPU and IVA (to the max. allowed by my device).

The third one is the one with the 729-1036 Mhz freq. band. I think the kernel is good enough to give an excellent experience with the top speed limited to 1036 Mhz, and I wanted to see if this gives great savings on batt. life.

Test 1. STD. No UV.

Test 2. UV. (these were my UV values)

Test 3. 700-100Mhz.

in progress...
[Samsung Galaxy Nexus] schizophrenia:
I do have the app and again thanks to Franco

but i am just curious, are there any Smartreflex IF I do not have the app
[Samsung Galaxy Nexus] raubkatze:
Smartreflex is a part of kernel.
[Samsung Galaxy Nexus] drawde40599:
R u drinking? I do a test also its called life, and my test has better battery then urs . What is the point of this??then using a nightly that is dead and gone? Running tests in controlled environment?? Its a phone bro, not cure for cancer.

Yell at me if u want, I'll like it . OK by; )
[Samsung Galaxy Nexus] SrTapir:
:eek::rolleyes:;)
[Samsung Galaxy Nexus] raubkatze:
I don't understand another thing. How is this possible when using device in airplane mode have only 2,5 hours battery life in spite of using stock battery

StabilityTest app?
[Samsung Galaxy Nexus] The Nexus Project:
Milestone 3 for a few weeks for me. Yes it's that good

Sent from my i9250 (GSM) Galaxy Nexus.

Phazenine@Twitter
[Samsung Galaxy Nexus] SrTapir:
I copy myself, 2 of the 3 first sentences:

My intention is to make the same test for every release in order to compare battery life between releases.

This test is not made to give a real battery life of the GNex, it's based on a stress test of the CPU (changing continuously the freqs) and GPU, and with the screen always ON. It's made to notice the differences between every new version of the kernel.

¿You really read all that's explained in the post? It's a closed test in a standard configuration to search for differences between kernels.

Doesn't matter, I'll not continue with this..

By the way, if you noticed something, you can see in to the test that Undervolting has no any value in the kernel due to a minimal gain in overall time test, this is a real value, due to was tested in the same conditions..

This test purpose was to test this little things that everyone is asking and asking and asking and asking again and again and again, and give something to sustain real answers..
[Samsung Galaxy Nexus] spinkick:
Nightlies are posted for testing and by doing it scientifically, it reduces error based upon making observations based on crap testing in "life"
[Samsung Galaxy Nexus] spinkick:
He is stress testing at full brightness. Running the cpu full blast through different levels of load.
[Samsung Galaxy Nexus] SrTapir:
Also:

1. It has to be made in airplane mode because there are huge differences if you have good or bad gsm coverage, you are in 2G, 3G or LTE, you're on WIFI, etc..

2. I used a "Stress Test" because I have to speed up the process of draining the battery life, I can't spend all the day to it to be drained.

3. I used a CPU/GPU test because I want to test the differences between 300 and 500 GPU speeds affecting battery life (something that Francisco has testing also).

4. i'm using and old nightly becuase #133 is considered one of the best battery friendly kernels released and I wanted to compare this one with Milestone 3 and future nightlies released.

5. etc..
[Samsung Galaxy Nexus] spinkick:
Told you guys undervolting was worthless. Smartflex is enough. The most significant power eater is the screen and radio.
[Samsung Galaxy Nexus] SrTapir:
:o

Thanks.
[Samsung Galaxy Nexus] zipredictive:
Wtf is wrong with you guys .... these are testing kernels ..... so every kind of test stress test etc is good.... for everyone who wants to try this kernel and Franco too....

And those test are much better than my "omg good battery Life" or yours "not this time number xxx was better"

So do you find it usefull ? Ok say thank you and watch those screenshots.... you dont need it? Ok shut tfu and respect others work
[Samsung Galaxy Nexus] bat0nas:
Hi,

Why this "Enable fast USB charge" is not enabled by default in stock ROM/Kernel?

Is it safe to enable it in this kernel? What could be the consequences?

The idea why I'm asking is: when I'm using Sygic navigation software in my car, the Nexus discharges faster than standard car charger (5V 1mA) can charge it.

Maybe fast USB charge would solve that?
[Samsung Galaxy Nexus] schizophrenia:
i am with you..

agree on what you do

thats called benchmarking
[Samsung Galaxy Nexus] Ruxin:
+1

Hit the thanks button on the original post as it's appreciated the work being put in to show some figures that may be helpful to people using the kernel.
[Samsung Galaxy Nexus] drawde40599:
No its a 100% waste of time, how is controlled testing better than real life?? Then using a kernel that's " expired " and missing major Linux android updates? U guys r so.worried about ur freaking battery its crazy just blows my mind LOOK MY PHONE STILL HAS 60% after 20 hours of not using it WOW!!! So.impressive . Try this one install a kernel use it threw more than one freaking battery cycle in your day to.day life, maybe 3 days or so ( I no i no its a long time ) then install the next one do.same thing and guess what???? U will no if its better or not because u had some real personal data to compare to! That would be 100% different from a controlled test . If the guy up there wants to test for his own personal use great but its usless for any one else .if he wants post his results great he can do what he wants Every phone is different from the screen to the battery that's y some guys get 2 hours some get 5 so u could do same exact test and u 2 would have diff results . . Ok by , I'm bored with this
[Samsung Galaxy Nexus] celyst:
I would search this thread, but it's a bit hard to search for the keywords :confused:

Why isn't hotplug governor recommended?

Number 3 is too troublesome :eek:

Hmm mine is currently running 5 hours and 10% gone... looks good :)
[Samsung Galaxy Nexus] franciscofranco:
Please continue with the tests, they are useful :)
[Samsung Galaxy Nexus] raubkatze:
You misunderstood me. I know what stress test is. But when I tested my device with stock battery it worked more then 3 hours. I think 2,5 hour is too few so I don't understand what eats the battery in this test.

About stress testing on the whole It's useful post on my mind.
[Samsung Galaxy Nexus] zipredictive:
I think that Those "expired" kernels are very important for Franco.... if stress tests say: kernel number xx1 xxx3 xxx5 are battery friendly under stress tests and xxx2 xxx4 xxx6 drain battery a lot maybe Franco could say "I used in 1 3 and 5 kernel some settings that I haven't put on 2 4 and 6 so those settings are good for battery" I'm not a dev and I don't understand many things about kernel I'm not a pro but I think that those benches are good and helpful
[Samsung Galaxy Nexus] nklenchik:
I'm testing the CM9Plus kernel right now. Can someone be so kind as to tell me the governor settings under the hood of interactive on Franco's M3 or r151? Like the timer, sampling rate...etc :)
[Samsung Galaxy Nexus] Metallice:
Gamma at 6 / 7 should be the new default. Looks so much better. Our screens were too "bright" and this helps a lot.
[Samsung Galaxy Nexus] fcasoli:
franco.Kernel purchased and installed the kernel, Nexus perfect!
[Samsung Galaxy Nexus] franciscofranco:
There!!! Exactly, someone that understands me xD
[Samsung Galaxy Nexus] natious:
Geez, didn't think it would be such a big issue to run with the stability from a milestone with a bit more gpu horse power.

Rather than having the potential instabilities from the extras being tested in the nightlies just to have some extra zoom while gaming.

:)
[Samsung Galaxy Nexus] Metallice:
SirTapir, I don't think running at full brightness is a good idea. All its doing it decreasing the "resolution" (in the scientific sense, not the display) of your results. You should be running on min brightness. Increasing the total battery life in your tests will allow you to notice differences that may otherwise attributed to random error. (AKA greater resolution)
[Samsung Galaxy Nexus] Metallice:
Its not that its a bad idea. Its just been discussed many times before. If you had literally read one or two pages back before posting you would have found this discussion and Franco's input.
[Samsung Galaxy Nexus] SrTapir:
Yepp I'm doing it at minimum, it's specified in the post.. :p (dim level 2 in Liquidsmooth options).
[Samsung Galaxy Nexus] Metallice:
Hey Franco I don't know if you saw my earlier post, but I really think you should take a look at imoseyon's commit for stability purposes if you are going to continue using 192mhz.
[Samsung Galaxy Nexus] Metallice:
My mistake. I just saw that user's post and didn't bother to verify it. Now I feel dumb...

oh and if you plan on doing a fourth test - how about testing out different governors? I see your using interactive, and I'd be very interested in see comparisons to on demand and lazy. Just a thought.