I ve been using the latest update (13/9) for 1 hour ish since my last charge, my battery dont move from 100%. What the hell is going on? What kind of witchcraft is this?
I install full gapps and i have this same problem with android auto, car detect phone but when i start configure car think is phone disconectedNikGApps stock doesn't include android auto. Use FULL or NikGapps-Addon.
Are you using the recomended firmware?, i was experiencing same issue and flashing the FW 13.0.3.0 posted here solved all problems.Does anyone have an idea why I might be losing sound system wide? After the boot its there for like 10 seconds, and then NO SOUND whatsoever - no dial pad tones, no media, no ringtone (i hear the dialtone when I call someone and hear them via the earphone, but thats the only sound I can get out of the phone since the last update) ?
no. but is that a thing? Im interested to know
As the fast charge goes to 33w it could be limited to less, maybe not everyone needs it and this way the battery is protected.
If you are into that kind of thing, I read that Advanced Charging Controller has a feature to limit charging current. Note that I do not use such Magisk module.As the fast charge goes to 33w it could be limited to less, maybe not everyone needs it and this way the battery is protected.
As the unit recognizes the original cable you can reduce the charging level by using not the original cable. I mean the original charger but another good cable. With original charger and original cable the unit is loading at about 5A, with original charger and not the original cable it is loading at 3A which is one point to extend the lifespan of your battery!As the fast charge goes to 33w it could be limited to less, maybe not everyone needs it and this way the battery is protected.
i got this too and i was on lineageos with some hacks to get it to work and now tried the fork version and it still wont work.Today Google Pay displayed notification on my phone, that contactless payments will no longer work on this phone, because this device is not certified bla bla (they have the info here) Did anyone else have this? I have not yet tried to pay anywhere to see if it actually blocks payments, but this is an important feature for me to have Google Pay working... should I be worried? It worked flawlessly so far... anyone experiencing issues with contactless payments on an unlocked phone with custom rom? I checked in Google Play settings and under Play Protect it says that my device is certified... so... strange.
I heard that there is a high possibility that Google is pushing in stages the requirement of Hardware-Backed attestation for Google Pay. There is a whole discussion about this on another thread on XDA (need to search). Last time i read through the thread, the situation was unclear because some can still use and some not (with no workarounds).i got this too and i was on lineageos with some hacks to get it to work and now tried the fork version and it still wont work.
some new security checks i havent found any info on how to bypass yet
Settings → System → Updater
Today Google Pay displayed notification on my phone, that contactless payments will no longer work on this phone, because this device is not certified bla bla (they have the info here) Did anyone else have this? I have not yet tried to pay anywhere to see if it actually blocks payments, but this is an important feature for me to have Google Pay working... should I be worried? It worked flawlessly so far... anyone experiencing issues with contactless payments on an unlocked phone with custom rom? I checked in Google Play settings and under Play Protect it says that my device is certified... so... strange.
a link would be nice,but ill try searching for it myself.I heard that there is a high possibility that Google is pushing in stages the requirement of Hardware-Backed attestation for Google Pay. There is a whole discussion about this on another thread on XDA (need to search). Last time i read through the thread, the situation was unclear because some can still use and some not (with no workarounds).
Alas, my post may just be speculation. I recommend you hop into the relevant discussion so that you can find a solution. I don't use GPay however because banks in my country do not support it.
Here's the linka link would be nice,but ill try searching for it myself.
on lineage os i was rooted to get it to work,on the fork i tried today that passes safetynet by default i wasnt rooted and still it didnt work.
now im on pixel experiance plus and it seems to work again.i have not rooted yet on this rom
thanks.Here's the link
![]()
[Discussion] Google Pay Magisk Discussion Thread
This thread is inspired by the PoGo Magisk discussion thread. It's meant to keep the clutter of "Google Pay doesn't work" posts out of the main Magisk threads. Please use this to discuss issues with Google Pay and possible solutions. There's a...forum.xda-developers.com
@Bitoholic you might want to bookmark this should GPay stop working for you
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned