Hello,
I did run dexdump on the application. I did find an entry for
getNeighboringCellInfo() (see below). I don't know dexdump or dalvik
well enought to understand the entry. Do you? Perhaps, you can see if
something is amiss in the entry.
I am really puzzled because the dexdump entry for
getNeighboringCellInfo() on the surface is not different from that for
other methods.
I still wonder if there is some problem related to
getNeighboringCellInfo() itself and getting information about
neighboring cells as I have not been able to retrieve neighboring cell
information in any of the ways I have attempted it.
Thanks.
Alex Donnini
#10 : (in Landroid/telephony/TelephonyManager;)
name : 'getNeighboringCellInfo'
type : '()Ljava/util/List;'
access : 0x0001 (PUBLIC)
code -
registers : 3
ins : 1
outs : 1
insns size : 14 16-bit code units
1d8bcc: |[1d8bcc]
android.telephony.TelephonyManager.getNeighboringCellInfo:()Ljava/util/
List;
1d8bdc: 7010 4d36 0200 |0000: invoke-direct
{v2}, Landroid/telephony/TelephonyManager;.getITelephony:()Lcom/
android/internal/telephony/ITelephony; // met...@364d
1d8be2: 0c00 |0003: move-result-
object v0
1d8be4: 3800 0800 |0004: if-eqz v0,
000c // +0008
1d8be8: 7210 005d 0000 |0006: invoke-interface
{v0}, Lcom/android/internal/telephony/
ITelephony;.getNeighboringCellInfo:()Ljava/util/List; // met...@5d00
1d8bee: 0c01 |0009: move-result-
object v1
1d8bf0: 1101 |000a: return-object v1
1d8bf2: 0d01 |000b: move-exception
v1
1d8bf4: 1201 |000c: const/4 v1, #int
0 // #0
1d8bf6: 28fd |000d: goto 000a //
-0003
catches : 1
0x0000 - 0x0009
Landroid/os/RemoteException; -> 0x000b
positions :
0x0000 line=255
0x0004 line=256
0x0006 line=257
0x000a line=261
0x000b line=259
0x000c line=261
locals :
0x0004 - 0x000a reg=0 tel Lcom/android/internal/telephony/
ITelephony;
0x0000 - 0x000e reg=2 this Landroid/telephony/
TelephonyManager;
On Apr 30, 8:16 pm, fadden <fad...@android.com> wrote:
> On Apr 30, 4:48 pm, alexdonnini <alessdonn...@gmail.com> wrote:
>
> > In my application's source folder, I do have a
> > com.android.internal.telephony
> > package containing the necessary modules:
> [...]
> > I have also made sure that the standard
> > com.android.internal.telephony
> > be not included in the library referenced by the application
> > (otherwise it does not build)
>
> I'm not all that familiar with the telephony stuff, but it looks like
> it's included in framework.jar. Did you remove the classes from
> framework.jar?
>
> Bear in mind that a class loaded by your application's class loader is
> not the same as a class loaded by the bootstrap class loader. They
> can actually co-exist in the same app, though this gets confusing in a
> hurry. Without a deep understanding of what you're doing and how the
> telephony stuff is supposed to work, I can't provide a detailed
> explanation of why things aren't working.
>
> What I can tell you is that the verifier couldn't find the method in
> question. You may want to verify that it really exists by running
> "dexdump" on your .apk and examining the output.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"android-framework" group.
To post to this group, send email to android-framework@googlegroups.com
To unsubscribe from this group, send email to
android-framework+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-framework?hl=en
-~----------~----~----~----~------~----~------~--~---
