Skip to main content

Timeline for SMS Thread / General Limit?

Current License: CC BY-SA 3.0

14 events
when toggle format what by license comment
Nov 13, 2013 at 7:09 comment added geffchang @David Sure, why not? [But ASE is not a programming site. That would be better off in StackOverflow]
Nov 13, 2013 at 7:08 comment added David @Izzy Oh okay. Just thought you might have meant that was happening to me. But do you think an SMS app, designed (probably on some simple function) to cache a certain number of messages and not load them, would alleviate my problems?
Nov 11, 2013 at 8:02 comment added Izzy @David I didn't mean to say this has to be the reason in your case (and I'm sure geff didn't understand it that way either). We were just completing the list in general, as for a future visitor this might be the crucial point. And it could have been a point in your case, so we wanted to make sure you know it and eventually can either rule it out. Besides: the internal card is of no interest for it, neither is the external card. The insufficient memory error is only related to phone storage (aka "internal storage"), not to any SD/external storage.
Nov 11, 2013 at 6:37 comment added geffchang @David I think the phone can only handle so much (think of PC RAM vs hard disk)
Nov 11, 2013 at 4:35 vote accept David
Nov 11, 2013 at 4:35
Nov 11, 2013 at 3:59 comment added David @Izzy no it isn't. It just REALLY lags the phone / stock SMS app. I have over 10 GB free on my internal SD card (no external slot). I never get the memory issue, just the lag.
Nov 10, 2013 at 14:17 history edited geffchang CC BY-SA 3.0
add update #1
Nov 10, 2013 at 14:11 comment added Izzy One more thing to keep in mind (geff, you might wish to include that directly with your answer) is the storage limit triggering the "insufficient memory" error. If I remember correctly, that would also prevent SMS from being stored (plus the possibility to send some on your own). This error is triggered usually when there's less than ~25 MB free space on internal storage.
Nov 10, 2013 at 13:52 comment added David well yeah I could always backup and store somewhere. But I haven't found a solution for that which I like, yet. I just think, that even how absurd the message count is, the app should be able to handle it. Every message already sent or received won't change, so there is no need to load the first x amount of messages after a thread hits x length.
Nov 10, 2013 at 12:50 comment added geffchang @David I have no idea. You'd have to check the play store for that. 100K seems overkill to me though. I normally delete my conversations after some time, or back-up those that are important to me.
Nov 10, 2013 at 11:25 comment added David I thought of that as well. Is there an app, that you know of, that would, cache x amount of the messages, only loading them if specifically called upon? Like if I kept scrolling up in the conversation, and hit a "load more" option? That seems like a simple enough fix for large SMS threads, no?
Nov 10, 2013 at 11:08 comment added geffchang @David I would assume this would be more of a hardware issue. On a PC, just try opening a really large text file (maybe 2-5GB) on Notepad, on an average PC. I think it would crash.
Nov 10, 2013 at 11:06 comment added David Well, I have ALMOST 100,000 SMS in one thread. I currently use Hangouts with the new SMS integration, but previously had to use GoSMS. GoSMS would be a little sluggish, and annoying. But, in the stock SMS app, I could load it one time, tap the big thread, and it wouldn't load. Then when I went back to the thread view, it wouldn't load. I don't want to delete them, and I won't. Just wondering why that happens, and if there is a limit in Android/OEMs. Also: I am rooted running a CM 10.1.
Nov 10, 2013 at 10:49 history answered geffchang CC BY-SA 3.0