June 10, 2015

Brickmuppet disease?

And now my phone will not connect to my wifi hub. Am I suddenly cursed?

My Kindle scared hell out of me last night, because Amazon rolled out an update. It was sitting here, turned off, and suddenly there was a busy-wait graphic on the screen and it stopped paying attention to me.

The Kindle and my tablet can both access the wifi, so that's not the problem. When the phone turns on, it connects to the wifi but fails when trying to get an IP assigned. Very strange.

Not really important, however; I don't use it for anything other than getting AccuWeather updates, and if necessary I can get that across Verizon. (I get a certain amount of digital data per month without extra charge, and this won't even come close to filling that up.)

But still very mysterious. Makes me wonder if Brickmuppet scheduled a trip to Portland or something.

Naah. Must be gremlins.

Posted by: Steven Den Beste in Daily Life at 08:01 AM | Comments (4) | Add Comment
Post contains 158 words, total size 1 kb.

1 Or ducks.

Posted by: Wonderduck at June 10, 2015 11:29 AM (jGQR+)

2 Was that the Kindle update that allows the user to turn off text justification? That was supposed to be "coming soon".

Posted by: Boviate at June 12, 2015 08:28 AM (XRvFv)


I don't have the slightest idea. It just showed up spontaneously and installed without asking my permission, and if there's some place that describes the new features I don't know what that might be.

If such a thing exists it's probably on Amazon's web site.

My Kindle Fire says its system version is "8.5.1_user_5158820", for whatever that's worth.

Posted by: Steven Den Beste at June 12, 2015 10:05 AM (+rSRq)

4 As it happens, I had the identical symptoms this morning.  Several of my machines could connect via wifi to my router, but couldn't connect to the internet (nor could I access the router itself via wifi).  I was able to connect to the router via a wired connection and discovered that the DHCP range had reverted to factory default --  I run my home network on 192.168.2.x -- hence connection, with an unusable IP address (the router retained the .2 address for itself.
I reset the DHCP range and all is now good (but I asked Verizon for a new router).

Posted by: Marshall at June 15, 2015 06:44 PM (GVtWn)

Hide Comments | Add Comment

Enclose all spoilers in spoiler tags:
      [spoiler]your spoiler here[/spoiler]
Spoilers which are not properly tagged will be ruthlessly deleted on sight.
Also, I hate unsolicited suggestions and advice. (Even when you think you're being funny.)

At Chizumatic, we take pride in being incomplete, incorrect, inconsistent, and unfair. We do all of them deliberately.

How to put links in your comment

Comments are disabled.
6kb generated in CPU 0.01, elapsed 0.0215 seconds.
20 queries taking 0.0146 seconds, 21 records returned.
Powered by Minx 1.1.6c-pink.