Congrats! 
Let’s see what works and what not, and then I’ll prepare an image with your changes, when I have the time.
3 Likes
Trank you very much for your help with launching tucana fw on toco!
I wiil test what works and what not, and definitely let you known.
In the previous post, in the “About product” screenshot, you can see one IMEI, but my device is a dual SIM device. There should be two IMEI’s.
It comes from tucana, right? Your device have only one SIM card?
How it is possible to fix?
Updated: Fixed, maybe restart helped
2 Likes
TEST PLAN:
Core functionality:
Display/Touch - Works
Wifi - Works
GSM Calls - Not tested yet
Cellular Data - not tested yet
Sound - not tested yet
Camera Pics - not tested yet
Video playback - not tested yet
More features that make the port complete:
Camera recording - not tested yet
Bluetooth - not tested yet
Vibration - not tested yet
Multiple cameras - not tested yet
MTP - not tested yet
Fingerprint on Display - not tested yet
Double-tap to wake - Works
Sensors:
GPS - not tested yet
Compass - not tested yet
Accelerometer - not tested yet
Proximity - not tested yet
Light - not tested yet
NFC - not tested yet
2 Likes
This is very bad news as it is the proeminent change between the devices. You have a file like this in /etc, named droid-config-t5/sparse/etc/dconf/db/vendor.d/jolla-camera-hw.txt at master · sailfish-on-fxtecpro1/droid-config-t5 · GitHub - maybe try to add some imageResolution that is matching what toco's camera has natively (just the
[apps/jolla-camera/primary/image]
imageResolution='4000x3000'
part). Then dconf update as root.
About multi SIM: I do have 2 IMEIs on tucana. I think it works accidentally. For example, in this file droid-config-tucana/sparse/usr/share/csd/settings.d/hw-settings.ini at master · sailfishos-on-tucana/droid-config-tucana · GitHub (just as before, ignore sparse/ as that your root or / folder) there’s SIM=1, maybe it should be 2.
Also, do you have this file
# cat /etc/ofono/ril_subscription.d/dual-sim.conf
[ril_1]
transport=binder:name=slot2
name=slot2
ecclistFile=/run/ofono/ril.ecclist1
2 Likes
Camera will produce many logs. Prepare two terminals with unlimited back scroll…
First, rm -rf ~/.cache/gstreamer-1.0/ (or /home/defaultuser/.cache/gstreamer-1.0). According to mal that test image shows up when the gstreamer droid plugin is already blacklisted. Now to find out how it gets blacklisted:
On one terminal, telnet or ssh (if telnet, su - defaultuser to switch away from root) and run GST_DEBUG=3 jolla-camera,
While in the other (actually start this first) you just run # logcat as root (devel-su if from ssh).
The output from logcat will be so large that you’ll probably not be able to use a paste service, a file hosting might be needed 
2 Likes
Currently the file jolla-camera-hw.txt coitants only one line:
~ # cat /etc/dconf/db/vendor.d/jolla-camera-hw.txt
'# this file here to allow patching for five cameras
So, I have added:
~ # cat /etc/dconf/db/vendor.d/jolla-camera-hw.txt
'# this file here to allow patching for five cameras
[apps/jolla-camera/primary/image]
imageResolution=‘4000x3000’
When I execute command: dconf update, then I got error “(dconf:2182): GLib-GIO-CRITICAL **: 09:35:01.082: g_dbus_connection_emit_signal: assertion ‘object_path != NULL && g_variant_is_object_path (object_path)’ failed”
Maybe here something not linked correctly? product_services?
'# df -h
Yes please fix the /product_services link if you find where it should point to.
Also, the jolla-camera-hw.txt resolution should have a native resolution for your device’s camera.
Could you please share some information, what files/folders here should be in side? Maybe possible to share a screenshot from tucana?
Sorry that was misleading - it is also a broken link on my device.
I have changed the file metadata.mount option from
What=/dev/block/by-name/metadata
to
What=/dev/sda19
And now I have mounted /metadata
Filesystem Size Used Available Use% Mounted on
/dev/sda19 11.5M 76.0K 10.9M 1% /metadata
What mounting points should be mounted/nessesarry?
Not sure you’re missing anything, maybe just grab logcat and GST_DEBUG=3 jolla-camera output as described a couple of posts above?
I will try to get the logs.
When I execute command: dconf update, then I got error “(dconf:2182): GLib-GIO-CRITICAL **: 09:35:01.082: g_dbus_connection_emit_signal: assertion ‘object_path != NULL && g_variant_is_object_path (object_path)’ failed”
How I can fix it?
I have added:
~ # cat /etc/dconf/db/vendor.d/jolla-camera-hw.txt
'# this file here to allow patching for five cameras
[apps/jolla-camera/primary/image]
imageResolution=‘4000x3000’
But cant activate.
Second issue, On incomming call phone doesn’t play a ringtone, but I can play any ringtone in menu. (Sound works) What I can check for fixing the problem?
1 Like
That may be benign, I think you can ignore that.
Are you sure this is a resolution your camera supports? I have just given it as an example.
At least remove rm -rf ~/.cache/gstreamer-1.0/ before trying again, as gst droid is blacklisted by gstreamer already.
Doesn’t sound right - but I have not experienced this before. So Ringtone volume is > 0? (curious: does it vibrate at least?)
1 Like
What is correct path?
~ # ls -lah /home/defaultuser/.cache/gstreamer-1.0
total 595K
drwxr-xr-x 2 defaultu defaultu 3.4K Oct 13 23:43 .
drwxr-xr-x 21 defaultu defaultu 3.4K Oct 10 21:19 …
-rw------- 1 defaultu defaultu 585.1K Oct 13 23:43 registry.aarch64.bin
Yes, Ringtone volume is > 0. Vibrate also doesn’t work.
home/defaultuser/.cache/gstreamer-1.0
This one
Ringtone volume is > 0. Vibrate also doesn’t work.
This means that ngfd service crashed or doesn’t start at all. This is a user service.
You can try starting it manually as defaultuser as ngfd -vvv
1 Like
Should I remove the file registry.aarch64.bin in derictory gstreamer-1.0?
ls -lah /home/defaultuser/.cache/gstreamer-1.0
total 595K
drwxr-xr-x 2 defaultu privileg 3.4K Oct 15 15:00 .
drwxr-xr-x 16 defaultu defaultu 3.4K Oct 15 14:53 …
-rw------- 1 defaultu defaultu 585.1K Oct 15 15:00 registry.aarch64.bi
About ngfd -vvv logs here
https://paste.fo/raw/e58d5c56813f
I forgot asking about booting Sailfish on phone. My phone boots with SailfishOS ~2 min 35 sec (from black screen to PIN inserting screen). I think that is too long. What about tucana?
Yes please. It will be recreated. Follow the steps here to get logs Trying to run the Mi Note 10 port on Mi Note 10 Lite - #121 by vlagged
Can you not run it as root? this is an user service.
That’s a bit longer than tucana, but is not very fast here either (maybe 1 min 30’). I have not looked into this issue recently.
Removing of directory “/home/default user/.cache/gstreamer-1.0/” fully broks functionality. Other APPs can’t be started anymore. Phone calls also does’t work. Need to reset or reinstall OS?