Related
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
I thought I'd post here my (and the people who helped me) progress on porting MultiROM to the HTC Nexus 9.
Contributors (so far, tell me if I miss anyone)
@Bogdacutu for his port of MultiROM on the Shield Tablet (The arm stuff)
@USBhost for testing as well as helping with the patch (patch is still WIP, more on this later)
@Tasssadar for MultiROM all together
@Unjustified Dev for his influence
Progress
Working: Multirom TWRP has been successfully compiled for flounder and has working ADB and MTP.
Partially Working WIP: MultiROM boot selector source has been ported to work with arm64. The multirom boot selector compiles for flounder in zip format and launches at device boot. However, touch does not work and there is no ADB at the moment.
Not Working WIP: The kexec hardboot patch currently does not work so the Nexus 9 is currently unable to boot another ROM other than the primary one.
Source
All sources can be found here (I know some of them may not work and may be a little messy but this is still a work in progress)
Device Tree
Kernel
MultiROM
MultiROM TWRP
Building Notes
I compile this with the CyanogenMod Device Tree. Instructionsfor building multirom can be found on the multirom wiki found here
Note: adbd and kexec-tools need to be replaced with these versions that are arm64 compatible
adbd kexec-tools
If you would like to contact me on hangouts about this, please PM me your Gmail.
Reserved
One more
I might have found a repository that may help us out with the kexec hardboot patch on arm64.
There are many commits here that relate to kexec on arm64
Very glad to hear!! Sooper work :thumbup::thumbup: :beer:
This may also pose useful for the arm64 instructions
...
Looks like kexec-tools may need to have a lot of changes for arm64.
There are the changes made on a more recent version or android tools (not the one for android/multi-rom). I think this commit may be helpful but changes would have to be made.
Re-based many of the repositories on MR64 the other day. Now I need to test....
Also, the kexec tools function for flounder is completely re-written so maybe kexec will work?
I'll have to try to test when I have a lot of free time...
Is this going to work to get Linux kexecboot working? I really would like to have Linux running natively on this tablet....
Any updates on the project?
Any news on this, hoping for developments so that progress can be made for oneplus2 and multirom?
Thanks
Hello, and whether support for Nexus 9?
@Hashbang173
What's the status of this ?
omerjerk said:
@Hashbang173
What's the status of this ?
Click to expand...
Click to collapse
I have tabled development for this until further notice.
Hashbang173 said:
I have tabled development for this until further notice.
Click to expand...
Click to collapse
Is there any deving goin on on this? I think its way too hard. kexec isnt x64 compatible. (The binary itself isnt. How will youll port hardboot ) First we will have to add x64 support to that. I have seen your commits. That isnt x64 supported too.
Please update me on this, im building on op2 if this works. Thanks <3
regalstreak said:
Is there any deving goin on on this? I think its way too hard. kexec isnt x64 compatible. (The binary itself isnt. How will youll port hardboot ) First we will have to add x64 support to that. I have seen your commits. That isnt x64 supported too.
Please update me on this, im building on op2 if this works. Thanks <3
Click to expand...
Click to collapse
I'm no dev but could this be helpful for kex ec on ARM64? https://www.spinics.net/lists/arm-kernel/msg462969.html
Hashbang173 said:
I have tabled development for this until further notice.
Click to expand...
Click to collapse
I know you've put this project on hold for the time being, but I would like to jump in on this dev-tastic venture. I got a Nexus 9 (LTE) for Christmas*, and wanted to let you know that you don't have to bear the burden of building/testing/debugging/etc. all by yourself. I am fairly well versed in the mechanics of MultiROM, and have been (and still am) a user of MR on my Nexus 7 (2013) since v28 . . and honestly, without MR on my Nexus 7, I probably wouldn't have the pen. testing abilities that have enabled me to offer those additional services to my clients (i.e., security consultation, data breach prevention, etc.).
My point is that I owe a lot to Tasssadar and the "MultiROM for Android" concept in general, so I am happy to give back in any way that I can.
The Nexus 9 has been my dream Android device ever since the rumor mill was buzzing with notions of a Nexus tablet with an ARM v8 (ARM64) based Tegra variant!!
Let me know if/when you wanna get this thing off the ground again, and I'll make myself available as much as possible.
FULL DISCLOSURE: Although I am fairly versed regarding MultiROM and it's mechanics (kexec-hardboot, modifications to TWRP, etc.), I don't have much experience when it comes to ARM v8. However, I am pretty fluent regarding desktop x64 programming applications and coding, so it shouldn't be too hard for me to wrap my head around this whole ARM v8, 64-Bit SoC/MoP revolution. If you (or anyone who knows) could fill me in on the challenges we are facing regarding kexec and hardboot in a 64-bit scenario, that'd be swell. In the mean time, I will do my best to get up to speed regarding the repos & commits you have referenced/linked up to this point.
THANK YOU FOR ALL OF YOUR HARD WORK THUS FAR, AND LET'S GET 'ER DONE MY FRIENDS!!
:fingers-crossed:
*BEST . . CHRISTMAS . . PRESENT . . EVER!!!!!!
Thanks Mom!!
They have a Multirom version working for the Nexus 6P which is an arm64 device using the kexec method. Here is the link if it helps you devs.
http://forum.xda-developers.com/nexus-6p/development/mod-multirom-v33-beta-1-t3313291
rifraf1 said:
They have a Multirom version working for the Nexus 6P which is an arm64 device using the kexec method. Here is the link if it helps you devs.
http://forum.xda-developers.com/nexus-6p/development/mod-multirom-v33-beta-1-t3313291
Click to expand...
Click to collapse
yep, I ported it to clark already, maybe I'll try porting it to flounder in the future
Multirom for yureka aka tomato (64bit snapdragon 615) is also coming today with kexec-hardboot patch. Hope other devices also get this fast
hi guys, I see there are still no threads for FirefoxOS that has been just released by FXP for our device too (z3c) so I'm creating one
this thread just to discuss about it!
INFO: http://fxpblog.co/2015/09/26/firefox-os-releases-by-fxp.html
DOWNLOADS: http://fxpblog.co/firefox/nightly/
INSTALLATION:
- You must have a UNLOCKED BL
- Extract all system images from the ARIES zip you downloaded
- Connect phone to PC in fastboot mode and then:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
downloading the zip for aries right now! will see how it goes
in the meantime, I have already some questions I would like to reply myself after testing the new OS or if somebody already knows the answers, please let me know!
1. rootable? DON'T THINK SO
2. recovery can be installed or to go back to stock will have to flash FTF via flashtool? SEEMS NO RECOVERY AT ALL?!
3. camera present/working? if so, without fish eye bug? CAMERA NOT WORKING AT ALL
4. gapps are needed? in firefox OS there is no Play Store right? NO GAPS, THERE IS MOZILLA MARKETPLACE WITH FEW STUFF STILL OF COURSE
Please contribute guys in answering all the above questions!
THANKS
All credits to Mozilla and FXP ( @freexperia ) teams of course!
few screenshots:
https://www.dropbox.com/s/2ut81qaqjgu3fqo/2015-10-01-11-14-23.png?dl=0
https://www.dropbox.com/s/vvrx7153ql6xjzf/2015-10-01-11-14-33.png?dl=0
few impressions so far:
the bad:
- no camera
- no dt2w
- no extsd support (where I have all my stuff!)
the good:
- seems very nice and promising
- app ops
- nice animations
will keep updating!
Really interested to try this once it's fully functional. Thanks for the heads up!
moly82 said:
- I'm pretty sure you must have a UNLOCKED BL
Click to expand...
Click to collapse
Unlocked bootloader for sure, since you must flash boot.img
Our device is ARIES, if someone doesn't know yet
Testing today...
me too just unlocked the BL!
EDIT: just booted inside FirefoxOS for my first time
things I noticed so far:
see OP
First impressions:
-only English language.. mmmhhh.. and the keyboard is only in english
-you can import your contacts also from gmail... ok.. that's good
-there's a tutorial at the beginning that explains how it works :victory:
-camera just doesn't work (the camera is in use by another app) !!??!!
-some popular apps ready to install... ok, fine!
-to take screenshots you have to press home+power... but I can't get it :crying:
-settings menu is like a hybrid between android and ios
-all the gestures work properly and are different from android, but they're friendly :good:
-the phone is getting very hot now
-arrrgghhh.... force close... the phone rebooted automatically :crying:
yes for sure not ready for daily driver, but seems very nice
for screenshots I just used android normal gesture (power + vol down)
no recovery right? will have to flash FTF to go back to stock?
phone is not hot at all here so far
Problem with camera is in HAL. Logcat... logcat.
In AOSP builds there is no camera, this is the cause.
Seems problem has been solved. Waiting for new build from fxp team then
https://t.co/XGZ6c75N0X
it seems very very basic and not ready for daily use but well better than nothing..! let's see
xperia z3c fxos
right now the bug for the camera on the lollipop build is being worked on, as far as i can find in our bug reports the kk build camera should be working or it would be under QA-blocker. Also for some of the problems you are having such as only english when building make sure to put PRODUCTION=1 it will make it so it flashes all of the languages, that just has to do with not setting the right build variables.
Fxos-QA contributor rep
Sorry i would give you links but i am a new user on this site so i cant...
jamie_fxos said:
right now the bug for the camera on the lollipop build is being worked on, as far as i can find in our bug reports the kk build camera should be working or it would be under QA-blocker. Also for some of the problems you are having such as only english when building make sure to put PRODUCTION=1 it will make it so it flashes all of the languages, that just has to do with not setting the right build variables.
Fxos-QA contributor rep
Sorry i would give you links but i am a new user on this site so i cant...
Click to expand...
Click to collapse
not sure to understand correctly, you mean there is a firefoxos version based on kk for z3c with working camera? where?
because it seems I can find only the lp build in fxp site... thanks! :silly:
moly82 said:
not sure to understand correctly, you mean there is a firefoxos version based on kk for z3c with working camera? where?
because it seems I can find only the lp build in fxp site... thanks! :silly:
Click to expand...
Click to collapse
i just double checked with of the devs, The aires device, you can build the kk version which does have a working camera, you just have to compile it yourself. The lp build currently available on task cluster does not have the working camera, in all honesty the lp kernal version is not fully complete yet, right now the camera is one of those parts that are not fully complete. if you want to take a look the bug number is 1163557 you have to go to bugzilla.mozilla.org it might help explain the situation. right now lp is experimental.
firefox os QA
mozilla rep
Jamie Charlton
thanks mate, will do! and thanks also for the info, it is nice someone from firefoxos project directly is looking around here and share info with us!
unfortunately i'm not skilled enough for building myself, so can just wait for fxp team to build them for us.
afaik devs are working on updated/fixed camera blobs for lp as we speak, so we could have a decent camera available for aosp soon, in that case hope it will land in firefox os too
really looking forward for a usable build of firefoxos for our device, it seems a very nice project... i like firefox, i like opensource, i don't like google at all recently... so hope to find in fxos soon a great alternative! :good: :fingers-crossed:
moly82 said:
thanks mate, will do! and thanks also for the info, it is nice someone from firefoxos project directly is looking around here and share info with us!
unfortunately i'm not skilled enough for building myself, so can just wait for fxp team to build them for us.
afaik devs are working on updated/fixed camera blobs for lp as we speak, so we could have a decent camera available for aosp soon, in that case hope it will land in firefox os too
ht
really looking forward for a usable build of firefoxos for our device, it seems a very nice project... i like firefox, i like opensource, i don't like google at all recently... so hope to find in fxos soon a great alternative! :good: :fingers-crossed:
Click to expand...
Click to collapse
come end of next week i might be able to get you a kk build, i cant say for 100% due to moz is giving me mine next week. If it comes with a KK kernal on it i can see if I can make you one, i dont think it is under nda for the blobs for kk, im not sure 100% though. i just know for the flame device im not allowed to give out builds that have not gone through approval from t2mobile as distributable.
moly82 said:
1. rootable? DON'T THINK SO
Click to expand...
Click to collapse
Yes. rootable.
jamie_fxos said:
come end of next week i might be able to get you a kk build, i cant say for 100% due to moz is giving me mine next week. If it comes with a KK kernal on it i can see if I can make you one, i dont think it is under nda for the blobs for kk, im not sure 100% though. i just know for the flame device im not allowed to give out builds that have not gone through approval from t2mobile as distributable.
Click to expand...
Click to collapse
thanks mate you rock!
will see so, btw no need to hurry for me, as I am taking my z3c to assitance today or tomorrow (broken magnetic port :crying: ) and dunno when I'll see it again... :silly:
moly82 said:
thanks mate you rock!
will see so, btw no need to hurry for me, as I am taking my z3c to assitance today or tomorrow (broken magnetic port :crying: ) and dunno when I'll see it again... :silly:
Click to expand...
Click to collapse
By the time you get it back i hope that i will already have a working build for you.
Also people, if the base image you are using is gotten from mozilla its a 99% chance its rooted, they are left unlocked for testing and development reasons, the only time they are locked usually is when you are getting them from the phone manufacturer also know as a production build, which we do not make.
Mozilla rep
Firefox OS QA
Jamie Charlton
Okay i have looked into it, the only way i can make you a base image is if it is blib free so you would have to get the blobs from Sony. The blobs are currently under nda so there is no way i can share them without getting in trouble. The only way it seems you could get the kk build with a working camera is if you flash back to android and then get the blobs from the device and then from there you would have to add them to the blob free base image.
The project got already discontinued by Mozilla because the not given chance to get close to Android, iOS or WIP
Maybe with a hardboot kernel it could be saved as a stable, second OS with Multirom...
I've been wanting to get into porting ROMs, although I'm not too sure how to go about it. I have a few in mind I'd like to attempt to bring to our device. Does anyone have any resources/links/videos on how to go about porting? Everything would be greatly appreciated
Which ROMs do you have in mind? I might be able to help.
P.S: You can look in the LineageOS porting instructions for our device, if that's going to help you!
proudlytm said:
Which ROMs do you have in mind? I might be able to help.
P.S: You can look in the LineageOS porting instructions for our device, if that's going to help you!
Click to expand...
Click to collapse
A few of the ones I've been thinking would be a good fit for this phone is the Pure Nexus Project, Slim7 (Want to get a fully working build of that going, love Slim7 haha), OmniRom, and lastly a MIUI port once I get the basics down.
I use macOS, but also have a virtual machine for both Windows 7 & 10 and Ubuntu and Fedora so any guides across any platforms help.
fireball0093 said:
A few of the ones I've been thinking would be a good fit for this phone is the Pure Nexus Project, Slim7 (Want to get a fully working build of that going, love Slim7 haha), OmniRom, and lastly a MIUI port once I get the basics down.
I use macOS, but also have a virtual machine for both Windows 7 & 10 and Ubuntu and Fedora so any guides across any platforms help.
Click to expand...
Click to collapse
I know different ROMs use different structures for device trees, but here's a guide to compiling Lineage 14.1 to the G4 Play. This guide is made for Ubuntu 14.04/15.04/16.04, but Fedora might be able to work as well as long as you can get the proper packages installed during the prerequisite steps:
http://wiki.lineageos.org/harpia_build.html
It may not help much with other ROMs, since I'm not sure if the other ROMs support using CM/Lineage based device trees to build, but this will give you the basic instructions on how to download source, get the proprietary blobs/device tree you need, and compile everything to a working zip.
As for actually making device trees for other ROMs to use during compilation, that I don't know myself, and was never really able to find out.
I build on Fedora. If you're using Fedora 25, use these steps to set up a build environment: https://gist.github.com/sultanqasim/09f19221c67c71edd099eb86c6a92467
I doesn't have enougth rigth to post to roms, so will post here.
WARNING! Everything you do, you do at your own peril and risk. I do not bear any responsibility for your faulty devices.
Knox will tick. ROM in alpha and not suitable for every day use.
Installation instructions:
1. Install TWRP
2. Reboot in TWRP (Menu unlock phone - Recovery)
3. Wipe -> Format Data -> write - yes -> Enter
4. adb push <LineageOS> /sdcard
5. adb push <SailfishOS> /sdcard
6. Into TWRP: Install <LineageOS>
7. Into TWRP: Install <SailfishOS>
8. Into TWRP: Install <Audio FIX>
9. Reboot in System
Enjoy!
Sailfish OS Android HAL based on Lineage OS 14.1.
Downloads:
TWRP for herolte
Lineage OS 14.1 for herolte
Sailfish OS 2.1.4.14 for herolte
Sailfish Galaxy S7 audio fix(based on work of painted.man)
Sources:
https://github.com/Driim
Build guide can be found here.
Problems:
1. WLAN worked partially(can't remember network to automatically connect after reboot)
2. Bluetooth not working
3. NFC not working
4. Fingerprint not working (Sailfish problem)
Debug:
In Ubuntu. Connect USB cable. telnet 192.168.2.15 2323 or ssh.
Changelog:
30.03.2018
Update to Sailfish OS 2.1.4.14
GSM calls fix
12.02.2018
Working mobile data and sms.
Great for a start! Have you tried flashing only the Sailfish ROM to see if it works without having to flash LineageOS?
CyanogenLover said:
Great for a start! Have you tried flashing only the Sailfish ROM to see if it works without having to flash LineageOS?
Click to expand...
Click to collapse
It's pointless, the Sailfish OS uses Lineage OS HAL layer to work with hardware, without Lineage OS it won't start.
Tried this. First off amazing job. I was trying to install Android apps but cant find android support on app store
dylanneve1 said:
Tried this. First off amazing job. I was trying to install Android apps but cant find android support on app store
Click to expand...
Click to collapse
I'm focused on hardware support. Android applications did not even look.
lSDriim said:
I'm focused on hardware support. Android applications did not even look.
Click to expand...
Click to collapse
Yeah you're right.
lSDriim said:
It's pointless, the Sailfish OS uses Lineage OS HAL layer to work with hardware, without Lineage OS it won't start.
Click to expand...
Click to collapse
Then you need to extract the components that make up the HAL layer. If you don't know how to do this, you could try asking around XDA or doing some web searching, but I'm afraid that I can't help you by actually doing it; I can only provide suggestions. However, since I'm quite interested, I'll stay subscribed to your post here.
---------- Post added at 04:39 PM ---------- Previous post was at 04:34 PM ----------
Please provide more screenshots!
CyanogenLover said:
Then you need to extract the components that make up the HAL layer. If you don't know how to do this, you could try asking around XDA or doing some web searching, but I'm afraid that I can't help you by actually doing it; I can only provide suggestions. However, since I'm quite interested, I'll stay subscribed to your post here.
---------- Post added at 04:39 PM ---------- Previous post was at 04:34 PM ----------
Please provide more screenshots!
Click to expand...
Click to collapse
I think you do not quite understand. I already extracted them and just wrote the version from which I extracted. So there are no Lineage OS on phone, only Sailfish OS and HAL components from Lineage OS 14.1(only proprietary components).
I update release and add new screenshots.
lSDriim said:
I think you do not quite understand. I already extracted them and just wrote the version from which I extracted. So there are no Lineage OS on phone, only Sailfish OS and HAL components from Lineage OS 14.1(only proprietary components).
Click to expand...
Click to collapse
Thanks for clearing that up. You probably should figure out how to merge the two packages together, so we don't have to flash two separate packages, one before the other. Also, see what you can find out about the remaining problems. Try to get other developers involved. Also, you can always Google, Yahoo, Bing, DuckDuckGo, Yandex, etc. anything you need help with. I find most solutions on the net.
CyanogenLover said:
Thanks for clearing that up. You probably should figure out how to merge the two packages together, so we don't have to flash two separate packages, one before the other. Also, see what you can find out about the remaining problems. Try to get other developers involved. Also, you can always Google, Yahoo, Bing, DuckDuckGo, Yandex, etc. anything you need help with. I find most solutions on the net.
Click to expand...
Click to collapse
Merging of two packets, it's question for Sailfish OS developers, because it's the only way to install Sailfish.
Some people work on solving problems, I also asked about this problems on sailfish porters irc channel. I write this thread to get other developers involved.
lSDriim said:
Merging of two packets, it's question for Sailfish OS developers, because it's the only way to install Sailfish.
Some people work on solving problems, I also asked about this problems on sailfish porters irc channel. I write this thread to get other developers involved.
Click to expand...
Click to collapse
Aren't you a developer?!? Just because you aren't an employee at Jolla doesn't mean you're not developing Sailfish! After all, isn't it opensource?
Admittedly though, I'm a novice too when it comes to developing OSes, however I'm still studying more programming languages. I'm interested in Java, Python, and C++, which may help in diagnosing problems with your build. As for actually applying it, I don't know how I could test it without messing up my S7 Edge.
CyanogenLover said:
Aren't you a developer?!? Just because you aren't an employee at Jolla doesn't mean you're not developing Sailfish! After all, isn't it opensource?
Admittedly though, I'm a novice too when it comes to developing OSes, however I'm still studying more programming languages. I'm interested in Java, Python, and C++, which may help in diagnosing problems with your build. As for actually applying it, I don't know how I could test it without messing up my S7 Edge.
Click to expand...
Click to collapse
Sailfish OS is open-source based, not all parts of Jolla is opened. But open part must be enougth to port new device.
To develop new Oses you need to know C(most of the system programming), C++ and Bash. You could try do S7 Edge port, but it better to have special phone fo this
I looked how can I separate Sailfish from Lineage OS and found Halium projects, that based on Ubuntu Touch. They start Android HAL in container, so system is more clean, now I am testing Halium build.
lSDriim said:
Sailfish OS is open-source based, not all parts of Jolla is opened. But open part must be enough to port new device.
Click to expand...
Click to collapse
So, what parts of the OS are opensource? Just curious; I know very little about Sailfish source code.
To develop new Oses you need to know C(most of the system programming), C++ and Bash. You could try do S7 Edge port, but it better to have special phone fo this
Click to expand...
Click to collapse
I'm learning C++, and I know some Bash. I might be able to diagnose problems if you'll output some log info. Try to be as descriptive as possible.
I looked how can I separate Sailfish from Lineage OS and found Halium projects, that based on Ubuntu Touch. They start Android HAL in container, so system is more clean, now I am testing Halium build.
Click to expand...
Click to collapse
Ah, Ubuntu Touch! That was a good venture. Too bad it didn't last. Let me know if it works better as the HAL for your project.
CyanogenLover said:
So, what parts of the OS are opensource? Just curious; I know very little about Sailfish source code.
Click to expand...
Click to collapse
Almost all except UI.
I'm learning C++, and I know some Bash. I might be able to diagnose problems if you'll output some log info. Try to be as descriptive as possible.
Click to expand...
Click to collapse
Bad idea, to much logs. If you not familiar with ofono, pulseaudio and etc, logs will not help.
lSDriim said:
Bad idea, to much logs. If you not familiar with ofono, pulseaudio and etc, logs will not help.
Click to expand...
Click to collapse
Not the entire logs! Just the ones with the errors that are produced from whatever needs fixing. Some commands that output constant log updates have filters. For instance, one way I diagnose a problem on Android is connect the device to my laptop, run "adb logcat *:E", repeat the action on the device that works improperly, then stop the output (usually CTRL + C) and scan the errors for the ones about my issue. If there is still too much to sift through, I try again, setting more filters. You can learn what filters you can apply by typing " adb logcat -h".
I don't know if adb works with Sailfish, but you might could discover logcat or something similar that will filter logs and output only the relevant information. As for what you just mentioned, I can diagnose issues with many Linux-based programs. I use Ubuntu. :victory:
As for the Wi-Fi not reconnecting; On the s7 atleast (probably more) there's a line in the build.prop "ro.securestorage.support"
Change that to the opposite of what it's on
solution for audio
I found solution for audio problem.
You have to edit /system/etc/audio_policy.conf:
- Delete AUDIO_OUTPUT_FLAG_DEEP_BUFFER flag on primary audio device
- Comment sections tms and playback_record
You also can pass argument config to pulseaudio-modules-droid and set location to your correct config file instead of editing vendor file.
continua el proyecto esta bien bueno 7u7
lSDriim said:
Almost all except UI.
Bad idea, to much logs. If you not familiar with ofono, pulseaudio and etc, logs will not help.
Click to expand...
Click to collapse
plss for s7 edge
Mujeeb64 said:
plss for s7 edge
Click to expand...
Click to collapse
I do not have Galaxy S7 Edge, but someone else can do it.