Originally Posted by c0rnholio
Let me know if it works!
! Wow, you're working pretty fast!
Unfortunately it's not working (yet) on my Nexus 4 with cyanogenmod 10.2. I've tested with your latest version 2.1.1 (23) from the market.
Here my observations:
At my first try, although I've enabled the HushSMS module in the Xposed installer, the module didn't get loaded by the Xposed framework. For some reason it looked in the wrong path so I got a "File does not exist" error in the Xposed logfile. Here is the logcat output (the same like in /data/xposed/debug.log):
09-25 08:10:14.692 I/Xposed ( 191): -----------------
09-25 08:10:14.692 I/Xposed ( 191): 25.09.2013 06:10:14 UTC
09-25 08:10:14.692 I/Xposed ( 191): Loading Xposed (for Zygote)...
09-25 08:10:14.772 I/Xposed ( 191): Loading modules from /data/app/pk.qwerty12.receivedsmssenttimesindetails-1.apk
09-25 08:10:14.942 I/Xposed ( 191): Loading class pk.qwerty12.receivedsmssenttimesindetails.ReceivedSMSSentTimesInDetails
09-25 08:10:14.942 I/Xposed ( 191): Loading modules from /mnt/asec/com.silentservices.hushsms-1/pkg.apk
09-25 08:10:14.942 I/Xposed ( 191): File does not exist
You can see the Xposed framework tried to load your module from the path /mnt/asec/com.silentservices.hushsms-1/pkg.apk
. I checked myself on the shell and saw that in fact it was installed under: /mnt/asec/com.silentservices.hushsms-2/pkg.apk
I have no idea why the application is installed at "hushsms-2" and why Xposed looked at "hushsms-1". Maybe this has to do with the fact that some days ago, when I tested HushSMS the very first time, I uninstalled and refunded it again after a few minutes, and yesterday bought and installed it once again. Maybe this re-installation caused the new path? But that's just a rough guess.
Nevertheless, I did the following steps, which corrected this problem:
- uncheck HushSMS module in Xposed
- uninstall HushSMS
- reboot phone
- install HushSMS again from Play Store
- activate HushSMS module in Xposed installer
- reboot phone once again
After this procedure the Xposed module gets loaded correctly (the application is now installed at /mnt/asec/com.silentservices.hushsms-1/pkg.apk
and exposed loads the module correctly now.
Sorry, no, after another reboot there is still a problem with the loading of the Xposed module. Now I get the same error again:
09-25 08:44:34.443 I/Xposed ( 191): Loading modules from /mnt/asec/com.silentservices.hushsms-1/pkg.apk
09-25 08:44:34.443 I/Xposed ( 191): File does not exist
but when I check on the adb shell the file DOES
exist at this location.
Hmm.. strange. Mabe the encrypted filesystems for protected apps (the /mnt/asec/.. ones) gets mounted after the Xposed framework loads?? Just guessing..
As a result of this problem (when module is not loaded) I can see your "special" SMS text ("allyourmessages.."). To avoid this you could insert a check
into your application if the Xposed module is really loaded
I saw a nice way to to this here in this Xposed module:
As you can see in the handleLoadPackage() method the author sets a static variable in his own Xposed module application. So at other places in his application he just needs to check the value of this static field, to determine if the module was correctly loaded by Xposed.
At the moment I have no idea, why the module loading is not working.. I will do some more checks and let you know, if I find something out. maybe you still need to outsource your Xposed module into a separate apk? No idea..