This project was moved to my private git server . This repository may not be up to date.

(Always prefer F-Droid build, when possible).

Ojo is a basic IP Camera surveillance wall. IP camera's RTSP streams are added via its url and shown in the classic tile configuration. The number of tiles is automatically choosen based on the number of configured cameras: a single camera goes full screen, adding more cameras the app switches to a grid view: 2x2, 3x3, 4x4 and so on. The maximum number of cameras is determined by the device's capabilities.

The stream decoding and rendering is demanded to VLC's library: without their effort this app wouldn't be possible. This app was specifically developed for F-Droid, as I couldn't find any open source RTSP vievers in the main repository.

The app can be opened deeplinking to url ojo://view. To open the app with focus on a specific camera, you can use an intent (it.danieleverducci.ojo.OPEN_CAMERA) to specify which camera you want to view. The extra argument it.danieleverducci.ojo.CAMERA_NAME will open the app with the camera with the name you specified while adding the camera. The extra argument it.danieleverducci.ojo.CAMERA_NUMBER starting at 1 could be used as well, if you have multiple cameras with the same name. See belows example how to use the intent. The flag (-f 268468224) could be useful if you want to switch to an other camera while the app is running.

adb -s <YOUR_DEVICE> shell am start -a it.danieleverducci.ojo.OPEN_CAMERA -f 268468224 --es it.danieleverducci.ojo.CAMERA_NAME <YOUR_CAMERA_NAME>
adb -s <YOUR_DEVICE> shell am start -a it.danieleverducci.ojo.OPEN_CAMERA -f 268468224 --es it.danieleverducci.ojo.CAMERA_NUMBER <YOUR_CAMERA_NUMBER>

• Thanks to brenard for the new grid sizing method
• Thanks to davquar for the fullscreen compatibility fix on Android 11
• Thanks to jayfan0 for the first deep link implementation
• Thanks to free-bots for the selection border on Android TV, intents for direct camera access and leanback support

The project is open to contribution, but with some limits:

• I'm sorry I can't accept AI-generated contributions. Reviewing a contribution requires time and effort from my side, while generating code with AI requires very little time and produces non reliable code that must be reviewed in detail. This is effectively shifting the work on my side, and in a forced way. If you feel you need a feature but you're not able to implement it by yourself, I prefer you to create an issue in the repository so I can implement it when I can, in a more mantainable way.
• Before implementing a big change, please contact me to ensure it goes in the project's direction.
• If working on an existing ticket, please name the branch accordingly (feature/ticketNumber, bugfix/ticketNumber...).
• Only issue pull requests to the develop branch, never on the main/master one.

Please see the main repository README file on how to obtain an account to my git instance.