Hi,
I experienced strange problems when activating the 'cell near' function on Tasker 5.1 to determine current position w/o GPS or google location services (LOS 15.01 03/24, latest modem/firmware).
After a few minutes (or cell changes, idk), the device slows down, finally reboots, and keeps on doing so even after reboot and dalvik/cache cleanup. In the logs, I find hundreds of lines saying
Google gives only one exact hit on the above log line, but links to a chinese article that is not exacly helpful to me.
@albsat reported in the LOS 15.1 thread:
Anyone else?
I experienced strange problems when activating the 'cell near' function on Tasker 5.1 to determine current position w/o GPS or google location services (LOS 15.01 03/24, latest modem/firmware).
After a few minutes (or cell changes, idk), the device slows down, finally reboots, and keeps on doing so even after reboot and dalvik/cache cleanup. In the logs, I find hundreds of lines saying
In the logs, there is no explicit hint about the process that is aborted, but if I disable tasker and reboot, I do not observe any effects like the above.03-27 17:26:18.037 28720 28720 F libc : CANNOT LINK EXECUTABLE "crash_dump32": "/system/lib64/libbacktrace.so" is 64-bit instead of 32-bit
03-27 17:26:18.037 28720 28720 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 28720 (crash_dump32), pid 28720 (crash_dump32)
03-27 17:26:18.040 28722 28722 F libc : CANNOT LINK EXECUTABLE "crash_dump32": "/system/lib64/libbacktrace.so" is 64-bit instead of 32-bit
03-27 17:26:18.040 28722 28722 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 28722 (crash_dump32), pid 28722 (crash_dump32)
03-27 17:26:18.044 28724 28724 F libc : CANNOT LINK EXECUTABLE "crash_dump32": "/system/lib64/libbacktrace.so" is 64-bit instead of 32-bit
03-27 17:26:18.044 28724 28724 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 28724 (crash_dump32), pid 28724 (crash_dump32)
...
Google gives only one exact hit on the above log line, but links to a chinese article that is not exacly helpful to me.
@albsat reported in the LOS 15.1 thread:
The exact same tasker configuration worked flawlessly on LG G4, Moto G, and Samsung Galaxy Nexus.Finally someone with the same problem. I am not glad but I have the same issue, but currently I am running the Google experience by @sooti.
Anyone else?
Last edited: