 |
|
|
|
|
|
|
|
|
|
HEY LOOKY HERE!! IT'S AN ACTUAL HUMAN-GENERATED POST FOR A CHANGE!!!!!!!! Shocking, ain't it? To be honest, between work and my other projects ( Otaku no Podcast being chief among those) I just haven't had the time. But, with NaNoWriMo in full swing and all of my friends (and their dogs too) participating in it, I figured that the least I could do would be to kick out a measly blog post or two. Anyway "R" is for Recalcitrant... which describes my 13" MacBook Pro's attitude towards me this evening (well, morning now). (and no, this post's title is not the title of a geek-themed Sue Graftonesque novel I'm planning to write for NaNoWriMo...) So this evening I discovered that the "R" key on my relatively brand new (purchased first week of September of this year) 13" MacBook Pro was sticky. Not horribly so - it still registered keypresses reliably. Only slightly sticky. But REALLY, REALLY annoying. Shortly thereafter I discovered that the "4" key was in a similarly annoying condition. Now I'm pretty sure that the machine didn't arrive in my hands in that condition. (Though I can't be 100% certain of course.) Which means that somewhere down the line I probably did something to it. I suspect certain sticky soda-like beverages which I am particularly fond of were involved. I don't recall spilling anything on the beloved machine (and no, I haven't been in any drunken stupors recently, so alcohol-induced amnesia is not a factor). So I suspect that a small droplet of said soda-like beverage managed to find its way to my keyboard, and fell somewhere around the "R" and "4" keys (which, interestingly enough, are located right next to each other on the keyboard). Obviously no warranty on earth would cover this. (Besides, the nearest Apple Store is 40 minutes away by car, and I don't drive, and Pam couldn't take me anyway, seeing as how she'll be headed in the complete opposite direction tomorrow, and yes there is an Apple Store where she'll be headed, but they don't have any Genius Bar appointments till next week.) And I need my machine in functioning condition. What to do, what to do??? Well, after much hemming and hawing, wailing, and gnashing of teeth, I decided, what the hell, you only live twice, and took matters into my own hands and proceeded to pop the "R" and "4" keys off the keyboard. I'm pretty good with mechanical things (or so I thought anyway), besides, how hard could it be? As it turned out, REALLY FRACKING HARD. Naturally, getting the keys off wasn't that difficult. (Entropy being the natural state of the universe and all that.) Although it was a bit nerve wracking - you have to basically shove some sort of prying tool down underneath the key and basically wiggle it around until you unfasten this little plastic thing that fits into a hole in the metal part of the computer. (At least I have the Apple Support Engineer Certified Plastic Prying and Poking Tool of Doom(tm), unlike the guy in the Youtube video I found, who was using... A SCREWDRIVER. *shudder*) A few disconcerting "snap" sounds later (did I mention that all of these plastic parts are extremely small and most likely extremely fragile?), and the key popped off smartly. I didn't see anything particularly gunky or sticky in there, but I gave all parts of the mechanism a good cleaning with rubbing alcohol anyway, giving it plenty of time to air-dry before attempting to put the thing back together. Which, naturally, didn't quite go as planned. No matter how hard I tried, I couldn't get the bits to fit back together. Despite all of my careful maneuvering of parts, it just wouldn't come back together. Once I came awfully close - the key actually snapped back, but at a really crazy angle, the surface of the key leaning way to the left and one half of the key completely unfastened in the socket. Finally, after much sweating, grunting, cursing, swearing, prayer (at this point I was willing to try anything), and finally Googling, I found this page at Apple's support site. It described the keyboard of the PowerBook G4, but from their description of the mechanism and the pictures they provided, it looked to me as though it were the same (or very similar) mechanism to my MacBook Pro's keyboard. So I followed their directions. After even more grunting and swearing (I'm sure my neighbors really loved me by now), I finally got both keys seated properly. All it took was four hours, about a gallon of sweat, and probably ten years off my life due to stress and vitriol. Did I mention the four hours part? Valuable time from my busy schedule, mind you - this is usually my "relax in bed and watch some anime before going to sleep" time. DAMN YOU YOU FOUL KEYBOARD DEMON FROM HELL!!! *shakes fist in air* At least it's all put back together now, and operates in a decidedly NON-annoying manner, with no hint of a sticky key in sight. (And before you PC using weenies utter a single word, it is a KEYBOARD, a MECHANISM. Has ABSOLUTELY NOTHING to do with the OS or software I run. The same thing could just as easily have happened with a Compaq or Lenovo or Dell or whatever laptop. In fact, if that were the case, the bloody thing probably would have broken off entirely. :P Tags: apple, hardware, keyboard, macbook pro, troubleshooting
Current Location: home
Current Mood:  irritated
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
One of the often-touted 300 new features in the new Mac OS X 10.5 "Leopard" is "Back to my Mac." This is a set of software that allows you to access your Macs at home while at work or on the road... or vice versa. Using it, you could copy files to or from that machine, or even remotely control its desktop, as if you were sitting directly in front of the machine, but across the network. Unfortunately, this feature didn't work well for many people -- myself included. In most cases, third party firewalls or routers (e.g. Linksys, Netgear, etc.) were to blame; however, even when running supposedly 100% compatible equipment, it would still not work for many people. Apple tried to correct these issues in the first software update, 10.5.1; that fixed it for some people but not everybody. Apple made more fixes with the 10.5.2 release, and apparently that fixed it, at least for me. I can now fully use Back to my Mac. Now it may still not work in certain conditions; for example, it probably won't work for me at the office, since they have the Firewall of Doom that pretty much blocks everything. However, it at least works for me on my EVDO modem, which is good enough for me. Anyway, click the link below, and you will see a screen shot of me using my laptop (Navi) to connect to my other Mac (Locutus) back at home, and sharing its desktop across the Internet. http://tinyurl.com/33boguTags: .mac, apple, back to my mac, leopard, mac os x
Current Mood:  jubilant
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Hot on the heels of the first iPhone unlock I reported on earlier, comes another iPhone unlock; this time a much easier one to install. It is fully GUI (graphical) and is literally a "one-click" path to unlocking your iPhone. The iPhone Dev Team has been the driving force behind most of the iPhone work to date. This includes, among other things, cracking the iPhone firmware images, researching how to "jailbreak" the iPhone (get out of its protected mode so you can access the entire iPhone filesystem), bypassing the requirement to activate the iPhone through AT&T, and creating an open SDK and toolchain for building native third-party iPhone applications. Well, now they have completed the "holy grail" of iPhone hackery; unlocking the iPhone. Their "anySIM" iPhone unlocking tool has been released and is available for download here. Perhaps the easiest way of getting this software (as well as tons and tons of other iPhone software) onto your device is by using the free AppTapp installer. This is a fully GUI based installer for your iPhone, similar in concept to the package managers you find on Linux, such as Apt-get/aptitude/etc. Basically you install it on your iPhone (just download the file - it is a standard Mac OS application - and run this application with your iPhone connected to your Mac, but NOT while running iTunes - i.e. close iTunes first). This will add a new "Installer" icon on your iPhone's menu screen; click it, and you will be presented with a long list of software applications that you can easily install on your iPhone. Be sure and install the "Community Sources" package so that you can get access to several other iPhone software repositories. Anyway, once you have the AppTapp installer installed, look for the "anySIM" unlocking application to show up here. It's not up yet, but the developers promise it will be up soon. Install it (when it becomes available), click the icon, and (to quote Steve Jobs) "Boom!" you've got yourself an unlocked iPhone. Tags: apple, iphone, unlock
Current Mood: excited
Current Music: Today in iPhone podcast #35
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
 Today will go down as one of the most significant days in the history of hardware/software hacking. For it is today that the first Free/Open Source iPhone unlock has been released to the world. Of course, there was a company called iPhoneSIMfree that claimed to have an iPhone hack, but they have dragged their feet for over two weeks after they announced their product, leading many to believe that it was vaporware. In fact, they did eventually release their product, but not directly to end users - instead, they are selling their product in bulk to several resellers across the globe, and it is up to us consumers to pick a reseller and buy the unlock from them. Well, for one thing, it is $99, a bit steep for a phone unlock in my books (when I got my ancient T610 unlocked many years ago, I think I only paid $20 or so for it). Also, these are all (including iPhoneSIMfree) pretty unknown companies, and many people (myself included) are questioning their legitimacy and trustworthiness. Finally, of those brave souls who did buy one of their unlocks, there are reports of trouble installing the thing. And if that isn't enough, there is the ever-present threat that Apple might nullify the unlock through a software update. Fortunately, a team of very bright hackers across the world have released their "iUnlock" program, a completely Free/Open Source unlocking solution. And it works beautifully - my iPhone unlocked without hassle, and I am now using it perfectly on T-Mobile. Everything works, except for Visual Voicemail, which requires special code (or equipment) on the cellular carrier end of things. The YouTube application requires a special hack to work properly, but this hack is widely available on the Internet. Everything else -- calling, 3-way, hold, caller ID, call forwarding, GPRS/EDGE data, etc. works just fine. And the fact that this is Open Source means that Apple will be very hard-pressed to block this one. Since the code is "out there" for people to examine and tweak to their content, if Apple tries blocking it in one way, there are sure to be many hackers working on the code to find a different way to unlock the phone, and a new unlock would surely be released soon after Apple's attempt to nullify it. That's the beauty of Open Source right there. Besides, Apple may not even bother with plugging the unlock. Several years ago, the Library of Congress, who sets the rules under which the Digital Millennium Copyright Act (DMCA) was enforceable, made several exceptions to the DMCA; one of these is that it is now legal for you to unlock a cell phone for your own use, as long as you are doing it without profit as a motive. Which means that the people selling iPhone unlocks will probably get busted, but the people making (and using) the Open Source unlock are probably safe. Further indication of Apple's indifference to iPhone hackery comes from this interview with Greg Joswiak, one of Apple's top marketing honchos. In it, he basically states that Apple doesn't really care about iPhone hacks one way or another, and that they aren't planning on specifically coding firmware releases to block hacks. (However, they warn that future software updates may unintentionally break hacks.) http://www.gearlog.com/2007/09/apples_joswiak_we_dont_hate_ip.phpFor more details, and to get the files you need to perform the unlock yourself, check out the following web sites: http://forums.macrumors.com/showthread.php?t=353612http://www.freeiphoneunlock.com/unlock/Tags: apple, iphone, t-mobile, unlock
Current Location: home
Current Mood:  accomplished
Current Music: Leo Laporte - The Lab with Leo #074
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
After the fallout from the recently-announced $200 iPhone price drop, Steve Jobs relented and agreed to split the difference with the consumer, offering $100 in Apple Store credit to all who purchased iPhones before the price cut was announced. (Note that, if you purchased your iPhone within 14 days, you can legally get a FULL refund for the device; just return it to the Apple Store and they will give you the full $200 credit as per their price matching guarantee.) I think this was a nice gesture on his part, and not necessarily called for. We early adopters are used to paying high prices for our kit, only to see them decrease shortly thereafter. True, $200 (about 1/3 of the price of the iPhone) is a rather steep price cut, and it occurred rather soon after the device was introduced; however, in the annals of tech gadget history, such a steep price cut so soon after a device's introduction isn't totally unheard of; the Nokia N-gage, for example, was discounted sharply very shortly after it was introduced. Anyway, Apple has just posted details and a web page on how you can claim your $100 credit. http://www.apple.com/iphone/storecredit/It's a pretty simple procedure, and involves supplying Apple with your phone's phone number and serial number (can be found on the back of the phone, or in Settings > General > About). You will get a (free) text message from Apple containing a claim code, which you then enter into the web form on the page above. Your store credit certificate prints out immediately, and can be used either at a retail Apple Store, or at the online Apple Store. I personally am planning on saving mine until October, when Apple's next generation OS, Mac OS X 10.5 "Leopard" will be released. Leopard will sell for $129, so this $100 credit will pay for most of it. Tags: apple, iphone, steve jobs
Current Location: work
Current Mood:  content
Current Music: Mischa Daniels/Tash - Round And Round (Electro Radio Edit)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Found this on some of the Internet forums I frequent. (I don't recall where, so I can't provide an attribution.) If you are frustrated by how slow the EDGE data transfer is on your iPhone, try holding the iPhone so that your hand does NOT cover the black plastic antenna area at the bottom of the screen. This requires a somewhat awkward grip on the unit, but I have noticed a definite improvement in the speed and reliability of my EDGE data connections. Some people on the online forums are reporting as much as a 50% increase in EDGE data performance using this technique. It's not a dramatic speed increase (like, it won't suddenly feel like WiFi or EVDO), but it definitely makes the EDGE network much more usable. Why didn't Apple locate the antenna at the top of the iPhone (where, incidentally, most other cell phone manufacturers place their antennas)? Sigh. At least on the iPod touch, they place the WiFi antenna at the top left of the back of the iPhone case (where the camera would be located on an iPhone). EDIT: I found the blog where I first read about this. URL has been TinyURL-ized for your convenience. http://tinyurl.com/2ll9reTags: apple, at&t, edge, iphone
Current Mood:  tired
Current Music: Ayumi Hamasaki - Too Late (Lab Life Remix)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Among my geek friends, we often joke that once a product hits Woot.com, it can pretty much be declared as dead, or at least very-soon-to-be-dead. Woot.com, in case you didn't know, is an Internet overstock clearing house of sorts, with a somewhat interesting business model. They only sell one item per day (which goes up at midnight Central time -- they are located in Carrollton, TX), at a fixed price. Once they have sold out of the quantity of the item that they have, that's it for the rest of the day - you have to wait until the next day and see what item comes up next. Sometimes, very rarely, a company chooses to launch a new product through Woot.com; this is signified by the now-infamous "pope hat" icon appearing on the item page that day (which really is supposed to be a picture of a rocket ship - get it, rocket ship, "launch" event??? - but it really looks like a Pope's hat.) But most of the time, it's a bunch of random crap that some warehouse or something wants to get rid of, and quickly. In fact, Woot often capitalizes on the crappy nature of the products they receive; periodically, when they have accumulated an excessively large amount of said crap, they actually sell "Bags of Crap" (BoC's) which contain 1-3 random items of detritus (depending on how many the user selects). Basically, you pay $1 per item (up to a maximum of 3 items), plus Woot's standard $5 shipping charge, and the lure is that (like Forrest Gump's infamous box of chocolates) "you never know what you're gonna get." Some people have gotten some pretty decent items. A long-standing legend says that one person even got a big-screen plasma TV even! But usually it's just a bunch of junk. Woot's article in Wikipedia does a far better job of explaining all this than my feeble attempt, I'm afraid, so go ahead and check it out if you're curious (or just terminally bored). Anyway, yes there IS a point to my ramblings. Last November, Microsoft finally launched its infamous Zune music/media player. It was supposed to be their great "iPod killer." Unfortunately it's turned out to be a big joke. Most technology pundits have widely panned the device. The device itself is actually technologically advanced - the screen is bright and clear, and much better suited for watching videos than the iPod with video's smallish screen. Of course, the device is pretty chunky... then again, it's a Gen.1 product, and remember, the first iPods were pretty chunky as well. But it's the software that really killed the Zune. First of all, being a Microsoft product, it was naturally tied to Windows. The product was released about 2 months before Windows Vista came out; however, they did NOT make the Zune's software (which is REQUIRED to get music and videos onto the device) Vista compliant. It took them forever to release the Vista update. And yes, the Zune used separate software for music/video management - it did NOT plug into the already-existing Windows Media Player framework. Naturally, the Zune featured Microsoft DRM, but again, they did NOT use the already-existing Microsoft PlaysForSure DRM standard. This means that any music you already bought from other stores, such as Microsoft's own music store, or the joint Microsoft/MTV venture "Urge," would NOT work on the Zune! You had to actually re-purchase your music through the Zune Marketplace, which used its own, COMPLETELY SEPARATE form of DRM. Many people were angry with Microsoft because they caved into the record companies. Aside from the above DRM crap, they actually made a deal with Universal in that, for every Zune sold, Microsoft would give a kickback to Universal. And finally, the device's oft-touted WiFi music sharing feature was ill-conceived and no doubt crippled by the music industry. Sure, you could share your music with any nearby Zune using the built-in auto-configuring point-to-point WiFi. But, the song would only last for 3 days or 3 plays, whichever came first. Once your 3 days or 3 plays were up, POOF, the song disappears from your Zune. This even applied to NON-DRM'd tracks, such as MP3's you added yourself to the Zune, or even freely downloaded Podcasts. (oh, speaking of Podcasts, the Zune software didn't even support this popular form of Internet broadcasting - to get a podcast onto a Zune, you would have to go to the podcast's website and manually download each episode as a separate MP3 file and add it to the Zune manually.) Anyway, back to the original point of all this. Last night, guess what appeared on Woot.com when I hit reload? Yep! the Zune!! In all its glory. Unfortunately they only had the white model. Too bad. I would have loved to see the infamous "brown Zune" on display. Anyway, Zune on Woot.com. Woot.com usually sells stuff that won't sell anywhere else and/or is about to die. You put 2 and 2 together. Here is a screenshot of the Woot.com page taken on the morning of Wednesday, August 22 at approximately 8:14 AM. I took this because Woot.com changes its items every night at midnight Texas time (or 10 PM Pacific Daylight time), so it will be gone by the time many people read this blog entry. At this year's Macworld, Steve Jobs did a little bit of comparison between Zune sales and iPod sales. The numbers were NOT pretty, and in the end, Steve put up a slide showing the Zune logo, going up in flames. Flames indeed! Tags: apple, ipod, woot, zune
Current Mood: jubilant
Current Music: ...the sound of silence...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
One of the many advances that the iPhone brought to the table is Visual Voicemail. Traditionally, you have to listen to your voicemails in sequential, FIFO (First-in, first-out) order. But what if you are expecting a call from a certain person, and want to go directly to that person's voicemail, while skipping the 3 or 4 telemarketers that called before him/her? With traditional voicemail, you'd either have to listen through the whole thing, or use the "skip" button (if your voicemail provider even supports that function) to quickly skip past them. (And what happens if you press it one too many times and overshoot? etc.) Visual Voicemail presents all of your voicemails in a list on-screen; each message is labeled with the caller's name (ascertained by the Caller ID of the person who left the voice mail, and matched to a person in your phone's address book). Here's the deal tho: if you only want to listen to message #8 of 12, you don't have to listen through the first 7; just tap your finger on message #8 and it starts playing immediately. Individual messages can be listened to, responded to, and deleted, each on its own, in this manner. Ever since Steve Jobs announced this feature at Macworld Expo in January, I have been curious as to how Apple and AT&T implemented this nifty little feature. Now I think I've figured out how they do it. Or, at least, I have a pretty educated guess as to how they do it. One thing GSM based cell phones (such as the iPhone) are (in)famous for is what I call "the GSM buzz." Try this: turn on a radio (or a pair of computer speakers), and put your GSM phone next to them. Wait a few minutes. (Or, if you are the impatient sort, go ahead and call yourself.) Unless your speakers are super shielded, you will hear a loud and annoying buzzing noise. This is because the radio frequencies that GSM uses are particularly "dirty," and they can "leak" into audio circuits (speakers, microphones, etc.) if placed near them. (I don't have a formal background in radio theory, so that's the best explanation I can give; if you have a better one, please feel free to chime in in the comments section.) Anyway, this "GSM buzz" is a pretty good way of telling when your phone is actually "talking" to the network. Usually, when a phone is idle, it only emits a very short burst of "GSM buzz" every few minutes. This (I think) is a sort of "heartbeat" connection; basically, every X minutes, your phone announces "Hey! I'm still here!" to the network. If the cell phone network doesn't receive one of these "heartbeat" packets after a certain time-out period, it assumes that your phone has either died, or you have moved out of the range of coverage, and the cellular network takes the appropriate action. (usually, immediately redirecting any incoming calls you receive to voicemail, or telling other cell towers to start looking for your phone in their coverage areas, etc.) Again, I don't have any formal training in cell phone theory or whatever; this is just my educated guess. But, if your phone is active -- you are making or receiving a call, sending or receiving a text message, or using your phone's data service -- then the thing really starts emitting signals, resulting in an almost-constant GSM buzz that sounds like a nest full of really angry bees. Depending on how intense your phone or data usage is, this can tend to get really loud and annoying. Anyway, when I am at work, I usually leave the iPhone sitting on my desk next to my keyboard. Naturally, I also have some computer speakers nearby as well. One time someone called me whom I didn't want to talk to (i think it was a telemarketer or something). While the phone was ringing, I heard the GSM Buzz. This I think was basically the AT&T network telling my phone "HEY! The phone is ringing!" Of course, once the phone stopped ringing, the GSM Buzz ceased. But, a short time later, the GSM buzz started up again, kept going rather intensely for several minutes. Right after it stopped, I heard the phone's "new voicemail" alert sound. Sure enough, there was an annoying message from that telemarketer (or whoever it was). I remember thinking how odd this was, because, with my previous GSM phone (which, admittedly was on T-Mobile), the sequence went like this: 1. loud sequence of GSM buzz while the phone was ringing 2. when the phone stopped ringing, GSM buzz stopped 3. several minutes later, a short burst of GSM buzz 4. the "new voicemail is waiting for you" indicator on my phone turned on Which leads me to believe that the short burst of GSM buzz in step (3) above was basically the T-Mobile network telling my phone "turn on the 'you have voicemail waiting' light." Naturally this made me wonder why AT&T's sequence appeared different. Could it be that my phone is actually *downloading* the whole voicemail message from the network? Might that explain the LONG burst of GSM Buzz before the "new voicemail" alert, instead of the short burst I witnessed on T-Mobile? So I set up an experiment. I reset my iPhone (to make sure everything was starting from a known state), and called myself on it. I let it ring through to voicemail, and left myself a message. Sure enough, several minutes after this, I heard the long burst of GSM buzz, and the iPhone announced "new voicemail waiting." Then, before doing anything else, I turned on the iPhone's "Airplane Mode." Airplane Mode basically turns of ALL of the wireless radios in the iPhone (cellular network, WiFi, and Bluetooth), making it "safe" for air travel. (because the FAA does not allow any sort of wireless signals in a moving plane) At this point, the phone is basically deaf, dumb, and blind... it can't talk to the cell phone network, nor can it be talked to by the cell phone network. I tapped through to the voicemail menu... and sure enough, the voicemail I left myself was listed. I tapped the "play" button... ...AND IT PLAYED!!! It seems that what I suspected is indeed true. Periodically, the iPhone calls out to the AT&T network and asks it "Hey, does the phone number that I am registered to have any voicemail?" If AT&T responds "yes," then the iPhone asks "Ok, go ahead and let me download it." The iPhone downloads it and stores it locally. So, in essence, your voicemail is actually stored ON YOUR PHONE, and NOT on the AT&T network. This is wild. And strangely enough, it is exactly the way that Japanese cell phones handle voicemail. Several years ago, we went on a wonderful trip to Japan. Aside from seeing lots of cool stuff and meeting lots of cool people (whom we are still friends with to this day), I picked up a few bits of cool technology. Including a Japanese prepaid cell phone. Now, this wasn't really a frivolous purchase. It really came in handy, as we were meeting several friends in Japan, and also trying to visit several restaurants helmed by the famous Iron Chefs; so being able to make and receive calls really came in handy. ("We're at the FOO train station, standing by the large BAR statue. Where are you guys?" etc.) Plus, it turned out to actually be cheaper to buy a prepaid cell phone, than to rent one. Anyway, as we were using it, we managed to get a few voicemails (missing calls from friends because we were in the bathroom or whatever). I never really figured out how to delete those voicemails, so I figured I'd just leave them there, and eventually, when the prepaid phone number expired, they would be erased from the voicemail server. Well, several months after we got back home, I happened to find that cell phone stashed in one of my random bags of stuff. The battery still had a charge in it, so I figured what the hell, and I turned it on. It fired up perfectly; but naturally, since Japanese cell phone networks are VERY different than US networks, I got the Japanese equivalent of "searching... no signal." Then I noticed the voicemail indicator was still lit, so I pushed the voicemail button. I was quite surprised to hear all of the voicemails that I had received on that phone, that I had forgotten to delete. Yes, apparently the Japanese cell phone network downloaded them to the phone itself. I am glad to see this technology finally make it onto US cell phone networks. I hope that other companies follow suit and deploy technology of this sort. It will undoubtedly require some upgrades on the phone end of things, but especially with today's powerful smartphones (which are in essence very powerful pocket-sized computers, and thus incredibly flexible and programmable), such a massive upgrade is definitely feasible. Tags: apple, iphone, visual voicemail
Current Mood:  curious
Current Music: ...the sound of silence...
|
|
|
|
|
|
|
|
|
|
|
|
![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small}
dburr's journal
Previous
amused
pissed off
