Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Currently, we have a binary data file, generated from desktop machine using oracle JVM. Desktop oracle JVM saves file in big endian format.
Now, we send to file to our Android device, and read from it. Our Android application doesn’t make use of any NDK feature. We realize the big endian file can be read correctly.
Is this behaviour consistent across different devices? Is there any need for me to check the endiannes during runtime, before my Android app read the file?
If you are using
DataOutputStreamandDataInputStream, then things will be encoded in a “machine-independent way”. This happens to be “network byte order” (ie: big-endian) for numeric types.