Android native mention permissions problem

running in the background adb shell push to use a native file into the / data / what directory below.
then use the shell chomd 0777 to enhance the native authority.

Finally shart a native

I am now wondering if there was any way I put this inside native added to an APP packaged into an APK. Then on the phone after installing APK. Allows applications to perform those actions performed adb

My idea is it possible to configure some stuff in the manifest.xml inside. Then let the APP has certain privileges native can put / data / down and elevate his privileges as 0777, running him.
------ Solution ---------------------------------------- ----
need root privileges
------ Solution ----------------------------- ---------------
native itself 777 wool useless ...
------ Solution ---------- ----------------------------------

Dude, I have a certain respect screenshots research, JNI basic feasible way, unless you are doing system applications
------ Solution ------------------------- -------------------
APP no authority to engage in this, unless the root over
------ reference -------- -------------------------------
buddy, you drop a good idea, but the only problem is impossible APP have permission to put the native / data / directory, not a cell phone unless the root, while your program also received root privileges.
------ reference --------------------------------------- < br> Thank you. .
777 but it executable permissions. The key is to put / data below.
I now think it is not so you can engage in a library file. Then with APP removed.
because I was going to do a screen capture of the broken thing. . . Grab framebuffer. .
left. .
------ reference --------------------------------------- < br>
Dude, I have a certain respect screenshots research, JNI basic feasible way, unless you are doing system applications  

Haha, brother I tried. . .
really is not feasible. / Dev/graphics/fb0 this device files generally have root privileges APP is writable read.
followed by adding graphics group of users can write to read. Other users do not have permissions. Set inside the manifest.xml FrameBuffer read permission will be reported than the system can not obtain APP.

Android permissions above these limits are too annoying.
If people do now Android screencast transferred to a PC client. There is a feasible method is, PC-side call ADB procedures put fb0 change the permissions on the device files that other users can read and write operations. Then you can write a native application or write a native library to read FrameBuffer the SO.
------ reference --------------------------------------- < br>
Dude, I have a certain respect screenshots research, JNI basic feasible way, unless you are doing system applications    

  

  
  
Haha, brother I tried. . .   
really is not feasible. / Dev/graphics/fb0 this device files generally have root privileges APP is writable read.   
followed by adding graphics group of users can write to read. Other users do not have permissions. Set inside the manifest.xml FrameBuffer read permission will be reported than the system can not obtain APP.   
  
Android permissions above these limits are too annoying.   
If people do now Android screencast transferred to a PC client. There is a feasible method is, PC-side call ADB procedures put fb0 change the permissions on the device files that other users can read and write operations. Then you can write a native application or write a native library to read FrameBuffer the SO.  

"PC-side call ADB procedures put fb0 change the permissions on the device files that other users can read and write operations" Brother, this can be achieved? Can pointers twelve?