LightBlog

jeudi 26 janvier 2017

Google is Optimizing Chrome OS for use on Tablets

Google announced a couple of education-focused Chromebooks this week with one being called the Acer Chromebook Spin 11 and the other being the ASUS Chromebook Flip C213. Both of these Chromebooks are 2-in-1 convertible style devices so they can both be used in notebook or tablet form.

They were actually created with modular components in mind so that they can be repaired much more easily. This was key since they'll be used in classrooms where kids can sometimes end up damaging certain pieces of it.

We've seen this trend of more Chromebooks integrating a touch screen display on their device. This is thanks to the touch UI that Google has been working on within Chrome OS and it is incredibly useful when you think that Android applications are built with a touch UI in mind. Since all Chromebooks launched this year and going forward will be able to install Android applications from the Play Store, this is just one of the many steps that Google is taking to expand the market for its customers.

Not everyone likes to use a 2-in-1 as a tablet though since it adds bulk to the device when that isn't really necessary (as we've seen in the tablet market). So again, Google has been working on the touch UI so that the experience is better with Chrome OS. We've seen this change in the new Samsung Chromebook Pro because of how much bigger the icons in the task bar are. This isn't a big deal when people interacted with Chrome OS with a mouse and keyboard.

Google's director of product for Android and Chrome for education and enterprise, Rajen Sheth, held a conference call this week for the launch of the two new education Chromebooks. During that call Mr. Sheth did talk about these two new Chromebooks, but he also spoke about the future of Chrome OS. He's proud of the work Google has put into the touch UI of Chrome OS and says it will open up the possibilities for OEMs to launch products in a wider variety of form factors. Saying we can "expect everything from detachables to tablets based on Chrome OS down the line."

Source: The Verge



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

Google I/O Scheduled for May 17th – 19th at the Shoreline Amphitheater

CES is behind us and we are looking forward to MWC happening in Barcelona this year, but many have been wondering when details for Google I/O were going to be announced. That changed this week when the Android Developers Twitter account published a teaser.

In the tweet, Google asked you to save the date, but didn't display any date for an upcoming event. Instead it was presented as a game where you were tasked to solve 5 puzzles from 5 clues in relation to 5 different places.

Once you clicked Go, a new tab opened up to a GitHub page for the user Kzuse201. This GitHub page had one project tied to it and the README.md file talked about solving those 5 puzzles again. This project also has JavaScript named idareyou.js. You do have the option to go back to the original page, and on there you see a big magnifying glass with a location pin bouncing in the bottom right of the screen. Clicking on this location pin opened up the new tab for Kzuse201's GitHub page again.

This directs you to a Jungle in Brazil thanks to a set of coordinates hidden in side that JavaScript file. The second clue in the puzzle takes you to an unlisted YouTube video that was uploaded by the Google Developers account. The video has nothing but the sound of wind in it since it's being filmed at a beach, but when you enable the closed captions feature you get another set of coordinates. This leads you to the third puzzle which ends up at Warsaw, Poland.

The fourth puzzle links you to a riddle that has been uploaded to Pastebin, which eventually has you winding up in Thailand. Then some people in a Discord channel figured out that assigning the name of the countries to positions of a chess board gives you the text "L IN E THEATRE SHO RE AM P H I." So now we know that Google I/O 2017 will take place on May 17th, 18th and 19th, and they will be holding the event at the Shoreline Amphitheater in Mountain View, CA again.

Source: Android Police



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

mercredi 25 janvier 2017

Free Software Foundation lists a Free Phone OS as a Top Priority for 2017

At XDA-Developers, we value and encourage original development efforts of all kinds. While we won't get into the debate over the merits of open source software versus closed source, we do recognize the desire for many users to run their devices on software they know is open for public scrutiny. When we discuss open source initiatives at XDA, it is usually in the context of asking companies complying with kernel licensing agreements (for the record, OnePlus did step up and finally release kernel sources a few days ago). We also applaud Sony's commitment to supporting open source development on their devices.

However, much of the software that is crucial to the basic functionality of the device is proprietary (such as the cellular baseband), so even measures such as these won't appease those of you seeking a truly open device. Unfortunately, there really isn't a place to turn for those of you who wish to have a truly open mobile device. One derivative of Android named Replicant offers software that is entirely free and open source (FOSS), but the current lack of device support hampers any widespread usage. Although, the project is in the process of re-basing on Android Marshmallow, but it is unknown how long that would take.

Hopefully that will change with the recent announcement from the Free Software Foundation that they are putting the free phone operating system as one of their top priority for 2017. In its mission statement, the FSF mentions the crucial need for a truly free mobile phone operating system:

Smart phones are the most widely used form of personal computer today. Thus, the need for a fully free phone operating system is crucial to the proliferation of software freedom.

Specifically, the foundation mentions putting their efforts into supporting the Replicant project. Moving forward, hopefully this means we will see more contributions to the project and ultimately more modern devices supported. The biggest roadblocks will of course be somehow getting crucial, proprietary hardware components working on these devices. Software developers may find it difficult to support certain components given companies' tendencies to restrict access to their proprietary technology.


If you would like to keep up to date or get involved with the project, you can access Replicant's forum page here, contribute to its wiki here, submit any bugs you find here, or simply donate to support the cause.



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

Security Analysts Identify a Trojan that Quietly Purchase Apps, a Rootkit that takes over your Device, and Ransomware that Locks your Device

For the average user on our forums, you are probably safe from most malicious threats to your device. After all, you are more likely to be running on the latest Android version with the latest security patches thanks to the effort of developers on our forums. Furthermore, you are likely more conscious of what permissions each application requests and actively avoid applications where the permissions don't match its functionality.

But for every member here who stays on top of their own cyber security, we have friends and family who don't. You might know a few people who are still rocking those Android Jellybean or KitKat phones, or perhaps they do use the latest flagship devices but they don't really care about what applications they install so long as it works for them. For the average Android user out there with nary a care in the world as to what software they are running, they are far more likely to be susceptible to security threats. And so, malicious actors take advantage of that fact, and develop software to steal information or force unwanted purchases on an end user's device.

Fortunately, we have various security companies out there whose job it is to identify, inform, and protect users from these threats. Two such firms, Doctor Web and Check Point, have identified several threats this week that we at XDA would like to share so you can ensure your friends and family don't fall for these tricks.

While we are providing the summary of the security findings outlined by these two companies, we implore you to follow the links within to see the full list of affected applications so you can see what you will need to avoid.


An application commonly installed by the Skyfin Trojan

Skyfin Trojan

This software, identified by Doctor Web earlier this week, acts as a Trojan on your device. Masquerading as a seemingly legitimate application, this Trojan can inject additional code into the Play Store's running process in order to steal your information and subsequently make covert installations and purchases behind your back. The module can simulate many functions of a regular Play Store query, including searching, purchasing, and rating, in order to artificially inflate any Play Store app listing.

The trojan is typically found within packages from third-party (non-Google) sources on the web, such as cracked game APKs. Once installed, the Android.Skyfin.1.origin implements an additional Trojan module called Android.Skyfin.2.origin into the Play Store process so it can collect the necessary information it needs to authenticate to the Play Store on your behalf. The malicious software also sends back uniquely identifying information about your device, such as the IMEI, device model, geolocation, and system language, so it will be notified that your device has been successfully compromised.

The criminals can then direct your device to download any application of their choosing on the Play Store. The downloaded app is not actually installed, but rather stored on the external storage directory so as to avoid detection. As the malware installs itself in the system directory (using a rootkit which should be noted does not affect Android devices running Marshmallow or later), it cannot be removed without root access.


The Return of HummingBad

A malware discovered last year named HummingBad is making a return, according to Check Point. This new variant which they are naming HummingWhale seems to be much more potent than its predecessor. HummingWhale, unlike HummingBad, has found a way to hide its malicious package and has accordingly sneaked its way into the Google Play Store. Check Point identified over 20 applications that were infected by this malware, with the infected apps attaining several million installations prior to Google removing them after being notified by Check Point.

To recap, HummingBad was a malware which employed a chain-attack tactic (successively installing additional malicious packages) and a rootkit to gain elevated privileges on a user's device. The malware had widespread penetration – over 10 million victims – until third-party application stores began to catch on. But now, its successor HummingWhale has been identified in several malicious applications that were uploaded under fake Chinese pseudonyms. Check Point identified a suspiciously large asset in the APK files of these malicious apps – a 1.3MB encrypted file which is actually an APK file itself that contains the main payload of the malware.

Some of the malicious code run to collect user data

This payload acts as a dropper which downloads additional malicious packages, but also employed something new called DroidPlugin to upload apps on a virtual machine. The malicious actor's server would feed the user fake ads and apps. When the user tries to close the advertisement, the app which was already installed quietly is uploaded to the virtual machine and run as if it was running on the actual device. This generates a false referrer ID for the ad, which generates ad revenue for the malicious actor.

The developers behind HummingWhale also went further in their malicious endeavors. The malware would hide the original app downloaded from the Play Store after it was installed, and the team would use fraudulent ratings to boost the reputation of the malicious applications. In the end, it's simply not enough to rely on Play Store reviews to vouch for the authenticity of an application.


Charger Ransomware

A seemingly innocuous battery saving app, at least to the average user

The last malware that we will discuss, and which was also disclosed by Check Point, is the Charger malware. This malware was found embedded within a Play Store application called EnergyRescue. Once installed, the application mines your SMS messages and contact information. But what's most concerning is what happens after it requests (and if the user grants) administrator privileges. The ransomware locks the device and demands that you send the criminals payment if you do not want them to sell your information:

You need to pay for us, otherwise we will sell portion of your personal information on black market every 30 minutes. WE GIVE 100% GUARANTEE THAT ALL FILES WILL RESTORE AFTER WE RECEIVE PAYMENT. WE WILL UNLOCK THE MOBILE DEVICE AND DELETE ALL YOUR DATA FROM OUR SERVER!TURNING OFF YOUR PHONE IS MEANINGLESS, ALL YOUR DATA IS ALREADY STORED ON OUR SERVERS! WE STILL CAN SELLING IT FOR SPAM, FAKE, BANK CRIME etc… We collect and download all of your personal data. All information about your social networks, Bank accounts, Credit Cards. We collect all data about your friends and family.

The user is asked to send 0.2 BTC (bitcoins), roughly $180, to disable the ransomware. The ransomware seemingly does not target users living in Ukraine, Russia, or Belarus which are locations likely where the attackers may be located.

Given the permissions and possible information that the application can extract, it is of course far fetched that this ransomware can do any real damage to your well-being. However, the mere threat presented may scare an unwitting user into acquiescing to its demands. Fortunately, the malware was quickly identified by Check Point who states there is no evidence it has yet infected any devices. Google has already been notified and has removed the offending application from the Play Store as well as added the identifying strings to its own malware database.


We would like to state that we aren't suggesting that Android is insecure, or that we are trying to scare you into believing that your device may be compromised. As we mentioned in the beginning, you are likely among the group of users who are less prone to falling for these tricks, but that doesn't mean you are entirely safe. In addition, you may have friends and family who do not pay attention to what they install, so we hope that by informing you of the existence of these threats you can better identify them to keep yourself and your close ones safe from malicious attacks.



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

Samsung Confirms a Galaxy Note 8 for Release in 2017

Samsung's Galaxy Note brand took a devastating blow this year with the recall and eventually being discontinued entirely due to some battery issues. This has sparked a new trend in the Android community, and with news publications in general, where each and every Samsung phone that catches fire seemingly needs to be reported on.

Don't get me wrong, the Galaxy Note 7 issue was huge and it deserved the attention it received. But the batteries we use in our phones are not 100% safe and these defective units do pop up from time to time.

With Samsung being highlighted in headline after headline about smartphone fires, many started to speculate about what the company was going to do with the Galaxy Note brand in general. This even started some rumors that Samsung would release a variant of the Galaxy S8 that was bigger and included an S Pen so they could retain some of their Galaxy Note fans without having to use the brand name. This speculation was stretched even further with some people thinking Samsung would ditch the Galaxy Note brand entirely.

The loss of revenue from the Galaxy Note 7 debacle didn't seem to hurt Samsung's overall profits during the fourth quarter of last year. Granted, a lot of this profit is from their component, display and appliance divisions, but they still managed to bring in over $7 billion in pure profit for the quarter. CNET was able to sit down with Samsung's mobile chief, D.J. Koh recently, and they talked about how the battery issue would impact the Galaxy Note series as a whole.

Mr. Koh isn't scared and feels they can win back the trust of their customers by creating a "better, safer and very innovative Note 8." He feels the fans of the Galaxy Note series are very dedicated and that it will be too difficult to simply walk away from that segment of the market. This makes a lot of sense too considering there aren't many OEMs who currently offer a premium smartphone experience that includes a stylus.

Source: CNET



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

New Report Reveals Possible Galaxy S8 Display, Camera, & Release Date Details

We've seen a number of Galaxy S8 rumors circulating throughout the Android community, from developing a new personal assistant, to moving the fingerprint sensor to the back of the device, and aiming for IP68 water and dust resistance. The device is said to come with the largest 5.7″ display, and we've heard that Samsung will be heavily leveraging their new personal assistant feature in multiple ways with the Galaxy S8.

Now, we have a report from The Guardian who backs up some of these claims and refutes some of the other rumors we have heard about.

Many have worried about whether or not Samsung's upcoming flagship phone will ditch the 3.5mm headphone port like other OEMs have done already. Sources close to The Guardian are backing up previously leaked renders that say the 3.5mm headphone port is still there on the Galaxy S8. We've known that Samsung is investing heavily into edge-to-edge displays and this new report describes the panel on the Galaxy S8 as an "infinity display."

The new rumor claims the camera will be similar to last year's with only an incremental increase in performance. They're under the belief that 64GB will be the smallest storage size option and that Samsung is keeping the microSD card slot as well. The Galaxy S8 should have a USB Type-C port and they're carrying over the iris scanner that was debuted with the Galaxy Note 7. The Guardian is backing up the rumors about the fingerprint scanner being on the back of the Galaxy S8, but doesn't mention anything about the physical buttons transitioning to software ones.

Their sources are telling them the Galaxy S8 will be released in two different size variants, with both of them being in the range of 5 to 6 inches. This clashes with the rumors we've heard that the bigger one could be as large as 6.2″. They're even being told that the phone will be available on April 21st, but it's unclear if that is the worldwide launch date, or specific to a certain region.

Source: The Guardian



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

The Last Android Wear 2.0 Dev Preview Includes Support for iOS

We've heard rumors that Android Wear 2.0 is going to be launched next month on February 9th. We've seen this huge update to Google's wearable platform be delayed already, so it will be interesting to see if they'll get it close to this rumored launch date.

Before things can be finalized though, Google has rolled out one last developer preview build to make sure the developers have their applications ready for the official release.

As we've seen with all of these developer preview releases for Android Wear 2.0, this last one is bringing some incremental changes to the table. The biggest one that will impact developers of the Android platform is the inclusion of an update to the Wearable Support Library. If your Android Wear application is compiled with API level 25 and this support library, then it is considered ready for deployment in the Google Play Store. There are some enhancements and bug fixes included, but it does not come with any updates to the preview watch image or emulator.

As far as enhancements and bug fixes are concerned, Google tells us this update includes support for NFC HCE (Host Card Emulation). We also learn there is a way to toggle to the single-page, icon-only action drawer with this new Android Wear 2.0 update. This change provides a faster and more streamlined navigation to different views in your app. We're also seeing some changes to the ProGuard and Complication API so the new configuration means complication data container classes will no longer be obfuscated.

The last thing Google talks about in this Android Wear 2.0 developer preview update is the addition of iOS support. This means that developers can distribute your applications to iPhone-paired watches by setting the standalone=true flag in your watch app manifest. This setting will tell the Play Store that the user doesn't have to have the Android phone application in order to use yours.

Source: Android Developers Blog



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