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

frdmspoplr said:
I've had it happen once on 1/25 and once on 1/26. But I swiped notifications twice just now, and a couple times in the past couple days, and it didn't occur, so it's obviously very intermittent.

I too like the feature as well, as there are times where I do want to keep a notification up and clear the rest.

As a sidenote, cm7 has had that feature for quite a while, so I'm not sure it could quite be considered "new."
Click to expand...

I'll leave it as is, and report it as still causing problems on our phone. Hopefully someone who knows more about it can fix it upstream. I guess it's only new for stock ICS, CM had it for a while.
 
Mr_Coffee said:
GreyCelt-curious as to your Theme of your MT?:cool:
Click to expand...

This is the notification screen. I have GO Launcher EX with the Windows 7 theme as a base theme and some minor tweaks to take out the obvious "Windows" looking items. I'm using Beautiful Widgets with the ICS theme and that's the weather part of the notification screen. The other part is an app called My Data Manager Free that tracks my data usage. Now that VM is gonna start throttling us in March I felt it was necessary to start tracking my data usage to see where I stand. I hope that answers your question.

See my Lock Screen and Home Screen here.

http://androidforums.com/motorola-triumph/378577-post-your-triumphant-screenshots-5.html#post3881336

EDIT: Oh, I forgot...I'm using the Espinosa Nova font from the font installer of the ROM Toolbox app. In case you don't know already, ROM Toolbox is a great all in one app for managing and modding your ROM.
 
Whyzor said:
Build 2012-01-26

Updates from Cyanogenmod 7:
- Fixed status bar swipe race (freezing) condition
- Customizable Carrier Label in Settings
- Bluetooth quickconnect option
- ICS rotation & transition animations.
- Option to lock volume keys in silent mode.
- Automatically restart ADB if TCP port settings change.
- Other minor fixes.

Build 2012-01-21:

Kernel changes:
- Touchscreen interrupts have dedicated workqueues now for faster processing. Removed firmware update & other non-functional code.
- Disabled Smartass & SavagedZen CPU governors. They were causing extra early_suspend processing, there are better governors available still.

Other changes:
- Bluetooth & Wifi can be enabled at the same time without 100% CPU utilization.


First version.
Click to expand...

I'm still using 1\21 build. I hightlighted the CM7 line where there might be a clue.

Edit: My point is that I use the swype to remove notifications sence I discovered it exsisted. I am going to apply the 1\31 kernel now
 
dsmryder said:
Has anybody sent a notice to CM?
Click to expand...

I saw on github that Whyzor already posted a comment. Its freezing on my build too. I just hate to have to reboot every time it happens. I may revert to one of my older builds until there is a solution.
 
I flashed the 1/31 kernel today and after using wifi my phone does deep sleep. Whysor, Thank you again for your continued work and for being so helpful.
 
sharpe351 said:
I saw on github that Whyzor already posted a comment. Its freezing on my build too. I just hate to have to reboot every time it happens. I may revert to one of my older builds until there is a solution.
Click to expand...
Is it only when you swipe notifications off, or at other times?
 
sharpe351 said:
when I touch the items on the menu it will sometimes freeze, kind like a half pass. I also have wakelock issues. Doesn't happen often either.
Click to expand...

Because the touchscreen on the MT is oversensitive, sometimes a tap registers as a slight side swipe, which activates the code that could freeze the phone. I'll push the kernel fixes for the wakelocks later tonight so you can pick that up for your kernel.
 
dsmryder said:
I'm still using 1\21 build. I hightlighted the CM7 line where there might be a clue.

Edit: My point is that I use the swype to remove notifications sence I discovered it exsisted. I am going to apply the 1\31 kernel now
Click to expand...

I know which ROM had the fix included. I was asking when people started seeing problems to determine whether the fix makes a difference on our phone. Apparently it doesn't because there were reports of freezing before and after that change went in. If problems only happened before, then the fix worked, if problem existed only after, then I would revert the change. Since neither is the case, I'll just leave it in.
 
Any idea what causes the glitchy video in portrait mode? I know it's a known issue but it doesn't just affect video players (ie. youtube, etc.). If it was just a matter of needing to switch to landscape to watch videos, I'd have no problems but this also affects my favorite weather apps, BeWeather and GoWeather! The animated in-app backgrounds apparently use video and it skips and stutters and in general ruins the feel of the app. I love this ROM and really don't want to go back to stock just to use these weather apps...
 
moonknightus said:
Any idea what causes the glitchy video in portrait mode? I know it's a known issue but it doesn't just affect video players (ie. youtube, etc.). If it was just a matter of needing to switch to landscape to watch videos, I'd have no problems but this also affects my favorite weather apps, BeWeather and GoWeather! The animated in-app backgrounds apparently use video and it skips and stutters and in general ruins the feel of the app. I love this ROM and really don't want to go back to stock just to use these weather apps...
Click to expand...

It could be a codec problem (since it only happens on some types of videos), or could be some unknown patch Motorola made in their stock kernel that we don't have source code for. Who knows, it would be a wild goose chase to find it.
 
Wait, I'm a little confused about the 1/31 kernel - Is the intention to fix the wakelock problem, or just make it more obvious to BetteryBatteryStats users?

Is the advised way to maximize battery life still to reboot after deactivating wifi or BT?

Thanks!
 
Bloody Templar said:
Wait, I'm a little confused about the 1/31 kernel - Is the intention to fix the wakelock problem, or just make it more obvious to BetteryBatteryStats users?

Is the advised way to maximize battery life still to reboot after deactivating wifi or BT?

Thanks!
Click to expand...

It does both, but if my attempt fails, at least from now on it will report proper wakelock to make future reports more useful. So far I'm noticing it has fixed the BT & Wifi wakelock problems (no guarantee about other wakelock problems though). No need to reboot after BT/Wifi with this kernel.
 
Whyzor:

Thank you for uploading the 1/31 kernel, it is helping me figure out the source of the wakelock issue. I've isolated the problem on my phone to letting JuiceDefender manage wi-fi. If I manage wi-fi manually, I can get the phone to deep sleep by disabling wi-fi prior to the screen turning off.

If I leave JuiceDefender on, and the screen sleeps, it will turn off wi-fi but the wakelock will remain.

BetterBatteryStats reports that the wakelock is named "wlan_lock".

Are there multiple methods for disabling wi-fi on the Triumph, or Android 2.3? It's possible that JuiceDefender is using some /proc or /sys interface to turn off wi-fi.

When I turn the wi-fi on and off via Extended Controls, the wakelock is released. I'll send the author of Juice Defender an email, but I want to be thorough about it.
 
You must log in or register to reply here.
Back
Top Bottom