yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] dansan382:
Actually.... I know the whole thing about how it turns blue when connected to the servers but I have screen shots showing speed tests going, me on Facebook, doing a Google backup and the 3/4G icons were gray. The signal bars were blue though. One build 5 my 3/4G is always blue. No biggie though. Just a personal pet peeve
[Samsung Galaxy Nexus] fullmetal509:
Anyone else tried experimenting with other kernels? I'm running Francos Milestone 6 and I still lag on certain areas especially playing music and web surfing at the same time.

Via Galaxy Nexus [LTE]
[Samsung Galaxy Nexus] IAreKyleW00t:
I'm using the LeanKernel that came with it, sort of. The developers for AOKP seemed to have messed with a few things - rendering some features completely unusable (a main one being the GPU OC'ing).

I fixed this by simply flashing the "official" leanKernel (latest stable). All this does is 'fix' a few of the missing features. I dunno why they were missing to begin with, but so far I'm enjoying leanKernel with AOKP. The color seems surprisingly good for me (which is a big thing for me). Benchmarks in Quadrant aren't the "best", actually scoring lower than the stock GNex - but I never trust those number for how well my phone really is. I only do it to get a good idea - and bragging rights of their high. ;D

Overall, I'm enjoying M1 - seems incredibly nice, and the implementation for a custom kernel I find to be a great idea. leanKernel is known for having great stability. I feel as though those 'removed' features were set like that in case someone else wanted to flash a different kernel without the "mess" that gets left behind.

I'm sticking with leanKernel for a bit - gonna see how well it rolls. My settings are below.

CPU: 350/1200 (there isn't a 1MHz option apparently... just goes from 920 > 1200)

Governor: InteractiveX (For better battery life)

GPU: 384MHz (using the command in the terminal: oc gpu 1)

I/O: SIO

TCP: westwood

Using the franco.Kernel App
[Samsung Galaxy Nexus] joshuajones:
I'm pretty sure blue means it's connected to your Google account. Because it stays gray before you flash gapps or if you have a Google sync error
[Samsung Galaxy Nexus] crobs808:
OK. Still confused by your wording though...By "icon" do you just mean the text that says "3G" or "4G"? Because that changes color with the signal bars. I'd really like to see one of your screenshots so I can see what you mean since mine always change together.
[Samsung Galaxy Nexus] fullmetal509:
Thank you sir :) Can you send link to most recent stable version?

Via Galaxy Nexus [LTE]
[Samsung Galaxy Nexus] IAreKyleW00t:
I most certainly can. Here you go!

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

When I "flashed" it, I just used franco's App to have it download and "auto-flash" it. Seemed to work for me since it fixed the issues I was having, but I assume it's no different. No need to wipe cache's or anything (although, you can if you want). Just flash it over and it'll overwrite what's there and add what's missing.

haven't had a single issue since. ^_^
[Samsung Galaxy Nexus] badboyg200:
sms

Is there anyway for quick reply to already be active once the screen is unlocked?? I find it kind of irrelevant unlocking my screen, going to the top and sliding down my bar then choosing quick reply just to respond. Is there anyway for it to just be open once I unlock it???
[Samsung Galaxy Nexus] crobs808:
You should be using Trinity:

http://goo.gl/8L4QI

---------- Post added at 09:22 PM ---------- Previous post was at 09:21 PM ----------

You can slide it down w/o unlocking.
[Samsung Galaxy Nexus] IAreKyleW00t:
Trinity is incredibly unstable for me no matter what version I use... I always get constant crashes. :\ plus, I'd like to try out how well lean kernel is. :p
[Samsung Galaxy Nexus] crobs808:
Most ppl flash the wrong version. Or they tweak OC, governor, voltage, etc. When it comes to kernels they run BEST when left alone.
[Samsung Galaxy Nexus] IAreKyleW00t:
It was the correct version... 384GPU, latest stable on the default settings. I go to run quadrant and it crashes my phone every time... Any other kernel is fine though. I Dunno what it is but it just doesn't like my phone for some reason.

Regardless, I'm liking lean kernel so far. I might actually stick with it. (Coming from Air Kernel)
[Samsung Galaxy Nexus] crobs808:
User error. Ran perfectly:
[Samsung Galaxy Nexus] IAreKyleW00t:
Call what you wish,I just haven't had a good time with it. I didn't see any noticeable performance improvement while I did try and use it anyways. Oh well, some people do better with other kernels. Is just person preference. ^^

Also, I score a bit higher or about the same on lean and air. :p
[Samsung Galaxy Nexus] crobs808:
You are speaking as if benchmark scores actually matter ;) Use what you like. I just want to make sure people aren't attributing crashes to kernels. It is rarely the kernel.
[Samsung Galaxy Nexus] Beamer9408:
I don't think it is user error at all some kernels run better for others. I for one can't use lean kernel it causes reboots on everything stock. Trinity runs fine for me faux doesn't do well for me either.
[Samsung Galaxy Nexus] Beamer9408:
Little preview of things being worked on.
[Samsung Galaxy Nexus] IAreKyleW00t:
Benchmarks mean absolutely nothing. Now, I'm going to leave this pointless conversation. :laugh:

Also, I like the colors on leanKernel. ^^
[Samsung Galaxy Nexus] crobs808:
It's always user error. A kernel will only run as well as it is treated but the right flashing order and formatting must be done prior. Sequentiality matters when flashing a new ROM and all the subsequent pieces.

There's a ridiculous belief that each Galaxy Nexus is "unique" (same belief exists among other models as well). A phone is not a biological organism. It is not like humans, who all respond differently to the same medication. A VZW Gnex is a VZW Gnex. If one Gnex is not behaving like another then the cause is 100% software based. I'm amazed that they are so many tech-minded people on here that believe in voodoo.
[Samsung Galaxy Nexus] Beamer9408:
No, just no. And flash order for a boot.img? Phones act different man. I'm guessing you fastboot erase boot before you flash a kernel???? Anything else would be pointless.
[Samsung Galaxy Nexus] crobs808:
My claim is that all phones OF THE SAME MODEL will act the same as long as the same software is on them. Sure, a VZW Gnex will act differently than a GSM Gnex, but that's a different model. My statement is that all Verizon Gnex's will act the same if the flash process and software is identical. Programs only do what their are told - there's no subjectivity to this but you are free to believe whatever works for you. (Not trying to sound condescending, just trying to keep thread logical)
[Samsung Galaxy Nexus] Beamer9408:
So if they all act the same on the same "phone" why do you prefer one over the other?
[Samsung Galaxy Nexus] crobs808:
I never said the kernels all act the same. Forget it ;) PM me if you want to continue this.
[Samsung Galaxy Nexus] iconaw1:
Oooooo I want that lock screen :)
[Samsung Galaxy Nexus] ThunderStick:
Accessibility features not working, talk back crashes constantly when enabled.

Only problem I found. Seems to be consistent through all aokp or cm based roms...
[Samsung Galaxy Nexus] mrbigdrawsz:
I'm getting System UI crashes when trying to go to Google Now using the Home button and drag up route.

Anybody else have this happen? Any idea how to fix? I can get to Google Now from the search widget or lockscreen.
[Samsung Galaxy Nexus] crobs808:
Did you flash the right Gapps release? The right file is: gapps-jb-20121012-JZO54K-Formula84.zip
[Samsung Galaxy Nexus] fullmetal509:
So far from my experience loving Milestone 1 started off with Francos M6. Had several lag issues such as having music playing and web surfing stutter at the same time.

Made the switch to latest Lean Kernel and I love it so far!

Before had I have noticed short or long pressing on Date or Time doesn't work(FC).

Also the haptic feedback when switching toggles on or off does not respond.

While playing music(PowerAmp) at the lock screen I have a black background, so far that's what I have encountered....

P.S. Sorry for my grammar :o

Via Galaxy Nexus [LTE]
[Samsung Galaxy Nexus] mrbigdrawsz:
Lean Kernel? 4.5 experimental or the 4.2 stable?
[Samsung Galaxy Nexus] MindEracer:
I'm getting amazing battery life on aokp stock kernel. Which is lean kernel 4.5 I believe. Already at 15+ hours with moderate use. With %26 battery left. Best battery life I've ever had!
[Samsung Galaxy Nexus] fullmetal509:
Lean Kernel 4.5 stable

Via Galaxy Nexus [LTE]
[Samsung Galaxy Nexus] flytechguy:
what governor and speeds are you using by chance? Auto bright on? Thanks.
[Samsung Galaxy Nexus] dimsdale:
Not having this problem. But I did a complete wipe formatting sys, data, cache and clean installing.
[Samsung Galaxy Nexus] sawyer815:
Battery Drain

I flashed to Milestone 1 but I have severe battery drain. About 5 hours total run time. I was working fine on JB build 5 with almost 24 hours light usage.

Here's my exact flash sequence:

Nandroid

Factory Data/Cache Wipe

Wipe Dalvik

Format System

Flash AOKP JB M1

Flash Gapps

Flash Trinity Kernel

Flash Exchange Security bypass mod found Here

Flash Gnex Louder mod found Here

Reboot, then setup and install apps via Google. Anyone have any input/suggestions?
[Samsung Galaxy Nexus] NoobDroid90:
I have been seeing some GPS problems. I believe is actually rooted in beautiful widgets. I saw this in build five as well.

If I allow Geo location with the app I get notifications that my location does not exist. Is anybody able to replicate this.
[Samsung Galaxy Nexus] Beamer9408:
I just don't agree with all vzw gnexus will act the same with the same kernel and same settings no 2 devices are ever that identical it never happens in micro hardware. I have experienced it from phone to phone. You believe what you want but I don't think its fair to everyone else to be throwing around such false information. I have asked this question to many people and nobody agreed with what you're trying to say. Not only that hands on experience should be enough.
[Samsung Galaxy Nexus] crobs808:
I already posted a 24hr battery use screenshot using Trinity. 16 is about avg though for most kernels.
[Samsung Galaxy Nexus] hlaalu:
Did group texting ever get merged? I stopped following aokp a few weeks ago. Thx

---------- Post added at 06:38 PM ---------- Previous post was at 06:20 PM ----------

Can you please site your sources/studies that say every phone is different? Aside from your friends and hands on experience. Not trying to be a jerk, I just always see people throw the line "every phone is different" around in the forums, and never produce any hard proof.

Me personally, I think about the production of a galaxy nexus, being built by precision robots, with precision hardware that is tested to be within a certain tolerance. Aside from a manufacturing defect, I don't see any possibility why two of the same phones would be different.

Please point me to some good reading on this, always eager to learn something.
[Samsung Galaxy Nexus] Beamer9408:
Not sure there is any hard evidence or reading materials around flash some different kernels and see what works and doesn't and I guarantee some will and won't and there will be some that swear by that kernel and some that say it blows. I for one can't run any kernel at over 1300 anything above that will freeze my phone causing a battery pull to get it back up. How many of you can run over that? There's one difference kernel developers wouldn't put these extra steps in there if they just didn't work for anybody they more than likely tested on their phones it worked before they released it they probably sent it out to a few people to test that's why you get disclaimers of may be unstable. All I'm trying to get at is just because a kernel isn't working great for you doesn't mean you didn't flash it properly. What's perfect for you may not be for me no matter the install. Also these were not friends I just said if we all had Verizon galaxy nexus and we all flashed the same kernel with the same settings enabled and flashed the same way would all of our phone behave the exact same? I said that in #teamkang and everyone told me no. I'm not a kernel dev or anything but ask around what works for some will not work for you and it has nothing to do with the way it was flashed. As far as I'm concerned I agree that trinity is the best kernel for my phone it never freezes doing the same activities lean kernel did. That's not saying every release of lean kernel would cause them but the ones I tried did. Another example is I cannot run a kernel with GPU over clocked to the 500's I just can't my screen glitches. I'm sure many of you can run 512 fine but I can't never have been able to and no way of flashing that will make me able to my hardware can't handle it.
[Samsung Galaxy Nexus] kioshi:
try fixing permissions in recovery mode. I had gallery FC on me and a little sluggish. I dirty flashed from build 5 aokp. Now all is well.

Exactly. Trinity kernel doesnt play nice on my phone concerning battery life...so far Francos works well and I've tried Lean and Air Kernel <--worst experience for me on that..And i always keep coming back to Francos for my phone.
[Samsung Galaxy Nexus] PatimusXPrime:
Is anybody having HORRIBLE signal drops or is it just me? I can't make phone calls, texts go through sometimes, all signal drops after failed call, all signal drops randomly, sometimes I get 4g and sometimes no 3 or 4g at all..

I have the most updated radios, 4.1.1 and am running Franco latest nightly.

If no one else is I'll try a few things..

*edit* I'm pretty sure it was the latest Franco nightly 298, don't flash it! Lol *edit*
[Samsung Galaxy Nexus] kioshi:
I'm running 298 perfectly for 2 days straight.....:confused:
[Samsung Galaxy Nexus] crobs808:
If you want to believe that two phones of the same model with identical hardware and software will run differently from each other then there's nothing I can do to convince you. I believe it takes a very stubborn mindset based only on anecdotal evidence to believe that, so I won't make anymore post about it.

On another note, my battery heat problem went away after a reboot.
[Samsung Galaxy Nexus] joshuajones:
I've seen big enough differences in screens in identical phones to believe the internals could behave slightly different. But not a whole lot..
[Samsung Galaxy Nexus] thirtynation:
Plea for help:

I'm having a problem with my phone not being able to get past the "initiating swagger" AOKP unicorn/gears boot screen. I am on build 4 (haven't had time lately to flash the newer builds). This has happened randomly a few times since flashing this build, but usually a battery pull and/or reboot into recovery and then reboot from there will fix it. Not today. It will not get past the boot animation no matter what I try. Tried wiping cache partition, no success. Then wiped dalvik, no success. Then wiped system, no success. Not sure if those were the right moves to make or not, but basically I tried everything except for factory reset/data wipe so that I don't lose everything. Then I reflashed build 3 which I still had on my SD card and still, no dice.

What would you guys suggest I do to get a full boot up? I'm willing to sacrifice data and do a factory reset to save the phone, but only as a last resort. Trying to find other options, if possible... I've come too far in tiny tower to revert back to what would be probably a month old TiBu backup!! (lol)
[Samsung Galaxy Nexus] jekern77:
Am I wrong in thinking that wiping system deleted the ROM?
[Samsung Galaxy Nexus] Beamer9408:
No you're right. You need to install the ROM again.
[Samsung Galaxy Nexus] thirtynation:
I have reflashed build 4 again a few times and it still does not get past the boot animation. :(
[Samsung Galaxy Nexus] shadowstewie:
Pull the battery out

Hold down power for 20 seconds

Put battery back in

Boot Recovery

Wipe Data

Wipe Cache

Wipe Dalvik

Format Data

Format System

Format Cache

Flash Build 4

Flash GApps

Reboot System

See if that works.

If it still doesn't work. Re-download Build 4 and GApps again. Use those instead and repeat steps above.
[Samsung Galaxy Nexus] travisjshepherd:
I had this problem, trust me it's scary, but here's what you do flash build 3 right before you go to bed and leave it. It will take FOREVER to boot up just looking at it makes it seem longer than it really is, which is why I suggest doing it at night.
[Samsung Galaxy Nexus] Beamer9408:
If none of the other suggestions work I try a nandroid if that doesn't work boot into recovery adb pull /sdcard or you could try to mount it in recovery and get everything from the sdcard that way then adb reboot bootloader and fastboot the stock images from Google. It really shouldn't take more than a hour to fix this problem I do a lot of risky/ trial things and there has never been a boot loop I haven't been able to get out of. If you need more help I'm glad to help just pm me and we can either hit an irc channel and I will walk you through it or I can teamview into your PC and do it.
[Samsung Galaxy Nexus] RacingManiac:
Is the Gallery syncing issue resolved at all? I am still on build 5 but I've noticed since 3(when I first switched to AOKP) that the gallery won't show any of my picasa album. While it doesn't bother me a ton it still bugs me. Switching to 5 with the new Gapps and I see its still the same. Interestingly I flashed the new camera app from 4.2 and it came with a new gallery app and that one actually syncs with picasa. But I get FCs when I try to do any editing or basically other than trying to view photos...
[Samsung Galaxy Nexus] hlaalu:
Have you tried flashing a different set of gapps? Or the picasa add on from formula84? Here is a quick test to see if you're on the right set.

Open your camera, hit the settings, if there is a huge list of settings/options then it's the wrong gapps package.

There is a trade off, you can either have the stock camera with picasa sync, or the custom camera with custom features but without picasa sync.

The 4.2 camera is buggy when viewing the pictures, it's a known issue.
[Samsung Galaxy Nexus] RacingManiac:
I guess we are trading off camera function to Picasa sync. Too bad the 4.2 camera is not that stable yet, there are some feature I like. For now I can just use the AOKP custom camera and use the G+ to view online album...
[Samsung Galaxy Nexus] johnhimm:
4.2 has been stable for me, look for a later upload.
[Samsung Galaxy Nexus] pntballer505:
Awesome build.

Before I flashed milestone1, I was testing out the

latest gapps with Build 5. And noticed it completely killed my

ability to use gps with google maps. The gps locks perfectly,

but when i try to find my location in gmaps or gnavigation,

it acts as if it cannot find satellites.

I figured flashing milestone1 would fix it. It did not.

So then I flashed an older stable version of gapps. Still did not fix it.

Not sure what the problem is.

Wiped cache and dalvik. Don't think a full data wipe would alter anything

Any ideas?
[Samsung Galaxy Nexus] t1.8matt:
For some reason I had problems with Milestone 1, system was incredibly laggy to the point of freezing. Tried different kernels to no avail. Too bad because it's one of my most favorite ROMs.
[Samsung Galaxy Nexus] flytechguy:
Try Trinity kernel Alpha 67. Getting amazing battery and performance. Been a long time user of Franco and its just not doing it for me like days of ICS AOKP.
[Samsung Galaxy Nexus] mrbigdrawsz:
Fixed it. I had only one action chosen and the other two were not in use. Once I added two more actions for the home button it worked. :banghead:
[Samsung Galaxy Nexus] PoorOldMoot:
I have been using milestone 1 since release and have been thoroughly enjoying it but I may have found a bug. When using 'slide to unlock' the notification pane can still be accessed. This can also cause the screen to unlock if I open a notification. Is this behavior intended?
[Samsung Galaxy Nexus] joshuajones:
Yes, it is intentional. It won't allow it if you have a pin/pattern lock though for security.
[Samsung Galaxy Nexus] PoorOldMoot:
I have noticed that. It seems odd that it is intentional to me, because it increases the likelihood of accidentally unlocking the phone (if even by a small amount). It's cool though because it is a pretty specific gesture required to bring the notification pane down.
[Samsung Galaxy Nexus] gorillabiscuit:
Hi... love the boot ani. I initialize my swagger every morning... Quick question: Gmail is not showing up after flashing gapps. I've wiped cache and reinstalled gapps two times. Each time it optimizes, but no gmail. Any ideas?
[Samsung Galaxy Nexus] PoorOldMoot:
I don't think gmail is included in gapps any longer, it is now in the play store.

https://play.google.com/store/apps/...&utm_medium=organic&utm_term=gmail+play+store
[Samsung Galaxy Nexus] Beamer9408:
Yeah gmail is not included in gapps anymore because it is available in play store.
[Samsung Galaxy Nexus] gorillabiscuit:
Thanks both of you! Some GAPPS, from other ROMs, include Gmail. I assume this is due to some being inverted, needing tweaks, etc. I'm a flash-aholic coming from FactoryROM. What are the pros/cons of AOKP vs. a customized AOSP like Factory? I don't mind the nova launcher, but I'm wondering why it's baked in if the AOSP builds can customize in that same vein...
[Samsung Galaxy Nexus] joshuajones:
Has anyone noticed discrepancies between the ram bar in recent apps and everywhere else? It constantly says I have hardly any RAM free when I have plenty..
[Samsung Galaxy Nexus] dansan382:
any word on baking in better group SMS in the stock messaging app? sadly i know a few clowns with i****'s and GoSMS works fine with i**** messaging. would like that in stock messager though. i know one of the roms has it built in, waiting for it on AOKP
[Samsung Galaxy Nexus] Beamer9408:
I've seen this discussed in the team kang

IRC channel and the guy that made that commit can not figure out why it displays different there he says he is using the same math but it still has not been figured out.

---------- Post added at 08:12 PM ---------- Previous post was at 08:11 PM ----------

That's has been committed as of November 1st. So next build will have group MMS. Here is what has been merged its a little confusing at first but if you look at it you well figure it out.http://gerrit.sudoservers.com/#/q/status:merged,n,z basically at the top left you will see aokp logo right above that you will see open merged and abandon. Abandoned means just that when you click that link the projects that show up underneath that tab are no longer being worked on if you click on one of those projects and scroll down you will see comments and sometimes they will give clues as to why it was abandoned either code wasn't right or they didn't like something about it. If you click the merged tab all of those projects have been merged to github. Meaning if you do a repo sync and run the build that's what you get exactly what has been merged. This is not only a way to have wider spread testing but also to ensure broken commits are not merged. If you click the open link those are projects currently being worked on. If you click a project link the commit message is to the right and gives more detail as to what that commit does. If you scroll down and read comments you will see the progress being made. This is where you see ROMs like the one i build coming from we are syncing to the latest merged source and looking through the open projects to see what we want to try. Hints the widespread testing people cherrypick those open commits and that's how you are able to test them.
[Samsung Galaxy Nexus] II12yanII:
im having an issue when my phone is asleep. the screen wont come back on at all and the only way to get it to come back on is to pull that battery and reboot. its getting really annoying. is there a fox for this or something?
[Samsung Galaxy Nexus] Beamer9408:
Either try switching kernels or bump your minimum up some. Also you may have an option to have your maximum screen off CPU state bump it up a little.