Database Develop

[Q] Droid 3 - GSM Module freezes

Hello,
Some time ago I bought a Motorola Droid 3 from Verizon.
As I live in Europe I unlocked it (bought a code on ebay).
I also flashed it with some radio ROM which was for a europe version of the phone.
I restored a stock ROM.
Sometimes when I try to call someone when I hit the Dial button it just starts to 'dial' shows connecting and freezes like that.
All the buttons seem responsive but whatever I click nothing happens
It just stays on connecting I can`t close this I can`t disconnect I can`t do anything other than Power off the phone and then power on again (the Power off is the only button which works normally).
Sometimes when someone tries to call me he/she receives a message that my phone is currently turned off...
I think there`s some problem with the GSM module it just freezes (no data is transfered, no calls can be accepted or no outgoing calls can be made)
When I reboot the phone everything works normally
I tried with many different ROMs but the issue is the same.
I was looking for some other Radio ROMs which I can use but I couldn`t find any.
Does anyone have any Idea what may cause this issue?

what model is listed on label under battery? XT862?
in Menu>Settings>About Phone
which system version is on phone? 5.7.906
which baseband is installed? N_03.18.29P

[Q] 5.1 Problems

So since I updated to 5.1 I have had lots of problems. Dropped calls, worse battery life, and when I call a place with a touch tone menu I am unable to get through it without pushing the number multiple times. I have already factory reset my phone twice, and I am still having issues. The most annoying one is the issue with touch tone menus. Has anyone else had this problem?
EDIT: Before anyone asks, I'm on stock 5.1 LMYM47M with Franco r21.

find a stock 5.1 rom in the n6 android development threads, flash it, and the latest supersu, both in twrp recovery, if you have it installed. easiest method to fix your issue. might not be the proper way, but thats what id do

simms22 said:
find a stock 5.1 rom in the n6 android development threads, flash it, and the latest supersu, both in twrp recovery, if you have it installed. easiest method to fix your issue. might not be the proper way, but thats what id do
Click to expand...
Click to collapse
I'll try one and see if that helps. At this point, I doubt it can hurt.

uhguy said:
I'll try one and see if that helps. At this point, I doubt it can hurt.
Click to expand...
Click to collapse
Are you on Tmobile?
The 47M seems to only work with Tmobile, since its the only one out with the M designation. The only one out for everyone else ends in the 47I (i)
I tried a few different roms and couldn't get LTE, only 3g calls. I wiped grabbed the rom from Nocturnal and so far so good.

navyvet420 said:
Are you on Tmobile?
The 47M seems to only work with Tmobile, since its the only one out with the M designation. The only one out for everyone else ends in the 47I (i)
I tried a few different roms and couldn't get LTE, only 3g calls. I wiped grabbed the rom from Nocturnal and so far so good.
Click to expand...
Click to collapse
I am on T-Mobile. I tried Chroma, and I am still having issues with touch tone in calls. I can dial a number and they show up on the screen, but when prompted to push 1 I have to hit it several times before it works.
EDIT: I flashed LeanKernel and then went back to Franco and I can now go through the dumb touch tone menus just fine. I'm not sure what happened when I initially flashed Franco, but it appears to be working now.

I was wrong. It's not fixed. Still don't have consistent touch tone menu use. Anybody else have an idea as to what could fix it?

I'm also on T-Mobile and have a lot of dropped calls across the board on various ROMs...stock and custom... Also have the m bootloader and radio but it was the same with the other 5.1 radio

uhguy said:
I was wrong. It's not fixed. Still don't have consistent touch tone menu use. Anybody else have an idea as to what could fix it?
Click to expand...
Click to collapse
I was able to get touch tones working again by disabling Enhanced 4G LTE mode in settings-->more-->cellular networks.

rjmillenbaugh said:
I was able to get touch tones working again by disabling Enhanced 4G LTE mode in settings-->more-->cellular networks.
Click to expand...
Click to collapse
This worked for me! Thanks. This was my biggest bug with 5.1. Tmobile.

DTMF tones not being registered.

So I had to call a couple different automated systems today, first PayPal then my bank
Both times I had to be redirected to an agent because it said the information I entered is not correct. I changed the length of the tones to long and I know some presses are being entered since I could navigate the menus, but it seemed when I got to multiple presses in a row (like account numbers and passwords) it wouldn't work. I even tested calling my voicemail. It told me my password was wrong, then I called from a different phone and got in just fine. I thought maybe I was going too fast so I tried it slow and still no luck. Is there something else I need to change?

I am having the same problem. Started on 5.1.

Do you have screen protector installed? Some people claim that 5.1 made proximity sensor more sensitive. Removing screen protector ( or cutting around proximity sensor) fixed the problem.

darek65 said:
Do you have screen protector installed? Some people claim that 5.1 made proximity sensor more sensitive. Removing screen protector ( or cutting around proximity sensor) fixed the problem.
Click to expand...
Click to collapse
Not sure about OP, but in my case the numbers I'm pressing show up as being pressed on the screen, but they don't register with the call itself. When I try to call my voicemail I have to push a number several times sometimes to get it to actually register. I may see "3333333", but only the last one actually registers.

I don't use a screen protector. Also like the other guy said, the button is being pressed, I turned on dialpad sounds to be sure.

Same problem on 5.1.
Sent from my Nexus 6 using Tapatalk

Are both of you that are having the same problem on stock? Figured I would submit a bug report if no one has a solution, just want to make sure someone has tested it on stock first.

I had the problem on the stock T-Mobile OTA. I was rooted and unlocked, but otherwise stock.

Stock rooted 5.1M
Sent from my Nexus 6

Same issue. Stock ROM. Franco kernel.

Stock 5.1 Franco Kernel. Same issue. Anyone getting anywhere with this. I've tried changing the DTMF from normal to long, and tried touch sounds on and off, which seems to be the only "fixes" mentioned in various places.

Eetabeetay said:
So I had to call a couple different automated systems today, first PayPal then my bank
Both times I had to be redirected to an agent because it said the information I entered is not correct. I changed the length of the tones to long and I know some presses are being entered since I could navigate the menus, but it seemed when I got to multiple presses in a row (like account numbers and passwords) it wouldn't work. I even tested calling my voicemail. It told me my password was wrong, then I called from a different phone and got in just fine. I thought maybe I was going too fast so I tried it slow and still no luck. Is there something else I need to change?
Click to expand...
Click to collapse
I had this same problem with another phone. I had to call my carrier to fix it because it was something on their end. Is everyone having this problem on the same carrier?

devilsmack said:
I had this same problem with another phone. I had to call my carrier to fix it because it was something on their end. Is everyone having this problem on the same carrier?
Click to expand...
Click to collapse
Verizon Here

Fixed issue by turning off VoLTE. So that sucks. Turned it back on after I was done activating the card I was trying to activate.

Does switching to long tones do anything? I've had this problem since 5.1 and am on Verizon with VoLTE.

Same problem here. Have had it across multiple versions of Chroma ROM (includes Franco kernel). VoLTE on means no DTMF, VoLTE off makes DTMF work perfect. Have seen references to similar problems on other phones and other networks.

New M radio (.16R) fixes DTMF recognition with VoLTE on. I'm on Tmobile if relevant. You can find this and all of the other radios here.

OTA update TO 5.1.1 solved this problem for me. Before the update it was almost impossible to enter my pass code in T-Mo voicemail.

stevemw said:
OTA update TO 5.1.1 solved this problem for me. Before the update it was almost impossible to enter my pass code in T-Mo voicemail.
Click to expand...
Click to collapse
LMY47Z fixes this on Verizon as well. I was having to wait a full second between numbers (which was a pita since I dial into a lot of conference calls every day)

swamp2 said:
New M radio (.16R) fixes DTMF recognition with VoLTE on. I'm on Tmobile if relevant. You can find this and all of the other radios here.
Click to expand...
Click to collapse
Unfortunately the new M (preview) radio fixed this but also does not permit conference calls. The 5.1.1 Tmo OTA radio maintains this fix but also permits conference calls. Specifically, this one:
LYZ48E (5.1.1 T-Mobile - Extracted from OTA - 05/23/2015)
MDM9625_104649.09.05.14R

Can receive texts/data and calls but cant make a call unless I switch to 2g Mode

Hey guys, Basically I live in Ireland and bought my friends nexus 6 when he got a new phone.
It was working great and I rooted 5.1.1 and when I saw The (only android 6.0 available) marshmallow update available on NRT I dirty-flashed it, after seeing a thread on reddit saying dirty flashing to marshmallow hadnt caused them any device defects
Had no complaints until I tried to call my sister today (admittedly the first call id made in the first two weeks of owning the phone) and it said "Sorry you don't have access to the service"
So I played around with some reboots and sim reinserting and was surprised to see that when I changed to 2g Mode, It could make the calls! Really strange, is there any chance that the marshmallow image released on NRT would've had bands specific to US carriers?
I can make calls via whatsapp for the time being I guess Lol, but if anyone could give me a headsup as to what I did wrong ( or even a solution) Id be pretty grateful!
Thanks,
Nick

wipe data/system then flash again. you should never dirty flash between 2 different android versions. and dont listen to anyone else, i bet they do have issues.

Thanks for the help but sadly this didnt work for me at all!

Was playing around last night after I reflashed and I went to system apps and on seeing telephone and phone (two seperate apps , normal?) I disabled 'phone' for a second and could place a call successfully over 3g - but obviously with no dialer interface whatsoever because the app was disabled. Ive rooted and custom flashed alot of my phones but this has me puzzled

I had this problem on a previous phone. What happened is that it was stuck on LTE only. I know this phone has volte, but try messing with mobile connection

Help, I can't receive any calls but no problems to make them.

Hello, everyone.
I need help with an issue I'm facing. My phone is not receiving any calls whatsoever and I don't know why. I can make calls without any problems, the issue is that I can't receive them.
I don't know when this started happening since I don't receive many calls, I don't know if it's a result of rooting the phone, because it's rooted, or what else can it be. I don't remember if the phone received calls before or immediately after being rooted.
I've tried flashing different modems but I haven't been successful. Also, I have gone through the settings and disabled everything that could be causing the calls to be blocked. I have also called T-Mobile and they disconnected and reconnected my phone to the network and I have gone to one store to have the sim card replaced and that didn't help either. I have wiped the cache and the Dalvik cache and nothing. The only option left that I know is to factory reset the phone wich I'm trying to avoid because I have a ton of apps and my home screens are already setup and folders created and I don't want to do all this setup again.
Here is the weird part. Under just this specific scenario I can make my phone receive calls.
Make a call to any phone
Hangup a couple of seconds after the other phone starts ringing.
IMMEDIATELY BEFORE the call is terminated (lost) dial from the other phone (the one that was called in step 1). This should be within one second and no more after the call is lost.
If I follow this procedure then the call goes through and my note 4 receives it, but the call shall be made immediately after I hang up, otherwise it doesn't go through.
Does anybody have an idea of what could be happening?
Thanks!!

try this, go to settings all the down to calls and click on call rejection which says auto rejection turn that to off, ive had the Same problem and thats what help me out