Related
This problem is starting to get really annoying. Recently i did a clean flash of cataclysm with code blue kernel, and i remember even on stock lollipop on my other nexus 5, there were no gps issues. This is an RMA unit which i have had for a little over a month now and today i desperately needed GPS cause i was lost...literally.
With 4g and gps it couldnt find me...crap
I have done everything, booted in safe mode, tried calibrating gps, rebooting, reinstalling google maps, everything. Every gps fixing app knows my exact location within seconds of turning on gps. literally, i live out in the country where there aren't many obstacles to obstruct the gps, im in my basement with 2 floors on top of me and STILL those apps find my location no problem. But GOOGLE ****ing MAPS cant find me! Its specifically google maps, everything else uses gps just fine.
any ideas what on earth to do?
I called google and they just offered to replace it. And i desperately dont want to go through that hassle again.
EDIT:
What ive done so far
1. tried safe mode and safe mode recalibration
2. tried factory reset
3. tried reflashing rom and kernel
4. flashing kitkat modems
5. using gps fixing apps
fixed it.
in App Ops on cataclysm rom i enabled location for oogle play services.
It looks like the issue is in play services and not gps
russian392 said:
fixed it.
in App Ops on cataclysm rom i enabled location for oogle play services.
It looks like the issue is in play services and not gps
Click to expand...
Click to collapse
Hi, can you give me the procedure that you have follow?
I've the same problem
Edogolf said:
Hi, can you give me the procedure that you have follow?
I've the same problem
Click to expand...
Click to collapse
In my ROM, I have option to control each apps individual permissions. (I think you can get "app ops" with xposed. Its built into cataclysm ROM).
I simply went to 'android system' and 'google play services' and enabled location access.
russian392 said:
In my ROM, I have option to control each apps individual permissions. (I think you can get "app ops" with xposed. Its built into cataclysm ROM).
I simply went to 'android system' and 'google play services' and enabled location access.
Click to expand...
Click to collapse
Thanks for your reply, this afternoon I tryied to flash the original SW and hope that this operation can solve my problem...
I'm not an expert and I prefer to use the original ROM, however I've all the option for the geolocation access available and setting on "YES"
Edogolf said:
Thanks for your reply, this afternoon I tryied to flash the original SW and hope that this operation can solve my problem...
I'm not an expert and I prefer to use the original ROM, however I've all the option for the geolocation access available and setting on "YES"
Click to expand...
Click to collapse
Good luck
russian392 said:
Good luck
Click to expand...
Click to collapse
Nothing happend... I've flash my cell but google maps doesn't work fine
I'll try next week to call the LG service and hope to solve this problem. Otherwise I'll change my phone with another brand.
Edogolf said:
Nothing happend... I've flash my cell but google maps doesn't work fine
I'll try next week to call the LG service and hope to solve this problem. Otherwise I'll change my phone with another brand.
Click to expand...
Click to collapse
Idk google should replace it no questions asked. I'd call them first.
This seems very strange. my N5, stock and unrooted (5.01) battery was getting bad so I replaced it with a unit from ebay. It looked like a genuine OEM battery but I suspect it wasn't.
And despite all the videos on Youtube etc. saying you can prise the back off the N5 without breaking anything I managed to break two tabs
Anyway after I put it all back my first heartstopping moment was NFC had stopped working, both for charging and for communications. A quick Google search revealed that was because the back had not snapped on properly so the antenna in the back was not contacting the motherboard contacts properly. A quick press of the back the case, a click and all was well,
But now the phone won't do trusted face or locations which it did before. If I go to trusted face and choose improve face matching I receive an error Couldn't start finding your face. And now face unlock never works as well as trusted location (my home).
I can't believe a new battery would affect that but perhaps somebody in these forums might have some knowledge of this problem?
I will wait for 5.1 to see if it fixes the problem, else I guess I have to live with it.
Thanks
Sounds like maybe the front facing camera connection might have been disturbed during battery installation.
If it was me, I'd go into the camera app and see if the front facing camera is working properly.
If not, pull the back off again and check around the camera for anything loose. Verify your antenna connections.
Best of Luck
That one of the first things I tried and the camera is fine. Also GPS works fine so trusted location should work.
lchiu7 said:
That one of the first things I tried and the camera is fine. Also GPS works fine so trusted location should work.
Click to expand...
Click to collapse
As you mentioned, waiting for the 5.1 OTA is going the be the best option short of factory resetting and losing all your data.
Hopefully the OTA will fix it for you when it arrives to your device.
If you prefer not to wait on Google, you could Download the 5.1 OTA and ADB sideload it using the STOCK recovery.
Nexus 5 OTA Help-Desk
Looks like you would need to follow :
Scenario #1
You are completely stock. Unlocked or Locked bootloader. No root permissions.
Continue to Section A
Best of luck
The problem is not from your battery.
Trusted places and faces are broken after the last Google Play update on a number of Nexus devices after they added the "on-body detection."
Some users get it to work, some temporarily, but it is not an issue with your new battery. From the forums i read, some users (not Nexus 5 ) got it to work by turning smart lock off and on, re-doing your locations in google maps, side loading the Google Play Services apk, uninstalling the Google Play Services and reverting it to previous version (mine is grayed out.)
I notice huge battery drain coming from the Google Play Services then I disconnected the GPS and it was no longer draining. I am assuming it's having trouble or a bug where it's searching my location for the Trusted places and draining my battery. This is only an assumption though. Hopefully it will be fixed in a future update. I still have not found a fix for my N5 or N7 2013 yet.
Just so others are not put off ive changed my Battery with no issues and have taken the back off 6 times. No clips broke. It is important to make sure all clips are pushed home and you should gently press the back allover as there are a lot of connections on the back that need to make contacts with the board
joegestes said:
As you mentioned, waiting for the 5.1 OTA is going the be the best option short of factory resetting and losing all your data.
Hopefully the OTA will fix it for you when it arrives to your device.
If you prefer not to wait on Google, you could Download the 5.1 OTA and ADB sideload it using the STOCK recovery.
Nexus 5 OTA Help-Desk
Looks like you would need to follow :
Scenario #1
You are completely stock. Unlocked or Locked bootloader. No root permissions.
Continue to Section A
Best of luck
Click to expand...
Click to collapse
I got the OTA update for 5.1 and it's made no difference. Might have to look at some other solutions.
chrisinsocalif said:
The problem is not from your battery.
Trusted places and faces are broken after the last Google Play update on a number of Nexus devices after they added the "on-body detection."
Some users get it to work, some temporarily, but it is not an issue with your new battery. From the forums i read, some users (not Nexus 5 ) got it to work by turning smart lock off and on, re-doing your locations in google maps, side loading the Google Play Services apk, uninstalling the Google Play Services and reverting it to previous version (mine is grayed out.)
I notice huge battery drain coming from the Google Play Services then I disconnected the GPS and it was no longer draining. I am assuming it's having trouble or a bug where it's searching my location for the Trusted places and draining my battery. This is only an assumption though. Hopefully it will be fixed in a future update. I still have not found a fix for my N5 or N7 2013 yet.
Click to expand...
Click to collapse
Not sure if that applies to me. I had the problem after I replaced the battery (though it could be coincidental) but before 5.1 where I understand is when on-body detection was first implemented.
I managed to get trusted places to work by walking around my section and getting the phone to recognise a new location which is basically the same as my home but with a different name. That seems to work but I still cannot get face detection, either with unlock or improve matching.
I found the reason for my large battery drain, it was one of my weather apps refreshing through Google play Services. I also did a temp fix for Trust Places like the other user did. I added two places next to my house, close enough to all cross each other. That did the trick for now.
Here's what worked for me
I got a phone call when my Nexus 5 was locked and instantly Trusted Face crashed and gave me a force close message. Here's how I managed to fix it:
1) First, I removed the existing face data and turned off Trusted Face.
2) From Settings --> Apps --> All, I found Trusted Face and Cleared Cache, Data, Force Stopped the app and then disabled & enabled the app.
3) Rebooted the phone holding the power button (Not through the menu)
4) Turned on Trusted Face and registered my face.
5) Then I had coffee, but that's not relevant to the case.
Note: I know some of the above steps are unnecessary and repetitive, but nothing else worked for me.
Good Luck !
Thanks. I tried that and now Trusted Face is working again.
PHP:
lchiu7 said:
Thanks. I tried that and now Trusted Face is working again.
Click to expand...
Click to collapse
I'm glad it worked.
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.
Phone: Redmi Note 10 Pro Max, Poco X3 ProOS: Android 11, on MIUI 12.5 and MIUI 12
Issue:
When I pick Voice to be my default call redirecting app, it does not make calls.
The Phone app just stays stuck on dialing and never dials. Never rings on the other end either.
Sometimes, it causes the phone app to stop functioning altogether to the point that I have to restart the phone to regain functionality. I have sought help for the issue all over the internet and cannot seem to get any info on it.
I don't have an issue with going into Voice app itself and making the call over Wifi. It just will not redirect via the phone app, which was very convienient.
I believe it might be specific to Xiaomi phones, but then again, I used a Phone that uses Google Dialer, and it is the same result, albeit, it was also a Xiaomi phone with Global ROM containing Google apps as defaults.
I believe this to be an issue with Xiaomi ROMs. If I make the call from any other Android 11 ROM, the call works just fine.
Any assistance with this will be very helpful. Google Voice is my most used app on my phone.
No one else is having these issues? Or is it that people don't use Google Voice as much?
Given all permission it requires? Allow auto-start up? Is the phone you said working fine a Xiaomi phone with custom Rom Android 11?
If custom Rom works fine, then it's MIUI's problem.
If it's MIUI problem, ask in Xiaomi official forum or online customer support service.
If custom Rom still having issue, it might be Google Voice issue. Either hardware or software issue.
I have given it all the permissions it needs. And I do believe it might be a Xiaomi thing because I have installed other phone apps and they too can't work. I've posted the issue in Xiaomi forums.
I was hoping other people might be facing the same issue and could help with solutions
Try turn off MIUI optimization in developer menu and see if it works.
Maybe also try this
https://www.reddit.com/r/Xiaomi/comments/bqasnd
MIUI optimization is nowhere to be found in this ROM. I am looking to see how I can disable it otherwise.
Damionix said:
MIUI optimization is nowhere to be found in this ROM. I am looking to see how I can disable it otherwise.
Click to expand...
Click to collapse
Go into developer setting, scroll down to the botton, press the reset to default setting multiple times. Then the MIUI optimization should show up.
I saw that, and tried it several times but it would not appear.
Damionix said:
I saw that, and tried it several times but it would not appear.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...eming-turn-on-miui-optimization-gone.4254555/
pl1992aw said:
https://forum.xda-developers.com/t/...eming-turn-on-miui-optimization-gone.4254555/
Click to expand...
Click to collapse
Thanks. That made it show up. I tried the call with optimization off, same thing. Optimization on, and still the same thing. I think it's a problem with Miui itself. Something in Miui is blocking voice from making calls when it's being redirected.
Hi, All
So, I'm trying to run custom ROMs as I want to set my HID_DEV_MTU_SIZE to 512 for amiibos, but every time I boot up the phone or manually turn Bluetooth on, it just says "turning on" and then turns itself off again, then back on, then off, then back on, then off... I can't get it to see any nearby bluetooth devices and the about section doesn't even show a Bluetooth address. It isn't an issue when I have stock OTA Android 10 installed, though...
I've reinstalled both Lineage 17 and Bliss more times than I can count, tried adding qcom.bluetooth.soc=smd to build.prop, disabling A2DP hardware offload; nothing works.
I've done a logcat several times, and it always comes up with bluetooth has died, not sure if that's of any help, though.
I know there have been other threads about this, but none of the solutions on those have helped, so apologies for starting another one.
I'm really lost at this point, any input would be greatly appreciated!
Thanks!!
Update: I installed Pixel experience and bluetooth works fine on there!
trainingtoothpaste said:
Update: I installed Pixel experience and bluetooth works fine on there!
Click to expand...
Click to collapse
Well i have in installed and its still troubleshooting... My device is Huawei p20 lite and Pixel Experience v13 installed