Otto K

@sandro I created a small tool that shows a button with black background and white text at given position and size that enables one to have on screen "button" for REC or SHUTTER or whatever. 
You could use it as it is as a "black screen" (just set the text to " " and position to 0 0 and size to 720 480) and to start the time lapse. I do it often to preserve the battery (AMOLED uses almost nothing for black screen). To remove it from screen just press and hold it for 5+ seconds. I also made a separate tool for time lapse that can have black screen as well as black screen with small red frame counter (useful). It can also make short videos instead of photos (let's say 10s video every 2 minutes, etc). 

@sandro I created a small tool that shows a button with black background and white text at given position and size that enables one to have on screen "button" for REC or SHUTTER or whatever. 
You could use it as it is as a "black screen" (just set the text to " " and position to 0 0 and size to 720 480) and to start the time lapse. I do it often to preserve the battery (AMOLED uses almost nothing for black screen). To remove it from screen just press and hold it for 5+ seconds. I also made a separate tool for time lapse that can have black screen as well as black screen with small red frame counter (useful). It can also make short videos instead of photos (let's say 10s video every 2 minutes, etc). 

@sandro I created a small tool that shows a button with black background and white text at given position and size that enables one to have on screen "button" for REC or SHUTTER or whatever. 
You could use it as it is as a "black screen" (just set the text to " " and position to 0 0 and size to 720 480) and to start the time lapse. I do it often to preserve the battery (AMOLED uses almost nothing for black screen). To remove it from screen just press and hold it for 5+ seconds. I also made a separate tool for time lapse that can have black screen as well as black screen with small red frame counter (useful). It can also make short videos instead of photos (let's say 10s video every 2 minutes, etc). 

Come on people, give the guy a brake! Let him finish his personal project, and then we can propose improvements or be critical in ergonomics and IQ.
In any way, Luca invests his personal time and money, and it is truly admirable what he has achieved so far (something that even metabones didn't touch). I believe that AFTER the product is finished there are a lot of experimenting and testing to check the real possibilities and improvements of the adapter. I hope someone will take it from there and add electronics, even if it takes a while arduino board on a box somewhere!

I love the "Gold Ring" on Samsung NX1... It will be a very long wedding!

I disagree, dude. I've got a pretty thriving business that's equal parts stills and video and the NX1 and NX500 do everything I need and more stills-wise. Fantastic dynamic range, high mp for great detail, wonderful adaptability for vintage lenses... Honestly what more do you need? This new speedbooster will only make things better, I can't wait to see how different some of my lenses look wider and a stop faster.

@kidzrevil Can't speak for others but I have nx500 so no evf from me
Great work Luca, I tried something similar (but much more primitive) with m42 a long time ago but I was unable to position the added elements precisely enough and got mostly useless results - your results are very positive!
Regarding canon vs nikon - yes it is true that due to longer flange straight adapter will not work, but let's wait and see how much of the space is actually used by this adapter - it might be doable to shave a millimeter or there and get canon lenses to work. 

FWIW, we seem to now have a method to make bitrate mods permanent (in hibernation image) so independent of Bluetooth and similar. But this currently applies only to bitrate mods (but should apply to 2.5k on NX500 as well). Other mods still depend on Bluetooth. We are all working on further improvements. 
See here for more information 
https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Permanent_bitrate_mods.md

FWIW, we seem to now have a method to make bitrate mods permanent (in hibernation image) so independent of Bluetooth and similar. But this currently applies only to bitrate mods (but should apply to 2.5k on NX500 as well). Other mods still depend on Bluetooth. We are all working on further improvements. 
See here for more information 
https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Permanent_bitrate_mods.md

FWIW, we seem to now have a method to make bitrate mods permanent (in hibernation image) so independent of Bluetooth and similar. But this currently applies only to bitrate mods (but should apply to 2.5k on NX500 as well). Other mods still depend on Bluetooth. We are all working on further improvements. 
See here for more information 
https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Permanent_bitrate_mods.md

@vasile is correct - if you are not sure what you are doing - don't do it. Added a large warning to github. 

FWIW, we seem to now have a method to make bitrate mods permanent (in hibernation image) so independent of Bluetooth and similar. But this currently applies only to bitrate mods (but should apply to 2.5k on NX500 as well). Other mods still depend on Bluetooth. We are all working on further improvements. 
See here for more information 
https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Permanent_bitrate_mods.md

No reason why it wouldn't, but I have no way to test it on NX1. 

@vasile is correct - if you are not sure what you are doing - don't do it. Added a large warning to github. 

@vasile is correct - if you are not sure what you are doing - don't do it. Added a large warning to github. 

FWIW, we seem to now have a method to make bitrate mods permanent (in hibernation image) so independent of Bluetooth and similar. But this currently applies only to bitrate mods (but should apply to 2.5k on NX500 as well). Other mods still depend on Bluetooth. We are all working on further improvements. 
See here for more information 
https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Permanent_bitrate_mods.md

They should apply to NX1 but involve EXTREMELY dangerous changes. DO NOT attempt to do them on your own unless you know what you are doing - a mistake WILL require you to send the camera for service.
Why? Because you change a library that is required by di-camera-app. For 2.5K you also change the di-camera-app itself.
A mistake and di-camera-app will crash leaving you without user interface. So just don't. Wait a bit please

FWIW, we seem to now have a method to make bitrate mods permanent (in hibernation image) so independent of Bluetooth and similar. But this currently applies only to bitrate mods (but should apply to 2.5k on NX500 as well). Other mods still depend on Bluetooth. We are all working on further improvements. 
See here for more information 
https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Permanent_bitrate_mods.md

FWIW, we seem to now have a method to make bitrate mods permanent (in hibernation image) so independent of Bluetooth and similar. But this currently applies only to bitrate mods (but should apply to 2.5k on NX500 as well). Other mods still depend on Bluetooth. We are all working on further improvements. 
See here for more information 
https://github.com/ottokiksmaler/nx500_nx1_modding/blob/master/Permanent_bitrate_mods.md

All done ... thanks again for your work on this !! @vasile
BTW ... quoting on this board seems to be broken. I tried to quote Vasile's remark above and instead it quotes my comment 4-5 posts above @Andrew Reid
 

@kidzrevil they didn't close the hole we are using, mods work fine, but due to changes in firmware the bitrate hacks don't work (as they work with messing with memory locations of already running process, etc).
Enabling 2.5k on nx500 works when adapted to new memory locations (already done by Kino Seed). 
You just have to wait and see what happens, but if you need higher bitrates don't update yet. 

@kidzrevil they didn't close the hole we are using, mods work fine, but due to changes in firmware the bitrate hacks don't work (as they work with messing with memory locations of already running process, etc).
Enabling 2.5k on nx500 works when adapted to new memory locations (already done by Kino Seed). 
You just have to wait and see what happens, but if you need higher bitrates don't update yet. 

@kidzrevil they didn't close the hole we are using, mods work fine, but due to changes in firmware the bitrate hacks don't work (as they work with messing with memory locations of already running process, etc).
Enabling 2.5k on nx500 works when adapted to new memory locations (already done by Kino Seed). 
You just have to wait and see what happens, but if you need higher bitrates don't update yet. 

It's here (this link contains all the versions and commit data) 
https://github.com/ottokiksmaler/nx500_nx1_modding/commits/master/NX-KS.zip

It's here (this link contains all the versions and commit data) 
https://github.com/ottokiksmaler/nx500_nx1_modding/commits/master/NX-KS.zip