Hello everyone,
I am not new to the android scene, and am quite familliar with linux development in java and c. I found myself in the pleasant position of having a second Atrix 4g that I had previously unlocked and played with a bit and decided it was time to have a look at some of the android issues that have managed to sufficiently annoy me.
To this end I have pulled down the aosp of ICS as well as CM9 for comparison. I see that there are issues with the tegra2 binaries for ICS and was going to have a go at building a 2.6.39 kernel for ICS.
Can any of you point me to some info on integrating a new kernel into the android build? As I understand it, the currently available binary drivers are build against 2.6.36 for GB.
Is it only the opengl drivers that are an issue? Are there opensource drivers for the bt/wifi/cell? The cameras/touch sensors/gyros etc?
I have done some research and looked over Googles build info, but it only covers the reference gear. I have not yet found a good guide on integrating 3rd party drivers for other hardware..
Thanks for all your assistance. Once I learn the build system I'm sure I will be able to make some useful contributions.
Also, I may be able to offer some hosting assistance for some projects.
* Kernel Newbies
* LWN article on merge: the KN post says the "ashmem" part did get added after the article was published.
* Kernel 3.3 source
From the assorted news stories online over the past few weeks, it would seem that this is core functionality: but assorted drivers and power-saving stuff would still need to be added back in.
Thats a great news
Sent from my GT-S5830 using xda premium
So what are the benefits of this? Linux distros support a wide range of x86 hardware where as Android x86 has limited driver support. Would we be able to get Android out to more x86 hardware with this? Also will this make the Ubuntu on Android project easier to port since the kernel could be shared between the two.
I think the key part here is to streamline use of the kernel for future projects. Current Android kernel use is way behind mainline; with stuff having to be backported and adjusted for CPU type.
Zalitoh
This Kernel is interesting
Hi.
Anything new with the 3.3 kernel ? I mean, maybe Cyanogen will start building on the linux kernel ?
Anyone knows ?
Hello people,
after some conversation with early ICS-on the transformer developer paulburton, I have a git repository of a mostly working linux 3.1 mainline kernel with some patches from paulburton to make it actually work.
Icluded are (as of now) :
improved atmel mXT1386 touchscreen driver
tegra_v4l2 camera driver
ov5640 soc camera driver
prox_lds6202 proximity sensor driver
fm34-500 voice processor driver
asusec keyboard driver (for dock)
al3000a ambient light driver
The purpose of this is not to port things back from some linux 3.X kernel to our 2.X kernel, but to have a fully working 3.X source tree some day, from which we could port to further linux versions in the future. This can also be helpful if we want to port android 5.X in the future.
The github is at https://github.com/skirata/linux/tree/android-tegra-tf101-3.1 .
(It's my github, if someone wants to become a collaborator, please let me know, I'll add you to the collab list.
WE NEED EVERY DEVELOPER WE CAN GET.
I will spend some time on this, but I think I can hardly finish this project on my own.
Totally support this, looks promising!
Thanks for the initiative.
Are you and guever working on this together? I can test and maybe help make aokp or megatron versions.
Sent from my Transformer TF101 using Tapatalk 2
Of course I'm willing to work, you know I've helped all I could.
My kernel has much of the code updated to 3.1, so may be we can use much of it.
This can be done in two ways, by modifying the code in paul whatever it takes, or modify mine. I have nothing clear which will be easier, because over time I have made several test on my code and unfortunately, when the kernel does not boot can not be debugged, so you have to turn back.
Until wednesday I will not be able to devote almost no time, so I think the first thing would be to check the operation of the kernel of paul (if not already done) with a current rom.
It is possible that the graphics drivers (most are binary system level) may not work with that kernel.
Well, it is what I think, that first we must see is what should be changed in the kernel to function properly (or whether to change the rom).
Teamwork is how it's meant to be done.!
I will setup a working kernel konfig in the next days to push this a little forward.
at Guevor :
I'm adding you in as a collaborator so we can work together on this.
Let's improve paulburton's drivers and add new ones based on latest nvidia images.
The advantage of upstream-porting rather than downstream-porting is we can port future kernel versions more easily with own written drivers.
Also, android 5.X porting will be a lot easier, as I think it won't support 2.6.X kernels at that time. And even if it would, we can have a massive performance boost if using 3.1 mainline kernel with improvements all over the world.
Glad to count you in, guevor.
I owe you so much already.
EDIT : Just in case, be sure to use the 3.1 branch of the linux repository, as the master branch is forked from torvalds (linux 3.4.X) and will get some love when we get the 3.1 kernel to work as good as we are satisfied.
Well, the main problem I see, thinking about future versions (5.x) is that we do not have the source code for video drivers, only a small part that exists in the kernel. This added to the fact that nvidia does not provide (at least I do not know) the binary drivers for android (as they made for linux), I think that may be, we do not see tegra2 drivers for 5.x. That does not mean we can not do something, but will be less optimal and more complicated.
Hopefully I'm wrong and nvidia make things easy , but I think no manufacturer will use tegra2 for new products, and do not think they will update current products to that version ....
guevor said:
Well, the main problem I see, thinking about future versions (5.x) is that we do not have the source code for video drivers, only a small part that exists in the kernel. This added to the fact that nvidia does not provide (at least I do not know) the binary drivers for android (as they made for linux), I think that may be, we do not see tegra2 drivers for 5.x. That does not mean we can not do something, but will be less optimal and more complicated.
Hopefully I'm wrong and nvidia make things easy , but I think no manufacturer will use tegra2 for new products, and do not think they will update current products to that version ....
Click to expand...
Click to collapse
Have you tried contacting Nvidia about this?
For the record, I am not a Linux user, even with what Im going to say, keep that in mind... My history is firmly routed in WinBlows land!
This has me all sorts of excited, I remember saying it back in paul's thread before it fell off the face of the earth (read, first few pages of the forum).
As stated at the top, while NOT a Linux user, I was trying to build CM9 for one of my tablets, to do so, I had setup a Linux box (tried a few distro's), and kept having issues, so a friend of mine walked me through updating to a 3.4.x kernel (3.4.0.-5 iirc), and things definitely FELT smoother vs the 3.0 (on the distro I was using before he berated me for it and moved me to a different one) and then 3.2 kernel in use (ill note hardware issues where also at play with the actual issues, but the smooth feeling after updating was definitely something I noticed).
I have no benchmarks or performance statistics to back that up, but as I said in paul's thread, and have now experienced in a "full" Linux environment, the future with Kernel v3.1 and up has me VERY excited as to what can be done with the OG Transformer! (vs mass backports to 2.x)
On that note, Subscribed thread, and time to get an RMA for my Tablet... the top basil part is starting to come off the unit
I haven't coded a lot with linux and android source, but I do have experience with coding and especially with reading through source code and finding syntax and other errors i.e. proofreading
So if you want me on the team I'm game!
Orkeren said:
I haven't coded a lot with linux and android source, but I do have experience with coding and especially with reading through source code and finding syntax and other errors i.e. proofreading
So if you want me on the team I'm game!
Click to expand...
Click to collapse
Every help is welcome !
Please tell me your github name and I will add you as a collaborator
If my help is welcome i am willing to test your builds on my TF101G B90 with dock. So let me know if you have to do something.
ajohn117 said:
If my help is welcome i am willing to test your builds on my TF101G B90 with dock. So let me know if you have to do something.
Click to expand...
Click to collapse
Will do for sure, but it could take some time until we can push out the first build for testing.
rayman33 said:
Hello people,
after some conversation with early ICS-on the transformer developer paulburton, I have a git repository of a mostly working linux 3.1 mainline own.
Click to expand...
Click to collapse
With my git every things works but usb hotplug,cam,hdmi-audio. ( usb works fine when insert add boot ) , also i will stop dev for it as i'm selling my tab :crying: but would be nice if this got finished.
also major thanks to paul
Do you started the project?
I tried some things yesterday, but it did not boot. I will have a look into spark rom and try some other things, I think I have some ideas.
Btw, kernel compiles fine, zImage is there, perhaps some early device drivers have to be updated. I will look into the ramdisk I created and fix some things ...
Just to let you people know. Progress is being made.
First progress
I managed to make it boot on revolver 4.1.1 rom. I modified the video drivers to be compatible with the actual binary drivers.
The touch screen is not working, but I really have not looked at it, maybe even compile options I chose are not the most adequate, but just wanted to get it to boot with video graphics working.
We better get each other updated via pm in the future ..
What touchscreen driver did you define in the kernel config ?
The new mxt1386 or the old one from the 2.6.39.4 kernel?
Maybe we need to rewrite the mxt1386 drivers.
rayman33 said:
We better get each other updated via pm in the future ..
What touchscreen driver did you define in the kernel config ?
The new mxt1386 or the old one from the 2.6.39.4 kernel?
Maybe we need to rewrite the mxt1386 drivers.
Click to expand...
Click to collapse
Well, I tested whether simply boot and graphics drivers failed as expected, and I've tried to change it and make it working. I think that is the basics (make it boot) to further adjust problems.
About the drivers, yes, I used mxt1386 but not detected coordinates, just click. I used a USB mouse to verify that the graphics drivers work.
I updated the repository with my changes.
Did you get a log cat already ?
It may reveal if the mxt1386 driver fails to load.
rayman33 said:
Every help is welcome !
Please tell me your github name and I will add you as a collaborator
Click to expand...
Click to collapse
easy as pie!
Code:
orkeren
I have been reading some of the items about people modifying ROMS, porting ROMS, etc. and I am not certain if I have all of the terminology correct. I am wondering if there is some type of architecture definition or diagram that would indicate the different parts of a ROM.
I found one web post that broke items down to kernel, libraries, bootloader, recovery, radio, framework, core, android runtime. What I don't know is what kind of correlation there is between a framework and runtime to a kernel. Is this a situation like Linux where you have a kernel with all of its drivers and you would run the Android GUI on top of that and any version of the Android GUI is going to work with pretty much any kernel, or is there some type of match-up between a kernel and specific versions of Android?
I have an Elocity A7+ which uses a Tegra II 1ghz dual core CPU. It was only built with Android 2.2. It seems like this tablet should be able to run ICS fairly well since I have seen a number of single core tablets running it. The manufacturer made the kernel source available for this tablet, but what I don't understand is if it is possible to build the ICS framework and runtime with this kernel.
Without detailed information it would seem to me that the kernel is taking care of interfacing directly with items like the touch screen, the camera, the audio system, the buttons, the wi-fi, etc. Do requirements for kernel interfaces change from android version to android version or can an ICS framework communicate with the kernel from a 2.2 device? Is there any kind of documentation that indicates what kernel calls have to be available to the different Android versions?
I apologize if I am not asking the right questions.
LinuxonAndroid is an on going project to bring a range of Linux distrobutions to Android devices, as the project has developed the team has grown and clear parts of the project have developed.
This thread has been created to handle development of the app itself, other parts of the project (Linux images, bootscripts etc) will have there own threads to talk about these sections and avoid confusions as the old thread has grown to 200+ pages.
XDA:DevDB Information
Complete Linux Installer, App for all devices (see above for details)
Contributors
zacthespack
Version Information
Status: Stable
Created 2014-06-07
Last Updated 2014-06-07
Reserved
Reserved
Could be interesting
Gesendet von meinem SGP321 mit Tapatalk
Yay, reorganized forums
droid bionic
can this work with a linux distro and the bionic hdmi port... Now cm11 has a working hdmi port it can be like webtop.
Casey Walt said:
can this work with a linux distro and the bionic hdmi port... Now cm11 has a working hdmi port it can be like webtop.
Click to expand...
Click to collapse
I'm not sure about the bionic hdmi port, as I haven't played with one of those yet, but this will allow you to load a linux distro with very nearly 100% functionality, the only real limits to the linux functionality are from not being able to compiler new drivers into the kernel that's stored by android, and the potential lack of some packages/functions in the ARM versions of some linux distributions.
One thing to be aware of, however, since you mentioned CM11, is that there is a glitch caused in the current version of the Complete Linux Installer app by CM11 ROMs which causes you to need to either manually input one command line to start the bootloader script, or set up a widget on your device to do that for you (sorry, it's a CyanogenMod quirk. We're working on it, but so far it's hard to track down since only CM seems to cause it).
robherc said:
I'm not sure about the bionic hdmi port, as I haven't played with one of those yet, but this will allow you to load a linux distro with very nearly 100% functionality, the only real limits to the linux functionality are from not being able to compiler new drivers into the kernel that's stored by android, and the potential lack of some packages/functions in the ARM versions of some linux distributions.
One thing to be aware of, however, since you mentioned CM11, is that there is a glitch caused in the current version of the Complete Linux Installer app by CM11 ROMs which causes you to need to either manually input one command line to start the bootloader script, or set up a widget on your device to do that for you (sorry, it's a CyanogenMod quirk. We're working on it, but so far it's hard to track down since only CM seems to cause it).
Click to expand...
Click to collapse
Im at school so I can't test it but I'll try and report back...hope it works