I don't know a whole lot about how android phones work so this is probably a stupid question.
If the android operation system code is open source and available for anyone to download what's stopping people from putting pure AOSP goodness on any given phone? Is it the kernel or bootloader or what?
Fe_Man said:
I don't know a whole lot about how android phones work so this is probably a stupid question.
If the android operation system code is open source and available for anyone to download what's stopping people from putting pure AOSP goodness on any given phone? Is it the kernel or bootloader or what?
Click to expand...
Click to collapse
from my understanding it has to be completely recoded or whatever to run on the hardware of a new phone, I think Cyanogen and crew just supply the base and framework to build on... but yes its out there for anyone to try and port, typically takes a team of devs with different specialties
blazing through on my VZ Droid Charge 4G
Kernel, RIL, and potentially a number of other things.
Just like drivers has to be ported for Linux on any PC (if the company didn't already code one for it), drivers has to be ported to a pure AOSP ROM from a TouchWiz source (which is still Android-based).
Most company-applied UIs to Android are deep in the system, therefore, you can't just take some files and put it into an AOSP ROM and have it magically work (known as kanging from another ROM), but you have to write in some stuff and build it specially for AOSP before it works.
Hi,
I want to build AOSP including google apps/services to make a similar factory image as possible as.
First time, I just build a AOSP with sevral google apps but It's very insufficient.
(code.google.com/p/aosp4nexus5/wiki/AOSPforNexus5)
I can see some error logs because of missing libraries, apks.
and I found that many proprietary blobs are not founded on AOSP.
Maybe I could porting it one by one manually , but it seems very annoying work...
I just want to build AOSP with google apps for nexus 5 5.0.1.
Are there any easy way for it?
Also very little tweaked custum rom maybe helped me,
(I think usually custom roms are so different from stcok even if they say simple.)
I'm a noob and worry about my silly question.
Thank you.
I have them included in my vendor directory. You can take a look at my git and figure out what you need...
https://github.com/grogg/platform_vendor
Hey,
i'm just curious about what the title describes. First of all.
What do i really need:
-kernel sources
-binary blobs (extractable)
-recovery / boot.img (extractable)
Let us just talk about the fairphone 2. Additional to the things mentioned we get the full source code of the OS (which i do not need?).
Where do the difficulties lie? For my understanding we just take the kernel sources, the official cyanogenmod (e.g.) source code, the binary blobs and the recovery / boot.img.
How difficult would it be to port Cyanogenmod to the fairphone 2.
Why is it difficult to port a device with existing (again cyanogenmod just as an example) cyanogenmod to a newer Cyanogenmod (Android) version?
I ask this to estimate/evaluate/judge (don't know the right term) the effort needed to do this. I think i'd be able to do that if i put enough work into it (i "speak" c and java), but i just need some answers.
Especially for example why it is more difficult to port Android 6 instead of Android 5 (which is the currently running Android version)
Thanks!
bigCrash
Has nobody an answer? Just one?
Im specifically interested in why it is more difficult to port e.g. cyanogenmod if there is only an older version of stock android and how important the kernel is? Why do we need kernel sources? Can't one just self-compile a kernel.
Where are the limits if i have a device running 4.2. Why can it possibly run 5.1 but not 6? Is the kernel limiting? Or only the effort to realize such a thing.
Thanks!
bigCrash
Hello there,
I am currently having a One Plus One. I have multi-rom utlity which allows me to have multiple android OS installed.
Currently the cyanogenmod based custom Marshmallow Rom I use (http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700) has switched over to using stable CM branch as their rom base. So this requires using Super SU for root access. Unfortunately Super Su is not compatible with Multirom implementation for OPO.
One suggestion provided was to try building the custom rom from source with user-debug flag. Meanwhile I came across two build.prop values (ro.build.type=userdebug ; persist.sys.root_access=1) which I hoped would enable inbuilt superuser without rebuilding the rom from source but they did not work.
So for now, there seems to be no other way around building from source ( I wanted to avoid this as much as possible because I have a very slow Internet access downloading 30 GB or so for the ROM alone will take a month for me).
So here are my 2 questions:
1> The rom developer in the thread mentioned in 2nd para, talks about 2 source (Kernel and the rest). When I looked at the manifest, they talk about replacing something. So does this mean I need to download the cyanogenmod sources as well or does repo sync take care of that automatically ?
2> I assume the kernel and rom need to be built separately. Can the "userdebug" mode be enabled only by rebuilding the kernel and then placing it with rest of the rom build zip provided by the developer to avoid rebuilding the whole rom ? or better yet flash the my userdebug kernel again after the normal rom installation ?
Thanks In Advance
crazydude10 said:
Hello there,
I am currently having a One Plus One. I have multi-rom utlity which allows me to have multiple android OS installed.
Currently the cyanogenmod based custom Marshmallow Rom I use (http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700) has switched over to using stable CM branch as their rom base. So this requires using Super SU for root access. Unfortunately Super Su is not compatible with Multirom implementation for OPO.
One suggestion provided was to try building the custom rom from source with user-debug flag. Meanwhile I came across two build.prop values (ro.build.type=userdebug ; persist.sys.root_access=1) which I hoped would enable inbuilt superuser without rebuilding the rom from source but they did not work.
So for now, there seems to be no other way around building from source ( I wanted to avoid this as much as possible because I have a very slow Internet access downloading 30 GB or so for the ROM alone will take a month for me).
So here are my 2 questions:
1> The rom developer in the thread mentioned in 2nd para, talks about 2 source (Kernel and the rest). When I looked at the manifest, they talk about replacing something. So does this mean I need to download the cyanogenmod sources as well or does repo sync take care of that automatically ?
2> I assume the kernel and rom need to be built separately. Can the "userdebug" mode be enabled only by rebuilding the kernel and then placing it with rest of the rom build zip provided by the developer to avoid rebuilding the whole rom ? or better yet flash the my userdebug kernel again after the normal rom installation ?
Thanks In Advance
Click to expand...
Click to collapse
Greetings,
Please read the Sticky threads for XDA Assist. This is not a help desk. XDA Assist is for helping new members or visitors navigate this site. You are a Senior Member and therefore you should know how to use the search feature and find the correct thread to ask your questions.
Thanks for understanding.
Thread closed.
LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in the products you find here before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, we will laugh at you. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- Make a backup of your important files
2 - Unlock bootloader with this guide
3 - Flash the TWRP, link here
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package ARM64 > 7.1 > Micro and below: visit OpenGAPPS
If during the gapps flash it gives you an error then in the TWRP terminal or on the adb shell you have to execute this command: "mkdir /tmp/bin"
Download:
Releases · XRedCubeX/android_device_meizu_m5c
Contribute to XRedCubeX/android_device_meizu_m5c development by creating an account on GitHub.
github.com
Working:
Boots
Storages
Bluetooth
Wifi
GPS - GNSS
Audio
NOT Working:
Camera
Hotspot
Offline Charging
Special Thanks
LineageOS
Moyster for device trees
Device Tree:https://github.com/XRedCubeX/android_device_meizu_m5c
Vendor Tree: https://github.com/XRedCubeX/android_vendor_meizu_m5c
Assim que possível, irei testar!
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
thiagosousa777 said:
Hi Red. I was taking a look at the ROM repository on GitHub, and saw that the default branch is now named cm-13.1. So, are you now working on an Android 6.0 ROM for the M5c?
Click to expand...
Click to collapse
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
XRed_CubeX said:
I have a slight indecision, now I can not carry on the Custom ROM because I do not have the right PC but when I am able to compile it, I will evaluate which one can work better
Click to expand...
Click to collapse
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
thiagosousa777 said:
I see. I would say that in the long run Lineage 14 would be more worthwhile, since Android 6.0 is becoming outdated, with no support for some apps. But really, I just wanted a ROM to replace Flyme, and its bugs. Also, many of the apps I use don't work, or don't work right on Flyme...
These days I was taking a look at /e/ OS. I've been thinking about venturing into porting this ROM to the M5c. For me it would be a challenge, since I've never done this before. But unfortunately at the moment I also don't have a PC that meets the requirements to compile the ROM
Click to expand...
Click to collapse
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
XRed_CubeX said:
I find it useless, just use lineage without gapps and it will be better than /e/, then anyway I don't know where to find the manifest
Click to expand...
Click to collapse
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
thiagosousa777 said:
You are right. However, /e/ has some nice features like e account synchronization, an app store, microG, and some of their apps... Of course we could get that with LineageOS, but it is interesting how /e/ already brings that well integrated and ready.
By the way, I am also looking at other non-Android systems, like Ubuntu Touch...
Click to expand...
Click to collapse
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
XRed_CubeX said:
Ah beautiful those non-android systems yes, unfortunately we have to forget them because of the prebuilt kernel and unavailable sources
Click to expand...
Click to collapse
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them, don't you?
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
thiagosousa777 said:
Well, from what I've been reading the process is similar to porting LineageOS. You just need the kernel sources and the device specific binary blobs. I'm guessing you know how to get them.
And the interesting thing is that there is a layer, called Halium, that interacts directly with the hardware. And that is actually what you should port to the desired device. Then you can install any Linux system on top of this layer, like Ubuntu Touch, Plasma Mobile, etc, and these are distributed pre-compiled.
Click to expand...
Click to collapse
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
XRed_CubeX said:
Mhh ... good, you are informed, however the vendor blobs are bull**** to take, the problem is the kernel sources but Meizu has not released them. However, some time ago I booted a Custom kernel based on ALPS (A custom AOSP from Mediatek to be clear) but the touchscreen doesn't work and I'm looking for a solution around but that I can't find
P.S: Fixing that kernel has great potential, forget android 7, you could also boot android 9 with sources, but as long as they are still working
Click to expand...
Click to collapse
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
thiagosousa777 said:
I confess I didn't quite understand one thing: so how did you port LineageOS to this device? You didn't need the kernel sources?
Click to expand...
Click to collapse
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
XRed_CubeX said:
At the time I was doing this lineage, I was with the prebuilt kernel, week ago I had done this kernel port to a twrp and the touch was not working so I left the device alone
Click to expand...
Click to collapse
Thanks for the clarification! It is a shame that Meizu does this (I wonder if they are not violating the terms of the Linux GPL license by distributing the kernel without publishing the modifications made to the source code).
Anyway, if a solution to this kernel problem related to the touch screen comes up, please let me know. In the meantime I'll keep reading Halium's documentation until a solution comes along, or until I get a compatible phone.
Great work!
Hello. I've been testing this ROM on my M5c and love it. The ROM is very good, fluid, lightweight... the only problem is that the camera doesn't work, as well as the cellular network data. Congratulations for the excellent work.
The ROM will no longer receive bugfixes?
pls compile
publish a release