Quote:
Originally Posted by makkonen
I don't have much doubt that the Touch Pro will eventually have (mostly) stable, (mostly) complete native port of Android. There is nothing preventing this in the hardware; the only thing at issue is the amount of time and inspiration available to the developers to make it happen. That there are still people working hard on improving the Vogue Android port gives a good sign that the Touch Pro port will continue to come along (though it might not reach maturity until most people have left it behind).
|
That's good to know. I'm one of those "late adopters" who doesn't give up on my phone till I've wrung most of the use out of it (or at least till the 2 year contract comes up for renewal). I expect to have my Touch Pro (I was assimilated by Verizon, but my Touch Pro is an Alltel branded phone on an Alltel plan, by the way) for at least the next year, assuming it doesn't fall apart or something, so I'll probably get more active in this project as time allows.
Quote:
Originally Posted by makkonen
As far as the battery, your numbers sound about right, and reasonable. I don't think there is a tool that could give us very good battery info in Android, since the underlying data that we have access to is not very good at this point. A constant drain of 300+ mA from a device with all its parts in a full-power state doesn't sound too far off. With power collapse working, that can be seriously reduced (to an average of maybe ~150mA). With power collapse working and the most offending battery drainers disabled (radio off, wifi off), I imagine the phone would probably only draw 25-50mA and would last for a day or more. Which is still less than ideal, but, again... reasonable.
|
I'm thinking that you're on the right track, that the phone is not remaining "asleep". I'm running a stock Alltel ROM on my phone tweaked quite a bit for power management, and it's only drawing about 40 to 50 mA in its sleeping state (screen off, and EvDO connected but dormant), and then up to about 350 mA when in use, equaling about a 20 to 24 hour discharge. My wife's Droid Eris draws about half of that, and she gets about 2 days out of a similar sized battery, so it's not simply a product of the OS. WiFi is a battery hog, we all know that... but a dormant (on, but not actively moving data) EvDO data connection and phone radio shouldn't draw that much. Something else is going on in the background.
Quote:
Originally Posted by makkonen
Finally, a resistive touchscreen is a fundamentally different beast than a capacitive one. There is no getting around this; Touch Pro Android will never support multitouch, and will never have the effortless touch experience of a capacitive panel. That said, we're not trying to make a resisitive screen act like a capacitive one -- we're using the driver from the HTC Tattoo (the one Android device with a resisitive screen). This driver obviously has some issues with our specific panel, but that's a smaller, more tractable problem than the capacitive/resistive issue.
|
That clears it up too. I wasn't real clear on this. I didn't realize that there was an Android device with a resistive screen out there.
I'll be diving into this project within the next few days... possibly my skillsets may if nothing else bring another point of view. This is a worthy cause, and I'll help in any way I can as time permits (I don't seem to have as much of that as I used to).