Jump to content

Google Pixel Buds "Touch and Hold" discontinuation: Difference between revisions

From Consumer Rights Wiki
mNo edit summary
Bythmusters (talk | contribs)
Copyediting and added cargo details, added incomplete notice
Line 1: Line 1:
Google displays an example of a [[Retroactively amended purchases|Retroactively Amended Purchase]] by removing an accesibility feature of the pixel buds line, and failing to offer a reasonable alternative to customers who rely on it.
{{Incomplete|Issue 1=Citations not properly formatted|Issue 2=More info with more in-text citations}}
{{IncidentCargo
|Company=Google
|StartDate=2024
|EndDate=
|Status=Active, Pending Resolution, Resolved, Unresolved
|ProductLine=Pixel
|Product=Pixel Buds
|ArticleType=Product
|Type=Accessibility
|Description=With an update, Google removed an accessibility feature from the Pixel Buds.
}}
 
Google displays an example of a [[Retroactively amended purchases|retroactively amended purchase]] by removing an accessibility feature of the [[Google Pixel Buds|Pixel Buds]] and failing to offer a reasonable alternative to customers who rely on it.


==Background==
==Background==
Google Pixel Buds are a line of Bluetooth earphones that integrate with Android smartphones. The Buds offer standard media and noise isolation controls via a touch sensitive surface. <ref>https://www.youtube.com/watch?v=sz2uaf-DvYw</ref>
Google Pixel Buds are a line of Bluetooth earphones that integrate with Android smartphones. The Buds offer standard media and noise isolation controls via a touch sensitive surface.<ref>https://www.youtube.com/watch?v=sz2uaf-DvYw</ref>


===What makes the buds stand out===
When the assistant is invoked without speaking to it, it will read out the time and read any unread notifications. On supported apps, the assistant feature could be used for text entry.
When the Assistant is invoked without speaking to it, it will read out the time and read any unread notifications. On supported apps, the user would have the option to hold down and dictate their response aloud.


==Removal of the "Touch and Hold" Feature==
==Removal of the "Touch and Hold" Feature==
In Early September of 2024, Google silently rolled out an update removing the "Touch and Hold" Gesture from the earbuds.
In Early September of 2024, Google silently rolled out an update removing the "Touch and Hold" Gesture from the earbuds.


Some users were suggested to ask the Google Asisstant to read their notifications when attempting to invoke the gesture.<ref>https://9to5google.com/2024/09/17/pixel-buds-pro-notifications/</ref>
Some users were suggested to ask the Google Assistant to read their notifications when attempting to invoke the gesture.<ref>https://9to5google.com/2024/09/17/pixel-buds-pro-notifications/</ref>


==Google's response==
==Google's response==
Line 17: Line 29:
==Consumer response==
==Consumer response==


 
A quick Google search reveals dozens of Reddit posts from owners disappointing by the fact it was removed completely instead of being made a toggleable option<ref>https://www.reddit.com/r/GooglePixel/comments/1fleu1g/google_is_taking_away_the_touch_and_hold_function/</ref><ref>https://www.reddit.com/r/pixelbuds/comments/1fleksj/i_got_the_dreaded_touch_and_hold_is_going_away/</ref>, some are looking for workarounds.<ref>https://www.reddit.com/r/pixelbuds/comments/1imf98p/anyone_tried_taskerautomate_to_mimic_touch_and/</ref><ref>https://www.reddit.com/r/pixelbuds/comments/1fefa3i/touch_and_hold_wont_read_notifications_anymore/</ref>
A quick Google search reveals dozens of reddit posts from owners dissapointed by the fact it was removed completely instead of being made a toggleable option<ref>https://www.reddit.com/r/GooglePixel/comments/1fleu1g/google_is_taking_away_the_touch_and_hold_function/</ref><ref>https://www.reddit.com/r/pixelbuds/comments/1fleksj/i_got_the_dreaded_touch_and_hold_is_going_away/</ref>, some are looking for workarounds.<ref>https://www.reddit.com/r/pixelbuds/comments/1imf98p/anyone_tried_taskerautomate_to_mimic_touch_and/</ref><ref>https://www.reddit.com/r/pixelbuds/comments/1fefa3i/touch_and_hold_wont_read_notifications_anymore/</ref>


==References==
==References==

Revision as of 07:54, 13 January 2026

⚠️ Article status notice: This article has been marked as incomplete

This article needs additional work for its sourcing and verifiability to meet the wiki's Content Guidelines and be in line with our Mission Statement for comprehensive coverage of consumer protection issues. In particular:

  1. Citations not properly formatted
  2. More info with more in-text citations

This notice will be removed once the issue/s highlighted above have been addressed and sufficient documentation has been added to establish the systemic nature of these issues. Once you believe the article is ready to have its notice removed, please visit the Moderator's noticeboard, or the discord and post to the #appeals channel.

Learn more ▼

Google displays an example of a retroactively amended purchase by removing an accessibility feature of the Pixel Buds and failing to offer a reasonable alternative to customers who rely on it.

Background

Google Pixel Buds are a line of Bluetooth earphones that integrate with Android smartphones. The Buds offer standard media and noise isolation controls via a touch sensitive surface.[1]

When the assistant is invoked without speaking to it, it will read out the time and read any unread notifications. On supported apps, the assistant feature could be used for text entry.

Removal of the "Touch and Hold" Feature

In Early September of 2024, Google silently rolled out an update removing the "Touch and Hold" Gesture from the earbuds.

Some users were suggested to ask the Google Assistant to read their notifications when attempting to invoke the gesture.[2]

Google's response

In a forum post, Google cited customer feedback for the removal but did not elaborate further. They suggest asking the assistant to read your notifications.[3]

Consumer response

A quick Google search reveals dozens of Reddit posts from owners disappointing by the fact it was removed completely instead of being made a toggleable option[4][5], some are looking for workarounds.[6][7]

References