henning Posted May 14 Share #21 Posted May 14 Advertisement (gone after registration) That is a powerful firmware update. Some minor improvements to the camera, but a significant update to the lens! 6 Link to post Share on other sites More sharing options...
Advertisement Posted May 14 Posted May 14 Hi henning, Take a look here Firmware 2.2.2 and my 35mm Summicron-M f/2 V.4. I'm sure you'll find what you were looking for!
poli Posted May 15 Share #22 Posted May 15 On 5/14/2025 at 12:15 AM, louiedi said: No I cannot select the Summicron manually. I can only select OFF or AUTO. Having the exact same problem with my m11-d and summicron KOB. Bit annoying. Link to post Share on other sites More sharing options...
poli Posted May 15 Share #23 Posted May 15 i stand corrected. Rebooted the camera, took lens on and off and now I can select the Summicron. 1 Link to post Share on other sites More sharing options...
Stef63 Posted May 15 Share #24 Posted May 15 Same here. I also seem to have received a hardware update on my 35 cron iv to a 35 noctilux. 1 Link to post Share on other sites More sharing options...
lct Posted May 15 Share #25 Posted May 15 How does the 35/2 v4 render with the 35/1.2 lens profile? Any differently? Just curious. Link to post Share on other sites More sharing options...
hdmesa Posted May 15 Share #26 Posted May 15 On 5/13/2025 at 3:29 PM, louiedi said: I installed Firmware 2.2.2 into my Leica M11 and M11 Mono. Everything seemed to be working fine until I attached my 35mm Summicron-M f/2 V4. My Lens Detection on both cameras now read my 35mm version 4 Summicron as a "1.2 35mm" My f/2 doesn't even have 6 bit coding. When I transfer a photo taken with my f/2 Summicron to the app FOTOS my photo lists my f/2 Summicron as a NOCTILUX-M 1:1.2/35 ASPH... 11 hours ago, poli said: Having the exact same problem with my m11-d and summicron KOB. Bit annoying... ...i stand corrected. Rebooted the camera, took lens on and off and now I can select the Summicron. 1 hour ago, Stef63 said: Same here. I also seem to have received a hardware update on my 35 cron iv to a 35 noctilux. Have to ask, have you all done the factory reset after updating to 2.2.2 per the firmware instructions? 1 Link to post Share on other sites More sharing options...
Stef63 Posted May 15 Share #27 Posted May 15 Advertisement (gone after registration) 46 minutes ago, hdmesa said: Have to ask, have you all done the factory reset after updating to 2.2.2 per the firmware instructions? I did not do a reset. Link to post Share on other sites More sharing options...
poli Posted May 15 Share #28 Posted May 15 no reset Link to post Share on other sites More sharing options...
don daniel Posted May 15 Share #29 Posted May 15 I am really glad my Summicron 35mm IV ist 6-bit-coded. But now I am afraid of updating, too. 😀 Link to post Share on other sites More sharing options...
pedaes Posted May 15 Share #30 Posted May 15 34 minutes ago, poli said: no reset 14 minutes ago, don daniel said: I am afraid of updating, too Just follow Instructions and re-set camera after updating f/w. Link to post Share on other sites More sharing options...
Stef63 Posted May 17 Share #31 Posted May 17 On 5/15/2025 at 11:15 PM, pedaes said: Just follow Instructions and re-set camera after updating f/w. Did it work for you? Assuming you have a v4. Link to post Share on other sites More sharing options...
lct Posted May 17 Share #32 Posted May 17 I don't see any problem if the 35/2 v4 is coded. It will be recognized as such by the camera since there is no screw head in the way of the 6-bit sensor anymore. Link to post Share on other sites More sharing options...
geotrupede Posted May 17 Share #33 Posted May 17 "the king of bokeh" code, about to be dethroned. I managed to code it in the past with a sharpener, colour faded off with the years so now that I could not be bothered by the coding needs, I have a reason to try once more. Same issue on M11 vanilla 35f2 becomes 1.2 and no option to say otherwise. Agree that this on/off should work as one imagines a switch... G> Link to post Share on other sites More sharing options...
lct Posted May 17 Share #34 Posted May 17 35/2 v4 flange coded and uncoded Welcome, dear visitor! As registered member you'd see an image here… Simply register for free here – We are always happy to welcome new members! 2 Link to post Share on other sites Simply register for free here – We are always happy to welcome new members! ' data-webShareUrl='https://www.l-camera-forum.com/topic/421237-firmware-222-and-my-35mm-summicron-m-f2-v4/?do=findComment&comment=5803579'>More sharing options...
Crem Posted May 20 Share #35 Posted May 20 On 5/17/2025 at 12:27 PM, lct said: 35/2 v4 flange coded and uncoded Welcome, dear visitor! As registered member you'd see an image here… Simply register for free here – We are always happy to welcome new members! Possibly silly question, but does it matter that the coded flange has one less screw holding things together? I assume not or I would have heard about it by now. Is that an official Leica flange or 3rd party? If/when I finally find a mint v4 I'd like to get it coded. Link to post Share on other sites More sharing options...
lct Posted May 20 Share #36 Posted May 20 24 minutes ago, Crem said: Possibly silly question, but does it matter that the coded flange has one less screw holding things together? I assume not or I would have heard about it by now. Is that an official Leica flange or 3rd party? If/when I finally find a mint v4 I'd like to get it coded. I got the lens 2nd hand but i guess it is an official 6-bit code as the 35/2 v4 belongs to lenses that can be coded by Leica. 1 Link to post Share on other sites More sharing options...
Stef63 Posted May 21 Share #37 Posted May 21 Problem seems to be solved in 2.2.3. My uncoded 35 v4 is detected as ... uncoded. 2 Link to post Share on other sites More sharing options...
pedaes Posted May 21 Share #38 Posted May 21 (edited) 42 minutes ago, Stef63 said: Problem seems to be solved in 2.2.3. My uncoded 35 v4 is detected as ... uncoded. So you are the real cause of the bug fix😃 Edited May 21 by pedaes 2 Link to post Share on other sites More sharing options...
louiedi Posted May 22 Author Share #39 Posted May 22 Firmware 2.2.3 has fixed the bug. I can, once again, have my KOB as KOB. Now where was I? Link to post Share on other sites More sharing options...
lct Posted May 22 Share #40 Posted May 22 10 hours ago, louiedi said: Firmware 2.2.3 has fixed the bug. I can, once again, have my KOB as KOB. Now where was I? You were explaining that your Summicron 35/2 v4 is not coded if i remember well. The camera should then display "Uncoded" unless you entered the profile of the lens manually in the meantime. Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now