in february next year.
Thanks in advance!
Heiko
The work is supported by the University of Applied Sciences Darmstadt
(h_da) and the Center for Advanced Security Research Darmstadt (CASED)
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post
but nothing helps...
I hope somebody can help me out.
Thanks!
Heiko
--
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
month ago. Somthing changed and I don't
know what it is.
If anybody has a solution fixing this I would appreciate any help.
Thanks!
Heiko
--
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
corrections or suggestions.
Regards
Heiko
--
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
/1T253P041O0R2m1U3Z1V
How does android process events in case of high CPU load? Does it
collect events and then sends many of them in a burst phase to the
handler of an app?
Best
Heiko
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send
the permission in the manifest) is installed, but
unfortunately isn't.
It does not even help to re-install the receiver. The only way to
resolve the issue is to completely uninstall the receiver application
and do a fresh install.
Is this behaviour intended (not a bug, a feature)?
Cheers,
Heiko
Hi again,
afaik there is no way to determine the sender of an (explicit) intent.
Every intent should hold an instance variable with the package and
class name of the sender. This would be a great way to verify the
source.
What are your thoughts about this?
Cheers,
Heiko
P.S
Mark, thanks a lot for the answer!
On Sep 15, 1:10 pm, Mark Murphy mmur...@commonsware.com wrote:
On Wed, Sep 15, 2010 at 4:33 AM, Heiko heiko.wi...@gmail.com wrote:
Is this behaviour intended (not a bug, a feature)?
Based on a previous discussion of this topic in this group, I think
), but the sample rates average around 85 on these
devices (reliable).
Any word on the reliability of the SensorEventListener? I am kind of
stuck here at the moment...
Cheers
Heiko
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post
Problem solved. In case others experience the same problems:
The constants for the sensors seem to be wrong. I used: getSensorList
(SensorManager.SENSOR_ACCELEROMETER).get(0); which returned a handle
to the magnetic field sensor. Also the Sensor.TYPE_ACCELEROMETER
constant returned a wrong
.
Thanks in advance.
Heiko
--
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
11 matches
Mail list logo
