Those are the screenshots from an older version of the ROM, when it was based on AOKP. Now it is based on CM10.1.1 and doesn't have the AOKP features you are seeing in the screenshots.
The dolby script can't cause any reboots. It is executed only one time, at boot, before the home screen appears. If the phone booted, then this script won't bother the system anymore, until the next reboot.
While it makes no sense at all, I'm sure that fixed it. I had a backup to test. In that backup I installed google +, ran antutu, random reboot. Backup restore, retest, reboot right after app install. I did this for 5 times and it rebooted at random times and always when I repeated the same "tests", but after deleting dolby, I tested it non stop for 2 hours and 0 reboots.
wow .. 4 days ?
What?? That doesn't happen from deleting the dolby script. You either deleted a vital system file, either mistakenly changed some permissions. It is impossible(believe me, absolutely impossible) to get any error by deleting or editing the dolby script.
Der again is irrelevant results ...if smone is free dn he can answer...others can simply shut der mouth ...as simple as dat....If I were you, I should have used the 'search box'. That is easier than asking questions. Laziness is not doing anything, it is doing things in the simplest way
anyway . Performance settings have to be activated by going in Settings->About phone and pressing Build number 7 times.
Does this activates the statusbar softkeys or the navigation bar that comes at the bottom of the screen?
It activates the navigation bar at the bottom of the screen. There are no statusbar softkeys in CM10.1.
My bad, dude. I tried it again and it purrs like a kitten. Must have done something wrong last time, because everything was crashing and the device was lagging like hell. Works great this time around. Flashing your crossbreeder now, to se how that suits me.
Glad to hear everybody's happy in the endMy bad, dude. I tried it again and it purrs like a kitten. Must have done something wrong last time, because everything was crashing and the device was lagging like hell. Works great this time around. Flashing your crossbreeder now, to se how that suits me.
Anyway, after reading a lot of good comments about CM9.2, I tried it, just for the sake of it. It seemed much smoother, but I still liked something about CM10.1. But only after going back to CM10.1, I noticed how big is the difference in performance between ICS and JB. Now I am using CM9.2 and I recommend it to anyone that is used to having a JB ROM as a daily driver. It is much smoother, believe me.Hi alin.p ¿which CM9.2 rom are you using?Glad to hear everybody's happy in the end
Thats exactly what i always tried to say here at xdaGlad to hear everybody's happy in the end
but the sad part is that all the developers here are working on their rom based on cm10,except a few really hoping that you drop your future project based on cm10 and start developing on cm9.. i think the few minor bugs that made you to drop cm9 and work on cm10 can be ingnored 
He even said he dropped cm9.2 because of the bugs still present in it and is waiting for cm10.2 rom to start working..
