I rooted and have been running CM7 for months never had a problem. Earlier today I started having trouble sending texts so I updated from Nightly 71 to nightly 75 thinking I stumbled into a nightly bug (which happens often) and this did not fix the problem. So I went to an old nandorid backup from 7-18-2011 and restored because that particular backup has always worked perfect for me. Still this did not fix my problem.
Then I got my big boy shoes on and downloaded Heimdall and a stock image of Froyo 2.2 for my Captivate. I followed the directions and downloads from here.
This did not fix my problem. I am currently running a 100% stock version of the phone now so I cant possibly think of any other way to fix this problem other than taking it up to AT&T and asking them if there is any way to have it sent out or to receive a new phone. As I think there might be a problem with the radio inside the phone.
I can still send texts on and off but I can not use data. My mother has an SGS Captivate running stock Eclair 2.1 (never been rooted or flashed) and she has FULL bars while I alternate between 1 and none. What gives??
Have you tried a different sim card?
UPDATE: All the sudden my mothers phone and my friends phone (AT&T Iphone) are reporting the same type of service issues. Maybe it was a service outtage in my area and my phone just saw it first? This is getting stranger.
Seems like AT&T issue, just wait 1 or 2 days and see if everything goes fine.
Related
Hello people. I searched for info on this issue, but nothing for the Captivate came up. Intermittently I'll wake my phone up and there will be a little circle with a line through it where there should be network info. Anything I try to do with the network pops up a "Not registered on network" (or something like that) message. Usually rebooting the phone will solve the problem, but last weekend after three reboots it was still doing it. I left my house and an hour later checked it and no circle/line icon. This happens every several days, so not a chronic problem yet. Still very annoying. Any solutions? Thanks.
Stock Captivate.
I would consider warranty return if it were me I havent seen or heard of this before your post. good luck.
I have a stock captivate and let's just say I am incredibly disappointed and annoyed with it and at&t in general I'm tired of all the run around and hold up concerning froyo, but this isn't the thread for that.
My phone has been glitchy since the get go. The newest is the issue with "not registered on network". It has happened off and on, but a couple days ago, after I had turned the phone off for the night and back on, the phone screen blanked out while the bottom touch panel stayed lit and everything became totally unresponsive. After several reboots by removing the battery, my screen finally came up again, but so did that little blue circle and line...voila..."not registered on network"
The guy in tech support from at&t tried to help me out. He stayed on the phone with me for over 2 hrs trying to correct the issue, but even after a factory wipe...nada. Lost all my apps, free and purchased... if we would have froyo like promised, all my apps would have been backed up...UGH...
This is actually my third captivate in as many months. My first phone bricked itself after 2 days. No one could ever figure out why. I am waiting on a replacement as we speak. Of course my "new" phone is being replaced with a refurbished one. I hate that considering my current phone was only 3 months old and didn't have a mark on it, but what can I do?
because you don't mention if you're running stock or a custom ROM, I'm going to assume custom ROM. and if you are, then you must have not searched very hard because this is already a semi-known issue: http://forum.xda-developers.com/showthread.php?t=864903
it happens to me ANY time I use a modem newer than JK3... when I use UGJK3 or older, no problems... but if I use UGJK4 or newer, random "no service" on the lock screen with the "circle with a line through it" in the notification bar. as of right now (I believe) there's no known issue why some modems fail on only some hardware. I have a batch 1006 and it works fine right up until the UGJK3 modem, while some people seem to have absolutely no issues with modems (even the newest ones like UGJL2 and TLJL3). basically, if you're running a JPY based ROM, flash JK3 and see if that helps... if that doesn't, go back to a stock captivate ROM of some sort with a stock modem so you don't have these issues (never happened to be me on JI6/JJ4)
Try changing ur SIM card. That could solve the issue.
In my case, it is original stock all the way. The SIM card is fine because I switched it into two different at&t phones and had no issues at all. Right now my Captivate is a gloried camera and MP3 player.
I forgot to subscribe to my own stinking thread! I know this is stale now, but here goes.
I'm running stock froyo, rooted. At the time of the original post I was using it completely stock on eclair. Shortly after the post, it stopped happening and haven't had issues since. I still don't know what caused it. Thanks for all the input though.
Sent from my SAMSUNG-SGH-I897 using XDA App
NvigR8 said:
I forgot to subscribe to my own stinking thread! I know this is stale now, but here goes.
I'm running stock froyo, rooted. At the time of the original post I was using it completely stock on eclair. Shortly after the post, it stopped happening and haven't had issues since. I still don't know what caused it. Thanks for all the input though.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Happened to me a year or so ago on a different phone. Turned out they were upgrading the tower closest to me with new hardware and were shutting it down intermittently to work on it.
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
brandon827 said:
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
Click to expand...
Click to collapse
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
sliderocket22 said:
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
Click to expand...
Click to collapse
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
homeslice976 said:
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
Click to expand...
Click to collapse
Man, I'm glad I'm not the only one having this problem. I thought my phone was defective at first, and now I don't feel so crazy anymore. My sister was furious with me, I had to pick her and her boyfriend up from DIA yesterday to take her to Copper Mountain to snowboard with my girlfriend and myself, and she called me 4 times and I didn't receive a single one. I wonder if it has anything to do with HSUPA being enabled on the phones, but at this point I'm just ready to give up root and go back to stock. I don't make tons of calls, but I'd like to be able to when I need to, and for my phone to not hang up on me in the middle of one. I have noticed though it's particularly bad for me when I'm on bluetooth.
I was also having those problems
I am using Revolution 4G 2.1. I'm in the process of trying to get the problem figured out. Stock rooted rom had problems for me because you couldn't set it to GSM only, and that's the only way I've found to make the phone reliably work as a phone.
If anyone can figure it out, I'd love to know what causes it. I've been poking around myself, but haven't come up with anything worthwhile. I suppose I'll flash a different rom and try that.
Sent from my Desire HD using XDA App
Anyone found any clue as to why this happens? I've searched the dev forums but nobody seems to mention this, which makes me wonder if most people have this problem.
Sent from my Desire HD using XDA App
I have never had this problem. Running a rooted stocker.
Sent from my Desire HD using XDA App
It happened to me again last night. Still had data but lost the ability to make/receive calls. I switched network to GSM only, the data switched to EDGE, and i was able to make/recieve calls. Turned back to GSM/WCDMA, no calls. Rebooted, no calls. Turned back to GSM only, calling functionality returned. I did another full wipe, installed AR 2.1, sound fix, apache 1.6 kernel, and calling is restored when connected to HSDPA/WCDMA. Has been working fine for the last 12 hours. I'll keep you updated. I don't know why it's doing this, and it doesn't make sense as to why a wipe would fix it. The first time this happened I was runing the stock radio. Last night when it happened i was running the recommended radio in the AR thread (M2). I've now switched back to stock this time...let's see what happens
Edit: I am also glad to know I'm not the only one having these issues...maybe someone a LOT smarter than I am can figure it out. It's annoying to have to have a slow data connection to have a reliable voice connection. The last Android I had (LG GW620 Eve), also did this from time to time, but I just blamed it on the fact that it was a POS. My voicemail actually went like this "This is Greg. I probably have no idea you called me just now, so please leave a message and I'll get back to you"
Edit: mike1986 (android revolution developer) just chimed in in his thread and stated these issues should be fixed in version 3.0 set to be released soon. Is anyone else that's having these problems NOT running Revolution?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
I had this problem when I first rooted (running Inspire 4G Stock Rom w/Root, HSUPA, and Sideloading from the development section) I installed Android Revolution 2.1 and it went away.
I know from my captivate days that sometimes a ROM just hiccups and a fresh flash can fix the issues. I don't know if this is the same with HTC, but it's all android so It's plausible.
Does anyone know if theres bug in ics for rogers users where incoming texts are timestamped 4 hours earlier?
Download the app SMS Time Fixer, free in the market place, works everytime, I used it on all of my unlocked phones which gave me this problem.
Sent from my Lumia 710 using Board Express
OFWGKTADGAF said:
Does anyone know if theres bug in ics for rogers users where incoming texts are timestamped 4 hours earlier?
Click to expand...
Click to collapse
It's been a "known issue" for some Rogers phones for a long time... regardless of Android version actually. It does seem to be ROM dependant but I haven't discovered what exactly causes it... it has something to do with the way Rogers sends the timestamp. Across a few different Samsung phones my experience has been... I had the problem on stock Eclair and used "SMS Timefix" to correct, then an update to the ROM fixed it and it was OK, then Froyo brought it back, and I used timefix again, then I flashed Darkky and it was gone, then I bumped to the SGSII LTE and it was OK with the stock ROM but back to timefix on every flashed ROM I used... When it's broken it seems to just treat your phone as if it's in Grenwich Mean Time regardless of what your timezone settings are (your offset will be the exact opposite of your actual timezone).
Sadly I've been unsuccessful at getting an ICS ROM working on my phone, so I'm back to running stock Rogers GB one and the stamps are correctly interpreted.
Oh DISCLAIMER... I have nothing whatsoever to do with the app other than being a user whenever I have a ROM that suddenly makes my phone think I'm sitting on the International Date Line.
I understand there are some other international carriers who's timestamps seem to function the same... SMS Timefix is a kludge but it works perfectly when there's a disconnect between the received timestamp and the actual time. I know following an SMS conversation is REALLY difficult when the other party seems to be texting from hours in the past (or future depending on where you are).
Hi all,
I'm running cm10 currently, have been using it for a long time. I have the 2.40 telestra radio installed, never had an issue in the past with it.
After flashing the new 0127 weekly from cm10 (4.1.2), I cannot make or receive any phone calls. SMS works fine, data works fine. I have recovered to an old backup that was working fine, still cant call/receive calls. The call begins, 2 seconds of nothing then says call ended. I have flashed a brand new ROM, recovered to 3 different ROMs (MIUI,venom,AOKP) all the exact same issue, I did a clean install, Ive tried different radio's 2.09/2.40 (only ones that seem to work well data wise for me), I've done everything except flash the stock ruu (which I'm having trouble finding documentation on, I believe the easiest way is with the one click tool, scared to flash the wrong ruu though )
My screen has a crack in it, not sure if its relevant as the issue began after I flashed the new nightly, I don't understand how this could be physical.
All in all, I'm stuck can't use the calling feature at all. The mic still works, tested with a recording app. I'm just looking for a suggestion as a next step.
The phone is a rogers HTC one x, please let me know any suggestions or if anyone has encountered this before.
Thanks in advance guys,
Josh
wilkins502 said:
Hi all,
I'm running cm10 currently, have been using it for a long time. I have the 2.40 telestra radio installed, never had an issue in the past with it.
After flashing the new 0127 weekly from cm10 (4.1.2), I cannot make or receive any phone calls. SMS works fine, data works fine. I have recovered to an old backup that was working fine, still cant call/receive calls. The call begins, 2 seconds of nothing then says call ended. I have flashed a brand new ROM, recovered to 3 different ROMs (MIUI,venom,AOKP) all the exact same issue, I did a clean install, Ive tried different radio's 2.09/2.40 (only ones that seem to work well data wise for me), I've done everything except flash the stock ruu (which I'm having trouble finding documentation on, I believe the easiest way is with the one click tool, scared to flash the wrong ruu though )
My screen has a crack in it, not sure if its relevant as the issue began after I flashed the new nightly, I don't understand how this could be physical.
All in all, I'm stuck can't use the calling feature at all. The mic still works, tested with a recording app. I'm just looking for a suggestion as a next step.
The phone is a rogers HTC one x, please let me know any suggestions or if anyone has encountered this before.
Thanks in advance guys,
Josh
Click to expand...
Click to collapse
Got it fixed, I ended up speaking with tech support from my carrier, they "refreshed my number" on the network, solved the issue. I ended up going through the entire RUU rewrite process for no reason. Just an FYI for other people out there, start with tech support first, ended up being an issue with the network, not my software.
i started a thread called " Data once lost wont re-connect" back in June
I still don't know what the problem is caused by but it's definitely lollipop related.
i have possibly tried every lollipop rom there is to try and it's always the same.
i'm a driver and cover the whole of Scotland, sometimes some obscure places
with no DATA signal..Once the exclamation mark was up then only a reboot would
sort out the problem and reconnect the DATA. I have tried 3 phones and they all
have the same problem. Now all the phones are on the Three network so it could
well be an incompatability between Three and lollipop??!
I have wiped the phones and put in 38r and 44s and i have not had to reboot
any of the phones this week so it looks like the problem is not apparent on KitKat.
I'm starting to enjoy the Oneplus once again !!!nearly had the samsung edge a couple
of weeks ago!!!
I was thinking that i might of been the only one with this problem untill it happened to the wife's
phone when on holiday.The daughter gave up her phone and went back to an iphone so tried hers on lollipop
and the same problem .
Hope this might help somebody out there it's been driving me insane and although i have had to forget lollipop
and go back to KitKat the phone is now back to being usable and i get my emails and whatsapp when i'm supposed to
Paul
I use Calkulin's ROM, currently on the latest, with EE and don't get this problem.
I drive a lot for my job as well, so would expect to see this if it existed.
I don't know what it could be. It all points to the Three network but why does it not happen on KitKat? There must be some issue with Three/Oneplus and Lollipop, especially as the problem is there on all three phones i have tried. After months of trying Lollpop ROMS and different Kernals i am totally stumped, but revert the phones back to 38r or 44s and everything is ticketyboo !!
I'd be tempted to put one of the phones on Calkulin's ROM, then stick an EE SIM card in (just get a PAYG for testing) and compare the results.
I presume you have double-checked the APNs are definitely the same?