[Q] Nook App's Battery Drain in Tab 4 Nook - Galaxy Tab 4 Q&A, Help & Troubleshooting

I noticed from reading the Battery Widget's stats that the Nook app (com.nook.app) on my Tab 4 Nook is using a lot of battery running in the background -- even though I have not used the app at all and have not bothered to sign in to my BN account!.
Is there any mean to mitigate this, short of rooting the device and disabling the app?

Just open the app, then press the menu button and it should show all your apps open. Now just hold on the nook app and hit app info. Now you can disable or force stop the app.

DUHAsianSKILLZ said:
Just open the app, then press the menu button and it should show all your apps open. Now just hold on the nook app and hit app info. Now you can disable or force stop the app.
Click to expand...
Click to collapse
"Force stop" can stop but not disable an auto-started app, it'd get started again after a while or after a reboot. The Nook app also consists of six different "services" which need to be individually force-stopped ...

Related

Force quit running apps

Just found this and thought I'd share. When in the app drawer, if you click and hold an app you get an uninstall option at the top right of the screen. Pretty handy. What I just noticed is that to the right of the uninstall option is a little i in a circle. Dropping the app here opens the app info window. Same window that you would normally have to go to settings -> mange apps -> find the app and tap it. Using the app drawer you can force close in 2 quick steps.
jsnryn said:
Just found this and thought I'd share. When in the app drawer, if you click and hold an app you get an uninstall option at the top right of the screen. Pretty handy. What I just noticed is that to the right of the uninstall option is a little i in a circle. Dropping the app here opens the app info window. Same window that you would normally have to go to settings -> mange apps -> find the app and tap it. Using the app drawer you can force close in 2 quick steps.
Click to expand...
Click to collapse
Thanks for the tip! Although that is force stopping not force closing. Force close is a dirty word
Good point. Changed the title.

[Q] Shutting down Nike+ Running App

I just recently used this NIke+ running app, and pun intended , it just keeps on running.
It has been eating up my battery, even when I'm already done using it. I am currently using Samsung Galaxy Note, on ICS, and when I check on the battery consumption, it shows that Nike+ is on the top of the list, instead of the screen.
How do I shut this app down, or its background process? I am new to android
long press on the home button or go to task manager. kill the app.
or go to settings, applications, select that app and force close it.
praetorius said:
long press on the home button or go to task manager. kill the app.
or go to settings, applications, select that app and force close it.
Click to expand...
Click to collapse
I tried "Force Close" , however, this didn't seem to work as I can still see the app from the battery monitor. I ended up uninstalling it.

How do you kill a running app

On my Samsung Gingerbread /Touchwiz Galaxy Phone long touch of the home button brings up recent applications with a task killer button that lists running apps with an exit button each.
The recent apps button on the Nexus doesn't seem to lead to a kill option.
I guess I could go to settings/apps/running and select an app and pick the stop from its page, but thats a lot more complicated.
Is there an easier way?
Press the right button (looks like two windows) then swipe to kill
Sent from my Nexus 7 using xda premium
rowanparker said:
Press the right button (looks like two windows) then swipe to kill
Click to expand...
Click to collapse
Thanks, I had the right button, but I was trying to kill with a long press instead of a swipe. I thought kill/delete with Swipes was an Apple thing, while Android used long press.
Maybe Apple will sue
Nah, in the iPod touch and iPad it's long press which brings up close buttons
According to the manual the only way to kill a task is in the settings / apps section. "Force Stop"
Swiping away the "recent apps" simply removes it from "recent apps"
Jellybean manages apps / memory automatically. You should never be short on memory.
Hemidroids said:
According to the manual the only way to kill a task is in the settings / apps section. "Force Stop"
Swiping away the "recent apps" simply removes it from "recent apps"
Jellybean manages apps / memory automatically. You should never be short on memory.
Click to expand...
Click to collapse
Yea, that isn't killing an app.
You don't need to kill apps as a matter of routine although people always seem to think so. Sometimes it is necessary if the app is behaving badly and there a lots of task-killers available that will do that.
I like "system panel" as it has other uses too.
The "recent apps" button is supposed to be there for your convenience so you can easily go from one app to another, if you are swiping them away you are just nullifying the point of the button.
Actually swiping away from the recent apps does indeed kill the app. You can verify the behavior on apps by swiping them away and opening them again. They will load from the beginning instead of where you left off.
Sent from my Nexus 7 using xda app-developers app
ok thanks, didn't know that. I think some of the other stuff I said is still kinda valid tho. There is no real need to kill apps.
Sent from my LG-P990 using Tapatalk
kangxi said:
Actually swiping away from the recent apps does indeed kill the app. You can verify the behavior on apps by swiping them away and opening them again. They will load from the beginning instead of where you left off.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I would hardly call that proof. It could simply be a signal to refresh instead of "pick up where you left off". After all, if you swipe it away you dont really have an urgent need to go right "back where you left off".
Hemidroids said:
I would hardly call that proof. It could simply be a signal to refresh instead of "pick up where you left off". After all, if you swipe it away you dont really have an urgent need to go right "back where you left off".
Click to expand...
Click to collapse
The proof is already out there. I just simplified it. There was a huge debate about it when the Gnex came out and I believe a Googler posted about it on Google+ as well.
Sent from my Nexus 7 using xda app-developers app
Don't most people put a task manager widget (Application Manager) on their home screens anyway for this so you can quit all active apps and clear your RAM? It was a standard app on my Samsung Captivate Glide, and I keep it next to my battery widget so maybe between the two I can make the battery last more than 8 hours.
-Ara
is there a way to delete all the runnings apps at once? It's tiring to swipe them out one by one..
sometimes after a long use you have more than 10 apps running, it would be easier if i can simply swipe them all out with one button
thunder9111 said:
is there a way to delete all the runnings apps at once? It's tiring to swipe them out one by one..
sometimes after a long use you have more than 10 apps running, it would be easier if i can simply swipe them all out with one button
Click to expand...
Click to collapse
Again, that's why I like my App Manager widget, you have the option to kill everything in one click (at least until I get the ics update, then it's two clicks for that damn confirmation screen).
-Ara
I've always heard it likened to the backing out of an app with the back button. If I go into G+, go into a room in messenger and skip to home, I can resume the app right where I left off (provided it's soon, hasn't been killed). But if I exit home, swipe the app out, it acts as if I've closed it but it's kept in memory. If I do the same but long press the app in the recent apps list, go to app info and kill the app, then it is forced out of memory. It's essentially killing the app. A good example is a music app; the app continues to play when you've backed out of the app via the back button, even when you swipe the app away as it is still in use. Force stopping the app has a definite result.
Guess it is time for the obligatory "why you shouldn't don't need to use a task killer" with Android. This is an old article, but this was true then and is even more so now. Killing all apps isn't necessary and can have negative effects.
-edit-
Probably should have linked the mentioned article;
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
AraDreamer said:
Again, that's why I like my App Manager widget, you have the option to kill everything in one click (at least until I get the ics update, then it's two clicks for that damn confirmation screen).
-Ara
Click to expand...
Click to collapse
There's no need for task killers. This has been confirmed over and over, even by Google. That's why they made them stop working in Froyo I believe'
Sent from my Nexus 7 using xda app-developers app
Hemidroids said:
According to the manual the only way to kill a task is in the settings / apps section. "Force Stop"
Swiping away the "recent apps" simply removes it from "recent apps"
Jellybean manages apps / memory automatically. You should never be short on memory.
Click to expand...
Click to collapse
Well, actually i use Cool Tool to monitor my available ram, and when I swipe away apps from the recent apps view, i free up lots of ram.
AraDreamer said:
Again, that's why I like my App Manager widget, you have the option to kill everything in one click (at least until I get the ics update, then it's two clicks for that damn confirmation screen).
-Ara
Click to expand...
Click to collapse
It works, but it ruins the the running tasks page. After you killed everything, bring up the running apps, and they are all still there. It doesn't get rid of the apps there, so that's still annoying

Proper way to close an application?

Is it the back button all the way out of the application or pressing the Home button? I can't seem to find a concrete answer!
ojai00 said:
Is it the back button all the way out of the application or pressing the Home button?
Click to expand...
Click to collapse
Those do the same thing, which is either leave the app running or leave it in a nearly running state. To actually close an app, you press the multitasking button (the button to the right of home) and swipe the app off the screen.
BUT, you generally don't need to do that in Android -- The OS manages most well behaving apps fine.
jaybeeunix said:
Those do the same thing, which is either leave the app running or leave it in a nearly running state. To actually close an app, you press the multitasking button (the button to the right of home) and swipe the app off the screen.
BUT, you generally don't need to do that in Android -- The OS manages most well behaving apps fine.
Click to expand...
Click to collapse
Swiping an app out of recents does the same thing as pressing the back button actually. To answer the first question, the back button exits an app properly, the home button just suspends the app
jaybeeunix said:
Those do the same thing, which is either leave the app running or leave it in a nearly running state. To actually close an app, you press the multitasking button (the button to the right of home) and swipe the app off the screen.
BUT, you generally don't need to do that in Android -- The OS manages most well behaving apps fine.
Click to expand...
Click to collapse
The back button actually does a better job closing the app, and usually the app has a close button when after jamming the back button. This is how you close (not force close/stop) the app.
If you are using an app and tap the home button, do other stuff and go back, you will be exactly where you were before. This is how you multitask (with the home button).
The multitask menu is like the one on iOS 4 and above. It is a menu of RECENTLY USED APPLICATIONS and is there just for quick switching. Swiping will not close the app, it will delete it off your "history."
Sent from my DROID2 using xda premium
jacklebott said:
Swiping an app out of recents does the same thing as pressing the back button actually. To answer the first question, the back button exits an app properly, the home button just suspends the app
Click to expand...
Click to collapse
http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle
Swiping gets you to the "activity shut down" phase (onStop and onDestroy are called, assuming your app is nice, it'll shut down).
Home-ing gets you to the onPause phase (from the things I tested, they usually then go to onStop (cached phase)).
Backing out gets you to the onStop (cached) phase.
(You can verify this by looking at Settings>Apps>Running. When I back or home out of an app, the app is shown with the same state (cached). When I swipe an app away, it's gone from both of those task lists.)
jaybeeunix said:
http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle
Home-ing gets you to the onPause phase (from the things I tested, they usually then go to onStop (cached phase)).
Backing out gets you to the onStop (cached) phase.
Click to expand...
Click to collapse
Although that is native Android behavior, developers almost always make it so the app will nicely shut itself off when pushing the back button.
For example, when I open Root Explorer, it starts of with a black screen, and only after Root Access is granted my files show up. If I tap back and open it again, bam! Same process.
If I tap home after opening and open it again, bam! Takes me right to the / file directory, no inital "startup" of app
Sent from my DROID2 using xda premium
Why can't developers just put an exit button in the app menu?
donec said:
Why can't developers just put an exit button in the app menu?
Click to expand...
Click to collapse
They can, some do, some don't *shrugs*
Sent from my DROID2 using xda premium
donec said:
Why can't developers just put an exit button in the app menu?
Click to expand...
Click to collapse
Generally speaking, there isn't a need for it -- The OS closes and restarts apps as needed to manage resources optimally. Additionally, as gagdude said, most apps save and restore their state beyond the OS cached state, so it isn't always obvious that an app was ever "gone".

How does an App open a disabled app to show an Ad?

My dad has a Galaxy J7 Prime it keeps opening Google chrome to show an full screen ad.
The problem is that chrome is disabled thru Apps on this phone.
He is complaining about the Ads on this phone and he wants them to stop without having to do a factory reset.
He hasn't downloaded any app recently but this started sometime last week. He uses only Adblock browser so Im all out of ideas.
These ads consists of advertising a app to download.
Lookout and Malwarebytes both say theres no problems.
EDIT: Will rooting this device and removing google chrome entirely from this phone using titanium backup solve the issue?
mrnapolean1 said:
My dad has a Galaxy J7 Prime it keeps opening Google chrome to show an full screen ad.
The problem is that chrome is disabled thru Apps on this phone.
He is complaining about the Ads on this phone and he wants them to stop without having to do a factory reset.
He hasn't downloaded any app recently but this started sometime last week. He uses only Adblock browser so Im all out of ideas.
These ads consists of advertising a app to download.
Lookout and Malwarebytes both say theres no problems.
EDIT: Will rooting this device and removing google chrome entirely from this phone using titanium backup solve the issue?
Click to expand...
Click to collapse
I've had this a few times with rogue apps.
Just find the app responsible.
Set your recents to list view. Next time the ad pops up press the back button.
Open recents and look at the apps, one should be responsible for the ad.
If you see a recent app listed with no icon it is probably that. To make it reveal itself long press on the left of the recent.
ashyx said:
I've had this a few times with rogue apps.
Just find the app responsible.
Set your recents to list view. Next time the ad pops up press the back button.
Open recents and look at the apps, one should be responsible for the ad.
If you see a recent app listed with no icon it is probably that. To make it reveal itself long press on the left of the recent.
Click to expand...
Click to collapse
What do you mean by setting Recents to list view?
mrnapolean1 said:
What do you mean by setting Recents to list view?
Click to expand...
Click to collapse
Tap the 3 dots.

Categories

Resources