look im a n00b(still learning android stuff),
so this question is just out of curosity
why cant we have kernel 2.6.32 ??
well google said froyo needs atleast 2.6.32 to run
but we here are running gingerbread smoothly on 2.6.29(thnaks to all the awsoms devs )
can someone knowledgble reply
thank you ;p
Simply because the kernel drivers needed for the X8 only exist in Linux 2.6.29 as published by Sony Ericsson.
If you would want to use a newer Kernel release (i.e. the ones Google is using for their Android builds) you need to port the drivers to that kernel version - read: make them fit the kernel.
That's a very tedious process, so it's easier for the ROM and Kernel developers to base their work upon the original SEMC Linux 2.6.29 sources.
on short: its easier to port drivers from 2.6.32 or 35 or 38 than make the base 2.6.32.... working on our phone
as b.jay said, porting kernels takes a long time, and if you recive only a couple of errors in the middle of it, BOOM, you gotta go back to the sart and track what wrong command you typed or what code is wrong etc. thats why no one has ported 2.6.32 kernel.
to many drivers to cope with, to much errors that you will recive. porting roms is easyer
thanks guyz for the answers....in short it is possible to have kernel 2.6.32....maybe nAa can port it....he has already backported some stuff.
It is possibe given someone wants to spend an insane amount of time (edit: we're talking several weeks to several months here) in forward-porting the Shakira specific drivers and additions to the ARM Linux code base.
I don't see it happen as it's a enormous undertaking for a single developer to port the whole stuff - that would require a medium-sized team of coders a) knowing what to port / b) well versed in Linux Kernel hacking / c) knowing how to code for ARM (edit: as the existing sources most likely need to be adapted to the Kernel ABI (in this case 2.6.3.x), which is not exactly stable in Linux and changes erratically as Linus' maintainers see fit. Also, don't forget that the changes need to be tested to see if the kernel boots and works flawlessly).
Don't hang your hopes too high.
need to much time to update linux version of kernel
But for instance lg optimus p350 has almost same specs but runs .32 kernel.it has same qualcomm 600 mhz cpu,ardeno 200,and 140 mb ram.so x8 has even better specs.so i dont se why this wouldnt be possible.
Sent from my GT-I5800 using xda premium
Related
Let's say that I wanted to get into android rom development, what would be a good place to start to learn. I've downloaded several e-books about android development, but they all pertain to writing applications for android OS, not really getting into modding the OS itself. I suspect I'd need to learn about linux then translate that knowledge to android?
Anybody have any good places to start or good reference materials?
It appears that none of the cyanogenmod team is even going to do anything with the Captivate, they're all working on I9000 and Vibrant, totally ignoring the Captivate. So, I thought I'd get in there and try and learn.
Building Android from source - their own site is the best for instructions on how to build android: http://source.android.com/
Building Captivate requires downloading the sources, building the kernel using the build_kernel.sh after you've fixed the toolchain paths. Or you can just use the usual linux kernel building method that the script actually does underneath.
Then you need to build eclair (or froyo). Samsung has opensourced most of the code but not all so you need to figure out how to merge vanilla eclair source into Samsung's tree, and build it. There is a readme in the source from Samsung about what to change in the build files.
You're going to be doing a lot of googling . . . I haven't figured out all the details of the Samsung eclair build so you're on your own there. Maybe others can chime in.
-Atin
atinm said:
Building Android from source - their own site is the best for instructions on how to build android: http://source.android.com/
Building Captivate requires downloading the sources, building the kernel using the build_kernel.sh after you've fixed the toolchain paths. Or you can just use the usual linux kernel building method that the script actually does underneath.
Then you need to build eclair (or froyo). Samsung has opensourced most of the code but not all so you need to figure out how to merge vanilla eclair source into Samsung's tree, and build it. There is a readme in the source from Samsung about what to change in the build files.
You're going to be doing a lot of googling . . . I haven't figured out all the details of the Samsung eclair build so you're on your own there. Maybe others can chime in.
-Atin
Click to expand...
Click to collapse
Thanks. Thats what I'm talking about, a lot of what you said seems Greek to me. I'd like to learn how to do all that. I guess, just read a lot from the google source website?
My advice would be to first learn how to go muck in the linux kernel and the Android sources in general. The Captivate code has been hacked some by Samsung so it doesn't quite follow all the rules about where files are supposed to go (there is no vendor tree for example) but at least it is a start. The google source site is the best for instructions on how to do vanilla stuff that's not hardware specific. Google around for more specific instructions related to the particular problem you are trying to solve after that.
Building working stuff at this level isn't easy. Unless you are somewhat experienced or willing to spend a lot of time learning and making mistakes, I'd say leave this to people who have some experience at this level and come back to it when building for the Captivate is well understood and the knowledge has been distributed enough so lots of people can help you when you have specific questions (no one likes answering general "how to" stuff on a device specific thread).
-Atin
Please!!!
any answer?????'
Use the search button before you make a thread!
i haven't found anything about the x8
lucasiumej said:
i haven't found anything about the x8
Click to expand...
Click to collapse
And chances are that you won't find a tutorial about how to cook a ROM for the X8.
In theory you have all the information you're possibly looking for around in the General Android Forums section as well as in the Chef section.
To build from scratch you need the Android SDK/NDK, the Android source code (you're most likely looking for the CM7 git sources), a kitchen, maybe Eclipse (the Integrated Development Environment) and a whole lot of coding experience to tackle the task. EDIT: You also need: A computer featuring a CPU supporting 64-Bit, a 64-Bit Linux distro (i.e. Ubuntu or Linux Mint in their x86_64 edition) and AT LEAST 8GB RAM to successfully compile Gingerbread/ICS.
The easier task might be to mod a existing ROM (of course ONLY with the express permission of the author of the ROM as well as of all other developers whose modules you are using), but even this requires a solid knowledge about what you're doing.
Oh, and you also need a phone where you can test out your ROM creation (just because it works in the SDK Emulator does not mean it works on the real device), and you need to be able pull your phone back out of "bad flash" in case your ROM or Kernel creation bricked your phone.
In short, the answer to your question is nothing more than reading up on lots of stuff and adapting things to the specifics of the X8 and porting a whole lot of stuff to make it work with the X8 (you know, the vanilla AOSP sources don't come with X8 drivers to support camera and so on).
As B.Jay said You need a looooooooooooooooooot of patience because every time something will go wrong. Also you must know how to analyze logs from terminal. It's really complicated stuff.
eagleeyetom said:
You need a looooooooooooooooooot of patience because every time something will go wrong.
Click to expand...
Click to collapse
LOL...
Yeah, welcome to the fabulous world of open source software where there are always surprises upon invoking "make"
you have to become einstien of android if you want to make a rom!! lol
freshy wanna cook a rom..??
yeah U have learn from modify rom first
and when u aready know what the stuff very well
that is u r ready...
Or you could use ROMMODGEN.com
Sent from my X8 using xda premium
Why do you need 8 Gb of ram?
I was able to compile CM7 with 1,5 GB of RAM on virtual machine. It was compiling for about 4 hours + time to fix errors 8GB of RAM is needed to compile ICS, because it's a beast There's one rule - more RAM, quicker result for magic "make" command
Since nobody seems to check the Q&A forum [Q] Kernel compiled in Ubuntu 12.04 fails
So i havent worked on a kernel in a while and decided id start workin on one again. Well I recently updated to 12.04 lts and no changes to my old source I just did a test compile and it wont boot. Same toolchain, source, ramdisk, etc.
Is there some sort of issue with compiling on 12.04?
Even redownloaded the source from my github and tried the toolchain recommended by samsung, stock tool chain, and 3 others and i still get nuthin. Just trying to compile a 2.2 kernel for the vibrant. No source i download works am i missing something?
does ANYONE have any ideas? I dont care who you are just something! I been at this for a freakin week and cant figure it out, ......i've changed nuthing but the OS and i really dont want to have to redo my entire setup because it is such a huge pain
Are you sure the kernel works? What is causing it to not boot?
I build ICS kernels just fine.
Check this and update tools for 12.04 http://source.android.com/source/initializing.html
trailblazerz11 said:
Are you sure the kernel works? What is causing it to not boot?
I build ICS kernels just fine.
Check this and update tools for 12.04 http://source.android.com/source/initializing.html
Click to expand...
Click to collapse
100% sure it works, its the same source as my old nightly# 3 kernel which i can flash and works fine. Its a 2.2 kernel so thatd be the main diff there, and I've already done the setup of the build environment. I dont get past the vibrant logo so i have no idea what the problem is >.< its driving me nuts
i tried the linaro TC, 2 diff code sourcery, google toolchain even, and no luck
I even started a fresh kernel from scratch and added just the EXT4/voodoo stuff and my ramdisk and still nuthin
so i remade my voodoo ramdisk and that still doesnt work.
I'm out of ideas, I've quadruple checked to make sure all my tools and erthing are installed......idk what the issue is
Not a developer but wouldn't downgrading to an older Ubuntu fix the problem? Btw I loved your gingerbread kernels and I hope you can get back to the top again Aim for 400mb ram with 720p and you will achieve something high
helikido said:
Not a developer but wouldn't downgrading to an older Ubuntu fix the problem? Btw I loved your gingerbread kernels and I hope you can get back to the top again Aim for 400mb ram with 720p and you will achieve something high
Click to expand...
Click to collapse
Id rather not but it seems that might be the case -_- I gotta look into how well older versions of ubuntu suppport the BullDozer cores before i do i guess.....
also I only made GB kernels for the NS4g i think ? o .o Vibrant I had been workin on it but I like being able to have MSAA in my games and what felt like greater stability, so i scrapt the new projects in favor of specific features i use :3
Ecotox I really wish you or another dev could make an updated CM7.2 kernel with Voodoo Color, OC/UV, and performance tweaks since Glitch is outdated and probably won't be updated for CM7.2. I know most devs have gone to ICS kernels, but CM 7.2 is still snappier and better for gaming then ICS.
hurtz777 said:
Ecotox I really wish you or another dev could make an updated CM7.2 kernel with Voodoo Color, OC/UV, and performance tweaks since Glitch is outdated and probably won't be updated for CM7.2. I know most devs have gone to ICS kernels, but CM 7.2 is still snappier and better for gaming then ICS.
Click to expand...
Click to collapse
I've been gone working on a game project, so I really haven't been doing much android stuff in months. If I get some time I might but can't make promises. Don't take this the wrong way but I'm looking for some help if anyone has any ideas not requests or compliments on previous work (though both are appreciated)
Sent from my Galaxy Nexus using Tapatalk 2
Can you use windows xp to compile kernels?
helikido said:
Can you use windows xp to compile kernels?
Click to expand...
Click to collapse
no
10 char
No but ty for the try....looks like imma have to revert back to 11.10...so let it be known for best results on compiling android use Ubuntu 11. If u have Ubuntu 12 and it works fine then leave it and good for u
Sent from my Nexus S 4G using Tapatalk 2
Hey there! Try downgrading gcc and g++ to version 4.4. If that doesn't work you can always just set up a dev VM in xen or vmware instead of blowing away the whole box. Hope that helps.
Hey guys, I wanna start a new "little" project and hope for some help from the one or the other.
I just realized, that noone until now really compiled a stock ROM for our device.
That means, we can't get a fully customized ROM. I mean Zeus ROM is close to it, but it's pretty restriced, to the typical "tweaks" like kernel, theming and so on.
So I thought of trying to compile the sourcecode. It's still compiling, but if I already look at the build.prop, it looks like it's not building for our device, although I followed LG's advices that are:
Code:
How to build
1. Android build
(1) Get the android base source code.
- Download the original android source code (Android 2.3.4 gingerbread) from http://android.googlesource.com
(2) Overwrite modules that you want to build.
- Untar opensource packages of P970_BDop_GingerBread_v20s.tar.gz into downloaded android source directory
- And, merge the source into the android source code(gingerbread)
(3) Run the build scripts.
- You have to add google original prebuilt source(toolchain) before running build scripts.
- Run the following scripts to build android
$ ./build/envsetup.sh
$ make -j4
into the android folder
- If the android is built sucessfully, you will find the outputs in this directory,
"out/target/product/generic".
So far it looks and is pretty simple. But like I said, with the commands mentioned, I think it doesnt build for our device.
Had to bypass some errors, since I am using a more recent toolchains as LG seems to have used, but since goolge is my best friend, he told me what to do
Now how can we get this sourcecode compiled?
Do I have to start like rmcc did? And add these files/add the content he added?
https://github.com/CyanogenMod/andr...mmit/04b8b02f13c62239dad2884530ad07b9fe3ebd60
Dont wanna mess up my building environment and start over again, that's why I am asking.
When typing lunch, it only shows:
1. Emulator
2. crespo (I think)
3. some HTC device
4. one more
at least I cant pick p970.
Would be nice, if we could get that done, since it would probably also work for our hopefully soon coming ICS!
Then we could get a VEEERY good ROM for our already lil bit old device
Hope we can make it and I am sure we can
All recommendations are welcome.
About that, you need to setup the proprietary binaries for LGE to be able to setup P970 for lunch. Beside that, the prebuilt must be of the similar version.
Sent from my LG-P970 using Tapatalk 2
GB + LGE ROM sources = nothing...
You have to add p970 as available project for lunch... and you have to get all the proprietary files (right, from LG GB) and al the vendor blobs (from CM7)... but IMHO it would have the same problems as CM7... becuase CM7 is AOSP with some extra stuff...
Huexxx said:
GB + LGE ROM sources = nothing...
You have to add p970 as available project for lunch... and you have to get all the proprietary files (right, from LG GB) and al the vendor blobs (from CM7)... but IMHO it would have the same problems as CM7... becuase CM7 is AOSP with some extra stuff...
Click to expand...
Click to collapse
How about downloading and setting up cm7 for our device, maybe pull latest files from our phone, replace them, add lg s stuff and maybe some minor changes. Do you think, it would build cm or stock rom? Thanks for the input
Sent from my LG-P970 using xda app-developers app
N00BY0815 said:
How about downloading and setting up cm7 for our device, maybe pull latest files from our phone, replace them, add lg s stuff and maybe some minor changes. Do you think, it would build cm or stock rom? Thanks for the input
Sent from my LG-P970 using xda app-developers app
Click to expand...
Click to collapse
It would be CM7...
LG's ROM source code is close to nothing... only mods to non-proprietary stuff... there is NOTHING more. so CM7 sources + LG's source = CM7 source... CM7 has used LG's stuff for its project...
The way IMHO is:
- Take latest Gingerbread AOSP sources.
- Take a existent target (as Crespo) and duplicate all the needed stuff with a different name... as P970.
- Once you can build P970 (a Crespo ROM will be generated), modify all the stuff with vendor blobs from CM7 and proprietary files from LG's GB.
- A way to understand what you are doing is to take AOSP complete code... CM7 complete code, and compare the way both sources compile the same target, (Crespo...) to obtain the differences... Once you understand how change from AOSP to CM7 for Crespo, you will try to make the opposite from CM7 to AOSP for P970...
Regards.
have good luck
:fingers-crossed:
Good luck for your project...:good:
Hello all! Hope all is well by you.
Based on what I've seen on this forum, the latest available kernel for the Touchpad is version 3.4.x - an older, unmaintained LTS branch, forked from Qualcomm's repos.
It seems that the mainline kernel source has code for the MSM8660 platform (what the Touchpad is based on) which leads me to wonder if it's possible to get a mainline kernel running on the device.
If my optimism serves me right, this could open the doors to running more non-Android systems on the device!
So far my attempts at booting my compilations have yielded nothing more than a hang at the HP splash logo. I've tried different GCC versions from Linaro (targeting arm-eabi) to no avail.
I'm unsure if I'd need to tweak any DTBs, though the 3.4 kernels don't seem to make use of those.
Of course a splash logo isn't too verbose... might anyone know if there's a serial console I can access over USB or some hidden port internally? Has anyone else made a similar attempt with any progress?
Cheers!
PieGuy128 said:
Hello all! Hope all is well by you.
Based on what I've seen on this forum, the latest available kernel for the Touchpad is version 3.4.x - an older, unmaintained LTS branch, forked from Qualcomm's repos.
It seems that the mainline kernel source has code for the MSM8660 platform (what the Touchpad is based on) which leads me to wonder if it's possible to get a mainline kernel running on the device.
If my optimism serves me right, this could open the doors to running more non-Android systems on the device!
So far my attempts at booting my compilations have yielded nothing more than a hang at the HP splash logo. I've tried different GCC versions from Linaro (targeting arm-eabi) to no avail.
I'm unsure if I'd need to tweak any DTBs, though the 3.4 kernels don't seem to make use of those.
Of course a splash logo isn't too verbose... might anyone know if there's a serial console I can access over USB or some hidden port internally? Has anyone else made a similar attempt with any progress?
Cheers!
Click to expand...
Click to collapse
I am not an expert, but have learned a lot by tweaking the kernel for the Hp Touchpad. To my basic understating none of the native driver codes were release as they are not "open source". How the developers got it working is by tweaking the hardware from what is "based on". If the drivers where open source, it could possible be more helpful on getting a lot more done. All I can do is provide some links from others that had tried:
The LuneOS is using the same kernel branch as Android, but there is no development for the kernel:
https://www.webos-ports.org/wiki/Main_Page
https://www.webos-ports.org/wiki/Main_Page
It will be great to have a kernel to run Linux natively.
Here are some work around that others had used:
https://github.com/mikestaszel/ArchLinuxARM-TouchPad
https://github.com/CalcProgrammer1/kernel_tenderloin_debian
https://forum.xda-developers.com/showthread.php?t=2761381
I did the following videos running Ubuntu (arm) as Chroot and is very fast !
https://www.youtube.com/channel/UCKoir6bzzPU-Uq9UjcRR3hw
Good luck learning!
@PieGuy128
Take a look at this post from @elginsk8r about a possible 5.0 Kernel:
There is a 5.0 kernel floating around that looks promising (uses mesa rather than proprietary blobs for display) albeit missing some key hardware support in it's current state. If anyone would like to take a look at the kernel sources and see what can be done it can be found here https://github.com/flto/linux/tree/msm8660. Building and booting instructions are here https://github.com/flto/linux/wiki
original post:
https://forum.xda-developers.com/showpost.php?p=83040029&postcount=273