thangfish
Android Expert
I've also made a habit of that, when finished with the camera.
-
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)
- Thread starter Whyzor
- Start date
-
- Tags
- motorola triumph
I think I can consistently reproduce this problem (using 1-26 build)Phone lasted less than 7 hours again today. Before it died, I checked BBS and sure enough, mmc1,2,3. Threw in the new battery, started up, and no issues again. Cycled wifi a few times and has still been fine. Weird. Past few days have been great though. Just about got me through the day on one battery.
1. Have JD enabled, and let it manage Wifi
2. Turn on Wifi, wait till Wifi connection takes over 3G.
3. Turn off screen and wait a minute, let JD to disconnect the Wifi
4. mmc1 2 3 are now showing up and wouldn't go until reboot.
Anyone can reproduce this problem?
Please let me know if there is any test I can help run on the phone
Whyzor
Android Expert
The status bar fix was upstream from CM7. I never noticed freezing status bar before, nor after that was in the build. I basically run with all animations, transitions, performance settings set for performance instead of eye candy. Maybe that has something to do with it. I'll keep a lookout for it.
I think I know what the problem is. TG's intentional wakelock for the wifi & my BT wakelock was implemented in the MSM_SDCC host code, which generates wakelocks called "MMC" (should've been properly named from the start. 1 of 3 MMC hosts can create the wakelock, and then later another host tries to unlock it, it can't because wakelocks can only be created by the same device. I had a fix last night, but it needs to be moved outside fo the MSM_SDCC code since it's causing the system to not boot. Will hopefully get something working in the next day or two.
frdmspoplr
Well-Known Member
Oh alright. I thought it was a fix you made. I used to run my phone like you as well. Oddly enough, I never had the status bar freeze on me until the 1/25 build, the first to incorporate the upstream cm7 fix, and I've experienced it one other time since flashing 1/26. Also, ever since the 1/25 build, probably 9 times out of 10 I get a status bar fc when I boot. It never occurs prior to 1/25, so I'm assuming its related to the fix, which obviously didn't completely work since I never encountered the problem until the fix lol.
minus5252
Well-Known Member
For those interested, here is the video installation guide for the 1/26/12 TG-Reloaded CM7 ROM:
CM7 (CyanogenMod 7) TG-Reloaded 1/26/12 - Carrier Label Changes, ICS Animations and Bluetooth Tweaks - YouTube
P.S. Speaking to those discussing the battery life above, I usually get to 24-30 hours on a charge, and rarely does it get below 15% before I charge it...loving the battery life. I play a few games for a few minutes every few hours, check email constantly, make calls and surf the web some.
CM7 (CyanogenMod 7) TG-Reloaded 1/26/12 - Carrier Label Changes, ICS Animations and Bluetooth Tweaks - YouTube
P.S. Speaking to those discussing the battery life above, I usually get to 24-30 hours on a charge, and rarely does it get below 15% before I charge it...loving the battery life. I play a few games for a few minutes every few hours, check email constantly, make calls and surf the web some.
idbl_fanatic
Android Enthusiast
nochancenine
Lurker
The last time I visited this forum there was a new kernel posted: WhyKernel-01-28
I flashed this kernel and since have seen quite a noticeable improvement in battery life, however, it appears that this kernel update has since been removed. Is there a known problem with this kernel WhyKernel-01-28? I haven't noticed any problems so far. In fact, the battery life gain since flashing this kernel has been really great.
I flashed this kernel and since have seen quite a noticeable improvement in battery life, however, it appears that this kernel update has since been removed. Is there a known problem with this kernel WhyKernel-01-28? I haven't noticed any problems so far. In fact, the battery life gain since flashing this kernel has been really great.
Whyzor
Android Expert
It was an attempt to fix the wakelock bug (which didn't work), I also have a better grasp of the problem now. You noticed better battery probably because just haven't run into the wakelock yet. I'll upload new ROM or kernel once a proper fix is in.
In the mean time, to avoid the wakelock bug, just reboot phone and don't turn on wifi or BT. You should have good battery.
Whyzor
Android Expert
Looks like you're using some sort of weather app/widget, and leaving wifi on a lot. So apps & services may be running in the background, using up power. See what's running in Settings - Applications - Running Services. A phone should be in deep sleep mode when the screen is off, and properly written apps only wake it once in a while to get data. Or even better, uninstall any such apps so the phone remains sleeping until needed. More tips can be found in this thread:
http://androidforums.com/motorola-triumph/461571-guide-triumphant-battery-tips.html
GreyCelt
Well-Known Member
Thanks Whyzor. Yeah, when I'm at home I have wifi on the whole time. When I'm going out and I'm not going to be near a Hotspot I turn off wifi. I've also gotten in the habit (probably from my days with the Intercept) of turning the wifi sleep mode to never. So, once you get that wake-lock fix out in the next kernel, I can set that to "when screen turns off" and save more battery, right? Maybe that's why I never experienced the wake-lock problem that everyone is talking about because I always had mine set to "never".
Whyzor
Android Expert
No, you won't experience any difference unless you turn off Wifi & BT. TG put an intentional wakelock for wifi (& I did for BT), so it doesn't fall asleep when screen is off and some app needs it (like a VoiP, or transferring data in the background). It's a problem with the proprietary driver on the MT, and we don't have source code for that, so this is just a workaround for it. You would get much better battery by turning OFF wifi & BT when not needed. Even use 3G to sync small amounts of data in the background.
Intercepter
Well-Known Member
Is that intentional wakelock whats keeping the radio from going into standby? a lower power mode? I see that in the qualcomconfig file that there are three modes. Deepsleep, standby and mcastfilter. I read somewhere that there is a lower power setting that is there for such things such as voip.
Just Infectiou
Newbie
What governor are you guys getting one day out of the triumph using? I have my min at 245 and max at 1305 with Smartassv2. Will switching to InteractiveX improve it that much? I can usually get about 16-18 hours on a non school day where I have decent service and am not constantly using wifi.
Whyzor
Android Expert
It prevents the Wifi/BT radio from going into suspend mode (deep sleep, the lowest power mode, next higher is idle). As for whether there's another mode for VoIP, you may want to dig into the code yourself. Even if there is, it would only help save a bit of power during VoiP calls, and still may disconnect if a user is transferring data with the screen off.
I use & recommend 61-1024 interactive (not X).
Intercepter
Well-Known Member
It was not mode for during voip calls but a lower power mode that would keep you connected enough to get the call then go higher power. I am probably mistaking what I was reading anyway lol.
Israelsalinas
Newbie
Why does the headphone media volume sound very low even at the highest volume? Alredy tried different headphones. Also tried same headphones on the Optimus V with Cm7, played the same song and the sound from the OV was much, much louder. Im using PlayerPro on both phones with same equalizer settings. Why does it sound very low on the Triumph?
Whyzor
Android Expert
There's probably a bug in the code on the MT that makes it low. I've heard others say using an app like DSP Manager or Volume+ can boost it. The couple of times I briefly used the headphones, it sounded fine.
I have a new kernel uploaded, it should fix the wakelock issues, or at least show up as "wlan_lock" or "bt_lock" in betterbatterystats instead of MMC or "event", if it's TG's or my code that's doing it.
WhyKernel-01-31.zip
MediocreBadGuy
Android Enthusiast
I'm sorry if this was mentioned before, but does this have the 2 way call recording patch?
thangfish
Android Expert
Yes.
Whyzor's kernel is based on Mantera's The OC kernel.
Edit:
Just checked the change log, and it's been in there since the 2011.12.28 build. Haven't read of it being removed for any reason.
MediocreBadGuy
Android Enthusiast
Just flashed the 1-26 build and 1-31 kernel and can't believe how smooth my phone runs.. The previous builds were a bit laggy for me but this has been greatly improved. Wow my phone is a beast now lol, thanks!
Israelsalinas
Newbie
Thanks for the new kernel. I alredy have dsp manager set to treble boost and ive also tried volume+ but its never nowhere as loud as the stock rom is.
TriumphLance
Android Enthusiast
Does the new kernal address the freezing status bar issue? I've gotten it the past two days after flashing the 1/26 build