I have a problem in my phone. If i send a text(SMS) to a person it gets delivered to a completely different person, Whose thread is not even present in the messaging app.I have tried factory reset, wipe data, root/unroot etc.. It did not work so i finally approached samsung, They claimed it was a problem with the motherboard and they replaced it. Now five days after getting back my phone with a new motherboard the problem has returned.
Any ideas why this is happening? Anyone else has this issue?
Also the bug returns 5 days after the factory reset/wipe/reinstalling andriod. Not immediately.
Phone is I9020t.
Well i know Sprint, we can do *#*#data#*#* in the dialer and then choose edit. Then under "others" MMSC url is an option and has an address. Get with another tmobile member and see if yours says the same. Might not even have this option. I would check it out
snandlal said:
Well i know Sprint, we can do *#*#data#*#* in the dialer and then choose edit. Then under "others" MMSC url is an option and has an address. Get with another tmobile member and see if yours says the same. Might not even have this option. I would check it out
Click to expand...
Click to collapse
Am in india and that ## thing doesn't work.
Have you check with your service provider?
snandlal said:
Have you check with your service provider?
Click to expand...
Click to collapse
Yeah, The problem is not with the service provider, Because i put my sim card in other Android phones and i did not experience the problem. So think the problem is only on the phone.
That is really strange. I dont know much about GSM. Seems like the phone isnt loading all your info from your sim card
snandlal said:
That is really strange. I dont know much about GSM. Seems like the phone isnt loading all your info from your sim card
Click to expand...
Click to collapse
Even if i put other sim cards in the phone, The same problem arises.
Very strange!
saranyan said:
I have a problem in my phone. If i send a text(SMS) to a person it gets delivered to a completely different person, Whose thread is not even present in the messaging app.I have tried factory reset, wipe data, root/unroot etc.. It did not work so i finally approached samsung, They claimed it was a problem with the motherboard and they replaced it. Now five days after getting back my phone with a new motherboard the problem has returned.
Any ideas why this is happening? Anyone else has this issue?
Also the bug returns 5 days after the factory reset/wipe/reinstalling andriod. Not immediately.
Phone is I9020t.
Click to expand...
Click to collapse
What version of android are you running? I know it was a bug with gingerbread that was fixed on 2.3.4
Sent from my PC36100 using XDA Premium App
Rem3Dy said:
What version of android are you running? I know it was a bug with gingerbread that was fixed on 2.3.4
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I am running 2.3.4. I thought the bug was fixed in 2.3.3. itself. I know that the initial versions had the bug.
Related
It updated OTA on it's own and was working last night. This morning I looked at my phone and it was connected. I moved it and it lost signal and hasn't gotten it since. I can't force it to connect, will get roaming but roaming in this area is emergency only.
AtomicPC said:
It updated OTA on it's own and was working last night. This morning I looked at my phone and it was connected. I moved it and it lost signal and hasn't gotten it since. I can't force it to connect, will get roaming but roaming in this area is emergency only.
Click to expand...
Click to collapse
Slight update, no APN settings are on here, won't save when I try to add them. Well it saves but then it still shows none.
Its busted, reflash
Sent from my Nexus S using xda premium
xsteven77x said:
Its busted, reflash
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Just did that. Still nothing.
Ok I've flashed 4.0.4 then CWM to 4.1.1 and nothing. Flashed 4.0.4 and nothing then flashed GB on it and nothing. I'm out of ideas.
Maybe you didn't save properly? Don't press back when done inputting everything, but press menu>save.
If that doesn't work, there's a remote possibility it's a problem with the SIM card. You might want to go to your carrier store and ask for a new one; in my experience this is usually free. Other than that, if flashing a whole new ROM doesn't fix it, I have a hard time understanding how it could be anything other than a hardware issue.
zorak950 said:
If that doesn't work, there's a remote possibility it's a problem with the SIM card. You might want to go to your carrier store and ask for a new one; in my experience this is usually free. Other than that, if flashing a whole new ROM doesn't fix it, I have a hard time understanding how it could be anything other than a hardware issue.
Click to expand...
Click to collapse
It was the sim card. I wished I would have thought of that before I wiped everything though. Oh well I got a clean install and learned a lesson. Never skip step 3...
After flashing between a couple ROMs the other night, I noticed under 'About Phone' that my phone number is different (it says 000-000-5777). After doing some research and coming to find out about this IMEI issue, I checked to make sure that my IMEI was still in tact, which it is (and I went ahead and backed it up). The only thing that is different is my phone number isn't showing up correctly.
I can still receive calls and MMS and I am getting my 4G service. Is this something worth worrying about or should I just forget about it as long as my IMEI is still there?
Thanks ahead of time for any input.
Atwooooood said:
After flashing between a couple ROMs the other night, I noticed under 'About Phone' that my phone number is different (it says 000-000-5777). After doing some research and coming to find out about this IMEI issue, I checked to make sure that my IMEI was still in tact, which it is (and I went ahead and backed it up). The only thing that is different is my phone number isn't showing up correctly.
I can still receive calls and MMS and I am getting my 4G service. Is this something worth worrying about or should I just forget about it as long as my IMEI is still there?
Thanks ahead of time for any input.
Click to expand...
Click to collapse
Read through the following thread regarding someone with a similar issue who fixed it: http://forum.xda-developers.com/showthread.php?t=2042116
pdykstra said:
Read through the following thread regarding someone with a similar issue who fixed it: http://forum.xda-developers.com/showthread.php?t=2042116
Click to expand...
Click to collapse
I saw that thread, but was just wanting to know if my phone number not being displayed correctly is anything to worry about if I am still getting service. I didn't know if it was something that needed to be fixed or just an effect of the ROM.
Which ROM are you running? If your still getting service, then it's probably not an emergency. I'm not sure if it will cause a real problem for you or not, but personally I would fix it to be on the safe side. If you odin back to Root66, backup your data, and then enter the re-provision code you should be back to normal. Then you could re-flash whatever ROM you are currently on.
If it's not causing you any problems, then it's up to you whether or not you want to spend the time on a fix.
and iitabon
pdykstra said:
Which ROM are you running? If your still getting service, then it's probably not an emergency. I'm not sure if it will cause a real problem for you or not, but personally I would fix it to be on the safe side. If you odin back to Root66, backup your data, and then enter the re-provision code you should be back to normal. Then you could re-flash whatever ROM you are currently on.
If it's not causing you any problems, then it's up to you whether or not you want to spend the time on a fix.
Click to expand...
Click to collapse
I am running Liquid Smooth Jelly Bean REV9.
When you say root back to Root66, what exactly is Root66 if you don't mind to clarify? And also, what is the provision code?
Thanks for your help.
Atwooooood said:
I am running Liquid Smooth Jelly Bean REV9.
When you say root back to Root66, what exactly is Root66 if you don't mind to clarify? And also, what is the provision code?
Thanks for your help.
Click to expand...
Click to collapse
Root66 is the original stock, rooted image of the initial firmware that shipped with the Verizon Galaxy S3. It can be downloaded from here and must be flashed through ODIN: http://forum.xda-developers.com/showthread.php?t=1762204
The re-provision code is done by typing *2767*3855# into the dialer. It will factory reset your device, so make sure you back up your data before entering it.
I can't guarantee this will fix your issue, but has fixed other similar problems in the past. The only reason you need to go back to Root66 is because Samsung removed the re-provision code from more recent builds because it is a security issue (the code can be embedded on websites to reset your device without you opting to do so).
pdykstra said:
Root66 is the original stock, rooted image of the initial firmware that shipped with the Verizon Galaxy S3. It can be downloaded from here and must be flashed through ODIN: http://forum.xda-developers.com/showthread.php?t=1762204
The re-provision code is done by typing *2767*3855# into the dialer. It will factory reset your device, so make sure you back up your data before entering it.
I can't guarantee this will fix your issue, but has fixed other similar problems in the past. The only reason you need to go back to Root66 is because Samsung removed the re-provision code from more recent builds because it is a security issue (the code can be embedded on websites to reset your device without you opting to do so).
Click to expand...
Click to collapse
Thanks for your help. After flashing back to stock, rooting/unlocking again and flashing back to Liquid Smooth, my phone number is appearing correctly.
I guess I spoke too soon. After a reboot, I noticed that my phone number under About Phone was displayed as "Unknown", and after rebooting a second time, it was displaying the number it did before (000-000-5777). Every time I reboot my phone, I get presented with an endless activation screen that I have to either hit the physical home button or do the 4 corner tap method to get rid of. I'm starting to think that the activation screen is what is causing this issue, considering after I reflashed Liquid Smooth and wasn't presented with the activation screen and my phone number was appearing correctly.
I guess this isn't really anything to worry about since I am getting full functionality out of my phone. But if anyone happens to have any input on this issue, feel free to chime in.
That's strange.. is it possible your SIM card is going bad?
Not the sim. Try rebooting but dont unlock the screen until it has a data connection. Once it does go see if the number is still the same or if its your number
Sent from my SCH-I535 using xda app-developers app
pdykstra said:
That's strange.. is it possible your SIM card is going bad?
Click to expand...
Click to collapse
Doubt it, I've only had the phone a couple weeks.
vabeachfc3s said:
Not the sim. Try rebooting but dont unlock the screen until it has a data connection. Once it does go see if the number is still the same or if its your number
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I always let the phone acquire a connection before unlocking, but am still presented with an activation screen and the phone number is still messed up. It hasn't been affecting my data or calls so I guess there is no sense in fooling with something so minor.
Thanks to both of your for your suggestions and input.
Mine does it too man.
Sent from my SCH-I535 using xda app-developers app
Try another rom and see if you get the same problem
Sent from my SCH-I535 using xda premium
Watoy said:
Try another rom and see if you get the same problem
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
He will. Alot of defective gs3s around.
Sent from my SCH-I535 using xda app-developers app
I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!
In case of emergency!
...Awesome... said:
In case of emergency!
Click to expand...
Click to collapse
I dropped my s3 in some water and quickly grabbed it, and dried it off. Everything seemed to be working ok, but then i noticed that it's acting like i don't have my sd card in it when i do. My wifes card gets recognized right away when i put it in, so i think my sd card is no good. Any suggestions on how i can recover data from it?? Thanx
ryanallaire said:
I dropped my s3 in some water and quickly grabbed it, and dried it off. Everything seemed to be working ok, but then i noticed that it's acting like i don't have my sd card in it when i do. My wifes card gets recognized right away when i put it in, so i think my sd card is no good. Any suggestions on how i can recover data from it?? Thanx
Click to expand...
Click to collapse
So your SD card doesn't read but hers does? And yeah then just get a new SD card go on a computer take your files off of it and put em back on the new SD card
Sent from my SCH-I535 using Tapatalk 2
Hi,
New to the S3 and this rom. Root, flash went well, and so far, I'm loving this rom. One problem that is stumping me is this:
Using ADW launcher, have a direct dial short cut to voice mail. The voice mail contact is set up to dial *86 ,,xxxx, so with one tap, I can call vm and access messages.
However, the keyboard then becomes non responsive. I can't delete or save messages, and if I have multiple messages, can't get to the next one.
Any suggestions on how to work around this appreciated.
I'm running the 3.2 beta version of LS, and really only have this, and one other minor issue.
Thank you.
Still haven't solved this, but here's more clarification:
Phone is running LiquidSmooth 4.2.1m v2.1m beta 3.2
1. Using a 'direct dial shortcut. the rom dialer has a contact set up named voicemail, that is programmed: *86;,,XXXX. When I hit the direct dial shortcut, voicemail is dialed, xxxx is sent, and I can hear my first voicemail. The problem is the dialpad is non responsive. So, I can't save or delete the first voicemail, nor can I proceed to listen to the next one.
If I dial *86, and enter the password manually, then the dial pad works.
Even if I dial any contact withGoDialer, then, open keyboard to dial and extension, I get the stock dialer.
I drive a lot, and need as few distractions as possible. Any suggestions on how to fix this would be greatly appreciated.
Thank you.
Have u tried using a different launcher just to be sure its not hardware/ROM related it might be the launcher?
Sent from my HTC One S using Tapatalk 2
--------------If you like puzzle, tackle this---------------
I tried pretty much everything on the internet before posting here.
My stock/no root phone started bootlooping. So I used Odin and root66.tar to get it back. Everything seemed to be good. After I got 3 updates:1) 30mb, 2) 60mb and 3) JB updated OTA. After 60Mb update my phone said Samsung and shows unlocked lock. After JB update my phone bootloops again.
I though it it was a bad update and reflashed stock no root 4.0.4 and OTA did the same thing.
I tried the gs3 tool to flash the recovery and it always fails.
I would appreciate any help.... I have been dealing with this non sense for the past 24h.
...Awesome... said:
Have u tried using a different launcher just to be sure its not hardware/ROM related it might be the launcher?
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Yes. I've been using ADW launcher, tried it with Nova, got the exact same result.
Alright, I'll try here. So, I'm on cleanrom 5.6. As far as I can tell everything is working, and there aren't any actual problems, but the phone doesn't know what the network is in settings and and when I drag down the notification bar it doesn't say it at the bottom. Anyone have an idea?
Sent from my SCH-I535 using xda app-developers app
MEID
does your cellular service connect? Also you are on verizon right? and did you do a dirty flash of cleanrom 5.6?
LtZKilla said:
Alright, I'll try here. So, I'm on cleanrom 5.6. As far as I can tell everything is working, and there aren't any actual problems, but the phone doesn't know what the network is in settings and and when I drag down the notification bar it doesn't say it at the bottom. Anyone have an idea?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
jwattt said:
does your cellular service connect? Also you are on verizon right? and did you do a dirty flash of cleanrom 5.6?
Click to expand...
Click to collapse
Yeah, my cell service connects and I can text and call. It just doesn't seem to have any idea that my carrier is verizon and it kinda seems odd.
Sent from my SCH-I535 using xda app-developers app
I am trying to install the stock systemui.apk file on my phone after I screwed up and flashed the wrong one, but installation always fails. I have moved the .apk to the /system/app folder and have changed the permission of the .apk but the file still won't install. What can I do?
carrier
Since you carrier wont load I believe following this tutorial with help fix your problem but check the conditions. Im not allowed to post links apparently so I attached it. I'll also flash cleanrom 5.6 and find out if its a software thing and get back to you. But it seems to me like its a MEID issue. So check the conditions in the link and if they are true I'd go that way. If not re-flash, clean install would be my suggestion. Yeah I run Cynagenmod 10.1 and it even knows I'm on Verizon. And Scott's roms always have the carrier.
LtZKilla said:
Yeah, my cell service connects and I can text and call. It just doesn't seem to have any idea that my carrier is verizon and it kinda seems odd.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
havy15 said:
So your SD card doesn't read but hers does? And yeah then just get a new SD card go on a computer take your files off of it and put em back on the new SD card
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
computer doesn't see the card at all..
I can't recall when I last had it working but my NFC completely stopped working. I have tried reverting back to absolute stock rooted nandroid. That didn't work so I Odin booted back to the original unrooted firmware. Still same problem. If I try to uncheck NFC from the more options it moves over and is immediately flipped back. I have gone into a Verizon wireless store to seek help but the guy made a sarcastic remark that his iPhone wouldn't have that problem...but I also as a few other notes I have tried hells ROM and also flashing the NFC file with the ROM which also didn't work and have tried the few NFC Google wallet fixes I have seen, also sadly no luck. I'm stubborn and don't want to give up if anyone knows if there is a possible fix, hope you can possibly help!
Sent from my SCH-I535 using xda app-developers app
replacement?
I think you may have a faulty chip. Also is your battery NFC capable? But to be honest Verizon will replace it for free if your under the 1 year warranty and don't have water damage or anything like that. Because if it doesn't work on the stock rom it's most likely a hardware problem in this case. So I would contact your carrier about that.
CeeMillz said:
I can't recall when I last had it working but my NFC completely stopped working. I have tried reverting back to absolute stock rooted nandroid. That didn't work so I Odin booted back to the original unrooted firmware. Still same problem. If I try to uncheck NFC from the more options it moves over and is immediately flipped back. I have gone into a Verizon wireless store to seek help but the guy made a sarcastic remark that his iPhone wouldn't have that problem...but I also as a few other notes I have tried hells ROM and also flashing the NFC file with the ROM which also didn't work and have tried the few NFC Google wallet fixes I have seen, also sadly no luck. I'm stubborn and don't want to give up if anyone knows if there is a possible fix, hope you can possibly help!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have the stock battery and when I did call Verizon the first time they wanted me to contact Samsung first then get back to them so I figured i'd bring it here. It had worked before so I was wondering if maybe it fried somehow? Phone has never been dropped, no water damage, watch because I said that i'll drop it in 5 minutes and shatter my screen I guess I'll just try Samsung tomorrow and see what they have to say.
nfc
Actually I just thought of something else to try. Have you gone in and force quit nfc and cleared the app data? That may resolve the problem. Nfc will be under all apps and it is named nfc service.
CeeMillz said:
I have the stock battery and when I did call Verizon the first time they wanted me to contact Samsung first then get back to them so I figured i'd bring it here. It had worked before so I was wondering if maybe it fried somehow? Phone has never been dropped, no water damage, watch because I said that i'll drop it in 5 minutes and shatter my screen I guess I'll just try Samsung tomorrow and see what they have to say.
Click to expand...
Click to collapse
jwattt said:
Actually I just thought of something else to try. Have you gone in and force quit nfc and cleared the app data? That may resolve the problem. Nfc will be under all apps and it is named nfc service.
Click to expand...
Click to collapse
Good idea, just tried it and it didn't do anything. Also tried that, rebooted recovery, wiped dalvick and cache fixed permissions then tried again with no luck. =/
nfc
Are you using a non stock kernel? Also when you went back to stock did you erase everything on the phone?
CeeMillz said:
Good idea, just tried it and it didn't do anything. Also tried that, rebooted recovery, wiped dalvick and cache fixed permissions then tried again with no luck. =/
Click to expand...
Click to collapse
This is getting kinda infuriating. Anytime I try to send a text, it bounces and won't send. If I text myself, it goes through. I've tried numerous things, reboots, turning off radio, text from pc.. anything I could think of. Calling is fine though. I can make a call or get a call from anyone. This is beyond me and pretty frustrating.
I just upgraded to the M8 and it should be here sometime next week. Did ATT goof when they ordered my new phone and do something to my existing? Should be something sim card related right? Idk, only a week but man this is ridiculous. I need my phone for work.
Any help would be awesome. Thanks guys.
Have you contacted at&t?
Sent from my Evita
timmaaa said:
Have you contacted at&t?
Sent from my Evita
Click to expand...
Click to collapse
I didn't think they'd help me because I'm on CM11.
Have you tried flashing another ROM to see if the problem persists or not across ROM changes?
Sent from my Evita
Did the SMS failure start right after flashing the ROM or other mod? Or did it just spontaneously start, and not seemingly related to any mods or settings you changed? If spontaneous, I would think its probably caused by AT&T borking up something on your account features or provisions when you did the upgrade. In which case, you are going to be able to fix it on your end.
redpoint73 said:
Did the SMS failure start right after flashing the ROM or other mod? Or did it just spontaneously start, and not seemingly related to any mods or settings you changed? If spontaneous, I would think its probably caused by AT&T borking up something on your account features or provisions when you did the upgrade. In which case, you are going to be able to fix it on your end.
Click to expand...
Click to collapse
I think he means "In which case, you are not going to be able to fix it on your end."
exad said:
I think he means "In which case, you are not going to be able to fix it on your end."
Click to expand...
Click to collapse
Absolutely. Language is such a pesky thing.
A friend of mine bought my one x running 4.2.2 from coolrom i believe.
he can receive picture messages but gets a failed message when sending.
Berserk87 said:
A friend of mine bought my one x running 4.2.2 from coolrom i believe.
he can receive picture messages but gets a failed message when sending.
Click to expand...
Click to collapse
It's most likely a problem with your APN settings, triple check those.
Sent from my Evita
I'm using the International version of the flat S7 on T-Mobile. I've been having this problem for about 2 months now although now it's happening much more frequently. I contacted T-Mobile about my problem, they went over some stuff in the sim card. Such as updating something, checking my area for interruptions, running a diagnostics on my phone. They said everything was fine. Although the problem kept continuing. They sent me a new sim card free of charge in hope of fixing my device. Even then that didn't help, my calls and texts still randomly do not come through. There are times it does and times it doesn't at all. Now I'm wondering if I have a faulty device? Is there any more options I could do to fix this problem?
Tried a factory reset?
Hi, I have tried S7 dialer app (SecContactsProvider.apk & SecContacts_M.apk - deodexed) for my samsung device (J2 2016), It worked fine but suddenly it stopped posting missed call notifications in call log and elsewhere. It becomes very difficult to track who called since there are no traces of caller. Really looking for fix for this.
Thanks.
*Detection* said:
Tried a factory reset?
Click to expand...
Click to collapse
No I haven't but I'll try it.
AplexApple said:
No I haven't but I'll try it.
Click to expand...
Click to collapse
Didn't seem to work sadly... Anymore solutions?
Return the phone
*Detection* said:
Return the phone
Click to expand...
Click to collapse
So I'd be something to do with my phone then?...