Regarding running Android LXC guest in Ubuntu touch by using Mir

[Daniel van Vugt]

Support for Android apps is unlikely to happen any time soon.

You have to remember that Ubuntu Touch is not Android, but is a full
Ubuntu system. The fact that Ubuntu Touch uses an Android kernel is not
sufficient to support Android apps.

Although parts of Android remain and are visible in the Ubuntu Touch
filesystem, they are unlikely to function correctly. Certainly even if
you could run an Android app right now then it would not appear on the
screen. That would require significant work. And even still, not all
Ubuntu Touch devices will be based on Android devices. So you would
really need to start from the ground up and build a self-contained
Android emulator.


On 07/01/16 17:53, 유재용 wrote:
> Come to think of it, by replacing surfaceflinger, would it be possible to
> 
> run Android apps as it appears as a native application in Ubuntu touch?
> 
> In other words, if you run Angry bird in Ubuntu touch, it will launch
> 
> Angry bird in Android and the screen output is composed to the application
> 
> inside Ubuntu touch?
> 
> Thanks,
> 
> Jaeyong
> 
> ------- *Original Message* -------
> 
> *Sender* : Andreas Pokorny<andreas.pokorny at canonical.com>
> 
> *Date* : 2016-01-05 03:07 (GMT+09:00)
> 
> *Title* : Re: Re: Regarding running Android LXC guest in Ubuntu touch by 
> using Mir
> 
> 
> On Mon, Jan 4, 2016 at 6:50 AM, 유재용 <jaeyong.yoo at samsung.com 
> <mailto:jaeyong.yoo at samsung.com>> wrote:
> 
>     Oh, I see. That is more interesting.
> 
>     Just for the curiosity, could you tell me more about the early days
>     before Mir?
> 
>     I'm wondering why you choose to remove surface flinger.
> 
>     Is there some constraint if you keep using Surface flinger and
>     another graphics server?
> 
>     Thanks,
> 
>     Jaeyong
> 
> 
> Hi Jaeyong,
> Replacng surfaceflinger with a mir based system compositor - next to the 
> obvious idea of making the android driver based stack similar to the 
> mesa/kms based stack - allows us to separate the user session from the 
> output and input devices allocation. With that it will be easy to have a 
> seamless switch between user sessions or have them running in parallel 
> and move devices between sessions .. and more.
> 
> regards
> Andreas
>