Phillip Tennen
Phillip Tennen
Of course I agree that doing this statically is a non-starter. But, it seems totally doable dynamically and a valuable QoL improvement. I understand the justification to want to avoid...
I now see bugs caused by the behavior mentioned in the commit message. I think both approaches above would avoid it.
As stated above, NanoTimeKit is an internal framework running on the Watch. To get headers you can either class dump the binary, or simply write them yourself. I do not...
@hamzasood Would you be willing to share what vector/general starting point you're using to get Carousal to load dylibs? Fully understand you don't want to share all your goodies, though...
@DJLectr0 Hey, that's better than nothing! Mind divulging how you did that? Maybe we could go digging together and see what we can figure out :-)
@DJLectr0 That post is sorely outdated and does not work on recent versions of the iOS sim. I cannot speak for the Watch sim as I have not tried it,...
@DJLectr0 Actually, I have. I totally forgot about this earlier, but @EthanArbuckle and I fooled around with loading some dylibs into the Watch sim's Prefs.app - nothing big, mind you;...
(Addressing each sentence in order) @DJLectr0 Loading a custom firmware isn't in the spirit of what we're trying to achieve IMHO. It's the argument of using Substrate over manually replacing...
@EthanArbuckle +1
@AlexeyBelezeko Simple answer: no. The reason is twofold: 1) That would mean we need native code execution on the watch, which is the end goal in the first place 2)...