yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] namtombout:
So would setting input boost equal to min frequency basically disable touch boost or would it help to keep CPU from ramping up to higher frequencies?

Nvm I set boost duration to 2 secs and it was ramping to high speed
[Samsung Galaxy Nexus] osm0sis:
Well logically setting input_boost_freq to your min would force the frequency down to that every time you touch the screen, probably making it lag like a montherf*cker. :p

Disabling touch boost (why would you want to kill the butter?) could probably be accomplished by setting boostpulse_duration to 0.
[Samsung Galaxy Nexus] Nephilim:
Alright, so those using my settings try this:

go_hispeed_load 86

target_loads 78

This should be fine per osm0sis' post, it doesn't affect performance negatively for me nor benchmarks so the most it'll do is possibly help with battery by not sitting in an endless cycle. I'll update my thread when I get to my PC.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] namtombout:
Battery over buttery my neighbor to the north. I like to think that if most work is done at lower freq then it will save battery even though I think Metalspring kinda said the opposite was true

My original thoughts/hope for touch boost was that it holds CPU at input boost frequency for boost duration and if load is still high after duration then go to hispeed freq or max freq.

I'll run some test to see if current freq > input boost freq will the CPU scale back down to input boost freq. I've been running input and min same freq for awhile and no noticeable lags and I don't think it was scaling down to input boost at higher frequencies.

Give thoughts and input please
[Samsung Galaxy Nexus] osm0sis:
You might be right there. Franco might have some load-based logic in there which might prevent that.

Your original hope is correct. That's what input_boost does. On f.K at the most extreme we had it at ~500 MHz, with hispeed at ~700 MHz for the "inverted" usage (since default has input higher). [MENTION=4110932]yellowdie[/MENTION] came up with the idea to force it to do exactly what you propose, but you still wouldn't want to set it to your absolute CPU minimum; it would defeat the purpose of touchboost altogether and you might as well just disable it with boostpulse_duration 0 if you're going to cripple the function that much.

[MENTION=4328678]metalspring[/MENTION] (and myself) were referring to screen off with what is known as "race-to-idle"; to recap, that's the idea you don't want to limit your frequencies too much or whatever your device is waking up from deep sleep to do will take longer and keep it awake longer. Again ~500 MHz is optimum for this, just enough to let it complete things quickly, without being "brain damaged" and get back to deep sleeping.

~500 MHz has always been an especially good "sweet spot" because somewhere between ~500 and ~700 the GPU also necessarily gets bumped up to it's next step - generally its max. Meaning if you keep screen off max and input_boost_freq at ~500 MHz you also save the GPU from auto-ramping along with it (unless after input_boost_freq it needs to go above that).

You better believe we've been down all these paths to come up with the defaults fellas. ;) They're nice and balanced.

Edit: So from all of the above, for battery saving you should try s_off_max 525 / i_b_f 525 / hs_f 700. (bp_d 250000 or 500000)
[Samsung Galaxy Nexus] thuongphuong:
Please support touch control :(
[Samsung Galaxy Nexus] bsmitty83:
Please ask the Dev of touch control to support my kernel :(
[Samsung Galaxy Nexus] osm0sis:
Here is all our work on coming up with different presets for people:

https://docs.google.com/spreadsheet/ccc?key=0AoUO8XSpvKCfdFVGMm5IRTgtLVptQ1FnNk5HR3djeFE#gid=2

"Auto-Tune Interactive" never made it to tuna (though it was totally awesome and what he uses on N4 and N5) outside of a test kernel Francisco gave us once, so ignore that stuff. Mostly "New AOSP Interactive" is relevant since that's what we use, and then the hs_f and i_b_f stuff from the "GN Original Interactive" stuff is what I was talking about for "inverted values" and is still useful, but the addition of target_loads makes the rest of that section useless.

BTW if you ever load up Google's Factory Image stock kernel again (unlikely since it's JB4.3 ramdisk ;)) those "Magic Tunables" we originally came up with for it still make it fly. :cool::p

Edit: Hmm, I think I'll update stock kernel with a KK ramdisk, native su daemon support and init.d, that'll be interesting/pointless.
[Samsung Galaxy Nexus] namtombout:
Awesome, its more like a fine tuned conservative governor than interactive now.

Btw has anyone heard from metalspring or ledz lately?

Edit

Ask and I shall receive lol, haven't seen you post in awhile metalspring
[Samsung Galaxy Nexus] metalspring:
Does this actually work? And what logging does it disable?
[Samsung Galaxy Nexus] bsmitty83:
It was a commit I added a few days ago , it seems to work
[Samsung Galaxy Nexus] osm0sis:
I think it disables dmesg/kmsg and logcat.
[Samsung Galaxy Nexus] midnightdevil66:
I got a sod on 3/5 smittyV stock settings. Sorry no logs, I know I should have provided something.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] hasnol143:
I got this on 3/5 smitty with Nephilim's settings. not sure what happened
[Samsung Galaxy Nexus] Nephilim:
Not my settings, I just got the same thing. Force close google search in settings/apps, it's what gave me the wakelock. After force closing it my device went to sleep again.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Yeah, I had Email/Exchange be stupid the other day and try to sync Calendar forever resulting in 100% awake for the 6 hours uptime my device had at the time. Unchecked Calendar and checked it again in the Settings Account sync for Email and it immediately synced normally and my device went back to sleeping normally. Weird stuff but random derps happen.
[Samsung Galaxy Nexus] lazydognet:
I've been using LiguidSmooth 3/5 with Smitty 3/5 for about a day now.... Good performance and surprisingly good battery life. I've seen a little lag here and there, but overall, it's been a good combo for me.

LDN
[Samsung Galaxy Nexus] Nephilim:
I think what a lot of people don't understand is that powermanagerservice is not an actual app but rather a representation of all micro wakes consolidated. I had to dig a little deeper to find that it was google search causing my wakelock for 2 1/2hrs.

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
I put a new SmittyV out just a few minor changes

full changelog

here

Mar 07, 2014

ARM: remove unnecessary mach/hardware.h includes …

2b18334837 Browse code

Rob Herring authored 3 years ago bsmitty83 committed an hour ago

Brian Smith

arch: arm: omap4: bump 307MHz GPU to 384MHz without increasing the vo… …

b25bcb24e5 Browse code

bsmitty83 authored 3 hours ago

Brian Smith

build cleanup

1b560cd3cc Browse code

bsmitty83 authored 4 hours ago

Mar 06, 2014

Brian Smith

sync struct wl12xx_platform_data to hardware/ti/wlan …

7cdff9499b Browse code

bsmitty83 authored a day ago

Brian Smith

omap4-common: only disable interrupt when port is suspending …

08d1c15b6d Browse code

bsmitty83 authored a day ago

Steven Rostedt

SELinux: Fix possible NULL pointer dereference in selinux_inode_permi… …

9af365b603 Browse code

rostedt authored 2 months ago bsmitty83 committed a day ago

vmscan: add customisable shrinker batch size …

0790e6aa2e Browse code

Dave Chinner authored 3 years ago bsmitty83 committed a day ago

Brian Smith

drivers/staging: Configurable android log buffer sizes …

d7cc313d1e Browse code

bsmitty83 authored a day ago

Brian Smith

kernel: Prevent unnecessary rfkill event generation. …
[Samsung Galaxy Nexus] osm0sis:
You're probably right. I always start on Other in BBS, look at the total time, time awake and drain, look at Kernel wakelocks (barely anything relevant there, ever, people. EVER), the top will always be PowerManagerService because it represents all the Partial wakelocks. Partial shows most of what you need to know. Another important thing people always miss is that counts can still be important even if a process didn't hold a large amount of wakelock time, so it's worth reading through the whole list, since it's sorted by time held. Then of course AlarmManager represents everything in Alarms so you go look there next. Sometimes Network is worth looking at too to see what's drawing data when it wakes up.

I'm still pretty impressed with NLP lately though. Since Google Play Services went to 4.1 it can still have sort of ridiculous wake counts but my idle drain remains good.

---------- Post added at 10:44 PM ---------- Previous post was at 10:38 PM ----------

Awesome to see this in there. 3 steps for GPU is nice nice nice.
[Samsung Galaxy Nexus] wisefreakz:
Not Found!!
[Samsung Galaxy Nexus] bsmitty83:
sorry bro got lost in [MENTION=4763201]mbq[/MENTION] 's awesome tracks . try it now
[Samsung Galaxy Nexus] wisefreakz:
Fixed!!! #hackthetuna
[Samsung Galaxy Nexus] bsmitty83:
Pm me a full size IMG of your SIG pic . I'll add it to the op
[Samsung Galaxy Nexus] wisefreakz:
Sure.... Ppl wanted me to change it to add the "V" into the eye and let the DirtyV closer to the chin.

What you prefer?
[Samsung Galaxy Nexus] lileoja:
friend thank you for your work, a question and works with cm tonight?
[Samsung Galaxy Nexus] bsmitty83:
Sounds good to me bro your the artist :D
[Samsung Galaxy Nexus] bsmitty83:
It should work on latest cm , but then again they may have changed some $h!t just cause they like to mess with everyones builds lol
[Samsung Galaxy Nexus] wisefreakz:
There u have master... check your PM :fingers-crossed:
[Samsung Galaxy Nexus] osm0sis:
My hackjob version of that second idea is here if you want that for the OP too!:

http://xdaforums.com/galaxy-nexus/development/kernel-dirtyv-t2613655/post50685571#post50685571 :)

I also inverted Nemed's cool logo for if we ever figure out how to get the bootlogo working.

That reminds me .. [MENTION=4243088]BigBrother1984[/MENTION] [MENTION=3685904]ak[/MENTION] / Carlo & Stefano, any ideas how to get bootlogos working again on Tuna for KitKat? You two were the kings of that. :)
[Samsung Galaxy Nexus] ASHURiCAN:
Excuse me to ask the question but I often read "tuna" when you're talking about your kernel, does it mean it's designed only for tuna devices? I since the beginning use it on my maguro device ... :$
[Samsung Galaxy Nexus] wisefreakz:
Hey [MENTION=4544860]osm0sis[/MENTION] i sent him the originals as you mentioned the other day also with the inverted one!!

In regards of the bootlogo... i see there's a Kitchen for kernels... i'm no linux nor cygwin guy so will not risk on that.. maybe you guys can sort that!!

http://xdaforums.com/showthread.php?t=1659584
[Samsung Galaxy Nexus] bsmitty83:
Tuna is simply any of the 3 galaxy nexus versions

Toro, toro+ ,and, maguro
[Samsung Galaxy Nexus] wisefreakz:
Tuna is the code for all Galaxy Nexus

Maguro is GSM version while Toro is the LTE version!

Edit: Forgot the Toro+ (@bsmitt83 is faster than me..lol)
[Samsung Galaxy Nexus] bsmitty83:
I think you derped cause I got no message yet , unless its just being slow ......
[Samsung Galaxy Nexus] hasnol143:
Yup this solved the problem,thanks. and by the way your settings are working awesomely! I avoided undervolting this time to see how the phone would react, so far no freezes! Next up will be undervolting.
[Samsung Galaxy Nexus] ASHURiCAN:
Thx for the clarification! ^^
[Samsung Galaxy Nexus] wisefreakz:
Check now!!
[Samsung Galaxy Nexus] cujo6801:
It's probably your kernel f****** it up..... :D

Sent from the "DOG" pound
[Samsung Galaxy Nexus] wisefreakz:
hahahahaha.. get it here then!!!

http://www24.zippyshare.com/v/36366686/file.html
[Samsung Galaxy Nexus] bsmitty83:
Naw , my source is available so u know there's nothing phishy in there lol , unlike some kernels , whos dev now has thousands of peoples personal info lol j/p
[Samsung Galaxy Nexus] bsmitty83:
It went through , thanks man ( thank god it did cause tour like has entirely too much animé ads on it , thought I was gonna have a seizure lol ) , its Fri night so i m not really sober .....
[Samsung Galaxy Nexus] wisefreakz:
About f***** up kernel... Check this dmesg... Latest 3-07 with Vanir...
[Samsung Galaxy Nexus] bsmitty83:
Not sure why people are getting all the sync errors , I get zero
[Samsung Galaxy Nexus] osm0sis:
Lets you convert to RLE bootsplash format and back but doesn't actually add the support. :(

I've got my own RLE tool I updated from DooMLorD's original one. ;)
[Samsung Galaxy Nexus] wisefreakz:
What rom? I might try it!!

OT: As you like [MENTION=4763201]mbq[/MENTION] track.. check this out... https://soundcloud.com/skylouder i used to produce e-music before i marry... lol... so i have some of them published!!

---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------

Damn... take this as a "thanks" as i'm out of thanks today :(

I remember [MENTION=3685904]ak[/MENTION] wrote a guide in the past at another forum (DT's one)... i will try to find it!!
[Samsung Galaxy Nexus] bsmitty83:
Sweet . I'm using omni 2/9 lol , its just my test phone and I loaded up whatever I had on computer after wiping the sdcard
[Samsung Galaxy Nexus] osm0sis:
Thanks for the tip!!!

Ka-CHING:

http://droid-hive.com/index.php?/to...dd-a-boot-logo-like-sgs1-to-your-gnex-kernel/

Pray with me now.. ;)
[Samsung Galaxy Nexus] wisefreakz:
Way to go [MENTION=4544860]osm0sis[/MENTION] ... finger crossed here :)
[Samsung Galaxy Nexus] bsmitty83:
Already tried it that way a few times , ak has the same write up here in the nexus dev section btw , but I could never get my image to show , but I'll try again someday
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION] there's some defconfig stuff you need to add and then I think it'll work. Looks like the only thing that was missing. :good:

---------- Post added at 12:11 AM ---------- Previous post was at 12:10 AM ----------

Ah crappy.. You had the cmdline in there and all those defconfig settings? I don't recall ever seeing your kernel spit out a cmdline when I split the boot.img. AK's always did. :confused:
[Samsung Galaxy Nexus] bsmitty83:
I only added the image to my remote git , I did change all the defconfig stuff , pulled an init binary from a sgs3 as per aks directions in his xda thread , it would get me a super small image if the word "android......." , that's it
[Samsung Galaxy Nexus] osm0sis:
Damn. Thought we cracked it. :(

I tried like 4 SGS3 init binaries for KitKat and they were all bad news for our device.

That's the console that's supposed to precede the bootsplash though, so you were kind of close. :good:

[MENTION=3685904]ak[/MENTION]
[Samsung Galaxy Nexus] wisefreakz:
Here is the PNG ready if you sort this thing out... http://www27.zippyshare.com/v/71318674/file.html

---------- Post added at 01:36 AM ---------- Previous post was at 01:22 AM ----------

[MENTION=4544860]osm0sis[/MENTION] Maybe this can help:

http://www.gentoo-wiki.info/HOWTO_Linux_Logo_Hack

http://xdaforums.com/showthread.php?t=1795388

https://android.googlesource.com/kernel/msm/+/android-msm-hammerhead-3.4-kk-r1/drivers/video/logo/

[MENTION=4608636]bsmitty83[/MENTION] thanks for the mention broski!!!!!
[Samsung Galaxy Nexus] Nephilim:
SOD on 3/7, back to 3/5 for me. :(

Sent from my Android 4.4.2 Galaxy Nexus
[Samsung Galaxy Nexus] ak:
You have to create an image with resolution of your phone

Akiller revolution!
[Samsung Galaxy Nexus] milojoseph:
Whoah can you share your sig without the ak and hack the mako plz
[Samsung Galaxy Nexus] wisefreakz:
[MENTION=4608636]bsmitty83[/MENTION] can you with the correct image size?

I've prepared one few posts above....
[Samsung Galaxy Nexus] osm0sis:
You could do that yourself in Windows Paint. Don't be lazy. :p

Guess you're a fan of wisefreakz' work, eh? :)
[Samsung Galaxy Nexus] milojoseph:
Sound like my mom dont be lazy milo.... lml and yes I am. 2mm I will try myself.
[Samsung Galaxy Nexus] ak:
[MENTION=262900]wise[/MENTION]freakz is the artist ... When I have access to my box yes ... I'm in station now milano central :cool:

Akiller revolution!
[Samsung Galaxy Nexus] aosp:
[MENTION=4608636]bsmitty83[/MENTION] Will the bootlogo support TouchControl? ?
[Samsung Galaxy Nexus] ak:
Mmm I think app control made support to dirty?

Akiller revolution!
[Samsung Galaxy Nexus] ak:
@wisefreakz

new log and thanks to you are online:

http://ak.hiddenbytes.org/

new logos are online for download:

http://xdaforums.com/nexus-4/orig-development/kernel-ak-t2473454
[Samsung Galaxy Nexus] büscher:
I have alot of error messages in dmesg on 3/7, also big wake lags and music glitches...

Some errors:

Alot of sync lost

[MIPI-HSI] wrong open cmd in rx step

Omapdss dsi: rx fifo not empty after write

Omapdss dsi: rawval 0x17000202

Omapdss dsi: Ack with error (0x2)

Omapdss dsi: Sot sync error

Dsi_vc_dcs_write(ch 1, cmd 0xf7, len 2) failed

Platform_pm_suspend+0x0/0x5c returns -16

Failed to suspend

Some devices failed to suspend

The last one also very frequently

?...

Also recorded this nice blurry google logo:
[Samsung Galaxy Nexus] osm0sis:
Wow so the final JB4.3 Google Stock kernel for the GN actually included target_loads. :highfive:

And it was set with an array by default. "70 920000:80 1200000:99" and with the other interactive "winning tunables" and the fstab mount tweaks only, I'm surprised to say Stock is pretty damn quick in KitKat.

Definitely good as food for thought. I'll post it up tomorrow since I've just been hitting my head against a wall trying to get a Linux cross compiler built under Cygwin for the last 4 hours. :eek: ;)
[Samsung Galaxy Nexus] novincobra:
+1 in PA 4.1 build 3/5
[Samsung Galaxy Nexus] ak:
Cross compile and cygwin will be fantastic ... I'm waiting ... You are a superman ... You work always for improve android.

Akiller revolution!
[Samsung Galaxy Nexus] aaron13:
I saw in your latest script that the boostpulse_duration was 750000. Shouldn't it be 75000?
[Samsung Galaxy Nexus] osm0sis:
So you read that post but didn't read my post almost directly after where I answered the question you just asked? :confused:

The NDK's standalone is next. :D Cygwin is so painful though... :(

Bed time. :p
[Samsung Galaxy Nexus] Atento:
I'm afraid to move on from 3/5 to 3/7. Battery life is simply amazing here. It's almost unbelievable.

The only drawback is the delay to show the lockscreen after press power button. It takes 2 or 3 seconds to show something.
[Samsung Galaxy Nexus] aaron13:
Sorry I didn't see that, it was almost 3 o'clock midnight, and I was tired of the whole week working :rolleyes:
[Samsung Galaxy Nexus] pvkiniyan95:
7/3 pretty good initial impressions...
[Samsung Galaxy Nexus] xAAnto7:
Best settings for any 4.4 rom based?
[Samsung Galaxy Nexus] qu4nd:
As usual, it is a good choice to use Nephilims settings ;) link see kernel faq in post #2...
[Samsung Galaxy Nexus] midnightdevil66:
[MENTION=4608636]bsmitty83[/MENTION] whatever magic you did on 3/7 is extraordinary. Never experienced this kind of idle battery drain on my toro since i got it over two years ago not to mention the smoothness and speed. All sync, WiFi, LTE and other crap on. I thank you sir for your great work and dedication to us.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] aosp:
What is best?
[Samsung Galaxy Nexus] paarthdesai:
you ;)
[Samsung Galaxy Nexus] lazydognet:
Can I ask a dumb question here.... I see in your suggested Governor Control Settings, you have:

go_hispeed_load: 78

target_loads: 85

But above you state that go_hispeed_load should always be higher. Did I miss another post somewhere that explains this?

Just wondering and trying to learn.

LDN
[Samsung Galaxy Nexus] büscher:
That are the wrong, old settings I couldn't change in the scripts until now. Will do this in the evening.

Also maybe Nephilim did not update his thread yet.

Edit: or where did you find these settings?
[Samsung Galaxy Nexus] wisefreakz:
Fantastico [MENTION=3685904]ak[/MENTION] !!!!!!!!
[Samsung Galaxy Nexus] dbh369:
No, he's changed his settings now, neph too I believe.

Btw, just crashed on 3/4, this I have a last kmsg from the right kernel this time:D

GP Music, viper, sound hound running simultaneously thru Bluetooth, too much? [MENTION=257693]butcher[/MENTION]'s settings except Illinois, 2 core power save, gpu at 512.

---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------

Oops, https://app.box.com/s/zoalo3uwgwq688x56f2e
[Samsung Galaxy Nexus] TheDareDevil:
Are we able to view Logs on the Smitty version in IDE's such as Eclipse?

Couldn't view them on normal DirtyV version but can on Franco
[Samsung Galaxy Nexus] lazydognet:
My fault... I meant to say they were from Nephilim's suggested DirtyV settings and not from osm0sis directly.

LDN
[Samsung Galaxy Nexus] bsmitty83:
Use 3/5+ , I reverted a change that was causing that oops

I'll get some new builds out today hopefully
[Samsung Galaxy Nexus] pvkiniyan95:
On 7/3 with few changes to the script...

gpu oc 1

Dynamic fsync 0

Multicore powersaving 0

Min screen on 350Mhz

Added settings, phone, keyboard, systemui to lmk script [MENTION=3317173]büscher[/MENTION] posted

Feeling smooth and much better....

Quite confused with target loads but left as it was

Try those changes if u want...
[Samsung Galaxy Nexus] büscher:
I will also change gpu oc to 1 in my script because of the new voltages.:thumbup:
[Samsung Galaxy Nexus] LeBaldi:
I cant flash the 3/5 and 3/7 builds... it Fail... I updated to lastast TWRP ( 2.6.3.2 ) and no lucky :(
[Samsung Galaxy Nexus] lazydognet:
No issues here using 2.6.3.1

LDN
[Samsung Galaxy Nexus] GilGameshn1:
Better and better ... 3.7 ... Evolving really ... With both buch and neph settings ... Both smooth both battery friendly ... Power management really improved thanks [MENTION=4608636]bsmitty83[/MENTION]

Sent From My GNex
[Samsung Galaxy Nexus] wisefreakz:
Try to redownload zip file... What errors does it throws?
[Samsung Galaxy Nexus] aosp:
Somebody please post a dmesg booting SmittyV-NoMeM-3.7.14 I'm on to something ?
[Samsung Galaxy Nexus] LeBaldi:
When I flash it become to unzip and return only "Failed!" and dont flash... on both builds :confused:

EDIT.: Tried to open the zip in windows and the file was corrupted... so downloaded again... and again corrupted... and 1 more time... and this time was ok... now it flashed :D
[Samsung Galaxy Nexus] Shambola:
Strange issue with 3/7: notification led and active display don't work. Does anybody have the same issue?
[Samsung Galaxy Nexus] neopbm:
Hi,

Sorry for the noob question, but is it ok to use int.d scriprts to apply somes settings, and then Trickster Mod to change color screen ? And only color, nothing else.

Thanks
[Samsung Galaxy Nexus] bsmitty83:
Mine both work
[Samsung Galaxy Nexus] dbh369:
Referring to trickster question

Make sure you give long enough grace period for init d to run. Also trickster applies all settings at boot so if you change init d, make sure and disable trickster and reset the kernel settings again.
[Samsung Galaxy Nexus] GilGameshn1:
Mine both work too .

Sent From My GNex
[Samsung Galaxy Nexus] cujo6801:
Mine works better....

Sent from the "DOG" pound
[Samsung Galaxy Nexus] heXacode:
Your init.d scripts will override Trickster Mod settings. If you go changing stuff in Trickster and reboot you will have bootloops at Google splash screen. It will take 2 battery pulls to get it back to normal.

You will then see Trickster giving a different setting (what you changed on it) versus your script.

The only thing I find that is OK is changing the colors via Trickster Mod. That shouldn't cause a bootloop even if there is a coded color setting in the script.

To be on the safe side I would copy the original script, keep it as a .txt format, save it on the sdcard or rename it to yourscriptname.bak in /system/etc/init.d/. Then duplicate the original script, take out the color codes, save, reboot, then use Trickster for the color settings.
[Samsung Galaxy Nexus] Atento:
Is there anything I can do to wake up my phone faster than it is using the power button? It takes 3 seconds to show something on the screen after I press the button.

Thank you.