• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Anyone using Tasker?

this is a sad day indeed....

i wonder if the dev will have a work around to this

I hope someone does or Google at least removes this restriction in Gingerbread when it eventually comes out. This is the one thing I REALLY HATE about Froyo. I had a couple great Tasker profiles set up to kill apps, but now I have to do it myself, booo.
 
this is a sad day indeed....

i wonder if the dev will have a work around to this

How is it a sad day? Killing apps promotes instability in the system. Re-jiggering the OS to prevent this gives you a more stable OS and forces you to deal with the problem app that's eating resources. You're forced to actually deal with the gaping wound instead of just putting bandaid after bandaid on it. How is this a bad thing?
 
How is it a sad day? Killing apps promotes instability in the system. Re-jiggering the OS to prevent this gives you a more stable OS and forces you to deal with the problem app that's eating resources. You're forced to actually deal with the gaping wound instead of just putting bandaid after bandaid on it. How is this a bad thing?

It is a bad thing because it is not an option. Yes I agree that task killers, etc are overused, but with an app like Tasker it makes it very useful to allow it to kill apps. It was nice that when I got out of my car Tasker could turn off bluetooth and kill Slacker. Now I have to unlock my phone, open slacker, and then kill it just to make it stop playing music. And if I am on a call, get out of my car after switching the call from bluetooth to my handset when I get off the phone Slacker starts playing automatically, sometimes I don't want Slacker to start playing in the middle of a store or whatever just because I ended my phone call.

Or like AppAlarm Pro, it used to be able to kill pandora when you exited the alarm. Now you have to exit the alarm, then open pandora and kill it too. Why not let the app that started another app kill the app that it started?

Some people were abusing it, but when used effectively letting an app kill another app made things a lot easier.
 
I don't see why Tasker can't do this for you. I've got a profile that turns on BT when I'm in my car (so I can use my handsfree headset) and turns it off when I get out of my car. It functions perfectly fine under Froyo as it did with Eclair. My music apps play through an FM transmitter in my car. When I unplug the transmitter, music stops as it did in Eclair although this is a function of the app itself and not Tasker.
 
I don't see why Tasker can't do this for you. I've got a profile that turns on BT when I'm in my car (so I can use my handsfree headset) and turns it off when I get out of my car. It functions perfectly fine under Froyo as it did with Eclair. My music apps play through an FM transmitter in my car. When I unplug the transmitter, music stops as it did in Eclair although this is a function of the app itself and not Tasker.

My bluetooth does turn off, but Slacker does not. I play slacker through my bluetooth and even if I use the headphone jack it automatically switches to the phone speaker when the other output is removed. There is no way to pause/kill the app now on Froyo without taking the time to do it yourself. Like I said really annoying if I am on a call when I get out of my car so Slacker starts playing as soon as I end my call!
 
I agree, the ability for Tasker not to be able to kill apps anymore is a bit annoying to say the least. And no I don't believe in task killers :)
 
Is this the reason I can't have the camera button open a menu with my camera, camcorder, and bar code scanner anymore?
 
Is this the reason I can't have the camera button open a menu with my camera, camcorder, and bar code scanner anymore?

I haven't heard anything about froyo not allowing an app to capture a button press, I haven't tried it but I haven't heard any other complaints either.
 
I haven't heard anything about froyo not allowing an app to capture a button press, I haven't tried it but I haven't heard any other complaints either.

Well to make it work Yout need to kill the camera task as it pops up, which i understand is impossible now in froyo. The more i learn the more I want 2.1 back.
 
Well to make it work Yout need to kill the camera task as it pops up, which i understand is impossible now in froyo. The more i learn the more I want 2.1 back.

Yeah, that makes sense. I like chrome to phone and flash and my louder speaker too much or I would go back just for being able to kill apps and have a working sms timestamp
 
Hey chris, you think the dev (pent) will make a fix our something?

I highly doubt that it is possible as this is implemented it the OS itself. I think our best chance of having this on 2.2 would be a custom ROM built from source, that specifically addresses this issue as part of the ROM. Maybe google will change their mind and remove this restriction in Gingerbread, but again that isn't happening soon either

Oh and BTW, it's CHRLS = Charles, common mistake, that's why I added my name to my sig
 
Even more annoying than not being able to kill music apps (I was doing the same thing as the guy above when I undocked from my car) is that since 2.2, Tasker is causing beeps during my phone calls, like a "you're being recorded" beep every 20 secs or so. I know it's Tasker because once uninstalled, this problem goes away.

Tasker is basically useless to me now, Locale seems to handle location settings better anyway.
 
Even more annoying than not being able to kill music apps (I was doing the same thing as the guy above when I undocked from my car) is that since 2.2, Tasker is causing beeps during my phone calls, like a "you're being recorded" beep every 20 secs or so. I know it's Tasker because once uninstalled, this problem goes away.

Tasker is basically useless to me now, Locale seems to handle location settings better anyway.

I haven't had that issue at all. I have plenty of other useful profiles set up that make me still love tasker.
 
hey "CHRLS" after posting around a little about a fix to the kill app problem 1 way around it is replacing the kill app with the "Go Home" task.
 
hey "CHRLS" after posting around a little about a fix to the kill app problem 1 way around it is replacing the kill app with the "Go Home" task.

Ok, so does that just bring up the home screen and leave the app running? my main problem with not being able to kill apps is because I can't stop Slacker from playing music. I would like to be able to just get out of my car and tasker turn Bluetooth off and stop my music without having to take my phone out of my pocket. will this work?
 
Ok, so does that just bring up the home screen and leave the app running? my main problem with not being able to kill apps is because I can't stop Slacker from playing music. I would like to be able to just get out of my car and tasker turn Bluetooth off and stop my music without having to take my phone out of my pocket. will this work?

So what profile settings do you use so that tasker knows you're getting out of your car with the phone in your pocket?
 
So what profile settings do you use so that tasker knows you're getting out of your car with the phone in your pocket?

Bluetooth connected - I have bluetooth in my car so when it disconnects I am getting out of my car. I have it set to that Bluetooth device so it behaves differently when I use my Jabra headset
 
I'm having an issue with the wifi near state. I've got a profile that's supposed to trigger if I'm on AC power and wifi near is a particular wifi network. This has been working beautifully for me all week until today when it went off when I was 15 miles away from where the wifi is. Why is wifi near not detecting that I'm not near that wifi network any more? I leave wifi turned on 24/7 on the phone just for this purpose.
 
I fixed my "beeping during calls" problem with Tasker by reinstalling. However, it's now force closing a lot when I try to make Location profiles. Really annoying...

I suppose a workaround to our car dock problem is to set media volume to 0. At least then you won't hear it blaring in your pocket and you can then stop your media programs at your leisure.
 
I suppose a workaround to our car dock problem is to set media volume to 0. At least then you won't hear it blaring in your pocket and you can then stop your media programs at your leisure.

Don't know why I never thought of that. I'm adding that to my exit task right now :cool:
 
My bluetooth does turn off, but Slacker does not. I play slacker through my bluetooth and even if I use the headphone jack it automatically switches to the phone speaker when the other output is removed. There is no way to pause/kill the app now on Froyo without taking the time to do it yourself. Like I said really annoying if I am on a call when I get out of my car so Slacker starts playing as soon as I end my call!

I've had this same problem... most recently when I finished a call after having entered a hospital. Not good.

As I said in the Tasker forums... what's the point of having a smart phone if you have to do everything manually?
 
Well to make it work Yout need to kill the camera task as it pops up, which i understand is impossible now in froyo. The more i learn the more I want 2.1 back.

In the context for the Camera Button, set the priority to Highest and check the Stop Event option. This will prevent the notification from being received by the camera app, which will then prevent the camera app from starting in the first place.
 
Back
Top Bottom