Notices

Originally Posted by marmistrz

YOu can attatch gdb: run camera-ui and then gdb attatch $pid
this will give you some backtrace

Originally Posted by Estel

Re bugs, and my attempt to collect the and report *proper* way to CSSU bugteam:

I tried it on two devices, one my "usual" everyday one, (thumb), and one freshly flashed (inc. emmc vanilla, which shouldn't be relevant). The 2nd device used cssu-thumb, later I reflashed it to stock again and used cssu-testing, then repeated tests.

On all three devices, I got positive results (aka bugs present) with ALL things reported, at some point, in this thread - including, but not limited to:

*autofocus suddenly becoming slow

* autofocus getting stuck at focusing only up to some random value (for example, few-centimeters - no matter what scene we point it at. When it get's stuck, it clearly *changes* focus, but always device to end up at the same value. Interestingly, value changes between "stuck" accidents, but during same "accident", remains the same.

*camera-ui getting frozen during saving of video, resulting in broken .mp4 container.

*camera-ui crashing randomly

*camera-ui suddenly starting to fail saving most of pictures took

*camera-ui suddenly showing black viewfinder (with all UI elements as they should be, though) and seeming like it "lost contact" with camera hardware (pressing autofocus doesn't move lens, etc) - until restart

*just as above, but with addition of camera-ui window getting clones, and showing proper viewfinder in that clone

...etc. The problem is, that ALL of those issues are not clearly reproducible - they just happen, quite often (especially during longer photo or recording runs - think few hours), if anyone cares to search for them. (I haven't found similar problems in stock camera-ui, when trying to replicate them there).

Now, I wasn't able to find ANY way of getting meaningful logs/debug content from camera-ui. No one who I asked about - including this thread, camera-ui2 thread, and CSSU bugtracker (inside camera-ui reported bug) was able to point me how to get meaningful logs/debug info from camera-ui. I assume that it doesn't have ANY, accessible to average Joe.

This result in complete inability to post a meaningful bug report, that would be anything more than things commented as rants.

Due to this, I'm "officially" giving up on attempts to gather those bugs and report them to bugtracker - at least until some sane way of getting debug output is introduced into camera-ui. If someone more knowledgeable is willing to pick it up, be my guest - it's not a full "rage quit", it's just fact that spending a total of ~90 hours of chasing those bugs, experiencing them, but being unable to report them in a way meaningful to maintainers is too frustrating.

Maybe things like attaching gdb or whatsnot would help, but I have no clue about such things ATM (to the point that I don't even know if it's relevant to this case), and I already spent too much time on this, getting only "worksforme and my girlfriend" answers - despite that reports about camera-ui2 being substandard are numerous (and the links just show a small bite of them).

For now, I'm using a simple hack to have camera-ui (vanilla) for everyday functionality, and run camera-ui2 manually, when I need higher quality video recording (and it's not so important, so I don't fear that it might get corrupted at saving), or some nice functionalities that camera-ui2 offers, like manual focus.

/Estel

Originally Posted by freemangordon

This is overcomplicated and not needed.

Estel (and the others), there is a very simple way to proviide useful information - install sp-rich-core along with syslog. It is my fault if I didn't say that earlier (though I think I did, but anyway). As soon as there is a crash, a coredump (and other useful things) is created and put in an archive to be provided to the developer(s).

Also, please install camera-ui2 from cssu-devel, I fixed what I think is a nasty "use after free" bug, which could lead to lots of various problems, including those intermittent faults you describe.

Originally Posted by UJKU

Can you share the simple hack that you made for using camraui2 and stock camera

Originally Posted by Estel

...
BTW - the rich coredump will help if I reproduce crash, but still, how to properly get debug info for (much more common than crashes) various strange non-crashing issues, if they would be still present, despite -devel update? Maybe some logging/output functionality could be provided to camera-ui, in the form of update? Unless there are better options, of course.

Originally Posted by freemangordon

Did anyone manage to get a coredump of a crashing camera-ui2?

Originally Posted by marmistrz

I'm not using the N900 atm due to the battery life problems, if I solve it, I'll give a try.

Anyway, I used to have sp-rich-core installed, but despite the (core dumped) messages no file was created in MyDocs. How to properly setup and configure sp-rich-core?