yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] furboom1240:
Looks like Google Play Services is near the top, and you're running the same release build my friend now enjoys. I'm certain that Play Services and its location queueing could be responsible. Since you're rooted, you can do quite a few things:

-Greenify Play Services (insist on doing so)

-Disable location manually or avoid high accuracy when you don't need it

-Amplify, published by [MENTION=526666]cryptyk[/MENTION] should be helpful, too. Consider donating to his cause if it works well for you.

Thank you for those wonderful screenshots! If you need more help don't hesitate to ask...
[Samsung Galaxy S Relay 4G] phred14:
Anyone have anything to say about recent nightlies? I just realized that I'm still running 20141103, which is getting to be quite old. I see that new nightlies aren't quite, but am not sure why the gaps are there.

TDM, is there anything you'd especially lke checked out, or to be on the lookout for on 20150118, or by the time I get to this there might be a newer nightly.

As for my part, camera movies quit working back at M8, and to be honest, I haven't tried since. GPS is still not working. I have some ideas, but haven't had time, and lack a viable Windows platform to go probing the Qualcomm NVRAM.

My battery life is erratic. Sometimes a charge will last 3-4 days, sometimes it gasps to last a single day. I haven't really been able to diagnose one way vs the other, though it looks like there might be excessive wakeups when it's draining fast. When I keep wifi off long enough, the battery life seems to get better. It almost seems as if some apps are looking to see if they can phone home, and keep trying. I'm guessing that there may be some interaction here from privacy guard, since maybe an app doesn't realize it can't turn wifi/data on and contact home, so it takes a long time to give up trying.
[Samsung Galaxy S Relay 4G] furboom1240:
Time to Sound Off...

Hello, everyone! I've recently joined the CyanogenMod Community and would like you to take a look at this post under "Samsung Devices".

https://plus.google.com/113740561882628613338/posts/crFZvHWNrvM

I've about had it with Samsung thinking they call the shots, and [MENTION=5037435]REV3NT3CH[/MENTION] and [MENTION=4126377]tdm[/MENTION] are truly the developing troopers that inspired me to spawn this post, because what Samsung is subjecting us to is unfair. Please share this post with as many people as you know so I can achieve the stated goal by Christmas 2015!

Thank you for letting me be a part of the XDA experience!

-Eric
[Samsung Galaxy S Relay 4G] phred14:
Last night I loaded the 20150125 nightly - it had been since 20141103 when I loaded my last one.

First off, the video camera works again. It had quite working back at M8, and I hadn't gotten around to testing it when I started running the TDM-built nightlies later last year.

Second, GPS still doesn't work. I haven't done any of the back-flash tricks, yet. I realized that my wife's Relay is still running M8, and I've never even tried the GPS on it. I got my Relay GPS working prior to that level with just a suggested AGPS data reload.

Third - I suddenly have 5 bars of cell signal at home. For all I know it's a coincidental new cell tower turn-on, but that would be awfully coincidental. More feared is that the signal isn't any better, it's just that the bar-display code is borked. However when I got in to my office, where I usually have no signal at all, I had no bars this morning. Tonight I'll have to test this, and compare it with my wife's Relay. I would have thought it would take a radio update, not a conventional firmware flash, to have any effect on signal, if even that could do it.

EDIT: Last night after getting home, I looked at my signal again. In one spot in the house, back to one bar, in another spot back to three bars. My coverage inside the house is variable and unreliable. The morning after the flash, it must have been at the high-point of variable. I'm thinking of buying a cell-repeater to get reliable in-house coverage.
[Samsung Galaxy S Relay 4G] phred14:
Latest GPS information...

The other day another search got me here : http://androidforums.com/threads/ge...gpsclrx-also-how-to-get-your-spc-code.370042/

The described technique involves a "special phone number". I've done one of those before, when I was getting SMS working with my Cell provider. It strikes me that what's happening here is that those special phone numbers are commands to the baseband radio processor. You know, the other piece of firmware besides the bootloader that had to be updated in order to get CM10.2+ working on the Relay. The Radio is a completely separate processor, called the "baseband processor", with its own memory, firmware, etc.

The pointer I gave was for a "Samsung Indulge", and I have no idea what that is, but it is a Qualcomm chipset, just like the Relay. I'm going to give this one a try over the next few days. With any luck, since it appears to be going directly to the baseband processor, it will cut through all of the back-flash/battery-removal stuff.

Incidentally, the MEID App didn't work for me, it never liked my IEMI. I found a web-based MEID converter that worked for me here: http://imei.org/meid-esn-imei-converter/

I'll EDIT this later based on experience. Getting this out now in case someone else beats me to it.
[Samsung Galaxy S Relay 4G] scotte9999:
Interesting find, thanks for digging into it. Please keep the thread updated with your findings!
[Samsung Galaxy S Relay 4G] phred14:
Well that one didn't work. The weather here is in a brief warm (mid-20's) spell, so I decided to try it on the way home, and leave the phone up under the windshield so it could get a lock, if possible. I put the listed code in, and got an error message. I don't have the error message here, since I was about to do this on the way home from work. However I searched on the error message, and it suggested rebooting in "safe mode", which I wasn't aware that phones had. I'll give that a try tomorrow, I guess. At the moment I'm not optimistic.

In the meantime, I found another nifty link:

http://www.technobezz.com/secret-codes-samsung-galaxy-variants-s2s3s4s5/

I haven't tried any of this yet, maybe later tonight. There are a few here relevant to GPS, to try out.

Now that I've started looking, there's quite a bit of information out there on the baseband processors. Much of it is security related, and sounds like rather bad news. (as in, not very secure) It turns out that there is also a third separate CPU and OS in most of these phones, onboard the SIM card. At the moment, give the hoops that have been described for re-enabling the GPS on the Relay, I'm becoming more sure that the real problem is in figuring out how to ask the baseband processor with "pretty please with sugar on top" to enable the GPS. I've seen references to the baseband processor grabbing values out of NVRAM, which has also been part of this discussion thread.

I've seen writings from some very knowledgeable people on this, but none of them are addressing this issue, or quite truthfully, getting down to this non-esoteric a topic. They're far more concerned with the security issues, at the moment.

EDIT - Today at lunch I tried adding "*" in front and/or "," in back of the string, as I'd seen suggested. I also tried booting into "safe mode" as suggested, and then trying the string. Nothing worked, I kept getting the same error message. I'm not actually sure if I got into safe mode - there was no visual indication.

Anyway, next up is that link above, in this post. I'm especially interested in "*#1575# Manage and control GPS Menu" that it mentions in "System Control Secret code for Samsung galaxy".
[Samsung Galaxy S Relay 4G] phred14:
None of that stuff works. That earlier special gps-specific code mentioned continues to give the same error message. I've also tried many of those other secret codes, and most of them give the same message, as well. A few of them don't pop the error dialog - the phone pauses for a few seconds, then acts like nothing had happened, no special number dialed. One of those codes flashed a black-and-while "home screen" and I thought, "Oh boy, a different / more primitive dialer to try the other codes with." But it wasn't so, the screen was an image only, none of the icons worked, and it disappeared after a few seconds.

I fear this was a dead end, at least for these sets of codes.
[Samsung Galaxy S Relay 4G] taiber2000:
hi TDM,

i hope you are well as we didn't hear from you for a while, i hope you are still working on giving us cm12 goodness.

thanks again for all your work.
[Samsung Galaxy S Relay 4G] furboom1240:
Funny you mention Safe Mode. My aunt accessed it on her phone by accident. Safe mode prevents the loading of third-party apps and installed updates to built in (or in her case, protected apps). Holding the restart button when at the power dialog will warn you of this. Sad enough, she never knew her S4 could be so fast...

Good luck on that GPS discrepancy. It seems to be a d2 based issue. I do understand that we don't heavily rely on that code tree, but you can't change the fact that the Exhilarate, Relay, and like-minded chip sets share a brain as well as their bugs...gave up on dialer codes when my fingers got sick of nightlies...

I've declared war on Samsung phones running this chipset and intend to find stable custom software for these devices to run. I am not endorsing cm12 nightlies for phones older than 2014 or a MSM8974.

I root responsibly, not recklessly. Love my Official #lt03wifi...
[Samsung Galaxy S Relay 4G] Artanis02:
Hye guys, I have a problem with WiFi.

http://xdaforums.com/galaxy-s-relay-4g/help/wifi-problem-t3038513

Can some help me?
[Samsung Galaxy S Relay 4G] phred14:
I've seen nothing of the sort. I routinely bounce between home and work wifi networks, with no problems. I'm currently running the 20150125 nightly, but haven't ever seen this particular problem on any nightly or milestone. Sorry I can't help, other than to give a counter-example.
[Samsung Galaxy S Relay 4G] phred14:
I don't think I ever did really get the phone into Safe Mode. I've kind of dropped the ball on GPS, and for that matter, most things Android, lately. Not enough time.

As for "running this chipset", that sort of annoys me about the way these forums are set up. I really wish that "back of" this forum and several others, were forums for the particular chips being used. As you say, there are lots of Samsung phones, and phones of other brands using the same Snapdragon processor, etc. The way things are now, there are forums all over saying, "What's wrong with my GPS?" and making stabs in the dark to fix it, like the flash-back/remove-battery/flash-forward thing. Somewhere else they're clrearing all of NVRAM, which may fix some phones, but could well brick others. But at its essence this is a chipset problem, but there's not focus at the chipset level, even though the chipset is so common.

I firmly believe that someone who understood the github layout and the ebb and flow of the Relay drivers better than I could compare GPS initialization and libraries from CM10.1, CM10.2, and CM11 and pinpoint the problem exactly. I guess the big question is if the old firmware blob is essential to the fix, or if CM10.1 is the essential part of the fix, and the old firmware blob is necessary for CM10.1.
[Samsung Galaxy S Relay 4G] phred14:
Is anyone aware of action on the FREAK attack on TLS? I've done some searches on xda, and it appears that somebody has a fix on a 20150318 nightly. I'm not sure if that's for all CM11 or just for that particular phone. I also checked, and see that Relay nightlies are coming out roughly once a week, with 20150316 being the last. So if this is indeed a CM11-level fix and not a model-specific fix, the fix should be available next week.

In the meantime, I've already tested that the Firefox app is immune to FREAK. (Combined with the https-everywhere extension, Firefox is a good addition.) We need the CM11-level fix because any app that uses TLS is currently vulnerable to FREAK - it's not just a web browser issue.
[Samsung Galaxy S Relay 4G] phred14:
I just applied the 20150323 nightly. The native browser is still vulnerable to FREAK. Firefox is still not vulnterable. I'll assume that the native SSL/TLS libraries are also vulnerable, until the native browser is not.
[Samsung Galaxy S Relay 4G] phred14:
I just applied the 20150330 nightly. It appears to fix the FREAK problem. I accessed the client test with the native browser, and it gave me a clean bill of health.

The bad news is that this makes me want to update my wife's phone. It's running M8 and has working GPS. Tonight I loaded IEMI Tool on her phone and saved the NVRAM, and did the same on mine. They're identical - not only does diff say nothing, md5sum comes up with the same numbers. Makes me wonder if IEMI Tool is really saving the right thing - at the very least, we should have different IEMI values tucked into there. I was really hoping to replace a few bytes of my image with matching bytes out of hers, and get GPS working. Previous posts indicated the relevant offset, and I was hoping to find differences there and for the IEMI. No doubt a few others, but I had an idea where to look, at least. The fact that they're identical makes me think this isn't doing what I thought it was.
[Samsung Galaxy S Relay 4G] scotte9999:
Would a better check to be the EFS partition data? I thought that was where the NVRAM (and IMEI) information was exposed.
[Samsung Galaxy S Relay 4G] phred14:
Do you have a particular recommendation for how to do this?

I thought that's what the "IEMI Tool" I was using was doing, but as I said, that can't be, if the IEMI is in there, because the data was identical for my wife's phone and mine. I remembered doing this a while back, and found another "efs.img" file dated Nov 30 - last time I had time to fiddle. I now have four identical files, three from my phone and one from my wife's.

Also, what I've read about backing up and restoring the EFS partition says basically, "Don't!" They suggest backing it up, but then go to say that attempting to restore it is about the last thing before considering your phone a brick, because that may happen when you attempt the restore. Maybe it's fear-mongering, but I'm fully capable of following directions, etc.
[Samsung Galaxy S Relay 4G] scotte9999:
You could try http://xdaforums.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325 . Basically the EFS is another partition (or two? I seem to recall the t699 having two hidden partitions, but I may be mistaken), and you can just dd the data from the block device to 'save' it.

I wouldn't go dinking around with randomly pushing new bits on there without understanding what the data format is, but it seems like looking at the partition data is more likely to capture per-phone differences.
[Samsung Galaxy S Relay 4G] Bobby Tables:
I've upgraded from the M11 snapshot to the 20150503 nightly via the built-in updater. So far, everything looks good. A quick test of the camera shows no problems, and the GPS still works. The native browser is immune to FREAK (though I normally use Firefox anyway). I haven't tried Bluetooth audio (that's in my car), but it was working in M11 as long as I didn't try to use 2.4 GHz Wi-Fi. Or was it the other way around (2.4 GHz Wi-Fi not working if Bluetooth enabled)? Anyway, the two don't get along, but my Avant can hotspot in 5 GHz mode, so I don't have to use expensive mobile data on a cheap MVNO.

This may be superstitious of me, but I did turn on the GPS before updating.
[Samsung Galaxy S Relay 4G] Tamarinde:
Ever since the GPS bug I have been very paranoid.

I put the settings on Device Only before I update now.
[Samsung Galaxy S Relay 4G] Gibson99:
how can you see (or control) what wifi band the phone is trying to use? when i look at mine, all i see is status (connected), signal strength, link speed, security and IP address. nothing about freq. and i do have a dual band router here at the house. that said, i'm still on M7 since it's pre-gps issues and does everything i need it to.

btw - nice username. how do you pronounce the punctuation in your full name? ;)
[Samsung Galaxy S Relay 4G] Bobby Tables:
It's really controlled by the AP rather than the phone. At home, I have DD-WRT, and I can put the 5 GHz band on a separate SSID, and just connect to that. On the road with my Avant in hotspot mode, there's an advanced setting that allows you to choose which band to broadcast. If you want to see what your Relay is connecting to, an app like SignalCheck Pro will tell you.

Just like it's spelled. :D
[Samsung Galaxy S Relay 4G] Bobby Tables:
Updated to the 20150510 nightly the other day, and GPS is still working fine. I had location settings on High Accuracy, no battery pulls or anything like that.
[Samsung Galaxy S Relay 4G] yohan4ws:
Has anyone got a mirror for the modem ??

I can't DL : RelayLJ1modem.zip from nardholio because dropbox says his public links are generating too much traffic and have been disabled temporarily .. . (I know I could attempt to flash stock rom, but last time I did that I lost all my internal SD data ... 2years worth of pictures without any chance of recovery .. i have since setup google + to back them up)

I installed CM11 last night, couldn't get a gps fix but I could no problem with CM10 (and SlimKat has been working no problem as well).

Been getting some battery drain and other nuisance things happening on my phone lately and looking at giving it a change.

I'll post my results as I know a lot of people are wary of moving ahead because of GPS issues.

thx!
[Samsung Galaxy S Relay 4G] falle21:
Here https://www.dropbox.com/s/5z4rejoxzlyj0gt/JB-stock-modem.zip?dl=0
[Samsung Galaxy S Relay 4G] yohan4ws:
Ok, Posting my status as I know several of you are wondering about the latest CM11 which are still being updated w/ Nightlies as of May 10th 2015 at this writing.

I flashed CM 10.1 from September 2013,

Installed the above JB stock modem,

Reboot, downloaded GPS Status APK - got lock after a minute or so.

I pulled the battery while the GPS was locked reboot the phone, and did a nandroid restore to my CM11 nightly may 10. 1st GPS lock 77 seconds, subsequent 4 seconds.

I will report on these items over my use today:

Wifi Tether - Works flawlessly.

Hands free bluetooth in car - Works flawlessly.

Fast charge - No worky :( Doesn't appear to have kernel support :( :(

Wifi & Bluetooth running simultaneously - No Go 2.4ghz - Bluetooth streams music, wifi 2.4ghz cant access any network resources. 5ghz works ok.

GPS Navigation - Works flawlessly.

Wifi Tether with Bluetooth - haven't tested, but assuming it won't work.

I read pretty much the entire thread to see what the working status of this ROM was before installing it, if there are any other issues people have had with this ROM since M8, let me know and I will verify its working status for you and report back in this thread.
[Samsung Galaxy S Relay 4G] Bobby Tables:
Camera

I've noticed that the stock CM11 camera will crash if a) it was previously set to save pictures to SD, and b) an SD card is not present. I was almost ready to start reverting to earlier builds before I discovered this.
[Samsung Galaxy S Relay 4G] yohan4ws:
A reboot fixes temporarily, but I've found that in-call volume doesn't work properly (I'm on latest update May 31st) I'll receive a call, it will be loud and i'll tap volume down, volume adjustment shows on phone and even if I do expanded panel adjustment, no change. This means if I'm with a customer, they can hear the other side of my conversation .. Might be related to connecting to bluetooth in the car, but I'm not digging that, otherwise battery life, performance and everything else including GPS has been great.
[Samsung Galaxy S Relay 4G] furboom1240:
I'm just glad your GPS works, chum. This has been a d2-wide issue. [MENTION=5037435]REV3NT3CH[/MENTION] mentioned the split Gerrit, but Samsung's hardware habits are equal...so even if you split the code, it's pretty much the same hull...
[Samsung Galaxy S Relay 4G] phred14:
Recent activity here finally got me off my duff and working on GPS, again.

Long ago, I'd used something I'd gotten from the Google app store to presumably back up my EFS partition. There are two apexqtmo's at our house, my wife's and mine. Hers is at M8, and the GPS still works. My GPS hasn't worked since the first post-M8 snapshot I installed some time in October. My hope had been to back up her EFS and mine, then look for the differences. I'd found some other documentation suggesting an offset into the EFS where GPS stuff was being stored. With that first tool, the EFS backups from her phone and mine were identical - I'd at least expect the IEMI to show up as a difference between the two, in addition to anything else. Those backups were 262144 bytes, which sounded like a reasonable number.

More recently scote9999 suggested a different program for EFS backup, from here on xda-developers. I have installed and used that program. The images it creates are in the realm of 14MiB, which seems way too big. This time there are differences between my wife's phone and mine, but unfortunately if I look at the offset mentioned in that documentation for the GPS stuff, it's in the middle of a sea of zeros, on both phones.

So unless someone has more information about these EFS backups that might get me started on a more fruitful path, this seems like a dead end, due to lack of documentation. I'd been pursuing "secret codes" also, because some of those looked as if they might directly twiddle GPS bits. None of those codes worked for me, so that avenue appears to be closed.

I guess it's time to back-flash, as others have done. My CWM Recovery is a year and a half old, so I presume my first step will be to update that. I've started reading a bit about Nandroid backup, and have two questions about that:

1 - The stuff I've read on Nandroid backup says that it backs up and restores everything but the kernel. I would expect CM10.2 and CM11 would have different kernels, so I'm not sure how Nandroid can backup/restore across revisions like that. Or is it just enough that you can reboot, in which case you pick up the appropriate kernel for what you just restored?

2 - I've had trouble before when sending files to the phone in Recovery, and not seeing them when normally booted, or vice versa. It looks to me as if the filesystems are mounted in two different ways, between Recovery and normal boot. Since having these problems, I've taken to loading new nightlies with "adb sideload", skipping the whole issue. Can anyone enlighten me, or give a pointer to enlightenment? (Not the Linux WM - I used it for a while, but don't any more.)

Thanks.
[Samsung Galaxy S Relay 4G] yohan4ws:
[MENTION=5993492]phred14[/MENTION] Nandroid backup is a snapshot of your current config, so long as the ROM is compatible with the recovery, it will boot.

I've gone from ICS, to JB, to KitKat with recoveries .. if you want to convert your CWM recoveries to TWRP, you'll need to load the rom and swap the bootloader then re-create the backup. Pretty sure kernel must be included in the backup if restores across such platforms is successful.
[Samsung Galaxy S Relay 4G] phred14:
I'm sure I'll need to update my CWM, but is there any real need to move to TWRP, or any particularly desirable reason? I guess I always figured it was a matter of preference.
[Samsung Galaxy S Relay 4G] Artanis02:
Has the GPS problem been fixed in recent days?