T-Mobile is bringing Data Stash to Simple Choice prepaid customers
With its announcement of Data Stash, T-Mobile brought some really great changes to the wireless industry. On qualifying plans, users have the ability to keep their unused data in a pool that will be saved up for an entire year. Customers can tap into the data whenever they run out of their allotment for the month, which allows users to avoid data overage charges. Up until now, T-Mobile only made Data Stash available for post-paid customers. But that’s changing today, as the Uncarrier has just announced Data Stash is making its way to prepaid customers.
Beginning Sunday, March 22nd, Data Stash will start rolling out to Simple Choice prepaid customers. Every prepaid voice customer with a qualifying Simple Choice plan will receive a Starter Stash (10GB of extra 4G LTE data). When that additional 10GB stash is used up, the customers will begin tapping into their own pools of data. The data can be used for up to a year, and after that, customers will need to start saving up again.
If you’d like a little more information on Data Stash or want to hear a bit of classic T-Mobile trash-talking, follow the source link below. Any T-Mobile prepaid customers excited for this announcement?
Samsung Galaxy S6, S6 Edge pre-ordering opens in Italy
Next month, the upcoming Galaxy S6 and Galaxy S6 Edge will be available around the world. Consumers in Italy, though, can pre-order either one of the two Samsung handsets starting today with an arrival scheduled for April 10. Opting to pre-order prior to April 30 will include a wireless charging kit at no extra cost. The Italian version of Samsung’s site shows the Galaxy S6 and Galaxy S6 Edge being offered in each of the color options announced at the devices’ debut.
Source: Samsung
Via: SamMobile
Come comment on this article: Samsung Galaxy S6, S6 Edge pre-ordering opens in Italy
Five of the hottest laptops available right now
These are some of the fastest, sexiest Windows laptops you can get your hands on right now.
Budget and practicality be damned, you want the best laptop out there. We’re showcasing some of the most eye-popping, top-of-the-line laptops currently available. A lot of these high performers will be perfect for gamers, but others aim to stay reasonably powerful while remaining insanely thin.
USB-C and BadUSB attacks: What you need to know
Apple announced the new MacBook with USB-C connector last Monday and already headlines are appearing linking it to known security issues, like BadUSB.
BadUSB is an attack that uses the way computers interface with the universal serial bus (USB) standard to try and load malware onto the machine. It’s a longstanding issue with USB in general, and nothing specific to Apple or the MacBook’s implementation of USB-C. Throwing Apple and a hot new product under the headline bus is a great way to get attention, but what’s really going on?
BadUSB is a concern for anyone that has USB port on any computer from any vendor. It’s theoretically possible for an attacker to set up malware on any USB device. That’s why you shouldn’t just grab cables or thumb drives or other peripherals from people or places you don’t know, especially if you have any reason to believe you might be a target.
The reason BadUSB is getting renewed attention for USB-C is that, on new products like the MacBook and the Chromebook Pixel, USB is also the charging port. So, BadUSB has a larger attack surface. (You’ll always be plugging into USB, not into something else like AC power or DisplayPort.)
Convenience exists in opposition to security. We know this. USB-C comes with all the advantages of being a standard, and all the disadvantages as well. Neither Apple nor Google nor anyone else can build in their own protections at the hardware level without violating the standard or potentially breaking compatibility.
Vendors, including Apple and Google, might need to adopt something like the iOS “Trust this Computer” prompt for OS X and Chrome OS. The trust prompt, which grew out of similar attacks, called Juice Jacking, means an external USB device can’t exchange data with the computer unless and until the person at that computer gives express permission for it to do so.
In the meantime, if you’re at all concerned about BadUSB, buy your own cables, adapters, and devices, keep them safe, and don’t use any cables, adapters, or devices you don’t absolutely trust. Don’t be scared or made to feel paranoid by overly sensational headlines. Be informed and avoid situations that could, even potentially, put you at risk.
Nick Arnott contributed to this article.
<!–*/
<!–*/
<!–*/
.devicebox
background-color: #5CB8DB;
border: 1px solid #E2E9EB;
float: right;
display: block;
margin: 0 0px 10px 10px;
max-width: 350px;
overflow: hidden;
width: 50%;
.devicebox h3
background: #8D98BD;
color: #fff;
font-family: “camptonmedium”,sans-serif;
font-size: 20px;
margin-bottom: 0;
margin-top: 0;
padding: 0;
text-align: center;
.devicebox h3 a
display: block;
line-height: 30px;
padding: 0 10px;
.devicebox h3 a:hover
background: #7e88aa;
text-decoration: none;
.devicebox .video
margin: auto;
border: 0px;
.devicebox p,
.entry-content .devicebox p > img,
.devicebox img
margin: 0px;
max-width: 100%;
padding: 0px;
.devicebox,
.devicebox a,
.devicebox a:active,
.devicebox a:hover,
.devicebox a:link,
.devicebox a:visited,
.devicebox p,
.devicebox ul,
.devicebox ul li,
.devicebox li
color: #fff;
.devicebox a:hover
text-decoration: underline;
.devicebox p,
.devicebox ul,
.devicebox ul li,
.devicebox li
border-width: 0px;
font-family: “camptonlight”,sans-serif;
font-size: 16px;
padding: initial;
.devicebox ul
margin: 0;
padding: 0.5em 1em 1em 30px;
.devicebox ul li
display: list-item;
.devicebox ul,
.devicebox ul li,
.devicebox li
line-height: 24px;
list-style: disc outside none;
.devicebox ul li:before
display: none;
.devicebox p ~ p
padding: 0px 15px 15px;
line-height: 1.25;
.devicebox p:first-of-type + p
padding: 15px;
.field-items p:last-of-type + .devicebox,
.slide p:last-of-type + .devicebox,
.article-body-wrap p:last-of-type + .devicebox,
.field-items p:last-of-type + .devicebox ~ .devicebox,
.slide p:last-of-type + .devicebox ~ .devicebox,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox
float: none;
margin: 0 auto 30px;
max-width: 700px;
min-height: 225px;
position: relative;
width: 100%;
.field-items p:last-of-type + .devicebox .video,
.slide p:last-of-type + .devicebox .video,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox .video,
.field-items p:last-of-type + .devicebox ~ .devicebox .video,
.slide p:last-of-type + .devicebox ~ .devicebox .video,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox .video
bottom: 0px;
left: 50%;
position: absolute;
right: 0px;
top: 30px;
.field-items p:last-of-type + .devicebox .video_iframe,
.slide p:last-of-type + .devicebox .video_iframe,
.article-body-wrap p:last-of-type + .devicebox .video_iframe,
.field-items p:last-of-type + .devicebox ~ .devicebox .video_iframe,
.slide p:last-of-type + .devicebox ~ .devicebox .video_iframe,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox .video_iframe
height: 100%;
padding: 0px;
.field-items p:last-of-type + .devicebox ul,
.slide p:last-of-type + .devicebox ul,
.article-body-wrap p:last-of-type + .devicebox ul,
.field-items p:last-of-type + .devicebox p,
.slide p:last-of-type + .devicebox p,
.article-body-wrap p:last-of-type + .devicebox p,
.field-items p:last-of-type + .devicebox ~ .devicebox ul,
.slide p:last-of-type + .devicebox ~ .devicebox ul,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox ul,
.field-items p:last-of-type + .devicebox ~ .devicebox p,
.slide p:last-of-type + .devicebox ~ .devicebox p,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox p
width: 43%;
.field-items p:last-of-type + .devicebox h3 + p,
.slide p:last-of-type + .devicebox h3 + p,
.article-body-wrap p:last-of-type + .devicebox h3 + p,
.field-items p:last-of-type + .devicebox ~ .devicebox h3 + p,
.slide p:last-of-type + .devicebox ~ .devicebox h3 + p,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox h3 + p
bottom: 0;
left: 50%;
overflow: hidden;
position: absolute;
right: 0;
top: 30px;
width: 50%
.field-items p:last-of-type + .devicebox h3 + p img,
.slide p:last-of-type + .devicebox h3 + p img,
.article-body-wrap p:last-of-type + .devicebox h3 + p img,
.field-items p:last-of-type + .devicebox ~ .devicebox h3 + p img,
.slide p:last-of-type + .devicebox ~ .devicebox h3 + p img,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox h3 + p img
float: right;
height: 100%;
width: auto;
@media all and (max-width: 500px)
.devicebox
float: none;
margin: 0;
max-width: 100%;
width: 100%;
.field-items p:last-of-type + .devicebox .video,
.slide p:last-of-type + .devicebox .video,
.article-body-wrap p:last-of-type + .devicebox .video,
.field-items p:last-of-type + .devicebox ~ .devicebox .video,
.slide p:last-of-type + .devicebox ~ .devicebox .video,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox .video
left: 0;
position: relative;
top: 0;
.field-items p:last-of-type + .devicebox .video_iframe,
.slide p:last-of-type + .devicebox .video_iframe,
.article-body-wrap p:last-of-type + .devicebox .video_iframe,
.field-items p:last-of-type + .devicebox ~ .devicebox .video_iframe,
.slide p:last-of-type + .devicebox ~ .devicebox .video_iframe,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox .video_iframe
padding-bottom: 56.25%;
.field-items p:last-of-type + .devicebox h3 + p,
.slide p:last-of-type + .devicebox h3 + p,
.article-body-wrap p:last-of-type + .devicebox h3 + p,
.field-items p:last-of-type + .devicebox ~ .devicebox h3 + p,
.slide p:last-of-type + .devicebox ~ .devicebox h3 + p,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox h3 + p
left: 0;
position: relative;
top: 0;
.field-items p:last-of-type + .devicebox ul,
.slide p:last-of-type + .devicebox ul,
.article-body-wrap p:last-of-type + .devicebox ul,
.field-items p:last-of-type + .devicebox ~ .devicebox ul,
.slide p:last-of-type + .devicebox ~ .devicebox ul,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox ul
width: auto;
/*–>*/
/*–>*/
/*–>*/
USB-C and BadUSB attacks: What you need to know
Apple announced the new MacBook with USB-C connector last Monday and already headlines are appearing linking it to known security issues, like BadUSB.
BadUSB is an attack that uses the way computers interface with the universal serial bus (USB) standard to try and load malware onto the machine. It’s a longstanding issue with USB in general, and nothing specific to Apple or the MacBook’s implementation of USB-C. Throwing Apple and a hot new product under the headline bus is a great way to get attention, but what’s really going on?
BadUSB is a concern for anyone that has USB port on any computer from any vendor. It’s theoretically possible for an attacker to set up malware on any USB device. That’s why you shouldn’t just grab cables or thumb drives or other peripherals from people or places you don’t know, especially if you have any reason to believe you might be a target.
The reason BadUSB is getting renewed attention for USB-C is that, on new products like the MacBook and the Chromebook Pixel, USB is also the charging port. So, BadUSB has a larger attack surface. (You’ll always be plugging into USB, not into something else like AC power or DisplayPort.)
Convenience exists in opposition to security. We know this. USB-C comes with all the advantages of being a standard, and all the disadvantages as well. Neither Apple nor Google nor anyone else can build in their own protections at the hardware level without violating the standard or potentially breaking compatibility.
Vendors, including Apple and Google, might need to adopt something like the iOS “Trust this Computer” prompt for OS X and Chrome OS. The trust prompt, which grew out of similar attacks, called Juice Jacking, means an external USB device can’t exchange data with the computer unless and until the person at that computer gives express permission for it to do so.
In the meantime, if you’re at all concerned about BadUSB, buy your own cables, adapters, and devices, keep them safe, and don’t use any cables, adapters, or devices you don’t absolutely trust. Don’t be scared or made to feel paranoid by overly sensational headlines. Be informed and avoid situations that could, even potentially, put you at risk.
Nick Arnott contributed to this article.
<!–*/
<!–*/
<!–*/
.devicebox
background-color: #5CB8DB;
border: 1px solid #E2E9EB;
float: right;
display: block;
margin: 0 0px 10px 10px;
max-width: 350px;
overflow: hidden;
width: 50%;
.devicebox h3
background: #8D98BD;
color: #fff;
font-family: “camptonmedium”,sans-serif;
font-size: 20px;
margin-bottom: 0;
margin-top: 0;
padding: 0;
text-align: center;
.devicebox h3 a
display: block;
line-height: 30px;
padding: 0 10px;
.devicebox h3 a:hover
background: #7e88aa;
text-decoration: none;
.devicebox .video
margin: auto;
border: 0px;
.devicebox p,
.entry-content .devicebox p > img,
.devicebox img
margin: 0px;
max-width: 100%;
padding: 0px;
.devicebox,
.devicebox a,
.devicebox a:active,
.devicebox a:hover,
.devicebox a:link,
.devicebox a:visited,
.devicebox p,
.devicebox ul,
.devicebox ul li,
.devicebox li
color: #fff;
.devicebox a:hover
text-decoration: underline;
.devicebox p,
.devicebox ul,
.devicebox ul li,
.devicebox li
border-width: 0px;
font-family: “camptonlight”,sans-serif;
font-size: 16px;
padding: initial;
.devicebox ul
margin: 0;
padding: 0.5em 1em 1em 30px;
.devicebox ul li
display: list-item;
.devicebox ul,
.devicebox ul li,
.devicebox li
line-height: 24px;
list-style: disc outside none;
.devicebox ul li:before
display: none;
.devicebox p ~ p
padding: 0px 15px 15px;
line-height: 1.25;
.devicebox p:first-of-type + p
padding: 15px;
.field-items p:last-of-type + .devicebox,
.slide p:last-of-type + .devicebox,
.article-body-wrap p:last-of-type + .devicebox,
.field-items p:last-of-type + .devicebox ~ .devicebox,
.slide p:last-of-type + .devicebox ~ .devicebox,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox
float: none;
margin: 0 auto 30px;
max-width: 700px;
min-height: 225px;
position: relative;
width: 100%;
.field-items p:last-of-type + .devicebox .video,
.slide p:last-of-type + .devicebox .video,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox .video,
.field-items p:last-of-type + .devicebox ~ .devicebox .video,
.slide p:last-of-type + .devicebox ~ .devicebox .video,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox .video
bottom: 0px;
left: 50%;
position: absolute;
right: 0px;
top: 30px;
.field-items p:last-of-type + .devicebox .video_iframe,
.slide p:last-of-type + .devicebox .video_iframe,
.article-body-wrap p:last-of-type + .devicebox .video_iframe,
.field-items p:last-of-type + .devicebox ~ .devicebox .video_iframe,
.slide p:last-of-type + .devicebox ~ .devicebox .video_iframe,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox .video_iframe
height: 100%;
padding: 0px;
.field-items p:last-of-type + .devicebox ul,
.slide p:last-of-type + .devicebox ul,
.article-body-wrap p:last-of-type + .devicebox ul,
.field-items p:last-of-type + .devicebox p,
.slide p:last-of-type + .devicebox p,
.article-body-wrap p:last-of-type + .devicebox p,
.field-items p:last-of-type + .devicebox ~ .devicebox ul,
.slide p:last-of-type + .devicebox ~ .devicebox ul,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox ul,
.field-items p:last-of-type + .devicebox ~ .devicebox p,
.slide p:last-of-type + .devicebox ~ .devicebox p,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox p
width: 43%;
.field-items p:last-of-type + .devicebox h3 + p,
.slide p:last-of-type + .devicebox h3 + p,
.article-body-wrap p:last-of-type + .devicebox h3 + p,
.field-items p:last-of-type + .devicebox ~ .devicebox h3 + p,
.slide p:last-of-type + .devicebox ~ .devicebox h3 + p,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox h3 + p
bottom: 0;
left: 50%;
overflow: hidden;
position: absolute;
right: 0;
top: 30px;
width: 50%
.field-items p:last-of-type + .devicebox h3 + p img,
.slide p:last-of-type + .devicebox h3 + p img,
.article-body-wrap p:last-of-type + .devicebox h3 + p img,
.field-items p:last-of-type + .devicebox ~ .devicebox h3 + p img,
.slide p:last-of-type + .devicebox ~ .devicebox h3 + p img,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox h3 + p img
float: right;
height: 100%;
width: auto;
@media all and (max-width: 500px)
.devicebox
float: none;
margin: 0;
max-width: 100%;
width: 100%;
.field-items p:last-of-type + .devicebox .video,
.slide p:last-of-type + .devicebox .video,
.article-body-wrap p:last-of-type + .devicebox .video,
.field-items p:last-of-type + .devicebox ~ .devicebox .video,
.slide p:last-of-type + .devicebox ~ .devicebox .video,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox .video
left: 0;
position: relative;
top: 0;
.field-items p:last-of-type + .devicebox .video_iframe,
.slide p:last-of-type + .devicebox .video_iframe,
.article-body-wrap p:last-of-type + .devicebox .video_iframe,
.field-items p:last-of-type + .devicebox ~ .devicebox .video_iframe,
.slide p:last-of-type + .devicebox ~ .devicebox .video_iframe,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox .video_iframe
padding-bottom: 56.25%;
.field-items p:last-of-type + .devicebox h3 + p,
.slide p:last-of-type + .devicebox h3 + p,
.article-body-wrap p:last-of-type + .devicebox h3 + p,
.field-items p:last-of-type + .devicebox ~ .devicebox h3 + p,
.slide p:last-of-type + .devicebox ~ .devicebox h3 + p,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox h3 + p
left: 0;
position: relative;
top: 0;
.field-items p:last-of-type + .devicebox ul,
.slide p:last-of-type + .devicebox ul,
.article-body-wrap p:last-of-type + .devicebox ul,
.field-items p:last-of-type + .devicebox ~ .devicebox ul,
.slide p:last-of-type + .devicebox ~ .devicebox ul,
.article-body-wrap p:last-of-type + .devicebox ~ .devicebox ul
width: auto;
/*–>*/
/*–>*/
/*–>*/
You’re Fired! Burn down everything in this explosive game for Windows Phone
You’re Fired! These are two words you really don’t want to hear from your boss. It’s also the title of a ridiculous game on Windows Phone that you probably shouldn’t play in front of a disgruntled coworker. You play as Jerry Canned who wants to burn down the office after being fired. It’s essentially an endless runner. Run as far as you can with gas containers without tripping into desks, fans, or drawers. It’s a free game, so there’s no harm in trying it out.
AT&T to get Samsung Galaxy S6 Active
AT&T usually gets the best phones first, and again they will get the Samsung Galaxy S6 Active. The Galaxy S6 does not carry on the tradition of being dust-proof and water-resistant like the Galaxy S5, as Samsung focused more on quality materials rather than durability. The Galaxy S6 has a metal frame with a glass front and back, similar to the Sony Xperia Z3, thus leaving is prone to the elements. The S5 was made mostly out of plastic with exception for the screen, and many reviewers focused on that as their main complaint.
According to Sammobile.com, AT&T will carry the Galaxy S6 Active(SM-G890A) which will be water-resistant and dust-proof. All of the internals will remain the same, with the exception of a larger battery(3500mAh.)
The post AT&T to get Samsung Galaxy S6 Active appeared first on AndroidGuys.
Google Now open API on its way
Do you use Google Now? Do you wish that your apps were Google Now aware? Earlier this year Google announced a list of companies it partnered with to grow Google Now outside of core Google apps. The list of companies involved is huge but it is not inclusive. If you use Pandora or Lyft it’s great. What if Lyft isn’t available in your area? What if you’re a Spotify customer? Today an announcement at SXSW by Aparna Chennapragada, Director of Product Management for Google Now, was made making full third party Google Now integration a reality. The pilot program is expanding and will include a full open API that app developers can use to tie into Google Now directly.
One of the biggest gains with this announcement has to do with the Android notification shade. More information displaying as Google Now cards means more space opened up in the notification area. The per app cards will be shown based on app usage patterns along with Google’s own special Now sauce. As of now, no major timeline for the API’s release has been scheduled. It is, however, on its way.
The post Google Now open API on its way appeared first on AndroidGuys.
You may want to take that HTC One M9 overheating report with a big grain of salt
According to a report that surfaced earlier today from Dutch website Tweakers, the HTC One M9 running the popular benchmarking app GFXBench suffers from significant overheating issues. The website measured the One M9 along with various other high-end devices through a thermal camera, and reported each of the device’s temperatures. The One M9 became significantly hotter than all the other handsets, reaching up to extreme temperatures of 55.4 degrees Celsius, or just over 131 degrees Fahrenheit. In the image provided, no other handset even comes close to the One M9’s numbers. Take a look at the image below for more information.
The report states that these high temperatures were reached only when running the benchmark app. When playing games like Asphalt 8 and Assassin’s Creed: Pirates, the temperature stayed around 42.5 degrees Celsius.
The reasoning behind this overheating issue? Most notably, the One M9 is running on Qualcomm’s Snapdragon 810 processor, which hasn’t exactly gotten the best track record for its performance since its release. Samsung ultimately decided to pass on the processor with the Galaxy S6 and S6 Edge handsets, possibly due to overheating issues that the processor has been rumored to have.
Comparatively, a few reports have also stated that the Snapdragon 810 doesn’t cause any overheating issues whatsoever. Anandtech tested the chip, and essentially said there were no overheating issues to be found. Now, of course the processor will run differently when its performing in different handsets, so the claims against overheating issues in this instance with the One M9 don’t really stand up.
Before we get too far ahead of ourselves on the processor overheating issues, there are a few other variables that come in to play. For starters, the HTC One M9 hasn’t been released yet. The handset in the test was not running even close to final software, which likely plays a big part in its overheating troubles. HTC recently delayed the launch of the One M9 in Taiwan to make some last minute software adjustments. While there’s no information on the software fixes it’s receiving, HTC is obviously still working on the handset to ensure the device’s stability.
The last thing we need to think about is the feasibility of this data. A metal device reaching temperatures of over 131 degrees could be dangerous to the human skin, and would likely be unbearable to hold for an extended period of time. By no means am I saying that the benchmark scores are inaccurate or that the temperature is wrong. But what I am saying is that HTC probably wouldn’t release a handset that overheats this much. They’ve been testing this device for months with the exact same chipset, and have presumably made adjustments where they see fit. Especially given the company’s financial standpoint in the mobile division, you’d think HTC wouldn’t overlook an issue this major.
The device we get in our hands in a few weeks will undoubtably be different from the device Tweakers is using in their report. And although the website’s findings coincide with just about everything we’ve been hearing about the Snapdragon 810, we need to withhold our judgement until we actually get our hands on the consumer-ready devices.
Alleged Xperia Z4 render shows familiar design and a few inconsistencies
Sony has been a hot topic this year in the mobile world, though admittedly for all the wrong reasons. The Xperia line has been around for years now, yet has failed to gain a mainstream following in any country but its home (Japan), where any given subway ride will inevitably turn up close to a dozen-or-more branded smartphones. One of the chief complaints the flagship Xperia Z line has endured is a bi-annual refresh rate that does little more than anger the very customers who buy the “latest and greatest.” However, word has it Sony has decided to rethink this habit.
Finally, today we have our first look at what claims to be the Xperia Z4, courtesy of OnLeaks, although there is one oddity that we’ll talk about in a little bit. First, let’s dive in and look at the leaked image (seen above). The source has claimed that the dimensions of the Z4 will be 146.3 x 71.9 x 7.2 mm thus indicating it will be a svelte product despite packing some serious hardware.
The endless supply of rumors can’t seem to conclude as to if the device will be QHD or standard Full HD, although judging from the dimensions seen here it would seem Sony has decided against a larger, 5.5-inch display. Other rumors include a new camera sensor along with the possibility of a Snapdragon 810. For additional details, please make sure to check out our rumor roundup. If the specs on the recently announced Z4 Tablet are anything to go on however, a QHD display and Snapdragon 810 will be on-board.
In terms of the phone’s design, there has already been criticism suggesting it looks too similar to the Xperia Z3, as well as the recently announced M4 Aqua. With respect to the latter there are some key differences in that the phone depicted in the leak’s top speaker (and presumably the bottom as well) are positioned along the edge of the device, the sensors’ positioning has been reversed, and it lacks the port seen on the right side of the Aqua:
Those suggesting the Z4 looks like the Z3 should re-familiarize themselves with the product in question, as if anything the Z3 looks like the Aqua:
In terms of the oddity mentioned earlier, one point must be raised about this leak: The screen simulation itself does not appear legitimate. Notice the app tray icon’s position: it’s about half-way up the phone which would suggest this device has a screen closer to 3 inches than a phablet. Still, when we examine the other recent leak claiming to be pictures of the Z4’s frame, the right-side does mesh with this new render:
On a final note, barring any dramatic changes, it’s safe to say the Xperia E4 isn’t going to be a design reference for Sony this year:
The Z4 is apparently not going to be taking any cues from the Nokia Lumia 1320-esque Xperia E4.
So there you have it. Assuming this new leak is legitimate, are there any thoughts on the design? While the product is seemingly more One M9 than it is Galaxy S6, if the camera sensor and screen quality are superior to the already-impressive paring on its predecessor, the Xperia Z4 might indeed be a phablet to watch out for. Now if only Sony could find some way to market it…
AIVAnet 