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

[hamagc]

makk I am seeing reports that the moment has mnc settings, they use 120. if it was not a used thing on cdma, does sprint throw it in just so the setting has a value? thoughts?

[TheTenthLetter]

Has been working great on my Boost'd Touch Pro, although t'was necessary to use the STARTUP~ file in the RAPH800 folder as opposed to "STARTUP.TXT," which would cause hanging at the HaRET progress bar 100% of the time (if you're experiencing this problem, this would be the first thing I'd check).

So far, I'm quite impressed. I'm almost to the point of full migration, but the battery drain is just too taxing for practical, out-and-about use at this point. Looking forward to the next update though, and am keeping my eye on this build. Thanks to all involved!

[makkonen]

hamagc: I could be totally wrong and have no idea. It wouldn't be the first time. But I think I'm right about how the htc-linux system deals with MCC/MNC (requiring 310/995 regardless).

TheTenthLetter. Alright. Thanks for the info. Looks like I'll need to make a new package just to put the startup.txt file in DOS format, if nothing else. I'll get on that soon.

Haaaaado Gei!

[chibiushi]

Originally Posted by makkonen

And you can use adb to transfer files (with adb push and adb pull). Accessing the sd card in a true, mass storage-y way, however, is not working, as the sd has to be mounted in Android in order to access the loop devices (data.img, system.sqsh, rootfs.img).

I was just curious, if the SD card has more than one partition can you mount only one partition, or do you mount the whole drive? I think it mount the drive, but if not would it be possible to install Android on one partition and still mount another partition in Windows?

[arrrghhh]

Originally Posted by chibiushi

I was just curious, if the SD card has more than one partition can you mount only one partition, or do you mount the whole drive? I think it mount the drive, but if not would it be possible to install Android on one partition and still mount another partition in Windows?

To my knowledge, Android does not boot at all if the SD card is partitioned. It needs to be one big partition for Android to be able to boot. And I'm not sure I follow you, why would you install Android on one partition and mount another partition in Windows anyways? That doesn't make sense, it's not like our cards are being formatted to something Windows doesn't talk like ext2...

[chibiushi]

Originally Posted by arrrghhh

To my knowledge, Android does not boot at all if the SD card is partitioned. It needs to be one big partition for Android to be able to boot. And I'm not sure I follow you, why would you install Android on one partition and mount another partition in Windows anyways? That doesn't make sense, it's not like our cards are being formatted to something Windows doesn't talk like ext2...

To transfer files to/from the SD card while in Android. Right now I boot into WM to do that, this would be easier; but I don't think it would work anyway.

[arrrghhh]

Originally Posted by chibiushi

To transfer files to/from the SD card while in Android. Right now I boot into WM to do that, this would be easier; but I don't think it would work anyway.

Yea, you're kinda thinking about it in the wrong way... it is confusing, I know. This project isn't really ever going to be ready for general consumption until we have a NAND. A lot of the userland stuff like this (I imagine) will be sorted out with a NAND. Won't solve all the problems (camera, GPS, battery etc), but a lot of the access issues that people are having should be resolved.

[makkonen]

Actually, you can partition the SD card into 2 or 3 partitions -- the first one fat32, for general storage, and then 2 ext2 partitions at the end, one for android system, one for data. (Or just 1 for the system.)

But to be effective for your purposes, it needs to get all the android files off the partition, so that the sd can be unmounted without losing access to any of the loop devices (system.sqsh, rootfs.img, data.img). There's a little code in our rootfs to mount system and data off of partitions, but that leaves the rootfs on the fat32 partition, so it's ultimately of no use.

Balsat has some builds that move everything to partitions. I'm not sure anyone but him has gotten a running system with his method, though.

(The partitioning method started with the Vogue port. People claimed having a dedicated partition would be faster. It turns out on Raphael it isn't, at all. At least not for me or those I've talked to who have tried it.)

All that said, I'm not sure mass storage mode even works. In Windows, I'm fairly certain it doesn't. However, if it does, you could try this solution from the vogue users, which allows the sd card to be mounted simultaneously over USB and on device.

edit: To clarify, the dual mount sd widget would solve the problem of having to move all the files off the partition to be mounted over USB. But it costs money.

[arrrghhh]

Ah, I am mistaken. I thought if the card was partitioned at all, Android would not boot.

I guess this was incorrect, thanks for straightening that out Makk.

In theory, we could make a swap partition to use on the SD card. I'm assuming the system just carves out part of the SD card for that anyways, but there may be a slight performance boost by making a dedicated partition to swap...

[makkonen]

It only fails to boot if the rootfs is not on the first partition. And, actually, the initramfs has been updated now where you can change that on the fly.

The problem is that usually if there's more than one partition, it's not intentional, and no one's trying to correct for it. Which is why so many people have the partitioning -> not booting problem.