On every ROM i am trying since installing xiaomi.EU (been on corvus OS and aospa extended) "OK google" is noto working andò trying to neable it crashes the google app, what can i do?
Do you run a different launcher like Nova Launcher?
Nothing, wait till google fix it
I fixed by flashing firmware with Xiaomi tool and now it works on custom ROMs
Related
Guys, I really need your help as my phone was stolen last week and I got a Xiaomi 5X as my only phone now. The things is I've tried all the different Google installers and none of them work, it's stuck at "checking info" when launching Google Play. What can I do? There's no global rom for 5X
Android V. 7.1.2 N2G47H
MIUI V. 8.5 Stable 8.5.15.0(NDBCNED)
I've manage to successfully install Google apps with this LINK .
Only problem was with Google Maps, search manually for APK and install it!
Hi everyone. I have been doing tons of research because I cannot enable voice activation ("OK Google") but there are so many different versions of rom it's hard to know what's working!
I bought the phone from AliExpress so it is the Chinese hardware but it came with the Global rom and unlocked bootloader.
I updated OTA twice to 10.3.1 Global but Google pay wasn't working so I researched Xiaomi.EU.
I installed TWRP and Xiaomi.EU rom STABLE 10.2.3 and I was able to use Google Pay but now turning on Google Assistant voice activation won't work. It has a problem where the option is not greyed out but if I tap it it instantly switches back (Picture below)
Like I said I have done tons of research but I can't seem to find a correct answer so if anyone knows a real solution for this version of rom please let me know! Is this feature even possible or not at all? Some seem to have it working...
Specs again:
Chinese hardware
Unlocked bootloader
Xiaomi.EU rom STABLE 10.2.3.0
No root or Magisk
SafetyNet passed
Thank you so much!
Hey
I used Havoc's ROM.
'Ok Google' works.
NFC Payment works with my Homebank, not with Google Pay.
Goalach said:
Hey
I used Havoc's ROM.
'Ok Google' works.
NFC Payment works with my Homebank, not with Google Pay.
Click to expand...
Click to collapse
Thank you. Well at least I know it will work with a AOSP rom but I want to try to use Xiaomi.eu first because it's based on original MIUI and so should be really stable.
Anyone tested Android Auto with Lineage-16.0 (or other ROM 9.0.0)?
I have problem on Redmi 4a with permissions - when it asks about permission to draw on another apps, after I accept that it still wants this, can't continue setup.
Same thing with others ROM 9.0.0 as Havoc-OS-v2.5 ,AospExtended V6.2, SuperiorOS-Nemesis....
Android Auto works perfectly with original MIUI 10 (android 7.1), what could it be? (selinux, opengapps, vendor partition...)
rq: no answer in Android auto forum !
Thx for solution
Same problem for me, I'm on nougat Resurrection ROM right now because I need Android Auto for my daily route. It's a strange bug related to some permission.
Hi, some time ago I used the Evolution x as a custom rom and I had the google camera of parrot043 which worked well, it was simple and there wasn't much need to configure anything.
I update the ROM, I reinstall the Google Camera and it doesn't work.
So I decide to use the Lineage Os (unofficial) and the google camera still doesn't work and crashes on startup.
I have Cam2API enabled and I have them at LEVEL_3.
The error that comes up is this:
Code:
Camera crashed java.lang.RuntimeException:
java.lang.NullPointerException: Cannot return null from a [email protected] @Provides method at Img.run(Unknown Source:26) at
java.util.concurrent.ThreadPoolExecutor.runWorker( ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.ru
I hope you have a solution and I hope you can help me, good day.
P.S: I use Stock ARM64 OpenGapps.
the last rom aosp that I tested in my mi9 was the crdroid a12 but after returning to the .eu 12.5.6 a11 the keyboard at the time of typing presents freezes which makes many words wrong in typing, I thought it may be some bug that gave because of the crdroid dai installed the pixel a10 and did not happen the bug more, then I went back again to 12.5.6 and the bug returned, you know how to fix this? when do I give format/yes it really removes all remnants of the previous rom?