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

[rev800x]

Anybody having issues getting Windows XP to see the phone via USB? I'm trying to install some programs but it won't see the device. And yes I have the USB debugging on.

[chrialex]

The code worked out of the box for me, tried it with the old data.img first with no problems, then backed that up and rebuilt it with no problems. Not sure on the looping...

[TWiST]

For the new 2.1 build do we still use the links on the first page for the rootfs and kernel and all that ?

[makkonen]

Originally Posted by peterm20

Side note: You got a TP2? Why not a Hero or moment? Well at least they will have someone skilled with android to help the rhod development.

I've got the SERO plan, which they don't allow you to activate an Android phone on. That's why I didn't upgrade to the Hero or the Moment.

And I got a cheap upgrade from insurance, due to some issues I was having with my TP. That's why I upgraded at all.

Originally Posted by rev800x

Anybody having issues getting Windows XP to see the phone via USB? I'm trying to install some programs but it won't see the device. And yes I have the USB debugging on.

A) You've got to have the phone hooked up to activesync before you boot into Android, or it'll never show up. B) You've got to add the usb_function_switch command to the eclair.user.conf file if it's not there (I can't pull it from my memory right now, search the thread and you should find it). If you do those two things, ADB should work (unless something's busted in the new kernels, which I doubt. It's been working on every kernel I've tried lately.)

Originally Posted by TWiST

For the new 2.1 build do we still use the links on the first page for the rootfs and kernel and all that ?

Those links are still applicable, yes. They point to the newest kernel, initramfs, and rootfs, all of which should work with the 2.1 builds.

[TWiST]

I updated with the newest rootfs and the newest kernel and I am having the boot logo looping forever hmmm

[makkonen]

Tried deleting data.img?

[TWiST]

It was a full clean install without a data.img yet, I am going to delete it if it created one and try again

[TWiST]

This is my startup the same one I have been using for a long time with the 2.01 builds

set ramsize 0x6000000

set ramaddr 0x10000000

set mtype 2039

set KERNEL zImage

set initrd initrd.gz

set cmdline "lcd.density=210 msmvkeyb_toggle=off physkeyboard=raph north_am_dialing=1 gsensor_axis=2,-1,3 rel_path=andboot acpuclock.oc_freq_khz=528000"

boot

[arrrghhh]

Originally Posted by TWiST

This is my startup the same one I have been using for a long time with the 2.01 builds

If you're making it to the boot animation, I can guarantee that it's not the startup.txt (well, pretty much guarantee :P)

You've reformatted the SD just to be sure? Based on some comments over @ XDA, people with the looping boot animation were just updating to the newest zImage & rootFS & it was fixing it. I never experienced the issue, so I'm not sure what caused it.

[peterm20]

Originally Posted by makkonen

I've got the SERO plan, which they don't allow you to activate an Android phone on. That's why I didn't upgrade to the Hero or the Moment.

And I got a cheap upgrade from insurance, due to some issues I was having with my TP. That's why I upgraded at all.

Ah good deal then, I was trying to get them to give me something other than a TP/TP2 when I was having issues with mine but I just went with upgrading to a android phone. Its sad sometimes it feels like the TP port runs better than the leaked 2.1 for the moment.