Hey guys, I was wondering if anyone else has this problem. When using the official COS 13 rom everything works but GPS is slow to get a fix and when it does, it is out of sync i.e. position is further back or forward from my real location.
When I flash to Nougat, GPS works as it should, locks pretty quickly and is accurate. I've tried changing modem firmwares, using TopNTP to patch the gps.conf file and nothing seems to work in COS 13, which is the OS I prefer since Kali Nethunter works on it with no hitches.
I would really like to go back to COS13 but I use GPS occasionally and as the old saying goes, you only wish you had it when you need it the most. Any help or thoughts would be appreciated. Thanks.
Guess no one else ever heard about this.
It's not that nobody has heard of it, but you're asking about an issue with an older version of Android that is no longer being actively developed, and due to security flaws is no longer safe to run on your handset. As with all versions of Android, the code is open sourced, so you are more than welcome to dig into the source code, get your hands dirty, and fix anything you want, but expecting anyone else to fix an issue on a deprecated OS is a bit much, IMHO.
Never asked if anyone can fix it, I won't be so bold since I never did any Android development myself, hence is stated I flashed different firmware and used GPS.conf apps etc just asked if anyone else came across this issue since at one point in time we were all on cos13 and if it could be solved by flashing a zip or editing a conf file.
Related
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Termuellinator said:
Hi, i was happy seeing that the dev of the CM/Carbon/Slim-Roms didn't just stop but moved from the old original shabbypenguin-thread to xda
the latest Carbon-Build ( CARBON-KK-NIGHTLY-20140825-0209-peregrine.zip ) finally works for the most part on my side, pretty happy with that.
unfortunately 2 things aren't and i wanted to see if anyone else has this issues or has some idea to solve them
first one is, that WiFi won't connect to all networks - at home on a netgear-repeater everything is fine - in the office it won't connect to D-Link and TP-Link routers.
the other, more troubling issue is that bluetooth isn't working as it should - as long as no device is connected, everything is fine, but as soon as it connects to my car-system (MB C-Class w204 without command if that makes any difference ) the bluetooth-process stops, reconnects, stops again and so on...with my laptop everything seems to be working fine and i think the first drive after coupling also worked fine - any idea what can be the cause of this? never had this kind of problem before, be it stock or older unofficial CM-Builds etc...
i'm refering to this thread btw: http://forum.xda-developers.com/moto-g/4g-development/rom-carbonrom-kitkat-t2847887
regards
Click to expand...
Click to collapse
*push* nobody got any ideas? i would post it in the appropriate thread (especially since this rom is still only nightly) as a potential bug report, but as a new user i'm not able to :/
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Termuellinator said:
just another push...somebody must have any idea on what i can try to either solve or at least track down the cause of the issue(s)
sure enough, the BT-issue is worse..
tried the newest build (dirty update and after that clean flash), but still no luck
Click to expand...
Click to collapse
The WiFi bug is a known issue since early August. It affects almost every Moto device (G, G 4G, X and defy?) it's reported several times to CM-s bug tracking system, but nobody cares... You can use custom kernels. Maybe they aren't affected.
I don't know anything about the BT bug.
i found some posts about people having the same kind of wifi-issue, but it is good to know, that the devs are aware and - kind of - working on it
the BT-thingy is driving me insane though...fiddled around a bit, stopping BT-Related processes etc...this somehow did something...my phone now connects and stays connected, i can make phone calls...but the contact list is incomplete - only 3 random contacts are displayed on the car system
haven't rebooted since then, i kind of fear that rebooting will bring back the issue :/
BT still working after reboot, so it seems my "fix" is permanent...must have something to do with deleting the BT-data/cache while process was killed i would think - in case someone else also encounters this problem
still can't acces all my contacts from Car-system though :/
Most nights roms have a lot of issues and it is pretty hard to stay aware all of bugs. Why don't you try something more stable like Pac Man RC or some. Sometimes a different kernel will help sometimes it's the opposite.
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Termuellinator said:
Well, i'd rather use a stable version for sure...
sadly, i didn't know about falcon<->peregrine, so i thought i can use all the Moto G roms with my xt1039...
and to this date there are no stable roms for peregrine that i am aware of - an old unofficial CM-Build worked pretty good for me, but CM unfortunatley doesn't offer all the features i want - carbon covers pretty much most of it, so i'm hoping that it will be "bugfree" soon enough ^^
Click to expand...
Click to collapse
All AOSP rom uses the CM device tree and kernel as a base, so the low level kernel bugs are the same.. Also the last "stable" CM for falcon is dated back to April, so you didn't lose anything with peregrine...
Just in case anyone encounters the same Issues:
with CARBON-KK-NIGHTLY-20140922-0414-peregrine the BT-Problems seem to be resolved, connection works and the contacts are accessible from the car.
WiFi still has problems with dhcp, but as stated, devs are aware of that :good:
bad news: flashed to CARBON-KK-NIGHTLY-20141103-0939-peregrine and the BT-issue is back as in the beginning - com.andoird.bluetooth stops working - but only following the first connect -.-
interestingly going back to my pre-flash-backup didn't resolve the issue (doesn't matter if i just restore or wipe prior to that...but after flashing/restoring the first connect works perfectly)...perhaps that leads to some ideas about the cause?
was just trying to get it to work like the other time by stopping/deleting data of com.andoird.bluetooth, but didn't work this time
ok, figured it out again, this time i'll post my steps in case anyone ever encounters similar issues (and for my future reference in case i encounter them again, too )
1) unpair
2)switch off bluetooth
3) stop com.android.bluetooth in "apps"
4) delete data of com.android.bluetooth
5) reboot
6) pair
7) unpair
8) delete data of com.android.bluetooth
9) pair
10) reboot
at least these are the steps i did and it seems to be working now, again
Using Google Maps with Lollipop CM12...Has anyone had the issue where they can get a GPS lock, Google even gives you the ETA of your destination, but as you drive, you lose your lock and Maps gets stuck - thinking you're on a random side street nearby while you're actually moving on course? I am using Location in high accuracy mode. I'm running the official 4.4.4 firmware posted by @Tigerstown too. Never had this issue before. Ideas anyone? Thanks!
calebcabob said:
Using Google Maps with Lollipop CM12...Has anyone had the issue where they can get a GPS lock, Google even gives you the ETA of your destination, but as you drive, you lose your lock and Maps gets stuck - thinking you're on a random side street nearby while you're actually moving on course? I am using Location in high accuracy mode. I'm running the official 4.4.4 firmware posted by @Tigerstown too. Never had this issue before. Ideas anyone? Thanks!
Click to expand...
Click to collapse
I have had this issue before. Not on cm cause I don't run that. I'm trying to think of what ROM this was on...I tried all the lock tricks I know. My maps did the same thing as yours. Only choice I had was not to run that ROM..if you get it figured out but I don't know what you can do I didn't try let me know
It looks a lot like this problem : http://forum.xda-developers.com/google-nexus-5/help/gps-dropping-signal-ota-lollipop-update-t2951515
(Also reported in AOSP : https://code.google.com/p/android/issues/detail?id=81140 )
Sadly it seems this problem has not yet been solved/acknowledged by Google...
Well that sucks, I'm looking for a fix to it. Preferably a fix that does not involve returning to stock, then reflashing to CM after I get a lock, and hoping the planets were lined up perfectly.
ieatabiscuit said:
Well that sucks, I'm looking for a fix to it. Preferably a fix that does not involve returning to stock, then reflashing to CM after I get a lock, and hoping the planets were lined up perfectly.
Click to expand...
Click to collapse
This issue has been fixed for me for quite some time now. Which device and ROM are u running? And are you 110% sure that you're using the latest firmware?
I got it fixed. Try though, and yes I'm absolutely positive that the firmware is up to date. It happened because I was messaging with a room that used a f2fs /system position, and CM needed it to be ext4, so it was formatted before installing. I just installed a known functional ROM, then installed CM with /system left as is. No Isadora since aside from CM using a newer recovery, and forcing it on us now.
Hi there, I bought an S Relay when it was first released here in the US. I just have a tiny issue with it that still hasn't been resolved in however many times I've updated the damn thing.
I currently have a cyanogenmod based rom on the phone, but this happens with almost any cyanogenmod rom. (Including the official ones) The screen, even though I unlock the phone, will sometimes decide to stay dark or give me this weird broken-crt pattern with bits of what I'm supposed to be looking at jumbled in. Does anybody else have this issue? Or am I just crazy?
In this respect, the offical samsung rom works great with the phone. I would use it if it didn't suck so bad, which is why I want to figure this out. The specific rom is FatToad[Android 5.0.2] by TeamApexQ, but this has happened ever since they started development on the cyanogenmod rom way back when.
Are you using bluetooth when this happens? As of FatToad 5.0.2, currently the only verified reason for this to happen is memory exhaustion (and resultant spike in CPU as it attempts to swap and fails) The only thing I've seen to cause this and not fall prey to Android's low memory killer is the bluetooth stack which seems a bit buggy. If you are not using bluetooth, please send me a logcat of the issue. Also, when this happens, can you still get to adb?
Magamo said:
Are you using bluetooth when this happens? As of FatToad 5.0.2, currently the only verified reason for this to happen is memory exhaustion (and resultant spike in CPU as it attempts to swap and fails) The only thing I've seen to cause this and not fall prey to Android's low memory killer is the bluetooth stack which seems a bit buggy. If you are not using bluetooth, please send me a logcat of the issue. Also, when this happens, can you still get to adb?
Click to expand...
Click to collapse
I'm going to install android studio now and see if I can get the log info. But no, without bluetooth enabled, this still happens.
I just dumped the log from my phone around when this happens. It took a few tries to get it to happen, but it eventually did. I stopped logcat right after I got the screen to wake and unlock successfully. I'll attach it here.
Also, adb does work even when the screen doesn't wake up.
(I had to zip it since the size nazis caught me 36 kb over the 512 kb limit.)
jjsullivan5196 said:
I currently have a cyanogenmod based rom on the phone, but this happens with almost any cyanogenmod rom. (Including the official ones) The screen, even though I unlock the phone, will sometimes decide to stay dark or give me this weird broken-crt pattern with bits of what I'm supposed to be looking at jumbled in. Does anybody else have this
Click to expand...
Click to collapse
Same problem here, and I have yet to find a solution (CM11)
I tried to change the governor, and it seemed to work, but then I*updated to Valdius 5.0.2, and no wakelocks.
Posting in Q+A since I didn't see anything like this amongst the Relay ROM threads...
I flashed my ROM to Validus 5.0.2 a couple of months ago, and discovered my GPS had stopped working. However, it was not like most cases of it failing that I had read (where it seemingly tries to get a fix but never does). Instead, any attempt to use the GPS in any app would crash and reboot the OS. I tried GPS Status among others in attempting to clear AGPS data, etc. with the same end result. Even GPS Status would crash while loading the GPS.
I had a suspicion that since Validus (and maybe FatToad also?) borrowed at least some functions from CM12, it also brought along a CM12 bug involving NVRAM corruption upon flashing (don't quote me lol, this is what I vaguely recall reading somewhere here). At least, CM12 ROMs on (at a minimum) D2 chipsets around the time of Validus's release in Feb. seem to also display GPS issues. Same goes for Validus builds on multiple other Samsung devices, among others, IIRC.
Not wanting to flash ROMs between stock and custom multiple times and maybe hopefully fix the problem (since I didn't see confirmation it would fix what *I* was experiencing), I bought a new phone for a daily (just in case) and tried the attached patch (believed I just used the hw patch). Much to my surprise, it worked! No bricked phone, just a functional GPS.
Unfortunately, since it was a little while since I found the patch, I don't completely recall its origin, other than it was to repair another D2 Samsung device with CM12 (may have been S2 or S3).
YMMV with the attached patches. It may fix the laggy acquisition as well, but I was not trying to repair that particular issue in my testing.
USE AT YOUR OWN RISK! Nandroid first! I take no responsibility if this patch results in data loss or sets your phone on fire.
I also make no claim to have created this. Credit goes to the mystery person somewhere in XDA who created/found this patch for an alternate device.
I am curious to see if the patch helps anyone else avert wiping their Relay to fix GPS. I hope it will help someone out.
DIRECTIONS: Place the attached zips into your sdcard, then flash from recovery. For good measure, wipe your Dalvik/cache after flashing before you reboot. You should only need to flash one of the zips for the fix to take effect. If the hwonly patch has no effect, then try hw+configs.
NOTE: Patch was tested on 5.0.2 Validus ROM. I am not sure if this works with other ROMs or Android versions. If you're willing to try it, let us know the results.
Anyone use Vue and have a device running Pie? I've searched all over and found no information. App will run fine when started and logged in for the first time, but after that, next time it runs it hangs on the blue PS logo screen and never gets to the main menu. I've seen this on three different Pie roms on my phone now. I've been trying to confirm if this is Sony's issue and it doesn't work on any Pie ROM...?
A month later nothing has changed. Sucks to have to either clear data and log in just to use this, or use the Kodi plugin which is only good when you are stationary because the 'drops' are too severe when they happen.
Same problem here. No luck finding a real fix so far.
At least someone corroborated this. I still find no discussion of this anywhere else.
And now even clearing data and logging back in doesn't work either.
This still doesn't work! Does anyone have it working on a stock Pie ROM? Just curious.