LightBlog

jeudi 8 octobre 2020

Samsung launches the Galaxy F41 with an Exynos 9611 and 6000mAh battery

Samsung on Thursday introduced the Galaxy F41 in India, in what the company is describing is a device for “the lifestyle of young Gen Z and millennial consumers.” The device was developed in partnership with India’s Flipkart and is the first under the new mid-range F Series.

The Galaxy F41 features a 6.4-inch Full HD+ sAMOLED Infinity U display (meaning it has a notch), a 6000mAh battery, and a triple-camera setup. There’s a main 64MP camera, an 8MP ultra-wide lens, and a 5MP depth lens for portrait shots. Samsung said the Galaxy F41 supports the company’s “Single Take” feature that takes ten different pictures — seven photos and three videos — with a single click.

Samsung Galaxy F41 colors

The device also comes equipped with an Exynos 9611 Octa-core processor, 6GB of RAM, and up to 128GB of internal storage that can be expanded to 512GB. The whole package features a glossy gradation back panel that comes in Fusion Black, Fusion Blue and Fusion Green.

Additionally, the device comes equipped with a rear fingerprint sensor, supports face unlock, and features Android 10 with One UI 2.

Samsung Galaxy F41 Forums

Samsung Galaxy F41 Specifications

Samsung Galaxy F41 Specs
Display 6.4-inch Full HD+ sAMOLED Infinity U
Camera
  • 64MP main lens
  • 8MP ultra-wide angle lens
  • 5MP depth sensor
Memory
  • 6GB + 64GB of storage
  • 6GB + 128GB of storage (expandable to 512GB)
Battery 6000mAh
Processor Exynos 9611 Octa-core
OS Android 10 with One UI 2

The Galaxy F41 will launch for ₹16999 on October 16 and be available on Flipkart, Samsung.com, and select retail stores; the version with more internal storage costs ₹17999. To celebrate the device’s launch, there are a number of promotions worth noting. During Flipkart Big Billion Days, you can get a discount on the Galaxy F41, bringing the price down to INR 15499 and INR 16499, respectively. And if you use an SBI credit or debit card during Flipkart Big Billion Days, you can get an additional 10% off.

Consumers can also take advantage of the Flipkart Smart Upgrade program, which Samsung said will only require users to pay for 70% of the device value. The plan will be available for payments made through credit card and EMI, and consumers can then upgrade to a new phone on Flipkart after 12 months.

    Samsung Galaxy F41
    The Galaxy F41 continues Samsung's successful formula of marrying a mid-range processor with capable cameras and a big battery.

The post Samsung launches the Galaxy F41 with an Exynos 9611 and 6000mAh battery appeared first on xda-developers.



from xda-developers https://ift.tt/3nvYiGD
via IFTTT

Hands-on with Night Mode in Google Camera Go: Democratizing Low-Light Photography

If there’s one area Google’s Pixel smartphones remain undefeated, it is definitely in camera software. Most of the magic in the Google Camera app happens on the software side. Even though the tech giant continues to use the same 12.2MP primary camera on its smartphones since the Pixel 2, the software algorithms backing the Google Camera’s phenomenal “computational photography” keep improving significantly with each new Pixel smartphone. Google’s incredible camera processing has inspired developers, including some of the most notable personalities on the XDA-Developers forums, to modify the Google Camera app to run on non-Google smartphones. Similarly, for low-end and budget devices, developers have also ported Google Camera Go, a lightweight version of Google’s camera app for Android (Go Edition) devices, which was recently updated with a Night Mode.

Night Mode, as you would expect, is analogous with Night Sight in the full Google Camera app. We tried out Camera Go’s Night Mode using a modified version of the app courtesy of developer and XDA Senior member mickey36736, better known as Wichaya in the GCam modding community. The latest Google Camera Go (version 1.8.332394960) APK was extracted from the Google Play Store by XDA Senior Member RKBD, but Night Mode does not show up if you sideload this version. Wichaya modified the APK to activate Night Mode, and that’s what we are using to test.

Note: Night Mode in the Google Camera Go app is currently exclusive to the Nokia 1.3 Android Go smartphone, but we’re using the mod on the Nokia 5.3. This article serves as a demonstration of the Night Mode feature in Camera Go rather than a review of the camera quality of the Nokia 1.3, which we do not have on hand.

Night Mode in Google Camera Go

The Google Camera Go app was first introduced earlier this year alongside the Nokia 1.3. It’s designed for low-end devices with single cameras, so it comes with a simple interface with basic features like face enhancement, photo, video, a portrait mode, and a built-in visual translator. The latest update to the app adds Night Mode, though Google is also preparing to add HDR support to the app.

HDR is not yet enabled in the modded version of the app by Wichaya (perhaps because Google themselves haven’t finished it), but Night Mode works on most of the devices we tried it on — even though we cannot ensure support on all modern devices. The new APK weighs only 16MB in size, ideal for a low-end device with limited storage. The mod also appears to have the Night Mode processing library, called “libNightMode_jni.so” and 7.1MB in size, within the APK itself.

I took the Nokia 5.3 running Google Camera Go out for a spin last night and tested it in different low-light conditions to see how well it fares. The following are some of the examples:

Night Mode Off (left) vs On (right)

Very evidently, the Night Mode on Google Camera Go improves the lighting significantly in all scenarios. Besides illuminating the scenes, Night Mode also helps improve the sharpness in the images. Despite this, there may be some instances of fairly low brightness where the Camera Go app fails to focus. There is a fair bit of noise in all the shots, primarily due to the high ISO values.

Notably, while the images without Night Mode are taken at 12MP, the images with Night Mode on are snapped at just 2MP and that is presumably to keep the image size low. Furthermore, reading into the EXIF data reveals that the exposure time is 3-4 times higher with the Night Mode than without it.

While the resulting images with Night Mode on the Google Camera Go aren’t incredibly impressive, we have to keep our expectations in check—Night Mode in Google Camera Go isn’t meant to be on par with Night Sight on the regular Google Camera, and expecting as such is only setting yourself up for disappointment. The results, when considering them on their own, are exciting due to the fact the app is intended for devices much lower in the price bracket.

You can find all of the images above and some more in the Flickr gallery shared below.

Google Camera GO Night Mode

What are your thoughts on the Night Mode on the Google Camera Go? Let us know in the comments below!

The post Hands-on with Night Mode in Google Camera Go: Democratizing Low-Light Photography appeared first on xda-developers.



from xda-developers https://ift.tt/30LRSJU
via IFTTT

HMD Global rolls out the Android 10 update to the Nokia 3.1 and Nokia 5.1

Amidst all of the talk about Android 11 updates, some people forget that OEMs are still working on updating their smartphones to Android 10. For example, HMD Global was expected to conclude its Android 10 rollout by Q2 2020, but they unfortunately missed the timeline. The company worked hard over the last few months clearing the backlog and they are now back on track. Just a day ago, we learned that owners of the Nokia 3.1 should look forward to the Android 10 update notification, while a similar update for the Nokia 5.1 should be ready within 24 hours. In keeping with its promise, HMD Global has now started rolling out the Android 10 update to the Nokia 5.1.

Nokia 3.1 XDA Forums ||| Nokia 5.1 XDA Forums

Both the Nokia 3.1 and the Nokia 5.1 debuted with Android 8.1 Oreo, which means the smartphones have now secured their second major Android OS update. Nokia says the OTAs will be rolled out in a phased manner. The first 10% of the userbase will receive the update on the first day, with the rollout steadily expanding to more users in the following days. The initial wave starts in the following regions:

  • Armenia
  • Azerbaijan
  • Bangladesh*
  • Belarus
  • Georgia
  • India
  • Kazakhstan
  • Laos*
  • Malaysia*
  • Mongolia
  • Morocco*
  • Nepal*
  • Philippines*
  • Singapore*
  • Sri Lanka*
  • Thailand*
  • Tunisia*
  • Ukraine
  • Uzbekistan
  • Vietnam*

* indicates a country where only the Nokia 3.1 receives the update, but not the Nokia 5.1

The updates bring along all the standard Android 10 features such as system-wide-dark mode, a new gesture navigation system, Smart Reply, revamped location and privacy controls, new Digital Wellbeing tools with Parental controls and much more. The Android Security Patch Level (SPL) has also been bumped to September 2020.

nokia_5.1_android_10_ota

Thanks to Nokia Community member .SJ for the screenshot!

As mentioned earlier, Android 10 is the Nokia 3.1 and 5.1’s second OS update and the device duo will receive no further OS updates from the OEM. HMD Global, however, allegedly plans to release stable Android 11 updates for several other devices in its lineup starting from Q4 2020.


Source: Nokia Community (1, 2)

The post HMD Global rolls out the Android 10 update to the Nokia 3.1 and Nokia 5.1 appeared first on xda-developers.



from xda-developers https://ift.tt/34CdLw7
via IFTTT

How OnePlus designed OxygenOS 11 to make bigger phones easier to use

Android 11 is here, and it brings along the waiting game for updates that Android users have grown accustomed to, in the past 11 years. The update situation has certainly improved though, thanks to efforts like Project Treble. Google is also sharing the Android source code with OEMs before release, allowing them to prepare an update to roll out to their users right around the time when Google rolls it out for the Pixels. If you have the OnePlus 8 or OnePlus 8 Pro, you can install OxygenOS 11 Open Beta 1 on your device to experience not only the latest version of Android but also the latest version of OnePlus’ custom UX skin.

OxygenOS 11 on the OnePlus 8 Pro – Hands-on with OnePlus’s Android 11 update

OxygenOS 11 brings along a fair few changes to OnePlus’ famed skin. There’s the widely requested Always On Display feature that has finally made an appearance with this update. You also get Android 11’s Conversation separator in the notifications shade, a redesigned weather app, a mistouch prevention feature in Game Space, improvements to Zen Mode, and UX changes to all other stock apps that make them easier to use with one-hand.

Download the OxygenOS 11 Live Wallpaper on any Android device

While users finally get to enjoy the Always On Display on their flagship phones, the initial reaction from many in the community was that OxygenOS 11 resembled what Samsung has been trying to do since One UI 2.0. One UI 2.0 shifted the design philosophy in favor of a larger “focus” block towards the bottom of the display while keeping the “viewing area” at the top, making the interface easier to use. OnePlus’ redesigned stock app experiences come close to the same lines, as a lot of people argued.

We had the opportunity to interview Mr. Sam Twist, Senior Product Manager for the OxygenOS team at OnePlus, to whom we put forth the same thoughts.

“With OxygenOS 11, we set out to continue doing what we have been doing since its inception in 2015. It’s about creating a fast, lightweight, highly customizable, and yet a simple user interface and operating system, and pairing that with simple aesthetics that people can use and understand. With OxygenOS 11, it’s is a bit more about smart and intuitive features that users from our forums, people in the media have been demanding for some time.

We’re aware of the comments early-on regarding the comparisons. But for us, to reach where we are right now, the journey was data-driven, community-driven, and also driven by the intuition of the great team at OnePlus — talented designers, product managers, and software engineers.”

OxygenOS 11 and One-Handed Use

Sam offered to give us a better look at the journey. It begins with hardware, as one would expect. Phones have become bigger through the years, coming through as a natural demand from consumers who now use them for tasks beyond just calling and texting. Beyond this, there is also a rise in content consumption and interaction — more than what it was a year or two ago. The hardware team believed that the screen is the king, but there was a pretty obvious problem in that vision: people’s hands aren’t really growing. So settling on a comfortable width became an important decision, one that then gets supplemented by a change in height and aspect ratio to fulfill the demands of a bigger screen and larger content area.

The software team joins the journey at this stage, and they do so by looking at anthropometric data, which refers to data related to human measurements. The team collects data related to measurements like the average hand size across key regions, and then further expands into how this correlates to touchpoints and interactions areas on the device’s display for both the hands. As one would expect, you can figure out how far someone can reach with their thumb with their dominant hand, which can be either left or right. This becomes the building block for OxygenOS 11’s update and its focus on better one-handed use.

About 65% of the display is within easy reach, Sam explained, so it makes sense to have most of your interactions within this area. The rest of the display is better utilized for displaying non-interactive content and information. As OnePlus’ research suggested to them, a lot of people use their phone in a flow that goes like: pick up with one hand -> interact for a short period -> put the phone down. Obviously, there are going to be instances when you need to get tasks done with both the hands (and thumbs) available, but a fair few of these use cases also go through the first flow — only once you have realized that you cannot comfortably reach all interaction areas, does the second hand come into the picture.

With OxygenOS 10.5 on the larger displays, we realized that one-handed use was not very intuitive, and we wanted to make something that people could use really easily with one hand.

The design team then builds upon this philosophy and pairs it with the simple aesthetics and the demands of the people. This is how OxygenOS 11 came to be in its current form.

One-handed reachability beyond landing pages

With this being said, we raised further questions. If OxygenOS 11 places prime focus on the ease of one-handed use, why not extend this driving philosophy across the UX and not just restrict it to landing pages? What we noticed in the new update is that a lot of these reachability changes remained restricted to the first page of the app. The philosophy did not percolate further below, and interactions beyond the landing page would bring back the need for the second hand coming into the picture. For instance, the new Weather app has the option to change the city placed on the top app bar, along with the overflow menu that contains the Settings option. The Notes app has a reachable landing page, but when you go to create a note, other options rest on the top once again. The experience feels incomplete, we argued, as the intention to go one-handed does not flow through the whole app.

Sam responds to this by firstly accepting that since this is still very much a beta release, the team at OnePlus is actively gathering feedback. Sam also concedes that this break in one-handed usability flow was a decision that needed to be made. Picking up the Notes app as an example, the top-level (landing page) is intended to be one-handed. The top-level is often accessed when the focus of the user is split between using their phone alongside other tasks — the phone is just a momentary tool in that instance, and information needs to be easily viewable and touchpoints quickly accessible with one-hand. If the user chooses to engage further, the focus shifts in weight towards the phone, and the second hand coming in is a stronger probability.

As for the Weather app, Sam pointed out that you can swipe on the display to cycle through the set locations. We didn’t know that, so that’s neat. For tasks like adding a city or going into the settings, OnePlus determines this to be the tipping point for user engagement, where the user is comfortable interacting with their phone in a more concentrated and focused fashion, and wouldn’t mind bringing in their other hand.

We suggested bringing down the buttons on the app’s bottom bar. There are a few touchpoints on the bottom bar on the Notes app, for instance. OnePlus has played around with layers during their designing process, with plenty of A/B testing across various designs, and this is what they settled on when taking into account their data-driven approach. Flipping the whole UX to be bottom-origin also doesn’t make complete sense either — users have come to expect certain interaction points, like the hamburger menu and the overflow button, at certain locations, and a completely radical overhaul will be jarring to a lot of users. The sweet spot is in the balance.

A dedicated one-handed mode?

With that being said, why doesn’t OnePlus consider adding in a dedicated one-handed mode instead? Several OEMs in their custom UX skins have a dedicated one-handed mode. Once activated, the entire content and interaction area shrinks down, making it easier to reach even the top app bars with one hand. A dedicated mode like this would make sense with the direction that OxygenOS 11 is taking.

Sam believes that a more bold approach to one-handed reachability was the need of the hour, rather than simply shrinking every UI element down into a smaller area. The changes in OxygenOS 11 present more information and give it greater visibility vis-a-vis the same on OxygenOS 10.5. So the space that other OEM solutions left blank when shrinking down the entire content area, can be better utilized to show information in a better and clearer format.

The bolder approach opened the door for OnePlus to go for a different font that made it easier to glance through the information, without necessitating engagement if the user did not want to engage. This means bigger titles, contrasting colors, and more on landing pages. And for pages at the second level when a user chooses to engage, the UX can adapt to expect that engagement. A simplistic shrink-down would not be able to achieve this.

But why not just make smaller phones then?

If a simplistic shrink down leaves out so much empty display space, why not make smaller phones? Smaller displays and device dimensions would remove the need for software to adapt to one-handed solutions. If you can already use your entire phone with one hand, you wouldn’t need a one-handed mode or a bold refocus.

Sam agreed that this was a good question. The industry is engaged in an arms-race on phone sizes, with every new generation superseding the previous when it comes to size, and there’s no clear end in sight. A larger display brings with itself tangible benefits that cannot be overlooked, and the OS (/UX) needs to adapt to better serve the needs that change every hour. It’s about finding the balance that brings about the burdenless experience towards the best of both worlds: a large display and the ability to comfortably use the phone.

OnePlus Sans font

The conversation turned to fonts. On OxygenOS 11, OnePlus has introduced a new font called OnePlus Sans that replaces the previous OnePlus Slate from 2017. Google actually mandates that OEMs ship their phones with Roboto as the default font on Android 11 as per the terms of the CDD. We inquired on what brought about the decision to switch over to the OnePlus Sans, considering that the OnePlus Slate was included already and Roboto remains the default anyway.

OnePlus Sans is part of our logo change, and part of bringing our brand into the 21st century and making an impact with users. It hadn’t changed for a long time, and if you look at other tech companies and forward thinking companies, we were feeling a little bit outdated. So this move [shift to OnePlus Sans] was part of the whole refresh package and future-proofing the brand and bringing it more in line with what people expect out of a leading tech company.

What is OxygenOS, really?

This question that we posed requires some context. It is no secret that Google has been chipping away functionalities from AOSP and delivering them through proprietary solutions like the Google Play Services framework instead. The move was borne out of a need to do something concrete about Android’s fragmentation problem, but the resultant solution invariably involved taking away the OEM’s role in Android as an OS and the changes that their “skin” could make to the OS. Further, OnePlus itself has been pushing more and more of its apps to the Google Play Store, making it easier to deliver updates and bug fixes to these apps without needing to roll out an entire system OS update for all the phones involved. With these two situations intertwined, the question remains — what exactly is OxygenOS really? And what does its future look like?

“In my opinion, putting everything on the Play Store isn’t about forcing fragmentation. It’s about giving people an option to try out apps for themselves. It’s empowering the consumers, even those that who want a taste of OxygenOS even when they do not have one of our devices. Download the Weather app, and check it out. Maybe you’ll love it, maybe you’ll hate it – and that’s what you discover for yourself.

What OxygenOS is, it is the umbrella around all of that. It’s the glue that brings the experience together. We believe, and we hopefully we demonstrate that too, that all of these apps run the best on our devices. We believe in Android, but to get the best experience, you have to get a OnePlus device in your hand. It’s about the optimizations that we make, the streamlining that we do, the smooth experience that users have come to expect from us.”

Android is the Mercedes platform, and we are the AMG. We tune the OS for performance, and we empower the customer with the things that they do want.

“Stock Android is a great platform to build on. But people have kind of lost sight of what pure AOSP and stock Android is. People have an image in their mind of what stock is, but they may not be really in tune with what stock is right now. You wouldn’t want to use pure stock Android, but it’s the perfect platform to build on. Stock Android is lightweight, and fast, over anything else, and really performant. And we at OnePlus can add in customizations on top of this. Building upon the platform, we aim to deliver on those pillars.

To circle back to the original question, it’s not about fracturing everything up and putting a divide between apps. It’s about empowering the consumer and giving people the option. And OnePlus’ OxygenOS 11 is the glue that brings everything together and provides the best experience.”

Why is OxygenOS called lightweight?

One of the prevalent emotions related to OxygenOS has been its “lightweight” characteristic. This was true in the early days of the UX skin, especially compared to the burdened experience on other OEM UX skins of that time. Early OxygenOS took Google’s Android (not to be confused with pure, stock AOSP) and sprinkled in some goodies on top. The end result in that time period was an OS that evoked “lightweight” as an emotion across everyone, unanimously.

But a lot of people would disagree on calling OxygenOS as lightweight in 2020. There has been a lot of pushback on bloatware added on top of devices like the OnePlus 8 series and the OnePlus Nord. Not all of them can be easily uninstalled — some of them require a step and two, extra. There are plenty of extra monetization surfaces that have been added onto the phone, and this comes in the backdrop of the devices rising in price across the generations. In the end, the overall idea starts going against the “burdenless experience” that OnePlus is aiming for. Why is OxygenOS still referred to as lightweight despite this whole scenario?

“On the user side, calling it lightweight would be a reference to OxygenOS being fast. It’s a phone that works out of the box and throughout its life in a very fast way. For a consumer, it’s just speed and performance. And I like to believe that we are delivering on that.

On the topic of pre-installed apps, with the disclaimer that I am not privy to the Indian business as much as I am to the global business, with OxygenOS 11, we are trying to rely more and more on APIs. This empowers users to engage better with what they want, rather than bundling in APKs everywhere. We look towards the future, and we believe that our model is the model that we really believe in.”

Sam narrated some comments from Qualcomm made in the context of the 5G push. At the very top end of 5G with mmWave, it will be faster to ping a satellite than it will be to access something internally. Would a user actually want apps in such a scenario, or would they be content with responsive and fast loading websites, web pages, and web apps?

To come back, for a customer, OyxgenOS might be lightweight, and for an advanced user looking under the hood, it might not be. If you look at us compared to other manufacturers, I still think we’re at the very bottom of how much code we have added on top of Android. People might think that we have done a lot of changes to bring about a change in looks, but usually, that’s still the same code that we have just modified slightly. The commitment to this general philosophy of “lightweight” is unwavering from our side. It has always been and will always be about putting phones in people’s hands and deliver on both performance and customizations, while still delivering an experience that is considered lightweight to the end-user. Features like AoD, Dark Mode 2.0, these are obviously features on top of the stock experience, but we do think these are worth adding. We could add so much more, but we also have to maintain a balance — what are the features that people will love, what are the features that the majority will engage with, what are they demanding. Can we add them while being lightweight, or do we skip the addition and risk users complaining that we do not have many popular features? There’s always a balance to be maintained, and we talk to the community and actively gather feedback on it.

OnePlus Logo

The magical appearance of the OnePlus Buds APK in OxygenOS

Recently, OnePlus pushed the OnePlus Buds APK to its devices. This move was not very transparently done, and the result was a fair bit of vocal pushback from users who were perplexed by the appearance of this APK on their phone. If a user did not intend to purchase the OnePlus Buds, the APK bore no utility and becomes a burden. We asked Sam to shed some light on the same.

For this particular issue, I do not work that closely with this particular team, but I can fairly assess the implications of this push onto the user. I accept — it is stuff on your phone. But hopefully, users can understand that in the grand scheme of things, it is so little. I understand — we could chip away all the time, and if we made that decision for everything, you’d fill up the phone in no time. But for us, we also need to balance the user experience. So when you open the case of the OnePlus Buds, you get the smart features that go with the buds, and it won’t be something that you would need to install yourself.  The user gets a nice connection journey, so it is a considered choice. The team that made that decision pushed that out in the hope that people understand that it is very lightweight and the impact is small — it’s not nothing, for sure — but hopefully the benefit for people that do want to engage with it, they get that lovely user connection experience. I do get the other side too — if we take that decision for every single thing, it will just spiral and spiral. That feedback is always valued and challenges us at every decision we make and we do appreciate it. But hopefully, you can also appreciate our side as well.

Don’t Kill My App!

One of the more frequent complaints on OnePlus smartphones and OxygenOS by extension is the surprisingly aggressive app killing/”optimization” behavior. It’s surprising because the hardware on these phones is on the upper end of the spectrum, so a lot of the erstwhile arguments that were usually expected for such behavior, such as low memory and limited battery, do not hold true anymore. However, there is a separate problem that Chinese OEMs that sell in China face — the lack of Google control essentially means a lot more rogue apps, more rogue app stores, and more rogue background persistence that stops the phone from going to sleep. Aggressive behavior becomes the duty of the UX in such a case, but the same brush cannot be used to paint the rest of the world where Google operates with a good degree of control (for the most part).

DontKillMyApp is a project that is meant to highlight how aggressively different manufacturers freeze background apps. It’s meant to provide context and relation to how well a phone handles background apps.

DontKillMyApp ✌ Make apps work (Free, Google Play) →

OnePlus is rated as one of the worst offenders in this regard, with the background limitations rated as being one of the most severe on the market, dwarfing the likes of Xiaomi and Huawei. Users need to enable extra settings to make apps work properly (turning off Battery Optimizations, turning off App Auto Launch, turning off Advanced Optimization). And for users who do not understand what is happening, the blame for an app not working gets pushed onto the app developer, even though they may not be the one to blame in this situation (i.e they follow best practices and have a foreground service with a notification, but still end up getting killed).

Does OnePlus take cognizance of the aggressive app killing and plan to address it in some way?

“It’s something that we have received feedback on. Ultimately, our job is to deliver the best user experience. And if that app killing or optimization is creating a negative user experience, we will look at addressing it and look to understand what’s happening. You’re right, there is a balance between what some apps demand these days and what the user is willing to give up. It’s hard for us to classify all applications, and start to tune our code to suit that. I’ve seen a few examples, and I’ll personally raise that with the team and try and look into it more and deal with it better. I’ve seen the DontKillMyApp service, I’m sad that they don’t do a thumbs up for any service, it’s all negative. But yeah, still something to look into, for us to find that balance in delivering the best user experience. It is a negative for us, it is negative for the consumer, and definitely something for us to consider for the future. We are asking so much from the chipset and the battery these days — what phones can do has grown exponentially, what batteries can do has grown in a more linear path, and the chipset is in the middle trying to keep up. Our job is to balance all of these three elements to deliver the best user experience. Something that people know us for is the smooth, fast, lightweight, snappy performance — and I’ll definitely bring this to the attention of the team. We gather feedback, and I don’t know right now if it’s better or worse in OxygenOS 11, but we are in the feedback stage of product development, and we’ll definitely deal with this better.

More usable Always On Displays?

OnePlus had briefly introduced Always On Display functionality back when the OnePlus 6 was released, but the feature was removed in May 2018 once users began complaining of poor battery life. OxygenOS 11 in 2020 finally, finally, finally brings along an Always On Display feature to new OnePlus smartphones, with the first AoD co-created with the Parsons School of Design and Art in New York City. However, the initial set of feedback on the feature was the fact that the AoD was a little too dim, making it difficult to view in higher ambient light situations.

Sam noted that they have taken feedback from users, and that changes are being done to make the feature better. There’s another AoD that is in the works, so that is something to look out for, as well. OnePlus’ AoD implementations aren’t just sticking to the standard format — the company hopes to deliver utility beyond just the time. For instance, the Parsons AoD mixes in elements of Digital Wellbeing, making users subtly aware of how many times they have unlocked their phone in a day. AoD serves as the gateway to the phone, and it’s rightly placed to make users aware of their habits without being distracting or condescending.

We’re creating products and experiences that people love, and it is a window to their world.

OxygenOS 11

AoD implementations, as Sam notes, is a complex problem with a lot of moving parts that can influence how much battery the feature sips away, and consequently, how it impacts user experience. AoD is a further balance between distraction and information. And there’s more to come from OnePlus on this end.

USB Passthrough Charging for OnePlus?

One of the features that flew under the radar this year is USB passthrough charging. Sony introduced it with the Sony Xperia 1 II under the name H. S. Power Control, and ASUS also enables the same for the ASUS ZenFone 7 series and the ASUS ROG Phone 3. USB passthrough charging essentially allows the phone to accept power directly from the charger rather than the battery, once a certain battery charge level is reached (usually between 90% to 100%). This prevents the battery from being trickle charged when the phone is actively getting used for intensive tasks like gaming. The end result is that you get lower overall heat generation during intensive tasks (since the battery is not charging), fewer charging cycles, both of which in turn help prolong the overall life of the battery and consequently, the phone.

While OnePlus does not explicitly advertise its smartphones as predominantly “gaming” smartphones, they are pretty good at gaming. And considering the push on faster charging, it just makes sense to have USB Passthrough Charging available as a standard feature in the near future.

While Sam is not responsible for hardware decisions, he does concede that passthrough charging is an interesting technology, especially for power users and gamers that make up for a good part of OnePlus’ target demography. No promises were offered, but at least we know that OnePlus is aware of this. Perhaps we can expect to see this on the OnePlus 9 series? A man can hope.

OxygenOS, and Battery Health and Longevity

The conversation also turned to battery health, a topic that is now seeing some more focus in these years. USB Passthrough Charging is marketed as a feature within the software, usually residing in setting areas concerned with battery health. With phones now being more expensive than ever, it is a natural expectation from consumers that their device will last for a fair few years, and battery health plays a good role in such an expectation. What does OxygenOS 11 do that helps battery longevity on OnePlus devices?

I think we at OnePlus build devices to last, hopefully, more than any other brand. We invite users to use their devices for long periods of time. And this is true now more than ever, with the increasing cost of devices and the actual utility of these phones also increasing. We recognize that longevity is really important and for that, we do have a few optimizations that we did implement. With Li-Ion batteries these days, battery cycles are an important part of the conversation on longevity. OxygenOS has smart charging, which attempts to learn your schedule and tries to figure out when you are going to get up. For cases of overnight charging, the smart charging feature will charge your device up to 80% and let it sit there through the rest of the night. And about 2 hours before your alarm or first calendar appointment, your phone will charge to 100%. So that is something that we have implemented quite recently. We are obviously trying to put in the best hardware, and we can also try to manage the battery cycles adequately to have this balance between the best user experience and getting the device to last long as well. It’s not a perfect science, it’s really hard to control everything. But our values add up to what is accepted as a good user experience overall. We look around in the forums, and we can see people still using the OnePlus 2 and OnePlus 3, and our data also shows a significant number of people upgrading the OnePlus 8 series from the OnePlus 2,3, and 5 series. Fair play, they are making their devices last, and they are getting the most out of what they have spent their hard-earned money on. So I hope that our values actually deliver on that.

OnePlus 5 and the cursed Android 10 update

We had the opportunity to bring up the OnePlus 5 and OnePlus 5T‘s cursed Android 10 update. Ever since the Android 10 stable rollout, OnePlus 5 and 5T owners have complained about a number of issues, ranging from poor battery life to broken EIS. The update had been so problematic that OnePlus themselves did not even list the build for download on its support website. The software release also featured outdated security patches (the April 2020 Security Patch Level, to be exact), despite the fact that the OnePlus 5T is still covered under the OxygenOS Software Maintenance Schedule (the OnePlus 5T was released on November 2017, so regular software updates ended by November 2019 but bi-monthly security updates should continue to November 2020).

Sam noted that this is handled by a completely different team, but he would nonetheless, highlight it internally. True to his word, OnePlus came out with an acknowledgment within 12 hours of the conclusion of our conversation/interview. While the answer may not be what users were looking for, getting some communication and assurance from the company is certainly appreciated. We hope they maintain proactive communication on this end.


A big thanks to Mr. Sam Twist for the interview opportunity and a shout out to the OnePlus team for helping coordinate this.

The post How OnePlus designed OxygenOS 11 to make bigger phones easier to use appeared first on xda-developers.



from xda-developers https://ift.tt/3nv6JSA
via IFTTT

Future ARM CPUs will drop support for 32-bit apps

In May 2020, ARM announced its 2020 CPU lineup, consisting of the ARM Cortex-A78 A-series CPU core and the new ARM Cortex-X1 core, the first coming under the Cortex-X custom CPU program. The new cores haven’t made their way to any shipping devices yet – users will have to wait for early 2021 to see phones powered by the new IP. That’s the way ARM announces its new products: the ARM Cortex-A77 CPU core, announced in May 2019, only made its way to shipping phones in February 2020. The ARM Cortex-A78 and the Cortex-X1 are 64-bit cores like their predecessors, but they also have hardware support for old 32-bit apps. ARM has now confirmed that this will change, though. Future ARM Cortex-A CPU cores will become 64-bit only starting 2022.

This announcement was made by Paul Williamson, VP and GM of Client Business at ARM, at an ARM DevSummit keynote. The news announcement means there will be no hardware support for old 32-bit applications in the future.

This shouldn’t mean bad news for the vast majority of apps, however. That is because Google has required apps submitted to Google Play since August 2019 to be 64-bit. ARM also notes that about 60% of apps are 64-bit compliant already. Most of the apps that aren’t 64-bit don’t belong to Western ecosystems. For app developers, there is plenty of time to update their old apps, considering that CPU cores announced in 2022 will probably make their way to shipping devices only in early 2023. If a 32-bit app is no longer being updated, though, this announcement means it will stop working in 64-bit-only devices that will launch featuring the future ARM Cortex-A cores.

Android itself is already 64-bit, as the operating system introduced 64-bit support with version 5.0 Lollipop back in 2014. However, Android and ARM’s CPU cores continue to support 32-bit applications, which means Android is not a 64-bit-only OS as of now, unlike iOS, which went 64-bit-only in 2017 with iOS 11. The legacy support of 32-bit applications will end in 2022 from the hardware part of the equation, and it’s fair to expect Google to follow this announcement by removing 32-bit app support in future versions of Android. As previously mentioned, this should be mostly invisible to end users.

What are the benefits in moving to 64-bit-only? These include improved performance in the operating system and for apps and games, up to 20% in some cases. It’s also easier for developers as they won’t have to support two binaries. They can focus on optimizing a single 64-bit binary, which could mean quicker update times.

For ARM, the news means that it can drop additional silicon from its CPU designs that it has needed to have legacy 32-bit support. This could save on silicon area, which could mean more powerful CPUs in the same die size. ARM’s 2021 and 2022 Cortex-A CPUs are code-named Matterhorn and Makalu respectively. It’s Makalu that will be making the switch to exclusively 64-bit. ARM has promised a 30% performance increase between the Cortex-A78 announced this year and Makalu, as the company keeps progressing with its CAGR (compounded annual growth rate).

The transition to exclusively 64-bit will start with the big CPU cores. (ARM didn’t state when the Cortex-X series will migrate to 64-bit only, but it’s likely that it will happen either at the same time or before the Cortex-A series.) The Cortex-A55 “little core”, announced in 2017, is a 32-bit/64-bit design, and its successor, which could launch next year, will still have 32-bit support for legacy apps. So the end result will be a CPU cluster design that mixes 64-bit-only Makalu with a smaller 32-bit/64-bit little core such as the successor of the Cortex-A55. The final product, however, will be 64-bit-only from the perspectives of developers and users. The Cortex-A55’s successor will presumably support support 32-bit for a while longer, but it will be irrelevant for users with Makalu powered devices and beyond.

So Android’s move to 64-bit exclusively will take place roughly five years after iOS completed its transition to 64-bit-only in 2017. Again, all of this shouldn’t make much of an effect for end-users, except for the benefit of improved performance. The onus is on app developers to update all of their legacy apps with 64-bit support before devices powered by ARM’s Makalu CPU arrive.


Via: Android Authority

The post Future ARM CPUs will drop support for 32-bit apps appeared first on xda-developers.



from xda-developers https://ift.tt/34ynQKt
via IFTTT

Amazon Fire TV gets Live TV support in India through SonyLIV, Voot, Discovery+, NextG TV

Amazon recently launched two new Fire TV Sticks and completely revamped the Fire TV UI to offer users a more personalized experience. The new Fire TV Stick and Fire TV Stick Lite are scheduled to go on sale in India later this month. And just a few days ahead of the first sale, the company has now announced that it’s bringing Live TV support to Fire TV in the country.

The feature adds a ‘Live’ tab on the navigation page and an ‘On Now’ row on the Fire TV home screen. In these new sections, users will be able to access Live TV channels from content providers like SonyLIV, Voot, Discovery+, and NextG TV. It will soon support live channels from Zee5 as well. Live TV on Fire TV will give users access to channels like Sony SAB HD, Colors HD, SET HD, Nick HD+, Dangal, DD National, News18 India, MTV Beats HD, SONY BBC Earth HD, Mastii TV Music, and Discovery.

Amazon Fire TV

Users who have subscribed to the services of any of the content providers mentioned above will see the ‘On Now’ on the Fire TV home screen, with a red bar at the bottom of each thumbnail indicating the real-time progress of the show. The feature also supports Alexa voice commands, and users will be able to access their favorite channels by saying commands like “Alexa, Watch Colors HD.”

Channel guide

Furthermore, users will also gain access to the Fire TV channel guide. The guide will be available in the Options row of the Live tab. Fire TV Lite users will be able to access the guide by pressing the guide button on their Alexa Voice Remote Lite.

Speaking about the new Live TV support, Parag Gupta, Head of Amazon Devices in India, said, “Since launching in India, Fire TV has been offering a vast selection of on demand movies, TV shows, popular apps and features to customers. With Live TV integration, we are making this experience even better by providing instant access to popular, real-time content for our customers without having to switch inputs. It enriches the content experience by streaming live TV on the much-loved Fire TV interface, just by asking Alexa. Amazon will continuously expand this selection and offer the best of live TV experience to our customers.”

The addition of Live TV support to Amazon’s Fire TV spells trouble for India’s already declining cable TV industry. The steep rise in the adoption of OTT platforms during the lockdown seems to have cemented the fate of cable TV in the country.

The post Amazon Fire TV gets Live TV support in India through SonyLIV, Voot, Discovery+, NextG TV appeared first on xda-developers.



from xda-developers https://ift.tt/33KaX0Z
via IFTTT

Download Google’s new “Captured on Pixel” and “Art & Culture” wallpapers

Last week, Google announced the Pixel 4a 5G and Pixel 5, the latest premium Pixel smartphones with Qualcomm’s mid-range Snapdragon 765G SoC. The two phones will only be available in a handful of regions, but they won’t reach the hands of consumers until later this month. With each new Pixel phone launch, Google introduces a new set of wallpapers in the Google Wallpapers app. Immediately following the launch event, I grabbed the new set of wallpapers from the Google Wallpapers app under the “For Fun” section, but we’ve since discovered two more sets of wallpapers that are likely for the Pixel 5. Using a modified version of the Google Wallpapers app, we discovered the “Captured on Pixel” and “Art & Culture” sections with loads of new wallpapers.

Google Pixel 4a 5G Forums ||| Google Pixel 5 Forums

Twitter user @forherpieces originally discovered these new wallpapers, and we can confirm that they show up if you modify the Google Wallpapers app to pull wallpapers from Google’s staging server. We can’t confirm if these wallpapers actually appear on the Pixel 4a 5G and Pixel 5, but we do expect they’ll become available for them since these wallpapers only showed up for us when we spoofed the device model. In any case, user @forherpieces was kind enough to extract the wallpapers and upload them for everyone to enjoy.

“Captured on Pixel”, “Art & Culture” Wallpapers

The “Captured on Pixel” wallpaper collection consists of 13 images from different photographers. There are photos from different parts of New York City, London, and Japan. These images were presumably captured on a Pixel phone—likely the Pixel 5.

Download the “Captured on Pixel” Wallpapers

Next up is the “Art & Culture” wallpaper collection. This collection consists of 21 images of various paintings and other artwork.

Download the “Art & Culture” Wallpapers

“For Fun”

Lastly, there are 12 new wallpapers in the existing “For Fun” collection. Like the wallpapers for the Pixel 4a, the new “For Fun” wallpapers are designed specifically with the Pixel 4a 5G and Pixel 5’s hole-punch cutout in mind.

Download the latest “For Fun” Wallpapers

It’s always fun to change your phone’s wallpaper, and Google is one of the best at designing new wallpapers. This time around, though, it looks like they’re spicing up the wallpaper selection with more real-world imagery. We’ll keep an eye out for when the new “Art & Culture” and “Captured on Pixel” collections go live, but you can check for their presence yourself by downloading Google’s Wallpapers app from the Play Store. Keep in mind that Google hides certain wallpapers based on what device you have, so you probably won’t see these new wallpapers unless you have either the Pixel 4a 5G or the Pixel 5.

Wallpapers (Free, Google Play) →

The post Download Google’s new “Captured on Pixel” and “Art & Culture” wallpapers appeared first on xda-developers.



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