FaceTime is one of the major new iPhone 4 features that set the smartphone apart from others, but we’ve been hearing that quite a few people are unable to place a FaceTime call from their iPhone 4, despite both parties being connected to Wi-Fi, which is the only requirement. In fact, we had the same issue when we tried to fire up our first FaceTime chat while at the Apple Store during iPhone 4 launch. I immediately walked over the to Genius Bar, figuring that my iPhone 4 wasn’t recognizing the fact that it had a front-camera or something, and the Genius was stumped, too. He was also in charge of handing out iPhone 4 units, so we didn’t have his full attention anyway. While he was doing his thing, we looked through the Settings area to see if there might be something there. As it turns out, there was.
For whatever reason, not all iPhone 4s are shipping with FaceTime enabled. The person I was with had just bought his iPhone 4, same as I did, and his had FaceTime enabled by default, while mine was disabled by default—both straight out of the box. If you are experiencing the same, first thing you should do is go into Settings, then Phone. Right beneath your phone number will be the FaceTime toggle. Switch it to “ON” and you are good to go.
So, after upgrading my PC from Windows 7 Ultimate 32-bit version to Windows 7 Ultimate 64-bit edition, I quickly determined that using Remote Desktop Connection for Mac 2.0 to connect to the PC resulted in no sound coming through the audio redirection feature. It took a bit of Googling to figure out exactly what was going on, but as it turns out, the x64 editions of Windows Vista, Windows 7, and Windows Server 2008 simply don’t include the audio redirection feature for the Remote Desktop Mac client. You’d think Microsoft would fix this themselves with a patch, but instead, they offer a Hotfix download. If you are unfamiliar with Microsoft Hotfixes, it’s pretty much an annoying process. You head to the kb article to find out about the problem, then request that a link to the hotfix download be emailed to you (because they couldn’t just put a download link on the help page?,) then you download the fix and attempt to open it. You then realize that the email with the download link also includes a password that you need in order to even run the fix.
C’mon, Microsoft, can we improve this asinine process?
At the very least, at the end of the day, the Hotfix worked, and I am again able to remote in to my PC from my Mac to listen to Zune. Good times.
Read More | Hotfix: Audio Redirection in 64-bit Windows for Remote Desktop
If you’re a Nexus One owner, you may be well aware of the 3G issue that the device has, where it won’t connect to (or stay connected to) 3G, constantly falling back to EDGE. We know not all have experienced this oddity, but it’s enough of a problem that we’ve been getting emails about it, asking if there was a fix. Luckily, Kevin Tofel over at jkOnTheRun seems to have figured out a fix, and it’s simple to do:
- Go into Settings
- Select “Wireless & Networks”
- Choose the “Mobile Networks” option near the bottom
- Go into the “Network Operators” section. The Nexus One will do a search for GSM networks around you.
- When the search is complete, tap the “Select Automatically” option. The phone should respond with “Registered on network.”
That should do it! According to Kevin, he hasn’t been able to get 3G access from his home in the 10 days that he’s had the device. After doing the above, he’s been speeding along on 3G non-stop, even after reboots. If you’re experiencing similar issues, give it a try, and let us know how it works for you!
Read More | jkOnTheRun
If you’re anything like me, and I’m making an assumption here (because that’s what irresponsible journalism is all about), you might only have so much money to go towards fancy gadgets and various electronic compensations for a strikingly diminished sense of personal worth. That can lead to some trouble if, for instance, you have a decent gaming headset that you want to use for your Xbox 360 instead of a bona-fide sound sytem, since you can no longer use Xbox Live without Microsoft’s proprietary, flimsy headset.
A few headsets, like those from Turtle Beach, alleviate this problem by offering individual chat volumes and the ability to both listen to your game and communicate with your buddies. It’s a worthy investment, but a bit of a waste if you already have a good gaming headset - dedicated XBL headsets can hover around the $150 range. All you need is a $5 adapter and zero soldering.
Hit the jump to see what you need.
In this episode, we give you a look at a bunch of the new little features that you’ll find in Windows 7. They’re all small things that, we think, will lead to a nice increase in productivity and time-saving. We are talking about things like Aero Peek, Snap, Pin, and the like. None of those terms ring a bell? Then you might wanna hit the play button up there on this episode of Bleeding Edge TV.
We recently reported an issue regarding the Motorola DROID and it’s MMS problem, and it looks like we’ve tracked down the issue.
After some hefty research (read: lots of Googling and failed MMS messages,) we finally stumbled upon a post over on Howard Forums from a user who seemed to identify this issue. We have tested it successfully, both purposefully breaking and then fixing our ability to send MMS.
The culprit: parentheses around your contact’s area code. If your contacts have parentheses around them when they are synced to the phone, the Droid faithfully preserves that. However, when the address is used for an MMS transmission (and ONLY MMS, for some reason), it glitches out and fails. [Ed. note: What an absolutely ridiculous bug!]
Here’s how to fix the DROID MMS issue, if you are experiencing it:
- Delete any open threads containing the user you want to MMS, including any text message threads. Otherwise, it will pull the address form the thread instead of using the new one.
- Edit the contact, removing the phone number and retyping it in. Notice the Droid will type the hyphens in itself, but will not place parentheses. Make sure to do this on EACH form of data this may synchronize from (e.g. Corporate AND Google contacts, if this person is in both. Haven’t figured out if parentheses coming from Facebook can cause a problem.)
- Soft reset the phone.
- Attempt the MMS.
This worked for us. Drop us a comment and let us know if it worked for you. There have been some reports of the problems reoccurring, and so we’d like to know your circumstances.
Personal note: Make sure you edit the information that syncs to your phone so it has no parentheses. I know I exported my contacts from Outlook, and imported them into Google, and Outlook puts parentheses by default, so that is why none of my contacts worked in the first place, but we COULD send to the guy at Verizon Wireless (because we typed in his number directly.) I’m wondering if somehow the parentheses data is somehow being synced back to the phone.
We’ve reported the situation to Verizon’s Wireless Data Technical Support team, who thanked us for the information. (Direct quote: “Awesome.”)
Today, Google “announced” a feature that technically already existed before now, but giving it a name makes it more real, right?
Google says that by taking advantage of the conditional call forwarding feature your carrier provides, you can forward calls that you do not answer on your phone to your Google Voice phone number, thereby replacing your company’s voicemail with Google’s. This functionality has actually always existed: Google Help forums reveal countless people already were setting up their functionality long before Google made this announcement.
It boils down to setting up your call forwarding feature (*71 or the like) to forward to your Google Voice number (or your “Access Number” if you sign up “Without a Google Number”). Then, when your call is forwarded to the Google Voice number, the voice mail is logged and transcribed and stored online, with delivery options such as email or text message to your cell phone. You don’t get all the features you get if you use an actual Google Voice number for people to call, but it is still a nifty service.
A bit more information about Google Voice after the jump.
Read More | The Official Google Blog
Okay, we were all disappointed by AT&T’s decision to delay iPhone MMS to early fall, but that doesn’t stop ambitious folks such as ourselves from finding a way around it. And we have. I can confirm that I was able to get MMS working on my iPhone 3GS with about 3 minutes worth of effort. You wanna do it to? Read on for complete instructions for enabling MMS on iPhone 3.1.
It’s no secret, we are big fans of Microsoft’s Zune - both the service, and the device. I’ve had a Zune Pass since the service launched, and use it daily (my Zune Pass profile.) If you aren’t sure what that is, it’s an unlimited music streaming and download service. You can listen to as much as you want for just $15 a month. In addition, you get to keep any 10 tracks of your choosing each month as well. Yours to keep, forever. Did you know, though, that you can stream any of your downloaded Zune tracks to your iPhone? Yeah, that’s one of the best parts. When you start connecting the dots, you soon realize that you have the potential of having an entire catalogue of music available to you, on your iPhone, regardless of the amount of storage you’ve got.
But, wait…how do you stream Windows Media Audio files to the iPhone, which doesn’t support that format? Furthermore, Zune tracks that aren’t downloaded as part of your 10 free keepers per month are riddled with DRM. Yeah, we hear you. There is no Zune app available for the iPhone itself. What you need is to install a piece of software on your PC, along with downloading an app on your iPhone. Join us, as we open up the musical floodgates.
Check out out HTPC on a Budget series and join us in building a great HTPC for under $1,000.
The challenge presented at the beginning of this process was for us to build a great home theater PC while sticking to a budget of $1,000. We knew we were up for the challenge, and wanted to walk you through that process with us. Here’s what we’ve done, as a refresher:
- Let’s Build a Budget HTPC
- Selecting Our Hardware
- The MSI 7411 Motherboard, and Why It Rocks
- Achieving Great 5.1 or 7.1 Surround Sound
- Driving multimedia content to the HTPC
- The ATI TV Wonder 650
- Laying Out All The Components
So, now that we have reached the end of this process, we need to take a look at how we did, right? Were we able to stick to our budget? Let’s see how we did…