Related
Hi ,
a couple of days ago, during a small emergency, I tried to call 911, and the the phone was showing CALL ENDED , after 1 second . all the time.
Today after several tests, found out, that my GSM Samsung Galaxy Nexys I9250
1 - with STOCK ROM, 911 works.
2 - with Android Revolution Custom ROM, DOESNT WORK.
3 - with LIQUID ROM , doesnt work.
the baseband installed right now is : I9250XXLA2
has any other person report this ISSUE.
I was lucky that wasnt not a REAL EMERGENCY, but I will like to inform this.
and should be a sticky somewehere, so any one that try any rom know about this possibility.
could happen on another phones? or is related to the i9250 GSM.
cheers
Ezequiel
ezequielpelax said:
Hi ,
a couple of days ago, during a small emergency, I tried to call 911, and the the phone was showing CALL ENDED , after 1 second . all the time.
Today after several tests, found out, that my GSM Samsung Galaxy Nexys I9250
1 - with STOCK ROM, 911 works.
2 - with Android Revolution Custom ROM, DOESNT WORK.
3 - with LIQUID ROM , doesnt work.
the baseband installed right now is : I9250XXLA2
has any other person report this ISSUE.
I was lucky that wasnt not a REAL EMERGENCY, but I will like to inform this.
and should be a sticky somewehere, so any one that try any rom know about this possibility.
could happen on another phones? or is related to the i9250 GSM.
cheers
Ezequiel
Click to expand...
Click to collapse
I hope you post this in the respective rom threads, this is an important issue.
Sent from a phone...
You checked "yes this is a question"
Guess where it belongs?
Thread moved!
Sent from my SPH-D700 using xda premium
keep working on it .
Very strange, with the stock rom, the 911 works.
I have 2 galaxy nexus I9250 .
with the same custom rom, panandroid, all baseband, and all the same,
one of the phone still not working the 911 emergency call.
I will flash a baseband update, and see if is fixed.
may be was the way this phone is unlocked? ,
the phone that is working, I unlocked it with f##K cdomo, app.
but the one is not working the 911, was Unlocked, and permanent, with a not matching IMEI number to the PRINTED IMEI on the back.
I will post more if i have news.
app f##k kodomo, makes the 911 number not working
not sure, which combination of steps, or if it is the permanent unlock or temporary unlock, that changes imei number, and breaks the emergency call.
to fix it, I restore an OLD backup, with stock rom, and then used the f##k kodomo ap v2, with the option of make backup (wear condom item ) and then install any rom, install f##k kodomo , and restore the backup. (original IMEI will be restored )
now everything is working .
the main problem, is the app KODOMO, used to UNLOCK the GN I9250,
and only few people or no one test the 911 CALL .
please test it if you were messing up with Kodomo App/ Unlocking the GN.
as could be dangerous if is not working during an emergency.
Hey guys,
I recently upgraded my Rogers Galaxy S3 d2att from CM10.1 Nightly 02/12 to CM 10.2 and have no longer been able to get the usual H+ connection. I now have either no letter or an E beside the signal bar. I did the following:
Dirty Flash 10.2 through Recovery Menu
Delete cache, dalvik and data in recovery menu
Couldn't get 3G, 4G or H+ Connection so I dirty flashed 10.1
Installed latest d2att rogers modem, installed latest bootloader, neither worked
Flashed back to CM10.1 Nightly
Can't get previous H+ connection on CM10.1 Nightly
I'm getting the worst headache trying to solve this. I'm more than willing to revert back to stock to try and get this working properly.
Thanks!
UPDATE:
I found out my IMEI was deleted while flashing. Does anybody know how I would get this back?
First off, how did you get cm 10.2
Cerhio;4409stock said:
[*]Dirty Flash 10.2 through Recovery Menu
[*]Delete cache, dalvik and data in recovery menu
[*]Couldn't get 3G, 4G or H+ Connection so I dirty flashed 10.1
[*]Installed latest d2att rogers modem, installed latest bootloader, neither worked
[*]Flashed back to CM10.1 Nightly
[*]Can't get previous H+ connection on CM10.1 Nightly
[/LIST]
I'm getting the worst headache trying to solve this. I'm more than willing to revert back to stock to try and get this working properly.
Thanks!
UPDATE:
I found out my IMEI was deleted while flashing. Does anybody know how I would get this back?
Click to expand...
Click to collapse
Try going back to stock by odin. That should work. And how did you get cm 10.2?? Can you give me the link where you downloaded from. That would be great.
Cerhio said:
Hey guys,
I recently upgraded my Rogers Galaxy S3 d2att from CM10.1 Nightly 02/12 to CM 10.2 and have no longer been able to get the usual H+ connection. I now have either no letter or an E beside the signal bar. I did the following:
Dirty Flash 10.2 through Recovery Menu
Delete cache, dalvik and data in recovery menu
Couldn't get 3G, 4G or H+ Connection so I dirty flashed 10.1
Installed latest d2att rogers modem, installed latest bootloader, neither worked
Flashed back to CM10.1 Nightly
Can't get previous H+ connection on CM10.1 Nightly
I'm getting the worst headache trying to solve this. I'm more than willing to revert back to stock to try and get this working properly.
Thanks!
UPDATE:
I found out my IMEI was deleted while flashing. Does anybody know how I would get this back?
Click to expand...
Click to collapse
Are you sure you don't mean CM 10.1.2? I don't think CM 10.2 is available for the Rogers or AT&T Galaxy S III yet...if it is please link to it.
n_alvarez2007 said:
Are you sure you don't mean CM 10.1.2? I don't think CM 10.2 is available for the Rogers or AT&T Galaxy S III yet...if it is please link to it.
Click to expand...
Click to collapse
Yes sorry, you're absolutely right! I still have service on my phone but I cannot even get 3G signal.
Cerhio said:
Yes sorry, you're absolutely right! I still have service on my phone but I cannot even get 3G signal.
Click to expand...
Click to collapse
1. Check if Access Points are correct
2. Check if you lost your IMEI (normally if you still get service but not mobile data beside edge, your IMEI will show as 0)
3. if the above aren't true, have you try flashing different nightly/stable or different roms?
and if your imei was deleted
you need to inject your imei again
first, take out the battery, beside the battery there should be serial numbers and imei numbers
secondly, you need SGS3 NV Gen and NV item reader & writer OR you can also use QRST though the process is a little more difficult (I don't think i can distribute the files here, and QRST you can google it)
as for SGS3 NV gen and nv item writer, you just need to copy and paste your imei to SGS3 NV Gen and it'll write to a text file, then all you need is to use NV item writer to connect with your phone and upload the file.
oh and you need to revert back to stock rom because the phone needed to be in RM + Modem + something mode lol... which is located in one of the secret menu .... i believe it was *#7284#
pcshano said:
2. Check if you lost your IMEI (normally if you still get service but not mobile data beside edge, your IMEI will show as 0)
Click to expand...
Click to collapse
I did...
I did
I followed your steps. The IMEI was injected successfully but the ERI is still showing 0. How do I fix that?
Or, how do I get it to re-register on the network with the IMEI in place?
Samsung Galaxy S3 (d2att) Poor or no Service
I'm having the same issue - or so it appears. my IMEI was also erased and I restored it using the method described above. That solved the issue of not being able to connect to the network at all, but now my connection last 3 minutes at best. I start off with LTE, then 3g, then g, then no letter at all and through that all, making/receiving calls, sending receiving texts, and even accessing the internet is only doable the first 3 minutes or so. After that, all if gone.
I've gone through the following radios:
I747UCLEM: modem_CWM_I747UCLEM.zip - 19.06 MB - May 22nd, 2012 (original shipped)
I747UCLG1: modem_CWM_I747UCLG1.zip - 19.06 MB - July 1st, 2012
I747UCLH1: modem_CWM_I747UCLH1.zip - 19.40 MB - August 1st, 2012
I747UCLH9: modem_CWM_I747_UCLH9.zip - 18.90 MB - August 9th, 2012
I747UCLI5: modem_CWM_I747UCLI5.zip - 19.51 MB - September 5th, 2012
I747UCDLK3: modem_CWM_I747UCDLK3.zip - 18.42 MB - November 3rd, 2012
I747UCDMG2: modem_CWM_I747UCDMG2.zip - 19.01 MB - July 2nd, 2013
I've tried various CWM versions, ROMs, and even Odined back to stock but still have the same issue. I ruled out the possibility of it being a SIM issue by placing my SIM in another phone. Service worked beautifully as expected. I took a working SIM from another phone and placed it in mine and had the same poor signal issue.
I've tried a good deal of troubleshooting methods and am seemingly stumped. I'm sorry to see that others are having the issue but I'd like to help however I can. the only thing I can say for certain is wrong at the moment is that my Serial Number seems to have been changed and no longer matches what is written on the phone....could that be the issue?
Current Serial number is displayed in about phone as: 1f03dbad
Hopefully, this provides some insight and someone a bit more knowledgeable than myself can help us find a solution.
If you need anything else, let me know and I'll do my best to provide it.
Please help I have the same issue, I have flashed back AT&T official ROM, but no 3G signals and weak phone signals. Did you guys find a solution? How do I check my ERI?
Please help if you have a solution.
triplethreat117 said:
I'm having the same issue - or so it appears. my IMEI was also erased and I restored it using the method described above. That solved the issue of not being able to connect to the network at all, but now my connection last 3 minutes at best. I start off with LTE, then 3g, then g, then no letter at all and through that all, making/receiving calls, sending receiving texts, and even accessing the internet is only doable the first 3 minutes or so. After that, all if gone.
I've gone through the following radios:
I747UCLEM: modem_CWM_I747UCLEM.zip - 19.06 MB - May 22nd, 2012 (original shipped)
I747UCLG1: modem_CWM_I747UCLG1.zip - 19.06 MB - July 1st, 2012
I747UCLH1: modem_CWM_I747UCLH1.zip - 19.40 MB - August 1st, 2012
I747UCLH9: modem_CWM_I747_UCLH9.zip - 18.90 MB - August 9th, 2012
I747UCLI5: modem_CWM_I747UCLI5.zip - 19.51 MB - September 5th, 2012
I747UCDLK3: modem_CWM_I747UCDLK3.zip - 18.42 MB - November 3rd, 2012
I747UCDMG2: modem_CWM_I747UCDMG2.zip - 19.01 MB - July 2nd, 2013
I've tried various CWM versions, ROMs, and even Odined back to stock but still have the same issue. I ruled out the possibility of it being a SIM issue by placing my SIM in another phone. Service worked beautifully as expected. I took a working SIM from another phone and placed it in mine and had the same poor signal issue.
I've tried a good deal of troubleshooting methods and am seemingly stumped. I'm sorry to see that others are having the issue but I'd like to help however I can. the only thing I can say for certain is wrong at the moment is that my Serial Number seems to have been changed and no longer matches what is written on the phone....could that be the issue?
Current Serial number is displayed in about phone as: 1f03dbad
Hopefully, this provides some insight and someone a bit more knowledgeable than myself can help us find a solution.
If you need anything else, let me know and I'll do my best to provide it.
Click to expand...
Click to collapse
I am having the same connectivity issues. I had to restore my IMEI earlier this week after a dirty upgrade, and then restored to several 10.1.x versions and back to 10.2, though this did not help. I did a stock restore and then rooted again, as well as restored 10.1.2 and nothing helped. I also dirty flashed beanstalk latest build, 2 builds of paranoid android and nothing worked.
Sometimes I can get on LTE or HSPA+ for a few minutes after turning data off and on, but this resets. I have also tried several APN settings, the ones provided by cyanogenmod as well as reconfigurations.
I having issues with CM10.1.3 ,I searching and finding this on the Google plus internet page of CM talking about compatibility of our phone with the news CM ROMs:
" To make sure your device is primed and ready for this state, the following lists the bootloaders compatible for each device:
d2att: I747UCDLK3 & I747MVLDLK4"
I have also change the baseband...
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
warweolf said:
I having issues with CM10.1.3 ,I searching and finding this on the Google plus internet page of CM talking about compatibility of our phone with the news CM ROMs:
" To make sure your device is primed and ready for this state, the following lists the bootloaders compatible for each device:
d2att: I747UCDLK3 & I747MVLDLK4"
I have also change the baseband...
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is irrelevant, the new bootloader was added into the recovery ROM so there is no need to downgrade the bootloader. I did just in case to see if my issue would be fixed but as expected it was not.
my device now: i9195, I9195XXUCNE6-DBT
I experience weak signal and many connection dropdowns. When this occured first, after i upgraded f4ktion Kernel 1.3.6 to 1.4.5 and
an older version of Carbon Rom (4.2.2) to 4.3 Carbon Rom. Until than everything was fine, flash of rom and kernel did not made any problem.
Btw i used Odin3 3.09 and clean install (step by step like in the guides) all the time.
After some days this realy annoyed me, so i went back to the older Carbon and kernel - problem still occurs.
So i went back to stock rom I9195XXUBML4-DBT (original was UBML4) - problem still existing.
Some time later f4ktion 1.5 and Carbon 4.4.4 was available, so i tried this..still no solution.
Now i am back to stock and updated to I9195XXUCNE6-DBT, same problem.
Some research told me many ne stuff to know..like flashing modem only. I tried some, nothing helped.
After hours of pointless googleing i noticed something on my phone.When i dont type the pin, i have normal signal. As soon as i type the pin
and "activate" my simcard, the signal strength drops. So i googled again and found this:
[Bug Watch] Android 4.3 Radio Bugs Causing Cell Connection Drops On Some Nexus 4 Handsets, Fixes In Sight (not allowed to post links)
I changed the network type to WCDMA only - it helped for some minutes(not many..maybe 2-3). I changed to GSM only and i had normal,
stable signal for like an hour. But later signal loses strenght again, and i need to change network type again.
I have the feeling, that its like a reset or restart of the radio.
But now i am all out of ideas and need some help.
Last thing i can do, is to bring it to repair. But my Knox says 0x1, so maybe you can help me before i ask Samsung.
I have similar problem since ugrading to KitKat roms. I had no problems with previous none Knox roms with MH3 modem but now with NE6 and NF7 KK modems the signal swings constantly up and down from 4 to 1 bars. This is in areas I previously had good signal. Internet also keeps dropping out requiring data toggling on and off. I've reflashed KK 20+ times and haven't been able to get rid of this problem yet.
I'm not sure if pre knox modems are installable but I intend to try and reflash MH3 modem, once I manage to do a successful backup.
I solved a similar problem by downgrade to 4.2.2 Brazil NE2, knox 2. Flashing separate modem (NE2), and reflashing full rom again. No problems for now
Now you stay on 4.2.2 ?
I dont understand why some people do have problems and some not. Is there different hardware version causing the trouble ?
Give me pls some information how you did the downgrade.
-Nandroid Backup
-philz
-Odin (if yes which version)
-why did you choose that rom
I tried to, but wasnt succesfull. I used Odin3 3.09 to flash 4.2.2 (UAMF5 i think) rom and got a brick. When trying to fix this nothing helped until i tried to flash with Odin3 3.04. But all i could do was flashing newest FW again. Did not test more after that, because i was very busy.
If you say that going back solved your problem, i will try again go go back myself. I've found some information on that and when its done i give some informations.
Same here, help?
I'm having the same problem with a newly acquired handset. I have full signal on some places and nothing on others, unfortunately in my house I have no signal! So it's quite exasperating.
My baseband version is I9195XXUCNE6
Android version is 5.0.2 with 3.4.0-cyanogenmod-g92aec50 [email protected] #1 kernel
Cyanogenmod version is 12-20150306-UNOFFICIAL-serranoltexx
Would it help if I flash a separate modem file through Odin? In that case, which one should I flash?
Any help would be appreciated a lot.
Thanks
franzasensi said:
I'm having the same problem with a newly acquired handset. I have full signal on some places and nothing on others, unfortunately in my house I have no signal! So it's quite exasperating.
My baseband version is I9195XXUCNE6
Android version is 5.0.2 with 3.4.0-cyanogenmod-g92aec50 [email protected] #1 kernel
Cyanogenmod version is 12-20150306-UNOFFICIAL-serranoltexx
Would it help if I flash a separate modem file through Odin? In that case, which one should I flash?
Any help would be appreciated a lot.
Thanks
Click to expand...
Click to collapse
If you have warrenty left then you should go to customer service then they will change your mainboard. and it would bw okay.
I was using cyanogen 12.1 stable release. everything was working. suddenly I could no longer hear people in calls and they could not hear me. I can make and receive calls, there is just no audio. I also don't hear a ringing noise when I dial. I have TWRP recover.
Things I have tried with cm 12.1:
I tried wiping my phone followed by flashing cm 12.1
I tried toggling speaker
I tried disabling google checkin service
My sim card works in another phone
I restored my stock recover (nandroid recovery?) and did a factory reset.
stock info:
SGH-M919
android 4.4.4
baseband m919uvufnk2
kernel 3.4.0-2437203
build KTU84P.M919UVUFNK2
bootloader = baseband
I'm not sure how to share logcat from cm 12.1 because i cant post urls and i dont se a way to attach a file.
update: wifi calling works
vandamere said:
I was using cyanogen 12.1 stable release. everything was working. suddenly I could no longer hear people in calls and they could not hear me. I can make and receive calls, there is just no audio. I also don't hear a ringing noise when I dial. I have TWRP recover.
Things I have tried with cm 12.1:
I tried wiping my phone followed by flashing cm 12.1
I tried toggling speaker
I tried disabling google checkin service
My sim card works in another phone
I restored my stock recover (nandroid recovery?) and did a factory reset.
stock info:
SGH-M919
android 4.4.4
baseband m919uvufnk2
kernel 3.4.0-2437203
build KTU84P.M919UVUFNK2
bootloader = baseband
I'm not sure how to share logcat from cm 12.1 because i cant post urls and i dont se a way to attach a file.
update: wifi calling works
Click to expand...
Click to collapse
Hmm... sounds like something that started happening on my M919 a few months ago.
Another user with similar (same?) issue posted in general here: http://forum.xda-developers.com/galaxy-s4-tmobile/general/sound-voice-calls-t3392450
My reply was this... haven't tried the fix yet:
dirkdigles said:
This just happened to my M919 a few weeks ago. Voice call audio works via bluetooth ONLY but not via phone speakers or wired headset. Everything else (media, videos, whatsapp calls, messenger calls, etc.) works fine.
I did a lot of research and found almost nothing ... except this:
https://www.youtube.com/watch?v=heJqdryGhrs
http://blog.brokenlcds.com/samsung-galaxy-s4-speaker-problem/
If you look at the 2nd picture, I believe that the solder connections on the Audio IC chip (in-call audio chip) are degraded.. Initially if I put pressure on that area on my phone, the audio would cut in and out. Now it's completely gone.
I've read that if you disassemble the phone and use a heat gun to carefully reflow the solder on that little chip, the connections re-attach and this may fix the issue.
I haven't tried because I can't afford a new phone right now and don't want to risk further damaging this one, so I just have my calls currently forwarding to my GVoice number, which works fine.
Click to expand...
Click to collapse
vandamere said:
I was using cyanogen 12.1 stable release. everything was working. suddenly I could no longer hear people in calls and they could not hear me. I can make and receive calls, there is just no audio. I also don't hear a ringing noise when I dial. I have TWRP recover.
Things I have tried with cm 12.1:
I tried wiping my phone followed by flashing cm 12.1
I tried toggling speaker
I tried disabling google checkin service
My sim card works in another phone
I restored my stock recover (nandroid recovery?) and did a factory reset.
stock info:
SGH-M919
android 4.4.4
baseband m919uvufnk2
kernel 3.4.0-2437203
build KTU84P.M919UVUFNK2
bootloader = baseband
I'm not sure how to share logcat from cm 12.1 because i cant post urls and i dont se a way to attach a file.
update: wifi calling works
Click to expand...
Click to collapse
Hi, a quick question, does it work on other ROMs? E.g., does it work normally on SlimLP, RR, AOKP, etc., to see if it is the phone or CM12.1 problem.
Also, to post a logcat, just paste it into the XDA post, and select the code flag.
Sent from my SGH-M919 using XDA-Developers mobile app
AlaskaLinuxUser said:
Hi, a quick question, does it work on other ROMs? E.g., does it work normally on SlimLP, RR, AOKP, etc., to see if it is the phone or CM12.1 problem.
Also, to post a logcat, just paste it into the XDA post, and select the code flag.
I haven't tried any other roms besides cm12.1. I tried updating my phone using kies to the lateset firmware and that didn't work either. Luckily my phone is still under warranty so I'm getting it replaced today.
When I tried pasting logcat, the forum said it was too long. I don't remember if I tried the log with warning level.
Click to expand...
Click to collapse
vandamere said:
AlaskaLinuxUser said:
Hi, a quick question, does it work on other ROMs? E.g., does it work normally on SlimLP, RR, AOKP, etc., to see if it is the phone or CM12.1 problem.
Also, to post a logcat, just paste it into the XDA post, and select the code flag.
I haven't tried any other roms besides cm12.1. I tried updating my phone using kies to the lateset firmware and that didn't work either. Luckily my phone is still under warranty so I'm getting it replaced today.
When I tried pasting logcat, the forum said it was too long. I don't remember if I tried the log with warning level.
Click to expand...
Click to collapse
Hi!! My girlfriend also has a similar problem, but she is on cm13. I haven't figured out the solution, but it seems that when you call someone, if you press the loudspeaker button twice (i.e. -> loudspeaker -> regular), the problem is solved. However, you need to repeat this for every call. Does this happen with your phone too?
Click to expand...
Click to collapse
Dear XDA forum members,
I've been experiencing this issue with incoming calls from a specific number since the upgrade to Android 8.0 (Oreo):
(this is a quote from my post on the Google productforums)
Hi all,
I've been experiencing a weird problem with my LG Nexus 5X phone. Let me explain:
When I dial my mobile phone number on my company's internal phones, I hear a dial tone on the line but drops after two 'rings'. With no redirect to voicemail. The phone itself does not ring, there is no trace of the call.
There is no problem when I call from a fixed residential or mobile phone.
Troubleshooting steps:
I work for a telecom provider myself, we checked the RAN and see paging going out to the handset, the handset responds to this paging. We then see the 'ALERTING' phase which means the call is in fact routed to the handset.
I then switched my SIM card to an iPhone and another Android phone, the problem does not occur with these handset.
So I tried a factory reset of my Nexus 5X, this didn't solve the problem.
Afterwards, I did another factory reset, but then set up the phone as a new phone instead of restoring a back-up. This also didn't solve the problem.
The phone was on Android version 8.0.0 (OPR4.170623.009, Oct 2017), I flashed it to Android 7.1.2 (N2G48C, Aug 2017), and the calls were working again!
I also forced the handset on 2G, but this also doesn't solve the problem.
I then flashed the handset again to the latest Android 8.0.0 (OPR6.170623.023, Nov 2017) release, but the problem occurs again. This time, I noticed that when the call is made from our company's internal phones, my cell phone's signal goes away and comes back up a few seconds later. So it seems that the radio crashes. I've attached a log of the radio made with 'adb logcat -b radio'. I also added the relevant crash log.
I've also tested this with a colleague who has the Nexus 5X. The problem also occurs on his handset.
When calling my brother who currently lives in the States (and also has a 5X), the problem does not occur.
Thanks in advance,
Ruben
Click to expand...
Click to collapse
The thing I've been wondering, would it be possible to flash the radio image of the stock 7.1.2 (N2G48C, Aug 2017) version on a system & bootloader image that runs version 8.0.0 (OPR6.170623.023, Nov 2017)?
So basically, use the radio software of Android 7 on an Android 8 system. Could this break anything? Otherwise I'd figure I just test this...
Thanks in advance!
Rubenvdp said:
Dear XDA forum members,
I've been experiencing this issue with incoming calls from a specific number since the upgrade to Android 8.0 (Oreo):
(this is a quote from my post on the Google productforums)
The thing I've been wondering, would it be possible to flash the radio image of the stock 7.1.2 (N2G48C, Aug 2017) version on a system & bootloader image that runs version 8.0.0 (OPR6.170623.023, Nov 2017)?
So basically, use the radio software of Android 7 on an Android 8 system. Could this break anything? Otherwise I'd figure I just test this...
Thanks in advance!
Click to expand...
Click to collapse
It is perfectly fine to do this. Just flash and see which gives you better dBm signal and data speeds.
Sent from my Nexus 5X using Tapatalk
Thanks for the answer! I flashed the radio-bullhead-m8994f-2.6.37.2.21 image, but the issue isn't resolved.
Guess I'll have to wait for Google to fix this.