very nice .
@Rick164 and I have been talking about making an android app for our AtmoOrb project, but havnt done that yet. Just a few days ago i started with the first few chapters of the google documentation about creating apps, but have not done more than a simple hello world app.
Since then however, i was thinking about adding support for apps into AtmoLight, so you dont have to use your remote to open the context menu. Maybe you are interessted in that? Instead of controlling AtmoCtrl, controlling AtmoLight. This way every handler can be controlled, different effects can be choosen and all that stuff. Let me know what you think .
My wish start to be accomplished.
My First goal when receive my first Ambilight system, was to make remote selector, for using it, out of MP. but using IR Remote was not easy due to "stop" timing issue with lib conflict.
With this soft, we can use static color / Live mode / VU Style on the fly ... for each device type. ( Atmowin / AtmoOrb / maybe hyperion ? )
i think, if you want for sure, help us to control Atmolight, and all the device who can remote.
AtmoCtrl is a small utility to control AtmoWin. AtmoLight is a plugin for MediaPortal. It is also able to control AtmoWin, but does support more commands. It also supports other software besides AtmoWin, for example AmbiBox, Boblight, Hyperion or Philips Hue lights. If your app could control AtmoLight instead of AtmoWin directly, then you automatically could control all these other programs aswell. However MediaPortal would have to be running.But what is the diffecrence in using AtmoLight Instead of AtmoCtrl?
|Android based client for MP2||MediaPortal 2||3|
|K||MpTvClient: Client for Amazon and Android devices||General||2|
|K||Client für Android und Amazon-Geräte||Allgemeines Support- und Diskussionsforum||66|
|Dvb-s2 zu android ipad||Einsteigerforum||0|
|Rezension Android TV Box KM8P||Barebones/PC-Systeme/Kaufberatung||8|