I can not get Google maps (or other google apps like calendar and YouTube) to work anymore, after applounge started having issues. (From posts here I can see many have difficulties with applounge…)
I then went to aurora store which worked more or less on app install and updates, but does not help with Google problems.
I tried looking into microG, but whenever I try to log in, I get the message that this Google account already exists on the phone. Made a new Google account, same result. Did restarts and reinstalls, same results.
So my main problem is: my Google services workaround is failing.
What do I do?
(I am travelling right now, so quickly looking up a hostel, seeing reviews on stuff, asking for ways, searching for the next supermarket and some museums opening hours, I don’t know how else to do all that without Google maps super duper unfortunately.)
It is not yet proven but updating /e/OS and / or Android version might force one to Update apps, and it might be hard to go back to this advice, and something “nearly working” might break further to “not working”.
You say /e/os 1.2 in your title, I think this will be the reason that the “fundamental” issues you are looking at seem unusable to you.
In case you would consider an upgrade (not especially suitable while travelling), perhaps start from telling us exactly what you are running
You may have read of an /e/ server outage may preclude some “quicker fix”. Maybe you read about App Lounge upgrade … but I think you will need newer /e/OS to get App Lounge to update itself in the way suggested here
… then you would be back to my first link warning, Re Google, assuming that is what you really want!
So are you sure it really does not work in open sky, out of built up area ?
What is possible to likely is that Network location is broken in your old build. One useful purpose of Network location can be that it often allows some sort of location quickly, then GPS jumps in with accurate location. However, slight speculation, GPS if it is viewed by the OS as non confident, may just not happen.
Just to add some information to @aibd’s good answer: Indeed, Google changed some time ago the way the Google Play Services signature was checked. Hence, a corresponding patch had to be implemented for microG (the open source Google Play Services replacement used by /e/OS and other custom ROMs). The patch was rolled out with /e/OS 2.6.x. (And indeed, I have just installed Google Maps on my OnePlus 6 with /e/OS 2.6.3, and Google Maps seems to work as intended.)
Unfortunately, you seem to be currently stuck at /e/OS 1.2 or /e/OS 1.20. The OTA upgrade is currently not available due to the Murena.io outage (and it is not clear whether it will be available at all even after the outage).
There are several threads with the fp4 label and some information how a “dirty flash” upgrade can be done without data and app loss, e.g.
If you decide not to wait for the end of the Murena.io outage and to try a dirty flash when back home, you should still backup all your data beforehand because the upgrade could still fail. (There is the hard saying that all data without backup is by definition unimportant and can be deleted without regret.)
Thanks everyone! Waking up to a lot of help, great!
I am not really deep into the whole free ROMs stuff and software in general, but I understand some.
Thanks for the reminder to not update Google stuff. I did now double check!
I had read about the murena outage, yes. And I figure it’s uncertain when a fix for my situation will be available and how stable it will be. I am fine with that for now and appreciate the devs work!
Now two main points.
GPS/localization: Gm does not find me. Waze does. Telegram gets stuck when trying to send location. Whatsapp manages to send location, but needs several tries. I am a good enough map reader so this is not a biggie for me atm.
e/OS version: I might be stuck, yes. Will not try flashing now. Will look into it when back home around the end of February, maybe the whole situation will have developed by then. OTA would be wonderful, but could consider doing it differently.
This is what I have right now: 1.20-s-20240220382012-stable-FP4
Probably mentioned in the links above, but the things to be most aware of
Stable, now known as official, you probably don’t want to change Build type to community=dev.
Stable means a higher chance of locked Bootloader. Lock status can be checked if you boot into Bootloader, will be stated. Be aware unlocking a locked bootloader will Factory reset, that is Format data.
1.20-s- indicates Android 12 (S). So you will inevitably be doing an Android version upgrade initially to Android 13 (T). Be aware Android 14 (U) was withdrawn. Probably not an issue if you wait till you are home.
As OTA has not happened when it should have or in the 9 months since, I think it unlikely now.
