Android system permissions
mukhiddin
project for reading DVD( all types ) discs and playing movies of this
discs. My task is porting this project to android x86 platform. Since
I
haven't much experience with android platform I involved some problems
with this task. I compiled source in Linux(Ubuntu 10.04) and in
NDK( for
x86 ). So the project consist of several .so files( shared libs ). As
I
know there only one way for for loading dynamic libs, it is with using
dlopens and dlsysms. But I don't want use this option, because our
source is very huge and with this option i have to provide linking for
each function within dlopens. I found out in android sources that c/c+
+
sources of projects which are coming within android platform are using
dynamic linking putting all .so files to the /system/libs. Then i also
tried in this this way, putting our project into android sources and
compile them with android itself. I think this way is suitable for us,
since our project would come with android x86 os. But the problem is
that file system is read-only. Some libs should write data in file,
but
since they are located in /system/libs, they cannot do such
operations.
I tried to change init.rc file. I gave 777 permission for almost all
folders and files except folder system and files in this folder. I
know
that it is not advised to give all permissions for folder system, but
i
need it only for testing purposes, it is not for final release
version.
How can i overcome this problem?
Thank you for your attention and help.
Sincerely,
Mukhiddin.
Chih-Wei Huang
in Android-x86.
Would you open source it?
Currently the /system dir is a compressed read-only
filesystem. But if put your libraries in the source tree and
rebuild the iso, you should get the libraries in /system/lib.
It's possible to make /system read-write-able,
if you are an experienced linux developer.
For example, you can create an ext3 partition
and copy /system to it, then change init.rc
to mount the partition to /system.
2010/11/24 mukhiddin <ymukh...@gmail.com>:
--
Chih-Wei
Android-x86 project
http://www.android-x86.org
mukhiddin
purposes, since we don't know which os would be installed in device
for which we are writing project. That's why I am not sure whether it
would be open source or not.
I'm not such a experienced linux developer. My android is installed in
sda6 and i have ext3 sda2. Can you explain me when i need copy /
system, after building and getting iso, or at the time of building. I
found this lines in init.rc
# mount ext3 /dev/block/sda6 /system
# mount ext3 /dev/block/sda6 /system ro remount
do i have to change it?
On Nov 24, 11:24 am, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> It's interesting to see a DVD player app
> in Android-x86.
> Would you open source it?
>
> Currently the /system dir is a compressed read-only
> filesystem. But if put your libraries in the source tree and
> rebuild the iso, you should get the libraries in /system/lib.
>
> It's possible to make /system read-write-able,
> if you are an experienced linux developer.
> For example, you can create an ext3 partition
> and copy /system to it, then change init.rc
> to mount the partition to /system.
>
Al Sutton
It would be far better to properly integrate the code, but for a proof of concept this would give you a quick route to show the value offered by Android-x86 and then you could go back and do a full integration once you get the OK .
Al.
> --
> You received this message because you are subscribed to the Google Groups "Android-x86" group.
> To post to this group, send email to andro...@googlegroups.com.
> To unsubscribe from this group, send email to android-x86...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
>