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
Related
I don't know why this setting can solve this problem (May be).
Go to
start > Setting > Connection > USB to PC
Step:
1. Uncheck USB to PC
2. Start > Setting > System > Screeen > Calibration the Alignment of Screen
3. Soft Reset.
My friend also use CHT9000 (Taiwan Version) and told me this method. After the above mentioned adjustment, not alignment problem up to this moment.
I also use this method. 2 days gone, no alignment problem was found. I will keep to update this post in the future.
Hope it can help. :roll:
anyone else tried this? anything to comment?
vapor said:
anyone else tried this? anything to comment?
Click to expand...
Click to collapse
There is a thread or two about this on the general side or somewhere.
"Search" will work fine.
I tought it is working but not.
I have contacted with the local HTC/QTEK partner.
Waiting for the official solution.
BR,
Joe
I think that I may have a proper fix. my alignment seemed to be fixed by a rom upgrade but has been getting prgressively worse for a few days. Last night I tried something hardware based. I will test this for two days before I will say what it is but I have had no misalignment issue in the few hours since I did it.
Phil
could you post what you did so even if it doesnt work, we would know?
vapor said:
could you post what you did so even if it doesnt work, we would know?
Click to expand...
Click to collapse
Ok it hasn't shifted at all today!
I was going to open it up to have a look at the rubber gasket that was mentioned in another post but chickened out!
Optional but probably a good idea; turn off and remove the battery.
1) Slide keyboard out and turn face down.
2) There are 2 tiny screws on the back of the screen that need to be undone. They have thread lock on them so a small crack will be heard as it releases.
3) Once the screws are out a further small crack noise may be heard. That'll be the tension being taken off the screen!
4) Put the screws back in and tighten (or should that be TyTN?). Do not over tighten these as it is only plastic.
5) If necessary realign the screen (hopefully for the last time)
As kind of proof that this has worked, this post was made from my v1605 on hsdpa while I was talking on the phone using bluetooth and got very hot and didn't need any realigning!
Hope it works for others!
Phil
I have the O2 Trion and my screen will be slight misaligned at the right side (cant use the vert scroll bar) . Is this exactly your problem ?
Does your problem happened again, if not could you post some pic/steps on how you did it ?
Thanks :roll:
4) Put the screws back in and tighten (or should that be TyTN?). Do not over tighten these as it is only plastic.
as long as there is no excessive used here, that is what you mean right?
sectorlord said:
I have the O2 Trion and my screen will be slight misaligned at the right side (cant use the vert scroll bar) . Is this exactly your problem ?
Does your problem happened again, if not could you post some pic/steps on how you did it ?
Thanks :roll:
Click to expand...
Click to collapse
That's what mine was doing when it got hot but it has been perfect all day!
vapor said:
4) Put the screws back in and tighten (or should that be TyTN?). Do not over tighten these as it is only plastic.
as long as there is no excessive used here, that is what you mean right?
Click to expand...
Click to collapse
You're correct. Before I did this one screw was clearly at an angle and afterwards it was straight.
If anyone else has success let me know and I'll try to get some photos and do a how-to on the wiki.
Phil
i tried this out for my friend and he claims that while it did fix the alignment problem on the right side, sometimes the screen becomes slightly misaligned. could be that i tightened a bit too hard so will look into this.
I'll try to get some photos and do a how-to on the wiki.
Click to expand...
Click to collapse
yes please
hi ...
when I undone the 2 screws.. i dont hear ANY noise... but I remove and returned it a little bit untight.
Let see... :roll:
Anybody had any success with this?
I haven't had any alignment issues since I did this 2 days ago.
Phil
low405 said:
Anybody had any success with this?
I haven't had any alignment issues since I did this 2 days ago.
Phil
Click to expand...
Click to collapse
When I did it for my friend, he claims that the screen, while does not have as serious an alignment problem as before, still has it. Its not that bad.
He notices that the problem usually comes after making a call. No matter how long the call (whether for 1 min or 40 mins), the screen will be slightly mis-aligned and needs to be re-aligned. Things like pressing the 'ENTER' button on the phone pad does not work unless he presses a certain part of the button.
Any advice for him?
low45,
I undone the 2 screws but hear no click or crack and return it back not so tight... is that the correct way... I will monitor mine, since it only happening once a day..
Though I do not hv one but I can inform that it is the bad quality of work..this has been happening to all the recent G4 Wizards and Prophets with SZ series serial number.
I think thehardware design has gone wrong..
Pls check yr serial number..if they start from HT or SZ
i think all the HTC Hermes manufactured are of the HT version
screw no help
ok... after a day.. it happened again...
I just hard reset and did not load the extROM last night... let see .. :roll:
me i go back to change it
i have HT630xxxx and no probleme
Hello,
After many hours of searching I havent found something that is like my problem. I got this model recently, and now the touch area issint working. In landscape mode only the bottom of the screen is working.
Is does not mather if you push for example in the left upper side corner or the left lower side corner.... Both will result in getting "Phone" up
I havent tried a hard reset or something. And Im running the standard Vodafone rom on it. (Windows mobile 5)
Is this problem hardware or software? and is there perhaps some kind of software so I can get a mouse cursor with my Arrow-keys?
I hope you guys can give me some answers. Its a waste not using this phone
I have also no idea what the reason is why its not working. It did not drop on the floor or something like that.
Thanks in advance,
Erlerain
erlerain said:
Hello,
After many hours of searching I havent found something that is like my problem. I got this model recently, and now the touch area issint working. In landscape mode only the bottom of the screen is working.
Is does not mather if you push for example in the left upper side corner or the left lower side corner.... Both will result in getting "Phone" up
I havent tried a hard reset or something. And Im running the standard Vodafone rom on it. (Windows mobile 5)
Is this problem hardware or software? and is there perhaps some kind of software so I can get a mouse cursor with my Arrow-keys?
I hope you guys can give me some answers. Its a waste not using this phone
Thanks in advance,
Erlerain
Click to expand...
Click to collapse
Welcome to the forum
I´ve never heard of this problem, but if I were you I try to reflas with another ROM to see if corrects (see the Wiki to learn how to), if not perhaps could be a hardware problem...
Good luck,
erlerain said:
Hello,
... In landscape mode only the bottom of the screen is working.
Is does not mather if you push for example in the left upper side corner or the left lower side corner.... Both will result in getting "Phone" up
...
Thanks in advance,
Erlerain
Click to expand...
Click to collapse
Have you tried to re-align the screen?
wovens said:
Have you tried to re-align the screen?
Click to expand...
Click to collapse
Yes, but it is not getting the points that it should get. So you can try it a thousand times, and it would not make a diffreance.
Anyone? (sorry to bumb)
I have the same problem. Though I read on someplace that the screen is actualy getting pressed somewhere. try these steps and check after each try.
1st: Massage the screen softly all over.
2nd: Take a something very thin and move it under the edges of the screen.
3rd: (this on is the one that usualy works for me) try to tap softly on the back of the screen.(The aluminum plate) tap it all around the back of it.
4th: (this is the last way out when step 3 doesn't work for me.) Tap softly around the screen.
Gonna put up a video on youtube on how I do it. so you get to know how hard to tap and stuff. Since I guess we're not the only people with this problem.
Edit: Ehm. does anyone know a good free webcam recording program so I can make a video.
Ive already tried those steps. did not work
Then open the monitor part of the phone and press on the backside of the LCD.
Yep, thought the same. Ive tried to open the casing of the monitor part, but its pretty hard to get the plastic cover off
Ill try it soon again.
Thanks MiZore for ur active answering
No problem, but if you find a solution that lasts please write how here. Because I also have this problem. You have to use a little force to the the cover off. There is a dissassembly guide somewhere, I can find it for you if you haven't used it already.
i dont have that guide
Here's the guide
http://wiki.xda-developers.com/index.php?pagename=HTC Universal Service Manual
I've found another temporary solution. Take a good grip on each side of screenpart of the universal, then bend it softly back and then forth. This hasn't failed me once yet. But still no permanent solution.
gonna open mine and put something that will apply a constant pressure to the back of the screen like som cotton or something simmilar. I'll let you know the results.
Also, do you use a replacement battery or the original that came with the Uni?
Okay I opened it up today, and I think I've found the problem. Though not 100% sure. From my inspections one of the cables(small ones inside the silver tape) on the flexcable is not connected. and sadly I'm not that skilled with fixing it. So I'm gonna order a new one. I will tell you if it helps.
Okey, so I continued working on the uni today again.
Ive de-assembled the entire screen section. inspected it if anything looked broken. Wich was not the case.
Re-assembled everything again. but I still have the same problem.
As far as I know I use the retail battery
When I have some spair time ill try to look for some damaged cables.
I dont see the future of this device very brightfull
erlerain said:
Okey, so I continued working on the uni today again.
Ive de-assembled the entire screen section. inspected it if anything looked broken. Wich was not the case.
Re-assembled everything again. but I still have the same problem.
As far as I know I use the retail battery
When I have some spair time ill try to look for some damaged cables.
I dont see the future of this device very brightfull
Click to expand...
Click to collapse
Well I had to cut open the gray cover for the cables to see the damage.
But I'll see what happens when my new cable arrives.
I've installed the new cable and that fixed the touchscreen for me.
But now my sound won't work for some reason....
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.
see link below in the focus forum and WPCentral article
http://forum.xda-developers.com/showthread.php?p=9492249&posted=1#post9492249
http://www.wpcentral.com/samsung-focus-couch-potato-or-glitch
Just confirmed this issue on my Omnia7.
This is retarded. Capacitive screens don't work that way.
not having any problem on my omnia 7...tried everything to try emulate some of the effects reported! not seeing any deterioration in sensitivity!
Not a pickle from my Omnia 7, Still as lush as ever and responsive as it should be, i've been mostly USING in on a pillow/soft surface when it's laying down next to me when i'm home and sitting here for hours on end.
Loving it even more when all these bugs/glitches come out and it's stomping them down.
I feel I should come back to this and apologise as I have found a pillow which messes up my phone's touch responsiveness too. Interesting.
at45 said:
I feel I should come back to this and apologise as I have found a pillow which messes up my phone's touch responsiveness too. Interesting.
Click to expand...
Click to collapse
What kind of pillow? This smells of static to me, seeing as capactive screens rely on the tiny electrical charges in your body. Polyester fabrics getsquite static, do they not?
It happens to me when I place it on my desk...
I noticed the same thing...but I didn't associate this with the soft surface, the touch screen doesn't work when it's plugged into the charger
gdrijver said:
I noticed the same thing...but I didn't associate this with the soft surface, the touch screen doesn't work when it's plugged into the charger
Click to expand...
Click to collapse
Glad I am not the only one who has seen this.
gdrijver said:
I noticed the same thing...but I didn't associate this with the soft surface, the touch screen doesn't work when it's plugged into the charger
Click to expand...
Click to collapse
It says that in the manual! Page 12:
The Manual said:
While the device is charging, the touch screen may
not function due to an unstable power supply. If
this happens, unplug the travel adapter from the
device.
Click to expand...
Click to collapse
Of course, that's assuming your power supply is dodgy...
CreepinJesus said:
It says that in the manual! Page 12:
Of course, that's assuming your power supply is dodgy...
Click to expand...
Click to collapse
I believe the manual is a load of BS. My iPad works fine when connected to my powerpoint. I've noticed that when the Omnia is charging via powerpoint its screen sensitivity does go down, BUT, when you hold the phone with your other hand, or even just touch part of the rear/side with one finger, the screen starts working flawlessly.... imo it could be some design flaw regarding conductivity
When I place my Omnia 7 on my car phone holder (from Capdase), the screen does not respond at times, and I can't seem to find any pattern why or how this happens. Sometimes it works, sometimes it doesn't. Once I take it off the phone holder, the screen is working fine again.
I wrote it in the other thread... but I had this problem too and after I flashed the newest firmware it was gone. Now the screen responds perfect no matter where I place the phone.
You should check the thread with omnia firmware out
Another solution I found is that you would need to Hard reset your device not through the settings but turning off and than press/hold volume down + camera and power on. Than press the middle button twice and than you will not have anymore problems with touch screen.
NikD1 said:
see link below in the focus forum and WPCentral article
http://forum.xda-developers.com/showthread.php?p=9492249&posted=1#post9492249
http://www.wpcentral.com/samsung-focus-couch-potato-or-glitch
Just confirmed this issue on my Omnia7.
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Capacitive_sensing
drleospaceman said:
http://en.wikipedia.org/wiki/Capacitive_sensing
Click to expand...
Click to collapse
o really?! I thought it was just magic and the magic couldn't work when the phone was placed on soft things! im so glad someone with intelligence could teach me about this capacitive thingy whoever he is!
you have completely cleared this up for me - i now see the error of my ways. must have been having hallucinations or something. sorry for this disruption everybody!
i hope the next version of our phone uses magic because that would be really cool!
on a side note to that, after updating my firmware yesterday this dosnt seem to happen anymore. stupid hallucinations!
Had this before, after the firmware Upgrade the Problem seems to be resolved but after some time ( 1 week or so ) it's back again.
Looks like there is a fix for the laying-flat-issue for the Focus:
http://forum.xda-developers.com/showthread.php?p=11077163#post11077163
Maybe it works for some issues with the Omnia 7 as well. Did anybody already try?
Yes, have the same. If I put it on my couch, or bed. Sometimes also on hard surfaces. Doesn't bother me too much though, but it is weird.
I'm not trying to toot my own horn here...but I was literally the first person (or one of them at least) on Microsoft answers, Youtube and forums alike to raise concern about this issue.
It's a conductivity problem. As long as one hand is touching the back of the phone (sometimes near the top or sides too) then the touch screen will operate normally.
The reason it stuffs up when you have it flat is because you're not touching the back of the device, hence the conductivity flaw.
Check all this, it's a problem with the Omnia 7's, deal with it or chose another handset. I ended up keeping mine, I can live with it.
(Excuse the fact they aren't URL, stupid forum rules won't let me until 8 posts. Just remove the space between h and ttp * w and ww)
h ttp://w ww.youtube.com/watch?v=xTSi3VdFJXg
h ttp://w ww.youtube.com/watch?v=UdDNRYSMGHk
h ttp://social.answers.microsoft.com/Forums/en-US/windowsphone7/thread/5c75a85c-9d38-4d12-8211-1c7432e22b2d
h ttp://social.answers.microsoft.com/Forums/en-US/windowsphone7/thread/319a7ed0-0889-4110-a9f1-81a620ba7a7f
I've done a ton of research and this may look like an issue that's been covered but from what I can find, i don't think it has... When I boot up, I usually use the power button to get to unlock screen, now, this just makes my phone's sense not work at all, I hit the phone button and that makes it function properly. I'm guessing it's a dirty contact dust, does anyone know where I can find a 'how to' to open it up and clean the contact?
I hope I haven't misplaced this thread, but it's not a screen issue from what I can tell.
Thanks
evereste said:
I've done a ton of research and this may look like an issue that's been covered but from what I can find, i don't think it has... When I boot up, I usually use the power button to get to unlock screen, now, this just makes my phone's sense not work at all, I hit the phone button and that makes it function properly. I'm guessing it's a dirty contact dust, does anyone know where I can find a 'how to' to open it up and clean the contact?
I hope I haven't misplaced this thread, but it's not a screen issue from what I can tell.
Thanks
Click to expand...
Click to collapse
If you're not a pro(or at least assisted by one) I wouldn't recommend you to even think about: in order to get to the part you need to clean (IMO it doesn't worth it to clean it for 5-7EUR) or to change it, you need to dismantle your hd2 piece by piece (literally), including lcd+touchscreen combo from main chassis!
If you can't leave with it the way it is, go to a service shop(a good one!)!
Cheers!
bib*oops said:
If you're not a pro(or at least assisted by one) I wouldn't recommend you to even think about: in order to get to the part you need to clean (IMO it doesn't worth it to clean it for 5-7EUR) or to change it, you need to dismantle your hd2 piece by piece (literally), including lcd+touchscreen combo from main chassis!
If you can't leave with it the way it is, go to a service shop(a good one!)!
Cheers!
Click to expand...
Click to collapse
Thanks, I think I will take it to a pro...It's working great just that one very slight inconvenience. I think I caused it by installing so many roms...I'm addicted.
Yeah i got the same problem. Power button sticks and the screen becomes unresponsive, so I use a combination of Button Savior and Button Remapper, my volume up button is now my power button.