Showing posts with label hardware. Show all posts
Showing posts with label hardware. Show all posts

Friday, 20 September 2013

Want Android your way? Stay tuned for Cyanogen's hardware partnerships

Want Android your way? Stay tuned for Cyanogen's hardware partnerships

Cyanogen, maker of CyanogenMod, one of the most popular third-party respins of Android, is planning something major. It isn't just a new version of its CyanogenMod software, it's a full-blown business plan that may include making CyanogenMod available as a preload on at least one phone maker's hardware.

Like the DD-WRT or Tomato firmware for routers, CyanogenMod's grown famous with some 8 million-plus Android fans. It adds tons of useful features not found in stock Android, removes carrier- and device-maker's bloatware, and works with a plethora of devices, both new and old. Other respins of Android are in turn based on CyanogenMod as well (such as Miui), as the project is open source.

Unfortunately, CyanogenMod -- and third-party versions of Android generally -- is notoriously difficult to load onto phones. Most Android devices ship with locked bootloaders, which requires a different installation process for each device.

Cyanogen co-founder Steve Kondik has decided it's time for a different approach. After raising $7 million in funding from Benchmark Capital, he left his previous job (working for Samsung since 2009, which gave him little time to run Cyanogen), hired a team of 17 developers, and formulated a plan to make CyanogenMod into a mobile OS that's all the more "by the users, for the users."

Aggressive end-user testing and feedback has long been a staple component of CyanogenMod's lifecycle. Kondik wants to not only keep it that way, but make it even easier to get on board the CyanogenMod train.

Among the first things Kondik has announced is a streamlined CyanogenMod installer that will soon be delivered through Google's Play store. The idea is to automate the install process as completely as possible, the best solution for end-users short of delivering CyanogenMod as a preload.

But plenty of gray areas remain. For one, whether or not Google will allow such software to be delivered by way of Play hasn't been established. Worst-case scenario: The user would have to sideload the CyanogenMod installer, which might prove little better than performing the whole process by hand.

A second question that's been asked (by The Verge, among others) and answered only vaguely: How does Cyanogen plan to make money if its core product -- the firmware itself -- remains a free item?

One obvious possibility is via a cut of hardware sales via a partner. That's Cyanogen's other big push. It wants to make a deal of some sort with a device vendor, although the name of the partner hasn't been announcer yet. (An educated guess: It's Samsung, by way of Kondik's previous job.)

Cyanogen could also make money by way of offering multiple versions of the product -- a free core version, with other features available either only as a for-pay item or only shipped with a hardware purchase. Yet another possibility is offering for-pay services of some kind: file storage, phone backup and restore functions, and so on.

What Kondik is trying to avoid, though, is becoming the very thing he hates. In his mind, the biggest issue with mobile devices running Android is that Google has turned them into "mobile cash registers" -- systems designed to monetize the users' behaviors first, with everything else a distant second. That's going to prove difficult, as software and hardware both become race-to-the-bottom commodities.

One other plan that Kondik has in store, though, makes perfect sense on the face of it: A name change and rebranding for the company, probably sometime next year. Let's see if the company's up to the task of delivering itself to consumers as frictionlessly as Google has.

This story, "Want Android your way? Stay tuned for Cyanogen's hardware partnerships," was originally published at InfoWorld.com. Get the first word on what the important tech news really means with the InfoWorld Tech Watch blog. For the latest developments in business technology news, follow InfoWorld.com on Twitter.


View the original article here

Thursday, 29 August 2013

IBM starts restricting hardware patches to paying customers

Following through on a policy change announced in 2012, IBM has started restricting availability of hardware patches to paying customers, spurring at least one advocacy group to accuse the company of anticompetitive practices.

IBM "is getting to the spot where the customer has no choice but to buy an IBM maintenance agreement, or lose access to patches and changes," said Gay Gordon-Byrne, executive director of the DRTR (Digital Right to Repair), a coalition for championing the rights of digital equipment owners.

[ For a quick, smart take on the news you'll be talking about, check out InfoWorld TechBrief -- subscribe today. ]

Such a practice could dampen the market for support service of IBM equipment from non-IBM contractors, and could diminish the resale value of IBM equipment, DRTR charged.

On Aug. 11, IBM began requiring visitors of the IBM Fix Central website to provide a serial number in order to download a patch or update. According to DRTR, IBM uses the serial number to check to see if the machine being repaired was under a current IBM maintenance contract, or under an IBM hardware warranty.

"IBM will take the serial number, validate it against its maintenance contract database, and allow [user ] to proceed or not," Gordon-Byrne explained.

Traditionally, IBM has freely provided machine code patches and updates as a matter of quality control, Gordon-Byrne said. The company left it to the owner to decide how to maintain the equipment, either through the help of IBM, a third-party service-provider, or by itself.

This benevolent practice is starting to change, according to DRTR.

In April 2012, IBM started requiring customers to sign a license in order to access machine code updates. Then, in October of that year, the company announced that machine code updates would only be available for those customers with IBM equipment that was either under warranty or covered by an IBM maintenance agreement.

"Fix Central downloads are available only for IBM clients with hardware or software under warranty, maintenance contracts, or subscription and support," stated the Fix Central site documentation.

Nor would IBM offer the fixes on a time-and-material contract, in which customers can go through a special bid process to buy annual access to machine code.

The company didn't immediately start enforcing this entitlement comparison policy however -- until earlier this month. "Until August, it didn't appear that IBM had the capability," Gordon-Byrne said. "We were wondering when they were going to do that step."

The policy seems to apply to all IBM mainframes, servers and storage systems, with IBM X system servers being one known exception. Customer complaints forced IBM to halt the practice for X servers, according to Gordon-Byrne.

This practice is problematic to IBM customers for a number of reasons, DRTR asserted.

Such a practice limits the resale of hardware, because any prospective owner of used equipment would have to purchase a support contract from IBM if it wanted its newly acquired machine updated.

And this could be expensive. IBM also announced last year it would start charging a "re-establishment fee" for equipment owners wishing to sign a new maintenance contract for equipment with lapsed IBM support coverage. The fee could be as high as 150 percent of the yearly maintenance fee itself, according to DRTR.

IBM could also use the maintenance contracts as a way to generate more sales.


View the original article here

IBM starts restricting hardware patches to paying customers

Following through on a policy change announced in 2012, IBM has started restricting availability of hardware patches to paying customers, spurring at least one advocacy group to accuse the company of anticompetitive practices.

IBM “is getting to the spot where the customer has no choice but to buy an IBM maintenance agreement or lose access to patches and changes,” said Gay Gordon-Byrne, executive director of the Digital Right to Repair (DRTR), a coalition for championing the rights of digital equipment owners.

Such a practice could dampen the market for support service of IBM equipment from non-IBM contractors, and could diminish the resale value of IBM equipment, DRTR charged.

On Aug. 11, IBM began requiring visitors of the IBM Fix Central website to provide a serial number in order to download a patch or update. According to DRTR, IBM uses the serial number to check to see if the machine being repaired was under a current IBM maintenance contract, or under an IBM hardware warranty.

“IBM will take the serial number, validate it against its maintenance contract database, and allow [user ] to proceed or not,” Gordon-Byrne explained.

Traditionally, IBM has freely provided machine code patches and updates as a matter of quality control, Gordon-Byrne said. The company left it to the owner to decide how to maintain the equipment, either through the help of IBM, a third-party service-provider, or by itself.

This benevolent practice is starting to change, according to DRTR.

In April 2012, IBM started requiring customers to sign a license in order to access machine code updates. Then, in October of that year, the company announced that machine code updates would only be available for those customers with IBM equipment that was either under warranty or covered by an IBM maintenance agreement.

“Fix Central downloads are available only for IBM clients with hardware or software under warranty, maintenance contracts, or subscription and support,” stated the Fix Central site documentation.

Nor would IBM offer the fixes on a time-and-material contract, in which customers can go through a special bid process to buy annual access to machine code.

The company didn’t immediately start enforcing this entitlement comparison policy however—until earlier this month. “Until August, it didn’t appear that IBM had the capability,” Gordon-Byrne said. “We were wondering when they were going to do that step.”

The policy seems to apply to all IBM mainframes, servers, and storage systems, with IBM X system servers being one known exception. Customer complaints forced IBM to halt the practice for X servers, according to Gordon-Byrne.

This practice is problematic to IBM customers for a number of reasons, DRTR asserted.

Such a practice limits the resale of hardware, because any prospective owner of used equipment would have to purchase a support contract from IBM if it wanted its newly acquired machine updated.

And this could be expensive. IBM also announced last year it would start charging a “re-establishment fee” for equipment owners wishing to sign a new maintenance contract for equipment with lapsed IBM support coverage. The fee could be as high as 150 percent of the yearly maintenance fee itself, according to DRTR.

IBM could also use the maintenance contracts as a way to generate more sales.

“If IBM decides it wants to jack the maintenance price in order to make a new machine sale, they can do it because there is no competition,” Gordon-Byrne said.

IBM is not the first major hardware firm to use this tactic to generate more after-market sales, according to Gordon-Byrne. Oracle adopted a similar practice for its servers after it acquired Sun Microsystems, and its considerable line of hardware, in 2010.

The Service Industry Association—which focuses on helping the computer, medical and business products service industries— created DRTR in January 2013 to fight against encroaching after-market control of hardware manufacturers. The SIA itself protested Oracle’s move away from free patches as well.

DRTR is actively tracking a number of similar cases involving after-market control of hardware, such as an Avaya antitrust trial due to start Sept. 9 in the U.S. District Court for the District of New Jersey.

IBM declined to comment for this story.

Joab Jackson covers enterprise software and general technology breaking news for the IDG News Service.
More by Joab Jackson


View the original article here

Thursday, 22 August 2013

Cyberattacks caused more Web outages than hardware failure in the EU last year

Although cyberattacks caused just 6 percent of significant outages of public electronic communications networks and services in the E.U. last year, they affected more people than hardware failure, a much more common factor in service disruptions, according to a report from the European Union Agency for Network and Information Security (ENISA).

Hardware failure accounted for 38 percent of all incidents and affected over 1.4 million users on average according to an annual incidents report released Tuesday by ENISA. By comparison, incidents that resulted from cyberattacks affected 1.8 million users on average.

Cyberattacks affected primarily Internet access and were the second most common cause for outages of fixed Internet service in particular, accounting for 20 percent of those incidents, ENISA said. They also accounted for around 13 percent of incidents that disrupted mobile Internet service.

The ENISA report compiles data on 79 incidents that occurred across 18 E.U. member states in 2012 and resulted in severe outages of both mobile and fixed telephony and Internet services. ENISA defines fixed Internet and telephony services as those offered through dial-up, DSL, cable, fiber, PSTN, VoIP over DSL and other wired networks.

Providers of electronic communication services are required to report significant network security and integrity breaches to national regulatory agencies, which in turn report them to ENISA and the European Commission. Nine countries did not report any incidents for 2012 and one country hasn’t implemented reporting capabilities yet, ENISA said.

The agency organized incidents into five root cause categories, but also split them by more detailed causes. The root cause categories were system failure, third-party failure, malicious actions, human errors and natural phenomena.

The most common root cause for incidents that resulted in outages was system failure. This accounted for 76 percent of outages and included incidents caused by both hardware and software issues. Most incidents in the system failure category affected switches, including routers and local exchange points, and home location registries, ENISA said.

Third-party failures accounted for 13 percent of incidents, malicious actions accounted for 8 percent, natural phenomena for 6 percent and human errors for 5 percent. Some incidents fell into multiple categories, the agency said.

Incidents caused by natural phenomena—storms, floods, heavy snowfall, earthquakes and other natural disasters—and those caused by human error resulted in the longest outages, 36 hours and 26 hours on average, respectively. However, they affected relatively low numbers of users at 557,000 and 447,000 on average.