• 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 changed Catlog to record every line to the SD card (I probably should done this from the beginning, as you said). I'm not over- or under-volted. It would be rough to go without Beautiful Widgets or JuiceDefender, although I'll try that if it happens again.

Thanks for taking a look at it.
 
Q: Does anyone else experience the phone's screen not turning off during a call?

Seems the proximity sensor or whatever it is that turns the screen on/off when it detects an object near the screen is disabled or doesn't work.

Edit: NM, seems to be working ok now!
 
The large amount of internal memory is the only thing I would miss from the Triumph if I switched back to Optimus V. I remember always running out of memory on the Optimus although I really loved that phones reliability.
 
Whyzor: I just wanted to thank you for all the great work you've done. Sorry about the tiny size of my donation. :-( It reflects relative poverty not a lack of gratitude.

The Optimus V is without question one of the best phones I've ever used. It's a little confusing to me why I got a Motorola over an LG.
 
I have thanked you many times via the thank button.

Not yet via PayPal O:-)

Thanks again for your work, and your attitude toward the mob that is this phones user base. I hope you leave feeling proud of your contributions. We will miss you.
 
Posting just to join in with the others saying thanks. I think I would've ditched this phone quite a while ago if it weren't for you, Whyzor. Hope to see you on the forums for future VM phones.
 
Thanks again for your work, and your attitude toward the mob that is this phones user base. I hope you leave feeling proud of your contributions. We will miss you.

Thanks everyone, I'm glad to have helped improve a lot of people's Triumphs (2800+ downloads of the 03-04 build as of today). Now if only VM would acknowledge it too by sending me their latest HTC One V, I don't care if it's a prototype, I'd jump in and help test it :D

The large amount of internal memory is the only thing I would miss from the Triumph if I switched back to Optimus V. I remember always running out of memory on the Optimus although I really loved that phones reliability.

Some have reported no problems using Link2SD (not to be confused with others with similar name). I've never needed to use it myself, yet.
 
I appreciate all the support. Another factor is the time and effort, since I have a full-time job as a software engineer, I don't want to spend my free time doing the same, life is too short to be in front of a screen all the time :) This was originally only supposed to be a small project for the holidays.
size

At first I was sad to see you are leaving. Knowing that you feel that life is too short to continue with TG-R is totally understandable (and makes it less sad), and I hope you do many fulfilling things in your new-found time! Thanks for everything! Your ROM for me personally, has made it my most modded phone and one of my favorite phones despite its flaws.

Oh, for the record, the real reason why Whyzor is leaving...

DIABLO 3
 
Some have reported no problems using Link2SD (not to be confused with others with similar name). I've never needed to use it myself, yet.
I use that on my wife's OV and it usually works fine, but now and then it causes stupid issues. I would recommend it for that phone. When she couldn't get texts because she had like 8 apps on her phone, that was ridiculous.
 
Is there a reason that you get the "phone storage space is getting low" message when there's like 90 MB of free space left? Any way to get around this?
 
Is there a reason that you get the "phone storage space is getting low" message when there's like 90 MB of free space left? Any way to get around this?

You may want to move some of your Apps to the SD card to free up some space.
 
Is there a reason that you get the "phone storage space is getting low" message when there's like 90 MB of free space left? Any way to get around this?

I know at least in Windows, it's not good to have less than 10/15% free space because it might interfere with paging and file operations. I don't know if the same applies to linux/android file systems.
 
So after some looking around, apparently Android/Linux, like Windows, requires ~10% free space. Not sure if its the same reason as in Windows, so maybe one of the Linux gurus can chime in. If I at least know why, then I'll feel better :p

I really prefer to not keep apps on the SD card. It loads slower than internal memory, and I've found that it mor easily becomes corrupted. Just last night I did a nandroid backup so I could try out cm9. Restored my backup and all the apps on the SD card had become corrupted and no longer showed up on the system. That's a few times now where I've had issues like that. Say what you want about iPhones, but there's dry good reasons they don't use SD cards.
 
So after some looking around, apparently Android/Linux, like Windows, requires ~10% free space. Not sure if its the same reason as in Windows, so maybe one of the Linux gurus can chime in. If I at least know why, then I'll feel better :p

I really prefer to not keep apps on the SD card. It loads slower than internal memory, and I've found that it mor easily becomes corrupted. Just last night I did a nandroid backup so I could try out cm9. Restored my backup and all the apps on the SD card had become corrupted and no longer showed up on the system. That's a few times now where I've had issues like that. Say what you want about iPhones, but there's dry good reasons they don't use SD cards.

When ever I do a nandroid backup I do two after clearing the caches. I have had issues in reloading my backup and after doing it again, the backup would load perfectly.
 
So, using this rom I've got a freezing issue with a couple games:

Zenonia 4: Game occasionally hangs, audio still plays fine in the background while a frozen frame is displayed on screen. Basically just seems to 'pause' the game while it's frozen (I don't die because it froze).

Osmos HD: Very similar to the above, except in Osmos, the screen kinda flips between two frames as it's frozen.

Anyone know of any fixes and/or what I could do to try to minimize the issue?

Edit: I've installed 03-04 from scratch, wiped data/system/cache and dalvik cache before install. Still freeze in Osmos, probably Zenonia too.
 
So, using this rom I've got a freezing issue with a couple games:

Zenonia 4: Game occasionally hangs, audio still plays fine in the background while a frozen frame is displayed on screen. Basically just seems to 'pause' the game while it's frozen (I don't die because it froze).

Osmos HD: Very similar to the above, except in Osmos, the screen kinda flips between two frames as it's frozen.

Anyone know of any fixes and/or what I could do to try to minimize the issue?

First, as with any issue like this, I'd do a nondroid backup (a couple) then switch to my FroyYo backup to see if it's related to the ROM. That way I could eliminate at least that much. Though it seems like it may be a "call" in the game, or maybe not enough buffer?
 
First, as with any issue like this, I'd do a nondroid backup (a couple) then switch to my FroyYo backup to see if it's related to the ROM. That way I could eliminate at least that much. Though it seems like it may be a "call" in the game, or maybe not enough buffer?

Yeah, I've switched back to stock and don't seem to have the freezing issues.. but don't want to go back to stock :(
 
I've occasionally played Osmos HD on the 03-04 build without problems. Make sure it's installed in internal memory, otherwise check the usual suspects, apps/services running in the background, try different performance and OS settings combinations. I run very minimal fancy animations and apps on my phone.
 
Since spring has come, I've noticed my previous custom automatic screen brightness has been too dark outside when it's sunny, so I came up with a few more brightness "profiles" so it's not afraid to run quite a bit brighter outside. The old one I posted is now "lowpower" and isn't the best if you plan to use your phone outside if it's very sunny.

data.png


Untitled.png
 
How would one put in these brightness adjustments? I have to use my phone outdoors often for work and it is impossible to see most days.
 
I've decided to sell my Triumph and go back to the trusty old Optimus V until the next VM phone worth buying comes out (The HTC one V looks promising if the rumors are true). The MT's unreliable touchscreen gets on my nerve every time I use it and I can't stand it any longer.

I'll make a final build & test it on the phone before I part with it. It's been quite a learning experience for me the past few months, I'll stick with VM's $25/mo plan since nothing else can beat it for my type of usage. So maybe you'll see me on another VM phone forum.

BTW If anyone wants to buy my Triumph w/ everything that came in original box + an extra 1600 mAh battery (mint condition) + a soft & hard case, PM me. Looking to sell for $180 or more, first/highest offer will be accepted. Otherwise it'll go on ebay tonight. I'll update this post if it's been spoken for.

I don't blame you. The action buttons' random failure to respond has been the single most annoying issue to me, CM7 issues included. So I take it there's no possibility of software helping the touch screen issue it's a 100% hardware issue? Maybe I was spoiled by the HTC Evo.

Eta
That being said, this phone is by far my favorite pre-paid as of yet thanks to your tremendous efforts with this ROM. I'm also a full time developer so I totally understand getting burned out with another project in your "free" time!
 
The proximity fix in 02-29 kernel never fixed it for me. The proximity sensor during calls not working drives me absolutely insane.

Thanks to mantera's new froyo kernel I discovered that the problem existed somewhere in Whyzor's changes so I flashed TG Reloaded 1-26 which has working proximity and flashed each successive kernel until I found the culprit. The kernel from 02-02 was the last one that worked right (proximity sensor). 02-08 seems to be the culprit. The changelog says "Removed some BKLs in input processing."

I tried flashing the 02-02 kernel with the 03-04 rom, but it just boots to a black screen. Whyzor, is there anyway you could revert the changes in 02-08 that broke proximity but keep the rest of the modifications so it works in the new rom?

UPDATE: mantera figured out the commit that broke it:
I added a test 1.7.20.zip file to the OP. This reverts the commit that tries to prevent 2 sensors from grabbing wakelocks. It looks like it's possible that when only one sensor is active, it may not be able to grab a wakelock.
I tested it and it works on the latest TG Reloaded. It takes a little longer for the screen to turn back on than in stock, but at least it's coming back on!
 
I've noticed proximity sensor flickering when during a call, but only once and it was in a dark room and the sensor was facing a light area, so maybe that's toggling it. The other occasional problem is if the other side disconnects a call first, the screen & all buttons won't respond for a few seoncds. Both of these are rare though, and work most of the time.

For the previous commits, all of the BKL commits were already reverted in a later build. The deep sleep problem with 2 sensors active fix is still in there so the phone can deep sleep properly.
 
My issue is (before mantera's update) that the screen doesn't come back on at all during a call. Like when I call a service number and have to press a number, I always have to push the power button to see the screen.

Are you saying the commit that mantera reverted messes up deep sleep? Or are you saying you've already done what mantera said he did?
 
Back
Top Bottom