Yesterday, Recognized Developer rayman released a new TA Dump tool for Xperia phones that should work on all recent Xperia phones which are currently vulnerable to the Dirtycow exploit.
from xda-developers http://ift.tt/2hjhZyj
via IFTTT
mercredi 7 décembre 2016
Universal TA Backup Tool is Available for Xperia Phones
from xda-developers http://ift.tt/2hjhZyj
via IFTTT
It’s Official, Pebble has been Acquired by Fitbit
It's no secret that Pebble has been struggling when it comes to making enough money to stay afloat. Reports of this started to swirl around the tech community even before they launched the Kickstarter campaign for the Pebble 2, Time 2, and Pebble Core. The crowdfunding campaign was incredibly successful as they were able to bring in over $12 million from over 66,000 backers.
Still, the company hasn't been able to bring in enough funds to meet their own demands.
Reports of this $40 million acquisition began at the end of last month, but even then it doesn't seem like a good thing for Pebble's future. The deal was reported by some to be as low as $34 million, and even that wouldn't even be enough to cover Pebble's current debts. Some said that Fitbit will only be taking on parts of Pebble, owning some of the company's IP like their operating system, watch apps, and cloud services, while leaving them to deal with their current stock and remaining server hardware.
Now, the acquisition is official and we should expect substantial changes because of it. We're told that Pebble will no longer be promoting, manufacturing, or selling any devices. While they are telling us Pebble devices will continue to work as normal, they do make sure to say "functionality or service quality may be reduced in the future." Warranty support for Pebble watches are no longer available, and returns of Pebble.com orders that were successful before December 7th will receive full refunds.
Speaking of Pebble.com, the website will no longer be accepting or fulfilling orders (including Pebble 2 pre-orders). If you purchased your Pebble device from a retail store, you'll have to go by their return/exchange policy instead of contacting Pebble. Kickstarter backers who have yet to receive their product will receive a refund within 4-8 weeks in the form of a chargeback (with no action needed from the consumer).
from xda-developers http://ift.tt/2hiQvZJ
via IFTTT
Google is Using File-by-File Patching to Reduce App Update Size
Back in July of this year, Google announced a new method of reducing the file size of application updates. They haven been using delta algorithms since 2012 to help reduce the file size of app updates, but earlier this year they rolled out a new one. This new algorithm is called bsdiff, and it was created by Colin Percival. Their experiments showed this new algorithm was able to reduce the file size of updates by 50% or more.
This was an impressive change to how the Play Store handled application updates, but Google wasn't done there. The company did more work and more tests, and have now announced a new approach that is said to go even further. This new process is called File-by-File patching, and Google's tests show that this method can reduce the file size of application updates by 65% (on average). In some cases, this new method can reduce the file size by more than 90%.
With this new method, Google projects they will be able to save up to 6 petabytes of user data each and every day. With some only having internet access via their mobile plan, and others having a metered home internet service, this could save people a lot of data. For this to work, File-by-File patching will detect changes to the uncompressed data. So they have to decompress both the old and new files so they can compute the delta.
Then to apply the patch, they decompress the old file and apply the delta to the uncompressed content before recompressing it into the new file. In Google's testing, they used apps like Netflix, Kindle, Gmail, Google Maps and even Farm Heroes Super Saga. The new File-by-File patching would sometimes only result in a file size reduction of 8% (when compared to bsdiff), but others showed as much as 40% more than bsdiff (Netflix), which resulted in the app update being reduced by 92% compared to the original file.
Source: Android Developers Blog
from xda-developers http://ift.tt/2gCogW7
via IFTTT
Fulmics Deodexer Automates ROM Deodexing on Windows
If you wish to deodex your ROM for customization purposes, check out Fulmics Deodexer. With an easy-to-use GUI and support for deodexing ODEX and OAT files for Marshmallow and later, FulMics can automate your deodexing needs.
from xda-developers http://ift.tt/2h6dQS8
via IFTTT
Best Holiday Tech Deals Under $50
Looking for some of the best holiday deals with a budget of $50? This video will highlight the top five deals that I was able to find for a decent price. Check out the deals below with our affiliate links.
Fire Tablet 7″
Fire features a 1024 x 600 IPS display with 171 ppi for a bright display with vivid colors and whiter whites. Enjoy a great viewing experience at all angles through a combination of IPS (in-plane switching) technology and an advanced polarizing filter.
Get this deal
Echo Dot
Echo Dot is a hands-free, voice-controlled device with a small built-in speaker—it can also connect to your speakers or headphones over Bluetooth or through a 3.5 mm audio cable to deliver stereo sound to the speakers you choose. Dot connects to the Alexa Voice Service to play music, provide information, news, sports scores, weather, and more—instantly.
Get this deal
Type-C USB Flash Drive
Transfer and backup files between your smartphone, computer or tablet. Use the USB Type-C connector on one end and the USB Type-A connector on the other end to easily transfer content between devices. It also functions as a convenient content bridge between devices with a standard USB-A input and those with the new USB Type-C.
Get this deal
EMIE Portable Power Bank
The adorable kitten design makes this more than just a charger, but a friendly companion. The 10,000mAh capacity will keep your devices fully charged for more than a day. It can charge the iPhone 6 four times, the Samsung S6 two times times, and the iPad mini one time.
Get this deal
Photos Live Case
Make a Live Case you can call your own. Start with your favorite photo, choose a style, and you're done. Your Live Case comes with a companion live wallpaper that turns your screen into a personal slideshow.
from xda-developers http://ift.tt/2hgI3hY
via IFTTT
mardi 6 décembre 2016
OnePlus Invites User Opinion on Camera Blob Release on OnePlus 3
The OnePlus 3 is an almost perfect fit to fill in the void created by the lack of a Nexus release this year. You get stellar hardware at affordable price range, and an experience that does justice to this hardware. OnePlus had also released the kernel source code and device tree for the OnePlus 3 (and OnePlus 3T as well) early on, so the enthusiast community had the opportunity to really dig in.
Our forums are testimony to the love that the developer community has extended on to the OnePlus 3. With a wide variety of custom ROMs with different bases (CM, AOSP, OxygenOS and even MIUI) to choose from, the OnePlus 3 is currently the flashaholic's device with good reason.
Even after all the developer friendliness that OnePlus has recently shown to the community by fulfilling their obligations and more, they still showed interest in going on ahead. The company promised to look into improving camera performance on non-OxygenOS ROMs, and we kept inquiring about it a few times after their promise. This is what Carl had to say on the issue, from our last interview:
Mario: Do you guys have any plans on helping with the development of the camera software for Custom ROMs?
Carl: We want to, and we've been talking about internally. So there's a challenge with the camera because if we want a blob, then there are two major challenges. The first one being, the code relating to the camera is on a lot of layers, so you have something related to the camera on the framework level, something on the Android level, something on a system level. So we're gonna have to rewrite a lot of code to be able to separate it in a way that allows us to blob it. And the second reason is, if we were to blob it the result is that the speed will suffer, so the speed of the camera UX on custom ROMs will suffer. We're still trying to figure out a way of how we can release something that will help people improve the camera in their custom ROMs without making the experience become too bad. And we don't want something with our logo to have a poor experience either. So it is going to be a little bit harder than we thought, but we've been discussing this.
In a forum post at the OnePlus forums, Bradon from the OnePlus Community team has given an update to the current camera situation.
Bradon mentions that discussions are still ongoing internally on how to best manage the release. The issue at hand is that camera code is something that OEMs need to spend a lot of time and effort to develop and fine-tune, effectively making it intellectual property. The various stakeholder involved in a company would definitely not be happy if OnePlus openly distributed its IP, as that would lead to OnePlus losing its edge against all competitors, big or small, as far as the camera performance is concerned.
But at the same time, lack of camera code has led to below-average camera performance on custom ROMs. ROMs are amongst one of the main draws on the OnePlus 3 right now, so a handicap like this presents a virtual roadblock in getting the best performance out of your device.
OnePlus was contemplating releasing camera blobs instead of code directly. This would allow ROM developers to directly insert the custom software into their ROMs without directly being privy to the code intricacies. While camera quality would improve for photos and videos to come at par with the OxygenOS experience, the overall camera experience would become slower than that of OxygenOS (which could have indirect implications for the Oxygen branding).
OnePlus is unhappy about this trade-off and how this would affect user experience on the device. But they are open to discussion, so the company has posed the following questions:
Would you be interested in camera blobs given these tradeoffs? Are there any alternative solutions that might make sense for you?
If you would like to chime in the discussion and share your thoughts, head on over to the OnePlus forum thread. Make yourself heard!
from xda-developers http://ift.tt/2g6oQPB
via IFTTT
Android’s December Distribution Numbers Show Lollipop is on Top
As we start the last month of the year, we get a look at how Android is being divided up among the current active install base (which are also visiting the Google Play Store). These stats were collected during a 7-day period that ended on December 5th, and as usual, any version of Android that is less than 0.1% of the active install base will not be shown in this graph. So let's take a look at how things compare to last month's distribution numbers.
Starting with the newest version of Android, we can see that 7.x Nougat is now up to 0.4% of the active install base. This is an increase of 0.1% compared to November, and includes devices like the Pixel, Pixel XL, LG V20 (among others) and custom ROMs that are based on Android 7.x Nougat. With so many devices in the market though, a 0.1% increase is at least 1.4 million devices. So that's something to keep in mind.
Next up we have Android 6.x Marshmallow up to 26.3% of the active install base, which is an increase of 2.3% compared to last month. Then we have Android 5.x Lollipop, that is currently the king with 34% of the active install base, which is actually down 0.1% compared to November's numbers. Then there is Android 4.4.x KitKat with 24% of the active install base, which saw a drop of 1.2% when compared to last month's distribution numbers.
At the tail end we have Android 4.1.x, 4.2.x and 4.3 Jelly Bean with 12.8%, which is down from 13.7% last month. Android 4.0.x Ice Cream Sandwich only has 1.2% (down a whole 0.1%), Android 2.3.x Gingerbread is at 1.2% (also down a whole 0.1%), and then Android 2.2 Froyo is still holding strong at 0.1% of the active install base. It will be interesting to see if Android Nougat will be able to beat Marshmallow's yearly progress and hit over 26.3% by December of next year.
from xda-developers http://ift.tt/2hcYDec
via IFTTT
Inscription à :
Articles (Atom)