3 ms·
And now how about a "dirty secret" for Kineto Wireless mentioned in the article several times. When their code is running on an Android device, even when wifi
by rogerbinns 15y ago
And now how about a "dirty secret" for Kineto Wireless mentioned in the article several times. When their code is running on an Android device, even when wifi calling is disabled, it spews an endless stream of messages to Android's log (aka logcat). Often several messages every two seconds. Almost all at Error level even though it just appears to be signal strength information. This is ridiculously amateurish. It is highly annoying as a developer to have to keep filtering this crap out. It also implies they don't bother to check what is happening with their own code.
I have emailed their support who didn't respond. I even wrote a Google Plus post about it:
https://plus.google.com/110166527124367568225/posts/h4jK38n4XYR
I often find their code gets wedged too. It gets into a state where it isn't working, but you can't enable or disable it. The only recourse is to reboot your phone.