MobileRead Forums - View Single Post

ploum · 03-01-2014, 05:06 AM

I've ran multiple tests and the probability that it's not Kobo fault is very very very low. Let me explain:

1. The Kobo was working fine circa 2.6/2.8. The bug seems to have been introduced with 2.10 or 3.0. That's a proof that the bug appeared following a Kobo modification.

2. I did some tests with multiple routers, some very exotic but can now reproduce the problem with the main VDSL*router used in Belgium which is built on a completely different platform than cheap Wifi router. That's not a proof by itself but already a strong hint.

3. No action on the router can solve the problem. I tried :*rebooting the router, setting a longer/shorter lease time, removing all existing connections. It doesn't change anything. Even assigning a fix IP to the MAC*address of the Kobo doesn't solve the problem. If there was anything wrong with the router, rebooting it would likely fix the connection.

4. On the other hand, rebooting the Kobo works everytime. This is a definitive proof that what is preventing to connect is "inside" the Kobo and that a simple fix could be done on the Kobo side.

5. I've also successfully did the following :*reboot the Kobo -> Connect on faulty router -> Disconnect -> Try to reconnect (without success) -> Connect to a completely different router (it works) -> Retry with the faulty router : It works ! Once again, that's a strong hint that something is not cleared properly on the Kobo side.

6. It should be mentionned that, randomly, the Kobo will connect any way! It's very rare but, sometimes, I'm able to connect 2/3 times before it refuses to connect any more. In January, I even spent 3 days away with my Kobo and when I went back home, the Kobo connected without any problem for 3 weeks! Without rebooting, it suddenly started to work. After 3 weeks, I*rebooted the Kobo for whatever reason and, since then, the bug reappeared. This is the proof that, when it wants, the Kobo actually can connect. Nothing prevents it to connect from the router side.

7. The issue is very similar to one that plagued Android Nexus devices end 2012/early 2013. Nexus devices would be unable to reconnect to some routers when waking up. You had to disable/reenable wifi in order to be able to reconnect. I had this issue with some Nexus devices and some routers. From my small samples, the routers affected are the same. It should be mentionned that Google fixed this issue in Android itself. Unfortunatly, I cannot find the fix anymore.

With all of those hints/tests, I just can't find any explanation where the router would be faulty. But I can find many way of explaining the bug with a buggy IP stack on the Kobo or any bug. In facts, the bug might not be related at all to the kind of AP you have but the channel or the number of Wifi you've used with your Kobo or anything.

03-01-2014, 05:06 AM	#39
ploum Zealot Posts: 147 Karma: 22818 Join Date: Apr 2013 Device: Pocketbook Touch HD 3 + koreader	I've ran multiple tests and the probability that it's not Kobo fault is very very very low. Let me explain: 1. The Kobo was working fine circa 2.6/2.8. The bug seems to have been introduced with 2.10 or 3.0. That's a proof that the bug appeared following a Kobo modification. 2. I did some tests with multiple routers, some very exotic but can now reproduce the problem with the main VDSLrouter used in Belgium which is built on a completely different platform than cheap Wifi router. That's not a proof by itself but already a strong hint. 3. No action on the router can solve the problem. I tried :rebooting the router, setting a longer/shorter lease time, removing all existing connections. It doesn't change anything. Even assigning a fix IP to the MACaddress of the Kobo doesn't solve the problem. If there was anything wrong with the router, rebooting it would likely fix the connection. 4. On the other hand, rebooting the Kobo works everytime. This is a definitive proof that what is preventing to connect is "inside" the Kobo and that a simple fix could be done on the Kobo side. 5. I've also successfully did the following :reboot the Kobo -> Connect on faulty router -> Disconnect -> Try to reconnect (without success) -> Connect to a completely different router (it works) -> Retry with the faulty router : It works ! Once again, that's a strong hint that something is not cleared properly on the Kobo side. 6. It should be mentionned that, randomly, the Kobo will connect any way! It's very rare but, sometimes, I'm able to connect 2/3 times before it refuses to connect any more. In January, I even spent 3 days away with my Kobo and when I went back home, the Kobo connected without any problem for 3 weeks! Without rebooting, it suddenly started to work. After 3 weeks, I*rebooted the Kobo for whatever reason and, since then, the bug reappeared. This is the proof that, when it wants, the Kobo actually can connect. Nothing prevents it to connect from the router side. 7. The issue is very similar to one that plagued Android Nexus devices end 2012/early 2013. Nexus devices would be unable to reconnect to some routers when waking up. You had to disable/reenable wifi in order to be able to reconnect. I had this issue with some Nexus devices and some routers. From my small samples, the routers affected are the same. It should be mentionned that Google fixed this issue in Android itself. Unfortunatly, I cannot find the fix anymore. With all of those hints/tests, I just can't find any explanation where the router would be faulty. But I can find many way of explaining the bug with a buggy IP stack on the Kobo or any bug. In facts, the bug might not be related at all to the kind of AP you have but the channel or the number of Wifi you've used with your Kobo or anything.