Galaxy S Relay 4G Development Thread

Search This thread
By:
Advanced…
Joe333x

Joe333x

Senior Member
Oct 6, 2009
1,070
123
So it seems my thread questioning about anyone getting the Relay has turned in the the Dev thread for it since for some reason XDA doesnt want to make a thread dedicated to it. I personally ended up buying a Note 2 which is why I dont follow this thread anymore but I just recieved a PM saying the thread was moved so I figured I would change the title of the thread from "Any one planning on getting the Galaxy Relay 4G" to "Galaxy S Relay 4G Development Thread".
 
Last edited:
Joe333x

Joe333x

Senior Member
Oct 6, 2009
1,070
123
debork said:
Definitely looking into a replacement for my G2, haven't really seen anything convincing thusfar. With a S4, this just might do it.
Click to expand...
Click to collapse

Thats what im thinking. I hope that the rumor of a 5mp camera is wrong and it ends up being an 8mp but even if it is a 5 as long as it has a good sensor and flash ill be happy. So far it seems it will basically be a Galaxy S3 with a 4" screen and a QWERTY minus 1GB ram which really doesnt matter. Ive never owned a samsung before but i guess they are really easy to root with a program from samsung called odin. Hopefully CM will be supporting it.
 
Dukenukemx

Dukenukemx

Senior Member
Jul 24, 2008
1,151
52
Jersey
Either way, it could be the next best upgrade for Desire Z owners. Especially with so many discouraged people with HTC and their policy's. They can keep them, and their phones. No ICS update, not even for related phones where we could bum the driver over. Not to forget how locked down the phone is. Plus Samsung phones are more consistant.
 
Joe333x

Joe333x

Senior Member
Oct 6, 2009
1,070
123
Dukenukemx said:
Either way, it could be the next best upgrade for Desire Z owners. Especially with so many discouraged people with HTC and their policy's. They can keep them, and their phones. No ICS update, not even for related phones where we could bum the driver over. Not to forget how locked down the phone is. Plus Samsung phones are more consistant.
Click to expand...
Click to collapse

Yeah Samsung seems to be the way to go these days. HTC locks their bootloaders, both HTC and LG dont provide updates, Sony phones are just not even close to the competition. Samsung provides the ODIN program so you can do what you please with what you paid for plus it seems they are providing pretty decent updates with the S2 and Note both year old devices getting Jelly been. Where my year old G2x is still on GB.
 
G

g1user101

Senior Member
Apr 16, 2010
1,658
99
OC
Only if confirmed specs come out. Some new phones that aren't super popular are getting outdated specs like the new mytouch lines by huawei
 
Joe333x

Joe333x

Senior Member
Oct 6, 2009
1,070
123
g1user101 said:
Only if confirmed specs come out. Some new phones that aren't super popular are getting outdated specs like the new mytouch lines by huawei
Click to expand...
Click to collapse

Yeah those new mytouch phones phones had been rumored for awhile now and the specs of them were outed well before they even came out i mean really a single core phone? Where going to be seeing quad core phones in the states soon
The only tmo mytouch that wasnt terrible was the first one. I had the slide and it was ok but had a locked bootloader and the genuis button is so stupid, never would buy another mytouch. I was really hoping that those rumors of a G3 were true but hopefully this Relay will turn out to be a great phone.
 
austriker27

austriker27

Senior Member
Feb 2, 2010
482
36
Hot dang that looks promising! Although I do love my g2 it'd be nice to have decent specs

sent from my rocking HTC G2 loaded with ICS
 
B

biohazrd51

Senior Member
Apr 26, 2011
492
180
I'd rather pierce my lip with a rusty nail than use a keyboard made by Samsung.

Or Touchwiz for that matter, at least that mistake of an interface can be fixed with another ROM. Just sayin.
 
Joe333x

Joe333x

Senior Member
Oct 6, 2009
1,070
123
biohazrd51 said:
I'd rather pierce my lip with a rusty nail than use a keyboard made by Samsung.

Or Touchwiz for that matter, at least that mistake of an interface can be fixed with another ROM. Just sayin.
Click to expand...
Click to collapse

The keyboard looks nice to me, who knows how it will feel since no one has tried it yet. I agree with the touch wiz but im hoping cm will support it.
 
B

biohazrd51

Senior Member
Apr 26, 2011
492
180
HTC keyboards are the only ones I've liked. The spacing, depth of key press, and layout are the only ones that I've cared to use. Everything else I've tried feels like I'm using something cheaply made.

Sent from my Nexus 7 using xda premium
 
T

thepaddedroom

Member
Apr 23, 2009
37
0
I think I'll wait for October. That's when my G1 & G2 came out. If October comes without any solid information on a G3, then I'll migrate over to whatever the next Nexus device might be.
Sent from my HTC Vision using xda premium
 
Dukenukemx

Dukenukemx

Senior Member
Jul 24, 2008
1,151
52
Jersey
Either way I'm waiting for my T-Mobile contract to end. Once that happens, I'm going to give T-Mobile a decision to make. Either give me a new phone of my choosing, or I switch carriers. A lot of my friends do this, and they end up with a brand new phone, like Samsung Galaxy S3's, but they're out of contract and desperate to keep you in it.

Carriers tend to give new contracts better deals for phones then those who just got their upgrade. Also, there's a lot of other carriers who offer a lot more for less then the big US carriers.
 
Joe333x

Joe333x

Senior Member
Oct 6, 2009
1,070
123
thepaddedroom said:
I think I'll wait for October. That's when my G1 & G2 came out. If October comes without any solid information on a G3, then I'll migrate over to whatever the next Nexus device might be.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse

Idk man id love to see a G3 as much as anyone else here but I dont see it happening especially with the stupid G4x thats going to be coming to tmobile. It wouldnt make sense for them to release a phone named G4x and then a phone named G3. G4x will be just as garbage as the G2x, it will have awesome hardware and a quad core but will have no software support from LG or NVidia.
 
A

agazza

Senior Member
Nov 21, 2011
282
16
Do you guys think it will work in sweden? Then someone needs to send me one. Htc can **** off now. To bad i dont like samsung build quality and feel. To plasticky

sent from phone
 
M

mruwek

Member
Jun 30, 2012
20
4
With Swype beta I don't really need physical QWERTY anymore. I'm just waiting for next nexus phone(s).
 
You must log in or register to reply here.

Similar threads

J
[root]Samsung Galaxy S Relay 4G
Replies
55
Views
69K
B
bs27975
N
[CM-10.1] Galaxy S Relay 4G/SGH-T699 NIGHTLIES
Replies
463
Views
69K
robuser007
robuser007
T
HOW TO: Free Unlock of Samsung Galaxy S Relay 4G - At your own risk!
Replies
82
Views
55K
B
bs27975
racosta201045
[root]\{cm9} samsung galaxy relay 4g (updated 11/19)
Replies
90
Views
31K
C
Chrizuki
N
[CM9][ALPHA]Galaxy S Relay 4G [12/8]
Replies
184
Views
30K
Casper Young
Casper Young

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 17
    N
    Nardholio
    Don't bother with that cm10.1 build. It's good but it's not that great. Something a *lot* better is coming down the pipe in a day or so. Let's just say that literally 15 minutes ago the cameras were fixed by lbcoder. And the Android 4.2.2 code upstream has evolved a lot in the last week. There's no longer any tearing in the display. I'd say you should have it in about 24-48 hours.

    Also, there will be no cm10.1 release thread. xda won't give us a forum, so **** em. We're in talks with cyanogenmod to get the Relay officially added to cyanogenmod. That'll show them we don't need no steenking forum.

    Sent from my SGH-T699 using xda premium
    View
    14
    Jax184
    Jax184
    Samsung Galaxy S Relay 4G Hardware Guide

    Normally I'd have posted this as its own thread, but given that we still don't have our own forum, I guess it'll have to be here.

    I've only had my Relay a week and already it's been torn apart! But what's bad for warranties is good for you, because now I can make a hardware reference guide for this phone like I did for the Sidekick 4G.

    As before, this is a work in progress and based on my own research. I'm not an expert on cell phone tech, so everything here is provided with no warranties. Please let me know if you notice any mistakes and I'll be happy to update this document. I'm particularly interested in better documentation for the various components, like in-house PDFs.

    Samsung Galaxy S Relay 4G Specifications:

    Released as T-Mobile exclusive on September 19th, 2012.
    SGH-T699
    FCC ID: A3LSGHT699

    2G Network: GSM/GPRS/EDGE – 850, 900, 1800, 1900 MHz
    3G Network: UMTS/HSPA+ – 850, 900, 1700, 1900, 2100 MHz
    WiFi: 802.11A/B/G/N dual-band 2.4/5GHz
    Bluetooth 4.0
    Near Field Communication

    CPU: 32-bit 1.5GHz dual-core Qualcomm Snapdragon S4 (ARM V7 Architecture)
    GPU: Qualcomm Adreno 225
    RAM: 1 Gigabyte DDR2
    Flash: 8 Gigabytes, ~5GB available to user under stock ROM
    MicroSD slot for expansion

    Display: 4" Samsung SuperAMOLED screen @ 800x480 with Multi-Touch Capacitive Touchscreen. 16,777,216 colours
    Keyboard: 5 row 52-key QWERTY keyboard with inverted-T arrow keys

    Rear Camera: 5 Megapixel with LED flash
    Front Camera: 1.3 Megapixel

    Other Features:
    Augmented GPS/GLONASS
    Accelerometer/Gyroscope
    Compass
    Light sensor/Proximity sensor
    Mobile High-Definition Link (HDMI)

    Size: 4.96" x 2.56" x 0.53"
    Weight: 5.6 Ounces
    Power: 1800mAH Lithium-Polymer rechargeable battery model EB-L1K6ILA with NFC antenna integrated.

    http://downloadcenter.samsung.com/c...y_S_Relay_4G_English_User_Manual_UVLG8_F4.pdf - User manual

    http://www.jax184.com/projects/Relay 4G/Draft Users Manual.pdf - Early draft of user manual, submitted during FCC approval.


    Hardware Details:

    T3i_1180bs.jpg



    0. Qualcomm MSM8260A Integrated Snapdragon S4 CPU, Adreno graphics core, UMTS modem, WiFi/Bluetooth backend, GPS/GLONASS receiver, DSP and USB controller
    Marked:
    Unknown
    (Located under RAM IC as package-on-package)

    1. Qualcomm WCD9310 "Tabla" Audio codec
    Marked:
    WCD9310
    NCM218R1
    A228002
    13

    2. Silicon Image SiI9244 MHL Transmitter
    Marked:
    SIMG
    9244BO
    NCS371A
    10L2230

    3. Samsung 8Gb (1GB) Low Power DDR2 DRAM
    Marked:
    Samsung 210
    K3PE7E700D-XGC2
    GKB2709U

    4. Samsung 8GB NAND Flash
    Marked:
    Samsung 228
    KLM8G2FE3B-B001
    HHGX259X

    5. Qualcomm HSPA+/CDMA2K/TDSCDMA/EDGE/GPS Transciever
    Marked:
    WTR1605
    OVV
    PHX403R1
    AA22501

    6. Qualcomm Dual-band Wi-Fi A/B/G/N, Bluetooth and FM Radios
    Marked:
    WCN3660
    PGW541R1
    A222002

    7. Unknown
    Marked:
    SWt
    GAD92

    8. Anadigics Multimode Multiband Power Amplifier Module
    Marked:
    ALT6181
    33945AC
    1231PH

    9. Anadigics AWT6624 UMTS1700 Power Amplifier
    Marked:
    6624R
    4233AD
    1230 PH

    10. Anadigics AWT6622 UMTS1900 Power Amplifier
    Marked:
    6622R
    4110AA
    1228 PH

    11. Invensense 6050 six-axis gyroscope/accelerometer
    Marked:
    Invensense
    MPU-6050M
    D2G554-K1
    EI 1226 D

    12. Qualcomm Power Management IC
    PM8921
    AD35130
    f3228004

    13. Analog Devices Mobile I/O Expander and QWERTY Keypad Controller
    Marked:
    ADP
    5587
    #215

    14. Texas Instruments BQ24157 Lithium-Ion Battery Charger
    Marked:
    TI27A3JXI
    BQ24157B

    15. NXP PN544 Near Field Communication Controller
    Marked:
    44501
    10 05
    NXD2314

    16. Atmel MaXTouch mXT224E
    Marked:
    MXT224E
    MAH-IR0
    2W1315B


    http://www.jax184.com/projects/Relay 4G/Internal Photos.pdf - Photos of a prototype Relay submitted to the FCC for approval. Notice that the PCB, RF plate, keyboard frame and even the back cover have all been revised.

    http://www.jax184.com/projects/Relay 4G/Test Results.pdf - Results of FCC testing of the NFC radio.


    Take Apart:

    T3i_1115s.JPG


    Start with the phone turned off.

    T3i_1116s.JPG


    Flip the phone onto its back and remove the battery, SIM card and MicroSD card.

    T3i_1125s.JPG


    Remove the 8 long screws around the edge of the phone and the two short screws in the battery bay using a fine-tipped Phillips screwdriver. Be sure not to mix these screws up when reassembling!

    T1i_7794s.JPG


    If available, use a thin nylon guitar pick for this next step. Metal tools will mar the plastic.

    T3i_1131s.JPG


    Unlike most Galaxy S devices, the seam between the inner back and the front case of the Relay 4G is not visible from the back of the device. Instead it is on the front, around the perimeter of the keyboard. Insert a thin prying tool here and gently unsnap the plastic halves.

    T3i_1136s.JPG


    Lift the back off.

    T3i_1152s.JPG


    Gently disconnect the headphone jack cable. This connector is very fragile, and should not be pried on with metal tools. Instead it should be gripped with fingernails and slowly pulled upward.

    T3i_1147s.JPG


    Disconnect the screen cable along the left side of the board. Like the headphone jack, this connector is fragile and must not by forced apart. Then remove the 5 short screws which hold the PCB to the front frame.

    T3i_1161s.JPG


    Gently lift the PCB upwards. There are clips around the edge which will need to be gently pressed to free the board.

    T3i_1167s.JPG


    If needed, the keyboard can now be removed. To separate the keyboard frame from the screen, remove the final screw and gently pull the plastic straight up. Be sure not to put undue stress on the screen cable. It is held to the keyboard frame in the gold plate, which is attached using double-sided tape.

    I did not dismantle the screen section of my phone beyond this point, but further disassembly appears to be straight forward.

    T3i_1176s.JPG


    To continue dismantling the PCB, gently disconnect the camera and MicroSD card socket cables. As above, these connectors are delicate and must not be forced apart.

    T3i_1170s.JPG


    Remove the two screws on the keypad side of the PCB to unfasten the RF plate.

    T3i_1178s.JPG


    Lift the RF plate off of the PCB.

    T3i_1180s.JPG


    The PCB is now bare.

    Assemble in reverse order.



    The PDFs linked to in the above document are owned by their respective companies. All else is covered by the following:

    View
    14
    N
    Nardholio
    http://db.tt/xjAvIRPT Tethering fix for MA2 stock
    http://db.tt/iEfsXunl MA2 baseband if you're on CM and care to upgrade. Samsung radios almost always offer no improvements and there's no difference I can see.
    http://db.tt/tsZc9hLA Odin flashable version of a newer CWM, fixes folder layout problems on CM10.1
    http://db.tt/n3woOEN1 CWM flashable version of a new CWM.
    http://db.tt/mPiKehtD A surprise :D

    Sent from my SGH-T699 using xda premium
    View
    12
    N
    Nardholio
    My dropbox was suspended for excessive bandwidth, so I'm mirroring this on Google Drive too

    Stock Odin file, pulled from Kies
    https://docs.google.com/open?id=0B1lS6BTmOE55V3BJSXRMbkpBTE0

    Odin
    https://docs.google.com/open?id=0B1lS6BTmOE55TV8yU0o3bm5lelE

    Rooted system image, flashable with Odin
    https://docs.google.com/open?id=0B1lS6BTmOE55VHlDcmlJUWVmcDg


    The reason the rooted system image is so much larger than the original is it's a direct dump from the phone, so it includes all the empty space on the partition.

    If you want to play around while someone compiles a CWM for this phone, it is true what they said, you can flash the SGSIII CWM and it will allow adb access but no on phone video. I also had to go into my Device Manager to manually set the driver as a Samsung adb device because I don't think the Samsung drivers are updated just yet. You can flash the stock Odin to get back to regular recovery and it would be trivial to create an Odin flashable version of just the recovery.

    Far easier to just flash the rooted system. If you get FC after flashing, clear cache and/or factory reset.

    Standard disclaimers apply, your warranty is now void, I am not responsible if you create a brick, back up your efs before messing around, etc etc etc
    View
    12
    kornyone
    kornyone
    ohhai!

    I am Jason Parker (kornyone from Github/Freenode/other places) from the G+ posts mentioned here. I was the one with RIL and made the post CM shared on G+/Twitter. Part of the reason they shared it is... I am already in the team maintaining the HTC Doubleshot. After more hardware failures than one should ever experience on the Doubleshot, I am finally abandoning that phone as my daily.

    I began training at a new job and was out of town for six weeks. During those six weeks, I picked up this Radar 4g/ApexQ to be my new daily. It exceeded my expectations -- faster HSPA, better battery life (stock atleast), operated with the msm8960 core nicely, and the BT has amazing range. I just didn't have the ability or time to hack it for many weeks... and it drove me crazy.

    I came home from training the same weekend as the BigAndroidBBQ (this last weekend) and I knew I was jonesing to hack this phone, even though I have numerous other projects on my plate (HTC Doubleshot, Nexus Q, personal and professional stuff, family life, etc).

    Rather than initially reinventing the wheel, I decided to use noptys's github repos. I was able to build a stable CWM from his jellybean branch. It worked well. I was off to the races.

    I found their IRC channel (#apexqtmo) at that time. I told them what I was up to, and someone suggested I try the ICS branch. I did so, posted screenshots. I then came home after work (I work second shift ATM), and started working on pieces of the source to fix the many core non-functional components.

    I fixed the RIL inadvertently, without any noticeable side effects, using the stock Samsung kernel source code/defconfig (apexq_rev02_defconfig). I previously was using noptys kernel ICS branch. Not only was RIL working, but I was pulling sick speeds (for T-Mobile anyways). Something I could not do on the Doubleshot (it topped out 3-5mbps/down, the apexq was reaching 10-16mbps down on average).

    I have not had a chance to dive into it more.

    BTW, I have not abandoned the HTC Doubleshot for CM. It's on hiatus. It's my wife's go-to daily driver and 3 months old (before T-Mobile killed it off in the stores). The ApexQ is my current daily... once I get audio and BT working again :)

    ---------- Post added at 12:11 AM ---------- Previous post was at 12:10 AM ----------
    originalgabriel said:
    okay, this is getting old ... We need a damn forum!

    We have root, we have a custom recovery, we have a dev (who just got working ril on cm9!) but we don't have a forum!?!

    Sent from my htc vision using xda app-developers app
    Click to expand...
    Click to collapse

    +1,000,000,000
    View

New posts