HTC One M9 Developer Edition Android 5.1 OTA

The Developer Edition of the HTC One M9 is receiving an over-the-air update to Android 5.1. … more

Index Project For XDA Device Subforums

Another ambitious project from the collaborative efforts of Recognized Contributors and Forum … more

The Atlas of XDA

A few weeks ago, we asked you “How Does Your Location Affect Your Life As A Power User?”. In the days that … more

New Snapdragons: Some Context & Contrast

It hasn’t been a good year for Qualcomm so far. Every device featuring the Snapdragon 810 … more

YourTube - Change the default YouTube pane

6,190 posts
Thanks Meter: 8,292
By GermainZ, Forum Moderator / Recognized Developer / XDA Portal Team on 2nd June 2014, 10:40 PM
Post Reply Subscribe to Thread Email Thread
1st July 2015, 08:02 PM |#561  
GermainZ's Avatar
OP Forum Moderator / Recognized Developer / XDA Portal Team
Thanks Meter: 8,292
Originally Posted by sino8r

I like the idea of continuing the module development through another dev but ONLY if GermainZ has actually abandoned it. Has anyone sent him a pm or actually contacted him? I mean he's a well respected member here and don't want to step on his toes...

I just don't bother replying to the same questions after a while. I've said before, more than once, that I'm not getting the time to look into any of my modules. That hasn't changed yet. This happened before (with some of the same users screaming "abandoned" again now), and the module was updated back then once I actually had some time to work on it. That being said, I don't expect them to stop being entitled people suddenly.

If you're interested, feel free to either send a PR or fork the module and start your own, whichever you prefer. I'm perfectly fine with either: that's why my modules are open source. If you'd also like me to add you as a contributor on the Xposed repo, please let me know.

I wrote a script (it's a shell script and isn't the most readable) to find obfuscated methods. It works for most methods (last I checked) but is no longer enough for changing the quality, so you'll have to figure that part on your own. You can find it here. If you can't run it, look for the "grep" lines and let me know if you can't understand it.

A quick tip to figure out which method to hook for changing the quality: hook View.class's onClick method (if memory serves right -- might be onTouch) and figure out which class the video player's quality button belongs to. Then hook all methods in that class, and work your way backwards to see which method is actually responsible for changing the quality. A *lot* of methods will be called for each step, and many of them will require you to look at many other classes or parent methods to finally understand what each does, but this will hopefully help you get started.
The Following 11 Users Say Thank You to GermainZ For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes