LineageOS On the Nexus 6P

In this video, TK compares a device running CM 14.1 with a device running LineageOS. You'll be familiar with most of the features in LineageOS if you have ever used a Cyanogenmod ROM. Since this is a really early look at LineageOS, there's only a few differences that you'll find. Let's take a look at what you can expect.

Boot Animation

This video gives us a good look at the new boot animation for LineageOS.

Contributors

In the contributors section, the logo to Lineage is shown where the CM logo used to be.

Updates

This is what you will find in the updates page for Lineage.

Besides this, you'll find that everything else is about the same between the two ROMs. Stay updated with LineageOS development in the XDA forums here.

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

Hexa ROM on the Pixel XL

In this video, Miles walks us through the Hexa ROM for the Pixel XL. This is one of the first LineageOS-based ROMs for the Pixel XL. This ROM has many of the same customizations as the Pure Nexus ROM that was reviewed a while back. You will find the LineageOS installer as will as a preloaded Cyanogenmod recovery. Check out the full video to see some of the best features in this ROM.

Download this ROM for your Pixel XL from the XDA thread here:

Hexa-Project Thread

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

Photos of HTC and Under Armour’s Smartwatch Leak For the Second Time

In line with a nearly identical leak from October of last year, another Weibo user has leaked more detailed photos of an HTC-Under Armour developed smartwatch shown to be running Android Wear. HTC has been expected to release an Android Wear device for more than two years, with initial rumors being picked up as early as mid-2014.

With Android Wear 2.0 potentially launching as soon as early February, leaks demoing Android Wear running on HTC hardware could suggest that 2017 may at last be the year that HTC decides to release its first smartwatch.

Then again, it is entirely possible that the present trend of delays for their smartwatch will continue, a plausible eventuality given the fact that the device pictured is shown to be running Android Wear 1.x less than a month away from the potential release of Android 2.0.

HTC has been struggling for nearly three years to succeed in the mobile market, while simultaneously making some rather absurd and avoidable mistakes in its recent past, namely expensive and ineffective ad campaigns and several underwhelming, overpriced, and overhyped flagship releases. Given the history of HTC's Project Halfbeak smartwatch, nearly three consecutive years of development to (maybe) release a single Android Wear device is likely not the winning strategy the company needs.

While Motorola has stated that it will not be introducing a new smartwatch for the release of Android Wear 2.0, ZTE, Huawei, LG, and Google all sport official or leaked evidence of plans to unveil one or two Android Wear devices each in 2017. If HTC does indeed plan on releasing their Halfbeak device this year, they will do so in the face of heavy competition.

---

Source: Weibo Via: AndroidPolice

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

Will Smartphone Modularity Make a Return in 2017?

Last year, we saw two OEMs try their hands at smartphone modularity with pseudo-modular cases and phone add-ons. But, we also witnessed the death of the actual modular device, the project that some say had the potential to revolutionize the smartphone industry.

With Google Ara out of the picture and LG also giving up, "modularity" in smartphones only exists (in a limited capacity) on the Motorola Moto Z family.
So the discussion topic for today is:

Will smartphone modularity make a return in 2017? Will any other OEM, or even Google for its matter, venture into smartphone modularity this year? Will other OEMs also look towards adopting, and perhaps standardizing, Motorola's pseudo-modular approach on their own devices?

Let us know your thoughts in the comments below!

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

Samsung Made $7.92 Billion in Profit During Q4, Shipped 90 Million Smartphones

Samsung had quite the year throughout 2016. Not only did they spend money by taking the Galaxy Note 7 off the market, but they also had to invest money into actually getting these recalled devices shipped back to them. Many thought it spelled doom for the South Korean conglomerate but things didn't really turn out that way.

Sure, profits would have been higher if they hadn't had to deal with this recall, but the company's other flagship and various endeavors were enough to help keep the mobile division afloat.

During the 4th quarter of last year, Samsung Electronics was able to bring in 53.33 trillion won in overall revenue. Compared to the same quarter in 2015, this was actually a slight increase from 53.32 trillion won. When we look at the whole year for Samsung, their revenues reached 201.87 trillion won, which again was up from the 200.65 trillion won they brought in for 2015. Looking at just the profit portion of the financial report, we see that Samsung was able to earn 9.22 trillion won for the quarter (which is about $7.92 billion).

This was a huge increase compared to the 4th quarter in 2015 when they brought in 50.1% less than they did in 2016. Profits for the whole year of 2016 reached 29.24 trillion won and this was a modest increase compared to 2015's profits when they were able to bring in 26.41 trillion won. So yes, Samsung's mobile division did slip a little compared to what it could have done if the Galaxy Note 7 hadn't had any issues, but they were still able to do well thanks to the company's components businesses (mainly the memory and display divisions).

It's also being reported by The Korea Herald that Samsung was able to ship a total of 90 million smartphones throughout all of Q4 2016. This is in addition to the 9 million "tablet PCs" that the company shipped during the same time period. A Samsung spokesperson has been quoted as saying they're going to try and get a water and dust resistant device in both the low-end and mid-range markets sometime in the future.

Source: Samsung Newsroom

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

Low Resolution Images Allegedly Reveal LG’s Upcoming Android Wear 2.0 Smartwatches

Some have been enthusiastic about the smartphone market and what it offers consumers, but many have yet to jump on board. The Android Wear platform had a nice start with many hardware OEMs supporting it with new devices. However, we have recently saw a decline in sales as many just don't feel the need to upgrade every year to every other year.

This has left some OEMs to not focus on the platform as much, but Google is wanting to revitalize the market with a couple of new devices.

We first heard rumors of these two smartwatches toward the middle of last year. Rumors started to circulate about Google wanting to build a couple of wearables and they were said to be released sometime after the 2016 Nexus phones were (which ended up being the Pixel and Pixel XL). This was about the same time that Google was trying to get Android Wear 2.0 released to the public as well, but then we ended up seeing this big update delayed until 2017.

Google finally announced that Android Wear 2.0 was close to a public release and that we can expect it on February 9th. With us getting so close to its release, it was surprising that the only leaks we had about the devices were from renders that were published by Android Police. Yesterday though, we got a look what claim to be the upcoming smartwatches from Google that are being manufactured by LG. If true, it looks like we'll be getting two sizes to choose from when they're released.

One of these has been dubbed the LG Watch Sport, and it's the one you see in the images that is black. The smaller one looks to have a gold finish to it and that is said to be called the LG Watch Style. It's interesting that these wearables were said to be Nexus devices at first, then speculated to be branded the Pixel watches, and now seem to be carrying the regular LG Watch brand.

Source: TechnoBuffalo

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

All Chromebooks Launched in 2017 Onward will Support the Play Store

Many have been excited at the prospect of their Chromebook receiving support for Android applications installed via the Play Store. This has been huge news for those who own a Chromebook, but it's left a lot of people to wonder if their device will get the update soon.

So far, it's been limited to Chromebooks like the ASUS Chromebook Flip, Acer Chromebook R11, and the Google Chromebook Pixel, but Google says they're working to add support for many others in the future.

Sadly, this experience hasn't been perfect since it was announced. Many have reported issues with the user interface of these apps on their device and this is why many devices only support it via the Canary or Developer channels. This is also why so many developers have prevented their apps from running on these devices. They don't want to offer a poor experience to their customers, and they certainly don't want to get bad reviews for a feature that has yet to his the stable channel.

But the big question remains, will my Chrome OS device ever receive support for the Play Store and if so, when will that update happen? We don't have Google's schedule for when they plan on adding support for additional devices. Progress has seemed very slow when it comes to bringing the feature to older Chrome OS devices. But we do have some good news for anyone looking to buy a new Chromebook. Google has confirmed on their Chromium OS page that all Chromebooks launching in 2017 and after will include support for Android applications via the Play Store.

We also have a list of which Chromebooks will eventually get updated to support Android applications. At least right now, we have a list of potential devices that will receive the update. Since this whole project is still in development, this list could change at any time. Check the list below to see if your device will receive the update…

Manufacturer	Device
Acer	Chromebook 11 C740
	Chromebook 11 CB3-111 / C730 / C730E / CB3-131
	Chromebook 14 CB3-431
	Chromebook 14 for Work
	Chromebook 15 CB5-571 / C910
	Chromebook 15 CB3-531 Chromebook 15, CB3-532
	Chromebox CXI2
	Chromebase 24 Chromebook R13, CB5-312T
Asus	Chromebook C200
	Chromebook C201
	Chromebook C202SA
	Chromebook C300SA
	Chromebook C300
	Chromebox CN62
	Chromebit CS10
AOpen	Chromebox Commercial
	Chromebase Commercial 22″
Bobicus	Chromebook 11
CDI	eduGear Chromebook K Series
	eduGear Chromebook M Series
	eduGear Chromebook R Series
CTL	Chromebook J2 / J4
	N6 Education Chromebook
	J5 Convertible Chromebook
Dell	Chromebook 11 3120
	Chromebook 13 7310
Edxis	Chromebook
	Education Chromebook
Haier	Chromebook 11
	Chromebook 11e
	Chromebook 11 G2
Hexa	Chromebook Pi
HiSense	Chromebook 11
Lava	Xolo Chromebook
HP	Chromebook 11 G3 / G4 / G4 EE / G5
	Chromebook 14 G4
	Chromebook 13
Lenovo	100S Chromebook
	N20 / N20P Chromebook
	N21 Chromebook
	ThinkCentre Chromebox
	ThinkPad 11e Chromebook
	N22 / N42 Chromebook
	Thinkpad 13 Chromebook
	Thinkpad 11e Chromebook Gen 3 ThinkPad 11e Yoga Chromebook ThinkPad 11e Yoga Chromebook Gen 3
Medion	Akoya S2013
	Chromebook S2015
M&A	Chromebook
NComputing	Chromebook CX100
Nexian	Chromebook 11.6″
PCMerge	Chromebook PCM-116E
Poin2	Chromebook 11
Samsung	Chromebook 2 11″ – XE500C12
	Chromebook 3
Sector 5	E1 Rugged Chromebook
Senkatel	C1101 Chromebook
Toshiba	Chromebook 2
	Chromebook 2 (2015)
True IDC	Chromebook 11
Viglen	Chromebook 11

Source: Google

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