LightBlog

mardi 1 mai 2018

Here are five high-end Chromebooks in development to challenge the Pixelbook

Evidence is mounting that a new generation of Chromebooks will utilise high-end features not commonly seen in Chromebooks such as powerful CPUs, 16GB RAM, backlit keyboards, and high-resolution displays.

High-end Chromebooks are few and far between, with the Google Pixelbook being the lone device that is head-and-shoulders above the rest. Five high-performance Kaby Lake Chromebooks are currently in development that would bring competition to the Pixelbook for a much-needed refresh to the enterprise market.

When developing new Chromebooks, the Chrome OS developers speed-up progress by starting with a master board and then use variants of the board to create different flavours for different manufacturers. This is why you'll often see devices—like the education refresh we saw early 2018—come with similar specification sheets across the range. Manufacturers will sometimes source different parts (e.g. batteries from different suppliers), but the specification sheet will remain similar across that generation of Chromebooks.

We've been following a rather interesting "master board;" codename Nami. Everything about Nami and its different flavours point to high-end machines from Chrome OS's stalwart manufacturers. Here's what we know so far:

There are five flavours of Nami, developed under codenames: Akali, Nami, Pantheon, Sona, and Vayne. There are hints that Vayne is Dell's and Sona is HP's. The others are still a mystery. These five boards inherit some very interesting features from their parent board:

      • Form factor: 360° convertible. Compared to the detachable announced by HP or the tablet by Acer, this is fairly vanilla for 2018 Chromebooks.
      • Screen: 2400×1600 panel, the same as what we've seen in the Pixelbook and the forthcoming HP x2. This could change for each variant, however, as the developers are working on just one engineering platform in these early days of development. [source]
      • CPU: Nami's variants will use high-wattage Kaby Lake chips, something we can infer from the fact that they have a fan profile to keep them cool. This means that these machines will be more powerful than their fanless counterparts. [source]
      • Memory: Based on Coreboot files, we'll have both 8GB and 16GB variants.
      • Keyboard: All variants except for Akali will have backlit keyboards.
      • Storage: At this stage, it looks like Nami variants could use either standard soldered eMMC or the faster and more expensive NVMe. It's too early to say for sure. [source]

No hint yet for stylus support, but that may come later. Beyond hard specifications, we can expect them to support Linux apps out of the box (it looks like all of the new Chromebooks like the HP x2 will). They will also have Wake on Voice support for Google Assistant [source].

The specifications point to an effort to fill the gap between the $550 Samsung Chromebook Pro and the $1000+ Pixelbook, and the number of devices in development mean more than a throwaway effort at prosumer devices. Google is steadily firming its grip in the education sector but has had little limelight in the enterprise sector.

The Lenovo Thinkpad 13 Chromebook was the last enterprise Chromebook, released in 2016.

The Lenovo Thinkpad 13 Chromebook, one of the latest enterprise Chromebooks, was released in 2016. Image source: Lenovo.com

The last enterprise Chromebooks launched in 2016 to little fanfare. But with Chrome Enterprise now on the scene, the Nami family could be another effort by Google to push into the enterprise space with enticing new hardware.

Release dates aren't confirmed. Development is still in early stages so we probably won't see them before Fall/Winter 2018, just as businesses start considering purchases to squeeze in before the end of the financial year. In the meantime, we'll continue tracking the exciting developments of Nami and friends.



from xda-developers https://ift.tt/2jjpTLa
via IFTTT

Here are five high-end Chromebooks in development to challenge the Pixelbook

Evidence is mounting that a new generation of Chromebooks will utilise high-end features not commonly seen in Chromebooks such as powerful CPUs, 16GB RAM, backlit keyboards, and high-resolution displays.

High-end Chromebooks are few and far between, with the Google Pixelbook being the lone device that is head-and-shoulders above the rest. Five high-performance Kaby Lake Chromebooks are currently in development that would bring competition to the Pixelbook for a much-needed refresh to the enterprise market.

When developing new Chromebooks, the Chrome OS developers speed-up progress by starting with a master board and then use variants of the board to create different flavours for different manufacturers. This is why you’ll often see devices—like the education refresh we saw early 2018—come with similar specification sheets across the range. Manufacturers will sometimes source different parts (e.g. batteries from different suppliers), but the specification sheet will remain similar across that generation of Chromebooks.

We’ve been following a rather interesting “master board;” codename Nami. Everything about Nami and its different flavours point to high-end machines from Chrome OS’s stalwart manufacturers. Here’s what we know so far:

There are five flavours of Nami, developed under codenames: Akali, Nami, Pantheon, Sona, and Vayne. There are hints that Vayne is Dell’s and Sona is HP’s. The others are still a mystery. These five boards inherit some very interesting features from their parent board:

      • Form factor: 360° convertible. Compared to the detachable announced by HP or the tablet by Acer, this is fairly vanilla for 2018 Chromebooks.
      • Screen: 2400×1600 panel, the same as what we’ve seen in the Pixelbook and the forthcoming HP x2. This could change for each variant, however, as the developers are working on just one engineering platform in these early days of development. [source]
      • CPU: Nami’s variants will use high-wattage Kaby Lake chips, something we can infer from the fact that they have a fan profile to keep them cool. This means that these machines will be more powerful than their fanless counterparts. [source]
      • Memory: Based on Coreboot files, we’ll have both 8GB and 16GB variants.
      • Keyboard: All variants except for Akali will have backlit keyboards.
      • Storage: At this stage, it looks like Nami variants could use either standard soldered eMMC or the faster and more expensive NVMe. It’s too early to say for sure. [source]

No hint yet for stylus support, but that may come later. Beyond hard specifications, we can expect them to support Linux apps out of the box (it looks like all of the new Chromebooks like the HP x2 will). They will also have Wake on Voice support for Google Assistant [source].

The specifications point to an effort to fill the gap between the $550 Samsung Chromebook Pro and the $1000+ Pixelbook, and the number of devices in development mean more than a throwaway effort at prosumer devices. Google is steadily firming its grip in the education sector but has had little limelight in the enterprise sector.

The Lenovo Thinkpad 13 Chromebook was the last enterprise Chromebook, released in 2016.

The Lenovo Thinkpad 13 Chromebook, one of the latest enterprise Chromebooks, was released in 2016. Image source: Lenovo.com

The last enterprise Chromebooks launched in 2016 to little fanfare. But with Chrome Enterprise now on the scene, the Nami family could be another effort by Google to push into the enterprise space with enticing new hardware.

Release dates aren’t confirmed. Development is still in early stages so we probably won’t see them before Fall/Winter 2018, just as businesses start considering purchases to squeeze in before the end of the financial year. In the meantime, we’ll continue tracking the exciting developments of Nami and friends.



from xda-developers https://ift.tt/2jjpTLa
via IFTTT

Honor View 10 Development Recap: New ROMs, Kernel, and Mods to try

Earlier this year the folks over at Honor announced the Honor Open Source Program for one of their newest smartphones, the Honor View 10. This was used as a way to give back the open source community while also providing ways to encouraged well-known developers to get their hands on the new device. Since then, we’ve seen a number of community developers start to work on the device. Today, we wanted to give you a development recap for the Honor View 10 that includes some new custom ROMs, custom kernels, and a couple of mods you should try out.

Honor View 10 ROMs

First up we have a preview build of CypherOS 6.0.0, which is considered to be an extension of AOSP. The goal of the developers is to maintain the purity of Android while also offering useful features for their users. These builds are updated and released weekly with new features, stability improvements, bug fixes, and more.

Another well known custom ROM now available for the Honor View 10 is another preview build but this time it is for the AICP 13.1 custom ROM. AICP is also known as the Ice Cold Project which started on the Desire HD back in 2012. The developers here use LineageOS as a base and then toss in some tweaks and features from AOSP.

The last custom ROM we’ll be highlighting today is Cosmic-OS v3.1 – Universe, which is based on Android 8.1 Oreo and is currently in its 20th revision since release. The developers behind Cosmic-OS use AOSP as its base for this ROM and then they toss in some additional features while also working to improve both performance and battery life.

Honor View 10 Kernels & Mods

A very well known custom kernel has recently made its way to the Honor View 10 from XDA Senior Member eng.stk. Their kernel, known as blu_spark, for this device will work when running either EMUI 8.x or any Android 8.1 custom ROM. The kernel has an extensive list of features and changes including an FS fsync toggle, ARM enhanced performance, and battery patches, and more.

There are a couple of mods that we also wanted to showcase today with the first enabling a call recorder feature within the settings, Just flash the provided ZIP file within TWRP and you should see the setting option appear. There’s also a mod (with an accompanying step by step guide) that shows you how to display your current data usage within the notification panel. This mod requires you to edit a certain file with root access and then change a line of code here before you can enable the feature in the device’s settings application.



from xda-developers https://ift.tt/2FxBpLL
via IFTTT

Honor View 10 Development Recap: New ROMs, Kernel, and Mods to try

Earlier this year the folks over at Honor announced the Honor Open Source Program for one of their newest smartphones, the Honor View 10. This was used as a way to give back the open source community while also providing ways to encouraged well-known developers to get their hands on the new device. Since then, we've seen a number of community developers start to work on the device. Today, we wanted to give you a development recap for the Honor View 10 that includes some new custom ROMs, custom kernels, and a couple of mods you should try out.

Honor View 10 ROMs

First up we have a preview build of CypherOS 6.0.0, which is considered to be an extension of AOSP. The goal of the developers is to maintain the purity of Android while also offering useful features for their users. These builds are updated and released weekly with new features, stability improvements, bug fixes, and more.

Another well known custom ROM now available for the Honor View 10 is another preview build but this time it is for the AICP 13.1 custom ROM. AICP is also known as the Ice Cold Project which started on the Desire HD back in 2012. The developers here use LineageOS as a base and then toss in some tweaks and features from AOSP.

The last custom ROM we'll be highlighting today is Cosmic-OS v3.1 – Universe, which is based on Android 8.1 Oreo and is currently in its 20th revision since release. The developers behind Cosmic-OS use AOSP as its base for this ROM and then they toss in some additional features while also working to improve both performance and battery life.

Honor View 10 Kernels & Mods

A very well known custom kernel has recently made its way to the Honor View 10 from XDA Senior Member eng.stk. Their kernel, known as blu_spark, for this device will work when running either EMUI 8.x or any Android 8.1 custom ROM. The kernel has an extensive list of features and changes including an FS fsync toggle, ARM enhanced performance, and battery patches, and more.

There are a couple of mods that we also wanted to showcase today with the first enabling a call recorder feature within the settings, Just flash the provided ZIP file within TWRP and you should see the setting option appear. There's also a mod (with an accompanying step by step guide) that shows you how to display your current data usage within the notification panel. This mod requires you to edit a certain file with root access and then change a line of code here before you can enable the feature in the device's settings application.



from xda-developers https://ift.tt/2FxBpLL
via IFTTT

TV or Tablet? Developer ports Android TV to the 18.4″ Samsung Galaxy View

Tablets can come in all shapes and sizes. Most tablets fall in the 7-10-inch range, but we've seen a few that push the boundaries. The Samsung Galaxy View is firmly in that discussion. This device has a whopping 18.4-inch display. You might think the size has more in common with a TV than a tablet. That's why XDA Recognized Contributor deadman96385 brought Android TV to the device.

Developers recently brought unofficial LineageOS 15.1 to the device. Now we're seeing LineageOS 15.1 TV, which is a port of Android TV. As you can see in the photos, this is the most recent version of Android TV with the revamped UI.

There are quite a few caveats if you're interested in this. First of all, Android TV was not designed for touchscreens, so you will need a Bluetooth controller. Netflix and Google Play Movies do not work, but you can sideload the phone version of Netflix. Casting to the tablet from other devices does not work. Check out the thread below for more issues and information.

Read more at the Samsung Galaxy View forum



from xda-developers https://ift.tt/2JIzVAW
via IFTTT

BLU Settles with the FTC Over Deceptive Privacy and Data Security Violations

Amidst all of the chaos surrounding ZTE and Huawei, another Android OEM is getting caught up in the mess. BLU has agreed to a settlement with the Federal Trade Commission (FTC), over allegations of misleading consumers and allowing a third-party Chinese company to collect personal details, such as text message contents and location information without knowledge or consent. When the news first came to light back in 2016, Amazon ceased sales of all BLU products until further notice.

As a result of the settlement, the company is now required to implement a “comprehensive data security program” to help prevent unauthorized access to consumers’ personal information. They also must address security risks related to past and present smartphones in order to make amends. What’s more, the company will be subject to third-party audits of their security every 2 years for the next 20 years. They must make sure to comply with record-keeping and compliance monitoring agreements during this time.

They had contracted the company ADUPS to issue security and OS updates, which took far more information than needed from consumers’ devices. This includes text messages, real-time location data, call and text message logs with full telephone numbers, contact lists, and lists of applications used and installed. Not only that, but BLU was also accused of misleading consumers by falsely claiming that they limited third-party collection of data from users of BLU’s devices to only information needed for software updates. If that’s not bad enough, ADUPS software was often found to contain security vulnerabilities which further put consumer data at risk. BLU and its co-owner and President Samuel Ohev-Zion failed to implement appropriate security measures in order to ensure the complete safety of user data, and also failed to evaluate the security of these preinstalled applications.

Despite the ADUPS software being disabled on BLU phones through software updates in 2016, the company failed to adequately disable it on all of their devices. BLU continued to allow ADUPS to operate on its older devices without adequate oversight, meaning that many users of their devices were still at risk.


Source: FTC



from xda-developers https://ift.tt/2jkR7RW
via IFTTT

BLU Settles with the FTC Over Deceptive Privacy and Data Security Violations

Amidst all of the chaos surrounding ZTE and Huawei, another Android OEM is getting caught up in the mess. BLU has agreed to a settlement with the Federal Trade Commission (FTC), over allegations of misleading consumers and allowing a third-party Chinese company to collect personal details, such as text message contents and location information without knowledge or consent. When the news first came to light back in 2016, Amazon ceased sales of all BLU products until further notice.

As a result of the settlement, the company is now required to implement a "comprehensive data security program" to help prevent unauthorized access to consumers' personal information. They also must address security risks related to past and present smartphones in order to make amends. What's more, the company will be subject to third-party audits of their security every 2 years for the next 20 years. They must make sure to comply with record-keeping and compliance monitoring agreements during this time.

They had contracted the company ADUPS to issue security and OS updates, which took far more information than needed from consumers' devices. This includes text messages, real-time location data, call and text message logs with full telephone numbers, contact lists, and lists of applications used and installed. Not only that, but BLU was also accused of misleading consumers by falsely claiming that they limited third-party collection of data from users of BLU's devices to only information needed for software updates. If that's not bad enough, ADUPS software was often found to contain security vulnerabilities which further put consumer data at risk. BLU and its co-owner and President Samuel Ohev-Zion failed to implement appropriate security measures in order to ensure the complete safety of user data, and also failed to evaluate the security of these preinstalled applications.

Despite the ADUPS software being disabled on BLU phones through software updates in 2016, the company failed to adequately disable it on all of their devices. BLU continued to allow ADUPS to operate on its older devices without adequate oversight, meaning that many users of their devices were still at risk.


Source: FTC



from xda-developers https://ift.tt/2jkR7RW
via IFTTT