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

Bloody Templar said:
Hey Whyzor, I just wanted to post thanks and props on an awesome build! You are a god among men, my friend!
Click to expand...

LOL, thanks, I appreciate that and all the nice comments from others. I'm just another guy who knows a bit about gadgets & software. Maybe I'm a little obsessive about improving phones, learning new things along the way, and sharing the results.
 
Austrie said:
You should (have) reserve 2 or 3 posts after main post if you are gonna add a lot of info, like wise for me, I needed(recently) one more reserved spot for information about governors, I/O, undervolting, over and underclocking; but I didn't so I just the picked the most important(frequently asked) at the bottom of my main post.

EDIT: You should put your changellog in a quote or code form to save more space, and just use color, bold, and italic to show the beginning of each build version.
Click to expand...

You're cramping my style man... ;) I don't see the point of reserving more than 2 posts, I can always format them however I want, using big separators is the same as having another post. And my philosophy is towards simplicity, too much info at once can be confusing. I provide links to the important relevant info. Also when something changes, there's less places that need updating (or has out-dated info).

Can't remember the last time I blushed, oh yeah when I had too much to drink.
 
Something seems wonky with the back button and the 4 sec app kill delay. Instead of going back 1 step with each tap, seems to go back continuously while holding it for the required 4 sec delay. May back up 5 steps or more while holding it.
I was kind of worried about changing the action of the back button, but figured I could get used to it. Sure would love to have it back the way it was. I think that even working the way intended, 4 sec to kill slows down things way too much.
Just my opinion... Others May disagree I guess.
 
thangfish said:
Something seems wonky with the back button and the 4 sec app kill delay. Instead of going back 1 step with each tap, seems to go back continuously while holding it for the required 4 sec delay. May back up 5 steps or more while holding it.
I was kind of worried about changing the action of the back button, but figured I could get used to it. Sure would love to have it back the way it was. I think that even working the way intended, 4 sec to kill slows down things way too much.
Just my opinion... Others May disagree I guess.
Click to expand...

I may shorten it to 3 seconds in the next version (default was 2 seconds). I just tried holding back in a few nested menus, and it doesn't go back repeatedly, but stays on the screen until it's either killed or I release the key. I think it may be an app specific behavior you're experiencing
 
Whyzor said:
I may shorten it to 3 seconds in the next version (default was 2 seconds). I just tried holding back in a few nested menus, and it doesn't go back repeatedly, but stays on the screen until it's either killed or I release the key. I think it may be an app specific behavior you're experiencing
Click to expand...

Ok. I'll experiment more.
Opera mini, fyi.
I used to be able to kill it on whatever screen it was on. Now, its long gone by the time 4 seconds elapses and I kill my launcher. :)
Dependably.
 
thangfish said:
Ok. I'll experiment more.
Opera mini, fyi.
I used to be able to kill it on whatever screen it was on. Now, its long gone by the time 4 seconds elapses and I kill my launcher. :)
Dependably.
Click to expand...

Ah yes, does the same on my Opera Mobile too. I believe I ran into this a while back when using QuickSettings, which has an optional shortcut that brings it up by holding the search key, and would never work in opera. I think it's because their apps use the "key-down" detection, rather than the proper "key-released" detection like most other apps. File a bug report with them :)
 
Whyzor said:
And my philosophy is towards simplicity, too much info at once can be confusing. I provide links to the important relevant info. Also when something changes, there's less places that need updating (or has out-dated info).
Click to expand...
Agreed. There have been many times I went to look at a ROM or something and there was so much bold and italics and all different colors and font sizes that it was incredibly hard to read. With this kind of stuff, people need the clearest instructions, especially with the potential to brick your $300 phone.

BTW, I agree that the 4 seconds feels too long. I'd definitely like 3 better.
 
Whyzor said:
[ snip ]I think it's because their apps use the "key-down" detection, rather than the proper "key-released" detection like most other apps. File a bug report with them :)
Click to expand...

Perhaps, but this behavior just started with this ROM version. Worked as expected with beta 08.
Not just opera either, I figured out.

Edit, hell maybe I'm not holding the button down good enough/long enough.
 
any reason why my gameloft games freezes up, I tried to clear dalvik cache and seems have no effect, plus I played with the governors and even went high as 1.4GH I reboot same effect -game freezes-, so I re-flashed the rom, FIRST I even clean my sd hard wipe it clean minus my music and pictures everything else I erase then I wipe data/factory reset, wipe cache partition, un-mount cache (no reason too just feels good LOL),and even format system (ouch format) Wipe dalvik cache....What am I doing wrong because with Froyocream 1.2 my games play very well so its not like a bad download any suggestions ?
 
thangfish said:
Perhaps, but this behavior just started with this ROM version. Worked as expected with beta 08.
Not just opera either, I figured out.

Edit, hell maybe I'm not holding the button down good enough/long enough.
Click to expand...

So here's the tradeoff, the latest touchscreen driver should be more reliable/smoother and gets rid of the freezing bug. The old one may have just masked the problem of some apps not using 'touch-release' to trigger events. I just went through a couple dozen of apps on my phone and most can be killed by holding, a couple behave like opera does. Killing can corrupt data, and should only be used on misbehaving apps.

This brings up the issue, Android OS supports some behaviors, and Google has guidelines for writing apps, not all devs don't follow those guidelines and the behavior is inconsistent, it's one of the downsides of giving more freedom to devs (unlike Apple for example).
 
TriumphBug said:
any reason why my gameloft games freezes up, I tried to clear dalvik cache and seems have no effect, plus I played with the governors and even went high as 1.4GH I reboot same effect -game freezes-, so I re-flashed the rom, FIRST I even clean my sd hard wipe it clean minus my music and pictures everything else I erase then I wipe data/factory reset, wipe cache partition, un-mount cache (no reason too just feels good LOL),and even format system (ouch format) Wipe dalvik cache....What am I doing wrong because with Froyocream 1.2 my games play very well so its not like a bad download any suggestions ?
Click to expand...

Because Froyo is a stock ROM, it may have internal settings/tweaks that only the manufacturer enabled & uses. CM7 is open source ported onto this device, along with some things still broken. It could be the game dev not using documented standard ways of doing things, or it could be an internal issue with CM7 on MT. Not sure what the problem is. Of the few games that I've played they all worked fine.

You could have CM7 as a daily driver if you only game once in a while, have a Froyo nandroid backup for when need to play those games or use HDMI.
 
You could have CM7 as a daily driver if you only game once in a while, have a Froyo nandroid backup for when need to play those games or use HDMI.[/QUOTE]


YOU read my mind, thats why I think I will buy a second SD card one for CM7 and one for Froyo (when in the game mood) and yes do a nandroid backup on each card

Thanks for explaining it to me makes sense some gameloft games works well on this ROM and some freezes


THANKS FOR YOUR WORK
YOU'RE THE MAN
:eek:
 
Whyzor said:
So here's the tradeoff, the latest touchscreen driver should be more reliable/smoother and gets rid of the freezing bug. The old one may have just masked the problem of some apps not using 'touch-release' to trigger events. I just went through a couple dozen of apps on my phone and most can be killed by holding, a couple behave like opera does. Killing can corrupt data, and should only be used on misbehaving apps.
Click to expand...

Well, ok then...
Anyway, I'm real happy with the rest of the ROM.
Kernel too.
Thanks
 
Hello I just downloaded and installed this rom an hour ago. When I received a text message I noticed the notification light is red. I thought it only blinked red when the battery was dead. Is this just my phone or do other people have this problem. Thanks ahead.
 
MIKE153 said:
Hello I just downloaded and installed this rom an hour ago. When I received a text message I noticed the notification light is red. I thought it only blinked red when the battery was dead. Is this just my phone or do other people have this problem. Thanks ahead.
Click to expand...
It's not a problem, it's a feature; more specifically it's called a notification light. Does it seem like a problem or where you just being sure? Also, Welcome To The Forums, enjoy your stay in your room :D
 
Austrie said:
It's not a problem, it's a feature; more specifically it's called a notification light. Does it seem like a problem or where you just being sure? Also, Welcome To The Forums, enjoy your stay in your room :D
Click to expand...

I was just being sure. Because on stock it was green when I received a message or email and red when the battery life was low. So I just wanted to make sure I installed the rom correctly.
 
raysurrx7 said:
after I flashed this it says that I am located off the coast of Ghana on maps. but i live in San Diego
Click to expand...

I think that's because the new GPS quickfix has intermediate_pos reporting on. I will disable it in the next version. In the meantime you can edit /system/etc/gps.conf file and find the line that says "INTERMEDIATE_POS=1", change it to 0" & reboot. Be sure to mount the /system as rw with these commands first in terminal emulator or adb shell:

su
mount -o rw,remount /system
 
I just tried out the gps, its something I rarely use, and it was interesting it started showing me as somewhere in the middle of the ocean but then it returned me to my actual location, now it seems to work fine. Basically my gps as far as I can tell works fine.

I actually had some issues with your last build but it very well may have just been me, since this one seems to work great. I've had no problems with scrabble( I think it was an issue with adfree) and my wifi has been fine as well(I think there was an issue there with Juice Defender).
 
As for me, GPS works great. It locks almost instantly, previously it took a minute or so.
It seems that the battery life have gotten a little better and touchscreen works more smoothly.

So far so good. Thanks for your work.
 
my phone still won't deep sleep after this update. cleared cache and dalvik, flashed update, after about 3-6 hours in deep sleep it sits at 200mhz. Running juice defender if that has anything to do with it. enable disabling wifi doesn't do anything.
 
idbl_fanatic said:
I just flashed this, and now my music will stutter like if the WiFi was on, when CM7 was just starting. (WiFi is off)
Click to expand...

Try a different CPU governor (like interactive or ondemand) and raising the minimum frequency. No code related to wifi or audio changed from last version. I don't have music stuttering using 61-1024 interactive.

bobloadmire said:
my phone still won't deep sleep after this update. cleared cache and dalvik, flashed update, after about 3-6 hours in deep sleep it sits at 200mhz. Running juice defender if that has anything to do with it. enable disabling wifi doesn't do anything.
Click to expand...

Download the BetterBatteryStats app here, and tell me what the partial wakelock & kernel wakelock processes are. I can't reproduce it on my phone.
 
You must log in or register to reply here.
Back
Top Bottom