yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] HippoMan:
Checked the goo.im site again. Now, the md5sum had changed:

14fa6a6fb5d0fdae09d09ca222879477

Also, the file is a lot bigger. It used to be 101M, and now, it's

172,048,887 bytes.

Both the size and the md5sum didn't change over several minutes,

so I downloaded it. This time it looks good. I'm going to try to flash

it, and I'll report back.

[COLOR="Blue"]% md5sum cm-10.1-20130307-UNOFFICIAL-apexqtmo.zip[/COLOR]
[COLOR="DarkRed"]14fa6a6fb5d0fdae09d09ca222879477[/COLOR] cm-10.1-20130307-UNOFFICIAL-apexqtmo.zip
[COLOR="Blue"]% unzip -l cm-10.1-20130307-UNOFFICIAL-apexqtmo.zip[/COLOR]
Archive: cm-10.1-20130307-UNOFFICIAL-apexqtmo.zip
signed by SignApk
Length Date Time Name
-------- ---- ---- ----
108 02-28-08 21:33 META-INF/com/android/metadata
234200 02-28-08 21:33 META-INF/com/google/android/update-binary
9431 02-28-08 21:33 META-INF/com/google/android/updater-script
6459392 02-28-08 21:33 boot.img
680 02-28-08 21:33 system/addon.d/50-cm.sh
132 02-28-08 21:33 system/addon.d/blacklist
522326 02-28-08 21:33 system/app/Apollo.apk
[I]... etc. ...
... etc. ...[/I]
365296 02-28-08 21:33 system/xbin/su
910124 02-28-08 21:33 system/xbin/vim
311272 02-28-08 21:33 META-INF/MANIFEST.MF
311325 02-28-08 21:33 META-INF/CERT.SF
1714 02-28-08 21:33 META-INF/CERT.RSA
1675 02-28-08 21:33 META-INF/com/android/otacert
-------- -------
264513041 3713 files
[Samsung Galaxy S Relay 4G] :
Reuploaded, md5sum matches now. Sorry about that.
[Samsung Galaxy S Relay 4G] BinkyTClown:
Thank you so much Nardholi and the rest of the team!

I know you said it doesn't need testing but is there anything in particular you need us to look at?
[Samsung Galaxy S Relay 4G] HippoMan:
Just a quick preliminary report so far: great job, nardholio!

Because I had last been running gee-one's rooted uvma2 rom, I

wiped /cache, /system, and /data, and then I flashed this new

CM10.1 rom, followed by gapps-jb-for-cm10-20121212-signed.zip.

It came up fine, which means that the rom on the goo.im site is

complete and functional.

I'm now in the process of restoring the Titanium backup of my

apps. The restore seems to be going more slowly than I remember,

but that could be my imagination due to excitement and impatience.

In any case, the system came up, and it's working fine, so far.

I'll give a more comprehensive report a little later.

.​
[Samsung Galaxy S Relay 4G] orange808:
March 7, 2013 release:

MD5 hash checksum: 14fa6a6fb5d0fdae09d09ca222879477

File size: 164.08mb

I can confirm that it boots up to the launcher. (Although you would have no reason to doubt.)

Tried updating straight from CM9. No dice. It boots up, but after that things are unstable. You will probably want to wipe before installing if you are coming from CM9... Didn't think it would work, but I had to try. :)
[Samsung Galaxy S Relay 4G] HippoMan:
nardholio's 2013/03/07 CM10.1 works very well for me so far.

Here are the things I've tried:

1. Phone -- works

2. WiFi -- works

3. Browser -- works

4. SMS -- works

5. Camera -- works (!!!)

6. Screen -- no "tearing" noticed (!!!)

7. Various communication apps ...

A. GMail -- works

B. Google Voice -- works

C. Viber -- works

D. Kakao Talk -- works

I'm afraid to check out tethering. After installing gee-one's rooted uvma2

and the RelayTethering patch yesterday, I tried WiFi tethering for 2-3 minutes

last night. Today, I received an SMS from T-Mobile telling me that if I try to use

tethering again, I'll have to pay for a special plan. After that, my HTTP accesses

were all redirected to a T-Mobile page. I needed to call T-Mobile customer support

to undo that page redirect.

If I use tethering on this CM10.1 rom, will the same thing happen? Or does

Cyanogen tethering bypass T-Mobile's checking?

In any case, everything I tried works fine. Once again, good work, nardholio!

.​
[Samsung Galaxy S Relay 4G] BinkyTClown:
I'm up and running and things are going smooth so far.

Did a full wipe then a Titanium restore.

Not really a problem but did we lose the ability to add widgets to the lockscreen? If so, is there an app I could use for them? Really only interested in calendar and weather.
[Samsung Galaxy S Relay 4G] HippoMan:
You might be able to get what you want via ...

System settings -> Lock screen -> Slider shortcuts

If that doesn't suit you, I've always used the WidgetLocker app to set up a

custom lockscreen whenever the standard one doesn't do what I want. You

can choose between a number of themes, configure the layout, and resize

the objects shown. It also allows you to add widgets, apps, etc.

.​
[Samsung Galaxy S Relay 4G] BinkyTClown:
That only lets you set what apps the slider can launch. I'd prefer free options if there are any :)
[Samsung Galaxy S Relay 4G] janejunx:
working just perfectly over here!
[Samsung Galaxy S Relay 4G] Jason78729:
Christmas has come early! Thanks to all the developers. I'll report back any bugs or issues if I come across any that aren't already listed.
[Samsung Galaxy S Relay 4G] orange808:
Bug: NFC does not toggle.
[Samsung Galaxy S Relay 4G] croogrog:
Re: [CM-10.1] Galaxy S Relay 4G/SGH-T699 3/7/13

What would it take to add custom apps to this? Is it as easy as just putting them into /system/app?
[Samsung Galaxy S Relay 4G] mikeybot:
Did anyone else sexperience a rather long (about 7 min currently) loading screen loop?
[Samsung Galaxy S Relay 4G] BinkyTClown:
Possible charging bug?

mikey - nope, my first boot was fast.

Nardholio - Having some strangeness with charging

I have a car charger, a wall charger, and two portable batteries that will charge the phone while OFF but not while turned ON. Both will charge my G2 whether off or on.

I have some other wall chargers that work both off and on.

Is there something in the rom that would be detecting the amps and not charging if they're too high/low?
[Samsung Galaxy S Relay 4G] onebornoflight:
Re: [CM-10.1] Galaxy S Relay 4G/SGH-T699 3/7/13

Neither my car nor the stock samsung charger would charge mine earlier -stock would but car charger wouldn't last build.
[Samsung Galaxy S Relay 4G] HippoMan:
Did you wipe /cache, /data, and /system before flashing? Remnants of your

earlier OS in one or more of these partitions might prevent a proper startup.

.​
[Samsung Galaxy S Relay 4G] :
Re: [CM-10.1] Galaxy S Relay 4G/SGH-T699 3/7/13

orange808: try rebooting at least twice and trying again. This was an issue coming from stock on cm9 and if confirmed I will add it to the list.
[Samsung Galaxy S Relay 4G] shawndaivari:
has anyone had issues with the last few nightlys gps not locking on? 5 22 nightly wouldnt work.

Thanks
[Samsung Galaxy S Relay 4G] dillalade:
Not on latest but perhaps worth trying this from the Q&A Thread - http://xdaforums.com/showthread.php?p=40976136
[Samsung Galaxy S Relay 4G] BinkyTClown:
Is there any way to move apps to the external sd card? I've got precious little space free on the "internal" card but 27 gigs free on my external.

---------- Post added at 02:13 AM ---------- Previous post was at 01:39 AM ----------

Looks like I found a solution.

http://xdaforums.com/showthread.php?t=2192122
[Samsung Galaxy S Relay 4G] misteropinion:
5/23 locked just fine for me.
[Samsung Galaxy S Relay 4G] Kueber:
Just curious, WiFi-tethering still doesn't work (with protection) on the latest build?

(Haven't actually a phone to test it, but I'm working on it - pretty annoying to get one here in Germany, lol)
[Samsung Galaxy S Relay 4G] misteropinion:
Flashing from 150 (5/23) with dalvik/cache wipe to 151 (5/24) bootloops. Flashing back to 150 boots OK again.

Again, away from a real computer, can't get adb log. Is there any way to collect anything helpful from this posthumously?
[Samsung Galaxy S Relay 4G] gtmaster303:
I think there are logcat apps available

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] crayz9000:
Wi-Fi tethering with WPA2 was fixed a couple weeks ago AFAIK.
[Samsung Galaxy S Relay 4G] misteropinion:
Yes, and I like catlog, but I would love to know how that helps me with a boot loop. I didn't think the logs reached back beyone power-on?
[Samsung Galaxy S Relay 4G] gtmaster303:
Then no. Yea, you would have to catch it real time

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] :
builds 151 and 152 both bootloop. For now stick with 150 or earlier. We'll keep you posted
[Samsung Galaxy S Relay 4G] gtmaster303:
Minor detail, but lock screen sound is delayed when you lock the screen. It clicks anywhere from 2-5 seconds after you actually lock the screen

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] misteropinion:
Builds 154 and 155 also bootloop.
[Samsung Galaxy S Relay 4G] shawndaivari:
Has anyone had any luck with google wallet working? Either with this rom or on GS Relay at all? Can it work on a CM rom or with this phone/tmo?

Thanks
[Samsung Galaxy S Relay 4G] :
Build 157 should boot. Also includes the following minor changes:

Linux version 3.0.80

Video code has been tweaked a little, let me know if the screen of death comes back as one fix for that has been reverted and another brought in

Audio fix for Hangouts imported from d2, not tested

If you have bricked GPS you may may find it to work with this build without having to do anything fancy (not tested)
[Samsung Galaxy S Relay 4G] Jason78729:
Thanks nardholio. Will report back.
[Samsung Galaxy S Relay 4G] caitsith810:
157 is bootlooping for me.
[Samsung Galaxy S Relay 4G] misteropinion:
I can boot 157 successfully. Did you clear cache? What version are you coming from?
[Samsung Galaxy S Relay 4G] janejunx:
Had two full freezes on this build. No lights coming on, no screen coming on, had to pull battery. Reverted to May 19th for now.
[Samsung Galaxy S Relay 4G] caitsith810:
From the May 23rd build, cleared cache and I've been bootlooping.
[Samsung Galaxy S Relay 4G] :
Ok I put the screen of death fix back in. Will be back in for build 158.
[Samsung Galaxy S Relay 4G] aawillma:
157 boot fine for me, no screen issues thus far so I'll hang on to it.

Holy spam in a can, my compass is working. :good:
[Samsung Galaxy S Relay 4G] Jason78729:
Build 158 boots fine. No issues with screen so far.
[Samsung Galaxy S Relay 4G] mrk2815:
have a few question about CM10.1 nightly for sght699 relay 4g

1 can you use google tts and talkback?

2 can you use the home button to answer calls and swap to the call waiting calls?

3 does it have over the air updates?
[Samsung Galaxy S Relay 4G] crayz9000:
1. Google Text to Speech works great on the latest nightlies, for any app that supports TTS.

2. Works just like normal CM. If you're coming from the Samsung firmware the behavior is a little different -- but in a good way, Samsung's modified phone interface frankly is garbage.

3. AFAIK, no CM dev builds have OTA updates. In this case, the nightly builds are hosted on a separate jenkins from the normal CM nightlies.

If you have ROM Manager Pro you might be able to configure it for the nightly build location, but I haven't bothered with Pro so I can't say. I just pull a nightly right off the Jenkins build site and flash whenever I have the time / feel like taking the risk.
[Samsung Galaxy S Relay 4G] stephenclower:
To add to this, be sure you patch the Google apps package with a newer Talkback. The version included with the March 1 Gapps will crash as soon as it begins speaking.
[Samsung Galaxy S Relay 4G] alphaeagle777:
hi this is my first time that i am realy going to mess with my wife phone, i have a one s,

i went to download build 158, but saw a couple newer builds witch one should i install

Thanks

edit since no reply, tried latest version so far so good
[Samsung Galaxy S Relay 4G] b3orion:
Compass?

I'm running build 162, and my compass still isn't working...

Still have crazy magnetic field strength and incorrect headings.
[Samsung Galaxy S Relay 4G] gee one:
I'm running an older build and my compass seems to work every other time that I use it.
[Samsung Galaxy S Relay 4G] Kueber:
Same here, using #165
[Samsung Galaxy S Relay 4G] :
Few things:

Which nightly to pick? Generally the latest. The ROM is now more or less stable and new nightlies generally just have whatever enhancements upstream provides.

Compass: This is a known issue. Calibrating the compass with an app like gps status seems to help.

Question: Who here has ever turned on their screen and got a flickering background/display and what have you done to resolve it?
[Samsung Galaxy S Relay 4G] Kueber:
I had this issue a few hours ago - I exited an application (supergnes) and suddenly everything went nuts. I just rebooted the phone, haven't seen this again since.
[Samsung Galaxy S Relay 4G] Jason78729:
Any updates on the 3.4 kernel progress?
[Samsung Galaxy S Relay 4G] :
3.4 kernel boots. Still no sound. Our phone is a bit of a bastard on the sound front. We share the sound code with only 3 other Samsung devices and as far as I know none of them have any kind of active developer support (and we differ even from those devices, which is why the jaguar audio worked but still had problems)

If you know any programmers who might be willing to lend us a hand please send them our way :p
[Samsung Galaxy S Relay 4G] dillalade:
Confirmed. Flashed one of the latest few days back and this is happening. But not on the nightly I was previously running, which I cant remember which it was.
[Samsung Galaxy S Relay 4G] Kueber:
Searched the forum, but didn't find anything on its current situation.

Is there any update on the apptosd issue?

As far as I know the only way to push some appdata to the sdcard is enabling that in the app itself.. a bit inconvenient, since most apps don't have that.
[Samsung Galaxy S Relay 4G] orange808:
Look up FolderMount.
[Samsung Galaxy S Relay 4G] stephenclower:
TuneIn Radio

Starting with the nightlies from around May 30, I can no longer get TuneIn Radio to work. When clicking on the app, the window appears for a brief second or two and then exits. Before I start posting logcats and the like, is anyone else having the same issue? Both TuneIn and TuneIn Pro appears to exhibit identical symptoms.
[Samsung Galaxy S Relay 4G] BinkyTClown:
I'll second folder mount. It's worth it's weight in gold.
[Samsung Galaxy S Relay 4G] Kueber:
Foldermount is quite handy, thanks again for the hint.

I have one question related to the performance of the phone.. the touch input seems rather sloppy to me - if I make the touches visible it's noticeable that the actual input always stays behind my finger, which isn't that unusual, but it will skip certain distances to 'catch' the actual input.. this results in laggy/choppy animations.

Anything I could do about that? I'm just asking because I've no idea in which way I could influence the touch input..
[Samsung Galaxy S Relay 4G] :
3.4 kernel working

Ril

Wifi

BT

Keyboard

Touchscreen

sound (if you see lbcoder on irc, thank him for his tremendous work on this)

Bug list:

BT/wifi unstable and have incorrect MAC addresses

No sensors (accelerometer/gyroscope/light sensor/compass)

No camera

I am releasing this as a preview only. Please hold off on bug reports. At this time this is not stable enough to be considered a daily driver.

http://ls.infernix.net/jenkins/job/...-20130614-EXPERIMENTAL-apexqtmo-nardholio.zip
[Samsung Galaxy S Relay 4G] misteropinion:
At least the today update Tune In Pro works for me.
[Samsung Galaxy S Relay 4G] Jason78729:
You're my hero. I'm downloading now for testing.
[Samsung Galaxy S Relay 4G] gtmaster303:
What benefit does the 3.4 kernel have over the current one?

Latest CM10.1 build seems flawless, so I'm wondering why go through all the trouble of breaking everything to fix it again...

Great work though!

:)

Also wondering if overclocking/undervolting is a feature that may be added?
[Samsung Galaxy S Relay 4G] :
We may separately release OC/UV but it won't be in our main builds. And the reason for the new kernel is simple. It's almost required for mainlining on CM now. And Android 5.0 is coming...

Note: sensors have been fixed in apexq-nardholio-3.4 build 59.

New bootloader + baseband are required for wifi + bt on 3.4 kernel. (Turn off GPS in android settings before upgrading your modem or a nasty surprise may await you): http://xdaforums.com/showpost.php?p=41209211&postcount=1 courtesy of kilr00y
[Samsung Galaxy S Relay 4G] Jason78729:
Phone, 3g, gps, audio including Apollo and Pandora work fine. Only issue I'm having that's causing any noticeable issues is WiFi. Any logs or anything I can do on my end to troubleshoot. I'd shake your hand for your tremendous work if possible. Not an insult or negative statement to anybody but the reason I love android is because we have the ability to push our phone's capabilities whether there is an immediate improvement. Keep up the great work and I hope infernix is still in the background with nard pushing boundaries.

---------- Post added at 11:35 PM ---------- Previous post was at 11:20 PM ----------

Tried wiping cache, dalvik, and fixing permissions but still no WiFi. Rarely UE Bluetooth but I'm going to use 3.4 build for the next day and report back.

---------- Post added at 11:49 PM ---------- Previous post was at 11:35 PM ----------

Also the audio skips about every 2 seconds with headphones plugged in.

When running lsmod from the terminal doesn't show any modules. The zram.ko module I run with a script is working but doesn't show with the lsmod command , maybe this has something to do with the WiFi module not functioning?
[Samsung Galaxy S Relay 4G] crayz9000:
I just noticed some strange behavior from the Gallery app, did a quick search, and cant find any relevant suggestions, so I was wondering if anyone else has observed this.

CM has had a .nomedia bypass to prevent folders from appearing in the Gallery for some time. Touch .nomedia in a folder you want ignored, and it just worked.

With JB, .nomedia still worked for the gallery but a new bypass was made to keep MediaScanner from sucking up juice on boot. For that, touch .noscanandnomtp in the folder you want ignored.

That was working fine from the April nightlies up to at least the 06/05 nightly (all dirty updates to that point). On Friday I did a clean update to the 6/14 nightly and poof, the gallery is suddenly showing all content in folders with .nomedia and .noscanandnomtp files inside.

Did those patches get reverted accidentally or did upstream change something again without fully explaining it?
[Samsung Galaxy S Relay 4G] Jason78729:
I'm running 6/9 nightly without a full data wipe install (just cache and dalvik) and all my folders with the .nomediaandnomtp (not sure if that's spelled right) are not displaying in gallery as intended. You might try deleting those files and recreate them.

---------- Post added at 05:02 PM ---------- Previous post was at 05:00 PM ----------

Nardholio, should I do I clean install when trying the 3.4 kernel builds? Think that may be why I couldn't get WiFi working?
[Samsung Galaxy S Relay 4G] crayz9000:
Tried that, also tried placing those files into new folders. Nothing works.

Something I've always wondered about is why the Gallery was written to not ignore hidden folders and files (those starting with a .)

It seems so obvious, and wouldn't require creating hacks to work around like the .nomedia and .noscanandmtp files to begin with.
[Samsung Galaxy S Relay 4G] Jason78729:
If you haven't tried yet , try deleting the cache and force closing the gallery and see if maybe that helps. Also in developer tools u can try the scan sdcard option to see if that will recognize those files.

---------- Post added at 05:29 PM ---------- Previous post was at 05:21 PM ----------

Just reread this and noticed I need to flash the new boot loader files. Sorry for not following instructions. Pulled a total noob move.
[Samsung Galaxy S Relay 4G] Jason78729:
Reinstalled 3.4 build #59 after following the instructions and so far everything is working well. Don't use BT so don't know about that but WiFi, sound, phone, 3g, and GPS all appear to be working correctly. The screen colors seem a little more dull. Gonna test as a daily driver for the time being.
[Samsung Galaxy S Relay 4G] dillalade:
Great work with 3.4 Nard. Nice.

Discovered a very weird thing over weekend.

Long story short, me & my cousin both have the Relay, rooted both running cm10.1.

Now, we were at a friends trying to connect to his wifi, he had it MAC filtered... basically when providing him with our MAC addresses (Wifi, advanced, scroll to bottom) it turned out both of our devices has the very same MAC address...... something weird happening here.

Hence only one of us/the first person to do so could connect to his wifi.
[Samsung Galaxy S Relay 4G] :
Wifi MAC addresses are a WIP. The address is stored in the prima nv file, and we're trying to crack that.

I'll just leave this here ;) https://github.com/CyanogenMod/andr...mmit/f04b4ffceac7a9259fca601f3ba3da53d29bdb99

(Official Cyanogenmod, coming very soon)
[Samsung Galaxy S Relay 4G] crayz9000:
Test case: Placed .nomedia and .noscanandnomtp empty files inside Download folder on root of SD card. Placed one photo into same folder.

1. Deleted Gallery data/cache, force closed, restarted: No change in behavior.

2. Deleted data/cache, ran SD card scan from Developer Tools. Same.

This, as I said, was basically a clean install of CM10.1 nightly 06/14. I hit the "clear data/cache" option in ROM Manager and rebooted, not immediately realizing it was going to wipe and reinstall for me. Not a mistake I'll be making again, but it's still interesting to note.

Another change in behavior I noticed when going from the dirty upgrades to the clean upgrade was that I suddenly had slider actions on my unlock screen, which I think were added sometime between April and now. So it seems when CM makes major additions or changes, the only way to make those changes stick is to do a clean upgrade.
[Samsung Galaxy S Relay 4G] stephenclower:
Unfortunately TuneIn, the XFinity app, Google Play Music, and similar audio/EGL-based apps are still blowing up. In an attempt to find exactly where this stopped working, I've been on a hunt for the nightlies from around May 28 and up. However, since Jenkins only keeps the last fifteen builds around, anything earlier appears to be gone. And, I stupidly didn't save a copy of the older zips. Does anyone still have a copy of the 5/28 ROM?

On a related note, do the afore-mentioned apps work with the new builds based off of the 3.4 kernel? (I dare not flash quite yet since I depend on my device for GPS and such as a blind pedestrian).

Thanks,

Steve
[Samsung Galaxy S Relay 4G] Jason78729:
I like what I see. Sure wish I knew how to code so I could be of more help.
[Samsung Galaxy S Relay 4G] :
Stephenclower: I do not recommend switching over to 3.4 yet. It is true it runs but it is not 100%.

I have been unable to reproduce the audio problem with Google Music everyone is talking about. Mind you I'm also running a build based on the d2 base and not our local nightlies. (They figured out how to make our 3.0 kernel work with their upstream while we get 3.4 sorted out). If you want to preview test the 3.0 kernel on the d2 base, you can grab build 156 on ls.infernix.net/jenkins/job/apexq-nardholio. I should have a 3.4 build on the same base up shortly.
[Samsung Galaxy S Relay 4G] stephenclower:
Nard,

Thank you. This ROM remix has renewed my radio!

Steve
[Samsung Galaxy S Relay 4G] terminal addict:
Given the commonality with d2, I'm wondering if there's Miracast support.
[Samsung Galaxy S Relay 4G] Jason78729:
[MENTION=2044079]Nardholio[/MENTION]. I've seen quite a few changes on github and noticed the build repositories are moving. Is this permanent or a work around till we get merged with the d2tmo. Anything new and exciting coming down the pipes?
[Samsung Galaxy S Relay 4G] :
Nightlies have been moved over to the new d2-common base and one of the cyanogenmod maintainer's personal repos while we wait for them to add our kernel and device tree to their main repos.

Any commits you see on our repo after today are most likely 3.4 related testing.

I don't have a miracast, so I can't test it, sorry. I'm guessing the integration with d2 is not going to miraculously fix any bugs though, we worked hard to make sure everything remained as is (Although it was weird it did fix the Google Music bug)