Active Topics
-
Firefox with Leste (10)
to Maemo 7 / Leste by teroyk - 3 days, 23 hrs ago - more...
|
2020-11-30
, 12:36
|
|
Posts: 2 |
Thanked: 3 times |
Joined on Nov 2020
|
#72
|
Is somebody working on the port for oneplus3(t) or is it dead?[/QUOTE]
Not sure it is "dead" but just not upgraded it seems since the 3.2.1.20 build which is a real shame as this flies on a OP3T (albeit with no bluetooth and camera issues)
I have seen some new commits here in
http://repo.merproject.org/obs/nemo:...lus:/oneplus3/
Which kind of look promising as this was mostly on bluetooth .
Need to reinstall it again on my OP3T and then point to these.
Last time I had it on my OP3T I upgraded it to 3.3.0.16 but like many had no viewfinder and also upgraded it to 3.4 but that broke - lots!
Maybe armed with new additions from here and using proper OBS upgrades too it might work
Not sure it is "dead" but just not upgraded it seems since the 3.2.1.20 build which is a real shame as this flies on a OP3T (albeit with no bluetooth and camera issues)
I have seen some new commits here in
http://repo.merproject.org/obs/nemo:...lus:/oneplus3/
Which kind of look promising as this was mostly on bluetooth .
Need to reinstall it again on my OP3T and then point to these.
Last time I had it on my OP3T I upgraded it to 3.3.0.16 but like many had no viewfinder and also upgraded it to 3.4 but that broke - lots!
Maybe armed with new additions from here and using proper OBS upgrades too it might work
| The Following User Says Thank You to andybleaden For This Useful Post: | ||
|
|
2020-11-30
, 17:25
|
|
Posts: 2 |
Thanked: 3 times |
Joined on Nov 2020
|
#73
|
By the way of a quick update
Had some time over the weekend and tried to upgrade *(knowing the camera viewfinder would break of course!) to 3.4..0.24
I made sure though to update a little differently.
Firstly I made sure my device was still pointing at the Mer Oneplus 3 fixes that have been updated here:
http://repo.merproject.org/obs/nemo:...lus:/oneplus3/
I noticed someone kind had updated them recently in Nov 2020.
Backup your Sailfish OS user files.
Open a shell as user nemo preferably via ssh
Install something like nano (to edit text files)
devel-su
zypper in nano
Change the repositories for example for version 3.4.0.24:
nano /usr/share/ssu/features.d/adaptation-community.ini
and update the address
http://repo.merproject.org/obs/nemo:...atest_armv7hl/
press ctrl x to save
y to agree to save
return to agree the name
then
nano /usr/share/ssu/features.d/adaptation-community-common.ini and update the address again
http://repo.merproject.org/obs/nemo:...atest_armv7hl/
press ctrl x to save
y to agree to save
return to agree the name
Then I used the following
ssu release 3.4.0.24
zypper ref
zypper up
version --dup
sync
reboot
Unlike the last time I upgraded to 3.4.0.24 it did not break so much - browser/emails etc all work - bluetooth does not nor does the viewfinder and mtp support appears to be broken (again) but the camera does work which is promising even if you are shooting blindfolded!
Another bonus is that is now really really fast - We are talking a decent upgrade in speed....especially the browser.
It aint perfect but worth a try - I notice a few glitches here and there and will report back
Had some time over the weekend and tried to upgrade *(knowing the camera viewfinder would break of course!) to 3.4..0.24
I made sure though to update a little differently.
Firstly I made sure my device was still pointing at the Mer Oneplus 3 fixes that have been updated here:
http://repo.merproject.org/obs/nemo:...lus:/oneplus3/
I noticed someone kind had updated them recently in Nov 2020.
Backup your Sailfish OS user files.
Open a shell as user nemo preferably via ssh
Install something like nano (to edit text files)
devel-su
zypper in nano
Change the repositories for example for version 3.4.0.24:
nano /usr/share/ssu/features.d/adaptation-community.ini
and update the address
http://repo.merproject.org/obs/nemo:...atest_armv7hl/
press ctrl x to save
y to agree to save
return to agree the name
then
nano /usr/share/ssu/features.d/adaptation-community-common.ini and update the address again
http://repo.merproject.org/obs/nemo:...atest_armv7hl/
press ctrl x to save
y to agree to save
return to agree the name
Then I used the following
ssu release 3.4.0.24
zypper ref
zypper up
version --dup
sync
reboot
Unlike the last time I upgraded to 3.4.0.24 it did not break so much - browser/emails etc all work - bluetooth does not nor does the viewfinder and mtp support appears to be broken (again) but the camera does work which is promising even if you are shooting blindfolded!
Another bonus is that is now really really fast - We are talking a decent upgrade in speed....especially the browser.
It aint perfect but worth a try - I notice a few glitches here and there and will report back
|
|
2021-04-04
, 18:43
|
|
Posts: 48 |
Thanked: 191 times |
Joined on Jan 2016
@ Münsterland, Germany
|
#74
|
I was gifted a Oneplus 3 these days. I revived the device from a softbrick I created ealier this day. (yeah!)
Later I managed to install SFOS 2.1.4.14 on it, @delaya73 thanks for your work.
Then I horribly failed in updating it and even flashed the original image multiple times to start again. Something tells me I have to do a lot of reading to get this to work.
Anyways, this is the story of my failure, I'm sharing it for those who are also starting to walk down this path and for my future self
Later I managed to install SFOS 2.1.4.14 on it, @delaya73 thanks for your work.
Then I horribly failed in updating it and even flashed the original image multiple times to start again. Something tells me I have to do a lot of reading to get this to work.
Anyways, this is the story of my failure, I'm sharing it for those who are also starting to walk down this path and for my future self
Code:
# This is the place i started: version SailfishOS 2.1.4.14 (Lapuanjoki) # I did this, to make sure I'm really on the OTA branch... ssu re 2.1.4.14 version --dup ssu re 2.2.1.18 version --dup reboot # This went great, let's try the next step: ssu re 3.0.0.8 version --dup # Alright, we are now on SFOS 3 that's easy.... ssu re 3.0.1.11 version --dup ## Uh-ooh... This leads to the following error: Error: This request will break your system! This request will break your system! nothing provides libstdc++ # Ok, the system might now be broken anyway, let's try some foolish stuff, while reading the forums: # Then: ssu re 3.4.0.24 zypper ref zypper up version --dup # This leads to this error: Error: nothing provides pulseaudio >= 12.2+git9 needed by pulseaudio-modules-droid-glue-12.2.4-1.7.35.jolla.armv7hl zypper ref zypper up # Doing a version --dup now results in Error: This request will break your system! This request will break your system! nothing provides libstdc++.so.6(CXXABI_1.3.9) needed by qtscenegraph-adaptation-0.7.5-1.5.4.jolla.armv7hl # dared to reboot. It was an mistake, notification led is white on, the screen stays black. At least the device can boot to recovery. It's time to start at 2.1.4.14. But there is this damn tutorial....
But there are newer packages in the repository that will be installed later automaticaly, ex.: if I install software from openrepos. After that new bluetooth packges are installed (from 'bluetooth-rfkill-event-hciattach-1.0.6' to 'bluetooth-rfkill-event-hciattach-1.0.8'). This breakes bt again.
After a reboot rfkill shows 'bluetooth bt_power' only. If I unblock bt via GUI, I'm able to attach a 'bluetooth hci0' manualy with 'devel-su hciattach /dev/ttyHS0 qca 3000000 flow sleep' and bt is usable, but not switchable.
Is somebody working on the port for oneplus3(t) or is it dead?