Database Info

Disable Google Voice

Hi Guys
Is there a way to disable Google Voice in Nexus One in non-Rooted devices? Google results are not useful.
I don't want this application to run in the background. It restarts even if you kill it.

read up on how android handles memory allocation.

maybe you can help me and show me where to read?

henihazbay said:
maybe you can help me and show me where to read?
Click to expand...
Click to collapse
Here you go. Highlights are at the bottom of my post and of the article.
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
*Android is hard coded to automatically kill a task when more memory is needed.
*Android is hard coded to automatically kill a task when it’s done doing what it needs to do.
*Android is hard coded to automatically kill a task when you haven’t returned to it in a long time.
*Most services (while possibly running in the background) use very little memory when not actively doing something.
*A content provider is only doing something when there is a notification for it to give. Otherwise it uses very little memory.
*Killing a process when it isn’t ready only causes it to have to reload itself and start from scratch when it’s needed again.
*Because a task is likely running in the background for a reason, killing it will only cause it to re-spawn as soon as the activity that was using it looks for it again. And it will just have to start over again.
*Killing certain processes can have undesirable side effects. Not receiving text messages, alarms not going off, and force closes just to name a few.
*The only true way to prevent something from running at all on your phone would be to uninstall the .apk.
*Most applications will exit themselves if you get out of it by hitting “back” until it closes rather than hitting the “home” button. But even with hitting home, Android will eventually kill it once it’s been in the background for a while.

Thanks for the reply.
Most of those highlights are not valid for me or for any nexus one users because:
a lot of unused application cause a big amount of RAM which is resulting with a lag/slower N1
Some applications will never be used by some users, for example Amazon MP3, or Google voice (for me)
So, coming to my initial question, is there a way to disable Google Voice?

I guess the simplest way is modacos kitchen. There is a option (?) to remove google voice.
And i agree that removing unneeded apps will improve performance.

any other ideas?

I have just deleted the apk from /system/app
;-)

when i go to /system/app and try to delete amazon MP3 it gives me an error...
i do see that it is -r- (i assume that means read only) is there a way to override that?

Either root and delete the .apk via adb, or you're out of luck.

jn_vista said:
when i go to /system/app and try to delete amazon MP3 it gives me an error...
i do see that it is -r- (i assume that means read only) is there a way to override that?
Click to expand...
Click to collapse
Is your device rooted?

no root, no delete

jin1207 said:
no root, no delete
Click to expand...
Click to collapse
Exactly. This forum isn't really the place for anyone who doesn't have or want root. Pretty much everything we do here requires root access.

Part Four said:
Exactly. This forum isn't really the place for anyone who doesn't have or want root. Pretty much everything we do here requires root access.
Click to expand...
Click to collapse
Agreed! Be rooted and do what mod you want to do...

Out of curiosity, with the Nexus, with GoogleVoice running how much free memory do you have? As Cy would say, "free memory is wasted memory." Why kill the app if it's not draining the memory that's needed?

So Carloswithac, that means ("taskiller", "advanced task killer", etc) are practically useless??
If so I'm uninstalling them From My Nexus.

Advanced Task Killer free is killing HTC Sense

On my HTC legend, i've installed Advanced Task Killer free, and when using the widget, it sometimes kills HTC sense. Anyone know how to add Sense to the ignore list?
Posting this on the Android forum, and not only Legend since I would think this apply to all Android devices with HTC sense

arxx said:
On my HTC legend, i've installed Advanced Task Killer free, and when using the widget, it sometimes kills HTC sense. Anyone know how to add Sense to the ignore list?
Posting this on the Android forum, and not only Legend since I would think this apply to all Android devices with HTC sense
Click to expand...
Click to collapse
well that happened to me on my hero try hiding the mail application because that is somehow connected to sense worked for me

toomie05 said:
well that happened to me on my hero try hiding the mail application because that is somehow connected to sense worked for me
Click to expand...
Click to collapse
Thanks, i'll try that
Gmail or exchange app?

There's a very simple solution, stop using task killers; they are completely and utterly pointless on Android.
Android's memory management is NOTHING like Windows Mobile. On there, apps keep running when you "exit" then, and don't close when other apps need their resources. On Android, apps stay in RAM in case you want to reuse them BUT, if something else needs their resources, or they've been inactive too long, Android itself will close them.
If the app is in RAM, odds are something is using it. So if you kill it, whatever is using it has to reload it all over again and that seriously kills your performance.
Stop using the things, seriously. After a couple of days, you'll be glad you did.

Agree with floatingfatman, all task killers do is slow sense down it needs all the processes to run correctly

I'll answer.
Open the Task killer and long hold on TouchFlo and choose ignore.

i use it with no problems. I found that if you take the mail widget off and then replace it it worls. Or just ignoring the mail on adv task killer. But it saves m,e a lot of battery life

arxx said:
Thanks, i'll try that
Gmail or exchange app?
Click to expand...
Click to collapse
Use htc stock so i think exchange app

Use one that doesn't suck, like TaskPanel.

I dont even know why you bother useing a task killer. I have had my phone a week now and didnt need one, until i read about it. Then i decided to install it and it just kept messing up programs (crashing, making sync stop etc) so i stoped using it.
Tbh, you dont need a task killer android release memory to apps that need it and they dont take cpu/battery either. Only thing you get by useing a task killer is programs that behave badly and might even crash the OS itself.
So dont just use it. They are all useing a exploit in the API for the programs and is not recomended or supported by neither google or android OS.

Yes, Android does good job on memory management, but however, many background apps/services will access Internet/sync from time to time, thus killing your battery, and that's why ATK does the magic. It might not apply to everyone, as not everyone are using the same apps.

Albert Poon said:
Yes, Android does good job on memory management, but however, many background apps/services will access Internet/sync from time to time, thus killing your battery, and that's why ATK does the magic. It might not apply to everyone, as not everyone are using the same apps.
Click to expand...
Click to collapse
Maybe you can reschedule the background apps/ services to longer update instead of killing them all the time. Or instead try other apps like "Active Apps" /"Watchdog" which shows you what are necessary to kill rather than blindly killing them.

[Q] how do you close apps?

so i found out how to force close apps under settings but theres gotta be a better way.
for example lets say i have browser, market, and facebook apps open. all showing under the window selection button. after time i get a ton of windows there and i don't want all of them open. how do i close them selectively without going through all the settings menu crud?
some apps let me close from within, most don't though and leave me stuck with a ton of windows (apps) open.

What you are asking isn't necessary unless an application has malfunctioned. There is no other way to close applications other than using the force close button in settings. Android handles this itself -- if this doesn't satisfy you download a task manager.

I don't think there is a way yet.
What Google needs to do is make those preview windows in the multitasking bar long-pressable for a menu to be able to close them.

modru2004 said:
so i found out how to force close apps under settings but theres gotta be a better way.
for example lets say i have browser, market, and facebook apps open. all showing under the window selection button. after time i get a ton of windows there and i don't want all of them open. how do i close them selectively without going through all the settings menu crud?
some apps let me close from within, most don't though and leave me stuck with a ton of windows (apps) open.
Click to expand...
Click to collapse
There is no need to manually close out apps. Since 2.1, Android has done an excellent job managing memory. It's been written many times (some directly from Google) that micromanaging your apps will actually hurt battery performance. You'll essentially be working against the system as opposed to helping it.

I am not sure if my task manager is working on this device. I use AutoKiller and when I killed task it doesn't appear as though anything closes. Can somebody confirm?

atoy74 said:
There is no need to manually close out apps. Since 2.1, Android has done an excellent job managing memory. It's been written many times (some directly from Google) that micromanaging your apps will actually hurt battery performance. You'll essentially be working against the system as opposed to helping it.
Click to expand...
Click to collapse
id like to point out thats NOT the issue.
the issue is the ton of windows you end up having to sort through unless you close them. its a quality of life thing, i don't like having unused unnecessary windows open that i have to sort through to get to the stuff i am using. its just bad form.

foldog22 said:
I am not sure if my task manager is working on this device. I use AutoKiller and when I killed task it doesn't appear as though anything closes. Can somebody confirm?
Click to expand...
Click to collapse
It will most likely not work until its rewritten. The way 2.2 and now 3.0 allow access is completely different then 2.1 and below. Plus as said about 200 million task there is 0 reason to run a task killer. If you wanna clear them out, even though there is 0 reason, reboot.

Okay, I get the memory management issue, but as the OP pointed out, I've got all sorts of icons in the "task bar area" (bottom right hand corner) that just sit there or keep coming back.
For example, I haven't listened to any music on my Xoom since yesterday morning, yet I've got an icon down there for Music and Rhapsody. Also, there's no way to clear some notifications.
There's got to be a way to at least clear out the notification isn't there?

you tap on the little icon music for example and you will see a little x on the right of it, click that and it closes it from the notification system

There is absolutely no reason to use a task killer or manually kill tasks. 2.2, 2.3, 3.0, etc. handle memory and tasks extremely well. In many cases, task killers will only cost you more battery and more slowdowns than letting tasks just run out and sit in memory. Unless you're seeing rogue or malfunctioning tasks in the background causing slowdowns, there is no need to kill them.
I do wish you could scroll through the recent running apps rather than only being able to access the latest 5, but spam closing background apps doesnt help at all.

arrtoodeetoo said:
I don't think there is a way yet.
What Google needs to do is make those preview windows in the multitasking bar long-pressable for a menu to be able to close them.
Click to expand...
Click to collapse
While I haven't used a task manager since I started learning how android actually works last year when starting to make apps, I can't help but want the same thing in honeycomb for malfunctioning apps. I think google left it out intentionally to discourage task-killing rampages by oblivious users.

Every time I read "you do not need to close apps" I want to scream. first hour of usage I had a second browser installed and it and the stock browser were conflicting with each other... all I wanted to do was a quick close of one of the browsers.
There are always a multitude of good reasons to want to close a background app. I completely understand the technical reasons why an app does not need to be closed, but from a user experience point of view, it should be made simple.

mjpacheco said:
Every time I read "you do not need to close apps" I want to scream. first hour of usage I had a second browser installed and it and the stock browser were conflicting with each other... all I wanted to do was a quick close of one of the browsers.
There are always a multitude of good reasons to want to close a background app. I completely understand the technical reasons why an app does not need to be closed, but from a user experience point of view, it should be made simple.
Click to expand...
Click to collapse
Which is exactly why in my first post I said "...isn't necessary unless an application has malfunctioned" otherwise such a thing is barely necessary. And in your case, the classic "Settings > ....... > Force Close" would have easily sufficed.

So what you are saying is that a method to kill tasks is necessary, just not often. I, for instance, just had the xda app stuck on the splash screen. I killed it and restarted the app and all was good. There is a potential for harm if used over zealously but at times it would be nice if there was a more convenient way to close an app when necessary.
Applications do not always behave as they should so to say there is no need to kill am app is making a naive assumption that every android app is perfect.
Sent from my Xoom using XDA App

martonikaj said:
I do wish you could scroll through the recent running apps rather than only being able to access the latest 5, but spam closing background apps doesnt help at all.
Click to expand...
Click to collapse
Oddly enough, if you turn to portrait, you get a few more. So, technically its not a hard limit on 5, but rather (literally) limited by space on the screen.
Anyone want to place a bet as to what rev we see scrollability?
Sent from my Evo using the XDA App

JanetPanic said:
So what you are saying is that a method to kill tasks is necessary, just not often. I, for instance, just had the xda app stuck on the splash screen. I killed it and restarted the app and all was good. There is a potential for harm if used over zealously but at times it would be nice if there was a more convenient way to close an app when necessary.
Applications do not always behave as they should so to say there is no need to kill am app is making a naive assumption that every android app is perfect.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
If this happens use the built in task killer, settings/applications/running tab.
Sent from my PC36100 using Tapatalk

bwcorvus said:
If this happens use the built in task killer, settings/applications/running tab.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
I did and it worked. As I said it would be nice to have a more convenient way of force stopping apps that are not behaving.
Sent from my Xoom using XDA App

Closing apps isn't necessary for two reasons.
1. Android does a good job at managing apps on its own.
2. You have 1GB of RAM to work with.
Sent from my HTC Vision using Tapatalk

Watchdog does a considerable job since it only lets you know when an app is misbehaving. And since being on 2.3 its barely given me any alerts. Perhaps further proving the awesome memory management.
Sent from my Xperia X10 using XDA App

delete please

Available memory and tasks

This is my 4th Android phone, and I am still a little unclear on how memory works on this machine. I use AutoKiller, yet I am still confused. As I understand it, 100mb or 5mb free, it shouldn't affect the operation of the device until something needs more than the available and has to clear room. So, how does this work, exactly? I am continually running low on the Triumph, yet if I set the preset in AutoKiller higher, I begin to lose services ranging from alarm clocks to social networking notifications. Where do I begin to find balance? Am I missing something?

I haven't had a problem with starting to lose services like the alarm clock but I was seeing the system significantly slow down even as I kept all unnecessary tasks from running. So I figured that I would root my system, and get rid of all the pre-installed software that I didn't use. The funny thing is that after I rooted the system all the memory issues went away, and the system really flies now. I don't know what changed, when I rooted it. But I am not seeing the same slow responses, the constant starting of tasks that I don't use and so forth. I know that its not an answer so to say, but I thought that I would share so as to maybe help you, or see if it happened with someone else.

HitchHiker said:
I haven't had a problem with starting to lose services like the alarm clock but I was seeing the system significantly slow down even as I kept all unnecessary tasks from running. So I figured that I would root my system, and get rid of all the pre-installed software that I didn't use. The funny thing is that after I rooted the system all the memory issues went away, and the system really flies now. I don't know what changed, when I rooted it. But I am not seeing the same slow responses, the constant starting of tasks that I don't use and so forth. I know that its not an answer so to say, but I thought that I would share so as to maybe help you, or see if it happened with someone else.
Click to expand...
Click to collapse
Thanks for the reply. It's nice to hear other experiences. I am already rooted, and AutoKiller requires root. I'm just being patient and hoping that a custom ROM can solve problems.

Rooting shouldn't change anything except whether or not the phone is rooted. That's it. Task killers rarely help because those apps you kill just come back as soon as you look away. So I would personally recommend you only kill the miscreant apps, and ultimately remove them if you can.
Sent from my Frankenphone using Tapatalk

primetechv2 said:
Rooting shouldn't change anything except whether or not the phone is rooted. That's it. Task killers rarely help because those apps you kill just come back as soon as you look away. So I would personally recommend you only kill the miscreant apps, and ultimately remove them if you can.
Sent from my Frankenphone using Tapatalk
Click to expand...
Click to collapse
Autokiller doesn't work that way. It merely changes Android's already existing internal programming to be a touch more aggressive. It does nothing on its own, merely giving you an interface to alter Android's own values for task management and app priority.
What I really need to know is if that aggression is necessary. Android's default minimum for memory is 24mb (that is the level at which the system will kill off empty apps). I can raise that number, but is it necessary? Some one told me that free memory amount is irrelevant in Android. If that's true, what is the point in making sure my system has 100mb free as opposed to 20mb?

I wouldn't think that extra memory management app is necessary, the only problems any android 2.2 phone (or any android) has are apps that are coded porely are installed. Just use a app that shows cpu usage. If a app is porely written you will see it..... those are the ones to uninstall.....not kill, uninstall.

tsac said:
I wouldn't think that extra memory management app is necessary, the only problems any android 2.2 phone (or any android) has are apps that are coded porely are installed. Just use a app that shows cpu usage. If a app is porely written you will see it..... those are the ones to uninstall.....not kill, uninstall.
Click to expand...
Click to collapse
Like I said, the app merely gives me a UI to alter Android's already existing internal programming in regards to service priority. I am just trying to better understand how Android does it's work.

2.21.401.10 and still multitasking issue?

So, I've heard the new update 2.21.401.10 still has the well known limited multitasking issues (see YT videos for One X, it's the same for us: http://www.youtube.com/results?sear...0.0.0.119.352.3j1.4.0...0.0...1ac.R68YKWQ8QnE )?? Is it true? How can we persuade HTC to keep standard Android multitasking?
I've also heard the audio issues (crackles, trashed sounds, some micro-stutters sound-related. You can easily notice this with games, f.e. Pinball Arcade or Mame4Droid etc. Won't hear these problems on GS2 and other Android phones) are still there too, so the audio driver is still the same.
Should I go back to GS2? Multitasking problem is very important for me...

I don't have issues with sound now, never have. A lot of games ether aren't compatible completely (gta 3), and others are just trash audio. If you want to test audio run a GOOD mp3 file, if it crackles its your phone....
Sent from my HTC One S running Axiom S

the multitasking of the one X and S isnt' bugged, it is in this way for a choice of HTC. Basically the system doesn't left completly open apps but it freeze them which is almost the same of restart the app from zero more or less. This is because HTC want to keep some resources free to have a more fluid sense experience.
Anyway if you have an unlocked device you can flash this script http://forum.xda-developers.com/showthread.php?p=27318828#post27318828 that should give you real multitasking and leave the cool HTC interface ( the task manager ) to swith from an app to another. I would try it but I don't want to unlock my device at the moment.

none of the scripts work. wait till developers will fix it on kernel level. no other solutions here.
HTC One S via XDA

hexaae said:
So, I've heard the new update 2.21.401.10 still has the well known limited multitasking issues (see YT videos for One X, it's the same for us: )?? Is it true? How can we persuade HTC to keep standard Android multitasking?
I've also heard the audio issues (crackles, trashed sounds, some micro-stutters sound-related. You can easily notice this with games, f.e. Pinball Arcade or Mame4Droid etc. Won't hear these problems on GS2 and other Android phones) are still there too, so the audio driver is still the same.
Should I go back to GS2? Multitasking problem is very important for me...
Click to expand...
Click to collapse
I agree with hexaae. It's worth nothing having a super-fluid UI if it means killing your opened browser when you try to live it in background. You just can't browse between browser and email: how is this supposed to be called multitasking??
I really believe this choice of HTC's is senseless... On a smartphone with 1GB of RAM...
Edit1: by the way, what is the "background processes limit" option in "development options" supposed to do? Possible values are 0, 1, 2, 3, 4, default.
Edit2: would it be an idea to make a poll and see how many people would be interested in this?

mannequin said:
none of the scripts work. wait till developers will fix it on kernel level. no other solutions here.
HTC One S via XDA
Click to expand...
Click to collapse
why do you say that it doesn't work? On the thread some guys has reported that it works!

light_n_roses said:
why do you say that it doesn't work? On the thread some guys has reported that it works!
Click to expand...
Click to collapse
It worked for me, problem was the battery started draining like crazy. Which got me thinking, the reason HTC did this was battery life. Nothing else. Sense was still just as smooth for me, but apps would multi task like I used to, but my battery would last less than half as long. So I went back to stock and am getting decent battle life again.
Sent from my H1S using XDA Premium.

MadJoe said:
It worked for me, problem was the battery started draining like crazy. Which got me thinking, the reason HTC did this was battery life. Nothing else. Sense was still just as smooth for me, but apps would multi task like I used to, but my battery would last less than half as long. So I went back to stock and am getting decent battle life again.
Sent from my H1S using XDA Premium.
Click to expand...
Click to collapse
Well this is quite natural, you should manually clear everything once that you put the phone on stand-by ( and here the cool HTC task manager interface lack of a " close all" button ) or if you don't want to do this you can put task killer widget on the home that kill everything by a tap. Anyway this would kill also the background process not started by you which is not good so HTC should really put a "close everything" button on task manager interface so we can kill just recent apps opened by the user and not from the system.
Sent from my HTC One S using xda app-developers app

it works for about "10 minutes". all script "fixes" are nothing more than a placebo.

mannequin said:
it works for about "10 minutes". all script "fixes" are nothing more than a placebo.
Click to expand...
Click to collapse
That is not true. Yes, the multitasking is not stock quality... but the scripts do have a noticeable effect that improves performance (assuming you have enough free memory).

mannequin said:
it works for about "10 minutes". all script "fixes" are nothing more than a placebo.
Click to expand...
Click to collapse
this shouldn't be a script ment to improove performance, this should be something that it works or not, an off/on ...

light_n_roses said:
Well this is quite natural, you should manually clear everything once that you put the phone on stand-by ( and here the cool HTC task manager interface lack of a " close all" button ) or if you don't want to do this you can put task killer widget on the home that kill everything by a tap. Anyway this would kill also the background process not started by you which is not good so HTC should really put a "close everything" button on task manager interface so we can kill just recent apps opened by the user and not from the system.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
It lacks the close all option because it is not needed. You dont have to close any apps unless they are something that need to be operating all the time like music player when it is playing songs or navigator and stuff like that. There is no difference for your batterylife whether you clear the "recent apps" list or not. And its called "recent apps" for a reason because it means that it has nothing to do with the fact is that application actually running or not. It has always being like that in android. It just makes it easier to jump between apps.
Using task killers and such only increases battery usage since the app it has closed needs to be loaded again when you use it the next time instead of it being just unfreezed from the memory.
HTC has set the automatic killer which kills apps on the background when running out of memory way too aggressive when you compare that to how it works on vanilla ICS or even older HTC phones running android 2.2 or 2.3.
However the latest update made multitask way better for One S. And Iam talking about the one which updatet android version to 4.0.4. Now you can jump between many apps without the fear of them closing immediately so Iam very happy with that now and it works as its should be.

Paqu1 said:
However the latest update made multitask way better for One S. And Iam talking about the one which updatet android version to 4.0.4. Now you can jump between many apps without the fear of them closing immediately so Iam very happy with that now and it works as its should be.
Click to expand...
Click to collapse
I've read comments by users who installed latest update and still have the limited multitasking issue (I'm waiting for the OTA update in Italy). Are you saying instead this has been "fixed"...?

Moved To Q&A​
Please post all questions in the Q&A section​

hexaae said:
I've read comments by users who installed latest update and still have the limited multitasking issue (I'm waiting for the OTA update in Italy). Are you saying instead this has been "fixed"...?
Click to expand...
Click to collapse
Well its working fine for me. I can now jump between 4-6 fairly light programs and 2-3 heavier ones without the previous app always closing like before the update.

Paqu1 said:
Well its working fine for me. I can now jump between 4-6 fairly light programs and 2-3 heavier ones without the previous app always closing like before the update.
Click to expand...
Click to collapse
Actually I still don't know because I do not have the last updated, I'm waiting that it goes online on automatic update.....
Hope you are right!

Paqu1 said:
Well its working fine for me. I can now jump between 4-6 fairly light programs and 2-3 heavier ones without the previous app always closing like before the update.
Click to expand...
Click to collapse
Please can you test this?
Open Google in the stock browser and type in something to search (but don't start searching!)... then switch between other apps and finally go back to the browser. Does it still reload and delete your input text?

I'm going to test the script now. Available memory is not an issue for me, as I removed Sense and am running Nova Launcher. My available memory usually sits around +230, ranging from 170-270. Haven't seen it drop below that. As for battery life, as long as you actually use the HTC multitask button and kill the apps that you don't want to go back to, the battery shouldn't really be affected, or at least the only effect will be a result of the apps that you actually want running, so it's a trade off, right? Keep in mind that means not killing the processes that will be automatically restarted by Android (ie using an auto task killer, or some pre Froyo type apps), only user apps that you recently launched and are now killing.

tgtoys said:
As for battery life, as long as you actually use the HTC multitask button and kill the apps that you don't want to go back to, the battery shouldn't really be affected, or at least the only effect will be a result of the apps that you actually want running, so it's a trade off, right? Keep in mind that means not killing the processes that will be automatically restarted by Android (ie using an auto task killer, or some pre Froyo type apps), only user apps that you recently launched and are now killing.
Click to expand...
Click to collapse
Oh god, didn't I just explained this few post earlier? You dont have to do any of that since it DOESNT have any impact to your battery life. Go ahead and test it if you dont believe me.
hexaae said:
Please can you test this?
Open Google in the stock browser and type in something to search (but don't start searching!)... then switch between other apps and finally go back to the browser. Does it still reload and delete your input text?
Click to expand...
Click to collapse
Ok, I just did what you asked. After doing that with the default browser I was able to jump between Dolphin HD which had two tabs open, youtube app and chrome without any of them closing. And I even went to home screen between them. I think thats pretty good compared how it worked previously. Because then often it was enough if I just jumped to homescreen and then right back the previous app to make it close.

Confirmed.
Official stock ROM, via OTA, ver. 2.31.401.5... and there IS multitasking, finally! Task manager is much more conservative (around 70-80% of cases) with executed apps in the multitasking-history-menu...
Yes, also the browser now won't reload pages if you switch to the mail app for a moment and go back...
~200MB free mem.