yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] LibertyMonger:
I figured it wasn't but never had that happen before. I was showing signal and it seemed to be ROM or kernel related. But I don't know much lol. I do know I have been having trouble making calls as well. Sometimes I try to call and phone stays silent and I hear my echo and other times calls drop right away. I realize none of this is kernel or ROM related just thought I need to post in case others are having the same issues. Just ignore me if not lol.

***EDIT***

Here is someone else with same issue,but I only seen it once. Maybe an AOKP issue...
[Samsung Galaxy Nexus] k_nivesout:
As of milestone 5, I still experienced a FC when selecting "storage" in the settings menu. There's been some discussion about it in the thread, something about mount points not being found due to some modifications CM made I believe. Other than that, it works great. Still kind of a shame though, since that's where the menu for USB mounting/storage is.
[Samsung Galaxy Nexus] aeroseek:
There is only one kernel...franco! lol. So the answer is I don't know if it happens on others. I also didn't have this problem prior to m5, but then I was running a different rom also (minco v2).

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] benkxda:
Storage in the settings is working ok for me with M5 && CM10 Nightliy from 27.08.2012.
[Samsung Galaxy Nexus] creeve4:
Still getting a FC with r246 and CM10 nightly 8/24.

I think it is due to the kernel using its own Ram disk instead of CM10's
[Samsung Galaxy Nexus] superbobup:
Ha I see :p

One thing you could try is making a nandroid, flashing a new ROM and see if that changes anything, or maybe ask Minooch if he changed/added some type of thermal criteria in v4
[Samsung Galaxy Nexus] JarGnex:
Idk if this has been reported before but whenever I want to listen to music either on my sony iPod dock or my home theater via aux the songs keeps pausing whenever a deep base is played for example I was listening to the motto by drake and the media player kept pausing. I tried it on the stock minco v4 player and poweramp music player. I'm on r246 running the 384mhz GPU
[Samsung Galaxy Nexus] jeetS:
Its a minco v4 issue...Not a kernel issue. I have it too...but mines random and has nothing to do with bass.

I think it has something to do with how the phone detects headphones... because when I listen to it with a podcast style app I use it will keep switching between headset audio to phone speaker audio. The music apps are set to pause if the headphones are removed...

Hopefully someone is looking into it.
[Samsung Galaxy Nexus] Dr_Ownage:
Havent forgotten to open camera?

I have a theory everyone who is getting bad battery. I also was getting pretty bad battery but was doing some reading while at work today and found that when your running android 4.0.3 Google recommends you run a bootloader of version PRIMEKL01, not sure about everyone else but i was on a VERY VERY old bootloader (PRIMEJK01 or something) i downloaded this new bootloader and it seems to have made all my battery drain issues disappear...

now this could be just coincidence however i haven't changed a thing. ill do a long test tonight, currently im at 90%

i didnt think bootloader had anything to do with battery or kernel or anything really for that matter, but maybe it does...

so again all those who are having bad battery, check your bootloader is the latest which is PRIMEKL01 :)

enjoy :)
[Samsung Galaxy Nexus] hitmanre:
Is it me or does 9.2 have worse battery life
[Samsung Galaxy Nexus] jan-willem3:
Yeah I got it since today. A month old but if you sim is one month old it is up to date enough.
[Samsung Galaxy Nexus] Dr_Ownage:
as i mentioned 2 posts earlier, check your bootloader version...
[Samsung Galaxy Nexus] incomer:
I've bootloader version PRIMEKJ10, where can I find the new one?

@Jan-willem3

Yeah sim is one month old.. It isn't a big problem, only in my home I have bad receiption, and there I see the switching between 3g and HDSPA is very slow/bad.. so when I'm home I need to set the radio on GSM only
[Samsung Galaxy Nexus] daandman:
PRIMEKK15 that I'm running is wrong then?
[Samsung Galaxy Nexus] EddyOS:
I seem to be getting some lag when waking the screen after it being idle for a bit. Once it's unlocked it's fine but the unlock slide is a bit stuttery. Only started this afternoon for some reason
[Samsung Galaxy Nexus] Dr_Ownage:
No, not wrong. Just old. Google released a new one. Good ol' Google :P

and apparently they recommend using it with 4.0.3

REMEMBER FLASH WITH FASTBOOT!

APPARENTLY this also works on LTE version. (BUT CHECK THAT FIRST)

i have a GSM version so that WILL work fine :)

link is here :)

http://www.box.com/embed/rmlduk4d3r58c3b.swf

and here once its finished uploading.

http://dl.dropbox.com/u/6390060/bootloader-maguro-primekl01_fastboot_flash.zip
[Samsung Galaxy Nexus] incomer:
Thanks!..

Flash with fastboot or is something else recommended?

Flash bootloader bootloader.img?

Edit:

Nevermind there is a batch file in the download!

Thanks!
[Samsung Galaxy Nexus] Dr_Ownage:
Let me know your findings with it hey. It seems to have fixed my battery one hell of a lot :)
[Samsung Galaxy Nexus] bebolf:
Would appreciate if you can post original link from Google ;)
[Samsung Galaxy Nexus] daandman:
Just to clarify I copy bootloader-maguro-primekl01.img to my tools folder, rename to bootloader & just enter fastboot flash bootloader bootloader.img?

Will my phone be wiped or anything if I flash it? Everything was wiped when I flashed KK15 & I didn't back it up because I didn't know it would be, but I think I did it wrong.
[Samsung Galaxy Nexus] incomer:
So far it is great, and my receiption problems are GONE:)? It is now switching between 3G and HDSPA far more 'natural'(so when it is going to 1 bar it looks like it is already searching for the 3G signal) so I've no downtime on Auto at the moment:)

Trying to try out some settings of the kernel(hotplug enabled now etc)
[Samsung Galaxy Nexus] ratson:
just execute the .bat in the zip, but it does what you described. no wipe is done/required.
[Samsung Galaxy Nexus] RVDigital:
No, I've designed the sheet from scratch, the values are generated based on a few data points I enter from test observations. I will be improving it as I go.
[Samsung Galaxy Nexus] Redflea:
Here are the CDMA links....for anyone interested...current CDMA bootloader is PRIMEL01.

http://rootzwiki.com/topic/12866-ra...ootcdma-galaxy-nexus-toroupdated-dec-23-2011/

This is kinda OT, sorry...
[Samsung Galaxy Nexus] just4747:
I think actually at the time I was on the Milestone 1 version of AOKP and just the stock kernel..I hadn't done Roman's kernel yet.

I miss that battery life. I could actually use the phone and not see a percentage drop for at least a few extra minutes compared to now. Not anymore now, on each kernel and ROM update, stays the same and sucks.

---------- Post added at 10:17 AM ---------- Previous post was at 10:12 AM ----------

Dude this won't help at all, it is just coincidence. I have that bootloader already and still get the same drain I described recently in this thread.

Won't do anything and has nothing to do with the battery.

---------- Post added at 10:23 AM ---------- Previous post was at 10:17 AM ----------

By the way Roman, purposely charged to 100 (98%) last night so I could see drain overnight (yes my phone is deep sleeping per CPU Spy). I woke up after about 7 hours on battery, phone sitting on my nightstand, and it dropped from the full 98% to 90%. I mean that sounds like more than others are getting and more than you say we should get.

If CPU Spy said that the phone was deep sleeping most (very close to all) of the time, then why would it still drain 8%???

And to hit even harder and make me more disappointed, after getting up and using the phone ALMOST not at all, but just enough to have the screen on a bit, I am already at 85%!! This is awful, I just can't get decent battery life trying anything. I literally practically don't even use it, but the act of having the screen simply on for like a minute total time makes it drop that much now. I mean, what the hell.

And I am on extended battery..what a joke.
[Samsung Galaxy Nexus] twilightrevenant:
I think the battery leaks when its at or near full. Definitely not a linear discharge. This is just my idea but I wouldn't test using 100% charged as reference point.

Btw, have you switched to stock kernel to see if if you could replicate your old results?
[Samsung Galaxy Nexus] just4747:
Just flashed stock boot.img for now..I'll see what happens but I don't think it'll help and I'll lose any speed that roman's kernel gave me..

Also, does it really matter if you keep the phone on CDMA mode vs. CMDA/LTE mode if you are in an area that you know has no 4G? It's affect on battery life is negligible right? Since the phone knows which mode to stay in automatically on CDMA/LTE mode??

EDIT: I pulled the boot.img from AOKP ROM which I use to re-flash stock kernel...I used the command "fastboot flash userdata data.img" in bootloader and rebooted. Is that right? It took a while to get signal back but I have it now. Just want to make sure I didn't screw anything else up or missed anything.
[Samsung Galaxy Nexus] billykxda:
In an effort to learn a bit more about kernels, I've spent the better part of the last week on Trinity. It's a good kernel for sure, but I am back to Francisco's kernel - 246 specifically. So far, 246 "feels" snappier. Battery life on Trinity was a bit better than M5. The color balance for whites seem somewhat subdued on both kernels - but that could just be my eyes.

In flipping through the Franco Install app, I may have inadvertently swyped the color multipliers to the wrong setting. Do they all default to 200? I don't want to re-flash and figured someone here could give me the heads-up.

Thanks!
[Samsung Galaxy Nexus] jtag PH:
The updater app should indicate Franco's recommended color values. You could also read back and there's a Google doc containing different color value combos.
[Samsung Galaxy Nexus] frenchy714:
The color multipliers (sliders) all default at 200.

EDIT: I may be wrong on that lol....I know Franco has its own color values when flashing but I adjust them immediately, so I can't remember exactly. In any case, the spreadsheet referenced in the above post is great to have and has a lot of different color settings you can use.

---------- Post added at 03:21 PM ---------- Previous post was at 03:15 PM ----------

Here's the link to the Google doc with the color settings.

https://docs.google.com/spreadsheet/ccc?key=0AmUsanWh1BpZdENqZ0FPQmRnUEs3SHBON1VsU3BmN0E#gid=0
[Samsung Galaxy Nexus] billykxda:
Thanks! I do believe that 200 is the default as well. I only mistakenly swyped one slider, and I recall they were all the same. So 200 it is.

I'll look back in this thread for that spreadsheet. If I don't emerge from this search adventure in the next few days, send someone in to pull me out. :D

Edit: DAMN you guys are fast! In the time it took me to write the sentences above, the link was provided! THANKS Frenchy!!
[Samsung Galaxy Nexus] Angelakaro:
I have a question: now that in stock jelly bean recovery has been introduced a new function to flash zip updates,is it possibile to flash the kernel with everything stock without rooting the phone?

EDIT: i know that this question has been already asked,but i want to know if with the new jelly bean recovery something changed
[Samsung Galaxy Nexus] franciscofranco:
Kernel default values are 182, 190, 200 with -4 0 5 RGB Gamma.
[Samsung Galaxy Nexus] gm007:
I tried the latest build 246 for a day, yes the phone is very responsive and wifi is much better but the data on 3g stopped several times and resumed after several minutes.

Anyway thanks for you hard work.
[Samsung Galaxy Nexus] billykxda:
Francisco,

Thanks for that!

You should know that in coming back to your kernel today from Trinity, I used your app and the default install set multipliers to 200, 200, 200. I prefer the kernel defaults you specified in the post above (182, 190, 200).
[Samsung Galaxy Nexus] The Gingerbread Man:
with fast boot you could flash it, any OTA update won't install because of non stock kernel. You could root, cwm flash kernel, use supersu app to unroot the phone and flash stock recovery to acheive what you say but its quite pointless imo and ota will still fail

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] grafyman:
I have problem drop calls and low signal...back to franco r243....thanks for your works franco...
[Samsung Galaxy Nexus] kashix:
which build are you on? R246?
[Samsung Galaxy Nexus] franciscofranco:
r246 boosted my signal so much, no more drops or grey signal.
[Samsung Galaxy Nexus] foueddyf:
Up to M5, that's what I used to get but with the wifi. I'd still be connected to the router but somehow internet wouldn't go through.

I would have to switch wifi off and turn it back on.

With r246, I can officially say this problem is thing from the past :) Those new wifi drivers are a godsend, thanks Franco!
[Samsung Galaxy Nexus] The Gingerbread Man:
R246, 1036 - 230 lazy CPU & 512 GPU kernel = good performance, perfect smoothness and fantastic battery life. I think I finally found the perfect balance

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Hungry Man:
Franco, the GPU voltage for CORE is now 974. Doesn't seem like it can go any lower (I can set it lower but it reports it at 974) - bug?

I think it's still misreporting because I can go down to a ridiculous voltage like 20mV and then suddenly it starts giving me issues, just as before but now it reports 974.

edit: Nevermind, it was smart reflex lowering the voltage of the next step up. My mistake.
[Samsung Galaxy Nexus] chugger93:
I couldn't be happier with this kernel. 246 rocks. I didn't use my phone a lot

..but 1 day 7 hrs is awesome.
[Samsung Galaxy Nexus] Hungry Man:
I may have mentioned this but governor settings do not start at boot. I have to change from interactive to another governor and then back for them to take effect.
[Samsung Galaxy Nexus] Serious_Beans:
You using supersu? It's sticking for me.
[Samsung Galaxy Nexus] Hungry Man:
Yeah, I am.
[Samsung Galaxy Nexus] franciscofranco:
franco.Kernel updater 6.3

Galaxy SIII:

* Add intial support for Power Modes - 4 presets and the ability to create your custom modes

Common:

* The cores panel is dynamic and if the kernel is onlining/offlining your cores you'll be able to see it watch live

* Fix two Force Closes when swipping the tabs

* Reworked the superuser root command function with better code and using threads when several commands are made

* Now will ask for root permission on app first start to prevent problems

* Several under the hood fixes

Should be available as soon as Google powers up their servers with red bull.

Please email me or post here before rating the app 1 star if you encounter a bug.
[Samsung Galaxy Nexus] creeve4:
Deleted
[Samsung Galaxy Nexus] bat0nas:
Hi,

I'm facing the data connection drops very often with r246. Was not that bad with previous releases.

What helps is: airppane mode off/on or data connection off/on in settings->data usage.

I am on latest minco ROM (v4).

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] armisis:
Ok, Tried r246 was on Milestone 5 (with AndroidMe CM10 (Latest Build)... On M5 running antutu benchmark i get the fastest scores yet, but r246 takes my benchmark rating from about 6400 down to about 5000... So I went back to M5...
[Samsung Galaxy Nexus] ceejay83:
You know benchmarks are useless right?
[Samsung Galaxy Nexus] kashix:
Are most of you on r246 or M5?
[Samsung Galaxy Nexus] Hungry Man:
246.
[Samsung Galaxy Nexus] Kurre:
Franco, have you studied ROW scheduler, if it would be beneficial to implement?

https://patchwork.kernel.org/patch/1274761/

It seems to be quite interesting, but who am I to say :D

But if you have any thoughts about it, I'd be very pleased to hear them :)

Sorry if this has been discussed before, I didn't find anything with a quick search.
[Samsung Galaxy Nexus] The Gingerbread Man:
I'm finding a bug with latest Franco app, changing power modes causes a force close, either in Franco preset ones or custom ones. I have sent a bug report through market both times.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] nnnnr14:
246

I got 99 problems but bamf ROMs ain't one! -nnnnr12
[Samsung Galaxy Nexus] tFrost:
246 runs incredibly smooth on my device, good job!
[Samsung Galaxy Nexus] kevinngck1:
Hi franco, cpu and color setting in your app can not be stick again
[Samsung Galaxy Nexus] Zflash:
Franco, your new app gives me a lot of fc's in the power modes menu.
[Samsung Galaxy Nexus] franciscofranco:
CPU stick just fine for me, I didn't change anything on that side.

Yeah thanks, I just realised I did something wrong, thanks.
[Samsung Galaxy Nexus] The Gingerbread Man:
It can't be easy maintaining 1 app for 3 devices, thanks for your support and looking forwards to the fix :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] eng.stk:
hi francisco, long time since u8800 kernel!

Now I have a GNex and first thing was trying your kernel ;)

I'm on #256 and it's very smooth. I found a little bug , kernel version says unavailable on system settings. I'm using CM10 JellyBro (other kernels show version just fine).

Nice work, as always.
[Samsung Galaxy Nexus] The Gingerbread Man:
#256 is not made yet hahaha 246 is latest but I think we all know what you mean ;) also the bug with kernel version not being shown in CM ROM is known :) you should try using the minco ROM (Franco helps develop it)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] eng.stk:
Obviously #246 :D

That ROM seems nice but it misses some Thigs I'm used to on CM.

I tried other kernels and it shows version correctly, weird bug :confused:
[Samsung Galaxy Nexus] derPianist:
I think I read a few pages back that it's because of the RAM Disk?

Franco Kernel uses his own RAM Disk while other Kernels are using the ROM built-in RAM Disk.

Am I right?

via Google Galaxy Nexus
[Samsung Galaxy Nexus] kashix:
Yes own tweaked ramdisk
[Samsung Galaxy Nexus] eng.stk:
yes should be it, makes sense.
[Samsung Galaxy Nexus] kashix:
Just to feedback, currently running on #246, sometimes there's disconnection of mobile data. It comes and go, not sure whether to revert back to M5 :confused:
[Samsung Galaxy Nexus] franciscofranco:
It's not easy, specially because I didn't prepare the app to host more devices from the beginning. But its looking better and better. Nexus 7 support will come when I think its ready and that'll make 4 devices :) Fix will come later than expected today, I have to write a review of the Lumia 900 and I only have 5 hours left :p

Its because of some of my changes to one kernel file that outputs the machine, host-name, kernel version. By default it shows "))" instead of the .version number of the compilation. Maybe CM did some changes to the framework and it doesn't read the file correctly. It doesn't bother me at all, it's in the bottom of my priority list.
[Samsung Galaxy Nexus] The Gingerbread Man:
I had a play with a nexus 7 today in car phone warehouse, its a lovely machine, really like it and the price is unreal considering the specs. The ui is so fluid and smooth and even had a quick blast on angry birds haha I'll be getting one when I have nothing better to spend £200 on :rolleyes:;) About cm, I say screw them and their little framework thing considering the **** they pulled on aosp tweaks and not crediting, but that's a whole other kettle of fish...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] J-Hop2o6:
Same, but mines doesn't FC, but changing the values is real sluggish. Also CPU and Color values aren't sticking after a reboot.

Same. CPU & Color values aren't sticking after reboot.

Can't wait for the fix :victory: And nice explanation on the missing kernel information in the about phone section. Hopefully you fix it since its a huge eye sore! :p j/k.

What did they do exactly? I didn't hear about this I think.
[Samsung Galaxy Nexus] franciscofranco:
Are you using SuperSu? Mine stick just fine! Try to remove the app and install is again.
[Samsung Galaxy Nexus] coolpages:
I'm using Franco Kernel updater 6.3 and JB246 in AOKP JB Nightly Aug 29.

Each time I tried to apply the Custom Power mode with the Franco Kernel Updater 6.3, the Franco Kernel Updater 6.3 crashes.

So I deleted the Custom Power Mode I created and recreated them, rebooted my my Galaxy Nexus. Unfortunately the problem does not go away and Franco Kernel Updater 6.3 crashes although it seem to set the parameters correctly on the Galaxy Nexus.
[Samsung Galaxy Nexus] franciscofranco:
Already said last page..
[Samsung Galaxy Nexus] J-Hop2o6:
It worked perfectly fine for me before the latest update using SuperUser. I even removed Franco app permissions, then added it back. Still no luck. Should I uninstall, then reinstall it?
[Samsung Galaxy Nexus] TEK112:
You should switch to SuperSU.
[Samsung Galaxy Nexus] IgnorantNerd:
Just flashed Milestone 5 and I'm wondering what settings are you guys using for great battery life without sacrificing too much performance? I've seen some ridiculous 4+ hours screen on times in this forum and I'm trying to get there as well.
[Samsung Galaxy Nexus] kashix:
you're already using it. The default configuration is the way to great battery life.
[Samsung Galaxy Nexus] stick1300:
Settings didn't stick on reboot for me either. Using SuperSU. Going to reboot again and see.
[Samsung Galaxy Nexus] TEK112:
That usually requires a franco data wipe of the app and reinstall/set-up.
[Samsung Galaxy Nexus] stick1300:
Update: worked fine that time. I think it had to do with being the first reboot after an update
[Samsung Galaxy Nexus] J-Hop2o6:
Did a data wipe --> negative

Did a un/reinstall --> negative

Franco has to fix it. And I overwritten the old backup (before I knew about the bug) so I can't restore the old version :( Just gotta avoid rebooting until the fix.
[Samsung Galaxy Nexus] osm0sis:
No. YOU need to install SuperSU. I too was reluctant about switching from SuperUser (since I'd paid for it), but honestly, SuperUser is very broken. I tried to mess around to keep it working by using older su binaries and all sorts of tricks but nothing involving SuperUser would stay working 100%.

SuperSU worked immediately and I've experienced zero issues with it. Switch. Rejoice.
[Samsung Galaxy Nexus] marcuso:
persistance-setting is not a SuperUser Problem! Happens to me with SuperSU as well since latest update ...

Tried re-installing/app-data-reset/reconfiguring any anything else i could think of .. no luck :(

I had the same issue a long while ago when i still was on ICS before.

That time franco also was claiming that it "should work" when it wasn´t. (that time I tried 4 different ROMs, did a couple of wipes etc .. nothing helped)

I was not using francos app for a while, but it used to work fine on my JB Rom (MCR) during the last weeks .. until the recent update.

Using superSU here - and also there i gave the app "fresh" rights.

I logged the commands (with SuperSU Pro) and found after reboot only one command (setting color multipliers) is run .. no OC/governor-settings.

When app starts it does only chmod cpu-max, but not setting it.

In the app the settings are just default then (not what has been set before) ... when setting again this works.

After reboot everything is default again and nothing is set.

:((
[Samsung Galaxy Nexus] joaquinf:
Nice kernel!

Hi franciscofranco!

I'm new to the nexus community (coming from htc sensation) and i've flashed your jb kernel yesterday (M5) as soon as i got my phone. So far the performance is mindblowing and the battery life seems promising, though i'll have to wait a couple of charging cycles to let things settle a bit.

I just wanted to say thanks for your work and all you've done for this phone. To show some support i've purchased your kernel app and i'm loving it :good: i'll play with it and try to find the perfect spot. I'm curious about the color and gamma tweaks. Let see how thing goes.

Keep up the good work buddy, and i will try my best to somehow contribute to your thread.

EDIT: on the other hand, for me settings does stick after a reboot :)