• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

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

Okay, I am having a very strange issue and I think I have pinpointed it to the Wifi.
I attempted to watch a movie on Netflix with Wifi enabled last night. As soon as the movie started it jerked, skipped, wouldn't hardly play anything. My CPU usage widget showed 100% CPU usage during this and even after I closed out Netflix. With the screen idle it was still at 100%.. I toggled Wifi, airplane mode, rebooted STILL happened. I rebooted into recovery, cleared cache, cleared dalvik, re-flashed the ROM and upon boot it was INSTANTLY at 100% CPU usage.
Here's what confused me.. as SOON as I toggled the Wifi off and switched to 3G the CPU dropped down to 30% usage and the clock speed lowered as well. I was able to finish my movie in 3G. Halfway during the movie I decided to toggle the Wifi on to see what happened and there was instant CPU spike. Netflix then slowed to a halt, force closed, and the CPU spike remained for MINUTES until I turned off the Wifi which again immediately reduced the CPU to normal
Any thoughts, comments, or suggestions? Is this releated to the memory leak?
 
GBPackers said:
Is the problem with 3G not working after the phone sleeps for awhile going to be addressed ever? I have to disable data and re-enable it every time for it to work again. I know tickerguy said that to radio code should work, but there is definitely a difference in stock compared to CM7. Stock I can always use data right after the phone is woke up. Thanks tickerguy for all the hard work!
Click to expand...

I am having the same issue with mine as well. It's not a big deal just need to turn off the radio and back on and it seems to work. I have noticed this also happening with WiFi as well. Strange thing is it only effects data as calls still come in, just no data.

Thanks again to TickerGuy & Isaac for all the hard work put forth, I for one appreciate it!!!! :D
 
g60madman said:
I am having the same issue with mine as well. It's not a big deal just need to turn off the radio and back on and it seems to work. I have noticed this also happening with WiFi as well. Strange thing is it only effects data as calls still come in, just no data.

Thanks again to TickerGuy & Isaac for all the hard work put forth, I for one appreciate it!!!! :D
Click to expand...

Other people said they have the same issue also, I wonder if a simple script could be added to toggle data off and back on when we wake the phone up?
 
Do I need to flash GAPPS if I just flash the new build over the previous build? I thought not, but I've been getting a TON of FCs while using the Market.

Also, Tickerguy, I have a suggestion. If it's at all possible, it would be pretty slick if there was an option to use one of the volume keys to take pictures while using the camera.
 
frdmspoplr said:
Do I need to flash GAPPS if I just flash the new build over the previous build? I thought not, but I've been getting a TON of FCs while using the Market.

Also, Tickerguy, I have a suggestion. If it's at all possible, it would be pretty slick if there was an option to use one of the volume keys to take pictures while using the camera.
Click to expand...


Just toggle your camera, hit the menu button, and then hit advanced options. There are options for using Volume up/down, search button, etc to take pictures with.
 
Has anyone tried to overclock with the later builds? For me it seems to still work except it completely kills the front camera. Anyone played around with it? thanks!
 
celicarunner said:
Has anyone tried to overclock with the later builds? For me it seems to still work except it completely kills the front camera. Anyone played around with it? thanks!
Click to expand...
Yeah, the OC kernel conflicts with any of the builds past 9/25 I believe. It'll still work fine, it just isn't compatible with the FFC changes that were made.
 
celicarunner said:
Has anyone tried to overclock with the later builds? For me it seems to still work except it completely kills the front camera. Anyone played around with it? thanks!
Click to expand...

The current kernal that is in this forum for CM7 is out of date. It doesn't have ext4 from what I understand, which is why the front camera is broken when you try flashing it. Isaac mentioned somewhere that he has instructions to make an up to date kernal that supports ext4 if you want.

Edit** ^ you beat me to it lol.
 
This is an awesome rom! once the wifi/standby/lockup issue is fixed this will be awesome. For some reason wifi really makes my phone lock up more than with it off. with wifi on it reboots about once/hour. otherwise awesome.
 
bobloadmire said:
This is an awesome rom! once the wifi/standby/lockup issue is fixed this will be awesome. For some reason wifi really makes my phone lock up more than with it off. with wifi on it reboots about once/hour. otherwise awesome.
Click to expand...

Same here. I have to leave Wifi completely off at all times even when awake. As far as 3G goes, it works awesome!! Loving it so far :D
 
Wifi/standby lockup is a real bitch to find as I can't get a trace on where it's freezing, and one of the obvious places I looked wasn't responsible for it. I wouldn't hold my breath on that one.

Now if my makeshift faraday cage would work to reliably produce a data drop.....
 
1337sause said:
Great job, Tickerguy!

Has anyone managed to come up with a decent, optimized stock gingerbread launcher without the awful homescreen scrolling lag? Other than the laggy launcher and absence of haptic feedback on the soft keys, this build rocks! Thanks again!

Just out of curiosity, what's the issue regarding haptic feedback?
Click to expand...

In my experience with launchers on this phone, all of them except launcherpro feel laggy if you're using a live wallpaper no matter what ROM/kernel I use or changes I make, including cache clearing and reflashing.

Tickerguy, Isaac, I'm a csc major highly interested in ROM's/Android and I want to help on this ROM and others, how did you you get started and how would you recommend I get started other than googling ROM development?

Thanks for CM7 on my prepaid beast!
 
laidback7 said:
In my experience with launchers on this phone, all of them except launcherpro feel laggy if you're using a live wallpaper no matter what ROM/kernel I use or changes I make, including cache clearing and reflashing.

Tickerguy, Isaac, I'm a csc major highly interested in ROM's/Android and I want to help on this ROM and others, how did you you get started and how would you recommend I get started other than googling ROM development?

Thanks for CM7 on my prepaid beast!
Click to expand...

i reccomend downloading a rom and tering it apart to see what its made up of... then tweak it a little flash it. then once you get a basic understanding, dig deeper. for example, start theming a rom, then add tweaks, and so on. (thats how i learned :D)
 
tickerguy said:
Wifi/standby lockup is a real bitch to find as I can't get a trace on where it's freezing, and one of the obvious places I looked wasn't responsible for it. I wouldn't hold my breath on that one.

Now if my makeshift faraday cage would work to reliably produce a data drop.....
Click to expand...
That sucks, because IMO that is the only thing keep this ROM from being an RC if not full release. Wish I could help you out further, but all i know are the symptoms.
 
ziggy46 said:
i reccomend downloading a rom and tering it apart to see what its made up of... then tweak it a little flash it. then once you get a basic understanding, dig deeper. for example, start theming a rom, then add tweaks, and so on. (thats how i learned :D)
Click to expand...

Preciate it ziggy, when you say "tear apart" does that mean editing the source code? I have 2+ years experience coding in java, c/c++, php, and sql, but what do I use to open/edit/compile files in a ROM; for ex: .ogg, metadata, or should I be tearing apart something else?

Is there a better forum/chat to ask you this? Or can I send you my email? I won't bother you long, just wanted to a know enough to start.
Thanks for your time!
 
bobloadmire said:
That sucks, because IMO that is the only thing keep this ROM from being an RC if not full release. Wish I could help you out further, but all i know are the symptoms.
Click to expand...


Same here, I wish it worked better, TG is doing a GREAT job, and I keep trying the new builds out, but I keep going back to stock because of WiFi
 
Google Latitude can't automatically check me in to places with the wifi standby bug (because it can't even get my course location without it), which kinda sucks. Good luck squashing that one.
 
Hey Ticker, not trying to pester you. I was wondering.... is hdmi not fixable...? is it going to be looked at...? Keep up the great work. still wishing you would let me donate some cash for your troubles.... ;-P
 
I don't know on HDMI yet. It's on the list, but not on the top of the list. One of the users here did send me a cable, so I have one.

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, even if I sleep the phone manually with the power button. It doesn't die. But off charge, if I don't tell the Wifi driver to go to sleep, it does very reliably blow up. This problem may have been fixed by Motorola but not pushed into their repository before they released their "open source" kernel. If so it's going to be a real bitch to find as I have to be able to replicate it in a way that gives me a backtrace before I can squash it. I have a suspicion that the kernel is hanging in the device driver; if it's in the .ko loadable file it's BAD as we don't have source to that. If it's in the kernel itself (e.g. a deadlock between two mutexes) it can be fixed but finding it is another matter since 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.)

The other problem - the data drop issue - is different. That looks like a CM7 problem. What I want is a trace of the RIL when it actually loses the connection, but I haven't been able to provoke that as of yet. I did manage to provoke a data lockup late this afternoon but unfortunately I couldn't find a "hook" (some set of conditions I can test) and I wasn't cabled when it died. I've got some ideas in this regard but I don't know if they'll work and I'm not all that enamored with the idea of simply shooting blind in the code here as recycling the data connection (which is all you need to do) is trivial but breaks active connections - so if you do it when it's unnecessary you get bad results.

There is also an occasional problem where the phone goes into "Searching" mode and never comes out. That requires an airplane mode cycle. I have not been able to reliably provoke that state, unfortunately, and that one is DEFINITELY in the radio code (not in CM7) - and toggling there is likely a really bad idea. Note that this problem is one that shows up in the stock code as well - I had it happen a couple of times on Froyo. This problem is one that is unlikely to be fixed except by new radio code out of Motorola, but it's also relatively rare.
 
laidback7 said:
Preciate it ziggy, when you say "tear apart" does that mean editing the source code? I have 2+ years experience coding in java, c/c++, php, and sql, but what do I use to open/edit/compile files in a ROM; for ex: .ogg, metadata, or should I be tearing apart something else?

Is there a better forum/chat to ask you this? Or can I send you my email? I won't bother you long, just wanted to a know enough to start.
Thanks for your time!
Click to expand...

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: http://sourceforge.net/motorola/triumphwx435/home/Home/
 
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.
 
You must log in or register to reply here.
Back
Top Bottom