Database Users

[GUIDE] Make VooDoo Settings Stick on Boot

FIRST: Supercurio makes a really awesome app, so I highly recommend purchasing the pro version to support further development for two reasons. First, it's the right thing to do and second, I haven't figured out how to make all of the VooDoo sound settings work yet, and I'm a busy college student in my senior year attempting to convince someone to pay me, so I don't have much time on my hands (thus my erratic shower schedule).
That being said, I have attached a script that I run on boot. That being said, I'm running AOSP's oiCSv43 ROM with Eugene's Speedy 2 kernel. So long as your kernel supports the following options (which will be listed below), you shouldn't have a problem with this script. I've also verified that it works just peachy with GLaDOS 2.5 for ICS-- another very good ICS kernel [I head 2.6 is quite nice]. (This should also work for GB roms if anyone cares to test for me)
You must have
root
superuser
busybox, or an alternate way to mount /system as writable (there are 2 other methods AFAIK)
ROM that supports init.d scripts OR scripter or some other app like it (in this case, you can just add the script to scripter and set it to run on boot)
If you don't (know if you) have init.d support, check out this post by damnmisur about scripting with ROM Toolbox
This script changes the following:
cpu governor -> interactive
max freq->1000mhz
min freq->150mhz
touchwake enabled with 10 second delay
back light dimmer settings are commented out, so it uses whatever is default for you kernel
bln enabled with blink disabled
blx commented out (reverts to kernel default which is likely 96%)
voodoo_color/red_multiplier->2724764160
voodoo_color/green_multiplier->3059586880
voodoo_color/blue_multiplier->2944130880
voodoo_color/red_v1_offset->-26
voodoo_color/green_v1_offset->-30
voodoo_color/blue_v1_offset->-33
voodoo sound anti-jitter, hi-fi play, hi-fi record, dac direct, voodoo sound control enabled
headphone_amplifier_level->+3db
voodoo sound mono downmix disabled
USE AT YOUR OWN RISK! I AM NOT LIABLE IF ANYTHING GOES WRONG!!!
NANDROID NANDROID NANDROID.
ALWAYS MAKE A BACKUP
NANDROID
The script is in the zip. To install:
Unzip archive into same directory as adb (or wherever you want if you know what you're doing)
open a terminal
Code:
adb remount
adb shell
su
busybox mount -o remount,rw /system
exit
adb push 99whirlpool-Speedy_2 /system/etc/init.d/99whirlpool-Speedy_2
adb shell
chmod 755 /system/etc/init.d/99whirlpool-Speedy_2 && reboot
The file has no extension! If you want to edit it, open it in a text editor. If you don't know what you're doing, don't play with it. To disable boolean values, change the 1 (1 means true i.e. on) to a 0 (which means false, i.e. off).
frequency values are in hertz
you can find out what scaling governors and frequencies your kernel supports by typing
Code:
adb shell
su
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
Feel free to edit anything you'd like!
DO NOT FLASH THE .ZIP FILE! Extract and follow the directions above

thanks....

Nice but some of your changes are the exact opposite of what I use. So I'll just change voodoo settings because I'll be a lot less to change with every boot than if I was to use this.
I do of course use easy settings. Color multipliyer: all the way right.
Gama: all the way left.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.

Thank you.

Don't voodoo settings stick by default? It seems my voodoo settings stick just fine without using any script?

Si_NZ said:
Don't voodoo settings stick by default? It seems my voodoo settings stick just fine without using any script?
Click to expand...
Click to collapse
They do with the PRO version, not the free one. I've also never had a problem with them NOT sticking on Pete Alfonso's GPA19, or any GB ROM for that matter, but many ICS users, including myself, have not been able to get our settings to stick recently.
This also means that I don't have to use NSTools or VooDoo Control.
Translation:
no apps changing settings on boot->
fewer individual SU requests (count the number of toast notifications, or check the request list in the superuser app for NSTools and VooDoo control on boot)->
faster boot sequence, and less lag on boot.
Not everyone may have this problem, but I and others do.

I'm visiting for a lesson, had read this before on aosp's or Eugene's kernel threads, but didn't get it so, wanted to ask and thank you for this help.
I'm trying to make voodoo stick, I downloaded your zip, opened and changed a couple of things in Wordpad, it asked to save and rezip, said yes. I used different multipliers and want bln to blink, so changed those numbers and the blink 0 to 1 (or vice versa, followed your directions).
So to do this, do I just flash zip in recovery? Any wipe or just flash away??
Like you said, I will backup, but really don't want to make a mess and thought I would double check first.

nmoreman said:
I'm visiting for a lesson, had read this before on aosp's or Eugene's kernel threads, but didn't get it so, wanted to ask and thank you for this help.
I'm trying to make voodoo stick, I downloaded your zip, opened and changed a couple of things in Wordpad, it asked to save and rezip, said yes. I used different multipliers and want bln to blink, so changed those numbers and the blink 0 to 1 (or vice versa, followed your directions).
So to do this, do I just flash zip in recovery? Any wipe or just flash away??
Like you said, I will backup, but really don't want to make a mess and thought I would double check first.
Click to expand...
Click to collapse
Don't flash the zip. It's just there so that I could upload the attachment properly.
The script is in the zip. To install:
Unzip archive into same directory as adb (or wherever you want if you know what you're doing)
open a terminal
Code:
adb remount
adb shell
su
busybox mount -o remount,rw /system
exit
adb push 99whirlpool-Speedy_2 /system/etc/init.d/99whirlpool-Speedy_2
adb shell
chmod 755 /system/etc/init.d/99whirlpool-Speedy_2 && reboot
I'll add a readme to the zip to make it more obvious.

Shark_On_Land said:
Nice but some of your changes are the exact opposite of what I use. So I'll just change voodoo settings because I'll be a lot less to change with every boot than if I was to use this.
I do of course use easy settings. Color multipliyer: all the way right.
Gama: all the way left.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
Click to expand...
Click to collapse
If your just worried about voodoo settings you could do the following :
http://forum.xda-developers.com/showthread.php?t=1366780 or just use the script from this method. Of course you have to edit numbers to your preference.
Sent from my Skanky Nexus S in the Matr1x using XDA App

damnmisur said:
If your just worried about voodoo settings you could do the following :
http://forum.xda-developers.com/showthread.php?t=1366780 or just use the script from this method. Of course you have to edit numbers to your preference.
Sent from my Skanky Nexus S in the Matr1x using XDA App
Click to expand...
Click to collapse
Thanks, I'm going to add this post to the OP as an alternative for those without init.d support

[Call for Help] Kernel Parameters - ro.secure

Ccurrently trying to get the SkyGO app working on the HD2.
One of the devs has suggested that for the app to work properly we need a Kernel with "ro.secure=1" set in it.
Currently I am bouncing between Typhoon 3.7.6 (which uses tytung's r14 kernel) and NexusHD2-ICS-4.0.3 (tytungs ICSr1 Kernel I believe)
Can anyone tell me how to find out if the kernel has this parameter set. If not how easy would it be for me to add it and recompile the kernel (pointers to kernel de/recompilation threads appreciated!
I'm not to worried about doing it myself if I have to.
TIA
mods - if this is in the wrong forum I apologise in advance, could you move it for me if it is

bobjbain said:
Ccurrently trying to get the SkyGO app working on the HD2.
One of the devs has suggested that for the app to work properly we need a Kernel with "ro.secure=1" set in it.
Currently I am bouncing between Typhoon 3.7.6 (which uses tytung's r14 kernel) and NexusHD2-ICS-4.0.3 (tytungs ICSr1 Kernel I believe)
Can anyone tell me how to find out if the kernel has this parameter set. If not how easy would it be for me to add it and recompile the kernel (pointers to kernel de/recompilation threads appreciated!
I'm not to worried about doing it myself if I have to.
TIA
mods - if this is in the wrong forum I apologise in advance, could you move it for me if it is
Click to expand...
Click to collapse
This is a question. [Q&A]

yz.hd said:
This is a question. [Q&A]
Click to expand...
Click to collapse
Thanks for the useful and insightful response
FYI - I realised that it might be after I submitted it! Which is why I caveated the post at the end.

this parameter is in the initrd.gz in the kernel in the boot folder of the ROM.
You should extract it and inside there is a file called default.prop
extract
mkdir initdir
cd initdir
zcat ../initrd.gz | cpio -i -d
compress
cd initdir
find . | cpio -o -H newc | gzip -9 > ../initrd.gz
Each line in the file default.prop is an attribute assignment. There we need to
Note the two properties: ro.secure, and ro.debuggable. . If ro.secure = 0 is allowed us to run the adb root command.
Usually we put the core ROOT refers to the ro.secure = 0. ROOT permission to refer to the general said on the phone
A license management program (Superuser.apk) procedures for the root user can grant permission.

bobjbain said:
Ccurrently trying to get the SkyGO app working on the HD2.
One of the devs has suggested that for the app to work properly we need a Kernel with "ro.secure=1" set in it.
Currently I am bouncing between Typhoon 3.7.6 (which uses tytung's r14 kernel) and NexusHD2-ICS-4.0.3 (tytungs ICSr1 Kernel I believe)
Can anyone tell me how to find out if the kernel has this parameter set. If not how easy would it be for me to add it and recompile the kernel (pointers to kernel de/recompilation threads appreciated!
I'm not to worried about doing it myself if I have to.
TIA
mods - if this is in the wrong forum I apologise in advance, could you move it for me if it is
Click to expand...
Click to collapse
look here this great kernel should have ro.secure set to 1

Bologna said:
look here this great kernel should have ro.secure set to 1
Click to expand...
Click to collapse
it doesn't, it's based on Tytung's Kernel, Tytung's doesn't so I'm not suprised that dorimnax's "greatest ever" (sic) doesn't teither

big thanks to magnus48, have decompressed the kernel, changed ro.secure to 1, recompressed, copied to /boot
Phone booted (which suprised me) and my SkyGo App now works.
Yay

magnus48 said:
The easy way is use root explorer and edit /default.prop on your device but is not free.
ro. means read only you can't change it's value after rom is loaded
Click to expand...
Click to collapse
So, I can either change the value in my kernel OR I can edit default.prop and reboot??
Won't the values in default.prop get overwritten on boot??

bobjbain said:
it doesn't, it's based on Tytung's Kernel, Tytung's doesn't so I'm not suprised that dorimnax's "greatest ever" (sic) doesn't teither
Click to expand...
Click to collapse
First question : Why of this sarcastic reply?
Second question : Can you please share your skygo working app, telling us what's the kernel you're using to have it working?
Thanks in advance

bobjbain said:
So, I can either change the value in my kernel OR I can edit default.prop and reboot??
Won't the values in default.prop get overwritten on boot??
Click to expand...
Click to collapse
forget this way. It did not work when rebooting the kernel overwrites the deafult.prop file.
The change should be done inside initrd.gz

magnus48 said:
forget this way. It did not work when rebooting the kernel overwrites the deafult.prop file.
The shange should be done inside initrd.gz
Click to expand...
Click to collapse
You should be able to pull it, make changes and push it back to phone via adb. Useful if you don't want to reflash
Sent from my HD2 using XDA

jwchips said:
You should be able to pull it, make changes and push it back to phone via adb. Useful if you don't want to reflash
Sent from my HD2 using XDA
Click to expand...
Click to collapse
default.prop is in the initrd.gz, this is extracted when the phone boots, so any changes you make to default.prop WILL be overwritten when the phone boots.
You have to make the changes inside the initrd.gz file.

Bologna said:
First question : Why of this sarcastic reply?
Click to expand...
Click to collapse
I don't quite hold dorimanx in quite the high esteem that others do, his work is good but it can be rushed as shown by his 5.x series of Kernels.
Bologna said:
Second question : Can you please share your skygo working app, telling us what's the kernel you're using to have it working?
Thanks in advance
Click to expand...
Click to collapse
Here although this is an app for UK Sky only and won't work for non-UK subscribers.

bobjbain said:
default.prop is in the initrd.gz, this is extracted when the phone boots, so any changes you make to default.prop WILL be overwritten when the phone boots.
You have to make the changes inside the initrd.gz file.
Click to expand...
Click to collapse
Any chance you could post the modified kernel? I am running R14 on GB3.2a so it would drop right in

CR5N said:
Any chance you could post the modified kernel? I am running R14 on GB3.2a so it would drop right in
Click to expand...
Click to collapse
yertiz.
Take a backup of your current initrd.gz first though to be on the safe side.

bobjbain said:
yertiz.
Take a backup of your current initrd.gz first though to be on the safe side.
Click to expand...
Click to collapse
Thankyou. This works on Tytung GB3.2a. F1 channel now working on this old HD2

What about SD builds?
magnus48 said:
forget this way. It did not work when rebooting the kernel overwrites the deafult.prop file.
The change should be done inside initrd.gz
Click to expand...
Click to collapse
I can access and edit default.prop on my SD build after the phone has booted. This seems to give me access to Sky News at least. But I still can't get premium channels. Do you think I still need to edit initrd.gz as well or is that now redundant?

johnkst said:
I can access and edit default.prop on my SD build after the phone has booted. This seems to give me access to Sky News at least. But I still can't get premium channels. Do you think I still need to edit initrd.gz as well or is that now redundant?
Click to expand...
Click to collapse
No, you will need to edit your initrd.gz
Before I did I could access Sky News only, afterwards the Sky world was my Oyster!!

bobjbain said:
No, you will need to edit your initrd.gz
Before I did I could access Sky News only, afterwards the Sky world was my Oyster!!
Click to expand...
Click to collapse
Thanks Bob. Is there anything else I should edit while I'm at it?
Currently after booting, my default.prop contains the following attributes:
ro.secure=0 (need to change this to 1)
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
I'm particularly suspicious of the last one!
Also... what should I use to edit default.prop within initrd.gz? I tried unzipping it with 7zip, editing the initrd file with a hex editor and re-zipping but it created a significantly smaller file...

johnkst said:
Thanks Bob. Is there anything else I should edit while I'm at it?
Currently after booting, my default.prop contains the following attributes:
ro.secure=0 (need to change this to 1)
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
I'm particularly suspicious of the last one!
Also... what should I use to edit default.prop within initrd.gz? I tried unzipping it with 7zip, editing the initrd file with a hex editor and re-zipping but it created a significantly smaller file...
Click to expand...
Click to collapse
I only ever changed ro.secure, don't have the phone any more so can't check the other values.
To edit the default.prop you need to uncompress the initrd.gz then recompress it using the following linux commands
Code:
extract
mkdir initdir
cd initdir
zcat ../initrd.gz | cpio -i -d
compress
cd initdir
find . | cpio -o -H newc | gzip -9 > ../initrd.gz
As I run windows I downloaded and installed cygwin and used that to uncompress and recompress the kernel.
I edited the default.prop in windows but you can use vi within cygwin if you want.
If you're uncomfortable doing this then attach your kernel to a post and I can do it for you.

[GUIDE][HOW-TO]Disable Hardware Keys Lights and Function

This Guide Will Disable Hardware Keys (Home, Menu, Back, Search) Light and make it disabled completely so we can use the on screen button like nexus phone in AOSP based ROM (AOKP/PACMAN/Codefirex)
NOTE: Don't Try This in CM Based Rom because CM don't have any on-screen button mod
For Disable The Hardware Keys Light :
Add The Following code to /system/etc/init.d/90userinit
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
and reboot
For Disable The Hardware Keys Function Completely
Navigate to /system/usr/keylayout/synaptics-rmi-touchscreen.kl (maybe it's touchscreen dependent mine is synaptic,i can't try for other)
For atmel is atmel-touchscreen.kl, for elan is elan-touchscreen.kl
Open it as text editor and delete all content of it and save and reboot
To Restore the Hardware Keys Light and Function
Just Copy and Paste the Backup File to the destination (/system/etc/init.d, /system/usr/keylayout)
NOTE: Don't Forget to Backup The ROM,default 90userinit, default touchscreen layout .kl before trying...

Hi hdorius,
maybe it's just typos, but, it will not work the way you describe it.
You have to remove ">" from the chmod command line and change 755 to 644.
BTW: for CM based ROMs, there is a tweak, too (using the file "brightness" etc.),
but it's more easy to just use the app "Keyboard Backlight Controller" from the market.
Cheers, Magpie

hdorius said:
This Guide Will Disable Hardware Keys (Home, Menu, Back, Search) Light and make it disabled completely so we can use the on screen button like nexus phone in AOSP based ROM (AOKP/PACMAN/Codefirex)
NOTE: Don't Try This in CM Based Rom because CM don't have any on-screen button mod
For Disable The Hardware Keys Light :
Add The Following code to /system/etc/init.d/90userinit
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
and reboot
For Disable The Hardware Keys Function Completely
Navigate to /system/usr/keylayout/synaptics-rmi-touchscreen.kl (maybe it's touchscreen dependent mine is synaptic,i can't try for other)
For atmel is atmel-touchscreen.kl, for elan is elan-touchscreen.kl
Open it as text editor and delete all content of it and save and reboot
To Restore the Hardware Keys Light and Function
Just Copy and Paste the Backup File to the destination (/system/etc/init.d, /system/usr/keylayout)
NOTE: Don't Forget to Backup The ROM,default 90userinit, default touchscreen layout .kl before trying...
Click to expand...
Click to collapse
In Viper DHD you have this on Viper tweaks cheers
Sent from my HTC Desire HD using xda premium

aljazirrr said:
In Viper DHD you have this on Viper tweaks cheers
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
Yuhuuu...is viperdhd an AOSP ROM?
Sent from my HTC Desire HD using Tapatalk 2

Magpie42 said:
Hi hdorius,
maybe it's just typos, but, it will not work the way you describe it.
You have to remove ">" from the chmod command line and change 755 to 644.
BTW: for CM based ROMs, there is a tweak, too (using the file "brightness" etc.),
but it's more easy to just use the app "Keyboard Backlight Controller" from the market.
Cheers, Magpie
Click to expand...
Click to collapse
I've tested myself and worked before I posted it and yes the cm have that tweaks,but I doesn't work for me when I set,btw thx
Sent from my HTC Desire HD using Tapatalk 2

hdorius said:
I've tested myself and worked before I posted it
Click to expand...
Click to collapse
So you have no clue at all what theses commands do?!
Sorry, but if you don't know what things do, you should not recommend them.
Your `chmod 755 > /sys/class/leds/button-backlight/max_brightness` will not change the mode of the file as needed,
but overwrite the 0, you previously wrote into "max_brightness", making the first command completely superfluous.
It ends up in a completely empty "max_brightness" file - if we think positive, assuming best case.
In worst case, STDERR has previously been redirected to STDOUT and your command will even result in a "max_brightness" file containing this:
Code:
chmod 755
Usage: chmod [OPTION] <MODE> <FILE>
-R, --recursive change files and directories recursively
--help display this help and exit
The effect of this - or empty - content is in fact unpredictable and only depends on the robustness of the routine, which evaluates the content of "max_brightness".
In your case, you may have been on the lucky side, cause the routine in your ROM seems to return a 0 in case of failure,
setting the value for brightness to 0 - so your "testing success" is nothing less than just sheer coincidence.
A less robust implementation may just crash, leaving your phone unbootable, in a boot loop or s/th even worse.
Cheers, Magpie

increase the hardware button britness on JB 4.2.1
Magpie42 said:
So you have no clue at all what theses commands do?!
Sorry, but if you don't know what things do, you should not recommend them.
Your `chmod 755 > /sys/class/leds/button-backlight/max_brightness` will not change the mode of the file as needed,
but overwrite the 0, you previously wrote into "max_brightness", making the first command completely superfluous.
It ends up in a completely empty "max_brightness" file - if we think positive, assuming best case.
In worst case, STDERR has previously been redirected to STDOUT and your command will even result in a "max_brightness" file containing this:
Code:
chmod 755
Usage: chmod [OPTION] <MODE> <FILE>
-R, --recursive change files and directories recursively
--help display this help and exit
The effect of this - or empty - content is in fact unpredictable and only depends on the robustness of the routine, which evaluates the content of "max_brightness".
In your case, you may have been on the lucky side, cause the routine in your ROM seems to return a 0 in case of failure,
setting the value for brightness to 0 - so your "testing success" is nothing less than just sheer coincidence.
A less robust implementation may just crash, leaving your phone unbootable, in a boot loop or s/th even worse.
Cheers, Magpie
Click to expand...
Click to collapse
Hi Guys,
can someone please help me and suggest me a way to increase the britness of the hardware button on my ZOPO 980 who is running JB 4.2.1
I have tried to edit the build.prop but did not find any line to modify , and I would guess this is not the right way.
thanks

Good
Sent from my KM-S220 using xda app-developers app

Thanks a lot

Works great on my d2vzw. I used option one and made the 644 changes that magpie suggested in second post
Sent from my SCH-I535 using Tapatalk

Thanks!
Great guide worked perfect on my htc amaze 4g

Thanks!

Viper DHD 3.0.1
in viperdhd this options is available in venom tweaks, version 3.0.1 is the latest and most stable version with complete sense 4.1 UI. I suggest you to try it once.

Nice guide, can I try this on nameless ROM, 5.0.2

total mess . anything related to disabling keylight and disable keys won't work for me . i am having note n7000 . first i enabled navigation bar and tried everything what was mentioned above , even i did tried replacing 755 with 644 and removing > but didnt work anything

ankitrajj said:
total mess . anything related to disabling keylight and disable keys won't work for me . i am having note n7000 . first i enabled navigation bar and tried everything what was mentioned above , even i did tried replacing 755 with 644 and removing > but didnt work anything
Click to expand...
Click to collapse
Maybe it don't compatible with samsung phone, i just tested it on my desire hd,sorry..

I am using micromax nitro A311 and its navigation key light is turned off, can anyone tell me how to enable the light of navigation keys?

hdorius said:
This Guide Will Disable Hardware Keys (Home, Menu, Back, Search) Light and make it disabled completely so we can use the on screen button like nexus phone in AOSP based ROM (AOKP/PACMAN/Codefirex)
NOTE: Don't Try This in CM Based Rom because CM don't have any on-screen button mod
For Disable The Hardware Keys Light :
Add The Following code to /system/etc/init.d/90userinit
Code:
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
and reboot
For Disable The Hardware Keys Function Completely
Navigate to /system/usr/keylayout/synaptics-rmi-touchscreen.kl (maybe it's touchscreen dependent mine is synaptic,i can't try for other)
For atmel is atmel-touchscreen.kl, for elan is elan-touchscreen.kl
Open it as text editor and delete all content of it and save and reboot
To Restore the Hardware Keys Light and Function
Just Copy and Paste the Backup File to the destination (/system/etc/init.d, /system/usr/keylayout)
NOTE: Don't Forget to Backup The ROM,default 90userinit, default touchscreen layout .kl before trying...
Click to expand...
Click to collapse
Brother can you help me up enabling button light in samsung exynos 7580 as button light feature is disabled in the RR sources.
Please it would be a great help to me struggling from months for the fix .

CYANOBIZ CM9 Support Thread!

Welcome to Gen8 CYANOBIZ Support thread!​
ATTENTION: This build is stil in early Beta stage! Bizcuite is not responsible of bricked tabs, world war or some kind of alien invasion!
What is this thread for?
This thread is made to help people run CYANOBIZ Unofficial CM9 on their tabs, report bugs related to this ROM and share tips and tweaks.
Before adding your problem(s):
Make sure you are running the latest release of CYANOBIZ !
Make sure your problems is not already listen in the OP (aka this post) !
Bug/Problem list:
Bluetooth can work only by command in Terminal Emulator. Not fixed yet.
Camera. Preview only (can not take pictures for now). Not fixed yet.
Battery stats (% works but no notification of charge). Not fixed yet.
Each problem reported by user will be posted here after its accepted. Remember to use the latest build before reporting.​
How to install CM9 step by step:
You have to install SDE before you attempt to install CM9. Follow the guide in this thread: http://forum.xda-developers.com/showthread.php?t=930197
From now on you have to download the files only from this thread: http://forum.xda-developers.com/showthread.php?t=1941377
Step 1: Download and decompress (unzip) CM9 image file. Rename it to "openaos-cm.img".
always remember to download the file made for your device. Each device has different specification like screen size, RAM, etc.
Step 2: Download zImage.zip (its usually named with the date of the build like "zimage041013.zip") and rename it to "zImage". Do NOT decompress it!
Step 3: Download "initramfs.cpio.gz".
Step 4: Download "data.img.tar.gz", decompress it and choose the size that fits to your needs. (This file will be used to install apps. If you usually install low amount of apps you can use 256MB. Recommended size: 512 MB.. After you decompress it, rename it to "data_ICS.img" and copy it to the root of your internal storage.
Step 5: Copy the decompressed CM9 system file (openaos-cm.img) to the root of your internal storage.
Step 6: Create a new text file. Insert this line: ICS||/openaos-cm.img|/init|0Archos|ARCHOS|ARCHOS|/init and save it. Rename the text file to "menu.lst" and copy it to the internal storage. (If it doesnt work open "menu.lst" with Notepad++ and add one additional line below by pressing enter)
Step 7: Installing the kernel and initramfs.cpio.gz:
Reboot your tab into recovery. Select Recovery System => Developer Edition Menu => Flash Kernel and Initramfs. Connect your tab to your PC via USB and copy the files from steps 2 and 3. (Its recommended to copy the files one by one)
You are done! :good:
Currently the kernel is not supported by other ROMs (except stock firmware with stock kernel).
How to add swap file
Use adb or Terminal Emulator and add these lines:
If you are going to copy the lines copy it line by line do not copy-paste the whole guide else it wont work!
swapoff -a
rm /swapfile
rm /system/etc/fstab
dd if=/dev/zero of=/swapfile bs=1024 count=50000
mkswap /swapfile
touch /system/etc/fstab
echo "/swapfile none swap sw 0 0" >> /system/etc/fstab
swapoff /dev/block/ramzswap0
swapon -a /swapfile
This activates a swap file of 50MB in the root of your system image file (CYANOBIZ_xxx.img also knows as openaos-cm.img
Do NOT increase the size over 50MB because the system will become full and it will result in a bootloop!
How to activate swap in internal SD card (storage). This way you can put highter value like 128MB/256MB/512MB/etc.
Use adb or Terminal Emulator and add these lines:
If you are going to copy the lines copy it line by line do not copy-paste the whole guide else it wont work!
swapoff -a
rm /mnt/storage/swapfile
rm /system/etc/fstab
dd if=/dev/zero of=/mnt/storage/swapfile bs=1024 count=128000
mkswap /mnt/storage/swapfile
touch /system/etc/fstab
echo "/mnt/storage/swapfile none swap sw 0 0" >> /system/etc/fstab
swapoff /dev/block/ramzswap0
swapon -a /mnt/storage/swapfile
If you want to see if it's working type "cat /proc/swaps"
You should see this:
cat /proc/swaps
Filename Type Size Used Priority
/mnt/storage/swapfile file 127972 0 -1
You swapfile is done!
Notice: Sometimes a logcat worths more then a hundred words.
If you like the ROM and you'd like to support it feel free to donate to Bizcuite. This way you can tell him a huge "Thank You" and support his job.

CYANOBIZ Unofficial CM9 Tips & Tweaks
These tweaks come with no warranty! There is a change of bootloop if you edit the wrong value.
Open your root File Explorer (most people use RootExplorer) then go to /system and add these lines to your Build.prop file:
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
wifi.interface=tiwlan0
net.dns1=8.8.8.8
net.dns2=8.8.4.4
qemu.hw.mainkeys=1
wifi.supplicant_scan_interval=120
persist.sys.usb.config=mass_storage,adb
ro.telephony.default_network=0
# dalvik props
persist.adb.notify=0
dalvik.vm.heapstartsize=25m
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=160m
#dalvik.vm.dexopt-flags=m=y
#dalvik.vm.heapstartsize=5m
#dalvik.vm.heapgrowthlimit=48m
#dalvik.vm.heapsize=196m
dalvik.vm.dexopt-flags m=y,o=v,u=y
ro.fb.mode=1
ro.sf.compbypass.enable=0
# persist.sys.shutdown.mode=hibernate
ro.config.hw_quickpoweron=true
mot.proximity.delay=25
ro.mot.buttonlight.timeout=0
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
ro.ril.disable.power.collapse=1
debug.sf.hw=1
debug.composition.type=gpu
debug.composition.type=c2d
windowsmgr.max_events_per_sec=240
ro.ui.fullscreen=false
debug.performance.tuning=1
debug.qctwa.preservebuf=1
dev.pm.dyn_samplingrate=1
video.accelerate.hw=1
ro.vold.umsdirtyratio=20
debug.overlayui.enable=1
debug.egl.hw=1
hw3d.force=1
persist.sys.composition.type=c2d
persist.sys.ui.hw=0
#ro.telephony.call_ring.delay=0
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.carrier=wifi-only
#crash tab don't enable it
#debug.enabletr=true

Many thanks for your works Mavasilisk. It's perfect!! Just don't forget the "e" in Bizcuite :angel:
Upload of first BETA release is in progres
Don't forget, if you install my kernel, you will NOT be able to use others OS (except original Firmware with original kernel of course)
Maybe we must add "This release is not official and not supported by cyanogen".
Bizcuite

bizcuite said:
Many thanks for your works Mavasilisk. It's perfect!! Just don't forget the "e" in Bizcuite :angel:
Upload of first BETA release is in progres
Don't forget, if you install my kernel, you will NOT be able to use others OS (except original Firmware with original kernel of course)
Maybe we must add "This release is not official and not supported by cyanogen".
Bizcuite
Click to expand...
Click to collapse
Updated. Sorry, I was so focused so I missed "e" in your nickname. Cant wait to try the first beta!

Mavasilisk said:
Updated. Sorry, I was so focused so I missed "e" in your nickname. Cant wait to try the first beta!
Click to expand...
Click to collapse
First page updated in dev section.
Link updated
Bizcuite
Sent from my GT-N7100 using xda app-developers app

How is sleep with CM9? I used to find with CM7 Bull my tab used to use more power than stock Froyo when sleeping. Also how well does Chrome work with 256mb ram? Thanks.

I prefer Boat Browser. Its very fast and snappy with the new HW. I can compare it to Opera. Chome is just....not my taste.

Browsers
Mavasilisk said:
I prefer Boat Browser. Its very fast and snappy with the new HW. I can compare it to Opera. Chome is just....not my taste.
Click to expand...
Click to collapse
Yes Boat browser works best but is laggy on bigger pages and force closes when I try to start flash content - flash player is still not working. Other browsers force close on bigger pages and chrome is slow. Opera final still dont work, beta is working but freezes on first couple starts. Even stock browser freezes on first couple starts and crashed system once and then started to work pretty normal. Most interesting thing is with Puffin browsers, they worked well under 1.8 and now Puffin free cant even start and Puffin paid freezes or force close when I try to start some web address or edit speed dial. I edited vm heapsize but it didnt help. I am still suspicious on GPU driver. Rom is fast and many apps and games works but we still have some major problems. Keep up with good work Biz and I hope that we will get stable rom soon.

Biz, check for dalvik cache and cache errors. I had some problems with apps when I forgot to wipe caches.

WiFi
Mavasilisk said:
Biz, check for dalvik cache and cache errors. I had some problems with apps when I forgot to wipe caches.
Click to expand...
Click to collapse
I dont have problem with cache but you were right we still have problems with wifi driver, that is our major problem for now. I hope that Biz will find good driver and recompile it soon.

aleksandarvs said:
I dont have problem with cache but you were right we still have problems with wifi driver, that is our major problem for now. I hope that Biz will find good driver and recompile it soon.
Click to expand...
Click to collapse
I try both. Today i have try to compile the driver module from cm9 sources and with archos gen8 stock kernel.
Compilation success but the driver doesn't want to be insert. I have warning during compilation and this failed the insertion.
Can you say me which security you use to connect you to your wifi?
I think that there is an issue with wpa1/2 security.
Because when i am at work i have no pb, it's a free hotspot wifi without any security just a login.
Bizcuite
Sent from my GT-N7100 using xda app-developers app

I am using WPA-PSK-CCMP and I can make it crash pretty often.

Hi Biz,
congrats to your excellent your CM9 Build. It's pretty fast. However I have a A70S like Mavasilisk and also have the same problems. I can make the tablet crash and reboot with Angry Birds Space with WIFI enabled. However if I disable Wifi and reboot so that the systems boots with WIFI off I can play the game. After another reboot with WIFI enabled the game crashes again.
I have a completely fresh system with nes data_ICS and I'm on WPA WLAN encryption.

groovey2k said:
Hi Biz,
congrats to your excellent your CM9 Build. It's pretty fast. However I have a A70S like Mavasilisk and also have the same problems. I can make the tablet crash and reboot with Angry Birds Space with WIFI enabled. However if I disable Wifi and reboot so that the systems boots with WIFI off I can play the game. After another reboot with WIFI enabled the game crashes again.
I have a completely fresh system with nes data_ICS and I'm on WPA WLAN encryption.
Click to expand...
Click to collapse
TO ALL WHO USES BETA 2.0 (only 2.0 a 2.1 will be upload this evening), PLEASE CHANGE THOSE VALUES:
in /init.rc:
Code:
write /proc/cpu/alignment 1
The original value is 4
And in /system/build.prop:
search "vm.heapsize" and set the value to 192m
Crashes/Kernel Panic must be a REAL old story.
Bizcuite

bizcuite said:
TO ALL WHO USES BETA 2.0 (only 2.0 a 2.1 will be upload this evening), PLEASE CHANGE THOSE VALUES:
in /init.rc:
Code:
write /proc/cpu/alignment 1
The original value is 4
And in /system/build.prop:
search "vm.heapsize" and set the value to 192m
Crashes/Kernel Panic must be a REAL old story.
Bizcuite
Click to expand...
Click to collapse
This post was a wrong way
Jut edit init.rc and change the value of this line: write /proc/sys/kernel/panic_on_oops 0
Set the value to 0.
The will be really stable!!!
Bizcuite
Sent from my GT-I9003 using xda app-developers app

So alignment to 1 or 2 ?

Mavasilisk said:
So alignment to 1 or 2 ?
Click to expand...
Click to collapse
4
Bizcuite
Sent from my GT-N7100 using xda app-developers app

First page (OP) updated with How-to add swapfile guide!

Ok, Good tutorial this rom rocks.
FYO, after upgrade my swap to 1G and my cpu to 1200... Chrome style unusable. I Think our poor gen8 is style weak to it...
Regards,
Rabbit

Try with OC to 1100.

[GUIDE] RIL on Vanir/FXP CM12

Hello everyone!
Making another guide, this time on how to fix RIL on CM12 based roms e.g. Vanir and FXP.
The cause of the problem is once again SELinux and the fix is rather simple... let's go!
Before we start there is one crucial requirement! :
Do you have a SIM PIN set? If YES just continue reading. If NO, please set one BEFORE flashing a CM12 ROM.
We need to be able to set SELinux to permissive before the phone attempts to access the SIM card or it will not work! If you have a PIN set, your phone will not "try" to load it till you entered the PIN and that gives SELinux mode changer the time to change the mode! If you have no PIN set the phone will load the SIM card almost immediately and the app is not quick enough to set the mode to permissive before it loads the SIM! Users with no SIM PIN can try "method 2"
Steps:
METHOD1:
1: Install a build of your choice (Vanir/FXP, and no this fix is not for locked bootloader CM12 roms like RR, there is another fix for those roms!).
2: Once your device has booted up, turn off auto brightness to prevent your phone from rebooting while doing these steps. (your phone will soft-reboot once after disabling auto brightness)
3: Download and install SELinux mode changer from here: Google Play (or any other app that is able to set SELinux to permissive on boot.)
4: Open the app grant root access and check the "show notification" Checkbox.
5: Fully reboot your device and WAIT on the lockscreen till the app says that it changed the SELinux mode to permissive!!!
6: Enter your SIM PIN and you should be ready to go!
METHOD2:
1: Create a new script file in /system/su.d.
2: Put this inside of the file:
Code:
#!/system/bin/sh
echo 0 > /sys/fs/selinux/enforce
3: Set correct permissions.
4: Reboot
(this method was not comfirmed by me! And it might not work, can someone try it?)
Remaining bugs:
1: When you call someone or you get called, the sound will be glitchy!
2: Auto-brightness still does not work!
3: More?
The fix was found by : @AndreAkaNick
Method2 found by @jojos10
Enjoy CM12!,
Noahvt

credits to @AndreAkaNick

Gara91 said:
credits to @AndreAkaNick
Click to expand...
Click to collapse
I almost forgot, thank you

@noahvt
The call gets really bad? You can hear the person on the other side?

lvints said:
@noahvt
The call gets really bad? You can hear the person on the other side?
Click to expand...
Click to collapse
Let me try that for a sec. I'll report when I get back AKA when my phone boots up to FXP 24/02

what if I run su setenforce 0 in terminal and reboot? Do I still need to set SIM PIN then?

vvaklnprm said:
what if I run su setenforce 0 in terminal and reboot? Do I still need to set SIM PIN then?
Click to expand...
Click to collapse
I tried that and it doesn't work...
After reboot selinux returns to enforcing...

How to make permissive selinux with init.d script?
I'm too lazy to download selinux mode changer

Or you can use this init.d script:
Code:
#!/system/bin/sh
echo 0 > /sys/fs/selinux/enforce
Or if init.d doesn't work in your ROM (like current FXP-CM12), you can install SuperSU and put the script in /system/su.d directory.
This way, there is no need to worry about SIM PINs and whatnot.

jojos10 said:
Or you can use this init.d script:
Code:
#!/system/bin/sh
echo 0 > /sys/fs/selinux/enforce
Or if init.d doesn't work in your ROM (like current FXP-CM12), you can install SuperSU and put the script in /system/su.d directory.
This way, there is no need to worry about SIM PINs and whatnot.
Click to expand...
Click to collapse
could you please make a flashable zip?
also how to get rid of cyanogen recovery? cant install anything

2 not working....but wait...what name this file should have?RIL?RIL fix?

The second fix will not work if Google Now is activated.
I get an error that Google (Now) has a network error while my data and radio works.

dimitrakhs1 said:
2 not working....but wait...what name this file should have?RIL?RIL fix?
Click to expand...
Click to collapse
2 only works if you have flashed chainfire's supersu zip and you can choose any name you like for the .sh file
Sent from my Nexus 7 using XDA Free mobile app

Yeah,but it don't need it in this version,it's pre-rooted already(Resurrection v5.3.6).You suggest flashing this anyway?

dimitrakhs1 said:
Yeah,but it don't need it in this version,it's pre-rooted already(Resurrection v5.3.6).You suggest flashing this anyway?
Click to expand...
Click to collapse
You can flash it if you want. I didn't flash it and now I'm using SELinux Mode Changer.

I have tried the 1st method
It works also on RR 5.3.6 #1 build by Furrydaus

jojos10 said:
Or you can use this init.d script:
Code:
#!/system/bin/sh
echo 0 > /sys/fs/selinux/enforce
Or if init.d doesn't work in your ROM (like current FXP-CM12), you can install SuperSU and put the script in /system/su.d directory.
This way, there is no need to worry about SIM PINs and whatnot.
Click to expand...
Click to collapse
I kept trying with FXP CM12 9th Feb , did all the above but RIL still not working.
edit - copied accidentally with a space behind the sh on the first line, hence wasn;t working. Everything works!

does not able to set 3g .. on latest vanir
hey im using latest vanir ... 5.0.2 022715 .. and tried the first method .. set a sim pin .. and it works but when i turn on data ... and set to 3g .. it reboot(screen fade out slowly ) and now when it reboot and again asked for the pin .. and i entered my pin then again it reboots

-EDIT-
it works, accidentally had a space behind the first line of the script hence it didn't work.
Guys my apologies.
Tested again. Turns out the script is not activating no matter what was done - permission set correctly (RWX RX RX chmod755), SuperSU flashed and set on boot, script inside /system/su.d folder. SELinux status keeps being on enforcing.

where can I find the system / su.d
Sent from my Xperia SP using XDA Free mobile app