yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] republitarian:
Every time I unlock my phone from a deep sleep its @ 29c-30c either on 143 nightly or milestone 3.....aokp build 33
[Samsung Galaxy Nexus] drawde40599:
Ya im no dev just a guy with to many phones, I don't no about speed scores or hot plug this and UV that, I go by "feel " of actually day to day use and 121 ( using 384, 512 just as good but I don't feel necessary ...) is just perfect no lag no heat, games work flawless, speed is fantastic, battery is crazy good I think 2nd best battery life ever off 121, its also the one I personally keep coming back to, the one I compare all the others 2, I try give all builds at least 24-48 hours of trying out before judging them, that short amount of time don't give the battery life a fare judgment,but dose everything else, don't get me wrong everyone of the builds run great usually as far as I can remember I haven't had any real issues with any build besides heat in last builds .... my opinion; ) appreciate your time @Franco!!
[Samsung Galaxy Nexus] RotxeD:
i totally agree. that kernel release was almost perfect in terms of battery life and smoothness. that, together with r133.
[Samsung Galaxy Nexus] drawde40599:
I forgot about 133, ima retry it but ur right I remember not being able choose between the two 121-133
[Samsung Galaxy Nexus] SrTapir:
I did not noticed a big impact in battery's life with stock GPU, but on the other hand I appreciate a notorious impact on general performance.

I think that you are right on the idea of an OCed GPU in nightlies, but not as convinced to mantain the stock GPU in milestones.. :p
[Samsung Galaxy Nexus] Metallice:
I've been running 192mhz on your M3 and its been working pretty well. Even though I broke custom voltages in the process, I'm still seeing good battery life. From my observations the phone seems very good about hopping in and out of 192mhz to avoid lagging, even with lazy.

FYI to all the people about to say that 192mhz won't save battery... EVEN if 192 and 384 are running at the same voltage, 192 will consume half as much battery. Battery consumption can be estimated as (frequency)*(voltage)^2.
[Samsung Galaxy Nexus] atsavlis:
Anyone know where I can download past nightlies from? I'm specifically looking for 121
[Samsung Galaxy Nexus] raubkatze:
http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/ 512 MHz GPU OC builds in Index, 384 MHz GPU OC in folder gpu_384mhz/
[Samsung Galaxy Nexus] SirOcelot:
We should be as lucky. Franco is the type of developer that has his ear to the ground, and interacts with fans, flashers, etc. If it were up to me, I would have closed the thread, had all posts deleted except mine, and all you would hear from me was my changelog. Of course I would probably be lurking other individual's threads to see what people are saying; we should be thankful Franco is not that kind of developer.

Sit back, relax, and enjoy Milestone 3.
[Samsung Galaxy Nexus] Langduscher:
+1

This can only be said of a handfull of devs. Francisco is one of them.

Thanks for that!

Loving r143 512. Very very smooth, great battery life (now @ 26%, 15h6m since last charge, 4h4m screen on)

Thumbs up!
[Samsung Galaxy Nexus] Hanny:
for all guys that your GTA III is NOT WORKING

for all guys that your GTA III is NOT WORKING

Well got my nexus a few days before and at this phrase im testing out games.

justnow, installed GTA III -> game crashed -> WTF? well but i dont panic, cause i know im excellent at researching.

after messing with it for around an hour, please take some time to read the following:

(unless specified, im talking about version 1.3, which should the latest)

1) please make sure the application package of YOUR GTA is "com.rockstar.gta3" because upon my knowledge / researched results, rockstar has released "com.rockstar.gta3ger" as their version 1.3 which the "ger" literally means german version but apart from this, the version is also considered to be "censored" because blood has been reduced and violence such as kicking enemies on the floor, are REMOVED.

2) however, i dont know which restrictions / variety of "com.rockstar.gta3ger" and "com.rockstar.gta3" apply on different areas / countries / app stores, one thing is clear - in december something like that, which means around the r18 release of franco kernel, franco has made a fix about the inability of executing GTA III. As the time reveals, at that time GTA III was just on its versions 1.0-1.2 stage, and franco directs the fix towards the application package "com.rockstar.gta". Im not going to talk about the reasons why GTA was originally incompatible, go read the first bunch of pages of this thread in december.

3) now thats the tricky point - franco fixed "com.rockstar.gta3", but you installed "com.rockstar.gta3ger" (the official censored 1.3 version from rockstar), therefore your sd card data is not fixed.

4) if you get a 1.2 version of GTA III (i dont know where), you will definitely not crash because it is "com.rockstar.gta" which is successfully directed to the fix made by franco and his sd cracking mate.

5) some of you may ask then what the hell the fix is? well, upon my knowledge i cant really answer this question technologically. but, you will notice a folder called /sd_images in your sdcard partition and inside there you will see "com.rockstar.gta.img" (all these happen after you installed the correct package of it, i.e. "com.rockstar.gta", and downloaded the data from your phone)

6) therefore, to make it work you must confirm that the package name is NOT "com.rockstar.gta3ger" as franco's fix will NOT recognize this package and its sdcard data so your game will fail to run the sd card data!

if you want some REFERENCE, try searching "GTA 1.3 uncut" (which means, the uncensored), on google :)

thanks franco, but regarding the above information, you may be interested to include "com.rockstar.gta3ger" in your fix in next few releases in order to satisfy some of the users :D

still, i just want to say =___= to those who leave such a great (and best) kernel just because of a game but not to invest into the issue themselves...

cheers!! ;)
[Samsung Galaxy Nexus] CaspaTheGhost:
Ondemand, 729/1228, auto brightness, SR on.

On the 512 nightly branch I was getting up to 5h under the same conditions.

Now its time for m5 and m3 to meet...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] willl03:
Awesome, thanks man
[Samsung Galaxy Nexus] rubino90:
Please franco i used your app and kernel my CPU temp id 51 celsius when stay screen on phone is not hot i don't touch smartflex ( id disabled) all stock :( js normal?
[Samsung Galaxy Nexus] drawde40599:
What extended battery r u using?
[Samsung Galaxy Nexus] -viperboy-:
I believe hotplug governor also turns off cpu1 when screen off today. I think that's what Franco and I talked about yesterday.
[Samsung Galaxy Nexus] raubkatze:
I think yes. But for the reason when screen is off, cpu1 doesn't need to.
[Samsung Galaxy Nexus] Metallice:
Hey francisco, I was wondering if you could tell me how your kernel app detects frequencies. I somehow managed to break it. Logcat shows an error with getmhz or something. I can't figure it out. Rom control sets frequencies fine.
[Samsung Galaxy Nexus] franciscofranco:
It reads the frequencies from the file. I will take a look tomorrow, too tired today.
[Samsung Galaxy Nexus] jhericurls:
What have you been doing for 5h 43m, over the 9h period your device has been on?
[Samsung Galaxy Nexus] pastasauce:
Milestone 3 gives some pretty bad drain overnight. Not a wakelock or APP issue, not really sure the problem. It just drops whereas previous versions its steady overnight, 1-2% max. Now it's up to 13-15%.
[Samsung Galaxy Nexus] zephiK:
milestone 3 is all normal to me. what does your battery usage say?
[Samsung Galaxy Nexus] pastasauce:
No wakelocks, and I haven't swapped apps. Haven't even updated Liquid ROM yet.
[Samsung Galaxy Nexus] zephiK:
Not saying wakelocks. In terms of battery usage on battery stats via Android settings.
[Samsung Galaxy Nexus] triStateMindgate:
Something has to be draining if its 10-15% /hr. What do batt stats say, ie Phone Idle, Android System, Cell etc, perhaps one of them
[Samsung Galaxy Nexus] CaspaTheGhost:
Official GSM.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] pastasauce:
Uh it's pretty typical. Screens on top as usual, nothing extremely out of the ordinary. Android OS a little higher than I'd like, but still not extremely high (10%).
[Samsung Galaxy Nexus] spaceman860:
Let the battery drain down then fully charge it. It happened to me to and that fixed it

Sent from my GNex {GSM} T-Mobile
[Samsung Galaxy Nexus] drtrmiller:
"True Black" is now a Bluish Glow?

I'm not sure if this is an issue, or where it belongs, but I think I mistakenly wrote an app developer of a night-time alarm clock yesterday telling them that the "black" background on their alarm clock app was more a bluish glow—similar to a TFT display—which should not be the case on the Galaxy Nexus.

Then, I ran a screen test and discovered that a pure black background with NO soft key glow (I have made my soft keys 100% transparent) and no other elements on the screen, is actually bluish

if you view it in a completely dark room

.

I don't recall the screen exhibiting this bluish property when I first got it, and I played around with the both color control settings and brightness, to no avail.

Is anyone else unable to achieve a "true black" on their Galaxy Nexus, running the latest milestone builds of Franco's Kernel and AOKP?

What could be the cause?

:~(

UPDATE: Found this post in another forum regarding the screen glow. Not sure if it could be fixed in the kernel, but I just never noticed it before yesterday.
[Samsung Galaxy Nexus] drawde40599:
Official huh . OK bye

---------- Post added at 07:21 PM ---------- Previous post was at 07:15 PM ----------

That's the only thing I hate about this phone the colors suck!! Super c only one that has been able to get them looking better but even then his app is beta, if he cant get his app perfected before this htc one x at&t or gs3 comes out this phone going into the pile with the others, anyways, for some reason the 100% stock rom's color dose look different after installing this kernel to me, don't make sense I realize this but on my phone its slightly different ( stock better )
[Samsung Galaxy Nexus] Felixpau86:
Anyone update to Franco MS3 and AOKP MS5... enable usb quick charge and not be able to charge properly via usb?

Using Franco's app to enable... did not enable on the MS5 settings.

Should I turn on quick charge on rom instead?
[Samsung Galaxy Nexus] YoungAceAtlanta:
I don't get how many of you are getting 15hours + with wifi always on

I'm using interactive, smartreflex, generic hot plug

And can barley make it past 6hours with it being on 45%

And yes I have good cell coverage
[Samsung Galaxy Nexus] schizophrenia:
i do have the same question but seems cant find the answer at all
[Samsung Galaxy Nexus] momomok:
Is there any screenshots for BetterBatteryStats?

esp. the partial wakelock and kernel wakelock
[Samsung Galaxy Nexus] hitman818:
What kernel version is this?
[Samsung Galaxy Nexus] drawde40599:
Check 1411 pages back o_O, crazyness

---------- Post added at 08:39 PM ---------- Previous post was at 08:36 PM ----------

Ever since I started charging whenever I was near a charger my battery started lasting longer in between charges I get avg 4 hour screen on time . Don't no if had anything to.do.with but I also let die completely 2 x a week . Try it maybe work for u to, crack flashing also a battery destroyer; )
[Samsung Galaxy Nexus] qballe:
IMM76I official by google , r141 ( gpu @ 384 ) , 384-1036mhz interactive, SR on, no other settings.

TNX FRANCO !!!!! :D

I spent 8+ hours in 3G, talk,mail, brightness auto... m8 is amazing !!

at home using wifi only, I can reach 2 day w/O charge !!! :eek:
[Samsung Galaxy Nexus] schizophrenia:
Just did a quick test after clean install of AOKP M5 and franco M3

running on Interactive on min 384 max 1344, airplane mode. with some UV

lost 3% battery on airplane mode within 2 hours....

and got this strange kernel wakelock "alarm_rtc" that wont stop until i turned of airplane mode

any clue?
[Samsung Galaxy Nexus] DaLoona:
Better watch out with letting it completely drain, li-ion batteries are known to not recharge sometimes when fully discharged.
[Samsung Galaxy Nexus] Frakatchoo:
Same here. Using Apex 1.0.2 and Franco Milestone 2, no problem. Just installed Milestone 3, and have a high battery drain (ondemand). I'm going to try others governors.
[Samsung Galaxy Nexus] jhericurls:
46% remaining after 1day 14hours on, screen time just over 2 hours.

I can quite easily get 2 days but only if I don't leave my house. Wi-fi doesn't use that much power and on idle its about 0.5% drain per hour. Different story if I use 3G.

My device goes to deep sleep pretty much as soon as I switch off the screen

All Google services disabled. Syncing 3 emails account (2 push and 1 hourly), calendar and chrome.

Current setup:

ondemand, smartreflex, generic hot plug, sampling_rate 40000, up_threshold 98, 384mhz - 1228mhz

On Nightly 140, but will be moving back to 121 to see if that is any better.
[Samsung Galaxy Nexus] CaspaTheGhost:
If you mean linux, its 3.0.8...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Go nightlies, special sunday coming up to XDA's table!

r151

* Revert a few patches for stability

* Added 192mhz CPU step for testing purposes

* Disabled RCU_BOOST for testing

* Added a few OMAP4 patches

* Merged some interactive patches from android-omap-3.0

* Added OMAP GAMMA interface from omapzoom. To test this interface run this command: echo X > /sys/devices/platform/omapdss/manager0/gamma where X goes from 5 to 10. The bigger the number the darker the screen will get. Test and report please.
[Samsung Galaxy Nexus] coolzjai:
THANKS FRANCO! I was just flashing the R121 nightlies 1 minutes ago before you release this R151 ;p Hope it is the OMAP stuff causes all the battery drain issues.!! Will report back sooner tomorow!!

Luve ya :)
[Samsung Galaxy Nexus] raubkatze:
We'll test it) Just 15 minutes ago I flashed clean AOKP M5 on my second GNex)

Thanks!
[Samsung Galaxy Nexus] maniac2403:
Was just setting up M3 :) Now starting to test 151. Thanks!
[Samsung Galaxy Nexus] TheSobadef:
DO NOT DO THIS. Do be honest, the GNEX will shutdown before the battery fully reaches 0, but if you let it die completely you could damage the battery.
[Samsung Galaxy Nexus] kout:
I actually did it once, and I'll never do it again, my G Nexus wouldn't boot anymore it would just reach the google screen, and make a little vibration every 5sec (some will know what I'm talking about)

I lost everything, I had to restore an old backup, god bless CWM :o
[Samsung Galaxy Nexus] Gahh Its Lee:
People really need to stop suggesting it. I mean once it maybe helped me? But the fact is that is messes up your battery so destroying your battery is never gonna help it last longer.
[Samsung Galaxy Nexus] raubkatze:
Fashed r151 (512), all cpu values stock, hotplug governor

echo 5 > /sys/devices/platform/omapdss/manager0/gamma

Multipliers: 180 / 205 / 340

Gamma: R -4 / G 0 / B 5

I haven't noticed lags, artefacts etc so far. Waiting for battery life results.
[Samsung Galaxy Nexus] maniac2403:
My setup:

AOKP M5, Franco 151 (384), ondemand, no uv, hotplug

echo 8 > /sys/devices/platform/omapdss/manager0/gamma

Min: 192 Mhz step.

Will provide feedback after few hours.
[Samsung Galaxy Nexus] -viperboy-:
This shouldn't ruin your battery, the phone doesn't let it actually drain down to empty even though it tells you its at 0. Personally, I've almost always let my battery die and when I'm doing a calibration, I always do that too. Never had an issue, my batteries always seem to hold a good charge.
[Samsung Galaxy Nexus] wolfy:
While I have fully discharged my battery fully at some point, and it does help calibration by making discharge statistics available to the OS, I am not fully convinced that it is beneficial overall to the service life of the battery. Fully discharging does heavily stress the battery physically when the battery technology involved is Lithium-ion.

It might not have been an issue for NiCad or NiMH batteries in the past, so the original advice was probably sound, it just doesn't apply in this case.

Source: http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries
[Samsung Galaxy Nexus] raubkatze:
After 11 minutes playing gta3 the temp increased up to 59°C. But for some reason the device is very slowly cools down. Just half an hour later the temp dropped to 36°C. An ambient temp is 20°C now.

I think maybe the problem is min cpu freq 192 MHz? I'll try again with 384 MHz.
[Samsung Galaxy Nexus] leelaa:
How do I run those commands?
[Samsung Galaxy Nexus] raubkatze:
For example using terminal on device.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] leelaa:
I keep getting permission denied when entering them :confused:
[Samsung Galaxy Nexus] jhericurls:
type: SU

before the command

I think 192Mhz is not working out too well for me, spending a lot more CPU time in 1228Mhz.

Well know better tomorrow, as I commute to work and spend a bit of time reading Kindle and listening to music.
[Samsung Galaxy Nexus] nklenchik:
Don't see any difference in performance with 192mhz as my min. Running interactive...report back later today after the gym
[Samsung Galaxy Nexus] xorob0:
192 work fine with me, but undervolt isn't better as 384

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] leelaa:
Still not working
[Samsung Galaxy Nexus] BrUhNiGGs:
Are you sure your doing it right?

Type SU (then press enter)

Echo X > /sys/devices/platform/omapdss/manager0/gamma

Replace "X" with any number between 5 - 10. 6 is my preference, I don't like it too dark.
[Samsung Galaxy Nexus] leelaa:
No I was not pressing enter after typing SU will try again.
[Samsung Galaxy Nexus] leelaa:
Now I get su nit found :confused:

Edit, I done it, I was typing su in caps instead of lowercase
[Samsung Galaxy Nexus] jeremysv:
"su" not "SU"

Commands are case-sensitive in Linux.
[Samsung Galaxy Nexus] leelaa:
I take it these commands don't stick after reboot
[Samsung Galaxy Nexus] BrUhNiGGs:
I just emphasized the "su" so he could get it...
[Samsung Galaxy Nexus] BrUhNiGGs:
Its for testing purposes for now
[Samsung Galaxy Nexus] maniac2403:
CPU spy tells me that the phone is only at 192Mhz for 10 minutes out of 5 hours of standby and light music. Don't think it's helping much.
[Samsung Galaxy Nexus] drawde40599:
It won't damage anything!! I do it all the time, been doing it for years and my battery's are just as good as the first day ..... btw when u buy an extended battery they tell u to do this, and do it once in a while ...... mugen .
[Samsung Galaxy Nexus] meilstone:
Well you need an init.d script if you want your settings stick after reboot.

Pls correct me if im wrong. but it must be right. same procedure as hotplug mod if you don't use the Franco App.

Feedback:

Using n151 with AOKP m5. Everything is fine. Except the Wifi. It has some troubles if i wake up the device. 192 mhz seems to be unnecessary.
[Samsung Galaxy Nexus] m.alkhalel:
im getting alot of wakelocks on 143 and relatively worse battery life comparing to 142, gonna try 151 now and i hope it helps with the damn wakelock. PS THX for your great work =)
[Samsung Galaxy Nexus] BrUhNiGGs:
How in the hell did you get 4 days of battery life?! How much screen time?
[Samsung Galaxy Nexus] BrUhNiGGs:
So is the 192mhz min supposed to conserve battery life at the cost of less performance? I don't really see a difference in performance. Working good so far with 192 min and 1344 Max with interactive. See how battery life is today.
[Samsung Galaxy Nexus] drawde40599:
color

Aokp M5, nightly 151, screen at 100% brightness, color setting 5 looks the best to me, then add voodoo cold and it looks pretty damn good; ) haven't had long enough to give any feedback but ....
[Samsung Galaxy Nexus] SupWiz17:
Flashing the new kernel now. What is the default value for the OMAP GAMMA command?
[Samsung Galaxy Nexus] drawde40599:
It said 0 if u look in folder...
[Samsung Galaxy Nexus] franciscofranco:
Try 192mhz with Lazy. Interactive is a bit more aggressive thus not using 192mhz a lot.

Its just a small test.
[Samsung Galaxy Nexus] twissii:
What are your settings ?

its amazing... i use Glados 1.30 kernel and get 5 hours screen time and a litte bit over one day.. please tell us how do you do it :)

Greetings from germany
[Samsung Galaxy Nexus] drawde40599:
I use voodoo color, so not really any help but after playing for last hour I like stock color best with voodoo, and for your testing I like #5 .....

@Franco is it normal for your app to read temp of sayyyyy 57°c wen u first open it then it drops down really quick to lower temp? Same frequency....
[Samsung Galaxy Nexus] m.alkhalel:
2 hours 2 mins 24 sec

---------- Post added at 09:10 PM ---------- Previous post was at 09:04 PM ----------

ROM : black ice 33.33

max 1344 MHZ

min 729 MHZ

interactive governor

no UV

Generic Hotplug, Sqlite, turn logger off : checked

screen on : 2 hours 2 min

its good and all, but still i had better with 142 and when i had not as much wakelocks
[Samsung Galaxy Nexus] Diger36:
R151 with Lazy and 192 gives me a lot of stuttering and lag. Trying different governors now.
[Samsung Galaxy Nexus] jhericurls:
Do you switch off Wi-Fi and data when your not using your phone?

I found it to be a bit laggy with OnDemand too. Also there was no point using Interactive as it would be a false economy, as you would be spending more time in the higher frequencies.
[Samsung Galaxy Nexus] BrUhNiGGs:
I'm using 192 with lazy. Doesn't seem laggy to me. For nowwww
[Samsung Galaxy Nexus] Gahh Its Lee:
Do you have CPU spy? I'm curious how often it'll even stay at low frequencies.
[Samsung Galaxy Nexus] ArmanUV:
Hi franco, Can you enable the wifi management option in your app from imoseyon kernel? it supports it now.
[Samsung Galaxy Nexus] Diger36:
Found Ondemand to be stuttering and lagging too. I'm back to 384 min for now.
[Samsung Galaxy Nexus] drawde40599:
Color

@Franco. U still have a nexus one? I use air kernel on mine, version 65 fps +blue, and the colors on that kernel r freaking beautiful!! I don't no anything about the colors besides that I really like them ( dose it take voodoo??? Is it even possible on this phone?? I dunno but If ur testing / looking at color tweaks give it a look ......

Been running 384 oc build 151 version for hours now, none stop, out the box settings, no heat issues no lag, its smooth, fast, clean, I like it better than M3, dunno bout battery I'm probably not the best guy for feed back on battery since I don't really care . Great build so.far thanks agn
[Samsung Galaxy Nexus] m.alkhalel:
yes, ofcourse i do , switching 3g/wifi on/off with advanced power control is just 1 click away :D
[Samsung Galaxy Nexus] -viperboy-:
I like ondemand, a good combo of settings that will give you good performance and good battery life with no lag would be:

Sampling rate: 50000

Up_threshold: 90

Down_threshold: 60

It was smooth on my GNex before I switched to hotplug.
[Samsung Galaxy Nexus] motoman234:
I'm really digging the new 192 frequency. Most kernels that have that low of a frequency tend to have some occasional lag, but your kernel isn't skipping a beat. Thanks for this beautiful kernel man! Now to see if I can crank up the brightness a bit.
[Samsung Galaxy Nexus] nklenchik:
r151 feedback: min 192 and interactive

At the gym for 90 minutes with 3 bars of signal and lost 8% on battery. That's listening to music and changing the song every 5-10 mins, occasional texts. Lets see how idle goes now
[Samsung Galaxy Nexus] Metallice:
People... underclocking is like overclocking, your phone may or may not like it. If your phone refuses to spend time in 192 or you experience lag, your phone probably doesn't like the 192 freq.

View attachment 1031670

Also I'll say this again... even if 384mhz and 192mhz are running at the same voltage, 192 will still consume half as much power as 384mhz. Battery consumption can be estimated as (frequency)*(voltage)^2...
[Samsung Galaxy Nexus] nklenchik:
Haha are you using your own custom Franco kernel?