Bluetooth failure on Nexus 9 with Flounder built from source

[john oliver]

Hi moderator ..  I started an earlier thread with the wrong title " Bluetooth failure on Nexus 7 with Flounder built from source" ..  https://groups.google.com/forum/#!topic/android-building/MPEpwUZPExA

It should have said  "Bluetooth failure on Nexus 9 with Flounder built from source". Can I please request that it be changed? 

[john oliver]

As I described earlier, see above link, I wasn't able to start bluetooth on a Nexus 9 (flounder)  with my Lollipop AOSP built from source, due to failure to talk to the hardware. It seems that the flounder config is either not fully rolled out yet or hasn't been fully tested, since:

1) the lunch menu doesn't contain an entry for flounder ( requires add_lunch_combo aosp_flounder64-userdebug) 

2) Its libbt config file seems to be incomplete:  ( hardware/broadcom/libbt/include/vnd_flounder.txt )

After manually editing the config file for 2) to point to the correct device ( /dev/ttyTHS2) and firmware location ("/vendor/firmware)  I am now able to see bluetooth start up successfully on a Nexus 9 running the AOSP built from source.

-johno

[john oliver]

.. and although the original /vendor/lib/libbtvendor.so in the factory image must surely point to the correct firmware, there must be an incompatibility somewhere which prevents the user debug build from loading/using that version of the library.

-johno

[Paul Beeler]

I'm really surprised at the lack of support on these forums. I came here in search of finding a solution for not being able to build aosp_flounder-user (which does not include all of the debugging tools). I was met with various errors that I have no idea what they mean or how to fix them. One of them seems to be related to the kernel as it was complaining about a missing KERNEL_OBJ/usr. I have already compiled my own prebuilt kernel and placed it in device/htc/flounder-kernel
The only usr directory I found was in the kernel source but apparently since I'm using a prebuilt kernel it shouldn't need source files! After I created the directory out/target/product/flounder/obj/KERNEL/OBJ I copied the usr directory from the kernel source. Yet I'm met with another error about missing updater to create a ota package...

As John said the source seems completely broken or incomplete on both user and userdebug building. Any help would be appreciated, regards.

[Glenn Kasten]

It's normal for top-of-tree on master to occasionally be broken temporarily.

For more stability use a named branch or tag.

Regarding lack of support, this is a volunteer forum,

so the more we all contribute positively, the better it will become.

[Paul Beeler]

Hi Glen thanks for the response.  Although it's not really pertaining to the issues described here.  You are correct in that I didn't specify which branch or tag I was building on.  I am attempting to build from the latest lollipop release tag https://android.googlesource.com/platform/manifest/+/android-5.0.2_r1

I realize this is a slightly different release version then the original poster here is using.  Although I'm still curious why I've encountered these strange errors.  AOSP has been around a long time, and this is the first time I've ever seen a nexus source just simply not work in certain building situations such as this.  As you said master branch is normally broken so I'll wait for a updated source release that will hopefully solve these issues!

--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-buildi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[R Herbster]

Hey, I still had to do a small change. I created the file /etc/bluetooth/bt_vendor.conf and added the following lines:

UartPort = /dev/ttyTHS2
FwPatchFilePath = /vendor/firmware/

Now, everything works just fine :-) and thanks for your solution!

-Raul