https://wiki.gumstix.com/api.php?action=feedcontributions&feedformat=atom&user=Bmidgley 2026-05-15T15:47:21Z User contributions MediaWiki 1.25.3 https://wiki.gumstix.com/index.php?title=RowboatAndroid&diff=5092 2011-02-19T13:50:11Z

<p>Bmidgley: /* Build a Kernel */</p> <hr /> <div>== Android on Overo ==<br /> There are several ports of Android to Overo; one port is based off the Rowboat-Android project. This project is focused on creating a port of Android for the TI OMAP processors such as the OMAP3503 and OMAP3530 used on the Gumstix Overo boards. The steps described below explain how to get Android Froyo (2.2) running on an Overo. At the current time, there is no support for the DSP but the SGX drivers are supported.<br /> <br /> == Setup ==<br /> This section explains how to download the required code and build a kernel and root file system.<br /> <br /> === Checkout Sources ===<br /> Repo is a tool to manage multiple Git repositories. You can install it wherever you like but if you have administrator rights, you might find this convenient:<br /> &lt;code&gt;<br /> $ sudo curl http://android.git.kernel.org/repo &gt; repo<br /> $ sudo chmod a+x repo<br /> $ sudo mv repo /usr/bin/repo<br /> &lt;/code&gt;<br /> With Repo installed, grab the manifest file that describes all the git repositories we wish to fetch and then use 'repo sync' to get the latest and greatest source:<br /> &lt;code&gt;<br /> $ mkdir ~/rowboat-android<br /> $ cd ~/rowboat-android<br /> $ repo init -u git://gitorious.org/~ashcharles/rowboat/gumstix-manifest.git<br /> $ repo sync<br /> &lt;/code&gt;<br /> This (default) manifest pulls most of the repositories directly from the rowboat-android project but a few specific repositories (ahem, the kernel) have been cloned from this project and tweaked for the Overo.<br /> <br /> === Build a Kernel ===<br /> This would be a good time to apply any kernel patches.<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android/kernel<br /> $ patch -p1 &lt; ~/0001-added-palo43-pushbutton-and-led-support.patch<br /> $ patch -p1 &lt; ~/[http://groups.google.com/group/rowboat/browse_thread/thread/adf23db34979817f/bfd1f0f7a13691c6?lnk=gst&amp;q=IGEPv2+ADB#bfd1f0f7a13691c6 0001-Enable-ADB-on-IGEPv2-board.patch]<br /> &lt;/code&gt;<br /> <br /> To build a kernel, follow [http://code.google.com/p/rowboat/wiki/ConfigureAndBuild#Build_kernel these] steps; you can use ''overo_android_defconfig'' to configure the kernel. E.g.<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android<br /> $ export PATH=${PWD}/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin:$PATH<br /> $ cd kernel<br /> $ make ARCH=arm overo_android_defconfig<br /> $ make ARCH=arm CROSS_COMPILE=arm-eabi- uImage -j8<br /> &lt;/code&gt;<br /> You should now have a shiny new 2.6.32 Overo kernel here ''arch/arm/boot/uImage''.<br /> <br /> === Build a Root File System ===<br /> Follow [http://code.google.com/p/rowboat/wiki/ConfigureAndBuild#Build_rootfs these] instructions to build a root file system using ''TARGET_PRODUCT=overo'' as the argument for make. E.g.<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android<br /> $ make TARGET_PRODUCT=overo -j8<br /> &lt;/code&gt;<br /> After a bit of a wait (read: an hour or two depending on your machine), you should have the ''root'' and ''system'' directories in the ''out/target/product/overo'' directory; we can combine these to make our final root file system:<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android/out/target/product/overo<br /> $ mkdir android_rootfs<br /> $ cp -r root/* android_rootfs<br /> $ cp -r system android_rootfs<br /> &lt;/code&gt;<br /> NOTE: Users wanting support for SGX hardware should skip to that section now before packaging their root file system.<br /> <br /> We use the built-in ''mktarball.sh'' utility to package our android_rootfs directory into a tarball wherein the files have appropriate (i.e. root) permissions; this means you need root permissions for this next step:<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android/out/target/product/overo<br /> $ sudo ../../../../build/tools/mktarball.sh ../../../host/linux-x86/bin/fs_get_stats android_rootfs . rootfs rootfs.tar.bz2<br /> &lt;/code&gt;<br /> You should now have a root file system tarball sitting here ''~/rowboat-android/out/target/product/overo/rootfs.tar.bz2''.<br /> <br /> === Getting SGX (Optional) ===<br /> The PowerVR SGX hardware found on Overo boards with a OMAP3530 processor (FE, Fire, Water) provides integrated graphics support; in particular, it seems to reduce flicker on displays attached to the Overo. It is necessary to add some extra libraries and drivers to the root file system to make use of this hardware. Grab the required code and build it:<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android<br /> $ git clone git://gitorious.org/rowboat/ti_android_sgx_sdk.git<br /> $ cd ti_android_sgx_sdk<br /> $ ./OMAP35x_Android_Graphics_SDK_setuplinux_3_01_00_03.bin<br /> &lt;/code&gt;<br /> At this point, you will be prompted to agree to the software license and asked where to unpack the source files (something like ~/rowboat-android/ is probably appropriate). Now navigate to this directory and edit the user-modifiable fields in the ''Rules.make'' file. Here are some suggested values:<br /> &lt;code&gt;<br /> HOME=/home/&lt;username&gt;/rowboat-android/out/target/product/overo<br /> GRAPHICS_INSTALL_DIR=/home/&lt;username&gt;/rowboat-android/OMAP35x_Android_Graphics_SDK_3_01_00_03<br /> ANDROID_ROOT=$(HOME)/android_rootfs<br /> CSTOOL_DIR=/home/&lt;username&gt;/rowboat-android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/<br /> KERNEL_INSTALL_DIR=/home/&lt;username&gt;/rowboat-android/kernel<br /> &lt;/code&gt;<br /> Finally, we can build and install this code (N.B. these command are issued from the directory where we unpacked the source):<br /> &lt;code&gt;<br /> $ make -j8<br /> $ make install OMAPES=3.x<br /> &lt;/code&gt;<br /> More complete instructions are available [http://code.google.com/p/rowboat/wiki/ConfigureAndBuild#Install_the_Android_Graphics_SGX_SDK_on_Host_Machine here].<br /> <br /> === DSP Support ===<br /> Currently, this version does not support the C64+ DSP found on Overo boards with a OMAP3530 processor (FE, Fire, Water). To get this working, these two pages may be helpful:<br /> * http://code.google.com/p/rowboat/wiki/DSP<br /> * http://code.google.com/p/rowboat/wiki/DSPCodecs<br /> <br /> == Install ==<br /> It is easiest to boot Android from a microSD card. Follow the instructions [http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Creating-a-bootable-microSD-card/111.html here] to create a bootable microSD card with a recent MLO and U-boot from [http://www.sakoman.com/feeds/omap3/glibc/images/overo/ gumstix]. Also copy over the Android kernel and untar the root file system (requires root permissions) you have created:<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android<br /> $ cp kernel/arch/arm/boot/uImage /media/boot<br /> $ sudo tar xaf out/target/product/overo/rootfs.tar.bz2 --numeric-owner -C /media/rootfs<br /> &lt;/code&gt;<br /> NOTE: this assumes the FAT partition of your bootable microSD card is mounted at /media/boot and that the EXT3 partition is mounted at /media/rootfs---adjust as appropriate.<br /> <br /> HINT: The commands to package the root file system, install the SGX (if desired), and copy these over to a microSD card are readily script-able; if you plan on doing this more than once...<br /> <br /> ==Boot==<br /> The Android kernel requires some special parameters on boot. I have set these up in u-boot as follows (though this is certainly not the only way to do it):<br /> &lt;code&gt;<br /> # setenv anddisplay 'vram=8M omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=lcd43'<br /> # setenv andconsole 'console=ttyS2,115200n8 console=tty0 androidboot.console=ttyS2'<br /> # setenv androot 'root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait init=/init'<br /> # setenv andbootargs 'setenv bootargs mpurate=500 ${andconsole} ${androot} ${anddisplay}'<br /> # setenv andbootcmd 'mmc init; fatload mmc 0 ${loadaddr} uImage; run andbootargs; bootm ${loadaddr}'<br /> # saveenv<br /> &lt;/code&gt;<br /> To boot Android, just type ''run andbootcmd'' at the u-boot prompt.<br /> <br /> If you always want to boot into android, set and save ${andbootcmd} as your boot command i.e.<br /> &lt;code&gt;<br /> # setenv bootcmd ${andbootcmd}<br /> # saveenv<br /> &lt;/code&gt;<br /> <br /> NOTE:<br /> If you are using a 4.3&quot; LCD panel (Chestnut43, Palo43), use ''defaultdisplay=lcd43''; for a 3.5&quot; LCD panel (Palo35), use ''defaultdisplay=lcd35''; for an external DVI monitor (Tobi, Summit), use ''defaultdisplay=dvi''. Even if you are using an LCD panel, it is not necessary to change the ''omapfb.mode'' as this just sets up the framebuffer in the case that an external DVI monitor is used.<br /> <br /> == Using Android ==<br /> For touchscreen displays, you might like to replace the ''pointercal'' file found in ''~/rowboat-android/devices/gumstix/overo'' with one specific to the display you are using. To do this, boot your Gumstix + touchscreen with the standard Angstrom build, do the touchscreen calibration step, and then grab the ''/etc/pointercal'' file from the root file system.<br /> <br /> A mouse with a scroll-wheel can be attached to the USB Host port via a USB hub and used as buttons:<br /> * Right-click---back to home screen<br /> * Middle(scroll)-click---options<br /> * Scroll---scrolls<br /> Note that the mouse doesn't function like a regular pointer.<br /> <br /> Please help out by listing features that are not (and, equally important, '''are''' working):<br /> === Known Working ===<br /> <br /> === Known Failing ===<br /> <br /> == Help and Help Out ==<br /> These steps have mostly been taken from (and would hopefully be integrated with :)) the [[http://code.google.com/p/rowboat/wiki/Main rowboat-android]] wiki; look here for additional information. Other useful links include:<br /> * http://omapzoom.org/wiki/OMAP_Android_Main<br /> The mailing list for this project is quite valuable; check the archives for rowboat@googlegroups.com.<br /> <br /> Patches, suggestions and improvements are most welcome---please send to ash (at) gumstix.com.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=RowboatAndroid&diff=5090 2011-02-17T04:21:58Z

<p>Bmidgley: /* Install */</p> <hr /> <div>== Android on Overo ==<br /> There are several ports of Android to Overo; one port is based off the Rowboat-Android project. This project is focused on creating a port of Android for the TI OMAP processors such as the OMAP3503 and OMAP3530 used on the Gumstix Overo boards. The steps described below explain how to get Android Froyo (2.2) running on an Overo. At the current time, there is no support for the DSP but the SGX drivers are supported.<br /> <br /> == Setup ==<br /> This section explains how to download the required code and build a kernel and root file system.<br /> <br /> === Checkout Sources ===<br /> Repo is a tool to manage multiple Git repositories. You can install it wherever you like but if you have administrator rights, you might find this convenient:<br /> &lt;code&gt;<br /> $ sudo curl http://android.git.kernel.org/repo &gt; repo<br /> $ sudo chmod a+x repo<br /> $ sudo mv repo /usr/bin/repo<br /> &lt;/code&gt;<br /> With Repo installed, grab the manifest file that describes all the git repositories we wish to fetch and then use 'repo sync' to get the latest and greatest source:<br /> &lt;code&gt;<br /> $ mkdir ~/rowboat-android<br /> $ cd ~/rowboat-android<br /> $ repo init -u git://gitorious.org/~ashcharles/rowboat/gumstix-manifest.git<br /> $ repo sync<br /> &lt;/code&gt;<br /> This (default) manifest pulls most of the repositories directly from the rowboat-android project but a few specific repositories (ahem, the kernel) have been cloned from this project and tweaked for the Overo.<br /> <br /> === Build a Kernel ===<br /> This would be a good time to apply any kernel patches.<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android/kernel<br /> $ patch -p1 &lt; ~/0001-added-palo43-pushbutton-and-led-support.patch<br /> $ patch -p1 &lt; ~/0001-Enable-ADB-on-IGEPv2-board.patch<br /> &lt;/code&gt;<br /> <br /> To build a kernel, follow [http://code.google.com/p/rowboat/wiki/ConfigureAndBuild#Build_kernel these] steps; you can use ''overo_android_defconfig'' to configure the kernel. E.g.<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android<br /> $ export PATH=${PWD}/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin:$PATH<br /> $ cd kernel<br /> $ make ARCH=arm overo_android_defconfig<br /> $ make ARCH=arm CROSS_COMPILE=arm-eabi- uImage -j8<br /> &lt;/code&gt;<br /> You should now have a shiny new 2.6.32 Overo kernel here ''arch/arm/boot/uImage''.<br /> <br /> === Build a Root File System ===<br /> Follow [http://code.google.com/p/rowboat/wiki/ConfigureAndBuild#Build_rootfs these] instructions to build a root file system using ''TARGET_PRODUCT=overo'' as the argument for make. E.g.<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android<br /> $ make TARGET_PRODUCT=overo -j8<br /> &lt;/code&gt;<br /> After a bit of a wait (read: an hour or two depending on your machine), you should have the ''root'' and ''system'' directories in the ''out/target/product/overo'' directory; we can combine these to make our final root file system:<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android/out/target/product/overo<br /> $ mkdir android_rootfs<br /> $ cp -r root/* android_rootfs<br /> $ cp -r system android_rootfs<br /> &lt;/code&gt;<br /> NOTE: Users wanting support for SGX hardware should skip to that section now before packaging their root file system.<br /> <br /> We use the built-in ''mktarball.sh'' utility to package our android_rootfs directory into a tarball wherein the files have appropriate (i.e. root) permissions; this means you need root permissions for this next step:<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android/out/target/product/overo<br /> $ sudo ../../../../build/tools/mktarball.sh ../../../host/linux-x86/bin/fs_get_stats android_rootfs . rootfs rootfs.tar.bz2<br /> &lt;/code&gt;<br /> You should now have a root file system tarball sitting here ''~/rowboat-android/out/target/product/overo/rootfs.tar.bz2''.<br /> <br /> === Getting SGX (Optional) ===<br /> The PowerVR SGX hardware found on Overo boards with a OMAP3530 processor (FE, Fire, Water) provides integrated graphics support; in particular, it seems to reduce flicker on displays attached to the Overo. It is necessary to add some extra libraries and drivers to the root file system to make use of this hardware. Grab the required code and build it:<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android<br /> $ git clone git://gitorious.org/rowboat/ti_android_sgx_sdk.git<br /> $ cd ti_android_sgx_sdk<br /> $ ./OMAP35x_Android_Graphics_SDK_setuplinux_3_01_00_03.bin<br /> &lt;/code&gt;<br /> At this point, you will be prompted to agree to the software license and asked where to unpack the source files (something like ~/rowboat-android/ is probably appropriate). Now navigate to this directory and edit the user-modifiable fields in the ''Rules.make'' file. Here are some suggested values:<br /> &lt;code&gt;<br /> HOME=/home/&lt;username&gt;/rowboat-android/out/target/product/overo<br /> GRAPHICS_INSTALL_DIR=/home/&lt;username&gt;/rowboat-android/OMAP35x_Android_Graphics_SDK_3_01_00_03<br /> ANDROID_ROOT=$(HOME)/android_rootfs<br /> CSTOOL_DIR=/home/&lt;username&gt;/rowboat-android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/<br /> KERNEL_INSTALL_DIR=/home/&lt;username&gt;/rowboat-android/kernel<br /> &lt;/code&gt;<br /> Finally, we can build and install this code (N.B. these command are issued from the directory where we unpacked the source):<br /> &lt;code&gt;<br /> $ make -j8<br /> $ make install OMAPES=3.x<br /> &lt;/code&gt;<br /> More complete instructions are available [http://code.google.com/p/rowboat/wiki/ConfigureAndBuild#Install_the_Android_Graphics_SGX_SDK_on_Host_Machine here].<br /> <br /> === DSP Support ===<br /> Currently, this version does not support the C64+ DSP found on Overo boards with a OMAP3530 processor (FE, Fire, Water). To get this working, these two pages may be helpful:<br /> * http://code.google.com/p/rowboat/wiki/DSP<br /> * http://code.google.com/p/rowboat/wiki/DSPCodecs<br /> <br /> == Install ==<br /> It is easiest to boot Android from a microSD card. Follow the instructions [http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Creating-a-bootable-microSD-card/111.html here] to create a bootable microSD card with a recent MLO and U-boot from [http://www.sakoman.com/feeds/omap3/glibc/images/overo/ gumstix]. Also copy over the Android kernel and untar the root file system (requires root permissions) you have created:<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android<br /> $ cp kernel/arch/arm/boot/uImage /media/boot<br /> $ sudo tar xaf out/target/product/overo/rootfs.tar.bz2 --numeric-owner -C /media/rootfs<br /> &lt;/code&gt;<br /> NOTE: this assumes the FAT partition of your bootable microSD card is mounted at /media/boot and that the EXT3 partition is mounted at /media/rootfs---adjust as appropriate.<br /> <br /> HINT: The commands to package the root file system, install the SGX (if desired), and copy these over to a microSD card are readily script-able; if you plan on doing this more than once...<br /> <br /> ==Boot==<br /> The Android kernel requires some special parameters on boot. I have set these up in u-boot as follows (though this is certainly not the only way to do it):<br /> &lt;code&gt;<br /> # setenv anddisplay 'vram=8M omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=lcd43'<br /> # setenv andconsole 'console=ttyS2,115200n8 console=tty0 androidboot.console=ttyS2'<br /> # setenv androot 'root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait init=/init'<br /> # setenv andbootargs 'setenv bootargs mpurate=500 ${andconsole} ${androot} ${anddisplay}'<br /> # setenv andbootcmd 'mmc init; fatload mmc 0 ${loadaddr} uImage; run andbootargs; bootm ${loadaddr}'<br /> # saveenv<br /> &lt;/code&gt;<br /> To boot Android, just type ''run andbootcmd'' at the u-boot prompt.<br /> <br /> If you always want to boot into android, set and save ${andbootcmd} as your boot command i.e.<br /> &lt;code&gt;<br /> # setenv bootcmd ${andbootcmd}<br /> # saveenv<br /> &lt;/code&gt;<br /> <br /> NOTE:<br /> If you are using a 4.3&quot; LCD panel (Chestnut43, Palo43), use ''defaultdisplay=lcd43''; for a 3.5&quot; LCD panel (Palo35), use ''defaultdisplay=lcd35''; for an external DVI monitor (Tobi, Summit), use ''defaultdisplay=dvi''. Even if you are using an LCD panel, it is not necessary to change the ''omapfb.mode'' as this just sets up the framebuffer in the case that an external DVI monitor is used.<br /> <br /> == Using Android ==<br /> For touchscreen displays, you might like to replace the ''pointercal'' file found in ''~/rowboat-android/devices/gumstix/overo'' with one specific to the display you are using. To do this, boot your Gumstix + touchscreen with the standard Angstrom build, do the touchscreen calibration step, and then grab the ''/etc/pointercal'' file from the root file system.<br /> <br /> A mouse with a scroll-wheel can be attached to the USB Host port via a USB hub and used as buttons:<br /> * Right-click---back to home screen<br /> * Middle(scroll)-click---options<br /> * Scroll---scrolls<br /> Note that the mouse doesn't function like a regular pointer.<br /> <br /> Please help out by listing features that are not (and, equally important, '''are''' working):<br /> === Known Working ===<br /> <br /> === Known Failing ===<br /> <br /> == Help and Help Out ==<br /> These steps have mostly been taken from (and would hopefully be integrated with :)) the [[http://code.google.com/p/rowboat/wiki/Main rowboat-android]] wiki; look here for additional information. Other useful links include:<br /> * http://omapzoom.org/wiki/OMAP_Android_Main<br /> The mailing list for this project is quite valuable; check the archives for rowboat@googlegroups.com.<br /> <br /> Patches, suggestions and improvements are most welcome---please send to ash (at) gumstix.com.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=RowboatAndroid&diff=5089 2011-02-17T04:19:08Z

<p>Bmidgley: /* Build a Kernel */</p> <hr /> <div>== Android on Overo ==<br /> There are several ports of Android to Overo; one port is based off the Rowboat-Android project. This project is focused on creating a port of Android for the TI OMAP processors such as the OMAP3503 and OMAP3530 used on the Gumstix Overo boards. The steps described below explain how to get Android Froyo (2.2) running on an Overo. At the current time, there is no support for the DSP but the SGX drivers are supported.<br /> <br /> == Setup ==<br /> This section explains how to download the required code and build a kernel and root file system.<br /> <br /> === Checkout Sources ===<br /> Repo is a tool to manage multiple Git repositories. You can install it wherever you like but if you have administrator rights, you might find this convenient:<br /> &lt;code&gt;<br /> $ sudo curl http://android.git.kernel.org/repo &gt; repo<br /> $ sudo chmod a+x repo<br /> $ sudo mv repo /usr/bin/repo<br /> &lt;/code&gt;<br /> With Repo installed, grab the manifest file that describes all the git repositories we wish to fetch and then use 'repo sync' to get the latest and greatest source:<br /> &lt;code&gt;<br /> $ mkdir ~/rowboat-android<br /> $ cd ~/rowboat-android<br /> $ repo init -u git://gitorious.org/~ashcharles/rowboat/gumstix-manifest.git<br /> $ repo sync<br /> &lt;/code&gt;<br /> This (default) manifest pulls most of the repositories directly from the rowboat-android project but a few specific repositories (ahem, the kernel) have been cloned from this project and tweaked for the Overo.<br /> <br /> === Build a Kernel ===<br /> This would be a good time to apply any kernel patches.<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android/kernel<br /> $ patch -p1 &lt; ~/0001-added-palo43-pushbutton-and-led-support.patch<br /> $ patch -p1 &lt; ~/0001-Enable-ADB-on-IGEPv2-board.patch<br /> &lt;/code&gt;<br /> <br /> To build a kernel, follow [http://code.google.com/p/rowboat/wiki/ConfigureAndBuild#Build_kernel these] steps; you can use ''overo_android_defconfig'' to configure the kernel. E.g.<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android<br /> $ export PATH=${PWD}/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin:$PATH<br /> $ cd kernel<br /> $ make ARCH=arm overo_android_defconfig<br /> $ make ARCH=arm CROSS_COMPILE=arm-eabi- uImage -j8<br /> &lt;/code&gt;<br /> You should now have a shiny new 2.6.32 Overo kernel here ''arch/arm/boot/uImage''.<br /> <br /> === Build a Root File System ===<br /> Follow [http://code.google.com/p/rowboat/wiki/ConfigureAndBuild#Build_rootfs these] instructions to build a root file system using ''TARGET_PRODUCT=overo'' as the argument for make. E.g.<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android<br /> $ make TARGET_PRODUCT=overo -j8<br /> &lt;/code&gt;<br /> After a bit of a wait (read: an hour or two depending on your machine), you should have the ''root'' and ''system'' directories in the ''out/target/product/overo'' directory; we can combine these to make our final root file system:<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android/out/target/product/overo<br /> $ mkdir android_rootfs<br /> $ cp -r root/* android_rootfs<br /> $ cp -r system android_rootfs<br /> &lt;/code&gt;<br /> NOTE: Users wanting support for SGX hardware should skip to that section now before packaging their root file system.<br /> <br /> We use the built-in ''mktarball.sh'' utility to package our android_rootfs directory into a tarball wherein the files have appropriate (i.e. root) permissions; this means you need root permissions for this next step:<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android/out/target/product/overo<br /> $ sudo ../../../../build/tools/mktarball.sh ../../../host/linux-x86/bin/fs_get_stats android_rootfs . rootfs rootfs.tar.bz2<br /> &lt;/code&gt;<br /> You should now have a root file system tarball sitting here ''~/rowboat-android/out/target/product/overo/rootfs.tar.bz2''.<br /> <br /> === Getting SGX (Optional) ===<br /> The PowerVR SGX hardware found on Overo boards with a OMAP3530 processor (FE, Fire, Water) provides integrated graphics support; in particular, it seems to reduce flicker on displays attached to the Overo. It is necessary to add some extra libraries and drivers to the root file system to make use of this hardware. Grab the required code and build it:<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android<br /> $ git clone git://gitorious.org/rowboat/ti_android_sgx_sdk.git<br /> $ cd ti_android_sgx_sdk<br /> $ ./OMAP35x_Android_Graphics_SDK_setuplinux_3_01_00_03.bin<br /> &lt;/code&gt;<br /> At this point, you will be prompted to agree to the software license and asked where to unpack the source files (something like ~/rowboat-android/ is probably appropriate). Now navigate to this directory and edit the user-modifiable fields in the ''Rules.make'' file. Here are some suggested values:<br /> &lt;code&gt;<br /> HOME=/home/&lt;username&gt;/rowboat-android/out/target/product/overo<br /> GRAPHICS_INSTALL_DIR=/home/&lt;username&gt;/rowboat-android/OMAP35x_Android_Graphics_SDK_3_01_00_03<br /> ANDROID_ROOT=$(HOME)/android_rootfs<br /> CSTOOL_DIR=/home/&lt;username&gt;/rowboat-android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/<br /> KERNEL_INSTALL_DIR=/home/&lt;username&gt;/rowboat-android/kernel<br /> &lt;/code&gt;<br /> Finally, we can build and install this code (N.B. these command are issued from the directory where we unpacked the source):<br /> &lt;code&gt;<br /> $ make -j8<br /> $ make install OMAPES=3.x<br /> &lt;/code&gt;<br /> More complete instructions are available [http://code.google.com/p/rowboat/wiki/ConfigureAndBuild#Install_the_Android_Graphics_SGX_SDK_on_Host_Machine here].<br /> <br /> === DSP Support ===<br /> Currently, this version does not support the C64+ DSP found on Overo boards with a OMAP3530 processor (FE, Fire, Water). To get this working, these two pages may be helpful:<br /> * http://code.google.com/p/rowboat/wiki/DSP<br /> * http://code.google.com/p/rowboat/wiki/DSPCodecs<br /> <br /> == Install ==<br /> It is easiest to boot Android from a microSD card. Follow the instructions [http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Creating-a-bootable-microSD-card/111.html here] to create a bootable microSD card with a recent MLO and U-boot from [http://www.sakoman.com/feeds/omap3/glibc/images/overo/ gumstix]. Also copy over the Android kernel and untar the root file system (requires root permissions) you have created:<br /> &lt;code&gt;<br /> $ cd ~/rowboat-android<br /> $ cp kernel/arch/arm/boot/uImage /media/boot<br /> $ sudo tar xaf out/product/overo/rootfs.tar.bz2 --numeric-owner -C /media/rootfs<br /> &lt;/code&gt;<br /> NOTE: this assumes the FAT partition of your bootable microSD card is mounted at /media/boot and that the EXT3 partition is mounted at /media/rootfs---adjust as appropriate.<br /> <br /> HINT: The commands to package the root file system, install the SGX (if desired), and copy these over to a microSD card are readily script-able; if you plan on doing this more than once...<br /> <br /> ==Boot==<br /> The Android kernel requires some special parameters on boot. I have set these up in u-boot as follows (though this is certainly not the only way to do it):<br /> &lt;code&gt;<br /> # setenv anddisplay 'vram=8M omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=lcd43'<br /> # setenv andconsole 'console=ttyS2,115200n8 console=tty0 androidboot.console=ttyS2'<br /> # setenv androot 'root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait init=/init'<br /> # setenv andbootargs 'setenv bootargs mpurate=500 ${andconsole} ${androot} ${anddisplay}'<br /> # setenv andbootcmd 'mmc init; fatload mmc 0 ${loadaddr} uImage; run andbootargs; bootm ${loadaddr}'<br /> # saveenv<br /> &lt;/code&gt;<br /> To boot Android, just type ''run andbootcmd'' at the u-boot prompt.<br /> <br /> If you always want to boot into android, set and save ${andbootcmd} as your boot command i.e.<br /> &lt;code&gt;<br /> # setenv bootcmd ${andbootcmd}<br /> # saveenv<br /> &lt;/code&gt;<br /> <br /> NOTE:<br /> If you are using a 4.3&quot; LCD panel (Chestnut43, Palo43), use ''defaultdisplay=lcd43''; for a 3.5&quot; LCD panel (Palo35), use ''defaultdisplay=lcd35''; for an external DVI monitor (Tobi, Summit), use ''defaultdisplay=dvi''. Even if you are using an LCD panel, it is not necessary to change the ''omapfb.mode'' as this just sets up the framebuffer in the case that an external DVI monitor is used.<br /> <br /> == Using Android ==<br /> For touchscreen displays, you might like to replace the ''pointercal'' file found in ''~/rowboat-android/devices/gumstix/overo'' with one specific to the display you are using. To do this, boot your Gumstix + touchscreen with the standard Angstrom build, do the touchscreen calibration step, and then grab the ''/etc/pointercal'' file from the root file system.<br /> <br /> A mouse with a scroll-wheel can be attached to the USB Host port via a USB hub and used as buttons:<br /> * Right-click---back to home screen<br /> * Middle(scroll)-click---options<br /> * Scroll---scrolls<br /> Note that the mouse doesn't function like a regular pointer.<br /> <br /> Please help out by listing features that are not (and, equally important, '''are''' working):<br /> === Known Working ===<br /> <br /> === Known Failing ===<br /> <br /> == Help and Help Out ==<br /> These steps have mostly been taken from (and would hopefully be integrated with :)) the [[http://code.google.com/p/rowboat/wiki/Main rowboat-android]] wiki; look here for additional information. Other useful links include:<br /> * http://omapzoom.org/wiki/OMAP_Android_Main<br /> The mailing list for this project is quite valuable; check the archives for rowboat@googlegroups.com.<br /> <br /> Patches, suggestions and improvements are most welcome---please send to ash (at) gumstix.com.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=433 2008-04-08T03:20:02Z

<p>Bmidgley: </p> <hr /> <div>== Essentials ==<br /> <br /> Install the basic bluetooth stuff with<br /> <br /> ipkg install bluez-utils<br /> <br /> First off, I had to move the &quot;sleep 1&quot; from after &quot;sdptool add ...&quot; to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.<br /> <br /> == Networking: pan access point ==<br /> <br /> ipkg install dhcp-server<br /> <br /> /etc/dhcp/dhcpd.conf needs to contain (among other things it comes with):<br /> <br /> subnet 10.0.1.0 netmask 255.255.255.0 {<br /> range 10.0.1.180 10.0.1.199;<br /> option broadcast-address 10.0.1.255;<br /> option routers 10.0.1.1;<br /> option subnet-mask 255.255.255.0;<br /> }<br /> <br /> /etc/network/interfaces:<br /> <br /> allow-hotplug bnep0<br /> auto bnep0<br /> iface bnep0 inet static<br /> address 10.0.1.1<br /> netmask 255.255.255.0<br /> network 10.0.1.0<br /> <br /> /etc/default/bluetooth:<br /> <br /> PAND_ENABLE=true<br /> PAND_OPTIONS=&quot;--listen --role NAP&quot;<br /> <br /> /etc/network/if-up.d/btap<br /> <br /> #!/bin/sh<br /> iptables -A POSTROUTING -t nat -j MASQUERADE -s 10.0.1.0/24<br /> echo 1 &gt; /proc/sys/net/ipv4/ip_forward<br /> iptables -P FORWARD ACCEPT <br /> /etc/init.d/dhcp-server restart<br /> <br /> You may need to re-run pand or re-run the post-up script.<br /> <br /> == Networking: pan client ==<br /> <br /> /etc/network/interfaces:<br /> <br /> allow-hotplug bnep0<br /> auto bnep0<br /> iface bnep0 inet dhcp<br /> <br /> /etc/default/bluetooth:<br /> <br /> PAND_ENABLE=true<br /> PAND_OPTIONS=&quot;--role PANU --search&quot;<br /> <br /> For some reason pan can't find my access point so I have to hardcode it<br /> <br /> PAND_OPTIONS=&quot;-c 00:0B:5D:44:33:22&quot;<br /> <br /> == Dialup networking: server ==<br /> <br /> == Dialup networking: client ==<br /> <br /> == GPS repeater ==<br /> <br /> Install gpsd and configure it for your gps connection.<br /> <br /> In /etc/init.d/bluetooth, change <br /> <br /> $RFCOMM_EXEC -r watch 0 1 /sbin/getty -w -L rfcomm0 115200 vt100 &amp;<br /> to<br /> $RFCOMM_EXEC -r watch 0 1 sh -c &quot;gpspipe -r &gt;/dev/rfcomm0&quot; &amp;<br /> <br /> Unfortunately, advertising your gps uses the same sdp record as advertising your bluetooth console, so this knocks out your console. You can bring it back on an unadvertised channel:<br /> <br /> $RFCOMM_EXEC -r watch 1 2 /sbin/getty -w -L rfcomm1 115200 vt100 &amp;<br /> <br /> but then you'll have to be able to manually choose channel 2. That's not a problem from linux, but problematic for others.<br /> <br /> == Keyboard or mouse ==<br /> <br /> Put your keyboard or mouse in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay madplay<br /> <br /> Edit /etc/bluetooth/audio.service to enable autostart:<br /> <br /> [Bluetooth Service]<br /> Identifier=audio<br /> Name=Audio service<br /> Description=Bluetooth Audio service<br /> Autostart=true<br /> <br /> Reboot now if you had to change this.<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=432 2008-04-08T03:13:22Z

<p>Bmidgley: /* Networking: pan client */</p> <hr /> <div>== Essentials ==<br /> <br /> Install the basic bluetooth stuff with<br /> <br /> ipkg install bluez-utils<br /> <br /> First off, I had to move the &quot;sleep 1&quot; from after &quot;sdptool add ...&quot; to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.<br /> <br /> == Networking: pan access point ==<br /> <br /> ipkg install dhcp-server<br /> <br /> /etc/dhcp/dhcpd.conf needs to contain (among other things it comes with):<br /> <br /> subnet 10.0.1.0 netmask 255.255.255.0 {<br /> range 10.0.1.180 10.0.1.199;<br /> option broadcast-address 10.0.1.255;<br /> option routers 10.0.1.1;<br /> option subnet-mask 255.255.255.0;<br /> }<br /> <br /> /etc/network/interfaces:<br /> <br /> allow-hotplug bnep0<br /> auto bnep0<br /> iface bnep0 inet static<br /> address 10.0.1.1<br /> netmask 255.255.255.0<br /> network 10.0.1.0<br /> <br /> /etc/default/bluetooth:<br /> <br /> PAND_ENABLE=true<br /> PAND_OPTIONS=&quot;--listen --role NAP&quot;<br /> <br /> /etc/network/if-up.d/btap<br /> <br /> #!/bin/sh<br /> iptables -A POSTROUTING -t nat -j MASQUERADE -s 10.0.1.0/24<br /> echo 1 &gt; /proc/sys/net/ipv4/ip_forward<br /> iptables -P FORWARD ACCEPT <br /> /etc/init.d/dhcp-server restart<br /> <br /> You may need to re-run pand or re-run the post-up script.<br /> <br /> == Networking: pan client ==<br /> <br /> /etc/network/interfaces:<br /> <br /> allow-hotplug bnep0<br /> auto bnep0<br /> iface bnep0 inet dhcp<br /> <br /> /etc/default/bluetooth:<br /> <br /> PAND_ENABLE=true<br /> PAND_OPTIONS=&quot;--role PANU --search&quot;<br /> <br /> For some reason pan can't find my access point so I have to hardcode it<br /> <br /> PAND_OPTIONS=&quot;-c 00:0B:5D:44:33:22&quot;<br /> <br /> == Dialup networking: server ==<br /> <br /> == Dialup networking: client ==<br /> <br /> == GPS repeater ==<br /> <br /> Install gpsd and configure it for your gps connection.<br /> <br /> In /etc/init.d/bluetooth, change <br /> <br /> $RFCOMM_EXEC -r watch 0 1 /sbin/getty -w -L rfcomm0 115200 vt100 &amp;<br /> to<br /> $RFCOMM_EXEC -r watch 0 1 sh -c &quot;gpspipe -r &gt;/dev/rfcomm0&quot; &amp;<br /> <br /> Unfortunately, advertising your gps uses the same sdp record as advertising your bluetooth console, so this knocks out your console. You can bring it back on an unadvertised channel:<br /> <br /> $RFCOMM_EXEC -r watch 1 2 /sbin/getty -w -L rfcomm1 115200 vt100 &amp;<br /> <br /> but then you'll have to be able to manually choose channel 2. That's not a problem from linux, but problematic for others.<br /> <br /> == Keyboard ==<br /> <br /> Put your keyboard in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay madplay<br /> <br /> Edit /etc/bluetooth/audio.service to enable autostart:<br /> <br /> [Bluetooth Service]<br /> Identifier=audio<br /> Name=Audio service<br /> Description=Bluetooth Audio service<br /> Autostart=true<br /> <br /> Reboot now if you had to change this.<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=431 2008-04-08T03:10:14Z

<p>Bmidgley: /* Networking: pan access point */</p> <hr /> <div>== Essentials ==<br /> <br /> Install the basic bluetooth stuff with<br /> <br /> ipkg install bluez-utils<br /> <br /> First off, I had to move the &quot;sleep 1&quot; from after &quot;sdptool add ...&quot; to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.<br /> <br /> == Networking: pan access point ==<br /> <br /> ipkg install dhcp-server<br /> <br /> /etc/dhcp/dhcpd.conf needs to contain (among other things it comes with):<br /> <br /> subnet 10.0.1.0 netmask 255.255.255.0 {<br /> range 10.0.1.180 10.0.1.199;<br /> option broadcast-address 10.0.1.255;<br /> option routers 10.0.1.1;<br /> option subnet-mask 255.255.255.0;<br /> }<br /> <br /> /etc/network/interfaces:<br /> <br /> allow-hotplug bnep0<br /> auto bnep0<br /> iface bnep0 inet static<br /> address 10.0.1.1<br /> netmask 255.255.255.0<br /> network 10.0.1.0<br /> <br /> /etc/default/bluetooth:<br /> <br /> PAND_ENABLE=true<br /> PAND_OPTIONS=&quot;--listen --role NAP&quot;<br /> <br /> /etc/network/if-up.d/btap<br /> <br /> #!/bin/sh<br /> iptables -A POSTROUTING -t nat -j MASQUERADE -s 10.0.1.0/24<br /> echo 1 &gt; /proc/sys/net/ipv4/ip_forward<br /> iptables -P FORWARD ACCEPT <br /> /etc/init.d/dhcp-server restart<br /> <br /> You may need to re-run pand or re-run the post-up script.<br /> <br /> == Networking: pan client == <br /> <br /> == Dialup networking: server ==<br /> <br /> == Dialup networking: client ==<br /> <br /> == GPS repeater ==<br /> <br /> Install gpsd and configure it for your gps connection.<br /> <br /> In /etc/init.d/bluetooth, change <br /> <br /> $RFCOMM_EXEC -r watch 0 1 /sbin/getty -w -L rfcomm0 115200 vt100 &amp;<br /> to<br /> $RFCOMM_EXEC -r watch 0 1 sh -c &quot;gpspipe -r &gt;/dev/rfcomm0&quot; &amp;<br /> <br /> Unfortunately, advertising your gps uses the same sdp record as advertising your bluetooth console, so this knocks out your console. You can bring it back on an unadvertised channel:<br /> <br /> $RFCOMM_EXEC -r watch 1 2 /sbin/getty -w -L rfcomm1 115200 vt100 &amp;<br /> <br /> but then you'll have to be able to manually choose channel 2. That's not a problem from linux, but problematic for others.<br /> <br /> == Keyboard ==<br /> <br /> Put your keyboard in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay madplay<br /> <br /> Edit /etc/bluetooth/audio.service to enable autostart:<br /> <br /> [Bluetooth Service]<br /> Identifier=audio<br /> Name=Audio service<br /> Description=Bluetooth Audio service<br /> Autostart=true<br /> <br /> Reboot now if you had to change this.<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=430 2008-04-08T03:09:03Z

<p>Bmidgley: /* Networking: pan access point */</p> <hr /> <div>== Essentials ==<br /> <br /> Install the basic bluetooth stuff with<br /> <br /> ipkg install bluez-utils<br /> <br /> First off, I had to move the &quot;sleep 1&quot; from after &quot;sdptool add ...&quot; to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.<br /> <br /> == Networking: pan access point ==<br /> <br /> ipkg install dhcp-server<br /> <br /> /etc/dhcp/dhcpd.conf:<br /> <br /> subnet 10.0.1.0 netmask 255.255.255.0 {<br /> range 10.0.1.180 10.0.1.199;<br /> option broadcast-address 10.0.1.255;<br /> option routers 10.0.1.1;<br /> option subnet-mask 255.255.255.0;<br /> }<br /> <br /> /etc/network/interfaces:<br /> <br /> allow-hotplug bnep0<br /> auto bnep0<br /> iface bnep0 inet static<br /> address 10.0.1.1<br /> netmask 255.255.255.0<br /> network 10.0.1.0<br /> <br /> /etc/default/bluetooth:<br /> <br /> PAND_ENABLE=true<br /> PAND_OPTIONS=&quot;--listen --role NAP&quot;<br /> <br /> /etc/network/if-up.d/btap<br /> <br /> #!/bin/sh<br /> iptables -A POSTROUTING -t nat -j MASQUERADE -s 10.0.1.0/24<br /> echo 1 &gt; /proc/sys/net/ipv4/ip_forward<br /> iptables -P FORWARD ACCEPT <br /> /etc/init.d/dhcp-server restart<br /> <br /> You may need to re-run pand or re-run the post-up script.<br /> <br /> == Networking: pan client == <br /> <br /> == Dialup networking: server ==<br /> <br /> == Dialup networking: client ==<br /> <br /> == GPS repeater ==<br /> <br /> Install gpsd and configure it for your gps connection.<br /> <br /> In /etc/init.d/bluetooth, change <br /> <br /> $RFCOMM_EXEC -r watch 0 1 /sbin/getty -w -L rfcomm0 115200 vt100 &amp;<br /> to<br /> $RFCOMM_EXEC -r watch 0 1 sh -c &quot;gpspipe -r &gt;/dev/rfcomm0&quot; &amp;<br /> <br /> Unfortunately, advertising your gps uses the same sdp record as advertising your bluetooth console, so this knocks out your console. You can bring it back on an unadvertised channel:<br /> <br /> $RFCOMM_EXEC -r watch 1 2 /sbin/getty -w -L rfcomm1 115200 vt100 &amp;<br /> <br /> but then you'll have to be able to manually choose channel 2. That's not a problem from linux, but problematic for others.<br /> <br /> == Keyboard ==<br /> <br /> Put your keyboard in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay madplay<br /> <br /> Edit /etc/bluetooth/audio.service to enable autostart:<br /> <br /> [Bluetooth Service]<br /> Identifier=audio<br /> Name=Audio service<br /> Description=Bluetooth Audio service<br /> Autostart=true<br /> <br /> Reboot now if you had to change this.<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=366 2008-03-23T05:10:01Z

<p>Bmidgley: </p> <hr /> <div>== Essentials ==<br /> <br /> Install the basic bluetooth stuff with<br /> <br /> ipkg install bluez-utils<br /> <br /> First off, I had to move the &quot;sleep 1&quot; from after &quot;sdptool add ...&quot; to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.<br /> <br /> == Networking: pan access point ==<br /> <br /> == Networking: pan client == <br /> <br /> == Dialup networking: server ==<br /> <br /> == Dialup networking: client ==<br /> <br /> == GPS repeater ==<br /> <br /> Install gpsd and configure it for your gps connection.<br /> <br /> In /etc/init.d/bluetooth, change <br /> <br /> $RFCOMM_EXEC -r watch 0 1 /sbin/getty -w -L rfcomm0 115200 vt100 &amp;<br /> to<br /> $RFCOMM_EXEC -r watch 0 1 sh -c &quot;gpspipe -r &gt;/dev/rfcomm0&quot; &amp;<br /> <br /> Unfortunately, advertising your gps uses the same sdp record as advertising your bluetooth console, so this knocks out your console. You can bring it back on an unadvertised channel:<br /> <br /> $RFCOMM_EXEC -r watch 1 2 /sbin/getty -w -L rfcomm1 115200 vt100 &amp;<br /> <br /> but then you'll have to be able to manually choose channel 2. That's not a problem from linux, but problematic for others.<br /> <br /> == Keyboard ==<br /> <br /> Put your keyboard in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay madplay<br /> <br /> Edit /etc/bluetooth/audio.service to enable autostart:<br /> <br /> [Bluetooth Service]<br /> Identifier=audio<br /> Name=Audio service<br /> Description=Bluetooth Audio service<br /> Autostart=true<br /> <br /> Reboot now if you had to change this.<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=365 2008-03-23T05:09:25Z

<p>Bmidgley: </p> <hr /> <div>== Essentials ==<br /> <br /> Install the basic bluetooth stuff with<br /> <br /> ipkg install bluez-utils<br /> <br /> First off, I had to move the &quot;sleep 1&quot; from after &quot;sdptool add ...&quot; to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.<br /> <br /> == Networking: pan access point ==<br /> <br /> == Networking: pan client == <br /> <br /> == Dialup networking server ==<br /> <br /> == Dialup networking client ==<br /> <br /> == GPS repeater ==<br /> <br /> Install gpsd and configure it for your gps connection.<br /> <br /> In /etc/init.d/bluetooth, change <br /> <br /> $RFCOMM_EXEC -r watch 0 1 /sbin/getty -w -L rfcomm0 115200 vt100 &amp;<br /> to<br /> $RFCOMM_EXEC -r watch 0 1 sh -c &quot;gpspipe -r &gt;/dev/rfcomm0&quot; &amp;<br /> <br /> Unfortunately, advertising your gps uses the same sdp record as advertising your bluetooth console, so this knocks out your console. You can bring it back on an unadvertised channel:<br /> <br /> $RFCOMM_EXEC -r watch 1 2 /sbin/getty -w -L rfcomm1 115200 vt100 &amp;<br /> <br /> but then you'll have to be able to manually choose channel 2. That's not a problem from linux, but problematic for others.<br /> <br /> == Keyboard ==<br /> <br /> Put your keyboard in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay madplay<br /> <br /> Edit /etc/bluetooth/audio.service to enable autostart:<br /> <br /> [Bluetooth Service]<br /> Identifier=audio<br /> Name=Audio service<br /> Description=Bluetooth Audio service<br /> Autostart=true<br /> <br /> Reboot now if you had to change this.<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=364 2008-03-23T05:08:26Z

<p>Bmidgley: /* GPS repeater */</p> <hr /> <div>== Essentials ==<br /> <br /> Install the basic bluetooth stuff with<br /> <br /> ipkg install bluez-utils<br /> <br /> First off, I had to move the &quot;sleep 1&quot; from after &quot;sdptool add ...&quot; to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.<br /> <br /> == Networking ==<br /> <br /> == Dialup networking ==<br /> <br /> == GPS repeater ==<br /> <br /> Install gpsd and configure it for your gps connection.<br /> <br /> In /etc/init.d/bluetooth, change <br /> <br /> $RFCOMM_EXEC -r watch 0 1 /sbin/getty -w -L rfcomm0 115200 vt100 &amp;<br /> to<br /> $RFCOMM_EXEC -r watch 0 1 sh -c &quot;gpspipe -r &gt;/dev/rfcomm0&quot; &amp;<br /> <br /> Unfortunately, advertising your gps uses the same sdp record as advertising your bluetooth console, so this knocks out your console. You can bring it back on an unadvertised channel:<br /> <br /> $RFCOMM_EXEC -r watch 1 2 /sbin/getty -w -L rfcomm1 115200 vt100 &amp;<br /> <br /> but then you'll have to be able to manually choose channel 2. That's not a problem from linux, but problematic for others.<br /> <br /> == Keyboard ==<br /> <br /> Put your keyboard in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay madplay<br /> <br /> Edit /etc/bluetooth/audio.service to enable autostart:<br /> <br /> [Bluetooth Service]<br /> Identifier=audio<br /> Name=Audio service<br /> Description=Bluetooth Audio service<br /> Autostart=true<br /> <br /> Reboot now if you had to change this.<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=363 2008-03-23T05:07:54Z

<p>Bmidgley: /* GPS repeater */</p> <hr /> <div>== Essentials ==<br /> <br /> Install the basic bluetooth stuff with<br /> <br /> ipkg install bluez-utils<br /> <br /> First off, I had to move the &quot;sleep 1&quot; from after &quot;sdptool add ...&quot; to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.<br /> <br /> == Networking ==<br /> <br /> == Dialup networking ==<br /> <br /> == GPS repeater ==<br /> <br /> Install gpsd and configure it for your gps connection.<br /> <br /> In /etc/init.d/bluetooth, change <br /> <br /> $RFCOMM_EXEC -r watch 0 1 /sbin/getty -w -L rfcomm0 115200 vt100 &amp;<br /> to<br /> $RFCOMM_EXEC -r watch 0 1 sh -c &quot;gpspipe -r &gt;/dev/rfcomm0&quot; &amp;<br /> <br /> Unfortunately, advertising your gps uses the same sdp record as advertising your bluetooth console, so this knocks out your console. You can bring it back on an unadvertised channel:<br /> <br /> $RFCOMM_EXEC -r watch 1 2 /sbin/getty -w -L rfcomm1 115200 vt100 &amp;<br /> <br /> but then you'll have to be able to manually choose channel 2. That's not a problem from linux, but problematic for others.<br /> <br /> == Keyboard ==<br /> <br /> Put your keyboard in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay madplay<br /> <br /> Edit /etc/bluetooth/audio.service to enable autostart:<br /> <br /> [Bluetooth Service]<br /> Identifier=audio<br /> Name=Audio service<br /> Description=Bluetooth Audio service<br /> Autostart=true<br /> <br /> Reboot now if you had to change this.<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=360 2008-03-21T04:35:55Z

<p>Bmidgley: /* Essentials */</p> <hr /> <div>== Essentials ==<br /> <br /> Install the basic bluetooth stuff with<br /> <br /> ipkg install bluez-utils<br /> <br /> First off, I had to move the &quot;sleep 1&quot; from after &quot;sdptool add ...&quot; to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.<br /> <br /> == Networking ==<br /> <br /> == Dialup networking ==<br /> <br /> == GPS repeater ==<br /> <br /> == Keyboard ==<br /> <br /> Put your keyboard in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay alsa-utils-arecord madplay<br /> <br /> Edit /etc/bluetooth/audio.service to enable autostart:<br /> <br /> [Bluetooth Service]<br /> Identifier=audio<br /> Name=Audio service<br /> Description=Bluetooth Audio service<br /> Autostart=true<br /> <br /> Reboot now if you had to change this.<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=359 2008-03-21T04:29:10Z

<p>Bmidgley: /* High-fidelity audio */</p> <hr /> <div>== Essentials ==<br /> <br /> First off, I had to move the &quot;sleep 1&quot; from after &quot;sdptool add ...&quot; to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.<br /> <br /> Install the basic bluetooth stuff with<br /> <br /> ipkg install bluez-utils<br /> <br /> == Networking ==<br /> <br /> == Dialup networking ==<br /> <br /> == GPS repeater ==<br /> <br /> == Keyboard ==<br /> <br /> Put your keyboard in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay alsa-utils-arecord madplay<br /> <br /> Edit /etc/bluetooth/audio.service to enable autostart:<br /> <br /> [Bluetooth Service]<br /> Identifier=audio<br /> Name=Audio service<br /> Description=Bluetooth Audio service<br /> Autostart=true<br /> <br /> Reboot now if you had to change this.<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=358 2008-03-21T04:28:23Z

<p>Bmidgley: /* High-fidelity audio */</p> <hr /> <div>== Essentials ==<br /> <br /> First off, I had to move the &quot;sleep 1&quot; from after &quot;sdptool add ...&quot; to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.<br /> <br /> Install the basic bluetooth stuff with<br /> <br /> ipkg install bluez-utils<br /> <br /> == Networking ==<br /> <br /> == Dialup networking ==<br /> <br /> == GPS repeater ==<br /> <br /> == Keyboard ==<br /> <br /> Put your keyboard in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay alsa-utils-arecord madplay<br /> <br /> Edit /etc/bluetooth/audio.service to enable autostart:<br /> <br /> [Bluetooth Service]<br /> Identifier=audio<br /> Name=Audio service<br /> Description=Bluetooth Audio service<br /> Autostart=true<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=357 2008-03-21T04:27:20Z

<p>Bmidgley: </p> <hr /> <div>== Essentials ==<br /> <br /> First off, I had to move the &quot;sleep 1&quot; from after &quot;sdptool add ...&quot; to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.<br /> <br /> Install the basic bluetooth stuff with<br /> <br /> ipkg install bluez-utils<br /> <br /> == Networking ==<br /> <br /> == Dialup networking ==<br /> <br /> == GPS repeater ==<br /> <br /> == Keyboard ==<br /> <br /> Put your keyboard in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay alsa-utils-arecord madplay<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=356 2008-03-21T04:26:35Z

<p>Bmidgley: </p> <hr /> <div>First off, I had to move the &quot;sleep 1&quot; from after &quot;sdptool add ...&quot; to before the sdptool command. The startup script seemed to be failing to run to completion before I did that.<br /> <br /> == Networking ==<br /> <br /> == Dialup networking ==<br /> <br /> == GPS repeater ==<br /> <br /> == Keyboard ==<br /> <br /> Put your keyboard in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay alsa-utils-arecord madplay<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=355 2008-03-21T04:23:58Z

<p>Bmidgley: </p> <hr /> <div>== Networking ==<br /> <br /> == Dialup networking ==<br /> <br /> == GPS repeater ==<br /> <br /> == Keyboard ==<br /> <br /> Put your keyboard in pairing mode and run:<br /> <br /> hidd --search<br /> <br /> The keyboard should connect and on subsequent runs it will reconnect automatically if you boot up with this in /etc/default/bluetooth<br /> <br /> HIDD_ENABLE=true<br /> HIDD_OPTIONS=&quot;--master --server&quot;<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay alsa-utils-arecord madplay<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=354 2008-03-21T04:13:20Z

<p>Bmidgley: /* High-fidelity audio */</p> <hr /> <div>== Networking ==<br /> <br /> == Dialup networking ==<br /> <br /> == GPS repeater ==<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay alsa-utils-arecord madplay<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect. A few itech headsets need &quot;8888&quot; but most need &quot;0000&quot; for the pin:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=353 2008-03-21T04:12:06Z

<p>Bmidgley: /* Voice audio */</p> <hr /> <div>== Networking ==<br /> <br /> == Dialup networking ==<br /> <br /> == GPS repeater ==<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and a USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay alsa-utils-arecord madplay<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=352 2008-03-21T04:11:37Z

<p>Bmidgley: /* High-fidelity audio */</p> <hr /> <div>== Networking ==<br /> <br /> == Dialup networking ==<br /> <br /> == GPS repeater ==<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and an external USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or any brand of USB adapter if you have a vx board.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay alsa-utils-arecord madplay<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=351 2008-03-21T04:05:56Z

<p>Bmidgley: </p> <hr /> <div><br /> == Networking ==<br /> <br /> == Dialup networking ==<br /> <br /> == GPS repeater ==<br /> <br /> == Voice audio ==<br /> <br /> Currently the way to use voice over bluetooth requires a vx board and an external USB bluetooth adapter with a CSR chip in it.<br /> <br /> == High-fidelity audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or (for a vx board) a USB adapter.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay alsa-utils-arecord madplay<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=350 2008-03-21T04:01:45Z

<p>Bmidgley: </p> <hr /> <div>== High-fidelity Bluetooth audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or (for a vx board) a USB adapter.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay alsa-utils-arecord madplay<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.<br /> <br /> <br /> == Debugging connection problems ==<br /> <br /> The best way to figure out what is happening is to use hcidump.<br /> <br /> ipkg install bluez-hcidump<br /> <br /> In a separate window, or in the background, start the dump:<br /> <br /> hcidump -XV<br /> <br /> And then in another window, try out your bluetooth command that isn't working. hcidump output is very verbose, but you'll probably be able to zero in on the issue by studying it a little.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=349 2008-03-21T03:54:29Z

<p>Bmidgley: /* High-fidelity Bluetooth audio */</p> <hr /> <div>== High-fidelity Bluetooth audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or (for a vx board) a USB adapter.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay alsa-utils-arecord madplay<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=348 2008-03-21T03:53:32Z

<p>Bmidgley: /* High-fidelity Bluetooth audio */</p> <hr /> <div>== High-fidelity Bluetooth audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or (for a vx board) a USB adapter.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay alsa-utils-arecord madplay<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.</div>

Bmidgley https://wiki.gumstix.com/index.php?title=Category:How_to_-_bluetooth&diff=347 2008-03-21T03:53:02Z

<p>Bmidgley: </p> <hr /> <div>== High-fidelity Bluetooth audio ==<br /> <br /> You can use A2DP with either the internal bluetooth adapter (model 08 or newer) or (for a vx board) a USB adapter.<br /> <br /> Install the packages you'll need:<br /> <br /> ipkg install bluez-utils bluez-utils-alsa alsa-utils-aplay madplay<br /> <br /> You'll likely need the passkey agent running, at least the first time you connect:<br /> <br /> passkey-agent --default 0000 &amp;<br /> <br /> put your headset in pairing mode. Usually this means starting from off and holding the power button down until it flashes. Then find the headset's address:<br /> <br /> hcitool scan<br /> <br /> edit your /etc/asound.conf with an adapter for bluetooth with the address you just found. My headset is made by itech, so I name the adapter after it:<br /> <br /> pcm.itech {<br /> type bluetooth<br /> device &quot;00:0D:3C:8A:13:06&quot;<br /> }<br /> <br /> now try playing something to it:<br /> <br /> madplay song.mp3 -r 44100 --output=wave:- | aplay -D itech<br /> <br /> you can also live-encode the line in source to a2dp:<br /> <br /> arecord -c 2 -f s16 -r 44100 | aplay -D itech<br /> <br /> unfortunately for live encoding, the delay is pretty bad and for some reason I can never get stereo audio from the line-in source.</div>

Bmidgley