yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] Jax184:
I've been using the new JB ROM for a few hours now and have found a quirk or two.

When manually adjusting the brightness, sometimes the screen takes on a blue tint. Like, things that should be a dark blue become much brighter. This goes away if I tweak the brightness back and forth a few times.

I rooted the ROM using the CWM+flashable root file from previous ROMs. It worked, though last night I kept getting "radio is requesting superuser access" until I restarted the phone. I don't know what that was about. Hopefully it doesn't happen again.

The compass is STILL misconfigured. Every time you boot the phone, it needs to be recalibrated before it has any idea which way is up or north.

No idea what you mean. Got a picture?

---------- Post added at 12:48 PM ---------- Previous post was at 12:12 PM ----------

Okay, so we may have something a little deeper here. Today I'm seeing the "radio is requesting Superuser permissions" dialog again and again. I'm unsure what this means, but as a wild-ass guess, it may be the ROM checking to see if the phone has been rooted. This could be bad for people out there who still have their warranties.
[Samsung Galaxy S Relay 4G] burbs:
I can't seem to get a screen shot, but it's like what you'd expect the hard drive LED to do when accessing data. I've looked up different "solutions" through Google, and it seems to be a developer's mode attribute, but I turned it off. One person says to uncheck the strict mode setting, which hasn't worked.
[Samsung Galaxy S Relay 4G] burbs:
Well, whatever it was, it's done doing its thing now. As the day went on, the red flashing border appeared with less frequency. Throughout this morning I didn't experience it at all. Maybe it was some type of optimization thing going on?
[Samsung Galaxy S Relay 4G] conspirator.of.crisis:
Tethering

So Jax184 are you tethering on the JB ROM on Wind somehow or are you waiting for the tethering fix like Braccoz? I am on Wind as well and want to keep running the JB ROM but need to be able to tether on pretty much a constant basis.
[Samsung Galaxy S Relay 4G] Jax184:
I'm waiting on tethering as well.
[Samsung Galaxy S Relay 4G] conspirator.of.crisis:
Thanks - I just wanted to make sure I wasn't missing something - guess that means I'm going back down to LJ1 until we get tethering!

---------- Post added at 09:47 PM ---------- Previous post was at 09:30 PM ----------

Now I'm in trouble - I got distracted while trying to go back to LJ1 and ended up applying the LJ1 tethering fix to the JB ROM. Phone rebooted and got stuck on the screen with SAMSUNG with the pulsating blue background and just wouldn't go further. Got back in through ODIN and flashed back down to the LJ1 ROM but again when the phone reboots it is still stuck on the same screen. Did I just brick it? Anyone got any suggestions as to how I can get back up and running on *ANY* ROM?
[Samsung Galaxy S Relay 4G] conspirator.of.crisis:
Alright so it turns out that I didn't screw it up - the problem is that I just can't seem to downgrade. If I clear the cache in recovery and then flash the BMC5 (ie JB) image the phone will come back up running 4.1.2. However when I clear the cache and flash any other image (LJ1, LH1, etc) the phone just gets stuck on the SAMSUNG screen (and I've left it sit there for as long as 10 minutes to make sure it isn't actually doing anything).

The only reason to downgrade though for me is that I need to tether. Hence faced with this problem I started going through all the Wifi Tether apps (that I tried before the tethering patch was out for the previous versions and none worked) and discovered the FoxFi works. It seems to override the T-Mobile tethering restriction in that when it is active the normal Mobile Hotspot icon appears (as well as the FoxFi icon) in the notification bar and when you pull it up it shows as On with the devices connected listed. Using FoxFi isn't as elegant as just using the built-in software hence I'll hobble along with the new image and FoxFi but still hopes that someone is kind enough and smart enough to figure out a tethering fix for this image.

Anyone got any comments or suggestions?
[Samsung Galaxy S Relay 4G] gee one:
Does anyone have the OTA update from TMO? I was going to make a flashable stock jelly bean rom, and the updater script is useful.

If you received the update and didn't apply it, it should be in the cache partition. PM me if you need help pulling it out.

sent while running with scissors
[Samsung Galaxy S Relay 4G] tany.jags:
Wouldn't this help?

http://xdaforums.com/showthread.php?p=40591848#post40591848
[Samsung Galaxy S Relay 4G] gee one:
That is the full rom, I was looking for the actual OTA update because I wanted to look at the updater-script.

Here it is:

http://rapidshare.com/files/1683651545/update_mc5_7bda365f.zip

7bda365f9db8d24235b22787ed0c560c update_mc5_7bda365f.zip
[Samsung Galaxy S Relay 4G] Nardholio:
Does GPS work on the new stock rom for you guys?
[Samsung Galaxy S Relay 4G] Nardholio:
You need to wipe everything, data, system, cache in order to downgrade from JB to ICS. Also wifi is likely to be broken due to the new JB over writing the persist partition. Someone who is still on ICS and who is rooted should probably keep a copy of that.
[Samsung Galaxy S Relay 4G] gee one:
I'm having some gps issues and radio is requesting superuser access. This is on rooted,debloated jb with the jb radio.

Let me know if you need logs, data, or want me to flash something.

sent while running with scissors
[Samsung Galaxy S Relay 4G] conspirator.of.crisis:
JB downgrade to ICS + GPS

Thanks for the info Nardholio! I guess that means I'm staying at JB then. Overall I'm happy with it and having no problems perse. However to address your specific comment about GPS, although I haven't had any issues with it I have noticed that it has taken up to 5 minutes to fully sync and get a position lock now. I hadn't attributed that to the upgrade necessarily though as this happens from time to time as being way up here in Calgary Alberta sometimes satellites aren't as easily visible as they could be and this happens occassionally with all of my GPS receivers. My old G2 used to have quite a lot of problems that way. Haven't noticed anything about root requests though as Gee One indicated.
[Samsung Galaxy S Relay 4G] Braccoz:
does making a cwm backup cover that, and all other stuff needed too?
[Samsung Galaxy S Relay 4G] gee one:
I flashed to JB using the system from kies dump and the OTA. I noticed that the symlinks in the OTA changed and are linked to the system partition, not persist. I didn't flash the sbl/rpm/aboot files.

Here is what is currently in my persist directory. Is there supposed to be more?

shell@android:/ # ls -R persist/

persist/:
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
dsps
lpass
modem
qcom
wcnss

persist//dsps:

persist//lpass:

persist//modem:

persist//qcom:
softap

persist//qcom/softap:
hostapd_default.conf

persist//wcnss:

---------- Post added at 06:32 PM ---------- Previous post was at 06:18 PM ----------

Another odd piece- the OTA includes patches for radio, aboot.mbn, rpm.mbn, sbl2.mbn, and sbl3.mbn, and tz.mbn.

The 400MB system dump also includes a cache partition and the persist partition, but the persist partition is empty.
[Samsung Galaxy S Relay 4G] :
As promised, the JB tethering fix. Untested since I don't run stock. https://dl.dropboxusercontent.com/u/103520801/Relay_tetheringfix_MC5.zip

Here is a list of other potential mods, although there are tons out there, and quite a few of them will work for our phone. http://xdaforums.com/showthread.php?t=1621289

Interested developers can pm me and as long as it isn't 100 people I will show you how to do it. I use a mix of Windows and Linux based tools for development. Specifically I run Linux in a vm under Windows. If you don't have access to both I can give you pointers but I won't be able to show you step by step.
[Samsung Galaxy S Relay 4G] :
Here is the file we're using to fix GPS on the CM-10.1 builds. I don't know if it will improve your performance on stock. Let me know. This is CWM flashable.

https://dl.dropboxusercontent.com/u/103520801/Relay MC5 GPS fix.zip
[Samsung Galaxy S Relay 4G] orange808:
https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2

Here's a handy app. Tell it to download gps assistance data for you. It helps.
[Samsung Galaxy S Relay 4G] conspirator.of.crisis:
Yeah I actually have it installed and have tried that and it doesn't seem to help much. With the G2 there were days I was pretty much at the end of my rope and tried just about everything to facilitate a lock - this was one of the better tools though. Thanks for the info!
[Samsung Galaxy S Relay 4G] janejunx:
Did a flashable modem ever happen? I haven't found one in my search yet.
[Samsung Galaxy S Relay 4G] orange808:
I hear the new radio is asking for superuser permissions..

You may not want it...
[Samsung Galaxy S Relay 4G] gee one:
Nardholio posted a radio in the development thread.

http://xdaforums.com/showpost.php?p=40755825&postcount=232

Something is asking for superuser permissions.

Here is dmesg | grep ^radio

<3>[ 2059.594170] init: sys_prop: permission denied uid:1001 name:sys.media.vdec.sw
<3>[ 2060.271203] init: sys_prop: permission denied uid:1001 name:ro.setupwizard.mode
<3>[ 2060.492110] init: sys_prop: permission denied uid:1001 name:sys.media.vdec.sw
<3>[ 2061.118785] init: sys_prop: permission denied uid:1001 name:ro.setupwizard.mode
<3>[ 2061.358369] init: sys_prop: permission denied uid:1001 name:sys.media.vdec.sw
<3>[ 2061.979673] init: sys_prop: permission denied uid:1001 name:ro.setupwizard.mode
<3>[ 2062.199480] init: sys_prop: permission denied uid:1001 name:sys.media.vdec.sw
<3>[ 2062.774118] init: sys_prop: permission denied uid:1001 name:ro.setupwizard.mode
<3>[ 2063.004455] init: sys_prop: permission denied uid:1001 name:sys.media.vdec.sw
<3>[ 2063.671814] init: sys_prop: permission denied uid:1001 name:ro.setupwizard.mode
<3>[ 2063.897756] init: sys_prop: permission denied uid:1001 name:sys.media.vdec.sw

here is ps | grep radio

radio 183 1 36608 2868 ffffffff 40114320 S /system/bin/rild
radio 184 1 10428 1992 ffffffff 40112320 S /system/bin/sec-ril
radio 201 1 4828 1080 ffffffff 400e7cb8 S /system/bin/at_distributor
radio 202 1 17548 412 c0202650 410abcb8 S /system/bin/diag_uart_log
radio 206 1 21696 1036 ffffffff 40172cb8 S /system/bin/qmiproxy
radio 207 1 26932 1088 ffffffff 40107cb8 S /system/bin/qmuxd
radio 565 1 25140 1444 ffffffff 40139ca4 S /system/bin/netmgrd
radio 587 1 23712 1424 ffffffff 40125a70 S /system/bin/cnd
radio 1001 192 521512 41464 ffffffff 400ffa70 S com.android.phone
radio 11005 201 876 448 c010820c 400f1500 S sh
radio 11006 11005 1008 516 c0185bb4 40044320 S dumpstate
radio 12540 12539 434292 18404 ffffffff 4010f320 S app_process

These last three weren't running earlier when it wasn't asking for superuser permissions.

I'm using the new radio/modem and tz.mbn file with a rooted, debloated, tether-fixed, system.
[Samsung Galaxy S Relay 4G] gee one:
I uploaded a relatively untested, rooted, debloated stock version of the new jb. It's the mc5_rooted_debloated... file.

Edit: fixed link! Sorry

ftp://75.98.172.214/

88d359fcc99667d15addcdcd870093c5 mc5_rooted_debloat_tether_88d359fc.zip

This is the full rom, not an ota. I would guess you can flash this over stock ics, but wipe cache and data if you are currently on cm10.

There is a weird issue with "radio" asking for superuser permission. It seems to happen once per reboot, and I've never granted it. I think any app signed with the samsung radio key will have the same uid, so it's probably not the actual radio. maybe....

I also changed the boot splash logo to a slightly different android picture. If there is a version 2, I'll change it back to stock.

Here are the files I removed. This list is more aggressive and some things will have to be downloaded from the market.

AmazonShopping_TMO.apk
BonusApp_TMO.apk
Evernote_tmobile_TMO.apk
FBAndroid.apk
Lookout_TMO.apk
MobileLifeContacts_TMO.apk
SlackerRadio_TMO.apk
SNS.apk
Telenav_TMO.apk
Vvm_TMO.apk
YahoonewsDaemon.apk
YahoonewsDaemon.odex
YahoonewsWidget.apk
YahoonewsWidget.odex
YahoostockDaemon.apk
YahoostockDaemon.odex
YahoostockWidget.apk
YahoostockWidget.odex

Cozi-tab-tmobile-prod_TMO.apk
com.mobitv.client.tmobiletvhd.apk
Highlight_TMO.apk
ECID-release_TMO.apk

IQ-tmobile-release-unsigned.signed_TMO.apk
IQToggle.signed_TMO.apk
system/lib/libiq_service_tmobile_2.2.so

Dropbox.apk
DropboxOOBE.apk
MusicPlayer.apk
MusicPlayer.odex
Magazines.apk
MediaHub.apk
YouTube.apk

Music2.apk
GMS_Maps.apk
Gmail.apk
Street.apk
PlusOne.apk
VideoPlayer.apk
VideoPlayer.odex
Videos.apk
Books.apk

SecCalendar_NAmerica.apk
SecCalendar_NAmerica.odex
DeepSea.apk
DeepSea.odex

S-Voice_Android_phone.apk

SecMemo.apk
SecMemo.odex
SecMemoWidget.apk
SecMemoWidget.odex

VoiceRecorder.*

AccuweatherWidget.odex
AccuweatherDaemon.apk
AccuweatherWidget_Main.apk
AccuweatherDaemon.odex
AccuweatherWidget_Main.odex
AccuweatherWidget.apk

TetheringProvision*

/system/media/audio/ui/Power On/Off ogg/wav (power on/off sounds)

sent while running with scissors
[Samsung Galaxy S Relay 4G] :
Gee one, it's interesting you flashed the tz by itself without the sbl. The tz validates the sbl partitions for boot or the device refuses to boot (although our bootloader isn't locked, so it might just display a warning or something if you had modified sbl)

I flashed the entire new tar before returning to cyanogenmod, and one thing is interesting. The bootloader continues to be unlocked but the sbl now sets the flash counter on boot if the recovery/kernel is modified. Previously I was able to clear the flash counter with Triangle Away. I can still do this, ie I can run Triangle Away and then power down and immediately go into Download mode and it shows 0 flashes and official status, but if I then boot the phone and run Triangle Away again the flash counter says 1 again.

Whereas before once I cleared the flash counter it stayed

I like your idea of just flashing the system partition. There's absolutely no reason to take sbl updates.
[Samsung Galaxy S Relay 4G] gee one:
Ahh, that explains why my flash counter is 25 and climbing.

I was never sure what the tz.mbn file did, but it didn't seem to hurt.

I updated the ftp link 2 posts up.

Edit: I unflashed the tz.mbn file and gps seems better and I don't get the radio superuser requests. Thanks Nard!

sent while running with scissors
[Samsung Galaxy S Relay 4G] onebornoflight:
OK so I tried to download the link you posted above, Gee-One, and it won't download over my phone's browser - it comes up as "website does not exist". Am I gonna need to be on a PC and right click/save target as? Or is the link now bad?

I want to update to JB but I don't wanna take the OTA and risk losing root or anything, or deal with the radio asking for superuser permission every boot. Is there a process established to go from the UMVA2 rooted rom with matching Modem/Baseband to stock rooted JB, or are we playing by ear still?
[Samsung Galaxy S Relay 4G] gee one:
yeah, it's odd that that mobile browsers interpret it as an http link?

It should work from a PC.
[Samsung Galaxy S Relay 4G] Jax184:
Can you summarize for a noob like me what you did that resulted in radio shutting up? It's been really bothering me!
[Samsung Galaxy S Relay 4G] gee one:
I'm not 100% sure that it is fixed. I did get some requests, but I was flashing back and forth between roms today.

I flashed the tz.mbn file from the uvma2 update before the jb update. There were no sbl updates prior to this, so they should be matching? Maybe.... ish....

After restoring to stock jb and reflashing the previous tz.mbn file, I haven't gotten any requests. GPS seems to work too, once it is calibrated and after the initial lock. It seems to stay locked for longer periods of time too (more than a minute).

Edit: hold the phone!!! If I had the previous tz.mbn flashed, wifi and bluetooth would not work. So now, it's the lesser of 2 evils.

sent while running with scissors
[Samsung Galaxy S Relay 4G] CrunchBangPow:
OTA Install

I don't know if i lucked out or what but I went ahead and installed the OTA successfully and did not lose root. All I got was a message from CWM recovery v6.0.2.8 asking if i wanted to install the unsigned update and then after about 5 minutes it finished, asked if i wanted to attempt to fix the recovery, and rebooted. Rebooted into JB still rooted, tested out root explorer, rebooted a few times and back into CWM. No issues and root still remains. Is this version of CWM that resilient? Usually every OTA i've tried before had made me loose root.
[Samsung Galaxy S Relay 4G] gee one:
I couldn't get the ota unless I was on stock system and recovery. Edit: re-read.

Let us know how it is behaving. My issues seem to be gone, but it's just one data point.

sent while running with scissors
[Samsung Galaxy S Relay 4G] maximumentropy:
radio superuser

I'm not the OP but maybe this will help you.

I replaced Superuser with SuperSU about two or three days ago, and haven't seen one of those messages since. I was also getting some random reboots, which stopped around the same time. There is a CWM flashable zip available which will remove Superuser automatically, or you can install from the market and then remove Superuser.apk (e.g. with a root file explorer).

Cheers,

entropy
[Samsung Galaxy S Relay 4G] orange808:
That really doesn't clear it up for me...

First of all, security through obscurity is no security at all. You are free to choose any app to manage your device that you like, but you might want to reconsider your choice...

Getting back directly on topic..

Is SuperSU blocking the requests and just not showing you any toasts? What do the logs say?
[Samsung Galaxy S Relay 4G] maximumentropy:
Why reconsider my choice? Are there known issues with SuperSU that I should be aware of? The reviews in the Play Store are overwhelmingly positive.

There is nothing about radio in the SuperSU logs, just ES File Explorer and Titanium Backup.
[Samsung Galaxy S Relay 4G] burritoboy9984:
Just wanted to say, I was on stock rooted with CWM, and as posted a few before, I simply downloaded the update via the android's update service, went through the stock process of updating and CWM saved itself and root.
[Samsung Galaxy S Relay 4G] crosscoder:
Has anyone that has upgraded to JB had any issues with the Continuous Input (Swype-like) function on the Samsung Keyboard? Since updating, that particular feature no longer works for me.
[Samsung Galaxy S Relay 4G] reju:
Soft bricked? After attempted upgrade to JB

Hi, I was running stock rom UVMA2 unrooted. I had applied the LJ1 tether fix and all worked perfectly for me.

Now I have just tried to upgrade to JB stock rom from the link given by Nardholio. But the Odin 3.07 flashing failed after it tried to write the system.img.ext4.

(BTW why do we always have to rename to .tar from .tar.md5 after extracting the rom zip file?)

So on reboot the yellow triangle with exclamation mark inside and saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again", shows up.

Kies could not connect to my mobile. But I could Odin flash CWM and manage to boot back to Odin mode or CWM recovery mode.

So then I tried to flash the old stock rom LH1, but again Odin encountered problem while writing system.img.ext4.

Now after 2-3 attempts the Odin gets simply stuck at writing system.img.ext4. It does not show any error. I have waited for 30 mins to see if there's any progress, but no luck!

Does Nardholio or Gee One or anyone have any idea what's going on here? I am saying soft bricked as I can still boot to both recovery options...

Thanks!
[Samsung Galaxy S Relay 4G] reju:
Soft bricked? After attempted upgrade to JB

I just remembered that I had tried to upgrade to JB with Odin3 v1.7 and not Odin3 v3.07 which had worked for me earlier.

Maybe this was the cause of the failed upgrade.

Now I am trying to flash with Odin3 v3.07 only and I am getting stuck as mentioned above.

Hope this helps!
[Samsung Galaxy S Relay 4G] reju:
Soft bricked? After attempted upgrade to JB

Trying to flash with old stock rom LH1

ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> boot.img

<ID:0/003> NAND Write Start!!

<ID:0/003> cache.img.ext4

<ID:0/003> NON-HLOS.bin

<ID:0/003> recovery.img

<ID:0/003> system.img.ext4

Gets stuck here :(
[Samsung Galaxy S Relay 4G] :
Get a new USB cable
[Samsung Galaxy S Relay 4G] reju:
Soft bricked? After attempted upgrade to JB

You are amazing :) That simply solved my problem!!

I have now upgraded to JB.

And I didn't know that I would have to root again.. I was under the impression that only OTA update will require re-root.

I wonder if a rooted phone I can update directly thru OTA? It did start downloading and I had cancelled it....maybe next time.?

Thanks Nardholio! :)
[Samsung Galaxy S Relay 4G] reju:
GPS/ Physical Keyboard issues

Hi, this fix did not work on my stock JB. It gave error "Unfortunately, locationServices has stopped. (OK)". If you click "ok" the phone resumes activity and this same message pops again in 3-4 secs. This loop continues on and on... Phone becomes literally unusable. Can we un-install this? I went for reflashing the rom.

Otherwise the stock GPS was not able to get location even after 15 mins..I gave up. So is there a bug here?

I also noticed that Physical Keyboard (sec keyboard) is set to "default" and we could change it to "US English" etc., but no way I could it get back to "default"? Needs a hard reset?

I happened to change "US English" and all the "alt" keys (except .com) stopped working!..

Thanks.
[Samsung Galaxy S Relay 4G] kilr00y:
i remember that dilemma on my dz. there's no option for "default".. but if i remember correctly you can simply uncheck the "US English" and it goes back to default.
[Samsung Galaxy S Relay 4G] reju:
Yes, that works for me. Thanks!
[Samsung Galaxy S Relay 4G] kilr00y:
anybody happens to have an recovery-flashable zip for stock? (or am i too dumb to find it?)

the ftp link to the debloated rom from gee one doesn't work for me..

i'd like to avoid the odin-messing-around... but need to try out some things on stock.
[Samsung Galaxy S Relay 4G] stephenclower:
The FTP link to the rooted JB ROM also does not work for me. Since I am blind and can't read the device's screen when it boots into CWM, is there an alternate way I can flash superuser to regain root access? I plan on returning to CM-10.1 now that I've played with the stock JB.
[Samsung Galaxy S Relay 4G] anon_az:
When doing this, did CWM complain about an invalid certificate on the update.zip? Did you just move ahead regardless with no ill effects?
[Samsung Galaxy S Relay 4G] burritoboy9984:
Yup, exactly right.

-Erik
[Samsung Galaxy S Relay 4G] anon_az:
So you're still rooted? Are you getting any of the issues others are seing with Radio requesting root or the like? I'm trying to get where you are (4.2 with root) and want to be sure I'm minimizing my chances of hitting issues. Thanks!
[Samsung Galaxy S Relay 4G] saurabhsaurabhrai:
Plz helpn me guys...

I have rooted my galaxy relay 4g but still running the stock rom 4.0.4....Now i want to update my phone to latest JB stock firmware....and i'm a rookie in this thing....Ned experts help....

Also...I'm using unlocked phone....my phone will be locked again if i'll update????

And I'm very sorry if i have posted in wrong thread...!!!!
[Samsung Galaxy S Relay 4G] Jax184:
The phone will remain unlocked if you update. In my experience, the easiest way to upgrade is to first restore the stock ROM using something like Odin, then update the normal way and re-root after.
[Samsung Galaxy S Relay 4G] saurabhsaurabhrai:
thanks jas...its a great relief to know that my phone will remail unlocked to all cariers as i'm using it here in Indian.....

But i'm already on stock 4.0.4 but rooted and i have downloaded the update file linked above.....

how can i install the update noe...as i'm unable to unroot my stock 4.0.4...

if u can help me to do that...I'll be very thankful...regards