I downloaded the OmniROM source but then I a bit confused what to do when it comes to adding a device to the ROM source. Can anyone help me with this.........
thejoker said:
I downloaded the OmniROM source but then I a bit confused what to do when it comes to adding a device to the ROM source. Can anyone help me with this.........
Click to expand...
Click to collapse
Are you trying to add a device already supported by Omni or adding a new device not already supported (In which case you will need to create a new device tree)?
shimp208 said:
Are you trying to add a device already supported by Omni or adding a new device not already supported (In which case you will need to create a new device tree)?
Click to expand...
Click to collapse
I think im adding a new device.BTW im making rom for redmi 1s.So how should I do it
thejoker said:
I think im adding a new device.BTW im making rom for redmi 1s.So how should I do it
Click to expand...
Click to collapse
Since your manufacture doesn't release the kernel source for your device that will make things a little bit different. But I would recommend checking out and following the steps in this guide, and then using this guide to convert the device tree to be Omni ROM compatible. The best way to get experience with creating device tree's is to look at similar device tree's to the device you own (Same SoC, same screen, etc.) and convert that device tree to suite your device. Let me know if you still have questions I'll be happy to answer them for you.
shimp208 said:
Since your manufacture doesn't release the kernel source for your device that will make things a little bit different. But I would recommend checking out and following the steps in this guide, and then using this guide to convert the device tree to be Omni ROM compatible. The best way to get experience with creating device tree's is to look at similar device tree's to the device you own (Same SoC, same screen, etc.) and convert that device tree to suite your device. Let me know if you still have questions I'll be happy to answer them for you.
Click to expand...
Click to collapse
The device tree and vendor tree both are available at github.
https://github.com/armani-dev
thejoker said:
The device tree and vendor tree both are available at github.
https://github.com/armani-dev
Click to expand...
Click to collapse
In that case it will be easier for you to compile Omni, what I would recommend doing is downloading the device tree and vendor tree for your device, and placing them in your Omirom source vendor folder and device folder respectively, and then taking the omni_armani.mk from here and placing it in your device folder that you downloaded above and using that to start compiling Omnirom.
shimp208 said:
In that case it will be easier for you to compile Omni, what I would recommend doing is downloading the device tree and vendor tree for your device, and placing them in your Omirom source vendor folder and device folder respectively, and then taking the omni_armani.mk from here and placing it in your device folder that you downloaded above and using that to start compiling Omnirom.
Click to expand...
Click to collapse
I downloaded both and placed the folders in their respective folders.But do I need to edit some .mk files for auccessfull compilation??Because everytime I lunch,I get errors.
thejoker said:
I downloaded both and placed the folders in their respective folders.But do I need to edit some .mk files for auccessfull compilation??Because everytime I lunch,I get errors.
Click to expand...
Click to collapse
Make sure your folder structure matches the device and vendor tree names for example it should be: "device/xiaomi/armani" you can see in full_armani.mk the developer has it set as "device/xiaomi/armani/" which means you should do the same. A couple of years ago I was compiling something for the Droid 1 and was using a device and vendor tree I had downloaded and I was getting an error about lunch could't find the device turns out I had my folders as device/moto/sholes when the developer had it in their tree as device/motorola/sholes which solved the lunch problem. Let me know if you still have questions.
Make sure your folder structure matches the device and vendor tree names for example it should be: "device/xiaomi/armani" you can see in full_armani.mk the developer has it set as "device/xiaomi/armani/" which means you should do the same. A couple of years ago I was compiling something for the Droid 1 and was using a device and vendor tree I had downloaded and I was getting an error about lunch could't find the device turns out I had my folders as device/moto/sholes when the developer had it in their tree as device/motorola/sholes which solved the lunch problem. Let me know if you still have questions.
Click to expand...
Click to collapse
Do I have to edit the Android.mk file in the device tree of my device????
thejoker said:
Do I have to edit the Android.mk file in the device tree of my device????
Click to expand...
Click to collapse
It's easier to just have your folder structure in your OmniROM source match the structure indicated by the device tree.
@shimp208 @thejoker anyone free to guide me? i am also trying to build omni rom for my device.
have snyced the repo and even have most of the stuff thats needed figured out. but can't figure out what goes where?
this is the device tree that i am using, i added it to local manifest.
Now the files which i need to edit mentioned on this page http://docs.omnirom.org/Porting_Omni_To_Your_Device
are now here to be found in the device folder? where are they??
i found them at on other person device tree of my device which i edited just to figure out stuff. but now where to place them?? also i can't seem to figure out the json file mentied on this webpage .
any sort of help will be appreciated.
Kapiljhajhria said:
@[email protected] anyone free to guide me? i am also trying to build omni rom for my device.
have snyced the repo and even have most of the stuff thats needed figured out. but can't figure out what goes where?
this is the device tree that i am using, i added it to local manifest.
Now the files which i need to edit mentioned on this page http://docs.omnirom.org/Porting_Omni_To_Your_Device
are now here to be found in the device folder? where are they??
i found them at on other person device tree of my device which i edited just to figure out stuff. but now where to place them?? also i can't seem to figure out the json file mentied on this webpage .
any sort of help will be appreciated.
Click to expand...
Click to collapse
Which specific files are you not sure where to place? A good starting point is to look where they are placed on a similar device tree and place them there. If you can provide some more details it will be very helpful. Also I am in the process of moving back to school when I get my stuff setup over the next day or so I'll try and take a closer look for you .
shimp208 said:
Which specific files are you not sure where to place? A good starting point is to look where they are placed on a similar device tree and place them there. If you can provide some more details it will be very helpful. Also I am in the process of moving back to school when I get my stuff setup over the next day or so I'll try and take a closer look for you .
Click to expand...
Click to collapse
here is the thread which i created. i have explained my sitaution in details.
http://forum.xda-developers.com/chef-central/android/advice-help-porting-omni-rom-op2-t3284334
Related
Hi guys,
I went to check for the HTC DX source code on htcdev.com, and saw there were around 31 sources, but they're are all CRC's...
Could anyone please explain to me, what is a CRC? I tried googling it, but it didn't really help.
Sent from my HTC Desire X using xda premium
kernel source
Lloir said:
kernel source
Click to expand...
Click to collapse
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
infernal77 said:
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
Click to expand...
Click to collapse
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Yasir Javed Ansari said:
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Click to expand...
Click to collapse
Thanks, Yasir, I know lli0r made a device and vendor tree, but he said the vendor tree might be incomplete. He tried to make us a CM9 but hasn't got the device itself. I also read you can extract the files from a running device, but for that you need extract-files.sh or proprietary-files.sh, which isn't in there. I'm sure I can google and find one of those files from another device and try to run them on mine, but they're probably device-specific as well. And there isn't one of those files in lli0r's github. I checked that I'm sorry, I am ompletely new to Android, let alone building roms, but I love to just experiment a bit
Btw, when are you getting your Desire X ?
Hello,
I wanted to discuss means of creating a device tree for the Samsung Galaxy S4 I9500 so the development can start for the ROM, What is putting us off the track ? What do we need to reach a fully working device tree ?
Hope we could reach something out together ..
Look here
Faryaab has already created one. Let's fork the main repo or branch it with individual repository.. Let's create a team and start working on it
I will set up my Linux machine tonight. Hopefully, we can achieve what we want
Rahulrulez said:
Faryaab has already created one. Let's fork the main repo or branch it with individual repository.. Let's create a team and start working on it
I will set up my Linux machine tonight. Hopefully, we can achieve what we want
Click to expand...
Click to collapse
Perfect .. As I want to release for this device and the lack of a properly working Device tree is stopping me !
We can not really start on Faryaab's tree. He has given up on the I9500. He is not willing to develop it further (as far as I know). But I still thank him for kick starting it
We need another complete tree now
There's a hell of a lot more involved than creating the device tree... There is no Exynos5 "Octa" platform support anywhere in the tree.
Each platform almost always requires some degree of customization to the frameworks to support it - the required customizations for Exynos5 "Octa" are undocumented. (search the tree for QCOM_HARDWARE or EXYNOS4_ENHANCEMENTS for some examples.)
Anyone can create a tree. Implementing support for a new platform throughout the codebase is a whole other story - and no one wanting to do THAT so far is why the I9500 has no CM support.
Entropy512 said:
There's a hell of a lot more involved than creating the device tree... There is no Exynos5 "Octa" platform support anywhere in the tree.
Each platform almost always requires some degree of customization to the frameworks to support it - the required customizations for Exynos5 "Octa" are undocumented. (search the tree for QCOM_HARDWARE or EXYNOS4_ENHANCEMENTS for some examples.)
Anyone can create a tree. Implementing support for a new platform throughout the codebase is a whole other story - and no one wanting to do THAT so far is why the I9500 has no CM support.
Click to expand...
Click to collapse
I know, what I am thinking is just try to port framework and other important libraries and see if that works. Exynos is badly documented
maradonaiconboy said:
Perfect .. As I want to release for this device and the lack of a properly working Device tree is stopping me !
Clubvegas999
Click to expand...
Click to collapse
Two posts above yours, He said that it's not going to be easy simply because Samsung just can't document a thing properly !
With lack of proper documentation , It would be extremely hard to create the device tree .. I too want to build my ROM for the i9500 but we need to figure something out to be able to continue ..
Folks just coming by and asking it to get/keep it going - that's not dev talk and plenty of other forums to post that in.
So if your post disappeared... that's why.
Thanks.
Did you guys see ewmno device tree for i9500?
Follow Me on Twiiter @razer1224
---------- Post added at 11:48 AM ---------- Previous post was at 11:45 AM ----------
johnhany97 said:
Two posts above yours, He said that it's not going to be easy simply because Samsung just can't document a thing properly !
With lack of proper documentation , It would be extremely hard to create the device tree .. I too want to build my ROM for the i9500 but we need to figure something out to be able to continue ..
Click to expand...
Click to collapse
Did you check camerawrapper. Cpp of Xperia... Since GT-I9500 uses a Exmor Rs sensor
Follow Me on Twiiter @razer1224
---------- Post added at 11:51 AM ---------- Previous post was at 11:48 AM ----------
I am forking farylaab repo too
Dont we need proprietary files?
Follow Me on Twiiter @razer1224
ill try to work on the vendor tree to
i will push today the basic files
RD's I think you guys can help me
Device Tree (Forked From Faryaab)
https://github.com/KiranSurath/android_device_samsung_i9500
Vendor Tree (Full Experiment)
https://github.com/KiranSurath/android_vendor_samsung_GT-i9500
We Can Work as a Team
razer1224 said:
Device Tree (Forked From Faryaab)
https://github.com/KiranSurath/android_device_samsung_i9500
Vendor Tree (Full Experiment)
https://github.com/KiranSurath/android_vendor_samsung_GT-i9500
We Can Work as a Team
Click to expand...
Click to collapse
I want to work with you as a team but my exams are not allowing me to do so. As soon as my exams gets ,I will join with you.
Sent from my GT-I9500 using XDA Premium HD app
Trying to build with only device tree
Follow Me on Twiiter @razer1224
Sent from my SCH-I545 using xda app-developers app
razer1224 said:
Trying to build with only device tree
Follow Me on Twiiter @razer1224
Click to expand...
Click to collapse
Did it work with you or not ?
johnhany97 said:
Did it work with you or not ?
Click to expand...
Click to collapse
No it didn't.
Status 7 error.
Akhil said:
No it didn't.
Status 7 error.
Click to expand...
Click to collapse
do you replaced folders in google source by the same from opesnsource.samsung com ?
and why in i9500-vendor.mk you wrote
$(call inherit-product, vendor/htc/samsung/i9500-vendor-blobs.mk)
Click to expand...
Click to collapse
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing, called “asserts”
You can delete this assert in updater-script to bypass this verification
did anyone brick there device from compiling error ?
S.a.M.e.R_d said:
did anyone brick there device from compiling error ?
Click to expand...
Click to collapse
oh, common.. Why you think device can be bricked by this? It won't. Just don't mess with boot block (and don't use engineering bootloader because it doesn't set boot block hardware write protection) and you always will be able to enter download mode and then flash whatever you want through Odin.
Hello there.
Here is device tree:
DOWNLOAD from My github.
It is in Alpha (developers) release as probably You will need to fix few errors by hand....but, anyway, someone must to start with something....
Kernel is in this moment not released by HTC, but We can do some things with prebuilt kernel.
PREPARATION:
Please, after You pull it inside cm-13 source, GET VENDOR FILES by cd into device/htc/htc_a51ul and
Code:
./extract-files.sh
(with connected phone in adb enabled mode)
Second, please comment out in BoardConfig.mk following line:
Code:
TW_THEME := pure4
and uncomment:
Code:
TW_THEME := portrait_hdpi
as I wasn't release yet pure4 design skin to github.
Third, if You cannot handle "BSP" (and it's about 99% that You can't ) comment out:
Code:
TARGET_USES_QCOM_BSP := true
and remove flag
Code:
-DQCOM_BSP
from COMMON_GLOBAL_CFLAGS
Then You are ready to build (until first error come)
PLEASE, don't take advantage with this if You really don't know how to handle errors as I will NOT help or respond on PM's regarding help about building this.
When something come up, will make post/and/or attach possible working image.
Cheers
EDIT1: dts is attached, so if someone like to play with kernel... Check it out. I will put changes to 64bit kernel on My github soon with this device tree.
EDIT2: kernel is updated. You can grab it on MY GITHUB
EDIT3: BoardConfig.mk is changed, so no need to change twrp skin and BSP (steps second and third).
Thank you, btw. great job!
Great beginning!
So, things changed... Kernel updated, device tree updated, read.me updated.
Please be free to pull Kernel and make changes so We can got it working. I was made first steps and don't have so much time to make all this together work but if few of dev's come aboard and take work, We can make it work soon.
So i am quite interested in this device, don't own it yet so @fergy would appriciate it, if you could push vendor (too much work to do it all manually, especially the makefile ).
Thanks.
List of vendor files are under my github device tree... When you extract files, makefile will be builded under vendor/htc/devicename
fergy said:
List of vendor files are under my github device tree... When you extract files, makefile will be builded under vendor/htc/devicename
Click to expand...
Click to collapse
I know that, but since i don't own the device i can't pull blobs using the script (obviously), so it would be awesome if you could create the vendor (run the script), git init and push
btw i remade the device tree based on the htc a5, looks much better now: https://github.com/Thecrazyskull/device_htc_a51ul
Thanks.
Thecrazyskull said:
I know that, but since i don't own the device i can't pull blobs using the script (obviously), so it would be awesome if you could create the vendor (run the script), git init and push
btw i remade the device tree based on the htc a5, looks much better now: https://github.com/Thecrazyskull/device_htc_a51ul
Thanks.
Click to expand...
Click to collapse
https://github.com/Skorupa123/vendor_htc_htc_a51ul
Recently I uploaded it, so, enjoy!
Skorupa123 said:
https://github.com/Skorupa123/vendor_htc_htc_a51ul
Recently I uploaded it, so, enjoy!
Click to expand...
Click to collapse
Thanks a damn lot!!!
@Thecrazyskull Do you make cyanogenmod?
@Thecrazyskull
I know that fergy aboneded our project.. But you.. Do you continue? Can i help you?
Dragonfail said:
@Thecrazyskull
I know that fergy aboneded our project.. But you.. Do you continue? Can i help you?
Click to expand...
Click to collapse
I pretty much lost interest, especially since i dont want to develop without owning the device.
Thecrazyskull said:
I pretty much lost interest, especially since i dont want to develop without owning the device.
Click to expand...
Click to collapse
I can help you.. please.. continue...
Sent from my HTC Desire 820 using XDA Free mobile app
Dragonfail said:
I can help you.. please.. continue...
Sent from my HTC Desire 820 using XDA Free mobile app
Click to expand...
Click to collapse
Its a pain for myself, and i don't wanna go through that so i won't be developing for this device anymore unless i can get my hands on one (very unlikely)
What is thts device tree not understanding
chitranjn_k said:
What is thts device tree not understanding
Click to expand...
Click to collapse
This is not really the place to ask...
chitranjn_k said:
What is thts device tree not understanding
Click to expand...
Click to collapse
If you don't understand it you don't need it.
Wysłano z Tapatalk / Sent with Tapatalk
Any idea about htc desire 826 dual sim i.e. a52_dtul device tree ?
So, after destroying a tremendous amount of data and a whole lot of wait, I finally synced the whole OmniROM 6.0 source code via repo. Now I want to compile it for my device XOLO BLACK (Codename: BLACK) so, can somebody tell me how I can and what am I gonna need (I mean files, like vendor files, kernel etc.)?
Also, how can I extract its device tree? Because it's not available online.
You will need the full kernel source code to even begin and everything I have found says it is not released. Without it you are out of luck.
zelendel said:
You will need the full kernel source code to even begin and everything I have found says it is not released. Without it you are out of luck.
Click to expand...
Click to collapse
No no, kernel is here: https://github.com/hiveinside/xolo_kernel
What do I need now?
NutVolt said:
No no, kernel is here: https://github.com/hiveinside/xolo_kernel
What do I need now?
Click to expand...
Click to collapse
You will need the device tree as well as working on the errors in the kernel as they come up and they will. Also you may have to fix any issues with the source as it only contains the open source parts. Check out some of the building tuts on the site.
It will not be a simple matter of adding the kernel and stuff and then building. It normally takes weeks of bug hunting and fixing to get it to even boot.
zelendel said:
You will need the device tree as well as working on the errors in the kernel as they come up and they will. Also you may have to fix any issues with the source as it only contains the open source parts. Check out some of the building tuts on the site.
It will not be a simple matter of adding the kernel and stuff and then building. It normally takes weeks of bug hunting and fixing to get it to even boot.
Click to expand...
Click to collapse
I know it's gonna take long but if I can't even start then I'll feel very bad, all the hard work I've done to just fetch the source.
Anyway, how can I make a device tree? Can you teach me?
I had made a thread about creating a custom ROM for Android over here: http://forum.xda-developers.com/general/xda-assist/building-custom-android-rom-t3526514#post70277383 and Art Vanderlay suggested I post here, so here it is.
I own the BLU Energy X 2, and I am in need of the Device Tree and Vendor Blobs for the phone to create a custom ROM based off of CyanogenMod. My device currently has CyanogenMod on it, however it's an unofficial port for the BLU Studio Selfie. I am not sure how the dev of that ROM got these files, however the Infinix Hot 2 is a "clone" of that device, so he may have just ported it from there, or it may have not even needed porting at all Anyways, for me to create a custom ROM based off of CyanogenMod, I need the Device Tree and Vendor Blobs. I do have the ProjectConfig file if that helps.
These files are usually somewhere on GitHub, but due to the development community for BLU devices in general being almost non-existant, these files are nowhere to be found. So, how can I get these files for my device to start building a custom ROM? Thanks
If you need any other information, please reply.
Device Specs:
BLU Energy X 2
Model #: E050U
Android Version: 5.1 Lollipop
Kernel Version: 3.10.74+
Chipset: MT6580
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Audriuskins said:
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Click to expand...
Click to collapse
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
NateDev473 said:
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
Click to expand...
Click to collapse
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Audriuskins said:
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Click to expand...
Click to collapse
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
NateDev473 said:
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
Click to expand...
Click to collapse
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Audriuskins said:
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Click to expand...
Click to collapse
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
These come from the oem. While the directions posted sometimes work it is dirty hacking at best and never stable. This is why developers stay away from mtk devices and they are really only used in cheap devices.
NateDev473 said:
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
Click to expand...
Click to collapse
Search on Github
Audriuskins said:
Search on Github
Click to expand...
Click to collapse
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
NateDev473 said:
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
Click to expand...
Click to collapse
No idea x)
I guess you can try xd
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
Ok, thanks
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
NateDev473 said:
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
Click to expand...
Click to collapse
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Audriuskins said:
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Click to expand...
Click to collapse
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
NateDev473 said:
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
Click to expand...
Click to collapse
I can't help you very much, because I'm new in MTK development ://
Audriuskins said:
I can't help you very much, because I'm new in MTK development ://
Click to expand...
Click to collapse
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
NateDev473 said:
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
Click to expand...
Click to collapse
I dont know