NX-KS Mod pack for NX1 / NX500

Just wanted to share a nice news:

TLDR - new persistent PID of di-camera-app is 248, keyscan also survives hibernation (works without bluetooth now) - we have a stable way to hack suspended image that is run on powering on the camera. :)

For details see here: https://github.com/ottokiksmaler/nx500_nx1_modding/issues/27#issuecomment-218683701
That's a big one, yes? Congrats!
Indeed. Once it makes into production all bluetooth issues will go away (BT will revert to original functionality) and bitrate mods will be super-stable and available instantaneously - you won't risk not having them applied even if you pull the battery.

You will be able to shoot with your chosen rates as fast as when you did not have them.
 
v1.56m

focus-pull is now as slow as possible
in case someone wants to use it as a focus-stack

Returned - TBBAF only as temporary feature, after use - reboot

Added Peaking's option for the new keyscan, not persistent

NX-KS-Readme

NX-KS download page

NOTE: This is still the UBER-SAFE, BT-Mod version, not messing with camera's hibernation image, and still loads as fast/slow as before. The automated messing with that will come a bit later.
EV+OK doesn't work on NX1 for some reason. I did install this version twice with clean sdcard but no luck. Mod install itself seems to be OK, it uninstall previous version, restart the camera and install new one, show the "version number" message, but gui doesn't work

In fact, EV+ button combinations doesn't work with hack, I can't run telnet or other things

EV button works fine outsibe the hack, it allows to change EV
bummer.. must be the new keyscan =/
I'll revert it back and disable the peaking option
 
Cool!!
 
v1.56m

focus-pull is now as slow as possible
in case someone wants to use it as a focus-stack

Returned - TBBAF only as temporary feature, after use - reboot

Added Peaking's option for the new keyscan, not persistent

NX-KS-Readme

NX-KS download page

NOTE: This is still the UBER-SAFE, BT-Mod version, not messing with camera's hibernation image, and still loads as fast/slow as before. The automated messing with that will come a bit later.
EV+OK doesn't work on NX1 for some reason. I did install this version twice with clean sdcard but no luck. Mod install itself seems to be OK, it uninstall previous version, restart the camera and install new one, show the "version number" message, but gui doesn't work

In fact, EV+ button combinations doesn't work with hack, I can't run telnet or other things

EV button works fine outsibe the hack, it allows to change EV
how about now?
updated to: v1.57m keyscan rollback / no auto-peaking

NX-KS download page
 
Last edited:
v1.56m

focus-pull is now as slow as possible
in case someone wants to use it as a focus-stack

Returned - TBBAF only as temporary feature, after use - reboot

Added Peaking's option for the new keyscan, not persistent

NX-KS-Readme

NX-KS download page

NOTE: This is still the UBER-SAFE, BT-Mod version, not messing with camera's hibernation image, and still loads as fast/slow as before. The automated messing with that will come a bit later.
EV+OK doesn't work on NX1 for some reason. I did install this version twice with clean sdcard but no luck. Mod install itself seems to be OK, it uninstall previous version, restart the camera and install new one, show the "version number" message, but gui doesn't work

In fact, EV+ button combinations doesn't work with hack, I can't run telnet or other things

EV button works fine outsibe the hack, it allows to change EV
how about now?
updated to: v1.57m keyscan rollback / no auto-peaking

NX-KS download page
Yes, it works now, thanks
 
This is very impressive, a big thank you to all the contributors.

Is there a way to have longer batch recording than 840 seconds (14 minutes)? That would be useful when shooting at 1920x1080 and to avoid the corrupted file after 74 minutes.
 
This is very impressive, a big thank you to all the contributors.

Is there a way to have longer batch recording than 840 seconds (14 minutes)? That would be useful when shooting at 1920x1080 and to avoid the corrupted file after 74 minutes.
keep an eye here.

rgds
 
I can confirm that keyscan works again.

And then a little bug (and a feature request):
  • After I install the mod, (I haven't deleted the SD card, I've just unpacked it in case missing the Presets folder is related to what I'm going to say), at least the Enable Bluetooth option is ALWAYS unchecked. Could you make it persistent between updates? (Hey, you are even mimicking Samsung behaviour erasing ALL user presets with each FW update..!!!!. :-D:-D:-D)
  • The small bug. OK, I know I have to reactivate Bluetooth option... (not too much work, truth be said). I enable it and... Bluetooth is not activated, no "B" icon on the screen. I need a power off/on cycle to truly activate Bluetooth.
 
Last edited:
I just wanted to thank you for the great work with this! The silent shutter option made my NX500 so much more useful for time lapse since I now don't have to worry about mechanical wear and tear on the shutter. The focus stacking is also very useful. I've just had the NX500 for a few days but find it really impressive what this little thing can do.

The only trouble I have is that when using the timer to start time lapse shooting, the battery seems to drain even if the camera switches itself off right after you choose "Start Time Lapse". If I set the camera to start 4 or 5 hours from now, it's completely drained by the time it's supposed to start, so no shots are taken at all. I didn't test this before the mod so i don't know if this is a result of the mod or if it's an issue with the camera itself.
 
Not possible (currently) to override iFn on lens - it's not connected as a keyboard device to camera but communicates completely differently and directly with di-camera-app. I would not hold my breath for it.
A pity...

Nevertheless I really miss that feature. If you cannot code it on the i-Fn (currently, I keep my fingers crossed for future possibility), would you be able to code it on the Preview button? (My Preview button is currently assigned to the Minimum Shutter Speed function, but I don't mind loosing this direct access over my beloved AF mode switch).
 
Last edited:
Err, something is still wrong (but in a different way).

I've set 5 Frames and 2 seconds. And I get only 4 shots (and the last one is front focused).

Edited (added): What remains unchanged is the extra last focus movement. After the fourth shot has been taken, the camera moves to the correct Far position (apparently). So it really seems you "only" have to add one more picture to whatever counter you are using to control the number of taken shots.

(In addition, I thought you said that there was also a "Focus stacking in progress" (or similar) message. If that was the case, then there's another bug here. I don't get any message).

OTOH, I can confirm that my 5 frames / 2 seconds fully survive a power off/on cycle and a battery out/in one.
 
Last edited:
This is very impressive, a big thank you to all the contributors.

Is there a way to have longer batch recording than 840 seconds (14 minutes)? That would be useful when shooting at 1920x1080 and to avoid the corrupted file after 74 minutes.
yes, you can change it in the file "init.sh"
##############################################
#Set Recording-Batch-Length in seconds
systemctl set-environment rbl=840
##############################################


edit the file from the zip, set the desired length of seconds, and reinstall the full pack with the new file.
 
Last edited:
I just wanted to thank you for the great work with this! The silent shutter option made my NX500 so much more useful for time lapse since I now don't have to worry about mechanical wear and tear on the shutter. The focus stacking is also very useful. I've just had the NX500 for a few days but find it really impressive what this little thing can do.

The only trouble I have is that when using the timer to start time lapse shooting, the battery seems to drain even if the camera switches itself off right after you choose "Start Time Lapse". If I set the camera to start 4 or 5 hours from now, it's completely drained by the time it's supposed to start, so no shots are taken at all. I didn't test this before the mod so i don't know if this is a result of the mod or if it's an issue with the camera itself.
The mod won't affect the problem you describe with the built-in functions of the delayed start of time-lapse.

Focus-stack is the handiwork of Otto, who is also behind all the tools that make this mod-pack possible, and I'm sure we all appreciate his efforts : )
 
Just what I've said.

Please re-read this and this former posts in case you missed them.

In v1.57, when you engage TBBAF through the very first time you use AF-ON, you automatically switch to CAF (although the display continues saying SAF). WHY? Why do you forbid me to use TBBAF in SAF?

As I'd said, given the AF-ON: AF Start option within the stock software key mappings, TBBAF feature is just a matter of disabling AF on Half-Shutter. I really think you don't need to do ANYTHING on the AF-ON button.

More over, something doesn't work fine with OIS and your AF-ON modification. OIS should be engaged by either HS or AF-ON. If you don't use the mod feature this is what happens. But within the mod feature, AF-ON randomly engages OIS (HS always engages it). Sometimes it works, sometimes it doesn't.

(I've done the OIS test with my S 50-150 lens at 150 mm where noticing if OIS is engaged is pretty obvious within any handshake).

Finally, I don't like the way the feature is turned on. Basically because you can't turn it off (but with a power off/on cycle). Nevertheless, I suppose this is just an early implementation which will be modified in the future. I think this setting should go in the Settings section rather than in the Custom Func. one, with a tick appearance which allowed the user to switch it on/off whenever desired.
 
Just what I've said.

Please re-read this and this former posts in case you missed them.

In v1.57, when you engage TBBAF through the very first time you use AF-ON, you automatically switch to CAF (although the display continues saying SAF). WHY? Why do you forbid me to use TBBAF in SAF?

As I'd said, given the AF-ON: AF Start option within the stock software key mappings, TBBAF feature is just a matter of disabling AF on Half-Shutter. I really think you don't need to do ANYTHING on the AF-ON button.

More over, something doesn't work fine with OIS and your AF-ON modification. OIS should be engaged by either HS or AF-ON. If you don't use the mod feature this is what happens. But within the mod feature, AF-ON randomly engages OIS (HS always engages it). Sometimes it works, sometimes it doesn't.
(I've done the OIS test with my S 50-150 lens at 150 mm where noticing if OIS is engaged is pretty obvious within any handshake).

Finally, I don't like the way the feature is turned on.
It's optional, you don't have to turn it on. : )
Basically because you can't turn it off (but with a power off/on cycle).
you can use "reboot"
decided to use this way of ensuring if it causes problems, it will have a safe-restart
Nevertheless, I suppose this is just an early implementation which will be modified in the future. I think this setting should go in the Settings section rather than in the Custom Func. one, with a tick appearance which allowed the user to switch it on/off whenever desired.
It is not there for safety reasons.
If enabled as "a checkbox" it will auto-start each time, and if there are problems with it, you will be stuck.
 
Just what I've said.

Please re-read this and this former posts in case you missed them.

In v1.57, when you engage TBBAF through the very first time you use AF-ON, you automatically switch to CAF (although the display continues saying SAF). WHY? Why do you forbid me to use TBBAF in SAF?

As I'd said, given the AF-ON: AF Start option within the stock software key mappings, TBBAF feature is just a matter of disabling AF on Half-Shutter. I really think you don't need to do ANYTHING on the AF-ON button.

More over, something doesn't work fine with OIS and your AF-ON modification. OIS should be engaged by either HS or AF-ON. If you don't use the mod feature this is what happens. But within the mod feature, AF-ON randomly engages OIS (HS always engages it). Sometimes it works, sometimes it doesn't.

(I've done the OIS test with my S 50-150 lens at 150 mm where noticing if OIS is engaged is pretty obvious within any handshake).

Finally, I don't like the way the feature is turned on.
It's optional, you don't have to turn it on. : )
Sure, but I just don't infer why you've done it in this (apparently more complicated) way. I mean if you don't force CAF, the user can effectively select between CAF or SAF. And if you don't meddle with the AF-ON button behaviour there's less risk of something going wrong (like OIS not being engaged "ramdomly", as example).

So, could you explain why you are doing what you're doing? I only see benefits in my proposal, I don't see any drawbacks. Please, notice I don't say there aren't any drawbacks, just that I don't see them. It really appears a win-win decision (although I'm probably wrong somewhere).
Basically because you can't turn it off (but with a power off/on cycle).
you can use "reboot"
decided to use this way of ensuring if it causes problems, it will have a safe-restart
OK, I understand. But when the feature is fully tested for some time, I really think the elegant solution is using a tick setting.
Nevertheless, I suppose this is just an early implementation which will be modified in the future. I think this setting should go in the Settings section rather than in the Custom Func. one, with a tick appearance which allowed the user to switch it on/off whenever desired.
It is not there for safety reasons.
If enabled as "a checkbox" it will auto-start each time, and if there are problems with it, you will be stuck.
(Couldn't you just uncheck it in case of troubles? But as I said, I understand this way as a good preliminary "alpha" version).
 
Can't have disabled half press auto focus - that's the issue with samsung implementation. Right now, the only way to *emulate* nikon like bbaf is to :

1. Switch to caf when afon is pressed

2. Switch to mf when it's released

If you mask the S1 button (half press, you can mask buttons) the camera does not capture the image. If you don't mask it the camera will refocus on half press. It's dumb but it is what it is.

There might be another way to do it but there's no way for me to know or try on nx500.
 
Many thanks!!!

Now I understand why it works the way it works...

(A nasty hack if I ever saw one!)

If any of you ever discover how to kill the AF part of Half-Shutter, a good number of possibilities would open up... Let's hope.
 
Last edited:
v1.58m

Batch-recording updated.
you can set how long the video batches will be

added "Wake me UP"
sets camera in deep sleep for a number of minutes (set by you)
(Not sure if preset time-lapse on time will survive the waking up)

NX-KS-Readme

NX-KS download page

This version still uses the BT-Mod.
(can't seem to find an easy way to make the Hibernation-Mod work for now)
 

Keyboard shortcuts

Back
Top