Develop Bugs

$50 credit from Sprint for LOS

After seeing so many people with LOS issues (myself being one of them) I figured I was due some credit back from Sprint for my trouble. I called and got in touch with a rep who wanted to troubleshoot my phone for the problems. This is my only phone and I explanined that it is a widespread issue and that a large amount of people in forums, including the Sprint forum, are experiencing the same problems. She offered to give me a replacement phone. I explained that it wouldn't do myself, Sprint, or Samsung any favors to replace the phone when it was most likely a firmware/OS/software related issue. She offered to give me a different model. I politely refused and mentioned that I know Sprint is aware of the issue and is most likely diligently working to solve it. I only wanted some sort of reimbursement for the LOS that has happened and may continue to happen until said update arrives. She asked me to hold while she spoke to her superior. When she returned, she said she could give me a $50 credit for the inconvenience. However, if I continue to experience the same problem, they will not be able to offer any more reimbursements. I should then run through any troubleshooting that they ask me to do and possibly get a replacement. She strongly suggested that I take it in for inspection at a sprint store. I may do this. But, I would really like to have a stock ROM to flash in Odin before I do that. I can just hear the tech tell me how it was all the fault of rooting that wrecked the radio.
I would like to stress the point that I was very polite, calm, reasonable, and understanding of what she had to do while speaking to the rep.

You are giving their average tech far too much credit. Apologies to any in present company...though you likely know precisely what I mean. (If you are here you aren't their "average" guy)

buggerritt said:
After seeing so many people with LOS issues (myself being one of them) I figured I was due some credit back from Sprint for my trouble. I called and got in touch with a rep who wanted to troubleshoot my phone for the problems. This is my only phone and I explanined that it is a widespread issue and that a large amount of people in forums, including the Sprint forum, are experiencing the same problems. She offered to give me a replacement phone. I explained that it wouldn't do myself, Sprint, or Samsung any favors to replace the phone when it was most likely a firmware/OS/software related issue. She offered to give me a different model. I politely refused and mentioned that I know Sprint is aware of the issue and is most likely diligently working to solve it. I only wanted some sort of reimbursement for the LOS that has happened and may continue to happen until said update arrives. She asked me to hold while she spoke to her superior. When she returned, she said she could give me a $50 credit for the inconvenience. However, if I continue to experience the same problem, they will not be able to offer any more reimbursements. I should then run through any troubleshooting that they ask me to do and possibly get a replacement. She strongly suggested that I take it in for inspection at a sprint store. I may do this. But, I would really like to have a stock ROM to flash in Odin before I do that. I can just hear the tech tell me how it was all the fault of rooting that wrecked the radio.
I would like to stress the point that I was very polite, calm, reasonable, and understanding of what she had to do while speaking to the rep.
Click to expand...
Click to collapse
This is a great tip. I'll be calling in tomorrow to describe my LOS, too! (And, of course, I'll be calm, polite, and understanding....)

daneurysm said:
You are giving their average tech far too much credit. Apologies to any in present company...though you likely know precisely what I mean. (If you are here you aren't their "average" guy)
Click to expand...
Click to collapse
They have a set group of questions they are required to ask, troubleshooting that they are required to do, and are not able to offer the type of technical support that you can get in a forum. The corporation will not allow them to. Every call in is recorded and statistics are most likely kept on how to keep the average customer happy with minimal effort. This sets guidelines that are enforced on their employees. Your best bet is to be polite, and kind with them. They have to do their job and as long as you stay politely firm in what you want, generally, you will get your way. Being rude, arrogant, demeaning, or negative with them will only get you a headache and them another ****ty day at work with a story to tell in the breakroom about the last arsehole who called in and thought he/she was "somebody".

buggerritt said:
They have a set group of questions they are required to ask, troubleshooting that they are required to do, and are not able to offer the type of technical support that you can get in a forum. The corporation will not allow them to. Every call in is recorded and statistics are most likely kept on how to keep the average customer happy with minimal effort. This sets guidelines that are enforced on their employees. Your best bet is to be polite, and kind with them. They have to do their job and as long as you stay politely firm in what you want, generally, you will get your way. Being rude, arrogant, demeaning, or negative with them will only get you a headache and them another ****ty day at work with a story to tell in the breakroom about the last arsehole who called in and thought he/she was "somebody".
Click to expand...
Click to collapse
Oh, I'm well aware of that. Perhaps I should have been more specific in what I was referring to:
I can just hear the tech tell me how it was all the fault of rooting that wrecked the radio.
Click to expand...
Click to collapse

You have obviously rooted your phone when many pointed out that zedo causes los. Your noise about phone quality given this fact is just disturbing. I suggest you back off to stock kernal plus root that has fixed los for many including myself. And be honest with sprint that you did so instead of generating fud so they can focus on real issues.
Sent from my SPH-D710 using XDA App

LOS has nothing to do with root.
Sent from my SPH-D710 using XDA App

jamescho72 said:
You have obviously rooted your phone when many pointed out that zedo causes los. Your noise about phone quality given this fact is just disturbing. I suggest you back off to stock kernal plus root that has fixed los for many including myself. And be honest with sprint that you did so instead of generating fud so they can focus on real issues.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
You are completely mistaken and are barking up the wrong tree. LOS is happening to many who have not rooted their phones. If you are not experiencing LOS anymore after flashing back to stock kernal, it is purely a coincidence. I have given no "noise about phone quality". You should take a read of my post and read it in full, again. I plainly said that it was a software related issue and that Sprint is aware of it. Sprint and Samsung are working on fixing it. Links have been posted numerous times as to Samsung and Sprint being aware of the problems. Everyone who has said that Zedo's kernal has caused this has been mistaken. People who have never even heard of Zedo's kernal are having the same troubles. Please read read read before flaming. I will not reply to any more ignorant remarks when it is obvious that the flamer has misread the OP, jumped to conclusions, and flew off on a delirious tantrum.

So should I call and get $50 too? I haven't lost anything to wanna ask for a reimbursement even if I have LOS all I do is reboot...I'm not losing anything...nothing is perfect
Sent from my Epic touch 4G using xda premium

buggerritt said:
You are completely mistaken and are barking up the wrong tree. LOS is happening to many who have not rooted their phones. If you are not experiencing LOS anymore after flashing back to stock kernal, it is purely a coincidence. I have given no "noise about phone quality". You should take a read of my post and read it in full, again. I plainly said that it was a software related issue and that Sprint is aware of it. Sprint and Samsung are working on fixing it. Links have been posted numerous times as to Samsung and Sprint being aware of the problems. Everyone who has said that Zedo's kernal has caused this has been mistaken. People who have never even heard of Zedo's kernal are having the same troubles. Please read read read before flaming. I will not reply to any more ignorant remarks when it is obvious that the flamer has misread the OP, jumped to conclusions, and flew off on a delirious tantrum.
Click to expand...
Click to collapse
LOS was caused for me through rooting. I can't speak for everyone but I can say that it did cause LOS for my device and probably others. You said it was inconvenience for you to have to go through this and mention maybe even taking your phone in for repair. You really can't blame others for assuming you are dealing with the LOS issues. And if you are not I don't really understand why you called Sprint to complain about this issue.
Maybe you should take a longer look at what you posted before deciding rather or not someone misread you. Though, it would probably be a waste of time. You've already proved to be oblivious to the fact that root is causing LOS for a lot of users.
jeffyv2 said:
So should I call and get $50 too? I haven't lost anything to wanna ask for a reimbursement even if I have LOS all I do is reboot...I'm not losing anything...nothing is perfect
Sent from my Epic touch 4G using xda premium
Click to expand...
Click to collapse
You apparently don't use your phone much for calls and text. My work calls me and will expect me to respond soon. Missing important phone calls can be really costly for me. I have standards, they don't have to be perfect but I do expect it to meet my standards. What is the point of having it if it doesn't?

jeffyv2 said:
So should I call and get $50 too? I haven't lost anything to wanna ask for a reimbursement even if I have LOS all I do is reboot...I'm not losing anything...nothing is perfect
Sent from my Epic touch 4G using xda premium
Click to expand...
Click to collapse
Do whatever you feel is ethical. I have lost plenty. I've lost business calls, missed potential appointments with clients, and numerous personal calls. I got the messages late and missed out on money and activities that I would have been involved in if I had the service that I pay a premium to rely on. The $50 doesn't come close to covering that. But, I feel that it is an act of good character that they gave it to me. I wouldn't have called and asked for it, if I didn't feel that I deserved it after being a loyal customer for over 12 years. It shouldn't be my responsibility to have to make sure I look and see if I have service every 5 minutes, when I am in an area that normally gets amazing 4G signal. I'm glad you haven't lost anything and I hope that continues for you.
BTW, I had LOS before flashing anything.

jamescho72 said:
You have obviously rooted your phone when many pointed out that zedo causes los. Your noise about phone quality given this fact is just disturbing. I suggest you back off to stock kernal plus root that has fixed los for many including myself. And be honest with sprint that you did so instead of generating fud so they can focus on real issues.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I havnt done a single thing to my phone other than change launchers and I get LOS. Havnt rooted it, havnt even wanted to yet. This is a real problem and I hope people do continue to call in a try to get money from sprint. If this continues then they might notice, "hey maybe we should fix this problem because its costing us 50 dollars worth of credit per customer that calls in to *****". Obviously that last part is wishful thinking thought. But come on dude, no need to flame someone like that, (especially when youre wrong).

jamescho72 said:
You have obviously rooted your phone when many pointed out that zedo causes los. Your noise about phone quality given this fact is just disturbing. I suggest you back off to stock kernal plus root that has fixed los for many including myself. And be honest with sprint that you did so instead of generating fud so they can focus on real issues.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I'm not on Zedo's kernel and I have LOS. I've had LOS on Stock without root, stock with root, v3 and v5 of ACS's kernel. Only one I haven't had LOS on is Zedo's, and that's cause I haven't tried it. Take your smug ass comments somewhere else.

I get los at work every time I bend over or kneel down to repair something,and it keeps powering down and back on. But I fixed it by moving my case to the side of my belt. My body blocked the signal and pushed the power button
Sent from my SPH-D710 using XDA App

djjosh said:
I get los at work every time I bend over or kneel down to repair something,and it keeps powering down and back on. But I fixed it by moving my case to the side of my belt. My body blocked the signal and pushed the power button
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I almost fell off my chair and **** myself after reading this.

That was not a joke, its true if you have a leather pouch put it on the front of your belt and tie your shoes it will loose signal an probaby sqeeze the power button
Would be funny if I was complaning and mad
Sent from my SPH-D710 using XDA App

djjosh said:
That was not a joke, its true if you have a leather pouch put it on the front of your belt and tie your shoes it will loose signal an probaby sqeeze the power button
Would be funny if I was complaning and mad
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
OMG! Tears are streaming. Please stop before the convulsions set in.

It just did it again dangit im trading for a Zio
Sent from my SPH-D710 using XDA App

Its not a ROM issue. If you live or travel in an area with ****ty signal you will get it. I had it about 7 times today. I ended up just turning the phone off. Basically if the phone loses signal you have to reboot.
Now I realize that many of you live in your mom's basement, work at the McD around the corner, and have a sprint tower in your back yard so you think the rest of us are crazy. No, the rest of us travel and enter areas where sprint coverage sucks.
Using roam control and leaving the phone on roaming I don't get the LOS unless I get deep into a building and lose the verizon signal.

eagercrow said:
Its not a ROM issue. If you live or travel in an area with ****ty signal you will get it. I had it about 7 times today. I ended up just turning the phone off. Basically if the phone loses signal you have to reboot.
Now I realize that many of you live in your mom's basement, work at the McD around the corner, and have a sprint tower in your back yard so you think the rest of us are crazy. No, the rest of us travel and enter areas where sprint coverage sucks.
Using roam control and leaving the phone on roaming I don't get the LOS unless I get deep into a building and lose the verizon signal.
Click to expand...
Click to collapse
I live in a great spot with excellent 4G coverage. I live on my own, work for myself and am kind of crazy myself so I kind of have a right to call others crazy. I am getting the LOS bug randomly and frequently. I have full bars here at home. It just dies and gives the dead circle. It just did it less than half hour ago. It also did it numerous times while working in the field, as well..
Some say that it is fixed by resetting their MSL. Some say they fixed it by flashing a certain kernal. Some believe that if you keister a pine cone and scrub your face with lemon custard that it will fix it, too. None of these things...er...has worked for me.

Serious camera issues...

Hi all,
I got my One X a few weeks ago, very soon after launch (O2). Initially I was very happy with my purchase but now I'm left extremely frustrated with this handset and regretting buying it - screen flicker, dropped calls, lots of little bugs, and now... The camera won't work!
I've been using it quite a bit since I bought it, but yesterday I was using it (no settings changed) and each time I took a picture there was either corruption in the image or a blank image with an exclamation mark icon instead of the picture. This now seems to happen almost every time I try to take a shot - I've done the following in an attempt to rectify:
1. Reboot handset
2. Ensured no other apps are running prior to using camera
3. Reset camera settings to default
4. Ensured phone was fully charged
5. Ensured I have enough free storage space (~22GB free)
I'm not going to perform a factory reset because I'm not convinced it's going to help anything AND I shouldn't really have to do that! I haven't got time to completely reconfigure my phone.
Still, I'm unable to take a photo and this is *really* annoying me! A premium handset with issues all over the place... Unacceptable!
Now I'm left thinking I'm going to go back to O2 and demand replacement with a SGS3, because by the looks of things HTC haven't actually fixed most of the bugs we're all experiencing.
Such a shame - had so much potential and a genuinely amazing device to pick up and use in many ways, but it's quite frankly not fit for purpose if I can't make reliable calls, take pictures or use the screen without serious flickering.
Has anyone else experienced these camera issues I described above?
Apologies for the tl;dr, just a very frustrated HOX owner.

So because you got a faulty phone all the others out there are not fit for purpose?
OK got ya that seems fair

There's something wrong with your particular phone, just get it replaced. The vast majority of people have no flaws whatsoever.

Lol... They won't offer a refund until you do a factory reset. I guarantee a factory reset will fix the problem. Stop having a cry are you 12 or something.
Sent from my HTC One X using Tapatalk 2

nikorette said:
Lol... They won't offer a refund until you do a factory reset. I guarantee a factory reset will fix the problem. Stop having a cry are you 12 or something.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Oh the irony of a childish response like that. That's how keyboard warriors really show their age.
For the record no, I'm significantly older and understandably annoyed by the poor quality of a ~£500 handset that I worked hard to pay for.
And as for the vast majority of people having no flaws - really?! I don't believe that for a second - by the looks of most of the boards a high proportion of HOX handsets have issues.
So yeah, I'm quite understandably frustrated - didn't realise how defensive this forum is lol

adamsharif said:
And as for the vast majority of people having no flaws - really?! I don't believe that for a second - by the looks of most of the boards a high proportion of HOX handsets have issues.
Click to expand...
Click to collapse
Yes really. It'd be incredibly foolish to assume that XDA users are representative of the majority of phone users and even more foolish to assume that people who have flawless phones will be just as vociferous as those with flawed phones.
So yeah, I'm quite understandably frustrated - didn't realise how defensive this forum is lol
Click to expand...
Click to collapse
Why don't you try and reflash your phone with a RUU or return it for replacement?

Well that's what I've done - just booked it in with O2 so will see what happens.
Still interested to know whether anyone has had this camera issue though?

adamsharif said:
Oh the irony of a childish response like that. That's how keyboard warriors really show their age.
For the record no, I'm significantly older and understandably annoyed by the poor quality of a ~£500 handset that I worked hard to pay for.
And as for the vast majority of people having no flaws - really?! I don't believe that for a second - by the looks of most of the boards a high proportion of HOX handsets have issues.
So yeah, I'm quite understandably frustrated - didn't realise how defensive this forum is lol
Click to expand...
Click to collapse
No just no. A high proportion of XDA USERS' HOX's have problems. Maybe because most have noticed a problem and have done a google search to find xda as one of the first links. They sign up and vote/make a topic about their problem, now to you and the rest of us it looks like most of the handsets are suffering from some sort of problem.
Most take this on board without looking at the big picture, those normal run of the mill users that don't have any use for xda, don't post about problems because they don't have any.
Stop being so closed minded xda is not the be all and end all of android. There are users out there that have never herd of xda or even ics.
It's pointless complaining here with such an aggressive attitude just do the factory reset and be done with it atleast if you do it now you'll be able to backup your apps via abd/fastboot.
IMHO your just childish, you need to suck it up and stop being such a girl.
Sent from my HTC One X using Tapatalk 2

nikorette said:
No just no. A high proportion of XDA USERS' HOX's have problems. Maybe because most have noticed a problem and have done a google search to find xda as one of the first links. They sign up and vote/make a topic about their problem, now to you and the rest of us it looks like most of the handsets are suffering from some sort of problem.
Most take this on board without looking at the big picture, those normal run of the mill users that don't have any use for xda, don't post about problems because they don't have any.
Stop being so closed minded xda is not the be all and end all of android. There are users out there that have never herd of xda or even ics.
It's pointless complaining here with such an aggressive attitude just do the factory reset and be done with it atleast if you do it now you'll be able to backup your apps via abd/fastboot.
IMHO your just childish, you need to suck it up and stop being such a girl.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Right, so how about the fact that I've actually read a variety of other forums including some of the operators' own too? You have ASSUMED that I have only looked at XDA.
Aggressive?! Childish?! I think you're reading into things too much here... What part of "man pays relatively large sum for device and is disappointed by its many flaws" do you not get?
Anyway, this is boring me; I guess I'll never know if anyone else actually has the same camera issues...

Lol you still don't get it. Some people just do not know about forums. Unless you get a number from HTC that states how many returns per device made. Nobody, not you or me will know. Not reading anything other than what's on my screen. I'm defensive, by logic you're aggressive.
I guess you won't. Everyone else just ran a factory reset instead of crying about it.
Anyway like most of the threads on here its no longer about the op's post and more about the ego of the people posting. I'll admit I am at fault sorry if I derailed your thread..
Sent from my HTC One X using Tapatalk 2

Did u updated to 1.28? In 1.26 some pics cannot be processed,this has been solved completely in .1.28
Sent from my HTC One X using XDA

Adamsharif;
You do seem to have a phone that, under UK law does not appear to be fit for the purpose for which it is intended, regardless of the warranty obligations of HTC.
In reality, you should back everything up and factory reset the phone, if only to rule out any problems which could be solved, by doing this. If then, the phone does not work, you are well within your rights to demand a refund or a replacement.

If you're not willing to do a simple reset to fix potential issue, HTC and the users here are definitely not going to be willing to help you out. We can't reset the phone for you, but you still want to fix it by using and looking at the phone until it behaves itself.

adamsharif said:
Right, so how about the fact that I've actually read a variety of other forums including some of the operators' own too? You have ASSUMED that I have only looked at XDA.
Aggressive?! Childish?! I think you're reading into things too much here... What part of "man pays relatively large sum for device and is disappointed by its many flaws" do you not get?
Anyway, this is boring me; I guess I'll never know if anyone else actually has the same camera issues...
Click to expand...
Click to collapse
Here you go, proof that the majority of XDA members have no issues whatsoever with their device.
http://forum.xda-developers.com/showthread.php?t=1585082
Of course, people with no problems don't post much on forums, so the actual, real-world results of such a poll would be MUCH more one-sided.
As for your camera problem, many people have suggested fixes; Factory Reset, re-flashing RUU and, if all else fails, return the device and get a refund/replacement.
People seem to think their £500 device is going to be perfect. Don't get me wrong, It SHOULD be perfect, but no device is ever going to be. The HTC One X issues are also relatively minor compared to some devices that came before it.

kannanX10 said:
Did u updated to 1.28? In 1.26 some pics cannot be processed,this has been solved completely in .1.28
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Exactly. There's an old thread about this issue. Fixed with 1.28
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

Ok, I guess I shouldn't have been so stubborn - currently backing up the device and will do a factory reset.
The backlight issue, however, is the one I'm returning for - the thing I find strange about both that and the camera issue is that they suddenly appear which really makes me feel that there are hardware issues in the first batch.
Lesson learned - don't buy a handset as soon as it comes out!
Personally I feel that mobile manufacturers need to undertake better testing and not rush their products to market - if you look at many of the recent handsets from Apple, Samsung, HTC there have been a lot of silly issues which have damaged reputations.
If I can have a HOX with working camera, backlight and calling it will be the perfect device!

You don't want to change your phone and yet you can't live with the problems. What do you want? Just ranting? Got it.
Sent from my HTC One X using XDA

ALL THE CORRUPTION ISSUES EXCEPT FLICKER are solved by firmware 1.29
My new hox was updated to 1.29 two days after I bought it, I never encountered the said issues, also flicker is related to overheat on 1.29 the phone temperature is a lot better
you regret buying the most praised and critically acclaimed android phone lol

I think we're being a little harsh on adamsharif, I love my HOX but its not without it's flaws and some of the 1.26 bugs were just messy...the phone shouldn't have been released with this firmware...it was rushed but I can understand why with the SG3 looming!
Unfortunately the average user turns to a forum when he / she has issues, the average user doesn't sign up to XDA to just say how happy they are, some do, just not your average joe, so it all looks like doom & gloom!
£500 is a lot of money, should we have to factory reset it after a few days / weeks? Should we not expect a near perfect product considering the money spent....I don't know....android isnt a perfect OS so I think the arsehole answer is get an iPhone!? I think in 3 months time we'll all be happier and mostly problem free!
Sent from my HTC One X using XDA

Guys please stop the pointless comments.
Back on topic. I suggest you try a third party camera app from market and see if that works. If it works, i too believe that hard reset will solve the problem. Also, don't underestimate hard reset. It usually solves most unknown issues

Freezing a lot lately..

My galaxy has been freezing a lot lately and the only way to fix is to pull battery. Any ideas how to fix this? Stock jellybean rooted.
Sent from my SPH-L710 using xda app-developers app

I've been having this issue also, it keeps getting worse. It seems like something is not getting cleared because after a clean wipe/flash everything is fine. Then as time goes on it starts happening again. I thought it might just be a rogue app, so I didn't install or restore anything and it eventually freezes. I think it may be a JB issue because I've seen people with other phones post about it as well. Maybe someone else can shed some light on this.

metalfan78 said:
I've been having this issue also, it keeps getting worse. It seems like something is not getting cleared because after a clean wipe/flash everything is fine. Then as time goes on it starts happening again. I thought it might just be a rogue app, so I didn't install or restore anything and it eventually freezes. I think it may be a JB issue because I've seen people with other phones post about it as well. Maybe someone else can shed some light on this.
Click to expand...
Click to collapse
I tried clearing cache, seems to work for now..
Sent from my SPH-L710 using xda app-developers app

That worked for me for a day, it just did it twice since I posted. I'm not sure what to do next. I guess I'll go to sprint, they replaced it once already because of this about a month ago.

metalfan78 said:
That worked for me for a day, it just did it twice since I posted. I'm not sure what to do next. I guess I'll go to sprint, they replaced it once already because of this about a month ago.
Click to expand...
Click to collapse
I really hope it doesn't come to that. It doesn't freeze for me on cm10. Just stock
Sent from my SPH-L710 using xda app-developers app

Maybe it's a touchwiz problem

metalfan78 said:
Maybe it's a touchwiz problem
Click to expand...
Click to collapse
Took mine in just now. They are gonna replace it. It froze while the guy was using it. I think the big man up top threw me a freebie because I forget to get rid of the root and all, but the sprint guy noticed how hot my phone gets (I thought it was normal but apparently not, he said it was borderline damaging my phone, been like that since the day I got it) and he said he was just gonna replace it right then and there. Getting it Wednesday. Glad he didn't see my clockworkmod.
But sprint is very good to me. Kinda sad they remember me because I come a lot since 2010.
Sent from a Nexus Galaxy S3 Running 4.1.2

Whiplashh said:
Took mine in just now. They are gonna replace it. It froze while the guy was using it. I think the big man up top threw me a freebie because I forget to get rid of the root and all, but the sprint guy noticed how hot my phone gets (I thought it was normal but apparently not, he said it was borderline damaging my phone, been like that since the day I got it) and he said he was just gonna replace it right then and there. Getting it Wednesday. Glad he didn't see my clockworkmod.
But sprint is very good to me. Kinda sad they remember me because I come a lot since 2010.
Sent from a Nexus Galaxy S3 Running 4.1.2
Click to expand...
Click to collapse
What's sad is a Sprint rep didn't see your ClockWorkMod...

They cover rooted phones. Really sounds like a hardware issue to me. Never had mine do anything like that and I've been rooted and custom from like the second hour I had the phone.

The Root said:
They cover rooted phones. Really sounds like a hardware issue to me. Never had mine do anything like that and I've been rooted and custom from like the second hour I had the phone.
Click to expand...
Click to collapse
I thought rooting your phone voided warranty? It is a hardware issue though..So i do see where you're coming from.

cbass15 said:
I thought rooting your phone voided warranty? It is a hardware issue though..So i do see where you're coming from.
Click to expand...
Click to collapse
It's really going to come down to store interpretation of the rules. Yeah, there are so many variables that could come with the rooting process itself it's also so unlikely to be the problem. The commonality of bad electronics is so, well....common and this does sound so hardware-ish. I'm absolutely certain some other store would have been jerks about it just because the store happened to hire jerks. Sounds like they get good people. I'd say write them a nice email. Try to add the guy's name in. At least help him get a better raise or something for his effort.

The Root said:
It's really going to come down to store interpretation of the rules. Yeah, there are so many variables that could come with the rooting process itself it's also so unlikely to be the problem. The commonality of bad electronics is so, well....common and this does sound so hardware-ish. I'm absolutely certain some other store would have been jerks about it just because the store happened to hire jerks. Sounds like they get good people. I'd say write them a nice email. Try to add the guy's name in. At least help him get a better raise or something for his effort.
Click to expand...
Click to collapse
Thank you for clearing this up. I'm with you on the hardware issue though, because if it freezes up for the basic scrolling then there is something wrong. Plus if it gets that hot that quick without much usage there is obviously something wrong.
My LCD went out and I had to go to 3 different Sprint stores just to get it fixed..

I hope it's not hardware related. This is the second phone that has done it and it takes about a month each time for the issue to show up. That could be a manufacturing defect, but it seems so rare and random.

cbass15 said:
I thought rooting your phone voided warranty? It is a hardware issue though..So i do see where you're coming from.
Click to expand...
Click to collapse
Yeah, in my sprint store I took my evo shift in rooted with an unlocked bootloader...they fixed it up temporarily and just told me to wait for a refurb :laugh:
Sent from my PG06100 using xda premium

I was hoping to avoid taking it in but since it keeps freezing and gets hot I guess I will go. Oh well. Thanks for all the input

cbass15 said:
What's sad is a Sprint rep didn't see your ClockWorkMod...
Click to expand...
Click to collapse
He would have if it didnt get to hot while he used it. While he was checking for normal freezing problems, it froze on him, and then right before he was about to factory reset it, he said he would just order a new one. He showed the other tech how hot it was and was amazed. It froze just from opening an app and scrolling,
and got hot with 3G turned on and the phone just sitting there. I've always used stock rooted, never flashed new kernel or anything. I think he might have noticed and just let it slide, because as I said before, I have been coming in since 2010 with legitimate reasons to replace phones. I just odin'd my phone after triangle away so it looks completely stock. Before that I backed up all my files with my backup, and when I get the new phone, I will just root it and restore. I'm lucky though. I told him that I have tried many factory resets and even the Odin ones where it wipes the internal memory and it still does it (which is true, I have). When I take it in, I could have acted dumb and said NY friend did that rooting so he could silences my camera blah blah, but I like to be honest.
metalfan78 said:
I was hoping to avoid taking it in but since it keeps freezing and gets hot I guess I will go. Oh well. Thanks for all the input
Click to expand...
Click to collapse
Just make sure you reset the flash counter and Odin it after you backup all the files you will need.
The Root said:
It's really going to come down to store interpretation of the rules. Yeah, there are so many variables that could come with the rooting process itself it's also so unlikely to be the problem. The commonality of bad electronics is so, well....common and this does sound so hardware-ish. I'm absolutely certain some other store would have been jerks about it just because the store happened to hire jerks. Sounds like they get good people. I'd say write them a nice email. Try to add the guy's name in. At least help him get a better raise or something for his effort.
Click to expand...
Click to collapse
I always try to do that. Every time I go in, the techs are so nice. They say sprint may call and text me about my store experience and they ask will you say you had a good one, and I always say I definitely will, but I never get that call or text. Didn't know you could email, so I will definitely do that now! Like I said, I have been where stores hire jerks, and tech wise, they have always been kind and willing to help. Maybe its because I'm straight forward with them, maybe not. If he would have asked if I rooted it I would have said yes. Thank you for the idea.
Sent from my SPH-L710 using xda app-developers app

The store I go to doesn't care about rooted phones

metalfan78 said:
The store I go to doesn't care about rooted phones
Click to expand...
Click to collapse
Well that's good. Just take it in and tell them what is going on. Glad I'm not the only one with the issue. I wasn't gonna take it in, but today it froze 6 times in a 30 min to and hour time interval and I decided it was time to. And I guess its not suppose to get that hot. Like I said, it did that from day one, so I thought it was normal lol.
Sent from my SPH-L710 using xda app-developers app

The Root said:
They cover rooted phones. Really sounds like a hardware issue to me. Never had mine do anything like that and I've been rooted and custom from like the second hour I had the phone.
Click to expand...
Click to collapse
Same way here lol.
Sent from my SPH-L710 using xda app-developers app

Is yours still freezing today? I was going to go to sprint after work but now mine won't freeze. I'm not sure if I should just go or not.

Galaxy Nexus death scheduled ?

Hi,
I've got my GN for about 2 years now. It always runned fine. I use it essentially to make calls, mails, some european "anti-cop" app called "icoyote", spotify and that's it
Everything stock, full google official, no cracked bull**** apps or whatever.
Ok so now for about 1 month it became less and less stable. It literally happened from one day to another. I guarantee i didn't add/change or remove anything.
Main issues are : spotify crashes many times (~20 to 50) a day and 50% of the time the GPS fix fails to go trough, but a simple reboot and it work's instantly.
So I tought I should make a full factory reset. I did that and the issues I was experiencing remained the same.
Now comes the 1million $ question : how the heck can something stop to work from one day to another ? If it was some *unpredicted*, classic hardware failure, a simple reboot would definitely not solve it, for sure.
Leading to think it has to be software related..OK, so a factory reset should solve : it doesn't neither.
Why are those apps crashing even in a very stock/factory config? I even did skip this google restore profile bull**** to be sure i'm workng in a perfect clean state.
The only logic conclusion is that there must be some kind of hard coded counter which reached the end and is now triggering randomly something, *i don't know based on what, or activated how* making this **** happen
It's very very very frustrating because it was working like a charm those past 2 years and i thought it was a good investment. I was obviously wrong, another death scheduled device.
Now with the 4.3, I got the feeling it becomes even worse. Today, I had to reboot 4 times to get a gps fix (working 100% of the time just after the reboot) and it was a hassle to get trough 2 songs without being cut off in the middle of it.
FU samsung

But you only tried to flash 4.3. It's like giving a patient only 1 medicine and when that not works declare him dead. There maybe other ways to revive your phone..
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
But you only tried to flash 4.3
Click to expand...
Click to collapse
when did i say that ? i'm done by years flashing a tool I use to work with. i'm not using it as a toy.
i received the update ota
there's nothing left to try, since my last basic test's where made in a official google factory default situation on a google phone
it's just stock u see? everything else i could try from this point would lead to a non-default situation making every further considerations totally pointless
Well, if i'm right, the so called "crash-routine" would *maybe* not be present in a custom rom, but, again, it worked before and has to work the same way now.
I refuse to use any other workarounds than factory resetting it and, since i already did that a few times, i'm done
i'm not awaiting some kind of help here. i'm just exposing my case and the frustration i'm feeling since samsung nicely dry-fcked me ^^

Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.

Read this. It's called Planned Obsolescence. Manufactures purposely make devices with limited lifespan in order to upgrade to their next new device.
http://en.m.wikipedia.org/wiki/Planned_obsolescence
Sent from my Galaxy Nexus using Tapatalk 2

Fastboot, Odin, omap.. All stock..
Sent from my Galaxy Nexus using XDA Premium HD app

johno86 said:
Don't know why you're acting up for no reason.
It doesn't take a genius to understand and figure out that applications designed and updated for 4.2.2 will most likely not work on 4.3 until the devs update it to work on 4.3. Which, from my experience, doesn't take long at all. That's probably one of the solutions to your few problems.
Way to take things a little too far and throw a tantrum rather than seeking help.
Also, if you have no intentions of seeking a fix then you didn't need to post anything at all.
You're not waiting around here for help? Well, I'm not going to offer help to someone with that kind of attitude.
Peace out you won't be missed.
BTW, there's nothing left to try? LOL
There's about 7 things left to try and one of them would have definitely worked 100%. Figure it out on your own since you know everything.
Click to expand...
Click to collapse
I ain't here to help either, i just couldn't agree more with what he said above... and its 2013, everyone knows that every electronic sh*t comes with a limited life span, if you didnt know that until now, i'm not sure where you been living..
Peace \m/.

Try wiping your SD card

Touch "gets stuck" on letters while typing

Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J

Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...

Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4

Go to the above mentioned link to see the entire discussion.
Right now, nobody 'official' is talking either way.
In fact the freezing isn't even being addressed by Google/ASUS in their 'update'.

I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app

I get this issue when playing a game or typing.

pheonix991 said:
I get this issue when playing a game or typing.
Click to expand...
Click to collapse
IXChicharitoXI said:
I've noticed this with SwiftKey. It doesn't happen often but sometimes it does.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Muikkuman said:
Are issues like hardware or software fault?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
danvee said:
Yep.
All part of the 'known' issues. Random rebooting, freezing, touch screen weirdness, etc.
Many more details here:
https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[526-550-false]
You're a member of a growing club...
Click to expand...
Click to collapse
Jaxione said:
Hi!
I have noticed another slight issue with my Nexus 7 2013. When typing touch sometimes gets "stuck" on a letter for a moment and that letter gets highlighted. During this brief moment I cant type.
Anyone else have this?
Br J
Click to expand...
Click to collapse
Well, I can give you some insight on this issue. I am working on this issue for some time and I am doing some research and tweaks with my device. I have enabled "show touches when registered" in developers option. I have always had this feature on since day one.
My device came without any problems apart from one non functional top speaker which is still not working till now. I even opened my nexus to see what could be the problem but I couldnot really find anything in the hardware.
However, when I upgraded my Nexus to the new version JSS15Q from JSS15J manually (I forced it, it didnot come on my device when I did) , I started to have little touch issues which I didnot have before. I only had one faulty speakers with no other issues and after the update I started to notice these little issues. In the beginning, however I was also facing jumpy touches (suddenly two words being typed or key stuck in one place or :silly: a word next to the word i am trying to type is typed instead ) issues which automatically were gone, not sure due to restarting it or the device settled itself or maybe me getting used to typing that way.
Now I am having issues of stuck keys.The key or game is stuck if my device is registering a touch although it shouldnot
.
I am planning to do a hard reset and clear wipes and cache and see what happens. If the problem persists, I will simply go back to Jss15j again.
This tells me that the issue for my device is simply SOFTWARE and not in the hardware. However, regarding some other issues like waking up device in its case automatically by light/magnetic sensors works sometimes and sometimes it doesnot especially after few minutes in sleep or if there is no opened app when the screen got into sleep. Yet, it will always turn on if it is connected to the charger. So there could be some earthing issues with the device too which could be taken care of by kernels. Or it maybe could be due to my case simply.
This concludes for me as simply softwares issues that are brought with 4.3 JB which I guess would be hopefully solved soon.
I am planning to visit Asus for fixing my speakers and I will try to see if they give me some heads up about jumpy touches and auto wake up issues.

Good thought, but current information is that 15Q contained a firmware update to the digitizer (or the likes), so reflashing 15J wouldn't change that. Apparently device firmware can only flash up.
Google /ASUS would need to package another update to do that. I'm sure they will if that's determined to be the problem.

Probably Google is loosing out on us. We have so many issues to be addressed. This Nexus seems to be a hurried productoin. I mean, like 2 - wait, 3 - Nexuses in one year....... man that's pretty obvious that Google is competing stupidly

This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.

That's odd indeed. I rarely type on my Nexus 7, but I do have this issue on 4.3 with my Nexus 4.
Sent from my Nexus 4 using Tapatalk 4

player911 said:
This is just our wonderful new software update.
Really glad in a way that more and more people are posting about this. After the update, everyone was shouting "ITS FIXED!!" when I never had problems before and now I do.
Click to expand...
Click to collapse
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.

OJ in Compton said:
There's really not much you can do when the statement of fixes from google bounces around the blogs (followed by the enthusiastic userbase) without any actual testing.
Still though, this is a weird issue because your device functions differently than mine. I'm not sure how Google can get all devices working properly with a single variant of the touchscreen firmware when there are likely hardware differences. The best solution to me would be something in the settings to calibrate the touchscreen or pick from different settings, but I doubt google has any interest in doing that.
It really sucks that we don't have a way to downgrade the touchscreen firmware because I never encountered any issues I have now on my device with a few days of moderate typing with the previous update.
Click to expand...
Click to collapse
They would have to have some sort of programming to determine what to do. Not saying there are 2 different firmwares or devices. But it is a huge issue for me.
I think it is probably the same on all devices but some just don't type enough or use it enough for it to become a problem. Maybe they don't know?
My touchscreen was a bit wonky before the new update, not saying it was perfect, but very manageable. Now its missing inputs, random ghost touches, stuck touches, etc.
I haven't seen any proof that there is a N7 running on 15Q with no touchscreen issues.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Touchscreen freezing totally is a new symptom of 15Q on mine.
Froze solid just using Tapatalk.
The power switch would activate the shutdown menu, but I couldn't select any option via screen. Volume control didn't do it either.
Had to hold power for 20 sec to shut it down.
Rebooted and all is well.
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:

danvee said:
But it's the opinion of some here (and possibly at Google /ASUS judging by their lack of timely action) that we effected people are statistically insignificant.....
They probably have the 'good', majority N7 2013s.
:banghead::banghead::banghead:
Click to expand...
Click to collapse
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates

I've had this problem too... Since I switched to PAC ROM and added the faux kernel it hasn't happened
Sent from my Nexus 7 using xda app-developers app

sfhub said:
I haven't forgotten you insignificant (statistically) folks...
Would you like to try this and give some feedback?
Take that multi-touch! Fix and lock in what works for YOU regardless of updates
Click to expand...
Click to collapse
Love to, and thanks for the hard work.
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices .... don't want to give them any.....
They've got us caught here: they're not doing anything effective, and we'd be penalized for using self-help.
I really hope that it solves at least the touch issues.

danvee said:
Problem is it requires unlocking the Bootloader.
Fully believing that warranty is going to come into play at some point I can't risk voiding it by doing that. I'm thinking they'll use any excuse not to cover these nuisance devices
Click to expand...
Click to collapse
I seriously doubt unlocking the bootloader will void the warranty
they actually can't legally just say you unlocked it therefore your warranty is void. They have to show how your unlocking caused the warranty issue you are complaining about. Look up Magnuson–Moss Warranty Act. It originally came about to protect car owners from dealerships voiding their warranty for using after-market wipers, oil filters, etc. Yes, they can void your warranty, but they'd have to show that the oil filter caused your window to not open. There needs to be cause and effect.
nobody has ever posted they were refused warranty because they unlocked the bootloader
since google hasn't been signing their factory images, you actually need to be unlocked even to flash those
Anyway, it is up to you. You need to do what is right for yourself. I got tired of waiting for Google so took things into my own hands.

So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?

danvee said:
So, essentially, by making factory images available for public download, they're acknowledging that it's necessary to unlock in order to use them, so, basically they can't find fault with it?
Click to expand...
Click to collapse
First off, I don't think they are trying to find fault with it to start, but if they did, yes, you could make the argument that the ease and availability of factory images made available publically was one of the reasons you bought this tablet over others and the fact that they require an unlocked bootloader, would make that standard procedure, so how could they possibly say that unlocking the bootloader is an automatic warranty void.
More importantly, simply ask them to show how unlocking the bootloader caused the damage/issue in question. They cannot, unless you really did do something that broke it as a direct result of something you put on the tablet after you unlocked it, but I think in that case, you would probably accept blame.