GMD GestureControl Gets Lollipop Support

GMD GestureControl is an app that allows you to control your (rooted) devices with multitouch … more

Xiaomi Finally Releases Kernel Sources

If you are familiar with Xiaomi, you might have heard that they are not the most compliant when … more

SwipeBack for Xposed Updated with Lollipop Compatibility

When the Xposed Framework was announced for Android Lollipop, most modules … more

One M9 Firmware Guide & Collection

While it is still under construction, XDA Recognized Contributor herwegan‘s thread will … more
Post Reply Subscribe to Thread Email Thread

Need Developers to Develop a App

1st April 2014, 05:56 AM |#21  
bhiga's Avatar
Recognized Contributor
Thanks Meter: 928
 
2,307 posts
Join Date:Joined: Oct 2010
Donate to Me
More
What @Asphyx said.

It's like modifying the fuel pump nozzle so you can feed diesel into any vehicle. Just because you can put it into the vehicle doesn't mean it will work. The vehicle has to support and know it's getting diesel, or it won't always work.
1st April 2014, 06:53 PM |#22  
Senior Member
Thanks Meter: 334
 
1,935 posts
Join Date:Joined: Dec 2007
Quote:
Originally Posted by bhiga

What @Asphyx said.

It's like modifying the fuel pump nozzle so you can feed diesel into any vehicle. Just because you can put it into the vehicle doesn't mean it will work. The vehicle has to support and know it's getting diesel, or it won't always work.

Google (and the DIAL Consortium) sort of did the same thing with DIAL operations that Google did with Android's HAL...Pretty much set up the front side of the operations but left it unstandardized on the backend and left it all up to the developer. HAL tells you how to call to the Android Hardware but the Manufacturers support those hardware calls differently (via the Kernel) than other Manf do which is why it is so hard to make a custom rom work properly on a newly released version of Android unless the Manufacturer has released a new Kernel made to support all the new calls in the newer Android HAL.

DIAL only discovers the device and tells the OS what IP it is, and is only standardized as far as how you load an application into the device. But it does not define what application gets loaded.... the 3rd Party App does.

After that how it operates is up to the player app that gets loaded and the App that loaded it, which can be totally different from App to App (see what Bubble can do that Plex still can't regarding Subtitles as just one example).

So the only ways to achieve this (That I can think of) is to
  1. Code this capability to list and play to DLNA devices directly into the Apps you want to use (Bubble, All Cast and many other not including Plex)
  2. intercept all signals between the Launching Device and Receiver, To fool the Launch device it is dealing with a CCast and to translate CCast commands to a DLNA equivalent. Which is virtually impossible without being able to load the app the Launch device asks the CCast to launch and then pulling out and sending a stream via DLNA.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes