[Q] Mobile AP and texting problems

[HeathicusF]

My wife's Infuse was running Serendipity VII. She was having some minor problems with it (such as the camera's flash not working consistently) and some apps crashing. So we decided to go with Zeus. Then the problems really started pouring on.

I flashed Zeus without doing a factory reset. I just wiped the cache partition and the Davlik cache. It was OK for a day or two, then it started misbehaving. More crashes, sluggish, when she sent a text message she'd get a "Message not sent" error (so she'd keep trying until she didn't get the error, meanwhile every attempt was actually being sent so people were getting her texts multiple times), Mobile AP would turn itself off (we do pay for the Mobile AP plan with AT&T).

So I did a factory reset/wipe user data, wiped the cache areas, and re-flashed Zeus. Restored everything with Titanium Backup. No change in behavior.

So, I used Odin to flash back to stock UCKD5 (using this). Things were OK for a day or so except that the time was displaying UTC time instead of local time. (I started another thread about that.) Then, the mobile AP started shutting off again, now with a message saying we don't have a Mobile AP plan. But we do. I flashed a new modem (UCKL2) last night hoping that would clear up both issues. It fixed the time problem, but Mobile AP is still saying we don't have a plan. And now she's also getting the "message not sent" error again when sending text messages (although the messages ARE being sent).

Any ideas on what the heck happened and what I could do to get her going again? Using the "Mobile AP" is essential as it is our only home internet connection (no cable or DSL available and we ditched satellite a few months back) and our kids are enrolled in an online school.

Would flashing another ROM clear things up? Maybe try stock again with the "ultimate unbrick" package or the Heimdall one? Or maybe try Zeus again? Or CatyRom?

 

[HeathicusF]

I reflashed to stock again using ultimate unbrick. (Wiped cache, factory reset, Odin to stock.) Mobile AP gave same errors. Texting seemed fine, but with Mobile AP not working I didn't test it long. Flashed Zeus again (Rooted, installed CWM, wiped cache, factory reset, formatted internal SD, installed the Zeus zip, rebooted and waited about 15 minutes before touching it.)

Mobile AP is fine (for now anyway) but texting is flaky. Some texts go through, but most don't. She just gets an error saying "Message not sent."

Any ideas out there???

 

[qkster]

I reflashed to stock again using ultimate unbrick. (Wiped cache, factory reset, Odin to stock.) Mobile AP gave same errors. Texting seemed fine, but with Mobile AP not working I didn't test it long. Flashed Zeus again (Rooted, installed CWM, wiped cache, factory reset, formatted internal SD, installed the Zeus zip, rebooted and waited about 15 minutes before touching it.)

Mobile AP is fine (for now anyway) but texting is flaky. Some texts go through, but most don't. She just gets an error saying "Message not sent."

Any ideas out there???

Idk..maybe you need and apn change.
Go to settings. Wireless. Apn.
Menu to bring up 2 stock apn.
create a new one. it's around..check my sigs line. After you write it in, menu and save. Select the new apn.
Reboot

 

[HeathicusF]

Found the APN info in the first link. Thanks! Does the name matter? I noticed it is "AT&T WAP" on my Captivate but "AT&T 310 410" on her Infuse.

 

[qkster]

Found the APN info in the first link. Thanks! Does the name matter? I noticed it is "AT&T WAP" on my Captivate but "AT&T 310 410" on her Infuse.

no..you can call it what you want.
HeathicusF's 310 410
but just for s&g's, I would call it "AT&T 310 410"

Did it fix your issue?

 

[HeathicusF]

I haven't made any APN changes yet. She uninstalled GoSMS (which had been restored with TiBu) and reinstalled it from the market. That was a "grasping at straws" solution since the problem was happening in both GoSMS and he stock SMS application. So far, no problems. But there have been other little spans of time with no problems then it would start acting up again. So I'm just keeping an eye on it right now. There are some differences between her APN settings and the ones listed, but I don't want to change anything if it really is working now.

 

[HeathicusF]

OK she has narrowed it down to a problem with long text messages. Anything over 160 characters will fail. That is why she thought it was flaky and working for a while each time we made a change. She'd send a lot of short "testing" type messages, which would go through and she would think everything was good. Then eventually she would write a long "real" message and it would fail and she would think the problem had "returned". Not having any problems like that before, she never associated the problem with the message length.

Based on some quick research, I think that is a modem problem.

If we can fix this issue, she'll be all good again.

 

[qkster]

OK she has narrowed it down to a problem with long text messages. Anything over 160 characters will fail. That is why she thought it was flaky and working for a while each time we made a change. She'd send a lot of short "testing" type messages, which would go through and she would think everything was good. Then eventually she would write a long "real" message and it would fail and she would think the problem had "returned". Not having any problems like that before, she never associated the problem with the message length.

Based on some quick research, I think that is a modem problem.

If we can fix this issue, she'll be all good again.

lol..click on my sigs -link #1. Read post #2.

it has to do with a modem ucki3.

 

[HeathicusF]

She has UCKL2.

EDIT: I misunderstood and thought you were saying the problem was with the UCKI3 modem. Should have looked at that post you pointed me to first. I see now that UCKL2 is the problem and UCKI3 is the solution.

 

[qkster]

She has UCKL2.

EDIT: I misunderstood and thought you were saying the problem was with the UCKI3 modem. Should have looked at that post you pointed me to first. I see now that UCKL2 is the problem and UCKI3 is the solution.

..........