yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] P30SiNa:
Is Wheatley Gov really improve battery?

I'm getting 5 hours screen-on time with Milestone 4 ondemand (Battery died after 19hours!!)

But I got only 3 hours screen-on time with r185 and battery lasts only 15 hours.

Am I doing something wrong? because as lots of people said, with Wheatley I have to get even better battery life!

My settings with Wheatley gov:

Min: 384 MHz

Max: 1228 MHz

only 4 or 5 hours with Wifi

Sync off most of the time

Brightness: 20%-30%

SR ON

---------------

My settings with Milestone 4 ondemand:

Min: 384 MHz

Max: 1036 MHz

Full time on wifi + Wi-Fi PM_Fast !

Sync on

Brightness: around 30%-50%

SR ON
[Samsung Galaxy Nexus] splus:
This is a typical example of how theory =/= practice.

Theory here is perfect but in practice I get same battery life with 384 and 512 MHz GPU, but with immediately noticeable difference in smoothness and scrolling.

512 GPU is simply much smoother for me on any ROM, any kernel version, and in any app.
[Samsung Galaxy Nexus] sago62:
I do not find obvious differences between 185 and 185 Linaro b2 ....sorry!:rolleyes:
[Samsung Galaxy Nexus] rogersnm:
Wheatley generally seems to harm standby mode time (ie. screen off - cpu doing fa), but it doesn't really explain a 40% drop in screen on time tbh

Presumably the assertion about the memory bandwidth bottlenecking everything must be incorrect. Also I have no idea what the SR values for the core voltage are when the GPU is @ 512 MHz, maybe someone could grab them during a benchmark?
[Samsung Galaxy Nexus] metalspring:
I already know what sr calibrated mine as...

384 gpu- 1025

512 gpu- 1050

A difference of 25 is almost nothing
[Samsung Galaxy Nexus] metalspring:
I think this is the important part...

max17040 4-0036: online = 1 vcell = 3625000 soc = 40 status = 2 health = 1 temp = 380 charger status = 0

rpmsg_omx rpmsg-omx1: local addr assigned: 0x401

omap-iommu omap-iommu.0: iommu_get: ducati qos_request

omap_hwmod: ipu: failed to hardreset

omap-iommu omap-iommu.0: ducati: version 2.1

rpmsg_omx rpmsg6: conn rsp: status 0 addr 101

sr_class1p5_calib_work: core: Calibration complete: Voltage:Nominal=1250000,Calib=1050820,margin=13000

rpmsg_omx rpmsg-omx1: Disconnecting from OMX service at 101

rpmsg_omx rpmsg-omx1: local addr assigned: 0x401

rpmsg_omx rpmsg6: conn rsp: status 0 addr 101

rpmsg_omx rpmsg-omx1: Disconnecting from OMX service at 101

max17040 4-0036: online = 1 vcell = 3415000 soc = 39 status = 2 health = 1 temp = 400 charger status = 0

[franciscofranco] c066e1dc - temperature is over the threshold, but throttling is disabled.

binder: 1132:2267 transaction failed 29189, size 168-0

omap_tshut_irq_handler: Thermal shutdown reached rebooting device

[MODEM_IF] cmc221_off()

[MODEM_IF] cbp71_off()

[MODEM_IF] cdma_ipc0 state changed: OFFLINE

PVR: PVRSRVDriverShutdown(pDevice=c78a5200)

PVR: SysSystemPrePowerState: Entering state D3

PVR: Uninstalling device LISR on IRQ 53 with cookie c79ef600

PVR: DisableSystemClocks: Disabling System Clocks

Restarting system.
[Samsung Galaxy Nexus] rogersnm:
That should still be an increase in GPU power consumption of 40% at 512 MHz. P=CfVV -> Hence power consumption is proportional to the frequency, which means if you increase it 33% (384 * 1.33=512), you're immediately going to increase the power consumption by 33% regardless of the change in voltage.

---------- Post added at 10:13 AM ---------- Previous post was at 10:12 AM ----------

You reached 110C :p
[Samsung Galaxy Nexus] metalspring:
I don't think so? I just checked dmesg and the "temp" part came up as 420 and I checked Franco's app and it said 52C

So dmesg temp of 420 equals about 52C

My last_kmesg said the temp was only 400 which would probably correspond to 50C
[Samsung Galaxy Nexus] nklenchik:
1.5ghz running just fine here
[Samsung Galaxy Nexus] rogersnm:
The temps in kmsg should correspond exactly to Franco's widget, they're just measure in mC. If you want to see a live output of temps during a benchmark, connect your phone, open an adb shell session and run:

while (true) { cat /sys/devices/platform/omap/omap_temp_sensor.0/temperature; sleep 1s; }

Just paste that in and execute and it'll display your CPU temp in mC every 1 second.

Btw:

My battery life on r185.linaro.b1, with my undervolt settings.

And to get everything out of the way in one post, here's r185.linaro.b2.512gpu
[Samsung Galaxy Nexus] metalspring:
Well then there might be the issue of linaro optimized Franco running too hot...I've never had an issue with temp before
[Samsung Galaxy Nexus] rogersnm:
You used to have a thermal throttling point :rolleyes: The temps cool down extremely quickly from >80C. Just watching the widget does not provide a reliable measure of your peak temperature.
[Samsung Galaxy Nexus] jhondidfool:
Now this is better, with linaro 185... 4206 Quadrant and 7096 on AnTuTu. I bet I could get it higer with a linaro ROM... Where did you say one can find those linaro akop? :D
[Samsung Galaxy Nexus] rogersnm:
Here you go, Maguro (GSM) b38 AOKP compiled with linaro: http://goo.im/roms/edt/maguro/aokp_maguro_build-38-O3.zip (from roman)
[Samsung Galaxy Nexus] metalspring:
I did a test with thermal throttling on and it still got up to almost 100C before I killed the test :(
[Samsung Galaxy Nexus] sago62:
careful, it seems to me to complain that the GPS does not work ....;)

this is the CM9 Linaro ..... https://plus.google.com/106870161233159147936/posts/FnMjopeY9FJ
[Samsung Galaxy Nexus] rogersnm:
I changed the throttle point to 95C, that sort of temp is expected but it shouldn't reach the thermal shutoff point.
[Samsung Galaxy Nexus] sago62:
but the next build franco will be built with Linaro?:confused:
[Samsung Galaxy Nexus] lesilent:
He said : NO.
[Samsung Galaxy Nexus] rogersnm:
You know you guys can just compile it yourself, it takes about an hour to initally set up a VM and about 30 minutes for each build. It's not too hard.
[Samsung Galaxy Nexus] Antob125:
Well Franco said if we prove it to him maybe he'll incorporate it. Maybe with all this testing he will. But who know till he sees everything that has been done in the past 24 hours.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sago62:
i used Franco for a long time and I would hate having to hold the stock kernel CM9 for optimizations Linaro ..... I do not understand!
[Samsung Galaxy Nexus] rogersnm:
You don't have to go back to stock, you can compile franco's kernel yourself.
[Samsung Galaxy Nexus] sago62:
i'm not so skilled .....:D:o
[Samsung Galaxy Nexus] lemmy_0:
wasn't able to reach 4k in quadrant, but was able to get 7k in antutu for the first time.

using aokp linaro + franco linaro
[Samsung Galaxy Nexus] rogersnm:
I got my highest quadrant to date with r185.b2.384GPU: (384-1536 MHz/interactive)
[Samsung Galaxy Nexus] superjjskate:
Can someone please help me find a fix to play Grand Theft Auto on your kernel. My OS is paranoid android but they said it's the kernel's fault.
[Samsung Galaxy Nexus] Hanny:
see if your problem is the one i pointed out :)

http://xdaforums.com/showthread.php?p=25437690#post25437690

cheers
[Samsung Galaxy Nexus] rogersnm:
I presume you've tried uninstalling and reinstalling?
[Samsung Galaxy Nexus] dr.sonic:
I am on r185 linaro b2.

When I test voltages one by one (min and max frequency are same), I can go with these:

1344 - 1175

1228 - 850

1036 - 800

729 - 800

384 - 775

192 - 750

But when I set min frequency on 192,and max on 1344, with these voltagese, my phone instantly freezes and reboots. I tried to set min frequency on 384, but same is hepening.

Any thoughts?

GNex via tt
[Samsung Galaxy Nexus] rogersnm:
Yeah I had a similar experience, it's best to set them whilst using a wider frequency range.
[Samsung Galaxy Nexus] dr.sonic:
Sorry, I didn't understand that. You mean that I need to enable 1,4 and 1,5ghz slots?

GNex via tt
[Samsung Galaxy Nexus] supernova_00:
Could you guys please create a new thread for all this benchmark crap so the issues with the latest nightlys don't get drowned out and missed by Franco?

Since 181 GPS takes a heck of a lot longer to lock on. 185 causes a lot of wifi related wlan related kernel wakelocks. I had wifi on for about 3 hours and had over an hour of kernel wakelock (something like 4000 counts).
[Samsung Galaxy Nexus] aleve1983:
+1
[Samsung Galaxy Nexus] The Gingerbread Man:
He means use on demand/lazy/interactive/conservitive. These governor use all frequency slots enabled

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Set security to open

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] JcMalta:
I agree that a benchmark forum would be a good idea, but at least here since installing 185 after it was a couple of hours old I have no problems whatsoever with wlan wakes:

Today Wifi on for over 12 hours since charge, 2m 49s wake lock ... battery at 54% -2hr 12m Screen on (battery low because I have been benchmarking)

Just checked GPS: 10 seconds to lock on 4 sats, 20 seconds to lock on 6
[Samsung Galaxy Nexus] supernova_00:
2.4 or 5 GHz? I'm using 2.4
[Samsung Galaxy Nexus] nodstuff:
r185 linaro b2

Not bad, not bad at all....
[Samsung Galaxy Nexus] JcMalta:
My router has both, but generally always run at 2.4GHz
[Samsung Galaxy Nexus] rogersnm:
I mean you should calibrate your voltages whilst using the min and max frequency you intend to use on a daily basis. Don't specifically set the min and max frequency to the frequency you're trying to calibrate the voltage for as that seems to make the phone more stable than it actually is.

---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------

ps.

Epic antutu score :eek:
[Samsung Galaxy Nexus] superjjskate:
Yes, now my only problem is that i can't find /sd_images on my sd partition. Is it hidden? Because i tried using Astro, Airdroid and Android File Transfer, im on a mac.

And I am on 1.1 does it still matter?
[Samsung Galaxy Nexus] aron7awol:
Well SD reads are back down to around 22 MB/sec with nightly #8, but regardless, it puts up some awesome scores:

AnTuTu:

Franco #8 @ 1.35 GHz - 6879

Apex @ 1.35 GHz - 6570

Franco #7.1 @ 1.2 GHz - 6390

Apex @ 1.2 GHz - 6012
[Samsung Galaxy Nexus] nrgaway:
Kernel Updater App Icon

Anyone else not getting an icon for the Kernel Updater app? Mine looks like a stock icon. Hopefully it gets updated to something else so I can quickly see it if there is actually no icon (hint; just use your avatar/photo)
[Samsung Galaxy Nexus] franciscofranco:
Icon gets changed in the next app update ;)
[Samsung Galaxy Nexus] Heppieboeddah:
2WCR

Just wondering if any adjusted kernel in future will be able to make 2 way call recording possible?
[Samsung Galaxy Nexus] Redflea:
Any reason for not creating a thread for your kernel in the dev section on Rootzwiki?
[Samsung Galaxy Nexus] zephiK:
Is there a reason why you're promoting RootzWiki on XDA?
[Samsung Galaxy Nexus] jknisley:
You know, I had similarly crappy battery life from AOKP11/Franco 7.1, and it wasn't their fault. Using CPUSpy, I found that the damn thing would never go in deep sleep. Eventually, I tracked it down to an overalarming widget. At this point, I get a decrease of around 4% per hour, which still is a bit on the high side and much higher than people are claiming.

The other thing I'm noticing is that those guys that get tremendous battery life aren't on 4G Data. Oh, their cell signal is on, and it's GSM, which is so much better on battery life, but also Wifi is running. I just turned off all of my radios and took a nap and battery life didn't drop *at all* over two and a half hours.

I'm going to test this wifi thing tonight, actually. On my Droid X, I noticed that battery life when I accidentally left wifi on all night and the thing unplugged was incredibly much better, and it just has the normal EVDOrA radio.

Anyway, my thoughts so far and think that this is a really fantastic, snappy kernel that I see terrific governor response on. Now to just figure out this damned LTE radio issue.

~j
[Samsung Galaxy Nexus] Arrio:
I wonder if overclocking to 1.35ghz will have a noticeable impact on battery life or smoothness of the device.
[Samsung Galaxy Nexus] DJ "suMo*:
Yo Franco, add this in the description for your app... Fu¢k!ng insane!

Sent from my GN
[Samsung Galaxy Nexus] Redflea:
There are a lot of users there who would benefit from knowing about/using this kernel...I've been talking it up on several threads, but having a thread for it in the dev section would make it a lot easier for people to find.

I'm not promoting a site, i'm promoting a kernel...I don't care about and don't get involved in any site-vs-site mentality or activities....we're all here to have fun and enjoy our phones, and I know this kernel will have a positive impact on users.
[Samsung Galaxy Nexus] joshnichols189:
http://rootzwiki.com/topic/10647-kernelgplgsmlte1-jan-francokernel-403-oc-tun-initd-colors/

..what?
[Samsung Galaxy Nexus] nicandris:
franco... franco... franco... ;)
[Samsung Galaxy Nexus] Heppieboeddah:
..what?!

http://rootzwiki.com/topic/10647-ke...-initd-colors/page__view__findpost__p__339526
[Samsung Galaxy Nexus] PresPPsP:
This is a great point. Pardon my ignorance, but could there be a governor like ondemand that with screen on could have 350mhz as a minimum and then 700mhz min with screen off? Seems practical for those that read RSS feeds, twitter, books etc.

Loving this kernel. Great work franco.

-josh
[Samsung Galaxy Nexus] Redflea:
Thanks... :) I'm on CDMA, so hadn't seen that forum/thread in the GSM dev section. Thanks for the link.

Too bad about the CDMA/GSM split, makes it too easy to miss things when items like kernels run on both but are only in one forum, though I understand that Franco likely doesn't want to maintain two threads per site...
[Samsung Galaxy Nexus] mohitrocks:
Wait so undervolting is confirmed working? If yes, what settings have you guys found to work perfectly?

EDIT: Sorry, should have read OP
[Samsung Galaxy Nexus] jknisley:
Well, the kernel intrinsically undervolts, but it doesn't allow you to set it. The device has been unstable with significant undervolts.
[Samsung Galaxy Nexus] just4747:
What overclocking apps do ppl use and what is the best recommended one for the nexus? Set CPU? JRummy's? Another? Any good free ones?

I noticed Set CPU hasn't been updated in forever..
[Samsung Galaxy Nexus] zephiK:
Hasn't been updated but it works. The developer of SetCPU also has a kernel for the GN. He uses one himself.
[Samsung Galaxy Nexus] philsfan:
so are people having good battery life keeping the min set at 700 with ondemand?

my apologies if this has been beaten to death already...

edit: i understand the less steps thing, and it makes sense. Just wondering people's results
[Samsung Galaxy Nexus] rogersnm:
It's called .sd_images, so yes, it is hidden. Also, check to see if the folder /sdcard/Android/data/com.rockstar.gta3 exists.
[Samsung Galaxy Nexus] dr.sonic:
Ok, I'll try like that, thanks.

GNex via tt
[Samsung Galaxy Nexus] nodstuff:
Ya I think when min and Max frequency are the same (performance governor does this) then no matter what you set the voltage to the phone won't crash, until you change frequency!

I remember from the nexus s someone saying that the voltage doesn't change until the frequency changes, it'll always stay at the voltage that was set before until the frequency changes. so ya, set different frequencies if you wanna figure out your voltages.
[Samsung Galaxy Nexus] dr.sonic:
Back on kernel topic, I have random data drops on r185 linaro b2.

GNex via tt
[Samsung Galaxy Nexus] six_dfx:
r185 testing report :

Running for 2 days now at 192/1536 interactive with 1536@1300mV and SR on, not a single reboot/freeze ...

Now for the bad part: I've got a huge battery drain since 185, it eats my battery about 2x faster than previous nightlies.

I've traced it down to a kernel wakelock: WLAN_RX_WAKE

For the 4 hours my phone has been running since unplugged (99% screen off), WLAN_RX_WAKE was held for 1 hour and 35 minutes.
[Samsung Galaxy Nexus] supernova_00:
Exactly the same for me :/
[Samsung Galaxy Nexus] superjjskate:
So, ELI5 how can I find the hidden ".sd_images" folder?

Yes the rockstar folder exist.
[Samsung Galaxy Nexus] rogersnm:
Running ls -la from shell displays hidden files and folders, or just act like it's there and navigate to it (cd /sdcard/.sdimages/).

Also download CatLog from the market and see if there are any messages from sdwatch.

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

To clarify; when this occurs are you still within range of your router, or does it happen when you leave wifi on and then go out? Also, the kmsg log would be helpful.
[Samsung Galaxy Nexus] six_dfx:
It seems to happen only when connected to the wifi AP, I'll try to verify this.
[Samsung Galaxy Nexus] supernova_00:
Still within range as I was at home the entire time. I'll have to get the log tonight when I get back home but what exactly should I do to ensure there isn't hours worth of log info?
[Samsung Galaxy Nexus] rogersnm:
There's nothing you can really do, being selective with what you post might mean important entries are missed. There's no personal data stored in kmsg though, it's just a log of kernel messages.

If you want you can grab the log with root explorer now and upload it via dropbox. (Reboot, navigate to /proc via Root Explorer, hold down "last_kmsg" and hit "send" and then "dropbox". You have to reboot as you can't upload kmsg whilst it's in use, upon reboot kmsg is moved to last_kmsg)
[Samsung Galaxy Nexus] :
Hi,

I am currently testing franco.Kernel-Linaro-R185-b2-512GPU.zip (Thanks rogersnm) and yes in benchs there is an improvement,in UI don't really know maybe it's a little too early (maybe transition/animation?).

With Ondemand/729Mhz-1.53Ghz/LiquidSmooth 1.4 rom:

And in Antutu the score for CPU integer is higher with Linaro...

Without Linaro in Quadrant lowest score for CPU and 3D (and never above 41**),in Cf-Bench about 82**...Wait and see...

:)
[Samsung Galaxy Nexus] hotnikkelz:
Really disliking those omap3 wifi patches. Battery life PLUMMETED with r185. I bled around 30% plus overnight. Usually I get around 1% an hour.
[Samsung Galaxy Nexus] yyz71:
Can I get this Linaro-R185-b2-512GPU.zip? Thanks..
[Samsung Galaxy Nexus] rogersnm:
It's attached at the bottom of my post here: http://xdaforums.com/showpost.php?p=27298380&postcount=19560
[Samsung Galaxy Nexus] yyz71:
Thank you kindly sir :D
[Samsung Galaxy Nexus] jcurtis369:
I went from 181 to 185 and phone started getting super hot looks like its back to m4 for now until the next nightly
[Samsung Galaxy Nexus] sago62:
With 185linaro b2 lose many times the GPS signal ...
[Samsung Galaxy Nexus] giugiu:
+1. Often during night I use 2g + wifi and with latest build I get more consumption than with 3g only.

Ciao

G.

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] P30SiNa:
Wifi eats a lot of battery in r185 but it's more powerful than older releases. I went back to Milestone because I'm getting a great battery life.

My phone is not smooth enough. I'm using Balance profile in franco.kernel app. Is it because I'm using CM9? I tried Liquidsmooth but it doesn't have Persian/Arabic fonts. There should be a language pack around I'll search later.

Well, is it because I'm using CM9?
[Samsung Galaxy Nexus] CaspaTheGhost:
Yeah, I'm experiencing higher WiFi drain with r185. It's 5pm and I'm down to 31% which would normally be two or three hours away...
[Samsung Galaxy Nexus] franciscofranco:
Thats not topic related I didnt release any kernel with that toolchain.

Any kind of posts with problems related with linaro kernel recompiles will not be given any assistance from my part.
[Samsung Galaxy Nexus] Theshawty:
If I'm not mistaken, that's the build a member here did :p
[Samsung Galaxy Nexus] endymion2k5:
I know it probably does not need to be said but please refrain from reporting bugs on the kernel that has been build with linaro. People will most likely get confused by this and franco will not give support on this, lets call it an 'expirimental' build. Use it at your own risk.

Many thanks for building this kernel rogersnm, will give it a shot in a few days!
[Samsung Galaxy Nexus] opethrocks:
A few bugs i would love to see get fixed...

- the earpiece volume bug, in call volume is really low sometimes, it seems like after a notification

- battery life extender not working

Other than that, r181 has been running great, no excessive wlan wakelocks battery life seems on par with other nightlies. And of course its smooth as hell. I know these are known bugs, i just didnt want them to be forgotten what with all this overclocking and linaro talk lately
[Samsung Galaxy Nexus] Theshawty:
I don't know if this behavior is kernel or ROM related, so I'm just gonna try my luck here. Many releases back, like sometime in the end of April shortly after I got this phone, I noticed it heated up severely during just charging without me playing/surfing on it and that stayed with me for a few AOKP/Franco releases but a short while back that completely stopped, which of course is a very good thing!

Could this be kernel or ROM related?
[Samsung Galaxy Nexus] mrasquinho:
I was writing the same as you when I saw your post.

It's an huge bug, since I use a lot phone calls (I think that calls are the main on a phone :p)
[Samsung Galaxy Nexus] jnr21:
+1

It appeared in r180 or r181 if i remember correctly.
[Samsung Galaxy Nexus] mrasquinho:
Nop. I'm using milestone4 and it happens. Milestone4 is #179 I think
[Samsung Galaxy Nexus] yyz71:
I installed it but it reads 384 gpu:confused: Wasn't this 512 gpu ?
[Samsung Galaxy Nexus] Antob125:
Franco you said if the community proved that linaro toolchain was worth it then you would look into it. A very nice member compiled a two gpu versions for testing and the results were amazing. I know you don't like quadrants as an example but maybe you could look into it to see if it's worth it. I think you will see in the past few pages that the community is for it. Even if you don't add it, just look into it please :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] kolyan:
I have volume bug too
[Samsung Galaxy Nexus] rogersnm:
It's 512, I just forgot to change the name in the config.
[Samsung Galaxy Nexus] japaneezy:
So I've been away for a while and using an old nightly and old version of the Franco app so forgive me for being out of the loop.

I just wanted to stop by and say that the gamma control is freaking awesome. I'm currently using 1.6 (haven't messed with the colors yet) on miui with a black icon set and it looks AMAZING. I'm so happy with this display right now. Thanks again.
[Samsung Galaxy Nexus] dr.sonic:
I am back on r181, no bugs, especially no volume bug.

GNex via tt
[Samsung Galaxy Nexus] yyz71:
Thanks again for the quick reply:D
[Samsung Galaxy Nexus] Gahh Its Lee:
Just started messing around with the 512 gpu kernel. My phone can run it perfectly if I bump the voltage to 1300 instead of 1250. Any chance you could add that tiny bit and maybe more of us can run it? If it would affect battery life a lot then obviously not but seems like a good idea to me.
[Samsung Galaxy Nexus] sago62:
I honestly did not notice something worthy of attention ... In addition, the GPS unhooked the signal continuously ...
[Samsung Galaxy Nexus] mrasquinho:
And why am I using milestone 4, r179, and the bug exists? :/
[Samsung Galaxy Nexus] dr.sonic:
I don't know. I usually have about 2 hours of talk time in a day, and didn't notice anything unusual about volume.

GNex via tt
[Samsung Galaxy Nexus] Lambetts:
Bump bump bump!!!

Sorry guys, if anyone knows it would be much appreciated. :-) I've posted this 3 times but it was drowned out by linaro benchmarks, which Franco clearly made known he was not interested. :D
[Samsung Galaxy Nexus] jnr21:
Ok, then i remember wrong.
[Samsung Galaxy Nexus] aeoveu:
Same here - I haven't noticed the bug either.

How are you guys able to reproduce teh bug?

I'm on r181 gpu384 btw.