Quote from: LDBenjamin on 10 / March / 2018, 21:32:33Tried it again and it's stable, no blinking.The blinking is unfortunately normal - especially when the camera is in shooting mode rather than playback mode. It's a long story.Now that you seem to have the install process worked out, here's a build with everything enabled (other than the nagging expired message). Let's see how that goes?
Tried it again and it's stable, no blinking.
Please let me know what I should do to test this.
Quote from: LDBenjamin on 10 / March / 2018, 22:19:09Please let me know what I should do to test this.AFAIK, we have never made a definitive list for testing every thing that a porter sets in the sub/<fw> directories. In general, the first firmware version of a new port gets some high level functionality tests - with a bias towards things that are hard to find or have caused problems. Just getting CHDK to load and display menus correctly is a big step all by itself. Subsequent additions of different firmware versions for any released port get a bit of a free pass. If they appear to work then, based on the original port being good, we mostly assume they are okay until anyone reports otherwise .So the big things I'd suggest checking are :RAW/DNG images - take some shot with DNG enabled and assure yourself that the DNG images actually look like uncorrected versions of the related JPGUSB remote - enable this and just use a regular USB cable plugged into a spared charger or computer port to trigger it and assure it's workingexposure overrides in the Enhanced Photo Operations menu - set both Tv, Sv, & Av and make sure the resulting image change appropriately when you change the valuesset a long exposure time (30 seconds) and then see if dark frame subtraction control works ( if not, it will take 60 seconds to complete a 30 second exposure)try out the edge overlay, historgram, and zebra functions and make sure they seem to work (i.e. usable images on the camera's LCD)try running some scripts - there are four simple ones included with the CHDK installation file and hundreds more online at places like this play with anything else that tweaks your interestThere is learning curve here so feel free to post questions. If all else fails - RTFM. And tell us how you did - if the 1.01b build passes the above list of tests without crashing then we will release it for distribution in the autobuild.
Firmware Update Method works well, photo are saved.
Using bootable sd card method, after shooting photo, camera display "memory card error" No photos are saved
Well, build 5000 works on both my G16's. Did you try low level formatting the card and start from scratch using STICK or CHIMP?
low level formatted by G16 && STICK, but same thing (memory card error)
@reyalp : will you take a look ?
I disabled FI2 in the autobuild. The two things that are known to fail on most digic 6 cameras are using hybrid auto mode, and the orientation sensor freaking out in playback mode. If these do not occur on G16, I guess we can re-enable FI2 loading.
Regarding the card error on boot, this sounds like the sort of card-dependent initialization issues we've seen on other cameras.
Started by waterwingz « 1 2 ... 54 55 » DryOS Development
Started by pittguy578 General Help and Assistance on using CHDK stable releases
Started by Christian72D General Help and Assistance on using CHDK stable releases
Started by vga71 Script Writing
Started by Fortesque General Discussion and Assistance
