I notice that the phone app freezes occasionally when I make / receive calls. When this happens and I am receiving a phone call, the phone app automatically goes in to speaker phone mode and does not respond to any of my commands.
I had not faced this problem on stock 2.2 and I don't remember if I had this problem over the short period of time that I had CM 7.03.
I have searched the forums on multiple websites for an answer to my problem but I have not been able to find a solution.
Does anyone know why this might be happening or what I can do to rectify this?
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
Phone app freezes occasionally on CM 7.1
Started by ssomnath, Dec 11 2011 06:46 AM
phone app freeze motorola droid 7.1
9 replies to this topic
#1
Posted 11 December 2011 - 06:46 AM
#2
Posted 11 December 2011 - 07:23 AM
I found that my phone app was very clunky on 7.1 until I turned swapping on. I have Latitude, Mail and Facebook apps on my phone and the three of them like to keep running all the time taking up 60MB+ of the RAM. Whenever I tried to bring the phone app up it would take an age and dialling numbers was really slow and jumpy, once I gave the system 50MB of swap on the SD card the phone app and interface seemed to behave much more sensibly.
There is a topic about getting the best performance out of 7.1 on a Hero http://forum.cyanoge...535#entry272535 If you are having trouble it might be worth taking a look there (or if yours runs well share the secret with the rest of us!)
There is a topic about getting the best performance out of 7.1 on a Hero http://forum.cyanoge...535#entry272535 If you are having trouble it might be worth taking a look there (or if yours runs well share the secret with the rest of us!)
#3
Posted 12 December 2011 - 03:08 PM
TafT - Thank you for your suggestion. I am no expert on swap spaces etc on phones but from what I read it appears to make the everything on the phone faster. In my case it is just the phone app that is acting up. All my other apps work just fine despite having ~ 70 MB of RAM free (at most) at any given point of time. I have made little / no performance modifications (besides JIT) to stock CM 7.1. Any suggestions?
#4
Posted 14 December 2011 - 11:18 AM
I have not been using CM very long so I cannot make many suggestions. I would say that I found the stock 7.1 release to be very slow, I jumped ahead to a more recent daily build and that was much faster for me so you could try something similar. As with all flashes you should backup anything you do not want to loose but I found that I could go from stock 7.1 to a 7.1 daily without an erase of the current image, this meant all my Apps and data were still there when I booted.
Download daily + Google apps to SD (just as with standard update) -> Flash ROMs (no-erase step) -> Boot
No guarantees but it might help and you should be able to drop back to the official 7.1 release if you find a daily does not work for you. Remember that daily builds come with even less guardedly than a release build & if you are unlucky you will pick a broken one so you might need to try two of there (although mine worked first time).
Download daily + Google apps to SD (just as with standard update) -> Flash ROMs (no-erase step) -> Boot
No guarantees but it might help and you should be able to drop back to the official 7.1 release if you find a daily does not work for you. Remember that daily builds come with even less guardedly than a release build & if you are unlucky you will pick a broken one so you might need to try two of there (although mine worked first time).
#5
Posted 15 December 2011 - 09:33 PM
Just wanted to chime in with my experience with 7.1. As usual YMMV.
After months of complaining about CM7 and falling back to CM6 I have finally found *my* perfect combination where my D1 is finally happy with CM 7.1:
First, do look into downloading Swapper2 and setting up a swap PARTITION. First make sure to back up your SD card to your PC, format your SD card, then use ROM Manager to partition your SD card into SD-ext and swap space. I currently use 512 MB for ext3 and 64 MB for swap (previously had 128 but it was overkill). Move your SD card contents on the PC back to your main (FAT32) partition. Go into Swapper2 and set your swappiness to 10 as a starting point. I currently have it set to 15. From a lot of reading I have done 10 is optimal but no more than 20.
As for your SD-ext partition, look into using Link2SD and moving non-critical apps over to the ext3 partition. Move any apps on SD to internal THEN create the links. If your internal memory runs out while doing this simply do a quick reboot from Link2SD to regain the lost space.
Lastly, strongly consider Prime's deprimed kernel. I use #19 as #20 uses BFS (and thus high Android OS usage) and the latest test causes a lot of lagging. Take a look at this thread:
http://forum.cyanoge...-kernel-how-to/
I use the same 20overclock config as the OP with satisfactory results:
1100 MHz, 68
1000 MHz, 60
850 MHz, 58
700 MHz, 44
550 MHz, 40
400 MHz, 32
250 MHz, 28
I use the bumblebee governor for all except my failsafe profiles (conservative) and screen off is set to 550/250 as consistent with how bumblebee behaves. See the OP's own profiles for an idea.
If you go through the Droid Forums thread linked within, you'll find the link to #19 if you look hard enough (as deprimed_previous.zip). If you feel that #20 or the latest test works well then by all means go for it. Again, my D1 works best with #19 but it may not be the same for you.
Other performance settings:
- No compcache. It's nothing but a headache.
- JIT disabled. (Adds some memory back.)
- Surface dithering disabled.
- 16 Bit Transparency checked.
- Purging of assets checked.
- Lock home in memory disabled. (I use V6 Supercharger) See this thread:
http://forum.xda-dev...ad.php?t=991276
- VM Heap Size 40m (though I have it set to 32m in the settings). See this thread:
http://www.droidforu...build-prop.html
EDIT: Posted clock rate and vsel values.
After months of complaining about CM7 and falling back to CM6 I have finally found *my* perfect combination where my D1 is finally happy with CM 7.1:
First, do look into downloading Swapper2 and setting up a swap PARTITION. First make sure to back up your SD card to your PC, format your SD card, then use ROM Manager to partition your SD card into SD-ext and swap space. I currently use 512 MB for ext3 and 64 MB for swap (previously had 128 but it was overkill). Move your SD card contents on the PC back to your main (FAT32) partition. Go into Swapper2 and set your swappiness to 10 as a starting point. I currently have it set to 15. From a lot of reading I have done 10 is optimal but no more than 20.
As for your SD-ext partition, look into using Link2SD and moving non-critical apps over to the ext3 partition. Move any apps on SD to internal THEN create the links. If your internal memory runs out while doing this simply do a quick reboot from Link2SD to regain the lost space.
Lastly, strongly consider Prime's deprimed kernel. I use #19 as #20 uses BFS (and thus high Android OS usage) and the latest test causes a lot of lagging. Take a look at this thread:
http://forum.cyanoge...-kernel-how-to/
I use the same 20overclock config as the OP with satisfactory results:
1100 MHz, 68
1000 MHz, 60
850 MHz, 58
700 MHz, 44
550 MHz, 40
400 MHz, 32
250 MHz, 28
I use the bumblebee governor for all except my failsafe profiles (conservative) and screen off is set to 550/250 as consistent with how bumblebee behaves. See the OP's own profiles for an idea.
If you go through the Droid Forums thread linked within, you'll find the link to #19 if you look hard enough (as deprimed_previous.zip). If you feel that #20 or the latest test works well then by all means go for it. Again, my D1 works best with #19 but it may not be the same for you.
Other performance settings:
- No compcache. It's nothing but a headache.
- JIT disabled. (Adds some memory back.)
- Surface dithering disabled.
- 16 Bit Transparency checked.
- Purging of assets checked.
- Lock home in memory disabled. (I use V6 Supercharger) See this thread:
http://forum.xda-dev...ad.php?t=991276
- VM Heap Size 40m (though I have it set to 32m in the settings). See this thread:
http://www.droidforu...build-prop.html
EDIT: Posted clock rate and vsel values.
Edited by AlphaMack, 15 December 2011 - 09:44 PM.
#6
Posted 16 December 2011 - 07:59 PM
Sounds similar to an issue I've had. The phone will lock up and I need to pull the battery to clear. When answering an incoming call the ringtone continues to play even if I can answer the call. I found another thread that mentioned an issue with the Favorites. I removed all contracts from Favorites and this seems to have resolved the issue, at least it has not reoccurred in the 48 hours since I did this.
Never had the issue with the stock build.
Never had the issue with the stock build.
#7
Posted 18 December 2011 - 03:55 AM
Thank you @AlphaMack. I will try out your suggestions soon. As of now, I am a little busy and I have (on a trial basis) shifted to MIUI. Have had it for 24 hrs and no F/Cs so far. It seems to be considerably slower than 7.1 but at least I don't have to pull my battery out to reboot my phone on a daily basis. I was hoping that I could get my hands on CM 9.0 (hopefully more stable than 7.1) but it appears that it is a lost cause.
I do have a dozen contacts in my favorites. I will try your tip @jet526. Thanks
Again, thanks for all the tips. I will try them out in a week or two.
I do have a dozen contacts in my favorites. I will try your tip @jet526. Thanks
Again, thanks for all the tips. I will try them out in a week or two.
Edited by ssomnath, 18 December 2011 - 03:56 AM.
#8
Posted 18 December 2011 - 05:36 AM
Well, it is not the Favorites. Had it happen again today with an incoming call. It did release resources this time and allowed the next call through.
#9
Posted 06 January 2012 - 02:40 AM
I have the same issue. I have had nothing but headaches with 7.1. It seems like any time I add apps it fails on me. I keep going back to an image I had from November. Getting rather frustrated and debating going back to stock...
#10
Posted 07 January 2012 - 06:15 PM
Back again. I tried MIUI for about 2 weeks. Initially I found it very attractive but I soon realized why I had installed CM7 in the first place - speed. I am back on CM 7.0.3 now. The phone froze twice since the time I installed it (I have made / received nearly 200 calls). Still, considerably better than CM 7.1. I am not convinced that the phone freezing has anything to do with the favorites. Perhaps CM 7.1 was released out prematurely. Also, I am yet to try the swap space trick.
Also tagged with phone, app, freeze, motorola, droid, 7.1
Samsung →
Samsung Galaxy S i9000 →
Samsung Galaxy S i9000 Stable Mod →
Stuck in SplashStarted by Kochen, 23 Mar 2012 |
|
|
||
Motorola →
Motorola Defy →
Motorola Defy General →
CM9 NFC Error?Started by transfo47, 20 Mar 2012 |
|
|
||
General →
The Lounge →
Cyanogen for Droid ChargeStarted by warsphinx, 19 Mar 2012 |
|
|
||
General →
The Lounge →
Cyanogen for Droid ChargeStarted by warsphinx, 19 Mar 2012 |
|
|
||
Commtiva →
z71 Variants →
z71 Variants Stable Mod →
Unable to root my XT502 after installing the Boston ROM (cm6.1.2-Z71)Started by Arjun Kaushal, 09 Mar 2012 |
|
|
















