Android, it's alive!.. (2.0.1) - Updated 12/24

[The Lance]

Originally Posted by The Machinist

open your startup.txt, change the msmts_calib to :=0x9f.0x39a.0x35c.0x78

save

reboot HaRET

enjoy.

did not help very much... I'm assuming that Machinist's Calibration

[cd993]

seems like developers over at XDA have started work on hero...

http://forum.xda-developers.com/show...596370&page=21 post 205

[The Machinist]

Originally Posted by The Lance

did not help very much... I'm assuming that Machinist's Calibration

at least it gets you to the edges of the screen! Niether of the two previous ones were very accruate. 0x7a.0x37f.0x35a.0x5e was too low in Y and 0x6a.0x3c1.0x376.0x8a was too high in Y and both had problems in X.

The first thing to determine was what numbers control which direction. the 1st number controls the pointer location in X(+); how far it can go right, the 2nd number is Y(+) how far it goes up, the third is X(-); left and the 4th is Y(-); down. And based on the values of all four numbers determines where the center will fall. Too much in Y(+) makes for a high center etc...

Now adding "3c1" to "37f" and divding by 2 on my calculator didn't yeild very good results (since mine doesn't add letters very well) so I guessed using a method I could never explain logically.

What I came up with seemed like a decent solution according to the "Pointer Location" within the "Dev Tools" app. in the eclair build. If anyone determines a better one I"ll be glad to use it!

[stuge123]

your calibration worked perfect for me! Thank you for your hard work.

[Airhead315]

Originally Posted by The Machinist

at least it gets you to the edges of the screen! Niether of the two previous ones were very accruate. 0x7a.0x37f.0x35a.0x5e was too low in Y and 0x6a.0x3c1.0x376.0x8a was too high in Y and both had problems in X.

The first thing to determine was what numbers control which direction. the 1st number controls the pointer location in X(+); how far it can go right, the 2nd number is Y(+) how far it goes up, the third is X(-); left and the 4th is Y(-); down. And based on the values of all four numbers determines where the center will fall. Too much in Y(+) makes for a high center etc...

Now adding "3c1" to "37f" and divding by 2 on my calculator didn't yeild very good results (since mine doesn't add letters very well) so I guessed using a method I could never explain logically.

What I came up with seemed like a decent solution according to the "Pointer Location" within the "Dev Tools" app. in the eclair build. If anyone determines a better one I"ll be glad to use it!

3c1 and 37f are hexadecimal numbers. as are the other numbers you mentioned.

To do calculations in hex use windows calculator and switch to Scientific then put it is hexadecimal mode. (In windows 7 select programmer mode).

(3c1+37f)/2 = 3a0

[The Machinist]

Originally Posted by The Machinist

at least it gets you to the edges of the screen! Niether of the two previous ones were very accruate. 0x7a.0x37f.0x35a.0x5e was too low in Y and 0x6a.0x3c1.0x376.0x8a was too high in Y and both had problems in X.

The first thing to determine was what numbers control which direction. the 1st number controls the pointer location in X(+); how far it can go right, the 2nd number is Y(+) how far it goes up, the third is X(-); left and the 4th is Y(-); down. And based on the values of all four numbers determines where the center will fall. Too much in Y(+) makes for a high center etc...

Now adding "3c1" to "37f" and divding by 2 on my calculator didn't yeild very good results (since mine doesn't add letters very well) so I guessed using a method I could never explain logically.

What I came up with seemed like a decent solution according to the "Pointer Location" within the "Dev Tools" app. in the eclair build. If anyone determines a better one I"ll be glad to use it!

Originally Posted by Airhead315

3c1 and 37f are hexadecimal numbers. as are the other numbers you mentioned.

To do calculations in hex use windows calculator and switch to Scientific then put it is hexadecimal mode. (In windows 7 select programmer mode).

(3c1+37f)/2 = 3a0

I think you missed the humor...