hello xda-developers
I am having problems building from source, I've been trying to get his to work for over a week or so with the help from the lovely people here:
https://github.com/EpicCM/d710tools/issues/10
I think this forum is probably a better place, I will organize my thoughts better on this forum for all to read!
i've tried to install this on different systems, a 12.04 ubuntu, 12.04 and a clean 10.04 vm. in my next post i show all logs for the 10.04 attempt. the build results are also for 10.04
WHAT'S WRONG:
The problem is (depending on the guide i follow) cm9 either does not build (complains about libump.so not existing, despite having the proprietary repo in my localmanifest), or when i install the .zip, my phone goes into an eternal black screen after the "samsung galaxy s2" screen
There are two different basic setups i've been doing (i've tried these two setups in ubuntu 12.04,12.10,10.04LTS)
And i cannot figure out why the [email protected]#$ing [email protected]#$ why!!!!!!!! /rant
(log)Build instructions 1:
this is the build instructions that lead to a build error, these instructions were taken from here:
https://github.com/EpicCM/d710tools/wiki
commands: http://pastebin.com/WbXgKmZp
results:http://pastebin.com/Lq5iLt8L
Note: between each build i do make clobber and make installclean.
(log)Build instructions 2 (after i do make clobber and make install clean, repo sync, and the vendor and d710 tools again):
taken from the readme here
https://github.com/EpicCM/d710tools
commands: . build/envsetup.sh && brunch cm_d710-userdebug
built results:http://pastebin.com/8FWtqkRf
and if you feel the need to download the file, here is a direct download link
buildresults.txt : pastebin.com/download.php?i=8FWtqkRf
NOTE: you'll notice i had to sudo apt-get install schedtool. Also, i've done this from scratch before so i know if i dont at the end up the build it tells me to get pngcrush, so i do that too
WHAT I KNOW:
I've done my homework on the error for the build instructions 1:
-I know libUmp.so is a proprietary file, and the file does no exist in that directory, however it exists in another directory.
-Looking at the proprietary, that is where it should be, is there a script to move these directories? it's not a simple one line cp.
WHAT I DONT KNOW:
-builds but black screens? wtf?
-even if i managed to make something to do the cp to the appropriate directories, I dont even know if i'll end up with the same problem
-perhaps there is more not stated in the tutorial? if so I cannot find it
help? i've lost some hair over this, i hope you all can help buy me time to grow it back
i'll try anything.... i'll start over from an 11.10 if somebody even hints it might work...
what i want from this post
--well of course i would love a solution
--but really what i need is help to debug this, i have no idea where to start, i've done all i believe google and my brain can handle
reserved
more debug information, non build logs. These are the instructions as i followed
LOGS:
With the goal of being very thoughrough, i will start from a clean ubuntu 10.04 VM (network is using bridged), and I will post the result of each command to setup the environment for building.
If i saw an error with these i would google, but i dont see a problem, so i'm here.
Here we go (using this guide to setup env for 10.04 https://github.com/EpicCM/d710tools/wiki)
NOTE: for this step i had to change 0.2.4 to 0.2.6 because 0.2.4 was not building, 0.2.6 appears to work with no problem.
Setup local java repo and java commands: http://pastebin.com/RGhD1Shb
Results: http://pastebin.com/iEnNzSh3
(log)Installing required packages (Ubuntu 10.04)
commands: http://pastebin.com/eCZXkNvV
results: http://pastebin.com/vwzxfVsq
(log)Iidk what this is but guide said to do it for ubuntu 10.04:
command: sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
result: [sudo] password for tryagain: [email protected]:~$
(log)IMKDIRS, DOWNLOAD REPO, INIT REPO:
commands:http://pastebin.com/58aunVxB
results:http://pastebin.com/kKq9vyf5
(log)IThen i LOCAL MANFIFEST saved as local_manifest.xml inside ~/android/system/.repo/local_manifest.xml, here's what my localmanifest looks like:
http://pastebin.com/SCPAV8Ne
(log)IREPO SYNC THE FILES:
you may notice in the script file i had to repo sync -j1 more than once, because sometimes it would fail... in the end had no errors
commands : repo sync -j1
results: http://pastebin.com/a5Pa3sbL
results2: http://pastebin.com/VGPcPrE6
(the reason why there are two results is that i apparently forgot to save the local_manifest.xml the first time, results2 shows with the syncing of the files i have in my local manifest)
(log)IPREBUILTS, APPLY.SH:
commands: http://pastebin.com/VVx84ujN
results: http://pastebin.com/w9Wij28c
NOTE: i had to gedit the vendor to get the term.apk since
https://github.com/downloads/jackpal/Android-Terminal-Emulator/Term.apk isnt working
i replaced https://github.com/downloads/jackpal/Android-Terminal-Emulator/Term.apk with http://dl.dropbox.com/u/11103217/Term.apk to get things going.
reserved
reserved just in case, i got a lot of text
I've tried different jdks different tutorials and refine this from scratch on 3 different Linux versions
Sent from my SPH-D710 using xda app-developers app
updated!!!!
bump
1/24hour bump
1/24 bump
Nigel here, try running running: adb lolcat ; while you're on the blackscreen so we can get some insight into what's wrong with the rom.
so adb logcat doesnt work, it doesnt recognize my device as connected to my computer on the black screen.
The computer says it's an unknown device, or the device errored.
but that didnt stop me from trying anyway, i went into recovery to try and find what i wanted. As adb works in recovery for some reason.
when i execute it in recovery i get this
C:\Users\dfreelan\Downloads>adb logcat
/sbin/sh: exec: line 1: logcat: not found
so I went into adb shell while in recovery and executed /system/bin/logcat and got this
http://pastebin.com/8hnAa3iK
I went into /dev/log and executed "cat main" and tried to cat all the other things there, but i didnt get more information than what you see there.
Here is the recovery.log from installing the .zip, in case that is good for some debugging:
http://pastebin.com/gVC1TYyy
dfreelan said:
so adb logcat doesnt work, it doesnt recognize my device as connected to my computer on the black screen.
The computer says it's an unknown device, or the device errored.
but that didnt stop me from trying anyway, i went into recovery to try and find what i wanted. As adb works in recovery for some reason.
when i execute it in recovery i get this
C:\Users\dfreelan\Downloads>adb logcat
/sbin/sh: exec: line 1: logcat: not found
so I went into adb shell while in recovery and executed /system/bin/logcat and got this
http://pastebin.com/8hnAa3iK
I went into /dev/log and executed "cat main" and tried to cat all the other things there, but i didnt get more information than what you see there.
Here is the recovery.log from installing the .zip, in case that is good for some debugging:
http://pastebin.com/gVC1TYyy
Click to expand...
Click to collapse
adb logcat doesnt work in recovery.
While in recovery, adb shell and pull a last_kmsg, also try editing your local_manifest to build with the ics device tree not the smdk tree and see if that helps.
ie: "<project name="EpicCM/android_device_samsung_d710" path="device/samsung/d710" remote="github" revision="smdk" />" change that to "ics", i think smdk had some issues with cm9.
also if you want, hit up #jb-dev-e4gt on freenode, you may get some help there, our main dev chris41g is MIA so the progress on this device is at a stand-still. Though i do see sbrissen and PhantomPhreak53 are working on cm10.1
hrubak said:
adb logcat doesnt work in recovery.
While in recovery, adb shell and pull a last_kmsg, also try editing your local_manifest to build with the ics device tree not the smdk tree and see if that helps.
ie: "<project name="EpicCM/android_device_samsung_d710" path="device/samsung/d710" remote="github" revision="smdk" />" change that to "ics", i think smdk had some issues with cm9.
also if you want, hit up #jb-dev-e4gt on freenode, you may get some help there, our main dev chris41g is MIA so the progress on this device is at a stand-still. Though i do see sbrissen and PhantomPhreak53 are working on cm10.1
Click to expand...
Click to collapse
well apparently it never writes to /proc/last_kmsg
I figured for kicks and giggles i'd show you kmsg i got freshly booting into recovery, but my guess is that it's no good.
http://pastebin.com/jJC6ZJsZ
here's the brunch std err, they error out as there is no target for d710 (maybe i should use the old kernel? new one is smdk)
http://pastebin.com/jP0mTkZS
brunch stdout
http://pastebin.com/X571EkmR
here's what happens when i use make -j4, you'll notice it still errors out on libUMP.so
http://pastebin.com/eXEcTRPK
here's the new local_manifest.xml, you know to make sure i didnt [email protected]#$ up
http://pastebin.com/zXLCWDAP
when i use the _old kernel (android_kernel_samsung_epic4gtouch_old) i get this build error:
http://pastebin.com/09hDh8Nh
when i use the control kernel (android_kernel_samsung_epic4gtouch) It compiles!!!!!
however, still does the same infinite black screen (and i was so optimistic too)
here's my new local_manifest.xml
http://pastebin.com/FgARtF77
and of course, there is still no last_kmsg :-/
You might take a look at this:
http://aosp.chris41g.org/chris41g_o...How-To-Compile-CyanogenMod-9-from-Source.aspx
I followed this guide, generally, with changes to compile CM10 and got it to work. I did it on ubuntu 12.04. I did have to make some changes for 12.04. I didn't/don't know what I am doing, but got it to compile and flash and work.
todivefor said:
You might take a look at this:
http://aosp.chris41g.org/chris41g_o...How-To-Compile-CyanogenMod-9-from-Source.aspx
I followed this guide, generally, with changes to compile CM10 and got it to work. I did it on ubuntu 12.04. I did have to make some changes for 12.04. I didn't/don't know what I am doing, but got it to compile and flash and work.
Click to expand...
Click to collapse
i was actually doing exactly that to try and get cm9 to work my very first time. i talked to hrubak on the irc channel. He looked at the ICS kernel and noticed chris41g changed some stuff and ssuspected that that's why CM9 wasnt working for me.
He suggested i just do CM10.
i'll post with my success or failure
Thanks for the reply!
Related
SOLVED
Big thanks once again to vladthedog!
vladthedog said:
HEH! Sorry , I didn't even realize it was the same person! are you able to run
Code:
sudo adb kill-server
sudo adb start-server
adb devices
First line is killing the server
Second line re-starts the server as root (this is REQUIRED)
third line will tell you if all went well
I ran round and round with this initially. the server HAS to start as root. Problem is, you can start the server with NO error messages as someone other than root, and then you will think all is well.
Click to expand...
Click to collapse
/SOLVED - note, tried again to make sure and got "adb not recognized command" or something simlar, so i just did
Code:
sudo su
./adb kill-server
./adb start-server
than i could exit root and it worked still. had to be in the sdk/tools folder for it to work. seems i still haven't gotten ADB into the proper setting to run w/out being in the directory.
[email protected] ~/sdk/tools $ adb devices
List of devices attached
???????????? no permissions
[email protected] ~/sdk/tools $ adb get-state
unknown
[email protected] ~/sdk/tools $ adb remount
error: insufficient permissions for device
Click to expand...
Click to collapse
i have USB debugging enabled.
it does this on every rom i try. currently using latest cyanogen.
not sure how to go about getting 'permission' so i can run ADB commands to my phone.
OS is Linux Mint 9, tried it as SU/ROOT also, get the same thing.
Try another os/computer with your phone and see if you still get the error
http://forum.xda-developers.com/showthread.php?t=722854
there's a thread on someone having java issues with linux mint, but there are multiple posts (prior to figuring out it was java) on other things about getting adb running in linux. look for my post (the long one) because it sounds like you just need to get the device running as root.
vladthedog said:
http://forum.xda-developers.com/showthread.php?t=722854
there's a thread on someone having java issues with linux mint, but there are multiple posts (prior to figuring out it was java) on other things about getting adb running in linux. look for my post (the long one) because it sounds like you just need to get the device running as root.
Click to expand...
Click to collapse
yeah that was my thread =P
ADB worked on this phone fine for a while than just recently started saying No Permissions. I didn't delete anything, didn't adjust anything, all I've done is flash different roms on the phone.
S'pose i'll steal the wifes laptop and load ADB onto it and give it a go later tonight.
HEH! Sorry , I didn't even realize it was the same person! are you able to run
Code:
sudo adb kill-server
sudo adb start-server
adb devices
First line is killing the server
Second line re-starts the server as root (this is REQUIRED)
third line will tell you if all went well
I ran round and round with this initially. the server HAS to start as root. Problem is, you can start the server with NO error messages as someone other than root, and then you will think all is well.
yeah thats what i just did to see and it indeed worked, than came here to post i found it and read yours so now i feel fantastic =D
slowly still learning linux. i might switch from Mint to Ubuntu since it seems to have more made for it and more support out there for a newbie such as myself.
i should also add, i unplugged my usb wireless mouse thinking it may of interfered with it, but seeing that you posted what i tried i'll go that it wasn't it. just a note to anyone else.
Nrre said:
yeah thats what i just did to see and it indeed worked, than came here to post i found it and read yours so now i feel fantastic =D
slowly still learning linux. i might switch from Mint to Ubuntu since it seems to have more made for it and more support out there for a newbie such as myself.
i should also add, i unplugged my usb wireless mouse thinking it may of interfered with it, but seeing that you posted what i tried i'll go that it wasn't it. just a note to anyone else.
Click to expand...
Click to collapse
I'd recommend Ubuntu as well. Over the years I've goofed around with linux, but about 6 months ago I ended up taking the plunge and removing my windows partition and going full-on linux. I've found that ubuntu seems to have the most support out there for us newbies.
Now that I'm more confortable, i've installed a few different flavors of linux on my laptop, but always find myself coming back to ubuntu. again, its primarily because of the support issue when I screw something up
Yeah I am right now switching to Ubuntu since there is a ton more support out there. Loading up the flash drive with it right now.
Once again thanks for all the help.
vladthedog
Thanks that saved my life
Works on Pardus-Linux 2011.2-CONFIRMED
vladthedog said:
HEH! Sorry , I didn't even realize it was the same person! are you able to run
Code:
sudo adb kill-server
sudo adb start-server
adb devices
First line is killing the server
Second line re-starts the server as root (this is REQUIRED)
third line will tell you if all went well
I ran round and round with this initially. the server HAS to start as root. Problem is, you can start the server with NO error messages as someone other than root, and then you will think all is well.
Click to expand...
Click to collapse
Thanks for the post...I was racking my brain trying to get ADB working on Pardus-Linux. I used to be an Ubuntu guy and recently saw the light...LOL.
Thanks for the help.
thanks
thanks i got it WHOO hoo View attachment 1282945 srry i had to re-edit it for my device id
Thank you man ! This procedure also worked for me on Linux Mint !
I was about to try on windows, what a shame...
Hi all,
I have just received my Defy and I'd like to flash Cyanogenmod 7, I've flashed numerous roms to numerous phones in the past but I was always using Windows. I now use Linux (latest ubuntu derivative).
Is there a guide anywhere for flashing from a linux machine? My google-fu is pretty much pulling up a blank on the subject!
Thanks very much
Follow steps from FAQ for CM7, and just use this : http://forum.xda-developers.com/showthread.php?t=1076138 for flashing SBF and rooting,
It's my second post for the same question today
There's just two things to know:
1) You don't use RSD Lite to flash sbf files, you use this instead: http://blog.opticaldelusion.org/2011/02/sbfflash-updates.html
2) To root the phone you don't use SuperOneClick. Instead, get this DefyRoot pack: http://forum.xda-developers.com/showthread.php?t=1076138. Extract the pack, run the script using sudo.
And that's that. With the above differences in mind, you can follow the usual instructions: http://forum.xda-developers.com/showthread.php?t=1065798
Edit: Damn, bikerabhinav was faster
Thank you guys for the quick replies! time to give it a go
Sorry but you don't happen to know the link for installing adb on linux do you? presumably I need it hehe
I got the SDK and extracted to a directory of my choice, how on earth do I use it though, executing android in a terminal does not work, the rest is simple, can't believe I'm stuck on this part lol
I sorted that, I ran android and downloaded the development tools, I now have adb. I need to research more now, ran adb via terminal, then tried to run the rootdefy.sh but it told me adb wasn't started! see this is going to be a learning curve in Linux
You don't need the SDK, the RootDefy pack has everything necessary. I never installed the SDK.
ADB starts automatically if it isn't running yet. Did you run the script as sudo, like I told you? If not, there can be various problems. It's not necessary to run it with sudo if there's an udev rule for the phone. The script attempts to write one, but I'm not sure if it still works with the latest udev versions.
So let's do it manually:
- unplug the phone
- create a /etc/udev/rules.d/51-android.rules file containing this:
Code:
ATTRS{idVendor}=="22b8", MODE="0666"
- now reload udev:
Code:
sudo udevadm control --reload-rules
- just to be sure, kill all previous adb instances:
Code:
sudo pkill adb
- now plug the phone in and run the script again; with or without sudo, it shouldn't make a difference anymore
Thanks very much, all done and dusted now
It was almost exactly this time last year that I got my first Android device. I had absolutely no development experience whatsoever, so if anybody told me that I'd make a Cyanogenmod 7 Gingerbread ROM for the Kindle Fire in 11 months from that time, I would've thought they were crazy.
Android is the easiest to build on Linux, primarily Ubuntu. This guide is designed around building on Ubuntu as well. The first thing you need to build from source is to actually get the source. For Cyanogenmod 9 (Ice Cream Sandwich) you'll have to pull from the Cyanogenmod repository. You'll also have to download a few packages for Linux like Java, and they will have to be put in a PATH folder. In the guide here (which is meant to build CM7 for the Droid X) it's identical for the Kindle Fire. You can follow that guide up until you do this command "cd ~/android/system/" The next step of that guide would pull the CM7 repository, but we want CM9 (ICS). Instead of pulling Gingerbread, you'll want to pull ICS copy this:
repo init -u git://github.com/CyanogenMod/android.git -b ics
It may ask you for your name and email address. Once that's done, you can "repo sync -j16" and it will start downloading the source. This will take a very long time ~2 hours here, but once that's done, you can move on
Each device has its own device configuration and vendor files for building. Luckily for you, I've already setup the necessary stuff to get ICS to build for the Fire. You can download my source from my github here https://github.com/jackpotclavin You'll have to download the ICS-Kindle-Fire-Device and ICS-Kindle-Fire-Vendor files and place them in specific spots. For the vendor files, they go into /android/system/vendor/amazon/otter
You'll have to make the amazon and otter folders, but the vendor files should go in them so any random file, say, otter-vendor.mk will be placed so it's like this
/android/system/vendor/amazon/otter/otter-vendor.mk, with the proprietary folder inside /amazon/otter/.
It's almost the same with the device files. Once you download those, you place them into the /android/system/device/amazon/otter/ folder that you'll have to make, so any random file, say, system.prop goes would be located at /android/system/device/amazon/otter/system.prop
Once that's all done, you can download the prebuilts. For this you'll have to navigate into /android/system/vendor/cm and execute the get-prebuilts file. This will download a few files needed for building that will halt the build process if they're missing. Once those are done, it's building time. In the terminal, navigate to your /android/system/ folder, and type the command:
. build/envsetup.sh && brunch otter
That should be it! If somebody gets stuck, reply in this thread and I'll tell them where to go, and I'll update the post to help out happy building
Thanks for getting the code up! And the post I'm sure will be very useful for people to get started building.
JackpotClavin said:
It was almost exactly this time last year that I got my first Android device. I had absolutely no development experience whatsoever, so if anybody told me that I'd make a Cyanogenmod 7 Gingerbread ROM for the Kindle Fire in 11 months from that time, I would've thought they were crazy.
Android is the easiest to build on Linux, primarily Ubuntu. This guide is designed around building on Ubuntu as well. The first thing you need to build from source is to actually get the source. For Cyanogenmod 9 (Ice Cream Sandwich) you'll have to pull from the Cyanogenmod repository. You'll also have to download a few packages for Linux like Java, and they will have to be put in a PATH folder. In the guide here (which is meant to build CM7 for the Droid X) it's identical for the Kindle Fire. You can follow that guide up until you do this command "cd ~/android/system/" The next step of that guide would pull the CM7 repository, but we want CM9 (ICS). Instead of pulling Gingerbread, you'll want to pull ICS copy this:
repo init -u git://github.com/CyanogenMod/android.git -b ics
It may ask you for your name and email address. Once that's done, you can "repo sync -j16" and it will start downloading the source. This will take a very long time ~2 hours here, but once that's done, you can move on
Each device has its own device configuration and vendor files for building. Luckily for you, I've already setup the necessary stuff to get ICS to build for the Fire. You can download my source from my github here https://github.com/jackpotclavin You'll have to download the ICS-Kindle-Fire-Device and ICS-Kindle-Fire-Vendor files and place them in specific spots. For the vendor files, they go into /android/system/vendor/amazon/otter
You'll have to make the amazon and otter folders, but the vendor files should go in them so any random file, say, otter-vendor.mk will be placed so it's like this
/android/system/vendor/amazon/otter/otter-vendor.mk, with the proprietary folder inside /amazon/otter/.
It's almost the same with the device files. Once you download those, you place them into the /android/system/device/amazon/otter/ folder that you'll have to make, so any random file, say, system.prop goes would be located at /android/system/device/amazon/otter/system.prop
Once that's all done, you can download the prebuilts. For this you'll have to navigate into /android/system/vendor/cm and execute the get-prebuilts file. This will download a few files needed for building that will halt the build process if they're missing. Once those are done, it's building time. In the terminal, navigate to your /android/system/ folder, and type the command:
. build/envsetup.sh && brunch otter
That should be it! If somebody gets stuck, reply in this thread and I'll tell them where to go, and I'll update the post to help out happy building
Click to expand...
Click to collapse
(Place holder for later)
Thanks for this post, hoping to start my first aneroid programming contribution soon. This should help get me started. I am assuming though we still need to build drivers to get all the hardware working right? Unless. We can somehow rip drivers from the stock kindle and edit them. Any guide on that type of work, or examples to get started?
Kewl. Going to try this tonight.
Sent from my Kindle Fire using Tapatalk
could you do something like this https://gist.github.com/908477 or maby make a extract-files.sh that pulls the proprietary files from the device please? or would doing a git clone https://github.com/JackpotClavin/ICS-Kindle-Fire-Vendor.git set everything up to build?
Yeah sure I'll do that. Right now the the prop files in the vendor folder come from 6.2.1 so there won't be any new files or features you're missing out on
So yeah, cloning the vendor files will get you same files, but once amazon releases a new revision it will be needed so I'll get on that
Sent from my Galaxy Nexus using XDA App
excited to see this I have a lot of catching up to do, but I'll be of what help I can to this project...
I've tried to sync that repo twice now and it's failed both times. I have successfully synced the CM7 repo in another directory so I'm pretty sure my computer is set up correctly.
It goes for about and hour and then stops with an error. Said something like "unable to fetch objects" or something. So, I just did repo sync again and it errored out almost immediately.
I deleted the source directory and tried again but failed in the same spot. Any ideas?
teookie said:
I've tried to sync that repo twice now and it's failed both times. I have successfully synced the CM7 repo in another directory so I'm pretty sure my computer is set up correctly.
It goes for about and hour and then stops with an error. Said something like "unable to fetch objects" or something. So, I just did repo sync again and it errored out almost immediately.
I deleted the source directory and tried again but failed in the same spot. Any ideas?
Click to expand...
Click to collapse
Yes, I had the same error last night and again early this morning. Will try it later to see if it was a temporary server or network issue.
It's not an issue with your setup. Google has reported some syncing issues for some including myself (took me over 20 times yesterday to sync)
Sent from my Galaxy Nexus using XDA App
Just curious.. since we all use the same exact hardware why not just 1 person build it and post the rom? Or is there something special that needs to be done?
So I feel like a tard. I am trying to setup my copy of ubuntu so I can hopefully learn some devving skills. But when i try and install this stuff I get errors.
git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool
You are typing "sudo apt-get install" in front of that, right?
teookie said:
You are typing "sudo apt-get install" in front of that, right?
Click to expand...
Click to collapse
Yea, and it says it can't find some of the packages. I mean i don't think I am that bad at linux, but this is just annoying that there is stuff not working.
thrasherht said:
So I feel like a tard. I am trying to setup my copy of ubuntu so I can hopefully learn some devving skills. But when i try and install this stuff I get errors.
git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool
Click to expand...
Click to collapse
It's probably java causing the problem. Oracle changed the license and ubuntu can't distribute it anymore. There might be a ppa, but if not you will need to get it from oracle.
ttabbal said:
It's probably java causing the problem. Oracle changed the license and ubuntu can't distribute it anymore. There might be a ppa, but if not you will need to get it from oracle.
Click to expand...
Click to collapse
So how am I suppose to get java jdk installed? I am at a loss. I downloaded the tar, but I didn't understand what they wanted me to do from the instructions on the oracle website.
Code:
$ sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
$ sudo apt-get update
$ sudo apt-get install sun-java6-jdk
I set mine up with this guide:
http://source.android.com/source/initializing.html
teookie said:
Code:
$ sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
$ sudo apt-get update
$ sudo apt-get install sun-java6-jdk
I set mine up with this guide:
http://source.android.com/source/initializing.html
Click to expand...
Click to collapse
thanks man.
Icetech3 said:
Just curious.. since we all use the same exact hardware why not just 1 person build it and post the rom? Or is there something special that needs to be done?
Click to expand...
Click to collapse
This is Android Development, I'm assuming it's intended as a 'how to get started' guide for aspiring Android Devs.
Icetech3 said:
Just curious.. since we all use the same exact hardware why not just 1 person build it and post the rom? Or is there something special that needs to be done?
Click to expand...
Click to collapse
It doesn't "need" to be done but some of us like doing it ourselves IF possible. Honestly your statement comes off as "I'm lazy" but I'm sure you just don't have time. Besides the more people you teach the stronger the development will become. You want more ROMs don't you?
-----------------------------------
I found the information on the following page very useful if your running Ubuntu 11.10 like I am.
http://mjanja.co.ke/2011/11/building-android-4-0-on-ubuntu-11-10/
-----------------------------------
I'm hoping to modify the source so no matter what device I compile for they will all have the same look. That will be sweet.
Thanks OP I love posts like this and hope you can add more useful information in the future. I used to do these "how to"s on the HTC Touch Pro before I actually started modding entire ROMs.
I have been having trouble trying to extract my htc desire(cm7.1) Proprietary Files. i am no expert on ubuntu and wanted to have a go at compiling a cyanogenmod rom.
My problem is i have adb to recognise my device but im having trouble to get the './extract-files.sh' command to work .
i have uses this guide to help me set up adb : http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
And following this guide to compile cyanogenmod: http://wiki.cyanogenmod.com/wiki/HTC_Desire_(GSM):_Compile_CyanogenMod_(Linux)
Heres a screenshot of the problem i get when i try to excute this command and try get extract the Proprietary Files.
Any tips or advice how to get this working ?
Hi!
i assume you didnt setup the path to adb in bashrc, as you use adb only in the folder where it is by ./adb... i think the script needs the adb path setup to run. i am not sure though
you could try resyncing the repo too.
Droidzone is right, how could i have missed that. maybe the path just doesnt exist. it exists only after the work tree is synced completely, and the repo is quite unstable. try again
Isn't it quite obvious that you have typed the path wrong? re check the path and type it correctly. You're still executing it from your adb directory. Don't just copy and paste commands. Think, and modify them according to the situation, and error messages.
Thanks guys for the help. Really appreciate it.
Sent from my HTC Desire using XDA App
I've been wanting to try an compile Android for myself to see how it's done, even though Slimroms officially supports my device..
Only problem for now though, is I've successfully compiled the ROM and everything but after I flash it, it won't boot.
I get stuck at the Slimkat splash screen. The boot animation doesn't start. Adb can recognize the device being connected. I haven't tried any adb commands other than adb devices. The LED doesn't come on like it's supposed to while booting. While the phone is connected to a computer, you can't look at the files on it while it's in this state.
(my device actually is a d2can but, it's pretty much the same as a d2att)
The ROM is supposed to work for all of the lte variants of the siii
Here are the commands I have used to compile it after installing java, bison and some other stuff... Ubuntu 14 LTS
mkdir ~/slimkat/
mkdir ~/slimkat/androidsys/
mkdir ~/slimkat/bin/
cd ~/slimkat/androidsys/
repo init -u git://github.com/SlimRoms/platform_manifest.git -b kk4.4-caf
repo sync
. build/envsetup.sh
lunch slim_d2lte-userdebug (I also tried brunch d2lte userdebug)
make -j2 bacon
Update: I fixed it. Just needed to add some files from theloonybin
https:// github.com/TheLoonyBin/proprietary_vendor_samsung
Arunscape said:
Update: I fixed it. Just needed to add some files from theloonybin
https:// github.com/TheLoonyBin/proprietary_vendor_samsung
Click to expand...
Click to collapse
can you be more clear how you add TheloonyBin ???
is there a command line for terminal or i just copy paste from the link ?
i have left msg in slim forums as well but for different problem.
S03iT said:
can you be more clear how you add TheloonyBin ???
is there a command line for terminal or i just copy paste from the link ?
i have left msg in slim forums as well but for different problem.
Click to expand...
Click to collapse
Git clone (put the url pf theloonybin)
Then it will dowload the files in a folder called.proprietary_vendor_manufacturer
Copy the folder.of your device into ~/source/vendor/manufacturer