Database Info

Manufacturers can build a phone anyway they want?

I have a problem with my phone but the company does not aknowledge it. It says that since all specific models behave the same way theres nothing they can do. So i want to ask. If my phone's touch screen is very incaccurate while being capasitive and while every other phone's is accurate there's nothing i can do? Can they also build phones that automatically shutdown without being aknowledged as a problem or anything else they like without mentioning the awkward behaviour prior to purchase?

Maybe you should RMA your phone, you can have faulty touchscreen, ... etc.
You should specify your phone manufacturer and model, than more people can help you.

CZMagic said:
Maybe you should RMA your phone, you can have faulty touchscreen, ... etc.
You should specify your phone manufacturer and model, than more people can help you.
Click to expand...
Click to collapse
Im just trying to make a point. I RMAed the phone and they told me every specific model has the same behaviour and theres nothing they can do. Im just trying to understand if i have a right to believe i have a problem or the company's answer is legit.

[Q] Stock GS3 dies while taking pictures

Ok here is my issue.
I had a VZ GS3, running the same software it had out of he box. ie I never rooted it or unlocked the bootloader(I was waiting for a stable JB/Touchwiz).
Anyway, I had the phone for about 3wks. Didn't run into any issues seemed to be working fine. One morning I was sitting around playing with the camera taking pictures of my girlfriend play with her dog.
In the middle of taking pictures the phone just died. At the the time the battery was pretty low maybe 10-15%. At first I thought the battery was dead so I tried charging it but the charging LED never lit up. Pressing the home button did nothing(no battery graphic). I went and took a shower leaving it on the charger for another 30min still no change. I tried booting into ODIN mode, but still got nothing.
So I got dressed and went to VZ. The tech pulled the battery and tried one from a display unit, but we still got nothing . We tried booting into ODIN with this new battery & still nothing. The tech said he had never seen anything like that happen before so they would return my phone on warranty (I don't have insurance).
Of course they send me a refurb and it works fine but I can't help but feel a little cheated, I bought a new $250 phone and through no fault of my own I have to live with this refurb. Also, this has made me a little wary of rooting my phone since if it hard bricks I won't be able to restore it to factory before sending it back.
Anybody hear of anything like this happening with other GS3's

What's wrong with a refurb? How do you feel cheated? You returned your non working phone for a phone that does work and passed another round of QC. I don't see the problem here.

mustbepbs said:
What's wrong with a refurb? How do you feel cheated? You returned your non working phone for a phone that does work and passed another round of QC. I don't see the problem here.
Click to expand...
Click to collapse
I feel cheated because using electronics puts on wear. The processor, the OLEDs, every piece of silicon in the phone is subject to degradation based on the amount of use, heat, liquid and impact its exposed to. By definition, the refurb is a phone that had some issue and was repaired.
I don't know what the phone has been exposed to prior to me receiving it. For all I know they re-flashed someones highly used phone stuck it in a new case/bezel and sent it to me. Any additional wear may down the road effect the performance of my phone. Its the same reason that the display unit at most stores is sold at a discount.
As to your talk of QC. They actually sent me 2 refurbs. The first one was put back together incorrectly & the battery door wouldn't close, so I had to return that one immediately after opening the box.

sololhj said:
I feel cheated because using electronics puts on wear. The processor, the OLEDs, every piece of silicon in the phone is subject to degradation based on the amount of use, heat, liquid and impact its exposed to. By definition, the refurb is a phone that had some issue and was repaired.
I don't know what the phone has been exposed to prior to me receiving it. For all I know they re-flashed someones highly used phone stuck it in a new case/bezel and sent it to me. Any additional wear may down the road effect the performance of my phone. Its the same reason that the display unit at most stores is sold at a discount.
As to your talk of QC. They actually sent me 2 refurbs. The first one was put back together incorrectly & the battery door wouldn't close, so I had to return that one immediately after opening the box.
Click to expand...
Click to collapse
Even if you buy new or get new for a replacement, you're still subject to the same problems that could arise, as you've already experienced. As for your other points, the phone has been out for a few months. I think you need to relax a little bit if you have legitimate issues, verizon will give you another refurb as you've already had to do.
Just because it's new doesn't make it impervious, as again you've already seen.

This was replaced under warranty so you should, in my opinion, have gotten a brand new phone. It's not like it was replaced out of warranty by an insurance company. You paid for a new phone that was defective at the fault of Samsung. It was not your fault. I'd contact Verizon AND Samsung and complain. Rerburb is NOT new. I call refurbished items used because that's a better definition of what they are.

I agree with sololhj. Even though the phone works and went through further qc, it's still not new. I paid for a new phone, I want a new phone. On my last phone there were issues, so I had it replaced. I got sent a refurbished one and it just wasn't the same. Weird feeling, hard to explain lol.
Sent from my SPH-L710 using xda app-developers app

mustbepbs said:
Even if you buy new or get new for a replacement, you're still subject to the same problems that could arise, as you've already experienced. As for your other points, the phone has been out for a few months. I think you need to relax a little bit if you have legitimate issues, verizon will give you another refurb as you've already had to do.
Just because it's new doesn't make it impervious, as again you've already seen.
Click to expand...
Click to collapse
Of course the same problems could arise, in fact I don't even blame Samsung for my phone bricking itself in the first. I probably just got a bad piece of silicon. The whole reason I started this thread is because now that this phone has been out for a month I thought I would have heard of this happening to someone else, but apparently it hasn't.
The point is, what if this phone belonged to a fellow XDA member who had a custom kernel running and had the cpu overclocked to 3GHZ, burning a whole in the phone? Then because of some other issue he reflashed the stock ROM, used the flash counter hack to return the phone to normal and returned it to Verizon.
Now that's my phone and all that wear & tear is on the chip potentially reducing its overall life. Aren't I entitled to a new unused piece of silicon, even if the probability of it having issues is the same as the refurb I received?

sololhj said:
Of course the same problems could arise, in fact I don't even blame Samsung for my phone bricking itself in the first. I probably just got a bad piece of silicon. The whole reason I started this thread is because now that this phone has been out for a month I thought I would have heard of this happening to someone else, but apparently it hasn't.
The point is, what if this phone belonged to a fellow XDA member who had a custom kernel running and had the cpu overclocked to 3GHZ, burning a whole in the phone? Then because of some other issue he reflashed the stock ROM, used the flash counter hack to return the phone to normal and returned it to Verizon.
Now that's my phone and all that wear & tear is on the chip potentially reducing its overall life. Aren't I entitled to a new unused piece of silicon, even if the probability of it having issues is the same as the refurb I received?
Click to expand...
Click to collapse
Yeah if you bought it in the last 14 days, verizon should give you a new one. Maybe I'm just not that paranoid about refurbished things as others.

[Q] What to check when getting a new phone?

I am buying a smartphone for the first time, and I am getting it unlocked, since unlocked devices don't any warranty, I should check everything while I still have time to return it. so besides scratches and visible defects, what else should I check when I get a new phone? I also like to know how can I make sure that it is a new device, and not used?
I am going to get something like Note 2, if it makes any difference.

MikeAlfa said:
I am buying a smartphone for the first time, and I am getting it unlocked, since unlocked devices don't any warranty, I should check everything while I still have time to return it. so besides scratches and visible defects, what else should I check when I get a new phone? I also like to know how can I make sure that it is a new device, and not used?
I am going to get something like Note 2, if it makes any difference.
Click to expand...
Click to collapse
I've bought a few used smart phones and it's gotten easier every time. Visible defects happen with any used device, be sure of the obvious, it turns on, the screen works, buttons work, battery charges, sound works, head phone jack works and that it can be activated with your provider.
Sent from my GT-N5110 using xda app-developers app

Try *#0*# on dialer

Won't turn on, tried everything i know.

Recently my S2 skyrocket turned off for no reason. I just wanted to check the time and it was off. 5 mins before was doing good and I was using it as always. Battery was 80% charged and in good conditions. Tried turning it on, it didn't. Pulled out the battery couple of times, didn't help. So when I went home I plugged the charger and tried with and without battery, no reaction at all. Tried to boot into recovery and download mode, nothing. Went to a local phone repairer and told me it was a problem about an internal part, something like ' memory chip' (don't know if I'm saying it right in english) He said it happens a lot with galaxy s2 and s3 phones.It would cost about 40$ to repair. I don't know if it's worth since the phone is too old now and not sure how much it'll resist or maybe this problem occurs again in no time. So I would appreciate if somebody knows anything, even a little might help me. Thanks.
Note: Phone was sim unlocked, using it in europe. No root, stock jellybean. (Done rooting and flashings before but it was all stock at the time)

Some time it happens if your motherboard is affected by VIRUS!!! In this situation you have no option rather than replacing it..

Sounds like hardware failure. Is it worth $40 to fix it? Up to you, although I would like to point out that the most modern replacements for the SR: the M8, S5 and G3, are all at least $200 through AT&T right now. The Rocket may not be worth fixing from a "what's the phone worth" point of view, but if you're not willing or able to dish out that much cash, the cost of repairing vs. upgrading might make repairing the older phone worthwhile.

T.J. Bender said:
Sounds like hardware failure. Is it worth $40 to fix it? Up to you, although I would like to point out that the most modern replacements for the SR: the M8, S5 and G3, are all at least $200 through AT&T right now. The Rocket may not be worth fixing from a "what's the phone worth" point of view, but if you're not willing or able to dish out that much cash, the cost of repairing vs. upgrading might make repairing the older phone worthwhile.
Click to expand...
Click to collapse
Well that's the problem. I don't feel like spending again for a new phone, the rocket was fairly good for my needs so I'm going with the repairing. It's a bit much for me but anyway I need the phone now. Kinda strange how a failure can happen like this and without a good reason, no signs of any problems at all.

$40 bucks is not bad, u could still sell afterwards for >$100

vincom said:
$40 bucks is not bad, u could still sell afterwards for >$100
Click to expand...
Click to collapse
Nobody would buy it in my contry Anyway they told me it can't be repaired. Sent it to 3 different places. They all told me it 'died' . Using a piece of crap now as my daily phone -.-"

Question Screen weirdness on me the other day.

My pixel 7 pro freaked out on me the other day and went black on me when I played a game and didn't come back for over 15 minutes then finally was responding again. Any reason why this happened . Hopefully software and not hardware. Hasn't happened since but still concerning .

Anyone ?

Redbeardkevv said:
Anyone ?
Click to expand...
Click to collapse
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.

jaseman said:
Flaky game? I never play games on any tool, which a smartphone is. I wish the OEM's would stop trying to make it even possible. Buy a "gaming" phone which is designed specifically for that purpose. In fact, some of the best phones available today (spec wise) are gaming phones! If it only happened while playing the game then that is where I would look.
Click to expand...
Click to collapse
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.

EtherealRemnant said:
This is one of the most ridiculous responses I have ever seen. There is nothing that makes a "gaming phone" special. They're using the same hardware and software as any other phone with gaming-specific gimmicks. The phone has a throttle mechanism to prevent any kind of damage.
Click to expand...
Click to collapse
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?

Hmmm

jaseman said:
Ridiculous...maybe...but the fact remains that you experienced this WHILE playing a game! So I wonder what the problem may be?
Click to expand...
Click to collapse
That's called a hardware defect if the hardware can't cope. Going blank for 15 minutes is not normal.

Hardware hmm and not software?

Redbeardkevv said:
Hardware hmm and not software?
Click to expand...
Click to collapse
What were you playing? If it was a graphically intensive game, I would definitely lean more towards blaming the hardware. It's very rare that a game can actually make a phone that unstable. In fact I can't remember the last time I've had a game make my phone unresponsive.

Roblox with my nephew

Redbeardkevv said:
Roblox with my nephew
Click to expand...
Click to collapse
I've never played that game but their site seems to suggest some rather low requirements so I would be shocked if an ARMv8 processor like Tensor 2 is going to struggle with it.
Android warning screens
Due to the very large number of Android devices in existence, we cannot be certain that all devices will run optimally even if they are running the correct version of the operating system and do not have a Tegra 2 chipset.
We have 2 levels of unsupported Android devices - skippable and unskippable:
Skippable Devices: These types of devices will get a warning telling you that your device may not be powerful enough to play experiences smoothly. This is just a warning to let you know that while your device isn't specifically supported, experiences might still run though they will likely lag a little (or a lot). Tapping outside the warning box will make it go away and the experience should keep loading.
Unskippable Devices: will get a message that informs you that your device doesn't meet the minimum system requirements. This means the device is not able to play experiences on Roblox. This message usually shows up on devices that use the Tegra 2 graphics chipset or a processor older than ARMv7. These kinds of tablets/phones do not support features that the Roblox needs to be able to function. However, users with these unskippable messages will still be able to access all other parts of the app outside of experiences.
Click to expand...
Click to collapse
https://en.help.roblox.com/hc/en-us/articles/203625474-ROBLOX-Mobile-System-Requirements

Yea I was thinking it had low requirements. Maybe bad coding ??? But then again no other app or game has caused that to happen. Sooo. Yea

I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
I've had a few wonky screen issues that hard locked my phone. Had one go black, but fortunately came back after holding power down. It once went all yellow with weird shapes/sections. And then just had some freezes with artifacts on the screen.
I'm going away for the holidays so I'll send it back when I get home if I'm still having issues. If you're going away, I'd suggest taking a backup phone just in case. Had mine die the first time when I was visiting my folks out of state. It sucked with no backup.
One thing I noticed is the screen does a fuzzy flash whenever I plug in a USB charger. It's only a split second but it is noticeable. Has anyone else experienced that?

Superguy said:
I don't think it's software. I already had one screen die. Went black and never came back on. I had it fixed under warranty at a local UbreakIFix (Asurion - Google's warranty partner). Techs were aware of a similar problem with the 5a and replaced my screen same day.
Click to expand...
Click to collapse
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.

V0latyle said:
Most of these failures have been a combination of both hardware and software - nothing is actually wrong with the screen. I'm not sure exactly how it happens, but it seems that this usually involves a OS crash (phone freezing up) followed by an attempt to reboot, but for some reason the bootloader has become corrupted and the device won't start. Fixing it generally involves replacing the mainboard, because most repair centers don't have the QPST or the software needed to perform low level reflash. This is a known issue over several generations of Pixels; the cause is unknown.
Click to expand...
Click to collapse
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev

Superguy said:
What was weird is when mine went black, the phone would still boot and in theory was still usable. Pushing the buttons gave haptic feedback like they were bringing up the power menu or adjusting the volume. I just couldn't see what was going on or use touch to give input.
Click to expand...
Click to collapse
Yeah, that's definitely a display issue. I'm talking about when the device doesn't work or respond at all, maybe vibrates on power up but doesn't respond to anything, and usually will come up as "Qualcomm Bulk USB" or something when connected to PC
Superguy said:
They told me they just replaced the screen. Didn't touch the motherboard.
I was using one of the custom kernels so I ended up having to wipe it and went back to stock kernel with magisk and some modules. It hasn't acted up as much as it did with the custom kernel, but there are still issues. I suppose it could be something that's messed up in the stock kernel, and perhaps tweaks a dev made in theirs may have exasperated it some.
If I end ups ending it back, I'll try a custom kernel again, but for now, I'm just sticking with stock.
*no disrespect intended or implied to any dev
Click to expand...
Click to collapse
For sure, active development may or may not have stability issues, it's all a learning process!