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.
I tried the latest dirty unicorn ROM and the resurrection remix rom and I am having trouble with the data and calls. It says that it can't recognize the Sim card (though it works fine on the stock rom).
I found on the RR official page that I just have to turn the cellular data off and them back on and my LTE connection works, but I can't make any calls. It says my cellular data connection isn't working but I can get on the internet, wifi, bluetooth, etc.
I have tried this as well "Go to apps then default apps then tap phone for the default call app"
Is there a fix for the SM-N900V?
I'll keep looking, but if anyone can point me in the right direction I would greatly appreciate it!
Has anyone had this problem with the SM-N900V and got it working? I love the RR rom and 6.0 mm, please help.
Hi all--
I wonder if you could please help me solve a tricky issue?
Before rooting, phone worked fine. Brand new Moto 5G Plus activated on Sprint network.
After rooting my G5 Plus with a custom rom (Dirty Unicorns), everything worked fine except I lost my LTE signal (Sprint). The phone functions in all other capacities (calls, SMS, wifi). To be clear, the phone is receiving a Sprint signal, but no data LTE/3G is passing through. Phone calls and SMS are fine.
When I go to Settings-Network & Internet-Mobile Network-Advanced-Carrier Settings, I get an error-- "com.android.phone has stopped."
I decided to test with another reliable custom rom so I installed LineageOS 15.1. Same exact problem-- no data, and carrier settings brings up ""com.android.phone has stopped."
Any ideas? I've googled myself to death and I've not found anything that has worked.
Thanks in advance, everyone.
Could you get us trough ur procedure of flashing ?
Sure
All done in TWRP
Factory reset (wipe data/dalvik/cache)
Install Custom Rom (either Lineage 15.1 or DU v12.5.2)
Wipe cache/dalvik
Install GApps (ARM64-- I tried to install 32-bit GApps as I've heard Moto G5 Plus runs on 32-bit architecture, but it failed-- install log told that ARM64 was the correct version for my device)
Wipe cache/dalvik
Install Magisk
Reboot
That's it-- one thing I noticed when restoring my manufacturer rom image was that I needed to issue a *#*# dialer command to get SprintDM to start recognizing the network. When I tried to issue that command in DU and LineageOS, nothing happened.
Following up on my last email
Does anyone know if the ##72786# or *#*#72786#*#* dialer command (which forces a system update to provision data with the carrier) is specific to Sprint or if it's part of Android? The reason I ask is because this command works fine on factory roms but doesn't seem to work on my rooted phones (in addition to the Moto G5 Plus, same thing happens with my wife's super old rooted Moto X with Renegade custom Rom-- but no problem with data on this phone). On stock factory rom, the phone resets and SprintDM provisions the data. On rooted Dirty Unicorns and LineageOS, nothing happens. I wonder if this broken command is related to the "com.android.phone" error I discussed above.
schleima said:
Hi all--
I wonder if you could please help me solve a tricky issue?
Before rooting, phone worked fine. Brand new Moto 5G Plus activated on Sprint network.
After rooting my G5 Plus with a custom rom (Dirty Unicorns), everything worked fine except I lost my LTE signal (Sprint). The phone functions in all other capacities (calls, SMS, wifi). To be clear, the phone is receiving a Sprint signal, but no data LTE/3G is passing through. Phone calls and SMS are fine.
When I go to Settings-Network & Internet-Mobile Network-Advanced-Carrier Settings, I get an error-- "com.android.phone has stopped."
I decided to test with another reliable custom rom so I installed LineageOS 15.1. Same exact problem-- no data, and carrier settings brings up ""com.android.phone has stopped."
Any ideas? I've googled myself to death and I've not found anything that has worked.
Thanks in advance, everyone.
Click to expand...
Click to collapse
A similar thing happened to me. I was rooted with a custom rom(Pixel Experience) but I switched carriers to Boost Mobile and now I have no data and com.android.phone crashes when I try to open carrier settings.
I have an SM-N900V (Note 3, Verizon variant, hltevzw).
Detailed timeline:
- I flashed it back to firmware OB6 using Odin 3.09.
- I rooted it using ArabicToolApp.
- I used this tool to unlock the bootloader
- I installed a build of LineageOS 14.1 for hlte
- It didn't recognize the SIM so I did a dirty flash of this build of LineageOS 15.1 for hltetmo on top (hltetmo actually has different hardware than hlte, and the correct one for SM-N900V)
- Messed around with the APNs until it recognized and connected to Verizon's network. I DO have functioning SMS and LTE data, but I have not tested phone calls yet
- Messed around some with SuperSU in system- and systemless-mode. Bricked my device more times than I could count, then unbricked over and over using SuperSU's impeccable installer. Messed around with this quite a bit
- Also messed around with Xposed some. The OS is too unstable to run Xposed Installer correctly, so I uninstalled it
- Removed SuperSU, installed Magisk. Phone now passes SafetyNet
So, my phone now runs 8.1 and a Lineage build from 9 days ago. Cool. But, if I was satisfied I wouldn't be making this post. There are multiple instances of the same kind of "app freeze" - App screen freezes, sometimes it'll go completely black. Interactivity doesn't work, obviously, the app is completely frozen. Hold Back to kill doesn't work (Application Killed toast shows, but nothing happens). ANR (when it comes up) Close doesn't work. Home button works and brings me away from the app, but it's still there. Swipe away in Overview doesn't actually kill the app. Even in App Info, Force Stop doesn't work. The app is forever frozen. Tapping the icon from the launcher no longer does anything, it doesn't even bring up the app. The app is permanently crashed and inaccessible until a reboot.
Issues:
- Sometimes when booting the phone will not recognize the SIM until a reboot. As in, "No SIM" message and everything
- Sometimes it will get stuck at boot, I have foxy-boot installed, so I can see the logs. I don't remember what it was all about, if it comes up again I'll update the post
- Google Chrome sometimes crashes when trying to download a file. I've gotten my phone to self-host before, but this issue always seems to come back, and when it does Google Chrome ALWAYS crashes when trying to download a file. App Freeze
- Netflix installs and logs in but freezes at the "can't connect to service (-9)" message. App Freeze
- Certain apps like NativeScript Playground get stuck at the splash screen. App Freeze
- Xposed Installer did this when opening the Settings, whether Xposed was installed or not. App Freeze
- F-Droid also sometimes crashes, although it's somewhat arbitrary, I can't reproduce it reliably. App Freeze
I have tried reflashing the ROM, flashing Xposed uninstaller, reinstalling Magisk, none of it seems to work. I have TWRP 3.3.0 so I can do pretty much anything that doesn't involve the SD card (the SD card is probably broken in hardware, it's so read-only that Android and TWRP both can't write to it at all, but they can both read the same half-broken filesystem).
I fear that this OS is just too unstable for the phone and there's nothing I can do. I sincerely hope this is not the case.
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
terminator911 said:
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
Click to expand...
Click to collapse
I did a clean installation of RR 6.0.0 (Android 8.1) and it works a lot better than LineageOS did, with even more configuration options. I really really hate Pie and its gesture-based gimmicks (Screw you Google for copying more of Apple's bad design decisions), so I assumed Oreo would be more stable, but the ROM I installed still has crashing apps. Google Chrome still won't download most things (I've gotten it to download before), trying to change the accent color crashes the 'LineageOS Settings' app, and F-Droid is seriously messed up, but most other things are stable, including the Verizon network which required no pesky APN setup.
I'm on the OB6 bootloader/modem, is that a problem? I doubt that would be an issue, but I can always back up and reflash via Odin. The cool thing is that I installed a patch to TWRP which backs up /data/media along with everything else, after installing the custom ROM. So, really, I can do anything and be perfectly fine. There's, AFAIK, no way to ruin the phone unless something exploits the eMMC brick bug.
If there's another ROM you'd recommend me install, I'd be happy to try it out. I would really like to have a stable OS on here, where Chrome will work and download files. I'd also love Camera2 API since the phone has the chip for it (Snapdragon 800), but none of the ROMs I have support it and there's been no discussion online other than some years-old threads with no answers. I know there have been some articles online listing Note 3 as a phone that'd support Camera2 API with a software update. Would updating the bootloader/modem do anything on that front?
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
terminator911 said:
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
Click to expand...
Click to collapse
Excuse me but custom ROMs don't have "the Samsung Internet browser". Additionally the modem shouldn't cause app crashes (if it does, correct me please).
I might try the Nougat ROM. Bluetooth calls don't matter to me, but stability does. I just kinda really like Oreo and all its customization options but it may be too new for this old phone from 2013. It still works as a phone though, Messages and phone calls work fine, so I may just deal with it.
I use Open Camera, and I've tried multiple Camera2 API enablers. The phone has a Qualcomm Snapdragon 800 and the necessary links (in hardware, between the camera/other things) to support Camera2, but nobody seems to have tried it. Probably because the Verizon Note 3 is really locked down, and can only be rooted on a special version of the samsung ROM, and can only be bootloader-unlocked via the eMMC brick bug... There are Magisk modules for Camera2 on Exynos-based devices, but none for the Verizon Note 3 AFAIK.
I just found out that RR 7 officially supports `hltetmo`, but RR 6 doesn't. That's kinda sad, I hate Pie, but I might try it...
I've had the SEPL stuff before, that's the one that can't be rooted. I suppose I didn't consider upgrading again after I unlocked my bootloader. I'll try SEPL1 firmware again, but with a custom ROM...
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
terminator911 said:
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
Click to expand...
Click to collapse
Yeah but, data and calling worked fine on the LineageOS and RR roms, so there's no reason to update the modem.
Besides, I flashed SEPL1 6 times using Odin (multiple times by flashing, rebooting directly into download mode and flashing it once more) and it doesn't want to update. Still on OB6. On the latest (official Pie) RR rom, data worked on first boot but doesn't work anymore (I'm going to mess around with the data settings until it works), but I have no reason to believe that my phone needs a modem update to function.
I did, many times, make calls to various phone numbers and they all worked flawlessly. SEPL1 is therefore not needed if that's all it does.
And I do know about all the Resurrection Remix versions: One is Nougat from their archive, one is the Oreo version I had installed just yesterday before flashing Pie, and the other one is Pie which is now officially supported.
I am currently working on getting RR7 to work, it's only crashed a few times, and I don't even remember what those times were (I think it was using the Back button in Overview/Recents at the same time as the Overview button?)
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
terminator911 said:
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
Click to expand...
Click to collapse
"pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot"
So...
- Reboot phone into Download mode
- Pull battery while in Download mode
- Flash thingy
- Reboot back into Download mode
- Flash thingy again
? That will be very difficult to do with my dodgy charging cable that doesn't like being repositioned...
I do that without pulling the battery, but I could try it with.
I'm downloading the full SEPL stock image to flash. Once that's done, I'll flash it, reflash TWRP, restore my backup, and see if the baseband has updated.
And no, never dirty flashed the ROM. Always completely wiped data, system, cache and everything. I always backup first. I currently have 3 backups: Lineage OS (before installing RR), RR6 (Oreo), and RR7 (right now before that stock image I'm going to flash).
My external SD card is nonfunctional and read-only with some trash files from the previous phone.
I flashed the stock SEPL ROM. Baseband still didn't change. Restored from backup, SIM now works. Network is detected, SMS and data both work reliably on all reboots.
I will mention that I did brick my phone by using Odin to erase the eMMC, but I fixed that from TWRP, and now everything works flawlessly. There are still some app crashes, but most things are very stable. Camera2 API still nonexistent, which is sad because I got used to it on my old phone, but I shouldn't hope for it.
Any Custom ROM without "no audio during call" bug in Asus Max Pro M1(3GB Ram variant)
Story: Installed LineageOS 4 months back, Had a good working mobile with latest build, & then I tried RR & AEX,
Resurrection OS & AEX latest builds had same "no audio during call" problem
Tried to restore but , facing the same problem in LineageOS too, I checked by installing all the available builds on website.
I checked speakers & mic via whatsapp call ,they working fine
Resurrection OS older builds (7.0.0s) don't have this problem but still they have lots of bugs & crash a lot.
I tried "build.prop" method didn't worked because there were no lines to change.
I tried installing "dolby plus oero patch" it wasn't getting installed via TWRP.
So basically this critical bug exists in every rom I'm trying. U know any rom which doesn't has this problem,
& I was thinking if anyone saved a twrp backup of most perfectly running device online for rescuing other devices later,
hi,
please see this thread
https://forum.xda-developers.com/asus-zenfone-max-pro-m1/help/call-sound-oreo-rom-t3848196
flash DoblyPlus with magisk not twrp.
after that you can restore to stock official roms for permanent fix audio without dobly