SFOS on F(x)tec Pro¹: progress, issues, tricks, free chat - Page 29 - maemo.org

Active Topics

[HOWTO] Comprehensive Firmware Flashing Guide for N9 (1,580)
to Nokia N9 / N950 by aspergerguy - 8 hrs, 40 mins ago
Nokia N9-00 Prototype Build S1.12 (RM-680 codename "Dali") (250)
to Nokia N9 / N950 by en0s - 3 days, 5 hrs ago
[Announce] Maebble - Pebble support for Maemo (118)
to Applications by glo-worm - 3 days, 17 hrs ago
Possible to flash Leste to eMMC? (6)
to Maemo 7 / Leste by Eri - 4 days, 7 hrs ago
more...

Page 29 of 37

Thread Tools

taixzo	2020-08-13 , 05:13
Posts: 959 \| Thanked: 3,427 times \| Joined on Apr 2012	#281

wait, the fingerprint reader is working now? How do I enable it?

edit: also, not exactly a SFOS feature but OKBoard support is still missing on the Pro1

__________________
Saera: A Siri clone for the N900, N9(50) and Jolla

Follow me on Twitter: twitter.com/taixzo

Quote & Reply |

The Following 2 Users Say Thank You to taixzo For This Useful Post:
juiceme, mosen

	mosen	2020-08-13 , 10:49
	Community Council \| Posts: 1,669 \| Thanked: 10,226 times \| Joined on Nov 2014 @ Lower Rhine	#282

Fingerprint was introduced ~3 weeks ago to devel.

If you are on testing branch and did not update in last 2 weeks, a dist-upgrade should pull the changes.

Code:

# zypper ref && zypper dup

There are few reports however of the settings option not being available in Jolla Settings. So you might already have sailfish-fpd-community package installed but not seeing UI options to configure.

In that case there is a testing app attached to this post to at least test the hardware.
But how to get it to working to unlock if settings options are missing is beyond me.

Attached Files

sailfish-fpd-community-test-1.0.0-1.2.1.jolla.armv7hl.rpm (94.2 KB, 52 views)

__________________
Watch our weird watchfaces for mighty AsteroidOS
Performance comparison Video Sailfish 2.0 vs 1.1.9 vs 1.1.7
[MC eV] Maemo Community eV membership application please concider to join!

Quote & Reply |

The Following 2 Users Say Thank You to mosen For This Useful Post:
juiceme, taixzo

taixzo	2020-08-13 , 13:42
Posts: 959 \| Thanked: 3,427 times \| Joined on Apr 2012	#283

I cannot zypper dup, apparently; I get a bunch of "missing package" errors, mainly about "nothing provides libstdc++.so.6(CXXABI_1.3.9)"

__________________
Saera: A Siri clone for the N900, N9(50) and Jolla

Follow me on Twitter: twitter.com/taixzo

Quote & Reply |

The Following 2 Users Say Thank You to taixzo For This Useful Post:
juiceme, mosen

Kabouik	2020-08-13 , 14:50
Posts: 1,336 \| Thanked: 3,932 times \| Joined on Jul 2010 @ Brittany, France	#284

Can you double check that you are currently running SFOS 3.3.0.16?

Quote & Reply |

The Following 3 Users Say Thank You to Kabouik For This Useful Post:
Jordi, juiceme, mosen

	mosen	2020-08-13 , 14:55
	Community Council \| Posts: 1,669 \| Thanked: 10,226 times \| Joined on Nov 2014 @ Lower Rhine	#285

It smells like you are on sfos 3.2 still?
In that case update to 3.3.0.16 first.

Code:

devel-su
ssu re 3.3.0.16
version --dup
reboot

Also you might check if you are in safe "testing" waters since on devel things changed frequently and our testing-user advise might not apply.
To change to testing see here

Quote & Reply |

The Following 3 Users Say Thank You to mosen For This Useful Post:
Jordi, juiceme, taixzo

taixzo	2020-08-13 , 17:53
Posts: 959 \| Thanked: 3,427 times \| Joined on Apr 2012	#286

Thanks! I suppose that's what I was asking on the last page about how to update to the latest SFOS version. And thanks for the tip, I was indeed in devel and have now switched to testing.

__________________
Saera: A Siri clone for the N900, N9(50) and Jolla

Follow me on Twitter: twitter.com/taixzo

Quote & Reply |

The Following 2 Users Say Thank You to taixzo For This Useful Post:
juiceme, mosen

taixzo	2020-08-14 , 23:09
Posts: 959 \| Thanked: 3,427 times \| Joined on Apr 2012	#287

I do note that after switching to testing, my Pebble stopped connecting. Have the bluetooth fixes not made it there yet?

__________________
Saera: A Siri clone for the N900, N9(50) and Jolla

Follow me on Twitter: twitter.com/taixzo

Quote & Reply |

The Following 2 Users Say Thank You to taixzo For This Useful Post:
juiceme, mosen

	Fellfrosch	2020-08-16 , 17:14
	Posts: 1,092 \| Thanked: 4,997 times \| Joined on Dec 2009 @ beautiful cave	#288

I'm a complete idiot. My Pro1 is in a bootloop after I updated. I should have switched to testing. Especially, because I sacrificed my backup on my SD card for more Space for photos, while I was on holiday.

So I decided to reflash.
Unfortunately It seems like I totally killed my device.

When I try

Code:

fastboot set_active a

I get

Code:

error: Device does not support slots.

(fastboot devices lists my device)

Any suggestions???

Quote & Reply |

The Following 3 Users Say Thank You to Fellfrosch For This Useful Post:
juiceme, Kabouik, mosen

oenone	2020-08-16 , 19:26
Posts: 84 \| Thanked: 146 times \| Joined on Feb 2015	#289

Originally Posted by Fellfrosch

So I decided to reflash.
Unfortunately It seems like I totally killed my device.
When I try
Code:
fastboot set_active a
I get
Code:
error: Device does not support slots.
(fastboot devices lists my device)

Any suggestions???

Had that issue when initially trying to flash SFOS onto the F(x)tec Pro1. Nothing to do but try multiple times and with different cables. Ended up working with a cable going from a USB-C port to a USB-A adapter to a USB-A to USB-C cable. Maybe a straight, proper, standards compliant USB-C 3.1 cable would work.

Have not been able to replicate it, so could have just been a fluke.

Quote & Reply |

The Following 3 Users Say Thank You to oenone For This Useful Post:
Jordi, juiceme, mosen

	mosen	2020-08-16 , 19:41
	Community Council \| Posts: 1,669 \| Thanked: 10,226 times \| Joined on Nov 2014 @ Lower Rhine	#290

Originally Posted by oenone

Have not been able to replicate it, so could have just been a fluke.

That behaviour has been reported before.
All reported flashing issues involved usb3 in some form and the advise to either use usb2 port or a usb2 hub solved all cases i know off.

@Fellfrosch,
Either it is usb3 problem, or if you got deeper trouble from the devel-update, revert to factory state using the Factory-Restore Tool maintained by tdm.

Viel Erfolg!

@taixzo,
Sorry to hear and it will not help you when i tell you that pebble connection should be possible in testing...
EDIT, just tested and it works on my end, but:
I had to restart the rockpool service from within rockpool dev-tools while it was connected shortly to not let it disconnect after some seconds. After that first hickup it connects reliably now "even" after reboot.