![]() |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
There is a 2.0.5.6 build on the mer OBS repo, but its OTA only. I ran repo sync last night and plan on crapping out a new hybris 12.1 based build tonight, or tomorrow night. I love Sailfish OS and I love being able to record video when I want to. Maybe it'll work great, maybe it won't boot, I'll snap, and i'll just run Android 4.4.4. Wish me luck friends.
|
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Hello people,
since today the sensors on my Nexus 5 with Sailfish 2.0.4 stopped working. Should I reflash the sensorfix? No auto-rotate, no auto-brightness etc. EDIT: Solved flashing the sensorfix3.zip again |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
I tried to install CM12.1 based Sailfish OS on my Nexus 5 but I am stuck in bootloop. I can see the Google logo only. I have latest TWRP 3.2.3 and I also tried with 3.1.0 and 3.0.2 but same result. I can't install the pure CM12.1 Android either. However, I am able to install CM13 based Sailfish OS just fine with latest TWRP. Any idea how I could install CM12.1 Sailfish OS?
|
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Hi. I did an cm12 installation today but only with TWRP 3.0.0 (need a special TWRP version for Ubuntu Touch). The installation went well. Please check the md5sum of you installation images...
md5sum of the images I use: Code:
fddbf46d033946f48d1c37bf81e973bb cm-12.1-20160704-UNOFFICIAL-hammerhead-nocheck.zip Quote:
Cheers and Good Luck with SailfishOS on your Nexus5... |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
|
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
Thanks. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
If you could let me know the main difference between 2.0.4.13 and 2.0.5.6 I would much appreciate that too! Thank you. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
@edp17
Have you tried to SSH into the device using usb after the reboot? |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
What's the benefit of upgrading 2.0.4.13 to 2.0.5.6 by the way? (Newer Qt5 libs or more stable system or new functions?) Thanks. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
|
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
|
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
Seemingly the God do not want me this upgrade. I tried twice. First, I accidentally cancelled the installation at around 35% (pressed CTRL+C in the wrong terminal window) Second time my PC went blind at about 70%. I could see only a blank screen and an error message, and had no idea whether the install continued in the background or not. I waited half an hour trying to find workaround on my other phone but I finally had to reboot my PC. After both of these attempts when I rebooted the phone, as @mautz suggested, I was able to connect to it from the PC with ssh. However when I tried the 'version --dup' again, I got an error "Error message: Couldn't resolve host 'releases.jolla.com'" I will try again. I think if my PC won't die in the middle of the process again, it will be success. I have followed the instruction from here. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Over the weekend I gave another shot to upgrade to 2.0.5.6. The install has frozen at 83%, then on a forced reboot the phone didn't boot into the rom again. I was able to ssh into it but cannot complete the upgrade. Same problem: couldn't resolve host...
I have found somewhere (don't remember) a long command to start/stop the wifi internet on Sailfish os but that didn't help either. Anybody know how can I workaround this, please? |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Do you use USB to ssh into the device?
Can you ping IPs? Have you checked the repos after the reboot? |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Yes, I used USB.
Well, I have not tried to ping IPs and I have not checked the repos after the reboot as this was not mentioned anywhere so far. :D Thank you for your suggestions. I may try it again but don't think that any soon because now I would like to focus on the build. If I can manage to create a build 3.1.0.0 with CM12.1 base, hopefully I do not need the 2.0.4.13 anymore. We will see. Once I am at home will post the hammerhead.xml. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Yesterday I didn't have time to continue my build process but I grabbed my hammerhead xml.
I remembered wrong because currently only the two suggested lines are in there (well almost the suggested with a slight change): Code:
<manifest> Code:
<project path="hybris/droid-hal-version-hammerhead" name="mer-hybris/droid-hal-version-hammerhead-12.1" revision="master" /> Edit: The correct path of the muppet is 'vendor/lge'. From here. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
You are on the wrong path. You need to fork the device and kernel files, modify them and put the path of your fork into the xml file.
Take a look at 5.4 in the HADK. For example, this is my hammerhead.xml: Code:
<?xml version="1.0" encoding="UTF-8"?> |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
Why do I need to fork/modify if I am not planning to push anything back to the github? I only planned to follow the instruction from HADK and contribute my work to the github once I successfully have managed to build an installation. Until I don't have a successful build I don't want to litter github with my trying. However, honestly, I already forked all necessary bits and am using those in my manifest file but I thought sharing the lines with the original paths. Anyway, this is what I use in my hammerhead.xml (everything is pointing into my fork): Code:
<?xml version="1.0" encoding="UTF-8"?> |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Just do everything as described in the hadk, You don't need to change much, because the example used in the HADK is the N5.
There is way to much stuff in your hammerhead.xml Remove everything except kernel and device project and path. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
A question. I have seen some extra lines were necessary for other phones like galaxy S7, OPO, sony xperia z3c, etc. Do you know what these other lines are for? |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Which extra lines do you mean, do you have an example?
And which 4 extra lines are you planning to use? |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
So, I used these: Code:
<project path="device/lge/hammerhead" name="CyanogenMod/android_device_lge_hammerhead" revision="stable/cm-12.1-YOG4P" /> Code:
<project path="device/lge/hammerhead" name="edp17/android_device_lge_hammerhead" revision="stable/cm-12.1-YOG4P" /> Code:
<project path="hybris/droid-hal-version-hammerhead" name="edp17/droid-hal-version-hammerhead-12.1" revision="master" /> |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
You have to make these repositories during the Adaptation. These contain the necessary files, to get everything working. This is explained in Chapter 7 of the HADK.
But first you need to get a working kernel after checking out the CM12.1 base. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
I just have checked chapter 7 in the HADK. Indeed it says I need to push some stuff into github, then upstreamed into https://github.com/mer-hybris and then create a PR in the appropriate branch. Then after these steps, I can add some extra lines into my local manifest. As I said, I don't want to push anything to github yet. However I will need to create the rpm/droid-hal-version-hammerhead.spec anyway if I would like to go forward to package the HAL. By the way, I expected to see an example hammerhead.xml in the 12.1 branch here as probably I am not the first who is doing this port. But there is no hammerhead.xml in there. :( Only bacon, espresso3g, falcon, kis3, onyx and pollux. I have checked all the 30 forks of mer-hybris/local_manifests and there is no file for the hammerhead in the hybris-12.1 branch. :( I am also not sure why cannot add those lines into the local manifest before building the kernel, but I believe the HADK and follow it to avoid problems. :) An extra question: at chapter 8.5 (Building the image with MIC) it says I need to use the latest non early access version at the release. That is 3.2.0.12 however this HADK I am using is about 3.1.0.0. So what version number should I st at the RELEASE? 3.1.0.11 as the HADK shows or 3.2.0.12 as the HADK suggests from the wiki page? |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
You don't need to upload anything to github if you do not want to.
The example of the hammerhead.xml is in the hadk, just replace cm-11.0 with cm-12.1 and you are good to go. Just do step by step as it is in the HADK, You can use the latest version 3.2.0.12 to build everything at the end. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Thank you. Now I started to compile the kernel (step 5.4 in the HADK), but the command 'make -j$(nproc --all) hybris-hal' failed.
Error: Code:
The present kernel configuration has modules disabled. Code:
No private recovery resources for TARGET_DEVICE hammerhead Code:
perl: warning: Falling back to the standard locale ("C"). |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
You can edit the defconfig files with an editor. The defconfig you need to edit is arch/arm/configs/cyanogenmod_hammerhead_defconfig.
Just enable the modules support(CONFIG_MODULES=y) and try again. EDIT: Maybe you need to do a 'make clean' before your next compile try. Or copy your modified defconfig file to .config in your kernel/lge/hammerhead directory or do a 'make cyanogenmod_hammerhead_defconfig' before doing make hybris-hal. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
Plus it seems my system doesn't like the 'make -j$(nproc --all) hybris-hal' or 'make -j2 hybris-hal' commands. Both gave me the 'make: *** Waiting for unfinished jobs....' error. Now it is running with 'make hybris-hal'. Fingers crossed. :) I will report once it finished or errored. ;) Edit: I tried without the 'make clean'. It is running ... |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
My happy was too early. This time it ran longer indeed but is still complaining about the missing file_contexts:
Code:
target Prebuilt: (/home/edp17/mer/android/droid/out/target/product/hammerhead/kernel) |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
No, the 'make clean' didn't make any difference:
Code:
Install: /home/edp17/mer/android/droid/out/host/linux-x86/bin/checkfc |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Could you paste the content of your 'device/lge/hammerhead/sepolicy/file_contexts'
file on pastebin or a similar page? Edit: SInce this seems to be an SELinux related problem, you could try to disable it and compile again. Take a look at these commits: https://github.com/RealJohnGalt/andr...371afbefae2cae https://github.com/RealJohnGalt/andr...ebe9fc087c0226 Maybe you need to do a breakfast $device after doing this changes again. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
I try another kernel cm-12.1 instead of stable/cm-12.1-YOG4P.
(The last commit on the cm-12.1 was in 2015 while the other cm-12.1-YOG4P changed in 2013 last time. It might matter.) So, I have changed the local_manifest accordingly and am re-doing the repo init and sync. Then we will see how the kernel compilation goes. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
|
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Just googled a bit.
Just use the cm-12.1 branch(without stable). RealJohnGalt was only a few commits behind and he got it working. Edit: And the waiting for other jobs to finish while compiling the kernel isn't an error. You'll get this message if one of the jobs stopped due to an error. This only tells you that the other jobs are still compiling and will finish their current work. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
I will do the compilation again (with selinux disabled) and if it fails I will post that file and let you know. Thanks for your support! :) |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
Now I am trying to find the location of BoardConfig.mk to double check the 'selinux=0' bit. Edit: I have found it. In CM there is no 'selinux=0' but in John's there is. I will update these both files BoardConfig.mk and cyanogenmod_hammerhead_defconfig once the new kernel is downloaded and before I start compiling. |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
I should have used John's repos directly from the beginning. :( It would save me a few hours. (Although I gained a lot knowledge from this. :rolleyes:)
|
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Sorry, you are right, it was deleted by this commit:
https://github.com/RealJohnGalt/andr...371afbefae2cae BoardConfig.mk should be in device/lge/hammerhead/ directory. Good Luck! |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
After a bit of reseaching, he disabled CONFIG_SECURITY_SELINUX_BOOTPARAM in his defconfig, because he disabled CONFIG_AUDIT which also disables SELinux.
Some information can be found in the files for the mer-kernel-check script here: https://github.com/mer-hybris/mer-ke...el_config#L196 |
Re: SailfishOS 2.0 Nexus 5 CM12.1 Alpha1 | Sfdroid Pre-Alpha/Early Preview
Quote:
I will adapt this change too. Although I am concerning he might have done too other changes am not aware of. :confused: I am strongly thinking about to abort the sync which is running and using John's repos instead of the CM. (both the device and kernel) Well, if the compilation errors again, I will scrap the whole repo I downloaded and use John's repos. Thank you VERY much for your help!! I very much appreciated you stayed awake and helped me! In Germany it is already 2 in the morning. :) |
All times are GMT. The time now is 16:26. |
vBulletin® Version 3.8.8