traccar-test-01
차이
문서의 선택한 두 판 사이의 차이를 보여줍니다.
| 양쪽 이전 판 이전 판 다음 판 | 이전 판 | ||
|
traccar-test-01 [2019/01/30 07:37] chajh |
traccar-test-01 [2021/04/13 06:54] (현재) |
||
|---|---|---|---|
| 줄 47: | 줄 47: | ||
| Low battery example: DBLAB0102' | Low battery example: DBLAB0102' | ||
| ^index ^ servertime ^ devicetime ^ | ^index ^ servertime ^ devicetime ^ | ||
| - | ^356| 2019-01-21 14: | + | ^284| 2019-01-21 14: |
| - | ^357 (Gap)|2019-01-21 18: | + | ^285 (Gap)|2019-01-21 18: |
| - | ^358| 2019-01-21 18: | + | ^286| 2019-01-21 18: |
| Traccar client spend the network data and battery, more or less. Old phones usually have smaller battery size than brand-new ones. We have already planned for the battery issue by providing additional battery to participants. Still, we need a tracking system that can save more energy and alert the battery getting low. | Traccar client spend the network data and battery, more or less. Old phones usually have smaller battery size than brand-new ones. We have already planned for the battery issue by providing additional battery to participants. Still, we need a tracking system that can save more energy and alert the battery getting low. | ||
| 줄 56: | 줄 56: | ||
| Energy saving example: DBLAB0102 (#119) \\ | Energy saving example: DBLAB0102 (#119) \\ | ||
| ^index ^ servertime ^ devicetime ^ | ^index ^ servertime ^ devicetime ^ | ||
| - | ^118| 2019-01-21 10: | + | ^46| **2019-01-21 10: |
| - | ^119 (Gap)|2019-01-21 10: | + | ^47 (Gap)|2019-01-21 10: |
| - | ^120| 2019-01-21 10: | + | ^48| 2019-01-21 10: |
| This case occurred twice on DBLAB0102 (iPhone). iOS seems to have got a kind of procedure that halts power-consuming process for a while. It may have a relation to the case 3. We have not founded the case 2 on Android phones yet. | This case occurred twice on DBLAB0102 (iPhone). iOS seems to have got a kind of procedure that halts power-consuming process for a while. It may have a relation to the case 3. We have not founded the case 2 on Android phones yet. | ||
| * Some data could be missed if the participant would have not recognized the battery level. | * Some data could be missed if the participant would have not recognized the battery level. | ||
| ==== Case 3: Process killed/ | ==== Case 3: Process killed/ | ||
| - | **Traccar blocked: DBLAB0102 (#1738)** | + | **Traccar blocked: DBLAB0102 (#1666)** |
| ^index ^ servertime ^ devicetime ^ | ^index ^ servertime ^ devicetime ^ | ||
| - | ^1736 | 2019-01-23 03: | + | ^1664 | 2019-01-23 03: |
| - | ^1737 (Delayed)| **2019-01-24 08: | + | ^1665 (Delayed)| **2019-01-24 08: |
| - | ^1738 (Gap)|2019-01-24 08: | + | ^1666 (Gap)|2019-01-24 08: |
| - | ^1739| 2019-01-24 08: | + | ^1667| 2019-01-24 08: |
| It is critical issue. You can see #1737 data sent after unblocking Traccar. (#1738) The circumstances like this can also be shown Case 4, but the system unblock automatically in that case. We must prevent this case.\\ | It is critical issue. You can see #1737 data sent after unblocking Traccar. (#1738) The circumstances like this can also be shown Case 4, but the system unblock automatically in that case. We must prevent this case.\\ | ||
| 줄 77: | 줄 77: | ||
| ==== Case 4: Sleep mode/idle ==== | ==== Case 4: Sleep mode/idle ==== | ||
| ^index ^ servertime ^ devicetime ^ | ^index ^ servertime ^ devicetime ^ | ||
| - | ^118 (Delayed) | **2019-01-21 10:40:36.633** | **2019-01-21 09:27:28** | 37.555067 | + | ^718 (Delayed) | **2019-01-22 08:57:05.475** |**2019-01-22 03:08:24** | 37.415295 |
| - | ^119 (Gap)|2019-01-21 10:40:36.915 | 2019-01-21 10:40:35 | + | ^719 (Gap)|2019-01-22 08:57:07.915| 2019-01-22 08:24:02 | 37.416994 |
| - | ^120| 2019-01-21 10:41:40.577 | 2019-01-21 10:41:40 | 37.555111 | + | ^720| 2019-01-22 08:57:11.347 | 2019-01-22 08:25:06 | 37.417065| |
| We can see server got two locations #118 and #119 at once because OS blocks sending position #118 so that Traccar client update the local location like #118 but it'd not sent. Unlike Case 3, however, the device resend the data spontaneously in this case. We've spotted a lot of idle mode delays. All of this case, the devices have no movement when they connected known Wi-Fi at home or in the office. Usually, the owner was sleeping or working inside. | We can see server got two locations #118 and #119 at once because OS blocks sending position #118 so that Traccar client update the local location like #118 but it'd not sent. Unlike Case 3, however, the device resend the data spontaneously in this case. We've spotted a lot of idle mode delays. All of this case, the devices have no movement when they connected known Wi-Fi at home or in the office. Usually, the owner was sleeping or working inside. | ||
traccar-test-01.1548833855.txt.gz · 마지막으로 수정됨: 2021/04/13 06:54 (바깥 편집)
