LightBlog

jeudi 30 juillet 2020

HMD Global’s first 5G smartphone, the Nokia 8.3 5G, is coming to the US this fall

The Nokia 8.3 5G was announced a few months back as HMD Global’s highest-end smartphone in 2020 so far (although there are rumors floating around of a Nokia 9.3 PureView in the works, so this could very well change soon). The Nokia 8.3 5G is also the company’s first, and so far only, 5G-enabled smartphone. While it’s not powered by the flagship Qualcomm Snapdragon 865, it does have the Qualcomm Snapdragon 765G, which has been the common choice for mid-range smartphones with 5G support throughout the year. Not only this, but HMD Global also claimed that theirs was the first 5G device in the market to be compatible with all 5G bands globally. This device was previously planned for a global release following an announcement at MWC 2020 but plans obviously changed because of COVID-19 (MWC was canceled, the phone’s announcement was delayed, etc.) Now, HMD Global has announced that the Nokia 8.3 5G is coming to the United States very soon.

nokia 8.3

The Nokia 8.3 5G. Source: HMD Global

How soon, you might ask? The phone is launching sometime in the fall as per the company’s official announcement. For now, though, HMD Global has not given an exact release date and there is also a lot of information essential to the U.S. market that has not been disclosed right now, such as which carriers will have the phone, which retailers will sell it, what RAM/storage configurations will be available, and more. All of this information will probably be disclosed as we get closer to the phone’s release.

HMD Global is also increasing its focus on the American market; they have already had a presence in the U.S. for years, but the company plans to increase its presence as they’ve done in other parts of the world. The release of the Nokia 8.3 5G in the U.S. is only a part of this renewed push; Juho Sarvikas, the current Chief Product Officer of HMD Global, has been appointed Vice President of North America in order to work more closely with carriers and bring even more Nokia-branded smartphones to Americans.

This is all amazing news for Nokia fans in the United States. Are you excited about the Nokia 8.3 5G?

Nokia 8.3 5G Specifications

  • 6.81-inch (1080 × 2400 pixels) Full HD+ 20:9 LCD screen with 120Hz refresh rate
  • Octa Core (1 x 2.4GHz + 1 x 2.2GHz + 6 x 1.8GHz Kryo 475 CPUs) Snapdragon 765G 7nm EUV Mobile Platform with Adreno 620 GPU
  • 6GB LPDDR4X RAM with 64GB storage, 8GB LPDDR4X RAM with 128GB storage, expandable memory with miroSD
  • Android 10
  • Single / Dual SIM
  • 64MP rear camera with Dual LED flash, ZEISS Optics, 12MP ultra-wide angle lens, 2MP macro and 2MP depth sensor
  • 24MP front-facing camera
  • Side-mounted fingerprint sensor
  • 3.5 mm headphone jack, FM radio receiver, OZO audio
  • Dimensions: 171.90 x 78.56 x 8.99mm; Weight: 220g
  • 5G SA/ NSA / Dual 4G VoLTE, WiFi 802.11 ac (2.4GHz + 5GHz), Bluetooth 5, GPS/GLONASS/Beidou, USB Type-C
  • 4500mAh battery with 18W fast charging

The post HMD Global’s first 5G smartphone, the Nokia 8.3 5G, is coming to the US this fall appeared first on xda-developers.



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

HMS Core 5.0 introduces an AR Engine, Computer Graphics Kit, Accelerate Kit and more improvements

Huawei Mobile Services, or HMS, is Huawei’s alternative to GMS, and it similarly consists of user-facing applications as well as core background services. HMS provides an experience that is consistent across devices and independent of the platform version. The HMS ecosystem is comprised of HMS Apps, the HMS Core, and the HMS Capabilities that the Core enables through its available APIs. The latest milestone update to HMS Core 5.0 introduces several APIs and improvements to existing APIs.

Huawei has doubled down on improving HMS Core and its allied services. After all, these services and service frameworks form the backbone of Huawei and Honor’s current experience. As of March 2020, Huawei’s global monthly active users has reached 650 million, representing an increase of 25% YoY. The number of registered developers on Huawei’s platform has also reached 1.4 million, a 115% YoY increase. And the total number of HMS Core apps has also exceeded 60,000 globally, which is a 67% YoY growth. Huawei is placing all of its bets on its own ecosystem, and the constant improvements in HMS Core are testimony to its long-term commitment towards the HMS vision.

HMS Core 4.0 was launched back in January 15, 2020, introducing new APIs in the form of the Map Kit, Machine Learning Kit, Scan Kit, WisePlay DRM, and more. Now, with HMS Core 5.0, Huawei is introducing some more new APIs: AR Engine, Computer Graphics Kit, Accelerate Kit.

AR Engine

Huawei AR Engine is equivalent to Google Play’s ARCore service. Thie AR Engine in HMS Core serves as a platform for building augmented reality (AR) apps on Android smartphones with HiSilicon Kirin chips. It integrates core algorithms for AR to provide basic AR capabilities such as motion tracking, environment tracking, and body and face tracking. With the AR Engine, you can build apps that bridge the virtual world with the real world.

In a nutshell, the Huawei AR Engine continuously tracks the device location and poses in order to provide motion tracking and environment tracking abilities. It makes use of the device camera to identify feature points in a given space, and then tracks the movement relative to these points, and subsequently integrates these changes with the data reported by the inertial sensor on the device. It can also recognize flat planes such as floors and walls, and it can also make an estimation of the lighting intensity around them when identifying feature points.

What makes Huawei’s AR Engine special is its ability to also enable movement tracking for humans. It can allow locating hand locations and recognize specific gestures. There is also a depth component within the API, which then comes together to let the API track as many as 21 hand skeleton points to implement precise interactive controls and special effect overlays. It can also track 23 body skeleton points to detect human posture in real-time, and Huawei envisages that you can use this data to build innovative apps around fitness and health too.

Computer Graphics Kit

The Huawei Computer Graphics Kit is a Vulkan-based high-performance computer graphics rendering framework. This framework consists of the PBR (physically based rendering) material, models, textures, light, component systems, and more. The idea behind the rending framework is to provide the best 3D rendering capabilities on Huawei devices that make use of HiSilicon Kirin chips. The framework also supports secondary development with reduced difficulty and complexity, which Huawei claims helps significantly increase development efficiency.

The Huawei Computer Graphics Kit can be used for 3D applications use cases as it encapsulates the necessary Vulkan API call methods, and also implements dedicated optimization on the Huawei GPU. This greatly reduces the workload in developing high-quality 3D static models. The Kit also provides for a high-performance multi-thread rending module that integrates the best practices in usage of Huawei-dedicated Vulkan enhancements and extensions. In essence, the Computer Graphics Kit helps accelerate the adoption of computer graphics in apps by offering developers the cutting edge tools they need to integrate the same into their software.

Accelerate Kit

The Huawei Accelerate Kit provides for multi-threaded acceleration capability that claims to efficiently improve the concurrent execution of multiple threads, thereby optimizing apps. This Kit opens this capability to developers as a set of C-language APIs. This will allow developers much more flexibility on current-generation Android devices that run on a multi-core setup. Multi-thread programming is generally achieved by controlling task execution by managing threads. With the Accelerate Kit, developers are freed from thread management details, so they can focus more on their own app while still gaining efficiency.

Audio Kit, Image Kit, Video Kit within HMS Core

HMS Core 5.0 also adds three new kits relating to the phone’s audio, video, and image capabilities. The Audio Kit enables audio playback capabilities based on the HMS Core ecosystem, including audio encoding, decoding capabilities at the hardware level and system bottom layer. The Image Kit allows you to incorporate scene-specific design and animation production functions into your app. The Video Kit currently provides for video playback capabilities, and work is on to incorporate video editing and even video hosting APIs in later releases. This will let you easily build apps that can play streaming media from an address provided by a third party.

Other upgrades to HMS Core

While the major focus of the version release is the new APIs, several new APIs are also getting new features. For instance, the Scan Kit now features deep learning-based scanning codes to improve scanning accuracy in more challenging situations with higher response speeds. The Map Kit has gained bus and subway route planning information, so developers can now use these to improve the functions within their apps. The Location Kit now supports fence management capabilities.


HMS presents itself as a window of opportunity for reducing your app’s reliance on Google services as well as an opening into Huawei and Honor’s device ecosystem, which still forms a substantial and unignorable part of the market. Huawei is in one of the rare positions of being able to offer a robust set of alternative APIs that provide a similar set of expected functionalities to both developers and users. Huawei intends to move ahead with HMS Core integration within its devices, so as a developer, can you really afford to ignore this important part of the market?

Check out all API Kits present in Huawei Mobile Services


We thank Huawei for sponsoring this post. Our sponsors help us pay for the many costs associated with running XDA, including server costs, full time developers, news writers, and much more. While you might see sponsored content (which will always be labeled as such) alongside Portal content, the Portal team is in no way responsible for these posts. Sponsored content, advertising and XDA Depot are managed by a separate team entirely. XDA will never compromise its journalistic integrity by accepting money to write favorably about a company, or alter our opinions or views in any way. Our opinion cannot be bought.

The post HMS Core 5.0 introduces an AR Engine, Computer Graphics Kit, Accelerate Kit and more improvements appeared first on xda-developers.



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

Samsung Galaxy S10 family receives new updates with August 2020 security patches

Besides Google’s generic Android Security Bulletin (ASB), several major OEMs like Samsung maintain their own version of security bulletins. If you take a look at the Android section of Samsung’s Mobile Security portal, you can get a clear idea about all the disclosed security vulnerabilities affecting closed-source vendor components, the underlying Linux kernel in Android, and various OS frameworks that have been fixed by Samsung till date. At the time of writing this article, the latest monthly security patch level (SPL) is still listed as July 2020 on Samsung’s bulletin, but the OEM has already started rolling out the August 2020 security patches to the Galaxy S10 series in some regions.

XDA Forums: Galaxy S10e ||| Galaxy S10 ||| Galaxy S10 Plus

The version number of the new build is G97xFXXU8CTG4, and it is currently available for the international variant of the Galaxy S10 (model number SM-G973F) and Galaxy S10+ (model number SM-G975F), both powered by the in-house Exynos 9820 SoC. Interestingly, we can’t find a similar build for the Galaxy S10e (model number SM-G970F) as of now, but it should be made available very soon. The OTA update is available in the DBT region, which is Samsung’s code for Germany. The full changelog for the update is not available yet, but we do know that Samsung ships a new bootloader (v8) with this build. As a result, the end-users can’t perform a downgrade to older builds once they install this update.

Samsung is known for pushing out updates in batches. Even if you are in Germany, you might have to wait a couple of days before the OTA notification pops up on your device. If you’re comfortable with manual flashing, then you can use a community developed tool named Frija to download the updated firmware from Samsung’s repository. The required parameters can be found in the screenshot below:

samsung_galaxy_s10_august_2020_patch_frija

Thanks to XDA Senior Member henklbr for the screenshot

The decrypted firmware package created by Frija can be flashed using Odin on any regional Exynos Galaxy S10 model, not just the German one. Note that the U.S. and Canadian Snapdragon 855-powered variants of the Galaxy S10 are not compatible with the aforementioned update.

The post Samsung Galaxy S10 family receives new updates with August 2020 security patches appeared first on xda-developers.



from xda-developers https://ift.tt/39CKiV4
via IFTTT

WhatsApp is working on a “Mute Always” option for chats, continues work on expiring messages and multi-device access

WhatsApp for Android recently received a new mute feature on the beta channel, which allows users to mute any chat right from the notifications shade. However, the mute feature has been designed in a way that it only shows up when you receive at least 51 messages from a single chat. Before receiving the requisite number of messages, the app shows a ‘Mark as Read’ button instead, which you can tap to dismiss the notification. While the new Mute feature can come in handy when you’re trying to ignore messages temporarily, it isn’t as effective as the upcoming Mute Always feature that is currently in the works.

According to a recent report from WABetaInfo, WhatsApp is working on a new Mute Always setting for chats that will allow users to indefinitely mute any chat or group chat. The feature appears within the Mute notifications option within any given chat and replaces the 1-year option currently available in the settings.

WhatsApp Mute Always

The upcoming feature was spotted in WhatsApp beta for Android version 2.20.197.3, and it’s currently under development. The feature is expected to make it to the beta channel in a future update.

Along with the Mute Always feature, WABetaInfo has uncovered some more information about the upcoming ‘expiring messages’ and ‘multi-device access’ features in the latest WhatsApp beta releases. We first learned about these features earlier this year in March, and WhatsApp recently started testing these features in a beta release.

WhatsApp Expiring Messages

With WhatsApp for Android beta version 2.20.197.4, the messenger has made some improvements to the UI for the expiring messages feature. Instead of giving users the option to choose how long new messages stay in the chat before disappearing, the updated UI reveals that all expiring messages will be automatically removed from a chat after seven days.

WhatsApp Linked Devices

The multi-device access feature, on the other hand, has received a new UI to help users manage all connected devices. The updated UI has been spotted in beta version 2.20.196.8 of the app, and it brings a new ‘Linked Devices’ option to the three-dot menu. Tapping on the option opens up a new section on the app which lists down all the linked devices and gives users the option to link a new device or log out of a linked device with a single tap.

Furthermore, WABetaInfo reveals that WhatsApp is planning to release a new privacy policy for Brazilian users, and users in the region will receive an in-app banner notification once the policy starts rolling out.

WABetaInfo also highlights a few details about the upcoming ‘Advanced Search Mode’ feature, which has also received some UI improvements. The feature was first spotted earlier this year in April, and it will let users select tags like Audio, Video, Documents, Links, GIFs, etc. while looking for an item sent or received in a chat.

It’s worth noting that all the features mentioned above are currently under development, and they’re not available to end-users in the respective beta releases of the app.


Source: WABetaInfo (1,2,3)

The post WhatsApp is working on a “Mute Always” option for chats, continues work on expiring messages and multi-device access appeared first on xda-developers.



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

Realme Buds Q Review: Good-sounding, Affordable TWS Earbuds with Issues

Remember when headphone jacks were a thing? Yeah, me neither. Thanks to a certain fruit sealing a 3.5mm hole in its glass slabs, and others following suit, Bluetooth earbuds and headphones have really taken off. As we have progressed since the move, cheaper and more accessible options were bound to appear. It’s time to talk about one of these cheaper options, the Realme Buds Q. These are a pair of earbuds priced at around $30, which is fairly cheaper than some of those fancy $250 models out there. How well do they hold up, though? Does the battery last? How good do they sound? Should you buy them?

Well, there’s only one way to answer these questions, and that’s with a review.

Unboxing and First Impressions

Like everything from Realme, the Realme Buds Q come in a bright golden-yellow box. Inside this container is your usual stuff: a charging case, some different tip sizes, a (short) charging cable, a user guide, and, of course, the earbuds themselves.

Let’s talk about the charging case first. Realme says it’s modeled after a “cobblestone” and it does look somewhat like a stone, but so does every other rounded earbuds case on the market. On the front, there’s a charging indicator and a little lip to lift the lid. On the back, we’ve got a Micro-USB charging port. Yes, you heard me right, Micro-USB. The Realme Buds Q are very much budget earbuds, so this kind of makes sense given the target audience. But I still think they could have managed to use a USB-C port instead. The charging cable that comes in the box is only about 4 inches long, so you may need to hunt for a longer micro-USB cable. While there’s a magnet to help keep the case closed, the hinge mechanism feels a little flimsy. It’s pretty easy to push it side-to-side, which doesn’t speak well for longevity.

Opening the case, you’ll find the earbuds with plastic films over the charging contacts. Realme says these earbuds are light, but you really need to actually hold them to feel what that means. The Realme Buds Q, charging case and all, are incredibly lightweight. It almost feels like I’m holding nothing when I pick up the case. In my ears, it feels like they’re going to fall out because of how light they are. I’m not entirely sure why you’d want earbuds that are almost as light as air, but it’s certainly quite an achievement, especially at this price point.

Realme Buds Q case Realme Buds Q case and earbuds Realme Buds Q case and earbuds

Now it’s time to power on the Realme Buds Q. And this is where I think Realme failed, right off the bat. The onboarding process is terrible. Most earbuds I’ve used will power on and go into pairing mode if there’s nothing to connect to. Some might have you long-press on the earbuds to enter pairing mode. The Realme Buds Q, however, do neither. When I took them out of the case, I couldn’t figure out how to enter pairing mode. I tried long-pressing, but all I got were some weird sound effects (more on those later). I tried putting them in the case and then closing and opening it: nothing.

You might be thinking, “why don’t you just read the manual?” Well, I did. The manual that came with my unit says to take the earbuds out of the case and let them sit for 15 seconds to enter pairing mode. That didn’t work.

Instead, to enter pairing mode, you have to put the earbuds in the case and long-press on them for 5 seconds. I had to find that instruction on a product page from a third-party seller on Amazon India. The Realme Buds Q may only be about $30, but I don’t think that’s an excuse for not providing better instructions.

Luckily, things get better after you pair the earbuds. Each earbud has its own capacitive touchpad for controls. I’ll go into the controls themselves later, but it’s nice to see Realme implement touchpads at such a low price.

Overall, my first impressions weren’t great. It’s not all bad (notice that I haven’t mentioned sound quality yet?), but the initial pairing process was too much of a mess to ignore.

Before we head into the controls, here’s a quick specs list for the Realme Buds Q.

Feature Spec
Dimensions Earbuds: 19.8mm x 17.55mm x 22.5mm

Charging Case: 59.8mm x 45mm x 29.9mm

Weight Earbuds: 3.6g each

Charging Case: 28.2g

Water Resistance Earbuds: IPX4

Charging Case: None

Frequency Response 20Hz-20KHz
Battery Life Earbuds: Up to 4.5 hours

With Case: Up to 20 hours

Connectivity Bluetooth 5.0

10m Range

Charging Micro-USB Port
Audio Formats SBC

AAC

Color Options Quite Yellow

Quite White

Quite Black

Controls

Moving past the onboarding issues, let’s talk about the controls. As I mentioned above, the Realme Buds Q have capacitive touchpads on each earbud for controls. They don’t cover the entire outer surface, but it’s certainly a more premium feel than, say, the Redmi Earbuds S, which have simple buttons.

Of course, a premium feel doesn’t mean much if there’s no functionality to back it up. Happily, the Realme Buds Q are pretty good at recognizing gestures, which is more than I can say for the $100 Amazfit PowerBuds.

In terms of what you can actually do with those touchpads, here’s a list:

  • Double tap either earbud for play/pause.
  • Triple tap the left earbud to go back to the previous track.
  • Triple tap the right earbud to skip to the next track.
  • Press and hold on both earbuds or 2 seconds to toggle Game Mode

For the tap gestures, you can’t tap too rapidly or nothing will happen. But they are consistent in their detection of slower taps, which is certainly appreciated.

That isn’t all for the controls, though. These earbuds work with the Realme Link app. If you pair them to your phone, you can use Realme Link to customize what the gestures do. There’s even a “secret” 2-second long-press gesture for each earbud that’s turned off by default. Here are the possible actions you can assign for each gesture:

  • Play/Pause
  • Next Track
  • Previous Track
  • Voice Assistant
  • None (Off)

The exception to this is the Game Mode gesture; this one can only toggle Game Mode or do nothing. For the price, though, you can’t really complain.

Now let’s talk a little about sounds. No, not sound quality, sounds. Like a lot of earbuds, the Realme Buds Q have sound effects for various state changes. When they connect, there’s a two-tone drumbeat sort of sound. And this is where things get weird. When enabling Game Mode, a sound like a motorcycle or a racecar revving up plays. Exiting Game Mode causes a gentle guitar strum to play. Personally, I think these sounds are kind of cheesy and a bit annoying to listen to every time.

Ergonomics & Usage

Earbuds aren’t only about controls, though. Here’s how well the Realme Buds Q hold up in terms of overall daily usage.

First up: multi-device pairing. I don’t know about you, but I like to use my earbuds with more than one device: laptop, phone, etc. For me, an important feature of Bluetooth earbuds is easy pairing/device switching. Unfortunately, as I mentioned in the first impressions section, the Realme Buds Q aren’t really that easy to pair to new devices. Even ignoring the poorly documented instructions, I don’t like that I have to put them in the case to pair them. A 5-second long-press out of the case would be just as effective and much more convenient for entering pairing mode.

Even if we disregard that issue, it’s still not a great experience. The Realme Buds Q seem to only be able to remember one paired device at a time. Putting them in pairing mode to change what they’re connected to causes the pairing prompt to show up on whatever device is attempting to pair. It also sets the volume to 100%, which is a bit of a nasty surprise if you’re not expecting it.

In terms of comfort, the Realme Buds Q are great. I personally think they’re a bit too lightweight, so they just don’t feel very secure in my ears. But they are very comfortable, and the fact that they’re so light makes me almost forget I even have them in. I’ve kept them in for multiple hours without my ears starting to hurt or itch. And for you fitness folks, the Realme Buds Q are IPX4 certified. So while you shouldn’t be swimming with them in, you shouldn’t need to worry about light rain or sweat frying them.

If you want to give one ear a break but still want to listen to music, the Realme Buds Q do work independently of each other (mostly). While you can’t pair each one to a separate device, either one can be in your ear while the other is charging without an issue (I guess this technically means you can do 20 hours of non-stop listening, as Realme advertises). There is no automatic ear removal detection feature on the Realme Buds Q, so removing one won’t automatically pause your music. Depending on your personal preferences, this could be a positive or a negative (for me, it’s a positive).

Finally, another tease about sound. A problem I’ve noticed on some Bluetooth earbuds, such as the Soundpeats Truengine2 or the Amazfit PowerBuds, is audio latency. On both the Soundpeats and Amazfit, the latency is terrible. They’re fine for listening to music, but forget trying to use them for a VoIP call or watching a video. With Game Mode on, the Realme Buds Q have pretty low latency, at an advertised 119ms. But even with Game Mode off, the latency is low enough to do VoIP calls, although videos are still slightly out of sync.

Battery & Charging

Now it’s time to talk about the batteries in the Realme Buds Q: all three of them. On its website, Realme advertises “20-hour non-stop music.” This is misleading at best. The actual claimed “non-stop” battery life for the earbuds themselves is about 4.5 hours. The 20-hour figure comes from the total time after topping up with the charging case. I don’t know about you, but I don’t think putting one or both of your earbuds in the case for an hour every four hours counts as non-stop. This is dishonest advertising.

Moving past that, 4.5 hours is pretty average for Bluetooth earbuds these days. It’s not amazing, and it’s not terrible. For $30, it’s perfectly fine, and most people won’t need any more than that at once. In my testing, Realme’s estimate does seem to be pretty accurate. Listening to music for 45 minutes brings them down by about 10%. And that’s pretty uniform, too. Over time, they might get out of sync by a percent or two, but you probably won’t have one die too soon before the other.

In terms of the charging case, it might be able to charge the earbuds 4-times over, and it might not be. What I do know, though, is that there’s a significant amount of standby drain in the case when the earbuds are in it. Even when they’re done charging, the case seems to continue giving them power. Leaving the earbuds in the case for more than a week or so causes both the case and the earbuds to go flat. If you aren’t planning on charging the case itself every night, it might be a good idea to leave the earbuds out of the case unless you’re charging them, though then you risk losing them. Some third-party sellers on Amazon India also have reviews littered with complaints on the case stopping charging completely for the users. While my case charges fine for now, this charge leak does not inspire confidence.

Realme doesn’t advertise any fast charging on the product page for the Realme Buds Q, so you’re probably not going to be able to charge them for 10 minutes and get an hour of playback. In some quick testing, it seems like it’ll take about an hour for the earbuds to charge from flat to full. The case itself has a handy charge indicator, though. It lights up red when the case battery is charging and turns off when it’s full. Like the earbuds, it should take about an hour to charge from flat to full.

Sound

I have to admit, when I used the Realme Buds Q for the first time, I was surprised at how good the audio sounds. After overcoming the initial pairing hurdle, I was expecting middling sound quality at best. But the sound is good. It’s no $500 Sony headphones quality, of course, but for $30, it’s kind of crazy. Music sounds clear, with plenty of highs and lows. Bass is a little heavy for my taste, but unlike other bassy earbuds I’ve used, it doesn’t seem to drown out higher frequencies. And of course, if you want to go deaf, the Realme Buds Q have plenty of volume to help you with your endeavor.

Now, the Realme Buds Q probably aren’t going to satisfy many audiophiles out there. Not only because of the high bass, but because of the limited codec support. These earbuds only support SBC and AAC. No LDAC or aptX here. On top of that, the Realme Link app doesn’t have any equalizer or audio tuning options in it, so you’re stuck with Realme’s in-house tuning. For most people, this is probably not an issue, but it is something to be aware of when making a purchasing decision.

In terms of noise, the Realme Buds Q have no form of active noise cancellation (if you were expecting that for $30, I’m not sure what to tell you). They are rubber-tipped earbuds, though, which means you’ll get pretty good passive noise isolation. It’s not going to be anywhere near an ANC-level experience, but you’ll be able to play your music loudly without annoying others.

And now, Game Mode. Game Mode is basically Low Latency Mode. When active, the Realme Buds Q will only have a claimed latency of 119ms, at the possible cost of audio quality. This is useful for listening to videos and games. In both situations, you need as little delay as possible between events occurring and you hearing them. For videos, that means synced audio and video. In games, it could mean the difference between getting a kill and being a kill.

Unfortunately, Game Mode is a little inconsistent, both across devices and operating systems, and compared to the normal mode. Testing on a Samsung Galaxy Note 9, the delay between Game Mode and normal sounds about the same. On an OPPO Reno3 Pro, there is a difference, but the delay is definitely more than 119ms in Game Mode.

Using the Earbuds Delay Test app, I was able to see that, on the Reno3 Pro in Game Mode, the delay was about 350ms. In normal mode, that delay shot up to over 500ms. Moving over to the Galaxy Note 9, the delay was about 350ms whether I was in Game Mode or not. On Windows, I wasn’t able to use the app, but I did find YouTube videos that provided the same feature. With Game Mode on, the delay was much closer to the advertised 119ms. With it off, the delay was around 350ms.

For voice calls, I don’t recommend using these earbuds. I tried both Telegram calls and traditional calls, and for both, the other side complained that I sounded “pretty bad.” On the Telegram call, my voice was robotic, which could be attributed to internet connectivity. But on a normal call, while I could hear the other side clearly, my speech wasn’t clear at all.


Conclusion

Overall, I think I have to give two conclusions on the Realme Buds Q.

The first is about the onboarding process and advertising. Realme really needs to fix the instruction manual, if they haven’t already. These earbuds may be cheap, but that doesn’t excuse poorly worded instructions. It’s also misleading to advertise “20-hour non-stop music” when the actual battery life between charges is up to 4.5 hours. While Realme does mention the real figures in the spec sheet online, the initial misleading claim is made in bright yellow at the top of the product page.

The second is for everything else. The Realme Buds Q are pretty good earbuds, especially for $30. They’re comfortable, the controls are consistent, the sound is good. The basics are all here, and you can even customize the controls. While the battery life may not win any awards, and I don’t appreciate the misleading claim of “20-hour non-stop music,” 4.5 hours is good enough for budget earbuds. Ignoring the initial pairing process and Realme’s arguably false advertising, the Realme Buds Q are pretty good TWS earbuds.

In most (at least somewhat) positive reviews, I’d take a moment here to recommend getting the product if it’s something you’re interested in, and I was going to. But I read some of the reviews on the Amazon India page (from third-party sellers), and there’s a worrying trend. Many people are reporting connectivity and battery issues. While I haven’t personally experienced these, and some fault could also possibly lie with the presumed-unauthorized seller, it’s also possible that Realme is skimping on quality control. The Realme Buds Q certainly would be worth the $30, but only if there were guaranteed quality assurance. And I’m not seeing that. For that reason, I’m a little hesitant to recommend buying these earbuds.

If you have $30-$35 to spend, and you want the Realme Buds Q, definitely give them a try. But be prepared to perform a warranty exchange. The Realme Buds Q are currently available in India for ₹2,499 and in Europe for €29.99.

Buy the Realme Buds Q: Flipkart (₹2,499) ||| Realme Europe (€29.99)

Honestly, it’s easier to recommend buying something like the Tronsmart Spunky Beat. There’s a version that has app support, they last for 7 hours on a charge, and more controls are available. They’re also about the same price.

The post Realme Buds Q Review: Good-sounding, Affordable TWS Earbuds with Issues appeared first on xda-developers.



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

mercredi 29 juillet 2020

OnePlus phones may finally get an always-on display with Android 11-based OxygenOS 11

Earlier this year, OnePlus finally committed to bring an always-on display feature to OxygenOS. Now, with the stable release of Android 11 coming in September for Pixel phones, OnePlus is teasing that they will introduce an AOD feature in the company’s OxygenOS 11 update.

OnePlus founder and CEO Pete Lau teased the feature with a cheeky Tweet, which you can view below.

While Lau doesn’t explicitly say AOD is coming to OxygenOS 11, it’s hard not to make that conclusion considering OnePlus already committed to bringing the feature to its devices. In fact, it has been one of the community’s most-requested features for months now. Back in March, OnePlus officially added the feature to its software roadmap after overcoming initial power consumption tests. “We are working on fine-tuning AOD to make sure it is perfectly optimized,” said Gary C., an OxygenOS operations staff member.

OnePlus said it has entertained the idea of an AOD feature for a while, but it was apprehensive to release anything official due to power consumption issues. The company explained that AOD “could roughly consume about 350-500 mAh of the batter, which means you might get one or two hours deducted from your daily usage.”

Even still, OnePlus said that people deserve the option if they want it, and considering many popular Android devices already offer an always-on display feature, the company no doubt wanted to bring further feature parity to its devices.

Lau doesn’t provide an exact release date for the always-on display option, but with Android 11 set to drop on September 8, we could see the feature be available shortly after. Last year, OnePlus released an OxygenOS 10 stable update in September, so if history is anything to go by, OxygenOS 11 will begin rolling out in a matter of weeks.

The post OnePlus phones may finally get an always-on display with Android 11-based OxygenOS 11 appeared first on xda-developers.



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

Realme 2 Pro and Realme 5/5s/5i Android 10 kernel source code now available

BBK Electronics’ Realme brand spun out of OPPO, but the brand’s Realme UI is still closely tied to OPPO’s ColorOS software. With the Android 10 update, Realme has introduced its self-branded Realme UI OS to many of its devices. The brand has been gradually publishing updated kernel sources corresponding to those releases. Now, the brand has now posted Android 10-compatible kernel source code for the Realme 2 Pro and the entire non-Pro Realme 5 family that includes the Realme 5, Realme 5s, and the Realme 5i.

Realme 2 Pro

The Qualcomm Snapdragon 660-powered Realme 2 Pro already has a rich aftermarket development community, made possible by the early kernel source drop from Realme. The phone picked up its stable Android 10 update about a month ago. However, the kernel source code corresponding to the update wasn’t made available up until now. You can visit Realme’s GitHub repo at the link below to download the updated source code (all without a proper commit history).

Realme 2 Pro Android 10 Kernel Sources ||| Realme 2 Pro XDA Forums

Realme 5/5s/5i

The Realme 5 and the Realme 5s share a common firmware due to their internal similarities, which means the existing Android Pie-based kernel source for the Realme 5 is somewhat suited for the Realme 5s as well. Despite sporting the same Qualcomm Snapdragon 665 SoC as the Realme 5/5s, the Realme 5i needs its own firmware, although there is very little difference between these devices. That’s why Realme has released the updated kernel source code for the Realme 5i in the same branch as the Realme 5/5s’s release rather than under its own branch as they did earlier this year. Check out the unified source below.

Realme 5/5s/5i Android 10 Kernel Sources ||| Realme 5 XDA Forums

Apart from the lack of commit history, Realme is known for publishing broken and/or incomplete source code. They are still not as swift as OnePlus when it comes to releasing and keeping the kernel sources up-to-date, but at least they are in a much better position than OPPO and Vivo, the two other companies owned by BBK Electronics.

The post Realme 2 Pro and Realme 5/5s/5i Android 10 kernel source code now available appeared first on xda-developers.



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