Hello,
I´ve got a critical bug with the newest nightly ( cm-10.1-20130328-NIGHTLY and No.27)on my Motorola Droid 4.
Everytime I make a call, or there is an incoming call I get the message that the process "com.android.phone" has been crashed. It´s not possible to make calls.
I had the same issue with an older nightly (Version of February I think) but it was fixed with another version (cant remember which one it was). Now with the newest the same problem appears.
I use the droid 4 in Germany, anybody with the same problem, or who has a solution for this bug?
Thanks for your help
Edit: I get closer:
Everytime I update I change the following things in the build.prop
telephony.lteOnCdmaDevice=0
ro.telephony.default_network=3
ro.telephony.gsm-routes-us-smsc = 0
ro.product.locale.language=de
ro.product.locale.region=DE
persist.ril.ecclist=911,*911,#911,119,118,999,08,0 00,112,110
ro.com.android.dateformat=dd.mm.yyyy
ro.com.android.dataroaming=false
ro.mot.phonemode.vzwglobalphone=1
ro.mot.phonemode.vzw4gphone=0
persist.radio.lte.mm.disable=1
ro.mot.lte_on_cdma=0
Without these changes the cell phone has a very bad reception in Germany. But to make phone calls is possible.
Anybody an idea which of these changes might be the problem?
I use the droid 4 in Italy and I have the same problem.
Try the following build.prop edit which was posted in the cm10.1 thread:
Fellow GSM users, I found the answer to com.android.phone crashes on receiving calls & hanging up outgoing - the phone app thinks it's in CDMA mode.
Set persist.radio.ap.phonetype=1 to force it to GSM.
Sent from my DROID4 using xda app-developers app
I had this same issue for a long time, it drove me crazy.
eventually i removed safestrap and went back to stock then re strapped. now any rom i install i use these changes to the build and NO others. Some cause more problems then they claim to fix.
telephony.lteOnCdmaDevice = 0
ro.mot.phonemode.vzwglobalphone = 1
ro.telephony.default_network = 3
ro.telephony.gsm-routes-us-smsc = 0
persist.radio.ap.phonetype=1
This fixed my issues and now i can make and receive calls without any problems...speakerphone at the moment is different
I'm in France and I've the same problem. With cyanogen, AOKP and liquid. Slightly less with aokp but I've.
If anyone have some solution to solve the problem we are more interested
If you don't have found solution. I just install cm-10.1-20130612-NIGHTLY-maserati and I don't have problem with android.phone.
Try the solution that was posted in this thread:
http://forum.xda-developers.com/showthread.php?t=2314452
I had similar problem, I had broken phone, or broken data - depending on build.prop configuration and it solved almost all my issues. I still get wrong signal strenght indicator, but it's not so important to me.
kolenda said:
I still get wrong signal strenght indicator, …
Click to expand...
Click to collapse
Has there come up a solution to that?
On the DROID 3 one only had to change the build.prop entry: "ro.mot.phonemode.vzwglobalphone=" from 1 to 0. Does not seem to have the same effect on the DROID 4, though.
Related
Hey Optimus users,
I'm using CM10 on new bootloader and I have a strange problem: around 30 % of my calls end right after 2 seconds the call was estabilished. So I call someone, hear "hello" and call ends. My previous system was CM7 and it was flawless, no call disconnections so it's obviously not a hardware related error.
I tried every method, changed baseband, ril, erased cal data etc.
Can someone help me analyzing the log file I (alogcat) made? I'm unfamiliar with at commands etc.
Here's the file: http://paleee.hu/alogcat.txt
Maybe the answer is hiding between the (logcat) lines...
Thanks in advance!
Sent from my LG-P990 using xda app-developers app
This morning I installed [STABLE][ROM][4.1.2][JZO54K] CyanogenMod10 | BUILD #3 with N.O.P.E. V2 - 800 MHz kernel and it work all fine until I noticed that I can't dial out a certain number.
The phone number is my GFs and the phone is right next to me. GFs phone rings for half a second and my phone say network busy.
Have tried all sorts of things (battery out, new dialer, removed contatcs,...) already but nothing changed.
Anybody had a similar problem and knows a solution?
This is an odd problem. Try swapping Sim cards and call your gf from her phone with your Sim in it and hers in yours. I doubt that would be the kernels or the roms fault.
Sent from my HTC Desire C using xda app-developers app
This problems caused by service provider. It happens time to time. Just wait a couple minutes.
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
640k said:
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
Click to expand...
Click to collapse
Hmm, it doesn't seems like poor performance. I ended up every task and it still happened.
However, I noticed that when I check the "2G ONLY" option it comes back to work. Maybe it's something with the HSPA/HSPA+ connection.
it could be completely carrier dependent then. my experience has been with vzw.
Moto X "Call Ended"
I have experienced this same problem in Houston on the T-Mobile network after switching over to Android. My T-Mobile rep told me they have had towers vandalized for copper which has impacted service for them, I believe he said it was about 15 towers and 10K a pop to get things corrected. What gets me is I was on a Bold 9900 and while I had signal problems in the affected areas of town I didn't not experience the "call ended" issue. I can also call other T-Mobile phones from those same areas but not land lines so to me this seems like a possible network routing issue which I have seen before between specific carriers.
If the problem does continue I may have to switch carriers. T-Mobiles service was previously outstanding in Houston but recently had not been great after the 4G LTE upgrades. I support multiple hospitals and need service to work correctly and will work with the T-Mobile Engineers to see if I can make headway on that front. I noticed another MotoX user reporting he only had the issue when flying in to Houston for work and that everything worked for him outside of Houston. His solution was to operate in 2G mode which for me is really not an option. I have to handle a lot of tasks over the network while on calls.
Anyways I would appreciate it if others could post if they are experiencing these issues and give as many details as possible so we can try to isolate the root cause of this problem and if found to be a carrier issue we can escalate with them. Thanks
dicarli said:
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
Click to expand...
Click to collapse
Call Ended Issue Resolved
Hi All,
I see this Call Ended Issue in many brands. So I assume the error is a combination of the Network along with the SimSlot.
I tried various combinations for my Moto-E mobile.
Before i post the solution i found, Let me provide a brief about the problem.
I use Vodafone network on sim1 slot and Uninor network on Sim2 slot. I started facing the call ended issue on my sim 1 vodafone network.
I inter changed the sim's and found the network working absolutely fine. This makes me to understand that the sim1 slot with the vodafone carrier has some network issue where that IMEI code has some problem.
i tried to place the vodafone sim again on the sim 1 slot and found the problem persists. So i came to that conclusion.
Hope this might help you and provide a instantaneous and temporary resolution.
Thanks,
Praveen.
Call Ended problem still going...
Hey,
I just rooted my Moto X (XT 1053), like 5 min ago, in the hope to fix this same problem. I`m no programer/developer and have nothing against rooting, I just don`t think I`m that kind of user. Anyway, about a week ago my phone started to drop my calls right after dialing. I restored factory settings, updated it and nothing worked. I took it for service and they offered to charge me 150 bucks to restore factory settings and update the software. So I was kinda forced to root and try to fix it this way. The problem is that I probably don`t understand half of what you guys say, so if there are any kind souls out there, please help me out.
To sum it up:
- No Sim Card error
- I get carrier services and can use mobile internet (3G because 4G is still too explensive here in Brazil)
- Directly drops my calls
- Won't receive calls
- Won't send or receive text messages via carrier (just over 3G or wifi)
I`ve tried another carrier's Sim Card, no go.
I`ve tried my Sim Card on another phone and it worked just dandy, so I really don`t think it`s carrier related.
I`m running Android 4.4.3, as the other updates weren`t available for my phone via Motorola. I thought maybe updating to a newer version of Android might do the trick. I just have no clue on how to do that on a rooted phone... or on a non rooted phone for that matter.
Can anyone give me any tips/pointers/etc... ?
Thanks!
I have the same issue with my moto x on Verizon. Have you been able to figure it out?
Hi everyone, I'm using Stocklite v8 custom rom, I am facing following issues,
1. Even when I have good network coverage (around 59 dBm) there is a huge lag while receiving a call. A caller to my number have to wait for around 20 seconds to receive a call, so sometimes the caller may end the call thinking my number is unreachable.
2. I don't receive SMS many times especially from web (e. g. I have not received SMS in first attempt from google when they wanted to verify my account) . I checked all the settings from my service provider but they said everything is fine.
I logged a complaint to my network provider but they think everything is fine. I even bought new SIM card thinking if the old one is causing problem, but still facing the same issue.
Even before Stocklite I was using Apocalypse rom & I was facing the same issue. So is it Android that causing me the problem?
Plz help me. Thanks in advance.
[1] Did you tweak some clock speeds, coz sometimes in roms they tweak it when your phone sleeps its clock speeds go down like 100mhz then when screen is on its back to full speed. And why do you have to wait 20 seconds??
[2] Try to go to airplane mode and turn it off, reboot. If that didnt solve your problem then apply a pin to your sim card, when i did that i can recieve sms.
Hope this solves your problem
timurdis said:
Hi everyone, I'm using Stocklite v8 custom rom, I am facing following issues,
1. Even when I have good network coverage (around 59 dBm) there is a huge lag while receiving a call. A caller to my number have to wait for around 20 seconds to receive a call, so sometimes the caller may end the call thinking my number is unreachable.
2. I don't receive SMS many times especially from web (e. g. I have not received SMS in first attempt from google when they wanted to verify my account) . I checked all the settings from my service provider but they said everything is fine.
I logged a complaint to my network provider but they think everything is fine. I even bought new SIM card thinking if the old one is causing problem, but still facing the same issue.
Even before Stocklite I was using Apocalypse rom & I was facing the same issue. So is it Android that causing me the problem?
Plz help me. Thanks in advance.
Click to expand...
Click to collapse
Wrong section mate
Please read rules before posting, this is General Thread...NOT Q&A THREAD, so next time post your questions in the correct section, thank you for understanding it
Cyber_Dragon001 said:
[1] Did you tweak some clock speeds, coz sometimes in roms they tweak it when your phone sleeps its clock speeds go down like 100mhz then when screen is on its back to full speed. And why do you have to wait 20 seconds??
[2] Try to go to airplane mode and turn it off, reboot. If that didnt solve your problem then apply a pin to your sim card, when i did that i can recieve sms.
Hope this solves your problem
Click to expand...
Click to collapse
Thanks for the reply.
[1] Yes, I did check some of the clock speed tweaks & Minimum RAM tweak. But unchecked all these tweaks & then tried it but still the problem is persisting.
The problem is that sometimes when people call me they don't hear my caller tune for around 15-20 seconds & able to hear the tune after I receive the call although there is good network strength. So most of the people don't wait for that long thinking my number ain't reachable & end the call. But if they give another try just after the first attempt, they get a reception from me within 5 seconds I hope u got my point now.
[2] I did try that airplane mode trick but seems it's not working for me.
As I already said this issue doesn't occur everytime, but it happens randomly & very frequently. Also sometimes I get duplicate SMSs from my network provider. They checked everything from their end & confirmed that it's not a network related issue.
So, I believe it's my phone which is causing me this problem.
Try not using internet
Try not using internet when not in use..
try uninstalling apps which enables when a call is made or recieved like shaplus caller info and truecaller or call recorder.
cyb3rillusi0n said:
Try not using internet when not in use..
try uninstalling apps which enables when a call is made or recieved like shaplus caller info and truecaller or call recorder.
Click to expand...
Click to collapse
I had installed call recorder once long time ago, but I have already uninstalled it. Other than that I have apps such as hangouts, clean master,google settings etc & rest are multimedia apps, but I don't know if they interfere during calls or not.
I have noticed one thing that the mentioned problem occurs mostly when my phone is in idle state, but it occurs when the screen is ON & when the phone is busy as well. I have already unchecked all the speed tweaks in my phone but still no solution found.
timurdis said:
I had installed call recorder once long time ago, but I have already uninstalled it. Other than that I have apps such as hangouts, clean master,google settings etc & rest are multimedia apps, but I don't know if they interfere during calls or not.
I have noticed one thing that the mentioned problem occurs mostly when my phone is in idle state, but it occurs when the screen is ON & when the phone is busy as well. I have already unchecked all the speed tweaks in my phone but still no solution found.
Click to expand...
Click to collapse
backup your apps, sms, data..
and flash stocklite again and do full wipe and wipe dalvik cache too.
cyb3rillusi0n said:
backup your apps, sms, data..
and flash stocklite again and do full wipe and wipe dalvik cache too.
Click to expand...
Click to collapse
Thanks I actually found out that its the problem with the phone itself. I tried to check on other handset and I didn't face such issues.
But now I am facing another major issue.Whenever I change my sim card and insert it into another phone, my dad receives an sms from number that says my IMEI has been stolen and everyday my phone credits get deducted. I dont know whether i have ever enabled change sim alert option or not but I am unable to find out that option in my stocklite v8 rom.
Please tell me how to disable that option in my phone, I am running out of my credits.
It comes and goes without a change of setting g, but instead of a phone ringing or vibrating it just shows a new voicemail. My wife complains that I never answer my phone but it never rings, even with all the sounds at their highest. Any ideas what might cause this?
On pure rom
Sent from my Nexus 6 using Tapatalk
Bad/weak signal?
Have you tried having her call you again to see if it rings - while in the same room? I feel like it could be a rom issue, but it's probably more related to service.
Carrier or rom. Need to reflash stock and start from scratch. If works on stock which I believe will be the case since mine works then clean flash the rom. It's not rocket science.
If you check the Sprint thread in General you'll see that a lot of people, including myself, have the same problem. It happens when you're connected to LTE and WiFi at the same time. Until a patch is released by Sprint, it seems the only thing we can do is turn off WiFi or change the preferred network type to 3G.
The bug is present on stock M P3 too.
Sent from my Nexus 6 using Tapatalk