location context not firing up until display is on/unlocked?

[M.Emrah OZKAYA]

hey, I have HTC Evo 3D and have a bit of a problem with Tasker. I want
to use net location feature (since Cell near is reported to be not
working when display is off) and I set up the radius large enough.
(2km or even more) I also have always on mobile data and background
data is enabled. Under monitor section of Tasker, display off timing
is 600 seconds. Well, after I enter a location (say, work) and wait 1
hour or more, still nothing. After I unlock the screen, it takes about
2 seconds to fire up the context. I have Android 2.3.4 and stock HTC
ROM if it makes any difference.

[Pent]

I havn't heard that one before. Could you make a log which starts
before you turn the device off to go to work and stops after you turn
it on at work ?

http://tasker.dinglisch.net/faq-how.html#x2

Thanks,

Pent

[M.Emrah OZKAYA]

I sent you the log. I would appreciate if you can have a look. Thanks.

[V Oz]

Not only Location context.

Cell Near, Sensor Orientation  (they work with Timer every 2 min or when display on)

Clear Run Log can send tomorrow if needed

I think Android 234 in stand by mode does not allows access to some resources. So, timer event wakes up system for a moment and ... 

[Ionized]

I am having the EXACT same problem:

I have @work and @home profiles, each of which work fine as soon as I
unlock the screen within the context location. They are using network
only, not gps, and again the profile works when phone is unlocked, the
radius is large and works fine. However, I want it to work while the
phone is still in my pocket, the profile should activate and perform
the tasks once I enter the location even IF the keyguard is still
active, because sometimes I can't get to the phone right away but I
want the tasks to be performed right away(at least within the 3 minute
location update time)

Also, I have already adjusted the screen off network location check
time(all check) to 3 minutes instead of ten, but that did not help. I
tested yesterday and this morning and after being in either location
for more than 5 minutes before unlocking the phone to see if it
worked, the profile STILL only went active and performed tasks as soon
as the screen unlocked.

Tonight I plan to disabled keyguard and then enter home location to
test if it is keyguard preventing the location context from updating.
If this is the case then with keyguard off the context should update
and tasks should run as intended. I will repost tonight with results.

Thanks to op for starting this thread, glad to hear I'm not the only
one.

Sent from samsung transform ultra on boost, 2.3.4

_robert

[Ionized]

I tested the setup on the way home from work just now and I was able
to confirm that even with Keyguard disabled, Android 2.3.4 does NOT
update network location with the Display off.
Hence, the only way for the Context to enable is when you hit the
power button and turn the screen back on. So rather than being
completely automated, you have to hit one button.

Hopefully a workaround can be found as this is one of the major
functions that I really like about Tasker! I have been trying to make
this work ever since I purchased Tasker a few days ago, and I am glad
to finally know that it isn't anything wrong with my setup but rather
with 2.3.4.

On Oct 18, 3:33 am, Pent <supp...@apps.dinglisch.net> wrote:

[V Oz]

ATM You can add timer event "Every 2 minutes" to @home @work profiles. Yes it's workaround and have limits like no exit task, but it works.

Hope Pent will check this ASAP

[Pent]

Thanks for the log.

It shows that the device is being turned on to check the location and
staying on correctly. Battery change events are received during that
time, but no location fixes.

Could you try leaving Wifi set On and in Android settings Wireless &
Network / Wifi Settings / Menu / Advanced / Wifi Sleep Policy select
'Never'.

I will add a preference for next version to keep the screen on dim
while doing background checks. That should help with the identical
Cell Near problem and may help with this one.

Pent

[M.Emrah OZKAYA]

Something weird happened today, I changed my EVO 3D's stock ROM to a
custom ROM and also changed to a custom kernel with the second core
always online with ondemand governor (in stock, it is offline and only
kicks in when needed) and also overclocked. And somehow I seem to be
getting correct location notifications today. It might be coincidence,
I need to test it more and but still... Maybe we can find a pattern
with someone.

[M.Emrah OZKAYA]

Oh and also, I had SetCPU installed and now switched to System Tuner.
Does anyone with non-working location triggers have any of these in
common?

[V Oz]

eer... I've done some experiments on weekend with locations.

And find that if CellNear context is true then Location context checks and works even with display locked. But only CellNear ... I didn't find true - works or no.

I didn't look for dependencies on governors. My Daemon Controller sets "powersave" for sleep governor for now.

Now, I'll try ondemand for sleep and check it ASAP.

[Ionized]

I tried the suggestion of adding a profile task that checks location
every 3 minutes if the screen is off, and even this did not work. I'm
going to keep trying different things but as of yet I have not been
able to get tasker to perform the tasks when the display is off.

[V Oz]

It seems Secure Settings plug-in with CPU Awake Only for 30 secs triggered every 2 minutes can be used as crutch for updating Cell Near contexts - not Display Dim (which runs with error for me)

It's not reliably and I'll continue oversee on this.

I've log states of CPU governor and frequency before and after launch of plug-in - both stay in "sleep" state, was set in Daemon Controller.

[V Oz]

Hi, Pent.

I confirm that profiles with Cell Near only or with Cell Near & GPS location contexts work fine in conjunction with profile contains Time context (Every 2 or 5 minutes) with Action Secure Settings plug-in CPU Awake Only 30 secs.

CPU Governor and frequency are stays on sleep states at triggering Time context moments.

AFAIU, that CPU Awake Only make Partial WakeLocks for a time (30 secs) .

Tomorrow I'll repeat this test with Debug SD and Run logs. Let me know if You want to see them.