Could someone point me to the repository containg the vendor overlay for the desire on a gb 2.3.7 build
e.g. here is the code i would use if building for the incredible
code:
cd ~/mydroid/system/device
cd htc
mkdir inc
cd inc
git clone http://github.com/koush/android_device_htc_inc.git inc
What i want to know is what url should i put in place of the red text for the desire?
Thanks I'm new to this
You could just use an extract from a working Rom or phone using the extract or unzip sh in the cm repository
Sent from my HTC Desire using xda premium
Are you suggesting i build it for a generic device and add drivers afterwards?
Pull the ones from cm7? Seems like a decent plan.
No you build everything specific for the bravo. You use the extracted proprietory files to complete the source
Sent from my HTC Desire using xda premium
rootSU said:
No you build everything specific for the bravo. You use the extracted proprietory files to complete the source
Sent from my HTC Desire using xda premium
Click to expand...
Click to collapse
Ye but apart from the proprietary files he'll also need the vendor folder containing all device specific non proprietary files and make-files for desire as well as a script to pull the proprietary files, and this seems to be the one he's looking for.
Non of the above is included for the desire in AOSP, so he'll need to get it somewhere else like from the cm7 project.
And device. Possibly hardware too
Sent from my HTC Desire using xda premium
Thank you for all the replies i'm still rather confused but i'm going to try using the vendor overlay for cyanogen with the make files and script and just see what happens
Sent from my HTC Desire using XDA App
Yep it should work ok, even though the make-files could need some adjusting. As a second option, Oxygen is also open source with desire support, so you could borrow those as well, but they should be pretty similar to the cm ones.
Rootsu when could you give me a short explanation of how you went about building etc. I have set up the builds environment and can build a rom for the emulator or nexus s. All i'm trying to do is build a basic stock GB ROM for the desire as part of teaching myself how to develop Android roms I understand dgb was a similar room for you which you have since worked on and published to these forums
Sent from my HTC Desire using XDA App
I used the redux 1.2 github repository to start with. I started there as for me it was the best Rom.
All I had to do to compile was get the proprietory files using the extract.sh
What I then did was learn my way around the source and work out how to change what needed changing. Swapping out the majority of the source with the Google repository.
There's still stuff I need to learn though, like changing the kernel but time is an issue for me.
I would recommend using redux or oxygen source as a starting point if I were you as cm is very different to pure aosp. I didn't know oxygen sources were available....
Sent from my HTC Desire using xda premium
A simple guide containing the oxygen and dev-null git links:
http://forum.oxygen.im/viewtopic.php?id=688
Thanks everyone really helpful
Sent from my HTC Desire using XDA App
Related
Herro all!
If my research serves me right, HTC has yet to release the source code for the kernel used in the Desire Z. I've tried compiling a kernel from Cyanogen's repo https://github.com/CyanogenMod/htc-kernel-vision but it doesn't boot. I pulled the config from the stock ROM and disabled some (supposedly) unnecessary drivers so that it would compile.
Does anyone have working kernel sources for Sense ROMs? I hope to make this thread a unified effort to fix the available sources.
That's odd. It should work on both. My kernel boots fine on the stock sense rom. And if you look at developer.htc.com the only kernel source released is the desire Z, the G2 has the source of all system files
Sent from my T-Mobile G2 using XDA App
You're probably running into the same issue I did when i started building Vision kernels. The base offset is different for these boot images, it needs to be 0x04000000.
rmk40 said:
You're probably running into the same issue I did when i started building Vision kernels. The base offset is different for these boot images, it needs to be 0x04000000.
Click to expand...
Click to collapse
Thanks. I'll test and post my repo up when I get something going.
Can someone who knows? Post a TUT to build the vision kernel? That's the only thing i am missing on my mac
Thanks if anyone does it.
i think that link is broken plz test it
rhcp0112345 said:
Can someone who knows? Post a TUT to build the vision kernel? That's the only thing i am missing on my mac
Thanks if anyone does it.
Click to expand...
Click to collapse
I second this request.. I was able to compile for my G1 and ever since I got my G2 I have been unable to get it to work... It has to be something that I am doing wrong but I can't figure it out.
a TUT and thread for support would be great!
Sent from my HTC Vision using XDA Premium App
can someone confirm for me that to compile Gingerbread I need a 64 bit system?... I have compiled froyo from cm github and have had trouble ever since I tried gingerbread... and I read today that 2.3 requires a 64 bit system... Is this true or is it outdated info?
Thanks for your time.
Sent from my HTC Vision using XDA Premium App
TheNewGuy said:
can someone confirm for me that to compile Gingerbread I need a 64 bit system?... I have compiled froyo from cm github and have had trouble ever since I tried gingerbread... and I read today that 2.3 requires a 64 bit system... Is this true or is it outdated info?
Thanks for your time.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
theres a guide on how to compile gingerbread on a 32bit system. i dont have a bookmark bu search it on google, its a Chinese site if not mistaken.
Ok I think I may have found a similar site... I just wasn't sure who to believe... Thanks for your time.
Sent from my HTC Vision using XDA Premium App
why people make android froyo rom so much but why the dont make gingerbread?
I think maybe because the source code for froyo roms was already made for this phone but gingerbread has had to be modified to run on wildfire.
Sent from my HTC Wildfire using xda premium
I'm trying to create a barebones Rom but I have never had to mess with the internals much, I've already removed all the apps for the alpha test but I was hoping someone might be able to write a tut on this? Or point me in the right direction?
Thanks in advance.
Sent from my HTC Wildfire S A510e using XDA
What is a barebones ROM? I like the name.
Sent from my HTC Wildfire S A510e using XDA
It will be my Rom with a custom kernel but with nothing on it apart from the needed parts from which users will be able to customize to their liking rather than having loads of crapware, the idea came from tinycore Linux.
Sent from my HTC Wildfire S A510e using XDA
lynuxlover said:
It will be my Rom with a custom kernel but with nothing on it apart from the needed parts from which users will be able to customize to their liking rather than having loads of crapware, the idea came from tinycore Linux.
Sent from my HTC Wildfire S A510e using XDA
Click to expand...
Click to collapse
Cool, cause the most roms have to much build-in.
Sent from my HTC Wildfire S A510e using XDA
lynuxlover said:
I'm trying to create a barebones Rom but I have never had to mess with the internals much, I've already removed all the apps for the alpha test but I was hoping someone might be able to write a tut on this? Or point me in the right direction?
Thanks in advance.
Sent from my HTC Wildfire S A510e using XDA
Click to expand...
Click to collapse
Download my senseless rom and look inside the zip to see what i removed after alot of trial and error whats in the system/app folder is as barebones as it gets
jermzii said:
Download my senseless rom and look inside the zip to see what i removed after alot of trial and error whats in the system/app folder is as barebones as it gets
Click to expand...
Click to collapse
Ahh thanks jermzii did that now I have 150mb free space internal storage WooP!
Hello every one. I wanted to ask where a beginer with no understanding about making rom's from source cloud find information to understand the hole sourece thingy and start making rom's.
Sent from my GT-5660 using sparta kick.
Just go read nearly all the general stuff toppic is what i do when i have a new phone. Today i got a second gio that needs fixing and a update.. For fun i start with the general toppic. Than i progress the other thopic's. Put some time in it to understand stuff.
See if you can backup the phone system and root the phone. Next a new recovery and a new rom. The info is all in this part of the gio forum.
thanks but I wanted to ask about making rom's from source I already have root,cwm recovery and a custom rom. I just want to know what shoud I do to understad how to make rom's from sorce.But still thanks.
Sent from my GT-5660 using xda premium
arniks8 said:
thanks but I wanted to ask about making rom's from source I already have root,cwm recovery and a custom rom. I just want to know what shoud I do to understad how to make rom's from sorce.But still thanks.
Sent from my GT-5660 using xda premium
Click to expand...
Click to collapse
building a rom from source is simple
you only need to setup the source directorys and sync some stuff the let the automated compile progress hapen and done
everyone can do this
but modifying java and xml
c++ c etc
is mostly on source
if you take like stock rom and smali modify its gonna be bit harder because of no source
but alsomore fun
Sent from my S500 using xda app-developers app
thanks.
Sent from my GT-5660 using xda premium
hey guys,
I want to run kitkat roms like carbon,beanstalk etc on emulator.
I have downloaded zip of roms, but how do i run them in android emulator?
Any help will be great!!:good:
You can't do that. The Roms in the desire section are built specifically for the bravos hardware. In order to run an android build in the emulator you would have to compile the ROM specifically for the arm emulator
Sent from my HTC Desire using xda app-developers app
Just flash it on your desire and see what happens. Trial and error.
desdesu said:
Just flash it on your desire and see what happens. Trial and error.
Click to expand...
Click to collapse
U got no idea