I was Googleing today, and was searching for Google Wallet for the HTC One XL. It never worked out,due to a few errors.
1. SMX is disabled
2. The secure elements in the NFC chip do no have the appropriate .libs for the Google Wallet .apk to work.
My question is this: has Jellybean/ Sense4+ changed anything? Especially with Newt's ROM, which is based of the Evo LTE. Any ideas, thoughts,or suggestions on getting this working?
I am wondering the same thing. I am on Viper XL 3.1.
I tried the APK directly off my Nexus 7 (so from the Play store) and was told my phone/carrier is not supported.
I then grabbed the current Modaco release and get the message setting up wallet this may take up to 5 minutes. After around 2-3 minutes it force closes.
Next I tried airplane mode + wifi only to be sure it wasn't an AT&T DNS thing. I was initially prompted to enable NFC (which I did earlier but it must of disabled itself at some point, and this is the first time Wallet had prompted me). Same thing, 2-3 minutes later got a force close.
Anyone have more info on if Wallet is able to be ran on the new JB releases?
Recently learned that Samsung no longer update Samsung Galaxy GT Y Young 5360. Custom Stock ROM UN-rooted is Android 2.3.6 so using the instructions on this site acquired Hyperion 8 build.02 base band S5360DXKJ1 which updated my Android device to version 4.01 so i was able to use the latest apps. however. 2 issues I have noticed and i was wondering if any developers could shed some light on how to fix.
1. wireless device keeps disconnecting after 2-3 hrs and it requires a reboot, yes defaults it goes offline when in standby mode and successfully reconnects when u log back in.. However if say Ur leave ya phone alone for some time say u go asleep. wake up check ya phone the wireless comes on then the icon vanishes and u have to reboot device to enable.
2. YouTube website and app base does nor load videos. something to do with Google play services this also effects snap chat, However Google plays serveries digital signed patch works on device. so why won't it support videos. Every time i run YouTube or snap chat app i get this error,' Some apps require Google play services which is not compatible with this device so this video cannot be played' But i have Google play services installed and the Google play store. Can you guys have a look at this run Hyperion 8 on the same model and do a few days test runs to see if u can perhaps release an update to resolve this problem. Thanks
Can anyone tell me why I'm experiencing these settings being grayed out on my phone? I've had Google assistant working fine before, but it hasn't been lately and this appears to be why. Language settings haven't changed since it was working before.
I have thé same trouble sincères thé Google voice match was updated
Same issue for me, in Italian language.
With the latest builds it's possible to turn the phone on with OK Google, but unlocking it doesn't work. Still asks for pin/fingerprint. Anyone see a solution for this?
Homestar1217 said:
Can anyone tell me why I'm experiencing these settings being grayed out on my phone? I've had Google assistant working fine before, but it hasn't been lately and this appears to be why. Language settings haven't changed since it was working before.
Click to expand...
Click to collapse
It's currently the same on all roms, it's working if you use a gsi
Flatric said:
It's currently the same on all roms, it's working if you use a gsi
Click to expand...
Click to collapse
Good to know I'm not alone!
You are not alone! This happened to me a few weeks back. All my searching leads to gapps verification, or shall I say use of gapps instead of built into system. This feature does work once again using gsi with Google apps pre-installed as well as pixel exp ROM, as they are verified there.
Sent from my Mi MIX 2S using Tapatalk
Hi,
Same problem here in french language.
Voice Match used to work last week. Activation by pressing home is not working too.
I have to launch the app by clicking it
I have solved with last update MIUI Global 10.0.9.0
duraaraa said:
With the latest builds it's possible to turn the phone on with OK Google, but unlocking it doesn't work. Still asks for pin/fingerprint. Anyone see a solution for this?
Click to expand...
Click to collapse
I am still having this problem.
Same here, it stopped working about a week ago. Tried everything: retraining model, changing language from “English (Ireland)” to “English (United Kingdom)”… nothing works. I have to press the button to activate the assistant. I'm using the Pixel Experience ROM by Psy_Man – amazing ROM BTW, super stable.
Which version of the Google app do you use? I installed the 8.65.6.21.arm64, and Voice Match works on it.
I am experiencing the same issue ever since I flashed AEX. Pixel Experience was working fine and no issue with assistant but after the problem appeared all ROMs stopped working. I am currently on MIUI global because it's so far the only ROM that has it working, but it still requires faceunlock/fingerprint to unlock the phone though it does wake up by saying OK Google.
I have not tried any GSI ROMs because I don't know if they are good enough as daily drivers but if anyone has a recommendation will definitely try it out.
jamesyuli said:
I have not tried any GSI ROMs because I don't know if they are good enough as daily drivers but if anyone has a recommendation will definitely try it out.
Click to expand...
Click to collapse
I tried out OctopusOS ROM GSI. Very stable, could be a daily. I used it for a few days. But I prefer to be able to use a true dark theme. Didn't have issues with Google hot words at all. A few tweaks and some magisk modules help it out.
https://forum.xda-developers.com/pr...led-device-development/9-0-octopusos-t3859233
I observe this behavior in all ROMs, except the pixel experience gsi, and variations of the official miui ROM, including the EU versions. I haven't tried other gsi ROMs, but the one I tried worked perfect, except for Bluetooth audio which didn't work at all, so it was not fit to be a daily driver for me.
1/2 - Trying OctopusOS Today! Installation was very frustrating and in the end the exact word of the guide here https://forum.xda-developers.com/xiaomi-mi-mix-2s/how-to/how-to-install-gsi-roms-pass-safetynet-t3814298 worked to get the rom booted (Doing the image install in TWRP did not work, but doing it over fastboot did). I'll report back on how it works. If this is a bust, I'll probably try Havoc next.
Update - So this is new. Bluetooth works! However it's one step forward, one step back again. voice match works from the home screen, but I do not have any options to re-train or delete voice match data, and while the option to enable access with voice match no longer says "not available in selected language", it is still greyed out and cannot be turned on. Updating google only adds "While Driving" to voice match menu, and it is turned on. very strange. I'll play with magisk a little and then try havok.
Voice Match is working again in latest AOSIP
Flatric said:
Voice Match is working again in latest AOSIP
Click to expand...
Click to collapse
There's also a changelog entry for PE that hotword enrollment was fixed! More stuff to try!
Let us know if it stays. Everytime I've flashed and setup as new, it worked fine for a few days, but then would just stop, and grey out like above. So far doesn't matter what version I'm using, and none of the fixes anywhere work.
Sent from my Mi MIX 2S using Tapatalk
noobtoob said:
Let us know if it stays. Everytime I've flashed and setup as new, it worked fine for a few days, but then would just stop, and grey out like above. So far doesn't matter what version I'm using, and none of the fixes anywhere work.
Sent from my Mi MIX 2S using Tapatalk
Click to expand...
Click to collapse
almost 24 hours so far on the 12/30 build of Pixel Experience with no issues. The rom just runs flawlessly, and I love the pixel live wallpapers. OK Google still working with none of the voice options greyed out. Android wear device working too (Explorist 4). Auto bright, and lock/unlock good too. Battery seems good so far. These points aren't relevant, but everything else seems to work good.
I know Pixel experience is not very dense on details for install so here's my process.
Use MiFlash to flash fastboot version of latest developer rom
Re-flash TWRP, enter wipe menu and wipe (Not format, NOT the one you have to type y-e-s) the first four options, Dalvik, Cache, System, and Data.
Flash your rom
Boot! (Regardless of whether or not it makes a difference, I like to let it sit on the first screen for a little, and then after 2-5 mins, I'll restart, before setting it up)
Oh! And I've had less issues since I installed MIUI, went into settings, and Signed out of my Mi Account. Not sure if it makes a difference, but I no longer have to "authenticate" and unlock after I install MIUI. This confused me because I read that unlocking BL automatically disables find my phone, but evidently not.
---------- Post added at 10:41 AM ---------- Previous post was at 10:39 AM ----------
Gopena said:
I observe this behavior in all ROMs, except the pixel experience gsi, and variations of the official miui ROM, including the EU versions. I haven't tried other gsi ROMs, but the one I tried worked perfect, except for Bluetooth audio which didn't work at all, so it was not fit to be a daily driver for me.
1/2 - Trying OctopusOS Today! Installation was very frustrating and in the end the exact word of the guide here https://forum.xda-developers.com/xiaomi-mi-mix-2s/how-to/how-to-install-gsi-roms-pass-safetynet-t3814298 worked to get the rom booted (Doing the image install in TWRP did not work, but doing it over fastboot did). I'll report back on how it works. If this is a bust, I'll probably try Havoc next.
Update - So this is new. Bluetooth works! However it's one step forward, one step back again. voice match works from the home screen, but I do not have any options to re-train or delete voice match data, and while the option to enable access with voice match no longer says "not available in selected language", it is still greyed out and cannot be turned on. Updating google only adds "While Driving" to voice match menu, and it is turned on. very strange. I'll play with magisk a little and then try havoc.
Click to expand...
Click to collapse
1/3 Didn't post this yesterday, I tried Havoc as well and it behaved like miui, no OK Google to wake & Unlock, but ok google from lockscreen brought up the pin pad, and unlocking with pin or FP would allow google assistant to activate. Havoc also had no bluetooth audio.
I noticed recently that "Ok Google" voice activation of the Assistant was no longer working. It took me a long time to notice because I only use this feature when driving longer distances, something I haven't been doing much during the pandemic.
With the newer versions if I say "Ok Google" or "Hey Google" there is no response. If I manually launch the Assistant ie long press on Home button it comes up and I can press the microphone and it works. If I try to retrain the voice model it tells me it's having issues connecting, and I cannot get past this message. It's clearly not a connectivity issue because I can use other Google apps and surf the web just fine.
I was curious when this had stopped working so I did some testing:
10.97.8.21 original version that came with the OS update, working
11.19.12.21 working
11.19.17.21 working
11.21.9.21 not working
11.27.6.21 not working
11.30.12.21 not working
11.39.7.23 not working
11.43.8.23 not working
12.2.11.23 not working
12.6.8.23 not working
12.10.7.23 not working
Obviously I didn't test every single version available but it seems that it broke between 11.19.x.x and 11.21.x.x. I was not able to find a good 11.20.x.x to download and test, so I can't rule that version out.
For now I've reverted to 11.19.17.21 but I'm concerned about security running that old of a version.
Any idea what might have changed in between those two versions to make this stop working?
Anyone else have similar experiences?
So.. I have this problem where (wait for it...) "Hey Google" doesn't respond, BUT (before you stop reading) it only stops responding after I've been on a voice call. Weird, eh?
Here are some fun facts:
1. To get it to respond again, all I have to do is manually open and close Google Assistant by tapping on the screen, then "Hey Google" will generally behave itself and respond until I get another voice call. Sounds easy (I even have a Tasker routine to automate the process), but it's still a chore and it's always a bit hit and miss.
2. I've tried every generic solution I can find on the internet, including retraining the voice model, deleting the cache and data, factory reset etc etc...
3. This issue is 100% specific to the OnePlus 8T running Android 13 (F.13, F.15 & F.62). I used MSM tool to go back to Android 11 and "Hey Google" worked like a charm. I took the OTA updates to Android 12, still working fine. As soon as I took the OTA update to Android 13 (guess what?) yep, the problem came back! No other apps were installed, only the apps built in to the stock ROM.
4. I've tried a number of custom ROMs. All Android 13 ROMs I've tried have this same problem. (Android 12 based ROMs not affected.) I've also tried EU, Global and Indian Firmware.
I sent feedback to OnePlus already, so hopefully we'll get a fix. In the meantime, please, if anyone has a workaround please let me know.
If you don't have a solution but want to complain about the problem here, I'll give you a listening ear.
706mix said:
So.. I have this problem where (wait for it...) "Hey Google" doesn't respond, BUT (before you stop reading) it only stops responding after I've been on a voice call. Weird, eh?
Here are some fun facts:
1. To get it to respond again, all I have to do is manually open and close Google Assistant by tapping on the screen, then "Hey Google" will generally behave itself and respond until I get another voice call. Sounds easy (I even have a Tasker routine to automate the process), but it's still a chore and it's always a bit hit and miss.
If you don't have a solution but want to complain about the problem here, I'll give you a listening ear.
Click to expand...
Click to collapse
Maybe the process of Google Assistant is killed in background by stock memory cleaner or some app?
Try whitelisting it (disable memory optimization and so on).
Rootk1t said:
Maybe the process of Google Assistant is killed in background by stock memory cleaner or some app?
Try whitelisting it (disable memory optimization and so on).
Click to expand...
Click to collapse
Thanks for the suggestion. The Google app is already set to 'Unrestricted' - are there any other processes/apps that should also be set to 'Unrestricted'?
I'm wondering if the Qualcomm Voice Assist Aqstic Audio Codec is not being implemented properly in Android 13.
So, I finally received a reply from OnePlus Support. They have asked me to send a screen recording of me saying "Hey Google" and the phone not responding. Sounds fair. I'll have to go back to stock OOS13 so they can see that the issue is not just with custom ROMs.
Oh well, guess I'll get round to that when I have a spare day...
(At least we can do a nandroid backup with TWRP these days. )
Please, if anyone is running an Android 13 ROM (stock or custom) on their 8T, please can you check if "Hey Google" is working properly on your device after making or receiving a call?
Please post on this thread whether it worked or not, and what ROM you are using. Thank you.
Here's a little update in case anyone's interested...
I sent OnePlus Support a screen recording of the malfunction. Today I received this reply:
I contact you due to the malfuntion of Google Assistant.
There is a need to solve this issue in the next update of Android. The version Android 13.1 will be pushed in June and please inform us if the issue still persists.
Best regards,
Klaudia
OnePlus customer service
Click to expand...
Click to collapse