Hi everyone.
I'm experiencing severe location inaccurateness using my one Oneplus 3 in germany.
I've already tried several different Oreo roms (OOS, LOS, RR, AOSPA), but all seemed to have the same location problems, especially indoors.
Neither cleaning agps nor changing the gps.conf seemed to improve the accuracy.
On the nougat based resurrection remix however everything was working fine for years, so I continued using this rom till now.
Recently the gps fix changed drastically within seconds, for about 100 meters.
The temporary solution was to reset the cache of the google play services and reboot the phone. This workaround lasts for 1-2 days, then I must clear the cache again.
Is anyone else having this issue or knows of a solution?
I would also be grateful for rom recommandations with stable gps.
Thanks in advance.
timperativ said:
Hi everyone.
I'm experiencing severe location inaccurateness using my one Oneplus 3 in germany.
I've already tried several different Oreo roms (OOS, LOS, RR, AOSPA), but all seemed to have the same location problems, especially indoors.
Neither cleaning agps nor changing the gps.conf seemed to improve the accuracy.
On the nougat based resurrection remix however everything was working fine for years, so I continued using this rom till now.
Recently the gps fix changed drastically within seconds, for about 100 meters.
The temporary solution was to reset the cache of the google play services and reboot the phone. This workaround lasts for 1-2 days, then I must clear the cache again.
Is anyone else having this issue or knows of a solution?
I would also be grateful for rom recommandations with stable gps.
Thanks in advance.
Click to expand...
Click to collapse
Never have this issue, even if i'm a flash'a'holic and have test (too?) many ROM. Nitrogen PIE work fine. LOS 14, 15, and Unofficial 16
works fine. Resurection, Havoc, Arrow, have their own problem but works fine. OOS and OOS_OB works fine...
Maybe one your apps is in conflict with the GPS tracker, or maybe you have a hardware related issue.
Related
Hello,
I started using the new ROM 2 days ago and I'm experiencing an anoying bug.
I already tried a hard reset to verify if the bug persist and it does.
When I'm in a building and I can't get a decent GPS signal, the location seems to default to Bengalore(bengaluru).
Any of you experiencing this bug or know a solution to this?
After using the freexperia android 4.1 for a while and using their latest nightlies, somewhen some months ago gps stopped working properly. I couldn't point my finger to it why it was behaving weirdly, but having examined the data now the problem is with the gps frequency. It only provides new data like every 5 seconds. I also tried the new legacy xperia with 4.3 but nothing changed. On original, everything works.
Anybody an idea what could be the problem? Would love to use cyanogen again.
Thanks
Somebody HELP!!!!!!!!
I'm running Resurrection Remix LP v5.5.8 on my T-Mobile Galaxy S4 (SGH-M919). I love this ROM, but I'm having a persistent problem with Bluetooth crashing, within minutes of starting up. This a consistent problem, not even remotely intermittent - happens every single time I try to turn on Bluetooth - it shuts itself off, refuses to turn back on again, and on occasion, gives me the error message "Unfortunately Bluetooth share has stopped."
I have tried clearing the Bluetooth share app cache and data to restart - it will then turn back on, but soon turns back off.
The problem was bad enough that I took RR off my phone and tried some other ROMs, including basic CM12.1. I came back to RR because the other ROMs had more critical issues, but they did help me eliminate causes of my problem, in that I didn't have Bluetooth issues with them like I do with RR, and I was still running all the same apps, same devices I was trying to attach, etc.
I've also played with several of the settings in the Kernel Aduitor, including completely shutting off the task killer. No difference - problem persists.
I also tried some of the apps on Google Play that say they're supposed to cure problems like this. Fixed nothing.
Please help. Is there an alternative something that I can flash - Bluetooth driver, different kernel, something, that can fix this issue once and for all?
Got the same problem. Android V6 RR Remix. Any suggestions?
Seems to be a consistent MM ROM issue, currently. Some seem to work better than others on some phones.
Keeping bluetooth working on the S4 seems to be "dark arts". Cyanogenmod has historically had much problems with this too. Some nightlies are okay, then others cause BT to crash. Some don't work at all.
Anyone have any resolution to this issue? I'm having the exact same symptom, but I'm on a different phone.
Note II / T-889, Conch Republic. Might've been from a radio update I did a while back, trying different ones now.
denverjoe72 said:
Keeping bluetooth working on the S4 seems to be "dark arts". Cyanogenmod has historically had much problems with this too. Some nightlies are okay, then others cause BT to crash. Some don't work at all.
Click to expand...
Click to collapse
You might give this AOKP 6 MM ROM a try:
http://forum.xda-developers.com/showthread.php?t=3391994
Users are reporting that after a week of testing the Bluetooth seems to be working rather well.
Sent from my SGH-M919 using XDA-Developers mobile app
Has anyone figured this out yet? This is infuriating. I had it reboot twice in 30 min with my stock ROM, so I had OP support "wipe" it, and reload the OS. After that, the GPS was all ****ed up so I said screw it and rooted it.
30 min into my drive into work today, it REBOOTED while running CM13 nightly and using Waze.
Charging doesn't change the outcome, bluetooth, etc. etc.
I am about to throw this phone out and get a pixel
never had this problem with MAPS.ME.
which navigations apps cause the problem?
I've been using Waze and Google Maps. It is totally random. Sometimes it won't happen for a week then all the sudden it reboots 4 times in a row.
Are you maybe using Xposed + n-ify?
The only time I had issues when using google maps navigation was when using n-ify.
Other than that, I used tha OP3 as a navigator for hours on our last scotland trip
and occasionally the last couple days without any issues.
No xposed or n-ify
+1.
I am using BJRR rom, which is also CM based.
But this problem is not persistent. Sometimes I can driver 1 hour without problem, but it could also happen within 15 minutes after I start driving.
I thought switching back to stock ROM can solve the problem, but I feel lucky that I haven't done that because it seems also to be an issue in stock, at least some of us has.
i had random restarts on 3.2.6 and 3.2.7 with root and exposed during navigation.
about 2 weeks ago switched to tesla n -- no reboots.
I have the same issue. It happens very randomly and in all roms I've used. (only marshmallow based) Usually after couple of hours of navigation either the phone reboots or looses GPS signal and only way to restore GPS lock is to reboot.
I'm currently using lineage OS 17.1 with 9.0.6 kernal, even though LOS 17.1 is sublime and works smoothly, one of the major issues that I face is that my wifi keeps disconnecting and connecting back quite often. It's not a problem with the router or modem, all my other other devices works fine in this network.
I've tired flashing different roms, combinations or roms and kernal and also tried flashing with or without magisk. None of them have helped so far, I've also wiped the whole thing and reflashed the los and other roms a couple of times.
I was previously on Experience Os by Jamal, had the same issue, but the disconnections were not this frequent.
Is there anyone else facing this issue or can somebody help me fix this, I need to run this phone at least a couple months more before and upgrade.
Thank you.
my op3 is on LineageOS 17.1 too (and i love it)
wifi problem on my phone is probably not caused by software,
it's more than likely a bad connection with the antenna,
because once there is pressure on the upper right corner it
starts reconnecting.