I keep hoping that someone, somewhere tweaks the native task manager (or something) so that I can actually have widgets and use apps...
Kratos
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).
Ok, i'm on build #11 right now, and is anyone else's boot anim super slow compared to previous builds? I came from #6 to #11, so that might be the problem? I'm not super sure.
Yeah, we have a limited amount of RAM, and unfortunately, GB requires more active RAM to run, meaning we have less left over for us to use with our apps, multi-tasking and widgets. Unless someone is able to manage to put together a GB 'lite' edition, stripped of components but givig enough of the core of GB to us, I
seriously doubt Motorola will release this for the DROID.
Been running #11 now for about 12 hours, and so far, I'm liking what I'm seeing. The best battery life I've had in awhile, and I haven't noticed anything getting shut down prematurely or anything. Hhmmn... I hope its a good sign of things to come. *crossing fingers*
ExpertOnTech (aka winner00) just recently psted a new build of his - I'm hitting it up in a few minutes....
I do, and have since stock 2.2 when I purchased Launcher Pro. I haven't had ANY memory management issues since abandoning task killers months ago. The App Nazi feature only surfaced on #8 for me and again with #11. If it doesn't clear by the next build, I guess I'll try doing a full wipe. It's been awhile anyway.
Surprising. Most people do - but it also depends upon how much free RAM you have to play with in the first place....
The aggressive task manager on these new GB roms may force me to go back to froyo soon :/
I'll give the CM7 nightlies a few more builds...but if it doesn't get remedied soon Ill have to go back.
It's not going to get fixed overnight. Unless you're absolutely willing to deal with things like reboots. soft reboots, low memory issue, background app FCs and whatnot, I'd recommend that you stay away from GB ROMs.
Of course, having said that, I'm using CM7 (winner00's mod) as my daily driver
I have to stay on Froyo, at least for the time being. I have tried all of the GB ROMs and must say that CM7 and UD are my favorite, but even with changing heap size settings, compache, etc, I cannot reliably use any of them.
I was really bummed at first, but I figure, at least I have the next best thing. Besides, I like Frozen Yogurt better than Gingerbread anyways. I've never really been a big fan of the taste of Gingerbread (any style).
Kratos
I'm going through the same thing. CM 1.6.2 is the only stable ROM that i like. i think CM7 nightly's are not the best for daily use. i was on full-#8 and it reboot while i was talking to my boss and other time on my clients, which looks really unprofessional. so i wait till CM7 is stable for daily use. ~Cyanogen Mod all the way~
Yeah, if you phone is used for business, you really have no choice.
1.Is it possible to stop GB from killing SetCPU?
2.Setting the VM heap size to the max isn't necessarily the best thing, is it? How do you determine what the best setting is?
3. Does anyone compress memory? I think that's what it's called, but there's an option to do something like 15% and then some other options. Just trying to make minor tweaks here and there to compensate for some of GB's quirks.
I debated going back to 6.1.2 because GB really is no different for me than FroYo. Thing is, the Market I use to download certain apps is down. I guess I could TiBU it.
Well, yes and no.
Yes if you have absolutely no other apps running taking up background memory - and I mean
none - no apps, no widgets, no swype, etc.
Otherwise, if SetCPU is running in the background, and you call up an app that needs RAM now, it is gonna kill to allow you to run the app.
However, CM7 nightlies have their own CPU governor - so unles you use profiles, there really is no need to even use SetCPU in the first place.
I restored build #6 and all is well again. All of my widgets and music stay running while multitasking. I'll wait a few builds and see if they get it fixed. That was very frustrating.
It's going to be hard to fix it - the GB core services use a lot more RAM initially than the FRoYo core services do - unless they can get that trimmed down, this is always going to be a factor on GB on the DROID and its limited RAM.
I notice keyboard errors with Swype on this (#12), if I click a word to replace it with something else the copy/paste dialog box pops up like I had held it down which then locks Swype from exiting the edit select dialog. Its not an issue because you can still click the swype key whilst inside a word and it will allow you to replace it. Seems like the timer for how long you actually held down something for the edit box was heavily reduced.
That is the only issue I've had so far.
I've had the same issue for a few builds now, since winner00's 7-2 build (?)
Try it in landscape and see what happens - in mine, Swype popup box wins instead of the edit/cut/copy dialog box and I can fix the word.
I meant to check earlier to see if this had been reported yet or not - thanks for the reminder.