-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
i noticed the same thing, along w/ the native message app. there is a problem w/ the scripts continuing to run after you kill them w/ taskiller/task panel/ etc. sprint/google will hopefully recognize this and remedy the situation.
i recently switched to handcent sms after trying chompsms for a week. by disabling the native message app and making sure it's killed, i was able to decrease my awake vs. up time substantially.
however, chomp wasn't sending me mms messages and i would have to resort to the native app to open them. this, obviously, would increase the up time and start the whole problem over.
handcent receives mms messages fine, but even w/ native message app killed, my up time is over 64% and rising
any help?
thanks in advance
i recently switched to handcent sms after trying chompsms for a week. by disabling the native message app and making sure it's killed, i was able to decrease my awake vs. up time substantially.
however, chomp wasn't sending me mms messages and i would have to resort to the native app to open them. this, obviously, would increase the up time and start the whole problem over.
handcent receives mms messages fine, but even w/ native message app killed, my up time is over 64% and rising
any help?
thanks in advance
Edaze55
Android Expert
In all fairness, its always been a GSM Hero forum. The Sprint Hero forum was actually created before the launch of Sprints Hero.
The GSM was added to deter posts for Sprint specific issues in that section since there is a section for Sprint Heros.
deviouskoopa
Newbie
i'm also using handcent now and wondering if there's a way to send/receive sms/mms without the stock messages app running every time, it's kinda annoying to kill constantly. also, do you think some app (stock or even market) is using sprint navigation regularly? if so, we could isolate the app and even stop using it.
i guess i'm just really annoyed by these continually starting apps...
pdragon
Android Enthusiast
As has been said in previous posts, there is no need to be killing the Messages app. As long as you don't send an SMS specifically through it, you won't have the sleep lockout. It may even be part of the core SMS functionality of the phone unless you're using something like chompSMS's own built in SMS service.
deepsouth06
Newbie
did this thread get away from what was really asked. look back at the original post and he is asking why the sprint nav keeps coming back up after the task is being killed.
pdragon
not true. i don't send messages through the native app, i use handcent. and it continually comes on and prevents my phone from sleeping. i have found taskcontrol to be the best solution to remedy this after trying taskpanelx and taskiller. there are numerous posts concerning this issue along with awake/up time. how can you tell devious what is happening with their phone is not happening? you are ignorant to the issue
not true. i don't send messages through the native app, i use handcent. and it continually comes on and prevents my phone from sleeping. i have found taskcontrol to be the best solution to remedy this after trying taskpanelx and taskiller. there are numerous posts concerning this issue along with awake/up time. how can you tell devious what is happening with their phone is not happening? you are ignorant to the issue
pdragon
Android Enthusiast
I'm not any more ignorant than any other user of the phone. Outside of issues confirmed by the phone's developers, none of us know exactly what's causing the non-sleep issue, so we're really all at the same level of ignorance at the moment. I see the Messages program coming on myself as well and I do not kill it and I do not have any sleep problems. I've pretty much stopped using Task Killers all together and I've noticed no difference in the performance of my phone at all. If it is Messages causing it in this case, it's a completely separate issue than the one that is acknowledged by HTC.
What I do know, and has also been found by many other people throughout this forum and the Sprint forums, is that Task Killers themselves are a very large part of the problem of phones not going into sleep modes properly or corrupting the apps themselves. You are preemptively terminating a program outside of its normal means. Just like any normal computer, this in itself can cause many unexpected issues and is never a recommended course of action unless there are no other means available. Most users have absolutely no need to kill the applications they're killing and are just doing so because they see it listed in their Task program and have no real idea what it's actually doing or why it may still be active.
And, from the help that I have been giving people with their phones, a very large majority of users that use a Task Killer are killing apps that SHOULD NOT be killed and are completely neglecting to mention this in any of their panicked postings for help. Once the full scope of people's issues are known, it really seems to be another unmentioned app that they installed causing the issue or killing things they shouldn't kill. Or as has been happening for many people here, it's a defective phone and it needs to be exchanged.
Saltwater Hero
Member
I noticed the same thing also...I keep killing sprint nav and it keeps coming back for no reason.
bottom line: android should have a dedicated/easy way to kill apps. this is the catch 22 of a true multi-tasking phone: webOS has it, even winmo 6.1 has it: when you X out a program it closes and doesn't run in background as has historically been the case.
as far as "panicked" people looking for answers: if apps that are not in use/rarely used (navigator, nfl, tv, messaging, etc) are continually running and consequently draining down a battery that already (more or less: no need to split hairs) needs to be charged every night, it's commonsense that a way to kill what is detrimentally affecting your phone should be easily accessible.
as far as "panicked" people looking for answers: if apps that are not in use/rarely used (navigator, nfl, tv, messaging, etc) are continually running and consequently draining down a battery that already (more or less: no need to split hairs) needs to be charged every night, it's commonsense that a way to kill what is detrimentally affecting your phone should be easily accessible.
I installed the Autostarts app, and it shows that Sprint Navigation and Messages are both set up as startup items under the "SMS received" action.
If you're rooted, the program can be used to disable the startup items. I haven't noticed anything wrong with receiving messages when Sprint Nav is disabled from starting up. However, when Messages is disabled I'll get notifications saying I have new texts but they don't show up in Handcent.
marcelo0292
Member
I have been doing some tests, and it appears to me that Sprint navigation only shows up on taskiller when I recieve txt messages...Idk why though