QRAlarm vs UVC Camera / Usb Camera custom

Side-by-side comparison of two open source alternatives

QRAlarm

Say goodbye to oversleeping with QRAlarm! 🚀 QRAlarm - QR Code Alarm Clock is an effective and smart alarm clock that gets you out of bed by making you scan the QR or Barcode to turn off the alarm! This makes it perfect for both heavy sleepers and productive early risers! 🔝 Have you ever... - ⏰ ...found yourself caught in the “snooze loop” where you kept snoozing the alarm while never getting up? - 😴 ...turned off your alarm giving yourself those mythical “5 more minutes” just to fall back asleep again and oversleep? - 📝 ...wanted to start off the day earlier to get your tasks done but you simply couldn’t leave your bed in the morning? Then QRAlarm is perfect for you! 🫵 QRAlarm is not just another alarm clock app - the QR alarm mission functionality is there to help you always get up on time! Because a strong and innovative alarm clock does not only wake you up - it makes sure that you GET UP! 🙌 If you are seeking to: - Fight with oversleeping, - Break your snooze habits, - Improve your morning productivity, - Build your perfect morning routine, - Stay healthy and happy, Then you have found the perfect alarm clock application - this is your new life hack! 📈 QRAlarm is a simple and lightweight alarm clock! Don't worry about low memory in your phone - QRAlarm is only around 15 MB making it perfect fit for everyone, no matter the device! 📱 QRAlarm has a simple, clean and intuitive user interface that makes the experience easy and seamless! You will feel at ease using QRAlarm as it does not overwhelm the user with bloated functions. QRAlarm is uncluttered, clear and beautiful! ✨ Download the app now, set up and configure your alarms and let QRAlarm work its magic! 🪄

UVC Camera / Usb Camera custom

Android-UVC-Camera The app connects to a usb camera from your Android Device. (OTG cabel or OTG Hub needed) This Project was built to perform an Isochronous Video Stream for all Android Devices (Above 4.1 Ice Cream Sandwich)(Mediathek Devices too) with UVC Cameras. The program uses your userspacr usb device driver to perform an isochronous transfer with your camera device. Follow this way to set up your own userspace device driver: First you have to set up all camera settings for your device. The program then saves the values and you can restore them later or overwrite them with other values. Use the "Edit/Save/Restore" Button to adjust the values. Use the automatic camera serarch to find and set up the camera. Explaination: When the automatic search succeeds, you first set up the MAXIMAL PACKET SIZE. If your device is a mediathek device, you may have to lower the value for the max packet size. The Value PACKETS PER REQUEST defines the Number of the Packets sended to the device: One packet has a size of 3000 bytes and you use 16 packets at one time for sending. Here you define the amount of Bytes which were sent. Next thing are the USB REQUEST BLOCKS (activeUrb): These are in relation to the max packet size. You have to find here the right values for your device and control the output on the screen under the menupoint "Isoread". Some typically values for Qualcom Devices are: 8 for the activeUrbs and 16 Packets per Request.... The first thing of the method Isoread is a Controltransfer to the camera device: If the controlltransfer is successful, than you are ready to go. Next take a look at the frames. When you receive identically and long frames, you can proceed to the method Isostream, where the frames were displayed on your screen. To know how big be a Frame should be, you can look at the output of the controll transfer of the camera in the log: maxVideoFrameSize, This value is returned from the camera and should be the valid frame size (The value is calculated by Imagewidth x Imagehight x 2). The IsochronousRead1 class shows you how the frames are structered by the camera. Different camerasetting == Different Frame structers. Try it out with different setting and look at the output. The eof hint shows the framesize in the log. For valid camera settings the size should be the same as maxFrameSize value of the controlltransfer. Output method Isoread: (Controltransfer) Thirst the program will send a controlltransfer to your camera device. The output of it looks as following: Initial streaming parms: hint=0x0 format=1 frame=1 frameInterval=2000000 keyFrameRate=0 pFrameRate=0 compQuality=0 compWindowSize=0 delay=0 maxVideoFrameSize=0 maxPayloadTransferSize=0 Probed streaming parms: hint=0x0 format=1 frame=1 frameInterval=2000000 keyFrameRate=0 pFrameRate=0 compQuality=0 compWindowSize=0 delay=0 maxVideoFrameSize=614400 maxPayloadTransferSize=3000 Final streaming parms: hint=0x0 format=1 frame=1 frameInterval=2000000 keyFrameRate=0 pFrameRate=0 compQuality=0 compWindowSize=0 delay=0 maxVideoFrameSize=614400 maxPayloadTransferSize=3000 The first line are the values you set in the program, to connect the camera. (Initial streaming parms} The secound line are the values from the camera, which the camera returned from your values. And in the third line are the new saved and final values from the usb camera. Outpuf from the first Method: isoRead: EOF frameLen=10436. --> For Example here a frame ends with a length of 10436 wich is not 614400 as we expected from the controltransfer, so you may have to change some values of you program to get a valid frame size.

FeatureQRAlarmUVC Camera / Usb Camera custom
LicenseGPL-3.0-onlyLGPL-2.1-only
Install sources
F-DroidGitHubIzzyOnDroid
F-DroidGitHub
Categories
Media PlayerDev ToolsVideoCalendar
Media PlayerDev ToolsVideo
Features
Ad-FreeOpen SourceNo Tracking
Ad-FreeOpen SourceNo Tracking
Platforms
Android
Android
Website
Source code