using rhodium as an android development phone

[millmanorama]

I can get android running on my sprint rhodium, and that is a great.

Does anyone know how/if i can get it to talk to the android sdk adb so i can develop my own apps and test them on my phone. If i am in active sync mode and connected when i boot into android , it reports that usb debugging mode is active, and the phone shows up as android adb in my device manager, but not when i run "adb devices" from the command line.

Any help would be awesome.

[jafterdark]

put this file in this folder \conf\ it's been edited to make usb to work for adb devices=D>

[millmanorama]

this worked perfectly! thanks a lot!

[millmanorama]

I don't what jafterdark did to that file, (or how any of this porting stuff really works in detail), but just out of curiosity, anyone know why this isn't enababled/included by default?

[jafterdark]

has to look like this

# custom shell commands, these commands run last
custom_shells{
#echo "Hello!!!" # example
#echo "You can create your own commands here" # example
echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch
}

[suree_n]

Thanks.

But I understand that the SDK still cannot see the Phone's storage , right ?

[suree_n]

Another question, jafterdar after I can adb devices, I try to replace the system fonts but the files are read only. I, then try to identify the system device i.e /dev/block/loop1 and try to remount as rw. but the flag still ro. anything wrong ?

do i have to set up anything on tp2. i only turn on usb debugging mode.

[suree_n]

I also tried using ADB remount, but again failed.....

[makkonen]

Hey, look, it's some questions I know the answers to.

1) Why isn't usb_function_switch set to 2 by default?

That's a hack to make it work in Windows. It makes it appear as a single device isntead of composite (so no simultaneous mass storage and adb). When it's set this way, it WON'T work under Linux (or OS X, I believe). Since the main devs tend to be running Linux, the default state is composite interface on, linux friendly. (And closer to how it should actually work. In the future, it'd be nice to have the composite interface working in Windows.)

2) Why can't /system be remounted in rw (read/write) mode?

Squashfs (the filesystem type for system.sqsh... ok, that should be obvious) is a highly compressed, low-overhead read-only file system. That makes it very good for system files, which need to be loaded often, and not take up too much space, but rarely need to be changed. Unfortunately, it means that... they can't be changed.

In order to modify the system files, you have to use a linux machine to unsquash the filesystem, make your changes, and then resquash it.

[suree_n]

Originally Posted by makkonen

Hey, look, it's some questions I know the answers to.

1) Why isn't usb_function_switch set to 2 by default?

That's a hack to make it work in Windows. It makes it appear as a single device isntead of composite (so no simultaneous mass storage and adb). When it's set this way, it WON'T work under Linux (or OS X, I believe). Since the main devs tend to be running Linux, the default state is composite interface on, linux friendly. (And closer to how it should actually work. In the future, it'd be nice to have the composite interface working in Windows.)

2) Why can't /system be remounted in rw (read/write) mode?

Squashfs (the filesystem type for system.sqsh... ok, that should be obvious) is a highly compressed, low-overhead read-only file system. That makes it very good for system files, which need to be loaded often, and not take up too much space, but rarely need to be changed. Unfortunately, it means that... they can't be changed.

In order to modify the system files, you have to use a linux machine to unsquash the filesystem, make your changes, and then resquash it.

Wow, you just enlightened me. For the unix newbie like me, it is just like impossible to modify it. Hope the developer guy will release the ROM kitchen soon so that I can cook it with my Thai fonts.