yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Gucci.Nexus:
what do you mean?

---------- Post added at 10:56 PM ---------- Previous post was at 10:50 PM ----------

can you please post a pic of your undervolting numbers... or tell me what you changed them to? my temp is around 95 degrees F. is that high?
[Samsung Galaxy Nexus] Moz007:
I'm sorry to come back to you again but I still can not apply the UV on boot, any ideas ?
[Samsung Galaxy Nexus] nodstuff:
95C is a little high alright, well unless you've been doing a lot of CPU intensive stuff like repeated benchmarks and graphic intensive gaming and so on.

Especially if you are running at 1536mhz.

I find that wheatley causes a lot of heat too due to the fact it keeps the phone at Max speed as much as it can.

I use interactive now and I find it a lot better, I hit 97C on r180 with wheatley and 1536mhz set as Max.

Rarely going over 75-80 now.

The attached voltages work for ME, they may cause reboots for you, every phone has different tolerances.

Derp edit: just realised you said 95F not C.

95F is fine. Mines at 143F right now.
[Samsung Galaxy Nexus] metalspring:
Franco or anyone, do you know what some good interactive governor settings would be to balance out the higher CPU slots? I like the performance of the high speeds but I also want decent battery by having them only used when really needed (like I don't really need to use 1536 slot to open tapatalk lol)

My 1420 and 1536 and 1228 are fairly even but I get almost no time on 1344 (see screenshot)

My current settings are

Above high speed delay- 20000

Boost-0

Go high speed load-90

High speed freq- 1420800

Input boost-0

Min sample time- 10000

Timer rate- 40000
[Samsung Galaxy Nexus] randommmm:
Why wifi_pm setting by bool is better than int? I don't quite understand, anybody can link me some source?
[Samsung Galaxy Nexus] Gucci.Nexus:
Thank you for your help. I will try them. Can you plz tell me your undervolt settings for 384 MHz and 192 MHz? They were cut off from your screen shot.

Cheers

Thanks, using my Gucci Nexus on XDA premium
[Samsung Galaxy Nexus] krex:
Ok, I figured out I don't understand how SR works. :confused:

Can anybody help me that:

- does SR calculate voltages by itself?

- has it any MPU reference table? (which voltage for which speed?)

- why are SR MPU voltages lower than the values we have when it is off? (comparing the CPU undervolt table to current voltages)

- why can SR voltage of 1.3Ghz be lower than 1.2Ghz has? (1230 vs. 1240)

- if you set SR off, how you can check current voltages?

Thanks for answers...
[Samsung Galaxy Nexus] nodstuff:
I don't use 192 or 384. 729 is my min frequency.

You could try 700 for both and see from there but tbh I don't know.

@Francisco: I know this is data from another phone but would it be of any use to us? Its to do with slub memory allocator being better than slab, slqb and slob.

http://xdaforums.com/showthread.php?t=1696284
[Samsung Galaxy Nexus] Metallice:
No. It mainly runs at max frequency. During low latency situations it maxes out the frequency like the performance governor to enter c4 deep idle cpu state quickly, which can happen even when the screen is on and active. Otherwise in high latency situations like gaming it acts like on demand

The goal is the best battery life in all situations.
[Samsung Galaxy Nexus] krex:
When you set new undervolted value and apply, do you see that current value goes to saved value?
[Samsung Galaxy Nexus] nodstuff:
Yes, whatever is shown in saved is shown in current once you hit apply
[Samsung Galaxy Nexus] rogersnm:
This:

Update to r181, r180 has instabilities.

My current voltage levels are:

1536 MHz: 1250 mV
1420 MHz: 1225 mV
1344 MHz: 1175 mV
1228 MHz: 775 mV
1036 MHz: 750 mV
729 MHz: 750 mV
384 MHz: 725 mV
192 MHz: 700 mV

729-1536 MHz is stable and 192-1228 MHz is stable but 192-1344+ seems to crash, even with 192/384 MHz set to the same voltage as 1036 MHz. Given that it should save more power running it at 729 min with these voltage settings compared to 192 min with SR and that it increases the responsiveness, I think I'll just stick with 729-1536 MHz.
[Samsung Galaxy Nexus] krex:
Pls, give advice why doesn't mine do? SR is off...
[Samsung Galaxy Nexus] rogersnm:
This post may be of interest:
[Samsung Galaxy Nexus] krex:
Thanks, yes it is, because I didn't install busybox...
[Samsung Galaxy Nexus] kompressorgpl:
Did this just now! Thanks!!!!
[Samsung Galaxy Nexus] justinjustin234:
i use this voltage setting but when i use SR, the phone crashes. why does it happen?
[Samsung Galaxy Nexus] rogersnm:
I briefly covered that in a previous post, it seems SR takes some reference from your current voltage level when it attempts to calibrate a new voltage level. However because the custom voltage levels are already at their minimum SR leads to instabilities.

People who undervolt should also see this post if they have boot instabilities: http://xdaforums.com/showpost.php?p=27153140&postcount=19050
[Samsung Galaxy Nexus] nodstuff:
UV + SR = No bueno. ;)
[Samsung Galaxy Nexus] krex:
It means, kernel app doesn't reload the default voltage values after an unexpected reboot?
[Samsung Galaxy Nexus] rogersnm:
Nope the kernel app does, however it appears to do it after it applies the voltage values which means there is a split second where you have a significant undervolt and SR on, leading to freezes/crashes. That init.d script runs during the boot animation, 5 or so seconds before the kernel app applies the voltage levels.

Edit: I misread your post. The kernel seems to default back to the default voltage values under certain circumstances. However if you set the voltages to a point where they it's almost stable, but then the phone ends up crashing 10 minutes later, the same voltage levels are reapplied. That init.d script is actually regarding a different issue which is to do with SR turning off too late in the boot process.
[Samsung Galaxy Nexus] dr.sonic:
I have only 90tweaks,is it the same as 98tweaks?

GNex via tt
[Samsung Galaxy Nexus] Meaple:
@franco

A couple, of things have been fixed in your app. Setting your power modes work as intended, creating a custom power mode works as intended but setting a custom power mode doesn't work. Almost there :-)

One little annoying thing is that after you create a custom power mode, the custom settings are still partially set so you have to select another setting first in order to select the same setting. For example, the tick for single core is ticked but you have to untick it then tick it again for it to fully register. It does throughout all of the custom power mode settings.

Posted from my secret spaceship.
[Samsung Galaxy Nexus] rogersnm:
Should be, it doesn't really matter which script you add it to as long as you add it to one of them :)
[Samsung Galaxy Nexus] krex:
Ok, but if it happens, how can I get out of bootloop?
[Samsung Galaxy Nexus] rogersnm:
If your undervolting the 1344 MHz+ levels you can just boot into the stock kernel via fastboot and change the app settings and reboot. If you're changing the 192-1228 levels and it goes pear shaped, the easiest way I found was to boot to recovery, mount /data then via adb move /data/app/com.franco.kernel*.apk to /data. That stops the kernel app from setting the unstable voltage levels on boot, after that you can boot back up, and then either move the apk back and change the settings, or reinstall it from the play store and start over again.

If you get stuck just watching the boot animation over and over again then that indicates corrupted system files and you'll need to go back to a nandroid (happened 3 times yesterday for me :()
[Samsung Galaxy Nexus] xorob0:
If you keep volume down hold on boot, the phone will block auto startup.

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] rogersnm:
Yeah, after that you can then go to the market place and uninstall the kernel app and reboot.
[Samsung Galaxy Nexus] nodstuff:
I got a corrupted fs yesterday, had a few reboots while testing voltages but every time it booted fine so I thought this is great, I'm one of the lucky ones, all that was happening was I was losing data in Franco app but everything else was fine so I kept going thinking I was invincible until the last reboot, phone booted fine bit every app fc'd. Corrupt. Sickened.

Still tho gave me a reason to flash rascream again, forgot how good it is!

Moral of the story, fsync off helps you to remember the good times! :D
[Samsung Galaxy Nexus] krex:
Thanks for advices! Let me ask more! :)

If there is no corrupted files issue, only bootloop, another way is to flash stock boot.img, isn't it? When it booted, clear kernel app's data and reflash franco's kernel?
[Samsung Galaxy Nexus] rogersnm:
Yeah if you get to the lockscreen and then freeze and reboot etc. You can boot to the bootloader, then via fastboot type "fastboot boot boot.img" where boot.img is the stock kernel img and that should boot up without overwriting franco's kernel. After that you can uninstall the app and reboot and it should boot back into franco's kernel.
[Samsung Galaxy Nexus] Theshawty:
if something randomly gets corrupted after a reboot or such, try enabling fsync. I haven't noticed any difference in performance having it on and I don't know why franco insist of having it off. (Only raises I/O for me in quadrant, but screw benchmarks)

Fsync = off, usually means your filesystem is at a risk upon every crash/reboot where data could be lost.
[Samsung Galaxy Nexus] krex:
Yes, good idea to only boot with stock, not to flash only for resetting kernel app...:) But now I'm not near a computer, so cwm is my only weapon, that led my thoughts.. ok, thanks again for your help, it was really useful!
[Samsung Galaxy Nexus] rogersnm:
I was under the impression that fsync's availability was hardcoded into the kernel?
[Samsung Galaxy Nexus] Moz007:
Are you sure undervolt is apply on boot ? because in the app, the "current values" back to default after reboot for me...
[Samsung Galaxy Nexus] Theshawty:
No idea. Currently, I use GLaDOS.
[Samsung Galaxy Nexus] rogersnm:
They're definitely set for me, do you have the set on boot checkboxes on the OC/UV page checked? (I know they don't mention voltage but it can't hurt) Which ROM are you on?

:eek:
[Samsung Galaxy Nexus] krex:
Maybe stupid question after all but: delete init.d is enough to get rid of custom voltages during bootloop?
[Samsung Galaxy Nexus] Moz007:
Yeap i check it and i can read the description : "VOLTAGES ARE NOT APPLIED ON BOOT" so i don't understand ?! Are you using an other application instead of franco's app ?
[Samsung Galaxy Nexus] metalspring:
Fsync cannot be enabled in Franco kernel unless you recompiled it from source and enable it or add source to toggle it...
[Samsung Galaxy Nexus] Theshawty:
:o

Ehm, the fsync this should be added as a toggle option. Would be awesome.
[Samsung Galaxy Nexus] rogersnm:
My bad your right, it seems mine were applying because I had the VoltageInfo widget on my home screen. When I removed the widget and rebooted they weren't applied. As a temp fix just add the widget :p, I'll work up a nice init.d script in the mean time.
[Samsung Galaxy Nexus] Diger36:
I have taken your UV levels except I have for

1536 MHz: 1275 mV

1420 MHz: 1250 mV

1344 MHz: 1250 mV

Running 192-1536 without stability problems. Tried ondemand, interactive and lazy so far. Not a single sign of instability yet. Have to give it some more thorough testing though...
[Samsung Galaxy Nexus] Moz007:
Ok it's working with the widget ! Ugly widget by the way...

Thanks!
[Samsung Galaxy Nexus] the_jako:
Hello, I have a strange problem wirh the lasts kernels... I use the phone in my car connected with a standard audio cable but with the lasts nightlies and milestone 4 the audio player (Spotify) stops after a few seconds... like the same thing happens when I disconnect the cable... when Milestone 3 works perfect... any ideas???

Thanks a lot!!

(Sorry for my English)
[Samsung Galaxy Nexus] rogersnm:
Which ROM do you use? AOKP has an option to set voltage levels on boot.
[Samsung Galaxy Nexus] Moz007:
Stock rom and never change for a custom.
[Samsung Galaxy Nexus] metalspring:
Set the headphone sound boost in francos app to 0...it's a known issue with the latest sound boost commit
[Samsung Galaxy Nexus] rogersnm:
Missed that post; nope, the custom voltages are not set by an init.d script, they're set by franco's app.
[Samsung Galaxy Nexus] jcbwaters3:
Im running milestone 4 with no problems but when I try to run 181 nightly I just get boot loops. I did get it to boot when I first flashed it but it wouldn't boot after that one time.
[Samsung Galaxy Nexus] rogersnm:
Does it hang at the google logo, repeat the boot animation forever or get to the lockscreen and then crash out?

---------- Post added at 01:29 PM ---------- Previous post was at 01:28 PM ----------

Running 192-1344 with 1344@1250mv still crashed out for me, whereas I can run 729-1536 with 1344@1175mv no problems :\
[Samsung Galaxy Nexus] franciscofranco:
Thanks for the compliment.
[Samsung Galaxy Nexus] bioan:
Sorry for quoting myself.
[Samsung Galaxy Nexus] franciscofranco:
Defaults in CM kernel are 400/400/400.
[Samsung Galaxy Nexus] bioan:
Do you recommend them? Although in this season we must have some values with good sun eligibility.
[Samsung Galaxy Nexus] rogersnm:
There higher the values you use, the higher the risk of screen burn in. Values <210 are recommended.

Even running:

1536 MHz: 1275 mV
1420 MHz: 1275 mV
1344 MHz: 1275 mV
1228 MHz: 775 mV
1036 MHz: 775 mV
729 MHz: 775 mV
384 MHz: 775 mV
192 MHz: 775 mV

Crashed out with 192-1536 but:

1536 MHz: 1250 mV
1420 MHz: 1225 mV
1344 MHz: 1175 mV
1228 MHz: 775 mV
1036 MHz: 750 mV
729 MHz: 750 mV
384 MHz: 725 mV
192 MHz: 700 mV

Those settings still run well for 192-1228 or 792-1536 MHz.
[Samsung Galaxy Nexus] :
Hi,

Not bad for my use,I mean perfect for me:

384Mhz-1.53Ghz/Ondemand governor/Smartreflex Off but no undervolt (yet)/70% brightness/Mainly browsing (only in 3g).

No other tweaks for battery life.Others have more...but with undervolt/underclock,all time with wifi,profiles,etc...

not here.

:)
[Samsung Galaxy Nexus] rogersnm:
@Franco I noticed a bug with the thermal throttle (pretty minor): When running with max frequency 1228 MHz, once it reached >75C it began throttling (as normal), however it first throttled to 1420 MHz, then 1344 MHz, then 1228 MHz making no difference as the max frequency the entire time was 1228 MHz. It did then throttle down to 1036 MHz which reduced the temp.

kmsg log:

<4>omap_thermal_throttle: temperature too high, cpu throttle at max 1420800
<4>throttle_delayed_work_fn: OMAP temp read 75400 exceeds the threshold
<4>omap_thermal_throttle: temperature too high, cpu throttle at max 1344000
<4>throttle_delayed_work_fn: OMAP temp read 75400 exceeds the threshold
<4>omap_thermal_throttle: temperature too high, cpu throttle at max 1228800
<4>throttle_delayed_work_fn: OMAP temp read 77400 exceeds the threshold
<4>omap_thermal_throttle: temperature too high, cpu throttle at max 1036800
<4>throttle_delayed_work_fn: OMAP temp read 77400 exceeds the threshold
<4>omap_thermal_throttle: temperature too high, cpu throttle at max 729600
<4>omap_thermal_unthrottle: temperature reduced, ending cpu throttling
[Samsung Galaxy Nexus] franciscofranco:
Thats useful. Maybe the throttling routine should be tweaked, it shouldn't iterate the frequency table from the top frequency available, but instead of the current frequency OPP.
[Samsung Galaxy Nexus] Zflash:
My Nexus just died completely, after installing de 512 GPU franco kernel. Even the bootloader crashes on the google logo and CWM doesn´t pop up. It´s back for repair now, so I´m hoping it´s still under warranty. If not, I´m gonna be pretty pissed off.
[Samsung Galaxy Nexus] mcdull:
i am getting tired on this kernel now.

i put it in 1.5g and it runs stable. however, it runs slower than stock. like with 5500 marks with antutu and gets really hot.
[Samsung Galaxy Nexus] kompressorgpl:
Jesus!!! Hope for the better...
[Samsung Galaxy Nexus] rogersnm:
You probably aren't going to get a lot of sympathy here but that is extremely rare, it might even be indicative of an underlying fault in the hardware.
[Samsung Galaxy Nexus] jnr21:
There is always small risk if you flash some experimental stuff, and we all already know it...right?
[Samsung Galaxy Nexus] franciscofranco:
The kernel doesnt touch the bootloader.
[Samsung Galaxy Nexus] andrew53517:
Don't you increase the burn in with settings that high?
[Samsung Galaxy Nexus] franciscofranco:
No one forces you to use this kernel. Dont like it use another one.
[Samsung Galaxy Nexus] Gucci.Nexus:
Noob question...sry... where do i change the above voltage settings? If it's unfervolt, are these the max or min?

What is SR?

Thanks, using my Gucci Nexus on XDA premium
[Samsung Galaxy Nexus] rogersnm:
SR stands for smartreflex, read back a few pages for more info.

edit:

You can change the voltage settings on the OC/UV page in franco's app. I don't understand your question about max/min.
[Samsung Galaxy Nexus] Treatcon:
You should still be able to use Odin to recover your phone. Search for it.
[Samsung Galaxy Nexus] Zflash:
Offcourse I know that. The phone booted after I installed the Kernel. I allways use 729/1334 speeds with smartreflex. No extreme stuff. The app applied it and all is well. 10 minutes later I got a messages, turned on the phone and it crashed. The picture was completely mutulated and the phone froze.

Removed the battery and turned the phone on. At that point the google logo started flipping and was scattered all over the screen. I entered fastboot and within instant the phone froze with also a blurry screen. After a couple of these cycles, the phone wouldn´t even go on anymore or at least there was nothing on the screen. Never used the 1.4 and 1.5 mode.

No use, the phone freezes in download mode as well.

Edit: I don't blame Franco for this in case someone is wondering. I'm just a bit pissed off because it's happend to me. The phone is allready at the supplier and hopefully is so dead they just replace the board.
[Samsung Galaxy Nexus] franciscofranco:
Im pretty sure you had a serious hardware malfunction. Sorry to hear that :(
[Samsung Galaxy Nexus] waylo:
I had a very similar thing happen ~2 months ago. Again, not attributing any blame to Franco. And in fact, I do think it was an underlying hardware defect that finally failed.

When I first got my GN in December, when I first booted it up and started with rooting/etc., I noticed at the BOOTLOADER screen I would sometimes have a weird screen flicker, and that the phone would actually sometimes freeze while in bootloader. Wasn't reproducible, so I didn't think anything of it.

3 Months later, I installed probably M2 atop AOKP with no tweak in settings. A few days later, the phone crashed, and a ended up very similar appearance as you describe above, with lots of graphical glitching. I could actually boot into bootloader and recovery, but any actions within that were very unreliable, with reboots galore.

The repair center said the CPU is faulty, with parts on backorder. It's been a ****ing long time waiting for them to fix it with no ETA. Hope you don't have to wait long.
[Samsung Galaxy Nexus] Zflash:
They're not simply replacing the board? With my Galaxy S they just replaced the board and that was that.

Yeah I know. The glitching part was weird to see.
[Samsung Galaxy Nexus] fatappel:
I know there are some aokp haters on this thread but the combination of franco's system info widget & the aokp navigation bar widget launcher is pretty cool....

View attachment 1117739
[Samsung Galaxy Nexus] waylo:
No idea what they're doing. Not much of anything apparently--It's been 2 months (see my sig) which I think is ridiculous retarded. I tried going back to my iphone 3g (gasp) but after fuztzing with tmobile edge for a week I just bought another Gnex from Google play. The first was from an importer so who knows what country it's in now.
[Samsung Galaxy Nexus] despard:
Hey Francisco will you be watching the Germany Portugal soccer match:D?
[Samsung Galaxy Nexus] The Gingerbread Man:
A bug with Franco app

As you can see I'm on m4, I selected power mode as full power and apparently I have wheatly and 1.5ghz, on m4 :rolleyes:

Haha well my phone is dreaming of running these last nightlies as much as me :p

No criticism I just thought I'd make it funny, well at least for me :D

Sent with a shake
[Samsung Galaxy Nexus] franciscofranco:
Yes I am :)

Ahah. Well thats just a name display, there is no Wheatley on Milestone 4 so its not selected thats for sure. I'll fix it in the next app update.
[Samsung Galaxy Nexus] The Gingerbread Man:
I know I was just trying to make a joke about it :)

Sent with a shake
[Samsung Galaxy Nexus] TyroneLT:
I couldn't agree more!
[Samsung Galaxy Nexus] MFD00M:
Happy new years everyone. Francisco, I don't know who slept better, my phone or me after one too many drinks last night =p. My phone dropped 2% in 6 hours of standby....excellent kernel! I will def pick up your kernel updater app
[Samsung Galaxy Nexus] inffy:
If you are running ARHD on you GNexus, then this won't work on your phone. You have to have a ROM that is based on 4.0.3 (ARHD is 4.0.2)
[Samsung Galaxy Nexus] Vangelis13:
Get "Market Enabler" & set it to o2 Germany (for example). Worked for me.
[Samsung Galaxy Nexus] drawde40599:
haters

I see haters already, ***** and whine on twitter about ur new app, #$%& em!!! I hope u make as much money as u possibly can with your app, its your time and energy, u offer the kernel free and if u want u can pay a 1$ and makes things even easier to find get updates . Keep up the good work thanks!
[Samsung Galaxy Nexus] :
Awww damn i don't have a credit card!!!!
[Samsung Galaxy Nexus] RjsShadows:
Is there anyway you could make a secondary kernel for us who overclock? Please, my phone runs 1.42ghz perfectly and to those who don't like to OC simply don't do it. I love this kernel by the way! Just miss the oc.
[Samsung Galaxy Nexus] magn2o:
Weird. I was able to buy the app, but I'm unable to download it. It's just stock at "Starting Download..." -- Killing the market process, clearing data, rebooting -- none of it has any effect. I can download any other all just fine. Tried on both HSPA+ and WiFi.

I'm in the U.S. and was able to find it in the market with no problem.
[Samsung Galaxy Nexus] inffy:
If you need OC, then there are other kernels out there which allow you to OC.

It will be added to this too in due time.

In my opinion it's not needed to do 2 different kernels. Much more work for Franco to do two different releases, considering he has other phones too to dev,
[Samsung Galaxy Nexus] rohdawg:
I'm on a 4.0.3

need to update my sig.

Found it after i flashed AOKP
[Samsung Galaxy Nexus] rabhw:
I have the same issue, still not fixed. I spoke to Franco in the meantime who kindly sent me the apk. Stupid market issues.
[Samsung Galaxy Nexus] franciscofranco:
Overclock is coming #8. Just some patience please.
[Samsung Galaxy Nexus] :
Love your work...this seems to be the only kernel that doesn't eat my battery! Thanks :cool:
[Samsung Galaxy Nexus] aron7awol:
I run interactive exclusively and love the snappiness. CPU Spy still shows the vast majority of my awake time spent at the lower frequencies so I don't think there's a big difference in battery life between ondemand and interactive.
[Samsung Galaxy Nexus] adamleerusse:
Hey Franco,

I've used your kernel a few times on different versions of roms (bigxies rom, ARHD and AOKP) but I've always had to flash back to stock kernel because of huge drain on battery. The worst being 7 hours complete battery drain with less than an hour screen time. Is there something I'm doing wrong? Do I need to use setCPU? It must be something I'm doing because so many users say how brilliant the kernel is :D

I'm currently on AOKP build 12 and willing to give the kernel another try :-) I noticed the screenshot off the market shows nightly 8.. is that exclusive for people that have brought the app? I'll buy the app if you can tell me what I'm doing wrong hahaha.

Thanks!