Application profiles not working after upgrade to Gingerbread

[golightly]

After upgrading to Gingerbread ROM (InsertCoin 1.08 on HTC Desire) I
have suddenly found that no application profiles fire in Tasker. I
have reselected the applications and even created a test profile which
simply pops up an alert when I start calculator - but it never gets
fired.

Does Gingerbread communicate the app start in a different way? I've
noticed a few other posts complaining about certain events not firing
properly after a Gingerbread upgrade. Could someone with a
Gingerbread ROM on a different device (preferably a stock one) just
test a simple profile based on an "application" and see if it works?

[Pent]

> Does Gingerbread communicate the app start in a different way?  I've
> noticed a few other posts complaining about certain events not firing
> properly after a Gingerbread upgrade.  Could someone with a
> Gingerbread ROM on a different device (preferably a stock one) just
> test a simple profile based on an "application" and see if it works?

It works on stock. Some people have complained about it not working in
Cyanogen 7, is your ROM based on that maybe ?

Pent

[joeviocoe]

When wiping or flashing a new ROM, and restoring Tasker, I find that
the "Settings/Accessibility/Tasker" becomes unchecked. And profiles
that rely on window titles won't work until I recheck. Is this your
problem?

[t4r]

I have the same problem on the CM7. Context application does not work
with any application. "Settings/Accessibility/Tasker" I have checked

[Pent]

http://groups.google.com/group/tasker/browse_thread/thread/4c48fcfc38d4f11/201baf242f121fbd?lnk=gst&q=CM7+lock#201baf242f121fbd

?

Pent

[golightly]

Thanks all.

The settings | accessibility | Tasker setting was unchecked which got
me excited: but no joy. Unfortunately I am not running a CM7 ROM.
However, there might be some CM7 code base. I don't have access to
the settings indicated in the referenced thread but I'll do some more
digging around in the ROM thread and see if I can discover a cause.

(incidentally, I did search before posting but searched for
"application" rather than "app" - just goes to show you can't be too
restrictive when looking for help!)

On Jun 12, 12:00 pm, Pent <supp...@apps.dinglisch.net> wrote:
> http://groups.google.com/group/tasker/browse_thread/thread/4c48fcfc38...
>
> ?
>
> Pent

[t4r]

Thanks PENT
for me, helped unchecking the "Lock home in memory" in settings CM

[golightly]

Can anyone explain what this setting achieves in CM7. I'll check on
their forum too to see if there's something I can learn.

[t4r]

I nothing changed and the application context is not working again.
I tried to check again and uncheck "Lock home in memory", restart my
defy and reinstal tasker
but without any effect

[Adam]

On Jun 11, 7:37 am, golightly <goo...@garylane.com> wrote:
> After upgrading to Gingerbread ROM (InsertCoin 1.08 on HTC Desire) I
> have suddenly found that noapplicationprofiles fire in Tasker.

I find the same.

Is this the fault of Tasker, InsertCoin or Gingerbread? Can devs
perhaps elaborate?

[Adam]

According to this thread: http://bit.ly/oU3zOS it is because
InsertCoin (and other) ROMs are 'deodexed'. Anything to be done in
that regard?

[BossMan]

How about trying the other way: http://android.modaco.com/topic/345141-odex-me-application/? :)

BR,
A.

[BossMan]

Deodexing should not have any impact on this - it's just a way apps are built (in order to get performance in some cases), but doesn't change how the system works.
I have a stock rom, which is odexed, but I asked my friend who has a deodexed GB ROM if he could try an app context, and it works for him - it just confirms it's not deodexing that causes this.

BR,
A.

[Krassimir VB]

Copied from XDA:

"A workaround for this problem is to change "ro.HOME_APP_ADJ=-17" in /
system/build.prop to "ro.HOME_APP_ADJ=1". After that, Tasker could
detect apps running in the foreground."

It's working for me that way.

[jeg...@gmail.com]

I'm having the app detection issue on MikG 2.52 (at least 1 other person on this ROM has the same issue), with one exception I've found so far - it will detect the Phone (dialer) app. The value in the build.prop on this ROM is "0" (zero) and I have not idea what to change it to, anyway. Pent - any ideas?

[Pent]

Only to experiment with the value.

Pent

[expose11]

So, if I do this

"A workaround for this problem is to change "ro.HOME_APP_ADJ=-17" in / 
system/build.prop to "ro.HOME_APP_ADJ=1".

I have two questions,  1. Do I use something like ES File Explorer (with Root Explorer checked and Mount File System checked) to open and edit the file (using the ES file explorer built in text editor.  AND 2. Do I just save it using the text editor or do I have to do anything else to make the system recognize it.  

Anyone tried this? Does it work?

[Rick Raiton]

I'm running MikG 2.5.1 and I can confirm that this works. I did try
first to create the setting in /data/local.prop as mentioned in one of
the linked threads, but that did not work. I used root explorer to
edit /system/build.prop directly and Tasker now detects app launches.
Along with the Secure Settings plugin I can now turn on/off GPS once
again when I start Maps, Nav, Golf app, etc. !!!!!

[expose11]

Thanks Rick. I also posted in MikG on XDA where this discussion was also going on.  Should help some folks out.

[jeg...@gmail.com]

Worked for me too, thanks for testing guys. I wasn't going to play with that file before a weekend... ;)