Has anyone tried PhoneAlarm Pro 2.10, on their Sprint TP. It has a call forwarding feature that does not use sprints system to call forward ($.20 a minute). I hate the fact that I can't call forward for free. I don't know how the software works, but I am thinking about giving it a whirl.
Does anybody have this running on the sprint TP successfully? I tried it, and can't get it to work. the repeating alarms do not work, and I am still trying to get the call forwarding to work.
phone alarm call forwarding does not work on sprint. dunno why but it doesnt.
I'm willing to make an offer for someone to write a program that does this on the sprint TP. Any takers? There has to be a lot of people with the sprint TP interested, at $.20 per minute to do it. Maybe using the conf calling feature that sprint offers for free as a back end.
Related
OK, I know I'll probably get slammed, but I searched and searched and can't find the answer...
I'm coming from the Nexus One on ATT where google voice worked flawlessly. Now, on Verizon with the Thunderbolt, it's a nightmare. Incoming calls don't get my Gvoice message, just a notice saying to enter a PIN. Also, Gvoice isn't showing the correct outgoing caller ID... even though everything "appears" to be setup properly in Gvoice settings and on the Thunderbolt.
I feel like I'm taking crazy pills!! Any ideas?
The information on the Google Voice Settings page didn't work for me. Telling you to dial some crazy * #### blah blah blah.
So I did some calling to Verizon and dug deeper. In order to get GV on your VZW, you need to do these steps:
*71[Google Voice Number]
*90[GVnumber]
*92[GVnumber]
Then GV should work.
I was in the same boat as you. Upgraded from TMO Nexus to this and was going crazy trying to figure out why GV wouldn't work.
Hope it helped?
Why don't u just fork out the money for Verizon's awesome visual voicemail! What a joke. Don't think Verizon likes gv.
Sent from my ADR6400L using XDA App
I just installed the app, dialed *xxxxxxxxxx (whatever number i was told to dial by the app or site) and it seems to be working fine. I've never used it before though, so I'll update this if something goes wrong.
Sent from my ADR6400L using XDA App
I did that and the voicemail still were intercepted by Verizon
Sent from my ADR6400L using XDA App
I just followed the directions on google.com/voice and mine worked fine. My voicemail gets picked up by GV.
i had previously set up gvoice with sprint so what I had to do in gvoice was delete my cell number and re-set it up so it would register with Verizon. Works fine after that.
usafle said:
So I did some calling to Verizon and dug deeper. In order to get GV on your VZW, you need to do these steps:
*71[Google Voice Number]
*90[GVnumber]
*92[GVnumber]
Then GV should work.
Click to expand...
Click to collapse
Thanks for the post, let me try it out. Also, after digging more at Google.com, I found these bonus codes depending on what network we're on...
Verizon (CDMA network): *71[GVnumber] AND *90[GVnumber] AND *92[GVnumber]
Verizon (TDMA Network): *74[GVnumber] and *73[GVnumber]
What net are we on with LTE?
Worked! THANKS!
Worked fine for me with just the *71-XXX-XXX-XXXX code BOTH times I had to set it up (thursday new phone, last night after rooting). I just called myself from my Skype out # and it rolled to GV voicemail.
All U.S. Verizon Customers are on the CDMA network.
Lipmonger said:
What net are we on with LTE?
Click to expand...
Click to collapse
distortedloop said:
Worked fine for me with just the *71-XXX-XXX-XXXX code BOTH times I had to set it up (thursday new phone, last night after rooting). I just called myself from my Skype out # and it rolled to GV voicemail.
Click to expand...
Click to collapse
That code only sets up forwarding for one group of calls. Unfortunately, you need to setup GVoice on the Thunderbolt to properly forward BOTH unanswered (missed) calls, and ignored (intentionally declined) calls. The two different actions are handled differently by Verizon - hence the multiple dial-in codes. Although I don't know what the third code is for.
More here... http://www.google.com/support/forum/p/voice/thread?tid=00a93855af6943b4&hl=en
Lipmonger said:
That code only sets up forwarding for one group of calls. Unfortunately, you need to setup GVoice on the Thunderbolt to properly forward BOTH unanswered (missed) calls, and ignored (intentionally declined) calls. The two different actions are handled differently by Verizon - hence the multiple dial-in codes. Although I don't know what the third code is for.
More here... http://www.google.com/support/forum/p/voice/thread?tid=00a93855af6943b4&hl=en
Click to expand...
Click to collapse
I'm not going to get into a huge back and forth over it, but I just tested my Thunderbolt phone both ways...I called it and let it go unanswered, and then I called it and hit the decline button on the screen. Both times it rolled to my Google Voice voicemail. I only set it up with the *71 code.
I'm not disputing that your experience may be different, but that's how it worked for me.
Whenever I try to add my new Verizon phone number, it shows up as a Gizmo account no matter what I select (Mobile, Home, or Work).
Just what I was looking for, thanks!
works the same as it did for me from my og droid. i wish there would be an icon telling me what number the people are calling me on. i have a bunch of people call the wrong number and i never know what line its on.
I had Google voicemail set up on T-Mobile with my N1, MyTouch 4G and it worked perfect. Tried to set it up on my Thunderbolt with Verizon and I went thru the set up procedure, dialed the *71 and my google # then *90 and finaly *92. When I was done I tried to call myself and see if it works, I get a message asking me to put the # I am trying to call and hit the pound button. Please help, Love Google Voice and I tried Verizon tech help and absolutely useless, tried to sell me theirs.
Please anyone, I want that Google voicemail app working.
vinnyjr said:
I had Google voicemail set up on T-Mobile with my N1, MyTouch 4G and it worked perfect. Tried to set it up on my Thunderbolt with Verizon and I went thru the set up procedure, dialed the *71 and my google # then *90 and finaly *92. When I was done I tried to call myself and see if it works, I get a message asking me to put the # I am trying to call and hit the pound button. Please help, Love Google Voice and I tried Verizon tech help and absolutely useless, tried to sell me theirs.
Please anyone, I want that Google voicemail app working.
Click to expand...
Click to collapse
Are you test calling from another # you associated with Google voice? If so try *67
hurl03 said:
Are you test calling from another # you associated with Google voice? If so try *67
Click to expand...
Click to collapse
I had a friend of mind call in and he got the same message. I have seen other posts of people with the same issue. I can not find out how they resolved their issue. Someone must have the answer, Verizon tech help didn't have a clue unless I was buying their V Voice Mail.
I also came over from t-mobile. All I did was set my phone's voicemail setting to my Google number, then did *71(my Google number) and my voicemail works fine.
Sent from my Bolt
So, with the stock root rom, with a few different roms, and even with different kernels and radios, I don't ever receive incoming calls (though if I make an outgoing phone call, it works just fine).
Anyone know if this is something I can fix? Or is it an issue on Verizon's side? They had to go through three 4G SIM cards before finding one that my phone could actually activate with, so I'm wondering if that's the problem.
Did you set up call forwarding? Try calling *73 as this disables all calls to be forwarded, and try again.
You know what? I think you might be right... before I got my Thunderbolt, I had an OG Droid set to forward calls to a different temporary number...
My phone is going through a restore right now, so the INSTANT it boots up, I'll be dialing *73.
EDIT
VICTORY! It must have kept the call forwarding on the line. Thank you SO MUCH.
you're welcome.
Does anyone understand exactly what this does other than create an extra step while dialing? I recently called T Mo to activate the Free WiFi Calling feature after finding out that if you don't specifically ask them to activate it, minutes are still used. When I had the My Faves plan I had my GV # as one of the 5 and because of that when I used GV Dialer the calls actually were free. The T Mo Rep. said that neither GV or GV Dialer does, or was ever intended to allow free calling. I was under the impression that by design the GV number somehow used Google's servers and therefore effectively "bypassed" the use of minutes in the data plan? Any insight would be appreciated. TIA...
Google voice calls are free, the tmob rep is clueless. It doesnt count toward your minutes. International calls are a different story.
Vibrant
simply galaxy simply honey
jpatt said:
Google voice calls are free, the tmob rep is clueless. It doesnt count toward your minutes. International calls are a different story.
Vibrant
simply galaxy simply honey
Click to expand...
Click to collapse
That's what I said to her. But, the response was that all it is supposed to do is be the quivalent of a "spoof number". Every time I make a call and look at My Account, it's taking the minutes. So, on the assumption they are in fact wrong, how do I get them to change it up since it's logging minutes anyways?
Hi all.
So I have this great SI4G from AT&T that I rooted and unlocked to my network, Rogers. However I've noticed that the 3 conditional call forwarding options are set with (I assume) the previous owner's number. If I try to disable them, or change the number I get an "unsupported" or "unexpected answer" error message.
I can still make and receive calls, but if I miss them, they will not go to my voicemail. Rogers does not support those options so I really don't know how to kill them... Any ideas?
I've seen this around and about the forums, but no solution really...
Thanks!
This is not meant to bump the topic, but I just flashed a new ROM and I still get those settings. This would mean it's stuck in the SIM card... which doesn't make any sense to me.
Anyone?
call rogers tech support, they should be able to help. My best guess.
*sigh* yeah thanks chrisrotolo, I forget to do that too often... and guess what? The forward thingy was a bug actually; they reset my VM and now it works fine. Turns out all the numbers that appeared are the numbers that the network puts in to compensate for these unsupported options.
+1 for me on the duh scale...
So... I recently got a replacement used Fascinate for my original unit that had a shattered screen. It has GeeWiz 4.2.2 loaded on it and I really like it. Damn near perfect... except for one thing and I'm not even sure/don't think it's the phone/ROM.
My texting issue is related to MMS. I can send any text... short, extended/pages long, picture texts (MMS) and I can receive all except long texts. And it's only an issue with my wife. She can write a book. LOL After doing more testing with other people, it seems to be a thing with Pageplus and Verizon. My wife is on Pageplus. I'm on Verizon...for now. My son is also on Verizon and has the same issue. I had a friend who is also on Pageplus send me a long text and it failed too. If I have someone on Verizon send me a extended text (over 140 characters) and comes thru fine. Only Pageplus customers seem to have the issue and it's only to my phone. I can have my wife send a long text to a friend who on Verizon and it goes thru fine.
The failure is on the senders side too. The senders phone will says failed to send. I don't get anything on my end. This is only to my phone.
I've searched and haven't found but a couple of references to a similar problem and no solutions. One possible thing that I haven't followed up on yet is this.... This phone was on Pageplus. I activated it on Verizon. Verizon shows no issues on their end at all but I'm wondering if Pageplus still has something in their system from the previous owner with this ESN. It's only Pageplus people that have this issue sending texts to my phone. They can send to other Verizon phones. And this is only long/extended texts that are 140 characters or more. Short texts and picture texts work fine. Oh....and if the sender attaches a pic to the long text, I will receive it.
It really weird. Wondering if anyone has seen anything similar or has any ideas. My next step is to call Pageplus support to see if they can help. I was also going to re-activate my old phone to verify the problem goes away. I welcome any insights.
Mike
PS - Sorry this is my first post. Can't believe I've been on this board this long and haven't posted before but this is a daily stop for me for years now.
Creepingdeath2 said:
So... .
Click to expand...
Click to collapse
have you checked the settings in the "Messaging" app itself, seems I recall a converting sms to mms or some setting that deals with that...
hhp_211 said:
have you checked the settings in the "Messaging" app itself, seems I recall a converting sms to mms or some setting that deals with that...
Click to expand...
Click to collapse
I thought that had more to do with outgoing texts than incoming but I will try it later and report back.
So I looked in the settings of stock texting app and it doesn't have the "convert long sms to mms" option but I'm running 8sms in Default mode, which basically just themes the stock app and adds a couple more setting/features....one of which IS "convert long sms to mms". It was doing this before I started using 8sms so it's not the app. I'll try the change and post back results.
I tried turning that option on but it had no effect. Open to other suggestions. Still need to call Page plus support yet too,
Sent from my Nexus 7 using Tapatalk
maybe try a different ROM to make sure it's not just an issue with GeeWiz? roll back to a stock ROM and see if that fixes anything... also use the right ROM, you know, eh03 for vzw devices, etc.
Or possibly try another texting app or even hangouts will do sms/mms...
It sounds like page plus is possibly not splitting the message into 2 sms or not converting a long sms to a mms unless it explicitly contains a picture,,,
I would think that is software settings
That also could potentially be the sender's messaging app not converting it to mms and/or not splitting the message into 2 sms.
I know you said there were multiple people sending you stuff,, to they both have the same app?
Let me try to clarify the scenario....
My phone is a Fascinate with Geewiz 4.2.2 ROM activated on Verizon (for now LOL).
I have several people on Pageplus that can't send me an extended text message, meaning a text message over 140 characters. One is an iPhone 4, one is a Fascinate on Superclean ROM, and the last is a Fascinate on Geewiz 2.9. If any of them try to send me a message that longer than 140 characters, it fails to send on THEIR end. I never see it. These same 3 people can send the exact same text that fails to other Verizon phones with no issue.
My phone was originally a Verizon phone that was then switched to Pageplus. When I got it, I put it back on Verizon.
It seems to me that this is an issue with Pageplus, almost like there's some information in their system still that sees my phone as inactive and refuses to send it. The texts fails on the senders end almost like they don't have service. I need to take a chunk of time and call Pageplus support and see if this is even a possibility. Regular texts and picture messages sent from those same phones DO make it thru. I can send all forms of SMS/MMS with no issues. It's only receiving and only from Pageplus customers. If a Verizon customer sends me an extended text, it comes thru no problem.
I would think if it's the ROM, the problem would be evident regardless of the carrier the message was sent from. How could a ROM single out a specific message from a specific carrier? I'm not saying it's possible but it seems like this is a system issue on Pageplus side.
Thanks for the suggestions. It helps validate the steps I've taken and my thought process to solve it.
Well, I spent about 2hrs on the phone between Pageplus and Verizon tech support. Each blamed the other for the issue but ultimately Verizon is looking into it. Made to Level 3 support for whatever that is worth. Supposed to get a call back after they pour thru whatever they have to look thru. We'll see. They all agree that if the phone can receive EMS texts (Verizons extended text message protocol), the phone itself can't distinguish between carriers. The settings for each are the same. Since Pageplus and Verizon use the same system/network, it SHOULD work and can't really be my device. It's something on one of their networks.
Oh... and nobody has ever heard of something like this ever happening....which gives me great confidence that it will get resolved... LOL
Latest... tech support has been less than helpful... SURPRISE! LOL
They said that my phone is rejecting the messages but can't explain how Verizon Extended messages get thru but not Pageplus...which uses the exact same system. Not sure what else to do than maybe try a different ROM to see if it really is Geewiz or not...or maybe swap a device on the account too.
Creepingdeath2 said:
Latest... tech support has been less than helpful... SURPRISE! LOL
They said that my phone is rejecting the messages but can't explain how Verizon Extended messages get thru but not Pageplus...which uses the exact same system. Not sure what else to do than maybe try a different ROM to see if it really is Geewiz or not...or maybe swap a device on the account too.
Click to expand...
Click to collapse
I would definitely try other roms... Not surprised about Verizon support lol...