Database Users

[09-06]SailfishOS & Multirom. How to set up guide

Hi sailors out there
When I'm going to read through the available sailfish threads the question about how to set up multirom & sailfish have been asked many times. So I thought I'm writing this little guide. I describe the procedure along the nexus 4 mako. But it have to be very similar on other devices like nexus 5 for example. The important parts that differs from mako are the kernel and modem image you've to use. I will describe the easiest way in my opinion. Experienced users have more capabilities to reach the goal. I will not describe how to install twrp recovery and unlock bootloader. Both are prequesites. Please use xda search or google to get this. But this little guide want's to be simple as possible. So let's begin .
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Beginning:
First we have to detect you're actual setup and where you want to go. Because nexus 4 is up to date I think the most common goal is to run android 4.4 as primary and sailfish os as secondary. Atm I have only paranoidandroid 4.4 on my device and will show you how to get everything working.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Requirements / Download following parts:
kernel aosp: http://d-h.st/A99
kernel cm: http://d-h.st/CCn
aosp = android open source rom. Ask in you're rom thread what version you're on with the rom
cm = cyanogen mod rom. Ask in you're rom thread what version you're on with the rom
Modem for nexus4 in version 0.84: http://d-h.st/cIJ
or
through an app in play store: https://play.google.com/store/apps/details?id=com.bpear.makomodem&hl=de
sailfishOS ea4: http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4.zip
cm 10.1.3: http://get.cm/get/aWH
Multirom manager in play store: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=de
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Before we're going on check up the following
1. All zip's you've downloaded have to be transferred on the device
2. Apps from play store are installed
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Installation process
Reboot in twrp recovery
Flash the new kernel
Flash the modem 0.84 in twrp. Or via the modem flasher from playstore. It's you're decision.
Boot back into android
Proof the functionality in android withe the new modem and kernel. Wlan working? Bluetooth? NFC?
Open mutlirom manager. Follow the installation steps.
After some time you'll be back in android. You have now the right modem, kernel and and a twrp multirom version on you're device
After this. Please reboot back into twrp recovery
There select the advanced button.
Then the multirom button
Select add rom and mark up the entry sailfish os
Press next.
Now you can choose two zip files to flash
zip1: Select the cm10.1.3 zip file
zip2: Select the sailfish EA4 zip file
Installation process is beginning.
After this select reboot
You automatically went into multirom where you can cancel the automatic boot process for the primary rom. Then you can select which rom you want to start.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And the most important thing is to read: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 for further question before you ask. I have described there many things to start with sailfish. If you find this useful think about to press the thanks button.

I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.

anttimonty said:
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
Click to expand...
Click to collapse
lol. and you ask why it won't work? It gave reasons for the instructions. Also look in the linked q&a thread at the bottom of first post. And here for you the relaese notes. Hope things becomes clear now. enjoy
Release Notes:
This release is based on SailfishOS 1.0.8.19 (Tahkalampi).
The Nexus 4 port is considered to be of alpha quality.
Though depending on your usage it might be stable enough for daily use.
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
MultiROM ≥v28 ability is in the image. See options of how to layout your MultiROM in #2 post below.
Alternatively, just have it as your primary ROM:
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/androi...s#instructions
b. Download links can be found here: https://developers.google.com/androi...ges#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-e...0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-e...mo-content.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the Sailfish OS .zip file in the same way ("on top of it")
* Reboot bootloader, Sailfish OS should boot and be visible
We recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
HW Support status:
(Look for Nexus 4 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Click to expand...
Click to collapse
Also I stated in first post why I only described the way I've did

Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.

anttimonty said:
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
Click to expand...
Click to collapse
yes. that's a great benefit of this device Do you like sailfish?
With modem version 0.84 you have all parts working in sailfish and android

Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish

anttimonty said:
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
Click to expand...
Click to collapse
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...

v3ng3anc32002 said:
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
Click to expand...
Click to collapse
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.

mudnightoil said:
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
hope the same for the z1c, but don't how is the chance to see this port (soon or later).

Works nicely on my n4. Looking for getting gapps to run....

mudnightoil said:
They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
Click to expand...
Click to collapse
This is just wrong
mudnightoil said:
I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
paulle said:
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Click to expand...
Click to collapse
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic

iuno said:
This is just wrong
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
thank you for information, followed your links to look at. It seems there for the z1c is a lot of remaining, we will need patience.

iuno said:
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
Don't think I'll regret getting the Z3C, from a hardware perspective ... held one the other day, as a friend had been gifted one by Sony. It's absolutely superb. Granted, I despise Android .. but for when the Jolla ****s itself / runs out of battery / when GPS or a camera is needed / roaming / skype /outdoor use, I can suffer it until there's a Sailfish port.
Hopefully as work is already under way for the One Plus One, the identical SoC used in the Z3 & Z3C won't be too much additional work.
For all the moaning and groaning about Mediatek, I'm guessing the simplest and best port of Sailfish will probably be for the Meizu MX4, as there'll be an Ubuntu ROM for it, and libhybris is used by Ubuntu Phone ...
Also, hopefully future iterations of the HADK will smooth out some of the problems porters are facing.

mudnightoil said:
Don't think I'll regret getting the Z3C, from a hardware perspective
Click to expand...
Click to collapse
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.

iuno said:
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
Click to expand...
Click to collapse
I wasn't saying Mediatek in general will be easier (though it's possible), but any device with an official Ubuntu ROM certainly will (should) be - Meizu MX4 (Mediatek) is the first of those.
P.S. The Z3C is fantastic ... though unfortunately in black as opposed to the red I ordered (it's being swapped tomorrow).

Thank you very much for these instructions. i have one question though. In order to download CM 10.1.3, it says to click that link which takes you to download CM installer app. Ive used that app before and as far as I kmow, it doesnt let you choose which version of CM you want to install, instead it just sets you up to install the newest CM 11. I downloaded 10.1.3 from their site. Either way, no big deal.
Also, which kernel do I download to install? Aosp or CM?
Thank you

Still up to date
Hi,
are these steps still up to date or should we follow a different set up guide to install the latest sailfish OS on the Nexus 4? Because most, if not all, the links on the first page end up 404...

Bluetooth sync from Jolla to Nexus 4
Flashed my Nexus 4 with the factory 4.2.2 from google with radio .48 and then flashed cm-10.1-20131003-SNAPSHOT-TREATFORCOOPER-mako-signed.zip because that seemed to be the 10.1.3 mentioned in the guides to end up flashing the latest sfos from this guide http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823.
I didn't try calling, it has 3G network working and wifi is working but I can't seem to get the contacts from my Jolla phone using the Bluetooth sync from the settings.
Anybody has some advice on this?

Just had a good look at the wiki of devices on the mer website and found out the bluetooth is not yet working on the Nexus 4...

Works perfectly on my oneplus one

[Q] Support for LG G3 with Cyanogenmod 12?

Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.

Yup, i confirm, doesn't work on lg g3. Pitty.

joergherzinger said:
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Click to expand...
Click to collapse
Sorry for my delay. I started a re-coding "marathon" on the weekend and it stretched for a week.
I intend to support the LG G3 as well as I possibly can, on any ROM. I have almost bought a G3 for testing a few times, but haven't gone through with it yet.
The CM12 kernel does not at present include the needed Qualcomm V4L FM radio "IRIS" driver.
I will try to submit the tiny 2 line config file change needed for that and see if they respond.
Someone built an FM friendly kernel and it worked, but there are/were still some audio issues. We can work around this with the new analog mode being added to Spirit2, and this should be properly resolved at some point.

Oh, thats great to hear.
For the Cyanogen part: They actually have a section in their bugtracker for FM Radio [1]. Once you have done that could you post the links to the pull request and the bug entry here. I will follow it and update my phone as soon as the fix is built. If there is anything I can do to help you please let me know.
[1] https://jira.cyanogenmod.org/secure...=+"FM+Radio"+ORDER+BY+priority+DESC&mode=hide

joergherzinger said:
Oh, thats great to hear.
For the Cyanogen part: They actually have a section in their bugtracker for FM Radio [1]. Once you have done that could you post the links to the pull request and the bug entry here. I will follow it and update my phone as soon as the fix is built. If there is anything I can do to help you please let me know.
[1] https://jira.cyanogenmod.org/secure...=+"FM+Radio"+ORDER+BY+priority+DESC&mode=hide
Click to expand...
Click to collapse
OK.
Last night I submitted the same patch for Xperia Z1 and it seems well received. First time I ever built a CM ROM and it took a few days to get everything downloaded and built and figure out how to submit CM patches etc.
My response time to posts and emails has increased, and my responses are more brief, because I have decided to spend more time doing what needs to be done and less time talking about it.

WOW great news!!
Thank's very much :victory:

mikereidis said:
OK.
Last night I submitted the same patch for Xperia Z1 and it seems well received. First time I ever built a CM ROM and it took a few days to get everything downloaded and built and figure out how to submit CM patches etc.
My response time to posts and emails has increased, and my responses are more brief, because I have decided to spend more time doing what needs to be done and less time talking about it.
Click to expand...
Click to collapse
Great! I'm trying CM12 in my G3 and, despite some typical nightly bugs, it's working quite well. I only really miss FM radio! :fingers-crossed:

Any progress ?

ariek44 said:
Any progress ?
Click to expand...
Click to collapse
Is the needed FM driver in the CM12 kernel for LG G3 now ?
And is the remaining problem that the sound sounds horrible ?
See my posts 9001 and 9002 for info on the new March 6 beta release. 9002 has link to the free version to try: http://forum.xda-developers.com/showthread.php?t=1059296&page=901

will not start
mikereidis said:
Is the needed FM driver in the CM12 kernel for LG G3 now ?
And is the remaining problem that the sound sounds horrible ?
See my posts 9001 and 9002 for info on the new March 6 beta release. 9002 has link to the free version to try: http://forum.xda-developers.com/showthread.php?t=1059296&page=901
Click to expand...
Click to collapse
New beta app says no tuner in current cm12 nightly. Tried flashing a different kernel - resin - but same result.

Phenax said:
New beta app says no tuner in current cm12 nightly. Tried flashing a different kernel - resin - but same result.
Click to expand...
Click to collapse
If you have the T-Mobile variant, I do not think FM can ever work for you.
As with the LG G2, only the Sprint and International variants have the FM antenna pin connected as needed to the headset jack for the antenna.
Other variants are purposely and permanently "broken" by shorting the pin to ground.
There was rumor here and there that other variants might work, but I think that was based on Spirit not showing a specific error at one point.
So, AFAICT, only the International D855 and Sprint's model.

joergherzinger said:
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Click to expand...
Click to collapse
I have built a CM12 based kernel that I think should work.
I do not have a G3 so I can not test it.
I can not make any guarantees that it will boot and won't harm anything.
This is a boot.img file. Anyone flashing it should understand how to flash such a file so I won't explain.
I will submit the patches to CM once someone can verify.
md5sum ~/mikes_boot_fm_12-20150307-UNOFFICIAL-d855.img
d8080528d3f37448e57a6da84162d4df
Thanks !

Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Edit: I just noticed that wake up by double tap does not work. I assume that just because you used a different kernel config to the stock cm one...

joergherzinger said:
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Edit: I just noticed that wake up by double tap does not work. I assume that just because you used a different kernel config to the stock cm one...
Click to expand...
Click to collapse
Great !
I did not touch the kernel config at all. I used this one, stock as of this morning, AFAICT: https://github.com/CyanogenMod/andr...0/arch/arm/configs/cyanogenmod_d855_defconfig
The config has this, unchanged:
Code:
CONFIG_RADIO_IRIS=y
CONFIG_RADIO_IRIS_TRANSPORT=y
All I did to patch/fix was this:
Code:
cp kernel/motorola/msm8226/drivers/media/radio/radio-iris-transport.c kernel/lge/g3/drivers/media/radio/radio-iris-transport.c
cp kernel/motorola/msm8226/drivers/media/radio/radio-iris.c kernel/lge/g3/drivers/media/radio/radio-iris.c
This copied the Qualcomm fix from the MotoG kernel source that allows radio-iris-transport to work built into the kernel, instead of only as a module.

joergherzinger said:
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Click to expand...
Click to collapse
Patch is here: http://review.cyanogenmod.org/#/c/90794/

I played around with it a bit more. FM worked like a charm, but several other things didn't work at all. Most importantly Settings crashed for me when I tried to open display settings. I assume that is because my CM is a little more than a week old while your build is just a few days old. I reverted by to my old boot.img but I will test the first nightly with your patch in it.

joergherzinger said:
I played around with it a bit more. FM worked like a charm, but several other things didn't work at all. Most importantly Settings crashed for me when I tried to open display settings. I assume that is because my CM is a little more than a week old while your build is just a few days old. I reverted by to my old boot.img but I will test the first nightly with your patch in it.
Click to expand...
Click to collapse
Maybe.
I've seen Settings crash on a few devices/ROMs.
Common AOSP Lollipop ROMs still have lots of problems.
They ALL have a nasty memory leak that gets bigger every time Spirit sends an RDS update to notification shade/remotes/lockscreen. I have to reboot my test phones every day or so to avoid unpredictable restarts when Android system_server fills its' internal table maxed at 51,200.
Stock Lollipop ROMs don't have this problem, so IMO must be some common bug in CM12 I think. (I could/should verify if Nexus/pure AOSP shares this.)

Well, it doesn't look too good. They seem to want this as a loadable module, which you explicitly stated different in your commit message. Any ideas an what to do next?

joergherzinger said:
Well, it doesn't look too good. They seem to want this as a loadable module, which you explicitly stated different in your commit message. Any ideas an what to do next?
Click to expand...
Click to collapse
Yes, I think so, it's just taking me a long time to do it.
The patches I provided WORK. The complaint was that IF they re-configure the kernel to use modules, then the kernel will not build and he did not like that.
Many kernels have removed modules now and it is rare to go back to modules, so I find this a bit strange, but I am not the one maintaining kernels.
The patches were not really "developed" by me. I just grabbed the very similar files from the MotoG CM12 kernel thinking they would not complain; it was just aligning the code between CM12 kernels.
My plan since the patches were rejected is to use the files from (I think) a Sony CM12 kernel that I think should work with or without modules.
But I have had a LOT of trouble getting d855 kernels and ROMs to build since my initial changes that worked AND it can take hours to build a new ROM and I still have not figured out how to build just the kernel, which is much faster.
This is the problem I had last night and the night before and I am not a ROM dev so it takes time for me to figure out what is wrong or how to fix (maybe a "make clean" or similar"):
creating userdata.img...
Running: mkf2fsuserimg.sh /tmp/tmpqdNGFw 12297699328
in mkf2fsuserimg.sh PATH=/home/m/android/system/out/host/linux-x86/bin:/usr/lib/jvm/java-1.7.0-openjdk-amd64/bin:/home/m/android/system/out/host/linux-x86/bin:/home/m/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin:/home/m/android/system/prebuilts/gcc/linux-x86/:/home/m/android/system/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin:/home/m/android/system/development/scripts:/home/m/android/system/prebuilts/devtools/tools:/home/m/android/system/prebuilts/android-emulator/linux-x86_64:/home/m/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/jvm/jdk1.8.0_25/bin:/home/m/b:/home/m/b/android-studio//bin/:/home/m/b/android-sdk//platform-tools/:/home/m/b/android-sdk//tools/:/home/m/b/android-sdk//build-tools/21.1.2/:/home/m/b/android-ndk-r10//build/tools/:/home/m/b/android-ndk-r10//
make_f2fs -l 12297699328 /tmp/tmpqdNGFw
/home/m/android/system/out/host/linux-x86/bin/mkf2fsuserimg.sh: line 31: 23180 Segmentation fault $MAKE_F2FS_CMD
Traceback (most recent call last):
File "./build/tools/releasetools/add_img_to_target_files", line 261, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/add_img_to_target_files", line 255, in main
AddImagesToTargetFiles(args[0])
File "./build/tools/releasetools/add_img_to_target_files", line 241, in AddImagesToTargetFiles
AddUserdata(output_zip)
File "./build/tools/releasetools/add_img_to_target_files", line 156, in AddUserdata
assert succ, "build userdata.img image failed"
AssertionError: build userdata.img image failed
make: *** [/home/m/android/system/out/target/product/d855/obj/PACKAGING/target_files_intermediates/cm_d855-target_files-079aa1bcfa.zip] Error 1
make: *** Deleting file `/home/m/android/system/out/target/product/d855/obj/PACKAGING/target_files_intermediates/cm_d855-target_files-079aa1bcfa.zip'
Click to expand...
Click to collapse
With troubles like these, and ROM builds taking hours and my lack of a G3 to test, this is moving slowly.
Add the fact that I am exhausted from the last few months of MORE major changes to Spirit2, some time spent with my family and looking into Android Auto and things move even more slowly.
...And the build guide for G3 seems to have disappeared too: http://wiki.cyanogenmod.org/w/Build_Guides#vendor=%22LG%22;
...And... any chance you know the OFFICIAL CM12 way of switching between module and non-module kernels ? I know the defconfig "CONFIG_MODULES=y" thing, but I'm not sure if other changes are needed. I can do a "make menuconfig" but I'm not sure if I should write .config to the defconfig. "make config" gives a million options; I tried that and produced a kernel that probably won't even boot on a G3.
Perhaps I should post in a G3 forum section asking for help.
I posted on that patch now: http://review.cyanogenmod.org/#/c/90794/

Hi, I don't understand half you are talking about
I'm just an user who wants CM12 and FmRadio.
That being said, I can read this changelog in 777 kernel thread (http://forum.xda-developers.com/lg-g3/development/kernel-777-kernel-t3003115). Did anyone try this "radio" builds?
02/08/15
- R6
- Fix Powersuspend
- CM kernel updates
- Synaptic touch firmware update
- Separate d855 builds with fm radio module
Click to expand...
Click to collapse
(EDIT: Tried by myself. Radio works with 777 kernel. However, audio quality is quite bad.)
Second, I would like to test any beta kernels, spirit app, or whatever in my G3 D855, in order to help making it work. Please tell me how can I do it.
Thank you very much!

LineageOS 14.1 ?

I think mi note 2 has been out for a long time but it seems that developers without much attention to this phone. I'm curiously Why ?
Because of old story - MIUI never release kernel source code ? or ...
Whatever it is, I would like to see there is lineageOS 14.1 in this phone.

Kris Chen said:
I think mi note 2 has been out for a long time but it seems that developers without much attention to this phone. I'm curiously Why ?
Because of old story - MIUI never release kernel source code ? or ...
Whatever it is, I would like to see there is lineageOS 14.1 in this phone.
Click to expand...
Click to collapse
It's the old story of lack of kernel source. Historically kernel sources have been released about 3/4 months after global rom availability, which happened a few days ago.
It doesn't help that availability all round has been limited for these. With so many people wanting the global edition and there being shortages of that model there's just not that many of these around at the moment in the hands of people that want to mod it. MIUI is very popular in China.
I'm hoping another 3-6 months we'll start to see some serious progress.
Luckily it's in the same device tree as a few other recent releases so there's some level of cross compatibility, lithium (Mi Mix) for example would require only minor modification to work and there seems to be more dev interest in that,
I did consider making a cooked MIUI rom for the Mi Note 2 (inc. xposed, root, a few tweaks here and there) but there didn't seem to be much demand and realistically if you want those features you already get them yourself without any real struggle.

I'm an old dev for CyanogenMod on Xperia.
I will try to put Lineage OS when the source of the kernel will be available.
A port can be possible with the source of the One Plus 3t (i supposed) but is better to wait official release of the kernel.

troufiniou said:
I'm an old dev for CyanogenMod on Xperia.
I will try to put Lineage OS when the source of the kernel will be available.
A port can be possible with the source of the One Plus 3t (i supposed) but is better to wait official release of the kernel.
Click to expand...
Click to collapse
Any news concerning kernel from Xiaomi or even Lineage?

//SkylarFlux// said:
Any news concerning kernel from Xiaomi or even Lineage?
Click to expand...
Click to collapse
Nope and nope :/

See here.

Thanks !
StoneTrapper said:
See here.
Click to expand...
Click to collapse

Has someone tried this? https://www.androidfilehost.com/?w=files&flid=168440&sort_by=date&sort_dir=DESC

AngelHxH said:
Has someone tried this? https://www.androidfilehost.com/?w=files&flid=168440&sort_by=date&sort_dir=DESC
Click to expand...
Click to collapse
Me and HondaJohn88 are working on new builds. It works and there are a few improvements and a few steps back, it still needs polishing before release.

LineageOS 14.1(Android 7.1.2), update to date - 20170512. Everything going well. (Thanks to hondajohn88)
https://www.androidfilehost.com/?fid=889764386195898578
Camera is not official one, it's snap camera - photo&video are working(Video recording, Front-1080p/Back-4K)
Auto brightness is working
Fingerprint Touch is working
... Others ... you try it and you will know...

Kris Chen said:
LineageOS 14.1(Android 7.1.2), update to date - 20170512. Everything going well. (Thanks to hondajohn88)
https://www.androidfilehost.com/?fid=889764386195898578
Camera is not official one, it's snap camera - photo&video are working(Video recording, Front-1080p/Back-4K)
Auto brightness is working
Fingerprint Touch is working
... Others ... you try it and you will know...
Click to expand...
Click to collapse
Tanks​ you ?

New Update:
https://www.androidfilehost.com/?fid=817550096634771139

New Update 0526:
https://www.androidfilehost.com/?fid=745425885120734790

Again thanks for your work!
Do you think it's possible that this becomes official?

meuhmeuh51 said:
Again thanks for your work!
Do you think it's possible that this becomes official?
Click to expand...
Click to collapse
These Lineage builds are by HondaJohn88 who I'm working with.
I've been bugging him to post them himself (when he does I'll get the old thread locked) but he hasn't yet.
Be aware that not every build he uploads is one that he's planning on sharing (or even an improvement over the last) - occasionally things break and some are more for archiving than actual use.
He shares his work in the Mi Note 2 Telegram group so I'd recommend joining so you can find out which build would be the most worthwhile.

StoneTrapper said:
These Lineage builds are by HondaJohn88 who I'm working with.
I've been bugging him to post them himself (when he does I'll get the old thread locked) but he hasn't yet.
Be aware that not every build he uploads is one that he's planning on sharing (or even an improvement over the last) - occasionally things break and some are more for archiving than actual use.
He shares his work in the Mi Note 2 Telegram group so I'd recommend joining so you can find out which build would be the most worthwhile.
Click to expand...
Click to collapse
Tank you

Thanks for this, gave new life to an old phone.
The latest build is from July 2017, right?

casacristo said:
Thanks for this, gave new life to an old phone.
The latest build is from July 2017, right?
Click to expand...
Click to collapse
There are newer builds of Lineage OS 14.1. Latest is from 12 January, if i'm not wrong

alexmanu1 said:
There are newer builds of Lineage OS 14.1. Latest is from 12 January, if i'm not wrong
Click to expand...
Click to collapse
Is that for Hermes or Scorpio? and where is the URL ?
Also I lost the IMEI (still have the number on a sticker) and so far failing miserably to restore it.

casacristo said:
Is that for Hermes or Scorpio? and where is the URL ?
Also I lost the IMEI (still have the number on a sticker) and so far failing miserably to restore it.
Click to expand...
Click to collapse
For scorpio. https://forum.xda-developers.com/mi-note-2/development/rom-lineageos-14-1-t3724739
About the imei issue , i don't know how to restore it , honestly.

Android O for M8

Any possibilities of ANDROID O for htc one m8

http://www.lineageosrom.com/2017/03/los-15-list-of-devices-getting-lineage.html
"This is all About the List i know though many more smartphones can get android 8.0 Oreo Because this list is not yet officially published by the google and This is not the official list its only based on the hardware and software of the devices that can support This type of android."

nolt said:
http://www.lineageosrom.com/2017/03/los-15-list-of-devices-getting-lineage.html
"This is all About the List i know though many more smartphones can get android 8.0 Oreo Because this list is not yet officially published by the google and This is not the official list its only based on the hardware and software of the devices that can support This type of android."
Click to expand...
Click to collapse
Lineages OS support the devices which have no official support from Google seems Lineages OS just have this project, wait and see for ONE M8

Someone need to build it when the source code drops. Until then you won't get any "Oreo"!

Thanks a lot @nolt, @Harrison Le & @mihran_thalhath

Has anyone tried this?
http://www.cyanogenmods.org/forums/topic/lineageos-15-htc-one-m8-android-oreo-8-0-rom/

anyone ?

I've tried but it didn't pass the bootanimation screen. I don't know what's the problem. I waited more than 30min but unfortunately no success.

grh35 said:
I've tried but it didn't pass the bootanimation screen. I don't know what's the problem. I waited more than 30min but unfortunately no success.
Click to expand...
Click to collapse
Same

David_UK said:
Has anyone tried this?
http://www.cyanogenmods.org/forums/topic/lineageos-15-htc-one-m8-android-oreo-8-0-rom/
Click to expand...
Click to collapse
I tried but stuck in bootloop and waited for a hour.

Don't you guys see a weird thing when the page says
LineageOS 15 GApps download link for HTC One M8 LineageOS 15 Oreo 8.0 ROM (Download the stock ARM64 GApps)​
Since when M8 become 64 bit arch ?
I'll never trust a site with wrong info and put my device on risk of bricking.

ckpv5 said:
Don't you guys see a weird thing when the page says
LineageOS 15 GApps download link for HTC One M8 LineageOS 15 Oreo 8.0 ROM (Download the stock ARM64 GApps)​
Since when M8 become 64 bit arch ?
I'll never trust a site with wrong info and put my device on risk of bricking.
Click to expand...
Click to collapse
I just flashed the rom and rebooted still it stucks at bootloop.

Seriously Guys??? Bruno is the only one right now who is trying to build O for m8. That build on that site was compiled by me, using Bruno's changes. It was not for public testing and someone shared it regardless. Just wait for Bruno to bringup O. Show some patience guys!

A reminder to all users who are willing to try Oreo at this moment:
Since the Oreo source just released, it would be possible custom ROM builds are highly experimental at this early stage. Please do take precautions on these builds and always have a full backup if you would like to try them out.
Stay safe and enjoy flashing!

jerryhou85 said:
A reminder to all users who are willing to try Oreo at this moment:
Since the Oreo source just released, it would be possible custom ROM builds are highly experimental at this early stage. Please do take precautions on these builds and always have a full backup if you would like to try them out.
Stay safe and enjoy flashing!
Click to expand...
Click to collapse
Yeah that's good thing b4 doing anything just take a full backup and play with any rom, in btw link for Oreo

mihran_thalhath said:
Seriously Guys??? Bruno is the only one right now who is trying to build O for m8. That build on that site was compiled by me, using Bruno's changes. It was not for public testing and someone shared it regardless. Just wait for Bruno to bringup O. Show some patience guys!
Click to expand...
Click to collapse
Thanks for your info. Will wait for official link from your side. I'm here to help you.

Patience is a virtue.
I remember when first versions of N roms dropped - they were mostly working, but not really usable
I'm just going to wait until stable los builds drop, then hopefully we'll get RR and others based on it.

Saleen28 said:
Patience is a virtue.
I remember when first versions of N roms dropped - they were mostly working, but not really usable
I'm just going to wait until stable los builds drop, then hopefully we'll get RR and others based on it.
Click to expand...
Click to collapse
Yeah patience needed for Android O for this old-age pretty smartphone.

I will say yes. https://forum.xda-developers.com/showpost.php?p=73545811&postcount=330

nunclud said:
I will say yes. https://forum.xda-developers.com/showpost.php?p=73545811&postcount=330
Click to expand...
Click to collapse
Yeah I too noticed that, waiting for official release.

Mipad Carbon Rom(Mocha)

I don't know if anyone knows about or tested the Carbon ROM build on July, 2017 which I found. Here's the link-
https://get.carbonrom.org/device-mocha.html
Please enlighten me if this is a fake website and fake custom ROM for Mipad(mocha).

it's legit and official site there.

Carbon Rom is Real ..... Not Fake!!!!!!!
I'm using it for past one week . working great

jeswinkumar said:
I'm using it for past one week . working great
Click to expand...
Click to collapse
Can u review the ROM in details?
Like Installation process, Android version, Pros and Cons,Stability, battery life,Performance and smooth operations, etc..

rocky869 said:
Can u review the ROM in details?
Like Installation process, Android version, Pros and Cons,Stability, battery life,Performance and smooth operations, etc..
Click to expand...
Click to collapse
I wouldn't use it yet. It was a test build, there are some broken stuff in it. Official build (built by servers) need some extra work, because the device tree/vendor needs to work without changes to the source code itself. This is not possible with our current trees (highwaystar's work), and so there are some issues with that build. Primarily, the camera is broken, because SELinux is enforcing. I've fixed it my personal builds, but now there are some issues with webview crashing. This is why I refrained from making a thread here. Once it's 100% stable, I will make a thread here.
Feel free to use it but don't complain when you realize some things are broken.

drakonizer said:
I wouldn't use it yet. It was a test build, there are some broken stuff in it. Official build (built by servers) need some extra work, because the device tree/vendor needs to work without changes to the source code itself. This is not possible with our current trees (highwaystar's work), and so there are some issues with that build. Primarily, the camera is broken, because SELinux is enforcing. I've fixed it my personal builds, but now there are some issues with webview crashing. This is why I refrained from making a thread here. Once it's 100% stable, I will make a thread here.
Feel free to use it but don't complain when you realize some things are broken.
Click to expand...
Click to collapse
Thanks for the feedback. I am using BDITA ROM latest version for over 6 months, although on KitKat but its the safest and most stable ROM I found for our MIPAD. Battery life,performance and ROM stability are 3 important things I look for in any ROM and BDITA serves me well.
I will wait more until I find a ROM which can replace BDITA