Hi,
Since OP released the source code of the OP3 I thought I would take a shot on compiling them.
I have a lot of experience with C++ on an application level and also did some minor work with windows drivers.
But on Linux I'm still a beginner.
Since the repository OP points to (https://github.com/OnePlusOSS/android/tree/oneplus3/6.0.1) contains only a shell script I guess I can't compile it on windows, right?
So I will go for a Linux VM, what OS should I use Ubuntu 12 or 14 or may be better Debian?
Also How much power does a machine need in order to compile a android image in a reasonable time frame? My PC has a 6 core i7 @ 4GHz with 64 GB of RAM, AFAIK I can give all cores to the VM and up to 32 GB or RAM.
Giving cores is no problem, but the more RAM I give the larger all the snapshots become, so what would be a recommended amount?
Also What tools do I need? I tried to run the pull_library.sh but it threw some errors as I did not have ADB installed in the VM, so before I try and try i thought I just ask what thing I'll need to swiftly succeed with my endeavor?
Cheers
David X.
DavidXanatos said:
Hi,
Since OP released the source code of the OP3 I thought I would take a shot on compiling them.
I have a lot of experience with C++ on an application level and also did some minor work with windows drivers.
But on Linux I'm still a beginner.
Since the repository OP points to (https://github.com/OnePlusOSS/android/tree/oneplus3/6.0.1) contains only a shell script I guess I can't compile it on windows, right?
So I will go for a Linux VM, what OS should I use Ubuntu 12 or 14 or may be better Debian?
Also How much power does a machine need in order to compile a android image in a reasonable time frame? My PC has a 6 core i7 @ 4GHz with 64 GB of RAM, AFAIK I can give all cores to the VM and up to 32 GB or RAM.
Giving cores is no problem, but the more RAM I give the larger all the snapshots become, so what would be a recommended amount?
Also What tools do I need? I tried to run the pull_library.sh but it threw some errors as I did not have ADB installed in the VM, so before I try and try i thought I just ask what thing I'll need to swiftly succeed with my endeavor?
Cheers
David X.
Click to expand...
Click to collapse
Why do you not asking this in the right section?
Maybe general or Q&A
Best Regards,
Taker
What are you expecting when trying to compiling this ? It's the device tree and the kernel, not a full rom that you can install and run on your phone. Maybe you should look at how to compile a full rom like cm13. (if you want to compile something with your beast). There are plenty of tutorials.
_Man0waR_ said:
What are you expecting when trying to compiling this ? It's the device tree and the kernel, not a full rom that you can install and run on your phone. Maybe you should look at how to compile a full rom like cm13. (if you want to compile something with your beast). There are plenty of tutorials.
Click to expand...
Click to collapse
and where would I find those?
DavidXanatos said:
and where would I find those?
Click to expand...
Click to collapse
perhaps by searching? there is a whole thread about building cm13 in Guides, News and Discussion. And google should bring you many results. I know I searched when I wanted to build my first rom a couple of years ago.
DavidXanatos said:
and where would I find those?
Click to expand...
Click to collapse
Come on. There is even a thread dedicated to building cm13 for the OP3. It should help you to start. There are several useful links inside the thread too. It's almost the same for any android rom (with a few adjustments).
http://forum.xda-developers.com/oneplus-3/how-to/learning-to-build-cm13-t3406725
Feel free to ask questions there if you get stuck. It should get you busy until we have official nightlies.
Good luck ! But please don't create a new thread 'Unofficial cm13 build'. We have enough of them
DavidXanatos said:
and where would I find those?
Click to expand...
Click to collapse
You will never be able to build yourself if you ask people where to find those.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Related
[This is not the place to say "this is awesome" or "thanks!"]
[DEVS ONLY]
I want to start this thread to keep up the progress on the port.
the bad news is that the SDK is incomplete for now, so (like other devices)
we will have to write our own code for the OS, the nook community
has done a wonderful job writing their own libraries and stuffs, so we will have to do the same.
Instead of pursuing different goals, let's focus on one thing at a time.
since GSM and CDMA versions are already out, it seems we suffer the same bugs, so for now let's unite strength and knowledge to overcome these.
I propose that the first goal to fix is the SurfaceFlinger, so we could at least see the apps, the buttons and the notifications.
it is currently throwing this:
04-06 22:01:35.495: ERROR/Surface(2960): dequeueBuffer failed (Out of memory)
this could lead us that it might coudln't start because of some malloc malfunction or something.
also that pvrsrvinit bugs me a lot.
update:
8/APR/2011
since DiP7 could fix SurfaceFlinger and other things using a different build from the GSM kernel, we have to dig deeper
======================================
CURRENT GOAL
Rebuild Kernel
======================================
Current approaches:
*none
Post any finding, guessing or anything, and please, please don't be afraid to ask anything you have a doubt, as a Dev you should not know everything, so we can help us each other
------------------------------------------
Google Easter egg:
while searching some info about the android.mk file , I put it on the chrome bar to search for that term, but instead I went to
http://android.mk
an easter egg web page from google lol
******TOOLS*********
How to send text and Keystrokes via ADB
http://bradchow.blogspot.com/2011/02/send-intent-and-key-event-by-adb.html
use DroidExplorer to easily access your device from your computer and makes changes from it
http://de.codeplex.com/
The Android Boot Process
http://www.androidenea.com/2009/06/android-boot-process-from-power-on.html
---Kernel Tools----
CPU Datasheet
http://forum.xda-developers.com/showthread.php?t=745877
Samsung GIT
http://android.git.kernel.org/?p=kernel/samsung.git;a=summary
PowerVR SDK
http://www.imgtec.com/powervr/insider/powervr-sdk.asp
Source code of samsung firmwares(keep and eye on this)
http://opensource.samsung.com/
Asus pad honeycomb Kernel Source
http://forum.xda-developers.com/showthread.php?t=1026528
ellokomen said:
======================================
CURRENT GOAL
Find why SurfaceFlinger is not working
======================================
Click to expand...
Click to collapse
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
updated approaches and new tools have been added
spacemoose1 said:
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
Click to expand...
Click to collapse
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
Click to expand...
Click to collapse
you mean that you made a port of a Linux Distro into the tab?
ellokomen said:
you mean that you made a port of a Linux Distro into the tab?
Click to expand...
Click to collapse
yes click here for the thread on the port of ubuntu
Current kernel source
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
here it is, bear in mind that this is for CDMA devices
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
daml said:
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
Click to expand...
Click to collapse
yeah but we need a place for the other devs to share their milestones, here is a place for technical discussion amongst us, to share the knowledge etc...
the other threads are flooded from non devs messages, so it´s kind of difficult to read 14 pages of information when the 80% is people complaining not making it boot
lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
Click to expand...
Click to collapse
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
D'oh! Nobody told me, LOL... I'll get another copy up.
spacemoose1 said:
D'oh! Nobody told me, LOL... I'll get another copy up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Flokey said:
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Click to expand...
Click to collapse
Digging through it now.
spacemoose1 said:
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
Click to expand...
Click to collapse
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
lilstevie said:
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
Click to expand...
Click to collapse
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Goal and tools updated*
spacemoose1 said:
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Click to expand...
Click to collapse
You don't know what a kernel panic is do you?
lilstevie said:
You don't know what a kernel panic is do you?
Click to expand...
Click to collapse
I thought that linux throws a dump log when it makes a kernel panic specifying the memory address and the cause of crash
Hey all.
I recently compiled android 4.0.3 AOSP for galaxy nexus as was explained in the topic at general discussion.
after a few days of issues, all went fine and i got myself a zip ota package file.
Now, as a developer, i wish to change the rom and the kernel, and debug/emulate it.
trying to type "emulator" didn't help and it suggested i would type "vemulator"
I got and installed vemulator but it asked me for a bootable image. (which one?)
Is there any way i could do this properly?
about the kernel development, i read some info and i separately got the kernel through a git repo. its alright but then again - how can i emulate it?
I do not wishing to risk my device is such early stage.
thanks.
You could try the android sdk.
Sent from my Galaxy Nexus using xda premium
further details please?
Until now i only used android sdk on windows.. so i have no knowledge of this under ubuntu.
I dont understand what you mean by emulating the kernel. I dont think that is possible as the kernel is so tightly tied to the hardware that it has to be loaded to the phone for testing. At least thats how i tested kernels. I make code changes, compile, and flash to device. When the code didnt work i had to flash old kernel or restore nand backup, then try again with code fixes. Repeat hundreds of times. Thats how i did it.
RogerPodacter said:
I dont understand what you mean by emulating the kernel. I dont think that is possible as the kernel is so tightly tied to the hardware that it has to be loaded to the phone for testing. At least thats how i tested kernels. I make code changes, compile, and flash to device. When the code didnt work i had to flash old kernel or restore nand backup, then try again with code fixes. Repeat hundreds of times. Thats how i did it.
Click to expand...
Click to collapse
Understood, Thanks
Now, about emulating the rom.. i understand it IS possible. which steps do i have to take in order to do that after i compiled the source?
Dutchy18 said:
Understood, Thanks
Now, about emulating the rom.. i understand it IS possible. which steps do i have to take in order to do that after i compiled the source?
Click to expand...
Click to collapse
The sources are buildable for multiple devices. Once build for one device it only runs on that device. Building for Galaxy Nexus (maguro) means no emulation but only running on real hardware.
If you want to build an image for the emulator you need to build the emulator configuration (e.g. full-eng). That will only run on the emulator not on a google nexus.
See http://source.android.com/source/building.html for possible configurations and how to run the emulator.
Well this thread is dedicated about the possibilities of getting a port of ubuntu phone os. Recently displayed and would be launched around MWC 2013, Ubuntu OS will be launched for galaxy nexus! .
although there are short threads present about the topic, aim of this thread would be to provide Support/Bug-Report/F.A.Q if any port of ubuntu shows up for our phone from our great developers.
This is refreshingly new OS.
HERE IS THE LINK TO THREAD--> http://forum.xda-developers.com/showthread.php?t=2174544
I am damn sure some-one will take up this great job
Latest: Ubuntu Phone OS Porting Guide https://wiki.ubuntu.com/Touch/Porting
Some of Features of ubuntu phone:(taken from wikipedia)
OS family Unix-like
Working state Current
Source model Open source
Initial release February 2013; 30 days' time
Available language(s) Multilingual
Update method Ubuntu Software Center (+ APT, …)
Package manager dpkg
Supported platforms i386, ARM
Kernel type Monolithic (Linux kernel)
Userland GNU
Default user interface Unity shell
So what may be the hindrances:
What kernel version is it based on
will it require bootloader unlock ;-(
UBUNTU PHONE OS
since it is yet to be released this is an open discussion, if any developer takes this project for defy, this thread will be a F.A.Q/support/Bugreport thread (if ever it happens )
i'm here for tests.
i'm not a developer, but you guys can count with my defy+ for tests. I really would like to have ubuntu phone on my defy+.
I'd love to see Ubuntu Phone OS on Defy. First of all it's based on Android kernel so there wouldn't be much difficulty for it. The sources should be out next month. Also we'll need to find a method to dual boot with a custom kernel because it's less likely for someone to use it as a primary OS.
Sent from my MB526 using xda premium
Will be very nice to see ubuntu working natively on ours Defy but the specification for minimal resources is beyond the possibilities of defy. So it can be ported but will be very laggy IMHO.
swapnil360 said:
I'd love to see Ubuntu Phone OS on Defy. First of all it's based on Android kernel so there wouldn't be much difficulty for it. The sources should be out next month. Also we'll need to find a method to dual boot with a custom kernel because it's less likely for someone to use it as a primary OS.
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
what is ubuntu's packaging method? i mean the OS image?
pgreed said:
Will be very nice to see ubuntu working natively on ours Defy but the specification for minimal resources is beyond the possibilities of defy. So it can be ported but will be very laggy IMHO.
Click to expand...
Click to collapse
Not that beyond. Min specs (as stated here) only ask 4-8GB internal storage for an entry-level ubuntu phone, everything else (CPU clock, minimum RAM and multitouch capability) already cover our phone. Plus, as far as I remember (though I can easily be wrong on this, since I haven't touched an Ubuntu machine for months, now), this OS (specially considering it was specifically deployed for running on phones) doesn't take more than 2GB when installed. Again, I can be wrong, BUT... What about multiboot? A class 6 8GB card (or even a class 4, like the one included with our phones) may do the job, and we will still be able to boot CM10+ and ask silly questions to Google Now.
vedhasd said:
what is ubuntu's packaging method? i mean the OS image?
Click to expand...
Click to collapse
I may be wrong, but I think I read in more than one place it'll be available as a flashable zip. Since the folks there at Canonical were able to boot this little beauty in a Galaxy Nexus, and they intend to release the GNx version (without many workarounds needed to install) before the end of january, I think it's pretty safe to bet on a recovery-flashable zip file. Last, but not least, I think an install script (like the ones devs use in current Android flashable zips) may be slightly modified to install Ubuntu from a system image, specially if you consider Aroma-based installers are doing wonders in matter of personalizing Android installations. This not considering (and in this matter I have absolutely no idea) the possibility of the disk installer of linux distributions be already running scripts very similar to those used on Android flashable zips to install desktop OSs on computers. Devs will be better suited to tell about the latter.
P.S.: if anyone there tried Android-x86, you guys can see the installable image is very similar to an Ubuntu (or any other linux) installation zip. This might lead us in the opposite direction, looking at which modifications were made for the installer to work with Android, and reversing them for a Ubuntu installer to work in a flashable zip.
K3n H1mur4 said:
Not that beyond. Min specs (as stated here) only ask 4-8GB internal storage for an entry-level ubuntu phone, everything else (CPU clock, minimum RAM and multitouch capability) already cover our phone.
...
Click to expand...
Click to collapse
Is nice that you are very optimistic with this. I wanna be so but ... the entry level processor is a Cortex9 ! which is more powerfull than ours and Ubuntu is based on 3.4x kernel and necesitate a bigger system ROM to install (ours is ~350MB). Anyhow will wait and see and ... speculate.
pgreed said:
Is nice that you are very optimistic with this. I wanna be so but ... the entry level processor is a Cortex9 ! which is more powerfull than ours and Ubuntu is based on 3.4x kernel and necesitate a bigger system ROM to install (ours is ~350MB). Anyhow will wait and see and ... speculate.
Click to expand...
Click to collapse
It may depend on how far our devs will be able to strip down the OS for our phone, I think we may not require full fledged running desktop compatibility but it still depends by what extent we can strip down the footprint!
Sent from my MB525 using xda premium
Ubuntu Phone OS Porting Guide https://wiki.ubuntu.com/Touch/Porting
red lens defy+ guinea pig
swapnil360 said:
I'd love to see Ubuntu Phone OS on Defy. First of all it's based on Android kernel so there wouldn't be much difficulty for it. The sources should be out next month. Also we'll need to find a method to dual boot with a custom kernel because it's less likely for someone to use it as a primary OS.
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
'm not developer but my red lens defy+ is available as a guinea pig.
Then I can make rather a system as primary OS alpha and p500 use my day-to-day
sorry my english
It would be nice if we had more one option rom. Live freedom!
are there some news? i've founded this video, but I can't understand if this is related to the thread in android development...
in youtube: watch?v=hglLF3dM8Zk (i'm not allowed to post link ^^ )
Kayant had released an alpha preview.. but the ubuntu project will be helpful iff we some how boot up 3.0.x kernel with RIL
Sent from my MB526 using xda premium
compiling AOSPA 3.+ for HTC ONE V (primou)
hello everyone as we all know now all developers are busy with there own rom and many of them left this HOV thread.
We don't have many developers to build a new rom for us, that's why we people are having less number of rom in HOV's thread.
So i have decided to start a new project in which we will c compile the AOSP3.+ rom from the source, but the problem is I am not a developer or programmer or any kind of genius.
so what i am going to do is i need a team in which we all can work together and try our best to port this rom from source successfully
anyone who is interested in this can reply to this thread, I'll be glad to having as much as people possible
If i get a team then, we all gonna work according to this guide -> http://forum.xda-developers.com/showthread.php?t=1863547
4.2.2 or 4.3?
well 3+ is 4.2.2
Seraz007 said:
well 3+ is 4.2.2
Click to expand...
Click to collapse
The lateset for many devices is running on 4.3.x, but I'm assuming it's 4.2.2 since the branch for 4.3.x is jb43.
MameTozhio said:
The lateset for many devices is running on 4.3.x, but I'm assuming it's 4.2.2 since the branch for 4.3.x is jb43.
Click to expand...
Click to collapse
3+ and 3.40 are two different versions
anything above 3.40( i think that is the version) is 4.3
Seraz007 said:
3+ and 3.40 are two different versions
anything above 3.40( i think that is the version) is 4.3
Click to expand...
Click to collapse
PA 3.60 for hTC Desire is 4.2.2
Anyway,back on topic.
so you joining @MameTozhio
Sure, I also found a device tree on github.
MameTozhio said:
Sure, I also found a device tree on github.
Click to expand...
Click to collapse
awesome! now the thing is we need atleast 2-3 people so that we can start our project and i hope you have Ubuntu 12.04 (Precise Pangolin) 64-bit in pc
gulsher said:
awesome! now the thing is we need atleast 2-3 people so that we can start our project and i hope you have Ubuntu 12.04 (Precise Pangolin) 64-bit in pc
Click to expand...
Click to collapse
Linux Deepin 12.12.1 (Raring based) 64-bit
Java 6 from Webupd8 ppa.
:good: I'm interested
i m also very new to Android rom development
but will try my best (100%) to support the project
i don't have ubuntu but i can get ready in a VM..do we need x64..x32 wont suffice
blade22 said:
:good: I'm interested
i m also very new to Android rom development
but will try my best (100%) to support the project
i don't have ubuntu but i can get ready in a VM..do we need x64..x32 wont suffice
Click to expand...
Click to collapse
It's harder with 32-bit, I believe. But I know you can build on 32-bit.
blade22 said:
:good: I'm interested
i m also very new to Android rom development
but will try my best (100%) to support the project
i don't have ubuntu but i can get ready in a VM..do we need x64..x32 wont suffice
Click to expand...
Click to collapse
great but i suggest that you make space for ubuntu it would be a better option, if you can or else vm is fine
Vm is fine if you have a LOT of ram, because otherwise the compiling process will take days lol..
If you make a partition, make it at least 70gb, some sources are even 50gbs..
mr_nooby said:
Vm is fine if you have a LOT of ram, because otherwise the compiling process will take days lol..
If you make a partition, make it at least 70gb, some sources are even 50gbs..
Click to expand...
Click to collapse
50 gbs wth in it
I really want to join , but my pc are windows 32bit and 2gb ram D:
sent from my Sensation XE
Mine is 4gb ram dual core 2.4ghz, and it goes pretty well. But school is starting soon so I have no more time to join the team..
Oh.. school...
I start next week.. I can't join unless I get free time..
danishaznita said:
50 gbs wth in it
I really want to join , but my pc are windows 32bit and 2gb ram D:
you can join even my pc config also is same 32bit with 2gb ram , if it will cause problem we will other members of the team for compiling ]
Click to expand...
Click to collapse
@MameTozhio even I am also having college infact the exam are coming soon, but we could do work slowly accordingly , we don't need to do anything in hurry so @mr_nooby you can also join
gulsher said:
@MameTozhio even I am also having college infact the exam are coming soon, but we could do work slowly accordingly , we don't need to do anything in hurry so @mr_nooby you can also join
Click to expand...
Click to collapse
Okay but our timezone.........
Hmm
sent from my Sensation XE
mr_nooby said:
Vm is fine if you have a LOT of ram, because otherwise the compiling process will take days lol..
If you make a partition, make it at least 70gb, some sources are even 50gbs..
Click to expand...
Click to collapse
70gb need to free some space then
is there a specific version of Linux OS needed..as suggested by OP ubuntu..can't we use redhat,linspire etc etc
I thought of developing a kernel so that i can use it with my CM11 that im going to port shortly. I thought I'll compile the stock kernel from source itself. I use android pre-built tool chain (arm-eabi-4.6)
I get a lot of compiler errors on stock kernel without any modifications itself...
Do i need to change my tool chain?
Sent from my One V using XDA Free mobile app
I never tried to build the stock kernel, but I think they did it with the android 4.0 toolchain.
To run CM, you need a CM-Kernel. You have to port things from the stock or a custom kernel (like Hellboy by maxwen) to the cm11 kernel.
Try to use rastomanchiks kernel sources (https://github.com/rastomanchik/android_kernel_htc_primou). This kernel is mostly working, stable and has a good battery life now.
I'd also like to build cm11, but my download speed is to slow to download the sources.
Exactly. Even my download speed is slow. And i have a cap also. After 8GB, my download speed drastically decreases. It takes ages to sync the sources...
Sent from my One V using XDA Free mobile app
How different is Cm kernel from stock? I mean what changes should i make?
Sent from my One V using XDA Free mobile app
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Help
jonas2790 said:
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Click to expand...
Click to collapse
Yeah. How do I port?
What happened to your CM12 project?
hehaichi said:
Yeah. How do I port?
What happened to your CM12 project?
Click to expand...
Click to collapse
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
jonas2790 said:
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
Click to expand...
Click to collapse
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
hehaichi said:
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
Click to expand...
Click to collapse
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
jonas2790 said:
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
Click to expand...
Click to collapse
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
hehaichi said:
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
Click to expand...
Click to collapse
Yes you can use a prebuilt kernel, but it will only work if the kernel supports you cm version.
You apply patches to a kernel by changing files or directories in the kernel. For example you can use another fs module (maybe with more functions) by copy and pasting the folder for the module from another kernel. The problem is, the new module may require some functions your kernel does not have so it won't compile.
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
hehaichi said:
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
Click to expand...
Click to collapse
1. It would be much, much, much work.
2. I think there are some device-specific drivers that only work with 3.0
I'm ready to do that work only if i knew how to...
Sent from my One V
hehaichi said:
I'm ready to do that work only if i knew how to...
Sent from my One V
Click to expand...
Click to collapse
Try to get into it yourself or talk with people who know about kernel developement, I'm also new to android developement.