Database Users

[VIDEO] S3 screen flickers with white pixels

I've only had the S3 for a few days and haven't even installed very many apps.
When I pull down the top menu or when I first open an app it flickers with white pixels.
I'm assuming this is a hardware issue with the phone?
What do you think?
--------
Well I was going to post a YouTube video of it, but I guess I can't because I don't have 10 posts.
Bummer dude.

Here is the last part of the URL, please take a look and let me know what you think-
/watch?v=_h7I4_qOd-s

iggz said:
Here is the last part of the URL, please take a look and let me know what you think-
/watch?v=_h7I4_qOd-s
Click to expand...
Click to collapse
Wow that's irritating issue - could be a hardware or software issue honestly but definitely not normal.

mobilehavoc said:
Wow that's irritating issue - could be a hardware or software issue honestly but definitely not normal.
Click to expand...
Click to collapse
Yeah, it's extremely irritating.
I actually just did a factory reset and it's still doing it.
So I'm guessing a hardware issue with the screen, just my luck!

Any other opinions on this?

iggz said:
Yeah, it's extremely irritating.
I actually just did a factory reset and it's still doing it.
So I'm guessing a hardware issue with the screen, just my luck!
Click to expand...
Click to collapse
Factory reset only deletes user data it does not "reflash" the OS. Before you return it you may want to (if you're into it) try reflashing stock ROM via Odin. If after you've flashed stock rom you are still experiencing issues then you know it's definitely hardware.

[Q] Nexus 4 Random Power Off

As the title states. Nexus 4 random power offs. Has anyone seen anything like this?
Here is the background info:
My parents have Nexus 4 phones as do I. All of our phones were ordered at the same time about 2 months or so ago when they became available again. All phones are the 16GB version. All phones bone stock with just OTA updates, not unlocked or rooted other than how they are shipped. All using T-Mobile prepaid plans.
My phone and my father's seem fine. My mom's however seems to shutdown on its own. It is random. Initially I thought that it may be an issue where she isn't used to a smart phone and isn't charging it enough. It happens though at times while it is connected to the charger. It also has happened while carrying it off the charger.
One odd thing is that when they got the phone they brought them to my house and dropped them off to have me set them up. One had the plastic screen protector with the printing on it from the factory the other didn't. I don't know which is which though now. It is a 50/50 shot if this is the one.
I have been around android since the G1 days and run the same phone. I can't think of a setting on the phone that would power it down at a certain time or period of time. She really doesn't have much for apps and is a very light user.
Not sure what to try but I was thinking about doing a wipe of the phone to see if it helps.
Anyone else have any ideas? If the wipe doesn't help the only other thing I can think of is that there is a physical issue with the phone.
I haven't seen this on my phone but there was a period of time where HD Widgets on my N7 would cause a reboot. That was fixed with an app update. This isn't a case where the device reboots. It is a complete shutdown which I find odd. So I have seen an app cause issues kind of like this. For the most part the apps that she has on her phone, I also have on mine. Well I have way more but there really isn't anything on her phone that I am not also running.
I should add that she has the phone in a TPU case. As we all do. My case design is a little different than theirs but they have cutouts for the buttons. So it isn't a case where the case is pressing on the power button. That could be an issue with my case as it covers the power button but I haven't had that issue.
Thanks

Sounds like it might be a defective battery...
Sent from my Nexus 4 using xda app-developers app

BigDig said:
Sounds like it might be a defective battery...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That is what I am kind of thinking. Either the battery or the smart battery chips. I think I will try a wipe first but like I said but it is odd.

sennister said:
One odd thing is that when they got the phone they brought them to my house and dropped them off to have me set them up. One had the plastic screen protector with the printing on it from the factory the other didn't. I don't know which is which though now. It is a 50/50 shot if this is the one.
Thanks
Click to expand...
Click to collapse
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.

amartolos said:
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.
Click to expand...
Click to collapse
I don't want to root and have my mom run a modified ROM. They live about a half hour from me so I haven't tried a wipe of the phone yet and because of the distance I don't want to deal with the issues that sometimes come up when you go with modified ROMs when I am not there. She is a very basic user and this is the first smartphone for my father and mother. Keep in mind they are in their early 70s and not really that strong on the tech side of things. I have to get some time to run over there and take a look at it. Maybe later next week.
I was just wondering if anyone else has had this issue. I think if a wipe doesn't help I will talk to Google. A search really didn't show much other than some people that were seeing a random reboot issue. I have seen apps doing that.
I have been through their warranty replacement process and it is a bit of a PITA. I am on my 3rd Nexus 7 due to hardware issues with the first 2. My N4 and my fathers have been rock solid.
While I have run custom ROMs in the past, I usually run stock until I find a need that requires me to root. Eventually I will probably root and go with a custom ROM on my N4 but

sennister said:
She is a very basic user and this is the first smartphone for my father and mother. Keep in mind they are in their early 70s and not really that strong on the tech side of things.
Click to expand...
Click to collapse
Yeah, I know what you mean. I'm giving my parents my old LG P990 phone and I just put an AOKP rom on it. I also installed Nova Launcher for them and configured it so there's just one texting app and one calling app the one and only one homescreen. No dock either, just in case they click something by accident or get lost in the app drawer
Since you have the same phone as your mom, a self-less workaround would just be to give her yours (pre-configured), and then you can fiddle around with the problematic one until you find a decent solution. :good:

amartolos said:
That sounds kind of questionable (fishy) to me... I also have the 16GB version, and I also did the OTA when I got it. But to be honest the stock OS lasted only about an hour before I rooted and started trying out custom ROMs I have not had the issue you're describing though. How are the results from your factory reset?
Also, would you consider putting on a stock-based custom ROM (such as rasbean vanilla) for your mother's phone? If the problem is software based then a reset or a new ROM might yield different results. But if the problem persists it might be hardware and I'd suggest you contact Google about servicing.
Click to expand...
Click to collapse
amartolos said:
Yeah, I know what you mean. I'm giving my parents my old LG P990 phone and I just put an AOKP rom on it. I also installed Nova Launcher for them and configured it so there's just one texting app and one calling app the one and only one homescreen. No dock either, just in case they click something by accident or get lost in the app drawer
Since you have the same phone as your mom, a self-less workaround would just be to give her yours (pre-configured), and then you can fiddle around with the problematic one until you find a decent solution. :good:
Click to expand...
Click to collapse
Hmm. That is a good idea. The PITA part would be to get everything loaded from my phone to hers. I really wish I could run Titanium backup without root as it would make it super easy to move the apps over. Though I don't have that much loaded on my phone. Things that are a pain to set up have configuration export methods like Tasker. It would rule out the end user being the source of the issue. I don't think that is it though. If we swap and it goes away, then I can consider the wipe as the solution. If the problem moves to me then it is a physical issue and call Google. If the problem persists with her, I load all her apps on the phone I carry as well to see if I start to have the issue or it becomes a training issue. The thing I like about this the most is that it is a clear process to rule out several things. I can go over there and sit with the phone but if it doesn't power off when I am there I don't gain much other than spending some time with my parents.
I don't think this is an issue but I did have to provide my IMEI# when doing the activations. In the past though on T-Mobile I have handed phones down to others and all we did was a SIM swap. I would imagine that is the case here.
Oh and one thing I did leave out. They were using their old cell phone chargers on the N4 phones. I told them to swap chargers and use the ones that came with the phone. The old ones may not put out enough power and the phone could in theory run down to the point where it shuts off and slowly charge from that point and I don't think it would turn back on. Keep in mind a retired user who just had a knee replacement so she is at home more often than not.

Did you find out the cause? I have the same issue happened twice today

The random shut off either charging or not happens to me but as mentioned before in a related thread, a lot of the times it also happens on Wi-Fi, and having WiFi optimization on.. purple were turning that off and some fixed the issues. This is my second nexus 4, so I right id give it a try and not use wifi and hasn't happen since I received mines on the 4th of may
Sent from my Nexus 4

noodles2224 said:
The random shut off either charging or not happens to me but as mentioned before in a related thread, a lot of the times it also happens on Wi-Fi, and having WiFi optimization on.. purple were turning that off and some fixed the issues. This is my second nexus 4, so I right id give it a try and not use wifi and hasn't happen since I received mines on the 4th of may
Sent from my Nexus 4
Click to expand...
Click to collapse
So you're saying it's a software issue?

Looks like it.. Turning off optimization or not even using WiFi at all worked..
Sent from my Nexus 4

Faulty compass

Does anyone else get the following:
1. GMaps not recognising the compass and not turning its compass as you turn round;
2. Compass app goes mental when you test by spinning round (mine spins the wrong way then back randomly)
?
Looks like my Note3 is proper fkd. At the moment it's just peeing me off.

fergusstrachan said:
Does anyone else get the following:
1. GMaps not recognising the compass and not turning its compass as you turn round;
2. Compass app goes mental when you test by spinning round (mine spins the wrong way then back randomly)
?
Looks like my Note3 is proper fkd. At the moment it's just peeing me off.
Click to expand...
Click to collapse
Sounds like the Note 3 is suffering from the same compass issue as the S4. The compass just needs to be calibrated. Download GPS Status & Toolbox (excellent app!) from Google Play Store and go to Tools/Compass calibration. That should fix it. Calibrate the compass outdoors away from metal structures for best accuracy. Factory reset resets also the compass calibration data, but luckily the calibration takes only about 10 seconds or so. Hope this helps!

PeteFinn said:
Sounds like the Note 3 is suffering from the same compass issue as the S4. The compass just needs to be calibrated. Download GPS Status & Toolbox (excellent app!) from Google Play Store and go to Tools/Compass calibration. That should fix it. Calibrate the compass outdoors away from metal structures for best accuracy. Factory reset resets also the compass calibration data, but luckily the calibration takes only about 10 seconds or so. Hope this helps!
Click to expand...
Click to collapse
Cheers Pete.
I did try that but it's still flying all over the place.
Sending it back as faulty. There's too much I dislike about this phone to make it worth £620.

I tried with mine and a few demo units from the stores.
After a thorough test, they all essentially have this problem. My one, when you go to *#0*# it would just either not spin or spin sporadically, same with the demo units.
I guess it's a software problem, 4.3 problem essentially, my AOSP'd Note 2 also has this problem

nicholaschum said:
I tried with mine and a few demo units from the stores.
After a thorough test, they all essentially have this problem. My one, when you go to *#0*# it would just either not spin or spin sporadically, same with the demo units.
I guess it's a software problem, 4.3 problem essentially, my AOSP'd Note 2 also has this problem
Click to expand...
Click to collapse
Wow, so perhaps all of them come with a feature that just doesn't work? Weird.

fergusstrachan said:
Wow, so perhaps all of them come with a feature that just doesn't work? Weird.
Click to expand...
Click to collapse
Well, probably just the batch that first came out. Do you have this problem?

nicholaschum said:
Well, probably just the batch that first came out. Do you have this problem?
Click to expand...
Click to collapse
I did, but sent it back.

fergusstrachan said:
I did, but sent it back.
Click to expand...
Click to collapse
Does your replacement have the same issue?

nicholaschum said:
Does your replacement have the same issue?
Click to expand...
Click to collapse
Ah, I see what you're getting at.
No, I didn't get a replacement. Sammy's seem to be all about the gimmick now, and I'm waiting for the N5 or a 32GB G2 to hit these shores.
Besides, £620 for a phone that does the pen-hover thing that my 2003 Windows tablet PC did? Nah.

fergusstrachan said:
Ah, I see what you're getting at.
No, I didn't get a replacement. Sammy's seem to be all about the gimmick now, and I'm waiting for the N5 or a 32GB G2 to hit these shores.
Besides, £620 for a phone that does the pen-hover thing that my 2003 Windows tablet PC did? Nah.
Click to expand...
Click to collapse
Oh right okay, so you yourself had the same problem, but probably some external reason not mainly because of this, you sent it back and issued a refund?
I have a feeling that when I leave my house, there is a lot of magnetic interference because my compass always works in my house :/

nicholaschum said:
Oh right okay, so you yourself had the same problem, but probably some external reason not mainly because of this, you sent it back and issued a refund?
I have a feeling that when I leave my house, there is a lot of magnetic interference because my compass always works in my house :/
Click to expand...
Click to collapse
?
I had the problem, per my original post, so I sent it back as faulty. There are other reasons I was happy to send it back though, as I wrote above.

fergusstrachan said:
?
I had the problem, per my original post, so I sent it back as faulty. There are other reasons I was happy to send it back though, as I wrote above.
Click to expand...
Click to collapse
Yeah, I noticed I was speaking to the OP like a min ago, I thought the OP got a replacement and never responded back, but alright! I hope a software update could fix this :/

nicholaschum said:
Yeah, I noticed I was speaking to the OP like a min ago, I thought the OP got a replacement and never responded back, but alright! I hope a software update could fix this :/
Click to expand...
Click to collapse
Heh. I hope they sort it out for you.

I'll be sending this device back and getting a replacement, since Rogers has a 15 days return policy if under 30 mins talk time, I'm gonna exchange for a brand new one and see whether that helps
Sent from my fingers to your face using my Samsung Galaxy Note 3!

Got a brand new one! If it still doesn't work, well then screw it, I guess a software update would fix it.

nicholaschum said:
Got a brand new one! If it still doesn't work, well then screw it, I guess a software update would fix it.
Click to expand...
Click to collapse
so you have found a solution for your compass problem?

Following up...
Anyone have any luck getting the compass fixed? Just got my Note 3 (T Mobile US) and I am having the same problem. Makes orienteering and geocaching all but impossible...

sophocles65 said:
Anyone have any luck getting the compass fixed? Just got my Note 3 (T Mobile US) and I am having the same problem. Makes orienteering and geocaching all but impossible...
Click to expand...
Click to collapse
My new device still has this bug, but calibrates faster than my first one. It's a widely known bug, maybe Samsung needs to fix it.

FWIW mine has the same problem. I did manage to get it work work correctly for a little while by using a "metal detector" app which vibrated when it detected something. It suddenly started behaving correctly for a short while.
Calibrating it with the GPS Tools app also fixes it for a little while.

Having the same issue with my Note 3 as well.The GPS Status app using the compass calibration fixes the problem but once you restart the phone the compass no longer works again and you need to calibrate once more.
It seems like a software bug issue rather than a faulty compass.It's annoying but at least there is a solution.

Touch screen sensitivity issue still in 38R

I wonder if anyone is also experiencing sensitivity issues with the new 38R OTA.
In my case It is evident when scrolling (homescreen, twitter, whatsapp....) and typing. Also the capacitive buttons seem a bit unresponsive from time to time.
What about you guys?
Edit: here you have the prove (bad scrolling and multitouch problem) i think i am going to RMA
Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src
Edit:
Suddenly the issue has been gone for a week, no problems at all since 15 October... I am so confused
Edit 2:
The sensibility issue is back on 24/10/2014 without changing anything

QuBeX said:
I wonder if anyone is also experiencing sensitivity issues with the new 38R OTA.
In my case It is evident when scrolling (homescreen, twitter, whatsapp....) and typing. Also the capacitive buttons seem a bit unresponsive from time to time.
What about you guys?
Click to expand...
Click to collapse
Yes, I also still have troubles with it. I especially notice it when typing.

gr4nchio said:
Yes, I also still have troubles with it. I especially notice it when typing.
Click to expand...
Click to collapse
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time

QuBeX said:
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time
Click to expand...
Click to collapse
I am really not sure... the last couple days I was on 33R CM11S with AK kernel and did not notice the problem at all. But it is not something that happens often in my case. So it is possible that I just did not wait long enough for it to appear.
I will stay on stock cm11s 38R for a few more days and then probably switch back to AK kernel to see if my previous experience is reproducible.
Did you even try to use a different kernel? Did you still have the issue?

gr4nchio said:
I am really not sure... the last couple days I was on 33R CM11S with AK kernel and did not notice the problem at all. But it is not something that happens often in my case. So it is possible that I just did not wait long enough for it to appear.
I will stay on stock cm11s 38R for a few more days and then probably switch back to AK kernel to see if my previous experience is reproducible.
Did you even try to use a different kernel? Did you still have the issue?
Click to expand...
Click to collapse
Just flashed AK, It seems that the unresponsiveness is still there
I am really dissapointed, i though this OTA would solve sensitivity problem...

QuBeX said:
Just flashed AK, It seems that the unresponsiveness is still there
I am really dissapointed, i though this OTA would solve sensitivity problem...
Click to expand...
Click to collapse
Sorry to hear it did not help.
I have also just noticed this post http://forum.xda-developers.com/showpost.php?p=55195972&postcount=62 which suggests macgyvering an improved grounding for the phone. I have to admit that I don't understand exactly what to do. But it might become clearer if I get frustrated enough to actually open up the phone
Please let me know if you try it and it works.

Touch screen is still going to be an issue. You can check the original bug which was reported here (still says in progress) https://jira.cyanogenmod.org/browse/BACON-55

gr4nchio said:
Sorry to hear it did not help.
I have also just noticed this post http://forum.xda-developers.com/showpost.php?p=55195972&postcount=62 which suggests macgyvering an improved grounding for the phone. I have to admit that I don't understand exactly what to do. But it might become clearer if I get frustrated enough to actually open up the phone
Please let me know if you try it and it works.
Click to expand...
Click to collapse
It could work but i don't want to touch inside the phone very much, I don't want to void my warranty. I think I will RMA with this video I just made. Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src

QuBeX said:
It could work but i don't want to touch inside the phone very much, I don't want to void my warranty. I think I will RMA with this video I just made. Multitouch and sensitivity issues in 38R: http://youtu.be/KSAl1Uh_Src
Click to expand...
Click to collapse
You should just know that OPO's customer service while polite, will give you the run around a while. Took me about a month before they finally granted the RMA.

jlevy73 said:
You should just know that OPO's customer service while polite, will give you the run around a while. Took me about a month before they finally granted the RMA.
Click to expand...
Click to collapse
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.

dipdewdog said:
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.
Click to expand...
Click to collapse
Not sure since I just requested a new phone.

dipdewdog said:
Will they RMA for a refund or just a new phone? I'm not convinced this will ever be fixed in software, and I'd rather go back to a mainstream manufacturer at this point.
Click to expand...
Click to collapse
They will, at least, replace your phone. I did and am waiting for my new one to arrive. If multitouch issues remain (and most likely will) i'll ask for a refund. I don't really care if the phone is "cheap for specs", this flaw is unacceptable.
My S3 is much worse hardware wise and feels SO much better while typing or anything else touch related. I did have to open a ticket and later show up a few videos of multitouch malfunctioning to oneplus. They decided it was a malfunctioning unit and i was eligible for a replacement. They never mentioned bacon 55 or a "known issue" common to every phone that would be solved at some point later on.
It's taking forever too. It's been over a month and it's mainly their fault because they take so long to reply to every single email. They did ask my VAT number before hand so they could send an invoice with it to my customs that would facilitate the returning process. Despite that, my phone got stuck on my country's customs precisely because they sent them an invoice without it and was up to me to ask it to oneplus. I waited about a week for what seems an poorly excel made document (compared to my country's invoices this is a joke of a document ). I sent it to the courier who picked up and they forwarded it to customs. Stuff went smooth from that point on. Oh yea, i'm from Portugal and even though my phone was sent to me from the UK the first time, to return a phone, you're going to send it to Hong Kong. All free of charge. I did have to print loads of pre made documents (about 10 pages?), because apparently sending anything with a battery is a big deal safety wise.
Even though they are, like someone said, polite, they do take a good while to reply to anything and aren't very keen to answer to anything that falls a bit out of their "process". For example, I've asked them several times if they would send me a new phone before or after a return mine. They never really cared enough to answer. Their English also seems translated by google sometimes. Several different people may take care of the same case. I've had about 5 or 6 different names reply to me and they all just use their first name like "Wilona". It made me stop to think i was sending my already paid phone to some place across the world because this randomly named guy told me so by email - in any other different scenario this would scream of a scam. But I've placed my RMA through an official ticket on their website, they actually made a new order request from their store on their website, they use very well known couriers with tracking numbers and it's the only way i'm ever getting a chance of having a properly working phone.
I did warn them before sending my "faulty" unit back they can expect me asking for a full refund if this new one isn't working any better.

I have been on liquidsmooth rom since I got the phone, no problems with touchscreen whatsoever, Installed new 38 CMS today and started to experience that problem. Also, cms lags compare to AOSP, this is pretty weird

QuBeX said:
Do you think it could be hardware problem? I am not sure, because sometimes it works perfect, but it is the 10% of the whole time
Click to expand...
Click to collapse
Flashing ColorOS for me gave a much better touchscreen experience, things worked flawlessly in all apps for me(Amazon is my biggest issue, any scrolling over a description/review would select it and move you to that section to read it, does not happen at all in ColorOS), so im thinking its software

This issue is so exaggerated...
Sent from my A0001 using Tapatalk

What is the touchscreen issue that people are referring to? Mine seems perfect? The only issue is the slight yellow at the bottom but you only notice it if you actually go looking for it.

jojohnson250 said:
This issue is so exaggerated...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Not really. It's bothersome.
Sent from my OnePlus One using Tapatalk

Mines slightly yellow at the bottom, appears to be getting a bit better though, unless thats just my eyes playing tricks on me. I haven't noticed touchscreen issues except i can't seem to press the spacebar properly

My touchscreen seems to be very picky as to where I touch. Sometimes it takes a few attempts. Since 38 I have had random reboots. I m stock rooted without anything else flashed.

jojohnson250 said:
This issue is so exaggerated...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
If you can say that you're a lucky one. It can render your phone completely unusable. Imagine your phone randomly assuming touches when you're not even touching it, non stop (stuff opening, key input, etc). You can't do anything else while it happens and the only way to stop is by rebooting. 5 to 10 times a day, everyday. Also, just about anything multitouch like simply zooming on a webpage has a 50% chance of working or send your phone spazing on a zooming in/out frenzy. So I'd say it isn't exaggerating, you just aren't experiencing the worse of it.

Always on display and night clock issue

Hi guys
Recently I developed a problem where the entire screen is dimly lit when the night clock and always on display are used. It seemed to just happen out of nowhere, nothing that I did that I can think of but it sort of defeats the purpose of having it on an oled display if every pixel is lit. Phone is on the latest update, never rooted, and the always on display is at the latest version. I have tried everything up to a full factory reset. Any help is greatly appreciated.
One thing to add, I even tried flashing a new firmware through odin

I'm having the same problem. Did you manage to find a fix?

captainnebevay said:
I'm having the same problem. Did you manage to find a fix?
Click to expand...
Click to collapse
No. Seems that we're not the only ones with the issue but nobody seems to know anything about it. I was hoping the latest update would fix it, but no. My current theory is that it's a bug in the always on display driver, but that seems to be updated through the galaxy app store. If anyone knows how to revert to an old version of always on display, it may be helpful.

Well, spoke to Tmobile, getting a replacement phone.

Same issue here (it glowed in the dark); called TM for replacement. All better now
Thx for the tip.

HTCforme? said:
Same issue here (it glowed in the dark); called TM for replacement. All better now
Thx for the tip.
Click to expand...
Click to collapse
Yea, it seems like a rare problem, but definitely a hardware fault. Oh well, got a brand new, non-refurb device, thanks to Tmobile. Glad it worked out for you.