Hello,
I started developing games for android a month ago, now Im wondering am I able to create a game such as super smash bros. for android that uses Bluetooth to communicate and play? The game will be mainly for tablet but will be adapted toward Mobile Phones.
Regards,
Tripplemin
tripplemin said:
Hello,
I started developing games for android a month ago, now Im wondering am I able to create a game such as super smash bros. for android that uses Bluetooth to communicate and play? The game will be mainly for tablet but will be adapted toward Mobile Phones.
Regards,
Tripplemin
Click to expand...
Click to collapse
Yes you can - Android supports standard Bluetooth API for peer-to-peer communication, typically using sockets over bluetooth l2cap protocol. This means you could also communicate with non-Android devices but not iOS - it does not support these API's.
Implementation is not too difficult, particularly if you are familiar with doing sockets in Java.
On the other hand, you will probably encounter wonkiness. One issue is various implementation bugs, which are different on the different manufacturers because they implement their own Bluetooth drivers and stacks.
Also, the Bluetooth protocol supports a master-slave architecture. A master can coordinate communication with up to 7 slaves, but operates poorly/inefficiently if it is simultaneously operating as a slave to another master (or the master of 2 piconets at the same time).
In practical terms this means that it will work best if none of the devices playing the game are simultaneously using Bluetooth for e.g. tethering, controller, headset, google glasses....
Also, what happens if the master of the piconet (probably the person who initiated the first connection) stop laying and leaves... how quickly and with what prodding from your app will a new piconet form?
Looking at what I have written I realize I am probably putting you off the idea, and I'm not sure if that is fair - while I've done Bluetooth on Android and have done all the weird piconet stuff on raw Linux, I have not personally encountered the issues I'm describing on Android (just Linux). So I'm partially conjecturing and would be happy if someone else who had tried these permutations on Android wanted to correct me...
QUESTION?
Thank you so much for yur reply and I would like to contact you in the future so would you please give me your email address?
Regards,
tripplemin
tripplemin said:
Thank you so much for yur reply and I would like to contact you in the future so would you please give me your email address?
Regards,
tripplemin
Click to expand...
Click to collapse
Ask in the forum. This is what this is made for.
Everyone knows different things. You will get the best help here because there are many people seeing your question here.
THAN YOU!
Oh ok....and I love XDA, it brings developers to help each other..
Regards,
tripplemin
May be its a silly question but surprisingly there is not a single article on the web about this!?
Well, Apart from the BASIC difference between them, which is, one is android os and another is android wear os, what are the pros and cons? What more? please help?
I understand -
1. OS difference.
2. Watchface limitations and watchface functionality limitation. Android wear watchfaces can be touched to change various feature depending on watch face which so far no Android watchfaces can do.
what else?
I've ordered one of the countless cheap Chinese MT2502 based smartwatches, the 'K88H Plus' which looks like it's brand new. I was seduced by the great looks but then reading the various reviews the firmware looks pretty common across many of these devices and pretty bad. So then I set about reading the various MediaTek development docs and it seems like the embedded os, frameworks and API's are going to be out-of-the-box MT LinkIt and the UI and all functionality of the watch is actually controlled by one or more VXP's which the manufacturers are including in their ROMs.
Has anybody looked at this in any detail ? Am I on the right lines here ?
So I'm thinking, I'll write a VXP which is a mini watch OS with watchface, built in continuous step counting and notifications handling to create a better overall experience.
Has anybody else tried this ? Can you use the USB charging cable to remote debug the VXP app i.e. will the watch behave like the Linkit Assist 2502 board ? Thanks, grateful for any pointers.
Did you figure this out? Or got any further? Very curious getting into app development for watches with this type of microcontroller (so not just watch faces). Two minds can do more than one! For as far as I've seen, the MRE 3.0 SDK can actually make an installable app, still playing with that.
Tag me in pls ... 3 is better than 2.
Hi,
Is there such a thing as a Wear OS implementation SDK? Like the emulator, but without the presentation/display layer?
For example, if I wanted to create a web page that could be paired to the phone and used the Wear APIs to show data and/or notifications, is there any code I could base it on?
I was think of going looking into the emulator but figured there may be something more tailored for this.
Thanks for any help
I have in my Renault Kwid the default, MediaNav Evolution (MN2) screen, with software version 9.1.3. I'm looking to modify some of the "hidden" configs, by entering to menu called MICON MENU, but since documentation and information about that hidden menu is so limited and contradictory, I wouldnt like to try it on the hardware itself, but instead, have a virtual machine where i can easily test what things go.
Its obvious that i would have to also emulate all the peripherals that the device itself has, but i think its possible to "bypass" them. I dont know yet, but i would like to try it out.
First of all i would like to get the OS to boot.
This is all the info I got for now:
CPU: 667MHz MIPS
RAM: 1GB
OS: WINDOWS CE 6.0
Ive also got an "update file" wich appears to have most of the operating system (i think).
Ive looked a bit in how to get starded. AFAIK, i will need to use qemu, but thats all i could understand.
Thanks!
Hello, i got a 2017 Clio recently with the same piece of HW and im looking through every exploit i can before paying to get an after-market screen, did you have any luck with your tries?
JDogg_679 said:
Hello, i got a 2017 Clio recently with the same piece of HW and im looking through every exploit i can before paying to get an after-market screen, did you have any luck with your tries?
Click to expand...
Click to collapse
Sorry, I left the idea as the renault system is already pretty crappy, and trying to mod it was already worthless. If you have any MN2, your best option is to change it for the new one linux based MN3, or buy a third party one
ffpp.2003 said:
Sorry, I left the idea as the renault system is already pretty crappy, and trying to mod it was already worthless. If you have any MN2, your best option is to change it for the new one linux based MN3, or buy a third party one
Click to expand...
Click to collapse
No worries thanks for the rapid response, do you have any links for a MN3 head unit ? I've been searching to check if its worth the money but no luck so far, all i can find is 3rd party ones.
JDogg_679 said:
No worries thanks for the rapid response, do you have any links for a MN3 head unit ? I've been searching to check if its worth the money but no luck so far, all i can find is 3rd party ones.
Click to expand...
Click to collapse
i dont think you can buy them. you'll have to probably go to a renault service center and ask them to change it. you could try looking on facebook marketplace, but you have to find a good deal
Hey, I also have an MNE, I agree that it's crap, however I would like to ask if anyone has tried to run AutoKit-WINCE on it?
@FAB1150 mentioned it in another thread
Or maybe someone tried to launch EasyConnected ?
ZgredekLCD said:
Hey, I also have an MNE, I agree that it's crap, however I would like to ask if anyone has tried to run AutoKit-WINCE on it?
@FAB1150 mentioned it in another thread
Or maybe someone tried to launch EasyConnected ?
Click to expand...
Click to collapse
Well, it would probably fail, as the guy in the thread you linked said, since those head units are made different but with the same propose, meaning that the hardware and software might be different, but they do exactly the same.
Also, one big factor about Windows CE, is that every OS build is strictly limited to work with the desired hardware that it was built for, more or less like any android ROM. The difference lays that Windows CE manages hardware resources different than any standard OS, thus forcing the app developer to make as many versions of the app as head units he wants to support.
Because of that, is that I want to emulate the entire MNE system, so I can test apps without ruining the device itself.
So far, I haven't made much progress. All I know now is that the CPU is an R4000 based mips cpu, with the model number AU1320. I haven't been able to find any datasheet yet. I also been learning about QEMU/KVM, but I did no progress given that I'm having some trouble to make a basic machine and support about mips emulation is very limited.
My main idea now is to port/develop some kind of scrcpy for the MNE