Develop Bugs

[DEV][WIP]Sailfish OS Port - Alpha 2

I heard at devcon that a few guys are working on Sailfish ports for a few phones, including ours. So I decided to get them together with the devs here on the forum to get the port done. The place where the developers and porters of Sailfish OS are talking to each other is on freenode, so if you want to help them... just go there and join the channel #sailfishos-porters.
Warning: This is a developement project. So please only join the channel if you really want to help. Just going there to ask for ETAs or stuff like that won' t be tolerated. Also this thread should be a place for developers to collect ideas and fix bugs, not for the purpose of asking for ETAs. Please keep that in mind.
For the initial port I would like to thank @vgrade; information on how to install the port are in second post!
XDA:DevDB Information
Sailfish OS, ROM for the ONEPLUS ONE
Contributors
dansou901, vgrade
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CM 11
Version Information
Status: Alpha
Created 2015-03-20
Last Updated 2015-03-29

This is a community port of Jolla's Sailfish OS for the OnePlus One.
It features a gesture-based user interface with a unique design and ease-of-use in mind.
For more information about SailfishOS please head over to sailfishos.org.
This is not an Android ROM, this is a different base of an operating system called Linux, running glibc library.
It only uses parts of Android for hardware enabling (drivers).
Release Notes:
The port is considered to be of alpha quality and released as a first step to the same levels of functionality as the Nexus 5 .
Download Location
http://images.devaamo.fi/sfa/bacon/
Kernel Source at http://images.devaamo.fi/sfa/bacon/...1.1.27-alpha1-201503192017-kernel-src.tar.bz2
Make sure you have a compatible cm11 version installed http://78.47.45.43/owncloud/public.php?service=files&t=9725fbb3b3c8d9706a2bb29388b3de83
Zip install tested with TWRP and MultiROM versions later than 20 March from http://forum.xda-developers.com/oneplus-one/development/mod-multirom-v26-t2835738
HW Support status:
(Look for OnePlus 5 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Bug reports, if internet search refuses to help:
First search XDA for keywords. Things like libsailfishapp have already been worked out by this amazing community
Software-related bugs (Sailfish OS): first search http://together.jolla.com . Tag your questions with "community-build"
Hardware-related problems: at the Nemo Project Bugzilla under Hybris-ing component
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone
oneplus forum thread at https://forums.oneplus.net/threads/sailfish-os-for-oneplus-one.279537/
Known issues:
OTA Updates do not work
The camera does not work
Android app support is not available (unlike in Jolla phone): please ask about the status for open-source Dalvik runtime framework on #sailfishos-porters on irc.freenode.net and also check this XDA Thread
All remaining: In Bugzilla
ROM Kernel: Linux 3.4.0
Changelog:
Alpha2 - 29 March 2015
WLAN fixed up - vgrade/yacuken
Alpha1 - 20 March 2015
Initial release
This is a new video of SailfishOS running on the oneplus one with wlan working . http://youtu.be/Vm4m_dlUYRw
Install Video at https://www.youtube.com/watch?v=iphzmCVofbk
Details of port can be found at http://piratepad.net/gVqPXuEGW4
Please join the porting efforts at IRC channel #sailfishos-porters.
Thanks to all the Jolla sailors and SailfishOS community members for all their help, especially @stskeeps for the QCOM_BSP catch.
BREAKING NEWS - SailfishOS 2.0 version WIP at https://plus.google.com/+TomaszSternaSMK/posts/DyQHm82v2b5
vgrade

Just a little status update that you see the project isn't abandoned: @vgrade is waiting for updated AOSP sources from Oneplus. Once they're live, he can cook something for us.

Is the project still alive?

CountDooku said:
Is the project still alive?
Click to expand...
Click to collapse
Ask @vgrade if it is still alive. I didn't hear anything the last weeks, but I hope that he's still working on it...

dansou901 said:
Ask @vgrade if it is still alive. I didn't hear anything the last weeks, but I hope that he's still working on it...
Click to expand...
Click to collapse
@vgrade, is the project still alive?

msri3here said:
@vgrade, is the project still alive?
Click to expand...
Click to collapse
Hey,
I've not been able to spend much time on this since xdadev:con due to day job commitments, fingers crossed I'll get some time over the holidays to progress some more.
BR
vgrade

vgrade said:
Hey,
I've not been able to spend much time on this since xdadev:con due to day job commitments, fingers crossed I'll get some time over the holidays to progress some more.
BR
vgrade
Click to expand...
Click to collapse
thanks for the quick reply
Take you time

vgrade said:
Hey,
I've not been able to spend much time on this since xdadev:con due to day job commitments, fingers crossed I'll get some time over the holidays to progress some more.
BR
vgrade
Click to expand...
Click to collapse
Let me know if you need any help, I'm new to porting, but I'd be willing to lend a hand and do some of the grunt work - if you need it.

I'm very interested by getting Sailfish OS on my One Plus.
I don't know how to install the build you'll provide but I suppose that you will give a litte tutorial with it.
I'm now following this thread !

Looking forward to this

@dansou901 might be of interest.
Edit: might be your work. [emoji5]
https://twitter.com/vgrade/status/573375605640695808

gsmyth said:
@dansou901 might be of interest.
Edit: might be your work. [emoji5]
https://twitter.com/vgrade/status/573375605640695808
Click to expand...
Click to collapse
Good find! I don't have twitter so I wouldn't see this... @vgrade, will you come here again when you're back from Barcelona? @KINGbabasula, is MultiROM ready to go for Sailfish OS?
Edit: It isn't my work, I'm not in Barcelona on MWC this year (but planning to go there someday...). So it's vgrades work together with the other Sailfish porters (see the IRC channel I linked in OP).

Have you guys seem this?
http://www.thejollablog.com/sailfish-os-oneplus-one/

topfreitas said:
Have you guys seem this?
http://www.thejollablog.com/sailfish-os-oneplus-one/
Click to expand...
Click to collapse
That's just a followup from vgrades tweet, so nothing new. The information that he will share the build after MWC is down in the comments...

Guys Hi
As you see great progress made during MWC week on the port. Stskeeps from Jolla identified the bug stoppng UI coming up so we are go now.
Good to see the chase up on Multirom as this makes it easier for folks to test. I think it just needs to have a build which includes the sailfish patches included so any recent upstream build should suffice. On the add room page you should see a SailfishOs radio button.
Stay tuned for more details and drop into #sailfishos-poters channel on freenode IRC and say hello.
BR
vgrade

For those wanting to build their own images I've put my porting notes at http://piratepad.net/gVqPXuEGW4 , join us at #sailfishos-porters channel on IRC .
vgrade
vgrade said:
Guys Hi
As you see great progress made during MWC week on the port. Stskeeps from Jolla identified the bug stoppng UI coming up so we are go now.
Good to see the chase up on Multirom as this makes it easier for folks to test. I think it just needs to have a build which includes the sailfish patches included so any recent upstream build should suffice. On the add room page you should see a SailfishOs radio button.
Stay tuned for more details and drop into #sailfishos-poters channel on freenode IRC and say hello.
BR
vgrade
Click to expand...
Click to collapse

vgrade said:
For those wanting to build their own images I've put my porting notes at http://piratepad.net/gVqPXuEGW4 , join us at #sailfishos-porters channel on IRC .
vgrade
Click to expand...
Click to collapse
Zip Image link now in second post in thread.
vgrade

vgrade said:
Zip Image link now in second post in thread.
vgrade
Click to expand...
Click to collapse
phone does not boot
i am using philz recovery to flash the rom can that be a problem

MasalaMan said:
phone does not boot
i am using philz recovery to flash the rom can that be a problem
Click to expand...
Click to collapse
Yes, this recovery does not have a version of tar which supports the -j option so the sailfishOs rootfs is not extracted, please use the recommended recovery
vgrade

Lineage OS updater missing in settings

I have the latest Lineage OS Rom (Feb 22,2017) on my MI Max Hydrogen and noticed that the Lineage update option is now missing within settings > about phone. Not sure if it was taken out in the last build or what happened to it.
I did flash a new gasps package last night for Google assistant however, no other changes. I'll do a new install if I have to, just thinking someone might have some insight beforehand.

Chadpurdy said:
I have the latest Lineage OS Rom (Feb 22,2017) on my MI Max Hydrogen and noticed that the Lineage update option is now missing within settings > about phone. Not sure if it was taken out in the last build or what happened to it.
I did flash a new gasps package last night for Google assistant however, no other changes. I'll do a new install if I have to, just thinking someone might have some insight beforehand.
Click to expand...
Click to collapse
I believe that the following link can be very helpful regarding your issue:
[ANNOUNCEMENT] Important Lineage/LineageOS Information To Know... by Ibuprophen
I wish you the best of luck!
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************

LineageOS 1st of January 1970

I just got a notification on my phone (HTC One m8) saying that there is a new update to LineageOS. When I open up the app the updater says that it's from the 1st of January 1970. Still says nightly and LineageOS 14.1 Android 7.1. Considering its the 1st of April I would think it's an April's fools, but I'm not sure. Anyone else in the same situation?
Thanks in advance

@BeastyUmbrella, They apparently released a corrected version on the 30th:
https://download.lineageos.org/m8
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

Ibuprophen said:
@BeastyUmbrella, They apparently released a corrected version on the 30th:
https://download.lineageos.org/m8
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
Click to expand...
Click to collapse
So I should just stick with the update from the 30th of March?
I have attached a screenshot of the update.
Thanks for the reply!

BeastyUmbrella said:
So I should just stick with the update from the 30th of March?
I have attached a screenshot of the update.
Thanks for the reply!
Click to expand...
Click to collapse
I really do believe you! I did notice that this issue came up for a recent release on a few devices within the Lineage's Gerrit and Github.
That was an issue that i had to see with my own eyes and i did... I was amazed at this too...
What you see on the link i had previously provided is the Official source for the releases.
I believe that the 1970 release error, though was a good year, was pushed out only through the LineageOS Device Updates.
Remember that if you ever see any device updates that do not look right, DO NOT, under any circumstances update your device with a questionable update. When in doubt, defer to the LineageOS website for the update. You may end up messing up a device ROM install and end up losing everything and have to start it all over with a fresh install.
Until you see a newer, and date appropriate, update from within your device, stick with the LineageOS website downloads and, if you decide to, update using the LineageOS website.
To add, the device updates are the same as the one's released through the website.
I wish you the best of luck!
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

Ibuprophen said:
I really do believe you! I did notice that this issue came up for a recent release on a few devices within the Lineage's Gerrit and Github.
That was an issue that i had to see with my own eyes and i did... I was amazed at this too...
What you see on the link i had previously provided is the Official source for the releases.
I believe that the 1970 release error, though was a good year, was pushed out only through the LineageOS Device Updates.
Remember that if you ever see any device updates that do not look right, DO NOT, under any circumstances update your device with a questionable update. When in doubt, defer to the LineageOS website for the update. You may end up messing up a device ROM install and end up losing everything and have to start it all over with a fresh install.
Until you see a newer, and date appropriate, update from within your device, stick with the LineageOS website downloads and, if you decide to, update using the LineageOS website.
To add, the device updates are the same as the one's released through the website.
I wish you the best of luck!
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
Click to expand...
Click to collapse
Thanks a lot!

Reporting of bugs

Where do I report bugs for the official Lineage?

isar998 said:
Where do I report bugs for the official Lineage?
Click to expand...
Click to collapse
Reporting bugs, issues, etc... within the XDA Forum very rarely ever gets the attention from any of the Lineage Developers (though a few of them do take a peek on occasion) but, there's a few preferred methods that Lineage asks for users to report them.
The following link provides a way (and outlines) for reporting bugs found in the LineageOS releases.
How to submit a LineageOS bug report to Lineage
The following link has some more options. Just scroll down to "Report bugs!"...
Welcome to the LineageOS wiki!
The following link has even more options for communicating with the Lineage developers for Contributing as well as receiving Support.
LineageOS Community
I wish you the best of luck!
"Live Long and Prosper..."
~Ambassador S'chn T'gai Spock
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].

Ibuprophen said:
Reporting bugs, issues, etc... within the XDA Forum very rarely ever gets the attention from any of the Lineage Developers (though a few of them do take a peek on occasion) but, there's a few preferred methods that Lineage asks for users to report them.
The following link provides a way (and outlines) for reporting bugs found in the LineageOS releases.
How to submit a LineageOS bug report to Lineage
The following link has some more options. Just scroll down to "Report bugs!"...
Welcome to the LineageOS wiki!
The following link has even more options for communicating with the Lineage developers for Contributing as well as receiving Support.
LineageOS Community
I wish you the best of luck!
"Live Long and Prosper..."
~Ambassador S'chn T'gai Spock
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].
Click to expand...
Click to collapse
Thanks bro. That was a great help!!

kan someone please report a bug lineage-16.0-20190209-UNOFFICIAL s5 Bluetooth sounds it turns off after a few minutes

X2pacXX said:
kan someone please report a bug lineage-16.0-20190209-UNOFFICIAL s5 Bluetooth sounds it turns off after a few minutes
Click to expand...
Click to collapse
Search here in XDA and report in thread where your ROM is published.

Lineage 16.0 updates failing on Samsung devices
All nightly builds on Samsung devices since 8/9/19 are having trust failures when trying to update either with the updater or manual update with TWRP. All my devices are running the latest bootloaders. I believe this change from the change log of 08/09/19 is causing the problem:
Changes included in lineage-16.0-20190809-nightly-gts210vewifi-signed.zip
msm8976-common: Add TZ.BF.3.0.3-00077 to trustzone assert android_device_samsung_msm8976-common.

Experimental Builds

Hi I am currently a cm user on cm13 and I wanted to wait a couple of months before switching to lineageos does anyone still have to experimental build for the M8? I don't want to lose my data.

emrc01 said:
Hi I am currently a cm user on cm13 and I wanted to wait a couple of months before switching to lineageos does anyone still have to experimental build for the M8? I don't want to lose my data.
Click to expand...
Click to collapse
I do have the "lineage-14.1-20170125-experimental-m8-signed.zip".
Though, i don't, personally, have the device, I had grabbed it for another member who had asked for a copy a while ago, the member ended up not wanting it anymore so I never uploaded it to my File Host Account.
I saw your question and your in luck! I still have it and will upload it and provide you a link to download it. Just give me a little time since the File Host site is running a bit slow.
Just an FYI... The Experimental builds are called Experimental Migration builds for (as you probably already know) the migration from the CyanogenMod to LineageOS.
In the meantime, here's a link that should be helpful in referring to that outlines the process in using the Experimental Migration builds.
Official LineageOS - Update & Build Prep
The following are some more helpful information regarding your device.
Official LineageOS - Info about M8
Official LineageOS - Install LineageOS on M8
I'll post the link as soon as the experimental build is done uploading.
"Live Long and Prosper..."
~Ambassador S'chn T'gai Spock
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].

Thanks and PS watch out your ships gonna die at genesis

emrc01 said:
Thanks and PS watch out your ships gonna die at genesis
Click to expand...
Click to collapse
Noooo..... I'm stuck in the Nexus with Kirk and Picard!!!
LMAO!
Well here's the link to the experimental build
lineage-14.1-20170130-experimental-m8-signed
Some individuals ask this question but, the MD5 file is only the checksum file that TWRP can use to verify the zip file. If you want to use it, just place it in the same location where the zip file is.
Be sure to read the information on the following link.
Official LineageOS - Update & Build Prep
This way you will understand that, after the migration has completed, you need to reboot back into Recovery to flash the latest nightly build.
*** PLEASE NOTE: If you use SuperSU and GApps, be sure to flash in the following order (at the same time).
1) Experimental build
2) SuperSU
3) GApps (for Nougat)
Then after the Experimental migration has completed, and your ready to flash the latest nightly (which is required to complete the migration), be sure to flash them in the following order.
1) Nightly build
2) SuperSU
3) GApps (for Nougat)
I know that it's redundant but, the LineageOS will undo the SuperSU and conflict with the GApps. This is why it's important to flash in the order above.
FINALLY... A hint... The way to know that the first Experimental migration has completed is basically after the device is booted and your done with the initial setup. Simply... If you are staring at the Home Screen... Then it's ready for the Nightly build to be flashed in the above order.
I did my best to explain this via text.
Please let me know how it went!
I wish you the best of luck!
"Live Long and Prosper..."
~Ambassador S'chn T'gai Spock
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].

Thanks

Went good successfully running latest lineage is build!

emrc01 said:
Went good successfully running latest lineage is build!
Click to expand...
Click to collapse
I'm happy to see it it had worked for you!
I'll keep the build on the file host account but, i can finally delete it from my device
I wish you the best of luck!
"Live Long and Prosper..."
~Ambassador S'chn T'gai Spock
Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise [NCC-1701].