Hi folks,
I have figured that there are Diamonds out there with a declination in the accelerometer, which can be noticed by playing Teeter.
Some of them do have the declination, some of them don't.
Mine does .
When you hold the Diamond completely straight, or lay the device down on a flat surface (table), the ball doesn't stay in place, but rolls down in my case.
Another guy having the Diamond has the same, but in his case the ball rolls to the other side. A few other Diamonds I have tested where working the proper way, when "flat" means really "flat".
Who has the same? And would there be a way to sort of calibrate the accelerometer?
Could it be because of the back casing not being completely flat?
Could be, but I have seen Diamonds where the ball just stayed in the middle without movement when lying flat on a table.
JayRayMee.NL said:
Could be, but I have seen Diamonds where the ball just stayed in the middle without movement when lying flat on a table.
Click to expand...
Click to collapse
You're sure the table was levelled?
I'm sure they only calibrate it roughly. There probabaly is a way to do it yourself, but first we'll need to know the API's for the accelerometer.
And have you measured the table with a water-lever or similar device? Because if not then putting the diamond on a table that you just believe to be flat seems like a really really stupid argument....
The only way you can tell is to put them alltogether on the same table. If you can hold the Diamond in your hands in such a possition so the ball doesn't move anymore I would say your table is just not exactly horizontal.
Try to remove back cover...
Guys,
Trust me, I know what I'm saying.
The thing is that my and a few other Diamonds have the Teeter ball rolling towards one side when held exactly the same way (or lying on the same table) while other Diamonds have the ball lying still in the middle of the screen.
May be they're not calibrated right then, like someone1234 said. Can you hold the Diamond in your hands in such a possition - even if tilted, so the ball doesn't move anymore?
demonizator said:
May be they're not calibrated right then, like someone1234 said. Can you hold the Diamond in your hands in such a possition - even if tilted, so the ball doesn't move anymore?
Click to expand...
Click to collapse
Yes I can.
And then it's tilted (not much, but it is tilted).
I found the solution. HTC knows that they unable to calibrate the accelerometer. So they chose to have that fancy looking backplate to cover this shortness of the device. Hmm. Evil me. Sorry
In my diamond, inside teeter, the ball fall down, even if in a flat surface.
tomorrow it will be replaced with a new one, and i hope it will got a well calibrated one.
at the moment its not a big problem, but think about the future, maybe "improtant" application developed starting from the accelerometer, that will get a wrong feedback...that could be a problem...
They (or a third party) just need to come with a tool that allows the user to calibrate the accelerometer himself, in sort of way the touchscreen calibration goes. Or something.
Developers challenge?
Now, i'm not saying you don't have a right to be annoyed and I see exactly why you'd want to get i fixed. However, does it matter that much? I'm just thinking, it is only an issue when you place the Diamond on a flat surface, how many games are you going to play that involve you placing the diamond on a table? What i mean is, the whole point of the sensor is it detects you moving the device, if you place it on a table the sensor becomes useless anyway.
Like I said: other than the table, when I hold the device in my hands I need to tilt the Diamond in order to have the ball stand still.
This means there is a declination in the accelerometer, and I would like to have that calibrated. And yes, that matters to me.
In the OEM pack for the Sensor (PACKAGE_Diamond_SensorSDK)
Code:
REGEDIT4
REGEDIT4
[HKEY_LOCAL_MACHINE\Services\HTCSENSOR]
"Order"=dword:00000008
"Index"=dword:00000000
"Flags"=dword:00000000
"Keep"=dword:00000001
"Context"=dword:00000000
"Dll"="HTCSensorService.dll"
"Prefix"="SEN"
"DisplayName"="HTC Sensor Service"
"Description"="HTC Sensor Service"
[HKEY_LOCAL_MACHINE\Software\HTC\HTCSensor\GSensor]
"RotateAngleThreshold"=dword:0000002d
"CheckingTime"=dword:000001f4
"TilingAngleThreshold"=dword:00000014
"NotifyAppRotationMask"=dword:0000003f
"FaceupAsPortrait"=dword:00000001
"FaceupToLandscape"=dword:00000000
"LandscapeToP0Threshold"=dword:00000028
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\MASD]
"SensorSDK"="3_3_18153516_0"
Does editing the "RotateAngleThreshold" value do anything? I think an increase should reduce the sensitivity.
Accelerometer..
I have the same problem.. I was about to start a new thread when I saw this one.
I just sent a mail to HTC with de problem description. Maybe they can tell me what to do about it. If not.. I will contact the company where I did order the device. So they can ship me a new one.
same problem here
Isn't that thing meant for measuring DIFFERENCES (change in G-force) instead of continuously measure currend position of your Diamond?
The second option is pointless to me, and so rough calibration should do exactly what it is supposed to do: know when you change your Diamonds position and to where it changed...
Related
Is this a design hardware fault or is it jusy my Unit?
There is a lot of play of the metal part that makes up the phone/stop/windows/ok functions on the front of the device. The whole part seems to be quite loose..
has anyone else noticed this?
I am sure I read a similar complaint somewhere but cannot place where. The person said a lot of play of the key which makes for the call accept and reject strip
Yes
..thats exactly the "problem" my device seems to have. At this point I am not sure if this is a general design fault or just my unit..
my kaizer has the same problem ..
i see that is common ....and i dont like it at all...
I will have to visit a store and check a future batch to see if the problem is still there or it is just a general design fault.. I have bough this unit on line..
The play has no adverse effect on the usability of the keys but it is not nice to see and feel on a 700 Euro machine...
Any additional input on this would be appreciated
Users are posting the same thing on other sites and I have yet to see a users state that their device is any different.
Anyone else?
Has anyone else experienced the same problem? As there is no much feedback on this I assume this problem is only present on my (perhaps just a few more..) device..
I'm not seeing this with mine, the lower hardkeys are a "unit" but it's not loose. The whole unit seems quite nice and solid.
Loose is an ambiguous measurement. All agree that they have some play,,,,,, which is another ambiguous description. I agree that there is more play in those keys than with similar devices but I do not believe there is anything wrong with the hardware. I was watchful when I first received my device because I notice that those keys were more mobile that what I was use to but after a week It seems pretty normal.
Unless they became unresponsive, jammed because of displacement or unless paint rubbed off the keys from contact with the other keys then I wouldn't say it was a flaw.
Mine is tight, except for the directional pad. THat is a bit loose. But the rest of the buttons are very tight, no wiggle at all.
Sorry, yes tight is subjective. When I shake the phone they don't move or make any sound. When I rub my finger across the hardkeys from right-to-left and left-to-right, the hardkeys don't move. If I put my fingernail in the edge of the case and the keys, I can move the "group" slightly.
So my subjective opinion is that they are solid and tight. Had I not seen this thread, I would never have given these keys a 2nd thought. So there are differences in the fit and finish I guess.
its definitely a problem of the htc produce process. all types of mobile phones had similarly problems. I now have the 4th Hermes and 2 of them had play on the frontkey or the full keyboard hat not the same space at the edge. its not fine but its normal...
Hi
I've been having trouble with the touchscreen on my MDA Vario III, I'd be grateful from some advice from some of you hardware gurus.
It seems to be detecting phantom touchscreen input, which can prevent it from properly detecting real input. This was evident in the Notes application, if I were to tap around the screen in draw mode it would sometimes draw dots, but often draw a straight or curved line between the last point and the most recent one. I thought something might be pressing on the borders of the screen so I did the thin card round underneath the bezel thing, which if anything made it worse, though that may just be me imagining it.
I sent it off to a local repair firm for a touchscreen replacement, got it back this morning and it seemed to be ok, but not perfect. During the morning, having rerun kaisertweak and installed a couple of cabs, it deteriorated again.
Right now it's cycling round the Alignment Screen, the cross is moving around on its own periodically. If I try tapping the cross it mostly doesn't detect the tap.
So right now, I've got a month old Kaiser, warranty void and insurance not applicable, that I simply can't use!
My question really is, what could the problem be if it isn't the touchscreen/digitizer (they are one unit on the Kaiser aren't they?) and it doesn't appear to be a physical problem with the housing of the screen? Does it imply a mainboard failure?
Does any user configuration at all survive a hard reset? Such as increasing the touchflo sensitivity with Kaiser Tweak?
Thanks
hipster
I did/do have the exact same issue, however on my unit it only happens when using some third party stylii (spelling?)....one old Ipaq 3970 metal stylus, and 2 multifunction pens. Using the onboard stylus (or any other light stylus, like the one from the P3600) I encounter no problems (knock on wood), no matter how hard I poke on the screen....
Unit is over 3 months old - have gotten used to it, just don´t use any heavy/metal stylus.
Your problem, however, seems to be a bit more pronounced.....
Thanks for the reply, michi, though your problem does sound a bit different, if just a change of stylus improves it.
I've tried the stylus from my old Wizard and the arse end of a pen, without success, sadly.
Oddly, I'm starting to think it might be slightly heat related, if I leave the phone off for a while it seems ok, and stops responding to taps more after it's been on for a while. Very strange.
hipster
I knocked up an impression of what I get when tapping in a pattern in the Notes application, image attached.
Reading other posts about perceived performance problems with the Kaiser, I wonder if there are other cases where it seems like it's locked up, but in fact it's just taking an age to figure out what you've just asked it to do, essentially just a problem with the touchscreen, not the whole device. That's definitely one of the symptoms I get....
It's back with the menders now, hopefully, they'll manage to sort it out this time...
Cheers
hipster
Not sure if it could be similar, but I had a Tablet PC which was prone to interference from the power supply. Perhaps this is the case. May the sheilding is not up to snuff? I am by no means an expert, but this might give you another path to explore for problem resolution. Hope it helps.
I have had about 7 different AT&T Tilts in my life and if my memory serves me right, I only remember 2 of them not having the issue I am about to entail.
When I slide my keyboard out, it seems that the ribbon cable or something under the metal hinge pushes against the back of the screen and you can actually see the screen colors fray and fade as if it would do it you were to push down too hard on it with your finger.
I am just wondering if anyone else has notice this. Wonder if it is a common occurrence. I would like to know what causes this.
No such thing on the 2 I've had. Never read of it on here either.
7 Tilt's? That was a typo, right?
No issues for me at all. No resistance or screen changes when activating the keyboard.
hmmm, odd. yeah 7 man haha
i have the worst of luck with phones. the one i thought was "THE ONE" i would keep till it was time to get a new phone was hit out of my hand and the hinge came loose so I had to replace that. That one did not have the problem i stated earlier. my replacement had that screen/hinge issue so i told em to send me another one by bullshitting that it will crack my screen...the one they sent me to replace that had the 7201 chip in it and 0 hours of talk time so it was brand freaking new...but it also had the screen issue...weird, huh? i wonder if it is anything to worry about?
The momentary color shifting occurs when you are applying too much pressure to the wrong area when sliding the phone open. I don't see this is normal use since I baby my Tilt, but I am able to reproduce it when I purposely try to.
NotATreoFan said:
The momentary color shifting occurs when you are applying too much pressure to the wrong area when sliding the phone open. I don't see this is normal use since I baby my Tilt, but I am able to reproduce it when I purposely try to.
Click to expand...
Click to collapse
yeah, i am aware. it happens regardless what i do. trying to figure out what is causing it so i can find a fix
Speaking from my job experience of ripping apart laptop LCD's, it's probably the ribbon cable; as mentioned previously...
Hi . I'm going to replace my vox for TyTn 2 (!) . I need to know , what I need to check if i want to avoid sending phone to services (I think Construction , some problems like bad joystick ... ) ?
i purchased my kaiser brand new in may 2008...so you will probably get better advice from those that have gotten refurbished or second hand units.
anyway, heres a list of items you might want to check (based on my own observations as well as based on the readings/reports of various issues i've read about here on the forum):
1. hardware keys should work 100%. some users buying off ebay, for example, report that the phone works and the FRONT buttons work but the slide out keyboard is shot. just an example, it could be the other way around. but the point is to check and make sure each and every button works.
2. usb connector should work 100%. best way to check is to see if the phone can establish an activesync connection (with a known working cable) and if the orange charging LED lights up. next, hook up a wired headset (that is known to work correctly) to see if the pins for the audio signals are functioning on the usb connector. long press the button on the wired headset to see if the device starts to dial the last number dialed.
3. look out for "dead pixels". there should be NONE. because the kaiser has a relatively low resolution screen with less pixel density, i don't think it is acceptable for there to be ANY dead pixel at all because even one can become an eye sore. a quick way to check is to bring up an all-black screen and see if all the pixels are black. next, bring up an all-white screen and see if all pixels have turned white. also remember that sometimes dead pixels come and go. i've had TWO dead pixels during my ownership of the kaiser. one went away as soon as i flicked the device from the side and it never came back. another one lasted for a week and had me quite worried because it happened after my warranty period was over. i tried "dead pixel 'sweepers'" and maybe they helped because that particular dead pixel also eventually went away after a week and never reappeared.
4. scratches on the camera lens. note that the kaiser has a plastic lens "cover" on the back cover of the device. this part is known to get easily scratched and i don't think it is reasonable to be anal about this part. HOWEVER, if you take the back cover OFF, then the actual camera lens underneath the back cover should be spotless. check BOTH cameras to see if they work and can capture decent images (test the main camera with the back cover OFF to get better results).
5. the slide mechanism should be relatively "solid". look for distortions on the image displayed on the screen as you slide. ensure that the sim remains detectable when the keyboard is slid out. ensure that the front buttons work when the keyboard is slid out. ensure that the microsd card slot continues to work when the keyboard is slid out. all of the above mentioned items are connected to the main motherboard via "ribbon cables" (hidden underneath the sliding mechanism) and sliding out the keyboard can cause faulty ribbon cables to act up. look out for that!
6. make sure the status/notification LEDs work. read the WIKI/manual for information about the normal/expected behavior of the LEDs.
7. the earpiece should work. the loudspeaker should work. the microphone should work.
8. the touch screen should work! try out bubblebreaker so that you can check the responsiveness of the screen across its entire surface. recalibrate the screen if you have to. remember, the kaiser's touch screen can occasionally be a bit fussy if a screen protector is present.
9. look for obvious scratches/damage to the screen and body. try to see if the damage really matters to you (as an eyesore) or to the device (can it affect the device's normal functioning?).
10. check the water exposure stickers under the battery to make sure they have not turned a pinkish color. if they are pink, there is a chance that the device was exposed to some amount (or a lot of) water in the past. while you're at it, check the battery contacts for corrosion (might cause power issues later) and check the battery compartment for any signs that a previous battery may have leaked (extremely unlikely). who knows, maybe the owner had it properly serviced after the water exposure so no harm in asking. if properly serviced at the right time after water exposure, there have been many success stories here on the forum of the device continuing its normal functioning.
ummm thats about it from my side, hope this helps!
TYVM ... i have this phone ... I'm really exited . I'm going to do Hard SPL tomorrow ... I want some good rom ... so what is fast ... and have that D3D driver ??
congratulations!
i answered your original question because it was a bit of a unique question.
but your second question about "which ROM is good and fast" cannot be answered by anyone except for YOURSELF. go ahead and explore the Kaiser ROM Development Section. read about some of the ROMs that seem to interest you. try out a few of them and see what you like and dislike. good luck!
OK ... can you tell me ... what does thet D3D driver ??? and why 101 MB ram and D3D not working together ???
And one more thing ... i try ANYTHING but i cannot set up android and run it .... And also I don't know how to make that default.txt
And can you explain me this ??? : http://www.youtube.com/watch?v=qL8uq4FtduY
didoop said:
OK ... can you tell me ... what does thet D3D driver ??? and why 101 MB ram and D3D not working together ???
And one more thing ... i try ANYTHING but i cannot set up android and run it .... And also I don't know how to make that default.txt
And can you explain me this ??? : http://www.youtube.com/watch?v=qL8uq4FtduY
Click to expand...
Click to collapse
How about you do some searching and explain it yourself or post in threads related to your topic.
ASCIIker isn't your personal guide through this site.
A friend's sister bought her a touchpad some time ago - not sure it's ever been used. When we run the diagnostics on it, there's a band right across it where the touch sensors aren't working. So, before I invest any more time into getting this thing going for her, is there any possibility that putting kitkat (or even some later version) on this will fix this problem or is it just flat out a hardware issue?
By a band do you me a 'dead space' is there a visible 'smear' on the screen?
It won't take much time at all to flash KK on it (famous last words).
Should go smoothly. Use Rolands Tutorials for reference.
middle_road said:
By a band do you me a 'dead space' is there a visible 'smear' on the screen?
It won't take much time at all to flash KK on it (famous last words).
Should go smoothly. Use Rolands Tutorials for reference.
Click to expand...
Click to collapse
A dead band. If you hit the screen there it doesn't register. About 2 inches wide from side to side.
Seems too defined to be software related but I thought I'd ask. If it won't help, I'm not sure I want to invest the time so I was hoping someone could tell me one way or the other.
doncaruana said:
A dead band. If you hit the screen there it doesn't register. About 2 inches wide from side to side.
Seems too defined to be software related but I thought I'd ask. If it won't help, I'm not sure I want to invest the time so I was hoping someone could tell me one way or the other.
Click to expand...
Click to collapse
I've repaired them where the battery was 'swelled' up from over charging, but I haven't yet seen a dead area from side to side.
Is it possible to bring it up in WebOS and see if the problem is there also?
_Dan
middle_road said:
I've repaired them where the battery was 'swelled' up from over charging, but I haven't yet seen a dead area from side to side.
Is it possible to bring it up in WebOS and see if the problem is there also?
_Dan
Click to expand...
Click to collapse
I have two Touchpads, both set up the same. One touchpad the screen works perfectly, but on the other one there are "dead spots" not lines where you lose the capacitive touch. Which leads me to believe that it is not software related in my case.
Don't know if that helps.
Sometimes is only dirt in the way. Open the Touchpad and clean the touch sensor from inside with alcohol.
Search on youtube for cleaning touch sensor, you will get the idea.
I have fix one that one, and it works with no dead spot.
good luck!