Database Info

Replaced battery in my N5 - now no trusted face or trusted locations

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.

Capacity for NFC full error

This pop up keeps appearing pretty much everytime I do anything on the phone...
Capacity for NFC services full. Not enough capacity to enable to service. Try disabling one or more services.
I tap change services and there is no service to disable and the capacity is 0%.
I don't use the NFC function and have never used it. I didn't even know what it was until this pop up problem started. Having Googled the problem, there seems to be a connection with banking apps but I don't have any.
This has happened ever since the most recent update a couple of days ago; it's either a massive coincidence or due to the update.
I have the 32.3.A.0.376 build, I've tried also software repair using Xperia companion but never solved the issue.
It's really starting to annoy me and I want to get it sorted. I've emailed customer service but no reply yet.
Any help at all would be massively appreciated.

S7 with custom rom(s) and Xposed - Internet connected apps breaking

Hi all, long lurking rom-installer who can self-fix most problems here. Got a problem I can't fix that's bothering me. Recently upgraded to an S7 so naturally rooted it on day one and been trying to get it my-kind-of-working fully ever since. I do like to bugger about with things in a vain attempt to shield some private data from some orgs and realise I'm in a particularly specific hole that I'll probably have to climb out of on my own, but if you don't ask...
Internet using apps pretend to work, sometimes for days, then just refuse to open. Screenshot example of the second and persistent error (after simply "Lightning has stopped" the first time) is attached.
Model: G930F
Current ROM: ambasadii 7.0 TW Nougat (here)
Xposed: 88.2
Root: Magisk
Significant mods:
1) use xPrivacy
2) disabled significant number of remaining packages using Package Disabler Pro (list attached)
3) run Orbot
4) run AFWall
5) modify app permissions in Settings/Apps to restrict where I think I safely can
6) run BackgroundRestrictor
The behaviour still emerges even if I don't apply 4), 5) or 6), it has started prior to me finishing my tweaking.
I know xPrivacy is not supported for Nougat but it seems to work ok for the most part with some retweaking of settings since moving from Marshmallow on my old phone. I understand it could be the cause of the problem but I'm wedded to (some of) my privacy enough to persevere before abandoning it. For the record I've checked the usage log for restrictions on any calls around e.g. internet that might be interfering but I've been unusually generous with permissions trying to fix this and there's no restrictions on any apps with internet access around that, or much else really at this point. I've also had a look in general usage log rather than app specific, looking for system components that may be working alongside the app and failing with a restriction but can't see anything being denied. Any system apps haven't been touched by me, I fetched what I could from xprivacy crowdsourced restrictions on the base ROM apps and then only applied my template to apps I've downloaded myself.
Some other background on the problem: everything will be set up as I like it - ROM installed, debloated, all the rest of above modding applied. It will be working super-fine. Nice and fast, little bloat left, just enough Google to get Play Store, apps installed and working, all will be and appear fine. After an undetermined & fluctuating length of time all of the internet-facing apps will suddenly not open. This includes but isn't limited to the Browser (stock and Lightning, Brave, Pale Moon, etc.), Twitter, Signal and the Official TWRP App.
Interestingly, internet-connecting apps that will connect on demand but don't seem to make a call on every app open (mostly due to prior settings changes) do not fail. They will still open fine and work fine, connecting when asked and not crashing. For example, K9 Mail and Pocket.
Another weird data-point: Signal will fail but will often do so later than the other internet-connected apps - possibly it has a token with GCM or something that when it expires will try to renew on app open which is when it starts to fail like the others?
The apps will work again if uninstalled and reinstalled but once the behaviour starts again, and it will, it will repeat. Sometimes twice or more in a day. So reinstalling every time is not going to make for a usable phone. It's like they have an error renewing their wifi lease or something.
It can take up to three days to begin - this build it worked fine for days whilst I was away and slowly, progressively building the system back up with regular TWRP backups. I can restore a TWRP backup from about 6 hours before the problem started and it'll work fine again, but still wait a random amount of time before the problem begins again.
I did think it may be something to do with the router here and home WiFi as it behaved much better whilst away and didn't break until my return, though that is likely coincidence. I'm in pattern-observing mindframe so false positives are everywhere. I thought it was connecting to the PC via USB that was doing it at one point.
Last data point: it's happened with a different base rom too (Decent here), same thing, but came on sooner each time. I would change the base rom again to see if it's something there but I suspect that should be one of the last things I try given it's happened across two roms now.
Anyway, if anyone has any insight on Nougat TW ROMs on an S7 with this kind of set up and/or any clues or ideas as to why internet connects would suddenly be crashing all these apps... I'd be grateful. Otherwise I have many reinstalls and possibilities to eliminate. Which means waiting many sets of days before I can repeat, which makes progress frustratingly slow when you depend on the phone (Signal particularly) to connect with people.

AFWall stands out if you're having problem with net connections to apps etc

Yes good point, thank you. I think i've run the ROM with same problems without any rules applied but I've disabled it fully now just to be sure. Much obliged.

If it persists, the proper way of troubleshooting would be to clean install the ROM only, no tweaks, Xposed, firewalls or anything, just the ROM and your apps you're having problems with
If that all works together fine, then add ONE new thing to the mix, test for a few days, rinse and repeat until you add something that causes the problem again
With testing for a few days between each new addition you're be 100% sure what is causing it once it starts again

Thank you! Yes that's the plan but I thought I'd ask first as there's a lot of waiting down that route. I did do it to a point during last build but only waited overnight after each phase. I think I'll start that.now. I can always restore this backup if the solution presents in the meantime.

Yea that's what I was thinking, backup this ROM, clean install, work out the issue, restore this ROM and fix it
Good luck

Thank you I'll report back if/when I work it out, for any other possible future readers.

I changed the base ROM & installed Xposed in a different way and rooted in a different way and tweaked Permissions to be more permissive and and and... I've read rovo89's farewell so I won't say "It's xprivacy" but it's definitely how xposed & xprivacy interact, whether by flashable zip or systemless magisk. It'll work fine for a good while but then starts corrupting everything internet connecting. Removing it removes the problem & restores the app functionality.
Sadly it's the same even if you restrict nothing in xprivacy & just leave it installed & switched on. I've had to remove it. Considering trying to go back to MM as I know it worked on my previous phone.

Phone functionality intermittently lost after upgrading to P

If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
I have no idea when calling functionality begins to be lost because I can still send and receive texts, but I can't make or receive calls. I don't even get a wave of missed calls or anything when it works after a reboot.
Google Assistant has it's own issues when this happens too. It won't come up with "Hey, Google" at all. When I long press the home button, Google Assistant comes up, but I just get the floating dots. Fortunately, it doesn't freeze when I try this. Restart the phone and I'm good for about 10 minutes or so. I tried installing 3rd party calling apps, but the problem persists.
Hoping this is a Pie issue and waiting for the next security patch, will likely do a sideload flash-all. Any suggestions as to what the problem is from? Could my SIM card be the problem? Any apps I could try to help narrow down the issue? I had no issues with Oreo.
Thanks in advance.

Tried rebooting in safe mode. Slightly similar results: works fine for about 10 minutes but then it's just the mic not working. I can make and receive calls with out the phone freezing, but no mic.

mbstone said:
If my phone is on for more than 10 minutes, I lose calling functionality. When I try to call someone, it freezes and the Pixel becomes unresponsive, forcing me to hold down power for 10 seconds for a reboot. After this, it works just fine for another 10 or so minutes.
Click to expand...
Click to collapse
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, with everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (a few days later, rarely get/make calls). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
After continued issues I parked phone in drawer a bit then pulled out and tinkered with a few weeks later. Tried to isolate problem using logcat and on a hunch I flashed TWRP and a custom ROM but NOT any gapps package. Sticking sim in and using the built in phone app (Resurrection Remix -com.android.dialer) it works without issue. What? I flashed gapps (correct version/etc) and sure enough the problem returned. Went back to rom minus gapps, works fine. So, with straight up stock rom - stock phone dialer fails, custom rom - it works without a gapps package but not with.

Aimless Rambler said:
I have a similar issue with a used Pixel I purchased. I couldn't place or receive calls, everything else working fine. Did the prerequisite online searches with results finding most everyone experiencing this issue chalking it up to hardware but I'm still thinking software. I tried a different phone app (drupe-enabled as default) with some success, then the problem returned (about 5 days later). The default google phone app (version 23.0) fails every time. Currently looking into TWRP/Root and hoping to eliminate certain default apps to experiment further. Will be keeping an eye on this post! :cyclops:
Click to expand...
Click to collapse
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.

Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.

brkshr said:
Are you guys on Verizon? I'm having this problem with my dad's pixel on vzw.
Click to expand...
Click to collapse
AT&T
---------- Post added at 07:47 AM ---------- Previous post was at 07:45 AM ----------
mbstone said:
Went back to Oreo before I had the problems and... problems persist. I'm sad. I had the privilege of speaking to someone from Google Support who was very knowledgeable. Unfortunately, my best option from the rep was to take it in to one of their authorized repair places.
Click to expand...
Click to collapse
--- Three weeks later ---
Could there be an issue within google play services with phone dialer app (any/or stock app)?
See my updated post (# 3) for what I've tried since..

Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.

brkshr said:
Vzw ended up replacing my dad's phone through extended warranty. I talked to Google for awhile. Multiple factory resets, factory image installs, tried older phone apks. Nothing worked.
Click to expand...
Click to collapse
Older/newer phone dialer apps didn't work for me either ... custom rom and eliminating google play services did (no gapps). I'm still tinkering with the device ... installing frequently used apps using F-droid and Yalp, will test it. Not quite sure why but it works.
I ended up flashing Lineageos for Microg, presents it's own problems in the learning experience but it works.

Nothing ever worked in the end. No, not with Verizon. Bought through Canadian carrier called Fido.
Called Google tech and they weren't overly helpful. I started a chat with a Google Tech and they suggested I take it to UBreakIFix. They did a free diagnostic test and I referenced https://support.google.com/pixelphone/forum/AAAAb4-OgUsIW_gxTpXX3s/?hl=by that thread. Said they'd fix it for free even thought I was out of warranty. Got a new motherboard and my phone works like a charm.

Some troubles with flashed ROM

I was having some issues with my Galaxy s6, so I figured if they stopped supporting my phone, I might as well get a new OS on it myself.
I rooted and installed 9.0
https://forum.xda-developers.com/ga...20x-5x-nexusos-9-0-samsung-galaxy-s6-t3843199
At first I tried to install previous versions of Lineage, but kept having issues with registering through google, but this one worked pretty easily. I am now using Nova launcher.
The issues I have with it are:
Slower GPS location, like much slower. I am now traveling in Toronto, and it's ridiculously slow to find where I am compared when i was in NYC. I'll continue testing though, maybe it was just a temporary bug
Battery drain seems faster. I was hoping to get an improvement on this issue.
I get no notifications when I get messages through "google voice' I have to open the app to look at it
There is no number in a red circle next to the app to tell me number of messages for it
Substratum not working, keep getting "could not fall back to rooted mode" although according to root checker, I'm rooted. I have no experience with this app, but it seems like it's worth checking it out lol
I think there may be more 'issues' but those are the main ones right now.

I use the latest OFFICIAL LineageOS 14.1, these works fine for me.