mirror of https://github.com/tLDP/LDP
minor editorial adjustments
several minor spelling and language fixes prefixed one command with $HOME (based on assumption) added line-breaking to one verbose mount output example clarifying allusion to Bob and Alice in file-transfer section adjusting five section titles to help with "directionality"
This commit is contained in:
Martin A. Brown
parent
eade26d53c
commit
00957a8a16
|
|
@ -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.
|
||||
|
||||
<p>
|
||||
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:
|
|||
|
||||
<tscreen>
|
||||
<verb>
|
||||
Linux:~$ mkdir .android
|
||||
echo "0X1E68" >> .android/adb_usb.ini
|
||||
Linux:~$ mkdir $HOME/.android
|
||||
echo "0X1E68" >> $HOME/.android/adb_usb.ini
|
||||
</verb>
|
||||
</tscreen>
|
||||
|
||||
|
|
@ -307,7 +307,7 @@ Connect your Andbox and run the <tt>adb shell</tt> command, which
|
|||
launches Android's internal shell. Please be aware that Android's
|
||||
native shell is much less sophisticated than <tt>bash</tt>; available
|
||||
commands are not made by GNU either, so you should expect minor
|
||||
differences. That said, there you are:
|
||||
differences.
|
||||
|
||||
<tscreen>
|
||||
<verb>
|
||||
|
|
@ -351,7 +351,7 @@ devices.
|
|||
|
||||
<p>
|
||||
Now run the <tt>mount</tt> command, to see what devices correspond to
|
||||
what directories:
|
||||
what directories (line-broken for readability):
|
||||
|
||||
<tscreen>
|
||||
<verb>
|
||||
|
|
@ -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:/ $ _
|
||||
</verb>
|
||||
</tscreen>
|
||||
|
|
@ -402,13 +402,13 @@ only access the internal storage, usually mounted on
|
|||
<tt>/mnt/sdcard</tt>, and the external storage (if available), usually
|
||||
mounted on <tt>/mnt/external_sd</tt>. The actual names of these
|
||||
directories may vary; e.g. <tt>/storage/sdcard0</tt> or something
|
||||
else. Find it out.
|
||||
else. You'll probably have to figure it out for each device.
|
||||
|
||||
<p>
|
||||
User data, programs included, is stored in <tt>/data</tt>. Using the
|
||||
User data, programs included, are stored in <tt>/data</tt>. Using the
|
||||
Android shell you can <tt>cd</tt> to that directory, but you can't
|
||||
list its contents as you lack root permissions. Programs are usually
|
||||
stored in <tt>/data/app</tt>, others (typically, paid programs and
|
||||
list its contents if you lack root permissions. Programs are usually
|
||||
stored in <tt>/data/app</tt>, but others (typically, paid programs and
|
||||
programs moved to the external storage) under <tt>/mnt/asec</tt>.
|
||||
|
||||
<p>
|
||||
|
|
@ -435,7 +435,7 @@ VFAT; directory names are therefore case-insensitive.
|
|||
|
||||
<itemize>
|
||||
|
||||
<item><tt>Android/data/</tt> contains directories containing
|
||||
<item><tt>Android/data/</tt> contains directories with
|
||||
programs' user data. Each directory is named after the application,
|
||||
using a naming convention that will be explained in Section <ref
|
||||
id="programs" name="Installing/Uninstalling Programs from Linux">.
|
||||
|
|
@ -646,7 +646,8 @@ Linux:~$ _
|
|||
<p>
|
||||
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.
|
||||
|
||||
<p>
|
||||
From the ``Home'' position, select ``Applications'' to get a list of
|
||||
|
|
@ -676,7 +677,7 @@ Andbox, using a cable or Wi-Fi.
|
|||
|
||||
<!-- ----- -->
|
||||
|
||||
<sect1>Copying via USB cable
|
||||
<sect1>Copying via USB cable (from Linux box)
|
||||
|
||||
<p>
|
||||
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 <tt>cp
|
|||
|
||||
<!-- - - - -->
|
||||
|
||||
<sect1>Syncing directories
|
||||
<sect1>Syncing directories (from Linux box)
|
||||
|
||||
<p>
|
||||
If you want to keep a directory synchronised between the Linux box and
|
||||
|
|
@ -828,12 +829,12 @@ Linux:~$ _
|
|||
|
||||
<!-- - - - -->
|
||||
|
||||
<sect1>Sorting files: <tt>fatsort</tt>
|
||||
<sect1>Sorting files: <tt>fatsort</tt> (from Linux box)
|
||||
|
||||
<p>
|
||||
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!
|
||||
|
||||
<p>
|
||||
|
|
@ -901,7 +902,7 @@ but the above works and is reasonably safe.
|
|||
|
||||
<!-- - - - -->
|
||||
|
||||
<sect1>Copying files via FTP server
|
||||
<sect1>Copying files from an Andbox FTP server
|
||||
|
||||
<p>
|
||||
This is the most traditional way to upload and download files to/from
|
||||
|
|
@ -956,7 +957,7 @@ Linux:~$ _
|
|||
|
||||
<!-- - - - -->
|
||||
|
||||
<sect1>Copying files via web server
|
||||
<sect1>Copying files from an Andbox web server
|
||||
|
||||
<p>
|
||||
Another way of getting files from your Andbox is making it a Web
|
||||
|
|
@ -1597,7 +1598,7 @@ gcc: no input files
|
|||
|
||||
<p>
|
||||
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!
|
|||
<sect>Taking screenshots and screencasts
|
||||
|
||||
<p>
|
||||
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">.
|
|||
|
||||
<p>
|
||||
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.
|
||||
|
||||
<p>
|
||||
|
|
|
|||
Loading…
Reference in New Issue