JohnHammond
/
asteroidos.org
mirror of https://github.com/JohnHammond/asteroidos.org.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update the Porting Guide wiki page

master
Florent Revest 2017-07-09 15:01:43 +01:00
parent 9fd9785e91
commit cf2d82deb8
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pages/wiki/porting-guide.hbs
View File

@ -47,8 +47,8 @@ layout: documentation
<div class="page-header">
<h1 id="usb">USB</h1>
</div>
<p>If you have your AsteroidOS system running, you will want to get a shell access to it with adb over USB. Try to run adb devices&nbsp;from your computer when your watch has been booted for a few seconds and check if you see your device. If you don’t, you may have a problem with your USB setup.</p>
<p>First of all, try to replicate the config of your Android Wear’s init scripts in <a href="https://github.com/AsteroidOS/meta-dory-hybris/blob/master/recipes-core/initrdscripts/initramfs-boot-android/init.sh#L26">your ramdisk’s init script</a>. Once you’re sure the USB config is the same, you should try to run <a href="https://github.com/AsteroidOS/meta-dory-hybris/blob/master/recipes-core/initrdscripts/initramfs-boot-android/init.sh#L52">adbd from your ramdisk</a> instead of the rootfs, if it solves the problem you may have an issue with usb_moded not starting adbd properly.</p>
<p>If you have your AsteroidOS system running, you will want to get a shell access to it with adb or SSH over USB. Use <i>dmesg -w</i> on your computer to check if your watch appears after having been booted for a few seconds. If you don’t see your watch, you may have a problem with your USB setup.</p>
<p>First of all, try to replicate the config of your Android Wear’s init scripts in <a href="https://github.com/AsteroidOS/meta-dory-hybris/blob/master/recipes-core/initrdscripts/initramfs-boot-android/init.sh#L26">your ramdisk’s init script</a>. Once you’re sure the USB config is the same, you should try to run <a href="https://github.com/AsteroidOS/meta-dory-hybris/blob/master/recipes-core/initrdscripts/initramfs-boot-android/init.sh#L52">adbd from your ramdisk</a> instead of the rootfs, if it solves the problem you may have an issue with usb_moded not starting adbd or RNDIS properly.</p>
<p>If the problem is the same, you may have a problem with your kernel’s config or drivers. First of all, make sure CONFIG_USB_G_ANDROID is still enabled in the generated build/tmp-glibc/work/XXX-oe-linux-gnueabi/linux-XXX/*/git/.config as it is quite common to find bitbake removing this option. If the option is still there, your kernel may need special patches.</p>
<div class="page-header">
<h1 id="display">Display</h1>