Originally Posted by hassanh403
thank you.It becomes impossible to receive a call or dial a call. Please fix it asap!
Set Google Phone to Default
At the end of the install in TWRP it displays..
- Installation complete!
You installed Google Dialer.
Please set it as default Phone
application to prevent calls
from rebooting your device.
Not the most accurate message, since you may not be able to answer incoming calls either.
Under App info-> Phone app-> (Switches to Default apps) Phone app-> select Phone (The Google version) as default.
Double check the permissions, and under the Advanced section make sure Display over other apps
Originally Posted by DarkHeart Z
Ever since the last 23rd march update, can't see chrome anymore because it's not even installed even after getting selected. Would you please make sure it's fixed because can't do any web browsing due to having only dependence on chrome webview. Hope it's getting a quick fix.
Originally Posted by DarkHeart Z
Not even for android 7.1? My device is an android 7.1 supported device at most. No update since then.
But my device is an android 7.1 upmost supported device. It doesn't require split apks. Can' t they provide normal apk for old devices?
Originally Posted by Magendanz
Just to get a little more specific on this bug report...
I notice the problem was introduced during the downtime from 20200311 to 20200321. If you skip connecting to the Internet in the Setup Wizard, everything looks pretty normal except that Chrome is missing from the app list. (It's actually installed to system/app, but doesn't show in the launcher.) However, if you attempt to use the Setup Wizard to connect and sign into Google, the screen goes entirely black after the panel where you can opt to restore from a backup. If you attempt to hit the Back button from this black screen, you'll get a "Google Play services isn't responding" alert.
Looking at the version log (open_gapps-arm-9.0-stock-20200321.versionlog.txt), Chrome, WebView and GMS were all updated in this timeframe.
Only the arm builds?
Installing the full stock build or are you using a gapps-config file along with the stock build to modify the install?
Are you also installing Pixel Launcher?
Seems to cause odd errors. (Black screens in SetupWizard and odd UI reboots.)
What version of WebView is selected ?
Setting-> System-> Developer options-> WebView implementation
I had a little testing time these past few nights to try a few things.
Clean installs using the full opengapps-stock arm64 builds seem to work Android 7.1, 9 and 10.
lineage-14.1-20200217-UNOFFICIAL-flounder and open_gapps-arm64-7.1-stock on my Nexus 9 (WiFI).
[The unofficial 14.1 builds for Nexus 9 are by the official maintainer. Only unofficial due to LineageOS depreciating official builds of 14.1]
Everything seems to work fine. Trebuchet was removed and replaced with Pixel Launcher.
lineage-16.0-20190811-UNOFFICIAL-angler and open_gapps-arm64-9.0-stock on my Nexus 6P. [It's an old build, the last lineage 16 for angler.]
Trebuchet was not removed and Pixel Launcher FC when selected but, Trebuchet still works.
- Will try later (on a different device) to see if Pixel Launcher FC's on an updated/current version of Lineage 16.
lineage-16.0-20190926-UNOFFICIAL-hammerhead and open_gapps-arm-9.0-stock on my Nexus 5.
[I]Did not have enough space for the full Stock package. So I used a gapps-config file to install opengapps.
The chrome.apk was installed but not available. Chrome webview was not installed even though I installed chrome. The default ROM webview was still in place.
Nexus 5 old unofficial linage 14.1, had some issues with resizing the system image but, I was able to get it to work. Installed OpenGapps stock package and well..
No WebView or launcher installed (Active/Available). Just hanging out on Android is Starting... When I unlock the screen. I can access Settings from the status bar, no chrome or luncher are listed under Apps. Under Developer options, no WebView is available.
This post became way too long, so I truncated it a bit and will stop for now.
I'm still testing when I can and will try to narrow down my findings a little bit.
I will leave a line from my Nexus 5 logcat since it caught me off guard and made me laugh.
01-01 07:02:27.012 1680 1680 D FallbackHome: User unlocked but no home; let's hope someone enables one soon?
If anyone is interested.
Might be running down a bad path due to old rom or install error.
Nexus 5 logs gDrive