Android 4.1.1 issues

[Michael Kizer]

I just received the OTA update to Jelly Bean (4.1.1) on my Verizon SGS3 and it seems to have broken a couple of things in Tasker.

I have a car mode profile that is triggered when I connect to my Bluetooth. It simply does the following:

1. Load App - Poweramp

2. Media Volume = 15

3. Stay On when connected to power

4. Send Intent (to turn driving mode on for a driving mode widget

1 & 4 seem to work fine, but 2 & 3 do not.

I did turn on the "Tasker - JB" option in Settings->Accessibility, but that had no effect...other than announcing a few random items in the UI (like opening a folder or switching home screens). And yes the "Talkback" service was turned off.

Anyone else get these to work on JB?

Thanks!

[Scott Miller]

I have the same device, also just updated. I have a profile to detect power, and use the stay on event. It is working for me. You didn't mention, so I will add that I have root. I was able to maintain it after the ota. Not sure if that is  relevant or not.

I don't adjust media volume, so I can't currently confirm that one.

Scott

[Michael Kizer]

On Monday, December 17, 2012 6:33:50 PM UTC-8, Scott Miller wrote:

I have the same device, also just updated. I have a profile to detect power, and use the stay on event. It is working for me. You didn't mention, so I will add that I have root. I was able to maintain it after the ota. Not sure if that is  relevant or not.

I don't adjust media volume, so I can't currently confirm that one.

Scott

Hmmm, strange. I do have root and this profile was working fine prior to the update. 

[Pent]

> I have a car mode profile that is triggered when I connect to my Bluetooth.
> It simply does the following:
> 1. Load App - Poweramp
> 2. Media Volume = 15
> 3. Stay On when connected to power
> 4. Send Intent (to turn driving mode on for a driving mode widget

Stay On is not possible without root in 4.2, but if I remember right
it's fine in 4.1. Try running it
manually to check it's not a problem with the condition. Send Intent
is definitely OK, it's not
Android-version dependent.

Pent

[Michael Kizer]

On Monday, December 17, 2012 10:53:03 PM UTC-8, Pent wrote:

Stay On is not possible without root in 4.2, but if I remember right
it's fine in 4.1. Try running it
manually to check it's not a problem with the condition.

I finally got back to tinkering with this one. I setup up a new profile called "Dock" with the only condition being Power (source: AC). The task is simply Stay On (with AC or USB power).

I set my display timeout to 15 seconds.

If I plug it into the dock, the "Dock" task becomes active, but the screen does not stay on. So, the problem could be that root is required, and the OTA update to 4.1.1 removed it.

I'll have to play around with the new method for gaining root on the Verizon SGS3 4.1.1 since the old method no longer works.

[Michael Kizer]

On Wednesday, January 2, 2013 2:03:28 PM UTC-8, Michael Kizer wrote:

If I plug it into the dock, the "Dock" task becomes active, but the screen does not stay on. So, the problem could be that root is required, and the OTA update to 4.1.1 removed it.

I'll have to play around with the new method for gaining root on the Verizon SGS3 4.1.1 since the old method no longer works.

OK, I was finally able to restore root access to my phone (verified with Root Explorer), but unfortunately this simply Stay On task still does not work. 

Anything else I should try?

[Pent]

> OK, I was finally able to restore root access to my phone (verified with
> Root Explorer), but unfortunately this simply Stay On task still does not
> work.

You need to also install the Secure Settings plugin and use that
instead of Tasker's builtin Stay On action.

Pent

[Michael Kizer]

On Thursday, January 3, 2013 11:56:56 PM UTC-8, Pent wrote:

You need to also install the Secure Settings plugin and use that
instead of Tasker's builtin Stay On action. 

OK, I installed Secure Settings (along with the Helper app), and replaced the Stay On step in my tasker profile with Secure Settings' "Stay Awake While Charging" (AC, USB). Still, no luck.

Anyone else have a Verizon SGS3 with 4.1.1 and able to get the display to stay on while charging?

[Scott Miller]

Yes, using the built in Tasker action. I am using "with AC or USB power." It works fine. Stock ROM, Verizon SGS3.

Scott

[Michael Kizer]

Well, I was searching around XDA Developers and came across a simple solution that seems to work (sort of). It seems some others were having issues with this since the 4.1.1 upgrade.

Instead of using the "Stay On" action, simply adjust the Screen Time Out value. So now, when connected to AC/USB I set the Screen Time Out to 20 hours, the Exit task resets it back to 5 minutes.

This works OK, although if I check the Display settings while connected to power, it says "After 34 minutes 7 seconds of inactivity". So, I'm assuming that this is probably the maximum value it will accept, or the display of the time in Settings is a bit wonky (I haven't tested it for the full 34 minutes yet).

[KCoram]

I'm having a similar problem with the media volume. I have a profile that only sets the media volume when Bluetooth is connected. the profile is entered just fine, but the volume is not changed. An identical action tied to a "headphones connected" profile for when my earbuds are plugged in works just fine.

When I use the volume rocker with my Bluetooth headphones connected, the volume dialog shows a Bluetooth symbol instead of a the Speaker icon shown when changing volume with earbuds connected.

My suspicion is that the 4.1.1 update has introduced a separate Bluetooth Media setting that either Tasker doesn't yet support (or that I just can't seem to find).

[Michael Kizer]

On Friday, January 4, 2013 3:06:24 PM UTC-8, Kevin Coram wrote:

I'm having a similar problem with the media volume. I have a profile that only sets the media volume when Bluetooth is connected. the profile is entered just fine, but the volume is not changed. An identical action tied to a "headphones connected" profile for when my earbuds are plugged in works just fine.

Yes, I have the same issue with media volume and Bluetooth. Good observation on the separate setting. Hopefully, it'll get fixed eventually.

I've been trying the same type of setup using NFC Task Launcher, but setting the media volume is hit or miss so far. I can't tell if it is getting set each time, or if the setting is sometimes remembered by Poweramp. 

[Dan]

My SG3 switches off after 34 minutes. That workaround does not work for me, apparently. See also https://groups.google.com/d/topic/tasker/3lJli5ACnW0/discussion

Anyone has found a solution for this?

Dan

[Peter Bongé]

I don't think that there is a separate volume setting for bluetooth. I've also had media volume problems with a bluetooth device on my Nexus 4 (Android 4.2.1). So I've done some testings without Tasker:

1. Set media volume to 5 and connected the BT device -> Media volume changed automatically to 10.

2. Set media volume to 15 and disconnected BT -> Media volume changed automatically to 5.

3. Directly re-connected the BT device -> Media volume changed automatically to 15.

That means: Jelly Bean remembers the media volume for BT devices and sets it if a device is connected and after disconnecting the previous volume will be set.

That also means: Switching on BT and changing the media volume shouldn't happen in the same task.

[Kevin Taylor]

I had the same problem on a Sony Xperia Z.
I'll try the 2 second wait - thanks for the tip.

On Wednesday, 27 March 2013 14:56:46 UTC, David Vaughn wrote:

This thread has been ded for a while but I have solved my Bluetooth Media Volume problem and wanted to post it in the event someone else has the same issue.

 

I have a Samsung Galaxy S3 (I535) running 4.1.1.  Is what I did was set my bluetooth headphone profile to be:

 

One Connection to headphone -> Wait 2 Seconds -> Set Bluetooth Voice volume to 7 -> Set Media Volume to 9.

 

That 2 second wait seemed to fix the issue for me. Hope this helps someone else also.