This is an amazing device. However, I figured out why the soft keys at the bottom are breaking! (By breaking I mean when you touch them, the light goes off and goes into a key lock disabling the menu key and the back key)
This phone most likely has a heat sink sitting on the bottom left corner of the device. When this phone is in a high temperature state (either lots of constant usage or a hot room) the heat sink begins to overheat causing the heat sensitive soft keys to think it's being held down.
Edit: (That or the GPU is sitting in the bottom left corner because i noticed when I run an emulator, it freezes the buttons really quickly. Especially if you get a text message in the middle of it)
therefore this is a HARDWARE error. Samsung, please fix this. Don't let this amazing device go down the ****ter. Either add a stronger heat sink, or like most laptops now-a-day, install a vent for the air to leave the phone.
Temporary fix?
Shut phone off for like 5 minutes, and place it in a cooler area.
Specs:
Stock Samsung Galaxy Firmware. Straight from the bell store. (I had to do a few wipes to exclude outside variables)
Phones these days are going to need a fan built in because they're getting too powerful.
I haven't made a forum search because I didn't want to get lazy and post this if I didn't find one.
TLDR: Hardware issue causing overheating.
I don't think the keys use heat. (Maybe it's a bug with the Bell variant). It's a capacitive touchscreen, so most likely uses electric current. How do you know the keys are heat sensitive?
it only stops working when its warm.
i use my phone constantly and i have never had this issue. actually, i have had two, as i returned the first one after two weeks for one that has the 3 button recovery enabled. not only have i never had this issue, but i have never come across any mention of it in any of the forums i frequent.
When I bought my phone, I was able to use both vol up+ home + Power, and the vol down + home + power, so I don't think I have the non recovery model.
I don't think mine has this problem or i haven't suffered from it yet anyway. Today the phone got really really hot, i was in an online multiplayer game whilst it was charging. I was aware the phone was becoming quite hot but i needed to carry on gaming lol anyway, for the first time i got a system message stating that 'battery charging had been paused due to excessive heat' so this shows the phone was hot. Well this finally got me off my game and i used the back key to exit without any troubles at all. You don't mention getting this error so does that mean mine was at a higher temperature?
I agree with andrewluecke about the keys being responsive to 'electric' and wonder if maybe you had sweaty/moist fingers whilst trying your keys, it does mention in the manual about irrational behaviour due to moisture.
I have a Bell phone and never once had this issue. I would take your phone back.
opensourcefan said:
I have a Bell phone and never once had this issue. I would take your phone back.
Click to expand...
Click to collapse
make that two
the OP definitely have a defective unit
maybe some one dropped it when it was being demo-ed or something like that
else it doesn't make sense why those buttons would be at those horrible conditions
AllGamer said:
make that two
the OP definitely have a defective unit
maybe some one dropped it when it was being demo-ed or something like that
else it doesn't make sense why those buttons would be at those horrible conditions
Click to expand...
Click to collapse
Well, I agree. I have the unlocked I9000 phone, and have never experienced this issue...
You probably have an intermittent fault caused by dodgy joints within the phone.
Get it repaired..
Nothing that could warm up is at the bottom http://www.careace.net/wp-content/uploads/2010/06/galaxy-s-disassembly-10.jpg (right)
Only the vibrator and the microphone
exactly, the stuff that warms up are the GPS and Wifi and those are at the top where the USB plug is
Yeah it's probably to do with a dodgy contact rather than heat, plus the touch buttons at the bottom are just an extension of the screen and so are capacitive, not heat activated.
Logicalstep
+1 for "never had issue"
You see that your buttons lock up when it gets warm and you automatically assume it getting warm locks up the buttons?
Ever thought that something in your phone was overloading and causing it to heat up at the same time causing the hardware keys to lock up?
sturmeh said:
You see that your buttons lock up when it gets warm and you automatically assume it getting warm locks up the buttons?
Ever thought that something in your phone was overloading and causing it to heat up at the same time causing the hardware keys to lock up?
Click to expand...
Click to collapse
And thats the increasing problem with XDA (and the internet in general).. It's becoming easier and easier for people to make ridiculous assumptions without proper proof. It's one reason why we should always question everything we see, if there isn't a reliable source, or proper testing.
Related
I have read many threads and forums about the problem of the Hermes becoming white. The soft reset in this case does not help.
I found the explanation in my case and I am not able to fix it quickly, without opening the device to screw the connector.
The problem is only due to the temperature of the device. When the temp is to hot, the screen is white, in my case, it typically happens when it stays in my pocket et I moving too much throug the office ;-)
Solution, simply open the keyboard and gently blow in the thin area between the two parts of the device.. in my case, the screen comes back in 2-3 seconds.
Enjoy !
Eric
Hermes/Schaps 4.31/Orange CH
To be honest, I have this problem on my 838 (wizard) previously.
I have found someone (engineer who I need to pay) help me to check.
It is actually the connection cable between the keyboard and screen start breaking.
This makes the connection poor.
End up, my wizard cannot be repaired and I have borrow my freinds hermes to use in the mean time.
I suggest you pay special attention to it.
I suppecm that you blow it is actually helping the connection of that cable.
huh
are you guys serious in what you're talking about?
blow in between the two parts of the device when it's hot to get the connection of the cable back?
are you sure you are talking about a mobile phone and not about a compressor?
thanks for your feedback. I am convince that in my case, the gentle blow does not move the connecting cable.
Additionaly, the tipical symptom reported in various thread is that the soft reset does not help, while letting it apart for 15 minutes does help. It can confirm that the simple temperature idea is fine.
Again, it works for me, it can help others, and sorry for the others that won't find a solution with mine!
actually, i am neutal to this topic.
But just want to share my experience.
In my case, my cable is aging. Initially, it can help with slide the keyboard open and close.
End up the engineer told me that cannot be repaired deal to no parts. he examined it using a microsope watching the cable.
no need to take it too series.
It is a cable connection issue, it is caused by either dropping or opening and closing the device numerous times. It can be fixed the part cost around $20 kinda hard to find but can be found if you search enought. I can repair the device if your interested either pm me or you can contact me at
[email protected]
nate
when this happened to my hermes last August i found slightly unscrewing the two screws on the back of the screen fixed it & not had a problem since
didnt know what the white screen was 'till i got it right after the external volume crapped out, so tired of tinkering with hermes, going Kaiser
As a science experiment I have bought a number of hermes on ebay- it is a cable connection issue or worn cable in the 4 I have played with - all fixed by cleaning and reinstalling cable/connection or replacing the cable assembly. I cant say this is the only bug but 4 outy of 4 inducates a trend to me
John
Oh my gosh, topic starter, that is the same exact issue that I frequently have with my 8525. I eventually found out that if I leave it in direct sunlight, put it in my pocket for too long, or in anyway expose it to relative heat, then it would turn white.
That's a nice "fix" you have there hahah. As for me, I just let it cool down by placing it in a cool and shaded place, works like a charm after a few minutes.
Anyone with a WHITE screen MUST READ this!!!
To bring credit to what I say below, I haved had tinkering experience with electronics for the past 10 years, not to mention that I am currently a 3rd year electronics engineering student.
I currently have 4 hermes units.
When I first had the white screen prolem on my first hermes about a year ago (may be 8-10 months?) my research on the net revealed that the problem is apparently the connector on the button pad board (part number 50H000380-30M-A). After serious tinkering and tweaking I finally got the (extremely sensitive) connector connected up so that the white screen issue actually dissapeared. However, since the connection was so delicate and so sensitive, I had to fix it in place with a hot glue. Hot glue actually added some thickness to it; given that there isn't much tolerance between the top of the connector and the cover, I needed to scrape away some plastic without putting a hole in it so it can accommodate the extra thickness, this is also required for the sliding function to be smooth.
However, right now I have 4 hermes, and I am faced with the same issue. On two units I have the white screen problem. After some intuitive testing I have found that the problem is not with the flex cable, nor with the connector on the flex cable, nor the connector on the button pad board. The problem is with the actual button pad board itself, as it contains fair bit of circuitry on board.
This is how I came to the conclusion. Since the white screen can be fixed with sensitive alignment of the connecor on the board, I wondered if it will display anything with that D-pad (button pad board) disconnected. On trial, it didn't display anything on both a functional unit and a unit with a white screen issue. From this I made the assumtion that the LCD initialisation sequence is contained on the button pad board (part number 50H000380-30M-A).
Having made this assumption, I thought since the symptoms of having it disconnected on a functional unit is the same with a unit that has the white screen symptom, I wondered if it will fix the white screen problem if I changed over the button pad board. On trial, I found that the white screen problem was a thing of the past. So, I don't know what on the button pad board actually causes the white screen, but it is DEFINITELY the board it self and not the connector.
PS: I don't know the proper names of the components but by the button pad board I am talking about is the board that lies under the front buttons of the unit that has the call, end call, start, ok...etc buttons.
uengin, u totally had make ur homework regarding the white-screen-issue.
Anyway, for me, I face the exact problem too. And my way is much simpler. When ever I face the white-screen problem (this cause by the high temperature, coz I notice it only happen when I put my 838 on my pocket while walking during sunny day), I simply turn off the screen for a while (by lightly pressing the power button), like 3-5 second, then turn on the screen back. And, voila~ it back to normal.
i get a white screen when i press on the plastic casing on the lower right side of the screen, above the right bar button. no temperature involved here. sending the hermes to sleep and waking it up restores the normal screen.
pcpc said:
i get a white screen when i press on the plastic casing on the lower right side of the screen, above the right bar button. no temperature involved here. sending the hermes to sleep and waking it up restores the normal screen.
Click to expand...
Click to collapse
There's actually a BGA chip in that vicinity on the button pad circuit board. It may or may not be that chip thats causing the issues, but I find it higly likely it is...
uengin said:
There's actually a BGA chip in that vicinity on the button pad circuit board. It may or may not be that chip thats causing the issues, but I find it higly likely it is...
Click to expand...
Click to collapse
if it is the chip, then this would be a loose soldering point?
would you recommend to handle the hermes with great care? eg. not putting it in my trouser pocket because oft the pressure?
pcpc said:
if it is the chip, then this would be a loose soldering point?
would you recommend to handle the hermes with great care? eg. not putting it in my trouser pocket because oft the pressure?
Click to expand...
Click to collapse
I doubt its a "loose" solder joint. It could be a dry joint. But then again you never know. However, the symptoms with the heating and cooling mentioned in the thread it could be one of the several devices on the button pad board failing due to heat.
As a general rule of thumb, definitely electronic devices of this calibre should be dealt with a level of care indeed.
nohanz said:
uengin, u totally had make ur homework regarding the white-screen-issue.
Anyway, for me, I face the exact problem too. And my way is much simpler. When ever I face the white-screen problem (this cause by the high temperature, coz I notice it only happen when I put my 838 on my pocket while walking during sunny day), I simply turn off the screen for a while (by lightly pressing the power button), like 3-5 second, then turn on the screen back. And, voila~ it back to normal.
Click to expand...
Click to collapse
Same for me which seems software issue but how to solve it
I'm having white screen problem too. I highly doubt it has anything to do with a cable because:
1) I almost never use keyboard, aka don't slide open the phone
2) lately white screen often happens when I touch a screen.
3) several times white screen got fixed by holding the phone next to aircondition outlet.
4) white screen recently started at the same time I've noticed that the battery started dying, it doesn't last as long as before. Before this battery I had another one, similar, and also never had white screen while that battery was new.
To conclude all this, at least in my case is more likely it's a battery issue and/or overheat. Tomorrow I'll use the original battery (I've replaced it with 3k mAh 2 years ago) this should proof me right or wrong.
My white screen issues started after a waist-high drop onto concrete, accompanied by the D-Pad and the surrounding buttons not working. In order to get the white screen to go away and the buttons to work again, I have a simple 2-step process:
Put the Hermes to sleep
Press hard right above the D-Pad/below the screen
When I wake the device up, it works just fine!
Interesting Find......
I just noticed something about my white screens.
IF the poweron led does NOT turn on then I get white screen when turning on my hermes.
If the poweron led turns ON(lights up) when turning my phone on then it won't white screen on me.
Sometimes, I'll place the handset down on a table or whatever, and completely of it's own accord, the screen will scroll right to the second page. Then a couple seconds later, it'll scroll right again to the third, and fourth. I'll pick it up and swipe back to the home screen and put it back down, and it'll do the same thing again. Basically.... wtf?
Sometimes it does it in menus aswell, scrolling down lists one by one every few seconds when the thing isn't even in my hands.
Has anyone else experienced this? I've had a couple of replacement handsets and it's done it on all of them!
Switchbitch said:
Sometimes, I'll place the handset down on a table or whatever, and completely of it's own accord, the screen will scroll left to the second page. Then a couple seconds later, it'll scroll left again to the third, and fourth. I'll pick it up and swipe back to the home screen and put it back down, and it'll do the same thing again. Basically.... wtf?
Sometimes it does it in menus aswell, scrolling down lists one by one every few seconds when the thing isn't even in my hands.
Has anyone else experienced this? I've had a couple of replacement handsets and it's done it on all of them!
Click to expand...
Click to collapse
It has happened to mine, intermittently. I was hoping that it was just a little piece of grit under the trackball and that it would stop, but now you've got me worried that it is a common fault. Mine is an unlocked white in the UK, bought from Devicewire and delivered around 10 days ago...
Yup, I can comfirm it has happened to me with 3 white sim free Heros. It can happen when the device is completely undisturbed so i'm assuming it's some weird software glitch.
I can't even identify what causes it, to recreate the conditions. Seems totally random.
Switchbitch said:
Yup, I can comfirm it has happened to me with 3 white sim free Heros. It can happen when the device is completely undisturbed so i'm assuming it's some weird software glitch.
I can't even identify what causes it, to recreate the conditions. Seems totally random.
Click to expand...
Click to collapse
Hopefully a (rapid) firmware upgrade will sort it...
Could it be something on the touch screen?
I think I have seen this too! Do we all have screen protectors on? I do on my Hero....
It seems to me like the people widget caused me some issues. I have removed it and the device is faster and this bug hasn't appeared for me at all since.
The Jones said:
I think I have seen this too! Do we all have screen protectors on? I do on my Hero....
It seems to me like the people widget caused me some issues. I have removed it and the device is faster and this bug hasn't appeared for me at all since.
Click to expand...
Click to collapse
Screen protector, yes. And the People widget (which I find very useful!)
Speaking about really weird things going on with the Hero. I can contribute with some funky stuff too:
When having my Hero near/under my mousecable the mousepointer (on the monitor) gets its own life. It starts moving randomly and begins to scroll the pages up and down in my browser WITHOUT me touching anything. I do have a cable connected mouse (USB). The phone has wifi, GPS and Network activated. I have not yet tested what happens with those turned off though.
Haha this is getting interesting. I noticed some mousepointer jitter when I was using the PC at work today, with my Hero nearby. I'll investigate more today.
Mine doesn't have a screen protector, but I do use the people widget on my second page. I'll remove it and see if it makes a difference to the spontaneous scrolling.
I just got my white unlocked hero 3 days ago and I just noticed this problem for the first time. The home screen would move over 1 or 2 screens without me even doing anything. Im wondering if it was major lag from previous movements I made. Im sure this is a software bug, does anyone know if HTC releases software updates for their android devices? I just switched from an iphone and hope they would release updates and fixes like apple did when something was wrong with a software release.
This phone is what... a week since launch day? We are early adopters and will find bugs. There'll be an update soon I'm pretty sure.
I think there is some interference with Wifi/Other radio and the Hero screen.
When i put mine on my desk next to my PC i cannot press all buttons on the touch screen but the wheel and hardware keys still work. When i move it 1m away from my PC this behavior is gone.
This problem happened to me when I had wet hands. All I did was wipe the hero dry and it worked fine again.
Thiesen said:
Speaking about really weird things going on with the Hero. I can contribute with some funky stuff too:
When having my Hero near/under my mousecable the mousepointer (on the monitor) gets its own life. It starts moving randomly and begins to scroll the pages up and down in my browser WITHOUT me touching anything. I do have a cable connected mouse (USB). The phone has wifi, GPS and Network activated. I have not yet tested what happens with those turned off though.
Click to expand...
Click to collapse
This is due to the phones aggressively high SAR value (it's really really high). I would think twice before putting this phone in your pant pockets if you ever want to have chidren
Ovek said:
This is due to the phones aggressively high SAR value (it's really really high). I would think twice before putting this phone in your pant pockets if you ever want to have chidren
Click to expand...
Click to collapse
Wow, really? I already have 2 so going to keep this in my pocket from now on!!!
Aaaaaaaand HTC didn't bother fixing this in the new rom. The T9 keyboard input bug and huge lag are also unchanged.
I can confirm that this odd bug still lurks around in the official 2.73.405.5 build.
It has been suggested that it migh be due to dirt inside the trackbal housing but then why would the homescreen suddenly scroll on its own without being touched? Maybe a sensor glitch? I don't know what solution HTC are using to read the movements of the trackball though... one thing is for sure; it's not a good one....
I'm 100% sure now it's not a hardware issue. It's happened on multiple Heros I've used, not long out the box either. The only thing I've noticed that indicates any kind of pattern to the apparent randomness is that it gets a lot worse when there's a lot of mobile data transfer going on. One time I physically couldn't get it to stay on the homescreen long enough to click an icon.
Just pitching in, exact same problem here. Very strange that everyone gets it to the right :/
Just notice on mine too, some automovement in menu and home
Upgraded yesterday to new firmware (modaco)
Could be an increase of trackball sensibili? I see a settings to tweak it on blackberry device...on android?
Anyone else having a weird, intermittent issue with the touch screen seemingly not working right
IE: I try to scroll and instead it makes a tap where my finger lands. Unlocking the screen doesn't work 50% of the time because the lockscreen will just lag out and I have to sleep/re-wake the device
This happens on stock and after i rooted to tiamats rom
XFreeRollerX said:
Anyone else having a weird, intermittent issue with the touch screen seemingly not working right
IE: I try to scroll and instead it makes a tap where my finger lands. Unlocking the screen doesn't work 50% of the time because the lockscreen will just lag out and I have to sleep/re-wake the device
This happens on stock and after i rooted to tiamats rom
Click to expand...
Click to collapse
I haven't experienced or heard of this before, at least as you're explaining it.
Is this accompanied by screen dimming? Did this start after the update to HC3.2?
okantomi said:
I haven't experienced or heard of this before, at least as you're explaining it.
Is this accompanied by screen dimming? Did this start after the update to HC3.2?
Click to expand...
Click to collapse
I use auto brightness, but I do not notice it changing during this happening
I got my XOOM with 3.2 on it
Your device may not be grounded. It's a common problem with touch screen devices. Does this happen when you're holding the device in your hands?
zehkaiser said:
Your device may not be grounded. It's a common problem with touch screen devices. Does this happen when you're holding the device in your hands?
Click to expand...
Click to collapse
I really don't know, let me do some testing and see what circumstances it is replicated under.
How would grounding be determined? Its not charging...
I do have it in a silicon/rubber case. Would that be a problem?
Just for the sake of satisfying my curiosity - if you are experiencing this issue while your Xoom is docked - try placing your fingers on the back of your Xoom and typing with your thumbs.
I am trying to resolve a similar issue that I only encounter while my Xoom is docked at one place in the world - my work. Nowhere else does it do this.
I have installed a power conditioner, with no effect. It happens whenever the power is plugged into the dock. If I use an external power supply it goes away (batteries). I did switch off the florescent lighting and it is better, so it may be EM related. especially since it is a *capacitive* screen.
I have also read of people with other capacitive touch screen devices have the same issue when it is not held in their hands.
Let me know either way.
Thanks,
Frans
XFreeRollerX said:
Anyone else having a weird, intermittent issue with the touch screen seemingly not working right
IE: I try to scroll and instead it makes a tap where my finger lands. Unlocking the screen doesn't work 50% of the time because the lockscreen will just lag out and I have to sleep/re-wake the device
This happens on stock and after i rooted to tiamats rom
Click to expand...
Click to collapse
I have seen issue on gtab where some roms/kernel where having issue with screen calibration, there was a calibration files that could be created in the root with the name calibration.ini and upon reboot it was fixed, I do not know if this is valid for a xoom tho...
with a few rom I had NO issue whatsoever and never reused the calibration...
fransdw said:
Just for the sake of satisfying my curiosity - if you are experiencing this issue while your Xoom is docked - try placing your fingers on the back of your Xoom and typing with your thumbs.
I am trying to resolve a similar issue that I only encounter while my Xoom is docked at one place in the world - my work. Nowhere else does it do this.
I have installed a power conditioner, with no effect. It happens whenever the power is plugged into the dock. If I use an external power supply it goes away (batteries). I did switch off the florescent lighting and it is better, so it may be EM related. especially since it is a *capacitive* screen.
I have also read of people with other capacitive touch screen devices have the same issue when it is not held in their hands.
Let me know either way.
Thanks,
Frans
Click to expand...
Click to collapse
Well you bring an interesting point. The device was in my hands but I was not actually touching it... It had a rubber sleeve on it.
I since got the Motorola hard case which has some areas exposed and I also disabled the lock screen, and I have not been able to replicate the problem at all.
The device was docked at one point, charging, and the problem showed up aagin (recalling from memory). The fix was to power off the screen and re-wake the device. This did involve touching it, so...maybe its an electrical thing?
P00r said:
I have seen issue on gtab where some roms/kernel where having issue with screen calibration, there was a calibration files that could be created in the root with the name calibration.ini and upon reboot it was fixed, I do not know if this is valid for a xoom tho...
with a few rom I had NO issue whatsoever and never reused the calibration...
Click to expand...
Click to collapse
I had this problem with the stock 3.2 ROM. I haven't done any calibration, and don't think I need to: it works perfectly majority of the time.
I'll reenable the lockscreen and try to replicate it again.
Okay I think I'm onto the problem
I opened the case just now, still lock screen disabled, pressed just the power button and the touchscreen was acting up again.. couldn't slide to scroll, but could tap/point only
I then put my thumb on the side, as if naturally holding it without a case, and it started working normally again without any kind of power cycle.
Thoughts?
Have you dropped or jarred your Xoom a lot? Look for threads I started in this forum, I have one that explains this issue and includes a fix. My Xoom is still working flawlessly. I'd link it but pre-calculus is about to start.
Elysian893 said:
Have you dropped or jarred your Xoom a lot? Look for threads I started in this forum, I have one that explains this issue and includes a fix. My Xoom is still working flawlessly. I'd link it but pre-calculus is about to start.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1068499
I bought the XOOM second hand from someone who claimed they hardly used it. Right now sitting infront of me, the bottom right, on the back edge, there is a small pressured crease as if it was dropped (looks like the corner of my phone when i dropped it on tile).
I personally have not dropepd it, but I throw this thing onto my bed all the time, it fell out of the dock onto my hard desk once, so yeah its been knocked around.
Will doing that mod void the warranty?
I found no warranty stickers or screws when I disassembled it. The back cover is made to slide down so that Moto can do the 4G upgrade, so I doubt they want to be fooling with that type of thing anyways. I can't say for certain that sticking a piece of foam in the back of your Xoom won't void the warranty, but I can say that it fixes the issue(which also could be covered by warranty if you can get someone to believe you've got the issue, I however could not, so I had to take it upon myself).
Alright
I just ran into the problem again playing a game.. seemed like the right half of my screen just stopped working intermittently. Kept playing and it returned to normal.
I may pop it open and try the foam thing. I'm pretty good with disassembling laptops.. I can't see this being much harder.
I just picked up a new (yep...new) HD2 for my daughter. I put Android on it for her, and it appears to be working fine...but I know back when I had mine, Android might have some intermittent issues...are most of the issues worked out now, or is there anything that I should tell her to lookout for? In other words, is she likely to have any problems with Android on the HD2?
Most probably not, most ROM-s are quite stable, but then again, it depends which android ROM did you install.
The only thing I would (if I bought a new HD2) try is not using the End call/Power button key too much, or better not at all (use a quite simple app called "Button Savior", you'll find it on the market, it's free and one of the musts for a HD2 running android).
Why?
Because there are numerous numbers of HD2 owners including myself that had the non-responsive touchscreen issue, which is caused by the End call/Power button key, which is actually squeezing the flat cable of the actual Digitizer/touchscreen.
It's a design flaw, so better be careful with that button.
Some people also experience random reboots. What worked for me was going into settings and selecting gsm only. Sometimes what happens
with some phones is when the HD2 goes from cdma to gsm the phone may reboot. It wouldn't do it everytime but this is something worth noting
anyway. If she doesn't say she's having that issue though there wouldn't be a point in changing the settings. Everything else seems to be ok now.
Also not sure if you have ever heard about bent battery pins but thats something you may want to inform your daughter about.
Zmooth is way better than button saviour.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Thanks for the info. Gonna try it!
Sent from my HTC HD2 using xda app-developers app
Erroneous91 said:
Most probably not, most ROM-s are quite stable, but then again, it depends which android ROM did you install.
The only thing I would (if I bought a new HD2) try is not using the End call/Power button key too much, or better not at all (use a quite simple app called "Button Savior", you'll find it on the market, it's free and one of the musts for a HD2 running android).
Why?
Because there are numerous numbers of HD2 owners including myself that had the non-responsive touchscreen issue, which is caused by the End call/Power button key, which is actually squeezing the flat cable of the actual Digitizer/touchscreen.
It's a design flaw, so better be careful with that button.
Click to expand...
Click to collapse
that's not strictly true.
What happens is that the layers that make up the phone from the glass, digitizer, lcd panel the CB and even the casing its self separate. what happens is mostly around the layers holding the panel together, the glue will separate, that can be down to frequent miss use but also the climate can affect it. it may feel like the button is failing because it becomes harder to push but that's because the layers have come part, this can also affect the digitizer , firstly because the layers have separated but also because as you pointed out the digitiser cable is right underneath that button, it can be damaged or more likely it falls out.
unfortunately it can happen to any device, a simple trick I started using when I noticed that the power button wasn't as protruding as normal is to squeeze the bottom corner of the device several times a day, I don't mean the button, I mean around it, some times you can feel is move back together, after the power button starts playing up its usually not long before the digitiser will do the same, may that be the cable or the panel its self.
So yes, be careful with the button, in that you don't need to push it hard, but also avoid sudden changes in temp, hot damp conditions, anything that can affect glue!
oh another one to watch Is the volume control, its a simple contact switch but is controlled by a single piece of plastic which is sprung only by the tension in the plastic its self. Basically don't push it too hard, if you find its not working or hard to work then you have either broken the plastic rocker or its popped out of its housing,
My phone last week wasn't receiving texts so I restarted it and when it came back on the touchscreen no longer worked. The little white light would go on when I touched it so it knew where my finger was but any movement would not unlock the phone so I couldn't actually do anything with it. Sure enough a factory reset fixed the problem but I am still waiting for them to get me a new one in case the problem happens again to me. Anyone else have this happen to them or just a freak occurrence for me?
My son has gotten a hold of my s4 twice now since I have owned it. Both times I couldn't get the phone unlocked even though the touch screen was recognizing my touch. Restarting fixed it both times for me. Not sure if this is the same problem you are talking about, just thought I would share.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Happened to me a few times. Both screen swipes and the capacitive button presses werent registering. Happened on lock screen, call logs (swiping to call wasnt working), and swipe to answer. Pressing the home button and going back to the app fixed it. Very random but annoying nonetheless especially when not able to answer a call
Seems like buggy software to me. I've had a different issue, my phone says I have data, but I don't, I've had to restart the phone to properly pick up a data signal. This has happened twice now. Seems to be like Samsung's touchwhiz is quite buggy...
Yeah restarting it did nothing for me, tried many times, took the battery out put it back in all that stuff. The same thing happened with my data, I had a connection that entire time that I was not receiving texts but none of them actually went through which is when the problem began.
sam2c said:
Happened to me a few times. Both screen swipes and the capacitive button presses werent registering. Happened on lock screen, call logs (swiping to call wasnt working), and swipe to answer. Pressing the home button and going back to the app fixed it. Very random but annoying nonetheless especially when not able to answer a call
Click to expand...
Click to collapse
What app were you able to get in to to fix it? Would like to know in case the problem happens again when they get me a new one.
This happened to me last night, about had a major freak out.
First I have a couple questions for all of you who had this issue, so maybe we can pinpoint the actual cause:
1. Did you get any type of moisture (even just a little condensation) anywhere on or around the phone? Mine started acting up after I accidentally put my phone on the coffee table where some condensation had formed from a drink being there previously.
2. Any of you drop your phone at all? Even just a minor drop...as the day before I had a little drop (maybe from a foot off the ground), but I do have a case.
The reason I ask is because I started having this issue immediately after the phone was put on the condensation. Don't know if that was the cause, though, because I'm not sure exactly which of the steps below actually fixed it.
First I had to identify the exact problem...which I found by turning on "show touches" in Developer Options within the settings menu. This brings up a little white dot on the screen any time it registers a touch. Sure enough, I was getting "ghost touches" on the top left corner of my screen every 30 seconds or so - and it would generally last for 10-30 seconds or until I turned my screen on and off (that would fix it temporarily). The ghost touch was causing my drop down menu to pull down slightly every once in awhile, as well as not registering any of my other touches (including capacitive buttons). I knew the screen itself wasn't broken, because any addition touches were registering via the white dot - they just weren't interacting with the UI.
After doing some research online, apparently there are a couple main reasons that this ghost touching could occur:.
1. Faulty digitizer. Obviously this would Suck, and I really hoped it wasn't the cause. To repair would mean replacing the entire screen, as apparently the digitizer is attached to the screen and would be very difficult to replace by itself.
2. Any kind of moisture, whether water, skin oil, etc, getting in the cracks of the phone and staying under the screen, causing the pressure to indicate a false touch. Possible repair options included putting the phone near a WARM (but not too hot) surface for a period of time to hopefully cause the moisture to evaporate. Also some people said it just evaporated on its own after a few days (again, I hoped I wouldn't have to resort to this as I'm impatient and don't want to be without my phone for that long lol).
3. Software issue. Possible fix includes toggling HW overlays and/or GPU rendering.
Here's what I did:
Took the phone apart completely, made sure there was no visible moisture anywhere (there wasn't). Intermittently blew the phone (from the back and front, while it was disassembled) with warm air from a blow dryer. Left it alone, disassembled, for about 30 minutes.
Put the phone back together, booted up, immediately went to developer Options and (a) disabled HW overlays and (b) DISABLED "Force GPU rendering" (I actually already had it enabled).
BOOM - problem was gone!
So like I said, I'm not sure which of those did the trick - or which problem I had to begin with - but I'd be interested to know if anyone else had similar issues and/or fixes?
sam2c said:
Happened to me a few times. Both screen swipes and the capacitive button presses werent registering. Happened on lock screen, call logs (swiping to call wasnt working), and swipe to answer. Pressing the home button and going back to the app fixed it. Very random but annoying nonetheless especially when not able to answer a call
Click to expand...
Click to collapse
CPA Poke said:
This happened to me last night, about had a major freak out.
First I have a couple questions for all of you who had this issue, so maybe we can pinpoint the actual cause:
1. Did you get any type of moisture (even just a little condensation) anywhere on or around the phone? Mine started acting up after I accidentally put my phone on the coffee table where some condensation had formed from a drink being there previously.
2. Any of you drop your phone at all? Even just a minor drop...as the day before I had a little drop (maybe from a foot off the ground), but I do have a case.
The reason I ask is because I started having this issue immediately after the phone was put on the condensation. Don't know if that was the cause, though, because I'm not sure exactly which of the steps below actually fixed it.
First I had to identify the exact problem...which I found by turning on "show touches" in Developer Options within the settings menu. This brings up a little white dot on the screen any time it registers a touch. Sure enough, I was getting "ghost touches" on the top left corner of my screen every 30 seconds or so - and it would generally last for 10-30 seconds or until I turned my screen on and off (that would fix it temporarily). The ghost touch was causing my drop down menu to pull down slightly every once in awhile, as well as not registering any of my other touches (including capacitive buttons). I knew the screen itself wasn't broken, because any addition touches were registering via the white dot - they just weren't interacting with the UI.
After doing some research online, apparently there are a couple main reasons that this ghost touching could occur:.
1. Faulty digitizer. Obviously this would Suck, and I really hoped it wasn't the cause. To repair would mean replacing the entire screen, as apparently the digitizer is attached to the screen and would be very difficult to replace by itself.
2. Any kind of moisture, whether water, skin oil, etc, getting in the cracks of the phone and staying under the screen, causing the pressure to indicate a false touch. Possible repair options included putting the phone near a WARM (but not too hot) surface for a period of time to hopefully cause the moisture to evaporate. Also some people said it just evaporated on its own after a few days (again, I hoped I wouldn't have to resort to this as I'm impatient and don't want to be without my phone for that long lol).
3. Software issue. Possible fix includes toggling HW overlays and/or GPU rendering.
Here's what I did:
Took the phone apart completely, made sure there was no visible moisture anywhere (there wasn't). Intermittently blew the phone (from the back and front, while it was disassembled) with warm air from a blow dryer. Left it alone, disassembled, for about 30 minutes.
Put the phone back together, booted up, immediately went to developer Options and (a) disabled HW overlays and (b) DISABLED "Force GPU rendering" (I actually already had it enabled).
BOOM - problem was gone!
So like I said, I'm not sure which of those did the trick - or which problem I had to begin with - but I'd be interested to know if anyone else had similar issues and/or fixes?
Click to expand...
Click to collapse
I should not have had any condensation at all on my screen when it began. I was using the phone playing with WatchOn and setting it up for my TV, I was messing with it for quite a while and realized after a period I hadn't received texts in a long time (I normally get at least 1 every 10 minutes, I was going on a hour and a half with 0) which I thought was weird so I restarted the phone.
When the phone came back online I did not notice the white dot pressing itself anywhere, but anytime I touched the screen it would immediately know where my finger was and follow it around, but not actually press anything. When I held the power button and the little Shutdown and Restart options came up, if I sat there and just pressed either one of them constantly they would eventually recognize that I pressed something and do that action.
I was also able to get into the homescreen by getting the talk option to come up and backing out of it (The buttons on the bottom of the screen all worked fine) but once in the homescreen I couldn't actually press any buttons regularly so gave up on it.
The guy at the ATT store said he hadn't seen any other complaints about it so I did a factory reset while there (I had already backed up everything with Kies) and when it came back on there seemed to be no problems.
Like I said though I am waiting for a new one anyway, they are backordered at my local store (Should have got a new batch in Friday, not sure where my phone is now) so hopefully the new one I get doesn't have this problem nor the lag problem a lot of people have been getting.
bmroczka said:
Yeah restarting it did nothing for me, tried many times, took the battery out put it back in all that stuff. The same thing happened with my data, I had a connection that entire time that I was not receiving texts but none of them actually went through which is when the problem began.
What app were you able to get in to to fix it? Would like to know in case the problem happens again when they get me a new one.
Click to expand...
Click to collapse
Just the stock Phone app. My problem seemed like a software problem more than anything else.
But if you have to restart the phone in order for the digitizer to respond, thats a different story. A swap should fix your issue, since it seems so uncommon.