search

ftde0 / yt2009

2009 youtube frontend.
Apache License 2.0
193 stars 119 forks source link

(Updates) Status on YT2009 compatibility with 1.x YouTube APKs #77

Closed mrkrabs206 closed 7 months ago

mrkrabs206 commented 7 months ago

Here, this is an open updates page for status.

Since I'm tired of waiting (and probably you), I have decided to make this for everyone.

Hopefully we can make 1.x apps supported with YT2009 in the near future someday (ftde0 said).

Last week: no response

Stay tuned for updates!

ftde0 commented 7 months ago

i did release an update 3 days ago that addresses some of 1.x issues. https://github.com/ftde0/yt2009/commit/f955cc7d4369a3ad5d46b27044d36b455b442fc2

if you're still experiencing issues with 1.6.21, make sure you've set shouldUseMasf to false. you can find where shouldUseMasf is by opening a 1.6.20(E) APK in jadx as this one doesn't have obfuscated variable names, unlike 1.6.21. apply the required change for your 1.6.21 decompile.

mrkrabs206 commented 7 months ago

i did release an update 3 days ago that addresses some of 1.x issues. f955cc7

if you're still experiencing issues with 1.6.21, make sure you've set shouldUseMasf to false. you can find where shouldUseMasf is by opening a 1.6.20(E) APK in jadx as this one doesn't have obfuscated variable names, unlike 1.6.21. apply the required change for your 1.6.21 decompile.

Okk

mrkrabs206 commented 7 months ago

i did release an update 3 days ago that addresses some of 1.x issues. f955cc7

if you're still experiencing issues with 1.6.21, make sure you've set shouldUseMasf to false. you can find where shouldUseMasf is by opening a 1.6.20(E) APK in jadx as this one doesn't have obfuscated variable names, unlike 1.6.21. apply the required change for your 1.6.21 decompile.

There isn't a shouldusemasf in 1.6.21

ftde0 commented 7 months ago

yes, as variable and class names in 1.6.21 are obfuscated. i referenced 1.6.20(E) as its variable and class names aren't obfuscated (and have a shouldUseMasf but the versions themselves don't work on modern android). once you find where shouldUseMasf would be in 1.6.21 (using 1.6.20(E)) you can set it to false.

mrkrabs206 commented 7 months ago

yes, as variable and class names in 1.6.21 are obfuscated. i referenced 1.6.20(E) as its variable and class names aren't obfuscated (and have a shouldUseMasf but the versions themselves don't work on modern android). once you find where shouldUseMasf would be in 1.6.21 (using 1.6.20(E)) you can set it to false.

thank you

mrkrabs206 commented 7 months ago

@ftde0 https://github.com/ftde0/yt2009/issues/78