{"action":"created","issue":{"url":"https://api.github.com/repos/openstf/stf/issues/366","repository_url":"https://api.github.com/repos/openstf/stf","labels_url":"https://api.github.com/repos/openstf/stf/issues/366/labels{/name}","comments_url":"https://api.github.com/repos/openstf/stf/issues/366/comments","events_url":"https://api.github.com/repos/openstf/stf/issues/366/events","html_url":"https://github.com/openstf/stf/issues/366","id":164906652,"number":366,"title":"Galaxy J1 Mini SM-J105H does not work","user":{"login":"sorccu","id":32509,"avatar_url":"https://avatars.githubusercontent.com/u/32509?v=3","gravatar_id":"","url":"https://api.github.com/users/sorccu","html_url":"https://github.com/sorccu","followers_url":"https://api.github.com/users/sorccu/followers","following_url":"https://api.github.com/users/sorccu/following{/other_user}","gists_url":"https://api.github.com/users/sorccu/gists{/gist_id}","starred_url":"https://api.github.com/users/sorccu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sorccu/subscriptions","organizations_url":"https://api.github.com/users/sorccu/orgs","repos_url":"https://api.github.com/users/sorccu/repos","events_url":"https://api.github.com/users/sorccu/events{/privacy}","received_events_url":"https://api.github.com/users/sorccu/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/openstf/stf/labels/device%20specific","name":"device specific","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-07-11T18:46:43Z","updated_at":"2016-07-24T06:08:20Z","closed_at":null,"body":"<!---\r\n\r\nIF YOU REMOVE THIS TEMPLATE WE WILL CLOSE YOUR ISSUE WITHOUT RESPONSE.\r\nJust read it. See the commonly asked questions and fill in the details we're asking, it saves so much of our time.\r\n\r\nHi there!\r\n\r\nPlease be sure to run `stf doctor` before submitting an issue. Please include screenshots, command output and log files if any.\r\n\r\n=== SUPER COMMON QUESTIONS ===\r\n\r\nQ. I'm having issues when multiple devices are connected.\r\nA. Usually caused by insufficient USB power supply or other hardware issue we can't do anything about.\r\n\r\nQ. Can I connect a device to STF over WIFI?\r\nA. Yes, with the `--allow-remote` option. However, ADB over WIFI can easily be 10x slower than USB, so don't expect too much.\r\n\r\nQ. How do I connect to my local STF from another computer?\r\nA. Try the `--public-ip` option or do a full deployment. See DEPLOYMENT.md in the doc folder.\r\n\r\nQ. Can I run STF on multiple machines?\r\nA. Yes, if you do a full deployment. See DEPLOYMENT.md in the doc folder.\r\n-->\r\n\r\n## What's the problem (or question)?\r\n<!--- If describing a bug, tell us what happens instead of the expected behavior -->\r\n<!--- If suggesting a change/improvement, explain the difference from current behavior -->\r\n\r\nGalaxy J1 Mini SM-J105H reportedly does not work due to a minicap failure, as can be seen in the logs below.\r\n\r\n```\r\nINF/device:plugins:screen:stream 36181 [xxxxxxxxxxxxxxxx] Reading minicap banner\r\nINF/device:plugins:screen:stream 36181 [xxxxxxxxxxxxxxxx] minicap says: \"INFO: (jni/minicap/minicap.cpp:444) New client connection\"\r\nWRN/device:plugins:screen:stream 36181 [xxxxxxxxxxxxxxxx] Connection to minicap ended unexpectedly\r\nINF/device:plugins:screen:stream 36181 [xxxxxxxxxxxxxxxx] Disconnecting from minicap service\r\nFTL/device:plugins:screen:stream 36181 [xxxxxxxxxxxxxxxx] Frame producer had an error Error: Failed more than 3 times in 10000ms\r\n    at FrameProducer._failLimitExceeded (/usr/local/lib/node_modules/stf/lib/units/device/plugins/screen/stream.js:220:26)\r\n    at FailCounter.emit (/usr/local/lib/node_modules/stf/node_modules/eventemitter3/index.js:73:35)\r\n    at FailCounter.inc (/usr/local/lib/node_modules/stf/lib/util/failcounter.js:29:10)\r\n    at FrameProducer._socketEnded (/usr/local/lib/node_modules/stf/lib/units/device/plugins/screen/stream.js:207:24)\r\n    at RiskyStream.emit (/usr/local/lib/node_modules/stf/node_modules/eventemitter3/index.js:71:35)\r\n    at RiskyStream.<anonymous> (/usr/local/lib/node_modules/stf/lib/util/riskystream.js:14:12)\r\n    at emitNone (events.js:91:20)\r\n    at Socket.emit (events.js:185:7)\r\n    at endReadableNT (_stream_readable.js:926:12)\r\n    at _combinedTickCallback (internal/process/next_tick.js:74:11)\r\n    at process._tickCallback (internal/process/next_tick.js:98:9)\r\nFTL/util:lifecycle 36181 [xxxxxxxxxxxxxxxx] Shutting down due to fatal error\r\nINF/provider 36173 [*] Cleaning up device worker \"xxxxxxxxxxxxxxxx\"\r\nERR/provider 36173 [*] Device worker \"xxxxxxxxxxxxxxxx\" died with code 1\r\nINF/provider 36173 [*] Restarting device worker \"xxxxxxxxxxxxxxxx\"\r\n```\r\n\r\n## What should have happened?\r\n<!--- If you're describing a bug, tell us what should happen -->\r\n<!--- If you're suggesting a change/improvement, tell us how it should work -->\r\n\r\nIt should have been operable like any other device.\r\n\r\n## Do you have an idea for a solution?\r\n<!--- Not obligatory, but suggest a fix/reason for the bug, -->\r\n<!--- or ideas how to implement the addition or change -->\r\n\r\nNeed to search for a fix or workaround in minicap.\r\n\r\n## How can we reproduce the issue?\r\n<!--- Provide unambiguous set of steps to reproduce this bug. Include code to reproduce, if relevant -->\r\n\r\n- [x] 1. Buy a Galaxy J1 Mini SM-J105H \r\n- [ ] 2. Connect it to STF\r\n\r\n## Help us understand your issue by providing context.\r\n<!--- How has this issue affected you? What are you trying to accomplish? -->\r\n<!--- Providing context helps us come up with a solution that is most useful in the real world -->\r\n\r\n## Please tell us details about your environment.\r\n<!--- Include as many relevant details about the environment you experienced the bug in -->\r\n\r\nKnown to be irrelevant in this particular case.\r\n"},"comment":{"url":"https://api.github.com/repos/openstf/stf/issues/comments/234759976","html_url":"https://github.com/openstf/stf/issues/366#issuecomment-234759976","issue_url":"https://api.github.com/repos/openstf/stf/issues/366","id":234759976,"user":{"login":"sorccu","id":32509,"avatar_url":"https://avatars.githubusercontent.com/u/32509?v=3","gravatar_id":"","url":"https://api.github.com/users/sorccu","html_url":"https://github.com/sorccu","followers_url":"https://api.github.com/users/sorccu/followers","following_url":"https://api.github.com/users/sorccu/following{/other_user}","gists_url":"https://api.github.com/users/sorccu/gists{/gist_id}","starred_url":"https://api.github.com/users/sorccu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sorccu/subscriptions","organizations_url":"https://api.github.com/users/sorccu/orgs","repos_url":"https://api.github.com/users/sorccu/repos","events_url":"https://api.github.com/users/sorccu/events{/privacy}","received_events_url":"https://api.github.com/users/sorccu/received_events","type":"User","site_admin":false},"created_at":"2016-07-24T06:08:20Z","updated_at":"2016-07-24T06:08:20Z","body":"Device arrived... it may have been stolen. The seal had been broken and the device is locked, asking for the previous owner's Google account. Very unexpected considering the eBay seller had nearly 7000 feedback with 99.2% positive rating.\r\n\r\nInitiating claim process."}}
{"actor":{"display_login":"sorccu"}}