• 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)

Thank you, Bsydz! I tried the "fix permissions". I had forgot about that. But I went ahead and converted my second partition to FAT32 to avoid compatibility issues in the future. That format is supported by all ROMs I believe. Thank you for the help and the link to that other thread. Working great now! No issues here. Tethering is working great and everything else is very smooth. Best stock ROM I've tried so far. Thanks again!
 
Sorry for so many questions, but what is the difference between your "try 3" kernel and MobsterGunz kernel? Which one is recommended for version 7 of this rom?
 
Sorry for so many questions, but what is the difference between your "try 3" kernel and MobsterGunz kernel? Which one is recommended for version 7 of this rom?
Basically Mobstergunz made his own version of the ROM right after I released it and put his hybrid kernel in it but had some issues so he made a new one. Basically page 2 explains as much as anybody else knows, but there isn't alot of info on it, you can look at the Ginger Sharp thread for some info. I just built my kernel a little while ago and left the "try 3" to be able to distinguish them, cause I built about 5 but 3 was the best of the 3 working kernels I built. I plan on refining it over time I am just engulfed in CM10 right now. It is very solid and I added too many features to remember, but plan on having a full write up on what changed on the next release, but it's gonna be a minute before I rebuild it again.
 
Ohhh okay, great!! Thanks so much!
Your kernel is working great. Tethering works. Wifi and Bluetooth coincide without issues. And no deep sleep problems either. I'm so amazed with this especially that its a stock variant. Thanks so much for the hard work
 
So I havent tried the kernal that you built for this BSydz. Is it only for those that use tether? What does it exactly add?
 
Ohhh okay, great!! Thanks so much!
Your kernel is working great. Tethering works. Wifi and Bluetooth coincide without issues. And no deep sleep problems either. I'm so amazed with this especially that its a stock variant. Thanks so much for the hard work
Thanks for the feedback. This is actually a heavily modified Stock ROM from a different phone, there are only a few files borrowed from the Triumph. I also ported another ROM from another phone, the U9000 ROM, only the zimage of the kernel and the wifi drivers are from the Triumph on both. Though the U9000 ROM is basically stock, I haven't had alot of time to work on customizing it like I had on this ROM.
So I havent tried the kernal that you built for this BSydz. Is it only for those that use tether? What does it exactly add?
I basically found an issue in the kernel that could effect tether and I wanted to test/fix it, so I learned how to build kernels and built one. While I was there I used the building tools to enable support for a bunch of stuff and gradually took out stuff that was making it glitchy til I had try 3. I still have to get some credits up like b_randon who I referenced for the clock speeds and whoever he got them from, so the overclocking, as far as clock speeds go, came from bkernel. Everything else was options from the build tools and other tools that I used. Basically I added support for filesystems, devices and other services, plus unlocked the MTU for tethering purposes. I didn't want to make it too experimental, my goal with anything is stability. I would rather it work every time than faster sometimes.
 
I didn't want to make it too experimental, my goal with anything is stability. I would rather it work every time than faster sometimes.

I agree whole heartily. I'm not interested in overclocking or tether, although I have done it, I can live without it..
 
Just wanted to mention to those who may run into the same issue:

The pre-installed Google Maps seems to list the street names in Chinese. Thought I am not sure of the cause, I uninstalled Google Maps with Titanium Backup and re-downloaded it from the Market to correct this small issue.

Anyway, I must say.. WOW!! The GPS is virtually instant. I'm so happy to have this!! :)
 
I reloaded v7 over the install and the dropped signal issue seems to be resolved. Got a wedding tomorrow so I can't play with it too much.
 
Okay, I have the new rom installed and working great. Today, I tried the wireless tethering.
The phone showed up on the wireless site search and connected just fine with excellent signal.
But (there's always a but???) my browser won't receive any data. Network Connections shows 16kb of data transferred and received (prox.) but the browser is stuck in "waiting for sitename.com"

What am I missing?
 
Okay, I have the new rom installed and working great. Today, I tried the wireless tethering.
The phone showed up on the wireless site search and connected just fine with excellent signal.
But (there's always a but???) my browser won't receive any data. Network Connections shows 16kb of data transferred and received (prox.) but the browser is stuck in "waiting for sitename.com"

What am I missing?
I think you missed the page before this and some of this page. :D
The short answer is, the original Triumph kernel sets the MTU limit to 1472 and alot of sites won't load with tether because of that. I built a custom kernel to fix the problem, while I unlocked the MTU in the kernel, the MTU seems to be set by the network. So MTU resets with a reboot or the lease runs out on the connection and resets when it renews. The MTU should be at 1500 and there is a script in the second post along with the new kernel. As soon as I figure out how to get the MTU to be set at 1500 I will be releasing an updated ROM. But, until then, you just need to flash the new kernel, then run the script with wifi off and then everything should be good to go for tethering. Just remember that the MTU will reset at some point in time, and all you will need to do is run the script. Hope this helps.
 
Hi, thanks to your work bsydz. I updated from V4 to V7, hoping that wired tetherwing would work, but it's not. What happens when I enable it, with the USB connected, is it disables itself after a few seconds, automatically. As if the USB connection is being reset, and then it goes back to asking me if I want to enable USB storage.

I tried running your script, but got an error:
error: SIOCSIFMTU (Invalid argument)

Also, MMS (a big reason I'm using this ROM) doesn't seem to be working. I thought that was fixed a while back? Any thoughts?
 
Hi, thanks to your work bsydz. I updated from V4 to V7, hoping that wired tetherwing would work, but it's not. What happens when I enable it, with the USB connected, is it disables itself after a few seconds, automatically. As if the USB connection is being reset, and then it goes back to asking me if I want to enable USB storage.

I tried running your script, but got an error:
error: SIOCSIFMTU (Invalid argument)

Also, MMS (a big reason I'm using this ROM) doesn't seem to be working. I thought that was fixed a while back? Any thoughts?
Well, I am tethered right now with usb, as I type. I need to know your complete install process and which recovery you are using. The script will only work with the new kernel, from the feedback, and will not work if wifi is on cause it shuts off the 3G. MMS has been fixed for a while, and I just got one yesterday. I absolutely do not recommend just flashing Ver7 over any of the previous versions, especially Ver4 or earlier, cause a whole lot of system level stuff changed. Get back to me with some more info and then we can take it from there.
 
thanks for your time.

Using CWM 5.0.2.6
1) wipe data/factory reset
2) advanced/wipe dvalik cache
3) install zip from sdcard (your zip)
4) boot
5) reboot to CWM, install the bloatware remover
6) boot, try to run script that sets MTU to 1500, fails. Script runs OK if I set it to 1400. But that borks wifi access point, of course.

You're mentioning something about a new kernel, did I miss something on the first post about having to replace the kernel in 7?
 
thanks for your time.

Using CWM 5.0.2.6
1) wipe data/factory reset
2) advanced/wipe dvalik cache
3) install zip from sdcard (your zip)
4) boot
5) reboot to CWM, install the bloatware remover
6) boot, try to run script that sets MTU to 1500, fails. Script runs OK if I set it to 1400. But that borks wifi access point, of course.

You're mentioning something about a new kernel, did I miss something on the first post about having to replace the kernel in 7?
Thank you for the details.

So, first, update the recovery to 5.0.2.7, not 5.5.0.4 cause it has some issues restoring froyo backups. 5.0.2.6 seems to be leaving behind data when it factory resets, from what I have read. If you read back through this page and the last matt832 was having some problems with 5.0.2.6, and there are more details about tethering.

I just built the kernel a couple weeks ago to deal with the tether issue, but the script is still needed. The Stock kernel limits MTU to 1472, that is why you can set it lower but not higher than 1472. The new kernel is in the second post, always check out the second post for new stuff, the script is also there and both have a short description. Hope this helps.
 
I love the Sharp port ROM! I recently wiped v5 and installed v7 (managed to skip v6 because v5 was working so well for me). I'm also using BSydz's custom kernel for v7 try3. A couple of changes caught my eyes and ears:

The notification area shows the time on the right edge, and when I pulled down the notification area, the v5 Sharp ROM displayed the date on the left edge, just like the stock Motorola ROM, but the v7 Sharp ROM does not. Is that set by the theme? Is there a setting I'm overlooking to turn that back on? I'm surprised how quickly I've gotten used to seeing the date when pulling down the notification area.

The v7 Sharp ROM started making a sound every time the phone was turned on and shut down, independent of my custom startup and shutdown sounds. The thread about BSydz's U9000 port mentioned these could be notifications of the SD Card being mounted and dismounted, and the sound in the v7 Sharp ROM do coincide with SD Card on-screen notifications. I listened to the sounds in the /system/media/audio/notifications/ folder, and found the one that Sharp (and maybe U9000?) use for this notification. It was OnTheHunt.ogg. I renamed that file and the SD Card mount/dismounts became silent. Afterwards, I renamed the sound file back to OnTheHunt.ogg and the SD Card mount/dismounts remained silent. Not quite sure why, but it looks like once the sound file was missing the audio notification was disabled, and restoring the filename back did not re-enable it. That's fine with me, as I don't like my phone making more noise than it needs to.
 
I love the Sharp port ROM! I recently wiped v5 and installed v7 (managed to skip v6 because v5 was working so well for me). I'm also using BSydz's custom kernel for v7 try3. A couple of changes caught my eyes and ears:

The notification area shows the time on the right edge, and when I pulled down the notification area, the v5 Sharp ROM displayed the date on the left edge, just like the stock Motorola ROM, but the v7 Sharp ROM does not. Is that set by the theme? Is there a setting I'm overlooking to turn that back on? I'm surprised how quickly I've gotten used to seeing the date when pulling down the notification area.

The v7 Sharp ROM started making a sound every time the phone was turned on and shut down, independent of my custom startup and shutdown sounds. The thread about BSydz's U9000 port mentioned these could be notifications of the SD Card being mounted and dismounted, and the sound in the v7 Sharp ROM do coincide with SD Card on-screen notifications. I listened to the sounds in the /system/media/audio/notifications/ folder, and found the one that Sharp (and maybe U9000?) use for this notification. It was OnTheHunt.ogg. I renamed that file and the SD Card mount/dismounts became silent. Afterwards, I renamed the sound file back to OnTheHunt.ogg and the SD Card mount/dismounts remained silent. Not quite sure why, but it looks like once the sound file was missing the audio notification was disabled, and restoring the filename back did not re-enable it. That's fine with me, as I don't like my phone making more noise than it needs to.
Ok, I was having a hard time remembering the date in the drop down, had to install Ver5 on my dev phone to see what you were talking about. I am pretty sure it is still there, it is just in black letters against the new black status bar. I'll figure it out and update it. I will probably just release a flashable zip to fix it til I'm ready for a new release. As far as the notifications go, I probably snagged a line from the U9000 ROM that I didn't mean to. I'll look in to it and if it is in the same area as the date I will include it in the zip. Just remind me if you don't see it in the next week or so, gotta work for the next few days, so I may forget.
 
Thank you for the details.

So, first, update the recovery to 5.0.2.7, not 5.5.0.4 cause it has some issues restoring froyo backups. 5.0.2.6 seems to be leaving behind data when it factory resets, from what I have read. If you read back through this page and the last matt832 was having some problems with 5.0.2.6, and there are more details about tethering.

I just built the kernel a couple weeks ago to deal with the tether issue, but the script is still needed. The Stock kernel limits MTU to 1472, that is why you can set it lower but not higher than 1472. The new kernel is in the second post, always check out the second post for new stuff, the script is also there and both have a short description. Hope this helps.

Hi, ok I've updated to CWM 5.0.2.7, re-installed the V7, and installed the modded V7 kernel #3 after that, and then booted and applied your script.
In it's normal state after USB is just plugged in, my computer sees a Modem: "Modem over Android C000" However when I turn usb tethering on, this disappears and nothing comes up in its place. I don't recall doing anything special to get tethering working on CM7, just enabled it on the phone, plugged in the USB and viola the computer was online. Any suggestions?
 
Hi, ok I've updated to CWM 5.0.2.7, re-installed the V7, and installed the modded V7 kernel #3 after that, and then booted and applied your script.
In it's normal state after USB is just plugged in, my computer sees a Modem: "Modem over Android C000" However when I turn usb tethering on, this disappears and nothing comes up in its place. I don't recall doing anything special to get tethering working on CM7, just enabled it on the phone, plugged in the USB and viola the computer was online. Any suggestions?
Look in network adapters for USB Ethernet/RNDIS, and you may have to enable the network adapter in Network Connections. I have it hooked up right now, and it does just pop up and connects. One thing that may possibly help, is to install the drivers from the phone, the moto drivers may not have included that driver, just a shot in the dark but hey it may work.
 
Just a little aside which might be convenient right now,.

For wired tethering I have been using PDAnet for android. This is a free download and seems about half as fast as DSL. Around 600Mbps.

It installed and ran with no screwing around. I only use it when traveling, which means not much. But, so far so good.

When the ROM allows wireless, I'll retire PDAnet.
 
Look in network adapters for USB Ethernet/RNDIS, and you may have to enable the network adapter in Network Connections. I have it hooked up right now, and it does just pop up and connects. One thing that may possibly help, is to install the drivers from the phone, the moto drivers may not have included that driver, just a shot in the dark but hey it may work.

Ok, I did some more detailed analysis of what's going on from the device enumeration standpoint. I restored the CM7 backup and did tethering tests, noting in device manager the 'ADB Interface' which is what XP finds for the usb network interface.

CM7, with tethering not enabled:
ADB Interface, Vid_0489 Pid_C000 MI_02

CM7, with tethering enabled:
ADB Interface, Vid_0489 Pid_C008 MI_02

SharpROM v7, tethering not enabled:
ADB Interface, Vid_0489 Pid_C000 MI_02

SharpROM v7, tethering enabled:
No ADB Interface exists in the device manager

No unknown device is enumerated with a Pid_C008 at all, so I don't think it's driver related. When yours is working, what Pid are you seeing
 
Just a little aside which might be convenient right now,.

For wired tethering I have been using PDAnet for android. This is a free download and seems about half as fast as DSL. Around 600Mbps.

It installed and ran with no screwing around. I only use it when traveling, which means not much. But, so far so good.

When the ROM allows wireless, I'll retire PDAnet.
Thanks for the feedback. The wifi hotspot does work, it just needs the new kernel and run a script, check the second post. Same goes for usb tether, with the new kernel and the script it works fine.
Ok, I did some more detailed analysis of what's going on from the device enumeration standpoint. I restored the CM7 backup and did tethering tests, noting in device manager the 'ADB Interface' which is what XP finds for the usb network interface.

CM7, with tethering not enabled:
ADB Interface, Vid_0489 Pid_C000 MI_02

CM7, with tethering enabled:
ADB Interface, Vid_0489 Pid_C008 MI_02

SharpROM v7, tethering not enabled:
ADB Interface, Vid_0489 Pid_C000 MI_02

SharpROM v7, tethering enabled:
No ADB Interface exists in the device manager

No unknown device is enumerated with a Pid_C008 at all, so I don't think it's driver related. When yours is working, what Pid are you seeing
I'm sorry, I don't know what is going on with your setup, I run Windows 7, and the hardware IDs I get are below. It maybe windows xp not switching drivers, you sound like you are familiar with device manager, so I won't go in to all that, but maybe refreshing the devices while the tether is on, I have had usb issues like that on several occasions with xp. I would suggest reinstalling the drivers from the phone, just to be sure. It even shows up in Ubuntu for me. I just really can't think of why it isn't working. Maybe somebody else has had a similar issue that can help.

Enabled: USB\VID_0489&PID_C008&MI_00

Disabled: USB\VID_0489&PID_C001&MI_01
 
A couple of things.

1. Any chance for a shut down menu? (shut down, reboot, recovery)
2. Making the app drawer settings stick. Every time I open it, I have to reset it so that the apps are in alphabetical order.
3. The home screen is driving me nuts. Is there any way to set it as a different screen and not just the first? I'd like to center the wallpaper on the middle screen but the home takes me back to the first screen to the left.
 
Can someone summarize quickly the advantages of this ROM over the rooted stock ROM? Is it faster, better battery life? What are the biggest advantages? Sorry if this information is already lodged somewhere upthread.
 
as my real estate friend always says: location, location, location.
Sharp rom comes with excellent GPS lock time.
 
Back
Top Bottom