Hot Problems: | Tasker Feature Requests

Some v2 table widget styles don't work or cause problems

Steve Waring — Thu, 28 May 2026 14:08:36 +0000

On text entries in a v2 table widget:
left/right alignment do nothing
a colour such as #FF0000 causes the text not to show at all
material colours such as primary do nothing

The following do work, and I assume others in the same groups do as well
a number for font size
cursive
bold

Cell Near cannot scan for 5G SA towers

lexiconart — Mon, 25 May 2026 11:14:40 +0000

I have several old profiles set up with Cell Near as a trigger, and have never had an issue with them until recently, when my evening profiles failed to trigger (the morning ones involving Cell Near triggered perfectly, and that was the last day any Cell Near profiles worked).

While troubleshooting, I realized that my carrier finally activated 5G Stand Alone (maybe part of the 2G/3G shutdown?). As a result, Tasker is unable to use Cell Near to scan these new cell IDs, the page remains blank even after scanning for 10+ minutes.

Does anyone know how to force Cell Near to read these new 5G SA towers?

Alternatively, is there an app that can feed this data to Tasker?

Here's what I tried so far:

Looking at a map of cell towers in my country, I can see that for LTE towers the formar used for Cell near is:
```
LTE:[MCC].[MNC].[cellID]
```
The map actually shows cell IDs for the 5G SA towers (it's 4 digits longer than the LTE cell IDs), but I'm not sure what the format for these towers are. I tried the following format:
```
5GNR:[MCC].[MNC].[cellID]
```
To further troubleshoot, I made a profile triggered by Cell Near to write the current cell ID to a .txt file:
```
Profile: Test Logs

State: Cell Near [ Cell Tower / Last Signal:{INSERT
ALL
CELL
IDS Ignore Cells:* ]



Enter Task: Log Cell ID

A1: Wait [
     MS: 0
     Seconds: 1
     Minutes: 0
     Hours: 0
     Days: 0 ]

A2: Write File [
     File: Download/cell_logtest.txt
     Text: %DATE %TIME - %CELLID
     Append: On
     Add Newline: On ]
```
1. When forcing LTE connection, it works to record new cell IDs
2. When going back to 5G, Cell Near goes green (but no arrow points to any of the LTE or 5GNR towers, and all values are 0). Also, the action doesn't record any cell IDs. When I force the Action to play, all it records is '%CELLID' instead of an actual value

Using Dismiss Scene v2 causes Wait For Scene v2 to fail (and thus can't validate scene data)

Steve Waring — Thu, 28 May 2026 14:19:13 +0000

This applies to Tasker 35.apk and 35-1.apk. I've requested beta access but an update has not arrived yet.

I love v2 Scenes - many many thanks.

So a task (Show) displays a V2 scene with various elements. There is a button with a Dismiss Scene event. After the Show Scene v2 statement, there is a Wait For Scene v2. All works fine, the values of the scene's elements can be access after the dismiss button is pressed, via variables.

I want to validate the scene's input before dismissing it, so change the Dismiss Scene event to a Run Task event. This task (Validate) checks all the input values are compatible with each other. If they are not valid it sets the text of a warning element in the scene, and returns. However if all the checks are ok, the screen needs to be dismissed and the main (Show) task needs to continue. Using Dismiss Scene v2 in the Validate task cause the Wait For Scene v2 to fail with a No active scene error. Changing this Wait For Scene v2 to have Continue after fail solves part of the problem, but the variables from the scene are not available to the task when it fails like this. My work round has been for the Validate task to copy all the variables into Global variables.

The validation cannot be performed at the time the Scene's elements are modified, because there is a lot of interaction between them, and regEx checking of text input fields, etc - it would be too onerus.

Is there a better way of performing validation before dismissing a scene?

Element of array does not work in text property of V2 scene elements.

Steve Waring — Sun, 31 May 2026 16:30:40 +0000

A value such as %myarray(%myindex) does not work when used as the text property of a Scene v2 element. This happens with text elements and Segmented button row elements, and probably others as well.

Second show scene v2 after wait for scene fails.

Steve Waring — Sat, 30 May 2026 15:13:15 +0000

If you show a v2 scene, wait for it with wait for scene result, and then show the original scene again, it either shows very briefly and then self dismisses, or it does not show at all.

A work around is to put a screen-id in the second show scene. Because of this simple work around, I think this is low priority.

Scene v2 vertical columns within horizontal row.

Steve Waring — Fri, 29 May 2026 16:33:42 +0000

If you have a horizontal row containing two vertical columns, only the first shows in the graphical part of the layout editor, and only the first shows when the scene is displayed. Please see attached screen shot.

sliders in Tasker actions difficult to control

Malcolm — Sat, 12 Jan 2019 12:17:47 +0000

Could the sliders (SeekBars) used by Tasker actions be improve or made customizable in settings? I find it impossible to use the press-and-drag method -- they just don't move, and the click method is very hit-and-miss. Using the arrows is often impracticable when the value range is large since the arrows change the value by only +/-1. Also in some cases a "logarithmic" (actually "exponential") scale would be more appropriate, e.g. for setting a Beep tone frequency where getting somthing in the middle of the audio spectrum on a linear scale that goes from ~0 to 16000 is extremely awkward. Or a simpler solution might be to include a keyboard edit box by clicking on the value.