My girlfriends pro+ often wont make calls. Stock gingerbread fw. You'll hit dial and it just doesn't respond for sometimes a min or two. When this happens I often find that there is barely any available memory. How do I prevent memory consumption from getting so high?
Related
Well hello there xda Community,
I decided to purchase a i-mate JasJar (HTC Universal) a while back. I have noticed that just about any ROM I install on here doesn't seem to perform very well, even some of the very best ones. I have a feeling that it is the CPU that may have been damaged in some way. I do not know for sure. Some issues that I've experienced go as; pauses in videos I play (audio, sometimes picture), sometimes songs pause for almost 10 seconds...It acts as if the whole device freezes up. Runs very slow when I run Skype (NEWEST VERSION) with nothing else running. Freezes sometimes when incoming call comes in if I'm using an application...ALL THE PROBLEMS I JUST STATED OCCUR SHORTLY AFTER SOFT RESET...and/or when there is a lot of free ram. I have also read in other posts of owner's jasjars booting up in five seconds...is this common, I'm generally waiting, oh...say around 30 to 45 Seconds...and btw, I've tried just about every tweak and tune up for the Jasjar (no improvment) CPU Speed up, RAM Cache increased....no luck,
I'm curious to know if this is how the device was designed to run or if this is just an isolated issue on the exact piece of equipment I'm using...
Any help or advice would be of any importance to me...Thanks
I too have a jasjar. On the skype issue, I use XCpuscalar 2.95 AND SET THE DEVICE SPEED TO 520 and the cracles disappear. I think the video issue you are having could be the device increasing and decreasing cpu speed depending on cpu usage so setting it on 1 cpu speed should help. Goodluck!
I'm using the latest damagecontrol rom on my hero with a 710 MHz overclock and I'm pretty happy with my hero. The phone performs a good deal better however my main issue from before still remains. The dialer lags horribly so that I can't answer 50% of my incoming calls.
Do I need a task manager? A better rom? A better dialer app? I like the main apps functionality but if there is an app that doesn't crash every other time then I'm down.
fortunado said:
I'm using the latest damagecontrol rom on my hero with a 710 MHz overclock and I'm pretty happy with my hero. The phone performs a good deal better however my main issue from before still remains. The dialer lags horribly so that I can't answer 50% of my incoming calls.
Do I need a task manager? A better rom? A better dialer app? I like the main apps functionality but if there is an app that doesn't crash every other time then I'm down.
Click to expand...
Click to collapse
There are several people who have this problem. Some people suggest setting your Slot Index to 1 instead of 2, but its not that big of a help in my experience. And I have heard that the towers force a specific polling rate on you.
I have found that moving ringtones from the SD card to internal memory seems to help a little if you have a slow card. Now that I have a class 6, the difference is negligable.
Actually it happens on outgoing calls as well. :\
happens to me too. isn't "ring lag" that has been discussed before. just a delay when you click on a contact name and it tries to call. can take up to 20-30 secs... will call them twice if you tap it twice, you'll have them on call waiting aaha.
Clear your call history, Mine after about 3 weeks makes the dialer lag so bad its unuseable. That at least helps with the visible dialer lag, doesn't seem to make much difference for incoming calls (which I still miss most of the time).
I just posted in another thread, I've tried a dozen different ROMS, OC and non-OC, and have yet to get the phone to ring for even 50% of the 23 second ring-cycle.
I had SEVERE lag when I was on the stock 2.1 release from Sprint. After I rooted I haven't tried all the ROM's out there, but there is NO LAG on Aloysius 2.1. Plus, if you download the snow version, you get the AOSP dialer as well so you can try both. I am not saying your current ROM is bad, but I'd play around and see.
i wonder if it is a diff phone.apk in that rom, i wonder if it could be extracted?
Hey guys,
A few weeks back I rom'd my HTC hero with VillainRom 12 and it was working great for awhile. Now however it crashes all the time, or just freezes up and I have to remove the battery.
I have the phone over clocked to about 650mHz. The battery temps seem fine.
Has anyone else experienced this problem before? Any way I can do a debug on my phone to find out what's crashing?
It's really starting to annoy me considering that I use my phone for my business and it's not good when a customer calls and my phone dies and reboots when I go to answer a call.
try overclocking to a lower extent
it might be because your phone cannot handle ur clock speed
(my MAX clock speed is 672... it simply crashes with 691 or higher)
You were absolutely right. It was clocked too high.
I turned it down and now it works great.
Thanks for the tip.
652 seems to be my max.
710 is my max, I can't go below 192 either or the phone starts to have a fit, I wanted to use a lower clock speed in "screen off" mode, but I'll have to stick with 192
Hi,
Currently i'm using kyrillos 5.5 (based on froyo 2.2 JPM).
I just want to share my experiences and things I did to get my phone running nicely.
- disable "sensor aiding" to get rid of 100% cpu-usage after exiting any GPS based application (also involved in camera crash). you find this setting in settings-'location and security'.
- with kyrillos rom 800 Mhz version, use setcpu or no-frills cpu governor to 'anything but conservative', so I chose (with setcpu) min.800mhz max.800mhz performance, and for screen-off profile 166-800 mhz on-demand governor. Cpu governor at conservative can stick your CPU at 83Mhz..which causes mayor lag as you can imagine.
It's assume it's not a Kyrillos issue, but fugumod (2.4 beta3) problem.
BTW somehow, the 800-800 Mhz. doesn't drain my battery much.
- I finally re-formatted my sd-card to fat32 (so no ext2 ext4 partitions anymore) to keep all memory caching/swapping in RAM and not to sd-card which could wear-out the sd-card in the end. I use class-2 card so could cause more lag because it's too slow for swap/cache/dalvik. Beware that you cannot install too many programs or you run out of memory..but hey do I need 50 games/apps on my phone ?
- I use zeam launcher as this launcher seems to use less memory (only 1 process too, not two as many other launchers). only disadvantage at this time is that auto-rotate doesn't follow your settings in phone, it's either on or off for zeam itself.
Ok I hope I help a lot of people with these tips/tricks.
If you have any additional tips/tricks, please reply so I can learn from it too
Br.
Michel
vleutmans said:
Hi,
Currently i'm using kyrillos 5.5 (based on froyo 2.2 JPM).
I just want to share my experiences and things I did to get my phone running nicely.
- disable "sensor aiding" to get rid of 100% cpu-usage after exiting any GPS based application (also involved in camera crash). you find this setting in settings-'location and security'.
- with kyrillos rom 800 Mhz version, use setcpu or no-frills cpu governor to 'anything but conservative', so I chose (with setcpu) min.800mhz max.800mhz performance, and for screen-off profile 166-800 mhz on-demand governor.
It's assume it's not a Kyrillos issue, but fugumod (2.4 beta3) problem.
BTW somehow, the 800-800 Mhz. doesn't drain my battery much.
- I finally re-formatted my sd-card to fat32 (so no ext2 ext4 partitions anymore) to keep all memory caching/swapping in RAM and not to sd-card which could wear-out the sd-card in the end. I use class-2 card so could cause more lag because it's too slow for swap/cache/dalvik. Beware that you cannot install too many programs or you run out of memory..but hey do I need 50 games/apps on my phone ?
- I use zeam launcher as this launcher seems to use less memory (only 1 process too, not two as many other launchers). only disadvantage at this time is that auto-rotate doesn't follow your settings in phone, it's either on or off for zeam itself.
Ok I hope I help a lot of people with these tips/tricks.
If you have any additional tips/tricks, please reply so I can learn from it too
Br.
Michel
Click to expand...
Click to collapse
That is some nice info...... I would like to add some myself....
For Battery:-
Disable data connection when not in use - drains battery like hell.
Disable Auto Sync - saves some processes and battery.
Brightness - lower screen brightness - the less brightness you keep the more the battery
The video player has it's own brightness so check that too.
Don't use task killers like ATK if you are a newbie and don't know much about system process..... if you kill all the process, some just start again as they are necessary.... instead use the stock task manager or watchdog.
Undervolting - ADVANCED USERS ONLY - please who know what they are doing can undervolt the cpu which increases the battery life by a noticeable margin.... for this you can use an app called pimp my cpu.
Stock Gallery - Spare from Using the Samsung stock gallery, it's a huge battery hog!
For Performance:-
APPS - VERY IMPORTANT - even though we have ext4 partion on sd card we do not have a super-phone that can handle 50 apps running in the background.... so keep passive and active multitasking to a minimum
Tweaks - for increasing performance on our phone you can enable JIT, change file partitions, install overclocked fugumod (800 mHz), fugutweaks.
Widgets - well although widgets are fairly usable and state that application is not actually open but infact they have processes and too many widgets on your home screen can affect your phone's performance as these processes stay even when you are not on your homescreen.
Keep the phone memory reasonably free - i mean the phone storage....
- quick call end: settings/Accessibility/use power button to end call
- quick call pick-up: settings/call/all call/pick up a call with home button
- disable mobile data: long press power button/disable mobile data
- not for froyo but usefull: press more than 10 sec the power button-->hard phone restart
data connection for me, doesnt causing battery drain..
hodostamas said:
- quick call end: settings/Accessibility/use power button to end call
- quick call pick-up: settings/call/all call/pick up a call with home button
- disable mobile data: long press power button/disable mobile data
- not for froyo but usefull: press more than 10 sec the power button-->hard phone restart
data connection for me, doesnt causing battery drain..
Click to expand...
Click to collapse
actually what i meant by data connection causing a huge drain was that it consumes more battery.
With all the specified things done i managed to squeeze a hell load of battery..... two days straight of heavy usage ........ sent around 500-600 messages.... talked for about six - seven hours..... and angry birds for 40 minutes before i got the low battery signal!.
addon to tips and tricks on froyo 2.2
Hi all,
I would like to add an already known setting to many and that is :
"switch on USB debug mode" in settings-applications-development.
This fixed for me a lot of frustration with navigon , when used in the car.
Normally after connecting power to the phone in my car, I got popup menu with choice of how to connect, like choice of mass storage, mediaplayer etc. I pressed the back button to get rid of it. Then I started Navigon which showed lot of lag and FC many times during a trip.
After setting usb debug, I don't get this choice menu anymore, and Navigon works like a charm.
Furthermore if I want to transfer data from PC to SD card I still can do this by selecting mass storage in the notification bar of the phone.
Hello together,
after i used Cm7.1 for some days with the CPU-Settings
(352-652 Smartass), i recognized that my phone sometimes is a little bit laggy. For example when i suddenly pull down the statusbar,when i open system from lockscreen, when mail arrives and are displayed in status bar. Its not lagging per se, but sometimes it does.
So i changed the lower value to 528 and the phone is much more responsive for me. Because i read in some threads here that people found Gingerbread Cm7 a little bit laggy, maybe that could be a solution for this issue.
Anybody made the same experience with the lower Cpu-settings?
nope. I'm running smartass on 245/710 and the only downside of the lower bound is that it takes a small fraction of a second until the lockscreen is present and (i assume) at 710 mhz. But that doesn't bother me.
I have to check if my incoming calls are delayed though, but no problem so far
(The wildfire will always be laggy sometimes imo, got to live with that )
Ive noticed the lockscreen-delay too, but with a higher cpumin its gone.The incoming calls were not much delayed for me at cpumin:342, ive checked it
10 times and it was always around 800-1500 miliseconds between the reaction of my wildfire and hearing the ringtone of the calling phone.
My problem was the initial lag when starting to do things, as im using the phone not for gaming .....mostly for sms,phoning,navigation and a lot of mailing i just want to have short reaction time get into mail menue and so on.....and this, i found for me, is much better with a higher minimum CPU frequency.