[android-developers] Re: Android SDK is so slow that is ridiculous.
honeycomb is also slower. congratulations google. -- 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 SDK is so slow that is ridiculous.
How did you exactly determine this? On Feb 24, 11:25 pm, sblantipodi perini.dav...@dpsoftware.org wrote: honeycomb is also slower. congratulations google. -- 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 SDK is so slow that is ridiculous.
:) On Thu, Feb 24, 2011 at 8:55 PM, sblantipodi perini.dav...@dpsoftware.orgwrote: honeycomb is also slower. congratulations google. -- 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
Re: [android-developers] Re: Android SDK is so slow that is ridiculous.
Not to mention that testing OpenGL games is impossible. The only way to test on devices is users, otherwise it's just a guessing and hoping for the best. In any case, I don't care WHY the emulator is so slow. Hopefully they'll make it fast in the near future, the iPhone emulator is much better. On Fri, Jan 28, 2011 at 11:52 PM, Jonathan Foley jonefo...@gmail.com wrote: As Dianne mentioned and others have before, the bottleneck is the dynamic translation of ARM opcodes to x86 opcodes. Other VM's like Vmware emulate hardware, but they are still executing code natively albeit with some hypervisor that itself has direct hooks within modern processors. The WebOS and WP7 and iOS emulators are all running builds compiled natively for x86 so they are fast. The Android emulator does not, though I don't see why it couldn't be. The emulator is unusable, I only use real devices except for UI assessment on smaller screens, though I use that less and less as the UI builder/previewer becomes more feature rich. Jonathan On Jan 28, 11:19 pm, Marcin Orlowski webnet.andr...@gmail.com wrote: All I was trying to say that emulating of 1GHz of any non native code at the instruction level will be slow on a 2Ghz host. I'd bet if you tried to run a PacMan 8-bit CPU at 1GHz, it wouldn't emulate at full speed or even come close. 8-bit or not is not directly related to possible emulation speed. And this is just type of architecture which is not the only factor that influences the whole process (and yes, you can run 8-bit pacman full speed on far slower devices - i.e. Spectrum emulator on Palm phone (which is 300MHz). I believe in case of Android the bottlenecks is not just different architecture but also a GPU support (or lack of h/w support of such) which hits performance badly. In general I believe it would help if Google could just spend a few bucks and simply hire bunch of folks from emulators scene. -- 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 -- ~ Jeremiah:9:23-24 Android 2D MMORPG: http://developingthedream.blogspot.com/, http://www.youtube.com/user/revoltingx -- 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 SDK is so slow that is ridiculous.
(and yes, you can run 8-bit pacman full speed on far slower devices - i.e. Spectrum emulator on Palm phone (which is 300MHz). I meant if Pacman's 8080 were running at 1GHz. No way it could be emulated at full speed on a 2GHz i86, if each instruction is emulated individually -- not even close. Even with caching or other optimizations, you would have to read/decode/execute/write in a handful of processor cycles. And that assuming you would have 100% of the cycles available to you, which you don't. The iOS emulator is Mac specific and it's probably more like a simulator than an emulator. I believe the only real viable solution is to simulate an Android system below at some cut-off layer.Even if the emulated processor is running at 600Mhz which is about the speed of the slowest Android devices, trying to emulate such an advanced processor architecture at an acceptable speed will not work. Actually, I am quite suprised that it's running as good as it is, so without knowing all details, it's possible that some things are already simulated, not emulated. -- 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 SDK is so slow that is ridiculous.
On Sat, Jan 29, 2011 at 1:26 AM, Miguel Morales therevolti...@gmail.comwrote: Not to mention that testing OpenGL games is impossible. The only way to test on devices is users, otherwise it's just a guessing and hoping for the best. In any case, I don't care WHY the emulator is so slow. Hopefully they'll make it fast in the near future, the iPhone emulator is much better. At the end of the day, you absolutely need to test and run on a device, especially for doing things like OpenGL games. An emulator or simulator on desktop hardware is never going to give you a good idea of how your app performs on real hardware. This isn't an excuse for the emulator being slow (we really would like to improve it, this is just a fairly challenging problem), but no matter what is done it can never be a replacement for running on a real device. -- 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. -- 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 SDK is so slow that is ridiculous.
It's easy to say that until you have actually written an OpenGL game for Android. Running at seconds per frame instead of frames per second means you can ONLY test on real hardware. On real hardware my game (Tank Recon 3D) takes over 5 minutes to load in the debugger (30 seconds on BlackBerry). Even working with these limitations you also have to develop for the different OS versions and screen sizes. Now I understand what you're saying with the emulation but this blanket answer is getting kind of old. Stop giving the 'You can't get there from here' answer and try and figure something out. The BlackBerry emulators route the OpenGL calls to the desktop PC and allow you to choose the level of acceleration. Maybe this is something that can be looked into. Sure I know you're not getting a 1:1 mapping but it does allows you to develop. How about making a new driver backed by the desktop GPU and give some way to select it? On 1/29/2011 12:53 PM, Dianne Hackborn wrote: On Sat, Jan 29, 2011 at 1:26 AM, Miguel Morales therevolti...@gmail.com mailto:therevolti...@gmail.com wrote: Not to mention that testing OpenGL games is impossible. The only way to test on devices is users, otherwise it's just a guessing and hoping for the best. In any case, I don't care WHY the emulator is so slow. Hopefully they'll make it fast in the near future, the iPhone emulator is much better. At the end of the day, you absolutely need to test and run on a device, especially for doing things like OpenGL games. An emulator or simulator on desktop hardware is never going to give you a good idea of how your app performs on real hardware. This isn't an excuse for the emulator being slow (we really would like to improve it, this is just a fairly challenging problem), but no matter what is done it can never be a replacement for running on a real device. -- Dianne Hackborn Android framework engineer hack...@android.com mailto: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. -- 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 -- Leigh McRae http://www.lonedwarfgames.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
Re: [android-developers] Re: Android SDK is so slow that is ridiculous.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/29/2011 10:55 AM, Leigh McRae wrote: It's easy to say that until you have actually written an OpenGL game for Android. Running at seconds per frame instead of frames per second means you can ONLY test on real hardware. On real hardware my game (Tank Recon 3D) takes over 5 minutes to load in the debugger (30 seconds on BlackBerry). Even working with these limitations you also have to develop for the different OS versions and screen sizes. Now I understand what you're saying with the emulation but this blanket answer is getting kind of old. Stop giving the 'You can't get there from here' answer and try and figure something out. The BlackBerry emulators route the OpenGL calls to the desktop PC and allow you to choose the level of acceleration. Maybe this is something that can be looked into. Sure I know you're not getting a 1:1 mapping but it does allows you to develop. How about making a new driver backed by the desktop GPU and give some way to select it? And what about you write and contribute this driver to the code base? There was something I disliked in the phone emulator, I fixed it for myself, and then submitted it in Gerrit and the patch was accepted, all in less than two months and it is now part of Gingerbread. Complaining about missing features on an open source project is ridiculous. On 1/29/2011 12:53 PM, Dianne Hackborn wrote: On Sat, Jan 29, 2011 at 1:26 AM, Miguel Morales therevolti...@gmail.com mailto:therevolti...@gmail.com wrote: Not to mention that testing OpenGL games is impossible. The only way to test on devices is users, otherwise it's just a guessing and hoping for the best. In any case, I don't care WHY the emulator is so slow. Hopefully they'll make it fast in the near future, the iPhone emulator is much better. At the end of the day, you absolutely need to test and run on a device, especially for doing things like OpenGL games. An emulator or simulator on desktop hardware is never going to give you a good idea of how your app performs on real hardware. This isn't an excuse for the emulator being slow (we really would like to improve it, this is just a fairly challenging problem), but no matter what is done it can never be a replacement for running on a real device. -- Dianne Hackborn Android framework engineer hack...@android.com mailto: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. -- 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 - -- Marc Petit-Huguenin Personal email: m...@petit-huguenin.org Professional email: petit...@acm.org Blog: http://blog.marc.petit-huguenin.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk1EcS8ACgkQ9RoMZyVa61es6wCeMZHA1Lu5GrzI4qNBIpW/vMQX 6NIAn3azdKrV6q6BAurX2sDMwJsEkfMp =tUSL -END PGP SIGNATURE- -- 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 SDK is so slow that is ridiculous.
iOS simulator is fast because XCode builds an X86 binary and because iPhone and OSX both run basically the same OS, there is no actual emulation happening, mostly just API mapping... It's running as a mostly OS-Native binary. Unless you want to develop your apps in Android itself on your desktop on an ARM CPU, you should understand that there will be a performance penalty for emulating the an ARM CPU on x86. One way to make it faster is to build an Android x86 emulator and stop emulating operations, instead using the CPU natively. It seems as if there is progress in that area, even if it's not all from Google. On Jan 29, 11:57 am, Marc Petit-Huguenin petit...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/29/2011 10:55 AM, Leigh McRae wrote: It's easy to say that until you have actually written an OpenGL game for Android. Running at seconds per frame instead of frames per second means you can ONLY test on real hardware. On real hardware my game (Tank Recon 3D) takes over 5 minutes to load in the debugger (30 seconds on BlackBerry). Even working with these limitations you also have to develop for the different OS versions and screen sizes. Now I understand what you're saying with the emulation but this blanket answer is getting kind of old. Stop giving the 'You can't get there from here' answer and try and figure something out. The BlackBerry emulators route the OpenGL calls to the desktop PC and allow you to choose the level of acceleration. Maybe this is something that can be looked into. Sure I know you're not getting a 1:1 mapping but it does allows you to develop. How about making a new driver backed by the desktop GPU and give some way to select it? And what about you write and contribute this driver to the code base? There was something I disliked in the phone emulator, I fixed it for myself, and then submitted it in Gerrit and the patch was accepted, all in less than two months and it is now part of Gingerbread. Complaining about missing features on an open source project is ridiculous. On 1/29/2011 12:53 PM, Dianne Hackborn wrote: On Sat, Jan 29, 2011 at 1:26 AM, Miguel Morales therevolti...@gmail.com mailto:therevolti...@gmail.com wrote: Not to mention that testing OpenGL games is impossible. The only way to test on devices is users, otherwise it's just a guessing and hoping for the best. In any case, I don't care WHY the emulator is so slow. Hopefully they'll make it fast in the near future, the iPhone emulator is much better. At the end of the day, you absolutely need to test and run on a device, especially for doing things like OpenGL games. An emulator or simulator on desktop hardware is never going to give you a good idea of how your app performs on real hardware. This isn't an excuse for the emulator being slow (we really would like to improve it, this is just a fairly challenging problem), but no matter what is done it can never be a replacement for running on a real device. -- Dianne Hackborn Android framework engineer hack...@android.com mailto: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. -- 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 - -- Marc Petit-Huguenin Personal email: m...@petit-huguenin.org Professional email: petit...@acm.org Blog:http://blog.marc.petit-huguenin.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk1EcS8ACgkQ9RoMZyVa61es6wCeMZHA1Lu5GrzI4qNBIpW/vMQX 6NIAn3azdKrV6q6BAurX2sDMwJsEkfMp =tUSL -END PGP SIGNATURE- -- 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 SDK is so slow that is ridiculous.
Other emulators works with natively speed, don't compare a 1GHz Cortex or Snapdragon processor with a modern desktop CPU please, its ridiculous. @Raphael: Thanks for the answer, I appreciate your answer and hope to see some fix soon :) On Jan 28, 3:44 am, Zsolt Vasvari zvasv...@gmail.com wrote: Honestly, what do people expect? You are trying to emulate a 1GHz computer on a 2GHz computer with a completely different architecture. I can't imagine it will ever be fast. I used do MAME development and can tell you that it's hard to get the emulation running for even a 10 year old system with a GPU. On Jan 28, 4:21 am, JAlexoid (Aleksandr Panzin) jalex...@gmail.com wrote: I have the same problem with all AVDs, regardless of the version. The emulator in general sucks in performance. I'm on 64 bit Ubuntu, bus same goes for Windows XP and Windows 7. On 27 янв, 03:58, Jake Basile jakerbas...@gmail.com wrote: I have a Core i7-920, 6GB of DDR-1333 RAM, and an ATI 5770. I get maybe 5-10 FPS on the Honeycomb emulator. This thing needs serious performance testing and improvement.- Hide quoted text - - Show quoted text - -- 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 SDK is so slow that is ridiculous.
I'm not complaining about the performance, since I know the problems behind it. But, with the inevitable performance problems maybe a simulated environment(with x86 architecture) or a Android x86 VM would be a better option(in performance). Problems will probably arise with the optimisations of native code for ARM architecture. On 28 янв, 04:44, Zsolt Vasvari zvasv...@gmail.com wrote: Honestly, what do people expect? You are trying to emulate a 1GHz computer on a 2GHz computer with a completely different architecture. I can't imagine it will ever be fast. I used do MAME development and can tell you that it's hard to get the emulation running for even a 10 year old system with a GPU. On Jan 28, 4:21 am, JAlexoid (Aleksandr Panzin) jalex...@gmail.com wrote: I have the same problem with all AVDs, regardless of the version. The emulator in general sucks in performance. I'm on 64 bit Ubuntu, bus same goes for Windows XP and Windows 7. On 27 янв, 03:58, Jake Basile jakerbas...@gmail.com wrote: I have a Core i7-920, 6GB of DDR-1333 RAM, and an ATI 5770. I get maybe 5-10 FPS on the Honeycomb emulator. This thing needs serious performance testing and improvement.- Hide quoted text - - Show quoted text - -- 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 SDK is so slow that is ridiculous.
Thanks for the lesson, I didn't realize that a 1GHz Cortex is not directly comparable to a 2GHz Core i3... All I was trying to say that emulating of 1GHz of any non native code at the instruction level will be slow on a 2Ghz host. I'd bet if you tried to run a PacMan 8-bit CPU at 1GHz, it wouldn't emulate at full speed or even come close. On Jan 28, 6:20 pm, sblantipodi perini.dav...@dpsoftware.org wrote: Other emulators works with natively speed, don't compare a 1GHz Cortex or Snapdragon processor with a modern desktop CPU please, its ridiculous. @Raphael: Thanks for the answer, I appreciate your answer and hope to see some fix soon :) On Jan 28, 3:44 am, Zsolt Vasvari zvasv...@gmail.com wrote: Honestly, what do people expect? You are trying to emulate a 1GHz computer on a 2GHz computer with a completely different architecture. I can't imagine it will ever be fast. I used do MAME development and can tell you that it's hard to get the emulation running for even a 10 year old system with a GPU. On Jan 28, 4:21 am, JAlexoid (Aleksandr Panzin) jalex...@gmail.com wrote: I have the same problem with all AVDs, regardless of the version. The emulator in general sucks in performance. I'm on 64 bit Ubuntu, bus same goes for Windows XP and Windows 7. On 27 янв, 03:58, Jake Basile jakerbas...@gmail.com wrote: I have a Core i7-920, 6GB of DDR-1333 RAM, and an ATI 5770. I get maybe 5-10 FPS on the Honeycomb emulator. This thing needs serious performance testing and improvement.- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text - -- 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 SDK is so slow that is ridiculous.
All I was trying to say that emulating of 1GHz of any non native code at the instruction level will be slow on a 2Ghz host. I'd bet if you tried to run a PacMan 8-bit CPU at 1GHz, it wouldn't emulate at full speed or even come close. 8-bit or not is not directly related to possible emulation speed. And this is just type of architecture which is not the only factor that influences the whole process (and yes, you can run 8-bit pacman full speed on far slower devices - i.e. Spectrum emulator on Palm phone (which is 300MHz). I believe in case of Android the bottlenecks is not just different architecture but also a GPU support (or lack of h/w support of such) which hits performance badly. In general I believe it would help if Google could just spend a few bucks and simply hire bunch of folks from emulators scene. -- 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 SDK is so slow that is ridiculous.
As Dianne mentioned and others have before, the bottleneck is the dynamic translation of ARM opcodes to x86 opcodes. Other VM's like Vmware emulate hardware, but they are still executing code natively albeit with some hypervisor that itself has direct hooks within modern processors. The WebOS and WP7 and iOS emulators are all running builds compiled natively for x86 so they are fast. The Android emulator does not, though I don't see why it couldn't be. The emulator is unusable, I only use real devices except for UI assessment on smaller screens, though I use that less and less as the UI builder/previewer becomes more feature rich. Jonathan On Jan 28, 11:19 pm, Marcin Orlowski webnet.andr...@gmail.com wrote: All I was trying to say that emulating of 1GHz of any non native code at the instruction level will be slow on a 2Ghz host. I'd bet if you tried to run a PacMan 8-bit CPU at 1GHz, it wouldn't emulate at full speed or even come close. 8-bit or not is not directly related to possible emulation speed. And this is just type of architecture which is not the only factor that influences the whole process (and yes, you can run 8-bit pacman full speed on far slower devices - i.e. Spectrum emulator on Palm phone (which is 300MHz). I believe in case of Android the bottlenecks is not just different architecture but also a GPU support (or lack of h/w support of such) which hits performance badly. In general I believe it would help if Google could just spend a few bucks and simply hire bunch of folks from emulators scene. -- 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 SDK is so slow that is ridiculous.
Performance problem on android SDK isn't related on what you are talking here. Android SDK is so slow also with android 2.2 and 2.2. The SDK uses only one core and this is a shame. Too slow for everything that needs more power than a fart app. -- 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 SDK is so slow that is ridiculous.
I agree, the SDK itself is slow, not just the emulator. I've noticed that with every release of the SDK it gets slower. -niko On Jan 27, 6:56 am, sblantipodi perini.dav...@dpsoftware.org wrote: Performance problem on android SDK isn't related on what you are talking here. Android SDK is so slow also with android 2.2 and 2.2. The SDK uses only one core and this is a shame. Too slow for everything that needs more power than a fart app. -- 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 SDK is so slow that is ridiculous.
On Thu, Jan 27, 2011 at 12:16 PM, niko20 nikolatesl...@yahoo.com wrote: I agree, the SDK itself is slow, not just the emulator. I've noticed that with every release of the SDK it gets slower. The SDK is a ZIP file (or a self-installing EXE on Windows). ZIP files do not have speed and hence cannot be slower. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in London: http://bit.ly/smand1 and http://bit.ly/smand2 -- 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 SDK is so slow that is ridiculous.
I have the same problem with all AVDs, regardless of the version. The emulator in general sucks in performance. I'm on 64 bit Ubuntu, bus same goes for Windows XP and Windows 7. On 27 янв, 03:58, Jake Basile jakerbas...@gmail.com wrote: I have a Core i7-920, 6GB of DDR-1333 RAM, and an ATI 5770. I get maybe 5-10 FPS on the Honeycomb emulator. This thing needs serious performance testing and improvement. -- 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 SDK is so slow that is ridiculous.
We are aware of the emulator speed issue and are actively working on it. R/ -- 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 SDK is so slow that is ridiculous.
Honestly, what do people expect? You are trying to emulate a 1GHz computer on a 2GHz computer with a completely different architecture. I can't imagine it will ever be fast. I used do MAME development and can tell you that it's hard to get the emulation running for even a 10 year old system with a GPU. On Jan 28, 4:21 am, JAlexoid (Aleksandr Panzin) jalex...@gmail.com wrote: I have the same problem with all AVDs, regardless of the version. The emulator in general sucks in performance. I'm on 64 bit Ubuntu, bus same goes for Windows XP and Windows 7. On 27 янв, 03:58, Jake Basile jakerbas...@gmail.com wrote: I have a Core i7-920, 6GB of DDR-1333 RAM, and an ATI 5770. I get maybe 5-10 FPS on the Honeycomb emulator. This thing needs serious performance testing and improvement.- Hide quoted text - - Show quoted text - -- 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 SDK is so slow that is ridiculous.
Odd, I've never had any real trouble with the performance. The first time the emulator comes up is always painful, but once it's configured everything else is reasonably swift. On Jan 26, 7:35 pm, sblantipodi perini.dav...@dpsoftware.org wrote: As title. I think that Androdi SDK should think to improve its performance instead of releasing new SDK... I have just downloaded the Honeycomb SDK on my Core I7 2600 Sandy Bridge (8GB RAM) and it so slow that is unusable, just like the 2.3 and 2.2 version. Shame on google for this. -- 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 SDK is so slow that is ridiculous.
I have a Core i7-920, 6GB of DDR-1333 RAM, and an ATI 5770. I get maybe 5-10 FPS on the Honeycomb emulator. This thing needs serious performance testing and improvement. -- 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 SDK is so slow that is ridiculous.
The issue with HC is that it now has a huge screen to draw, and the emulator itself doesn't implement any hardware acceleration of drawing, so it needs to emulate ARM code that is rendering to a window, and then emulate yet more ARM code that composites together the final display. Implementing hardware acceleration of drawing in the emulator is extremely non-trivial. It's not a matter of needing performance testing and improvement. The bottle-neck is very obvious, it is just difficult to solve. And wouldn't you like to have *some* kind of working HC emulator now before devices ship? On Wed, Jan 26, 2011 at 5:58 PM, Jake Basile jakerbas...@gmail.com wrote: I have a Core i7-920, 6GB of DDR-1333 RAM, and an ATI 5770. I get maybe 5-10 FPS on the Honeycomb emulator. This thing needs serious performance testing and improvement. -- 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.comandroid-developers%2bunsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- 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. -- 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 SDK is so slow that is ridiculous.
And wouldn't you like to have *some* kind of working HC emulator now before devices ship? I just wanted to say yes, absolutely. Thanks for getting this to us soon, even in an unfinished/preview state rather than making us wait for the device to ship and our apps to be broken on customers hardware. -Kevin On Jan 26, 8:05 pm, Dianne Hackborn hack...@android.com wrote: The issue with HC is that it now has a huge screen to draw, and the emulator itself doesn't implement any hardware acceleration of drawing, so it needs to emulate ARM code that is rendering to a window, and then emulate yet more ARM code that composites together the final display. Implementing hardware acceleration of drawing in the emulator is extremely non-trivial. It's not a matter of needing performance testing and improvement. The bottle-neck is very obvious, it is just difficult to solve. And wouldn't you like to have *some* kind of working HC emulator now before devices ship? On Wed, Jan 26, 2011 at 5:58 PM, Jake Basile jakerbas...@gmail.com wrote: I have a Core i7-920, 6GB of DDR-1333 RAM, and an ATI 5770. I get maybe 5-10 FPS on the Honeycomb emulator. This thing needs serious performance testing and improvement. -- 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.comandroid-developers%2Bunsubs cr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- 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. -- 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
