yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] apsis:
@gahh its lee

I can't agree, I have never set uv at boot and if I forget to enable it after an reboot I always recognize higher drain. Without UV I haven't also reached the 4 hour screen on mark with my setup yet, but with UV I most of the time reach it.I guess it depends on how it's under volted and how you gonna compare it. For me the benefits are significant and there's no negative aspect by undervolting the device, it's just some extra juice for my device.but everybody for his likes, but in my opinion the 2% statement is absolutely faulty. Btw I'm on the latest nightly now for 5 hours, first half of the time the device wasn't undervolted to see if sod's appear, since the half of the time i undervolted to my desired settings and if I do take a closer look to the Android battery graph ,I can already see that in the first half at screen on there was a higher drain, the graph on the screen on time in the second half is even more flat .and down to almost 50% now, I already have 2:50 screen on time. I absolutely like the benefits of undervolting. And my screen brightness btw is set to static.

To franco

Thx for setting kernel back to the famous r66, with your latest nightly I haven't had any sod now (knock on wood). It's great how fast you are reacting on comment's here, and problems with your kernel's have been sorted out that fast.

Great work

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] mistermojorizin:
what are your undervolt settings?
[Samsung Galaxy Nexus] chadouming:
Well, i do remember that i read something about that and the gain achieved by UV is not major. Tho it might be a bit more than 2%, i would doubt it cut the drain by more than 6-7%. We would need to do a lot of testing to know who is right. I personnaly keep undervolting even tho i know it doesnt change a lot. For the negative aspect, as long as we give enough power for the device to reliably work, it should not have bad effect on it.
[Samsung Galaxy Nexus] M3drvr:
How about experimenting with a 512+ gpu oc? Like 850 or something

By the way, is the reason for the new CPU frequencies because of the 5% bus over clock? Or is that still incorporated?
[Samsung Galaxy Nexus] mikeandjaimie:
Hey Franco, just purchased the app finally yesterday and loving it, but with 96, 1382 starts severely choking my phone every couple seconds, like it took me almost 25 seconds and countless tries to swipe through the app tabs. Switching back down a step fixes it, but then your not oc. 1350 ran flawless for me on 94 though. Any possible causes? Using hotplug, sounds tweak and wifi in settings with ondemand and default voltage..
[Samsung Galaxy Nexus] fzpb61:
I've always left the UV settings stock. I want to try some other settings to see if my battery time increased like others have stated. What are you guys setting your UV values to?
[Samsung Galaxy Nexus] nitrox1:
Are you able to go lower, at the 700&1000MHz steps? Or do you start you get freezes?

Also when you look in Franco's app, do you ever look at the voltages and see mpu jump from 725mV, to 0?

I always get freezes below 800@350mhz.

Swyped from my tuna surprise with extra crispy bacon.
[Samsung Galaxy Nexus] ArmanUV:
Someone did it for Nexus S:

http://xdaforums.com/showthread.php?p=22126792#post22126792

Note that nexus s doesn't have any dynamic voltage calibrations like smartreflex (afaik) and its screen is smaller and therefore less power hungry. So if it was really 2% for nexus s, it would be practically nothing for our phone.
[Samsung Galaxy Nexus] hawkye:
That was odd, r96 put me in a bootloop. I couldn't go back to r94 or any of the earlier kernels. I was using the franco governor. I wonder if that was my issue. I should have changed it to OnDemand before I flashed r96. I am reflashing my Axiom Crossbreed ROM again to see if I can get it to boot.
[Samsung Galaxy Nexus] hasnol143:
Id like to know what setting you use?
[Samsung Galaxy Nexus] Serious_Beans:
Still hearing the popping sound, without ezekeels sound hack. Aokp m4 and nightly 96
[Samsung Galaxy Nexus] momomok:
Same here, very annoying
[Samsung Galaxy Nexus] ramerco:
Yes it undervolts on its own, but UV settings can set the limits.

For example the range for process speed 1200 might be 1300 to 1400 mv. System goes to 1300 mv at the lowest. If you set UV for 1200 at 1250 mv then you save power. Simple as that. Of course, too low and you'll get reboots.

I use 810, 975, 1075, 1150, and 1200 for 350-1350. I have notice that 1200 and 1350 seem to us the same voltage (from what is set in 1350) no matter what I set in 1200.

You can now check ur current voltage in Franco's app. Set to static clock speed and the check voltage.

Would be a great feature if voltage showed clock speed next to it :D. Francisco? Maybe?
[Samsung Galaxy Nexus] franciscofranco:
Very good idea, I thought about that earlier but forgot, thanks for the reminder.
[Samsung Galaxy Nexus] nklenchik:
I bet the best battery with the stock voltages to be honest. If I UV I feel like my phone's working harder with the voltage given to do what it has to
[Samsung Galaxy Nexus] jenarelJAM:
Bug Report

Not sure if you've already caught and fixed this in your nightly builds, but I was using milestone build # 1 and something to do with your volume modification breaks the ability for Tasker to set the volume.

I was running AOKP milestone 4 with Franco milestone 1. I just reflashed AOKP milestone 4 to get the default kernel and Tasker can set my volumes again.
[Samsung Galaxy Nexus] fzpb61:
Yes...this would be great. I notice it says my CPU voltage is 1050mV, yet that isn't one of the settings I have in the UV settings. So the phone must be doing something on its own???

Also, if the voltage is too low and the phone freezes, are they reset to stock when it reboots? Just don't want to set it to something and then not be able to get out of it! Thanks!
[Samsung Galaxy Nexus] franciscofranco:
UV settings NEVER load on boot for security purposes.

r97 is out. Only fix is the decrease of 1382mhz to 1344mhz since having that much was causing lag issues on some devices.
[Samsung Galaxy Nexus] Serious_Beans:
going to do anything about the popping?
[Samsung Galaxy Nexus] fzpb61:
Thanks...sorry if that was a noob question.
[Samsung Galaxy Nexus] vomer:
eagerly awaiting 384 gpu version :D
[Samsung Galaxy Nexus] rabhw:
Just a small bug report for the app. It seems like when awaking the phone from sleep after having launched the app before it went to sleep, the app doesn't display the latest build info. The fix is to go back to homescreen, kill the app via the task switcher, then re-launch the app and it refreshes the latest builds.

I'm not sure if it's a matter of sleep, or whether it's from multitasking that something gets pushed out of memory, but yeah. Just fyi!
[Samsung Galaxy Nexus] nccu_eagles:
Damn it, I just flashed #94 a couple hours ago now #97 is out? :confused:
[Samsung Galaxy Nexus] ChongoDroid:
Hehe its always a good thing
[Samsung Galaxy Nexus] fzpb61:
I have this happen as well. App won't tell me what the latest versions are like it can't communicate to server or just doesn't. I use the same method to get them to show again. Just feedback..not a big deal.
[Samsung Galaxy Nexus] franciscofranco:
Yep thats how Android manages activities. I don't even know what is the method I need to re-implement for that, I only use onResume, onPause and onDestroy and I thought those were enough.
[Samsung Galaxy Nexus] CaspaTheGhost:
Has Ezekeel issued a fix then?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Serious_Beans:
So it's just Ezekeels sound mod that is causing it? Didn't know since I didn't have it on, if Franco didn't implement it guess not lol.
[Samsung Galaxy Nexus] vomer:
I looked back and it seems like it started around r94. Maybe franco can "roll back" that change?

The sound makes me cringe lol. Feels like it is damaging something (probably is not but still lol).
[Samsung Galaxy Nexus] kanemari:
using #96 with clean modaco IR12 4.0.4 rom.

im consistently getting better performance on benchmarking tools limiting the upper cpu step to 1228 rather than 1382. for some reason it gets really choppy and the cpu integer and floating point benchmarks drop like crazy. it gets a bit better adding more voltage but its not exactly comprehensive, and still worse overall. i get a difference between 6400 (with 1228 max) and 4063 (with 1382 max) benchmark ranking with antutu.

the popping sound seems to have disappeared. i was getting them at the beginning and the end of calls. it almost sounded like a temporary volume increase because when i was playing music and made a call, the music volume jumped and cut out, then did the same once the call ended when it started playing again. but if the music was off it just made a pop sound, which im assuming was the same thing.

but having overall excellent results so far using min-729 max-1228 undervolted to 900 and 1075, with auto brightness off and approx 30-40% brightness static.

also, i find that i get better results turning the high quality audio off and using the DSP Manager equalizer from CM9 to adjust levels. high quality on gives better ambiance listening to classical FLACs with good headphones, but streaming 256kb RnB mp3s from google music using earbuds doesnt need that kind of quality and i lose too much loudness that is needed in public places because of the background noise.

my 5c worth.
[Samsung Galaxy Nexus] Dubai.xda:
Mate what about having the dots after opening the galary
[Samsung Galaxy Nexus] vomer:
I am guessing we have to wait till he releases the 384 GPU version.
[Samsung Galaxy Nexus] nodstuff:
If I use r89 which I think has the live gpu oc, how would I go about setting it to 384 instead of 307 without using the app??

What script would I have to write?
[Samsung Galaxy Nexus] mazubo:
As an honest recommendation, I highly recommend his app for tuning the kernel. It's the same cost as a coffee, but value wise its the size of a football field!
[Samsung Galaxy Nexus] sishgupta:
In my home country the app is about the cost of a bag of rice but easily worth the value of an elephant, two cattle, and 6 sheep.
[Samsung Galaxy Nexus] mazubo:
I like your comparison better! You cannot have enough sheep! :D
[Samsung Galaxy Nexus] nodstuff:
I have the app, I've had it since I got the phone!!

The most recent update removed the live gpu settings from the app!

They aren't there anymore but I found the script anyway and its working fine so all is good again! ;)
[Samsung Galaxy Nexus] mazubo:
Cool cool! I should have read into it a bit more..... the option to update gpu on the fly is dooooooope! That's some Franco Swaggger for ya! I'm glad you were able to find the script! Cheers!!
[Samsung Galaxy Nexus] KLUVJ:
HERE's a battery update for 96. which is identical to 97. i even tangoed for half an hour. SUPER HEAVY USAGE went from 87 to 3 in 5 hours with 3.25h screen on time
[Samsung Galaxy Nexus] irishrally:
Lots of good information there. Thanks for link.
[Samsung Galaxy Nexus] apsis:
I use the same values that were posted here:

http://xdaforums.com/showthread.php?p=23628823

And I'm running ondemand @ 384-1200mHz.absolutely no problems so far. But possibility of using UV is always device independent.you should always try on your own and lower them in 25mV steps. I just used then to have a new point to start at with the next frequencies. Maybe I will update my older values later. I always do some heavy UV (+25/+50mV from getting reboot's or sod's).

So far the values are working great, no issues so far on my device. It looked very promising yesterday, so I'm gonna keep them for the day and maybe will drop them down some more later.

I know that smart reflex UV's my device on it's own, but it will never get as deep as my undervolt (you can see it in the live oc section).

And it's more than just 6% battery drain that is saved, it's more like if you use your device it all over uses less power, which gives me better on screen times with a total from +1 hour on total some times. To me, I always can see it's benefits clearly. if you need some testing, feel free to do so. But I will stick with uv

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] stupidslow02gt:
What do you guys think about this:

I'd say also delete everything in system/etc/init.d + wipe cache & dalvik.

They are saying stuff in that folder can carry over from kernel flashes. I've flashed a million kernels and have never emptied that folder. Is there some truth to this? I'm getting ready to flash back to Franco because I need to do some testing, so I need to know if I have to empty this folder. Also is Franco nightlies still using an OC gpu?
[Samsung Galaxy Nexus] raubkatze:
Last night with r96

1228

384

ondemand

Hotplug Mod

And flashing r97 now... it is like a drug to flash new nightly)))

Waiting for nightly with 384 GPU to try it.
[Samsung Galaxy Nexus] kanemari:
that new kernel (#97) did the trick... the CPU step change to 1344 max (undervolted to 1275) has benchmarked at 6950 (increased from 4063).

all other settings the same as my previous post.

and yes, i know benchmarks aren't that useful for usability and user experience, but when the user experience is consistently this good, you need numbers as a quantitative comparison in my opinion.

but without a doubt, increasing the minimum CPU step to 700 has made multitasking, screen waking, and usability during app installs and other high IO activities (which happens a lot when reinstalling your apps to a clean rom) so much more fluid there is no comparison. if you arent undervolting and running 350 as the minimum CPU step, why not undervolt and use 700 as the minimum instead?
[Samsung Galaxy Nexus] clefster:
What about if you never check automatically, but put a button that checks for updates. When it's checking, the 'latest version' part is replaced with a waiting indicator of some sort so we know it's checking. right now you don't know if it's updating, or waiting, or what.
[Samsung Galaxy Nexus] stupidslow02gt:
How much screen on time did you have with these results? Is r96 the OC 516 GPU?
[Samsung Galaxy Nexus] Niksko:
Having major issues. Not sure if it's related to the kernel, but the only thing I've changed in the last few days has been the kernel. Flashed a nightly (r93 I think) and this afternoon I became stuck on the boot animation.

I've factory reset, wiped dalvik, reflashed Modaco's IR12, not reflashed IR12, reflashed IR12 with an older kernel (17.2) and so far nothing has pulled me out of the boot animation loop.

It's really really frustrating. I know it's not bricked, but then again, nothing is working.

Any suggestions?
[Samsung Galaxy Nexus] kiwi45:
Same for me..gone back to r89.
[Samsung Galaxy Nexus] raubkatze:
r96, r97 with 512

Screen Time on 48m 56s
[Samsung Galaxy Nexus] johno168:
This kernel and the franco updater app runs like a beast. Speed and battery life is great. One issue, i noticed yesterday. I had re-download all my game data for Modern Combat 3 (in which i lost progress) (700mb), GTA III (also lost game save data) (370MB) and Need for speed hot pursuit (400mb). I checked the cleaner script inside the zip and found it actually clears dalvik cache in both cache and data. Is there a way to easily restore the data or at least prevent the deletion of my game data? Thanks in advance.
[Samsung Galaxy Nexus] Niksko:
Did you solve the problem? By flashing back to an older kernel?

I've tried flashing back to #17.1 which is ancient compared to what we're at now, but nothing will get me out of the boot animation loop.
[Samsung Galaxy Nexus] raubkatze:
Did you try flashing other custom or stock roms?

Try:

1. wipe cache partition

2. wipe data/factory reset

3. flash rom

4. flash kernel

5. reboot
[Samsung Galaxy Nexus] kiwi45:
Yep, r89 is the last stable version for me as the GPU is not overclocked by default.
[Samsung Galaxy Nexus] Niksko:
Are you able to give me a link to r89?
[Samsung Galaxy Nexus] the_jako:
Waiting for nightly with 384 GPU too... I have a lot of problems with the GPU overclocked...
[Samsung Galaxy Nexus] Wanya79:
On which Level stands the Sound Volume Hack by default in Franco's Kernel? or is it disabled by default?
[Samsung Galaxy Nexus] johno168:
Bump
[Samsung Galaxy Nexus] Diger36:
See the first post of the OP... There's a download link.
[Samsung Galaxy Nexus] raubkatze:
First post
[Samsung Galaxy Nexus] Niksko:
Cheers. I just assumed there weren't official links to it because I couldn't find any on Franco's website.
[Samsung Galaxy Nexus] raubkatze:
Have no problem with 512 but really want to try it)
[Samsung Galaxy Nexus] kanemari:
one complaint.. notification sounds keep resetting the max volume boost back to zero if music is playing. it seems to switch itself back if the music is stopped for a few seconds and restarted, but if music isn't stopped it just plays at the lower volume unless you reapply in the kernel app. is there a way to automatically reapply the boost after a notification sound event finishes? or apply the same boost to all system sounds instead of just media? (if that's how it works?)

this isn't an issue with this version only. its always happened to me since the hack was implemented.
[Samsung Galaxy Nexus] kecinzer:
To fix popping sound problem simply turn on High-performance audio :) (by Ezekeel advice).
[Samsung Galaxy Nexus] Niksko:
Ok. I downloaded the latest ROM from Modaco, and then I flashed r89. No dice.

I've gotten a logcat though. Perhaps somebody in the know will be able to interpret it.

Next step is to download the stock ROM and give that a go.

Link to the paste of my catlog

EDIT: Oops, that's not the whole log. I'll update in a minute with the full one, from boot to a little while into the animation loop.

EDIT2: Fixed
[Samsung Galaxy Nexus] tophernuts:
Just in case anyone was wondering, the galaxy note kernal works fine on a gnexus. I just gogled xda Franco kernal saw the galaxy and downloaded it haha
[Samsung Galaxy Nexus] raubkatze:
Try to flash AOKP M4 - really stable rom.
[Samsung Galaxy Nexus] aPiso:
With AOKP M4 and franco my phone restarted while I was browsing and got in a bootloop for no reason. Now I'm on MoDaCo and seems fine.
[Samsung Galaxy Nexus] :
Hi,

Thank you very much,indeed it works perfect:)

Not thought of that ;)

:)

Francisco about the previous nightly (r96):

As other people had this problem too,it was caused by what?

Just to know :)

Because with r96 at 729Mhz-1.38Ghz and LiquidSmooth rom it was awesome,very very fast!

There really was a difference with the previous nightlys in term of UI...

The best expect the lockscreen issue...
[Samsung Galaxy Nexus] raubkatze:
I had no such problem on AOKP M4 + Franco's from M1 till the latest nightly.

---------- Post added at 12:57 PM ---------- Previous post was at 12:52 PM ----------

3 hours after flashing r97 - looks very good
[Samsung Galaxy Nexus] viskas:
ciao francisco!

I've been using for nearly a week now AOKP M4 with your kernel M1, as I previously wrote I have a worse battery drain but I see from BBS that partial wavelocks come from "google services".

I assume I have to exclude the kernel as a reason for that. Am I right? thank you!

keep up with your great job!
[Samsung Galaxy Nexus] Elganja:
can confirm this works for me as well
[Samsung Galaxy Nexus] Niksko:
Ok. Tried to flash yaku-icl53f, I get up to Installing update, and then "Installation aborted".

Any hints?
[Samsung Galaxy Nexus] arvylas:
Franco: Battery life doesn't seem so good for me. I had the same problem with previous nightlies after r64. you have reverted a patch from 64 to 66 if im correct so this didn't work for me! The rest are perfect.
[Samsung Galaxy Nexus] raubkatze:
I wrote above:

And no dalvik wipe. Just cache and data.
[Samsung Galaxy Nexus] Niksko:
Thanks for your help. This still doesn't work. I wiped the cache, then wiped data/factory reset, then tried to flash the stock yakju. The result is:

Installing: /sdcard/<filepath and name>

Finding update package...

Opening update package...

Installing update...

Installation aborted.

And the background image changes to one of an android with its belly open with a red triangle with an exclamation mark in the middle hovering above.
[Samsung Galaxy Nexus] danielvc:
try to install a different rom, not stock yakju. I think it has something to do with root vs. stock.
[Samsung Galaxy Nexus] raubkatze:
Hmm

Do you have backup your own stock rom?

---------- Post added at 02:20 PM ---------- Previous post was at 02:11 PM ----------

Same here. I wrote about it and proposed to flash AOKP as I have no problem with AOKP+franco.Kernel
[Samsung Galaxy Nexus] hosmsdos:
Still having popping sound in build 97 going back to milestone
[Samsung Galaxy Nexus] vomer:
Cannot see this setting.... Where is it located/ what app to use?
[Samsung Galaxy Nexus] fdxgnd:
I have 4.0.3 as well. I wanna test
[Samsung Galaxy Nexus] dantheman_:
ME too!

Running 4.0.3 on my GSM nexus.
[Samsung Galaxy Nexus] franciscofranco:
I dont need anymore to test LTE version thanks. Nightlies might come sooner than wednesday as progress has been faster than I imagined.
[Samsung Galaxy Nexus] franciscofranco:
First nightly is up and running. Enjoy the first awesomeness, more to come!
[Samsung Galaxy Nexus] rabhw:
Looks like an awesome build Franco, I wish ARHD would be on 4.0.3 so I could use it.
[Samsung Galaxy Nexus] DebauchedSloth:
Awesome kernel. Very, very stable and quick!
[Samsung Galaxy Nexus] energie:
hi Franco i'm going to try your kernel.

I would ask the deep sleep entering freq, do you kernel have a deep sleep profile?

could it be of any use create a deep sleep profile with 350mhz powersave?

Whats the default deep profile freq?

thanks
[Samsung Galaxy Nexus] Shetlander:
Congrtaulations on a brilliant kernel. I am using the 4.0.3 ROM from bigxie and with this kernel it flies. I would be interested to try this with a 1.35Ghz oc and GPU overclock. Probably leave the SGS2 by the roadside!
[Samsung Galaxy Nexus] sluflyer06:
Running the same combo, fast and smooth so far, haven't ran into any bugs.
[Samsung Galaxy Nexus] yyz71:
Been running 4.0.3 since this morning and I'm jumping on this kernel right now thanks :)
[Samsung Galaxy Nexus] franciscofranco:
No, not sleep profiles, they are not good, and it only ****s your battery, just leave it be.
[Samsung Galaxy Nexus] energie:
perfect, thanks.

waiting for some UV :D

Great performances :)

Lets see battery!:p
[Samsung Galaxy Nexus] nicandris:
emmmm what 4.0.3 rom do you guys use on the GSM nexus?
[Samsung Galaxy Nexus] franciscofranco:
http://xdaforums.com/showthread.php?t=1399238
[Samsung Galaxy Nexus] sluflyer06:
Speaking of performance by SD reads are just awesome with this kernel 32.6MB/s. Database I/O and SD speeds got pretty horrendous with 4.0.2and.0.3 without this kernel...all is great now and the speed is noticeable with today's kernel.
[Samsung Galaxy Nexus] flakz0r:
OMG I FLASHED THIS ON 402 AND NOW I BRICKED MY PHONE :eek:

just kidding, good job man :)
[Samsung Galaxy Nexus] Mikey:
So it is compatible with LTE devices also??

So i can copy this thread over too the CDMA section???

​
[Samsung Galaxy Nexus] nicandris:
that's what the dev said
[Samsung Galaxy Nexus] mohitrocks:
Hey fancisco,

I wanted to know if you would make an overclocked variant of this rom? I would really like to have an overclocked GPU + CPU since it worked so nicely for me on the last build
[Samsung Galaxy Nexus] minooch:
As stated previously, it is not a top priority. Currently we're running nightlies, *maybe* in the future
[Samsung Galaxy Nexus] raubkatze:
In franco.Kernel Updater app on Settings tab > Turn high performance sound
[Samsung Galaxy Nexus] Niksko:
I do have a nandroid from about a month ago. At this stage I just want something that works, regardless of what it is.

In my infinite wisdom (really just to save space which I thought I'd need), I copied the last nandroid I made from my sdcard onto my pc, and then deleted it from the sdcard.

I'm not trying to push it back on with adb, but the largest file seems to not want to go back on.

I'll download AOKP and give that a go too.

Thanks again for all the suggestions.
[Samsung Galaxy Nexus] stellaryt:
When end a call there is a strange noise from the handset with r97.Does anybody have the same issue?