When i try to delete a threads, handcent crashes. the reason i want to delete threads is because i believe my conversations of upwards 2000 messages are slowing down the handcent performance and therefore my phone >
anyone else have this problem or know a way to delete all that garbage?
View 2 Replies
I want to clean format my phone. Is there a way to save/backup my saved texts in Handcent prior to wiping?
View 2 Replies View RelatedI have had the 'low memory' notification on my phone for a while, plus Handcent has been extremely laggy lately... so I decided to delete some of my SMS as I have never deleted them and Im sure I have thousands...
I have tried to delete the threads in handcent, force delete in handcent, and delete in the stock messages app.. and every single time the phone winds up hanging and eventually the program will FC.
is there a way to delete threaded messages, similar to if you wanted to delete emails? like if i have 20 text threads, and only wanna delete 10.. but do all 10 at the same time..
View 1 Replies View RelatedI searched the forum but couldn't seem to find an answer relating to the Hero. Im trying to delete large sms threads (700+ messages) but have been unable to do it. Basically nothing happens and if I keep pressing 'delete all threads' the phone just freezes. I have tried it then left the phone overnight to see if it just needed time, I have also tried keeping the backlight constantly lit for around 15 mins in case that affects it but still nothing. Any suggestions? I am using handscent if that makes any difference.
View 4 Replies View RelatedAnyway to auto delete the message threads?
View 2 Replies View RelatedI have been searching but so far have not found the answer to this question: is there an app to automatically delete threads when they get to a certain length or if they have been inactive past a certain date?
My old phone just autodeleted the oldest text once you got past 100, and while it is nice to have more memory than that I do not want to go through my threads and manually delete them to stop them from taking up too much memory. anyone know/use such an app?
Just switched from the iPhone 4S to the Galaxy S3. I wanted to transfer my small handful of text messages from the iPhone to the S3. I found an app called iSMS Grab, and was able to accomplish this pretty easily. However, now the stock messaging app seems sluggish and, when I try to delete older threads, they just won't delete. I've tried doing so with a long press and thru the Menu button. I then uninstalled the iSMS Grab app, cleared data thru Settings > Apps > Messaging > Clear Data, formatted the microSD card, and even removed the SD card - and they still won't delete!
I know the ultimate fix is a factory reset, but I have over 1100 contacts that I've spent a full day configuring ringtones and Caller ID photos. I'll reset if I must, but hopefully I can get some feedback from experienced users here. This is my first day with an Android phone.
I've only just got this phone today, and have no idea how to delete text threads!
View 1 Replies View RelatedFirst of all I am very pleased with the Droid (including the keyboard) and Android OS 2.0. Have been playing with it since december 13th and I especially love the texting app. In my home, Berkeley CA, it worked great, but now in Puerto Rico there seem to be some glitches. I turned off the auto delete messages because I prefer that. Not sure if its because I disabled the auto delete or because I am in Puerto Rico, but randomly when I go to my texting app, all my threads will be gone. This has happened to me twice now within a week.
View 7 Replies View RelatedI am trying to delete large text messaging threads in the stock messaging app on my Sprint HTC Hero. It is taking an inordinate amount of time to accomplish this task. I deleted one thread that had a mere fifteen texts in and that took over ten seconds. Now, I just tried deleting a thread that has one hundred texts in and it has been minutes and it still has not deleted the thread. Has this happened to anyone else? Would deleting the data in the "Manage Applications" section delete these texts faster or would that be inadvisable? In my opinion this deletion lag is ridiculous.
View 10 Replies View RelatedHave a problem with the DX. Hopefully someone can help. I have deleted several of my text message threads but they show up in my contact history and I cant get rid of them how do I permanently get rid of them . where they show up in contact history is if you delete a text thread and then you go to that persons contact info and swipe left 3 times the text thread is there , how do you delete this from this location ?
View 2 Replies View RelatedWhat are the advantages/disadvantages in placing a lengthy network access code in a thread in an activity or a thread in a service? How would it affect the application? I am writing a streaming audio player and from what I've read so far putting the code in a service will still end up blocking the application so a new thread is needed, does anyone know if it makes more sense to put this piece of code in a service.
View 1 Replies View RelatedI'm trying to clear all text bc my phone is getting laggy when I try to text. SO now my phone keeps freezing up when I open text. This happened to anyone?
View 3 Replies View RelatedI just recently got my HTC hero and I have a question about the messaging app. First of all, I am currently using Handcent mainly because if you use the stock app, texts always show up on the lock screen even if you are using the pattern lock. That is annoying, and I don't understand what the point of the pattern lock is if you can just see my texts without having to even unlock my phone...anyway, so I am using handcent and it's fine. I've made sure to remove notifications on the stock app so that I don't get double notifications, but my question is: is there a way to delete the stock app? I mean is the phone going to slow down since it is getting texts from 2 apps, does that make sense? Even though the notifications are disabled for the stock app, the texts still go there and they are also going to handcent...
So basically i would like to know if:
1. i can delete the stock app (i have rooted my phone so...)
2. does it matter that the phone is pulling texts to two different apps
3. is there a way to make my texts not go to my lock screen, if so i would just not use handcent
Finally, on handcent, i will oftentimes get a text twice from people. does anyone have this problem?
when the stock Messaging app wasn't cutting it, I installed Handcent.But it started flaking out on me, so I dumped it and went to the more-reliable chompSMS.I liked it a lot.But to be completely honest, I missed some of the features of Handcent. But reliability is Job 1, so I kept chompSMS for a few weeks.Then I heard that Handcent received a major update a few days ago, so I replaced chompSMS with Handcent. So far so good. I got all the features back, and I haven't had one single issue in days of texting. So if you're like me and you left Handcent for chompSMS, you may want to give the new version a spin.
View 49 Replies View RelatedWe are in the process of refitting some of our recievers and services with IntentServices (mostly to address rare ANR issues - and because IntentService is pretty cool...). In one case we are converting a traditional service to an IntentService. The original service fired off a few methods whose job was to download data from our servers. Each of these requests would spawn a thread of their own to do the work (apparently not fast enough to avoid the occasional ANR). So now we have a question concerning the life cycle of these processes.
For example, the following situation demonstrates what is happening:
- Start Intent Service - Trigger Download1 - Download 1 thread starts - End Intent Service
- Download 1 thread continues..... - Download 1 thread ends
Our question concerns our exposure to the OS shutting down the Download 1 thread because the Intent Service has terminated before it finishes up. Not sure if it is becomes more or less likely that the OS will view it as something that can be flushed.
If the Download 1 thread is more likely to be flushed by OS we will need to take a different approach.
I am working on a simple application (studying purposes) which list all the files from a selected folder. On top of that I would like to have a search feature where the user can search for files (the code for that is already in place). Now, I was thinking about having the search running in the background somehow, whilst the user can still navigate, create folders, copy, sort and do other stuffs normally. When the search finishes the user would get a notification and then could click on it and go to that activity (It ideally should be the same ListView I already use for browsing the files, I would just need to update the Adapter there with the latest processed data after clicking in the notification). What's the best answer for that? Threading or AsyncTask?
View 4 Replies View RelatedI'm trying to understand the idea behind the Services. If it runs in the program's thread, why not create just a separate thread (or AsyncTask) to do the job? Can a service keep running in the background? For example, i want to create a task that will continuously be polling data from a server, even if the main application is not running. Can this be achieved with a Service?
View 8 Replies View Relatedwhile debugging and app that uses AsyncTask to record audio and update UI I noticed that everytime that an AsyncTask object ends running (finishes doInBackground and onPostExecute or on Cancelled it´s thread stays alive (running status).At least for me that should not be the behavior of the class since the doInBackground task may not stay running forever (as an example the android manual says that a status bar should be updated by an asynctask, and it won´t last for the whole app running time).Is there anything I´m missing, as a method to destroy it, or should I just ignore and keep creating threads as I need and the VM will handle them as it needs resources?
View 9 Replies View Relatedhow do i save certain threads?
View 1 Replies View RelatedAs my app matures, I find myself finding more and more uses for threads. By now I must have about 25 threads, all doing important things and working together in symphony.
I notice however that my app is sitting around 15.5MB resident. Compared to the browser (+/-35MB) I feel pretty safe, but I do notice the resident size of my app ever increasing.
The question is, how much overhead is involved with adding a thread?
I'm also wondering if the synchronized keyword encounters more and more latency with each new thread that is present?
I have an activity that uses a Timer (java.util.Timer) to control the display. I set it off to repeat its run() method every second or so. When it runs, it updates some View elements.
As Timer runs in its own thread, I assumed this would be reliable. But I notice that sometimes there is a stutter, or delay, in the views updating. It's like they occasionally get stacked up, and all happen together. Studying the output from logcat, I notice that this happens when the device is doing something else - some system functions, or sometimes a garbage collection.
How can I avoid this? I'm not aware I can run the main activity in a thread of its own, can I? If the timer has its own thread, why is it affected?
We are developing an application that needs to suspend and resume threads like a debugger (meaning in a non-safe way like Object.wait() and Object.notify()).In the Java SDK the methods Thread.suspend() and Thread.resume() are deprecated but we can still use them. Also there is the Java debugger API which allows one to do that if you connect to the VM as a debugger. Is there some API for android we can use? Is there a published Java Debugger API we can apply for Android?
View 2 Replies View RelatedI have a question about the background thread handling change that went into SDK 1.6. I read here that BG threads get placed in a scheduling class that can't use more than 5-10% of the CPU in order to keep the foreground responsive. Do system services get into that scheduling class?
My app uses repeating alarms. It was great with 1.5, very reliable. Since the upgrade to 1.6, the phone seems to be dropping some of my repeating broadcasts, especially if I am doing something fun in the foreground like with WIFI when the Alarm is supposed to fire. I do not have any of the task killer programs that have been a hot topic lately. To be clear, the dropped alarm broadcast behavior is intermittent. I am not 100% sure if I really am doing something when it has failed. If the timer is a one shot, it seems to work better but there is no real empirical evidence here. My phone is usually in my pocket when I fire one of the one shot alarms. If my theory about system services in the background scheduling class is correct, then I probably cannot find a workaround or defensively code a solution. Will it be the same in 2.0?
Have others seen issues with alarms and with the setRepeating method? I am looking for suggestions to troubleshoot this problem. How can I determine if the problem is the broadcast, if it is the repeating alarm creation, or if there is some other issue like low memory coming in to play.
I have a couple of worker threads in my app which I stop and restart during onPause() and onResume(). I use a method that clears all the reference to and from the threads when stopping. However ThreadGroup is still retaining a reference to my threads and causing a small memory leak. After pausing and resuming my app about 40 to 50 times I will then get OutOfMemory Errors when loading bitmaps. Allthough this doesn't effect most of my users I do get occasional reports of crashes. How can I remove the references to my threads from ThreadGroup so that GC can do it's job.
View 4 Replies View RelatedCurrently I have two threads, other than the UI thread, which need to communicate with each other. Thread one needs to be able to send messages directly to thread two, and vice versa. What is the best way to implement this?
At the minute, my code looks like this...
I'm writing a live wallpaper, and I'm forking off two separate threads in my main wallpaper service. One updates, and the other draws. I was under the impression that once you call thread.start(), it took care of everything for you, but after some trial and error, it seems that if I want my update and draw threads to keep running, I have to manually keep calling their run() methods? In other words, instead of calling start() on both threads and forgetting, I have to manually set up a delayed handler event that calls thread.run() on both the update and draw threads every 16 milliseconds. Is this the correct way of having a long running thread?
Also, to kill threads, I'm just setting them to be daemons, then nulling them out. Is this method ok? Most examples I see use some sort of join() / interrupt() in a while loop. I don't understand that one...
I have two questions about sensor listeners
1. from which thread are sensor values updated and should this be synchronized? can sensor's listener callback be a good place to call custom's view onDraw method? as this should be done from different thread. I cant find anything about it. In another words my problem is that I want to listen to sensors change and draw something on view surface but I dont know which thread (the main thread of the application?) is updating sensor's state
2. If I register sensor listener with SENSOR_DELAY_FASTEST my application is not responsive at all! Raw application with TextView only is not reacting to go back or home button! How should I deal with this or am I doing something wrong?
Trying to understand the Android framework model. I have an application that needs to have several threads running. On thread gets GPS fixes, another picks up GPS fixes and pushes them to server, and yet another occasionally polls a server for dispatched orders. Some of these threads update status Views as well.
Since I am new to Android, the application framework model hasn't clicked for me. Where are these threads started? Right now I start the threads in the initial Activity, but if I understand it right, once that Activity goes invisible it is stopped. Furthermore, I have to track GPS and network statistics so that I can have a View which may (or may not) be the active View.