Friday, March 2, 2018

Huawei Watch 3 is confirmed, but isn’t coming anytime soon

The original Huawei Watch was a hit and deemed by many to be the best Android Wear device on the market. While this may be the case, other companies like Motorola began to pull out of the smartwatch market or reduce their output. Despite seeing stagnating sales in recent years, a report issued by IDC stated that smartwatch sales were not only set to increase but set to double by 2021. It appears the tides are changing when it comes to smartwatches and sales are starting to pick up. As a result of increased sales and the Huawei Watch 2 being a success, Huawei's CEO Richard Yu has told TechRadar that the Huawei Watch 3 is currently in the works, but the company is taking their time with it.

When asked about the next Huawei Watch release, Yu told TechRadar, "It will come later – there's no hurry because Huawei Watch 2 sells well. We're not in a hurry, so we're launching the new watch later."

huawei smartwatch

We haven't heard anything about the new Huawei Watch 3 despite the rumor mill still remaining active for other devices. We've seen all manner of leaks in recent months, from minor to major, but none really have pertained to the smartwatch. It's likely we won't see it launch with the Huawei P20, which is going to be unveiled at the company's press event on March 27th. It seems that the earliest unveiling we may see at a big event would be at IFA 2018 in Berlin at the end of August. Huawei launched the Kirin 970 at IFA last year, so the company is no stranger to the convention.

Either way, we have confirmation that the device is being worked on even if it's not necessarily launching soon. It's also interesting to note that Motorola's statement largely has the same meaning as Huawei's, except both have temporarily left the market for different reasons. Now the only question remains will the Huawei Watch 3 be like the original or be more sports-oriented like the second iteration?


Source: TechRadar



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

Essential and Google are the best at updating their phones according to SecurityLab

As Google talks about the next billion people to get online being possible thanks to Android, many are worried about the security ramifications of these less expensive devices. As a whole, Android is a secure mobile platform, but that's only true when the devices are kept up to date with security patches. Data collected by SecurityLab shows that if security updates are important to you then you should be picking up a smartphone from either Essential or Google.

Hardly any of the major Android smartphone OEMs have shown they're capable of getting security updates out in a timely manner. Most can't even deliver the updates on time for their flagship smartphones during the entire time they're supported. This will continue being an issue for the next billion people to get online as they're more likely to be purchasing an affordable smartphone. We have yet to see a company dedicate resources to keeping these devices updated.

If you can afford it though, data from SecurityLab shows that Essential and Google are the best Android OEMs for updating devices in a timely manner. It takes them less than a week for the first device to receive the new security update, while the rest of the market can take weeks or even months. Those who have purchased their device from a carrier are still waiting months (even with Essential and Google devices) before every device on that carrier is patched and up to date.

After Essential and Google, companies like BlackBerry, Nokia, and Sony have shown they are dedicated to the cause as well. They just tend to take a week or longer before they can get that first security update out. This is likely to not be an issue for those who are just using their phones to watch YouTube videos or surf online. However, we're seeing more people handling their finances and making payments with their smartphones, so keeping these devices secure is only going to become increasingly important.


Source:@SecX13



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

Huawei P20 Lite leaked with 5.84” display and notch, will cost €370 in Spain

While we didn't get to see any new Huawei phones (we did get to see the next device in Huawei's MediaPad lineup) at the Mobile World Congress 2018, the Huawei P20 Lite has shown up in a leaked brochure from Vodafone Spain. We've already seen some leaked photos and specifications of the device, but now we have them confirmed complete with the official cost (in Spain, at least) as well.

huawei p20 lite

As you can see above, a full set of specifications are listed for the device. Firstly, the CPU appears to be the Kirin 659. It's not listed by name but the clock rates match up. The device will also have 4GB of RAM and 64GB of onboard storage. It's unknown if it will have expandable storage, but it's likely given that Huawei tends to include hybrid SIM trays in their phones. The phone will have a 3000 mAh battery and launch with Android 8.0 Oreo, meaning Project Treble support is also present. The display is 5.84-inches with 2250 x 1080 resolution, an almost 19:9 aspect ratio with a notch at the top that houses the ambient light sensor, in-call speaker, and front-facing camera. The camera hardware also suggests it will take decent photos, with a dual camera setup at the back comprising of a 16MP camera in tandem with a 2MP camera. The front camera will be a single 16MP shooter. There is a rear-mounted fingerprint sensor and it will be available in two colors: black and blue.

huawei p20 lite

The Huawei P20 Lite is said to retail at €370 but can be paid for monthly at €14.50 through Vodafone Spain. The device is looking to be just like a flagship with some cut corners, though it's unknown if the corners that were cut are the right ones. For now, it's shaping up to be a pretty stellar device. We don't know when it will actually launch, but we learned last month that it would not be launching at the Mobile World Congress, much like the LG V30+'α'.


Source: GSMArena



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

Android P May Support Blocking Calls From Unknown, Private, and Pay Phone Numbers

We're nearing the release of the first Android P Developer Preview (judging by how much activity has died down in AOSP), but there's still a few tidbits here and there of possible upcoming features in the next major version of Android. We recently learned about possible native Iris scanner support, privacy tweaks such as blocking camera and microphone access from idle apps, and much more. Now, we're seeing another feature in the works: enhanced call blocking features.

A new set of commits has shown up in the AOSP gerrit from a Sony engineer. Sony engineers have recently been behind a ton of carrier related changes in Android, such as giving the ability for carriers to define the LTE signal bars, hide the signal strength from settings, and add a national roaming toggle in settings, so it's not too surprising to see another change from them. The change this time is a lot more user friendly, though, as the commits add new features to the default dialer app: the ability to block calls from unknown numbers, private numbers, pay phones, or any numbers not in your contact list.

Android P Call Blocking Android P Call Blocking

Existing Call Blocking Feature on the Google Pixel 2 XL running Android 8.1 Oreo

Currently, you are only able to block calls on a per-number basis. The numbers that you block must be added manually, which means you basically can only block calls from unwanted numbers after-the-fact. With these new settings, however, you can restrict who is allowed to call you so you won't ever be bothered by unwanted phone calls.

Android P Call Blocking

Here are the strings for the text that will be displayed in the new blocked numbers setting in the dialer app.

Enhanced Call Blocking Features

    <!-- The name of a feature available under the Call settings. -->  <string name="phone_settings_call_blocking_txt">Call Blocking</string>  <!-- Call type to be blocked. See the explanatory text "phone_settings_number_not_in_contact_summary_txt". -->  <string name="phone_settings_number_not_in_contact_txt">Numbers not in Contacts</string>  <!-- Explanatory text under the call type "phone_settings_number_not_in_contact_txt". -->  <string name="phone_settings_number_not_in_contact_summary_txt">Block numbers that are not listed in your Contacts</string>  <!-- Call type to be blocked. See the explanatory text "phone_settings_private_num_summary_txt". This is also called Anonymous or Withheld depending on region. -->  <string name="phone_settings_private_num_txt">Private</string>  <!-- Explanatory text under the call type "phone_settings_payphone_summary_txt". -->  <string name="phone_settings_private_num_summary_txt">Block callers that do not disclose their number</string>  <!-- Call type to be blocked. See the explanatory text "phone_settings_private_num_summary_txt". -->  <string name="phone_settings_payphone_txt">Pay phone</string>  <!-- Explanatory text under the call type "phone_settings_payphone_txt". -->  <string name="phone_settings_payphone_summary_txt">Block calls from pay phones</string>  <!-- Call type to be blocked. See the explanatory text "phone_settings_unknown_summary_txt". -->  <string name="phone_settings_unknown_txt">Unknown</string>  <!-- Explanatory text under the call type "phone_settings_unknown_txt". This occurs when no caller ID information unavailable (e.g., international calls, IP phones that operators cannot identify the caller) -->  <string name="phone_settings_unknown_summary_txt">Block calls from unidentified callers</string>  <!-- Notification. Make this translation consistent with "phone_settings_call_blocking_txt". -->  <string name="phone_strings_call_blocking_turned_off_notification_title_txt">Call Blocking</string>  <!-- Notification that appears when the feature Call Blocking has been disabled. -->  <string name="phone_strings_call_blocking_turned_off_notification_text_txt">Call Blocking disabled</string>  <!-- Title of the dialog "phone_strings_emergency_call_made_dialog_text_txt". -->  <string name="phone_strings_emergency_call_made_dialog_title_txt">Emergency call made</string>  <!-- Notification details that appear when the user taps the notification "phone_strings_call_blocking_turned_off_notification_text_txt". -->  <string name="phone_strings_emergency_call_made_dialog_call_blocking_text_txt">Call Blocking has been disabled to allow emergency responders to contact you.</string>  

According to the strings, you can block phone numbers in the following contexts:

  • The phone number is not in your contacts list
  • The phone number is not disclosed by the caller (Private)
  • The phone number is from a pay phone
  • The phone number does not have any caller ID information (Unknown/Unidentified)

Call blocking is disabled if a user places an emergency call, which makes sense as it's imperative that someone in distress is able to have emergency responders reach back to them. Responding to a comment from a Googler, the Sony engineer mentions that it is an "operator requirement" for a persistent notification to be displayed telling the user that call blocking has been disabled after an emergency call, so there should be no confusion or panic from the user in these circumstances.

Android P Call Blocking

Finally, it appears that these new enhanced call blocking features will be available only if your carrier allows it, which is disappointing. We can imagine certain carriers trying to sell you these call blocking features as part of an "added value" package.

Android P Call Blocking

Ultimately, this would be a great change to Android. Although there are many free call blocking apps on the Play Store, you are basically trusting that the app isn't doing anything with your call history. With a built in feature, you wouldn't have to worry about that.

Now, keep in mind that this feature hasn't actually been merged in AOSP yet. That means it isn't confirmed to ship with Android P yet, but it's very likely that it will be. A Googler reviewing the patch states that they are "very much in favor of this change as a whole" so it will likely be merged soon. It may not show up in the first Android P Developer Preview, but as we've seen with the Android Oreo Developer Previews, it's still possible for new features to be added even if the initial preview drops before the commits are merged.



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

Thursday, March 1, 2018

Open GApps Now Supports Android 8.1 Oreo (ARM+ARM64)

GApps packages (short for Google Apps) are essential in the custom ROM development community. The reason why GApps are not bundled with custom ROMs such as LineageOS is that while LineageOS is an open-source Android distribution, Google apps are not open-source. Apps such as the Play Store, Gmail, Maps, etc, do not use the Apache or GPLv2 license. Therefore, custom ROM developers can't bundle them with their builds, as doing so presents legal challenges.

Throughout the years, many different GApps packages have been popular. ParanoidAndroid GApps used to be one of the most widely used GApps out there, but the packages were discontinued in 2015. In the same year, Open GApps sought to carry forward where ParanoidAndroid GApps had left off.

The distinguishing feature of Open GApps is that it has been completely developed by writing build scripts that allow for the automated creation of new updated packages automatically, according to the developers. Their development process is open-source, and builds are generated every (European) night.

Since its first release, Open GApps has gradually went on to become the most recommended GApps package out there. It allows users to choose from ARM, ARM64, and x86 platforms, with supported Android software versions ranging from Android 4.4 KitKat to Android Oreo.

The recent release of LineageOS 15.1 has increased user interest in custom ROMs. Recent developments in Project Treble have also meant that the development community has something to look forward to, after years of seeing an era of increasingly locked-down devices which has stifled development. The first builds of LineageOS 15.1 were released this week (based on Android 8.1 Oreo), but OpenGApps did not offer GApps for Android 8.1 Oreo (specifically, the SetupWizard was still 8.0).

This changes now as OpenGApps now offers packages for Android 8.1 Oreo for the ARM and ARM64 platforms. Android 8.1 packages for x86 and x86_64 aren't supported yet, but this should not affect most users, as very few Android devices are based on either of these two platforms.

OpenGApps warns that GApps packages for Android Oreo are still "beta quality". However, the release of GApps for Android 8.1 Oreo means that they are now compatible with Android 8.1 custom ROMs such as LineageOS 15.1. As such, users no longer have to use alternative GApps packages which aren't automatically updated. They can flash the Open GApps packages via TWRP — and it should be noted that the GApps packages must be flashed immediately after flashing a custom ROM (before rebooting to system) in order to avoid crashes.


Download OpenGApps



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

Xiaomi Redmi Note 5 launching in China with Android 8.1 Oreo

A couple of weeks ago Xiaomi launched their highly anticipated Redmi Note 5 and Redmi Note 5 Pro in India. For those curious, we went hands-on with the two new smartphones at the company's initial launch event in New Delhi. Since then we've seen a couple of flash sales happen directly from Xiaomi and Flipkart, but so far it has been limited to India. We have just learned that the Chinese smartphone OEM is getting ready to launch the device in China later this month and it looks like it will be shipping with Android 8.1 Oreo.

It was an interesting move to see the company launch the Redmi Note 5 and Redmi Note 5 Pro in India first. The country has become a critical market for the company, so it's certainly a move that makes sense from a business perspective. Now that Xiaomi has the India launch out of the way, they're preparing to bring the device to their home country of China. According to their Weibo page, it will happen later this month on March 16th.

What's more interesting about this launch is that Xiaomi looks to be shipping a newer version of Android on it. In India, the Redmi Note 5 and Redmi Note 5 Pro are both shipping with Android 7.1.1 Nougat with Xiaomi's MIUI 9.2 OEM ROM. There was talk about Android Oreo at the event but a timeline has yet to be given. However, several TENAA listings have shown that Xiaomi is getting the device certified in their home country with Android 8.1 Oreo.

Xiaomi Redmi Note 5 Android 8.1 Oreo

This move was somewhat expected as we previously reported that an update to Android 8.1 Oreo for the Redmi Note 5 Pro could bring support for Project Treble. We've seen very few smartphone OEMs update a device from Nougat to Oreo while also adding support for Project Treble. It's become cliche to say that a company wants to launch with an outdated version of Android just to prevent the implementation of Project Treble, but there are some out there who are putting the work in for their customers.

Xiaomi Redmi Note 5 Android 8.1 Oreo Xiaomi Redmi Note 5 Android 8.1 Oreo Xiaomi Redmi Note 5 Android 8.1 Oreo
Source 1: TENAA Source 2: TENAA Source 3: TENAA



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

How to Enable Face Unlock on the Xiaomi Redmi 4X

If you're running version 9.2.5.0 of the MIUI 9 Global Stable ROM on the Xiaomi Redmi 4X, then you have likely noticed that it doesn't have the Face Unlock feature available. This is a feature we recently saw announced with the launch of the Redmi Note 5 Pro (and many other Android devices as of late). However, thanks to XDA Junior Member shubhandu (and Exetron on 4pda.ru) we are now able to enable this feature on the Redmi 4X thanks to a flashable ZIP file in TWRP. So far, it has been tested and shown to be working on the Redmi 4/4X running this version of MIUI 9 and shubhandu has ported it to the Redmi Note 4 as well.


Check out this guide in our Redmi 4X forum



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