LightBlog

vendredi 7 février 2020

Lyft is testing a boatload of new safety, UI, and QoL features for drivers and passengers

Passenger safety is of utmost concern for cab aggregators and ride-sharing apps like Uber and Lyft. For this reason, the companies include a number of safety features to help passengers in case something goes awry. Earlier this year, Uber introduced 3 new safety features for riders in India in a bid to crack down on driver-related incidents in the country. Similarly, Google Maps also introduced a safety feature back in October last year which was designed to alert users whenever their cab went off route. Now, it seems like Lyft is also prepping up its app to introduce similar safety features, among other things.

According to recent tweets from renowned tipster of unreleased features Jane Manchun Wong (@wongmjane), Lyft is testing several new safety, UI, and QoL features for both riders and drivers. Here are all the new features that will be released on the Lyft app soon:

Dark Mode for Lyft on Android

Google finally rolled out a system-wide dark mode with Android 10 last year. Since then third-party developers have been working to update their apps to add this new feature. A number of popular apps like WhatsApp and Instagram have already received this functionality. And now, it seems like Lyft will receive its own dark theme soon. As seen in the tweet below, the dark mode in Lyft switches all the white elements, including those in the map, to dark gray.

The dark mode will roll out to both riders and drivers, however, there’s no information from the company regarding the release timeline yet.

Auto-arrive alert when driver is near destination

Lyft is also working on an “Auto-arrive” alert for drivers which will automatically notify riders whenever the driver is near the destination. The feature will show up in the Navigation settings on the Lyft Driver app.

Commute alert for riders

Lyft is also working on a price and traffic alert tool for riders called “Commute alert”. Once released, this feature will allow users to set a route within the app and get tariff/traffic alerts for the route. Users will be able to set a recurring alert at any given time during the day using the Repeat and Notification time sections.

Voice search for entering the ride destination

The ride-sharing app is also testing a new voice input feature which will allow riders to enter their destination using a voice command. The feature will appear as a microphone icon within the search bar. Users will be able to tap on the icon and say the name of a place or an address to enter the destination.

Background location sharing

Lift is also testing a background location sharing feature that will allow the company to make sure that rides are on track and help drivers locate riders easily. The feature will be available within the privacy settings and it will allow riders to share their location either until drop-off or until pickup. In order to ensure user privacy, Lyft will ensure that the background location is shared only when a rider requests a ride and they’ll have the option to stop location sharing at any time.

Along with all the aforementioned features, Lyft is also testing a couple of exclusive features for drivers. These include notification preferences that will allow drivers to select if they wish to receive push notifications or text messages from the app, a biometric lock to secure the app with their fingerprint, a price level indicator for the price watch tool, in-app vehicle service appointment scheduling, and a driver referral mileage bonus. Do note that none of the aforementioned features are live on the Lyft app right now and there’s no information from the company regarding a release timeline.

Source: Twitter

The post Lyft is testing a boatload of new safety, UI, and QoL features for drivers and passengers appeared first on xda-developers.



from xda-developers https://ift.tt/31yNj4A
via IFTTT
Publié par à Aucun commentaire:
Libellés : ,

Lyft is testing a boatload of new safety, UI, and QoL features for drivers and passengers

Passenger safety is of utmost concern for cab aggregators and ride-sharing apps like Uber and Lyft. For this reason, the companies include a number of safety features to help passengers in case something goes awry. Earlier this year, Uber introduced 3 new safety features for riders in India in a bid to crack down on driver-related incidents in the country. Similarly, Google Maps also introduced a safety feature back in October last year which was designed to alert users whenever their cab went off route. Now, it seems like Lyft is also prepping up its app to introduce similar safety features, among other things.

According to recent tweets from renowned tipster of unreleased features Jane Manchun Wong (@wongmjane), Lyft is testing several new safety, UI, and QoL features for both riders and drivers. Here are all the new features that will be released on the Lyft app soon:

Dark Mode for Lyft on Android

Google finally rolled out a system-wide dark mode with Android 10 last year. Since then third-party developers have been working to update their apps to add this new feature. A number of popular apps like WhatsApp and Instagram have already received this functionality. And now, it seems like Lyft will receive its own dark theme soon. As seen in the tweet below, the dark mode in Lyft switches all the white elements, including those in the map, to dark gray.

The dark mode will roll out to both riders and drivers, however, there’s no information from the company regarding the release timeline yet.

Auto-arrive alert when driver is near destination

Lyft is also working on an “Auto-arrive” alert for drivers which will automatically notify riders whenever the driver is near the destination. The feature will show up in the Navigation settings on the Lyft Driver app.

Commute alert for riders

Lyft is also working on a price and traffic alert tool for riders called “Commute alert”. Once released, this feature will allow users to set a route within the app and get tariff/traffic alerts for the route. Users will be able to set a recurring alert at any given time during the day using the Repeat and Notification time sections.

Voice search for entering the ride destination

The ride-sharing app is also testing a new voice input feature which will allow riders to enter their destination using a voice command. The feature will appear as a microphone icon within the search bar. Users will be able to tap on the icon and say the name of a place or an address to enter the destination.

Background location sharing

Lift is also testing a background location sharing feature that will allow the company to make sure that rides are on track and help drivers locate riders easily. The feature will be available within the privacy settings and it will allow riders to share their location either until drop-off or until pickup. In order to ensure user privacy, Lyft will ensure that the background location is shared only when a rider requests a ride and they’ll have the option to stop location sharing at any time.

Along with all the aforementioned features, Lyft is also testing a couple of exclusive features for drivers. These include notification preferences that will allow drivers to select if they wish to receive push notifications or text messages from the app, a biometric lock to secure the app with their fingerprint, a price level indicator for the price watch tool, in-app vehicle service appointment scheduling, and a driver referral mileage bonus. Do note that none of the aforementioned features are live on the Lyft app right now and there’s no information from the company regarding a release timeline.

Source: Twitter

The post Lyft is testing a boatload of new safety, UI, and QoL features for drivers and passengers appeared first on xda-developers.



from xda-developers https://ift.tt/31yNj4A
via IFTTT
Publié par à Aucun commentaire:
Libellés : ,

Google Chrome will soon block insecure downloads on HTTPS pages

Google recently rolled out the Chrome 80 stable update to Android and desktop. As part of the update, Google introduced a number of new features, including the auto-upgrade mixed content feature we learned about back in October last year. This new feature is part of Google’s plan to secure the web with HTTPS. Now, in a bid to make HTTPS pages even more secure, Google Chrome will also block insecure downloads on secure pages soon.

In the blog post, Google claims that insecurely downloaded files are a risk to users’ privacy and security. Such files can easily be swapped out for malware by attackers and they can also be at risk of being read by eavesdroppers. In order to address these risks, the company plans to eventually remove support for insecure downloads in Google Chrome. Blocking insecure downloads on HTTPS pages is the first step Google is taking towards this measure. This is crucial because currently Chrome doesn’t indicate users that their privacy and security are at risk while they’re downloading content on secure pages.

Google Chrome insecure downloads warning

Starting with Chrome 82, which is expected to be released in April 2020, Chrome will gradually start warning users (as seen above) about mixed content downloads. These downloads will be blocked completely at a later stage. This change will first impact file types that pose the most risk to users, like executables, and then address more file types in subsequent releases. Google claims that the gradual rollout is “designed to mitigate the worst risks quickly, provide developers an opportunity to update sites, and minimize how many warnings Chrome users have to see.”

At first, Google will roll out these restrictions on mixed content downloads on desktop platforms, starting with Chrome 81. Here’s the detailed timeline for restrictions on desktop platforms:

  • In Chrome 81 (released March 2020) and later:
    • Chrome will print a console message warning about all mixed content downloads.
  • In Chrome 82 (released April 2020):
    • Chrome will warn on mixed content downloads or executables (e.e. .exe).
  • In Chrome 83 (released June 2020):
    • Chrome will block mixed content executables
    • Chrome will warn on mixed content archives (.zip) and disk images (.iso).
  • In Chrome 84 (released August 2020):
    • Chrome will block mixed content executables, archives and disk images
    • Chrome will warn on all other mixed content downloads except image, audio, video and text formats.
  • In Chrome 85 (released September 2020):
    • Chrome will warn on mixed content downloads of images, audio, video, and text
    • Chrome will block all other mixed content downloads
  • In Chrome 86 (released October 2020) and beyond, Chrome will block all mixed content downloads.

These restrictions will be delayed by one release for Android and iOS users, with warning starting in Chrome 83. Google claims that since mobile platforms have better native protection against malicious files, the delay will give developers a head-start towards updating their websites before users are impacted. Developers can ensure that downloads only use HTTPS in case they don’t want users to ever see a download warning.

Additionally, in the current version of Chrome Canary, or in Chrome 81 once released, developers can also activate a warning on all mixed content downloads for testing by enabling the “Treat risky downloads over insecure connections as active mixed content” flag. Google plans to further restrict insecure downloads in Google Chrome in the future and to this effect, the company has urged developers to fully migrate to HTTPS in order to avoid restrictions.

Source: Google Security Blog

The post Google Chrome will soon block insecure downloads on HTTPS pages appeared first on xda-developers.



from xda-developers https://ift.tt/386tgNf
via IFTTT
Publié par à Aucun commentaire:
Libellés : ,

Google Chrome will soon block insecure downloads on HTTPS pages

Google recently rolled out the Chrome 80 stable update to Android and desktop. As part of the update, Google introduced a number of new features, including the auto-upgrade mixed content feature we learned about back in October last year. This new feature is part of Google’s plan to secure the web with HTTPS. Now, in a bid to make HTTPS pages even more secure, Google Chrome will also block insecure downloads on secure pages soon.

In the blog post, Google claims that insecurely downloaded files are a risk to users’ privacy and security. Such files can easily be swapped out for malware by attackers and they can also be at risk of being read by eavesdroppers. In order to address these risks, the company plans to eventually remove support for insecure downloads in Google Chrome. Blocking insecure downloads on HTTPS pages is the first step Google is taking towards this measure. This is crucial because currently Chrome doesn’t indicate users that their privacy and security are at risk while they’re downloading content on secure pages.

Google Chrome insecure downloads warning

Starting with Chrome 82, which is expected to be released in April 2020, Chrome will gradually start warning users (as seen above) about mixed content downloads. These downloads will be blocked completely at a later stage. This change will first impact file types that pose the most risk to users, like executables, and then address more file types in subsequent releases. Google claims that the gradual rollout is “designed to mitigate the worst risks quickly, provide developers an opportunity to update sites, and minimize how many warnings Chrome users have to see.”

At first, Google will roll out these restrictions on mixed content downloads on desktop platforms, starting with Chrome 81. Here’s the detailed timeline for restrictions on desktop platforms:

  • In Chrome 81 (released March 2020) and later:
    • Chrome will print a console message warning about all mixed content downloads.
  • In Chrome 82 (released April 2020):
    • Chrome will warn on mixed content downloads or executables (e.e. .exe).
  • In Chrome 83 (released June 2020):
    • Chrome will block mixed content executables
    • Chrome will warn on mixed content archives (.zip) and disk images (.iso).
  • In Chrome 84 (released August 2020):
    • Chrome will block mixed content executables, archives and disk images
    • Chrome will warn on all other mixed content downloads except image, audio, video and text formats.
  • In Chrome 85 (released September 2020):
    • Chrome will warn on mixed content downloads of images, audio, video, and text
    • Chrome will block all other mixed content downloads
  • In Chrome 86 (released October 2020) and beyond, Chrome will block all mixed content downloads.

These restrictions will be delayed by one release for Android and iOS users, with warning starting in Chrome 83. Google claims that since mobile platforms have better native protection against malicious files, the delay will give developers a head-start towards updating their websites before users are impacted. Developers can ensure that downloads only use HTTPS in case they don’t want users to ever see a download warning.

Additionally, in the current version of Chrome Canary, or in Chrome 81 once released, developers can also activate a warning on all mixed content downloads for testing by enabling the “Treat risky downloads over insecure connections as active mixed content” flag. Google plans to further restrict insecure downloads in Google Chrome in the future and to this effect, the company has urged developers to fully migrate to HTTPS in order to avoid restrictions.

Source: Google Security Blog

The post Google Chrome will soon block insecure downloads on HTTPS pages appeared first on xda-developers.



from xda-developers https://ift.tt/386tgNf
via IFTTT
Publié par à Aucun commentaire:
Libellés : ,

Android 11’s “Share to Print” feature will make it easier to print images and PDFs

Back in 2017, Google introduced a built-in print service on Android Oreo for printers that support the Internet Printing Protocol (IPP). Before that, users had to search for third-party print services on the Play Store in order to print something from their Android device. This change was brought about by technology contributed to AOSP by the Mopria Alliance, which was founded by Canon, HP, Samsung, and Xerox. Mopria Alliance has since played a major role in improving printing on Android devices, bringing support for WiFi Direct Printing in Android Pie. Now, an engineer from the Mopria Alliance has submitted code to AOSP which suggests that Android 11 might include a new ‘Share to Print’ feature that will simplify printing images and PDF files.

Google just merged a new commit to the Android Open Source Project (AOSP) to enable “share to print” — a feature that will give developers the ability to send an intent to the Print Service to directly print images or PDF files without the user having to manually choose a print service from the share menu. As of now, it doesn’t look like this code change will add a dedicated print button to the share menu as, in its current form, the feature is just a way to bypass the share menu and enable apps to directly send images/PDFs to the default printing service.

The code suggests that in Android 11 developers will be able to add a “print” button to their apps that directly sends an image or PDF to the user’s default printing service. This “print” button should be constructed to send an intent targeted to either the activity “com.android.bips.ImagePrintActivity” or “com.android.bips.PdfPrintActivity”, and with the action “android.intent.action.SEND”, category “android.intent.category.DEFAULT”, and data with the image or PDF file.

According to the commit description, this feature “makes[s] it easier for apps to print to any supported printer via a normal share intent.” The PrintManager handles sending content at an appropriate resolution for printing to any installed and enabled Print Service. The commit further reveals that image content “is downscaled to a good DPI for preview (screen DPI) or delivery (300 DPI).” The fit or fill options are “activated by the user’s landscape vs. portrait print attribute selection,” and photos “default to a locale-specific default photo media size.” As of now, there’s no official information from Google regarding the matter, but we expect to learn more in the weeks leading up to the first Android 11 open beta release.

Source: AOSP

The post Android 11’s “Share to Print” feature will make it easier to print images and PDFs appeared first on xda-developers.



from xda-developers https://ift.tt/31ycSmf
via IFTTT
Publié par à Aucun commentaire:
Libellés : ,

jeudi 6 février 2020

Android 11’s “Share to Print” feature will make it easier to print images and PDFs

Back in 2017, Google introduced a built-in print service on Android Oreo for printers that support the Internet Printing Protocol (IPP). Before that, users had to search for third-party print services on the Play Store in order to print something from their Android device. This change was brought about by technology contributed to AOSP by the Mopria Alliance, which was founded by Canon, HP, Samsung, and Xerox. Mopria Alliance has since played a major role in improving printing on Android devices, bringing support for WiFi Direct Printing in Android Pie. Now, an engineer from the Mopria Alliance has submitted code to AOSP which suggests that Android 11 might include a new ‘Share to Print’ feature that will simplify printing images and PDF files.

Google just merged a new commit to the Android Open Source Project (AOSP) to enable “share to print” — a feature that will give developers the ability to send an intent to the Print Service to directly print images or PDF files without the user having to manually choose a print service from the share menu. As of now, it doesn’t look like this code change will add a dedicated print button to the share menu as, in its current form, the feature is just a way to bypass the share menu and enable apps to directly send images/PDFs to the default printing service.

The code suggests that in Android 11 developers will be able to add a “print” button to their apps that directly sends an image or PDF to the user’s default printing service. This “print” button should be constructed to send an intent targeted to either the activity “com.android.bips.ImagePrintActivity” or “com.android.bips.PdfPrintActivity”, and with the action “android.intent.action.SEND”, category “android.intent.category.DEFAULT”, and data with the image or PDF file.

According to the commit description, this feature “makes[s] it easier for apps to print to any supported printer via a normal share intent.” The PrintManager handles sending content at an appropriate resolution for printing to any installed and enabled Print Service. The commit further reveals that image content “is downscaled to a good DPI for preview (screen DPI) or delivery (300 DPI).” The fit or fill options are “activated by the user’s landscape vs. portrait print attribute selection,” and photos “default to a locale-specific default photo media size.” As of now, there’s no official information from Google regarding the matter, but we expect to learn more in the weeks leading up to the first Android 11 open beta release.

Source: AOSP

The post Android 11’s “Share to Print” feature will make it easier to print images and PDFs appeared first on xda-developers.



from xda-developers https://ift.tt/31ycSmf
via IFTTT
Publié par à Aucun commentaire:
Libellés : ,

[Update: Confirmed] Realme’s next flagship phone with the Qualcomm Snapdragon 865 could launch soon

Update 1 (02/07/2020 @ 12:45 AM ET): Realme has essentially confirmed that its next flagship phone will feature a Qualcomm Snapdragon 865 SoC. Scroll to the bottom for more information. The article as published on January 23, 2020, is preserved as below.

Earlier this month, Chinese OEM Realme launched its first 5G enabled smartphone — the Realme X50 5G — in China. The device packed Snapdragon’s latest mid-range 765G processor, coupled with up to 12GB of RAM and 256GB of internal storage. Earlier this week, the company revealed that it will hold a global 5G launch event on February 24, at MWC 2020. Now, according to a recent report from Android Authority, the company may also launch a Snapdragon 865 powered flagship 5G device, alongside the Realme X50, at the event.

Realme

The report showcases a leaked screen of the highest score posted to the popular AnTuTu benchmarking app yet. The screenshot is from a Realme device with model number RMX2017 and with a score of 574,985 points, the Realme RMX2071 blows away the previous high score of 560,217 allegedly posted by the upcoming Xiaomi Mi 10. The screenshot also reveals that the device will be powered by the Snapdragon’s flagship 865 chipset with the Adreno 650 GPU. While Realme wasn’t among the companies to confirm a Snapdragon 865 powered device at the Snapdragon Tech Summit late last year, it’s great to see the Chinese OEM doubling down in the flagship space.

For the unaware, Realme is primarily known for its budget and mid-range devices. The company launched its first true flagship — the Realme X2 Pro (review) — back in October last year. The device featured top-of-the-line specifications at an affordable price and we expect the company to continue this trend with its upcoming flagship.

Source: Android Authority

Update: Realme confirms its next flagship will feature the Qualcomm Snapdragon 865

Realme’s CMO Mr. Xu Qi Chase has essentially confirmed that the company’s next flagship will come with the Qualcomm Snapdragon 865. In a Weibo post, Mr. Chase mentions “Realme new machine. Keywords: 5G flagship, LPDDR5, coming soon”. While this does not explicitly mention Snapdragon 865, the only 5G flagship SoCs which support LPDDR5 are the Snapdragon 865 and the Exynos 990. The Exynos 990 will debut on the Samsung Galaxy S20 series, and there’s practically no chance that Realme gets to use the SoC for its own flagship. So the other logical choice remains the Snapdragon 865.

Source: Weibo

The post [Update: Confirmed] Realme’s next flagship phone with the Qualcomm Snapdragon 865 could launch soon appeared first on xda-developers.



from xda-developers https://ift.tt/36nasrs
via IFTTT
Publié par à Aucun commentaire:
Libellés : ,
Inscription à : Articles (Atom)