yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] John5788:
I have problems with screen wake. Is it just me? I would try to wake up the phone, but screen is still off. I can still touch and control elements on the desktop, I just can't see anything. I have to attempt waking it multiple times for the screen to come live.
[Samsung Galaxy S Relay 4G] janejunx:
I thought MMS sizes were carrier-dependent?

http://support.t-mobile.com/docs/DOC-3310

Says it maxes at 1MB, but maybe that's just outdated? Seems totally crazy of them to demand something that would affect all t-mobile phones.
[Samsung Galaxy S Relay 4G] gtmaster303:
Been having the same problem intermittently all the way back to the 3.0 kernel builds

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] :
We've traced the AVS bug to AVS on the second core. People that were avoiding newer builds because it crashes are asked to please try build 247 or later.
[Samsung Galaxy S Relay 4G] scaltro:
I'm using the build 247 and I haven't got a reboot yet... Nice!

Only I can still have issue with my sd card... sometimes is not recognized or I can see during the day the icon mounting sd even if I never touched it...

Never got this issue before jumping to kernel 3.0
[Samsung Galaxy S Relay 4G] shawndaivari:
Latest nightly pre 3.4

Does anyone have a link to the most recent nightly pre 3.4

I use it as my daily driver, and 3.4 is just a little to unstable for work.

Thanks in advance
[Samsung Galaxy S Relay 4G] DOMF:
Unstable how? My phone has been completely stable on build 246, and it's my daily driver.
[Samsung Galaxy S Relay 4G] misteropinion:
So, if you flash between the Nardholio and nightly builds, you may get into a situation where your phone crashes, usually while in the browser, sometimes as often as every 50 minutes or so. I fixed this by doing a factory reset from recovery and flashing a nightly (two days ago's). Stable as a rock, tho going in and turning off privacy guard on certain apps is tedious (like sundroid , so it could get my location, or Gmail so it could autocomplete recipients).

I have a last_kmesg from one of these crashes, but I'm not sure it's of any value (diagnosis: don't do that).

So, yeah, try that.
[Samsung Galaxy S Relay 4G] shawndaivari:
have the issues with bluetooth/wifi at sametime been straightened out?

also the front camera glitches?

those were the main ones that i had no problem with pre 3.4 that are keeping me from updating.
[Samsung Galaxy S Relay 4G] :
The test builds are not for general use. Flash with extreme caution.
[Samsung Galaxy S Relay 4G] misteropinion:
Oh, I know. This was the last AVS kernel that you had suggested, and I flashed away from it because of the charger problem. Even after doing a factory reset tho, I still get reboots on the nightly. I have two last_kmesg now, but I'm going to flash from 250 to 252 and see if that helps.
[Samsung Galaxy S Relay 4G] tylik:
I installed 252 last night. Generally, it looks good. But I'm getting an "insufficient storage available" error when installing a number of my most used apps. And considering that I have half a gig available, installing an 8mg app would strike me as that much of a stretch.

Including TuneIn radio, which I usually use when I'm running and on my commute (by bike) so this is likely to make me very sad indeed.

I'm in the process of installing 253, because hey, why not, but any clues for the clueless?
[Samsung Galaxy S Relay 4G] :
/data/ and /sdcard/ appear to share the same physical internal memory partition. It will not allow you to install any more apps when this falls below 500MB. This is not a bug.

Move your photos/music to an external SD. You can set the camera app to automatically save there as well.

New features in build 253

New charging code ported from the galaxy s4 (yes, really) with less kernel spam and compiles more cleanly. Still needs a few tweaks. No, your car charger still does not work. Get a better charger or short the d+ d- pins.

MMS sizes back to our pre d2-ones. Clear data on mms.apk (will not erase your text messages) and reboot before trying (also note this patch will not be in official cyanogenmod)

Extra gain in voice calls a bit quieter, but still plenty loud. This patch may not make it into official cyanogenmod either.

And this thread may be closing soon ;)
[Samsung Galaxy S Relay 4G] tylik:
I saw some notes about how to better utilize the partitions, and I'll try to look into that sometime in the next few days.

Even when I wiped all the user data and caches, after I'd installed the OS, I only had something like 516 mb of space available, so there really isn't anything much I can move. Nor am I clear on how to use standard disk utitilties on the internal memory (which is sad, because gparted would be awfully weclome.)

Am I doing something wrong here? That seems like relatively little space, but then plenty for what I was trying to do.
[Samsung Galaxy S Relay 4G] BinkyTClown:
i posted a workaround on the charging issue on an old build. i just checked and it works on the latest nightly.

1. turn your phone OFF

2. plug it in to the car charger

3. leave it plugged in and power it on.

as long as you leave it pluged in, it will stay charging.

i dont know why this works, but for me its reliable
[Samsung Galaxy S Relay 4G] tylik:
*facepalm* Yeah, never mind that last bit. That was a little more hidden than expect. Should be good to go now.
[Samsung Galaxy S Relay 4G] tylik:
Now that I've been using 253 for a few days -

Generally, this is really sweet. I am noticing that it will frequently drop my bluetooth headset and reconnect to it immediately (or less frequently, will need to be manually reconnected). And it does go through its battery, but that's been noted elsewhere.
[Samsung Galaxy S Relay 4G] BinkyTClown:
I started having sdcard issues when I moved to a newer build this week. Most of the time, the phone isn't seeing it at all. :(
[Samsung Galaxy S Relay 4G] Jason78729:
I like the new branch on github. Very curious and pleased.
[Samsung Galaxy S Relay 4G] misteropinion:
Is anyone else getting random reboots? Been going on for a while. I did a full wipe and flashed only nightlies from maybe 249 on. Is it worth it bringing in any last_kmsg dumps?
[Samsung Galaxy S Relay 4G] John5788:
just got one today for first time. I'm using 255 build.
[Samsung Galaxy S Relay 4G] :
Random reboots are indeed happening, and the error log from them is less than informative. You may email me logs at my name @ gmail dot com or put them on pastebin and post the link.
[Samsung Galaxy S Relay 4G] :
[MENTION=3552582]Jason78729[/MENTION]: ;)

[MENTION=3991690]BinkyTClown[/MENTION] , [MENTION=494880]scaltro[/MENTION] If you are having sdcard issues, try doing a battery pull for a minute, and then booting without the sdcard and then pop it in. I remember having the same issue with some of the newer builds and that's how I solved it.

Dumb chargers are fixed in build 258. If you are using a build between 253 and 257 you should upgrade ASAP regardless of the charger you are using, because the new charger code had a bug that will keep your charger on after the battery is full, something that you probably don't want.
[Samsung Galaxy S Relay 4G] tylik:
FWIW - I've been having sd card problems for the last couple of days. I just flashed 258, and powered down, pulled the battery, pulled the card, powered up, and reinserted the card. It is not insisting it is a blank or unreadable sd card and would like to reformat it for me. I haven't gotten around to digging out the converter so I can look at the card on one of my main boxen. Though prior to this when I attempted to look at the card it claimed I had insufficient privileges to do so. (And still does, but as the card is unmounted this seems a bit more explicable.)
[Samsung Galaxy S Relay 4G] BinkyTClown:
Thanks, I'm actually not getting that card to show up in my USB reader now. Unfortunately I don't have a spare to test with but I'll pick some up later this week.
[Samsung Galaxy S Relay 4G] :
Random reboots should be fixed in the latest builds. I blame d2 :p

Also there is a semi functional cm-10.2 build if you know where to look ;)

There is also an annoying new bug where it only draws 100 mA when charging over USB. We're looking into it.
[Samsung Galaxy S Relay 4G] stephenclower:
Awesome! Do you have any list of what works/what doesn't in the experimental 10.2 builds? I'm mainly after whether sound works. If so, I'll happily flash the build if you need a tester.

Thanks,

Steve
[Samsung Galaxy S Relay 4G] wedg11383:
I flashed it last night and used it briefly.

Sound worked. Wifi and data seemed fine. I could make calls and bluetooth worked.

The only issues I really noticed was the camera was really flaky. It only worked briefly before giving a can't connect to camera message. Also I had trouble with root access. After flashing, my apps couldn't gain root access. I was able to flash supersu binaries through cwm and it worked, but only through the supersu app, not through CM's built in interface. I couldn't get it to work with the superuser binaries.

Wifi and bluetooth still seemed to have issues when used simultaneous.

I hope this helps.
[Samsung Galaxy S Relay 4G] Xyro TR1:
Out of curiosity, does this ROM have Wifi Calling support packaged in?
[Samsung Galaxy S Relay 4G] orange808:
If you need wifi calling, you will have to stay on stock. For newbies, that means you won't be flashing a CyanogenMod rom. That's not unique to this device. The devs aren't letting you down, "being lazy", or ignoring you. It just isn't something you will find on CyanogenMod roms.
[Samsung Galaxy S Relay 4G] DOMF:
Just OOC, what's the technical reasoning for this?
[Samsung Galaxy S Relay 4G] crayz9000:
As a qualified response from someone who knows next to nothing about the WiFi calling process, I would hazard an educated guess that WiFi calling is a proprietary T-Mobile modification and that as such it falls outside the scope of CyanogenMod.

Having said that, there are debloated stock ROMs you can choose if you don't want all the other Samsung/TMo crapware.
[Samsung Galaxy S Relay 4G] stephenclower:
I'm running Nard's latest build from this morning, and so far nearly everything is working with the exception of wi-fi, and downloads over HSPA+ are very, very slow. Definitely not bad all things considered.
[Samsung Galaxy S Relay 4G] misteropinion:
I had one reboot still, I've had some issues with in call earpiece sound garbling (possibly tied to t-mobile visual voice mail app), and I'm having problems with onscreen notifications (like from su) not going away until. With the 31jul nightly.
[Samsung Galaxy S Relay 4G] stephenclower:
FYI, anyone wanting to try out CM-10.2 should use the 4.3 Gapps from here: http://xdaforums.com/showthread.php?t=2378992
[Samsung Galaxy S Relay 4G] killkillkill:
DO NOT use that gapps. Its borked. BADLY.

Use this one instead;

http://download.clockworkmod.com/gapps/gapps-jb-20130726.zip

Also, FORMAT your system partition before installing the 4.3 system image. CWM has an option in one of the menus for that.

If you've already installed the apple version of gapps, format system, reinstall system, and THEN install the good gapps.
[Samsung Galaxy S Relay 4G] stephenclower:
Interesting; they worked for me. There was another XDA thread with a tiny 17MB Gapps package that was definitely screwed up. Out of curiosity, what didn't work for you in the larger package from the 26th?
[Samsung Galaxy S Relay 4G] :
So, a funny thing happened to me the other day when I got Android 4.3 booting for the ApexQ. The S3 folks still hadn't gotten it booting and they said wtf. Then they said please ApexQ, can we have your code. And then a wonderous thing happened.

https://github.com/CyanogenMod/android_device_samsung_apexqtmo

We missed the release cycle for 10.1, plus I don't like coding for more than one branch at a time. Plus 10.1 is like, so last week man.

Nightlies will be shifted over to 10.2 from OFFICIAL CyanogenMod sources very soon. Official CyanogenMod nightlies will come out soon as well. And we will have official release versions whenever 10.2 is released.

They made us bump the MMS sizes back down. It'll be like this for awhile. Once official nightlies are out we'll start providing unofficial nightlies with user-requested features, and a few neat things like extra governors and whatnot. And maybe if we ask them nicely enough they'll let us have some of them officially.

So yeah...
[Samsung Galaxy S Relay 4G] janejunx:
Fun!

Just so everyone knows, GoSMS allows you to set custom MMS settings, including size, that persist through updates, if you needed a fix for MMS until we can do fun things again.
[Samsung Galaxy S Relay 4G] Jason78729:
Nard, words can't express my appreciation for your work. I Gabe up on porting governors due to instability and no noticeable differences with battery or performance.

I briefly switched to 10.2 but had to go back to 10.1 because I needed the reliability for some training at work. Since then I've been having issues with my text messages not going out at all. Messages received were fine and calls worked both ways. Now that my work issues are done I'll be switching back to 10.2 to start testing. Thanks for your awesomeness and I hope your as happy as I am that the S3 team needed the lil ole Relay for help. :D
[Samsung Galaxy S Relay 4G] Jason78729:
Anybody having issues with CM10.2 build #268 with Wifi. Not working at all for me. Lsmod doesnt list it as being loadeed and manually trying to insert the module fails with "insmod: 'prima_wlan.ko' failed (no such device)". Any guesses? For now going back to CM10.2 build #264.
[Samsung Galaxy S Relay 4G] noobnl:
gs3 is so last year. We are so lazy to fix the gs3. Most of my time is on the jf tree.
[Samsung Galaxy S Relay 4G] :
There's only one noobnl, and there's hundreds or thousands of people trying on the s3. I just exploited a timing loophole to inject my untrusted code ;)

(PS way to steal my thunder)
[Samsung Galaxy S Relay 4G] gutbomb:
I was using the July 30th build and noticing i was getting a lot of reboots when I use chrome. I just tried last night's build and once again, it reboots after a few minutes of browsing around in chrome. I tried the chrome beta as well but it's no different. The whole UI freezes for a few seconds, stops responding to touch, then the screen goes dark and then it reboots. It's not after a specific amount of time, and it's not on any specific web pages either. I'll gladly post any logs or anything else you need to try to fix this issue.

Edit:

It's actually not limited to Chrome. It seems to be happening with other apps in the foreground as well. Maybe a heat thing?
[Samsung Galaxy S Relay 4G] misteropinion:
This is the same failure mode I see. The logs i've looked at ***** about a paging failure in the wlan driver, then it panics and stops and restarts the hardware, but i think it's being caused by aliens. They're usually to blame.
[Samsung Galaxy S Relay 4G] Jason78729:
[MENTION=280224]nard[/MENTION], Correct me if this incorrect.

It looks like the nightly's are now all the CM 10.2 branch on the Jenkins site. As mentioned early in this forum if you flash the CM 10.2 builds you will need to also flash Gapps for CM 10.2/Android 4.3. Are we going to open a new development thread or just rename this thread and continue posting development updates or issues here? Thanks
[Samsung Galaxy S Relay 4G] chuckiev79:
I gave latest nightly a brief test run, and boots fine, but kept getting fc's on several apps like google movies and multiple wallpapers (live wallpaper) app. Also camera unable to connect. I downloaded 4.3 gapps. And updated everything. It seems fix permissions doesn't run through all apps. I tried to fix permissions with 3rd party app, and fc's seemed to calm down a bit, but did eventually return. I read on some other forums that camera has had similar problems on nexus and other devices.
[Samsung Galaxy S Relay 4G] misteropinion:
Can someone say which is the very last 10.1 nightly?
[Samsung Galaxy S Relay 4G] chuckiev79:
#263
[Samsung Galaxy S Relay 4G] gtmaster303:
I think I'll leave this here...

http://www.cyanogenmod.org/blog/this-week-in-cm-aug-0-2013

New Devices

This week, we introduced the following devices into our Github repo:

10.2 Compatible:

# Samsung Galaxy S Relay 4G (apexqtmo)

I always use the thanks button to decrease clutter, but I'll make one exception.

Nard and team you guys rock!
[Samsung Galaxy S Relay 4G] :
I'll start a new thread this weekend sometime. There's a few bugs with 4.3 but we actually have less bugs on a few things. In the meantime, don't flash anything until I post ;p
[Samsung Galaxy S Relay 4G] osnapitsjoey:
Could someone send me the link to the last good working 10.1?

Sent from a jail payphone
[Samsung Galaxy S Relay 4G] DOMF:
Well, in the list of builds on the Jenkins site http://ls.infernix.net/jenkins/job/apexq-staging/

There's one: http://ls.infernix.net/jenkins/job/apexq-staging/263/

That says at the bottom "Last known good cm-101 build. KEEP THIS."

It's probably that one.
[Samsung Galaxy S Relay 4G] osnapitsjoey:
Thanks my man, any reason why the wifi won't turn on?

Sent from a jail payphone
[Samsung Galaxy S Relay 4G] DOMF:
Mine wouldn't when I was using TWRP. If you're using TWRP, flash the recovery in that link.
[Samsung Galaxy S Relay 4G] osnapitsjoey:
Twrp? I used clock work mod recovery if that's what you're talking about

Sent from a jail payphone
[Samsung Galaxy S Relay 4G] Jax184:
Our CM rom currently doesn't work with TWRP. It's Clockwork or nothing right now.
[Samsung Galaxy S Relay 4G] osnapitsjoey:
That's what I'm using, wifis still not working though, any fixes?

Sent from a jail payphone
[Samsung Galaxy S Relay 4G] ToniCipriani:
I'm actually planning to do the Touchstone mod, and most accomplished this (on the EVO 4G and the Epic) by just pushing the 5V from the Touchstone coil onto the VBUS. So I suppose I will be affected by this?
[Samsung Galaxy S Relay 4G] :
Nah we fixed it.
[Samsung Galaxy S Relay 4G] ToniCipriani:
You guys are awesome. But I think I'm returning my phone... something's wrong with it. Keeps corrupting SD data, tried 2 SD cards already, same problem.
[Samsung Galaxy S Relay 4G] :
On stock or which build of CM?
[Samsung Galaxy S Relay 4G] ToniCipriani:
Plain stock 4.1.2, with some debloating. I just got this phone so wanted to test out everything before doing or flashing anything else.
[Samsung Galaxy S Relay 4G] BrainSlugs83:
Error 404?

Looks like http://ls.infernix.net/jenkins/job/apexq/ is down -- is there somewhere new we should be going to get the latest builds?
[Samsung Galaxy S Relay 4G] :
Official cyanogenmod get.cm
[Samsung Galaxy S Relay 4G] MikeChannon:
Closed at OP request.
[Fascinate Q&A, Help & Troubleshooting] skorp1982:
I have a verizon fascinate so its obviously cdma, is it possible to mod the phone somehow so that i could get it activated with telus or bell canada? since i live in canada the fascinate is pretty much an ipod touch
[AT&T, Rogers HTC One X, Telstra One XL] tyessen:
After reading countless threads about RUUing or OTAing to the 3.18 Jellybean software, I think I know what everything means. But just to be safe, I want to confirm some things before I try anything. I have never been on a stock firmware other than when I got my phone, and it came on the 2.20 ICS software.

1. I used the SuperCID method to unlock my bootloader. I've read that having SuperCID will screw up the update to jellybean. But, I've also read that having s-off will bypass the CID check when updating, making the update work normally.

My phone has a CID of 1111111 (SuperCID), and is also s-off. Does this mean if I flash back to a stock ICS rom and OTA up to jellybean, everything will be alright? After all of the info I've sifted through, my personal answer is 'yes, everything will work.'

2. If I do proceed with an update to JB, will I still have S-off and/or a root? I've looked at the facepalm s-off thread under the Original Development section, and see no mention of a compatibility or incompatibility with Jellybean. This is the first HTC device I've ever owned, so I'm not as familiar with s-off as some of you may be. I did find this from searching the s-off thread... http://xdaforums.com/showthread.php?p=38197741

If I recall correctly, I was running Viper XL when I s-off'd. It was a jellybean firmware at that time, probably built from the jellybean stock firmware. My personal answer to the question is 'yes, I will still be s-off, but I still don't know about a root.'

As far as a root goes, I'm at a loss of what to look for. I don't see a thread dedicated to a jellybean root, but then again, I'm not as well rounded with troubleshooting as others.
[AT&T, Rogers HTC One X, Telstra One XL] exad:
S-off will stick until you manually undo it. Whether you ruu, flash roms, whatever. Only way to lose s-off is to do fastboot oem setsecurityflag 3. Root is software so it's set within the rom. All the custom roms have root by default. With an unlocked bootloader any rom that doesn't have root can have root by flashing su. Consider root as having administrator on windows. If you don't have windows installed there's no administrative access to have right? Hence it doesn't stick but is built into the roms you flash.

S-off eliminates security checks so you you can ruu, flash anything and there won't be any checks that say hey, this isn't the right device or hey, this bootloader is unlocked, you can't ruu..

Just make sure not to flash anything not intended for the evita.

Hopefully this makes sense.

If you have any other questions, do not hesitate to ask.
[AT&T, Rogers HTC One X, Telstra One XL] tyessen:
Thanks, this pretty much answered all of my questions :) so if I just wanted a rooted stock rom, I would just follow the steps in the root guide that involve pushing and installing the su binary, and ignore the extra ones that involve changing the CID?

I can't seem to find any links to stock rooted for ICS (it's a preference to me over JB, sorry :P) anymore. My thoughts were to run the 2.20 RUU and root it, which seems like a valid option based on your response :)
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Ics is obsolete. If you really want stock rooted Ics.

You're correct.

Run an ics ruu

Flash twrp, flash su
[AT&T, Rogers HTC One X, Telstra One XL] redpoint73:
If the goal is JB, then I'd recommend the JB RUU, rather than the OTA. RUU is a much cleaner and problem-free install.

'yes, everything will work' is a bit too presumptive to me. You can never be sure that everything will be okay. Modding your phone always has its risks, even under the safest of circumstances. But S-off will prevent the particular case of a (virtually guaranteed) brick caused by installing the RUU or OTA with SuperCID + S-on.
[AT&T, Rogers HTC One X, Telstra One XL] tyessen:
I didn't mean everything as in it will be right out of the box, no errors or problems by that, sorry. I meant that the flash/RUU would complete successfully and I would be running a stock firmware again.

And like I said, I've never ran the official JB firmware, so I'll give it a try and see how the battery holds out. I know ICS had a much better life than other JB custom roms out there, but then again, custom means extra (most of the time).

So, maybe I'll just head straight for the jellybean RUU instead. My only concern is that the h-boot would update, and that sets off a little flag in my head with s-off problems (even though it was confirmed it would stay in place until I manually went back to s-on).