Building the camera app for volla phone

[ubports-user]

Hello there,

because the camera on volla phone stopped to work after installing updates (it just crashes after i displays the splash), I decided to install older versions, because I thought it might be caused by the patches made to the camera app.

So I have build the following versions via clickable:

camera-app-v3.0.1.765
camera-app-v3.1.2

Both versions still crash.

I wonder about the following messages produces by clickable --debug:

Framework in manifest is "ubuntu-sdk-15.04.4", Clickable expected "ubuntu-sdk-16.04.5".

How do I switch the framwork which clickable uses? I would like to compile with the framework specified in the manifest. The clickable documentation does not tell me how to switch to older framework.

Then there is another message:

- functional:qt_qml_import_versions_framework
	Files contain QML imports too new for frameowrk used: SlideshowView.qml,FocusRing.qml,ViewFinderOverlay.qml,ShootButton.qml,ViewFinderView.qml,ProcessingFeedback.qml,Information.qml,PhotoEditorLoader.qml,ViewFinderExportConfirmation.qml,ViewFinderOverlayLoader.qml,VideoReview.qml,GalleryViewLoader.qml,OptionsOverlay.qml,OverlayBlur.qml,AdvancedOptions.qml,PictureReview.qml,StopWatch.qml,GalleryView.qml,PhotoRollHint.qml,OptionValueButton.qml,ResponsiveGridView.qml,BottomEdgeIndicators.qml,PhotogridView.qml,OptionButton.qml,NoSpaceHint.qml,camera-app.qml,GalleryViewHeader.qml,ViewFinderGeometry.qml,UnableShareDialog.qml,SharePopover.qml,DeleteDialog.qml,IconButton.qml,CircleButton.qml,ThinSliderStyle.qml,ZoomControl.qml

OK, I do not understand the problem here, just wanted to mention this.

Then another log message regarding app.armor:

 - security:policy_groups_safe:camera:picture_files
	(NEEDS REVIEW) reserved policy group 'picture_files': vetted applications only
 - security:policy_groups_safe:camera:video_files
	(NEEDS REVIEW) reserved policy group 'video_files': vetted applications only
 - security:redflag_fields:camera.apparmor
	found redflagged fields (needs human review): read_path

I'm not sure if that problem maybe is enough to stop app.armor to not run the at all via clickable --debug?

Sorry for beeing not so verbose on this topic, I'm very new to the system and environment - searching for some inputs, hints, etc. how to get some grab on the topic.

[saveurlinux]

The last version is 3.2.3 maybe it solve your problem.
I've got volla phone as well and camera app works very well.

[TotalSonic]

The camera app has been working for me on Volla with no problems - on both OTA17 Stable and RC channels. I would suggest resetting or reinstalling to try and fix this

Best regards,
Steve Berson

[ubports-user]

Thank you very much for your quick replies.

Hard-Reset is an viable option then. However, my questions remain valid and maybe I can pinpoint the problem. In /var/log I can not see any crash dumps, is there some other location for logs like kern.log or is there some tool like ltrace?

After all, I think the system should at least create some log entry when an application is shut down for whatever reason.

[TotalSonic]

@ubports-user - you can install the Logviewer app from the Open Store to view more log info.

Best regards,
Steve Berson

[ubports-user]

@totalsonic said in Building the camera app for volla phone:

@ubports-user - you can install the Logviewer app from the Open Store to view more log info.

OK, but I do not see anything related to the camera there.

However, I had a look into the system settings app and within the section "Application Authorisation" I see an section for camera, but 0 apps are configured to have camera access in that section. When I look into UT Tweak Tool, the camera app is described to have access to the camera.
I start to believe app.armor is maybe the right place to start searching for the problem, will dig into that