Hi Anton, thank you so much for your amazing contribution. I am observing Traccar android client with latest PlayStore release version. The service gets crashed on some devices after sometime. I will share the logcats of those devices soon. However as of now my question is regarding the memory allocation which i suspect may be contributing to these crashes. Can you refer the below memory usage screenshots and suggest if you feel anything abnormal? (One image is at 2:24pm just after starting the client and other after 4:46pm, service still running)
https://drive.google.com/open?id=1DkzL-3TxKH01zJCfuamKgwBuPtSSPNDT
https://drive.google.com/open?id=1Di_Hli8aakVVLbAcbS-Wg3tlCC_GyXec
I don't see anything abnormal.
Thanks for reviewing. Honestly, i am unable to find anything in the logs related to client crash. But yes, service stops running and no locations are being reported (I am trying to find a pattern/scenario when it happens). The app is whitelisted (battery optimization disabled) on all the devices under test. Autostart permission granted. Will sanitize the logs and share with you soon. Thanks again for your time.
Hi Anton, thank you so much for your amazing contribution. I am observing Traccar android client with latest PlayStore release version. The service gets crashed on some devices after sometime. I will share the logcats of those devices soon. However as of now my question is regarding the memory allocation which i suspect may be contributing to these crashes. Can you refer the below memory usage screenshots and suggest if you feel anything abnormal? (One image is at 2:24pm just after starting the client and other after 4:46pm, service still running)
https://drive.google.com/open?id=1DkzL-3TxKH01zJCfuamKgwBuPtSSPNDT
https://drive.google.com/open?id=1Di_Hli8aakVVLbAcbS-Wg3tlCC_GyXec