diff --git a/LDP/inprogress/Linux-Android-HOWTO.sgml b/LDP/inprogress/Linux-Android-HOWTO.sgml index 79f1eea6..7317cac5 100644 --- a/LDP/inprogress/Linux-Android-HOWTO.sgml +++ b/LDP/inprogress/Linux-Android-HOWTO.sgml @@ -111,11 +111,11 @@ on. Nothing special, really: in general, you'll have to be able to find out where options are in your device. I would be glad to provide information, but unfortunately no identical menus or screens can be found across different devices of different brands and different -Android reseases. You will have to figure it out yourself. +Android releases. You will have to figure it out yourself.

Finally: rooting your device might be desirable, but it's not -necessary as long as this HOWTO is concerned. Root permissions are +necessary as far as this HOWTO is concerned. Root permissions are normally forbidden in Android, unless an enlightened vendor decides otherwise. I will mention a great program that needs root access (Webkey), but the rest of recommended software will not need it. By @@ -246,8 +246,8 @@ Some devices may also need this additional step: -Linux:~$ mkdir .android -echo "0X1E68" >> .android/adb_usb.ini +Linux:~$ mkdir $HOME/.android +echo "0X1E68" >> $HOME/.android/adb_usb.ini @@ -307,7 +307,7 @@ Connect your Andbox and run the adb shell command, which launches Android's internal shell. Please be aware that Android's native shell is much less sophisticated than bash; available commands are not made by GNU either, so you should expect minor -differences. That said, there you are: +differences. @@ -351,7 +351,7 @@ devices.

Now run the mount command, to see what devices correspond to -what directories: +what directories (line-broken for readability): @@ -368,25 +368,25 @@ tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0 tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0 none /dev/cpuctl cgroup rw,relatime,cpu 0 0 /dev/block/platform/sdhci-tegra.3/by-num/p3 /system ext4 \ -ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0 + ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0 /dev/block/platform/sdhci-tegra.3/by-num/p7 /data ext4 \ -rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,\ -journal_async_commit,nodelalloc,data=ordered 0 0 + rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,\ + journal_async_commit,nodelalloc,data=ordered 0 0 /dev/block/platform/sdhci-tegra.3/by-num/p4 /cache ext4 \ -rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,\ -journal_async_commit,nodelalloc,data=ordered 0 0 + rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,\ + journal_async_commit,nodelalloc,data=ordered 0 0 /dev/block/vold/179:8 /mnt/sdcard vfat \ -rw,dirsync,nosuid,nodev,noexec,relatime,gid=1015,fmask=0002,\ -dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,\ -shortname=mixed,utf8,errors=remount-ro 0 0 + rw,dirsync,nosuid,nodev,noexec,relatime,gid=1015,fmask=0002,\ + dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,\ + shortname=mixed,utf8,errors=remount-ro 0 0 /dev/block/vold/179:8 /mnt/secure/asec vfat \ -rw,dirsync,nosuid,nodev,noexec,relatime,gid=1015,fmask=0002,\ -dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,\ -shortname=mixed,utf8,errors=remount-ro 0 0 + rw,dirsync,nosuid,nodev,noexec,relatime,gid=1015,fmask=0002,\ + dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,\ + shortname=mixed,utf8,errors=remount-ro 0 0 tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0 /dev/block/dm-0 /mnt/asec/com.collabora.libreoffice-2 vfat \ -ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,\ -codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 + ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,\ + codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 shell@android:/ $ _ @@ -402,13 +402,13 @@ only access the internal storage, usually mounted on /mnt/sdcard, and the external storage (if available), usually mounted on /mnt/external_sd. The actual names of these directories may vary; e.g. /storage/sdcard0 or something -else. Find it out. +else. You'll probably have to figure it out for each device.

-User data, programs included, is stored in /data. Using the +User data, programs included, are stored in /data. Using the Android shell you can cd to that directory, but you can't -list its contents as you lack root permissions. Programs are usually -stored in /data/app, others (typically, paid programs and +list its contents if you lack root permissions. Programs are usually +stored in /data/app, but others (typically, paid programs and programs moved to the external storage) under /mnt/asec.

@@ -435,7 +435,7 @@ VFAT; directory names are therefore case-insensitive. - Android/data/ contains directories containing + Android/data/ contains directories with programs' user data. Each directory is named after the application, using a naming convention that will be explained in Section . @@ -646,7 +646,8 @@ Linux:~$ _

An Andbox can easily share its installed programs with another device, provided that the Android versions are compatible. All you -need is Ghost Commander. +need is Ghost Commander. In the next paragraph, you can see how to +send a file to Alice using Bob's Andbox.

From the ``Home'' position, select ``Applications'' to get a list of @@ -676,7 +677,7 @@ Andbox, using a cable or Wi-Fi. -Copying via USB cable +Copying via USB cable (from Linux box)

When you connect your device via USB cable, Linux may see it either as @@ -779,7 +780,7 @@ of the command: it's not the same as the Linux command cp -Syncing directories +Syncing directories (from Linux box)

If you want to keep a directory synchronised between the Linux box and @@ -828,12 +829,12 @@ Linux:~$ _ -Sorting files: fatsort +Sorting files: fatsort (from Linux box)

Let's suppose you copied a bunch of music files to your device. You -run your music player and open the directory containig the files. -Surprise: they're not sorted, and are displayed in (apparent) random +run your music player and open the directory containing the files. +Surprise: they're not sorted, and are displayed in (apparently) random order!

@@ -901,7 +902,7 @@ but the above works and is reasonably safe. -Copying files via FTP server +Copying files from an Andbox FTP server

This is the most traditional way to upload and download files to/from @@ -956,7 +957,7 @@ Linux:~$ _ -Copying files via web server +Copying files from an Andbox web server

Another way of getting files from your Andbox is making it a Web @@ -1597,7 +1598,7 @@ gcc: no input files

That's it! From now on, you can compile programs directly on your -Android box. Don't expect to be able to compile anything, though. +Android box. Don't expect to be able to compile every single, though. @@ -1853,7 +1854,7 @@ user interface! Taking screenshots and screencasts

-Some Anddroid versions let the user take a screenshot natively, +Some Android versions let the user take a screenshot natively, usually holding the Power and Volume Down buttons together. For all others, there's DroidAtScreen: @@ -1982,7 +1983,7 @@ url="http://www.osmand.net" name="http://www.osmand.net">.

Congratulations! You have now some basic information on how to turn -your Andbox into something useful, and how to interact with it using +your Andbox into something even more useful, and how to interact with it using your trusted GNU/Linux machine.