You can enable the icons from the SettingsExtra app.hello, i installed the rom and everything seems to work fine. But I was used to seeing if I had coverage for HD calls (VoLTE) and calls over WiFi (VoWiFi), which would show up on the bar; I haven't found a way to put it here. It can?
So, I installed the Google dialer and I cannot replicate the issue.how can I get the Aosp dialer back? there is no other dialer to choose in settings.
many thanks!So, I installed the Google dialer and I cannot replicate the issue.
Anyway, here the AOSP dialer apk:
![]()
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.www.androidfilehost.com
The only way would be to not uninstall the phone apk, but I think you should ask/confirm with the maintainer of the gapps about this.many thanks!
but can you see in my logcat that the dialer is constantly activating the display while receiving a call?
i have installed your aosp dialer, granted all permissions and set it as default phone app. but when i press phone/settings/display options or other some setting options the app stopps. is there anything else i need to do to get the aosp phone app fully working?
hmm, is it possible to re-install rom and gapps without wiping data (apps and settings)? i assume that i'm not the only one with this problem.The only way would be to not uninstall the phone apk, but I think you should ask/confirm with the maintainer of the gapps about this.
There is probably a way to flash the gapps without removing the stock phone apk.
If you enter TWRP, you can just flash (in order) the ROM zip and the Gapps zip without wiping data. You will keep everything installed this way (app, data, settings, everything). Of course, if you flash the same gapps, you will probably lose the AOSP dailer again.hmm, is it possible to re-install rom and gapps without wiping data (apps and settings)? i assume that i'm not the only one with this problem.
i freezed the google dialer with titanium backup and made the aosp dialer to a system app. but the problem is still there. can you see it in the logcat? https://ctxt.io/2/AAAQQLFWEw
the only thing i want to change is to have surnames first and display order by surname. thank you in advance!
i got an answer from an nikgapps developer. he says: "the log does not reflect any exceptions due to gapps. try searching for exception or gms in the logs."If you enter TWRP, you can just flash (in order) the ROM zip and the Gapps zip without wiping data. You will keep everything installed this way (app, data, settings, everything). Of course, if you flash the same gapps, you will probably lose the AOSP dailer again.
The issue with the AOSP dialer is that I sent you the apk but it would need also the odev/vdex file to (probably) work correctly. That would require rooting the device, and you will lose it at every update...
I suggest to ask in the Nigapps thread/telegram group if anyone else has the same issue first, to see if they can fix it.
I cannot access the log anymore (https://ctxt.io/2/AAAQ8NJEEA), but yes there was no exception. The dialer app was just turning the screen ON all the time, for smoe reason.i got an answer from an nikgapps developer. he says: "the log does not reflect any exceptions due to gapps. try searching for exception or gms in the logs."
i don't know what to do with this answer?
here is a new link: https://ctxt.io/2/AAAQqBD7EQI cannot access the log anymore (https://ctxt.io/2/AAAQ8NJEEA), but yes there was no exception. The dialer app was just turning the screen ON all the time, for smoe reason.
The issue is:
thank you again for your answer.The issue is:
DialerLegacyInCallActivityPeer: com.android.incallui.LegacyInCallActivityPeer.onNewIntent:1095 Restarting LegacyInCallActivity to force screen on.
It's not clear why DialerLegacyInCallActivityPeer is keeping the screen on to me.
I'm now able to replicate the issue. I'm looking into this.thank you again for your answer.
it seems that nikhil doesn't know what's causing this issue too. but he means that it is not gapps related. i dont know... he told me to set google dialer in the nikgapps config file (within the flashable zip file) to "2" (# NikGapps installer recognizes 3 config values # -> 0 (Skip the package) # -> 1 (install the package and delete corresponding aosp app = standard) # -> 2 (install the package and do not delete corresponding aosp app)).
i tried to set the google dialer to both 0 and 2. but in both cases the issue with the crashing aosp dialer is still present. flashing order is: rom, gapps, magisk. when it is done, wipe dalvik/cache.
here is the log from the crashing aosp dialer: https://ctxt.io/2/AAAQzLIHEQ
There is an issue with the AOSP Dialer, I've included a fix for it. It will be included also in the next OS release.
It is in the SettingsExtra app, but at the moment charging LED is enabled anyway and there is no option to disable it.where can i find the custom led manager? i want to deactivate the charging led.
i see the led manager in the settings extra app. but what does it change if I enable it? nothing to customize notification led?
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it!
*/