Database Info

Google Maps 4.0

Has anyone tried out the new GMAPS 4.0 on their device? Has anyone got it to work when using GPS? I installed it and everytime I click on Use GPS it crashes the application. This use to happen to my old I910 with version 3.32 and not sure why.

07aspenx said:
Has anyone tried out the new GMAPS 4.0 on their device? Has anyone got it to work when using GPS? I installed it and everytime I click on Use GPS it crashes the application. This use to happen to my old I910 with version 3.32 and not sure why.
Click to expand...
Click to collapse
Version 4.0 works perfect on mine and I get a quick lock on GPS. Maybe you should try reloading it.

i get a gps satellite lock inside in under thirty seconds with 4.0

I had this same issue as well. I had to revert back to v3.2.1 to use the app.

Envirosciguy said:
Version 4.0 works perfect on mine and I get a quick lock on GPS. Maybe you should try reloading it.
Click to expand...
Click to collapse
Tried uninstalling and reinstalling a few times and the same result. I also reverted back to an older version.

wow, I just got my i-920 omnia2 about 4 weeks ago and it was about 3 weeks ago I downloaded and installed google maps. it is version 3.3.0. when did they come out with version 4? the one I have works fine. takes a while to acquire satellites. I just tried out that latitude yesterday. very cool thing, but it didn't work. but the phone that I was "tracking" had latidute running then "exit". it asks if you want to still send location info and yes was selected. per google, when in this mode it sends signal based on cell tower info--does this to preserve battery life since if the gps were on constantly and sending signal if would drain it. cell tower info not as accurate. but it didn't work at all. showed essentially no movement. was going to try to leave google maps open and thus sending gps info to see if it worked that way.
oh, to original poster--didn't the i910 have gps locked so you couldn't use it except for verizon stuff?

hammerjr said:
wow, I just got my i-920 omnia2 about 4 weeks ago and it was about 3 weeks ago I downloaded and installed google maps. it is version 3.3.0. when did they come out with version 4? the one I have works fine. takes a while to acquire satellites. I just tried out that latitude yesterday. very cool thing, but it didn't work. but the phone that I was "tracking" had latidute running then "exit". it asks if you want to still send location info and yes was selected. per google, when in this mode it sends signal based on cell tower info--does this to preserve battery life since if the gps were on constantly and sending signal if would drain it. cell tower info not as accurate. but it didn't work at all. showed essentially no movement. was going to try to leave google maps open and thus sending gps info to see if it worked that way.
oh, to original poster--didn't the i910 have gps locked so you couldn't use it except for verizon stuff?
Click to expand...
Click to collapse
The GPS on the I910 was unlocked. I used IGO8 as well as GOOGLE MAPS and BING.

GPS
I have the i920 and have installed the google4 with no problems. The gps was locked within one minute, didn't time it but was within 10 meters.

Just installed Google Maps 4.0 yesterday -- works AWESOME on my i920, gps lock within 30 seconds when outside. Unfortunately still no navigation like they have on the newer android devices (grr, google bastadz!) but it most certainly does not crash.
What ROM are you using, and did you uninstall the older version manually before installing the new one? Also try using SKTools' uninstaller -- that will also scan for left behind registry keys \ temp\cache files and remove them.

Well I installed the newest version which is 4.1 with the voice command and it works great.

Working great
I would make sure you have the version available for the windows 6.5. Other than that I can't think of anything that would cause this problem besides the fact you don't have the GPS turned on for both the phone and the program.

[Q] Google Navigation keeps force closing since update

Hi guys,
SInce updating my stock HTC One S to Android 4.1.1 and HTC 4+, I cannot get Navigation to work properly. It force closes every 10 or so seconds.
The GPS is clearly working as it does find the route immediately, and starts to navigate - but then closes!
I rely heavily on Google Nav and seeing as I just got a new refurbished phone from my network, I don't want to have to put this one in for repair as well and be phonelesss for another week +...
Is this a known problem?
Thanks as always,
TD

thedynamix said:
Hi guys,
SInce updating my stock HTC One S to Android 4.1.1 and HTC 4+, I cannot get Navigation to work properly. It force closes every 10 or so seconds.
The GPS is clearly working as it does find the route immediately, and starts to navigate - but then closes!
I rely heavily on Google Nav and seeing as I just got a new refurbished phone from my network, I don't want to have to put this one in for repair as well and be phonelesss for another week +...
Is this a known problem?
Thanks as always,
TD
Click to expand...
Click to collapse
Have you tried clearing the app data and cache? Are you rooted? Sometimes I find a quick re-install does the trick. I'm guessing you have tried all of those, but thought I would through them out there.
Also, have you tried a different app. like Waze?

you're not alone
this is a known problem, see below
http://forum.xda-developers.com/showthread.php?t=2067128&highlight=gps
http://productforums.google.com/forum/#!topic/maps/1T_mDNfU8Z0

yep, it's known problem. Been using Viper 2.2.0 and nav fc in 3d mode. I put it in 2d mode as soon as I start the nav or turn screen off and use voice guidance only.

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.

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.

Google Voice Match Discussion

So I had a couple of Moto X Plays laying around which I wanted to repurpose as "Google Home" and security camera. So I take the necessary steps to install and update Google. Trying out Assistant gives me the: "Google recognized your voice, all set" -sequence and shuts of the toggle for voice match again. Weird! So I keep trying solutions upon solutions and I even revert back to stock rom 7.1.1 and to my surprise it start working again, that is, until I update my Google app again. Now somewhere Google seems to have decided not to support older ROMs anymore. Because guess what: that same version still works fine on my daily driver Samsung Galaxy S9 stock ROM. I am wondering: Is Google deliberately making newer versions of the Google App have Voice Match fail on these older roms (7.1.1 stock and 7.1.2) or am I just being an idiot?
That said I'm gonna try and find out which version of Google App I can get my older ROM to have voice match again.