On Wed, May 27, 2009 at 1:40 PM, sarang sarangd...@gmail.com wrote:
Is this a bug in emulator 1.5 ?
Yes, it's a known bug in the 1.5 emulator which will be fixed in the next
SDK release.
However, what others have mentioned is true, there is little you will be
able to do in the emulator
Unless of course one has a sensor simulator :-)
http://code.google.com/p/openintents/wiki/SensorSimulator
(I should mention that we did not have time yet to upgrade it to SDK
1.5, but some people already got this to work in the 1.5 emulator).
I'd say simulating the sensors in this way can be
Actually, the sensor code I had written with the SensorSimulator
( http://code.google.com/p/openintents/wiki/SensorSimulator ) before
any Android hardware was available publicly, worked perfectly on the
G1 when it came out - apart from the known issues with the wrong
orientation sensor values
Firstly, openIntents sensor simulator is a very good tool for compass
applications. I have used it without any breakage..
Further,, the compass bug in 1.5 r1 is FIXED in SDK 1.5 r2. Go
ahead, there's no breakage now.
Cheers.
Peli wrote:
Unless of course one has a sensor simulator
I am going to strongly, strongly recommend that people test such code on a
real device. I don't know what you were doing, but every case I know of
using sensors required a fair amount of tuning on the device to achieve the
right feel. For example, the auto-rotation code went through many many
On Jun 26, 10:03 am, Dianne Hackborn hack...@android.com wrote:
I am going to strongly, strongly recommend that people test such code on a
real device. I don't know what you were doing, but every case I know of
using sensors required a fair amount of tuning on the device to achieve the
right
There is a considerable amount of development that can be done, even
without actual sensor hardward. Having to comment out all sensor
related code to get graphics, keystrokes and all the other minutia
working is not productive. The emulator really needs to get fixed.
Rud
On Jun 25, 8:32 pm,
I just tried to run a Compass example in r2 and it hung on getting the
sensor manager. I don't think the bug is fixed and isn't just a
compass bug.
But if you have any suggestions I am open to trying them.
@L!TH!UM - I also am a long time embedded developer. Yes, you have to
get onto the real
Is there any update on this?
I need to build a compuss application but the API Demo doesn't work in
the emulator.
You will need actual hardware to test sensor-related applications. Partly,
this is due to the emulator bug.
--
Mark Murphy (a Commons Guy)
http://commonsware.com
Android App
Is there any update on this?
I need to build a compuss application but the API Demo doesn't work in
the emulator.
Thanks,
Declan
DeathStick.org
On May 29, 3:12 am, Sahil Arora sahilz...@gmail.com wrote:
Hi,
What do u mean by a virtual box??
Regards,
Zhubham.
On Thu, May 28, 2009 at 7:00
But also, there is no way you are going to be able to implement a
working app like this without doing it on real hardware. It would be
kind-of like trying to implement a touch user interface without a
touch screen. :)
On Thu, Jun 25, 2009 at 10:05 AM, Mark Murphymmur...@commonsware.com wrote:
Yes, this is a known bug in the emulator.
On Wed, May 27, 2009 at 4:40 AM, sarang sarangd...@gmail.com wrote:
I have been trying to use the OS-sensor and graphics-compass in the
APIDEMO (through emulator 1.5) by directly browsing through the menu
or through instrumentation, I have observed
Hi,
What do u mean by a virtual box??
Regards,
Zhubham.
On Thu, May 28, 2009 at 7:00 PM, Brett Chabot brettcha...@android.comwrote:
Yes, this is a known bug in the emulator.
On Wed, May 27, 2009 at 4:40 AM, sarang sarangd...@gmail.com wrote:
I have been trying to use the OS-sensor and
13 matches
Mail list logo
