Rewrote the “init.triumph.rc” starting over from scratch.

For the most part what I had done was took the “init.rc” from the Sharp 2.3.5 boot.img and then using “meld” added in anything from the other variants “init.rc” scripts that had either been different or not found in the  Sharp 2.3.5 “init.rc” making comments as to what variant the entry originated if not already found inside the  Sharp 2.3.5 file. I then used “Meld” again doing a comparison with my modified Sharp 2.3.5 “init.rc” and the Stock CM7 “init.rc” and removed all entries from the custom “init.rc” already found in the Stock CM7 “init.rc”. After this I again used “Meld” and repeated the same process used above with the “init.rc” but used the “int.qcomm.rc” files in place of the “init.rc” using the Sharp 2.3.5 “int.qcomm.rc” again as the base moving in different entries found in the “int.qcomm.rc” from the other variants. After this I took the new “int.qcomm.rc” and added each entry into the new “init.rc” and renamed the file “init.triumph.rc” and added it into the device files renaming the old file “init.triumph.rc.old”.

After the file was in place I then went through and commented out any duplicate entries with different values based on what files are used from what variant. In doing this I did my best to leave notes on what entries would need to either be commented out or uncommented based on what proprietary files are used. I also removed and made notes on what entries will break data if used for future references .

So far have noticed differences in performance from using the old file. Wifi for one is connecting in half the time it had using the old file.

In doing all of what is above I also added the “int.qcomm.sh” script found inside all the varients boot,img's after extracting. For the most part it looks like what is found in the script will not have an effect or be used but noticed a few that may.