Develop Bugs

[Q] No data and no calls

Randomly I have not been able to text, make calls or get a data connection with my phone. I was running CM 7.0.3 when this all of a sudden started. Restarting my phone would allow me to make calls and get a data connection for a few minutes and then I would not be able to do either. I flashed the newest CM7 nightly build and a new radio, Vision_Radio_12.57.60.25_26.10.04.12. The same problem continued so I flashed Virtuous 2.0.0 but that made no difference.
Anyone have any idea of what I can do to fix this?
Thanks.

I'd say try flashing a different ROM. But since you've fresh flashed the same ROM I'd say that pretty much counts.
Next I'd call the carrier and confirm that you SIM/account is in good standing, and that the towers are working properly in your area. I've had the freakout about "omg my phone is jacked up" and after flashing all kinds of ROMs, radios, etc. I just called T-mobile and they confirm that there was just a network problem in my area.

ur doing a full wipe right?

martonikaj said:
I'd say try flashing a different ROM. But since you've fresh flashed the same ROM I'd say that pretty much counts.
Next I'd call the carrier and confirm that you SIM/account is in good standing, and that the towers are working properly in your area. I've had the freakout about "omg my phone is jacked up" and after flashing all kinds of ROMs, radios, etc. I just called T-mobile and they confirm that there was just a network problem in my area.
Click to expand...
Click to collapse
I actually did flash a different ROM and the issue continued. I'll be contacting Bell to see if maybe it's a service issue.
smokeuout said:
ur doing a full wipe right?
Click to expand...
Click to collapse
I did a full wipe after trying the nightly CM7 and same issue.

knifer said:
I actually did flash a different ROM and the issue continued. I'll be contacting Bell to see if maybe it's a service issue.
I did a full wipe after trying the nightly CM7 and same issue.
Click to expand...
Click to collapse
If you contact bell they'll know that you rooted your phone and they will have less sympathy to help you fix it.
Sent from my HTC Vision using XDA App

evilcuber said:
If you contact bell they'll know that you rooted your phone and they will have less sympathy to help you fix it.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
How? Do like I did and google the right build number for your device because they will ask, and you don't want to get caught saying 'GRJ***'
Sent from my HTC Vision using XDA App

evilcuber said:
If you contact bell they'll know that you rooted your phone and they will have less sympathy to help you fix it.
Click to expand...
Click to collapse
They won't know unless you tell them.
PaganAng3l said:
How? Do like I did and google the right build number for your device because they will ask, and you don't want to get caught saying 'GRJ***'
Click to expand...
Click to collapse
This.

i tell my carrier straight up that im rooted...they dont say anything...but im not calling tech support either

If the OP is just calling to see if their have been any reported service outages or interruptions in his area, whether he is rooted or not shouldn't matter.
A couple times in the past few years, I've had instances where I lost both data and voice service for up to a couple hours at a time, over the course of several days. Then the problem just goes away. This seems to fairly typical, if they are upgrading or repairing your local tower.
If the OP has tried flashing various ROMs, and tried a new radio, I'd be inclined to say the ROM is not the problem. If the problem persists, you may ask your carrier to send a new SIM (or go to their store and ask for one).

hi,
you are not alone!
i have this problem with OE HTC 2.3.3 stock rom! (unrooted original device from Nov. 2010)
so i had very bad mobile connection and after ~1day (without reboot) i can't phone with it.. mobile network only "x" but data connection is fixed to gprs.
very strange!
so i send my phone back and orderd new one.
i think this is was hardware problem.
short:
- reboot bringt full funktion but the mobile connection is not so good as 4month ago (same point).. 4month ago it was "H" and now only gprs
after many hours >8h. calls didn't work, the phone said "no provider"... (x)..
- the strange thing is that data connection is degrade to gprs
this problem exist from the last 2 HTC OTA updates. but onyl the last 2.3.3 makes it really unusable
i hope this problem don't come back with the new desire z now rootet with cm 7.10 rc1 (what a feeling)

[Q] Galaxy Nexus 4.0.4 Incoming calls bug (no mic/speaker)

Hey guys
I got a pretty weird problem here.
I have a Galaxy Nexus with Rogers running the stock USA 4.0.4 rom from google.
Since this morning, any incoming calls I get seems muted from both side.
Caller: no mic / no speakers
Me: no mic no speakers
But if i call bacl, it work.
So incoming bug, outgoing are fine......
Here's what I tried until now:
Clear cache
Reboot
Uninstall recently added apps
Reboot again....
My girlfriend is running a gnex from rogers with the stock canadian version (first version of ics) without problems.
Is anyone know about this issue and have a fix?
Btw, network seems fine, 3g work well, wifi as well

Try flashing the radio from the stock canadian version (or a later leaked one for your region is one is available) if you have unlocked the bootloader. The yakju builds contains radios adapted for the European market (based on the naming of the radio version, XXLA2 in this case) so could have incompabilities with other parts of the world.

Thing is that it's was working well until this morning. And it's the stock us Rom gave by google....
Other canadian are using it.....and if the phone is accepting outgoing call well, as same as receiving call but just not having mic\speakers, i don't thong it's because of the radio it is using. I'M not a programmer but it sound weird to me that it can work well for a few days then the radio decide it's incompatible all of sudden.
blunden said:
Try flashing the radio from the stock canadian version (or a later leaked one for your region is one is available) if you have unlocked the bootloader. The yakju builds contains radios adapted for the European market (based on the naming of the radio version, XXLA2 in this case) so could have incompabilities with other parts of the world.
Click to expand...
Click to collapse

What radio version did it include? XXLA2? You can check under Settings -> About.
Try running a logcat (ADB logcat) and then call your phone to see if it throws any errors.

There is a known signal issue with 4.0.4 which might be what you are experiencing. If you root your phone, you can try setting the min frequency to 700 MHz and flashing either UGKK7 or UGKL1, which are canadian basebands. I'm on AOKP b30 with UGKL1, and I have no issues, despite my min frequency being 384 MHz.

19250xxla2
blunden said:
what radio version did it include? Xxla2? You can check under settings -> about.
Try running a logcat (adb logcat) and then call your phone to see if it throws any errors.
Click to expand...
Click to collapse

The thing is that the main reason i downloaded that rom is because i want auto-update by google....if i root i will not get it.....if i change radio i will not get it as well......
TheSobadef said:
There is a known signal issue with 4.0.4 which might be what you are experiencing. If you root your phone, you can try setting the min frequency to 700 MHz and flashing either UGKK7 or UGKL1, which are canadian basebands. I'm on AOKP b30 with UGKL1, and I have no issues, despite my min frequency being 384 MHz.
Click to expand...
Click to collapse

I am having the exact same issue since this morning. Samsung Galaxy S2 LTE running the following ROM since January :
DJ ICS V1.0.3 & ICS+ V1.0.3 [Sky Ice + ICS Perfection]
I tried rebooting the phone a couple of time but I am still not able to talk/hear people who call me, when I call them back it is working.
Also, maybe unrelated, but since the last week or two I have been having issues with incoming/outgoing calls ringing forever, never getting to voicemail usually a reboot helped with this.
Another thing that come to mind and that I just figured might be related to the issues : I subscribed to Rogers One Number service a day or two after it became available. Since then I started having incoming/outgoing call issues. I think I will be calling them very soon regarding this.

MAN I THING YOU HAVE SOMETHING HERE
I'm suscribed to Rogers one number as same as you. I never used it since I registered but that could be related. I'll dig into that direction.
matd123 said:
I am having the exact same issue since this morning. Samsung Galaxy S2 LTE running the following ROM since January :
DJ ICS V1.0.3 & ICS+ V1.0.3 [Sky Ice + ICS Perfection]
I tried rebooting the phone a couple of time but I am still not able to talk/hear people who call me, when I call them back it is working.
Also, maybe unrelated, but since the last week or two I have been having issues with incoming/outgoing calls ringing forever, never getting to voicemail usually a reboot helped with this.
Another thing that come to mind and that I just figured might be related to the issues : I subscribed to Rogers One Number service a day or two after it became available. Since then I started having incoming/outgoing call issues. I think I will be calling them very soon regarding this.
Click to expand...
Click to collapse

Man as strange as it appear it now work...... (i did nothing) mayne Rogers is messing up with the network.....since LTE launched network act weird sometime.....but i'll take a look to the one number thing
matd123 said:
I am having the exact same issue since this morning. Samsung Galaxy S2 LTE running the following ROM since January :
DJ ICS V1.0.3 & ICS+ V1.0.3 [Sky Ice + ICS Perfection]
I tried rebooting the phone a couple of time but I am still not able to talk/hear people who call me, when I call them back it is working.
Also, maybe unrelated, but since the last week or two I have been having issues with incoming/outgoing calls ringing forever, never getting to voicemail usually a reboot helped with this.
Another thing that come to mind and that I just figured might be related to the issues : I subscribed to Rogers One Number service a day or two after it became available. Since then I started having incoming/outgoing call issues. I think I will be calling them very soon regarding this.
Click to expand...
Click to collapse

[Q] Caller ID Hieroglyphs

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.

[Q] blazer rom question

Okay so I love this rom. I installed it when it was at 1.6. I checked back to see if they had updated anything and wow it was already at like 2.1. I got to reading and found out that 2.1 uses a new kernel and would not recognize my 64 gig micro sd, so I installed 2.0. Everything works great except for one thing. In some areas, I cannot make calls. It acts like it is dialing, but never starts ringing and eventually hangs up. I am showing in some cases full bars. I am roaming, but I have full service. I have checked my roaming guards and roaming networks. Changed almost every setting that I can with no avail. Sometimes when I try to make a call, I will lose all bars of service. One thing to note, when in this area, I can still use my internet and 3g service, just no calls. Before updating, I could make calls in the area easily. I can drive five minutes down the road and make calls with no problem. I am figuring it is maybe a different tower. Also this area is roaming as well. I can make calls no problem. Just wondering if anyone maybe has an answer for this. I have searched the blazer rom official forum and have came up with nothing. Advanced thanks to anyone that may have an answer and for the help.

bump

Maybe update Ur prl? And do a clean install?
*
Rooted Evo dead.
Rooted Evo shift dead.
Rooted Galaxy s3 alive and well!

joshtycobb said:
Maybe update Ur prl? And do a clean install?
*
Rooted Evo dead.
Rooted Evo shift dead.
Rooted Galaxy s3 alive and well!
Click to expand...
Click to collapse
Okay, will do. Will update later.

robertqadkins said:
Okay, will do. Will update later.
Click to expand...
Click to collapse
*Update*
Okay, so I tried updating my prl with no luck. I updated via the option in the menu. A question that I had is do I need to do this on my Sprint network, or can I do it while I am roaming? Also I completely did a fresh flash of blazer 2.0, Superior, and blazer 1.6 (the last working rom that I had) and now they are all doing the same thing. My wife's phone, a s2, works fine in that area as well as my buddy's. Any other suggestions?

robertqadkins said:
*Update*
Okay, so I tried updating my prl with no luck. I updated via the option in the menu. A question that I had is do I need to do this on my Sprint network, or can I do it while I am roaming? Also I completely did a fresh flash of blazer 2.0, Superior, and blazer 1.6 (the last working rom that I had) and now they are all doing the same thing. My wife's phone, a s2, works fine in that area as well as my buddy's. Any other suggestions?
Click to expand...
Click to collapse
Get an up to date rom. That rom is notorious for not being updated or supported by the developer.

bchalker said:
Get an up to date rom. That rom is notorious for not being updated or supported by the developer.
Click to expand...
Click to collapse
I did, I tried superior. It did the same thing. Now I can only make calls on roaming networks occasionally. I have to keep trying to call and call and eventually one of the calls will go through, sometimes. Other times I can't get a call out at all. My internet works fine. I have tried 2 different roms. 2 versions of Blazer and Superior. I tried updating my prl on while connected to the Sprint network and that did not help. I am at a loss here. I have tried just about everything that I know. Could it be a hardware problem? I would not think so since I can make and receive calls fine while not roaming. Any suggestions?

Where are you located? Kind of sounds like a Sprint issue.

MBCO said:
Where are you located? Kind of sounds like a Sprint issue.
Click to expand...
Click to collapse
I don't think it is a sprint issue. My wife's stock s2 works fine. I am located in Danville, WV. I get no sprint service where I live and am always roaming, so this is a pretty big deal. Also, this morning I installed MOAR with no luck either. Could it be a hardware issue? I don't think it is because if i'm not roaming it works fine...must be something small.

Major Problem. Cant hear people on the phone

Hello there. I have a major problem which is makeing me consider going back to stock. When someone calls me or I call someone the call connects but I cannot hear the person on the line and they cannot hear me. I do not have this problem when I use Csipsimple to make voip calls. Its only when I use the actuall line. I am useing P.A.Cman True All in 1 ROM with the UVLI1 radio. Can someone please help me. This is a major game breaking feature. I have tried two differnt roms and a differnt radio. It will work intermittently for a bit but then stop. Some times a reboot will work. Some times it wont. Please help before I buy a different phone

I've had that issue before and its annoying. ROM related or maybe just how u flashed it. I would reflash with a clean wipe if u insist on sticking with that ROM. If not then I would recommend using slim star 2.2 ROM. That I can guarantee will not have this problem. If perhaps u still do however, then I would have to say you have a bigger problem....hardware even perhaps....but I highly doubt it...
So yeah try slimstar2.2 just to troubleshoot then go back if you want and ull see if its just the ROM. I'm not advocating slimstar over PAC allinone I'm just picking it cuz its what I have now and I can confirm u won't have that issue. Good luck
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Had this problem on most Roms with a bunch of different radios. Thought it might be a hardware problem. I flashed the new UVLI4 and not only am I receiving calls where I never received them before but I'm not getting my 2 phone calls a day with no one on the other end. Only about 4 days into it, but no empty phone calls yet. Actually took me 2 days to realize it, kinda nice.

I've had a similar problem intermittently on several ROMs. My first suggestion is to reflash the radio - often this will fix the issue. If that doesn't work, you can contact tmo customer service and have them reset your phone on the network by "purging your HLR or BLR on the network (source: http://forum.xda-developers.com/showthread.php?p=35585027), That's worked for me also. hope that helps.