The typical method to obtain signal strength has been to extend the
PhoneStateListener class and override the onSignalStrengthsChanged
method. Anytime the signal strength changes the system will call this
method passing in the new ASU.
Since this method is now deprecated as of Android 2.0, how
is android.telephony.SignalStrength class. Let me
know if this works, doubt that it will be backwards compatible.
Ne0
On Nov 17, 1:46 am, Ken Adair kadai...@gmail.com wrote:
I'm assuming it is returning -1 because it is no longer being used
with 2.0?
--
You received this message because
That could be. If that is the case, I'd love to hear why. Doesn't seem
like it would be problematic or a security issue to provide such
access. Hopefully, we can get an official answer here soon.
On Nov 17, 1:48 pm, Rachel Blackman ceruleanspa...@gmail.com wrote:
On Nov 17, 2009, at 10:41 AM,
I second the SDK confusion. I was able to create a PhoneStateListener
and override the onSignalStrengthChanged method. However, the asu is
always -1. I am also testing on the Droid. Someone at Google please
advise.
Regards,
Ken
--
You received this message because you are subscribed to the
I'm assuming it is returning -1 because it is no longer being used
with 2.0?
--
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
Agree with the posters above. Please advise.
--
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
As anyone else encountered 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
To be more specific... is this the correct way to broadcast a GPS
setting change since I can't access the updateProviders() method
directly?
Intent intent = new Intent(Intent.ACTION_PROVIDER_CHANGED);
sendBroadcast(intent);
Thanks again,
Ken
To be more specific... is this the correct way to broadcast a GPS
setting change since I can't access the updateProviders() method
directly?
Intent intent = new Intent(Intent.ACTION_PROVIDER_CHANGED);
sendBroadcast(intent);
Thanks again,
Ken
To be more specific... is this the correct way to broadcast a GPS
setting change since I can't access the updateProviders() method in
the LocationManager directly?
Intent intent = new Intent(Intent.ACTION_PROVIDER_CHANGED);
sendBroadcast(intent);
Thanks again,
Ken
In one of my applications I am dynamically enabling the GPS system
setting based on a user's request. My problem is that I also have a
LocationListener which doesn't pick up this change. If the device is
restarted or the system settings Activity is brought up the
LocationListener kicks in -- the
I'm having this issue too...
On Oct 17, 11:00 pm, atrus123 [EMAIL PROTECTED] wrote:
I ended up rebuilding my workspace, and I haven't had any of the
strange editor errors since then.
On Oct 17, 7:37 pm, Anm [EMAIL PROTECTED] wrote:
I am very definitely using Java 1.5, as I'm using
This capability was in M5... guess someone changed their mind.
On Sep 9, 2:16 pm, Justin (Google Employee) [EMAIL PROTECTED] wrote:
but isn't that why you list an app's permissions before
installation (as shown in the marketplace screens)?
To some extent yes, but there are some permissions
13 matches
Mail list logo
