Definitely! This ROM is working great, and I love it, no question.
But I think there is a good reason why many devs do not accept/ignore a bug report when you use a custom kernel or mods like xposed.
I suffer from lack of impulse control and after reading through a few pages of comments I couldn't help myself.
XDI suffer from lack of impulse control and after reading through a few pages of comments I couldn't help myself.
You're using the one on the first page?I'm getting a signature validation failure with gapps. I've tried downloading it twice and gotten the same thing both times. Anyone else? I'm going to try downloading an older version.
so the google camera app is crashing for me. Anyone else with that problem? It crashes right after load.
so the google camera app is crashing for me. Anyone else with that problem? It crashes right after load.
Is there another place to download it if I can't get this one to work. I guess downloading from the gapps site just won't work. Also, I don't understand why the one from here isn't working. It can't be a bad download. I tried it twice.
....anyway. I'm a hairs breath away from going back to stock and just loading up xposed to get the primary features I want.
Did you reboot recovery before flashing the GApps in the OP? Did you flash vendor after you flashed GApps? There's several things that can go wrong if you don't follow the flashing instructions precisely
Flash RomYep. Pixel XL Verizon variant that I unlocked with the recent workaround.
When I bypassed the zip check I got a failed boot. I ended up downloading one from the gapps site.
Try downloading camera app from playstore.Yes to both. I followed the instructions to a T. Multiple times LOL!
The only problem I was getting is a zip validation failure with GAPPS. I downloaded it a second time and got the same thing. I then tried unchecking zip validation and went through the process. At that point, I got a failed boot. It tried twice and then went right back to twrp. I even tried the whole process with zip validation turned off a second time and it did the same thing.
Finally, I downloaded gapps from opengapps.org. I selected arm64, 8.1, and nano. It seemed to work, but now I'm getting camera errors and that is apparently the cause.
Try downloading camera app from playstore.
https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera
Sent from my Pixel using Tapatalk
@General_Tso
Here are the exact things that I did to get WiFi calling to work again:
1. Open phone app.
2. In the dialer, type *#*#4636#*#*
3. Go to "phone information".
4. Toggle "volte provisioned", "video call provisioned", and "WiFi calling provisioned". I don't remember if any are greyed out. If WiFi calling provisioned is greyed out, try just toggling volte and video call provisioned.
5. Go back to the previous screen. Wait a minute or two. Now check the phone information tab again. If you see volte and WiFi calling checked, you're good. Otherwise, try toggling them on again and go back and wait a minute. Sometimes it takes a while to trigger the provisioning.
6. Once volte and WiFi provisioning are toggled ON in that menu, go back to the phone app>3 dots>settings>calls. If you have a WiFi calling tab, you're good to go, and it's working. Check the emergency address information to verify that it can connect to the service.
That is what I did. I'm pretty sure the gapps are my issue. I'm just not sure why the ones I downloaded from here are working for everyone else and not me.
I haven't but i see it now. Looks like an easy fix. Just have to add a display state check for doze(ambient).Have you noticed the ambient display + long press power button for torch bug?
I haven't but i see it now. Looks like an easy fix. Just have to add a display state check for doze(ambient).
Currently, it looks like it's only checking if the screen is on. I'll try to get it fixed.
https://github.com/LineageOS/androi...d/server/policy/PhoneWindowManager.java#L1793