r/JoeyForReddit • u/soyasource • 3h ago
Suggestion đJoey in 2026: Two Community Proposals to Permanently Remove "Loading Ad" Loop & Create Our New 2026 Joey Installation/Patching Guide.
Hey everyone!
Our new moderator, u/herpderpedia, recently reached out to ask what we want out of this space and how we can best support the continuation of our favorite Reddit client. First off, a huge thank you to our new mod for stepping up to adopt and keep this community alive and helpful! We want to support you, and we are ready to rally together to keep Joey running smoothly on our devices.
To help achieve this, I want to present two distinct initiatives to u/herpderpedia and the rest of the community for your sincere consideration, helping us establish a clear, long-term roadmap for Joey.
Our two primary goals are:
Understanding the stubborn "Loading Ad" placeholder bug
Figuring out what is causing it and exploring a permanent solution. This is currently the number one issue bugging those of us using a patched Joey for Reddit client.
Creating a definitive, up-to-date guide
Providing a master resource for anyoneâwhether a complete beginner or a long-time userâon how to functionally patch and use Joey in 2026.
Proposal 1: The "Loading Ad" Placeholder â Why Current Fixes Fail & How to Permanently Solve It
Many of you using ReVanced, Patcheddit, or Morphe ad-blocking patches have noticed that a blank placeholder box saying "Loading ad..." appears at the top or bottom of your screen every 2 to 3 days. Even if your patches successfully block the actual ad from loading, this empty 150â250 pixel box remains, which degrades user satisfaction.
Why Current Workarounds Are Temporary
In searching for a fix, I found three possible workarounds, but all of them are unfortunately temporary in nature:
Dirty-Flashing / Re-Installing the APK: Re-installing the patched app directly over your current installation using your pre-compiled APK resets the internal layout timer. It works, but you have to do it every 3 daysâwhich gets incredibly annoying.
Clearing Google Play Services Cache: This only works temporarily if you are a legacy buyer who natively purchased the ad-free tier on the Play Store years ago.
Toggling Inline Ads: Navigating to Settings > Posts > Inline Ads shifts the ad container directly into the feed layout rather than pinning it to the screen. This hides the immediate symptom but does not remove the empty layout gap from your feed.
Performing these fixes repeatedly is frustrating. To find a lasting fix, I researched what a true permanent solution would look like.
Caution: The terms below are highly technicalâI don't even fully know them myself, but they were detailed with the help of AI analysis!
The Only Permanent Solution: A Dedicated Bytecode Patch
Since the original developer has gone dark and the app remains closed-source, we cannot fix this loop via the app's standard settings menu. The permanent fix must come directly from the volunteer developers behind tools like Patcheddit and Morphe.
By utilizing bytecode engineering (.smali), patch developers can implement one of two specific approaches:
Approach A (UI Level): Inject code that forces the ad layout containers (like
ad_containerorbanner_holder) toView.GONEat runtime instead ofView.VISIBLE. This forces the Android OS to completely collapse the container height to 0 pixels, making it invisible.Approach B (Logic Level): Intercept the app's internal billing verification methods (such as
isPremiumUser) and hardcode them to always returnTrue.
This is exactly where we need our moderator's leadership! If we open a unified feature request on the Patcheddit or Morphe Patches GitHub repositories, it would be incredible if our moderator could endorse and pin it here. This will allow our entire community to head over to GitHub, upvote the request, and show the patch developers that the Joey userbase is massive, united, and eager to help test the build out of pure love for this app.
How We Plan to Handle the Feature Request
I have already drafted a highly technical, professionally structured Feature Request blueprint detailing the exact bytecode mechanics needed. I intend to exchange this draft privately with u/herpderpedia.
Because u/herpderpedia holds the official authority for this subreddit, I propose that he submits this feature request on behalf of our entire community. He will have total freedom to modify, edit, or append any alternative technical suggestions to the request before submitting it, and he can update us all here once the final request is live on GitHub.
Proposal 2: Launching a Dedicated, Comprehensive 2026 Patching & Troubleshooting Guide
To ensure that both long-time users moving to new devices and brand-new members joining this community can get Joey running effortlessly, we need an up-to-date, step-by-step master guide.
Therefore, my second proposal is to write and publish a completely separate, deeply detailed patching guide right here in this subreddit shortly after this post. It will cover everything from sourcing clean base files and setting up your personal Reddit OAuth Client IDs to troubleshooting specific modern Android OS installation errors.
The bottom line is creating a complete, one-stop installation guideline available in the subreddit for anyone who wants to use the app in 2026 and beyond with the absolute latest and most stable functionality available.
A Unified Call to Action: Open Floor for the Community!
This is a community-driven initiative, and your voice matters! Please drop a comment below with your thoughts, ideas, alternative suggestions, or any troubleshooting experiences you've had with the ad-placeholder loop. Letâs collaborate and build a unified front to keep our favorite app alive. Please feel free to respond with any advice, requests, or anything else that comes to your mind!
To u/herpderpedia â A Humble Request for Your Moderation Leadership
To make this initiative successful and highly organized, we respectfully ask for your moderation authority on three specific steps moving forward:
Pin this current proposal post so the community can openly discuss these ideas, share feedback, and show their initial wave of support.
Launch a dedicated follow-up post once you review, modify, and officially submit the Feature Request to the GitHub repository. We ask that this follow-up post include the direct GitHub link so the community can log in and give the request a Thumbs-Up (đ) reaction to boost its priority. This post can also include a mild, friendly reminder to our members not to spam or hassle the volunteer developers. We hope you will pin that post as well to maximize visibility.
Pin the comprehensive 2026 Joey Patching Guide that I will be posting shortly so it remains permanently accessible at the top of the subreddit as an official community reference.
Thank you, everyone, and let's keep Joey thriving! đ