Subject: General Tech | May 3, 2016 - 02:09 PM | Jeremy Hellstrom
Tagged: Android, google, security
Assuming your service provider is not one of those who block Google's patches from coming to you directly you should probably charge up that device, get on WiFi and check your available updates. Any Google device running 4.4.4 or newer, including Nexus devices, will have up to 40 patches to slurp up. Many of the patches are for a vulnerability similar to the previous Stagefright exploit, apps can use the drivers from Qualcomm and NVIDIA to break into the Qualcomm TrustZone on unpatched devices. The Register provides a full list of the patches which are being pushed to Nexus and Android One devices.
"Google has today issued a bundle of 40 security patches for its Android operating system.
A dozen of the fixes correct critical vulnerabilities in versions 4.4.4 of the operating system and above. About 74 per cent of in-use Android devices run Android 4.4.4 or higher."
Here is some more Tech News from around the web:
- Nvidia, Samsung pump brakes in car-crash GPU patent rip-off race @ The Register
- Google Chrome to Internet Explorer: 'I'm the king of the world!' @ The Inquirer
- Why quantum cryptography could be a one-way street @ Nanotechweb
- Pittasoft BlackVue DR650GW-2CH Car Dashcam Review @ NikKTech
- NikKTech & GAMDIAS Game On USA - CANADA Giveaway @ NikKTech
Subject: Mobile | April 14, 2016 - 04:59 PM | Scott Michaud
Tagged: vulkan, google, android n, Android
We knew it was coming. Google was a partner of Vulkan since it launched, but support was coming at some point after the desktop launch. We expected that it would be soon, but now we know that the new graphics API is in Android N Developer Preview 2. Other platforms, like apparently the Samsung Galaxy S7, are able to ship Vulkan drivers, but it is “a part of the platform” in this Android N pre-release.
Vulkan is particularly useful for mobile because those devices tend to have many cores, but relatively slow cores, which drive a decently fast GPU. Whether the benefits end up being higher performance or just better battery life (as the CPU can downclock more and more often) depends on the application, but it can be useful for 3D applications, and eventually even 2D ones, like future Qt applications with many elements, or even web browsers (when drawing complex sites).
It's good that Google is supporting Vulkan, especially after their ban of OpenCL drivers from Nexus devices. We want a single GPU compute interface across as many platforms as possible. While Vulkan isn't as complete as OpenCL, lacking some features such as unified memory, it should be more useful than OpenGL ES compute shaders.
Subject: General Tech | April 11, 2016 - 01:30 PM | Jeremy Hellstrom
Tagged: Android, blackberry, Priv
Blackberry has abandoned the Priv, calling it somewhat of an expensive mistake not only because of the investment costs but also because it was priced well above what consumers are willing to pay for a phone. They will be developing a new Android device which is intended to sell at $400, in line with the competitions prices. This also seems to imply that the BB10 OS will no longer be actively developed at Blackberry although they have not stated that for the record. They also haven't disclosed how many Priv's were sold but considering what they told The Register and others it is likely to be well below what they had hoped. They aren't dead yet but they are certainly low on health.
"BlackBerry's CEO has used an interview with United Arab Emirates outlet The National to announce plans to move the troubled mobe-maker's Android efforts downscale."
Here is some more Tech News from around the web:
- Build Your Own GSM Base Station For Fun And Profit @ Hack a Day
- The Performance Of Ubuntu Software Running On Windows 10 With The New Linux Subsystem @ Phoronix
- What did the one Toshiba desktop SSD say to the other? Our cell size has shrunk @ The Register
- Sandberg USB Master Charger Pro Review @ NikKTech
Seeing Ryan transition from being a long-time Android user over to iOS late last year has had me thinking. While I've had hands on with flagship phones from many manufacturers since then, I haven't actually carried an Android device with me since the Nexus S (eventually, with the 4.0 Ice Cream Sandwich upgrade). Maybe it was time to go back in order to gain a more informed perspective of the mobile device market as it stands today.
So that's exactly what I did. When we received our Samsung Galaxy S7 review unit (full review coming soon, I promise!), I decided to go ahead and put a real effort forth into using Android for an extended period of time.
Full disclosure, I am still carrying my iPhone with me since we received a T-Mobile locked unit, and my personal number is on Verizon. However, I have been using the S7 for everything but phone calls, and the occasional text message to people who only has my iPhone number.
Now one of the questions you might be asking yourself right now is why did I choose the Galaxy S7 of all devices to make this transition with. Most Android aficionados would probably insist that I chose a Nexus device to get the best experience and one that Google intends to provide when developing Android. While these people aren't wrong, I decided that I wanted to go with a more popular device as opposed to the more niche Nexus line.
Whether you Samsung's approach or not, the fact is that they sell more Android devices than anyone else and the Galaxy S7 will be their flagship offering for the next year or so.
Subject: Mobile | March 9, 2016 - 02:22 PM | Scott Michaud
Tagged: pixel c, nexus 6p, nexus 6, nexus 5x, google, android n, Android
With basically zero warning, Google has released Android N previews for the Nexus 5X, the Nexus 6, the Nexus 6P, the Nexus 9, the Nexus Player, and the Pixel C. It can be installed by flashing the OS onto the device, or by joining the Android Beta Program. Personally, I'd recommend joining the program, because then updates are pushed over-the-air. Be sure to back up your personal data, too. Almost every method of installing or removing the preview build will intentionally wipe the device. (Technically, installing from the Android Beta Program shouldn't erase user data, but errors can occur, and, even then, the device will be wiped when you leave.)
Aligning with this announcement is a discount on the Pixel C. It is only available to developers, and only within the US. Also, before I found out that Canadians were not eligible, I tried getting a code and the website seems to silently fail. It basically just refreshes and no email is sent, so Google might have pulled the plug once non-developers heard the news. Android Police believes that it only applies to the 64GB version, but Google's announcement wasn't clear on that. This would make the Pixel C available for $450 USD, which is quite cheap for a 10-inch, Tegra X1 device.
Android N will have a few user experience (UX) changes. The two most obvious ones are app splitscreen, which behaves like Windows 8's Windows Store app snapping, and “direct reply notifications,” which allows, for instance, replying to a chat message from the notification itself. Google has also moved to OpenJDK, as we mentioned during the holidays. This is an Oracle-approved, open-source implementation of Java that can be freely used.
Subject: Mobile | February 26, 2016 - 12:04 PM | Sebastian Peak
Tagged: windows phone, Project Astoria, microsoft, developers, build 2015, Android
A smartphone is nothing without a large selection of quality apps these days, and to that end it seemed Microsoft was going to follow the BlackBerry OS 10 method (injecting life into a platform barren of software by borrowing Android apps) when they announced the "Windows Bridge for Android" last year.
(Image credit: Microsoft)
Blackberry accomplished this by adding the Amazon app store to OS 10, which gave BB users at least some of the apps an Android user has access to via Google Play. BlackBerry also provided devs tools to help them convert Android apps to run on the BB 10 OS platform, but the market share of BB OS 10 just isn’t high enough to justify many doing this.
Microsoft appeared to be headed in this direction when they introduced Project Astoria at last year’s Build conference, which was going to enable devs to bring Android apps over to the Windows mobile OS. Well, that’s over. In an update published yesterday by Kevin Gallo, Microsoft’s Director of Windows Developer Platform, this news was spun positively (of course).
“We also announced the Windows Bridge for Android (project “Astoria”) at Build last year, and some of you have asked about its status. We received a lot of feedback that having two Bridge technologies to bring code from mobile operating systems to Windows was unnecessary, and the choice between them could be confusing. We have carefully considered this feedback and decided that we would focus our efforts on the Windows Bridge for iOS and make it the single Bridge option for bringing mobile code to all Windows 10 devices, including Xbox and PCs. For those developers who spent time investigating the Android Bridge, we strongly encourage you to take a look at the iOS Bridge and Xamarin as great solutions.”
To editoralize here a bit, I will add that I own a Lumia smartphone, and in my experience Windows Phone is an innovative and extremely efficient mobile OS. However, the lack of quality apps (and the non-existent updates for those that do exist) is too great a barrier to use a Windows Phone as my primary device. It’s telling that BlackBerry's latest smartphone, the Priv, runs Android, as BlackBerry has effectively given up trying to compete with their own OS.
BlackBerry Priv, which runs the Android 5 OS (image credit: BlackBerry)
Microsoft seems unwilling to do this, but they are a software company first and foremost and that's not surprising. But as a hardware company they have struggled with portable devices, as we saw with the ill-fated Kin smartphone, and of course the Zune music player. Android is the only realistic option if you want to compete with iOS on a smartphone, but Microsoft hasn't given up on the OS just yet. As much as I like the tiled interface, I think it's time to say goodbye to this iteration of Windows Mobile.
Subject: Mobile | February 21, 2016 - 02:52 PM | Sebastian Peak
Tagged: snapdragon 820, smartphone, qualcomm, MWC 2016, MWC, modular phone, LG G5, LG, ips, G5, Android
LG has officially unveiled their newest flagship Android handset, and in addition to high-end specs the G5 features a unique modular construction.
The LG G5
The G5 is powered by the new Snapdragon 820 SoC, and offers a 5.3-inch, 2560x1440 IPS display (making slightly smaller than the earlier G4, which was a 5.5-inch device with the same resolution). And while the G5 looks every bit a sleek Android flagship, there’s more going on here than the typical sealed handset. LG has implemented a modular design, where optional components can be added from a port on the bottom of the phone.
The LG Cam Plus (left) and Hi-Fi Plus (right)
The first of two announced modules is the LG Cam Plus, which is a camera grip that also adds 1200 mAh to the battery capacity (for a total of 4000 mAh). The second is the LG Hi-Fi Plus, which adds a high-resolution DAC and headphone amp to the phone. The headphone amp is “tuned by B&O”, and the DAC supports up to 32-bit / 384 kHz. The Hi-Fi Plus can also be used as a standalone USB device.
(Image via Android Police)
One of the features that had leaked ahead of the announcement was an always-on display, leading to speculation about the use of an OLED panel. But this is LG we are talking about, and they have implemented a high-DPI (554) IPS display instead. So how does this always-on display feature avoid aggressively draining your battery? The post from ComputerBase offers this analysis:
“Instead, the company opted for an optimization of display drivers and power management in order to realize the permanent display of notifications, time, date and other information on the large main screen. The adjustments for example it is possible to limit the backlight to a part of the screen. According to LG, the activated always-on function consumes thanks to the optimizations per hour 0.8 percent of the battery charge.”
Specs via Android Central:
- Display: 5.3-inch IPS quad-HD quantum display (2560x1440, 554 dpi)
- Processor: Snapdragon 820
- Storage: 32GB UFS ROM, microSD up to 2TB
- RAM: 4GB LPDDR4
- Rear camera: 16MP main, 8MP wide-angle (135 degrees)
- Front camera: 8MP
- Battery: 2800 mAh removable
- Modules: LG Cam Plus (camera grip with 1100 mAh), LG Hi-Fi Plus with B&O Play
- Dimensions: 149.4 x 73.9 x 7.7mm
- Weight: 159 grams
- Networks: LTE/3G/2G
- Connectivity: Wifi 802.11a/b/g/n/ac, USB Type C, NFC, Bluetooth 4.2
- Colors: Silver/Titan/Gold/Pink
- Operating system: Android 6.0.1
There were three additional accessories announced with the phone: The 360 VR (a VR headset) 360 CAM (for creating 360-degree movies and photos) and something called the Rolling Bot (a Wi-Fi connected sphere equipped with a camera, mic, and speaker).
Ryan had hands-on time with the G5 from LG's booth at MWC 2016:
No specific pricing or release date have been announced yet, but we should know more next month when LG is expected to provide more release details.
Subject: Mobile | February 21, 2016 - 01:00 PM | Sebastian Peak
Tagged: VIBE K5 Plus, VIBE K5, Snapdragon 616, Snapdragon 415, smartphone, qualcomm, MWC 2016, MWC, Lenovo, Android
Lenovo has announced a new pair of smartphones in their VIBE series, and these offer very impressive specs considering the asking price.
The VIBE K5 will retail for $129, with the K5 Plus slightly higher at $149. What does this get you? Both are 5-inch devices, with a modest 1280x720 resolution on the standard K5, or FHD 1920x1080 on the K5 Plus. The phones are both powered by Qualcomm SoCs, with a Snapdragon 415 in the K5 (quad-core 1.4 GHz), and the faster Snapdragon 616 (8-core 1.7 GHz) in the K5 Plus.
Here’s a look at the specifications for these phones:
- Screen: 5.0” HD (1280x720) display (K5) or IPS Full HD (1920x1080) (K5 Plus)
- Processor: Qualcomm snapdragon 415 octa-core (K5) or 616 octa-core processor (K5 Plus)
- Storage: 2GB LP DDR3 RAM | 16GB eMCP built-in storage | up to 32GB microSD expandable storage support
- Graphics: Adreno 405: up to 550MHz 3D graphics accelerator
- Camera: Rear: 13MP with 5-piece lens and FHD video recording, Front: 5MP fixed-focus with 4-piece lens
- Connectivity: Dual SIM slots with 4G LTE connectivity + BT 4.1; WLAN: Wi-Fi 802.11 b/g/n, Wi-Fi hotspot
- Battery: 2750mAh interchangeable battery
- Audio: 2 x speakers, 2 x mics, 3.5 mm audio jack, Dolby Atmos
- Thickness: 8.2 mm (.32 in)
- Weight: 142 g (5 oz)
- OS: Android 5.1, Lollipop
On paper these smartphones present a compelling value reminiscent of the ASUS Zenfone 2, with the K5 Plus easily the better bargain with a 1920x1080 IPS display and octa-core processor for $149. We’ll have to wait to pass judgment until the UI performance and camera have been tested, but these new VIBE K5 phones certainly looks like a promising option.
The VIBE K5 and K5 Plus will be available in March.
Subject: Mobile | December 30, 2015 - 11:09 PM | Scott Michaud
Tagged: Android, oracle, google, Java, openjdk
The Android ecosystem was built atop a Java-like framework, although a native development kit was added later. Oracle, current owner of the Java copyrights and trademarks, was not too happy with this. The two companies, Google and Oracle, were in a legal battle for the last three-and-a-half years. The courts have not ruled overwhelmingly in favor of either side.
Google is now replacing their implementation with one that is derived from OpenJDK. Officially, this is so Google has more say in how the language evolves. This would also circumvent all legal issues, because OpenJDK is supported by Oracle, but Google is not commenting on that advantage. They are in an ongoing legal battle, so that is not surprising. It wouldn't immunize them from damages that are ruled for existing products. Changing now only limits the number of products that infringe, if it is eventually ruled illegal, and remove an awkward gap where nothing is legal until a fix is implemented.
From a performance and feature standpoint, the two JDKs are supposedly equivalent nowadays.
Subject: Editorial, Mobile, Shows and Expos | December 9, 2015 - 07:04 AM | Scott Michaud
Tagged: yahoo, mozilla, google, Firefox OS, Android
Author's Disclosure: I volunteer for Mozilla, unpaid. I've been to one of their events in 2013, but otherwise have no financial ties with them. They actually weren't aware that I was a journalist. Still, our readers should know my background when reading my editorial.
Mozilla has announced that, while Firefox OS will still be developed for “many connected devices,” the organization will stop developing and selling smartphones through carriers. Mozilla claims that the reason is because they “weren't able to offer the best user experience possible.” While the statement is generic enough to apply in a lot of contexts, I'm not sure how close to the center of that region it is.
This all occurred at the “Mozlando” conference in Florida.
Firefox OS was born when stakeholders asked Mozilla to get involved in the iOS and Android duopoly. Unlike Windows, Blackberry, and other competitors, Mozilla has a history of leveraging Web standards to topple industry giants. Rather than trying to fight the industry leaders with a better platform, and hoping that developers create enough apps to draw users over, they expanded what Web could do to dig the ground out of their competitors.
The issue is that being able to achieve high performance is different from actually achieving it. The Web, as a platform, is getting panned as slow and “memory hungry” (even though free memory doesn't make a system faster -- it's all about the overhead required to manage it). Likewise, the first few phones landed at the low end, due in part to Mozilla, the non-profit organization remember, wanting to use Firefox OS to bring computing to new areas of the world. A few hiccups here and there added another coat of paint to the Web's perception of low performance.
Granted, they couldn't compete on the high end without a successful app ecosystem if they tried. Only the most hardcore of fans would purchase a several-hundred dollar smartphone, and intend to put up with just Web apps. Likewise, when I've told people that phones run on the Web, they didn't realize we mean “primarily localhost” until it's explicitly stated. People are afraid for their data caps, even though offline experiences are actually offline and stored locally.
The Dinosaur in the Room
Then there's the last question that I have. I am a bit concerned about the organization as a whole. They seem to be trying to shed several products lately, and narrow their focus. Granted, all of these announcements occur because of the event, so there's plenty of room for coincidence. They have announced that they will drop ad tiles, which I've heard praised.
The problem is, why would they do that? Was it for good will, aligning with their non-profit values? (Update: Fixed double-negative typo) Or was it bringing in much less money than projected? If it's the latter, then how far do they need to shrink their influence, and how? Did they already over-extend, and will they need to compensate for that? Looking at their other decisions, they've downsized Firefox OS, they are thinking about spinning out Thunderbird again, and they have quietly shuttered several internal projects, like their division for skunkworks projects, called “Mozilla Labs.” Mozilla also has a division called "Mozilla Research," although that is going strong. They are continually hiring for projects like "Servo," a potential new browser engine, and "Rust," a programming language that is used for Servo and other projects.
While Mozilla is definitely stable enough, financially, to thrive in their core products, I'm concerned about how much they can do beyond that. I'm genuinely concerned that Mozilla is trying to restructure while looking like a warrior for both human rights and platforms of free expression. We will not see the books until a few months from now, so we can only speculate until then. The organization is pulling inward, though. I don't know how much of this is refocusing on the problems they can solve, or the problems they can afford. We will see.