Hello guys as a developer when we make a rom, we have alot of requests from people which is fine and good. However, it comes to a point where we have so many requests for things, which we do not have time for in our free time. You have to remember we develop in our free time, and it is not a full time job, it is something we enjoy to do. Developers do expect requests, but not constantly, i will try to add features when people request it, but as explained above some of us, physically do not have the time, but some members annoy you by sending the same messages over and over again so the aim of this thread is:
If the Developers cannot do it, for whatever reason you should try it your self, and not just annoy them about it!
Now before we start there are things I want you to consider, before starting:
Code:
#include
*
* Your warranty is now void.
*By you using my Mods, Roms etc...
* I am not responsible for bricked devices, or dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Do not Start a thread with upcoming, or WIP because it is a waste of space, only post it when it is ready.
If you don't plan on continuing development, do not post it!
Do not steal other peoples work, ask them first, if they say no, build your own from a RUU or from source.
You can ask for help from other Developers, but do not annoy them over the issue they will help in their own time
Now the main things are out of the way, just one more thing if you are using lets say my ReVoluTioN RoM as a base if you just place a theme over it, and say it is your work it ISN'T! If you are just going to do that make a new theme thread instead, that way you will be credited, however, if you are adding extra code and your OWN custom HTC apps, or whatever that is maybe then yes it is worth making a new rom thread,ONLY IF IT IS YOUR WORK at implementing such code or new features.
ALSO if you are using a Existing rom as a base, give the developer credit for that and a link to their profile, to make sure you appreciate their work!
Now Onto the Tutorial:
In this guide, or new RoM builders it is a good idea to use an android rom kitchen called dsixda's Android Kitchen it is Compatible with Windows, Linux and Mac OS X.
Just a note about this kitchen:
The kitchen will not automatically turn you into a developer. A developer is someone who writes code or builds something from the ground up and understands exactly what goes on behind the scenes. The kitchen hides all that and puts a user-friendly interface above it. However, this may be the push that gets you into development in the future.
A little bit of prior UNIX command-line knowledge would be useful to get started with the kitchen, but the help guides should be enough for a newbie. Knowledge of command lines is always important if you ever want to get involved in Android or development.
However, just as a reference this is what the user interface looks like:
Main Menu:
1. Set up working folder from ROM
2. Add root permissions
3. Add BusyBox
4. Disable boot screen sounds
5. Add wireless tethering
6. Zipalign all *.apk files to optimize RAM usage
7. Change wipe status of ROM
8. Change name of ROM
9. Check update-script for errors
10. Show working folder information
Advanced Options
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add /data/app functionality
14 - Add Nano text editor + sysro/sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Tools for boot image (unpack/re-pack/etc.)
21 - Unpack data.img
22 - Sign APK or ZIP file(s)
23 - Convert update-script or updater-script
24 - Miscellaneous optins / Plugin scripts
99. Build ROM from working folder
00. About/Update kitchen
0. Exit
Click to expand...
Click to collapse
In order to make the kitchen work you will need to be running one of the following operating systems:
Windows, this can be from Windows XP all the Way up to Windows 8
Linux/Unix, based system I use ubuntu 11.04 but 12.10 is good too
Mac/OSX, however it is recommended 10.4 or above.
First of all you need to download the kitchen from here: LINK
Once you have downloaded it follow the operating system guide of your choice below:
Windows, XP, 7 and 8:
There are currently three choices for windows users these include:
Cygwin, this is a UNIX command line environment for windows
Virtual Machine, this is a good choice but you need a powerful system, with a fast CPU and lots of RAM!
Use the Ubuntu WUBI installer, this basically creates a installation of ubuntu inside windows, and can be easily uninstalled.
WINDOWS OPTION 1: CYGWIN:
I currently use this option for my Rom compiling, but this is due to the fact I have a 2nd Gen Core i3, and 8GB of RAM if your CPU is not very fast I recommend the third option!
Lets get started then...
Fist of all download the Java JRE for windows, it is recommended you use this link.
Secondly, download the cygwin binaries from here.
Below you will find the additional steps required to get it working properly on your windows based system
Russell664's guide to getting cywin working for HTC Desire C
First of all run the downloaded Cygwin" setup.exe" you downloaded in the last step, but be sure to select the default installation paths, which are:
Install from the internet, to download required packages
install to C:\cygwin, to make it easy to access
Once that is done you will be greeted with the "select packages" screen, from there go to the search box and look for the following packages:
gcc, this is found under the "devel" section to select it click the + icon on the section it is found in. After this find this single package "IT HAS TO HAVE THE EXACT NAME OF gcc NOTHING ELSE! once you have found it click it and press "Skip" after to select more packages.
Once the above is done you will need to search for these packages:
perl, this is found under the section of "Interpreters"
cpio, this is found under the section of "Utils"
util-linux, this is found under the section of "Utils"
ncurses, this is found under the section of "Utils"
zip, this is found under the section of "Archive"
unzip, this is found uder the section of "Archive"
wget, this is found under the section of "Web"
Once this is done click next to begin downloading the required packages, this may take some time to do this.
When everything is downloaded, and installation had completed, there will be a new cygwin desktop icon, once this is clicked a linux terminal will be displayed.
Once this terminal is displayed, we need to next configure "java" do do this follow these simple steps:
First of all type "java" (do it without the quotes) if the terminal says "command not found" go on the the next step. However if it dooes not say that skip these following steps for setting up java
To fix the no command found follow these steps:
First, make a backup of your .bash_profile file in case you make a mistake later in this procedure.
Enter the following in the terminal:
cp .bash_profile .bash_profile.backup
Next, find out where your java.exe file is and run the appropriate command to add it to your Cygwin path.
For example, my java.exe is found under C:\Program Files\Java\jre7\bin, so I had to type:
echo "PATH=/cygdrive/c/Program\ Files/Java/jre7/bin:\${PATH}" >> .bash_profile
Modify the command above so that it matches the actual path to your installed Java.
Remember to add a "\" character before any spaces in your path, as shown above.
Type the following so that the file gets loaded (you only need to do this once):
source .bash_profile
There should not be any errors displayed if successful.
(Otherwise, if you made an error in the .bash_profile file, restore your backup by typing: cp .bash_profile.backup .bash_profile, and then try the procedure again)
If done correctly, then when you type 'java' it should display some help information.
Once this is finished you are now setup to use the kitchen on your Windows based computer!
Click to expand...
Click to collapse
WINDOWS OPTION 2: VIRTUAL MACHINE:
Before considering this option for building Roms in this environment reads the Pros and cons first.
Advantages of using virtual box:
The size of the installation doesn't have to be predetermined. It can be a dynamically resized virtual hard drive.
You do not need to reboot in order to switch between Ubuntu and Windows.
The virtual machine will use your Windows internet connection, so you don't have to worry about Ubuntu not detecting your wireless card, if you have one.
The virtual machine will set up its own video configuration, so you don't have to worry about installing proprietary graphics drivers to get a reasonable screen resolution.
You always have Windows to fall back on in case there are any problems. All you have to do is press the right Control key instead of rebooting your entire computer.
For troubleshooting purposes, you can easily take screenshots of any part of Ubuntu (including the boot menu or the login screen).
It's low commitment. If you later decide you don't like Ubuntu, all you have to do is delete the virtual hard drive and uninstall VirtualBox.
Disadvantages of using virtual box:
In order to get any kind of decent performance, you need at least 512 MB of RAM, because you are running an entire operating system (Ubuntu) inside another entire operating system (Windows). The more memory, the better. I would recommend at least 1 GB of RAM.
Even though the low commitment factor can seem like an advantage at first, if you later decide you want to switch to Ubuntu and ditch Windows completely, you cannot simply delete your Windows partition. You would have to find some way to migrate out your settings from the virtual machine and then install Ubuntu over Windows outside the virtual machine.
Every time you want to use Ubuntu, you have to wait for two boot times (the time it takes to boot Windows, and then the time it takes to boot Ubuntu within Windows).
If you still wish to use the virtual box route follow these steps to get it installed:
Installation of virtual box
The first thing you have to do is obtain VirtualBox. First of all visit the VirtualBox website's download page and install it the same way you would any normal Windows program.
Once Virtualbox is installed, launch it from the windows start menu, after this click New to create a new virtual machine. Once the wizard comes up press the next button as seen below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can call the machine whatever you want. If you're installing Ubuntu, it makes sense to call it Ubuntu, I guess. You should also specify that the operating system is Linux.
VirtualBox will try to guess how much of your memory (RAM) to use for the virtual machine. If you have 1 GB or less of RAM, I would advise you stick with the recommendation. If, however, you have over 1 GB, about a quarter your RAM or less should be fine. For example, if you have 2 GB of RAM, 512 MB is fine to allocate. If you have 4 GB of RAM, 1 GB is fine to allocate. If you have no idea what RAM is or how much of it you have, just press next.
If this is your first time using VirtualBox (which it probably is if you need a tutorial on how to use it), then you do want to Create new hard disk and then click Next.
Click next at this section, don't change anything!
A dynamically expanding virtual hard drive is the best option, because it'll take up only what you actually use. I have come upon weird situations, though, when installing new software in a virtualized Ubuntu, in which the virtual hard drive just fills up instead of expanding. So I would actually recommend picking a Fixed-size storage.
Ubuntu's default installation is less than 3 GB. If you plan on adding software or downloading large files in your virtualized Ubuntu, you should tack on some buffer.
Click Create and wait for the virtual hard drive to be created. This is actually just a very large file that lives inside of your Windows installation.
Then this will show up:
The next thing to do to make the (currently blank) virtual hard drive useful is to add the downloaded Ubuntu disk image (.iso) boot on your virtual machine. Click on Settings and Storage. Then, under CD/DVD Device, next to Empty, you'll see a little folder icon. Click that.
Select the Ubuntu .iso you downloaded earlier.
Once the image is selected, click ok.
You may get a bunch of random warnings/instructions about how to operate the guest operating system within VirtualBox. Read those, and then you may also want to mark not to see those again.
Wait for Ubuntu to boot up.
Once it's started up, just follow the regular installation procedure as if you were installing Ubuntu on a real hard drive (instead of a virtual one).
Afterwards, in order to use your virtualized installation (instead of continually booting the live CD), double-check that the CD/DVD Device entry is Empty again.
Now you have ubuntu installed on virtualbox! Now on the the next part, making the kitchen work.
WINDOWS OPTION 3: WUBI INSTALLER:
Before you start this download the ubuntu iso image from the website, and burn it to a cd!
You may want Linux but think Virtual Box is too much effort to install, or it runs too slow for you, then you can try the 'Wubi' installer from Windows. This method will install Ubuntu Linux inside a file in your Windows operating system and will boot from it.
Use this method only as a last resort, as it will modify your PC's boot loader and may also require some hunting for video drivers if you're not lucky. The benefit to this method is that it runs the kitchen super fast. The downside is that setting it up may require some technical expertise and Linux experience! If it's not working out for you, just go back to Windows and run the Wubi installer again to uninstall.
You can find lots more info about Wubi in YouTube and Google search. In the meantime, here is a summary of the required instructions:
First, download and install the Wubi installer. A good size to allocate for Ubuntu would be 20 GB (this is for all your roms and updates)
When it finishes installing, the PC will reboot.
Select Ubuntu from the boot selection menu.
Notes:
NOTE: If the screen remains blank afterwards and never shows the login screen, then you have a video driver issue. You will need to reboot, and then at the Ubuntu boot options, press 'e' to edit the command line. To force the generic video drivers you will need to add something like this: nomodeset (Just Google it)
When you arrive at the desktop, configure your Wi-Fi connection by clicking on the seashell-shaped icon at the top right section of the screen.
Follow the instructions in the next section of this FAQ ("Ubuntu Linux") for installing Java. That should be all you need to do. I really hope this helped you out.
NOTE: If you had to do the video workaround earlier on, then you'll need to edit /etc/default/grub and change the appropriate lines so that it always boots up in this mode and so you won't need to edit it every time in the boot menu. i.e. Open up an xterm and then type sudo vi /etc/default/grub, modify the file, then type sudo update-grub. Again, Google is your friend.
Ubuntu 11.04 to 12.10:
UBUNTU NATIVE INSTALL:
Before you follow any of these step mentioned in this ubuntu section, you NEED to have it installed either on a physical drive (Partition) or inside a virtual machine. If you do not meet the requirements you need to first install ubuntu, which will be mentioned above this post.
Okay these next steps of setting up the running requirements for the kitchen on linux are very easy compared to the windows setup, the required steps are:
First open up the terminal windows, the buttons to quickly do this are:
Code:
CTRL + ALT + T
If you are using the 64-bit version of ubuntu, type the following into your terminal:
Code:
sudo apt-get install ia32-libs
Now if you go onto the ubuntu market place, a shortcut is found on the sidebar.
Once you are in to market, in the search bar type "Java"
There will be many choices which come up, but you need to install the package name of:
Code:
OpenJDK Java Runtime
This option is usually displayed at the top of the search result.
Once the Java has installed, type "java -version" If installed correctly it will bring back some information into the terminal.
Code:
java -version
If you are using Ubuntu in a virtual machine, you NEED to follow these extra steps to complete installation.
This thread will be updated as soon as possible, i need to get other stuff done so hang tight.
Configuring DSiXDA's kitchen
Just to note the HTC Desire C is not compatible with kitchen, there is a work around that works perfectly so follow the steps further down the thread, these are the officially supported devices for a reference:
Remember this is a reference, and is extracted from DSiXDAs thread itself.
Code:
Acer Liquid
Dell Streak 7
HTC Amaze 4G
HTC Aria / Liberty
HTC Desire
HTC Desire HD / Inspire 4G
HTC Desire S
HTC Desire Z / Vision / T-Mobile G2
HTC Dream / G1
HTC Droid DNA
HTC Droid Eris
HTC Evo 3D
HTC Evo 4G
HTC Evo 4G LTE
HTC Evo View 4G (untested)
HTC Evo Shift 4G
HTC Flyer (untested)
HTC HD2
- Use NAND ROM method (Please follow this thread for details)
HTC Hero / G2 Touch
HTC Incredible
HTC Incredible 2
HTC Incredible S
HTC Legend
HTC Magic / myTouch 3G
HTC myTouch 3G Slide
HTC myTouch 4G / Glacier
HTC Nexus One
HTC One S
HTC One X
HTC One X+ (AT&T and International versions)
HTC One XL
HTC One V (including CDMA version)
HTC Rezound
HTC Sensation
HTC Tattoo / Click
HTC Thunderbolt
HTC Wildfire / Buzz
HTC Wildfire S
Huawei Ideos X6
- Please follow this thread for details
Huawei U8100/U8110/U8120/U8150/U8160/U8180/U8650
Huawei U8220 / T-Mobile Pulse
LG Ally
LG GT540 Optimus
LG Nexus 4 (mako)
LG Optimus 2X (P990)
LG Optimus Black
- Please follow this thread for details
LG Optimus G2X (P999)
LG P500
- Please follow this thread for details
LG Shine Plus
LG Vortex
Micromax A60
Motorola Atrix (unconfirmed)
Motorola CLIQ / CLIQ XT
Motorola Droid
Motorola Droid Bionic
- Please follow this thread for details
Motorola Milestone (unconfirmed)
- You may need to remove the boot.img before building
Samsung Galaxy Ace 2 - GT-I8160(L/P)
Samsung Galaxy Mini
Samsung Galaxy Nexus (untested, 'maguro' and 'toro' versions only)
Samsung Galaxy Note
- GT-N7000 - please follow this thread for details
- SGH-I717 - Please follow this thread for details
Samsung Galaxy Note 2
- Supported for:
-- Sprint variants - SPH-L900 - Please follow this guide
-- T-Mobile variants - SGH-T889(V) - Please follow this guide
-- Verizon variants - SCH-I605
(unconfirmed - see this equivalent guide)
-- International variants - GT-N7100/N7105(T)/N7108
(unconfirmed - see this equivalent guide)
-- AT&T/Rogers/Bell/Telus variants - SGH-I317(M)
(unconfirmed - see this equivalent guide)
-- US Cellular variants - SCH-R950
(unconfirmed - see this equivalent guide)
Samsung Galaxy R GT-I9103
Samsung Galaxy S (GT-I9000 and most variants)
- Please follow this thread for details
Samsung Galaxy S Plus (GT-I9001)
- Please follow this thread for details
Samsung Galaxy S2
- Supported for:
-- GT-I9100 and Exynos CPU variants - Please follow this thread for details
-- Qualcomm/LTE variants
(AT&T Skyrocket, Rogers, Telus, T-Mobile, Bell HD LTE SGH-I757M,
Telstra GT-I9210T)
- Please follow this thread for details
Samsung Galaxy S3
- Supported for:
-- T-Mobile/Mobilicity/Wind variants: SGH-T999(V) - Click here for a guide
-- AT&T/Rogers/Bell/Telus variants: SGH-I747(M) - Click here for a guide
-- Verizon variants: SCH-I535, SCH-R530U - Click here for a guide
-- Sprint variants: SPH-L710, SCH-L710 - Click here for a guide
-- International variants: GT-I9300(T) - Click here for a guide
-- International LTE variants: GT-I9305(T) - Click here for a guide
-- Korean variants: SHV-E210K/L/S and SHW-M440S (unconfirmed)
Samsung Galaxy W (GT-I8150)
- Please follow this thread for details
Samsung Nexus S / Nexus S 4G
Sony Ericsson Xperia 2010 devices (X10 / X10 Mini / X10 Mini Pro)
- Can only build ROM without boot.img (please follow this thread for details)
Sony Xperia 2011-12 devices, specifically:
- TX, P, U, Sola
- Active, Arc, Arc S, Mini, Mini Pro, Neo, Neo V, Neo L,
Play, Ray (follow steps below):
- Can only build ROM without boot.img
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
- OR If using Nandroid backups: Rename system.yaffs2.img to system.img
- Use this system.img in kitchen's original_update folder
- WARNING - If using a ROM made from system.sin (not Nandroid), it
is recommended to flash from the temporary (fastboot) Clockwork
Recovery, rather than the regular Clockwork Recovery, otherwise
device may not boot (possibly because custom recovery files in
system folder are not added to ROM? e.g. recovery.tar).
ZTE Blade / Orange San Francisco
Now for the compatibility fix details
There are one of two ways you can do this, these being:
Do the file editing manually, I will explain it step by step for you.
Or be lazy and use my provided file at the bottom if this post.
If you choose to learn a little bit more from this tutorial, you may want to go the manual route. That is all well and good, however, follow these instructions precisely, or you could cause a lot of problems with your phone. If you don't feel safe doing it manually, use my file below to make sure that does not happen.
Here we go...
Option 1:
By this step your kitchen should be downloaded, and confirmed that it does in fact start up, if it does your set to go and follow these remaining steps.
In your kitchen directory, you will find a tools folder you want to Click that and then the Edify_defs folder after that, the file structure should look like this:
Code:
C:\cygwin\home\yourusername\Kitchen\tools\edify_defs
This is on a Windows based system.
Code:
\home\yourusername\Kitchen\tools\edify_defs
This would be on a linux based system, it will be very similar.
Once you are in this folder save a file called "Golfu". (You can do this by saving the file as a blank text document, but save it as *file insted of .txt)
Get a recovery.img (Yes the one used for flashing your recovery, or a stock one) And save it in the "Original_update" folder, the file structure should look like so:
Code:
C:\cygwin\home\yourusername\Kitchen\Original_update
This is on a Windows based system.
Code:
\home\yourusername\Kitchen\Orginal_update
This would be on a linux based system, it will be very similar.
Once you have done that follow these menus through the kitchen:
Code:
Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder.
Once this is done, once again go to the Orginal_update folder and you will find the extracted recovery.img, open it's ramdisk folder and Follow this file structure:
Code:
/system/etc/recovery.fstab or /etc/recovery.fstab
After you have found this file open it with a text editor. (Due to this being code, you will want it in a neat fashion, this is why I recommend NOTEPAD++ for windows user, linux user you are fine with the standard one included)
When looking at the code you are looking for these lines:
Code:
sys_mnt=\/dev\/block\/[B]mmcblk0p25[/B]
cache_mnt=???
data_mnt=???
sdcard_mnt=???
However you are only really looking for the system block number, you can add data etc later on manually though updater scripts it is much easier. Remember you are looking for this line highlighted in bold, you can just copy that number down, it is the same for every HTC Desire C.
The last step is too add these lines you have found, to the "golfu" file you created, basically you want it to look exactly ike the code below, copy and paste it if you wish:
Code:
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p25
cache_mnt=???
data_mnt=???
sdcard_mnt=???
Now the configuration is now done of the kitchen, now you can move onto how to build your Rom from a RUU, or from an exsting rom such as Revolution, or nameless.
Option 2:
As said in option 1 you need to make sure you Rom kitchen starts up and shows the menu, this means it is working. If it does not do that you have done something wrong.
Basically you need to download this attached file, unzip it and place it in the following directories. (Make sure you read to notes at the end of the directory code, so you know what operating system it is aimed at)
Move the file here:
Code:
C:\cygwin\home\yourusername\Kitchen\tools\edify_defs\thefileyoudownloaded
This is on a Windows based system.
Code:
\home\yourusername\Kitchen\tools\edify_defs\thefileyoudownloaded
This would be on a linux based system, it will be very similar.
That is basically it, now you need to read below, on how to actually build your roms.
Reserved for FAQ
Great Russell! I'm glad to see a guide of this nature within our forum, it will certainly help to promote further development on our device. There are a lot of guides available concerning this topic, however none that have anything specific to the Desire C, I look forward to seeing the completed guide!
First post updated, nearly finished, the windows section is finished, the ubuntu section needs a little bit of work. However this guide is ready to use for people who plan on using windows.
Good luck guys.
russell664 said:
First post updated, nearly finished, the windows section is finished, the ubuntu section needs a little bit of work. However this guide is ready to use for people who plan on using windows.
Good luck guys.
Click to expand...
Click to collapse
Thankyou russell I plan on following this ...once I get the time . I'm out of thanks again this morning which is weird as I havn't used any today . I will spam you later :good:
Thanks Rich
The thread should be complete tomorrow, with the ubuntu section.
Sent from my HTC Desire C using xda premium
I can't get Ubuntu installed, the installation freezes at about 75%. Tried using Wubi and real installation on a partition.
I suggest you to use Ubuntu on dual boot. Boot Ubuntu from stick.
I know but that is just a demo
Sent from my HTC Desire C using xda app-developers app
You can install it from the demo, let it load to the desktop. There is a icon saying install ubuntu on the desktop, click it and install ubuntu. You can do this from a USB stick or cd
Good luck.
Sent from my HTC Desire C using xda premium
That's what I did, installation doesn't complete but freezes after about 75 per cent
Sent from my HTC Desire C using xda app-developers app
Could you take a picture of the screen?
Are you installing on a VM, and if so how much RAM have you allocated to you VM, and how much does your system have?
Sent from my HTC Desire C using xda premium
Strange, okay if you are using a VM my recommendation is to use 2Gb of ram, if you have 4GB in your computer. However installing linux is still your best option. Now if ubuntu does not work for you, you can try linux mint. This already has java installed, and can run the kitchen out of the box, all you need to do is make it comparable with our phone.
The main thing what I think could be happening is lack of ram or possible corrupt image of ubuntu, try the linux mint approach and update us with your results mate.
Best of luck.
Sent from my HTC Desire C using xda premium
Not using a vm my computer wouldn't be able to run smoothly it's pretty crap
I'll re download the iso and try again, if that doesn't work ill try Linux mint
Sent from my HTC Desire C using xda app-developers app
update: still didn't work, downloading linux mint right now...
does anybody know a way to install that awesome looking unity interface on mint?
Use the version of ubuntu from this link http://forum.xda-developers.com/showthread.php?t=2152398
It already has most of the packages required for building a rom preinstalled
Unity awesome? never KDE is much better im my opinion.
Yes you can install it with the command:
Sudo apt-get update
Sudo apt-get ubuntu-desktop
That will install unity for you.
nikhil16242 said:
Use the version of ubuntu from this link http://forum.xda-developers.com/showthread.php?t=2152398
It already has most of the packages required for building a rom preinstalled
Click to expand...
Click to collapse
Staahp!!! xD
So many choices... my linux mint download only just completed and you posted that xD
will look at it later