You know one thing that’s not right after installing OS 3.0, at least for me? Fifty percent of the time I dock the Neocell into it’s dock at my bed side, system sounds stop playing. Music will play, the alarm will go off, the ringer will work and all app sounds work… but the system sounds, like the keyboard clicks or “new mail” sounds don’t work. They won’t work until a few minutes, or until I go into the system sound settings and turn the ringer volume down, then up.

I’ve searched online and haven’t noticed anyone else having this problem. I wonder if this is something unique for me, or if it has something to do with the custom system sounds I have installed manually installed.

See, I have an iPhone dock next to my bed. It’s got the USB cable hooked up to it, for power, and it’s also got the line out connected to a really nice small stereo sitting next to it. When I set the Neocell down into the dock, it automatically is connected to power and all sound then automatically plays through the stereo. Ring tones, alarms, new mail notifications, music, you name it, it all plays through the speakers sitting under the table. It’s really ******’ tight to be able to hear your phone ring from the kitchen.

Well, from what I assume, because of the Neocell detecting it’s connected to a dock with a lineout connected, when I undock, it must get a little confused and doesn’t realize “Hey, you need to start playing sound from the internal speaker again”… so when I undock, no sounds. The only way’ta fix it is either to wait a few minutes, or, go into the system settings, turn down the ringer, then turn it back up… which then fixes it. This didn’t start until after OS 3.0.

Kinda’ annoying… but because it looks like I’m the only one havin’ this problem, it’s not gonna’ be something that’ll get fixed. That kinda’ sucks. Any of you havin’ this problem?

Peace, J

You guys hear about the text message security hole found in iPhones? If ya haven’t, in a nutshell, one person found a way to send SMS control (text) messages to iPhones that can either make them not respond for a short time, or take limited control of them. Don’t worry… it ain’t all that.

Basically, someone would have to rediscover this hole in iPhones (something unlikely for anyone to do), then know the phone number of someone who has an iPhone… then send them all these text messages… and for what, to bug someone who’s got an iPhone? Man, I ain’t worried about it myself… and not just because i can’t even receive text messages, but the odds of someone discovering this bug again, and then hitting you with it, the odds are about as good as you winnin’ the lottory.

But, there is a fit for it… Apple released a patch, OS 3.0.1, that plugs up the hole. And, here’s the best part… people who are jailbroken, like me (via Redsn0w), are able to upgrade to the OS 3.0.1 and then jailbreak with Redsn0w (using the same Redsn0w files). Basically, you’ll need to reinstall your OS and then rejailbreak.

But I ain’t doin’ it… ya know? I mean, this isn’t something you need to go out and do. I’m waiting on patches that fix things that effect things we actually do or use. You can if you want, but I’m not updating…

Peace, J