by Peter Ridge

A lot of people are having problems connecting the Sony BDP-BX57 and BDP-S570 Blu-ray disc players to the Internet via Wi-Fi with encryption enabled (WEP, WPA, WPA2, etc.). I ran into this as well, but eventually got it working with a pretty easy fix. So, don’t return yours to Costco or BestBuy just yet.

To make sure your connection problem isn’t a configuration error, be sure that your SSID in the player’s wireless network configuration matches the one in your wireless router (properly entered upper- and lowercase letters, if any). It’s a good idea to turn off all wireless encryption to verify that the Blu-ray player connects via Wi-Fi without it and that video or music streams properly over the network.

Finally, verify that your Blu-ray player’s firmware is up to date. Some earlier network problems were the result of firmware bugs and you want to make sure that you’re not suffering from one of those problems. The current version, at the time of this post, is M04.R.735. To find the firmware version in your disc player, do the following:

1. From the player’s main menu, scroll all the way to the left to Setup.
2. Select System Settings, then System Information at the bottom.
3. The firmware version appears near the top of the screen.

If your firmware is older than M04.R.735, update it before continuing on. I’ll wait right here.

All set to continue? Good. If you updated the firmware, double check that unencrypted wireless is still working. Now, re-enable encryption in the wireless router, set the corresponding encryption mode in the player (WEP, WPA, WPA2, etc.) and enter the correct encryption key. At this point, if you’re encountering the problem, having enabled encryption will result in a good wireless connection, but no Internet access. The player’s green Wi-Fi LED on the front of the device will be on, but the IP address will start with 169 instead of the usual 172 or 192.

It seems that firmware changes can introduce problems with the network configuration information or other related data in the system. As a result, encryption over the wireless doesn’t work properly. To fix this, do the following:

1. In the player’s menu, scroll all the way to the left to Setup.
2. Scroll to the bottom and select Resetting.
3. Select Reset to Factory Default Settings. Don’t worry, it won’t reset just yet.
4. Select Network Settings to wipe out all the network configuration data.
5. Re-enter the wireless network settings that you did before. (I know, it’s a pain.)

That’s it. It should connect to the wireless and to the Internet now. Wiping the old network data and re-entering it removes whatever was causing the wireless not to properly encrypt the network communication. If, for some reason, resetting just the Network Settings isn’t enough, you can opt to reset everything. It’s the last reset item in the menu.

Did it work for you? Do you have a different model Sony Blu-ray player or even a different brand with a similar problem and found a fix? Post your experiences in the comments.

Post a comment

Related posts:

• Linksys Router Doesn’t Connect to Ambit uBee U10C018 Cable Modem

by Peter Ridge

Do you have a Samsung Epic 4G or other Android phone? Do you have to recharge your battery daily or more than once a day even when you’re hardly doing anything with it? That’s not normal. My Samsung Epic, when lightly used, only needs to be recharged every three to four days.

“Impossible!” you say. “These are powerful phones and they use up the battery faster.” That may be true if you’re talking on the phone, watching videos and playing Angry Birds on it all day long. However, many people are having to frequently recharge their phones even under light to no usage, which should not be happening.

“You must use task killers, Juice Defender, a special kernel or some extreme tools to get that kind of battery life.” Actually, I’ve tried some, but abandoned such measures. They’re not necessary. There are many well-known ways to conserve power such as turning off services you don’t need, checking for mail less often, dimming the screen, etc. These are certainly important and should be practiced. But, there’s more.

Despite these normal power conservation techniques, when the Samsung Epic starts to drain the battery, it does so at an alarming rate. Here’s a log of the battery level at approximately ten-minute intervals that I kept when mine recently started to suck the battery dry:

62% @ 11:37 pm
61% @ 11:45 pm
59% @ 11:58 pm
57% @ 12:10 pm
56% @ 12:17 pm
55% @ 12:27 pm
52% @ 12:37 pm
51% @ 12:47 pm
50% @ 12:57 pm
49% @ 1:07 am
48% @ 1:10 am
47% @ 1:20 am
45% @ 1:36 am
44% @ 1:50 am
43% @ 2:05 am

It’s draining the battery at a rate of about 10% per hour. This is with the phone’s screen, GPS, 3G/4G data, Wi-Fi, automatic updates, Bluetooth and sound turned off. No applications were running. In fact, during this period, I had more things turned off than I usually do.

It’s been documented at the Sprint Community forum and various blogs that the Samsung Epic can go into a mode where it will continuously search for the cellular network. I have encountered this and the usual fix is to turn on airplane mode for a few seconds and then turn it off again to reset the radio. Unfortunately, I found that this fix doesn’t always work. Even shutting down the phone completely and then turning airplane mode on and off doesn’t help.

In the two cases thus far, when the simple fix for this problem didn’t work, two things did. The first was turning on airplane mode overnight. The second was turning the phone completely off overnight. Here’s a short log of battery life after the overnight fix for the sudden battery consumption I logged above:

41% @ 8:33 am
41% @ 8:44 am
41% @ 8:49 am
41% @ 9:00 am
40% @ 9:01 am
40% @ 9:10 am
40% @ 9:20 am
40% @ 9:33 am
39% @ 9:41 am

As you can see, now the phone is only consuming 1-2% per hour, rather than 1% every 10 minutes. The screen was off, but 3D data was enabled and some services that I turned off during the excessive battery usage were running again since the phone had freshly booted. So, despite having more things turned on, the phone is back to normal and will last significantly longer than the 8-10 hours that many owners of the Samsung Epic are reporting online as “normal”.

Does this fix really require turning the phone off (or putting it into airplane mode) all night? At this time, I’m not sure how long it needs to stay in the off/airplane state. It definitely needs more than a few minutes, because I’ve tried that and it’s not enough. So, it’s somewhere between a few minutes and 6.5 hours.

Have you tried this fix? How long did you have to keep your phone off or in airplane mode to get it to behave? Post your experience in the comments.

Post a comment

by Peter Ridge

I recently ran into a situation where a Linksys WRT-54G wasn’t able to get an IP address when connected to an Ambit/uBee U10C018 cable modem. This issue may also apply to other routers when used with the U10C018 cable modem.

When a PC is connected directly to the modem, everything works fine and the Internet can be reached normally. When a router is placed inbetween, then there is no longer any access to the Internet. Viewing the status information in the router shows that it is unable to acquire an IP address, even though the router is set to use automatic configuration via DHCP, the same as the PC.

Apparently, the U10C018 cable modem is aware of the MAC address of various routers. In order to get the router to work with the modem, use the MAC cloning feature of the router. The location of this option will depend on your particular router brand and model. When you find it, turn it on. Then, set the desired MAC address.

On the Linksys router, the MAC address cloning page has a button to copy the MAC from the PC that’s currently connected to the administration interface. If your router has this feature, use it to set the router to the same MAC address as your computer. If your router does not have this feature, then you’ll have to get your MAC from the network driver or the network card.

Once you have a non-router MAC entered into the MAC cloning setting, save and restart the router.

Have you run into this issue? If so, post your router model and steps to configure MAC cloning for it in the comments.

Post a comment

by Peter Ridge

Many reviews of the Samsung Epic 4G (SPH-D700) Android phone fault it for the backlighting of the four shortcut buttons at the bottom of the phone. When the keyboard backlight times out (six seconds, by default), those touch-sensitive shortcut buttons are no longer visible at all. The area becomes completely black. As a result, you either have to memorize which location is Menu, Home, Back and Search, or increase the backlight’s timeout, which uses more battery power.

Well, there’s actually another solution. When the shortcut keys are not visible, simply press the camera shutter button, located at the bottom-right of the phone when held in portrait orientation. Et voila! The keyboard backlight turns on. Since the camera button is raised, it’s easy to find, even in the dark.

Have any other tips for the Epic 4G? Share them in the comments.

Post a comment

by Peter Ridge

After installing Ubuntu 9.04 Jaunty and enabling the nVidia 180 driver (onboard video is a nVidia GeForce 6150 LE), I restarted the system and was greeted by the normal login screen. However, after logging in, my screen (Dell 2407WFPHC) went blank with a monitor message that the resolution was out of range. It appears that many people are running into this problem. The following fixed it for me.

1. Open a terminal window
2. Go to the X11 directory (cd /etc/X11)
3. Make a backup of the current xorg.conf file (e.g., sudo cp xorg.conf xorg.conf.backup)
4. Use your favorite editor to open xorg.conf (e.g., sudo vim xorg.conf)
5. In the section “Device”, add the following line:
       Option “UseEdid” “False”
6. The “Device” section should now look like the following:
       Section “Device”
           Identifier “Default Device”
           Driver “nvidia”
           Option “UseEdid” “False”
       EndSection
7. Save the xorg.conf file
8. Log off and restart the X server (from the login screen, click on Menu and select Restart X server)

That’s it. Now, when I log in, I’m able to see the screen and select a resolution using the nVidia X Server Settings tool.

Note: In the nVidia X Server Settings tool, if when you click the Save to X Configuration File button, you get an error message that it can’t save, run nvidia-settings from a terminal window using gksudo (for Gnome, e.g., gksudo nvidia-settings) or kdesudo (for KDE, e.g., kdesudo nvidia-settings). If, instead, you get a “can’t parse xorg.conf”, just rename /etc/X11/xorg.conf to something else so nvidia-settings can create a new file.

Can’t set your screen to the native resolution of your monitor? See the companion post, Ubuntu 9.04 nVidia Driver Screen Resolution Problem.

Post a comment