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

Root CM 7.0 Nightlies

ok, flashed build #8 and can't get USB to connect to transfer files. It just flashed the screen then back to home...not sure what's going on with that...also can't find USB debugging settings

Other than that, this is slick! (and the Honeybread theme makes it look that much sweeter)
Maybe it's that "sweet" Honeybread theme that's screwing up USB ... cause no problemo here.
 
Upvote 0
I'm using ExpertOnTech's (aka Winner00) build - he has the correct libaudiopolicy.so file to make DSP manager work, among other things. His is a pull and compile of the same exact code that CM7 uses, but his builds are usually after the build bots, so they have more up-to-the-minute commits, and he even helps test out items that have not actually been approved (committed) in his builds.

Fantastic overall.
 
Upvote 0
Yea but, having to go into recovery every time you want to get into your sdcard sucks.


Yesindeedy! But, for now, it's worth the hassle to get this stellar battery life I'm getting! Hopefully it will fix for me in build 9 that should be available toni...oh, wait... :)

On a side note, I successfully flashed RC1 for CM7...on my wife's Desire. Dare to dream, Droid 1. Dare to dream.
 
Upvote 0
Does anyone have any issues witht SetCPU showing "SetCPU has been granted SU permissions" or something like that when they open up SetCPU after some time? It doesn't happen all the time, but maybe every few hours, I'll hit the SetCPU widget I have on my home screen just to check, and it'll get the pop up saying it was granted permission.

Does this mean that it loses its rights to SU after some time, and had I not simply opened the app again to check, it would have remained at stock settings? I'm not talking restarting the phone, this is just waking it up after an hour or so.

The widget says 800/125, the way I want it to be, but after waking the phone up again after some time, it'll say 125/125, my screen off setting. And never change again.
 
Upvote 0
I have the nightlys. How come I am not getting a notification when I get emails?

Using which app? Gmail, stock Email, K9, etc? I get notifications for both K9 and Gmail no problem, don't use the stock email so couldn't tell ya. If it's Gmail, make sure you have the account setup to sync under Settings>Account>Google. Everything else, make sure notification settings are correct.
 
Upvote 0
Using which app? Gmail, stock Email, K9, etc? I get notifications for both K9 and Gmail no problem, don't use the stock email so couldn't tell ya. If it's Gmail, make sure you have the account setup to sync under Settings>Account>Google. Everything else, make sure notification settings are correct.

Thanks.

Gmail. From the market. The weird thing is the wifes droid (same set up) is doing it as well.
 
Upvote 0
Does anyone have any issues witht SetCPU showing "SetCPU has been granted SU permissions" or something like that when they open up SetCPU after some time? It doesn't happen all the time, but maybe every few hours, I'll hit the SetCPU widget I have on my home screen just to check, and it'll get the pop up saying it was granted permission.

Does this mean that it loses its rights to SU after some time, and had I not simply opened the app again to check, it would have remained at stock settings? I'm not talking restarting the phone, this is just waking it up after an hour or so.

The widget says 800/125, the way I want it to be, but after waking the phone up again after some time, it'll say 125/125, my screen off setting. And never change again.

Or it means the app has been permanently killed by Gingerbread, b/c SetCPU always asks for root privileges when it starts up.

That's one thing that is both pleasing to some and annoying to others - the fact that GB aggressively kills apps more so than previous Android versions.

As to the widget - I think there was an update in the market very very recently that was supposed to fix the issues with using the widget on GB - for the same reason, actually. Since the CM nightlies contain a built in CPU manager, I stopped (as of a few days ago_ using SetCPU altogether.

You might need to kill and restart SetCPU / remove & re-add the widget / clear data & re-set up SetCPU if you already have the latest version. I recommend the last step particularly if you restored your settings from a backup - try setting it all up again fresh.
 
Upvote 0
If I remember correctly, it was also an issue with FroYo as well. But I'll try that.

Would using the internal governor, usually found in the ROM settings, fix the issue of asking for root access every time? It won't be using SetCPU, but wouldn't it automatically get root access when starting up because it's built in to the ROM?
 
Upvote 0
That's one thing that is both pleasing to some and annoying to others - the fact that GB aggressively kills apps more so than previous Android versions.
I'd fall into the "annoyed" category, myself. It would be nice if I saw better battery life on GB ROMs vs Froyo, but thus far, this hasn't been the case. For the same reason I don't use task-killers, I see little benefit in a more aggressive native manager.

Instead, it seems to shut down apps that I actually want running in the background, such as PowerAmp, almost defeating the purpose of multitasking.
 
Upvote 0
I'd fall into the "annoyed" category, myself. It would be nice if I saw better battery life on GB ROMs vs Froyo, but thus far, this hasn't been the case. For the same reason I don't use task-killers, I see little benefit in a more aggressive native manager.

Instead, it seems to shut down apps that I actually want running in the background, such as PowerAmp, almost defeating the purpose of multitasking.

Well put. I'm noticing that Pandora is getting shut down once-in-awhile. And like you, I've yet to see the benefit of it as far as battery life is concerned.
 
Upvote 0
If I remember correctly, it was also an issue with FroYo as well. But I'll try that.

Would using the internal governor, usually found in the ROM settings, fix the issue of asking for root access every time? It won't be using SetCPU, but wouldn't it automatically get root access when starting up because it's built in to the ROM?

Absolutely. I just made the switch myself to using the internal CPU governor only, and I have just that extra little bit of RAM that SetCPU used to be using in the background - but I've also noticed that most of my half-second lags on the homescreen are gone.

Surprising how much difference only a few MB free can make.

I'd fall into the "annoyed" category, myself. It would be nice if I saw better battery life on GB ROMs vs Froyo, but thus far, this hasn't been the case. For the same reason I don't use task-killers, I see little benefit in a more aggressive native manager.

Instead, it seems to shut down apps that I actually want running in the background, such as PowerAmp, almost defeating the purpose of multitasking.

I'm with you regarding the battery life. I haven't seen an increase *too* much with regular use.

Idle battery time is a whoppingly different story though. before I enabled my Twitter and FB widgets again, I could easily get well over a day of standby time with the battery having more than 30% left.

Well put. I'm noticing that Pandora is getting shut down once-in-awhile. And like you, I've yet to see the benefit of it as far as battery life is concerned.

Odd. I haven' had Pandora die on me yet. At least, not that I can recall.
 
  • Like
Reactions: coonster
Upvote 0
Not having multitasking ability has me still using Froyo. Can't do two things at once. Heck, on Froyo I can do Nav, listen to music and wifi tether all at once. I can't even do two at once on GB.

Is it just me or has the problem seem to have gotten worse since build #8? I rely heavily on Setting Profiles and it's being killed repeatedly, same for MixZing.


Do you guys have "Lock Home In Memory" checked in the Performance Settings menu under CyanogenMod Settings?

I had it checked and I just tested playing music and using Nav at the same time, and I couldn't do both simultaneously.

I unchecked "Lock Home In Memory" and now I am able to multitask successfully, but I get a somewhat lengthy redraw when returning to the home screen after doing anything RAM intensive.

So if you do have your home screens locked in memory, try disabling that feature and see if you can multitask (and/or deal with the redraws).
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones