yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] monkey hung:
So with 180 at 1.5GHz @ 384 MHz with no change in the voltage or anything, interactive governor and full power the phone ran fine and wasn't running hot. Same thing now with 181 but now the phone is running hot on 1.5GHz @ 384MHz. AOKP B38

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] zjmdp:
if i want using the voltage i set, should the disable smartreflex be checked?
[Samsung Galaxy Nexus] nodstuff:
My situation is the exact opposite!

Running hot on 180 @729/1536 wheatley 384 gpu and running cooler on 181 with the same settings.
[Samsung Galaxy Nexus] monkey hung:
Hmm well I hope Franco takes a look at this

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nodstuff:
Yes and contrary to popular belief it doesn't save battery. Neither does limiting screen off frequencies.

A guy called bedalus did battery tests on nexus s and found that when using lazy governor with screen_off_max_frequency (lazy was the only governor with the option) it saved battery more than when screen of frequencies were limited.

I like how wheatley runs at Max frequency when screen is off. Its all about race to idle.
[Samsung Galaxy Nexus] nodstuff:
Mine hit 97C yesterday so you're all good! :D
[Samsung Galaxy Nexus] metalspring:
I can attest to Wheatley governor not being good on battery for playing music with screen off

I did that last night and it drained 40% for 9 hours compared to maybe 25% with interactive doing the same thing for about the same amount of time
[Samsung Galaxy Nexus] nodstuff:
Ya I agree with you in terms of music, that's a constant task more or less, as in its protracted, whereas syncing or receiving texts etc. etc. Are not constant tasks.
[Samsung Galaxy Nexus] Mrc527:
Franco, why do you removed the /proc/config.gz support?

We cannot recompile with your new settings... Please, take it back to us!:D
[Samsung Galaxy Nexus] jnr21:
I think that interactive is smoother than weathley. I was tested both with 1,5ghz.
[Samsung Galaxy Nexus] rogersnm:
Yep that will do it if you can't get the modified sd card binary to work. You can overwrite the files with Root Explorer or with ADB and then reboot afterwards. (After you reboot you should delete the /sdcard/.sd_images/ directory to regain some space)

ps. most of what's written about "zero point energy conversion" is crap
[Samsung Galaxy Nexus] Remoteconcern:
Interesting. I can run 1.5 at 1350mv, no trouble. If I drop the voltage any lower, smart reflex kicks in and I get instability. I wanted to see how low I could go :D
[Samsung Galaxy Nexus] heo_con184:
+ 1 for this.

I changed back to interactive.
[Samsung Galaxy Nexus] franciscofranco:
I did? If I did it was a mistake :(
[Samsung Galaxy Nexus] flolep:
Indeed... Look at this...

http://www.youtube.com/watch?v=i1x7p-nxvKA&feature=youtube_gdata_player
[Samsung Galaxy Nexus] KingDavid63:
On milestone 4 I'm noticing the volume hack 0-3 don't stick on boot, theoption is still checked but it's not working. I turn on Google music start playing a song, open up Franco app reselect 3 and bam loud and clear like it's suppose to be, here's my problem after I enable the hack after boot my music well only play for a free seconds and cut off.... So annoying everytime, only way I can successfully listen to a song is turn it on hack 1. Any help?
[Samsung Galaxy Nexus] rogersnm:
Looks like whatever you fixed did the trick, 1536 MHz@1375 mV (wheatley) has been running stable for 2 hours whereas before it conked out after 10 minutes. *touch wood*
[Samsung Galaxy Nexus] luckydude:
so why you removed hot plug governor ??
[Samsung Galaxy Nexus] rogersnm:
Read the changelog :rolleyes:
[Samsung Galaxy Nexus] bryant_16:
Can I check, will changing the CPU to 920mhz helps in the battery life?
[Samsung Galaxy Nexus] luckydude:
than x for that , what governor should i choose to do this ? ( shutdown 1 core when screen is off ) sorry for asking questions . i have bought my phone just a few days , before that i had galaxy s i-9000 . i'm familiar with this kind of kernels & etc but in this case i\m a beginner .
[Samsung Galaxy Nexus] franciscofranco:
Being a beginner doesn't mean you can't search.
[Samsung Galaxy Nexus] :
Hi,

Thanks for the update :)

No issue for me with the nightlie r180 about stability at 1.53Ghz (but with Smartreflex off,maybe that helps).

In any case thanks for the 1.42Ghz slot,that give another choice between 1.3** and 1.5** Ghz,perfect!

It's been a long time ago:7KS03602MG147140M ,take a few beers :cool:

+the ability to disable the thermal control in your app and the world is perfect :D

Is a 1.6*Ghz slot is planned?

Great job sir ;)
[Samsung Galaxy Nexus] flolep:
+1 on this one. What are those stability changes you made, Francisco, to let our phones working at 1536?

So happy to attain this frequency with stability. My phone has never been so smooth. 4028 in quadrant. 32 in nenamark2. Well ok, battery is draining but it's ok for me with this performance :-)

With 180, 1536 frequency rebooted with all governors. I tried all. So I was a bit skeptical when some people said that 1.5 was the original frequency of the gnex. I just told me that maybe you could find some trick to stabilize... And... Tadaaa... You made it...

Thanks again Francisco. And thanks too for 1420 frequency that I for sure will use when I want smoothness but a little bit more battery :-)

Keep up the magical work :-)

Take care.
[Samsung Galaxy Nexus] selectah:
Since I updated to MS4 im experiencing mobile data drop issues. It happens when I loose my wifi connection through bad signal. Then it says "no Internet conection" in the notification bar.

Then I have to reboot or whatever? to fix it.

Is that a known problem with m4??

I never experienced it before :( not with ms3 and recently I ran 174 nightly I think.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] bat0nas:
Could you please repeat the URL to procedure how to update the kernel in a proper way?

Something was about wiping something before updating. It was called Erezil Kernel Update Procedure or smth like that.

Thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rogersnm:
See this post: http://rootzwiki.com/topic/13092-leankernel-minimalistic-kernel-380-52712/page__st__9700#entry654031

and this post: http://xdaforums.com/showpost.php?p=23714758&postcount=3251

Just flashing the kernel via CWM should do all the cleaning necessary.

If you still want to flash the reset kernel then you can find it here: http://faux.androidro.ms/ICS-4.0.4-Reset-Kernel.zip
[Samsung Galaxy Nexus] Rovian:
Thanks for adding a higher CPU clocks Franco, the scores are sick! :D
[Samsung Galaxy Nexus] scriptx:
wifi FTL

I've been having wifi issues since #169, with latest CM9 nightly. I'm on M4 now with similar results. I'm not sure if it's an android issue, or the kernel module, nor have I done due diligence to try another ROM, though the problem has persisted across nightly builds of both this kernel & CM9.

Any thoughts?
[Samsung Galaxy Nexus] ploep678:
how can i DISABLE the batterylife extender(BLX)? I want my phone to charge up to 100% for real...

It doesn't matter which value i put in the BLX option in franco's app, the value in /sys/class/misc/batterylifeextender/charging_limit won't change.

How can i set it to 100?

Thanks a lot.
[Samsung Galaxy Nexus] rogersnm:
Try going back to stock, if the issue persists then you should contact Samsung.
[Samsung Galaxy Nexus] franciscofranco:
Heres some nice news for all of you:

5.0:

* Galaxy Nexus

- Wi-Fi PM_FAST works now for the latest r18* or newer nightlies

- Introduced for the first time a panel to create custom Power Modes. It still has bugs, but I decided to ship it like this for bug testing and for community feedback. No Power Mode is set on boot at this time. More options and general cleanup will happen in the next builds. This gave me a hell of a work to make it modular and easily adapted for my likes and for the app progress. Please don't rate 1 star because "OMG IT DIDNT UPDATE SETTINGS UNTIL I REBOOTED THE APP FIX NOW". Read the changelog and you'll be happy
[Samsung Galaxy Nexus] metalspring:
I'm noticing some heavy battery drain on 181, only about an hour and I'm down 45% normally I get around 3 hours total from 100% and with 181 it looks like I'll barely get 2
[Samsung Galaxy Nexus] rogersnm:
I'm currently at 3h20m screen on @55% brightness with 48% battery remaining. Battery drain doesn't seem significantly different.
[Samsung Galaxy Nexus] emd2009:
Same glitch here. Also 181 won't boot on AOKP b38.
[Samsung Galaxy Nexus] metalspring:
Maybe I have to give it more time I suppose, I did just flash a new rom too so that could be it
[Samsung Galaxy Nexus] kompressorgpl:
What ROM?
[Samsung Galaxy Nexus] rogersnm:
Can you pull /proc/last_kmsg after a failed boot via ADB in recovery?
[Samsung Galaxy Nexus] emd2009:
Any help? I also have the same issue.
[Samsung Galaxy Nexus] dpaine88:
Well I'm going back to interactive, 700-1500mhz. Wheatly ran fine but felt slower.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] emd2009:
I'll try and that tonight when i get home.
[Samsung Galaxy Nexus] Mrc527:
Yep, I cannot find it anymore.... :D

I'm still waiting for your next nightly to have it;)
[Samsung Galaxy Nexus] ragnarokx:
I understand Franco doesn't agree with what CM did, but not supporting the ROM isn't hurting the CM team - it's hurting the users.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Rovian:
I have r181 installed on B38 atm without issues whatsoever, had one issue before which was the black screen, but Franco fixed it in no time. :)
[Samsung Galaxy Nexus] schizophrenia:
so I just finished my whole day work and went out using Rmap with r181 ondeman$ 192/15xx. as opposed to my earlier stage with r181, i kept having reboot like 5 times when i was on Rmap. First time it happened after my phone was on and running after 10 to 15min or so... then i started GPS status and moved up the UV from 1375v to 1400v (default) and after 5 minutes it rebooted. then started and rebooted and on. so i went down to 1.4Ghz and tried. another 10 to 15minutes or so and it rebooted again.

It feels to me whenever i have one application running for a certain amount or time or even shorter, it reboots but it was not due to heat because my phone never reached over 70C

i wish i can get a log but Catlog always keeps loading and never show me the log. Somethings is wrong with the log thing

i am sad﻿
[Samsung Galaxy Nexus] mullemulle86:
I dont get the difference between wheatley and ondemand

Which one is better for battery?
[Samsung Galaxy Nexus] bryant_16:
Do I need to wipe davik cache when I flash this kernel?
[Samsung Galaxy Nexus] rogersnm:
Flashing the kernel via CWM wipes the dalvik-cache for you, I don't know what the app does via auto-flash.

There are roms just as good as or better than CM which people can use instead.
[Samsung Galaxy Nexus] vomer:
Franco the change log section is your app still shows milestone 3. Not a big deal but letting you know

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jnr21:
Hit back and go to changelogs again, now it's shows ms4.
[Samsung Galaxy Nexus] Theshawty:
Franco: The Linaro android thing. Will that speed up your kernel beyond all limits known to mankind? ;)

At least I hope AOKP includes these changes :p
[Samsung Galaxy Nexus] mullemulle86:
Could someone tell me?
[Samsung Galaxy Nexus] rogersnm:
For more information look up C states.
[Samsung Galaxy Nexus] ragnarokx:
I've seen people post the same thing about Franco's kernel, but I still want to use it.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rogersnm:
lol good point well made :p
[Samsung Galaxy Nexus] andrew53517:
I'm noticing some faster drain too. But I think I need more testing before I can conclude it's for sure. But it appears standby isn't as good as 180. But still too early to tell.

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] Hanny:
yo franco! thanks for this cool update! :D heres my feedback:

i tried pressing the SAVE button but it just stays on the same customizing screen, if i go back to the settings menu, there are nothing shown in my "custom power modes" list.

furthermore, at this moment if i go back to "Set a custom power mode", the "description" of all rows become blank (like nothing is set). but if i press on them (even the "Name"), it shows the previous chosen value is marked with a circle. If i press on the previous chosen value, the window will pop away but the "description" of that row does not change. It will change when i change the "chosen value" to another. (and back to my desired one if i want it). However, after all these, it still doesnt respond when i press on "Save".

Thats what I got! Yay. Btw, i gave you 6 stars... :cool:
[Samsung Galaxy Nexus] rogersnm:
Exactly the same here, the values stay selected even after a force kill of the application.

Edit: After some messing about I checked and I now have two saved profiles, "Normal" (what I called it) and another called "null".

Edit 2: Also after selecting a custom profile, I can't seem to set a profile under "Franco Power Modes", no matter what I select, it still says "None" underneath and the desktop widget still says null. I can still switch between my "null" and "normal" profiles though.

Further Edit: Even after a reinstall of the app "Franco Power Modes" still appear to do nothing
[Samsung Galaxy Nexus] opethrocks:
Whats your setup? Stock battery?
[Samsung Galaxy Nexus] Gahh Its Lee:
Couldn't run 1.5 on 180. On 181 its running like a beast. A beasty boss I say
[Samsung Galaxy Nexus] PresPPsP:
Wow. 181 working great for me. On 180 using 1536 and early, i would get periodic tennis. Upped voltage to 1450 but didn't seem to help. 181 has been flawless today under the same conditions. Bravo.
[Samsung Galaxy Nexus] wildguess:
Both r180 and r181 won't boot up for me either (stock 4.0.4).
[Samsung Galaxy Nexus] scriptx:
Agreed x2! I'll nandroid today and try out another ROM for the sake of using this kernel, but I'm a CM fanboy, and having the same ROM/resources on multiple devices is a nice win, so I know what's inevitable.
[Samsung Galaxy Nexus] rogersnm:
Stock Battery

AOKP M5

Franco Kernel r181

384 MHz GPU

Wheatley Governor

192 MHz Min Freq

1536 MHz Max Freq

1375mV voltage for max freq

55% Screen Brightness

WiFi and Cellular Data Enabled

729 MHz screen off max freq

Wi-Fi PM_FAST Enabled

XXLA2 Baseband

All volumes at max

I think that covers it, I'm now at 5h20m screen on time with 18% battery left.

I would point out that I'm keeping the screen on for the sake of it by constantly using it in order to try and benchmark battery usage.

And I don't know why the font of my post appears to have changed either :confused:
[Samsung Galaxy Nexus] sert00:
tried not using 192 for the minimum freq?personally with glados e wheatley,and minimum of 400 mhz (liveOC) never had any reboot\freeze
[Samsung Galaxy Nexus] mazubo:
Ohhhhhhh Snap!
[Samsung Galaxy Nexus] nodstuff:
Indeed.
[Samsung Galaxy Nexus] nikulogical:
1.5 made me reboot on r180 but on r181 it seems pretty stable. Stock voltages.
[Samsung Galaxy Nexus] Gahh Its Lee:
That's my experience as well its running great
[Samsung Galaxy Nexus] jcmm11:
I'll confirm that 181/wheatly appears to be stable at 1500 where 180 was causing reboots (stock voltage).

I also agree that interactive seems smoother than wheatly and personally I'll be going back to interactive.
[Samsung Galaxy Nexus] kompressorgpl:
With this setings I had 2 reboots when make a bench test... Had to get to 1400Mhz max
[Samsung Galaxy Nexus] rogersnm:
Finally ran out of juice after 6.25 hours screen time, 5 antututs, 3 quadrants, a few youtube videos, chrome beta web browsing and push gmail. Not too shabby at all :p

I only charge to 96% and took those with 4% left, so if I really wanted I could have eeked out another 30 minutes of screen time.
[Samsung Galaxy Nexus] Diger36:
Now that is pretty impressive :thumbup:
[Samsung Galaxy Nexus] nikulogical:
That's crazy.. I'm losing 10% for every 8mins of screen time with 1.5 Max and wheatley.
[Samsung Galaxy Nexus] jnr21:
2000mah battery?
[Samsung Galaxy Nexus] Diger36:
With r181 things seem stable. Running Wheatley and Max 1536. I do have a problem with a game I play. Airport city. After a few minutes my phone still gets quite hot and starts to lag... That could be just bad programming from the game makers.
[Samsung Galaxy Nexus] Nick87:
Again very noticeable battery savings with Milestone 4 and 192mhz as the lowest treshold and 1344mhz as the highest.

Made a lot of calls today and some facebooking (not much) and still at 67% after 11h41min of battery use.

With Milestone 3 and the 384 mhz lowest cpu treshold I was easily already in the 50% range. So again about a 10% gain it seems.

Good stuff! Really good work Franco!
[Samsung Galaxy Nexus] rogersnm:
Nope stock battery, I listed all my settings here: http://xdaforums.com/showpost.php?p=27105180&postcount=18893
[Samsung Galaxy Nexus] nikulogical:
Did your device get noticeably warm?
[Samsung Galaxy Nexus] rogersnm:
Nope, franco's widget reported the CPU temp as generally being between 35-50C while idle, got up to 90ish during the benchmarks but that's pretty standard. The phone never felt warm to hold.

I spose CPU spy info is good as well: It spent 2h50m at 1536 MHz and 3h20m at 192 MHz, the rest was mostly deep sleep.
[Samsung Galaxy Nexus] dracon6ai:
Just requesting a change on the app. Recently you put the CPU core part to display the current status of the cpus as opposed to being able to toggle them like it used to be. Would it be ok to add the toggle back? Reason being if I'm testing out Wheatly 728-1548 with screen off to 1548 and get curious to see how it handles in single core mode I now have to change the Power Mode to "Power Save", and change my governor, min CPU, max CPU and screen off CPU back to what I had. Where as before I'd just toggle CPU 1 off. I know you changed it for a reason but wouldn't mind that ability again. Thanks again for all the awesome work!

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] olivercervera:
OH MY GOD!!!! I can do max 3h and 30min of wake up display!!!!! (NO OC)

Compliments!

---

Someone can confirm that there are issues with this kernel and CM9? I would like to install this rom but i can't left franco.Kernel!
[Samsung Galaxy Nexus] asim0:
@Francisco please add a 576 mhz slot, and replace that odd 729 with a 768 cause it hurts my eyes :p
[Samsung Galaxy Nexus] xorob0:
Totally agree with you, it'll be used as minimal value without battery drain but with smoother unlock an better idle time.

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] aquavalanche:
Guys, I'm wondering, how much temperature does our phone capable to hold? I watched movie and it gets so hot like 79C on franco app..

Is there any way to reduce the heat without sacrificing the performance?

I don't think I'm gonna try the 1.5 ghz

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nodstuff:
The CPU gets throttled when the temperature goes over 75C to prevent damage.

Mine hit 97C after a lot of benchmarks and gaming and its still fine.

The phone will turn off once it hits 110C to prevent the chip being destroyed.

79C is fine after heavy use.
[Samsung Galaxy Nexus] simms22:
110C. when it reaches this temp, the cpu automagically gets shut off. ive reached this temp quite a few times(with thermal throttling turned off), on purpose of course, to test if the safety feature actually works. and it does :)
[Samsung Galaxy Nexus] rogersnm:
Does SR kick in if you set the voltage below a specified level? I set the voltage to 1335 mV for the 1.5GHz slot but the widget reports that it's running at 1230 mV
[Samsung Galaxy Nexus] Bl4ck3urn:
Is the wheatly governor a big battery saver compare to the interactive one?
[Samsung Galaxy Nexus] simms22:
yea. thats why if you are having trouble ocing you should turn off SR. SR doesnt know ocing, so it tries to keep the voltage to a minimal. problem is, to oc that high, you need more voltage.
[Samsung Galaxy Nexus] jhondidfool:
192-1536 MHz @ 1350mV Wheatley... Stable and butter smooth for the whole day. On 181
[Samsung Galaxy Nexus] rogersnm:
When I set the voltage to >= 1350 mV the widget reports the voltage level I set, however when it's less than 1350 mV it seems to report ~1220 mV. If I set the voltage to 1325 mV (currently at 1330 mV) it crashes out almost immediately.

That's with Antutu CPU stress running the BG to make it use the max freq.

It seems to be something to do <1350mV:

Just got the best quadrant I've ever managed @ 1330 mV though

The kmsg logs show SR calibrating itself even at the 1.5 GHz level
[Samsung Galaxy Nexus] willl03:
Seemed bad for me, back to interactive. Curious to know how it is for the others
[Samsung Galaxy Nexus] nikulogical:
What's the lowest stable under volt settings you guys are using for 1500 step. 1350 seems to be working for me so far.
[Samsung Galaxy Nexus] jnr21:
Wethley drains battery faster than interactive on my gnex. Interactive is smoother too IMO.
[Samsung Galaxy Nexus] rogersnm:
Yep according to kmesg SR is trying to calibrate the 1.5 GHz voltage level when voltage <1350 mV

sr_class1p5_calib_work: iva Stop sampling: Voltage Nominal=950000 samples=10
sr_class1p5_calib_work: iva: Calibration complete: Voltage:Nominal=950000,Calib=860920,margin=13000
wlan0: no IPv6 routers present
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1340000,Calib=1230000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1340000,Calib=1230000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1317000,Calib=1090000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1300000,Calib=1220000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1325000,Calib=1230000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1340000,Calib=1230000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1317000,Calib=1090000,margin=0
sr_class1p5_calib_work: mpu Stop sampling: Voltage Nominal=1025000 samples=9
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1025000,Calib=840000,margin=10000
max17040 4-0036: online = 1 vcell = 3766250 soc = 63 status = 2 health = 1 temp = 360 charger status = 0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1330000,Calib=1220000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1325000,Calib=1230000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1300000,Calib=1230000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1203000,Calib=1000000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1340000,Calib=1230000,margin=0
sr_class1p5_calib_work: mpu Stop sampling: Voltage Nominal=1025000 samples=12
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1025000,Calib=840000,margin=10000
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1325000,Calib=1220000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1300000,Calib=1220000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1317000,Calib=1090000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1203000,Calib=1000000,margin=0
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1340000,Calib=1220000,margin=0
sr_class1p5_calib_work: mpu Stop sampling: Voltage Nominal=1025000 samples=12
sr_class1p5_calib_work: mpu: Calibration complete: Voltage:Nominal=1025000,Calib=840000,margin=10000

sr_class1p5_calib_work: mpu: Calibration complete: voltage:Nominal=1340000,Calib=1230000,margin=0

It seems to calibrate 1.5GHz from 1340 mV to 1230 mV which causes the CPU to **** itself not much later
[Samsung Galaxy Nexus] TyroneLT:
How big is your battery and what was your screen brightness like?
[Samsung Galaxy Nexus] TyroneLT:
How big is your battery and what's your screen brightness