This is a Technological blog which is used to share knowledge and views of industry experts.
Saturday, 17 January 2015
Thursday, 15 January 2015
Google’s Project Ara update: New partners, inductive data transfer, and cutting-edge battery tech
Google’s Project Ara update: New partners, inductive data transfer, and cutting-edge battery tech
Ever since Google’s Project Ara debuted, consumers have been interested in the possibility of a customized smartphone with hot-swappable modules and varying functionality that can be changed on the fly depending on the user’s needs. Today, Google gave a major update on where the program is and where it’s headed through 2015.
Right now, Google is focused on building what it calls the Spiral 2 device, a new version of the hardware that will include multiple modules, greater flexibility, the option to swap out the battery while the device is in low power mode, and the opportunity to use multiple antennas for better signal sourcing and multiple carrier support. Spiral 2 also shifts from FPGA’s (Field Programmable Gate Arrays) to ASICs — specialized application-specific integrated circuits with superior performance and generally lower power consumption compared to FPGAs.
Spiral 2 still has some problems with signal degradation over the long term and an issue with the framework used to attach the various modules. Google is reportedly working on induction signaling, with a 150-micron gap between components that will prevent the wear and tear that comes with repetitive switching back and forth. These improvements will come with Spiral 3, which adds additional RF field improvements as well (as shown below).
Project Ara’s roadmap
Google also laid out the Project Ara longer-term roadmap through 2015, including plans for an eventual market test in Puerto Rico by the end of the year.Spiral 3 will add the Rockchip reference design, an LTE 4G modem, an Android release, packaging and decorating improvements, and an updated framework for software development that’s meant to make it easier for both software and hardware developers to build their projects. Google also talked up the concept of giving new and unusual battery designs a forum to experiment with Project Ara — there are battery technologies that offer substantial improvements over conventional lithium polymer architectures, but either cost too much for typical inclusion into smartphones or have other, specialized requirements. Some of these could be met within the Project Ara modular concept, and Google wants to see the platform used for prototyping and market testing.
Longer term, the goal is to create an initial pool of some 20-30 modules, including some of the options shown above. Google didn’t go into detail on what a “pollution sensor” might be, but it’s possible to include a carbon monoxide, carbon dioxide, and other types of smoke detector modules in a smartphone platform. A Project Ara device could conceivably include multiple modules to scan for various types of atmospheric contaminants, along with an LTE modem to report their prevalence at specific locations.
Google has stressed the goal of creating an entire ecosystem around this concept rather than simply throwing it to the consumer-wolves, which implies that the device could at least find targeted applications in specific markets or spaces where its customizability are a selling point. It’s not clear if the wider consumer space will take to the device (this will likely be cost-dependent) but the modular nature could prove popular with enthusiasts and hobbyists who want the ability to customize a phone for particularly long battery life or with specialized sensors. The ability to use multiple antennas could also prove useful for globetrotters, if the phone can be equipped with a sufficiently flexible LTE radio to allow for a truly global device.
If the Puerto Rico tests go well, Google intends to move forwards with market availability in the 2016 timeframe.
Google throws nearly a billion Android users under the bus, refuses to patch OS vulnerability
Google throws nearly a billion Android users under the bus, refuses to patch OS vulnerability
Google Android Logo |
When it comes to providing security updates for previous products, various manufacturers have pursued different strategies. Some, like Microsoft, tend to provide security updates long after they’ve stopped selling an operating system (Microsoft only stopped providing Windows XP support last year). Others, like Google and Apple, have pursued tighter timelines for security updates. Google is now doubling down on that schedule, refusing to patch bugs in Android 4.3 or prior, even when those bugs could expose critical vulnerabilities on nearly a billion devices.
The flaws in this case affect Android 4.1 to 4.3, aka Jelly Bean, which began shipping in mid-2012 and was the primary version of Android through late 2013, or roughly 14 months ago. Up until quite recently, Google has aggressively patched problems in Android’s WebView rendering engine. Before KitKat (Android 4.4), all versions of Android used the version of WebView found within the Android Browser for rendering HTML webpages. With KitKat and Lollipop, Google updated the operating system to use a WebView plugin derived from its Chromium project.
When Security firm Rapid7 discovered a new exploit in the Android Browser version of WebView, it contacted Google to inform the company that Android 4.3 and below were vulnerable. Google’s response and policy change are raising major eyebrows. Specifically, the company states that:
If the affected version [of WebView] is before 4.4, we generally do not develop the patches ourselves, but welcome patches with the report for consideration. Other than notifying OEMs, we will not be able to take action on any report that is affecting versions before 4.4 that are not accompanied with a patch.
In other words, security staff are now expected to submit a patch to fix an issue when they report it. If they do, Google will “consider” the patch to see if it resolves the problem. If they don’t, Google now says the only thing it can do is inform various OEMs of the problem.
What Google is doing, in essence, is telling its user community “Sorry, you have to tell Samsung, LG, and Motorola to provide you with an updated version of our operating system.” This is hilariously impossible. It would never fly in the PC world — imagine Microsoft telling customers “Sorry, you have to make HP, Dell, and Lenovo provide you with a free update for our operating system.” The disparity is even larger if you consider that, in most cases, a computer running a previous version of Windows can be upgraded by the end user to run the next version. That upgrade may be a headache, but system requirements on Windows haven’t budged in nine years.
The average phone or tablet buyer has no way to upgrade their operating system unless the carrier provides an OTA update, and two-year upgrade cycles means that plenty of people are going to be stuck on broken devices with known exploits that Google isn’t going to fix. Granted, the fact that Google fixes an exploit doesn’t mean that carriers will deploy it, and fragmentation has been a major problem in Android’s ecosystem over the years — but there’s a difference between acknowledging the difficulty of maintaining security updates for the entirety of one’s user base and flatly refusing to do them.
Pushing OEMs off open-source Android
One obvious reason for Google to stop fixing Android Browser problems is that the company is aggressively moving to get OEMs to stop using Android’s open-source features and to replace them with features licensed directly from Google. Ars Technica has done an extensive write-up on this trend here, and getting rid of the Android Browser is a key facet of moving away from an Android that’s actually maintained and useful.No, Google isn’t killing Android — it’s just ensuring that the only parts of the program that get feature updates, capability improvements, and performance enhancements are the parts that require licensing agreements and promises not to develop competing products. The reason Amazon’s Kindle Fire has its own app store, and Samsung’s continued interest in Tizen are both the result of Google’s push to embed itself into the center of mobile business while paying lip service to the idea of open source.
By throwing all of the responsibility for security updates back on carriers and security researchers, Google is telling OEMs that they can either agree to its licensing terms and fall in line, or take on the responsibility of performing security updates that they’re typically not qualified or funded to do. It’s a trick worthy of Microsoft in the Bad Old Days, and it’s particularly funny to see the company doing this, given that it threw Microsoft under the bus in December when it published the full details of a security flaw two days before Redmond patched it, on the grounds that the desktop and laptop OS company wasn’t moving fast enough.
Saturday, 10 January 2015
Windows 10: 12 things you need to know
Windows 10: 12 things you need to know
Microsoft gave the first look at its Windows 10 operating system on Tuesday, a major release that will span all hardware from PCs to phones and try to address the ills that have dogged Windows 8.
The event in San Francisco was aimed mostly at enterprise customers, and Microsoft promised an OS that will be more intuitive for the millions of workers still on Windows 7 and older OSes. Here’s a rundown of some of the key points we learned Tuesday about Windows 10.
Why Windows 10?
The natural name would have been Windows 9, but Microsoft is eager to suggest a break with the past. “We’re not building an incremental product,” said Terry Myerson, head of Microsoft’s Operating Systems Group.
Microsoft considered the name “Windows One,” he said, to match products like OneNote and OneDrive and its “One Microsoft” business strategy. But he noted the name was snagged a long time ago, by a young Bill Gates.
Perhaps Microsoft didn’t like the idea of being numerically one step behind Apple’s OS X. (A reporter asked jokingly if subsequent versions will be named after big cats.)
Whatever the reason, Windows 10 it will be.
“When you see the product in its fullness, I think you’ll agree it’s an appropriate name for the breadth of the product family that’s coming,” Myerson said.
What car does it resemble?
Yup, Microsoft came up with a car analogy. It wants you to think of Windows 10 as a Tesla.
“Yesterday, they were driving a first-gen Prius, and when they got Windows 10 they didn’t have to learn to drive something new, but it was as if we got them a Tesla,” Myerson said.
What devices will it run on?
All of them. Microsoft demonstrated only the desktop version Tuesday, but Windows 10 will be for tablets, smartphones and embedded products, too.
“It will run on the broadest types of devices ever, from the smallest ‘Internet of things’ device to enterprise data centers worldwide,” Myerson said. “Some of these devices have 4-inch screens, and some will have 80-inch screens. And some don’t have any screen at all.”
Is there a start menu?
There is, and it tries to combine the familiarity of Windows 7 with the modern interface of Windows 8. That means the menu is split: On the left, apps are displayed in the familiar Windows 7 style, while on the right are more colorful “live tiles” that open the modern, Windows 8-style apps. The start menu is customizable, so you can resize the tiles and move them around, and make the start menu tall and thin or long and flat.
Will I still toggle between two distinct app environments?
Apparently not. In Windows 8, when you launch a modern-style app, it takes you into that modern UI, and when you launch a Win32-style app, it launches to the traditional desktop environment.
In Windows 10, “we don’t want that duality,” said Joe Belfiore, a corporate vice president with the OS group. “We want users on PCs with mice and keyboards to have their familiar desktop UI—a task bar and a start menu. And regardless of how an app was written or distributed to your machine, it works the way you expect.”
So how does it look now?
If you launched one of the new-style apps in Windows 8, it filled the whole screen and there weren’t many options to resize it. With Windows 10, the familiar “windows” metaphor is back; you’ll be able to resize the new-style apps and drag them around the screen like an old Win32 app. Conversely, if you’re using an older Win32-style app, it will be able to “snap into place” and fill all the available screen space just like the modern apps.
What else is new?
Some users have been confused by the Windows 8 interface and can’t figure out what’s open on their screen or how to get back to an app. Windows 10 has a feature like OS X’s Mission Control that lets you zoom out and see everything that’s open on a PC, then select any app to enter it.
You can also have multiple desktop configurations open and switch between them. So if you have two apps on the screen for a particular task, sized just how you want them, and then you change to some other apps, you’ll be able to get back to those first apps easily without having to resize them again. You can navigate through several of these desktop displays at the bottom of the screen.
What’s in it for business customers?
Today’s event was focused primarily on business users; Microsoft will talk about the consumer aspects of Windows 10 early next year. There weren’t a lot of specifics but here are a few points:
— Microsoft promises that Windows 10 will be more intuitive than Windows 8. “Windows 10 will be familiar to end users whether they’re coming from Windows 7 or Windows 8. The workers will be immediately productive,” Belfiore said.
— It will be compatible with “all traditional management systems in use today.” Customers are increasingly using “mobile device management” tools to manage phones and tablets. “Windows phones and tablets support MDM today, but with Windows 10, customers will be able to use MDM to manage all their Windows devices” including PCs, laptops and even Internet of things devices.
— Developers will get “one application platform,” Belfiore promised. “Whether it’s building a game or a line-of-business application, there will be one way to write a universal application that targets the entire product family,” he said.
Will it still be touch-enabled?
Yes. “We’re not giving up on touch,” Belfiore said. That means you’ll still be able to use touch to do things like scroll and pinch-to-zoom on laptops and desktops.
There’s also a new feature, tentatively called “continuum,” for people using two-in-one PCs. When you detach the keyboard from a Windows 10 hybrid, it will ask if you want to go into tablet mode. If you say yes, the UI changes to better match a tablet. The app expands to full screen, for instance, and the start menu switches into a larger-icon mode.
Is there a Command Prompt?
You’re kidding, right? Well, actually there is. Microsoft showed how it now supports shortcuts like CTRL+C and CTRL+V so you can paste in a directory listing from another app, for instance. Belfiore called it a “niche, geeky feature” but said he wanted to show the diverse range of users the OS is trying to support.
When will it be released?
The OS will launch around the middle of next year, after Microsoft’s Build conference. Before that, a select group of “Windows insiders” will receive a “technical preview build” for laptops and desktops on Wednesday this week, followed “soon after” by a preview for servers. Previews of other device categories will follow later.
Subscribe to:
Posts (Atom)
The Future of Remote Work, According to Startups
The Future of Remote Work, According to Startups No matter where in the world you log in from—Silicon Valley, London, and beyond—COVID-19 ...
-
Cyber security v/s Information Security Hollywood exerts influence over many areas of modern life, even down to how people thi...
-
By now, you’ve probably already heard, seen or even played with one of the technical Windows Server 2016 previews. If not, I urge you to d...
-
The Future of Remote Work, According to Startups No matter where in the world you log in from—Silicon Valley, London, and beyond—COVID-19 ...