Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FBIOGET_FSCREENINFO Bad file descriptor #12

Open
GoogleCodeExporter opened this issue Feb 28, 2016 · 2 comments
Open

FBIOGET_FSCREENINFO Bad file descriptor #12

GoogleCodeExporter opened this issue Feb 28, 2016 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Launch native binary from /data/data/app/binary using ProcessBuilder

What is the expected output? What do you see instead?
A screenshot is made. Binary exits.

What version of the product are you using? On what operating system?

Android 2.3.6, Nexus One; not rooted.

Here's a logdump:

I/LogThread(21851): Program initialized
I/LogThread(21851): Starting server...
I/LogThread(21851): - Socket creation
I/LogThread(21851): - Socket binding
I/LogThread(21851): - Socket in listening mode
I/LogThread(21851): Server started.
I/LogThread(21851): Listening on 0.0.0.0:42380
I/LogThread(21851): Signal handling setup
I/LogThread(21851): Starting main loop.
I/LogThread(21851): << select() on sockets... >>
I/LogThread(21851): Incoming client connection
I/LogThread(21851): - Connection accepted
I/LogThread(21851): << select() on sockets... >>
I/ScreenshotService(21851): Error writeImageFile: null
I/LogThread(21851): Client socket signaled for input
I/LogThread(21851): - Retreiving data
I/LogThread(21851): - Command identified as SCREEN
I/LogThread(21851): - Taking screenshot
I/LogThread(21851): An error occured: ioctl FBIOGET_FSCREENINFO Bad file 
descriptor
I/LogThread(21851): Exiting now...


Original issue reported on code.google.com by genn...@codeseekah.com on 21 Mar 2012 at 8:18

@GoogleCodeExporter
Copy link
Author

By default native servce access fb0 Framebuffer but In latest mobiles like 
Samsung Galaxy S3 there are multiple frame buffers like fb0, fb1, fb2..... and 
none of them is accessible. I need to understand which one is the primary 
buffer where I can get Frames. Can someone please help me with this ?

Original comment by DIPI24...@gmail.com on 8 Jan 2014 at 6:07

@GoogleCodeExporter
Copy link
Author

I am facing the same issue, on an Xperia Neo. If I understood the problem 
correctly, we can take screenshots without root permissions only when the 
framebuffer is readable from everyone.

Original comment by alessand...@gmail.com on 20 May 2014 at 7:18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant