Is it possible to downgrade the fw? If so, I'll update and try it out
Yes, it is very easy to upgrade and downgrade the Canon firmware. I have both the 1.1.4 and 1.1.5 Canon firmware update on a spare card. To make it really easy for testers I uploaded the firmware to my bitbucket download area.
Incorporated pull request #842 to fix Autoexposure module. Also merged in latest unified to update the changes made to the 700D.114 stubs.S file.
Found out there's a problem with Full resolution silent pictures. It hangs after the first shot on both DNG and MLV. Simple silent is working fine. No logs saved. Downgraded to 114 and it is fine. Darn it, I'm pretty sure this used to work fine. Maybe one of my stubs is off?
Found the problem using check-stubs.py. Somehow the is_taskid_valid changed. FRSP works fine now.
The installer FIR does not use is_taskid_valid, so I don't see any reason to compile a new one. Don't remember adding any new features to it anyway.
I must admit I still haven't installed 1.1.5 yet, but some weeks ago I was working on a project with two 700D's, one of them was on 1.1.5 and one on 1.1.4, both with magiclantern installed and quite the same settings. What I noticed is that the one on 1.1.5 got really hot and the battery drained at least twice as quick as on the one on 1.1.4. Also I think we had two crashes on the 1.1.5 camera while the 1.1.4 had none.
Have you also experienced the battery drain issue? Any ideas what is causing it?
I haven't noticed those issues but now that a1ex is suggesting merging 700D.115 I'm finding all sorts of problems. It would be good to get crash logs and some more details about the heat and battery drain.
If you have two cameras with different firmware versions, but similar settings and same workload, you can check the CPU usage - that should be a predictor for battery drain.
In particular, the following will affect the battery life, so double-check them when comparing:
LiveView usage (the biggest impact)
FPS (whether in Canon menu or ML override)
LCD brightness (minor impact)
Display usage in photo mode (turning it off will make a difference)
CPU-based overlays in LiveView (e.g. RGB or RAW-based zebras, focus peaking, magic zoom)
Nice side project: hunt for ADCs in the firmware - one of them might be the battery voltage.
I did a test using the same camera on different firmware versions and the results of the CPU usage was pretty much identical. Idling around 55-65%. I've also been running some stress tests on 1.1.5 and when I came across an issue I noted it and reproduced it on 1.1.4. Note that this is a very minor firmware update and there are only a few significant changes.
Looks like the only stubs that were really changed were:
So, if you bypass the signature check, you'll be able to load the 1.1.4 build on 1.1.5, and most features, except for those that depend on the above stubs, will probably work.
The hg rename command didn't seem to work - the 1.1.4 files appear deleted and the 1.1.5 ones appear added from scratch, with no relationship between them. This did work in the first changeset, but probably this info was lost somewhere along the way. Looking into it.
edit: it's fine, it was just the GUI frontend not showing things well; hg diff --git shows the renames well.