This is really frustrating! :evil:
The signal on my phone shows good reception, but meanwhile the phone is off. When people call me, they get forwarded to my voice mail, although the phone never rang in the first place!
Does anyone else have this problem, and better yet... how do you fix it?
Thanks!
when you ask the same question in more then one forum all you get is
that you push out a question which may not have been answered yet
and thereby limit the posiblity of the person seeking help ever
being found by somebody who got answers
please dont! think of the children
have you checked the divert setting in the "phone" control panel, perhaps it is set to forward all calls to voicemail??
if you can make outgoing calls, then it is a call forwarding problem.
This used to happen to me also, and also happend to my friend using an mpx. We also were both on Tmobile in the states so I thought it was some network problem either on tmobiles end or PPC. However this has not happened to me since I upgraded to the 1.72 rom
Rudegar, that was an honest mistake... first time I post on here.
As for the phone problem, this happens on its own. For example, I'd have my phone on, use it, then hang up. The phone now is still on, but 'off the hook'. A while later someone would call and get forwarded to my voice mail because the phone is off... on its own. I don't know if I'm explaining this well enough but that's what's happening. I will try upgrading, but how does one do that?
Thanks!
no problem happens to the best of them or so they've told me
Hi I am currently a T - Mobile customer and when I originally bought my Samsung Galaxy S2 with the company, I thought I could take advantage of using both the T - Mobile network and 2G services of the T - Mobile Orange Network.
However after successfully using it for the first 2 weeks, after my KE7 firmware update, I have an unbranded phone, it did not connect to the network anymore, stating, even if I manually select T - Mobile Orange in GSM mode only, Cannot registor with network, Unable to connect, then it states it is registered and yet I have emergency calls only stated and not either T - Mobile or even T - Mobile Orange. Then it will not connect to either network manually until I restart the phone.
I have since flashed my phone with various other firmwares, am currently on cognition s2 1.13, it's a great Rom, and still the same thing occurs.
I have contacted T - Mobile, they can't fix it, I have took the phone to a Samsung Repairer and they couldn't see anything wrong, stating it was a fault with Orange, as the guy in the shop's T - Mobile branded Galaxy s2 did the same.
Anyone solved the mystery, or is able to explain the issue to me?
It's doing my nut in, I have had phones like these for years, flashed them and enjoyed them, and usually work things out for myself, my last phone was an Samsung I8910, which was great with custom firmware support and I must say the Galaxy s2 is by far my favourite ever phone, but even my Samsung Omnia I8910 works properly on T - Mobile and Orange, and the latest and greatest phone won't!!
Have you tried flashing a different modem? Seeing as the cognition rom is based on I9100XXKG1, I know of a couple of forum members that have had trouble with the KG1 modem, and had to revert to the KF2 modem.
Worth a try? It won't wipe you phone of anything daft either.
List of official modems: http://forum.xda-developers.com/showthread.php?t=1131950
Before you do anything, can you dial*#1234# and just check what phone software is installed?
Thanks for the option Unfortunately I have tried the KE2, KE7, KF2 and KG1 Modems now, none of them have worked. It is really bizaar as the bloody thing works really well on T - Mobile, when there is coverage, plus the 3 and H is great speeds when they are in coverage, it just won't switch to Orange
mattisfaction said:
Thanks for the option Unfortunately I have tried the KE2, KE7, KF2 and KG1 Modems now, none of them have worked. It is really bizaar as the bloody thing works really well on T - Mobile, when there is coverage, plus the 3 and H is great speeds when they are in coverage, it just won't switch to Orange
Click to expand...
Click to collapse
one moment, I'm on t-mobile aswell.
text YES to 2121.
Homer moment: Doh, you cant text can you?
Just for reference, I'm with Orange and in my network list I have both "Orange" and "Orange and T-Mobile". I can connect to the Orange one fine, but not to the other one. It does switch to T-Mobile sometimes though. I've seen it do it.
Hi again, I have text yes to 2121, and it was working on my phone before. So yours has no issues then?
mattisfaction said:
Hi again, I have text yes to 2121, and it was working on my phone before. So yours has no issues then?
Click to expand...
Click to collapse
No, but I remember I used to have an everythingeverywhere app in data/private, which is no longer there.
I just texted yes to 2121 and now it lets me register on orange aswell as t-mobile.
stoney73 said:
No, but I remember I used to have an everythingeverywhere app in data/private, which is no longer there.
I just texted yes to 2121 and now it lets me register on orange aswell as t-mobile.
Click to expand...
Click to collapse
I just looked in data/private and do not have an everythingeverywhere app, plus I have just again text 2121 and still cannot use the orange network
Cheers for your advice though mate
johncmolyneux said:
Just for reference, I'm with Orange and in my network list I have both "Orange" and "Orange and T-Mobile". I can connect to the Orange one fine, but not to the other one. It does switch to T-Mobile sometimes though. I've seen it do it.
Click to expand...
Click to collapse
Cheers for the information
Unfortunately if I let mine automatically switch network, it switches to emergency calls only if I am out of a t mobile network range, not orange, and it used to switch to orange no problem
Then when it is in emergency calls only, I have to turn it on and off to get it to work at all, as it will not register back to T mobile
My last attempt......when you go into wireless/mobile network settings, is data roaming ticked?
stoney73 said:
My last attempt......when you go into wireless/mobile network settings, is data roaming ticked?
Click to expand...
Click to collapse
Yes it is, cheers for all your help. It's very frustrating and I can't fathom it out, so cheers for trying yourself
You don't need data roaming ticked in order to use Orange. T-mobile and Orange are both considered 'home' networks.
I'm on T-Mobile without data roaming ticked and it switches automatically to Orange without any issues. Might be worth phoning t-mobile up and seeing if there's some sort of issue with your account.
I installed Lite'ning Rom and found that I couldn't connect to Orange on my unlocked tmobile sim. Turned out that I had the "com.orange.authentication.simcard.permission" apk missing.
Downloaded it here:- http://www.contentsd.nl/apk/SimServicePermission.apk
and installed it with titanium and registered ok on orange.
Hope this helps.
dirobeshploppy said:
I installed Lite'ning Rom and found that I couldn't connect to Orange on my unlocked tmobile sim. Turned out that I had the "com.orange.authentication.simcard.permission" apk missing.
Downloaded it here:- http://www.contentsd.nl/apk/SimServicePermission.apk
and installed it with titanium and registered ok on orange.
Hope this helps.
Click to expand...
Click to collapse
I've just checked my simfree phone and it has the above apk installed. How on earth did you figure out you were missing this apk??
Joey2o11 said:
I've just checked my simfree phone and it has the above apk installed. How on earth did you figure out you were missing this apk??
Click to expand...
Click to collapse
Was browsing the list of stock apk's here:-
https://spreadsheets.google.com/spreadsheet/pub?hl=en_US&hl=en_US&key=0Ag43oj7rLQP4dENZcmhGN0ZUa3pHSENVeXlqUm5vV0E&single=true&gid=0&output=html
and noticed the "com.orange.authentication.simcard.permission" reference and when I checked via titanium it wasn't installed so I tried it and it sorted out my problem.
Hiya guys. Sorry to jump on this thread but I am having the same issue as OP. I'd just like to give you an update on what I know so far. It is a nightmare trying to speak to someone at T-Mobile who actually knows whats going on, but I was persistent and got through to an engineer who said that they are having transmitter problems in east anglia and surrounding areas...not sure if you are in that area or not. Unfortunately all the engineer said is that they are working hard to a. figure out what the problem is ang b. fix it! He also could not give me an ETA and said that the only way to get back onto the network is to reboot the phone a couple of times. Not ideal, but I though it was something to do with the VillainRom that I flashed...so here's stupid me flashing stock, bricking/unbricking the phone etc etc only to find out later that its not the phone...on the plus side I have amazing battery life now haha who would have thought ey!
Anyways, hope this information is useful to you all.
Steph
It is not a ROM issue - it is a T-Mobile/Orange fault
stephan.pieri said:
... I was persistent and got through to an engineer who said that they are having transmitter problems in east anglia and surrounding areas...not sure if you are in that area or not. Unfortunately all the engineer said is that they are working hard to a. figure out what the problem is ang b. fix it! He also could not give me an ETA and said that the only way to get back onto the network is to reboot the phone a couple of times. Not ideal, but I though it was something to do with the VillainRom that I flashed...so here's stupid me flashing stock, bricking/unbricking the phone etc etc only to find out later that its not the phone...on the plus side I have amazing battery life now haha who would have thought ey!
Anyways, hope this information is useful to you all.
Steph
Click to expand...
Click to collapse
Absolutely right Steph, it is not ROM related.
T-Mobile have acknowledged that there is a problem with registering T-Mobile customers on T'Orange cell towers.
I've been having this issue for a couple of weeks now (also in East Anglia), and after a lot of perseverance I got transferred to Level 2 support (Technical Support - not Customer Support) last Monday. They said there was a 'rectifier problem' on a mast in Henny Street, near Sudbury, Suffolk at the end of June and it has had a knock-on effect on other masts in the area. It was/is a level 2 priority for fix.
I wasn't happy with that explanation as it happens all over Suffolk!
Still with the issue on Thursday, I called them again and got straight through to Level 2 as they had marked my account as an on-going problem which Customer Support (in the Philippines) couldn't handle.
While explaining in detail the 'Your SIM does not allow you to connect to this network' problem the Guy I was talking to received an internal notification that they were aware of issues registering on T'Orange cells, that they'd known about it for 72 hours, have no idea what is causing it, and no eta to fix.
I've been using a forced connection to T'Orange for the last couple of days (poor T-Mo signal in house which always caused it to hunt for T'Orange anyway). Downside of course is that it won't get a 3G signal when forced into T'Orange mode.
Still happening today so need to give them another prod...
Oh, and I found this thread searching for answers - I don't have a Galaxy S, I have a Desire. Further proof that it isn't ROM related.
I'll update when I find out more from them.
Aaron
Just spoken to them again, problem is still on-going, they are still investigating and looking for more samples of the problem to try and isolate the issue. In light of that I would suggest anyone else having this to phone them and ask for Technical Support and register the fault - the more samples they have, the better chance of getting it resolved.
In other words, they still don't know what's causing it or when they'll fix it.
hi guys, im new here. here is my problem:
i have a brand new samsung galaxy s3 and im having a problem with the s voice application. it works fine on data conection, but when i switch to wifi i get "network error. please try again". this is the second phone the dealer gave me. the previous one was giving the same error, i returned and got a new one and still having same problem. its a non rooted international version.
can anyone help me with this???many thanks
zeynl said:
hi guys, im new here. here is my problem:
i have a brand new samsung galaxy s3 and im having a problem with the s voice application. it works fine on data conection, but when i switch to wifi i get "network error. please try again". this is the second phone the dealer gave me. the previous one was giving the same error, i returned and got a new one and still having same problem. its a non rooted international version.
can anyone help me with this???many thanks
Click to expand...
Click to collapse
S voice is crap m8, at least it is for me cos i'm a scouser (liverpool) but it isn't perfect anyway, not something that you should return your phone over, but if it's bothering you then i would clear all defaults and maybe try a different wifi connection, it would be bad if it was down to a router needing rebooting lol.
Mines fine on either and i think a problem like this persisting over two phones means that either its a horrible coincidence or something else is ado.
Check your wifi, or try someone elses.
dladz said:
S voice is crap m8, at least it is for me cos i'm a scouser (liverpool) but it isn't perfect anyway, not something that you should return your phone over, but if it's bothering you then i would clear all defaults and maybe try a different wifi connection, it would be bad if it was down to a router needing rebooting lol.
Mines fine on either and i think a problem like this persisting over two phones means that either its a horrible coincidence or something else is ado.
Check your wifi, or try someone elses.
Click to expand...
Click to collapse
s voice its not a must for me. but still why cant i get what i payd for?lol...especialy after samsung making all that marketing about the s3 and the svoice app.
i tryed with 3 difrente wifi conections all with a good strong signal.cleared all the data and all on the s voice app but nothing. now im just pisd with samsung. went to their costumer care centre and they say they are still trying to find out what the issue is as several other users have reported this error
Hello All,
I have been looking around and seeing if anyone else is experiencing the same issue I have. But I have not had much luck. I have seen similar cases, but for whatever reason, some of the workarounds found that worked for others have not been successful for myself, or are temporary.
For the past three months, I have been experiencing an off and on issue where I am unable to receive texts, but I am able to send out text. And it is something that I would not realize until people actually notify me, or it is awkwardly silent on the "texting front", which makes me second guess myself. Almost every other week or two weeks this has occurred. At the time, I am running Darky's 8.8 [4.1.2] ROM for the i9300. I have tried rebooting, taking out the SIM, re-flashing Darky and re-flashing Stock (full wipe, etc), and replacing my old SIM with a new one. None have been successful thus far. The only success I have found is that inserting my SIM in a different phones allows the text to flow through almost immediately. I would then place the SIM back in the i9300 and any new texts sent I would receive immediately. After a week or two, it randomly just stops receiving text again, and the cycle continues.
I was wondering if whether this may be a bug with the Android OS itself? I have seen a few posts in regards to SMS being handled by Jelly Bean, but I am not 100% sure if my issue would fall in the same boat. Or if it is possibly faulty hardware? Or some kind of network issue. My network is AT&T, but I'm ruling out a network issue since I am able to receive text almost instantaneously on other phones.
Any information, advice, or help would be greatly appreciated.
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
JJEgan said:
Its not a bug .
Usual reason is wrong MMS message centre settings or network settings .
jje
Click to expand...
Click to collapse
I've verified that the MMS APNs and SMS settings are correctly configured to AT&Ts network. If it were incorrect from the beginning, I would not get text messages (or MMS) at all. But in this case, it is intermittent and only resolved when I get to "unload" the text messages on to another device.
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
b-eock said:
Same thing happens to me (why I had to use my upgrade to buy a phone from them -_-) I'm using a S2 for now... it sucks when you have been on the S3. Their excuse for not being able to help me was "Its an international phone, therefore may not work with our network." That's freaking BS. It worked for 6 months before this issue came up. New micro SIM card is the only temporary solution for now. When I have time. I'm going up there or calling help line. Gonna file a complaint and mention I might be leaving service with them or I can say legal action will be taken since they are denying me a service I'm paying for. They should start helping by them. I don't abuse their services. I don't tether. I don't cheat them in any way. Its retaarded.
Click to expand...
Click to collapse
Ahh! Thank you b-eock! I don't mean this in the wrong way, but I'm glad that I'm not the only who has experienced this. When this occurred to you, were you on some version of 4.1.2? From what I can remember, this issue never came up until I upgraded from 4.1.1 to 4.1.2. Just trying to find some kind of trend here...
I have had to call up AT&T a number of times regarding this issue. And each time they were of no help. Although they were able to confirm that everything on their end of setup correctly, I got the same BS that you got. And they even gave me the whole baloney that I should upgrade so that they can help assist me better and that since it is not their branded phone, it may not be fully compatible.
I really do not want to give up on this. And I definitely want to find a solution. So I am hoping there is a lucky one out there that has tried different ways of getting fixed. Whether that be trying a new ROM, or downgrading from Jelly Bean to ICS, etc.
Came up a few weeks after I upgraded to 4.1.2 but there isn't really a connection between that. It worked before. Its just random crap. And them telling us everything is good on their end, that's complete BS. They don't know what's going on behind their computer screen.
Same exact thing happens to me. It's ROM dependent i'm thinking. Samsung roms from other countries do it the most for me. Has done it on AT&T and AT&T with StraightTalk. Experiencing it on Purelok HD v3.1 right now. I love this rom but im probably going to go AOSP/AOKP as I don't experience it on those kind of roms.
Camera just isn't the same without the Samsung software to me.