I apologize for my bad English I am Italian and use google translate
I need a guide on how to compile Android from source
(the ParanoidAndroid for accuracy)
which linux distro to use?
which packages to install?
which commands to use?
I have a lot of time free
and a core i5 cpu
I think that to compile Android from source
but I need a guide
then I ask you developers, you can post a guide
----------------------------------------------------------------------------------------
write from my pc using win8 e programming a websites
bomdia said:
I apologize for my bad English I am Italian and use google translate
I need a guide on how to compile Android from source
(the ParanoidAndroid for accuracy)
which linux distro to use?
which packages to install?
which commands to use?
I have a lot of time free
and a core i5 cpu
I think that to compile Android from source
but I need a guide
then I ask you developers, you can post a guide
----------------------------------------------------------------------------------------
write from my pc using win8 e programming a websites
Click to expand...
Click to collapse
Well, you need a lot of work to get a working build, as i currently compile CM9 for SXL.
Recommended distros: Ubuntu 12.04 Precise / Linux Mint 13 Maya with Cinnamon interface to have the best linux experience << The best linux distro i ever used
Packages: Well, you need to check the Paranoid site to download the repo for ICS or JB variant of source-code.
Commands: Lots of commands, there are tutorials online. Example >> here
After this, you will need the device tree for SXL, i have one that is deprecated (not updated for some time), it does not work the variant uploaded here, but i will upload it.
You will need the vendor files, i also have the files but as the build of CM9 don't work, i haven't upload them anywhere untill i can get an at least experimental build that boots
Link for android device tree for sxl by me here
There is a lot of work and there aren't any specific guides on how to do this, you need to join communities and be a pain on the ass for them untill you learn how to do this.
I hope this helps anyways
Lexmazter said:
Well, you need a lot of work to get a working build, as i currently compile CM9 for SXL.
Recommended distros: Ubuntu 12.04 Precise / Linux Mint 13 Maya with Cinnamon interface to have the best linux experience << The best linux distro i ever used
Packages: Well, you need to check the Paranoid site to download the repo for ICS or JB variant of source-code.
Commands: Lots of commands, there are tutorials online. Example >> here
After this, you will need the device tree for SXL, i have one that is deprecated (not updated for some time), it does not work the variant uploaded here, but i will upload it.
You will need the vendor files, i also have the files but as the build of CM9 don't work, i haven't upload them anywhere untill i can get an at least experimental build that boots
Link for android device tree for sxl by me here
There is a lot of work and there aren't any specific guides on how to do this, you need to join communities and be a pain on the ass for them untill you learn how to do this.
I hope this helps anyways
Click to expand...
Click to collapse
thanks a lot I think I start tomorrow I'm a little tired
Hi just so you know you won't be able to compile Paranoid Android for ICS from source as it was never released.
If you can get JB to work then you will not only be a hero but also be able to use Paranoid Android source
I have a problem I can not download the sources of the paranoid in any way
help (or build the sources normal Android?)
Did you follow a guide how to set up the environment in linux? Or Mac.. the way you can download sources is git clone and then the git link. There are many guides on doing that part. Also when I download source it times out in a 4 mb/s connection and I need to use a better connecyion
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
anders3408 said:
Did you follow a guide how to set up the environment in linux? Or Mac.. the way you can download sources is git clone and then the git link. There are many guides on doing that part. Also when I download source it times out in a 4 mb/s connection and I need to use a better connecyion
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Click to expand...
Click to collapse
aa ok but the guide I was reading did not say that it was necessary to clone each of the sources piece by piece, but he said to use a single link.
I have linux mint 14 with cinnamon (from the 13 consigliatami lextmazter I do not work)
both in Italy and in spite of my connection is approximately 16 mb / s (88% above the national average)
Post link to guide.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
bomdia said:
aa ok but the guide I was reading did not say that it was necessary to clone each of the sources piece by piece, but he said to use a single link.
I have linux mint 14 with cinnamon (from the 13 consigliatami lextmazter I do not work)
both in Italy and in spite of my connection is approximately 16 mb / s (88% above the national average)
Click to expand...
Click to collapse
I do not recommend Linux Mint 14 as it is new edition, based on new Ubuntu version 12.10 if i remember good, don't know for sure, that's why, on Ubuntu 12.04 building is supported, even though on some guides it is said that on 12.04 it is experimental, well, it was, now it should be stable.
Also, if you want to port things like Paranoid or PAC you should start with AOSP or CM9 or AOKP, to put it short, versions that have guides and source codes on their sites. In my opinion CM is the best thing to start with, that's why i started CM9, after that you can easily port every 4.0.4 AOSP based ROM.
The same thing applies to JB, if you can port or build AOSP or CM10, you can port every JB AOSP based ROM very easily following only a few basic steps, that's how things work in this hood
Off-topic: I was a little distracted from building/testing/devving because of the school affairs, but today i will resume my work on CM9, if things work well, i will have a bootable build this very evening.
same as lexmazter, sound correct. the hard part is build CM9 rom, rest is pretty easy.
Lexmazter, i am about to try take a ramdisk from cm9 primou and make changes in every lines and see if i can get it to work with runnymede. if it does we will have a working aosp bootimg. i have compiled a zimage from source and it works with wifi and bt and so on in sense rom, also zimage works with cm9 with wifi.
lexmazter, can you please take a bencmark test with antutu 3.0.1, the new one, and post screenshot of the score and wich rom you are in ? they have made the test much diffrend so score is diffrend in 3.0.1 than older , so i have nothing to compare it to
anders3408 said:
same as lexmazter, sound correct. the hard part is build CM9 rom, rest is pretty easy.
Lexmazter, i am about to try take a ramdisk from cm9 primou and make changes in every lines and see if i can get it to work with runnymede. if it does we will have a working aosp bootimg. i have compiled a zimage from source and it works with wifi and bt and so on in sense rom, also zimage works with cm9 with wifi.
lexmazter, can you please take a bencmark test with antutu 3.0.1, the new one, and post screenshot of the score and wich rom you are in ? they have made the test much diffrend so score is diffrend in 3.0.1 than older , so i have nothing to compare it to
Click to expand...
Click to collapse
5941 no OC with LTX Kernel v0.7 and Sense 3.0 by fshami, also, i think i found the right ramdisk for now for CM9, it solved the dalvik-permissions, now i still need to boot the build, still trying to figure what is wrong here and why it hangs after Android is upgrading... >> Starting applications.
I can work more on my device now as i have a cheap second phone to use if for calls and sms.
so then I decided, when I start buildare the source of AOSP Android 4.2 jellybean I think it's easier for me to start.
I had to use because the new mint old man crashed always
bomdia said:
so then I decided, when I start buildare the source of AOSP Android 4.2 jellybean I think it's easier for me to start.
I had to use because the new mint old man crashed always
Click to expand...
Click to collapse
As a recommandation, i would recommend building AOSP 4.0.4, it is easier to start and has more chances of working, after that, you have the experience and the headstart to work on 4.1 and only after that on 4.2.
Just start with baby-steps, it is easier and increases the chances of success.
Lexmazter said:
As a recommandation, i would recommend building AOSP 4.0.4, it is easier to start and has more chances of working, after that, you have the experience and the headstart to work on 4.1 and only after that on 4.2.
Just start with baby-steps, it is easier and increases the chances of success.
Click to expand...
Click to collapse
ahh ok then I try to go with 4.1 if I can not then step 4.0.4
bomdia said:
ahh ok then I try to go with 4.1 if I can not then step 4.0.4
Click to expand...
Click to collapse
Well, i recommend this because i'm still building 4.0.4 and i haven't successfully booted a build, so that's why i say this, because if you get the 4.0.4, in short terms, all you need to change for 4.1 is the graphics driver, but for 4.2 i don't know for sure, too new for me and i'm still trying to get 4.0.4 to air
then my kernel is not so bad 5838 with sense 4.1 v. 1.5.1 and still missing some improvments
which ramdisk are you using, zimage from stock rom should get it to boot, but the ramdisk as you know need to be changed to cm9. when you compile from source it should also make a ramdisk that will fits the rom, i think it is best to check what the diffrence in the new ramdisk and the old one with VM errors and then fix them, perhaps it will boot then ? one specific compiled by you ? post a logcat in your cm9, had also some bootloop in my cm9 port but got it booting.
anders3408 said:
then my kernel is not so bad 5838 with sense 4.1 v. 1.5.1 and still missing some improvments
which ramdisk are you using, zimage from stock rom should get it to boot, but the ramdisk as you know need to be changed to cm9. when you compile from source it should also make a ramdisk that will fits the rom, i think it is best to check what the diffrence in the new ramdisk and the old one with VM errors and then fix them, perhaps it will boot then ? one specific compiled by you ? post a logcat in your cm9, had also some bootloop in my cm9 port but got it booting.
Click to expand...
Click to collapse
just enter the irc channel, will talk more there, no need to spam the forum with this.
The boothanging is because of the audio, the ramdisk is good, i use the LTX v0.7 zImage and ramdisk from stock edited to fit the build.
Also, the ramdisk is not made with the build, maybe if you compile the kernel with the rom, and for this you need to put the kernel online and othe things, and because of proxy, i can't and won't do that. For more details, like i said, find me on the irc.
link here
you say that jelly beans to need a new kernel? because sifting through the Internet I found this: https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources there are also drivers for jelly bean of adreno 2xx
bomdia said:
you say that jelly beans to need a new kernel? because sifting through the Internet I found this: https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources there are also drivers for jelly bean of adreno 2xx
Click to expand...
Click to collapse
yeah, those are the drivers
But they do not require a new kernel
Lexmazter said:
yeah, those are the drivers
But they do not require a new kernel
Click to expand...
Click to collapse
but I need or I do not need?
Related
Hi guys,
I stopped a while to build rom for tatoo but I continued to follow the thread.
For fun I have compiled the latest stable kernel ... if anyone cares to test it I'll put the link here.
I take this opportunity to insert a link to my kernel sources generated using HTC.
I think it's correct to use this kernel for the development of libraries on the camera and radio, as it turns out to be the only kernel you know works.
Compiling the latest kernel I have seen many great features ... but totally missing some drivers, such as those in radio ...
I do not understand this anxiety developers to have a custom kernel and the most updated ... But I think it is appropriate to start building a secure kernel. When the camera and the radio works then you can create as many kernels you want ... but not before.
This is my thought ... meanwhile I'll use this post to whoever wants to download the kernel and HTC for those who want to test my kernel 2.6.35.4.
Kernel_2.6.29_HTC
contain for shure all drivers for FMRadio,camera,bt ecc and all htc patches (if presents). this kernel il generated from HTC kernel source downloaded from htc site.
Features added: ext3 and ext4 partitions support
Kernel_2.6.35.4_v1NOT WORKING
Is a testing kernel. it is generated compiling the last stable source released on kernel.org
Kernel_2.6.35.4_v2
- FMRadio diriver inculded
- voltage and current regulator support
- Led drivers
- ext3 ext4
nice job, my friend.
francians said:
nice job, my friend.
Click to expand...
Click to collapse
is not nice... it haven't the radio drivers and i don't know if it work well...
i have only spent some time today because i have nothing to do..
it isn't a serious kernel for me...
ikxdf said:
Hi guys,
... But I think it is appropriate to start building a secure kernel. When the camera and the radio works then you can create as many kernels you want ... but not before.
Click to expand...
Click to collapse
Although I´m no dev, this is actually very sensible. I´d rather had a slightly outdated but FULLY functional kernel, than the most up-to-date but crippled one...
No source or config files or tweeks you made?
Good day ikxdf!
Seg
segway_ said:
No source or config files or tweeks you made?
Good day ikxdf!
Seg
Click to expand...
Click to collapse
i will upload the source and the config soon
The attached kernel Kernel_2.6.35.4_v1_[ikxdf].zip does not even boot.
No adb no something on /proc/last_kmsg after boot to recovery!!
Nice try ikxdf.
Seg.
segway_ said:
The attached kernel Kernel_2.6.35.4_v1_[ikxdf].zip does not even boot.
No adb no something on /proc/last_kmsg after boot to recovery!!
Nice try ikxdf.
Seg.
Click to expand...
Click to collapse
This is because he based it on the stock Linux kernel, and not the android branch... I don't even know if it's compiled for ARM or x86, but I'll check that soon...
Sent from my HTC Hero using XDA App
EDIT: I have checked for the kernel architecture and it is compiled for ARM. I also took the liberty of extracting the config from it, and saw that it seriously need lots of attention. I have attached a copy of the config below... BTW: good luck with getting this to work
segway_ said:
The attached kernel Kernel_2.6.35.4_v1_[ikxdf].zip does not even boot.
No adb no something on /proc/last_kmsg after boot to recovery!!
Nice try ikxdf.
Seg.
Click to expand...
Click to collapse
please sega-way evitate your sarcasm and read well before writing:
ikxdf said:
is not nice... it haven't the radio drivers and i don't know if it work well...
Click to expand...
Click to collapse
ikxdf said:
For fun I have compiled the latest stable kernel ... if anyone cares to test it I'll put the link here.
Click to expand...
Click to collapse
if u don't know i haven't a tatto for testing.
if anyone want test and send me the error i will try to fix if i find the time.
for me the only correct kernel is the 2.6.29 compiled from the htc source. All other kernel is only a game.
For the next time...learn to read all post before writing.
Thanks
kiljacken said:
This is because he based it on the stock Linux kernel, and not the android branch... I don't even know if it's compiled for ARM or x86, but I'll check that soon...
Sent from my HTC Hero using XDA App
EDIT: I have checked for the kernel architecture and it is compiled for ARM. I also took the liberty of extracting the config from it, and saw that it seriously need lots of attention. I have attached a copy of the config below... BTW: good luck with getting this to work
Click to expand...
Click to collapse
thanks Kill. I can't take a look now but next week i will try to recompile it. Please i need a .config of a original 1.6 ROM...can u upload it here?
ikxdf said:
thanks Kill. I can't take a look now but next week i will try to recompile it. Please i need a .config of a original 1.6 ROM...can u upload it here?
Click to expand...
Click to collapse
from the tattoo.. it was gz now is zip
ikxdf said:
please sega-way evitate your sarcasm and read well before writing
Thanks
Click to expand...
Click to collapse
Its just a feedback...
Sorry if you take it as something else....
Seg
i'm trying to made this kernel booting and have add some features:
- FMRadio diriver inculded
- voltage and current regulator support
- Led drivers
if anyone want test it i will upload it today
uploaded in first posts
I've been away from the Tattoo scene since we got root on this little device.
I'm currently interested in getting psfreedom to run on Tattoo but it seems that the stock HTC kernel is crippled (missing usb stuff). If your kernel is at least bootable, this would be a nice place to start
mainfram3 said:
I've been away from the Tattoo scene since we got root on this little device.
I'm currently interested in getting psfreedom to run on Tattoo but it seems that the stock HTC kernel is crippled (missing usb stuff). If your kernel is at least bootable, this would be a nice place to start
Click to expand...
Click to collapse
if u are talking about 2.6.35.4 version you have to try if it can boot because i haven't a tattoo for test it.
I have sell my tattoo after 2 week but all great users of this thread have always made a great testing job for me and for my rom.
If anyone want test if this kernel is booting or not i will contine to develope it.
If it doesn't boot and adb will start i need a logcat.
if u are talking of the original htc kernel 2.6.29 version it is already working on my rom (Pancake) .
i will release sonn the wlan.ko module for 2.1 and for 2.2 roms for the 2 versions of kernel.
Hi, ikxdf!
I'm willing to try your kernel. I am quite an experienced linux user of desktop and server but I'm quite new regarding ROM flashing. But still, from what I gather I have to flash your kernel archive in the boot sector, right?
I have AmonRA's recovery installed and tested. And I'm eager to try cooked stuff as I've just gotten my Tattoo out of service today after 3 weeks!!! I was so dissapointed in having my old Nokia again.
Hey guys, I've seen some people that are interested in learning how to develop for Android, so I thought I 'd share my Android Dev Resources bookmarks folder with all of you It's grown significantly since I last showed it to you guys in my CM9-Woot thread.
How to port ROM's to the Desire S (Similar to our phone)
Init.d Script guide
Modding ICS
Build.prop tweaks
ICS style settings mod
Porting Android
Chef Central XDA
GreenROM Project
Android App Development Tutorial
How to port cm7,9,10
How to properly de/recompile APK's
Remap search button to recent apps
Google Android Training
Marakana tech tv (Android tutorials)
CPU Governors explained
Jellybean porting
How to- Compiling from source
How to make you're own custom ROM
How to compile CM10
Compile JB on ubuntu
Build.prop mod- Project Butter
Github.com
XDA Android software and hacking
Building your first kernel
Compile ICS on Ubuntu
CyanogenMod wiki- Compile CM9
Hopefully this inspires more people to learn how to develop for our phone
ZaySk said:
Hey guys, I've seen some people that are interested in learning how to develop for Android, so I thought I 'd share my Android Dev Resources bookmarks folder with all of you It's grown significantly since I last showed it to you guys in my CM9-Woot thread.
How to port ROM's to the Desire S (Similar to our phone)
Init.d Script guide
Modding ICS
Build.prop tweaks
ICS style settings mod
Porting Android
Chef Central XDA
GreenROM Project
Android App Development Tutorial
How to port cm7,9,10
How to properly de/recompile APK's
Remap search button to recent apps
Google Android Training
Marakana tech tv (Android tutorials)
CPU Governors explained
Jellybean porting
How to- Compiling from source
How to make you're own custom ROM
How to compile CM10
Compile JB on ubuntu
Build.prop mod- Project Butter
Github.com
XDA Android software and hacking
Building your first kernel
Compile ICS on Ubuntu
CyanogenMod wiki- Compile CM9
Hopefully this inspires more people to learn how to develop for our phone
Click to expand...
Click to collapse
thanks for that mate if anything i wanna try build a kernal from the htc source so that we can get your cm9 port or kaijuras fully working
naathaanb96 said:
thanks for that mate if anything i wanna try build a kernal from the htc source so that we can get your cm9 port or kaijuras fully working
Click to expand...
Click to collapse
Meh, don't bother with my CM9 port, the code for that build is ancient in technological terms. I'll be compiling CM10 or AOKP JB for you guys next month when my bandwidth meter restarts. I waster a LOT of bandwidth trying to sync the CM10 code and having it run into a fatal error at the end. Such a piss off.
ZaySk said:
Meh, don't bother with my CM9 port, the code for that build is ancient in technological terms. I'll be compiling CM10 or AOKP JB for you guys next month when my bandwidth meter restarts. I waster a LOT of bandwidth trying to sync the CM10 code and having it run into a fatal error at the end. Such a piss off.
Click to expand...
Click to collapse
stuff making my own rom haha ill use kaijuras as the base. just downloading and installing ubuntu 64bit now so i should "HOPEFULLY" have a kernal compiled by the end of today from htc source. which hopefully fixes camera and everything
naathaanb96 said:
stuff making my own rom haha ill use kaijuras as the base. just downloading and installing ubuntu 64bit now so i should "HOPEFULLY" have a kernal compiled by the end of today from htc source. which hopefully fixes camera and everything
Click to expand...
Click to collapse
Let me know how ubunto is as an OS. As I've thought about dual booting with ubunto or OSX. Just haven't had the time yet .....
Sent from my HTC Incredible S using Tapatalk 2
vizzy said:
Let me know how ubunto is as an OS. As I've thought about dual booting with ubunto or OSX. Just haven't had the time yet .....
Sent from my HTC Incredible S using Tapatalk 2
Click to expand...
Click to collapse
should be up and running in about 30 mins
vizzy said:
Let me know how ubunto is as an OS. As I've thought about dual booting with ubunto or OSX. Just haven't had the time yet .....
Sent from my HTC Incredible S using Tapatalk 2
Click to expand...
Click to collapse
I like Ubuntu a lot. I've only used 11.10, and 12.04 but I personally prefer 11.10 due to the fact that 12.04 is "only experimentally supported for compiling ROM's and not guarenteed to work". I also find 11.10 to be significantly more stable and smooth than 12.04, but it could be because of my older computer and processor.
If you're good with technology and computers (Which you most likely are since you're on XDA) then you should have no problem learning how to use Ubuntu. There are a little bit more quirks in Ubuntu than in Windows, and the problems typically have to be fixed in the Terminal, but it's not that bad. I personally enjoy using Ubuntu, I found it to be very easy to learn how to use. (But I'm a major nerd )
Edit: If you want to know anything else about Ubuntu, let me know and I'll fire up my VM.
ZaySk said:
I like Ubuntu a lot. I've only used 11.10, and 12.04 but I personally prefer 11.10 due to the fact that 12.04 is "only experimentally supported for compiling ROM's and not guarenteed to work". I also find 11.10 to be significantly more stable and smooth than 12.04, but it could be because of my older computer and processor.
If you're good with technology and computers (Which you most likely are since you're on XDA) then you should have no problem learning how to use Ubuntu. There are a little bit more quirks in Ubuntu than in Windows, and the problems typically have to be fixed in the Terminal, but it's not that bad. I personally enjoy using Ubuntu, I found it to be very easy to learn how to use. (But I'm a major nerd )
Click to expand...
Click to collapse
8 mins left on my download
Thank you for your hardwork!
By the way, which one did you tried from the above links?
I have gone thru some of the links, some does not work with
sense?
vinboy3 said:
Thank you for your hardwork!
By the way, which one did you tried from the above links?
I have gone thru some of the links, some does not work with
sense?
Click to expand...
Click to collapse
My pleasure I've read them all, and tried out a majority of them myself. Some work, some don't but they all teach you valuable lessons and are worth reading. Not all of them are for Sense ROM's, only some of them are. I also really want to compile CM10 which is why I also have a lot of AOSP links. Some are also app tutorials, I'm also trying to learn how to write apps.
That's an impressive list, thanks for sharing.
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here -
http://forum.xda-developers.com/showthread.php?p=33291894
He'll probably help us out if we make some progress in booting up Codename with it at least
TheDareDevil said:
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here - http://forum.xda-developers.com/showthread.php?t=1899335&page=38
He'll probably help us out if we make some progress in booting up Codename with it at least
Click to expand...
Click to collapse
Upon the exit of JB roms ago, were used GB modified kernel, now with source code maybe will be possible to compile a fully working kernel, but afaik there are no 3.x kernel for JB, maybe someone is working out of xda on irc channel but don't known..
Sadly I do not have much competence, plus I don't have the phone it's to repair....
There is kernel 3 for incredible 2 and desire s..may be someone can port it..
Sent from my HTC Incredible S using xda app-developers app
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
TheMegosh said:
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Well tbh honest a working GB kernel would do too.
Like the front camera and chrome and screen flickering etc.
Damn I wish kaijura was here
Sent from my HTC Incredible S using xda app-developers app
CyanideJack said:
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Click to expand...
Click to collapse
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
ZaySk said:
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
Click to expand...
Click to collapse
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
CyanideJack said:
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
Click to expand...
Click to collapse
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
l0st.prophet said:
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
Click to expand...
Click to collapse
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
ZaySk said:
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
Click to expand...
Click to collapse
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
markj338 said:
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
Click to expand...
Click to collapse
I know, it would be going down a pretty redundant path. If I was able to port over a JB ROM using nik's ROM's as a base, then my ported ROM would inherit all the same bugs nik's ROM's already have.
I wish kaijura was still around, I have so many questions I want to ask about compiling from source! Luckily lordclokan was a massive help to me in that regard. Kaijura's github hasn't seen action in months either, sadly.
Forgive my ignorance, but isn't the Desire HD essentially our device with a bigger screen and less memory? That being the case, could we not just port across one of the 3.0 Kernels from that?
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Well you can prolly get ideas from adi ( he posted http://forum.xda-developers.com/showpost.php?p=33302707&postcount=387 not sure if you saw it) he seems to know what's up.
TheDareDevil said:
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
So it looks like the furthest things got regarding a 3.0 Kernel was;
Adi_Pat said:
chan
Ok so 2.6.35 works with Jellybean. Why not pack the ramdisk with zImage compiled from 3.0.y sources(Considering you are using standard boot.img format[?]) Because to get it to boot, you would not require any hacks/changes to source, editing ramdisk(init.rc) is enough to make it boot initally.
EDIT: You may also need to change init binary.
Click to expand...
Click to collapse
l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Very interesting, thanks for the informative post. :good:
zaysk said:
very interesting, thanks for the informative post. :good:
Click to expand...
Click to collapse
happy november!!!
markj338 said:
happy november!!!
Click to expand...
Click to collapse
A very happy November indeed
This is Strictly Development i u know something plz share if don't then be slient
What is ION .?
Noob way :- It makes things awsome -by lauppenstepperwolf
there is awsome explaination on LX git Wiki
LX said:
#### What is Shared Memory?
Memory is usually private; an app takes a chunk and nothing else can access it.
Sometimes, it makes sense to share memory between processes; for example, an app writes to the screen buffer, while the gfx driver reads that same buffer to put it on the screen. You need a special memory system for that.
####PMEM vs. ION
Back with Gingerbread, every ARM chip maker (Qualcomm, TI, nVidia, Samsung, more?) had their own way of doing shared memory. The Qualcomm way was a system called **PMEM**.
Problem: when a vendor sells a chip to Sony and Samsung, he needs to write two drivers, one for each shared memory system.
To reduce maintenance efforts, Google introduced **ION**, a unified shared memory system, that all vendors use since ICS
Problem: from ICS forward, Qualcomm only provides graphics drivers for ION. PMEM is obsolete.
For a while, stuff still worked, but it is getting worse for us - see the Google Maps app for example.
####Move to ION
An option is to rework the kernel, replace the PMEM system with ION, and replace the old PMEM drivers with newer ION drivers. A common problem on several old devices is, that the camera chip is non-standard, and Sony (Samsung, HTC) never wrote ION drivers for the old cameras. Moving to ION then means you lose the camera completely.
A new solution is to move the kernel to ION, but have a PMEM system on top of ION so that the old camera libs can connect to it. As far as I know, this was pioneered by the Dev_Connection team that maintains the Samsung S+ i9001 (great team, hats off to Christopher83 especially).
Another implementation of an ION/PMEM hybrid was made by galaxyfreak for the HTC Explorer (Pico).
The i9001 and the Pico have similar hardware to our 2011 Xperias (2011, MSM, 512MB RAM, similar specs).
Feedback for the ION builds is very positive. Performance is good and it solves some graphics problems like the Google Maps flickering, and it solves the slow browser.
####ION on LegacyXperia
It would be the next big step after the 3.x kernel, but, it's a lot of work.
On the i9001, 8 devs work on 1 device, while on our side, 1 dev works on 8 devices.
The i9001 approach was to migrate 10.1 to ION, then 10.2, then 11; instead of directly doing 11-ION.
Click to expand...
Click to collapse
ETA :- Nowhere to release
============================================================================
THIS IS A REWORK ON nAa-kernel to use ION but with no video recording support ... until mike does spread his awsome magic with his new scratch ported kernel...
Source :- http://www.github.com/rebel-x/msm7x30-3.4.x-nAa
Current Progress : Intial Pushes done "yay" lets hope it boots
NOTE :- We need your help , i m not able to do alone since i have very limited knowledge about kernels , Please forgive me if my coding somewhere wrong cause
ok so thank you i will post progress as we all get step further ,
thank you
Credits :
Mike : we all know why
nAa : Awsome dev
szezso : always helpful
XDA:DevDB Information
ION-Kernel, a Kernel for the Sony Ericsson Xperia Arc
Contributors
officiallysonyrebel, szezso, Mike
Kernel Special Features:
Version Information
Status: Testing
Created 2014-01-08
Last Updated 2014-01-07
Don't ever give up!
you also need To build rom with ion accelator
offical
its offical jb kernel ?
mahsun72 said:
its offical jb kernel ?
Click to expand...
Click to collapse
Can you read? It's not even official. It could be also for CM11 since he mentioned browser lag, which is an existing bug in CM11.
To OP, I should be able to check the coding and whatnot. Only problem is I'm currently in the army and unable to access my computer on weekdays.
僕のLT18iから送られてきた
@n1kolaa i guess you can start work on this if you have time.. I have seen you working.. Seems a real genius can you?
Sent from my Nexus 5 using Tapatalk
I should also be able to check the code as I'm proficient in C++. Let me know where I can help out, it's a good initiative.
ION and PMEM should'nt be device specific, no ? Isn't the work done on i9001 reusable here ?
First it could be interesting to locate all patches applied on the kernel to implement the hybrid memory allocation.
Edit :
I suppose the kernel in question is this one :
https://github.com/AriesVE-DevCon-TEAM/samsung-kernel-msm7x30/tree/cm-11.0_ion_pmem_adsp
Boudin said:
ION and PMEM should'nt be device specific, no ? Isn't the work done on i9001 reusable here ?
First it could be interesting to locate all patches applied on the kernel to implement the hybrid memory allocation.
Edit :
I suppose the kernel in question is this one :
https://github.com/AriesVE-DevCon-TEAM/samsung-kernel-msm7x30/tree/cm-11.0_ion_pmem_adsp
Click to expand...
Click to collapse
ion is different for every device i guess
Update :
finished initial kernel part (lets hope it boots know)
vishal_android freak said:
@n1kolaa i guess you can start work on this if you have time.. I have seen you working.. Seems a real genius can you?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
im now focus on shool,also i give my arc to my sister i now have only idol mini
n1kolaa said:
im now focus on shool,also i give my arc to my sister i now have only idol mini
Click to expand...
Click to collapse
Well, that's still fine.. Mini you have for testing.. Give it a try, you never know what you can end up with, probably a working kernel with ion support.. :thumbup:
Regards,
vishal_android freak
vishal_android freak said:
Well, that's still fine.. Mini you have for testing.. Give it a try, you never know what you can end up with, probably a working kernel with ion support.. :thumbup:
Regards,
vishal_android freak
Click to expand...
Click to collapse
its idol mini form alcatel,how can i test new kernel with it explain it to me
n1kolaa said:
its idol mini form alcatel,how can i test new kernel with it explain it to me
Click to expand...
Click to collapse
Ohh.. My bad.. Sorry..
Sent from my Nexus 5 using Tapatalk
I think I can develop based on this. Is the ION kernel actually booting and working preperly etc. ?
CedArctic said:
I think I can develop based on this. Is the ION kernel actually booting and working preperly etc. ?
Click to expand...
Click to collapse
i have completed allocation but that f**kin msmfb code is a heck since we are using drivers from 3.0 need a lot of work
rebelos said:
i have completed allocation but that f**kin msmfb code is a heck since we are using drivers from 3.0 need a lot of work
Click to expand...
Click to collapse
all the best bro.. Any improvements?
gpkumaran said:
all the best bro.. Any improvements?
Click to expand...
Click to collapse
yea its compiling know but no where Close to Boot ... i have changes locally purchased a XMP with screen destroyed only for kernel debugging purpose
rebelos said:
i have completed allocation but that f**kin msmfb code is a heck since we are using drivers from 3.0 need a lot of work
Click to expand...
Click to collapse
Thanks for your work! I love KK rom and im wait ion kernel :thumbup:
Regards
To many 4.4 roms are coming out....in my opinion all kitkat devs should focus on just 2 roms and this really good kernel.
At least with 2 different 4.4 roms there is still competiton for improvement without scattering work to much.
A nicely developed kitkat will save out Arc from retirement.
Btw i was wondering, since HDMI sources for kitkat are not available, would it be possible to create-compile a MHL compatibility for our arc? so we can use MHL accessory instead of HDMI? Or a virtual machine on kitkat running the stock ICS HDMI feature?
I'm no dev so i have no idea how hard it could be.....just asking out of curiosity, many use hdmi on arc for movies or android desktop with OTG mouse and keyboard. Its really a pity we cannot make it work on 4.4 yet.
Dr.SAM88 said:
To many 4.4 roms are coming out....in my opinion all kitkat devs should focus on just 2 roms and this really good kernel.
At least with 2 different 4.4 roms there is still competiton for improvement without scattering work to much.
A nicely developed kitkat will save out Arc from retirement.
Btw i was wondering, since HDMI sources for kitkat are not available, would it be possible to create-compile a MHL compatibility for our arc? so we can use MHL accessory instead of HDMI? Or a virtual machine on kitkat running the stock ICS HDMI feature?
I'm no dev so i have no idea how hard it could be.....just asking out of curiosity, many use hdmi on arc for movies or android desktop with OTG mouse and keyboard. Its really a pity we cannot make it work on 4.4 yet.
Click to expand...
Click to collapse
A better Kitkat .. lets summerize current kernel situation
1. nAa 3.4 full of hacks
2. using drivers and stuffs from 3.0.x
3. Stuck on Abandoned PMEM {with every increasing android version we are using patches more than before to maintain PMEM causing soo many graphic lags
4. msm_fb code /* lets not focus on it currently */
why this mess /* to bring 3.4 kernel faster */
i m trying on 3.0.x-nAa kernel cause it is Pure CAF and also mike is working on Pure CAF 3.4.x MHL enablin gis such a lot and lot of work we are not in fully stable stage to look at MHL and other workaround first..
our device is a 3 year old piece of hardware without camera and HDMI libs using outdated kernel and drivers what should be the main goal
1. To make kernel updated with current sources
2. then make things working
3. then wprkaround for all abandoned hardware(like HDMI)
hope u know why we are focus on kernels and roms know ... and to come at point of compeion in roms
there is no compeition we are not selling our products .. we are working cause we like it and more roms means more respect for developers who are working tirelessly on maintaining those roms @Marchinho6 please no these kinds of post ..!these will spam thread
Hi developers, I'm a newbie for developing Android. Can i ask you all? How do you build and develop Resurrection Remix,CyanogenMod,Crdroid,AOSP,etc? I want to build and develop my own rom,please?:crying: Thanks.
Look on their tutorials...
Having a separate computer for doing builds is a huge difference. The amount of storage and RAM it takes to build these ROMs is large. I have tried to build from source many times on my laptop. Get a dedicated build machine with enough memory and storage to complete the builds.
Rezei said:
Look on their tutorials...
Click to expand...
Click to collapse
I have been working on building from source for over a year now. I have followed many different tutorials for repo and building. I still have had no luck. I have not given up yet. Every video I have watched makes it look easy, but it is not that easy. Just now I have had gnults_handshake TCP errors when repo is going on. It isn't all that easy to debug Linux commands when building a build environment.
So I finally built CM 11, 12.1, and CM 13 from source. It took one successful build to make the difference. Good stuff!
Can you point me at one of those tutorials?
Thanks
They are on this website. Have a look around.
You need a complete linux distro , you must done a dual-boot it's better , linux alone is fah , and go to see guides for terminal commands you should use , in dual-boot you must have at less 200 Gb for the distro and then you're done with fews hours and days of patience
Man, I follow this tutorial.
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763/page1
Abdullah Yusoff said:
Hi developers, I'm a newbie for developing Android. Can i ask you all? How do you build and develop Resurrection Remix,CyanogenMod,Crdroid,AOSP,etc? I want to build and develop my own rom,please?:crying: Thanks.
Click to expand...
Click to collapse
You'll need few requirement to go :
- Hardware
- 8GB RAM (more is better)
- minimum dual core CPU
- minimum 150Go storage
- Some knowledge :
- For that, I recommend you to read pages on Android Developers AOSP, looks other commits to understand how does a device tree (or hw, kernel, etc..) work, and be curious each thing you don't understand on in a device tree, check what is it (e.g.: you see "libIon", check what is "libIon")
Good luck!