Like others, I've had the sneaking suspicion that the battery on my new iPhone 3GS was being consumed faster than I would suspect, given my level of usage day in and day out. My average morning usage would consist of a call or two, a few Web searches, a cursory e-mail check on three or four accounts, listening to a podcast or audiobook for an hour, and 20 minutes of gaming. By noon, I'd find the battery -- fully charged when I started -- would be hovering around 50 percent capacity.
When iPhone 2.0 came out, one of the first things I did was to disable e-mail push on days I didn't specifically need it. With that in mind, I took a few extra steps in battery management along the same lines.
First of all, I rechecked the e-mail push/fetch settings. After making sure that Push was turned off, I set "Fetch New Data" to Manual on the master control, also making sure each individual e-mail account was also set to manual in the Advanced screen.
Second, I turned off Push Notifications in the absence of anything trying to use it. On my iPhone at the moment, the only applications that support Push Notifications are the AIM instant messaging client and TapTap Revenge 2. Although I had individually disabled Push Notifications for each, I decided to also disable the master control as well -- since I'm not currently using the feature.
Lastly, I did a complete restore of the iPhone. When I got my 3GS a couple weeks ago, I did restored the settings, accounts and applications from my old iPhone 2G. In hindsight, this was a poor decision: The restore did not move a lot of data that I wanted to port to the new device (like Wi-Fi security passwords and application passwords) but may have brought some legacy bits with it that I don't want.
For instance, the complete restore and reconfiguration from scratch resolved some of the Bluetooth difficulties I wrote about in my review of the new device. Specifically, the BlueAnt Supertooth 3 speakerphone that wouldn't work with my 3GS suddenly worked fine.
As for battery performance since I made these modifications, it's only been two days but at first glance things have improved. On the first day, the normal amount of morning usage I described above left about 80 percent remaining capacity. Subsequently, I used the iPhone as normal throughout the rest of the day, did not charge my phone overnight, used it as normal on the morning of the second day -- and I now find myself with 46 percent remaining capacity.
A small sample size, to be sure, but so far so good.
There's a bunch of little tidbits that came out of my week with the Pre that didn't make it into the main Palm Pre review and slide show. Here are a few items of note:
Not a formal coverage test by any means, but I was able to listen to Pandora on the Pre with very good success. I made it all the way from downtown Oakland, Calif., to Milpitas (about 35 miles down Interstate 880) without a drop. It looks like when coverage drops from EvDO to 1xRTT, however, that Pandora -- or the Pre -- can't recover and the music dies.
Instant messaging is a bit of a problem on the Pre, as it can be a major battery hog. Since IM and SMS are both in the same Messaging application, IM won't turn off in the conventional manner. Closing the Messaging app by throwing it off the screen doesn't work -- it still runs in the background. Instead you have get into the Messaging app and click on Buddies and then your presence indicator in order to sign out.
Many may not know this, but Palm has released a small firmware upgrade since the launch, taking the device to 1.0.2. If it hasn't happened to your device yet, go to the Upgrade application and give it a shot. If on the WAN connection, you may have to try several times. Wi-Fi will be quicker.
Every now and then the device hangs, showing a blue sky background with a few clouds. To force a restart, hold down the power button and slide the ringer mute back and forth three or four times.
I'm hearing some reports of trouble with Exchange servers with a little extra security. I haven't noticed that myself, but I did not have a problem downloading attachments in one instance. I got some long error message for a couple hours, but it still worked over IMAP. I couldn't replicate the next day, but it is something to keep an eye on.
When coming out of BART tunnels or other such areas with poor to nonexistent coverage, the Pre will report that I am roaming and data is not supported. Users should keep an eye on the bill to make sure they aren't getting screwed by something there.
I didn't talk about the phone's sound quality. In a nutshell, decent from the handset but a little muddy. Understandable, by any means. Over the included wired headset or Bluetooth, it sounds just fine.
The Touchstone power block is sold as an accessory for $70. You have to swap out the stock back face plate for one with an extra power conductor that comes with the Touchstone. The stone is a little sloped so you can keep using the device while charging.
Didn't get a chance to try the Pre with iTunes before I sent it back but I did connect it to a PC. When connected, the user must choose -- media sync, USB drive mode or just charge. If in USB drive mode, you can't use the phone. A really draconian way of keeping you from tethering, and pretty stupid if you ask me. If anyone knows a legitimate technical reason for this, I'd love to hear it.
Anyone still hoping Newber will make it through Apple's maze of certification can kiss that hope goodbye and should now start longing for Google to open up subscriptions to Google Voice née GrandCentral soon instead.
From the e-mail just sent to beta users like myself:
"As you may be aware, Newber first applied for acceptance into the App Store on October 2nd, 2008. After more than five months awaiting approval, and despite both overwhelming response from the professional community and varied attempts to get any kind of response from Apple, Newber has not received a review. Not rejected, not accepted - limbo.
We are sad to say that for this reason FreedomVOICE has stopped development on Newber. For this reason we will be ending the extended Newber Beta Test on March 31st, 2009. We would like to give you the next few weeks as an opportunity to begin transfer of your Newber phone number to the carrier of your choice. If you are interested in doing so, simply contact your new carrier and follow their procedure for having a number transferred. Your new carrier may contact FreedomVOICE Technical Support at 1-800-477-1477 ext. 2 if they need to verify any information.
After March 31st, all remaining Newber Beta Test phone numbers will be canceled."
More depressing news about this can be found here.
update: Got the go-ahead to move from GrandCentral to Google Voice yesterday. More on my impressions of the new service coming soon.
In the run-up to Apple's iPhone OS 3.0 unveiling, I found myself less interested in the specific details of what would or would not come with the actual release, but rather in whether my first generation iPhone would be party to the new features at all.
I expected the worst, anticipating Apple try to force me into a hardware upgrade approximately two seconds after my existing service contract expired. Now I am well aware of the growing obsolescence of my iPhone - with its diminishing battery capacity and molasses slow EDGE data connection - so the new software seemed like a great opportunity to push cheapskates like me into some new hardware.
So I was pleasantly surprised when the news was not quite as dire as I expected.
While iPhone OS 3.0 will be available sometime this summer as a free download to all iPhone 3G users (under contract with a carrier, of course), as a "special bonus", Apple will also let users with Gen 1 hardware install the update for free as well. Due to hardware limitations, 1st generation iPhones would be absent some features though, namely MMS and stereo Bluetooth.
iPod Touch customers (of both hardware generations) can also gain access to the new software for $9.95.
I've been waiting with baited breath all week for Google to upgrade my GrandCentral account to the rebranded Google Voice service. Hopefully with this upgrade, GrandCentral will finally be usable given my particular set of needs and devices - only a full year after I first tried putting the service to work.
"Man, I hate the Comcast DVR. I thought it would be fine as a secondary recording device, but it just keeps letting me down. I think I will call Comcast and cancel the DVR service."
One of the more frequent comments that I have gotten from readers in reaction to my January look at the first beta of Microsoft's forthcoming Windows 7 desktop operating system was that Windows Vista and--guilty by association--Windows 7 got in the way of people doing real work.
Only a few have bothered to elaborate on what they mean by this, but I suspect that those with this complaint fall into two camps: those uncomfortable with the new UI and menu structure introduced in Vista, and those who have run afoul of the User Account Control security functions.
UIs are not natural things. They are artificial constructs borne out of committee and group think, and are therefore never what any one specific person wants. They're a consensus. Whatever is left is something most people essentially memorize and get used to. Personally, I stuck with the Windows 2000 interface for the last nine years, but Windows 7's new taskbar and start menu really appeal to me.
On the other hand, I tend to view UAC in the same way I view public urination laws. Yeah, following the rules of either may slow me down from my daily appointments, but for the sake of health (staying free from malware), sanitation (keeping the registry and file system uncluttered), and social mores (not spreading a worm or botnet to others), the laws--and the feature--are worth having on the books.
I've been using Vista on my work machine for a full year now, utilizing UAC the whole time. Not only is UAC active, but I require an over-the-shoulder password in order to make a change (as in, I am not an admin and therefore need a secondary admin account for approvals). In that time, I've learned exactly which applications behave as I think they should under UAC, which applications have idiosyncrasies or problems (with security products being among the worst offenders due to their constant need for updates), and when I can expect to need those admin credentials.
My count of UAC prompts over the last seven days? Six, and all occurred as I intentionally upgraded software. I wonder if six in a week qualifies as getting in the way of real work?
A lot of people hate UAC because the feature breaks legacy applications. But this is not the fault of Windows really, but of the third-party software. It's bad code, written by lazy, hurried, or unconcerned developers adhering to development standards 10 years in the rear view mirror. I can't tell you how many product vendors I have talked to who have given me the same spiel about their software, saying in essence, "We'll get the features right, then fix the security later." And I am galled whenever I read about developers with the temerity to complain about the new security features in Windows getting in the way of the fast development of their code.
Always operating your computer with full administrative permissions has always been a broken model. No other mainstream operating systems encourage operating as root, and with Vista, Windows finally is trying to join everyone else. But users continue to balk, because they have grown accustomed to working by the rules of their broken model.
Stated plainly, sticking with Windows XP because later Windows break applications only serves to reward and enforce those sloppy development practices. In truth, it is not just Vista (or Windows 7) breaking those applications. Windows XP, like Windows 2000 before it, could certainly be operated by limited rights users, and a whole cottage industry has sprung up in the Windows eco-system just to solve permission problems for limited rights users on those systems.
To make an apples-to-apples comparison, whether Vista/Windows 7 is to blame for your loss of productivity, or whether it is actually due to bad software, I ask those steadfastly sticking to Windows XP to remove your administrative credentials from your user account. Get familiar with the "Run As" command, with multiple logins, and dealing with application permissions. Then make your assessment.
Alas, I admit I have been complicit in furthering these bad practices with shortcomings in my own testing and analysis for eWEEK. Therefore, I make this pledge -- from here on, in my reviews, I will ensure all software I test designed to run on Windows desktops operates as advertised with only limited user rights. And I will call out those that fail this litmus test.
Maybe together we can put a stop to the garbage foisted upon us.
The other day, Microsoft invited me over for an early look at Window Mobile 6.5, the next iteration of the company's operating system for phones. I didn't get to actually use the OS, but from my brief time watching it in action, I garnered several first impressions.
I think it safe to say that people will like using Windows Mobile 6.5 more than previous iterations. On the down side, there remains a lot of work still to be done before the operating system is ready to ship (I would say a November release is more likely than July), and the focus of the OS has swung back toward end-user enhancements over the needs of corporate administrators.
First of all, the new icon-based Start Menu looks to be a significant improvement over the current menu-driven layout. The honeycomb shape of the touch zones leaves lots of room for finger-based manipulation of the screen -- perhaps too much. While I absolutely love the idea that I will no longer need a stylus to get around in WM, I found on-screen real estate is now not consumed efficiently and users may need to do a lot of scrolling to find the applications they want.
Unlike with the iPhone or Android user interfaces, Windows Mobile 6.5 scrolls top to bottom (rather than side to side). The vertical scroll presents the Start Menu as a long list, rather than a page turning, which required more manipulation than I felt was necessary. This may have been due to the overwhelming sluggishness of the scrolling function, which I was promised will be improved as the OS moves through the beta process. The user can manually customize the order of icons in the menu to put more frequently used applications at the top, but that process could probably use some intelligence to automatically move icons up as applications get used.
I really liked the new approach to showing the user time-sensitive details, even when the phone is locked. I could see the next calendar item without unlocking the interface, and I could directly access applications with a state change from the lock screen. For instance, if a new voice mail is detected, I could go directly from the lock screen to the voice mail application without having to interact with the main menu or home screen first.
Unfortunately, the Microsoft representatives would not show me a touch-screen keyboard -- in fact, I saw no typing at all during the demonstration. The unit I saw in action (an HTC Touch Diamond, I think) did not have a physical keyboard, and I was anxious to see if the new on-screen keyboard was finger-ready (as I truly hate the tiny stylus-oriented on-screen keyboard that usually comes with WM). Even though I specifically asked to see the keyboard, I was deflected off with the nebulous statement that the keyboard will be different depending on the device.
This lack of cooperation leads me to believe that nothing has changed to this point with the touch keyboard. Microsoft had no qualms about showing me other features that didn't yet work right, so why be coy with the keyboard?
WM 6.5 also brings an updated mobile browser with it, at long last bringing a full browser experience natively to Windows Mobile. Users have the choice of either the full Web experience (which includes built-in Flash support) or a more mobile-friendly iteration.
I definitely found the zoom controls more user-friendly than some of the competition. Users could bring up a slider on the right side of the screen to adjust the zoom, then use a finger to move the on-screen focus to the appropriate spot, keeping an eye on on-screen markers that indicate the relative position on the page. The feature is not as intuitive as the iPhone's pinch and spread gestures, but much easier to use than the zoom on RIM's latest BlackBerrys.
Interestingly, the Microsoft representative told me that the browser in WM 6.5 is based on Internet Explorer 6, because that browser was still the most commonly used (and developed for) in the world. To my ears, that claim sounded out-of-date. I took a quick look at the browser utilization rates over the last year for eweek.com, and indeed found IE 6 was runner up to IE 7 (and third, also behind Firefox 3.0 for 2009). I'm no expert on Web development, but it sounds like the WM 6.5 browser may already be a little creaky from old age.
The Microsoft folks also showed me a demo of Recite, the early-stage voice recording and search feature. Although the feature sounds like total winner -- record a voice message and then search for it later with just a keyword -- I got the sense during the meeting that there was a pretty decent chance that Recite would not be in the official 6.5 release. The demo itself was pretty much a disaster, as only one out of four attempts identified the intended message.
We talked a bit about the My Phone synchronization service. First of all, calling My Phone a synchronization service is somewhat disingenuous, since the phone only connects once a day in the middle of the night. Let's just call it a daily backup -- a one-time full backup with ongoing incremental updates. Fortunately, from the screens I saw during the demo, it looks like My Phone will be usable for more than documents, contacts and calendars, as users should be able to back up some media (photos) as well. Ring tones will not be backed up.
The mobile administrator in me got hung up on the utility of My Phone in a business setting. For regulatory purposes, administrators need to be able to account for sensitive information wherever it may be. But My Phone really runs the risk of letting corporate documents out into the wild. Let's say a user downloads an e-mail attachment to the mobile phone, and then the attachment gets backed up to My Phone. Suddenly, this document has replicated to another service altogether, where it is accessible from other devices and PCs and out of corporate control.
When I asked about how administrators could stop this from occurring, I didn't get the sense this was a high priority for Microsoft at this time. Administrators could probably bar the user from replicating documents to My Phone altogether via policy, but perhaps not limit the synchronization to only certain stores or storage devices.
Let's just say I have some fear that in its zeal to replicate and expand beyond some of the appealing features that draw users to Apple or Google devices, Microsoft is giving short shrift to one of the largest segments of its existing customer base -- corporations. While Windows Mobile 6.1 was all about enhancing the mobile OS for corporate use and management, the newest version has swung back the other way to attract consumers and business end users, apparently without expanding the administrator's control over or visibility into how these new features behave.
In fall 2008 at CTIA, or more specifically at one of the satellite shows, I met with representatives of a company called Newber. They were writing an application for the iPhone. A little like GrandCentral, Newber provides users with a VOIP phone number, and the application redistributes calls received by that number to whatever number you want, such as to a land line or an iPhone.
I participated in the beta for the software, liking it on the whole when compared with GrandCentral, but not enough to pay the monthly fee once the software and service got approval from Apple's App Store.
Back in November, I got notice that the beta was officially ending, but we testers could keep using it until the App Store launch. I uninstalled the beta and moved on, figuring I would blog a little about it once it officially launched.
Today, it occurred to me that I hadn't heard anything about the software for a long time. Checking Newber's site, I learned why: It still has not been approved, 125 days and counting.
Check out the little ticker on Newber's homepage that counts out its pain, day by day.
The good news is that Newber now has a BlackBerry beta in the hopper too. If the company's lucky, RIM's App Store validation will not be nearly as onerous.
Rules: Once you've been tagged, you are supposed to write a note with 20 tech-related things, facts, habits or ideas about yourself. At the end, you will tag no one, since you should have forsworn chain letters years ago. However, if you want to share your tech idiosyncrasies, you can reach me at agarcia@eweek.com or leave a comment below.
1. Come July, I will probably ditch my iPhone. Not because of the device itself, but because AT&T's network gives lousy coverage in my house, in my office and along my commute route--even though I live in the heart of technology country. Those 4,490 available rollover minutes say it all.
2. I used to be a zealous advocate of building one's own PC. Now it seems like a lot of trouble, and maybe not such a great way to save money.
3. I built a telephone conference server to use at work out of old PCs, open-source software and a bunch of analog lines off our corporate PBX. The building and testing were infinitely more interesting than the meetings.
4. At home, I've been steadily digitizing all my media, mostly because I hate all the shelf space it takes up. I still can't cut the cord to physical media, though, as I like having it around. This is an annoying conundrum for me.
5. I am as baffled as anyone by Microsoft's phalanx of Windows 7 versions. I'd prefer to see two versions--Home and Corporate--with software add-on packs (for media, security and management). Unfortunately, I suspect this would make things harder for everyone somehow.
6. Despite my years of experience with wireless technology, I still can't make 1080p video stream consistently well without throwing thousands of dollars at the cause.
7. I hate running anti-virus software, and until last year, I never did on my personal systems. The rise of drive-by Web threats secreted on normally trusted sites really freaks me out, though.
8. I use Windows XP, Vista, Seven and CentOS Linux on a regular basis. None of them have changed my life. Perspective, people.
9. I pretty much never back up my personal data.
10. I got my start in IT because I kept accidentally cracking into a Unix server at work. I like to think the IT director saw something in me, but really, I think she just wanted to keep an eye on me.
11. During my first server crisis as an IT staffer, I spent the night on the floor next to the server with a bunch of manuals and Chinese food. The next morning, when everything was working properly, I thought that maybe, just maybe, I could do this for a living. The problem was something like, "Novell 3.12, when running on a server with an EISA bus, loads all memory-resident programs under 640K, no matter how much memory you have." Adding the OS2 namespace had pushed me over the limit. Or something like that--it's kind of a blur now.
12. My first PC was a Texas Instruments TI-99/4a, the second an IBM PC Jr. To keep my parents from using the systems, I wrote an authentication program that, when wrong credentials were entered, would match the onscreen text color to the background, then reboot the machine.
13. I got my first e-mail account in 1991, accessing it using Pine. Seven years later, when they forced everyone on the server to start using POP3, I lost interest in that account.
14. I find helping someone buy a smartphone is much harder than helping them choose a PC. It's simply too personal a preference to impose your will on. I ask three questions: "What carrier do you want to use?" "Can you type on a touch-screen?" "What three things do you want most to do with it?" I point in the right direction, then I get out of the way.
15. My personal domain name is an obscure Simpsons reference. It's not as cool as it once was. Or, it was never cool.
16. I use many VOIP services--mostly Skype,GrandCentral and Raketu. I still have a land line, although I never use it.
17. I loved the hands-on expertise and great customer service of my old DSL ISP, but I love even more the lower price and fast pipes provided by the local cable conglomerate. This makes me very sad.
18. While I suspect that I could easily replace my cable subscription with over-the-air HD, Netflix Watch Now, Hulu and Amazon.com services, I am not quite ready to make that leap.
19. On many occasions, I have stood in a Best Buy or Fry's looking for geek inspiration. More often than not, I will pull out my iPhone and order whatever inspires me online (usually at Amazon.com) while still standing in the store.
20. I think everyone should learn how to do bare-metal virtualization. Find instructions online on how to load VMware's ESXi on a USB stick, plug it into a computer with a lot of RAM and give it a shot. It will be worth the effort. Bonus points if you make an iSCSI server to use with it.
