I have a relatively simple task to be done every monday: copy a folder to extSD placing the date in the name of the folder.
Well some week I found the copied folder and some weeks not. Tasker is alway open. So I have no idea what happens.
Any Idea?
francus said:
I have a relatively simple task to be done every monday: copy a folder to extSD placing the date in the name of the folder.
Well some week I found the copied folder and some weeks not. Tasker is alway open. So I have no idea what happens.
Any Idea?
Click to expand...
Click to collapse
Did you check Tasker log?
No #Henkate, but checking found "run log" I'll try to run it when we'll get close to the relevant day
thanks
Have you already tried setting the "Use Reliable Alarms" to Always in preferences/monitor?
No GrippingSphere, but now activated it. Is it helpful?
francus said:
No GrippingSphere, but now activated it. Is it helpful?
Click to expand...
Click to collapse
Putting Reliable Alarms to Always in Tasker is necessary when you are using time to trigger a task (for example rebooting your phone every 3am everyday, or put your phone to airplane mode every day from 11pm to 5am).
Now that you've activated it, you can observe if it fixed your problem.
I have noticed that tasker will not execute the taske unless the screen is on. Even if it's not optimised and when using reliable alatms when off.
HatchetEgg said:
I have noticed that tasker will not execute the taske unless the screen is on. Even if it's not optimised and when using reliable alatms when off.
Click to expand...
Click to collapse
Have you disabled battery optimization for tasker?
ktmom said:
Have you disabled battery optimization for tasker?
Click to expand...
Click to collapse
Yes, I have had this issue quite some time.
Althought from my testing, it depends on the commands within the profile.
I have found a work around to switch ariplane mode on when screen off, by this action.
Run Shell > Command: echo lock_me > /sys/power/wake_lock ,use root: Checked
Then run this Action, near the end of the task.
Run Shell > Command: echo lock_me > /sys/power/wake_unlock ,use root: Checkedhis comand after the task has finished.
With the changes you suggested, Putting Reliable Alarms to Always and disabling battery optimization for Tasker this week it worked. Many thanks
Related
i wanna perform some tasks when the phone is going to power off or reboot, eg sync
i heard that a sync will be called if reboot is executed, so how about power off?
i wonder if i can do it in a way similar to linux's init6.d or init0.d, which i can tell the phone to do something b4 poweroff or reboot
thx
ykk_five said:
i wanna perform some tasks when the phone is going to power off or reboot, eg sync
i heard that a sync will be called if reboot is executed, so how about power off?
i wonder if i can do it in a way similar to linux's init6.d or init0.d, which i can tell the phone to do something b4 poweroff or reboot
thx
Click to expand...
Click to collapse
Linux, unlike some other Unixes, always calls a sync before halting the system. So it shouldn't be necessary. It would be nice to have somewhere to add shutdown scripts though. They probably wouldn't fire with a 'reboot' shell command though.
Best method might be to actually replace the reboot binary with something that can call shutdown scripts, somehow.
RyanZA said:
Linux, unlike some other Unixes, always calls a sync before halting the system. So it shouldn't be necessary. It would be nice to have somewhere to add shutdown scripts though. They probably wouldn't fire with a 'reboot' shell command though.
Best method might be to actually replace the reboot binary with something that can call shutdown scripts, somehow.
Click to expand...
Click to collapse
Yes, i know... but for normal linux distro only. i wonder android will sync always since it shuts down almost instantly
Get Tasker. You can automate practically anything with that app. I just checked and you can trigger apps or tasks to be launched when the shutdown command is launched.
jimmy-bish said:
Get Tasker. You can automate practically anything with that app. I just checked and you can trigger apps or tasks to be launched when the shutdown command is launched.
Click to expand...
Click to collapse
o really? Thx a lot
Not a problem. There's a 7 day trial available. It's definitely worth paying the money at the end of the 7 days, though. Use those days to really see what Tasker is capable of. There are guides all over the net on how to do some really cool stuff with it.
I have been using the latests builds to see if they mitigate a common problem in our devices (mine is a Polaris). The insufficient memory makes it lag until forever when switching amongst applications, not only the heavy ones, but also the supposed light applications like Messaging, Phone, Contacts, etc.
The system has to work under really hard conditions: 20 - 28 MB when starting up. Every application I run is a fire proof. Applications like Navigation makes our devices literally crawl and bite the dust. Not far away, I was driving and tried to play some music at the same time. It was impossible. The waiting was unbearable and it finally hung like a pro.
My question is: is there any chance to free up memory or use it more efficiently in order to avoid these undesirable situations?
Did polaris get back some memory with Froyo kernel like vogue did? From the video buffer or something... what res do you run at?
I'm running at 240x320 - 120 dpi
I made a screenshot of a "free" command in a terminal (see attachment image).
My kernel is this one (converted with Atools):
http://androidhtc.git.sourceforge.n...=2.6.32/VOGUIMG-320-FROYO-10-4-10.NBH;hb=HEAD
Thanks for your interest!
Im not sure.. but is there a way to use the sd as ram?
I think its not fast enough, but i havent seen any "benchmarks" yet how fast the ram on the polaris works.
Maby its slower but fast enough to work as swap etc?
Enabling compcache will help you.
Still, our little devices cannot multitask very well with Android, but I can navigate and play music at the same time, with compcache.
You will need drivers that match your kernel, in /system/lib/modules. I have packaged some in the first post of this thread that should work for each of the two popular kernel versions.
n2rjt said:
Enabling compcache will help you.
Still, our little devices cannot multitask very well with Android, but I can navigate and play music at the same time, with compcache.
You will need drivers that match your kernel, in /system/lib/modules. I have packaged some in the first post of this thread that should work for each of the two popular kernel versions.
Click to expand...
Click to collapse
Alright, I'm downloading the modules for 2.6.32. After applying the update, what should I do to enable compcache? Some time ago, this setting was in Spare Parts.
SuperJMN said:
Alright, I'm downloading the modules for 2.6.32. After applying the update, what should I do to enable compcache? Some time ago, this setting was in Spare Parts.
Click to expand...
Click to collapse
Open terminal
type: Su
and then
compcache.sh enable
-Arturo- said:
Open terminal
type: Su
and then
compcache.sh enable
Click to expand...
Click to collapse
any way to confirm that it worked?
margosmark said:
any way to confirm that it worked?
Click to expand...
Click to collapse
type FREE in terminal and look under swap if it shows zero then it's not active.
-Arturo- said:
type FREE in terminal and look under swap if it shows zero then it's not active.
Click to expand...
Click to collapse
yea, try doing free from a terminal you should have an amount of memory for the swap row
For testing...
Thank you SuperJMN for this thread : I hope this help us for better use of our phone.
Like you, when I try to use my GPS navigation (Navigon or Igo8) I'm bored that's too slow !! Impossible to change anything if I want...
I try now with Compcache enable, I can see 130024 (total and 104156 used) instead of 104024 : swap = 26000
Cheers.
manu33xtro said:
Thank you SuperJMN for this thread : I hope this help us for better use of our phone.
Like you, when I try to use my GPS navigation (Navigon or Igo8) I'm bored that's too slow !! Impossible to change anything if I want...
I try now with Compcache enable, I can see 130024 (total and 104156 used) instead of 104024 : swap = 26000
Cheers.
Click to expand...
Click to collapse
any better luck with comcache on??
Report
I installed this update for my .32 kernel (dated September, the 30th):
http://forum.xda-developers.com/attachment.php?attachmentid=409422&d=1285714954
My build is the latest: http://sourceforge.net/projects/androidhtc/files/system-froyo-01-10-10_16.tgz/download
When I open a terminal and type
su
compcache.sh enable
it states that compcache will be enable in 120 seconds.
After that time, a free command doesn't reveal any change.
I've also tried typing
su
compcache.sh start
When doing this, it processes the command and after 30 seconds or so, some lines are displayed:
Code:
insmod: can't insert '/system/lib/modules/lzo_compress.ko': File exist
insmod: can't insert '/system/lib/modules/lzo_decompress.ko': File exist
insmod: can't insert '/system/lib/modules/ramzswap_compress.ko': File exist
swapon: /dev/block/ramzswap0: Function not implemented
vm.swappiness = 30
After that, a free command doesn't reveal any change, too.
SuperJMN said:
I installed this update for my .32 kernel (dated September, the 30th):
http://forum.xda-developers.com/attachment.php?attachmentid=409422&d=1285714954
My build is the latest: http://sourceforge.net/projects/androidhtc/files/system-froyo-01-10-10_16.tgz/download
When I open a terminal and type
su
compcache.sh enable
it states that compcache will be enable in 120 seconds.
After that time, a free command doesn't reveal any change.
I've also tried typing
su
compcache.sh start
When doing this, it processes the command and after 30 seconds or so, some lines are displayed:
Code:
insmod: can't insert '/system/lib/modules/lzo_compress.ko': File exist
insmod: can't insert '/system/lib/modules/lzo_decompress.ko': File exist
insmod: can't insert '/system/lib/modules/ramzswap_compress.ko': File exist
swapon: /dev/block/ramzswap0: Function not implemented
vm.swappiness = 30
After that, a free command doesn't reveal any change, too.
Click to expand...
Click to collapse
Try this one
http://dl.dropbox.com/u/7688082/androidupdate.tar
Also is terminal added to the white list in super user app.?
Try with this update...
l1q1d said:
Try with this update...
Click to expand...
Click to collapse
It worked! Thanks!
By the way, the touchscreen behaves erratically with 4-oct NBH. Test with calibration app and tap the screen. You will notice abrupt lines.
Edit: if you want to see which behavior I'm referring to, watch this video: http://www.youtube.com/watch?v=DPLu41BUB1Y
It happened sometime in the past, but with this one it happens the same (although the abruptness is not as much as in this video).
Edit 2: Strangely enough, it is fixed on reboot, but after some time running the touchscreen starts to behave crappy again. It happens with the newest .NBHs made in October.
Basically I had 100% at 9am
at 1130 am I had 28% and this is without doing hardly anything.
I then put data packet mode off and airplane mode on -- and it lasted 2 hours without draining.
Therefore I know all the drain is due to some background apps.
Is there any tips, tricks, etc. to stop this drain ? like stop synching etc.
This battery drain is brutal!
Find the culprit ?
Install some app monitoring app like system panel and check?
You already know its something that needs internet. So check all your apps when they are syncing and how often. Check in some task manager of running app/services , cpu usage/network use, everything what should be dormant and its active. (or just check in the apps you ran if there isnt a circle running thats suggesting that app is doing something )
Oh one thing is not using skype and install adfree
PAGOT said:
Find the culprit ?
Install some app monitoring app like system panel and check?
You already know its something that needs internet. So check all your apps when they are syncing and how often. Check in some task manager of running app/services , cpu usage/network use, everything what should be dormant and its active. (or just check in the apps you ran if there isnt a circle running thats suggesting that app is doing something )
Oh one thing is not using skype and install adfree
Click to expand...
Click to collapse
I haven't found it yet - what apps would you specifically advise to use ? I have hotmail, google, and facebook on "sync" mode -- maybe I'll take that off and see if it works.
Other than that, I don't have hardly anything running that I can see -- WIFI and GPS is always off. I use a task killer on "INSANE" that closes apps constantly and everytime the screen goes off so I'm not sure what could be running.
Funkadelick said:
I haven't found it yet - what apps would you specifically advise to use ? I have hotmail, google, and facebook on "sync" mode -- maybe I'll take that off and see if it works.
Other than that, I don't have hardly anything running that I can see -- WIFI and GPS is always off. I use a task killer on "INSANE" that closes apps constantly and everytime the screen goes off so I'm not sure what could be running.
Click to expand...
Click to collapse
It can be:
- a weak network (2G/3G) constatly switching.
- Gallery bug
- File system errors
take a look on what "suck" your CPU time.
Install Better terminal:
/ $ su (enter)
#top (enter)
And watch & report.
ttf said:
It can be:
- a weak network (2G/3G) constatly switching.
- Gallery bug
- File system errors
take a look on what "suck" your CPU time.
Install Better terminal:
/ $ su (enter)
#top (enter)
And watch & report.
Click to expand...
Click to collapse
Awesome advice. I will go do that now and report back soon. Cheers
ttf said:
It can be:
- a weak network (2G/3G) constatly switching.
- Gallery bug
- File system errors
take a look on what "suck" your CPU time.
Install Better terminal:
/ $ su (enter)
#top (enter)
And watch & report.
Click to expand...
Click to collapse
what am i looking for exactly
I have this thing running
it's soooooooo choppy -- how do I stop it so I can analyze the data lol
i usually plug my phone into the computer and use adb logcat to see whats going on, i usually find the culprit that way
My battery Life sucks as well. These are the culpruts at the moment.
Voice Calls 17%
Display 17%
GPSD 17%
Maps 14%
Cell Standby 10%
Wi-Fi- 8%
TIKL 7%
Phone Idle 4%
Facebook 4%
Android Os 3%
Android System 3%
My thoughts are that is location based services such as google weather widget. I have disabled Latitude and the weather widget set to 6hr refresh. I should mention this is on a Galaxy i9000M running CM7 03122011.
UPDATE: Try BulletProofing Apps with my latest V6 SuperCharger Script! Use the following link OR use the link in my signature
I didn't want to risk making the SuperCharge & Bulletproof thread too confusing so I figured it best to make a "sister" thread.
This is a work in progress.
But if this information is helpful, please click the thanks button
HUGE thanks to Feeyo and Bear in NM for helping me figure out a workable solution on locking a background app in memory on boot up.
Feeyo gave me the gist of it but it wouldn't work on boot.
After posting in this thread at Droid Forums, things got rolling - with alot of help from Bear in NM.
Create a Unix script file with no extension (I named it 97oom) with Notepad++ and put it in your i/system/etc/init.d/ folder and put this inside:
Code:
#!/system/bin/sh
sleep 60
PPID=$(pidof [B]com.estrongs.android.safer[/B])
echo "-17" > /proc/$PPID/oom_adj
Permissions: chmod 755 /system/etc/init.d/97oom (same as 10overclock)
You can also do it on the phone itself:
1. Make a copy of 10overclock
2. Renamed it to 97oom (I have a 98governor and a 99complete so...)
3. Deleted the text and put the text you see above
4. Set permissions
Then reboot to test!
You can check to see if it worked with either Auto Memory Manager (AMM) or AutoKiller Memory Optimizer (AKMO).
The bold text in the above code is the process name of the app that you want to protect!
Note: You can get the process name from most process monitors or with AKMO or AMM.
That command "as is" will give ES Security Manager the highest priority of -17.
AKMO shows it as being ignored by the OOM killer
At first it wasn't working on boot because ES Security was not yet loaded in memory.
The "sleep 60 "command fixes that by waiting 60 seconds to execute the command
You can also do this in GScript Lite with this:
Code:
PPID=$(pidof com.estrongs.android.safer)
echo "-17" > /proc/$PPID/oom_adj
This comes in handy for apps that don't load on bootup - just run a GScript for those apps
I suggest you get Busybox Installer and have it install the latest BusyBox (v1.19).
This ensures GScript doesn't spit out ugly stderr: messages.
GScript Tip: 1. Make a file (with any text editor) with the commands
................. 2. Rename it with an .sh extension (example 97oom.sh)
................. 3. Put it in sdcard/gscript folder
................. 4. Run GScript, Menu key, Add script, and click Load file, select a script and Save (leave SU checked)
Even better, you can make shortcut for any GScript.
Long press desktop > Shortcuts > GScript Lite > Select... BOOYA!
As I said, this is a work in progress.
Taming the OOM Killer explains that an app will be ignored by the OOM killer if it has the -17 priority.
The problem is that Android will still shuffle it's priority downwards like it does with any inactive app.
If that happens, then the app reverts to it's usual priority.
This is why ESS will lose it's -17 after a couple of hours. It just sleeps ALL the time.
My thinking that if a more active background app, such as an SMS app or a music app is given the -17, it won't lose it's priority at all.
Feedback with results is more than welcome!
No need to set a variable, just use back-ticks:
Code:
echo -17 > /proc/`pidof [B]com.estrongs.android.safer[/B]`/oom_adj
Although that may be a little too complicated for some people to type in. Best to keep it simple I suppose...
That's pretty cool.
I figure most people would copy/paste the whole thing and replace the process name.
So maybe the back ticks wouldn't be a big deal.
That is why I try and avoid putting any code I use on forums. Someone who actually knows what they are doing will always come along and whack me ;^)
Seriously, good work Zep.
Craig
I don't mind.
That's all a part of learning so it's always good that there's somebody around that's "smarter" at something than me.
For example... this script I'm trying to get working for supercharging stock phones...
On custom roms, CM and FroyMod at least, I'd modify /system/etc/rootfs/init.mapphone_umts.rc
I flashed stock telus 2.2 and the path seems to be just /init.mapphone_umts.rc
I don't see rootfs anywhere
But there is a rootfs is mounted
To mount as rw, "mount -o remount,rw /system" doesn't work
In gscript, I'm getting "sed not found" errors too.
grrr...
how well do you think this would work with handcent? it's a little laggy to load up on my phone, but i want to try it out more. will keeping handcent in memory eat up ram that i need otherwise? and do you think it will be active enough to keep it's -17 after a few hours? thanks
edit: i was trying it out, it disappeard from processes withing a few minutes. oh well, maybe it doesnt need to be running anyway
Did you check with AMM to see if handcent had the high priority or if it really got killed?
ya, i checked. it was set to -17, then next time it refreshed it was gone. then i opened handcent, went back, and the process had a different pid, not oom level. oh well
damn
Maybe some apps are too prone to get killed off and the only way to keep them alive is with multitasking friendly minfree values
zeppelinrox said:
damn
Maybe some apps are too prone to get killed off and the only way to keep them alive is with multitasking friendly minfree values
Click to expand...
Click to collapse
Yes, I've seen the same happening with the stock SMS app. I did not receive SMS anymore so I decided to look at it a bit closer (using adb logcat). I started the SMS app, noted down the PID and set the oom_adj value to -17 using adb shell. A few seconds later it was killed. Setting the minfree values back to system default allows me to receive SMS again. Also whatsapp, gtalk and push mail now work reliable. With high minfree values I could see in the logs that, when a message arrived the app is started and immediately killed afterwards. So, I was never notivied that a SMS or whatsapp message had arrived. With default minfree values it seems to work more reliable.
But it all depends on how you use your phone, I guess. I'm using it as my communication central and don't want to miss any message. If you use it more as your mobile gaming or surfing device you might still be better off with high minfree values.
I agree.
That's why I made 6 different profiles.
The multitasking and balanced 2 settings, for example, will leave you with more free ram but are actually more background app friendly than stock google/android values.
zeppelinrox said:
I agree.
That's why I made 6 different profiles.
The multitasking and balanced 2 settings, for example, will leave you with more free ram but are actually more background app friendly than stock google/android values.
Click to expand...
Click to collapse
I see. I did not realize that. It seems I've been reading your post too superficially.
I'll give those settings a try. I've just lost another SMS (this time with the default setting)
If I can't get this under control I might go back to CM6. I understand this is not as memory hungry as CM7 is.
Well, handcent is a giant pain in the ass.
I'm running stock telus froyo and the thing doesn't even stay loaded and I'm not even doing anything.
I run it.
Try and bulletproof it with a gscript (and sometimes handcent is even killed off if I take too long opening gscript lol)
The script won't even change the priority of hancent.
It stays at an 9 or 10 in the content provider grouping.
But the thing is a pig anyway.
20+ mb of ram used up and the app itself is close to 5 mb.
Maybe froyo has a reason to not like it? LOL
very very important and informative post!
thank you!
one question: any idea why "Auto Memory Manager" isn't avialable to
milestone according to market?
I can't install it from market site and wasn't able to find it in market application?
zeppelinrox said:
Create a Unix script file with no extension (I named it 97oom) with Notepad++ and put it in your i/system/etc/init.d/ folder and put this inside:
Code:
#!/system/bin/sh
sleep 60
PPID=$(pidof [B]com.estrongs.android.safer[/B])
echo "-17" > /proc/$PPID/oom_adj
Permissions: chmod 755 /system/etc/init.d/97oom (same as 10overclock)
You can also do it on the phone itself:
1. Make a copy of 10overclock
2. Renamed it to 97oom (I have a 98governor and a 99complete so...)
3. Deleted the text and put the text you see above
4. Set permissions
Click to expand...
Click to collapse
I did it, and after reboot stock sms app (com.android.mms) is killed, I cheched in AKMO, and that fix didn`t help, so I set default minfree values in AKMO (although the previous settings weren`t so strict)
Ok, first off, I am a UK Milestone, running Cyanogenmod 7 RC4. I am trying to raise the oom_adj of COM.ANDROID.MMS and I just used the method zeppelinrox posted instead of the proposed alternative (though I did try that too) and the startup command seems to do nothing. So I decided to try the GScript way and I get this:
Code:
stderr:
stderr:
stderr:
stderr:
stderr:
stderr: cannot create /proc//oom_adj: directory nonexistent
stderr:
stderr:
stderr:
I have never used GScript before and maybe I am doing something wrong here, but I am running it the script as superuser, I have exactly what zeppelinrox has (except a change for the messaging app process name) and I am at a total loss here. Other methods worked fine on my RC3 and keep Messaging as a "Foreground Group" app, but in RC4 it is an "Empty" and that means it will likely get killed a lot. I am using stock minfree values, just using AMM to check oom. I don't want to be missing texts, so any help would be greatly appreciated. Let me know if you need anything else.
You get that "directory nonexistent" error because the app was already killed so there is no PID anymore.
I suggest you get Busybox Installer and have it install the latest BusyBox (v1.19).
This ensures GScript doesn't spit out ugly stderr: messages.
I finally installed CM7 for the first time and RC4 at least does have the option to lock messaging app in memory.
It's sitting in the foreground with a 0 priority
I thought that maybe it was killed already also, but I opened Messaging -> checked System Panel to ensure it was running -> ran the GScript (which failed as noted before) -> and checked System Panel once more and it was still running. Maybe I am crazy here..
I am using the "Lock messaging in memory" but "Messaging" process is still killed by the stock manager, is it still alive in some separate process? It certainly is not 0 priority in Foreground, still sitting in "Empty" at something generally over 4 priority.
I will probably just switch back to the previous build as all was well there, though I would like to be able to keep up with the newest features.
Thank you for the Busybox link, I will try that.
That's strange.
Maybe that setting needs a reboot?
I remember seeing messaging in content provider earlier and then I was actually surprised to see it in the foreground.
I actually checked to see if I still had the 97oom file in the init.d folder but it's not there.
But it should be immediate because if I uncheck Lock messaging in memory, it gets instantly killed.
I run it, check lock messaging again, and AMM shows it in the foreground group again.
Stderrs... now I dunno what's going on with that
GScript was working perfectly in stock Telus rom without stderrs after installing busybox (to get certain commands to work).
But in CM7, after updating busybox, stderrs all over the place.
Now I have to figure this out.. those stderrs are annoying as hell
zeppelinrox said:
You get that "directory nonexistent" error because the app was already killed so there is no PID anymore.
I suggest you get Busybox Installer and have it install the latest BusyBox (v1.19).
This ensures GScript doesn't spit out ugly stderr: messages.
I finally installed CM7 for the first time and RC4 at least does have the option to lock messaging app in memory.
It's sitting in the foreground with a 0 priority
Click to expand...
Click to collapse
What am I missing here? I'm looking at my CM7 Milestone right now with the "lock messaging app in memory" selected. And the messaging app is sitting in "background". Then I set the oom_adj value to -17 and a few minutes later messaging is gone. I'm starting to become desperate.
Hello i have no plan from Tasker.
I need to do the Following
Every Night 2am it should turn on Display launch a app inside this app navigate to a button to launch a 30 second ad and after watching this it should close the app and turn display off....
Anyone can help me step by step to do that?
No one?
You could find the solutions for this in this location.
https://tasker.joaoapps.com/userguide_summary.html
Long time ago i needed an app to be cleared the cache everyday, but i have not kept that tasker stuff.
You do need to make a task with the start and stop things, and also a profile that starts at a certain time and then starts the task you made.