{"action":"created","issue":{"url":"https://api.github.com/repos/fesch/CanZE/issues/17","labels_url":"https://api.github.com/repos/fesch/CanZE/issues/17/labels{/name}","comments_url":"https://api.github.com/repos/fesch/CanZE/issues/17/comments","events_url":"https://api.github.com/repos/fesch/CanZE/issues/17/events","html_url":"https://github.com/fesch/CanZE/issues/17","id":107051641,"number":17,"title":"Dongle sometimes stops responding, usually with a fast blinking or not at all blinking Host LED","user":{"login":"yoh-there","id":4979670,"avatar_url":"https://avatars.githubusercontent.com/u/4979670?v=3","gravatar_id":"","url":"https://api.github.com/users/yoh-there","html_url":"https://github.com/yoh-there","followers_url":"https://api.github.com/users/yoh-there/followers","following_url":"https://api.github.com/users/yoh-there/following{/other_user}","gists_url":"https://api.github.com/users/yoh-there/gists{/gist_id}","starred_url":"https://api.github.com/users/yoh-there/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yoh-there/subscriptions","organizations_url":"https://api.github.com/users/yoh-there/orgs","repos_url":"https://api.github.com/users/yoh-there/repos","events_url":"https://api.github.com/users/yoh-there/events{/privacy}","received_events_url":"https://api.github.com/users/yoh-there/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/fesch/CanZE/labels/bug","name":"bug","color":"fc2929"},{"url":"https://api.github.com/repos/fesch/CanZE/labels/help%20wanted","name":"help wanted","color":"159818"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":28,"created_at":"2015-09-17T19:03:46Z","updated_at":"2015-10-04T12:45:12Z","closed_at":null,"body":"On my S3, when I run the driving screen, things freeze (BT led not flashing on the dongle for quite a while, at least 10 seconds or more). Could this be a time out? I have a feeling we need to include a time out value defined at al filters as some raw packets flow very fast, others very slow.\r\n\r\nI could do the analysis per frame type if we agree?\r\n\r\nISO-TP sequences should have a time out in the order of 100 ms."},"comment":{"url":"https://api.github.com/repos/fesch/CanZE/issues/comments/145348117","html_url":"https://github.com/fesch/CanZE/issues/17#issuecomment-145348117","issue_url":"https://api.github.com/repos/fesch/CanZE/issues/17","id":145348117,"user":{"login":"fesch","id":1027354,"avatar_url":"https://avatars.githubusercontent.com/u/1027354?v=3","gravatar_id":"","url":"https://api.github.com/users/fesch","html_url":"https://github.com/fesch","followers_url":"https://api.github.com/users/fesch/followers","following_url":"https://api.github.com/users/fesch/following{/other_user}","gists_url":"https://api.github.com/users/fesch/gists{/gist_id}","starred_url":"https://api.github.com/users/fesch/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fesch/subscriptions","organizations_url":"https://api.github.com/users/fesch/orgs","repos_url":"https://api.github.com/users/fesch/repos","events_url":"https://api.github.com/users/fesch/events{/privacy}","received_events_url":"https://api.github.com/users/fesch/received_events","type":"User","site_admin":false},"created_at":"2015-10-04T12:45:12Z","updated_at":"2015-10-04T12:45:12Z","body":"When an activity closes, the following is happening:\r\n- the registered filters are cleared (this happens in the CanzeActivity from which all others inherit)\r\n- the filters of the MainActivity are being registered (to read the speed)\r\n- all listeners are being freed up (this is done by the closing activity itself)\r\n\r\nIf the device reading thread is inside a query at that moment, it will finish it. The worst that could happen is that no listeners will be fired and the answers will not be considered at that right moment. In fact, the BT loop will and should be active as long as CanZE is running. Switching between different activities should not stop it in any way. That's the reason by \"fields\" is synchronized and each access to that field should respect it.\r\n\r\nAnother thing: When I last was hit by the \"dongle stuck\" problem, I did not switch between activities at all. Just started the app, opened a given activity, waited a bit and Bang! hot a hang with strange result. I retried yesterday, but was not able to reproduce it."}}