yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] brianisme:
Yep that is with actual usage. Don't get me wrong, I am extremely pleased with that :)
[Samsung Galaxy Nexus] bendirkss:
I have had lockscreen lag on every rom I have ran besides stock. And I have always used this kernel, any ideas?
[Samsung Galaxy Nexus] drawde40599:
That's about what I get, with NO tweaking, screen 80%, GPS, data, sync ....I've tried tweaking, this and that and this, and its pretty pointless in my opinion, I actually get worse battery no.matter how little or lot . I figure Franco has everything set to be the best its going to so y mess with it . So 4 hours with this big ass screen, is as good or better than my other 12 android phones ....
[Samsung Galaxy Nexus] dreamz0r:
This kernel gave my phone a significant boost, keep ut the good work!
[Samsung Galaxy Nexus] houzuoguo:
Wanna save some battery?

Have a look at this, my experience on undervolting my Nexus using Franco kernel:

Red - system not stable

Green - system stable and runs without any crash

https://docs.google.com/spreadsheet/ccc?key=0Ah8PsMa_NqfedC1sZjhWUkNCRHJHeWNOS1RzU1NUNEE
[Samsung Galaxy Nexus] TheInVisibleGoD:
Even a squirrel is unable to do it... :p
[Samsung Galaxy Nexus] kevinngck1:
Thanks! Trying this
[Samsung Galaxy Nexus] nklenchik:
Thanks man, I upped each of those values by 25 just to be safe :D
[Samsung Galaxy Nexus] BrUhNiGGs:
My phone froze with the given values on green. I'm going to up each value by 25mhz and see how it goes.

Btw, what's are some good values for governor control on interactive gov? I have no idea what to input using Franco's app.
[Samsung Galaxy Nexus] BryanChung:
Same here. I upped the values by 25. :D
[Samsung Galaxy Nexus] arshad14:
I tried those voltage settings on Interactive with Franco's kernel. Let's see if I get any freezes. So far for the past hour I didn't have any issues. A game like Draw Something, which is known to crash a lot of phones 'cause it seems to be heavy also ran smoothly. I'll be able to report back tomorrow 'cause I want to see if I get BSOD.
[Samsung Galaxy Nexus] BrUhNiGGs:
Mine froze within 5 min from trying to type in tapatalk. But so far so good with every value increased by 25mhz. :D
[Samsung Galaxy Nexus] arshad14:
Any ideas which one is more recommended for governors? Interactive or HotPlug? 'Cause according to the changelog, r143 has some added improvements to the Interactive governor for OMAP 3.0. What do you guys recommend, and I'm asking from a battery saving perspective followed by performance.

Edit: Running a Stress test on my phone now with the new change with the interactive governor and the new UV settings recommended above. So far with over 6 minutes of stress test, no errors on the CPU or GPU.
[Samsung Galaxy Nexus] stellaryt:
His green value is safe for me,some of value which I seted is lower than his.

But hardware have different "physique",so just try urself and you will know which is for you:)
[Samsung Galaxy Nexus] joeyfong:
Updater is updated.
[Samsung Galaxy Nexus] blitz911:
Incredible battery life on 143. My battery was in my locker at work with 98% battery..6 hours later, it's at 93%..I'm using Interactive governor, 384-1228, generic hot plug on, smart reflex on, stock rom. I've never gotten that small of a drain from any kernel..Just incredible..oh and the rest of the time its just blazingly smooth...thanks a million:thumbup:
[Samsung Galaxy Nexus] drawde40599:
Not to say it won't work, or help, but its been proven over and over agn messing with voltages dose basically nothing, 143 been out for what a lil over a day?? So no one here even Nos how good stock settings r yet ... so what u going compare to? 1 day of running the kernel? Makes no sense

MY OPINION!!!!! Yell at me if u want: )
[Samsung Galaxy Nexus] jnr21:
Just passed antutu and quatrant benchmarks with your cpu uv settings without any crash. Thanks.
[Samsung Galaxy Nexus] atsavlis:
Do you run these numbers with smartreflex off??
[Samsung Galaxy Nexus] nklenchik:
Smartflex will adjust to those settings I believe
[Samsung Galaxy Nexus] bat0nas:
I don't know how you guys.. but I don't feel any effect changing those values.

I setill need to charge my phone each night after MUCH less than 20h of standby and less than 2h of screen time.

:D

Maybe changing MHz or any other value saves few minutes, it doesn't make much of the sense. You still need to charge it overnight.

And I didn't see any significant difference between stock kernel and franco. I bet there's a difference (thousands of people just can't be wrong!), but it's not seen by me.

I will keep experimenting for some time with the settings I see people are happy. Let us see how it goes.
[Samsung Galaxy Nexus] houzuoguo:
Using the fixed voltage settings on different nightlies have shown no difference to me so far. The figures were not made in one day - I've been experimenting with the voltage settings in the past week and collect results. On my phone it has shown 6% (of 100%) decrease in battery usage - not much, but quite noticeable ;)
[Samsung Galaxy Nexus] raubkatze:
Thanks for posting your experience. But I remember (correct me if I'm wrong) Franco wrote it's no good idea to use generic hotplug with hotplug governor because this governor already has dynamic hotplug.
[Samsung Galaxy Nexus] tixed:
Kernel crashed again (and rebooted), in the same situation. I'm trying to send you crashlog, but nothing happens (gmail window with log don't pop out).

The situation is:

- watching some video in DicePlayer;

- homescreen, trying to load playlist for Play Music from widget;

- reboot.

Can't reproduce that 100%, will try to do it though. Also, reboot was pretty fast - without google logo stage (started from your kernel boot anim). Could resend you crash log from the first time, if you need it.
[Samsung Galaxy Nexus] raubkatze:
Use CatLog to grab log.
[Samsung Galaxy Nexus] tixed:
Hmm, what info from there would be useful? I'm not very familiar with android programming and structure... Maybe I should filter something.
[Samsung Galaxy Nexus] bigeyes0x0:
If you phone hot reboot I think you can pull /proc/last_kmsg and past the content to pastebin.com for franco to check.
[Samsung Galaxy Nexus] drawde40599:
That's all I'm saying the tweaking is not worth it, 6% is 15 min on a charger, unless u have no access to a charger its not worth it and even then ...., and I'd say 90% of us have a charger at home, work, and car, I look at it like this, Franco spends hours and hours messing, tweaking, developing his kernel, if there was something better he would do it ....

---------- Post added at 12:21 AM ---------- Previous post was at 12:19 AM ----------

R u running 100% stock settings?
[Samsung Galaxy Nexus] raubkatze:
Yes, I really forgot about it. It's the best way.
[Samsung Galaxy Nexus] drawde40599:
I flashed the stock 4.0.4 image when it came out just to check it out I ran it for two days, I got 2.5 hours screen on time both days, I get avg of 4 with Franco, if u can't feel the speed difference between Franco and stock kernel using stock settings ur phone is broken and u should send in for warranty
[Samsung Galaxy Nexus] tixed:
Depends on what you mean by 'stock'. The only thing I've changed in kernel settings were slight OC and some features like SQlite defrag, fast USB charge, etc. No UV or any other 'dangerous' tweaks. Kernel is nightly 143, btw.

If every setting is important - I could list them all.

Got it, give me URL to his pastebin profile pls (can't find it in his sig).
[Samsung Galaxy Nexus] drawde40599:
Ya that's what I meant, UV, I no some under volt like crazy then blame the kernel ...... k bye
[Samsung Galaxy Nexus] raubkatze:
He meant cpu freq, cpu uv, iva uv, core uv, governor settings etc.

You can simply paste it and post link here.
[Samsung Galaxy Nexus] tixed:
Oh, ic. Never used it before so wasn't sure what pastebin is :) Think I'd better stick to dropbox, it's what I know better.

http://dl.dropbox.com/u/33093864/last_kmsg

So, to clarify - that was sudden hot reboot, no UV, interactive gov, 729-1344 CPU, generic hotplug on (not sure if that matters - screen was on for a long time anyway, and hotplug switch off one core only if screen is off afaik). Nightly 143.
[Samsung Galaxy Nexus] maisi:
You could try a lower GPU voltage since you are on 384Mhz.

I can go 800-850-900 (153Mhz-307Mhz-384Mhz) without a problem. For 512Mhz i would need around 1050mV.
[Samsung Galaxy Nexus] borneanheadhunter:
No audio in when paired with Bluetooth headphone. Currently on Liquid smooth 1.3 . In nighty 141 it works.
[Samsung Galaxy Nexus] kmso:
should be normal....never see anyone post a picture that is 3g standby whole day with moderately use can get over 3hr screen on time (standard battery)

But the speed is obvious compare with stock kernel i think
[Samsung Galaxy Nexus] relax24:
I'm using the 143 kernel and I was under the assumption that any undervolts you did, SR would take that as the highest possible voltage. Is that correct?

I've undervolted, however in the calibrated voltages section, I see a higher voltage number to the one I set. Am I doing something wrong (maybe not reading this thread properly)
[Samsung Galaxy Nexus] jnr21:
Disable smartreflex.
[Samsung Galaxy Nexus] relax24:
Great thanks.
[Samsung Galaxy Nexus] leelaa:
Hi ive just updated my app, and i see governor control settings,

sampling down factor.

sampling rate.

sampling rate min.

up threshold.

can anybody give me a brief explanation as to what these settings do?

i take it that some performance can be gained from these settings?

maybe i could get some minor settings to start me off?

Edit: i found a thread so its ok.
[Samsung Galaxy Nexus] franciscofranco:
I talked to imoseyon last night and he said even stock kernel from google is crashing so I believe somethings a bit wrong that even we cant figure out, specially because the kernel crash logs are impossible to understand.
[Samsung Galaxy Nexus] siuba:
good job!

do i need to disable smartreflex?

---------- Post added at 08:19 PM ---------- Previous post was at 08:15 PM ----------

i dont think so! my voltage setting never work! still keep on default..
[Samsung Galaxy Nexus] tixed:
Wow. I see. Well, so then it's pretty much useless to send you logs when more similar crashes occur?
[Samsung Galaxy Nexus] franciscofranco:
Sometimes logs are useful sometimes they arent. Just send them.
[Samsung Galaxy Nexus] rovertjoey:
Great work. Phone used to heat up but not anymore!

sent from my bold 9900 running ics
[Samsung Galaxy Nexus] Stretlow:
What's considered normal temp and what's considered overheating, I've got Francos widget but not sure whats normal
[Samsung Galaxy Nexus] franciscofranco:
Overheating is when it starts to throttle, which happens if the CPU reaches 61ºC or more.
[Samsung Galaxy Nexus] leelaa:
Franco this is probably a no brainer, but I just wana make sure.

I am guessing the 512oc will give better frames per second in high end games?
[Samsung Galaxy Nexus] franciscofranco:
Yes you know the answer for that question ;)
[Samsung Galaxy Nexus] brianisme:
Anything in the low-mid 30 degree C range is normal for me. Although I've seen mine go as low as 25 degree C according to the app :confused: Could be the ambient temperature of my metal desk that it is resting on.
[Samsung Galaxy Nexus] momomok:
I doubt if it is kernel-related.

I remember someone here told me that if your phone reboot without going back all the way back Google logo, it is a "soft" reboot, and usually an indication of ROM issue/bad apps.

That was quite a while ago, though (at the time when I was tinkering with IR kernel on my N1).

Sent from my Nexus Prime
[Samsung Galaxy Nexus] albatros_1994:
How can i see that the voltages are applied correctly?SR Off
[Samsung Galaxy Nexus] hotnikkelz:
Whoa

I don't think I EVER got under 40 deg C, and i'm on franco defaults milestone 2. I have dual core on, that's about it I think
[Samsung Galaxy Nexus] Stretlow:
So would the phone be considered "safe" as it were if it runs consistantly at around 40-50?
[Samsung Galaxy Nexus] The Nexus Project:
Been on 143 since it's release. One of the best Franco kernel experiences to date. Performance is solid & battery life is stellar. Overheating problem solved. Great work Franco. You got my vote for best GNEX kernel.:thumbup::cool:

Sent from my i9250 (GSM) Galaxy Nexus.

Phazenine@Twitter
[Samsung Galaxy Nexus] brianisme:
I'm sure ambient temperature will have a lot to do with it. Also, if you have dual core on the whole time, that could most certainly affect the temperature.
[Samsung Galaxy Nexus] Manafa:
Franco, I have very weird problem. When I dial a number from phonebook or dialpad, it takes a lot of time to start dialing - sometimes around 7-8 sec. or more. If I restart the phone, this problem disappear for a while, but start again sooner or later. The problem is harder on On Demand settings and not so bad on Interactive, but stll exist. Never happened on Lazy governor. I'm using Nova launcher and have picture on most of my contacts, if this is matter.
[Samsung Galaxy Nexus] loudaccord:
tried to find the answer to this... but any reason my phone isn't using the 1036 frequency? I have 729min 1228max... for some reason 1344 is being used also though. Interactive gov with generic hotplug enabled.

thanks.

edit: Rom is Liquid 1.3... I looked in performance settings and it reflects the same settings and in my kernel app.
[Samsung Galaxy Nexus] maxpower1985:
Dont know if its kernel related but I had artifacts on homescreen and in google maps this morning.. Exactly like a gpu artifacts..

Whats the problem?
[Samsung Galaxy Nexus] zephiK:
Flash the 384 version of the nightly
[Samsung Galaxy Nexus] jhericurls:
You must be gettings some good battery life with them stats. It all seems fine to me.
[Samsung Galaxy Nexus] Hanny:
hey franco! :D GREETINGS there!!

I know it's abit late but finally, finally I feel so proud to finally follow you here from our O1 home :cool:

just bought ur app, and flashed the kernel, it feels so damn good even before the phone starts!! loll

Thanks in advance the best kernel developer and look forward to test every release with you in the future!! :):)

- your loyal reporter Miasmic
[Samsung Galaxy Nexus] wparkins:
Hey Franco,

Tried your Kernel, loved it so I bought the app.. Not that I plan on to much custom work, I wanted to show support... plus the CPU temp monitoring is nice. Keep up the great work, will report any problems.
[Samsung Galaxy Nexus] bradm23:
Franco,

I have been comparing r141 and 143 a lot and for some reason 141 is a lot smoother when scrolling. With 143, scrolling slowly on web pages, contacts, and home screen has a juddering feel, however its smooth as butter without judder with 141. I know there aren't many patches between the two, what would make this happen?

I tested this with lazy and interactive, default freq, no undervolting.
[Samsung Galaxy Nexus] Hanny:
hispeed_freq in governor control :rolleyes: check few pages back or try to search "1344" :p
[Samsung Galaxy Nexus] loudaccord:
my battery life is okay, just kinda strange that the middle freq isn't being used.
[Samsung Galaxy Nexus] Manafa:
One issue I have noticed. When charging my phone trough wall charger, it's marked as USB charging and it takes a lot of time. If I choose Fast USB charging from Franco's app, then it is stated as AC charging and it's charge normal. Not sure this is kernel or rom related. I'm using Liquidsmooth 1.3 and latest Franco kernel.
[Samsung Galaxy Nexus] psyren:
I think that's ROM related...
[Samsung Galaxy Nexus] Manafa:
Probably. I will post it in there thread, too.
[Samsung Galaxy Nexus] sruel3216:
i get the same thing on lazy gov. 1334 is being used when max is set to 1228
[Samsung Galaxy Nexus] rovertjoey:
My phone was warm to touch. Particularly at the back around the camera area. I've used other kernels and this seems to be the only one that doesn't heat my phone up. Even stock heated my phone.

Don't know the temp again was warm to touch

sent from my bold 9900 running ics
[Samsung Galaxy Nexus] wparkins:
Has anyone had the Franco kernal app fail? Is that Rom, App, Or kernal related.
[Samsung Galaxy Nexus] drawde40599:
fix permissions reboot

---------- Post added at 08:37 AM ---------- Previous post was at 08:29 AM ----------

Its 100% not the rom or the kernel, I have the same same setup mine works fine .... search this thread for reset kernel
[Samsung Galaxy Nexus] bradm23:
The high speed-freq was only for lazy I believe. The choppy scrolling was with lazy and interactive on 143, but was silky smooth on 141... not sure what could of caused this
[Samsung Galaxy Nexus] bmwessen:
Hey franco would you like to come over ti the HTC One X ? Are you planing to Do a Kernel for this device?

Gesendet von meinem HTC One X mit Tapatalk 2
[Samsung Galaxy Nexus] franciscofranco:
hispeed_freq is for interactive.

I have a One X, waiting for HTC to drop the sources. But this is not the place to talk about that.
[Samsung Galaxy Nexus] CaspaTheGhost:
Issue is most likely related to the T9 dialer, not kernel...

Err, GPU OC perhaps?!
[Samsung Galaxy Nexus] jnr21:
I have max cpu set to 1344mhz, but hispeed_freq allways going back to 1228000 after reboot, is this a bug?
[Samsung Galaxy Nexus] krex:
Sorry, maybe it already was but I don't find... Does this kernel include the fix from IMM76I for signal drops issue?

Thanks!
[Samsung Galaxy Nexus] drawde40599:
Yep, be4 Google even released it: )
[Samsung Galaxy Nexus] demon2112:
what signal drops? radio?wifi?

i have signal drops on wifi at work..its a thompson router
[Samsung Galaxy Nexus] jhericurls:
Is thats 3G or wi fi screen time?

I'm just over 2 hours screen time with 46% left and thats 3G only.
[Samsung Galaxy Nexus] bradm23:
Was hispeed freq changed in 143 for interactive also? Can't believe the difference in smoothness between these two. 141 is perfect but 143 is choppy scrolling.
[Samsung Galaxy Nexus] Stretlow:
25% Brightness :rolleyes:
[Samsung Galaxy Nexus] albatros_1994:
i have to do some more tests but my battery last longer with Sr on...with a strong undervolt i have a fast battery drain...it isn't normal...:confused:

My setup:

CPU:800mv-900-1100-1100(384-1228) IVA:800mv-900 CORE:850mv-900-950 (153-384)

Generic Hotplug - interactive
[Samsung Galaxy Nexus] franciscofranco:
Choppy? Not for me.
[Samsung Galaxy Nexus] spinkick:
Not sure why people are trying so hard to under volt. Less stable and very little difference in power. Make sure you have no wake locks and keep the screen off and you are good.
[Samsung Galaxy Nexus] dwang:
What I've noticed w 143 is that it's sometimes smooth and sometimes choppy. 141 seemed to be more consistently smooth to me.

Since you now have a one x maybe u aren't using the gn enough to notice that?
[Samsung Galaxy Nexus] drawde40599:
Are u on liquid Rom?? Cause I noticed this with 142, talked to one of the dev on liquid Rom he recommended turning on the gpu rendering in settings and no more issue for me
[Samsung Galaxy Nexus] paranoid2007:
Wow, this has to be the ultimate way for battery saving. Should be stickied. ;-)

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] dwang:
I wonder if this commit made in 142 could be the cause of the choppiness in 142 and 143. I also tried out the kanged 142 with 512gpu compiled from a somebody on this forum and noticed it was choppier than 141.

https://bitbucket.org/franciscofranco/android-tuna-omap/changeset/f4f4256eeff8

"Sample time 10k like in the other governors and increase the minimum time on each state by 4 sample ticks to reduce the bumping and increase battery life."

Nevermind, that commit was for lazy and I noticed the choppiness on interactive.
[Samsung Galaxy Nexus] franciscofranco:
Can you reproduce that with ondemand?

No I use both devices, I have two sim cards.
[Samsung Galaxy Nexus] dwang:
Let me try. I'm actually testing out leankernel now that it has 512 gpu oc.

Smoother than 143, but not as smooth as 141. :-)
[Samsung Galaxy Nexus] raubkatze:
I'm sure r143 as smooth as r141 and NenaMark2 agreed with me -)

Not too lazy to check:

r143 (512) - 31.6 fps

r141 (512) - 31.6 fps
[Samsung Galaxy Nexus] dwang:
that has nothing to do with it. When you run the tests, the cpu is maxed out.

I suspect that the choppiness seems to be related to the governor not ramping up the cpu speed or maybe ramping it up inconsistently causing overall choppiness.
[Samsung Galaxy Nexus] franciscofranco:
Traitooooor :p

Ok let me know if you try with ondemand. I've been using interactive lately so I dunno how the other governors are acting up.
[Samsung Galaxy Nexus] nklenchik:
Hey Franco what are the stock voltages on 143? I uv'd and I think I'm seeing slower performance

Edit: nvm I rebooted and they're there haha
[Samsung Galaxy Nexus] raubkatze:
And what? I also believe my eyes.

If it doesn't work as you want try out ondemand as Franco wrote. For me r143 works fine.
[Samsung Galaxy Nexus] The Nexus Project:
Have been using"on demand" since release (143).	Butter soft & excellent battery life with :thumbup::cool:stock scaling

Sent from my i9250 (GSM) Galaxy Nexus.

Phazenine@Twitter
[Samsung Galaxy Nexus] drawde40599:
On demand, don't have the choppy build 143, its interactive for me
[Samsung Galaxy Nexus] franciscofranco:
Yep. It should be fixed on M3 since I already had to merge a bunch of patches from googles android-3.0 branch since r143.
[Samsung Galaxy Nexus] leelaa:
I can't wait for milestone 3, feel like a little boy waiting for Christmas :D
[Samsung Galaxy Nexus] CaspaTheGhost:
I've had three freezes on r143, using interactive, 729/1244, SR on, no hot plug.

Couple have happened whilst pressing the home button from my home screen which extends the notification.

Otherwise its been working well, occasional stutter as has been mentioned, but like its most recent predecessors its top notch.

Gonna switch back to Ondemand until the next release, be that rxxx or m3...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Manafa:
What you mean T9? I have problem mainly with my contacts, not the dialpad? I never use T9. And why changing the governor solve the problem?
[Samsung Galaxy Nexus] swiftyy:
I'm on 143 and it won't let me manually set voltages below the SR values.

SR will always show the auto volts. Never had this issue in the 130s roms.
[Samsung Galaxy Nexus] CaspaTheGhost:
Misunderstood, you mentioned contacts and dial pad so I thought you meant the T9 dialer. Do you mean the time it takes to connect once you initiate the call?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Who's ready for Milestone 3?
[Samsung Galaxy Nexus] Gahh Its Lee:
You know we are.
[Samsung Galaxy Nexus] dpaine88:
Me! Me!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] blackdub370:
Gogogogogogo!
[Samsung Galaxy Nexus] raubkatze:
I think everyone and always!)
[Samsung Galaxy Nexus] meilstone:
Just drop it master!!! ;)
[Samsung Galaxy Nexus] Razer(x):
Come on mate! I have to get up early tomorrow :D
[Samsung Galaxy Nexus] kashix:
go go Milestone 3!
[Samsung Galaxy Nexus] mazubo:
We.are.ready.

:-D
[Samsung Galaxy Nexus] nklenchik:
1000x yes
[Samsung Galaxy Nexus] mazubo:
Love it!

:-D
[Samsung Galaxy Nexus] dpaine88:
App says M3 but downloads M2

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Downloads M3 trust me, I just have to update the app to change the Milestone download process to be like the nightlies process and update the filename as it should.