I have the OG Droid running 7.1. I like the ROM in general, but the phone has some problems... I don't really get text or email notifications, I loose I data connection every once in a while, the phone freezes when locked (can't unlock and can't answer a call), plus a few others.
I am wondering if a downgrade to 7.0.3 will help out at all (if so, is there anything special I need to know before downgrading, or can I just use ROM Manager to do it)? Or would I be better off just getting rid of most of my apps (most are on the SD card for storage reasons).
I am only keeping this phone until the Galaxy Nexus is released (so hopefully not too much longer), but in the last week it has become almost unusable.
Does anyone have any suggestions to get me through another week or two?
Thanks for the help!
Welcome to CyanogenMod
 |
Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
|
Guest Message by DevFuse
1
1 reply to this topic
#1
tberman333
-
- Members
- 2 posts
- Device Model:Droid
- MOD Version:7.0.3
- Recovery Image:ClockworkMod
Posted 01 December 2011 - 07:57 PM
#2
dwoid
-
- Members
- 5 posts
- Twitter:none
-
Country:
- Device Model:Droid 1
- MOD Version:CM
- Recovery Image:ClockworkMod
Posted 06 December 2011 - 02:47 AM
I've got a Droid1 and had pretty much the same issues. Everyone's Droids are configured differently -- I have pretty much maxed mine out with lots and lots of apps (around 145) and a lot of customizations, enough that 7.1 just wouldn't run reliably. I downgraded to 7.0.3 and have been very satisfied with its stability and performance since then, with the following caveats:
1) You cannot run live wallpapers -- there just isn't enough memory on the box to try to keep them and other important services running at the same time. This makes a HUGE difference in performance, and really puts into question the use of live wallpapers in general, except on platforms that have lots of CPU and lots of memory resources (ie: a few phones and many pads).
2) Messaging *has* to go into reserved memory. Otherwise you won't get text message notifications. I also put my launcher in reserved memory because I don't like to wait for it to re-catalog applications (did I mention I have lots of apps?).
3) I have removed (moved to a non-executable location) ADW from the CM7 ROM, replacing it in ROM (/system/apps) with my preferred GO Launcher. Probably not a huge performance difference, but having both ADW and GO Launcher in ROM was a waste of space since I wasn't using ADW at all. While in this process I have also similarly removed a few other apps that were in the ROM that I was never going to use, and have moved a few apps that were in ROM to SD because I very rarely use them.
4) Email notifications are still not totally reliable with my work Exchange server. I'm not sure if that's due to CM7 or due to an Exchange upgrade at work, but it's noticeable. (Interestingly, my Honeycomb pad does get all notifications ok.) Notifications for my personal email are pretty reliable. It would have been nice to have an option for Email in reserved memory to make sure it stays active and ready, but it's logical that it isn't an option because there are a number of Email clients to choose from. Of the two (Email and Messaging), I'd personally much rather have reliable notifications of text messages.
5) SetCPU and CM7 don't seem to cooperate very well. I use SetCPU because I like having profiles, but I don't get the impression CM7.0.3's CPU overclocking controls -- even when not turned on at boot time -- release control to SetCPU, I'll often find SetCPU running a profile that should have changed and didn't. CM7.1 did the same thing. I am running a custom kernel (Chevy), but it has been extremely reliable and I don't see it as being the source of this problem.
6) Even with a heavily loaded Droid1, the camera seems to work well under CM7.0.3, as does blue tooth and tethering. I had trouble with all of these under CM7.1.
7) I do still get an unexpected re-boot every once in a while. Not often, and not predictably, but it just happens. In general, I find CM7 to be not quite as reliable as Froyo was, however it does do more in a lot of ways. The only Froyo feature that I'm doing without under CM7.0.3 is live wallpapers (which do run, but they slow the device down a lot, lower battery life and add heat, and they get switched out of memory and stop running). But CM7.0.3 gives me a lot of other added features, so I'm willing to trade off.
For me, I'm happy enough with CM7.0.3 that I'm probably going to keep my Droid1s (I have two of them) running it for the rest of their lifetimes. If CM ICS comes out for the Droid1, I may try it, but I'm not expecting it to be more reliable than CM7.0.3 at this point in time.
[edited for spelllling]
1) You cannot run live wallpapers -- there just isn't enough memory on the box to try to keep them and other important services running at the same time. This makes a HUGE difference in performance, and really puts into question the use of live wallpapers in general, except on platforms that have lots of CPU and lots of memory resources (ie: a few phones and many pads).
2) Messaging *has* to go into reserved memory. Otherwise you won't get text message notifications. I also put my launcher in reserved memory because I don't like to wait for it to re-catalog applications (did I mention I have lots of apps?).
3) I have removed (moved to a non-executable location) ADW from the CM7 ROM, replacing it in ROM (/system/apps) with my preferred GO Launcher. Probably not a huge performance difference, but having both ADW and GO Launcher in ROM was a waste of space since I wasn't using ADW at all. While in this process I have also similarly removed a few other apps that were in the ROM that I was never going to use, and have moved a few apps that were in ROM to SD because I very rarely use them.
4) Email notifications are still not totally reliable with my work Exchange server. I'm not sure if that's due to CM7 or due to an Exchange upgrade at work, but it's noticeable. (Interestingly, my Honeycomb pad does get all notifications ok.) Notifications for my personal email are pretty reliable. It would have been nice to have an option for Email in reserved memory to make sure it stays active and ready, but it's logical that it isn't an option because there are a number of Email clients to choose from. Of the two (Email and Messaging), I'd personally much rather have reliable notifications of text messages.
5) SetCPU and CM7 don't seem to cooperate very well. I use SetCPU because I like having profiles, but I don't get the impression CM7.0.3's CPU overclocking controls -- even when not turned on at boot time -- release control to SetCPU, I'll often find SetCPU running a profile that should have changed and didn't. CM7.1 did the same thing. I am running a custom kernel (Chevy), but it has been extremely reliable and I don't see it as being the source of this problem.
6) Even with a heavily loaded Droid1, the camera seems to work well under CM7.0.3, as does blue tooth and tethering. I had trouble with all of these under CM7.1.
7) I do still get an unexpected re-boot every once in a while. Not often, and not predictably, but it just happens. In general, I find CM7 to be not quite as reliable as Froyo was, however it does do more in a lot of ways. The only Froyo feature that I'm doing without under CM7.0.3 is live wallpapers (which do run, but they slow the device down a lot, lower battery life and add heat, and they get switched out of memory and stop running). But CM7.0.3 gives me a lot of other added features, so I'm willing to trade off.
For me, I'm happy enough with CM7.0.3 that I'm probably going to keep my Droid1s (I have two of them) running it for the rest of their lifetimes. If CM ICS comes out for the Droid1, I may try it, but I'm not expecting it to be more reliable than CM7.0.3 at this point in time.
[edited for spelllling]
Edited by dwoid, 06 December 2011 - 09:20 AM.
