yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] RW-1:
Hey thanks, didn't think about erasing the home number there, took it off, but at least you saw it.

I look forward to the new zip, no worries, I'm finishing an alert shift today and plan on relaxing this weekend, so I understand the work constraints.

I figure re-flashing the framework may be all that is needed, it was seeing double that made me question it, plus I wouldn't want others to encounter the same if they were using the return to stock as well.

You do good work Muzz ...
[Samsung Galaxy Nexus] mmuzzy:
Hey RW-1, I redid the file with fresh copies of SystemUI and the framework files so it will not only restore the stock battery indicator but give you back the power menu. I've also checked incoming calls and I don't get that snowball looking thing you had on an incoming call. ;)

Stock Battery Indicator: http://tinyw.in/Rrho
[Samsung Galaxy Nexus] artjef:
Try downloading Google Sync to a PC that you are running Outlook on to access exchange. The Google Sync will keep your Google calendar up to date.

Another thought: Also if you are syncing to a corporate Exchange that the administrator could do updates or change which APIs that are allowed breaking or stopping many types of sync.
[Samsung Galaxy Nexus] RW-1:
Ok, downloaded to PC and will transfer to phone and flash, then let you know, doing a backup as well first. Thanks!

UPDATE: Totally good to go, framework icons, gps lock, and power menu returned, receiving call good as well, back to the dots, etc.

Awesome!

Other than fresh copies, was there something you saw in that other one, or was it perhaps just a fluke?

Kudo's though, because now others can go back to the stock batt and keep the power menu as well ...

Enjoy your weekend!
[Samsung Galaxy Nexus] mmuzzy:
I just took a newer copy with the power menu in it. I think that plays nicer with the ROM now. Thanks for trying it out. :)
[Samsung Galaxy Nexus] RW-1:
You're welcome, glad to assist where possible. Keeping that with the backed up 10-27 ...
[Samsung Galaxy Nexus] SparkyXI:
You know, this has become the perfect ROM. Think about it: totally stock AOSP, with mod choices to load to your liking, and second to none support. Always fresh with the new AOSP builds... Seriously makes this phone on VZW more tolerable.

Well done as always.
[Samsung Galaxy Nexus] mmuzzy:
It should be pointed out that SparkyXI posted that at 11:11. Freaky.

Thank you

That's the interesting thing. Stock. Stock OTA has all the stuff Verizon wants in there, which is really not so bad on this phone anyway. Stock AOSP is, well, not good because for some odd reason things are missing. Some things make sense like drivers Google can't give us because of licensing but other things like the missing file that defines the pull down text just has me scratching my head. So really the ROM is just an attempt at being a mix somewhere in the middle and we sneak things in to make it nicer to use... because I use it too and I don't want to use a broken ROM either.

MODs. Well. I hope you forgive me if I try to get away from them myself. That's why I snuck in the power menu, etc. If someone else wants to throw one together for the ROM, I'm all for it. I've had the kernel I've done for another phone used in other ROMs and both versions of the ROM used as the base for custom ROMs.

What this ROM is as I upload it is the ROM I want on my phone, and it is of course. ;)
[Samsung Galaxy Nexus] silverramsrt:
11:11 plus 11 minutes = mmuzzy's post (11:22):eek:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mmuzzy:
Oh sure, you couldn't wait until 11:33. ;)
[Samsung Galaxy Nexus] Fahrenheit:
So I tried this, but it would never sync without autosync enabled. Calendar would still only sync partially. That prompted me to look for some other issues, and I came across the phone code that enables Email Debugging: *#*#36245#*#* - dialed that in the phone app and it showed a new debug menu in the Email app. From there, I enabled verbose logging....and long story short, the problem was that a specific calendar invite was crashing the sync. Once I deleted the bad invite, everything started synching again.

Android 4.1.x apparently has a problem with calendar invites that recur forever, and that have hundreds of invitees. I had the same recurring calendar invite when I was on ICS and the calendar synced fine then.

Thanks for the ideas!
[Samsung Galaxy Nexus] mmuzzy:
Wow. Amazing that you were able to find that. Kudos to you for your perseverance.
[Samsung Galaxy Nexus] techspecs:
+1. This is THE build for this phone. The AOMP. :beer:
[Samsung Galaxy Nexus] Badger51:
Old Voice Mail Icon now appearing

MMuzzy et al,

Really enjoying this ROM and noticing great battery life.

I'm currently on the 10/27 ROM

This last week I flashed several ROMs starting with the 10/24 and 10/25 versions.

Somewhere along the way, the old Verizon voicemail icon starting appearing in my notification bar.

I use Google voice for voice mail .

Is there a way to disable the old voice mail, *86 ?

thanks
[Samsung Galaxy Nexus] mmuzzy:
Thank you. Have you gone into the phone app settings and made sure you've got Google Voice selected and configured instead of carrier?
[Samsung Galaxy Nexus] RW-1:
Seconded...

The word Stock is overused, it is exactly what we want, I prefer to put it in this way:

If VZW actually allowed Google to update the damn thing each time there was new changes to AOSP, then this is what we would have.

People always ask what's so great about this, and that's it, you get the latest code changes without major additions.
[Samsung Galaxy Nexus] Badger51:
Voice Mail COnfiguration

Yes, Google Voice is selected.

When I go to configuration, I do get the error message that "your network carrier is not supported for automatic voicemail configuration"....

However, I've seen that before and Google Voice has been working properly.
[Samsung Galaxy Nexus] mmuzzy:
Yeah that seems to be a normal condition to get that error. The only other piece I can think of is to make sure that the voicemail didn't get switched off for the number: https://www.google.com/voice/b/0#phones
[Samsung Galaxy Nexus] artjef:
Nice find
[Samsung Galaxy Nexus] subsonicbug:
badger, go through the process of deactivating and reactivating you google voicemail in the voice account settings.

you will have to dial a *73 code to deactivate then a *71+voicemail number code. ive had to go through this on nearly every flash to get things set up right again.

hope that helps
[Samsung Galaxy Nexus] SparkyXI:
Freaky indeed, since that's my lucky number (hence the "XI" in the username)...
[Samsung Galaxy Nexus] artjef:
Google Servers

A little off topic but ...

Have you notice over the last month or so that the Google servers seems unavailable (Strength bars or WIFI bars are grey or white depending)? Or is this just an East Tennessee thing? I do not believe it has anything to do with the ROM as I have seen my son's S3 do the same. Any ideas on what's the cause?
[Samsung Galaxy Nexus] mmuzzy:
"Tapatalk 11", now I get it.

I haven't seen this personally. Is there any pattern to when it happens? If the Wifi is marginal it might be avoiding it, and then switching modes between data and wifi would give a white indicator until it established connection again.. That can be switched off in the wireless settings.
[Samsung Galaxy Nexus] artjef:
Seems to be in the afternoon and I usually notice it on 4G but have seen it on WiFi. I am beginning to wonder if VZW is playing with ACLs on their routers. Or maybe they are testing one of the next generation firewalls from someone like Palo Alto.

Did change my WiFi settings though.
[Samsung Galaxy Nexus] gmmorrell:
Definitely. Wasn't sure if it was ROM. It only happens at work and never at home. The signal at work is weaker and both locations have WiFi. (Chicago).
[Samsung Galaxy Nexus] erasable:
I saw this last week. WiFi and 4g greying out randomly for second or two. I haven't seen it since and I'm in NJ. I think I read Google was having problems last week, maybe it was related? Either way its been solid this week even after Sandy.
[Samsung Galaxy Nexus] silverramsrt:
Have I mentioned how much I like this ROM?

I like not having to keep my phone tethered to the wall.

Using the latest nightly from Franco and 2100mah batt. Only had an hour of screen time but I never use WiFi and signal isn't the greatest at work.

Well, I wrote all this thinking I had screenshots! What a fail!:what:

Anyway, 17hrs on battery is a new personal best.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] johnco1972:
I saw thishttp://www.ibtimes.co.uk/articles/4...ellybean-update-galaxy-nexus-apps-package.htm pop up on one of my news feeds. Seems reassuring that Google is keeping the nexus family together through continued updates. I think that will keep the nexus reputation up.
[Samsung Galaxy Nexus] RW-1:
Looks to me that they got a C&D, because it's gone, the download, but I already had the camera and the second release of the 4.2 KB, which is nice. Didn't bother with the clock though, can wait on that.

We won't get a good 4.2 until the source hits and dev's like Muzzy can incorporate it with the latest drivers for our hardware. But the GNex is far from being left out in the cold here.
[Samsung Galaxy Nexus] techspecs:
No, it's there in the linked thread in the OP.

Edit: the hyperlink is on the word 'released'.
[Samsung Galaxy Nexus] SparkyXI:
I change up the stock Tapatalk signature to something different every post. Just cuz.

Sent from my Galaxy Nexus using RapaBap 2
[Samsung Galaxy Nexus] jeffc83:
Best ROM I've used on my gnex. Thanks for all your hard work Muzzy! Battery life is much better and I have not one issue to report.

For what it's worth, I flashed Muzzys 2nd build over stock...would not boot. Wiped and had no issues. I of course reloaded all my apps and went problem free from there. I then flashed his latest over that and have had no issues at all. I like having the ability to flash/upgrade the ROMs that come from Muzzy without having to wipe each time....thanks again! (I did wipe cache, dalvik, and system before flashing)
[Samsung Galaxy Nexus] mmuzzy:
That makes me think of that game "Bop It".

Excellent. Glad it's working well for you. :)
[Samsung Galaxy Nexus] baboonsRus:
Sorry if this is off topic,but muzzy, I noticed your thanks in the thread about the 4.2 transformation... does that mean it plays well with your latest version of this ROM?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mmuzzy:
I did try it, yes. Everything seems to work as OK as others have reported with 4.1.2. I'm obviously not making a big deal about it since officially it isn't out. I really the changes. Looking forward to its release.
[Samsung Galaxy Nexus] :
Just flashed and it works flawlessly.
[Samsung Galaxy Nexus] johnco1972:
I think we can thank MMuzzy for keeping a clean ROM that isn't full of mods that can screw things up.

I flashed the transformation zip over the MMuzzy's latest and it runs beautifully.
[Samsung Galaxy Nexus] mmuzzy:
That reboot addition on the power menu doesn't play nicely with battery mods but I still think it's a keeper. I'm really liking the new camera.
[Samsung Galaxy Nexus] :
Totally loveeee the new camera! its so simple and amazing. The keyboard is also pretty freaking awesome as well. typing with it right now :)
[Samsung Galaxy Nexus] tacopimp:
Got a link to what you flashed? Thanks
[Samsung Galaxy Nexus] johnco1972:
This is what I flashed.

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

I'm going to make the same disclaimer as everyone else: flash at your own risk. (Just covering my butt)
[Samsung Galaxy Nexus] mmuzzy:
Holy cow. I notice they have 4.2 GAPPs already. If anyone flashes this over the ROM I see Gallery and Google Now as being potential issues just because of how GAPPs works vs included.
[Samsung Galaxy Nexus] RW-1:
I saw that too, but for me I'd never grab the "transformation" pack, that's placing too much trust to install three or more apps at once, when you may or may not be sure if all three will play nice.

I did the last iteration of the 4.2 camera, because those who did the first release on the board Iinked to from DL, they had issues because not all the required lib files were there. that got solved, and my install was with no issues.

KB, did both releases with no issues.

clock - naah, I'll wait until 4.2 itself ;)

as for GAPPS, kinda the same there: I don't see any reason one should require the app ported over just because it is 4.2, you know what I mean ... unless there was some magic feature added (such as the play store allowing you to clear out an app out of the "all" list when that leaked, or the gmail swipe to delete, etc.) to me, those can wait as well.
[Samsung Galaxy Nexus] johnco1972:
What would the potential issues be? I'm on your 10/27 ROM. Give me a few clues where and what to look for, and I'll see if I can find any issues.
[Samsung Galaxy Nexus] mmuzzy:
I agree 100 percent. Although I did try the camera and keyboard, but that's as far as I went.

The potential problem, in broad strokes, is that the ROM is compiled with a version of libraries that are dynamically linked to the applications. I'm reading where these libraries are being overwritten with newer ones to make the 4.2 apps work. The problem is that if OTHER apps were linked against the original library files then you have a library mismatch against what the app is expecting. It's a potential domino effect. I'm also reading where people with AOKP and CM10 are wondering why their stuff broke when they flash these AOSP files. I think it's great to tinker with the new files but people should assume things might break, especially if you aren't on AOSP (or the Nexus, yes really).
[Samsung Galaxy Nexus] johnco1972:
That makes sense. I haven't noticed any issues, but that isn't to say something might be broken that I am unaware of. I'm not complaining...I knew when I flashed it that there was risk.
[Samsung Galaxy Nexus] Protibus:
I am running AOKP M1 and flashed the new 4.2 GAPPS. No problems at all for me at all, just some really nice new apps.
[Samsung Galaxy Nexus] mmuzzy:
Nice. Thanks for the update. :)
[Samsung Galaxy Nexus] johnco1972:
MMuzzy, quick question. How can I re-enable the home screen auto rotate? I liked it on the 10/24 ROM and would like to keep that feature.
[Samsung Galaxy Nexus] mwalt2:
Just add the following to your build.prop:

launcher.force_enable_rotation=true
[Samsung Galaxy Nexus] mmuzzy:
It was still enabled in the last build unless you ran the disable script. The line MWalt gave will restore it though.

Thanks, MWalt.
[Samsung Galaxy Nexus] johnco1972:
I checked and that line is set to true. Now that I think about it, the home screen rotate didn't stop working up to I flashed that zip android 4.2 features.
[Samsung Galaxy Nexus] mmuzzy:
Ah. Launcher in 4.2 might ignore that.
[Samsung Galaxy Nexus] johnco1972:
So there is one possible bug. Have to wait for some other feedback. I'm hoping in a week 4.2 will be available and it won't matter :)
[Samsung Galaxy Nexus] mmuzzy:
I'm not going to even worry about patchwork 4.2 apps until we see 4.2 in aosp. It might not be a bug at all in a complete ROM.
[Samsung Galaxy Nexus] RW-1:
Totally with you there ...
[Samsung Galaxy Nexus] xolanir:
I don't think people should even be discussing any 4.2 patch work in this thread because you didn't intro it as part of the mmuzzy experience, and because it's not official. What ever issues arise from people doing the patchery, those need to be taken to the respective thread for troubleshooting purposes so as to not clutter this thread.
[Samsung Galaxy Nexus] darklordofthesith:
When 4.2 comes out and you update the rom , is it possible to give a choice of what battery to have? I personally don't like the circle meter. I think a choice would be good. I see the vote, but if possible could we have a choice? Sorry for sounding like a little bi**h.
[Samsung Galaxy Nexus] :
Agreed, but I don't really like the circle one personally. I like there one we have in the newest build currently. I liker the kinda "stockish" look but still shore the percentage perfectly. and dude you're not complaining it's OK.
[Samsung Galaxy Nexus] Cam2:
When I check MMuzzy's ROM in Goo Manager, I see zip files for the circle battery and the stock battery, so we already have a choice.
[Samsung Galaxy Nexus] mmuzzy:
Agreed. I think it's great to hear 4.2 apps are working but the true test will be when we see 4.2 hit the repos and we have a better idea if we have weirdness then. Until then, it's a moot point to even worry about something not working regarding 4.2 gapps. There's nothing to fix because we're making those apps work by stepping on 4.1.2 libraries, etc.

I'm not even sure I'm going to bother with the battery indicator in 4.2. I'm seeing a battery with percentages in the quick toggles on 4.2. So the power menu, maybe, but the battery might be a non issue.
[Samsung Galaxy Nexus] :
Oh yeah i forgot about that haha. That's true. so I guess the battery indicator won't be a problem after all!
[Samsung Galaxy Nexus] johnhimm:
Can confirm the 11/03 Circle Clock Build and the 4.2 Gapps are running good. 3 days without any issues.

Great rom Muzz
[Samsung Galaxy Nexus] mmuzzy:
Probably not. I think it'll work that way just fine.

Thanks.

Yeah I figured those alternative ROMs would be found if anyone wanted them but we're just waiting for the new 4.2 goodies before we do anything major now.
[Samsung Galaxy Nexus] RW-1:
Major doesn't include ABSW* eh ? :)

*Angry Birds Star Wars
[Samsung Galaxy Nexus] mmuzzy:
LOL. Thankfully it isn't. They're slapping Star Wars on everything and calling it a special edition. Luckily it isn't a dessert so we aren't in danger of Android: Star Wars edition. Oh wait, we already had that on the droid. :P
[Samsung Galaxy Nexus] mmuzzy:
Rom update - avrcp 1.3

November 10, 2012

- Bluetooth AVRCP 1.3 fix (tbriggs)

Minor update to attempt fixing missing metadata when pairing to some bluetooth enabled headends. I have no way to test if the patches work but nothing seems broken and I do see bluetooth devices in my house still... so there's that. ;)
[Samsung Galaxy Nexus] SparkyXI:
Something that's been bothering me... For some reason, when connected to a bluetooth device, speech to text errors out. This isn't just on your ROM, but throughout Android. Any thoughts on this?

Sent from my Galaxy Nexus using non-voice-dialing-via-bluetooth-Tapatalk 2
[Samsung Galaxy Nexus] pennjersey83:
11-10 ROM working great. Like the battery. Thank you mmuzzy
[Samsung Galaxy Nexus] darklordofthesith:
Well 4.2 is out but not for our nexus. So we wait for the man to make our nexus new again. Looking forward for another great release from ya.
[Samsung Galaxy Nexus] BOY_:
Out as in the source is in aosp? If so, this is good news :)
[Samsung Galaxy Nexus] mmuzzy:
Bluetooth is one of those things that's hard for me to do much with since I don't have anything bluetooth but lets see what happens after 4.2 and I'll take another look at it.

Thanks :)

Nothing yet in the repo. I just checked again. If it drops while I'm at work it'll be my project for the afternoon.
[Samsung Galaxy Nexus] RW-1:
An ota to the nexus 4 does not mean it's "out".

Not in source yet but that could happen for today or tomorrow, with luck...
[Samsung Galaxy Nexus] mmuzzy:
fingers crossed and linux box on simmer
[Samsung Galaxy Nexus] wickets:
still amazes me that updates are faster from you than they are direct from the goog. 125 thumbs up
[Samsung Galaxy Nexus] mmuzzy:
Thanks. That's the great thing about the Nexus, we have a really active dev community. Lots of great ROMs to basically insure we don't need to rely on Verizon for the updates. Unfortunately they're the roadblock more than anything.
[Samsung Galaxy Nexus] keatre:
Galaxy Nexus 4.2 - HSPA+

HSPA+ Only, though. Unless the drivers/binaries from 4.1.2 can carry over.
[Samsung Galaxy Nexus] mmuzzy:
Correct. Nothing in the repos yet. We're still in F5 mode.
[Samsung Galaxy Nexus] keatre:
Right - just some additional information for the lurkers.
[Samsung Galaxy Nexus] mmuzzy:
My plans for the afternoon just firmed up:

https://groups.google.com/forum/?fromgroups=#!topic/android-building/-ymcoMuDAbA
[Samsung Galaxy Nexus] MarkGbe:
very nice :D
[Samsung Galaxy Nexus] Greg Tolan:
Awesome! I just saw this and had to head to this thread. By this weekend MMuzzy will have banged out 3 ROMS!!! :cool:
[Samsung Galaxy Nexus] techspecs:
::chanting:: four.. two..! four two! Muzzy, I feel good knowing this is in your capable hands.
[Samsung Galaxy Nexus] RW-1:
Darn, you beat me to it ....

Ok ... no excuses, let's see it by ....... tomorrow heheheheehe or tonight, depends on your DL bandwidth with everyone grabbing it.

This is good though: "-Proprietary binaries to run AOSP on Galaxy Nexus (maguro, toro and

toroplus), Nexus 7 (grouper) and Nexus 10 (manta) are available at

https://developers.google.com/android/nexus/drivers "

so playfully .... Get to it man! :)
[Samsung Galaxy Nexus] SparkyXI:
Woot. Can't wait, buddy. Can't wait.
[Samsung Galaxy Nexus] BOY_:
w00t
[Samsung Galaxy Nexus] mmuzzy:
I just ran home to start sync and... it's not done in the repo yet :P

I got halfway home when I realized I didn't check yet. SSH from work I guess.
[Samsung Galaxy Nexus] NeoMagus:
Had to get you off the devils number in thanks there buddy lol , I'll check back later looking forward to more great work!
[Samsung Galaxy Nexus] drPheta:
Awesome. I'm stoked, however anyone know what the word on Google Voice not working with 4.2 is? I rely on it heavily, and I wish they'd update that app to allow MMS... but this issue is just horrible if it's not fixable soon.
[Samsung Galaxy Nexus] mmuzzy:
I avoided 4.2 apps for this reason. I would put money on it working on a 4.2 ROM. Patchwork hybrid ROMs of 4.1.2 and 4.2 would have all sorts of issues. Although credit goes to the devs that had stable releases with that balance.

EDIT:

...and we're live! Commencing sync. :)
[Samsung Galaxy Nexus] Greg Tolan:
No this is weird it is an issue with google voice and 4.2. I have a stock/rooted N7 and updated to 4.2. GV crashes whenever I try to send a text from it.
[Samsung Galaxy Nexus] Scallywag1:
What about voice mail?
[Samsung Galaxy Nexus] mmuzzy:
Hopefully we see an update soon then. I use it as well.
[Samsung Galaxy Nexus] Greg Tolan:
Good question..doesn't seem to be a problem. I just tested it.

agreed.

---------- Post added at 02:47 PM ---------- Previous post was at 02:44 PM ----------

http://www.androidcentral.com/users-report-serious-crash-google-voice-android-42
[Samsung Galaxy Nexus] pennjersey83:
uh-oh...I think I have a problem

I decided I wanted to try the stock battery mod. I flashed it and now when I try to reboot I get stuck at the "X" logo. I have currently been on the "X" logo for 6 hours. When I try to restore my Nandroid backups they both say md5 mismatch. When I plug my Nexus into my PC windows explorer does not see it so I cannot transfer the ROM file to my Nexus and try to re-flash.

Does anybody have any suggestions on how I can fix this problem?
[Samsung Galaxy Nexus] Scallywag1:
Do u have the ROM on ur SD still? Pull battery and reflash rom with only a format system and cache.
[Samsung Galaxy Nexus] mmuzzy:
I think you can turn off the md5 check. Might be worth a shot.
[Samsung Galaxy Nexus] pennjersey83:
Does CWM have the option to turn off md5 check?

I don't have the ROM on my sd card. I guess that was a mistake too. My biggest mistake was renaming my nandroid backups with spaces in the name. Right now I'm trying to learn how to adb push a ROM to my device.
[Samsung Galaxy Nexus] RW-1:
Can you manually boot it into fastboot (both volumes and power)?

If so try that and then hook it to your computer, perhaps then you can use ADB to push a ROM over .... just ideas to try ...

No offence to CWM, but I abandoned that when TWRP came along ...

With the room on the GNex, I always keep the current ROM, kernel and last kernel, mods, on the SD "root", in addition to a current backup, just makes sense in case you need it.