I've had this problem before using Cyanogen 6+, but still haven't seen any questions on this forum about it. My buddy also has a rooted slide with Cyanogen 6.1.0 and has the same issue.
The messaging app is going very slow. It takes a good 8 or 9 seconds to load the thread list, and then takes another 6 or so seconds to open a message.
After I send a message, or when I receive a message, it takes almost 10 seconds for it to appear on my phone. I've been having to read texts in my notification bar because of this.
Anyone have any ideas how to speed it back up? I have not tried deleting all the threads, as I wanna keep that as the last option.
Ah, nevermind.
Wiped cache, Dalvik Cache, and (because I've needed to do it for a little while now) battery history.
Messaging app is back up to full speed.
Related
So lately I have been having problems with my Epic. I was previously running Nebula rom, but it would always restart randomly and one time it would restart endlessly until I took it home and returned it to stock. I tried Nebula 1.0.7 again but same quirky problem. Now Iv been running the latest release of the ViperRom, but today it did the same restart thing, where all of the sudden the booting animation would come up and my phone would be restarted.
And now my messages have been acting funny. I run Handcent as my SMS app. I noticed the message pop ups would get to my phone, and then in 10 or so seconds it would vibrate and the app would recognize it had a message. Sometimes i could send a message through the pop-up and then when I went into the main part of Handcent, my message would be sent before the message i replied to, And sending messages takes forever now. I seem to be able to remedy this for a short time by going into CWM and fixing permissions, but its a very temporary fix.
Sorry for the long read, but this is making me mad. Any input is appreciated.
If this is in the wrong section, just let me know and Ill move it.
Some others, including myself, have reported similar problems when upgrading to EB13. For me, about 30 minutes into the phone being on, my cpu load would jump to 100% load (check yours with an app such as Process Monitor Widget). When my cpu was at 100%, the phone itself would run fine, but it seemed as if priority was given to everything BUT data apps such as the browser and GO SMS (the messenger app I use). I got the same popup/message problems and sending messages sometimes took minutes.
If you're in the browser, type in a website, and it hangs, hit home and then go back into the browser. I found that the data transfer would kick in and load my webpage after going back into the browser. In my case this worked only when I hit home to exit the browser, rather than hitting back to close the browser.
Let me know if any of this information helps. And if you are having a similar issue, this thread may help a bit.
midNight 4.1
I have been running midNight ROM 4.1 EB13 w/EXT4.
I have no issues at all and overall this ROM series has been rock solid. I tried a couple and read for weeks before settling in on that 1 ROM.
It is super easy to get up and running with it.
Just my 2 cents <grin>
Hi.
As the title says, I am having problems with freezing/lockups when receiving/sending SMS. It only happens with large message treads (300-800 msgs in tread).
To the problem, when I receive a new SMS and open it to read it, every thing is fine, but when I press the back button to exit, nothing happens for a while, then the screen goes black, and after a while a popup ask to force close or wait for program to respond. This can take from 10-45 seconds, mostly the latter.
If I just enter a msg tread, without recieving a new SMS or sending one, every thing works like a charm.
I am running Leedroid 3.08.02 on a HTC Desire/Bravo. And have 60Mb free memory. Also had this problem in Leedroid 3.07.
Did a full wipe of the phone when upgrading, and then restored my SMS.
PS. I am posting here since newbies arent allowed to post in developers section.
Hope for some smart feedback..
Thxs!
I had a similar issue using Go SMS on Leedroid 3.0.8.2. Sometimes when exiting SMS, phone would reboot. Didn't really solve it, just assumed it might be because memory was pretty full and/or caused by really long message threads.
Have been trying out LeeDrOiD HD V3.3.1 - Port today, sms seem to be snappier with no lag but then I have lost all the long threads when I swapped.
Same problem! Please help!
tobfo1 said:
Hi.
As the title says, I am having problems with freezing/lockups when receiving/sending SMS. It only happens with large message treads (300-800 msgs in tread).
To the problem, when I receive a new SMS and open it to read it, every thing is fine, but when I press the back button to exit, nothing happens for a while, then the screen goes black, and after a while a popup ask to force close or wait for program to respond. This can take from 10-45 seconds, mostly the latter.
If I just enter a msg tread, without recieving a new SMS or sending one, every thing works like a charm.
I am running Leedroid 3.08.02 on a HTC Desire/Bravo. And have 60Mb free memory. Also had this problem in Leedroid 3.07.
Did a full wipe of the phone when upgrading, and then restored my SMS.
PS. I am posting here since newbies arent allowed to post in developers section.
Hope for some smart feedback..
Thxs!
Click to expand...
Click to collapse
Same problem! Please help!
Same problem here, with the same ROM...
I have some similar problems. My phone freezes once a day. Did you try a different radio? I am thinking of doing so.
My GS3 on AT&T with stock ROM keeps having lockup / freeze issues with the stock launcher and email app.
Sometimes when I unlock my phone or hit the home button while in an app the home screen comes up with just a few icons and now icons on the bottom row. It stays like this, unusable and unresponsive, for 20-30 seconds and then the phone seems to reload the launcher and everything is fine.
It is quite a pain.
Also - the stock email app freezes for 30-60 seconds or more after checking my POP account most of the time. It downloads all messages and shows them but freezes and will not let me do anything. I get that wait or force close message after a while. Eventually it starts responding again.
My POP setup has messages left on the server for 3 days so my desktop can always catch up and download the messages permanently. The GS3 email app seems to re-download messages it already received if I delete them too. I am wondering if having 200 - 400 messages on the server is slowing things down even though it downloads the 20-30 new ones pretty quickly.
Any ideas on these lockups?
Have you tried a factory reset and are you current on your updates
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
No and Yes....
DerekPradoFLA said:
Have you tried a factory reset and are you current on your updates
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Have not done a reset....what settings and data are backed up automatically by Google? I'd hate to have to reconfigure everything.
I do have all apps up to date. Phone is not rooted or running any custom ROMS, etc.
This started happening pretty much immediately since I installed the 4.4.3 update late July, and has just gotten worse.
For a single one of my contacts, the SMS app lags HORRIBLY whenever I am doing anything with said person. It takes about half a minute just to load when I click his name, and the phone keeps completely freezing for up to 10-15 seconds EACH letter I type! It's not just the SMS app itself, but even the keyboard freezes up and is unresponsive. I can keep typing and it will apparently actually record the next 30 or so taps and just blaze through them ... then lag for another half minute or so again. None of the settings (how little there are) have had any effect. Once I click send the message also takes a bit before it appears and starts to send. Any action with this contact open in the SMS app seems to lag my phone like a unusable nightmare.
Since this is the person I tend to text the most, I have been tempted to crush the phone in my hand at this point. It is ONLY happening with them, and ONLY after the 4.4.3 update. It's not consistent either; I was still having this issue earlier today, but right now as I wanted to text him again it was working perfectly lag-free.
I know the first response anyone is going to say is to wipe my phone, but with this being the only issue I have, I really do not want to completely obliterate everything and start over from scratch just to fix one person in my SMS app. On top of that, I want to keep my SMS texting history as well. (Plus I would have no idea if restoring a backup wouldn't also restore the issue).
Has anyone else encountered or heard of anything like this? Or has any ideas of anything OTHER than wiping the phone or my SMS history I can try? Considering the app only pre-loads the last 10 or so messages when you open a contact anyway, I highly doubt it's my history. I am going nuts with this stupid thing.
It is probably something in that message thread.
Deleting all messages from that person will surely fix it, based on what you've said.
You can try wiping the messaging apps cache. Other than that, I think you're stuck.
Second the opinion above. If it's only one message thread doing it, seems likely it's something unique to that thread. Too many messages, pics, etc. I used to use Titanium Backup to save messages between rom flashes, back when I cared about them, so a backup app can save the messages, let you delete the thread and see if it still happens with a blank slate.
Hello there,
I am posting this thread with a problem. Roughly a year ago I purchased the HTC M9 (after 2 very satisfied years using the M7). Up untill about a week ago everything was working fine for me, the only small issue I've had so far is the lack of memory space. Although this issue was easily solved by simply upgrading my device using a Sandisk SD card.
However, since a couple of days my device started overheating very quickly and lagging. Again, I tried to fix this by rebooting the phone and using CCleaner to clean up some of the junk on the device. Now here comes the actual problem: this morning I was simply using the Youtube app to watch a video when my device suddenly crashed (with 50% battery life). I plugged my phone into a charger and booted up the device again but I get a an error report saying "Sense Home stopped working", which means I'm currently unable to use my device. For some reason the HTC report function is bugged aswell, as I cannot seem to send an error report to HTC.
Can anybody tell me what is going on here and how I could solve this problem? I'm very dependent on my phone because of university and work and would like to fix this as soon as possible and preferably not with a hard reset.
Thanks in advance.
Okay I went ahead and tried out something myself based on the following on a thread on androidcentral com titled ""Unfortunately, HTC Sense has stopped" loop" (I'm not allowed to post links yet)
So I went to Apps and cleared the cache of the Sense Home app (without being in safe mode). My phone started working again, but I lost alot of information as apps like Whatsapp and Google Chrome are completely reset and I lost my contacts. Is there any way I can fix this process?
I cleared my cache but my device is still keeping me in that damned Loop. I don't want to lose my pictures or videos. What else can I do? I have an HTC One M9.
Solution to Sense Home crash loop
Kamir Tyree said:
I cleared my cache but my device is still keeping me in that damned Loop. I don't want to lose my pictures or videos. What else can I do? I have an HTC One M9.
Click to expand...
Click to collapse
Quoting the page: crowdsupport.telstra dot com dot au/t5/Device-Updates/HTC-M9-Marshmallow-6-0-update-causes-problems/td-p/577965
"Boot the phone as per normal, ignore the "Sense Home has stopped" message for now.
Pull down the notification drawer,
Tap on the cog to get into settings (once in settings clicking ok on the "Sense home has stopped" message should make it dissapear so you can see what you are doing),
Go into Apps,
Go into Sense Home,
Tap on storage,
Tap on "Clear Data".
This will delete all the data stored with the Sense Home app, not your photos or messages of contacts or anything like that.
You will have to re-configure your home screen(s) though :-/
Once you've done that you should be good to go.....You may need to reboot."
I have the same problem which started at the same time.
Tried everything, clearing Sense cache, system cache from recovery, installed custom recovery and Revolution HD rom its all the same... Everytime after few minutes or hours same problem occurs! Loop Sense crashing, rebooting, wifi turning on and off by itself...
Please someone help
Hi guys, I had the same problem just two weeks ago. Tried cache clearing, factory reset, yada yada yada. Despite all the error report pop ups I managed to use Google app to get to play store, and updated sense home from there. That did the trick. I lost all my contacts and apps but still the phone works again.
devinbost said:
Quoting the page: crowdsupport.telstra dot com dot au/t5/Device-Updates/HTC-M9-Marshmallow-6-0-update-causes-problems/td-p/577965
"Boot the phone as per normal, ignore the "Sense Home has stopped" message for now.
Pull down the notification drawer,
Tap on the cog to get into settings (once in settings clicking ok on the "Sense home has stopped" message should make it dissapear so you can see what you are doing),
Go into Apps,
Go into Sense Home,
Tap on storage,
Tap on "Clear Data".
This will delete all the data stored with the Sense Home app, not your photos or messages of contacts or anything like that.
You will have to re-configure your home screen(s) though :-/
Once you've done that you should be good to go.....You may need to reboot."
Click to expand...
Click to collapse
Thanks, great solution, apps and everything still there - I was so worried. For me this problem was a show stopper, do I even consider getting another HTC phone?? Why can't HTC modify Home Sense to disable the alert, once initiated, when the battery is fully charged, then this very annoying, irritating and phone disabling problem would just go away?