guys, please help me out, whenever I touch a notification, nothing happens, in facebook for android app, It worked perfectly till 2 days ago but now, since I don't have my PC, it is disturbing me a lot.
I have this issue too (similar)
Honestly, the only push notifications I ever see from fb are messages, and when I try to click it, nothing happens.
I don't know how but they started working on their own again, maybe it was a temporary problem at facebook's server
I can't remember the last time I had a facebook notification. I've got notifications enabled but haven't seen any for a very long time, I just assumed it stopped working since Facebook Messenger was released
try and see if you get same problem with 3g or wifi. I had same problem but with 3g only and that is because it can take longer to load.
They stopped working for a while for me too but now they seem to be back. I haven't ever counted on them working because it's always been pretty spotty
Same error here
Maybe it's going to be a update with facebook app.
I get those notifications too and they are anoying.
It just about time to wait an update from FB devs.
Tidane said:
It just about time to wait an update from FB devs.
Click to expand...
Click to collapse
If they were to ever put any actual care into their Android app... :/
Notifications for Facebook never seem to work. I have tried to unistall/reinstall, turn notifications off then back on, doesn't matter. They really need an overhaul of the app!
Yeah i had problems getting the notifications to work on android 2.3.6 on my note. They opened about half the time. I'm trying out ICS now and hopefully it'll work better!
Guys, Im on ICS resurrection remix for a time now, and the bugs you refer are still there, to me the app's faulty. Its only useful when you want to share a photo
is better use a web browser alternative
has been happening to me for the past few weeks. doesn't always happen though, more like randomly
Hey guys,
This is my first post, and I would greatly appreciate some help. I'm clearly quite a rookie at this. But I rooted my Verizon gs3 quite some time ago, and everything has run smoothly since. I did use it while in the UK on GiffGaff Mobile, and still worked fine. Now I am using Simple Mobile.
Just today, I installed the CyanogenMod 11 KitKat. I am able to send & receive MMS. And I can receive SMS, but I cannot send SMS.
I have tried changing the SMSC number using the dialer, but it keeps reverting back to "+12063130004",145 . I have also tried using different SMSC codes using the GoSMS app. I've played around with the APNs as well, but from the little that I know about this, this only has to do with MMS not SMS, correct?
Don't know what else to do, and I can't find any threads that have helped me yet.
PLEASE help, and I would greatly appreciate it.
amber12129 said:
Hey guys,
This is my first post, and I would greatly appreciate some help. I'm clearly quite a rookie at this. But I rooted my Verizon gs3 quite some time ago, and everything has run smoothly since. I did use it while in the UK on GiffGaff Mobile, and still worked fine. Now I am using Simple Mobile.
Just today, I installed the CyanogenMod 11 KitKat. I am able to send & receive MMS. And I can receive SMS, but I cannot send SMS.
I have tried changing the SMSC number using the dialer, but it keeps reverting back to "+12063130004",145 . I have also tried using different SMSC codes using the GoSMS app. I've played around with the APNs as well, but from the little that I know about this, this only has to do with MMS not SMS, correct?
Don't know what else to do, and I can't find any threads that have helped me yet.
PLEASE help, and I would greatly appreciate it.
Click to expand...
Click to collapse
If you toggle airplane mode or reboot the phone can you send an SMS? I haven't played with my phone at all lately but suddenly similar symptoms have manifested. I can send 1 SMS every time I reboot, but then it stops sending SMS after that one. Is this true with you? I haven't found a fix yet, but I'm trying to flush out the problem completely.
Whisk_33 said:
If you toggle airplane mode or reboot the phone can you send an SMS? I haven't played with my phone at all lately but suddenly similar symptoms have manifested. I can send 1 SMS every time I reboot, but then it stops sending SMS after that one. Is this true with you? I haven't found a fix yet, but I'm trying to flush out the problem completely.
Click to expand...
Click to collapse
I figured it out!! Finally! I had the same issue - I was able to send one message, then suddenly nothing. Do you have Google Voice+ ?? If so, try disabling it. You cannot disable it through the Settings>Apps - you actually have to go into the App then and select disable.
amber12129 said:
I figured it out!! Finally! I had the same issue - I was able to send one message, then suddenly nothing. Do you have Google Voice+ ?? If so, try disabling it. You cannot disable it through the Settings>Apps - you actually have to go into the App then and select disable.
Click to expand...
Click to collapse
I don't see "Google Voice+" Are you referring to Google+ or a different app altogether? This is driving me mad.
mtemlm satisfy
Whisk_33 said:
I don't see "Google Voice+" Are you referring to Google+ or a different app altogether? This is driving me mad.
Click to expand...
Click to collapse
Its just called Voice+. I know, I spent hours trying to sort it out. Other than that and messing around with the SMSC number, I'm not sure what else would be the problem.
amber12129 said:
Its just called Voice+. I know, I spent hours trying to sort it out. Other than that and messing around with the SMSC number, I'm not sure what else would be the problem.
Click to expand...
Click to collapse
So what do you mean by go into the app? if I press menu> manage apps, and then under the tab "All" at the bottom there is a "Voice+". I'm on CM10.2 and it appears that the "Voice+" is part of CM. If I open my app drawer and scroll down there is no app called Voice+.
There is Voice Dialer and Voice Search, but nothing else in the app drawer with a similar name. If I'm not going down the correct path please let me know. Thank you.
Whisk_33 said:
So what do you mean by go into the app? if I press menu> manage apps, and then under the tab "All" at the bottom there is a "Voice+". I'm on CM10.2 and it appears that the "Voice+" is part of CM. If I open my app drawer and scroll down there is no app called Voice+.
There is Voice Dialer and Voice Search, but nothing else in the app drawer with a similar name. If I'm not going down the correct path please let me know. Thank you.
Click to expand...
Click to collapse
Hmm, that's odd that its not showing up in the app drawer. It should be. Do you use Google Voice at all? On my phone, the option to disable or uninstall is blocked when I go into Settings>Apps. But if you don't use the app and your phone allows you to, maybe try disabling and/or uninstalling from there?? Let me know, and I'll keep looking.
amber12129 said:
Hmm, that's odd that its not showing up in the app drawer. It should be. Do you use Google Voice at all? On my phone, the option to disable or uninstall is blocked when I go into Settings>Apps. But if you don't use the app and your phone allows you to, maybe try disabling and/or uninstalling from there?? Let me know, and I'll keep looking.
Click to expand...
Click to collapse
So, I have the option to force stop it. (no change in results).
I've even downloaded the "Google Voice" app, which added the "Voice+" app, opened it, confirmed that it was on disable and still no change.
I have no idea why this problem started this morning since I don't believe I am any changes to my phone the past couple days... I really don't know what information I can provide to help troubleshoot it...
I'm having the same exact problem starting this morning. I can send exactly one message and then I have to reboot or turn airplane mode on/off to send another. Everything was working perfectly fine yesterday, though. I've tried deleting my phone's cache in the recovery menu but it hasn't helped.
thezam said:
I'm having the same exact problem starting this morning. I can send exactly one message and then I have to reboot or turn airplane mode on/off to send another. Everything was working perfectly fine yesterday, though. I've tried deleting my phone's cache in the recovery menu but it hasn't helped.
Click to expand...
Click to collapse
Are you also on CM11? What is your carrier? I've done a factory reset and upgraded from CM10.2 to CM11 and still haven't been able to ride my self from the problem. Nothing I have tried has changed anything. I made a new thread since it seems that the original purpose of this thread has been answered via the disabling of Voice+. The new thread is http://forum.xda-developers.com/showthread.php?t=2657822
Whisk_33 said:
Are you also on CM11? What is your carrier? I've done a factory reset and upgraded from CM10.2 to CM11 and still haven't been able to ride my self from the problem. Nothing I have tried has changed anything. I made a new thread since it seems that the original purpose of this thread has been answered via the disabling of Voice+. The new thread is http://forum.xda-developers.com/showthread.php?t=2657822
Click to expand...
Click to collapse
Carrier: Verizon. I was initially on CM 10.2 but both rolled back to CM 10.1 and upgraded to CM 11 to see if any of those fixed the problem. Neither did and I reluctantly (for now at least) went back to stock and unrooted my phone. Texting is working fine but I absolutely hate TouchWiz. I have no idea what could have caused the issue and, like you, I didn't make any changes at all before it happened. It literally appeared out of the blue.
thezam said:
Carrier: Verizon. I was initially on CM 10.2 but both rolled back to CM 10.1 and upgraded to CM 11 to see if any of those fixed the problem. Neither did and I reluctantly (for now at least) went back to stock and unrooted my phone. Texting is working fine but I absolutely hate TouchWiz. I have no idea what could have caused the issue and, like you, I didn't make any changes at all before it happened. It literally appeared out of the blue.
Click to expand...
Click to collapse
A bunch of us on S4s seem to be having the same problem! The timing of this issue all happening at once is weird... http://forum.xda-developers.com/showthread.php?p=50552025
OK this really does seem to work for me as a temp workaround...it sticks through reboots and all. Go to the dialer and enter the trusty old *#*#4636#*#* then go to phone settings and change preferred network type to CDMA only then back out and reboot.
It kinda sucks cause it's slow on the go, but at least I can send texts reliably. I have WiFi most places I am anyway.
If anyone figures out a real long term fix please post!!!
amber12129 said:
Hey guys,
This is my first post, and I would greatly appreciate some help. I'm clearly quite a rookie at this. But I rooted my Verizon gs3 quite some time ago, and everything has run smoothly since. I did use it while in the UK on GiffGaff Mobile, and still worked fine. Now I am using Simple Mobile.
Just today, I installed the CyanogenMod 11 KitKat. I am able to send & receive MMS. And I can receive SMS, but I cannot send SMS.
I have tried changing the SMSC number using the dialer, but it keeps reverting back to "+12063130004",145 . I have also tried using different SMSC codes using the GoSMS app. I've played around with the APNs as well, but from the little that I know about this, this only has to do with MMS not SMS, correct?
Don't know what else to do, and I can't find any threads that have helped me yet.
PLEASE help, and I would greatly appreciate it.
Click to expand...
Click to collapse
i just installed cm 11 yesterday and i am having same problem you have, i am on simple mobile too please what did you do, to fix it, thank in advance...
gagnier27 said:
i just installed cm 11 yesterday and i am having same problem you have, i am on simple mobile too please what did you do, to fix it, thank in advance...
Click to expand...
Click to collapse
sorry for such a late response. I solved this by just disabling Google Voice+. It is just called Voice+ in the app drawer, and when you open it, just tap 'Disable' & reboot the device.
amber12129 said:
sorry for such a late response. I solved this by just disabling Google Voice+. It is just called Voice+ in the app drawer, and when you open it, just tap 'Disable' & reboot the device.
Click to expand...
Click to collapse
Some people don't have voice+ and the solution you used isn't an option for them.
For those of us less fortunate than you, It seems you can fix the problem by loading a TW ROM and flashing the MB1 firmware. Then you can return to CM
I had XVoice+ for Exposed on my SGS4, it stopped me from sending texts. It was ok when i uninstalled it. I hope that might help.
Hi all. I recently updated the software to 38R and noticed that forward lookup no longer works on the dialer. I've got the setting ticked and the lookup provider is still Google but nothing works.
Is anyone else having this problem?
I have the same issue. I changed the provider but still it won't lookup nearby business phone numbers. Even the reverse lookup is not performing
I hope it gets patched.
Sorry for the bump but has anyone found a way to solve this? It doesn't work with the CM12 Dialer App either and I really miss this functionality from the Stock Google Dialer found on my Nexus 5. I've tried a lot of different ways to get the Google Dialer 2.0 APK working on CM12 including trying to deodex the apk and then building a version of CM12 with odexing enabled and everything just resulted in the dialer force closing, so I'm at a loss here.
EDIT: Well... I did all of that... just to find out my issue with Forward Lookup was that somehow my location services managed to turn itself off. Turned it on and it works now. I feel like a fool but I'll leave this here in case anyone else is having similar troubles.
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Flash something else more stable that better suits your needs for now. This rom is still a work in progress. There will be a few hiccups from time to time. Wait for the next update
Sent from my SAMSUNG-SM-G890A
M7mD.Sa3eD said:
After last update ( Build cm-13.0-20160110-UNOFFICIAL-skyrocket ) i can't make calls
the device reboots when i do this and this problem was in ( Build cm-13.0-20151219-UNOFFICIAL-skyrocket )
so what i can do ??!
Click to expand...
Click to collapse
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.
spacebar208 said:
Yeah me too, I'm in the process of sending logs to developer. So I went back to 20151222 until problem analysed/resolved.
Click to expand...
Click to collapse
I'm on 20151222 right now until the problem be solve
Sent from my SGH-I727 using Tapatalk
Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/
Cyanogen Mod is dead
dimapoter said:
Bumping the **** outta this. Same issue on a build one year later (Cm13 Oct 01/2016 Celox). Contacts and phone stopped working. So I replaced them with Google's AOSP variants from the play store. At that point, the phone reboots when I try to call. The 3g works wtf...
Edit:
Yes, this was sent from my SGH-I727R by I'd rather be making calls with this. Also, incoming calls work. Just outgoing is the issue. Can't be my radio, right? Cm11 or 10 whatever it was worked flawlessly on the same one.
Edit2:
Ok, so after jerking around the apps, disabling/re-enabling the system dialer, etc., I received a call from my friend. At the point, all four soft keys stopped working while the calling issue completely fixed itself. After a reboot, the soft keys and the calling work flawlessly 0.0
Typical Android issues...
Although my friend is complaining about some beeping noise coming from my end during a call. Will look into it.
So current fix (for now): disable/re-enable the inbuilt contacts and dialer apps, reboot, enable them, clear their data, cache, whatever it takes, etc. Keep doing so until it magically fixes itself. Maybe try getting a buddy to call you and pick up. That is all I can think of in order to reproduce such weirdness :/
Click to expand...
Click to collapse
I don't think anything will really work in cm now because it's now discontinued and function will not work Cyanogen Account, etc. I also think it's modems stopped working... see here:Click Here
Hi everyone,
For those of you whom are using GV as their primary phone number, you certainly noticed that the phone dialer doesn't work when Google Voice is set to initiate your calls
I thought that the problem would be fixed in no time, but I was wrong. So I decided to give CM13 a chance and everything worked as expected. Great, GV works, my phone works, everything is beautiful.
Except that I got so much used to MIUI7 that I found CM to be very limited.... not to mention that the battery was draining much faster under CM than it was under MIUI.
I went back to my previous system and decided to put a cross on GV... not really a big deal. But I was wondering if this problem could come from a dialer not able to use GV app... hence my question:
Is there an alternative dialer that could be used under MIUI which would "force" GV to work again?
Please don't tell me that Hangouts works just as well, I hate it badly...
Thanks a lot for your help and suggestions.