Related
I recently had a problem with my 1st Touch Pro with image ghosting/ burn in and ive just had it replaced. Now the same problem is happening with the new device. The problem only seams to happen with custom roms being used on the device. If i re-flash my phone back to the default/stock rom i get no screen problems at all.
Any idea why this only happens on custom roms and not the default/stock rom??
edit: ive attached an example of what i mean in image ghosting/burn in. Just in case some people wasn't sure what i meant by it.
More info?
Heya! What was the last ROM you had this problem with? Version info would be extremely helpful as I have heard that specific builds have some graphics bugs.
I've had that same issue as well on 2 different fuze's. Using various builds of EnergyROMs... However, after reflashing to stock and using it awhile, I'd get the ghosting on that too.
Anyone have any ideas?
Ehh my 2nd Fuze is doing this so I'm getting a replacement, and I'll just do the HTC ROM upgrade and keep WM6.1. I'm tired of it, and the landscape view also distorts the start menu icons 90% of the time.
Having flashed back to a stock rom, doing a hard reset... Playing with it for awhile... The ghosting is evident on it as well... I've also had where the bottom section of the screen will flicker quickly...
Anyone else?
I think it's a hardware defect. My first phone did that, and then after a few weeks, I had to get a warranty replacement because the screen eventually went completely black after doing it intermittently).
I've had both ghosting effects & occasional rapid flickering since I first bought the Fuze back in November. It's intermittent but happens most when the device is hot (either from use or simply being in a hot location). So far it always clears up after a while. This happened on the stock rom and every custom rom I've used so far.
I'm fairly certain it's a hardware issue with the Fuze/TP because the ghost will tend to remain there for a while even after a soft reset.
Hopefully my good fortune continues and it doesn't end up breaking permanently some day.
it is definitely a hardware issue.
I just received a "repaired" phone back from HTC today only to turn it on and find the same problem. I had to call again today and complain...and the only thing they could do for me was ask me to send it in again....so pissed.
I literally got 5x FUZE replacements and each had this until this last one I've gotten...!
Vid: http://www.youtube.com/watch?v=fFb4bQomqPw
Thx
JFlitt
JFlitt said:
I literally got 5x FUZE replacements and each had this until this last one I've gotten...!
Vid: http://www.youtube.com/watch?v=fFb4bQomqPw
Thx
JFlitt
Click to expand...
Click to collapse
were they replaced through HTC or ATT?
I am on my third Fuze.
First day when I upgraded to Fuze the screen started doing this. So I took it back to AT&T for replacement. On the drive back home screen on second device started doing exact same thing. Took it back and got yet another replacement. This one works, but I have seen it happen once or twice in the 3 or 4 months I've had it.
AT&T also told me when I got this phone that it was the last exchange I could make for the 90-day exchange. If I had another problem I'd have to send this back to the company. WTF is that all about? You're going to inconvenience me because you keep giving me bad eggs? At least this one works right.
Is anyone with a Touch Pro having the same issues? Or is it all just us AT&T customers?
I have an O2 Xda Touch Pro. The only symptom I have that remotely resembles the ones listed here is the flickering at the bottom. But, in my case at least, the flickering is caused by a particular shade of gray displayed in Opera...and that's the only time it happens. So, again for me, it seems to be a software issue.
Drew
Flickering is another side affect that mine occasionally has... just in the bottom 1/5th or so of the screen... Most easily seen when in landscape mode in messaging.
those are all hardware issues too, its just only being displayed because that certain shade of grey is whats making it visibly noticeable.
Well, we'll see if replacement number 4 has the same issues soon...
They actually offered me a BlackBerry Bold/9000 as a replacement phone like it is even in the same universe.
Hardware differences?
Anyone with a buggy Fuze want to post the part number / sku number etc...? Maybe we are looking at a bad batch or a bad but unannounced hardware version?
I had this too on energyrom, I allways passed it off as a touch flow 3d opengl issue which would draw to the screen.
But thinking about it, it does occour when the device is hot, and the screen flickers also.
But It allways goes away after a soft reset for me.
Vodaphone UK TP
I have this problem too :/
Well, I just got my replacement, and it is doing it as well. I'll post some screen shots of it later on today.
Anyone want to tell me what numbers we want/need?
Hey guys,
I've just receieved my third HTC handset with what I'd consider to be a major issue.
HTC Touch2 in 2009 - would often power off during calls (probably due to WinMo). Hardware buttons quickly became loose after about a month of use, and the backlighting stopped working.
HTC Legend in 2010 - this phone is two months old and the top speaker is so broken I can barely hear somebody on a call. Everything crackles and pops and, according to people on the other end, they can barely hear me either. It's annoying as when I bought it the call quality was great but gradually the speaker got buzzier and buzzier.
HTC 7 Trophy - the most serious of the bunch. Yesterday, whilst web browsing, the phone displayed a still multicoloured screen of static. None of the buttons would work. After taking the battery out and restarting, the static re-appeared. I've managed to power on the phone since - you have to wait an hour with the battery out - but you get the same static lock ups when web browsing or using search after about five minutes. Having had a similar experience on my laptop, it looks to me like a GPU failure.
Am I the only one who has experienced incredibly shoddy hardware quality control from HTC? I'm going to have to replace the HTC Trophy and, at the moment, I'm starting to seriously question going with an HTC. The touch2's button issues were forgiveable because that was relatively cheap, the Legend's speaker was incredibly annoying but the Trophy's GPU failures are completely unforgiveable IMO. They render the phone completely useless.
Am I just unlucky or have others experienced similar concerns?
Cheers
My Hero has been fine, along with my touch... Although that met a washing machine in the end
Finally ~ Someone With A Similar Issue
Finally, someone that doesn't purely worship HTC... Although I haven't experienced issues to the magnitude of your's, I haven't been 100% happy with my phone since the day I bought it. I have a HTC Desire, and I got this phone in confidence after reading many reviews about how good the phone was, these reviews were clearly written from people with 0% experience with the phone.
I will number the issues I have had with the build quality of this phone...
1) The case on the back of the phone, has only ever been took off about 4 times, I have never dropped my phone or anything, however it starting to come off, yes, I can take the back of my phone off, without using the finger slot.
2) The screen is so easy to scratch? It was in a pocket with an Asthma spray, and there was no vigorous shaking of my pocket, yet somehow the screen just completely f****d up man... wow.
3) This is probably the worst issue I have. Every time HTC releases an update for my phone, I run into some sort of issue. I got my phone in May/April 2010 (it's on Orange UK however de-branded and now due to update issues, running a custom ROM) and immidiatley I found that an update had been released. After downloading the update the phone started to install the update, however it restarted and nothing happened. Left it for about an hour, nothing... So yes, I did the worst, took the battery out and messed it up completely. The shop I got it from forced me to send it to HTC, it took them 5 weeks (VERY poor customer service) and when I got it back they had barely fixed it, as when I turned it on, it finished installing the update?
4) I have had some other software issues, such as the system occasionally locking up and having to remove the battery to get anything to work. Occasionally the screen will lock up, like I won't be able to click any icons, however I'll be able to swipe from screen to screen, and it really can be quite annoying. As far as battery goes, it will last me an entire day, but will require a charge at the end of the day.
However, I think me and you are in a minority. I'm 14 years old, and I talked my Dad into buying a HTC Desire HD. He hasn't had a single problem with his, it installs updates perfectly without and issue, and the software performs seaming-less (except for a problem with a process that took up 80.9% of the RAM, fixed by turning the USB Debugging on?) So I believe HTC are good, theres just a few really, really bad apples in there, and unfortunately HTC won't admit this, and don't want to do anything about it... I hope I helped, I'm fairly new on here...
Cheers, Michael.
Well guys,you are a minority indeed.This Tuesday I received my Desire HD,which is my fourth handset from HTC.I have had a Diamond,a Hero,a Desire and now the Desire HD.The only problem I ever had was with my Diamond which,after one year and a half took some water in it without getting exposed to any water,but it was because the climate here is very humid.Other than that I have never had an issue.And I am no fanboy,if I had problems I would change without second thought.
I'll just tell you that a friend of mine punched my Desire HD with his full strength(don't ask why) while it was in my pocket.I thought the phone was done for,scrap,but the phone is like nothing happened.My friend's hand wasn't so lucky however,it still needs ice!
I already sent my phone to Samsung to repair it under warranty, but I just wanted to see if any one else experienced this problem with Blaze 4G.
Basically, the problem first appeared rarely but progressed within several days to the point that the phone's touchscreen is unresponsive most of the time. It is not present constantly, and that confuses me. It also does not depend on what ROM I am using at the moment, so I guess it must be a hardware problem. The touchscreen can work for 30 minutes to several hours and then become unresponsive for half-day or so. Removing battery or rebooting the phone does not have any effect on this occurence - it still is unresponsive at random.
E107946 said:
I already sent my phone to Samsung to repair it under warranty, but I just wanted to see if any one else experienced this problem with Blaze 4G.
Basically, the problem first appeared rarely but progressed within several days to the point that the phone's touchscreen is unresponsive most of the time. It is not present constantly, and that confuses me. It also does not depend on what ROM I am using at the moment, so I guess it must be a hardware problem. The touchscreen can work for 30 minutes to several hours and then become unresponsive for half-day or so. Removing battery or rebooting the phone does not have any effect on this occurence - it still is unresponsive at random.
Click to expand...
Click to collapse
Haven't heard any issues similar to yours. You probally had a lose connection or worse, but as far as I know the only bug across the boards was the issue not hearing when making/receiving a phone call. From what I seen and others mentioned is the audio bug only occurred on custom ROMs not stock.
---------- Post added at 08:51 PM ---------- Previous post was at 08:45 PM ----------
Where do you live? Maybe its from moisture. I've heard others (not blaze users) report that there phone became unresponsive due to overactive moisture sensors. They go crazy over in the middle east and places with high temps or humidity.
jbats said:
Where do you live? Maybe its from moisture. I've heard others (not blaze users) report that there phone became unresponsive due to overactive moisture sensors. They go crazy over in the middle east and places with high temps or humidity.
Click to expand...
Click to collapse
I live in Bay Area (South Bay). The humidity is quite low, actually. The phone has never been placed in a moist or humid environment. This problem appeared out of the blue. It was not a ROM issue for sure, as it appeared in stock GB, stock ICS and AOKP JB. Heck, the screen was unresponsive even in TWRP
E107946 said:
I live in Bay Area (South Bay). The humidity is quite low, actually. The phone has never been placed in a moist or humid environment. This problem appeared out of the blue. It was not a ROM issue for sure, as it appeared in stock GB, stock ICS and AOKP JB. Heck, the screen was unresponsive even in TWRP
Click to expand...
Click to collapse
Sounds as if it was hardware related pro ally a bad sensor
Well, they updated the status as fixed and shipped. They put the cause as "touchpad failure" and the solution - S/W update. I am kind of sceptical of this repair, but tomorrow I shall see for myself.
Sent from my Prism using xda app-developers app
E107946 said:
Well, they updated the status as fixed and shipped. They put the cause as "touchpad failure" and the solution - S/W update. I am kind of sceptical of this repair, but tomorrow I shall see for myself.
Sent from my Prism using xda app-developers app
Click to expand...
Click to collapse
sounds like they just did a wipe and flashed stock...
Racing19969 said:
sounds like they just did a wipe and flashed stock...
Click to expand...
Click to collapse
Yes, that is what they did apparently. I got phone today with a stock ICS (it had GB when I sent it to them), and it still has the same problem It seems that people who are responsible for repair have no clue about what they are supposed to do.
I will send it again and in the meanwhile, I will get a T-mo Galaxy SII from Walmart. If Blaze gets fixed - great, if not, I will end up with a slightly more performing phone for $300.
Almost a month later, I received my phone second time from Samsung repair department. Well, this time they actually listened to me and replaced the touchscreen. Now, the phone works fine.
In this past month I have tried:
1) T-Mobile Prism (Huawei)
2) T-Mobile Exhibit 4G (Samsung)
3) Family Mobile Galaxy S II (same as T-Mobile but without a SIM card included)
4) T-Mobile Optimus L9 (LG)
I had high hopes for S II and even considered keeping it, but it turned out to be a very mediocre phone (even though it was still better than the AT&T version). Too large and, as a result, uncomfortable; in addition, the GPS was extremely slow to respond and almost any unofficial version of 4.1.2 resulted in an extremely bad sound quality. Noticeably larger screen still had the same resolution as the Blaze 4G.
The most acceptable phone was perhaps LG Optimus L9 - it was thin and lightweight, had high resolution (960x540), good reception and responsive GPS. The only disadvantage was not having NFC. I used it stock and unrooted for the entire 2 weeks, so I do not know how it would function with 4.1.2. If somebody wants a well-functioning smartphone for only $200, I would highly recommend it.
If my Blaze 4G breaks down again, it will probably not have warranty (until March 2013),so my next device would most likely be Nexus 4.
I've read a few threads on the screen Flickering and there doesn't seem to be any resolution .
I'm on my 3rd tablet now (thanks best buy accident damage warranty!) And this one is flickering worse lately than ever. I updated to the latest firmware, yesterday only to boot up to horrible bouts of flickering during the setup screens.
The odd thing is, there seem to be no consistency to it. Some days it's so had I can't even use the thing, other days it doesn't happen at all. I use the tablet every day for notes or PDF viewing. I've used it with no magnetic cover (totally naked) and with the cover.. doesn't seem to change the occurrences.
I've turned overlays on/off force gpu render on/off.. nothing seems to fix it. Sometimes changing the overlay will reduce the flickering other times it doesn't affect it at all.
I hate to say it, but if I can't resolve it, I'm going to be forced to move to the surface 3.
I'm an electrical engineer and I've done as much trouble shooting as I can think to do.. but I've come up empty handed.
Anyone else have these problems? Has anyone found a definitive fix?
I sent mine back 3 times. The first was a reset. Thanks for wasting my time. The second was a motherboard and that didn’t do it. The third time they did a motherboard, digitizer, and usb port. It's finally stable and back to normal. After 5 trips back, the BB warranty triggers a new unit. Check if it triggers a refund.
I get it occasionally, so far I'm able to resolve it by booting into custom recovery (TWRP) and clearing dalvic to allow all apps to rebuild. Sometimes this resolves it for a few days, sometimes a couple of weeks. Its a repeatable "fix" that makes me question if the issue is related to memory or trim or something like that. Kind of reminds me of how with the first generation nexus 7s one would see slow downs after a while and filing storage with fake data then deleting it would improve performance for a while.
I'm definitely not a tender user of the device. I go back and forth between multiple ROM's and kernels on a daily basis testing what is testable, and unfortunately also what is not. Anyway, even though mine was bought as refurbished on eBay, I have never had any issues like the ones you describe. More specifically, I have never had any issues what-so-ever, that was not created due to my own ignorance. To me the device seems indestructible.
Besides, I would hate to be in the place of my device, or I would definitely have turned schizophrenic. Should I feel bad about pushing it through all this?
Because we're trying to figure out if it's related to a specific device type, which one do you have? P900, 905, 907A or another?
ShadowLea said:
Because we're trying to figure out if it's related to a specific device type, which one do you have? P900, 905, 907A or another?
Click to expand...
Click to collapse
P900 wifi. Us version bought at best buy.
Today the tablet has been rock solid, I have literally done nothing between when it was flickering like mad and now.
I wonder if it might be related to some kid of data transfer. either over wifi, or when data is written or read from storage or SD card. I've take then SD card out to eliminate that as the problem.
Mine was P900 from BB
Issue lies with the screen.
This happened with me I sent it back to Samsung, 3 times. They seem to have finally got it right. They replaced the battery and then the display screen. Now it appears to be working I will let you know after a month if it is still good. They also told me that they will not replace the device even though I bought it and the issue was right from the start. Not even 6 months old. When working the device is excellent.
Ah, so now we know for sure the battery is replaceable. That's good news. Maybe someday our batteries will no longer hold a charge and we can replace it. Now for a good video on tear down and what tools to use to do that and where to get a replacement battery. I know it's early for most of us but someday......we will have to replace that battery. I'm one of those that keep my toys (computers/laptops/tablets/phones,) for many years.
Mine is running like new since last service. Getting the BB Geek Squad warranty has paid for itself already. I get 2 years on anything over $500.
Mine is a p900. I purchased from samsung website. Mine has been doing it fresh out of box. So bummed.
Ive had my 12.2 since march and it recently started flickering. It seems to tuen of the screen for a millisecond especially when lots of refreshes happen. Like scrolling a pdf. A few days back it was bad. Now it has gotten better and I havent noticed anything.
{Diemex} said:
Ive had my 12.2 since march and it recently started flickering. It seems to tuen of the screen for a millisecond especially when lots of refreshes happen. Like scrolling a pdf. A few days back it was bad. Now it has gotten better and I havent noticed anything.
Click to expand...
Click to collapse
My P900 has just begun flickering exactly as you describe. So I should just be patient and hope it goes away by itself?
I'm flickering again. Turning the screen brighter is what triggers it for me. Returning to stock just to get it back and have it flicker again to hit the magic 5 returns may be what I have to do.
https://youtu.be/CvxbVft69Kg
I just followed this guide. Its been a week now, not had any flickering since I did it.
Manya3084 said:
I just followed this guide. Its been a week now, not had any flickering since I did it.
Click to expand...
Click to collapse
Lifting the motherboard only temporary close the gaps of cracked battery connector. The permanent fix need to do: re solder the battery connector.
Look closely under magnified glass or microscope , you'll see the cracked solders. You can test by pushing the connector slightly, a bad one will move easily or lift off from its solder joints.
This video was removed from the poster after I pointed out his guessing solution. Flickering screen has nothing to do with LCD connector on the motherboard.
Lifting mother board actually you're applying pressure on the battery connector from rear cover.
I have had my P900 sent to Samsung service twice without having the screen flicker fixed. I thought this was a known problem and that Samsung themselves should be aware of it? Maybe I should supply some XDA links next time...
Skickat från min SM-P900 via Tapatalk
bluebirch said:
I have had my P900 sent to Samsung service twice without having the screen flicker fixed. I thought this was a known problem and that Samsung themselves should be aware of it? Maybe I should supply some XDA links next time...
Skickat från min SM-P900 via Tapatalk
Click to expand...
Click to collapse
Depend on where you send for service, they know how to fix it now. Service Centers actually are contractors provide services for Samsung and others, the fact that most people don't know.
http://forum.xda-developers.com/showpost.php?p=59573206&postcount=100
It Works. Battery connector replaced. Smoooooth
After 2 visits to Samsung , my unit finally works fine.
Motherboard and LCD were changed first time. But issue persisted.
Second time, battery connector was replaced. Since then it has worked very very smoothly.
Beut said:
Depend on where you send for service, they know how to fix it now. Service Centers actually are contractors provide services for Samsung and others, the fact that most people don't know.
http://forum.xda-developers.com/showpost.php?p=59573206&postcount=100
It Works. Battery connector replaced. Smoooooth
After 2 visits to Samsung , my unit finally works fine.
Motherboard and LCD were changed first time. But issue persisted.
Second time, battery connector was replaced. Since then it has worked very very smoothly.
Click to expand...
Click to collapse
Thanks, missed that other thread. Next time, I'll send them an en explicit request to replace the battery comnector, and refer to those two threads.
Stefan
Tapatalked on some kind of Samsung tablet
I pre-ordered my S7 edge (SM-G935FD) and was using it moderately (as a normal user generally does). Everything was quite normal and I didn't tweak any of its settings. I didn't even try out any graphic intensive games on it. But on the 20th day of its usage, I noticed a slight tinge of discoloration on the screen, appearing as if screen burn-in had ocurred. I tried factory reset and the situation worsened after 22nd day. The whole screen went greenish! I don't know if it's related to "Always On" feature but I can presume that as the only reason for the sudden burn-in. Hopefully, I was able to replace it with a new one as it was under 30 days replacement guarantee.
Here are the images of that defect:
1. http://i.imgur.com/ZEHxYrK.jpg
2. http://i.imgur.com/P3Mi7v9.jpg
3. http://i.imgur.com/2Ycg1oB.jpg
4. http://i.imgur.com/fLJx1ko.jpg
5. http://i.imgur.com/Veqh7Ft.jpg
6. http://i.imgur.com/0cEkEkA.jpg
7. http://i.imgur.com/fLypn9J.jpg
8. http://i.imgur.com/V4JACXP.jpg
9. http://i.imgur.com/iOmtR2T.jpg
I want to know if anyone has any other reason for screen burn-in to happen. FYI, the phone was never dropped, pressed on screen, rooted nor tweaked any other display settings in developer options.
You just got a defective unit, doesn't have anything to do with AOD.
if it was, more people would say this, and the AOD jumps around the screen to prevent the burn-in
Nothing to do with AOD at all
lvnatic said:
You just got a defective unit, doesn't have anything to do with AOD.
Click to expand...
Click to collapse
Liquid Li0n said:
if it was, more people would say this, and the AOD jumps around the screen to prevent the burn-in
Click to expand...
Click to collapse
I agree with you, but why did it happen all of a sudden on 20th day of its usage?
All I can assume is that pre-order lots are quite low graded!
Definitely not AOD related.
That is definitely not related to AOD. This is a hardware fault. You'll need to return it for warranty repair.
the_scotsman said:
That is definitely not related to AOD. This is a hardware fault. You'll need to return it for warranty repair.
Click to expand...
Click to collapse
I already got a replacement. But that thing was worring me in case it happens again!
Sent from my shiny new SM-G935FD using Xda-Developers mobile app
techsammy said:
I agree with you, but why did it happen all of a sudden on 20th day of its usage?
All I can assume is that pre-order lots are quite low graded!
Click to expand...
Click to collapse
Every company has these issues, you have to realise this phone was manufactured in millions and accidents can happen. I got a black phone first and later switched to gold simply because I preferred the color, both phones were perfectly working. And AOD definitely is not causing this, you can use the feature without worrying.
like everybody else is saying. nothing to do with AOD. this can happen to everyone. don`t even think its a burn-in, seems like parts of the screen is dying(as for the curtin effect) you don`t need to worry, this prob won`t happen again
techsammy said:
I already got a replacement. But that thing was worring me in case it happens again!
Sent from my shiny new SM-G935FD using Xda-Developers mobile app
Click to expand...
Click to collapse
This is not even screen burn in. If it's screen burn in you can see the aod clock every time. Not these discoloration issue. You just have a faulty unit. That's all.
Sent from My Galaxy S7 Edge
Thanks everyone. I'm relieved now. ?
Sent from my shiny new SM-G935FD using Xda-Developers mobile app
I also had problems with my first S7e. Had a dead pixel and was not able to fix it. Changed it and now everything is ok.
To generally say preorders had lower quality is wrong i would say. At the moment it seems to be obly a few devices and compared to the order volume its normal to have a few problems with some small amount of devices. So please change the header or let delete it as it might be confusing and fear some people without any reason.
Thanks
techsammy said:
I pre-ordered my S7 edge (SM-G935FD) and was using it moderately (as a normal user generally does). Everything was quite normal and I didn't tweak any of its settings. I didn't even try out any graphic intensive games on it. But on the 20th day of its usage, I noticed a slight tinge of discoloration on the screen, appearing as if screen burn-in had ocurred. I tried factory reset and the situation worsened after 22nd day. The whole screen went greenish! I don't know if it's related to "Always On" feature but I can presume that as the only reason for the sudden burn-in. Hopefully, I was able to replace it with a new one as it was under 30 days replacement guarantee.
Here are the images of that defect:
1. http://i.imgur.com/ZEHxYrK.jpg
2. http://i.imgur.com/P3Mi7v9.jpg
3. http://i.imgur.com/2Ycg1oB.jpg
4. http://i.imgur.com/fLJx1ko.jpg
5. http://i.imgur.com/Veqh7Ft.jpg
6. http://i.imgur.com/0cEkEkA.jpg
7. http://i.imgur.com/fLypn9J.jpg
8. http://i.imgur.com/V4JACXP.jpg
9. http://i.imgur.com/iOmtR2T.jpg
I want to know if anyone has any other reason for screen burn-in to happen. FYI, the phone was never dropped, pressed on screen, rooted nor tweaked any other display settings in developer options.
Click to expand...
Click to collapse
Exactly the same thing happened in my friend's Note5 and he got a replacement in india........it happened within 2-3 days of his purchase............criticize samsung india on their official twitter and facebook pages for deploying poor quality standards in their indian manufacturing unit,i had a terrible time finding a good black onyx device in india as two of them had dead(black) pixels in their resp display's and one had a terrible front cam ......................
You just got a lemon screen, just unlucky really. Doesn't really happen often and when it does, only a minority units (yourself etc)
Like most are saying. That doesn't look like burn in. Just a bad display. Bound to be a few. Sorry for your bad luck.
Sent from my SM-G935T using XDA-Developers mobile app
techsammy said:
I agree with you, but why did it happen all of a sudden on 20th day of its usage?
All I can assume is that pre-order lots are quite low graded!
Click to expand...
Click to collapse
Because sometimes things fail. Get it repaired under warranty.