My application does have
<uses-permission
android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission
android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission
android:name="android.permission.ACCESS_COARSE_UPDATES" />
Here is an example of the fialure I referred to in my message:
This code:
ArrayList<NeighboringCellInfo> mNeighboringCellInfo;
mNeighboringCellInfo = new ArrayList<NeighboringCellInfo>
();
mNeighboringCellInfo = (ArrayList)
mTelephonyManager.getNeighboringCellInfo();
for(int i = 0; i < mNeighboringCellInfo.size(); ++i)
{
System.out.println("mNeighboringCellInfo.get(i) -
"+mNeighboringCellInfo.get(i));
}
generates this failure:
05-29 16:46:08.981: WARN/dalvikvm(5415): VFY: unable to resolve
virtual method 13918: Landroid/telephony/
TelephonyManager;.getNeighboringCellInfo ()Ljava/util/List;
05-29 16:46:08.981: WARN/dalvikvm(5415): VFY: rejecting opcode 0x74
at 0x013a
05-29 16:46:08.981: WARN/dalvikvm(5415): VFY: rejected Lcom/android/
commmanager/CommManager;.onCreate (Landroid/os/Bundle;)V
05-29 16:46:08.981: WARN/dalvikvm(5415): Verifier rejected class Lcom/
android/commmanager/CommManager;
05-29 16:46:08.981: WARN/dalvikvm(5415): Class init failed in
newInstance call (Lcom/android/commmanager/CommManager;)
05-29 16:46:08.991: WARN/dalvikvm(5415): threadid=3: thread exiting
with uncaught exception (group=0x40013e28)
Could you send the community an example of code where you were
successful in using getNeighboringCellInfo()? It would help all of us
who have not been able to get getNeighboringCellInfo() to work,
correct our mistakes.
Thanks.
On May 29, 4:24 pm, Mark Murphy <[email protected]> wrote:
> alexdonnini wrote:
> > I have low expectations that this message will get any response as it
> > seems that Google developers do not like to address issues too close
> > to the Android core and to strategic mobility applications.
>
> Do you honestly think insulting "Google developers" will improve your
> chances of getting answers?
>
> > Yet, getNeighboringCellInfo() does not work. Any attempt to call it in
> > an application results in application failure.
>
> File a bug report athttp://b.android.com. I didn't find any issues
> referencing that method. If you can attach a project that reproduces the
> issue, so much the better.
>
> BTW, the Android 1.5 docs say you need the ACCESS_COARSE_UPDATES
> permission -- do you hold that permission? That might be a documentation
> bug, in that I cannot find any other reference to that permission, so
> you might also try ACCESS_COARSE_LOCATION. None of that would seem to
> line up with the stack trace you posted in that one thread, but you
> never know...
>
> --
> Mark Murphy (a Commons
> Guy)http://commonsware.com|http://twitter.com/commonsguy
>
> Need Android talent? Ask on HADO!http://wiki.andmob.org/hado
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
