yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ChazzMatt:
It's stupid when "disble wif-fi on sleep" is the default setting. In Froyo two years ago, when I found that setting and DISABLED it, my Android phone was so much more useful! I couldn't figure out why my phone kept having to connect to the wi-fi network every time I touched the screen. No emails coming in, no social media updates Frustrating! And in that OS, that setting was in such an obscure place, it was ridiculous. :rolleyes:

Now the first thing I check is to make sure my wi-fi stays on all the time. I'm on wi-fi most of the time (at home and work). So, if wi-fi does not work when the screen is off, my phone is USELESS.
[Samsung Galaxy Nexus] stegg:
Milano, Wind, I had the issues yesterday, H+ icon not showing and data connection dropping (ie no blue bars).

today it seems ok! :confused:
[Samsung Galaxy Nexus] tobitronics:
There is one thing I dont get. The hispeed-freq of M6 is 729 mhz but the input-boost is 1036mhz. That would mean that if the cpu gets above the given load it would go to 729, but every time i touch the screen it would bump to 1036. Isn't that strange or am I thinking wrong?
[Samsung Galaxy Nexus] finger11:
Flashed M6, lost all my data too. Boots just like a factory reset.
[Samsung Galaxy Nexus] :
Just wanna make sure I got this correct. Smart reflex is disabled on the GPU correct? Still there for CPU though?
[Samsung Galaxy Nexus] whisky_:
Anyone got an answer for me?

My phone has this issue where at times I can't swipe through screens quick enough because the phone can't keep up with my fingers. This happens only sometimes and goes away by its self in a while or if I reboot my phone. So while I'm swiping through screens, the phone won't register the speed of my finger and just swipe normally or open an app by accident because it thinks I tapped on the icon instead of swiping. It gets annoying. Very annoying. Has this happened to anyone else?

I'm not running any memory intensive apps. For what its worth, it'll fix its self with the browser and an app or two open at times.

I'm running the latest CM10 nightly with Franco milestone 5 kernel and I don't think I've ever experienced this with the stock kernel from JB or CM.

EDIT: Just updated to Milestone 6. So far, no issues. Fingers crossed.
[Samsung Galaxy Nexus] shreddintyres:
There is nothing in the update script that would have precipitated that. Either you accidentally told your phone to factory reset in recovery or something got borked in your recovery.

what were your steps when you flashed the kernel?
[Samsung Galaxy Nexus] zephiK:
no

10char
[Samsung Galaxy Nexus] inffy:
Yes conservative is better in normal use.

If you do benchmarks all the time...then interactive or ondemand are right choices.

In normal everyday use -> choose conservative
[Samsung Galaxy Nexus] chikimonke:
App Requests

Franco, thanks again for the great Kernel. Two requests for your app though.

#1 - Can you add in a "Are you sure" type prompt to the reboot into recovery option? This way an accidental press of that option doesn't immediately reboot the phone? Especially with Kernel Settings and Overclock being on either side of the option.

#2 - Any chance of a widget or two? Something like SetCPU only add in which governor is being used. Or maybe another that would show you the pie chart of time spent in each state. And so you it can stay a 1x1 widget, don't put a legend in the widget, just have Red represent the fastest step, and move towards the cooler colors as the steps get slower.

Just some thoughts and wishes. I rely on talented individuals like yourself to pull these things off, as it is not in my skill set.
[Samsung Galaxy Nexus] franciscofranco:
The first is planned as its easy, the second one is quite cool. Starting next week I plan to add tons of new features to the app, and your second idea is something I'd like to add. Thanks.
[Samsung Galaxy Nexus] aron7awol:
I actually notice no difference in battery life between interactive, ondemand, and conservative, but I do notice a big difference in responsiveness on interactive. For this reason, I recommend interactive for normal usage. If you are super worried about battery life, lower your brightness. That will make a huge difference.
[Samsung Galaxy Nexus] apsis:
Hey Franco, again great update on your Kernel. Its almost perfect for me, great battery life and great overall perfomance. I would like to buy your app, but i dont have an creditcard registered, is it possible to get your app via Paypal?
[Samsung Galaxy Nexus] franciscofranco:
Argh I didn't have time yet to set that up, been pretty busy with real life =/
[Samsung Galaxy Nexus] bradm23:
Letting new kernel settle in, thanks for the update. So far seems like performance is about equal with 10. Seems like battery is a little worse in sleep, but better during use. I don't like to jump to.conclusions so I will report back once I get a full cycle.

. I

---------- Post added at 05:27 PM ---------- Previous post was at 05:24 PM ----------

Franco, have you received any feedback on the camera issue draining battery. If this is an issue, will deleting Google talk solve the issue so we don't have to open and close the camera each reboot?

Thanks!
[Samsung Galaxy Nexus] nic85:
so interactive is the best also for daily usage?

franco what do you think? :o
[Samsung Galaxy Nexus] aron7awol:
Yes, in my opinion. I notice everything is just a bit snappier for me running interactive, and like I said, it doesn't seem to affect my battery life in any noticeable amount.

Everyone has their own opinions on this matter, that's why you can change them. Try them all and come to your own conclusions.
[Samsung Galaxy Nexus] dpaine88:
I would assume he thinks the best settings are the ones that came with the kernel.

If it is set to 700-1200mhz as it comes with, I dont think the governor would make a huge difference since 700mhz should be enough to keep most tasks smooth. Thats probably why he chose conservative, and I believe he tweaked it as well.
[Samsung Galaxy Nexus] mfish123:
I really would love to have my dump analyzed. Are you talking about this general thread for the app: http://xdaforums.com/showthread.php?t=1179809&page=229

Or is there a thread specifically for this app in the Galaxy Nexus - if so, unfortunately I can't seem to find it.

Thanks in advance
[Samsung Galaxy Nexus] FormelLMS:
Can anyone please explain me, why we have a minimum from 700 mhz?

Isn't it a battery killer to let a cpu run on this speed, as it can run much lower when its not in use?

Send from my iphone5s
[Samsung Galaxy Nexus] dpaine88:
If you go back like 10 pages, theres a post with 4 great reasons in separate paragraphs that explains this extremely well.

I have been getting great battery life at 700-1200 conservative.
[Samsung Galaxy Nexus] RVDigital:
This test caps the end of this testing period. As most devs are now loading the latest and major Linux Kernel updates, the cycle needs to be started over. Additionally, the Stress Testing will become a little more "stressful" in an effort to better be able to calculate a real wold estimate.

NOTE: In fairness, Franco's Kernel Tested here IS NOT the most current one, IMOs IS and includes the final Linux Kernel updates.
[Samsung Galaxy Nexus] VoicesX:
Anymore have reboot with Google images (browser)????

Enviado desde mi Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] aron7awol:
What did you have your brightness set to during the stress tests?
[Samsung Galaxy Nexus] fatsix:
Changes in franco.kernel app appear to be sticking after reboot. Thanks!
[Samsung Galaxy Nexus] RVDigital:
Great Question!

All stress tests are done with the min screen brightness. For the SetCPU test, the screen remains on for all tests.
[Samsung Galaxy Nexus] Dr_Ownage:
thanks, mustve missed it while skimming past this morning :)
[Samsung Galaxy Nexus] shawnaye:
All the tremendously positive reviews about m6.

Next thing Franco is gonna say that m6 is actually r273! Haha.
[Samsung Galaxy Nexus] davidukfl:
i will say m6 is running super smooth. Only thing holding it back is the random data dropping
[Samsung Galaxy Nexus] finger11:
Downloaded the kernel with the Franco app, went into ROM manager (latest version) and flashed the zip that the app downloaded with ROM manager. I checked the boxes to clear cache/davlik.

Update: I let the Franco app download and flash/reboot and it worked fine.
[Samsung Galaxy Nexus] goldleader:
+1 on the Milestone 6 is smoother than my gf's p**** :D I'm one happy camper, great job Franco!
[Samsung Galaxy Nexus] Jebus99:
Sorry if it's been asked before but does the change to the interactive governor's frequency change thread priority apply to the dyninterractive governor too?
[Samsung Galaxy Nexus] dannejanne:
I believe you are facing this bug:

http://xdaforums.com/showthread.php?t=1576739

Does turning off & on the screen fix the issue? If so yeah it's that bug. Solution is to raise the gamma of the screen.

Tapatalked
[Samsung Galaxy Nexus] shooter365:
How to copy my kernel before flashing franco ones?

Gesendet von meinem Stock Jelly Bean 4.1.2 GN
[Samsung Galaxy Nexus] rye&ginger:
Had this as well now. Was plugged in over night. My WiFi setting is on while plugged in. Toggles do not work, go in and out of the WiFi settings and you can see that. WPS button gives error.

Let me know if a certain log will help.

M6 with CNA 3.6.5.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] SahilC:
How much screen on time are you guys getting on the latest kernel? :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] SUTHRNFRIED:
Depends on how you use your phone. I've always got 2-2.5 hrs on with 16-18hrs usage on every Franco kernel. Milage will vary per person.
[Samsung Galaxy Nexus] Hatshipuh:
Franco Updater App got a backup/restore function, otherwise depending what kernel you were using before, you can get it in the belonging kernel thread.

Tap-a-talked from my Galaxy Nexus
[Samsung Galaxy Nexus] MontyQ:
Never flashed a kernal before seems simple flash zip in cwm like all other stuff then wipe cache and dalvik and reboot....

If I flash it as is and dont play/ overclock or touch anything well I get better batttery time over the kernal in PA, whick is cm10 one also well colours on my phone look better then on the cm10 one as they seem to e abit yellowy/geenish

thing is I wanna do this and leave it not play with it for hours to see tiny changes in colour/battery

any ideas about use it as is please chime in....thnx all for the help
[Samsung Galaxy Nexus] Wynnded:
Agreed, using the Franco's App would be the logical first choice. The second choice might be making a nandroid backup to return to.
[Samsung Galaxy Nexus] sruel3216:
i have had 3 full cycles now with m6 and each one gets better. you really need to be patient and have it settle. performance is insane and my idle battery is amazing on 4g lte
[Samsung Galaxy Nexus] willl03:
M6 is simply amazing, I run interactive 384-1036mhz + v6 supercharger and its just as smooth as an overclocked performance governor. I get 4h screen on time over a day
[Samsung Galaxy Nexus] EDNYLaw:
Franco's stock settings are pretty nice for battery and performance. Of course, silicon varies, so you may find that his "stock" settings aren't the best for you. However, they are pretty nice all around settings. Color is again, up to you. You may find his color too much of one thing or another. If you want a great kernel, flash Franco's kernel, if you want to tweak it, do that too. I have absolutely no complaints about his kernel and I've been using it for about a year.
[Samsung Galaxy Nexus] mr4r4n:
What's s v6 supercharger?
[Samsung Galaxy Nexus] SUTHRNFRIED:
http://lmgtfy.com/?q=v6+supercharger
[Samsung Galaxy Nexus] Coolgoly:
It's a memory management script
[Samsung Galaxy Nexus] sruel3216:
its not needed on this device. its for better performance that older phones benefit from. this phone has plenty of memory
[Samsung Galaxy Nexus] Tarun95:
I went back to stock and realised that Google can't do a job like Franco. This **** is way faster than stock !! Not joking here. Damn serious
[Samsung Galaxy Nexus] MontyQ:
ty for the info :)
[Samsung Galaxy Nexus] msmall22:
M6 has broken my gps, flashed back to 183 and all is fine with world once more.
[Samsung Galaxy Nexus] bradm23:
GPS was first thing I tried, works fine here. Try turning on GPS and give it a few minutes. If that doesn't work, they downloading gps stats from the market and reset your signal and see how many satellites u are viewing.
[Samsung Galaxy Nexus] franciscofranco:
Nah doesnt broke any GPS sorry.
[Samsung Galaxy Nexus] gianton:
GPS works fine here, on CNA 1006 nightly.
[Samsung Galaxy Nexus] Kurre:
Maybe, but I enjoy not having launcher redraws every now and then ;) well that's actually achieved by services.jar hack but anyway..:)

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] MontyQ:
TY first kernal flash ever my PA (cm10) kernal phone colours were yellow/greenish now they look normal lol like I would want then too

ty to all who answered my questions and helped out
[Samsung Galaxy Nexus] Steve46xda:
Can someone explain me how Smartreflex works? If I modify voltages (with franco's app) in OC/UV section, smartreflex will continue to work or will stop? Modifying UV I fix a voltage for every frequency or I just put a lower threshold to voltages so they can't go down over that level?

Thanks!
[Samsung Galaxy Nexus] !crazy:
It is like you said. What have you found strange?
[Samsung Galaxy Nexus] shinkeel:
This is caused by CM10 parts, this is setting mistake from default, ( advanced -> CMColours ) and set colours like that 400, 400, 400 ( twice over security screen burn-in value ) , this is why you have screen "so yellow", you can set down this value or can use franco App or Trickster for set it right, same problem with leankernel and fugu, trinity don't suffers this bug because IMHO don't have CM10 compatible sys interface ( and Cm10parts can't modify it color )
[Samsung Galaxy Nexus] tobitronics:
The whole story. It would mean that my device is running permanently on the input speed, which is 1038. My question was if this is right or that my thinking is wrong.

Beamed from my Google Galaxy Nexus
[Samsung Galaxy Nexus] msmall22:
I didn't think you'd done anything that would affect it, I'll keep investigating.
[Samsung Galaxy Nexus] F_T_B:
That's what I actually meant. Some ROMs do have it set by default, which is plain stupid (yet again I repeat myself) for someone using Android like a normal person that has Wi-Fi around the house, and doesn't want to waste cellular data when the phone is sleeping which for instance happens when people sleep, or so I think. Rant over.

Some ROM-related problems affect all kernels, so make sure it's not the ROM's fault first. Franco works on just one ROM to develop this kernel, so keep that in mind when not everyone has the same problem.
[Samsung Galaxy Nexus] ChazzMatt:
No, more likely it's r276. : ;)
[Samsung Galaxy Nexus] !crazy:
Permanently? This is what you wrote: "...but every time i touch the screen it would bump to 1036." So when you touch the screen it jumps to 1036 (or you can choose different frequency.) and then behaves as usual governed by other parameters.

You can disable ti if you don't like such behavior. Here is the link to docu where you can find more:android-tuna-omap / Documentation / cpu-freq / governors.txt
[Samsung Galaxy Nexus] RoscoeDpG:
M6 runs great and makes everything smooth, i went back to 281 because i feel like that one gives me best batt for my usage but im gonna give them both another run see how it comes out 2nd time around
[Samsung Galaxy Nexus] IAmAN00bie:
Think of SR like dynamic undervolting. There are two values, the nominal voltage and the calibrated voltage. The nominal is the upper threshold and is the value you see in the UV settings, while the calibrated is determined by the system and is the lower threshold the device will go to. SR will dynamically undervolt between the upper and lower limit. If you lower the settings in the UV tab while leaving SR on, then you are lowering the nominal voltage. This can be problematic because then the system might lower the nominal voltage lower than your phone can handle, and you would get an insta-reboot. So if you plan on manually undervolting, disable SR.
[Samsung Galaxy Nexus] Coolgoly:
Disabling smartreflex can fix my problem?I can't undervolt on M6 because phone crashes.

Sorry for the repeated questions.
[Samsung Galaxy Nexus] Leegalaxy:
It seems like the drain from r283 immediately stops after I flashed r284 test.
[Samsung Galaxy Nexus] franciscofranco:
Suggestion: stop undervolting, Smartreflex does its job.
[Samsung Galaxy Nexus] simms22:
short answer, yes. disable it if you want to undervolt. longer answer, i never undervolt, yet i am extremely happy with my battery life. undervolting can lead to your device using more battery instead of less. instead, i underclock when i want my battery to last a long time. usually i set it to 1036mhz(trinity), its still snappy at that speed yet battery juice seems to last longer. this is with all kernels, not just what i use(trinity). francisco is right, smartreflex does its job.
[Samsung Galaxy Nexus] franciscofranco:
From now on I will doubt anyone claiming bad battery life. Max brightness, stock kernel settings lots of wifi and 3G.
[Samsung Galaxy Nexus] gianton:
Impressive! Which ROM?
[Samsung Galaxy Nexus] IAmAN00bie:
Proof? Why would it use more battery instead of less? That doesn't make any sense at all. Undervolting can lead to stability issues, but it definitely does not cause the battery to drain more - because by definition the CPU is drawing less power.
[Samsung Galaxy Nexus] tobitronics:
I wish i had it like you. Today on auto brightness, some 3d gaming and 2d gaming, some twitter and facebook and xda, lots of wifi, little 3g and got 2.5 hours when i reached 10% left. I notice that my battery drains as fast in standby as that it does when in use. Maybe it's wakelocks? How can I check if I have them?

Beamed from my Paranoid Google Nexus 7
[Samsung Galaxy Nexus] gianton:
Install Better Battery Stats and check your kernel wakelocks.
[Samsung Galaxy Nexus] franciscofranco:
MiNCO v5.

Betterbatterystats app. Its probably FB app ****ing your idle consume.
[Samsung Galaxy Nexus] gianton:
It must be a hot couple with M6! Lol!!!

BTW, customizations like battery percentage is included in Minco v5?
[Samsung Galaxy Nexus] osm0sis:
If I recall correctly, the way I saw it explained previously was that undervolting a frequency after a certain point might not be unstable but basically makes it "brain damaged" so that when it's on that frequency it has to work longer, and since operations take longer they take more battery.
[Samsung Galaxy Nexus] cassius_20:
M6 is smoother than butter on some teen a**:)

Heres my results. Currently using dark paranoid android (was on minco v4; had to see what the whole fuss about hybrid mode; gotta say, very impressed). Stock default kernel settings/no uv or oc. 4 hours easily attainable. M6 is very well behaved.

Screenshots
[Samsung Galaxy Nexus] simms22:
if the cpu is drawing less power but for a longer amount of time, in the end its using more power. its especially noticeable if your device is on the very edge of stability.

---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------

nice post number :D
[Samsung Galaxy Nexus] ac3theone:
this kernel supports int.d right?
[Samsung Galaxy Nexus] simms22:
init.d is something that your rom has to support, not the kernel. anyways.. http://xdaforums.com/showthread.php?t=1912504
[Samsung Galaxy Nexus] ac3theone:
thanks
[Samsung Galaxy Nexus] simms22:
thats for the nexus 7, maybe itll help with your galaxy nexus.
[Samsung Galaxy Nexus] osm0sis:
Actually, I think it can be one or the other. Stock isn't supposed to support init.d, but with franco and busybox installed to xbin it works for me.
[Samsung Galaxy Nexus] simms22:
it can be one or the other, but most kernel devs leave it for the rom devs to do. adding init.d support can be a separate flashable too :)
[Samsung Galaxy Nexus] IAmAN00bie:
Undervolting will NOT compromise performance at all. Underclocking and Overclocking (clock speeds) is whats responsible in regards to performance. Benchmarks will also prove that performance remains the same. Most beginners usually think and assume undervolting will sacrifice performance but they are wrong. Therefore, more power CANNOT be drawn. The CPU does not work any harder because it is drawing less power.

http://forum.notebookreview.com/har...arket-upgrades/235824-undervolting-guide.html

Your CPU either does/does not run at a certain frequency/voltage. 1s and 0s.
[Samsung Galaxy Nexus] irminsul:
You probably remember Bedalus did a study for the Nexus S with amp meters and stuff. http://xdaforums.com/showthread.php?p=22126792#post22126792

As the hummingbird isn't the same as the omap4460, I think it's reason to believe similar conditions will occur on the Nexus prime.

Undervolting is causing more troubles then it gives you the benefit of more battery life.
[Samsung Galaxy Nexus] IAmAN00bie:
Right, undervolting can cause stability issues, but the argument here is whether or not it increases/decreases battery life. By definition of what undervolting does to the CPU, less power is drawn. The CPU does not have to "work harder". That is a misconception. Undervolting does NOT affect performance. It DOES affect stability, which is quite obvious if you start undervolting too low.
[Samsung Galaxy Nexus] simms22:
thats written 4 years ago for notebook undervolting. and since when is stuff found online always right? i can only speak from my experience with undervolting.
[Samsung Galaxy Nexus] IAmAN00bie:
Undervolting is undervolting. The principle has remained the same for decades. Your experience without any hard numbers does not disprove the math and many tests that prove undervolting saves on power draw. If you want to keep telling people that it brings instability, sure go ahead, because it definitely can. But without any proof to backup your claim about increasing battery drain, your claim is invalid.
[Samsung Galaxy Nexus] simms22:
anyways, thats cool. enjoy your undervolting :)
[Samsung Galaxy Nexus] IAmAN00bie:
Just remember, P = C *(V^2)*f ;)
[Samsung Galaxy Nexus] irminsul:
Look at this link

http://xdaforums.com/showthread.php?p=22126792#post22126792 these are test with a semi-scientifically set up amp meter plugged in to a Nexus S proving that extreme UV costs more power. With moderate uv no more than 2% of battery was saved, and guess how many battery only one single reboot caused by the uv will cost? Exactly. As simms said, enjoy your uv we will enjoy our stability and win battery life by underclocking.
[Samsung Galaxy Nexus] gaich:
Waiting for it!!!!
[Samsung Galaxy Nexus] IAmAN00bie:
Lol your link actually just proves my point https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdEY4T3dXWVFDWk9lREdJNGFfU2NwRlE#gid=0

Look how consistently as the voltages decreases, the battery drain in mW goes down. Yes, there are 2 "Weird results" that went unexplained. Does that prove that undervolting was the cause of it? No - because the majority of the rest of the results show the trend that undervolting = less drain.

edit: http://xdaforums.com/showpost.php?p=22126806&postcount=2

Taken from your link... he even uses the same formula... so yes UV won't save much battery, but it definitely doesn't drain MORE. And don't tell me that his testing is not valid because it doesn't conform with what you expected.
[Samsung Galaxy Nexus] MontyQ:
ty colours on this kernel are better scrren not as bright on max tho is this becuase the cm10 overkills it, or this to save battery ?
[Samsung Galaxy Nexus] shooter365:
I'm on stock 4.1.2 :) factory Image ^_^ Could I back up my kernel with franco kernel App?

Gesendet von meinem Stock Jelly Bean GN
[Samsung Galaxy Nexus] osm0sis:
Oh man, I'll never forget. I think mom used to sing that to me in a lullabye. :laugh: