Not sure but that is probably a bug of the gapps. Consider (afaik), stable gapps for a11 are not here yet. Nothing i can do about, just wait for future releases. Btw, as soon as my NVME arrives, ill update and rebuild dsds correctly.
(coff coff infinite google photos backup too considering the app see it as a pixel coff coff )
This is XZ1, not XZ. I don't want to sound rude, but talking about another device in a XZ1 thread can make confusion (moreover, i have no idea how to answer about considering i know nothing about that device).
The May Release already available in Download section (second post). For the June one, im waiting the nvme to arrive and the PE team to update more things inside (no sense to release something...that have the same exact thing of the previous release). Probably 10-20 June build will be ready for single and dual. Thanks for patience.
It has plenty of horsepower, still a really good SoC and fast UFS.
No idea. Check and let us know
No. Forget it on Android 11, stock camera is not compatible.
? it lost nothing. I'm using it (at least, the september release that im going to post in some minutes) and says certified device.
Not possible, and not ...logical.
Going to post it in some minutes
No idea. Try with new september release
Curious. Search if some magisk module can fool this security system, probably yes, or to start just try with the september release.Days ago I wanted to pay in a store with the phone but I was surprised to see that the intended card wasn't ready for contactless payments although I've used days before. Forgot about until now... tried to initialize the card again and:
View attachment 5406971
I didn't even tried to install Magisk on this ROM!
Ah.. Maybe a month ago I've (so ways before last successful contactless payment) I've tried to login as root from adb, also I remember to try the TWRP's File Manager... It’s still certified in Playstore and Microsoft Intune says it's ok (Intune would always detect Magisk even if hidden).
It was my actions and Google got notice days after?
Or Google made a change since last week?
Did someone else have the same problem?