mobileLockIdleTimer reported error on some device

[trevix]

One of users of my App, on a Android 10, model "POT-LX1T", reported an error on line 106:

Code: Select all

 105    if the environment = "mobile" then
 106         mobileLockIdleTimer --avoid darking the screen on mobile
 107    end if

The error is:

Error on line: 106 char: 1
Error: 624,624,253,253,241,353,573,253,241,353,

Is it possible that in some device this command doesn't work?
Note: Idle Timer is set, in the standalone application settings

No other Android device reported this error

Thanks for any help

[jacque]

That doesn't look like a normal LC error code so it's hard to say. But you could wrap the command in a "try" block so at least the error would be avoided.

[trevix]

I guess I would do that, but this will not solve the fact that I need certain part of my app to be always awake.
The error code I supplied is an edit version that gets sent home (to my DB) whenever an error occurs in the standalone (with the approval of the user, off course.
I wish i could make something useful of the Android simulator. Last time i tried, it took 2, 5 hours to launch the OS

[LCMark]

@trevix: The mobileLockIdleTimer command cannot throw an error - so I think there is perhaps something wrong with the error collection somehow. More strange is the fact it is error code 624 - the latter is 'wait aborted' - from what I can see the only way that error could be generated on mobile is through using the `quit` command whilst you are performing a `wait` (or some LC command which implicitly calls wait).

In terms of the emulator, have you tried setting up an x86(-64) android emulator, and testing from LC on that? The code they run is 'identical', but because its the same arch as the host OS they run at a much more sane speed.