Android Auto #578

puff · 2024-01-17T07:27:24Z

Adds basic Android Auto and Android Automotive support.

Features:

Browse & play albums, playlists, and albums in each genre.
Artists start an instant mix when playing them.
Jump to albums/artists by letter (click A-Z on scroll bar).
Seek forwards and backwards in songs.
Skip to previous and next songs in queue, as well as directly to any song in the queue.
Shuffle button
Offline mode support.
- Even outside of offline mode, it will try to use downloaded items before going online, unless it is fetching all items for root category (e.g. albums, artists, etc).
Search (voice and keyboard)

Future features/TODO?

Repeat button
Favorite button
Instant mix button
Home tab
Genres should start an instant mix (not yet implemented in Finamp)
Offline mode artists/genres instant mix (not yet implemented in Finamp)

Currently, there is a hard limit of ~~100~~ 250 (online mode) or 1000 (offline mode) items displayed so the app doesn't crash on large libraries.

// dev notes

Investigate why it doesn't switch to the Now Playing screen sometimes when starting playback, or takes a while before switching to it. This is likely because of the playback states being wrong.
Add pagination so we can show more than 100 items. This and This may be useful.

jmshrv · 2024-01-18T13:42:53Z

This is awesome to see finally :)

Is the 100 item limit just an awkward thing with Android Auto or a thing that specifically needs to be fixed here? Jellyfin luckily makes pagination very easy when fetching from the server.

Artwork sounds like an annoying issue to fix though 🙃

puff · 2024-01-18T16:21:57Z

Is the 100 item limit just an awkward thing with Android Auto or a thing that specifically needs to be fixed here? Jellyfin luckily makes pagination very easy when fetching from the server.

I put that limit because someone reported Android Auto crashing on large libraries (1000+) I do have an idea on how to add pagination to it, so I'll probably work on that tonight.

Artwork sounds like an annoying issue to fix though 🙃

Yeah, I'm gonna have to do some experimentation with that.

Chaphasilor · 2024-01-18T16:25:31Z

Thanks for the PR! I can try to take a look at it in the coming days, I just need to find a car to test with ^^

I'm guessing there is no built-in pagination support in Android Auto, and I don't think it would be super useful anyway.
I believe focussing on quick actions, like shuffle all songs, instant mixes and playing recently played items is a good approach.

Search and some voice interactions would definitely be useful down the road (hah), but if basic playback and browsing is working then I guess it qualifies for a beta.
Maybe it attracts some additional contributors :P

puff · 2024-01-18T18:34:28Z

I just need to find a car to test with ^^

You can use the emulator! #24 (comment) It's very convenient for debugging too.

I'm guessing there is no built-in pagination support in Android Auto, and I don't think it would be super useful anyway. I believe focussing on quick actions, like shuffle all songs, instant mixes and playing recently played items is a good approach.

Yeah, I think I agree with you. Not sure that pagination should be a priority. I typically just use a playlist anyway lol.

Search and some voice interactions would definitely be useful down the road (hah)

Yeah, 100%. I wanted to incorporate that into this PR, but I was having an issue I didn't really understand where it crashes when searching. EDIT: fixed the crash, was a problem with changing the package name

Chaphasilor · 2024-01-18T20:55:10Z

Yeah I know about the emulator and have used it last time, but in the end I want to make sure everything works on an actual car too ^^

Regarding voice, how flexible is that? Can it only be used for voice search, or could we enable custom actions, like saying "Start playing Hello by Adele" and it will start an instant mix?

puff · 2024-01-18T21:52:54Z

Can it only be used for voice search, or could we enable custom actions, like saying "Start playing Hello by Adele" and it will start an instant mix?

I know you can do stuff like that with app actions. There's also a version for Android Auto/Automotive.

Chaphasilor · 2024-01-18T22:33:15Z

The second link you provided seems to be geared towards navigation/Points-of-Interest apps. Here's the one for media apps: https://developer.android.com/training/cars/media#support_voice

Seems like it has everything we need. If the user indicates an item type (album, playlist, etc.) we can use that to deal with Jellyfin's poor search, and if they omit the type "Play some music" we could resort to shuffle all for now. Would you like to look into it? :)

puff · 2024-01-19T01:39:24Z

Would you like to look into it? :)

Sure, I have some time the next few days so I'll see if I can understand this and get something usable.

Chaphasilor · 2024-01-19T16:02:38Z

Awesome. Let me know if you need help with anything!

Edit: Just checked it out on the emulator, here are a few things I noticed:

Clicking an item in the "Genres" tab should start an instant mix for that genre. Searching for albums by genre is probably not used that often and not really suitable for driving anyway
- Same thing for artists maybe?
Placeholder images (especially for artists) would be nice to make sure the item names are aligned
For albums and playlists I'd really like to either be prompted if I want to play in-order or shuffled (that might not be ideal while driving), or have a way in the settings to set default behavior
The sorting is a bit different than in the phone app, not sure if you can do anything about it. Names that start with symbols are sorted by the first non-symbol character in the car, but not on the phone. Examples are "...Baby one more time", "& Friends" is "F", ".me", "(Un)Commentary"
The jump-to-letter function is neat, but only works with the loaded items. Is there a way to load items on-demand, like is done with the new "fast scroller" on the phone app?
I think we definitely need a "home" tab/section. I'll see if I can get something going for the entire app, since the phone app is supposed to also get a home screen with the redesign
- There's also a "for you" section in the Android Auto home screen music widget (swiping left on the music widget) where the items from the home screen could be shown. Right now it just shows first 3 items from the albums tab, although strangely in the sorting of the phone app (symbols first)
There's a display bug when shuffle is active. The order of the list is correct, but the index of the currently playing song is not shown correctly in the list (the bars next to the active song are on the wrong item). Did you do any implementation for the queue? Otherwise I'll have to dive into just_audio once again to see if I can fix it...

puff · 2024-01-20T17:40:56Z

Thanks for the feedback, I agree with your observations here.

Clicking an item in the "Genres" tab should start an instant mix for that genre

I was thinking we could replace the genre tab with the home tab. Android Auto by default only allows 4 tabs, and genres don't have instant mixes (though we could shuffle albums within the genre).

For albums and playlists I'd really like to either be prompted if I want to play in-order or shuffled

I don't think this is possible, but a setting for the default would work.

The sorting is a bit different than in the phone app
The jump-to-letter function is neat, but only works with the loaded items

I don't think I can do anything about these :(, they seem to be built into Android Auto.

There's also a "for you" section...

Seems like this is related to that section, looks to be possible.

There's a display bug when shuffle is active

I've done a little troubleshooting, and I'm confused. It seems there may be a bug somewhere causing a conflict between just_audio and the new queue service?

finamp/lib/services/music_player_background_task.dart

Line 377 in 2ea2156

queueIndex: event.currentIndex,

The queue service expects queueIndex to be the non-shuffled, original index:

finamp/lib/services/queue_service.dart

Lines 94 to 101 in 2ea2156

    
           _queueAudioSourceIndex = event.queueIndex ?? 0; 
        
           if (previousIndex != _queueAudioSourceIndex) { 
        
             int adjustedQueueIndex = (playbackOrder == 
        
                         FinampPlaybackOrder.shuffled && 
        
                     _queueAudioSource.shuffleIndices.isNotEmpty) 
        
                 ? _queueAudioSource.shuffleIndices.indexOf(_queueAudioSourceIndex) 
        
                 : _queueAudioSourceIndex;

finamp/lib/services/queue_service.dart

Lines 148 to 151 in 2ea2156

    
           int adjustedQueueIndex = (playbackOrder == FinampPlaybackOrder.shuffled && 
        
                   _queueAudioSource.shuffleIndices.isNotEmpty) 
        
               ? _queueAudioSource.shuffleIndices.indexOf(_queueAudioSourceIndex) 
        
               : _queueAudioSourceIndex;

I suspect somewhere in just_audio expects it to be the shuffled index and is sending it to the backend (ExoPlayer?), which results in the queue showing the wrong song as selected. To elaborate, the erroneous selected song in queue is in the position of the original (non-shuffled) index, which is why I suspect this.

Changing queueIndex to the shuffled index, and replacing both occurrences of adjustedQueueIndex in queue_service directly to _queueAudioSourceIndex fixes the issue, however I'm not sure of the implications of this.

music_player_background_task.dart

- queueIndex: event.currentIndex,
+ queueIndex: _player.shuffleModeEnabled && (shuffleIndices?.isNotEmpty ?? false) && event.currentIndex != null ? shuffleIndices!.indexOf(event.currentIndex!) : event.currentIndex,

queue_service.dart

-int adjustedQueueIndex = (playbackOrder == FinampPlaybackOrder.shuffled &&
-         _queueAudioSource.shuffleIndices.isNotEmpty)
-     ? _queueAudioSource.shuffleIndices.indexOf(_queueAudioSourceIndex)
-     : _queueAudioSourceIndex;
+ int adjustedQueueIndex = _queueAudioSourceIndex;

Chaphasilor · 2024-01-21T10:52:36Z

We could reduce the number of tabs even further, with a home tab and a library tab? On the library tab we could have a grid with the different categories.

Genre mixes should be possible, at least there's a way to add a genre to a mix on the phone 🤔 But maybe that just adds all individual albums, not sure.

Can we change the sorting within Android Auto? If something like "Recently Added" is possible, then it should be possible to use the BaseItemDto's SortTitle too.

I'll take a look at the modifications to the queue service. just_audio is really opinionated and the layered architecture doesn't make things easier. I've struggled with it for many monhs 🙃

Edit: Genre instant mixes should be a thing, at least it works in the Jellyfin app. No idea why it's hidden in Finamp...

Chaphasilor · 2024-01-21T16:32:09Z

@puff I managed to fix up the queue based on your proposed changes. There were a few other things I needed to adjust, and I fixed a bug that I introduced a while ago (items in next up were not being reported to the external/OS queue).
From my testing everything seems to work as it should, but please let me know if anything is off!
With the beta release approaching fast I would hate to break things, and there have been the strangest bugs with playback and queue management in the past...

…itive

puff · 2024-01-22T20:02:39Z

We could reduce the number of tabs even further, with a home tab and a library tab?

Yeah, I like that idea.

Genre mixes should be possible

I didn't see a way already implemented in Finamp yet, but yeah it should be possible if the Jellyfin app has it.

Can we change the sorting within Android Auto?

Yes, we can sort the MediaItem list before returning from getChildren. While testing, I noticed the offline sort already used doesn't match output from the Jellyfin api when sorting names.

finamp/lib/components/MusicScreen/music_screen_tab_view.dart

Line 327 in 4463bff

offlineSortedItems!.sort((a, b) {

Looks to be because the Jellyfin api is case-insensitive:
https://github.com/jellyfin/jellyfin/blob/7027bc00fc06314929011735e425763779cb4076/MediaBrowser.Controller/Entities/BaseItem.cs#L897

I've fixed it and added sort to Android Auto. It uses whatever sort option is selected in the phone app.
Before & After:

Chaphasilor · 2024-01-23T07:00:44Z

Thanks for fixing that. There are some sorting-related issues that need to be tackled at some point anyway, like #444 or #581, so if you feel like taking a look while you're dealing with sorting anyway, that would be much appreciated.
Otherwise I'll try to fix it after some bigger issues have been fixed...

puff · 2024-01-23T08:13:19Z

I managed to get artwork to work with offline items and (kind've) Android Automotive using the android_content_provider package.

The white icon in the middle is the placeholder art.

Only problem is that for Android Automotive, we can't use http(s) URIs. Because of this, we have to resolve them ourselves. My current implementation hangs until every item has a resolved image. I think the way to fix this is to offload it to the ContentProvider. For now, I've commented it out until I have a better solution.

Chaphasilor · 2024-01-31T10:11:03Z

Did you manage to take a look at the voice command stuff? Or is there anything that you need help with? :)

puff · 2024-02-01T03:02:23Z

Did you manage to take a look at the voice command stuff? Or is there anything that you need help with? :)

I've been having some trouble with it. It doesn't default to finamp even when it's open (maybe I forgot to configure something though?). It really doesn't like to recognize the app's name, you have to say it slowly. Saying "album" or really anything else other than the name of the song/album makes it default to YouTube Music (probably your default music service) so extras is always null.

"play some music on finamp"

Seems like some generic phrases are stripped out, odd that the "on finamp" part wasn't though.

"play black ray on finamp"

If you want to try it out, you just need to add this to the manifest:

<intent-filter>
  <action android:name="android.media.action.MEDIA_PLAY_FROM_SEARCH" />
  <category android:name="android.intent.category.DEFAULT" />
</intent-filter>

and uncomment playFromSearch in music_player_background_task.dart

Chaphasilor · 2024-02-02T23:46:35Z

Sorry for not responding earlier, I was a bit busy. Just tested it out and didn't manage to invoke the playFromSearch() method even once, although I did manage to get it to recognize the app's name a few times. I did manage to open the app by saying "Play some music on Finamp", but I don't think that's related to the manifest changes.
If the problem would just be to properly recognize the app name, then this might help, if it still works. But I think the whole voice command stuff seems to be pretty flawed, with YouTube being the default for a lot of things even after explicitly not selecting a default in the Assistant settings.
I only tested with Google Assistant, not with Android Auto, but I'd expect results to stay the same.

I guess we should skip this feature for now, including regular search. Search is due for a rewrite soon, and it makes little sense to integrate the old version now...

Chaphasilor · 2024-05-26T20:21:27Z

Nothing in the logs sadly. Only logs I get are Getting children of <xyz> and Couldn't get offline image [...] (for the ones that don't have an image, where the placeholder is correctly being applied).

Here's what it looks like:

I can try testing it with an actual car in the coming days, maybe even tomorrow.

Komodo5197 · 2024-05-26T23:22:42Z

lib/services/queue_service.dart

+
+    // replace with content uri or jellyfin api uri
+    if (downloadedImage != null) {
+      artUri = downloadedImage.file?.uri.replace(scheme: "content", host: "com.unicornsonlsd.finamp");


Will all these content URIs work on iOS? Android seems to have a custom handler we've written.

Good catch, should probably have a platform check here.

Komodo5197 · 2024-05-26T23:24:27Z

lib/components/MusicScreen/music_screen_tab_view.dart

@@ -57,6 +57,7 @@ class _MusicScreenTabViewState extends State<MusicScreenTabView>

  final _jellyfinApiHelper = GetIt.instance<JellyfinApiHelper>();
  final _isarDownloader = GetIt.instance<DownloadsService>();
+  final _finampUserHelper = GetIt.instance<FinampUserHelper>();


Is this line used?

Not anymore, at least according to the linter ^^

Komodo5197 · 2024-05-26T23:26:53Z

lib/components/PlayerScreen/queue_list.dart

@@ -1263,3 +1264,41 @@ class PreviousTracksSectionHeader extends SliverPersistentHeaderDelegate {
  @override
  bool shouldRebuild(SliverPersistentHeaderDelegate oldDelegate) => false;
 }
+
+class QueueTracksMask extends SingleChildRenderObjectWidget {


This should be removed.

Komodo5197 · 2024-05-26T23:27:41Z

lib/main.dart

@@ -111,6 +112,21 @@ void main() async {
        : "en_US";
    await initializeDateFormatting(localeString, null);

+    // Load the album image from assets and save it to the documents directory for use in Android Auto
+    final documentsDirectory = await getApplicationDocumentsDirectory();


Don't put this in documents. Put it in application support. Also, this whole block should probably be in one of the submethods where we've still got the errorApp wrapper.

Komodo5197 · 2024-05-26T23:32:41Z

lib/main.dart

@@ -111,6 +112,21 @@ void main() async {
        : "en_US";
    await initializeDateFormatting(localeString, null);

+    // Load the album image from assets and save it to the documents directory for use in Android Auto
+    final documentsDirectory = await getApplicationDocumentsDirectory();
+    final albumImageFile = File('${documentsDirectory.absolute.path}/images/album_white.png');


I don't think constructing files from full pathstrings is considered good practice? I'm not sure how much that matters though.

/images/album_white.png could be moved to a constant. Not really sure what else to do here.

I basically mean using the path_helper to combine the segments. Like I said, I'm not sure how much it matters though.

lib/services/music_player_background_task.dart

Komodo5197 · 2024-05-27T00:33:31Z

lib/services/music_player_background_task.dart

+
+  // triggers when skipping to specific item in android auto queue
+  @override
+  Future<void> skipToQueueItem(int index) async {


Can't we just rename skipToIndex to match the override?

I think skipToIndex() is clearer, and it doesn't really hurt to do it this way?

I guess not? It's pretty strange to have this pointless redirection though.

I actually don't think so. There are some weird external methods that the OS can decide to call, but unifying this into a more sensible API seems like a good idea to me.
Basically, all we're doing is say "if Android Auto decides it needs to skip to a specific queue item, that just means we skip to the provided index, just like we do in some other cases". That redirection is basically some documentation/explanation saying that the two actions are equivalent, without there being any confusion...

lib/services/music_player_background_task.dart

lib/services/android_auto_helper.dart

Komodo5197 · 2024-05-27T00:56:53Z

lib/services/android_auto_helper.dart

+        || tabContentType == TabContentType.artists || tabContentType == TabContentType.songs;
+  }
+
+  Future<MediaItem> _convertToMediaItem({


This should probably be unified with the method in queueService. Maybe the id string and playable bool should be optional parameters for that? Alternatively, it looks like this is only used for menu items, so maybe you just unify the art URI fetching and then cut this version down?

Chaphasilor · 2024-05-27T08:07:21Z

Thanks for the review Komodo! The age of this PR is starting to show...

I'll try to go through your comments later and improve the sections as best as I can :)

Chaphasilor · 2024-05-27T19:14:22Z

Also before I forget, the way Symfonium handles playing in-order vs. shuffled is by making each "leaf" item a node/collection, which has two children, "Play in order" and "Play shuffled". I think that would also be a good solution for us, and we could even add more choices, like starting and instant mix or adding to Next Up.

lib/services/android_auto_helper.dart

Chaphasilor · 2024-05-27T20:39:58Z

Okay, aside from breaking the whole Android Auto media browser, the review findings should be handled now 😅
I'll try to figure out what exactly broke tomorrow...

Chaphasilor · 2024-05-27T21:01:23Z

There we go. Managed to fix it today :D

Chaphasilor · 2024-05-30T18:37:00Z

Okay, the enhanced search is also working now. I'd like to get a like button onto the AA player screen / media notification because it's been a long-requested feature, and then this should be ready to merge

Chaphasilor · 2024-05-30T18:42:43Z

Also before I forget, the way Symfonium handles playing in-order vs. shuffled is by making each "leaf" item a node/collection, which has two children, "Play in order" and "Play shuffled". I think that would also be a good solution for us, and we could even add more choices, like starting and instant mix or adding to Next Up.

Custom browse actions (https://developer.android.com/training/cars/media#custom_browse_actions) would be a much better solution though...

…ng media notification

Chaphasilor · 2024-05-30T22:27:50Z

This should be ready to merge now. All the basics are working reasonably well. If someone could confirm that this still works fine on iOS that would also be nice :)

Chaphasilor · 2024-06-02T16:06:20Z

Okay, I'll merge this in now for the next update, since most things should be working fine. If not, we won't know without having users test it anyway.
Enhancements and new features can come at a later point, based on user feedback.

Chaphasilor · 2024-06-02T16:08:01Z

Thank you for getting this started looking into the documentation, etc. @puff!

Chaphasilor · 2024-06-07T16:34:26Z

@puff do you have a working Automotive setup? I'm low on disk space, but it seem like we need screenshots from Automotive for our Play Store listing to pass the review.

If you could grab some screenshots in landscape and portrait mode using the official demo server, that would be great!

frandj99 · 2024-10-24T19:01:57Z

Hey guys, any update on this?
I'm really hoping to see a Jellifin client workin on Android Automotive and I just found this discussion.
May I ask if there's hope to see Finamp on car's Play Store soon ? 😅
This would be a game-changer for me (and I think also for other AAOS users)

Titaniumtown · 2024-10-24T21:15:55Z

@frandj99 this was merged 5 months ago and is in the redesign branch. You can install the beta using the instructions in the README.md.

Chaphasilor · 2024-10-25T05:40:53Z

@frandj99 while this has indeed been merged into the beta for some time, I'm not sure if it actually works with Android Automotive. Please try it out and let us know!

frandj99 · 2024-11-17T19:10:00Z

@Titaniumtown @Chaphasilor I was finally able to build the app (also I had to go through a private test on Google Play Console in order to install on my car, cuz sideloading is not allowed 🥲)
I have some bad news so... I feel a login screen is missing. If I open the app I only get a message with "Loading contents..." as in this photo (sorry, it's in Italian)

I'm down to test anything, let me know if I'm missing something or so...

Chaphasilor · 2024-11-17T19:56:27Z

@frandj99 is that Android Automotive? Does it install the app directly onto the car? 🤔

frandj99 · 2024-11-17T20:28:35Z

@frandj99 is that Android Automotive? Does it install the app directly onto the car? 🤔

Yes, it's Android Automotive of my Volvo XC40.
Let's say that installing any app I want is not easy 😅
Basically Android Automotive has its own Play Store application section, so I can download just a small number of apps approved for cars.

Sideloading is not allowed at all, I can't access the developer setting on Volvo AAOS "for security reasons", so the only way you can install any application is through the Play Store.
So what have I done? I paid Google for app publishing (even if I won't really do this), compiled the app with a different package name, added the string so I can use it while driving, create the signed app bundle and finally do the closed beta test with myself only, in order to see the app on my Play Store.

Yeah, looong and boring way, I needed some help by a friend of mine to compile the app in Android studio but finally today I was able to see the Finamp icon on my car 😄 (but it doesn't work)

puff added 3 commits January 16, 2024 19:38

Move _includeItemTypes() to TabContentType

6a2238d

Basic Android Auto support

8da2b09

Try using downloaded parent before going online in Android Auto

d168fb7

puff added 2 commits January 18, 2024 16:20

Add shuffle to Android Auto

f877624

Use correct shuffle status for Android Auto

56d4f2a

Artists now start instant mix in Android Auto

05e5f72

synchronize internal queue and Android media queue

efb14bd

Chaphasilor and others added 3 commits January 21, 2024 18:45

fix adding to next up when shuffle is active

0789c31

Add sorting to Android Auto and make offline sort by name case-insens…

7a24508

…itive

Remove unused parameter in Android Auto getBaseItems

aad1edf

Only sort downloaded items if not playing them in Android Auto

99d01f2

Use a ContentProvider to resolve artwork for Android Auto

b3656c8

Chaphasilor added 2 commits May 26, 2024 22:26

explicitly handle request for recent ("For you") root

895fe77

fix syntax error

289f3b2

Komodo5197 reviewed May 27, 2024

View reviewed changes

lib/services/android_auto_helper.dart Outdated Show resolved Hide resolved

Chaphasilor added 2 commits May 27, 2024 22:20

improvements based on review

adf2a81

fix errors, properly join file paths

6d12f78

Chaphasilor added 2 commits May 27, 2024 22:59

fix issues with content provider custom artwork URIs

03470f9

fix album name always being shown

ddc66e8

search multiple item types

4274089

Chaphasilor added 2 commits May 31, 2024 00:24

added like button to media notification, added settings for customizi…

68d3b3d

…ng media notification

Merge branch 'redesign' into pr/puff/578

1901816

Merge branch 'redesign' into pr/puff/578

ae315fb

Chaphasilor merged commit c68cdf0 into jmshrv:redesign Jun 2, 2024
4 checks passed

Android Auto #578

Android Auto #578

Conversation

puff commented Jan 17, 2024 • edited Loading

Features:

Future features/TODO?

// dev notes

jmshrv commented Jan 18, 2024

puff commented Jan 18, 2024 • edited Loading

Chaphasilor commented Jan 18, 2024

puff commented Jan 18, 2024 • edited Loading

Chaphasilor commented Jan 18, 2024

puff commented Jan 18, 2024 • edited Loading

Chaphasilor commented Jan 18, 2024 • edited Loading

puff commented Jan 19, 2024 • edited Loading

Chaphasilor commented Jan 19, 2024 • edited Loading

puff commented Jan 20, 2024 • edited Loading

Chaphasilor commented Jan 21, 2024 • edited Loading

Chaphasilor commented Jan 21, 2024 • edited Loading

puff commented Jan 22, 2024 • edited Loading

Chaphasilor commented Jan 23, 2024

puff commented Jan 23, 2024 • edited Loading

Chaphasilor commented Jan 31, 2024

puff commented Feb 1, 2024

Chaphasilor commented Feb 2, 2024

Chaphasilor commented May 26, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Chaphasilor commented May 27, 2024

Chaphasilor commented May 27, 2024 • edited Loading

Chaphasilor commented May 27, 2024

Chaphasilor commented May 27, 2024

Chaphasilor commented May 30, 2024

Chaphasilor commented May 30, 2024

Chaphasilor commented May 30, 2024

Chaphasilor commented Jun 2, 2024

Chaphasilor commented Jun 2, 2024

Chaphasilor commented Jun 7, 2024

frandj99 commented Oct 24, 2024

Titaniumtown commented Oct 24, 2024

Chaphasilor commented Oct 25, 2024

frandj99 commented Nov 17, 2024

Chaphasilor commented Nov 17, 2024

frandj99 commented Nov 17, 2024

puff commented Jan 17, 2024 •

edited

Loading

puff commented Jan 18, 2024 •

edited

Loading

puff commented Jan 18, 2024 •

edited

Loading

puff commented Jan 18, 2024 •

edited

Loading

Chaphasilor commented Jan 18, 2024 •

edited

Loading

puff commented Jan 19, 2024 •

edited

Loading

Chaphasilor commented Jan 19, 2024 •

edited

Loading

puff commented Jan 20, 2024 •

edited

Loading

Chaphasilor commented Jan 21, 2024 •

edited

Loading

Chaphasilor commented Jan 21, 2024 •

edited

Loading

puff commented Jan 22, 2024 •

edited

Loading

puff commented Jan 23, 2024 •

edited

Loading

Chaphasilor commented May 27, 2024 •

edited

Loading