No new products after current stock sells

WinFuture says the decision has already been presented during closed press briefings. The report claims that no new OnePlus products will launch in Europe or the US once the remaining stock has been sold.

Previously announced software support is not expected to change. OnePlus would continue operating in China and India in a reduced form, while Oppo is expected to widen its European presence.

OnePlus has not confirmed the withdrawal at the time of writing, so this remains a report rather than an official announcement. Still, it follows months of warning signs. OnePlus Europe previously said it was evaluating its regional roadmap and product strategy, while its websites in several European countries began directing shoppers towards Oppo products.

What this could mean for OnePlus watches

Of course, most of the attention will sit on OnePlus phones. But if the pullback covers the full product range, it would also bring the Western run of OnePlus smartwatches to an abrupt end.

That could make the recently launched OnePlus Watch 4 the final model officially released across these markets. It arrived in April with a titanium body, Wear OS 6, dual-band GPS and the multi-day battery formula that helped the series stand out from most Wear OS rivals.

I have tested several versions of the company’s watches, and the line had finally settled into a convincing rhythm. The larger model won me over in my OnePlus Watch 3 review with its battery life, reliable GPS and smooth dual-chip setup, while the 43mm version kept most of that experience in a case better suited to smaller wrists.

The OnePlus Watch Lite took another route by dropping Wear OS and concentrating on a lighter, simpler experience. It still delivered dependable heart-rate and GPS results in my testing, giving the range a useful lower-cost option rather than a watered-down flagship.

That variety is what would disappear. OnePlus had started covering both ends of the market, with full Wear OS models for people who wanted apps and Google services, plus a simpler watch for those who cared more about tracking and battery life.

Current owners should not panic

Current owners should not expect their watches to stop working if OnePlus confirms the exit. The report says previously promised software support should continue, while services such as Wear OS, Google Wallet and the OHealth app already sit within a wider software ecosystem.

The longer-term picture is less certain. Warranty handling, replacement availability and regional support could become more awkward as inventory clears, while future features will depend on how much attention Oppo continues to give existing OnePlus devices.

OnePlus has produced some of the better recent alternatives to Samsung and Google in the Wear OS market. If the report proves correct, smartwatch buyers will lose one of the few brands pushing genuine multi-day battery life on Google’s platform.

The post OnePlus may leave Europe and the US, putting future watches in doubt appeared first on Gadgets & Wearables.

How Bevel works with Fitbit Air through Google Health

Bevel already works with several wearable platforms, including Apple Watch, Garmin, Oura and Amazfit. Fitbit Air remained a fairly obvious gap, particularly for iPhone users who had moved from an Apple Watch but wanted to continue using Bevel.

The new Google Health integration closes that gap. Google Health now acts as the bridge between Fitbit Air and Bevel, automatically bringing compatible health data into the app rather than requiring a manual workaround through Apple Health.

That connection makes particular sense for Fitbit Air. As I found in my full Fitbit Air review, the screenless tracker is designed to disappear on the wrist and leave most of the interpretation to the phone app. The hardware collects the data, but the software determines how useful that data feels.

Bevel provides a different way to view it. The app centres its experience around recovery, strain, sleep, fitness and longer-term health trends. Its recent Bevel 3 update added Biological Age and Health Records, allowing wearable information to sit alongside blood tests, clinical documents and lifestyle data.

There is an important distinction here. Google Health integration does not mean Bevel has launched on Android. Bevel remains an iPhone app, but it can now receive information held in Google Health from Fitbit Air and other compatible devices.

The wider update goes beyond Google Health

Google Health support forms part of Bevel’s 2026 Mid-Summer Release, which also expands Bevel Intelligence. Users can now ask the AI system to build complete cardio workouts using targets based on time, distance, intervals, pace, power or heart rate zones.

Those workouts can sync to Apple Watch for use during training. Google Calendar and iCloud Calendar integration also allow Bevel Intelligence to adapt a training schedule around meetings, appointments and other events rather than treating exercise plans as separate from the rest of the day.

Bevel has also introduced Ghost Mode for temporary conversations and food logging. Chats can expire after between one and 24 hours, while new controls let users disable persistent knowledge and choose between fast, thinking and adaptive response modes.

Strength Builder receives its own set of changes. AirPods Pro 3 can display live heart rate on the phone, while a rebuilt Live Sync system aims to improve communication between Apple Watch and iPhone. Users also get exercise previews on the watch, on-the-fly set editing and support for dual-loaded machines in the plate calculator.

Blood pressure tracking is now available inside the Biology section. Readings can sync from Apple Health or be entered manually, while the nutrition database has gained thousands of additional foods and improvements to portion selection and meal analysis.

Bevel becomes a more credible Fitbit companion

The timing is interesting because Bevel has spent the past year reducing the barriers to using its platform. Most of the core app became free with version 2.4, while Bevel Intelligence remained the main paid layer.

For Fitbit Air owners, the new integration creates a clearer choice. They can use Google Health as the main destination for their data or feed the same wearable information into Bevel for a more recovery-led presentation.

The figures shown by the two apps may not always match exactly. Bevel applies its own calculations and scoring methods, so sleep, resting heart rate and recovery outputs can differ even when the underlying information comes from Google Health.

The post Bevel adds Google Health support for Fitbit Air users appeared first on Gadgets & Wearables.

The teardown published on iFixit was carried out specifically to investigate why one of the buttons had fallen out. Opening the watch revealed retaining clips on the other button stems, while the affected button had no clip at all.

One missing part explains the failure

That provides a fairly convincing explanation for this individual failure. The button was not worn down or damaged by a difficult repair, it appears to have left the factory without the component needed to secure it inside the case.

Similar button problems have been reported by some Pebble Time 2 and Pebble 2 Duo owners. The teardown cannot show how many watches are affected, but it moves the discussion beyond software glitches by documenting a physical assembly fault in a production unit.

Other owners have described the Pebble Time 2’s front glass cracking after relatively minor impacts. The glass sits slightly above the surrounding metal frame, leaving its edge more exposed, although Pebble has not acknowledged a design problem or published failure figures.

Those reports should still be treated cautiously. Photos and individual experiences do not establish that the display is unusually fragile across the wider production run, especially when plenty of owners have not experienced a crack.

Repairs may not be straightforward

The watch is held together by four screws and the back can be removed relatively easily. Once inside, however, the design becomes less repair-friendly.

The 185mAh battery is soldered to the main board rather than attached through a simple connector. Reaching the display also requires heat because the front glass and screen are glued into place, making a home repair far more involved than the removable back initially suggests.

The bigger concern for buyers is Pebble’s official 30-day warranty. Core Devices covers manufacturing defects for only 30 days after the watch is received, with the company explaining that its smaller operation needs to limit its exposure to hardware claims.

That is important because assembly problems may not become obvious immediately. A loose or unsecured button could survive the first few weeks before falling out after the written warranty has expired.

Our earlier Pebble Time 2 report covered the watch completing production testing and entering mass production after several delays. This teardown suggests at least one assembly problem still made it through those checks.

There is not enough evidence to call this a production-wide failure. Still, new owners would be sensible to inspect every button closely and test them repeatedly during the first 30 days, while their watch remains covered by Pebble’s unusually short warranty.

The post Pebble Time 2 teardown exposes a missing button clip appeared first on Gadgets & Wearables.

The problem and the fix

The frustrating part was that the ring often seemed to be working. Owners could still see heart-rate information from the night, but the app would leave Sleep and Readiness blank the next morning.

In some cases, this continued for several nights. Reports on Reddit and Facebook described people charging the ring, syncing it again and trying a soft reset without bringing the missing results back. The presence of overnight heart-rate data suggested that the ring had not simply run out of power or been worn incorrectly.

That lines up with Oura’s own description. The company says Ring 4 and Ring 5 could collect enough information to recognise a sleep session, yet fail to display it in the iPhone app.

Oura has now marked the problem as fixed and directs affected iPhone users to install app version 7.18.2. Cases connected with recent ring firmware, which could also remove Readiness information, are listed as resolved.

What to try if your data is missing

Start by updating the Oura app through Apple’s App Store. Once the update is installed, place the ring on its charger and sync it again.

If the results are still missing, Oura recommends changing the app’s location permission to either Always or Never. Close the app, reopen it and run another sync.

Some owners have found that removing the ring from the phone’s Bluetooth settings and reconnecting it restores normal tracking. This is an unofficial workaround but may be worth trying if updating and resyncing do not help.

The final step is to contact Oura support and share the ring diagnostics. Support can then check whether the device is syncing properly or whether the hardware needs further attention.

The fix follows a larger Oura rollout

The correction arrives as Oura expands its software across several ring generations. In our previous Oura update article, we covered Ring 5 features moving to older models alongside live activity tracking, lab uploads and additional health tools.

Those additions are less useful when the underlying overnight record is incomplete. Sleep and Readiness remain central to the Oura experience, so losing an entire night has a noticeable effect on the following day’s guidance.

Ring 4 and Ring 5 owners using an iPhone should check that the Oura app has reached version 7.18.2. Anyone who continues to see gaps after updating, checking location access and resyncing the ring should contact Oura support.

The post Oura update restores missing Sleep and Readiness scores appeared first on Gadgets & Wearables.

I left both trackers alone

Fitbit Air and Whoop are designed to blend into the background. You wear them, get on with your day and check the results later.

That convenience formed a big part of my earlier Fitbit Air versus Whoop comparison. This time, I wanted to see what happens when neither tracker receives any help. Will they properly track my run?

I wore Fitbit Air on one ankle and Whoop on the other because I wanted to use both as secondary background trackers while keeping my Garmin Forerunner on my wrist. I did not start a workout from either phone app, so both devices had to recognise the run automatically.

Garmin measured 8.10km in 47 minutes and 17 seconds, with an average heart rate of 139 bpm and a maximum of 161 bpm. An easy run. The total elapsed time was 49 minutes and 15 seconds because I stopped briefly mid-session.

Whoop recorded far too much

Whoop recognised the activity as walking (which I then changed to running in the app). But it placed the start time at 3:06pm and the finish at 5:53pm. That gave me a running workout lasting 2 hours, 47 minutes and 59 seconds.

Now, I was actually walking before and after the run. So Whoop appears to have pulled much of that surrounding movement into a single activity. The result was 11,938 steps, 1,169 calories and an activity strain of 15.8.

Its average heart rate came in at only 114 bpm, well below Garmin’s 139 bpm. Whoop also recorded a maximum of 180 bpm, compared with 161 bpm on the Garmin.

The heart-rate graph makes the problem obvious. It includes long low-intensity sections, repeated drops and several sharp changes that do not resemble one continuous 8km run.

Whoop detected that something was happening, but it failed to understand when the run actually started and ended. That undermined almost every number attached to the activity.

Fitbit Air missed the opening section

Fitbit Air produced a much cleaner activity, but Google Health initially placed its start at 4:26pm, around ten minutes after I began the Garmin activity. That gave me a distance of 6.11km and a duration of 39 minutes and 34 seconds.

Its average heart rate came in at 142 bpm, only 3 bpm above Garmin. The maximum was 159 bpm, compared with 161 bpm on the Garmin. Fitbit also counted 6,580 steps and estimated 513 calories during the initially detected section.

The good thing is that Google Health lets you edit the start and end times of an automatically detected activity from the Fitness tab. When I moved the start time back by ten minutes, the recorded distance increased from 6.11km to 7.77km. That left it 330 metres short of Garmin’s 8.10km result.

This changes the interpretation considerably. Fitbit Air had not completely lost the opening section. Google Health had retained enough underlying data to recalculate most of the missing distance once I corrected the start time.

However, it also means automatic detection needs checking after the activity. A hands-off tracker should ideally identify the correct boundaries without requiring the user to adjust them manually.

There was no route map in the app, so I cannot confirm whether the distance came from the phone’s GPS, movement estimates or a combination of the two. But the final 7.77km result was much closer to Garmin than the initially detected activity suggested.

Background tracking still needs checking

So what’s the takeaway?

Fitbit Air delivered the better result after I corrected its start time. Its 7.77km distance came reasonably close to Garmin’s 8.10km, while its average and maximum heart-rate readings were also close.

Whoop captured far too much surrounding activity. Fitbit detected too little initially, although editing the start time recovered most of the missing distance. Neither produced a record I could accept without checking it, but Fitbit’s corrected result was clearly the more usable of the two.

This was an ankle test, so it should not be treated as a verdict on normal wrist performance. But for devices built around passive tracking, the basic lesson is hard to ignore. Wearing them and forgetting about them still means checking their work afterwards.

For a deeper look at each device, read my full Fitbit Air review and Whoop review.

The post I let Fitbit Air and Whoop automatically track the same 8km run appeared first on Gadgets & Wearables.

The AI toggle comes with a heavy warning

As first reported by How-To-Geek, the setting appears inside Samsung Health’s privacy controls under the label “Consent to the use of health data for AI training and modeling.” It sits alongside separate permissions covering other data. Some Samsung Health users are finding the AI training consent switched on after accepting the app’s latest privacy notice.

On the surface, this looks like a normal opt-in control. Users can move the switch off when they do not want their health information used to develop Samsung’s AI systems.

The next screen changes the picture. After the consent is withdrawn, Samsung Health displays a warning saying the user will no longer be able to sync health data with their Samsung account!

It also states that health data will be deleted unless Samsung must retain it under applicable law. Any legally retained information will then be erased when the required retention period ends.

So this is not really just a simple AI toggle. You can say no to Samsung using your data for AI training, but you may also lose cloud syncing and some of your stored health history. Not good.

The exact process may depend on where you live and which privacy rules apply. Users in other regions may see different wording, a separate consent process or no AI training switch at all. Samsung does not make those regional differences particularly clear inside the app.

Some important details remain unclear

The warning is still pretty vague. It does not say whether only data stored on Samsung’s servers will be deleted or whether anything saved locally in Samsung Health could disappear too. It also leaves open the question of which tracking features still work without account sync.

That is not a small detail for long-time Galaxy Watch users. Samsung Health can hold years of activity, sleep, heart rate and body composition data, along with medication details, health records and cycle tracking information.

Samsung’s US consumer health privacy statement says users can withdraw consent where the law allows it. Once they do, Samsung should stop the related collection, use and sharing of their health data. The app also includes options to download or erase personal information.

Downloading data first looks sensible

Anyone planning to withdraw consent should download a copy of their Samsung Health information before confirming the change. The option appears in Samsung Health under Settings, followed by Download personal data.

The downloaded archive gives users some protection if the withdrawal process removes their synced history. It also provides a clearer picture of what Samsung Health has stored before the account connection changes.

The larger problem is not that Samsung asks for permission to train AI. A separate toggle is better than hiding that use inside a general privacy policy.

The problem is the apparent connection between declining AI training and losing cloud syncing or stored data. Consent can technically remain optional while still becoming difficult to refuse in practice.

The timing is handy, with Galaxy Unpacked set for July 22. Samsung is expected to show off new Galaxy Watches and more health AI, so this privacy question may soon get even bigger.

The post Samsung Health users face an awkward choice over AI training appeared first on Gadgets & Wearables.

Battery complaints have been around for weeks

The battery issue is the more notable of the two. Complaints first appeared while owners were running version 22.35, with some reporting that the problem continued after they moved to 22.38.

That update arrived in late June with fixes for crashes during golf activities, incorrect dive-depth behaviour and an LTE LiveTrack problem. It did not include anything related to power consumption.

Reports on Garmin’s forums described watches running down considerably faster than expected. Some owners found themselves charging every day or even more frequently, while Garmin support staff contacted affected users to gather information.

Version 22.39 is the first stable release to name a fix for the problem. Garmin describes it as a fix for “possible battery drain”, although it has not explained what was causing the watches to lose power so quickly.

The second change addresses possible problems during voice calls. Garmin has not provided any further detail, so it is unclear whether this relates to failed calls, dropped connections or another part of the calling experience.

Garmin says the staged rollout has reached 20% and will increase as it progresses. Owners who do not see version 22.39 immediately may therefore need to wait for it to reach their watch.

Only the Pro models are named

The announcement covers the Fenix 8 Pro and Fenix 8 Pro MicroLED. Garmin has not included the standard Fenix 8, Fenix E, Enduro 3, Tactix 8 or Quatix 8 in this particular rollout notice.

That is worth noting because some standard Fenix 8 owners have reported similar battery behaviour. It does not necessarily mean the watches share the same fault, but Garmin has yet to announce a corresponding fix for them.

Separate rollout notices are common across Garmin’s closely related watch families. Another release may follow, although there is currently nothing official to confirm that.

This is not a feature update, but it may prove more valuable than one for affected owners. A Fenix watch that suddenly needs daily charging loses one of its main advantages, so the early response to version 22.39 should quickly show whether Garmin has dealt with the problem.

The post Garmin targets Fenix 8 Pro battery drain with update 22.39 appeared first on Gadgets & Wearables.

Two versions are moving through certification

The strongest evidence comes from two new Xiaomi smart bands approved in China on June 5. The paired models are believed to represent the regular Smart Band 11 and a separate NFC version, although regulators use the generic name Smart Band rather than the final retail names.

To remind, Xiaomi used closely related model numbers for the standard and NFC versions of Smart Band 10. And the two new devices were approved in China on the same day. That supports the Smart Band 11 and Smart Band 11 NFC interpretation.

A related certification then surfaced at Taiwan’s NCC, while the presumed NFC version reached the UAE’s TDRA on July 8. The UAE entry classifies it as a short-range, low-power device, which confirms little beyond wireless connectivity but adds another market to the launch trail.

Documents linked to the Taiwan filing show a 233mAh battery. That matches Smart Band 10, so a large capacity increase does not appear to be part of this generation. Battery life could still change through the display, processor and software, while an earlier leak also claimed faster magnetic charging.

Xiaomi has also named Smart Band 11 in its own Clue Plus promotional terms. The offer covers the UK, UAE, Taiwan, Japan and several European markets, providing stronger evidence of an international release than the regulatory filings alone. Only the regular variant is mentioned there, no Active or Pro.

Late July or August looks more likely

There is still no confirmed Smart Band 11 event. Xiaomi has scheduled a Redmi Note 17 launch in China for July 14, but the company has not teased a fitness band and no reliable leak has connected Band 11 to that presentation.

A launch later in July or during August looks more plausible. Regulatory approval often arrives shortly before Xiaomi begins promoting a wearable.

Smart Band 10 was announced in China on June 26, 2025 and reached international markets shortly afterwards. Xiaomi could follow a similar approach this year rather than holding the global version back for a separate event months later.

Our previous Smart Band 11 coverage looked at a specification leak claiming a larger 1.78-inch display with 2200-nit brightness, HRV monitoring, body-temperature sensing, EDA-assisted stress data and a barometer. It also mentioned recovery scoring, more than 200 sports modes and ten-minute charging for up to three days of use.

Anyone considering Smart Band 10 may want to wait until Xiaomi reveals its plans. The current certification pace makes a launch within the next several weeks very possible.

Sources: China CMIIT standard model filing, China CMIIT NFC model filing, Taiwan NCC filing, UAE TDRA equipment database, Xiaomi Clue Plus offer terms

The post Xiaomi Smart Band 11 certifications point to a late summer launch appeared first on Gadgets & Wearables.

The UK filing adds another piece

We covered Garmin CIRQA earlier this week after spotting new trademark filings in Canada and Europe. At the time, that already made the name more interesting because it showed Garmin protecting CIRQA beyond the original US filing from February.

Now there is another entry to add to the list. Credit goes to one of our readers, who spotted the UK filing and pointed us in its direction.

The UK Intellectual Property Office shows CIRQA under trade mark number UK00004405896, with the application received on June 23, 2026. The same date is also shown for examination, while the status history moved to pre-publication on July 2.

That does not mean that the trademark has completed the whole registration process. But it does show Garmin is continuing to secure the CIRQA name across major markets. The timing also lines up with the EUIPO and CIPO filings we reported previously.

The UK filing lists a priority date of February 25, 2026, with the United States of America as the priority country. It also references US trademark number 99670310, which ties this new UK entry back to the original USPTO filing.

The device wording stays the same

The UK listing keeps the same Class 9 language seen in the earlier filings. It describes CIRQA as wearable devices and instruments placed on the human body, including electronic sensors and monitors for measuring and analysing physical parameters, physiological data, bio-signals and bodily behaviour.

The filing also mentions recovery from physical and emotional stress, human alertness level, performance, training, storing and transmitting data, and receiving instructions related to those functions. It again frames the device for non-medical and non-therapeutic purposes.

There is still room for interpretation here. Trademark descriptions tend to cast a wide net, and Garmin will not reveal the actual product through legal wording alone. But the language remains specific enough to hint at a Whoop-like device, or at least something designed to sit outside the usual Garmin watch format.

The CIRQA trail now covers the US, Canada, Europe and the UK. That does not confirm a launch is imminent, but it does suggest Garmin is doing more than parking a name in one market.

Our guess is that CIRQA could make its debut around late August. Garmin often has new hardware to show around IFA in Berlin, and a body-worn recovery or performance sensor would give it a different kind of wearable story from another sports watch.

This article originally appeared on Gadgets & Wearables, the first media outlet to report the story.

The post Garmin CIRQA trademark trail expands to the UK appeared first on Gadgets & Wearables.

VO2 max gets a recalibration pass

The most interesting item is the VO2 max algorithm change. Zepp Health says the update improves VO2 max accuracy, but also adds that results will be gradually calibrated based on new workout data after installation.

Which means owners should not expect the watch to instantly rewrite their fitness profile the moment the update finishes. The Balance 2 will need fresh sessions before the updated algorithm has enough recent data to settle. This, most would agree, is a sensible approach.

The altitude fix is also worth watching in real use. Zepp Health says the new firmware improves altitude data stability during outdoor workouts and reduces abnormal fluctuations in accumulated ascent and descent. In fact, we have noticed some issue with altitude tracking in device we have been testing in recent months. Hopefully, this will help to resolve the discrepancies.

Zepp Flow gets more useful on the wrist

Zepp Flow also gets a broader set of changes. The update adds more flexible volume control, quicker voice feedback and improvements around notification reminders and related settings.

The change-log also mentions expanded voice interaction. Balance 2 owners can now ask for HybridCharge-related information and use voice commands to reach more workout modes, system apps and frequently used features.

Map navigation gets a smaller tweak, but one that could matter mid-session. After opening the map track menu during a workout, users can access the feature through a newly added navigation entry.

Golf also gets attention, but this is more niche. The firmware changes the completion reminder wording for golf course data downloads and terrain map downloads. It also adjusts hole-switching logic to improve behaviour on the course.

A small update

There is no sign here of Zepp OS 6 or Strava Live Segments, if that is what you were waiting for. But for current Balance 2 owners, the practical takeaway is simple. Install it before your next run, hike or round of golf, then give the VO2 max and altitude changes a few workouts before judging them.

The late June firmware brought bigger owner-facing additions, including HybridCharge, Next Hard Session, HYROX tools, Helio Core Motion accessory support and several workout-related improvements. This new update looks more like a clean-up pass after that larger feature drop.

The post Amazfit Balance 2 update tweaks VO2 max altitude and Zepp Flow appeared first on Gadgets & Wearables.