yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] Gibson99:
more info on gps, again, from m7.

seems google maps has completely quit using anything but cell/wifi to try to get a location. rebooting doesn't help anymore. if i change location from high precision to device only (gps sats, no agps), gmaps just gives up and says it can't get a fix.

meanwhile waze works just fine, as does gps test - i've seen gps test tell me it can see like 15 sats within just a few seconds, yet when i quit gps test and go back to google maps, gmaps just sits there like a stump. it gives me a general fix with the giant blue circle that doesn't even include my actual location, and i can scroll/zoom the map just fine. quit gmaps and go to waze or gpstest, and again, it's fine.

i tried downgrading from the current "material design" version of gmaps to the one that i put on w/ cm, and it still wouldn't get a fix, even immediately after a reboot.

waze is nice and all, but i don't understand why it won't use the system TTS - the one built into waze is slow and sounds horrible compared to the standard one (with HD voice pack). also waze seems to want to send me down crazy side streets that can't possibly be faster than the freeway or main road i'm on... and when it does tell me to turn, it's right as i'm passing the street - no possible way to make that turn.

might give OSMand another try, to see how it has improved in the years since i first tried it. i do like the live traffic info on gmaps though...
[Samsung Galaxy S Relay 4G] tdm:
Ohai

No, nothing really works yet. But it's coming...
[Samsung Galaxy S Relay 4G] Gibson99:
I think that would be worthy of a whole new thread. ;)
[Samsung Galaxy S Relay 4G] phred14:
One thing that strikes me about Lollipop is that it's shipping ART by default - I don't even know if Dalvik is in there. Way back when I first put on M8 I tried ART - briefly. It was throwing so many crash dialogs I had a hard time getting it back to the Settings option to switch back to Dalvik. (It was so painful, that if I knew more Android I would have switched back by editing a file in adb.)

Has anyone else tried ART on the Relay, especially after M8?
[Samsung Galaxy S Relay 4G] chuckiev79:
I have tried art on the relay. Not on this rom, but from my experiences art did not perform well overall in comparison to dalvik. I think battery life was about the same, but in certain instances the phone just froze for a moment and then got caught up.
[Samsung Galaxy S Relay 4G] Tamarinde:
I use TomTom and GMaps but both of them can't use GPS no matter what settings I use
[Samsung Galaxy S Relay 4G] Jeopardy:
I have been using ART constantly on M11 with no problems. Not even in development work. The applications start quicker, but the overall performance difference is most likely just placebo effect. But it is at least as good as on Dalvik.
[Samsung Galaxy S Relay 4G] orange808:
ART is just getting its foot in the door. It's likely that Google will incrementally update ART (and break compatibility with legacy apps) over time.

Just out of curiousity, is GPS functioning on any M11 Relay devices out there? You should be able to get a fix with location services and wifi disabled.
[Samsung Galaxy S Relay 4G] stashcroft:
I've got two relays. On one the GPS works fine and on the other it doesn't work at all.

The one which works was running stock. I upgraded the bootloader and modem firmware and then installed M11.

On the broken one I ran loads of different nightlies all the way up to some time in August. Nothing brings it back to life I've even tried flashing back to stock. I might just have dodgy hardware as I can't remember if I ever tested the GPS before people started reporting it didn't work.

Cheers,

Scott
[Samsung Galaxy S Relay 4G] chuckiev79:
I have had gps issues from day one on this phone, and the relays sensors are made messed up to boot. Here's a thread from way back that hopefully can shed some light on this subject. http://xdaforums.com/showthread.php?t=2261021
[Samsung Galaxy S Relay 4G] phred14:
Did your relay where the GPS failed to work on M11 start working again when you flashed it back to stock?

Did you do any factory resets anywhere in the processes?

I took a look in M8 vs M11 images, and in a file "/system/etc/init.d/60compass" and found some interesting differences. There are 2 devices in this file, and from the name I presume they're what's used for GPS/location. With M8 those devices were input3 and input4, and with M11 they changed to input8 and input9. I verified with my recent-nightly relay that input8 and input9 are indeed the correct device names, as called for by the initscript. I wondered/hoped that there was an initscript-to-device mismatch, but since some people/devices are working, that couldn't really be the problem. There must have been some sort of driver change to cause this device name change, presumably.

I had to do some sort of data reset to get GPS working at all on my Relay, but that was right after I first got it, and I forget what I did. I have since tried resetting the AGPS data after moving to the recent nightlies, but that didn't fix anything.

My wife's phone is still at M8 - I'm not flashing her up until I'm fully happy with operation on more recent releases. I haven't yet tried GPS on her phone, however. If there are any M8 vs recent comparisons or experiments, I should be able to help out.
[Samsung Galaxy S Relay 4G] stashcroft:
That's fixed it. I was using too new a version of stock in the past.

Flashed back to old CM-10.1 build and old modem.

Tested GPS and it worked.

Then flashed back to CM11 M11 and MC5 modem. Everything is fine.

Cheers,

Scott
[Samsung Galaxy S Relay 4G] juajaime:
Great news! So can anyone provide an updated modem image to flash?
[Samsung Galaxy S Relay 4G] orange808:
Don't get too excited about the fixes. I see the S III has the same issue and many users are also unable to get to GPS to function. Hopefully, it will get squared away in the L update.
[Samsung Galaxy S Relay 4G] phred14:
I did a little digging based on the thread link you posted. Nardholio said this: "from what I understand there's a non-volatile (ie factory reset, reboot, etc won't fix it) privacy setting on the GPS which, when activated, basically breaks GPS." So I managed to find my way to this: "[Qualcomm] Complete List of NV Items" - http://xdaforums.com/showthread.php?t=1954029 One of those lines under "NV Categories" is "GPS". So I've followed that link, and looking through that listing find an item, "823^"GPSOne Privacy"^"GPS*"". This might be what Narholio is talking about. I'm planning to find some sort of app that will let me read/write the NV data. What will be telling is if working vs non-working focuses down to the value in this one location. It might be possible to fix very simply, without all of the flash/pull-battery/reflash stuff.

If anyone out there knows more about what I'm talking about than I do, which I admit isn't much, please chime in. Better yet, if someone has a favorite app that does this, and if we can match this value to working/non-working GPS...
[Samsung Galaxy S Relay 4G] taiber2000:
hello,

i see that the nightlies are build as expacted but the M12 isn't up, is the M builds will be stoped?
[Samsung Galaxy S Relay 4G] Artanis02:
Hey guys.

Anybody having performance issues?

When somebody calls me or my phones wakes up with the alarm, the sound buzzes and glitches for a moment, any ideas?

I'm on older nightly but the issue was the same when i flashed the new one.

Also, is there a way to make physical keyboard work on CM10 ? (I assume simply copying the keyboard files to the zip is not enough, derp...)

Greets
[Samsung Galaxy S Relay 4G] phred14:
More on GPS / NV

OK, after a wonderful Thanksgiving out-of-state at my daughter's, I scared up a few minutes tonight. I found some app, forgotten which, which generated the file "efs.img", which I've pulled over to my PC. Incidentally, the file is 262144 bytes, or 256k. I'm sitting at byte offset 823 in that file, and my data is hex 41. I have no idea what that value is supposed to mean or if I'm really at the right offset. (Should I be doubling or quadrupling it - is that 823 a byte address, or a 16 or 32 bit word address?)

I believe the IEMI is also supposed to be stored somewhere here in the NV, but have no idea what offset it's at. The documentation I pointed out earlier is parsed out into pieces, and while that helped me find GPS it doesn't help me find IEMI. That at least would let me have a calibration point, because I could verify that the IEMI value there matches what the phone tells me its IEMI is.

Or has anyone else tried looking at this yet? Any other values for this byte? I can tell you that my GPS doesn't even show satellites.

There is another package called EFS Pro that can work with Qualcomm NV, but it's a Windows-only thing, and I only have Linux running here.
[Samsung Galaxy S Relay 4G] furboom1240:
LiquidSmooth users had a similar complaint about the physical keyboard, too. Under Settings>Language and Input, you may have to manually specify the keyboard layout and language under sec_keypad or something similar.

I hope this points you in the right direction.
[Samsung Galaxy S Relay 4G] Artanis02:
Well, I have tried quite a bit with the keyboard layout but nothing seemend to work, so i just went to CM11, but the performance is terrible.
[Samsung Galaxy S Relay 4G] orange808:
Depends on how you define performance.

In general, CM11 has been stable and compatible.
[Samsung Galaxy S Relay 4G] Artanis02:
Not :D

In my case i am having performance issues, laggs, launcher reloads etc.

BTW I copied the files responsible for the keyboard controlls from CM11 to CM10 and it work lol :D but i encountered wifi errors and launcher unexpected closes.

Will investigate.
[Samsung Galaxy S Relay 4G] taiber2000:
so i installed one of the latest nightlies (i belive the 28/11) and yes the gps isn't working anymore. trying to use fastergps the fix it but no dice.

from the reading in this thread it's seems that it some kind of privacy setting in some of the NV files... there's any new news about that.

btw the performance is flawless.
[Samsung Galaxy S Relay 4G] taiber2000:
btw the liquidsmooth rom has gps working, can we port that to cm11 tree?
[Samsung Galaxy S Relay 4G] phred14:
Do they have it universally working, or only for some? Even with CM11 some people have working GPS, some don't. We may be seeing luck-of-the-draw so far with liquidsmooth. (Or maybe not, maybe they have a real fix.)
[Samsung Galaxy S Relay 4G] taiber2000:
My previous rom was liqudsmooth (before the milestone version) and the gps worked. I understand that since then the gps brooked as well. Must be some changes to the tree. Most likely the section that is shared by the two roms.
[Samsung Galaxy S Relay 4G] chuckiev79:
This makes allot of sense to me. I wonder if GPS related build parts can be extracted from an older (working) ROM and put into a flashable zip.
[Samsung Galaxy S Relay 4G] juajaime:
Same here, was able to update to the milestone right after a clean install of the previous version for a semi-working GPS (not as many satellites but still able to get good accuracy). Still on LS since I need GPS for work.
[Samsung Galaxy S Relay 4G] robuser007:
Any progress on cm12 ?
[Samsung Galaxy S Relay 4G] scotte9999:
My wife asked me why Gmail wasn't flashing the notification LED after updating to a nightly from a week or so ago. I looked at the settings, and "Display and Lights" is now just "Display".

Is this the case for everyone else? The phone is working great otherwise.
[Samsung Galaxy S Relay 4G] Artanis02:
Yup, no LED options in CM11 ;/, we should port the ones from CM10, those were great.
[Samsung Galaxy S Relay 4G] juajaime:
For GPS someone reccomended flashing a .pit file from Odin:

http://xdaforums.com/showthread.php?t=2133400
[Samsung Galaxy S Relay 4G] stashcroft:
That file isn't for this phone and will probably break things.

I've got two relays one where the GPS as always worked and one where it was broken.

If you look further up this thread you'll see that I got the broken working by following the advice in this very old thread:

http://xdaforums.com/showthread.php?t=2261021

That method seems to work for everybody and there is even an explanation behind what is going on.

Cheers,

Scott
[Samsung Galaxy S Relay 4G] tdm:
No I've been busy with other things. But I'll try to have it working shortly after we start official nightly builds.
[Samsung Galaxy S Relay 4G] orange808:
I'll flash back to stock and try a nightly this week.

<rant>

Yikes. The devs are asking S3 and Relay users to wipe, flash back to stock, flash the new CM image, and figure out your data situation afterwards. All for a simple upgrade between milestones.

Not only that, but this is the second time this has gone down.

Most people won't have that kind of time and patience. If the d2 wanted to shed users, this is going to be wildly successful.

</rant>
[Samsung Galaxy S Relay 4G] tdm:
Which devs? Do you have a link? I'm the relay dev at the moment and the relay is not tied up in the d2 at all anymore.
[Samsung Galaxy S Relay 4G] phred14:
I believe he's referring to post #274 on this thread. As referenced by that post, back on May 2, 2013, Nardholio suggested a combination of flashing back to stock, pulling the battery at strategic time(s), and flashing to a new image.

My interpretation of his post is that there is a byte in the Qualcomm NVram for "GPS Privacy" that shuts it all down. Apparently having had problems with that "feature", they just quit touching it at all. But that means that somehow if that byte gets set to the wrong value, there is nothing that can set it back to the right value. The flash to an old ROM gets you to somewhere that can set that byte the right way, and the rest is to keep from touching it. Personally I'm not sure why there can't be a small app to just fix that byte. (I realize that NV probably has to be written by-the-block, but that's a detail.) There's another app for fiddling with NV that's used primarily to tweak the radios. There is also a Windows (All Linux at my house) program, I believe called EFS Pro, that can tweak the NV.

Nor am I sure what's up here... At first GPS didn't work for me, then I did something about deleting AGPS data and it started working. Then after flashing one of the new nightlies, it quit again, and deleting AGPS data didn't help. But it seems to me that the new nightly wouldn't have changed that byte. There's more discussion of this, along with some detail, back on this thread.
[Samsung Galaxy S Relay 4G] tdm:
Yeah I've heard of the GPS privacy thing but never encountered it. Maybe I can ask around at work.
[Samsung Galaxy S Relay 4G] orange808:
So, the Relay is or is not running a fork of the d2?
[Samsung Galaxy S Relay 4G] furboom1240:
Been like that since M11, by the way. I use Xblast to supplement that discrepancy.
[Samsung Galaxy S Relay 4G] taiber2000:
it will be highly appreciated. no gps is a bug that should be addressed.
[Samsung Galaxy S Relay 4G] tdm:
When nard left and I picked up, I split the relay off from d2. It's pretty much independent now (but they do share the same kernel sources).
[Samsung Galaxy S Relay 4G] juajaime:
Flashing 10.1+older modem with a battery pull followed by the latest nightly & modem worked for me! Thanks Scott!
[Samsung Galaxy S Relay 4G] phred14:
I take it then that you didn't have to flash to the old bootloader, just the old modem, in order to flash 10.1?

I'm not sure which level it came with, but my Relay didn't need the bootloader/modem flashes. My wife's, which I bought a few months later, did.
[Samsung Galaxy S Relay 4G] taiber2000:
this is not a preeminent solution as it can happened again after flashing new build.
[Samsung Galaxy S Relay 4G] kodimagnyl:
Thanks for the solution for the gps problem, worked like a charm!

with a new OEM battery and the latest build, my battery life has improved drastically. Now on 33% after 1d10h of mixed use and regular sync of several accounts and apps! this is almost twice what ive had previosly on several roms including stock...

Cheers:good:
[Samsung Galaxy S Relay 4G] phred14:
I've been doing more thrashing over the GPS stuff over the past few days. Nothing solid, but I'm getting a few inklings and have a few questions in case anyone else can supply some information. At the moment I'm looking at a copy of CM11 source checked out back in late August.

1 - There appear to be two chips involved in the GPS, one looks like a radio chip that shares GPS with several other radios, and the other looks like what I'm guessing is a GPS engine on the main processor SOC.

2 - There is also a firmware blob mentioned for the GPS. I'm guessing that this gets loaded into the GPS engine mentioned in #1.

3 - Looking at the source code, it appears that at the bottom level, communications with the GPS engine are through RPCs. Surprisingly there don't appear to be that many bottom-level RPCs defined either, somewhere in the realm of a half-dozen or so.

4 - I've found several defined variables of the sort NI_PRIVACY_OVERRIDE, and the "N" at the start of that appears to be related to Networking. I'm not sure if this involved with the privacy bit we're talking about in the firmware, or not.

5 - I haven't found any references to the NV ram anywhere near the GPS stuff, but then this might be part of the problem.

6 - I haven't found any initialization code for the GPS engine, but maybe that's all buried in the blob.

Since the "GPS fix" involves flashing CM10.1, I've been looking at the CM10.1 source on github. It's such a big batch of stuff I'd rather not download it all. At the same time, it's really difficult to get any sort of big picture using a web browser on github.

Questions:

1 - Does anyone have a feel if I'm barking up the right tree?

2 - While writing this post I did a quick search and found another place to look. I've only skimmed it, but am posting the link here for others, "Understanding Andriod GPS Architecture" :

http://xdaforums.com/showthread.php?t=2063295

On the same search, I found "How to clear Modem Memory(nvram). (fixes gps and many modem issues like slow speed)" :

http://xdaforums.com/showthread.php?t=1226074

I somehow doubt that it's fully applicable to the Relay, but it does share some similarities to the back-flash/battery-pull fix.

3 - I get the impression that there have been significant source code tree changes between 10.1 and 11, and even some tree changes in the past few months. Does anyone have a better feel for what changed, and can perhaps point me in the right direction for looking on github?

My hope here is that we could find our way to an app or native binary that would stuff the right info into nvram, to bring back the GPS easily and safely.
[Samsung Galaxy S Relay 4G] furboom1240:
My Christmas Relay for Root

Hello, everyone! As you may have noticed on my signature on recent posts, I no longer own the Galaxy S Relay (#apexqtmo). The reason I finally parted ways with my QWERTY sweetheart was for the benefit of another sweetheart:

I obtained my HTC One M8 November 3rd, 2014 via Swappa from a start-up seller in Cuadahy, CA. The phone was already rooted, and even S-Offed (LIquid sunshine gets a whole new meaning and I'm sure was well worth the $25 - Please do not pirate Sunshine - I discourage such behavior as it is disrespectful to the devs who put code, sweat and tears into making it work for you - and ONLY you!)

Of course, the Relay sports a Mini-SIM sized card (some carriers refer to it as Standard SIM) and the One M8, uses Nano-SIM (not much bigger than my ring fingernail) and I asked T-Mobile to send me a Nano-SIM to activate my new pride and joy. When the two joined up, the activation process took only 6m12s (oh yes I timed it!) and I was thrilled.

But now, my Relay, divorced from the phone number it carried from Sprint, wanted new life. I gave it exactly what it asked for. On November 29th, just 60 hours after I had Thanksgiving dinner in Canarsie, I gave the gift of CyanogenMod 11 to a friend who had ABSOLUTELY NO IDEA WHAT TO DO WITH IT! Her previous phone was a Galaxy Exhibit (#codinatmo) and it ran out of space (1.47 GB is not even a meal) and since her phone sported a Mini-SIM, it was an easy swap for her.

On her old phone, TouchWiz on JellyBean 4.1.2 was an abomination, composing a 221-system-app roster that she couldn't delete even if I helped her. It actually reminded me of what my Relay had gone through before I discovered wonderful maintainers, past and present, like [MENTION=2044079]Nardholio[/MENTION] [MENTION=4908192]Magamo[/MENTION] and [MENTION=4126377]tdm[/MENTION] and I will say, I thank you ALL for indirectly making my friend's dreams come true with a phone that has software that treats her with the respect she so deserves from a device that should WORK.

Oh, and I can't forget to acknowledge [MENTION=2668734]thomassafca[/MENTION] for the fabulous work on your Samsung Galaxy S5 theme (com.thomassafca.theme.new.touchwiz) which is my friend's CM11 theme of choice on her rooted new toy. Certainly worth the $2.57 - get it here.

No rooted device is tricked out enough without Xposed Installer and modules, and [MENTION=4419114]rovo89[/MENTION] I'm certainly grateful for your hard work. With my help, she's doing fantastic running that marvel. I have faith that you can make an ART-compliant version of Xposed one day that all custom users can enjoy.

Of course, the reason I mentioned this assortment of devs is to illustrate one important point - Development requires teamwork.

Together Everyone Achieves More
[Samsung Galaxy S Relay 4G] AndroAsc:
I flashed from CM 10.1 to CM11-M11 and my battery is getting drained really fast. Is this a known issue?
[Samsung Galaxy S Relay 4G] furboom1240:
You may not have supplied this detail, but are you using the right baseband and bootloader? I understand CM 10.1 = Jelly Bean 4.2.x, but inquiring minds would like to know more details, like a screenshot of your battery stats. Initiate a screenshot by holding Power+Volume Down at the same time until a shutter sounds.

That will help determine what could be causing your battery to slip up...
[Samsung Galaxy S Relay 4G] Gibson99:
Also with noting whether it was a clean or dirty flash, and maybe what recovery you're using.
[Samsung Galaxy S Relay 4G] AndroAsc:
I've attached some screenshots on the battery stats and OS details. It was a clean flash, and I was using TWRP. I did flash the bootloader and radio as per the wiki instructions.
[Samsung Galaxy S Relay 4G] taiber2000:
hi tdm,

as the CM12 source is out, the next update will be CM12 and no CM11?
[Samsung Galaxy S Relay 4G] TPMJB:
^I second this. [MENTION=4126377]tdm[/MENTION] are you planning on working on Android 5.0? I thought your roms ran the best! I still run your AOKP every day!
[Samsung Galaxy S Relay 4G] Gibson99:
Not that long ago he posted a photo of a relay running 5.0 but said it was still very flaky and just barely even booted up. Takes time...
[Samsung Galaxy S Relay 4G] tdm:
Yes I'll be working on cm12 soon. I'll try to pick it up again this week.
[Samsung Galaxy S Relay 4G] REV3NT3CH:
[MENTION=4126377]tdm[/MENTION] just a heads up... where i have Lolli is just about where s3 is...camcorder doesnt work on all d2 variants and cousins but i have perfect working camera.... audio doesnt work worth a damn and i believe that is to blame for video not working as well according to logs. i was able to get wifi going by switching some stuff in fstab for modem by switching to firmware-mdm like everyone else did and by also going module-less like the s3's and most the other cousins did...all that really needs done is audio/video and camcorder (which again...camcorder is an issue for all currently)

Edit: if you need any help or wanna collaberate just pm me or we can discuss more on hangouts or something
[Samsung Galaxy S Relay 4G] taiber2000:
i hope that tdm and REV3NT3CH will work together to bring us the best experience we can have.

thank you both kind sirs.