Comment #280 on issue 439818 by
johnj...@gmail.com: Samsung 303: frequent
Frustration is increasing again. The activity on this forum gives the
impression progress is stalling. I can now recite this #wifi40 issue id
number ("439818") as easily as my childhood phone number. I purchased four
Samsung 303's six months ago so that I could demonstrate how simple Web
Store Apps could be developed on off-the-shelf ARM Chromebooks. I planned
to launch before Google I/O 2015. That's two weeks away now and I still
don't have stable Chromebooks!
Not to theory-craft, but if this issue is triggered by something like a
Stuxnet-style-worm in networking firmware then Chrome OS needs to "set
thine house in order" so the true culprit can be identified. As of now,
Chrome OS simply drops it's connection without explanation.
Example: using usb3-to-ethernet adapter specific unmanaged switches with
specific network usage triggers a connectivity loss and Chrome OS just
shows "cone x" even when wifi is disabled! Users observing this behavior
assume Chrome OS dropped it's connection.
Example: using corrupted firmware on a wireless router with specific
network usage triggers a connectivity loss and Chrome OS stalls, shows full
bars, then no bars, then stops scanning for networks. Users observing this
behavior assume discounted Chromebooks are generally unreliable.
If specific network behavior is triggering the connection loss then Chrome
OS should identify it as a network error. For example: "Access Point blah
violated protocol blah and was disconnected by Chrome OS to protect your
Chromebook from blah."
I've exhausted my spare time testing this. Preliminary tests of Stable
Build 42.0.2311.153 connected to Cisco SF100-24 via Linksys USB3GIG show
good stability. I'm restricting myself to that configuration until someone
on this forum can inspire some hope for change.