[APP] MortRunner, run all scripts in a directory - Windows Mobile Development and Hacking General

I have some things on my phone i want to automate,
building an application for it would be a little over the top,
mainly because it can be done with mortscript quite easily
the only problem would be that the script would be running, always..
So i build an application which runs mortscript periodically
the initial app is the config where you can define the settings and select the
directory the App needs to look in.
next have the app create the shortcut and when you run the app through the shortcut, the app should run all the scripts in the folder.
Please note that while the script is running the time does not increase,
this is to make sure that no 2 scripts can be run at the same time.
ToDo.
- change the icon, this one is probably not freeware (any help is appreciated)
- sort the scripts before running
It has been tested on a emulator and my diamond, everything seems to be working like it should.
Let me know what you think

reserved 1

reserved 2

Related

Do something every 15 min

I want to execute some code (e.g. poll a website for new data) every 15 minutes. What is the best, most power efficient way to do this?
I think these are my options:
A) auto start my app at device boot, run it in the background as hidden window and use a 15 minute timer.
B) create a Windows service that is always running in background and can fire my app
C) Call some API to register my app with the system so it is launched every 15 minutes, even if it has been shut down. (Which API?)
Thanks.
Use mortscript. Use the following script:
Run "filetorun.exe"
RunAt( Timestamp()+900, "this-script.mscr" )
replace the word filetorun.exe with the app you want to run
replace the words this-script.mscr with whatever you call this script.
Hi Axman,
thanks for the suggestion but Im writing a standalone .exe in C++. Not sure what runtime I need for mortscript and I prefer not taking any dependencies.

Oxios Memory Msg Box Prompt Disabled. Download here

Oxios developed a very useful tool for Windows Mobile (WM2003/5/6/6.1) called “Oxios Memory” sometime ago. On running it, it’ll flush your RAM (kind of) and recover substantial amounts of memory that can be used by the currently program. It is so good at this that many people run it regularly on their phones, and most of them want to run it in an automated mode (through a scheduler or a script). But the problem (so far) was that it generates a Message Box at the end for which the user has to press “OK” button to make it go away. There is no known way of disabling this message box and many attempts to work around it by scripting the “press OK” action have been very unreliable at best. Hence, it took it upon me today to remove this nagging problem and 5 minutes later we have a “clean” Oxios Memory.
Yes, no more nagging prompts
Download it from here: http://tech.shantanugoel.com/2008/0...-box-in-oxios-memory-apps-windows-mobile.html
If you like it, then DIGG IT by clicking here
i waited for this...
Thanks nothin.
Do provide your comments on the site as well
And please do spread the word
Can you do the same to oxios hibernate instead of just closeapps?
Great job! Could you do the same for Oxios Hibernate as well?
OK, request accepted
Will modify the hibernate app as well tonight.
In the meanwhile, If you like it, then DIGG IT by clicking here
I did the same for Oxios app using MORTSCRIPT....
With your app is there a way to select the time after the program runs or we have to do a mortscript program which launches your app at a specific time?
An other question...
To push the "Ok" button what did you do?
I used mortscript to press "CR" after the script run....
flaviopac: Its different from what you did. I've not made any "app". I've modified the original oxios executable file so that it does not display the message box at all, hence there is no need of "clicking" ok anymore.
shantzg001 said:
flaviopac: Its different from what you did. I've not made any "app". I've modified the original oxios executable file so that it does not display the message box at all, hence there is no need of "clicking" ok anymore.
Click to expand...
Click to collapse
Ok.....
And what about HIBERNATE??
flaviopac: I'll modify the hibernate app as well tonight and will post at that same location.
Good job Shantz.
WB
Nice work, thanks!
Cool Job done
that's awesome !!! eager to download
On Popular demand I've modified the Oxios Hibernate app as well. Please redownload the file given at my site again. The zip file now has both the apps Oxios Close as well as Oxios Hibernate.
shantzg001 said:
On Popular demand I've modified the Oxios Hibernate app as well. Please redownload the file given at my site again. The zip file now has both the apps Oxios Close as well as Oxios Hibernate.
Click to expand...
Click to collapse
Many thanks man!
These files are very usefull!
Thank you Shantz. This is just great.
Excellent Shantz! I have Oxios scheduled daily with "Run Everyday" app, now no more OK's to look at!
galaxys said:
Excellent Shantz! I have Oxios scheduled daily with "Run Everyday" app, now no more OK's to look at!
Click to expand...
Click to collapse
Hmm can you tell me where you found this "run everyday" app and does anyone know easiest way to schedule oxios hibernate to run hourly?
*nevermind...found the run everyday app here on this forum [ http://forum.xda-developers.com/showthread.php?t=294575 ] but still interested in way to run more often than that.
For running the app at set interval of time, i will put in this shameless plug
You can also use my app ShantzTodayChanger
It is a app runner/scheduler plus a theme/wallpaper cycler. Moreover, it has a masking functionality. So if you dont want to change ur themes etc, you can just configure it to run as a pure exe scheduler. so, using it you can run the app after every, say 5 minutes to after any number of years and any other interval in between
famewolf said:
Hmm can you tell me where you found this "run everyday" app and does anyone know easiest way to schedule oxios hibernate to run hourly?
Click to expand...
Click to collapse
You could also use Mortscript.....

[REQ] very small app to display "toast" msg

I am in need of a very small app (just a few lines of code) to display a "toast" message in the active window.
I have the milestone, and made some mods on it, and using the hw keyboard i made shortcuts to execute functions and i would like to display a status from the scripts, and so far it only works with Beanshell(Android Scripting Environment), but the window popup is simply to annoying. so if somebody can make the toast command in a java app, and add the, i think, intent call function so i can execute this using "am" from shell script.
Yes, i know, i could probably do it myself, but i am no good at the "I-went-to-the boat->on my cycle->using my legs" object oriented programming thingy..
If anybody can help me out, any help is appreciated...
I was interested in looking into this to help my growth of android, so gave it a shot.
This is an app that starts, displays the input message, then exits.
run it through command line using the following:
am start -a android.intent.action.MAIN -e message mytoastmessage -n com.rja.utility/.ShowToast
whatever is passed in for the 'message' is displayed in a long toast.
if nothing is passed a toast saying such is displayed.
Let me know if this works for you.
corruptor64 said:
I was interested in looking into this to help my growth of android, so gave it a shot.
This is an app that starts, displays the input message, then exits.
run it through command line using the following:
am start -a android.intent.action.MAIN -e message mytoastmessage -n com.rja.utility/.ShowToast
whatever is passed in for the 'message' is displayed in a long toast.
if nothing is passed a toast saying such is displayed.
Let me know if this works for you.
Click to expand...
Click to collapse
Hmm cant get it to work can you write a example script and upload plz thanks.
ngagephone said:
Hmm cant get it to work can you write a example script and upload plz thanks.
Click to expand...
Click to collapse
Ok it works now is there any chance you can reupload your app but make the icon from the app drawer gone you can do this by removing <category android:name="android.intent.category.LAUNCHER" /> from the manifest file thanks in advance.
ngagephone said:
Ok it works now is there any chance you can reupload your app but make the icon from the app drawer gone you can do this by removing <category android:name="android.intent.category.LAUNCHER" /> from the manifest file thanks in advance.
Click to expand...
Click to collapse
Good call on removing the icon from the drawer. It really doesn't belong there for this type of application.
corruptor64 said:
Good call on removing the icon from the drawer. It really doesn't belong there for this type of application.
Click to expand...
Click to collapse
Thanks will give it a go cheers.
Ok just tested works good this will be nice for my custom rom for displaying msg from my scripts thanks.
Sent from my Pulse Mini using XDA App
I edited the original reply and added a signed apk for the no drawer icon version.
The original version will expire in a year and will not be able to be installed after that since it was signed using debug certs which are valid for a year after the apk was created.
Download the latest one and use that. Glad i could help.
cool, can you guys make one to play a sound? or is their a script or line of code that will play a sound? I made a few scripts to download/install a boot animation but i cant figure out how to notify once its done, thats what im going for. as of right now it just reboots the phone when its done.
corruptor64 said:
I was interested in looking into this to help my growth of android, so gave it a shot.
This is an app that starts, displays the input message, then exits.
Click to expand...
Click to collapse
thanks alot! it already sounds like it works for others.. this is a very nice idea for giving status backs in customs, so its worth alot for modders somehow, when the java is not a knowledge you have
ill test it tomorrow and see how it works out.
corruptor64 said:
I edited the original reply and added a signed apk for the no drawer icon version.
The original version will expire in a year and will not be able to be installed after that since it was signed using debug certs which are valid for a year after the apk was created.
Click to expand...
Click to collapse
resigning when making new mods is less a problem, than coding it
im sure it'll work out in the end...
Damn i think i spoke to soon it works fine via the adb shell it shows the msg i made on the phone but if i try to run it in terminal emulator on the phone it does not work. Any ideas? if any one has it working via terminal emulator do you mind uploading a sample script?
ngagephone said:
Damn i think i spoke to soon it works fine via the adb shell it shows the msg i made on the phone but if i try to run it in terminal emulator on the phone it does not work. Any ideas? if any one has it working via terminal emulator do you mind uploading a sample script?
Click to expand...
Click to collapse
It works through adb shell for me and using Terminal Emulator app on my phone. I copy and pasted the following in terminal emulator on my phone and it showed a toast as expected.
am start -a android.intent.action.MAIN -e message 'this is the displayed text in a toast' -n com.rja.utility/.ShowToast
I don't do scripting so can't help there, sorry. Hopefully someone else can provide you the script you need. From my perspective i think everything is good. Let me know if you find out otherwise.
Good Luck!
Hmm it does work the problem i had is i was making the scripts in windows using notepad++ and i have noticed if i open the script on android i have blocks at the ends of each line. I have had this problem in linux when doing scripts via windows. Any way its not a problem with your app so thanks.
ngagephone said:
Hmm it does work the problem i had is i was making the scripts in windows using notepad++ and i have noticed if i open the script on android i have blocks at the ends of each line. I have had this problem in linux when doing scripts via windows. Any way its not a problem with your app so thanks.
Click to expand...
Click to collapse
UltraEdit rulez!
foxdog66 said:
cool, can you guys make one to play a sound? or is their a script or line of code that will play a sound? I made a few scripts to download/install a boot animation but i cant figure out how to notify once its done, thats what im going for. as of right now it just reboots the phone when its done.
Click to expand...
Click to collapse
Per this request, I made an app that plays a specified sound stream for the duration requested. It does not force a specific sound, but plays whatever sound is set for the type at the time.
/*
* Example run command:
* am start -a android.intent.action.MAIN -e raisevolume 'true' -e soundduration '8000' -e soundtype 1 -n com.rja.utilities/.PlaySound
*
* Program Options and valid values:
* Not passing in a flag is the same as passing false.
* raisevolume - boolean that forces the sound to be played.
* - sets sound mode to normal and raises volume to max - after sound is played, resets mode and volume to previous values
* soundtype - number to indicate type of sound to play
* - Valid Values:
* - 0 - ringtone
* - 1 - notification
* - 2 - alarm
* soundduration 8000 -- if nothing is passed default is 4000. This is the duration the sound is played.
*/
Please let me know if you have any questions or problems with it.
right on! thanks dude! ill give it a go and let you know how it works
Two years ago I was in need of a simple notification tool that could have been run by a command line in a script.
So far the best I found was this thread and the tiny app made by corruptor64.
That wasn't exactly what I was looking for so I finally decided to try to make the tool by myself.
Starting from scratch (I am not an Android developer) in a few days of studying and developing I ended up with a working small app, that I named Notify4Scripts and I made it public only this past June, here on GitHub
https://github.com/halnovemila/Notify4Scripts
Note that since the app is basically a service that has to be launched by the Android's shell "am" (activity manager) command, the Android system needs to be rooted first in order to be able to use such am command and have notify4scripts executed.
halnovemila said:
Two years ago I was in need of a simple notification tool...
Click to expand...
Click to collapse
Could you please write an intent to open a directory given as a variable when I tap notification. I want to use it with clamav daemon running on my phone so that I can open the directory containing infected file when I get the notification. Please note that directory can be out of $EXTERNAL_STORAGE e.g. /data/data/ which is only accessible with root privileges.
Can the notification be multi lined or expandable with "b_noicon 0" so that complete path and virus name is visible before opening the directory?
Thanks for this great tool.
mirfatif said:
Could you please write an intent to open a directory given as a variable when I tap notification. I want to use it with clamav daemon running on my phone so that I can open the directory containing infected file when I get the notification. Please note that directory can be out of $EXTERNAL_STORAGE e.g. /data/data/ which is only accessible with root privileges.
Can the notification be multi lined or expandable with "b_noicon 0" so that complete path and virus name is visible before opening the directory?
Thanks for this great tool.
Click to expand...
Click to collapse
Hi,
the intent depends on the app you are willing to use to "open" the target folder.
If you are willing to use a terminal emulator app you can look at the many example I've wrote on the wiki available at the GitHub page of my tiny project (here's the direct link to the wiki https://github.com/halnovemila/Notify4Scripts/wiki ).
In such examples I illustrate how to call the terminal emulator app and have commands passed to it for execution.
If you'd like to use other apps, like a file explorer app, then you need to know the proper intent for that app.
The "easy" way is to make a home screen shortcut of the app opening a folder, then locate the Launcher app database, open it and read the intent used for the shortcut (that's how I found out all the intent used in the examples).
When the notification layout is set to "Custom View" (which always is when b_noicon is set to 1) multi lines text content is possible (also with use of \n new line escape code in the text) but it's not "expandable". You can adjust the content text size and remove the title line (with str_title "") to gain more room and be able to fit longer text on the notification box.
Hope this helps

[APP][TOOL][AUTOMATION] Cron Phone Your Phone[UPDATE (9/28/11)]!!

Major Changes to the UI and usage Check the market for the latest version or use the version attached to this post. If you have trouble with the posted version use the market version as it will always have the lastest fixes. The attached version might have an issue I did update the attached version but I won't manage it here.
1. Complete task ui revamp, easier building and management of tasks.
2. Added cron string builder, you can now build time string with rolling pickers and show you the next execution date (great for visualizing your time string). This will build 98% of the schedules most of us use.
3. Clicking on the clock in the Cron tab will now show all the active queued tasks (tasks that were active when cron was started).
4. Added option to run on boot for a task, this makes tasks execute if the option is checked and cron is set to auto restart. This allows a task to run only, at boot, and the task does not have to be active. (Sascha Kerkeling).
5. Added option to import scripts, you can now import the contents of a script file (Sascha Kerkeling).
6. You can now activate/deactivate a task from the tasks view.
7. I have kept the old tasks view in place for this update so that you can trasnfer any existing tasks over... it will be removed next update.
8. Added cron change log... this will automatically show once every update.
9. Added safe guard so that a reboot command cannot be fired with the execute on boot option (just in case).
10. Added better logging of why task commands fail, this will show as a complete stack trace in the execution log.
11. Added 6 new default tasks that might be helpful (Sascha Kerkeling, A. Simmons).
This is cron for your phone a small app I developed to allow me to restart/shutdown my phone on a schedule, but Cron has a billion uses and I wanted to see how others will use it I also use it to backup my market apps on a schedule.
**WARNING YOUR PHONE NEEDS TO BE ROOTED TO USES THIS APP**
This app can be dangerous if used wrong, if you use this app incorrectly and mess your phone up its your fault not mine. You wouldn't blame snap-on if the wrench you used breaks a bolt on your car, so don't try and blame me for what you do wrong with this tool. If you do I will only point at you and laugh.
**WARNING YOUR PHONE NEEDS TO BE ROOTED TO USES THIS APP**
Features:
Uses the standard Cron4Phone time string schedule.
Run all type of shell commands on any schedule you can think of.
Run tasks to shut your phone off on a schedule.
Auto restart so Cron4Phone continues to run even after a restart.
Small apk foot print.
unlimited concurrent tasks available.
Set a task as inactive/active.
Test execution setting to log commands only.
I'm really looking forward to seeing how others will use this tool. Please feel free to point out errors or suggestions. If you want help setting schedule I can give pointers.
Android market download
ooooh
as soon as I can liberate a copy from a market enabled phone I will begin tinkering... that might take a while
would you consider releasing it to f-droid.org if your license allows?
Here you go
Here's a copy... I haven't opened the source up although I probably will in the future, when I have more time to spend on it (working on a video game). This copy is signed with the same key as the market version and its ad supported I will slowing be updating the task management part of the ui.
this is the market description
*****YOUR PHONE NEEDS TO BE ROOTED TO USES THIS APP*****
This app can be dangerous if used wrong, if you use this app incorrectly and mess your phone up its your fault not mine. You wouldn't blame snap-on if the wrench you used breaks a bolt on your car, so don't try and blame me for what you do wrong with this tool. If you do I will only point at you and laugh.
*****YOUR PHONE NEEDS TO BE ROOTED TO USES THIS APP*****
-----------NEW INFO READ------------
After another full audit and help from Sascha Kerkeling and M. Porter, I redesigned Cron to no longer use long running service and instead now (correctly) uses AlarmManager to precisely execute tasks in a WakefullIntentService. This will will insure that all task are executed even when the phone is in deep sleep (even when the phoen doesn't hold any other wake locks) and barely uses any resources to accomplish this. I will now be able to focus on the UI... Dynamic task here we come!
-----------NEW INFO READ------------
Cron4Phone is a time-based job scheduler in Unix-like computer operating systems. Cron4Phone enables users to schedule jobs (commands or shell scripts) to run periodically at certain times or dates. It is commonly used to automate system maintenance or administration, though its general-purpose nature means that it can be used for other purposes, such as connecting to the restart your phone and backing up apps. This is a foreground service so that it is guaranteed to stay running, use the home key to back out of the app or double tap the back arrow to kill the app. Killing the app kills the service.
Features:
Uses the standard Cron4Phone time string schedule.
Run all type of shell commands on any schedule you can think of.
Run tasks to shut your phone off on a schedule.
Auto restart so Cron4Phone continues to run even after a restart.
Small apk foot print.
5 concurrent tasks available.
Set a task as inactive/active.
Test execution setting to log commands only.
This tool can be used to do endless amount of things, I'm really looking forward to see what you guys can use it for so please share your ideas, command and schedules.
I have provided 3 tasks that I thought would be the most useful to most users shutdown, restart, and backup apps.
Interesting
Sent from my SCH-I500 using XDA App
testing your application, it's really simple.., i'm hoping custom task can be added more
New version
EDIT: removed refer to the OP...
I attaching a new version to this post, it fixes a bug with the restart on reboot not registering your tasks. Basically if your phone reboots and you have active tasks and cron is started it will keep on running.
As for the ui I will slowly work on updating the task tab so that task can be managed dynamically, other than that the rest of the ui will basically stay the same, I want it to stay simple and small.
The market version has also been updated.
ttt for updates!
Very nice app, I would like to see more Linux tools working with Android.
Sent from my Zio using xda premium
Yes and this was one that I thought was needed, and while you can run cron on your phone through busy box, this app doesn't need that module and uses standard java to mimic cron all while putting a clean ui on top of it.
Thank you.
[EDIT]
ACK! Okay, I just stopped and started the cron and it is now working. Sorry about this post. :-/
[/EDIT]
I am going to resurrect this thread because I can't figure this out and I'm a Unix admin. I have tried to set a schedule for a job to run every 5 minutes (this was to test, the actual job will run every 30 minutes). I have tried to set */5 * * * *, /5 * * * *, and 0,5 * * * * and none of them work for every 5 minutes. Can you look into this or give an example in here? Thanks!
fstrim
If anyone is still out there -- I use Cron4Phone to schedule daily reboots and would like to add an fstrim command to run daily, maybe weekly. Can anyone help me with setting this up (command syntax, etc)?
Is there any chance to get the apk from somewhere? Thanks in advance!

Apps that runs on startup/background

I hate it when an app runs in the startup specially if the app is not that important. Is there any way of disabling those apps that run in the startup? As well as those apps that runs in the background even if you don't need em to? They eat up RAM and make the NC slow! I wish I can manage them.
Let them be android takes care of itself.
Read this: http://forums.androidcentral.com/general-help-how/102171-apps-always-running.html#post1088042
---
- Sent from my LG Optimus V using Tapatalk
les02jen17 said:
I hate it when an app runs in the startup specially if the app is not that important. Is there any way of disabling those apps that run in the startup? As well as those apps that runs in the background even if you don't need em to? They eat up RAM and make the NC slow! I wish I can manage them.
Click to expand...
Click to collapse
Yes...get an app in the market called Android Optimizer, it is free. In the menu hit the startup manager icon. Disable the app (s) you don't want to run at start up or background.
StarlahRain said:
Yes...get an app in the market called Android Optimizer, it is free. In the menu hit the startup manager icon. Disable the app (s) you don't want to run at start up or background.
Click to expand...
Click to collapse
You sure of that name? I did a search in the market and do not see it.
StarlahRain said:
Yes...get an app in the market called Android Optimizer, it is free. In the menu hit the startup manager icon. Disable the app (s) you don't want to run at start up or background.
Click to expand...
Click to collapse
You do not need an app like this. People use task killers and startup blockers and then complain about how crappy and slow stuff is because THEY ARE NOT ACTUALLY RUNNING IN THE BACKGROUND. They are cached for faster start up next time. They do not take up any battery or CPU power. Android is linex not windows.
--------------------------------------------------
Here is the post i linked to earlier:
I develop Android apps so I though I'd explain why a task killer isn't needed on an Android system.
Activities
Android apps use activites to preform tasks. For example, if you use a file manager to send a picture via email, the file manager calls the send activity within an email app, passes the file name to it and the email app sends the picture.. not the file manager. This will result in seeing the email app as "running" even though the user didn't actually launch that email app.
Smaller apps
Using activites helps developers design smaller apps. A file manager app that contains every bit of code needed to do everything a file manager does would likely be so large that no one would want to install it. Developers know that an android phone more than likely has an email app so there is no need for the developer to include email code in his/her file manager to send a picture when he/she can call an activity in an existing email app to do the job. This results in a smaller file manager app since there is no need to include email code or any other code for an activity that can be done via an app that is already present on the phone. This also alleviates redundant code. When you install an app outside of the android market, also known as sideloading, the file manager app calls the package installer (already present in Android) to install the requested app.
Running apps vs. cached apps
The "Manage Applications" list included in many android devices lists running apps as well as cached apps. Cached apps don't use any CPU or battery, they're cached so they will load faster the next time you need them. Killing cached apps results in those apps requiring more time to load the next time they are launched.
System management
By default, every android application runs in its own Linux process. Android starts the process when any of the application’s code (activities) needs to be executed, and shuts down the process when it’s no longer needed and system resources are required by other applications.
* 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.
If you see an app running that you didn't launch, it's most likely because an activity within that app was called by another app to perform a task. If you kill the app you didn't launch, the system has to relaunch that app in order to complete its task. This is why some people kill a task and then see it immediately running again. Constantly killing that app creates a situation where the user is battling the system resulting in wasted system resources.
Android is Linux
Android is not a Windows-based OS, it is based on Linux. Many of the apps you think are running aren't actually running, they're cached, this is typical with a Linux operating system and is much more efficient than other systems. Cached apps don't use any CPU or battery, they're cached and will load faster the next time they're needed.
Let the system manage resources.
---
- Sent from my LG Optimus V using Tapatalk
patruns said:
You sure of that name? I did a search in the market and do not see it.
Click to expand...
Click to collapse
I apologize ..it is called Optimize Tool Box...lite version(free)...
koopakid08 said:
You do not need an app like this. People use task killers and startup blockers and then complain about how crappy and slow stuff is because THEY ARE NOT ACTUALLY RUNNING IN THE BACKGROUND. They are cached for faster start up next time. They do not take up any battery or CPU power. Android is linex not windows.
--------------------------------------------------
Here is the post i linked to earlier:
I develop Android apps so I though I'd explain why a task killer isn't needed on an Android system.
Activities
Android apps use activites to preform tasks. For example, if you use a file manager to send a picture via email, the file manager calls the send activity within an email app, passes the file name to it and the email app sends the picture.. not the file manager. This will result in seeing the email app as "running" even though the user didn't actually launch that email app.
Smaller apps
Using activites helps developers design smaller apps. A file manager app that contains every bit of code needed to do everything a file manager does would likely be so large that no one would want to install it. Developers know that an android phone more than likely has an email app so there is no need for the developer to include email code in his/her file manager to send a picture when he/she can call an activity in an existing email app to do the job. This results in a smaller file manager app since there is no need to include email code or any other code for an activity that can be done via an app that is already present on the phone. This also alleviates redundant code. When you install an app outside of the android market, also known as sideloading, the file manager app calls the package installer (already present in Android) to install the requested app.
Running apps vs. cached apps
The "Manage Applications" list included in many android devices lists running apps as well as cached apps. Cached apps don't use any CPU or battery, they're cached so they will load faster the next time you need them. Killing cached apps results in those apps requiring more time to load the next time they are launched.
System management
By default, every android application runs in its own Linux process. Android starts the process when any of the application’s code (activities) needs to be executed, and shuts down the process when it’s no longer needed and system resources are required by other applications.
* 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.
If you see an app running that you didn't launch, it's most likely because an activity within that app was called by another app to perform a task. If you kill the app you didn't launch, the system has to relaunch that app in order to complete its task. This is why some people kill a task and then see it immediately running again. Constantly killing that app creates a situation where the user is battling the system resulting in wasted system resources.
Android is Linux
Android is not a Windows-based OS, it is based on Linux. Many of the apps you think are running aren't actually running, they're cached, this is typical with a Linux operating system and is much more efficient than other systems. Cached apps don't use any CPU or battery, they're cached and will load faster the next time they're needed.
Let the system manage resources.
---
- Sent from my LG Optimus V using Tapatalk
Click to expand...
Click to collapse
Yes..I have noticed some side effects.alarms and what not. I guess ur right the only real way is to completely uninstall the apk ..would u happen to know why my adw launcher keeps forceclosing each time boot my nook? I am not running any icon packages..so what other source (or app) could be calling on it to run at startup?
StarlahRain said:
Yes..I have noticed some side effects.alarms and what not. I guess ur right the only real way is to completely uninstall the apk ..would u happen to know why my adw launcher keeps forceclosing each time boot my nook? I am not running any icon packages..so what other source (or app) could be calling on it to run at startup?
Click to expand...
Click to collapse
I am not familiar with adw. Is there an option to save it in memory I know that many replacement launchers do so you might want to make sure that is checked.
Also if you are using a task killer, it is probably trying to kill it and that could cause it to force close.
---
- Sent from my LG Optimus V using Tapatalk
StarlahRain said:
Yes..I have noticed some side effects.alarms and what not. I guess ur right the only real way is to completely uninstall the apk ..would u happen to know why my adw launcher keeps forceclosing each time boot my nook? I am not running any icon packages..so what other source (or app) could be calling on it to run at startup?
Click to expand...
Click to collapse
Do you have Titanium Backup installed? You can clear data and uninstall apps with that as well.
auto starts kills those apps... i run it on my NC>.......i dont need dialer /voicemail...etc.....
Just a thought but if you continue to have force close issues with apps, try running fix permissions. This usually ends the issues. I run adw ex and have no problems. Those few times I have had issues, fix permissions has solved the problem. Just sayin.....
Sent from my NookColor using Tapatalk

Categories

Resources