Hell everyone,
I recently rooted my phone and installed LiquidSmooth on my AT&T Samsung S3. About three days into using the ROM, I notice some connection problem between my phone and AT&T's network. The problem I experienced was I wouldn't receive texts or calls from other people even though the phone is connected to the network. When I do receive the texts, they come all at once at the same exact moment. Which means my notification ringtone going off like crazy.
This problem usually occurs at night around 9-12PM. I also experienced the same exact problem when I first started using CM10, the stable build. The one thing I also noticed after installing both ROM's is there's no voicemail number. I had to manually add a voicemail number, which is my own number, right?
I decided to unroot my phone and run Samsung's newly released JB update, which totally blows besides the battery life. As of right now with the unrooted phone and Sammy's updates, everything is running fine.
Thanks very much, I appreciate any help I get from you guys. And, I do want to apologize in advance if this question had already been asked. I tried searching, but couldn't find anything on the subject. If you guys need anymore details, please do not hesitate to ask. I will try my best to provide as much detail as possible. Thanks once again.
Wondering if anyone has seen this issue before. (see attachment)
If the caller is in my contact list, name is displayed without issues. However, if they are not, I get a string of strange characters appear as the name. Same goes for Private Callers, or unknown numbers.
The phone is a Samsung Galaxy S3 running AOKP d2att (4.2.1 JOP40D) Build 1.4.2012
Kernel Version: 3.0.57
Android Version: 4.2.1
Baseband: I747MVLDLK4
Model: SGH-I747(M)
Originaly purchased from Rogers (Canada) but used on the Fido network. I have had no other issues, LTE works great via FIDO or Rogers apn's and caller ID worked fine in stock.
I also have the same issue with CM10. Any help would be great!
I experience this as well. It started happening after i changed from running stock Touchwiz to Task's AOKP. It would be nice to have it fixed but as long as I can see the number of the caller that's good enough.
I was afraid someone was going to say that. However, I don't believe this is an issues we should have to live with, there has to be a reason as to why this is occurring. Anyone have any ideas?
Lahey360 said:
I was afraid someone was going to say that. However, I don't believe this is an issues we should have to live with, there has to be a reason as to why this is occurring. Anyone have any ideas?
Click to expand...
Click to collapse
Full Wipe, Reflash Everything. Should be your first thought every time there is some funky problem that no one else really has.
BAM1789 said:
Full Wipe, Reflash Everything. Should be your first thought every time there is some funky problem that no one else really has.
Click to expand...
Click to collapse
Agreed, and believe me, I have already been down that road numerous times. After a full wipe and reflash back to stock, everything works fine. As well as simply restoring to stock after AOKP/CM flash via CWM backup. Yet, as soon as a custom ROM is applied, good bye call display. Something has to be missing...
My friend is having this issue with his Fido Galaxy S3 running CM10 stable. A fix is definitely needed!
Same thing here on latest AOKP on SGS3 on Fido.
Rogers here, same issue. CM10 stable. If the person is in my contact list it shows normally, but the caller id is wonky as described above.
I think since people on the contact list show normally this issue takes a little while for some people to notice. At first I thought it was just some foreign guy calling me Then a few more calls... and I found this thread, although I would describe the display as "garbled" really. But obviously more than a few people have this issue.
This might be one of you guys, http://code.google.com/p/cyanogenmod/issues/detail?id=7074 -- talking about CM10.1, but this bug is in CM10 too obviously.
Possible fix
Hi guys,
I was thinking about this and noticed that people with this problem seemed to be on the I747MVLDLK4 baseband. It occurred to me to try switching it out and seeing if that had any effect.
Yes it does.
I used my co-workers phone (removing his phone number from my contacts first of course) and called my phone. Normally I get gibberish (I tested immediately before flashing to verify) and viola, my caller ID works now, with the tiny exception that there is a trailing "@" symbol. But otherwise it showed up correctly.
I flashed the I747MVLLH1 baseband and that *seems* to have fixed the issue. Apparently the speeds, connectivity and such can vary between basebands and your location so you may want to try a few basebands listed here and see if any of these work for you. Just remember not to flash an AT&T baseband on a Canadian phone or the other way around.
Post your results if this works for you. Cheers!
That is great news!!! I will test a few and post results.
Link is broken tho....
Edit:
http://forum.xda-developers.com/showthread.php?t=1831898
Edit2:
WORKED LIKE A F**KING CHARM!!!!!
Went down the list flashing each one and doing some various tests. Placing/receiving calls, LTE connectivity, speed tests, etc... Safe to say, I747MVLLH1 seems to be working best.
My phone is originally from Rogers, but service is with Fido (Fido sim) yet still using the Rogers APN settings.
Right on man Glad it worked for more than just me. That default base band actually seems pretty lousy in general, thinking back I'm not sure it was really working in the stock, factory firm ware either. I recall seeing unknown caller from phone numbers that I knew had id's.
Cheers!
Edit: can we mark this solved?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
After banging my head against the wall, I finally came across this thread..... THANK YOU!
I747MVLLH1 fixed my scrambled callerID
chasem said:
After banging my head against the wall, I finally came across this thread..... THANK YOU!
I747MVLLH1 fixed my scrambled callerID
Click to expand...
Click to collapse
This worked for me as well, thank you.
Same problem on my LG P930 from Bell, unlocked and connected to rogers. Using CM 10.1 2/21 nightly currently, but it was happening on older nightly's too.
I guess I have to hunt down baseband options for my handset unless other solutions have come up since the last posts to this thread.
spindley said:
This worked for me as well, thank you.
Click to expand...
Click to collapse
Worked for me too.
Samsung Galaxy S3 i747 Rogers Toronto "I747MVLLH1"
Open jira report
There is an open JIRA report against CM10.1 RC3 in regards to this issue.
Yes flashing an older ICS modem will work temporarily but there is obviously a problem with the newer JB modems released for our devices that we can hopefully get resolved.
If you want to see this fixed, sign in to JIRA and vote for the issue to help get it some support.
https://jira.cyanogenmod.org/browse/CYAN-1202
I also understand that not all of you are necessarily using CM10.1 but you may be using a ROM that pulls it's base code from CM so there is a good chance if they fix it, it will be fixed for whatever other ROM you are using.
Thanks.
Hi folks,
Sometimes I can't receive picture messages and I can never send them to my wife's telus phone. They show up as white squares with no text included. Anybody had this or can provide suggestions? I have tried many things so far. Full story below...
Thanks
**************************
I have a Telus T989/ S2X. I have had it for 1.5 yrs and have flashed numerous ROMS since I rooted it about a year ago. Over this time I have had MMS issues on and off.
From early ICS ROMS (darkside) and now to Jelly Bean roms (CM10 nightly, Jedi Jelly, Slim-Star...and more) I have had a strange issue. I can send picture messages to almost everyone and receive from almost everyone. Occasionally I have an issue receiving from friends on the Rogers/ Fido network and it stalls at 'downloading'. I tried unchecking auto-retrieve and it does not fix it. I have also tried multiple radios on multiple roms.
More recently my msgs cannot be viewed when I send them to my wife's phone ( I know, a blessing sometimes right?). She is on the same network (Telus) and has no problem sending/ receiving from anyone. When I send to her it shows as a white/ blank square and none of the text I typed shows up. Regular text are no problem ever.
I called Telus support and they ran me through checking the APN settings and a bunch of other tests sending pics back and forth and no fix. They are going to escalate the problem. I tried the trick of sending yourself a picture via gmail too without any luck. I didn't tell them I was rooted and on 4.1.2....but I have tried tons of diff roms and done a bunch of searching on the forums and google.
Just today I tried the Koodo 4.0.4 rooted ROM with no luck. Then I got pissed off and backed everything up and rolled back to the Telus 2.3.5 Gingerbread ROM. Guess what? MMS worked just fine!!?? I double checked the APN settings and they were identical.
So....has anyone else had this issue? I don't want to be stuck on Gingerbread just to use MMS. Could it be that the newer versions of the MMS/ SMS have issues? I noticed that when I went back to 2.3.5 it said "converting to MMS" when I attached a pic. I never see that in any other ROM.
Any suggestions or solutions that people have come across? I am slightly frustrated....especially since my wife's Nexus S has no problems and my S2X is way better but failing.
Thanks for your time and thoughts folks!
CHBAD
maybe u were send pics that were larger than the network supports. Hypothetically telus may only support 5meg attachments while Rogers/Fido does 10 ( I think this is actually the case but I'm not 100% sure). Use a third party app like hand cent or gosms that supports MMS compression and see how u fair
icenight89 said:
maybe u were send pics that were larger than the network supports. Hypothetically telus may only support 5meg attachments while Rogers/Fido does 10 ( I think this is actually the case but I'm not 100% sure). Use a third party app like hand cent or gosms that supports MMS compression and see how u fair
Click to expand...
Click to collapse
Thanks for the response. I will try that...and update later.
CHBAD
CHBAD said:
Thanks for the response. I will try that...and update later.
CHBAD
Click to expand...
Click to collapse
It seems like some are getting through with Handcent. So the stock app in CM10 is not working then? I should try different size files maybe to see if that is a factor like you said.
i recently my second S3 that i had flashed to page plus. i was told everything would work just as it did when it was stock with sprint. when i got it i noticed that i could receive MMS but not send them .It just says sending continuously until you get fed up enough to delete the message knowing its not actually going through. The next day I took the phone back to the dealer that i had flash it thinking they would know exactly how to fix it. its been a week now and the closest thing they could do was put an app called HOUDINI on it that allows me to send and receive MMS( im guessing through different APN settings?)although the app itself is laggy and horrible and i want to get rid of it as soon as humanly possible. they told me that had flashed the sprint S3 a couple times that week to page plus for other people and everything worked as it should but couldn't figure out what was going on with mine. another thing ive noticed is that it says i am receiving 3G data, but when compared to my friends phone on Verizon using 3G im not getting near the speeds he is.
im hoping to root my phone this week so i can get rid of that annoying camera shutter sound which sprint was nice enough to lock, and update to the latest version of android.
I have utilized the search button and haven't come across this particular problem or question
my questions...
1. has anyone had their L710 flashed to pageplus and experienced similar problems with data or MMS? or possibly heard of it and know a fix i am unable to find?
2. will rooting and/or updating android mess up my carrier flash and cause me to need another flash? from my research ive found that rooting should have NO effect on the flash, but updating might cause me to need to re-flash for the carrier.
Okay so i have a T-Mobile S4 it is now running 4.3, The phone was rooted and running the Google Edition custom rom on 4.2.2 when this issues started.
When i first rooted the phone and installed the Google Rom it worked fine, i could send pix to iphone and receive them from iphone (yes ive tested it with many iphone users and its always the same outcome) however a few weeks ago they stopped receiving any pic text i would send and i would receive theirs as well. I have tried this on wi-fi and just on my cellular network and it still doesnt work.
So last night i thought it might be due to the face i need to update to 4.3, so i un-root my phone, factory reset it so its back to 100% stock, update to 4.3 and im still having the same issue. It works fine with anyone using a Android device, but 90% of my friends and my GF have iphone so this is starting to piss me off...
any info would really help me out. and i didnt a search but nothing to the effect of my problem came up...
The problem is not with your phone, its because apple sucks.
Sent from my GT-I9295