• 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

Some news on the Wifi lock stuff.

It's NOT locking the kernel entirely. This is a very useful piece of information. While working on it this evening I managed to get it into the locked state when a SMS came in. That wasn't particularly unique, but that the LED continued to flash was of great importance - the kernel has to be running for that to happen, as the PWM "soft glow" is actually done in the kernel - it's not in the hardware.

It's not a breakthrough but it answers an important question - the kernel is not locking up with interrupts disabled, which was my original belief. Whether this will ultimately lead me to be able to fix it, however, is unknown.
 
tickerguy said:
Some news on the Wifi lock stuff.

It's NOT locking the kernel entirely. This is a very useful piece of information. While working on it this evening I managed to get it into the locked state when a SMS came in. That wasn't particularly unique, but that the LED continued to flash was of great importance - the kernel has to be running for that to happen, as the PWM "soft glow" is actually done in the kernel - it's not in the hardware.

It's not a breakthrough but it answers an important question - the kernel is not locking up with interrupts disabled, which was my original belief. Whether this will ultimately lead me to be able to fix it, however, is unknown.
Click to expand...

you never cease to amaze me. you guys always find a way to figure problems out so quickly and fix with in a few days.:cool:
 
I'm not betting on being able to fix this one at this point in time.

A couple of things I've tried have been dead ends, and I'm mostly shooting entirely in the dark here, because I can't get a trace on what it was doing before it locked up - so I don't really know where I'm aiming.

This is a rough one. Most of the others are in the category of "you can track this down"; this is not necessarily in that group. If I could get it to lock up when it was connected to USB power I'd be a happy kid, but thus far I can't get it to misbehave when it's on the debugger.
 
tickerguy said:
I'm not betting on being able to fix this one at this point in time.

A couple of things I've tried have been dead ends, and I'm mostly shooting entirely in the dark here, because I can't get a trace on what it was doing before it locked up - so I don't really know where I'm aiming.

This is a rough one. Most of the others are in the category of "you can track this down"; this is not necessarily in that group. If I could get it to lock up when it was connected to USB power I'd be a happy kid, but thus far I can't get it to misbehave when it's on the debugger.
Click to expand...
Try using alogcat... you wont have to be connected to usb to get the info you need. Just set the app up so that it saves the log as it happens to your sdcard. So you wont lose it if you shut down
 
tickerguy said:
I'm not betting on being able to fix this one at this point in time.

A couple of things I've tried have been dead ends, and I'm mostly shooting entirely in the dark here, because I can't get a trace on what it was doing before it locked up - so I don't really know where I'm aiming.

This is a rough one. Most of the others are in the category of "you can track this down"; this is not necessarily in that group. If I could get it to lock up when it was connected to USB power I'd be a happy kid, but thus far I can't get it to misbehave when it's on the debugger.
Click to expand...

Not sure if you have read up on the MIUI thread but djboi2011 found that the "advanced wifi lock (free)" app in the market actually fixes the wifi lockups. I undid your "deep sleep" fix (changed the value of gEnableSuspend=2 back to gEnableSuspend=3 in qcom_cfg.ini) and installed that app and I went all day with wifi on without a single lockup. I uninstalled the app and got a lockup the first time it went to sleep. I haven't tested it on CM7 but I can't think of a reason of why it wouldn't work on CM7 as well.
I imagine the app is preventing WIFI (or perhaps the phone in general? - though the screen still sleeps) from sleeping in any way which may be what is locking up the phone. Perhaps if you contacted the developer to see what exactly it does, it could narrow down where the problem could be.
 
dsspain said:
After three reboots using os monitor
tTorrent running did bring the cpu to as high as 74% near startup
however, it does not appear to be a memory leak
the memory never dropped below 120 mb
the cpu did average about 47% total(system and apps)
i did not monitor the temp, which is possible i guess
will check that next, but the phone didn't feel warm at all
and that was on 3g not wifi
also the longest it took to get the reboot was 32 minutes
Click to expand...

The Triumph doesn't have a CPU temp sensor so I couldn't test and see if it was overheating before reboot, so without being able to hook it to a computer, I guess that's it for me. And by the way, reboots 100% of the time within one hour of starting tTorrent and usually within 30 minutes, and the memory stayed at 120mb, and CPU averaged about 46% in 25 tests,
 
metalman1884 said:
From my experience the SMS and the MMS (like picture and audio) works perfect. It's the SMS converted into MMS (due to the text being too long) that i have had issues with. I've sent a few out but the person never got them. So in messaging settings I checked "SMS split" and also "Split counter" (just in case) and they received it right away.

Seems like there's still a little problem with MMS texts to me
Click to expand...

ah, okay, this is why I thought my MMS was not working. It was not sending MMS text messages. I guess I'll have to enable split and send a bunch of messages. worked fine on stock. oh well =/
 
Okay, I had the whole battery issue too. My phone turned off at 52% due to low battery. It was exactly at 52% when I flashed the Beta (10/22), I was coming from the Alpha (10/16). I did a full wipe and clear cache.

Do you think this was the move from Alpha to Beta or would it have happened with any of the updates? I suppose each time I put on a new build I will make sure it is fully charged, Do the full wipe, cache then the battery stats.
 
septembersrain said:
Okay, I had the whole battery issue too. My phone turned off at 52% due to low battery. It was exactly at 52% when I flashed the Beta (10/22), I was coming from the Alpha (10/16). I did a full wipe and clear cache.

Do you think this was the move from Alpha to Beta or would it have happened with any of the updates? I suppose each time I put on a new build I will make sure it is fully charged, Do the full wipe, cache then the battery stats.
Click to expand...

If you cleared battery stats moving from alpha to beta, and it was at 52%, I would guess that's why it's doing that. Reset battery stats when at 100%...and no need to reset battery stats every time flashing new rom.
 
I have been watching this thread since almost the beginning, and just installed Tickerguys ROM yesterday, as the 10/22 build was the first one I thought I could use as a daily build. I must say, I LOVE it!

In the previous page, I noticed that NewUser0 had issues with MMS, and I have to report I do as well. It may be just my phone, and I'll be reinstalling the ROM for a second time when I get home, I can receive MMS and send SMS, but I cannot send MMS messages. I believe I did all the steps correctly to install, and yes I did reset the phone to defaults before installing.


NewUser0 said:
is mms supposed to be working on cm7 now or no? I'm a little confused, i thought it wasn't but I don't see it on the not working list. Out going mms are not working for my phone currently. If not, then i'll continue to patiently wait, but i wasn't sure if it has already been fixed and it's just my phone and i should be looking into fixing it or not.

It was recently fixed for muiu, i don't know if that fix can be applied to cm7 or not? i know some of the fixes have been able to be applied in both directions.
Click to expand...
 
tickerguy said:
Zig an android trace does me no good - I need a KERNEL trace.
Click to expand...

Is this what you're looking for?

In the terminal emulator:
$su
#cat /proc/kmsg > /sdcard/kmsg.txt

As long as you leave the terminal emulator open it updates kmsg.txt. It worked when I tried it, but since I don't know how to interpret it I don't know if it will help.

Good luck and thanks for all you've done so far!
 
cubmoney said:
If you cleared battery stats moving from alpha to beta, and it was at 52%, I would guess that's why it's doing that. Reset battery stats when at 100%...and no need to reset battery stats every time flashing new rom.
Click to expand...

I did not clear my battery stats when I was at the 52%. I just did a Factory Restore and Cache wipe. I had never done the clearing of battery stats on this phone prior to the one I just did this morning.

Though I do think that now that I've cleared the stats at 100%, I likely won't have a problem when putting on a new update.
 
wsimon said:
I undid your "deep sleep" fix (changed the value of gEnableSuspend=2 back to gEnableSuspend=3 in qcom_cfg.ini) and installed that app and I went all day with wifi on without a single lockup.
Click to expand...


Where is this "Deep sleep" located? And how do you change it?
 
idbl_fanatic said:
Where is this "Deep sleep" located? And how do you change it?
Click to expand...

See -> http://androidforums.com/triumph-all-things-root/423184-rom-port-miui-1-10-14-triumph-10232011-2-gb-2-3-5-based-15.html#post3368195

Basically with ES File Explorer and with System mounted in its options. Open /system/etc/firmware/wlan/qcom_cfg.ini and change the line gEnableSuspend=2 to gEnableSuspend=3. Then save and reboot the phone. This undoes TickerGuys fix to the WiFi lockups which causes WiFi to disconnect and sleep every time the phone sleeps.
 
wsimon said:
Not sure if you have read up on the MIUI thread but djboi2011 found that the "advanced wifi lock (free)" app in the market actually fixes the wifi lockups. I undid your "deep sleep" fix (changed the value of gEnableSuspend=2 back to gEnableSuspend=3 in qcom_cfg.ini) and installed that app and I went all day with wifi on without a single lockup. I uninstalled the app and got a lockup the first time it went to sleep. I haven't tested it on CM7 but I can't think of a reason of why it wouldn't work on CM7 as well.
I imagine the app is preventing WIFI (or perhaps the phone in general? - though the screen still sleeps) from sleeping in any way which may be what is locking up the phone. Perhaps if you contacted the developer to see what exactly it does, it could narrow down where the problem could be.
Click to expand...
Confirmed. This app works for me as well. Setup gEnableSuspend=3 and set up the Advanced Wifi Lock app, and bob's your uncle.
 
wsimon said:
Not sure if you have read up on the MIUI thread but djboi2011 found that the "advanced wifi lock (free)" app in the market actually fixes the wifi lockups. I undid your "deep sleep" fix (changed the value of gEnableSuspend=2 back to gEnableSuspend=3 in qcom_cfg.ini) and installed that app and I went all day with wifi on without a single lockup. I uninstalled the app and got a lockup the first time it went to sleep. I haven't tested it on CM7 but I can't think of a reason of why it wouldn't work on CM7 as well.
I imagine the app is preventing WIFI (or perhaps the phone in general? - though the screen still sleeps) from sleeping in any way which may be what is locking up the phone. Perhaps if you contacted the developer to see what exactly it does, it could narrow down where the problem could be.
Click to expand...

You rock, sir!
 
This isn't a valid solution! The app keeps a wake lock, which keeps the phone from entering a wake state and hence doesn't put the Wifi to sleep. Yes it technically works, but now your phone isn't sleeping when the screen shuts off at all and you will have a huge battery drain!
 
PsyberS said:
This isn't a valid solution! The app keeps a wake lock, which keeps the phone from entering a wake state and hence doesn't put the Wifi to sleep. Yes it technically works, but now your phone isn't sleeping when the screen shuts off at all and you will have a huge battery drain!
Click to expand...
doesn't seem to be draining any more than stock rom.
 
Sorry in advance if this has already been asked but I've been searching and can't find an answer. When I start up CWM I get the following messages:

E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log


Then when I try to install cyanogenmod I get these messages:
Finding update package...
Opening update package...
E:Can't open /sdcard/update-cm-7.1.0-TG-0.3-Beta-Triumph-signed.zip
(bad)
Installation aborted.

Can anyone help me or know why it's doing this? Thanks
 
You must log in or register to reply here.
Back
Top Bottom