Invalid number error with custom ROMs - Galaxy S 4 Q&A, Help & Troubleshooting

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.

Related

[Q] VS98012B Phone app not functional

XDA,
Received my phone (vs980) and immediately rooted and installed ROM on it. I have gone through multiple ROMs with the same result in that everything works great except for the phone app. I can navigate through contacts and dial fine, but when I execute the call, the screen goes black for about 10 seconds (can still see the status bar) then finally gets to the "call in progress" screen where it immediately ends the call. Phone will not even recognize inbound calls and sends them to voicemail after about a second or two of ringing. I am currently on resurrection remix v5.1.1 but was previously on C-rom v6.5 (also tested 6.4 with same result). Unfortunately I can't say I made a call on stock before rooting/ROMming so I don't know if it's a persistent issue. I have tried clean wipe of data/system/cache/dalvik cache, and have cleared the app data for the phone and dialer apps as well to no avail. Baseband version is vs98012b. Should I try wiping internal storage as well? My next step is to return to stock and test there but that seems like a more labor intensive process that could be avoided if I'm missing something else. Could this be a possible hardware issue? All help is appreciated.
B

CM 12.1 calling problem

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

Stock / Google Dialer and rebooting when trying to make a call?

I've seen this mentioned in other places before, other threads and in the r/motox subreddit, about how the open GAPPS package apparently flashes the Google Dialer over the stock one, and it doesn't work with the Pure? Which is what causes the reboots whenever I try to make a call or, presumably, get a call, which until now I chalked up to random reboots in CM13.
So I've seen a bunch of posts about it, but none that explain how to actually fix it? Am I doing something wrong from the start?
Bonus question, I've been having radio problems on almost every AOSP rom I flash, either Wifi doesn't work upon booting and it persists in other ROMS or cell service is out (even though LTE data works fine). Is the radio (which I assume is the same as the "modem") included in each ROM package and is replaced every time you flash a new one, or does it persist in some system directory cross-firmware?
There are so many posts on how to fix I'm not sure how you could miss them. Set as default or uninstall.
lafester said:
There are so many posts on how to fix I'm not sure how you could miss them. Set as default or uninstall.
Click to expand...
Click to collapse
Set what as default? Or uninstall what? When I look in the apps list all I see is "phone". Nothing under the name google dialer or anything. It's just confusing, I didn't have this problem on other phones.
Sorry for the double post but I figured instead of making another thread I'll continue asking here, I'm STILL having cell issues, no matter what ROM I flash, stock or AOSP, or any of the radios I can find around the forums, whether it be with the February security update or not, I'm still not getting a connection. In fact once I flashed a new modem, I went from not being able to send texts etc. but able to get LTE data, to getting no connection at all. I'm totally lost, this is the second time it's happened I have no idea what to do. Happens in every single rom.
Last time it was fixed once I flashed from stock (which I had in turn flashed to try to get rid of the problem) to CM13 I think. But it was totally random, I have a feeling it didn't even have anything to do with the ROM itself...
Google searching: "Google Dialer reboots when making a call" >
http://android.stackexchange.com/qu...s-when-making-or-receiving-a-call-nexus-6cm13
https://www.reddit.com/r/cyanogenmo...cm_13_nexus_5_soft_reboots_when_a_phone_call/
Even from Open GApps own FAQ page:
https://github.com/opengapps/openga...boots-when-i-receive-or-make-a-phone-call-why
Thanks, I honestly dunno why I couldn't find that before. At first I wasn't even aware it was actually called the "google dialer" so I was just googling "phone app reboots after flash/root/etc" and obviously it wasn't turning up many results. But the stock rom rooted debloated thread had the instructions at the bottom, now I know. Whoops. Like I said, just really confusing coming from other phones where everything mostly just worked....
The baseband is still perplexing me though, in the bootloader under baseband it says <not found>. I'm keeping on trying to flash different stock roms to see if I get lucky.
EDIT: so I think flashing the modem at the SAME TIME as a new ROM might be the key? I think I saw something about that on some random obscure post and tried it out and bam, it worked like a charm. Anyway hopefully that works again when I flash to something new

Big problems with my Ascend G7-L03

Hello everybody,
I'm relatively new to the world of ROMs and I'm hoping some people smarter than me can help.
A few weeks ago, I started having issues with my phone, on the stock ROM for Wind Canada, restarting continuously. It would sometimes work for up to 10 hours, but sometimes no longer than 10 seconds. There didn't seem any rhyme or reason to it doing so. I figured that it was a good time to play around with a new ROM, and I took a backup (of a faulty operating system). It's been a bit of a ****show since then, and I don't remember exactly everything that I've tried, but here is a sampling:
CM13.1 - the ROM successfully loads, but then I get stuck in a reboot loop.
CM12.1 - I figured that if 13.1 didn't work, I shouldn't try 14.1, so I went down to 12.1. This worked beautifully, until I tried to make a call - and I can't hang up. To hang up, I need to reboot the phone. Annoying, to say the least. Everything else seems to work really well, other than a slightly shortened battery life, but I can live with that, if everything else works.
CM14.1 - I tried loading it, but it says right off the bat that the L03 isn't part of the compatible list and doesn't process. I know I can suppress that message, but I figured that if it was meant to be on that list, it would be.
Resurrection 5.1 - I don't remember what happened here, but I think it ended up in a bootloop.
I can't find the original ROM on Huawei's site, and the one that seem similar for different countries are meant to be done within the OS as an update (Update.app).
So, I'm stuck here - I can't seem to revert back to the original ROM (which was Android 4.4.4, which was fine), and I can't seem to update to any other ROMs. I want to fix this, because as far as I'm concerned, the hardware is pretty good and I can make this phone last. However, my wife is pushing me to replace it...
Does anybody have any advice as to what I should try next? I really don't feel like using CM12.1 in its current state, which is what is installed now, since I need to reboot between phone calls, but it seems to be my only option for now.
Three notes - 1) I am currently on my 5th or so install of CM12.1. I have tried to look for ways to replace the dialer, since that seems to be the problem, but I haven't found a way. Can one replace the stock dialer?
2) I have tried installing multiple GAPPs packages, including ones that supposedly replace the dialer, but this hasn't helped.
3) I don't know if this is relevant, but in CM12.1, under "About phone", my Device model is "unknown". Is that always the case?
Somebody out there must have a better solution and my hair's all gone now, from me pulling it out...
Any help you can give me is appreciated!!!
Thanks,
Steve
UuUuPpPp....
Exactly in the same boat as Steve...... "Cant hang up" is seems to be the only major problem.....i have the exact phone too.....and tried same things too to no help....any help wud be appreciated...

[Q] SM-G900P - Mobile Network not available issue on AOSP ROMs

My device is unlocked SM-G900P. I can't use my device at any TouchWiz ROMs, it is so laggy. I was installed TWRP then flashed the RR 5.8.4 with openGapps's GAPPS. Then the Google authentication's SMS works well at first boot. But when I tried to call, it says "Mobile network not available" . And it won't receives any call from others . Then I tried to flash other AOSP ROMs, first I tried Lineage OS, It's same as authentication works but not available to call to others or receive :crying:. How to fix this issue?

Categories

Resources