yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] sishgupta:
80% I got it cuz im a HUUUUGE effing nerd and i like to do nerdy stuff.

20% cuz i wanna:

- be able to grab files off of a friends USB thumb drive while im out and move it to my phone instead of taking his thumb drive.

- hook up random USB devices. Like I can control my canon 50d with my android now due to Chainfire's sweet app. https://market.android.com/details?id=eu.chainfire.dslrcontroller

- I can also hook up a gamepad and use it in some games.
[Samsung Galaxy Nexus] loudaccord:
you sir, put me to shame. All cool stuff.
[Samsung Galaxy Nexus] Icey34:
`

Can I somehow run auto-brightness without this? Any flashable ninja zips?
[Samsung Galaxy Nexus] eiabea:
:-D same here ;-)

flashed 17.2 again, but my usb stick only blinks shortly and thats it

worked fine with 15.2
[Samsung Galaxy Nexus] kimboinatl:
What settings are you guys using in the color control that you feel give you the best display?
[Samsung Galaxy Nexus] minipaolo:
I'm using -2 0 2
[Samsung Galaxy Nexus] thegtfusion:
Franco we miss your updates in your Nexus S kernel!!!! :(
[Samsung Galaxy Nexus] Nebucatnetzer:
Get a Galaxy Nexus and you can have as many as you want. :D
[Samsung Galaxy Nexus] kimboinatl:
Something else I noticed - the Hot Plug Mod option is not staying checked in the updater for me when I reboot. Was this turned off or something? Or is it only available with certain governors?
[Samsung Galaxy Nexus] whiteintegsg316:
What is the hot plug mod?
[Samsung Galaxy Nexus] kimboinatl:
1st option below:
[Samsung Galaxy Nexus] whiteintegsg316:
OK thank you now I need to buy his app. I did not know it had all of that in it
[Samsung Galaxy Nexus] Gahh Its Lee:
You don't need to. You can enable it in terminal but if you like his rom its a nice way to donate more or less.
[Samsung Galaxy Nexus] samizad:
Love the Navigation Bar with Fry from Futurama. Will I find the mod in the Themes section?
[Samsung Galaxy Nexus] johno168:
OMG! Love it it looks awesome! gota link for that?!
[Samsung Galaxy Nexus] HRodMusic:
same question
[Samsung Galaxy Nexus] franciscofranco:
Ok, my mac has been moody since yesterday, and I only got it up and runnin' one hour ago, gonna work on this kernel now, thanks for all the feedbacks and bug reports.
[Samsung Galaxy Nexus] kimboinatl:
Thanks guys! I made the Fry search button myself. I was going to make other buttons based on other memes or maybe the Futurama characters, but I just haven't had time to finish them. I'll attach the image files for Fry, feel free to use it if you want (if you need to know how to use it you can just PM me, I don't want to de-rail the thread). They're white on a transparent background, just hover inside the attached thumbnails box.
[Samsung Galaxy Nexus] whiteintegsg316:
Sweet
[Samsung Galaxy Nexus] poopooface:
Sorry for being a difficult customer, but after getting excellent benchmarks and great performance in 17.2 right after turning 2d hardware accel on, my device inexplicably started lagging again a few hours later. Now I can't even type stuff in evernote without the keyboard lagging several seconds behind my fast typing. This happened on stock and Jame Bond kernels, but never with Franco before! If there is any log I can send, let me know.
[Samsung Galaxy Nexus] franciscofranco:
Dmesg please!!
[Samsung Galaxy Nexus] poopooface:
I uploaded my logfiles to:

http://pastebin.com/W2LkY3zr

using the GetLogs program. I think that includes dmesg.

I generated dmesg manually using the command prompt on my computer, entered the last **** I saw as a search, and it appeared at about line 9000 of the pastebin file lol. I'm sorry for the length of this; please feel free to let me know if there is a way to get dmesg in isolation. I first noticed that it was really slowing down at about 8:00PM EST (USA time) tonight.

Thanks again for all the great work! I appreciate your help.
[Samsung Galaxy Nexus] franciscofranco:
Nothing is showing on the logs...Which frequency are you using?
[Samsung Galaxy Nexus] Heroic_Kaizer:
where can I get to the kernel settings to change the color temp?
[Samsung Galaxy Nexus] AzzaD:
I'm on 700-1200 francoturtle on 17.2, AOKP Build 23, and still it seems when I reboot I get about 0:20 seconds of 350 MHz in CPU Spy even though min is MHz, is this a bug?
[Samsung Galaxy Nexus] ratson:
really rarely I got myself in the situation that after unlocking the screen the screen stays unresponsive. I can set the volume, use the knobs, but touch screen is off, only a battery pull helps. this happened to me with many versions, but only once in a week (I could not get a dmesg so far)

anyone with same issues? how can I help in the resolution?
[Samsung Galaxy Nexus] stesmi:
Wait, what?

// Stefan
[Samsung Galaxy Nexus] anoraknophobia:
Anyone has the default voltage settings from the 17.2 Kernel for me ?

Currently the Franco app shows me the following:

1500 MHz - 1400mV

1350 MHz - 1380mV

1200 MHz - 1380mV

1000 MHz - 1317mV

700 MHz - 1203mV

350MHz - 1025mV

Looks pretty high for me. Think i had much lower voltages in earlier kernelverisons.

I am running the francoTurtle gov.
[Samsung Galaxy Nexus] yyz71:
Just did a benchmark test with 17. No UV!! And the result are wow :-)
[Samsung Galaxy Nexus] lollo1927:
I have a little problem:

I'm trying the rom M3 with 17.2 kernel and I have two Nexus.

I installed everything perfectly equal, but one also goes to great at 1.5 GHz, the other is wrong, I have to use up to 1.35 GHz ... HELP
[Samsung Galaxy Nexus] khenderick:
That's normal. Every CPU die is different, and the smallest difference can make 1.5GHz stable on one phone and unstable at another.
[Samsung Galaxy Nexus] lollo1927:
Provided that at 1.35 GHz is just fine, there's a way to change some parameters to make them equal?

Thanks...
[Samsung Galaxy Nexus] yyz71:
The funny thing is 17 works great on my phone with 1.5 but once I upgrade 17.1 And upwards everything seems to stutter!!
[Samsung Galaxy Nexus] poopooface:
FrancoTurtle 350-1500, GummyNex 0.7.0

Thanks again!
[Samsung Galaxy Nexus] kimboinatl:
This is what I noticed too. I think I read that Francisco had to make some modifications to the kernel to make it more stable, which might explain the difference. Is anyone here still running 17 without problems?
[Samsung Galaxy Nexus] AzzaD:
sorry, don't know how I missed that but I meant I'm getting a short period on 350mhz on boot seemingly even though its not in my frequency range I've chosen (700-1200MHz)
[Samsung Galaxy Nexus] avelec:
I,m still running 17 since it came out without any problem (didn't even bother to update). Running FrancoTurtle 400-1500, AOKP-23. Phone has the best battery live 19 hours with 10% left with more than 1 hour call time, about 1.5 hours screen on time. Phone is fast, cool, and not a single problem. Thanks Francisco.
[Samsung Galaxy Nexus] THE_KINGDOM:
What are u experiencing on the phone that the 1.5GHz is "wrong"?
[Samsung Galaxy Nexus] EsPeHil:
These cpu's are made to run at 1.2 GHz. Anything above it is just extra. Just like with desktop cpus. Not all overclock like crazy. My old Athlon XP 1800+ overclocked from 1.53GHz to 1.6 while my friend rocked it over 1.8...
[Samsung Galaxy Nexus] lollo1927:
One is fast, the other hangs for 5-10 seconds on each page, which is home applications that drawer ...
[Samsung Galaxy Nexus] kimboinatl:
Thanks for the reply. I'm going to back off to 17 and use the same governor settings and see what happens. Just an experiment... not like I NEED 1.5Ghz, but I'm interested to see if I get the same results as before.

EDIT: Just downgraded to 17. Runs smoothly at 1.5Ghz using FrancoTurtle and FrancoGazelle (so far). Running AnTuTu now.

EDIT: Well, that's interesting... I got an AnTuTu score of 5000. I was expecting it to be a lot higher. I'll try it again with 17.2 and 1.35Ghz.

EDIT: Still hitting scores around 5000. It should be way higher than this... according to this I'm running slower than an LG2X.
[Samsung Galaxy Nexus] xdafann:
Hello!

Tried to install 17.2 with latest apex, but getting bluer blacks now.

I can notice that in the settings menu as well as in the messages upper side.

Any solution?

Thanks
[Samsung Galaxy Nexus] Malarie:
Upgraded to frannko.. For some reason, My battery never drained thats fast. I have AOKP MS 3 and latest Franko Kernel.
[Samsung Galaxy Nexus] mtmjr90:
I had a similar horrible battery issue with AOKP 23 and FK 17.2 but after about a day, it settled down and I'm getting decent battery life again. Could be better...but then, it could always be better;) Fwiw, I switched it to 3G only for a while but idk if that did anything...
[Samsung Galaxy Nexus] THE_KINGDOM:
Oh ok I see. Could thanks just wanted to know. I had a little lag on 1500 too, a bit more lag than 1350. So I stuck with 1350
[Samsung Galaxy Nexus] jkoljo:
I have had multiple reboots while under high system load with 17.2, stock settings :/ Apex 1.0.2 ROM
[Samsung Galaxy Nexus] drawde40599:
buy francos kernel app and adjust it (color)
[Samsung Galaxy Nexus] lollo1927:
...me too...
[Samsung Galaxy Nexus] magn2o:
5678 @ 700-1500 (ondemand) on #17 with AOKP b23.
[Samsung Galaxy Nexus] stagejuan:
Hey guys really want to try this out... from what Ive seen mostly everyone is using a ROM even for the 4.0.4 ... Im on stock 4.0.4 ROM... anyone using this kernel on a stock 4.0.4 ROM? just looking to pickup some better battery life
[Samsung Galaxy Nexus] IINexusII:
guys you do know that antutu app had updated, and changed some of the settings for ICS, so we would be getting lower scores than normal. i can get 6200 with 1200-350 on francoGazelle and with turtle its about 5800.. if you're just overclocking for benchmarks then you're wasting your time. test it using linpack or with games
[Samsung Galaxy Nexus] cLOUDFAn:
a few pages back someone posted a screenshot showing 74xx

i got 66xx (350~1350) or 67xx (350~1420) with 17.2 (or lean 2.0.1) + aokp m3
[Samsung Galaxy Nexus] drawde40599:
Battery life with this kernel and stock is exactly the same for me, I tested 100% stock rooted rom with this kernel (4.0.3), speed is the difference for me, this kernel way faster . I no not exactly reply ur looking for but 4.0.4 can't be that much different . The guys showing 24+ hours of phone time have everything turned off (data, wifi, screen MHz turned down ......) or there not using the phone . I have brightness turned all the way up, wifi, data on 100% of time and I'm texting 300+ texts a day some internet 5-6 phone calls and when I'm not " crack flashing " roms or kernels I get 10-13 hours out of full battery . This is exactly about the same as any of the 13 androids I've owned . So my opinion u should flash this kernel because it runs perfect and is fast ,better battery??? Maybe,? I don't get better battery but I have a charger so.I.don't care . Its definitely worth trying and if u don't like it Google has stock kernel and Rom file available so real easy go back .
[Samsung Galaxy Nexus] Shetlander:
Bad news im afraid Franco. After an hour I have just woken my phone up and had a spate of bad graphical glitches which took at least 10 presses of the power buton to put right.
[Samsung Galaxy Nexus] Waitzar:
I just flashed latest kernel build# 12122011. The only changes I did to the phone after the flash was set UV settings as follow:

1200 @ 1150

920 @ 1100

700 @ 950

350 @ 900

Everything seem to be running fine after the flash except weird SuperUser permission issue on the first boot after the flash. As soon as I entered my PIN# I was greeted with the message "Light Flow SuperUser Denied". So I opened up Light Flow app and asked me for Permission, I set it Allow and didn't receive the same SU Denied message after subsequent reboots.

Also, Beautiful Widget gone weird. The clock widget didn't render correctly (missing borders and background colors). I dragged the widget in the trash and drag a new clock widget back on the homescreen which rendered correctly until I rebooted the phone. The problem returned. So I uninstalled Beautiful Widgets apps and reinstalled it. That fixed the problem for good.

I am using Stock ROM with this Kernel.
[Samsung Galaxy Nexus] sqx:
Is this kernel compatible with revolution HD rom?
[Samsung Galaxy Nexus] inffy:
Well...what do you think? :D
[Samsung Galaxy Nexus] Shetlander:
Franco. Just installed CPU spy and it shows something interesting. It shows time in state at 1400mhz as 1min 19 secs. It also shows phone in a deep sleep of 43mins 53 sec. I am using the OC kernel but it is set at a max of 1200mhz.

Im wondering if the glitches are a combination of waking from deep sleep to a freq that doesnt work or maybe a gpu with not enough juice for the OC to wake quickly?

Im alot more experienced in overclocking PC,s but would think the same principal applies to any silicon chip.

EDIT - I am using the HD ROM and apart from the ongoing recognised problem it works fine with it.
[Samsung Galaxy Nexus] sluflyer06:
My first boot into the Kernel also started me at 1.4 for some reason. I went into SetCPU and moved teh slider down and back to 1.2 and it hasn't allowed itself back at 1.4 since...also when I ran antutu it showed my CPU speed as 1200000mhz or a similar amount of zeroes.
[Samsung Galaxy Nexus] joshnichols189:
I too have seen the speed in setcpu at 1400 when I have a set max of 1200
[Samsung Galaxy Nexus] Shetlander:
SetCPU showed 1200mhz as soon as it was booted up. I have never had to change the slider but it seems strange why it would use 1400mhz?
[Samsung Galaxy Nexus] franciscofranco:
I have no idea actually. Try to run with the no overclock kernel. I'll talk to coolbho about it.
[Samsung Galaxy Nexus] EddyOS:
I've had no issues so far on the non-OC kernel. All seems to be behaving
[Samsung Galaxy Nexus] Kraenesk:
Have you considered a 1200 kernel with just gpu over clock? I hope liveOC comes here at some point. Loved that on my ns. Was using your kernel on ics
[Samsung Galaxy Nexus] GchildT:
Short answer; yes.
[Samsung Galaxy Nexus] sluflyer06:
OK. Something is def. up with this Kernel. Yes it is for sure booting at 1.4ghz, and

big.

Getting 6%/hr battery drain while in deep sleep. My worst ever battery drain before this was 3-4%/hr. I'm going to flash the non-OC kernel.
[Samsung Galaxy Nexus] franciscofranco:
I just contacted coolbho to be sure that the issue is mine or from his code.
[Samsung Galaxy Nexus] Shetlander:
Already flashed it. Testing it and will see how it goes. So far there is no 1400mhz in CPU spy and the phone appears to be going into a deep sleep OK.
[Samsung Galaxy Nexus] sluflyer06:
I flashed non-OC version (which I only use the OC version for UV anyway). reset all the state timers and betterbatterystats and left my phone alone starting 10 minutes ago, I'll report back in an hour and see where the battery stands with no use.

Which brings up a question..I thought only the OC kernel allow undervolting? I'm still able to set UV..maybe I forgot the chronology of changes to the kernel.
[Samsung Galaxy Nexus] franciscofranco:
The no OC version has undervolt. The only difference between the kernels is that one has Overclock and the other one doesn't.
[Samsung Galaxy Nexus] dwang:
Deep sleep working fine here.
[Samsung Galaxy Nexus] :
Deep sleep fine here too. Anyone recommend a lite app to under volt?
[Samsung Galaxy Nexus] sluflyer06:
SetCPU works well.

EDIT: used 1% battery in the last 30 minutes, stayed in sleep the whole time. Unless there is another update today I will charge my phone to 100% before I go to sleep tonight and let it drain overnight. wakelock doesn't seem to show any problems, few different processes going for a couple seconds each.

That would still be ~16% drain overnight which is still way high compared to others phones (like GS2, Evo 4G) but it would be an improvement for THIS phone since I've had it. Time will tell.
[Samsung Galaxy Nexus] ChongoDroid:
I get great battery on Pauls pre beta 2 4.0.4
[Samsung Galaxy Nexus] Shetlander:
From my experience with #17 etc I have found that running at 1500Mhz results in severe thermal throttling leading to low scores. I had managed a run of Antutu with a score of 7184 at 1500Mhz but that was acheived by running the phone in the fridge to reduce thermal throttling. With kernel 13.1 @1350 I can regularly get over 7000 with Antutu and that is with the phone used as normal not in the fridge. I am currently using 15.2 which returns a score of just under 7000 (6984).

I have come to the conclusion that 1500Mhz is just plain old impractical and results in slower speed with a bit of use than a lower clock speed. I feel the better way forward would be to raise the max clock to say 1382Mhz and overclock the MPU like Ezekeel has done.
[Samsung Galaxy Nexus] viskas:
With 17.2 my gnex is heating up like it never did before. How can I solve this?!?

Ciao!!!
[Samsung Galaxy Nexus] renaud:
You guys should really stop using your phone for the sole purpose of running benchmarks.

This phone already gets throttled when at 1200, what do you expect from 1500?

If you really have nothing more interesting than doing benchmarks, ask Franco for a 2.4+ghz kernel and find a liquid nitrogen shop to be able to cool the phone... at least that would be worth a viral video on YouTube

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] stagejuan:
Thank you sirr
[Samsung Galaxy Nexus] ironeagle:
Anyone facing SMS issue?, I can't sent SMS :-( Maguro Build 23 - Franco 17.2

Resolved :-) I screwed up SMSC setting for my carrier
[Samsung Galaxy Nexus] akce2001:
I was wondering if AVRCP1.3 support which has recently been added to Bluez stack can be added to the kernel or there are other dependencies that prevents it from working? Thanks,
[Samsung Galaxy Nexus] franciscofranco:
I think I have to do a rebase. I'm gonna stop pushing mainline kernel patches as they've proved to be worth more trouble than they are worth and I really can't afford to have a unstable kernel for some users. This is gonna take some time, but I'm sure it will be totally worth it.
[Samsung Galaxy Nexus] clefster:
I've noticed a few reboots last couple of weeks (starting from around 16.1/2 I think).

Here is the last_kmsg bit:

[49393.789794] EXT4-fs error (device mmcblk0p12): ext4_ext_insert_index:798: inode #73336: comm flush-179:0: ix > EXT_LAST_INDEX!
[49393.790008] Aborting journal on device mmcblk0p12-8.
[49393.817962] Kernel panic - not syncing: EXT4-fs (device mmcblk0p12): panic forced after error
[49393.817993]
[49393.818176] Backtrace:
[49393.818328] CPU1: stopping
[49393.818389] Backtrace: invalid frame pointer 0x00000098
[49393.818634] Rebooting in 5 seconds..
[49398.098480] Restarting Linux version 3.0.21-franco.Kernel-nightly-17.2 (francisco@francisco.local) (gcc version 4.4.3 (GCC) ) #47 SMP PREEMPT Wed Feb 15 01:45:08 WET 2012

Any ideas?
[Samsung Galaxy Nexus] chakra:
Your kernal has been great for me. I stuttered a bit at 1500 on 17.2, but maybe my phone just can't hack it. I have not tried 1500 on 17, but it runs fine at 1200 for me. Thanks and the app is great.
[Samsung Galaxy Nexus] XanSama:
Thankyou, thank-you, thank you. Was beating my head on this issue.

I've created and attached a CWM installer for busybox 1.19.4-cm9 for anyone else who is interested. Perhaps Franco will put a link/note in the OP?

Edit: Fixed CWM file...
[Samsung Galaxy Nexus] bradm23:
hahaha, like the post a few pages back that the kid got his 7000+ benchmark because he put it in the fridge.. seems pretty crazy to even think of doing this :eek:

The has to be the most flooded thread I have ever seen on any forum. I think we should get back to discussing kernel related development and leave the noob question and the benchmark talk to the Q&A or general section... Maybe someone should come up with a wiki?
[Samsung Galaxy Nexus] kimboinatl:
I realize that benchmarks should not be the reason one installs a kernel. That's not why the subject was broached. You would expect to see benchmark scores that are at least around the same benchmarks you would get with a stock Galaxy Nexus... Now I haven't changed much around on my phone since first installing this kernel (which gave me a great score the first time I benchmarked it), so that's why I asked about bechmarks, because mine has actually gone down. So I thought it was worth asking how others fared, and whether other people were seeing slower scores as well; this was all meant to help me figure out if it was my kernel or some other issue with my phone. Unfortunately, scores seem to be all over the place, so it's sort of inconclusive to me. I'll probably just have to temporarily go back to the stock kernel to know for sure.

For those who checked their scores, thanks again, much appreciated.
[Samsung Galaxy Nexus] DarkGruf:
I have gps fix issues since 17.x. The gps see the birds in instants but the phone can't compute a position within some minutes (around 2 minutes) when it is some seconds with 16.x. I use GPS status to know when the position is done and the satellites stay in "grey" for a very long time even if they are detected at once and even when the bars turn green it's very long to get a position.
[Samsung Galaxy Nexus] dirtyhank:
Given the controversy I decided to run a few benchmarks and to my surprise going back to 15.2 made my AnTuTu scores go up by 1000 points (mainly due to RAM and CPU scores). And although this is totally subjetive the phone feels a bit snappier.

I agree benchmark scores aren't the holy grail but when run under same conditions (as I did) they can help profiling new features.

PD: All tests run under francoGazelle and a max freq of 1350MHz.
[Samsung Galaxy Nexus] nory82688:
Hey can someone post Francos 17 kernel for me? I would appreciate it
[Samsung Galaxy Nexus] marc.tulley:
Its been posted twice now and .1 once. Have a look several pages back
[Samsung Galaxy Nexus] nory82688:
I did. I found it.......
[Samsung Galaxy Nexus] maisi:
I have exactly the same error! I thought my phone was damaged but since you get the same error, even with the same index, i can now be sure it's a kernel issue. (works on EVERY other kernel)

Does it happen to you when you write data on the sdcard?

Maybe we aren't the only ones and some other error's are based on this problem.

I'm trying to build a version of Francos kernel without his ext patches but currently I can't get Linux to build my code correctly :(
[Samsung Galaxy Nexus] Shetlander:
KID!:rolleyes: Compliment I suppose considering im 41 years old.:D

As for crazy, not really. The temp in a fridge is about 4c so its not even freezing. Its a bit like overclocking a PC CPU. Some people do use liquid nitrogen, I personally use water. Its about dissapating the heat so as not to hit the thermal limit. If the surrounding area is cool enough it will absorb the heat more readilly from the CPU.
[Samsung Galaxy Nexus] clefster:
Not specifically.. noticed it while using Chrome a few times which probably is storing cache etc. I think it's also usually while the phone is charging at the same time (when I'm in bed about to sleep and using phone)
[Samsung Galaxy Nexus] kimboinatl:
I just tried this. I backed off to 15.2, set my speed to 1350 using the performance governor, and my score jumped up to 6070 (about +1000 or more)... Still a little low, but I have other stuff running and my phone is a little warm from charging all night. So this seems to be an improvement.

Francisco, if it helps any, I was noticing the biggest slow down during the 3D test when on 17.2. It would run fine, and then "hiccup" - I could actually watch it occasionally slow down to 40FPS.
[Samsung Galaxy Nexus] Qortez1:
Could you post a link to 15.2 would be much appreciated my good sir
[Samsung Galaxy Nexus] poopooface:
Same here... I found that wiping cache and dalvik eliminated the most extreme of the ass performance, but I get the same experience with the mid-animation slowdown as this guy in the AnPooPoo knights part.

Similarly, when I enter a big block of text in Evernote, it will start out OK but then hiccup after about 15-20 seconds of continuous input. Then when I hold down the delete key, it will be smooth, then hiccup, smooth again, hiccup, etc.
[Samsung Galaxy Nexus] phunghoang24:
+ 1 exactly!
[Samsung Galaxy Nexus] franciscofranco:
I'm aware of all the bugs, I'm working as we speak on the rebase, I cleared my day's schedule for this.