Wednesday, April 24, 2013

Android and Me

Android and Me

AOSP stock Android available now for Sony Xperia Z

Posted: 23 Apr 2013 02:32 PM PDT

Sony’s willingness to support third-party developers and hackers is well known at this point. Just some months ago, with support from Google, Sony more or less turned the Xperia S into a Nexus smartphone. They provided all the binaries they could for the device, along with a developmental AOSP, stock Android, build for developers to play around with. Unfortunately, Google backed away from the project within a short time, and the Xperia S never became a bonafide AOSP managed device. But that didn’t stop Sony from keeping all the necessary files to run stock Android available on their github page.

Announced today on their developer blog, Sony is now doing the same thing with their latest flagship smartphone, and has released an AOSP build for the 5-inch 1080p Xperia Z, complete with as many binaries as they can possibly supply. Sony was able to provide the necessary files to get the SD-card, Wi-Fi, Bluetooth, GPS, LED light, and most sensors working, but cannot provide the binaries for the camera or modem. Although they do have both working well internally.

Because of the broken modem and camera support, along with a handful of bugs, AOSP for the Xperia Z isn’t ready for every day use quite yet, but it could be only a matter of time. A quick look on XDA shows that the Sony released AOSP code for the Xperia S was used to make a successful ROM. There’s little reason to believe the Xperia Z won’t follow suit. All the files needed for getting AOSP up and running on your Xperia Z are located on Sony’s github, ready for contribution from developers committed to making this project daily-driver worthy.

The decision to give developers and consumers the tools needed to customize the firmware on their Xperia S was, as you would imagine, very well received. Sony was celebrated for being open minded and receptive to consumer demands. Doing the same thing with the Xperia Z seals that reputation. What do you think of Sony’s decision to release vanilla Android for their flagship devices?

    

HTC One Q&A Part 2

Posted: 23 Apr 2013 09:55 AM PDT

Several weeks ago we asked for your questions about the new HTC One, and nearly 1k people responded. We have been sifting through the comments and we hand picked a select few to feature in today's Q&A feature. Read on for Part 2 of our answers, and don’t forget to check out Part 1 if you missed it.

Question by DevCompany: How well does HTC One sync my data with Mac OS computers and how easy is it to transfer my contacts and emails from iPhone?

htc-one-transfer-content

Transferring content from an old phone is easy with the transfer tool.

Answer: HTC provides a tool to transfer data from almost any smartphone including the iPhone (models 3G, 3GS, 4, 4S, 5). For an iPhone it is easy to restore your content from an iTunes backup file. Users just need to connect their iPhone to a computer, install HTC Sync Manager, and then choose the content they want to transfer. Select content can also be transferred from an iPhone to the HTC One via Bluetooth.

For transferrring content from an Android phone to the new HTC One, users can install the HTC Transfer Tool from the Google Play Store. This Android app establishes a direct WiFi connection between the two devices and allows users to select the content they want to transfer.

Question by sandwich: What is the actual, regular-usage battery life? After all the excitement fades and you get into a regular usage pattern, does it last the whole day and then some, or do you need a charger part-way through?

Answer: Every user will see different battery life based on their location and the types of Android apps they have installed. For me, the new HTC One typically lasts 14-16 hours on a single charge. I consider myself an average user, but I keep all the radios on including Bluetooth, GPS, and WiFi.

HTC also provides an optional Power Saver mode that further extends battery life. This tool allows you to throttle the CPU power, reduce the screen brightness, turn off vibration, and puts your data connection to sleep when the screen is off.

Question by mcheung: Here is my question for HTC. Why did you decide to take away the "Recent Apps" button and just have the "Home" and "Back" buttons?

htc-one-bottom-630

The HTC One only features two buttons — back and home.

Answer: From what I understand, HTC removed the multitasking button to further simplify the phone operation for average users. Recent apps can still be opened by double-tapping the home button, and Google Now can be launched by holding down the home button.

Question by tommydaniel: With all the camera features, which new feature is your favorite?

Answer: My favorite part of the camera experience has to be Video Highlights. This feature takes all the photos, videos, and Zoes (3 second clips of video and photos) from your gallery and then automatically creates a 30 second highlight video. There are six theme packs to choose from that determine the video effects, timing of the cuts, and background music.

This is my favorite feature because the phone does all the work. You can take your new HTC One out to the park and record a bunch of video clips and photos of your family, and then watch a video of the event by the time you get back to your care. Each video file is compressed to around 10-15 MB, so they are easy to share on any social network of your choice.

I have been using Video Highlights every weekend since I got my HTC One, and I can’t wait for HTC to add some new theme packs to remix my content.

Brought to you by the new all-metal HTC One®. It’s everything your phone isn't.

htc-one-logo

    

HTC One faces Netherlands import ban due to high-amplitude microphone chip

Posted: 23 Apr 2013 07:40 AM PDT

HTC can’t seem to catch a break. Amsterdam’s district court has granted Nokia's request for an injunction against the HTC One. The phone is equipped with a high-amplitude microphone chip, developed by ST Microelectronics for Nokia, and according to court documents, Nokia and ST Microelectronics signed a contract that would give Nokia exclusive rights to the new chip for 12 months.

From what we can gather, ST Microelectronics was under the impression that Nokia only had 6 months exclusivity, starting in 2011. Since the Nokia 720 was the first mass-produced device to use the high-amplitude mic chip, the courts have ruled that Nokia still has exclusive rights to use the chip until February 2014.

Since HTC is not at fault in this situation, Amsterdam’s district court will allow HTC to sell its current supply of the HTC One in the Netherlands, but HTC will not be allowed to import any new devices equipped with the ST Microelectronics chip. With an estimated population of 16 million, the Netherlands isn’t one of HTC’s most important markets. However, we suspect HTC is already looking for another high-amplitude microphone chip supplier. The last thing HTC needs is for Nokia to cite this case as precedent in other European countries.

    

Is Google really working on a 32GB Nexus 4 with LTE for I/O?

Posted: 23 Apr 2013 06:31 AM PDT

Even though the Nexus 4 was released just some five months ago, the rumor mill is quick at work, spinning tales of new hardware set to be announced at Google I/O. Among the rumors that a new Nexus 7 will be announced, there is a recently surfaced rumor that Google is working on an updated Nexus 4 with LTE and 32GB of storage.

When Google released the Nexus 4, it was made perfectly clear that a lot of the things missing from the device were intentional. The lack of LTE and limited storage being the two most prominent issues picked at by practically everyone talking about it. Andy Rubin, then the head of Android, was quoted as saying the absence of LTE was, “tactical.”

The LTE situation across the globe is complex. To access GSM/HSPA+ speeds all over the globe, only a handful of frequencies need to be accessible to a device. The issue changes greatly with LTE, and even more so with America’s CDMA/LTE hybrid networks. If Google were to release an LTE device, how would it work?

Any LTE enabled Nexus device would most likely only work on one or two LTE networks. The most likely scenario would be Google releasing a revised Nexus 4 that works on AT&T and T-Mobile LTE. Rumors that an LTE enabled Nexus 4 would work on other carriers, or that it would include CDMA, seem far fetched.

While there is a sizable user base to be captured with CDMA devices in the US, the amount of negotiating, update hassles and AOSP headache needed outweigh the benefits. Right now, there’s simply no easy way to craft one device, and have it work everywhere.

The rumored Nexus 5, on the other hand, could be a totally different story. At Mobile World Congress this year, Qualcomm announced the RF360; A single chip capable of working on a staggering amount of networks. Everything from GSM, to EV-DO, to LTE. Unfortunately, it won’t be ready until the second half of the year. Or, right around the time when the Nexus 5 is rumored to launch.

If you were hoping to see the Nexus 5 at Google I/O, you shouldn’t hold your breath. Rumors on the Nexus 5 have been swirling for over a month now, but the timing is a bit off. Google still has a lot of life left in the Nexus 4, especially if this latest rumor comes true, and it’s updated with access to AT&T and T-Mobile LTE.

As for the Motorola X Phone, it’s hard to imagine it being tacked onto Google I/O. It’s totally possible, but if the Nexus 7 and an updated Nexus 4 with LTE are announced, along with Key Lime Pie, it’s highly unlikely Google would stuff the X Phone in there as well. Even more so if it really has been pushed back to August for release.

So, to answer the question, is Google really working on a 32GB Nexus 4 with LTE for Google I/O? It’s very possible. There was a refreshed Nexus 7 released, once Google had access to cheaper radios and storage, so that may be the case with a refreshed Nexus 4. Just keep in mind, the more you add to the rumor, the less reasonable it becomes. Supporting Sprint and Verizon CDMA and LTE, along with T-Mobile, who is the only official launch partner right now, and AT&T LTE doesn’t seem feasible. And releasing more than one new device, mid-cycle, doesn’t make a whole lot of sense.

    
Posted by at 8:08 AM

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)