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

[peterm20]

I got 6-7hrs of use with android yesterday. with listing to pandora for about a hr of that.

[hamagc]

per someone on hofo:

Latest update.

The latest kernel allows full functional Bluetooth audio streaming.

any news on this makk?

[hamagc]

peter thats amazing for us!

[makkonen]

Originally Posted by hamagc

per someone on hofo:

any news on this makk?

That looks like a Vogue thing -- I haven't heard anything new about bluetooth audio streaming on Raphael, though I think it comes down to a library issue more than the kernel.

After a little investigation, looks like the htc-vogue kernel just got bluetooth drivers backported from the 2.6.32 kernel. We do not have that, as far as I'm aware.

[hamagc]

doh! well thats no good for us.

[adenicol]

Originally Posted by makkonen

Hmm. I'm not sure about this one. Clearly it's set up right if it manages to boot; it's possible the SD Card is just too slow to load, so it's not finding it. If so, adding rootdelay=5 to the cmdline (in startup.txt) might help. That's a shot in the dark, but give it a try.

I tried this and it seemed to be working, was able to reboot two times in a row after 9 failed attempts before adding this. however, on the third reboot after putting that in the command line it started failing again. What I am getting is:

dosfsck 3.0.1, 23 Nov 2008, Fat 32, LFN
Logical sector size is zero.
mount: mounting /dev/block/mmcblk0 on /sdcard failed: invalid argument
Failed to mound the SD card, Cannot continue
/bin/sh: can't access the SD card. Cannot continue.


If I hadn't mentioned it before, the previous release booted up every time with no problems at all, when I updated to this release is when I started having this issue.

[staubio]

Thrilled about how far this has come at that Android is now a real, occasional option on the TP. I've also sent along a donation to keep the momentum going.

Just curious: I've seen a lot of these ports where certain functionality was indicated as nearly impossible or too difficult. Are the remaining items (GPS, camera, battery life, touch screen quirks) simply items that aren't there yet but should be do-able, or are they daunting issues with the proprietary hardware? Would love to never go back to Windows for any reason if I could.

Anyway, awesome progress and look forward to continuing to use this and send along my support.

[makkonen]

I would say none of the problems are unfixable. GPS with the same chip works on Vogue. There are camera drivers, but they have not been ported/integrated (I don't know if there are any insurmountable problems, but I believe a similar camera is used on the G1/Dream). I don't know if cameras in general are tough to reverse engineer -- even the Vogue still has pretty poor camera support. The touch screen seems to be working nearly flawlessly for me (averaging should be turned off in the kernel, I think, but otherwise it seems to respond correctly).

Of course, when and if things actually get fixed is a different question than whether it is possible. But as long as developers don't all jump ship, I think eventually all the major parts will come together.

[peterm20]

I keep getting the:

[ 4.167083] mmcblk0: mmc1:aaaa SU08G 7761920Kib
[ 4.173675] mmcblk0: p1
Running an fschk on the SD card
dosfsck 3.0.1. 23 Nov 20008, FAT32, LFN
Logical sector size is zero.
mount: mounting /dev/block/mmcblk0 on /sdcard failed: Invalid argument
Failed
Failed to mount the SD card. Cannot continue.

Error more frequently lately. normally if i mount the SD card manually and restart it works on the next boot. but not so much. I noticed another guy had the same issue a few posts back but I couldn't find it to quote

[silverD16y71996]

ok just installed the new version on my touch pro, no issue on install, and so far everything is working great... data is amazing wifi is great.

anyone know if contacts can be imported some way from outlook.

also having a issue with the background wallpaper.. it wont change and the stock paper is smaller, it has black bars top and bottom, like its wide screen...

the phone dialer seems to have larger numbers than the screen numbers 1,2,3 are partilly hidden under the the section where the dialed number shows up