it would make the code much more understable and less complex
There are many ways to have an API that is "more understandable and less complex". Those objectives do not require inheritance. In some cases, inheritance may be a way to achieve those objectives, but inheritance is not the only solution. And, in some cases, like this one, inheritance has its own issues.
For instance: When trying to zoom you have to first update the camera parameters with the zoom value and then set the camera parameters to the camera. In my own camera object, I then would be able to implement something like camera.zoom();
Use composition.
composition is what I am doing right now. But I feel that there has to be somthing better
Since here is no constructor for Camera
that is part of the Android SDK, you do not have much of a choice in the matter, if you want reliable code.