yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Gahh Its Lee:
I sit at 46 under normal every day usage.
[Samsung Galaxy Nexus] Hanny:
2 pages back, i have asked the exactly same question and the answers are there ;)
[Samsung Galaxy Nexus] Metallice:
Yes. Just enter 720mv for 192 in Franco's app and hit apply.
[Samsung Galaxy Nexus] jnr21:
Wow, i have 42c in idle.
[Samsung Galaxy Nexus] tcchuin:
I guess franco either lives in somewhere cool, or he has a powerful airconditioner.

btw, can anyone try to replicate the 300++mv on core?
[Samsung Galaxy Nexus] minooch:
Happy to report that nightly 7 has certainly fixed the battery drain. There is also a possible little surprise ;) you'll have to wait and see I guess :)
[Samsung Galaxy Nexus] irishrally:
tease ... hook it up
[Samsung Galaxy Nexus] winner00:
Looking forward to #7!
[Samsung Galaxy Nexus] GchildT:
Can't wait!

Swyped from my Galaxy Nexus
[Samsung Galaxy Nexus] SoleOfJohn:
I must be an idiot

I just flashed Version #6 and I cant get my flash drive to read on my GN. What am I doing wrong? I'm sure it's something stupid simple, and I've already searched the thread for USB hosting and the 2 pages of results didn't tell me much other than it was disabled and now it's back...
[Samsung Galaxy Nexus] ro_explorer:
How about the cifs and tun modules. Will the insmod stuff be working? I really miss my cloud :)

// sent from my green robot //
[Samsung Galaxy Nexus] jopherr:
Is your cable OTG capable? Make sure that there is 5 pins in the microusb side. I just used my USB thumb drive and USB mouse yesterday and it worked just fine ( I'm using build 6)
[Samsung Galaxy Nexus] SoleOfJohn:
Appears so...
[Samsung Galaxy Nexus] chikimonke:
I have noticed that due to the way the connector sits on the curved edge of the phone there are actually some of my USB cables that won't plug in far enough to register as being plug in. My kindle USB cord works fine, some of the others that I have do not. I have noticed that the plastic bezel around the micro USB connector is a bit big on the cables that don't work, an much smaller profile on the kindle cable and the supplied cable. I bet there's a little interference with your cables housing.
[Samsung Galaxy Nexus] SoleOfJohn:
It goes in the same amount as my charge and sync cables go in... I'm not sure what I'm doing wrong. Is it like the tablets where its called USB drive in the file managers? I have Astro and Root Explorer...
[Samsung Galaxy Nexus] jopherr:
Uhhh yeah. I see your 5 pins. I dunno what to say. I dont think our gnex can read nfts. When my uncle plugged in his nfts formated thumb drive, I couldn't see his contents(but I could read/write on it) I haven't tested fat-32 tho)
[Samsung Galaxy Nexus] Bisazz:
Have you tried using StickMount by chainfire? you'll need it to mount the flash drive once you plug it in, and you'll find the contents in sdcard/usbstick/sda1.

If a mouse/keyboard or whatever doesn't work, then there's a problem with the cable most likely.
[Samsung Galaxy Nexus] SoleOfJohn:
Perhaps exFAT?

---------- Post added at 01:01 AM ---------- Previous post was at 12:58 AM ----------

That's what i was missing was that app. Perfect Thanks a ton! :D!
[Samsung Galaxy Nexus] kjwalker:
Must. Have.

Appreciate your work :)
[Samsung Galaxy Nexus] jopherr:
Hahah I forgot to mention I had this installed
[Samsung Galaxy Nexus] minooch:
Sorry but it's not my work to release, francisco will release it when he's ready
[Samsung Galaxy Nexus] jopherr:
So jelllly
[Samsung Galaxy Nexus] RonnieRuff:
Had one for 2 weeks! Missed ya! (Big grin)

Bounced off a cell tower near you by ICS and my Galaxy Nexus. Zoom Zoom
[Samsung Galaxy Nexus] loudaccord:
in for #7 :)
[Samsung Galaxy Nexus] franciscofranco:
It comes in some hours, got work to do now.
[Samsung Galaxy Nexus] nikosrs4:
is there any possibility for the kernel to handle the battery used by the radio/data when it's in use of course?
[Samsung Galaxy Nexus] dwang:
Ok right, the custom voltage values with smartreflex enabled specifies the ceiling for the voltage calibration.
[Samsung Galaxy Nexus] superbobup:
For anyone who manages the wiki, this is the clearest/simple explanation of SR and UV ever! Thanks Franco
[Samsung Galaxy Nexus] franciscofranco:
Not really, but my device works very well.

Not that I know of.
[Samsung Galaxy Nexus] fatappel:
I sit around 28c or 29c at idle. Using default 384/1228 ondemand settings on 158 kernel. AOKP M5 build. So far so good. Thanks franko.
[Samsung Galaxy Nexus] tcchuin:
franco, i managed to do 300mv++ on core undervolt, is the chipset really able to run on that low voltage?=x
[Samsung Galaxy Nexus] Cutting-TM:
Hey Franco. Any chance to add interactiveX v2 governor? If I understood it right, its a combination of hotplug and interactive governor right?
[Samsung Galaxy Nexus] pongalong:
I idle at ~40c and get to ~70c from streaming music.
[Samsung Galaxy Nexus] dpaine88:
I hang around 40c usually and hit 50 during most gaming, 60-70 during intense benchmarks
[Samsung Galaxy Nexus] giugiu:
Solved cleaning dalvik. Thanks and sorry for the wrong report!

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] schizophrenia:
correct me if I am wrong but your temperature is battery temperature

some members here are referring to the CPU temp, which is something from mid 30C to almost 60C
[Samsung Galaxy Nexus] mistermojorizin:
i know this probably won't happen, but I am throwing it out there anyway - I would really love to have a version that has the 710mv SR'ed in and the lower wifi voltage from the 156 kernel, because i've never had a reboot, screen of death, or wifi drop on any of your kernels, Franco, and would just love to use lower voltage, but let SR increase when it needs to.
[Samsung Galaxy Nexus] :
Which Rom are you on Franco ?

Taptalked by GNexus
[Samsung Galaxy Nexus] superbobup:
You can always set your own voltage for the 192mhz without turning off SR. Don't know about the wifi voltage, but I'm not sure if it would have a tangible difference
[Samsung Galaxy Nexus] dpaine88:
Yea, I wonder if Francos 40C is referring to CPU or Battery
[Samsung Galaxy Nexus] schizophrenia:
likely CPU temp, as displayed in his app
[Samsung Galaxy Nexus] jhericurls:
Anyone have their status bar clock freeze on 158?
[Samsung Galaxy Nexus] dpaine88:
So I had been using Interactive 729-1228 for a while and decided to try OnDemand for the hell of it.

It stays in 700mhs A TON more than interactive ever did!!

Will going between 700-1228 a lot like interactive does hurt the battery life?
[Samsung Galaxy Nexus] mistermojorizin:
setting your own voltage without rutning off SR = capping SR, so it cannot go UP to the voltage it needs to when it needs to ramp up. there is currently no way to change the lower limit of SR, which is what I want. I don't want it capped on the up side. i want to have a lower, lower limit.
[Samsung Galaxy Nexus] CaspaTheGhost:
AOKP?
[Samsung Galaxy Nexus] sruel3216:
i listen to a lot of music and i am struggling to find which gov to use for best battery. i like the cmplus kernel cuz it stays at the lowest frequency while music is playing with screen off. however, i love franco cuz it is the smoothest but in cpu spy the freq always jump around while playing music with screen off. what do you guys recommend?
[Samsung Galaxy Nexus] avetny:
I think 158 is laggy when u swipe between home screens.

Regards.
[Samsung Galaxy Nexus] nklenchik:
Can't reproduce that
[Samsung Galaxy Nexus] jhericurls:
No LiquidSmooth. Had the clock freezing bug when I was on AOKP rom. But not had it again since I moved to Liquid, but just go before after using 158 for a few hours.

Try upping the threshold in Governor controls, I've mine set to 98.
[Samsung Galaxy Nexus] Sveke:
Try setting your min/max to the same while you're listening.

Like 384/384, that should force it to stay.
[Samsung Galaxy Nexus] franciscofranco:
CPU temperature.
[Samsung Galaxy Nexus] sruel3216:
yes im sure that would work but i dont wanna have t do that each time lol

Franco, anyway to lock the lowest freq when the screen is off while listening to music?

thanks
[Samsung Galaxy Nexus] superbobup:
Perhaps I understand SR and your desire incorrectly. Currently, SR is giving you a voltage for 192 that is ABOVE what you need right? If you set a voltage lower than the SR value in the UV table WITHOUT turning SR off, it should simply run at this voltage, right? For instance, your current 192 voltage is 800mv but you want to go down to 750. Place 750 in the UV table and SR should use that value for that slot (since like you said it caps the up side).

However, I don't understand why it would ever ramp up the voltage after it has calibrated it to the SR value...
[Samsung Galaxy Nexus] sruel3216:
yes this works. i just tried it
[Samsung Galaxy Nexus] Metallice:
I'm not sure I understand the second question, but higher frequencies consume more battery and thus, in the case of interactive, ramping up and using max freq more often will consume more battery than not, I.e lazy or on demand.

In practice this difference is small for a couple reasons. For one the battery used by the CPU is not the largest drainer battery, behind the display and even the radios BY A LOT. Finally, there's the "race to idle" (or even race to lower freqs) principle. Even when browsing the web or playing music with the screen off, being able to reach idle faster helps to alleviate some of the battery impact from running higher frequencies. This isn't perfect though, as running lower frequencies for more time will always consume less than high frequencies with more deep sleep. This is due to the fact that power drain is approximately (freq)*(voltage)^2. Because of bthe "squared" part especially, power use vs freq is not a linear relationship, and therefore, proportionally more time in idle cannot overcome the non-proportional, quadratically increasing power cost.

That being said, undervolting, lowering max clock speed, lowering min clock speed, using lazy/ondemand over interactive, and so will all have real befits to battery life, but the benefits may be so minor when compared to the radio,display, uneccesarry wake locks, that it may not be worth the performance costs associated with each, especially when you consider "race to idle".

It all depends on you and what you like and the performance benefts/costs you actually notice.

I PERSONALLY see zero to minimal performance loss when using 192mhz min and when using lazy over ondemand over interactive. So I use them since they will help battery in a small, but real way. However I do see a performance hit when lowering my max clock speed from 1.5ghz so I keep it there. There will be a battery hit, but the small relative battery use of the CPU and the race to idle principle mean its not TOO bad for battery.

Phew!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] CaspaTheGhost:
Interesting that the infamous clock freeze has appeared elsewhere.

As said, up the threshold so it takes more for it to ramp up.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sruel3216:
ok what gov and number do you recommend?
[Samsung Galaxy Nexus] superbobup:
I'm running stock OnDemand 384/1200. I stream all my music through Play Music and it only touches 1228 for a second or two when it has to load a new song
[Samsung Galaxy Nexus] olivercervera:
I am considering to install CM9 on maguro.

(Maybe it's a noob question) Franco Kernel works on CM9?

I think that it's the best ever made for gnexus, and I can't live without it :(
[Samsung Galaxy Nexus] ZiCoN:
I'm running CM9 and Franco.... Running like a dream
[Samsung Galaxy Nexus] fatappel:
Threw you a "thanks" for pointing me in the right direction. I appreciate the help. Kernel 158 is still running great and at a cool 30c for me in idle as you can see below. Hope i got it right this time. Thanks for your work franco.
[Samsung Galaxy Nexus] CaspaTheGhost:
Ondemand is the relevant governor and 80 is the default so I'd experiment from 90 and see how it fairs.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jan-willem3:
Do you guys also notice when you set the max frequency at 384 mhz.

And the min frequency also at 384 mhz that the phone still remains very fast? Like it is not setting the max frequency correctly? Or is the phone really so fast at that frequency.
[Samsung Galaxy Nexus] sing1gnis:
I'm still having WiFi fits on 157. Not getting gtalk messages until I turn the screen on and I notice that my signal is gone. After a few seconds it connects back. Is that a kernel problem? Been running nightlies for a while now and never noticed this issue until 156 and now 157.

1228/729 ondemand hotplug on
[Samsung Galaxy Nexus] sruel3216:
did what you recommended and it seems to help so far. thank you
[Samsung Galaxy Nexus] franciscofranco:
#4.4

* A lot of under the hood changes meant to fix some force closes and overall app stability

* Removed ability to email me and automatically send me dmesg logs - people abused this features, specially the "Log me" one, and I don't want that

* Added a donate me link in the menu option - while this seem like a weird addition I'm only adding it because I got a lot of requests for this in the last months, so there you go

* Added a Kernel support link for the official XDA thread
[Samsung Galaxy Nexus] The Gingerbread Man:
I'd love to see a feature in your app to show time spent in each CPU speed, much like CPU spy.
[Samsung Galaxy Nexus] franciscofranco:
I already thought about it, maybe a widget too. I'll see what I can do.
[Samsung Galaxy Nexus] rmcsc:
You're the man, man. Keep up the great work.

I flashed back to M3 today to last me the day. 158 was too unstable for me (and for others, as I've read). 157 was good. Chose M3 since it's stable and I just need a stable phone at the moment. Too busy to be tinkering around.
[Samsung Galaxy Nexus] BrUhNiGGs:
Yes that would be much better. I don't like installing like 5 different apps to monitor my CPU and battery stats to see what's going on my phone. Would be great to have in all-in-one app which would be yours. Whenever you have the time or ability of course :) thanks for your hard work
[Samsung Galaxy Nexus] franciscofranco:
Unstable? I didn't get any instability report for r158 so far.
[Samsung Galaxy Nexus] nklenchik:
You sure know your stuff. Glad you're here to help everyone out to be honest :P
[Samsung Galaxy Nexus] rmcsc:
It reboot a couple times. Sorry I didn't sent anything, I've been busy today. I'll reinstall 158 and if anything comes up, I'll drop you a logcat. But... wait. If it reboots, the logcat is gone, right? What is it I have to send if it reboots?

Sorry for not reporting anything today. Now I feel like a bad user. :(
[Samsung Galaxy Nexus] mingkee:
On the app "scaling governor" part, which option I should use?

I want a mode closest to stock, or have a good balance between performance and battery life.

I chose "conservative".
[Samsung Galaxy Nexus] FC1032:
Thanks again Franco! Recently clean installed, then went to the latest nightly.

Battery life is as usual impressive (screen shots later). I didn't notice the gamma settings from omap before. Now I tweaked it and I'm getting the nice colours I expect from an amoled screen. Also helps lessen the grainy linen look.

:sly: what sorcery is this?! So glad I got the app.
[Samsung Galaxy Nexus] willl03:
Got a bootloop and lost launcher settings after a restart on r158, had this problem on r152 too, never before

Gonnay try r154 as people seem to like it a lot

By the way, I've got 3h50 screen on time over 16h. Spent half the day on r133 with ondemand 384-1350, the other half on r158 interactive 700-1350. Thats including a bit of time messing in recovery mode, amazing where this kernel has come

Edit: had some very high temps on r154, 45-50*c idle and 60+ when I do something. Back to 158, back to normal
[Samsung Galaxy Nexus] jasonkx:
Franco, there is a problem with your Kernl, it doesnt work with Apple Magic Mouse!
[Samsung Galaxy Nexus] rmcsc:
Dude, duh. Cause this isn't for the Magic Mouse. Flash the iPad one on it, search it up.

Just out of curiosity, what are your settings, Franco? I know you're probably tweaking at every moment but at a "moment of tranquility", what do you use?
[Samsung Galaxy Nexus] jnr21:
nice, but check cpu temp, not battery temp.
[Samsung Galaxy Nexus] jericho7:
the OS responsiveness for me with 158 is insanely good, much better than it has been for a while with some of these nightly builds
[Samsung Galaxy Nexus] jasonkx:
On other kernels the mouse works very well so don't be a fool. Just reporting a bug to the developer.
[Samsung Galaxy Nexus] bigeyes0x0:
You know, I think one should mention "This is not a joke" if they ever mention Apple on this forum. TBH I consider using an Apple product a blasphemy, thus I was contemplating your previous post was a joke or not, and sure someone thought it was.
[Samsung Galaxy Nexus] yungboss22:
Franco, i have a question, when i deactivate Smartreflex, did the core and iva voltages can be undervolted via your app like before with SR on ? Thanks :)

*Edit: Did the core and iva undervolting work with sr off ? :)
[Samsung Galaxy Nexus] inffy:
Any plans to add vibrate control to the kernel and the app. I love the option on glados and trinity.
[Samsung Galaxy Nexus] maisi:
Hi,

anyone else gets tons of those error messages on dmesg?

"

[ 145.654998] omapdss DISPC error: SYNC_LOST, disabling LCD

[ 145.655059] omapdss DISPC error: First SYNC_LOST.. ignoring

"

They always appear when i unlock my screen, i also notice a crackling noise when listening to music.

They don't appear on r142 which was the only older version i had on my phone.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] rmcsc:
Hey, I was just trying to make a light-spirited joke and get a laugh. Cool off.
[Samsung Galaxy Nexus] galakanokis:
Hi Franco

Just wanted to say thanks. I am new to the Galaxy Nexus (came from captivate) and I think your kernel kicks some serious ass! The sleep battery drain is insane. I actually thought my battery indicator was on the fritz as my battery didn't move for nearly two hours.

Just running the M3 as I just don't have time at the moment to play around with the nightlies but that will happen soon.

I just wanted to add that I love your app but a couple of times now I have not been able to down load the nightly kernel. Not a big deal as they are other ways to grab the file but thought I would mention it.
[Samsung Galaxy Nexus] frankyyy02:
Running latest CM9 and nightly 151 was fantastic but just moved to nightly 158 and am seeing the same issue I had with fugu kernel. I am seeing flicker between standard colours and a dark blue sort of overlay. Also laggy when this happens. If I lock the screen again and unlock again all returns to normal but continues intermittently. Its almost like its under powered. When I had the issue with fugu I was told it was due to voltages and tolerances in the hardware. Disabling smart reflex fixes the issue.

Back on nightly 151 and all good.

Is there anything i can do or will i be stuck on 151 now? What would cause it between 151 and 158? Any ideas?

Edit: I am on latest radio and boot loader.

Thanks.
[Samsung Galaxy Nexus] The Gingerbread Man:
R158 I had a random reboot during the night, I suspect it was my fault for trying to under volt 192 to 700mv sr on, interactive.

Now I'm trying 720mv for 192 sr on and conservitive with further undervolting across other speeds
[Samsung Galaxy Nexus] mcdull:
I have flashed 158 and reduce the voltage of 192mhz to 710mV.

No reboot so far. But I have another issue here.

The CPU load keeps high and therefore it stays at 1.3Ghz for quite a long time.

Even it jump to the 192mhz for 0.5s it rise back to 1.3Ghz almost immediately.

I am not sure if it is franco related. And I notice that a process named debuggerd is always at the top of the list that consumes cpu.

Please advise if I can check the process that throw the crash data to debuggerD? Thanks.
[Samsung Galaxy Nexus] lukasb9000:
hi

I never had any problems with the kernel until now: my phone just eent dark and wouldn't let me turn the screen on again neither did holding down the power button to reboot work had to pull battery and after that could only reboot to recovery and from there to android homescreen

was using 157 @ 512; 190 - 1300 ondemand

now I flashed 158 no issues so far
[Samsung Galaxy Nexus] The Gingerbread Man:
I don't know about the 2nd thing but try using a different governor if you wanted to try and keep your CPU at lower speeds. On demand is what Franco seems to be recommending now, I'm using conseritive and not facing any lags.
[Samsung Galaxy Nexus] phunghoang24:
I feel Nightly-151 is the best in my phone. newer version is lag more than too (185), V151 I got 3 days uncharging weekend + 20% battery more.
[Samsung Galaxy Nexus] coolzjai:
test mode: *#*#4636#*#*

Has anyone noticed that in the test mode, the option

"Set preferred network type" had changed from "GSM/CDMA Auto (PRL)" to "WCDMA Preferred"?

Just for personally knowledge, which mod actually take care of this changed?

Would it affect the battery life / connection stability if we set it to diff one?

thanks
[Samsung Galaxy Nexus] AzzaD:
working well on #158 :D
[Samsung Galaxy Nexus] qballe:
+1

similar problem with #154, someone has an idea ?

flashed today 158 but the problem persist.

using wifi, i turn on the monitor and Gtalk is "gray" disconnected .

( no wifi sleeping policy )

help :D
[Samsung Galaxy Nexus] Gahh Its Lee:
Hmmm another SOD last night I don't ever get these and I've been running 192 since you made it available. Any ideas?
[Samsung Galaxy Nexus] franciscofranco:
Whats your voltages?
[Samsung Galaxy Nexus] schizophrenia:
maybe i am one of the few lucky ones?

but I do manually tweaked the voltages a bit but still using SmartReflex ON

So I am on AOKP M5, Franco r158 (512), Ondemand, 192-1344 with Generic Hotplug on.

I am having quite good battery life as of now.

been on 18 hours, screen on 1:31 and with battery 43% left

wifi 99% on

so far no SOD or whatever funny things happened

my UV tweaks as attached.

to most of you my battery life isn't amazing but for me so far this is the best I get out of franco. I used to get no more than 20 hours (on wifi) and at most 2hrs screen on in some early nightlies. For the past few nightly, I was actually getting crappy battery too.

I am sure this time I am beating that without a problem.
[Samsung Galaxy Nexus] Gahh Its Lee:
Stock voltages which confuses me. Happened the last two nights but before that it hasn't in several months.
[Samsung Galaxy Nexus] franciscofranco:
Strange... Use 384mhz and see if the SoD happens again please.
[Samsung Galaxy Nexus] shohratshankar:
I've been using this kernel from the day I bought my phone about a month ago.

Other than a variation in battery life. I have found all builds to be perfect.

I have never had a reboot or Fc.

I just love my phone and especially Franco Kernel.

Was using Aokp, but find better battery life using Liquid. I decided to try it out once Franco started supporting it.

Thanks again Franco. You are a great developer.
[Samsung Galaxy Nexus] tcchuin:
try if you can set 300mv on core UV :D
[Samsung Galaxy Nexus] eriksengh:
Hi Franco.

Have been using this kernel for months now and just love it.

158 runs very well on my phone.

However i noticed something strange today. when using "Increase maximum sound volume" music stops playing after a short time just like it used to for some users back when this feature was new.

Not a big deal, just wanted to mention it :)

Anyway, Thanks for the very best kernel for GN :D:D:D:D
[Samsung Galaxy Nexus] schizophrenia:
153Mhz from 875 to 300? is that really possible? battery lasts longer that way?
[Samsung Galaxy Nexus] BrUhNiGGs:
My heat issues have been gone ever since I uninstalled Facebook for Android, CPUspy, and BetterBatteryStats. Partially was from switching from Liquid to AOKP. Might go to Liquid again to see if there will be any heat issues. If anyone has it, try uninstalling as listed above.
[Samsung Galaxy Nexus] PresPPsP:
Are you on #157? The stock voltage was too low (710mv) for my phone in that build. franco bumped it up to 800mv in #158. I've since uv'd it to 750 without issue.

-Josh