Run app not working after Galaxy S4 upgrade to Android 4.4.2

[Steve Rothkin]

I just got my wife a brand new Samsung Galaxy S4 (Verizon LTE). It came with Android 4.3. Initially I rooted it and then loaded the latest Tasker (from the Play store) while still on the stock OS as it came from Amazon (the OS update wouldn't work until I later activated the phone).

Anyway, tasker worked fine with Android 4.3 stock. It successfully ran all of my startup apps in the "Boot Run Tasks" task (which indirectly keys off of tasker monitor start).

Then I used the Verizon updater to upgrade the phone to the latest stock I545VRUFNC5 firmware which is Android 4.4.2. Now, NONE of the apps get started (and I don't see any errors about launching them either).

I did also happen to lose root in the upgrade process (and haven't been able to get it back yet, quick internet search indicates that this version of the firmware is locked down even tighter than the one that came on the device).

I've attached a debug log that was running while I manually triggered the "boot" processing (through a tasker shortcut on my home screen) and I've also included the full tasker backup and a snapshot of the about device screen.

[Scott Miller]

I don't think this is a Tasker problem. I have the same phone, upgraded to 4.4.2 via OTA, and have root (search for towelroot, but read everything). During boot, most things, but not everything, seems to hang. If I open task manager and free memory from the RAM tab, everything starts. Something is blocking, but I don't know what. I'm considering a factory reset if I can't find it otherwise. But Tasker runs just fine after I clear the block. Nothing conclusive from my own logs yet, but if I get a chance I might take a look at yours to see if I can get a clue.

Scott

[Steve Rothkin]

OK, after finding towelroot and getting root back, now everything is
working correctly. Surprised that Tasker needs root to run apps (even
chained from a home screen shortcut), but I guess (at least in Android
4.4.2) it does.

[Scott Miller]

I doubt that's it. I've heard others complain about slow boot times, but after several reboots it got better. Sadly that's not the case for me.

Scott

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.
Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[Pent]

working correctly. Surprised that Tasker needs root to run apps (even
chained from a home screen shortcut), but I guess (at least in Android
4.4.2) it does.

I can't explain your observations, but if we're talking about Load App,
I can definitely say that root is totally irrelevant.

Pent

[Steve Rothkin]

This had nothing to do with boot time. Although the tasks were invoked from the monitor start event, I can also invoke them from a tasker shortcut on the home screen and the problem happens then too.
And, like I said, fixing root fixed the problem.
Anyway, slow boot time wasn't an issue.

[Steve Rothkin]

Maybe something changed in this particular firmware release from Verizon/Samsung that makes it relevant.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/5BdIqnvmW6Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--
Steve Rothkin (914)762-4566 Check out my professional profile and connect with me on LinkedIn: http://www.linkedin.com/in/stevenrothkin/