busybox is on /bin which isn't in the partition that's flashed with npcupg.bin, so I dont think you can replace busybox. You can build a minimal busybox with only the utilities you need, and that should be able to fit on /npc as part of your npcupg.bin image.How could I pack a different kind of busybox to the firmware file?
This isn't working for me but I've already got firmware 13.01.01.36 so the camera assumes it is newer and won't install.Patched Firmware 13.01.01.31 based on 13.01.01.30:
- Has Telnet enabled
- Has FPS fix, steady on 15fps
- Stays up&running > 3 days, even when disconnected from WAN
Instructions to install:
Place npcupg.bin on root of (preferably empty) SD card
Insert SD card into slot on Doorbell
Open YooSee App -> Settings -> Firmware and select install. This will install the local firmware from SD.
I like to thank users @mrxyz, @sp00025, @SecuritySeeker, @petervk for their input and for sharing their work here.
I take no responsibility for any kind of damages or malfunctioning resulting from using attached firmware.
Thanks very much for this firmware, the actually image quality of this is much better than my DB1 however the framerate drop and reboots were a no no.You could also use the IPCam tool provided in this thread to push the firmware to the doorbell.
Florissilfhout- I just want to say a big thank you to you and the other users you mentioned. This made the camera soooo much better. I could not use it reliably with shinobi or tinycam until I upgraded to this firmware. It stays on 15fps.Patched Firmware 13.01.01.31 based on 13.01.01.30:
- Has Telnet enabled
- Has FPS fix, steady on 15fps
- Stays up&running > 3 days, even when disconnected from WAN
Instructions to install:
Place npcupg.bin on root of (preferably empty) SD card
Insert SD card into slot on Doorbell
Open YooSee App -> Settings -> Firmware and select install. This will install the local firmware from SD.
I like to thank users @mrxyz, @sp00025, @SecuritySeeker, @petervk for their input and for sharing their work here.
I take no responsibility for any kind of damages or malfunctioning resulting from using attached firmware.
It was possible in my setup to use ntp to set the needed time, albeit a faked timezone use. TZ variable is working and needs some adjustment by -1 to achieve the correct readings.... Say if you need UTC-5, set it to UTC-6. With "export TZ=UTC-6" and the quoted ntp command it will sync to the correct time. Only, setting environment variable in dhcp.script fails. So putting the ntp command there even after export TZ will sync only to UTC.I got the NTP client running with
/mnt/disc1/busybox ntpd -q -p [server]
added in the /npc/dhcp.script. But this only gives UTC, I didn't manage to get my correct timezone set. Neither TZ variable nor a /etc/timezone helped. Also datetimectl is not supported by busybox.
Any idea?
Maybe studit question if I’m going to use this image do I still need the app to configure RTSP password and other things?Florissilfhout- I just want to say a big thank you to you and the other users you mentioned. This made the camera soooo much better. I could not use it reliably with shinobi or tinycam until I upgraded to this firmware. It stays on 15fps.
If you are having problems with consistent streaming/recording, use this firmware!
Thanks again Florissilfhout!
If you copy the firmware file to the root of the uSD card, called npcupg.bin and boot the camera, it should pickup that there's a new image and flash it.In such a setup what I miss is a simple way to flash the FW without the vendor provided app. If anyone knows how do do it via telnet without setting TFTP server, etc., please share your thoughts.
Nooo, it does not work this way. Otherwise, the firmware always updates on boot if npcupg.bin is not removed from your SD. Using windows software like IPCTestTool is also of a little help as it requires the cloud connection to operate.If you copy the firmware file to the root of the uSD card, called npcupg.bin and boot the camera, it should pickup that there's a new image and flash it.
Thank you so much to everyone who worked on this. Two years ago I invested a lot of time attempting to solve this 5 fps limitation. After finding the string in the firmware, making an attempt at ghidra and researching for a month or two I came to the realization this was above my paygrade. I gave up in defeat and thought it was over.... Tonight I installed the firmware patch you guys have been working on and am getting a steady stream of 15fps. Thank you... This really makes this cam viable now that the chop is gone from 5 fps.Patched Firmware 13.01.01.31 based on 13.01.01.30:
- Has Telnet enabled
- Has FPS fix, steady on 15fps
- Stays up&running > 3 days, even when disconnected from WAN
Instructions to install:
Place npcupg.bin on root of (preferably empty) SD card
Insert SD card into slot on Doorbell
Open YooSee App -> Settings -> Firmware and select install. This will install the local firmware from SD.
I like to thank users @mrxyz, @sp00025, @SecuritySeeker, @petervk for their input and for sharing their work here.
I take no responsibility for any kind of damages or malfunctioning resulting from using attached firmware.
YooSee's website states
Image sensor: SmartSens SC2235
SmartSens's Product list says
Max Frame Rate 1920H x 1080V @50fps
I ran strings on ncp.exe... Now I feel overwhelmed and hopeless....
I think something is wrong with their code... More like something is moving, frame rate is down... and stays downCode:[%s, %d]:something is moving, frame rate is normal [%s, %d]:nothing is moving, frame rate is down VENC_autoDownFrameRate vNightModeDownFrameRate
same with NightModeDownFrameRate