Database Users

[Q] want to compile CM7 - easy dev

So i would like to edit easy Dev to compile CM7 but I'm a linux newbie. I'm not afraid to admit it. Currently i'm on Ubuntu 10.10 Netbook remix, just running it off of a pendrive. How hard would it be to edit it to compile CM7 instead of CM6?

It IS Lupus said:
So i would like to edit easy Dev to compile CM7 but I'm a linux newbie. I'm not afraid to admit it. Currently i'm on Ubuntu 10.10 Netbook remix, just running it off of a pendrive. How hard would it be to edit it to compile CM7 instead of CM6?
Click to expand...
Click to collapse
Well... You'll need a vendor tree first. And you'll have to run it on a 64-bit box with 64-bit linux. You have to change 'froyo' to 'gingerbread' in EasyDev, so it will grab CM7 source. There will also be some other differences to work out.
As soon as there's a vendor tree available and I have the time to test, I'll finish up EasyDev v7. Some of the additions that I have actually worked on so far are:
1) two or three bug fixes
2) adding CM7
3) adding option to install tiny or full gapps
The CM6 code has been unstable recently in addition to koush's hosting having issues, so I have had plenty of speed bumps in addition to real life stuff.
So... If you can wait on me, that's fine. If not, go for it! Feel free to post your code changes in the thread. We'll take any help we can get.

gnarlyc said:
And you'll have to run it on a 64-bit box with 64-bit linux.
Click to expand...
Click to collapse
Conap mentioned this before as well - just out of curiosity, do you know what the dependency is that requires x64? The compilation target is an ARM device, so I can't imagine that it is a library issue... is it simply a matter that one of the compilation/build tools needs more than 3-4 Gigs of VM?
I remember that building the kernel source trees on a uniprocessor would come to a halt if you tried it on a linux box with less than about 768 Mb of RM, but hitting the 32-bit limit (3-4Gb) with build tools seems kinda surprising.
bftb0

bftb0 said:
Conap mentioned this before as well - just out of curiosity, do you know what the dependency is that requires x64? The compilation target is an ARM device, so I can't imagine that it is a library issue... is it simply a matter that one of the compilation/build tools needs more than 3-4 Gigs of VM?
I remember that building the kernel source trees on a uniprocessor would come to a halt if you tried it on a linux box with less than about 768 Mb of RM, but hitting the 32-bit limit (3-4Gb) with build tools seems kinda surprising.
bftb0
Click to expand...
Click to collapse
I honestly wasn't sure, but a quick Google search...
http://groups.google.com/group/android-building/browse_thread/thread/852d63ab6124c87e
This is a post from the Android Building group. It appears to be a JDK issue. I've not really tested either way as of yet, although apparently Google says "use a 64-bit host to build, that's what is supported."

[VMWare Image][9-DEC-2011] Android AOSP/ROM Developer Environment

Everyone is allowed to make changes to the VMWare image and re-upload it. If you re-upload the VMWare image with the made corrections, post the download link(s) in this thread. I will update the first post.
If there is a AOSP Developer that is willing to make a complete tutorial, please make one that works and is up-to-date with 2.3.7
The more people we have working on making ROMs, the better.
This VMWare image is:
- Base: Ubuntu 10.04 LTS
- ICS ready
- Gingerbread ready
- Fully updated
- Eclipse with ADT Plugin
- Android Kitchen Integrated
PASSWORD: root
Latest changelog (Coming soon)
- Based on 10.04 LTS instead of 11.10
- Different approach
Download link:
Bypass 24h wait time, limit reached --> Solution? Reset your ip! In Belgium this is easy by restarting your modem/router. This may be different in other countries.
more mirrors will come!
Part 1
Part 2
Part 3
Image is extracted, where do I start?
Continue from this link
How to build 2.3.7 for Nexus S
This is just a snippet that may help you.
repo init -b android-2.3.7_r1 < /dev/null (This branch is ready to use with Nexus S and Nexus S 4G)
repo sync
source build/envsetup.sh
lunch full_crespo-userdebug
make -j8 (-j8 = for eightcores like 2600k, 2630QM / -j4 = for quads 2500K/2620M/Q6600 / -j2 for dual cores / ...)
Click to expand...
Click to collapse
Don't forget to add the vendor files of the device. You need to download the scripts as well of the driver binaries.
Click to expand...
Click to collapse
I tested a quick build. And it's working.

A virtual machine with limited RAM in order to compile AOSP? Definitively not a good idea. Why not dual boot? Sooooo easy to install the worst distro ever (*buntu).

This is awesome. My only problem is that I only have VMWare Workstation 7.

Super! Waiting for this

djjonastybe said:
Dear community,
I made a AOSP developer environment for VMWare Workstation 8 or latest VMWare Player (free).
You can use this VMWare image as a base to build AOSP ROMs. Imade it for those having trouble getting it to work or maybe if you don't have time to set it up properly. Well if you are downloading this you might have a good reason!
Anyway have fun!
If there are any errors let me know.
This VMWare image is:
- ICS ready
- Gingerbread ready
- Fully updated
Download link:
...uploading...
Click to expand...
Click to collapse
Who would have guessed that an android dev would have difficulty setting up a linux enviroment . . . go figure.

You do not have to be an Android Dev to compile Android. I haven't written a single line of code for Android and can compile AOSP 2.3.7 fine.
This is simply to save time. And if you have good enough hardware (like myself) compiling Android AOSP in a VM session works perfectly fine.
Most people that are into computers have a rocking system. I have 12GB ram, I dedicate 8 for my VM and the rest for my main OS (windows 7). Works fine, what's the issue?
Some people don't want to dual boot and sometimes a Linux distro doesn't support certain hardware or can't be installed.

I would appreciate it. THANKS

nice.....this could be very useful
Sent from my Nexus S using xda premium

FeaRThiS: Who would have guessed that an android dev would have difficulty setting up a linux enviroment . . . go figure.
Click to expand...
Click to collapse
You seem to be the only one against uploading this.
Guys I am still trying to upload it. I am splitting it in 700MB sizes. Crocko's uploadservice is down. I will upload it on depositfiles and multiupload
12,5%

@FeaRThiS just stated the obvious. I also think the first step to understand how to build an AOSP ROM is knowing how to setup the development environment.
I don't have anything against using a VMWare image. But, IMHO, considering the time for uploading/downloading the file, if you do the setup yourself (in VMWare or whatever), you should have already been compiling your ROM by now.

suksit said:
@FeaRThiS just stated the obvious. I also think the first step to understand how to build an AOSP ROM is knowing how to setup the development environment.
I don't have anything against using a VMWare image. But, IMHO, considering the time for uploading/downloading the file, if you do the setup yourself (in VMWare or whatever), you should have already been compiling your ROM by now.
Click to expand...
Click to collapse
Okay, its not useful for you two.
Next!
I like it and i will try it.

djjonastybe said:
You seem to be the only one against uploading this.
Guys I am still trying to upload it. I am splitting it in 700MB sizes. Crocko's uploadservice is down. I will upload it on depositfiles and multiupload
12,5%
Click to expand...
Click to collapse
I have nothing against it and it may even be useful in case of emergency when you can not access a linux machine, but as stated by @S suxeN the first step for any dev would be learning to create their own dev enviroment.

i didnt say that.
but the statement is right. Anyways i yet think this image is of great use, as you can always start from there, if u did something wront, what can always happen to nun-linux users.

I don't know anything about linux. Is Eclipse with ADT on here by any chance? If not, what IDE is there to develop with in this VM?

I didn't think that far. Eclipse is not installed.
But I will work on it for next release. For now you have to install it manually. I hope tomorrow evening the new vmware will be uploaded!

Hey guys, don't be so hard on the fella. He's doing us a great service in a way. Not all of us are able to bring laptops wherever we go, dual-boot, etc. I just downloaded this to my external drive that I use to keep my stuff on for work and it'll come in handy when I wanna test apps without worrying about nuking my phone.
Also, it helps that I can demo apps on the thing to co-workers on screen than using a phone. That way I won't have to worry about them screwing things up if they decided to 'explore.'

http://code.google.com/android/nexus/drivers.html#crespogwk74
Can someone help me with this? This has the binaries for the Nexus S.
Where do I place the scripts?
I have a vendor folder with several maps in it now. But I don't know what I have to do now.
I placed the 'vendor' folder in my working directory. But lunch isn't showing up crespo in the list.
These are my steps:
Building
I executed lunch. I realised I did not have crespo in the list. So next, I read the line 'Building for devices'.
Eventually I ended up here:
Building devices
Obtaining proprietary binaries
Starting with IceCreamSandwich, the Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for Nexus S, Nexus S 4G, Galaxy Nexus, and PandaBoard can be downloaded fromGoogle's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
There are no official binaries for Nexus One, ADP2 or ADP1., ADP2 or ADP1.
Click to expand...
Click to collapse
I clicked the link and downloaded the GWK74 binaries.
Now then I read further:
Extracting the proprietary binaries
Each set of binaries comes as a self-extracting script in a compressed archive. After uncompressing each archive, run the included self-extracting script from the root of the source tree, confirm that you agree to the terms of the enclosed license agreement, and the binaries and their matching makefiles will get installed in the vendor/ hierarchy of the source tree.
Click to expand...
Click to collapse
I have the vendor hierarchy...
Do I have to put these files in:
my home folder/bin
OR
home folder/workingdirectory_name
Or what do I have to do now?

updated first post with small hint on how to download 2.3.7 for our Nexus S. Good luck!

yep, i think this is pretty awesome. for me, i'm not an android dev but i've dabbled with theming and porting mods from other phones to the epic 4G previously. i'd love to be able to start with a system ready to go and mess around with some guides to learn how to compile source, etc... thanks.

Nice image man, gonna give it a go later. Thought I'd put my word in the discussion , sure there lots of talented devs, but they have all got different hardware/software and time requirements. So this becomes a useful tool to add to the inventory.

ROM Dev for Ara??

How would ROM deving work for this type of phone where people choose their own specs?
now that i think of it, how would there be updates either? its like a one and done process. so if you buy the phone, you'll stay on the Android version that comes preloaded

I am thinking towards windows kind of update model but free this time.
Only thing is can we modify Linux kernel for enough flexibility.

NaveenKumarXDA said:
I am thinking towards windows kind of update model but free this time.
Only thing is can we modify Linux kernel for enough flexibility.
Click to expand...
Click to collapse
Might be able to work if the MDK enforces a unified modular structure. And extra parts of ROM's would target some v heavy/popular modules.

I think you ubuntu may be the way to go.

Since my knowledge is really limited, if Google and manufacturers cooperate for open-hardware and open-source environment, it will be like installing drivers on a new OS. So everyone can use latest version of Android. Am I right or really really wrong?
Sent from my GT-I8190 using XDA Premium 4 mobile app

I could imagine an official update method in which the used modules are recognized and the update fits perfect to that phone or the modules have anyhow universal usable drivers stored on themselves while you can change them without re-flashing the entire rom.. what do you think?

Surely if all the componets are made by the same manufacter the roms would be universal but with some roms being heavier for the powerfuller phones and lighter for cheaper phones

It will be harder. There will be bloated kernels that account for unused modules. Likely to be devs that tune to a specific hardware set [their's], etc. But w/ a diy modular phone, they'll probably be no shortage of developers.
A cooler way would be to enable more run as module on kernel and have each module self-load its drivers [like plug-n-play]. This could avoid the kernel bloat I aluded to earlier.
Rob

insink71 said:
A cooler way would be to enable more run as module on kernel and have each module self-load its drivers [like plug-n-play]. This could avoid the kernel bloat I aluded to earlier.
Rob
Click to expand...
Click to collapse
I agree with this, or maybe if the system can build the driver files on startup or installation. but then you will be looking at stall's and system freeze if it's interrupted. (just mentioned something similar in another post lol!):fingers-crossed:

If the bootloader can report the serial/models of the components, the kernel can turn on and off what's needed or not. From there yes, there will be a ****ton of modules to compile even if half aren't used. We can also expect to see hybrid kernel drivers doing different things based on some data returned by the actual component (e.g. 16GB vs 32GB storage) -- assuming those components work the same.

Maybe they'll make a new OS for this, kinda like Windows OS. It's supposed to be universal, no matter what kind of parts are installed.

The rom devs can list the minimum specs for the rom so the user has at least the minimum for the rom
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Nope, it is said that you can change modules on the fly. Maybe there are just drivers in the plug in that are loaded first...
Maybe the compatibility to drivers coves with android 5.0?
Regards
Gesendet von meinem C6503 mit Tapatalk

as people have said this wont be common outside the custom pc type market and if it don't support android in some from whether that be via a custom rom and recovery like cwm/twrp it will be a massive flop
i cant see why it cant come with a option that has cwm installed with a rom,them its attractive to coders

I really hope that they have the option for sales of just the outer shell. Then, people like me can custom select whatever they want without having to waste the stock modules which would then be rendered useless.

i hope they make a rolling system similar to how its done by Arch Linux where you start with just a base and let the owner select his own modules or let the user make their own module. that would be fantastic! i mean perfect!

pandasa123 said:
How would ROM deving work for this type of phone where people choose their own specs?
now that i think of it, how would there be updates either? its like a one and done process. so if you buy the phone, you'll stay on the Android version that comes preloaded
Click to expand...
Click to collapse
I think there will only be ROMs for certain phone combinations
Sent from my ultimately bumped up LG-P700 running CM11

The modularity will be programmed into the OS. Wether that part goes open source or not is another question.
Gesendet von meinem XT1039 mit Tapatalk

all parts will be class compliant iirc, meaning each new OS/rom only needs have generic drivers, anything that isn't class compliant needs to carry its own drivers, i could be wrong but im sure thats what he said in the interview with the first working spiral 1

I may be a bit crazy in thinking this.
But I'd LOVE project ARA and Cyanogenmod to partner and have their CM OS on the ARA modular phones. Imagine we could have theme chooser on the device. And customise it exactly to our liking.
inside and out in this case.
But alas it's only a pipe dream.

Linage OS for PC based on android-x86 [Unofficial] [Experimental] [Based on cm-13.0]

Download: http://geektillithertz.com/wordpress/index.php/2017/01/03/lineageos-13-android-x86-on-pc/
Source: https://github.com/ric96/lineagex86
Bugs:
you tell me

FIRST !!!!!!
Congratulations my friend , but it no workie on my x86 tablet that was running cm13 x86
Kernel bladibla ..sorry so fix it bro !

How does it works?
is it an operating system to install on PC ?
is it a windows application ?
is it a linux application ?
what are we supposed to do with the.7z file ?

This looks promising. Keep up your good work!
Sent from my SM-G935F using Tapatalk

mlsoftlaberge said:
How does it works?
is it an operating system to install on PC ?
is it a windows application ?
is it a linux application ?
what are we supposed to do with the.7z file ?
Click to expand...
Click to collapse
The 7z file needs to be extracted in 7zip file manager. There should then be a IMG file that you need to burn to a USB with Win32DiskImager and boot on a PC. Then install the the HDD in the installer. Be careful with the HDD formatting, its a confusing naming system. I have accidentally formated the wrong drive in the past. It is a full OS.

Is it only for x64-CPUs or also for x86-CPUs? If it is not for x86-CPUs, than i ask you to compile a x86-Build. Thank you! I want install it on an ASUS Netbook.

I try to install geekbench or antuto and it force close
Sent from my MI 5 using Tapatalk

What about lineage-14.1?

it would be awesome if it's 14.1 since nougat support freeform

Lineage is the siccessor of the biggest alternative rom CyanogenMod. For me, there are many reasons to love cm: 1. I like to make all devices looking same, i hate sony-samsung-htc-huawei-moto...themes,bloatware and so on! (Only Sony cam is really nice)
Before a view years, cm was really good. When i buyed a new device (especially 4 months old), mostly there was a ready CyanogenMod out, sometime official, so i flashed and was happy. In the last 2 or three years, CyanogenMod was getting bad worse worst! Not much new devices, not much new updated, not actually Android versions, not much good mods, extras etc. included.
I hope, and it seem so, that it al will be getting better! But there is one big problem:
cm died becouse of getting commercial etc.
Developers must live ,so they need money.
Many developers proramm in their free time and have to work an their main job (waste of genious i say)
My suggestion is that lineage should get the best of both worlds, commercial and free/open source!
The main OS and all of his extras should be free to load, install and use!
Some not important services like OTA updates or user-support (not called customer-support) should cost money, but not much!
I think, a small price of 1€/Month could everyone pay who wants and was respect of this work..i would. When the account is empty, an support ab could be closed and no OTA's could be loaded...

Can you add multi tasking and external screen support to your x86 i mage.
Someone has already done the necessary code for it https://forum.xda-developers.com/android/general/rom-oxi-smartphone-computer-oneplus3-t3558293
Just needs to be included in the x86 image

Interesting idea
Enviado de meu Mi 5s Plus usando Tapatalk

Taking to chat instead

Does it work for 32 bit CPUs? I want to install it on my ASUS Netbook.

xEmre66 said:
Does it work for 32 bit CPUs? I want to install it on my ASUS Netbook.
Click to expand...
Click to collapse
There's a new build of CM 14.1 -86 here:
http://www.android-x86.org/download
I managed to install it to an old netbook [Toshiba N450 Netbook].
It is fast and has a beautiful interface.
Some apps keep foreclosing though.
It can be installed on 32bit and 64bit laptops.
It would be great to hear other feedbacks!
Hats OFF to the devs.

patrol31 said:
There's a new build of CM 14.1 -86 here:
http://www.android-x86.org/download
I managed to install it to an old netbook [Toshiba N450 Netbook].
It is fast and has a beautiful interface.
Some apps keep foreclosing though.
It can be installed on 32bit and 64bit laptops.
It would be great to hear other feedbacks!
Hats OFF to the devs.
Click to expand...
Click to collapse
It works great on USB for me but keeps crashing on my NVME install (looping com.phone crashing and system framework keeps stopping). Maybe it's just my pc?

Jbuch84 said:
It works great on USB for me but keeps crashing on my NVME install (looping com.phone crashing and system framework keeps stopping). Maybe it's just my pc?
Click to expand...
Click to collapse
I installed it on the hard disk where my windows is installed and gave it a 16gb data allocation. So far it is running great. Maybe try a fresh install.

Will it work on hp pavilion running on Windows 7 x32 cpu?
If working please tell me the smallest to biggest bug.

patrol31 said:
I installed it on the hard disk where my windows is installed and gave it a 16gb data allocation. So far it is running great. Maybe try a fresh install.
Click to expand...
Click to collapse
Did fresh install. What type of hard disk did you install on.. HHD, M.2, NVME? Mine is NVME and crashes on boot.

Jbuch84 said:
Did fresh install. What type of hard disk did you install on.. HHD, M.2, NVME? Mine is NVME and crashes on boot.
Click to expand...
Click to collapse
HDD, it's an old netbook.

[DISCUSSION] ExFAT file system driver

Hi! So this is rather a request or a brainstorming on a certain subject but I've been testing with the available roms and kernels. For some reason most roms do not support the well known and widely used exfat file system. Even when it is supported in their kernel the system still won't see any partition that runs under exfat. No big name kernels were able to detect my exfat partition. Pixel Experience, Lineage OS, dotOS, miracle DROID, AOSP etc. None. Not even after flashing Electra Blue, Franco, Inferno and such famous kernels that said to have support. KudKernel is the only one that allows their users exfat file system usage. I dig deep into the subject and even tried to inject exfat support via sudo and scrips to certain kernels but I failed miserably. Do you think it is possible to make any kernel support exfat or just those kernels that use the latest Linaro toolchain?

greenys' said:
KudKernel is the only one that allows their users exfat file system usage.
Click to expand...
Click to collapse
The trick is to discover how KudKernel does it.

https://github.com/cryptomilk/kernel-sdfat
This is what's done in kudkernel

DarthJabba9 said:
The trick is to discover how KudKernel does it.
Click to expand...
Click to collapse
Whether or not I find out what's done in kud kernel and how does it support exfat sd card I can't do a thing about it since it'd need me to recompile and rebuild any other kernel that does not support exfat. Which is rather problematic for me, a non-ubuntu/Linux user who knows nothing about coding in that area. Ergo I'm still in the same situation I started from . -.
By the way I only get know of it today that I can't rebuild a kernel on Windows.

greenys' said:
Whether or not I find out what's done in kud kernel and how does it support exfat sd card I can't do a thing about it since it'd need me to recompile and rebuild any other kernel that does not support exfat. Which is rather problematic for me, a non-ubuntu/Linux user who knows nothing about coding in that area. Ergo I'm still in the same situation I started from
Click to expand...
Click to collapse
You are correct - you will need to build the kernel yourself. Or you can ask the developers of your favourite kernels (or ROMs) to add sdfat support. It is a fairly painless process, which would take a developer less than 5 minutes to do. Of course, they might not be interested in doing it.
By the way I only get know of it today that I can't rebuild a kernel on Windows.
Click to expand...
Click to collapse
Technically, yes. But you can install VirtualBox on your Windows PC, and create a Linux Virtual Machine (VM) under VirtualBox. When you boot up the VM, you are running full-blown Linux - alongside all your other Windows stuff.

DarthJabba9 said:
You are correct - you will need to build the kernel yourself. Or you can ask the developers of your favourite kernels (or ROMs) to add sdfat support. It is a fairly painless process, which would take a developer less than 5 minutes to do. Of course, they might not be interested in doing it.
Technically, yes. But you can install VirtualBox on your Windows PC, and create a Linux Virtual Machine (VM) under VirtualBox. When you boot up the VM, you are running full-blown Linux - alongside all your other Windows stuff.
Click to expand...
Click to collapse
Oh my. Sure will look into that. But that will take some (tremendous) time and till then I still can't use my sd card properly -_- Anyways, thanks.

greenys' said:
Oh my. Sure will look into that. But that will take some (tremendous) time and till then I still can't use my sd card properly -_- Anyways, thanks.
Click to expand...
Click to collapse
Official LineageOS received support for exfat this week

Noter2017 said:
Official LineageOS received support for exfat this week
Click to expand...
Click to collapse
Oh my, that's some wonderful news! Been waiting for this so long I can't explain. Thanks for the info!