search

anestisb / android-prepare-vendor

Set of scripts to automate AOSP compatible vendor blobs generation from factory images
347 stars 156 forks source link

eSIM manager crashes on sargo #161

Closed scott-8 closed 5 years ago

scott-8 commented 5 years ago

eSIM manager constantly crashes when building with the full configuration on sargo. This does not affect normal SIM use, or the naked config.

Moved from https://github.com/PieDelivery/android-prepare-vendor/issues/1 for tracking.

anestisb commented 5 years ago

@PieDelivery can you paste relative crash logs from adb/serial?

Also can you give it a try with current head (noticed you missed some libs)?

scott-8 commented 5 years ago

Here's the entire log, in case you're interested in anything else (there are a couple of other random errors, not sure how important they are). If you scroll down to the bottom you can see eSIM Manager crashing (at around line 6300). This is without the changes you made, I'm rebuilding it with those changes but it'll take a few hours.

It looks like it might just be crashing because it can't find Google Play Services, in which case it might be better to just remove it.

05-22 01:20:17.866 5066 5066 E AndroidRuntime: java.lang.RuntimeException: Unable to create application com.google.android.euicc.EuiccGoogleApplication: java.lang.SecurityException: Failed to find provider com.google.android.gsf.gservices for user 0; expected to find a valid ContentProvider for this authority

logcat.txt

scott-8 commented 5 years ago

Flashed it with the changes, everything still seems to work, didn't seem to change anything with the eSIM, however. Here's the log, the errors are at the very end.

logcat2.txt

anestisb commented 5 years ago

Ok so the missing com.google.android.gsf.gservices content provider is actually a Google Service package. Therefore, the full image cannot be run if not bundled with GApps. I'm guessing you're trying the full config without them right?

scott-8 commented 5 years ago

Yes I'm tested the full image without GApps.

anestisb commented 5 years ago

Well it seems that the eSIM packages cannot work without GApps. At any case the full config is meant to be used with GApps so usually I test it under the context of having both. Have you tried installing GApps on the top (or bundle them with the main AOSP build)?

scott-8 commented 5 years ago

That makes a lot of sense, I didn't know it was assumed to be used with GApps. I installed microG to test. The crashing stopped, and I was able to get to the screen for scanning a QR code for an eSIM unlike before (I don't have an actual eSIM to test). I'll mark this as closed.