yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] gee one:
Not sure if this is related or helpful, but... I'm having gps issues on the stock rom. I was running a home built version of cm10 from around April 10th. I switched to the mc5 stock rom that was just released and it has compass calibration issues. I should note that the cm10 version I was using also had compass calibration issues, although they seemed to be much larger. Here's the odd part- I got a bunch of superuser toasts that showed radio asking for superuser access. It only happened during a short time period and hasn't happened since. Maybe it's not related? Maybe the issue goes deeper than cm10?

sent while running with scissors
[Samsung Galaxy S Relay 4G] :
GPS should be fixed starting with build 111. Looks like not all of the new Samsung blobs were good. People are having GPS issues under the new stock Jellybean as well. If you have PERSISTENT gps issues after flashing the new build, pm me and I will send you instructions to get it going again.
[Samsung Galaxy S Relay 4G] dillalade:
Just tested build 111 on a full wipe:

1] GPS works.

2] However "whilst recording" the rear camera video footage is still shown with wrong colours (and slightly skewed/stretched.)

(However playback is normal.)

3] Didn't test Audio.

(Back to my nandroid backup)

:thumbup:

SGR-4G on CM10.1 {JB}
[Samsung Galaxy S Relay 4G] misteropinion:
GPS works by straight flashing 111 onto 109. Lock screen camera now works.

Thanks, Nard!
[Samsung Galaxy S Relay 4G] crayz9000:
So, I've been running the April 5 build since April 7th or so, with no FCs and only the minor issue of Bluetooth phone audio not connecting to my car -- I'll pick up a call and the audio goes dead until I switch it back to the handset. I thought A2DP only applied to HQ audio like music...

I'd like to switch to the a good build, which it looks like apexq-111 is the most recent and fixes the GPS issues from the Samsung JB blobs. apexq-infernix-136 is the latest successful build of that branch with jaguar audio, but that's three days old so I'm guessing it doesn't include the GPS fix yet.

Would I be better off going to apexq-111 right now, or waiting for the jaguar audio 3.4 kernel build to get the GPS fix applied?

Also, per post # 232, I presume that we need to update to latest baseband before flashing any builds past 107...
[Samsung Galaxy S Relay 4G] misteropinion:
I can't say if you should stand pat or jump to a new build, but I didn't flash the new modem until this morning after I flashed and tested features on 111. All of the radio functions worked, but I did have some significant delays linking up wifi (and, of course, everything still works with the new modem---I did a cold start of my GPS, data and calls all work, can't say if wifi is faster yet, I can't sync up my phone while I'm at work, will update once I get home).
[Samsung Galaxy S Relay 4G] killkillkill:
Video recording colors are perfect. The blue tint is only on the PREVIEW, the video itself is perfectly fine.

The only actual problem with colors was with STILL images, pictures taken looked like they were close to black-and-white. That is fixed now with the new blobs. The blobs contain camera calibration values, so obviously, they won't be right if the device the blobs come from has any difference in the camera compared to what you're running it on.
[Samsung Galaxy S Relay 4G] kilr00y:
With Build 112 i get:

$ adb logcat | grep Thermal
E/ThermalDaemon( 253): Thermal daemon started
E/ThermalDaemon( 253): Unable to open config file '/system/etc/thermald.conf'
E/ThermalDaemon( 625): Thermal daemon started
E/ThermalDaemon( 625): Unable to open config file '/system/etc/thermald.conf'
E/ThermalDaemon( 680): Thermal daemon started
E/ThermalDaemon( 680): Unable to open config file '/system/etc/thermald.conf'
E/ThermalDaemon( 700): Thermal daemon started
E/ThermalDaemon( 700): Unable to open config file '/system/etc/thermald.conf'
E/ThermalDaemon( 951): Thermal daemon started
E/ThermalDaemon( 951): Unable to open config file '/system/etc/thermald.conf'
E/ThermalDaemon( 1310): Thermal daemon started
E/ThermalDaemon( 1310): Unable to open config file '/system/etc/thermald.conf'
E/ThermalDaemon( 1465): Thermal daemon started
E/ThermalDaemon( 1465): Unable to open config file '/system/etc/thermald.conf'
E/ThermalDaemon( 1995): Thermal daemon started
E/ThermalDaemon( 1995): Unable to open config file '/system/etc/thermald.conf'

seems like something went absent here...
[Samsung Galaxy S Relay 4G] wedg11383:
Lockscreen Rotate

Has anyone else had lockscreen rotation stop working on newest nightlies. It will still rotate if keyboard is opened but not automatically as it used to. Is this a CM change?
[Samsung Galaxy S Relay 4G] misteropinion:
I have had a problem were I see the lockscreen and the lockscreen camera fighting with each other (flickering overlays), but I can't reproduce it repeatably and a few rotations often fixes it.
[Samsung Galaxy S Relay 4G] onebornoflight:
Has the charging issue with usb chargers been addressed/fixed in these newer builds or is Android still ONLY starting MTP when you connect the stock USB charger? This is the ONLY thing stopping me from being permanently on CM 10.1.
[Samsung Galaxy S Relay 4G] misteropinion:
Still broke, though the issue tracker says that there is a patch for it, but for some reason it isn't being rolled into the build yet.
[Samsung Galaxy S Relay 4G] :
Everyone, make sure you tick GPS off in settings before upgrading to the latest modem. As far as I can tell that's all that's necessary to ensure your GPS still works after upgrade. If you don't, you will have to flash back to an earlier modem (and ROM), cycle GPS on and off, and then flash forward again.

Also, can someone with charger problems please test this build for me?

http://ls.infernix.net/jenkins/job/...-20130429-EXPERIMENTAL-apexqtmo-nardholio.zip

It also contains some new camera code, but in my tests didn't seem to fix any of the video recording issues.
[Samsung Galaxy S Relay 4G] gee one:
Would that apply to the stock rom as well, or is that something specific to the nightlies and jelly bean?
[Samsung Galaxy S Relay 4G] :
I don't know if people on stock would suffer from the same bug. The bug is related to a privacy setting on the GPS chip itself, which gets stuck in privacy mode and then when you flash a modem/ROM that doesn't use the setting it stays on.

(Parenthetical aside, I have mixed feelings about the setting, since in theory its good but I've never heard of software accessing ths GPS data outside the standard Android API, which is what it is meant to prevent)

I don't know if Samsung has something in the upgrade process to prevent the setting from getting stuck on stock. If you do though my fix to get it unstuck does work on stock.
[Samsung Galaxy S Relay 4G] misteropinion:
Yes, that fixes the charger problem. I flashed to that experimental from nightly 112. That being said, I'm going to flash up to 114 because the lock screen camera doesn't work in this experimental build.
[Samsung Galaxy S Relay 4G] crayz9000:
I guess I lucked out then; I'm using Llama to switch radio stuff off and on depending on where I am and what the battery percentage is. I flashed the new radio first, then flashed the build 111 ROM and haven't had any issues.

Still haven't had a chance to try bluetooth phone audio with build 111.
[Samsung Galaxy S Relay 4G] dillalade:
I can confirm Bluetooth Phone Audio through my Honda works as expected

:thumbup:
[Samsung Galaxy S Relay 4G] janejunx:
Flashed per your instructions and still have GPS (using one of the more stable jaguar audio builds, can't recall which).

In fact, my GPS locks and modem initialization/text sending seem considerably speedier now; my texts are sending way faster and my weather widget pulled information on first boot faster than I'd ever seen.
[Samsung Galaxy S Relay 4G] onebornoflight:
Removed for inebriated posting... sorry guys.
[Samsung Galaxy S Relay 4G] dillalade:
Clearly detailed with link to the latest gapps package in the OP :p
[Samsung Galaxy S Relay 4G] fantomex:
1) Unchecked the GPS before upgrade to latest modem. GPS works

2) Charging works on less power chargers (dunno how fast though)

3) Bluetooth sound works in this build. My Raikko speakers started working again. Whoa!

You rule Nardholio. Is there any donation page or something?
[Samsung Galaxy S Relay 4G] Jason78729:
Agreed, how can we donate?
[Samsung Galaxy S Relay 4G] kilr00y:
gps works fine now, but the compass is very unreliable.

logcat states that

W/MPL-9_sup( 628): 9 axis sensor fusion not available - No compass detected.

when running applications that try to use the magnetic compass.

in gps-status there are three values for magnetic strength (three axis, i guess). only the first value changes. the other two remain the same. but heading keep on jumping, no matter in which orientation i hold the device...

can anybody confirm this? i'm running CM10.1 nightlies.
[Samsung Galaxy S Relay 4G] fantomex:
my compass sudenly started working after upgrading to latest modem and http://ls.infernix.net/jenkins/job/...-20130429-EXPERIMENTAL-apexqtmo-nardholio.zip

before i was only able to use heading
[Samsung Galaxy S Relay 4G] onebornoflight:
Ok so I wiped cache and dalvik, wiped system and flashed the 4/29 experimental build and it bootlooped. Restored my Nandroid of UMVA2 and tried flashing one of the earlier builds I had already successfully flashed previously that wouldn't charge and then flashing the 4/29 over it with a cache/dalvik wipe and still bootlooped. I was flashing from my external sd using TWRP... any ideas?
[Samsung Galaxy S Relay 4G] :
Anymore confirmations on changes to camera behavior on experimental build? I see one report of face unlock not working but is working on main nightlies. Anyone care to test?
[Samsung Galaxy S Relay 4G] wedg11383:
Can the experimental be flashed directly over a nightly build?

---------- Post added at 06:33 PM ---------- Previous post was at 05:58 PM ----------

I think the earlier report was implying that the camera accessed by swiping to the side from the lockscreen isn't working. I am seeing the same thing with this experimental. It just freezes, no display. It does seem the face unlock is broken as well. I cant even set it up. Screen just displays starting up with blank face outline.

Camera app still has the same display issues in video mode for preview but results are fine. Still freezes up/crashes a lot when switching between front/back camera in video mode or acessing options in video mode . Camera in apps like Barcode Scanner/Skype still seem fine.
[Samsung Galaxy S Relay 4G] killkillkill:
There are two chips in the unit that provide similar and/or overlapping function: The MPL in this phone is completely unrelated to compass. The compass is on the YAS532.
[Samsung Galaxy S Relay 4G] kilr00y:
so how to read that warning? he wants to "borrow" the compass from the other chip so he can make that 9-axis-fusion-thingy? but seems like the compass is either unavailable (driver missing?) or used by something else..

as a matter of fact, the compass does NOT work at all.. he shows something. but seems like he's getting those readings from the gyroscopic sensor. fiddeling around the phone with a magnet changes the magnetic field strength that is displayed, but the arrow stays where it is. (works with my old desire z, meaning the influence from the magnet IS strong enough to make the arrow move).

it's the same for all the NIGHTLY and EXPERIMENTAL firmwares i tried out today.

<6>[ 0.883869] yas530_ext_mod_init: Probe name yas530_ext_mod
<6>[ 0.884175] input: geomagnetic as /devices/i2c-12/12-002e/input/input2
<6>[ 0.884327] input: geomagnetic_raw as /devices/i2c-12/12-002e/input/input3
<6>[ 0.884388] geomagnetic_probe: set from defconfig.
<6>[ 0.884388] geomagnetic_probe: yas magnetic position is 0
<4>[ 0.884510] i2c-core: driver [geomagnetic] using legacy suspend method
<4>[ 0.884510] i2c-core: driver [geomagnetic] using legacy resume method
<3>[ 0.908194] (null): initial offset = 656076117

seems to be the relevant module init from dmesg.

when i

echo "1"> /sys/devices/i2c-12/12-002e/input/input2/enable
cat /sys/devices/i2c-12/12-002e/input/input2/data

the values change as i put a magnet near the phone.

304300 -670500 -1415300
304300 -672700 -1415300
304300 -670300 -1415300
306600 -682500 -1417000
304800 -680400 -1416600
305300 -680800 -1416600
305700 -681700 -1416600
305000 -680400 -1416600
317100 -657700 -1406300
310200 -749400 -1360800
302900 -650500 -1414000

judging from this i assume we have a working, initialized compass. the device file is world readable, so there should be no issues with permissions either. so much for the linux side...

now... which service reads the values and provides them to the android framework?
[Samsung Galaxy S Relay 4G] killkillkill:
Do you know how to read? MPL has NOTHING to do with compass!!!! COMPASS IS YAS532.

Judging from the fact that the magnet changes the readings, your compass is functional.
[Samsung Galaxy S Relay 4G] misteropinion:
I flashed cm-10.1-20130506-EXPERIMENTAL-apexqtmo-nardholio.zip (after actually making sure I have a backup this time). The lock screen camera starts (though it took slightly longer than when entering the Camera app). I don't use the video ever so I can't speak to what it does or does not do. Charging now works on at least some chargers where it would not work before.

This is pleasing.

I'm about to run out to lunch, so I'll check a2dp, gps, compass and the fairly low power charger in the car and report back shortly.
[Samsung Galaxy S Relay 4G] shawndaivari:
is there a nightly that has the better call audio fix but also has a2dp for music?

thanks
[Samsung Galaxy S Relay 4G] kilr00y:
yeah.. i've got that. but he wants to fusion something together. at least that's how i understand it.. and since in our space and time there are only three dimensions, he's got to be looking for something else. maybe 3 axes gyro, 3 axes accel and 3 axes magnetic. and i'm quite sure that there's a compass involved, because:

W/MPL-9_sup( 628): 9 axis sensor fusion not available - No compass detected.

he doesn't frickin' find one. so how the hell do i tell him that it's there and where to find it?

because, hey.. we have one. it's just on another chip, as you kindly pointed out. and without a lil help it seems like Mr. MPL in unaware that Mrs. YAS532 just lives next door and he misses out on a great opportunity to make some... connections.. to her ;)

i've been googling about this and there's a hardware abstraction sensor service thingy. but i only found a way to set it up during system building (the config is compiled in). didn't find anything about a config file. but maybe there is.

somebody who's familiar with the android framework and/or image building should take a look at this...
[Samsung Galaxy S Relay 4G] :
There is now only one set of nightlies. Call audio is nice and loud and a2dp works. Speakerphone echo is unfortunately back but we expect to get that sorted soon enough.
[Samsung Galaxy S Relay 4G] misteropinion:
GPS works, compass is iffy, a2dp works, BT sync was very fast. I'm going to bring a different USB cable out to check the charger later, cable is suspect.
[Samsung Galaxy S Relay 4G] misteropinion:
Oh, and swapping the lock screen video camera to the FFC yielded an immediate, unforgiving camera hardware hang which required a reboot to clear. It works "as expected" once the phone is unlocked and you enter the Camera app (by which I mean the colors are off in the preview and the FFC preview is duplicated times 6... hey, is that because the resolution of the FFC is a fraction of the RFC's? Maybe not 1/6th, but is there cyphering involved which is going awry?). Again, this is all with Nard's experimental from this morning, 6May.

That said, if my car charger works once I replace the USB cable (possibly one too many slams in the car door) I'm happy enough I'm not going to bother flashing up to a Nightly until I hear these changes are rolled in. I really like having the car charger (and a2dp).
[Samsung Galaxy S Relay 4G] :
I just tested face unlock for the first time myself and had no issues. Can you give me steps to reproduce the lockup?
[Samsung Galaxy S Relay 4G] :
Try clearing data?
[Samsung Galaxy S Relay 4G] onebornoflight:
Lol worked like a charm, updated to CM10.1 4/29 build, and battery is charging. Did the whole "radio is requesting superuser permissions" ever get figured out? Wanting to flash the newest modem since I'm only showing 3G since I flashed CM and I'm wondering if that is why.
[Samsung Galaxy S Relay 4G] misteropinion:
I use pattern unlock. Swipe left to get to the camera. Always starts up as still camera. Switch to video camera. Switch to the FFC. At this point something bad happens. I had it lock the camera hardware requiring a reboot, I've had it crash and drop back to the unlock screen, and I've had the camera hardware hang but you could exit. If you can exit, sometimes the camera works when you go back, sometimes it does not. When you unlock the phone and enter Camera, sometimes it works and sometimes it "cannot connect to camera".
[Samsung Galaxy S Relay 4G] :
Starting with build 150, the following changes have been introduced to the main nightlies:

Thermal daemon errors quashed (thanks to kilr00y for reporting it)

Front facing camera now previews video correctly (recording untested and red and blue still swapped). It still hangs when switching back to still images but it's a soft hang, ie you don't have to reboot the phone.

Charging issues should be gone.

Previous screen of death issues were fixed by infernix and I didn't report that.

Current bug list:

Red and blue swapped on video recording preview, recorded video seems fine

Wifi tethering works in unencrypted mode only

Speakerphone echo and audio still needs a few touch-ups

You tell me

Roadmap to development:

Video recording issues and tethering are kernel problems and as of today we are not going to do much more development on the current kernel so we can get 3.4 going.

Audio is being worked on, timeline may shift if we find out it's a kernel problem.
[Samsung Galaxy S Relay 4G] crayz9000:
Build 150? Current build in main apexq is 120...
[Samsung Galaxy S Relay 4G] kilr00y:
please add the (magnetic) compass to the bug list.

as of now it's non-functional. seems like he uses thes gyroscope whenever an application asks for a compass

this is not an kernel issue as i pointed out earlier.

i'm looking into finding a solution myself, but i'm pretty inexperienced with the android framework.
[Samsung Galaxy S Relay 4G] :
Yes I meant 120.

kilr00y: You are more than welcome to join us on irc. The more the merrier.
[Samsung Galaxy S Relay 4G] gtmaster303:
Unencrypted as in you can't protect your network?
[Samsung Galaxy S Relay 4G] Jax184:
Yeah, can't enable WPA and stuff when operating in WiFi hotspot mode.
[Samsung Galaxy S Relay 4G] Jason78729:
Question on Stock JB update files on CM

I downloaded the stock Jellybean zip and noticed that there are multiple partitions/folders that are included in that update zip. Some examples are the persist.img.ext4, tz.mbn, etc. Is upgrading to stock with these new partitions/folders necessary? Will it affect performance (positive or negative) to upgrade to stock Jellybean with the new partitions/folders and then reinstall CM over stock Jellybean?
[Samsung Galaxy S Relay 4G] dillalade:
My charging had gotten progressively better the more I used phone.

But since flashing build 121, my charging is very normal now, charging/increasing even with screen on!

Very Happy :thumbup:
[Samsung Galaxy S Relay 4G] Jason78729:
Flashed 5-08 nightly and so far everything works as promised. Charging improved to the point I would consist that bug closed. GPS fine with new modem. Don't use camera or video. Only issue I have left is voice echo on other end of phone. I think nardholio is very close to releasing us a stable cm10.1. At this point I'm ready to start flashing 3.4 kernel builds because I now have a build that is stable enough that I can fall back to when needed.
[Samsung Galaxy S Relay 4G] :
Considering we don't have sound on 3.4 yet I'd hold off
[Samsung Galaxy S Relay 4G] kilr00y:
i have been explained yesterday my Nardholio that tz,sbl? and rpm belong to the secondary bootloader. they are not supposed to be mandatory

if you don't update the cache image, he shouldn't mind as android is supposed to rebuild it as needed.

the persist image is empty, so i heard, though can't confirm yet.. i'm working with those images atm.

the NON-HLOS.bin is the radio update.

and the system image, finally, is supposed to contain the actual Jelly Bean(s) ;)

EDIT: cache contains a recovery image... i guess he installs it on first boot. and persist actually is empty.
[Samsung Galaxy S Relay 4G] gtmaster303:
Lol, I'm sure if you labeled the network "virus" or something, that would deter most from connecting to you.
[Samsung Galaxy S Relay 4G] killkillkill:
Won't scare anyone running a linux kernel. Virus? Me no worry, me is INVINCIBLE!!!! :cyclops: :eek: :highfive:
[Samsung Galaxy S Relay 4G] kilr00y:
compass issues....

since i'm finally done putting the stock image into a recovery-flash i was able to compare what stock and cm10.1 do with the compass. with stock, compass works. with cm10.1 - as we know - it doesn't.

the device inits in kernel differ like this:

JB stock kernel: 3.0.31

[ 1.701510] yas530_ext_mod_init: Probe name yas530_ext_mod
[ 1.701754] input: geomagnetic as /devices/i2c-12/12-002e/input/input2
[ 1.701877] input: geomagnetic_raw as /devices/i2c-12/12-002e/input/input3
[ 1.701938] geomagnetic_probe: set from defconfig.
[ 1.701938] geomagnetic_probe: yas magnetic position is 5
[ 1.702029] i2c-core: driver [geomagnetic] using legacy suspend method
[ 1.702029] i2c-core: driver [geomagnetic] using legacy resume method

CM10 kernel 3.0.73

[ 0.883534] yas530_ext_mod_init: Probe name yas530_ext_mod
[ 0.883839] input: geomagnetic as /devices/i2c-12/12-002e/input/input2
[ 0.883992] input: geomagnetic_raw as /devices/i2c-12/12-002e/input/input3
[ 0.884022] geomagnetic_probe: set from defconfig.
[ 0.884022] geomagnetic_probe: yas magnetic position is 0
[ 0.884144] i2c-core: driver [geomagnetic] using legacy suspend method
[ 0.884144] i2c-core: driver [geomagnetic] using legacy resume method

both kernels provide the same input file to access the compass. and those provide data fine. but the stock kernel sets the yas magnetic position to 5 whereas the cm10 sets it to 0. could this be the reason it's not found when he attempts that sensor-fusion that fails?
[Samsung Galaxy S Relay 4G] reju:
Email Inbox Auto Check

I using nightly #116. I have noticed that the Email "inbox auto check" (frequency) does not work. So I don't new emails automatically.

Instead I need to manually refresh by opening the email application. Does anyone else have this problem?
[Samsung Galaxy S Relay 4G] infernix:
WPA2 tethering works in current nightlies, as does A2DP and low power audio playback. I am still looking into wifi direct. does anyone even use it?
[Samsung Galaxy S Relay 4G] dillalade:
Wow that's awesome!

So happy about a2dp, low power audio playback sounds superb!

I would use wifi-direct to screen share to my samsung flatscreens at home and office, it would be a really nice feature.

As would MHL/Hdmi output to those flatscreens that don't support wifi-direct screen share.

(My typical MHL output usage would be for apps like SlingPlayer.)

Going to DL latest build and give it a whirl :good:
[Samsung Galaxy S Relay 4G] gtmaster303:
That's great! Any chance we can be added to the CM lineup officially?

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] wedg11383:
Camera colors seem fixed in this newest nightly as well. Am I just seeing thing?
[Samsung Galaxy S Relay 4G] :
Sh, don't tell anyone. Next thing you know you'll notice we fixed speakerphone as well.