I put the new AW2.0/Android N developer preview on my AT&T LG Urbane 2nd Ed LTE and now I can't make or receive calls. Tried rebooting the watch & the connected phone. Wiped watch and started over. Got the SIM card recognized immediately after wipe but still couldn't make or receive calls.
Yes, it is an issue with the 2.0 preview. Reinstall the 1.5 image (for after testing) from the same page.
phone functionality is completely broken, or just sometimes on aw2 dp2?
Cellular is broken, I reported it here.
Related
I bought a refurbished Motorola Defy+ which came preinstalled with Gingerbread 2.3.4. Out of the box, the phone was able to receive calls, although I didn't test making calls at that time.
I ran the stock Software Update from Settings, and this installed 2.3.6 on the phone. Since that point, I can no longer make or receive calls on the phone. As soon as the phone tries to make the connection, it reboots: either when making a call into the phone, at the first ring, or when dialing out. I have confirmed that it's not the dialer itself that is the problem by using different dialer apps.
I have performed a full factory reset on the phone and tried with wifi, etc turned off but it has made no difference at all. Other features of the phone are absolutely fine and I have had no unexpected reboots due to any other cause.
After searching around it seems quite a few people have had problems with their Defy+ rebooting, but this is generally either during a call or just randomly. In my case it is absolutely at the exact time that it tries to make the phone network connection and at no other time.
Could this be a hardware problem, or is it more likely to be the 2.3.6 ROM installed by the software update? If I install another ROM, is it likely to fix the problem? If so, how would I go about downgrading the phone to the 2.3.4 version?
Thanks in advance.
OK, I jumped the gun.
I hadn't actually connected to any of my mobile phone network's APNs at the time I posted the above. Now that I have configured it to connect via 2G or 3G, I get random reboots all the time.
Not that this helps or anything.
Hi everyone,
I recently bought the phone from T-Dimension and it's having some issues and I was wondering if anyone could help me out or if they've run into something similar. The issue is I can't seem to send/receive any calls and I can't send/receive any texts. The bizarre thing is it works for the first 45 seconds when I reboot but then locks me out straight after that. The phone is issued from Hong Kong and had Color OS on it but I flashed CyanogenMod onto it, here's some more information.
- The phone is connected to Amaysim, which runs of the Optus network I believe, so it's connected onto the mobile network just fine.
- The Micro-SIM card I'm using is brand new, it's put in correctly into the slot, meaning upside down facing towards the bottom of the phone, so that's fine.
- I've tested the SIM with other phones and it works perfectly fine.
- When it locks me after 45 seconds, it fluctuates from saying, "Call Not Sent" to just it being stuck on the dialling screen.
- After being locked out, I can't receive any calls either, I've tried calling the phone but nothing shows up.
- After being locked out, I can't receive any messages either, when I try to send a message it just stays stuck in sending, and if I restart the phone, it just says the text failed.
- I've contacted Amaysim Help Desk, and they say my problems lie with the phone being locked, and I'll have to contact the manufacturer to sort it out.
- I've also contacted my supplier, who seems to have trouble finding out the issue.
- APN settings are set correctly with my mobile carrier.
- Already done a factory reset, didn't fix the issue.
- Put the preferred network type to 3G under Mobile Network settings.
- I flashed CyanogenMod 11S using this tutorial from youtube, /watch?v=QDKOEtN9pbo and downloaded the cm-11.0-XNPH22R-bacon-signed.zip file.
Please can anyone help me with issue, sorry for long wall of text, I really want this phone to work!
Cheers,
You probably should flash another modem & then try.Here
http://forum.xda-developers.com/showthread.php?t=2824139
Sent from my One using XDA Premium 4 mobile app
LukaZilla said:
Hi everyone,
I recently bought the phone from T-Dimension and it's having some issues and I was wondering if anyone could help me out or if they've run into something similar. The issue is I can't seem to send/receive any calls and I can't send/receive any texts. The bizarre thing is it works for the first 45 seconds when I reboot but then locks me out straight after that. The phone is issued from Hong Kong and had Color OS on it but I flashed CyanogenMod onto it, here's some more information.
- The phone is connected to Amaysim, which runs of the Optus network I believe, so it's connected onto the mobile network just fine.
- The Micro-SIM card I'm using is brand new, it's put in correctly into the slot, meaning upside down facing towards the bottom of the phone, so that's fine.
- I've tested the SIM with other phones and it works perfectly fine.
- When it locks me after 45 seconds, it fluctuates from saying, "Call Not Sent" to just it being stuck on the dialling screen.
- After being locked out, I can't receive any calls either, I've tried calling the phone but nothing shows up.
- After being locked out, I can't receive any messages either, when I try to send a message it just stays stuck in sending, and if I restart the phone, it just says the text failed.
- I've contacted Amaysim Help Desk, and they say my problems lie with the phone being locked, and I'll have to contact the manufacturer to sort it out.
- I've also contacted my supplier, who seems to have trouble finding out the issue.
- APN settings are set correctly with my mobile carrier.
- Already done a factory reset, didn't fix the issue.
- Put the preferred network type to 3G under Mobile Network settings.
- I flashed CyanogenMod 11S using this tutorial from youtube, /watch?v=QDKOEtN9pbo and downloaded the cm-11.0-XNPH22R-bacon-signed.zip file.
Please can anyone help me with issue, sorry for long wall of text, I really want this phone to work!
Cheers,
Click to expand...
Click to collapse
Hey there fellow Aussie. See link provided by other member, it should fix you up.
Transmitted via Bacon
That modem actually proved to be worse for me.. Before I didnt have stable 3G connection.. that modem made my 4G connection worse too. The best, and most stable modem I have found thus far is in the latest nightlies. It is still very very very weak when it comes to 3G connectivity but its better than everything else I have tried. And believe me, I have tried pretty much every rom there is on this forum including XNPH22R, XNPH25R, MahdiRom, CyanHacker, and All the nightlys.
The only one I havent tried is Color OS because I am afraid it will lock my bootloader again.
(Duplicated from previous post as per suggestion by admin. See here: https://forum.xda-developers.com/general/help/voice-transmission-phone-calls-t3690651 See Addendum notes)
Hello! Long-time lurker, first time poster.
I have a sudden problem with my Android phone (Samsung Galaxy S6 running Android 7.0). Hopefully you bright gentlemen and gentle-ladies can help me:
Approximately 1 week ago (edit: 3 weeks ago), my phone stopped transmitting Voice data on phone calls. I cannot hear what the other user says on their phone, and they cannot hear me, however, pressing number keys DOES transmit the dial-tone to the other user (both ways). It does not matter if I call them or if they call me. It does not matter where I am physically, I have tried in several locations around the city (likely on several towers). It does not matter if they are using a mobile or land-line. (Addendum: Hangouts dialer functions perfectly with the hardware, before and after factory reset(s), Bluetooth headset works with Hangouts but not regular Phone)
During this time, all of my data connections work fine. Texts, Email and Browsing is unaffected. Phone performance is normal.
Since this has occurred, I have:
- Simulated battery disconnect
- Wiped Cache Partition
- Force-stopped the Phone app (all three instances)
- Verified the physical Microphone is working using the Voice Recorder app (it works fine)
- Booted the phone in Safe Mode
- Contacted my service provider to check in there was any problems with my account or transmissions.
- Transferred my Sim card to another device to test if my card/connection was ok. (Voice worked 100% on the secondary device)
- And lastly today (two weeks ago); Completed a Factory Reset
(Addendum:
- Flashed stock firmware from Sammobile via Odin
- Attempted to clean out the Microphones with toothpicks and blunt metal objects, just to be sure
- Plugged in and removed a wired headset as well as checking for debris)
I am sitting here now trying to understand how a hardware problem could possibly cause a failure of Voice encoding on only one app, and how to fix it. Or how a software problem survived the Factory Reset (and Firmware flash) into the fresh install. I did indeed try without any 3rd party apps being installed, without even adding my Google or Samsung accounts to the phone, just plain old Android; no dice.
Any suggestions?
I recall one fixing another phone that had a problem with its Capacitive Touch Screen being not sensitive enough/not reading presses problem by accessing a special menu that allowed me to re-download the driver. Is there anything like that for the Voice? (Addendum - I have looked at all the star ** codes available for this model and tried several, nothing has worked so far)
Thanks!
Thoughts today (Oct 31/17): I am not sure that flashing a custom rom is really what may fix the phone. I am willing to do so, but it is somewhat frowned upon by Canadian carriers (or at least it used to be). I was curious if it was a problem with Noise Cancellation or an SD Card problem as those are issues brought up when googling the issue. My current plan is to flash to a stock Android 6.0.1 and see if the phone works then. If so, then try the standard upgrade path. Any suggestions will be helpful!
I want to start by saying thank you to everyone on this forum. I have learned so much from reading the guides and resources (particularly those by @Gawd, @spanna, @Heisenberg, @EddyOS, and @Timmmmaaahh. I know some may have moved on but you legacy remains.).
This issue seems to have come up before on the forum, but I have not found one that matches my own situation with a solution, unless I am missing something. I am also lucky in that I have access to another near identical OPO without the issue for comparison. I am visiting my family and we all have OPO.
I have noticed that my phone will have decent to good signal (1-4 bars of Tomobile LTE) be able to use cellular data and send SMS, but not make and receive phone calls in certain areas. I would have been content saying this was a reception/carrier issue. However, I am visiting family for Memorial day and have been able to troubleshoot this with their phones. I bought my parents OPOs when it came out and my brother has a Find7, so we all have essentially the same hardware. For my troubleshooting I used primarily my mother's OPO (not updated since CM11S) and occasionally my brother's Find7. Both my mother and I have the 64 GB edition of OPO purchased around Oct-Nov 2014. Both are cobranded with Cyanogen, though mine was purchased a month or two prior to hers. When comparing the OPOs I notice her phone is able to send and receive calls in places where mine is not able. We have similar reception. I have cellular data and can still SMS. The issue is just with calls. I have tried the following (i have bolded things which I noted were different):
Basic stuff:
1) Making and receiving calls with both phones side by side. Her phone can send and receive calls in all areas (even with just one bar), while mine can only make and receive calls in some areas. My brothers Find7 has identical performance as my mothers phone.
2)Toggling airplane mode. -- Same result.
3)Toggling LTEonly, 3g only, and 2g only. -- Same result.
4)Verifying APN -- Identical for all three phones
5)Swapping SIM Cards -- both phones perform the same irrespective of which sim card is in it.
6)Verfied IMEI -- present in all phones.
7)Verifying signal strength (dBm/asu) in phone settings (*#*#INFO#*#*) -- near identical between phones. Our dBm numbers were the same but my asu number was sometimes triple her phone's asu. Her's was identical to the Find7.
More advanced stuff:
8) Removing the back cover and making sure the terminal are making contact to the backplate antennae.
9) Changing roms and firmware. No success.
- I had recently upgraded from the final release COS 13 to the latest Oreo RR with a clean wipe using TWRP. I was running RR when I first started this.
- First I tried flashing my recovery file with TWRP. It says it ran successfully, but didn't make any changes to the system.
- Since my mothers phone has no issues I tried to replicate her setup. I fastboot flashed the cm-11.0-XNPH05Q-bacon-signed-fastboot.zip provided by spannaa.
- I found some similar posts to my problem which linked to gawds firmware. I verified that both my mother's working OPO and mine had the same OS (XNPH05Q) and baseband (c7-00020) I also tried flashing different firmwares with no benefit.
- I tried fastboot flashing back to COS 11 XNPH33R (what my OPO came out out of the box with).
- I then used EddyOS guide to return device to stock COS 13.1.2. with no change.
- Thinking another new ROM may include a better firmware. I most recently did a clean install of AOSPExtedned and currently have baseband c6-0241.
Going forward:
- I was thinking of flashing gawds firmwares with AOSPExtedned. Is this safe?
- Looking to disable/unlink my google voice account from my cell number. My mom does not have this set-up. I noticed a delay in making calls, and that my google voice account has a log of all my missed calls (those that never make it to my cell). Maybe it interfering with my calls going in and out.
- Any suggestions on diagnostics I can run while I have access to my Mom's functioning OPO.
Much thanks for everyone's help.
Hi everyone. I have a 2020 Moto G Power that uses the Verizon LTE network but is unlocked and on a Straight Talk plan. I bought it used and it has Android 11 on it. Build number is RPMS31.Q1-54-13-6 and is all stock, but it just had a security update overnight, so not the same that i've been having the issue on.
The problem I'm having with the phone is that I noticed that calling will randomly not work. I'll try to make a call, there will be no audible sounds on the handset like the normal ringing or anything, and the call will just hang up after a few seconds. I've been fixing it temporarily by rebooting the phone and it starts working after it comes up.
The issue appears to be either with the whole phone, or just the Phone app/calling in general. I only ever checked the calling function before trying to mitigate it with a reboot.
Has anybody heard of this kind of issue, know what might be causing it, or know any steps to troubleshoot it or permanently fix it?