Isn't looking for battery change intent not really a neat thing to do?
Can it not be possible to look for USB connect and disconnect uevents
in the uevent observer thread and have an intent broadcast for USB
disconnect and connect?

On Aug 3, 12:37 pm, Dianne Hackborn <hack...@android.com> wrote:
> All @hide does is prevent the associated symbols from being exposed in the
> SDK.  The code is still built.
>
>
>
> On Sun, Aug 2, 2009 at 11:12 PM, riazrahaman <rahaman.r...@gmail.com> wrote:
>
> > I find that the code under /frameworks/base/core/java/com/android/
> > internal to have a few package.html files with "@hide" string, there
> > by hiding all the code in those folders. Also some functions in the
> > code located in those locations have the "@hide" to find a few
> > functions.
>
> > As per my understanding this might be done to not build the code for
> > SDK. How do I get this build for other than SDK? I am interested in
> > the files
>
> >    * UsbStorageActivity.java
> >    * UsbStorageStopActivity.java
>
> > Removed @hide from all the package.html and files under internal
> > folder. After that I am getting an error in R.java built for internal.
>
> > Can any one share information on how to build this code and is there
> > any particular reason other than not build for SDK for hiding this
> > code?
>
> > I could see that some folks have got to build the UsbStorage*.java
> > files (http://osdir.com/ml/android-porting/2009-05/msg00539.html)
> > but no information shared on how to get this enabled.
>
> --
> Dianne Hackborn
> Android framework engineer
> hack...@android.com
>
> Note: please don't send private questions to me, as I don't have time to
> provide private support, and so won't reply to such e-mails.  All such
> questions should be posted on public forums, where I and others can see and
> answer them.
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to