문서의 선택한 두 판 사이의 차이를 보여줍니다.
양쪽 이전 판 이전 판 | 다음 판 양쪽 다음 판 | ||
traccar-test-01 [2019/01/30 05:33] chajh [Future works] |
traccar-test-01 [2019/01/30 07:37] chajh |
||
---|---|---|---|
줄 1: | 줄 1: | ||
- | ===== Traccar Client on Old Smartphones | + | < |
{{: | {{: | ||
줄 5: | 줄 5: | ||
[[traccar-test-01-kr|한국어 문서/ | [[traccar-test-01-kr|한국어 문서/ | ||
- | ==== Intro ==== | + | ===== Intro ===== |
We have been studying differences of daily activity between disable people and non-disable. So, we had to gather people' | We have been studying differences of daily activity between disable people and non-disable. So, we had to gather people' | ||
Anyway, we adopted Traccar as our GPS tracking platform base, and we'd already tried several experiments. It worked well, but we got a bad news recently. \\ | Anyway, we adopted Traccar as our GPS tracking platform base, and we'd already tried several experiments. It worked well, but we got a bad news recently. \\ | ||
- | ==== What's the problem? ==== | + | ===== What's the problem? |
GPS is only available outdoors.((In fact, today' | GPS is only available outdoors.((In fact, today' | ||
줄 18: | 줄 18: | ||
Besides, it is sufficient so that we can get the places our participant visits, although we don't catch actual location where they are in each place. | Besides, it is sufficient so that we can get the places our participant visits, although we don't catch actual location where they are in each place. | ||
- | ==== There is a gap! ==== | + | ===== There is a gap! ===== |
{{:: | {{:: | ||
줄 27: | 줄 27: | ||
We must look into which was right. | We must look into which was right. | ||
- | ==== Test ==== | + | ===== Test ===== |
Unfortunately, | Unfortunately, | ||
줄 38: | 줄 38: | ||
To get more information, | To get more information, | ||
- | ==== Result and Analysis ==== | + | ===== Result and Analysis |
We configured the client to send its location every 60 seconds. Theoretically, | We configured the client to send its location every 60 seconds. Theoretically, | ||
^ ^ < 2 min ^ 5 ^ 30 ^ 60 ^ 120 ^ 180 ^ 360 ^ > 360 ^ total ^ % of < 2 min ^ | ^ ^ < 2 min ^ 5 ^ 30 ^ 60 ^ 120 ^ 180 ^ 360 ^ > 360 ^ total ^ % of < 2 min ^ | ||
줄 44: | 줄 44: | ||
^DBLAB0103| 8852 | 144 | | ^DBLAB0103| 8852 | 144 | | ||
Although the iPhone(0102)' | Although the iPhone(0102)' | ||
- | === Case 1: Low battery and shutting down === | + | ==== Case 1: Low battery and shutting down ==== |
Low battery example: DBLAB0102' | Low battery example: DBLAB0102' | ||
^index ^ servertime ^ devicetime ^ | ^index ^ servertime ^ devicetime ^ | ||
줄 53: | 줄 53: | ||
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. | ||
* 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 2: Low battery and energy saving mode === | + | ==== Case 2: Low battery and energy saving mode ==== |
Energy saving example: DBLAB0102 (#119) \\ | Energy saving example: DBLAB0102 (#119) \\ | ||
^index ^ servertime ^ devicetime ^ | ^index ^ servertime ^ devicetime ^ | ||
줄 62: | 줄 62: | ||
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 (#1738)** | ||
^index ^ servertime ^ devicetime ^ | ^index ^ servertime ^ devicetime ^ | ||
줄 75: | 줄 75: | ||
* iPhone: Some data could be missed if the participant would have clicked pop-up unconsciously. | * iPhone: Some data could be missed if the participant would have clicked pop-up unconsciously. | ||
* Android (Samsung): Some data could be missed if the participant would have turned off energy saving options in advance. | * Android (Samsung): Some data could be missed if the participant would have turned off energy saving options in advance. | ||
- | === Case 4: Sleep mode/idle === | + | ==== Case 4: Sleep mode/ |
^index ^ servertime ^ devicetime ^ | ^index ^ servertime ^ devicetime ^ | ||
^118 (Delayed) | **2019-01-21 10: | ^118 (Delayed) | **2019-01-21 10: | ||
줄 85: | 줄 85: | ||
* If the user didn't go outside for a long time, we could be misunderstood this case as Case 3. | * If the user didn't go outside for a long time, we could be misunderstood this case as Case 3. | ||
- | ==== Summary ==== | + | ===== Summary |
* Most gaps caused by sleep/idle mode of the operating system. There is no data loss unless the user forgot carrying his phone. | * Most gaps caused by sleep/idle mode of the operating system. There is no data loss unless the user forgot carrying his phone. | ||
* The user must experience the device blocks Traccar because of its power consumption. It is usually three days after. We need to make sure the participant' | * The user must experience the device blocks Traccar because of its power consumption. It is usually three days after. We need to make sure the participant' | ||
* Battery issue is not trivial. | * Battery issue is not trivial. | ||
- | ==== Future works ==== | + | ===== Future works ===== |
* This is data about locations. We need to make some visualization tools with Korean maps. Traccar supports google and openstreetmap but they have some deficiencies because of legislations. | * This is data about locations. We need to make some visualization tools with Korean maps. Traccar supports google and openstreetmap but they have some deficiencies because of legislations. | ||
* We also need monitoring system for notifying users to prevent any data loss. | * We also need monitoring system for notifying users to prevent any data loss. | ||
* All participant have to take a pre-test period at least three days. We could assure Traccar working on the device fine. | * All participant have to take a pre-test period at least three days. We could assure Traccar working on the device fine. |