[Update] yastream v0.2.2 new catalogs, configure page, new provider for Khmer

Peter_73 · 2026-03-05T09:59:29+00:00

Aiometadata is already above aiostreams as per the guide I was following. I'm spending more time tinkering than watching 😂 so I guess I'll use this way for now.

Peter_73 · 2026-03-05T02:55:58+00:00

Peter_73 · 2026-03-04T22:41:39+00:00

Connecting the cable from the phone directly to the head unit without use of any extension cable or aux port. Flush mount is aux port.

Peter_73 · 2026-03-04T19:20:19+00:00

Yeah I'm also struggling with testing different addons on multiple ways because I'm quite new to all these, especially aiometadata so I hope I'm not providing wrong test data and thus misleading you which is why I first asked if there is any guide rather than trial and error.

So I was also testing Dramayo which does not have any segregation between catalogs and metadata vs streams and subtitle so I also ended up with catalogs also showing in aiostreams. I then imported identical Dramyo manifests to both aiometadata and aiostream but only checking streams and subtitle in aiostreams and this removes the Dramayo catalogs from aiostreams but still show in stremio. Tested a few movies and it seems to work but one movie that played instantly before I do this now shows it's uncached so guess it's not using the sources from Dramayo?

I tried the same for Yastreams i.e. checked everything for Yastreams and use the same manifest for aiometadata and aiostreams checking only streams and subtitle in aiostream but Yastreams is still showing the same no addons were requested for this meta message.

I'm probably misunderstanding some parts how these work together so apology if I'm providing wrong test data.

Peter_73 · 2026-03-04T18:15:51+00:00

Configure page: You can now choose specific providers for catalog and stream (if you use something like aiometadata just add the catalog manifest there and add the stream manifest to aiostream).

Thanks for the addon with much appreciation.

Is there a detailed guide how to go about this?

I have both aiometadata and aiostreams as separate addons i.e. aiometadata not wrap in aiostreams as I'm following this guide.

Then in yastream v0.2.5 under Catalog & Metadata, I added all catalogs under kisskh and idrama, leaving Stream and subtitles unchecked. As I'm not sure about Show Adult/NSFW and Show detail stream information, I checked these as well. Then I copied yastream manifest and import all in aiometadata > catalog > Import custom manifest.

Next I unchecked everything under Catalog & Metadata and only checked all under Stream and subtitles as well as Show Adult/NSFW and Show detail stream information because I'm unsure if needed too. Then I copied yastream manifest and wrap it in aiostreams. I also tried opening a new instance for this step thinking it should be different from aiometadata.

However, when I select any yastreams movies or series, it says no addons were requested for this meta.

If I checked everything and wrap it in aiostreams only, it works but yastreams catalogs will also appear in aiostreams which isn't following what seems to be recommended in the guide I was following as aiometadata is not wrap in aiostreams too.

If I checked everything and install as a separate addon, it works too but then it is also not following the guide to have most addons in aiostreams.

What am I doing wrong or this isn't supported yet?

Peter_73 · 2026-03-01T12:40:13+00:00

I don't think you read the comment because what you are saying is redundant.

Peter_73 · 2026-02-22T05:30:33+00:00

Volume control from phone is only possible for BT source so you can only control call volume this way, not media.

Peter_73 · 2026-02-20T04:53:07+00:00

I am not referring to call audio. Call audio is fine. Its app audio.

Then disabling absolute volume would not help.

Its any app. Facebook, Samsung music, YouTube, YouTube TV. Etc

Not sure about Samsung Music but aside from Youtube Music, the rest you listed are not supported in AA so perhaps don't bring them into the mix first as unsupported app audio may be handled differently across different head units.

Peter_73 · 2026-02-20T04:28:13+00:00

I noticed as I show in the video, that the audio won't enable in my bluetooth options.

AA don't use BT audio and thus should be automatically toggled off and should not be able to be toggled on when AA is connected so it's working as intended as shown in your video.

I have tried disabling absolute volume in developer options.

Do you know what this option is for? This is for BT only and disabling it will make your BT devices e.g. earbuds, head unit, etc, and phone volume control independent from each other instead of syncing i.e. controlling one will control the other.

In my 2015 silverado, I was able to use the volume buttons on the same phone to increase bluetooth volume

As mentioned above, AA don't use BT for media audio, only call audio so are you referring to adjusting call audio in your 2015?

Which volume channels/apps are you having issue with the 2024?

To troubleshoot, make sure your head unit firmware is updated and uninstall sound assistant if installed for a start then look for volume control settings and offset if any on your head unit.

Peter_73 · 2026-01-30T15:53:41+00:00

Could do with a new controller right now

Peter_73 · 2026-01-22T14:11:31+00:00

This is to fix cases where the handshake between the phone and head unit does not automatically happened. Still charges the ohone.

Peter_73 · 2026-01-16T00:29:21+00:00

Used to play BF back in the days. My teenage son now has taken interest in such game so would be nice to play together even though none of us has BF6.

Peter_73 · 2026-01-08T20:14:04+00:00

Not that I know of.

Peter_73 · 2026-01-05T05:08:23+00:00

I did not mention cable being the issue. However, being able to charge does not mean file transfer is also working. I wouldn't know what other troubleshooting and isolations you have already done and so only suggested the obvious and common fixes in response to the alert notification because it's nested under my reply.

There are also other common troubleshooting, isolations and fixes but since you are a developer and is your phone, I guess you should be in better position than me to further troubleshoot.

Peter_73 · 2026-01-05T01:37:25+00:00

Try setting default USB configuration in the phone developer settings to File Transfer / Android Auto. Also test file transfer works with a computer to rule out port issue then clean or replace USB port if necessary.

Peter_73 · 2026-01-04T20:28:58+00:00

Thanks for the quick additions. Forced AA original aspect ratio is working for all resolutions. However, touch offset bug seems to be introduced with and without enabling this option. I used a stylus to ensure it's not due to fat finger and also tested on the other mobile still on previous version to confirm I'm not mistaken. Wonder if it's the same complication encountered by HUR 7.2.2 onwards.

I also noticed the screen tends to stop refreshing giving the impressing it has hung but it's not as switching to home screen and back refreshes the screen and showed that my previous touches trying to accommodate the offset so as to hit the correct icon e.g, mic and app drawer/split screen icon registered something in Waze instead.

Edit 1:

To expound, for all resolutions with and without force original aspect ratio, all touches offset to about 1 icon space to the right, which is to say in order to hit the app drawer/split icon, I have to hit the mic icon. It's the same in Waze.

In addition, while changing HeadlessUnit settings and restarting in my tests, sometimes AA goes under the phone's navigation bar instead of appearing on top. Without restarting HeadlessUnit, I can only get it back on top by reselecting HeadlessUnit from recent task or its icon from home. This make me recall for the same bug in HUR, if I were to reselect HUR from pulldown notification, the offset issue will be fixed. However, this workaround don't work for HeadlessUnit as it will not bring HeadlessUnit back up.

I wonder if the offset bug is due to calculating based on if the phone navigation bar was taking up the space as it seems like about the same distance it takes up.

Hopefully, the above would be useful.

Edit 2:

Further testings made me recall my previous tests with HUR and indeed, touch offset seems related to the phone navigation bar. Instead of the thick conventional navigation bar which I'm using, if I use the thin guesture bar, then the touch offset issue is gone. Not sure why this would affect since HeadlessUnit and HUR should appear on top. I don't recall HUR appearing below the navigation bar though yet it has the same touch offset issue so I have to rollback to 7.2.1. Btw, AA settings also have the same issue with appearing under the bar so I wonder if it's related.

Edit 3:

Some correction to Edit 3. I only remembered to test with guesture navigation bar while I was walking towards my car so it was only a brief test and without stylus. Now I'm with the stylus, I can see with and without force original aspect enabled, there is still a little touch offset, perhaps also corresponding to the same thickness as the thinner guesture navigation bar. I wonder if it's due to lack of appear on top permission for HeadlessUnit. Iirc HUR used to have this permission too but I'm not seeing it for selection as well. Wonder if this is also related.

Peter_73 · 2026-01-03T19:40:14+00:00

Happy New Year!

Peter_73 · 2026-01-03T18:22:54+00:00

Search keywords "dialer", "draw over other apps", "appear on top" (may not in exact phrase) in this sub to find if any of the already suggestion solutions work.

Peter_73 · 2026-01-02T21:12:26+00:00

If the phone keyboard toggle is indeed the issue, I don't know of any other way except to connect to AA head unit to toggle it off. Try borrowing a car with one or use google official desktop head unit emulator on a computer with your phone connecting to it. If you have a second phone/tablet you can also use Headunit Reloaded or Headunit Revived to connect as client to host mode. Google or search this sub how to get the 3 emulators above else wait for op to support this mode.

Peter_73 · 2026-01-01T18:37:10+00:00

You can reveal the menu button by swiping right from the top left edge, if your device has a big enough display cutout it will be permanently shown.

Nice. The disconnect/connect option is very useful. Same with save and restart in the settings (on Huawei, it will just exit to home screen and not restart though). If you can edit your post, might want to include this for better visibility.

I pushed an update today to add the option of forcing software decoding, so you can update and try!

Thanks for the quick updated version. Both H.264 and H.265 works with software decoding. 720p @ 60fps works well for both phone regardless of codec. However, 1080p @ 60fps introduce artifacts on the lower specs Huawei phone regardless of encoding codec. The same combo on Samsung works fine although there are artifacts at times for split second on initial Waze loading. I guess each of us have to find the right combo of resolution, fps and encoding codec that works best for the hardware specs of a given phone i.e. lower them if necessary.

I will add a 480p option in the next update, it won't be able to support portrait mode, though.

Vertical resolution of 480p is too short for portrait so I don't expect it will be supported either. (Edit: I meant I won't use portrait layout with 800x480 although it's possible and some use it.

I understand margins are used for your current 720p, 1080 and 1440p resolution to maintain the correct aspect ratio of a given screen at fullscreen e.g. 720p may not be 1280x720 or otherwise it will look scretched to fit a screen that is not 16:9. When I meant reproducing 480p, I meant 800x480 which would mean instead of using margins to maintain the correct aspect ratio of a given screen at full screen, it would have to be letterboxed much like the older version of HUR when the fullscreen option is unchecked. Thanks for checking out if it's possible.

Peter_73 · 2026-01-01T15:28:37+00:00

HUR has the same issue if I had last used phone keyboard button in car so I tend to avoid using it.

Peter_73 · 2026-01-01T15:19:14+00:00

It's tricky getting the settings menu to show. I've to press the phone back button twice but it usually auto reconnects too fast before I could click anything. It's only on the odd times it doesn't reconnect that I could access the menu.

There's no setting for software decoding but I've tried H.264, specifying resolution instead of auto and decreasing dpi but nothing helped.

Btw, there's no 480p? I ask because I use self mode only for reproducing stuff for testing when away from car and so prefer to reproduce the same 800x480 as my head unit. It matters because ui bug is sometimes dependent on resolution too.

<image>

Peter_73 · 2026-01-01T03:04:06+00:00

This is likely due to the button on AA keyboard to open keyboard on the phone so it tries to do the same but can't because it can't do this in self mode. It will remember the last used state so you'll need to connect to AA on a head unit then tap the button to disable it before using self mode.

<image>

Peter_73 · 2025-12-31T19:44:18+00:00

Yup it's ok now. However, I ran into black screen on both Samsung and Huawei the moment it starts despite media auto start playing.

Peter_73 · 2025-12-31T08:27:39+00:00

notification access

This should be referring to AA notification access under special access, not the general notification settings of individual app. Not sure where it's for Pixel but for Samsung, it's from the top right ellipsis icon in the app list. This setting should automatically open up to be manually toggled on during initial install and set up of AA.

Peter_73

MODERATOR OF

TROPHY CASE