My phone app opens at random times, or when I unlock it the phone app has come to focus.
I only have stock + root. I have not used android for years, but I use Unix based systems for private and work all the time.
Related
I have been using 'Close Everything' app for awhile thinking it does what it suppose to do. Just today I held down the home key and 6 apps are fully opened. Now I need another app that actually does the job of closing apps. Anybody know one?
holding down the home key opens up a window of the last six apps opened and used.
AFAIK, the way Android works, apps don't get closed. If you by some outside means manage to kill an app off, Android will think something's wrong, and resurrect it if it can. The only 100% way to kill an app I know, is to reboot (and then not start it).
/Mats
Advanced task manager by Arron La
They aren't actually running AFAIK
They are the last six apps used, it doesn't matter if they are running or not
Try using task manager for root. I use a combination of several closing apps and this one seems to work well. I'm not sure if its in the market tho. But I found it on one of the threads. Happy searching
Advanced Task Manager will allow you to kill the processes and applications of your choosing. (It is on the market for US, that's where I got it free)
As said, Advanced Task Manager is what you need. It's nice letting you choose apps to never kill so you can just hit the End All button and be lazy
Hey all, i am starting to find out about creating apps. I have started with creating a simple webview app that shows a website.
What i am having trouble with is after editing the files in eclipse i hit run an in the SDK emulator all i get is a black screen wit android write on it.
Any ideas?
NOTE: i am very new to this
Be patient it takes like 10 mins or more for the emulator to load
Novice here.
Yes, it will take sometime. Here it starts quickly (core i5 notebook). But it may take a long long time.
You can also use your phone to debug and deploy. It's very very quick, takes virtually no time to load, like the emulator. At least here.
Good luck!
Thanks all it did take a while was juts me being inpatient.
Follow-up question: When debugging an app in eclipse, if you change your source during a debug session, it should restart my app/activity/whatsis, right?
Yeah.. not getting that at all, and my current dev box leaves something to be desired in the horsepower department. Those emulator restarts are killing my interest in working on this pet project of mine.
I found a link that should let me use my Evo directly, hopefully that will do the trick.
--Mark
Sent from my PC36100(Evo) using XDA App
Update:
Grr. I installed the HTC Sync 2.blah, so I can actually connect to my Evo now from within Eclipse but I'm still running into problems. Eclipse still isn't automagically updating my app when I change-n-save. Am I just expecting too much here?
Oddly enough, it DID update the changed app when I unplugged my evo from my laptop and plugged it back in. This took several seconds to catch up, but it beats the hell out of waiting for a new emulator to boot. Ouch. We need some way to freeze/save the emulator state so we can relaunch it with it's memory and so forth already in place.
I'd mangled my first hand-rolled "hello world" app (started monkeying with stuff without knowing what did what), so it no longer ran. Note To Self: "Test Only" flag seems to mean "emulator only". That was a snag.
So I whipped up a demo app (the "Skeleton App" for 2.1) project. Installed and ran fine. I changed a couple buttons to Log.d(...) instead of What They Did, and after the unplug-plugin trick, the app updated. The buttons no longer performed their original tasks... instead they now do what looks like NOTHING! LogCat isn't showing my debug messages at all (which wasn't a problem previously when I was just using the emulator).
Am I just missing the boat here or what?
I have used Nokia Symbian Belle couple of years back and I use AppsKeeper app to prevent app from closing. Even if it gets closed, automatically it will start that app by checking every 5 seconds. Is there any app that does the same functionality in android?
i think that if you open app it keeps open till you manually close it... we android rather want to kill it and only start when we want to som apps start on their own.
Hi all,
My model SM T330 has begun periodically freezing with whatever app I try to run eventually crashing about 30-60 seconds in. At its best the app simply crashes and dumps me back to the home screen (which often fails to load my shortcuts and widgets). At its worst it will completely freeze when I try to transition to a new app or otherwise try to navigate the UI. I would chalk this up to it getting old but I got lucky and managed to get the home screen to load only to find that an app called "baby angel" had suddenly appeared there (it uses the Android system app icon). I was able to get the applications manager to last long enough to find that this app wasn't listed anywhere (even under "all"). I don't see how it could be an actual system app because I haven't updated my OS (version 5.1.1) in a while (unless it updated itself even after I told it not to) and I couldn't find any reference online to a system app of that name (just a bunch of live wallpapers that I definitely don't have).
At this point I assumed I'd been infected with malware so I ran a full scan with McAfee but it came up with nothing. I find this hard to believe but I'm not sure how to proceed or if the two events are even related. Right now I'm just keeping the Wi-Fi off in case it's being accessed remotely somehow (did I mention my tech literacy is mediocre at best?)
Any advice would be greatly appreciated. If I've left out some important piece of information feel free to ask.
Flash the stock firmware with Odin.
We're building an app that will be installed on smartphones and displayed on a desk. The user need to be able to close the app and use the device, but when he does not use the device the app should move to the front automatically after X minutes.
Here is the catch: we need to support new devices for the coming 3 years and the user should not be able to close/kill the process.
Android: We found that we could use the permission BIND_DEVICE_ADMIN to make the process unkillable. However it will be deprecated soon and we have no idea how long it will remain functional.
iOS: We found no solution
Does anybody have a workaround/solution or does somebody know how much longer they will support the BIND_DEVICE_ADMIN permission?
I know it seems like something fishy, but it's actually intended for distribution internally via our company MDM and it makes sense in the context we are using it for.