GPS don't work in any app - Moto G5S Questions & Answers

Very recently I installed a new rom, the lineageos 17.1 that is here on the forum and good the rom is being very good for me, but today I needed to use uber to go to a place but the GPS just didn't work anywhere, either by the browser, be it in applications similar to uber, waze, etc.
I never had this problem before when using the factory rom, but I would like to know if you have any solution to fix this, because I really don't want to go back to the factory rom, because after a while my cell phone locks up too much.

Related

Google Play Services issues

I like to switch up ROMs a lot, going back and forth between Sense ROMs and sometimes to AOSP/CM-based ones. Typically, I wipe everything and install from a fresh download, check MD5s, etc. I don't back up and restore apps with Titanium Backup either.
Today I reflashed Team Ecliptic Revamped v3. It booted fine, etc. I reinstalled a lot of apps fresh from the Play Store and set everything up, logging into the usual Facebook, Twitter, eBay, etc.
Then at some point I wanted to get Xposed installed along with some modules and had to reboot. When I did, everything I'd installed from the Play Store was gone. l tried to update Google Play Services but it wouldn't allow it. I cleared data from anything/everything that I thought could be involved, but that did no good. Then I tried removing my Google account and reinstating it. Now it wouldn't allow me to log into Google at all.
I had no choice but to restore a Nandroid of another ROM.
Then I tried flashing the port of the OnePlus CM version (v2), which ran great for me a week or two ago. All of the above happened again.
What am I missing here? I'd be grateful for any suggestions.
p.s. Is it just me or are the custom recoveries acting screwy lately? I have the darndest time getting the latest TWRP (MDMower's 2.7.1.3-beta) to flash anything, and the latest Philz I could find for M7VZW, which I think goes back to early July, isn't much better.
major_works said:
I like to switch up ROMs a lot, going back and forth between Sense ROMs and sometimes to AOSP/CM-based ones. Typically, I wipe everything and install from a fresh download, check MD5s, etc. I don't back up and restore apps with Titanium Backup either.
Today I reflashed Team Ecliptic Revamped v3. It booted fine, etc. I reinstalled a lot of apps fresh from the Play Store and set everything up, logging into the usual Facebook, Twitter, eBay, etc.
Then at some point I wanted to get Xposed installed along with some modules and had to reboot. When I did, everything I'd installed from the Play Store was gone. l tried to update Google Play Services but it wouldn't allow it. I cleared data from anything/everything that I thought could be involved, but that did no good. Then I tried removing my Google account and reinstating it. Now it wouldn't allow me to log into Google at all.
I had no choice but to restore a Nandroid of another ROM.
Then I tried flashing the port of the OnePlus CM version (v2), which ran great for me a week or two ago. All of the above happened again.
What am I missing here? I'd be grateful for any suggestions.
p.s. Is it just me or are the custom recoveries acting screwy lately? I have the darndest time getting the latest TWRP (MDMower's 2.7.1.3-beta) to flash anything, and the latest Philz I could find for M7VZW, which I think goes back to early July, isn't much better.
Click to expand...
Click to collapse
TWRP updated today to 2.8 (http://techerrata.com/browse/twrp2/m7vzw)
as for playstore, i havent heard of this before. Try the new TWRP and do a full wipe and report back and i will try to troubleshoot with you.
I installed the new TWRP version but it makes no difference. I reflashed One Plus CM 11 as a test. It flashed fine, ran great, and then I rebooted for Xposed and... boom. Same problem. Maybe I need to RUU and start fresh?

[HELP THREAD] cm-14.1 on LG-G3 (Model: D8555)

I decided to update my phone from CM13 to CM14.1 the other day without having read anything about CM14 and not realising how new it was (yes I know, stupid thing to do!).
So after the update I've had nothing but problems with google services not working properly, so I uninstalled google services from the apps menu within the phone, downloaded the Android 7.1, ARM, Stock version of GAPPS from opengapps.org and booted my phone into TWRP and flashed the newest version of gapps.
This fixed the issue with google services not responding, however now none of my apps work.
Anytime I try to load an app such as facebook, email, browser. My phone will freeze for several minutes and then the app will just tell me its stopped responding.
Does anybody have any advice on what to do? (I dont care if the result is that I have to wipe the phone and lose everything on it, just want my phone to work again!)
Edit: an additional piece of info, any time I try to do something that requires root access (for example moving an app to my SD card) my phone will tell me that I don't have root access, even though I must because I'm using cyanogenmod...
Rhaom said:
I decided to update my phone from CM13 to CM14.1 the other day without having read anything about CM14 and not realising how new it was (yes I know, stupid thing to do!).
So after the update I've had nothing but problems with google services not working properly, so I uninstalled google services from the apps menu within the phone, downloaded the Android 7.1, ARM, Stock version of GAPPS from opengapps.org and booted my phone into TWRP and flashed the newest version of gapps.
This fixed the issue with google services not responding, however now none of my apps work.
Anytime I try to load an app such as facebook, email, browser. My phone will freeze for several minutes and then the app will just tell me its stopped responding.
Does anybody have any advice on what to do? (I dont care if the result is that I have to wipe the phone and lose everything on it, just want my phone to work again!)
Edit: an additional piece of info, any time I try to do something that requires root access (for example moving an app to my SD card) my phone will tell me that I don't have root access, even though I must because I'm using cyanogenmod...
Click to expand...
Click to collapse
Try doing a clean flash of the rom along with the respective gapps package. You have to flash the rom and gapps together. And for the root issue, you have to first turn ON root from the developer options in settings.
Sreerag ag said:
Try doing a clean flash of the rom along with the respective gapps package. You have to flash the rom and gapps together. And for the root issue, you have to first turn ON root from the developer options in settings.
Click to expand...
Click to collapse
Scrap this, solved the additional problem I was having.
Thank you for your assistance, all is working well now
Hi guys, is there a way to change the carrier name? The correct name for my carrier is "telecom Italia spa", not "... Italiz spa". Thanks in advance.

Android Auto Broken for me since Oreo! Problem persists across OOS and Custom Roms!

I am having major issues with android auto since Oreo
Essentially, what is happening is that the Android Auto app itself will work with two and only two apps. They are Google Maps and Google Play Music.
My problem is, none, and I truly do mean no other 3rd party apps will work with Android Auto.
I should also restate that this is a problem with the Android Auto app itself, so let's pretend no head unit or car is involved. This can be replicated on just the phone.
Here's the behavior:
-Open android auto
-Open any 3rd party app (Let's say IheartRadio)
Either one of two things happen next:
-Instantly get a screen that says "IHeartRadio Doesn't Seem to Be Working"
OR
-IHeartRadio starts like it should, and is able to play music for about 15 seconds, and then I get "Doesn't seem to be working" screen
-This happens for every 3rd party app, not just IHeart, but Plex, TuneIn, Radio Scanner, EVERYTHING except Google Play Music and Google Maps.
I should also state that Android Auto and 3rd party apps worked without a hitch, absolutely flawlessly in Nougat.
And, I've asked around the OP5t forums here and nobody is having the same problem.
-------
What I've tried so far (And hasn't worked)
-Re installing Android Auto
-Re installing every 3rd party app and re-trying
-Installing a custom ROM (Oreo) (Same exact behavior right after factory reset flashing new rom )
-Tried installing 3rd party apps from a non google play source
-Flashing OOS 8.0 Stable, as well as OB4 thru factory wipes
What I haven't tried:
-Re-locking the bootloader and flashing back to OOS nougat (Would this even help?)
I'm totally at wits end here, folks. I bought the OP5t to accompany my new car as my old phone couldn't handle android auto, this is one of the most imporatnt features to me.
Does anyone have any suggestions? Would flashing back to nougat and locking the bootloader like the phone was brand new help me? I've never seen such a problem that persists through clean flashes.
Thank you kindly everyone,
Hey!
I had this exact same problem.
I managed to solve this.
I am on OOS Open Beta 4.
Install latest:
Android Auto:
https://www.apkmirror.com/apk/google-inc/android-auto/
Android System Webview:
https://www.apkmirror.com/apk/google-inc/android-system-webview/
Google Maps:
https://www.apkmirror.com/apk/google-inc/maps/maps-9-74-0-release/
Google App:
https://www.apkmirror.com/apk/google-inc/google-search/google-search-7-23-24-release/
Google Play Services:
https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-12-2-21-release/
After installing all the apps, reboot your phone.
Android auto should work smooth again!
Just FYI, the bootloader status (locked/unlocked) has nothing to do with this.
Nick502 said:
Hey!
Android auto should work smooth again!
Click to expand...
Click to collapse
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
captainstarbucs said:
Hey there, first and foremost, thank you so much for taking time to respond! I tried your suggestion, but I'm still not having any luck
I'm going to keep messing around with it, but thank you again for the reply.
Click to expand...
Click to collapse
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Nick502 said:
Ohh that is really weird. Make sure you install all the Google Beta apps, and also the latest Android Auto version.
Are you using the Red Dash cable?
Click to expand...
Click to collapse
Yes, I'm using the dash cable that came with the phone, but this problem is isolated within the android auto app. I don't need to connect it to the car to get the issues I'm having. Just launching the app on the phone itself and starting up a 3rd party app will trigger the "seems to not be working" screen.
If I connect it to the car, the same behavior happens. No issue with the connection to the car since I'm still able to use Maps and Play.
I'm considering flashing back to nougat to see if it works and OTA'ing til I get stable 8.0 and dirty flashing OB4 today.
UPDATE!!!
I got it working, and how I fixed it was a total PITA, but it works and I'm on OOS OB4.
Here's what I did:
1. Download the first available nougat OOS and flash it. Factory wipe from stock recovery. Once booted, install android auto and 3rd party apps. Test if it works, if so...
2. Sign in google account and update to 5.0.4 via OOS updater
3. Once rebooted into 5.0.4, take OB4 and stick it onto root, and reboot to recovery again
4. I dirty flashed OB4 over 5.0.4 and it seems to work fine!
I haven't tested this in my car yet, I will be on a long drive tomorrow and update results.
Waze on android auto
Waze is working parallel to google Maps without any problems. When you open navigate both programs are shown.
Damn I just noticed it. My maps work but I tried to open Google play music and got the same error.
That was the one thing that consistently worked for me. Which rom are you on?

[Solved] Navigation apps crash on end of install/first start - LineageOS

I can't install neither Mapfactor Navigator nor Here WeGo on my Mi Max 3.
Running lineage-16.0-20191011-UNOFFICIAL-nitrogen. Firmware is 10.something
With Navigator: I tried it on a fresh install of Linage, tried it on a fresh install of AospExtended-v7.0-nitrogen-20191115-1506-ALPHA either for good measure but to no avail.
I got both APKs on my SD-card, click either to install, yes, all rights, it says it got installed successfully but on first start it crashes to reboot after a few steps - farthest I came was downloading some maps.
But most of the time it crashes directly after choosing between free or TomTom maps
HERE is basically the same thing, different steps in setting up, but crashes right before it gets to what it's supposed to do.
As you can surely tell by the description, I'm a newbie, so please use simple explanations...
Edit: Just installed Xiaomi.eu 11 and Navigator works fine. I just really, really don't like this OS for it's intrusiveness, so any suggestions still welcomed
2nd Edit: Solved! When switching back from Xiaomi.eu to Lineage, I had the infamous error 7 and had to edit the updater script file. This somehow had the side effect that I could install Mapfactor Navigator and it seems to run flawlessly now.
So I guess thank you for reading...
No, might as well use the opportunity for a general thank you to this forum - without you guys I would be forced to use my phones as the manufacturers intended them. And who wants that.

Enabling GPS on OnePlus 5T with Lineage OS

Hello there
To begin with I had a Huawei P9 Lite, which I de-googled without root or unlocked bootloader. Short story I used adb tools to remove many packages. In the end everything worked well, but no matter what I did, I couldn't use GPS.
Now I bought a used OnePlus 5T(compatible with Lineage OS) and after a bit of struggle I installed the custom ROM. Everything is great, but again no GPS ‍
I searched the internet and tried many things, installed MicroG services via F-Droid , as well as many UnifiedNlp apps and back-ends. In the end neither OSM maps can track me, nor google maps in the browser...I saw some guides using TWRP to install MicroG, but I am afraid I would lose data on the phone.
The question is what's the problem and is it normal to happen on stock Lineage OS? And if so what I must do in order to have proper GPS and tracking functionality for offline use of maps? Preferably without erasing data on the phone. I would also welcome links to other guides.
Update:
After the next Lineage OS update I was able to connect and use GPS, even without MicroG and the various back-ends, which I uninstalled.
The problem is if I haven't used it in a while it takes 5-10 minutes to find me no matter if I use OSM maps or GMaps WV(a great app, which sandboxes the web version of google maps in a single, manageable application with no history).

Categories

Resources