[Xposed Framework Modules] kotey:
Ok, I think I'll have some say on this:

- Take a look at MX Player choice of material colours. I think its suffice to please some material girls/boys.

- Or use the idea of 'Chameleon' theme that is adjustable, such as used in Fleksy and Minuum keyboards.

- The whole 'material' fiasco is taking too much toll, I think (not only this app, most other app cases are worse). In v2.9 which I use, it already has enough material feel in it (as the app it is). The whole point of this util is the clipboard, which should be lean, clean, fast and memory efficient. What is the point of designing the "preferences" interface to be material when it is a "setup and forget" thing. I'll do even it has Froyo ugly preferences interface but thats me, I'll choose smooth operation over interface any time of the day.

- Speaking of 2.9, that is why I choose it over 3.0, it does its job for almost a year and I have zero complaint. I don't feel the need for another design upgrade for what's already does its job best. In fact, I refused to update several apps because of this "materialistic" issue, what I can complain to the devs, I already did (xda/gplay/email). How many people have Lollipop now anyway? Maybe I'll reconsider when I get ahold of Zenfone 2, or not.

- Actually there are quite a few apps which upgraded the interface to material without adding anything to the size. There're even some with become even smaller (replaced "bloated" ActionBarSherlock with Material). But to be honest 70% actually added some more megabytes, which I despise so much.

Will do this, now I'm using this very phone to tether for 3G on the laptop, and xposed module installation requires reboot. And I know I'll have to do another reboot because I will again downgrade to currently in use version. I'll post the screenshots later, to describe it.

I'm sure I'm having that bug. But nevermind, I will re-confirm again, will reinstall 2.9.1 again. And 3.0.2 too.

Yes, I've taken a look at the codes. Both afollestad (480k smali) and melnykov (85k) libraries require android support library (10 MB). Actual dhm47 codes are only 800kb which, in pre-3.0 is the only thing used. I will say that <2MB is the "new minimum" I probably have to accept in the future, so I don't blame you, I know you tried hard...

Anyway I still vote for the good and slim previous guy over this new fat guy who eats too much because he has new companions whose terms are to include another of their companions who eats tenfold. I'll help to test the 3.0.2 for the above bug, but I'm sure I'll go back to 2.9 for practical use, at least for now. :)

-----

Food for thought

(General rant, not particular to this app or any/all good dev/devs):

I blame libraries authors for this (and Google too, they started this mess with Google Play Service and then some more) I wonder why everyone has to code linked codes in libraries, which in turn links to another code which in turn link to another. Libraries should be made stand alone, not dependent on another libraries. Android now becomes more like Visual Basic. At least in VB one can use a single shared .DLL but in Android, all the codes and resources and dependencies has to be compiled and included in every app, making each app so big. This started to happen circa mid-2014. I know, that most developers don't have much choices because library choices are limited, and most of the libraries (I'd say foolishly) somehow would depend to some Google monster libraries in the end.

Actually, app devs have some choices. For instance, drop gingerbread support in newer version. Another, try to avoid anything linked to Google codes, until Google provide updated libraries that will include everything in their glorified GMS.apk which for now did nothing other than some authentication and spying on your whereabouts which called Location Services. What I mean is, there's GMS.apk (for the login and spying purposes) and Google should create something like ASL.apk (Android Support Library) OR merge both of them. And then apps/libs authors can just use that by applying minimal codes (or tiny jars) in apps. AFAIK, the iOS development did just this. And Microsoft too. I wonder why Google took the opposite way. To fill old/small devices flash memory faster, perhaps? Not to mention size of APK+DEX (Dalvik or ART, all the same, ART is actually bigger) when other platforms its just APP. I'm sticking to Android because of the convenience and freedom, but in practicality its the worse (in term of coding and memory/storage/cpu use) and unoptimized platform compared to others.

Now, we just wait for ARM/x86/MIPS Android NDK mess to plague the Android world more, since Intel and Imagination started to act agressive against ARM...

If I want to monetize my 100k app today, the only way is to make it at least a 1.8 MB APK (about 3-5 MB dex inside) if I include GMS ADS. Or worse, third party ads such as Ad Colony will eat tens of megabytes of consumers data and device storage with video ads (imagine a SMS backup app or Flappy Bird clone game with 200MB of data; 10k are preferences .XML, the rest are video ads). Life has become so hard nowadays, for both devs and users. Until some communities such as the one on XDA take some action.

I rest my case.