This is a re-post of a question posed by naddie in the development forum. I was curious about something similar, and received some indication that the dev forum was the wrong place to get the question answered. Any thoughts over here?
"I'm starting to learn how to compile Android ICS from source, and thanks to Shen's tutorial, I'm starting to "get it".
So I do have a few questions before I get started.
1) Does the Nexus S and the Samsung Vibrant use the exact same hardware?
2) Can I use the Nexus S binaries listed here (http://code.google.com/android/nexus/drivers.html) for the Vibrant if question #1 is a "yes"?
I was going to buy a Nexus S or GNexus just for the purpose of learning, but if my Vibrant is basically an Nexus S, I say why not use it? It's not my daily phone.
FYI, it already has ICS Passion v9.2 on it, and has an FFC (I added it). I would just like to get started in compiling my own ROM for the sake of learning, starting a new hobby, and hopefully able to contribute to the Android community in which I have already benefitted as a ROM-flashing enthusiast."
Yep, that'd be me. Posting to automatically subscribe.
I went ahead and followed the steps of Shen's guide and currently compiling into an OTA package.
I built it as if it was for a Nexus S. Would I brick my Vibrant if I flash it?
If so, what do I have to do to make it a Vibrant specific ROM, assuming the binaries for the Nexus S works for the Vibrant?
Right now I'm thinking there's no way it will work just like that. Otherwise ICS for the Vibrant would have been a trivial thing for the more seasoned developers.
Even if it's something I can't do on my own, I'd like to learn how it's done. Anyone who can chime in on this, please do. Thanks!
*bump*
Anyone?
Dude, I think you and I are alone on this one... :E
the devices are a little different but what you could do is track down all the specs of the vibrant, chip set and everything and figure out what is the same between the 2, then you wouldnt have to port over as many binaries, also we have 3 ics ports currently so you should be able to take everything you need from those roms and build for the vibrant
I am fairly certain there is a way to do it on your PC to compile all the binairies, libs, modules,...and flash it through a type of dummy phone set up on your PC without ever touching your physical phone. It was in another forum that I am a member of. If you want more info on it, I can PM a buddy of mine about it. Not sure if it was a github type thing or some other repository and then you build your source on your PC and if it works great you can transfer to phone. If not, then no harm no foul and you find the problem.
You can pull up basic specs on NS and Vibrant on GSMarena side by side. That is how I decided on picking the Vibe instead. I am kind of a media whore and like the external sd slot. 14+gb on internal and 32gb sdcard is supreme storage.
I decided to do it proper, and found that the CyanogenMod github has the binaries:
https://github.com/CyanogenMod/android_device_samsung_vibrantmtd
However, in the step where I run ./extract-files.sh (which requires the phone to be jacked into the PC and recognized by ADB), it copied files over, but had complaints of missing files.
Upon running lunch, it said it did not find a config file for the SGH-T959.
Here's the post I did on the Tutorial thread. No answers yet.
I appreciate the responses here, though.
http://forum.xda-developers.com/showpost.php?p=21025049&postcount=89
Related
I know that the Dart is based off of the Galaxy Mini, which runs Gingerbread, and was wondering if there is any known way to get Gingerbread on the dart (which runs Froyo stock.) Is there an image of the Galaxy Mini I can flash, or a Cyanogen port or anything? I haven't really seen much as far as custom ROMs for this phone.
Yea any info for this phone will be great I got one and need drivers to work in xp or 7
I am also looking for info on a gingerbread rom for this and there are gingerbread roms for the galaxy mini which is the same device pretty much but someone has to code one.
what do you mean you need usb drivers, to turn it on to usb mode go to usb mode on the device, if you need drivers then you can use the galaxy s drivers from samsungs site
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Yes, there is CyanogenMod running on the SGH-T499. Unfortunately the forums where it is posted are down at the moment. Mostly everything is working, there is the screen wakeup delay on incoming call, and the buttons at the bottom don't light up.
If you are planning on doing the network/sim unlock, it has to be done on the original rom, so might want to do that first: http://forum.xda-developers.com/showthread.php?t=1335548
I can't post external links yet, so here is the post that links to the other forums where the latest CM port is posted: http://forum.xda-developers.com/showpost.php?p=19936092&postcount=100
continue developing
ive noticed that development seems to have dragged to a halt on the t499 and i was wondering if someone would be interested in making a project out of this, perhaps continue developing on the cm7 that has already be started, or the cm9 that the thread has been closed on, im not too experienced in development on android but id be willing to help any way possible
I was hoping to find something here for my girlfriends Dart. Looks like I may have to tell her to get a new phone after having it less than a year. To bad. She loves her Dart. I was wanting to make it more enjoyable for her. I'm not a programmer but I can read and follow directions. If there is anything I can do to help, let me know. As of 12/14/2012 my Gf. still has the phone..
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
Sorry first off I'm not sure if this is the right forum. Was thinking developers but there was an ominous warning at the top of that one so I decided not to take the chance.
The question is can Linux be installed on an Android based device natively? I'm aware of chroot enviroments and have done those. I also found this http://forum.xda-developers.com/showthread.php?t=981688 which is slightly cooler but it's still an AUFS based chroot mount. I found the same question asked here http://forum.xda-developers.com/showthread.php?t=1272964 but there was no answer and I didn't want to zombie the thread. Google searches didn't turn up anything useful either.
While I'm thinking the question is fairly device agnostic my device is a Droid 2 Global. I'm getting ready to replace it soon but I'm thinking it might make a nice little embedded system. From what I've read about my device in particular it's got some type of "lock" that disallows the use of other kernels but I am not afraid of recompiling the kernel for my device with additional needed modules for file systems or whatever. I have done this in the past.
I'm not super picky on the distro, but given a choice I guess I'd go with Debian (hardly ever changes so I can just check for security updates once a week or so and otherwise forget about it).
I wouldn't expect anyone to be able to answer this directly as I'm sure it'd be a novel. I'm more hoping someone might have a link to a guide or something that I just completely failed to locate.
So I kept digging and I found this: http www dot htc-linux.org forwardslash wiki forwardslash index.php. As the link suggests it's focused towards HTC devices but between it and some other links on there I think I can work with it.
I'll mark the thread as [SOLVED], but since it ended up being fairly useless (sorry) go ahead and delete if it amuses you to do so, any passing admin.
Ubuntu is coming out with an official version for Android soon.
Sent from my ADR6425LVW
I Am Marino said:
Ubuntu is coming out with an official version for Android soon.
Sent from my ADR6425LVW
Click to expand...
Click to collapse
This is probably your best answer. The Ubuntu build that runs on top of Android for webtop/lapdock purposes is running from the same kernel as Android is according to what I've heard. They will be providing the source so we'll see what the community can do with it.
It is possible on some Android devices, such as the Transformer and Desire.
But the Droid 2 Global, having a locked bootloader and the inability to install custom kernels, is not able to use native Linux.
If you want an Android device that is able to use native Linux do some research to find the one that fits you best.
Sent from my DROIDX using Tapatalk
have you seen this? interestiong reading...
http://whiteboard.ping.se/Android/Debian
Itbelikedat said:
have you seen this? interestiong reading...
http://whiteboard.ping.se/Android/Debian
Click to expand...
Click to collapse
I tried it a small time ago. Everything works but zygote and its forks fail to start, perhaps due to mount namespaces implementation on Android, but I'm not sure. Seeking a way out for this but not successful so far due to lack of knowledge.
Hi guys
I'm aware of CyanogenMod, but is it possible to have a completely stock JB ROM with no mods (other than busybox, deodexing, etc..) or custom apps installed? I can't seem to find one
Cheers
The community will correct me if I'm wrong, but I believe you'd have to build from source (AOSP) if you wanted something that is super-vanilla and hasn't been touched by a manufacturer outside of CM, AOKP, etc.
That said I also believe this particular question should be posted in the General or Q&A sections, for future reference.
djmatt604 said:
The community will correct me if I'm wrong, but I believe you'd have to build from source (AOSP) if you wanted something that is super-vanilla and hasn't been touched by a manufacturer outside of CM, AOKP, etc.
That said I also believe this particular question should be posted in the General or Q&A sections, for future reference.
Click to expand...
Click to collapse
Thanks for the reply
I mean Android was made to work on all devices right, but does CM do something like adding "drivers" (or the equivelent)? Is that what developers do when they "port" something like a new ROM that has been released on a similar device?
If multiple devices have a stock Android JB ROM, and they're also using a Tegra 2 CPU (and I'm guessing they all use the same type of RAM) etc.. is it quite easy to port? Do you have any idea how difficult it would be to compile it from source/getting it to run on a device?
I'm into technology, but without some serious research, I wouldn't have a clue where to start unfortunately
P.S. Yeah I realised after, already reported it to be moved
I've never ported between devices, but I've read enough to say confidently that things can be tough if you are porting between devices that are too different. At the very least you should stick between manufacturers...like it would be easier to port from Galaxy S2 Hercules to S2 Skyrocket for example than it would be from S2 to HTC xxx. There are quite a few good guides that explain how to port safely as long as the board configs and other important stuff are the same. If you aren't sure, don't do it.
For compiling from source, do a search on XDA here for shenye's guide "Compile JB on Ubuntu" - it was also featured on XDA TV. It's very helpful. Compiling isn't all that hard, but takes time and patience especially if you are working on a non-flagship device. It will likely take much research to find the right repositories for your device and vendor config, plus time to fix any errors the compiler reports.
Good luck!!
My Atrix got it's case cracked and the touch-screen display died, and given I already got a replacement phone I feel a bit adventurous. I wanted to see if I could build my own computer with what remains, so I wanted to run Linux natively (no Android). Given that there's a Linux 4 Tegra from Nvidia:
Is there a chance that I could build my own distro based on that?
Should I use another kernel (like the one currently used in gingerbread or CM7)?
Please note that I'm not trying to do webtop.
I thought of building my own handheld with the Atrix, or what remains of it. So any tips on how to get started would be great.
Cheers!
wrong section
ovitz said:
wrong section
Click to expand...
Click to collapse
Umm... what section would you suggest other than Q&A?
It was moved. Sorry 'bout that. I was under the impression that development questions were on the other forum...
"Android development" is in the description. I think they keep that forum just for Android-specific things, even though Android is just a flavor of linux.
tonglebeak said:
"Android development" is in the description. I think they keep that forum just for Android-specific things, even though Android is just a flavor of linux.
Click to expand...
Click to collapse
You're being way too literal. It's been used for all sorts of non-Android dev multiple times. Right now, Boot2Gecko is right there. The fact of the matter is that when it pertains to dev questions, this post would most likely be answered there. I'm pretty sure it'll die here on this forum with barely any useful answer, if at all.
The development section is mostly for things that are "in progress", ie. with "something to show". Questions, discussions and ideas go elsewhere.
As for your question, I believe I've seen a thread about this already, and quite recently too.
ravilov said:
The development section is mostly for things that are "in progress", ie. with "something to show". Questions, discussions and ideas go elsewhere.
As for your question, I believe I've seen a thread about this already, and quite recently too.
Click to expand...
Click to collapse
I've checked a few that I've found on the forum, but most had no answer and were about other devices. With regards to the Atrix or the Tegra, I've only found threads about webtop.
Not to argue too much about this too much, but I've seen threads that started with nothing in the dev section. Like the Kernel porting project that started as a mere placeholder for the project. Point is, I've done my research and found no pointers to the questions I have. I made it in case another dev had an idea about it. I may have missed something, but that's why I asked in the first place. If I believed I had covered all grounds by myself, I wouldn't have asked in the first place.
Lugaidster said:
I've checked a few that I've found on the forum, but most had no answer and were about other devices. With regards to the Atrix or the Tegra, I've only found threads about webtop.
Not to argue too much about this too much, but I've seen threads that started with nothing in the dev section. Like the Kernel porting project that started as a mere placeholder for the project. Point is, I've done my research and found no pointers to the questions I have. I made it in case another dev had an idea about it. I may have missed something, but that's why I asked in the first place. If I believed I had covered all grounds by myself, I wouldn't have asked in the first place.
Click to expand...
Click to collapse
What you're looking to do seems similar to this question: http://forum.xda-developers.com/showthread.php?t=2110161
The difference between the webtop and a stand alone installation of Linux won't be that different, mainly it would just be where on the device the OS is installed and how video is handled. That said, I'm not sure about the kernel, specifically the video drivers, since they're intended for Android and may not be compatible with X. AFAIK, Wayland is closer to Android than X is, but Wayland isn't quite ready.
Anyway, assuming you did succeed, what you would end up with would be less like a true desktop (as you'd be pretty much locked into a specific kernel, and therefor any packages limited by it, but it doesn't invalidate the effort), and more like a persistent live CD, since the OS would be installed to an area mounted as read-only (to prevent flash wear), with access to an area that has read/write access, like in Android where you store apps and user files. Overall, it could be fun if you enjoy a challenge and aren't intimidated by soldering and using the JTAG connector.
lehjr said:
What you're looking to do seems similar to this question: http://forum.xda-developers.com/showthread.php?t=2110161
The difference between the webtop and a stand alone installation of Linux won't be that different, mainly it would just be where on the device the OS is installed and how video is handled. That said, I'm not sure about the kernel, specifically the video drivers, since they're intended for Android and may not be compatible with X. AFAIK, Wayland is closer to Android than X is, but Wayland isn't quite ready.
Anyway, assuming you did succeed, what you would end up with would be less like a true desktop (as you'd be pretty much locked into a specific kernel, and therefor any packages limited by it, but it doesn't invalidate the effort), and more like a persistent live CD, since the OS would be installed to an area mounted as read-only (to prevent flash wear), with access to an area that has read/write access, like in Android where you store apps and user files. Overall, it could be fun if you enjoy a challenge and aren't intimidated by soldering and using the JTAG connector.
Click to expand...
Click to collapse
Actually, I might have to do soldering anyway. I'm not really intimidated by it and don't really care all that much for phone functionality and such. I'm not even interested all that much in X as my project is more towards transforming it into a handheld gaming (more like emu) device. I don't mind compiling software specifically for the system. The question is pretty low-level in that regard for me. I want to know if I have to do anything with regards to the kernel since it's specific to Android. Given that most emus I know that would run acceptably in a tegra 2 don't really need the GPU, I don't mind just using framebuffer so HW doesn't really interest me.
Lugaidster said:
Actually, I might have to do soldering anyway. I'm not really intimidated by it and don't really care all that much for phone functionality and such. I'm not even interested all that much in X as my project is more towards transforming it into a handheld gaming (more like emu) device. I don't mind compiling software specifically for the system. The question is pretty low-level in that regard for me. I want to know if I have to do anything with regards to the kernel since it's specific to Android. Given that most emus I know that would run acceptably in a tegra 2 don't really need the GPU, I don't mind just using framebuffer so HW doesn't really interest me.
Click to expand...
Click to collapse
Unfortunately, it's going to be one of those areas where you'll have to make an educated guess, since as far as we know, no one has successfully pulled off a straight Linux implementation on the device.
That said, nVidia does have both Android and Linux images for the Ventana dev kit, so it should be possible. In my case, I would compare the source code for their Linux kernel vs the stock Linux kernel vs their closest Android kernel vs the stock Android kernel. The biggest thing is how the the device specific files translate from one kernel to another, because you'll likely need to translate the device specific files for the Atrix in the same manner. The changes may be subtle or they may be drastic. The main thing is to just be able to set the pins properly so you don't release any "magic smoke". Unfortunately, I see no source code for any of nVidia's kernels.
Anyway, that's how I would do it, but I do suspect that someone with more knowledge could find a much simpler approach and hopefully they'll chime in, but this part of the forums isn't the thriving hub of activity it used to be, so I don't know if that will happen any time soon or at all.
lehjr said:
nVidia does have both Android and Linux images for the Ventana dev kit
Click to expand...
Click to collapse
Atrix is a Whistler, not a Ventana.
http://forum.xda-developers.com/showthread.php?p=33289027#post33289027
ravilov said:
Atrix is a Whistler, not a Ventana.
http://forum.xda-developers.com/showthread.php?p=33289027#post33289027
Click to expand...
Click to collapse
Thanks for the heads up and the link! :highfive: