Given the clarification in the comment (should be in question, most important bit of information!), the answer is yes.
Accidential modification is something that should in theory be quite unlikely as there is link-level CRCs in place as well as checksums in the TCP/IP stack. The theoretical chance of an accidentially modified packet passing the link layer undetected is one in four billion which sounds almost like "never going to happen" but it actually does happen not so rarely. Consider that there's quite a few packets going over the wire, not just one or two. So the TCP/IP stack should almost certainly catch the ones that make it through. Right?
Well yes, in theory. In practice, research shows that about one in 16 million packets makes it through although it shouldn't (Stone, J., Partridge, C. SIGCOMM 2000).
Although you can never reduce the likelihood of failure to zero, throwing in a SHA-1 checksum the way you suggest will lower the risk so far as to count as "does not matter". Technically it is a lie to say so, but you can consider this "guaranteed" by all practical means.
While malicious modification may be a valid concern (though it's not for you as stated), the expectation of accidentially encountering a collision on SHA-1 is outright ridiculous. This isn't going to happen during your or your childrens' or grandchildrens' lifetime.
However, do note that creating a socket that uses TLS is about 5-6 lines of code in Java (including
import statements), which is not really more work than creating a plain vanilla socket, and it will also make malicious modification several orders of magnitude harder. The overhead of TLS is not that bad either, so it's usually an acceptable thing to do.