Related
I was wondering if it would be possible to use tasker to flick wifi off and on when wifi drops and/or 3g activates. Lately it seems on my phone that when I go out of wifi range and the 3g/4g connects the last wifi spot is remembered and almost acts like it is still in range causing issues when trying to connect to the next spot. I already installed the 7 day trial but haven't had as much time to research as I thought. Sound possible? Wasting my time?
rxnelson said:
I was wondering if it would be possible to use tasker to flick wifi off and on when wifi drops and/or 3g activates. Lately it seems on my phone that when I go out of wifi range and the 3g/4g connects the last wifi spot is remembered and almost acts like it is still in range causing issues when trying to connect to the next spot. I already installed the 7 day trial but haven't had as much time to research as I thought. Sound possible? Wasting my time?
Click to expand...
Click to collapse
What ROM are you on? I haven't had any of the problems like you describe since moving to Gingerbread.
Sorry, still stock. I keep thinking about flashing a rom but like others I am hoping for an official release soon with all the updates/leaks. Also this is my first android phone and I don't have total confidence in flashing it. For instance for whatever reason rooting using the "regular" method didn't work and had to use superoneclick. The latest rom thread also seems like a bit of a hodge-podge of things needed to get everything working....no disrespect intended to the individuals working on it.
Sent from my SAMSUNG-SGH-I997 using XDA App
rxnelson said:
Sorry, still stock. I keep thinking about flashing a rom but like others I am hoping for an official release soon with all the updates/leaks. Also this is my first android phone and I don't have total confidence in flashing it. For instance for whatever reason rooting using the "regular" method didn't work and had to use superoneclick. The latest rom thread also seems like a bit of a hodge-podge of things needed to get everything working....no disrespect intended to the individuals working on it.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Superoneclick is the "Regular" method for most people...
Infused 2.x had a few rough patches as he tried to integrate UCKI3/I4 stuff to fix the known issues with the Rogers release, but that has settled down as people have figured out what's broken in I3/I4 and what's not.
Serendipity VII is still stable, Mikey didn't rush to bring in the I3/I4 stuff. If you flash it, you'll have the following issues:
No audio on first call after boot - toggling speaker on/off will fix it (Hellraiser known issue)
No HDMI (won't see this until AT&T releases Gingerbread)
Data speed issues (However the Hellraiser beta9 kernel or my DD kernel may improve this - I am STILL waiting for someone in an area with good speeds to do an A/B comparison between old/new kernels.)
Camera limited to 15 FPS video - but you can flash the UCKI3 camera libs to fix this, there's a separate flashable package with its own thread in the dev section
None of the above bother me significantly (In fact as I live in the boonies and shoot with an SLR, the data speed and camera issues don't bother me at all), so I have been on S7 for a while.
In general you will find that there are VERY few people here running stock Froyo any more.
Good news is that if you screw up, Samsungs are VERY easy to restore to stock. Download mode (aka Odin/Heimdall mode) is awesome.
Entropy512 said:
Superoneclick is the "Regular" method for most people...
Click to expand...
Click to collapse
I guess that is where doubt started setting in about whether I should start flashing the phone or not. Both stickied root threads point to the rage against the cage method and one points to superoneclick being the old method. Thanks for all the info. I wasn't aware off the 30fps fix since I don't frequent the development threads. I honestly haven't had the time to do the necessary research if I get stuck so I have stayed stock.
Back on topic, I did get a chance to look up the some things in tasker and will try it out at work tomorrow since this is where it seems I have the most trouble. I'll post back if it works.
I was wondering if anyone is currently using Sean Z's Sky Ice Cream ROM and has used the NFC on the ROM? It says that the NFC is "limitted" working. I was wondering has any one used it with one or more of the NFC apps from the Android Market to read tags or transfer info? I Know "Google Wallet does not work because there is no SE on the SkyRocket (yet). I just wanted to know about the NFC abilities working with existing apps from the market without trouble.
I am asking because I am about ready to try out one of the ROMS other than "stock" and NFC is a must! I want to buy some NFC tags and start using them to launch tasks on the phone and transfer information. I think I have narrowed it down to the latest build of Alien or the Sky Ice Cream ROM. It just depends on which one seems more stable (including the stability of NFC). I am tired of waiting for AT&T to get off the pot and enable NFC on these phones. ISIS is supposed to be rolling out in a couple of select test markets this month so they (AT&T) could theoretically update the NFC capabilities on the Stock ROM at any time...but who knows? I have offered a decent donation to anyone that can enable NFC in the stock ROM and I am going to wait until that offer expires before I flash one of the ROMS mentioned above, but I don't think its going to happen on the stock ROM.
So, if anyone can give me some feedback on the issue I would appriciate it. Thanks.
I use sky ics. Along with a tag writer app by NXP Semiconductors. You can find it in the market by searching NFC in the market. Seems to work great
Sent from my SAMSUNG-SGH-I727 using xda premium
Is there any major milestone that must be overcome in order for the cyanogenmod team to officially support the HOXL? Are we just waiting for ROM cooks to take initiative? I know S-off is nice to have, but I don't believe it's a requirement.
No but kernel source would be required for jelly bean at the very least. And probably a little more developer interest.
Sent from my HTC One XL using Tapatalk 2
jordanetodd said:
No but kernel source would be required for jelly bean at the very least. And probably a little more developer interest.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
what's the deal with developer interest on the One X ? Is this not a popular phone or is it that most developers bought an international version?
Seems like ther'es been a fair amount of work as far as ROMS and mods and things go, but the Kernel source is the reason that there are working JB roms for the GS3 and we don't even have CM9 fully working yet....
I believe the developer interest come from a few factors.
1) There are few developers that get paid nothing and porting CM9/10 is a lot of work.
2) There are hundreds of devices how do you pick which one gets the CM9/10 .... sales.
The HTC One XL is a nice device but as a LTE device and from HTC it is likely not the strongest selling phone in North America
shorty6049 said:
what's the deal with developer interest on the One X ? Is this not a popular phone or is it that most developers bought an international version?
Click to expand...
Click to collapse
There's definitely more people on the One X international version. People will find that most phones with kernel source available and unlocked bootloader will draw more developers... But in this case quantity =/= quality. I've had several android phones over the years and yes, while it's nice to have a giant land of developers with pages and pages of roms to look through, they lose their luster to mediocrity. You'll find some of the best devs who weren't discouraged by the locked down devices such as this one, and as a result, the product (ROM, kernel, etc) will always be top-notch. And a smaller, more intimate dev community encourages more interaction and community support, making the overall experience that much better.
I think we already have pretty solid support, given that there's still no kernel source available.
We have great Sense-based ROMs (the CleanROM family, amongst others) as well as pretty-solid alphas of CM9 and AOKP. Personally I've been very tempted to try either CM9 or AOKP, but I haven't made the plunge yet. A friend of mine is using CM9 has his daily driver without issue.
I believe the team working on CM9 has plans to incorporate their currently-unofficial branch into being officially a part of CM9 (or CM10) once kernel source is released and the remaining issues are resolved.
Functioning CM9/10 is all i really want on this device. I don't need anything flashy. Just give these awesome devs the source kernel HTC!!!
The major milestone is kernel source. Without it, the devs can't squash some of these remaining bugs on our device. Without that, we won't get merged into the main branch (afaik). As to why there are more people on the international version, just look at what you just said. The INTERNATIONAL version. It's available on more carriers and yes, it is a heck of a lot easier to develop for since they didn't have to waste time trying to figure out how to unlock the bootloader (which makes them at least a month of ahead of us in terms of development) and they have source.
Trust me, once we have source, development will skyrocket.
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
pearlbrian said:
Functioning CM9/10 is all i really want on this device. I don't need anything flashy. Just give these awesome devs the source kernel HTC!!!
Click to expand...
Click to collapse
Our CM9 port is totally functional! Though...not 100%...but from what I've seen it's good enough for a daily driver. I'm running AOKP M6.2 and it's perfectly usable.
stnguyen09 said:
The major milestone is kernel source. Without it, the devs can't squash some of these remaining bugs on our device. Without that, we won't get merged into the main branch (afaik). As to why there are more people on the international version, just look at what you just said. The INTERNATIONAL version. It's available on more carriers and yes, it is a heck of a lot easier to develop for since they didn't have to waste time trying to figure out how to unlock the bootloader (which makes them at least a month of ahead of us in terms of development) and they have source.
Trust me, once we have source, development will skyrocket.
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
Our CM9 port is totally functional! Though...not 100%...but from what I've seen it's good enough for a daily driver. I'm running AOKP M6.2 and it's perfectly usable.
Click to expand...
Click to collapse
Sorry, i didn't mean functional. I meant, like you said, 100%.
pearlbrian said:
Sorry, i didn't mean functional. I meant, like you said, 100%.
Click to expand...
Click to collapse
yeah, my issue is that the few things that ARENT working are the things I want the most. Frustrating that this is as good as it can get unless HTC releases that source (which it's sort of staring to look like they may get away with not doing at all)
I think source will come. It's just sad that i have JB running on my old as bones Captivate while my shiny new one x is stuck with Sense :crying:
AOKP is great, very little doesn't work. It even has NFC. I have been using it for about a week. Very stable.
Sent from my HTC One X using xda premium
kleeman7 said:
AOKP is great, very little doesn't work. It even has NFC. I have been using it for about a week. Very stable.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
shorty6049 said:
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
Click to expand...
Click to collapse
If you connect your tablet through the wifi hotspot on your phone then you wouldn't need bluetooth right?
SkizzMcNizz said:
If you connect your tablet through the wifi hotspot on your phone then you wouldn't need bluetooth right?
Click to expand...
Click to collapse
Not quite sure what you mean,
The tablet would get Internet from my phone, then I'd use the tablet to stream music to my stereo via bluetooth
shorty6049 said:
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
Click to expand...
Click to collapse
From the AOKP thread:
What doesn't work:
Tethering (coming soon)
Panorama mode in Camera app
2G/3G switch (needs kernel source)
Same multitouch bug as CM (needs kernel source) <- When you have multiple touch points active and you remove one, the phone loses track of all of the others
Face Unlock
Other things may come up too depending on your specific situation (especially if you don't clear dalvik and cache or don't factory reset).
stnguyen09 said:
From the AOKP thread:
What doesn't work:
Tethering (coming soon)
Panorama mode in Camera app
2G/3G switch (needs kernel source)
Same multitouch bug as CM (needs kernel source) <- When you have multiple touch points active and you remove one, the phone loses track of all of the others
Face Unlock
Other things may come up too depending on your specific situation (especially if you don't clear dalvik and cache or don't factory reset).
Click to expand...
Click to collapse
Edit- I was looking at the wrong AOKP thread.
(for whatever reason, android beam doesn't seem to be working when I try it on milestone 6.2 though) I touch the phone to the tablet (both with NFC and android beam turned on) and nothing happens.
Tried it with a photo open as well to see if you needed content to beam . No luck
shorty6049 said:
Edit- I was looking at the wrong AOKP thread.
(for whatever reason, android beam doesn't seem to be working when I try it on milestone 6.2 though) I touch the phone to the tablet (both with NFC and android beam turned on) and nothing happens.
Tried it with a photo open as well to see if you needed content to beam . No luck
Click to expand...
Click to collapse
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
stnguyen09 said:
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
Click to expand...
Click to collapse
I got it to work using CleanRom (not a photo, it told me it didn't support receiving large files) . I might flash something new tonight... I really just want something that does wifi tether (which I'll have to read into more... I feel like it's tougher to get that feature working on this phone than it was on my Evo) and NFC (so I can automatically turn on tethering when I get in the car) . I'm alright using a sense-based ROM if I have to since anything is pretty fast on this phone and cleanrom is relatively AOSPish
stnguyen09 said:
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
Click to expand...
Click to collapse
Sending Photos only works on JB. With ICS you can you can send contact info and Youtube links. Works between CM9 on One X and my N7 running JB.
The GPS takes 5 minutes to lock, and it does it at 1600 meters (un)accuracy.
It behaves like this no matter what rom i try (Sky, Slim, CM9/10, Embryo etc), except for stock Rogers ICS.
The agps patch and other gps patches on XDA didn't do anything.
When i first bought it, it had stock Rogers ICS and GPS worked perfectly, never mind the fact that i live in EU.
Then i tried custom roms and it started to funk around and has been doing as long as i run a custom rom.
Today i installed Rogers ICS as a last resort and suddenly the GPS locks in seconds and with great accuracy too (9 meters).
And so the question, what the hell is causing this?
OR
How do i make the GPS work with the custom roms?
I have been running custom ROM's since a day after I got my Skyrocket, and the AGPS patch has never failed to work for me. I have been running CM10 for pretty much the last 4+ months, and GPS always works. Not sure what your issue might be.
You can flash agps patch from Boombah's aroma installer. Always works for me
------------------------------------------------------------------------
Sent from my Skyrocket i727 w/ Blinky'sRevenge
-----------------Nexus 7 running AOKP M1-----------------
rpr69 said:
I have been running custom ROM's since a day after I got my Skyrocket, and the AGPS patch has never failed to work for me. I have been running CM10 for pretty much the last 4+ months, and GPS always works. Not sure what your issue might be.
Click to expand...
Click to collapse
I'm not sure either.. The phone is canadian with a Rogers brand on battery cover. When i install a stock AT&T rom the GPS more or less dies.
Any other rom and the GPS dies. Stock Rogers ICS rom and voila works like a clockwork.
And it doesn't react at all to any GPS patch, and i've tried like 10 different ones. aGPS is not new to me, i've successfully used it on other phones. But for some reason it doesn't do anything for my Skyrocket.
Mike on XDA said:
You can flash agps patch from Boombah's aroma installer. Always works for me
------------------------------------------------------------------------
Sent from my Skyrocket i727 w/ Blinky'sRevenge
-----------------Nexus 7 running AOKP M1-----------------
Click to expand...
Click to collapse
Thanks i'll try that, just don't see how Aroma is going to help if it's the same patch i've tried earlier.
On the other hand, with ghouly issues like this who knows what might help and what won't ?
Worst case scenario is that i'll be stuck with Rogers FW if i want working GPS, which is acceptable with some tweaks especially the Droid Razr M launcher
The thread is here: http://forum.xda-developers.com/showthread.php?t=1732304
--------------------------------------------------------------------
Sent from my Skyrocket i727 running Team Dirt
--------------Nexus 7 running AOKP PUB--------------
Did u by any chance leave location access for Google apps disabled? If u did on AOSP ROMs GPS will never lock
icenight89 said:
Did u by any chance leave location access for Google apps disabled? If u did on AOSP ROMs GPS will never lock
Click to expand...
Click to collapse
Nope, it's always turned on.
If SW doesn't solve/change anything - where might the problem be? Yes, that's right, it's probably in HW!
Check your GPS antenna contacts (antenna is inside the inner plastic, the one you see when you open back cover and remove the battery). Bend them a bit and clean their contact points to make sure they contact well.
If your phone is still within warranty or the above doesn't help - replace it.
Jack_R1 said:
If SW doesn't solve/change anything - where might the problem be? Yes, that's right, it's probably in HW!
Check your GPS antenna contacts (antenna is inside the inner plastic, the one you see when you open back cover and remove the battery). Bend them a bit and clean their contact points to make sure they contact well.
If your phone is still within warranty or the above doesn't help - replace it.
Click to expand...
Click to collapse
Hi Jack_R1
Software does indeed solve everything. In short: stock rogers ics rom = perfect gps, custom rom/stock at&t rom= no gps.
Oops. Guess I skipped some lines reading the OP - returned and found your line talking about it. Sorry about that.
Did you try reinstalling custom ROMs after you got quick lock on stock ROM, to test that the issue remains?
I'd suggest a couple of things:
1. Try installing AT&T ICS ROM for testing. If it also gives you a good lock - you'll have better reference point.
2. Look at the APN you use in Rogers' ROM and in other ROMs. If you're using automatic ones - they might be different and include GPS-related stuff (type "supl").
3. Copy stock gps.conf from Rojers and try using it on custom ROMs.
4. Download FasterFix and try choosing different NTP pools.
5. Download GPS Status & Toolbox, see what exactly happens when you run it, describe here. What satellites are you seeing (numbers), how much time after running it, in which condition, etc.
Jack_R1 said:
Oops. Guess I skipped some lines reading the OP - returned and found your line talking about it. Sorry about that.
Did you try reinstalling custom ROMs after you got quick lock on stock ROM, to test that the issue remains?
I'd suggest a couple of things:
1. Try installing AT&T ICS ROM for testing. If it also gives you a good lock - you'll have better reference point.
2. Look at the APN you use in Rogers' ROM and in other ROMs. If you're using automatic ones - they might be different and include GPS-related stuff (type "supl").
3. Copy stock gps.conf from Rojers and try using it on custom ROMs.
4. Download FasterFix and try choosing different NTP pools.
5. Download GPS Status & Toolbox, see what exactly happens when you run it, describe here. What satellites are you seeing (numbers), how much time after running it, in which condition, etc.
Click to expand...
Click to collapse
1 The AT&T roms didn't give me an adequate lock, until the JB updates were leaked & released.
2 I'm always using automatic APN's but they don't have any GPS info.
Haven't tried #3..
4 FasterFix didn't help.
5 GPS Status shows 4-7 satellites and only 2-3 locks with horrible accuracy. The thing is now i get perfect locks with any ROMs.. I could've disallowed Google Services to use GPS as I might've confused it with Google Search & Ads wanting my location..
Thanks for your help :good:
hi..
i'm getting this phone since i was tired waiting for the JB port for the captivate glide (and i mean a port which actually works with bluetooth phone), plus, i see that it seems to have a faster processor, and actually official support for JB) still i don't understand why it's considered low activity legacy device. (i don't care much about the camera, at most i just do portal submission to google. )
Um, not to be rude, but where's the question? lol
It's specs are rather mid-range, the keyboard is very niche by now.. so it's a low activity device due to its low popularity?
why it's considered low activity legacy device?
is no one using it?
emaayan said:
is no one using it?
Click to expand...
Click to collapse
it's a niche device. far less popular than the big names like galaxy s3/s4, htc one, xperia z etc etc
so is the captivate glide i assume...
and yet it has it's own forum..
Braccoz said:
it's a niche device. far less popular than the big names like galaxy s3/s4, htc one, xperia z etc etc
Click to expand...
Click to collapse
emaayan said:
and yet it has it's own forum..
Click to expand...
Click to collapse
uh, yes, and this is relay's own. doesn't really matter where they put it...
We didn't choose to put the device here. The mods did.
We're lucky to even have a forum. Despite the fact that low end phones which you've never heard of got forums before they even launched, the mods decided that the Relay was not popular enough to have one. Even once we had a booting CM9 ROM. After 6 months of complaints, they finally gave us one. But they put it here.
Previously we were squatting in another device's forum, so this is an improvement.
but it still looks better then the captivate glide..
i mean it has an OFFICIAL jellybean, and i'm assuming someone made it a stock rom of jelly bean. it has a better processor even.
what i don't understand is why do you even NEED a section of low activity devices, i mean it's not like you don't have enough ROOM on the internet like a library or something.
emaayan said:
i mean it has an OFFICIAL jellybean, and i'm assuming someone made it a stock rom of jelly bean. it has a better processor even.
what i don't understand is why do you even NEED a section of low activity devices, i mean it's not like you don't have enough ROOM on the internet like a library or something.
Click to expand...
Click to collapse
Well, I don't know what you'd have us do about it. No one here had anything to do with the decision, or possesses the power to change it.
Jax184 said:
Well, I don't know what you'd have us do about it. No one here had anything to do with the decision, or possesses the power to change it.
Click to expand...
Click to collapse
Aye, and to your earlier point we worked hard to get us our own little space.
Had the device gotten it's own forum at launch or before it, popularity would be higher... but that's a cause and effect issue that's long past debating.
Woot.
We got a forum!
~Running CM10.1
emaayan said:
is no one using it?
Click to expand...
Click to collapse
It's just less popular. The phone quite good actually.
Well like I said , I gave up on it: ( wish I could use it.
Sent from my SGH-I927 using Tapatalk 2
I'm going to try something outrageous and attempt to whore this thread to ON topic ..
I'm thinking about swtiching from the captivate glide for the same reasons, i want a jellybean phone with working bluetooth and a physical qwerty keyboard.
How do you relay 4g owners find the keyboard vs. the glide ? easier to type?
How are the cases, number row easy to access?
How are the Rom's ... Fully working, issues ??
I'm pretty comfortable with my phone but i've never been "in love" with teh keyboard like I was on a blackberry.. .i find the keys are too spaced apart and too big for typing without looking at the keyboard.
speed performance etc are great.
camera spec shows 5mp camera vs. 8mp. How are the quality of the pictures vs the glides ??
Thanks much!
my impression were (i've ditched it and returned to glide)
the keyboard does seem easier to type, and glide buttons seem harder to press, i keep getting my fingers stuck in the middle between the keys. the numbers row are easy access cases seem solid.
roms however are a problem, i'm talking about the stock roms as i havn't been able nor to root, or intstall a rom. there seems to be a wifi issue that keeps getting the phone disconnected and re-connected, making internet connection impossible, initially i thought it might be my AP acting up, but the glide didn't have any issues. only the relay.
another main problem, is that performance, or lack of it. to tell you the truth , i didn't notice any difference, in fact it might have been more sluggish then the glide. this off course might have been an issue with all the bloatware i couldn't uninstall not being root, however i noticed that with jellybean you specify disable on each service, and that might have been helfull.
my attempts at doing root, failed. i tried using CWM, (there seems to be only one version for this phone) however this particualr cwm fails at installing everything else on signature verification message. in other cwm mods, and twrp you can disable signature verification, but they are all being installed with cwm (not odin flashable).
in the end i tried re-flashing the rom with JB, and ended up with wel..not a brick, but ever since then, i can't seem to dial out. there internet seems to be working over the sim card, but not dialing. i'm not sure if i should get another phone to try again, as there doesn't seem to be much support, actually i didn't even see any "bare boned" rooted stable non-alpha roms for this thing yet (or ever be). like the glide has.
as for the camera, i realy don't think there's a difference between 5 and 8 mp, i didn't see any difference.
in short, hardware the phone seems fine, however the rom ,root, etc.. lack of it) doesn't seem to be very common, as of know i'm not sure if i should get another one and try again, or hold off and see if it dies.
yohan4ws said:
I'm going to try something outrageous and attempt to whore this thread to ON topic ..
I'm thinking about swtiching from the captivate glide for the same reasons, i want a jellybean phone with working bluetooth and a physical qwerty keyboard.
How do you relay 4g owners find the keyboard vs. the glide ? easier to type?
How are the cases, number row easy to access?
How are the Rom's ... Fully working, issues ??
I'm pretty comfortable with my phone but i've never been "in love" with teh keyboard like I was on a blackberry.. .i find the keys are too spaced apart and too big for typing without looking at the keyboard.
speed performance etc are great.
camera spec shows 5mp camera vs. 8mp. How are the quality of the pictures vs the glides ??
Thanks much!
Click to expand...
Click to collapse
I moved to this phone from the samsung epic. I loved that phone and wanted something similar so I got the relay on a whim. I was able to root and install cm with little trouble. The keyboard is nice but I think the droid 4 keyboard feels nicer. My fiancee has the droid 4, however, and the phone has had many problems with it. Some chargers do not fit well in port, thus not charging the phone. Also the phone gets really hot and read somewhere sometimes this melts stuff inside, thus phone not charging the phone as well. Overall relay is boss, although I rooted and flashed everything before official jb update. So not sure what that entails. The new kernel is still iffy for me. Getting "...not responding" messages for several apps stock and otherwise, but running 6.19 build and everything is smooth.
Sent from my SGH-T699 using xda premium