Related
Hey Guys,
Whats the best tools for building the kernel? roms? rom kitchen etc.
For a macbook pro 17 10.6.4.
I seem to have problems with everything.
is there a tool-chain? for osx?
Thanks!
Wrong section buddy. Ask a mod to move it to general.
Sent from my SGH-T959 using XDA App
Alex530 said:
Wrong section buddy. Ask a mod to move it to general.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Honestly,
I dont see why this should go to general. Its about dev work. Hence in the android dev talk.
i agree, this is a development related question. I too would like to know where/which toolchain to get.
any help is greatly appreciated.
Development is for when you actually developed something.
Sent from my SGH-T959 using XDA App
vague questions about development in general on the android platform should go somewhere in here...
http://forum.xda-developers.com/forumdisplay.php?f=564
The vibrant section isnt the only subforum around here...
This section was made specifically for posting developments to the vibrant platform...
edit: oh yeah forgot about chef central all your cooking needs...
http://forum.xda-developers.com/forumdisplay.php?f=611
If you're looking to do kernel hacking or just build a system, then all you need is the command line. All of the tools in the SDK are written to be used this way, but if you're going to be editing source files, you may want a decent text editor (I like TextMate). If you're uncomfortable with the command line, then you probably shouldn't doing that kind of development.
For applications themselves, Eclipse is probably the way to go. It's a bit bulky (and not the nicest IDE), but it is quite competent and gets the job done. Plus, there are the ADT (Android Development Tools) that allows for graphical management of your SDK targets, as well as an AVD editor for setting up different emulator environments and one-button access to DDMS.
(While this question may have been best posted in the general Android dev section, I don't see any reason why it's not development related and should be in general or Q&A.)
rpcameron said:
If you're looking to do kernel hacking or just build a system, then all you need is the command line. All of the tools in the SDK are written to be used this way, but if you're going to be editing source files, you may want a decent text editor (I like TextMate). If you're uncomfortable with the command line, then you probably shouldn't doing that kind of development.
For applications themselves, Eclipse is probably the way to go. It's a bit bulky (and not the nicest IDE), but it is quite competent and gets the job done. Plus, there are the ADT (Android Development Tools) that allows for graphical management of your SDK targets, as well as an AVD editor for setting up different emulator environments and one-button access to DDMS.
(While this question may have been best posted in the general Android dev section, I don't see any reason why it's not development related and should be in general or Q&A.)
Click to expand...
Click to collapse
thanks rpcameron - we appreciate the info!
and vinnydakid why bother posting if it doesnt answer the question or provide direction. your comment just took up space...
sorry...double post...
rpcameron said:
If you're looking to do kernel hacking or just build a system, then all you need is the command line. All of the tools in the SDK are written to be used this way, but if you're going to be editing source files, you may want a decent text editor (I like TextMate). If you're uncomfortable with the command line, then you probably shouldn't doing that kind of development.
For applications themselves, Eclipse is probably the way to go. It's a bit bulky (and not the nicest IDE), but it is quite competent and gets the job done. Plus, there are the ADT (Android Development Tools) that allows for graphical management of your SDK targets, as well as an AVD editor for setting up different emulator environments and one-button access to DDMS.
(While this question may have been best posted in the general Android dev section, I don't see any reason why it's not development related and should be in general or Q&A.)
Click to expand...
Click to collapse
Thanks for this info.
I already use eclipe with the android plugin. That's how i was able to write the one click root apk.
But, ive tried a few rom kitchens. and they dont seem to work.
Also, Looking for a deox that will work on mac. For both APK/ROM.
Also, Looking to see how to build a kernel on a mac.
I think i need a working tool-chain to cross compile.
If someone can point me to it.
I haven't used it for android development yet, but xcode is an awesome application for programming on the mac. And best of all, not only is it free, but it ships on every osx install disc in the extras section.
Sent from my Vibrant using the XDA app.
Typos, incorrect words, gibberish, and other nonsense brought to you courtesy of Swype.
rhcp0112345 said:
Thanks for this info.
I already use eclipe with the android plugin. That's how i was able to write the one click root apk.
But, ive tried a few rom kitchens. and they dont seem to work.
Also, Looking for a deox that will work on mac. For both APK/ROM.
Also, Looking to see how to build a kernel on a mac.
I think i need a working tool-chain to cross compile.
If someone can point me to it.
Click to expand...
Click to collapse
To build a kernel from source on a mac, you're going to need to dual-boot linux (ubuntu seems to be very popular among devs) set up your dev environment and run a make (compile)
jroid said:
To build a kernel from source on a mac, you're going to need to dual-boot linux (ubuntu seems to be very popular among devs) set up your dev environment and run a make (compile)
Click to expand...
Click to collapse
I'm pretty certain that OS X can cross-compile Android's linux kernel. (I'm not 100% on this, but pretty certain. If it's not, a dual-boot is not necessary: I use a VM in VirtualBox.) However, if you're compiling Android sources (and AOSP), 10.6 is not presently supported (but it is possible, with work). Also, you need to use HFS+ with case-sensitivity—if your drive is not formatted for a case-sensitive filesystem, then building in a disk image is advisable.
Smali/baksmali both run on a Mac, so if you need to de-odex there is no problem there; but they are command line programs.
As far as a ROM kitchen: Call me crazy, because perhaps I'm in the minority here, but a "kitchen" is not really development in my eyes; it's putting a bunch of files into a zip file (which can be done on the command line, again), and perhaps editing a few text and/or XML files specific to the hardware.
In the end, other than ensuring your machine meets the requirements necessary to build the source (and you can find them at the source website, make sure to check the "Setting up your machine" section), the Mac already has all of the programs necessary. From what I've seen of most of Google's Android developers, many (if not most) use a Mac.
rpcameron said:
I'm pretty certain that OS X can cross-compile Android's linux kernel. (I'm not 100% on this, but pretty certain. If it's not, a dual-boot is not necessary: I use a VM in VirtualBox.) However, if you're compiling Android sources (and AOSP), 10.6 is not presently supported (but it is possible, with work). Also, you need to use HFS+ with case-sensitivity—if your drive is not formatted for a case-sensitive filesystem, then building in a disk image is advisable.
Smali/baksmali both run on a Mac, so if you need to de-odex there is no problem there; but they are command line programs.
As far as a ROM kitchen: Call me crazy, because perhaps I'm in the minority here, but a "kitchen" is not really development in my eyes; it's putting a bunch of files into a zip file (which can be done on the command line, again), and perhaps editing a few text and/or XML files specific to the hardware.
In the end, other than ensuring your machine meets the requirements necessary to build the source (and you can find them at the source website, make sure to check the "Setting up your machine" section), the Mac already has all of the programs necessary. From what I've seen of most of Google's Android developers, many (if not most) use a Mac.
Click to expand...
Click to collapse
At the moment MacOS 10.6 ("Snow Leopard") is not supported.
((((
well I meant vm when I said dual-boot. I'd recommend just to make a decent size partiton on your drive and install a linux distro. I'd rather make compiles on the full OS rather than compiling on a vm
I think im just going to wait for my netbook on WED. Macbooks only have 4G of ram. MAX. I hate VM'ing. slows everything down.
rpcameron said:
I'm pretty certain that OS X can cross-compile Android's linux kernel. (I'm not 100% on this, but pretty certain. If it's not, a dual-boot is not necessary: I use a VM in VirtualBox.)
Click to expand...
Click to collapse
After thinking on it a little, I realized the reason cross-compiling is an issue is only because of the processors, not because of OS X/xnu versus Linux. Cross-compiling is building for one processor on another—in this case, building for ARM on x86.
There really is no issue of OS X/xnu versus Linux because both are fully POSIX compliant; as long as the same build tools are used in the toolchain, the only issue is having an ARM toolchain running on x86. Don't know what I wasn't thinking clearly before, but there's the core of the matter.
Of course, the original caveats stand: building on 10.6 (Snow Leopard) is not supported, and the build cannot be done on a case-insensitive filesystem (which is the default for OS X). But git/repo and the rest of the build environment runs without a problem on 10.5, therefore there is no problem building Android/AOSP on a Mac. (Again, "cooking a ROM" is no problem regardless of your OS X version or filesystem, because nothing is really being built, only packaged.)
The kernel and even Eclair build even with Snow Leopard but you have to change some make files and fix some code. Google "android eclair 2.1 snow leopard" and you'll find a few links that tell you the changes needed. You also need to make some changes to build Eclair using the default Java 6 that comes with Snow Leopard - google it.
The toolchain for the kernel is Code Sourcery - both the 2009q4 and 2010q1 versions work. Also, you need to make sure that your disk is case-sensitive - or build a disk image that is case-sensitive and mount that, it is what I do. Again, google is your friend and there are some pages that tell you exactly what you need to do to set up the environment.
For development using the Android SDK, the installation page for the SDK tells you how to set it up on the Mac. You would use Eclipse for development. I tend to use emacs when in the Android code proper, while I use Eclipse for App development.
ROM kitchens - beats me. That's not development
-Atin
atinm said:
The kernel and even Eclair build even with Snow Leopard but you have to change some make files and fix some code. Google "android eclair 2.1 snow leopard" and you'll find a few links that tell you the changes needed. You also need to make some changes to build Eclair using the default Java 6 that comes with Snow Leopard - google it.
The toolchain for the kernel is Code Sourcery - both the 2009q4 and 2010q1 versions work. Also, you need to make sure that your disk is case-sensitive - or build a disk image that is case-sensitive and mount that, it is what I do. Again, google is your friend and there are some pages that tell you exactly what you need to do to set up the environment.
For development using the Android SDK, the installation page for the SDK tells you how to set it up on the Mac. You would use Eclipse for development. I tend to use emacs when in the Android code proper, while I use Eclipse for App development.
ROM kitchens - beats me. That's not development
-Atin
Click to expand...
Click to collapse
I read the 'thats what i do'
any chance you can share with me a pre-done version?
I really hate to go through all the work if its been done. (reinvent the wheel)
THANKS
rhcp0112345 said:
I read the 'thats what i do'
any chance you can share with me a pre-done version?
I really hate to go through all the work if its been done. (reinvent the wheel)
THANKS
Click to expand...
Click to collapse
I am assuming that you mean to build the kernel and eclair, not just do applications.
You will need to do *some* work if you want to build the kernel and eclair using Snow Leopard because you do have to set up your environment - read the http://source.android.com/source/download.html setting up your machine page to get that squared away and also install the code sourcery toolchain 2010q1 build. The changes in the eclair source are easy - use www.justinlee.sg/2010/06/22/compiling-android-2-1-eclair-source-on-mac-os-x-10-6-snow-leopard/ and follow the steps (there really are just two changes).
If you just want to build apps, then you don't need any of this and just need to install the SDK.
Formerly:
"[Q] Droid 2 Users using 32-bit(x86) or 64-bit?"
I'm trying to develop something that will help droid2 users but I need to know whether most people use a 32-bit OS or have a 64-bit OS. This way I can help the most people by starting on the one with the most users. Thanks for your input.
This is for any OS Windows or Mac or Linux.
MODERATOR: Please Close and Remove This Thread, Thanks!
If you have a 64bit you can run x86 so why not just make that version. <-- Windows at least
Anyways, I am running Windows 7 Ultimate x64
I thought about starting with that but because I'm running a 64-bit OS aswell I have to make the 32-bit product on a 32-bit OS so I'd have to do tweak it a little bit and was hoping most people were using 64-bit.
that makes sense.
32 bit is always the safest route to take because of the backwards compatibility of 64 bit OS with 32 bit executables. You are going to have to make that call though. If you want to reach the most people though, I would say 32 bit.
Sent from my DROID2 using Tapatalk
Can you shed some light on what you are creating? I am interested in this project. I can also host it for you if needed.
lol it has to do with linux and that's all I'll put out right now but I'll update as soon as I get further into it. This was going to be my test post because I want to start making it I just needed so guidance as to where to start.
That would be awesome if you could host (I'm new to dev stuff and was gonna ask for some help getting it out there).
not a problem. just let me know when you need it. I am currently working on acquiring a new domain so that it will host droid2 files and we can grow this section of the forums because the Droid 2 is lacking in the dev department lol
I'm new to d2 but facelessuser makes a good point. I'm intrigued...
Sent from my Full Android on Vogue using XDA App
This is just a heads up post
I'm almost done making a custom ubuntu 10.04.1.iso with adb and the sbf_flash script for linux install this will allow anyone to flash their phone in linux as it's a live cd and will be booted from the disk tray for a single session. No windows driver problems or RSDlite errors.
(it's in x86 if you were wondering; which was the main reason it's not already posted.)
Im kind of new to this. Iv'e created some apps succesfully in Eclipse and stuff like that.
But, I like to start with ROM development. I have no idea where to start! Would be really nice if someone could tell me how to start with creating/porting a ROM.
Iv'e read that you need to have Linux Ubuntu, is that true?
So Iv'e almost installed Ubuntu now on a Virtual machine, downloading HTC Android Kitchen. Am I doing right?
EDIT: Märkte att det nog fungerar till Windows. <- Also noticed that I wrote that on Swedish! :S (I wrote: Noticed that it propably works with Windows.)
As far as I know I don't think you need Ubuntu, but you've probably figured that out by now It should work for windows and mac too, although it looks like ubuntu is the only linux-based distribution it works on..
And I'm curious, How is the rom-making going?
I wouldn't recommend flashing roms using a virtual machine... a screwup in the vm might make your test phone a 600 dollar paperweight... check out wubi... actual partitioned ubuntu installer that when unstalled defaults back to the windows bootloader...so you don't have to screw with lilo or grub...oh also leaves windows as the default OS...so you don't accidentally boot into ubuntu after every reboot
Sent from my ADR6300 using Tapatalk
Ubuntu is perfect for ROM development/porting. A virtual machine is perfectly fine to dev on. But you will need at least a 12gb virtual disk though. These sites should get you up and running
http://source.android.com/
http://developer.android.com/index.html
Sent from Conical .07
I already got everything set up on windows.
HTC android ROM kitchen, SDK manager and eclipse.
I dont really know where to start. Ive just created a simple ROM using the shipped RUU, added like apps2sd, root and that stuff. Also edited like status-bar background in framework-res.apk and stuff like that.
Id like to go in abit more deeper, whats next?
Use the first link. Go to porting. Then go to "get source" on the left side.
You need to get the source. Then compile.
Sent from Conical .07
linuxmotion said:
Use the first link. Go to porting. Then go to "get source" on the left side.
You need to get the source. Then compile.
Sent from Conical .07
Click to expand...
Click to collapse
There is no "get source"? Link?
My bad. Its under source : -)). That site should be a good place to start
Sent from Conical .07
Everyone is allowed to make changes to the VMWare image and re-upload it. If you re-upload the VMWare image with the made corrections, post the download link(s) in this thread. I will update the first post.
If there is a AOSP Developer that is willing to make a complete tutorial, please make one that works and is up-to-date with 2.3.7
The more people we have working on making ROMs, the better.
This VMWare image is:
- Base: Ubuntu 10.04 LTS
- ICS ready
- Gingerbread ready
- Fully updated
- Eclipse with ADT Plugin
- Android Kitchen Integrated
PASSWORD: root
Latest changelog (Coming soon)
- Based on 10.04 LTS instead of 11.10
- Different approach
Download link:
Bypass 24h wait time, limit reached --> Solution? Reset your ip! In Belgium this is easy by restarting your modem/router. This may be different in other countries.
more mirrors will come!
Part 1
Part 2
Part 3
Image is extracted, where do I start?
Continue from this link
How to build 2.3.7 for Nexus S
This is just a snippet that may help you.
repo init -b android-2.3.7_r1 < /dev/null (This branch is ready to use with Nexus S and Nexus S 4G)
repo sync
source build/envsetup.sh
lunch full_crespo-userdebug
make -j8 (-j8 = for eightcores like 2600k, 2630QM / -j4 = for quads 2500K/2620M/Q6600 / -j2 for dual cores / ...)
Click to expand...
Click to collapse
Don't forget to add the vendor files of the device. You need to download the scripts as well of the driver binaries.
Click to expand...
Click to collapse
I tested a quick build. And it's working.
A virtual machine with limited RAM in order to compile AOSP? Definitively not a good idea. Why not dual boot? Sooooo easy to install the worst distro ever (*buntu).
This is awesome. My only problem is that I only have VMWare Workstation 7.
Super! Waiting for this
djjonastybe said:
Dear community,
I made a AOSP developer environment for VMWare Workstation 8 or latest VMWare Player (free).
You can use this VMWare image as a base to build AOSP ROMs. Imade it for those having trouble getting it to work or maybe if you don't have time to set it up properly. Well if you are downloading this you might have a good reason!
Anyway have fun!
If there are any errors let me know.
This VMWare image is:
- ICS ready
- Gingerbread ready
- Fully updated
Download link:
...uploading...
Click to expand...
Click to collapse
Who would have guessed that an android dev would have difficulty setting up a linux enviroment . . . go figure.
You do not have to be an Android Dev to compile Android. I haven't written a single line of code for Android and can compile AOSP 2.3.7 fine.
This is simply to save time. And if you have good enough hardware (like myself) compiling Android AOSP in a VM session works perfectly fine.
Most people that are into computers have a rocking system. I have 12GB ram, I dedicate 8 for my VM and the rest for my main OS (windows 7). Works fine, what's the issue?
Some people don't want to dual boot and sometimes a Linux distro doesn't support certain hardware or can't be installed.
I would appreciate it. THANKS
nice.....this could be very useful
Sent from my Nexus S using xda premium
FeaRThiS: Who would have guessed that an android dev would have difficulty setting up a linux enviroment . . . go figure.
Click to expand...
Click to collapse
You seem to be the only one against uploading this.
Guys I am still trying to upload it. I am splitting it in 700MB sizes. Crocko's uploadservice is down. I will upload it on depositfiles and multiupload
12,5%
@FeaRThiS just stated the obvious. I also think the first step to understand how to build an AOSP ROM is knowing how to setup the development environment.
I don't have anything against using a VMWare image. But, IMHO, considering the time for uploading/downloading the file, if you do the setup yourself (in VMWare or whatever), you should have already been compiling your ROM by now.
suksit said:
@FeaRThiS just stated the obvious. I also think the first step to understand how to build an AOSP ROM is knowing how to setup the development environment.
I don't have anything against using a VMWare image. But, IMHO, considering the time for uploading/downloading the file, if you do the setup yourself (in VMWare or whatever), you should have already been compiling your ROM by now.
Click to expand...
Click to collapse
Okay, its not useful for you two.
Next!
I like it and i will try it.
djjonastybe said:
You seem to be the only one against uploading this.
Guys I am still trying to upload it. I am splitting it in 700MB sizes. Crocko's uploadservice is down. I will upload it on depositfiles and multiupload
12,5%
Click to expand...
Click to collapse
I have nothing against it and it may even be useful in case of emergency when you can not access a linux machine, but as stated by @S suxeN the first step for any dev would be learning to create their own dev enviroment.
i didnt say that.
but the statement is right. Anyways i yet think this image is of great use, as you can always start from there, if u did something wront, what can always happen to nun-linux users.
I don't know anything about linux. Is Eclipse with ADT on here by any chance? If not, what IDE is there to develop with in this VM?
I didn't think that far. Eclipse is not installed.
But I will work on it for next release. For now you have to install it manually. I hope tomorrow evening the new vmware will be uploaded!
Hey guys, don't be so hard on the fella. He's doing us a great service in a way. Not all of us are able to bring laptops wherever we go, dual-boot, etc. I just downloaded this to my external drive that I use to keep my stuff on for work and it'll come in handy when I wanna test apps without worrying about nuking my phone.
Also, it helps that I can demo apps on the thing to co-workers on screen than using a phone. That way I won't have to worry about them screwing things up if they decided to 'explore.'
http://code.google.com/android/nexus/drivers.html#crespogwk74
Can someone help me with this? This has the binaries for the Nexus S.
Where do I place the scripts?
I have a vendor folder with several maps in it now. But I don't know what I have to do now.
I placed the 'vendor' folder in my working directory. But lunch isn't showing up crespo in the list.
These are my steps:
Building
I executed lunch. I realised I did not have crespo in the list. So next, I read the line 'Building for devices'.
Eventually I ended up here:
Building devices
Obtaining proprietary binaries
Starting with IceCreamSandwich, the Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for Nexus S, Nexus S 4G, Galaxy Nexus, and PandaBoard can be downloaded fromGoogle's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
There are no official binaries for Nexus One, ADP2 or ADP1., ADP2 or ADP1.
Click to expand...
Click to collapse
I clicked the link and downloaded the GWK74 binaries.
Now then I read further:
Extracting the proprietary binaries
Each set of binaries comes as a self-extracting script in a compressed archive. After uncompressing each archive, run the included self-extracting script from the root of the source tree, confirm that you agree to the terms of the enclosed license agreement, and the binaries and their matching makefiles will get installed in the vendor/ hierarchy of the source tree.
Click to expand...
Click to collapse
I have the vendor hierarchy...
Do I have to put these files in:
my home folder/bin
OR
home folder/workingdirectory_name
Or what do I have to do now?
updated first post with small hint on how to download 2.3.7 for our Nexus S. Good luck!
yep, i think this is pretty awesome. for me, i'm not an android dev but i've dabbled with theming and porting mods from other phones to the epic 4G previously. i'd love to be able to start with a system ready to go and mess around with some guides to learn how to compile source, etc... thanks.
Nice image man, gonna give it a go later. Thought I'd put my word in the discussion , sure there lots of talented devs, but they have all got different hardware/software and time requirements. So this becomes a useful tool to add to the inventory.
Im having a hell of a time figuring out how to configure git in Ubuntu 11.10. I am very new to the Linux environment and was wondering if someone could help me get my foot in the door and at least get the my work environment set up properly and the proper source code downloaded. Im really only interested in modifying the kernel so if you can help me set up and understand whats going on Id be greatly appreciative.
Thanks...
oh dude dont even get me started on linux ive literally just spent the past 2hrs trying to get flash to work on kubuntu i got so pissed i uninstalled and am switching back to ubu as we speak lol. ubuntu should have an irc help channel i know xubuntu did when i was playing around with it.
i just looked and there channel is #ubuntu
huzza!!!!!!!!!!!!!!!!! freakin a i finally got flash to work properly on kde shell i completly uninsulated kubuntu installed ubuntu downloaded flash from adobe not from the software center then put it in mozilla/ plugins folder and reinstalled kde on ubuntus terminal and all my settings stook. sorry for the rambling but yall have no idea of how stoked i am im probably going to make kde my default desktop now lol
I'm just having trouble getting ADB to recognize my phone. Also it seems Samsung didn't include a config file for the kernel to add things like overclocking etc.. Unless its hidden somewhere else?
Sent from my SCH-I400 using XDA
jaizero said:
I'm just having trouble getting ADB to recognize my phone. Also it seems Samsung didn't include a config file for the kernel to add things like overclocking etc.. Unless its hidden somewhere else?
Sent from my SCH-I400 using XDA
Click to expand...
Click to collapse
U building from source?
Sent from my SCH-I400 using xda premium
I have the source just not too sure how to utilize it in Ubuntu, like I said I'm learning as I go. I tried doing an adb pull from my phone for the config file in windows and I get the error "file or directory does not exist" however it did work when I tried it with my Acer A500...
Is there a config.gz included in the source somewhere? I've been reading about something called defconfig but there are numerous references to that within the source.
If I can find that file I feel like building our own kernel would be infinitely easier... Maybe I'm too optimistic..
i actually recocmend installing linux mint first a lot more stuff works out of the box with it but if you like unity just search for ubuntu in the software manager and u can install it over mint.
Just as an FYI, you are likely not going to be able to use Ubuntu 11.10 to build the Continuum kernel. You'll need to use either 10.04 (LTS) or 10.10 to get the proper build tools. Also, getting git to work should be as simple as installing it. I believe it is under git-core or similar. You should have a look at the page for setting up a build environment for AOSP on what to install and such, as it is a pretty good starting point.
Minty Fresh
I tried installing Mint over Unity with no success. All of the other desktop environments work, but not Mint. I wonders why.
u need to install the mint live cd first then one youve got everything update install ubuntu u can search for it in the package manage or get it in terminal
i believe the command is sudo apt-get ubuntu-desktop
Bierce22 said:
u need to install the mint live cd first then one youve got everything update install ubuntu u can search for it in the package manage or get it in terminal
i believe the command is sudo apt-get ubuntu-desktop
Click to expand...
Click to collapse
Will this erase windows like you too? Jk
Sent from my SCH-I400 using xda premium
10chr
Bierce22 said:
10chr
Click to expand...
Click to collapse
Cheer up chuck. I was just pwaying
Sent from my SCH-I400 using xda premium
Found this today. Came out today lol
http://rootzwiki.com/_/articles/the...or-setting-up-adb-and-transferring-files-r592
Sent from my SCH-I400 using xda premium
Anyone know what defconfig the Continuum uses? There are about 100 different defconfigs within the kernel source. Does the Continuum have a codename or something?
P.S. everything seems to be working fine in Ubuntu 11.10.
jaizero said:
Anyone know what defconfig the Continuum uses? There are about 100 different defconfigs within the kernel source. Does the Continuum have a codename or something?
P.S. everything seems to be working fine in Ubuntu 11.10.
Click to expand...
Click to collapse
Not sure., you might check the fascinate forums. I'd bet its the same.
Sent from my SCH-I400 using Tapatalk 2
jaizero said:
Anyone know what defconfig the Continuum uses? There are about 100 different defconfigs within the kernel source. Does the Continuum have a codename or something?
P.S. everything seems to be working fine in Ubuntu 11.10.
Click to expand...
Click to collapse
It should be listed in the readme with the source, but it should be something like "garnett_defconfig"