Tag Archives: beta

Google Chrome OS Notebook (CR-48): One week in

Just a quick update in my ongoing series about using the CR-48. View earlier posts here: Initial observationsa few more observations, and discovering developer mode.

Since my last post,  

I’ve burned through my free 100MB of Verizon. 3G. Attempted to set up add-on data plan online (to tide me over until my free 100MB allotment resets next month), Verizon web form accepted my information and then displayed a “call Verizon” page. Called Verizon to buy add-on data: Long, painful process to finally get transferred to a Verizon employee aware of the Google CR-48 program and special pre-paid data offerings. In all fairness, it’s a new program and Verizon is likely in the process of getting front-line staff trained. Still, wish it had been a smoother process

Continue to use the CR-48 as my primary personal laptop. Surprisingly, the adjustment has been smoother and more pleasant than I expected. After enabling developer mode and installing the developer OS update, the trackpad responsiveness issues seem to be resolved. 

Squashing bugs: I figure if Google sent me a free laptop on the condition all I need to do is use it and report bugs, I’ll do my best to get them feedback on my experience. I’ve found some bugs but since data is saved to the cloud, even those requiring a rude shutdown haven’t really been an issue. It’s a nice experience.

I’ll continue to blog on my CR-48 observations — leave a comment if you have any questions.


Google Chrome OS Notebook (CR-48): Discovering Developer Mode

After being surprised and delighted to receive a Google Chrome OS Notebook (CR-48) a few days ago, I’ve been blogging about my CR-48 initial observations and day-to-day experience.

Yesterday, I decided to try out Developer mode after reading an article on ChromeOSSite.com. It’s an easy process, essentially flipping a switch located in the battery compartment, rebooting and a few other steps (outlined by ChromeOSSite.com here). When I first rebooted, I was greeted by an unnerving screen that declared the OS unverified. Clicking on this screen took me to screen explaining how to re-load the OS (the provided url mentioned loading the OS onto a thumb drive and re-installing). OOPS!

All I needed to do was to remain on the initial boot-up screen following reboot. By waiting at that screen several seconds, the system beeps a few times and then boots into the user log-in screen (as expected). Whew!

My understanding is that developer mode enables:

  • Shell access & other geeky fun: As I kick around in the CR-48, I may want to delve more deeply — developer mode enables this exploration
  • More frequent OS updates: The “normal” (non-developer) mode provides a beta experience. As soon as I rebooted into developer mode, a new OS update was downloaded — perhaps an OS version closer to alpha than beta?

So far, the Developer OS version seems slightly faster than the beta. The OS still struggles with pages containing Flash plug-ins and chugs a bit when trying to load several bookmarks at a time. But hey, it’s beta (or perhaps even alpha), right? Bugs and rough edges are to be expected…. just part of the experience.

I’m still surprised that I haven’t needed to revert to using my Vaio (aside from a short time on Friday). I’m finding the Chrome OS user experience enlightening in just how much I live on the web.

I haven’t yet used the built-in Verizon 3G connectivity, and may try this out today away from home. I love that 100MB is provided free monthly, but a little concerned about how quickly I could burn through that. Luckily, Verizon has included an unlimited day pass for $9.99 in their CR-48 data plan offerings.

I’ll continue to blog on my CR-48 observations — leave a comment if you have any questions.