Lanchon

the patched service uses this code to read the global sigspoof enable setting: https://github.com/Lanchon/haystack/blob/master/patches-src-gen/sigspoof-ui-global/services.jar/GeneratePackageInfoHook.java and the patched settings app uses this code to read and write said setting: https://github.com/Lanchon/haystack/blob/master/patches-src-gen/sigspoof-ui-global/Settings.apk(common)/FakeSignatureGlobalSetting.java

hi, it seems like there's an issue with your twrp. could you provide a link that explains why system is and must be mounted this way? thanks

yeah, i'm surprised the FS is not mounted in /. i don't know if this is standard for the new layout. in any case, i don't have a test device...

yes i'm aware of the system as root FS situation. what i was asking was whether it was standard of TWRP to mount the fs in /system instead of /...

hi, it's entirely possible to patch in-device. in fact, the patcher could use the 'addon.d' mechanism to patch automatically after every rom flash, just like gapps self install after every...

if you want to make a solution yourself for current haystack, you can. dexpatcher runs just fine in the dalvikvm. take a look here to see how: http://stackoverflow.com/questions/10199863/how-to-execute-the-dex-file-in-android-with-command

@Nanolx, > you'll now find the sub directory framework-patcher this is indeed an on-device framework-patcher. You can use it in two ways: > > flashable zip dalvikvm is not available...

definitely use flashize! it takes a shell script and outputs a flashable zip. output from the shell script gets displayed in recovery. there's also optional output logging, zip extraction, and...

why `(char*) strerror_r(error, buffer, length);` ? strerror_r returns an int, not a pointer.

hey, have you made any progress?