PPCGeeks
Page 33 of 68 « First 233132 33 343543 Last »
Show 40 post(s) from this thread on one page

PPCGeeks (http://forum.ppcgeeks.com/index.php)
-   Android On TP2 (http://forum.ppcgeeks.com/forumdisplay.php?f=179)
-   -   Android, it's alive!.. (2.0.1) - Updated 12/24 (http://forum.ppcgeeks.com/showthread.php?t=102603)

Noir 12-31-2009 07:01 AM
Re: Android, it's alive!.. (2.0.1) - Updated 12/24
 
Quote:
Originally Posted by D\/8 (Post 1450073)
The Hero image is probably a better base to work with in porting to our phone as it is a CDMA device with a lot of the same specs.

I'm sure whatever has been done so far will easily be redone with the Hero image. I don't see someone going this far with such a high profile project and just dropping it and moving on unless there was a reason behind it...

Personally, I'm intimate with both the TP2 (mine) and the Hero (my girls) and I cannot wait till the day we can run droid on the TP2... Being a diehard WM fan for many years now, I think I'm going to jump ship and head over to Android...
tough to say I know that devices that will work is gsm first

The Machinist 12-31-2009 01:06 PM
Re: Android, it's alive!.. (2.0.1) - Updated 12/24
 
Quote:
Originally Posted by The Lance (Post 1449383)
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 12-31-2009 01:56 PM
Re: Android, it's alive!.. (2.0.1) - Updated 12/24
 
your calibration worked perfect for me! Thank you for your hard work.

Airhead315 12-31-2009 03:04 PM
Re: Android, it's alive!.. (2.0.1) - Updated 12/24
 
Quote:
Originally Posted by The Machinist (Post 1451043)
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

sanjsrik 12-31-2009 04:00 PM
Re: Android, it's alive!.. (2.0.1) - Updated 12/24
 
quick question, I'm guessing this is a fully-functioning android build that you have to replace the ROM on the TP2 to make work or does it work from within WindowsMobile? Sort of like AndroidKidd?

Apologies, I started reading the 33 pages and got lost along the way with the very technical discussions such as calculating hex numbers.

tr0s 12-31-2009 04:24 PM
Re: Android, it's alive!.. (2.0.1) - Updated 12/24
 
Quote:
Originally Posted by sanjsrik (Post 1451622)
quick question, I'm guessing this is a fully-functioning android build that you have to replace the ROM on the TP2 to make work or does it work from within WindowsMobile? Sort of like AndroidKidd?

Apologies, I started reading the 33 pages and got lost along the way with the very technical discussions such as calculating hex numbers.
basically there is a program called haret that you run from within windows mobile, it executes and runs android over top of windows something like a linux live cd does over top of your home computer. it doesn't install itself to your memory or mess up your current system setup. to go back to windows you simply restart the phone. it does save files and settings to your microSD but that's about it.

sanjsrik 12-31-2009 04:26 PM
Re: Android, it's alive!.. (2.0.1) - Updated 12/24
 
Thank you, very much. I'm not stupid but that explanation was concise, clear, and helpful.

Awesome response and thank you tr0s

The Machinist 12-31-2009 05:11 PM
Re: Android, it's alive!.. (2.0.1) - Updated 12/24
 
Quote:
Originally Posted by The Machinist (Post 1451043)
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!
Quote:
Originally Posted by Airhead315 (Post 1451454)
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...

HTCotta 12-31-2009 06:08 PM
Re: Android, it's alive!.. (2.0.1) - Updated 12/24
 
K i'm missing something. What exactly do i need to do with this? I tried root of device, run haret. Root of storage card, run haret. Neither of them worked, i guess I thought this was easier than it is haha.

twostep 12-31-2009 06:31 PM
Re: Android, it's alive!.. (2.0.1) - Updated 12/24
 
Quote:
Originally Posted by HTCotta (Post 1451944)
K i'm missing something. What exactly do i need to do with this? I tried root of device, run haret. Root of storage card, run haret. Neither of them worked, i guess I thought this was easier than it is haha.
put the entire folder in the root of the SDCard and then click haret, and it SHOULD work. in theory.


All times are GMT -4. The time now is 06:29 PM.
Page 33 of 68 « First 233132 33 343543 Last »
Show 40 post(s) from this thread on one page

Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com


Content Relevant URLs by vBSEO 3.6.0