Related
I just picked up another 8525 after returning the first one to checkout the Blackjack. I wanted to make sure I at least tried it before my 30 day return policy kicked in. I noticed on my second 8525 the keyboard does not lock into PDA mode as secure as my first one. It seems that the top part of the phone locks better then the bottom. So when I hold it has a phone I tend to slide the keyboard open a little. Has anyone had these issues? It just seems to easy on the second one to unlock/open the keyboard.
brmcguire said:
I just picked up another 8525 after returning the first one to checkout the Blackjack. I wanted to make sure I at least tried it before my 30 day return policy kicked in. I noticed on my second 8525 the keyboard does not lock into PDA mode as secure as my first one. It seems that the top part of the phone locks better then the bottom. So when I hold it has a phone I tend to slide the keyboard open a little. Has anyone had these issues? It just seems to easy on the second one to unlock/open the keyboard.
Click to expand...
Click to collapse
I'm afraid this is a fairly common problem. The metal runners/sliders have small indents at each end (cannot see these unless device is dismantled) that create the click into place when the sliding blocks attached to the base part slide over them.
These indents are often too shallow to create a nice firm click and in extreme cases the actual runner has sprung apart where small micro welds have broken.
There are fixes for this but only for those that don't care about their warranty and want to dis-assemble the device. I have done this fix and it now requires a very firm two thumbed push to open. However I do not recommend you do this when there is the possibility of exchange/return or repair.
Mike
If you decide to do it on your own I can vouch for Mike's method. He emailed me the process and I posted it on the WIKI.
barrydavisjr said:
If you decide to do it on your own I can vouch for Mike's method. He emailed me the process and I posted it on the WIKI.
Click to expand...
Click to collapse
Sounds like its possbile then. Where in the Wiki can I find the how-to? I looked and could not find it. Thanks again for the information.
It is under the hardware overview at the bottom. andMike i added some props to you for the method!
Mike, you must of really nailed this process. I guess I have to try it now.
barrydavisjr said:
It is under the hardware overview at the bottom. andMike i added some props to you for the method!
Click to expand...
Click to collapse
Cheers barrydavisjr.
Did it all work out well for you, I hope so.
Thanks
Mike
mikechannon said:
Cheers barrydavisjr.
Did it all work out well for you, I hope so.
Thanks
Mike
Click to expand...
Click to collapse
Yes Worked perfectly!!!
I have not done it yet, but plan to soon. To clarify what your fix does is that it tightens the sliding keyboard rails? or provide a better click when its closed?
Just read your site. I think that answered my question. Thanks, I will try and post my success (...or failure).
Great fix. One of the little but annoying things about the device fixed.
sliding keyboard then freezes
hello, I got my device ! I'm very happy but when I slide the keyboard, and here the left 'click' then it freezes.
It is very strange, is there anything I can do ?
Thanks in advance for any suggestion
dam said:
hello, I got my device ! I'm very happy but when I slide the keyboard, and here the left 'click' then it freezes.
It is very strange, is there anything I can do ?
Thanks in advance for any suggestion
Click to expand...
Click to collapse
I don't think the "clicking" mechanism is what's making your device freeze. I believe its the display going from portrait to landscape mode what's probably making it freeze up. Have you hard reset to make sure there is no 3rd party today plugins that are having issues with switching to landscape mode?
sliding keyboard, frozen device
dear brmcguire, thank you for your answer. I think I have to be more precise.
When I slide the keyboard and stop before the "click", it is ok, it moves to the landscape mode without problem. Then, when I push untill it locks, on the right lock it is ok but when pushed untill the left lock, then it freeezes. To be precise, "freeze" means that the menu bar opens, and the tactil screen does not answer anymore to the pen, (I can still use the buttons).
That is why I believe it is a hardware malfunction, but I'm still a newby
Does anybody had a similar problem ?
Any help appreciated
dam said:
dear brmcguire, thank you for your answer. I think I have to be more precise.
When I slide the keyboard and stop before the "click", it is ok, it moves to the landscape mode without problem. Then, when I push untill it locks, on the right lock it is ok but when pushed untill the left lock, then it freeezes. To be precise, "freeze" means that the menu bar opens, and the tactil screen does not answer anymore to the pen, (I can still use the buttons).
That is why I believe it is a hardware malfunction, but I'm still a newby
Does anybody had a similar problem ?
Any help appreciated
Click to expand...
Click to collapse
Ok, I see. It does sound like a hardware issue. I would try exchanging it for a new one.
dam said:
dear brmcguire, thank you for your answer. I think I have to be more precise.
When I slide the keyboard and stop before the "click", it is ok, it moves to the landscape mode without problem. Then, ...,,,,,,,,,,,,
Click to expand...
Click to collapse
I think we're all agreed it has to be hardware. There is no software that operates when the "left" edge clicks into place. There are two circuits that operate softwarewise when the keyboard opens
1. There is a small magnet operated switch that changes portrait to landscape and that's working fine,
2. The light sensor above the "p" key top right which operates the keyboard backlight.
I don't think either of these is responsible.
At a guess either the Multi connector Mylar Cable for the screen/digitizer connection is getting trapped/pulled/stretched and partially breaking its connection or the click into place is creating an internal squeeze against possibly the "windows" button hardkey next to the Green Phone Key.
I think like brmcguire that I'd get it back to shop while still in warranty perhaps after doing all the usual things like a hard reset - just in case we're all wrong and it is software.
Or you just never quite open it far enough to click into place. I do this a lot, partly because I've got a really firm click into place on both right and left sides that if I'm just quickly using keyboard I find I can get every key without the final clicks.
Mike
thanks
I tried hardware reset but no change. Anyway, thank you so much for your anwers. Not that it works better, but to feel support is quiet healing.
cheers !
mikechannon said:
I think you're right, maybe we need a Hermes counselling and psychological support group. All charges forwarded to HTC of course!
Mike
Click to expand...
Click to collapse
ok, I gave back my device, I will see what happen. Thanks !
RE. loose keyboard
CAN someone give me the direct link to the wiki page bc i couldnt find it i dont know why, if you know how to do it you can also send me the directions but PLZ someone send me a link thanks again
Did this fix after fighting with a very loose slider from the beginning. This and Mob6 software and I love my TyTn again.
Thanks for the instructions and thanks for the wiki.
derf
Hi all, this is my first post on this forum but I've been reading for a while to educate myself.
I've got a Herm200 that I've been trying to troubleshoot but to no avail. I'm fairly certain that it has a hardware problem but I haven't been able to isolate anything.
Here's whats happening:
Occasionally the screen will come out of stand-by all white. This will also happen randomly if i touch the screen to perform a command. While the screen is operating, sometimes the buttons on the face will stop working, however the buttons across both sides will continue working just fine.
When the screen turns all white a soft, hard, or stand-by cycle will not always bring it back to life. The fact that the hard reset wont always fix the problem makes me think it's a hardware issue since the phone will boot-up with the the all-white screen.
This is incredibly frustrating especially since HTC wont accept any warranty claims in the USA on the Tytn.
At first I thought this might be a problem with the ribon connection between the screen and the base but i haven't been able to confirm or discount anything at this point. I have yet to find a way to consistently reproduce or rectify the problem so it's very hard to troubleshoot.
I pretty much have to take a second phone with me everywhere right now just incase i need to make a call. Please help! Has anyone ever encountered such a problem?
Thank you in advance!
SneezyRobot said:
Occasionally the screen will come out of stand-by all white. This will also happen randomly if i touch the screen to perform a command. While the screen is operating, sometimes the buttons on the face will stop working, however the buttons across both sides will continue working just fine.
Click to expand...
Click to collapse
Hi. This sounds very similar to a problem that I experienced with a HERMES100. I bought the phone off someone on Ebay recently - someone had obviously scrambled the radio on it. I re-flashed it, and it sprang to life. However, after a couple of days, I experienced a problem where occasionally the LCD would stop refreshing, all the pixels faded away leaving only a white screen. Under these circumstances, some of the buttons on the phone stopped working. Turning phone on/off sometimes cured the problem, or it would require the occasional hard reset. This would happen once or twice a day and I suspect thats why someone tried to re-flash the phone.
In the end, out of curiosity I took the entire phone apart, put it all back together again and now there are no more problems!! Totally fixed!
My suspicion is that it was one of the ribbon cable push connectors on the mainboard - possibly not seated properly, or a bit of dirt contaminating the connection. Obviously when I took the phone apart I must have re-seated it.
If you are planning to take your phone apart, please exercise considerable care because some of the parts are very small and easily damaged. I would recommend buying a proper kit to take it apart. I bought mine for about £5 off ebay. Particularly useful are the plastic spoon "wedges" used to gently prise open the case after removing the screens. Don't use a screwdriver - you will scratch the case.
Good luck.
wow... that sounds like exactly what's going on here, I actually even tried to disassemble it lastnight but didnt have the right driver set. thank you for the advice!
I'll look for one of those sets but what would you search for if i needed to find it?
Thanks again, I just got a set off of Ebay. Hopefully it'll be here next week
With any luck it'll be a connection issue.
I have had the exact same problem. Because I got the Tytn through work I made our IT department handle the issue and I am currently waiting for a replacement and to find out what happened.
Yep, it looks like the problems the OP is having are very similar to the problems we've been having over in this thread:
http://forum.xda-developers.com/showthread.php?t=291027
I'm beginning to think it's a hardware problem as well but not entirely sure.
People in the above thread mentioned that using the scroll wheel a while then moving back to use the D pad fixed the problem (very briefly in my case.) Once I use the center D pad button again it locks the hardware buttons under the screen until I make my device sleep and resume.
Somtimes rather than making all the front hardware buttons unresponsive the issue is that once I use the Down Dpad button I can't use the up button. Pressing up will make it go down, as will pressing down (at least that's working ).
Regarding the white screen - this sometimes also occurs. I can force it to white screen by putting a little pressure on the silver panel surrounding the top, right and bottom of the screen (I have an imate jasjam). Randomly when there's no pressure on the rim and I wake it out of standby, it has a white screen that can only be fixed by turning the screen off and on again.
Finally, the LED indicator seems screwy. Sometimes it never flashes. Other times it flashes sporadically (uneven intervals - we're talking maybe a minute between one flash then seconds before another). When I charge it sometimes the LED doesn't come on but nevertheless it charges. Sometimes if the LED is on it never turns green to indicate a full charge. Yet other times it comes on orange, turns green, then never switches off!
Is it possible that
a) The hardware button problems.
b) The white screen problem.
c) The LED problem.
are all related to some kind of connection going loose? Why would the hardware button problem be temporarily fixable with use of the scroll wheel if this were the case?
The other thread has fallen silent. I'm hoping that some of the gurus in here can offer some input here, even if they don't know the answer but can formulate an opinion. I know very little about these devices.
Thanks in advance guys!
PS - don't really know if I should start another thread, I've posted here as it seems like very much the same issue.
Anybody any idea? advice?
I had a similar problem with my HERM100. I didn't mess around with it too much, I just had Cingular replace it out of warranty exchange (thank god those original ROMs are on the wiki ). I did notice however that after doing a master reset, the screen would function again although I haven't messed around with it too much. I got so frustrated with removing the battery for 5 minutes and STILL powering on with a white screen that I just threw it in my back seat until the new one arrived.
I don't have these screen issues. I only have hardware button problems. It's so damn frustrating! I already own a replacement.
I just received a call from my girlfriend. I wasn't able to answer the phone with the buttons, only with a screentap. I also wasn't able to close the call with the hardware button. Since the side buttons work, I went to settings -> phone, closed it, and there we go. The hardware buttons worked again.
Why the heck is this? I truly hope for some wizz out there with some advice, since HTC would only tell me to send it back after replacing it with a new TyTN with same issues.
Regards,
DM.
Anyone anyone?
HELP!!!!
barncourt said:
Hi. This sounds very similar to a problem that I experienced with a HERMES100. I bought the phone off someone on Ebay recently - someone had obviously scrambled the radio on it. I re-flashed it, and it sprang to life. However, after a couple of days, I experienced a problem where occasionally the LCD would stop refreshing, all the pixels faded away leaving only a white screen. Under these circumstances, some of the buttons on the phone stopped working. Turning phone on/off sometimes cured the problem, or it would require the occasional hard reset. This would happen once or twice a day and I suspect thats why someone tried to re-flash the phone.
In the end, out of curiosity I took the entire phone apart, put it all back together again and now there are no more problems!! Totally fixed!
My suspicion is that it was one of the ribbon cable push connectors on the mainboard - possibly not seated properly, or a bit of dirt contaminating the connection. Obviously when I took the phone apart I must have re-seated it.
If you are planning to take your phone apart, please exercise considerable care because some of the parts are very small and easily damaged. I would recommend buying a proper kit to take it apart. I bought mine for about £5 off ebay. Particularly useful are the plastic spoon "wedges" used to gently prise open the case after removing the screens. Don't use a screwdriver - you will scratch the case.
Good luck.
Click to expand...
Click to collapse
This is my first post as I've so far managed to cure all my issues from just reading the forum. However, I am now having a similar problem with the white screen.
I have a cingular 8525. It fell and the following day the call and end buttons remained lit and wouldn't turn off and they also wouldn't work.
I soft reset, nothing, I then removed the battery and when I turned it back on, there was a white screen and the buttons below still don't work.
I have read the other posts on this issue, but I need help on exactly what kit to buy to reconnect the screen cable and instructions on how to do it as I've never taken apart a phone before, although I have dabbled with other electronic devices.
Your help would be much appreciated, as I am in Jamaica and there are no technicians here who I trust to help.
Thanks in advance.
Below are links to 2 kits I'm thinking of getting. Is either one better than the other?
http://www.pdasmart.com/pdaphonehtcmini.htm?gclid=CJrHntO-hosCFQx1VAodaQf6KQ
http://cgi.ebay.com/SCREWDRIVERS-TO...01677255QQcategoryZ108648QQrdZ1QQcmdZViewItem
CINGULAR IN JA said:
This is my first post as I've so far managed to cure all my issues from just reading the forum. However, I am now having a similar problem with the white screen.
I have a cingular 8525. It fell and the following day the call and end buttons remained lit and wouldn't turn off and they also wouldn't work.
I soft reset, nothing, I then removed the battery and when I turned it back on, there was a white screen and the buttons below still don't work.
I have read the other posts on this issue, but I need help on exactly what kit to buy to reconnect the screen cable and instructions on how to do it as I've never taken apart a phone before, although I have dabbled with other electronic devices.
Your help would be much appreciated, as I am in Jamaica and there are no technicians here who I trust to help.
Thanks in advance.
Below are links to 2 kits I'm thinking of getting. Is either one better than the other?
http://www.pdasmart.com/pdaphonehtcmini.htm?gclid=CJrHntO-hosCFQx1VAodaQf6KQ
http://cgi.ebay.com/SCREWDRIVERS-TO...01677255QQcategoryZ108648QQrdZ1QQcmdZViewItem
Click to expand...
Click to collapse
Both kits look ok. PDA one tells you a little more but the basics appear to be in both.
I'm curious though you soft reset and took the battery out, but have you done a HARD reset? I would always try this first before dismantling.
Mike
In my case, they also are always lit up when the screen is also active.
And no matter what ROM version, they occasionally stop responding. Side buttons keep working.
mikechannon said:
Both kits look ok. PDA one tells you a little more but the basics appear to be in both.
I'm curious though you soft reset and took the battery out, but have you done a HARD reset? I would always try this first before dismantling.
Mike
Click to expand...
Click to collapse
Thanks for the response.
I couldn't do a hard reset because the buttons weren't working.
I have made some progress with the phone now. Found a tech guy who looked at it for me. The white screen is gone, but the buttons still stop working from time to time.
All the connections seem ok.
Is there anything else that could cause the buttons to malfunction?
CINGULAR IN JA said:
Thanks for the response.
I couldn't do a hard reset because the buttons weren't working.
I have made some progress with the phone now. Found a tech guy who looked at it for me. The white screen is gone, but the buttons still stop working from time to time.
All the connections seem ok.
Is there anything else that could cause the buttons to malfunction?
Click to expand...
Click to collapse
Nothing obvious.
Have you got applications installed that you have loaded - could be one thats playing up.
Have you now been able to do a hard reset?
If taking device apart and reassembling improved things it does suggest hardware though and might be worth double checking all those multi-connector blocks for good connections - i.e. take them out and in a few times to ensure any oxidation on contacts is removed.
Mike
mikechannon said:
Nothing obvious.
Have you got applications installed that you have loaded - could be one thats playing up.
Have you now been able to do a hard reset?
If taking device apart and reassembling improved things it does suggest hardware though and might be worth double checking all those multi-connector blocks for good connections - i.e. take them out and in a few times to ensure any oxidation on contacts is removed.
Mike
Click to expand...
Click to collapse
Thanks Mike.
I will give that a shot.
I haven't installed any new applications recently, so I don't think it is a software issue.
Thanks again.
CINGULAR IN JA said:
Thanks Mike.
I will give that a shot.
I haven't installed any new applications recently, so I don't think it is a software issue.
Thanks again.
Click to expand...
Click to collapse
If it wouldn't be a software issue, why is it, in my case, instantly resolved when going to settings -> phone with the side buttons?
i had this problem i took it to a guy who fixed the problem he said it was a very small tear in the flex cable which causes this white screen every now ant then and the buton problem , sorry to say its the cable problem and u need a very capable person to fix it or replace it with a new one . its very common problem baised on the guy who fixed it .
dmxl said:
I don't have these screen issues. I only have hardware button problems. It's so damn frustrating! I already own a replacement.
I just received a call from my girlfriend. I wasn't able to answer the phone with the buttons, only with a screentap. I also wasn't able to close the call with the hardware button. Since the side buttons work, I went to settings -> phone, closed it, and there we go. The hardware buttons worked again.
Why the heck is this? I truly hope for some wizz out there with some advice, since HTC would only tell me to send it back after replacing it with a new TyTN with same issues.
Regards,
DM.
Click to expand...
Click to collapse
Exactly what is happening to me, no white screen issues, just screen taps and answering calls, I also have another problem where the PDA will not allow me to open anything, be it the start menu or contacts, it will open and quickly close again. I have had mine swapped through Telstra in Sydney, it worked fine for a while and then the same crap again. These problems started before I even touched the OS, so it must be a build problem. Maybe we should write a joint letter to HTC letting them know that there is a serious problem with their machine.
I have had the same problem, got my Tytn through work so we sent it back to the company that supplied it to us. Got it back yesterday and they had replaced the "switchboard". Not sure what it is but there was the problem. Had white screen and buttons not working.
Hi guys!
Long time no post!
I hope you can help point me in the right direction.
Two things started happening with my 8525 TyTN, rendering it unusable. I do have a backup one, so it's no panic. But I would LOVE to try to repair this.
Here's what happens!
1 - The two LEDs in front don't work! No green; no blue; no amber. (HOWEVER, When I first replaced the battery after a hard reset, I did see is glow red for a second!)
2 - None of the buttons on the front work! None. Start/End, the D-pad, mail, internet explorer. All dead!
Interestingly enough... the LCD screen is perfect, as is the touch screen.
The unit also works perfectly fine.
I did a Hard Reset.
I am using WM6.0.
I am wondering... PERHAPS there is some kind of ZIF cable that goes from the body to the top panel? MAYBE that came loose?
If you have seen inside your TyTN, is there one cable/ribbon for lights/buttons?
If so, that would explain it!
If there are two cables/ribbons.... one for lights, one for buttons, then the odds of them BOTH falling out are near impossible!
I would LOVE to hear any ideas or thoughts!!!
Thanks as always!!!!!
Mike
Hello and welcome to a new phone!
I have a similar problem, mine sometimes gets a white screen and the D-pad buttons rarely work for long.
It is quite possibly a loose ribbon cable.
There is actually a thread here about this issue - just do a search for 'white screen' or similar and you'll find it. It was posted to within the week so shouldn't be far from the top if you browse for it, but I can't remember which Herme's category it was in.
There's even a full guide with pics to pulling your 8525 apart!
Cheers! Oggy. ó¿ó
try a new rom,.
I have the same problem. I thought it was bcs my TyTN fell down once. It started with Iexplorer always popping up when I wanted to do something. I thought the IE button at the top was stuck or something and when I pressed hard on the message button everything was okay. All buttons worked. But after a few days they stopped working and pushing the message button wont work also. And both the red and green call button leds are always shining. It sometimes happens that the dpad works for a second and than nothing.
I used the original wm5 and flashed to 6.1 now, no change tho.
it's not the rom, tried several roms now
for me it's just the call answer button, but this is annoying enough
there are some topics in the hermes section which describe the problems you encounter or even worse problems (the lcd flickering or just giving you a bright shining white) and they all say it is a loose cable connector right under your dpad
some of them opened their tytn (guarante already gone) and put some sort of paper or rubber or sth else on the connector.
other say tighten or loosen the screews worked for them, but none of the solutions seem to be final, it always works for some time.
if you have still guarantee i would try sending back or try somewhere else a repair, that is what i will do with tytn
i hope i do not have to pay for the repair
good luck
Loose screw
I was able to fix this problem after ATT told me that I was out of warrenty and it was going to cost 499.00 for a new phone.
I it turn out it is a loose screw on the inside and to get to it you have to undue 11 screw to get to it. I might be able to fix it for you. I dought you would be able to get into this phone and not hurt any of the other functions.
Rick
Hi,
could you advise how you managed to fix it?
Thanks.
button failure and white screen
I have the same problems, if I turn off and on for 3/4 times everything back to normal. But is really annoying because I miss calls.
To me seems a software issue.... I can solve it by turning off the screen does not make sense hardware problems
have a look to this post:
http://forum.xda-developers.com/showthread.php?t=435281
I have still to test the suggestion of schaps advance config version 2.02.1.0.0
Sorry it not a software issue and you can flash a 100 roms and it still won't work. You simply have a bad flex cable and possibly a defective dpad circuit board. You have to crack open the phone to replace it and it has to be carefully done. There are tons of DIY's about opening the phone and replacing the cable. There are even YouTube Videos about it.
Aaaaghh. I am on a trip overseas and the backlight of the LCD screen on my Dopod 838 Pro just went out. Under a bright light I can make out the screen changing as things happen, but it kind of makes it hard to read (impossible!!). Luckily TomTom kept talking to me, although not as good without the picture of the map to follow!!
Anyone heard of this before? Have read of a few "white screens", but this seems different to other posts.
Would appreciate any tips on fixing or replacing the screen. I plan to try to pull the machine apart and make sure a connector hasn't come loose when I get home, but am hoping I am not up for a new machine just yet.
Although this may be an excuse to upgrade to the Touch HD when it available in Australia!!
Thanks in advance.
3 things
try 1st
make sure your brightness is turned up, settings/system/backlight
try 2nd
backup device, hard reset, see if this works. ( the backlight should not be a software issue, but it is possible)
try 3rd (although I would try this 2nd if you can, because if this works will not lose your personal data like you will in step 2)
take apart and check the flex, (common cause of this problem)
Thanks, time to find my torx screwdrivers!!
Have been playing with as many settings as I could see with a bright torch, and then tried a hard reset (fortunately it was still able to connect to my PC for backing up data).
Even loaded a new ROM OS.
It happened to my Jasjam and I found the scroll wheel circuit board was the culprit (don't ask me how). I managed to get a "broken" Jasjam off ebay for a fair price and cannabalized it for the part I needed. Fixed it nicely.
I don't know if your is the same thing but if you can get a hold of a "broken" Hermes it might be worth a shot. Found the "broken" Jasjam had nothing wrong with it either. Good buy for $120AUD...
Cheers...
ultramag69 said:
It happened to my Jasjam and I found the scroll wheel circuit board was the culprit (don't ask me how). I managed to get a "broken" Jasjam off ebay for a fair price and cannabalized it for the part I needed. Fixed it nicely.
I don't know if your is the same thing but if you can get a hold of a "broken" Hermes it might be worth a shot. Found the "broken" Jasjam had nothing wrong with it either. Good buy for $120AUD...
Cheers...
Click to expand...
Click to collapse
Oh thanks heaps man I just fixed my JasJam backlight problem by replacing the scroll wheel circuit with another one!!! This was definately the issue, i would have never thought of trying this! This should be added to the wiki.
afaast said:
Oh thanks heaps man I just fixed my JasJam backlight problem by replacing the scroll wheel circuit with another one!!! This was definately the issue, i would have never thought of trying this! This should be added to the wiki.
Click to expand...
Click to collapse
how exacly to do that, i have a backlight problem to please help
backlight only turned on when i slide my hermes
Hi there!
I bought a damaged G1 from ebay to hack on.
There is some strange behaviour, that seems to be related to the trackball.
Everytime i scroll some pages for a while, the trackball is going really mad.
It toggles between applications, e.g. starts phone app or contacts and enters weird numbers.
If i leave it completely untouched the system behaves normal.
Just to give it a try, i disassembled the device and removed the trackball mechanic. Result: Everything behaves normal.
Due to these problems, i started a little research on the trackball parts.
So here's what i found (see attachment).
I will do some further investgation and check out if i'm able to fix this issue.
My suspicion is, that one of the magnetic sensors got damaged and toggles between high and low all the time, even without the trackball beeing moved.
Did anyone realized such a behaviour on a G1?
Any comments are welcome!!
Regards,
scholbert
Note that the trackball on HTC DREAM is identical to the trackball used in RIM cripplephones, so you can find a replacement easily... you can probably get a broken RIMjunk for $5 with good trackball hardware, or you can try at something like blackberrytrackball.com.
Hey lbcoder,
i knew that the touchball is identical to those used in the blackberries.
Thanks anyway to add this info and for pointing me at the web link!
Got a spare part with broken flat cable from another G1 device.
I'll have to do some further testing and then start the soldering job
BTW the trackball itself is not the damaged part. It's one of the magnetic sensor parts, i suppose.
Would be interesting if anyone else ever was affected by some irritating trackball issues?
Regards,
scholbert
It *is* magnetic though, so theoretically it *could* be an issue with the mechanical components rather than with the sensor itself... i.e. something stuck in the wrong place getting picked up by the sensor as continuous. Unless you've tried swapping them out already.
If you haven't already, I would at least try that. No need to go all the way to soldering just to find that it was something else
...
If you haven't already, I would at least try that. No need to go all the way to soldering just to find that it was something else
Click to expand...
Click to collapse
Sure, just did some test with the other mainboard (connector for touchscreen is damaged on this part).
The trackball behaves normal with this combination.
So the sub-PCB must be O.K.
I'll try searching for something weird on the original mainboard.
Damn, this would be much harder to fix i suppose
I'll keep you informed!
Anyway, maybe the datasheet would be of any use for the curious geeks
Best regards,
scholbert
experts welcome
Hi again,
after some more testing and examination of the hardware stuff, i'm in doubt that this problem is hardware related.
So i started to think of some software related issues.
I know that bootcode and Android filesystem should be aware of bad blocks in NAND memory.
But anyway here's the history of the device (so far i know it):
- It came to me with stock bootloader and firmware 1.5
- A stock update was made to firmware 1.6
- I did a downgrade to RC7 using a goldcard
- Rooted the device using telnet
- Installed cm-recovery-1.4
- Followed the steps from cyanogen's wiki to move to v4.2.12.2
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
- Also did a radio update to 2.22.19.26i
- Installed Hard-SPL as well
Everthing went fine, also no problems during registering to a google account.
I am able to boot into HSPL and the cm recobery is also intact.
It's very strange that the trackball weirdness did not change during all these up/downgrades.
I also got some issues with the power button.
Sometimes the device can not be set to sleep and immediately comes back into active state
Apart from that the device behaves quite normal...
What the hell is wrong with this device?
Could there still be some corrupt areas in NAND caused by bad blocks even after reflashing the system?
Any advice would be welcome!
Regards,
scholbert
scholbert said:
Would be interesting if anyone else ever was affected by some irritating trackball issues?
Click to expand...
Click to collapse
Yes, my trackball likes to 'triple-click', which causes issues sometimes, especially when submitting web forms. I even have to use Ra_mon recovery over cyan because he has option to use talk button where my trackball multi-clicking would bypass the 'click home to continue any other key to abort' by auto-clicking to abort.
Hi jalsing,
thanks for your reply
Yes, my trackball likes to 'triple-click', which causes issues sometimes, especially when submitting web forms. I even have to use Ra_mon recovery over cyan because he has option to use talk button where my trackball multi-clicking would bypass the 'click home to continue any other key to abort' by auto-clicking to abort.
Click to expand...
Click to collapse
Sounds like hardware related damage, because this occurs in recovery mode as well. Maybe the pushbutton underneath the trackball causes this issue, while pressed.
Could be some corrosion or similar causing this...
Is there anyone who made some experience with file corruption or bad blocks?
Regards,
scholbert
scholbert said:
I also got some issues with the power button.
Sometimes the device can not be set to sleep and immediately comes back into active state
Click to expand...
Click to collapse
I have noticed some weirdness in the power button, but I am thoroughly convinced that, at least in my case, it must be hardware related.... if I just shove down on the power button with the pad of my finger, it goes off and then right back to the lock screen. If I press the power button on the 9-clock point with a finger nail, it behaves as expected.
Although I must admit that this appeared coincidentally with a radio firmware upgrade.
Hey there,
I have been having an odd issue too although one that has not been mentioned. About a week ago when i scrolled "left" or while landscape "down" the trackball got jammed every 3 rotations. When you continue scrolling it repairs itself temporarily and then returns. This issue is still present but is not quite so bad.
I'm guessing that this would also be a hardware issue. Its not at a stage where its overbearingly annoying yet, just wondering if anyone else has similar issues.
Hi vonapets,
have you tried to check your hardware with HTC Dream diagnostic programm on sdcard? You'll have to create a "goldcard" and with the file DREADIAG.nbh.
Insert the card and enter bootloader mode, the test software will load automatically. Please search the forum, if you don't know what i'm talking about.
Anyway i did these tests on my device sometime ago and all hardware test were successful.
That's why it's all so strange
Especially i run the button test several times, and the test software did pass with no errors.
Regards,
scholbert
???
It's me again
Seems that i'm nearly the only one who suffers from this specific trackball issue.
Anyway i won't give up so early and i really hope to find the reason of this erroneous inputs.
After checking some of the system libs and the framework files concerning file integrity, i started some rudimental debugging with adb.
Working with the tool getevent i found out that input event2 (trackball) is detected correctly and disappears if the trackball remains untouched.
When the random inputs are going to start, input event3 (virtual keyboard) occurs though i did not touch anything (especially not the virtual keyboard)
If i am at home screen the inputs hit google search entry field and most of the time the number "3" is printed.
Input event3 stays active until i fiddle around with the trackball or press some hardware buttons. This sometimes stops the weirdness
I also did check the interrupt counting with cat /proc/interrupts.
Everything looks quite normal....
I am really wondering what is causing this.
Maybe it is a side effect from some damaged hardware part (maybe MSM7201 itself) or it is some software bug that has never been observed before.
Maybe it is the result of some bad timings...
Really got no clue right now!
EDIT: Just for completeness. Also did perform RAM test and other hardware diagnostic with DREADIAG. No errors here!
Regards,
scholbert
jalsing said:
Yes, my trackball likes to 'triple-click', which causes issues sometimes, especially when submitting web forms. I even have to use Ra_mon recovery over cyan because he has option to use talk button where my trackball multi-clicking would bypass the 'click home to continue any other key to abort' by auto-clicking to abort.
Click to expand...
Click to collapse
+1
i have trouble using recovery too. I have to press it very lightly to get it to select only once otherwise it clicks several times ><
Not a huge issue for me really, i don't use it that often, but it is pretty irritating.
But, no. I've never had it enter any numbers or anything, that is strange.
However, i do have a strange problem where when the phone receives a slight knock, like if it's in my pocket and it bangs against something, or i drop it a couple of inches onto my desk or something, a random app will launch. I have no idea why this happens and it's not anything coming in contact with the screen because it happens even when it's locked. It's usually the market which opens too for some strange reason. Oh, it also reboots sometimes too
Yeah, i think i need a new phone
scholbert said:
It's me again
Seems that i'm nearly the only one who suffers from this specific trackball issue.
Anyway i won't give up so early and i really hope to find the reason of this erroneous inputs.
After checking some of the system libs and the framework files concerning file integrity, i started some rudimental debugging with adb.
Working with the tool getevent i found out that input event2 (trackball) is detected correctly and disappears if the trackball remains untouched.
When the random inputs are going to start, input event3 (virtual keyboard) occurs though i did not touch anything (especially not the virtual keyboard)
If i am at home screen the inputs hit google search entry field and most of the time the number "3" is printed.
Input event3 stays active until i fiddle around with the trackball or press some hardware buttons. This sometimes stops the weirdness
I also did check the interrupt counting with cat /proc/interrupts.
Everything looks quite normal....
I am really wondering what is causing this.
Maybe it is a side effect from some damaged hardware part (maybe MSM7201 itself) or it is some software bug that has never been observed before.
Maybe it is the result of some bad timings...
Really got no clue right now!
EDIT: Just for completeness. Also did perform RAM test and other hardware diagnostic with DREADIAG. No errors here!
Regards,
scholbert
Click to expand...
Click to collapse
Virtual keyboard? Or touchscreen? Is the virtual keyboard actually listed as a separate input from the touchscreen? If it is, then how could it even be triggered when the vk isn't even opened? Or is the vk open when this weirdness happens? Could it simply be the digitizer that's borked?
Here's a REAL SIMPLE IDEA: clean the digitizer with rubbing alcohol. Can't hurt, and now that you bring touch events into the picture, there is a little bit of a dejavu feeling starting to come over me -- not from personal experience mind you, but I do recall someone mentioning something about a greasy digitizer causing some weird problems.... that went away when it was properly cleaned.
And if nothing else, if it happens to be a digitizer problem and the digitizer is totally borked, try disconnecting it. You should still be able to navigate by trackball and hack on it without a functioning touchscreen.
I know it sounds confusing, but it's true...
Thanks for the replies!
Is the virtual keyboard actually listed as a separate input from the touchscreen?
Click to expand...
Click to collapse
Yepp!
If it is, then how could it even be triggered when the vk isn't even opened?
Or is the vk open when this weirdness happens?
Click to expand...
Click to collapse
Yepp!
BTW, you may type characters on the vk simultanously, while there are numerous 3's fired from somewhere inside the system.
The ascii changes if i also scroll the trackpad....
If you are able to close vk it opens up again randomly
Could it simply be the digitizer that's borked?
Click to expand...
Click to collapse
Nope!
Already did test with disconnecting the digitizer, same behaviour.
Very wicked and confusing
I really think there must be something destroyed inside the MCU.
Short circuit or ESD damage on a GPIO bank of the chip.
I will do further debugging.....
scholbert
...not givin' up
Hey there,
i don't know if this is still of interest for someone, but anyway here's updated information about this confusing behaviour:
- booting into recovery console (different kernel, only initrd running from RAM)
- scrolling up with the trackball causes ASCII char "u" in this console
- after scrolling the hardware keyboard is blocked
Using SHR kernel:
- used sd boot image from leviathan and flashed it to the boot partition
- sdcard is used as rootfs
- system boots up after login i enter the console
- scrolling up with the trackball causes strange ASCII string "u542i3" in this console
- after scrolling the hardware keyboard is not blocked
Pretty sure that some parts of hardware are causing this "ghost" input.
I decided to put the mainboard into pure alcohol for some hours.
Though the humidity stickers on my mainboard never turned to red, i just want to make sure that there's no dirt causing this strange effect.
Anyway it's my last hope....
P.S.: Anyone ever programmed a simple commandline tool to observe the state of the systems GPIO?
Would be very helpful to find the needle in the stack
EDIT: In the meantime i found out a lot, about the internal components of the HTC dream.
If there's some interest, i may open up a new thread post some information about it.
Cheers,
scholbert
O.K. no ideas anymore.
Quoting myself:
scholbert said:
...
I decided to put the mainboard into pure alcohol for some hours.
...
Anyway it's my last hope....
Click to expand...
Click to collapse
Last hope has gone!
Some hardware part has also gone, i suppose.
Battery life was always very worse using this mainboard, which is another indicator, that something hardware related had gone mad.
P.S.: Anyone ever programmed a simple commandline tool to observe the state of the systems GPIO?
Click to expand...
Click to collapse
Anyone??
Whatever, i think i'll use that mainboard for some awesome experiments
Bye bye,
scholbert
Hey, new to this forum, and just stumbled across your post searching for a resolve to my problem, which seems to be very similar to yours.
Phone seems to work fine except:
When rolling trackball up (even slightest movement) I get virtual keyboard appearing on screen and u542i3.....(continuous 3's) types into the searchbar.
Also MENU button is inop, although one on keyboard is ok.
When locked, sometimes the screen and key backlights constantly go on and off.
Seems to flatten the battery pretty quick.
I stripped the phone checked everything clean and dry etc, tried turning the trackball upside down on the offchance, but no change. I have done nothing software related as I'm not too clued up on that side of things. It has the std 1.6 operating system as far as I know.
I have no clue where to go from here with it though, think my best bet might just be to get another one that needs a screen or something and use mine for parts?
Good to see I'm not alone with this issue though so there's a chance someone may figure it out.
....at least i'm not alone
Hi ram5ay,
thanks a lot for your reply!
ram5ay said:
...
When rolling trackball up (even slightest movement) I get virtual keyboard appearing on screen and u542i3.....(continuous 3's) types into the searchbar.
Also MENU button is inop, although one on keyboard is ok.
When locked, sometimes the screen and key backlights constantly go on and off.
Click to expand...
Click to collapse
That's exactly the behaviour of my device.
Seems to flatten the battery pretty quick.
Click to expand...
Click to collapse
True, i also observed this issue.
Seems that parts of the hardware are damaged or not set up correctly due to some other error.
As a result some of the GPIO's may act as an output and are shortened to Vio or GND. This could be a reason why the battery got drained so fast
Anyway, as i already wrote down, got no clue how to fix this.....
Best regards,
scholbert
scholbert said:
got no clue how to fix this.....
Click to expand...
Click to collapse
Cool man, no worries. Maybe futile, but I'll prob pull mine apart again and have another look, if I have any success I'll keep you posted.