ERIS on Page Plus = dropped calls - Droid Eris Q&A, Help & Troubleshooting

Hey gang,
I am still having an issue with Dropped calls/Disconnects on the first call made from a fresh boot of the phone, and random dropped calls with the message that i need to deposit more funds.
My device: HTC Eris (i have two of these phones on PPC with the same exact issue)
My plan: T&T 1200
My issues: I get the "Dropped Call/Disconnected" problem EXCEPT with a twist.
EVERY time I reboot my phone (since day one when I joined PPC a few months ago) my first call lasts about 45 seconds then disconnects with no message. I just hear a few beeps and the call is gone. I can then call or receive a call from the person I was just talking to and stay connected as long as I like. I tried to fix this by making my first call to my voicemail, but that didn't work. My first in/out call to a real phone always disconnects within 45 seconds 100% of the time.
My troubleshooting:
Standard programming via *22890. Programming is successful but my problem is not fixed.
*22801 never connects.
*22891 programs correctly but does not fix my issue.
Flashing the VZW/Alltel Hybrid PRL (http://forum.xda-developers.com/showthread.php?t=673661) updates the PRL correctly but doesn't fix my issue.
Some have reported that dialing #737 (to get automated PPC account info) after a reboot fixes the problem but it doesn't fix the issue for my two phones
*#*#4636#*#* then select "Phone Information", then scroll down and CDMA auto PRL or CDMA only. Neither fixed the issue.
Any other tips?

I havent had any problems with PP.

it is very strange indeed.
My two phone numbers initially came from Sprint.
We left Sprint and joined Page Plus once I bought two used Eris's locally (Nashville Tennessee area... 615 area code)
I REALLY don't want to have to change my number, but may have to as a last resort.
This issue is driving me nutz. =P

Related

Occasional No Dial Out/SMS Sending

Hi all,
Looking for a bit of help/advice.
On occasions, probably between 1-3 times a day, when I try to make a call on the Hero, the call appears to look like it is dialing out but it just sits there saying 'dialing' but never connects to the destination which can be any UK number / Orange 150 etc. Either rebooting the phone or leaving it for 10 mins or so fixes the problem, but it does become annoying!
At the same time as this happening, when I try to send an SMS, I get the error 'SMS not able to send' in the notification bar. Again, I have to keep trying and it sorts itself out.
A final problem and I am not sure if it is related or not is I have had numerous people try calling me at various times, my phone doesn't ring or display a missed call, nor do I get a missed call SMS but the person who tried calling me said the line was actually ringing first and then went through to voicemail. I have witnessed this myself by calling my phone, getting a ringing line but the phone doesn't respond?
Any ideas of help would be appreciated. This problem has existed on Modaco Roms 2.2, 2.8 and 3.0 - I'm on Orange UK.
Thanks,
Nick
I have the same problem with the Orange Poland. When I logged on to the 3G sometimes you can not call or send SMS. When I switch to the 2G network problem disappears.
Yeah, it is strange, I have done that too, turn off the 3G to 2G and back to 3G which sometimes cures it, but not all the time.
I've tried various things, made sure the apps aren't closed with Taskkiller or anything like that. There is no specific time or occasion it happens, it just does now and again.
Well I have tried everything. I recieved all the settings from my operator , changed over 10 ROMs and gone back to the original too, i tried what you said to turn 3G off , i reset to factory , i unrooted.....Nothing works for me. I just get "Unable to send". I also tried 4 SIMs from different operators !!!

delayed text messages

right,
my wifes starting to lose her temper with her hero.
she send over 150 text messages a day, but receiving them seems to be a very hit and miss affair.
she gets texts ok for a while, then gets nothing for 10-20 mins (from what i can tell) then all the ones she has missed arrive all at once.
orange UK have basically told her to naff off and talk to HTC.
so, can anyone tell me whats causing the problems, is it an orange problem, or a phone problem.
if its the phone, whats causing the problem
doing a bit of a search, one explanation seems to be that the phone is running out of memory and it shuts down the text app and relaunches it later on, if so, how can i prevent/stop this happening.
she is on the current rom from HTC which she installed about 10 days ago to try and prevent this.
thanks in advance for any advice / help you can give
from what i have read on the forum it might be a problem with the stock messaging app.
try installing handcent sms or chomp sms from the market and see how that goes.
don't forget to turn off the notifications from the stock sms app or you will get multiple notifications for the same message.
also if your wife is using task killer applications she should put the messaging app on the ignore list!
Me too!
I am having this very same problem, although on a slightly smaller scale (150 texts/day?!). I also get the problem where callers are going straight to my voicemail when the phone is right beside me, receiving full signal, which, to my mind, would seem to be related.
I spoke to Orange who fobbed me off with "oh, there's a mast down in your area, switch to use 2G only", despite my protestations that the problem occurred when I was in different parts of the country...
Interestingly, it happened with my Touch Diamond as well when I first got that, about 18 months ago; I was never sure that it was completely cured, but it sure as hell wasn't as bad as it is now on my 2 month old Hero with stock Orange ROM.
My twopenneth, for what it's worth.
P.
Try a new updated Radio rom maybe? One way to tell if its a network issue is to make calls to 150 for about 10 seconds and see if the stuck messages come through, if so its a network issue. I wouldn't let orange customer service fob you off they don't have the reporting tools to actually look into the issue's.

[Q] Error 16: Switch 694 after S-Off; Phone dysfunctional

I followed Bentenrai's guide to S-Off, Rooting, and Recovery. Internet (both Wi-Fi and 3G/4G data) works, but I am unable to make/receive phone calls or send/receive text messages.
The phone call error occurs after about 2 rings, which says "Error 16 (then in Spanish) Switch 694".
The sms error is: "sms error radio interface resource shortage" with details "cause code:64, error class: 2".
I tried everything from the "Phone does not work after S-Off" thread and was on the phone with 2 Sprint operators for over an hour. The first operator had me update profile and PRL, then had me turn off/pull battery while she did stuff twice to no avail. The second operator (who was mean and treated me like a moron) had me turn mobile networks off and on again, update profile and PRL, and pull battery (yes, she actually wanted me to pull the battery while the device was on; I powered it off first).
Is anyone else experiencing this or has anyone found a solution?
Thank you very much!
Yup, I found the fix. It's really easy! Tell the person to do a "CHLS Refresh", and then restart your phone.
http://forum.xda-developers.com/showthread.php?t=1194460
Thanks! I also just saw the thread in the General section about all the lucky people who achieved S-Off without the error.
I'll call them back tomorrow and report back.
i had the same error after rooting my phone, just try to call any number, and after listen to the message, it will connect you to a sprint rep. they will confirm some information with you and they will tell you that they will reset from their side and ask to turn off the phone for 30 sec and boom, it's a go.
After some thought, I realized both Sprint reps only had me pull the battery for a few seconds. I decided to leave the battery out for about 5 minutes and when I powered back on, I was able to connect to voicemail. I let it stay connected for a bit and then was able to make phone calls and texts. Suddenly, I began receiving Error 67 messages, so I updated profile and PRL. Since then, (knock on wood) everything has been ok. Phew!
Forgot to mention this tidbit of wisdom from the 2nd Sprint rep: She told me my problems with making calls was because there's an outage in my area. I told her that wasn't likely because I was using another Sprint phone to talk to her. She still persisted in saying it was an outage. Yay!
That's it? no other responses to this. My sons phone is a paper weight at the moment. He can't even dial Sprint and nothing else has worked. Anyone have another idea?

[Q] While Roaming, Call Disconnects Before Dialing Out. No Data

I know it's been a pretty common issue for rooted EVO 3D users to get an error 16 while roaming, which requires them to call Sprint and go through some rigmarole to get the phone working again.
I seem to be having a different (although similar) issue. I have no issues making calls, or with data while I'm on the Sprint network. But now that I'm roaming off of a nearby Verizon tower out here in the middle of no-where, I'm having issues. I try to place a call, and immediately the phone sounds a disconnection beep and that's it. I also do not have data.
About 45 days ago up here I received a message about not being authenticated (the error 16), but I was told that they couldn't fix this without me bringing my phone into the store. I just reset the phone and did hands free activation again, and avoided the store. I haven't noticed any issues after that, and I do go in and out of roaming areas sometimes while in the city.
I just tried to do a chat with Sprint. I specifically said I had an error 16 and needed an HRL refresh (I lied). The rep had me power off my phone while she attempted to send it a signal. After this she had me dial *2 and my phone process crashed while I tried this. I also still couldn't call out. She tried having me power off again. Same problem. Next she told me to power off my phone and keep it off for 30 mins. If it wasn't fixed by then, she gave me a support number to call.
Anyway, not sure if the support number will help. Figured I'd just see if anyone has had a similar issue or experience. I found another thread mention resetting through ##786# and using your MSL to get into it. My EPST process seems to crash when I try this. ##DATA# doesn't crash though...hm.
I'm running the Synergy 3Dvo Rom (Nightly 344 I think?). Stock kernel.

[Q] SMS Error Code 98

EDIT: 11:15pm 9/25/2012 - ISSUE RESOLVED, SEE BOTTOM OF POST FOR SOLUTION
Okay, relevant information first:
Evo 4G LTE on Sprint
HBOOT 1.15 S-ON HTC DevUnlock
Current ROM CM10 Nightlies
Sprint-Google Voice integrated number
Now for the issue:
Texts can not be sent through the messaging app. When attempting to send a text, it will say "sending..." for a few seconds, then I get a notification saying "message not sent". Clicking on this notification takes me to the messaging app where the failed message has a red triangle next to it. When I long press the failed message, it comes up with a menu, and when I click "view details" it says "Error Code 98".
This happens both when connected to WiFi and when not connected to WiFi. It also happens both in my home town, and another town 45 minutes away (meaning the issue doesn't seem to be with the particular tower).
The last successful text sent or received was on Sept 13th.
Calls still operate as normal.
No changes were made by me between when my SMS was working properly, and when it stopped working. (Same ROM, Recovery, Kernel, etc). I haven't downloaded any SMS apps (handscent, gosms, etc) that could be interfering with the messaging app. I DO have the Google Voice app, but I had that when SMS was working properly as well, and the GV app hasn't been updated since March (meaning it shouldn't have changed how it was behaving).
Other peculiar behavior:
In addition to not being able to send texts via the messaging app, it seems that my number is also unable to receive texts. When texts are sent to my number, my phone does not receive them and they also do not show up in my Google Voice inbox. The sender is given no notice that the text has not been received. I am able to send texts from the Google Voice app, and others successfully receive them. When I send a text to myself from the Google Voice app, I receive it in my Google Voice app, but not in the stock messaging app (even though my Google Voice app settings say that texts will be received via the messaging app).
Things I've Tried (Updated: 3pm EST, 9/25/2012 ):
* Turning it off and on again
* Updating CM10
* Changing Google Voice settings (though it's possible I overlooked a setting)
* Factory Reset, Reflash ROM
* Flash Sense ROM, Update Profile/PRL
* Flash different AOSP ROM (Paranoid Android)
Things I've Not Tried (in order of how willing I am to do the things):
* Using an alternate SMS app (GoSMS, Handscent, etc)
* Un-integrating (and Re-integrating) Google Voice
* Giving the EvoLTE a relaxing bubble bath, to calm it down
* Flash Stock, Unroot, Update Radio
So, does anyone know what might cause this problem, and/or how to resolve it?
EDIT: Solution below
STORY:
I called Sprint Support, and had them reactivate my old phone (Evo4G running a CM9 alpha), by giving them the MEID for that phone. At this point I powered the phone back on, and called an activation number that they had given me (888-546-0314). On a Sense ROM, I would have simply updated my profile, instead of calling the number. We then tried SMS on the reactivated phone, and it worked (also, texts began showing up in Google Voice again at this time). I turned off my Evo 4G LTE, then I gave him the MEID for it and had him switch my number back to that phone. After he said he had switched it, I powered the Evo 4G LTE back up, and updated the profile, which I was able to do since I was still on Viper4G (note: I had to update the profile via WiFi, it might have worked over data, but it was taking longer than expected so we cancelled and just use WiFi for the update). Once the profile had updated, I called the test number again to confirm that the phone was activated. When I tried SMS, it worked as it should, including sending a copy to Google Voice.
TL;DR:
1. Find an old phone
2. Write down the MEID of both phones
3. Find a third phone to use to call Sprint (since you'll be activating/deactivating the other phones throughout the call)
4. Call Sprint Customer Support (888-211-4727), and punch the appropriate numbers until you are talking to someone
5. Have them switch your number to the old phone's MEID. Make sure the old phone is activated.
6. Have them switch your number back to the new phone's MEID. Make sure the new phone is activated.
7. Texting should be working on your new phone again.
Notes: The old phone may not be necessary. It may be enough for the Sprint Service Rep to deactivate your phone and then reactivate it. But I figured I would write out the EXACT method that solved the problem for me, since I am positive that this method has worked at least once. I have neither the means nor the desire to recreate the problem, so I will have to leave testing of other methods to the next person that experiences this problem.
Update: Clean flash of Paranoid Android did NOT resolve the issue. Still getting "Error Code 98".
So, this tells me/us this is not an issue with CM10 (which is not surprising, since I have no idea how what ROM I have flashed would keep Google Voice from receiving the texts as well).
This may sound odd but try moving the time up an hour or back an hour, error 98 is a problem with home agent, it's a sprint network error. I don't know of anything else that's helped
Try calling sprint and ask them if they can do anything. When I went s-off I had to call them bc my calls and text had errors. Data worked though.
They pushed something that fixed it in less than 10 seconds. Just wanted me to verify my account.
I tried changing the time 1 hour forward, and 1 hour backward, neither of those resolved the issue.
On hold with the Sprint tech department (it's taking longer than 10 seconds, but hopefully they figure out how to fix it.)
EDIT:
Mini-Update: Flashed Viper4G (a sense ROM), problem persists.
Updated profile and PRL while in Viper4G, problem persists.
Was told by Sprint technical support to press ##6-digit-MSL-here# and edit something, then reboot. Did that. Problem persists.
SOLUTION
The problem has been resolved, and the OP has been edited to include the method used to solve the problem.
If this was a game, Anthonicia would win for being closest (though it took closer to 2 hours on the phone with Sprint to fix the issue, if we include all four calls I made, 20-30 minutes if we only include that final one).

Categories

Resources