Fairphone released the code source, binary drivers (proprietary blobs) and build intruction of the Fairphone 2.
In future they will also find instructions on how to contribute, ready-to-use builds (maybe including contributions) and information on other Fairphone open source projects.
Dedicated website : code.fairphone.com
Hey guys! I wonder why there's no active devoloping going on. The code is released, the hardware and software is completely open and if I'm not mistaken the phone has been shipped allready. So where are the custom ROMS?
I'm afraid there are not enough FP2s out there to attract custom ROM developers. What a pity, it would be so much easier to develop custom roms with all the Software being open source. Maybe there will be a SailfishOS ROM in the near future. And I think one of the official FP2 devs is trying to port CM....
Gesendet von meinem FP2 mit Tapatalk
Lazerus2005 said:
I'm afraid there are not enough FP2s out there to attract custom ROM developers.
Click to expand...
Click to collapse
Yeah that's probably the problem. It would be a nice phone if there were more custom ROMs available.
It's definetly such a pity that there isn't any dev that is interested in this phone... If only i could code!
Well, we have SailfishOS, Ubuntu Touch and LineageOS running on the FP2. And we have 2 official flavours of Android (Google and AOSP) oob.
Related
Hi, I've just received my OPO on the 27th. I was really interested in Android development when I had my Nexus 5 and started building my own AOSP ROM, I've been looking into doing the same for the OPO but am unable to find an actual way of building AOSP with Google's code. I know OPO released their AOSP kernel source here: https://github.com/OnePlusTech/android_kernel_oneplus_one and CyanogenMod has thiers here: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974 but I'm unable to work out a way of including these into my AOSP build and I would prefer to not build CM.
Note: I'd like to build AOSP myself, I'm fully aware that there is a current official OPO build available.
Thanks in advance,
Lewis
LewisD94 said:
Hi, I've just received my OPO on the 27th. I was really interested in Android development when I had my Nexus 5 and started building my own AOSP ROM, I've been looking into doing the same for the OPO but am unable to find an actual way of building AOSP with Google's code. I know OPO released their AOSP kernel source here: https://github.com/OnePlusTech/android_kernel_oneplus_one and CyanogenMod has thiers here: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974 but I'm unable to work out a way of including these into my AOSP build and I would prefer to not build CM.
Note: I'd like to build AOSP myself, I'm fully aware that there is a current official OPO build available.
Thanks in advance,
Lewis
Click to expand...
Click to collapse
It's advisable that you create your own tree from the CAF MSM8974 using CM GPS and other drivers and build CAF AOSP. Otherwise, it's close to impossible/very difficult. Pure AOSP is again near impossible/very difficult for non nexus devices.
Thank you very much for the reply, so building AOSP is pretty much impossible then?
I was having a look around on the internet last night and came across this: http://developer.sonymobile.com/kno...uild-aosp-kitkat-for-unlocked-xperia-devices/
Would there be a way of adapting this guide to allow for an easier build process of AOSP for our device? The other confusion that I face is if it's impossible to build AOSP for the OPO then how are ROMs such as this available?
LewisD94 said:
Thank you very much for the reply, so building AOSP is pretty much impossible then?
I was having a look around on the internet last night and came across this: http://developer.sonymobile.com/kno...uild-aosp-kitkat-for-unlocked-xperia-devices/
Would there be a way of adapting this guide to allow for an easier build process of AOSP for our device? The other confusion that I face is if it's impossible to build AOSP for the OPO then how are ROMs such as this available?
Click to expand...
Click to collapse
VanirAOSP uses CM trees as of now. Again, CAF AOSP is basically AOSP for non nexus Qualcomm devices., and any experienced dev can whip up a tree and get it working. Also, reaally good devs can/may be able to port AOSP if they wanted. It's a matter of whether they want to do it or not.
That link is for Sony devices only because Sony already provides CAF trees as an OEM so devs can build.
rudi_j7 said:
VanirAOSP uses CM trees as of now. Again, CAF AOSP is basically AOSP for non nexus Qualcomm devices., and any experienced dev can whip up a tree and get it working. Also, reaally good devs can/may be able to port AOSP if they wanted. It's a matter of whether they want to do it or not.
That link is for Sony devices only because Sony already provides CAF trees as an OEM so devs can build.
Click to expand...
Click to collapse
Ah yes, I see what you're saying now. Thanks for clearing this up for me! I just noticed when I looked at the VanirAOSP ROM thread that it states CM for it's credits, haha. I apologize for my ignorance.
Hello
I would like to create my first rom for oneplus one but without modification from OMNI or CM, basically vanilla rom. but I have some doubts.
Can I create a rom based on AOSP with device tree from OMNI/CM right?
Thanks!
Will Xiaomi release kernel sources fully for this smartphone & therefore able to have active rom development (including Android M 6.0 roms) in the near future ?
(Kernel sources for the Xiaomi Mi3 & Mi4 were released very late and not in full and are the reason I believe that many Lollipop roms for these devices are not stable).
I think it depends on whether the device goes international. They were quick to release the sources for the Mi4i, and that is the only phone they officially sell internationally. That said, at least it uses the most common SOC of 2015.
Does it help that it has the same soc as the nexus 5x?
ermacwins said:
Does it help that it has the same soc as the nexus 5x?
Click to expand...
Click to collapse
It helps a little bit maybe, but the problem is all the other stuff inside the phone is different. You still need proper sources from Xiaomi.
M.
Do Xiaomi devices have root "built-in" ?
I'm interested in ROM development, too, but for the first months having root would be enough.
Giocarro said:
Do Xiaomi devices have root "built-in" ?
I'm interested in ROM development, too, but for the first months having root would be enough.
Click to expand...
Click to collapse
I have seen a guide on MIUI forum: "How to flash TWRP Recovery and Super Su(Root) on Xiaomi Mi4C"
Having access to kernel will also mean ir blaster will work on custom roms?
ermacwins said:
Having access to kernel will also mean ir blaster will work on custom roms?
Click to expand...
Click to collapse
Don't count on that. Many device that have kernel source and ir blasters still don't work on aosp based roms. Due to all the drivers for the hardware being closed sourced.
zelendel said:
Don't count on that. Many device that have kernel source and ir blasters still don't work on aosp based roms. Due to all the drivers for the hardware being closed sourced.
Click to expand...
Click to collapse
When we say kernel source, is that pertaining to the soc?
ermacwins said:
When we say kernel source, is that pertaining to the soc?
Click to expand...
Click to collapse
The kernel covers all aspects of the device in one form or another.
zelendel said:
The kernel covers all aspects of the device in one form or another.
Click to expand...
Click to collapse
Let's say xiaomi is taking long to release their kernel source but the source for nexus 5x soc is out, would that be enough for aosp rom?
ermacwins said:
Let's say xiaomi is taking long to release their kernel source but the source for nexus 5x soc is out, would that be enough for aosp rom?
Click to expand...
Click to collapse
No it won't. You will also need the device tree for this device. It's not how long it takes for them to release it that I would be worried about. It's if the source is complete and not broken like they are known to release. They have a habit of release broken source to force users to use miui. If you look at other devices from this OEM it takes months some times a year before they release it and when they do it is broken and devs have to take weeks to get it even remotely working. Then there are still bugs that are never fixed.
zelendel said:
No it won't. You will also need the device tree for this device. It's not how long it takes for them to release it that I would be worried about. It's if the source is complete and not broken like they are known to release. They have a habit of release broken source to force users to use miui. If you look at other devices from this OEM it takes months some times a year before they release it and when they do it is broken and devs have to take weeks to get it even remotely working. Then there are still bugs that are never fixed.
Click to expand...
Click to collapse
So having an aosp based rom as a daily driver is out of the question?
ermacwins said:
So having an aosp based rom as a daily driver is out of the question?
Click to expand...
Click to collapse
isn't the Broken OS ROM by TS Team AOSP based ?
Of interest:
[News] Mi 3/4/Note Kernel Source Code Released! Next to Be, Mi Note PRO, Mi 4c/S:
http://en.miui.com/thread-235127-1-1.html
Don't sceptical, I reconstruct Redmi 2 kernel source without any help from Xiaomi. They released Redmi 2 kernel source for KitKat when my device already run "fully open source" and almost bug free Marshmallow :laugh:
Hi, i always wanted to know but Never ask..
Now i want to know about and sorry of simple demand.
What is the diference between an official ROM and unofficial ROM ?
And also diference of thread Android development with original Android développement.
Thanks.
green2005 said:
Hi, i always wanted to know but Never ask..
Now i want to know about and sorry of simple demand.
What is the diference between an official ROM and unofficial ROM ?
And also diference of thread Android development with original Android développement.
Thanks.
Click to expand...
Click to collapse
It's actually fairly simple... an "official" ROM is one that is authorized, and often supported by, the development team of that ROM and the device is considered an "officially supported device".
But since the source code for these ROMs is open source, anyone can build or compile them for their device or another device that isn't officially supported. The ROM is not supported by the development team, but by the ROM maintainer/builder only. These types of builds that are either not officially supported devices, have modified the source code outside of the original developers guidelines, or not authorized by the development team are called "unofficial". They may even be by the same maintainer as the official version, but they modified (perhaps used a different toolchain) from the original guidelines for the ROM and it cannot be considered official any longer.
Really, it's boils down to: is the device supported and authorized by the core ROM development team... if yes, it's official... if no, it's unofficial.
Android Original Development is supposed to be for ROMs, kernels, and other projects that are completely original by the author, or authorized originals... Cyanogenmod/LineageOS is a good example of this... ROMs like Resurrection Remix are not considered "original" because they are based on Cyanogenmod, thus they just go into the Android Development section.
If in doubt about what the forum groups are for, read the sticky posts in each group.
Thanks now it's more clear
I'm a kind of lazy man and not good in English. Building a whole rom from source code can be a hard work for me since I have no experience about dealing with any programming except porting rom for a device. I haven't done this for a long time since 4 years ago. But Google's project treble was an brilliant news for me.
I want to try for a Chinese rom called Smartisan OS, and also noticed that Pixel/XL has so less developer, unlike Nexus5, which has so many custom roms for flashing.
But I don't understand project treble completely, only heard the news. Is there any official or unofficial documents teaching us to use this function for developing custom-made roms?
Will it be necessary to build a rom from source code from project treble, or just simply doing some copy and paste (kind of like the roms I've made for a Chinese tablet. I was only unpack the kernel as well as rom zips and paste some stuff then repack them, it did worked)?
BTW, Smartisan OS seems to be based on Android 7.x and no official news about supporting project treble, I don't know can it be done if the target rom don't support project treble at all.
Forgive me if I'm too nasty, just curious.
Mi 8/Mi 8 Explorer Edition/Poco F1 Same Branch
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/dipper-o-oss
najjurocks619 said:
Mi 8/Mi 8 Explorer Edition/Poco F1 Same Branch
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/dipper-o-oss
Click to expand...
Click to collapse
Blimey! That's a very good sign!
Hopefully they're intact and usable
thesoupthief said:
Blimey! That's a very good sign!
Hopefully they're intact and usable
Click to expand...
Click to collapse
Indeed, Hoping for great future and development for this device, The cheapest SD 845 yet.
isnt this a security lapse
prabaharanaece said:
isnt this a security lapse
Click to expand...
Click to collapse
Lol are you joking? Xiaomi have themselves released the kernel sources. How does that make it a security lapse when they themselves announced this during the phone launch?
Great news! Hope to see LineageOS soon for this phone.
kishore1998 said:
Lol are you joking? Xiaomi have themselves released the kernel sources. How does that make it a security lapse when they themselves announced this during the phone launch?
Click to expand...
Click to collapse
It is rather a question from me, I know mi released the codes but question is can it be used by someone for hacking this phone. I guess it would be more easier for the hackers now.
prabaharanaece said:
It is rather a question from me, I know mi released the codes but question is can it be used by someone for hacking this phone. I guess it would be more easier for the hackers now.
Click to expand...
Click to collapse
POCO F1 is not the only phone with it's kernel source released. You will find kernel sources released for many phones by different brands (Sony, Samsung, LG, OnePlus and so many more). The purpose of releasing the source is to accommodate custom ROM and Kernel development by developer community (like XDA) and find out vulnerability (if any) in the process. Any vulnerability found is usually patched in updates. Yes the source can be used to compile a kernel or ROM with malicious code or an app which'd try to exploit the vulnerability but it will only affect those who'd install any such app/kernel/ROM. Now any flashaholic you'd meet will tell you how they'd only install apps from trusted sources and flash ROMs/Kernels available on XDA etc. In nutshell, I don't think trying to hack a phone using kernel source is worth it as it targets very limited people who are cautious enough on what to install on their phones making it more difficult to hack. Any developer can enlighten you more on the issue as I might be totally wrong on the issue too.
P.S. It's because of such source code releases that community like XDA is thriving.
prabaharanaece said:
isnt this a security lapse
Click to expand...
Click to collapse
All linux based kernels are open source
Also it is mandatory for OEMs to release kernel sources per GPL license rules.
I got my phone today, waiting for some awesome development..
Thank you everyone for comments :good:. I got my phone today as well
Will only buy it if any rom(i wish for Omni) is built from sources(not ported rom) and officially supports Treble <3
Otherwise simply useless phone for me :X
Would suggest the same for others too
xuser_ said:
Will only buy it if any rom(i wish for Omni) is built from sources(not ported rom) and officially supports Treble <3
Otherwise simply useless phone for me :X
Would suggest the same for others too
Click to expand...
Click to collapse
All roms are build from aosp and other sources, this is not 2012 where ported roms exists here. What are you talking about? Also, the phone is launched with 8.1 so it officially supports treble out of the box. You high or what?
Btw: good to see early release of kernel source but on the other hand, the unlocking of bootloader showing me 30 days (720hours). How will I live for 30 days using MIUI?