yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] fatappel:
after a full day of use on r181 - it's really impressive work. ran wheatley 384/1536 MHz with default voltage in both low level and very demanding situations and it's solid as a rock. performance is great and it's a wonderful accomplishment but I do not see this set-up as a daily driver. at idle, the battery life is amazing and no complaints there. seems to sleep very nicely and quickly. however, if you're doing simple browsing or even just responding to an email where your screen is on for say 5 minutes, the heat that accumulates and visual drop in battery percent by percent, right in front of your eyes is astounding. personally the minimal performance gain of the extra 308 MHz is not worth the expenditure of extra battery life and the addition of a heating pad in my pocket. going to continue to play with wheatley but at 384/1228 which is plenty of performance for me. wheatley compared to my previous governor of choice - on demand i feel is a bit choppy when first waking up the phone after it's been sleeping for a bit but the quick deep sleep is worth the initial slight chop in my opinion...so far. just felt like sharing my experience. keep up the incredible work franco. thanks
[Samsung Galaxy Nexus] rogersnm:
Which is explained by this commit: https://bitbucket.org/franciscofranco/android-tuna-omap/changeset/1583700eeb8f

Could you modify that to use a lower boundary (and modify the stock voltages) or to check the CPU freq if available?

I posted my settings here: http://xdaforums.com/showpost.php?p=27105180&postcount=18893
[Samsung Galaxy Nexus] franciscofranco:
Basically if smartreflex detects an OPP with a nominal voltage >= 1350mV it skips the calibration for that same OPP. If we dont do this SR wont understand that the device needs more voltage and calibrates it down. Then kaboom.
[Samsung Galaxy Nexus] rogersnm:
I set the voltage for the 1.5 GHz OPP to 1349 MHz which caused SR to calibrate it to 1220 mV, leading to resets. Can you lower the boundary to something like 1300 MHz so I can try to undervolt the chip to <1350mV?

/* Based on Imoseyon's idea to properly calibrate high frequencies e.g. >= 1.5Ghz MPU */
if (volt_data->volt_nominal > 1300000) {
[Samsung Galaxy Nexus] franciscofranco:
I will have to think about it ;)
[Samsung Galaxy Nexus] supernova_00:
Franco, is there anything in the trickster mod that can be applied to your kernel? I've seen a few people talk about that mod saying your kernel with it is awesome so I'm curious what the mod actually does? I don't understand what is listed in the trickster mod thread and haven't followed this thread long enough to know exactly what all you have incorporated.
[Samsung Galaxy Nexus] Meaple:
@franco

I updated your app and non of the power modes do anything. I select one of your power modes and it doesn't change anything. If I create my own power mode it doesn't save it.

I figure I would test m4 for a bit.

Posted from my secret spaceship.
[Samsung Galaxy Nexus] rogersnm:
I seem to have the 1536 MHz slot running stable at 1225mV (SR Off)

It's taken the peak temps from about 94C to 78C, which combined with getting rid of the 75C throttle point should yield "superlative benchmarks" :D
[Samsung Galaxy Nexus] eaglesport:
I have the same issue. It won't save the power modes I create. I'm sure an update will be out soon as Franco said, he released it knowing some bugs were included and wanted feedback.

Swyped from my Galaxy Nexus
[Samsung Galaxy Nexus] jhericurls:
To be fair your feedback is not relevant to the rest of us normal Nexus users.

You got some kind of super Nexus phone :p
[Samsung Galaxy Nexus] andQlimax:
IMM76L pushed to AOSP

http://groups.google.com/group/android-building/browse_thread/thread/7eb2d2b0473cb54?hl=en

Any little fix on the kernel side maybe? :)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Theshawty:
Will those make a factory image someday? :p
[Samsung Galaxy Nexus] rogersnm:
It all went south eventually, got it down to a quadrant run at 1100 mV and then it decided to completely give up. I got boot loops before eventually recovery to 1225 mV after a few kernel flashes via fastboot. Good job I had titanium backups as my gmail, tasks, launcher and franco settings were all corrupted.

Still that's all part of the fun of overclocking :p
[Samsung Galaxy Nexus] simms22:
you mean.. thats all part of the fun of having fsync off ;)
[Samsung Galaxy Nexus] rogersnm:
Given that it doesn't crash except for when I fook about with the voltages and lower them to stupid levels, I can't really complain :p
[Samsung Galaxy Nexus] Exostenza:
I flashed on m4 from imoseyon 3.8.0 and now about 2/3 of my calls are so low volume wise I can hardly hear what the person in the other end is saying even with full volume. Is this a known issue?

The battery life is MUCH better but the volume issue is a deal breaker.

Sadface.jpg
[Samsung Galaxy Nexus] franciscofranco:
Exactly :)
[Samsung Galaxy Nexus] andrew53517:
I'm seeing some really high battery drain when idle, unfortunately I have to go back to 180. It was pretty stable for me but 181 ran great just the insane idle drain (such as almost 15% in an hour and a half.. :confused: )
[Samsung Galaxy Nexus] Theshawty:
Other than meaningless benchmark scores, what other things do we get with fsync off? Why can't it be left on?
[Samsung Galaxy Nexus] grisha1:
Speaks volumes.. :thumbdown:
[Samsung Galaxy Nexus] simms22:
just meaningless benchmark scores, i/o mostly. but as much as i warn people about having fsync off, im just as guilty for turning fsync off myself :rolleyes:
[Samsung Galaxy Nexus] rogersnm:
They may be meaningless, but lets be honest the vast majority of people using this kernel probably came here either for the battery improvements or the performance, which was no doubt a decision based either directly, or by proxy, on the benchmark scores. As an example; there was a lot more activity in this thread when the 1.5 GHz slot was added, but lets be honest, just how much do you notice a 14% overclock [compared to the 1344 MHz slot] in daily usage?

ps. I <3 the 1.5 GHz slot xD
[Samsung Galaxy Nexus] simms22:
i like the 1.7XX slot. seems like benchmark scores start going down after(1.8+).
[Samsung Galaxy Nexus] nodstuff:
Exactly, all it takes is one person to say "ZOMG 1.5ghz is the shizzzzzzzzzzz!!!1111" and everyone thinks the same.

Power of suggestion.

I would also like to add that I too love 1.5ghz, its the shizzzzz!!111
[Samsung Galaxy Nexus] Gahh Its Lee:
1.5ghz made my family love me again. Also my cat came home. I can now reach the center of my back and do handstands. Oh happy day
[Samsung Galaxy Nexus] 6jaipur6:
Francisco all can I say us that you are an Einstein:D in kernels .After a half a day with 181 default settings all is awesome and smooth. And off topic .... R9 for One X make me very happy . My phones work like hell( in best terms). Thank you again like always!
[Samsung Galaxy Nexus] do0b:
first reboot just occured after 24hours(ish) with r180, 1536-384MHz, 512GPU, wheatly, SR on.
[Samsung Galaxy Nexus] Gahh Its Lee:
Try 181 its more stable.
[Samsung Galaxy Nexus] do0b:
okay. also, the phone crashed while i was on 'reddit was fun'.

will go to r181 now.
[Samsung Galaxy Nexus] renna1992:
would be interested too :)
[Samsung Galaxy Nexus] Lambetts:
Unfortunately, wifi seems to be a little dodgy.... just stops, freezes, then resumes. Hasn't happened with other kernels. Using M4 too....anyone else have a similar issue?

Also, anyone got a nice, calibrated set of colour settings? Like from a calibrated photographic spec monitor?

Thanks guys.
[Samsung Galaxy Nexus] Backwardsblade:
Apologizes if this is misplaced, new gnex user. Kernel is excellent--181, seeing some issues with the updater application since update. Cannot adjust power settings or make a custom one. Stuck on balanced mode at all times. Running latest cm9 nightly. Many thanks and TIA.
[Samsung Galaxy Nexus] do0b:
http://xdaforums.com/showthread.php?t=1521195
[Samsung Galaxy Nexus] Sveke:
Giving 181 a try at 1536, let's see if my ****ty silicone maintains this time......
[Samsung Galaxy Nexus] dpaine88:
1500 interactive is wicked fast

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] smccall:
Want to say love your kernel and your premium app but since the recent update it force closes every time I try to open it and it won't auto flash with out getting stuck on the boot screen. Please help. It will force close as soon as I slide to the oc and uv screen
[Samsung Galaxy Nexus] psyren:
Had a couple of issues with the screen not coming out quite as fast as it normally would. I sort of fixed the problem by removing the screen off max freq (making it the same as my max freq), but it did happen again once afterwards, though not as bad.

It seems to lose time (anything up to a few seconds) when this happens; maybe it's making the whole device freeze?

Other than this, the device has been performing fine. Temps are good, no reboots.

192-1536, SR on, 384 GPU, Wheatley.
[Samsung Galaxy Nexus] simms22:
go to manage app, find the app and clear its data. or you can try uninstalling and reinstalling the app.
[Samsung Galaxy Nexus] denpad2010:
I flashed m4 and 180 and seems work fine, battery is great but, when I want check battery info, shows more than 5 days so that means data didn't reset, any suggestion I removed battery and nothing anyway battery life is great
[Samsung Galaxy Nexus] do0b:
It is! I got 7385 on antutu and 7038 with wheatly
[Samsung Galaxy Nexus] franciscofranco:
App works fine. Try what simms suggested, it should fix it.
[Samsung Galaxy Nexus] franciscofranco:
Blame CM9. Update your su binary or something, it works fine for me with rascream.
[Samsung Galaxy Nexus] do0b:
Anyone with 384mhz for max frequency screen off? Any problems?
[Samsung Galaxy Nexus] nikulogical:
I've been getting higher antutu scores with on demand and interactive compared to wheatley. 180/1500 freq for all.

I can't tell the differences in battery life yet.. has anyone done any tests?
[Samsung Galaxy Nexus] smccall:
Did that already have tried everything :D

Tried 3 different roms and several kernels. I have done nothing but except the update that's when it stopped working. I've installed uninstalled it cleared data reset su permissions. Have even gone as far as having the app the only one installed on a fresh flash.
[Samsung Galaxy Nexus] nikulogical:
[Delete]
[Samsung Galaxy Nexus] simms22:
have you tried running a fix_permissions or clearing your dalvik/cache?

try uninstalling it then clearing your dalvik, then reinstall it after you boot up.
[Samsung Galaxy Nexus] do0b:
franco's app v5 is quite buggy when saving custom power modes.

yes yes i know it says on the changelog. just 'reporting' it.

EDIT: franco's power mode doesnt work too.
[Samsung Galaxy Nexus] Backwardsblade:
I saw the same issues. Franco thought it was largely related to cm9 changes, but it's worked with an older apk from a previous backup. Right now 181 is working great with 4.9. Maybe you can get lucky with an old backup like it did.

sg
[Samsung Galaxy Nexus] jcmm11:
Yes and no
[Samsung Galaxy Nexus] Diger36:
I must be missing something. When I make a custom power profile and activate it, how do I get back to normal? I ended up erasing the Franco app data but there must be an easier way. Especially turning one core off. The rest can be set manually but the core would not get back on...
[Samsung Galaxy Nexus] schizophrenia:
it may sound a bit unrelated but is there anything in the kernel that may affect the GPS performance?

Coz during r180 and r181, it always takes a long time to get a good GPS fix.

but when I reverted it back to M4 due to many reboots that I got even on r181, my GPS fixed in a snap and with lots of satellites fixed.

I run the same voltages and even with the same max/min and governor.

Any thoughts? voltage issues?
[Samsung Galaxy Nexus] Moz007:
I can't apply uv on boot...

I creat a uv.txt with this code :

#!/system/bin/sh
echo "1375 1200 1175 1125 1000 875 725 700" > /sys/class/misc/customvoltage/core_voltages

I put it in "/system/etc/init.d" folder an apply full permissions and nothing happens...
[Samsung Galaxy Nexus] Lambetts:
+1

Just reporting, app has some serious issues. Wont show voltage, powermodes are all over the place and screen off frequency doesn't stick. I'm using M4.....its a milestone, little surprised.

Thanks.
[Samsung Galaxy Nexus] rogersnm:
I was getting about 6400 with r180 at stock voltages, now I get:

It's been stable with those voltages for 8 hours.

Battery drain wise I left my phone with the screen off and wake locked all night and ended up with:

It lost ~10%pts battery with some web browsing at the start and end

(Ignore the weird bit at the start of the graph, that was me messing about)
[Samsung Galaxy Nexus] The Gingerbread Man:
Franco, here is kmsg for non booting devices with r181

<6>[ 119.930847] max17040 4-0036: online = 1 vcell = 4193750 soc = 95 status = 1 health = 1 temp = 300 charger status = 0

sorry for delay
[Samsung Galaxy Nexus] franciscofranco:
I hope to have enough time today to correct what is borked, I ve gathered enough feedback I think.
[Samsung Galaxy Nexus] franciscofranco:
Nop, thats debug stuff from the battery.
[Samsung Galaxy Nexus] justinjustin234:
im using r181

why cant i see the C4 state in CPU spy?

thank you:)
[Samsung Galaxy Nexus] franciscofranco:
App and kernel are different things, why mix them? Voltages work fine here, power modes as well, screen off freq too. Running the same market version on my device.
[Samsung Galaxy Nexus] The Gingerbread Man:
yeah i gathered that much, its all adb pull /proc/kmsg kmsg.txt gave me after ctrl + c gave me as without ctrl + c gives no output, im chatting with rogersnm who is nidly helping me with this stuff.
[Samsung Galaxy Nexus] bat0nas:
Testing #180 at max speed with wheatley governor and at voltages in the screnshot.

So far so good.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] johno168:
wow 67c is a bit high don't you think?
[Samsung Galaxy Nexus] franciscofranco:
Yes, later today :)
[Samsung Galaxy Nexus] inffy:
Oh, I have missed the Kernel updater utility. Just bought it too :)
[Samsung Galaxy Nexus] taz2781:
I just buy the kerner updater... after almost 1 hour of problem... But Franco i have to do this public, you are the best, you response to the problem was astonishing fast... the man contacted me by gtalk, something that not every one do!

Gracias hombre por tu soporte! :D
[Samsung Galaxy Nexus] StuMcBill:
I just went back to MoDaCo ir8 (including MoDaCo kernel) and I was able to activate / deactivate NFC with no problem, however, when I flashed back to Franco 7.1 I was unable to activate NFC again.

However this might be caused by MoDaCos 4.0.3 compatibility pack which he has on his ROM, going to ask on MoDaCo. This is causing problems with Camera too.

Sent from my Amiga 500 using Workbench
[Samsung Galaxy Nexus] Redflea:
Also just purchased the Franco kernel updater from the market...looks like this in case others are looking for it...

View attachment 838137
[Samsung Galaxy Nexus] sirj00:
+1 thanks couldn't find it.
[Samsung Galaxy Nexus] trismegistos:
Franco. 7.1 is awesome!
[Samsung Galaxy Nexus] rohdawg:
Not coming up in my market AT all....odd.

This kernel rocks though....thank you so much. I'll be supporting as soon as I can locate the app!
[Samsung Galaxy Nexus] Redflea:
I searched on kernel updater, and then found it on the search results...might try that.
[Samsung Galaxy Nexus] PanBongo:
found it without problems, u might as well now
[Samsung Galaxy Nexus] drawde40599:
My Google wallet works just perfect! I use every day at McDonalds and in work vending machine, I.don't have any " tags " so can't comment on that
[Samsung Galaxy Nexus] jameslfc5:
This should help...

https://market.android.com/details?id=com.franco.kernel

Thanks Francisco!

Sent from my Galaxy Nexus running Romanbb's amazing AOKP ROM!
[Samsung Galaxy Nexus] rohdawg:
US market here...not showing up. Checked on the web version of the market, shows up but is shown as "not compatible with your device"

Thanks for the help, maybe its a US market prob. Thats the only difference I see after looking at who has posted they have found it.
[Samsung Galaxy Nexus] drawde40599:
min

So 700 is recommended MHz for min, and ondemand is recommended gov?
[Samsung Galaxy Nexus] damobster54:
Installed the app with no issues! Looking forward to the first time I can use it :)
[Samsung Galaxy Nexus] mightybrick:
Shows up as able to install and compatible with my device. I'm in Utah.
[Samsung Galaxy Nexus] beekay201:
Most likely, a rom (build.prop) issue. What do you see in build.prop on ro.build.fingerprint? Test keys, or release keys?

He can also try market enabler, but if he's using test keys thats not going to work. It's probably not a location issue, imo.

Edit: i'm using test keys, and market doesnt find it.

/me sent this from a i9250 using tapatalk
[Samsung Galaxy Nexus] mightybrick:
I show release-keys.
[Samsung Galaxy Nexus] Redflea:
Yup, US here as well, CDMA/Verizon, on CM9 Kang ROM by winner00, best ROM for the VZW Nexus available. :)

This is the CM9 Kang fingerprint:

ro.build.fingerprint=google/mysid/toro:4.0.2/ICL53F/235179:user/release-keys
[Samsung Galaxy Nexus] beekay201:
Like 90% confirmed that it's an issue due to fingerprint.

/me sent this from a i9250 using tapatalk
[Samsung Galaxy Nexus] franciscofranco:
Only **** I see there is the system complaining about unknown partition table of mmcblk0boot1... if thats the problem I have no idea. What rom are you using?
[Samsung Galaxy Nexus] Moz007:
Nobody knows ? :(
[Samsung Galaxy Nexus] franciscofranco:
You are trying to apply mpu voltages to core...
[Samsung Galaxy Nexus] justinjustin234:
can anybody tell me how to check the usage time of c4 state?

thank you:)
[Samsung Galaxy Nexus] jnr21:
Lol
[Samsung Galaxy Nexus] Moz007:
Oups ! okay i change it to

#!/system/bin/sh
echo "1375 1200 1175 1125 1000 875 725 700" > /sys/class/misc/customvoltage/mpu_voltages

Still not working... What extension should I use for the file ? .txt is ok ?
[Samsung Galaxy Nexus] trinhtunglc:
Hi guys. I'm using CM9 nightly with Franco kernel. How can i use the usb host to connect a flash disk? please help :)
[Samsung Galaxy Nexus] justinjustin234:
please help:(
[Samsung Galaxy Nexus] jnr21:
You shouldn't use any extension at all. This isn't windows :)
[Samsung Galaxy Nexus] Moz007:
I tried to put "uv" file in "/system/etc/init.d" and still not working... I forgot something ?
[Samsung Galaxy Nexus] jnr21:
And you disabled smartreflex first?
[Samsung Galaxy Nexus] Moz007:
Yes but if this is working, how do i know ?

I look in CPU Undervolt option and all current values should appear here ?
[Samsung Galaxy Nexus] jnr21:
Maybe you should purchase franco app, you can uv, oc, disable sr etc etc in one app.

Ps. Can you guys paste your long logs to pastebin, it's not so nice to scroll long pages with tapatalk :D
[Samsung Galaxy Nexus] Moz007:
I have the app ! But we can't apply uv on boot with it and i want to do that manualy !
[Samsung Galaxy Nexus] Lambetts:
Thanks for your reply Franco.

App and kernel are developed by yours truly so they do correlate don't they, as the app is a 'control' for your kernel? Haha. I could be wrong though. :)

I wasn't having a go or anything Franco, was just reporting. I think you've misunderstood a few of my posts unfortunately, I mean no ill will and I do mean well. I'm just a paying, supporting client. ;)

Anyway, no worries, might just be my end. I didn't see any voltages though for some reason and the screen off frequency was saying 384, but when I went to change it to 192, the selection box was already on that? So it did stick, just wasn't showing correctly. Same with the power modes. Just not labeling it right, but still had my selection selected. Not sure what's happening there.

Some feedback anyhow.

Thanks mate. :)
[Samsung Galaxy Nexus] justinjustin234:
nobody knows?:(
[Samsung Galaxy Nexus] rogersnm:
The max screen off freq doesn't appear to do anything on the wheatley governor, I set it to 729 MHz and then turned the screen off and checked the CPU stats 8 hours later and it had been at 1536 MHz for 5 hours.

The "Franco Power Modes" in the app also doesn't appear to work live, although it does seem to be set upon reboot, although the "Power Mode: " in the widget displays null regardless of the choice.

I've just been playing for a few hours and I've got some nice stable undervolt settings with SR off.

1536 MHz: 1250 mV
1420 MHz: 1225 mV
1344 MHz: 1150 mV
1228 MHz: 775 mV
1036 MHz: 750 mV
729 MHz: 750 mV
384 MHz: 725 mV
192 MHz: 700 mV
[Samsung Galaxy Nexus] Remoteconcern:
Those are crazy low, and I suspect only stable because Wheatley doesn't use the middle frequencies very often.
[Samsung Galaxy Nexus] rogersnm:
I use interactive but I also tested each individual frequency by setting the min and max freq to that specific frequency to force it to use it. Then I did stability tests and idle tests for each freq at the given voltage level - it did take around 5 hours. After that I set min to 192 and max to 1536 and did further stability and idle tests.

That said I had to bump the 1.5 GHz freq up by another 25 mV so I'm now running:

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

I wouldn't call it totally stable, but I'm getting there :)

---------- Post added at 02:00 PM ---------- Previous post was at 01:46 PM ----------

The app does apply the undervolt on boot assuming the last shutdown wasn't due to a crash. If the system crashes and then reboots, it seems to apply the default values rather than the saved values (which is a very good idea).

---------- Post added at 02:04 PM ---------- Previous post was at 02:00 PM ----------

ps. Anyone wanting to try undervolting should make a full CWM backup first as it sucks having to patch things up with titanium backup. Also, turn off SR before you begin undervolting as I achieved much better undervolts with SR off.
[Samsung Galaxy Nexus] TyroneLT:
Tried running over clock on 181 on the wheatley governor to 1.5ghz and other then the phone getting hot it ran pretty well all day. No freezes or reboots.
[Samsung Galaxy Nexus] SpOuK-3-:
@franco

Any loss of data reported with r181? I go one last night... No data working but works after a reboot...

I'm not sure of what to send...

Thanks!
[Samsung Galaxy Nexus] kompressorgpl:
Hello! I have a navigation software call Ndrive (TMN drive). After 3 or 4 start ups I get a reboot... Is the only apk that get me reboots... Is a kernel problem or a ROM problem?
[Samsung Galaxy Nexus] Gucci.Nexus:
Ever since flashing AKOP 38 (i also flashed- franco M4) my gps location in maps isnt as good as it used to be. I notice in settings - location, the setting for gps source is not there. I used to change that from bluetooth to gps.

Do you think my gps problem might be a result of flashing AKOP rom, or would it more likely because of the Franco kernel?

Thanks so much for your hard work, and sharing.
[Samsung Galaxy Nexus] Theshawty:
Maybe the wrong server is set for the gps? For me, the server was set to north america, but with FasterFix, I set it to Europe.
[Samsung Galaxy Nexus] rogersnm:
@Franco - could you add a check in the app so that before it applies the custom voltage on boot, it checks to see if a certain file exists, and if the file exists then it doesn't set the voltage?

With my experience of undervolting I often got reboot because I set the voltage a little bit too low, but the app kept setting the voltages after each boot causing it to reboot again, and thus bootloop. The only way around this was to boot into safemode and uninstall then reinstall the app. If I could create a file in recovery that would stop the automatic setting of custom voltages it would be a big help

Pseudo code wise:

function setCustomVoltages() {
if (!file_exists("/sys/safeBoot")) {
applyVoltages();
return 1;
} else {
// Custom voltages not applied due to safeBoot flag
return 0;
}
}
[Samsung Galaxy Nexus] thoth_19:
Keep us updated on your stability finding. Running your UV setting on lazy governor to see how she'll do.