Develop Bugs

Porting Roms from *** To the Evo

I assume this is the correct forum otherwise please move this.
What is the best article(s) to read if you want to start learning how to port roms from other android phones to the Evo? I've been searching on here and on google and it seems most articles are either outdated or only talk about editing existing cooked roms so I finally broke down and posted this. Yes I do use Linux and I do program in Java and .NET and do have a bachelors in software development but I have just never looked into doing this type of work until now.
Thank you, any direction I'm pointed in is appreciated.

I'll direct to you the Q&A forum.

Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)

sirmx said:
I'll direct to you the Q&A forum.
Click to expand...
Click to collapse
Thanks sirmx, I did do a search there but again came up short.

ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Sounds good, what I'll do is go ahead and start one, nothing special maybe even ones that already been done just to get the experience under my best.

ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk

Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is if friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.

What about something A LOT simpler like adding the CRT animations to a ROM? any pointers? Any TUT you can point me to?

ThatSmartB0y said:
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
Click to expand...
Click to collapse
Oh I hear ya. Just throwing in my 2 cents. Found that having a clean updater-script is half the battle.
Sent from my PC36100 using Tapatalk

I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App

Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.

evomattnc said:
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well said. People love to flame anyways and XDA is famous among other Android forums for being so harsh. This thread helped me out big time, and it's especially nice to see Leoisright and myn in here giving up a few pointers, because I too was curious about porting. I never worked up the confidence to ask, just too worried about it being passed over or getting flamed because I'm young and curious.
Sent from my PC36100 using XDA App

Yah, Q&A never got me anywhere, i learned off of trial and error, still learning now.
EDIT:OP:IF you want you can ombine mine and leo's tuts together, to make this thread permanent.

Subscribed!!!!!!!!
Good stuff!
Sent from my PC36100 using Tapatalk

Yeah I want to thank the devs that have stopped by so far and gave tips, already using them . Hopefully most of them drop In at least once and leave one tid bit that would make this thread awesome!
Sent from my PC36100 using XDA App

Ha, you taking applications for an apprentice myn?
myn said:
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

Yes I was afraid to post this at first which isn't good, you shouldn't be afraid to ask questions but I get that sometimes the same questions have been answered 100 times prior so I understand the quick to judge portion of it. But I want to thank everyone who has contributed tips, advise and places to start. Thank you.

Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
So I've been looking at beyond compare, did you use this from everything and just edit all the non evo files to match existing evo ones from within windows?

[q] just wondering if possible to port .sense to mt3gs

HELLO EVERY BODY I was just wondering if it is possible to do a port of benjamingwynn's super awsome .sense rom to the mytouch 3g slide?
It's just a really great rom that might just bring the mt3gs back for one last time.
Just don't want to give up on this phone, I love it to much.

well, i might, but, im more focused on getting WiFi to work in ANY sense 3.5 rom

Well that is important and I thank you for working on it! I
I just wanted to know so I can give porting a rom a try. Want to contribute something instead of just using.
Oh by the love your roms
Sent from my SGH-I897

can anyone give me any suggestions to get me in the right direction so I can learn how to port roms

mon5trum said:
can anyone give me any suggestions to get me in the right direction so I can learn how to port roms
Click to expand...
Click to collapse
well, start by setting up either a linux partition, or install cygwin (you need the custom one in the dsixda kitchen thread) and setting up your kitchen, but for the most par, just make sure you are trying to port a non-sense rom with a sense base, or vise-versa
Also, always replace /system/usr and /system/bin/akmd
but you will figure out what else on your own

Whoareyou said:
well, start by setting up either a linux partition, or install cygwin (you need the custom one in the dsixda kitchen thread) and setting up your kitchen, but for the most par, just make sure you are trying to port a non-sense rom with a sense base, or vise-versa
Also, always replace /system/usr and /system/bin/akmd
but you will figure out what else on your own
Click to expand...
Click to collapse
Thank you very much for taking some time to help out a total NOOB!
Whoareyou you are great!
Sent from my Wildfire S

Dont know if this will help or not. You may or may not be aware of it. I checked out the thread a little, http://forum.xda-developers.com/showthread.php?t=1445517 and development has been suspended. Apparently there were some problems with wifi and cell service on the latest version 3.0 from the little bit I read there. I did notice a few people saying that v2.0.1 was working pretty good for them though.
It also appears that they had it working for the Legend in v2.0.1 so that could be the easiest port if you do decide to tackle it. (The Legend is nearly identical to our Espresso if I am remembering correctly)
v3.0 was available for the Wildfire and the Salsa, and since we have a working port of Salsa, that may help as well (for either the 3.0 or 2.0.1).
Sorry I can't be much more help than this right now. Hopefully this can help give you some ideas.
Note: the download links do not work at all, but i did find them all here.
http://goo.im/devs/benjamingwynn/dotsense/
Good Luck to you!

DocHoliday77 said:
Dont know if this will help or not. You may or may not be aware of it. I checked out the thread a little, http://forum.xda-developers.com/showthread.php?t=1445517 and development has been suspended. Apparently there were some problems with wifi and cell service on the latest version 3.0 from the little bit I read there. I did notice a few people saying that v2.0.1 was working pretty good for them though.
It also appears that they had it working for the Legend in v2.0.1 so that could be the easiest port if you do decide to tackle it. (The Legend is nearly identical to our Espresso if I am remembering correctly)
v3.0 was available for the Wildfire and the Salsa, and since we have a working port of Salsa, that may help as well (for either the 3.0 or 2.0.1).
Sorry I can't be much more help than this right now. Hopefully this can help give you some ideas.
Note: the download links do not work at all, but i did find them all here.
http://goo.im/devs/benjamingwynn/dotsense/
Good Luck to you!
Click to expand...
Click to collapse
Thank you for your support and advice.
That is a very good starting point. Once the weekend gets here I will try to get started.
One more question what are the minimum requirements for a PC, I have 4 gigs of ram two hard drives one with 250 gb the other with 1 tb and a pentium core duo processor I think. (Not sure on the processor, been a while since I looked)
Sent from my Wildfire S

I would say that should be plenty. I have not yet attempted compiling or porting myself but i use a much weaker machine for a lot of my android stuff and it has been pretty good for the mods and such ive been working on. Search google or xda for android development min requirements and you should find some info on recommended specs for what u want to do.
Sent from my Little Engine That Could using XDA App

one more thing I tried to plug my mt3gs to my pc but neither my wife's laptop or my desktop wont recognize my phone neither htc sync or as a mass storage device, as I am going to start my little project on saturday. So just want to know if there is a solution for this? Can someone please help me your help is very very appreciated.

Have u tried a different cable? Does the phone start charging when u plug it into the PC? if u just want to transfer files u can try an app like SwiFTP from the market. I believe there are also ways to run adb over wifi, but ive never looked into it so not totally sure bout that. Did u check to make sure in settings that its not set to Charge Only?
Sent from my Little Engine That Could using XDA App

DocHoliday77 said:
Have u tried a different cable? Does the phone start charging when u plug it into the PC? if u just want to transfer files u can try an app like SwiFTP from the market. I believe there are also ways to run adb over wifi, but ive never looked into it so not totally sure bout that. Did u check to make sure in settings that its not set to Charge Only?
Sent from my Little Engine That Could using XDA App
Click to expand...
Click to collapse
This all started to happen with the original cord that came with the phone but I will try different cords just too see if I can get it to work. And if not I will look in to that adb through wifi thing, but most likely if a different cord works I will still research that whole process. I thank you for your help and advice. :thumbup:
Sent from my all powerful ANDROID phone!!

Hello again everyone, Sorry that I haven't posted any news or anything but my life just got a little crazy and it cut down my free time considerably. I was just wondering if I was to late to start this project and someone else started with it, or am I still good with it...
Thanks for any responses!!!
Sincerely
The mon5trum under your bed

[HELP] Creating custom ROM

Hello everyone,
I've been on these forums for some time already, and have avidly watched the development of new ROMs and apps. But always only as a user.
I have now become interested in developing my own ROMs for the Xperia Play, and I would like to ask you some questions:
1) What programs and utilities exist for developing custom ROMs, and which one would you suggest for a beginner?
2) I myself have an r800i, but I would like my ROMs to work on the other models too, how difficult is that to do?
Thanks in advance,
Si1ver Shad0w

No idea how to do it myself but look here:
http://forum.xda-developers.com/showthread.php?t=1801690
Sent from my R800i using xda app-developers app

Its not that easy as creating your own bootlogo.
1. Make the name
2. The features mustnt be same, implent something different, something cool and useful, because if you make something that was already released like 2times, people doesnt care..
3. Use Android SDK
However you will need Ubuntu, but you need a knowledge how to do it. You cant just say from day one to day two "Hey i want to be famous! I make the best ROM!".. If you are stuck at this point and you arent modder or hacker, i woudnt recommend it doing.
Click "Thanks" if useful.
Sent from my R800i using xda app-developers app

wuby said:
Its not that easy as creating your own bootlogo.
1. Make the name
2. The features mustnt be same, implent something different, something cool and useful, because if you make something that was already released like 2times, people doesnt care..
3. Use Android SDK
However you will need Ubuntu, but you need a knowledge how to do it. You cant just say from day one to day two "Hey i want to be famous! I make the best ROM!".. If you are stuck at this point and you arent modder or hacker, i woudnt recommend it doing.
Click "Thanks" if useful.
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
For the moment I won't be releasing anything, just want to tinker by myself and if it works out then maybe share it with the community.
I'm currently wanting to just modify the stock 2.3.4 ROM, so I don't think I will be needing the Android SDK. But apparently Android Kitchen needs a Unix environment to work, so I'm now downloading the latest Ubuntu and gonna put that on a virtual machine. =)

Also, I was wondering, I have seen some custom ROMs that can be installed even with a locked bootloader, how exactly is that done?

Developers Support Thread

Developers Support Thread
What does that mean?​
Quite literally, this thread is intended to support developers. I intend to help out anyone who needs a hand in an attempt to develop for the Galaxy Nexus, or any other phone but I'm going to reference my website with step by step instructions to get you through the beginning stages and comfortable with development. This will also cut down on the number of "noob questions".
Background:
My private messages and e-mail stay filled with usually the same questions. There are lots of people who have android phones and the excitement of owning them doesn't stop there. They want to learn how these other people are creating custom roms on their phone. Some people want a minimalism rom, pure AOSP with maybe one or two mods, such as reboot and status bar toggles, but otherwise want a stock setup. They browse around all these great roms but they are just too many mods for their taste. What do you do from there? You can request a developer release a version with only those two mods, and then wait for the end of time because it's not coming. Or you can compile your own rom from source code and have whatever mods you choose.
Rules:
1) No trolling. If someone appears to be a troll and everyone agrees they are a troll, leave it at that. NOT responding to a troll is the only way to defeat them so practice that rampid in this thread.
2) Anyone who knows an answer to a question posted, feel free to join in, the entire community including current developers should participate. This will only serve to strengthen the development community.
3) No question is too small. Everyone starts somewhere so if someone post asking what a terminal is, or how to find usb debugging in settings, do not discourage them from continuing to learn. There is no place for that and you will have become a troll. You will know it too because everyone will ignore your comments .
Get your start here:
http://source.android.com/source/initializing.html
This is google's own instruction but it's hard for some people just starting off to feel comfortable with. I have elaborated on this guide with an entire website aimed at educating people. Please visit here: http://www.dreamsforgotten.net Understand the site is very new, I have been working on it for a month or so, but it will grow and evolve as does this thread. Any questions that get tackled here that are repeated, and seem to affect many people, I will add the resolution to the website as well.
I do have ad sense on the website in an attempt to cover the hosting fees, there is no option to set up an account @ dreamsforgotten.net. Anyone is free to stop by and view it, and take from it what they need. So far I have enough instruction in place to get anyone who is using a supported development device (as well as sprint and verizon galaxy nexi lol) compiling from source rather quickly.
Please leave me feedback on what you would like to see addressed in the future, and consider this the support thread. Dreamsforgotten.net is for you to get a step by step instruction on setting up an environment, this thread is for you to expand that and get assistance when you hit a snag in the road. Thanks guys and I'll be responding to questions as I get time. Enjoy.

Okay im planning on Porting Rasbean Jelly to the Toroplus variant as Dreams and others from the Black Bean thread know. Just some questions.. Ubuntu 12.10 was just released and that is what i am planning on installing since it now supports my laptop. Will that be sufficient? I remember hearing some issues with compiling on it. Also how much space should i dedicate to the install? I planned on dedicating around 250GB but all im doing is syncing Rascarlo's git with his permission of course and then adding the necesseties for the toroplus (if thats even what im needing to do). And compiling? Do i honestly need that much space? Also will i need Swap to help my Laptop build? It has 6GB's of RAM and i hear the Minimum for building is around 16GB's otherwise it will take quite a while. Any insight would be great

ÜBER™ said:
Okay im planning on Porting Rasbean Jelly to the Toroplus variant as Dreams and others from the Black Bean thread know. Just some questions.. Ubuntu 12.10 was just released and that is what i am planning on installing since it now supports my laptop. Will that be sufficient? I remember hearing some issues with compiling on it. Also how much space should i dedicate to the install? I planned on dedicating around 250GB but all im doing is syncing Rascarlo's git with his permission of course and then adding the necesseties for the toroplus (if thats even what im needing to do). And compiling? Do i honestly need that much space? Also will i need Swap to help my Laptop build? It has 6GB's of RAM and i hear the Minimum for building is around 16GB's otherwise it will take quite a while. Any insight would be great
Click to expand...
Click to collapse
I already spoke with you but i recommend two hundred gigs really two fifty minimum hdd. I roll with 8 gigs but compile time is horrendous since jelly bean. I'm sure almost all distributions can be set up to develop debian arch mint ubuntu etc but each have to be done so desperately. I'll work on write ups for each java 6 being the biggest hurdle for most new developers.
Sent from my Galaxy Nexus using Tapatalk 2

dreamsforgotten said:
I already spoke with you but i recommend two hundred gigs really two fifty minimum hdd. I roll with 8 gigs but compile time is horrendous since jelly bean. I'm sure almost all distributions can be set up to develop debian arch mint ubuntu etc but each have to be done so desperately. I'll work on write ups for each java 6 being the biggest hurdle for most new developers.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
How long do you think it'll take? Using 6GB of RAM. And I have a quad core amd at 2.0ghz?
Sent From My N7 via Tapatalk

ÜBER™ said:
How long do you think it'll take? Using 6GB of RAM. And I have a quad core amd at 2.0ghz?
Sent From My N7 via Tapatalk
Click to expand...
Click to collapse
8 gig 1.2 gig quad core 8 hours. Use ccache when you build I would go 50 gigs
Sent from my Galaxy Nexus using Tapatalk 2

dreamsforgotten said:
8 gig 1.2 gig quad core 8 hours. Use ccache when you build I would go 50 gigs
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You'll have to explain that.
That's quite ridiculous... now in doubting it... I don't think it'll handle that stress... it is a laptop I have a fan for it and it has a pretty good exhaust fan but that's still ass long as time.
Sent From My Toro+ via Tapatalk

ÜBER™ said:
You'll have to explain that.
Sent From My Toro+ via Tapatalk
Click to expand...
Click to collapse
Yeah on the build android page there are directions for setting up ccache you have to add a line to your bash rc and run a command before you build. When I head home, I'll add a page in tutorials explaining that further, it was next on the list.
Sent from my Galaxy Nexus using Tapatalk 2

Talking to motcher he says he uses ccache and with his dualcore 1.7ghz and 2 GB of RAM it takes him 3hrs and 1.5 after he builds ccache.
Sent From My Toro+ via Tapatalk

Great idea man.
I want to add status bar toggle and navigator key re–map in Stock ROM.
I have tried system ui.apk & framework.apk decompile, but somewhere struck.
Can you please help to achieve the goal
Sent from my Galaxy Nexus

8 hours!?
mine builds in 10 minutes after CCACHE, and 30-40 before....

ÜBER™ said:
Talking to motcher he says he uses ccache and with his dualcore 1.7ghz and 2 GB of RAM it takes him 3hrs and 1.5 after he builds ccache.
Sent From My Toro+ via Tapatalk
Click to expand...
Click to collapse
Instructions added here http://dreamsforgotten.net/ccahce.html Note the actual ccache folder difference in the command? Changed in JB.
sendhiloo7 said:
Great idea man.
I want to add status bar toggle and navigator key re–map in Stock ROM.
I have tried system ui.apk & framework.apk decompile, but somewhere struck.
Can you please help to achieve the goal
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Galaxy Nexus, I'd say don't do that. If you have a machine even remotely capable put you a linux partition, through VM if you must , and compile you a version from source. With step by step instructions those too mods wouldn't be that hard. First off, by decompiling you have to decompile both stock rom and a rom with the features you want. Then you have to put those changes in your file in smali which is bytecode aka machine readable. If you know my history, you know I have done this before with the Nexus S because the mod I wanted to copy was samsung proprietary code but in no other circumstance would I want to do that. You need to sync google source, add in the files for your phone, and then do some searching on github to find the two mods your wanting. You copy that code into your source and compile. It's more difficult than that and I just hit you with a lot so start at it, and when you reach a snag come back for help. But...if you must do this in smali...this is what you missing based on what you say you already started. decompile systemui.apk decompile frameworks/base decompile settings.apk. Find (whatever rom you find source for your mod) their version of the file rom control.apk. Copy that in your zip (obviously last step). Diff merge your stock decompiled 3 files against the rom's smali files. Same way as source, use github to find the affected lines of code. Copy over all code, all images, all xml files that are missing. Fix what's there and altered. Settings.apk is going to have a file in src/com/android/settings/foo/foo/ called settings.smali. This file is where your mods in rom control are going to be able to speak to mods you just did to the frameworks/base.

Thanks a ton dreams adrenaline is pumping hope I can get some sleep super excited for tomorrow.
Sent From My N7 via Tapatalk

ÜBER™ said:
Thanks a ton dreams adrenaline is pumping hope I can get some sleep super excited for tomorrow.
Sent From My N7 via Tapatalk
Click to expand...
Click to collapse
I seen how much my theme guides were referenced this is bigger and a huge load but much needed. Your quite welcome.
Sent from my Galaxy Nexus using Tapatalk 2

dreamsforgotten said:
Instructions added here http://dreamsforgotten.net/ccahce.html Note the actual ccache folder difference in the command? Changed in JB.
Galaxy Nexus, I'd say don't do that. If you have a machine even remotely capable put you a linux partition, through VM if you must , and compile you a version from source. With step by step instructions those too mods wouldn't be that hard. First off, by decompiling you have to decompile both stock rom and a rom with the features you want. Then you have to put those changes in your file in smali which is bytecode aka machine readable. If you know my history, you know I have done this before with the Nexus S because the mod I wanted to copy was samsung proprietary code but in no other circumstance would I want to do that. You need to sync google source, add in the files for your phone, and then do some searching on github to find the two mods your wanting. You copy that code into your source and compile. It's more difficult than that and I just hit you with a lot so start at it, and when you reach a snag come back for help. But...if you must do this in smali...this is what you missing based on what you say you already started. decompile systemui.apk decompile frameworks/base decompile settings.apk. Find (whatever rom you find source for your mod) their version of the file rom control.apk. Copy that in your zip (obviously last step). Diff merge your stock decompiled 3 files against the rom's smali files. Same way as source, use github to find the affected lines of code. Copy over all code, all images, all xml files that are missing. Fix what's there and altered. Settings.apk is going to have a file in src/com/android/settings/foo/foo/ called settings.smali. This file is where your mods in rom control are going to be able to speak to mods you just did to the frameworks/base.
Click to expand...
Click to collapse
Ok. its little bit hard to understand :crying: . Ok first i will build the VM & compile from sourece.. Then let you know

sendhiloo7 said:
Ok. its little bit hard to understand :crying: . Ok first i will build the VM & compile from sourece.. Then let you know
Click to expand...
Click to collapse
No problem, you start the work and I'll help where needed. Goto my website and use google for the VM. That should get you to where you are ready to build. Once you get there I'll help you with the options to both find the source code changes for your mods, and incorporate them into your source code.

dreamsforgotten said:
No problem, you start the work and I'll help where needed. Goto my website and use google for the VM. That should get you to where you are ready to build. Once you get there I'll help you with the options to both find the source code changes for your mods, and incorporate them into your source code.
Click to expand...
Click to collapse
Thanks
Sent from my Galaxy Nexus

Anybody have experience with Ubuntu 12.x and building android? Ran into an issue with repo. Trying to init the repo i want to sync it spits out the error 23: error : Python not found. Or something similar I forget exactly. The only thing Google brought up was the fact that I either have the wrong Python version or it is not in my shell path.
Sent From My Toro+ via Tapatalk

ubuntu 12.04 64bit: http://forum.xda-developers.com/showthread.php?t=1863547
its all you need. just replace the repo down there with rasbean's or whatever you want to compile. 12.04 has been a terrible pain in the ass for me, at some point i had to revert back to 11. but back then i couldnt find a nice and compact manual, so this one should guide you through.

molesarecoming said:
ubuntu 12.04 64bit: http://forum.xda-developers.com/showthread.php?t=1863547
its all you need. just replace the repo down there with rasbean's or whatever you want to compile. 12.04 has been a terrible pain in the ass for me, at some point i had to revert back to 11. but back then i couldnt find a nice and compact manual, so this one should guide you through.
Click to expand...
Click to collapse
Yeah that's what I feared... didn't feel like having to reinstall... I've been using 12.10 not .04 I know motcher uses 12.04 just fine. Going to get a bootable for it hopefully it likes my laptop.
Sent From My Toro+ via Tapatalk

I prefer debian over ubuntu now, with any distro that don't work with you pc out the box you probably need a proprietary kernel version. If you have a lap top that sound doesn't work you'll def need one. Additional files may need to be loaded for Wi-Fi support as well. All of these have pretty easy guides to get the job done. Be sure to set Linux up completely before establishing the build environment.
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Binaries...what do they mean?

I'm curious to what the binaries mean for upcoming roms. My assuption was that the roms were from the source meaning they had everything. So what are they and what for and why would they matter now? No this is not a "i'm a noob question" I just don't know...:angel:

www.google.com and if you dont know then sorry you're a newb
Sent from my Galaxy Nexus using xda app-developers app

b1337 said:
www.google.com and if you dont know then sorry you're a newb
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I already did that. Nothing really explained what it was "what are android binaries"
I didn't want to come off asking a typical question (which it probably is) that would result in you know, the typical noob answers:cyclops:
I wanted to know why are roms made without the google given binaries and with them "now provided" how would they make current roms and future roms any different, without directly asking

digitallure said:
I already did that. Nothing really explained what it was "what are android binaries"
I didn't want to come off asking a typical question (which it probably is) that would result in you know, the typical noob answers:cyclops:
I wanted to know why are roms made without the google given binaries and with them "now provided" how would they make current roms and future roms any different, without directly asking
Click to expand...
Click to collapse
They have provided th 4.2.2 binaries for building a 4.2.2 rom from aosp, that's all.
Currently, developers have been building 4.2.2 hybrid roms.

digitallure said:
I already did that. Nothing really explained what it was "what are android binaries"
I didn't want to come off asking a typical question (which it probably is) that would result in you know, the typical noob answers:cyclops:
I wanted to know why are roms made without the google given binaries and with them "now provided" how would they make current roms and future roms any different, without directly asking
Click to expand...
Click to collapse
ROMs are made with Google binaries, for the most part. Think of them as drivers for your hardware. For this Nexus, we're still missing camera and GPS binary. There's other ways around this though.
Sent from my Nexus

bk201doesntexist said:
ROMs are made with Google binaries, for the most part. Think of them as drivers for your hardware. For this Nexus, we're still missing camera and GPS binary. There's other ways around this though.
Sent from my Nexus
Click to expand...
Click to collapse
ooohhhh. ok. I get it. So this should make ROMs perform and stablier? I've been bouncing around 3 ROMs I like and when one acts up then i'll go to another. Almost given up and went back to stock 4.1.1...lol.

digitallure said:
ooohhhh. ok. I get it. So this should make ROMs perform and stablier? I've been bouncing around 3 ROMs I like and when one acts up then i'll go to another. Almost given up and went back to stock 4.1.1...lol.
Click to expand...
Click to collapse
Well, they do allow custom ROMs to be made, but new binaries don't necessarily mean new ROMs will be stabler. If you don't build from source, don't worry about it.
Sent from my Nexus

b1337 said:
www.google.com and if you dont know then sorry you're a newb
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Get off the forum. Seriously, you're not contributing to anything, you know damn well that's not an easy google-able answer.
Anyway, to expand on bk201's answer:
Code needs to be compiled for it to be run. When you take code and compile it, you get a "binary" that you can run, but you can't see the original code that created it.
Manufacturers and chip designers don't always like their secrets exposed (and for good reason) so rather than put out all the code for their hardware, they compile it themselves, and give us their binary.
The result is a driver we can use, but not change. That makes it trickier to work with when making a rom, and they're the reason many old phones run newer versions of Android very unstable or not at all.

Electrodeath0 said:
Get off the forum. Seriously, you're not contributing to anything, you know damn well that's not an easy google-able answer.
Anyway, to expand on bk201's answer:
Code needs to be compiled for it to be run. When you take code and compile it, you get a "binary" that you can run, but you can't see the original code that created it.
Manufacturers and chip designers don't always like their secrets exposed (and for good reason) so rather than put out all the code for their hardware, they compile it themselves, and give us their binary.
The result is a driver we can use, but not change. That makes it trickier to work with when making a rom, and they're the reason many old phones run newer versions of Android very unstable or not at all.
Click to expand...
Click to collapse
Thanks for the answer

Does anyone have a zip file to flash the new binaries for Maguro?

ReggieS2 said:
Does anyone have a zip file to flash the new binaries for Maguro?
Click to expand...
Click to collapse
You don't flash them. As has been discussed in this thread, they are used by developers when compiling a rom from source. If you're not compiling, then they aren't of much use to you.
Sent from my Nexus 7 using Tapatalk HD

najaboy said:
You don't flash them. As has been discussed in this thread, they are used by developers when compiling a rom from source. If you're not compiling, then they aren't of much use to you.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I read this over at Paranoid Android's G+ page so it lead me to think that I needed something
Recently the AOSP has been fully completely, all the needed drivers are supplied. We have updated AOSPA immediately of course and a couple of hours later we've had it merged.
Now i want everyone to listen up. YOU ABSOLUTELY NEED TO BE UP TO DATE. Or else your device will be incompatible, unable to make calls perhaps or who knows what. Google supplied a new bootloader, and for phones, new radios. You can get them straight from Google and install via fastboot. Or, the easier way perhaps, you go to XDA and get them as flashable ZIP files.
Either way, this concerns all 4.2.2 roms out there that include Googles new 4.2.2 hardware drivers.