Develop Bugs

[ROM][WIP] Sailfish OS 2.1 Nexus 10

An alpha build of Sailfish OS 2.1 for Nexus 10 (manta)
Its in rough shape but we are slowly but surely getting there.
YOU CAN DUEL BOOT WITH ANDROID! - See second post for info
UPDATE July 9th 2018: I am still still working on this. I have some stuff to try, mainly rebuilding the old June 2017 audio jack kernel in both hybris hal and the base rom, meaning, HOORAY - I'll be forced to start building my own android base. in the mean time things are the same in the OP, use the new build if you want the latest release and don't mind a lack of video, use the old one for creepy silent videos. I am counting down for Sailfish OS 3.0 to come out, I already know that its going to break anything I fix. And a big sigh is released.
Credits:
Lineage OS team for the LOS 14.1 Base (seriously, THANKS)
Jolla for that perfect software
followmsi for the fixed kernel sources that don't inherit those dirty lineage audio jack issues.
All the people on the #sailfishos-porters IRC who kept me motivated and full of hope (mal, krnlyng, Mister_Magister, sledges, m4r0v3r, piggz, r0kk3rs, just to name a few)
LOS14.1 Base: https://drive.google.com/file/d/1W3k2PzWKQU_-1qbhho_8MespNzr5zBlD/view?usp=sharing - I didn't make this at all.
Sailfish OS 2.1.3.7 alpha 0.1.2 rootfs: https://drive.google.com/file/d/1QKux9YkUHi7XZtGEJbUh_xYms5-BsLjo/view?usp=sharing - I did for sure make this (well, I ported it, credit to Jolla for sillica and stuff)
Sailfish OS 2.2.0.29 alpha 0.2 rootfs: https://drive.google.com/file/d/1IkWtZxAPGeiSiqCpMcbct-M43QlCsG8m/view?usp=sharing - THIS IS THE SUPER SPOOKY UNSTABLE RELEASE!!! BEWARE!
Adaptations Libhybris page: https://wiki.merproject.org/wiki/Adaptations/libhybris/Manta
My Video Review of alpha 0.1.3: https://www.youtube.com/watch?v=NmEGKZHquhQ
I have a lot to test so Ill populate this list more later but:
What works:
- Rotation
- ALS
- Magnetic Sensor
- Video
- Touch
- Hardware Keys
- Power Management and Sleep
The Checklist of What I Need to Fix
- Audio
- Video (droidmedia is broken in my latest clean build, this does not effect the rom in the OP, I would never update a rom with this many regression bugs)
- USB Charging
- Bluetooth
- GPS
- Haptic Feedback/Vibration
- Camera
CAMERA DOES NOT WORK IN THE BASE ROM SO IT WILL NOT WORK IN SAILFISH OS
Change log:
alpha0 - initial working release
alpha0.1 - added rotation fix, defined MALI_QUIRKS, applied a ton of random patches that did nothing
alpha0.1.1 - fixed taking screen shots, built gst-droid (you can now play mp3s but sound is still broken along with video)
alpha0.1.2 - built SDSVideoFix droid media! we can now play video but there is still ZERO sound at all.
alpha0.1.3 - unreleased, REGRESSION BUG: Video is broken - trying again.
alpha0.2 - Updated image to Sailfish OS 2.2.0.29, droid media still broken. I recommend staying on the old alpha 0.1.2 build.
Our device is the highest resolution device to ever run Sailfish OS (for now). Let's all feel extra special for a bit.
General About
Linux Kernel: 3.4.113
Rom Base: Lineage OS 14.1
Sailfish OS Version: Sailfish OS 2.2.0.29 | 2.1.3.7
Sources:
(This is on the to do list)
Also my Discord ID is dirtymikelikesfeet#9871

Tips and Tricks
Get landscape rotation in ALL apps
Go to warehouse, and install patch manager and autorotate anywhere (or something like that)
Reboot
voila.
Dual Boot Lineage OS 14.1 and Sailfish OS
This is super easy, so basically the Hybris installer doesn't touch /system or /data (at least none of the installed android files) so you can boot between the two rather easily. You will need a Lineage OS 14.1 boot image (Inside the Lineage OS 14.1 zip) and Hybris boot (inside the Sailfish OS zip). When you want to boot between the two, boot into TWRP Recovery, and flash the appropriate boot image. This should make it easier for testers.
Q/A
Does flashing a new Sailfish OS image wipe my android files? - As far as I know? No. But I haven't really tested this. It shouldn't.
"Is this usable as a daily driver?" - No. not right now. Once I fix audio maybe, but as it stands now, unless all you do is read emails, watch silent movies, and play simple games and read books, its pretty garbage. You can browse the web with web cat but it has 1/3 of the screen not used.
"Why did you use the LOS14.1 base you idiot? you realize we will never have working camera now right???" - Lesser of all evils. Once I get a good stable LOS 14.1 based sfos port (working everything), and a list of all my tweaks to fix everything, I will try making an LOS 13 based sfos port. I like camera too, and do occasionally use it on this tablet.
"Does it have android app support?" - No. Maybe one day I will hack alien dalvik onto it and post a concept install for Nexus 10, but no promises.

Looks interesting,I will have to follow your work to see how far this goes. ?

Yes me to. I still have my Nexus 10 but don't use it much because it's horrible for streaming videos, unless I flash gingerbread. Anyway hope you keep at this, thanks for your effort.
Sent from my LG-ls990 using Tapatalk

aheeejd said:
Yes me to. I still have my Nexus 10 but don't use it much because it's horrible for streaming videos, unless I flash gingerbread. Anyway hope you keep at this, thanks for your effort.
Sent from my LG-ls990 using Tapatalk
Click to expand...
Click to collapse
Thanks for the interest, the current thing to do is add minimer to m N10 so I can fix hwcomposer, it is wonked real bad and I think it's why jolla-startupwizard won't work right now.

*bump* because it finally ****ing works (sort of)

sailfish for nexus 10
Galaxyninja66 said:
*bump* because it finally ****ing works (sort of)
Click to expand...
Click to collapse
a better browser please??or a new version??

ted111 said:
a better browser please??or a new version??
Click to expand...
Click to collapse
browser bugs are proving near impossible to solve, and manually rebuilding qtmozembed did nothing. I am going to try and crank out a 2.2 build tonight with the vendor repos included but I doubt much will change. As far as browser, the cut off is a problem with qt that I am still figuring out how to solve.
OKAY! Building new image with mic as I type this. it's at 162/473, hope it doesn't fail but it rarely does at this point. Using followmsi's new 0611 build as a base, and I have thrown in TheMuppets vendor repos for broadcomm and the like, hopefully something cool happens, but I am 99% sure this build will be the same broken build accept based on sailfish OS 2.2. This means no gstreamer, i.e. no videos, no mp3 files, no nothing. Also I doubt Audio will just fix it self either.

Galaxyninja66 said:
*bump* because it finally ****ing works (sort of)
Click to expand...
Click to collapse
tested 2.2.0.29 ,no videos, sound, webpirate browser simple works

ted111 said:
tested 2.2.0.29 ,no videos, sound, webpirate browser simple works
Click to expand...
Click to collapse
Its terrible, I know.
and the audio isses we are no closer to fixing since I have ZERO idea what is causing them, and neither do the people I've worked with. I am reloading the CM11 based port and trying to work out the gralloc issues on it, there are a ton of dependency files missing on that port for hwcomposer, but it should be fixable. everything is fixable.

Galaxyninja66 said:
Its terrible, I know.
and the audio isses we are no closer to fixing since I have ZERO idea what is causing them, and neither do the people I've worked with. I am reloading the CM11 based port and trying to work out the gralloc issues on it, there are a ton of dependency files missing on that port for hwcomposer, but it should be fixable. everything is fixable.
Click to expand...
Click to collapse
any news about it?

123123123123123213 said:
any news about it?
Click to expand...
Click to collapse
I no longer own the device, 10.1 and 11 sources had hwcomposer errors (but working audio afaik). 12-13 sources failed to boot for reasons entirely unknown since the logs looked fine (and no, it wasn't a no UI/display error, I checked and it was in telnet still, again, for seemingly no reason). 14.1 worked like a charm but sadly the audio issues were just a mystery. Rotation was an easy fix and I think at that point GPS had very little mw so it was hit or miss and debugging it was not done often so it was mostly undocumented. Don't know about now.
tl;dr
10.1-11 - broken hwcomposer, wayland is gimped in 2.0 and beyond period, and fbdev wouldn't work either
12-13 - refuses to boot past the telnet stage for unknown reasons
14.1 - audio is broken, using followmsi and the stock lineage sources/matching base images.
I'd love to work on this again actually, but a new N10 would cost me 80 AUD and I'd have to prep a new VM since I wiped all mine switching to macOS.

Device Tree for Oreo?

Hello
I want to build a resurrection remix Oreo ROM for my d2can/d2att but I can't seem to find the proper device tree and kernel tree for Oreo. Is there a way to either port the nougat trees or make my own tree compatible for Oreo?

It is but you are going to go through literal hell learning how to do so. i am working on the same thing and have some stuff figured out but getting help has been next to impossible. you have to read countless websites piecing the information together and trying things until it works. you can go into the lineageOS IRC but they dont talk too much, and like answering questions even less. What i learned was a bit easier then using the lineage repos for everything was just to sync lineage 15.1 or 16.0 and then to google around for a device tree and kernel. they usually still come from github but have different names. for example our s3 here goes by more names then d2att for example. SGH-i747 is another variant of s3. if you look for the other variants you will find more device trees. you can get lunch to show them to you by adding them to the vendor folder before you attempt to run the envsetup.sh as for the boot.img you will need to again google around a bunch and learn about mkbootimg and the tools needed to extract and repack them, if you use superrs-kitchen you will extract and see the files bot many will have a lock, and you cant edit the init.rc. you can extract your boot from your device directly via adb, or download a rom and unzip it n grab that boot.img if you use a rom you know works. you can change the OS version and all necessary info in the files to tell the phone its android 8.1 and whatnot. but as i said its not a short process. ive spent many many night getting frustrated because lunch fails partway into a build, or i flash a kernel i complied and it doesn't work. getting Pie 9.0 and Oreo 8.1 to boot on my s6 edge plus was a nightmare and a half, and the s6 files are all readily available to me from lineage to use as a base. the s3 was really popular however, and i know lineage has a nougat rom for it, so they must have repos with trees
---------- Post added at 03:44 AM ---------- Previous post was at 03:42 AM ----------
https://github.com/Bdaman80/SGH-I747
device tree.
https://github.com/sgs3/SGH-I747M_Kernel
kernel

SailfishOS For Redmi Note 5/ Redmi Note 5 Pro

When will sailfishos ever appear? I love Linux/GNU and I want to see this OS on whyred

If you port it.

Not worth it. Not enough people will use it

Yes! I also love GNU / Linux and would also like Sailfishos / Ubports / Halium / PlasmaMobile on whyred to porting! The only pity is that they did not post the LOS 14.1 Device tree. In Messages Dev LOS 14.1 not answer Probably you need to build the device tree yourself. Since halium max version base Android 7.1, sailfish os is base Android 8.1 Experimental / Unstable (.
Not worth it. Not enough people will use it
Click to expand...
Click to collapse
Well so what? GNU / Linux desktops run 2% of users, but you can still use There are drivers, there is stability, there is software.
On smartphones, Complicated this is , but other OSes are still possible. Snapdragon SoC features allow. Looking for a device tree, Halium, enough time and straight arms.

TITANIST26 said:
Yes! I also love GNU / Linux and would also like Sailfishos / Ubports / Halium / PlasmaMobile on whyred to porting! The only pity is that they did not post the LOS 14.1 Device tree. In Messages Dev LOS 14.1 not answer Probably you need to build the device tree yourself. Since halium max version base Android 7.1, sailfish os is base Android 8.1 Experimental / Unstable (.
Well so what? GNU / Linux desktops run 2% of users, but you can still use There are drivers, there is stability, there is software.
On smartphones, Complicated this is , but other OSes are still possible. Snapdragon SoC features allow. Looking for a device tree, Halium, enough time and straight arms.
Click to expand...
Click to collapse
We have lineageos 14.1
https://www.google.com/amp/s/forum..../development/rom-lineageos-14-1-t3765529/amp/

I think its a pretty good idea. Just because some people don't use them doesn't mean its useless.
Sailfish is already present for redmi note 5 / 5 plus. It would be a great addition for our note 5 pro too

a2p1k02 said:
We have lineageos 14.1
Click to expand...
Click to collapse
Need not assembled ROM * .zip, and you need to have a device tree, branch cm-14.1 (device_xiaomi_whyred, kernel_xiaomi_whyred, vendor_xiaomi_whyred on Github). And it is not there, only lineage 15.1. I will try to collect lineage

karan5chaos said:
reply
Click to expand...
Click to collapse
I did not find the https://forum.xda-developers.com/chef-central/android/how-to-build-lineageos-14-1-t3551484 instruction for building specific files for the device tree and google too not found. Found the old for cm 11 or others do not describe a sufficiently assembly system. Help me find this guide!

I think people have ported sailfish using lineage 15.1 as well. Did you check maemo.org? I'm sure you will find the required guide there.

After a long search still found mer-hybris 15.1. I put the command repo sync to download the source SFOS about 13 gb (at a speed of 4 Mbit/s) tomorrow is downloaded and I will continue porting.

TITANIST26 said:
After a long search still found mer-hybris 15.1. I put the command repo sync to download the source SFOS about 13 gb (at a speed of 4 Mbit/s) tomorrow is downloaded and I will continue porting.
Click to expand...
Click to collapse
You are my hero !
Thank you so much for your efforts and persistence. It's because of members like your this community is thriving. I will gladly be a tester and report back issues and feedback if any.

karan5chaos said:
Reply
Click to expand...
Click to collapse
I think you know how to resume the ragged download source repo.
After repo sync, --fetch-submodules prints:
error: in `sync --fetch-submodules`: revision lineage-15.1 in LineageOS / android_kernel_xiaomi_sdm660 not found
Proceeding from the fact that the Internet is a little unstable, "warning, fatal" were pouring into the terminal. To stop this, I pressed ctrl + c. but it was necessary ctrl + z (suspend the process)
How to fix?
PS: In a few days, I will have a better internet connection.
PPS: Question is closed, I looked in google, I found a similar case
https://stackoverflow.com/questions/51466608/multiple-android-repo-sync-fatal-errors

TITANIST26 said:
I think you know how to resume the ragged download source repo.
After repo sync, --fetch-submodules prints:
error: in `sync --fetch-submodules`: revision lineage-15.1 in LineageOS / android_kernel_xiaomi_sdm660 not found
Proceeding from the fact that the Internet is a little unstable, "warning, fatal" were pouring into the terminal. To stop this, I pressed ctrl + c. but it was necessary ctrl + z (suspend the process)
How to fix?
PS: In a few days, I will have a better internet connection.
PPS: Question is closed, I looked in google, I found a similar case
https://stackoverflow.com/questions/51466608/multiple-android-repo-sync-fatal-errors
Click to expand...
Click to collapse
I think the question at stack overflow did mention some fix in second answer. Did you try that ?

A300FU Lineage 16.0 Selfbuild Bootproblem [SOLVED]

hi all
my story:
i got my hands on a samsung galaxy a300fu (aka. a3ulte) 2015 and successfully installed twrp3.2.3 and a custom lineage build version 14.1. my goal however is to build, install and boot lineage 15.1 or lineage 16.0. the building is not the problem! i can build both versions (with help of the lineage wiki and the local manifest from the github user "Galaxy-MSM8916"). i can also install them however i'm unable to boot them.
what i tried so far:
- the mentioned github user offers multiple lineage 15.1 downloads for the device but none of them seem to boot (it crushed my PIT or something i needed to reflash the recovery image)
- since android 8.0 the debug mode is off so i needed to build an engineering version (another 4h) to get some kernel messages but i'm kind of overwhelmed with 11000 lines of debug (not counting the loops)
- on androidfilehost there is a lineage 16 build from the user vlw (also present here on xda) which strangely seems to be working! after checking its system properties file however it seems this build is kind of a hybrid (part a3lte, part a3ulte). also i'm unable to contact him that's why i'm writing here.
i'm pretty much out of ideas and would like to know if any of you has an idea how to proceed.
regards
edit:
related to github.com/Galaxy-MSM8916/android_device_samsung_gprimeltezt/issues/1
able to boot after renaming hardware/qcom/keymaster/Androir.mk to hardware/qcom/keymaster/Android.mk.nobuild

[ROM][UNOFFICIAL][10] e/OS 0.22 q for Motorola One xt1941-4

Following this thread, I recently built e/OS 0.22q for Motorola One xt1941-4 (deen). Please refer to https://e.foundation/e-os/ to learn more about e/OS.
After several weeks of usage this ROM seems to be very useful. Find the zip file with the images of the Andoid 10 version here. Unzip and flash using adb and fastboot. Please use at your own risk!
I used the following repos in my local manifest:
https://github.com/electimon/device_motorola_deen, branch Lineage-17.1
https://github.com/electimon/vendor_motorola_deen, branch Lineage-17.1
https://github.com/100Daisy/android_kernel_motorola_deen, branch android-10-release-qpks30.54-22-13
In addition, I included
https://github.com/LineageOS/android_system_qcom, branch Lineage-17.1
which is obviously needed by some stuff from vendor. Vendor files are from 2019, so if someone could provide a more recent repo, I would be glad to know (last stock rom provided by Motorola is from October 2021)
All credits go to the creators of the LineageOS 17.1 port (link to thread at the top of this post)! Very good job guys!

Works just fine, thanks.

LSV12 said:
Works just fine, thanks.
Click to expand...
Click to collapse
Thanks!

Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian

01nick07 said:
Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian
Click to expand...
Click to collapse
I'm sorry, but I have no time and I am not good at making tutorials at all. Please refer to the thread referenced at the beginning of the initial post. There you should find all necessary information. If this is not enough, do some more searching and reading on XDA. If you still feel uncomfortable, stay with the stock rom.

Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'

xdadevc said:
Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'
Click to expand...
Click to collapse
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...

HerrElling said:
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...
Click to expand...
Click to collapse
I read your article and managed to follow it and compile my own e/os. I'm also not an android developer. I did some kernel work in the early days, around Android 2.0 but my path diverged and now I'm completely lost.
Let's keep in touch. If you restart your efforts, I'll be happy to contribute. Meanwhile I'll try my best to get some info from the e/os forums and (pray) the lineageos residual devs.