Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS! - Page 111

SoCalSpecialist · #**1101** (**permalink**) 02-22-2010, 12:13 AM

[/QUOTE]
Hi. We don't get a lot of VZW users, and the one dude who was working on the RAPH500 port got buried under schoolwork, I think, so he's no use. Where does the boot process die? Right at the start? Do you never even get the little tiny text scrolling by?

You could try contacting praxidike and seeing if he can tell you the changes he made... or you can grab his kernel over at the htc-android forums... but they are WAY out of date at this point.[/QUOTE]

the tiny txt scrolling no. all i get is the HaRET boot load bar and thats it.

but let me ask u this, if in fact i do get my mittens on that kernel is there a way that you can possibly cook some things up for it and bring it up to speed.

BTW thanks for the reply!

**makkonen** · #**1102** (**permalink**) 02-22-2010, 04:06 AM

Probably not. The kernel is available on this thread, but alone it doesn't provide much insight into what the problem is. I don't think praxidike ever found what the specific problem was with the newer kernels that caused them not to boot. Something framebuffer related, I gather, but I don't know what specifically.

Until we can find the specific commit that was causing the problem, we can't put the fix into the more recent kernels and get them booting.

DropZone9540 · #**1103** (**permalink**) 02-22-2010, 08:27 AM

aww... 3 days and no new kernel.

edit: was looking back at the last few days and found the 02/21! Sweet!

thespatt · #**1104** (**permalink**) 02-22-2010, 12:30 PM

Quote:

Originally Posted by makkonen

On an unrelated note, if anyone wants to try something out, I tweaked a few of the touchscreen settings, in an effort to get it to register less double/triple/mis-clicks. I don't think it actually makes anything better, but I'd avoided using the on screen keyboards pretty much ever because of it before, so I don't have a good baseline for comparison. Anyone want to try to come up with a good a/b test?

Screen seems wonky now. Some things are better, but the right side of the screen causes it to try and start moving to the right home screen. Also trying to pick up widgets and get rid of them is jumpy. And double taps on the left side of the screen keyboard are still there.

Also, the only button that doesn't seem to work consistently is back. I can always get the menu, phone, end and home to work, but back only works if it lights up when you slide over it. And I haven't quite figured out what triggers that to work.

Thanks for all your hard work, I've been jealous of my wife's Hero since we got it.

klobster · #**1105** (**permalink**) 02-22-2010, 01:02 PM

I am surprised this hasn't been asked yet. Has anyone tried this from a SERO plan? The reps claim that you cannot use an Android based device from a SERO plan, so I am curious as to what would happen if you attempted to use this for a few days.

answerman · #**1106** (**permalink**) 02-22-2010, 01:30 PM

Please don't take this as a n00b post... I've been around here for the last 4 years or so (I did the 6700/6800/Touch Pro sequence like a lot of us), but I've been fairly quiet since I got my Touch Pro, just running the stock ROM. My previous two phones were tweaked/customized to within an inch of their lives though... starting with HelmiC's work on the 6700 and going right through most of DCD's ROMs, while being quite involved in the projects involving the unlocking of the GPS chip on the HTC phones.

I got my wife a Droid Eris for Christmas, and I've been pretty impressed with it. So, the idea of getting Android running on the Touch Pro definitely is interesting. I've been following this thread when I've had time, and I have a couple of questions aimed primarily at Makkonen. If these were asked earlier in the thread, please accept my apologies.

First, and most important... Makkonen, with your experience working with this project, do you see the ultimate goal of actually running Android as the native OS being a possibility? Are there hardware differences between the Touch Pro and Droid Eris (using another HTC phone as an example) that would prohibit it? I'm not as knowledgable about the phone hardware as I am with desktop CPUs, but to me a stopping point would be if the actual core OS directives were "hard coded" into the chipset. With the ability to flash the chipsets, I would think that even if this was the case it could be overcome.

Secondly, regarding the battery issues: is the battery truly being depleted at the rate Android is reporting, or is it an issue with the driver (or whatever Linux uses) reporting incorrectly? Has anyone done a test using some equivalent of ACBPowerMeter for WinMo to actually gauge the rate of battery discharge in mA per hour? Using some rough numbers, if a 1300mAH battery is being depleted in 4 hours, that means a constant drain of over 300mAH. Has anyone verified this?

Finally, regarding the touchscreen: again using my previous comparison, the Droid Eris uses a capacitive screen, while the Touch Pro uses a resistive screen. Is that a hardware difference? Meaning, are we trying to make a resistive screen "act" like a capacitive screen? That would explain a lot of the sensitivity issues.

This project looks interesting, and I learned never to say "never" a long time ago... people all said that WinMo 6 would never run on the 6700, and I was there the night that HelmiC "virtually" came into the room and unveiled his work. We've come a long way... and if there is anything I can do to assist, let me know.

hamagc · #**1107** (**permalink**) 02-22-2010, 01:32 PM

the software of the phone does not matter. the ESN number is what is locked on sprint. you can take an htc hero and put windows mobile on it and it still can't be activated on sero. likewise, you can take a touch pro and put android on it and activate it no problems.

sprint has a list of esn numbers from certain phones (hero, moment, pre, etc) that can not be activated on a sero acct.

Batman · #**1108** (**permalink**) 02-22-2010, 03:16 PM

can somebody upload the newest package and modules for me? mediafire keeps bootin me off.. thanks!

tgkdubb · #**1109** (**permalink**) 02-22-2010, 03:43 PM

Quote:

Originally Posted by klobster

I am surprised this hasn't been asked yet. Has anyone tried this from a SERO plan? The reps claim that you cannot use an Android based device from a SERO plan, so I am curious as to what would happen if you attempted to use this for a few days.

SERO user here. I"ve been playing with the Android ports on the TP since about day 1 and nothing has happend to my plan...I think you may be referring to having an "actual" Android phone on the accnt, but again I;m not sure of any restrictions on that either.

hamagc · #**1110** (**permalink**) 02-22-2010, 03:46 PM

Quote:

Originally Posted by tgkdubb

SERO user here. I"ve been playing with the Android ports on the TP since about day 1 and nothing has happend to my plan...I think you may be referring to having an "actual" Android phone on the accnt, but again I;m not sure of any restrictions on that either.

Quote:

Originally Posted by hamagc

the software of the phone does not matter. the ESN number is what is locked on sprint. you can take an htc hero and put windows mobile on it and it still can't be activated on sero. likewise, you can take a touch pro and put android on it and activate it no problems.

sprint has a list of esn numbers from certain phones (hero, moment, pre, etc) that can not be activated on a sero acct.