Samsung’s new app claims to alleviate motion sickness using sound
Samsung released a new free app today called Hearapy, now available for Android devices through the Google Play store, that it claims can reduce the symptoms of motion sickness using just sound. The app's functionality is very straightforward. It plays a low 100Hz sine wave tone through a pair of connected headphones for 60 seconds. […]
Andrew Liszewski
is a senior reporter who’s been covering and reviewing the latest gadgets and tech since 2006, but has loved all things electronic since he was a kid.
Samsung released a new free app today called Hearapy, now available for Android devices through the Google Play store, that it claims can reduce the symptoms of motion sickness using just sound.
The app’s functionality is very straightforward. It plays a low 100Hz sine wave tone through a pair of connected headphones for 60 seconds. This is supposed to stimulate the vestibular system – the parts of the inner ear that are responsible for orientation and maintaining balance. The app allows the duration of the tone to be adjusted between 40 to 120 seconds, but a full minute of listening is supposed to provide relief from motion sickeness symptoms like nausea for up to two hours. It can be repeated as needed.
Samsung says the app was inspired by research conducted by Nagoya University in Japan released last year that found specific sound wavelengths helped to reduce “the staggering and discomfort felt by people that were asked to read a document in a moving vehicle.” It’s not a guaranteed cure, however, and the effectiveness may vary based on the headphones you’re using. Samsung recommends pairing the app with its Galaxy Buds 4 Pro, but while Hearapy works with most headphones or earbuds, they need to be able to reproduce the tone at an 80 to 85-decibel volume level for it to be most effective.
Follow topics and authors from this story to see more like this in your personalized homepage feed and to receive email updates.
- Andrew Liszewski
The Verge AI
https://www.theverge.com/tech/904579/samsung-hearapy-mobile-app-galaxy-buds-motion-sickness-symptomsSign in to highlight and annotate this article

Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
releaseavailableBDD Test Cases from User Stories: 5 Steps and 12 Scenarios
<p><strong>User stories set the destination. Test cases map every path, including the wrong ones.</strong></p> <p>In this post we walk through a 5-step BDD decomposition framework for turning a single user story into concrete Given/When/Then scenarios, with a complete worked coupon example. BDD (Behavior-Driven Development) structures tests as <a href="https://cucumber.io/docs/gherkin/reference/" rel="noopener noreferrer">Given/When/Then scenarios</a> that both stakeholders and tools like Cucumber or SpecFlow can understand.</p> <p>Most teams write user stories in a format like:</p> <blockquote> <p>As a checkout user,<br> I want to apply a discount coupon,<br> So that I pay less for my order.</p> </blockquote> <p>Then they try to extract test cases directly from that sentence. The result i
Preliminary Explorations on Latent Side Task Uplift
TL;DR . This document presents a series of experiments exploring latent side task capability in large language models. We adapt Ryan’s filler token experiment into a more AI Control-like setup with main task and side task and find that Claude Opus 4.5 can solve harder arithmetic problems latently when it has a longer trajectory. This shifts its 50% accuracy threshold from ~5-step to ~6-step problems after 240 lines of irrelevant output. However, we don’t observe strong evidence to believe that current generation of models generally benefit much from wider parallel compute enabled by longer trajectories with the exception of Opus 4.5. Code is made available here GitHub . Longer Agent Outputs Can Increase Side Task Capability. Claude Opus 4.5's latent arithmetic accuracy as a function of pro
Covariate Forecasting: The Next Leap in Time-Series Database Capabilities
<h2> Beyond the Myth of "Simple" Time-Series Forecasting </h2> <p>Many practitioners still view time-series forecasting as a straightforward exercise: use historical data to predict future trends. In real industrial systems, however, the problem is far more complex.</p> <ul> <li>Load forecasting is tightly coupled with temperature variation.</li> <li>Equipment health prediction depends heavily on operating conditions.</li> <li>Wind power forecasting is driven by meteorological factors.</li> <li>Production energy consumption forecasting relies on scheduling plans.</li> </ul> <p>In practice, real-world time series exist within strongly coupled multivariate systems. Relying solely on the historical values of a target variable imposes a natural ceiling on predictive performance. The true techn
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Releases

How to Use the ES2026 Temporal API in Node.js REST APIs (2026 Guide)
<p>After 9 years in development and countless TC39 meetings, the JavaScript Temporal API officially reached <strong>Stage 4 on March 11, 2026</strong>, locking it into the ES2026 specification. That means it's no longer a proposal — it's the future of date and time handling in JavaScript, and you should start using it in your Node.js APIs today.</p> <p>If you've ever shipped a date-related bug in production — DST edge cases, wrong timezone conversions, silent mutation bugs from <code>Date.setDate()</code> — you're not alone. The <code>Date</code> object was designed in 1995, copied from Java, and has been causing developer pain ever since. Temporal is the fix.</p> <p>This guide covers <strong>how to use the ES2026 Temporal API in Node.js REST APIs</strong> with practical, real-world patter

缓存架构深度指南:如何设计高性能缓存系统
<h1> 缓存架构深度指南:如何设计高性能缓存系统 </h1> <blockquote> <p>在现代分布式系统中,缓存是提升系统性能的核心组件。本文将深入探讨缓存架构的设计原则、策略与实战技巧。</p> </blockquote> <h2> 为什么要使用缓存? </h2> <p>在软件系统中,缓存的本质是<strong>用空间换时间</strong>。通过将频繁访问的数据存储在高速存储介质中,减少对慢速数据源的访问次数,从而显著提升系统响应速度。</p> <p>典型场景:</p> <ul> <li>数据库查询结果缓存</li> <li>API响应缓存</li> <li>会话状态缓存</li> <li>计算结果缓存</li> </ul> <h2> 缓存架构设计原则 </h2> <h3> 1. 缓存层级策略 </h3> <p>现代系统通常采用多级缓存架构:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code>┌─────────────────────────────────────────────┐ │ CDN (边缘缓存) │ ├─────────────────────────────────────────────┤ │ Redis/Memcached │ ├─────────────────────────────────────────────┤ │ 本地缓存 │ ├─────────────────────────────────────────────┤ │ 数据库 │ └─────────────────────────────────────────────┘ </code></pre> </div> <p><strong>原则<

Axios Hijack Post-Mortem: How to Audit, Pin, and Automate a Defense
<p>On March 31, 2026, the <code>axios</code> npm package was compromised via a hijacked maintainer account. Two versions, <code>1.14.1</code> and <code>0.30.4</code>, were weaponised with a malicious phantom dependency called <code>plain-crypto-js</code>. It functions as a Remote Access Trojan (RAT) that executes during the <code>postinstall</code> phase and silently exfiltrates environment variables: AWS keys, GitHub tokens, database credentials, and anything present in your <code>.env</code> at install time.</p> <p>The attack window was approximately 3 hours (00:21 to 03:29 UTC) before the packages were unpublished. A single CI run during that window is sufficient exposure.<br> This post documents the forensic audit and remediation steps performed on a Next.js production stack immediatel
Guilford Technical CC to Launch Degrees in AI, Digital Media - govtech.com
<a href="https://news.google.com/rss/articles/CBMipgFBVV95cUxQOXdfNFpXQjJyRlo4aTA1cjdwZk5IbTNTNi1BU25hQUNlSjVXcE5ZelJNbFRMYUZsVFNWZ3lxX21TQ3NocHdLbldydkR0Q1JURXR5eVhXd3ItNjlJcE1TdHFPMnA1c0FQWDBmbWtNRC04YWRIelU5LWU3Rl9ZWHctYU02d2M4WHJ5a2pwaW0xcTRyNkVqSThhNkNxbFlZSkF4Q2tIZHNn?oc=5" target="_blank">Guilford Technical CC to Launch Degrees in AI, Digital Media</a> <font color="#6f6f6f">govtech.com</font>

Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!