Quick question: I am trying to use instrumentation to launch a second screen upon pressing a button on the first screen (which is automatically launched by the instrumentation code). I successfully do so. But, what I now need to do is click something on the second screen (which is part of the same project!). I have tried creating instrumentation and launcher classes for this second screen but I dont know how to communicate between the first and second screen.
Any help will be greatly appreciated! On Nov 23, 2:38 pm, "Marcio Alexandroni" <[EMAIL PROTECTED]> wrote: > I'm just wondering about these security issues, injecting events, access to > some low level APIs, screen lock, telephony, etc. I've been developing on > other mobile operating systems for years and all them allow this kind of > technique, it's valuable for some kind of applications, mainly in corporate > applications where the company wants the user with no access to phone > features like downloads, games, etc, but only a limited set of features. > > My question is, would you consider adding all this 'privileged' APIs to the > security in the manifest, with a 'red' level of alert to the user upon > installation, with description of the potential risks, so that user can > decide? > > I know Android core developers said they don't want user to decide, but in > my oppinion it is really what should happen. > > Just my thought. > > Marcio Alexandroniwww.cialogica.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
