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 ?
Related
This script is for if you are compiling android from source and want to convert one tree to another name. For instance, we have been using a modified mako tree so if you wanted to start compiling for the Optimus G you would download the mako tree and modify it to our device. That would normally mean you need to replace all instances of the word mako with geeb or whatever you want to call it. and also rename some files as well. this script does it all for you.
just put it in the device tree directory and run it and it will prompt you for the rest.
it will ask you about the current device name and the new device name. the current device name should be the name of the device you are switching from and the new device name should be whatever you want to rename it to. both should be just one word like mako or skyrocket or geeb or geeb_att_us (underscores are OK).
Download -------> name-changer.py
Click to expand...
Click to collapse
Click to expand...
Click to collapse
the script requires python to run (it works in python 2.5....not sure about python3)
just run (in the device tree directory):
Code:
./name-changer.py
please let me know if you have any suggestions or bugs. thanks
So if I'm reading this correctly, you would be able to have the sources for say paranoid android, then you put this in there and it would edit the sources to work for our phone?
Or am I way over thinking this?
Sent from my Nexus 4 using Tapatalk 2
MrZim4 said:
So if I'm reading this correctly, you would be able to have the sources for say paranoid android, then you put this in there and it would edit the sources to work for our phone?
Or am I way over thinking this?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
This is for the device source.... Not android source. Its for converting one tree to another phone. I just made it because I tend to do this manually all the time so I just wanted to automate the process.
Sent from my LG-E970 using xda app-developers app
Complete Source for the MediaTek MT6589 is available at Sony Open Source Archives
I have confirmed that it is full and shows only warnings while building and builds without errors.
What Next?The config?
It is the full source for the Xperia C. :good:
dev0xteam said:
Complete Source for the MediaTek MT6589 is available at Sony Open Source Archives
I have confirmed that it is full and shows only warnings while building and builds without errors.
What Next?The config?
Click to expand...
Click to collapse
I believe the config file is device dependent so will be different for a116......
still if anyone takes up the project of building it for a116 he has to modify the config :fingers-crossed:
here is kernel source of mmx canvas HD aka fly iq451
https://disk.yandex.ru/public/?hash=VJjzmkQPL8/elQ2+VKi89/k0nd//iBWRDiIhNZOCrzg=&locale=ru
Dj_Ignatius said:
here is kernel source of mmx canvas HD aka fly iq451
https://disk.yandex.ru/public/?hash=VJjzmkQPL8/elQ2+VKi89/k0nd//iBWRDiIhNZOCrzg=&locale=ru
Click to expand...
Click to collapse
Is it complete?
dev0xteam said:
Is it complete?
Click to expand...
Click to collapse
i think yes..
Ok. The sony source is not fully complete but.enough to build a kernel. Still there is some problem in config or something else which is not allowing the kernel to compile..
Sent from my A116 using xda app-developers app
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
konnorrigby said:
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
Click to expand...
Click to collapse
A general question :- i previously had mmx a75 which of course didn't had the sources but overclocking through mtkcpu from playstore was achieved..!! So why our device can't be overclocked using the same app..??
Sent from my A116 using xda premium
Hopefully this means we get cyanogen based ROMs soon
Sent from my Canvas HD running X-flare V2 ROM
axis.meister said:
Hopefully this means we get cyanogen based ROMs soon
Sent from my Canvas HD running X-flare V2 ROM
Click to expand...
Click to collapse
Did you read the thread?
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
konnorrigby said:
Did you read the thread?
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Read the OP and got my hopes high. Read your post now and ...
lets hope Mediatek actually releases full sources in the future.
konnorrigby said:
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
Click to expand...
Click to collapse
http://www.hacktohell.org/2013/07/mediatek-mt6589-complete-source.html#.Ui5G3sanojp
can this be the full source? i am not a dev so idk anything about it there is a link in the link i gave u maybe u can see it and tell us
so any good news about custom kernel?
Is this enough to build a custom kernel atleast?
Sent from my Micromax A116 using Tapatalk
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
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?