this might seem like something stupid but all of a sudden the enhanced features or rcs in android messenger stopped working. when i go into the setting it brings up the opt in screen, does the circle and gives me the check like everything is ok. but it doesnt work. when i go back in all it continues to do is give me the opt in screen never giving me the actual options of the features. it has worked for me since it rolled out. nothing has changed with my setup, i am unrooted. anyone else run into this? i have tried clearing cache, data, force stopping, restarting, uninstalling and reinstalling and even updating profile. so strange but this is a feature i really liked. any help is appreciated.
thanks
Just stumbled across your post from a Google search as I am having the same issue on my Galaxy S6 on Sprint (which like you, was indeed working previously) and my brand new Sprint LG G6. On both, anytime I tap on the enhanced features in the settings it brings up that blue opt in screen, gives me a nice check mark, but I still can't get in there anymore to change the settings or verify it is working. I've tried all sorts of combinations of the Messenger app and Carrier Services to no success. If you managed to resolve this, please let me know!
Mine was working on my note 4 but it does not work on my Galaxy S8 plus. Did you guys ever resolve this? Mine never even gives the checkbox it just stays on the Excuse the wait Messages will let you know when this is complete.....
xPhrostx said:
Mine was working on my note 4 but it does not work on my Galaxy S8 plus. Did you guys ever resolve this? Mine never even gives the checkbox it just stays on the Excuse the wait Messages will let you know when this is complete.....
Click to expand...
Click to collapse
I've got the exact same problem. Have you found a solution?
Ditto on my S8. @xPhrostx or @Stanleywinthrop ... did either of you ever end up having any success?
Oddly enough, it worked fine on my dad's S3!!!
Related
Im using a Samsung Focus bought from Rogers but using with Fido. It's NOT unlocked however, but works though.
I heard that MMS wont work if I use Rogers phone on Fido, and that's true, it doesnt.
But I have 2 other problems, and Im not sure if they are my Samsung Focus' problem or a Window Phone problem.
1) I tried the group chat feature for the first time a few weeks ago and turns out it doesnt work! When I try it out, it tells me there has been an error or something.
2) I noticed that when I go to the original Marketplace app, it doesn't show the updates for my apps. I remember it did before and it updated all my apps, but last month I found out some of the apps I had have been updated but yet the Marketplace doesnt tell me that and I have no idea how to update them. I have a lot of apps and I don't want to go through each one of them to see if they have updates and then reinstall; that would be terribly tedious.
So does anyone else have one of these 2 problems and does anyone know how I could fix them?
Thank you!
ETA: also just for your information, my Focus has the latest update I believe. the 7740 version
MMS works on ATT if you run att connection setup. Does samsung have something similar for rodgers?
updates should work... what if you use wifi?
Maybe something has them hung up along the way. hard reset to fix it?
ROCOAFZ said:
MMS works on ATT if you run att connection setup. Does samsung have something similar for rodgers?
updates should work... what if you use wifi?
Maybe something has them hung up along the way. hard reset to fix it?
Click to expand...
Click to collapse
I dont mind not having MMS. I dont use data, I only use wifi. Yea, so far, it seems like the only way to fix the app update problem is by resetting the phone. But i still dont know whats causing the group chat to not work; and yes, I did turn group chat on in the settings.
thanks for the reply
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.
Hey guys. Ia anyone having any issues with background data? I don't get push Notifications When im not on WiFi. Even when I'm on WiFi, my screen needs to be on to retrieve them. I've tried toggling the background data setting on and off. Music seems to work fine though, streaming. Tried prl and profile updates and even hard reset. I also installed the software update. anyone else having the same issue? Ia there a setting I'm missing?
Tyia
I have something similar, it seems to update but only when it wants to. Specifically with some apps data works only when on WiFi. For Example Google Play Music takes forever (I mean 10 minutes to load one song) to load songs on Sprints Network, but it is immediate on WiFi. Same thing with Facebook App, it will take 15-20 minutes to load data when in Sprint Network. As soon as I connect to WiFi it works immediately. Other apps work great, others don't.
Had the same issue. Sprint told me to do the ##72786# trick. Seems to work so far.
skinneejay said:
Had the same issue. Sprint told me to do the ##72786# trick. Seems to work so far.
Click to expand...
Click to collapse
Grrrr i don't get it. I tried that, still a no go. Google play music, google wallet and hangouts don't work period on lte. But voice search and the google app works just fine. No push Notifications on anything except on gmail for some reason. So frustrating, i don't get email notifications for work which is bad. I blame sprint's software team because my sprint note 4 and the s6 on verizon and att have no such issues.
I also posted a thread describing the same issues. All i know is sprint bette be working thier asses off on this because this is ridiculous i miss my gvoice txt for work because of this. If a customer cant txt me than i lose money. And im blaming sprint right now
Not to mention that the workaround is to use wifi. To use wifi!! Did they forget that there is also a major bug with wifi draining the phone like crazy as well. Pretty messed up
I've got the issue back again. I'm going to best buy to return. My wife's white phone is working perfect. Do you guys have the black version?
White, im outside of my 14 days. I have the white.
It works! Out of nowhere today , all of the issues are gone !
Guys please contact your carrier and samsung this is a bug affecting a lot of phones. I'm on the 4th and it is still an issue. The first 2 were black 64gig models and the last 2 are gold 64gig models.
http://forum.xda-developers.com/gal...s-stop-screen-off-t3071248/page4#post60888131
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
I have no idea when calling functionality begins to be lost because I can still send and receive texts, but I can't make or receive calls. I don't even get a wave of missed calls or anything when it works after a reboot.
Google Assistant has it's own issues when this happens too. It won't come up with "Hey, Google" at all. When I long press the home button, Google Assistant comes up, but I just get the floating dots. Fortunately, it doesn't freeze when I try this. Restart the phone and I'm good for about 10 minutes or so. I tried installing 3rd party calling apps, but the problem persists.
Hoping this is a Pie issue and waiting for the next security patch, will likely do a sideload flash-all. Any suggestions as to what the problem is from? Could my SIM card be the problem? Any apps I could try to help narrow down the issue? I had no issues with Oreo.
Thanks in advance.
Tried rebooting in safe mode. Slightly similar results: works fine for about 10 minutes but then it's just the mic not working. I can make and receive calls with out the phone freezing, but no mic.
mbstone said:
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
Click to expand...
Click to collapse
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, with everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (a few days later, rarely get/make calls). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
After continued issues I parked phone in drawer a bit then pulled out and tinkered with a few weeks later. Tried to isolate problem using logcat and on a hunch I flashed TWRP and a custom ROM but NOT any gapps package. Sticking sim in and using the built in phone app (Resurrection Remix -com.android.dialer) it works without issue. What? I flashed gapps (correct version/etc) and sure enough the problem returned. Went back to rom minus gapps, works fine. So, with straight up stock rom - stock phone dialer fails, custom rom - it works without a gapps package but not with.
Aimless Rambler said:
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (about 5 days later). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
Click to expand...
Click to collapse
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
brkshr said:
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
Click to expand...
Click to collapse
AT&T
---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------
mbstone said:
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Click to expand...
Click to collapse
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
See my updated post (# 3) for what I've tried since..
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
brkshr said:
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
Click to expand...
Click to collapse
Older/newer phone dialer apps didn't work for me either ... custom rom and eliminating google play services did (no gapps). I'm still tinkering with the device ... installing frequently used apps using F-droid and Yalp, will test it. Not quite sure why but it works.
I ended up flashing Lineageos for Microg, presents it's own problems in the learning experience but it works.
Nothing ever worked in the end. No, not with Verizon. Bought through Canadian carrier called Fido.
Called Google tech and they weren't overly helpful. I started a chat with a Google Tech and they suggested I take it to UBreakIFix. They did a free diagnostic test and I referenced https://support.google.com/pixelphone/forum/AAAAb4-OgUsIW_gxTpXX3s/?hl=by that thread. Said they'd fix it for free even thought I was out of warranty. Got a new motherboard and my phone works like a charm.
Recently on my Note 10+ (SM-N975U1) running stock Pie and Dec 1 2019 update, I have been experience 2 issues.
Notifications for some apps are delayed
App updates hang on Google Play Store
For the app updates, they stall with "Download Pending" or the download stalls with <100% complete.
Resolution steps that have NOT worked
Clearing cache and data for Google Play Store
Rebooting phone
Rebooting into Safe Mode
Changing from Wifi to Cell Network Data and vice versa
Stop/starting app updates
Current Workaround
Closing/swiping the Google Play Store and opening it again. It will eventually complete downloading after multiple attempts and install/update an app - you will have to repeat this continuously for every app you want to install or update.
Is there anyway to debug this without doing a complete reset?
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
mtweisenbarger777 said:
This is a problem I've had on many phones over the last few years. It took me a while to figure it out but it's bluetooth related. More specifically, I had the "Dynamic Lock" option enabled on my Windows 10 work laptop (which basically just locks my pc when my phone gets far enough away). I disabled this and now all my notifications come immediately and play store updates work as they should. I realize that you may not have that enabled and if that is the case then turn off your bluetooth for a while and see what happens. It worked for me and several others on the samsung community forum.
Click to expand...
Click to collapse
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
selector said:
Thank you! I turned off Bluetooth but nothing happened but after I rebooted with Bluetooth off everything started to work again. Is there a permanent fix for this? I am assuming turning back on Bluetooth will cause this to happen again? The strange thing this never happened to my Note 8.
Click to expand...
Click to collapse
I have no idea why this happens. What I do know I have had this issue on LG phones, Pixels, and Motorola's. It isn't a Samsung thing. I think it's an Android Bluetooth issue.
This is an old thread - but in case someone else finds it, I came across someone's suspicions in another thread that their Plantronics headset was causing some kind of problem with their Bluetooth. I began unplugging my Savi headset when not in use and it seems to help... YMMV.
This has been going on since Pie; made me upgrade from my Note 8 to Note 10 and it came right back. Infuriating.
You may also want to try to rub a lucky stone and do some chanting as well, because it's about as effective as hoping for a fix after all this time.