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

[hussmanne]

Makkonen, loving all the work you've put into this. I'm using this on a daily basis now. The battery life/GPS are the only things stopping this from being a full time alternative to Winmo. Camera is secondary. You mentioned the bleeding edge and the autobuilds. I clicked on the links you provided, but I'm not sure how to try these out with the other files. Would it be possible for you to provide some details on to how to integrate these builds/download them into the file set that you've provided?

Thank you in advance.

The views expressed here are mine and do not reflect the official opinion of my employer or the organization through which the Internet was accessed

[rujelus22]

to use the auto builds you just need to replace your zimage and modules file with the ones you are using and reboot. if the zimage name is different you need to change your startup.txt file to match or change the zimage name to match you startup.txt

Also you guys are awesome, I have been using android exclusively for 3-4 days now. the only thing that even slightly bugs me is the super sensitive screen, playing games that you click and drag on, or trying to move icons is really hard sometimes. Other than that GPS\camera\BT I hardly ever use so I never notice. Thanks again for everyones hard work.

[bechard]

I just posted my results for RAPH800 on the autobuild for the latest... Its great.

[celsius0010]

Thanks makkonen I think I had an old data file because the market gps and music work now. The first post has gps listed as not working so I'm guessing its off the towers. Thanks man I appreciate it! Typin this in android..

[Switcher05]

It seems to be working perfect except for wifi, i can turn it on and off and connect to my wifi but once connected it disconnects after about 30 seconds or so. Not even staying on long enough to load market terms and conditions. Is there any solution to this? I have wiped the entire package with no results.

[bechard]

Originally Posted by Switcher05

It seems to be working perfect except for wifi, i can turn it on and off and connect to my wifi but once connected it disconnects after about 30 seconds or so. Not even staying on long enough to load market terms and conditions. Is there any solution to this? I have wiped the entire package with no results.

Did you try the autobuild? The latest autobuild kernel was working for hours on wifi for me.

[Santehnik]

I have intresting bug... sometimes when i launch android i have my keys not working!
Works only power key & NaviWheel, but i can't press home, end, left/right, etc...
How to fix this?

[makkonen]

Originally Posted by Santehnik

I have intresting bug... sometimes when i launch android i have my keys not working!
Works only power key & NaviWheel, but i can't press home, end, left/right, etc...
How to fix this?

The fix for that is to reboot and make sure you don't touch the navi pad while booting. Not sure why it happens, but that seems to be the workaround for now.

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?

This kernel's also got a few more modules built in... someone was asking me about netfilter for tethering (can't remember if it was here); it's in there.

[karafa]

Originally Posted by makkonen

The fix for that is to reboot and make sure you don't touch the navi pad while booting. Not sure why it happens, but that seems to be the workaround for now.

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?

This kernel's also got a few more modules built in... someone was asking me about netfilter for tethering (can't remember if it was here); it's in there.

I had asked, thanks so much for putting it in. I'm going to try it now. A good test is making a pattern unlock thing, and seeing how easy it is to do that on both kernels.

[peterm20]

Originally Posted by makkonen

The fix for that is to reboot and make sure you don't touch the navi pad while booting. Not sure why it happens, but that seems to be the workaround for now.

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?

This kernel's also got a few more modules built in... someone was asking me about netfilter for tethering (can't remember if it was here); it's in there.

Like I've written before If i wait for it to go to sleep and then wake it up the nav buttons work again for some reason.

If you put the wifi tether app from the hero on our phones it says something about missing components from the kernel. I would figure it would be netfilter/iptables modules.

It seems the current eclair branch out isn't making anything that is bootable for me. Anyone else trying to compile their own image? After doing a sync about 2 days ago since then it doesn't make a bootable image.