Here is the problem that I am having trying to port the MultiConf over to Android. I have the Android SDK, Processing and everything working correctly however, I have getting an error when trying to compile the code because of the usage of size() in the MultiConf code. Is there a work around for this?
Hamburger wrote:the controlP5 library has been ported to Android?
I installed the newer version of controlP5 however I am now having problems with "List<Byte>". If I can get pass this one, maybe it will error when it comes to the controlP stuff.
Are you sure this is a good thing? The GUI code is horrible. Better support a native Android project that is also open source https://github.com/eziosoft/MultiWii_EZ_GUI ... just saying
copterrichie wrote:It only support Bluetooth and I am unable to install it from Google Play.
Unsupported device or because of your region? Well ... there is always compiling the source for yourself. No more difficult than porting the GUI code
Regarding bluetooth, what kind of Android device do you have and what is the technology you plan to use with it? Wifi Direct?
Google Play claims it is an unsupported device however, I was able to install many of the same apps from 1Mobile Market as listed on Google Play but eziosoft is not listed on that app server. I downloaded the source for MultiWii_EZ_GUI but it is a little more than I want to tackle at this moment. Really, the MWC Gui is not that bad, I made it pass the "List <Byte>" with ArraryList. So we are making some progress and yes, I do want to use the Wifi.
You should be able to install the APK's directly, if you don't know where to get them just ask and someone will get them for you. (If needed i can compile it if that is the case)
IMHO trying to use a ported version of Processing and other libs that already suck in a PC doesn't seem good idea. If you do have the time to dedicate to such project It would be better applied to further improving the existing desktop app preferably moving it away from Processing. Helping the guys that made the desktop app and that were able to still make something good out of Processing.
copterrichie wrote:It only support Bluetooth and I am unable to install it from Google Play.
Unsupported device or because of your region? Well ... there is always compiling the source for yourself. No more difficult than porting the GUI code
Regarding bluetooth, what kind of Android device do you have and what is the technology you plan to use with it? Wifi Direct?
Google Play claims it is an unsupported device however, I was able to install many of the same apps from 1Mobile Market as listed on Google Play but eziosoft is not listed on that app server. I downloaded the source for MultiWii_EZ_GUI but it is a little more than I want to tackle at this moment. Really, the MWC Gui is not that bad, I made it pass the "List <Byte>" with ArraryList. So we are making some progress and yes, I do want to use the Wifi.
Thank you soooooo very much, This is greatly appreciated. I hope to get up to speed with java soon because as I was playing with this port, there is android.hardware.wifi.p2p that I REALLY Really would like to try.
Thank you soooooo very much, This is greatly appreciated. I hope to get up to speed with java soon because as I was playing with this port, there is android.hardware.wifi.p2p that I REALLY Really would like to try.
Thank you again.
btw what device do you have ? I will check why my app is not compatibile.
Yeah I have a similar one made by Odys. What will you be using on the MWC side for Wifi?
P.S. I fully understand why you are doing this; Because you can! And it's fun! That's what we are here for, after all. Some time ago I started a UI for Android using the "App Inventor", but it became a monster quickly and I abandoned it.
Gartenflieger wrote:Yeah I have a similar one made by Odys. What will you be using on the MWC side for Wifi?
P.S. I fully understand why you are doing this; Because you can! And it's fun! That's what we are here for, after all. Some time ago I started a UI for Android using the "App Inventor", but it became a monster quickly and I abandoned it.
I have one of these Serial-to-Wifi Devices, there are many more on ebay and cheaper now.
copterrichie wrote:If anyone is interested, here are the links to the required files.
I installed fresh software but got the same issue as one year ago "No library found for processing.serial"... as i remember it's an exception for android...
juanquy wrote:Read Ezio posts here (Forums/Software/Multiwii EZ GUI) and you will find a direct link to the apk... good look porting from Processing to Android.
At first, I was not going to reply to this but it is just too funny, the port is already done. I just need to get the Wifi working which is nothing to do with the WiiConfig.
ezio wrote:Does it compile to apk? If yes could you post somewhere compiled app?
No, the 2.0b is still beta and the making an apk is not fully implement yet however, the project can be exported, then imported into Eclipse where a apk can be generated. I am still learning, so it will be awhile before I can do that. I can zip up the export if that will help.
Well, my curiosity got the better of me and I just had to try it. This apk is untested. Beware!!! The serial is disable awaiting the WiFi code. So, all it will do at this point is start and display the screen formatted to 800x480.
Could you share *.pde file also which could be compiled in processing (for android ofcourse). I have not success to install this *.apk on ASUS Prime tab with Android 4.1.1.
mahowik wrote:Could you share *.pde file also which could be compiled in processing (for android ofcourse). I have not success to install this *.apk on ASUS Prime tab with Android 4.1.1.
I am not going to concern myself with trying to do this right now because this is not something people seems to want and I am just do it for myself. I have an obligation to release any improvements done to the code for which I will do.
mahowik wrote:Could you share *.pde file also which could be compiled in processing (for android ofcourse). I have not success to install this *.apk on ASUS Prime tab with Android 4.1.1.
I am not going to concern myself with trying to do this right now because this is not something people seems to want and I am just do it for myself. I have an obligation to release any improvements done to the code for which I will do.
Just last night, I found a way to have it adjust the screen based upon the information provide by the system. However, it would require a rewrite of the code to adjust. At this time, I am not sure it would be worth the effect seeing there is little interest in this project.
// Place this at the top of your sketch import android.util.DisplayMetrics;
// Place this inside your setup() method DisplayMetrics dm = new DisplayMetrics(); getWindowManager().getDefaultDisplay().getMetrics(dm); float density = dm.density; int densityDpi = dm.densityDpi; println("density is " + density); println("densityDpi is " + densityDpi);