So I right now i am using CM7 with a2sd or data2sd, so ext3 is linked to phone memory, and i have around 1.8 gb of free space in phone.
My problem is, the phone is too slow. It's driving me crazy. I open facebook, facebook is not responding, wait or kill it, i choose wait few times then it works, but it freezes, same for all apps actually, foursquare, or gmail or else. I don't have a clue about reason of it. I am using 4 gb class 6 (bought class 6 for this) with 1.5 gb of ext3.
I am not sure if CM roms have problems (just my 2 cents, I am not telling this is bad), I used CM roms for long time, CM9 definitely too slow for my phone, I can barely use it without those too slow messages.
I arranged cpu to 400 mhz, as minimum and 768 mhz as max, and still it's causing that problem. I am not sure if I should switch to some other rom, or do something else? I actually bought class 10 8 gb microsd today just hoping it will be better.
It really drive me crazy, the phone wasnt like that before, I am so desperate that all I want is just a bigger internal memory, and rest can be all default.
Anyone may have idea about the cause, or perhaps the solution?
Try to move it on the internal storage (maybe remove the SD card) and if it works properly then there is some problem with your SD card.
I have CM7.2 too (with Link2SD) and I don't have any problem with it.
bonjurkes said:
So I right now i am using CM7 with a2sd or data2sd, so ext3 is linked to phone memory, and i have around 1.8 gb of free space in phone.
My problem is, the phone is too slow. It's driving me crazy. I open facebook, facebook is not responding, wait or kill it, i choose wait few times then it works, but it freezes, same for all apps actually, foursquare, or gmail or else. I don't have a clue about reason of it. I am using 4 gb class 6 (bought class 6 for this) with 1.5 gb of ext3.
I am not sure if CM roms have problems (just my 2 cents, I am not telling this is bad), I used CM roms for long time, CM9 definitely too slow for my phone, I can barely use it without those too slow messages.
I arranged cpu to 400 mhz, as minimum and 768 mhz as max, and still it's causing that problem. I am not sure if I should switch to some other rom, or do something else? I actually bought class 10 8 gb microsd today just hoping it will be better.
It really drive me crazy, the phone wasnt like that before, I am so desperate that all I want is just a bigger internal memory, and rest can be all default.
Anyone may have idea about the cause, or perhaps the solution?
Click to expand...
Click to collapse
Try to use data2sd. And it also depends on the governor. Try to use sio governoer.. hope it helps.
Related
Sup all! I love my Hero. I use it as my primary music player on the go.
As most of us have encountered though, it happens sometimes that music starts stuttering after half a day of usage. The problem arises when the music stutters for about a tenth of a second on wakeup, and could start stuttering really badly and intermittently while the phone is asleep. It's frustrating when I can't listen to a complete song without interruption!
I figured, if the phone is silky smooth soon after boot, but starts degrading after a while, it's certainly a software bug that's causing the hiccups. Looking at logcat didn't yield much else than AudioFlinger warnings, but after connecting through SSH and looking at top, I noticed the process /system/bin/mediaserver was using up to 17% of the CPU all the time. I killed it, and the music stopped, but then the process restarted, and the music started again, though from the beginning of a different track.
But the music was smooth again, and the CPU usage of /system/bin/mediaserver dropped drastically.
That's all I have so far. Anyone have a clue why mediaserver would start eating CPU cycles like that? Could it be fixed in future custom ROM releases?
I'm hoping for the best.
YES!
This has pretty much been my biggest concern since I got the phone, but haven't looked into it at all.
I am glad someone else brought this up, I'd like to see some discussion on it, and once I get some free time AND get the IM.apk working, I would like to help in figuring this out.
Just briefly I took a look at the Android OS source, and mediaserver doesn't seem to be in there, so I'm going to make a guess and say that mediaserver is an HTC-specific service. (It's 2:30 in the morning here, I really won't have time until at least Sunday to put this theory to the test. )
If it IS HTC-specific, well, there are pros and cons. A pro is that this would mean that simply using a different music app could instantly fix the problem. Cons: The HTC apps are not open source, and we'd probably have to rely on HTC fixing the code, hopefully in the 2.1 update... and, I really like the HTC Music app, so I'd rather not switch to something else if I don't have to.
If it's NOT HTC-specific, then we'll probably have the same problem with every Music app... HOWEVER, this also means that the community has a better chance of fixing it without HTC's help.
One potential solution I've been thinking of is to use Linux's nice function to give mediaserver a higher priority. This means that other processes will run slower when music is playing, but the mediaserver process should constantly get all the CPU cycles it needs. If I'm listening to music on my phone, I'm more than willing to accept a bit of slow-down in everything else.
Sidenote: After disabling compcache and applying this (http://forum.xda-developers.com/showthread.php?t=622666) fix, the issue is much less noticeable, but it's still there. If I were to venture a guess, I would say that disabling compcache is where this improvement came from, since compcache uses some CPU power to compress the memory.
mediaserver is part of the AOSP. It's inside platform/frameworks/base.git, in /media/mediaserver/.
I'll try looking into it but I doubt I'll find anything. =\
In some cases a better SD card helped
ROM based
I seem to recall this being a ROM based issue. I think I had it for a couple of the early versions of Paul's MoDaCo, but in the newer versions it was fixed, and its never been an issue on any of the AOSP 2.1 ROMs i've been running.
I would guess its probably something from the original HTC release that was badly implemented, or un-optimised.
[I think it may have been sorted for MoDaCo when teknologist released his custom kernal?]
I have a Transcend Class 6 8GB, which I think is a well respected card around here. Besides, it doesn't explain why the process starts choking up after a few hours.
By the way, I run on MoDaCo 3.2 beta 5, with the OOM killer tweaked. It's definitely a software bug where the mediaserver gets stuck in a a strange processor-intensive mode.
as for me A-Data micro sdhc turbo class 6 run smooth/faster on music playback/transfer or backup/apply file in recovery.
I have BT audio in the car, what I have found is that when a new track starts the begining seems slower than normal but speeds up, but this doesn't happen when I listen through the phones speaker or headphones? I run on MoDaCo 3.1 and my micro sdhc is a Kingston 4gb.
Could it be it takes a while for the "waves" from the new track to be caught by the stereo, so it takes a while to catch up? (lol!)
Hopefully when andriod 2.1 comes out it will be sorted?
Don't know how it happened, sorry
as i know when u on wifi or BT it will consume more power eat up cpu & phone will surely laggy. if u using normal cable earphone it doesnt consume more power then BT & wifi & dont eat much cpu. BT is eat lot of battery & cpu if im not wrong.
i get this same problem. Its been there since the stock firmware, and is still apparent in MoDaCo 3.1. Even with a class 6 8gb SD card, its still there.
Now Im running a 2.1 variant, its gone, so it would suggest its a rom problem for sure
alexperkins said:
i get this same problem. Its been there since the stock firmware, and is still apparent in MoDaCo 3.1. Even with a class 6 8gb SD card, its still there.
Now Im running a 2.1 variant, its gone, so it would suggest its a rom problem for sure
Click to expand...
Click to collapse
are you sure u using bluetooth audio without lag?
Hey there,
sorry for my bad English (that's why I post extremely seldom )...
I got a rootet HTC Desire with RCMixHD 3.0 and the D2WE-Script. Installed is a 8 GB SDHC Class 6 Card...
The thing is EXTREMELY slow (you can't use it), and sometimes really "lightning quick"...
The SD is formattet 1 GB Ext4 and the remaining 7 GB as Fat32...
AlphaRev installed for S-OFF...
HBOOT-0.93.0001
Radio 5.09.05.30_2
Recovery is AmonRA 2.0.1
I dunno why, but the device is sometimes this kind of slow... If the Screen is off, and you press the Powerbutton you can count slowly.. 1...2....3...4...5.... and a long time later the screen turns on and you can unlock it. Or if you swipe through the home-screens its pretty laggy... you swipe, nothing happen, and THEN it moves (or you have to try more often to swipe)... same at the App-Drawer... Open Apps is ok, the Apps doensn't hang or something (most times)... And the battery is empty in about one day without massive use...
Autokiller is installed and set to "Strict"
SetCPU is installed and set to Smartass @ 1113 MHz (this sometimes isn't set, too... you have to manuelly set the max. Frequency to another value and back and THEN it's recognized).
Sync with Exchange, Googmail, Facebook is enabled...
Hmm... If someone has an idea it would be wonderful!!
I thought that it's maybe the Ext4 Journaling... But nearly everyone here seems to have Jounaling enabled and no porblems with that...
Thank you for reading this crap XD
Greetings,
Alex
You don't need memory optimisation at all. Android does it for you when your running low on memory. You also must be running loads of stuff in the background or going through like 100 apps a min to get it that high. Also, change the scaling to ondemand or performance because the rest seem to mess up and not work too well with roms. You can set setCPU to boot when phone is booted. Also, your SD card needs to be fast enough but with it being class 6, I would say it is fast enough.
Hey there,
thanks for the answer. I know that Android has an internal task-management.
If I understand that right, Autokiller only sets other limits to the internal task-management so that it will kill unused tasks earlier. but I'll try it out when autokiller is disabled..
To SetCPU:
I'll give that a try, too.
Thanks!
Greetings,
Alex
edit:
BTW:
SetCPU has no Option "Performance" on my phone ... I set it to OnDemand 384 - 1113 MHz, Apply on Boot. And it has alsways root-access.
In the meanwhile I uninstalled the Taskkiller... And yeah... my old 4 GB SD has Class 6 too. I read here, that that's the minimum for installing Apps on SD...
Class 4 is the minimum for using A2SD. Did doing that solve your problem(s)?
Good morning there!
Hmmm it seems that it's a little better. But I don't know if this is just imagination
Especially if I install apps the performance is pretty bad... So I thought maybe it's the journaling (earlier I used Ext2 which has no journaling)... I dunno...
Does the data amount on my SD-Card matter?
I have much SMS (ok.. not really much data, but who knows?!), Videos and Music...
Thanks for the help!
Greetings,
Alex
Update:
It seems that now it's a little bit better, but now the phone doesn't awake from Standby very often (I have to pull out the battery - which is very annoying because I have a Otterbox )...
Any other ideas?!
Thank you!
Greetings,
Alex
So... Here another Information:
I flashed the same ROM 3-4 times again, the newer versions, too...
But no effect.
Sometimes it works for a few days, sometimes it works until the next reboot...
Now I flashed another ROM. At the first time it has the same errors like the last, but now it seems to work properly... It's not 100% what I'm looking for, but ATM the main thing is, that it doesn't crash and theres no loss of data...
Thanks again for the answers and the help!
Have a nice day!
Greetings,
Alex
I flashed LeeDroid 3.0.8.2 yesterday (via Rom Manager if that makes a difference) and I've noticed a lot of poor performance.
I get wake up lag and it takes the phone anywhere between 5-8 seconds from the moment I unlock the phone until I can actually use it. It's stuck and any actions take a good few seconds to register and show their effects.
Then when I receive calls it takes the phone about 3-4 seconds to show the caller on screen and until it does I can't answer.
FWIW the phone is running A2SD+ LeeDroid 3.0.8.2 on a C2 4gb Sandisk sd card, but with the same card and LeeDroid 2.5 I had none of these issues.
Any help will be greatly appreciated.
Hi
I'm running the same ROM, and, I've found if you set setcpu to a higher minimum, like 384, the problems with calls and stuff seem to go away, try that, hope it helps
Also, if the problems stay, then it may be time to get a bigger or higher class memory card, there have been people reporting sluggishness with lower class cards.
Not sent from an IPhone of any sort, sent from my leeDroid powered Desire
I solved this issue by flashing LeeDroid's HD port and man oh man... It's such a fantastic experience, it's like I have a new phone, a faster, more responsive one.
end_of_message / COMPUTOR4500
Hi,
i want to start a discussion with those of you who have such unstable Desires.
I am one of the sad guys having one of them. It seems that there are a few Desires which do not run like all the others.
A typical thing with this Desires are complete freezes of Android. Very often they happen when the screen is off, the phone is idle and recieve a SMS or a Phone call. The phone freezes imediately and you are never informed of the SMS or Call. It is just lost. You just detect that you can not power on your phone and must remove the battery to get it back to life.
I have this starnge freezes with every ROM. Most people do not believe you because they do not have the problems.
I have tried several things till now.
- A new SD Card
- Several ROMS
- Allways full wipe
- Allways format SD card with gparted
- Allways start from scratch without backup of Apps
- Different Kernels
- Delvik internal
- uvm...
But all of this things did not help! It seemed that only i have the Problem and i was thinking its a hardware defekt.
I was searching for a new Android device as i again installed a new ROM and read from someone with the same problems. I also read about the UV capabilities of Deamon Controller.
So i give this a try.
I now have installed AIO 3.0.4 on CM7r2 with x2sd with latest radio and one Ext4 partition. First of all i went to deamon controller and put up the voltages a little bit. And since i have done this my freezes nearly are gone.
I now played around with the settings and it turns out that you must find the right values. To much voltage is not good and to less is also not good.
It seems that there are some CPU's in some desires which are not very stable and do not like the OC / UV.
It would be very nice to know about your expirience with unstable Desires and what you have done to fix this. Perhaps we can also find good values for UV.
Or we can find a mix of things to make this Desires also stable.
Regards
Kai
It's a known issue that too much undervolting or overclocking leads to CPU freezes, or kernel panic and then restarts. That different boards have different thresholds of these is also known. That's why we usually built locks for CPU freq and voltages while booting up, and then the user is responsible for experimenting with different freq/volt values and finally arriving at an optimium range for his CPU.
Hi,
thanks for the reply.
Do you know what are the default settings in a standard rom? Is there a CPU freq and voltage change or is the standard 998 and 1275 mv?
My problem is that standard settings, tables from custom roms did not work for my desire. It is really very unstable wiith this settings and i am hoping to find other Desire users having the same problem to find a good solution.
Thanks again for the help.
Yes, 998 Mhz is the standard freq at which freq is usually locked/
Thanks again, so using 998 with 1275 schould be the normal mode every desire is supposed to work with?
I am happy
Thanks to all of you who helped me with my problems.
Finnally after one year of Problems it seems i have a solution for my unstable desire.
After 2 Days of intensive testing i want to share my experience with you.
Seems my Problem was solved by setting own UV(undervolt) values.
It works great for me, other CPU can need other values, you must play around with it. But you can also try to use my settings.
I can say the phone is now rock solid. I could not believe that it was such a little thing. I even managed now to overclock it to 1190 without freezes.
As i said i had issues with every image and tried alot with new SD cards, other kernels, setting CPU speed ... Nothing helped. I had total OS freezes 3 - 15 times a day.
But now with the new UV settings in Deamon controller i get it really stable!
I want to explain you exactly my set up.
But i strong believe it was the UV / OC settings which do the stabilisation!
My set up:
Alpharev cm7r2 (S-Off)
4 ext Recovery
16 GB Samsung Sd Card Class 10
Fat32 + 1024MB Ext4 for x2sd
Runnymed AIO 3.0.4
X2SD Script
Deamon Controller with andrev_oc and custom UV settings entered in Deamon Controller.
Things i have applied:
RunnyMede_NO_Xloud.zip (speakers are too load for me in original)
No_TPWakeUp-Runny.zip (I do not want to wake up the phone with TP)
50+ APP's
Batterylife is not too bad i think. This is a screen shot of a medium to haevy using day.
Now here are the screens on UV and OC (and battery life):
kai-t said:
Thanks to all of you who helped me with my problems.
Finnally after one year of Problems it seems i have a solution for my unstable desire.
After 2 Days of intensive testing i want to share my experience with you.
Seems my Problem was solved by setting own UV(undervolt) values.
It works great for me, other CPU can need other values, you must play around with it. But you can also try to use my settings.
I can say the phone is now rock solid. I could not believe that it was such a little thing. I even managed now to overclock it to 1190 without freezes.
As i said i had issues with every image and tried alot with new SD cards, other kernels, setting CPU speed ... Nothing helped. I had total OS freezes 3 - 15 times a day.
But now with the new UV settings in Deamon controller i get it really stable!
I want to explain you exactly my set up.
But i strong believe it was the UV / OC settings which do the stabilisation!
My set up:
Alpharev cm7r2 (S-Off)
4 ext Recovery
16 GB Samsung Sd Card Class 10
Fat32 + 1024MB Ext4 for x2sd
Runnymed AIO 3.0.4
X2SD Script
Deamon Controller with andrev_oc and custom UV settings entered in Deamon Controller.
Things i have applied:
RunnyMede_NO_Xloud.zip (speakers are too load for me in original)
No_TPWakeUp-Runny.zip (I do not want to wake up the phone with TP)
50+ APP's
Batterylife is not too bad i think. This is a screen shot of a medium to haevy using day.
Now here are the screens on UV and OC (and battery life):
Click to expand...
Click to collapse
I hope this works with my setup. I have not applied wht you've listed. And I am on stock hboot, 4 GB class 4, Clockwork Mod recovery...
Will try it later in the day. Thanks!
Hi kartnite,
would be nice if you could share your experience with us if you have tried it.
Some more infos i have collected in onother thread, perhaps helpfull:
I have also used the SD Tools App.
Think i was wrong it's a samsung class 6 card:
6.1 MB write speed
27 MB read speed
My own thoughts to the comments about OC / UV:
Since the Display uses the most amount of the Battery it does not really matter to use some mv more or less. This is also prooven because the original images uses 1275 mv and 998 MHZ fix!
Some CPU's seems not to like undervolting. Some seems to have no problems with this.
For my CPU it is true that standard UV values make the phone freeze very often. Set the voltages up a little bit makes the CPU happy and my phone is stable
Also i think it is no danger, as long as you do not go over 1275 you are using the normal voltages.
About battery life i think it is important that your phone enters deep sleep mode when you turn the display off. You can check it with CPU Spy App.
My battereylife is good, at least more than 24 hours with normal usage.
My deamon settings are:
sleep min: 384
sleep max: 998
wake min: 284
wake max:1190 (here with 1350 mv)
I have set the 1190 since my phone is stable. The 1190 makes the ROM even more responsive if used.
Regards
Kai
Well, been a few hours now since I applied those settings.
Total of three force closes- Facebook, Mail and Sense.
Comparatively lesser than what it was earlier, but force closes nonetheless.
Yes, I did find that "improvement" in responsiveness but the lag returned.
I'm looking at other options, too.
Sorry for the delayed response. Wanted to wait a few hours before sharing what I observed.
Thanks for those additional points, mate. Will try them later in the day...
-
Swyped from XDA-Premium
kai-t said:
Hi kartnite,
would be nice if you could share your experience with us if you have tried it.
Some more infos i have collected in onother thread, perhaps helpfull:
I have also used the SD Tools App.
Think i was wrong it's a samsung class 6 card:
6.1 MB write speed
27 MB read speed
My own thoughts to the comments about OC / UV:
Since the Display uses the most amount of the Battery it does not really matter to use some mv more or less. This is also prooven because the original images uses 1275 mv and 998 MHZ fix!
Some CPU's seems not to like undervolting. Some seems to have no problems with this.
For my CPU it is true that standard UV values make the phone freeze very often. Set the voltages up a little bit makes the CPU happy and my phone is stable
Also i think it is no danger, as long as you do not go over 1275 you are using the normal voltages.
About battery life i think it is important that your phone enters deep sleep mode when you turn the display off. You can check it with CPU Spy App.
My battereylife is good, at least more than 24 hours with normal usage.
My deamon settings are:
sleep min: 384
sleep max: 998
wake min: 284
wake max:1190 (here with 1350 mv)
I have set the 1190 since my phone is stable. The 1190 makes the ROM even more responsive if used.
Regards
Kai
Click to expand...
Click to collapse
Thanks Kai,
finally i found someone with the same problem,
firstly i even try to use another kernel just like gingerbread 0.9 or 0.8.
I forgot the low-voltage influence(just like OC in Computer),
thank for your sharing~
Hi all,
sorry, but i have bad news.
The UV settings seemed to help a couple of days, but than my desire begin to freeze again.
It all started with a forced close of Whatsapp. After that many force closes returned and my desire also beginn to stuck.
I tried to repair the Filesystem with gparted. But it made it even worse.
I tried the whole Weekend, and even with only 998 and no UV the Problems kept.
Seems that somehow the image gets corrupted, even Dalvik wipe, or reflashing did not help.
Now i again started from scratch.
I installed AIO 3.0.5 with complete wipe and new partitioned SD card.
This time i set up the ROM without inserted SIM Card. I have done this because things alsways stuck when SMS, Phone things happen.
I think the SIM can have influence on the ROM's stability. I do not know why.
But without SIM Card insert i could set up everything without Problems.
Installed Andrev_OC and let all settings and UV as they are. Setup Apps, Contacts, Facebook. Let the phone sync and set up. Started it a few times.
I runs stable. I made a backup.
After the Backup got this HTC Launcher error, restrted and it was ok.
Then i inserted the SIM card. Till now it works. But lets look if it gets unstable again.
If this try will not succeed i will buy a new HTC and will sell my Desire. This freezes sucks.
But as said today it worked perfect. With many SMS and phone calls withoud freeze. It is really a strange thing!!!
Hope i can tell good news in a couple of days!
kai-t said:
Hi all,
sorry, but i have bad news.
The UV settings seemed to help a couple of days, but than my desire begin to freeze again.
It all started with a forced close of Whatsapp. After that many force closes returned and my desire also beginn to stuck.
I tried to repair the Filesystem with gparted. But it made it even worse.
I tried the whole Weekend, and even with only 998 and no UV the Problems kept.
Seems that somehow the image gets corrupted, even Dalvik wipe, or reflashing did not help.
Now i again started from scratch.
I installed AIO 3.0.5 with complete wipe and new partitioned SD card.
This time i set up the ROM without inserted SIM Card. I have done this because things alsways stuck when SMS, Phone things happen.
I think the SIM can have influence on the ROM's stability. I do not know why.
But without SIM Card insert i could set up everything without Problems.
Installed Andrev_OC and let all settings and UV as they are. Setup Apps, Contacts, Facebook. Let the phone sync and set up. Started it a few times.
I runs stable. I made a backup.
After the Backup got this HTC Launcher error, restrted and it was ok.
Then i inserted the SIM card. Till now it works. But lets look if it gets unstable again.
If this try will not succeed i will buy a new HTC and will sell my Desire. This freezes sucks.
But as said today it worked perfect. With many SMS and phone calls withoud freeze. It is really a strange thing!!!
Hope i can tell good news in a couple of days!
Click to expand...
Click to collapse
Hope you succeed in it.
I just replied you yesterday & set the UV setting before I slept last night.
And I have fully charge with battery in 100%.
But it still happened again, drained of battery to 30% and froze.
Also I have late for work without alarm clock.
I dont want to give up, but it is hard.
kai-t said:
Hi all,
sorry, but i have bad news.
The UV settings seemed to help a couple of days, but than my desire begin to freeze again.
It all started with a forced close of Whatsapp. After that many force closes returned and my desire also beginn to stuck.
I tried to repair the Filesystem with gparted. But it made it even worse.
I tried the whole Weekend, and even with only 998 and no UV the Problems kept.
Seems that somehow the image gets corrupted, even Dalvik wipe, or reflashing did not help.
Now i again started from scratch.
I installed AIO 3.0.5 with complete wipe and new partitioned SD card.
This time i set up the ROM without inserted SIM Card. I have done this because things alsways stuck when SMS, Phone things happen.
I think the SIM can have influence on the ROM's stability. I do not know why.
But without SIM Card insert i could set up everything without Problems.
Installed Andrev_OC and let all settings and UV as they are. Setup Apps, Contacts, Facebook. Let the phone sync and set up. Started it a few times.
I runs stable. I made a backup.
After the Backup got this HTC Launcher error, restrted and it was ok.
Then i inserted the SIM card. Till now it works. But lets look if it gets unstable again.
If this try will not succeed i will buy a new HTC and will sell my Desire. This freezes sucks.
But as said today it worked perfect. With many SMS and phone calls withoud freeze. It is really a strange thing!!!
Hope i can tell good news in a couple of days!
Click to expand...
Click to collapse
Changing UV din help me too.. So back on Samsung SD card (class 2) and it works fine.. I would suggest you to try with Samsung SD cards, cause they have better read speed.. I never has even i single with Samsung SD card but with Sandisk class 4 i had many freezes with same ROM and setup...
Thanks for the suggestiones,
i think that UV did not really help.
Yes i have a 16 GB Samsung card. I tried everything to get rid of this bug.
Now i am very supriesed, since the last setup yesterday the phone worked without freeze. But lets see sometimes things get worse after a few days.
I really do not understand what causes the trouble.
Setting it up without SIM Card seemed to help?
I am really confused. I always set up ROMS very correct. Means full wipe. Let boot , give time to stabilize... But mostly the ROMS crash before having set up all apps.
Without sim there was no problem. Now lets look how it goes on with this set up.
Before i have inserted the SIM again i pressed on the metal from the sim slot to make the sim fit better? Perhaps this helped? Anyone knows about problems with this causing ROMS to freeze?
If i think back my Problems started with a new SIM Card from O2 Germany.
I will report if it will start to freeze again or if it work.
Regards
Kai
kai-t said:
Thanks for the suggestiones,
i think that UV did not really help.
Yes i have a 16 GB Samsung card. I tried everything to get rid of this bug.
Now i am very supriesed, since the last setup yesterday the phone worked without freeze. But lets see sometimes things get worse after a few days.
I really do not understand what causes the trouble.
Setting it up without SIM Card seemed to help?
I am really confused. I always set up ROMS very correct. Means full wipe. Let boot , give time to stabilize... But mostly the ROMS crash before having set up all apps.
Without sim there was no problem. Now lets look how it goes on with this set up.
Before i have inserted the SIM again i pressed on the metal from the sim slot to make the sim fit better? Perhaps this helped? Anyone knows about problems with this causing ROMS to freeze?
If i think back my Problems started with a new SIM Card from O2 Germany.
I will report if it will start to freeze again or if it work.
Regards
Kai
Click to expand...
Click to collapse
I guess for me it was more over SD card issue.. My be your case is different .. best of luck on new setup.. I will be buying new SD card soon
Hi,
wish you the best luck! I have a Samsung SD card.
Works since 2 days stable. One FC when installing Facebook and i had to reboot.
But no OS freezes or missed SMS / calls.
Let's see if it stays like that. Sorry tht the UV not helped, but perhaps try fitting the SIM card better (with tesa on the back or pressing on the mettal) and try to install ROM first without SIM.
Another tip for Battery drain. I recognized yesterday that i have battery drain and i could see that my phone only gets partitialy into Deep Sleep. I serached what it is and in the end i recognized that it was the Facebook app. Installed the update to the newest version and now my phone went into Deep Sleep.
If you are not sure use CPU Spy to check.
If your display is off your phone should be nearly 100% in Deep Sleep. In Deep Sleep my phone uses nearly no battery! Thats really great and gives a long standby time! So check that newest Facebook is installed!
Regards
Kai
I don't want to be the spoilsport, but I've got the same problem only with my Samsung 16gb class 6 card, not with my "older" Sandisk class 2. But this card is way too slow for sense 3.5.
I've tried the higher UV values, which solved the freezing problem for a few days. But only temporary.
I'm considering switching to an ASOP ROM, just to keep my phone running stable. It often crashes on incoming calls or during nighttime. I missed a lot of calls and alarms.
kai-t said:
Hi,
wish you the best luck! I have a Samsung SD card.
Works since 2 days stable. One FC when installing Facebook and i had to reboot.
But no OS freezes or missed SMS / calls.
Let's see if it stays like that. Sorry tht the UV not helped, but perhaps try fitting the SIM card better (with tesa on the back or pressing on the mettal) and try to install ROM first without SIM.
Another tip for Battery drain. I recognized yesterday that i have battery drain and i could see that my phone only gets partitialy into Deep Sleep. I serached what it is and in the end i recognized that it was the Facebook app. Installed the update to the newest version and now my phone went into Deep Sleep.
If you are not sure use CPU Spy to check.
If your display is off your phone should be nearly 100% in Deep Sleep. In Deep Sleep my phone uses nearly no battery! Thats really great and gives a long standby time! So check that newest Facebook is installed!
Regards
Kai
Click to expand...
Click to collapse
Thanks for the tips.. I do get great battery while display is off, but when display is on it consumes lots of battery.. For this, some one asked to set the auto brightness to lowest. in rcmix display settings..
After months of suffering the random freezes and blank screens I've came to the conclusion that my problem stems from the sd card (not the actual card as I've tried a few) but the component which holds the card.
I've returned the phone to cpw but got it back untouched!
The way I test if it's the sd card if to open my camera app and if the small box in the bottom right of the screen is not showing the last picture taken (it shows black instead) then I turn phone off, push down on the sd card, reboot, and everything works - for a while!
Edit-I'm using the oxygen ROM so the camera app is the aosp one. If you have a file explorer then trying to open a file on your sd card will also let you know if there is a problem
Hi iain2510,
which camera app do you use? I do not have this small box.
Regards
Kai
Lately my G4 has suddenly locked up several times, usually when unlocking. Everything would slow to a crawl (several minutes for anything to respond) or freeze entirely until I rebooted (which sometimes required pulling the battery).
I installed Cool Tool to diagnose the problem and found that it happens when free RAM gets under about 180MB. kswapd kicks in with several hundred MB/s of I/O (I saw it over 1000 once). I'm not sure what it's doing with that much I/O, but of course it makes everything grind to a screeching halt.
Looking in Kernel Adiutor (sic), ZRAM is set to 700MB and swappiness (who puts swap on a flash storage device anyway?) is 80. Both seem very high to me. Why using 700MB of precious RAM food for a virtual, compressed (slow!) swap file, and swap so often? I adjusted them to. 250MB and 20 respectively. As expected I now have way more free RAM (average ~600MB, up from ~300), things seem more responsive and I haven't had any lockup (but I only did this a few hours ago, so too early to know if it really fixed the problem).
Anyone know why these were set to such large numbers? Anyone else have this issue and if so, does this tweak help?
Mine was 40 in swappiness but zram value stick to 700mb
That's odd. I wonder if some process adjusts it on the fly when RAM is low?
Just had another "freeze" with ~200MB free. Again kswapd doing a bunch of I/O and slowing everything else down. Wasn't nearly as bad this time though. Less I/O going on, things were sluggish but not completely frozen, was able to open the recent apps menu and hit Clear All to free up a ton of memory and get things running smoothly again. Maybe need to tweak OOM killer and swappiness settings more so I don't have dozens of old aops/tabs hanging around hogging memory.
RenaKunisaki said:
Just had another "freeze" with ~200MB free. Again kswapd doing a bunch of I/O and slowing everything else down. Wasn't nearly as bad this time though. Less I/O going on, things were sluggish but not completely frozen, was able to open the recent apps menu and hit Clear All to free up a ton of memory and get things running smoothly again. Maybe need to tweak OOM killer and swappiness settings more so I don't have dozens of old aops/tabs hanging around hogging memory.
Click to expand...
Click to collapse
are we both the odd bunch? this is the first time I've come across someone else experiencing the same issues as me! switched from a Samsung to an LG, 3GB to 4GB device respectively, and still experiencing this from time to time.