Develop Bugs

More Lumia 900 weird behaviors and oddities

I haven't seen any threads pointing out the issues I've been having with my Lumia 900. For context, my Lumia is a pre-order cyan model that has been updated via Zune to the latest firmware.
My observed "unique" issues:
Pressing the Windows button, especially inside of games act CRAZY. Pressing the Windows button does nothing - the phone won't go home to the tiles. This is consistent across most games. Sometimes it will simply go into "voice" mode, but then am unable to cancel the voice by hitting back. It just sits there, no matter which key I mash. This is not consistent...sometimes it acts this way, sometimes it acts normally.
Pressing the "back arrow" key...pretty much identical to the above, except instead of "voice" mode, I get the app chooser. When in the app chooser, hitting the Windows key does nothing. At times, the only way to exit some apps is to hit back arrow into app chooser, choose another app, then hit the Windows key to go home. Again, only in games.
My Lumia randomly picks up capacitive button input, even when my hand is nowhere near the buttons. This almost manifests itself as a "Search" key press. Again, this only seems to happen when playing games! What is strange is that I can reasonably consistently repeat this behavior by touching the metal bezel around the camera.
Why in games only? Reasoning seems to suggest that Nokia may have slipped some detect code into the OS that alters capacitive button behavior when gaming to address a major WP7 complaint regarding accidental key presses exiting games. It's well within Nokia's rights given they have a customization exemption from Microsoft. That said, I've heard of no such "feature" existing, nor have I heard of anyone else having the issue.
I'm likely going to go back to the AT&T store and request a new device, because on top of this, my phone has the annoying vibration "buzz", as well as the phone generally seeming less responsive and reliable than my old Focus.
Thoughts?

I just tried in a couple of games to verify, and I don't have any of the issues you've described. I'd say get it swapped out.

I have none of these issues either. I also recommend a swap out.

I'd also suggest returning it.
I don't think those behaviors are normal for this phone; mine doesn't behave that way.

I just returned my cyan phone. No problem from the AT&T store at all. One sales guy was unaware of the problem, but the guy next to him was up to speed. They had cyan un stock and was going to do a straight swap, but I was aware enough to ask about white...they still had 2! Cyan would have been a straight swap, but for a $35 restocking fee, I could have the white. On top of that, he did I could return my cyan bumper case, so id be $20 out of pocket for a phone that wasn't available in the $100 rebate timeframe, yet still keep the rebate. Done deal!
FWIW, fit and finish in the white phone is noticable better: no loose buttons, no vibro rattle and the gloss white looks great. I'll know more on the soft key issues after I reinstall more apps.
I'm a very satisfied customer.

Actually, this is a KNOWN issue -- specifically when playing audio through the bottom speaker. Here's a link to the Nokia thread discussing this problem.
Does your new phone not have that issue? Here's a test: play a song through the built-in speaker, wait 10 seconds...do the capacitive buttons not respond properly, or act as if you've long-pressed them? You can "fix" the issue by plugging in some headphones.
Very strange.

yipcanjo said:
Actually, this is a KNOWN issue -- specifically when playing audio through the bottom speaker. Here's a link to the Nokia thread discussing this problem.
Does your new phone not have that issue? Here's a test: play a song through the built-in speaker, wait 10 seconds...do the capacitive buttons not respond properly, or act as if you've long-pressed them? You can "fix" the issue by plugging in some headphones.
Very strange.
Click to expand...
Click to collapse
My new phone works perfectly, given the repro steps above. Playing music through the bottom speaker and waiting over 10 seconds, the capacitive buttons work just fine...no long press behavior, at all.

kenikh said:
My new phone works perfectly, given the repro steps above. Playing music through the bottom speaker and waiting over 10 seconds, the capacitive buttons work just fine...no long press behavior, at all.
Click to expand...
Click to collapse
Interesting. I did a side-by-side comparison with my co-worker -- same phone, same color (cyan), purchased at the same time. His phone is fine, mine is not. I can repro the issue at ANY TIME by simply playing a song through the speaker. I can fix the issue at any time by simply plugging in headphones. Wacky.
Looks like I need to swap my phone, which kinda sucks.

yipcanjo said:
Looks like I need to swap my phone, which kinda sucks.
Click to expand...
Click to collapse
I thought so, too, but after having the gloss white, I am happy I made the switch. I noticed that the matte finish cyan was starting to hold dirt, requiring cleaning to keep it looking good. I think that the gloss white will have no such issue.

kenikh said:
I thought so, too, but after having the gloss white, I am happy I made the switch. I noticed that the matte finish cyan was starting to hold dirt, requiring cleaning to keep it looking good. I think that the gloss white will have no such issue.
Click to expand...
Click to collapse
Well....after testing my co-worker's phone (that didn't have the capacitive button issues), I decided to head to the AT&T store and swap my phone. The sales rep (at AT&T) sympathized with me...as he also had the same issues. His was a "launch day" phone, and he noted that only the earliest phones seemed to have this issue, though not all of them.
Anyhow...new phone...no issues, thus far. Bummer that it required a handset swap, but what'cha gonna do! Glad to have a healthy Lumia 900 (in Cyan) once again

My lumia has a mind of its own at times. It'll launch speak to me randomly, even when my phone is laying on the counter. The captivate buttons are either super sensitive or non responsive.
My internet connection is very unreliable. It'll lose data connection out of no where. Dedicated camera button will not always work. Usually I have to wake the phone up first for it to respond.
Internet explorer is rubbish. Sometimes it will load the page with hella glitches.
This is the second lumia I've gone thru. I even did the software update.
As much as the higher ups want me to sell this phone I refuse to. Maybe I've just been unlucky twice but IMO they need to extend the $100 credit for another month.
I gave this phone an honest chance but as soon as the HTC one comes out I'll be ditching this phone.

chivamex10 said:
My lumia has a mind of its own at times. It'll launch speak to me randomly, even when my phone is laying on the counter. The captivate buttons are either super sensitive or non responsive.
My internet connection is very unreliable. It'll lose data connection out of no where. Dedicated camera button will not always work. Usually I have to wake the phone up first for it to respond.
Internet explorer is rubbish. Sometimes it will load the page with hella glitches.
This is the second lumia I've gone thru. I even did the software update.
As much as the higher ups want me to sell this phone I refuse to. Maybe I've just been unlucky twice but IMO they need to extend the $100 credit for another month.
I gave this phone an honest chance but as soon as the HTC one comes out I'll be ditching this phone.
Click to expand...
Click to collapse
Those are *NOT* normal issues. I would say swap it out once again...

Mine has been great. None of the regular issues I've read about. The only problems I've had is the disappearing keyboard, which is an OS problem not a hardware problem. Even though it's supposed to have been fixed, I still have this problem with my Radar, HD7, HD2 running Tango (refresh), & my 900. I digress, my bad, I've also just started to get a weird white flashing on my IE9 address bar. It flickers in & out, just started yesterday & continues to do so everytime I'm online.
Sent from my Lumia 900 using XDA Windows Phone 7 App

chivamex10 said:
My lumia has a mind of its own at times. It'll launch speak to me randomly, even when my phone is laying on the counter. The captivate buttons are either super sensitive or non responsive.
My internet connection is very unreliable. It'll lose data connection out of no where. Dedicated camera button will not always work. Usually I have to wake the phone up first for it to respond.
Internet explorer is rubbish. Sometimes it will load the page with hella glitches.
This is the second lumia I've gone thru. I even did the software update.
As much as the higher ups want me to sell this phone I refuse to. Maybe I've just been unlucky twice but IMO they need to extend the $100 credit for another month.
I gave this phone an honest chance but as soon as the HTC one comes out I'll be ditching this phone.
Click to expand...
Click to collapse
All of this is the same for me, except this is my first WP7 phone.
Just had to try it out, but have decided it's not for me. HTC One X when it comes out, then trading for One S or Xperia S..
Anyway, I want to add that I used the headphone jack for the first time this past weekend, and I noticed that there is a TON of background noise when playing sounds, but goes away a few seconds after audio stops... so it is very obviously coming from the phone itself.
NOT impressed.

mmceorange said:
All of this is the same for me, except this is my first WP7 phone.
Just had to try it out, but have decided it's not for me. HTC One X when it comes out, then trading for One S or Xperia S..
Anyway, I want to add that I used the headphone jack for the first time this past weekend, and I noticed that there is a TON of background noise when playing sounds, but goes away a few seconds after audio stops... so it is very obviously coming from the phone itself.
NOT impressed.
Click to expand...
Click to collapse
Hmmm....well, at least you get to replace it. Good luck with your One. Noticed it too has a nasty bug it shipped with. But, thats OK, its Android, and is not held to the same standard as anything Windows. Wait a minute....didn't the iPhone, the latest one, ship with a Siri bug or something...nahhh...couldn't be, I have to be remembering wrong. We all know that HTC and Samsung absolutely deliver the most impressive, long Lasting, bug free devices in the universe, with a solid reputation for innovation and length of use.
But, really, good luck with whatever choice you make. I'm sure you'll be very impressed.

alodar1 said:
Hmmm....well, at least you get to replace it. Good luck with your One. Noticed it too has a nasty bug it shipped with. But, thats OK, its Android, and is not held to the same standard as anything Windows. Wait a minute....didn't the iPhone, the latest one, ship with a Siri bug or something...nahhh...couldn't be, I have to be remembering wrong. We all know that HTC and Samsung absolutely deliver the most impressive, long Lasting, bug free devices in the universe, with a solid reputation for innovation and length of use.
But, really, good luck with whatever choice you make. I'm sure you'll be very impressed.
Click to expand...
Click to collapse
haaaaahhhhhh I know what you're getting at, but at least android has a huge development community to take care of just about any issue that pops up
If people were hacking the crap out of the 900 (which I'm sure will come in time) then I might stick with it just to see what is possible. But for now, it just isn't for me.

mmceorange said:
haaaaahhhhhh I know what you're getting at, but at least android has a huge development community to take care of just about any issue that pops up
If people were hacking the crap out of the 900 (which I'm sure will come in time) then I might stick with it just to see what is possible. But for now, it just isn't for me.
Click to expand...
Click to collapse
And that needs to be ok. I left the Android community because I believe that many of the OEMs rely on the dev community to get somethings right. And I'm really not ok with that for everything.
but, to each his own.....good luck on yours...

chivamex10 said:
My lumia has a mind of its own at times. It'll launch speak to me randomly, even when my phone is laying on the counter. The captivate buttons are either super sensitive or non responsive.
My internet connection is very unreliable. It'll lose data connection out of no where. Dedicated camera button will not always work. Usually I have to wake the phone up first for it to respond.
Internet explorer is rubbish. Sometimes it will load the page with hella glitches.
This is the second lumia I've gone thru. I even did the software update.
As much as the higher ups want me to sell this phone I refuse to. Maybe I've just been unlucky twice but IMO they need to extend the $100 credit for another month.
I gave this phone an honest chance but as soon as the HTC one comes out I'll be ditching this phone.
Click to expand...
Click to collapse
This is typical of the early phones that had glitches. My cyan had all of these issues...my white 900 has none.
It's a bummer that the 900 had so many issues out of the box...pretty inexcusable, actually. But having had the experience of using a first gen device, I knew that it wasn't the OS, it was the phone.
When your 900 is running significantly worse than an old Focus, it's the phone.

kenikh said:
This is typical of the early phones that had glitches. My cyan had all of these issues...my white 900 has none.
It's a bummer that the 900 had so many issues out of the box...pretty inexcusable, actually. But having had the experience of using a first gen device, I knew that it wasn't the OS, it was the phone.
When your 900 is running significantly worse than an old Focus, it's the phone.
Click to expand...
Click to collapse
You know though....every phone, every brand has these...'glitches'. Its only a matter of 'if' they happen to you. Every phone mentioned on any forum, as being superior, has its own list of complaints that a significant number of people subscribe to.
I also think that if anything, Microsoft is held to a different standard than others. Just as Apple is begining to take heat for the slowing down of innovation. Basically, more people, more interest, more issues.
Even Android is running into problems based on quality of hardware, and the lack of testing on all hard ware in general, instead relying more on the dev community to help them out.
None of it is excusable, but I 'notice' that only Microsoft seems to be held accountable for such things.
Anyone here ever get an Android phone that was basically a piece of crap? I'm sure we can all supply examples....for me, the LG G2x, the Motoroal Bionic and the Motorola Droid 2x, as well as the HTC Sensation. The nicesst words I can use is....Rubish. But, like everything else, it only matters if it happens to you. There are fans of those phones all over the place. Yet, for me, POS's.
Not everyone likes every phone. I like Windows Phone. My son does not. He said to me....Dad, its nice, its ok, but it doesn't wow me. And I want to be wowed. That needs to be ok. He didn't say Microsoft was crap, and, Windows OS sucked. It just wasn't for him. Even though his last phone, the Sensation, had just stopped working, he ran out and got an HTC One-s . Go figure.
People that have problems with any phone, should be disinclined to venture in that area again. But, I repeat, it appears that people hold Microsoft to a higher level of accountablity in the Mobile area, than say....Google.
Just my Opinion.

Very true alodar1! I love WP OS and all my phones running it. These things will be fixed & for me, at least, they are not deal breakers.
Sent from my Kick Ass Lil Radar using XDA Windows Phone 7 App

[Q] HTC One X questions – temperatures, CPU frequencies, ripples and perhaps more.

Hello everyone. First of all, I want to write a small disclaimer saying that I have already searched multiple forums in order to find specific answers to my questions, but haven't managed to find the answers I needed. Furthermore, I am a first-time user on XDA so I also wanted to say Helloooo!!!
Here's the story. Two-days ago I have purchased an HTC One X from Orange, so it's the Tegra 3 international version. I need to point out that this is my very first smartphone. I haven't owned one until now because I felt like all I needed was a small box to speak in. However, times change and I am finally living in the present .
Needless to say, I love this device. However, I have a few questions regarding the handset, and handsets in general.
- First, the temperature. I have searched forums and I have learned that some smartphones get hotter than other, and that it's a normal thing. However, since I am not used with a hot device in my hands (literally and figuratively) it got a bit scared and I have searched the web for answers. The thing is, I wasn't able to find what is the exact safe-zone for this specific device. Keep in mind that this is a Tegra 3 version, and from my understanding Tegras it gets hotter than Snapdragons. Also, I have noticed that on many threads and forums, people mix-up battery and CPU temperatures…I simply want a clear answer. I want to know the safe-zone for both the CPU and battery, separately.
As a side note, I don't really care if the device feels warm in my hands when running demanding apps and games (normally the device is quite cool). However I am afraid I will damage the device if I play heavy 3D games….I don't want that to happen.
I was also wondering whether or not it's safe to use the phone with a protective case on, like otterbox defender. Wouldn't that rubber make the temperatures even higher?
====
- Second question: I ran StabilityTest because I got paranoid and I wanted to see if my device was stable. I ran the first CPU test (unrooted) for about 15 minutes and got no errors. However, I have noticed that on screen it said the cores run at 1,000 MHz…Wasn't this supposed to run at 1,5 Ghz?
=====
- Third. I have also learned yesterday evening that some HTC One X units have a screen ripple issue…I tested mine and indeed I have the same problem.
However, it slightly ripples mostly on the left side. The thing is, it doesn't bother me because it only ripples if I press the glass on its very edge, and I can't see a reason why I would do that when using the device normally. I admit, I haven't pressed too hard because I really like the device and I don't want to damage it.
So what I was wondering is this. Is it normal for every One X to get this ripple effect? I have searched an older thread somewhere, and opinions were mixed. People have said that as long as it doesn't affect the rest of the screen, it's normal. Others (probably those owning another device) claimed it's not normal and the owners should replace the device.
However, the thread was a few months old and I wanted to get some newer answers. Has HTC answered this issue? Is it or is it not normal? I mean, I know no ripples > some ripples, but still. Is it dangerous? Will the problem get worse with the passage of time?
The thing is, someone claimed they have returned the device only to get an even worse one…I am not bothered by how my display ripples. It's nothing annoying, so as long as everything remains the way it is, I see no reason to return the device.
Will it get worse in time…?
Also, is the HTC One X the very first device to experience this issue? If not, how did the situation developed for other handsets experiencing ripple issues?
====
- Lastly, some people claimed that a certain update addressed a certain overheating issue. I am running software version 1.29.401.11 and it says I'm up to date (again, international version). Was this bug-fixing update released on the international version already, or am I running a version that overheats my device? Or, was this problem present on the international version to begin with?
Thank you so much for having the patience of reading my wall of text. I apologize if any information was already out there, I simply couldn't find the answers I needed. Well, I found some.
Regards,
Neevar.

i really want to thank you for asking these questions. many of my questions will be answered too. i am waiting for the latest batch coz i believe i will get a perfect HOX. my basic issue is battery life is short. dint you face any problem like that? or wifi problem?
anyways. i am using N900. it is the most hackable device. i do many hacking and testing with it. can all these be possible with HOX. i am sorry but HOX will be my first android device so i know very little about android.
1) is it possible to hack WEP and WPA (with dictionary) wifi network?
2) is there MDK3 for android?
3) dsniff, dnspoof, etc
4) MITM attack.
if i buy HOX i will really miss my N900 for all these. is it possible to use them in android?

muid02 said:
i really want to thank you for asking these questions. many of my questions will be answered too. i am waiting for the latest batch coz i believe i will get a perfect HOX. my basic issue is battery life is short. dint you face any problem like that? or wifi problem?
anyways. i am using N900. it is the most hackable device. i do many hacking and testing with it. can all these be possible with HOX. i am sorry but HOX will be my first android device so i know very little about android.
1) is it possible to hack WEP and WPA (with dictionary) wifi network?
2) is there MDK3 for android?
3) dsniff, dnspoof, etc
4) MITM attack.
if i buy HOX i will really miss my N900 for all these. is it possible to use them in android?
Click to expand...
Click to collapse
First of all, thanks for arranging all these questions in nice manner.
I'll surely keep track of this thread, as I'm also having similar doubts, which are not yet clear even after reading many threads and posting threads....
Looking forward to buy a new HOX here, preferebly from latest batches....
And a kind request to members those who are replying;
kindly give an unbiased opinon, and pls dont mix up any other issues...
muid02:- buddy, Please read what the thread is for....dont mix up unnecessay issues here, like your N900, adroid and other stupid stuffs...If you want clarification in those issues, start a new thread....

Neevar said:
Hello everyone. First of all, I want to write a small disclaimer saying that I have already searched multiple forums in order to find specific answers to my questions, but haven't managed to find the answers I needed. Furthermore, I am a first-time user on XDA so I also wanted to say Helloooo!!!
Here's the story. Two-days ago I have purchased an HTC One X from Orange, so it's the Tegra 3 international version. I need to point out that this is my very first smartphone. I haven't owned one until now because I felt like all I needed was a small box to speak in. However, times change and I am finally living in the present .
Needless to say, I love this device. However, I have a few questions regarding the handset, and handsets in general.
- First, the temperature. I have searched forums and I have learned that some smartphones get hotter than other, and that it's a normal thing. However, since I am not used with a hot device in my hands (literally and figuratively) it got a bit scared and I have searched the web for answers. The thing is, I wasn't able to find what is the exact safe-zone for this specific device. Keep in mind that this is a Tegra 3 version, and from my understanding Tegras it gets hotter than Snapdragons. Also, I have noticed that on many threads and forums, people mix-up battery and CPU temperatures…I simply want a clear answer. I want to know the safe-zone for both the CPU and battery, separately.
As a side note, I don't really care if the device feels warm in my hands when running demanding apps and games (normally the device is quite cool). However I am afraid I will damage the device if I play heavy 3D games….I don't want that to happen.
I was also wondering whether or not it's safe to use the phone with a protective case on, like otterbox defender. Wouldn't that rubber make the temperatures even higher?
====
- Second question: I ran StabilityTest because I got paranoid and I wanted to see if my device was stable. I ran the first CPU test (unrooted) for about 15 minutes and got no errors. However, I have noticed that on screen it said the cores run at 1,000 MHz…Wasn't this supposed to run at 1,5 Ghz?
=====
- Third. I have also learned yesterday evening that some HTC One X units have a screen ripple issue…I tested mine and indeed I have the same problem.
However, it slightly ripples mostly on the left side. The thing is, it doesn't bother me because it only ripples if I press the glass on its very edge, and I can't see a reason why I would do that when using the device normally. I admit, I haven't pressed too hard because I really like the device and I don't want to damage it.
So what I was wondering is this. Is it normal for every One X to get this ripple effect? I have searched an older thread somewhere, and opinions were mixed. People have said that as long as it doesn't affect the rest of the screen, it's normal. Others (probably those owning another device) claimed it's not normal and the owners should replace the device.
However, the thread was a few months old and I wanted to get some newer answers. Has HTC answered this issue? Is it or is it not normal? I mean, I know no ripples > some ripples, but still. Is it dangerous? Will the problem get worse with the passage of time?
The thing is, someone claimed they have returned the device only to get an even worse one…I am not bothered by how my display ripples. It's nothing annoying, so as long as everything remains the way it is, I see no reason to return the device.
Will it get worse in time…?
Also, is the HTC One X the very first device to experience this issue? If not, how did the situation developed for other handsets experiencing ripple issues?
====
- Lastly, some people claimed that a certain update addressed a certain overheating issue. I am running software version 1.29.401.11 and it says I'm up to date (again, international version). Was this bug-fixing update released on the international version already, or am I running a version that overheats my device? Or, was this problem present on the international version to begin with?
Thank you so much for having the patience of reading my wall of text. I apologize if any information was already out there, I simply couldn't find the answers I needed. Well, I found some.
Regards,
Neevar.
Click to expand...
Click to collapse
Temperature - it does get hot. A lot of people say don't play games whilst charging the device, as it will get hotter.
I personally don't believe in this. The phone should have safeguards (similar to a PC) to specifically stop it overheating - infact it does, when it gets too hot, it stops charging. If it overheats and dies (which is a big if, i've certainly not heard of anyones hox dying from overheating), then this would be covered under warranty anyway. Which I believe is 2 years. It would be reallllly stupid for HTC not to test for heat issues before release. I'm sure they had a fleet of devices all running stress tests just to make sure they didn't melt.
I don't know the 'safe zones' all i know is that HTC confirmed that reaching a temperature of 55c is normal and nothing to worry about. I have since read of people reaching higher temps (72c) but I don't think even that had any adverse effects
The CPU underclocks itself for power saving. This is a separate feature from the companion core. This can be modified, you have to create a shortcut (easiest way is to use minimalistictext, and create a widget, that on tap will open the power saving settings shortcut.) It does run at 1500 however. You haven't been conned at least
Most hox's i've had (6 in total) had the screen ripple, the general rule on whether it is normal or not - if you have to push really hard to get it to ripple, then it's fine. It's only when it ripples on a very gentle touch that you might want to get it replaced/repaired. (a gentle touch does fall into normal use, and this ripple imo shouldn't happen under normal use.)
Do be sure that if you send back the device, that it IS a hardware problem, and that it is a bad enough issue to warrant possibly getting another, but worse problem. Note that I've been through 6 hoxs, each one of them with different (and some of the same) problems. The 6th one, is also defective, and is due to be replaced soon.
I don't believe the HOX is the first device to suffer from screen ripple. My DHD did it. The difference was i had to push unbelieveably hard to make it happen the slightest bit. So clearly there is some sort of design flaw here, particularly on those hoxs that just need a slight touch for it to happen.
Regarding the update that addresses overheating, somebody correct me if I'm wrong, but i think thats the 2.05 update, which hasn't been officially released yet, only leaked. You can install a custom rom with the 2.05 base, but otherwise just be patient and we shall soon have the update OTA.
Hope this helps

lawrence750 said:
Hope this helps
Click to expand...
Click to collapse
Thank you so much for the detailed reply Lawrence. Your feedback really cleared some things in my mind.
Regarding the temperature, I have never seen the LEDs go red or anything like that. It just feels warm, that's all. I just checked the temperatures and right now while idling it shows 39 degrees, but considering the fact that my room temperature is around 33 degrees, I suppose that's a good value (yeah, AC broke, I run a big fan in my face lol). While playing GTA 3 for about 30 minutes last night the temps reached 50 degrees. I have seen older posts claiming that 50 degrees is really bad, but those posts were after or even before the handset launched in certain regions, and most people claiming this were comparing the One X with their own handset. Now that you've said HTC confirmed that 55 is a normal temperature, I think mine performs quite well to be honest...
Note* I haven't played while charging.
About the screen ripple. It doesn't happen on normal use. but if I focus in holding my fingernail on the very edge of the screen and drag it from top to bottom, i do see faint ripples. as I've said, it doesn't bother me as long as it won't get worse... do you have any idea if it can get worse somehow with the passage of time?
I am rather afraid to replace it since yes, I might end up with an even worse unit... so, for me at least it all depends on whether or not the ripples can get worse or if it can damage my display in time. I really don't know what to do here...I certainly don't want to replace my phone for more than one time...
Since you already replaced your HTC One X 5 times now, can you tell me how the process works? Will they replace my phone at the Orange store or do they need to check on it for a frikin week before deciding to give me another?...
Regarding the update, if it's not out then I'll just wait. Considering the fact that according to HTC my temps are in check, and considering the fact that I never got a warning and / or reboot, I should be safe, I hope.

Neevar said:
Thank you so much for the detailed reply Lawrence. Your feedback really cleared some things in my mind.
Regarding the temperature, I have never seen the LEDs go red or anything like that. It just feels warm, that's all. I just checked the temperatures and right now while idling it shows 39 degrees, but considering the fact that my room temperature is around 33 degrees, I suppose that's a good value (yeah, AC broke, I run a big fan in my face lol). While playing GTA 3 for about 30 minutes last night the temps reached 50 degrees. I have seen older posts claiming that 50 degrees is really bad, but those posts were after or even before the handset launched in certain regions, and most people claiming this were comparing the One X with their own handset. Now that you've said HTC confirmed that 55 is a normal temperature, I think mine performs quite well to be honest...
Note* I haven't played while charging.
About the screen ripple. It doesn't happen on normal use. but if I focus in holding my fingernail on the very edge of the screen and drag it from top to bottom, i do see faint ripples. as I've said, it doesn't bother me as long as it won't get worse... do you have any idea if it can get worse somehow with the passage of time?
I am rather afraid to replace it since yes, I might end up with an even worse unit... so, for me at least it all depends on whether or not the ripples can get worse or if it can damage my display in time. I really don't know what to do here...I certainly don't want to replace my phone for more than one time...
Since you already replaced your HTC One X 5 times now, can you tell me how the process works? Will they replace my phone at the Orange store or do they need to check on it for a frikin week before deciding to give me another?...
Regarding the update, if it's not out then I'll just wait. Considering the fact that according to HTC my temps are in check, and considering the fact that I never got a warning and / or reboot, I should be safe, I hope.
Click to expand...
Click to collapse
I don't think the ripple gets worse over time, I can't say for sure really because I haven't had one long enough to see, however I can say that it does appear to be the way they are assembled that causes the issue, and its that that defines how bad the ripple is, rather than it getting worse over time.
My most recent hox, didnt have very bad ripple, and now after 'repair' it does, and also has a dead pixel in a different place. I suspect they actually replaced the screen, and it so happens that this screen has bad ripple. The other one didn't.
If I could find out for definite what they did it would kinda confirm whether the ripple gets worse over time or not, but they didn't log anything about the repair (tracking site never updated) and HTC can't tell me anything other about it than 'we're still waiting for it in repair center'
The replacement process (this applies to UK):
Sales of goods act states that if there is a fault with the device, in the first 6 months after purchase, it is the retailers responsibility to repair, replace, or refund the purchase, unless the retailer can prove that you caused the fault yourself.
If the repair option is chosen, then this mustn't significantly inconvenience the buyer. IE if they send it back unrepaired, they don't really have a choice from then, other than to replace it or refund you.
However there is also a cooling off period.
http://whatconsumer.co.uk/cooling-off-and-cancellations/
Depending on whether you bought the phone from an Orange shop (from actually within the shop) or bought it via internet/phone/mail, it differs slightly.
I'm pretty sure you don't actually
If you bought it online, or by phone, but not in the shop, then you will have a 7 day cooling off period, from the conclusion of the contract
If the service was activated before the 7 day cooling off period, then you have given up the right to a cooling off period, but this must have been clearly communicated and with your agreement.
Orange must also send you written confirmation of the contract and any other additional information applicable. If this doesn't arrive within the 7 days, but before 3 months after purchase, then the cooling off period doesn't start until these confirmations have arrived.
Assuming you're out of this 7 day period, and also assuming that you haven't accepted the goods yet(see below) then you can reject the goods if they aren't as described, fit for purpose, or aren't of satisfactory quality.
Customers are considered to have accepted goods when they:
tell you they have accepted them
alter them
keep them for a reasonable length of time - this varies according to the nature of the goods
Click to expand...
Click to collapse
I'm just looking for the cooling off period when bought in a shop, but my head hurts lol, if you do a bit of searching on google should come up fairly easily
Even if there isn't a cooling off period, which you don't need a reason to cancel, then you can reject the goods as mentioned above, on the basis they aren't of satisfactory quality, and in this instance orange will possibly replace, but they aren't obliged to at this point. Appeal to their goodwill, but they may well insist on sending it for repair.

I have read before than if CPU ran at 80 + degree every time then it can last for 2 years , so no worries about heat guys. The money which we have paid is worth.
Sent from my HTC One X using Tapatalk 2

forumhookersdotcom said:
I have read before than if CPU ran at 80 + degree every time then it can last for 2 years , so no worries about heat guys. The money which we have paid is worth.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
But can the adjacent components withstand that heat emitting from the CPU?
Sent from my HTC One X using xda premium

stuart0001 said:
But can the adjacent components withstand that heat emitting from the CPU?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
they use the foil layer to spread the heat over the device, so yes i expect that any nearby components would be fine.

I'm starting to get pissed off.
I got in touch with an HTC technical agent via their online form, and I have received an email where the agent told me that the battery temperature should not go over 50 degrees Celsius. If that happens, then he advised me to return the phone immediately.
He also said that ripples are not normal and once again, I should return the phone.
So I ran Glowball for about 20 minutes and my battery has gone up to 61 degrees Celsius....
I decided to take my phone back to the store where I have bought it. Those dudes raised their shoulders and told me to go to the company that deals with warranties in order to get a paper, then return to them.
I asked them if I can cancel my contract and get a refund, but no, apparently it too much time has passed since I made the purchase.
I have called the company and a clueless lady answered then cut me off mid-sentence when I started talking about technical stuff. She was clearly clueless but asked me if I have been at the store with my phone...derp...
Then she told me that I should go there on monday and see what's what....
What an incompetent way of doing things. I am 99% certain that I won't go anywhere with these monkeys, either that or I'll waste at least a whole month trying to get a hold of a HOX that works as intended.
This being my very first smartphone, I am very disappointed and I'm fearful I have just got myself a two year contract with a carrier, for a phone that doesn't work and with which I'll probably stuck with because of these idiots.
And by the way, why hasn't HTC recalled or announced every carrier and company that deals with warranties that every phone that has ripple and overheat issues need to be recalled and replaced as soon as someone like me shows up in their store with a faulty device in their hands???

htc one x cpu and battery
Hi,
I have the following problem:
I have a HTC One X and have the BinDroid 5.0.0 Rome installiert.Der battery goes down quickly and the system hangs, no matter what I want ... the problem was with Coredroid V4.0 and BinDroid 4.0.0 already ... Not even in Whatsapp I can write without it hangs and the battery will not work correctly if it depends on the charger as soon as I use some program ... no matter what, whether whatsapp or other app's ... in the car when it depends on the charger, it produces the error message "Unable to load, the unit will be more current than the charger can charge" <- something like that ^ ^
now my question: it may be that generally run all CPUs instead of one CPU and the other can be switched on when it is necessary, as it should be normal, according to HTC?
What can or should I do that my HTc one x fluent running again?
Am very satisfied with BinDroid and in my opinion is the best ROM for the HTC One X

Random shut downs?

Hi guys. Haven't been here in a while. My daughter is now saying her cap. glide is randomly shutting itself down- not related to low battery. It happened 3 times in one week. When she powered it up the battery was fine. The phone is about 9 months old. I think it has a 12 month warranty. At least on the samsung site it says 12 months. We got it from ATT with contract renewal.
I read that the regular Captivate had this problem. Did it flow over into the glide? Haven't found anything about it. I assume ATT will replace with a refurb if anything.

sashusmom said:
Hi guys. Haven't been here in a while. My daughter is now saying her cap. glide is randomly shutting itself down- not related to low battery. It happened 3 times in one week. When she powered it up the battery was fine. The phone is about 9 months old. I think it has a 12 month warranty. At least on the samsung site it says 12 months. We got it from ATT with contract renewal.
I read that the regular Captivate had this problem. Did it flow over into the glide? Haven't found anything about it. I assume ATT will replace with a refurb if anything.
Click to expand...
Click to collapse
I use mine pretty heavy and havent noticed any problem i assume that you are running the phone completely stock and if so i would suggest that you download samsung kies from samsungs site and run it then plug the phone in and it will ask you if you want to update the phone it may run better on the newest firmware that there is other wise i would download avgs free antivirus app and run it to see if there are any apps that might be to blame i would post links but to avoid spam i am not allowed

og anarchy said:
I use mine pretty heavy and havent noticed any problem i assume that you are running the phone completely stock and if so i would suggest that you download samsung kies from samsungs site and run it then plug the phone in and it will ask you if you want to update the phone it may run better on the newest firmware that there is other wise i would download avgs free antivirus app and run it to see if there are any apps that might be to blame i would post links but to avoid spam i am not allowed
Click to expand...
Click to collapse
Thanks for your response. Yes, it is stock rom, but I have it rooted with CWM recovery on it. I don't think kies can update it due to CWM. And it's in another state. LOL. But good to know you don't have the issue. As for running antivirus, my daughter does not even know what that is- she barely runs it on her computer. If I ever get my hands on it I will try your suggestion for AV.

Could be a battery issue... mine did the same, and when I took out the battery it was slightly swollen.

Thanks for that. I'll have her check it out.:fingers-crossed:

Interested in your solution
My wife's Captivate Glide just started having random shutdowns last week. I came over looking for a "return to stock" thread hoping that putting a new OS might help when I saw this thread. I've been reading xda on the GalaxyII boards since getting mine last year so have some familarity with xda. Wife prefers to not update OS so I want to avoid ICS. She had AVG installed and I added Lookout to scan with it also and can't seem to find an issue with those. The problem for her mainly manifest itself when she has the internet turned on. The phone will basically act like the battery is critical and do a shutdown even if it is over 50 percent. power up with the cord in and it still shows good charge. If I find something that works I'll post it here also.

I have random shutdowns/boot cycles too. I've narrowed it to a hardware issue. I was running rooted stock rom, but also ran liquidsmooth and now on aokp rom, and its still happens.
I posted a topic a couple weeks ago, asked if anyone has any experience replacing the power button..its not that it sticks, but if pressed the wrong way in the wrong spot, the phone goes into endless boot mode, with the samsung logo up for about three sec, then black, then samsung logo, then black.
The timing is rarely the same. There's no debris or gunk. Its not battery. Its not overclock issue. Its something to do with the phyical power button.
Can I diasble power button using key remapping?
Sent from my SGH-I927 using xda premium

Having the same problems with my Glide, and I really do think it's a hardware issue since my battery looks fine. After reading many threads here and elsewhere, I'm resigned to the fact that it can't be fixed, but more suggestions are welcome.

My daughter has had this phone for almost a year and it just started happening to hers. She is very hard on her phone. 5000 texts/month with alot of drops. She just might have abused it to near death. lol.

Random Boot
Hello guys;
I think I'm having same or very similar issue.
My phone is randomly shutting down; some times is in cyclic restarts.
Did you guys came up with a solution to this problem?
Thanks

sashusmom said:
My daughter has had this phone for almost a year and it just started happening to hers. She is very hard on her phone. 5000 texts/month with alot of drops. She just might have abused it to near death. lol.
Click to expand...
Click to collapse
5000 texts per month?
Does your daughter know how to speak or is she only familiar with written language?

If you're on a stock rom, it's almost certainly a bad battery.
Battery voltage will drop when it's hot or if it's damaged. When you turn it back on, the phone says you still have plenty of power left.
What the phone is really doing is making a guess about how much battery life it has left.
It knows the voltage. Now, if you know the voltage a battery is producing with no load, you can get sort of an idea of how much more life you can get out of it. The phone keeps track of this (roughly) and tries to guess. It's also not going to let the battery drop too far down below 3.6 volts, it will shut it off for safety, because if you truly completely discharge a lithium battery, you can't charge it. (there are tricks to get them going again, but it's bad for them.)
And a damaged battery can have plenty of volts, but once you put it under load it will drop sharply. The phone will power down to protect the battery, or it just won't be able to stay on any longer.
Anyway, pull your battery. Make sure it isn't bulging. Pick up a spare off of ebay for $10 and see if it is better.
Or if it's under warranty, just take it in.

davidpartay said:
5000 texts per month?
Does your daughter know how to speak or is she only familiar with written language?
Click to expand...
Click to collapse
Lol.... Sometimes it's only 3 thousand. But you are right. The art of communication is being lost on this generation of kids who rely on computers, tablets, and smartphones. Instead of calling, they text about everything.
My daughter is graduating:victory: with a double major- Theatre and speech (performance) so we know she can talk and sing and psychology with ambitions to get a masters in dance therapy to work with autistic kids.... If broadway does not work out Any directors or producers out there need new talent?? :fingers-crossed:

epsalmond said:
If you're on a stock rom, it's almost certainly a bad battery.
Battery voltage will drop when it's hot or if it's damaged. When you turn it back on, the phone says you still have plenty of power left.
What the phone is really doing is making a guess about how much battery life it has left.
It knows the voltage. Now, if you know the voltage a battery is producing with no load, you can get sort of an idea of how much more life you can get out of it. The phone keeps track of this (roughly) and tries to guess. It's also not going to let the battery drop too far down below 3.6 volts, it will shut it off for safety, because if you truly completely discharge a lithium battery, you can't charge it. (there are tricks to get them going again, but it's bad for them.)
And a damaged battery can have plenty of volts, but once you put it under load it will drop sharply. The phone will power down to protect the battery, or it just won't be able to stay on any longer.
Anyway, pull your battery. Make sure it isn't bulging. Pick up a spare off of ebay for $10 and see if it is better.
Or if it's under warranty, just take it in.
Click to expand...
Click to collapse
Very informative. Thank you. She did pull the battery and it was fine. It is about a year old. I got her 2 replacements and she just doesn't use them. I will suggest that she switches to a new one- although they are almost a year old too, but unused- I charged them up once before i gave them to her.

phone saga continues!!!
:silly: Well, my daughter being sooooo poor that she couldn't buy herself a BOX of tissues(cough-cough), she was pulling toilet paper from the dorm bathroom and plop! OOps!! Her phone fell into the drink! (toilet bowl!!)
She knew enough to pull the battery and used a blowdryer to start the dry out process, and put it into a bag of rice. Didn't leave it in long enough and tried to power on- did a little dance, and it died. I thought she fried it, but she put it in rice again- battery pulled and slid in the open position.
2 days later she called us on it- (today) and it seems to be working!!!:victory:
So, Rice saved the day again! :silly::good::highfive::fingers-crossed:
We'll see how long it lasts. I bought a cheap go phone last nite on att for $21 as a temporary replacement. Maybe it won't be needed.

Help!!
Hard to believe my glide is begining to give problems. After flashing a stock kernel on spike55 jb 4.2 rom,i started getting random app crashings. So i sought to revert by flashing back the original jb ROM,but it got worse. Now i was uable to get network and my baseband version displayed unknown also i had random reboots.
At this junction, i realised i had to revert to stock. So i got a stock ICS rom from sammobile, flashed it via odin and whala! Problem seemed solved. So i flashed CWMR and reflashed jb 4.2.
Afterward, all seemed well not until the random reboots came back. So here i was thinking about my phone being tired of all the flashing and wanting to be on stock. I went back to stock, but the random reboots still lingers.
Though i have a feeling the problem is with my power rocker cos only a little tap pops up the power menu.
At this junction, i dunno what to do. I'll be very grateful if i can get any real assistance from anyone. Thanks a bunch in anticipation.

So I thought I'd post again. Daughter home for good. Started complaining about her battery again. I found her 2 spare batteries that were never used. Had her make the switch.
Then I looked at the removed battery. It was slightly swollen. You had to look straight down to tell. Looking at it flat, it seemed to be fine. But put it on end and it had a slight bulge. So it was a battery going bad. We caught it before the phone was damaged.
Sent from my Nexus 7 using Tapatalk 4

Hello!!! Back again My daughter ran on macadam and her unprotected cap. glide plopped out of her sweatshirt pocket and hit hard. A small hairline crack in the screen, but it pretty much killed the digital panel. She had it for 18 months and for her, that's a record. But she loved the phone.
We just got a new one unlocked one off amazon for $138. No contract renewal for her.
If anyone is still reading this thread, her OS is 2.3.5 or 6. Is it worth updating to ics? We don't have kies installed so it will be a job to get everything installed, get drivers working, etc. She will be happy with GB. Last time I made the change to swap external and internal sd cards and she had no problems.
So is ICS worth the effort? Battery life? Can the sd swap trick work? Any advice will be appreciated. Presently it is new and stock.

sashusmom said:
So is ICS worth the effort?
Click to expand...
Click to collapse
..it might even have come with ICS, the UI differences to GB are very slim.. Can't say more because stock roms are far inferior to the beast called P.A.C.man ROM :laugh: :good:
Really depends if she is tech savy and will explore the depths of customizability and usage... If so, http://pacman.basketbuild.com/index.php?dir=main/i927/nightly/ is the next place to go
Nightly builds 'been broken for 10 days now but should be fixed soon by awesome @kick buttowski :good:
And on a rooted phone, Titanium Backup can import/export SMSs and contacts supposedly even over to a different rom. (Still struggling a bit getting all my contacts ported from the sony xperia system, but..)
Oh by the way, one of them plastic hard cases is about 5$ on the bay
...It's not water proof though

eMPee584 said:
..it might even have come with ICS, the UI differences to GB are very slim.. Can't say more because stock roms are far inferior to the beast called P.A.C.man ROM :laugh: :good:
Really depends if she is tech savy and will explore the depths of customizability and usage... If so, http://pacman.basketbuild.com/index.php?dir=main/i927/nightly/ is the next place to go
Nightly builds 'been broken for 10 days now but should be fixed soon by awesome @kick buttowski :good:
And on a rooted phone, Titanium Backup can import/export SMSs and contacts supposedly even over to a different rom. (Still struggling a bit getting all my contacts ported from the sony xperia system, but..)
Oh by the way, one of them plastic hard cases is about 5$ on the bay
...It's not water proof though
Click to expand...
Click to collapse
Nice to see people are still using this phone. As far as the case- I must have bought 5 of them for her. She didn't want them on her phone. Now that she paid for her own replacement, she may rethink that one! lol. She is not tech saavy at all, so custom builds are not her thing. I didn't even do the mods on this phone that I did on her original. Thanks for your input. OH, it's still GB.

My experience with ARCHOS and the 101xs (BAD EXPERIENCE)

On the 3rd of June 2012 I bought an Archos 80 G9 tablet, I was happy with it, it worked fine, until December 2012. Suddenly I could not charge it any more, if I connected it to try to charge it switched off. So I contacted ARCHOS repair service and I sent my tablet to ARCHOS. After almost 2 months waiting for a replacement, they upgraded my old tablet with a brand new ARCHOS 101 xs. I was a little fed up because I was waiting almost 2 months for a replacement but, well, I thought, let's give ARCHOS an opportunity.
Guess what. The brand new ARCHOS 101 xs was faulty as well. Without touching the screen the borders are active, it goes back or opens the menu on the clock side without touching it, if you are watching a video the menu appears without touching it. I tried whatever I could: I tried not to touch the keyboard connection (thinking I could short-circuit the tablet), I rotated it because maybe it was a problem with some corners, I upgraded to 4.1 and to 4.1.2 and also I downgraded to 4.0.26, I recalibrated the screen from Android menu, I recalibrated the screen from Archos recovery menu, I reset android and I reinstalled android.
I wrote ARCHOS replacement and they asked me to send it again. GREAT
I received the replacement (second replacement, third faulty Archos tablet), apparently a brand new Archos 101 XS(PC123902679), I say apparently because it fails again. What a coincidence, don't you think?
I recalibrate the screen a dozen of time, and blah blah blah...
Now I've recorded some videos showing the behaviour of the screen without touching it but I cannot added them because I'm a new user on XDA.
The same day I received the tablet I called archos (didn't work) and I wrote to [email protected] and to [email protected], after 12 days they don't response to me. What do you think? What should I do? I'm waiting for a solution since January, first time I sent the tablet to RMA.

My situation is very similar to yours. I had three faulty 101G9s in the space of a few months!
Eventually Archos upgraded me to a 101XS but this tablet displays exactly the same problem you are describing.
My screen suffers from touches even when I'm not even handling it.
I don't really want to send back to Archos again (yet) as it means being without a tablet and restarting with all my apps etc yet again.
I have found a way to calibrate the screen to stop this issue.
Hopefully it might work for you too.
First, in Developer Options enable Show Touches.
Then In Repair and Formatting calibrate the screen when you can see the phantom touches being recognised : I have to hold my tablet at the very edges (not touching the screen) and then I see touches displayed at the bottom-left, top-left and top-right of the screen.
Sometimes it takes a couple of tries but you know it has worked when part way through calibration the areas showing touch, stop displaying (as though they're no longer being touched).
I plan to use my tablet as it is until just prior to the warranty expiring and then send it back because, although I have found a solution, it is still far from perfect; the digitiser is definitely faulty.
Sent from my 101XS using XDA app

Thanks Extreme_One that worked for me! Maybe I will do the same and send it back just prior the warranty expiring. Although, I don't know, maybe I keep it as it is, I'm tired to deal with Archos.

enneston said:
Thanks Extreme_One that worked for me! Maybe I will do the same and send it back just prior the warranty expiring. Although, I don't know, maybe I keep it as it is, I'm tired to deal with Archos.
Click to expand...
Click to collapse
I'm really glad I was able to help. The last time I performed this special calibration was about three weeks ago and my tablet has been working fine since.
I just wish Archos would work to get Google Earth working properly. Maybe next firmware update...
Sent from my 101XS using XDA app

Extreme_One said:
I'm really glad I was able to help. The last time I performed this special calibration was about three weeks ago and my tablet has been working fine since.
Click to expand...
Click to collapse
Did it work fine after updating the firmware? Or did you need to do the special calibration after updating the firmware? I mean, do you need to do the special calibration after every updating?
Thanks again!!

I updated to 4.1.2 on day one and haven't reverted back.
I only recalibrate if/when I need to; not needed to for about three weeks now...
Sent from my 101XS using XDA app

Archos are by far the worst piece of kit I have ever used. As for customer service....non existent. I too have a 101XS....with too many problems to list. Ended up getting a Samsung Tab 10"....not a single problem. Archos release a media player....then ask you to pay for the codecs to be able to watch media on it. Cowboy outfit with low spec/tech.....soap box away!

Another bad experience
Hi Everybody.
I'd want to share my own bad experience with Archos service department.
I bought an 101xs at the third quarter of 2013. A few days after it fell down from my hands while the earphones were plugged, the outcome was earphone jack not working anymore.
I asked for an RMA clarifying that the problem was my fault so I wanted to pay for the repair. They agreed and sent me the RMA and I delivered the tablet to France (35 euros shipping cost!).
Briefly: they sent me the device back, unrepaired, saying that warranty did not cover physical damage! No message quoting our previous mail conversation was successful. Always the same reply: "Warranty does not cover physical damage".
I wonder... was I contacting human beings? Maybe they are but, are they Chinese recently migrated to France?
Never ever more Archos!

It's interesting what touchscreen chip (digitizer) does this tablet have? What's the output of "lsmod" and what's the output of "cat /sys/bus/i2c/devices/*/name" on stock firmware? This problems are mostly due to cheap or buggy touchscreen chip or due to bad EM shielding inside some parts of the device. It may happen also when you are charging the device and using its touch screen simultaneously on cheap digitizers.

I realize I am late to this, but after sending in a dead G9 I also got the 101 xs. I must be one of the lucky few, been working great for the last few years, wife loves it.
Did not like RMA experience though, like most it took months. On the plus side, my G9 WAS out of warranty and they still sent me a free replacement.

[Q] "Retroactive Bricking" or "spontaneous" hardware fault? [Xpost One X/X+ Help]

[Q] "Retroactive Bricking" or "spontaneous" hardware fault? [Xpost One X/X+ Help]
*PSA: This will be crossposted in xda GenerAL Q&A and HTC One X+ forums, I hope cross posting is allowed, haven't seen it mentioned in rules.*
Hi all,
Quick disclaimer: I've been lurking parts of xda now and again for a couple years now, have flashed a couple of phones and tablets now and again for mainly practical reasons, recently getting more interested in it as a ""fun" interest or "hobby".
SO: I am very aware that this is my first post, the rules, search function, etc. ..
BUT: After extensively searching both google and specifically xda to help me resolve this issue *myself*, I decided to create an account and post. I'm sorry if this Q should have been put in the newbie thread, my assessment was that it probably has no place there.
ALSO PLZ NOTE: What was meant to be a succinct summary and question somehow turned into a condensed but complete rundown of events, so here is a...
TL;DR:
- Replaced HTC One X+ display/digitizer unit myself, ran fine for 5 weeks.
- Then: flashed twrp 2.7x or 2.8, not sure anymore, before installing Android HD Revolution 33.1 by mike1986, and following the official instructions, which ran great for about week until my phone spontaneously BRICKED THE F*CK OUT COMPLETELY.
(yes, true brick, paperweight, robot-corpse, whatever)
=> Question: IS "RETROACTIVE/RETROGRADE BRICKING POSSIBLE/A "THING"??
If so, what could I have done wrong? (POSSIBLY something to do with a bootimage of firmware that I was sure I had the up to date version of... dunno though).
=========================================================================
About 6 weeks ago:
- Cracked the display of my HTC One X+ badly by dropping it onto concrete-type floor at a rave/party
=> Decided to try and replace it myself, researched for a good while (talking several days here, 90s/00s kids),
=> Decided to replace the display/digitizer unit myself to save money and gain knowledge.
Repair process was challenging and nearly as nerve wracking as playing the WSOP (not kidding, have played it three times), had an issue immediately after putting it back together where it suddenly wouldn't charge AT ALL anymore (NO LED), and overheated, and had unusually fast battery drain of its remaining charge (which never ran out completely before resolving that issue, since I kept turning it off whenever possible).
=> Took it apart and put it together again XX times until realizing the power switch flex cable kept slipping out of its two (jawbone?) connectors during putting it back together (I was doing something wrong with the flex positioning).
=> This resolved the issue.
=> Felt like a hero and that I win at life (since this phone has a rep as being hard to meddle with, and this was my first time even opening, let alone taking apart a smartphone).
=> Continued joyful phone shenanigans for over one month.
=> THEN: Decided to root it, mainly because there was a particular app I wanted that required root ("Quick reply for Whatsapp/Pushbullet", for the curious).
My previous, very limited rooting/flashing experiences =
- Google Nexus One (CWM/Cyanogen) a few times, years ago
- Galaxy Tab 10.1 (CWM/Cyanogen 10.1 ages ago, TWRP/Omnirom Kitkat 4.4.4 recently) a couple times.
So, did my research (or so I thought..?) for this particular custom ROM, decided to go for Android Revolution HD for HTC One X/+ 33.1 by mike 1986 (because it looked fckin awesome, and it was, while it ran) and loved the sh*t out of my "new" phone for about a week. Especially the vastly improved battery life seemed almost surreal, a big deal for a fixed-battery phone.
Then, ONE FATFUL EVENING in a bar, I remember looking at my phone and seeing 35% left, (days before it would've been an amazing 70-80% on an avg. day), which may not be relevant as it was my birthday, so had been using it a lot that day => may be a moot point
- Next time I looked at the phone ( < 1 hour without active use for sure) it was dead.
"Hmmmm," thought slightly drunk me. Whatever, charge it later, weird sh*t happens.
- Got home later, charged it over night after booting it with usb cord attached (mains).
Seemed normal, I even set an alarm.
=> Alarm never rang because it was in a powered-off state again come morning, despite all-night charging.
=> It booted to HTC logo. Seconds later, it turned off again. Held down power again, all I saw was the soft touch buttons flashing red a few times. After this it unexpectedly became (or was secretly crowned):
!! COMPLETE AND UTTER FCKNG KING BRICK OF BRICK COUNTRY AND ATTACHED TERRITORIES !!
No power on with or without volume up/down held for whatever amount of time;
No charging, no heating up when "charging";
No LED in any colour or flashing frequency, ever;
No response after hours and days of charging on different USB cables on PC/wall socket;
PCs and laptops don't register a sign of anything when it penetrates their port parts, etc etc...
...
.Even that semi-mystical bright-light-exposure-while-charging "light sensor manipulation" thing (which apparently worked for a lo of people with similar issues) did nothing for the cause.
Promotion: *Paperweight status successfully acquired.* Yay.
=====================================================
Now, obviously my first thought was that the power flex that gave me trouble during display replacement probably slipped again., somehow (I had taped it down solidly I thought).
=> SO I opened it once again, flex position seemed ok, but I wasn't sure of its functionality as it did look kind of battered from the somewhat unprofessional repair I had conducted on it (which I openly admit to, though I really did try my absolute best).
- Spontaneously took mainboard/battery combo to a local independent phone/accessory shop after being told they'd take a look for free
(I was in there was in there buying a microsim adapter so I could use my ancient Nexus One, since my GF has my old S2 now, which she kindly offered back, but its hers now, so nah. Great phone though.)
=>Shop's advice echoed my thoughts: Flex cable may be screwed, I may have damaged it by bending in the wrong direction/too often, and that damage somehow didn't manifest until much later. I didn't mention the recent rooting + flashing as I deemed it irrelevant at the time.
Their secondary thoughts: Battery or mini-usb port fukt, (which would require soldering, which they don't even offer).
=> SO, feeling confirmed in my layman's assessment, I cheaply got a pristine new replacement flex on ebay, double checked all videos/tutorials, implemented the damn thing with considerably more skill/experience and even higher anticipation. What happened next was shocking:
Absolutely nothing, obv.
=> Did an additional epic f*ckton of internet/forum research, found similar problems and some resolutions, but no real answers, probably because my main problem translates to a kind of hybrid question.
So here I am now am with my core question:
Is it possible to FULLY brick an HTC/any smartphone but not become aware of this until one week later, when the device dies OVER ONE WEEK of reliable and amazing performance?
(and if yes, what aspect/stage of the flashing process is this likely related to?)
If the answer is NO, it must be a hardware fault with probability rank (I think)
:
1.) Battery dead for whatever reason
2.) Mini USB OR mainboard/integral component (equal rank as not sure), possibly caused by incompetent repair, but why or how would this express itself over a month later??
3.) Other, which I'm not aware of.
While researching new ROMS for the N1, I realized that I may have messed up on the "bootimg part" of the flashing process of the Revolution ROM, a part I found v. confusing in the instructions, even after rereading them many, many times. It was about the most recent firmware, which I was pretty sure I had anyway, since it was unrooted before and I do remember installing some firmware updates over the air.
I still did my best to follow the instructions though.
=> Maybe this has something to do with it, i.e. the hardware can't accept a charge because the software allowed it to become too uncharged (a fairly paradox concept to me, but apparently it can happen. Guess it's like a BIOS-type thing).
Thank you for anyone who read this far!
As it stands, I refuse to give up hope so soon after experiencing that rush of having fixed it myself.
Any specific or general help, tips, hints, pointers, replacement phones (One M8 or S5 plz., Iphones will go straight on ebay) would and will be greatly appreciated!!
The obvious choice is to get a new battery and see what happens, but I'm not sure if I wanna sink any more money into this phone, only to later find out the mainboard is at fault (not worth the money replacing), AKA "get a new phone without a contract", which would more than suck for me financially atm (Im ignoring my N1 here, which I love, but don't wanna be stuck with, esp. as it has the standard-issue broken power button (which I actually had repaired once under warranty, back in the ol' days of yore some prefer to refer to as 2009.
So guys: What's my move, if there is one, besides going to a local/online service centre (I live in Germany btw.) and probably paying unproportionate cash money to even have it looked at?
Cheers, thanks, merci, danke
PS: Just saw the polling function, so I attached one just for the hell of it, to see what happens (never used one before).
If you feel both qualified AND so inclined as to pass judgement on this here serious business, please indicate what you think may be the cause of my issue.
Poll is in "General QA" Forum original post: http://forum.xda-developers.com/general/help/retroactive-bricking-spontaneous-t2948954

*BUMP 1*
Come on guys, I know it's a wall of text, but can't someone at least answer the TL;DR?
=> Is is possible to flash a custom rom which then (possibly because of improper installation) causes the phone to brick about a week later?
Simple question surely!