Related
Anyone can put a brief discription and the tools to make your own cupcake rom? Any help will be appreciated. I want to learn to make my own roms as well. Thank you.
It isn't easy as you think.
You must edit the source code.
NiN39Z said:
Anyone can put a brief discription and the tools to make your own cupcake rom? Any help will be appreciated. I want to learn to make my own roms as well. Thank you.
Click to expand...
Click to collapse
are you talking about something like the PPC kitchen for windows mobile users?
if so, i was once a winmo guy. before android obviously. In my opinion if you are talking about something like the kitchen to point and click what apps you want your rom to have stock. i think it will be quite some time before we see something that in depth for two reasons.
1. It will require root. which not everyone feels comfortable doing.
2. The people who do have root and are flashing roms probably flash roms as soon as haykuro, the dude, or JF drops something. we cant even make up our minds about what rom we want yet lol.
In thought of the second reason it would be a great idea to have a "kitchen" type program for the PC that people can just point and click what rom they want the pc to push to the phone either by way of ADB or update.zip methods.
Plus on top of that... its not like there is anywhere near the amount of apps that winmo has to choose from just do do the same things.
again... in my opinion. it will be quite some time. Till then... (and more importantly back to your question) At the moment, the only way to build a rom is to compile it yourself. Check out all the reading you can do at www.android.com and get an idea of what you are getting into. Id love to see more people getting into development.
Yea i wanna compile my own rom actually. SO, I wanna get a breif discription and find the tools for it
www.android.com
happy reading.
I was thinking of getting a 2nd G1 as a 'test subject',,,, wouldent be a total waste of £165 quid, and then if gives me something real to develop on and troubleshoot on the fly
£165? Where'd you get that figure from???
And on the making your own cupcake ROM, you should follow the thread about compiling from the latest source for your phone, you'll learn a lot there and eventually get used to compiling your own aplications. Learn a bit of java and you'll be able to edit the source, get some custom apps working.
Thanks for ur input guys.. Im learning java development in college next semester so, ill be cooking up andriod roms after that for future devices
Easiest way to make your own rom atm with minimal technical knowledge is just taking a rom from JF, haykuro or thedude, unzipping them and adding/subtracting things that you want (adding a theme, removing or adding certain apps, adding tweaks, adding onscreen keyboards, etc). You then sign the file and put it on your phone.
Use this to sign the update (must have the SDK):
http://forum.xda-developers.com/showthread.php?t=473580
Hi guys,
Lately I have been developing a kitchen to help ordinary people learn how to build their own ROM on HTC-based Android devices. It allows you to do basic things such as rooting a shipped ROM, adding apps2sd, modifying the task killer memory threshold, etc.
Today I added some settings to make it work for the Droid Eris, but I am unable to test it, as I don't have an Eris.
Here is the link to the kitchen:
http://forum.xda-developers.com/showthread.php?t=633246
Please try it out if you can, and let me know if it works
Before flashing any ROM from the kitchen, please make a Nandroid backup first of your existing ROM!
Thank you, and enjoy!
I will cook a rom with your kitchen and test it on my Eris. Thank you for your work.
Will update with results.
UPDATE!
kitchen mostly works, the roms build and they flash onto the phone. had a few problems with setting task management, then tried option 14 and 15 with a few errors as well, so i just skipped that and just did a very basic rom build. so the core of the kitchen works and you can build roms, the issues i am having could be with my setup or it could be that DSIXDA was unable to test it before releasing, but for an untested kitchen it is FANTASTIC!
if this works does this mean we can overclock our phones..?
ashertheplague said:
if this works does this mean we can overclock our phones..?
Click to expand...
Click to collapse
what from the first two posts made you think this?
because i was reading that with this we can make a rom that doesnt belong on our phone and make it to where it can go on our phone. soo if we get a rom that can be over clocked will that work
Thank you!! Of course I am damned by the leak but I feel a root coming on and this will really come in handy...
ashertheplague said:
because i was reading that with this we can make a rom that doesnt belong on our phone and make it to where it can go on our phone. soo if we get a rom that can be over clocked will that work
Click to expand...
Click to collapse
I don't believe you would be able to make a ROM that have the capabilities to OC. With all these current ROMS that have been made by competent cooks, yet none of them OC. But hey, you might be able to and prove me wrong. Which I do hope you can. But I have read from a few forums that OC is not that possible.
We don't have the source for 2.1 for our phone. When we do then OC'ing will be possible. That won't be released until hopefully with or shortly after official 2.1 OTA is released from Verizon.
Thanks!
Probably won't be cooking as much as fiddling with ROMs to suit my own ideals of them, but this seems like it might open the doors to a lot more people.
Just tried porting the DarchDroid ROM:
http://forum.xda-developers.com/showpost.php?p=5663463
From the base of this:
eris21official-root.zip: http://www.multiupload.com/YP1BIUOF60
Everything was successful and I got a signed ROM, but it wouldn't boot. Just got stuck on splash. Tried doing logcat too but nothing showed up.
alexhendershott said:
Just tried porting the DarchDroid ROM:
http://forum.xda-developers.com/showpost.php?p=5663463
From the base of this:
eris21official-root.zip: http://www.multiupload.com/YP1BIUOF60
Everything was successful and I got a signed ROM, but it wouldn't boot. Just got stuck on splash. Tried doing logcat too but nothing showed up.
Click to expand...
Click to collapse
Please make sure you can flash an actual Eris ROM before you start work on porting roms from other devices. Let me know how that works out.
dsixda said:
Please make sure you can flash an actual Eris ROM before you start work on porting roms from other devices. Let me know how that works out.
Click to expand...
Click to collapse
I actually tried one of your kitchens yesterday, i'm guessing it didn't have eris support then But this is the problem i had It wouldn't boot It was just stuck on the three android skateboard screen wouldn't even go thru the bootanimation. so I can back up his story on this.
t2noob said:
I actually tried one of your kitchens yesterday, i'm guessing it didn't have eris support then But this is the problem i had It wouldn't boot It was just stuck on the three android skateboard screen wouldn't even go thru the bootanimation. so I can back up his story on this.
Click to expand...
Click to collapse
Yesterday there wasn't any Droid Eris support, that's why it wasn't working yesterday. I had to modify the kernel build command a bit for the Eris. Actually, now that I think about it, the code from yesterday should still work, as it correctly figured out the kernel's base address.
I'll dig into it a bit more...
quick quesion, what are the main differences between hero and eris roms?
Sent from my Eris using the XDA mobile application powered by Tapatalk
So where Can I get a stock eris rom since you advise against using nandroid backup???
fKngFtd said:
quick quesion, what are the main differences between hero and eris roms?
Sent from my Eris using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Basically the kernel's physical base address and the WiFi module. There are a few minor things as well. I did not port an Eris ROM myself when I had the Hero, but this is what people have told me.
CaptainJager said:
So where Can I get a stock eris rom since you advise against using nandroid backup???
Click to expand...
Click to collapse
you can get the rom in the very first post of this section. im surprised you missed it.
http://forum.xda-developers.com/showthread.php?t=649705
dsixda, when i tried to follow your setup guide for your kitchen, i noticed that you didnt have any links for x64 based linux setups. i tried to find the java bin and jre install files but linux is new to me and i dont think i grabbed the right ones. would you be able to point me to the right links for those on ubuntu 9.10 x64?
thanks!
Have you tried obtaining the Java package with the sudo command? Unfortunately I have not tried the 64 bit method, nor have I been asked about it before. If you find a way please let us know.
If you guys are still having problems with the cooked ROM not booting, then I'll ask some of the experienced Eris cooks around here for help.
ECLIPS3 said:
you can get the rom in the very first post of this section. im surprised you missed it.
http://forum.xda-developers.com/showthread.php?t=649705
dsixda, when i tried to follow your setup guide for your kitchen, i noticed that you didnt have any links for x64 based linux setups. i tried to find the java bin and jre install files but linux is new to me and i dont think i grabbed the right ones. would you be able to point me to the right links for those on ubuntu 9.10 x64?
thanks!
Click to expand...
Click to collapse
dsixda said:
Have you tried obtaining the Java package with the sudo command? Unfortunately I have not tried the 64 bit method, nor have I been asked about it before. If you find a way please let us know.
If you guys are still having problems with the cooked ROM not booting, then I'll ask some of the experienced Eris cooks around here for help.
Click to expand...
Click to collapse
I will try cooking a new ROM right now. No porting or anything, just a cooked ROM from the original 2.1 root with some apps removed so I know it is different.
Updating in a few...
I'm working on a ROM right now using your kitchen. I just recently came across your kitchen while searching the forums. I am using version v0.38 and I'm assuming eris support is on v0.39, correct? Should I just extract the the files into the same directory that I have been using for v0.38?
I'll let you know when I sign and try to flash if it works. Thanks for taking the time to do this.
Ok, I'm loving Gingerbread, but m-deejay has been including Cyanogenmod in his recent builds, which I don't want.
I'm REALLY keen to work on my own Gingerbread build...but need pointers on the steps I need to take.
I want to use a clean custom Nexus One Gingerbread build, such as http://forum.xda-developers.com/showthread.php?t=885784
Then I'll have to replace the Nexus drivers and stuff with the HD2 ones...this is where the problem starts...how do I know which files are needed for HD2 specifically?
And then I need to add/remove apps etc to customise it?
I don't want anyone to hold my hand, just to at least point me in the right direction, as finding this information seems to be very difficult, unlike Windows Mobile cooking, which has lots of good tutorials...even though I'd expect that to be the other way around
I taught myself WM cooking & dev, but this is a whole new ballgame to me....
Appreciate any help I can get...
I'll happily donate a few $ to anyone who can help me get a stock build going...
No one able to shed ANY light? Give me ANY pointers?
Like I said, I'm willing to donate $ if I get help to get a ROM built...
Good pointers!!!
Have you tried with this tutorial?
SEE THIS!!!
This is the best step by step guide, and there is everything you need to port/make good working ROM for LEO.
Regards.
NemanjaLO said:
Have you tried with this tutorial?
SEE THIS!!!
This is the best step by step guide, and there is everything you need to port/make good working ROM for LEO.
Regards.
Click to expand...
Click to collapse
Yea I saw that, thanks...only problem is that it's an old build, and it's miui.
Where do I find the latest drivers etc? And how is a NAND build different? How do I package up a NAND ROM?
I was thinking the very same thing but when I started looking into it I got put off by the complexity and the time it would take.
Have you thought about just modding MDj's ROM, stripping it back to bare ginger and replacing the bits we dont want, this might be easier that building one from scratch.
Yea, it's a possibility...but I won't learn as much doing it that way...and I'd rather try to create my own than use someone else's hard work as a base, if you know what I mean.
I have time, and am willing to learn as much as I need to...I just need some pointers...there are plenty Android HD2 chefs now, surely one of them is willing to help out
It's really not that difficult. I didn't really like the CM mod either, so created my own stock rom. I'm now at the point where I got it all working. I don't mind to give you a helping hand if you really are interested.
I'd love to see this too!
SamanthaMarquez said:
It's really not that difficult. I didn't really like the CM mod either, so created my own stock rom. I'm now at the point where I got it all working. I don't mind to give you a helping hand if you really are interested.
Click to expand...
Click to collapse
Hey,
yes I've VERY interested...I'm hoping to get a stock-ish one together with my own little touches...maybe release one if I learn enough about it.
Any help you can give would be much appreciated...
Even to start with, a list of the basics...ie get ROM dump, extract xyz, do this...anything at all...
I just got back from a swim at the beach to relax, intending to come back and try to figure it out on my own with what help I can get from that page linked above...but if you have managed to get one together, thats even better
This might be of some use for windows users (I've successfully tried extracting MDJ's Gingerbread system.img with it).
http://android.modaco.com/content/z...-boot-recovery-system-userdata-kitchen-ready/
yea extracting is easy...but I would prefer to use a clean build to start from, rather than m-deejays...trying it using the guide in the link above with the Nexus S dump...having to use some donor files from m-deejays build though...still trying to get my head around it all
Well I gave it a quick try using the above guide, and it gives "NAND Kernel Open Fail".
I used m-deejays kernel, and put all the relevant files into the correct directories before making the system.img, and i put initrd.gz and zimage into boot.img, so I dont know what I did wrong...?
You don't use system.img on nand. You need to create a yaffs.img. Which I've never done before. I've only made builds the sd way, not nand. Maybe all you have to do is rename the .img after you create it. You should jump on irc, room #htc-linux-chat. You would get your answer in like 5 secs;p
NAND ROMs do use system.img, have a look in any NAND ROM, you'll see system.img, boot.img and the flash files.
Yaffs is the filesystem...I created the img files with the "mkyaffs2image" command.
(As per this thread: http://forum.xda-developers.com/showthread.php?t=897940)
I've made all of these but get the damn kernel error...it can't be difficult, lots of devs have released ROMS...surely someone is willing to help?
I'd rather not go into irc, as thats the dev channel isnt it? Dont want to be a noob popping in asking hwo to cook Android for the HD2
i think what would be a cracking idea is if someone were to create 3 "standard" kitchens for anyone to download and start modding with.
kitchen 1) desire / desire HD with NO mods
kitchen 2) Froyo / gingerbread with NO mods
kitchen 3) Froyo / gingerbread with Cyanogen included
they should just be 100% stock but able to build a fully working rom. This way everyone can start to learn, and its always easier with a complete kitchen and just as educational - moreso as you get to see the correct layout for files / directories and all the correct tooling is already in place.
I will add to davids "donation" pot if someone were to make these available, whatever david is willing to donate and i will add another $20 (US) or £15
Whether they be Windows or Linux based kitchen does not matter to me, but i believe that android being open source these resources should be made available
G
Your right, not thinking clearly from all the jack daniels. You do need yaffs tools to mess around with the system.img though...#htc-linux is the dev channel. #htc-linux-chat is where you go to ask questions. Devs don't even go in that channel. Just chefs fire the most part. That's where everyone goes to learn how to build.
g.lewarne said:
i think what would be a cracking idea is if someone were to create 3 "standard" kitchens for anyone to download and start modding with.
kitchen 1) desire / desire HD with NO mods
kitchen 2) Froyo / gingerbread with NO mods
kitchen 3) Froyo / gingerbread with Cyanogen included
they should just be 100% stock but able to build a fully working rom. This way everyone can start to learn, and its always easier with a complete kitchen and just as educational - moreso as you get to see the correct layout for files / directories and all the correct tooling is already in place.
I will add to davids "donation" pot if someone were to make these available, whatever david is willing to donate and i will add another $20 (US) or £15
Whether they be Windows or Linux based kitchen does not matter to me, but i believe that android being open source these resources should be made available
G
Click to expand...
Click to collapse
Yea, something like that would be handy...but even to start with, I'd just love to know the basic processes needed to get a basic Android build running on the HD2, without having to rely on someone elses current build.
I tried the link above, and it did sort of help understand a little of whats going on...but this stupid kernel error is preventing me from knowing how my test build works/or doesnt work...
I mean I had too use m-deejays gingerbread dump to get some of the driver files etc from...but where does he get them from? Thats the stuff I dont know...
It's obviously not overly difficult as there are so many devs pumping out HD2 ROMs...would just love one of them to share the secrets
Cash - not sure ... depends on how much help I get, but I'm willing to donate along the lines of US$20 or so...
mattfmartin said:
Your right, not thinking clearly from all the jack daniels. You do need yaffs tools to mess around with the system.img though...#htc-linux is the dev channel. #htc-linux-chat is where you go to ask questions. Devs don't even go in that channel. Just chefs fire the most part. That's where everyone goes to learn how to build.
Click to expand...
Click to collapse
hehe...
What server is that chat room on?
the_scotsman said:
NAND ROMs do use system.img, have a look in any NAND ROM, you'll see system.img, boot.img and the flash files.
Yaffs is the filesystem...I created the img files with the "mkyaffs2image" command.
(As per this thread: http://forum.xda-developers.com/showthread.php?t=897940)
I've made all of these but get the damn kernel error...it can't be difficult, lots of devs have released ROMS...surely someone is willing to help?
I'd rather not go into irc, as thats the dev channel isnt it? Dont want to be a noob popping in asking hwo to cook Android for the HD2
Click to expand...
Click to collapse
Is it possible that the img files need to be created as ext4 rather than yaffs? I know gingerbread runs on the ext4 system (where froyo ran on yaffs2) but I'm not sure how this relates to building the rom.
Nah, don't think so...not accroding to: http://forum.xda-developers.com/showthread.php?t=897940
Ive tried a few more times but am still getting the kernel error...so I cant even test if my build works or not as it wont even boot...so very frustrating...
Lets break it down........
1st
Here's a brief intro I did a few days ago read it..
http://forum.xda-developers.com/showthread.php?t=897940&page=2
The above goes for any .img used with DAF, they are yaffs2 images.
2nd
The sensible option for a clean build would be an existing stock gingerbread rom on a sister device. AdamG just happens to make the cleanest Desire roms around. I've had my eyes on this build for a minute, check it out and see if this what your looking for. Oxygen v2.0-RC6
3rd
I've been able to unyaffs disect, reassemble and get some 'customized' roms running. They flash, boot, & work great.....but I lose root permissions. lol
I was acutally doing this with the 1.6 NAND rom of MDJ that came as a single.img
That particular file was just system.img & boot.img yaffs2'd together. After I disected it I was able to unyaffs the 2 images and edit/modify change kernels, etc. etc. The only problem I have run into is the root issue.
Conclusion:
----------------------------------------------------------------------------
I'd be glad to help out any way I can in porting a ROM worthy of our devce
Any serious inquries can be directed to my inbox for private discussion on gtalk .
I'm no dev and am in no way claiming to be. I do have some findings and that's why I'm offering my help. Cheers
Hey been looking around through xda for a bit but couldnt find anything.
Im after a guide on how to start making my own ROM.
If anyone could post a link to a guide or let me know the important steps on how to start.
Had a U8800 for a bit and love it and want to make it perfect
Cheers
first you have to understand some programming language , specifically c or java, but most high level languages are similar
then I am told that you need to have a deep understanding of linux file system, which I don't... so I am not qualified to give you anymore advice...
For me I started out trying to port clockwork recovery to u8800. There's a guide by koush that gives the most basic steps on how to do this. Following that and doing a lot of reading I was able to get it pretty good and obviously Geno has since taken over to basically perfect it.
I think the recovery is a good place to start since it's similar to the normal android os but just really cut down. Try building it from source and work out how to get it on the phone and booted.
As well as Stockwell's very useful suggestion (do you have a link to the specific koush guide that you found useful, Stockwell?), you might want to go to XDA's Chef Central, and cyanogen's advice at :-
http://forum.xda-developers.com/showthread.php?t=667298
below are the links to "further reading" that I've extracted from that post.
Android Developer Guides: http://d.android.com
Working with AOSP source: http://source.android.com
Platform Developer Guide: http://pdk.android.com
Android Gitweb: http://android.git.kernel.org
Git Ready (Git tips and tricks): http://www.gitready.com/
Building CyanogenMod: http://wiki.cyanogenmod.com/index.ph...ng_from_source
How Dexopt works and what are those odex files: http://android.git.kernel.org/?p=pla...5936;hb=master
stockwell said:
For me I started out trying to port clockwork recovery to u8800. There's a guide by koush that gives the most basic steps on how to do this. Following that and doing a lot of reading I was able to get it pretty good and obviously Geno has since taken over to basically perfect it.
I think the recovery is a good place to start since it's similar to the normal android os but just really cut down. Try building it from source and work out how to get it on the phone and booted.
Click to expand...
Click to collapse
Would you please give the link to koush's guide?
Here's the guide by koush:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
I think it's missing some stuff though. At the very least it looks like you would need to do
. build/envsetup.sh before running lunch. I think there was another problem but I can't remember what it was now.
Thanks everyone for the info.
I am studying IT at the moment and am about to learn java so sort of wanted something to have a go at while learning
Everyone is allowed to make changes to the VMWare image and re-upload it. If you re-upload the VMWare image with the made corrections, post the download link(s) in this thread. I will update the first post.
If there is a AOSP Developer that is willing to make a complete tutorial, please make one that works and is up-to-date with 2.3.7
The more people we have working on making ROMs, the better.
This VMWare image is:
- Base: Ubuntu 10.04 LTS
- ICS ready
- Gingerbread ready
- Fully updated
- Eclipse with ADT Plugin
- Android Kitchen Integrated
PASSWORD: root
Latest changelog (Coming soon)
- Based on 10.04 LTS instead of 11.10
- Different approach
Download link:
Bypass 24h wait time, limit reached --> Solution? Reset your ip! In Belgium this is easy by restarting your modem/router. This may be different in other countries.
more mirrors will come!
Part 1
Part 2
Part 3
Image is extracted, where do I start?
Continue from this link
How to build 2.3.7 for Nexus S
This is just a snippet that may help you.
repo init -b android-2.3.7_r1 < /dev/null (This branch is ready to use with Nexus S and Nexus S 4G)
repo sync
source build/envsetup.sh
lunch full_crespo-userdebug
make -j8 (-j8 = for eightcores like 2600k, 2630QM / -j4 = for quads 2500K/2620M/Q6600 / -j2 for dual cores / ...)
Click to expand...
Click to collapse
Don't forget to add the vendor files of the device. You need to download the scripts as well of the driver binaries.
Click to expand...
Click to collapse
I tested a quick build. And it's working.
A virtual machine with limited RAM in order to compile AOSP? Definitively not a good idea. Why not dual boot? Sooooo easy to install the worst distro ever (*buntu).
This is awesome. My only problem is that I only have VMWare Workstation 7.
Super! Waiting for this
djjonastybe said:
Dear community,
I made a AOSP developer environment for VMWare Workstation 8 or latest VMWare Player (free).
You can use this VMWare image as a base to build AOSP ROMs. Imade it for those having trouble getting it to work or maybe if you don't have time to set it up properly. Well if you are downloading this you might have a good reason!
Anyway have fun!
If there are any errors let me know.
This VMWare image is:
- ICS ready
- Gingerbread ready
- Fully updated
Download link:
...uploading...
Click to expand...
Click to collapse
Who would have guessed that an android dev would have difficulty setting up a linux enviroment . . . go figure.
You do not have to be an Android Dev to compile Android. I haven't written a single line of code for Android and can compile AOSP 2.3.7 fine.
This is simply to save time. And if you have good enough hardware (like myself) compiling Android AOSP in a VM session works perfectly fine.
Most people that are into computers have a rocking system. I have 12GB ram, I dedicate 8 for my VM and the rest for my main OS (windows 7). Works fine, what's the issue?
Some people don't want to dual boot and sometimes a Linux distro doesn't support certain hardware or can't be installed.
I would appreciate it. THANKS
nice.....this could be very useful
Sent from my Nexus S using xda premium
FeaRThiS: Who would have guessed that an android dev would have difficulty setting up a linux enviroment . . . go figure.
Click to expand...
Click to collapse
You seem to be the only one against uploading this.
Guys I am still trying to upload it. I am splitting it in 700MB sizes. Crocko's uploadservice is down. I will upload it on depositfiles and multiupload
12,5%
@FeaRThiS just stated the obvious. I also think the first step to understand how to build an AOSP ROM is knowing how to setup the development environment.
I don't have anything against using a VMWare image. But, IMHO, considering the time for uploading/downloading the file, if you do the setup yourself (in VMWare or whatever), you should have already been compiling your ROM by now.
suksit said:
@FeaRThiS just stated the obvious. I also think the first step to understand how to build an AOSP ROM is knowing how to setup the development environment.
I don't have anything against using a VMWare image. But, IMHO, considering the time for uploading/downloading the file, if you do the setup yourself (in VMWare or whatever), you should have already been compiling your ROM by now.
Click to expand...
Click to collapse
Okay, its not useful for you two.
Next!
I like it and i will try it.
djjonastybe said:
You seem to be the only one against uploading this.
Guys I am still trying to upload it. I am splitting it in 700MB sizes. Crocko's uploadservice is down. I will upload it on depositfiles and multiupload
12,5%
Click to expand...
Click to collapse
I have nothing against it and it may even be useful in case of emergency when you can not access a linux machine, but as stated by @S suxeN the first step for any dev would be learning to create their own dev enviroment.
i didnt say that.
but the statement is right. Anyways i yet think this image is of great use, as you can always start from there, if u did something wront, what can always happen to nun-linux users.
I don't know anything about linux. Is Eclipse with ADT on here by any chance? If not, what IDE is there to develop with in this VM?
I didn't think that far. Eclipse is not installed.
But I will work on it for next release. For now you have to install it manually. I hope tomorrow evening the new vmware will be uploaded!
Hey guys, don't be so hard on the fella. He's doing us a great service in a way. Not all of us are able to bring laptops wherever we go, dual-boot, etc. I just downloaded this to my external drive that I use to keep my stuff on for work and it'll come in handy when I wanna test apps without worrying about nuking my phone.
Also, it helps that I can demo apps on the thing to co-workers on screen than using a phone. That way I won't have to worry about them screwing things up if they decided to 'explore.'
http://code.google.com/android/nexus/drivers.html#crespogwk74
Can someone help me with this? This has the binaries for the Nexus S.
Where do I place the scripts?
I have a vendor folder with several maps in it now. But I don't know what I have to do now.
I placed the 'vendor' folder in my working directory. But lunch isn't showing up crespo in the list.
These are my steps:
Building
I executed lunch. I realised I did not have crespo in the list. So next, I read the line 'Building for devices'.
Eventually I ended up here:
Building devices
Obtaining proprietary binaries
Starting with IceCreamSandwich, the Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for Nexus S, Nexus S 4G, Galaxy Nexus, and PandaBoard can be downloaded fromGoogle's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
There are no official binaries for Nexus One, ADP2 or ADP1., ADP2 or ADP1.
Click to expand...
Click to collapse
I clicked the link and downloaded the GWK74 binaries.
Now then I read further:
Extracting the proprietary binaries
Each set of binaries comes as a self-extracting script in a compressed archive. After uncompressing each archive, run the included self-extracting script from the root of the source tree, confirm that you agree to the terms of the enclosed license agreement, and the binaries and their matching makefiles will get installed in the vendor/ hierarchy of the source tree.
Click to expand...
Click to collapse
I have the vendor hierarchy...
Do I have to put these files in:
my home folder/bin
OR
home folder/workingdirectory_name
Or what do I have to do now?
updated first post with small hint on how to download 2.3.7 for our Nexus S. Good luck!
yep, i think this is pretty awesome. for me, i'm not an android dev but i've dabbled with theming and porting mods from other phones to the epic 4G previously. i'd love to be able to start with a system ready to go and mess around with some guides to learn how to compile source, etc... thanks.
Nice image man, gonna give it a go later. Thought I'd put my word in the discussion , sure there lots of talented devs, but they have all got different hardware/software and time requirements. So this becomes a useful tool to add to the inventory.