yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Robin M:
Bigeyes,

Thanks for your prompt reply. Your reply lead me to believe that my 99trikster scirpt in init.d may not be running, or is not correct. Here is what lead me to that suspicion...

A sub-directory called "trickster" was indeed an obvious choice, and I did look for one after installing the mod with CWM. But it was not there. So, since you said the .conf file was generated by the /system/xbin/tricks script, I ran that. And in fact, that did generate the trickster.conf file in the /sdcard directory.

I then made some changes in the CPU freq settings to test. Changes did NOT take place after reboot. So, I ran the tricks script again and the changes DID take place. (Well one of them did. I had changed the min freq. to 216000 and the script apparently would not allow a setting below the DEF_MIX_FREQ value of 350000. Interresting.)

Anyhow... Since the original .conf file was not generated, and since the tricks script was not run on reboot, I suspected a problem with init.d. In checking the 99trickster script I found only these two lines...

#!/system/bin/sh

tricks boot &​

The second line looks incomplete, but I confirmed that this was all that was in the CWM zip file for that script. Is this correct?

I am running THIS STOCK IMMK76 ROM, but the OP says that in addition to being zipaligned and deodexed, rooted, etc. it was also init.d enabled. Shouldn't your script work on this stock ROM? Im curious now as to why the init.d script is not working. (I have not tired any other init.d scirpts.)
[Samsung Galaxy Nexus] bigeyes0x0:
@Robin M: It is supposed to be like that "tricks boot &", tricks is to called the command, boot is its argument and & is to run this whole command as a background process.

I suspect it's really something as you said, somehow init.d does not fire at boot. Easy solution is for you to install a kernel that also includes a ramdisk that does support init.d (franco, leankernel, fugumod). I will take a look at that ROM if I have time.

About the frequency settings you set. That is depends on your kernel. Can you tell me the one you're using? if your kernel does not have 216000 slot then my script can't force it.

BTW are you sure you're using the latest 20120602 version? I only add busybox and init.d in this version.
[Samsung Galaxy Nexus] Robin M:
To be honest (and fair), I did not necessarily come to that conclusion. The instructions in the OP are admittedly sketchy but I would agree with bigeyes0x0 that they do seem adequate for anyone who has had experience running scripts in Android. My problem is that the script did not work properly and did not generate the .conf file for me. And that's what left me confused.

---------- Post added at 01:03 PM ---------- Previous post was at 12:42 PM ----------

Yeah, I installed that latest version. Just downloaded it last evening. I had been running the AOKP rom, which does include many performance settings. But when VZW released IMM76K as an OTA update this past week, I wanted to try it so see if it would cure some awful connections problems that are generic to the CDMA Glaxay Nexus. And I want to be running somthing simple while I test that latest build from VZW. I'm using the latest VZW stock kernel (3.0.8-gda6252b dated 4/13/2012), and the latest radios from the IMM76K build. When I've had a chance to see how the comminications work with this stock upgrade, then I'll go back to a more complex rom. I'll probably give the franco kernel a try also, as it seems to get high marks on these forums. But for now I want to keep things very simple. I was, however, looking for a way to lower CPU freqs so as to get better battery performance, which is why I downloded your scripts.

Thanks for your help.
[Samsung Galaxy Nexus] bigeyes0x0:
OK, I got the gist now. So first off stock kernel can't go lower than 350MHz, you can't force it. My script is just a way to expose inherent possible tweaks for kernel and general ROM tweaks (zipalign, screen state optimize, sql optimize).

As for the init.d problem, for now I suspect that it was done incorrectly in the original ROM but it was enough for my script to detect that the ROM already has it so my script didn't add the necessary part to init.rc. Can you get this file /init.rc from your ROM for me (this file is in the ramdisk so it's only exist on your running phone not in the CWM ROM zip)? You can use any file manager app (root explorer, es explorer...) or use adb pull /init.rc to get it.
[Samsung Galaxy Nexus] Robin M:
Yeah, I came to the same conclusion about the init.d not being set up properly on the original (slightly modified) rom. I didn't really understand that stock phone roms are not set up to handle init.d scripts. Here is my init.rc file. Are you able to verify the problem and fix it?
[Samsung Galaxy Nexus] Juiced718:
Why don't I have screen and fast charge mods anymore? I flashed redemption rom and pbj kernel is that why? I don't get why that would be but if you can enlighten me I'd appreciate it

vzw GNex
[Samsung Galaxy Nexus] blckngldhwk:
That's fair, there is certainly a bit of hypocrisy on my part and I'll own that. Thanks for the follow up and your continued contribution to the community.
[Samsung Galaxy Nexus] bigeyes0x0:
Stock ROM does not have init.d support and it looks like that ROM has init.d support added differently. Normally one would include this in init.rc to support init.d

service userinit /system/xbin/busybox run-parts /system/etc/init.d
oneshot
class late_start
user root
group root

but this rom init.rc has init.d support added with

start sysinit
//.....A lot of code inbetween........
service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
disabled
oneshot

Now according to my knowledge this should be ok, too and Trickster MOD CWM script would detect this and do not add another conflicting entry to run init.d. As I only have a GSM GNex, I can't test this ROM to be sure. Do you have a nandroid back up before applying my mod so we can check whether init.d works or not on that ROM? To do so you can create a file with following contents in /etc/init.d

#!/system/bin/sh

echo "init.d works" > /data/media/checkinitd
chmod 666 /data/media/checkinitd

Then you need to set this file permission as 755 or rwxr-xr-x (same thing, just different conventions)

If after boot you see the file checkinitd with "init.d works" as content then that's my derp and I will try to fix it, otherwise it's the ROM dev's derp, and you will have to take it up to him.

Finally if all of this is over your head, just install a kernel with init.d support built in as I said in my previous post.

P.S. This init.rc you got, is it after you installed my MOD or before (you did nandroid restore)?

Yeah that should be why. AFAIK that kernel is nearly stock so you won't find anything fancy in it.
[Samsung Galaxy Nexus] Robin M:
The init.rc I sent was AFTER I installed your MOD, however I did a nandroid immediately BEFORE I installed your MOD, and that original init.rc script has the same lines in it as below...

service sysinit /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d

disabled

oneshot
​

I did exactly as you suggested. After restoring my nandroid I had no /etc/init.d folder, so I had to create that and I gave it the same rwxr-xr-x permission. Then I followed your instructions to the letter. After a reboot, the new init.d script did NOT run. So to test the script I ran it with "script manager" (smanager), and only then did it generate the file "checkinitd" in the appropriate folder.

So.. bottom line is that the init.d convention in this rom is NOT working.

Thanks so much for pin-pointing this problem and trying to help. All was not lost as I have learned several things from you I did not know before. So... Thanks for that too. :)
[Samsung Galaxy Nexus] fullmetal509:
So is this a "Mod" or an actual from? Cause I keep thinking its a small mod to something in every rom?

Via Galaxy Nexus [LTE]
[Samsung Galaxy Nexus] tacosrdelicioso:
What does the title say? Ik they've made it especially hard to read what with the bold letters and all
[Samsung Galaxy Nexus] SoCalSpecialist:
will this work for MIUI? know what..im gonna flash it and find out :good:

UPDATE:

ok so i nand'd obviously, wiped all cache's and batt stats and installed.

gotta say, its alot more snappier and boot time has definitely changed. dont know anything about the fast charge just yet, because im sitting on a full battery, but will definitely report back with my findings on that.
[Samsung Galaxy Nexus] blckngldhwk:
So this is JB friendly?
[Samsung Galaxy Nexus] bigeyes0x0:
If you check the screenshots I did for the app, you can see they were on JellyBean.
[Samsung Galaxy Nexus] blckngldhwk:
Silly me, I mistakingly read the entire OP and didn't find this info. Should have known to check external links to screen shots in the second post.
[Samsung Galaxy Nexus] LNJ:
So when I pick user preset in Screen, I get sliders but none of the settings stick.

The other presets don't allow for tweaking. Brightness does not work either.

Script flashed fine.

Any help?

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] bigeyes0x0:
Silly question but did you press on Apply?
[Samsung Galaxy Nexus] LNJ:
Yup. Even reset, uninstalled and reinstalled!

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] LNJ:
Ok got it bro.

I flashed the reset in cwm, flashed the remove and flashed the mod again and now it works.

Thanks.

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] bigeyes0x0:
It's hard for me to debug TBH, because I've just installed FuguMod myself and it works.

May I ask if you have ever use this MOD before? If so I might have a clue of what went wrong.

(JB made sandbox jail and and file access permission more strict and this is just another remnant).
[Samsung Galaxy Nexus] LNJ:
First time. Maybe cause I'm using Odexed rom?

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] bigeyes0x0:
No not related at all. This mod does not touch any apk. But now you made it works, it's practically impossible for me to debug anyway. As I and my testers all use it fine. If you ever runs into it again, please provide a logcat.
[Samsung Galaxy Nexus] LNJ:
I only get multiplier and gamma sliders for user preset. The other 3 presets only have the brightness sliders!

Is this correct?

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] bigeyes0x0:
Yes, as the other presets have gamma, multiplier, and contrast (on kernel that supports it, FuguMod not) values hard coded. Only user preset it is meant to be customizable. I thought this is obvious.
[Samsung Galaxy Nexus] LNJ:
Lol I was expecting sliders in those as well to tweak it a little just to offset the blueness!

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] bigeyes0x0:
Nice idea. I'll consider that. For now check /sdcard/trickster dir, default values for these presets are in color.conf
[Samsung Galaxy Nexus] LNJ:
Thanks. Also you might want to rename the Brightness sliders to Contrast.

Sent from my GNex running Jelly Bean 4.1.1
[Samsung Galaxy Nexus] yyz71:
Ok I just installed this and my navbar just vanished :confused: Using bigxie 4.1.1 .
[Samsung Galaxy Nexus] bigeyes0x0:
My MOD is likely have nothing to do with this.

Did you install any battery or navbar mod? If so point me to it. I'll checked if it's borked.
[Samsung Galaxy Nexus] blckngldhwk:
Had the same problem.
[Samsung Galaxy Nexus] bigeyes0x0:
Any of you who had navbar missing please get me the output of this command

ls -l /system/app/SystemUI*

you can use either adb shell or terminal emulator from the market to get this.

Also if you install any SystemUI mod, point me to that so I can check whether that itself is the **** that cause this issue. Generally this is not my issue, but badly modded SystemUI.apk. A dalvik-cache wipe in that case will also kill your status and navbar.
[Samsung Galaxy Nexus] Zax_Was_Here:
Hey, i just installed the mod and the accompanying control app. I appreciate it, and my phone does feel a bit faster, and i'm checking out the battery life currently. I'm just curioius what the battery life extender option does exactly, just so i can have a basic idea whats happening to my phone.

Thanks again for the mod.
[Samsung Galaxy Nexus] bigeyes0x0:
It's to limit the maximum charge percent your phone will take, to lengthen your phone battery lifetime. Personally I find that useless as one can always buy a new batt, not exactly expensive.
[Samsung Galaxy Nexus] Zax_Was_Here:
Ah, similar to what my laptop has. With a phone like this, where battery life is minimal i'd avoid it as well.

Thanks for the quick response
[Samsung Galaxy Nexus] ceejay83:
do the mods work with stock jb kernel?
[Samsung Galaxy Nexus] bigeyes0x0:
Yes it does. It's universal as I said somewhere before.
[Samsung Galaxy Nexus] ceejay83:
I lost my status bar/nav bar and sound as well, installed this mod - http://xdaforums.com/showthread.php?t=1747632

here's the output from that command:

-rw-r--r-- root root 1002220 2012-07-14 11:43 SystemUI.apk
[Samsung Galaxy Nexus] bigeyes0x0:
I checked it. That **** is borked. He f*cked up SystemUI.apk signature. Then you or something wipe dalvik-cache and when your phone boots, odex of SystemUI.apk can't be recreated. Please go shove it up his ***, not mine :D.
[Samsung Galaxy Nexus] ceejay83:
will i bork trickster mod if i flash that mod after yours?
[Samsung Galaxy Nexus] bigeyes0x0:
Technically Trickster MOD is not borked, only that SystemUI.apk is borked leading to problems.

I haven't checked if after zipaligning, odex file needed to be recreated. If it is then it's borked, if not then you can run Trickster MOD fine after install that mod first. Still sooner or later installing a kernel that has script to wipe out dalvik-cache will bring you the same trouble (franco, GLaDOS, Air and might be others). I advise you to shove it up his *** ASAP, so others won't run into the same problem, tell him to read this http://www.galaxynexusforum.com/for...562-how-decompile-compile-using-apktools.html .

EDIT: I'm gonna disable zipalign by default in the next version so new user won't run into this problem unless they enable zipalign. I need to stress that the root cause is not the zipaligning process itself but the borked mod.
[Samsung Galaxy Nexus] FrostyF7:
This is interesting.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] smoothone:
Just wondering if the Trickster Rom is for the Nexus? If it is then where can we try it out, thanks.
[Samsung Galaxy Nexus] bigeyes0x0:
It is but it's for the GSM Galaxy Nexus as I made it from google IMM76I image, it does not work on toroplus.
[Samsung Galaxy Nexus] FrostyF7:
So if I where to put this mod on an aosp rom it would be like the actual trickster rom?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bigeyes0x0:
Yes, nearly identical. The remaining mod is dalvik-cache in cache partition which free up space for your virtual sdcard. And the other is Zeppelinrox's supercharged services.jar for better multitasking.
[Samsung Galaxy Nexus] FrostyF7:
Thanks for the input.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dangambino:
The values in script are listed ad "binary". Is that what needs to be imputed to activate that particular mod? And the specific integer in those mods? Thnx in advanced r
[Samsung Galaxy Nexus] john9:
wow! nice to see this,thanks for sharing
[Samsung Galaxy Nexus] bigeyes0x0:
Binary as in 0 and 1 to disable and enable respectively. I thought that is obvious.

So if you want to enable feature named X just set X=1
[Samsung Galaxy Nexus] SITH16:
Does anyone know if this will work on paranoid android?
[Samsung Galaxy Nexus] bigeyes0x0:
I heard someone flash it successfully. To be sure just do a nandroid before hand.
[Samsung Galaxy Nexus] spykedvodka:
Question, does it work with rooted stock?

Thanks!
[Samsung Galaxy Nexus] bigeyes0x0:
It's only requirements are root and CWM, the next version might not even need root (in private testing), so you can use it on your ROM, sure.
[Samsung Galaxy Nexus] spykedvodka:
Thanks!
[Samsung Galaxy Nexus] spykedvodka:
Ok I'm retarded or something... i can't figure this out. Anyways, this is my question... I flashed the zip with cwm, does that mean its working now? Or do I have to use the terminal stuff it said in the Usage section and if I do, how exactly do I do that?

Thanks!
[Samsung Galaxy Nexus] Ryjabo:
I actually have the same question.
[Samsung Galaxy Nexus] bigeyes0x0:
If you see directory /sdcard/trickster with file trickster.conf inside after installing through CWM, then it should work. To change settings modify trickster.conf, but you don't really need to if you don't want/need to change settings. The default is good enough in general.
[Samsung Galaxy Nexus] jeffreynothing43:
Flashed it this morning...thank you. I've been running rooted stock ROM/kernel since day one. I have no desire to flash any custom ROMs on this phone as I am completely happy with how it is out of the box...rooted of course. But I have been looking for a zip aligned stock ROM, which this mod seems to have solved. Much appreciated.
[Samsung Galaxy Nexus] Reno Skyy:
I installed this an its in the settings but how do I use it?
[Samsung Galaxy Nexus] bigeyes0x0:
If you can't follow the Usage guide in the first post, wait a week or two. The GUI is coming.
[Samsung Galaxy Nexus] SITH16:
Does this work on paranoid android?
[Samsung Galaxy Nexus] bigeyes0x0:
It works on CM so I think it should. To be cautious, a nandroid is recommended.
[Samsung Galaxy Nexus] ElfinJNoty:
still planning on the GUI?
[Samsung Galaxy Nexus] bigeyes0x0:
You'll see it tomorrow I think.
[Samsung Galaxy Nexus] JuanDaDon86:
Does this work with jellin rc3 and I don't understand the benefits
[Samsung Galaxy Nexus] JuanDaDon86:
I have trinity kernel too sorry for the noon question
[Samsung Galaxy Nexus] bigeyes0x0:
It should work as long as you have a custom recovery.
[Samsung Galaxy Nexus] JuanDaDon86:
What's some things I could use with trinity kernel
[Samsung Galaxy Nexus] bigeyes0x0:
Just install the script and app, you will see what you can do with it then. If you don't like it then, you can always uninstall.
[Samsung Epic 4G Touch] DreamManifested:
I flashed this rom and kept my EL29 kernel. Does that mean in order to get this Rom and get my CWM recovery back I have to reset my phone to stock and start all over again with the EL26? Also, is the swype keyboard in the rapps, and how do i get the face unlock to work?
[Samsung Epic 4G Touch] slick_rick:
When you flashed Frankenstein rom, your kernel changed to the FE21 kernel included with the rom so not sure what you mean by you kept el29 kernel since that's not compatible with ICS. The reason you have stock android recovery now is because of all the bricking issues performing certain functions in custom ICS recovery so devs are leaving out custom recovery from their roms. So yes, when you want to change roms, backup, etc., you must go back to the el26 cwm kernel first and flash, backup, etc. from there. Not sure about your last two questions since I'm not using that rom. Let me know if you need anything else.
[Samsung Epic 4G Touch] DreamManifested:
Thanks. I see that the kernel has been switched, but initially I had the Blazer rom with el29. What rom are you running
[Samsung Epic 4G Touch] slick_rick:
I'm running CM9 alpha 4. Its fast, smooth, no problems at all.
[Samsung Epic 4G Touch] DreamManifested:
So all the ics rooms need el26 reboot versus el29
[Samsung Epic 4G Touch] slick_rick:
Not to sure what you mean by that. If you're saying what I think you're saying, yes you must use el26 cwm kernel whenever flashing anything ICS related or backing up or restoring. Using anything else and you risk bricking your phone.
[Samsung Epic 4G Touch] stormglove:
Slick_rick is correct, as far as Swype i just sign up for the Swype beta from you phone browser to get a download for it, that way i always have it to restore with titanium so i can get Swype on any rom. There's also some Swype keyboards floating around in the app section but i haven't tried them. They should work though.
[Samsung Epic 4G Touch] lambohoos:
Flashing Help

Wow... I needed this thread. I just recently went through what I thought were all the instructions to flash this rom. I had previously used the PD Odin executable routine to upgrade from Gingerbread to ICS. I saw the reviews on this rom and really liked what I saw. I used Odin 1.85 to set up CWM-El26 so I could flash this ROM. I got everything working ( I do get that yellow triangle on reboots) but I did notice the CWMod Recovery does not stay on the phone. It reverts back to the basic ICS Recovery (where I GUESS you cannot flash zip files). Now all this said... After flashing this ROM, I am still on FE16. Is there something else I am missing.

I got into rooting when I had my Dinosaur Moment, and now I have that itch again. Thanks again for all your help!
[Samsung Epic 4G Touch] slick_rick:
So what's wrong with your setup?
[Samsung Epic 4G Touch] lambohoos:
I guess I was a bit over the place. I was wondering why it wasn't keeping my CWM recovery instead of the generic one? I can deal with the yellow triangle.

---------- Post added at 04:30 PM ---------- Previous post was at 03:52 PM ----------

Swype is in the removed apps. You have to Unknown Sources checked under device administration. You can mount your phone, add the swype.apk file to the phone, and install it using the astro file manager. I still go back and forth between swype and the stock ICS keyboard. Word prediction seems to work better in the stock.
[Samsung Epic 4G Touch] slick_rick:
Oh well your cwm recovery disappeared because it wasnt packed into the kernel that came with the rom you flashed. And you can get rid of the yellow triangle using a USB jig or an app called triangle away. Just Google search something like "triangle away apk+chainfire+xda" and you should be able to find it.
[Samsung Epic 4G Touch] DreamManifested:
So how do I get cwm back. I just tried to start all the way from stock el29 and then get 26 And my phone was messing up until I put Frankenstein back on
[Samsung Epic 4G Touch] slick_rick:
Why do you need cwm recovery?
[Samsung Epic 4G Touch] DreamManifested:
Nevermind i got swype and face unlock now. Just put the apk on my usb and used astro. Thanks man
[Samsung Epic 4G Touch] lambohoos:
Hey... I hit the thank button but I got the triangle away and it worked like a charm! Thanks again. Maybe they can get the CWM 5.0.2.7 to stay packaged in the ROM setups in the future!
[Samsung Epic 4G Touch] DreamManifested:
so i tried to redo this flash with the el26 kernel. but then my phone started acting crazy, telling me that the calendar storage stopped working. finally after putting frankenstein back on my phone, it stopped coming up. the only problem im experiencing now is that i cant download pics in my text messaging. but i can use my 3g, 4g, and wifi for everything else. I dunno if this is because im in PR or because i messed something up. Please give me some feedback if you know anything
[Samsung Epic 4G Touch] stormglove:
You started up with el26? That will never work with this rom. You need an ics kernel.
[Samsung Epic 4G Touch] DreamManifested:
i know. but when you flash the rom it changes to ics. im saying, initially i started with the el29. QBkind77 advises to flash it after having the el26 installed, but i was too hasty.
[Samsung Epic 4G Touch] stormglove:
Hmmh...i only ever do el26 never el29. I'm not sure what happened then. You are correct if you flashed the ROM it is ics. It must have been a bad flash or a bad download as well, sorry.
[Samsung Epic 4G Touch] justin24:
I'm on Blu Kuban and I am on EL29 QB King 77 said I don't really need to switch Modems?? Is that corret? One XDA member said he uses FE 22 with out issue. I am using the ICS Blu Cuban rom.
[Samsung Epic 4G Touch] bendovermore:
Got good news my friend. U can flash the kernel separately. I prefer mobile Odin with calkulins fe22. As for the yellow triangle use triangle away by chainfire. All problems solved!!!