p1 is an invalid register in that context. In fact, baksmali should have caught that! :)
With .registers 2 and a single argument, you have registers v0 and v1, with p0 being aliased to v1. p1 would actually be v2, which isn't allowed, per your .registers directive.
What you want is
invoke-static {p0, p0}, Landroid/util/Log;->d(Ljava/lang/String;Ljava/lang/String;)I
or equivalently
invoke-static {v1, v1}, Landroid/util/Log;->d(Ljava/lang/String;Ljava/lang/String;)I
With respect to how to debug this sort of error, the best thing you could have done would be to look in the dalvik source code for the VFY error strings that you see, and identify exactly what the error message means (i.e. what error condition is it triggered on), and where in the bytecode the error occurs.
For identifying where it the bytecode the error occurs, look at the error lines
10-05 21:52:42.081: W/dalvikvm(32021): VFY: rejecting opcode 0x71 at 0x0000
10-05 21:52:42.081: W/dalvikvm(32021): VFY: rejected Lcom/shqipe/worthstream/utils/Utils;.log (Ljava/lang/String;)V
This shows that the error happened in the Lcom/shqipe/worthstream/utils/Utils;.log (Ljava/lang/String;)V
method, at bytecode offset 0 (i.e. the first instruction). However, in case it's not clear which instruction it is referring to, you can use the -f option to baksmali, which will cause it to add the bytecode offset as a comment before each instruction.