Conversation
Hi, thanks for trying to help, I was on Android 14 back then and now on 15, the provided patch is working on both Android version for Twitter 10.63 (Sorry but I don't really update modded apks unless something breaks so I couldn't verify if the same applies to newer updates) edit: @kitadai31 btw if you want I can share my apk so you can easily test it |
|
Oh, really? Hmm...
Thank you 🙏 |
|
These patches are much appreciated. Thank you
let's just keep them. |
|
@kitadai31 since we're here, can you also send me your patched APK to check if the smali instructions were patched properly? Edit: Just for the record, I had my APK sent to @kitadai31 via Telegram earlier |
|
@dic1911 I tried your manually modified 10.63.1 apk, but the app chooser still don't open. However, just only once, when I tapped on an external link on a profile page, the app chooser appeared, but it said "There is no app for this action." OK, I'll send my patched apk tomorrow |
@kitadai31 This sound like what would happen when you have default browser set, can you try to freeze the browser which it opens automatically when you tap on links? |
It works! I thought that patch allows us to choose browser every time even if the default browser is set. |
|
But, if the default browser is not set, the stock Twitter also opens a normal intent chooser. This dialog is a little different from the app chooser in that it has an "Always" button, but I think it is almost same. (to be honest) |
It's just how Android works, AFAIK when a default browser is set and you want to open the link with a chooser for something else, you need to iterate through apps to check what apps can open the link and make UI yourself |
|
@dic1911 How about this? #540 (comment) It is possible that the behavior of the Twitter app has changed in recent versions after you contributed the browser chooser patch. But if you think that patch is still useful, of course I'll drop the commit d654ba4 and fix the patch instead. |
|
@kitadai31 Since I don't really know when it's changed, maybe just leave the patch there and add a note so people would know it should only be applied on older versions? |
↑ To see if it is correct, I just tried Twitter 10.23.0.
Based on the above result, I don't think that's necessary. @dic1911
|
|
@kitadai31 I'd ask @crimera for opinion instead since I don't really own piko ;) |
…ng instead of throwing an exception when failed
… to ReVanced Patcher v21
… to "related" "Tweet Detail Related Tweets" was mistakenly abbreviated to "Detailed". "Related" is more accurate word to describe "Discover more" section. However, the name of the patch is not changed in this commit. Because renaming the patch name might affect in manager/builder that's use this patch name. Variable names and string keys are also not changed as per the patch name.
The last working version was 10.48.0. Moreover, it is possible on the stock Twitter.
9046295 to
be7aa54
Compare
Fair enough. I re-pushed the PR branch with some updates:
@crimera Ready for review! |


Hi 👋
I made some improvements of piko patches.
This pull request contains 6 commits.
Integrations: crimera/revanced-integrations#121
1. fix(Bring back twitter): Resource compilation fails on ReVanced Manager
I also simplified some constants of this patch.
2. fix(Enable Reader Mode): Specify the compatible version, show a warning instead of throwing an exception when failed
Compatible version is useful for users who want to use reader mode.
Also, if the patch has failed, show a warning instead of showing a wall of the stack trace.
WARNING: "Enable Reader Mode" is not supported in this version. Use X 10.72.2 or earlier. The patch was not executed.Screenshot
[ADDED]: This change add a notice of compatible version only to the patch description. Because if I add a target version to the patch, Manager will no longer show "Any" for suggested version.
3. docs: Add compatible CLI and Manager versions to README until bumping to ReVanced Patcher v21
This is absolutely necessary!
4. fix(Remove Detailed posts): Change the settings label from "detailed" to "related"
"Tweet Detail Related Tweets" was mistakenly abbreviated to "Detailed".
"Related" is more accurate word to describe "Discover more" section.
Note: The name of the patch is not changed in this commit.
Because renaming the patch name might affect in manager/builder that's use this patch name.
Variable names and string keys are also not changed as per the patch name.
Only the setting label has been changed.
I also fixed a typo "Revist" as well.
5. fix: Remove non-functional
Open browser chooser on opening linkspatchThe last working version of this patch was
10.48.0-release.0.So, I tried updating this patch according to #442.
Then, I fixed the patch and I checked that the integrations method (
openWithChooser) is called correctly when I open any links. (Checked with logs)However, the app chooser still doesn't open.
It seems that
Intent.createChooser()has no effect.Tested on Pixel 3, Android 14 (LineageOS 21).
3 browsers are installed: Chrome, Firefox and Via.
So I think this patch is not working and should be removed.
I also tested the link which has an external app.
For example, I installed Pixiv app on my phone, so when I opened a Pixiv link on patched Twitter, the app chooser should be opened and show "Chrome or Firefox or Via or Pixiv?" choices.
But it opens the Pixiv app directly. App chooser wasn't opened.
For reference, these are the patch source I used.
https://github.com/kitadai31/piko/blob/5d1e295c41f9b98299e1de820bd7d7ba5d90de7a/src/main/kotlin/crimera/patches/twitter/link/browserchooser/BrowserChooserPatch.kt
https://github.com/kitadai31/piko/blob/5d1e295c41f9b98299e1de820bd7d7ba5d90de7a/src/main/kotlin/crimera/patches/twitter/link/browserchooser/fingerprints/OpenLinkFingerprint.kt
6. feat(Settings): Add a description to "Native features" page
The usage of native features were unclear.
This helps users find the native features.
Screenshot
I have one question for this commit.
I changed "detailed" to "related" only for English strings.
I checked with Google Translate and found that it is still translated as "detailed post" in some other languages.
Should I delete the changed string from all languages?
Or shouldn't?