Bug: Changing profile causes reboot
Hi all!
I'm not sure this is the right place for bug reports.
I have a Trail2-bike with OS 4.9.5.
When any activity is running, changing the profile via menu causes the device to reload the OS.
Steps to reproduce the problem:
Start any activity, for example: Menu/Start/Free activity
Change che profile: Menu/Settings/Activity profiles//Profile/<anything>
It displays the hourglass icon and reloads the OS.
Note: it happens when I change the profile through the menu. If I tap on the status bar and I change the profile it does not reboot.
-
Hello,
Make a statuts report and read this report with a text editor (Notepad), to Know the reboot origine.
Before the reboot, you must see either a key notification or an automatic screen light adjust.
The number of lines with the command automatic screen light adjust, is very important!.If you turn the comutation of automatic screen light adjust to OFF state, the cases of automatics reboots will be decreases
This is a recomandation from an others user, with zero reboot since start of june, the date where this users had turn to off the automatic light computation.
-
I made a status report right after the reboot.
The only this I see before the reboot is the hourglass icon. I also disabled the automatic backlight setting and it made no difference.
There are many files in the zipped status report. "compegps.log" has some infos that may be useful. This bug is very easy to reproduce. I forgot to say that I'm using two maps: Italy_HighResolution.CDEM and Italy_OSM_21q2.vmap (the former was not used to display the map).
2021-07-12 11:26:12 [pid:377, thid:1950793728, thspid:377] Triplog Started
2021-07-12 11:26:12 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:6144 begin
2021-07-12 11:26:12 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:6144 end
2021-07-12 11:26:12 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:290 end
2021-07-12 11:26:12 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:6600 begin
2021-07-12 11:26:12 [pid:377, thid:1858073392, thspid:422] NewEvent to be tracked. key: "StartNavigating"
2021-07-12 11:26:12 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:6600 end
2021-07-12 11:26:12 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:2512 begin
2021-07-12 11:26:12 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:6600 begin
2021-07-12 11:26:12 [pid:377, thid:1858073392, thspid:422] NewEvent to be tracked. key: "ViewTools"
2021-07-12 11:26:12 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:6600 end
2021-07-12 11:26:12 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:2512 end
[pid:377, thid:1950793728, thspid:377] mapa ** avoid reload
[pid:377, thid:1950793728, thspid:377] mapa ** avoid reload
2021-07-12 11:26:22 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:887 begin
2021-07-12 11:26:22 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:887 end
2021-07-12 11:26:25 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:3400 begin
2021-07-12 11:26:25 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:3400 end
2021-07-12 11:26:27 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:3410 begin
2021-07-12 11:26:27 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:3406 begin
2021-07-12 11:26:27 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:3406 end
2021-07-12 11:26:27 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:6149 begin
2021-07-12 11:26:27 [pid:377, thid:1950793728, thspid:377] Engine Ejecuta_Comanda:6149 end
2021-07-12 11:26:27 [pid:377, thid:1950793728, thspid:377] TThreadITV created with id: 1821373232 "TTareaProcesosLentos"
2021-07-12 11:26:27 [pid:377, thid:1821373232, thspid:551] TThreadITV started execution of "TTareaProcesosLentos".
2021-07-12 11:26:27 [pid:377, thid:1821373232, thspid:551] TThreadITV ended execution of "TTareaProcesosLentos". Stack trace (most recent call last) in thread 377:
#2 Object "/lib/arm-linux-gnueabihf/libc-2.19.so", at 0x764b0aff, in
#1 Source "/home/jenkins-user/CompeGPS/Desarollo/Lib/Linux/backward/commit_c25d2e/backward.hpp", line 2255, in sig_handler [0xce76b]
#0 | Source "/home/jenkins-user/CompeGPS/Desarollo/Lib/Linux/backward/commit_c25d2e/backward.hpp", line 2233, in load_from
Source "/home/jenkins-user/CompeGPS/Desarollo/Lib/Linux/backward/commit_c25d2e/backward.hpp", line 711, in handleSignal [0xce637]
Segmentation fault (Address not mapped to object [0x206f6c6e])
Segmentation fault (core dumped)
----------------------------------------
twonav-loader: callToSystem finished. Command: "CompeTwoNav"
Child exited normally with status:139
System call "CompeTwoNav" segmentation fault
********* StartTwoNav
2021-07-12 11:26:42 [pid:562, thid:1951080448, thspid:562] ****************************************************************
2021-07-12 11:26:42 Start
2021-07-12 11:26:42 [pid:562, thid:1951080448, thspid:562] **** _Version__4.9.5 (BUILD 202104061603) **** -
The staus report is here: https://we.tl/t-pKbIEGZALZ
I hope it is useful to fix the bug.
-
Good evening,
Here it is a forum of users "like you", to contact the after-sales service you must use the send a request link at the top of this page. The response is made within 48 hours, you fill out the form and you must attach the status report.
A priori, it seems that you have a corrupt file in your GPS.
cordially
-
Nope, it's not a corrupted file. I also reproduced the bug with no files at all (I moved all files in a subdir and the Trail2 started clean without maps o anything loaded).
I'll contact the support as you suggested.
Out of curiosity, are you part of Twonav in some way? You wrote a lot of messages in this forum.
-
Good evening
When I say corrupted files, I mean files that are used by the TwoNav app to operate, not your data files.
TwoNav reboot because the program to run will point in memory, to look for its instructions, where the code is corrupted. (At each restart the error returns to the same address, and as it is always on the same action it is the same segment of code).
When you have the info on the return after repair, ask them about the cause.
CDLT
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
7 Kommentare