[Q] Mobile Internet occasionally not working - Hero CDMA Q&A, Help & Troubleshooting

I have a rooted unrevoked 2.1 CDMA Hero. The mobile internet occasionally stops working every 3-4 hours. I can temporarily fix it by disabling and re-enabling the mobile internet. Is there a cause for this or is it an inherent fault with either this rom or the Hero? It's also happening to a friend of mine who has a CDMA Hero that is not rooted & running 2.1.
Also, I'm sorry if this has been asked before. The search function is currently disabled for me.

I've always had this issue. not very often, but often enough to annoy me. I believe it is more a Sprint network issue than anything. Try updating your prl, that may help.

Thank you very much for the reply! I'll see if this helps.

Related

network Connection Error

Hey guys,
I was just wondering if any one is currently, or has in the past, had connection issues with their g1. I believe I read there was an issue when RC29 came out, but I'm not totally sure. Anyways, here is my problem. I am running a rooted and unlocked g1 with dwangs 1.6 on it. I have AT&T so I only have edge as well. I've noticed that I started getting a lot of "Network Connection Errors" a few days ago. I'm pretty sure it started before I rooted, but it seems to be worse now. I upgraded to 2.1, and then downgraded again in the past two or three days. My downloads from the Market are constantly stopping and being unbelievably slow (yes, I know EDGE is slow, but they are significantly slower than normal). When trying to search the market, and/or use apps that access the network I'm constantly having to click retry to gain a good network connection. Hopefully you guys have some insight. Thanks!
nope... not really, not on any of my 7-8 G1's, all broken for diff reasons (never signal issues). but im on T-Mo

Sprint Users Whats not Working 2.1?

Being a sprint user myself upon the camera development this morning (still needs work but something is better than nothing)
i have come to realize that Eclair and Android on The Sprint HTC Touch
is very close to complete.
only things left that i know of are:
bluetooth audio (music playback)
video recording
Video playback
but i want to see if anybody else has found anything.
thoughtlesskyle said:
Being a sprint user myself upon the camera development this morning (still needs work but something is better than nothing)
i have come to realize that Eclair and Android on The Sprint HTC Touch
is very close to complete.
only things left that i know of are:
bluetooth audio
and video recording
but i want to see if anybody else has found anything.
Click to expand...
Click to collapse
bt audio works for calls.
Yea I know it is but not for audio routing so you can't listen to music through it
Video playback is also still not working.
I'm running the super eclair from incubus
Well the camera on mine still isn't working after the update. It loads but when i take a picture it crashes.
I'm very new to this so I'm trying to learn as I go.
but also I'm not receiving text for some reason, everything else seems to be working fairly well.
diabolicalnyc said:
I'm running the super eclair from incubus
Well the camera on mine still isn't working after the update. It loads but when i take a picture it crashes.
I'm very new to this so I'm trying to learn as I go.
but also I'm not receiving text for some reason, everything else seems to be working fairly well.
Click to expand...
Click to collapse
Text messaging is a known issue with super eclair. It works on other builds.
cool now that the camera is working does everyone have MMS setup to send?
acegolfer said:
Text messaging is a known issue with super eclair. It works on other builds.
Click to expand...
Click to collapse
He mentioned it was.
maybe i'll try another one. I really like his version but text is pretty important.
My phone specifies that its a Tmobile my touch now after upgrading it to Myn’s Warm Donut Android 1.6 with Prodical Sun Theme. Also I get a MMI code issue. What should I do to fix this.
Tsvallette said:
My phone specifies that its a Tmobile my touch now after upgrading it to Myn’s Warm Donut Android 1.6 with Prodical Sun Theme. Also I get a MMI code issue. What should I do to fix this.
Click to expand...
Click to collapse
its always going to say my touch 3G, thats just what he has the build set to recognize the phone as, it shouldn't cause any problems
i have no clue what an MMI code is so im not sure
This is day two of going back to this phone and I dont have any data connection. In two more days according to Sprint I should have 100 percent access to whats on my account. I hope I have data connection soon. If I dont have it back by then I will be posting it here. I miss my data connection!
Tsvallette said:
This is day two of going back to this phone and I dont have any data connection. In two more days according to Sprint I should have 100 percent access to whats on my account. I hope I have data connection soon. If I dont have it back by then I will be posting it here. I miss my data connection!
Click to expand...
Click to collapse
what happened there, was your Data working before you flashed to android?
I have the Vogue and the Titan. I switched from my Vogue to the Titan due to some minor issues and now my Titan is doing the same thing. Before switching back to my Vogue I flashed the rom with the Android, liked it alot and then called up sprint and did a switch back to my newly improved Vogue. According to the sprint rep it will take upto 4 days for all provisioning to be complete. As of right now I have it all working except for the data. My phone doesnt even show a data connection and when it tries to access something via internet it says "You don't have a network connection. Ths could be a temporary problem or your SIM card may not be provisioned for data services. Please try again when you are connected. If it continues, call Customer Care."
Ohh yah, *2 and *4 doesnt work. I was going to call them today to see if they could speed things up but cant call them this way.
Tsvallette said:
I have the Vogue and the Titan. I switched from my Vogue to the Titan due to some minor issues and now my Titan is doing the same thing. Before switching back to my Vogue I flashed the rom with the Android, liked it alot and then called up sprint and did a switch back to my newly improved Vogue. According to the sprint rep it will take upto 4 days for all provisioning to be complete. As of right now I have it all working except for the data. My phone doesnt even show a data connection and when it tries to access something via internet it says "You don't have a network connection. Ths could be a temporary problem or your SIM card may not be provisioned for data services. Please try again when you are connected. If it continues, call Customer Care."
Ohh yah, *2 and *4 doesnt work. I was going to call them today to see if they could speed things up but cant call them this way.
Click to expand...
Click to collapse
yea so i have an easy fix to your problem, flash back to windows mobile once its back an loaded access the internet, it should do some sort of dialing #777 thing then flash back to android after IE loads any sort of web page.
you should be perfectly provisioned right now the max it usually takes is like 24 hours, although i do still have nightmares from my days as a service tech provisioning those sprint Direct Connect phones
but yea so if you were in android before you activated the phone thats why you dont have data
Thank you. I relized that I would probable needed to do this but I didnt want to if there was a easier way to resolve this issue. I recall that I needed to do this when I went for stock rom to nfs 6.5 and had no internet as well. I then needed to load the 6.3 rom and then back to 6.5. This time I reverted to the 6.3 nfs rom and straight to this one.
okay so I am super new to this...i have a sprint vogue and i am running the zen-hero files from my sd card...I cannot get my caller id to work to save my life...it shows just numbers when someone calls me please help...

3G Data Stalls. Radio On/Off Cures

Currently running 2.2 FRF83, but I experienced this on 2.1 too...
Sometimes whilst browsing, the browser will stall when requesting a new web page. Eventually the page will timeout with a page unavailable or data connection error.
At the same time no other data functions work - email, Twitter etc. Also tried Dolphin browser but no luck, so I don't think its browser related.
The 3G icon shows both up/down arrows flashing as if it's requesting and receiving data.
While this is happening, a quick check of the phone info page does indeed show packet and byte counts increasing for both PPP Sent and PPP Received.
It's as if the data is coming down, but the phone doesn't recognise this.
To fix the issue I turn the radio off and back on. This immediately solves the issue, until it happens again, which could be in a few minutes again.
Have tried different radio settings like WCDMA Preferred, WCDMA Only, Auto prl etc. Still the same.
Has anyone else ever experienced this? Any possible solutions?
I have the same exact thing happening to me. I'm on AT&t in the US. Very frustrating, I was hoping that 2.2 would fix this. I've sent an email to Google regarding this and have yet to hear anything back.
So I'm not the only one then. It'll be interesting to see how many more Nexus One owners experience this issue.
Hope there's a solution somewhere out there.
Same ned a fix bad
Sent from my Nexus One
I get the same problem using the FroYo radio (4.06).
No problems with the older 4.04 radio though. Unfortunately I can't use that with 2.2 of course.
I was in America using At&t and had no problems with 2.1. I moved to Turkey and got on Turkcell and had problems then either.
I installed 2.2 (since the first ones came out FRF50) and am now on the latest and ever since I have had similar problems. I have to reboot the phone when this happens and then it works for many hours until it happens again.
When I go into market it pops up a dialogue box and makes me hit retry twice and then works.
It would be nice if this was straightened out.
I just got off the horn with Google support. The SE had me do *#*#INFO#*#* then bring up the menu and choose "select radio band" I then set the phone for "USA Band" the phone confirmed success. This seems to have worked for me. Hope it helps you.
Yep, I already have mine set to Euro Band. The "3G Freeze" still occurs for me.
Interested to hear how you get on with that Band setting nonetheless.
I'm on AT&T and had fantastic signals prior to the FRF83B update. Since I updated the radio, I'm having the exact same issues. It's becoming a pain when I'm trying to stream internet radio, because it cuts out every 20 or 30 seconds. I also noticed the other day, where I use to get strength, I had *no* reception.

[Q] Location services on 3g wont work ATT

I posted a few days ago but got no replies and the thread died out. I found that people on the "Rogers" network were having similar problems. However, the solution did not work for me.
Whether I am on stock 2.1 or a 2.2 rom, my location based on mobile networks doesnt work. That is at least for 3g. Whenever my phone happens to get on Edge, my weather widgets update and I can see a general location on maps.
My needs are miniscule, but the problem is there. Is there nayone else having this same issue? Any replies are welcome. I feel very helpless
(UPDATE)
Bump
I just got a new captivate from ATT and the location service on 3g still doesn't work. Could it be my sim card?
Well, I appreciate the responses and wonderful feedback. It reassured me that the problem was not just with me....
Sarcasm aside it seemed to have been some kind of network problem with ATT. Location services based off of the network are working fine now.
Sent from my SAMSUNG-SGH-I897 using XDA App

Frustrations with MMS on T-Mobile (ATT model, black)

An hour ago this was going to be a totally different post.
I'm using an ATT branded, black HTC One. My SIM is for T-Mobile. Like many others, I'm experience issues with sending/receiving MMS. I had been using Android Revolution HD 71.1 and would be unable to send MMS. Strangely, though - my ability to send them seemed locations specific. At work it was no problem, at home it would fail every time.
Unless I disabled WiFi. With WiFi disabled, they seemed to send no problem, but with WiFi and Mobile Data simultaneously enabled it would return errors. Disabling WiFi while at home was an inelegant solution, so I tried downgrading to Android Revolution HD 30.6, which is Android 4.3 rather than 4.4.2. This seemed to have done the job. Until it no longer worked.
Same issue. Wifi disabled - fine. Wifi enabled - unable to send MMS. Everything else works fine, phone calls, mobile internet, etc.
This was meant to be a post advising others how to fix this problem. Instead I'm right back where I started.
This is very frustrating. Especially since I thought I had found a solution only for it to fail once again.
Miguel_Lancaster said:
An hour ago this was going to be a totally different post.
I'm using an ATT branded, black HTC One. My SIM is for T-Mobile. Like many others, I'm experience issues with sending/receiving MMS. I had been using Android Revolution HD 71.1 and would be unable to send MMS. Strangely, though - my ability to send them seemed locations specific. At work it was no problem, at home it would fail every time.
Unless I disabled WiFi. With WiFi disabled, they seemed to send no problem, but with WiFi and Mobile Data simultaneously enabled it would return errors. Disabling WiFi while at home was an inelegant solution, so I tried downgrading to Android Revolution HD 30.6, which is Android 4.3 rather than 4.4.2. This seemed to have done the job. Until it no longer worked.
Same issue. Wifi disabled - fine. Wifi enabled - unable to send MMS. Everything else works fine, phone calls, mobile internet, etc.
This was meant to be a post advising others how to fix this problem. Instead I'm right back where I started.
This is very frustrating. Especially since I thought I had found a solution only for it to fail once again.
Click to expand...
Click to collapse
When I was running the T-Mobile 4.4.2 with Sense 5.5 I had issues receiving MMS when connected to WiFi. They would always fail, I would have to disconnect from WiFi and then the MMS would automatically receive. But, since the update to the T-Mobile 4.4.2 Sense 6.0 OTA rom, all the MMS now work as normal whether I'm connected to WiFi or not.
I do know that the SMS app called ChompSMS has a specific T-Mobile setting that will temporarily switch from WiFi to cellular to send/receive MMS and back again. Maybe you can try that if you don't want to run the stock ROM.
@Miguel_Lancaster
Try upgrading to the latest tmous firmware. 5.14.531.1 ,might help. I will include the latest tmous radio and radio config. I have an att phone/sim, but i'm running gpe firmware and rom. I hope this helps.
It had seemed when I first got the device up and running that everything was fine with MMS (that was using 4.4.2, Sense 6.0), but either after a certain number of messages, or while in certain areas I would have to turn off WiFi to be able to send MMS.
That's why I tried downgrading to 4.3 with the alternate version of Android Revolution HD (essentially a tweaked version of the stock HTC ROM). What I find odd about the two version of that ROM (30.6 vs. 71.1) is that the installer for one includes an model selection screen and the other treats them all alike. 30.6 allows me to choose between International, ATT/Developer, Sprint, T-Mobile, etc.
Initially I chose ATT/Dev as that's the hardware model of my HTC One and wasn't keen to deal with a soft-brick. As stated in my first post, this seemed promising initially but shortly after ran into the same bug. I flashed one more time and tried using the 'T-Mobile' model selection during install. This has proven the most reliable method for me thus far. I suppose it would have to do with the radio being flashed between versions? It's curious to me that a similar option is not included in the other ROM version -- something I wanted to address in that ROM's development thread, but am prohibited from doing currently due to my post count.
Anyhow, 4.3 with Sense 5.5 seems to finally be working for now. Android 4.4.2 and Sense 6.0 did have some some aesthetic differences that I preferred, in addition to seeming marginally faster. I'll deal with an older version of the OS though if it means my phone functions properly.
Thank you both for your replies.
One thing that may be worth mentioning is that I've yet to enable Group MMS in my messenger settings this go-around. I suspect that its coincidental, but I'm reluctant to see what happens if I do enable it.
Maybe I'll try again with 4.4.2 in the future, but all this flashing, re-flashing, and settings tweaking becomes pretty tedious. In relation to that point: Does anyone have any experience with the built in HTC/Google app backup/sync. For some reason I've never really trusted any all-in-one solutions to be reliable, especially between ROMs or Android versions. Perhaps I should trust them more?
P.S.
CID Getter app lists my CID as CWS_001 --
don't know why I never bothered checking that until now. Could changing it to TMO_001 be helpful at all or does it not matter?
I broke MMS again, but this time I figured out how!
AdBlock Plus seems to be the culrpit.
As soon as I installed it MMS stopped working again. Unless WiFi gets turned off. Or ABP. If ABP is disabled everything works fine.
I did some research and it seems to be that ABP filters traffic on port 80, the same port that MMS send/receive.
I tried changing my APN settings for T-Mobile to operate through port 8080 as a workaround, but that didn't help. For now though, seems that AdBlock Plus is the perpetrator. I'm gonna try one more time with 4.4.2 and see if I can duplicate the same results.
Miguel_Lancaster said:
I broke MMS again, but this time I figured out how!
AdBlock Plus seems to be the culrpit.
As soon as I installed it MMS stopped working again. Unless WiFi gets turned off. Or ABP. If ABP is disabled everything works fine.
I did some research and it seems to be that ABP filters traffic on port 80, the same port that MMS send/receive.
I tried changing my APN settings for T-Mobile to operate through port 8080 as a workaround, but that didn't help. For now though, seems that AdBlock Plus is the perpetrator. I'm gonna try one more time with 4.4.2 and see if I can duplicate the same results.
Click to expand...
Click to collapse
Hi Miguel, I can confirm that AdBlock Plus will prevent you to send and receive MMS. Looks like the app block traffic on the port used by MMS. I have personally experienced this issue, and disabling AdBlock Plus solved it. There is also a few thread here that discuss that issue (irc, I posted in those). This issue was also reported hundred of times on AdBlock Plus forum, not sure if there is any solution (except for disabling it): https://adblockplus.org/forum/viewtopic.php?f=11&t=11755#p66133
edit:
http://forum.xda-developers.com/showthread.php?t=2326679
http://forum.xda-developers.com/showthread.php?t=2335038
http://forum.xda-developers.com/showthread.php?t=2301551
alray said:
Hi Miguel, I can confirm that AdBlock Plus will prevent you to send and receive MMS. Looks like the app block traffic on the port used by MMS. I have personally experienced this issue, and disabling AdBlock Plus solved it. There is also a few thread here that discuss that issue (irc, I posted in those). This issue was also reported hundred of times on AdBlock Plus forum, not sure if there is any solution (except for disabling it): https://adblockplus.org/forum/viewtopic.php?f=11&t=11755#p66133
edit:
http://forum.xda-developers.com/showthread.php?t=2326679
http://forum.xda-developers.com/showthread.php?t=2335038
http://forum.xda-developers.com/showthread.php?t=2301551
Click to expand...
Click to collapse
Yup, it's a shame that such a well documented bug has gone unfixed.
Good to finally have figured out my problem, only took a few days of tinkering to finally narrow it down to ABP and be able to make a relevant search to back up my hunch.

Categories

Resources