Database Develop

[Q] Wich files to edit when porting from TITAN to THEA

Hello XDA,
As all of you may know there is a 4G LTE version of the Moto G 2nd Generation, better known under the model number XT1072 and XT1079. Unfortunately almost all ROMs are created for the titan. While the titan ROMs boot just fine because of the almost exact HW, when installing those ROMS we don't get 4G and the speakers and earpeace, especially while calling, get unusable.
So instead of sitting on my butt and asking LUK to develop a 4G patch, can anyone guide me ? I know how to setup the SDK and know the theory about compiling from source but have never done it. Do we have to recompile something or can I just replace certain files with some other files from the (one and only) CM12.1 port for the THEA ?
This must be doable I think.

soulaiman said:
Hello XDA,
As all of you may know there is a 4G LTE version of the Moto G 2nd Generation, better known under the model number XT1072 and XT1079. Unfortunately almost all ROMs are created for the titan. While the titan ROMs boot just fine because of the almost exact HW, when installing those ROMS we don't get 4G and the speakers and earpeace, especially while calling, get unusable.
So instead of sitting on my butt and asking LUK to develop a 4G patch, can anyone guide me ? I know how to setup the SDK and know the theory about compiling from source but have never done it. Do we have to recompile something or can I just replace certain files with some other files from the (one and only) CM12.1 port for the THEA ?
This must be doable I think.
Click to expand...
Click to collapse
It's easy but I'm not going to help in dirty ports. Build roms from source instead, this is my recommendation.
If you want to learn how to build roms from source I can help you but you'll need to have Linux machine to do that.

LuK1337 said:
It's easy but I'm not going to help in dirty ports. Build roms from source instead, this is my recommendation.
If you want to learn how to build roms from source I can help you but you'll need to have Linux machine to do that.
Click to expand...
Click to collapse
Thanks for the reply Luk, I also think that building from source is the same. I have followed many, many guides but somehow the part where I have to point to the thea specific HW blobs fails. The extract-files.sh points to ./../../$VENDOR/msm8226-common/setup-makefiles.sh [email protected] wich I understand is the motorola folder in the WORKING_DIRECTORY. Somehow I can't find the right repo on github to point it at.
Sorry for the noobish Q... There is a first time for everything.
EDIT: I wanted to say that I think that porting from source is better, not the same.

soulaiman said:
Thanks for the reply Luk, I also think that building from source is the same. I have followed many, many guides but somehow the part where I have to point to the thea specific HW blobs fails. The extract-files.sh points to ./../../$VENDOR/msm8226-common/setup-makefiles.sh [email protected] wich I understand is the motorola folder in the WORKING_DIRECTORY. Somehow I can't find the right repo on github to point it at.
Sorry for the noobish Q... There is a first time for everything.
EDIT: I wanted to say that I think that porting from source is better, not the same.
Click to expand...
Click to collapse
You could use blobs from TheMuppets instead: https://github.com/TheMuppets/proprietary_vendor_motorola

LuK1337 said:
You could use blobs from TheMuppets instead: https://github.com/TheMuppets/proprietary_vendor_motorola
Click to expand...
Click to collapse
Thanks !!
I was really confused and got the CM12 branch instead the first time. Lol now I feel like a noob haha (wich I am when it comes to developing).
Will post here if I have any Questions/errors (that google can't help me with).
:good:

soulaiman said:
Thanks !!
I was really confused and got the CM12 branch instead the first time. Lol now I feel like a noob haha (wich I am when it comes to developing).
Will post here if I have any Questions/errors (that google can't help me with).
:good:
Click to expand...
Click to collapse
Also don't use git clone manually, make your local_manifests xml instead.

LuK1337 said:
Also don't use git clone manually, make your local_manifests xml instead.
Click to expand...
Click to collapse
Oh okay, I will look into that in a minute.
Now I got an issue that really got my head hurting... When I do the lunch command, my Moto G isn't in the list of devices... What Am I doing wrong ?
I have got a directory called thea in WORKING_DIRECTORY/device/moto/thea
I have got also an old thea directory (cm12.1) in WORKING_DIRECTORY/thea and WORKING_DIRECTORY/thea2
All the blobs from TheMuppits repo are in de device/moto/thea dir
All the poperiatary blobs are also in the XT907 dir...
I've done the
Code:
cd /device/moto/thea
init android-5.1.1_rx
repo sync
and let it finish without errors.
Once I get over this I will be good to go.
Oh, and thanks for sharing the knowledge !

soulaiman said:
Oh okay, I will look into that in a minute.
Now I got an issue that really got my head hurting... When I do the lunch command, my Moto G isn't in the list of devices... What Am I doing wrong ?
I have got a directory called thea in WORKING_DIRECTORY/device/moto/thea
I have got also an old thea directory (cm12.1) in WORKING_DIRECTORY/thea and WORKING_DIRECTORY/thea2
All the blobs from TheMuppits repo are in de device/moto/thea dir
All the poperiatary blobs are also in the XT907 dir...
I've done the
Code:
cd /device/moto/thea
init android-5.1.1_rx
repo sync
and let it finish without errors.
Once I get over this I will be good to go.
Oh, and thanks for sharing the knowledge !
Click to expand...
Click to collapse
Your directories are bit off, it should be looking like this.
CM/device/motorola/msm8226-common
CM/device/motorola/thea
CM/device/qcom/sepolicy
CM/device/qcom/common
CM/kernel/mototola/msm8226
CM/vendor/motorola
Don't forget about rest of CM source :3

LuK1337 said:
Your directories are bit off, it should be looking like this.
CM/device/motorola/msm8226-common
CM/device/motorola/thea
CM/device/qcom/sepolicy
CM/device/qcom/common
CM/kernel/mototola/msm8226
CM/vendor/motorola
Don't forget about rest of CM source :3
Click to expand...
Click to collapse
Oh okay got ya. Do I have to do some kind of refresh command when I touch the folders ?

soulaiman said:
Oh okay got ya. Do I have to do some kind of refresh command when I touch the folders ?
Click to expand...
Click to collapse
If you're building CM then all you have to do is to get vendor, do envsetup.sh and just brunch thea.

LuK1337 said:
If you're building CM then all you have to do is to get vendor, do envsetup.sh and just brunch thea.
Click to expand...
Click to collapse
I'm trying to build an AOSP build like yours to learn. I'm following this guide:
http://forum.xda-developers.com/chef-central/android/tutorial-compile-lollipop-ubuntu-t2929410
I guess it is similar in steps as what you described ?
Even with all the files in the correct directories when I exec the lunch command it doesn't list the moto G. See screenshot.

soulaiman said:
I'm trying to build an AOSP build like yours to learn. I'm following this guide:
http://forum.xda-developers.com/chef-central/android/tutorial-compile-lollipop-ubuntu-t2929410
I guess it is similar in steps as what you described ?
Even with all the files in the correct directories when I exec the lunch command it doesn't list the moto G. See screenshot.
Click to expand...
Click to collapse
You won't get clean AOSP to build, also u messed up directories as you put vendor in device.
If you have hangouts you can add me ( https://plus.google.com/108108436166506337243 ) so I could help you live.

LuK1337 said:
You won't get clean AOSP to build, also u messed up directories as you put vendor in device.
If you have hangouts you can add me ( https://plus.google.com/108108436166506337243 ) so I could help you live.
Click to expand...
Click to collapse
Thanks for all the help man, really appreciate it !
Yeah stupid fault of my part. Will try it.
About Hangouts: My hangouts app allways FC's on me so that will be for another day. I'll add you asap ! Thanks!
Also it is 1:45AM here so

soulaiman said:
Thanks for all the help man, really appreciate it !
Yeah stupid fault of my part. Will try it.
About Hangouts: My hangouts app allways FC's on me so that will be for another day. I'll add you asap ! Thanks!
Also it is 1:45AM here so [emoji14]
Click to expand...
Click to collapse
K, I'm in the same time zone fyi.

[DEV][G925F] CyanogenMod 12.1 Development

Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
​

Reserved

i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)

vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.

add me as participant to the repos ^^
https://github.com/OldDroid

OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them

Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.

mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?

nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support

First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying

mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then

Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer

Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?

Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself

mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk

lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset

Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.

mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.

-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes

mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.

[TWRP][INFINIX][3.0.2-0] TWRP for Infinix Hot-2

Keeping it short and simple, this is a source compiled version of TWRP 3.0.2-0 for the HOT-2. I have based it on @Nonta72's device tree with Infinix hardware configs. If this works for you, please report as such so I can get it official. Officially supported device get automatic builds which are made available at dl.twrp.me/<device_codename> at each major release. Thank you.
Download : My Website
XDA:DevDB Information
TWRP for HOT 2, Tool/Utility for the Infinix HOT 2
Contributors
MSF Jarvis, Nonta72
Version Information
Status: Testing
Created 2016-04-13
Last Updated 2016-04-13

MSF Jarvis said:
Keeping it short and simple, this is a source compiled version of TWRP 3.0.2-0 for the HOT-2. I have based it on @Nonta72's device tree with Infinix hardware configs. If this works for you, please report as such so I can get it official.
Click to expand...
Click to collapse
Hey,
Thank you for your courageous work.
Unfortunately the first build didn't seem to work on my device.
If fails to boot to recovery, then reboots straight to OS.
Please note that:
- You need cm-13 branch to compile the newer TWRP (like TWRP 3.0.x)
- If you're compiling a recovery without kernel source code, you need to use the prebuilt kernel from recovery.img, not sure if the kernel from boot.img is the same in recovery.img In my sources, I uploaded the one from boot.img
- Something may be wrong with the source. I will properly check this week-end. I except the device name to be wrong.

Nonta72 said:
Hey,
Thank you for your courageous work.
Unfortunately the first build didn't seem to work on my device.
If fails to boot to recovery, then reboots straight to OS.
Please note that:
- You need cm-13 branch to compile the newer TWRP (like TWRP 3.0.x)
- If you're compiling a recovery without kernel source code, you need to use the prebuilt kernel from recovery.img, not sure if the kernel from boot.img is the same in recovery.img In my sources, I uploaded the one from boot.img
- Something may be wrong with the source. I will properly check this week-end. I except the device name to be wrong.
Click to expand...
Click to collapse
- I upstream-patched the tree to cm-13.0 (Atleast for TWRP)
- The kernel's are the same, only the init.rc changes. I'll have to see to that.
- I found d5110_infinix pointless, since you have asserts for d5110 as well, ROMs will pass the device name assert and flash.

MSF Jarvis said:
- I upstream-patched the tree to cm-13.0 (Atleast for TWRP)
- The kernel's are the same, only the init.rc changes. I'll have to see to that.
- I found d5110_infinix pointless, since you have asserts for d5110 as well, ROMs will pass the device name assert and flash.
Click to expand...
Click to collapse
If boot.img rcs are different from recovery.img ones, then it won't probably boot. But I think the fstab files are the same.
I will add a new branch with recovery rcs on week-end.

Nonta72 said:
If boot.img rcs are different from recovery.img ones, then it won't probably boot. But I think the fstab files are the same.
I will add a new branch with recovery rcs on week-end.
Click to expand...
Click to collapse
Recovery ones are usually barebones, because boot.img rc's are quite complex, because they have to fix perms on the entire sysfs, set default IO scheduler, CPU Governor and create mount points. Recovery rc's are about 20 lines in the oldie device I maintain along with the LAVA Pixelv1.
Let's work together to get this booting and I'll also get your name on the device page as maintainer
And I usually keep my word.

MSF Jarvis said:
Recovery ones are usually barebones, because boot.img rc's are quite complex, because they have to fix perms on the entire sysfs, set default IO scheduler, CPU Governor and create mount points. Recovery rc's are about 20 lines in the oldie device I maintain along with the LAVA Pixelv1.
Let's work together to get this booting and I'll also get your name on the device page as maintainer
And I usually keep my word.
Click to expand...
Click to collapse
Sure
Let's make it work! :highfive:

Nonta72 said:
Sure
Let's make it work! :highfive:
Click to expand...
Click to collapse
New build : http://msfjarvis.me/seedmtk/HOT-2/TWRP/
Not sure this one will boot either, but let's try

MSF Jarvis said:
New build : http://msfjarvis.me/seedmtk/HOT-2/TWRP/
Not sure this one will boot either, but let's try
Click to expand...
Click to collapse
The problem persists.
We have a WhatsApp group, you may want to join us by sending over your number (in PM if you wish). That will make exchange faster.

Nonta72 said:
Sure
Let's make it work! :highfive:
Click to expand...
Click to collapse
MSF Jarvis said:
New build : http://msfjarvis.me/seedmtk/HOT-2/TWRP/
Not sure this one will boot either, but let's try
Click to expand...
Click to collapse
In 15 minutes, there will be twrp-3.0.2-2 available there. If you're interested to see what I did to it, check the commits
This one has logcat enabled as well, so you may wanna help me that way. I don't do WhatsApp, so you may want to hop on to #team-redux on http://webchat.freenode.net rather.

Nonta72 said:
Sure
Let's make it work! :highfive:
Click to expand...
Click to collapse
Made a typo in BoardConfig, now it's okay. Building now :fingers-crossed:

MSF Jarvis said:
Made a typo in BoardConfig, now it's okay. Building now :fingers-crossed:
Click to expand...
Click to collapse
Nonta72 said:
The problem persists.
We have a WhatsApp group, you may want to join us by sending over your number (in PM if you wish). That will make exchange faster.
Click to expand...
Click to collapse
Another test build is up : 3.0.2-2

MSF Jarvis said:
Another test build is up : 3.0.2-2
Click to expand...
Click to collapse
You should probably compare x510 files with sprout8/4 files; because it still doesn't boot ...

Nonta72 said:
You should probably compare x510 files with sprout8/4 files; because it still doesn't boot ...
Click to expand...
Click to collapse
Maybe I should, but where's the similarity?

MSF Jarvis said:
Maybe I should, but where's the similarity?
Click to expand...
Click to collapse
I never compared them ...
Since you already compiled TWRP for sprout, I thought it would be easier to compare with x510. :laugh:
Anyways, I did many unsuccessful attempts to port sprout4/8 roms to x510 without success. Both devices are slightly differents.

Nonta72 said:
I never compared them ...
Since you already compiled TWRP for sprout, I thought it would be easier to compare with x510. :laugh:
Anyways, I did many unsuccessful attempts to port sprout4/8 roms to x510 without success. Both devices are slightly differents.
Click to expand...
Click to collapse
sprout(4|8) are MT6582 devices, just like the LAVA Pixelv1. I don't know how the x510 ended up with a MT6580 processor

Ah, sadly didn't work for me, it doesn't boot to recovery mode, i already tried "reboot recovery" and "adb reboot recovery" method but didn"t work.. But if i flash twrp 2.8.7.0 it works...
Infinix Hot 2 (16+2 GB version)

RendyAK said:
Ah, sadly didn't work for me, it doesn't boot to recovery mode, i already tried "reboot recovery" and "adb reboot recovery" method but didn"t work.. But if i flash twrp 2.8.7.0 it works...
Infinix Hot 2 (16+2 GB version)
Click to expand...
Click to collapse
I know it isn't booting. Just on a note, your 2.8.7.0 boots? Coz it's just an emulator build, designed to run on the Android Emulator, not an actual device ??

MSF Jarvis said:
sprout(4|8) are MT6582 devices, just like the LAVA Pixelv1. I don't know how the x510 ended up with a MT6580 processor
Click to expand...
Click to collapse
Because MT6580 is a recent version of the MT6582. Forget the "2" that became "0" at the end. The MT6580 is even faster than the MT6582 and can match some MT6592 (with 1GB RAM). I saw a 33,000+ antutu on a MT6580 (with 2GB RAM) and overclocked (yes! overclocked, idk how but they said so).
MSF Jarvis said:
I know it isn't booting. Just on a note, your 2.8.7.0 boots? Coz it's just an emulator build, designed to run on the Android Emulator, not an actual device ??
Click to expand...
Click to collapse
Sir, you're talking about the messed up ramdisk. In fact, there are many builds, the one you have seen have many bugs probably because of the messed up rcs.
The only recovery that works good for me is the one made by Ovatek. I made few commits to my github including the fstab file changes you suggested...

Went here http://forum.xda-developers.com/cro...al-android-development/recovery-twrp-t3353364 and have noticed your work on the Lava Pixel. I compared ramdisk of TWRP 3.0.2 for that device and found out that it's just the same as sprout4 and 8!
In fact, the seedmtk is just a "name"; the files are very identical to 1st gen Android One. For example: Both sprout4/8 and Pixel V1 use fstab.sprout in ramdisks.
The Infinix Hot 2 is a whole different story! It doesn't seem to even have a codename LOL In its ramdisk, you find fstab.mt6580 not fstab.sprout (or something alike).
One more thing, if you unpack boot.img of Hot 2 using Carliv Image Kitchen, you get 9 files + ramdisk folder. But if you unpack Pixel V1's boot.img with the same tool, you get 6 files + ramdisk folder.
You can find ALL 2nd Gen Android One devices here on Wikipedia

Nonta72 said:
Went here http://forum.xda-developers.com/cro...al-android-development/recovery-twrp-t3353364 and have noticed your work on the Lava Pixel. I compared ramdisk of TWRP 3.0.2 for that device and found out that it's just the same as sprout4 and 8!
In fact, the seedmtk is just a "name"; the files are very identical to 1st gen Android One. For example: Both sprout4/8 and Pixel V1 use fstab.sprout in ramdisks.
The Infinix Hot 2 is a whole different story! It doesn't seem to even have a codename LOL In its ramdisk, you find fstab.mt6580 not fstab.sprout (or something alike).
One more thing, if you unpack boot.img of Hot 2 using Carliv Image Kitchen, you get 9 files + ramdisk folder. But if you unpack Pixel V1's boot.img with the same tool, you get 6 files + ramdisk folder.
You can find ALL 2nd Gen Android One devices here on Wikipedia
Click to expand...
Click to collapse
Actually speaking, the OEM for the MT6582 device went with naming the device 'sprout', which I vehemently oppose, to avoid confusion. The stock boot.img's ramdisk also contains files according to the 'sprout' nomenclature. I took the sprout4 device tree, updated all *.rc's from the stock marshamallow boot.img and added in a bunch of TWRP flags.
One important thing you most probably already know, Infinix Hot 2 uses a standard MTK boot.img header, while the LAVA Pixelv1 uses an AOSP format, so it can be unpacked using standard tools, while yours requires Carliv's kitchen.

Porting oxygen os

Hey I have used oxygen os on my oneplus 3t and I wanted to port is to our titan. I am new to porting and stuff so I wanted to know from where could I get any help?
Regards Mehul

port it please i love oxygen os
but how long it will take to port

saurabh.k said:
port it please i love oxygen os
but how long it will take to port
Click to expand...
Click to collapse
If I can have the source code from somewhere I'll start immediately but I ain't able to find any help.

https://github.com/OnePlusOSS/android
this is source code

saurabh.k said:
https://github.com/OnePlusOSS/android
this is source code
Click to expand...
Click to collapse
I currently have some urgent work to do on the request of my dad as he has asked me to install LOS 14.1 on his device and recover all of his data as well. So once I finish with that I'll start porting oxygen OS as soon as possible.
Thanks in advance
Sorry to make you wait

okk its fine.but. port it for surely

I will start also trying to port oxygenos for titan, i'm downloading now code source

walidham said:
I will start also trying to port oxygenos for titan, i'm downloading now code source
Click to expand...
Click to collapse
Hey can we cooperate and do it together?
I'd like to do that as it's one of my initial projects so any help would be very much appreciated

i will be thankful if u guys port oxygen os for titan
good luck

Mehul03 said:
Hey can we cooperate and do it together?
I'd like to do that as it's one of my initial projects so any help would be very much appreciated
Click to expand...
Click to collapse
ok no problem, ur welcome, iant also cooeperate with u,
i downloaded source code version 6.0 and i'm start build it

walidham said:
ok no problem, ur welcome, iant also cooeperate with u,
i downloaded source code version 6.0 and i'm start build it
Click to expand...
Click to collapse
You downloaded the source code for which device, if you downloaded it for titan then where did you get it from?

Mehul03 said:
You downloaded the source code for which device, if you downloaded it for titan then where did you get it from?
Click to expand...
Click to collapse
from her : https://github.com/OnePlusOSS
and i used cm-13.0 device tree for titan, also i'm try to integrate kernel also.
I change device/qcom/common with cm , remove kernel-tests from vendor/qcom/opensource, but still have some error like this :
make: *** No rule to make target 'out/target/product/titan/kernel', needed by 'out/target/product/titan/dt.img'. Stop.

btw how long will it take to build the port
i am asking this bcoz i love oxygen os and i am thankfull for u guys that u r porting it

walidham said:
from her : https://github.com/OnePlusOSS
and i used cm-13.0 device tree for titan, also i'm try to integrate kernel also.
I change device/qcom/common with cm , remove kernel-tests from vendor/qcom/opensource, but still have some error like this :
make: *** No rule to make target 'out/target/product/titan/kernel', needed by 'out/target/product/titan/dt.img'. Stop.
Click to expand...
Click to collapse
Good luck for it nothing is impossible! but I have never seen oxygen os in any moto devices its very hard to make source compatible for titan ))))

Kranoner said:
Good luck for it nothing is impossible! but I have never seen oxygen os in any moto devices its very hard to make source compatible for titan ))))
Click to expand...
Click to collapse
We're trying
Let's see what happens

Kranoner said:
Good luck for it nothing is impossible! but I have never seen oxygen os in any moto devices its very hard to make source compatible for titan ))))
Click to expand...
Click to collapse
Thanks,
After 2h of compilation i'm stuck in sepolicy error
device/motorola/msm8226-common/sepolicy/rild.te:5:ERROR 'unknown type sysfs_battery_supply' at token ';' on line 13744:
I will change device/qcom/sepolicy with cm version and add vendor/cm and see if resolve this error

walidham said:
Thanks,
After 2h of compilation i'm stuck in sepolicy error
device/motorola/msm8226-common/sepolicy/rild.te:5:ERROR 'unknown type sysfs_battery_supply' at token ';' on line 13744:
I will change device/qcom/sepolicy with cm version and add vendor/cm and see if resolve this error
Click to expand...
Click to collapse
Wow... oxygen os will give oxygen to our device titan.
Good luck.
Sent from my Moto G 2014 using Tapatalk

neeraj121y said:
Wow... oxygen os will give oxygen to our device titan.
Good luck.
Click to expand...
Click to collapse
But I guess that's gonna take loads of time as presently the kernel is showing only errors

walidham said:
Thanks,
After 2h of compilation i'm stuck in sepolicy error
device/motorola/msm8226-common/sepolicy/rild.te:5:ERROR 'unknown type sysfs_battery_supply' at token ';' on line 13744:
I will change device/qcom/sepolicy with cm version and add vendor/cm and see if resolve this error
Click to expand...
Click to collapse
Have you tried MoKee instead of LOS?
https://github.com/MoKee/android_device_motorola_titan
https://github.com/MoKee/android_vendor_motorola_titan
They use different kernel.

PsyClip-R said:
Have you tried MoKee instead of LOS?
https://github.com/MoKee/android_device_motorola_titan
https://github.com/MoKee/android_vendor_motorola_titan
They use different kernel.
Click to expand...
Click to collapse
Thanks for help
I will try,
I changed the original externel/sepolicy with LOS , and after 3h of compilation i got this error :
Code:
out/target/product/titan/obj/ETC/sepolicy_intermediates/policy.conf:1:ERROR 'syntax error' at token '' on line 1:
When i chek the file i found that is empty.

General Kernel source finally released

It finally happened the source code is released
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/spes-r-oss
Leaving this also as a place for first discussions. So, go for it.

NeoPreacher said:
It finally happened the source code is released
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/spes-r-oss
Leaving this also as a place for first discussions. So, go for it.
Click to expand...
Click to collapse
Finally!!!

Let's gooooooooooo!!!!!!!!!

It only took them a year and three months to release it.
Oh god...

NeoSDAP said:
It only took them a year and three months to release it.
Oh god...
Click to expand...
Click to collapse
lmao

Snapdragon_Mid_2020.SPF.1.0.1R_r00024.0
lol it makes even more sad.

Does the Kernel being for Android 11 mean its useless for us? Can Android 12/13 roms not be made with it? I really just wanted working doubletap2wake, would the Android 11 Kernel make that happen? Thank you!

Zylam Marex said:
Does the Kernel being for Android 11 mean its useless for us? Can Android 12/13 roms not be made with it? I really just wanted working doubletap2wake, would the Android 11 Kernel make that happen? Thank you!
Click to expand...
Click to collapse
No; sure; works already flawless in PA, but sure why not. There are others problems eg. missing drivers in source and missing devs in group. Fyi: many people using a13 custom rom with a11 stock kernel actually on rn11

nice. they can now close 1k issues regarding spes kernel. hahaha

pulsar said:
nice. they can now close 1k issues regarding spes kernel. hahaha
Click to expand...
Click to collapse
There are some people fixing the issues with source already!

NeoPreacher said:
No; sure; works already flawless in PA, but sure why not. There are others problems eg. missing drivers in source and missing devs in group. Fyi: many people using a13 custom rom with a11 stock kernel actually on rn11
Click to expand...
Click to collapse
Oh wow really, tape2wake works great in PA? I have tried almost all roms but PA. Thank you for letting me know, a shame the Kernel is missing drivers and such. I wonder why Xiaomi is trying to make sure the Note 11 is never developed for, it's such a good phone with a custom rom.

BerserkSlayer said:
There are some people fixing the issues with source already!
Click to expand...
Click to collapse
Haha I think Pulsar was referring to Xiaomi's github page where there would be like 10 posts a day asking for Spes kernel

tap2wake also works on PixelExperience, FWIW.
EDIT: board_id.h is present in the same directory, not in include/. \
I've tried compiling the kernel from Xiaomi's sources and stumbled across an error about a missing header file:
Code:
drivers/misc/st21nfc.c:43:22: fatal error: board_id.h: No such file or directory
#include <board_id.h>
^
compilation terminated.
make[2]: *** [scripts/Makefile.build:338: drivers/misc/st21nfc.o] Error 1
make[1]: *** [scripts/Makefile.build:642: drivers/misc] Error 2
This file board_id.h does not exist in the include/ folder. Perhaps Xiaomi uploaded incomplete sources?

aureljared said:
tap2wake also works on PixelExperience, FWIW.
EDIT: board_id.h is present in the same directory, not in include/. \
I've tried compiling the kernel from Xiaomi's sources and stumbled across an error about a missing header file:
Code:
drivers/misc/st21nfc.c:43:22: fatal error: board_id.h: No such file or directory
#include <board_id.h>
^
compilation terminated.
make[2]: *** [scripts/Makefile.build:338: drivers/misc/st21nfc.o] Error 1
make[1]: *** [scripts/Makefile.build:642: drivers/misc] Error 2
This file board_id.h does not exist in the include/ folder. Perhaps Xiaomi uploaded incomplete sources?
Click to expand...
Click to collapse
yes

Much easier to compile this kernel using Clang rather than GCC. Still getting used to it, it's been a good while since my last kernel compile, haha.
Does anyone know how to build a new boot image by hand? I have a working boot.img for PixelExperience and I'd like to replace the kernel with one that I built for testing, but I'm not sure if I should still use mkbootimg like with older Android devices as this is the first time I'll be dealing with a device that uses dtb/dtbo files. Any insights would be welcome.
aureljared said:
EDIT: board_id.h is present in the same directory, not in include/.
Click to expand...
Click to collapse

Not an expert here. What exactly are the benefits of this? What does it mean for custom ROM development?

SAM209 said:
Not an expert here. What exactly are the benefits of this? What does it mean for custom ROM development?
Click to expand...
Click to collapse
For one, it is theoretically easier to keep the device up to date without having to wait for Xiaomi's updates. Some changes that come with Android's monthly security patches are made to the kernel, for example, and having the kernel source code means we can apply those patches faster than if we were to wait for updated kernel builds from Xiaomi.
Some ROMs like LineageOS also require kernels to be built from source (i.e., not prebuilt) for a device to be granted official status.

Hello,
Can someone guide me on how to install that kernel on redmi note 11 (Pixel Experience custom os)
Already installed twrp 3.7.0 but gives me some errors all the time like Invalid zip file format!.
I download it as zip from github and put it in twrp folder and install it from there.
Thanks in advance

jasmin811 said:
Hello,
Can someone guide me on how to install that kernel on redmi note 11 (Pixel Experience custom os)
Already installed twrp 3.7.0 but gives me some errors all the time like Invalid zip file format!.
I download it as zip from github and put it in twrp folder and install it from there.
Thanks in advance
Click to expand...
Click to collapse
There's nothing to flash here. Only the link to the kernel source. There's still some work to do for a flashable kernel (compiling eg). Also there are drivers missing in the source it seems. What you tried was flashing the uncompiled kernel source package i guess and that.. doesn't work

Oh ok,I though it was finished already.