yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Dr Byte:
... but the rest of the time, it'll chew up resources trying to compute your location using other means (like cell towers, wifi router MAC addresses etc) if you let it. "It's not a bug, it's a feature!"

There is one simple way to test your hardware. It will take a day of 'sacrifice.'

Take a nandroid backup, or equivalent. Back that up on your PC.

Wipe everything

Install your current ROM (optional) and M3 of franco's kernel (not)

Boot and go through the setup wizard

NOTHING ELSE. Just use it for the day as a phone.

Then, if it seems happy, install the apps one at a time. I said simple, not convenient!

If that still gives you "poor" results, go back to a stock image and try that for a day.

If THAT still gives you poor results, I see a warranty claim in your future.

Just one final thought: check that you have the appropriate radio/baseband for your carrier.
[Samsung Galaxy Nexus] DaTraS:
Hey,

flashed your kernel and i love it so far.

My phone can handle the 1,4ghz it seems, but the volume bug instantly hit me.. :(

(I have a device from Germany, where the newest version was already installed and had no volume-bug so far..)

Any chance that the fix will be included soon?

Thanks mate!
[Samsung Galaxy Nexus] Andrmgic:
The fix for the volume bug is kernel based.. and i don't think google has posted the fixed source code yet.. so this kernel doesn't currently include the volume fix. To my knowledge, only the stock kernel contains it.
[Samsung Galaxy Nexus] franciscofranco:
Yes, without kernel sources I can't do ****.

Btw thanks to those who left nice comments over RootzWiki forum, I guess some other "dev" won it this week...I wonder what the criteria was. I bet that without the phone I'll do a better job than his. I wonder where I'm gonna get 500 euros to buy one GN...
[Samsung Galaxy Nexus] flakz0r:
There's a thread on General section with the changes submitted to fix the volume bug - the code to add 2 ms debounce time to the buttons - isnt that what you need?

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

How did Paul O'Brien release his modded kernel with the fix included?

(sorry, i dont know **** about kernels :))
[Samsung Galaxy Nexus] Chirality:
The kernel source that includes the volume fix is now up in the AOSP repo.
[Samsung Galaxy Nexus] franciscofranco:
Thanks both of you. Going to patch it right now.
[Samsung Galaxy Nexus] franciscofranco:
Update is up gogo.
[Samsung Galaxy Nexus] The Gingerbread Man:
Jesus you work fast man! Just to clarify booting CPU is now set to 1.2ghz as boot animation was very laggy on 3122011
[Samsung Galaxy Nexus] franciscofranco:
Working fast because my tester with the device is online I gotta abuse him ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
Hahahahha he's a great guy for putting up with the abuse :D

Not that I know who he is :rolleyes: you got the perfect candidate trust me
[Samsung Galaxy Nexus] franciscofranco:
It's mister mskip :)
[Samsung Galaxy Nexus] flakz0r:
I'll have my phone on monday, if you need anything. I can even let you look at it in person, since we live on the same city. Sorry, no touching. :D
[Samsung Galaxy Nexus] The Gingerbread Man:
OK just had a little test myself and obviously boots OK but the app drawer and home screens seem to take a little time to populate also powering down seems to take longer for some reason. On a whole this isn't as snapy as 2.12.11 on default cpu settings. This one isn't laggy but just doesn't seem quite as quick as 2.12.11 so going back for now as I don't get volume bug but will be here for next round of testing.

Btw tested on mikes rom with kkxx6 baseband left CPU settings as how you made as default
[Samsung Galaxy Nexus] darrendm:
Dec4 kernal looks great.

Hopefully getting my phone this Monday/Tuesday.

Would the first correct steps be; unlock bootloader, install CWM, root using superuser, install this kernal?
[Samsung Galaxy Nexus] The Gingerbread Man:
I know that why I said hes perfect as he is senior mod, recognized dev and IT consultant and has great patience to deal with noobs like me helping me for a whole night lol
[Samsung Galaxy Nexus] franciscofranco:
"All your Galaxy Nexus belong to me" ;)

Thanks for the feedback. I smell issues with the enabling of a higher frequency than stock 1,2ghz. Not much I can do without the phone :(
[Samsung Galaxy Nexus] The Gingerbread Man:
Unlock your boot loader straight away if you intend to as it wipes phone so no point in setting up to do it later again then yes root then cwm and your set for testing stuff :D
[Samsung Galaxy Nexus] Andrmgic:
As long as those issues don't smell like burning silicon, I think we'll be ok :)

So far so good on DEC 4.. will post back if it gets too toasty..
[Samsung Galaxy Nexus] The Gingerbread Man:
Sure no worries. I really admire you and mike for making stuff for phones neither of you actually own. Your both doing a grand job and can only image how fast the ball will get rolling when you both actually get nexus'
[Samsung Galaxy Nexus] JCUK89:
Hey, Ive just flashed it as well, but my GN boots with 350. any clues how to resolve this issue?
[Samsung Galaxy Nexus] Vangelis13:
Clicking refresh in a frenetic matter will answer both those questions..! :-)
[Samsung Galaxy Nexus] Redflea:
Ahhhhh, I'm familiar with that behavior.

So the answer would be not yet...
[Samsung Galaxy Nexus] sefirosu0522:
You gotta be kidding me! This worked. New phone. Don't know it that well yet. Thanks!
[Samsung Galaxy Nexus] Dr_Ownage:
Just flashed, hopefully we can see some nice battery drain from this one :)

Has UV been fixed?
[Samsung Galaxy Nexus] Andrmgic:
preliminary battery drain results look good.. 1 hr 8 minutes and still @ 100% :)
[Samsung Galaxy Nexus] grinch247:
are you not using the phone? what voltages are you running? I'm right @ 2 hrs w/ phone and have used it to make some calls etc...I'm @ 84%
[Samsung Galaxy Nexus] GchildT:
I'm sure he's talking about device @ idle...
[Samsung Galaxy Nexus] Andrmgic:
precisely.

My primary issue with Franco's previous kernels was idle battery drain. I don't care if the device drains while I'm actually using it..
[Samsung Galaxy Nexus] franciscofranco:
In one hour Ill release nightly 7.1, just gonna watch a movie with my gf.
[Samsung Galaxy Nexus] jhericurls:
Anyone experiencing an issue with very slow charging?
[Samsung Galaxy Nexus] lynxboy:
Geek translation:

one hour Ill release nightly 7.1, just gonna watch a movie on my beautiful galaxy nexus.

Seriously though, looking forward to the release. Looks like the battery issues have been solved.

Regards.
[Samsung Galaxy Nexus] Spronx_:
Just throwing in my 2 cents.

Since flashing, idle battery drain seems to have gone.

UV interface works - I tested this by dropping 1200 mhz to 900mv and it hung/reset.

I'm still noob with CIFS. Don't use it, haven't tested it.

Phone connects to computer just fine :)

voltages are:

1150

1025

925

775

Fantastic kernel! GSM extended battery is in the mail, my phone will never die once I have it! :D
[Samsung Galaxy Nexus] DarthPiggie:
Omg that tidbit about the camera being open in the OP really made me LMAO! For some reason your wording was just hilarious to me. :p
[Samsung Galaxy Nexus] Vangelis13:
An official battery..?
[Samsung Galaxy Nexus] lynxboy:
Yes you can order them online from Korea via eBay and others. Check the accessories forum.

Mine is on the way par avion.

Regards.
[Samsung Galaxy Nexus] franciscofranco:
Nightly 7.1 out.
[Samsung Galaxy Nexus] lynxboy:
Flashed.

Will report back. :)

Regards.
[Samsung Galaxy Nexus] nory82688:
http://item.mobileweb.ebay.com/viewitem?itemId=110797756938&index=5&nav=SEARCH&nid=54093346895

Is this the one you are talking about?
[Samsung Galaxy Nexus] Enhanced:
Yes.
[Samsung Galaxy Nexus] lynxboy:
That's where I ordered from. They are based in Korea and very helpful over email. There is another website which may be cheaper, but check the threads in accessories forum for more info. Someone has posted pics and stats regarding the battery.

After being back on stock for the past few days it's great to see the improved colour range with this kernel (whites especially) and feel the speed again!

Regards.
[Samsung Galaxy Nexus] jkoljo:
Could anybody test OTG on #160? :)
[Samsung Galaxy Nexus] metalspring:
Here's my screenshot of 4 hours normal usage, custom auto brightness settings, 192-1344 interactive, poor 3g reception, 25 minutes playing music with screen off (wakelock)

kernel settings- hotplug dual core mode, high quality sound, logging off, suggested colors/gamma settings, smartreflex enabled, GPS on, mostly web browsing, liquid 1.35 NateModz red/black theme, full sync, Verizon nexus, extended battery...if anyone wants I can post my custom auto brightness settings
[Samsung Galaxy Nexus] xyzulu:
I can't seem to mount the USB using my OTG cable on #160

Previously I had been using stickmount, so perhaps I missed something.

USB lights up, but no mount made, or requested. Where does it usually mount?

Edit: Installed Stickmount, can mount usb just fine then.
[Samsung Galaxy Nexus] jkoljo:
Which ROM are you using?
[Samsung Galaxy Nexus] xyzulu:
Stock 4.0.4
[Samsung Galaxy Nexus] jkoljo:
Oh, cool. So the problem must be in AOKP builds b35 and b36 :)

Thanks for your help!
[Samsung Galaxy Nexus] drawde40599:
Cute!! ; )
[Samsung Galaxy Nexus] nory82688:
Hey Franco, just wanted to say that this has to be my favorite kernel that you've made so far (999) r160. This kernel has given me the best battery life out of every single one of your kernels so far, and its still amazingly fast and fluid. Your app has come a long way also,letting me tweak you kernel the way I want is awesome. So, I wanted to say thanks, and keep up the great work!
[Samsung Galaxy Nexus] AdamZA:
Just like to amazingly point out that I had 0% (ZERO!) battery drain overnight.

How is that even possible!? WiFi, data,sync off but phone radio still on.
[Samsung Galaxy Nexus] metalspring:
I just had a quick question about the governor settings for interactive governor...is it better to set the high speed setting to 1344000 or 1228000 for better battery life?

This is what my current CPU speed slot times look like with average usage (not many very CPU intensive apps)

Btw I changed the min sample time to 20000 instead of the stock 80000 if it makes a difference
[Samsung Galaxy Nexus] AdamZA:
The way I usually do it is to stick to 1228000 unless I know I'm going to be doing something which requires the extra power. With stock Android being such a light OS, it's not necessary in my opinion to overclock until needed. 1228000 is naturally better for battery since its a lower frequency.
[Samsung Galaxy Nexus] metalspring:
I'm talking about the governor settings in the Franco app under governor control by the way, I like the little extra power of 1344 frequency to be readily available if needed, I'm just curious if changing the hispeed_freq to 1228000 instead of 1344000 will help keep it at 1228 unless the extra speed really is required or if making the CPU wait to jump to 1344 will actually hurt battery life...I'm thinking about changing the go_hispeed_load to 90 if it would help as well
[Samsung Galaxy Nexus] jhericurls:
I got 5% drain over 7 hours which is very good. Everything on and wi-fi off, I used these conditions as its reflects my day to day usage the most.

So taking in to consideration of possible poor reception, I would be over moon if I average 1% drain per 1 hour.

I've Hotplug on, so will look at drain tonight with it off.
[Samsung Galaxy Nexus] klauhr:
Hey Franco,

i noticed that in my configurations Colorsettings don't stick after boot. Now i have been testing something. In think it is a problem with SuperSU. Because when i'm using Android Revolution HD it ships out with SuperSU when i'm chaning the colors and reboot won't stick. But when uninstall SuperSU and install superuser(with su binarys from superuser) it works perfect. Stock rom with SuperSU don't work for me too. Not testet stock with superusers, sorry.

Just an Idea if you get more Bugreports with not sticking color after reboot.

I'm using superuser now and be happy.

Thank you for great Kernel :)
[Samsung Galaxy Nexus] AdamZA:
Oh, I understand - sorry about that!

Let me know how you get on with it as I was thinking of using governor control but not sure how to get the best out of it. Plus my current governor choice is Lazy which isn't compatible with governor control.
[Samsung Galaxy Nexus] zenzip:
can you post your setting? min/max freq. kind of governor, brightness etc...

I've a bad batterylife on AOKP milestone 5 and franco r160

ondemand 384-1228

brightness 60-75%, hotplug off, logger off, sound perfomance on, gamma and multipliers color on recommended values, wifi off, sync on, middle usage... only 18-20h with 1.20/1.50 screen on time....too low batterylife!!!

no bad wakelocks in BetterBatteryStat

pls help me :D

Thanks
[Samsung Galaxy Nexus] relax24:
Trying r160.

Last night over 7hrs sleep, I lost 2% battery.

Wifi on, sync off, 2g (gsm only). Device was asleep 97% of the time. Wakes due to whastapp scheduled 4am backup and the notorious facebook katana wake which I can never seem to get rid of, and also wlan_rx_wake (which I also can't get rid of). I'd have probably lost less than 2% if I had just turned off wifi.

interactive 192/1036 mhz. SR on. Hotplug OFF.

only Cpu undervolts -

192mhz - 750mV

384mhz - 850mV

729mhz - 950mV

1036mhz - 1100mV

Using it now as normal during work. Will see how it goes.
[Samsung Galaxy Nexus] schizophrenia:
i can never get that much unless on Wifi
[Samsung Galaxy Nexus] zenzip:
so my batterylife is normal?

from what I read, compared to other users my batterylife is too low...
[Samsung Galaxy Nexus] schizophrenia:
there are some users having really amazing battery life

but i am one of those who are so cursed.

if on 3G data, i only get around 6-8 hours with 2-230 hours screen on time.

yours are definitely better than mine anyway haa..
[Samsung Galaxy Nexus] SirOcelot:
No questions, just try:

Interactive 192-1228

brightness 30%, hotplug off, logger off (checked),

sound perfomance off, gamma and multipliers color on recommended values (Doesn't matter, it's for aesthetics), wifi on, sync on.
[Samsung Galaxy Nexus] zenzip:
hahaha so I'm lucky man!

I'll try it, with this setting wich are your batterylife?
[Samsung Galaxy Nexus] kmso:
i sure it is normal!
[Samsung Galaxy Nexus] Sveke:
Those getting crappy battery life, what's the signal strength in your area?

When I have a garbage signal 4g or 3g, it literally cuts my battery in half.

Good test is go home, charge up full, put on wifi, and use your phone sitting on your couch all night and see what happens.
[Samsung Galaxy Nexus] relax24:
Does anyone undervolt their IVA & Core figures? If so, what do you use that is deemed stable for YOUR phone?
[Samsung Galaxy Nexus] metalspring:
I've been testing my settings and so far it seems fairly good, I'm getting a nice balance of times at 1344 and 1228 speed slots, and it's more weighted towards 1228, which is just perfect

For anyone that wants to try it, choose inactive governor

Governor control settings-

above hispeed delay- stock 20000

Boost- stock 0

Go hispeed load- 90

Hispeed freq- 1228800

input boost- stock 0

Min sample time- 20000

Timer rate- stock 20000
[Samsung Galaxy Nexus] metalspring:
Smartreflex does a pretty good job by itself, I tried undervolting them before but I couldn't find a way to really test iva voltage to be sure it was stable and my core undervolt was only like 25 below the smartreflex value
[Samsung Galaxy Nexus] hotnikkelz:
Noob question

What is the point of taking generic hotplug off?

Shouldn't keeping it on give more battery? I noticed a lot of people take it off and I have no idea why.

Also how the hell to read this batterystats app? Someone needs to explain this in stupid for me
[Samsung Galaxy Nexus] franciscofranco:
A little search would be enough. If one turns the screen on/off a lot onlining/offlining cpu1 ****s the battery life like theres hell on earth because hotplug is an hard operation for the system.
[Samsung Galaxy Nexus] Langduscher:
With a lot of syncing going on, and generic hotplug disabled, the phone completes tasks faster so is in deep sleep more/ quicker. Turn it on when you go to sleep/ don't sync (data + wifi off) and turn it on. Then it will drain the least battery.

edit; Francisco beat me to it :p

BBS is not kernel related so I suggest you ask in the appropriate forum for more explanation or use the help section in the app, it explains it pretty clearly how to use BBS.
[Samsung Galaxy Nexus] relax24:
Well not true exactly. BBS has a kernel wakelock section, so if he's seeing a lot of stuff in there then he's right to post it in here...just not the partial wakelock stuff
[Samsung Galaxy Nexus] Langduscher:
I totally agree mate :)

But discussing how the BBS app works is off topic ;)
[Samsung Galaxy Nexus] hotnikkelz:
Well that sounds ****ty.....sounds like there's no point to ever enable it lol.

Anyway my time so far on 160 has been good to be honest. Which is strange as 199 wasn't. I feel as if my phone is crazy or am I crazy...i'll have to do start doing theses test more scientifically. I'll recheck the overnight drain. I'm sure it isn't as good as how others are reporting though, but will confirm.
[Samsung Galaxy Nexus] joeyfong:
what is the changlog for updater 4.7.1??
[Samsung Galaxy Nexus] franciscofranco:
Now theres a question that I really dont want to answer or I will shoot someone because it cant be more obvious regarding the place you can read the changelog from.
[Samsung Galaxy Nexus] kompressorgpl:
Franco Hello!!! I send you a PM... I got your apk! Great stuff! I've been read this thread for a beat of time... I now some one gone shoot me but, and theres is no other way to say it... It's difficult!!! We have the kernel; we have the ROM; and we have the phone to tweak!!!! How about, some of the HEADS here, trie to make a manual? For better performance; for better battery life... Just trie to help...
[Samsung Galaxy Nexus] nodstuff:
That's a good idea but unfortunately the way everyone uses their phone is different!

What works for me might not work for you!

And there really isn't all that much to it, to save battery turn off sync, data, turn down brightness of the screen etc. etc.

For performance gain, up the clock speed, governor change etc.

It would be a short manual.
[Samsung Galaxy Nexus] kompressorgpl:
Thank´s!!!
[Samsung Galaxy Nexus] joeyfong:
sorry, I purchased at androidpit, I only see the changlog at google play
[Samsung Galaxy Nexus] hawkye:
Then follow him on G+. He posts the changelog there also.
[Samsung Galaxy Nexus] jaxenroth:
Need some help. Running 160 and I've noticed I'm getting a lot of screen tearing/digitized pixles. No matter what gov or clock settings I use, I still get them. Any ideas? Thx.

Sent from my phone...
[Samsung Galaxy Nexus] republitarian:
Might be artifacts. Are u running 384 or 512?
[Samsung Galaxy Nexus] jaxenroth:
Here's my CPU settings and here's what I'm talking about

Sent from my phone...
[Samsung Galaxy Nexus] qballe:
with 384mhz gpu version or 512 ?

test this release of 160 :

http://minooch.com/franciscofranco/Galaxy Nexus/nightlies/gpu_384mhz/

maybe your gnex can't handle 512 mhz gpu, franco always makes 2 release of every kernel for this probem.

;)
[Samsung Galaxy Nexus] jaxenroth:
That seemed to fix it. Looking good now. Thx bro. Guess my CPU can't hang. Lol.

Sent from my phone...
[Samsung Galaxy Nexus] barmyman:
how can i turn off hot plug? the commands in the first post are not working
[Samsung Galaxy Nexus] qballe:
Buyng the app ? :confused:
[Samsung Galaxy Nexus] barmyman:
I think that the path to the file is just incorrect
[Samsung Galaxy Nexus] qballe:
Yep but the 2$ are to support this project not for the app in itself imho ;)
[Samsung Galaxy Nexus] slayp00n:
A few updates ago my settings stopped going on boot for colour.

The offsets and multipliers both are not remembered on boot through the app with the latest nightly.
[Samsung Galaxy Nexus] cancerouspete:
Just to throw a wrench in the mix, while I experience screen tearing the most at 512, on more than one occasion I've seen it at 384. Only coincident I've noticed is it tends to happen the split second before the omap gamma setting kicks on...
[Samsung Galaxy Nexus] DontJoinTheDarkSide:
am i the only one who can't seem to run franco kernel anymore. after 143 my phone just constantly crashes after installing this kernel.

Doesn't matter what build i'm on. liquid/aokp

Other kernels work fine. And what's even more odd.

Trying to use 143 also doesn't work anymore.

And yes i wiped cache + dalvik cache. formatted system and all that snazz.

Also relocked bootloader/flashed stock and still no luck.

Becoming quite annoying since i bought the app specifically to use the kernel.

-____-

EDIT:

Flashing R130 512 and that's running fine with AOKP build 36. What the hell...that's it starting off fresh without restoring backup apps.

However I only restore the apps, never the data.
[Samsung Galaxy Nexus] klauhr:
Could u answer me if you are using superSU or superuser?
[Samsung Galaxy Nexus] cancerouspete:
Franco was aware and announced that it had been broken. Ensure you are indeed running the latest version of the app, not kernel.

--gnex toro bb 4/9 4.0.4--
[Samsung Galaxy Nexus] cancerouspete:
If I'm not mistaken, 143 is pre 4.0.4 and all the roms seem to be using 4.0.4. Tried the latest nightly? Also, after formatting etc, did you use titanium to restore the Franco app+data? Perhaps old settings are being restored and conflicting

--gnex toro bb 4/9 4.0.4--
[Samsung Galaxy Nexus] macellaio:
Yes, it is. The correct path is /sys/module/omap2plus_cpufreq/parameters/generic_hotplug. echo 0 > that file or change it directly using your root enabled file manager of choice.

Francisco, also in the OP, not that it matters much, but just for the sake of clarity it states CFQ is the default I/O scheduler. You've been using SIO for quite some time now.
[Samsung Galaxy Nexus] franciscofranco:
Its not broken anymore.
[Samsung Galaxy Nexus] Stretlow:
Mine doesn't either,i presume it's a conflict with cm9... Not francos fault
[Samsung Galaxy Nexus] yyz71:
Hey franco why is 192 not being used?

Sent from M5
[Samsung Galaxy Nexus] Benji1983:
hey franco

maybe im the first one with an issue about this kernel

if i start a navigation with navigon europe i got random reboots

greetz benji
[Samsung Galaxy Nexus] nodstuff:
Is your min CPU speed set to 192mhz?

If not then its not gonna be used!

Your min is most likely set at 384mhz.

No mystery here!
[Samsung Galaxy Nexus] cancerouspete:
I know, hence past tense :) just trying to assist the people who insist on not reading any posts before the their own. Funny no sooner did you say its fixed (for the 4th time) someone again posts same thing lol

--gnex toro bb 4/9 4.0.4--
[Samsung Galaxy Nexus] isinisterx:
It would be ****ing awesome if the kernal could detect when music is played and switch to music mode
[Samsung Galaxy Nexus] yyz71:
so I rebooted and still 192 is not sticking!!!!

http://img.tapatalk

.com/63f214de-2169-545c.jpg

Sent from M5
[Samsung Galaxy Nexus] endymion2k5:
Had the same issue until a few minutes ago. Im using CM9 aswell (15 may compile) in combination with superuser.

- Update franco kernel updater to the latest version

- Open superuser and check the binary for updates, if none found (which was the case for me), update it anyway.

For me it now sticks on reboots.

On a side note: The governor setting did not stick either before, this has also been fixed by using the above (for me anyway)
[Samsung Galaxy Nexus] rmcsc:
You seem to have a rogue app sucking your resources to hell. Get Badass Battery and see what consumes the most battery life.
[Samsung Galaxy Nexus] franciscofranco:
Su binary is the problem 99% of the time, but Im not gonna bother trying to make people understand that, its not my job.
[Samsung Galaxy Nexus] nodstuff:
No, the problem is that his phone isn't utilising the 192mhz slot.

Its only going as low as 384 even though 192 is the selected minimum.
[Samsung Galaxy Nexus] yyz71:
Dude this has nothing to do with a rogue app!!! Simply 192 is not sticking :mad: