maxrave-dev / maxrave-dev/SimpMusic

[Android Auto] Typing in search bar saves every character as an entry in YouTube search history

Open
#2,295 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
11.4k
Forks
599
Avg merge
3d 18h
Merged PRs (30d)
7

Description

Duplicate Check
  • I confirm I searched for existing reports and found no duplicates.
Describe the Bug

When using SimpMusic via Android Auto, typing in the search bar sends every single character typed as an individual query to YouTube's search history. This results in the search history being polluted with incomplete, character-by-character entries (e.g., c, cc, ccc, cccc, etc.).

Note: This behavior does not occur when searching directly from the smartphone application interface.

Steps to Reproduce
  1. Connect the phone to Android Auto.
  2. Open SimpMusic on the head unit display.
  3. Open the search bar and type a query character by character (e.g., typing cccccc).
  4. Check your YouTube search history (via YouTube app or web).
  5. Notice that every intermediate typing step has been saved as an individual search history item.
Expected Behavior

Partial queries sent while typing on Android Auto should not pollute the YouTube search history. Only finalized searches (or proper debounced search submissions) should be added to the history, consistent with the smartphone app's behavior.

App Version

1.6.0

Android Version

Android 16

Device Model

Nothing Phone 3a

Custom ROM
  • I am using a custom ROM
Custom ROM Name (if applicable)

No response

Screenshots (optional)
Image Image
Log / Error Details

N/A (No crash occurred)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by tracing the Android Auto search handling and compare it with the smartphone application's search flow, then reproduce the character-by-character query behavior. Done means intermediate queries no longer create history entries and only finalized or properly debounced searches are recorded.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.