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

Dunno if this has ever been brought up but i was wondering if it was possible to make the screen brighter? Even with the screen brightness all the way up its still hardly readable in the sunlight while driving down the road. My wife has a Motorola Droid Bionic and hers is a lot brighter. I know that her phone is a more expensive phone and has better hardware but i was just wondering if it was possible to say change something in the kernel or source to be able to allow u to brighten the screen up more.
 
jbarbourx said:
Dunno if this has ever been brought up but i was wondering if it was possible to make the screen brighter? Even with the screen brightness all the way up its still hardly readable in the sunlight while driving down the road. My wife has a Motorola Droid Bionic and hers is a lot brighter. I know that her phone is a more expensive phone and has better hardware but i was just wondering if it was possible to say change something in the kernel or source to be able to allow u to brighten the screen up more.
Click to expand...

Not likely, the LCD screen is a hardware limitation. Try taking off the thick built-in screen protector if not already, it will let a bit more light through, the Gorilla Glass doesn't need it anyway.
 
Oh aight thnx. I kinda figured it was a hardware thing but beings that u can adjust most everything else like overclocking and over/undervolting i figured there might be a way. I dont use any screen protector or anything but i guess i can live with it. Just something ive been wanting to ask about.
 
viskon said:
It is my first experience of Sleep of Death on my phone since I first switched to CM7.

Had an SOD on the 02/02 build as well. Wiped data, flashed the 02/18 build,set up the phone and keeping my fingers crossed.
Click to expand...


I too have been plagued with Sleep Of Death problems for a while through several revisions of Reloaded Rom. since i have not seen discussion about it here i thought it was something unique to me and had been pulling my hair out trying to figure out the cause.

NOTE: SOD is NOT about screen going blank after a call. It is when the phone refuses to wake up from sleep. i.e. unable to turn the phone back on via power button, requiring a battery pull.

there's no outward sign that anything was wrong. the notification light could still be blinking if there was message waiting. i won't find out that it's dead until i try to turn the phone back on. it has caused me to miss unknown number of calls... i also noticed that when the phone is in the SOD state it will not charge and the indicator light will not come on solid as normal when power is plugged in.

SOD seems to be completly random and seems more likely to happen after phone calls. (although i am not 100% sure about that point.)

if i remember correctly in the early days of CM7 we had similar problems with SOD when wifi is set to turn off when screen goes off. it was resolved by Tickerguy later on. i wonder if it could be the same bug creeping back in due to some of the optimization done in Reloaded Roms.

It might also explain why the problem is not wide spread and reported, as not everyone uses WIFI extensively. (i myself uses JuiceDefender to turn off/on wifi automatically and travel between several different WIFI access points during the day.)

i hope this brings some attention to this apparently rare but crippling bug...


also, as it hasn't been said enough: Thank you Whyzor for your amazing work!
 
jbarbourx said:
Oh aight thnx. I kinda figured it was a hardware thing but beings that u can adjust most everything else like overclocking and over/undervolting i figured there might be a way. I dont use any screen protector or anything but i guess i can live with it. Just something ive been wanting to ask about.
Click to expand...
Whyzor was referring to the screen protector that comes on your phone from the factory. You may not even realize it's there, but it is, and it doesn't have a lot of fans around here. Most people find that the display looks better and the touchscreen is more responsive without it.

Here's a thread to help you if you are interested in removing it: http://androidforums.com/motorola-triumph/385289-best-way-remove-factory-screen-shield.html
 
Hopefully, this isn't too far off-topic as the issue's been settled already, but - with any phone, Murphy's Law applies.

Sometimes a hardware component like a sensor will fail all on its own, having nothing to do with a rom update (but because of the coincidence in time, it's easy to think that the rom was the cause).

An easy way to check state of health of your phone sensors is with Elixir, free in the Market.

Cheers and many thanks for your thread bandwidth for the side-topic, just hoping this is helpful info in general.
 
I have never had SOD on CM7, I also have never used Juice Defender. Tickerguy's code to keep a wakelock when wifi is turned on is still in there, which I believe is to prevent the SOD.

Juice Defender may be messing with things in its own way of "enabling" or "disabling" the wifi, which is different than the manual way. Try uninstall juice defender and manually toggling wifi (w/ power notification bar) for a week or so and if the SOD is still there, reinstall it, at least ruling out JD. Also the fact the notification LED is blinking means the phone is active and kernel still running. So the "death" part likely is from an attempt to wake it up from that state (which also points to Juice Defender trying to do whatever it does).

One last thing, don't overclock or undervolt since that can add to random problems.
 
This issue has happened to me 4 times since I flashed my MT with the latest build for CM7 TG-Reloaded (Latest: 02-18). So I flashed my MT with Reloaded 2/2/12 Release which I never had any issues.


bombaw8 said:
I too have been plagued with Sleep Of Death problems for a while through several revisions of Reloaded Rom. since i have not seen discussion about it here i thought it was something unique to me and had been pulling my hair out trying to figure out the cause.

NOTE: SOD is NOT about screen going blank after a call. It is when the phone refuses to wake up from sleep. i.e. unable to turn the phone back on via power button, requiring a battery pull.

there's no outward sign that anything was wrong. the notification light could still be blinking if there was message waiting. i won't find out that it's dead until i try to turn the phone back on. it has caused me to miss unknown number of calls... i also noticed that when the phone is in the SOD state it will not charge and the indicator light will not come on solid as normal when power is plugged in.

SOD seems to be completly random and seems more likely to happen after phone calls. (although i am not 100% sure about that point.)

if i remember correctly in the early days of CM7 we had similar problems with SOD when wifi is set to turn off when screen goes off. it was resolved by Tickerguy later on. i wonder if it could be the same bug creeping back in due to some of the optimization done in Reloaded Roms.

It might also explain why the problem is not wide spread and reported, as not everyone uses WIFI extensively. (i myself uses JuiceDefender to turn off/on wifi automatically and travel between several different WIFI access points during the day.)

i hope this brings some attention to this apparently rare but crippling bug...


also, as it hasn't been said enough: Thank you Whyzor for your amazing work!
Click to expand...
 
Anyone else tested wifi hotspot?
I tried again on computer it seems the AP disappears as soon as the connection is established...
Right now I don't have cell signal but the connection to wifi hotspot seems very stable..... Gonna do more test tmr.
Is there a way to change channel for wifi hotspot? Does it automatically detect the best available channel?
 
Gdibig said:
Mine works, but there is a short (1 - 2 sec) delay as someone reported above.

Thanks Whyzor for all of your work on this ROM!:):):)"http://androidforums.com/members/whyzor.html"
Click to expand...

I have observed strange behavior from what I think is the proximity sensor.

I am left handed, and set something in the settings that related to the fact my phone's bottom left corner is down while talking (assuming right handers bottom right would be down).
I frequently get a lot of vibe alerts about 45 seconds into calls (I have that setting off). I do not know how many, but it keeps vibrating until I pull the phone from my face. At all times the phone works, but it is hard to ignore when it is your phone, and it can be herd on the other person's phone too. I would think the 45 second setting would be just one vibration, I guess I will try it? I have had longer calls where it occurred again.

Sometimes at the end of a call, the phone stays dark when removed from my face. Normally I can get it back by hitting the power button. I did have to disable the power causes hangup option that I started with.

Not sure if this helps anyone define their problem better, but it is what I have noticed.
 
I was on the latest build, but went back to the 1/28 build. Things just seemed smoother on that one. I did re flash the older kernal on the new build, but it still seemed clunkier for some reason. Of course it could just be me. I really love the phone with this rom :D
 
I just turned ON the 45 second vibrate feature and it now just vibrates ONE TIME. I may never turn that OFF again! It is going to be nice to not have to work around the vibration period.

If anyone else has experienced this you know how much nicer just one vibration is.
 
I just flashed this, kudos. It's awesome. A problem I'm having though, is that Facebook, GMail, and other social networking style apps keep crashing on me. Anyone know what could be doing that?
 
ziggy46 said:
How do we set the screen to dim before it goes completely off?
Click to expand...
Yes, I asked that a couple days ago, and would love to get that working again.

It's annoying that the screen shuts off without warning, and I keep having to reach for the power button to turn the screen back on, instead of just tapping the screen when I see it dim, when I am trying to read these forums and such.

It's interesting how you don't realize how important some features are until they stop working.
 
I had a problem today with my browser not rotating today.
I can set the "view in landscape". I checked my acceleratormeters with "phone tester" (it's in the market). They work.
Diagnosticly I don't know how to narrow it down.

P.S. a reboot fixes it. But the geek in me likes to have long up-times
88 hours before the reboot.

And thank you Whyzor, TickerGuy, and Iaasic(wrong spelling?). Without you, we wouldn't have such an awsome ROM.
 
xcoma said:
I just flashed this, kudos. It's awesome. A problem I'm having though, is that Facebook, GMail, and other social networking style apps keep crashing on me. Anyone know what could be doing that?
Click to expand...

I don't have those problems, sounds like they're app issues. Try going into settings - applications and wiping each app's cache, or boot into recovery and rewiping cache & dalvik-cache (it never hurts). Or try a fresh install if none of these work.

ecarlson said:
Yes, I asked that a couple days ago, and would love to get that working again.

It's annoying that the screen shuts off without warning, and I keep having to reach for the power button to turn the screen back on, instead of just tapping the screen when I see it dim, when I am trying to read these forums and such.

It's interesting how you don't realize how important some features are until they stop working.
Click to expand...

I just increase the time for screen to auto sleep to 2 minutes. Most of the time I turn it off manually with the power button anyway. The autodim may have something to do with auto-backlight settings some of you changed with the latest settings aricblunk posted.

dsmryder said:
I had a problem today with my browser not rotating today.
I can set the "view in landscape". I checked my acceleratormeters with "phone tester" (it's in the market). They work.
Diagnosticly I don't know how to narrow it down.

P.S. a reboot fixes it. But the geek in me likes to have long up-times
88 hours before the reboot.
Click to expand...

Sounds like an app problem. The kernel is responsible for the hardware interaction which you confirmed is working, to narrow a ROM problem, multiple apps would have to have the same problem. If it's just one app with the problem, then it's the app's fault (probably its cache or settings got corrupted, so try wiping those again).
 
Well love this work never had a Roman this good before and I thought you might want to know that if I try to run a standard quadrant score at 2 ghz it locks up and bad to pull the battery no biggie no one runs it like that any way also I've Been using wifi tether by lemons and buxton its super stable but that's nothing cause its an easy work around
Any way great job
edit.
It seems to be the quadrant standard apk.
 
Whyzor said:
The autodim may have something to do with auto-backlight settings some of you changed with the latest settings aricblunk posted.
Click to expand...

I've got my backlight set to 30%, just like I did on Stock, and the auto-dim isn't working (it did on stock). I temporarily tried turning Auto-backlight on, with the default settings, and even played with other settings, before setting them back, and that didn't fix the auto-dim.
 
ziggy46 said:
How do we set the screen to dim before it goes completely off?
Click to expand...
If you want the screen to dim automatically, go into the custom auto backlight settings and set the dim level to 20 or 16 or whatever you like. I'll go back and add that to my post, I probably should've thought about that earlier.

Edit; here's the update: (later edit: apparently this still doesn't enable dimming and was based on my own intuition which turned out incorrect, I'm not sure how to enable dimming with custom auto backlight.)

If you want the screen to dim automatically, go into the custom auto backlight settings and set the dim level to 20 or 16 or whatever you like, something lower than the 26 minimum when you're in a low-light environment too dim for the sensor to read as any darker. That way you have a warning before the screen goes blank. I just personally prefer not having it dim because I don't usually stare at the screen for more than a minute. You could also just go to Settings > Display > Screen timeout and set that to 2 or 5 minutes instead, so you never have to tap the screen to keep it awake.
Click to expand...
 
Hey,

First, thanks Whyzor for all the work. Love this ROM.

Second, on that camera bug with the EXIF data, is that for any app that uses the camera writes the date wrong or just the default camera app?

Thanks.
 
Anyone else having problems with Google Listen podcast app?

I was trying to download my podcasts over wifi and it kept timing out. Specifically, I was trying to download Science Friday and Car Talk, each about 20 MB. It would download anywhere from 3 to 15 MB before freezing up the wifi. I would not be able to access the internet or anything for a little while although the wifi indicator on the phone never turned off. In less than a minute, connectivity would be restored, but I would need to restart my podcast download from the beginning. I tried several times and even tried going back to the 02-02 build. Eventually turned off wifi and was able to download over 3G.

I tried to download some other random 20MB file over wifi and had no problems with that.
 
You must log in or register to reply here.
Back
Top Bottom