Active Topics

 


Reply
Thread Tools
Posts: 1,746 | Thanked: 1,832 times | Joined on Dec 2010
#91
i attempted that no luck, this error occurs

Using Wayland-EGL
[W] QQmlImportDatabase::registerPluginTypes:1875 - Module 'QtCamera' does not contain a module identifier directive - it cannot be protected from external registrations.
[W] DeclarativeWindow:eclarativeWindow:82 - No default allowed orientations defined. Check your device configuration!
[W] unknown:84 - qrc:/qml/FocusReticle.qml:84: TypeError: Cannot read property 'x' of undefined
[W] QtCamModePrivate::setPreviewSize:219 - Cannot set preview caps. Preview not supported
[D] LocalSensorManagerInterface::loadPluginFinished:92 - void LocalSensorManagerInterface::loadPluginFinished(QD BusPendingCallWatcher*) "Unexpected reply signature: got "i", expected "b""
[W] QtCamViewfinderRendererNemo:aint:93 - renderer not started yet
[W] QtCamModePrivate::setPreviewSize:219 - Cannot set preview caps. Preview not supported
[W] QtCamImageModePrivate::applyFastCapture:54 - applyFastCapture: not supported
[W] QtCamModePrivate::setPreviewSize:219 - Cannot set preview caps. Preview not supported
[W] QtCamImageModePrivate::applyFastCapture:54 - applyFastCapture: not supported
[W] QtCamDevice::start:207 - Failed to start camera pipeline
[D] showError:227 - Error: Failed to start camera. Please restart the application.
edit:

I ended up removing the stock app and installing the one from warehouse, still no luck

after closing the program this error:

(harbour-cameraplus:5113): GStreamer-CRITICAL **:
Trying to dispose element audio-capsfilter, but it is in READY instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.


(harbour-cameraplus:5113): GStreamer-CRITICAL **:
Trying to dispose element audio-volume, but it is in READY instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.


(harbour-cameraplus:5113): GStreamer-CRITICAL **:
Trying to dispose element viewfinderbin-queue, but it is in READY instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.


(harbour-cameraplus:5113): GStreamer-CRITICAL **:
Trying to dispose element image-encodebin, but it is in READY instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.


(harbour-cameraplus:5113): GStreamer-CRITICAL **:
Trying to dispose element viewfinderbin-capsfilter, but it is in READY instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.


(harbour-cameraplus:5113): GStreamer-CRITICAL **:
Trying to dispose element imagebin-capsfilter, but it is in READY instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.


(harbour-cameraplus:5113): GStreamer-CRITICAL **:
Trying to dispose element videobin-capsfilter, but it is in READY instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.


(harbour-cameraplus:5113): GStreamer-CRITICAL **:
Trying to dispose element vf-bin, but it is in READY instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.

[W] QObject::startTimer:1519 - QObject::startTimer: Timers can only be used with threads started with QThread
[1]+ Killed harbour-cameraplus

Last edited by m4r0v3r; 2015-05-10 at 16:12.
 
BluesLee's Avatar
Posts: 411 | Thanked: 1,105 times | Joined on Jan 2010 @ Europe
#92
@m4r0v3r: I fear you are running in different issues now as the default version of cameraplus is not the same as the one on openrepos. I would disable MSameer's repo, remove cameraplus and re-install the default cameraplus. I reproduced your first issues but i was able to get cameraplus running again by editing the mentioned configuration file.

Try
Code:
pkcon install harbour-cameraplus
This will install
Code:
http://repo.merproject.org/obs/home:/sledge:/experimental:/gstdroid/sailfish_latest_armv7hl/armv7hl/harbour-cameraplus-0.0.29+droidmedia.20150504202426.90.g1a753a9-10.13.1.jolla.armv7hl.rpm

Last edited by BluesLee; 2015-05-10 at 16:56.
 
Posts: 1,746 | Thanked: 1,832 times | Joined on Dec 2010
#93
would I have to extract cameraplus from the zip to get it running again? and the same issues plagued me both the default version and MSameers version,

think ama just go for a clean flash, when I copied over from the zip it started to complain that a Qt module was missing.

Last edited by m4r0v3r; 2015-05-10 at 16:49.
 
Posts: 1,746 | Thanked: 1,832 times | Joined on Dec 2010
#94
another bug is that my notification dont make the normal sounds which should be the messagetone, instead they make the noise when the device is unlocked and the message application is in the background I think.

that small beep, even when the device is locked
 
Posts: 1,746 | Thanked: 1,832 times | Joined on Dec 2010
#95
i installed emumaster, funnily enough it ran snes mario all star at 21fps. something is clearly up with the device when the Jolla would get a full 50-60fps
 
Posts: 738 | Thanked: 819 times | Joined on Jan 2012 @ Berlin
#96
can you test mumpen64 and mario kart/wave race how good it work with the analog stick?
__________________
www.sailfishmods.de
 
Posts: 1,746 | Thanked: 1,832 times | Joined on Dec 2010
#97
has that even been ported?
 
Posts: 738 | Thanked: 819 times | Joined on Jan 2012 @ Berlin
#98
sure, check Warehouse/openrepos.

you can start the game with this command line:
Code:
mupen64plus /path/to/the/rom/xxxx.z64
__________________
www.sailfishmods.de
 
Posts: 1,746 | Thanked: 1,832 times | Joined on Dec 2010
#99
Originally Posted by cvp View Post
sure, check Warehouse/openrepos.

you can start the game with this command line:
Code:
mupen64plus /path/to/the/rom/xxxx.z64
well it runs, but there isnt any controls, and the screen is portrait in the top left for less than half the screen. So I assume needs more work lol
 
Posts: 307 | Thanked: 488 times | Joined on Sep 2010 @ USA around Chicago
#100
Originally Posted by m4r0v3r View Post
well it runs, but there isnt any controls, and the screen is portrait in the top left for less than half the screen. So I assume needs more work lol
Well I started playing with the config file, /home/nemo/.config/mupen64plus/mupen64plus.cfg

Increased resolution:
[Video-General]
# Use fullscreen mode if True, or windowed mode if False
Fullscreen = True
# Width of output window or fullscreen width
ScreenWidth = 1080
# Height of output window or fullscreen height
ScreenHeight = 1920


I still haven't figured out how to change resolution to landscape or enable control. There is a lot more settings in the configuration file, if you want to play with it.
__________________
Apps for iPhone & iPad
Malayalam Keyboard for iPhoneTelugu Keyboard for iPhoneGujarati Keyboard for iPhone
 
Reply


 
Forum Jump


All times are GMT. The time now is 07:17.