Hi there, and good luck with your venture...

In general, all the work that is described in the tutorial that you are following, is about setting up the AOSP interface layer between the Ubuntu Touch image and your device. (Maybe this can be more clearly seen by the deploying guide, here https://wiki.ubuntu.com/Touch/Deploying , but this is for much later). As such, the procedure is very close to the work of bringing AOSP to a device... and there is a lot of support for that in popular forums, such as xda, where the user base is much larger, and you will be getting a lot more feedback (I presume).

Now, about your question, a quick search with mr. google says things related to mixup between 64bit and 32bit packages. Your problem is it is more like setting up the development environment properly than anything else...

Hello everyone,

So I am trying to port ubuntu touch to a samsung galaxy tab S. In particular, I am at the point where I have found the git repository of someone who has ported cynogenmode to the same device, and I am trying to put together the /hardware and /vendor structure in the /phablet tree that is asked in the ubuntu touch porting guide.

I have 2 issues (most prob. many more, but those are the ones I see right now) :
a ) The /vendor folder. I have actually downloaded the AOSP repository as well, and I cannot see the vendor folder in the tree. Am I missing something? I understand that I am supposed to put in there binaries of proprietary drivers (correct me if I'm wrong). I have the list of those files from the cynogenmod port, and I have copied these binaries and compiled libs from my device, however, I have no idea where to put them (feel free to through anything nasty at me here :D)

b ) Inside the hardware folder I already see samsung_slsi/exynos5. I suppose this is great, because I found out that my device runs on an exynos5. On the other hand... where am I supposed to put the /audio /camera folders ? inside the pre-existing /samsung_slsi ? or I create another /samsung folder ? The guide says be faithful to the AOSP hierarchy.... however I don't see this being clear at this poing.

Thanks in advance for any input!,
Panagiotis