I have made a build environment in VMWare. I have added all necessary programs to the Gnome menu. I spent a good 6 hours on making this and compressing this.
Before you use the VMWare image change RAM and CPU to your needings. I suggest at least 2GB RAM and 2 cores assigned for decent performance.
I have also enabled 3D acceleration for OpenGL developers or those who want to try making games.
Requirements
VMWare Player (FREE)
VMWare Workstation (optional, paid)
Features
- Everything is installed:
- Android SDK Tools
- Eclipse
- Android AOSP ready: tested with Jelly Bean
- CyanogenMod ready: tested with CyanogenMod 10 and later
- Developer links in Firefox to CyanogenMod and Android AOSP.
Downloads
One package
http://rapidgator.net/file/49386792/Android_Developer_Environment_1.7z.html
Splitted
http://rapidgator.net/file/49403760/Android_Developer_Environment_1.zip.001.html
http://rapidgator.net/file/49400833/Android_Developer_Environment_1.zip.002.html
FAQ
Can you upload on a mirror?
- No it takes too much time and bandwidth. I don't have the money to buy extra bandwidth.
Passwords?
- All passwords are: 'root'
Looks awesome! I just finished downloading it.. But whats the passwords? For the user anddev and root.
mattmannlt said:
Looks awesome! I just finished downloading it.. But whats the passwords? For the user anddev and root.
Click to expand...
Click to collapse
I would highly recommend each user and ESPECIALLY new users go through the process of setting up and configuring their own development environment. You will gain a lot of understanding on how Linux and thus Android operates by working with it yourself, and this really is important. This is great for a experienced dev who wants to have a backup of his own environment, but I think it's just adding one more crutch that the newbies really won't understand.
Password is 'root'
I thought this was a nice and obvious password to use. Sorry for letting you wait.
djjonastybe said:
Password is 'root'
I thought this was a nice and obvious password to use. Sorry for letting you wait.
Click to expand...
Click to collapse
aa
---------- Post added at 08:07 AM ---------- Previous post was at 08:01 AM ----------
Djj, was building cm10 in vmware are more stable then virtualbox? Tks
Sent from my LG-P990
orbital_71 said:
Djj, was building cm10 in vmware are more stable then virtualbox? Tks
Sent from my LG-P990
Click to expand...
Click to collapse
No. Just about the same. I use virtual box .
Sent from my Galaxy Nexus using xda premium
lithid-cm said:
No. Just about the same. I use virtual box .
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Lithid-cm, i am a beginner as i had install virtualbox with ubuntu 12.04 in it, but with 512m. I not rushing for building rom up just for mine knowledge and understand on building enviroment would that be fine? Tks
Sent from my LG-P990
orbital_71 said:
aa
---------- Post added at 08:07 AM ---------- Previous post was at 08:01 AM ----------
Djj, was building cm10 in vmware are more stable then virtualbox? Tks
Sent from my LG-P990
Click to expand...
Click to collapse
It's much more stable using VMWare. Many systems have trouble downloading the source code. Virtual Box gets the 'HTTPS ... not received' errors. Honestly I don't know how to say the error accurately because I simply skipped Virtual Box due to that issue
djjonastybe said:
It's much more stable using VMWare. Many systems have trouble downloading the source code. Virtual Box gets the 'HTTPS ... not received' errors. Honestly I don't know how to say the error accurately because I simply skipped Virtual Box due to that issue
Click to expand...
Click to collapse
Djj, here another question. i am a beginner if i set to only with 512m for vmware will that be fine as I not rushing for building rom up just for mine knowledge and understand on building enviroment would that be fine? Sorry can't download from rapidgator if u upload to mediafire u still have to pay? Tks
djjonastybe said:
It's much more stable using VMWare. Many systems have trouble downloading the source code. Virtual Box gets the 'HTTPS ... not received' errors. Honestly I don't know how to say the error accurately because I simply skipped Virtual Box due to that issue
Click to expand...
Click to collapse
These issues are simple configuration mishaps and can be fixed easily. Nat tends to do this, I use a bridged nic. There are also a few kernel values you modify to fix any "download errors". I have never experienced any issues like you are suggesting using virtual box.
Sent from my Galaxy Nexus using xda premium
orbital_71 said:
Lithid-cm, i am a beginner as i had install virtualbox with ubuntu 12.04 in it, but with 512m. I not rushing for building rom up just for mine knowledge and understand on building enviroment would that be fine? Tks
Sent from my LG-P990
Click to expand...
Click to collapse
I had issues building with less then 3 gig of memory. 512 might be too low. Might need at least 2 gig.
Sent from my Galaxy Nexus using xda premium
Those who want to install Sun Java JDK (Oracle) need to follow this tutorial:
http://forum.xda-developers.com/showthread.php?p=28793435#post28793435
Follow the Java part I made the guide some time ago
Kernel Source
Hi,
I'm new to android development.
I know that every ROM will have a Linux kernel, but where does this kernel come from?
I googled it, but I still can't figure it out.
I'll just take a wild guess.
Is it from
1. The source that you git from? (Ex: AOSP, CM10, AOKP)
2. The kernel of the Linux OS? (Ex: This VM's Linux kernel)
and by the way, am I able to change the kernel myself? (Ex: 2.6.35 to 3.0.8)
Thanks!
goldchang said:
Hi,
I'm new to android development.
I know that every ROM will have a Linux kernel, but where does this kernel come from?
I googled it, but I still can't figure it out.
I'll just take a wild guess.
Is it from
1. The source that you git from? (Ex: AOSP, CM10, AOKP)
2. The kernel of the Linux OS? (Ex: This VM's Linux kernel)
and by the way, am I able to change the kernel myself? (Ex: 2.6.35 to 3.0.8)
Thanks!
Click to expand...
Click to collapse
You get the kernel source from your device manufacturer.
goldchang said:
Hi,
I'm new to android development.
I know that every ROM will have a Linux kernel, but where does this kernel come from?
I googled it, but I still can't figure it out.
I'll just take a wild guess.
Is it from
1. The source that you git from? (Ex: AOSP, CM10, AOKP)
2. The kernel of the Linux OS? (Ex: This VM's Linux kernel)
and by the way, am I able to change the kernel myself? (Ex: 2.6.35 to 3.0.8)
Thanks!
Click to expand...
Click to collapse
lithid-cm said:
You get the kernel source from your device manufacturer.
Click to expand...
Click to collapse
Or port it from a similar device.
Will try this soom to decompile and compile the Settings.apk from Jelly Bean... Anyone any Tips? Please send me a PM.....
Hi,
can somebody else upload one package on a mirror or something ! because splitted ones are taking forever to download !
Thanks !
ShivangDave said:
Hi,
can somebody else upload one package on a mirror or something ! because splitted ones are taking forever to download !
Thanks !
Click to expand...
Click to collapse
Don't have a mirror, but why don't you just download a Linux ISO and set it up for yourself? Should be smaller downloads the whole way, everything will be up to date, and you'll get invaluable learning experience.:
thewadegeek said:
Don't have a mirror, but why don't you just download a Linux ISO and set it up for yourself? Should be smaller downloads the whole way, everything will be up to date, and you'll get invaluable learning experience.:
Click to expand...
Click to collapse
I have tried to setup the environment but many packages are missing...
EDIT: Downloaded splitted ones... corrupted !
hey guys, im good java programmer but i dont have any idea about android
so i was wondering what are the benefits of learning android developments?
, will it be easy since i'm good java programmmer?
if that idea is good then what android books do you guys recommend for me?
Related
So I had a go at this and it seems to have worked.... sort of, I expected an error or few . I'm surprised how well my HP Mini handled the source compile, even if it did take 6+ hours from start to finnish. Now I know all the documentation says 64bit is required for some of the build tools to compile JellyBean, but isn't there a way around this? Tomorrow I'll take another stab at it and post up the errors.
DNRDustin said:
So I had a go at this and it seems to have worked.... sort of, I expected an error or few . I'm surprised how well my HP Mini handled the source compile, even if it did take 6+ hours from start to finnish. Now I know all the documentation says 64bit is required for some of the build tools to compile JellyBean, but isn't there a way around this? Tomorrow I'll take another stab at it and post up the errors.
Click to expand...
Click to collapse
i doubt that it will work...just check the build packages for gb and jb you will know it for yourself
still pretty noob status
I'm new to all this so it all looks like a bunch of jibberish to me. But I want to learn, so I'm jumping in. Adding the repositories and DL'ing the tools isn't an option? If 64bit is required, why is 32bit included in the CM source tutorial?
DNRDustin said:
I'm new to all this so it all looks like a bunch of jibberish to me. But I want to learn, so I'm jumping in. Adding the repositories and DL'ing the tools isn't an option? If 64bit is required, why is 32bit included in the CM source tutorial?
Click to expand...
Click to collapse
which tutorial? can i have a source please
I think 32bit is just included because the guide was probably formatted from a template.
http://wiki.cyanogenmod.org/wiki/HTC_One_XL:_Compile_CyanogenMod_(Linux)
DNRDustin said:
I think 32bit is just included because the guide was probably formatted from a template.
http://wiki.cyanogenmod.org/wiki/HTC_One_XL:_Compile_CyanogenMod_(Linux)
Click to expand...
Click to collapse
they are 32 bit pacakges .. yes the guide is in the formatted template
Title says all. Comment with something under here if you have a GP 4.2. I'm making a ROM for it but, due to my network speed (slooooow), I want to know how many users will download it. Thanks in advance!
PS. If you know other users that have this Player tag their names into your reply!
I have one, but I've since replaced with with the 5 inch model. I still use it on occasion to test apps and things.
I have one, so does @SerkTheTurk @lets_zock and @ChaosChris
Sad that this is a very unsupported device (both by Samsung and developers)
No. I have not it. I leaved it to the samsung center with the latest hard brick. For now i only have a note 1 but i want to sell it to buy an iPhone 4 or a SGS 3.
Inviato dal mio GT-N7000 utilizzando Tapatalk
64kb said:
I have one, but I've since replaced with with the 5 inch model. I still use it on occasion to test apps and things.
Click to expand...
Click to collapse
As far as you have a monkey into your brain that needs ROMs to calm down itself...
drakonizer said:
I have one, so does @SerkTheTurk @lets_zock and @ChaosChris
Sad that this is a very unsupported device (both by Samsung and developers)
Click to expand...
Click to collapse
I saw... I will configure a VM with Mint 15 to (try to) develop a CM7/9 version starting from the work made by @SerkTheTurk...
HellPie said:
As far as you have a monkey into your brain that needs ROMs to calm down itself...
I saw... I will configure a VM with Mint 15 to (try to) develop a CM7/9 version starting from the work made by @SerkTheTurk...
Click to expand...
Click to collapse
I have one and I would help you if I could. But it's not that easy. My Player lies in my rom with dust on it..
lets_zock said:
I have one and I would help you if I could. But it's not that easy. My Player lies in my rom with dust on it..
Click to expand...
Click to collapse
I only have some questions:
1) Is it true that I need to have a 64 bit CPU? If yes, I have not, but in a VM is it possible to have it?...
2) What Linux OS is the best to get a fast compilation time? (My VM: 2Core, 1.5GB Ram, HDD USB 2.0 to host it (only used for the VM), 128GB of virtual HDD)
3) With Mint 15 64bit VirtualBox crashes on boot, is this a problem of the "64bit" version or is a problem of the small quantity of RAM?
I have it! It will be really, really, really great to have a new ROM, since we've got a few numbers of developers for this device. A CM7 or CM9 ROM, like u said u're going to try to do, would be really great for future developers and a future Jelly Bean ROM. ( Nowadays, I'm using ChaOS ROM v1 + S3 Modpack made by @ChaosChris )
HellPie said:
I only have some questions:
1) Is it true that I need to have a 64 bit CPU? If yes, I have not, but in a VM is it possible to have it?...
2) What Linux OS is the best to get a fast compilation time? (My VM: 2Core, 1.5GB Ram, HDD USB 2.0 to host it (only used for the VM), 128GB of virtual HDD)
3) With Mint 15 64bit VirtualBox crashes on boot, is this a problem of the "64bit" version or is a problem of the small quantity of RAM?
Click to expand...
Click to collapse
1)I believe you can build CM7 with a 32 bit OS (that requires only a 32bit processor) but for CM9 onwards you need a 64 bit version of Linux (which requires a 64 bit processor)
2)You can use Ubuntu 10.04 (as recommended on the official Android developers website) for maximum compatibility and less compilation errors.
3)Yup, you cant use 64 bit OS'es on 32 bit processors, neither with VMs nor by actually installing it on another partition.
drakonizer said:
1)I believe you can build CM7 with a 32 bit OS (that requires only a 32bit processor) but for CM9 onwards you need a 64 bit version of Linux (which requires a 64 bit processor)
2)You can use Ubuntu 10.04 (as recommended on the official Android developers website) for maximum compatibility and less compilation errors.
3)Yup, you cant use 64 bit OS'es on 32 bit processors, neither with VMs nor by actually installing it on another partition.
Click to expand...
Click to collapse
1) So for 3 or 4 years (I haven't enough money for a new pc and my parents will never buy another one only because "the cpu can work with the double number of bit in the same time" (Yes, my father were born with the "linux inside" signature, but with a 16/32bit brain))
2) Ok, I'll try
3) Damn!
4) With this post I can now post in the dev section! So when I'll fixed all bugs with current rom I will open a thread for it! Thanks!
Android Developers said:
For Gingerbread (2.3.x) and newer versions, including the master branch, a 64-bit environment is required.
Click to expand...
Click to collapse
So I cannot compile it... :'( Nooooooooo... :'( :'( :'(
I think you can compile cm7 with 32 bit Ubuntu because AFAIK, @SerkTheTurk has a 32 bit CPU (intel centrino) but he has compiled CM7 (though not booting ) successfully for our device...so you can try
Sent from my SGH-T499 using xda app-developers app
Ah. I will try. Thanks! For now with my rom I am at the same point of 3 days ago. Bootloop, bootloop and more bootloop. I think that I will restart from 0 adding one feature every flash and then when I will have enough features and stability I will relase it.
I have it, I love it and I heavily use it everyday... I hope this device can get more support, but it's wishful thinking...
HellPie said:
Ah. I will try. Thanks! For now with my rom I am at the same point of 3 days ago. Bootloop, bootloop and more bootloop. I think that I will restart from 0 adding one feature every flash and then when I will have enough features and stability I will relase it.
Click to expand...
Click to collapse
Great idea! Building a ROM in this way would be really useful to have more knowledge about what you're doing. This will help you to, if there is an error, find out exactly where it is, so you can fix it. Good thinking. Good look, maybe we finally got a sucessful CM7.
I am talking about my modded stock based rom... the cm one will wait because i need to fix some errors with the vm.
Inviato dal mio GT-N7000 utilizzando Tapatalk
lol Got it. Will you try to develop themes for your custom ROM?
Yes. But not now. I'll make themes after I have modded all the Rom because if I mod a part of the rom i need to mod all themes so when i end the modding-time i will start with all done and the theming process will be more faster.
Inviato dal mio GT-N7000 utilizzando Tapatalk
HellPie said:
Yes. But not now. I'll make themes after I have modded all the Rom because if I mod a part of the rom i need to mod all themes so when i end the modding-time i will start with all done and the theming process will be more faster.
Inviato dal mio GT-N7000 utilizzando Tapatalk
Click to expand...
Click to collapse
I can make themes for you if you want. I an currently working on a KitKat theme, and I've managed to do some statusbar mods like transparent mod, jb clock etc. I might release it for the stock XXLF1 ROM but I can do it for you too.
Thanks. I talked with [email protected]:-$ and now we are working toghether. But he has not got the player anymore so he only help me saying me what he tested and what not.
Inviato dal mio GT-N7000 utilizzando Tapatalk
I own one and I use it everyday! I rooted it but only have tried the stock rom. I want to try a custom rom. But don't know which one is the most stable or best
Sent from my YP-GI1 using xda app-developers app
So I'm using one of the kitkat roms and I can't seem to get USB OTG and USB charging to work at the same time? Is this just not possible? Or do I need to do something special? I bought one of the OTG Y cables that allows the hookup of a charger and a USB device and it's still no go, it'll show it's charging for a minute or so after a USB device is mounted but then the charging icon goes away?
Someone had mentioned to me that a custom kernel may be needed?
Yep you would need a custom kernel.
ThatFrigginAzn said:
Yep you would need a custom kernel.
Click to expand...
Click to collapse
Any documentation around on how to build this kernel to do what I need?
Hdale85 said:
Any documentation around on how to build this kernel to do what I need?
Click to expand...
Click to collapse
Look in my signature for a guide. For the specifics, you will need to find a kernel on github that has what you are looking for and port it to your build. My roll your own kernel guide will get you started. You will need a partition with Debian Linux to complete the guide. I suggest AntiX.
sleekmason said:
Look in my signature for a guide. For the specifics, you will need to find a kernel on github that has what you are looking for and port it to your build. My roll your own kernel guide will get you started. You will need a partition with Debian Linux to complete the guide. I suggest AntiX.
Click to expand...
Click to collapse
Can it be a kernel from another device? or does it need to be similar?
Also how about Ubuntu? I'm familiar with Ubuntu, but I'll look at AntiX
From what I gather I only need USB host mode so that the USB port is not outputting power.
Hdale85 said:
Can it be a kernel from another device? or does it need to be similar?
Also how about Ubuntu? I'm familiar with Ubuntu, but I'll look at AntiX
From what I gather I only need USB host mode so that the USB port is not outputting power.
Click to expand...
Click to collapse
Ubuntu should work, though the names of the dependencies might be off. Easier to just partition off and install Antix. Damn good distro. I went with stable for the guide, but you can easily switch later to testing or unstable by changing up the sources list.
For what you need, you may find it as an option when adjusting the menuconfig during the make process.
The second post in the thread tells a bit about changes necessary for the 500 device, as I originally made the guide for the 510.
There are currently two other kernels for the 500 that were successfully made using the guide. One of them also has a decent install through recovery script
sleekmason said:
Ubuntu should work, though the names of the dependencies might be off. Easier to just partition off and install Antix. Damn good distro. I went with stable for the guide, but you can easily switch later to testing or unstable by changing up the sources list.
For what you need, you may find it as an option when adjusting the menuconfig during the make process.
The second post in the thread tells a bit about changes necessary for the 500 device, as I originally made the guide for the 510.
There are currently two other kernels for the 500 that were successfully made using the guide. One of them also has a decent install through recovery script
Click to expand...
Click to collapse
What's the difference between the 500 and 510?
Hdale85 said:
What's the difference between the 500 and 510?
Click to expand...
Click to collapse
The 510 is the Google play edition, whereas the 500 is the lg version. If you didn't buy it through the play store, you have the 500.
The best way to learn would be to follow the guide all the way through, copy and paste, and then figure out what you are doing while you are doing it!
Also, this should be posted in the questions thread rather than development if a moderator would be so kind to move this post.
Oh ok the 510 is the google play edition. Either kernel should work right? They are the same device... I'm not running the stock rom as I wanted a basic 4.4 rom as this is eventually going in my car.
Well you posted right before me lol, but I made the post here because I know there are a couple other people looking for the same thing so I was hoping we could develop a kernel for everyone.
Hdale85 said:
Oh ok the 510 is the google play edition. Either kernel should work right? They are the same device... I'm not running the stock rom as I wanted a basic 4.4 rom as this is eventually going in my car.
Click to expand...
Click to collapse
Unfortunately no, there are some differences, mostly with naming, but that can be important.
There are two parts to the boot image for our device, the ramdisk, and the kernel itself. The ramdisk plays a key roll in deciding certain options for the device, while the kernel controls more common options you may find on any device.
Most of the install from recovery scripts, repack the kernel zimage with the existing ramdisk from the device. But this doesn't really matter either.
All of the multi device kernels tend to be larger than necessary and have problems they shouldn't.
Long story short is that each device has it's own kernel source, which has supposedly been optimized for its device. This isn't exactly true, and the list of changes I've made to better the 510 device's kernel is astounding.
If you follow my guide, all of this will become apparent.
Alright thanks I'll look over it.
So what makes the510 different?? Is the firmware different? Obviously they didn't change the hardware so could one somehow convert the 500 to a 510? Only reason I'm interested is because some of that stuff you said doesn't work on the 500 it seems? Such as fastboot?
Hdale85 said:
So what makes the510 different?? Is the firmware different? Obviously they didn't change the hardware so could one somehow convert the 500 to a 510? Only reason I'm interested is because some of that stuff you said doesn't work on the 500 it seems? Such as fastboot?
Click to expand...
Click to collapse
Lg specific drivers mostly. Fastboot requires an unlocked boot loader, which the V500 does not have. An exploit is used to bypass the boot loader on the 500. Loki.
The gpe is pure android, with just a couple of perks thrown in, as it uses an Lg platforms. Our device , that being the V510 most closely resembles the Nexus 4 (Mako) version, and was probably based off that device. The items I have added to the 510 kernel as enhancements, mostly came from a mako kernel with the rest simply being tweak corrections to the existing source code.
Those changes alone made huge improvements in performance and battery.
sleekmason said:
Lg specific drivers mostly. Fastboot requires an unlocked boot loader, which the V500 does not have. An exploit is used to bypass the boot loader on the 500. Loki.
The gpe is pure android, with just a couple of perks thrown in, as it uses an Lg platforms. Our device , that being the V510 most closely resembles the Nexus 4 (Mako) version, and was probably based off that device. The items I have added to the 510 kernel as enhancements, mostly came from a mako kernel with the rest simply being tweak corrections to the existing source code.
Those changes alone made huge improvements in performance and battery.
Click to expand...
Click to collapse
Yea I just found the long thread about converting, its strange they can't seem to get it to work? Quite strange... Well I'll have to research the other bits I guess from others that have made V500 kernels or something.
maybe this commit is what you need
https://github.com/oubeichen/android_kernel_lge_v500/commit/ee86db750adf2bb7b4f7b988ba6937d92551373b
I havent tested yet but this is ported from a nexus4 kernel thread. v500 and nexus4 have the same power management ic
Sent from my LG-V500 using XDA Premium 4 mobile app
oubeichen said:
maybe this commit is what you need
https://github.com/oubeichen/android_kernel_lge_v500/commit/ee86db750adf2bb7b4f7b988ba6937d92551373b
I havent tested yet but this is ported from a nexus4 kernel thread. v500 and nexus4 have the same power management ic
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If anybody wants this, I'll compile it into the V510. Looks pretty straightforward. Thank you for the link.
Hdale85 said:
Well you posted right before me lol, but I made the post here because I know there are a couple other people looking for the same thing so I was hoping we could develop a kernel for everyone.
Click to expand...
Click to collapse
Indeed! :fingers-crossed:
treetop777 said:
Indeed! :fingers-crossed:
Click to expand...
Click to collapse
I'm going to take a stab at a custom kernel, but I have to setup linux on my desktop again so I'm not sure when I'll get around to it lol. Might be able to this week sometime.
If I can't get USB Host mode with charging enabled I'm going to have to look into a wireless HD solution or something, and even then that won't fix the setup I wanted to use for high end sound.
news ????
Hi folks,
I just started to port UbuntuTouch for the Sony Xperia Z Ultra and I think I should have a *.zip ready for testing in 2 weeks.
Until then, I will use this thread as a scrap book to document all the troubles I run into, all the things that needed my special attention and fixes that are not that obvious. I hope there will be some fellas brave enough to test everything and report back or even to join me with the development.
Best regards,
Kalle
First Update:
I found that the Ubuntu Touch version that ist based on CyanogenMod was not updated to a more recent version. This means that I have to either look into AOSP or backport everything to CM-10.1. I think backporting is kinda stupid because newer we are writing new software to improve things. Sadly I don't have much experiance with AOSP so I will have to find out how everything works and what the differences to CyanogenMod are.
The good news is, that I'm catching up with the mailing list, which means I'll have a place to call for help.
Also I'm in the progress to start a git repo, but I'm unsure what I will need to add, maybe some common stuff from sony does not need to be changed.
So long,
Kalle
Update!
There is a new porting guide! See here
I already freed some space for it and ordered a bit more ram so after my exam next week, I'll pick this up/Start all over.
Hope you are as excited as I am,
Kalle
XDA:DevDB Information
Ubuntu Touch for Sony Xperia Z Ultra, ROM for the Sony Xperia Z Ultra
Contributors
KalleEatingBrain, Kohelet
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Testing
Created 2014-05-14
Last Updated 2015-02-24
freaking awesome!
freaking awesome!
i would like to test. maybe i can help with developing/porting
Thank you for your efforts. I will test if needed.
Sent from my C6806 using XDA Premium 4 mobile app
Great this would be awesome if you can make it happen. I'm here for testing if required.
Sent from my C6833 using XDA Premium 4 mobile app
In also here for testing... Ubuntu Touch has intruiged me, I would love to try it out.
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
iBuzman said:
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
+1
Nice.ill be watching out everyday
Sent from my C6833 using XDA Premium 4 mobile app
blueether said:
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
Click to expand...
Click to collapse
Cool, thanks can you give me a hint on how to deal with new targets in Aosp? I mean setting up the files in a way "lunch" is able to find the right target.
Sent from my C6833 using XDA Free mobile app
vendersetup.sh file in vender/ might be what you are looking for?
have a gander at this http://www.kandroid.org/online-pdk/guide/build_new_device.html
How are you doing on this? I've just started working on this as well and am curious to know how far along you've gotten/what issues you've run into.
Sent from my Nexus 7 using XDA Free mobile app
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Kohelet said:
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Click to expand...
Click to collapse
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
KalleEatingBrain said:
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
Click to expand...
Click to collapse
I actually got past the libhybris issue. The problem was that the porting guide is out of date. It's based on using cm-10.1 whereas the current source for Ubuntu is based on cm-11.0. So if you use 4.4.2 instead instead of 4.2.2 then it works. But there are so many other issues and the documentation for fixing them is so poor. I've kept a running list of problems I've come across and the solutions for them (it's below).
Also they dropped the whole UCM thing so you should be able to get sound working once you actually get a working build, but I couldn't get it to build. The error that is currently in my way has to do with "No rule to make target signapk.jar needed by com.qualcomm.location" or something or other. And I found nothing on how to solve that online.
At this point I've decided to take a short break from the whole thing because it's so frustrating.
Once I get motivated to work on it again, I'll probably start from scratch.
Issues List (I apologize for not being specific about the errors, I didn't write them down verbatim):
If you get an error about libelf you need to add CyanogenMod/android_external_elfutils to your local_manifests/roomservice.xml and also add external/elfutils under subdirs in build/core/main.mk
Don't forget to also add device/sony and vendor/sony to build/core/main.mk as well.
The build will complain about not having a rule to make android-boot.img. To fix you have to go to device/sony/fusion3-common/custombookimg.mk and change boot.img to android-boot.img. You need to make the same change in device/sony/rhine-common/custombootimg.mk
I got an error about android.hardware.bluetooth_le.xml. If you just restart the build it doesn't complain, but I didn't find a proper solution to that.
If you get the libhybris error you have the wrong version of the Ubuntu source. Make sure you're using 4.4.2 when you phablet-dev-botstrap. It should be phablet-dev-bootstrap --sources aosp --repo-branch phablet-4.4.2_r1 [target_directory]
You might get an error about a product_config.mk and how it's missing a makefile for togari. You have to make sure that in device/sony/togari Android.mk, cm.mk, full_togari.mk, and vendorsetup.sh PRODUCT_NAME is the same. I solved this by changing PRODUCT_NAME to cm_togari in all of them and then renamed full_togari.mk to cm_togari.mk
You might get an error like MODULE.TARGET.SHARED_LIBRARIES.libOmxCore already defined in hardware/qcom/media. You should have CyanogenMod/android_hardware_qcom_media-caf-new in your repo manifest with a path of android/qcom/media-caf-new so you can safely rm -rf the hardware/qcom/media directory to get past this error.
If you get an error about dtbToolCM, add /device/qcom/common/dtbtool to your subdirs in build/core/main.mk
You may get an error about mkbootimg, that's because Sony uses a different version of mkbootimg. The only option I found was to download it from the internet (Thanks DooMLorD!). Once you get that version edit device/sony/rhine-common/custombootimg.mk and replace $(MKBOOTIMG) with the path to your downloaded mkbootimg binary.
You might get an error about no rule to make target something/something/signapk.jar needed by something/something/com.qualcomm.location. I didn't find a solution to this error.
Click to expand...
Click to collapse
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
blueether said:
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
Click to expand...
Click to collapse
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Kohelet said:
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Click to expand...
Click to collapse
Yeh carbon and slim were easy to build, and simple fixes. AOSP on the other hand I wish I had kept a build log
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch. I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
KalleEatingBrain said:
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch.
Click to expand...
Click to collapse
That could potentially be a major source of my problems. i wasn't aware of that.
I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
All I have at the moment is a fork of the CM repos. Feel free to add me to your repo. My username on Github is Kohelet as well. I can start to look into removing java dependencies as well.
As for the sound, the mailing list made it appear as if it was a simple matter of running
Code:
$ sudo apt-add-repository ppa:ci-train-ppa-service/landing-018
$ sudo apt-get update
$ sudo apt-get dist-upgrade
$ sudo apt-get install pulseaudio-module-droid
I could be wrong though.
Hi
Maybe it's a stupid question, but I have thid doubt. I have bought a new ssd 250gb for my laptop and I have to partion it.
I want create a dualboot system Window 8.1 + Ubuntu to learn to develop kernel and android rom.
Oh my lapton I will install a second mechanical hard disk (500gb) where I will put photo and data .
My doubt is : how much space is recommended for develop Android kernel and Roms ?
I have thought to give 220gb to window and the rest to Ubuntu and use the second mechanical hardisk to put the rom and kernel source.
Do you have any suggestion or advice to give me ? Tomorrow I would install the new hard disk and I think all of you are the best people to ask
aeroxr1 said:
Hi
Maybe it's a stupid question, but I have thid doubt. I have bought a new ssd 250gb for my laptop and I have to partion it.
I want create a dualboot system Window 8.1 + Ubuntu to learn to develop kernel and android rom.
Oh my lapton I will install a second mechanical hard disk (500gb) where I will put photo and data .
My doubt is : how much space is recommended for develop Android kernel and Roms ?
I have thought to give 220gb to window and the rest to Ubuntu and use the second mechanical hardisk to put the rom and kernel source.
Do you have any suggestion or advice to give me ? Tomorrow I would install the new hard disk and I think all of you are the best people to ask
Click to expand...
Click to collapse
Did you find out how many GB?
lewisville said:
Did you find out how many GB?
Click to expand...
Click to collapse
Example for S4 mini AICP ROM with kernel source included
After repo sync ~34GB
After brunch serranoltexx ~59GB
piskor said:
Example for S4 mini AICP ROM with kernel source included
After repo sync ~34GB
After brunch serranoltexx ~59GB
Click to expand...
Click to collapse
Any idea why my 90GB would not suffice? I am running out of space even with 90GB trying to build CM
lewisville said:
Any idea why my 90GB would not suffice? I am running out of space even with 90GB trying to build CM
Click to expand...
Click to collapse
Build with CCACHE enabled. I don't use it
piskor said:
Example for S4 mini AICP ROM with kernel source included
After repo sync ~34GB
After brunch serranoltexx ~59GB
Click to expand...
Click to collapse
piskor said:
Build with CCACHE enabled. I don't use it
Click to expand...
Click to collapse
So, I should build it with CCACHE disabled?
lewisville said:
So, I should build it with CCACHE disabled?
Click to expand...
Click to collapse
It's up to you. If you want use CCACHE, you need more space.
It is advised to have about 100gb set aside to build. With source code expanding every day you will always want to have extra.
piskor said:
It's up to you. If you want use CCACHE, you need more space.
Click to expand...
Click to collapse
Thank you so much. I do not have that much space on my Mac currently. So to confirm, if I disable CCache, 90GB should suffice right?
The only downside from what I read would be that it will compile every time so the build will be slow. Is that correct?
lewisville said:
Thank you so much. I do not have that much space on my Mac currently. So to confirm, if I disable CCache, 90GB should suffice right?
The only downside from what I read would be that it will compile every time so the build will be slow. Is that correct?
Click to expand...
Click to collapse
Ad. 1 I think so, but it depends on your device source. In my case it is enough
Ad. 2 Correct
Thanks @piskor