CM 12.1 calling problem - Galaxy Grand 2 Q&A, Help & Troubleshooting

First of all hello everyone..!
this might seem like a noob questions, but the issue I am facing are real..
I installed the latest update of cm 12.1 yesterday "cm-12.1-20150911-UNOFFICIAL-ms013g-ver_AIO"..
I had been using "cm-12.1-20150614-UNOFFICIAL-ms013g-ver4_2" till yesterday
and overall, all the improvements in the latest ROM are fantastic..
ISSUE: right from my first boot, every time I get a call, and end it, it just doesn't hang up and the phone just shows the error: com.android.phone has stopped, and right after I click okay another error pops up: Dialer has stopped working
and then I neither can hang up the current call, nor I can make/take another call, the contact name of the first caller also gets stuck on the screen...until I restart the phone..and then it happens all over again..!
i.e.: A called me first, hanged up and the error appeared, now even if B calls me, the screen shows A calling, and I can't answer or reject the call..!
Can anyone please tell me how to get past that?

Flash the latest CM12.1 by Mukul SOni or Aapav

Related

Three Problematic Issues - Help Please!

Morning/Afternoon/Evening folks.
I am experiencing the following three problems with my Nexus 4. I am running on stock Jelly Bean 4.2.1 and rooted with a TWRP custom recovery.
1) Its been of lately since the 4.2.1 update. Perhaps its the update itself. I get the following error message when someone is trying to call me and I can't answer the call at times. So I have to hit okay and the call gets automatically disconnected. Then I have to redial the person OR if I end a call with someone the same message pops up and then I have to hit okay to proceed.
Message in question: unfortunately the process.com.android.phone has stopped.
2) I also get the "unfortunately process.com.android.phone has stopped" message when I dial *#*#4636#*#* and go into Phone information and if I want to change something I get the same message.
3) Last but not least, when I set it to LTE, it goes back to WDCDMA preferred without me a) rebooting or b) changing the settings again. Again is anyone else experiencing this or is it just my phone?
Thanks in advance!

Installed i9500 ROM instead of i9505 ROM

I was trying to install the GoldenEye Rom 12 for the S4 i9505. I don't know how, but I accidentally installed the Rom for the S4 i9500. Now I'm unable to make/receive calls and Wifi is disabled.. It occasionally lags on almost every app. When I'm making calls, I'm able to dial the number. As soon as I hit the call button, my phone screen turns black and the notification bar starts flickering. As for receiving calls, I'm unable to pick up calls as the screen doesn't even appear. I tried restoring from a nandroid backup, flashing a stock rom/recovery and it doesn't solve the problem. Any ideas how do I solve it?
Help please.. It's urgent
xComplicit said:
I was trying to install the GoldenEye Rom 12 for the S4 i9505. I don't know how, but I accidentally installed the Rom for the S4 i9500. Now I'm unable to make/receive calls and Wifi is disabled.. It occasionally lags on almost every app. When I'm making calls, I'm able to dial the number. As soon as I hit the call button, my phone screen turns black and the notification bar starts flickering. As for receiving calls, I'm unable to pick up calls as the screen doesn't even appear. I tried restoring from a nandroid backup, flashing a stock rom/recovery and it doesn't solve the problem. Any ideas how do I solve it?
Click to expand...
Click to collapse
Hey
Is your phone definitely GT-I9505?
Which operator/telco are you using, in which country?
That happened to me when they first upgraded to the new bootloader. My guess is you're still on the older non-KNOXy one?
It's weird that your phone's not bricked. I would make sure that you're actually using a i9505 then download a rom for that device and flash it.

[Q] CanĀ“t use Phone app

Hello, I have problem.
Iam using noobdev 4.4. CM11 nightly on my i9505 without problem, but suddenly, maybe after last nightly update phone app stop work.
I can go to internet, receive messages, but when i want to call someone the screen goes black and doesn't answer and the menu bar "flash" I have to wait during 20-30 seconds before to return on my home screen. When I receive a call, after answering it, screen goes black too. I cant hear the person on the other side, and they cant hear me.
I tried everything, flashing many other modems/radios, roms, restoring backups, flashing another recovery, flashing official firmware and it still dont work.
Help me please:crying:

Invalid number error with custom ROMs

I couldn't stand ugly Touchwiz UI anymore, so I decided to root my I9505. My first ROM was Danvdh GPE, I really liked it, everything was fine, except one thing annoyed me: dialed numbers appeared as "Unknown". Almost every number which I dialed from dialer or even from contacts, appeared as unknown and I had to enter it again or save it to contacts. At first, I thought that it is a ROM issue, because I didn't had this on stock, but then I upgraded to crdroid marshmallow ROM and still had the same problem, but now, every time I started to call or sometimes after successful call I received "Invalid number" error additionally. I tried different dialers, but still got the same problem. Why these dialers are not recognizing my numbers? Is it possible to fix this?
The problem is that Dialer do not show the dialed numbers. Even though I receive "Invalid number" error, phone still makes successful call.
It's a known issue on most of the custom Android 6.x ROMs, with the possible exception of JDCTeam's AOSP. Until the developers work it out, you either have to deal with it, or not use an Android 6.x ROM.
I had the same issue with Danvdh's Lollipop ROM. It's strange that some of the outgoing calls are shown as unknown and some of them are shown correctly. I don't understand what is causing this. I had a presumption that outdated baseband is causing this issue, but I updated it and still everything is the same.
I flashed to JDCteam's AOSP Marshmallow ROM and now everything is working perfectly! Thank you.

reboots when keys are pressed for a long time

have a nice day
Third-party rom has this error;
finally, i found the reason why the phone restarted itself
reboots when keys are pressed for a long time,
I'm experiencing this error especially in the fingerprint reader
for your information..
my device oneplus5..
always the most current firmware was installed.
i encountered this error.
Third-party rom error;
Codename Phoenix
Pixelexperience
Havoc-Os
hopefully, can be corrected
thanks all..
SqooK said:
have a nice day
Third-party rom has this error;
finally, i found the reason why the phone restarted itself
reboots when keys are pressed for a long time,
I'm experiencing this error especially in the fingerprint reader
for your information..
my device oneplus5..
always the most current firmware was installed.
i encountered this error.
Third-party rom error;
Codename Phoenix
Pixelexperience
Havoc-Os
hopefully, can be corrected
thanks all..
Click to expand...
Click to collapse
And you're sure that this issue is a rom fault? Do you have any logs or steps to reproduce? You are the only one with this issue?
At which roms does this not happen?
strongst said:
And you're sure that this issue is a rom fault? Do you have any logs or steps to reproduce? You are the only one with this issue?
At which roms does this not happen?
Click to expand...
Click to collapse
I'm sure the error is a rom error because I don't encounter this problem in oos rom
remember that there was a mistake in the past. The screen was locked and only the led light was on,,He wasn't making a move on the phone.
I get an error when I tap the keypad area repeatedly or when the phone is in a closed area (pocket mode)..
this error is more of a problem I have encountered in the last 2-3 months.
for example aex romda and unofficial pixelexperince mod did not have this error...
SqooK said:
I'm sure the error is a rom error because I don't encounter this problem in oos rom
remember that there was a mistake in the past. The screen was locked and only the led light was on,,He wasn't making a move on the phone.
I get an error when I tap the keypad area repeatedly or when the phone is in a closed area (pocket mode)..
this error is more of a problem I have encountered in the last 2-3 months.
for example aex romda and unofficial pixelexperince mod did not have this error...
Click to expand...
Click to collapse
As I wrote before: please take logs and steps to reproduce. Then post is within the specified rom thread, cause here no developer takes care of it and I can't remember to read a similar issue somewhere.
ok, thanks
Random Reboots
I had the problem of my One plus 5 rebooting over and over from first initial set up to updating the phone from stock to 9.0.4. I unlocked it and flashed crDroid hoping it would fix it, initially it didn't until I just thought of trying to disable the hardware keys in the crDroid settings and chose to use onscreen software keys and so far no forced reboots since toggling the hardware buttons off. So maybe it is an issue with the system getting confused between a screen tap and hardware key press if someone can confirm this helped their one plus 5 rebooting on its own even after updating to latest ROMs from official updates.
Hello
there is an error I've encountered in a long time
I encountered this error in other roms with havoc-os
restarting in the phone pocket
oneplus 5
I think the source of this error is caused by double-clicking on the lock screen
(I don't have a problem when I close the settings)
when I open the setting, I'm having this problem, so my idea is why.
Can you check the code order?

Categories

Resources