LightBlog

dimanche 12 avril 2020

LG V60 ThinQ with Dual Screen Review – So Close to Greatness

LG launched the V10 back in 2015, kicking off what has been a very interesting series of devices. Say what you will about LG, but they’re not afraid to try new things. Many of these features end up as nothing more than “gimmicks,” discarded after a couple of generations. The LG V60 ThinQ includes yet another one of these interesting “gimmicks,” but will this be the one to last?

Before we dive into the LG V60 ThinQ, let’s take a look back at the V Series. The LG V10 had a small “Second Screen” above the main display for widgets and other odds and ends. LG continued with the Second Screen on the LG V20 a year later. Things went sharply in a new direction when the LG V30 launched without the Second Screen and a much more slimmed down and polished design. That trend continued with the bigger LG V40 ThinQ which had more cameras and a notched display, a first for the series. Then, the LG V50 ThinQ introduced the Dual Screen attachment, which brings us to today.

The Second Screen only lasted two generations before LG gave up on it. The first attempt at the Dual Screen attachment for the LG V50 ThinQ wasn’t super compelling, but the company made a lot of improvements with the LG G8X ThinQ. So now we’re at the second V Series device with the Dual Screen and the third iteration overall. Is this finally the “gimmick” that LG will stick with for the long haul, or is the V60 doomed to be yet another last effort? Let’s find out.

LG V60 ThinQ Forums

LG V60 ThinQ Specifications

Specifications LG V60 ThinQ (T-Mobile variant)
Dimensions & Weight
  • 169.3 x 77.6 x 8.9mm
  • 214 g
Display
  • 6.8-inch Full HD+ P-OLED
  • 2460×1080 pixels, 395 PPI
  • 20.5:9 aspect ratio
  • 500 nits brightness
  • 83.1% screen-to-body ratio
  • Gorilla Glass 5
SoC
  • Qualcomm Snapdragon 865:
    • 1x Kryo 585 Prime core (ARM Cortex-A77 based) clocked at 2.84GHz
      3x Kryo 585 Performance cores (ARM Cortex-A77 based) clocked at 2.4GHz)
      4x Kryo 585 Efficiency cores (ARM Cortex-A55 based) clocked at 1.8GHz
  • Adreno 650 GPU
RAM & Storage
  • 8GB/128GB
  • microSD card slot
Battery
  • 5,000mAh
  • Qualcomm Quick Charge 4.0+
  • Wireless charging
Fingerprint Sensor In-display fingerprint sensor
Rear Cameras
  • 64MP primary sensor, 1/1.72″, 0.8-micron, f/1.8, 78-degree FOV, OIS, Dual Pixel PDAF, pixel binning to 16MP with 1.6-micron effective pixel size
  • 13MP ultra-wide angle sensor, 1/3.4″, 1.0-micron, f/1.9, 117-degree FOV, Dual Pixel PDAF
  • ToF Z Camera with HQVGA resolution, 80-degree FOV, 1/4″, 14-micron, f/1.4
  • Video recording:
    • 8K at 26fps
    • 4K at 60fps
    • HDR10+ video recording
    • 4K time lapse
    • AI time lapse
    • EIS
    • Video Portrait
    • Voice Bokeh
Front Camera
  • 10MP, 1/3.1″, 1.22-micron, f/1.9, 72.5-degree FOV
Audio
  • 3.5mm headphone jack, 32-bit Hi-Fi Quad DAC
  • Balanced stereo speakers
  • 4 microphones on the top, bottom, left, and back to capture 3D audio recording
  • 3D Sound Engine
Network Bands
  • 4×4 MIMO, 256QAM with 3CA, CAT 22; Carrier Aggregation: 1UL 7DL
  • 5G: Sub-6GHz Bands N25, N2, N41, N66, N71
  • 4G LTE: Bands B2, B4, B5, B12, B46, B48, B66, B71 (TMUS) B25, B26, B41, B46, B48 (SPCS)
  • 3G
    UMTS: Bands B2, B4, B5;
  • 2G
    GSM: Bands 850/900/1800/1900 MHz
  • 1.9 GHz CDMA PCS, 800 MHz CDMA
Connectivity
  • Wi-Fi 6
  • Bluetooth 5.1
  • S-GPS and Qualcomm Service for Enhanced Location Accuracy
  • USB 3.1 Type-C port
  • NFC
Android Version Android 10

LG V60 Hardware & Design

I think everyone will agree that the LG V60 ThinQ is a big phone. The 6.8-inch display is very close to the display size on some smaller tablets, after all, with the device itself being just over an inch shorter than the latest iPad Mini. Obviously, it’s much narrower than a tablet, but there’s no getting around the fact that this is a very large phone. It’s easily the biggest phone I’ve ever used.

Maybe I’ve become a curmudgeon who hates big phones, but the size of the LG V60 ThinQ is something that really impacts my daily usage. I remember reviewing the LG V10 and I couldn’t get over how big, thick, and heavy it was. The LG V60 isn’t heavier than I would expect, but it certainly feels like LG has returned to the tank-like design of the first V Series devices.

Phone size is a very subjective thing. You might be the type of person who spends most of their screen time on a phone, so a big display might be something you really like. Personally, I prefer a smaller device that’s easier to use with one hand. I also prefer the feel of a smaller device in my pocket as I find it annoying to have a big phone bouncing around while running or cycling. Everyone’s use cases are different.

Putting the size aside, the design of the LG V60 ThinQ is really nice. I received the “Classy White” model from LG USA for review, but both the blue and white color options feature Gorilla Glass 5 on the front and Gorilla Glass 6 on the back. The glass back slopes drastically into the aluminum frame around the edges. It’s nearly a chamfer, but not as sharp. The LG V60 is a decently thick phone, and the shape of the back really makes that known. The aluminum frame provides a nice contrast with the white back. One negative about the glass back is how much it shows fingerprints.

The rear cameras are aligned in a horizontal row, very similar to the Samsung Galaxy S10. It makes the back of the phone look like a robot face, which may or may not be a good thing depending on your view. On the left side, you’ll find the power button, and on the right side is where the volume buttons and Google Assistant button live. I like Google Assistant and use it pretty frequently, but I find this button placement to be a little annoying. The volume up, down, and Assistant buttons are basically the same size, so it’s not super obvious by feel if you’re pressing volume or Assistant. The bottom edge features the USB-C port, speaker grill, and an ancient round port called a “headphone jack.”

The front of the device is pretty standard. LG ditched the dual front-facing cameras in favor of a single camera in a waterdrop notch this time. I don’t miss the second camera. If you’re going to have a notch, I definitely prefer making it as small as possible. The bezels around the display are surprisingly big, but only because the display doesn’t curve around the edges like most flagship phones. I have to admit it’s been kinda nice using a flat display.

Overall, if I put my personal bias against giant phones aside, this is a very attractive phone made with premium materials. It feels like a flagship phone in your hands. That may seem like an obvious statement, but it’s not always the case. I think the company made the correct design changes in going from the LG V50 to the LG V60. That includes the Dual Screen accessory as well, but more on that later.

LG V60 Display

The LG V60 is a flagship phone that can compete with the likes of the Samsung Galaxy S20 Ultra in almost every category. The one area where the LG V60 doesn’t stack up, at least in terms of raw specifications, is the display. While many high-end devices are rocking Quad HD+ displays with 90Hz or even 120Hz refresh rates, the LG V60 only has a 1080p display with the classic 60Hz refresh rate. This is a downgrade from last year’s LG V50 as well.

1080p on a screen this large seems like it would be a problem, but this is a surprisingly good display. Everything looks crisp and clear with vibrant and deep colors. LG’s OLED panels were a bit iffy in earlier generations, but I haven’t noticed any of those problems on the LG V60. The lower resolution hasn’t been a big deal to me either. Refresh rate, on the other hand, is something you will notice if you’re coming from a phone with a 90Hz or 120Hz panel. I haven’t upgraded my daily driver to such a device yet, so it doesn’t bother me.

I will talk about the Dual Screen in-depth in its own section, but I should mention here that it has essentially an identical display. Brightness and color are matched on both panels, but you can choose to tune them separately if you’d like.

There is a really big issue in the display department, though: auto-brightness. It’s bad. I’m the type of person who enables auto-brightness on day one and then never thinks about it again. On most phones, I don’t have to think about it again. Auto-brightness on the LG V60 ThinQ, unfortunately, is unusable. I can be sitting in my living room with ample lighting and all of a sudden the brightness will lower until the display is nearly unreadable. This has happened to me on multiple occasions, and it’s so bad that I had to disable auto-brightness altogether. I hope LG can fix this in a software update.

One final note on the display: There is an optical fingerprint sensor under the display. This is my second phone with an under-display fingerprint sensor, and I still don’t like it. I just find it to be generally annoying and frustrating to use.

Dual Screen Accessory

As mentioned before, LG’s first attempt at the Dual Screen accessory felt unfinished. LG solved many of the problems with the Dual Screen attachment for the LG G8X, and they’ve continued to refine things further with the LG V60 ThinQ. The Dual Screen experience is about hardware and software, both of which have been improved this time.

First, let’s talk about the hardware. Like I said in the display section, the Dual Screen has the same display as the phone itself, including the notch (which is fake on the Dual Screen). The bezels are also the same, which is both a good and bad thing. The bezels on the phone and Dual Screen make it easy to touch the edge of the screen near the hinge. The downside is there’s a very large gap between the two displays.

The gap between the displays is why the Dual Screen is better for using two apps side by side rather than spanning one app across both. You can’t think of this as a tablet that can fold in half, like the Samsung Galaxy Fold. It’s really more of a small, digital notebook. The best way to use the Dual Screen to its full potential is to do independent tasks on each screen.

Moving on from the Dual Screen’s display, let’s talk about the case itself. The cutout on the back for the cameras has been greatly reduced in size. On the LG G8X, it was a big square cutout that revealed half of the phone’s back. This time around, the cutout is the size of the camera bump, which offers better protection and looks nicer. LG has also added a ribbed texture to the case that adds some nice grip, but I’m not a fan of the look.

Software is a huge part of the Dual Screen experience. After all, slapping a second screen on your phone isn’t useful if you can’t interact with it in a meaningful way. LG has improved several of the Dual Screen software features on the LG V60, making it feel like a more complete product.

The control buttons that pop-out from the side of the display are ever-present, and they have the same features as last time. You can swap the screens when you have two apps open, move apps between screens, put the main display to sleep, and span apps across both screens in “Wide View” if supported. “Wide View” is one area where LG has made some improvements.

The LG G8X only supported Google Chrome for Wide View, but the LG V60 ThinQ adds YouTube, Google Maps, Google Photos, Gmail, the Google app, and the Naver Whale browser. That’s still a pretty small list, but it is an improvement, and you can easily force more apps to use Wide View with a simple app.

As I mentioned above, there’s a considerable gap between the displays, and that makes Wide View not super useful. Sure, it can be nice to view a website or Google Maps in a larger view, but that’s not what I find myself wanting most of the time. Rather than spanning both displays, I would love to see apps with a “dual pane” UI. For example, it would be great to view Gmail with the inbox on one screen and open emails on the second screen. I highly recommend an app called “G8X BrowserHelper” for improving the Dual Screen experience. You set it as your default browser, and when you tap a link in any app it will open it in a browser window on the other screen, keeping the current app open.

The most fun part of the Dual Display experience is still the game controller feature. I’m not a big mobile gamer, but I enjoy a good side scroller or racing game. The game controller is great for those times, and I love the ability to create your own custom controller for every game. At the end of the day, it’s still a touchscreen controller, which has its downsides, but it’s a huge improvement over controls that overlay on top of the game UI.

As I’ve already said, you shouldn’t compare the LG V60 ThinQ with Dual Screen to the Samsung Galaxy Fold. The best way to use the Dual Screen is to have two apps running at the same time, not one app spanned across both screens. If the latter is how you expect to use the Dual Screen you’re not going to like it. This is why I don’t find the Wide View feature to be that compelling.

Another aspect that’s different from a true “foldable phone” is you don’t have to keep the Dual Screen attached. Once you stop treating the LG V60 with its Dual Screen accessory like a foldable phone, the experience becomes much better. There’s a ton of potential here, but it sadly depends on developers to support it. Something like the dual-pane UI I mentioned would be awesome for a multitude of apps, but why should developers rush to support something that LG could abandon?

One last thing about the Dual Screen: Don’t underestimate its use as a kickstand/tripod. You can watch a video in landscape mode while the LG V60 is propped up on the table. You can position it to take photos. It’s more useful than you might think.

LG V60 Cameras

LG V60 Dual Screen

Note: Due to Stay at Home orders, I was not able to go out and test the cameras as much as usual. Max Weinbach contributed some of his camera samples as well.

It’s time to talk about one of the most important aspects of every flagship phone: the camera quality. The V Series has rocked triple rear cameras for a while, but the LG V60 ThinQ goes back to two (the front also drops from two to one camera). More cameras don’t always mean they’re good cameras, but it does mean more options.

The LG V60 ThinQ drops the dedicated telephoto lens in favor of using digital zoom on the large 64MP main camera. The main sensor captures images at f/1.8 with a pixel size of 0.8 microns. LG says the sensor supports zoom from 2X to 10X, but this is via digital zoom from a crop on the main lens. The second camera is a staple among LG phones: wide-angle. It’s 13MP at f/1.9 and has a 117° field of view. Both cameras are assisted by a ToF sensor.

LG V60

In a word, I would describe the LG V60 ThinQ cameras as “okay.” In some situations, I was very impressed with the results, even preferring them over the Samsung Galaxy S20 Ultra. But in other situations, I was disappointed.  The main issue I noticed is inconsistent exposure. Certain parts of a photo can end up overexposed, leaving darker areas hard to see.

While Samsung phones can soften images too much, LG phones seem to go in the opposite direction. Sometimes I noticed excessive sharpening, which can make a photo look noisy. If I had to choose between over sharpening and over smoothing, I would take the extra detail every time. But it’s still a problem, nonetheless.

Let’s get one thing out of the way: A large megapixel count is not a replacement for true optical zoom. That being said, the zoom capabilities of the LG V60 ThinQ are pretty decent, all things considered. It uses software to digitally crop and sharpen the zoomed-in photos. The results can sometimes look like an oil painting, but in general, they are better than what you would normally get from digital zoom.

On the video front, the LG V60 ThinQ is capable of recording 8K video. I’m not sure many people own an 8K TV yet, but having that extra quality from the get-go can be useful for video editing. 8K video can be recorded at 24FPS while 4K video can be shot at 60FPS. Video overall looks pretty great. Along with the extra microphones mentioned in the audio section below, this is a great device for video capture.

The 10MP selfie camera isn’t super noteworthy. It gets the job done. LG’s Portrait Mode algorithms could use some work, though. One little tidbit about the camera software that I like is Motion Photos. They work basically the same as on a Google Pixel phone and even support playback in Google Photos.

Overall, I would say the LG V60 ThinQ’s camera situation is just good enough for a flagship phone. I don’t think it can beat Apple, Google, or Huawei, but it’s fairly close to Samsung.

LG V60 Performance

by Max Weinbach

The LG V60 ThinQ is one of the faster phones on the market thanks to the Qualcomm Snapdragon 865. While it’s not the fastest Snapdragon 865-powered phone I’ve tested, it is still faster than LG’s previous generation phones. There are no frame drops, no app loading lag, or anything of the sort. It is like any other modern flagship: fast as it should be. To be honest, I don’t feel it necessary to run through a bunch of benchmarks because I feel it really shines in real-world performance, but I’ll still share some results for good measure.

What I’m doing here is simple: I’m running these benchmarks on the LG V60 ThinQ, LG V50 ThinQ, iPhone 11 Pro Max, and Samsung Galaxy S20 Ultra. This is so you can see what the difference is between two Qualcomm Snapdragon 865 devices and LG’s previous generation phone. The settings will be the same with the same apps across the devices.

Geekbench is the go-to CPU benchmark. Since Geekbench released Geekbench 5 with an emphasis on AI, AR, and ML, along with some camera stuff, I decided to use it for benchmarking. To give some simple context, these are likely some of the highest scores we will be seeing on Android phones this year.

Next up is AnTuTu. This is, in my opinion, one of the better benchmarks. It tests pure CPU and GPU performance along with usage tests like scrolling and HTML5. The higher the score the better. AnTuTu also separates each category into its own number. You get a score for memory, GPU, CPU, and UX performance.

Both the LG V60 ThinQ and the Samsung Galaxy S20 Ultra have UFS 3.0 storage for faster theoretical storage speeds. The LG V50 ThinQ has UFS 2.1 storage, so the LG V60 ThinQ has an advantage here over its predecessor. Honestly, these speeds don’t matter that much. You won’t notice much of a difference between the devices. Still, I know people like to compare minor details between devices, so here are the results for the phones.

3DMark is also a great way to test GPU power. If a phone scores well here, you won’t have to worry about it running any Android game. The LG V60 ThinQ handles it very well, as expected. According to 3DMark, the LG V60 outperforms over 99% of smartphones that have been tested. I threw the newest iPhone in there because people love to compare iPhones to Android phones, and as you can see, the GPU on the LG V60 beats the iPhone by a cool 200 points.

Look, the LG V60 ThinQ is really fast. It’s one of the fastest phones you can buy. It’s hard to project longevity, but I feel like this phone will still perform well for two years or more without massive slowdowns.

Joe’s Thoughts: Day to day performance on the LG V60 has been really great. This is easily the fastest device I’ve used. I can crank up the graphics on games and the phone handles it without any issues. Installing apps from the Google Play Store is super quick. It certainly makes some of my other phones feel a bit slow.

LG V60 Battery & Charging

One of the best things about the LG V60 ThinQ is battery life. Packed with a 5,000mAh battery and a 1080p display, this is one of the few phones that I can honestly say might not need a nightly charge. The battery capacity alone isn’t that noteworthy (it’s the same size as the Samsung Galaxy S20 Ultra), but the “low” display resolution and only 60Hz refresh rate greatly help with battery life. You can expect to get around 5 hours of heavy screen-on time in a day.

As for charging, the LG V60 ThinQ supports fast wired and wireless charging. It comes with a 25W charger in the box as well as a cool magnetic adapter to charge the phone with the Dual Screen cover on. With the included charger, you can go from 0% to 25% in about 15 minutes. 30 minutes will get you halfway charged. Wireless charging does work with the Dual Screen cover on, but it’s a little slower than normal.

LG V60 Audio

I’ve reviewed a lot of LG phones, and there’s a subset of people who want to hear about the audio quality. Truthfully, I’m not anything close to an audiophile. While I can say the audio from the LG V60 sounds really good, the Quad DAC technology is wasted on me. There are two audio features that I do really like, though. First, the LG V60 has a headphone jack. I’ve largely moved on to Bluetooth headphones, but I still appreciate having the physical port from time to time. It doesn’t hurt to have it.

Second, the LG V60 has stereo speakers. That’s a feature that sounds good on paper, but it doesn’t always pan out in real life. The stereo speakers on the LG V60 are, thankfully, very good. The phone gets super loud and the audio quality is great. The last audio feature to mention is the phone’s audio capture ability. The LG V60 has four microphones that help out a lot when recording video. Video recording has always been a big part of the V Series, so it’s nice to have improved audio capture to go along with it.

LG V60 Software

The LG V60 ThinQ ships with Android 10 and the company’s LG UX skin. In terms of pure aesthetics, I don’t mind LG UX at all. To someone who has never used an LG phone, I would compare the look to a combination of Google Pixel and Samsung’s One UI software. In terms of actual usage, it’s much closer to the latter. LG is clearly taking many cues from Samsung here.

One UI put a big focus on one-handed usability by moving UI elements lower on the display. LG is attempting to do the same thing with LG UX. This is most noticeable when you expand the notification shade and the Quick Toggles all move to the bottom of the screen. The implementation doesn’t seem quite as fully fleshed out as on One UI, however.

The default LG Launcher is decent enough. You have the option to have an app drawer or go iOS-style with all the apps on the home screen. One of the most annoying things about LG’s software is the app drawer, though. You can sort the apps by name or download date, but it will not retain your choice. Downloaded apps are always added to the end of the list. This is maddening and I have no idea why it’s still a thing.

Another weird thing in LG’s software is the way gestures act with third-party launchers. You can use Android 10’s gesture navigation with third-party launchers. However, when you switch to a new default launcher, it will always revert to the 3-button navigation bar. You have to manually go into the Settings, find the Navigation Bar options, and enable gestures again. It’s a little annoying.

For the most part, I would say LG UX is an inoffensive Android skin. The biggest issue with LG software is support. LG has been doing a better job lately at providing consistent updates, but that’s only because the only to go was up. The LG V40 ThinQ launched with Android 8.1 Oreo in October 2018, two months after Android 9 Pie was available. It didn’t receive the Android 9 Pie update until June 2019. My T-Mobile LG V60 ThinQ has the February 2020 security patches, and I’m afraid it will be stuck on that for a while. The update situation makes it hard to recommend LG phones.

Conclusion

The title of my LG V60 ThinQ first impressions was “A Good Phone at a Great Price.” My argument was the LG V60 ThinQ fails to “win” in any of the categories where it competes. The Dual Screen isn’t as exciting as other gimmicks in the smartphone world right now, and as just a smartphone, you can do better elsewhere. The saving grace was the price tag, which undercuts many of the top flagships on the market. However, I don’t think I was giving the LG V60 enough credit.

My first impression of a device is usually my final conclusion. In most cases, it doesn’t take long to get an idea of what a phone has to offer. However, with the LG V60, I started out pretty “meh” on it, but I’ve slowly come around to liking it more. A lot of that has to do with finally understanding how best to use the Dual Screen, but I also think the LG V60 is a sneaky good smartphone by itself.

The pricing is still the biggest selling point for the LG V60. Even with the Dual Screen, which costs around $100 by itself, the whole package is about $200-300 cheaper than several top-of-the-line devices. The only area that is an objective downgrade from other flagships is the 1080p 60Hz display. I don’t think the camera quality stacks up, but that is more subjective.

If you are looking for a flagship phone and you can’t justify the $1,000+ price tags, the LG V60 ThinQ is a nice option. One of the questions you’ll have to ask yourself is if the Dual Screen is worth the extra $100. I really like it as an accessory to use at home while consuming content on the couch, and I can also see it as a very useful productivity tool. For me, though, the entire package is too bulky to take anywhere in my pocket. I still think it’s a good reason to buy the phone.

There are two main concerns with the LG V60 ThinQ: Will it get updates and will the Dual Screen continue to be supported? We’ve already talked about LG’s issues with software updates and their tendency to ditch interesting ideas. Both of those things will impact your long term experience. Sadly, I don’t have a lot of confidence in LG in this regard. The LG V60 ThinQ is a super compelling device with a lot of positives, but it succumbs to LG’s longstanding deficiencies much like their other devices.

Buy the LG V60 from AT&T | Buy the LG V60 from T-Mobile

The post LG V60 ThinQ with Dual Screen Review – So Close to Greatness appeared first on xda-developers.



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

samedi 11 avril 2020

Android 10 internal beta leaks for the Nokia 8 Sirocco and Nokia 5.1 Plus

HMD Global’s bootloader unlock policy might be a mess, but the company still has a pretty good reputation among Android enthusiasts due to their speedy update schedule and minimal software changes. Be it the entry-level Nokia 2.2 or the mid-range Nokia 7.2, HMD Global has kept its promise to roll out the Android 10 update according to the roadmap published by the OEM. The COVID-19 outbreak has delayed the rollout a bit, but leaked beta builds suggest that updates for the Nokia 8 Sirocco as well as the Nokia 5.1 Plus are on their way.

Nokia 8 Sirocco XDA Forums || Nokia 5.1 Plus XDA Forums

In the past, similar beta builds for the Nokia 6.1, Nokia 6.1 Plus, Nokia 7 Plus, Nokia 7.1, and Nokia 9 PureView surfaced on the Internet before the official update rollout. XDA Senior Member hikari_calyx was the man behind those leaks, and he is also responsible for sharing the current set of beta builds as well. While the initial Android 10 update package for the Nokia 8 Sirocco dates back to January 2020, the Nokia 5.1 Plus Android 10 beta build has been built quite recently. The latter can also be installed on the China-exclusive Nokia X5, provided the unit has been cross-flashed earlier with the global Android One firmware.

nokia_5.1_plus_x5_android_10_leaked

The installation procedure is fairly simple for owners of the Nokia 8 Sirocco as the update packages can be sideloaded using the stock recovery image. Nokia 5.1 Plus users, however, need to acquire root privilege using the MediaTek-su exploit before attempting to play with the leaked Android 10 beta build. This particular requirement can be bypassed by unlocking the bootloader first, but HMD Global doesn’t provide any official method to achieve that on the Nokia 5.1 Plus.

Download internal Android 10 build for the Nokia 8 Sirocco

Download internal Android 10 build for the Nokia 5.1 Plus

It’s worth noting that flashing these beta builds on your phone may affect the warranty status. You might also encounter some unforeseen bugs or face issues while rolling back to the stable channel in the future, so we would advise caution before tinkering with your daily-driver.


Thanks to XDA Senior Member hikari_calyx for the screenshot (via Twitter)!

The post Android 10 internal beta leaks for the Nokia 8 Sirocco and Nokia 5.1 Plus appeared first on xda-developers.



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

How to rebrand the Sprint OnePlus 7 Pro 5G with EU firmware to try out OxygenOS Open Betas

OnePlus made its official debut in the US market with the T-Mobile-branded OnePlus 6T. Since then, the OEM has continued its collaboration with T-Mobile as well as teamed up with Sprint for the OnePlus 7 Pro 5G. While the increased availability of OnePlus phones in the U.S. is a plus, the downside is the negative impact on software update frequency. Even worse is that U.S. 5G OnePlus phones are not eligible for the OxygenOS Open Beta Program. XDA Senior Member Whoareyou has now killed two birds with one stone: He came up with a method for converting the Sprint OnePlus 7 Pro 5G to the international/European firmware without unlocking the bootloader, and he has also ported the Open Beta firmware from the 4G variants.

OnePlus 7 Pro XDA Forums

Although Sprint has yet to offer an official bootloader unlock tool for the OnePlus 7 Pro 5G, owners of the phone can opt for an unofficial method earlier created by Whoareyou. It is possible to flash a modified EU firmware afterward, but doing so breaks SafetyNet Attestation thus DRM-protected HD videos from streaming services such as Netflix and Prime Video are not accessible, among other things.

The latest version of the ‘hack’, on the other hand, will not break SafetyNet. Sprint users might face some APN related issues, and the About Phone section is broken, but otherwise, the conversion procedure is pretty seamless. The steps are noted below.

  1. Unplug and completely power off the phone.
  2. Download and open the modded MSM download tool.
  3. Uncheck SHA256 check.
  4. Connect your USB cable to your PC.
  5. Hold Volume DOWN and UP at the same time.
  6. While holding those keys, insert the USB.
  7. Keep holding those keys, click ‘Enum’ in the tool.
  8. Click on ‘Start’.
  9. Wait about 5-10 minutes, setup over Wi-Fi, accept the Android 10 OTA and you’re done.

Convert Sprint OnePlus 7 Pro 5G to European firmware — XDA Thread

Talking about the Open Beta port, it is based on the latest Open Beta 11 build for the regular OnePlus 7 Pro. The package can be installed on both European OnePlus 7 Pro 5G units (with model number GM1920) and Sprint units (with model number GM1925). The About Phone section won’t be populated properly and Verizon’s Visible MVNO is unsupported by this ported firmware, but users can finally get a taste of bleeding-edge features such as the Instant Translation service.

Oxygen OS Open Beta for OnePlus 7 Pro 5G — XDA Thread

To restore the factory firmware, please refer to the device-specific unbrick thread: EU, Sprint.


Thanks to XDA Senior Member Some_Random_Username for the tip!

The post How to rebrand the Sprint OnePlus 7 Pro 5G with EU firmware to try out OxygenOS Open Betas appeared first on xda-developers.



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

vendredi 10 avril 2020

Google Phone app can now be installed on some non-Pixel phones from the Play Store

The Google Phone app is Google’s default dialer application that’s pre-installed on Pixel smartphones, Android One smartphones, and more recently, Xiaomi smartphones sold in Europe. It isn’t usually possible to install the application on other devices without using either a modified application or a Magisk Module, but today we found out that the latest version of the app can be installed on certain devices straight from the Google Play Store.

We were first tipped off about this possibility by XDA Senior Member springer.music who said that the latest Google Phone app can be installed on the ASUS ZenFone 6 running the latest ZenUI update, version WW_17.1810.2003.144. Multiple users on the official ASUS ZenTalk forums also confirmed this possibility. Curious, I decided to see if I could install the app on some of my own devices. Lo and behold, I managed to hop onto the Google Play Store and download the app onto my OPPO Find X2 Pro running ColorOS 7.1. Specifically, the version I installed was version 47.0.305350684-publicbeta. When I first installed the Google Phone app, I was met with a warning that phone calls may not work because the device was “incompatible,” but after granting it various permissions and making it my default dialer app, I was able to successfully make and receive phone calls. Features such as Assisted dialing, Caller ID & spam, and Nearby places seem to be available, but Pixel-specific features like Call Screen are not.

XDA’s Max Weinbach also confirmed he could install the app on his LG V60 ThinQ and make and receive phone calls, but he was unable to install the app on his OnePlus 6T running OxygenOS or his Samsung Galaxy S20 Ultra running One UI 2.1. I was also unable to install the app on my OnePlus 7 Pro. This could be a sign that Google plans on expanding support for the Google Phone app to more devices, or it could just be that Google accidentally forgot to mark this update as incompatible with certain devices.

We briefly checked the Manifest and found that the app still requires the com.google.android.dialer.support shared library to be present. This shared library is not present on the Samsung Galaxy S20 which is why the app refuses to be installed on it. This library is, however, present on the OPPO Find X2 Pro and ASUS ZenFone 6, which might explain why the app can be installed on those devices. To check if this library is present on your own device, you can run the following ADB shell command:

pm list libraries | grep "com.google.android.dialer.support"

You can try downloading the latest version of the Google Phone app from the Google Play Store link below or from APKMirror. Let us know if the app works for you!

Phone (Free, Google Play) →

This article was updated at 5:45PM EST on April 10, 2020, to add more details about why the app seems to be compatible with more devices now. Another update at 6:05PM EST was made to add that the required shared library is present on the ASUS ZenFone 6 as well.

The post Google Phone app can now be installed on some non-Pixel phones from the Play Store appeared first on xda-developers.



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

LineageOS 17.1 based on Android 10 is now officially available

If you call yourself a custom ROM veteran, you definitely have heard about LineageOS. LineageOS traces its roots back to CyanogenMod, the custom ROM that became popular on the HTC Dream/T-Mobile G1, the first Android smartphone available for purchase. CyanogenMod, in turn, went on to become one of the most popular custom ROMs available across a plethora of devices, and several of the key developers and maintainers of the project went on to establish LineageOS when Cyanogen decided to stop supporting CyanogenMod. LineageOS picked up the reins with LineageOS 13.0 and LineageOS 14.1 releases, and the project has continued along over the years. Now, LineageOS is marking its major version bump up to LineageOS 17.1 with Android 10 as the base.

LineageOS XDA Forums

Why Lineage 17.1 and not 17.0?

Android 10’s source code made its way to AOSP in September 2019, and the LineageOS team has been hard at work to bring forward their ROM and its features to the new Android version base. AOSP, though, had undertaken massive refactoring in certain areas, which made porting over take longer than anticipated. AOSP also introduced features like the new Permissions Hub, which conflicted with the custom ROM’s PrivacyGuard feature, forcing them to drop it. Both of these changes meant that the team had to work harder and take more time for bringing up the ROM as a whole to Android 10.

Meanwhile, the December 2019 Android Security Bulletin was released by Google, and the LineageOS team decided to rebase on the more feature-filled Google Pixel 4/4XL tag of AOSP. Owing to this, the team has also decided to jump up on the subversion, going from 17.0 to 17.1. For the future too, if there is any large scale rebasing undertaken onto a different tag, the team will jump up on the subversion number.

As a consequence of this jump, the team will be locking all Lineage-17.0 branches to contributions on their Gerrit, and abandoning existing 17.0 changes. Developers are still free to cherry-pick changes to 17.1, though.


Administrative and maintenance changes

The jump up to official LineageOS 17.1 means that most of the current build resources will now focus on building these new updates for supported devices. This has the expected side-effect of diverting resources from older builds. With the 17.1 branch reaching feature and stability-parity with 16.0, it will become the most recent and most actively developed branch, with regular nightly builds for supported devices commencing from January 31, 2020. Consequently, 16.0 will be moved to weekly builds, while 15.1 will be deprecated from automated builds.

LineageOS 17.1 will launch building for a small selection of devices, with additional devices to come as they are marked as both Charter compliant and ready for builds by their maintainer.

The Lineage team is also bringing over focus to their Wiki refresh. The LineageOS Wiki was recently extended and device maintainers were given significantly more options to customize their device’s individual installation, update, and upgrade instructions. As of LineageOS 17.1, maintainers will be expected to run through the full instructions on their device wiki and verify that the information holds true for their device. This renewed focus on the wiki is in light of the building up changes to AOSP, such as System-As-Root, A/B Partition Scheme, and Dynamic Partitions, which have the combined effect of obsoleting the instructions many of us have been following for years from memory — those instructions are now either no longer valid or are missing very critical steps. For example, the Heimdall (Samsung flashing tool) instructions were horribly outdated, so these have been updated to reflect new information. So if you are making the jump to LineageOS 17.1 or are just generally interested in custom ROMs, it would still be a good idea to check out your device’s Wiki page.


New features in LineageOS 17.1

LineageOS 17.1 brings over several new features to the ROM family:

  • New partial screenshot UI that lets you hand-select smaller parts of your screen and edit the screenshots.
  • New adapted ThemePicker app from AOSP, with support for the usual range of accents, font change, icon (both QuickSettings, and Launcher) shape, and icon resource changes (eg. changing the shape of the Wi-Fi/Bluetooth icons).
  • Use fingerprint sensor to hide and protect apps within Trebuchet Launcher
  • Merge October, November, December 2019, January 2020, February 2020, and March 2020 security patches.
  • Wi-Fi Display is available once again.
  • Support for on-screen fingerprint sensors (FOD) added.
  • Support for pop-up and rotating cameras added.
  • WebView updated to Chromium 80.0.3987.132.
  • ROM is currently based on AOSP’s android-10.0.0_r31 tag, which is the Pixel 4/4 XL’s tag.

Further changes

Lineage Recovery

Lineage is also making the switch to Lineage Recovery as the defacto solution to install LineageOS. Lineage Recovery will be built by default for all officially supported devices. The team mentions that this change was done purely to streamline their own processes and not to dissuade users away from other custom recoveries. Device maintainers retain the freedom to recommend alternative recovery on their device’s Wiki page alongside full instructions for usage.

AOSP’s Permission Hub and LineageOS’s PrivacyGuard

We’ve talked about this change in the past, and now the change is finally here. LineageOS 17.1 drops support for the homebrewed PrivacyGuard implementation in favor of AOSP’s Permission Hub as the team was unable to port the PrivacyGuard framework to Android 10. Google did not release Permissions Hub with Android 10, but the code for it still exists within AOSP. So, the Lineage team forked it and now presents that as the solution as it is claimed to be almost equivalent in features, but conflicted in attempts to co-exist alongside PrivacyGuard.

Rooting — no addonsu binary support

As a byproduct of the removal of PrivacyGuard and the switch over to Permission Hub, the addonsu binary that was usually offered as a simple root access solution is no longer feasible, as we had informed before. Users interested in root have the option to use ADB root, or flash compatible third-party solutions such as Magisk. The team clarifies that this does not mean that any particular third-party solutions are endorsed as officially supported — so you still need to be mindful of the root solution working harmoniously with your ROM.

Deprecation of Styles API

The Styles API is also now getting deprecated in favor of AOSP’s ThemePicker app. The team claims complete feature parity, and even feature superiority with ThemePicker.


Upgrade instructions for LineageOS 17.1

If you are on official LineageOS 16 and your device is present on the list of officially supported devices for LineageOS 17.1, you would still need to manually update your device as per instructions present on your device’s specific wiki page. The LineageOS updater app generally does not support upgrades from one version of LineageOS to another, so users have to make a conscious decision to update instead of being surprised by an OTA.

Device-specific instructions can vary, but for most devices we checked, the update instructions rely on using the adb reboot sideload command, and then adb sideload /”filepath” command. The Lineage team also mentions that updating within the official release channel builds does not require the user to wipe their device; but moving from an unofficial build to official LineageOS will require a device wipe from recovery.

It is very likely that you will be able to install LineageOS through a custom third-party recovery, but that is not the recommended upgrade method from the developers, so your mileage may vary on a per-device basis. Be sure to check your device’s wiki, its support page, and our own forums to ensure that you follow the correct methods to upgrade to avoid any issues.

You should also note that your ROM installation will not include Google Apps, for the simple reason that those apps are proprietary. You need to sideload a separate GApps package, with a heavy preference towards the GApps package recommended by your device maintainer/developer, because of the reasons we explain in a separate PSA. As a side note, Open GApps also released their official Android 10 flashable packages recently.

Your ROM will also not ship with a default root solution, as we explain in the preceding paragraphs. You need to separately flash third-party solutions.


LineageOS 17.1 – Official builds for supported devices

The following is the official build roster for batch 1 of the LineageOS 17.1 rollout:

Device and Forum Link Device codename and Wiki Link Maintainer
ASUS Zenfone 6 (ZS630KL) I01WD luca020400, OrdenKrieger
BQ Aquaris X bardock eloimuns, Quallenauge, Team aquaris-dev
BQ Aquaris X Pro bardockpro Quallenauge, Team aquaris-dev
Fairphone FP2 FP2 chrmhoffman
Google Nexus 6 shamu Elektroschmock, npjohnson
Google Pixel sailfish intervigil, razorloves
Google Pixel XL marlin intervigil, razorloves
HTC One 2014 m8 bgcngm
HTC One 2014 Dual-SIM m8d bgcngm
LG G2 (AT&T) d800 Kapricomus, Arnau, YoDevil
LG G2 (T-Mobile) d801 Kapricomus, Arnau, YoDevil
LG G2 (International) d802 Kapricomus, Arnau, YoDevil
LG G2 (Canadian) d803 Kapricomus, Arnau, YoDevil
LG G3 (AT&T) d850 firebird11, HardStyl3r
LG G3 (Canada) d852 firebird11, HardStyl3r
LG G3 (International) d855 firebird11, HardStyl3r
LG G3 (Korea) f400 firebird11, HardStyl3r
LG G3 (T-Mobile) d851 firebird11, HardStyl3r
LG G3 (Verizon) vs985 firebird11, HardStyl3r
LG G5 (Global) rs988 npjohnson
LG G5 (International) h850 npjohnson
LG G5 (T-Mobile) h830 npjohnson
LG V20 (AT&T) h910 npjohnson
LG V20 (Global) h990 npjohnson
LG V20 (Sprint) ls997 npjohnson
LG V20 (T-Mobile) h918 npjohnson
LG V20 (US Unlocked) us996 npjohnson
LG V20 (Verizon) vs995 npjohnson
Motorola Moto Z griffin DD3Boh, erfanoabdi, shr3ps, stargo, vache
Motorola Moto G6 Plus (XT1926-2/3/5/6/7/8/9) evert Jleeblanch
Motorola Moto G7 river erfanoabdi, Nolen Johnson (npjohnson), SyberHexen
Motorola Moto G7 Plus (XT1965-2/3/6) lake Jleeblanch
Motorola Moto X4 payton erfanoabdi
Motorola Moto Z2 Force nash erfanoabdi, npjohnson
Motorola One Power (XT1942-1/2) chef Hasaber8
OnePlus 3/3T oneplus3 dianlujitao
OnePlus 6 enchilada luca020400, LuK1337
OnePlus 6T fajita LuK1337
OnePlus 7 Pro guacamole LuK1337, Tortel
Razer Phone cheryl mikeioannina
Samsung Galaxy S4 Active (GT-I9295) jactivelte arco, npjohnson, side
Samsung Galaxy S4 (SGH-I337) jflteatt arco, npjohnson, side
Samsung Galaxy S4 (SCH-R970/C/X,  SPH-L720) jfltespr arco, npjohnson, side
Samsung Galaxy S4 Value Edition (GT-I9515/L) jfvelte arco, npjohnson, side
Samsung Galaxy S4 (SCH-I545) jfltevzw arco, npjohnson, side
Samsung Galaxy S4 (GT-I9505/G, SGH-I337M, SGH-M919) jfltexx arco, npjohnson, side
Samsung Galaxy Tab S5e Wi-Fi (SM-T720) gts4lvwifi bgcngm, LuK1337
Sony Xperia 10 kirin LuK1337
Sony Xperia 10 Plus mermaid LuK1337
Sony Xperia XA2 pioneer cdesai, LuK1337, Stricted
Sony Xperia XA2 Ultra discovery LuK1337
Xiaomi Mi 6 sagit ArianK16a, Elektroschmock
Xiaomi Mi 8 dipper infrag
Xiaomi Mi Mix 2 chiron mikeioannina, wight554
Xiaomi Mi Mix 2S polaris bgcngm
Xiaomi POCO F1 beryllium bgcngm, warabhishek
Lenovo ZUK Z2 Plus z2_plus DD3Boh

More devices should be making the transition soon to LineageOS 17.1, so keep an eye on our frontpage as we will run regular stories on the same.


New features in LineageOS 16.0 branch

In addition to the latest branch, the older LineageOS 16.0 branch is also seeing a few major changes:

  • Wi-Fi display is available once again.
  • You may now route the hotspot connections through the device’s VPN.
  • Support for on-screen fingerprint sensors (FOD) added.
  • Support for pop-up and rotating cameras added.
  • Merge July, August, September, October, November, December 2019, January 2020, February 2020, and March 2020 security patches.
  • WebView updated to Chromium 80.0.3987.132.
  • It is now possible to compile LineageOS 16.0 on macOS.

LineageOS 16 – Official builds for supported devices

While maintainers work towards bringing up devices to official LineageOS 17.1 based on Android 10, you can still find automated weekly builds for these devices that are supported for LineageOS 16:

LineageOS 16 Official Build List. Tap/click to expand.

Device and Forum Link Device codename and Wiki Link Maintainer
ASUS ZenFone 3 (ZE520KL, ZE552KL) zenfone3 makorn645
Asus Zenfone Max Pro M1 X00TD SagarMakhar
Asus Zenfone Max Pro M2 X01BD Bauuuuu, kubersharma001
BQ Aquaris X bardock eloimuns, Quallenauge, Team aquaris-dev
BQ Aquaris X Pro bardockpro Quallenauge, Team aquaris-dev
BQ Aquaris X2 zangya eloimuns, Kra1o5, Team aquaris-dev
BQ Aquaris X2 Pro zangyapro eloimuns, Kra1o5, Team aquaris-dev
Essential PH-1 mata haggertk, intervigil, jrior001, rashed
Fairphone 2 fp2 chrmhoffmann
Google Nexus 6 shamu Elektroschmock, npjohnson
Google Pixel sailfish intervigil, razorloves
Google Pixel XL marlin intervigil, razorloves
Honor 5X kiwi BadDaemon, dobo, joelh
Honor View 10 berkeley LuK1337
Huawei P20 Pro charlotte LuK1337
LeEco Le 2 s2 codeworkx, Rk585
LeEco Le Max2 x2 tortel, ThEMarD
LeEco Le Pro3/Le Pro3 Elite zl1 codeworkx
Lenovo P2 kuntao mikeioannina, highwaystar
Lenovo Yoga Tab 3 Plus YTX703F Quallenauge, Vladimir Oltean
Lenovo Yoga Tab 3 Plus LTE YTX703L Quallenauge, Vladimir Oltean
Lenovo ZUK Z1 ham sb6596
LG G3 (Sprint) ls990 firebird11, HardStyl3r
Motorola Moto G7 river erfanoabdi, npjohnson, SyberHexen
Motorola Moto X 2014 (XT1092/3/5/6/7) victara linckandrea, Tortel
Nextbit Robin ether javelinanddart, mikeioannina, npjohnson
Nubia Z17 nx563j BeYkeRYkt
OnePlus One bacon jrior001, npjohnson
OnePlus 2 oneplus2 OzzysCmAcc, aviraxp
OnePlus 3 oneplus3 dianlujitao
OnePlus 5 cheeseburger codeworkx, jrizzoli, xingrz, amartinz, jumoog
OnePlus 5T dumpling amartinz, codeworkx
OPPO F1 (International) f1f highwaystar
OPPO Find 7a/7s find7 mikeioannina
OPPO R5/R5s (International) r5 maniac103
OPPO R7s (International) r7sf celoxocis
OPPO R7 Plus r7plus maniac103
Realme 3 Pro RMX1851 karthick111, nibaji, darshan1205
Samsung Galaxy A3 2016 (SM-A310F/M/N0/Y) a3xelte danwood76, Stricted
Samsung Galaxy A5 2016 (SM-A510F/M/Y/K/L/S/8) a5xelte danwood76, Stricted
Samsung Galaxy A5 2017 (SM-A520F/DS/W) a5y17lte filiprrs, raymanfx
Samsung Galaxy A7 2017 (SM-A720F/DS) a7y17lte filiprrs, raymanfx
Samsung Galaxy Note 3 (SM-N9005/P) hlte haggertk, npjohnson
Samsung Galaxy Note 3 (SM-N9008V) hltechn haggertk, npjohnson
Samsung Galaxy Note 3 (SM-N900K/L/S) hltekor haggertk, npjohnson
Samsung Galaxy Note 3 (SM-N900T/V/W8) hltetmo haggertk, npjohnson
Samsung Galaxy S III Neo Dual-SIM (GT-I9300I) s3ve3gds fcuzzocrea, PythonLimited
Samsung Galaxy S III Neo Samsung Camera(GT-I9301I/Q) s3ve3gjv fcuzzocrea, PythonLimited
Samsung Galaxy S III Neo Sony Camera (GT-I9300I/Q) s3ve3gxx fcuzzocrea, PythonLimited
Samsung Galaxy S5 Active klteactivexx javelinanddart
Samsung Galaxy S5 LTE (G900AZ/F/M/R4/R7/T/V/W8,S902L) klte haggertk
Samsung Galaxy S5 LTE (G9006V/8V) kltechn haggertk
Samsung Galaxy S5 LTE (G900I/P) kltedv haggertk
Samsung Galaxy S5 LTE (SCL23) kltekdi haggertk
Samsung Galaxy S5 LTE (G900K/L/S) kltekor haggertk
Samsung Galaxy S5 LTE-A lentislte cvxda, sassman
Samsung Galaxy S5 LTE Duos (G9006W/8W) kltechnduo haggertk
Samsung Galaxy S5 LTE Duos (G900FD/MD) klteduos haggertk
Samsung Galaxy S5 Neo s5neolte danwood76, Stricted
Samsung Galaxy S5 Plus kccat6 cvxda, sassmann
Samsung Galaxy Tab S2 8.0 Wi-Fi (2016) gts28vewifi mccreary, syphyr, luca020400
Samsung Galaxy Tab S2 9.7 Wi-Fi (2016) gts210vewifi syphyr, luca020400
Sony Xperia Z3 z3 Tom1000, Myself5
Sony Xperia Z3 Compact (D5803/D5833) z3c ArianK16a
Wileyfox Storm kipper jrior001
Wileyfox Swift crackling jrior001
Xiaomi Mi 5 gemini bgcngm, defer, h2o64
Xiaomi Mi 5s capricorn LuK1337
Xiaomi Mi 5s Plus natrium LuK1337
Xiaomi Mi A1 tissot flex1911, TheScarastic
Xiaomi Mi Mix lithium balika011, blunden
Xiaomi Mi Note 2 scorpio joe2k01
Xiaomi Mi Note 3 jason dianlujitao
Xiaomi Redmi 3S/X land Isaac Chen
Xiaomi Redmi 4/X santoni Isaac Chen
Xiaomi Redmi Note 4 mido aryankedare
Yandex Phone amber HighwayStar, vm03

Much like LineageOS 17.1 builds, we should see more devices making their way onto the weekly LineageOS 16 build roster.


Support LineageOS

LineageOS is and has always been a community effort, riding on the back of volunteers dedicating their own resources for the general good of the community. If you want to contribute to LineageOS, there are multiple ways to do so.

Becoming a device maintainer

The primary way you can help LineageOS grow to more devices is to maintain the ROM for devices that you can. If you’re a developer and would like to submit your device for official support, you can follow the instructions present over here. Once you submit, you’ll receive some feedback on your submission. If it’s up to par, you will be invited to Lineage’s communication channels, and your device resources will be forked to LineageOS’s official repository.

Providing translations

Alternatively, you can also provide translations for different languages through Crowdin. The team mentions that even if your language is not officially supported in Android, you can reach out to the team and they’ll take steps to include your language. However, the team requests that you should submit translations only if you have reasonable proficiency in the language.

Donations

Running automated builds for such a wide roster of devices takes resources. You can contribute towards some of these costs by donating to LineageOS through their PayPal or Patreon.

Donate to LineageOS: via PayPal ||| via Patreon


This article was updated at 4:35 PM EST on April 10, 2020, to add the Google Nexus 6, Google Pixel, Google Pixel XL, BQ Aquaris X, and BQ Aquaris X Pro to the list of devices with official LineageOS 17.1 builds.

The post LineageOS 17.1 based on Android 10 is now officially available appeared first on xda-developers.



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

Google and Apple announce the Contact Tracing API and Bluetooth spec to warn users of COVID-19

Due to the ongoing threat posed by SARS-CoV-2, Google and Apple have teamed up to announce a new API and Bluetooth Low Energy specification called “Contact Tracing.” The idea behind contact tracing is to inform users if they’ve recently been in contact with someone who has been positively diagnosed with COVID-19. South Korea and Taiwan have successfully “flattened the curve,” as in they’ve limited the number of new cases to fall below the capacity of their healthcare systems, by implementing widespread testing and contact tracing. According to the Associated Press, several countries in Europe including the Czech Republic, the U.K., Germany, and Italy are developing their own contact tracing tools. Apple and Google hope to empower nations and medical organizations around the world with the ability to trace the spread of the novel coronavirus, but the two companies also recognize the potential privacy concerns with this pandemic containment method. That’s why the two companies have created the new API and Bluetooth spec “with user privacy and security central to the design.”

Google and Apple published blog posts and documents that outline their goals to roll out a new API and Bluetooth LE specification. Due to urgent need, both companies are tackling this problem in two stages. First, in May, both companies will release an API that “[enables] interoperability between Android and iOS devices using apps from public health authorities.” These apps will be made available for users to download on the Google Play Store and Apple App Store. Second, in the next few months, both Google and Apple will add support for a new Bluetooth Low Energy specification into Android and iOS. Google says that adding a Bluetooth LE Contact Tracing spec “is a more robust solution than an API and would allow more individuals to participate, if they choose to opt in, as well as enable interaction with a broader ecosystem of apps and government health authorities.”

Once an app integrates the new API or the BLE specification has been integrated into the OS, Android and iOS users can receive notifications if they’ve recently been in contact with someone who has been diagnosed with COVID-19. Notably, the BLE solution will not require the user to have an application installed, but if they choose to install one of the official apps, then the app can inform them on the next steps to take after they receive a notification. This will allow users to decide if they need to self-quarantine for 14 days or to seek testing and further medical intervention. Here is an example flow of what Google and Apple envision will be possible with this new Bluetooth LE spec:

Contact Tracing

An overview of COVID-19 contact tracing using Bluetooth Low Energy. Source: Google/Apple.

Here is what Google says about how they designed the new Android Contact Tracing API to protect user privacy and security:

  • Apps calling the API via the startContactTracing method are required to get user consent to start contact tracing. If this is the first time the API is being invoked, the user will be shown a dialog asking for permission to start tracing.
  • In order to be whitelisted to use this API, apps “will be required to timestamp and cryptographically sign the set of keys before delivery to the server with the signature of an authorized medical authority.” In other words, unauthorized COVID-19 apps will not be allowed to use this API.
  • If the user uninstalls the app, the stopContactTracing method “will be automatically invoked and the database and keys will be wiped from the device.”
  • The user, after having confirmed a positive diagnosis of COVID-19, must grant explicit consent to upload 14 days of daily tracing keys. A dialog will be shown to the user if the app calls the startSharingDailyTracingKeys method.
  • Users will be shown what date and for how long they were in contact with a potentially contagious person, down to increments of 5 minutes, but not who or where the contact occurred.

Here is how the new Contact Detection Service BLE spec will protect user privacy and security:

  • The spec does not require the user’s location or any other personally identifiable information. Location-use is completely optional and is only done after the user provides explicit consent.
  • Rolling Proximity Identifiers are changed every 15 minutes on average, which makes it “unlikely that user location can be tracked via Bluetooth over time.”
  • Proximity identifiers retrieved from other devices “are processed exclusively on device.” This means that the “list of people you’ve been in contact with never leaves your phone.”
  • It’s up to the user to decide if they want to contribute to contact tracing. Users who are diagnosed with COVID-19 must consent to sharing Diagnosis Keys with the server. There will be transparency about the user’s participation in contact tracing, and “people who test positive are not identified to other users, Google, or Apple.” In fact, this information “will only be used for contact tracing by public health authorities for COVID-19 pandemic management.”
  • In case you’re wondering, the Content Detection Service should not significantly drain the battery of a device if the hardware and the OS support “Bluetooth controller duplicate filters and other [hardware] filters” to “account for large volumes of advertisers in public spaces.” Scanning is “opportunistic,” meaning it can occur within existing wake and scan window cycles, but will also occur at a minimum of every 5 minutes.

Because the new Contact Tracing specs are designed with user privacy and security in mind, it’s debatable how effective they’ll be at limiting the spread of COVID-19. According to The Verge, such opt-in, non-invasive contact tracing measures may have limited effectiveness. The issues boil down to a lack of widespread adoption by the population and a potentially large number of false-positive Bluetooth proximity events. Still, I hope this new initiative is successful. It’s rare to see Google and Apple collaborate on anything, but desperate times call for desperate measures.

Sources: Google Blog Post, Overview of COVID-19 Contact Tracing, Contact Tracing BLE Spec, Contact Tracing Cryptography Spec, Android Contact Tracing API Spec,

The post Google and Apple announce the Contact Tracing API and Bluetooth spec to warn users of COVID-19 appeared first on xda-developers.



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

Latest Google App beta adds “Search Tools” filters and tests revamped Assistant settings

The Google App is a core part of Google Mobile Services because it contains Google Search, Google Discover, Google Podcasts, Google Assistant, and Google Lens. Google has packed so much into the app that there are always minor tweaks and A/B tests that we tend to gloss over. In the last few versions of the Google App beta, though, there have been some noticeable new features and design tweaks that we wanted to bring your attention to.

New Search Tools Filters

The first tweak we wanted to bring up, which was spotted earlier today by 9to5Google, is the addition of “Search Tools” in the mobile Google search site. If you open the search tab and enter a search query, you can scroll to the right until you see “Search Tools.” Here you can filter by time (Any Time, Past Hour, Past 24 Hours, Past Week, Past Month, or Past Year) or by results (All Results or Verbatim.) Previously, you had to open Google search in Google Chrome or another browser in order to search with these filters enabled.

Google App beta Search Tools Google App beta Search Tools Google App beta Search Tools

These Search Tools filters are available with Google App beta version 11.4 but are not yet available in the stable channel.

Revamped Google Assistant Settings

Google Assistant settings in the Google App are currently split up into 4 separate tabs: You, Assistant, Services, and [Name’s] Home. In recent versions of the Google App, however, Google has been testing a rearranged version of the Assistant settings page that places all of the settings into a single column. 5 of the most frequently accessed settings are pinned to the top, however. These include Routines, Music, Basic info, Languages, and Voice Match. Below these 5 settings are two cards for “You” and “Devices” which link to their respective settings. Lastly, the remaining settings can be accessed by tapping on the “view more” button at the bottom.

Image credits: Abner Li @ 9to5Google

These rearranged Assistant settings have appeared for a few writers at 9to5Google, but they have not yet widely rolled out for those on the latest Google App beta version.

The post Latest Google App beta adds “Search Tools” filters and tests revamped Assistant settings appeared first on xda-developers.



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