[android-developers] Re: Android 3.1 is too slow
On Friday, June 10, 2011 11:34:13 PM UTC+1, Glenn Maynard wrote: Saying "use a real device" isn't very helpful or realistic. Android > apps need to be tested in many screen configurations and in every > supported SDK level. If the cost of entry to Android development is > thousands of dollars of test devices, that's just too high. > I agree with you 100%. Unfortunately, that doesn't change the fact that the Honeycomb emulator is just not usable. But looking on the bright side, the pre-Honeycomb emulators are mostly not too bad. Gingerbread has a few specific issues, and sure, they are a lot slower than a real device, but they are generally usable. String -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: Android 3.1 is too slow
"Use a real device" is a good answer, especially when it comes to Honeycomb as the market stands today. It will likely fragment some over time but I highly doubt it will turn into what the phone market has. Frankly, I'd rather pay $400 for a tablet than even fire up the emulator once. If you expect to release your app and support the platform in a first-class way, you'll need one eventually anyway. Chris Stewart http://locomolabs.com On Jun 11, 2011 1:40 PM, "Glenn Maynard" wrote: > Saying "use a real device" isn't very helpful or realistic. Android > apps need to be tested in many screen configurations and in every > supported SDK level. If the cost of entry to Android development is > thousands of dollars of test devices, that's just too high. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Android 3.1 is too slow
Saying "use a real device" isn't very helpful or realistic. Android apps need to be tested in many screen configurations and in every supported SDK level. If the cost of entry to Android development is thousands of dollars of test devices, that's just too high. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Android 3.1 is too slow
Hope is on the horizon :-) I've seen some preliminary work at Google IO being done by Google engineers to use PC's hardware acceleration for the emulator's screen. It wasn't quite stable yet, but the performance shown was great! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Android 3.1 is too slow
I only use the emulator to test screen configurations on different devices... Specs are available on the internet, so you can change your Emulator easily enough to use those specs. For real testing, like say if the application actually works and performance testing, I use a real device. On 10 jun, 12:30, String wrote: > On Friday, June 10, 2011 5:32:50 AM UTC+1, Raja Nagendra Kumar wrote: > > How does others manage to use it for development.. > > > > Nobody does. The 3.x emulator is worse than useless; it's not possible to > develop for Honeycomb without a real device. > > [*Worse* than useless? Definitely. If it simply didn't run, that'd be > useless. But as it is, it can suck up huge blocks of your time *trying* to > use it. It's really that bad.] > > String -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Android 3.1 is too slow
On Friday, June 10, 2011 5:32:50 AM UTC+1, Raja Nagendra Kumar wrote: How does others manage to use it for development.. > Nobody does. The 3.x emulator is worse than useless; it's not possible to develop for Honeycomb without a real device. [*Worse* than useless? Definitely. If it simply didn't run, that'd be useless. But as it is, it can suck up huge blocks of your time *trying* to use it. It's really that bad.] String -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Android 3.1 is too slow
You either: 1. Accept its slow and continue to use it 2. Develop on a real device You should test it on a real device before deploying it anyway. On Jun 9, 9:32 pm, Raja Nagendra Kumar wrote: > Hi, > > Android SDK simulators are dead slow even on i7 machines with 16 GB > ram.. > > How does others manage to use it for development.. > > Are there any tweeks and tricks.. > > Regards, > Raja Nagendra Kumar, > C.T.Owww.tejasoft.com -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: Android 3.1 is too slow
No, no tweaks or tricks. They're working on hardware acceleration on the graphics, which should probably help out. But for now, you're sol. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
