yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] artjef:
I do not believe you bear any fault other than you are human. I and many others appreciate your time and hard work. You spend time building the ROMs we love and then you stay around to help. I personally think that is outstanding. Please don't let one user get to you. Look back at all the users who appreciate you and your work. 897 pages before we had a ____ that pretty outstanding and that says a lot about you.

thanks mmuzzy
[Samsung Galaxy Nexus] georgeascott:
I'm a lurker.. :) I happened to update the day before a new build ha. Just my luck. Running with it for now and it is nice and smooth... As expected. I'll probably wait til the day before an update again too.

Btw, never did figure out what went wrong with my usb connection issue but I have found the USB flex replacement for $7 on the 'zon. It must be the problem because I notice the other evening that it would stop charging if I held the cable a certain way so I must have damaged it at some point.

Random question for the themers.. is there a tool/app that allows you to tap an area of any app and see the path to the image? (Was it Firefox that had the 'show elements' feature for debugging?) Obviously, I can get knee deep in an explorer looking for images to mod, I was just wondering if there's an easier way. Thanks!
[Samsung Galaxy Nexus] billykxda:
Tiny:

Thanks for the heads-up on FasterGPS. Every time I try to use GPS, it takes minutes to get a lock - sometimes up to 5 minutes. Each time, this is trying to access GPS from my car. It can make using Navigator a non-starter when I need quick directions. Frustrating!

I just installed FasterGPS and Iook forward to <hopefully> faster lock times next time I need it.

I am still on Mikes' FV from a couple of releases ago - but slow lock speeds have been an issue for me forever - regardless of ROM.

Thanks again.

-bk

---------- Post added at 09:58 AM ---------- Previous post was at 09:55 AM ----------

Thanks!

I'll give this a try if FasterGPS out-of-the-box doesn't get me a fast GPS lock.

Just catching-up on the world of Muzzy...
[Samsung Galaxy Nexus] mpressive:
Mmuzzy,

Agreed!! Your ROM and the general spirit of support found in this thread has been a God send for me and I'm sure many others!!!!!
[Samsung Galaxy Nexus] mnbrightblade:
Is dirty flash from vanilla to french not recommended?
[Samsung Galaxy Nexus] Frixtion:
I'm not sure what to tell you about vanilla to French vanilla but,

Be aware in the latest fv build mmuzzy incorporated superuser into the system and you must unistall/ delete the original before updating/ flashing to 4/13. Rw1 a couple pages back instructed process. I did a clean flash and you dont have those worries.

I'm replying an driving
[Samsung Galaxy Nexus] jpinsl:
@mmuzzy Just saying thanks for giving the world such a rock-solid ROM. My GNex has never been happier. Excellent Work!
[Samsung Galaxy Nexus] Wdswds:
Lurker here to confirm. I try not to post because I am afraid I'll clog up the thread, but I love your work, mmuzzy. About to make a donation to you right now.
[Samsung Galaxy Nexus] muffnman:
Did the notification drawer functionality change recently? Sometimes I'm getting the toggles, other times I'm getting the regular shade.

Anyone else experiencing this? Is this tweakable somewhere within the ROM?
[Samsung Galaxy Nexus] RW-1:
Ok, so I received a call today, and was on phone, took my Gnex away from my face, and what I had was the regular phone screen, no pic, as the caller was not in my contact list, red end button, however floating above that was the ringer phone symbol and I could move it to the green phone, or the red phone, but nothing was occurring, I couldn't end the call either, so I allowed my caller to do so after finished.

I've tried to replicate the issue, but so far have not done so, but I'm just being diligent in reporting it.

(Most of the time unless I need to use the keypad, etc. the phone is to my face for most of my calls :) )

Latest ROM, included kernel, blue zenyth softkeys added using zipthemer, nothing more added or tweaked.

Still rocking Mmuzzy ...

---------- Post added at 03:45 PM ---------- Previous post was at 03:43 PM ----------

If you have no notifications then swiping down should bring quick settings toggles. I haven't seen any malfunctions with this on the new release so far...

---------- Post added at 03:48 PM ---------- Previous post was at 03:45 PM ----------

Vanilla is just that, no added mods to the Android 4.2.2, it is just AOSP itself, you still need GAPPS.

FV is the same, though several tweaks and Quick Settings have been incorporated.

I believe you could do a dirty flash to FV, but uninstall superuser first, and you would want to check you hadn't added any of your own 3rd party mods, which may not play well with FV, as to what those are, it's open to interpretation. (I'd remove any themes that might exist, anything that may have played with framework ...)
[Samsung Galaxy Nexus] mnbrightblade:
I've added nova launcher, tiny kernel and Trickster mod.
[Samsung Galaxy Nexus] demill66:
Just wondering if anyone else has had any issues with the bluetooth voice dialing feature ever since the newest update of google search. It seems to cause some conflict with bluetooth share. Would this have anything to do with the ROM or would it simply be a conflict between the programs themselves.

Also, MMuzzy, is it possible to get a pre 4.2.2 rom from you to make a comparison.

Thanks all.
[Samsung Galaxy Nexus] tshelby73:
Yes. It's Google search issue. Remove update in apps will go back to normal. Does this even on stock 4.2.2.
[Samsung Galaxy Nexus] r_dub:
Just flashed this ROM and a few mods, I have my phone plugged in but while it shows it charging it the battery percentage keeps dropping. The charger worked just fine before flashing the ROM.
[Samsung Galaxy Nexus] mmuzzy:
It's just the stock AOSP source and stock kernel. Not much there to blame. I have after market cords that will do that to me also though. The only thing I can recommend is try another cord, USB port, or AC charger if you have one.
[Samsung Galaxy Nexus] wickets:
thanks to the ibenjakinov question and the mmuzzy reply......answered all one needs to know :)

btw, you and mwalt rock
[Samsung Galaxy Nexus] mmuzzy:
Glad to hear you found you answers.

Agree about mwalt, and thank you. :)
[Samsung Galaxy Nexus] techspecs:
Is there an AOSP changelog to JRO03R or is it just general sprinkles of magic throughout? We all know I'm going to flash anyway but I'd feel better knowing that I'm 'upgrading' something. :cool:
[Samsung Galaxy Nexus] Ianxcom:
JBQ said in twitter its only minor bug fixes.

BTW running great. Thanks for this!
[Samsung Galaxy Nexus] GabrielNM23:
How's battery life on this new build? And if your using a custom kernel please post what your using with this, thanks
[Samsung Galaxy Nexus] deadpixell:
Seems like a silly question but I shouldn't have to reflash the new radio files once I flashed this rom right? I did wipe data/cache but I don't think that would change the radios?
[Samsung Galaxy Nexus] buddyfriendo:
You won't, it's a one time thing.
[Samsung Galaxy Nexus] deadpixell:
Cool thank you! Just gotta find a replacement kernel depending on how this one does.

Thanks again MMuzzy!
[Samsung Galaxy Nexus] mmuzzy:
I confess. I don't normally leave my phone off a charger if there's one around so overnight is my best gauge of sleep time. After the only night of that it seemed on par with the last kernel and build though. And as Ianxcom said, it looks like Jean-Baptiste's thoughts are the build diffs are pretty much just little magic sprinkles than major changes.

In any case, sometimes it's just nice to know you're on a newer build. ;)
[Samsung Galaxy Nexus] Pierceye:
Just rooted and updated to this from stock ICS and battery life seems to be pretty much identical, which is a good thing. Beats my Evo with a 2000mah battery by a decent margin. Just running the ROM as provided, no custom kernel, no mods.
[Samsung Galaxy Nexus] r_dub:
Anyone else's Verizons apps not working? I get "services temporarily unavailable" all the time.
[Samsung Galaxy Nexus] marcjc:
NFL app.... I have no issue with Verizon login.
[Samsung Galaxy Nexus] GabrielNM23:
Downloading/Flashing this right now. Going to use it as my daily for the weekend, I'll try this with francos/trinity/lean/air kernels and share my findings. :laugh:
[Samsung Galaxy Nexus] chrisomnia1:
When installing the rom, power menu, battery, and dsp causes systemui error. Also when going into the app drawer I lose the nav buttons.

Will try just the rom this time. May be battery mod. Anyone else getting this?
[Samsung Galaxy Nexus] GabrielNM23:
Was it only the battery mod you used or did you use another mod?
[Samsung Galaxy Nexus] chrisomnia1:
I used all 4 mods in the OP first and got the error w/no nav buttons. I installed the rom with only the power menu and no error occured.

I also don't have Verizon in the pulldown, which isn't a big deal for me. Just an FYI.
[Samsung Galaxy Nexus] horten229:
Just one difference I noticed between JRO03O and JRO03R - the [emergency] Cell Broadcast Service under Settings/Wireless & Networks is now gone.

It's kind of a nice thing to have. It has poped up three times since I switched to JRO03O (Tornado and flood warnings).

Maybe this was a JRO03O Verizon thing?
[Samsung Galaxy Nexus] mmuzzy:
It was probably the DSP Manager that caused it because I didn't touch that MOD after the update. I flashed, and I'm still using, the Enhanced Power Menu and 1% mod now. I noticed the Emergency Broatcast Service settings were gone too. I haven't looked into it at all and I won't be able to until later. We're going to visit family in Rhode Island today. I'll take a look at it when we get back though.

I will still be around on the forum today, however. Have a good day guys.
[Samsung Galaxy Nexus] RW-1:
I'd pull the Trickster mod, but since I don't know what it does/modifies ... If you really only did those three, nova and the kernel should be ok, lots of people swear by (not at) Tiny :) Besides flashing the ROM will replace the kernel anyways, then you can go back ...
[Samsung Galaxy Nexus] 06stang:
Was having issues with other ROMs and battery life. Came back to Mmuzzy and haven't looked back. I missed the theme changer for a while but got over it.

Great ROM and great dev. Thanks Mmuzzy.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] demill66:
When I removed the update, I get a force close of the search, even when I press the mic icon on the search bar.
[Samsung Galaxy Nexus] artjef:
I run all three with no issues. I am not sure I would dirty flash though.
[Samsung Galaxy Nexus] Frixtion:
I don't want to speak for mmuzy but I think he would say uninstall it and install from the play store. Couldn't hurt at this point and seems how no one else has said anything i figured I would.
[Samsung Galaxy Nexus] marc.ientilucci:
Not sure what did it but 4/13 FV battery life is MINT!! And no speed has been sacrificed :D
[Samsung Galaxy Nexus] KnappyRoot:
The other day I was sending/receiving a bunch of group MMS messages. At one point my phone was unable to receive any messages or phone calls. It was like a log jam where nothing was getting thru. Once I restarted my phone all my messages came through one after the other. This doesn't seem to happen if I am using Handcent on 4.1.2 but I would rather come back to 4.2.2 cause I'm missing me some Muzzy. Has anyone else have this happened to them?

In jest of recent posts, maybe it's the ROM, it can't be a problem with my hardware!

Muzzy, I follow this thread every day. I am very impressed with how you take time to reply to just about every question or issue that someone has (if someone doesn't beat you to the answer, which is another testament to what a great little community you started here). Please do not stop what you're doing and how you're doing it.
[Samsung Galaxy Nexus] Frixtion:
@knappyroot I just went to play store and checked reviews of galaxy nexus users and your not the only one having issues w/handcent. Just thought I'd put that out there for you I didn't read them all but first 10
[Samsung Galaxy Nexus] veloslave:
After figuring out that dirty flashing was killing my battery performance...I will never do it again.

FWIW

BTW... you know we love you MMuzz, don't try to deny it. ;)
[Samsung Galaxy Nexus] mnbrightblade:
So basically bite the bullet, use titanium and do a clean flash.
[Samsung Galaxy Nexus] artjef:
Absolutely
[Samsung Galaxy Nexus] darklordofthesith:
Any reason why the 4/13 update to the 2100 mAh framework with centered clock won't apply to Mmuzzys 4/13 fv rom?
[Samsung Galaxy Nexus] Keyboards:
What kernels are you guys using that are showing the best results?
[Samsung Galaxy Nexus] tshelby73:
You try clear cache and data for the app. You may have a different issue than mine. I am on stock right now but on 4.1.2 and 4.2.2 had the issues you have explained. Haven't tried new search update on mmuzzy yet. Sorry if not much help.
[Samsung Galaxy Nexus] Kyle C:
I've been using Tinys kernel. No lags, no reboots, great battery life.
[Samsung Galaxy Nexus] darklordofthesith:
Using lean right now. Latest build. Great battery life and speeeed.
[Samsung Galaxy Nexus] mnbrightblade:
+1 this.
[Samsung Galaxy Nexus] dustrho:
Which version are you using? There were supposedly issues with versions 3.3 or greater, so I don't want to try one that's going to cause issues for me. I know 3.1 worked fine for me when I was running it some time ago.
[Samsung Galaxy Nexus] vishious89:
Theme Changer

MMuzzy, you know of any way to get Theme Changer on the rom? I went over to CM 10.1 for a few days, loved the theme changer, hated the subpar performance and speed when compared to your rom. Gladly returned to your rom and completely besotted with the much better performance. I do kind of miss the Theme Changer though, and was curious if you knew of any way to add it?
[Samsung Galaxy Nexus] MR H3LLMAN:
It would have to be added into the actual source itself as it requires framework and system modifications to work correctly.
[Samsung Galaxy Nexus] tiny4579:
Aside from the warning about WEP there is nothing wrong.
[Samsung Galaxy Nexus] Lyxdeslic:
Quick question: does this Rom contain the quick reply/read button in notifications for SMS?

Edit: never mind, I see it all now. I can custom flash the option. My apologies.
[Samsung Galaxy Nexus] ba_hamilton:
I was on cm10.1 for a few days also and returned back home. The Midnight Gapps Project took care of my need for themes. As the name implies it is dark inverted gapps plus a bunch of other apps that have been themed . There is now an aroma installer for it. It's very well done and works great with mmuzzys rom.
[Samsung Galaxy Nexus] Lyxdeslic:
Trying to download the Quick Reply SMS zip but it keeps saying webpage not found. Does anyone have a mirror available?
[Samsung Galaxy Nexus] demill66:
Did everything from superwipe to following MMuzzy's instructions on clean wipe. I'm trying to find a copy of his last two iterations of his ROM, so I can reinstall and see if either of those older ones work.
[Samsung Galaxy Nexus] dustrho:
Just flashed tiny kernel 3.4.1. What settings are you running different than how it comes? I want great battery life without the lag. Thanks.
[Samsung Galaxy Nexus] tiny4579:
To truly get rid of the lag flash 4.1.2. There's no true lag fix from a kernel level. As there are so many places that list kernel settings (such as my thread), try those first.
[Samsung Galaxy Nexus] jcmm11:
Older versions are available on goo
[Samsung Galaxy Nexus] dustrho:
What thread are you referring to, and what was the last 4.1.2 mmuzzy ROM?
[Samsung Galaxy Nexus] mmuzzy:
There is a 4.1.2 ROM from October 26 in ROM Manager. That's probably about the last one before the first 4.2 ROM anyway.

Edit: This is Tiny's kernel thread which is what I think he was referring to http://xdaforums.com/showthread.php?t=1994248
[Samsung Galaxy Nexus] tiny4579:
Yep my kernel thread. I should have been clearer.
[Samsung Galaxy Nexus] Frixtion:
Here you go(http://db.tt/O7jYjRsm)

, when you get the web page not available just hit back on your phone and it will bring you to the box page your looking for.

Frixed the link ;) (https://m.box.com/view_shared/u0m16u652999807dy16k)
[Samsung Galaxy Nexus] techspecs:
I'm inexplicably intrigued by this. What do I lose going back to 4.1.2? Google Now?
[Samsung Galaxy Nexus] tiny4579:
New keyboard, quick settings, lockscreen widgets, new clock app. Not much. Google Now started with 4.1.1 so you'll have it still. I'm keeping 4.2.2 because of the improvements to CM10.1 over CM10 and I have this weird thing of wanting to be on the latest and greatest.
[Samsung Galaxy Nexus] techspecs:
O hai! Have we seen this? http://www.androidpolice.com/2013/0...e-4-2-2_r1-2-here-is-the-developer-changelog/
[Samsung Galaxy Nexus] mmuzzy:
I'm sync'ing up now. I'll have new builds tomorrow but it seems to be Nexus 4 stuff. Still... shiny new build number. I know how it is.
[Samsung Galaxy Nexus] slyd0997:
Ahhhhhh. No love for grouper?
[Samsung Galaxy Nexus] mmuzzy:
Actually yes. The 7 is one of the only Nexus devices I own so it's a no brainer. ;)
[Samsung Galaxy Nexus] slyd0997:
(smile)
[Samsung Galaxy Nexus] billykxda:
Haven't flashed in a while. Interested in this latest that Mike is building - just b/c I think it's about time to catch up with the rest of you.

To save me the research time reading the back-posts, do Mike's newer ROM's require that you uninstall SuperUser prior to flashing? Otherwise, everything is the same 'ole?
[Samsung Galaxy Nexus] Frixtion:
If your doing a dirty flash, then yes yes you want to uninstall superuser before doing so. RW-1 was thinking and suggested caution with any mods you may have installed that might cause problems. Anyone else want to chime in

Clean flash no worries
[Samsung Galaxy Nexus] billykxda:
I only do clean-flashes - so I am good.

Thanks for the assistance.

-bk
[Samsung Galaxy Nexus] mmuzzy:
Ok this is weird... I had a hard time syncing and noticed an android-4.2.2_r1.2b and now when I start to build I get this:

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=4.2.2

TARGET_PRODUCT=full_grouper

TARGET_BUILD_VARIANT=userdebug

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a-neon

HOST_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-3.5.0-17-generic-x86_64-with-Ubuntu-12.10-quantal

HOST_BUILD_TYPE=release

BUILD_ID=JER09

OUT_DIR=out
[Samsung Galaxy Nexus] veloslave:
Full Grouper?

Was that your input or?

BTW... anybody figure out what the changes are?
[Samsung Galaxy Nexus] mmuzzy:
I was building a ROM for the N7. I'll do Toro after that. I'm just surprised that I haven't seen anyone catch that there is a newer build out there. I'm sure they will sooner than later.
[Samsung Galaxy Nexus] tiny4579:
That build id is wrong. It should be jdq39e. Check that the build project had no merge errors.
[Samsung Galaxy Nexus] mmuzzy:
Tiny, check out the manifest. There is an android-4.2.2_r1.2b. That's what I synced to and got this build id. I suppose you're right though. Hmm.
[Samsung Galaxy Nexus] Broadleynine:
Just wanted to tell you both good luck, we're all counting on you. ;)

Sorry, I can't pass up a chance to use an Airplane! quote.

Seriously though, Muzzy, your ROM just plain rocks! Never once had a problem I couldn't fix myself because of all the info on this thread. I've been rocking your ROM since December and haven't looked back and don't plan to.

We all appreciate the hard work and time put in to make this, IMO, the best ASOP ROM available.

Cheers!
[Samsung Galaxy Nexus] mmuzzy:
Thanks. I trust Tiny's info. If he thinks it's a fubared build id I'm going to stay clear of it. I'll have a build soon although it won't be much more than a new build number.
[Samsung Galaxy Nexus] jcmm11:
4/17 carbon nightly is using it already. Specified as mako only.

"Update to Android 4.2.2_r1.2. Build id is JDQ39E. This only applies to mako."
[Samsung Galaxy Nexus] mmuzzy:
Thanks. I've been aware of this already which is why I'm not losing any sleep getting builds out. Very minor update of a minor update.
[Samsung Galaxy Nexus] Broadleynine:
I've skipped the last couple releases mainly out if laziness but also because I haven't had a problem with the one from early March. However, I like to clean flash every few months and a shiny new build number is a great reason to flash. At least that's what I'm telling myself so I'll stop procrastinating.
[Samsung Galaxy Nexus] tiny4579:
I don't have a full AOSP build to verify everything (CM repo). How do you sync your source? If you did jb_mr1.1-release you should still have JDQ39E. I'm skeptical about this r1.2b. I've never seen that before and the build numbering seems different. I f you were curious mmuzzy, then you could probably sync by the tag instead of the branch.
[Samsung Galaxy Nexus] thered1:
I've been using this Rom forever and it's great. I rooted a long time ago and forgot the process. I've been full wiping and flashing with Clockworkmod. My phone's acting up a little.

Sorry if this sounds noobish, but I've read everywhere and can't find anything. What is the best way to do a full wipe of everything (including the SD). Completely back to stock, wipe all user data (even when I do a full wipe, my files are still there). And then get the French vanilla back?

Thanks!
[Samsung Galaxy Nexus] tiny4579:
The factory image process using Google's factory images will actually format the /data partition which wipes the sdcard as well as flash the radios from that release as well. Also the stock build gets flashed and stock recovery reflashed. There is one for 4.2.2 as well. The only thing not stock would be the bootloader stays unlocked.
[Samsung Galaxy Nexus] mmuzzy:
ROM Update

April 19, 2013

- Merged in android-4.2.2_r1.2b (JER09)

- Updated Superuser

- De-integrated Superuser

I know it's a different build number than 4.2.2_r1.2. Yay? ;)

EDIT: I forgot, I also separated Superuser again. It was too confusing and the update route just sucks.
[Samsung Galaxy Nexus] tiny4579:
This JER09 is still sketchy. I don't even see it in platform/build as a tag:

https://android.googlesource.com/platform/build/+refs

Also, this is very weird from the default.xml. This never should have been pushed as a tag. I doubt you'll notice anything different but it's good to be on a released build:

<project path="build" name="platform/build" groups="pdk" revision="f03d227b09d0bc3e1b2342811d5106aa7749fad0" >
<copyfile src="core/root.mk" dest="Makefile" />
</project>

I see it in manifest though and the only difference in the manifest from 1.2 and 1.2b is this

- <project path="build" name="platform/build" groups="pdk" >
+ <project path="build" name="platform/build" groups="pdk" revision="f03d227b09d0bc3e1b2342811d5106aa7749fad0" >

I still have a better feeling of you using 1.2 over 1.2b especially since jb-mr1.1-release is following JDQ39E.

Mmuzzy, what revision does your manifest point to?
[Samsung Galaxy Nexus] Broadleynine:
Sweet! I'll flash it after work today and report back.

Muzzy, can't thank you enough for this awesome ROM.
[Samsung Galaxy Nexus] mmuzzy:
I agree. I don't think there is anything different either. Heck, there isn't really anything different for Toro anyway. This is where I saw it FWIW: https://android.googlesource.com/platform/manifest/+refs

Thanks. Hopefully it goes smoothly for you.
[Samsung Galaxy Nexus] tiny4579:
I was updating my post while you were responding. For sanity's sake you probably should follow based on the tags and if there's a funny branch that isn't tagged then don't use it. Ideally you should be able to use jb-mr1.1-release, if not, find the latest tag in manifest.
[Samsung Galaxy Nexus] mmuzzy:
Fair enough. I'll do that going forward. Thanks, Tiny.
[Samsung Galaxy Nexus] techspecs:
I'm running the latest build with tiny's latest kernel. Running perfectly so far.