[android-developers] Re: ideal system configuration for developing Android 3 apps

2011-03-22 Thread String
And if you're not in the USA, you're kinda screwed for Honeycomb 
development.

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: ideal system configuration for developing Android 3 apps

2011-03-22 Thread j.s. mammen
I am not in US and I really dont want to buy new hardware to develop
for Android as its only an hobby and learning tool.

I was looking for any optimization anyone has done on their system,
such as increasing the default JVM memory, increasing the default
stack space etc.

On Mar 22, 3:11 pm, String sterling.ud...@googlemail.com wrote:
 And if you're not in the USA, you're kinda screwed for Honeycomb
 development.

 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: ideal system configuration for developing Android 3 apps

2011-03-22 Thread String
I think the point is that the Honeycomb emulator is abominable on every 
configuration that anyone's reported. Even Google has admitted that it's 
really bad.

AFAIK, nobody's reported any success with improving the situation by 
tweaking settings, either. Why don't you do that, and let us know what you 
find?

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: ideal system configuration for developing Android 3 apps

2011-03-22 Thread Mark Murphy
Actually, bumping the RAM helps a bit. hw.ramSize (Device RAM size)
of 1024, if you have enough memory on your development machine, does
improve performance. It is still fairly dreadful, but I couldn't even
get it to boot with whatever the default was.

On Tue, Mar 22, 2011 at 7:19 AM, String sterling.ud...@googlemail.com wrote:
 I think the point is that the Honeycomb emulator is abominable on every
 configuration that anyone's reported. Even Google has admitted that it's
 really bad.
 AFAIK, nobody's reported any success with improving the situation by
 tweaking settings, either. Why don't you do that, and let us know what you
 find?
 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



-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

_The Busy Coder's Guide to Android Development_ Version 3.5 Available!

-- 
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: ideal system configuration for developing Android 3 apps

2011-03-22 Thread j.s. mammen
Thanks Mark for your suggestion.
According to the API, the default is 96MB RAM which I am not sure
applies to all versions of API.

I will try your suggestions and other hardware options mentioned in
API and update this thread.

-jm

On Mar 22, 4:23 pm, Mark Murphy mmur...@commonsware.com wrote:
 Actually, bumping the RAM helps a bit. hw.ramSize (Device RAM size)
 of 1024, if you have enough memory on your development machine, does
 improve performance. It is still fairly dreadful, but I couldn't even
 get it to boot with whatever the default was.





 On Tue, Mar 22, 2011 at 7:19 AM, String sterling.ud...@googlemail.com wrote:
  I think the point is that the Honeycomb emulator is abominable on every
  configuration that anyone's reported. Even Google has admitted that it's
  really bad.
  AFAIK, nobody's reported any success with improving the situation by
  tweaking settings, either. Why don't you do that, and let us know what you
  find?
  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

 --
 Mark Murphy (a Commons 
 Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy

 _The Busy Coder's Guide to Android Development_ Version 3.5 Available!- 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: ideal system configuration for developing Android 3 apps

2011-03-22 Thread j.s. mammen
Ok, here is what I did to make the Android 3 emulator slightly more
usable:
- increased emulator vm.heap to 256 from 49
- reduced the resolution to 1024x768, default was much higher
- emulator ram to 512 (tried 1024 but it crashed )
- also increased the eclipse vm to 1024

Its slightly more faster than before!!!

On Mar 22, 5:02 pm, j.s. mammen mamm...@gmail.com wrote:
 Thanks Mark for your suggestion.
 According to the API, the default is 96MB RAM which I am not sure
 applies to all versions of API.

 I will try your suggestions and other hardware options mentioned in
 API and update this thread.

 -jm

 On Mar 22, 4:23 pm, Mark Murphy mmur...@commonsware.com wrote:



  Actually, bumping the RAM helps a bit. hw.ramSize (Device RAM size)
  of 1024, if you have enough memory on your development machine, does
  improve performance. It is still fairly dreadful, but I couldn't even
  get it to boot with whatever the default was.

  On Tue, Mar 22, 2011 at 7:19 AM, String sterling.ud...@googlemail.com 
  wrote:
   I think the point is that the Honeycomb emulator is abominable on every
   configuration that anyone's reported. Even Google has admitted that it's
   really bad.
   AFAIK, nobody's reported any success with improving the situation by
   tweaking settings, either. Why don't you do that, and let us know what you
   find?
   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

  --
  Mark Murphy (a Commons 
  Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy

  _The Busy Coder's Guide to Android Development_ Version 3.5 Available!- 
  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: ideal system configuration for developing Android 3 apps

2011-03-22 Thread Chris Stewart
Honestly, if you have any serious intention of developing for Android 3.0,
you need to forget about the emulator.

--
Chris Stewart
http://chriswstewart.com



On Tue, Mar 22, 2011 at 11:28 AM, j.s. mammen mamm...@gmail.com wrote:

 Ok, here is what I did to make the Android 3 emulator slightly more
 usable:
 - increased emulator vm.heap to 256 from 49
 - reduced the resolution to 1024x768, default was much higher
 - emulator ram to 512 (tried 1024 but it crashed )
 - also increased the eclipse vm to 1024

 Its slightly more faster than before!!!

 On Mar 22, 5:02 pm, j.s. mammen mamm...@gmail.com wrote:
  Thanks Mark for your suggestion.
  According to the API, the default is 96MB RAM which I am not sure
  applies to all versions of API.
 
  I will try your suggestions and other hardware options mentioned in
  API and update this thread.
 
  -jm
 
  On Mar 22, 4:23 pm, Mark Murphy mmur...@commonsware.com wrote:
 
 
 
   Actually, bumping the RAM helps a bit. hw.ramSize (Device RAM size)
   of 1024, if you have enough memory on your development machine, does
   improve performance. It is still fairly dreadful, but I couldn't even
   get it to boot with whatever the default was.
 
   On Tue, Mar 22, 2011 at 7:19 AM, String sterling.ud...@googlemail.com
 wrote:
I think the point is that the Honeycomb emulator is abominable on
 every
configuration that anyone's reported. Even Google has admitted that
 it's
really bad.
AFAIK, nobody's reported any success with improving the situation by
tweaking settings, either. Why don't you do that, and let us know
 what you
find?
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
 
   --
   Mark Murphy (a Commons Guy)http://commonsware.com|
 http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy
 
   _The Busy Coder's Guide to Android Development_ Version 3.5 Available!-
 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


-- 
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: ideal system configuration for developing Android 3 apps

2011-03-22 Thread David A. O. Lozano
I'm new on android dev, so how much had changed 3.0 from previous version? (I 
guess you can develop in 2.x an debug normally then test 3 specific 
functionality on device

Chris Stewart cstewart...@gmail.com wrote:

Honestly, if you have any serious intention of developing for Android 3.0,
you need to forget about the emulator.

--
Chris Stewart
http://chriswstewart.com



On Tue, Mar 22, 2011 at 11:28 AM, j.s. mammen mamm...@gmail.com wrote:

 Ok, here is what I did to make the Android 3 emulator slightly more
 usable:
 - increased emulator vm.heap to 256 from 49
 - reduced the resolution to 1024x768, default was much higher
 - emulator ram to 512 (tried 1024 but it crashed )
 - also increased the eclipse vm to 1024

 Its slightly more faster than before!!!

 On Mar 22, 5:02 pm, j.s. mammen mamm...@gmail.com wrote:
  Thanks Mark for your suggestion.
  According to the API, the default is 96MB RAM which I am not sure
  applies to all versions of API.
 
  I will try your suggestions and other hardware options mentioned in
  API and update this thread.
 
  -jm
 
  On Mar 22, 4:23 pm, Mark Murphy mmur...@commonsware.com wrote:
 
 
 
   Actually, bumping the RAM helps a bit. hw.ramSize (Device RAM size)
   of 1024, if you have enough memory on your development machine, does
   improve performance. It is still fairly dreadful, but I couldn't even
   get it to boot with whatever the default was.
 
   On Tue, Mar 22, 2011 at 7:19 AM, String sterling.ud...@googlemail.com
 wrote:
I think the point is that the Honeycomb emulator is abominable on
 every
configuration that anyone's reported. Even Google has admitted that
 it's
really bad.
AFAIK, nobody's reported any success with improving the situation by
tweaking settings, either. Why don't you do that, and let us know
 what you
find?
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
 
   --
   Mark Murphy (a Commons Guy)http://commonsware.com|
 http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy
 
   _The Busy Coder's Guide to Android Development_ Version 3.5 Available!-
 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


-- 
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: ideal system configuration for developing Android 3 apps

2011-03-21 Thread PatternMusic
The Honeycomb emulator is reportedly quite slow on all systems. Your laptop is 
probably fine. You should probably spring for a real Xoom. The Wifi-only model 
is due in US stores by the end of March. I can vouch that the 3G model is quite 
nice and works fine for development.

- Richard Lawler

-- 
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