Hi XDA,
first of all, let's introduce myself. I'm a greenhorn at an indian outsourcing company working in the netherlands. my job is primarily 'being dutch' which happens to be a 24h a day job but something i can very easily multitask
so in a moment of 'what the coitus are they paying me for' i decided that i wanted to use a 'controlling-parent-or-boss-friendly' version of android. but it doesnt exists because android doesnt really allow such 'control' apps to work properly if they are 'only' an app (I tried a few to combat my infobesitas which is also the real reason why i'm doing this).
so why not. i'm a developer, i've got time. i know next-to-nothing about android, but i'm young and naive and terribly optimistic. lets get the source, modify it so it has baked in 'parental' controls, build it, use it, be happy with my lack of infobesitas, maybe sell it to my boss-and-other-evil-people?
so i tried to build AOSP using googles guidelines
i installed the latest ubuntu. i downloaded the packages (one didn't when i tried first but it worked when i downloaded it apart), created the working directory, got repo, repo-ed the source, ran the source configure.sh thing ran lunch and ran make.
my disk ran out of pizza space (i thought a 66gb partition would be enough, but not so much) so i enlarged my petition, throw the entire working directory away and repeated the process
only i get this error
out/host/linux-x86/obj/SHARED_LIBRARIES/libart_intermediates/arch/x86_64/quick_entrypoints_x86_64.o:function art_quick_instrumentation_entry: error: undefined reference to 'art_quick_instrumentation_exit_local'
googled this to no avail. put some post on my fb wall if anybody could teach me Android OS/ROM development for 150 euro (or more if i needed the person more than the ammount justifies). but i guess my 'friends' dont make roms in their free time (which is reasonable sinds im the 1337est h4ckz0r i know),
please help me with this.
so now i'm here. bounty is up for you too but for it ill expect a bit more than getting android to build. a teacher would teach me the ropes of rom dev using skype or something.
Related
Hello wonderful comminuty,
The long and the veiny of it is, I want to upgrade the (full) ubuntu I have running and I can't. I realize that this would most likely break things like aiw, and the top notification bar. I don't care about the top bar, but would want to keep aiw for obvious reasons. I've gotten much better at working with linux over the last few months, but I'm still quite nib, so please don't hate on me for dreaming if this is impossible. I've looked all over the place and haven't seen anyone talking about it, so maybe it's just too much. Here's my questions anyway:
1) Would upgrading ubuntu make anything better, or even be worth the effort it will take?
2) Is there any possible way to upgrade the ubuntu version used on the dock? (Automatic update obviously doesn't work. I've read a lot about manually upgrading with CD's and such and can't find a place to stick a CD in my phone. Also, couldn't seem to find a way to mount an image like a disk, or a way that worked rather.)
Thanks in advance for anyone who can help, even with the differences in versions of ubuntu and what upgrading would change.
I haven't tried it myself but i've run over the links a few times. If you're on 4.1.52/26 then heres the link: http://forum.xda-developers.com/showthread.php?t=1000316
If thats too complicated, here's the EASY guide to it with a video showing it off: http://androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-android/
Thanks for the reply and the information, but not quite what I was looking for. I've already used Sogarth's webtop2sd and have full ubuntu running. I guess I should have been clearer. What I meant was that after gaining full access to ubuntu, and fixing apt-get, and installing a bunch of programs, I sit here thinking, hmmm what's next. So since this version of ubuntu is like 9.04 or something, we're using old repos and outdated software. I want to turn it into like ubuntu 10.04+
Anyone can help with that?
You'll need a lot of time/energy, but...
should be possible to do it. I was thinking of doing this myself, but am not sure I can make the time (18+ hr work days ) Motorola recently open sourced the web top code. Take a look at http://sourceforge.net/projects/motorola-webtop.motorola/files/WT-1.2.0-X/WT-1.2.0-110+WT-1.2.0-135/
The instructions are already outdated at the site - the rootstock command in the readme no longer builds rootfs since the jaunty repository is no longer available. I tried to build the natty rootfs but that has a couple of problems (which can be resolved - I ran out of time this weekend )
I will keep at it as time permits (might take ages, since time is tight right now). Let me know if you want to take the plunge and successfully build this (or if you need help).
Cheers
It is not easy to do because Moto has a bunch of hacked up stuff in /osh
You could try the approach here: http://forum.xda-developers.com/showthread.php?t=1093790
What this does is bring up the standard webtop, but then runs applications in a chrooted environment with a standard dist. I am not ceratain how "clean" it is because you have a bit of both environments running.
The ideal solution is to port the Moto changes (those that one cares about) into the newer distro, but that is more work.
EDIT: missed acerbix's post. I agree
Thanks for the information guys.
I did stray from the path today, and thought "hey, why not just run the debian chroot stuff INSIDE my full ubuntu, and then I'd basically have a window with an upgradeable distro..." Well, needless to say, I did get it to work, the only problem being that I couldn't run a GUI since my display was in use already by the first instance of xserver. I'm sure there's a way around that as well, and I'll surely keep looking into it.
That's not what I REALLY wanted though anyway... I'm going to look through those source code files and see if I can figure this all out. Since we can move the whole webtop environment to the sdcard now (thanks Sogarth), my idea of a perfect end result would be a completely independant distro with just aiw functional. That top bar is pretty useless and wastes my screen space...
Any help is always appreciated, I'll let you guys know if I come up with something.
hey everyone. ive been googleing and googleing for weeks and weeks trying to educate myself on how the android build process works and how a device tree works. what i have been able to figure out is the device configuration has been moved form /vendor to /device between eclair and froyo. although i am very lost and confused. i have gone through source.android.com several times, and i have also gone through the very outdated platform developers guide. right now i am trying to teach myself how to set up a build environment for a real device. im doing this purely out of learning experience so i can apply it to something useful in the future. i have several devices at my disposal (epic 4g, droid1, atrix 4g, acer iconia a500) any of which i would be willing to use for learning. does anyone have any recommendations on reading material im missing? any good place to ask stupid questions? there is lots of documentation out there but i just cant seem to find it. where should i go from here? i wish i could just take a class on this. because there is so much information out there i have no idea where to go from here.
I was actually going to make a post along the same lines as yours. From what I have found the pinned post in this forum from cyanogen about cooking is probably the most useful information to get started.
The issue I have is a forum just on this topic alone. It would be nice to have a forum that only discussed merging manufacturers released code into AOSP. By googling I have found the Atrix source code that Motorola has released and also the AOSP itself. By reading cyanogens post and mucking around with the source this should give you a good start.
Good luck and if you come across a forum with just this topic discussed post a link.
Also for setting up an environment this post is good for getting everything setup to compile what you need. It is a post to compile CM7 but it can be used for what you are looking for.
gh123man said:
hey everyone. ive been googleing and googleing for weeks and weeks trying to educate myself on how the android build process works and how a device tree works. what i have been able to figure out is the device configuration has been moved form /vendor to /device between eclair and froyo. although i am very lost and confused. i have gone through source.android.com several times, and i have also gone through the very outdated platform developers guide. right now i am trying to teach myself how to set up a build environment for a real device. im doing this purely out of learning experience so i can apply it to something useful in the future. i have several devices at my disposal (epic 4g, droid1, atrix 4g, acer iconia a500) any of which i would be willing to use for learning. does anyone have any recommendations on reading material im missing? any good place to ask stupid questions? there is lots of documentation out there but i just cant seem to find it. where should i go from here? i wish i could just take a class on this. because there is so much information out there i have no idea where to go from here.
Click to expand...
Click to collapse
2nd hit googling android porting.
http://www.netmite.com/android/mydroid/development/pdk/docs/
Nothing is truly "update-to-date" there are somethings that your going to have to do your homework on. That is a very detailed guide on the basics of getting a port going and working towards the "device tree"
Unless the device tree is from a google nexus phone, then most likely the trees are not perfect. Cyanogenmod for example, the devs that work hard on creating those device trees don't just know what will and won't work. Each phone is different alot of trial and error. Do you build a binary from source, or do you use prop files already on the phone, that is all based on what is trying to be done and how much you know. Eventually you figure it out. It hard to just say what creates the device tree. Its just like someone asking for tips on how to write Java.
Bottom line, just do it and have fun.
lithid-cm said:
2nd hit googling android porting.
http://www.netmite.com/android/mydroid/development/pdk/docs/
Nothing is truly "update-to-date" there are somethings that your going to have to do your homework on. That is a very detailed guide on the basics of getting a port going and working towards the "device tree"
Unless the device tree is from a google nexus phone, then most likely the trees are not perfect. Cyanogenmod for example, the devs that work hard on creating those device trees don't just know what will and won't work. Each phone is different alot of trial and error. Do you build a binary from source, or do you use prop files already on the phone, that is all based on what is trying to be done and how much you know. Eventually you figure it out. It hard to just say what creates the device tree. Its just like someone asking for tips on how to write Java.
Bottom line, just do it and have fun.
Click to expand...
Click to collapse
thanks for the response. maybe im just searching for the wrong things... that and its not sinking in to my thick skull lol.. ill keep reading. im just trying to learn how it all works. some of the things i read either dont make sense or are really vague. i am currently cramming java into my head for app development. i suppose thats a good place to start. my end goal is to contribute.
gh123man said:
hey everyone. ive been googleing and googleing for weeks and weeks trying to educate myself on how the android build process works and how a device tree works. what i have been able to figure out is the device configuration has been moved form /vendor to /device between eclair and froyo.
Click to expand...
Click to collapse
I am trying to figure out how to build/port ROMs too. It has been a nightmare trying to study that. Not enough material, or the material is incomplete. Most of the tutorials are meant to be done with nexus devices wich has a native suport from android. No such a help for someone who is seeking a way to build for a new, unusual device (like me).
I didn't get this "three" thing. And, In my case, it is a little bit weirder because I am trying to build for a MTK6577 processor. (Some may say I am screwed).
although i am very lost and confused. i have gone through source.android.com several times, and i have also gone through the very outdated platform developers guide.
Click to expand...
Click to collapse
Many years ago I said: there will be a Time when people will know the "internet junkyard" or the "virtual online trash can".
I was reffering to outdated information. This information is available now and is not completely reliable because it is old and no one got rid of it.
It is something that is new (although the information is old, the event is pretty new) and we must learn how to deal with it. Unfortunally.
To de development point of view, I've been facing an incredible hard time just to find new information about building a custom rom from the source or porting an existent one.
I know i didn't help at all, but, I felt I must say that.
Anyway, knowing about anything, let me know.
Best regards!
gh123man said:
hey everyone. ive been googleing and googleing for weeks and weeks trying to educate myself on how the android build process works and how a device tree works. what i have been able to figure out is the device configuration has been moved form /vendor to /device between eclair and froyo. although i am very lost and confused. i have gone through source.android.com several times, and i have also gone through the very outdated platform developers guide. right now i am trying to teach myself how to set up a build environment for a real device. im doing this purely out of learning experience so i can apply it to something useful in the future. i have several devices at my disposal (epic 4g, droid1, atrix 4g, acer iconia a500) any of which i would be willing to use for learning. does anyone have any recommendations on reading material im missing? any good place to ask stupid questions? there is lots of documentation out there but i just cant seem to find it. where should i go from here? i wish i could just take a class on this. because there is so much information out there i have no idea where to go from here.
Click to expand...
Click to collapse
Here is the Small Guide Made to Begin from scratch for Android Device Tree Building
As in the title, I recently purchase a new HTC phone, and it's built for ChinaTelecom(carrier). So i think most here haven't even heard about it and it's called:
--------HTC new Desire VC
--------aka HTC t238d
Now comes the problem!!
Before this phone which i got it nearly free, i always relied on my oldold milestone. Quite old fashioned but really good phone and the most important thing is that Milestone is a WORLDWIDE POPULAR phone, so cm7, miui, anything else, worked hard with it~ Long casual years with Milestone, even after some 3rd-party rom groups stopped supporting it, it still has got lots lots of fans and hackers work on it. Until the day i change my phone, i was extremely using almost-perfect ICS on my oldstone...
But the stone finally get exhausted at everything, everything is not smooth, not one more app is installable or the phone became veryvery not-usable... And this new one mentioned above is great at these points, quite good hardware, stock ics etc.
The main thread comes: I hate Chinese carrier stock roms, and I hate HTC Sence also... And I have been using cm7~9 nearly all the time and of course, it's my favorite. But i can't find my SPECIAL phone in the cm10(or 9) support list without doubt. And no foreign hackers works on it without doubt again. There do exist some Chinese developers making t238d custom roms but they are not good.
Let me explain, in China, both developers and customers prefer a thing they called Chinaly I suppose... They don't like stock android, i mean the google one, they split out the gapps with nothing left but lots of Chinese things instead, i.e the huge Tencent Empire products maybe you have heard. Even they hate holo style!! Millions and Millions of apps are fake-ios themed. I am totally minority so not a single locale developers like my idea indeed.
I like google, like cm, like HOLOed apps, like fake-vanilla things even. And CM becomes my last hope. I have to port it to my phone on my own...
What I got
--------totally pure Linux OpenSuse(i686/x86-64 both)
--------openJDK, gcc things
--------SDK,NDK thins
--------the great kitchen
--------repo init -u git://github.com/CyanogenMod/android.git -b jellybean , repo init -u git://github.com/CyanogenMod/android.git -b ics both (jb prefered, i love cutting-edge toys... but no suitable develop skill sadly)
--------primodd kernel sources from here: h t t p://htcdev.com/devcenter/downloads (search desire vc you will also find them)
Then i think i have got a prepared environment and both clean complete cm src and htc stock kernel src, that means i can port cm to my phone!
But, if I really can, what shall i do now.....Just a little advice will be very very appreciated, cause i've struggled with those problem for quite long time.
And if i suck, which means i just can't do what i want because of any reason, please tell me too.
Thank you guys anyway！
Everyone that asks this gets the same response. There are many basic porting guides all over the web. Google for some of those. Find a phone with a similar build type. Might get lucky and find a device you can build and it boots, then you just have to fix device specifics. You are attempting to embark on a new journey. I don't have your device. I can't really help. You need to figure out a lot of this on your own.
What lithid said also applies to the rest of us. We can't say "Oh right, edit this file, that file, and the other file, and viola you'll have a perfectly booting CyanogenMod." It takes some experience, a lot of reading, and a lot of trial and error. Also expect the device to be unusable/unbootable 90%+ of the time so if this is your primary device I suggest holding off on the development.
So short story: Google it.
Hello Everybody,
I just wanted the ICS for my device as we are still running on GB and which is awful thing for an Dual-Core,Tegra-2 device(Micromax A85 a rebranded Mobile of K-Touch w700/Cherry Magnum 2X).We tried to create a ICS for our device but we failed as we are not having kernel sources for our device and they haven't released kernel for any device.
And so i started asking developers that can they help us and the only answer i got was no and they kept saying no way , your situation is hopeless and all that.
And Now I Just Wanted to know That when a mobile is manufactured first time they didn't have any kernel source for it they create it for the device or develop it for the device and when they can develop it then why we can't develop it as we all are humans and what they can do i can do.So Please Tell me now how to create kernels not that you can't,nothing can be done.And I think that Xda Is A Great Site and now i wanna know that are there real developers or there are some kind of script kiddies present in Xda.
Now Show me What developers have got and i know deep inside my mind that there are developers which can help me.They are just needed to be discovered.!!!!!
Well....it is possible, but ts a ton of work and will take months...its something no one wants to do for free, as the end result isn't worth all the work.
I'm no expert on kernels...I'm actually pretty new to them, but I'll tell you this: you have to identify every single chip in your device, you then need to implement there drivers...you need to make thousands of files....the end result is a folder that is over 100 MBS....almost completely "text" documents....I would never even attempt it unless I was getting paid a lot of money...
The people who make these from scratch (manufacturers) typically have teams of people who are specialized who have gone through years of schooling and work to get where they are at now.
And keep in mind there is different kinds of development....don't start calling people script kiddies if they don't know how to make kernels from scratch...for all you know thy could be one of the best app or game developers around...they are just specialized in a different area
I really dislike the way you are asking for help...you seem to be indirectly putting down a lot of people in the OP...and basically saying if you can't build a kernel from no source then you're not a developer...these people have jobs and life's, they don't have the time to make a kernel from nothing. The reason manufacturers are able to is because that is there job...that's what they do for hours a day everyday...
Anyways...try bugging the manufacturer for source...they have to release it or they are in violation of GLL (I think that's the name...) and they could get sued...as far as I know due to android being open source kernel source must always be released.
Sent from my SGH-I997 using Tapatalk 2
mg its GPL v2.0
mg2195 said:
Well....it is possible, but ts a ton of work and will take months...its something no one wants to do for free, as the end result isn't worth all the work.
I'm no expert on kernels...I'm actually pretty new to them, but I'll tell you this: you have to identify every single chip in your device, you then need to implement there drivers...you need to make thousands of files....the end result is a folder that is over 100 MBS....almost completely "text" documents....I would never even attempt it unless I was getting paid a lot of money...
The people who make these from scratch (manufacturers) typically have teams of people who are specialized who have gone through years of schooling and work to get where they are at now.
And keep in mind there is different kinds of development....don't start calling people script kiddies if they don't know how to make kernels from scratch...for all you know thy could be one of the best app or game developers around...they are just specialized in a different area
I really dislike the way you are asking for help...you seem to be indirectly putting down a lot of people in the OP...and basically saying if you can't build a kernel from no source then you're not a developer...these people have jobs and life's, they don't have the time to make a kernel from nothing. The reason manufacturers are able to is because that is there job...that's what they do for hours a day everyday...
Anyways...try bugging the manufacturer for source...they have to release it or they are in violation of GLL (I think that's the name...) and they could get sued...as far as I know due to android being open source kernel source must always be released.
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
It's GPL my friend.
But to answer OP's question, taking the Linux kernel and configuring it to boot on a phone/tablet takes a HUGE amount of effort and time. This is something that paid developers do for companies like HTC or Samsung. It usually requires a whole team of developers who work on it months, or even years before the release of the device. Even then, the developers still continue to improve on the kernel and the manufacturer can release an OTA update. I'm not saying that it's impossible, but it is a task that is definitely not worth it. It's just better to ask the company for the kernel sources.
i had always meant to do some developing but the drop in activity i realized when i moved from the sensation to the rezound really compelled me to start plus i have some work that i really have to do and really dont want to do so you know how it goes. Anyway to it
i started by googling how to build android roms which lead me to xda university giving me a nice expaination as to the various parts of android which i was already familliar
another search lead me to the offical how to build android from source page. i had a few concerns so i thaught i would ask here
i have knowlage building various web applications(php,js,ect) and not the let the fromework so this for me kinda apps i like thinking and innovating. i have a little experience with c++(i was at the stage of learning a gui when my old laptop crashed) so i think i have atleast good enough programming experience to catch on to java at a nice pace. Am currently reading and following googles nice little guid on developing android. Am in the process of setting up work envo (already got ubuntu 12.04 up). and thaught i would just leave a post here to see if anyone had any advice for me?
what i wanna do is be able to port for us,build original roms AOSP they call it for us, build and or port sense roms for us and eventually get to the point where i can get us sense5 or help neo(or any other dev) help us get sense 5. oh and i think i would like to build/modify kernels as well. oh oh and being able to invent exploits to get root or s-off for devices i might get in the future.
Question: while i was reading i was seeing where the buiding process was doing alot of synceing with google servers ect. i dont actually want to submit whatever garbage i might write to them while am testing so im still on the right track following the guid here correcto??
short version: I wanna build android custom roms ect not just edit files and put it out am i on the right tract following the guid here (i already know a lil programming)? http://source.android.com/source/initializing.html
any advice/resources/links welcomed
oki am on the page that says "building and running" i dont see anything for our device am guessing thats because development from aosp has stopped for us and thats where ppl like neo and cyanogen make thier magic. what is the next tut or read for me?
Try this. You could always pull Neo's CM 10.2 repos instead of the 10.1.
http://signatures.mobile-overload.com/wp-content/uploads/2013/07/sig-cm-5.png