Merkury720
Merkury720 copied to clipboard
guino
ppsapp patch requests
IF your ppsapp is not listed HERE, feel free to post your ppsapp patch requests here along with the firmwareversion, hardwareversion information from http://admin:056565099@IP/devices/deviceinfo for your device along with the MODEL (ie merkury 720p or geeni 720p, etc).
I will look at it when I have a chance and post it in the list above (and will remove it from here).
You're amazing man! I'm so happy you finally got it working, you genius :) Here's my firmwareversion:"ppstrong-a2-tuya2_teco-2.7.4.20191111" hardwareversion: S4C_A1_V10_1245 , model : Nedis camera (WIFICI20CGY)
Could you please patch my ppsapp?
@solidssss your ppsapp patch is posted here: https://github.com/guino/ppsapp-rtsp/issues/1#issuecomment-754199410
@guino Hmm, it's not working properly. I can enter the adresses http://user:password@IP:8080/cgi-bin/snap.cgi and http://user:password@IP:8080/cgi-bin/mjpeg.cgi, but they do not display anything, it's just empty. I've tried to get the RTSP stream in VLC and other softwares, but it's not working either. http://192.168.1.9/proc/self/root/mnt/mmc01/hack says done.
@solidssss are you able to telnet into the device ? I can double check the patch file -- I assume you used https://www.marcrobledo.com/RomPatcher.js/ to create the RTSP version of ppsapp and placed it in the root of SD card names as 'ppsapp' ? Last, for mjpeg/snap.cgi these should work as long as busybox is working (even if you don't patch ppsapp) assuming you adjusted the addresses in the snap/mjpeg cgi files, did you do that ?
Oh sorry, I didn't know about the rompatcher. I took my home\app\ppsapp & ppsapp-rtsp.ips and patched them, put them on the root of the SD card as 'ppsapp' without any file extension but I still cannot get RTSP to work. I'm still supposed to keep the old ppsapp in the home\app\ folder right?
I had missed the part about patching the adresses of mjpeg/snap.cgi. After I patched the adreses it works! But I really would want the RTSP to work too. I can enter the camera with telnet.
that's progress nonetheless. After you copied ppsapp (the one you got from rom patcher) to the root of the SD card (as ppsapp) -- did you reboot the device ? You should hear the startup sound 2 times when the device boots -- RTSP should work after the second startup sound at rtsp://IP:8554 - please confirm you heard the startup sound 2 times and confirm the rtsp URL. I checked the patch and everything looks good so I would expect the patch to work.
Yes, I rebooted after I placed the patched ppsapp. I do hear two startup sounds, but I cannot get anything with VLC, Home Assistant or Perfect IP Camera app. The url I use is: rtsp://192.168.1.9:8554. I tried to start VLC with --rtsp-tcp rtsp://192.168.1.9:8554 too, but it did not work. I have blocked internet access to the camera btw, if that has anything to do with it.
Ok, you can't disable internet access to the device -- if you block it the device won't fully start (and won't start RTSP).
Please allow internet access to the device then try again. If that doesn't fix the issue we'll have to do some debugging, in which case: please do this:
- Modify your line 10 of custom.sh changing
/mnt/mmc01/ppsapp &to/mnt/mmc01/ppsapp &> /mnt/mmc01/ppsapp.log & - Reboot the device (verify it makes 2 startup sounds) and wait 2 minutes
- Try opening the RTSP stream with VLC
- Remove SD card, Copy the ppsapp.log from the SD card, ZIP and post it here so I can review it.
Without the log to review there's not much I can do.
Oh my god, it's working now! Thank you so much for your hard work @guino I gave the camera internet access and now it works flawlessly with RTSP. It took like 2 minutes extra for it to fully boot and show RTSP feed though, but that's ok.
softwareversion":"2.7.5","hardwareversion":"M7C_AK_V10_1245","firmwareversion":"ppstrong-a2-tuya2_geeni-2.7.5.20200520
--deleted--
If you would be so kind!
@solidssss These devices are very slow so yeah it takes some time for it to boot up entirely and startup the application completely. I appreciate your feedback and donation!
@Dsm20001 I'll take a look soon and post a patch for it.
@Dsm20001 should be done here: https://github.com/guino/ppsapp-rtsp/issues/1#issuecomment-754841429 Remember to use the https://www.marcrobledo.com/RomPatcher.js/ to patch your ppsapp into a rtsp enable version then copy it to the root of SD card as ppsapp and reboot. If you want snap/mjpeg.cgi to work you also have to edit the files to set the address provided with the patch file.
Hi guino! Thanks for all the work so far! I've searched the current patch list for both my firmware and ppsapp md5 and not seeing it there. Since I looked over what would be required to do the patch myself, and that's way outside my wheelhouse, here's the requested info for whenever you or someone else has the time:
"softwareversion":"2.7.5","hardwareversion":"M7C_AK_V10_1245","firmwareversion":"ppstrong-a2-tuya2_geeni-2.7.5.20200221"
--deleted--
Thanks!
@Mathurian this is done here: https://github.com/guino/ppsapp-rtsp/issues/1#issuecomment-754896349 Remember to use the https://www.marcrobledo.com/RomPatcher.js/ to patch your ppsapp into a rtsp enable version then copy it to the root of SD card as ppsapp and reboot. If you want snap/mjpeg.cgi to work you also have to edit the files to set the address provided with the patch file.
Thank you finally got it. I had to use a different Rom Patcher, but finally got it!!!! now if i can get my outdoor camera's the same way lol. Thank you so much!!!
Here's another Merkury 720 ppsapp - same version/firmware as your initial posting on this camera, but a different MD5 hash. Needs patching.
Smart Home Camera - Mini7C software version 2.7.3 hardware verison: M7C_AK_V10_1245 firmware: ppstrong-a2-tuya2_geeni-2.7.3.20190720 MD5: 0dbd3d62584d4b57cdc0764efd1d3110 --deleted--
@russinnes I think you may have got a bad copy of ppsapp (the one you posted above). It is mostly the same file as https://github.com/guino/ppsapp-rtsp/issues/1#issuecomment-740389996 but there's a 64Kb section in the file that is different and appears to be all 'garbage'. This could be an issue with the SD card or just a side-effect from powering off the camera too fast after applying the hack (to get the file). Please do this:
- Power off device + remove SD card
- Insert SD card om computer, rename the "home" directory/folder to "home-old"
- Properly Eject/unmount SD card from tray/explorer/icon/etc
- Insert SD card on device while powered off
- Power device on (normally)
- Use http://admin:056565099@IP/devices/reboot to reboot the device after it's up and running
- Power off device, copy ppsapp file again from /home/app/ and check the md5 -- I am taking a guess it will be the same as the one previously posted.
Please notice I am asking you to rename the home directory instead of deleting it so the new home directory is saved in a different area of the SD card (to rule out an issue with bad sectors).
Let me know the results.
@russinnes I think you may have got a bad copy of ppsapp (the one you posted above). It is mostly the same file as guino/ppsapp-rtsp#1 (comment) but there's a 64Kb section in the file that is different and appears to be all 'garbage'. This could be an issue with the SD card or just a side-effect from powering off the camera too fast after applying the hack (to get the file). Please do this:
- Power off device + remove SD card
- Insert SD card om computer, rename the "home" directory/folder to "home-old"
- Properly Eject/unmount SD card from tray/explorer/icon/etc
- Insert SD card on device while powered off
- Power device on (normally)
- Use http://admin:056565099@IP/devices/reboot to reboot the device after it's up and running
- Power off device, copy ppsapp file again from /home/app/ and check the md5 -- I am taking a guess it will be the same as the one previously posted.
Please notice I am asking you to rename the home directory instead of deleting it so the new home directory is saved in a different area of the SD card (to rule out an issue with bad sectors).
Let me know the results.
Good catch - Was just about to open it to patch it manually. New MD5: b796c6f02abe9e278fbe40bdd27e64cb. Let me run it against your earlier patch . Ill let you know.
@russinnes I think you may have got a bad copy of ppsapp (the one you posted above). It is mostly the same file as guino/ppsapp-rtsp#1 (comment) but there's a 64Kb section in the file that is different and appears to be all 'garbage'. This could be an issue with the SD card or just a side-effect from powering off the camera too fast after applying the hack (to get the file). Please do this:
- Power off device + remove SD card
- Insert SD card om computer, rename the "home" directory/folder to "home-old"
- Properly Eject/unmount SD card from tray/explorer/icon/etc
- Insert SD card on device while powered off
- Power device on (normally)
- Use http://admin:056565099@IP/devices/reboot to reboot the device after it's up and running
- Power off device, copy ppsapp file again from /home/app/ and check the md5 -- I am taking a guess it will be the same as the one previously posted.
Please notice I am asking you to rename the home directory instead of deleting it so the new home directory is saved in a different area of the SD card (to rule out an issue with bad sectors). Let me know the results.
Good catch - Was just about to open it to patch it manually. New MD5: b796c6f02abe9e278fbe40bdd27e64cb. Let me run it against your earlier patch . Ill let you know.
No Go - Here's round 2 attached (unpatched) --deleted--
@russinnes This one has a different bad area, meaning: the part that was bad on the 1st one you posted is now ok, but there's a different section of the file that is bad. I am 100% sure now that the firmware is the same as the one I posted on https://github.com/guino/ppsapp-rtsp/issues/1#issuecomment-740389996 -- You may want to repeat the process above but instead of using /devices/reboot to restart it, you can login by telnet and execute /mnt/mmc01/busybox sync then umount /mnt/mmc01 then remove the card and copy ppsapp and check the md5.
3rd time finally got the same MD5 as your initial patch. Out of interest (and perhaps the issue), this camera is paired with the generic tuya app - there is no setting for record. Upon detection of SD, it is always recording, with no option to turn it off. It wouldnt unmount via any normal means as it was constantly being written to. I ended up killing the ./ppsapp PID via telnet to finally get it to stop writing. Hence the prior bad sectors/writes/etc. Try #4 coming up.
3rd time finally got the same MD5 as your initial patch. Out of interest (and perhaps the issue), this camera is paired with the generic tuya app - there is no setting for record. Upon detection of SD, it is always recording, with no option to turn it off. It wouldnt unmount via any normal means as it was constantly being written to. I ended up killing the ./ppsapp PID via telnet to finally get it to stop writing. Hence the prior bad sectors/writes/etc. Try #4 coming up.
Like a charm - unbelievable. Good catch.
@russinnes yes, it records 24/7 by default with no settings in the tuya app but you can modify it on the json file like I did in my write up so it only records motion (or disable it). You can also turn off the LED and/or disable/force night mode (I did it to try), but like you said no settings in the app for any of that.
For anyone following the project I just uploaded some changes to snap.cgi/mjpeg.cgi along with a jpeg-arm file which should prevent the occasional image glitches that we had with the original version (which was very much a rig). The new version uses a custom written C application with a double buffer to verify the buffer/image wasn't changed by the device while reading it.
If you use snap.cgi/mjpeg.cgi and want to take advantage of the glitch free version you have to copy jpeg-arm to the SD card root and copy snap.cgi + mjpeg.cgi (to cgi-bin/) and make sure the address is set for your ppsapp.
For anyone following the project I just uploaded some changes to snap.cgi/mjpeg.cgi along with a jpeg-arm file which should prevent the occasional image glitches that we had with the original version (which was very much a rig). The new version uses a custom written C application with a double buffer to verify the buffer/image wasn't changed by the device while reading it.
If you use snap.cgi/mjpeg.cgi and want to take advantage of the glitch free version you have to copy jpeg-arm to the SD card root and copy snap.cgi + mjpeg.cgi (to cgi-bin/) and make sure the address is set for your ppsapp.
Ran the native app, an RTSP stream, and an mjpeg stream all simultaneously and only capped at ~65% cpu. Much cleaner than using dd! I'm going to add some custom motion detection scriptability to what you have done, I've been digging around a little bit, just need to dig out a VM with the arm toolchain to test.
@russinnes I updated jpeg-arm to find the end of the jpeg in the buffer and only transmit the latest jpeg data without any left over/previous data from the buffer. This seems to be working better with VLC and other applications that can view mjpeg (although I never had issues with firefox before).
--deleted--
Hope you can help me
Merkury 720p
| evname | "Smart Home Camera" |
|---|---|
| model | "Mini 7C" |
| serialno | "058312676" |
| softwareversion | "2.7.3" |
| hardwareversion | "M7C_AK_V10_1245" |
| firmwareversion | "ppstrong-a2-tuya2_geeni-2.7.3.20190917" |
Hack is done
Could you please patch my ppsapp?
Thanks
