• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][PORT] Sharp ROM 2.2.2 for the Triumph (Updated: 12/16/12)

[ROM] Stock 2.3.5 from Taiwan Sharp SH8188U - xda-developers ....dont know if its on there but its from xda....might help might be old news
Thanks, but that is the one I found months ago and led me to finding this cause it would not work. I appreciate it though.
For some reason, something was setting the minimum CPU scaling frequency to 245... I went into the system folder a low and behold it was set to that. SO I did some inspection.

On your try 3 kernel /etc/init/init.qcom.post_boot.sh runs as a service via init.qcom.rc and was forcing the cpu governors and speeds to those levels. I simply commented out those lines in init.qcom.rc and setcpu was able to set things correctly.

I also noticed that the toolbox/getprop does not work, so a lot of the scripts that are in there are misbehaving.

Wifi does not turn off automatically on lockscreen, so the phone never goes into deep sleep, which is a huge problem. I went and looked at the code quickly and noticed the wifi unload script was not seeing screen lock, so I will look around some more to see where the event comes so I may trigger the unload.
Thanks for the feedback.

Ok, so I built a new kernel and am about to make the boot.img and when I looked, I had the min cpu set at 122880 in the init.rc. So I'll have to search or ask a few of the other devs that have built kernels to see what has to be changed, because the post boot is the same on stock and a couple other X6 variant ROMs that I checked, kernel and ROM. So I have to say it must be in the kernel. No-frills CPU has no issues setting the speed at boot as far as I have seen. This was mentioned on the second or third page when mobstergunz made his kernel. I'll do some research but right now I am almost done with this kernel just need to test it, so hopefully I can get it figured out, but maybe not on this run.

I just included a few things in the kernel that are in the toolbox file like dual sd and a few others but, I don't have source for the Froyo kernels except the Triumph, so I am referencing GB kernels for fixes. Plus I am just starting to learn how to code, I never really looked at code before a few months ago, plus I just got my first android phone about a year ago, so you'll have to excuse my lack of some basic knowledge. I would appreciate if you could explain how the scripts are misbehaving, and any other info would be much appreciated.

I have never had the not deep sleeping issue with this ROM, JD was the culprit for a few people, that was why I suggested ditching JD for now. Wifi shouldn't shut off or go in to deep sleep at the lockscreen as far as I know, but as I said before, you'll have to excuse my lack of some basic knowledge of android. Where exactly did you find the wifi unload script? If it was in a system file and not in a built file, like framework.jar, then lockscreen is not in any of the X6 variant stock ROMs.

Again, thanks for the feedback, specifics definitely help, but sometimes they go over my head. Once I learn something though, it just kinda sticks, so keep the details coming guys.
 
I just spent a while trying to make a flashable zip to put in the MODs section but nothing I did would work, I rewrote the updater script 5 times and it looked like it worked but still sound on boot. I had to use root explorer and follow these instructions, http://androidforums.com/triumph-all-things-root/380511-how-silence-boot-ups-shut-downs.html, the flashable zip on that page did not work for me either.
It is located here /hidden/data/Power-on sound/.

Can i Just delete the sound and not have one at all?
No, you will have issues, you just need to replace the file with the one from the thread or use some of the suggestions on how to make a custom one. Most of the details can be found in that thread. Once you change it, it will stay that way until you flash either the stock ROM or hidden partition zip from b_randon14. Hope this helps.
 
I used the included wifi hotspot no other apps for tether.

I just tried ES file explorer but it won't run scripts, or I am missing a setting, also wouldn't run with Astro. I have run it with Root Browser Lite, and Rom Toolbox Lite, but had to take the space out of the file name. I know it works with Root Explorer. Any of the script apps will run it. These are just a couple tests I did.

The terminal emulator way is the for sure way to do it.
In terminal emulator:
Type su
Hit enter
Allow root access
Type "ifconfig rmnet0 mtu 1500" without the quotes
Hit enter
You're done

Hi Bsydz,

First of all, I want to thank you vehemently! You finally got tether to work on my Triumph.

I am using the latest 7/15 rom and your v3 kernel.

I unzipped the MTU script file and placed the .sh file into the init.d folder that I created in system/etc.

When I manually run the .sh file using root explorer, tethering works like a champ, and its fast too.

I do have a question:

The .sh file in my created init.d folder doesn't seem to run automatically when I reboot the phone. Aren't the init.d folder's contents supposed to run automatically? Its ok, it works when I manually run it, but I was just wondering if it is possible to make it auto run at boot.
 
Hey guys, I just finished my updated kernel and need some people to take it for a test spin. I updated the touchscreen drivers along with some video, audio and headset code. I also pushed the kernel source to github if anybody wants to play around with it. https://github.com/BSydz/Triumph-Sharp-2.2.2-Custom-Kernel.git

BSydz Sharp Ver8 Custom Kernel.zip

I basically just need some input on how the touchscreen is performing and if I broke any audio or headset stuff. I have it running on both my phones as we speak, I wouldn't ask anybody to try something I haven't already done, I just can't test everything, and don't have any kind of headset to test with. Thanks for all the help guys, hopefully I can get Ver8 together before I have to go back to work monday. :D

I also think I found out how to get the GB kernels from other X6 variants to read our baseband version correctly. Things you stumble upon when you add too much code, gotta love it. :hmmmm: :D

Edit: I messed with the config file so OC is not included, but will be when I release it.
 
Hi Bsydz,

First of all, I want to thank you vehemently! You finally got tether to work on my Triumph.

I am using the latest 7/15 rom and your v3 kernel.

I unzipped the MTU script file and placed the .sh file into the init.d folder that I created in system/etc.

When I manually run the .sh file using root explorer, tethering works like a champ, and its fast too.

I do have a question:

The .sh file in my created init.d folder doesn't seem to run automatically when I reboot the phone. Aren't the init.d folder's contents supposed to run automatically? Its ok, it works when I manually run it, but I was just wondering if it is possible to make it auto run at boot.
Thank you. That seems to be the million dollar question, how to get it to run automatically or get it set how it needs to be. If you find a way or anybody else has any suggestions feel free to post it. I only have so much time to work on this, as the head salesman at work just sold 6 more roofs and we are currently getting our butts kicked trying to keep up. I just don't have the mental capacity after work to analyze code. If anybody wants to help out, send me a PM. Not that there is much to do on this ROM, but basically everything I fix in this can be put in the U9000 ROM also and may help get GB on our phone too.
 
New touch screen drivers are amazing...for the first time i played temple run and lost because i suck at it and not because the touchscreen drivers suck...lol...more great stuff,keep it up...thanks!

Noticed some screen flicker after flashing new kernel...ha..d max events set to 175 since i started with this rom and changed to 250 and flicker gone...dont know of it had anything to do with the kernel but i had never noticed it before...like the new kernel so far cant wait for finished product with oc
 
bsydz... Some good background on init:

Android Initialization Process - Android

again on property system:

just do IT: android property system


I looked at init.rc and I see where min cpu set to 122880, the issue is that later scripts override it. after init.rc, the init.qcom* init scripts are run, and init.qcom.rc calls /etc/init.qcom.post_boot.sh which runs as a service (and will rerun on state changes) and sets the min CPU speed to 288Mhz and forces the ondemand governor. The issue is that root is built at runtime, so the only option is for me to modify /etc (/system/etc) where I put exit 1 into the top of init.qcom.post_boot.sh to stop the service from running and hence from overriding my governor and clock settings.

Now I think I found the script which correctly unloads the wifi driver, one problem is in the current kernel the getprop (toolbox) does not work. To get the kernel to release the wakelock it looks like two modules need to be unloaded (libra.ko and libradioif.ko). I polled the currently running phone (lsmod) and infact when wifi is on, those two modules are loaded. There also seems to be some inconsistency since some scripts call 7627_surf and some call 7630_surf manually because I'm assuming this is a hack because the triumph really has an 8655 and the writers had to compensate with some inconsistencies in the older S2 chipset drivers. In any case it's messy.

So I am going to manually run this and see what happens. If it works then there is a possibility to get deep sleep running without manually turning off the toggle.
 
I love this ROM. I don't like the sharp camera though. Can someone who has successfully replaced the sharp camera with the stock camera explain how they did it? Can I take the Stock camera and camcorder from the U9000 ROM and just replace them? Do I have to do this before flashing the ROM or can I do it if I already have it flashed?

Thanks for any help.
 
bsydz... Some good background on init:

Android Initialization Process - Android

again on property system:

just do IT: android property system


I looked at init.rc and I see where min cpu set to 122880, the issue is that later scripts override it. after init.rc, the init.qcom* init scripts are run, and init.qcom.rc calls /etc/init.qcom.post_boot.sh which runs as a service (and will rerun on state changes) and sets the min CPU speed to 288Mhz and forces the ondemand governor. The issue is that root is built at runtime, so the only option is for me to modify /etc (/system/etc) where I put exit 1 into the top of init.qcom.post_boot.sh to stop the service from running and hence from overriding my governor and clock settings.

Now I think I found the script which correctly unloads the wifi driver, one problem is in the current kernel the getprop (toolbox) does not work. To get the kernel to release the wakelock it looks like two modules need to be unloaded (libra.ko and libradioif.ko). I polled the currently running phone (lsmod) and infact when wifi is on, those two modules are loaded. There also seems to be some inconsistency since some scripts call 7627_surf and some call 7630_surf manually because I'm assuming this is a hack because the triumph really has an 8655 and the writers had to compensate with some inconsistencies in the older S2 chipset drivers. In any case it's messy.

So I am going to manually run this and see what happens. If it works then there is a possibility to get deep sleep running without manually turning off the toggle.
Thanks for the info. Now, to clarify, there is no deep sleep issue with this ROM, the only deep sleep issues have all been with apps or tweaks that have been applied. Also the kernel zImage is a slightly modified Stock Triumph kernel, the ramdisk is from the Sharp ROM, they are almost identical for the most part, also the wifi drivers(the two ko files you mentioned) are from the Triumph because I had to use the zImage to get BT to work. This is the same setup I used with the U9000 ROM, with the ramdisk from that cause it was slightly different. The toolbox is identical between the ROMs so if something is not working it probably wasn't working in stock either. I only have the stock Triumph froyo kernel source so I have to work with what I have. You can try the toolbox with the original kernel, it is a fully stock zImage. Basically there are no wifi or deep sleep issues that I have seen, or have been reported with Ver5 or beyond, there are a ton of posts about deep sleep and wifi in the first 6 pages or so. You can also try mobstergunz kernel in the second post to see if there is a difference but setcpu doesn't set the settings on boot with it either, but no-frills seems to work with both kernels though. This is my first attempt at building a kernel from source so if you have any suggestions I will try them out. I am still learning, I don't know what half the stuff I edit does, it is all trial and error, with a lot of error. :D
 
I love this ROM. I don't like the sharp camera though. Can someone who has successfully replaced the sharp camera with the stock camera explain how they did it? Can I take the Stock camera and camcorder from the U9000 ROM and just replace them? Do I have to do this before flashing the ROM or can I do it if I already have it flashed?

Thanks for any help.
Either way should work fine. If you do it through a root explorer just make sure you set the permissions.
 
I've been fighting with this kernel all day. Just when I had it almost finished I broke wifi and can't seem to figure out what happened. I have to give it a rest cause I have to get up at 5AM, so no update for a minute. I uploaded the framework res with the status bar date fixed, the link is below for anybody interested. Just replace the framework-res.apk in system/framework in the Ver7 ROM with the one in the zip, then flash the modified ROM. I would make this flashable but I don't have the time right now and hopefully I'll get a new release out soon.

Hopefully I'll have some time next weekend or if it rains some time this week to get some stuff put together.

BSydz Ver7 Status Bar Date Fix.zip This is not Flashable!
http://www.mediafire.com/?533h98d4n1qai71
 
Thanks for the info. Now, to clarify, there is no deep sleep issue with this ROM, the only deep sleep issues have all been with apps or tweaks that have been applied. Also the kernel zImage is a slightly modified Stock Triumph kernel, the ramdisk is from the Sharp ROM, they are almost identical for the most part, also the wifi drivers(the two ko files you mentioned) are from the Triumph because I had to use the zImage to get BT to work. This is the same setup I used with the U9000 ROM, with the ramdisk from that cause it was slightly different. The toolbox is identical between the ROMs so if something is not working it probably wasn't working in stock either. I only have the stock Triumph froyo kernel source so I have to work with what I have. You can try the toolbox with the original kernel, it is a fully stock zImage. Basically there are no wifi or deep sleep issues that I have seen, or have been reported with Ver5 or beyond, there are a ton of posts about deep sleep and wifi in the first 6 pages or so. You can also try mobstergunz kernel in the second post to see if there is a difference but setcpu doesn't set the settings on boot with it either, but no-frills seems to work with both kernels though. This is my first attempt at building a kernel from source so if you have any suggestions I will try them out. I am still learning, I don't know what half the stuff I edit does, it is all trial and error, with a lot of error. :D

Bsydz. n00b. I found the issue. Apparently when I flashed your kernel the default advanced wifi setting is to keep a wakelock. I have it turned off now when screen off and it is both turning the radio off correctly and releasing the partial wakelock. I put a marker in that script I mentioned and I don't think it's being used, so this must be done in the framework with wifimanager all together.

As for the governor, I've been playing around the last few days (among the other stuff), and I found that the interactive/deadline at 61/1000 is smooth as silk and the screen touch responsiveness is leaps better than ondemand or the X and smoothass I was trying. I will let you guys know how the battery life plays out, but it looks like 3-4% per hour in deep sleep mode or running mostly in 61mhz so I'm not sure if the GSM overlay on CDMA is purely battery optimizing...

BTW - Awesome job on this. You ROM has made this POS usable... My wife has stopped complaining, so that in itself is a blessing... Just thought you should know that your time is making a direct benefit to the community, and is much appreciated.
 
For me, the most look forward feature of the new kernel is the touch-screen improvement. Thanks for the hard work, BSydz!


The new kernel runs awesomely for me touch screen is super responsive. But just to be clear I removed the thick plastic screen protector they applied in the factory that was causing me to have sensitivity issues. I replaced it with one from skinomi and it is millions of times better! I also pulled the Mms.apk out of another sharp rom i found on here because i couldn't handle the white theme to the stock Mms. Maybe you should make that a avaiable option BSydz. I also found one that gives hella options but it force closes. Maybe you can get it to work on this rom!
 
Mods:
Most mods are flashable in recovery and will not require reinstalling anything.


MODs can be reversed by just flashing the same or latest version of the ROM


MTU/Tether FIX:
Here is the script for anybody that wants to try this out. Just extract the file,and open it in a root explorer and select execute. Wifi must be disabled and 3G must be active for the script to execute correctly. It doesn't seem to work from the SD card, I put it in system/etc/init.d folder and it worked. This also may only work with my custom kernel.(more testing is needed) The custom kernel should be compatible with all Sharp ROM versions.
BSydz mtu 1500.sh.zip
Kernels:
Boot to recovery, flash zip file, then reboot.

BSydz Sharp Ver7 Original Kernel:
BSydz Sharp Ver7 Original Kernel.zip


BSydz Sharp Ver7 Custom Kernel - try 3:
Credit to b_randon14, pwnyourace, Napsta, DooMLoRD, and FXP for the overclock patch.
This is a custom kernel I built that changes the MTU settings and includes overclock and underclock abilities. This custom kernel should be compatible with all Sharp ROM versions. This will be refined over time.

BSydz Sharp Ver7 Custom Kernel - try 3.zip


Mobstergunz Updated Ginger Sharp 2.2 kernel:

Thanks to Mobstergunz
Hybrid Kernel for Rev 2.2.zip
Build.props:
Installation:
Boot in to recovery and flash zip. Or extract the zip and copy the build.prop to your system folder.



BSydz Sharp 2.2 Ver7 build.prop:
This is the original Ver7 build.prop
BSydz Sharp 2.2 Ver7 build.prop.zip


BSydz Sharp 2.2 Ver7 Triumph Stock build.prop:
This will make the phone look like a Stock Triumph
BSydz Sharp 2.2 Ver7 Triumph Stock build.prop.zip


BSydz Sharp 2.2 Ver7 Thunder.prop:
This will make your phone look like an HTC Thunderbolt
Thanks to JollyRoger87 for creating the thunder.prop concept.

BSydz Sharp 2.2 Ver7 Thunder.prop.zip


BSydz Sharp 2.2 Ver7 Sharp 2.35 build.prop:
This will make the phone look like the GB version of the Sharp ROM
BSydz Sharp 2.2 Ver7 Sharp 2.35 build.prop.zip

Boot Animation Sound:
Info can be found here.
Status Bar Notification Widgets:
Thanks to ajace for bringing this to my attention.
Play Store Link: Status Bar Notification Widgets

attachment.php
BSydz Stock Sharp 2.2 Triumph Bloat Remover
Installation: Flash in recovery, then reboot.
Removes:
Android_RSS_Home2_FB3_hdpi.apk: RSS Reader
DocViewer.apk: Document Viewer
FileManager_FB3_hdpi.apk: File Manager
FMRadio_Home3_hdpi.apk: FM Radio
NameCardRec.apk: A Business Card Reader/Rolodex
NotePad_FB3_hdpi.apk: Notepad
VoiceNote_FB3_hdpi.apk; Voice Note Taker
GenieWidget.apk: News & Weather app

Note: This is very easy to customize to your liking, just open the zip and edit updater.script in META-INF\com\google\android with notepad++ or your favorite text editor.

BSydz Stock Sharp 2.2 Triumph Bloat Remover.zip


Hopefully, many more to come!

ENJOY!!!


__________________
"If somethings in your way, you gotta move it or use it." - Me

If you would like to thank me, beyond just saying thanks, you can donate to my coffee fund to keep my eyes open.
Donate


ide like to thank you first of all, //fist-bump//.

but could you include in the description what exactly each file does when flashed?

for instance the kernels or props or is the mtu/tethering update included in the other kernels, which i think it may be in the try 3 one?...??

whats the difference between each of those and the one included in the rom on the main post? i know i could read through 20 pages of posts to find out but imo the info should be there, it wouldn't take long.

thanks again, nice work!
 
Man i just flashed CM9 onto my triumph ....... Now i have been running CM9 on my optimus V with no worries and I loved it. I ran it on the Triumph and I hate it. No offense to the DEVS they are doing great work for what it is but i hate it when compared to this ROM .The screen responsiveness is horrible i lasted 10 minutes. I switched right back no need for anything else. BSydz phenominal job man this is the best ROM i have used on any phone short of Harmonia 2 .
 
ide like to thank you first of all, //fist-bump//.

but could you include in the description what exactly each file does when flashed?

for instance the kernels or props or is the mtu/tethering update included in the other kernels, which i think it may be in the try 3 one?...??

whats the difference between each of those and the one included in the rom on the main post? i know i could read through 20 pages of posts to find out but imo the info should be there, it wouldn't take long.

thanks again, nice work!
Thank you for the feedback. There is not much more info to include. Basically, the build.props just make the phone look like another phone, there are no tweaks included. Some people wanted it to look like a Triumph and some wanted the thunder.prop for game compatibility in the market, I just put up the rest for the heck of it. I have no documentation for mobstergunz kernel, and my try 3 is, just like the discription says "This is a custom kernel I built that changes the MTU settings and includes overclock and underclock abilities.". Basically I found what was stopping tether in the kernel and tried to fix it, while it didn't fix it, it unlocked the MTU so that a script could set the MTU correctly, and while I was there I included OC abilities. I honestly don't understand what info may be missing, but if anybody has any suggestions I am always open to any help. Hope this puts some things in perspective for you, I'm still learning myself, but basically everything I have learned has came from this forum. If you have any more questions or suggestions feel free to post them.
 
Hey guys, I just finished my updated kernel and need some people to take it for a test spin. I updated the touchscreen drivers along with some video, audio and headset code. I also pushed the kernel source to github if anybody wants to play around with it. https://github.com/BSydz/Triumph-Sharp-2.2.2-Custom-Kernel.git

BSydz Sharp Ver8 Custom Kernel.zip

I basically just need some input on how the touchscreen is performing and if I broke any audio or headset stuff. I have it running on both my phones as we speak, I wouldn't ask anybody to try something I haven't already done, I just can't test everything, and don't have any kind of headset to test with. Thanks for all the help guys, hopefully I can get Ver8 together before I have to go back to work monday. :D

I also think I found out how to get the GB kernels from other X6 variants to read our baseband version correctly. Things you stumble upon when you add too much code, gotta love it. :hmmmm: :D

Edit: I messed with the config file so OC is not included, but will be when I release it.

I've basically stopped following this thread cause my phone was working as it should :). Going to flash this weekend and post any bugs that might come up.

Thanks again BSydz!
 
Ver8, check out post #979. The only thing that could possibly make it better would be the option to overclock. But even without overclocking, my phone has never ran this smooth. Bsydz is a genuis
 
This is ROM is great i really enjoy it, im only having one isse, when i connect the triumph to my computer open up the drive it only includes 4 "files" (autorun, drive, Phone_F_USB_Driver_v.1.1.7 , setup) rather than what it previously had a bunch folders and files in particular im looking at putting new music on my phone and the Sony Music folder is not there. Thanks for any help, ive searched through this thread and havent had any luck. PS i came from CM7 and dont have any other mods i know of
 
This is ROM is great i really enjoy it, im only having one isse, when i connect the triumph to my computer open up the drive it only includes 4 "files" (autorun, drive, Phone_F_USB_Driver_v.1.1.7 , setup) rather than what it previously had a bunch folders and files in particular im looking at putting new music on my phone and the Sony Music folder is not there. Thanks for any help, ive searched through this thread and havent had any luck. PS i came from CM7 and dont have any other mods i know of
Sounds like you are not turning on usb storage. When you connect the usb cable, either a screen with a little android guy will pop up and then just select turn on usb storage, or in the notification drop down you will see usb connected, when you select it it will take you to the screen mentioned above. Or you can just put your sd card into the computer to transfer files. Hope this helps.
 
Sounds like you are not turning on usb storage. When you connect the usb cable, either a screen with a little android guy will pop up and then just select turn on usb storage, or in the notification drop down you will see usb connected, when you select it it will take you to the screen mentioned above. Or you can just put your sd card into the computer to transfer files. Hope this helps.

sorry it was me being an idiot, for what ever reason though 2 windows were popping up and i didnt look at the other window. Thanks though
 
Back
Top Bottom