mardi 25 juillet 2017

Adobe to Finally Kill Flash in 2020 by Stopping Updates and Distribution of the Flash Player

This week seems to be bringing bad news for once-popular applications. Yesterday, Microsoft announced the deprecation of Paint after 32 years of service (though it’ll be offered on their application store), and today, Adobe is ringing death bells for Flash.

Adobe is planning to End-of-Life Flash by the end of 2020, as the company has now finalized plans to stop updating and distributing the Flash Player. Content creators are encouraged to migrate any existing Flash content to newer open formats like HTML5, WebGL and WebAssembly. These standards have matured over the past years and have overtaken Flash in its functionality of providing interactive and creative content on the web. Many Flash plugin capabilities have directly been integrated into browsers, thus deprecating such plugins.

This End-of-Life announcement from Adobe comes in collaboration with several technology partners like AppleFacebookGoogleMicrosoft and Mozilla. For instance, Apple offers WebKit as an alternative to Flash, stating that Apple users have been experiencing the web without Flash since a while. iOS devices never supported Flash in the first place, and users on Mac began their transition away from Flash in 2010 when Flash was no longer pre-installed. Currently, if Mac users install Flash, Safari places extensive restrictions around its use.

Similarly, Google’s Chrome will increasingly require explicit permission from users to run Flash content until support is completely removed in late 2020. Microsoft will phase out support for Flash in Microsoft Edge and Internet Explorer, culminating in the complete removal by late 2020. Microsoft Edge already requires user interaction before running any Flash content starting with the Windows 10 Creators Update, and Flash will disabled by default in both of Microsoft’s browsers by 2019. Mozilla also looks to disable Flash by default for users in 2019, and only users running the Firefox Extended Support Release will be able to continue using Flash through late 2020. Once Adobe stops with its security patches, no version of Firefox will load the plugin.

Adobe also plans to move more aggressively to EOL Flash in certain geographical areas where unlicensed and outdated versions of Flash Player are being distributed.


The death of Flash had been predicted long ago. With Adobe announcing the final timeline for its death, content creators who still utilize Flash are advised to jump ship as soon as possible.

What are your thoughts on the death of Flash? Let us know in the comments below!

Source: Adobe



from xda-developers http://ift.tt/2uyBAmj
via IFTTT

Fairphone Explains Why They Had to Stop Supporting the Fairphone 1

As a smartphone customer who spends hundreds of dollars on a new device, it always sucks to hear when the device I want to keep using is no longer receiving support. This is most commonly an issue when someone wants to keep receiving software updates as they bring in both new features as well as security patches. But it can also be in terms of hardware peripheral replacements (batteries, cases, screen protectors, chargers, etc.).

Sadly, this is what happened a couple of weeks ago when Fairphone announced they would no longer be able to continue supporting the Fairphone 1. Not only did this mean the device would no longer receive software updates (which means the device will not be updated to now-ancient Android 4.4 KitKat), but it also means that the company will no longer be selling any spare parts for the device either. With the Fairphone 1 being a modular smartphone, this can be an issue for current owners.

Last week, the CEO of Fairphone published a blog post that detailed exactly why they had to make this decision. During the launch of the Fairphone 1, the company used the hardware manufacturing partner Guohong for most of the supply chain. They decided to end this partnership after a certain period of time so Fairphone had to contact individual spare parts suppliers to ask them if they would be able to produce extra supplies for the company.

This worked for a while, but even those supply chains ended up retiring this hardware over time. They repeated this again but they eventually just became financially unable to keep this going. The company says they’ve learned a lot with the supply issues of the Fairphone 1 and hope to leverage that knowledge to help them prevent this from happening as quickly in the future. One step to ensure this is by generating more working capital and another step is to improve their planning and estimations with spare parts for the Fairphone 2.


Source: Fairphone



from xda-developers http://ift.tt/2uxKdxn
via IFTTT

Joy-Con Enabler Lets You Use Both Joy-Cons on a Rooted Android 4.1+ Device

Nintendo’s Joy-Con controllers use a standard Bluetooth connection so it’s always been possible to pair a single Joy-Con to an Android device. Where this gets tricky though is when you want to use both of them together as one controller during a gaming session. This is where Joy-Con Enabler from XDA Senior Member AnkitChowdhury comes into play. It requires root access to work but is compatible with Android 4.1+ devices including Marshmallow and Nougat. The application is free with in-app purchase and can be found in the Play Store here.

Check out Joy-Con Enabler in our Apps and Games forum



from xda-developers http://ift.tt/2eLeqVQ
via IFTTT

Motorola Moto Z2 Force is Now Official: Quad HD Display, Snapdragon 835, 2,730 mAh Battery

We’ve been talking about the Moto Z2 Force from Motorola since April of this year when rumored renders created from CAD dimensions were leaked to the public. At that time, renders claimed that the device would come with a 3.5mm headphone port but then later leaks of renders had showed this wasn’t to be the case at all. That leak also suggested it would have a 5.5″ Quad HD 18:9 display as well, but the aspect ratio wasn’t talked mentioned during the launch event in New York today.

We did learn about the Moto Z2 Force would be using the company’s ShatterShield material earlier this month when the company started sending out press invites for the event. That was indeed confirmed today and it consists of a multi-layer design that makes it durable. This also has a replaceable exterior “lens” because while it shouldn’t ever shatter, it can get scratched up so this can be replaced if yours ever gets roughed up during a drop or even during regular use.

Moto Z2 Force Back

As we learned in a leak just 5 days ago, the Moto Z2 Force is thinner than many had hoped it would be. Coming off the back of the thinner Moto Z2 Play launch a couple of months ago, the Moto Z Force successor does indeed have a thinner design. It has been confirmed that the Moto Z2 Force has a 2,730mAh battery which is a significant drop over the 3,500mAh battery we saw in the original Moto Z Force. Motorola hopes you’ll buy one of the battery pack Moto Mods if you want to add any additional battery capacity to the device.

Along with this thinner design, the company has also switched to using 7,000 series aluminum that we can see with a brushed design on the back of the phone. On the back we also see the two camera setup that had been talked about in previous rumors as well. So the round, protruding camera module consists of two 12-megapixel f/2.0 cameras that both have phase detection and laser autofocus. However, Motorola has yet to mention anything about image stabilization just yet.

One of these cameras will be shooting is regular full color while the other will only be capturing monochrome images. This is a system that we’ve seen implemented by Huawei in the past and these images are combined to give you a higher detail image. The camera application will have additional features as well including the ability to add depth-of-field effects, a “True B&W” mode, and more. Motorola devices have never been known for top of the line camera performance though, so we’ll have to wait and see if this route bodes well for them.

moto z2 force white

The company confirmed previous rumors about the Moto Z2 Force being made available to all major wireless carriers in the United States, unlike what we saw with its predecessor. It will have the Snapdragon 835 SoC powering the device with a different combination of RAM and storage depending on which country the device is sold in. This is something we had also learned in a previous rumor with devices outside the US having 6GB of RAM and 128GB of internal storage whereas the US version will have a 4GB/64GB combo.

It will ship with Bluetooth 4.2 but a future update will bring support for 5.0, early adopters will get a free Insta-Share Projector Moto Mod for a limited time, and it will be priced at around $720 (the AT&T variant will cost $810 at launch). Expect the Moto Z2 Force to go on sale starting next month on the 10th of August and pre-orders will begin later today at various retailers and carriers.


Source: The Verge

 



from xda-developers http://ift.tt/2uxS79V
via IFTTT

Latest Gov Tuner Project Update Reduces Code Size by 70%

The Gov Tuner Project was initially released back in June of last year, but recently received a big update to version 4.1. This project, thanks to XDA Senior Member Senthil360, Recognized Developer Debuffer, Recognized Developer / Contributor Paget96, and F4uzan, tries to configure your CPU governor to give you the best battery life, fluidity, and smoothness. This latest update rewrites the code from scratch, reduces the code size by 70%, increases optimization and more. You can find the full changelog for version 4.1 down below.

v4.1
- Rewritten code from scratch
- CPU detection algorithm updated
- Code size reduced by 70%, increased efficiency and better loop controls
- Values revised for all devices and profiles
- GovChanger removed (there are app alternatives)
- Profile values arranged in tables for easier access and updates
- Algorithm depended values such as target_loads added to hybrid script
- Increased optimization and overall efficiency
- Disabled loop execution by default
- Room for community involvement in future releases
Check out the updated Gov Tuner Project in our Android Software and Hacking forum



from xda-developers http://ift.tt/2v4PS0W
via IFTTT

OnePlus Explains the Cause of the OnePlus 5 911 Bug

Exactly one week ago we started seeing reports about a OnePlus 5 owner who had attempted to place a 911 emergency call, but was unable to due to a bug. Right when the person tried to call emergency services (to report a building fire), the OnePlus 5 simply rebooted. They attempted this two times in a row and the forced reboot happened both times they tried to call. This is a very dangerous bug to have on your phones as sometimes you’re only able to attempt to call one time if you’re in danger.

OnePlus was made aware of the issue and immediately started working on a fix. Two days later the team reported that the issue was found and a hotfix update was being pushed out to devices at that time. OnePlus 5 owners could wait for the OTA update notification to be pushed to their devices, or they could manually check to see if they were eligible. Because sadly, this was an incremental update and only a small number of people received the update on the first day.

The hotfix update seems to have reached most, if not all, of those who own the OnePlus 5 now and the company has started to talk about the issue at hand. In a new forum thread published earlier today, OnePlus says the issue here was “related to a modem memory usage issue.” The company says this bug was a “random occurrence” for some customers who were on a VoLTE network. And the reboot seems to have only happened when the OTDOA protocol was triggered during an emergency call.

OnePlus worked directly with Qualcomm to fix the issue since it was related to the modem (which Qualcomm provides). Incidentally, over the last week we have also seen reports from other people on Reddit about their phones (from multiple OEMs) experiencing similar issues when they tried to dial 911.


Source: OnePlus



from xda-developers http://ift.tt/2uTSmip
via IFTTT

Samsung Plans to Triple its Chip Foundry Market Share in 5 Years

While average customers know of Samsung for their finished products (smartphones, TVs, etc.), the company actually produces a lot of the components used inside these devices. One area of focus is the company’s chip foundry business which they use to produce their Exynos SoCs. Samsung competes with the likes of TSMC and Intel as one of the few who actually fabricate their own chips in-house and it looks like the South Korean tech giant is looking to expand in this area.

Samsung is the market leader when it comes to technology like AMOLED displays and memory chips, but they actually lag behind TSMC when we just look at contract manufacturing for SoCs. Current reports puts TSMC at 50.6% last year while Samsung was only able to capture 7.9% (though important clients). They’re even trailing behind the likes of Global Foundries and UMC which were reported to have 9.6% and 8.1% respectively. But this new move from Samsung shows they want to shrink that gap over the next few years.

Samsung doesn’t have any unrealistic projections either, with its Executive Vice President and head of the new Samsung foundry division, E.S. Jung, saying the company wants to become a strong #2 player in the market. If Samsung’s plans are successful, then they should easily be able to hit that goal too. Mr. Jung also says they’ll be able to keep these new factories flexible so they can increase or decrease production depending on the demands of the market.

Samsung will be able to do this by relying on memory chip lines when demand for regular chip demand is low. This is something that would benefit both Samsung and consumers as high demand for memory chips in both the smartphone and PC sectors have increased pricing significantly. Samsung’s end goal with this new expansion has them trying to obtain 25% of the chip manufacturing market over the next 5 years.


Source: Reuters



from xda-developers http://ift.tt/2eKHVHt
via IFTTT