Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
N.K.V. said:
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
Click to expand...
Click to collapse
I love your initiative! Unfortunately I'm not a developer...
Send from my XT1068 using Tapatalk.
nice work mate.... developers are needed urgently....
Why do you think developers will find you and this thread? It works the other way. You need to find developers and ask for help. I suggest you start here and here
I keep my fingers crossed for the success of the project :highfive:
Yes, I am reading all possible guides given by the developers.
By that only i have reach this far.
But for device tree and kernel, device specific modifications are necessary, and I really need help of some one who has actually done this before.
If this is successful , we can have an alpha build of CM 12 , in 3-4 days.
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
k2wl said:
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
Click to expand...
Click to collapse
This is great news. A team effort can do anything.:good:
Thanks to NKV and Kewl. Great initiative. God Bless You.
Sent from my Nexus 7 using XDA Free mobile app
okay guys,
let's keep this thread clean for developers.
you can always hit like to appreciate
UPDATE: @k2wl is working on kernel and device tree, it will take him some days.
@k2wl and N.K.V.
Thx for your time and work :good:
I wait for the right Software on xt1068!
I have a little bit of knowledge and i can learn really fast, if you guys need help, you can count on me
which model will this be for? (please say xt1064)
Bobboman said:
which model will this be for? (please say xt1064)
Click to expand...
Click to collapse
Doesn't matter. It will be for all variants!
absolutely brilliant, i wish i knew a lick of programming so that i could help get this done faster (i'm tired of seeing a SU update in play store and not being able to use it because it sends my G into a bootloop)
Thanks man, lollipop official update have a bug while playing music via bluetooth when screen is lock, can you fix it on this rom?
Ha ha...Let's make the ROM first..
Bug fixing in Second task.
Now that lollipop soak has started in India....i think Work should go fast. :beer:
Waiting for it. Please keep updated though!
I'm interested in helping with this.
Sent from my A0001 using XDA Free mobile app
Hope to See this soon! Thanks guys!!
Nice intitiative...but i think making device tree and vendor for this device will not be tht easy....still hope for best
Does this sound feasible for me to get a kernel going for 901F
Compile a stock samsung kernel and test it works on device. (will test with my S2, if I can find samsung sources.)
If cannot find samsung sources compile someone else's sources and test.
Once I confirm I can compile a kernel properly then grab 900F sources, and compare to a custom kernel source to see whats changed.
Try to apply same changes to 901F
done?
Hello guys!
As we dual-sim g3 users known,our software version is not up to date everytime,and the system doesn't smooth like others,so in order to be able to experience the smooth stock rom I want to sharing something about how to port single sim variants like d855 to dual-sim (d857/858...).
Here we go,I will use d855_30f as a base rom port to d858hk.
1.Download the KDZ(both d855 and d858hk),extrat it(WindowsLGFirmwareExtract by @bullghost) to get the boot and system,deodex it ,I am using SVADeodexerForArtx32_v4.1(by @savdev)
2.Now we have to know about the differences on hardware(wifi,bluetooth,FM) between them,the dual sim variants are using broadcom chips instead like korean variants(F400,not include FM,because they have TMDB).So we should take these drives from d858hk30a.
something we need:
app/BluetoothMidiService/*
app/LGBluetooth4/*
app/FmService/*
bin/BCM4339_003.001.009.0105.0458_LGE_G3L_SPRINT_FM_ORC.hcd
bin/bdaddr_loader
bin/brcm-uim-sysfs
bin/brctl
bin/btnvtool
etc/acdbdata/*
etc/bluetooth/*
etc/firmware/fw*
etc/venus.*
etc/permissions/com.broadcom.bt.xml
etc/permissions/com.broadcom.fm.xml
etc/sensors/sensor_def_variable.conf
etc/wifi/*
etc/audio_policy.conf
etc/featureset.xml
etc/gps.conf
etc/mixer_paths.xml
etc/rssi.xml
framework/com.broadcom.bt.jar
framework/com.broadcom.fm.jar
framework/com.lge.fmradio.framework.jar
lib/hw/audio.a2dp.default.so
lib/hw/audio.primary.default.so
lib/hw/bplus.default.so
lib/modules/*
lib/libaptXHD-1.0.0-int-Android21-ARMv7A.so
lib/libbcmwl.so
lib/bluetooth_bdt.so
lib/bluetooth_jni2.so
lib/bluetoothsettings_jni.so
lib/libbt-aptX-ARM-4.2.2.so
lib/libbt-codec_*.so
lib/libhardware_legacy.so
lib/liberft*.so
lib/libwifilgeext_jni.so
vendor/firmware/BCM4339_003.001.009.0105.0458_LGE_G3L_SPRINT_FM_ORC.hcd
delete in 30f:
priv-app/macfeesecurty
etc/init.qcom.ftm_module.sh
etc/init.qcom.ftm_module_out.sh
lib/hw/bluetooth.default.so
build.prop modify:
add:
Code:
persist.radio.multisim.config=dsda
delete:
Code:
persist.sys.cust.lte_config=true
ro.lge.capp_cupss.rootdir=/cust
ro.build.sbp=1(not sure)
ro.lge.singleca.enable=1([COLOR="Red"]not sure[/COLOR])
ro.lge.custLanguageSet=true
persist.data.sbp.update=0([COLOR="red"]not sure[/COLOR])
sbp.oppartition.rw=0([COLOR="red"]not sure[/COLOR])
change:
Code:
ro.product.model=[COLOR="red"]LG-D855[/COLOR] to [COLOR="red"]yours[/COLOR]
wlan.chip.vendor=[COLOR="red"]qcom to[/COLOR] [COLOR="red"]brcm[/COLOR]
wlan.chip.version=[COLOR="red"]wcn[/COLOR] to [COLOR="red"]bcm4339[/COLOR]
3.the boot partion you can use stock bumped d858hk30a boot.
use AndroidImageKitchen(by @osm0sis) to extrat boot.img and add comments in ramdisk/init.lge.rc
Code:
#USE_SECUREBOOT
[COLOR="red"]#[/COLOR]verity_update_state
[COLOR="Red"]#[/COLOR]determine_run_wallpaper
repack it and bumped.
4.that's all,hope this will be useful to you,maybe there are some other files need or change,feel free to post your options,let's do this together to make it stable.
Hello again,
Again I post here because I am denied posting in the correct spot. I suppose this silly denial will end, eventually.
I have a question for @Silesh.Nair :
In the dev thread, you tell somebody that he can build CM14.1 from source himself, using that guide:
http://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
In a further post, you seem to indicate that the Moto G4 Plus build is obtained direct from the CM source repo.
I found that github repo for CM on the moto G4: https://github.com/CyanogenMod/android_device_motorola_athene
Unfortunately, the latest tag is marked CM 13 ... and there is nowhere to find the BSP files for CM 14.1.
Now, since it seems quite evident to you, but not at all for me, could you please kindly tell us where we can obtain the BSP files (device tree, vendor, kernel) for CM14.1 - Athene?
Thank you for your understanding my confusion.
You cannot post on a dev forum till you get to 10 posts.
You obviously cannot build cm14.1 using the device tree in cm github.
You have to sync the sources and add your device, vendor and kernel repos from here in your local manifest file.
Thank you
Silesh.Nair said:
You cannot post on a dev forum till you get to 10 posts.
You obviously cannot build cm14.1 using the device tree in cm github.
You have to sync the sources and add your device, vendor and kernel repos from here in your local manifest file.
Click to expand...
Click to collapse
Thank you for this snippet of information. I will look further into it.
In the world of embedded systems, when you have a generic operating system that can be used with many different hardware targets, a Board Support Package ("BSP") is the set of files that are required to build the generic OS on a specific target. For example here the BSP is all the files that are specific for the Moto G4/Plus (e.g. device tree, vendor, kernel), once you have a generic CM 14.1 distribution to start with. "BSP" refers to all the target-specific files that would not be the same on another target (i.e. a different phone).
I think this nomenclature is quite appropriate for the subject at hand.
I am trying to build the latest OOS 13 kernel .
The source I am working with is https://github.com/OnePlusOSS/android_kernel_oneplus_sm8250/tree/oneplus/sm8250_t_13.0.0_op8
In the past , i've built for Samsung and Lenovo devices , although I am unsure of a few things with our oneplus8t
Which defconfig file should I be using? as I do not see a kebab config within the root directory of android_kernel_oneplus_sm8250 or arch/arm64/configs/
Google has helped , but not too much material on building OOS kernels
What is the difference between a OOS kernel and AOSP kernel ? Would I be able to take a commit from AOSP and apply to my OOS ?
Appreciate any insight , and hope to be able to release a kernel soon!
SOLUTION
Backed up my boot.img with ex-kernel manager . Brought the boot.img to my build folder. Extracted defconfig with extract-ikconfig
Hey Dude I'm on oos11..i wanna compile a new kernel..which debconf to use.. the one in the vendors or what? Kona-perf.debconf?
Please help me which debconf to use for OnePlus 8
@hightech316 any luck on building the custom kernel yet?