yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] GinoSylum:
My guess is tweaking down the screen settings in the color control tab and keeping the screen dark. I have messed with everything in the app and played with the power saving setting in my rom (aokp 33) and I max out at 2 and a half screen on time. But I crank up the color and keep it on 100 brightness at all times. I would rather swap out the battery then dim my screen, its just too pretty! :D

And on a side note... Howard Stern?? How 1990 :rolleyes: Opie and Anthony is the only thing worth listening to, they have little Jimmy!
[Samsung Galaxy Nexus] axne1:
My setup is bright. Not a lot of phone calls but mad media,music pictures ect...

I hope this helps.

sent from a Android device :)
[Samsung Galaxy Nexus] axne1:
Trust me I've seen several different setups. They act different on every device. My wife's gnex has the same setup,and is getting the same results!

:)

sent from a Android device :)
[Samsung Galaxy Nexus] sing1gnis:
Opie and Anthony, really? That's funny. :o

My color settings are stock, but I use Voodoo Display. Screen brightness is at 50%. I have one Gmail account syncing and I would consider myself a light user. Still can't get much over 2 hours screen time.
[Samsung Galaxy Nexus] Rootuser3.0:
Yea with extended battery
[Samsung Galaxy Nexus] axne1:
That's the first thing I bought :)

sent from a Android device :)
[Samsung Galaxy Nexus] axne1:
4hrs is the gold standard for kernels on this device... and if you don't have a extended battery... then your going backwards. Jk v;)

sent from a Android device :)
[Samsung Galaxy Nexus] sing1gnis:
What screen brightness are you using? Also, is that with WiFi, 4G/3G?
[Samsung Galaxy Nexus] axne1:
I use wifi every where. But I have some data in there. But usually 50% brightness

100mbp speed in eau claire,wi my house. Charter broadband.

sent from a Android device :)
[Samsung Galaxy Nexus] Gahh Its Lee:
I have two standard batteries if I get the extended can I put the standard in and still use the extended back?
[Samsung Galaxy Nexus] axne1:
Yes its a better fit than the extended back cover! That was shocking :eek:

sent from a Android device :)
[Samsung Galaxy Nexus] Gahh Its Lee:
Sweet I'll have to pick one up I was hesitant because I didn't wanna have to carry an extra battery and back
[Samsung Galaxy Nexus] Flip35:
Which one u guys talking about the 2100 fr android central, I'm trying to buy another batt I already 2 but the regular ones and I saw the one at android central that it really doesn't change the back much cuz I want to be able to still use my cases I have lots of them :D
[Samsung Galaxy Nexus] axne1:
2100 OEM

sent from a Android device :)
[Samsung Galaxy Nexus] TEK112:
The factory extended battery has its own backplate. However, the difference is so slight it is compatible with all standard cases.
[Samsung Galaxy Nexus] axne1:
The factory extended battery leaves a slight gap between the case and the camera lens. That's why use the back that came with the phone

sent from a Android device :)
[Samsung Galaxy Nexus] Flip35:
Yup that's why I want it, I think I saw it on android central, is that the one u guys getting if not would u happen to have a link, thanx

---------- Post added at 01:13 PM ---------- Previous post was at 01:09 PM ----------

is this the one? http://www.shopandroid.com/samsung-2100mah-extended-nfc-battery-w-door/8A37A9667.htm
[Samsung Galaxy Nexus] axne1:
Yep

sent from a Android device :)
[Samsung Galaxy Nexus] mike216:
Really and this doesn't put too much pressure on the battery to the phone? It seems like it would be too tight
[Samsung Galaxy Nexus] Gahh Its Lee:
I'm curious do we have any real data on this battery? Like that'll make so much of a difference doing the math itll give me around an extra half hour of life.
[Samsung Galaxy Nexus] mike216:
Good question. Is the system smart enough or do we have to show it what's there
[Samsung Galaxy Nexus] Gahh Its Lee:
I have no idea when I got my phone at first the battery dies QUICK. One time I accidentally turned it on after it died and it was at 47% again... its been better since. By no means am I saying it did anything could be a total placebo
[Samsung Galaxy Nexus] aliensquale:
Trexcell 3800 extended battery here. Phone lives for around 30 hours usually..screen on time of around 4 hours seems pretty average.. I'm on wifi at home
[Samsung Galaxy Nexus] Gahh Its Lee:
Wait your get four hours screen on??? That's average for the stock...
[Samsung Galaxy Nexus] axne1:
Lol

sent from a Android device :)
[Samsung Galaxy Nexus] TEK112:
Not even close. Average for stock is 2.5 hours. I have the 2100 factory extended battery and I can't break two hours of regular use and I use my phone heavily.
[Samsung Galaxy Nexus] mike216:
This must be all 4g because that would seem about right?
[Samsung Galaxy Nexus] Gahh Its Lee:
I'm just telling you the accepted average is between 3-4 hours depending on signal. I get 3 hours every day with **** service on a standard battery.
[Samsung Galaxy Nexus] thechosen1ji:
I am using that same extended battery and I am seeing 6 hrs screen time on with r141
[Samsung Galaxy Nexus] skrowl:
What are your voltage settings?
[Samsung Galaxy Nexus] thechosen1ji:
Sorry dont know what the village setting are?? lol. I just flashed this kernel using bamf rom 1.2
[Samsung Galaxy Nexus] andrew53517:
I just changed my hi_speed_load from 85 to 95 and I think I made your kernel 2x faster... Idk what it does but wow.

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] wayneb02:
Which extended battery are u using?
[Samsung Galaxy Nexus] thechosen1ji:
Trexcell 3800 mah got it from Amazon for 20.00$
[Samsung Galaxy Nexus] Zacisblack:
IS there such a thing as a tweak to increase digitizer responsiveness? I always notice the lag time between when I move my finger and the action being performed. It bothers me a lot.
[Samsung Galaxy Nexus] ryanbg:
I'm from St. Paul! Nice to know someone other than me nearby uses XDA!
[Samsung Galaxy Nexus] axne1:
651 frogtown! OK back to the thread :)...

Born and raised in St Paul!

sent from a Android device :)
[Samsung Galaxy Nexus] TEK112:
Nope, 3G only and barely any WiFi.

Running: Exchange, Gmail, Currents, Reader, Weather widgets, Prey recovery, Tapatalk, Hootsuite, lightflow and maybe a few I forgot about.
[Samsung Galaxy Nexus] axne1:
I only use a clock widget. That helps me alot.

sent from a Android device :)
[Samsung Galaxy Nexus] TEK112:
I was always curious why people use a clock widget. You need to unlock your phone to see it and the time is already big as life on the lock screen.
[Samsung Galaxy Nexus] Gahh Its Lee:
I like the screen animatiom
[Samsung Galaxy Nexus] TEK112:
Yours animates? Which one are you using?

---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------

You will most likely find that the responsiveness it fine (go into developer options and enable show touches). It is the ROM/kernel that is causing the lag. You can play with settings like turning animations and transitions off to speed up the reaction time.
[Samsung Galaxy Nexus] Zacisblack:
I figured but I'm just wondering if its possible to develop a tweak or multiple tweaks to increase response time. I know Apple has a strict rule where the overall response time must be less than 20ms. I would like to see this improved for Android as well as it would make using our devices much easier. Increasing the Max_events_per_sec definitely helped me some but it only goes so far. A kernel side tweak to increase response time doesn't seem too farfetched.
[Samsung Galaxy Nexus] Gahh Its Lee:
I use beautiful Widgets it gives me the sense style animations. Useless but I like it.
[Samsung Galaxy Nexus] TEK112:
OK, cool. I thought you meant the factory clock widget, that's why I was intrigued. Yeah, I used to run the flip clock too.
[Samsung Galaxy Nexus] dwallersv:
Have you read the OP? Fully explained there. Please ask a more specific question and we'll try to help.
[Samsung Galaxy Nexus] Mandelbrot.Benoit:
So I was finally able to buy the app and have some questions.

V1 gamma offset triple (default -4/0/5, set with 'echo "-10 0 -2" > v1_offsets' for example, causing green tint when 2. value < 0)

In the app are three spaces for Red/Green/Blue. Now the default setting is -10/0/-2 for R/G/B? So if I have a slightly blue tint I can put a -4 in the Blue space only, reboot and see what changes are made. Go to -6 if more is needed? This can be repeated for all colors? Is there a way to see what current values are?
[Samsung Galaxy Nexus] :
You should not be using SET CPU profiles. Especially for screen off.

The TI OMAP 4460 has this feature built in.

If you don't believe me, you can ask Franco
[Samsung Galaxy Nexus] kjwalker:
You quoted the default, -4/0/5.

Changes made are applied as soon as you hit the Clicky Clicky button, no reboot required. Current values are shown in the application.
[Samsung Galaxy Nexus] franciscofranco:
FIOPS is a new IO scheduler. Maybe you get more with my kernel because I have it more optimized? I don't have a direct answer to that :/

Don't need interactiveX, if you want cpu1 off thing that interactiveX offers just use the hotplug function on my kernel, does the same as interactiveX and it works in every governor.

Maybe, maybe not, doesn't cause any issues for me.

Multi-touch is a known bug from ICS/google's kernel. Nothing related to my own.

Btw app issue has been solved, it was just a standard Google procedure.
[Samsung Galaxy Nexus] wallendiaz:
I just did another test with shadowgun, and everything works fine, I think it is a problem of dead space, after I play shadowgun I did a multitouch test and all works perfect, the problem is dead space.
[Samsung Galaxy Nexus] rjskalet:
Regarding the hotplug question. you just run it through adb shell or terminal correct? also after you run it, is there a return that comes out saying its enabled or anything? i have never really messed with kernels other than flashing them.
[Samsung Galaxy Nexus] wallendiaz:
I solved the problem, uninstall and install deadspace and I have no problems with touchscreen, all games are now more fluid, excellent kernel.
[Samsung Galaxy Nexus] Natolx:
Franco, I know you questioned earlier whether it was safe to charge the battery faster than it currently is(1AMP draw) but what about increasing the total draw capability of the phone?

There are situations in the car with e a 1 AMP charger that the phone will drain even while plugged in.

eg. Navigation + Screen on streaming Pandora over 4g. Throw a Wifi tether in there and you're really draining.

Edit: just to note there was a test that showed nexus can only draw 1 amp currently
[Samsung Galaxy Nexus] EyeOfTruth:
Thanks for the info. Its an easy enough test I disable my profiles and leave my max at 920mhz and see if I see a major difference in drain.
[Samsung Galaxy Nexus] tryceo:
How do I enable hotplug in the kernel?

Do I need terminal commands?
[Samsung Galaxy Nexus] sinik420:
Read the op where it mentions hotplug
[Samsung Galaxy Nexus] cancerouspete:
V1 gamma offset triple (default -4/0/5, set with 'echo "-10 0 -2" > v1_offsets' for example, causing green tint when 2. value < 0)

I think there was just some confusion with the sentence structure. Since many of us are from different countries, this is understandable. I personally had to re-read this a few times. It initially sound like, "the default is -4/0/5, you set this with 'echo -10 0 -2'". Would have been clearer (US crowd) saying:

(default is -4/0/5, set with 'echo "-4 0 5" > v1_offsets' for example. causing green tint when #2 value < 0)
[Samsung Galaxy Nexus] Berzerker7:
That's not what interactiveX does. interactiveX is interactive with a <lowest speed slot> min/max with screen off. That + the cpu1 hotplug disable should make for marvelous battery life with the phone in deep sleep.

Also, any chance nightly 13 will have added speed steps like the other kernels have been implementing?
[Samsung Galaxy Nexus] chakra:
Franco has said no he is not going to include a lower speed.
[Samsung Galaxy Nexus] Bayhill Jacket:
@cancerouspete you nailed it, thanks. The colors are perfect for me.
[Samsung Galaxy Nexus] dr_w:
Wow

Fantastic Kernal dude. Thank you for this. Its a night and day difference.
[Samsung Galaxy Nexus] nerdslogic:
How is your battery life guys

Swyped from my Nexus.
[Samsung Galaxy Nexus] kjwalker:
It wouldn't make any difference. The CPU is power collapsed when it is in deep sleep. When it wakes, you want it to do what it needs to do as fast as possible so it re enters deep sleep. That is why capping the screen off speed is not good.
[Samsung Galaxy Nexus] yondercomesthetrain:
Took it off of the charger at 2am last night to see the difference it makes in battery life and then picked it back up around noon today and did some calling and whatnot. Im very pleased with the overall battery life I have with this kernel. Amazing work, Mr. Franco.
[Samsung Galaxy Nexus] axne1:
My response time Is terrific

I feel bad for the people who got a bad device.

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] andrew53517:
Where do you go to increase the max_events_per_second?

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] Zacisblack:
System>Open Build.Prop in text editor. Check to see if it's already there and if it's not add windowsmgr.max_events_per_sec="300" Not sure if that's the max but it is on LiquidSmooth.

EDIT: I also found this. It's not anything I've come across before.

ro.max.fling_velocity=(Any value between 4000 and 12000)

ro.max.fling_velocity=(Any value between 4000 and 12000)

I think higher numbers result in faster scrolling.

---------- Post added at 01:11 PM ---------- Previous post was at 01:10 PM ----------

Mine is terrific too, but I can guarantee it's not as responsive an an iPhone 4/4S.
[Samsung Galaxy Nexus] TEK112:
I can confirm on DTs AXI0M PATIENT ZERO the value of max events is 320 using his CMPLX script.
[Samsung Galaxy Nexus] Zacisblack:
Sooo I came across an app that basically does what I was describing. It's called SGS screen Booster.

https://play.google.com/store/apps/...Nob3A0YXBwcy50b3VjaHNjcmVlbmJvb3N0ZXIuY29tIl0.

It works fine with our phones and definitely seems to increase sensitivity. I can now barely touch the screen and it registers. I'd like to see this worked into ROMS/Kernels.
[Samsung Galaxy Nexus] hajabooja:
Thank you! Conservative back to being default governor?
[Samsung Galaxy Nexus] Metallice:
It's a mistake. I believe he's fixing it.
[Samsung Galaxy Nexus] axne1:
Quadrant scores are down.

First impression just saying :o

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] masri1987:
Wtf is the lazy gov?
[Samsung Galaxy Nexus] spinkick:
Similar to lazy user. The kind that dont use the search button.
[Samsung Galaxy Nexus] masri1987:
Lol we have a jokester.

If I wanted to search I would if. But I'm at work and direct answers are much better than searching.
[Samsung Galaxy Nexus] deaffob:
For me, the default is interactive :O
[Samsung Galaxy Nexus] franciscofranco:
Yes I made interactive the default.
[Samsung Galaxy Nexus] axne1:
I musta missed class that day cuz I didn't know that interactive was the default... lol

:D

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] timbck2:
I'm having Wifi problems again with nightly #143. Anyone else? I'm starting to wonder if it's because I switched to the 512 MHz GPU version (though I don't know what that would have to do with Wifi). I'll try the 384 and see if it helps.
[Samsung Galaxy Nexus] TEK112:
Awesome!
[Samsung Galaxy Nexus] KassaNovaKaine:
Nothing wrong with that question. I just tried quickly searching myself and couldn't find a decent comparison between 'lazy' and all the current ones.
[Samsung Galaxy Nexus] Tree of Knowledge:
14 pages back

http://xdaforums.com/showthread.php?t=1276092
[Samsung Galaxy Nexus] foueddyf:
I'm on 384 and have the same problem since #141. I gotta go back to #140.

Wifi seems to be lost while the phone is asleep because I never lose it while using my phone.
[Samsung Galaxy Nexus] axne1:
I've been stashin my favorite Kernel's for a rainy day :)

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] spinkick:
http://bit.ly/IBAAzt

edit: Just messing around. :)
[Samsung Galaxy Nexus] deaffob:
+1 wifi problem
[Samsung Galaxy Nexus] sway40:
No wifi prob here

~Sent from my GNexus on Aokp~
[Samsung Galaxy Nexus] axne1:
Two Gnex in my house on 143 stable & smooth

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] GinoSylum:
143 (512) working great for me.. no wifi problems, clean and smooth...:cool:
[Samsung Galaxy Nexus] axne1:
One thing that has worked for me is studying the devs, and following them on almost every social platform .

I have only used Franco's kernels

& Romans Aokp builds

so if something goes wrong I can reduce

the "what happened" neways

My family loves that combo, and my battery does too. I get crazy quadrant scores & SUPER crazy battery life!!!

Thanks Franco!

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] timbck2:
I switched back to the 384 MHz kernel (#143) and Wifi seems to work better. I think my phone just doesn't like 512.
[Samsung Galaxy Nexus] cancerouspete:
Running 141 and 512, and no wifi problems, even while sleeping.

Silly question, but under the wifi advanced setting, there is an option for when to keep the radio awake... Make sure this is set to "always", and not sleep with screen off.

Sorry if you already knew, just something to try... I noticed after a factory reset it always defaults to sleep with screen off

Sent from my Galaxy Nexus Toro - BB 404
[Samsung Galaxy Nexus] Flip35:
Same here
[Samsung Galaxy Nexus] mocsab:
First of all thank you for the work you did on teh Kernel - I am using it on my Sprint GNEX and it is working beautifully -

I also wanted to thank you for the Franco Kernel Updater - what an incredible piece of work that is!

I have never had this kind of control at the Kernel Level before - and have always had to use things like SETCPU and or VOltage Control and VOODOO all to do what your one ap can do - well worth the small price you offer it for at the Market.

Just wanted to say thanks- it all works beautifully - and helps me get that much more from this incredible phone.
[Samsung Galaxy Nexus] timbck2:
I'm having another problem, but I can't pin down whether it's kernel-, ROM-, or (yikes!) phone-related. This has happened twice now. I hit the power button to wake my phone from sleep, and the touchscreen is completely nonresponsive. I can turn the screen on and off all day, but I can't unlock or otherwise use my phone. The only way out is to pull the battery. Anyone else seen this?
[Samsung Galaxy Nexus] CruzECO13:
Nightly 143 (384) is running very smooth on my Sprint GNex. Too early to comment on battery life. The app is very neat too. Thanks =]

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Flip35:
iight welcome to the sprint owners, u guys in for a treat with this phone, love it
[Samsung Galaxy Nexus] axne1:
Welcome friends from Sprint

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] pluto22:
The app is downloading milestone 2 not 3. Did I jump on too quick? :)
[Samsung Galaxy Nexus] spinkick:
must have. I got 3
[Samsung Galaxy Nexus] alphanu22:
make sure your app is up to date.

M3 is there
[Samsung Galaxy Nexus] JohnKuczek:
Auto flash downloads M3, zip downloads M2.
[Samsung Galaxy Nexus] azsl1326:
Same issue here. Running latest Franco App.

---------- Post added at 12:56 AM ---------- Previous post was at 12:54 AM ----------

Is Milestone #3 running @ 384?
[Samsung Galaxy Nexus] franciscofranco:
App downloads M3 even if it shows M2 on the download, don't worry. It's fixed on 4.2.2 app update just pushed.

Milestone is stock GPU.
[Samsung Galaxy Nexus] pluto22:
After the app update it downloaded as M3. I compared it to the M2 file I had to confirm if my save of M2 was overwritten and it was. :( Does anyone have a copy of M2? It my trusty fall back kernel when things seem wonky.
[Samsung Galaxy Nexus] GinoSylum:
Go back to the original post of this thread. There are links there for all versions of the kernel. Click on one of the download links and you will see them.
[Samsung Galaxy Nexus] axne1:
I'm staying on 143 it has been crazy great!!!but I flashed m3 on my wife's gnex will report .. if I need. :)

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] pluto22:
I think the milestone 2 on that link is really M3. The size is the same as M3 and the date of the boot.img is 4/26.
[Samsung Galaxy Nexus] Flip35:
Running milestone3, dam it feels really smooth...thanx Franco for this sweet build
[Samsung Galaxy Nexus] axne1:
It is Franco explained it on his updater app...

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] DroidRage1:
I'm getting reboots when pressing the 'stop' button in Google Music, and trying to launch the Amazon MP3 app. Any way to fix this?
[Samsung Galaxy Nexus] Nwkeng:
what scaling governor are most running on milestone 3? I think default is conservative.
[Samsung Galaxy Nexus] innov8ion:
No, it's interactive.
[Samsung Galaxy Nexus] Flip35:
Im running Hotplug
[Samsung Galaxy Nexus] Zacisblack:
Sounds like a ROM issue. Try wiping data/cache for GMusic.
[Samsung Galaxy Nexus] stick1300:
So, if my Scaling Gov. is set to hotplug, should I uncheck the Generic Hotplug setting?
[Samsung Galaxy Nexus] jbdan:
So OnDemand is no longer the gov of choice when wanting the best battery?

M2 and OnDemand has been superb these last 2 weeks
[Samsung Galaxy Nexus] upther:
I've grown accustomed to the 384 GPU so I think I'll stick with 141. Thanks for all your work Franco!!
[Samsung Galaxy Nexus] Zacisblack:
Not sure how you tell the difference. You'd get 1-2fps extra if any.
[Samsung Galaxy Nexus] timbck2:
No I didn't know about that setting, mine was set to "only while plugged in". Thanks for the tip!
[Samsung Galaxy Nexus] upther:
It's probably all in my head, but it just feels smoother.
[Samsung Galaxy Nexus] andrew53517:
So after a well deserved vacation (I think you need one, you deserve it!), what's next on the agenda for this kernel? Any surprises ;)

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] axne1:
Had to flash this milestone after my wife's Gnex hit 3724 and 3703 on quadrant standard this morning after last nites flash!

She has gotten great battery (just like M2) $o thanks Franco. Oh yeah you do need some R&R :):beer:

sent from a Android device :)

I'm always on!
[Samsung Galaxy Nexus] mistawolfe:
Do you have hotplug enabled? If so disable.
[Samsung Galaxy Nexus] franciscofranco:
Im going to draw a roadmap for the next month of nightlies then I will share it with everyone when its ready.
[Samsung Galaxy Nexus] andrew53517:
Sounds like a great plan to me! Thanks!

Galaxy Nexus & ASUS Transformer Rooted!
[Samsung Galaxy Nexus] tacosrdelicioso:
It seems disabling smart flex has gotten me more battery. What is the governor of choice for battery?
[Samsung Galaxy Nexus] Zacisblack:
It would be legit if you could work in TouchWake and Vibration control like in Glados =). Performance first though, of course.
[Samsung Galaxy Nexus] Zacisblack:
FYI I still seem to be getting random data dropouts on milestone 3 =\.
[Samsung Galaxy Nexus] mike216:
Interesting! Could you share your undervolt settings if you did UV? And governor
[Samsung Galaxy Nexus] TEK112:
It depends how you use your phone that will dictate the best governor. For example: hotplug is great if you don't constantly check your phone for updates like I do. For me, hotplug would cause instability and poor battery life. Ondemand is good if you can deal with the initial lag. As I said though, depending on your unique usage it could be almost any of them. Try them all and see for yourself. Just like undervolting, it is very phone/user dependent. YMMV.