So since SafeStrap can boot an AOSP based ROM that can use the same kernel, I decided to make a CyanogenMod 10.1 ROM for those who can only use safestrap.
I've gotten my build environment set up, and repo sync'd cm-10.1.
My question is:
Where can I get proprietary binary "blobs" for this device? I see I can get some device files from
https://github.com/ggow/android_device_amazon_hdx-common and
https://github.com/ggow/android_device_amazon_thor(or apollo) (cm10.1 branch for both)
Where do I put these once cloned? Can I just "lunch full_thor-userdebug" and "make" after that?
Thanks in advance.
Related
Hi all,
I am looking to find a way to build from repository the latest camera/gallery combo and email/calendar from 4.4 in a CM10 (4.1.2) build process. I get the error that I am building a version of Android too low to use these resources. I have the default set in the repo manifest, and a build version in my cm.mk file. I have tried to a simply chang the fingerprint to 4.4.2 and then adjusting the build number. I also changed the repo version to sync with but it still wants to build 4.1.2
I keep getting into trouble with different local settings in jni files etc. Has anyone managed to do this successfully or is it always a case of cross your fingers and copy the apk in after the build. Ideally I would want to avoid this as I want to make it rather than mka and get a nice ODEXed set out.
Any help very much appreciated
The reason why nobody else is doing this is because it's really improbable you get this working.
For this to work you have to port most of the stuff that makes 4.4 version 4.4 back to your CM10.
It would be way easier to compile 4.4 and change the undesired apps back to CM10 apps. Because 4.4 does have the API and features that CM10 does, just not the other way around.
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
Ok so I have built cm11 for my device (galaxys s 4g), and ported cm11 from another device to (aries -> galaxy s 4g). CM11 has too much going on IMO and I just want pure aosp on my device, the problem is that there are no (recent) aosp roms for my device, or any similar devices.
So how do I port my device to a different flavor of android when there are no roms of that flavor?
What have I tried?
So far I have setup the aosp 4.4 repo to a different folder than my cm11 repo (the build environment files should be the same right?)
I tried using the manifest from the cm11 rom and buidling with aosp,that didnt work it didnt even finish compiling =(.
I browsed the aosp source for other devices by the same manufacturer, but everything looked completely different from what I am used to.
The most helpful guide in this direction sofar has been cyanogenmods guide but it has left me with more questions than answers.
What [I think] I need to know
Custom recovery - aosp doent seem to include a recovery, the cm guide says to start with the recovery. So i need to know if I need to add a custom recovery to aosp, or if i can install aosp roms from twrp without breaking it.
Binaries - It is safe to use the binaries used in CM11 for aosp/any other flavor, or are the binaries flavor specific? (im thinking they are safe to use, but not entirely sure).
Device files - what files should be safe to use for any flavor?
Kernel - Cm builds the kernel when you compile the rom (or so it says), does aosp build the kernel when you build the rom, or do I have to build the kernel separately? Is it safe to say use a CM11 kernel with an aosp rom?
Im building Omnirom, from source (im a newbie) and i have succesfully build android 4.4.4 from the official repo.
Now, i want to update that rom, using https://github.com/duvall which has a branch with android 5.1 for my galaxy s2 (i9100)
I haver read some posts, that said that a i have to remove official repo and pull to that custom repo using local manifest. but i dont know how to do that... i dont know what i need to put in that local manifest could anyone help me ?
thanks
Hi guys, I'm doing a Cyanogenmod 12.1 porting for my device that is unsupported. I can build everything and I get a flashable zip but I'm using a prebuilt stock kernel image extracted from the stock lollipop rom. After flashing, the phone does not boot and It's impossible even to access to logcat, so I think it's a kernel related issue. My question is:
- I have the stock kernel source (v.3.10) given by the vendor
- I have the cyanogenmod kernel source (v.2.69)
Do I have to build the stock kernel or I can build the cyanogenmod one by merging the drivers modules and others stuff?
And if I flash a wrong kernel image can my device become unusable?
I read that is not fair importing built kernel modules from other kernel version, but if I merge the kernel trees, is it the same?
Sorry in advance if my question is a noob question
Well I don't know much about porting roms or kernels though. But with what I've heard flashing the wrong kernels can permanently render your phone useless..
Sent from my Tecno F7 a ...?
I've been trying to figure out how to build Cyanogenmod from source for a few devices. I've looked at many tutorials and such, but I haven't been able to find one that explains how to build Cyanogen for a device that had an old version of Cyanogen but hasn't been updated since. For example, the official builds for a certain device only go up to 12.1, but I want to build it for 13.0. Does anyone have any advice?
spenceboy98 said:
I've been trying to figure out how to build Cyanogenmod from source for a few devices. I've looked at many tutorials and such, but I haven't been able to find one that explains how to build Cyanogen for a device that had an old version of Cyanogen but hasn't been updated since. For example, the official builds for a certain device only go up to 12.1, but I want to build it for 13.0. Does anyone have any advice?
Click to expand...
Click to collapse
I would recommend starting by using the device tree for your device that supports 12.1 and try using that tree to compile 13. To do this download the 13 code and put the 12.1 device tree in the proper folders (device, vendor, kernel) and try compiling a build and start seeing what errors you get. Let me know if you still have questions I'll do my best to help you out!