Hi Developers,
This is about FileObserver Bug. I am using FileObserver in my application
to keep track of newly created, deleted and modified files (images, video,
MS Word document and PDF files). I am successful in handling these events
in Lollipop but partially successful in Marshmallow.
D
Hi Developers,
This is about FileObserver Bug. I am using FileObserver in my application
to keep track of newly created, deleted and modified files (images, video,
MS Word document and PDF files). I am successful in handling these events
in Lollipop but partially successful in Marshmallow.
D
See an open bug:
http://code.google.com/p/android/issues/detail?id=12479
--
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
Indeed I was suprised too. I found this post from an android.com
offical stating the docs are wrong and sub-folders are NOT watched.
Which does match what I'm seeing in my app. Too bad really ... that
would be an excellent feature!
http://groups.google.com/group/android-platform/browse_thread/thr
Hi Freddy,
strange .. I thought the FileObserver uses Linux native call
"inotify" ,
which is able to send events for directories too,
What definitly will not work is FileObserver for sysfs entries.
Good luck ! Frank
On 12 Okt., 00:41, Freddy wrote:
> ok. I found more info. Apparently the d
ok. I found more info. Apparently the docs are incorrect.
FileObserver does not support recursive file watching.
On Oct 11, 1:50 pm, Freddy wrote:
> The FileObserver class doesn't appear to be working as advertised.
>
> I created a class extending the FileObserver class. I initialize the
> cla
Hi,
Thanks for the help. Yes, my class name was also FileObserver. Now
managed to resolve it.
Regards,
Perumal
On Jul 12, 6:49 pm, Mark Murphy wrote:
> On Mon, Jul 12, 2010 at 2:31 AM, perumal316 wrote:
> > I want to observe the changes made to the filesystem. I am reposting
> > as previously
thanks solved it. instead of creating in separate threads i did it in
single thread by creating an instance of fileobserver for each
directory and calling startwatching(); in a loop.
On Feb 4, 11:03 pm, Dianne Hackborn wrote:
> You don't need to create any threads to use FileObserver -- it is
>
what if I have to observe 2 or more folders (or paths)? even then
threads are not required?
how to register callbacks?
On Feb 4, 11:03 pm, Dianne Hackborn wrote:
> You don't need to create any threads to use FileObserver -- it is
> callback-based.
>
> On Tue, Feb 3, 2009 at 11:27 PM, pradeep w
You don't need to create any threads to use FileObserver -- it is
callback-based.
On Tue, Feb 3, 2009 at 11:27 PM, pradeep wrote:
>
> i need to observe a sdcard i.e all the folders inside. i am creating
> fileobservers for each folder in saparate threads, but i don't think
> it is efficient. is
10 matches
Mail list logo