No push notifications on AOSP rom. - Nexus 5 Q&A, Help & Troubleshooting

Hello all,
I love my nexus 5 and I am trying to run an AOSP rom (tried both LiquidSmooth and CarbonRom) but for reasons unknown to me I can not get push notifications to work with apps such as Instagram, Snapchat, Twitter, and Google+ messages in hangouts. I believe these are all related to Google Cloud Messaging (GCM) for notifications.
I have tried different PA Gapps and Banks Gapps, PNF- Push Notification Fixer, different Kernels, clean installs, logging in and out of my Google Account, wiping the framework data.
I flashed a rom based on Stock and had no issues at all with notifications!!
Somebody for the love of god help me figure this out!
Thank you

Working fine here on paranoid android
Sent from my Nexus 5

Pirateghost said:
Working fine here on paranoid android
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah definitely something wrong on my end, just don't know what lol.

After being on stock rom all day and getting notifications flawlessly, I nandroided back to my liquid setup and notifications seem to be working!! Then by dirty flashing to the newest 24th build I lost notifications again. I'm forced to believe that the wiping of cache+dalvik is breaking my push notifications. Not sure why!
And yes I have tried clean installs of the Rom and it did not work.

Related

[Q] Gapps Stops Working and Persistant Activation

I just flashed my first ROM so I'm not used to this whole thing. I figured that I would have some trouble along the way.
I own a VZW GS3, now running LiquidSmooth 4.2.2. I downloaded the ROM and the gapps that they linked (I didn't install the nightly builds, just the official). However, every time I attempt to sync my contacts, gapps crashes. I haven't really found a good answer via the search bar. I need sync to work, so disabling it isn't an option (plus, half of my contacts are missing). Should I re-flash gapps, or was that not the correct version to use anyways? GooManager is saying that the latest version of gapps for this device is the "20121011" version.
Also, every time I reboot my phone, it goes into this perpetual "Activation is required". That's weird because my IMEI is fine, and I can call/text/surf once I home out of that screen. Has anyone experienced this before?
EDIT: It looks like the sync issue ONLY happens when turning on the "browser" sync option. I've disabled that for now, but I have a new problem.
My "People" app is populated will all of my contacts, however that has not transferred over to my phone's contact list (used for phone and messages). How can I get those contacts names and information moved over?
Regarding the activation on every reboot, do you live in an area with poor reception? Also it seems as that issue only happens to me on certain roms I've tried.
That is not the latest gapps package. Try flashing 20130301.
Sent from my SCH-I535 using xda app-developers app
mr_cj said:
That is not the latest gapps package. Try flashing 20130301.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That's the one I did flash.
I think I've fixed my issues. I cleared the Cache/Dalvick, flashed the new nightly, and re-cleared. That solved all the gapps problems. As for the activation issues, it still happens intermittently. I'll give Verizon a call if there are still issues.
Thanks everyone!

4.3 AOSP Dialer issues

So for some reason my phone doesn't like the dialer on every 4.3 AOSP ROM I've tried. I've been on Slim bean, Eclipse and now Liquid Smooth. I get a force close whenever I open the dialer on all these ROMs. I just Odin'd back to stock and rooted using the casual method. This hasn't happened on 4.1.2 or 4.2.2 ROMs. Something on my phone doesn't like it. I just can't figure it out. I thought going back to stock and starting from fresh would help it. Please don't ask if I dirty flash. I never do. I wipe everything a minimum of 3 times and have even wiped internal storage.
I'm using ex dialer and it works just fine. And I disabled the stock phone app. Makes me think it's a graphical issue.
Would switching kernels help?
Sent from my SCH-I535 using Tapatalk
Are you using the gapps that come with Slim? I believe that message means that the gapps package you're using is conflicted with something in the ROM or vice versa. I'm on Slim with their AIO and not having the same issue.
For example, I used to test Slim for Cordell and had the same thing happen. It happened because he forgot he had updated the gapps package he was using and I was still using the one from the site. Once I flashes the correct gapps, then the issue was solved.
I always download the correct gapps and I did so from the slim ROM website. I tried two different gapps packages from there, AIO and aroma gapps, and it still happened. This same thing happened on two other 4.3 ROMs as well, Eclipse 6.0(4.3) and LS 2.10 with the 20130813.zip gapps.
It just doesn't add up but it's still not enough of a deal breaker for me to leave 4.3 ROMs.
Sent from my SCH-I535 using Tapatalk
ExDialer is awsome, I never use the stock one anymore. I'd move on and not worry about it.
Sent from my GS3 running Pac-Man ROM 4.3 nightlies with KT747 Kernel
Sorry, not sure what it could be. Only other thing would be the kernel
So I had the issue on root box 4.2.2. I have been on this ROM before with no issues. It worked right after the initial boot up. But after I finished downloading apps from play store and a couple from my SD card is when it started not working. Pretty sure it's not rom, gapps or kernel related. If I felt like it and had the time, I'd wipe and start over but I just don't feel like doing that right now. If I ever switch to another AOSP ROM, I will try just downloading apps from the play store and seeing if that fixes it. It's just weird, that I removed all apps installed from my SD card and it still won't work. I install all of the same apps on tw ROMs and have never had these problems. Oh well. I will stick with ex dialer.
Sent from my SCH-I535 using Tapatalk
Wow! That was easier than I thought. I was using Super Backup and restoring my call logs across different ROMs. This is what was causing my dialer app to crash. All I did was go into the dialer app settings and looked at the permissions for the app and it just came to me. Maybe if I clear my call log it will work. So I did and immediately it worked. Didn't even have to reboot. Such a relief to know that the problems weren't with the ROM.
Sent from my SCH-I535 using Tapatalk

Google Dialer Force Close

I am on the Elix-R Rom and after a few days the Google Dialer force closes on me. I flashed only that particular Gapp with Elix-R. I noticed this same thing happened when using the Paranoid Android Rom as well. I have tried re-flashing, changing kernels, updating TWRP, flashing the dialer again and nothing. Does anyone know why this might happen?
Maybe you need more gapps to enable it to work. Try flashing full gapps first
Sent from my Nexus 5 using Tapatalk

Slimkat apps won't invert?

I've had the latest stable slimkat ROM, with slim gapps installed. When I turn darkslim on in settings none of the apps will invert. Tried weekly ROM and gapps, same problem. Not sure when this started happening, but it did work roughly a month or more ago. Tried a clean install, same. Tried both dalvik and art, same. Nothing I do results in inverted apps. Any suggestions?
Does slimkat actually invert gapps? Not sure if it does, cause it doesn't for me.
Try flashing an inverted gapps.
wangdaning said:
Does slimkat actually invert gapps? Not sure if it does, cause it doesn't for me.
Try flashing an inverted gapps.
Click to expand...
Click to collapse
Yes it does, its called TRDS and it's always worked for me with the latest slim gapps.
FYI Gmail hasn't been invertable for a while and now nor is play store as of yet
I used to have inverted Google now, but not anymore
sketron13 said:
I used to have inverted Google now, but not anymore
Click to expand...
Click to collapse
The problem is google are in the process of updating all their apps to the material design. Google now / search oesn't invert either i believe. You can go back to an older gapps but you'll be pushed updates via play.
There is actually a slim gapps thread:
http://forum.xda-developers.com/slimroms/general/gapps-official-slim-gapps-trds-slimkat-t2792842
Okay, I saw the thread but didn't see this mentioned. Thanks for the explanation, I'll try to search a little harder next time
Haha. For once I wasn't suggesting someone use search ;]
Sent from my Nexus 5 using Tapatalk

XT1033 Falcon CM12 (31/01) - Cannot send/receive sms - 3G, MMS, in/out calls fine!

Hey all. I really hoped I would have sorted this just by searching but... still stuck.
I have an XT1033, which I updated from cm11 > cm12 falcon (31/01 nightly) using TWRP 2.8.1. Gapps mini modular package from PA link. From my forum searching etc I thought the XT1033 dual sim was now all good to go on the falcon nightlies but since the update I havent been able to send or recieve any sms although 3g data, incoming and outgoing calls and MMS are all fine. Below are some things I have tried.
Sim card has been tested to send and receive fine in another phone.
MMS is working fine and all APN settings have been double checked.
I've tried using the *#*#4635#*#* menu to see if the SMSC number was the problem. Confirmed it was correct.
I tried flashing again using CWM as well with the same result. Also tried again with TWRP, this time formatting (almost) everything, data, system, data/media, dalvik, regular cache etc. Tried flashing a falcon nightly from 27/01 as well to see if it worked.
It looks like this problem has occurred for a couple of XT1033 owners upgrading recently to CM12 but I'm not sure if anybody has worked out where the issue is?? If anyone has any troubleshooting ideas, suggestions etc... Thanks in advance.
:good: and thanks to the CM devs, contributors etc. (And google I suppose). Im really loving Lollipop, the material ui and all the usual CM tweaks, the rom is friggin sweet otherwise. From a long time lurker/searcher of xde who usually finds my q already answered.
Sms not working
3down2togo said:
hey all. I really hoped i would have sorted this just by searching but... Still stuck.
I have an xt1033, which i updated from cm11 > cm12 falcon (31/01 nightly) using twrp 2.8.1. Gapps mini modular package from pa link. From my forum searching etc i thought the xt1033 dual sim was now all good to go on the falcon nightlies but since the update i havent been able to send or recieve any sms although 3g data, incoming and outgoing calls and mms are all fine. Below are some things i have tried.
Sim card has been tested to send and receive fine in another phone.
Mms is working fine and all apn settings have been double checked.
I've tried using the *#*#4635#*#* menu to see if the smsc number was the problem. Confirmed it was correct.
I tried flashing again using cwm as well with the same result. Also tried again with twrp, this time formatting (almost) everything, data, system, data/media, dalvik, regular cache etc. Tried flashing a falcon nightly from 27/01 as well to see if it worked.
It looks like this problem has occurred for a couple of xt1033 owners upgrading recently to cm12 but i'm not sure if anybody has worked out where the issue is?? If anyone has any troubleshooting ideas, suggestions etc... Thanks in advance.
:good: And thanks to the cm devs, contributors etc. (and google i suppose). Im really loving lollipop, the material ui and all the usual cm tweaks, the rom is friggin sweet otherwise. From a long time lurker/searcher of xde who usually finds my q already answered.
Click to expand...
Click to collapse
same issue for me... Sms not working on any custom roms... Pls help
Not the answer you are probably wanting to hear but I have a similar problem just a different model phone. Use a 3rd party app that lets you manually set the apn. EvolveSMS or Smitten both let you do just that and are pretty nice apps as well.
Thanks for the reply
n0ts0smart said:
Not the answer you are probably wanting to hear but I have a similar problem just a different model phone. Use a 3rd party app that lets you manually set the apn. EvolveSMS or Smitten both let you do just that and are pretty nice apps as well.
Click to expand...
Click to collapse
THANKS FOR THE REPLY DEAR FRIEND.. BUT I INSTALLED SO MANY 3RD PARTY APPS LIKE TEXTRA SMS, GOSMS ETC. BUT IT DIDN'T FIX MY PROBLEM... :crying:

Categories

Resources