Hi, We are aware of the Market implications altering the application lifecycle to have multiple activities resumed. We do know that the current Android CDD does not allow this. As this is our early prototype we took some degrees of freedom and implemented it this way to be able to utilize both displays.
There are many ways of using a secondary display. It could e.g. be a smaller “info” display like those on clamshell phones that would be rendered natively. But we wanted to integrate the display into the system in order for full Android applications to run there. With the standard Android activity lifecycle, an activity will be paused whenever another activity comes in front, hence starting a new activity on the secondary display will pause the activity on the primary display. This makes the dual-display concept a little less useful. We see a lot of really useful use-cases that can be implemented on Android devices by having multiple activities running on dual displays. So is there any way of allowing applications to run on both displays without breaking the CDD requirements? Best regards Mikkel Christensen Ixonos Plc On Dec 13, 11:54 pm, Dianne Hackborn <hack...@android.com> wrote: > It looks like in your demo you have multiple resumed activities running at > the same time. I would very strongly recommend against this, if you want > your device to be considered compatible with Market. This has very deep > repercussions for the activity lifecycle, which is likely to cause subtle > application incompatibility. Especially if multiple people are doing their > own slightly different implementations. > > If you don't care about Market, of course, have at it. > > On Tue, Nov 30, 2010 at 12:51 AM, Mikkel Christensen < > > > > > > > > > > mikkel.christen...@ixonos.com> wrote: > > Hi, > > > On Nov 22, 12:25 pm, Deva R <r.deva...@gmail.com> wrote: > > > >Has any one been able to do this? Is there some official doc from > > > Android on how to achieve this? > > > In the company that I work for, we have been working on an Android 2.2 > > dual display solution. > > > The basic idea is: > > - Applications will via a framework extension indicate the display ID > > where the application should run > > - The WindowManagerService will at application start time get the > > requested display ID from the starting application > > - WindowManagerService provides the display ID to the SurfaceFlinger > > which will create a new surface on the requested display > > - The SurfaceFlinger has been modified to handle compositions using > > OpenGL on multiple displays > > - The ActivityManager has been modified to allow the top applications > > to run simultaneously on two displays > > - The event system has been extended to handle a secondary touch > > device operating in parallel. This has been integrated with the > > WindowManagerService which takes care of dispatching events to the > > proper applications > > > We have uploaded a video to YouTube showing our prototype: > >http://www.youtube.com/watch?v=5CWl4bTRKuw > > > Hope this will help you. > > > Best regards, > > Mikkel Christensen > > Ixonos Plc. > > > -- > > unsubscribe: > > android-porting+unsubscr...@googlegroups.com<android-porting%2Bunsubscribe@ > > googlegroups.com> > > website:http://groups.google.com/group/android-porting > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
