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.
Related
I've been using albinoman887's ROMs for quite a while, moving from 10.1 to 10.2 and finally CM11. Never had an issues. In November I changed to sultanxda's current 4.4.2 ROM and have updated it ever since. Roughly since the late December 2013 updates (I cant recall excactly as I didn't use this phone over this period and my 2,4h Ghz Wlan failed), the Wi-Fi fails to turn on. I have read countless threads, here and elsewhere, and I am sure that this question has been asked many times - yet, despite hours of research I haven't been able to locate the reason.
S-OFF
Hboot 1.27 with juopunutbear's method
currently using
3.0.101-Sultan-kernel-ION-r57
Baseband version 11.76C.3504.00P-11.29A.3504.18M
Bootloader Locked
I have tried
- flashing several different ROMs, from Sense-based to RUU, older albinoman887 and sultanxda's, with and withouth GAPPS and different kernels
- WiFix Manager
- Tried to flash a new radio
I am not entirely sure whether the last bit worked; I followed to guidelines in this thread. The first option didn't work as it said "Remote not allowed" (is that due to my locked bootloader?). The second one with the sd-card showed no errors (actually showed "success"), however the Radio in the fastboot remains unchanged at RADIO-11.29A.3504.18_M (I tried to flash Radio 11.76C.3504.00P_11.29A.3504.18_M)
I have followed the guidelines precisely, although I am pretty sure I do not understand exactly what's happening behind certain commands (and hope not having to do so for getting further with this issue).
I am using teamwin recovery.
I have suspected that perhaps there is a mismatch somewhere along the lines of my radio. GetRIL has reported that RIL/baseband doesn't match, but I am not sure whether I understand what that means.
RIL 4.0.0013HMQ
Baseband 11.76C.3504.00P-11.29.A350
Is it a problem that the baseband in CM11 and GetRIL is shown as 11.76, while in fastboot the Radio is as 11.29 - or are these different things?
Bluetooth is btw working just fine, so is everything else. At one point in time, after wildly flashing several roms I got to the point where it rebooted constantly, however, this seems to be (as far as I can tell) gone.
3G and everything else seems to be working.
RIL/Baseband is meanwhile matching, yet to no avail regarding the WI-FI; it keeps "turning WiFi on..."
I currently have:
RIL 4.0.0024HMQ
Baseand 11.72.3504.00P-11.23.3504 ;
flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
Dear filosofem
thanks for the quick reply. I followed the instructions, then went into my current ROM (one using 3.4.10-SebastianFM-1.0.3 Kernel) and the WI-Fi is still trying to turn on constantly.
Wiped cache and dalvik (and everything else excepct SD card) and installed the latest sultanxda ROM, in the following order:
1. Kernel Aroma Installer, 2. ROM (cm-11-20140217-Sultan-pyramid.zip); 3. mini-GAPPS - yet the problem persists.
htc-sen said:
Dear filosofem
thanks for the quick reply. I followed the instructions, then went into my current ROM (one using 3.4.10-SebastianFM-1.0.3 Kernel) and the WI-Fi is still trying to turn on constantly.
Wiped cache and dalvik (and everything else excepct SD card) and installed the latest sultanxda ROM, in the following order:
1. Kernel Aroma Installer, 2. ROM (cm-11-20140217-Sultan-pyramid.zip); 3. mini-GAPPS - yet the problem persists.
Click to expand...
Click to collapse
try this my metaller mate
go to system->etc->wifi and delete the wpa_supplicant.conf. file
first back it up in your sdcard just in case
see how it goes
Unfortunately I forgot to mention in the first post that I have tried this method as well. I have also deleted the entire "wifi" folder where the supplicant file is stored (as suggested in one of many threads as a workaround)
Edit: Managed to get the supplicant file deleted again after the firmwire update to 3.33, yet again to no avail.
did you try to change WiFi region code ? you can change it by pressing settings button while in wifi, choose advance and change it over
Yes, I have tried that with the WiFix app, but also manually. Manually at least it doesn't stick to either Germany or Europe - although I am not sure whether this should really make a difference in not turning on at all. Isn't the main difference that the US merely uses additional channels that routers in Europe may not allow?
I cannot scan for networks since I don't even get there; the rest of the Advanced Wi-Fi settings will be saved, but not the region code (it states "specify the region code for Wi-Fi" every time I enter, no matter what I've selected before).
I have also ordered a new back cover, since afaik that houses the antenna, although I remain doubtful that this will work. Or does anyone think it could be worth a shot if its a hardware issue? Or would a hardware issue rather affect another part; i.e. a connector or a cable?
htc-sen said:
Yes, I have tried that with the WiFix app, but also manually. Manually at least it doesn't stick to either Germany or Europe - although I am not sure whether this should really make a difference in not turning on at all. Isn't the main difference that the US merely uses additional channels that routers in Europe may not allow?
I cannot scan for networks since I don't even get there; the rest of the Advanced Wi-Fi settings will be saved, but not the region code (it states "specify the region code for Wi-Fi" every time I enter, no matter what I've selected before).
I have also ordered a new back cover, since afaik that houses the antenna, although I remain doubtful that this will work. Or does anyone think it could be worth a shot if its a hardware issue? Or would a hardware issue rather affect another part; i.e. a connector or a cable?
Click to expand...
Click to collapse
can I say I had the same exact problem updated to kitkat "4.4.2" and my wifi n Bluetooth was killed just like how u explained n i read all thread on google, one method i haven't tried is pulling the phone apart n clean it .......
Thanks to everybody for the many suggestions - It seems, at least for me, that the problem has clearly been hardware-related. So many hours flashing countless of ROMS and yet the solutions was probably somewhere in the antenna. Today I received a new cover and after a reboot WiFi returned as normal.
I would therefore advice everyone who is in the same position (and judging by the many forum posts, it is quite common) to first try a new cover. I ordered mine for 17€ from amazon (and had it not worked, I could have returned it).
htc-sen said:
Thanks to everybody for the many suggestions - It seems, at least for me, that the problem has clearly been hardware-related. So many hours flashing countless of ROMS and yet the solutions was probably somewhere in the antenna. Today I received a new cover and after a reboot WiFi returned as normal.
I would therefore advice everyone who is in the same position (and judging by the many forum posts, it is quite common) to first try a new cover. I ordered mine for 17€ from amazon (and had it not worked, I could have returned it).
Click to expand...
Click to collapse
Hey, i had the same problem as you and for some reason as soon as i remove the back cover my wifi problem was fixed. Mine fixed it self over time
But then withouth a back cover you would only have a small percent of both network and Wi-Fi coverage (if you were lucky to get any at all), wouldn't you?
htc-sen said:
But then withouth a back cover you would only have a small percent of both network and Wi-Fi coverage (if you were lucky to get any at all), wouldn't you?
Click to expand...
Click to collapse
No, you misunderstood me. What i did to fix it was basically remove the back cover which gave me signal instantaneously and then i placed my finger on the gold thing ( the one above the camera) and this boosted my signal to max and then i put my case back on and my wifi was fixed for about 30 mins. Each and every time the time limit increased and one day later my wifi stopped disconnecting.
So here's my issue, my Galaxy S Blaze has been switched from ROM to ROM constantly, I have seen ROMS with modified build.props, other added features, and a bunch of other tweaks, you name it! I don't know what all those tweaks mean, I have no idea if it could affect the way my phone receives the signal but it got me so frustrated that I kept switching roms until finally then I went back to stock and am no longer am switching to another ROM.
Here's a history of the ROM switching I've made in the past couple of months:
1st - MIUI
2nd- Cyanogenmod
3rd- Gummy ROM
4th- Liquidsmooth ROM
5th- Cyanogenmod
6th- Dirty Unicorns (problems with signal started occurring right about here, and onwards)
7th- Stock ROM (hmm... nope nothing fixed.)
8th- Validus (still no, I didn't like the constant force-closing of many apps)
9th- Gummy ROM (nope, what's worse is my screen kept freezing if I had atleast 2 apps open and I slid down the notification drawer)
10th- Cyanogenmod (well, maybe switching to cyanogenmod will fix it)
11th- Gummy ROM (*sigh* switching back? Nope, still didn't help my signal)
12th- Stock ROM (you would expect it to be fixed right about here, but nope)
So what's up what is the exact problem with my signal? Here's the thing: My signal works! That's a start atleast. However, if I turn on my Wi-Fi while I'm home, I can still call/text people, all of that works. But after maybe 2 hours or so, the signal bar is still there, it's telling me it has signal and it's connected, SOMETIMES it will be empty meaning I have no signal(when I really do). But in reality, I can't receive texts, nor calls, none of that. So how do I fix it? By restarting my phone sadly, that has been the only solution for me for these past 2 months. People have complained to me because I don't answer my phone anymore, well I'm sorry my phone can't receive those calls due to this messed up signal. There are 3 other T-Mobile phones in the house that have no problem! The problem here is with my Blaze phone.
So what if I turn the Wi-Fi off for the whole day and see if it's the main thing causing the issue? Well, I did this. Turns out that the signal stays on longer than when I'm on Wi-Fi but it still goes out. I have switched SIM Cards, I have tried switching my APN: from "epc.tmobile.com" to "fast.t-mobile.com" but the problem appears to happen more quickly on the "epc" one than the "fast" one. Please help me with this, this has been frustrating me a lot lately. I'm not sure if anyone has even had the same exact problem that I'm having, I've searched online but haven't seen a similar problem.
Some of you might say, wow that is a lot of ROMS you've switched to, I'm sure there were more that I missed but that's as of recent. I can install ROMS correctly, I know how to use CWM when installing a .zip and using Odin when it's a .tar(or other supported file extensions). I've factory reset, wiped the cache, the dalvik cache, all before installing a new rom. After installing each rom, I've also factory reset and wiped the cache to make sure no other problems could affect the way the rom would work. Hopefully I did the procedure right, thanks for anyone who's willing to help me!
Right now I am running:
Baseband Version:
T769UVLH5
Kernel Version:
3.0.8-perf-T769UVLH5-CL990184
[email protected] #1
SMP PREEMPT Fri Aug 17 15:12:14 KST 2012
Android Version:
4.0.4
Another Issue is that I can't even transfer files to and from my phone when connected to my computer! This is another big issue, here are some images:
http :// i.imgur.com/xx699ss.png
http :// i.imgur.com/1wRzJpX.png
Here's what happens when I turn Wi-Fi Calling on but maybe it's just a built-in function that I forgot it had and it's probably normal:
http :// i.imgur.com/cTSqRci.png
By the way, sorry for the links just copy and paste them in a browser to and remove the spaces between the http :// and i.imgur, thanks! Unfortunately, I can't post links until I reach 10 posts. If the links don't work for you, I've also provided attachments.
Many thanks!!!
That last picture does show the proper function of Wi-Fi calling however I don't know what to say about the rest of your problems.
Sent from my SAMSUNG-SGH-T769 using XDA Free mobile app
There are two things I would recommend trying...
1. Use Blackhole System Wipe
I know you've been following all the proper steps in CWM (and I would say to keep doing so), but I've added using Blackhole, in addition to the first steps, and I always get great system performance on my phone, and my parent's phones (I put them on ProvisionMod after stock was being stupid). It works well for pre installation for ANY ROM and helps prevent pesky issues. However, chances are, your issue is baseband related and this probably won't solve it... But still! You never know! It's worth a shot!
2. Reroot your phone
I know this will be annoying and pesky... but sometimes the process goes wrong from the beginning and starts giving issues later on... When I first rooted my mom's blaze, something went wrong, despite my following all the directions, and one of her partitions was completely disabled, no matter the ROM. I redid the process of rooting her phone (not from GB though... From the ICS stock) and fixed the issue instantly! I would try these two steps first and see if they do anything! Good luck!
Sent from The Doctor's Blaze
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
Flashed from CM13 to CM14 without issues. However, every nightly after 11/16 causes my phone to not send txt messages. Have tried different apps, checked carrier settings, re-flashed, etc. Any help would be appreciated.
I think the Beanstalk thread gives us the best perspective on the issue. Probably early issues that will eventually get fixed.
Which baseband? This behaviour smells a lot like some of the other weirdnesses I've seen when I've had an image installed which was expecting a baseband other than the one I had in play. When I tried CM14 had the latest official O-something or other for the SM-G900P SPR and like a lot of folks, GPS was just not functional at all. So... after wiping the everythings (literally everything except my ejected microSD card) and reinstalling CM13 through TWRP certain operations (like initializing GPS) were still taking a good 30-45 seconds to initialize which wasn't the case previously with the late October nightly I was using. ...another sign that something has gone off the rails with the modem-y parts, and that they might be in a tizzy about being talked to with the wrong API.
So... just to reset everything I wound up reflashing the O-something stock firmware I had, then letting it upgrade itself via the two OTA patches to PK1. (Don't worry, I find the idea of tolerating Sprint's Crazy-Town modifications laughable.) Updated the profile and the PRL for giggles, and then reflashed in TWRP, wiped the everythings again and sideloaded the same CM13 nightly and Gapps.
I've just gotten things squared back away with CM13 and haven't had a chance to circle back around to try CM14 again (because all that other stuff takes a few hours and makes testing conflict with things like, sleeping and eating) with the new baseband, but the pass through stock and it's updates sorted out the strange 30-45s glitches. If anyone's actually tried CM14 with a PK1 baseband it would probably be worth hearing if they've got GPS and cellular traffic working simultaneously.
Update: Sure enough, after upgrading to the PK1 baseband (via a reflash to stock) CM14.1 seems to be able to handle cellular data and voice calls, wifi, bluetooth and GPS. There was a bit of weirdness with Allo making a terrible sound instead of beeping, but all things considered it looks like it's stable enough to be a daily driver for the SM-G900P now.
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.