I will upload it here.
Post automatically merged:
I need OpenGL ES 3.0
Post automatically merged:
Hey I uploaded my ramdisk.img but it got disappeared after I posted it.
Post automatically merged:
..
Post automatically merged:
Will this be okay?
I removed .img and edited it to .zip and uploaded it.
You can override lower gl es version, but you cant fake to higher version.How to change OpenGL ES version without using gltool in darkmatter exo 4.7 beta 2?
I didn't understand clearly.You can override lower gl es version, but you cant fake to higher version.
To override, you have to edit init.android_x86_64.rc found in ramdisk.
Like this(pay attention to last line);
View attachment 1818
Available strings are; 2.0 | 3.0 | 3.1
yesI didn't understand clearly.
If my OpenGL ES version is 3.2 then can I change it to version 3.0?
I have to add the last text like you did in the screenshot above and save it?
Yes, and noI have to add the last text like you did in the screenshot above and save it?
And do I have to restart the system?
can I do it from APT tool or is there any other way to unpack and repack ramdisk?- to unpack the ramdisk, you must compile the kernel and the ramdisk if it is not compiled, the ramdisk cannot be unpacked (must be with the kernel in use).
- when it's repacked, change ramdisk-new.cpio.gz to ramdisk.img and copy and then overwrite the existing ramdisk.
I use AIK (Android Image Kitchen) when disassembling it is simple and easy.can I do it from APT tool or is there any other way to unpack and repack ramdisk?
No need to compile kernel, they are not even related.- to unpack the ramdisk, you must compile the kernel and the ramdisk if it is not compiled, the ramdisk cannot be unpacked (must be with the kernel in use).
- when it's repacked, change ramdisk-new.cpio.gz to ramdisk.img and copy and then overwrite the existing ramdisk.
You are sure?No need to compile kernel, they are not even related.
Yes, the tool you using does not support compressing method, but i guess it depends on windows.
I say are you sure even though I have provided a screenshot of what happens if the ramdisk doesn't compile.
I edit my message, simply read it.I say are you sure even though I have provided a screenshot of what happens if the ramdisk doesn't compile.
what you're saying I don't understand because in other applications it's the same when I try it. but indeed for phone models compilation with kernel is not required.Yes, the tool you using does not support compressing method, but i guess it depends on windows.
#unpack ramdisk (must be executed at root directory, which contain ramdisk.img)what you're saying I don't understand because in other applications it's the same when I try it. but indeed for phone models compilation with kernel is not required.
mkdir ramdisk && ( cd ramdisk && zcat ../ramdisk.img | cpio -iud )
cd ramdisk && find . | cpio -o -H newc | gzip > /ramdisk_new.img
For linux users it will be easy to unpack and repackage the ramdisk it seems. but I'm still using windows OS as primary so I won't use this method.#unpack ramdisk (must be executed at root directory, which contain ramdisk.img)
mkdir ramdisk && ( cd ramdisk && zcat ../ramdisk.img | cpio -iud )
# repack ramdisk (must be executed at root directory, which contain ramdisk folder)
cd ramdisk && find . | cpio -o -H newc | gzip > /ramdisk_new.img
"well i am own of that syntax, it just works xD"
you can excute them on darkmatterFor linux users it will be easy to unpack and repackage the ramdisk it seems. but I'm still using windows OS as primary so I won't use this method.
I think that's part of how the gearlock works when it's executed the first time.you can excute them on darkmatter
You should start using linux distro anyway.I think that's part of how the gearlock works when it's executed the first time.
Post automatically merged:
thanks for the info maybe i can do something from this way.