Hi all, this is a question that belongs in the dev forums, mod please move if you'd like.
I'm trying to compile a ROM from AOSP source for my tablet and need to get the device's proprietary binaries. What is the success rate of using proprietary binaries from an older version of Android (5.x) on a newer build (7.x)?
My device (T330-NU) only has binaries available for 5.x. Logically I would think that I can't use these on newer Android builds.
If the answer is that I cannot use the binaries from 5.x in my 7.x build then how do unoffical ROMs such as CM14 for my device seem to work? Are these binaries/drivers created from scratch? In these situations do the developers use a generic driver?
tyia
Bump since moved to another forum
Related
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.
I am trying to run a program which require at least kernel version of 3.11 and so far now I cannot find any android phone devices which fullfil this requirement. Furthermore I need a list of devices for which cyanogenmod official/unofficial is available alongwith kernel source code. I would really appreciated the developers on this forum to put those devices.
Thanks alot.....
Hi, I am currently building custom rom for my Lenovo a7000-a (aio_row) and I have a few questions regarding the device section of the AOSP build.
1. I have seen that to build the custom ROM for a device, I would need the following .mk files from topic "Android device configuration AOSP" in Stackoverflow.
However, from the device configuration/device-tree(?) from user rohantaneja in Github, I see that I would also need files that look like drivers for the devices based on the files on that github. May I ask how would I obtain these files?
2. Would flashing an arm64 generic build of custom AOSP into any Android device work or not? If so, why?
Seems like the amount of knowledge that I faced off with confused me a lot.
Any help is appreciated.
Thanks in advanced.
i'm noob here, so... sorry if the question sound silly...
is it possible to have an old qualcomm device (msm8610) a latest linux kernel such as 5.10 or 5.11 if i don't need the baseband functionality? is all the other driver is also closed source? i'm asking this because i have an old unused phone that i want to use to learn about kernel compiling and learn about hardware and stuff, and i just don't want to waste my time if such thing is impossible (compiling latest kernel for old phone)...
pink101 said:
i'm noob here, so... sorry if the question sound silly...
is it possible to have an old qualcomm device (msm8610) a latest linux kernel such as 5.10 or 5.11 if i don't need the baseband functionality? is all the other driver is also closed source? i'm asking this because i have an old unused phone that i want to use to learn about kernel compiling and learn about hardware and stuff, and i just don't want to waste my time if such thing is impossible (compiling latest kernel for old phone)...
Click to expand...
Click to collapse
If the stock kernel source code for your device is available to the public, you can use that to compile a new custom kernel for your device. But, an old device may not be able to use the latest kernel. If the stock kernel source code for your device is not available, you can't build a new custom kernel for your device.