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

Whyzor said:
Try adding this line to the end of /system/build.prop:

mot.proximity.delay=150

The problem I'm talking about (I wouldn't call it Sleep of Death), is when the other side disconnects a call first before you pull the phone away, it remains sleeping for up to a minute or two. Pressing the power button or anything doesn't do anything.
Click to expand...

I apologize for not having defined SOD.

The SOD I am referring to is when I put the phone to sleep, either by a brief press of the power button or letting it time out to screen off, and after an hour or so I try to wake the phone by a brief press of the power button but find that the phone is not responsive to any button presses. It "died" in sleep.I then would have to pull the battery to get the phone to restart.

Hope this clarifies.

BTW- No SODs since wiping data and reflashing 02/18 today morning. Running like a dream. Thanks Whyzor!
 
The test kernel 2/19, not only provides the cryptography hooks, but seems to have a lower battery drain rate. (I skipped 2/18, so it might be low drain there to).

I have not used the phone today, but I have not seen a 0.7/hr drain for awhile.

Not sure if it is the wake locks, or something else, but I like the change. Thanks!
 
wigginst said:
Anyone else had camera problems with 2_18 kernel? My camera would not work on that kernel and even caused the phone to reboot. Went back to 08 kernel and the camera is fine.
Click to expand...

I am on 2_28 build, no problem with camera at all.

ps: I did a fresh flash(wipe data/factory reset).
 
Thanks Whyzor. I just played with some settings in "Call settings", the problem seems to be gone now.

forgot exactly which one(s) I changed, could be one or multiples of the following:
"always back to call log"
"keep screen awake"
"always use proximity"

Whyzor said:
Try adding this line to the end of /system/build.prop:

mot.proximity.delay=150

I was going to add that by default, but then noticed it was working properly in the latest build. It could be a timing issue depending on what background apps & services are running on each person's phone. The problem I'm talking about (I wouldn't call it Sleep of Death), is when the other side disconnects a call first before you pull the phone away, it remains sleeping for up to a minute or two. Pressing the power button or anything doesn't do anything. But it does eventually come back (at least for me). I'm not sure how long some of you waited, probably not long enough and just pulled the battery and calling it SOD.

I'll add that line in the next build just to be sure, wasn't sure if it could cause side effects for some people.
Click to expand...
 
Is anyone else having issues where the screen keeps turning off if you're not using it that second? I'm typing this really fast so the screen doesn't shut off, is what I mean. I have logs of it happening if that would be helpful. It's kind of an issue, in that it prevents use really.
 
linsanity said:
I am on 2_28 build, no problem with camera at all.

ps: I did a fresh flash(wipe data/factory reset).
Click to expand...

Factory reset clears both caches, and then some. No need to do wipe cache while doing a reset. I'd only do a reset if I were to change something major. Even then, Ive flashed ICS over on accedent and it worked fine for my days testing.
 
Teklogikal said:
Is anyone else having issues where the screen keeps turning off if you're not using it that second? I'm typing this really fast so the screen doesn't shut off, is what I mean. I have logs of it happening if that would be helpful. It's kind of an issue, in that it prevents use really.
Click to expand...

Sounds like you have an issue with the part of the programming that runs the timer for the screen saver. I would redownload, clear caches and reflash.
 
Ok, nevermind, apparently after I flashed the 2/18 kernel there was no screen timeout set in the display settings. I set it and the problem went away, so I'm assuming that was it.
 
I had the sod issue with the first reloaded rom .. i was on the phone
Trying to get directions to sons dentisy so went stock so my calls
would end smoother

My music would go crazy...playing randomly and even when firced closed
But that could very well be my part.

The last thing is vanishing memory. Id go from 4g to 00mb which is
only an issue because it disables my ability to download...this seems
To be a non pervasive issue.

Cant wait for fixes/ work arounds cuz stock is so lame:)
 
AndroidSureDo said:
I had the sod issue with the first reloaded rom .. i was on the phone
Trying to get directions to sons dentisy so went stock so my calls
would end smoother

My music would go crazy...playing randomly and even when firced closed
But that could very well be my part.

The last thing is vanishing memory. Id go from 4g to 00mb which is
only an issue because it disables my ability to download...this seems
To be a non pervasive issue.

Cant wait for fixes/ work arounds cuz stock is so lame:)
Click to expand...

Could very well be user error because top post specifically says
No titanium backup restores. I like short cuts :D
 
Is wifi hotspot functional? I tried with a HP TouchPad with CM7, the connection drops a few seconds after successful connection and then I can't find the AP anymore. Have to disable/enable wifi hotspot for the AP to reappear.
 
Shoutout to Whyzor for getting the CM7 custom automatic brightness working perfectly. Here's my settings:

Window length: 5 s
Reset threshold: Disabled
Sample interval: 0.5 s
Use custom: yes
Screen dim level: 26
Edit levels:
Number of levels: 20
Levels: see below
screenshot-1329861298961.png
screenshot-1329861308073.png
screenshot-1329861317025.png


Allow light decrease: yes
Decrease hysteresis: 50%

This does a pretty good job of matching ambient light levels. All the ambient light level boundaries are odd multiples of 15 because the sensor reports lux levels in multiples of 30, which means that as the moving average is calculated, it will "quantify" into those multiples of 30 (given a constant light level reading), and away from the transition levels, so ideally it'll transition and settle into a set brightness as quickly as possible. I made 26 the dimmest the screen gets because any darker than that gets unreadable in light levels too low for the sensor to measure with any additional precision, aka the minimum value the light sensor reads is reached.

EDIT: (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 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.
 
Thanks for taking the time to post this.

Seems like I've had a part-time job in working on these settings. I'll be glad to try these.
 
One issue i am having with 02-18 (no issue with 02-02) Is when in a call when you move the phone to go to hang up or open the numberpad to navigate a IVR the screen does nto turn on i am having to use the power button to turn on my screen while in a call so that i can hit numbers, turn on speaker, or end the call
 
wutname1 said:
One issue i am having with 02-18 (no issue with 02-02) Is when in a call when you move the phone to go to hang up or open the numberpad to navigate a IVR the screen does nto turn on i am having to use the power button to turn on my screen while in a call so that i can hit numbers, turn on speaker, or end the call
Click to expand...

Whyzor has suggested adding this to the end of your build.prop
mot.proximity.delay=150

I would add make sure Always Use Proximity is checked. That has helped some folks in the past.
 
Lets be thankful for the great job Whysor, TG and Issac and others have done to make this ROM as great as it is, and for continually improving it.
They are doing this free. You are getting it free.
 
marc12868 said:
I don't know if you are trolling, or if you are being serious either way just stop and appreciate what Whyzor has done. He could have just done nothing and then we might be now
Marcus is right its a mother of a problem and there are cables to get it working from the USB port at least I got a friend that uses one on a g2s any way xda has a thread for it there mmust be alot of issues its a realitivly new fiction on android so surely a turf one to conquer.
Click to expand...
 
jondroot said:
cause i dont have time to nerd out
Click to expand...

Come on, dude. If it were simple, dont you think hdmi would be working already?

You dont accomplish anything with that attitude and you're hurting those of us who rely on the devs in this forum. What if Whyzor just decided to not post anymore...would that make you feel better?

Look! He is updating this rom which he does for free on a daily basis. All I have to say is thanks Whyzor!
 
If you really need HDMI, use stock and stop complaining. Be grateful you have better options available for your phone at no cost at all.
 
Well. Hi there.

So I come by, expecting to find appreciation for hard working devs and some feedback to help with the effort.

But instead, I find other - so I have deleted that as noise.

I think everyone here can dig where I'm coming from - post politely, without any snark, or face penalties for failure to follow a mod warning.

Somehow, I am pretty sure that things will improve here. I'll be watching with great interest. :) ;)
 
ok im having 2 problems...
1. the prox sensor not working.
2. google music f/c alot and gives me black screens
 
PimpinEZ said:
ok im having 2 problems...
1. the prox sensor not working.
2. google music f/c alot and gives me black screens
Click to expand...

what exactly are you doing to reach the conclusion #1 above? proximity sensor works only during phone calls. I don't use the newer google music app myself, but others have said it does work, it sounds like it's an app problem, or some settings or messed up cache. Wipe caches in recovery mode & also application cache for google music.
 
You must log in or register to reply here.
Back
Top Bottom