Root [ROM][Beta][FINAL] CM7 Android For Triumph [Tickerguy Edition, Kernel: mine] 11/19

[TheBritton]

Are all of you that are having reboot problems using Juicedefender? Because today I installed Juicedefender for the first time, and I'd definitely have to say that it doesn't get along with our CM7. Seriously, I've had at least 10 reboots today. Typically, I've averaged less than one a day. It seems like it's mostly related to wifi being turned on when the screen is powered on. It's pretty crazy that so many of the problems we're having with CM7 seem to be directly related to the wifi.

I don't use Juice Defender. But for me, WiFi on even while the screen is awake locks up alot of apps but causes very few reboots (I reboot manually every morning and evening) I have resorted to streaming Netflix via 3G now (which is actually good quality to my surprise) and leaving WiFi off at all times.

As I mentioned in an earlier post, my CPU usage widget locks at 100% and CPU clock speed is locked at full speed as a result of WiFi being active which makes streaming Netflix impossible along with a severe hit to battery life. Not complaining, just sharing my experience with this issue. I can do without WiFi for now, in exchange for such an awesome ROM.

 

[metatroid]

The Wfii lockup is very serious as it prevents a backtrace when it happens and as such I'm literally shooting in the dark. I cannot get it to lock up if it's plugged into USB [..] I can't attach to the phone when it happens (e.g. to use gdb or similar on the kernel to force a break and then backtrace it.)

This might be useless info that you already know, but it is possible to run both adb and gdb wirelessly using 'ADB Wireless' and gdbserver/gdbclient respectively.

 

[tickerguy]

Debuggers are worthless when the kernel is locked up either in a spinlock of some sort or via a deadlock; a wireless interface does you no good (nor does a wired one) as what you need is a way to generate an NMI - which in this sort of environment you don't have.

 

[minikirchner]

Are all of you that are having reboot problems using Juicedefender? Because today I installed Juicedefender for the first time, and I'd definitely have to say that it doesn't get along with our CM7. Seriously, I've had at least 10 reboots today. Typically, I've averaged less than one a day. It seems like it's mostly related to wifi being turned on when the screen is powered on. It's pretty crazy that so many of the problems we're having with CM7 seem to be directly related to the wifi.

I had JuiceDefender Ultimate when I was still on stock. Loved it! But if I remember correctly, it doesn't work on Android 2.3. I switched to Green Power Free until they get an update to work with 2.3. Both of them work very well. But Juice Defender I guess doesn't work for 2.3. Hope this helps!

 

[ziggy46]

There isn't any reason to tear anything apart. Just have a look at the source code found at these links:

TG's Github account: https://github.com/tickerguy
Mine: https://github.com/ikarosdev
Cyanogenmod: https://github.com/CyanogenMod

You can also check the issue tracker if you feel like taking on a project: https://github.com/ikarosdev/CM7_Triumph_bug_tracker/issues?sort=created&direction=desc&state=open

Oh, and Motorola's pathetic attempt at being "open" with us: Triumph WX435 / Home / Home

i didnt mean stip it down to code or anything... i just meant open up the zip and look around, change some things, then flash it. just to get the basics and then move higher (source code) but since he has that experience he should be ok with building from source.

 

[TheGeekRedneck]

I dont know if this helps or not but For me the reboots seem to be directly related to the amount of Bluetooth and wifi toggling I've been doing.

For example I use an app called Unified Remote to control my home theater pc via the touch screen on the phone through a Bluetooth connection. Every thirty minutes or so the Bluetooth connection will drop and the only way to fix it is to toggle Bluetooth off and then back on again with the status bar power control widget. About every third time I have to do this the phone will reboot... its almost like clockwork.

 

[TheBritton]

Quick question. Does the battery temp sensor work in this ROM? My bat stat widget seems to always show 76.1 degrees with no fluctuations. Just curious.

 

[SamuraiFox18]

Apparently with wifi off, setcpu with low modifying speed for each profile of battery level, and no live wallpaper makes my phone save more battery power and no reboots. And I am happy until they come up with the beta releases.

 

[frdmspoplr]

I had JuiceDefender Ultimate when I was still on stock. Loved it! But if I remember correctly, it doesn't work on Android 2.3. I switched to Green Power Free until they get an update to work with 2.3. Both of them work very well. But Juice Defender I guess doesn't work for 2.3. Hope this helps!

I just tried out Green Power Free, and it does the same thing Juicedefender did...makes my phone completely unusable. In just a half hour I had about 3 or 4 reboots. I'd love to be able to use one of them, but I guess I'll have to stick to doing every thing manually. Maybe this is why it didn't ship with GB in the first place, cause Motorola knew that wifi would bork every thing?

 

[laidback7]

thanks isaac, i'm on it

 

[isaacj87]

I had JuiceDefender Ultimate when I was still on stock. Loved it! But if I remember correctly, it doesn't work on Android 2.3. I switched to Green Power Free until they get an update to work with 2.3. Both of them work very well. But Juice Defender I guess doesn't work for 2.3. Hope this helps!

Sure it does. Albeit, I'm using the free version. I'm running Juice Defender on MIUI (2.3.5) and it's working quite well. Solves all my data drop issues!

@laidback7:

No problem, glad to have you with us.

 

[johnpro112]

Hey guys I'm new to the Motorola Triumph. I was wondering is there any possible way to remove the "Virgin Mobile" name in the navigation bar/notification bar? Other than that this port is awesome! This phone is much better than the Samsung Galaxy Indulge.

 

[isaacj87]

Hey guys I'm new to the Motorola Triumph. I was wondering is there any possible way to remove the "Virgin Mobile" name in the navigation bar/notification bar? Other than that this port is awesome! This phone is much better than the Samsung Galaxy Indulge.

Yeah, there is. I can't remember off the top of my head, but you can set a custom carrier name (or remove it period) in Settings --> Cyanogenmod Settings.

 

[evanrobinson85]

Ticker or Isaac, I am interested in learning to develop Android games, apps, and firmware. I need to start off small seeings how I have no programming experience. And at the time I have an idea for a flash game that already exists from the romp but want to figure a way to integrate it in to Android as a playable app. Any suggestions where I should start, or know of some good how to for dummies books..? Thanks in advance.

 

[lifeblows10]

I have noticed that my proximity issues went away when I checked to "Always use proximity" under Settings>Call Settings

 

[johnpro112]

Apparently with wifi off, setcpu with low modifying speed for each profile of battery level, and no live wallpaper makes my phone save more battery power and no reboots. And I am happy until they come up with the beta releases.

I can vouch that this helped with stopping the consistent reboots.

 

[TheBritton]

I can vouch that this helped with stopping the consistent reboots.

Same here.

 

[elflip88]

My mms is not working, what was that app to fix it???

 

[tickerguy]

What's coming in the next release:

1. Possible fix for the data drop issue. I am TESTING a change in the framework code that should detect the "Type A" (data shows connected but is dead; voice/SMS works) problem. The "Type B" problem (infinite "Searching") is definitely in the Radio code (it happens under Froyo too) and is nearly impossible to detect accurately, as it looks exactly from an application perspective as if there really is no signal. I think I have a fix for Type "A", but can't fix Type "B". Again, this is under test and what I did might not work - I need to catch it "fixing it" at least a couple of times before I declare success (it hasn't so far, but I haven't dropped Type "A" so far either since I added it.)

2. Removed front camera features that are unsupported (the cause of the blowups); that's now fixed.

3. Working on trying to get the mirroring back in snapshots (taken pictures) and video from the FFC. This should have been fixed in the last update but wasn't, and it's not clear why. I didn't hold the previous build on this, and may not hold this one either.

4. Soft keypad lights are now PWM-controlled and the default table (you can change it in CM7's settings) now has the keypad backlight on "softly" in low light, ramps to match middle lighting conditions, and then turns them OFF in near-daylight and above.

Several attempts have been made to resolve the Wifi lockup on sleep with it active. So far, no dice. One fix from a different related build was attempted but failed. This is a very serious problem in terms of finding it for a whole host of reasons and it is very hard to run down due to how it locks up.

There are a handful of other things I want to behave differently and of course the other bugs on the list, including the proximity sensor. That one is evading me right now as we're using the Froyo libraries. I suspect the only fix for that is to get off the Froyo libs, which may prove difficult - we'll see.

There is no timeline on the next release at this point but I will keep people posted and may choose to loose what I have at any point in time if it appears it would be useful (and is stable enough to do so.)

 

[frdmspoplr]

Is there any way to connect to my PC via bluetooth without enabling tethering?

 

[tickerguy]

What are you trying to do? Most of the bluetooth functionality is supported, if your PC stack handles the various functions (not all do.)

 

[frdmspoplr]

What are you trying to do? Most of the bluetooth functionality is supported, if your PC stack handles the various functions (not all do.)

I was using Unified Remote, but tethering automatically turns on, so then I can't keep the phone wifi on. It's not a big deal since I can just use 3G, but I was just wondering if there was a way to disable tethering.

 

[tickerguy]

Huh? Tethering should NOT automatically turn on. That has to be requested from the PC end - figure out why your PC is requesting access to the network via the Bluetooth connection and turn it off on that end.

 

[minus5252]

What's coming in the next release:

1. Possible fix for the data drop issue. I am TESTING a change in the framework code that should detect the "Type A" (data shows connected but is dead; voice/SMS works) problem. The "Type B" problem (infinite "Searching") is definitely in the Radio code (it happens under Froyo too) and is nearly impossible to detect accurately, as it looks exactly from an application perspective as if there really is no signal. I think I have a fix for Type "A", but can't fix Type "B". Again, this is under test and what I did might not work - I need to catch it "fixing it" at least a couple of times before I declare success (it hasn't so far, but I haven't dropped Type "A" so far either since I added it.)

2. Removed front camera features that are unsupported (the cause of the blowups); that's now fixed.

3. Working on trying to get the mirroring back in snapshots (taken pictures) and video from the FFC. This should have been fixed in the last update but wasn't, and it's not clear why. I didn't hold the previous build on this, and may not hold this one either.

4. Soft keypad lights are now PWM-controlled and the default table (you can change it in CM7's settings) now has the keypad backlight on "softly" in low light, ramps to match middle lighting conditions, and then turns them OFF in near-daylight and above.

Several attempts have been made to resolve the Wifi lockup on sleep with it active. So far, no dice. One fix from a different related build was attempted but failed. This is a very serious problem in terms of finding it for a whole host of reasons and it is very hard to run down due to how it locks up.

There are a handful of other things I want to behave differently and of course the other bugs on the list, including the proximity sensor. That one is evading me right now as we're using the Froyo libraries. I suspect the only fix for that is to get off the Froyo libs, which may prove difficult - we'll see.

There is no timeline on the next release at this point but I will keep people posted and may choose to loose what I have at any point in time if it appears it would be useful (and is stable enough to do so.)

AWESOME! Thanks for the update, can't wait. I have noticed much fewer 3G drops in A0.8, to the point that I thought it was already fixed until yesterday.

Keep up the great work!

 

[tickerguy]

Well the code change has caught two data drops thus far today and fixed both without intervention. It appears to be working, but I'm going to run it for a bit yet before I loose it, along with looking for a few more things I'd like to bundle into the next turn.