yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] mmuzzy:
That it is. We'll be looking forward to seeing what you come up with. :)
[Samsung Galaxy Nexus] j0hnnyth3f0x:
hopefully i don't disappoint, i'm just looking at navbar stuff now, and kmakunamatataguy has been really helpful! standup guy, that one....might take me a while though, i'm just learning to crawl right now-more like just discovering i have hands! lol
[Samsung Galaxy Nexus] madAdam6LOVE:
Is this a stable, wife-friendly ROM?

Giving my old Gnex to the wife. I was a crackflasher (don't even remember what ROM is installed at the moment).

Was looking around for the best ROM for a one-time install (no updating).

Would this be a good choice, or can anyone recommend a better one?
[Samsung Galaxy Nexus] j0hnnyth3f0x:
This is definitely a stable rom! But since it is based off aosp and not the actual vzw update, there will be steady updates to it. If you'd rather not maintain the device for your wife might I suggest flashing the Google factory 4.1.1 image?
[Samsung Galaxy Nexus] mmuzzy:
I think it would be fine. There isn't a lot of bleeding edge to the ROM. The Vanilla ROM is most like an OTA, the French Vanilla ROM has things like modified toggles, expanded desktop (allowing the bars to hide for full screen), and and extended power menu.

You want to grab files in the first post to do the following in Recovery:

1. Wipe the phone using either the Superwipe script or doing the normal clearing cache, formatting system, dalvik cache, etc.

2. Flash the ROM you chose

3. Flash GAPPs

4. Flash the Pano fix for the panoramic mode on the camera.

That should pretty much do it.

This is good advice too. It's probably a better idea.
[Samsung Galaxy Nexus] j0hnnyth3f0x:
I hope I didn't offend you, muzzy! Reading my post, it kind of looks like I'm steering people away from your rom and I assure you, it's only because madadam doesn't want to update it! I would suggest this rom to anyone hands down big guy :)
[Samsung Galaxy Nexus] mmuzzy:
No way! I think that having the phone go back to stock for a low/no maintenance installation makes the most sense. The ROM isn't always the right choice. Heck, it probably isn't more often than not.
[Samsung Galaxy Nexus] cowsquad:
Is anyone experiencing force closes using Google voice search? I clean installed latest vanilla ROM and latest gapps from the OP.
[Samsung Galaxy Nexus] raypino:
I've changed my recovery to the latest twrp very nice recovery and I redownloaded all the files and still give me status 7. dunno what else to do to try to install this rom.
[Samsung Galaxy Nexus] ChrisDoctorD:
I am experiencing the same Google Voice Search problem. I just clean installed the latest Rom/Gapps last night.
[Samsung Galaxy Nexus] jcmm11:
At this point all I can suggest is backing up your sdcard and doing a full format. (Format both system and data). After you format adb push the rom to the phone then install via recovery.

Did you manually mess with the file structure at all? There's something on your device that's not right. The rom installs fine and I know that TWRP works just fine as well.
[Samsung Galaxy Nexus] b.huss2:
Maybe this will help (straight from the op):
[Samsung Galaxy Nexus] ShanMan14:
After keeping up with this thread since I installed it and reading the last several pages, I think I'll be sticking with the 12/18 version I installed, which I guess would now be called "French Vanilla." It works great for me. :cool:
[Samsung Galaxy Nexus] realgadawg:
Could not flash.

I did ota download of this ROM. After flashing it, I got an error message. Now I can't flash any new downloads, nor can I flash a backup. What did I do wrong? Thanks.
[Samsung Galaxy Nexus] BOY_:
I just flashed the latest Tiny Kernel and I'm having issues too with TWRP. I guess I'll mount/unmount system and see if that fixes it.
[Samsung Galaxy Nexus] realgadawg:
Could not flash.

I did an ota download of this ROM. After flashing it, I got an error message. Now I can't flash any new downloads, nor can I flash a backup. What did I do wrong? Thanks.
[Samsung Galaxy Nexus] raypino:
all I did was root then unlock bootloader and installed a rom using at the time cwm touch recovery. installed the leaked ota from Verizon and now joelz aosp and now trying this.
[Samsung Galaxy Nexus] :
Is it any coincidence that people are suddenly having trouble flashing ROMs right at the start of the new year? Maybe that y2k bug from 13 years ago finally came around...

For everyone trying to flash the ROM unsuccessfully with the status 7 error, does it happen on ANY ROM or just MMuzzy's? I'm currently running the 12/30 build on the latest (2.3.3.0) TWRP recovery - I can't think of a good reason (other than perhaps a bad download or a corrupted recovery) that would prevent others from being able to flash.
[Samsung Galaxy Nexus] Bleezyd:
So Ive been on Muzzy's ROM for hte last couple months and never had any real issues until this 12/30 rom. Now my phone doesnt just reboot, it just turns off for no reason. I'll try to unlock my phone to use it and I find the phone is just off. After having this happen 3 times in a day, Im going to reflash back to the 12/18 rom which worked fine for me.

Anyone else having this issue?
[Samsung Galaxy Nexus] realgadawg:
For me, any ROM that try download and flash. I had liquidsmooth on my sdcard before hand, I could flash that.
[Samsung Galaxy Nexus] mmuzzy:
Crashes, reboots, Error 7, etc

I feel like this happened the last time I shaved away GAPPs too. The funny thing is that part of the reason I do it is because I felt like I was taking on the responsibility of those apps, which really have nothing to do with the ROM, and the issues when they go wrong. It's still happening even though I've done it.

I just wiped my phone, went into recovery, superwiped, flashed the ROM, flashed GAPPs. I didn't have the status 7 error, these are the same files posted on Goo.im. I still think it has to do with the filesystem and what partitions are mounted at the time. I still think it's a recovery issue more than a ROM issue.

The Google voice search crashing? Yup, it did for me too. That file comes from GAPPs. When you go into Google Now for the first time one of the first things it tells you is there is a new version available and asks if you want to upgrade. If you upgrade it, no more FC. Make sure you update your stuff.

Random reboots? No idea on that one... system data being recovered? Some rogue app or widget? Alternative settings on an alternative kernel? I'm only guessing because it isn't happening to me so I can't fix what isn't broken here.

Am I cranky? Only because I'm still sick. I came home early so I'm going to get some rest. It is, however, frustrating and increasingly unrealistic to me to find a balance that makes sense. No matter what I do everyone won't be happy. All I ask is that you don't ask me to reinvent the wheel... and not try to fix what's already been fixed.
[Samsung Galaxy Nexus] Bleezyd:
Thanks Muzzy. I know we all appreciate your work and your quick responses to issues, etc.

I did not do a full system wipe when going from 12/18 to 12/30 rom, so maybe that is my issue. I just flashed it over as usual and then my phone just started turning off for no reason. I dont change anything on your roms, everything is as you have it. same kernel, settings, etc. So ill try again later with a full wipe and hopefully that will help.

thank you
[Samsung Galaxy Nexus] mmuzzy:
I hope so. I don't take it lightly when you have issues. That's why I started from scratch again a while ago to take each point and try to replicate it or identify what might be happening. You might have something there. I think a clean install and restoring your apps, even with their data from TB, etc will give you good results. That's what has been working for me since I first hit the forum anyway.

Fingers crossed.
[Samsung Galaxy Nexus] RyanTX:
I have installed the latest 12/30 and the 1212 gapps. T9 dialing is still acting up every now and then like I had mentioned in a previous post. It's okay though, everything else is rock solid!

Thanks again mmuzzy for all your work and support. Not too many devs are as responsive as you are.
[Samsung Galaxy Nexus] mmuzzy:
Appreciate it. We'll we'll keep our eyes open on the T9 dialing. I still think it's better than it was in any event.
[Samsung Galaxy Nexus] notstevek:
I'm having no problems at all here. Tiny kernel and newest build...
[Samsung Galaxy Nexus] ChrisDoctorD:
I just updated my Google Search and it works just like new. Sorry I didn't think to do that. Thanks MMuzzy!
[Samsung Galaxy Nexus] techspecs:
Not picking on you but the general rule is that if you dirty flash (meaning not wiping) and have an issue, you need to first do a full wipe and reinstall before coming here to report an issue.

People's extreme patience and helpfulness in this thread should not be misunderstood to be a desire to help people who are not taking all reasonable steps to help themselves first. That means search the thread, check your md5s, do a full wipe if necessary. The spirit of this community is collaboration and problem solving. Problem solving can only happen if people are pulling their end of the deal.
[Samsung Galaxy Nexus] thechainrule:
Which radios are to be used with this rom? Ive had installed for about 2 weeks now, super smooth stuff. Keep it up guys!
[Samsung Galaxy Nexus] Wartickler:
You are too humble, sir.

(O;

Sent from my Galaxy Nexus Toro that is way better than yours [see also: "Mmuzzy"]
[Samsung Galaxy Nexus] johnhimm:
Is the Vanilla ROM's kernel the "Google kernel" unaltered or has it been tweaked?
[Samsung Galaxy Nexus] techspecs:
AFAIK it's stock in keeping with the vanilla AOSP goal. I think all adjustments to straight AOSP are disclosed in the OP.
[Samsung Galaxy Nexus] Jays2Kings:
Since the same new gapps, I keep getting FC's in Google Now when I try to search with the camera. The G Now from a couple gapps back works fine, but just thought I should share.

Edit: sorry wrong thread
[Samsung Galaxy Nexus] :
Working fine here. As stated 1 page back make sure that your Google Now is up-to-date via the Play Store. Double check permissions, etc. Your post doesn't give anyone a lot to go on.
[Samsung Galaxy Nexus] Jays2Kings:
My bad, posted in the wrong thread.
[Samsung Galaxy Nexus] jpayne97:
bluetooth problems

On the Dec 22 build but this has happened on all the builds up to that since I've been running mmuzzy. Whenever I connect something on Bluetooth and then disconnect that device I can't reconnect unless I restart. Similarly I can't disable Bluetooth. It sits at "turning Bluetooth off". Only restarting fixes this. All clean installs. No settings restored. On tiny kernel. 2.4.0. Any ideas?
[Samsung Galaxy Nexus] pennjersey83:
I know I'm never supposed to ask for release times on xda. I love this theme and I'm still on mmuzzys 12/22 because I won't update if I'm going to lose this blackout theme. I don't mind staying on 12/22 forever just wondering if you will update your blackout theme or if I should stop checking on updates. Thanks adb
[Samsung Galaxy Nexus] techspecs:
You answered your question with the first eight words. OP specifically asked people recently not to ask the modders for ETAs. I recommend you just keep patiently waiting.
[Samsung Galaxy Nexus] jaenizzo:
What is the center lock screen I just flashed it but don't see a difference. Do someone have a picture or something to post what it is thanks
[Samsung Galaxy Nexus] pennjersey83:
Wasn't asking you but thanks for your input and point taken

. I wasn't asking when I was asking if. I think asking a modder about future support is a little different than asking for ETAs.

And adbFreedom can just ignore my post if I asked a dumb question.
[Samsung Galaxy Nexus] ba_hamilton:
I've been playing around with the Expanded Desktop option and found an app called GMD Gesture Control on XDA. Basically it lets you substitute the soft keys with screen gestures or swypes. It does some more stuff but I'll let you read up on it if you are interested. The one drawback to the free version of the app is that you can't show/hide the status bar.

It is kinda cool having your phone in full screen mode all the time but it does take some getting use to. It's fun to play around with.
[Samsung Galaxy Nexus] serika:
One of the features listed says native tethering. Does that mean I can use the built in tethering function and it won't charge me extra? Also, is there any built in features to change the battery icon or do you have to flash that separately? Lastly, can you add buttons to the navbar below?

Thanks!
[Samsung Galaxy Nexus] :
Not to speak for adbFreedom, but here is his response to this question over on rootzwiki:

adbFreedom on 12/30 blackout theme

In theory, yes, you should be able to use the built-in tether without being charged extra. In case you're worried, this should be a little re-assurance:

Verizon ordered to pay $1.25 for blocking tethering apps

Additionally, no, this ROM is meant to be AOSP, as stated directly in the OP. There are no features built-in to change the battery icon or the navbar buttons, but if you re-read the OP you'll see that both adbFreedom and myself have both of these mods available in different packages. Here's a link to my 12/30 mod repo, including different navbuttons as well as battery icons:

Kmagameguy Mod Repo for 12/30 build

--edit---

This is what the center lockscreen does - by default the lockscreen is right-aligned. The mod centers the clock (note that the second screenshot is the lockscreen mod with a personal theme of my own also applied - the default lockscreen centering mod will not change the lock symbol to the arrow).
[Samsung Galaxy Nexus] serika:
Thank you so much for that info! reassuring on the data and very helpful with those links. :good:
[Samsung Galaxy Nexus] gorillabiscuit:
Effing A... love you muzzy... In a completely heterosexual way.
[Samsung Galaxy Nexus] adbFreedom:
It's not a dumb question at all. I did however answer on rootz and thanks kma for linking that. I will see about updating the theme when I have time, but I just know what's involved and I don't want anyone to expect it because there is a chance I won't find the time. I would rather deliver when unexpected than have you waiting and let you down.
[Samsung Galaxy Nexus] pennjersey83:
Thanks. I appreciate you letting me use your theme and mmuzzy letting me use his ROM. I watched a YouTube video about making ROMS and themes and the amount of work that goes into all this is crazy. I have trouble passing a Java class at college. I still haven't even used Linux on desktop let alone created my own theme. I realize you guys are sharing your own creations with all of us and it's time consuming. The dark black and cyan blue notification pull-down in your theme should be standard in Android.
[Samsung Galaxy Nexus] gorillabiscuit:
I have the arrows... Love it.
[Samsung Galaxy Nexus] rockon83:
Love this ROM MMuzzy, thank you! The only feature i'd love to see added is the ability to change the LCD density and have the market keep working, as found in slim bean or paranoid android. Otherwise, loving this ROM. I've tried others and keep coming back to this one. Thanks again!
[Samsung Galaxy Nexus] adbFreedom:
You can change the density by editing your build.prop if you wish, but no matter what ROM or density you choose you will always run into some problems if you go away from 320. There is a thread on xda that explains it more thoroughly here

http://xdaforums.com/showthread.php?t=1392089
[Samsung Galaxy Nexus] icebear8:
there is a problem i found with 4.2.1 but i think it is with all 4.2.1 roms i noticed when using native tethering (And any tethering) PSN can not access it but when i downgrade to stock 4.1 then it works just fine.
[Samsung Galaxy Nexus] gt5oh:
how the hell did you get that battery life
[Samsung Galaxy Nexus] thered1:
I never had a problem with a Muzzy ROM until this one. I never had to do a full wipe either (except when upgrading from 4.1 to 4.2). Because GApps were removed, this broke everything. Anyway, I flashed 12/30 French Vanilla...

When I first flashed (and cleared cache), the camera was missing. I then reflashed, flashed gapps (12/12) and fixed permissions in Clockwork (maybe this was a mistake?) and when I rebooted, it forced me to log into all my google accounts again (makes sense, since the other data was missing). I got tons of force closes and when I reconnected my account, everything seemed better.

Most importantly:

Google Navigation is no longer saying street names! This is driving me crazy. This was a bug with Android 4 + a maps update a while ago, but it was fixed. Now, it's back and it's annoying! Please investigate!

Thanks for all your work Muzzy. You still make fine Roms!
[Samsung Galaxy Nexus] notstevek:
You need to do a clean install, this is all because you did a dirty flash.
[Samsung Galaxy Nexus] thered1:
Ok, I'll post back if there are any other issues (probably won't be). Can someone confirm that the navigation says street names instead of just "head east" and "turn left"

Thanks!
[Samsung Galaxy Nexus] xolanir:
Anytime I use the navigation, it mixes between street names & "in a quarter mile turn right/left" usually like that. Anyone else hear anything different?
[Samsung Galaxy Nexus] notstevek:
Mine says turn left / right in a quarter mile etc but shows the Street names
[Samsung Galaxy Nexus] thered1:
Thanks guys. I think this actually has nothing to do with the ROM. I tested on a Nexus 7 with stock 4.2 and it did the same thing. 10 minutes later, they both spoke the street names. Must be some weirdness with Google
[Samsung Galaxy Nexus] margelef:
In case anyone else was experiencing this same issue (not being able to use Voice Search while paired via BT Audio), someone posted a fix in the Google Bug report page in my original post.

The fix is to change the language for the Google Voice Typing from Automatic to English (US)...or whatever language you choose.

From that Google Code thread:

"Settings > Language & Input > Keyboards and input methods. In the settings for Google Voice typing uncheck "automatic" and select the language of your choice"

I can confirm that this did, indeed, fix the issue for me.
[Samsung Galaxy Nexus] RyanTX:
I have the same problem with Xbox Live.

---------- Post added at 08:11 AM ---------- Previous post was at 08:09 AM ----------

We were having the same problem before 4.2 and that was the suggestion - but that didn't work. I am not having any problems with BT and voice search/typing when paired with my truck.
[Samsung Galaxy Nexus] Wartickler:
Local cache?...

Perhaps it is simply having to download a local cache of all of the street names before it can begin saying them...?
[Samsung Galaxy Nexus] :
I've had this happen once in a blue moon as well. I can fix it by turning off the GPS, force stopping maps in the settings menu, and then clear it's cache and data. Once I re-lock with GPS it will go back to speaking street names.

Also, not to be off topic but it looks like chainfire has opened up voting on the SuperSu icon redesign. Since that particular app is included in MMuzzy's ROM, I thought it's users might like a say in which icon will replace Super Andy (Personally the current icon is ugly as sin, and its about time he considered a more professional design in line with the android style guide IMO). I have a few designs in there actually, but I won't say which ones so that everyone has a fair vote.

SuperSu Icon Voting
[Samsung Galaxy Nexus] margelef:
Are you paired with Media Audio (A2DP Profile) or just Phone audio (HSP/HFP Profile)? I was only having the voice search issue when I was connected via A2DP.

In my BT settings, if I disabled "Media audio" for my car, then voice search would work fine. But with "Media audio" enabled, voice search would get stuck on "Initializing" forever.

After I did the fix of setting a language on the Google Voice Typing, I can use voice search even when I'm connected with "Media audio". So there is definitely an issue with the "Media audio" / A2DP profile and the Google Voice Typing Automatic language.
[Samsung Galaxy Nexus] SparkyXI:
Voted. Thanks.

I've often wondered why Super SU is used in this ROM, as opposed to Superuser by ChainsDD. What are the differences between the two? What makes one the preference over the other?
[Samsung Galaxy Nexus] :
The biggest difference between the two is that SuperSu has the su binary file built-in, whereas superuser does not. All this means for the end user is slightly less maintenance work. When SuperSu updates, you don't need to worry about configuring anything. Its a little harder to tell when superuser updates as just a market update doesn't necessarily mean the binary file that handles root is also up-to-date (most of the time its just bug fixes related to the app itself(. In order to update the binary file with superuser, you have to open the app up and run the binary update check. That's a little more work than I like to bother with for a simple permissions management app, which is why I'm liking the broader adoption of SuperSu.

I also don't really like the superuser icon. Its a small thing, but rooting and jailbreak already carry a pretty negative connotation for manufacturers due to piracy, and the fact that the "face" of android's root management seems to allude to it (its an android with an eye patch) doesn't quite sit well with me.
[Samsung Galaxy Nexus] gorillabiscuit:
heh... well, I'm sort of a light phone user. However yesterday was a full day of push mail and some phone calls... so maybe it was aliens.
[Samsung Galaxy Nexus] SparkyXI:
I hate it as well... I had no idea there was a contest going on - the moment I saw the contest link, I quickly mocked up my own and sent it over. Hopefully he'll still accept mine, as it's pretty rockin' (or so I think).
[Samsung Galaxy Nexus] Bleezyd:
Muzzy - Just an FYI but I figured out the reason my phone was suddenly turning off on its own was because of a loose extended battery/cover. Im running a 3800mAh battery with a bigger cover and somehow the battery connections were becoming loose and thus causing the phone to turn off. My issues were nothing ROM related. :)

Cheers! :good:
[Samsung Galaxy Nexus] 06stang:
Just flashed the zip for the new Seeder mod listed on Droid Life. Not sure if placebo effect but phone seems faster. Good mod

Here's the link to anyone that wants to try it.

http://xdaforums.com/attachment.php?attachmentid=1535868&d=1354625246

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] HeroOfTime:
Out of curiosity, when you flashed the .zip, did it add an app to your phone? I flashed it on my Nexus 7, but didn't have an app appear, so I wasn't sure if the flash took.
[Samsung Galaxy Nexus] 06stang:
No need for an app. The apk he offers just install it on the phone outside of recovery. The recovery zip does it all. No need for settings or anything.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] HeroOfTime:
That's what I assumed, but thought I'd ask since you know what assuming does... Thanks.
[Samsung Galaxy Nexus] brownel02:
Notification bar icons

MMuzzy, et el,

I am a recent convert to this ROM (noon time today). I have been on CNA 3.8 for a while (love all the options but wanted to try out a 4.2 ROM). So far I like the layout and feel I just have a few questions if you don't mind. My initial search did not turn up anything.

1. Is there a way to remove/reorgainze the notification bar icons (I am used to the CM style so the full page not in my order thing is tough to jump into) I thought I read you could but can't for the life of me find where.

2. As for the soft keys, I am looking for a few pics of the mods several folks have done here to see what I would like. I am interested in keeping the stock color but would like smaller keys and is it possible to add 'other' apps to the soft keys? In my previous setup I had Back, Nav, Home, Camera and Menu. Is anything like this possible?

Thanks for the great work.
[Samsung Galaxy Nexus] georgeascott:
1. Long press "settings" in the pull down. Uncheck all, then recheck in the preferred order.

I have no help on number 2. Sorry.
[Samsung Galaxy Nexus] gorillabiscuit:
I use kmgmg's theme for center lock screen and a custom circle battery with minimal soft keys... I look sharp.