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

Root [ROM] CM7 TG-Reloaded (Final: 03-25)

I've had zero issues with this ROM, but I also format /system, /data, /cache, then wipe dalvik cache before flashing any new updates, followed by gapps. I don't play games, but Google Earth's 3D view and Street View for Google Maps both worked great and run silky smooth now. I run my phone at 245 MHz - 1.4 GHz using the interactive governor. The 1.4 GHz range is the fastest speed the MSM8x55 ships at according to Wikipedia, so I figured it was a good balance between truly unleashing the CPU in times of need and running a minimal risk of long-term damage, especially since I don't game on the phone so the chip is never under heavy load for very long anyways, nor does it ever experience too extreme of an environment in terms of temperature.

SaurusX said:
That's why you have to insert it yourself. Use jdgui to look at Motorola's stock framework.jar and replicate the needed code into CM7. I did it for the DroidX and now we have fully functioning HDMI in CM7 with it coming soon to MIUI (video currently works). What I did for the DX won't translate directly as I've already examined a system dump for the Triumph and I can tell things are just different. It's the difference between the Qualcomm MSM8665 chip in the Triumph and the TI OMAP3 in the DroidX. If you're interested, see the link below to see how I did it on the DX.

[MOD] How to Enable HDMI Video on a ROM - Audio SOLVED! - RootzWiki
Click to expand...

If this does prove fruitful, our phone will be pretty much perfect as far as I'm personally concerned. Although, having an ICS ROM as stable as this one would be rather incredible. Shame the phone manufacturers are too blind to see how much value many of us place on high-quality software updates for those who have little intention of purchasing any new hardware...
 
SaurusX said:
That's why you have to insert it yourself. Use jdgui to look at Motorola's stock framework.jar and replicate the needed code into CM7. I did it for the DroidX and now we have fully functioning HDMI in CM7 with it coming soon to MIUI (video currently works). What I did for the DX won't translate directly as I've already examined a system dump for the Triumph and I can tell things are just different. It's the difference between the Qualcomm MSM8665 chip in the Triumph and the TI OMAP3 in the DroidX. If you're interested, see the link below to see how I did it on the DX.

[MOD] How to Enable HDMI Video on a ROM - Audio SOLVED! - RootzWiki
Click to expand...

It has some interesting ideas, the MT is not really a Motorola phone with Sense or any of the other proprietary blobs like on the DroidX. There's still a lot of work in trying to figure out what the stock framework signals it's sending out and coding that into CM7.
 
Whyzor said:
It has some interesting ideas, the MT is not really a Motorola phone with Sense or any of the other proprietary blobs like on the DroidX. There's still a lot of work in trying to figure out what the stock framework signals it's sending out and coding that into CM7.
Click to expand...

No doubt that it will be some digging around to try and find out what's changed in the framework. However, if you've already eliminated the possibility of the HDMI being driven by a system app (like the DroidX) then it MUST be in the framework. I would compare the Cyanogenmod source code to that new 2.3.4 ROM posted by ziggy46 so that you're closer to comparing apples to apples. Careful analysis of logcats from a working and then a non-working ROM was a huge part in me unraveling the DroidX. One thing I noticed working on the DX was that the essential HDMI framework coding was simply slipped into the AOSP source by Motorola. Almost nothing else was changed. It was really me looking at the Cyanogenmod source in one window and then the decompiled jdgui code in another and reconstructing the pre-compiled code.

I'm really hoping someone can accomplish this on the Triumph, because I'd love to ditch Verizon for the $35/month Virgin plan. :D
 
SaurusX said:
No doubt that it will be some digging around to try and find out what's changed in the framework. However, if you've already eliminated the possibility of the HDMI being driven by a system app (like the DroidX) then it MUST be in the framework. I would compare the Cyanogenmod source code to that new 2.3.4 ROM posted by ziggy46 so that you're closer to comparing apples to apples. Careful analysis of logcats from a working and then a non-working ROM was a huge part in me unraveling the DroidX. One thing I noticed working on the DX was that the essential HDMI framework coding was simply slipped into the AOSP source by Motorola. Almost nothing else was changed. It was really me looking at the Cyanogenmod source in one window and then the decompiled jdgui code in another and reconstructing the pre-compiled code.

I'm really hoping someone can accomplish this on the Triumph, because I'd love to ditch Verizon for the $35/month Virgin plan. :D
Click to expand...


I've been working on this for awhile now and have had some success but there are still problems. I've posted my progress in this thread: http://androidforums.com/triumph-all-things-root/488824-dev-continuing-triumph-ics-development-21.html

I've gotten to the point where I get a blue screen coming up (so there is some signal) on my monitor when I plug it in but nothing more.

The problem is that the stuff that drives the HDMI is all over the place: the hdmi daemon and all the libraries it depends on (libsurfaceflinger, liboverlay etc.) as well as the HDMIService and HDMIListener in the framework as well as references all over the place and CM7 has no backend support for it.
It also looks like it is significantly different from the DroidX fixes which you had to do, which isn't surprising as it is a completely different chip.

I've been pulling stuff from the andro-id rom which is a GB based rom with working HDMI. I have pulled apart the services.jar file (by using dex2jar and then jdgui). I haven't tried the framework.jar file yet but it's hard to know where to look. I am pretty sure the problems that remain are somewhere in the framework (likely either in the services.jar or framework.jar)

If you get the triumph I could get you caught up at exactly all that I have done to get to this point and maybe you could help finish her up as you already have experience with this :)
 
I am going to ask anyway I don't see it here, I had an optimus v and flashed roms on it with no problems,so what exactly do i need on my card the rom of course, latest Gapps of course, anything else? besides the painfully obvious. I'll wipe the cache and dalvik cache to save my stuff create a backup and all, but with V i had to do all this formatting this and that, is that necessay? I don't see a step by step for the newb which I guess I still am. Any help would be appreciated!!
 
jkdmoore said:
I am going to ask anyway I don't see it here, I had an optimus v and flashed roms on it with no problems,so what exactly do i need on my card the rom of course, latest Gapps of course, anything else? besides the painfully obvious. I'll wipe the cache and dalvik cache to save my stuff create a backup and all, but with V i had to do all this formatting this and that, is that necessay? I don't see a step by step for the newb which I guess I still am. Any help would be appreciated!!
Click to expand...

See http://androidforums.com/triumph-all-things-root/445483-guide-installing-cwm-custom-rom-motorola-triumph.html

Basically for your first install of a Rom you need to Wipe Data/Factory Reset and for upgrades of the same rom afterwards you just need to Wipe Cache
 
jkdmoore said:
I am going to ask anyway I don't see it here, I had an optimus v and flashed roms on it with no problems,so what exactly do i need on my card the rom of course, latest Gapps of course, anything else? besides the painfully obvious. I'll wipe the cache and dalvik cache to save my stuff create a backup and all, but with V i had to do all this formatting this and that, is that necessay? I don't see a step by step for the newb which I guess I still am. Any help would be appreciated!!
Click to expand...
http://androidforums.com/triumph-al...stalling-cwm-custom-rom-motorola-triumph.html

http://androidforums.com/triumph-al...l-things-root-guide-updated-03-01-2012-a.html

sorry, i pointed to the threads and stepped out, i guess i forgot to hit send (insert facepalm)
 
I know I'm clogging up this thread with HDMI babble, so one last post from me here. Reading through the ICS Development thread it looks like there's already some real progress made in enabling HDMI. I can also tell that the hardware and software is entirely different from what I was playing around with. With any luck you guys will have it figured out by the time my contract is up and I can start saving some real money by moving to Virgin. The Triumph is obviously the flagship phone and the only one I would consider getting. I don't want to give up features I already have, but I don't want to go back to Froyo either.
 
SaurusX said:
No doubt that it will be some digging around to try and find out what's changed in the framework. However, if you've already eliminated the possibility of the HDMI being driven by a system app (like the DroidX) then it MUST be in the framework. I would compare the Cyanogenmod source code to that new 2.3.4 ROM posted by ziggy46 so that you're closer to comparing apples to apples. Careful analysis of logcats from a working and then a non-working ROM was a huge part in me unraveling the DroidX. One thing I noticed working on the DX was that the essential HDMI framework coding was simply slipped into the AOSP source by Motorola. Almost nothing else was changed. It was really me looking at the Cyanogenmod source in one window and then the decompiled jdgui code in another and reconstructing the pre-compiled code.

I'm really hoping someone can accomplish this on the Triumph, because I'd love to ditch Verizon for the $35/month Virgin plan. :D
Click to expand...
try 22.80 with grandfather in plan of $25 dollars and keepcalling.ca to topup for %5 discount. yes this makes triumph a good phone already
 
SaurusX said:
I know I'm clogging up this thread with HDMI babble, so one last post from me here. Reading through the ICS Development thread it looks like there's already some real progress made in enabling HDMI. I can also tell that the hardware and software is entirely different from what I was playing around with. With any luck you guys will have it figured out by the time my contract is up and I can start saving some real money by moving to Virgin. The Triumph is obviously the flagship phone and the only one I would consider getting. I don't want to give up features I already have, but I don't want to go back to Froyo either.
Click to expand...

I don't consider it "clogging up this thread with HDMI babble". I think it's valuable input that could really help the one and only thing this ROM is lacking. Not sure if I speak for most of us on here but I would love to have HDMI function properly on this ROM. Also, it seems that you have more knowledge on the subject than most of us. I would like to help, just don't have a clue where to start. So thanks for trying to help us out even if nothing does come of it. And thanks to Whyzor again for the continued awesomeness and development of this ROM!!!
 
I have confirmed the "screen dim before off" change. I have loaded TG's beta .1 and it will dim before off. On beta .2 and above it won't. Could someone else double confirm this also? After I get my environment set up and look into the camera app, I'll look into this one.
 
If someone wants to beat me to the find, I'm all for it. We know the approximate date. We just need to rummage around. It's not like I REALLY know what I'm doing.:D
I just may be foolish enough to try. That and my friend keeps telling he will help me learn this stuff.
 
jkdmoore said:
okay can i use the latest Gapps from xda with this rom?
Click to expand...

As long as it's for CM7, yes. But in the end I don't think it matters, gapps.zip just ENABLES Google Market/Play on CyanogenMod ROMs, so any latest updates will be downloaded afterwards anyway.
 
Hey whyzor, great rom! I did want to mention though that I've been having issues with the capacitive buttons' backlights. They're quite dim and they flicker, which is especially noticable as you move the phone. I've installed your rom on about 3 different triumphs now (dealing with amazon to get one that isn't broken), and they all do the same thing. Any tips on how I could fix that via settings or modifying a file, if anything?
 
tacticblue said:
Can someone comment on the difference in speed between this ROM and the stock ROM. Has anyone clocked it for comparison sake? Just curious!
Click to expand...

You can check out these threads. TG's or pwnyourace I'm sure there are others that have mentioned it. I'll try to do a test run on my wife's phone, she's still stock.
Edit: I found a video of an unmodified Triumph. They claim scores between 1600 and 1800
 
Semperverus said:
Hey whyzor, great rom! I did want to mention though that I've been having issues with the capacitive buttons' backlights. They're quite dim and they flicker, which is especially noticable as you move the phone. I've installed your rom on about 3 different triumphs now (dealing with amazon to get one that isn't broken), and they all do the same thing. Any tips on how I could fix that via settings or modifying a file, if anything?
Click to expand...

Mine doesn't flicker noticeably, but the settings are
"from your home page" Settings--> CyanogenMod settings--> Display--> Automatic backlight-->
and look at the various settings in there. I'm sure one like the "Decrease hysteresis" is what you're looking for.
 
Anyone else having a problem with Hanging With Friends crashing the phone and rebooting whenever you attempt to start/continue a game on the latest ROM? Tried a fresh install and it still crashes the phone.....or on the rare chance that the game doesn't force a reboot, all of the games animations are choppy and laggy.
 
tacticblue said:
Can someone comment on the difference in speed between this ROM and the stock ROM. Has anyone clocked it for comparison sake? Just curious!
Click to expand...

It's faster, in overall user input smoothness and some benchmarks, plus it has updated GPU drivers.

Semperverus said:
Hey whyzor, great rom! I did want to mention though that I've been having issues with the capacitive buttons' backlights. They're quite dim and they flicker, which is especially noticable as you move the phone. I've installed your rom on about 3 different triumphs now (dealing with amazon to get one that isn't broken), and they all do the same thing. Any tips on how I could fix that via settings or modifying a file, if anything?
Click to expand...

In Settings - CM Settings - Display - Automatic Backlight - Edit Other levels, Set the Buttons column values to something high. I actually set it to zero because the stock values is too bright and shows the light leakage on my phone. The flicker is a fast pulse that simultes reduced brightness and saves battery. The backlight is really only needed in completely dark conditions, in any sort of environment light the capacitive buttons can be seen easily without backlight.
 
As a total aside I wanted to update the "Games that will run"
(perhaps we should make a different thread saying which ones will/won't work? just an idea)
Plants vs. Zombies is working for me now. I don't know why it wouldn't before. Also, World of Goo has worked for a while, I just got it the other day though (It was on sale! WOO!)
 
You must log in or register to reply here.
Back
Top Bottom