Revised “Juice Defender”-like Tasker profiles

A couple of months ago, I posted up My “Juice Defender” Tasker Profiles. I've had a while to play around with different versions of those profiles, and this is what I've finally settled on. (I'm going with Tasker shorthand here and just showing you the final product—if you need handholding on how in general to build a profile, see the prior blog post, which walks you through step by step.)

Under Variables, you'll need to create two variables. I called them %DATA and %SCREENOFFTEST.

Under Profiles, create a profile called Screen Off Data Off. The triggers are the event Display Off and the state Not Power Any. Then create a Task called Screen Off Data Off.

You can see what I built here. The basic gist of it in plain English is that it turns on a temporary test to see if the screen stays off. Then it waits 15 minutes. If the test is still on, it turns the data off, turns auto-sync off, and then cancels the test.

Tapping the wrench in the bottom-right corner brings up the Task Properties. Set the Collision Handling to Abort Existing Task. This means if you turn the screen off and then turn it on again and turn it off again within 15 minutes, the first instance of this task will be aborted in favor of the most recent time you turned the screen off.

The next Profile is called Screen On Data On. The triggers are an event of Display Unlocked and a state of Not Airplane Mode. Then you'll also create a Task called Screen On Data On.

For this profile, you can see the end product again. The gist is: if you wake up the screen, that test from earlier should be off. And then if data is off, you turn it back on again.

I made the timeout 15 minutes so that the data isn't constantly turning off and on again, but I still get the battery life savings. I also turned off auto-sync for good measure. It doesn't really need to be off, though. If data is off, Android won't look to auto-sync. Lastly, I made the trigger for screen on data on to be unlocking instead of just turning the display on. That's because on my phone (the Galaxy Nexus) it can be sometimes easy to accidentally jostle the power button, so I don't want to turn on data until I unlock the phone, which means I'm actually using it for something data-related. The data reconnects fairly quickly on the Galaxy Nexus (on my old phone—the MyTouch 4G—the reconnection time was much longer).

I hope you found this helpful!


Verizon Galaxy Nexus First Impressions

I just got my third Android phone. You can read about my previous experiences: T-Mobile MyTouch 3G First Impressions, Why people get Nexus phones: I rooted my MyTouch 4G after less than one day

This time, I got a Nexus phone—the Samsung Galaxy Nexus. I’m just going to list the positives and negatives. These are positives and negatives for me. There may be things you care about that I don’t and things I care about that you don’t. Either way, you may find these lists useful in some way.


  • Swipe-away notifications.
  • Swipe-away recent apps list.
  • Software buttons.
  • Beautiful screen.
  • Built-in screenshot ability without root (volume down button and power button together).
  • Verizon LTE network.
  • I have a Tasker profile that’s a tweaked version of what Juice Defender does. It’s either near-instant or only one second to reconnect when the screen turns back on.
  • No shutter lag on camera.
  • Camera photo quality better than most reviews would have you believe.
  • Speaker is audible, despite what negative reviews say.
  • No need to root to get vanilla Android.
  • Will get updates to new version of Android before other phone models.
  • Not much bloatware on here, but Verizon managed to squeeze a couple of useless apps on. With Ice Cream Sandwich, you can disable these apps even if you can’t uninstall them.


  • Headphones are noise-reducing ones, which are really uncomfortable for me. I know others prefer these. And I found an extra set of old headphones I can use instead.
  • Autorotate is slow.
  • The Android File Transfer app for Mac OS X needs the phone to be unlocked (makes sense, but confusing before you know it), and can transfer only one folder at a time from Finder.
  • Even though speakers are audible, they are not loud, so you will have to crank them up to the max volume to get decent sound.
  • Facial recognition to unlock takes too long. It has to load in a second or two before it even tries to recognize your face.
  • Battery life is not good. The screen is huge, and in the battery stats it easily takes up more than 50% of the battery use. Fortunately I can make it through the whole day using my pseudo–Juice Defender profile in Tasker. I also bought an extra battery from Verizon for $20.
  • The menu soft key (which is now three dots) is sometimes at the top of the screen and sometimes at the bottom of the screen.
  • Keyboard autosuggestions is worse than the Gingerbread keyboard, which was awesome. I used to get four or five autosuggestions. Now I get only three and have to long-press on one to get more.
  • Now that file transfer is MTP, I can’t use DoubleTwist as I normally would. Luckily, I could copy a ton of music and then use the AirSync plugin to finish the rest of the sync wirelessly. I understand why Google moved from MSC to MTP, but it’s also screwed things up a bit.
  • The screen is large, which is beautiful, but it also means I can’t do one-handed WordFeud/Words with Friends while on the bus.
  • If you use the slide-to-unlock unlock method, there’s no way to disable the haptic feedback on it.

Overall, despite all the cons, I love this phone. Ice Cream Sandwich has a beautiful UI, which is a joy to use. The phone is fast. And Verizon’s LTE is wonderful.