Another note: You don't really have to flash the image with the @hide gone, that class will be accessible by any APK. You just need to have it visible in your development environment.
-Zach On May 12, 1:05 pm, Alin Radut <alin.claudiu.ra...@gmail.com> wrote: > On May 12, 7:00 am, Zach Hobbs <ho...@helloandroid.com> wrote: > > > Did you change anything when you built the SDK? If not, then the > > classes will still not be visible. > > > Hint: classes or methods with "@hide" in the comment block above the > > code are not visible in the jar built for the SDK. > > I removed the @hide from RfcommSocket.java and after a lengthy 4 hour > compile now it shows up in the .jar file. > > The problem is that after I flashed the device with the img files I > can't access the Wireless controls screen because it crashes. It > appears that there is a problem with the bluetooth A2DP service. The > adb logcat output is available here:http://clawoo.ro/pub/logcat.txt > and the traces.txt file is available here:http://clawoo.ro/pub/traces.txt > > The problem is that I cannot enable the bluetooth service if I cannot > access that screen so I cannot test if I can interact with RFCOMM as I > need. Do anyone have any idea why the wireless controls screen > crashes and what can I do about it? > > Thanks, > Alin --~--~---------~--~----~------------~-------~--~----~ 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 For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
