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

Mantera's revert likely will cause the phone to not deep sleep sometimes (that's what the purpose of that fix was for). And I don't experience the problem you're describing using the 03-04 ROM & included kernel with the proximity sensor not waking up the phone, I don't believe there is widespread problem with the proximity sensor. It's something specific on your phone.
 
I'm having the same trouble with the screen going (and staying) black during a call. The only way to turn it back on is to press the power button.

A suggestion was made that it could be a hardware problem/phone specific issue; I'm not sure. I've used a rooted stock and froyocream sandwich ROMs and the issue does not exist. I can say that the issue did not exist in earlier TG-reloaded builds either.

Now that I've said all that...thanks for all your work Whyzor! I'm a new (2 month) owner of a MT and your ROM is the only reason I didn't return the phone to bestbuy and go with a different carrier.

My report is only for debugging/improvement purposes. I don't have the knowledge to do what you do. Thanks again.
 
Mantera's revert likely will cause the phone to not deep sleep sometimes (that's what the purpose of that fix was for). And I don't experience the problem you're describing using the 03-04 ROM & included kernel with the proximity sensor not waking up the phone, I don't believe there is widespread problem with the proximity sensor. It's something specific on your phone.

Yeah, I actually ran into it the other day when I was running cm7 for the day to test out theOC. I thought it was odd that I had to hit the power button to wake phone back up after a call but I didn't think twice about it. However, I can see how that could get bothersome if you use the phone as a phone a lot (which I don't).
 
Can anyone else confirm this proximity problem on the 03-04 build? There were a few builds that this happened on before, even on my phone, but the most recent build should be fine.
 
...I can see how that could get bothersome if you use the phone as a phone a lot (which I don't).

Yes, I'm on the $45/mo because it's really hard for me to not use over 300 minutes. But I have a feeling you're in the majority. Everyone else I know is on the grandfathered $25/mo plan b/c they don't talk hardly ever.
 
Thanks for all the work you have put into this phone Whyzor.

Just as confirmation, I too have had the proximity sensor issue with the last few releases where during a call the only way to wake up the screen is with the power button. It isn't hardware because it was not a problem a few reloaded releases ago and when I flash FroyoCream it is resolved. None of the settings change this (i.e. always use proximity sensor, etc.).

Again, thanks for all of your development on this phone.

Edit: I should add that I have done a clean install (wipe data/factory reset) of this 03-04 ROM and still have the problem
 
Can anyone else confirm this proximity problem on the 03-04 build? There were a few builds that this happened on before, even on my phone, but the most recent build should be fine.

I also have issues with the proximity sensor. I tried the usual fixes like factory reset/fresh install with no apps but the problem still existed. I didn't bother mentioning it though because this ROM is amazing and I didn't want to seem bothersome. lol
 
I also have issues with the proximity sensor. I tried the usual fixes like factory reset/fresh install with no apps but the problem still existed. I didn't bother mentioning it though because this ROM is amazing and I didn't want to seem bothersome. lol

Same here

Update: just flashed mantera's latest OCkernal v1.7.20 and the problem is gone
 
I do notice this on my Triumph but isn't really a an issue except for when I'm dealing with an automated machine where I am required to push 1, 2, 3, etc, and have to push the power/lock button to turn the screen on. I also notice that the lock sound plays shortly after I put the phone up to my ear, telling me that the screen is locked.
 
I do notice this on my Triumph but isn't really a an issue except for when I'm dealing with an automated machine where I am required to push 1, 2, 3, etc, and have to push the power/lock button to turn the screen on. I also notice that the lock sound plays shortly after I put the phone up to my ear, telling me that the screen is locked.

Hmm, that locking sound is an interesting clue. What if you try different values in Settings - CM settings - interface - lockscreen - delay & timeout values?
 
Hmm, that locking sound is an interesting clue. What if you try different values in Settings - CM settings - interface - lockscreen - delay & timeout values?

I've tinkered with these settings while the OV was my primary phone. Just deals with the regular lockscreen and nothing else.
 
I've been on the 03-04 build since it was released and the proximity sensor has never worked. I don't call a lot, but it does get annoying.

Mantera's TheOCv1.7.20 will fix the issue. Take note that Whyzor believes it might keep the phone from deep-sleeping. I haven't been running the kernel long enough to tell whether it's effecting battery life or not.
 
Anyone know a way I could troubleshoot the mic on my headphones? Skullcandy 50/50s and the mic doesn't seem to work. I know the inline control does because I can use the button for play/pause, skip, etc.
 
I do notice this on my Triumph but isn't really a an issue except for when I'm dealing with an automated machine where I am required to push 1, 2, 3, etc, and have to push the power/lock button to turn the screen on. I also notice that the lock sound plays shortly after I put the phone up to my ear, telling me that the screen is locked.

I can also confirm that it is necessary to press the power button to wake the screen during and after a call. As mentioned I also hear the lock screen sound after I put the phone up to my ear.
 
Mantera's TheOCv1.7.20 will fix the issue. Take note that Whyzor believes it might keep the phone from deep-sleeping. I haven't been running the kernel long enough to tell whether it's effecting battery life or not.


Reflashed everything and added TheOC, it went right to deep sleep, I'll report back when I make a call if proximity works.
 
Mantera's TheOCv1.7.20 will fix the issue. Take note that Whyzor believes it might keep the phone from deep-sleeping. I haven't been running the kernel long enough to tell whether it's effecting battery life or not.

If I remember correctly, you have to toggle on and off the wifi and use cpu spy to see if it goes into deep sleep mode again after turning screen off.
 
Anyone else having issue downloading apps from google play from your computer to your phone. Google play force closes when I download something from my computer to my phone.
 
Can anyone else confirm this proximity problem on the 03-04 build? There were a few builds that this happened on before, even on my phone, but the most recent build should be fine.


Yeah I have the proximity problem on 03-04 build and the last 2 builds before. The screens flickers most phone calls and always have to hit power button after call to get screen back.

side note: I am getting the best battery life ever on the 03-04 build. Thanks for all your work Whyzor!
 
I had that problem last night (right after I flashed TheOC Kernel but correlation is not causation!) but it cleared after a bit; I get the feeling it was a distant end problem.


re: deep sleep.
CPU Spy is just what I was looking for (but couldn't find); thanks for mentioning it. Mine wont go into deep sleep with either WiFi or BT on; is there something else I need to configure properly or is that just the way it is?
 
I flashed mantera's OC kernel to try and fix the incall black screen. it worked for about 2 hours then had the black screen problem again
 

re: deep sleep.
CPU Spy is just what I was looking for (but couldn't find); thanks for mentioning it. Mine wont go into deep sleep with either WiFi or BT on; is there something else I need to configure properly or is that just the way it is?
Yes, that's just the way it is. Something to so with the workaround Tickerguy used to get wifi to work properly, if I remember correctly.
 
Back
Top Bottom