Hello,
My device is a Lenovo Yoga Tab 2 830f running stock Lollipop 5.0 at the moment. Bootloader unlocked and permanent TWRP recovery.
I am trying to learn about Android development while building CM13 for this device. I am using the following as my references:
surdu_petru's TWRP recovery
Olivier's CM12.1 port
Lenovo's open source code for Yoga Tab 2
CyanogenMod's porting guide
I have the following questions:
* What exactly are we supposed to do with the files in the archive supplied by Lenovo?
* Why did Olivier start porting CM12.1 instead of CM13? Also, why x86 instead of x86_64?
* Is there any agreed-upon device configuration I should be using for this Baytrail tablet? How about this BoardConfig.mk for Minnowboard Max from Intel Android-IA?
The CyanogenMod porting guide is not exactly specific on any particular strategy how to set up the BoardConfig.mk and other files in ./device/. I get it that it's trial and error for the most part, but is there any general guideline I should be following?
I expect this learning experience to take at least a couple of months, so I'll be keeping this thread open for more questions as soon as I have them.
Hello, I am also interested in working on this device. I am currently trying to build using these instructions: https://forum.xda-developers.com/th...-cyanogenmod-12-1-lenovo-yoga-tablet-t3333360
Related
I was going through the xdadevelopers forums when I saw that the process of installing ROMs seems of be device dependent. Can someone please explain me why it is so?
More specifically, shouldn't the process of installing a pure Android ROM (AOSP) be the same on every device since all of them are based on the ARM architecture.
I haven't installed an android ROM before, but I am trying to understand why the process isn't similar to installing a Linux based OS on my computer.
I recently bought an Android tablet (HCL ME X1) to experiment with ROMs but later realized that there aren't ROMs for this device. Can someone let me if I can use the ROMs of any other device for this?
Because all different models have different hardware so the rom has to be specific to that device.
Sent from my GT-I9100 using Tapatalk
Thanks for the reply stylez.
So I guess if I want to develop a custom ROM (say an AOSP ROM) I will need the device drivers which my vendor wrote.
Is there any way of identifying the vendor specific drivers of my device? I am using an HCL ME X1.
hello all
i like to develop since 9 years old. Actually i am 24. I don't understand well the basics of Android and propietary devices. I used to install CM on all my family's devices, but always unofficial builds and not selfKANGs. Since 1 week ago, I am trying to build the the CM's 11.0 with no luck. Then i went to official google's developers site of android, and finally i got a system compiled and ready to install.
but now, before to push the flashing key, i am doubting about all... i mean, there'r a lot of steps I havent done:
1. obtain propietary binaries from my actual installation
2. not sure about if built the correct official version or compatible for samsung galaxy s iii (gt-9300)
3. i just wanted to add support for a S3C USB Host HUB for connecting my keyboard and mouse into my S3's micro-usb port.
so, now that i have obtained a lot of curiosity about that world, i want to learn more and more... but haven't anything clear at all.
then, can you please answer me the following questions?
1. why everyone is installing CM in S3? And not official android version?
2. how can I configure and add support to my USB host hub into the correct version of the kernel for the actual 4.4 KitKat software (CM-11.0) of my S3's?
3. can you explain me why can't I compile CM-11 or CM-10.2 with my Ubuntu Server 14.04 ? Lot of errors...
I would have more time to ask and ask, but I need to stop here.
Thanks to all for all the information in the posts I have read until now. And for the future's ones.
See ya,
Abel.
Hello guys.
This question is specially for devs or advanced users with development skills.
My question is related to the kernel source of one of my devices, Huawei Mediapad T1 10 (codename: hwt1a21l). I got the kernel source from the oficial Huawei website and uploaded it to a github repo. My device, which has a msm8916 chiset, doesn't have any development (roms, recoveries, device tree, etc) and his rom, EMUI 3.0, is based on Kit Kat 4.4.2.
I have been trying to bring development for this tablet many months ago because the stock rom is too deprecated for the hardware that has, with the msm8916 there is a huge potential to bring it a lot of development.
Well, i'm going to summarize my problems when trying to bring development for the device:
To get started development, for example a LineageOS build i needed a solid base to start with: device tree, propietary blobs and kernel source, so i got all of them. I ported the device tree from another one very similar to mine (with the same chipset), extracted the propietary blobs with the build tools from the source and got the kernel source from the Huawei website. So everything seemed to be good, but when i start the build process with my Linux machine (repo sync > source build/envsetup.sh > breakfast hwt1a21l > brunch hwt1a21l) i always receive thousands of build error by the kernel source, and i have been fixing (or at least avoid) a lot of them but it never ends, so i don't know if it's worth to keep trying to "fix" them or if i'm wasting my time.
So, what i have been trying to do: i have been trying to build a LineageOS 14.1 and TWRP recovery with my device tree This: Mustang-ssc/android_device_huawei_msm8916-common ported from this one from @dianlujitao : dianlujitao/android_device_huawei_msm8916-common and the specific kernel source for my device downloaded from the Huawei website Mustang-ssc/android_kernel_huawei_hwt1a21l. Here ends the summary.
So after a lot of hours, days and nights over the last months trying to make progress with this and not getting any help from the few devs i asked after seeing my lack of progress i decided to publicly ask for help.
The questions:
1. I have the official kernel source (Mustang-ssc/android_kernel_huawei_hwt1a21l) which i didn't have success to compile it, and then i saw the kernel source from a device almost identical to mine (same chipset, brand, ram, ...) (dianlujitao/android_kernel_huawei_msm8916). Can i use that kernel source as a base for my device after porting the specific configurations of my official kernel source (defconfig, drivers, libraries)? That one is much more updated and probably optimized than mine, but i don't know if it's possible to adapt a kernel source from other device using your kernel source.
2. This may be a dumb question: my device has Kit Kat 4.4.2. Is there any link between the kernel source and the android version the device has? I mean, i don't know if i should do something to adapt my kernel source for newer android versions (Marshmallow, Nougat) of if it's ok to just build with it without any change.
If you read it all, congratulations, you're awesome
Still waiting for a reply
Hi, I just set up a build environment to be able to compile LineageOS from source for my Galaxy S3 (I know it's an old device, but I'll move over to a Galaxy S4 as soon as the replacement screen comes in the mail). I followed the official instructions on LOS's website for my particular device, without knowing I wouldn't be able to build the latest version (15.1 at this point in time) because they only support 14.1 for the Galaxy S3. So my question is: is there a way I can "port" a newer version of lineageos, in this case, 15.1 to a device that is already supported by 14.1? If so how? I'm new to the rom building community and I've always relied on other people's builds but I want to move on to building my own, that implies that I have some basic knowledge of linux commands and computers in general, but if you could point me to a comprehensive tutorial or just write instructions on how to do it
FYI I'm using Google Compute Engine's VM through SSH to build but I can also free up some space on my physical machine's SSD and build from there if that's easier.
Thanks.
Hello all,
I have a question regarding compiling the android source. This is mostly a general question that can be applied to any device ; however, the device I will be using is the Ascend Mate 7.
I recently got an old Ascend Mate 7 from a friend that I can do what ever with. So, I figured I would try to build Android from source and then flash it to the device.
I have already downloaded the source code. I am about to build the source for the Ascend Mate 7. Then, I found out that I might need to know the Device tree? There seems to be some conflicting information regarding this. Using google's guide, all I need to know is the code name for the device and there we go. We can compile the source! (Woot!)
On the other hand, other guides state that I need to download the device identity such as the tree, vendor, and kernel and include this in the source. (See this guide on xda website: https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763) In another guide, I need to setup the jack server? (https://www.digitalocean.com/community/tutorials/how-to-build-android-roms-on-ubuntu-16-04)
So which is it? Should I just follow Google's guide or do I really need to know the device identity? If the latter, How do I search for the device tree, vendor, and kernel? More importantly, what are these and how do they work in relation to the Android source?
Also, I believe I will need manufacturer drivers for my phone to operate the peripherals. How do I download this? This might be a stretch but can't I get those files from the Mate 7?
Any thoughts?