String has a constructor that receives an array of bytes and converts that to a string. One thing to note however is that an array of bytes cannot be determined to only have 1 byte per character as it might be in wide character format. But there are constructors that allow for converting the type of ascii encoding if need be.

To get the first 10 bytes from a stream or even the first n bytes, use the following.



Now to read in the integer version.



Likewise there are multiple types of buffers in the java.nio package. Both are included in the android API so you should be good there.

You may also be interested in DataInputStream which might make things easier for you if you are having trouble getting your head around how the ByteBuffer's work.

Here would be one way to convert your function LoadHeader.



C to Java caveat
Java is a much more strongly typed language than C, so there is an abstraction between memory and your program. Unlike C where everything is just memory and you can manipulate it however you want and use neat pointer and memory address manipulations to do anything you want to it, in java there is a more strict contract between memory and the language everything essentially in java is an Object rather than memory. While java allows binary operations on primitive types an Array in java such as int[] array; is basically an object not like in C where it is just a sequence of bytes somewhere in memory. Thus you cannot guarantee the format of memory, so a by product of using java is to adhere to this strict contract. In java you must write code to specifically convert between types or properly use inheritance to solve your problems. Hope this helps, and also the reference documentation for Android is your friend, use it until you know every bit of it because it could save you a lot of time hunting down problems or writing low-level routines that have more stable and tested solutions. Just something to keep in mind as you convert your code.

Skeletal Animation vs Keyframed on Android
As far as Skeletal animation versus key framed. I am not sure what the programmable shader support is for the OpenGL ES specification. But if it is supported it might limit the amount of array size for matrices which would limit your Skeletal animation shader but it might still be doable. If there is no shader support then key framed is the way to go since doing skeletal animation without a shader would result in modifying the vertex buffer for an object and applying matrix transforms for the bones either every frame or just converting the skeletal animation to keyframed when loading the program, and applying the animation matrix transforms while loading.