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

Bruce777 said:
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
Click to expand...

The term "black screen problem" doesn't distinguish between the 2 problems. 1 is if other side disconnects, the screen stays blank for a while and even power button won't bring it back. 2nd problem as some have reported, is when put to ear, the proximity sensor turns off the screen, but when the phone is pulled away again, it doesn't turn screen back on during the call. I have another attempted fix for the 2nd issue in the next kernel.

Bill Clay said:
Will we still have the updated GPU drivers if we use a different kernel with TG-Reloaded? :confused:
Click to expand...

There are 2 parts to the GPU drivers update, 1st part is in the kernel, 2nd part is in the /system/lib/egl/ binary files. Both are included in TG-Reloaded ROM, any other kernel will have to have the new KGSL driver component (mantera's kernels is the only other right now that supports it).
 
Any reason why this from feels a little sluggish? Compared to MIUI, it seems that way. Not to be saying anything bad, just curious if this is normal or what. Like scrolling left n right feel sluggish when you are on your home screen and swipe to other windows. Maybe its the launcher? I'll try Go launcher and see it it performs better.
 
Can someone test if the proximity sensor "not waking screen during call" problem is present or better in either of these two kernels:

Kernel 02-18 (which has the 2 sensor wakelock fix):
WhyKernel-02-18.zip

Kernel 03-23 (same as above, but disabled INPUT_GPIO):
WhyKernel-02-23_NO_GPIO.zip

EDIT: The older flashable kernels may not work with the more recent ROM builds due to newer GPU drivers.
 
Whyzor said:
The term "black screen problem" doesn't distinguish between the 2 problems. 1 is if other side disconnects, the screen stays blank for a while and even power button won't bring it back. 2nd problem as some have reported, is when put to ear, the proximity sensor turns off the screen, but when the phone is pulled away again, it doesn't turn screen back on during the call. I have another attempted fix for the 2nd issue in the next kernel.

It's funny I've actually encountered the "1st" and "2nd" problem. I've pretty much ignored the first because it happens very rarely but the second one is a constant. I'm going to flash both kernels you posted in the last post and report back.
Click to expand...
 
darknight88 said:
Any reason why this from feels a little sluggish? Compared to MIUI, it seems that way. Not to be saying anything bad, just curious if this is normal or what. Like scrolling left n right feel sluggish when you are on your home screen and swipe to other windows. Maybe its the launcher? I'll try Go launcher and see it it performs better.
Click to expand...
Mine isn't particularly sluggish. Could be the launcher. I have several widgets and ADW is the only launcher that's completely smooth for me.
 
darknight88 said:
Any reason why this from feels a little sluggish? Compared to MIUI, it seems that way. Not to be saying anything bad, just curious if this is normal or what. Like scrolling left n right feel sluggish when you are on your home screen and swipe to other windows. Maybe its the launcher? I'll try Go launcher and see it it performs better.
Click to expand...

I use go launcher, it's much smoother than the default ADW was.
 
Whyzor, quick question. I know you haven't updated this ROM (in its entirety) in a while... I was wondering if we would see a "updated" build in the future? (Not to say it needs an update. I'm really wondering if there is anything that would be updated.)
 
My ADW starts perfectly smooth but after a while the whole thing gets sluggish.

Next CM7 update, I'll wipe and start over and won't slam everything into it at once this time, making it pretty hard to observe/troubleshoot (hey, it's a novelty for me atm). I'll be making good use of the ROM Manager backup utility.
 
Whyzor said:
Can someone test if the proximity sensor "not waking screen during call" problem is present or better in either of these two kernels:

Kernel 02-18 (which has the 2 sensor wakelock fix):
WhyKernel-02-18.zip

Kernel 03-23 (same as above, but disabled INPUT_GPIO):
WhyKernel-02-23_NO_GPIO.zip

Just flash like a ROM, no need to wipe caches.
Click to expand...

I also have a problem with the proximity and I tried to install the 02-18 kernel but when I reboot after installing I get a black screen. It appears the phone has booted successfully as I hear messages coming in but I cant seem to wake the phone and it remains a black screen. I re-downloaded thinking the first download was corrupt but same thing. I also tried installing kernel 02-23_NO_GPIO and the same thing happened....black screen but messages coming in.

Restored to build 03-04 successfully. Sorry I could not help out. :o
 
I flashed the 2-18 kernel and the screen now comes back on (it does flickr / stutter a bit though) during a call when I pull it away. I haven't flashed the 2-23 kernel, and hopefully you won't have to :^)
Thanks Whyzor!
 
Oh well :(
2-18 kernel was working (screen would come on in call when i pull the phone away from my face) then it stopped.
flashed the 2-13 and didn't fix it.
thanks for trying. I'm willing to test/report anything else
 
Final build uploaded, see post #1 for link, remember to wipe cache before flashing. My proximity sensor wakes the phone up in a few brief test phone calls, (deactivated phone, which just gave a recorded message error).

The previous kernel flashable zips must not be compatible with the newer ROM builds, maybe due to new GPU drivers. The only difference between previous 03-04 and latest 03-25 kernel is latest has enabled INPUT_GPIO again (I suspect may be the cause to the proximity issue).

Kernel Changelog:
- Enabled INPUT_GPIO in kernel config again

Other:
- Reverted to original libaudioalsa.so and liba2dp blobs to be safe & since there were no noticeable audio improvements in last build.
- Default to 'dim' auto-brightness profile values by aricblunk

Updates from Cyanogenmod 7:
- Fixed EXIF data writing for camera
- Fixed soft keyboard appearing on dialer sometimes
- Show PIN entry even if lockscreen is disabled
- Backported "disappearing SD media" fixes from CM9
- Fixed ext4 image generation when size is exact multiple of block size
- Fix cursor repeatedly moving back to beginning of To field in MMS app
- Battery status can be shown in PatternUnlockScreen also
- Added Max SMS length option
- ADWLauncher: Added option to lock Action Buttons in main dock
 
I think I did something wrong. For some reason on this update my Google account is gone along with the contacts associated with it. Google Play Store works but it says I need to add an account. Once I click "Yes" to do so, nothing happens. I can't add a Google account in Accounts & Sync settings either. Any suggestions?
Other than that, everything is perfect!

I didn't wipe system or data. I will try that along with a full factory reset possibly and reflash gapps.
 
Reflashing gapps worked. My account was back after I flashed gapps and signed into Google again.. I'm gonna factory reset though in addition just because I like the feeling of a fresh install with no potential problems.
 
britton1981 said:
Reflashing gapps worked. My account was back after I flashed gapps and signed into Google again.. I'm gonna factory reset though in addition just because I like the feeling of a fresh install with no potential problems.
Click to expand...

same...

also, when playing music the phone doesnt bog down and slow down anymore. YAY! :D
 
You must log in or register to reply here.
Back
Top Bottom