I've tried DeviceAnywhere. If you want to do anything outlined in your message, I would suggest to get a real device. For example, the device is in their lab, it's not moving, so no actual moving GPS location. Sensors, gestures, etc., not much you can do virtually.
As for the CPU, what I heard is that it's at full 528MHz. On Fri, Sep 11, 2009 at 9:05 PM, gjs <[email protected]> wrote: > > Hi there, > > I be interested for someone to report back on the actual useability of > the virtual test environment. > > Particularly - > * opening, closing physical keyboard > * display using the touchscreen (including multi-touch) various > gestures, swiping etc > * switching through the various orientations > * compass, accelerometer pitch and roll - ie moving the phone around > in 3d > * camera, taking (real) pictures and video > * audio, both record and playback and voice dialing, search > * gps > * the proximity sensor and light sensors > > I think they would need some very fancy robotics to accomodate a lot > of this, else a lot of emulation which sort of defeats the purpose. > > Regards > > PS I wonder if the CPU is pegged at 384mhz like the G1, hope there is > a better heat/power budget, so you can actually use 528mhz > > > On Sep 11, 11:34 pm, JoaJP <[email protected]> wrote: > > Mark, > > The D pad issue can be lifted off of the product demos. Who ever found > > that from only looking at the video is pretty sharp... I typically > > don't start putting in the effort until I have some hardware or at > > least a serious emulator in my hands. Once the devices roll out I am > > sure more issues will pop up. I might walk down to the T-Mobile store > > one of the days and check one out, if they let me, just for laughs. > > It's the principle that makes me wonder. It's lost on me how virtual > > test environments are sufficient to support testing nowadays, where a > > good rate of the apps rely on sensor inputs and where timing is key. > > So, rhetorically asking, what's the approach, beyond that? That devs > > buy all the shiny toys can't quite be the answer. Or can we factor > > that into charging for apps (uhum). > > > > On Sep 11, 5:49 am, Mark Murphy <[email protected]> wrote: > > > > > JoaJP wrote: > > > > The vast majority of apps will not receive any "adjustment", safe > some > > > > exceptions with deep pockets that can justify the expense. > > > > > For the Cliq's D-pad, I suspect that the vast majority of apps will not > > > need changing. > > > > > -- > > > Mark Murphy (a Commons Guy)http://commonsware.com| > http://twitter.com/commonsguy > > > > > Android Training in Germany, 18-22 January 2010: > http://bignerdranch.com > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
