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

[Whyzor]

I'm on the 1/26 build and lately I have encountered a weird bug. During a call when someone hangs up on me, my phone will freeze and not respond to the wake button for about ten seconds. Also, I have calibrated my battery but the phone always dies when it hits about ten percent. I searched threads but couldn't find an answer. Ideas? Thanks again for all you do!

There's a bug where the proximity sensor turns off the screen when in phone call, and when the other end disconnects, it comes out of phone call mode, but the proximity sensor is never turned back on. So a workaround for now is to either pull the phone away from your head when you know the call is about to end, turn off the prox sensor, or just wait the time needed for phone to be active again. Could try the "Call Settings - Always use Proximity sensor".

I was also wondering if there is a possibility of increasing the MMS size in the default messaging app? I prefer it over a 3rd party one, but size cap may be due to VM limitations? If not will this mod work? [HOW-TO] [TEAM XPOSED] How to set your own customized MMS messaging size options - xda-developers Sorry for n00b questions and happy Super Bowl to everyone who celebrates it!

I'm not going to do any mods that messes with the VM network defaults. For large data, you shouldn't be using MMS anyway, use email or a number of other apps. Also increasing the size on your end doesn't mean the recipient will be able to handle the larger size (just like email attachments).

 

[Just Infectiou]

After a few minutes of testing the always use proximity seems to have solved the problem. Thanks!

 

[robali911]

Hey guys, I am curious, if I run my CPU at 61 Low & 1024 Max is there any chance of phone damage from going so low (61)? Reason I am asking is because I use my BT all day long and CPU Spy shows I am getting most of my time at the stock 245 which is normal. I am thinking that if I set my low to 61 the interactive gov will go up and down as needed. I want to do this for bat life while using BT. I am not a big fan of overclocking but I do like the idea of underclocking to save bat life. Is there any possible way I can damage my CPU by underclocking to 61 on interactive gov with my max set to the stock 1024? I don't mean to sound paranoid but now that I have this new ROM I am loving my phone and don't want to take any chances on CPU or phone damage just to save some bat life. Any feedback would be appriciated. I am almost sure that underclock is safe but I just wanted to get a for sure answer. I know the risks of overlcocking but am not sure if there is any with underlocking. Thank you in advance,
Rob....

 

[wigginst]

Any thoughts as to why my Bluetooth kicks my wifi off line when I turn it on? I thought this had been fixed so both could work now (and it did for me briefly). Have reflashed but seems to still be one or the other right now.

 

[robali911]

Any thoughts as to why my Bluetooth kicks my wifi off line when I turn it on? I thought this had been fixed so both could work now (and it did for me briefly). Have reflashed but seems to still be one or the other right now.

I had the same problem and a few others. What I did was pull the bat, wait about 5 minutes then boot into recovery. I then did a full wipe, I mean wipe everything but the SDCard. After I flashed the ROM and Gaps I rebooted the phone I let it sit for about 5 minutes. I then powered off the phone for a couple minutes then powered back on and setup everything and all worked perfect. It seems that sometimes the phone keeps stuff in memory even when you shut it which prevents a clean flash. I noticed that by pulling the bat and waiting the given times it fixed all of my problems, I hope this helps...

 

[Whyzor]

Hey guys, I am curious, if I run my CPU at 61 Low & 1024 Max is there any chance of phone damage from going so low (61)? Reason I am asking is because I use my BT all day long and CPU Spy shows I am getting most of my time at the stock 245 which is normal. I am thinking that if I set my low to 61 the interactive gov will go up and down as needed. I want to do this for bat life while using BT. I am not a big fan of overclocking but I do like the idea of underclocking to save bat life. Is there any possible way I can damage my CPU by underclocking to 61 on interactive gov with my max set to the stock 1024? I don't mean to sound paranoid but now that I have this new ROM I am loving my phone and don't want to take any chances on CPU or phone damage just to save some bat life. Any feedback would be appriciated. I am almost sure that underclock is safe but I just wanted to get a for sure answer. I know the risks of overlcocking but am not sure if there is any with underlocking. Thank you in advance,
Rob....

Underclocking is absolutely safe. Hardware damage comes from overheating, overvolting can cause things to overheat, and even using a lot of components together can too, like max CPU + GPU + GPS + BT + Wifi + audio + haptic motors could get toasty. Underclocking & undervolting just makes sure the CPU part is minimized. Using interactive govenor should make the min freq even less noticeable in terms of usage since it ramps up so quickly when there's demand. I use & recommend 61-1024 interactive and it's very smooth.

 

[robali911]

Underclocking is absolutely safe. Hardware damage comes from overheating, overvolting can cause things to overheat, and even using a lot of components together can too, like max CPU + GPU + GPS + BT + Wifi + audio + haptic motors could get toasty. Underclocking & undervolting just makes sure the CPU part is minimized. Using interactive govenor should make the min freq even less noticeable in terms of usage since it ramps up so quickly when there's demand. I use & recommend 61-1024 interactive and it's very smooth.

That is the best news I have heard all day. When I get some of my bills paid off you are going to get some money for all the great work on this ROM. You would not believe how many times I have switched from my Triumph to HTC and then back again when I was on stock ROM. I think it is way cool you are fixing the important stuff like BT and so many other things that none of the other ROMs seem to care about. Anyway, keep up the great work and thank you for explaining that to me. I am going to use those settings right now & BTW, the ROM is working perfectly in every area, thank you so much

 

[agentc13]

Hey guys, I am curious, if I run my CPU at 61 Low & 1024 Max is there any chance of phone damage from going so low (61)? Reason I am asking is because I use my BT all day long and CPU Spy shows I am getting most of my time at the stock 245 which is normal. I am thinking that if I set my low to 61 the interactive gov will go up and down as needed. I want to do this for bat life while using BT. I am not a big fan of overclocking but I do like the idea of underclocking to save bat life. Is there any possible way I can damage my CPU by underclocking to 61 on interactive gov with my max set to the stock 1024? I don't mean to sound paranoid but now that I have this new ROM I am loving my phone and don't want to take any chances on CPU or phone damage just to save some bat life. Any feedback would be appriciated. I am almost sure that underclock is safe but I just wanted to get a for sure answer. I know the risks of overlcocking but am not sure if there is any with underlocking. Thank you in advance,
Rob....

Undervolting will not harm the CPU but could do grievous harm to your data on the SD card and/or in the NV if the CPU misses a timing window.

You're just reducing the margin between "operates fine" and "oops - missed a timing window."

Note that if you crash while overclocked, undervolted or both you must presume that some random number of I/O cycles took place in which data was not correctly written prior to the CPU resetting.

Since most of what's going on in a phone is reading (e.g. read a contact entry to make a phone call, etc) rather than writing the odds of you getting hosed in a way that really hurts is pretty low, but it's definitely not zero.

The power savings from undervolting are real but not particularly large; you're trading operating margin for amp/hours on battery draw.

There are some dangers, but it is not very common. I would agree that it is safe as far as hardware is concerned, but the danger is not to your hardware, but rather to your data.

 

[robali911]

There are some dangers, but it is not very common. I would agree that it is safe as far as hardware is concerned, but the danger is not to your hardware, but rather to your data.

Thanks for the input. I never changed any of the Svel settings, I only changed my min-max to 61-1024 Interactive Gov. I am afraid to mess with the Svel settings; for me if it can go wrong it will LOL. BTW, when you take a pic does your focus square turn Green or does it stay Red? I can see it come into focus but the square never turns Green it turns Red then takes the pic. I was just wondering if this is normal or if it is something I may have done. The pcitures come out fine so it is no big deal, just curious. Anyway, thank you again for the post, it is great to have your questions answered so fast. Take care and thanks again,
Rob...

 

[marc12868]

Thanks for the inupt, I am only doing the UC not the UV, I would be afraid to undervolt the system. Knowing my luck I would be one of those few people who would have data loss. While we are on the subject of things, I just took a pic and noticed the focus square was Red before it clicked. The picture came out focused & I can see that it is in focus but the square does not turn Green, is this normal or do I have a bug?

Its just a bug with cm7. I used to have it on my OV and on my MT. It still focuses just doesn't change color.

 

[robali911]

Its just a bug with cm7. I used to have it on my OV and on my MT. It still focuses just doesn't change color.

Thanks for the info, glad to know it is not just me LOL. Take care and thanks for the fast reply

 

[michambers1994]

I get better coverage with this rom signal wise.

 

[scotters83]

Hi Guys, New to this forum. I tried to search the best I could on this thread, so if I missed any information about this already on here, I apologize.

I'm using the 2-02-12 build. I'm having an issue with Groove IP with this rom that I wasn't having with the VM stock. Before I contact Groove IP I wanted to see if anybody else here happened to have the issue.

Sometimes when I receive a call to my Google Number through Groove IP, I hear it start to ring once, and then it stops. When I look at my phone, my phone is frozen and sometimes requires a reboot, and there usually isn't any missed call listed. I know somebody did call, because it's happened before and I'll immediately get a voice mail on Google Voice if someone leaves one. As well, my wife mentioned when it happened once that the phone rang 4 or 5 times on her end as she was calling me.

Has anybody had this issue and know if it is a rom issue or something I'm not thinking of? Don't want to point fingers at this rom first, as I realize it's a beta and I enjoy it a lot!

Thanks,
Scott

 

[wigginst]

I know the phone freezing coming out of calls was mentioned earlier having something to do with the proximity sensor. I am having the same issue even using the bluetooth so I don't think the proximity sensor even acts. The phone freezes after a call and it is sometimes a couple of minutes before I can make any other calls.

 

[Whyzor]

Sometimes when I receive a call to my Google Number through Groove IP, I hear it start to ring once, and then it stops. When I look at my phone, my phone is frozen and sometimes requires a reboot, and there usually isn't any missed call listed. I know somebody did call, because it's happened before and I'll immediately get a voice mail on Google Voice if someone leaves one. As well, my wife mentioned when it happened once that the phone rang 4 or 5 times on her end as she was calling me.

Sounds like Groove IP is having some trouble starting up. Try going into settings - applications for Groove IP and clear its cache. Also clear cache for Google Voice (if you have that installed), and the phone app.

If that still doesn't work, see if you can reproduce this with a CLEAN ROM install, just install Groove IP and nothing else after factory reset & reflashing this ROM. Titanium restore can corrupt some system files, or it's because of another app that got installed afterwards that is interfering with things. Also Groove IP doesn't work well with VM's network for most people. Using it on Wifi is more reliable.

I know the phone freezing coming out of calls was mentioned earlier having something to do with the proximity sensor. I am having the same issue even using the bluetooth so I don't think the proximity sensor even acts. The phone freezes after a call and it is sometimes a couple of minutes before I can make any other calls.

Add this line to the end of /system/build.prop (must mount /system in rw mode first), & reboot. It should fix the freezing after other end disconnects a call when screen is off. This will be included in the next release.

mot.proximity.delay=150

 

[ziddey]

Hi Guys, New to this forum. I tried to search the best I could on this thread, so if I missed any information about this already on here, I apologize.

I'm using the 2-02-12 build. I'm having an issue with Groove IP with this rom that I wasn't having with the VM stock. Before I contact Groove IP I wanted to see if anybody else here happened to have the issue.

Sometimes when I receive a call to my Google Number through Groove IP, I hear it start to ring once, and then it stops. When I look at my phone, my phone is frozen and sometimes requires a reboot, and there usually isn't any missed call listed. I know somebody did call, because it's happened before and I'll immediately get a voice mail on Google Voice if someone leaves one. As well, my wife mentioned when it happened once that the phone rang 4 or 5 times on her end as she was calling me.

Has anybody had this issue and know if it is a rom issue or something I'm not thinking of? Don't want to point fingers at this rom first, as I realize it's a beta and I enjoy it a lot!

Thanks,
Scott

I'm surprised you're able to use GrooveIP at all. What are your settings?? I've never been able to have an acceptable conversation with it. csipsimple seems to be working okay, but I'm assuming pbxes.org is just working better than before right now. Of course, google talk / skype is absolutely immaculate.

 

[marx2k]

I'm starting to get the issue where every time I unplug the phone for longer than 5 minutes, I have to pull the battery in order to get it to restart. The phone is fully charged. I'm trying to rule out Juice Defender so I'm disabling it for now and will see if it clears anything up.

 

[dsmryder]

I'm starting to get the issue where every time I unplug the phone for longer than 5 minutes, I have to pull the battery in order to get it to restart. The phone is fully charged. I'm trying to rule out Juice Defender so I'm disabling it for now and will see if it clears anything up.

Are you running at a low (61MHz) clock speed? If so, I would kick it up to 245 to see if that can get you into your system to see what is locking it up.

 

[LoneSnark]

I would like to add a known problem to the list, namely the inability to send e-mail via the SMS system, a feature of the stock rom. The CM7 messaging app insists on sending via the MMS system which requires a data connection.

 

[Whyzor]

I would like to add a known problem to the list, namely the inability to send e-mail via the SMS system, a feature of the stock rom. The CM7 messaging app insists on sending via the MMS system which requires a data connection.

SMS is a technology that uses only the cellular data system. It was never meant to send anything large like an email. The stock ROM probably has an app by VM that makes it SEEM like it's using just SMS (like toggling data on & off quickly). Almost all smartphones require data to send & receive MMS & email.

 

[LoneSnark]

I believe you are mistaken. The translation between SMS and the e-mail system is on virgin mobile's backend, not the phone. Hence the SMS restrictions upon the feature (160 character limit). That this is not allowed on other networks might explain why CM7 on the Triumph does not.

 

[scotters83]

Sounds like Groove IP is having some trouble starting up. Try going into settings - applications for Groove IP and clear its cache. Also clear cache for Google Voice (if you have that installed), and the phone app.

If that still doesn't work, see if you can reproduce this with a CLEAN ROM install, just install Groove IP and nothing else after factory reset & reflashing this ROM. Titanium restore can corrupt some system files, or it's because of another app that got installed afterwards that is interfering with things. Also Groove IP doesn't work well with VM's network for most people. Using it on Wifi is more reliable.

Thanks a bunch. I cleared the cache and it seemed to fix the problem so far. Thanks for your hard work on continuing this rom. I know it's probably pretty easy and fun for you, but it is making my move to a prepaid phone totally worth it.

I just use Groove IP on WiFi while I'm at home for a second line without draining my minutes. And whoever asked above, I'm just using the default settings for Groove IP and it seems to work fine! My calls actually seem a bit clearer on this rom too, than on stock. But maybe that's just a coincidence.

 

[Whyzor]

I believe you are mistaken. The translation between SMS and the e-mail system is on virgin mobile's backend, not the phone. Hence the SMS restrictions upon the feature (160 character limit). That this is not allowed on other networks might explain why CM7 on the Triumph does not.

Entirely possible, like the VM activate app that only works on Froyo ROMs. If someone knows what app it is & confirm it to work on a CM7 ROM, I'll gladly include it. BTW I use Google Voice and it forwards SMS, and by using the default SMS app I'm able to reply to a GV-translated number without problems. Maybe you can try a different SMS app. Most email accounts that forward to SMS also don't have special requirements, as long as SMS works.

Thanks a bunch. I cleared the cache and it seemed to fix the problem so far. Thanks for your hard work on continuing this rom. I know it's probably pretty easy and fun for you, but it is making my move to a prepaid phone totally worth it.

Actually it's not as easy as it looks. We devs commit the final working code (most of the time) after a lot of work & testing behind the scenes, so it may seem like trivial changes & stuff. But believe me there's a reason why teams of full-time engineers with good salaries normally work on this kind of stuff. Most of us just happen to have most of the necessary experience to apply it to something like this in our free time.

On a side note, I have the "event" wakelocks fixed in the kernel. Will release it after some more testing.

 

[viskon]

Just had the notification bar freeze on me. Everything else works fine.

 

[redgjm]

The alarm clock flips out sometimes. It goes off like normal but then won't turn off. I have to pull the battery to get it to stop.