yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] aron7awol:
Ok, I guess it doesn't only exist on this kernel. I've been running GlaDoS for a few days and I've noticed much less lockscreen lag anecdotally. Could be my mind playing tricks on me.

---------- Post added at 02:10 PM ---------- Previous post was at 02:00 PM ----------

Francisco: Please add interactive governor back for those of us who prefer it.
[Samsung Galaxy Nexus] chakra:
Do I still follow this thread for future non milestone releases or will this be a milestone only thread?
[Samsung Galaxy Nexus] bradm23:
This worked. I have audio set at 13 in app as recommended, however I had to turn my audio out volume to about 60% for it to not pause.

I personally wish audio hack was removed for milestone and reinstated for a nightly until bugs are worked out.

I can't comment on battery yet cause I flashed 8 times this morn trying to figure the audio, but performance is great
[Samsung Galaxy Nexus] YoungAceAtlanta:
Thanks that work
[Samsung Galaxy Nexus] nuggahund:
How do I download an older version of the kernel?

For some reason the battery performance is very poor for me running milestone 1 :(
[Samsung Galaxy Nexus] deezid:
Wow, finally great GPS! :D

---------- Post added at 08:54 PM ---------- Previous post was at 08:49 PM ----------

Same here (18.4-18.6 were great here - but no working GPS - at least with Modaco 4.0.4...)
[Samsung Galaxy Nexus] heo_con184:
Just bought the updater app from Android Market to support Franco.

Thanks for your hard work. Really appreciate your work.
[Samsung Galaxy Nexus] kimboinatl:
Just updated to Milestone 1. Smooth and creamy. I was in the car and had my phone plugged into the stereo, and the volume was really low, so I set it to 13... boom, sounded great after that. I haven't checked to see if my values are still not sticking through a reboot though.

Also figured I should mention that I wasn't able to download the M1 update through the updater - I kept getting "download failed". I just went to your URL directly with my phone and downloaded it that way.

Francisco, great job, and congrats on hitting the first milestone with this kernel. Great work.
[Samsung Galaxy Nexus] StuMcBill:
Will "Only when plugged in" do the job?

Cheers

Stewart
[Samsung Galaxy Nexus] sluflyer06:
batterystats from sitting overnight last night. Burned through about 17-18% in 7 hours. Just putting this up for information sake since this issue is fairly widespread.

This is with Dec13 Test Kernel.

Uploaded with ImageShack.us
[Samsung Galaxy Nexus] sethyx:
For me it burned 40% in 8 hours (wifi off, 3g w/ sync on, non-OC, original radio img) :(

Dunno if it's because of the kernel or MCR pre-Ir6, but today I'm switching to ARHD & stock kernel.
[Samsung Galaxy Nexus] sluflyer06:
My top wakelock is always shifting, so far on different days they've been

alarm_rtc

mipi_link

suspend_backoff
[Samsung Galaxy Nexus] Shetlander:
I have to disagree with you. On my phone it goes into deep sleep over night with both Wifi and radio on when looking at cpu spy and the battery graph.

---------- Post added at 03:35 PM ---------- Previous post was at 03:33 PM ----------

I lost 20% juice overnight. I was testing out airplane mode. Wifi and Radio where off but it still lost a 5th of power.
[Samsung Galaxy Nexus] sethyx:
Same here. Full night in deep sleep, but burning battery like hell.
[Samsung Galaxy Nexus] akalias1981:
This is becoming more and more widespread on both stock and custom ROMs/kernels. Does anyone know if Google have yet responded in any kind of way? This is clearly a software bug in ICS is it not?
[Samsung Galaxy Nexus] GchildT:
I believe so.
[Samsung Galaxy Nexus] ock:
I had been testing a couple of kernels for the past few days, and only stock (and AOKP's) has 0.5%/hr standby drain. MCR also having similar issues.

Apart from BetterBatteryStats and CPUSpy, any good app to help diagnose what could be the cause?
[Samsung Galaxy Nexus] sluflyer06:
It certainly seems to be. I have a nandroid of a totally stock setup i'm going to restore to right before i go to sleep tonight and see how it goes(and then wake up and restore back to this kernel of course! ;) ). Then tomorrow night I might do a image with stock kernel but all my other tweaks/patches and see how that goes.
[Samsung Galaxy Nexus] eiabea:
The Galaxy Nexus is my first SAMOLED phone, so i am just wondering if it is normal that the screen consume more than 50% of the battery

With my Nexus S radio eats the most battery...
[Samsung Galaxy Nexus] franciscofranco:
No, the screen uses a **** load more than the ****ing radio.

@everyone

Something must be wrong with kernel 3.0 in general too many reports of higher battery drain than what should happen.
[Samsung Galaxy Nexus] :
Phone battery was good this morning while on the way to work and using it. Used like 10% in the hour travelling and heavy use. Then used like 50% battery while at work for 8 hours and not even taking it out my pocket. Gone back to stock kernel for a while until its sorted. Which I've no doubt Franco will do, especially since he's going to have the phone soon, should speed up the process.
[Samsung Galaxy Nexus] franciscofranco:
The strange thing is that this is a common thing between all the custom kernels, I actually fixed two or three wakelocks with my own code implementations and all my kernels are known for awesome battery life... we'll see whats happening tomorrow when I flash this baby.
[Samsung Galaxy Nexus] Melhouse:
Yes it does. I tried the latest fresco kernel now, and even in Airplane mode Android OS consumes alot of wake time and cpu time.

This was stock ROM.

It would be nice if others tested this as well.
[Samsung Galaxy Nexus] StuMcBill:
Sounds great, look forward to it!
[Samsung Galaxy Nexus] GchildT:
For the passed 8 hours, light use;

1% @ 920Mhz

1% @ 700Mhz

13% @ 350MHz

83% @ Deep Sleep

AndRevHD1.3.2 w/ lastest OC Test Kernel.
[Samsung Galaxy Nexus] gambiting:
Franco, when are you getting your Nexus? Do you need more money for it? I already donated,but man, you deserve the device you make so much better ;-)
[Samsung Galaxy Nexus] inffy:
I think he is getting it tomorrow =)
[Samsung Galaxy Nexus] franciscofranco:
Tomorrow from 9h to 13h thats the scheduled time!!
[Samsung Galaxy Nexus] heo_con184:
Sound Control doesn't work for me while Volume+ works like a charm. But it's a minor thing.
[Samsung Galaxy Nexus] THE_KINGDOM:
This problem 10000% exists. I know that if u turn the volume below about 75% problem goes away. It occurs when volume is high enough and the audio cuts out from auxiliary and resumes again. This problem needs to be addressed.
[Samsung Galaxy Nexus] THE_KINGDOM:
This is the biggest bug on this kernel so far I cannot believe more people haven't identified this yet.
[Samsung Galaxy Nexus] inffy:
I can also report that the app doesn't set cpu settings at boot :(
[Samsung Galaxy Nexus] Stretlow:
Yeah same problem here.
[Samsung Galaxy Nexus] Notn4:
franco, in the m1 changelog you mention USB fast charge...

you are referring to this aren't you ? http://xdaforums.com/showthread.php?t=1524020

well anyway, I tried IncrediControl to enable it as chad instructed but only to find that IC gives an error directly that tells me that the kernel doesn't support fast charge??

EDIT: anyone with this problem? well anyway, I found the solution :) you MUST use the beta 1.5 IncrediControl for it to work (the one on market is 1.4)... quite stupid of me not to read chads post enough carefully, but I bet someone else will make the same mistake :)
[Samsung Galaxy Nexus] landale:
Same here, which is really disappointing because this Kernel is amazing otherwise. However audio cut outs when using headphones is a pretty major problem. It shouldn't be a tough fix. Just let us disable the sound hack and we are all good again.
[Samsung Galaxy Nexus] wsrider:
+1 same thing here still wont stick after reboot.
[Samsung Galaxy Nexus] dwang:
i'm wondering if its related to superuser?

With setcpu, i notice that on reboot, you can see the su permission printed out on the display, whereas I don't see anything for franco app on rboot.
[Samsung Galaxy Nexus] franciscofranco:
Thanks for all the reports. They will be adressed.
[Samsung Galaxy Nexus] THE_KINGDOM:
I agree just disable the sound hack and the problem should be fixed. I believe this problem began since I'm the introduction of the volume hack. Its the biggest issue right now on this kernel, by far.
[Samsung Galaxy Nexus] Spronx_:
Just an end user here, but I've noticed that with any version after 16, my reception and data drops out. Even the lastest m1.

I use AOKP, with the XXKL1 radio. The signal only seems to drop out when screen is off... not when I'm actually using it.

just my 2 cents. I'm still using 16.
[Samsung Galaxy Nexus] fjdifede:
Franco

The volume default on m1 can be fixed I got a bug whit power amp soulden't we be responsable for our own earing healt I love how 19 build performed.

This is the best kernel so far however shoulden't be called M1 having a bug when we modified the volume using your app.

Thanks for the greate work!!!!!
[Samsung Galaxy Nexus] nitrox1:
+1 for interactive to come back, thanks Franco.

Swyped from my tuna surprise with extra back bacon.
[Samsung Galaxy Nexus] wlee2:
I have the same problem with M1 with poweramp and notifications coming in, They sound "blurred" then the volume turns down i have to pause and play music again to get it working.

i tried at default volume of 13 and other values still happens though.

other than the volume hack i really liked M1 but reverted back to 18.4 for now to get 1.5ghz ^_^...

Great kernel..
[Samsung Galaxy Nexus] joelteixeira:
I'm using volume at 9 and either volume and quality seems great to me. If you feel your phone smoother at 1.5 that's ok but please don't get stuck by numbers. My phone is far smoother at 1.35 on M1 than running at 1.65 on previous releases.

All the best
[Samsung Galaxy Nexus] SpOuK-3-:
+1 on this bug... But with DI.fm app...
[Samsung Galaxy Nexus] Elemenopee:
It sounds a lot like you have your power saver enabled.
[Samsung Galaxy Nexus] franciscofranco:
There's no need to repeat over and over again about the volume hack thingy, I know that exists, and even if I can't reproduce the error I'm gonna work on a fix for it, but as you all know I also have a life and I also have the app bugs to fix.

About interactive governor...I don't know about that. I gotta think.
[Samsung Galaxy Nexus] Vangelis13:
www.world-of-nexus.com/download-section
[Samsung Galaxy Nexus] xTee:
is 100% safe to use hotplug mod enabled?
[Samsung Galaxy Nexus] Vangelis13:
100% safe as in what / how..?
[Samsung Galaxy Nexus] LucaZPF:
nobody??

it's important for me to know this
[Samsung Galaxy Nexus] optmkleung:
If using AOKP, try disable volume link under sound setting. I have this problem before, unlink fix it. Using vol:13, and high performance, using volume + for speaker @13 as well.
[Samsung Galaxy Nexus] xTee:
for hardware
[Samsung Galaxy Nexus] M00_cow:
Is there any way to disable the volume hack as I cannot lower the max sound levels to volume that will not permanently damage my headphones.

Using a level of 0 is still too high.
[Samsung Galaxy Nexus] SpOuK-3-:
:) Don't worry, even if my phone reboot every hours... i'll keep your kernel :) Your work is amazing... With all those updates... You still have time? ;p
[Samsung Galaxy Nexus] franciscofranco:
In the future, yes.

Reboots? How much are you undervolting?
[Samsung Galaxy Nexus] Vangelis13:
Well, I'm not sure exactly what you mean with hotplug mode being 100% safe for the phone's hardware but, yeah, I don't think anyone has damaged their phone by using this kernel. Or any other kernel in here for that matter..

For as long as you follow instructions & read the threads you'll be ok.

If you now were to run your phone every day for hours on end on 1,5 GHz and ignore that it gets hot and just continue, would that be safe? No..
[Samsung Galaxy Nexus] M00_cow:
Thankyou.

Battery life and performance have been top notch re: my milestone experience. :)
[Samsung Galaxy Nexus] M00_cow:
Could someone post some safe undervolt settings for myself to use?
[Samsung Galaxy Nexus] franciscofranco:
You don't need to undervolt, smartreflex does that for you ;)
[Samsung Galaxy Nexus] SpOuK-3-:
I'm joking ;) everything is perfect ;)
[Samsung Galaxy Nexus] Serious_Beans:
Wait so I don't need to manually set undervolts? O_o
[Samsung Galaxy Nexus] Frakatchoo:
Yep interactive governor is gone ?!
[Samsung Galaxy Nexus] kimboinatl:
Francisco, not sure if this will help with the issue with settings not sticking, but figured I should mention it because it seems weird to me.

I sort of suspected that the scripts in my /syste/etc/init.d folder were not being executed on startup, so I was poking around in the init.rc file on my phone, and I have this entry for init.d:

# Execute files in /etc/init.d before booting
service userinit /system/xbin/busybox run-parts /system/etc/init.d
oneshot
class late_start
user root
group root

Keep in mind that I'm familiar with Unix/Linux, just not specifically Android, but this didn't look right to me. I backed the file up and tried modifying the service line, then rebooted my phone. No joy, doesn't look like my settings stuck. I went back in and noticed that the backup file I had created was gone, and the init.rc file was back to what it was originally set to above, as if something was overwriting it.

Anyway, figured I would mention this. Hope it helps.
[Samsung Galaxy Nexus] franciscofranco:
You can't change init.rc on runtime, you have to change it directly into the ramdisk. What changes have on made on that piece of code?
[Samsung Galaxy Nexus] kimboinatl:
Gotcha, that would explain why my changes disappeared. Thanks.

I tried modifying the above code to use a sysinit.sh script I grabbed off of the net that is supposed to kick off the scripts in init.d. I didn't see a userinit.sh script anywhere on my phone, which I am assuming would be needed with the code above.
[Samsung Galaxy Nexus] boostedmr2:
What's up guys. How are you guys like cm9 and Franco kernel over stock? Any pros/cons been running Franco exclusively for along time and didn't even think twice when I flashed cm9 to flash Franco. But all over the cm9 thread they say to run they stock kernel just wanted to hear some opinions on this.
[Samsung Galaxy Nexus] franciscofranco:
Of course they want you to run their kernel :p

Just pushed app version 3.3.2 in hope the set on boot ****s have been fixed for good.
[Samsung Galaxy Nexus] boostedmr2:
So leaving my voltages stock. Smart reflex is undervolting them on its own? Any way to check what voltages the phone is running at? Also what effect does under volting have on smart reflex?
[Samsung Galaxy Nexus] M3drvr:
I'm not having the aux out problem or any problem to do with that. Used my aux out for about 12-13 hours over passed two days. But one thing I did notice...when I change my ring volumes to vibrate, it no longer puts a vibrate icon in status bar, just the crossed out horn now. The phone still vibrates like normal though. Anyone else get this? I haven't changed roms in I'd say about 3 weeks now and running same build. This just happened when I flashed the m1 kernel. I tried reflashing the rom and kernel but still happens. Wiped out all data for the heck of it and clean installed, still same.
[Samsung Galaxy Nexus] franciscofranco:
If you do find . | grep calib you'll find the calibrated values.

When we undervolt manually we are just limiting the nominal voltage, which means we're just lowering the limit that smartreflex can calibrate into. People saying undervolting saves battery are mostly wrong, it's placebo 99% of the time ;)
[Samsung Galaxy Nexus] sam2c:
I keep noticing people overclocking their phones ....are there any real world benefits to that? Is the phone running slow for you guys when using a particular software? Hows battery life when overclocked?

Just curious
[Samsung Galaxy Nexus] ChongoDroid:
Mostly for increased e penis sizes, but yeah it's light speed overclocked.
[Samsung Galaxy Nexus] wormbaby11:
Do people uses Setcpu with this or just uses the franco apps for the cpu setting?
[Samsung Galaxy Nexus] r3ferrei:
Fixed here with new version. Over clock and Gama settings loaded on boot. Thanks.
[Samsung Galaxy Nexus] snidrx:
Hi, i purchased the app at the market, then flashed it on my gnex thru the app running on aokp build 27 but i noticed when the phone boots up it opens up poweramp automatically and when i am using my headset, i can hear hissing/static sound when you open apps, swipe etc. is this normal? thank you!
[Samsung Galaxy Nexus] izzledizzle:
Maybe I'm just an idiot, but I have the Franco Updater app (which is very convenient, definitely worth supporting the dev for that app,) and the scaling governors that I show are conservative, On demand, and performance. It did have interactive before but I just updated the app and noticed it is gone. What happened to francoturtle and gazelle? I don't think I've seen them since I downloaded the app a few weeks ago but I always saw them under SetCPU. Are those still there but just named under one of the other 3? Thanks and keep up the good work!
[Samsung Galaxy Nexus] heo_con184:
Franco decided to keep only 3 governors instead of 5 like before. Ondemand is the default governor. I don't really know the difference among them.
[Samsung Galaxy Nexus] MacDaddyTMT:
Personally, I would like to see the return of Turtle and Gazelle, if for no other reason than the sheer awesomeness of the names. But that's just me. =p
[Samsung Galaxy Nexus] Schiehallion:
Set on boot now working perfect after updating Franco app.
[Samsung Galaxy Nexus] joelteixeira:
I second this. Thank you for all your dedication Francisco.
[Samsung Galaxy Nexus] franciscofranco:
They are just taking a well deserved vacation before they come back for kicks ;)
[Samsung Galaxy Nexus] rene_r:
Hi, how can I Check if my scripts in init.d were executed on boot?

Thx in advance

Rene_r
[Samsung Galaxy Nexus] SrTapir:
I´m totally ignorant here, but with UV I understand that you are limiting the higher limits of Voltage the system can use, I'm wrong?

So if it is true, if you UV with a 20% less voltage each frequency, you are saving this voltage every time the system needs max speed and voltage, saving battery though.. Then you´re not limiting the lower value smartflex con go, otherwise you're limiting the higher. :confused:

In battery terms I can´t asure anything because is difficult to have real values, but with UV I really notice a descent in device temperatures for example when I play games..

Sorry for sticking with this, and thanks for the Milestone, is amazing.
[Samsung Galaxy Nexus] franciscofranco:
I said "lowering the limit smartreflex can calibrate into", same thing as you did, with other words!

But you said it all :)
[Samsung Galaxy Nexus] Exostenza:
I have absolutely no lag on my lockscreen with franco.kernel.
[Samsung Galaxy Nexus] 02busa:
Milestone Kernel has been rock solid for me so far. Blazing fast, and loving the fast charging implementation.. Many thanks to Franco, Chad, and anyone else involved.
[Samsung Galaxy Nexus] rene_r:
Is there a way to increase the vibrate intensity, because I have a CaseMate case and the vibrate intensity is quite bad, so I sometimes miss calls, when my phone lies on my desk(only vibrating..)

br

rene_r
[Samsung Galaxy Nexus] nitrox1:
So your saying the CPU has a form of AVS, or HAVS, or DSV, and all we are doing is changing the lower part of the range.

So when I have 350mhz, at 850mV. All I've done is change it's voltage range from hypothetically. 925mV-975mV to 850mV-975mV, if that's correct I can't help but think I'm allowing my CPU allot of choice and thinking space.

Is there an equivalent,

Su

Checkv

Command I can use

Swyped from my tuna surprise with extra back bacon.
[Samsung Galaxy Nexus] touchee:
Any chance we can have a working option to load cifs as a module? I need cifs support but want to keep using your kernel.
[Samsung Galaxy Nexus] sam2c:
LMFAO! Gotcha
[Samsung Galaxy Nexus] rene_r:
The answer is:

Smart Vibrator, an absolutely great tool!!
[Samsung Galaxy Nexus] khenderick:
@franciscofranco, seems there is a small glitch in your android app; when "scrolling" trough the different pages (swiping left and right), the menu item in the top isn't updating with the name of the active page.
[Samsung Galaxy Nexus] joelteixeira:
If you are talking about Information / OC / Settings... It's updating here.

Update: Weird, just took 3 screenshots and one got a different size/dimension. :confused:
[Samsung Galaxy Nexus] khenderick:
Seems it's related to the 240dpi. In this screenshot, its the "INFORMATION" that won't update.
[Samsung Galaxy Nexus] rene_r:
How do I enable/disable fast usb charging?

thx in advance

rene_r
[Samsung Galaxy Nexus] joelteixeira:
It's on settings tab (on franco.kernel Updater app).
[Samsung Galaxy Nexus] khenderick:
In the app > settings > enable fast usb charge
[Samsung Galaxy Nexus] rene_r:
OK, and is there also a way to activate it if I don't have the kernel updater?

thx !

rene_r
[Samsung Galaxy Nexus] joelteixeira:
:D, I didn't know we could also swipe (left/right) when using drop-down menu, I tried dpi 240 for some days before and been always "clicking" on the menu to change screens. lol stupid I am.
[Samsung Galaxy Nexus] geebees90:
Hi everyone, I have come from Nexus S, and I am wondering how would I be able to change color settings with this kernel if it allows, and how would I change sound settings as it says in the title "Color and sound control". With Nexus S, I had the NStools and Voodoo to play with color and sound. How's that possible with Galaxy Nexus.

I will be grateful.......
[Samsung Galaxy Nexus] joelteixeira:
Most of settings can be changed via commands from terminal but franco.kernel updater is an application that consolidates everything and is strongly recommended.

Tapatalked from my Nexus Prime
[Samsung Galaxy Nexus] ArmanUV:
read the op.

easiest way is franco's app which is paid but gives you a warm fuzzy feeling that you are supporting franco.

otherwise, you need to get your hands dirty and write a couple of init.d scripts. search this thread for "echo".
[Samsung Galaxy Nexus] Nighthound:
I believe you can use

echo 1 > /sys/kernel/fast_charge/force_fast_charge
[Samsung Galaxy Nexus] Mrc527:
So...you are telling me that i have to download that app to enable fastcharge?

Wasn't enabled by default in franco's kernel? :D
[Samsung Galaxy Nexus] inffy:
You can do it also from the command line. It's not enabled by default.

So either buy the app, or use command line magic.
[Samsung Galaxy Nexus] rene_r:
Thx!!
[Samsung Galaxy Nexus] Foxhounnd:
Hey guys, running the latest Kernel, along with AOKP MS3 and am having the worlds worst battery life, it's absolutely abysmal. Funny thing is, I notice no difference between OC's and UV's and my stock battery and 2100mah battery. For the life of me I can't figure out the problem, what's the best method for solving this?

Cheer's

Adam
[Samsung Galaxy Nexus] MacDaddyTMT:
Is there any way to get the color multipliers to apply on boot? I know the app doesn't do it, but can I do it via a script or something? I've never written a script of this sort before, so any hand-holding would be appreciated.
[Samsung Galaxy Nexus] inffy:
check that your phone goes to deepsleep, you can use free cpy spy for that. If the phone never enters deep sleep state, then get betterbatterystats and check for wakelocks that prevent the phone going to deep sleep.
[Samsung Galaxy Nexus] rene_r:
Have a look at this, it's quite easy:

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

br

rene_r
[Samsung Galaxy Nexus] Darwichee:
Hi guys,

I've used the M1 now about 11h, and the standby time of this kernel is the best, but when using apps like games it's not that great, i can't really tell now, but it feels like FuguMod can handle more, meaning when you're using apps.

I can't really confirm this since im not a advanced user, but what do you guys say? Have you used FuguMod, to compare with this Kernel?

thanks