Newbie struggles: getting started with Android

Developer Tools Core SDK Android
1

Hello,

I just got a Leia device (LDP-20WHW1.0), and I am trying to understand the ecosystem, but there is a lot of controversial information - or I have a lot of misunderstanding. Could you enlighten me?

The display with the built-in apps is amazing, but I want to build the 3D display into my app. I am basically a web developer; I have just a little knowledge of native Android development. I have a SvelteKit + Capacitor Android app, which has a functionality to view, rotate and interact with a 3D model (it could also run in the browser, of course). I want to keep it simple as I am not expert of it, and I don’t want to be. I guess for the simplest way on the JavaScript side, I “just” need to use some real-time conversion on the screen in the Android native code to get the 3D effect that the Leia device supports.

01.: Correct SDK

As I see in the Developer Docs sidebar

I guess I can use Core Native SDK and Android Media SDK.

But in the SDK page, there is no Android Media SDK:

I found “LeiaSR SDK”, which is referenced by this documentation:

which goes to this repository:

When I download and open the docs, I see it’s the “CNSDK” 0.10.31 and it has a License menu item in the sidebar which says: “CNSDK requires a valid license key. Contact Leia Support to get one.”

After a few minutes I found this online documentation:

It’s SRSDK 0.10.39 and the Licensing menu option is missing.

??? Is it CRSDK or SRSDK now? Which is the correct version? Is it the same and renamed, or different? What is the difference, and what should I use? How is possible that LeiaSR-Android-Releases contains CNSDK, but the LeiaSR-Android-Doxygen-Documentation talks about SRSDK? Which is the correct one? Why we need to licence them?

02.: Android Media SDK

In this page I see Android Media SDK.

I also checked the repos, and I found this

which references to the MediaSDK doc in readme.md
https://docs.leialoft.com/leia-android-media-sdk/
which is not found.

Also this repository

Which has the issue for unable to locate dependent file

on Sep 8, 2023 reply: “You are a bit early. We are getting ready for the launch of this tool on our website, along with all needed dependencies.”

So What is this Android Media SDK exactly? Is it under development or all of this information is deprecated? If deprecated, why is some reference still avaliable for it? The SDK is not included in the example repository, and I can’t find where should I get it. Is this Android Media SDK the one I should use for Android 3D, or the CNSDK / SRSDK?

03.: NeurD

As I see the NeurD is the lib that “convert media files from 2D to 3D”.
03.: So is it not the part of the AndroidMediaSDK/CNSDK/SRSDK? I need to build it all together?

Summary

So please give some comprehensive informations about the ecosystem, because I can’t understand by the controversial docs.

Also, in my case, what do you think how should I implement the 3D view to my software? The native Android app is basically a webview, and the code inside is a SvelteKit + Capacitor webapp which interacts with the native Capacitor plugins for native capabilities, like saving a file to the disk. So what I want is to add an extra layer of display, which converts the 2D view to the 3D panel. I also want to turn this effect on and off, because not my whole application is 3D, just there is a 3D model viewer.

A step-by-step tutorial for newbies would be also nice, but I can’t find any. Do you have any?

Thank you all of your help!

1 Like
2

I’m sorry it’s so confusing. I wish that I could be of more help. But I’ve have limited success with three.js. And gave up. It’s such a great platform but without a way to experience the rest of the world on the web as stereo (through an enabled browser) I doesn’t seem like things are going anywhere. It’s just not possible to expect every website or web app to update their code to display pages on the lumepad. We should be able to hit the VR button like you do with other devices.

I’ll follow this hoping someone posts a solution.

3

What I also don’t understand is:

  • if the AI chip is built-in to the tablet
  • and the NeurD software is there
  • and it is a custom Android-build
  • and it works flawlessly on-the-fly, as we can experience it in LeiaTube

then why is it not bui-t-in already? There should be a switch where you can turn on and off auto-conversion on fullscreen apps, like when you turn on and off Bluetooth, Wifi and Airplane mode in Android: an OS-level 3D switch would be awesome.