lundi 19 février 2018

AOSP Android Oreo ROM Now Available for the Honor View 10

We’re nearly three months into 2018, and most devices launching in the coming months will ship with Android 8.0 Oreo out of the box. Every one of those devices will support Project Treble, which is great news — we’ve already seen the endless possibilities Treble brings to the table. It gets single, generic system images based on Android 8.0 and Android 8.1 booting on a handful of devices; it can be ported to devices that didn’t ship with Project Treble, like the Redmi Note 4, and allow those devices to run generic system images; and it makes it easier to install custom ROMs on obscure phones that otherwise wouldn’t have received developer support. Honor’s latest flagship, the Honor View 10, supports Treble, opening it up to a world of custom ROMs. And unsurprisingly, it has already received its first AOSP ROM.

The AOSP ROM for the View 10 was developed by Team OpenKirin, a team of developers who focus on Kirin-based devices, with contributions from XDA Senior Member phhusson, who is leading the charge for Project Treble development. (OpenKirin is also behind the development of Treble-enabled ROMs on devices like the Honor 9 and the Honor 8 Pro.) As of right now, the ROM has minor bugs such as SafetyNet not passing (which you can get around using Magisk) and inaccurate signal bars. Otherwise, though, it’s working perfectly, and includes extras like the Google Pixel boot animation, FPS gestures, and the EMUI camera with the latest AR Lens feature.

If you have a View 10 and are interested in trying the AOSP ROM on your device, head to the official thread and download it. It’s based on Android 8.0 (not 8.1) pure AOSP, without bloatware, and it’s a great alternative for people who can’t stand the View 10’s stock EMUI skin. It’s also likely that this ROM will work on other Treble devices, like the Mate 10, Mate 9, and Xperia XZ1.

Let us know in the comments if you’re excited to see Treble development grow!


Check out AOSP Oreo for the View 10



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

Official TWRP now available for the Xiaomi Redmi Note 5/Redmi Note 5 Plus

Thanks to Xiaomi devices’ competitive price tags, the developer community around them has grown rapidly over the years. Its size is likely one reason why the Xiaomi Redmi Note 5 and the Xiaomi Redmi Note 5 Plus, which were released just last week, have both already gotten flashable TWRP images. They’re from XDA Senior Member TingyiChen, who made them available on the XDA forums.

When it comes to custom ROM development, you can’t get anywhere without a custom recovery. Flashing ROMs is nearly impossible without one — it’s one of the simplest ways to write to the /system partition where Android operating system files reside — and they open the door to third-party firmware on the Redmi Note 5 and Redmi Note 5 Plus. You’re no longer stuck with MIUI or any other proprietary Xiaomi software.

There’s even better news. The same developer who released working TWRP images for the devices also published a mostly functional port of LineageOS 14.1, meaning it’s already possible to install custom ROMs on the Redmi Note 5 and Note 5 Plus. All it takes is unlocking the bootloader, flashing TWRP, and flashing Lineage through the recovery menu. (If you’re looking for tips on how to get started, check out the relevant XDA forum threads.)

To recap, the Redmi Note 5 and Redmi Note 5 Pro, the mid-range successors to Xiaomi’s Redmi Note 4, pack powerful hardware. The former has a 5.9-inch Full HD+ (2160 x 1080) 18:9 screen, a Qualcomm Snapdragon 636 processor, up to 6GB of RAM and 64GB of storage, and dual 12MP cameras. The latter features the same 18:9 screen, but has a single camera instead of two, swaps out the processor for a Qualcomm 625 chipset, and maxes out at 4GB of RAM.

Sadly, both phones ship with Android Nougat instead of Android Oreo, and so don’t support Project Treble out of the box. There’s always a chance, of course, that the developer community will update them with Treble compatibility a la the Xiaomi Redmi Note 4, but only time will tell.


Download TWRP for the Xiaomi Redmi Note 5 and Redmi Note 5 Plus



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

LG’s 2018 Flagship will launch in June with a 6.1″ 18:9 MLCD+ Display

Earlier this year, after LG’s smartphone division posted its 11th consecutive quarter of declining revenue, the company announced it would reevaluate its mobile strategy. Going forward, LG chairman Jo Senong-jin said, it would only release new phones when it felt it should, rather than adhere to a release schedule. But that doesn’t mean the company plans to leave the mobile market entirely, and according to a report in VentureBeat, the next release from LG is right around the corner. Meet “Judy”, LG’s upcoming flagship phone.

The South Korean company’s next high-end smartphone, which will feature “military standard” durability and a “brand new design” that’s IP68 water- and dust-resistant, isn’t much like its predecessors. It has a 6.1-inch, 18:9 FullVision display that’s complaint with HDR10, according to VentureBeat, and it’s slightly larger than the LG G6. The screen is said to be a relatively new technology called MLCD+, which contains an RGBW matrix with a white sub-pixel. It’s capable of a higher brightness (up to 800 nits) while reportedly consuming up to 35% less power than standard IPS LCD displays.

The flagship device’s other specs include a Qualcomm Snapdragon 845 system-on-chip coupled with 64GB of onboard storage and 4GB RAM. It also has stereo speakers, which VentureBeat describes as “boombox” speakers; wireless charging; and a digital assistant of some kind, likely integrated with LG’s recently announced Vision AI and Voice AI. Finally, it’ll have a dual camera module with two 16MP, f/1.6 aperture sensors.

If the rumors pan out, it sounds like “Judy” will be a fitting upgrade from LG’s previous devices. It’s unclear how it’ll slot alongside the LG V30s, an “enhanced” version of the LG V30 that’s expected to be announced at Mobile World Congress in Barcelona (according to VentureBeat, it won’t be a part of LG’s troubled G series lineup). But it won’t be long before we find out more — “Judy” will launch in June.


Source: VentureBeat



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

samedi 17 février 2018

BQ Aquaris X/X Pro Receiving Android 8.1 Oreo Beta Before Most Flagship Phones

BQ, a Spain-based budget smartphone vendor, has a presence in Europe and the US, but it tends to fly under the radar when it comes to media coverage. That’s partly because its smartphones aren’t particularly competitive against models from China-based rivals such as Xiaomi, Honor, and Motorola. However, in regions where it’s hard for customers to buy phones from the aforementioned companies, BQ has a foothold.

The BQ Aquaris X and the Aquaris X Pro, two of the few mid-range smartphones in the company’s product lineup, have virtually the same specifications: a Qualcomm Snapdragon 626 system-on-chip, a 5.2-inch Full HD (1920×1080) IPS display, a 16MP rear camera with a f/2.0 aperture, a 8MP front camera, and  a 3,100mAh battery. The difference is that the Aquaris X has 3GB of RAM paired with 32GB of storage, while the X Pro comes with 4GB of RAM and up to 128GB of storage. They’re also aesthetically different: the Aquaris X has a plastic back, while the X Pro has a glass back (both phones have a metallic frame).

The phones were announced in March 2017. The Aquaris X’s launch price was €280 ($347), while the X Pro cost €360 ($446) and €400 ($496) for the 64GB and 128GB storage versions, respectively. They shipped with stock Android 7.1.1. Nougat, the latest version available at the time.

Now, it appears that both phones are receiving an update to Android 8.1 Oreo. It’s surprising news considering that Nokia (HMD Global) and Essential are the only other non-Google OEMs to have released Android 8.1 Oreo updates. (The Nokia 8 started receiving its stable Android 8.1 update earlier this month, while the Essential Phone recently received its first beta of Android 8.1.)

BQ Aquaris X Android Oreo

Lorenzo Ori is an external collaborator who makes custom kernels for BQ devices. According to him, the OTA update comes from BQ, and is only available in the beta channel. The screenshot shows that the update includes Android’s January security patch.

It’s great news for owners of the Aquaris X and the X Pro, and serves as a reminder that it’s not necessary big OEMs which are first to roll out Android updates. Sometimes, smaller OEMs beat them to the punch, and we hope that this serves as a motivation to all other Android OEMs to start releasing Android software updates on a timely basis.

Thanks to Lorenzo Ori for the tip!



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

Facebook Loses Lawsuit Against Belgium, Fined €250,000 A Day Until it Complies with EU Privacy Laws

Facebook has long been under scrutiny over its privacy policies. The company was fined €1.2 million last year by a court in Spain for privacy violations, for example. Now, a Brussels judge has found it guilty of violating European Union privacy laws.

The decision issued this week, which stems from a 2015 lawsuit alleging that the social network illegally monitored users’ internet activity, says that the company ran afoul of EU privacy laws by failing to state which user data it saves, how long it stores the data, and how it uses it.

As a consequence, Facebook has been ordered to pay up to €250,000 a day (up to a maximum of €100 million) until it complies with Belgium’s General Data Protection Regulation (GDPR) and delete the illegally collected user data. In addition, it is required to publish the complete court verdict on its website.

It’s one of the largest fines imposed on Facebook since the social network was ordered to pay €110 million for misleading European regulators during the company’s acquisition of WhatsApp.

“We’ll comply with this new law, just as we’ve complied with existing data protection law in Europe,” Richard Allan, a spokesperson for Facebook, told HLN.

Belgium’s privacy watchdog and a plaintiff in the lawsuit, the Belgian Privacy Commission, applauded the ruling, stating, “Facebook has just launched a large campaign where they stress the importance of privacy. We hope they will now make this a reality,”

Facebook announced that it will appeal the court’s decision. “In recent years, we have worked hard to help people understand how we use cookies to display relevant content and protect Facebook,” Mr. Allen said. “We have formed teams that focus on protecting privacy, engineers developers and we have developed tools that give users choice and control options.”

It’s unclear if the company’s request for appeal will be granted.


Source: HLN (in Dutch)



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

vendredi 16 février 2018

The Huawei P20 Plus will have a beefy 4,000 mAh battery to power its Always on Display feature

Huawei, the third largest smartphone manufacturer in the world, is preparing to launch the P20, P20 Plus, and the P20 Lite at an event in Paris on March 27th. The company was previously expected to launch the 3 smartphones, code-named “Emily,” “Charlotte,” and “Anne” respectively, during the upcoming Mobile World Congress event in Barcelona. However, those plans were scrapped, allegedly due to fear of being overshadowed by Samsung’s Galaxy S9. As the P20 series announcement approaches, we are continuing to see more information about the devices leak from various sources, and today we can reveal some new information about the P20 Plus: it will have a beefy 4,000 mAh battery and an Always on Display feature.

We have found evidence for these findings based on firmware files obtained by @FunkyHuawei, the man behind the FunkyHuawei.club service, which allows users to updateunbrick, or rebrand Huawei and Honor phones for a fee.

Digging into the firmware, we discovered that the P20 Plus’ product partition contains Huawei’s Always on Display APK. This means that the app will be pre-installed on the device at launch. Previously, the only other Huawei phone to feature an Always on Display feature is the Mate 10 Pro—which happened to be its first flagship phone with an OLED screen. Whether or not this means that the P20 Plus will have an OLED screen is unclear, though the possibility is strong. The Huawei Mate 10 featured an LCD screen in contrast with the Mate 10 Pro, so it wouldn’t be unusual for two Huawei phones in the same series to have drastically different display technologies.

Huawei P20 Plus

Huawei Mate 10 Pro’s Always on Display Feature

As for the battery, we uncovered that the P20 Plus battery capacity is set at 4,000 mAh. This is the number that is reported to apps through Android’s APIs. Further, we also found that the regular P20’s battery capacity is registered as 3,320 mAh—a fairly substantial difference between the two models. We aren’t sure about any RAM/storage discrepancies between the two devices, but it’s likely that the P20 Plus will have a slight advantage in that regard.

We previously exclusively reported on the biggest design change of the upcoming P20 flagship smartphones: the controversial inclusion of an iPhone X-style notch. We believe that this notch will be where Huawei implements their new Point Cloud Depth Camera to compete with Apple’s Animoji and Face ID features. We also recently found that the latest P20 firmware is running on Android 8.1 Oreo with EMUI 8.1, though we do not know what new features EMUI 8.1 will bring. Both the P20 and the P20 Plus will feature Huawei’s latest HiSilicon Kirin 970 SoC, the same SoC in the Huawei Mate 10 series and the Honor View 10.

There are a lot of rumors about these two devices, and with the launch date creeping up next month, more will come. The alleged designs of all 3 devices recently leaked, so there probably isn’t much left to learn about these devices. If we do learn more information about the Huawei P20 devices, we will update you on our findings.



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

Google Maps v9.72 Beta Prepares to Add Uber Account Creation, Improves Transit Guidance and Road Closure Reporting, and More

Google Maps v9.72 beta is rolling out to users via the Play Store. User-facing changes are far and few between, but we did an APK teardown of the app and discovered a lot of information about upcoming features. In short, Google is adding native Uber integration to Google Maps, meaning users will be able to create Uber accounts from within Maps. Alerts about car parking, directions, and transit guidance are being improved, and there are new notifications. Finally, users will be able to submit more information about road closures.

There is a lot to get into, so let’s get started.

An APK teardown can often predict features that may arrive in a future update of an application, but it is possible that any of the features we mention here may not make it in a future release. This is because these features are currently unimplemented in the live build and may be pulled at any time by Google in a future build.


Create an Uber account from Google Maps

Uber integration

<string name="ACCOUNT_LINKING_CONTINUE">Continue</string>
<string name="ACCOUNT_LINKING_GOOGLE_SIGN_IN"&gt;Get started</string>
<string name="CANCEL_ACCOUNT_LINKING_MESSAGE">You need to link your accounts to book a ride</string>
<string name="CHOOSE_ACCOUNT_CONTINUE_AS_NAME">Continue as %1$s</string>
<string name="CHOOSE_ACCOUNT_LIST_TITLE">Choose account</string>
<string name="CHOOSE_ACCOUNT_OTHER_ACCOUNT">Use a different %1$s account</string>
<string name="CHOOSE_ACCOUNT_SUBTITLE">Link %1$s to your Google Account</string>
<string name="CHOOSE_ACCOUNT_TITLE">Book a ride in less than 30 seconds</string>
<string name="CHOOSE_PHONE_NUMBER_ADD_NUMBER">Add phone number</string>
<string name="CHOOSE_PHONE_NUMBER_LIST_TITLE">Choose another phone number</string>
<string name="CHOOSE_COUNTRY_CODE">Choose country</string>
<string name="CONTENT_DESCRIPTION_COUNTRY_CODE">Country code: %1$s %2$s</string>
<string name="COUNTDOWN_TIMER">%1$d:%2$02d</string>
<string name="COUNTRY_CODE">(%1$s)</string>
<string name="CREATE_ACCOUNT_CANCEL_BUTTON">Cancel</string>
<string name="CREATE_ACCOUNT_COARSE_LOCATION">Current city</string>
<string name="CREATE_ACCOUNT_CREATE_BUTTON">Create account</string>
<string name="CREATE_ACCOUNT_DISCLAIMER">By continuing, you agree to %1$s &lt;a href=%2$s>Terms&lt;/a> and &lt;a href=%3$s>Privacy Policy&lt;/a> and agree Google may access your %4$s account information. &lt;a href=%5$s>Learn more&lt;/a></string>
<string name="CREATE_ACCOUNT_LOCATION_LABEL">Location</string>
<string name="CREATE_ACCOUNT_PHONE_LABEL">Phone number</string>
<string name="CREATE_ACCOUNT_SUBTITLE">Your %1$s account will be created with the following information</string>
<string name="CREATE_ACCOUNT_TITLE">Almost done</string>
<string name="ENTER_PHONE_NUMBER_DISCLAIMER_FULL">"You'll get a code via SMS. Carrier rates may apply."</string>
<string name="ENTER_PHONE_NUMBER_ERROR">Something went wrong. Try entering a different phone number.</string>
<string name="ENTER_PHONE_NUMBER_NO_EXISTING_NUMBERS_SUBTITLE">To create one, enter your phone number</string>
<string name="ENTER_PHONE_NUMBER_NO_EXISTING_NUMBERS_TITLE">"You don't have an account with %1$s"</string>
<string name="ENTER_PHONE_NUMBER_TITLE">Enter phone number</string>
<string name="LINK_ACCOUNT_DISCLAIMER">By linking, you agree Google may access your %1$s account information. &lt;a href=%2$s>Learn more&lt;/a></string>
<string name="LINK_ACCOUNT_LINK_BUTTON">Link accounts</string>
<string name="LINK_ACCOUNT_TITLE">"Let's link your %1$s account"</string>
<string name="RESEND_SMS_ERROR">"Can't get a new code with this phone number. Try entering a different phone number."</string>
<string name="VERIFY_CODE_ERROR">Wrong code. Try again.</string>
<string name="VERIFY_CODE_RESEND_SMS_BUTTON">Get new code</string>
<string name="VERIFY_CODE_SMS_DELAY_LABEL">"Didn't receive a code?"</string>
<string name="VERIFY_CODE_SMS_DELAY_TIME">Wait %s and try again</string>
<string name="VERIFY_CODE_SUBTITLE">Sent to %1$s</string>
<string name="VERIFY_CODE_TITLE">Enter verification code</string>
<string name="CREATE_UBER_ACCOUNT_DISCLAIMER">"By continuing, you agree to Uber's &lt;a href=%1$s>Terms&lt;/a> and &lt;a href=%2$s>Privacy Policy&lt;/a> and agree Google may access your Uber account information. &lt;a href=%3$s>Learn more&lt;/a>"</string>

This is the headlining new feature we discovered in our teardown. Currently, booking an Uber ride from Maps requires installing and signing into the Uber app, but the new strings indicate that Google is adding support for Uber account creation to Maps.

When the feature goes live, users will be able to create Uber accounts without leaving the Maps app. It’ll prompt them select their country code, enter their phone number, and type in a text verification code. It’ll also show a disclaimer letting users know that when they create an Uber account in Maps, they’re also agreeing to Uber’s Terms and Privacy Policy and allowing Google to access their Uber account information.

Car parking

<string name="CAR_PARKING_DIFFICULTY_EASY">Easy</string>
<string name="CAR_PARKING_DIFFICULTY_HARD">Limited</string>
<string name="CAR_PARKING_DIFFICULTY_MEDIUM">Medium</string>
<string name="CAR_PARKING_DIFFICULTY_ONSITE">On-site</string>

In 2017, Google Maps gained a feature that lets users know if car parking is likely to be available near a location, and how difficult it might be to get that parking. These strings suggest that Google is planning to expand on this: a future version of Maps will let users know if on-site parking is available at a location.

Direction preferences

<string name="DIRECTIONS_AVOIDING_FERRIES">Avoiding ferries</string>
<string name="DIRECTIONS_AVOIDING_HIGHWAYS">Avoiding highways</string>
<string name="DIRECTIONS_AVOIDING_HIGHWAYS_FERRIES">Avoiding highways, ferries</string>
<string name="DIRECTIONS_AVOIDING_HIGHWAYS_TOLLS">Avoiding highways, tolls</string>
<string name="DIRECTIONS_AVOIDING_HIGHWAYS_TOLLS_FERRIES">Avoiding highways, tolls, ferries</string>
<string name="DIRECTIONS_AVOIDING_TOLLS">Avoiding tolls</string>
<string name="DIRECTIONS_AVOIDING_TOLLS_FERRIES">Avoiding tolls, ferries</string>

These strings polish the route options experience. Maps will explicitly say that it’s routing around highways, tolls, and ferries when users set their preferences in the route options setting. (The options appear in the overflow button when a user taps on the Directions button.)

New notifications

<string name="NOTIFICATION_SUBTEXT_GENERIC">Tap to correct your transport mode for better updates</string>
<string name="NOTIFICATION_SUBTEXT_SPECIFIC">Tap to correct your commute mode for better updates</string>
<string name="NOTIFICATION_TITLE_DRIVE">"Don't drive to work?"</string>
<string name="NOTIFICATION_TITLE_GENERIC">How do you commute?</string>
<string name="NOTIFICATION_TITLE_TRANSIT">"Don't take transit to work?"</string>

Maps will ask users questions such as, “How do you commute?”, “Don’t drive to work?” and “Don’t take transit to work?” via notifications. Another new notification will let users quickly change their transport and commute preferences.

Improving the “Questions and Answers” feature

Questions and answers

<string name="PLACE_QA_ACCESSIBILITY_YOUR_ANSWER_OVERFLOW_MENU_DESCRIPTION">Overflow menu for your answer: %1$s</string>
<string name="PLACE_QA_ACCESSIBILITY_YOUR_QUESTION_OVERFLOW_MENU_DESCRIPTION">Overflow menu for your question: %1$s</string>
<string name="PLACE_QA_ALL_DROPDOWN_MENU">All</string>
<string name="PLACE_QA_ANSWER_DROPDOWN_MENU">Answers</string>
<string name="PLACE_QA_ANSWER_QUESTIONS">Answer questions about places</string>
<string name="PLACE_QA_ANSWER_QUESTIONS_HELP_TEXT">Share your knowledge and help others by answering questions about places.</string>
<string name="PLACE_QA_ASK_OR_ANSWER_QUESTIONS">Ask or answer questions about places</string>
<string name="PLACE_QA_ASK_OR_ANSWER_QUESTIONS_HELP_TEXT">Need more info? Ask questions about businesses and places on Google Maps. You can also help others by answering their questions.</string>
<string name="PLACE_QA_ASK_QUESTIONS">Ask questions about places</string>
<string name="PLACE_QA_ASK_QUESTIONS_HELP_TEXT">Need more info about a place? Ask a question and let others lend a hand.</string>
<string name="PLACE_QA_DELETED_QUESTION_PLACE_HOLDER_TEXT">[Deleted question]</string>
<string name="PLACE_QA_INACTIVE_PLACE_ERROR_MESSAGE">This place has been removed or deleted</string>
<string name="PLACE_QA_INACTIVE_PLACE_SUBTITLE">Place no longer exists</string>
<string name="PLACE_QA_INACTIVE_PLACE_TITLE">Inactive place</string>
<string name="PLACE_QA_NO_ANSWERS_YET_HELP_TEXT">Anyone can answer questions to help others learn more about a business or a place. Just search for a place, select a question and tap &lt;b>Add an answer publicly&lt;/b>.</string>
<string name="PLACE_QA_NO_QUESTIONS_OR_ANSWERS_YET">No questions or answers yet</string>
<string name="PLACE_QA_NO_QUESTIONS_OR_ANSWERS_YET_HELP_TEXT">Anyone can ask or answer questions to find out more about a business or a place. Just search for a place and use the &lt;b>Questions &amp; answers&lt;/b> section.</string>
<string name="PLACE_QA_NO_QUESTIONS_YET_HELP_TEXT">Anyone can ask questions to find out more about a business or a place. Just search for a place and tap &lt;b>Ask the community&lt;/b>.</string>
<string name="PLACE_QA_QUESTION_DROPDOWN_MENU">Questions</string>
<string name="PLACE_QA_SEE_THE_QUESTION">See the question</string>
<string name="PLACE_QA_SUCCESS_MESSAGE_ANSWER_DELETED">Your answer was deleted</string>
<string name="PLACE_QA_SUCCESS_MESSAGE_QUESTION_DELETED">Your question was deleted</string>

These strings are related to the Questions and answers feature in Google Maps. Maps will now let users know about whether a place is inactive or no longer exists (if it’s removed and deleted, for example). There are new accessibility strings for overflow menu answers, and when a user taps the delete button for a question/answer he or she submitted, the app will indicate whether the question/answer was deleted successfully

Detailed information for road closures

Road closures

<string name="RAP_DISAMBIGUATION_CLOSED_ROAD_OPTION_DESCRIPTION">Report issues like construction, crashes, or other closures on this road</string>
<string name="RAP_DISAMBIGUATION_CLOSED_ROAD_OPTION_TEXT">Road is closed</string>
<string name="REPORT_A_PROBLEM_PICKER_DIALOG_REPORT_ADDRESS_INFO">Address info</string>
<string name="REPORT_A_PROBLEM_PICKER_DIALOG_REPORT_CLOSED_ROAD">Closed road</string>
<string name="REPORT_A_PROBLEM_PICKER_DIALOG_REPORT_ROAD_INFO">Road info</string>
<string name="REPORT_A_PROBLEM_PICKER_DIALOG_SUBTITLE">Select an issue to report</string>
<string name="REPORT_ROAD_CLOSED_ADD_DETAILS">Add more details</string>
<string name="REPORT_ROAD_CLOSED_INSTRUCTIONS">Help people know more about this closure</string>
<string name="REPORT_ROAD_CLOSED_OPTIONAL">(Optional)</string>
<string name="REPORT_ROAD_CLOSED_ROAD_PICKER_SUBTITLE">Tap all sections of the road closure</string>
<string name="REPORT_ROAD_CLOSED_ROAD_PICKER_TITLE">Select the roads</string>
<string name="REPORT_ROAD_CLOSED_TOOLBAR_TITLE">Report a road closure</string>
<string name="REPORT_WRONG_ROAD_INFO_PICKER_TITLE">Select the road</string>
<string name="ROAD_CLOSED_ADD_SCHEDULE_PROMPT">Add closure dates and times</string>
<string name="ROAD_CLOSED_DIRECTION_ONE_WAY">One way only</string>
<string name="ROAD_CLOSED_DIRECTION_PLACEHOLDER">Which way is closed?</string>
<string name="ROAD_CLOSED_DIRECTION_PROMPT">Direction</string>
<string name="ROAD_CLOSED_DIRECTION_TWO_WAYS">Both ways</string>
<string name="ROAD_CLOSED_REASON_CONSTRUCTION">Construction</string>
<string name="ROAD_CLOSED_REASON_CRASH">Crash</string>
<string name="ROAD_CLOSED_REASON_EVENT">Local Event</string>
<string name="ROAD_CLOSED_REASON_NATURE">Nature</string>
<string name="ROAD_CLOSED_REASON_NATURE_FALLEN_TREE">Fallen tree</string>
<string name="ROAD_CLOSED_REASON_NATURE_FLOOD">Flood</string>
<string name="ROAD_CLOSED_REASON_NATURE_MUDSLIDE">Mudslide</string>
<string name="ROAD_CLOSED_REASON_NATURE_PLACEHOLDER">Choose which type</string>
<string name="ROAD_CLOSED_REASON_NATURE_SNOW_ICE">Snow or ice</string>
<string name="ROAD_CLOSED_REASON_NOT_SURE">Not sure</string>
<string name="ROAD_CLOSED_REASON_OTHER">Other / Not sure</string>
<string name="ROAD_CLOSED_REASON_PROMPT">Reason</string>
<string name="ROAD_CLOSED_SCHEDULE_ADD_DATE_TIME">Add details (optional)</string>
<string name="ROAD_CLOSED_SCHEDULE_CLOSED_NOW">Closed now?</string>
<string name="ROAD_CLOSED_SCHEDULE_END_WHEN">When will the closure end?</string>
<string name="ROAD_CLOSED_SCHEDULE_FROM">Start date</string>
<string name="ROAD_CLOSED_SCHEDULE_HEADER_PROMPT">When</string>
<string name="ROAD_CLOSED_SCHEDULE_INVALID">Change what you entered so the end date is in the future and after the start date</string>
<string name="ROAD_CLOSED_SCHEDULE_UNTIL">End date</string>

Users are already able to report road closures via Google Maps, but these strings indicate that they will soon be able to add more detailed information about those closures — anything from why the road is closed to which section of the road is closed and when the closure will end. Users will also be able to report the cause of the road closure (e.g., construction, crashes, fallen trees, and local events).

Transit guidance

<string name="TRANSIT_DIRECTIONS_ONLY_ONE_STOP_SUPPORTED">"Can't give transit directions for multiple stops"</string>
<string name="TRANSIT_GUIDANCE_APPROXIMATE_DURATION">About %1$s</string>
<string name="TRANSIT_OCCUPANCY_CRUSHED_STANDING_ROOM_ONLY_DESCRIPTION">Crushed standing room only</string>
<string name="TRANSIT_OCCUPANCY_FEW_SEATS_AVAILABLE_DESCRIPTION">Few seats available</string>
<string name="TRANSIT_OCCUPANCY_MANY_SEATS_AVAILABLE_DESCRIPTION">Many seats available</string>
<string name="TRANSIT_OCCUPANCY_STANDING_ROOM_ONLY_DESCRIPTION">Standing room only</string>

Google Maps is getting improved transit features. The strings reference a feature called “transit occupancy”, but at this point, there’s not much else to go on. Future versions of Maps will also let users know when it can’t give transit directions for multiple stops, and show the approximate duration of transit guidance.

Error messages

<string name="CANT_FIND_A_WAY_THERE">"Can't find a way there"</string>
<string name="CANT_REACH_GOOGLE_MAPS">"Can't reach Google Maps"</string><string name="LOCATION_RESPONSE_ERROR">"Can't find your location. Try again in a few minutes."</string><string name="QUIT_BECAUSE_ANDROID_AUTO_RUNNING">"Your phone can't display Google Maps while Android Auto is running"</string>
<string name="SOMETHING_WENT_WRONG">"Something went wrong. Can't get directions there right now."</string>

Maps now shows more error messages. There’s a standard location response error and a “Can’t reach Google Maps” error, as well as a customary “Something went wrong” error (which will show up when Maps can’t get directions). There’s also a message about how Google Maps can’t display on the phone’s screen while Android Auto is running.

Miscellaneous

<string name="ACCESSIBILITY_FF_ENTRY_POINT">Question mark</string>
<string name="BUSINESS_HOURS_CLOSING_HOURS_TITLE_V2">Closing time</string>
<string name="BUSINESS_HOURS_OPENING_HOURS_TITLE_V2">Opening time</string>
<string name="TAB_BUTTON_BADGE_CONTENT_DESCRIPTION">Tab has new updates</string>

The first string adds to Maps’s existing accessibility features, while the second and third strings cryptically point to a “V2” feature business opening and closing times. The last one lets users know when a tab button has new updates (for example, when someone posts a new review posted on a point of interest’s Reviews tab).

Maps - Navigation & Transit (Free, Google Play) →


Let us know in the comments if you spot anything new, and follow our APK Teardown tag for more articles like this!



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