Hi everybody, I am new in building from source, and this seems to be a bit complicated at first... I owe a zuk z1, an officially cm13 supported phone. I am trying to port omni rom to my phone but I haven't been able to find a single guide on xda about how to omnify my cm repo.
This is really frustrating, because I want to do it, I have time, but I don't have the minimal knowledge about what files do I have to edit...
I've downloaded the omni-lp repo, I introduced a local_manifest with my device, kernel and vendor setup, I re-synced, but at this point I don't know WTF I need to "omnify" (as a lot of users say but don't explain...). I have read different things in different threads but there isn't one which says you have to edit THIS and THIS, and add this, here, so I am completely lost.
If you could help me as I have helped people in this forum a lot of times I would be really helpful, and I would create a guide for the people stuck in my situation.
I hope anybody can help me,
Thanks!
Anybody knows nothing about buiding omni ROM in Omni Q&A subforum?
Probably a bit technical for most xda users
I don't have your device so can't advise on specifics, but in the past when I've done this, I've taken a repo for a device that is in both cm and omni, looked at the differences there, then applied those changes to the one I'm trying to port.
Hope that makes sense, good luck!
Sent from my Nexus 6P using Tapatalk
schiznik said:
Probably a bit technical for most xda users
I don't have your device so can't advise on specifics, but in the past when I've done this, I've taken a repo for a device that is in both cm and omni, looked at the differences there, then applied those changes to the one I'm trying to port.
Hope that makes sense, good luck!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Any help is appreciated.
Thanks, lets ser if anyone can tell me anything else!
luiseteyo said:
Any help is appreciated.
Thanks, lets ser if anyone can tell me anything else!
Click to expand...
Click to collapse
Well, here's the "official" Omni documentation.
http://docs.omnirom.org/Porting_Omni_To_Your_Device - I've used it with some success, and would recommend finding a TWRP config for your device so you don't have to figure out what it is yourself. If you have a caf based device, you'll need to look at the find7 config (just an example) to see which BoardConfig flags you need - they're slightly different than CM (eg you need to specify the Display, Audio, and Media variants). Also note that Omni doesn't include qcom specific repos by default - you need to add them manually or to you omni.dependencies files. Also, for caf devices, there isn't a device/qcom/common repository (well, there is but it doesn't work ) so you'll need to add things such as the dtbTool manually to your repo...
Frankly, the Omni team is much more knowledgable than me so you could check out their IRC channel for any issues.
Hope this helps and Have Fun!
Really thanks. I tried to use that guide in the past but didnt succeed. Will try luck again using your comments!
Thanks again
Enviado desde mi Z1 mediante Tapatalk
luiseteyo said:
Really thanks. I tried to use that guide in the past but didnt succeed. Will try luck again using your comments!
Thanks again
Enviado desde mi Z1 mediante Tapatalk
Click to expand...
Click to collapse
Also, I should note that the find7 includes a lot of things in oppo/msm8974-common so look there as well if you have a caf device (I think the ZUK Z1 is but not having the device couldn't say for sure).
@luiseteyo even i am trying to do the same for oneplus2. no help. IRC omniROM channel isn't much help either. maybe we can help each other by sharing what we discover along the way. u can msg me on telegram anytime, my telegram user name is "kapilj"
xc-racer99 said:
Also, I should note that the find7 includes a lot of things in oppo/msm8974-common so look there as well if you have a caf device (I think the ZUK Z1 is but not having the device couldn't say for sure).
Click to expand...
Click to collapse
Great idea, I've found a very clean find7 omni github I am using to check what is modded. I'm not at home but as soon as I get there I will download telegram and send u the link.
But I repeat, I am a newbie and I dont know how to do this. I wouldnt like to slow your progress down.
Enviado desde mi Z1 mediante Tapatalk
There u go:
https://github.com/omnirom/android_...mmit/06bea287fd4952a79e551171e373889a2bff4b55
Enviado desde mi Z1 mediante Tapatalk
Warning: Very few people have worked on 64-bit CAF snapdragons (any non-Nexus Qualcomm device that isn't AOSP or Sony) - so you're treading on new ground where few of us have worked. There are likely core components within the Omni trees that are missing.
In my case - I have zero interest in Snapdragon 810 devices. I only own two because they were sent to me by a manufacturer - and those are both Sony devices and Sony AOSP is rather unusual in this regard (as a lot of work has been done to allow them to use AOSP HALs/frameworks instead of CAF.)
For 64-bit devices, maxwen's R5 work might be a better reference.
Entropy512 said:
Warning: Very few people have worked on 64-bit CAF snapdragons (any non-Nexus Qualcomm device that isn't AOSP or Sony) - so you're treading on new ground where few of us have worked. There are likely core components within the Omni trees that are missing.
In my case - I have zero interest in Snapdragon 810 devices. I only own two because they were sent to me by a manufacturer - and those are both Sony devices and Sony AOSP is rather unusual in this regard (as a lot of work has been done to allow them to use AOSP HALs/frameworks instead of CAF.)
For 64-bit devices, maxwen's R5 work might be a better reference.
Click to expand...
Click to collapse
Thank you for your response. I had look at few unofficial ports and figured out that it's beyond me. So for time being i have dropped this project and concentrating on learning through CM based ROMs. Will come back to omni when i have gather enough knowledge. Hopefully someday oneplus2 might get omnirom, that will help me in learning a lot of new things.
I am following few repo just to learn anyway.
Btw lot of people asking for omnirom for yureka, yuphoria and many other 64bit devices. Omnirom isn't available for many devices. I Hope that will change as well.
Related
Hey guys,
I've set up an organization on github und uploaded my config there.
Could you please provide me your github usernames via PN so I can add you to the team?
Thanks,
Daniel
Doublepranks. But I just wanna join for learning if you would let me in....
Sent from my XT1033 using Tapatalk
swordrune10, don't have a moto g yet but most likely getting one for xmas
Sent from my Galaxy Nexus using Tapatalk
Josalaito, i'm working in cm 10.2 now, and i think we need a hard work because msm8x26 is not fully supported by cyanogen and we need to use 8960(The same happened in my old y300 cm doesnt support 8x25 and we use msm7x27a)
Hi, my username is debaj, I hope I can help anything as a geneal Android developer since I have no experience in ROM development except building Cyanogenmod for my old Nexus S
My Username on github is: denizkoekden
Regards,
Deniz
Still don't have a Moto G but wanna buy one for christmas...
My username on GitHub is: Lopicl
github username: immortalyash
i think we go go ahead with ms8226 as config as motorola giving sources it will things easier for us to add stuff for msm8226 and make it full compatible
immortal_yash said:
github username: immortalyash
i think we go go ahead with ms8226 as config as motorola giving sources it will things easier for us to add stuff for msm8226 and make it full compatible
Click to expand...
Click to collapse
I think it's best to begin with msm8226 from the outset rather than trying to kang a different board
I'm seapoint on Git by the way. https://github.com/seapoint
My Moto G arrives Tomorrow
too bad I won't have time to do anything
I am Scrizz on github
Count me in. as for creating a kernel, device, hardware and properity tree. Github : calibrex
Problem is now, i've seen that the MotoG stands under MSM8226 and MSM8926 @ Wikipedia. Which one is the Phone now really using ?
I see josalaito did a bit of work on Github *thumbsup*
7alvi reporting for call of booty..jk
Count me in. Will be getting mine by January (most likely) and for my work I have built Carbon, Mokee, Slim, AOKP, baked, anir, etc etc for HTC Pico..!
kaliberx said:
Count me in. as for creating a kernel, device, hardware and properity tree. Github : calibrex
Problem is now, i've seen that the MotoG stands under MSM8226 and MSM8626 @ Wikipedia. Which one is the Phone now really using ?
I see josalaito did a bit of work on Github *thumbsup*
Click to expand...
Click to collapse
its MSM8226 and we have already started with device tree...it would be better art with kernel as i m not a kernel man
immortal_yash said:
its MSM8226 and we have already started with device tree...it would be better art with kernel as i m not a kernel man
Click to expand...
Click to collapse
Hmm ok, was just confused because there different Specs out there : one says 8926 the other 8226 .
Will start my Stuff tonight, as soon i come Home.
kaliberx said:
Hmm ok, was just confused because there different Specs out there : one says 8926 the other 8226 .
Will start my Stuff tonight, as soon i come Home.
Click to expand...
Click to collapse
try using mine or alpha or any pre started device tree willl save you some time
BTW any knows which audio blob is being used in Motog?
Guys, please use git. Clone the team repo and start commiting changes
Sent from my XT1032 using xda app-developers app
a1Pha said:
Guys, please use git. Clone the team repo and start commiting changes
Sent from my XT1032 using xda app-developers app
Click to expand...
Click to collapse
don't worry, I got u
Sent from my Nexus 7 using Tapatalk
Me too i can do something for kernel... Also i have a sort of device tree on my github (yeah, a sort of)
Inviato dal mio Nexus 7 utilizzando Tapatalk
Lopicl.00 said:
Me too i can do something for kernel... Also i have a sort of device tree on my github (yeah, a sort of)
Inviato dal mio Nexus 7 utilizzando Tapatalk
Click to expand...
Click to collapse
we really do need a kernel tree and if someone could pull the prop files that would be great
Sent from my Nexus 7 using Tapatalk
If you want, you can fork my kernel project.
Hi All!
I have been trying to compile a Kernel for Android from Kernel.org Source. Avidly awaiting a Nexus 7 I got straight to work. I have created a zImage. I have been trying to document the process but rather than type it again I have been doing it here. If someone with a Nexus 7 wants to give this a go I would be very much grateful. This is an ongoing process. I have included the file and necessary instructions here...
It looks like I cant post external URL's .... YET! If you want to post here or PM Me I will send you the links.
If someone could test this for me it would be greatly appreciated.
Thanks
I'd like to help. How do you intend to test the kernel though? (since I'm not sure if it would work in Android, but of course you're probably more experienced than me)
Bogdacutu said:
I'd like to help. How do you intend to test the kernel though? (since I'm not sure if it would work in Android, but of course you're probably more experienced than me)
Click to expand...
Click to collapse
Basically people flash it and then test it. People can provide their own benchmarks if they want. Against their previous Kernel versions etc. I have a sort of active thread on the Neowin Forums about this but I cant post links yet on XDA. I also got my VPS setup today to build and host the files.
JamesSawyer said:
Basically people flash it and then test it. People can provide their own benchmarks if they want. Against their previous Kernel versions etc. I have a sort of active thread on the Neowin Forums about this but I cant post links yet on XDA. I also got my VPS setup today to build and host the files.
Click to expand...
Click to collapse
Okay then, I can do that. I assume you can PM links?
You might be able to state the URL address in your post for your kernel. I'd test it and I guess others may also.
Hi All,
I have someone from Neowin who is going to post the links for me.
At the moment my guide and files are all disjointed I am trying to organize it better.
Great idea! I'll look around your thread @neowin.
What supposedly differences are there from the native android kernel and one compiled using the code from kernel.org?
Personally I just like playing with Bleeding Edge code. You would get all the latest features from source as well as bug fixes most end users wouldn't see. Performance is to be determined, Battery life and CPU performance etc. Its also quite a little Niche that I like been a part of if it all works and comes off.
The kernel you're compiling most likely won't work if you don't even have the machine definitions nor the drivers for your nexus (seeing that you have taken the source directly from kernel.org)
The best of testing a new version would be to backport it but doing so takes an incredible amount of time and considerable skills.
Envoyé de mon Nexus 7 en utilisant Tapatalk
I have used the Prebuilt ToolChain from git and also the defconfig to build the kernel from Google. I have created a boot.img this should make it easier. I am just waiting a Nexus 7 myself to test this anyway.
JamesSawyer said:
I have used the Prebuilt ToolChain from git and also the defconfig to build the kernel from Google. I have created a boot.img this should make it easier. I am just waiting a Nexus 7 myself to test this anyway.
Click to expand...
Click to collapse
You need to have proper board files, proper drivers (device-specific ones) and tons more. I don't think it will work without those. Then chances are it's not going to compile properly; it will throw tons of errors. After you get it to compile, you have to get it to boot. After you get it to boot, you have to get it fully-functional (not necessary if this is a test kernel). So unless you have gone through it all, I don't think it'll work.
BUT I may be wrong.
It compiles no problem, That's what I am wanting people to test :good:
JamesSawyer said:
It compiles no problem, That's what I am wanting people to test :good:
Click to expand...
Click to collapse
Ready to test! Check that neowin thread, but all the links I've tried lead to 404
vrutkovs said:
Ready to test! Check that neowin thread, but all the links I've tried lead to 404
Click to expand...
Click to collapse
Hi!
Well I have not been on this for a few days however I set up a quick and dirty VPS. Looks like the process fell over. I have restarted it and published any files people might find useful on here.
http://svm24652.vps.tagadab.com:8000/
All actual builds are in the build folder.
JamesSawyer said:
Hi!
Well I have not been on this for a few days however I set up a quick and dirty VPS. Looks like the process fell over. I have restarted it and published any files people might find useful on here.
http://svm24652.vps.tagadab.com:8000/
All actual builds are in the build folder.
Click to expand...
Click to collapse
wow you are building 3.13 kernel?! Impressive if it boots
I have a patched 3.4.76 AOSP kernel in my repo thats all hahaha
poondog said:
wow you are building 3.13 kernel?! Impressive if it boots
I have a patched 3.4.76 AOSP kernel in my repo thats all hahaha
Click to expand...
Click to collapse
I am trying to ha! :highfive:
Do you have your 3.4 Kernel? Do you have notes how you built it?
Edit: Updated to include 3.13rc8
I have done some more merging from latest Mainline and Flo Kernel from Google. Its building as we speak. Time to head to Tesco.
Hopefully what I have done will get rid of a compile time error I was having.
Has anyone got the ones I made previous to boot. I have my Nexus 7 on the way as of today so I will be testing it on my own sooooon!! :good:
http://linux.jamessawyer.co.uk:8000/
A bit more easy to remember. There are some test builds and experimental stuff on there too. I might do requests if anyone wants me to make a build for their device let me know. Rather than the Nexus 7 2013. I only did that because thats the device I am getting
The link is down
I am trying to build an image for angler. Looking for make files to build the image for angler (Nexus 6P) Where can i find the vendor/make files to build the image.
How do I see the angler option when I do lunch?
Do a quick search on Github, it should have everything you need.
Thanks for the reply. I looked at the git hub. But I saw so may files. Not sure, which files I need to make the build.
debby_8 said:
Thanks for the reply. I looked at the git hub. But I saw so may files. Not sure, which files I need to make the build.
Click to expand...
Click to collapse
Trying to build the kernel myself, would also appreciate some info. Samsung always at least always includes some help file to specify the toolchain needed etc.
to build angler you need all the device files from android_devie_huawei_angler im fairly sure. Iv gotten my new handset and been working with a guy whos helped me to get a booting port of Omni Rom up and running other than that im not sure exactly how to help.
if your trying to build a image you surely know what files you need to use?
mehmehmen said:
to build angler you need all the device files from android_devie_huawei_angler im fairly sure. Iv gotten my new handset and been working with a guy whos helped me to get a booting port of Omni Rom up and running other than that im not sure exactly how to help.
if your trying to build a image you surely know what files you need to use?
Click to expand...
Click to collapse
Well in my case, at this point I just want to build the kernel. It's really too bad that XDA doesnt accept posts like this on their 'development' forum. On this general FAQ forum I dont think it reaches the right audience and hence no reponse from anybody yet, to this fairly simple question. I wish XDA would support developers a bit more and would allow development questions on the development forum.
I understand what you mean, although the development forums used to get INUNDATED with questions similar to these which would usually be able to be remedied with a bit of googling and a decent amount of reading. I think you would find if you were to go to the actual angler kernel threads and be very concise and polite in asking for any help that someone would actually be happy to help at least a little bit.
You have to remember on the dev forums most people are kind of in the know of what they want to do and roughly how to do it hence why they prefer posts to remain within the realms of people contributing to thread projects and giving test feedback as opposed to asking for help on seperate (although maybe related) issues.
Im currently working on the angler with a couple of guys and we have a booting fully operational OmniRom port in testing stages now, which may end up to me then posting that as a full [ROM] thread and trying to offer support on the device for that rom. The guy that built the rom himself is very good and has helped me understand a lot, with the right attitude and willingness to learn I am sure you would be welcome in the IRC channel where I personally would be happy to try and help you get your head round some things, as the next goal for me regarding the 6p in terms of our project is going to be kernel based compiling as i want to try and get a really robust kernel built now we have a seemingly stable feature full rom built and booting.
Feel free to message me if this sounds like it may be of some help
Regards
Meh
mehmehmen said:
although the development forums used to get INUNDATED with questions similar to these which would usually be able to be remedied with a bit of googling and a decent amount of reading.
Click to expand...
Click to collapse
That happens on any forum.
I think you would find if you were to go to the actual angler kernel threads and be very concise and polite in asking for any help that someone would actually be happy to help at least a little bit.
Click to expand...
Click to collapse
Sure but that would be going off topic on someone's thread.
You have to remember on the dev forums most people are kind of in the know of what they want to do and roughly how to do it hence why they prefer posts to remain within the realms of people contributing to thread projects and giving test feedback as opposed to asking for help on seperate (although maybe related) issues.
Click to expand...
Click to collapse
Everybody has questions, regardless of their level. I was the maintainer for Cyanogenmod Note 4, so if the above would be true, I wouldnt be here I'm sure I can figure out myself how to get the Angler kernel compiling but it would save me, and others who will try the same in the future, quite a bit of trouble if someone who had done it would just post the used toolchain etc.
Anyway you used a lot of words without helping at all. That's exactly my point, when posting on a general forum you can expect these kind of replies. That's why I'd love to see a true development forum here on XDA, not just a 'developer' forum where people just support their projects. Giving support to a project, has not much to do with development.
Nah, I could have expected this. I'll figure it out myself. Thanks but no thanks.
*EDIT* I guess this will work, using toolchain 4.6 like they recommend, it's probably the latest anyway (?)
https://source.android.com/source/building-kernels.html
They dont mention Angler, but I'll try this anyway, I think it might work. And I'll let people know if it worked or not, so someone in the future who reads this thread will know how too. Although I kinda doubt a developer will search the general FAQ forum here ...
Might wanna try asking that on a kernel development thread in Dev section - kernel developers are usually friendly to people willing to rightfully use (and maybe improve) their work. They should be at least give you a vision on how go get the basic Angler kernel up and running.
As for me... I build CM, everything on the CM wiki is mostly enough for me.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Use googles 4.9 aarch64 toolchain for kernel to start off. Any questions feel free to hit me up, better on hangouts though as I forget about XDA sometimes ha. Pm me for email.
rustyjay said:
Use googles 4.9 aarch64 toolchain for kernel to start off. Any questions feel free to hit me up, better on hangouts though as I forget about XDA sometimes ha. Pm me for email.
Click to expand...
Click to collapse
Thanks mate ! That's what I was looking for, will try that one.
---------- Post added at 03:23 AM ---------- Previous post was at 03:03 AM ----------
Ok and it's building !
Steps I took:
1) Download angler kernel here: https://android.googlesource.com/kernel/msm/+/android-msm-angler-3.10-marshmallow-dr
2) Download toolchain with: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9
3) add the toolchain to the path, in my case: export PATH=~/android/toolchains/aarch64-linux-android-4.9/bin:$PATH
4) go to the unpacked kernel dir
5) export ARCH=arm64
6) export SUBARCH=arm64
7) export CROSS_COMPILE=aarch64-linux-android-
8) make angler_defconfig
9) make
Thanks again @rustyjay for the toolchain info !
---------- Post added at 03:32 AM ---------- Previous post was at 03:23 AM ----------
AndyYan said:
As for me... I build CM, everything on the CM wiki is mostly enough for me.
Click to expand...
Click to collapse
As much as I love CM (I was maintainer for the Note 4), I don't particularly see the point of running it on a Nexus device. I just want some kernel tweaks (for example that damn fuel gauge is giving me wakelocks), so I think l wont jump onto CM. But who knows ...
---------- Post added at 03:46 AM ---------- Previous post was at 03:32 AM ----------
Build completed So I guess I just insert the resulting Image.gz-dtb into the boot.img (with android image kitchen for example), right ? Will try tomorrow, but I think that should work. off to bed now ...
Yeah what it basically does when I build aosp, don't know too much about kitchen.
rustyjay said:
Yeah what it basically does when I build aosp, don't know too much about kitchen.
Click to expand...
Click to collapse
Ok I used android image kitchen to replace the Zimage, flashed it and ... it boots
Cool, so that's easy. Now for the next part: building the whole rom ! Any idea on how to do that ? Or where to even download the code ? Is there even a whole ROM to build, including the blobs etc ? I think i saw google releasing a device tree but not the whole ROM, right ? I must say I havent really googled myself this, will look into this today myself too.
*EDIT* yeah here's the device tree: https://android.googlesource.com/device/huawei/angler/ but I dont think it's the whole ROM, going to download it now ...
*EDIT2* No this definitely isnt the whole ROM,not even the device tree There's not a lot in there !?!
*EDIT3* Info here: https://source.android.com/source/running.html
*EDIT4* So as per the link above, it turns out that most drivers are blobs ! Hmm that's a bit disappointing. You buy a Nexus because supposedly it's 'open source', turns out most of it is not.... Anyway so it seems it's just a matter of compiling the sourcecode that IS there and then adding the blobs.
*EDIT5* So this section explains the whole process of setting up the environment, downloading, syncing and building: https://source.android.com/source/requirements.html looks very similar to the CM install/build process indeed !
To me its easier than cm but aosp is what I do the most. And to build for aosp you'll need angler device tree and vendor blobs. Ive been using the huawei vendor from pure nexus github.
Aosp out of the box is really unfinished though to me so it takes some work with cherry picks to get everything slick.
rustyjay said:
To me its easier than cm but aosp is what I do the most. And to build for aosp you'll need angler device tree and vendor blobs. Ive been using the huawei vendor from pure nexus github.
Aosp out of the box is really unfinished though to me so it takes some work with cherry picks to get everything slick.
Click to expand...
Click to collapse
Thanks for all your info, much appreciated. Currently syncing to AOSP like explained on that page I linked, will take a few hours I guess.
BTW, what are you exactly building this for ? Just some tweaks ? I saw this kernel wakelock qpnp_fg myself, I just disabled CONFIG_QPNP_FG=y in the defconfig, the wakelock is gone but like I expected, the battery gauge doesnt work anymore neither, lol. Will need to look into it for a real fix I guess.
Also I'm planning to make an option to default MTP as USB connection. It's just plain crazy Google left that out in 6.0 !
I've been building for myself for like 2 years now, kernels I just started really messing with about 6 months ago. I just had a hard time finding a ROM with stuff I like and not a million other mods added to it. Now its just hard for me to stay on stock or a ROM I didn't cook up.
rustyjay said:
I've been building for myself for like 2 years now, kernels I just started really messing with about 6 months ago. I just had a hard time finding a ROM with stuff I like and not a million other mods added to it. Now its just hard for me to stay on stock or a ROM I didn't cook up.
Click to expand...
Click to collapse
It's my first Nexus and am just loving it already. I mean, getting CM to run on a Samsung device is of course fun, but it's also just SO much work. I dont think I could do it all over again on another non AOSP device.
Now on nexus, just syncing directly from google and building it, what a breeze this is !
Oh yeah if your into building, nexus is really the only way to go. My first nexus was the ns in '10 and have had a nexus phone ever since
OK, so I don't know anyone else with a 6p but want a second opinion on my rom/kernel so far. I do not want to start and maintain a thread, why I'm posting this here.
https://drive.google.com/file/d/0B_f86wvdx8LKUm12NHpxSVBhVEk/view
Its not a kitchen sink rom, if there's interest I'll make a changelog with the proper credits to people and probably upload builds to my drive.
rustyjay said:
OK, so I don't know anyone else with a 6p but want a second opinion on my rom/kernel so far. I do not want to start and maintain a thread, why I'm posting this here.
https://drive.google.com/file/d/0B_f86wvdx8LKUm12NHpxSVBhVEk/view
Its not a kitchen sink rom, if there's interest I'll make a changelog with the proper credits to people and probably upload builds to my drive.
Click to expand...
Click to collapse
What are your main changes ?
Anyway I just finished building the ROM myself. It ends up with system.img, userdata.img, recover.img, ramdisk.img, ramdisk-recover.img. I'd probably just flash boot.img and system.img, right ? That userdata.img, what is that exactly anyway ? If I flash that I'll lose my user partition=installed apps, I guess ?
BTW I didnt pull any blobs so I guess it wont run anyway. I guess I first need to extract the blobs ? Does the AOSP build process include the blobs automatically ?
Thanks !
Hi out there!
Today i've looked another time for kernel sources of our loved (and hated) phone.
The only full source i've found was this one on the Sony Website:
http://developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-33-2-a-2-37-and-33-2-b-2-37/
I don't have the time nor the knowledge of kerneldevelopment to check this out.
My question is:
Is it possible to port this Sony kernel, to have a working p9000 kernel, with the goal to have let's say DirtyUnicorn running?
greetings
vsrookie
vsrookie said:
Hi out there!
Today i've looked another time for kernel sources of our loved (and hated) phone.
The only full source i've found was this one on the Sony Website:
http://developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-33-2-a-2-37-and-33-2-b-2-37/
I don't have the time nor the knowledge of kerneldevelopment to check this out.
My question is:
Is it possible to port this Sony kernel, to have a working p9000 kernel, with the goal to have let's say DirtyUnicorn running?
greetings
vsrookie
Click to expand...
Click to collapse
Kernel and ROM are 2 different things. We could get DU working on stock kernel, but we need valid device and vendor trees. Sometimes you can make them yourself, other times the manufacturers provide them.
Jonny said:
Kernel and ROM are 2 different things. We could get DU working on stock kernel, but we need valid device and vendor trees. Sometimes you can make them yourself, other times the manufacturers provide them.
Click to expand...
Click to collapse
Ok. But an android system need functions from the kernel, don't they?
What do you exactly mean with device tree and vendor tree? The drivers for the components? If it is so, then can't we "just take them" and integrate in the kernel source?
greetings
vsrookie
Ps: Basically i need to read sonething about Android development. [emoji12]
Sent from my P9000 using XDA-Developers mobile app
vsrookie said:
Ok. But an android system need functions from the kernel, don't they?
What do you exactly mean with device tree and vendor tree? The drivers for the components? If it is so, then can't we "just take them" and integrate in the kernel source?
greetings
vsrookie
Ps: Basically i need to read sonething about Android development. [emoji12]
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Vendor tree example >>> https://github.com/omnirom/android_vendor_omni
Device tree example >>> https://github.com/omnirom/android_device_sony_kitakami-common
The Android system does use functions from the kernel but its not really "aware" of doing so, you can run custom ROM's like DU, Omni etc from stock kernels most of the time without any issues.
So basically: When/If Elephone decides to release CM13, it's still possible they won't give us the vendor/device tree? So that's basically a byebye to porting roms?
Sorry, I'm a nub too.
Boristruyens said:
So basically: When/If Elephone decides to release CM13, it's still possible they won't give us the vendor/device tree? So that's basically a byebye to porting roms?
Sorry, I'm a nub too.
Click to expand...
Click to collapse
Tbh that is a massive probability, making device and vendor trees is not non-trivial and is a lot of work. For instance the HTC 10 still doesn't have a stable CM build, and there are some hard hitters in the AOSP dev world that own that device. I'll have a look and see what I can do but I'm an app developer and an apk editor (i.e. Java and Smali are more my languages than C/C++) more than a source builder so I might not be able to do much.
Can i use it for making recovery for moto m
The P9000 has a kernel on github anyway ...
Hey guys!
NEWS 1: Guys, with help of another developer we are working on the device tree. The builds currently are booting up and there are bugs to be fixed. We have currently released LineageOS 15.0 first test build only to the insiders (.i.e. testers of K10 - K420DS/N).
NEWS 2: We will also be working on K10 MS428. We will be compiling LOS 14.1 for the phone.
Source: https://github.com/LG-K10/android_device_lge_m216
does k430dsY also counts in this project, sir?
EDIT: im a pure noob both in android and english grammar
black_is_colour said:
does k430dsY also counts in this project, sir?
EDIT: im a pure noob both in android and english grammar
Click to expand...
Click to collapse
Yes.
I'd also love to see the LG K10 K410 Dual or Single SIM variant ROM. Is that possible?
abittercoffee73 said:
I'd also love to see the LG K10 K410 Dual or Single SIM variant ROM. Is that possible?
Click to expand...
Click to collapse
yes.
pvineeth97 said:
yes.
Click to expand...
Click to collapse
Good to hear that. But is the 1 or 1,5 GB of RAM enough to maintain a smooth run of the Android 7? And, well, when we can expect the earliest results? Sorry for that, but I'm really interested in this project.
Woohoo!
GuyInDogSuit said:
Woohoo!
Click to expand...
Click to collapse
I already updated my guide.
https://forum.xda-developers.com/lg-k10/development/unofficial-metropcs-428-t3578814
GuyInDogSuit said:
I think so. He ported TWRP to the MS428, so it's possible.
@pvineeth97, any word on this?
Click to expand...
Click to collapse
I will start compiling 7.1 soon
I am busy with my course projects and exams. I will start compiling it in May.
Once AOSP is available I'll gladly build and maintain LineageOS. I don't have the time to work from scratch, porting is a ton of work I'm not ready to commit to! Good luck with this, looking forward to it.
Can you post link from device tree if it's online? (Not for TWRP but for AOSP/LineageOS)
Professor Woland said:
Can you post link from device tree if it's online? (Not for TWRP but for AOSP/LineageOS)
Click to expand...
Click to collapse
I am not ready with those yet. I am working on the device tree. Once I finish compiling LineageOS I will upload the device tree.
LineageOS/AOSP for k430 too?
Please keep on topic within this thread! Thanks all
Forum moderator,
Matt
a_lewicki said:
LineageOS/AOSP for k430 too?
Click to expand...
Click to collapse
Yeah. Later for K430/MTK.
Take my kiss, thnx; Waiting for your work.
+ I have a k430dsy device.
I'm working on the k428/ms428 variants and pvineeth97 is working on the 420 variants. Others may come down the road.
I'm building the device tree now based on a few unofficial builds for devices with the msm8909 SoC, so with some luck it may not take too much work to get it going for us. All depends on how much time I can dedicate to it.
JoeMoDo said:
I'm working on the k428/ms428 variants and pvineeth97 is working on the 420 variants. Others may come down the road.
I'm building the device tree now based on the BQ Aquarius X5 tree I forked from the LineageOS github. It has the same SoC as the K428, so with some luck it may not take too much work to get it going for us. All depends on how much time I can dedicate to it.
Click to expand...
Click to collapse
Right on! Good job and good luck!
Once I'm done, and have it compiled and bootable, I'll need a couple beta testers to help me iron out kinks before releasing publicly (unless of course it just works flawlessly ). This is only open to k428/ms428 owners who can competently recover from brick on their own, and are willing to produce adequate logcats regarding any issues. Hoping to have a bootable rom in the coming weeks, we'll go from there. Keep in mind bootable may mean far from stable. Many things may be broken at first. If you're not willing to dedicate the time and work to help me fix such issues (ie, camera not working, audio not working, data not working, everything not working), please don't volunteer. If you aren't competent with adb, don't know how to produce a logcat, and don't know what to do with a bricked device, please don't volunteer. I won't have the time nor patience to walk anyone through fixing their device, and work on the port. If you feel competent, you can message me with your interest.