Related
for those of you that dont know video share does not work on the htc fuze it your settings say wap.cingular. att has tried to fix this with no success still waiting on a call back from them. we know that the settings should say ims.cingular butmanually changing it does not work it has to come from htc like that. so it anyone has any suggestion please post. and yes i do have the service from att and it works on other video share phones.
I have had alot of issues with differant devices and VIDEO SHARE, to that i will say this; have them remove the soc code(feature) and then add it back to the account after a soft reset on your device. This has been the process that has corrected mine for many of my devices.
Any relief on this? curious if it is the ROM I am using or if it really isnt working.
iceberg1824 said:
for those of you that dont know video share does not work on the htc fuze it your settings say wap.cingular. att has tried to fix this with no success still waiting on a call back from them. we know that the settings should say ims.cingular butmanually changing it does not work it has to come from htc like that. so it anyone has any suggestion please post. and yes i do have the service from att and it works on other video share phones.
Click to expand...
Click to collapse
strangely my phone sometimes says ims.cingular and I cannot connect and it asks for a password on boot up. Most of the time it is wap.cingular. Weird...
As for videoshare, you have to be on a 3g (H) connection to stream data and talk at the same time. I haven't tried the videoshare, but I will test and see what I get....any other ideas?
Video Share Checklist
I just thought I'd share my experience with getting Video Share to work properly on the FUZE (and on my LG VU) So here it is:
Checklist
3G Service Area: you (and the other party) MUST be in a 3g service area, with at least 2 bars, why 2 bars you ask? well, quality of service mainly, less than 2 bars and your 3G will be very slow, remember you're trying to transmit alot of data with Video share.
A Data Plan: This was a shock, but not really... if you don't want to be charged for every KB of data sent / received in addition to the 35 cents per minute pay per use or whichever plan you have, you must have a good data plan to cover the charges... I don't understand why AT&T feels they must double charge, once for the feature and then for the data to use that feature, MMS Messages do the same... if they charge a high rate for MMS, you shouldnt be charged for the associated DATA, what a rip!
Video Share PPU, Starter, or Premium service (the service itself) -- not much to say but DUH, also the receiver must have this service and an appropriate data plan as mentioned above or you will never see the option on your phone during a call.
IMS APN Feature: (FREE) Although the guy I finally got a hold of to make this all work (who had a thick accent and was hard to understand, but knew what he was doing) told me that video share will work with wap.cingular, there have been reports that it doesn't. When you provision Video share the network automatically changes your APN to ims.cingular, IMS APN feature must be on your account for access or it could give you all sorts of problems form "forbidden" on browsing to rejected emails/mms. If you have a 3G phone this is most likely on your account, it is the new higher speed apn for 3G, maybe that's why the internal customer service code for it is "3GMM" hmm....
Correct settings in your phone: I'm not going to go into those details here, but its obvious, you must have the correct settings.
Correct IMEI: Here's the fun one, I had tried everything above as mentioned in scattered posts throughout the net only to call at&t several times getting frustrated over not getting any results, the final time I called them I ended up talking to some guy in a "special department" related to video share issues. After reviewing all settings on my account he finally figured out the problem (which took him about 2 minutes after getting transfered) the IMEI numbers for my phones were not listed in the system. (blame the dealer I bought the phones from as they are supposed to enter this) there are several places the IMEI's get listed, and I'd think they could easily pluck this information from the network when the phone registers but no, I read him my IMEI information from both lines on my account that video share didn't work for (the FUZE and the VU), he had us remove the batteries as he sent the updates across the network, and BAM the very next call between the phones and video share works like a champ. What this boiled down to is the network didn't know what type of phone I had and what features to turn on and what to do to make the phones talk to each other in a compatible form. I'd think this would cause all sorts of other issues with the network too, not just for video share.
A final note on this: if you change phones, make sure you call and have the IMEI information updated, if I change my FUZE for another FUZE it would probably work, but if I swap the device out for a different model it would not necessarily pick the most compatible features for my phone...
Privisioned Dates: When you go to your online account management and add features, it says they are immediately effective, sometimes this is true, but in the case of my account it likes to post-date to the next bill cycle. This is especially true when you visit an AT&T store, it will definitely post-date there. I had 3 IMS APN features and Video Share features on my account, all with different dates, this is because, I tried to add and 2 people at the store tried to add, to make sure Video Share and IMS are on your account and active / effective TODAY you have no choice but to call customer service and tell them you want them on your account effective immediately. While it will appear on your account management that you have it, don't trust it as it only checks for the feature, not the active dates.
And finally the internet connection: Some people have noted that your connection must be active before the call, this is not true although it is very helpful. The video share negotiation takes place over the phone control channel, when it is determined that you both have the service and compatible phones it will send a message to both phones. They will then try to turn on their data connections and verify with the server whether or not the option should be turned on. If your data is active before the call your video share button will be available instantly as it is for me. If it is NOT then it will take ~20 seconds or more to connect to the net and contact the server to verify, then turn on the option for you. Just make sure your internet works in general and that you can connect and you should have no problems during a normal call.
I hope this helps at least some of the people out there having this issue, and maybe some others having other issues with the network. Sorry for the long post
vs is ok now
OK this is a miracle finally got my HTC fuze to do video share. When I started this thread I was so mad at ATT and htc. Well here is the deal I had tried just about every avenue to get this to work and after reading whitehawk82 post, one of his points stood out.
FIRST make sure you have the latest sim card from ATT and IMS APN Feature is activated, now be aware that ATT needs to reset your entire data service so the ims.cingular can kick in on the ATT fuze. To make sure this is working when you turn on your fuze it will automatically connect to ims.cingular as with all video share phones.
SECOND now that you are connected you would think it would work, well not quite that easy. Now you need to re-install original ATT fuze rom and finally when you go to contacts live video share call will no longer be grayed out. Put back all your info manually for best results sprite restore may put back some incorrect settings.
whitehawk82 said:
I just thought I'd share my experience with getting Video Share to work properly on the FUZE (and on my LG VU) So here it is:
Checklist
3G Service Area: you (and the other party) MUST be in a 3g service area, with at least 2 bars, why 2 bars you ask? well, quality of service mainly, less than 2 bars and your 3G will be very slow, remember you're trying to transmit alot of data with Video share.
A Data Plan: This was a shock, but not really... if you don't want to be charged for every KB of data sent / received in addition to the 35 cents per minute pay per use or whichever plan you have, you must have a good data plan to cover the charges... I don't understand why AT&T feels they must double charge, once for the feature and then for the data to use that feature, MMS Messages do the same... if they charge a high rate for MMS, you shouldnt be charged for the associated DATA, what a rip!
Video Share PPU, Starter, or Premium service (the service itself) -- not much to say but DUH, also the receiver must have this service and an appropriate data plan as mentioned above or you will never see the option on your phone during a call.
IMS APN Feature: (FREE) Although the guy I finally got a hold of to make this all work (who had a thick accent and was hard to understand, but knew what he was doing) told me that video share will work with wap.cingular, there have been reports that it doesn't. When you provision Video share the network automatically changes your APN to ims.cingular, IMS APN feature must be on your account for access or it could give you all sorts of problems form "forbidden" on browsing to rejected emails/mms. If you have a 3G phone this is most likely on your account, it is the new higher speed apn for 3G, maybe that's why the internal customer service code for it is "3GMM" hmm....
Correct settings in your phone: I'm not going to go into those details here, but its obvious, you must have the correct settings.
Correct IMEI: Here's the fun one, I had tried everything above as mentioned in scattered posts throughout the net only to call at&t several times getting frustrated over not getting any results, the final time I called them I ended up talking to some guy in a "special department" related to video share issues. After reviewing all settings on my account he finally figured out the problem (which took him about 2 minutes after getting transfered) the IMEI numbers for my phones were not listed in the system. (blame the dealer I bought the phones from as they are supposed to enter this) there are several places the IMEI's get listed, and I'd think they could easily pluck this information from the network when the phone registers but no, I read him my IMEI information from both lines on my account that video share didn't work for (the FUZE and the VU), he had us remove the batteries as he sent the updates across the network, and BAM the very next call between the phones and video share works like a champ. What this boiled down to is the network didn't know what type of phone I had and what features to turn on and what to do to make the phones talk to each other in a compatible form. I'd think this would cause all sorts of other issues with the network too, not just for video share.
A final note on this: if you change phones, make sure you call and have the IMEI information updated, if I change my FUZE for another FUZE it would probably work, but if I swap the device out for a different model it would not necessarily pick the most compatible features for my phone...
Privisioned Dates: When you go to your online account management and add features, it says they are immediately effective, sometimes this is true, but in the case of my account it likes to post-date to the next bill cycle. This is especially true when you visit an AT&T store, it will definitely post-date there. I had 3 IMS APN features and Video Share features on my account, all with different dates, this is because, I tried to add and 2 people at the store tried to add, to make sure Video Share and IMS are on your account and active / effective TODAY you have no choice but to call customer service and tell them you want them on your account effective immediately. While it will appear on your account management that you have it, don't trust it as it only checks for the feature, not the active dates.
And finally the internet connection: Some people have noted that your connection must be active before the call, this is not true although it is very helpful. The video share negotiation takes place over the phone control channel, when it is determined that you both have the service and compatible phones it will send a message to both phones. They will then try to turn on their data connections and verify with the server whether or not the option should be turned on. If your data is active before the call your video share button will be available instantly as it is for me. If it is NOT then it will take ~20 seconds or more to connect to the net and contact the server to verify, then turn on the option for you. Just make sure your internet works in general and that you can connect and you should have no problems during a normal call.
I hope this helps at least some of the people out there having this issue, and maybe some others having other issues with the network. Sorry for the long post
Click to expand...
Click to collapse
And this is why Video Share will NEVER take off. It's too ****ing complicated to get working on 2 devices, and it is completely USELESS. Seriously... I talk to people online and we both have webcams, but we don't get on cam just to talk. We just talk. Video is such an unnecessary part of every day communication.
I have an unrooted ATT version of the nexus one. Randomly about 1 or 2 times a day while I am texting I will get a failed to send message and no matter how many times I try it just keeps failing. It won't allow me to send texts to anyone else either. however I continue to receive texts which is kinda odd.... the worst part is that always while this is happening I cannot make or receive phone calls this is very frustrating since I could be missing phone calls and wouldn't know it until I try and send an SMS or make a call. I have tried a lot of different things such as setting my bands to USA and setting my network preference to WCDMA Only but to no avail... I also tried a factory reset... also if I try and toggle airplane mode or turn off the radio it just crashes and I need to reboot.. if i try checking the SMSC while this is occurring but hitting the refresh button
I get refresh error and if I try and update it with the correct number I get update error... I really love my N1 and would really appreciate anyone who could shed some light on this issue
Re: My Nexus One won't send text messages or make phone calls unless I reboot
Could this be an AT&T network issue? I had similar symptoms with my HTC Hero (admittedly running EDGE) in certain parts of San Francisco earlier this year. It seemed to be the result of network congestion. Does this occur in a city or other urban area?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I am actually not on AT&T I am on Rogers network in Canada. I am living in Toronto so the 3G coverage is really good and I`ve never had this kind of issue with my previous phone which was a BB9000 and none of my friends seem to have any of these problems
I also found ppl on some other nexus one forums describing the exact same problem which leads me to believe its not a network issue but I am still not 100% sure I tried calling Rogers and had them do a cancel location and it didn`t fix the issue either
I had this issue only this morning and I'm in the UK, I put the phone into Airplane mode and back again and then everything is fine.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
jasrups said:
This actually happened with me today, a text kept failed and didn't get pushed through until I reset the phone. I'm hoping this doesn't turn into a daily thing
Click to expand...
Click to collapse
Same thing happened to me today. I'm on a stock unrooted AWS version of the N1.
hayden1987 said:
next time this happens if it happens again could u guys try and make a phone call before resetting so we can see if our problems are identical?
Thanks
Click to expand...
Click to collapse
I am unable to make phone calls, send texts, etc. until I reset. It has no impact on Wifi but kills the cell network completely.
wmm said:
This sounds like a problem I have had for several months now on T-Mobile (I just bumped the thread under the "General" topic to see if there were any developments, as I've been away from the board for six weeks or so). The symptoms I have are that the signal strength icon in the status bar shows zero bars with an "x" and the home screen says "No service." When I attempt to power off, after a while the spinning arrow stops spinning, the trackball flashes once, and then the phone reboots (takes about 45 seconds to a minute after I initiate the power-down before the reboot starts).
Click to expand...
Click to collapse
I also have a long delay after hitting restart when I get this issue. Maybe Ill try to get a logcat and see what it gets stuck on..
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
http://www.google.com/support/forum/p/android/thread?tid=3f4ad5ffac46bf92&hl=en
http://www.google.com/support/forum/p/android/thread?tid=47dc569ca9667ba7&hl=en
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
blisk said:
I'm getting RMA'ed, again, for the same issue plus not being able to register on the network after I get the x with four blank bars. I get either "error searching for networks" or "sim is invalid on this network". It's since fixed itself... somehow but i was without any phone service despite trying everything (calling tmobile for network outages, hard reset, reseating the sim card, other stuff) for about 3-4 hours twice now... and a few shorter time periods (1-3 minutes of those errors) before that.
Possible solutions.. which I've only done after it started working again but didn't cause anything bad to happen. So far have been without any of the previous issues, plus my original long standing issue of not being able to send texts, get any sort of data, or call (I call it the up arrow without a down arrow problem where the phone is trying to connect but doesn't receive anything back). These solutions were originally posted here:
They're also solutions I've come up with for my issue as well and seemed to have worked for a couple of others.
It's as follows:
*#*#4636#*#* and selecting phone information. Press the menu button and select the proper band. I'm guessing if you're in canada on rogers which uses the same band as AT&T US you'd select USA band. Anyway after selecting it should re register on the network.. close out of there. Turn off and turn on the phone and see how that goes. For people in other regions I have no idea what to properly select but it was posted on one of the threads on the google forums that it should be "automatic". Check with your provider and/or google tech support.
Another thing I've seen is again in the *#*#4636#*#* menu under phone information put in (THIS NUMBER IS ONLY VALID FOR TMOBILE USA) under SMSC 12063130004 and press update. Call your provider for your number. Restart the phone.
Less likely solutions (in order of descending likeliness to help you in your particular case):
Hard reset and/or verify the APN settings for your carrier. I've been told non factory default APN values for tmobile over the phone (google support) so I don't know if verifying them or asking for them will help or cause more issues but sometimes there's apps the mess with the APN values which could cause some of your issues. So while this has a high potential to help, it's easy to screw up. Hard resetting the phone will give you factory default values (I'm 99% certain but from what I remember). Changing them from non factory default isn't a terrible thing however call your provider rather than google tech support for the values.
Calling up and asking to add/verify the IMEI number to the network (i never did this until recently although it didn't fix my issue right when they added it anyway) and/or doing a network cancellation might help. Unlikely but if you' RMA'ed once they'll have the wrong one on file and could cause issues depending on the network.
Replacing the SIM card. Takes literally 30 seconds. They ask for account info at the store, they scan the new one.. and give it to you. You pop it in and go. If you have an older SIM card this DEFINITELY could be the issue. Its unlikely its defective but it's always worth ruling that out.
Let me know if any of these help.
Click to expand...
Click to collapse
I`ve tried all the solutions u`ve mentioned except for swapping to a new SIM card... I guess it might just be my next step but I have my doubts
I get this kind of issue occasionally, under these specific conditions only:
1. I'm at work.
2. I bring my phone with me into an area with no signal (screen says no signal, and I have 4 blank bars with an X) for more than a couple of minutes (for me, it's the room with the coffee machine - which I use a lot - no provider gets signal there on any phone).
3. It doesn't always happen, just sometimes, but when I go back to my desk, it won't reconnect.
4. Going into and out of airplane mode fixes it every time. However, with the latest CM and Ivan's Diet kernels, going into and out of airplane mode causes an immediate reboot when I try to come out of it, and only when I'm NOT connected by USB and when I AM coming from "dead" service, making logging the problem, well, problematic. Using other kernels (even OC'd kernels) does not seem to cause this airplane mode problem.
Only had this happen once trying to send a plain old SMS. I restarted the phone and no problem. I didn't think of trying to make cell calls, but if it happens again, I'll try that.
I too have had this issue with SMS. My browser works though when the SMS problem occurs. Haven't tried a phone call. I am on T-Mobile USA.
Are any of you using task-killers that may somehow be interrupting an important background service?
I have the same exact thing happen and I am on T-mobile US. I was hoping that I wasn't the only one but it seems to happen on all of my phones so I have just chalked it up to network congestion. Unless someone has an actual answer.
I have this issue about once a day.
Running the newest Cyanogen with no other modifications. Radio is the most updated one available.
Flipping to Airplane mode and backed worked on my G1 if I had an issue similar to this but the Nexus doesn't respond to it.
I reboot atleast once a day to fix this. -- Not sure if it's the radio or Cyanogen.
Anyone else have some input?
EDIT: Should have included, I am on T-Mobile
Click to expand...
Click to collapse
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Have any of you edited your build.prop yet?
This helps with the switch from Edge -> 3G -> H.
I wonder if it would fix this issue.
I don't have the issue so I am unable to test myself.
This link may help. Its at least something to try.
http://forum.cyanogenmod.com/index.php?/topic/1721-3g-connectivity-issue-fix/
This link my help too.
http://forum.xda-developers.com/showthread.php?t=659102
Re:
same thing with me im going to check out those steps your provided.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
azalex86 said:
Are any of you using task-killers that may somehow be interrupting an important background service?
Click to expand...
Click to collapse
I am using Advanced Task Killer Free, but I'm pretty sure I added important background services to the ignore list so they shouldn't be killed.
Just to double check, what background tasks shouldn't be killed?
I want to get rid of AT&T, but keep my captivate for wifi phone use if possible. I really need to get phone service through my wifi because reception where I live on any network is horrible. I know I could just get vonage, but if there is a "free" alternative, like google voice, id like some info. If you want to PM me that's cool. If I absolutely must keep a number active for google voice ill just switch to a cheaper carrier. I hear t-mobile will let people open data only service that links a phone number, and I know I can unlock the phone and use it on tmobile. Anyway if anyone has any input for keeping the phone but ditching carriers altogether please let me know.
...I will try to turn off my service and try google voice, linking it to my wife's phone number, and see if I can get it to work when I get home from Christmas shopping later...
Yup.. pay the million dollar fee to disconnect from AT&T before your contract is up - ***edit go to another carrier and they will unlock the phone to work on their carrier. You would need to request the unlock code from AT&T (I don't know if they would do it or if its really even needed.) then go to the other carrier.
And... depending on how long you've been on your contract I "think" its a minimum of $175.00 - but you will need to talk to your AT&T rep.
At least it isn't Verizon - with a crazy $600.00 early termination fee that my job had to pay for 3 phones!!
Other carriers don't unlock phones.
OP all carriers offer microcells that you put in your house to get cell service. Att has one. Google voice requires an existig number to forward calls to; your phone needs a number. If you only have wifi then why bother with a cell phone? If you can't get good cell then a data only plan wont help either.
Sent from my MB520 using XDA App
Thanks. I sort of just needed to know if it was possible to have google voice with any number or if it had to be the cell I was using google voice on. I know I can pay to get out of contract. I also knew I could carrier unlock my phone. Thank you.
Hi, I still consider myself a noobie when it comes to Android, but i do have experience with other platforms, and (if i understand you correctly) CAN be accomplished. I have personally done this on an iphone,WinMo,and sort of on a Blackberry.
1.Wi-fi calling : By using Skype In/Out you can have a number that rings in and you call out. It will cost around $60.00 annually.
2. 3G calling requires a carrier for data and some hacking but it can be done.
P.M. Me if you need some help.
Google voice can be used with a cell or land line phone number. Haven't tried to use it strictly WiFi so I can't offer much there, but it does work with any existing number you have.
Google is offering free calls through 2011 through your browser. Not sure if this helps much, but...
http://googlevoice.com/showthread.php?139-Free-Calling-in-Gmail-through-all-of-2011
I would think you can do this through a mobile browser as well provided you can get WiFi access
I'm using straight talk on an at&t s6 edge. Trying to get the google voice voicemail to work. I've tried the mmi code **004*gmnumber# to activate conditional call forwarding, but I always get "couldn't get server response".. Trying to change the voicemail service provider also gives errors. "Can not read data. Network or sim error"
I have tried the individual mmi codes for different kinds of conditional call forwarding, but get same error:"couldn't get server response".
I have read that at&t controls the conditional call forwarding service, being the original carrier for straight talk, but because I don't have an active account, they can not change features for my number.
The ST rep tells me that there might be a hardware specific mmi code that Samsung may provide?
Does anyone have any solutions?
Thanks guys,
Gozirra
Gozirra, I was having a similar problem with my iPhone 6 (on AT&T) and my S6 (on Cricket). I think it may wind up being these phones (both are AT&T branded). I wound up swapping the sim card into a spare (Cricket branded) Moto G LTE and the MMI code worked without issue.
This exactly what I just did and it works. For months I have been trying to forward my Cricket voicemail to Google Voice, from Samsung S5. I couldn't. I called Cricket, they said there's nothing they can do. I then I saw gm2racer's post, used my sim card in my son's Samsung Prime. Voila.
Same issue here with S6 active + straight talk and with youmail as well.. invalid mmi.. straight talk says they dont support conditional forwarding, however 3 windows phones prior all worked on ST (both att and vzw phones)..
Frustrating enough i'm considering switching to tmobile (not willing to switch phones per say, i just got the s6)
I know this isnt the most hit thread on this topic, but today I resolved my issue... I have an AT&T (unlocked cause its older and paid for) Galaxy S6 (SM-G920A), that I simply plugged in the cricket SIM from my older Cricket phone and started using on their network. I got the immediate system text messages that reconfigured most of the call settings and the phone worked fine but in the past couple months, i keep getting complaints that i dont have voice mail set up from callers.
I did, I do, and I have used my google voice number for years now, and use it for my outbound calling (install the gv app and have it set outbound for all to GV). I also use GV as my mailbox... and I know how to use the **004 string to change forwarding (conditional, as in when you dont answer, cant answer, etc).
But with my AT&T S6 and the MM 6.0.1 (DQC1 official AT&T rom) - that 004 string wouldnt work. Neither would changing forwarding settings from the phone settings. They all state they cant talk to the server... and theres no option in my call settings for voicemail to set voice as the handler (versus your carrier).
So I was kind of stuck.. and here is what I did.
I flashed it using odin to the sm-g920aZ QB2 firmware (as in , the Cricket firmware for the S6, 6.0.1 MM version in March 2017).
I know.. it is taking a risk as some people state it doesent work.. some do.. well.. mine did. And since I have never tried to get root or do a custom OS, i am still official (thats all I have ever flashed, was official ROMs), and galaxy pay works, and the phone works, more or less perfectly from what I can tell. In fact, its got a TON less bloatware running a cricket ROM vs AT&T ROM.
And lo and behold, call forwarding works great now. And I actually got a firmware update notice from cricket 5 minutes after it was flashed.. and, well... all I can say is COOL.
I would probably stay with a MM (6.0.1) version of the ROM or match whatever you have now. I understand once you go to nougat, you cant go back to MM, and that may be true for moving between carrier ROMs also.. (cant go from Cricket 7 to at&t 6).
Anyhow.. Ive done a ton of research on this and thought since XDA helped out immensely (thanks everyone for posting roms and such), I would give ya'll a heads up that this worked for me.
I might go ahead and take those cricket firmware updates OTA. I know its a risk, as my phone is really a 920A (it shows as 920AZ now in settings also), but I really think its the exact same hardware... if I brick it I'll let ya'll know.
Confirmed, updates are good.
24br said:
I might go ahead and take those cricket firmware updates OTA. I know its a risk, as my phone is really a 920A (it shows as 920AZ now in settings also), but I really think its the exact same hardware... if I brick it I'll let ya'll know.
Click to expand...
Click to collapse
I let it go ahead and apply all of the recent Cricket updates to the S6 (920AZ) and confirmed its been running fine for 2 days now with no issues and no loss of functionality.
Makes me wonder what setting was changed by the cricket firmware - that allowed call forwarding to work properly and be set/reset/accessed by the device? The network and device didn't change, just the firmware.. but I dont see anything in the APN settings that relates to voice mail (maybe its something else that needs to change to allow CF settings?)
ANyhow.. your mileage may vary.. and Cricket firmware is WAY less bloated than AT&T for sure!
Not sure how much help there is for such an old phone but I have a Note 5 (SM-N920V) that I use with Pageplus. I had check and been told by numerous reps and websites that the phone would be fine to use and handled VoLTE. When Verizon shut the towers a few days ago my text and calls went down too. I still have data but that's it. According to Pageplus, they are aware of the issue but have no ETA (keep getting told 24 hours and that was 5 days ago) According to other techs there's a firmware issue but I can't seem to figure out what is needed to fix this. It seems like the phone is capable of VoLTE but it isn't activated and there isn't anywhere to do so. I found someone who was flashing Note 8s with the same issue but they only handle 8 and up so I'm hoping maybe someone here can help. Thanks in advance!
In settings under network configuration.
While this phone supports 4G VoLTE it may not be whitelisted by Verizon. Their side needs to be configured to accept it.
blackhawk said:
In settings under network configuration.
While this phone supports 4G VoLTE it may not be whitelisted by Verizon. Their side needs to be configured to accept it.
Click to expand...
Click to collapse
Thank you for getting back to me. How would that be handled? I can't do anything on my end as nothing is there or greyed out. Pageplus tech support is useless and there's no way to get Verizon on the line when you don't have an account with them so I'm not sure how to proceed. I can't afford to replace the phone at this time which is why I'm trying to find a way to get this to work.
omgthisisridiculous said:
Thank you for getting back to me. How would that be handled? I can't do anything on my end as nothing is there or greyed out. Pageplus tech support is useless and there's no way to get Verizon on the line when you don't have an account with them so I'm not sure how to proceed. I can't afford to replace the phone at this time which is why I'm trying to find a way to get this to work.
Click to expand...
Click to collapse
I don't know. I have AT&T, they list their white listed devices. Couldn't find Verizon's whitelist.
Sim card may need to be updated and phone's hidden settings reconfigured.