• 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

Thinking Tickerguy should be renamed Rockguy cause he seriously Rocks. Can’t express my gratitude enough in words. Guess that means I should make a donation. Seriously though, you have saved me much embarrassment as my office is overridden with snooty ars iphone users who thought it was funny to pock fun at the guy with the Android phone who is constantly tapping his screen because he is unsure if his lagging or his selections had not registered at all. Well the joke is now been flipped as this crapy ars Android Phone is putting their iclones to shame and at the same time running circles around the 2 other Android phones at the office that have duel core processors. Amazing how you have outdone Moto/Virgin without any of the recourses backing either one. Can’t help but wonder if they are either complete morons or just didn’t care assuming their users wouldn’t notice the difference.
 
marx2k said:
- When I unlock the screen (I turned off off/on animations due to glitchiness), I will see my normal android desktop and then it goes into the screen lock
Click to expand...

Not an issue with the 10/26 build. I think it probably had something to do with the deep sleep setting used in the earlier builds to prevent wifi from locking up
 
Hey guys, any of you experiencing a bug where the icons have to constantly redraw themselves on the desktop whenever you switch to it from an app? Once the icons redraw the desktop runs OK but it happens almost all of the time and the redraw process is slow. I thought that maybe it was GoLauncher but it's also doing it with stock ADW Launcher.

Thanks for any tips.
 
Prey521 said:
Hey guys, any of you experiencing a bug where the icons have to constantly redraw themselves on the desktop whenever you switch to it from an app? Once the icons redraw the desktop runs OK but it happens almost all of the time and the redraw process is slow. I thought that maybe it was GoLauncher but it's also doing it with stock ADW Launcher.

Thanks for any tips.
Click to expand...

Try going into CyanogenMod settings/performance and select "Lock home in memory"
 
Prey521 said:
Hey guys, any of you experiencing a bug where the icons have to constantly redraw themselves on the desktop whenever you switch to it from an app? Once the icons redraw the desktop runs OK but it happens almost all of the time and the redraw process is slow. I thought that maybe it was GoLauncher but it's also doing it with stock ADW Launcher.

Thanks for any tips.
Click to expand...

This is because Android is unloading the launcher from memory, so you see it re-loading it when you go back. As shimdachef mentioned, CM7 has a setting to lock it in memory so that won't happen.
 
I think I found the problem...in the GoLauncher Settings, I disabled "System Persistent" which they make note is experimental....now it's back to normal and running smooooooooooooth!
 
I'm using the ice cream sandwich launcher along with the ics cm7 theme and it's awesome! Both can be downloaded from the market..
 
mpness said:
I too have random reboots from waking as well as the desktop (or whatever app I was using) before the lockscreen comes up.
I also have had issues with people not understanding me, I thought it was virgin's service but on second thought I don't think so.
Click to expand...

Yes, it seems to have happened immediately after I switched from the stock rom. It seems like my voice is cutting out to people I'm calling or are calling me.

The random reboots from waking will probably be less of an issue with this new update on the 26th. We'll see in the next few days how this update behaves.

I am somewhat concerned about the call quality issues. Tickerguy, do you know if something like that is even controlled by the rom itself? Is it possible that switching from stock to CM7 can degrade voice calls?
 
Fixing a bunch of Github oddities this evening.....

Incidentally, if you use that place I strongly recommend you always pull whatever project manifest you're using into a CLEAN directory and make damn sure it builds before you do anything that might damage your local copy.

If you don't, and run into what I just ran into..... well, you're going to be pissed. Let's just say that there were several instances of things that I committed and pushed and were not there.

A good bit of time has been spent this evening cleaning that up.... hopefully what I have pulled down (now) builds cleanly - we'll see.

I have had zero call quality issues and I am on the phone a lot. If you have the CPU cranked down stop doing that!
 
Is there a known issue with CM7 connecting to hidden SSID networks? I notice it will not connect to a hidden wireless network. I checked the first post and also the github and nothing is listed. I found some info over at XDA that said it's a known issue. Just checking.
 
I'm also getting the dialer drain on beta3. 49% drain is dialer, 49% is Android system, and 3% is phone idle. Android is bad at math.

Updating to beta4 now. Thanks again Tickerguy. :D
 
g60madman said:
Is there a known issue with CM7 connecting to hidden SSID networks? I notice it will not connect to a hidden wireless network. I checked the first post and also the github and nothing is listed. I found some info over at XDA that said it's a known issue. Just checking.
Click to expand...

+1 on this hidden ssid issue(?) :/

*** btw this is my first time installing a ROM. yey! lolz
 
do you think you can re-enable the option to keep home in memory again please? im using launcherpro and anytime i open an app then go back to the launcher it has to load up all the widgets and apps again. i had the keep home in memory checked in previous builds and it worked fine, but in the newer builds even though i have it checked it almost never stays open. i wouldn't mind it using a little ram since i don't really have many applications running in the background so i always have about 100 to 130 mb ram free.
 
can anyone explain this wifi lock thing to me more? I've noticed since I updated to beta4 that my wifi no longer shuts off when the screen is off as its supposed to with juice defender but it no longer does. Won't this drain my battery faster?
 
portezbie said:
can anyone explain this wifi lock thing to me more? I've noticed since I updated to beta4 that my wifi no longer shuts off when the screen is off as its supposed to with juice defender but it no longer does. Won't this drain my battery faster?
Click to expand...


I have no problems with juice defender managing my WiFi on beta4. Juice defender usually monitors traffic before disconnecting data. Maybe that, maybe another setting you have on the app or elsewhere.
 
Is haptic feedback going to be fixed? Should vibration on notifications be working? The progress is amazing, but I always have my phone on vibrate only but I can't do that now, so I end up missing any notifications.
 
aricblunk said:
Is haptic feedback going to be fixed? Should vibration on notifications be working? The progress is amazing, but I always have my phone on vibrate only but I can't do that now, so I end up missing any notifications.
Click to expand...

The vibration on notifications has been working for quite a while now. Mine works fine under B4. I would double check all your settings first and if those are ok, reinstall CM7.

Haptic feedback works for everything except the soft keys. Tickerguy hasn't really said if he was going to work on those any time soon, but I would imagine they aren't much of a priority right now.
 
OGWillikers said:
I'm also getting the dialer drain on beta3. 49% drain is dialer, 49% is Android system, and 3% is phone idle.
Click to expand...

I've also been seeing strange battery stats with all of the beta builds. Initially I assumed it was probably due to my not doing a full wipe/reset for a few builds, but for the latest beta I wiped everything and restored my apps with Titanium Backup, and I am still getting very strange battery stats.

Dialer is the biggest issue- once I make or receive a call, it immediately jumps to or near the top of the list. And even if I don't make another call for the rest of the day, it seems to stick right at that same percentage. Note that on previous builds, Dialer never used much battery. Typically "Voice Call" is where you'd see the drain if you were making calls, but I don't think voice call is even showing up at all anymore.

I've also noticed some other weird behavior. For one, some (maybe all?) apps are not being listed in the battery stats. I played games for an hour or two last night, but none of those apps were listed in my batter usage stats at all. I've also had other apps besides Dialer show weird stats. AlarmDroid has occasionally shown similar behavior to what Dialer is doing above.

Long story short, I do think there is some kind of issue going on here, and there seem to be at least several of us with this problem.
 
g60madman said:
Is there a known issue with CM7 connecting to hidden SSID networks? I notice it will not connect to a hidden wireless network. I checked the first post and also the github and nothing is listed. I found some info over at XDA that said it's a known issue. Just checking.
Click to expand...

Yep, I've also read it's a known issue and have not read of any successful workarounds so far. One suggestion people have given was using an app called "Hidden SSID Enabler".

The app has done nothing for me.
 
You must log in or register to reply here.
Back
Top Bottom