[sheedonz]

Problem

When the car is switched off, Android Auto disconnects and the Fermata process is usually killed. Next time Fermata is opened, YouTube always starts on the home page and the unfinished video is lost.

YoutubeFragment only keeps the page URL in the fragment's saved state (onSaveInstanceState), which doesn't survive the process being killed. YT_RESUME_POS is persisted, but it's only applied when the YouTube engine is already the active one, which is never the case after a fresh start.

Change

• Save while playing: the URL and position of the playing video are stored in the addon preferences every 5 seconds and on pause.
  • The URL comes from the player (movie_player.getVideoData().video_id) when the page isn't a /watch or /shorts/ page. m.youtube.com plays search results and feed items inline without changing location.href, so the page URL alone isn't enough.
• Restore on a fresh start: when the fragment is created without saved state, the saved video is loaded with t=<seconds>s.
• Unmute once: YouTube mutes videos that autoplay without a user gesture, so the resumed video is unmuted once when it starts playing. Other autoplayed videos (feed previews) are left alone.
• Clear when finished: the saved video is removed when it ends.
• New setting: "Resume last video" in the YouTube addon settings, enabled by default.

Restarts where the fragment's saved state survives are unchanged.

Testing

Tested on an Honor 400 Pro (Android 16) with a 2.0.2 auto build that includes this change:

• Played a video from search results (inline playback), force-stopped the app at 35 s, relaunched: it opened the same video at 35 s and kept playing. Repeated at 75 s and 235 s with the same result.
• The resumed video plays with sound (no "tap to unmute"; an active media audio player is reported).
• The new setting appears in Settings → Addons → YouTube.

Not tested: inside a real car (my own build isn't listed by Android Auto because it's not signed with your key, which is why I'm sending this upstream rather than running a fork), and the "video ended clears the session" path.

Only English strings are added; the other values-* files fall back to them.

🤖 Generated with Claude Code

[rickselest]

This sounds awesome. Would love this feature. Thanks for working on it.

[AndreyPavlenko]

Review: resume last video. Request changes on the must-fix items below. Should-fix items can land in this PR.

Must fix

1. Autoplay previews overwrite and clear the saved session. JS_VIDEO_ENDED calls clearLastVideo() unconditionally, so a finished feed or search preview deletes the user's unfinished video. timeupdate and pause also save for any playing video, so the stored target becomes whatever played last. Suggested fix: skip progress saves while the video is muted, and on ended clear only when the ended video id matches the saved id (send the id with the event).

2. The unmute flag can be consumed by the wrong video. unmuteOnPlay() is armed in onViewCreated before loadUrl(DEFAULT_URL). If the home page autoplays a muted preview, the first playing event consumes the flag: the preview is unmuted and the resumed video stays muted. Suggested fix: pass the resumed video id to unmuteOnPlay(id) and unmute in playing() only when fermataVideoUrl() contains that id. Note that fix 1 and this one interact: the resumed video starts muted, so the "skip while muted" check must exempt it.

Should fix

3. Progress is saved even when "Resume last video" is off. saveLastVideo writes prefs every 5 s regardless of YT_RESUME_LAST. Gate the save on the pref.

4. lastSavedUrl only drives logging. Remove the field and the changed flag, or drop the log lines.

5. getVideoUrl() fallback conflicts with isVideoUrl. Stream URLs usually lack /watch? and /shorts/, so the filter rejects them. Drop the branch or make the filter match what it returns.

6. No automated check for the new logic. getResumeUrl (query rewrite, t replacement, pos > 0) and saveProgress parsing are plain Java and easy to unit test. The ended path is untested per the description.

Also consider: the p.unMute() plus v.muted = false pair is a workaround for platform muting; a comment saying so would help the next reader.

— Claude