Hey guys...
So, I have my Desire Z since about 4 weeks and nothing went wrong with it.
Really NOTHING bad happened, it didn't fall on the floor, didn't fall into water, etc etc.
So this afternoon I unlocked it and suddenly I got a blank grey screen.(worked perfect in the morning) The phone did react to my power up/on button, but I couldn't see what I was doing. Also the touchscreen worked, because I could unlock it (I heard the unlock noise) but I only get a blank grey screen.
I tried Bootloader and Battery pull. Also I took out my SD/SIM/Battery and just blow through the whole phone but nothing want to happen:-(
By the way, my phone is fully rooted and running on Cyanogenmod7 since 5 days. Everything worked perfect until this afternoon...
EDIT:
Looks just like this http://i51.photobucket.com/albums/f368/forthcomingtangent/DSCI1196.jpg
I should start by saying I'm not that new to android, but I am by no means an expert and have not been able to figure out how to get out of a very confusing situation.
My tf700 is currently running 4.1.1 Jelly Bean and the newest firmware version 10.4.4.23. Before the firmwarm update, I had unlocked my device thinking that I would try out some of the newer roms based on many recomendations from the facebook Infinity group. I never got around to rooting and installing TWRP, and a few days later I updated to the current stock firmware version manualy (downloading zip from website, flashing from stock recovery). Everything worked great for the first 2 days, and I had compeltely forgoten about rooting/romming thinking that the risks far outway the reward as my device was already near perfect. This morning my infinity began to act funny. Touch responseiveness was awfull (about 1/3 times I pressed, it would react) and it would sporadically stop charging while connected to a power supply. Some time later, while I was watching a flash video my screen turned completely blue and I force restarted it by holding the power button. From then on, I could not turn on my infinity and I tried EVERYTHING (pushing the reset button with a pin, trying a cold boot, holding power for 30 sec etc.). When i tried any of these combinations, the device would start vibrating and the vibrations would not stop. Also, the screen remained black the whole time and nothing I did would even get me a faint glimmer of any sort of screen response.
Has anyone had this sort of issue? I do not think this is a firmware problem seing as it worked fine for 2 days with this firmware and I am at a complete dead end as to what to do. Because I am unlocked, I can not send in my infinity for repair as my warranty is gone. Any help with this issue would be greatly apreciated!
~ Rock
rock1324 said:
I should start by saying I'm not that new to android, but I am by no means an expert and have not been able to figure out how to get out of a very confusing situation.
My tf700 is currently running 4.1.1 Jelly Bean and the newest firmware version 10.4.4.23. Before the firmwarm update, I had unlocked my device thinking that I would try out some of the newer roms based on many recomendations from the facebook Infinity group. I never got around to rooting and installing TWRP, and a few days later I updated to the current stock firmware version manualy (downloading zip from website, flashing from stock recovery). Everything worked great for the first 2 days, and I had compeltely forgoten about rooting/romming thinking that the risks far outway the reward as my device was already near perfect. This morning my infinity began to act funny. Touch responseiveness was awfull (about 1/3 times I pressed, it would react) and it would sporadically stop charging while connected to a power supply. Some time later, while I was watching a flash video my screen turned completely blue and I force restarted it by holding the power button. From then on, I could not turn on my infinity and I tried EVERYTHING (pushing the reset button with a pin, trying a cold boot, holding power for 30 sec etc.). When i tried any of these combinations, the device would start vibrating and the vibrations would not stop. Also, the screen remained black the whole time and nothing I did would even get me a faint glimmer of any sort of screen response.
Has anyone had this sort of issue? I do not think this is a firmware problem seing as it worked fine for 2 days with this firmware and I am at a complete dead end as to what to do. Because I am unlocked, I can not send in my infinity for repair as my warranty is gone. Any help with this issue would be greatly apreciated!
~ Rock
Click to expand...
Click to collapse
Update:
I can now rarely get it to vibrate for even a second holding the power for a long long time. Screen does not come on at all. Looks completely dead.
By your description sounds like a dead or dying LCD.
Sadly RMAing to Asus may cost you out of pocket.
Where did you get the tablet and how long ago?
Thats OK said:
By your description sounds like a dead or dying LCD.
Sadly RMAing to Asus may cost you out of pocket.
Where did you get the tablet and how long ago?
Click to expand...
Click to collapse
I was hoping it wouldn't lead to something like this. I got my tablet from Amazon around the first week of september. I have treated it very well.
I'm not quite sure how it could have burned out, my brightness is usualy <50% and I have used the super IPS+ more less time than I can count
on one hand. If this is the case, Is it possible that a technical problem like this would still be repaired on warranty seeing as it has nothing to do
with the bootloader?
Also I'm not sure how this explain the constant vibrating that does not turn off untill the battery runs out. The way I see it is you could be right, the tablet is trying to tell me it's not going to work, or there is really some kind of software glitch.
Have you ever had LCD problems with a tablet? any idea how much this could cost?
rock1324 said:
Have you ever had LCD problems with a tablet? any idea how much this could cost?
Click to expand...
Click to collapse
I've not had any manufacturing problems with my tab.
I don't see anything you may have done that caused the screen to go bad.
Sounds odd yet a few folks have had their tablet just start working again after seeing similar dead LCD's.
The vibrate thing is weird...almost like a bootloop with no screen.
There's a chance Asus may co-operate if you contact them for an RMA.
It's worth a shot...not sure if Asus has any standard repair rate for this sort of thing.
Curious do you see the back-lights in a darkened room?
Thats OK said:
I've not had any manufacturing problems with my tab.
I don't see anything you may have done that caused the screen to go bad.
Sounds odd yet a few folks have had their tablet just start working again after seeing similar dead LCD's.
The vibrate thing is weird...almost like a bootloop with no screen.
There's a chance Asus may co-operate if you contact them for an RMA.
It's worth a shot...not sure if Asus has any standard repair rate for this sort of thing.
Curious do you see the back-lights in a darkened room?
Click to expand...
Click to collapse
Thanks for the advice, I have heard some terrifying stories of Asus customer support (never had a problem with them myself) and of devices just being completely lost in their care.
To answer your question, no the back lights are not visible at all. The only way I know the Infinity is somewhat alive is by the led coming on while charging and the somewhat random vibrating patterns that happen when trying to boot up.
Hello everyone,
I am an owner of an LG Nexus 4 for a few months now.
The device worked well for the first few months, than one day I dropped it and the screen shattered
The touch sensors stopped working, although the LCD display didn't,
So I had the screen replaced and everything went back to normal.
Then, after the 4.3 update I think, I started having problems with the mobile connections, it died all of a sudden and didn't came back, and the device went off, and when I turned it back on, the battery indicator showed a lower percentage than before, than the device went off again.
Mostly, after the first shutdown the device wouldnt come back unless i charged it.
I also had the battery changed because it turnes out it got inflated (turnes out that happens), and it didn't help either.
I thought the 4.4 update will help, but it didn't.
What could the problem be? Is it hardware or software?
As the title says, I'm very frustrated. It could be from the hit he got when the glass broke, some interior parts could have got hurt,
Or from when the battery inflated.
or that I just got a crappy device in the first place, who knows.
Thank you and sorry for the long post.
Yours,
Yarin.
I'm not sure how this is possible, but about once or twice a day, the back button on my S6 is pressed on it's own. It has happened when the device has been on the desk, I see the soft keys light up, the device vibrates like they've been touched and the app I was on went back, all while I was not even touching the device.
It's happened mostly when I'm holding the phone but not even close to touching the buttons, and once it happened and pressed the back button about 10 times in a row while I watched it.
The phone is completely undamaged, perfect condition, never touched water, not dirty at all, buttons are 100% clean. Happens while it's charging or on battery.
Has anyone else experienced this?
(My device was repaired by Samsung for a different issue, motherboard replaced, this only started happening after the repair)
i have, started like yours random. then it started happening more and more so when i was at the store waiting for someone i decided to factory reset ( factory reset twice while at the store) but it got worse. couldn't even get passed initial setup the phone just kept spamming back button so i just kept going back. luckily i already ordered a replacement s6 from tmobile since i was having some other issue with the phone. sadly the replacement s6 took over 7 days to get here. shipped through UPS and got to hawaii then for some reason UPS gave it to USPS for delivery. kinda sad that i ordered screen protectors 2 days after i ordered replacement phone and the screen protectors got here 4 days later through USPS. but other than that my NEW ( we all know its refurbished) galaxy s6 so far has no issues. even the no audio on calls is fixed.
also if you are going to order a replacement, be sure to let them know you have a GALAXY S6 and the date it was released. i say this because the 2 tmobile reps i talked to kept asking questions they say it was for them to determine if my galaxy s6 that was what 2 almost 3 months old at the time was still under warranty
My s6 was showing the same issue with the stuck back button.
It started randomly but than it went crazy and stuck. I wasn't even able to use it.
But 1 factory reset fixed it.
But yesterday the random stuck back button started again when the phone was on my desk and it was really hot (weather was hot as well as the phone). I turned it off for a while and apparently the issue stopped.
I'm not sure it's temperature, firmware, whatever related but I really don't want to factory reset it again.
No solution here, but it is happening to me as well
Solved
Hi i had the same problem aswell , i bought samsung s6 in Pakistan, after the update the back button kept pressing ghostly, i went to local samsung repair shop and the assistant reset something from the setting and then it was fine, i even asked him what you did and how you did? but he said it is secret lol very stupid. i could have post the solution if i know it, but i think it is very easy and something to do with setting. i am sure it is not hard/soft reset. i will post this on other forums to help other people.
thanks
having this problem with my phone too, i cant even get it to stay on the settings screen long enough to back up my stuff
edit: well i think i solved it. i tried clearing the cache, didnt work. then i did a hard reset, didnt work. then i went back and cleared the cache and did a hard reset at the same time and it seems to have worked.
+1 same problem. It happens mainly when the phone is on the move. Funny thing it happened 3-4 times while taking the metro (go figure) with the data on. Usually when I turn off the data, it reduces the amount of back press.
Normal reset doesn't solve the problem. It stops after a while, probably when the phone cools down. I can't seem to reproduce it, but I believe it has something to do with the data on.
I don't really want to factory reset so I'm going to write to samsung directly as the phone is brand new.
i am having same issue too.
---------- Post added at 09:20 PM ---------- Previous post was at 09:16 PM ----------
Did anyone try loading a custom rom and got it fixed ?
I've had that issue with my first one. Took it back ASAP as it was DOA. Got a brand new one 3 days later as they didn't have any in stock. This one doesn't have any problems. Don't worry to mutch about it. Get it exchanged.
It is a hardware defect: When the phone turns up power to the radio to strengthen the connection, it can cause Electronic Noise to leak over the connection into the capacitive buttons (due to poorly insulated shielding tape), causing the phone to think the buttons were pressed. That's why you notice the problem more when roaming -- the device needs to be repaired/replaced.
I have the exact same problem...did anyone contact the manufacturer and got a response on the matter?
I believe it may be an app setting messing with the system settings. My device did it once and wouldnt allow me to use my device. After factory reset it made it worse so i used twrp and wiped everything but my modem and flashed my stock firmware and it stopped and hasnt done it since
Sent from my SM-G925P using Tapatalk
faiding said:
It is a hardware defect: When the phone turns up power to the radio to strengthen the connection, it can cause Electronic Noise to leak over the connection into the capacitive buttons (due to poorly insulated shielding tape), causing the phone to think the buttons were pressed. That's why you notice the problem more when roaming -- the device needs to be repaired/replaced.
Click to expand...
Click to collapse
Hum that's interesting, thanks for your precious input on this.
I did contact Samsung who asked me to do a factory reset. It didn't change anything.
They redirected me to a Samsung office in Paris, not for repair but for a deeper factory reset... (not sure what they are talking about), but I haven't been there since due to lack of time.
However, I didn't experience the problem since the last update FXXU3QOKN so I'm keeping an eye on it.
Following "faiding's" comment, I'll probably pay them a visit for a replacement.
working "workaround"
workaround:
lower the speaker volume to ~75% in all settings (Media, ringtone, system, notifications, etc...)
Whats going on? why is it working?
some posts ago someone (user called "faiding") mentioned something about EMC leak, or at least he meant to, by mentioning a faulty insulation.
with that in mind i did some testing and found out that the closes radiating component it the speaker... and once you lower its emissions even thought the faulty insulation, the EMC leak is sufficiently low and the 'capacity short' is avoided.
Note: depending on how 'faulty' is your insulation (it varies from one phone to another depending on production line assembly) lower the volume until the issue stops accruing.
not full-proof but working
What worked for me is turn power saving on
possible fix
might be a coincidence, but this worked for me:
(I am a new user so i cant post a link but here is what you should do)
1. enter YOUTUBE
2. find this video: "Samsung Galaxy S6 Touch Screen Sensitivity Fix"
worked like magic for me
Repair tech
It is true that if your in the US and your phone has no damage or any water damage to void your warranty even if you bought it from someone else, u can register the phone at samsung website and then request a repair. It will still have a warranty.
But as I am a Cellphone tech, sometimes I rebuild phones. A s6 came into my shop and i once rebuilt it and worked for a while before doing the phantom touches on task and back keys. So when i pulled the screen up a little off the touch keys, it would stop. I gave up after a while trying to figure it out as i had more things to work on. Back in December i decided to rebuild it again, new screen, new battery, new frame and new back. Turned it into a gold s6 to try and sell it again. Sold it couple days ago, and it came back the next day doing the same thing. So got bored tonight and started to take it back apart. Figured i would try one more thing, replaced the charging port (which is also the soft touch keys) to see if that would resolve it. So far its not wigging out but im letting it sit here and try using it from time to time, with wifi on and a simcard installed. So far its not going crazy, but I will let everyone know if it fixes it or not. As for the "Youtube thing" I tried that, did not resolve. Im guessing its a defective soft touch keys/charging port.
I would not recommend this repair unless your phone is out or voided of warranty.
dslayer83 said:
It is true that if your in the US and your phone has no damage or any water damage to void your warranty even if you bought it from someone else, u can register the phone at samsung website and then request a repair. It will still have a warranty.
But as I am a Cellphone tech, sometimes I rebuild phones. A s6 came into my shop and i once rebuilt it and worked for a while before doing the phantom touches on task and back keys. So when i pulled the screen up a little off the touch keys, it would stop. I gave up after a while trying to figure it out as i had more things to work on. Back in December i decided to rebuild it again, new screen, new battery, new frame and new back. Turned it into a gold s6 to try and sell it again. Sold it couple days ago, and it came back the next day doing the same thing. So got bored tonight and started to take it back apart. Figured i would try one more thing, replaced the charging port (which is also the soft touch keys) to see if that would resolve it. So far its not wigging out but im letting it sit here and try using it from time to time, with wifi on and a simcard installed. So far its not going crazy, but I will let everyone know if it fixes it or not. As for the "Youtube thing" I tried that, did not resolve. Im guessing its a defective soft touch keys/charging port.
I would not recommend this repair unless your phone is out or voided of warranty.
Click to expand...
Click to collapse
Hi dslayer83,
I've the same problem with my S6
Could you solved the problem replacing the charging port?
It would be very important to me knowing how to repair the phone because I buyed it abroad. In my country Samsung does not cover warranty.
Up with this thread!
I had an S6 since January.. initially the problem was very random, maybe 1 or 2 times per day, sometimes would go crazy for a while
Then i had some time with no defect at all (a couple of weeks?) without doing nothing
This past week, the phone was feeling like the MENU button (what menu as in this phone there isn't any?) and that was very weird!
Today, it simply went completely crazy, and now is completely unusable... i can't actually swtich it off as the back key is pressed so quickly i don't have the chance of doing nothing!
EDIT: Managed to reboot and wipe cache... now it is useable, but still hits the button from time to time
Update... went unuseable again today.... factory resetting now...
If it works, shall we suspect is something software related?
Update: Not working... it started giving the phantom touches just after the factory reset then suddenly stopped
Worked fine for few hours, then started craza again
Now i have done a wipe and factory reset again, and still unuseable
Hello guys,
I got a problem on my Google Pixel out of nowhere. I turned it off a few days ago and when trying to turn it on again a few hours later it did not work.
Nothing happened whether it was plugged it or not so I thought the battery was faulty.
I ordered a new one and changed the battery. Now the phone turns on but the screen remains black (I can tell it's turning on because it vibrates).
The screen is black but is still responsive, I can still (with difficulty since I don't see anything) enter my pin code and then answer calls, receive messages and so on.
It is also worth mentionning that it seems to work the same with the old battery which I thought was faulty (I am 100% sure it wasn't vibrating before I changed it the fist time because I tried for two days before ordering the new battery).
Do you think replacing the screen would be enough or could it be another issue ?
Thanks for your help.
Kargrim said:
Hello guys,
I got a problem on my Google Pixel out of nowhere. I turned it off a few days ago and when trying to turn it on again a few hours later it did not work.
Nothing happened whether it was plugged it or not so I thought the battery was faulty.
I ordered a new one and changed the battery. Now the phone turns on but the screen remains black (I can tell it's turning on because it vibrates).
The screen is black but is still responsive, I can still (with difficulty since I don't see anything) enter my pin code and then answer calls, receive messages and so on.
It is also worth mentionning that it seems to work the same with the old battery which I thought was faulty (I am 100% sure it wasn't vibrating before I changed it the fist time because I tried for two days before ordering the new battery).
Do you think replacing the screen would be enough or could it be another issue ?
Thanks for your help.
Click to expand...
Click to collapse
Have you dropped the phone? not like the ribbon cable connecting the screen to the motherboard could be loose and needs to be reattached again? just a guess though..
Arju said:
Have you dropped the phone? not like the ribbon cable connecting the screen to the motherboard could be loose and needs to be reattached again? just a guess though..
Click to expand...
Click to collapse
Hello Arju,
No I didn't drop it.
Since I had to take off the screen to change the battery I had to unplug the ribbon cable. When putting everything back together I tried many times to unplug/replug it without success so far. (I did not glue it back yet to the case so far so I still have access).
Moreover, since the touch screen is working I am guessing it has to be attached correctly.
Thanks for your idea anyways.