disable screen orientation in sound and display settings and reboot the
emulator. it's work for me
--
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
Hi Jiaoni,
I still look forward to an officer's or groupmate's answer.
I have only one CPU. But I think we encountered almost the same
situation.
Maybe I should reinstall my operating system although it has been
WinXP SP2.
Or it is because my OS is Chinese version? (I guess you come from
China)
Hi All,
Mine is also occupying 100% CPU. I am a fresh man and just now created
a HelloWorld in Eclipse. When I ran it as an Android application,
after a while, it keep 100% occupying some minutes and only the text
Android_ with black background in the emluator.
My OS is Windows XP and Eclipse
Mine is also occupying 100% CPU. I am a fresh man and just now created
a HelloWorld in Eclipse. When I ran it as an Android application,
after a while, it keep 100% occupying some minutes and only the text
Android_ with black background in the emluator.
My OS is Windows XP and Eclipse is 3.4. I
Hi Chauncey,
Yes, sometimes I encountered such situation like yours, the emulator
stopped at the Android.. stage and never moved on. I had to kill and
restart it.
However, my above situation is a bit different, that the emulator is
actually working, but it's always occupying 100% cpu. Although
Hi Dianne,
Thanks. I tried adb shell top -t command, and here is the result:
PID TID CPU% S VSS RSS UID Thread Proc
578 784 83% R 191676K 23200K system er$SensorThread
system_server
788 788 8% R948K412K root top top
And according
Hi David,
I don't use Linux now, so I have not tries it.
Thanks,
Jiaoni
On Aug 21, 7:35 pm, David Wilson d...@botanicus.net wrote:
Are you on Linux? You could try this.. From a terminal:
killall -STOP emulator
To pause it while not in use, and:
killall -CONT emulator
To
Hi,
Thanks for the replies. Here's my situation:
1. I am running emulator on windows XP;
2. when show top in adb shell console, the system_server process
occupies the most cpu;
Thanks a lot,
Jiaoni
On Aug 21, 7:35 pm, David Wilson d...@botanicus.net wrote:
Are you on Linux? You could try
Okay, so something in the system itself is running a lot. adb shell top
-t might be able to isolate that more (showing individual threads).
On Sat, Aug 22, 2009 at 12:22 AM, jiaoni jiaoni5...@gmail.com wrote:
Hi,
Thanks for the replies. Here's my situation:
1. I am running emulator on
This is a known bug. I reported it back in June. A work around is
provided by the Google developer in the bug thread.
http://code.google.com/p/android/issues/detail?id=3099
On Aug 21, 2:57 am, jiaoni jiaoni5...@gmail.com wrote:
Hi,
Many times (not all the times), my emulator is running 100%
Which platform are you running your emulator on?
--
Jack Ha
Open Source Development Center
・T・ ・ ・Mobile・ stick together
The views, opinions and statements in this email are those of
the author solely in their individual capacity, and do not
necessarily represent those of T-Mobile USA, Inc.
What do you see in adb shell top?
On Fri, Aug 21, 2009 at 12:57 AM, jiaoni jiaoni5...@gmail.com wrote:
Hi,
Many times (not all the times), my emulator is running 100% of one of
my two CPUs on the machine.
Can anyone tell me why it is so, and how can I reduce the cpu usage?
Thanks a lot,
Are you on Linux? You could try this.. From a terminal:
killall -STOP emulator
To pause it while not in use, and:
killall -CONT emulator
To unpause it. Note doing this might screw up the emulator's idea of
the current time, but I've used this lots of times in the past with
other Qemu
13 matches
Mail list logo
