yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] divequip:
Avsat! app registration issue involving GCM & GAPPS

Hi all,

I have been a silent follower of this thread for about a year.

I don't post as I never have anything to add but would like to take this opportunity to thank you all for the knowledge you have passed along and enjoyment you have provided.

I am running MMuzzy ROM 12//22 with Tiny Kernel 2.4.2 (3.0.31).

I recently installed the Avast! security app.

I am not able to register the phone with Avast!.

I get the following error message:

"Could not connect to Google Cloud to Device Messaging (PHONE_REGISTRATION_ERROR). Please make sure that your Google account is set up correctly. Screen shot attached.

My thinking was that the problem was most likely with my gapps so I reflashed:

goo.im/gapps/gapps-jb-20121212-signed.zip

When that didn't solve the problem I wrote to Avast customer support.

Today I received the following reply:

"This message is from Google Cloud Messaging (GCM) framework, which is used for connecting to avast account. Avast is only using it, so this error is not connected to our application, but to ROM itself.

I have read some notes about MMuzy ROM and it seems that the GCM support is missing there - please try to download GCM framework and GAPPS from CM site and try to flash them. Avast officially supports only original ROMs and CM builds."

Attached are screen shots of the Google Apps installed on my phone.

My question is do you agree with the above statement?

If so, can you recommend which GCM framework and GAPPS from CM to download and flash?

Thank you for your assistance.
[Samsung Galaxy Nexus] mmuzzy:
I'd love to know what 'original ROMs' means when Android is an open platform. CM isn't an original ROM either and I don't understand why he says that one is ok. As for GAPPs, the one I link is the official GAPPs that even CM uses. Also, I really want to know what knows he has about my ROM. Really? My ROM is an AOSP build. You know, the code from Google?

The bit about GCM framework has to do with code in the program, not the OS. And If you do a search for that error it always points back to Avast. Shocking. I don't think you got an answer from anyone who knows what they're talking about I'm afraid.

The error has something to do with whatever order of events is happening with account authentication. The fixes I see all seem to point to roughly something like this:

- Disconnect from Google-Account

- Reboot

- Connected again to Google-Account

- Connected to Avast

So no, in a nutshell, I don't agree. I think it was someone who doesn't know enough to give you a helpful answer and decided finger pointing was the way to end the conversation.

----

EDIT: I'm still sick so my patience for things like fingers pointing at me from customer service people is lower than normal. Sorry.
[Samsung Galaxy Nexus] gorillabiscuit:
I guess my first question in response to your concern is why in the world would you install Avast on your mobile? The #1 reason battery life sucks, apps crash, and people complain of slow performance is 3rd party crapps. They're no good for personal use on a PC so why would they be good for an Android. Sorry for the rant, but AV for Android is as useless as "t*ts on a bull" :cowboy:

---------- Post added at 08:35 PM ---------- Previous post was at 08:30 PM ----------

You know what I love? Everyone has their beta 4.2.1 builds with huge disclaimers about how this is experimental and buggy and blah blah blah... and Mmuzzy's ROM is like "Here's my ROM, enjoy." Just sayin'...
[Samsung Galaxy Nexus] ArnieG:
Amen
[Samsung Galaxy Nexus] Wartickler:
I always thought it was, "...about as useful as t*ts on a boar hog..." :cowboy:

Sent from my Galaxy Nexus Toro that is way better than yours [see also: "Mmuzzy"]
[Samsung Galaxy Nexus] zerocool79346:
Bingo
[Samsung Galaxy Nexus] divequip:
Dear Mr. Muzzy,

Thank you for your well thought out, thorough and instant reply to my inquiry.

I took your comments to heart and knowing how accurate you always are I Superwiped and then flashed your 12/30 French Vanilla ROM, Tiny's kernel and "your" gapps.

I then let the phone reinstall my apps from the google play store instead of using Titanium backup (another one of your tips).

I then went through the Avast setup which now went flawlessly.

So once again it's proven then when mmuzzy speaks one can follow the advice with confidence.

Also, just reinforces the "mmuzzy axiom" -- when you start getting strange results, do a superwipe and ROM re-installation.

I will copy this thread to the Avast CSR.

Missed the post about you being under the weather. I've had a recurring cold since Thanksgiving and it certainly is draining and tests one's patience.

Thanks again to the mmuzzy gang!

Best regards and Happy New Year,

Jack
[Samsung Galaxy Nexus] mmuzzy:
I'm just glad it worked for you. Thanks for the update.

------------

By the way, you're all awesome :)

Night guys. Im pooped.
[Samsung Galaxy Nexus] SparkyXI:
Keep on that sickness... It's definitely going around...
[Samsung Galaxy Nexus] ba_hamilton:
My experience with the seeder mod was not good. Battery went from 60% to 20% in 30 minutes. Did not notice any significant improvement in speed. Proceed with caution.
[Samsung Galaxy Nexus] objectivedays:
Awesome job!

Thanks for the awesome ROM, really appreciate all of the hard work that went into this.
[Samsung Galaxy Nexus] jcmm11:
As far as avast goes it's more than antivirus (which I would turn off). It's also, among other things, one of the highest rated anti-theft/loss apps out there. It also has other features which people may or may not consider useful.
[Samsung Galaxy Nexus] AirBoss24K:
Been loving this ROM since I downloaded it a few days ago and I've been doing some tweaking to get the most of my battery. So far, the battery has been fantastic, but there is one Partial Wakelock in particular that's got me a little confused and I was hoping you guys could help me figure out what it is. It's called "Genie" and it's got my phone awake for a whopping 8 minutes which is almost double the next item on the list (Facebook). I've attached a screenshot of my BBS so ya'll can get a better idea of what it might be. I've already done several searches and I'm fairly good at troubleshooting but this one has me stumped. It's clearly a Google related service that has something to do with the News and Weather, but I'm not sure what or where it is.

I know this isn't exactly ROM related, but I know there's a lot of smart guys in here who probably have some good suggestions for me! Thanks in advance ;)
[Samsung Galaxy Nexus] runandhide05:
That's the built in new and weather widget, odds r its syncing in the background

Seen here
[Samsung Galaxy Nexus] dswartze:
Not on wifi here at work. I am talking about the phone's signal strength to the tower, which I can see from my office. I normally have 5 bars of 4G from my desk. Right now I only have 3 bars of 3G!

I also tried calling the *228 number to reprogram the phone - but I cannot get the phone's keypad up to press 1 or 2, so activation fails.

---------- Post added at 12:39 PM ---------- Previous post was at 12:36 PM ----------

Darn! Just tried to restore from the backup I made yesterday before flashign your ROM and get an error while trying to restore the system partition.
[Samsung Galaxy Nexus] ibenjakinov:
Try using the wugfresh app that mmuzzy posted a few posts back to go back to a 4.0.4 stock factory image (IMM76K) and see if you still have signal issues. If so, it might be a hardware issue.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] samuelhadams:
I'm experiencing really really long boot times with the 8/22 version. So long that I wiped data, cache, and dalvik cache to start fresh and still no change. Seems if I reboot right after booting then the bootup time is minimal. But if the phone has been on for awhile boot time is unbelievably slow. About the same time it takes for the system to boot the first time after installing the ROM. Thoughts?
[Samsung Galaxy Nexus] mmuzzy:
The long boot is normally a result of something that doesn't shut down properly. it's a file system check. if an application is acting funny that might cause it. It would also explain why its less likely to happen right after you start up. not all your applications are probably running full tilt yet.
[Samsung Galaxy Nexus] samuelhadams:
System is hanging during bootup on the Google screen but not the Nexus boot screen. Does that affect your diagnosis?
[Samsung Galaxy Nexus] mmuzzy:
Actually no. That's where it will sit. The first time booting Jelly Bean takes a long time, then it's quicker unless there is something flagged as being wrong with it. A lot of times this is what will happen if you pull the battery while the phone is on, or if there is an app that isn't shutting down cleanly as you power down.

If you do a search for 'long boot' 'google logo' and 'jelly bean' you'll find people with a similar problem. It's normally just the first boot unless there is a repeat offender app, etc. You could try fixing permissions, then I'd probably clean flash and be very selective of the apps you install so if the issue comes back you can try to figure out which one is causing it.
[Samsung Galaxy Nexus] samuelhadams:
I'm going to try a fresh flash. However, I'm not exactly confident it will resolve my long boot times. I install apps very sparingly. Right now I might have 5 market apps installed and they're the same ones I always use. I'll report back.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ibenjakinov:
Any time I change any system files, i.e. bootanimation.zip, or restore any type of system files with Titanium Backup (system apps, browser, bookmarks, mms/txt msgs) it will hang at the Google logo to do a file system check. Also if you use a mod like Trickster mod and set it up for zipalign or SQL it will hang do a file system check on the next reboot. Usually this will just happen after making these types of changes or after installing a new ROM. Some people claim that flashing the JB bootloader can help with long boot times but I'm not sure how valid that is.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] mmuzzy:
I flashed that almost as soon as Jake came out with it and I thought it helped but it also could have been the timing of the phone 'settling down' after its consistency checks.

Even still, it might be worth trying if it hasn't already been tried.
[Samsung Galaxy Nexus] revo_65:
So fixed the network unknown error I had. In a round about way from the thread here on xda to change the carrier name I got linked to rootzwiki and pushed an eri.xml file from there to /data and no more issues! (I would attach the file but I'm on my phone)

So far loving this. Nice stock and quick. Awesome work!
[Samsung Galaxy Nexus] mmuzzy:
I'm glad you got it fixed... however, that's why I asked if you had flashed any mods that might have written to the framework.

When I saw that a decompiled element of the framework was the fix a few weeks ago I tried to figure out why it was needed in the first place. What I found was that, for some reason, that part of the overlay in the AOSP source was missing for our device. So I made sure the file was in my source for the past couple of builds. Anyone who has been using the ROM since that happened hasn't had those issues since I figured that out. It's kind of like applying the fix before the ROM is even built. The only thing I could think of that would break the fix was a MOD being flashed that might overwrite my fixed framework-res file. This would include nav bars, battery mods, those sorts of things.

But the bottom line is that I'm glad you fixed it. :)

EDIT: The file is supposed to be found at overlay/frameworks/base/core/res/res/xml/eri.xml in our device directory before the ROM is compiled and it isn't in the source. If you look on another AOSP ROM where it exists at compile time you won't even find the file in the ROM because it's supposed to be part of the framework-res.apk. /nerdmode
[Samsung Galaxy Nexus] revo_65:
Hey thanks for the quick response and in depth explanation. Its not often you find devs that stop and explain things so we can see the behind the scenes aspects of the ROM. Thanks again and awesome ROM!
[Samsung Galaxy Nexus] mmuzzy:
I appreciate it. Also, I really want to thank you for finding a fix that works. There's always more than one way to get somewhere and I'm glad you found it and stuck it out. Well done. :)
[Samsung Galaxy Nexus] Moonkae:
Very pleased with the ROM. Performance was excellent, buttery smooth with stock kernel. Battery life was equally nice: 2.5 hours on screen time over ~12 hour day (3g, mostly WiFi usage). Question: I want to flash francos kernel to compare but I'm really just so happy I'm considering just keeping it as is (if it isn't broke don't fix it). If it isn't as good will the stock kernel image located at the bottom of this page work: ???

http://rootzwiki.com/topic/28486-ro...-themes-work-on-boot-now-08242012-0533pm-edt/

I did some searching and this was the only good source for the stock JB kernel I could find, MMuzzy what do you think? Excellent work
[Samsung Galaxy Nexus] mmuzzy:
Thank you :)

There are a number of ways to get the stock back if you flash over it. One of the easiest ways to get a kernel back on a ROM, assuming you haven't flashed a bunch of MODS which you'd lose, is to just to dirty flash the ROM again. Also, Dakota0206 has an awesome Jelly Bean page. I find myself checking there before I google something JB related: http://www.thesuperusersguide.com/everything-jelly-bean.html . He has a whole section of kernels too, including a flashable stock one.

The bottom line, make sure you still have a copy of the ROM as a fallback and have fun. ;)
[Samsung Galaxy Nexus] Moonkae:
Ah excellent. I did see that page during my Google search, have it bookmarked now. You seem to be pretty active in your own thread, replying to almost any questions people have, and thats super awesome. I've been trying a few new JB roms here and there over the last week but I can say this one is the best overall, can't beat that AOSP (I do miss the notification pulldown toggles but hopefully someone makes a mod to add that). Speaking of mods, what is the 'Enhanced power menu' exactly? I would assume its the additional options (boot into recovery, restart, etc) when the power button is held down.

Again, excellent work. I'll be using it and will report any major issues.
[Samsung Galaxy Nexus] AGeleff:
So, do you guys remember the 4G radio issue I was having when I initially flashed this ROM last weekend? Here's something strange. I recommended this ROM to my buddy's brother, who was having perfect 4G connectivity prior to installing this ROM, and after he installed it, he started experiencing the same 4G drop issues that I was having.

What's weird is that he's about 80 miles from my place in Philly and lives in an area that typically gets stronger 4G signal than I do in or around my home. It's so weird. I'm not saying there's anything wrong with this ROM, especially since other people haven't been having the issue, but I just found it strange.

Any ideas?
[Samsung Galaxy Nexus] mmuzzy:
Much appreciated.

The MODs can be a problem with ROMs because they need to tromp on the framework on your phone. So unless a MOD actually pulled it from your phone, it could break something else. That goes for any ROM actually so I try to duplicate the functions in widgets or apps.

The Enhanced Power Mod adds reboot and recovery. What I use is a toggle in Elixir2 notification toggles to duplicate it. I'm able to do reboot/recovery/shutdown from a toggle. No messing with the framework of your phone's ROM and it saves wear and tear on the power button. ;)

There are other notification toggle apps in the market. Elixir2's toggles are the prettiest but I'm used to that app.
[Samsung Galaxy Nexus] mmuzzy:
I'm seriously at a loss on how flashing the ROM affects signal. The baseband files aren't contained in the ROM so it's not like it's flashing a bad copy. The thing I'd suggest is to go into status in the ROM and see what the actual db level of the signal is compared to preflashing the ROM or perhaps to someone else that can measure signal on the same carrier. Perhaps it isn't the signal level but the way the bars are displaying?
[Samsung Galaxy Nexus] AGeleff:
I thought the same thing, but it's not like the signal is just low - rather, it just cuts off.

Like I said, I'm not blaming the ROM at all. His radio files were unaltered, like you said. It's just strange how the same literal problem happened to his device, too.
[Samsung Galaxy Nexus] gorillabiscuit:
Thanks for the clarification... I prefer SeekDroid.
[Samsung Galaxy Nexus] johnhimm:
Does the vanilla ROM include the tether patch?
[Samsung Galaxy Nexus] techspecs:
Yes.

---------- Post added at 06:12 AM ---------- Previous post was at 06:10 AM ----------

I installed the apk as a easier to remove trial. No issues with drain and some things are WAY faster like how fast Tapatalk loads these threads for example. I likie.
[Samsung Galaxy Nexus] j0hnnyth3f0x:
I seem to remember a small conversation about voice search fc'ing, was there a fix found for this? I don't remember seeing one...

EDIT: except for the choose English instead of automatic in the language settings fix, which didn't work for me

Sent from my Mmuzified Galaxy Nexus
[Samsung Galaxy Nexus] mmuzzy:
Yes. Update yer stuff. If you go to Play and do your updates, you'll find Google Search in manual updates. The app in GAPPs seems to be FC'ing until you update.
[Samsung Galaxy Nexus] j0hnnyth3f0x:
Wow...derp! I feel retarded now... Thanks mmuzzy, you are a scholar and a gentleman, or gentleperson if we're being PC :)

Sent from my Mmuzified Galaxy Nexus
[Samsung Galaxy Nexus] mmuzzy:
No problem. The first silly question is free. ;)
[Samsung Galaxy Nexus] marc.ientilucci:
so to clarify, i am flashing french vanilla/Panoramic Mode Fix/gapps in that order correct?

or do i do the Panoramic Mode Fix after i have the rom set up - reboot back into recovery and flash then?:confused:
[Samsung Galaxy Nexus] mmuzzy:
The pano fix is because when I shaved off GAPPs I wanted to keep the better Gallery2/camera so I'm not compiling the AOSP one. In the process I didn't copy the lib files required for pano. The zip file simply copies the necessary files I missed. It doesn't really matter what order you flash them in. As I'm talking I probably could have avoided it altogether if I had.

So it really doesn't matter but:

ROM

GAPPs

Fixes and/or MODs
[Samsung Galaxy Nexus] Robin M:
If you are talking about the original boot animation (pictured below) that first came with the GN phone, that has ALWAYS been a favorite of mine. I'm using it still with this ROM. Here it is. Do NOT flash it. Simply put it into /data/local/ and change the permissions to rw-r--r--.

PS... This animation has been upgraded from the original for HD graphics. Also, don't worry. It contains no sound. ;)

s
[Samsung Galaxy Nexus] mmuzzy:
I liked that one too but that animation was stock for ICS. After getting used to the new Nexus boot the 4.0 boot animation feels like regression.
[Samsung Galaxy Nexus] dmillerzx:
First off, want to say thanks to MMuzzy, I love your ROM! The issues I'm experiencing are with wifi and don't believe they're due to this rom; however, 4.2. I've noticed two different issues with wifi since upgrading to 4.2 (clean flash).

After sleeping (I believe more specifically deep sleep, as this only happens after at least ten minutes of sleeping) my wifi will disconnect upon waking from sleep and then connect again. It appears that while the phone is sleeping there isn't any network connectivity at all. Even worse is that sometimes when I awake from sleep both the wifi and cellular bars are grey forcing me to reboot. I've noticed this to be especially troubling when waking in the morning as my reception is all grayed out and messages are queued up waiting for my phone to function on the network again.

I know 4.2 has a plethora of wifi issues; most are being reported for the N4 though. Is anyone else seeing similar behavior? Is there any changed we can flash the 4.1 wifi driver and use that instead of the new 4.2 one?

Also if anyone is wondering my wifi optimization option is disabled and wifi during sleep is set to always. Any feedback would be greatly appreciated. Thanks so much and keep up the good work MMuzzy
[Samsung Galaxy Nexus] gorillabiscuit:
I've experienced the grey bars forcing a reboot, but for the most part they just reconnect and turn blue. Have you flashed a custom kernel? I know a lot of people are having random seemingly hardware issues because they flash a custom kernel that doesn't play nice. Let me know...
[Samsung Galaxy Nexus] know8677:
Regarding wifi strength:

I've been on this ROM since it came out. Currently on the 12/30 French Vanilla version with stock kernel.

Wifi strength has been weak for me the entire time. I know this because work wifi has a 2nd level of authentication so I have to re-enter a second user id and password in the browser when it disconnects. I'll bet I notice it disconnected a half dozen times a day and have to re-login.

This never happened before moving to 4.2.1.
[Samsung Galaxy Nexus] dmillerzx:
Using the stock kernel that came with French Vanilla.
[Samsung Galaxy Nexus] 06stang:
Yup I love the new simple Nexus X logo. I made boots and splash screens for every phone I've owned with Android but never saw the need with this phone. Big demand but no motivation when it's already perfect for me.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] georgeascott:
I've not had another 4.2 ROM long enough to compare, but I have had occasional issues with the wifi not staying connected. My optimization is also disabled and WiFi sleep is set to stay on. It has never required a full reboot though. Simply toggling WiFi normally does the trick for me.

I recently set up the native internet calling for making and receiving calls and the warning is true.. Significant drain on battery (from around 14 hours or more to barely 4 hours with over 6k wake locks from the phone). It did manage to keep the WiFi awake and avoid the disconnecting issue though... I disabled the receiving option and I'm back to 15+ hours and just toggling the WiFi when it is needed.

I don't know if using the 4.1 driver would work. I would think there would be an issue since 4.2 has the optimization feature and is on by default. (I actually wish that worked.. I leave WiFi on always and could probably get a few more hours if it did what it claimed to do)
[Samsung Galaxy Nexus] 06stang:
I have automateit turn on my Wifi every weekday at 5 and off every morning at 7 and have yet to have any issues with Wifi. Working great for me at home at least.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Robin M:
Curious... In the OP, one of the features listed says " Fixed-pull-down carrier text". Someone asked a few weeks ago what that is, but AFAICS, no one ever answered. Does anyone know what that means? :confused:
[Samsung Galaxy Nexus] gorillabiscuit:
There was a time when the carrier text when pulling down your notification drawer showed CDMA-T64 or some such nonsense... now it says Verizon. Not a big deal, but a fix nonetheless.
[Samsung Galaxy Nexus] Robin M:
Yep, it says "Verizon Wireless". You're right... not a big deal. But thanks.
[Samsung Galaxy Nexus] notstevek:
I forgot to make a backup of the stock 4.2 boot animation and overwrote it with this one, and i miss the 4.2 stock nexus one, can anyone post it up, i went through the pages as i thought it was posted, I'll also re go through the addons as i think i saw it in one of their posts but if i don't edit this saying i found it please, if you can, link me, thanks.
[Samsung Galaxy Nexus] sporkette:
Stock jb boot animation

http://xdaforums.com/attachment.php?attachmentid=1162428&d=1340902771
[Samsung Galaxy Nexus] mmuzzy:
There are overlay files for each device and for some reason the Toro device overlay is missing the eri.xml file which defines what to display on the pulldown for various conditions. I just make sure it's there before I compile so it never says TCDMA-64.
[Samsung Galaxy Nexus] chukis13:
No matter how many roms I flash I always end up back here. Thanks for the great rom!