That's why if you were to write the same code natively in the NDK, you
would get the same result, even though it's native code.
Yusuf Saib
Android
·T· · ·Mobile· stick together
The views, opinions and statements in this email are those of the
author solely in their individual capacity, and do not necessarily
represent those of T-Mobile USA, Inc.
On Aug 6, 1:42 pm, Jason Proctor <jason.android.li...@gmail.com>
wrote:
> oh i'm sorry, i had a brainfade reading your post.
>
> i should have said that /dev/graphics/fb0 is mode 660, which means
> unless you're root or in group 1003 then you can't read it. maybe the
> native process runs setgid or something, which enables it to happen.
>
> maybe the internals guys can say more, but right now it looks like
> this device isn't available to regular SDK apps.
>
>
>
>
>
> >Sorry to be slow, but I thought the code I posted IS trying "/dev/
> >graphics/fb0" and not "/dev/fb0". What am I missing?
>
> >On Aug 6, 10:53 am, Jason Proctor <jason.android.li...@gmail.com>
> >wrote:
> >> on my machine at least, fb0 is in /dev/graphics, rather than /dev.
>
> >> you might try that...
>
> >> >I noticed that in the native code, the way they capture the
> >> >framebuffer data is by calling "int fb = open("/dev/graphics/fb0",
> >> >O_RDONLY);"
>
> >> >I tried to do that with Java, by calling "File f = new File("/dev/
> >> >graphics/fb0");" but I get a "file not found" exception.
>
> >> >Any idea why?
>
> >> --
> >> jason.software.particle
>
> --
> jason.software.particle
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
