yellow tint to screen compared to ATT version? - One (M7) Q&A, Help & Troubleshooting

I was one of the impatient people that tried to cancel their order for the developer edition (sent an email) and ran out on Friday morning and bought the ATT version. The next I noticed that orders were being shipped (mine being one of them). Long story short, I rented the ATT one for the $35 restocking fee for the weekend and now have my dev. edition in my hands.
I noticed one person mention a yellow tint to thier screen, and when I compared my phone to the ATT, sure enough it was very apparent. I have heard and come up with a few reasons why looking around online. I want to get your thoughts on what is causing this, if it will go away and if you can see it in yours. With that said I compared to my wife's S3 and it is still a load better than her screen in every way.
1. The phone was just recently built and the glue is still drying - not sure if I buy that one but it is a theory
2. Defective screens - could be, but I would think that would be easy to spot in any quality control process... no dead pixels that I can see (or stuck) but a uniform yellow tint across the entire screen
3. Could it be the ATT software tweaks that make thier's whiter? I almost feels like the "temperature" of the screen has just shifted toward a yellow / warm. Could this be the default screen settings and ATT actually did something GOOD to the phone rather than just installing apps, etc. Do they even have this ability?
Either way - I am going to keep the developer phone. If it is glue it will dry, if it is defective I will wait for stock to build up and exchange with LetsTalk, and if it is something ATT did, I will wait for a custom ROM to allow me to configure the settings.
Curious to everyone else's thoughts... and if they notice the same thing (or are able to compare to T-Mobile, etc)

pennektj said:
I was one of the impatient people that tried to cancel their order for the developer edition (sent an email) and ran out on Friday morning and bought the ATT version. The next I noticed that orders were being shipped (mine being one of them). Long story short, I rented the ATT one for the $35 restocking fee for the weekend and now have my dev. edition in my hands.
I noticed one person mention a yellow tint to thier screen, and when I compared my phone to the ATT, sure enough it was very apparent. I have heard and come up with a few reasons why looking around online. I want to get your thoughts on what is causing this, if it will go away and if you can see it in yours. With that said I compared to my wife's S3 and it is still a load better than her screen in every way.
1. The phone was just recently built and the glue is still drying - not sure if I buy that one but it is a theory
2. Defective screens - could be, but I would think that would be easy to spot in any quality control process... no dead pixels that I can see (or stuck) but a uniform yellow tint across the entire screen
3. Could it be the ATT software tweaks that make thier's whiter? I almost feels like the "temperature" of the screen has just shifted toward a yellow / warm. Could this be the default screen settings and ATT actually did something GOOD to the phone rather than just installing apps, etc. Do they even have this ability?
Either way - I am going to keep the developer phone. If it is glue it will dry, if it is defective I will wait for stock to build up and exchange with LetsTalk, and if it is something ATT did, I will wait for a custom ROM to allow me to configure the settings.
Curious to everyone else's thoughts... and if they notice the same thing (or are able to compare to T-Mobile, etc)
Click to expand...
Click to collapse
Well I'm not owning a HTC phone, but I had a yellow tint issue with my Xperia S(it happened to the fresh new ones, just after it was launched, some said the same thing you said at 1. (glue still drying), but the effects are still visible now, and the phone is 1 year old already. So, it may be something similar here. I am sorry for not being able to confirm as I don't have the phone, but I'm giving some info...

Pictures??
Sent from my GT-I9300 using xda premium

mine looks normal to me

kkk121 said:
Pictures??
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I am not sure if these really do the difference justice... but it is clear a day when side by side in person.

pennektj said:
I am not sure if these really do the difference justice... but it is clear a day when side by side in person.
Click to expand...
Click to collapse
The Dev edition is Warmer while the ATT is cooler. I can clearly see the difference. I'll have to compare the dev edition when it arrives tom to the T-mobile version.

I have an AT&T version and a 32GB unlocked and the color temperature of the 32GB unlocked is definitely a little warmer. I don't have any professional instruments so I can't measure the white point and tell you whether the AT&T version is too cold or the unlocked version is too warm, but honestly, if I didn't put them side by side, I don't think I would have noticed.
As to the cause, it could be simple device to device variance. Maybe some AT&T versions have a warmer color temperature as well. Or maybe the AT&T is using a panel from a different manufacturer. Or it could be the firmware. The AT&T version is running 1.26 and the unlocked version is on 1.29 with a slightly newer kernel. Maybe the warmer temperature is part of the newer software and the AT&T version will be that way too when it gets the update. Who knows.

I got the 32 gb unlocked today and it looks cooler like the att version in the pictures

There was a thread posted before talking about how the htc one may have different screen manufacturer's. So some may have a Samsung screen, other sharp etc etc.
Sent from my HTC One using xda premium

Related

[Q] Marks on screen in low light

I got my GSM Dev Edition last week and in the last few days I've noticed dark, asymmetrical streaks that almost look like scratches or claw marks in the bottom left quarter of the screen. These only show up on dark blue/gray backgrounds (such as the dialer and settings screens) and in low light - such as in the dark - I noticed it when i play around with it in watching TV in bed. I cleaned the display thoroughly to rule out dirt and oil, and I also noticed the marks don't show up in screenshots. My wife has a Verizon Moto X, and she doesn't have the streaks, but I did notice a few dark dots/spots that appear in similar situations.
I called Motorola, and even though I unlocked the bootloader, they will give me an RMA and evaluate the phone, but I'd have to ship it and then wait 7-10 business days to get it back. I was hoping they might say they'd just exchange it so it'd be a quicker process.
Is anyone else noticing something like this, or notice it now that I've pointed it out (sorry!)? Since I dropped close to $700 on this phone, it should be perfect, so it's hard to "unsee" it now even if it is borderline (or flat-out) nitpicking. But it doesn't affect functionality or even viewing in normal lighting, it doesn't show up on any other colored screens, and I really don't want to have to send my phone away and be without it for probably 3 weeks minimum. I've never had an issue with any phones or devices before where I've had to send them back for warranty repair or evaluation. Anyone have any advice or thoughts on this? Is it worth my time? Thanks!
mohlsen8 said:
I got my GSM Dev Edition last week and in the last few days I've noticed dark, asymmetrical streaks that almost look like scratches or claw marks in the bottom left quarter of the screen. These only show up on dark blue/gray backgrounds (such as the dialer and settings screens) and in low light - such as in the dark - I noticed it when i play around with it in watching TV in bed. I cleaned the display thoroughly to rule out dirt and oil, and I also noticed the marks don't show up in screenshots. My wife has a Verizon Moto X, and she doesn't have the streaks, but I did notice a few dark dots/spots that appear in similar situations.
I called Motorola, and even though I unlocked the bootloader, they will give me an RMA and evaluate the phone, but I'd have to ship it and then wait 7-10 business days to get it back. I was hoping they might say they'd just exchange it so it'd be a quicker process.
Is anyone else noticing something like this, or notice it now that I've pointed it out (sorry!)? Since I dropped close to $700 on this phone, it should be perfect, so it's hard to "unsee" it now even if it is borderline (or flat-out) nitpicking. But it doesn't affect functionality or even viewing in normal lighting, it doesn't show up on any other colored screens, and I really don't want to have to send my phone away and be without it for probably 3 weeks minimum. I've never had an issue with any phones or devices before where I've had to send them back for warranty repair or evaluation. Anyone have any advice or thoughts on this? Is it worth my time? Thanks!
Click to expand...
Click to collapse
In case anyone cares, after talking with them again, Motorola is letting me straight-up return the phone (even with unlocked bootloader). Then I'm just going to turn around and buy another new one - or perhaps even save a few hundos and get a gently used AT&T or T-mobile version (I like this phone so much as-is that I feel like I don't even need the unlockable bootloader). Why it can't just be an outright exchange where I send them this phone and then they ship me out another, I have no idea. At least the marks will be gone after going through this trouble..
mohlsen8 said:
In case anyone cares, after talking with them again, Motorola is letting me straight-up return the phone (even with unlocked bootloader). Then I'm just going to turn around and buy another new one - or perhaps even save a few hundos and get a gently used AT&T or T-mobile version (I like this phone so much as-is that I feel like I don't even need the unlockable bootloader). Why it can't just be an outright exchange where I send them this phone and then they ship me out another, I have no idea. At least the marks will be gone after going through this trouble..
Click to expand...
Click to collapse
Yes! I have them as well. I didn't even know how to describe them until I saw your post. White AT&T model. I filed a warranty claim through AT&T and they are sending me out a replacement. I thought about just letting it go since they are basically not visible unless it's a gray type background but just knowing they are there erks me to no end.
capathy21 said:
Yes! I have them as well. I didn't even know how to describe them until I saw your post. White AT&T model. I filed a warranty claim through AT&T and they are sending me out a replacement. I thought about just letting it go since they are basically not visible unless it's a gray type background but just knowing they are there erks me to no end.
Click to expand...
Click to collapse
Yeah seriously, I couldn't stand seeing them anymore, and this morning was prepared to ship my phone away for 3 weeks to have it repaired. I'm glad they're just letting me return it. It feels tainted to me and I want a perfect one, especially for full retail price. Glad to know I'm not alone.
If anyone else is looking for them (again, sorry in advance), they're easily visible in the background of Titanium Backup and "Notification Toggles" app by j4velin. Also can see them in between stuff on the dialer and anywhere in the settings.
mohlsen8 said:
Yeah seriously, I couldn't stand seeing them anymore, and this morning was prepared to ship my phone away for 3 weeks to have it repaired. I'm glad they're just letting me return it. It feels tainted to me and I want a perfect one, especially for full retail price. Glad to know I'm not alone.
If anyone else is looking for them (again, sorry in advance), they're easily visible in the background of Titanium Backup and "Notification Toggles" app by j4velin. Also can see them in between stuff on the dialer and anywhere in the settings.
Click to expand...
Click to collapse
Oh for sure, Basically 700 bucks for a phone with tax it better be perfect. I don't blame you at all. Just curious, did you try a factory restore? I am almost certain it's a hardware defect but I thought about trying that.
Thanks
capathy21 said:
Oh for sure, Basically 700 bucks for a phone with tax it better be perfect. I don't blame you at all. Just curious, did you try a factory restore? I am almost certain it's a hardware defect but I thought about trying that.
Thanks
Click to expand...
Click to collapse
Yes, I ruled that out too. Flashed back to stock everything using the images in the FXZ but the marks are still there. It almost looks like the glass itself is stained or something where these "streaks" appear. No idea.

Defective Sprint replacement phone! Argh

- I am in the employee advantage club so obtaining phones is a little different or somewhat harder in some cases being that you have to wait for the employee to approve it.
-Anyways I had my HTC ONE set up perfected, but the camera was becoming increasingly worse with the purplelicious pictures.
-Picked up my phone today from my contact @ sprint and it was all sealed nothing was out of place and it looked good.
-First things first checked the hboot, baseband and android version which is on I 1.44 and android 4.1.2 and so I was happy.
-First thing I noticed the dang power button was messed up when I pressed it it would sag to the right and go inside the phone. I called sprint to activate it the phone once I got it on and it took about an hour of changing ## numbers. Finally good but...
-Now I am thinking maybe i can live with the power button but i noticed something else; there was now vibration from the phone what so ever. I checked every single dang option and everything is enabled but still no vibration. Well I called sprint and gave them my rant about their quality and assurance control which I was very pissed about after waiting sometime for the replacement. Then called my Sprint contact to reorder another phone but this licks. My phone was in prestigous condtion despite the camera and I receive a much far worse phone in return.
Anyways end Rant-
I am curuious if anyone else has had a similar issue with the vibration function not working or just receiving a shady phone all together.
I've been lucky. My first phone blew the top speaker but my second one is perfect. Neither of them had the camera issue.
Sent from my unknown using xda app-developers app
Had my phone repaired. It came back with scratches (yes, scratches that I KNOW were caused after they opened and processed it), and gaps, and glue out the corners, and a crappy power button. It was dropped once by a person I was showing it to (had taken the case off just for them) and who tried to press the power button, resulting in it falling onto hard tile from ~5 feet.
flomexico said:
I've been lucky. My first phone blew the top speaker but my second one is perfect. Neither of them had the camera issue.
Sent from my unknown using xda app-developers app
Click to expand...
Click to collapse
I must say I have been lucky as well in the past especially with my OG EVO'. They sent brand new ones no questions asked. I didnt have to use Total Protection either for the defects.
I never knew that the purple haze was really an issue. A lot of photos without a quality camera don't work well at night unless you are good at tweaking. Unfortunately mine was getting progressively worse even in good lighting conditions. Sprint will make it right, but it more less a convenience issue. I thought I scored too with the 1.44 Hboot hopefully the next one will have the same Hboot.
I took the firmware update on the defective phone. I get much better battery life on android 4.3 IMO. I wish I could walk in the store and say my phone is tweaked can I get another and call it a day, but being in the discount program with the huge savings I am considered an employee and have to wait for regular or new consumers to get items first.
Thanks for the stories and replies.

So what's the deal with the camera red tint?

I have 3 HTC Ones (all sprint) in my possession at the moment. Mine has the red tint problem. The other 2 (wife's + wife's insurance replacement.. she just broke the screen ($first time ever using phone insurance, thank god we had it$)) both seem to be fine - no red issue.
All 3 phones started with 1.31.651.2, both mine and the broken screen phone have been updated to 3.04.651.2 The new replacement is still 1.31.651.2. We've had these phones for just about 2 weeks (embarrassing, we weren't even a week into enjoying these before she dropped it..). Anywho..
I did some camera experimenting tonight to find out a few things, here are the results:
Camera issue exists with both 1.31 and 3.04. I saw some posts about people thinking the update had something to do with it, but I don't think so. The phone w/ red had it both pre and post 3.04. The normal phone has been normal both pre and post 3.04. The 3rd phone is still on 1.31.. I've left it alone as a sort-of control phone.
Heat doesn't matter (maybe if you melted things tho.. ). My phone would exhibit red regardless of waking 'cold' fresh from sleep or after heavy usage where it would really start to warm the hand. Both the normal phone and the control phone would be fine following the same pattern.
ISO 100 doesn't fix things, it just lowers the ISO enough that the camera software? stops trying to add gain/noise to the signal. Taking [roughly] the same picture between all 3 cameras at iso 100, the red one is still noticeably red tinged when compared to the other 2 phones, they're all just much darker so it's less noticeable esp if you didn't have anything to compare to.
Full wiping/resetting (incl media/data) doesn't make a difference.
Unrelated to the camera and this is kind of a nitpick, updating to 3.04 really slowed the UI down. It's still extremely fast, but it's kine of like things run at 30fps now where as 1.31 everything was 60fps. The best repeatable example is scrolling when unlocking the phone. 1.31 is silky 60fps smooth, 3.04 is crossfire/sli microstuttery. Reset/wipe doesn't make a difference.
Attaching a few boring pics.. excuse the boringness The 2 normal phone pics are pretty much the same so I've only uploaded 1 to compare w/ the red phone. Have a bunch more, but these pretty much typify what is going on.
So is this a hardware defect? What's the best way to deal with it? I don't mind shipping it to HTC and go w/o for a bit to get it addressed, but I do want to make sure it's dealt with. I'd also be pretty steamed to get either a refurb or used phone in return, because we bought these new less than 2 weeks ago (Costco).
Even though we are technically still in the 14day return window, I'm pretty sure we can't return the phones and try to switch to another Sprint offering because of insurance being used already (sigh), but that's fine - we do like the phones and want to keep them.
How do I get this fixed?
Thanks!
*edit* Contacting HTC via http://www.htc.com/us/contact/email/ just gave me a 403 Forbidden error, so this is already starting off in a bad light (pun?).
*edit2* Resubmit and got through, I'll keep this thread updated as I find out more. (I haven't been able to find any concrete info regarding all of this, so maybe this will come in handy for someone in a similar situation at some point)
pbassjunk said:
I have 3 HTC Ones (all sprint) in my possession at the moment. Mine has the red tint problem. The other 2 (wife's + wife's insurance replacement.. she just broke the screen ($first time ever using phone insurance, thank god we had it$)) both seem to be fine - no red issue.
All 3 phones started with 1.31.651.2, both mine and the broken screen phone have been updated to 3.04.651.2 The new replacement is still 1.31.651.2. We've had these phones for just about 2 weeks (embarrassing, we weren't even a week into enjoying these before she dropped it..). Anywho..
I did some camera experimenting tonight to find out a few things, here are the results:
Camera issue exists with both 1.31 and 3.04. I saw some posts about people thinking the update had something to do with it, but I don't think so. The phone w/ red had it both pre and post 3.04. The normal phone has been normal both pre and post 3.04. The 3rd phone is still on 1.31.. I've left it alone as a sort-of control phone.
Heat doesn't matter (maybe if you melted things tho.. ). My phone would exhibit red regardless of waking 'cold' fresh from sleep or after heavy usage where it would really start to warm the hand. Both the normal phone and the control phone would be fine following the same pattern.
ISO 100 doesn't fix things, it just lowers the ISO enough that the camera software? stops trying to add gain/noise to the signal. Taking [roughly] the same picture between all 3 cameras at iso 100, the red one is still noticeably red tinged when compared to the other 2 phones, they're all just much darker so it's less noticeable esp if you didn't have anything to compare to.
Full wiping/resetting (incl media/data) doesn't make a difference.
Unrelated to the camera and this is kind of a nitpick, updating to 3.04 really slowed the UI down. It's still extremely fast, but it's kine of like things run at 30fps now where as 1.31 everything was 60fps. The best repeatable example is scrolling when unlocking the phone. 1.31 is silky 60fps smooth, 3.04 is crossfire/sli microstuttery. Reset/wipe doesn't make a difference.
Attaching a few boring pics.. excuse the boringness The 2 normal phone pics are pretty much the same so I've only uploaded 1 to compare w/ the red phone. Have a bunch more, but these pretty much typify what is going on.
So is this a hardware defect? What's the best way to deal with it? I don't mind shipping it to HTC and go w/o for a bit to get it addressed, but I do want to make sure it's dealt with. I'd also be pretty steamed to get either a refurb or used phone in return, because we bought these new less than 2 weeks ago (Costco).
Even though we are technically still in the 14day return window, I'm pretty sure we can't return the phones and try to switch to another Sprint offering because of insurance being used already (sigh), but that's fine - we do like the phones and want to keep them.
How do I get this fixed?
Thanks!
*edit* Contacting HTC via http://www.htc.com/us/contact/email/ just gave me a 403 Forbidden error, so this is already starting off in a bad light (pun?).
*edit2* Resubmit and got through, I'll keep this thread updated as I find out more. (I haven't been able to find any concrete info regarding all of this, so maybe this will come in handy for someone in a similar situation at some point)
Click to expand...
Click to collapse
I don't have that problem
Sent from my HTCONE using Tapatalk
@pbassjunk check this thread out.
http://forum.xda-developers.com/showthread.php?t=2317507
Yeah I have this problem as well. Had it since I got the phone (before 4.3 update). I just try to not take pictures in low light even though that's what the camera is for. Hopefully it's a software problem and they fix it but I'm pretty sure it's a hardware problem
Sent from my HTC One using XDA Premium
4.3 update fixed that. If you still have it after 4.3, your device is defective.
Sent from my HTCONE using Tapatalk

Retitled. How to hose your phone in 35 easy steps. :)

To be fair to HTC/Sprint I retitled this. As the phone is not representative of a normal M8 (either by hardware or corrupted/miss programming).
Long story.
If you want the short version, "This phone sucks" (and by the way so does the S5).
Here is the long version.
Bought the phone first day.
HTC Unlocked and Rooted it as soon at it was available. Applied S-OFF as soon as it was available.
I had not much time to play with it and stayed on Stock and have WIFI on full time which is used at work and home.
Couple days ago I decided to try some ROMs (being very patient for things to mature a bit). I tried Barebones, pretty good ROM. Note I had "dirty flashed it".
Then I took my first long trip since I got the phone. 100 miles into the boonies.
It popped up "Roaming Guard every 2 minutes", every call. But it was still running ok.
I had forgot to shut the roaming guard off (or it was locked out by the time I though of it).
This is a known issue and happened on M7as well. Most reliable way to deal with it, is to full wipe in order to disable it. (I tried all the tricks).
Well at this time OMJ released his "Harman" ROM and Firmware.
Well I guess it's a good time to start clean, wipe and switch to OMJ's Harmon ROM (and firmware) (whom I've been a loyal customer of)
So this stupid Roaming Guard thing keeps coming and going as I sort out which ROM I want, restoring things with TB etc.
But now, my phone is "stuck is 1X". WTF. And if it does occasionally show 3G as soon as I use it, it drops out completely or reverts to 1X.
So now I think I hosed something really bad. Can't get 3G at home or work. My wifes HTC One M7 is fine (running OMJ's BadBoys ROM)
Updated Profiles, played with PRL's.
So I put it all back to factory (except S-ON) and used the HBOOT that hides that's it's S-OFF.
And flashed the closest Stock ROM I could find (which so happened to get no Data or Voice at all). Perfect !!
Then took it to sprint store, and it was a sharp kid and he said it was rooted and nicely handed it back. He suggested I add T.E.P. and "try again".
Well I figured I'll have to S-ON it. And stopped in another store to added T.E.P. just in case. I had like 2 days left.
So I was gonna go home S-ON it and go to another Sprint "repair" Store but decided I really needed to get to some other commitments.
So I restored a backup and on the road and the phone was back to "Normal" except for the stupid Roaming Guard thing. WTF.
Then it hit me. The new ROM from OMJ was telling me what my REAL network was doing and the stock ROM was lying through it's teeth.
I'm well aware of Developer ROM's displaying "1x" when it sees 1x but after being on the stock ROM (with WIFI on), I kind of forgot about it.
And I was never clear what the "New" Spark Icons were really saying anyway (with WIFI ON or OFF).
So the truth is this thing has been running like crap since day 1. And I believe even worse since the first OTA firmware update.
I started researching options to get the Galaxy S5. Turns out the reviews are worse on the S5 than the M8.
Then I kept finding threads like this one.
https://community.sprint.com/baw/thread/155517
Maybe I have a bad phone. Maybe I'll just smash the thing and try another one.
I miss my M7. Luckily my wife has it.
I had to get my first M8 replaced because it was roaming all the time. My second one is much better . Sounds like you have a bad one like my first one. I returned mine within the first 14 days to get a no-questions-asked replacement for full refund.
Uhh.. No problems here. Sounds like a defective device to me. They won't swap it where you rooted it, TEP will cost you a deductible and they'll send you a refurbished model. Shouldn't of rooted so quickly.
Sent from my 831C using xda app-developers app
I don't understand if u don't want the roaming guard to sound just uncheck it on the settings. If you have trouble with your settings dial *#*#4636#*#* and select phone information scroll down and select the option cdma+evdo/lte then reboot and check if that help. Then again u should be aware of this
http://forum.xda-developers.com/showthread.php?t=2701255 just in case u r not.
Sent from my 831C using XDA Premium 4 mobile app
breezedragon said:
I don't understand if u don't want the roaming guard to sound just uncheck it on the settings. If you have trouble with your settings dial *#*#4636#*#* and select phone information scroll down and select the option cdma+evdo/lte then reboot and check if that help
Sent from my 831C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not so easy to shut Roaming Guard off. I'll bet if most people look right now, You'd find it greyed out.
I just completely wiped my phone again. Ran RUU on it. Immediately Disabled the Guard. And a half hour later it's all locked out again (but it's locked out disabled).
I don't know what causes it to lock.
But you do have to do it immediately after a wipe.
I'll check out the Options #*# option you suggested. Thanks. I remember that being mentioned before.
Aldeel said:
Uhh.. No problems here. Sounds like a defective device to me. They won't swap it where you rooted it, TEP will cost you a deductible and they'll send you a refurbished model. Shouldn't of rooted so quickly.
Sent from my 831C using xda app-developers app
Click to expand...
Click to collapse
I tend to root as soon as it's available. In case an OTA comes out and lose the ability to ever do it. I also like to see if I can root it with in the 14 days, because if something does go wrong I can swap it. I can make it factory looking again. I just didn't want to bother in case they could fix it, because it felt like just a programming issue. I knew I was taking a chance when I brought it in like that. I've brought in MUCH more hacked phones and walked out with a brand new one, with no T.E.P.
I'm still not sure if this is a "Broken" phone. It definitely won't pull in weak 3G like my M7 did.
mswlogo said:
I'm still not sure if this is a "Broken" phone.
Click to expand...
Click to collapse
It probably is.
Fwiw, I've never seen my roaming guard settings greyed out.
As a sprint tech I can tell you 100% of the M8's that have come in to my store that I've replaced have been better the second time around. Seems like there were some lemons in the first batch. You'd better take it in to get exchanged or break it to get a replacement soon(lol) because as of today we were ordering new replacements, soon it'll be refurbs once there is stock in the warehouse.
I also noticed the serial number on my original M8 started with FA, while my current one starts with HT. Could be that ones from a specific location were bad.
There is problem in this phone. I don't think why you face this type of problem?
HaiKaiDo said:
As a sprint tech I can tell you 100% of the M8's that have come in to my store that I've replaced have been better the second time around. Seems like there were some lemons in the first batch. You'd better take it in to get exchanged or break it to get a replacement soon(lol) because as of today we were ordering new replacements, soon it'll be refurbs once there is stock in the warehouse.
Click to expand...
Click to collapse
Thanks for the heads up. Hopefully I won't have to "break it". I never have, but I would if it came down to it.
I was thinking that they are not refurbished yet as well.
I'm not convinced 100% it's broken yet.
I did notice in a breakdown of the phone, that they do have little spring loaded contacts to the Antenna's, which have been a problem on past phones. And that might be all it is.
I have $18.00 glass screen installed on it as well. And it's installed PERFECTLY. Chances of that happening again are slim
I really would like to get this phone to work.
That thread I posted, folks got second phones and still had issues.
I think it has to do with this whole Spark thing.
You know I wouldn't be rooting and wanting the option of Roam only etc. if the Sprint Network wasn't so bad in the first place.
The only thing that keeps me is the SERO plan. But that is wearing thin. Everyone of my co-workers gets 10-40x faster data rates than I do.
AT&T or Verizon.
Sprint better get their act together.
Oh and the store I did go to. They just fired all their Techs 3 weeks ago. It used to be a good store to go to.
Captain_Throwback said:
It probably is.
Fwiw, I've never seen my roaming guard settings greyed out.
Click to expand...
Click to collapse
Me neither.
Should definitely look into getting it replaced, though.
Captain_Throwback said:
I also noticed the serial number on my original M8 started with FA, while my current one starts with HT. Could be that ones from a specific location were bad.
Click to expand...
Click to collapse
My M8's serial number starts with FA and so far, the only real issues I've had are sending/receiving texts at home. Sometimes, they come in delayed but I attribute that to the network moreso than the phone. Though, updating the profile/prl seems to fix it. Forcing the phone to re-provision while on CDMA rather than LTE seems to also keep it from happening sooner.
mswlogo said:
Thanks for the heads up. Hopefully I won't have to "break it". I never have, but I would if it came down to it.
I was thinking that they are not refurbished yet as well.
I'm not convinced 100% it's broken yet.
I did notice in a breakdown of the phone, that they do have little spring loaded contacts to the Antenna's, which have been a problem on past phones. And that might be all it is.
I have $18.00 glass screen installed on it as well. And it's installed PERFECTLY. Chances of that happening again are slim
I really would like to get this phone to work.
That thread I posted, folks got second phones and still had issues.
I think it has to do with this whole Spark thing.
You know I wouldn't be rooting and wanting the option of Roam only etc. if the Sprint Network wasn't so bad in the first place.
The only thing that keeps me is the SERO plan. But that is wearing thin. Everyone of my co-workers gets 10-40x faster data rates than I do.
AT&T or Verizon.
Sprint better get their act together.
Oh and the store I did go to. They just fired all their Techs 3 weeks ago. It used to be a good store to go to.
Click to expand...
Click to collapse
Yeah lucky for me I dont work at a corporate store lol. They did a mass layoff of techs in corporate stores.
No problems here either
~m8whl modded stock
2.265 Max ¦ 300 Min
ondemand
row
I'm curious now if my phone is bad or its network related. I seem to drop/miss calls quite often. I just checked my serial number and it starts with FA as well.
I'm wondering if these phones were all built in different locations. I have a gold one from best buy and this thing works like a champ. I get similar cell signal compared to my s3. Even at my in laws house which just got lte a few months back and my brother in laws house where I get no signal on my s3, it acted the same with no signal. He lives in a secluded area. I'm reading a lot of negative things about phones bought thru Sprint being problematic. Haven't read anything about the gold best buy phones acting up. What do you all think could these phones be built in totally different locations?
Sent from my 831C using XDA Premium 4 mobile app
Maybe not different locations, but definitely different batches. Some could have subpar antennas.
I believe the serial number indicates the distribution center from which the device was produced. I saw mention of it in the Firewater thread when people were trying to figure out why it worked on some devices and not on others.
Serial number for my phone started with FA. Ordered it after watching the unveiling, got it two days later.
Haven't had a single problem with the phone as far as software, and no hardware issues like defects.
Guess I'm just lucky.
Knock in wood taking the firmware update on H/K ROM doesn't change things down the line.
sprkat85 said:
I'm wondering if these phones were all built in different locations. I have a gold one from best buy and this thing works like a champ. I get similar cell signal compared to my s3. Even at my in laws house which just got lte a few months back and my brother in laws house where I get no signal on my s3, it acted the same with no signal. He lives in a secluded area. I'm reading a lot of negative things about phones bought thru Sprint being problematic. Haven't read anything about the gold best buy phones acting up. What do you all think could these phones be built in totally different locations?
Sent from my 831C using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have a gold one as well and also see none of these issues. It also seems to be comparable to my S3's reception.

Guys,Please post snap of your back panel, near the volume keys

I believe my back panel is slightly raised near the volume keys, I see small gap there. I don't have any other phone to post snaps at this moment, Will you please put zoomed snaps of your back panel near the volume keys.. Would like to confirm if it is a issue with my handset only or it looks same for other handset too.
Thanks a lot.
plss guys help
This has been brought up a few times in the forums already. From what I have heard, Moto has already acknowledged the issue and will take care of it. If you look at these two threads, you can see pictures of member's phones with the issue, from very minor all the way to extreme circumstances.
http://forum.xda-developers.com/nexus-6/help/cover-peeling-off-t3004941
http://forum.xda-developers.com/nexus-6/general/nexus-6-quality-issues-2-2-phones-t3002262
If you must have a photo, here is mine. The issue on my personal phone is very minor (I wouldn't have even realized it if it weren't for those links above) and gets just a little bit worse if the phone gets warm. However, even at its worst, I can barely get under the back cover with my fingernail.
I am not able to post a photo right now, but I can confirm the back cover is ever so slightly raised between power and volume buttons on my Nexus 6. I can't say if it has been like that from day one, but is so minor right now that it doesn't bug me. If it gets worse I'd probably get a cheap replacement back from eBay instead of going through an RMA process.
Here's a picture of mine, which has an almost undetectable gap. Unchanged since I purchased it.
Can I post a picture of potato?
badboy47 said:
Can I post a picture of potato?
Click to expand...
Click to collapse
can 1 (kăn; kən when unstressed)
aux.v. past tense could (ko͝od)
1.
a. Used to indicate physical or mental ability: I can carry both suitcases. Can you remember the war?
b. Used to indicate possession of a specified power, right, or privilege: The president can veto congressional bills.
c. Used to indicate possession of a specified capability or skill: I can tune the harpsichord as well as play it.
2.
a. Used to indicate possibility or probability: I wonder if my long lost neighbor can still be alive. Such things can and do happen.
b. Used to indicate that which is permitted, as by conscience or feelings: One can hardly blame you for being upset.
c. Used to indicate probability or possibility under the specified circumstances: They can hardly have intended to do that.
3. Usage Problem Used to request or grant permission: Can I be excused?
Click to expand...
Click to collapse
Going by the above, in the most cases I would suggest the answer would be "yes"
Thanks to all those who posted. Mine is quite similar to you guys, very slightly raised. I guess ill keep an eye , if its get worse then go for replacement.
I just took mine back yesterday to T-Mobile store and had it replaced. Mine was slightly raised at store then when I got home and set it up and actually played a few games I decided to take the back off because I felt dampness on my right hand and was confused. Thought maybe it was sweat, but to my surprise when I took case off the back panel had a huge gap/bulge right around the volume buttons.!? But what really freaked me out is the liquid that was coming out of it as well. I managed to push the panel back down and as I was doing this this liquid was oozing out from that whole side. I immediately call T-Mobile store where I purchased it and was told not to use the device and turn it off and don't charge it.
When I took device to store they where vary concerned and the rep. Actually called a rep. At Motorola about the situation. At least that's what the sale rep. At T-Mobile said. They immediately gave me a new device and a free case / cover for the phone and sent me on my way.
I don't know what the rep at Motorola told the sale rep. But he did say they are taking a serious look at this issue. It seems to be a battery issue and some batteries are actually bursting. IDK but I have a new one now with no issues and love this device.
Sent from my Nexus 6 using XDA Free mobile app
Hi
I just got mine from Tmo and start to notice this problem just like yours, i need to ask if the back case does help in this situation?
do i have to worry about it?
This means most of the devices have this back panel issue. Mine is 64GB one, so its not just 32GB that have the issue
I just called Tmo and they were very helpful and after 5 minutes of hanging up the phone they had shipped a new-brand device (as he told me they will). and i have to ship them the defective device. they also credit my account 10$ for me to ship the device
it should arrive tomorrow i hope the new one will be OK
prestige2 said:
Hi
I just got mine from Tmo and start to notice this problem just like yours, i need to ask if the back case does help in this situation?
do i have to worry about it?
Click to expand...
Click to collapse
I would return as soon as possible if your seeing any gaps in back panel. I not only had a bulge in mine but also had a mysterious liquid coming out of it. I know its hard to believe ,I wish I would have taken a picture but I didn't. Trust me just return it for another device.
Sent from my Nexus 6 using XDA Free mobile app
I have something similar however its very minor. If I push with my nail it maybe moves 0.5mm
Mine looks like this http://images.anandtech.com/doci/8687/IMG_0152.JPG
I replaced my back cover when they became available on ebay because there were some scuffs from the factory and the covers were only about $8. The new one is raised slightly. You can push it down but it raises back up over time. I would imagine any replacement will do the same until they address the adhesive on the back,

Categories

Resources