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
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
Hi,
I know that Android Gingerbread is quite old so probably most people would not bother to port it any more, but I need it for a university project where the hardware resources are very limited.
After a lot of work, I managed to build Android Gingerbread for the Digilent Zedboard, but it is not reacting to any touches on my USB touchscreen or to movements/clicks with a USB mouse.
getevent provides the expected events and I tracked them in InputReader.cpp and they seem to be dispached fine, but the UI does not react to the input. I can see that the events are enqueued, but cannot find where Android actually picks up those events and works through that queue. Does anybody have an idea?
I followed a tutorial on elinux.org (I am not allowed to post links yet. It's elinux.org [slash] Zedboard_Android)
with small modifications (enabled USB touchscreens in the kernel config, switched to a different android repo since the one in the article is offline)
Any help is much appreciated.
Thank you!
Android Gingerbread is no longer supported, and cannot use Google Play Services.
Why are you trying to run Gingerbread?
Please read THIS BEFORE responding.
Thanks for the answer!
x13 said:
Android Gingerbread is no longer supported, and cannot use Google Play Services.
Click to expand...
Click to collapse
I do not need Google Play Services.
x13 said:
Why are you trying to run Gingerbread?
Click to expand...
Click to collapse
We are trying to show dynamic partial reconfiguration with Android. For that purpose, we selected the Xilinx Zynq processing system. It consists of a dual-core ARM processor and an FPGA. The point is to reconfigure parts of the FPGA from Android during runtime.
Unfortunately, we were unable to find hardware designs for the upper-level Zynq chips and do not have enough resources to build one ourselves. Therefore we are stuck with the smaller chips and went for a ZedBoard.
At a point in history (I am not sure when) there was even official android support for the ZedBoard by iveia. They used android gingerbread, thats the first reason why we chose to use it.
The second reason is that the ZedBoard has very little resources (slow processor, little RAM, no GPU), which disallow more current Android versions to run. Some people got more recent version booting (google noritsuna android zedboard), but they reported it being slow since there is no gpu and low ram (they used linux swap since the built in ram is not enough for android - but linux swap from an SD card is terribly slow). Also, we were unable to replicate their build. All build processes go through but it does not boot. No debug output is available - not even kernel messages over UART. I suspect the u-boot setup is wrong but am no expert and cannot fix it.
Gingerbread is working fine (except for the touch issue), so we decided to stick with it.
Good afternoon, I'll try to explain my doubts as simple as possible, this would solve the problem of many users with Atom processor Z8700 that can not have sound on their android device.
Phoenix OS works perfectly BUT NO SOUND
Prime OS works perfectly BUT NO SOUND
Android X86 works perfectly BUT NO SOUND
OpenTHOS works perfectly BUT NO SOUND
ok, but i have a nameless .iso build of Android x86 in which the SOUND WORKS PERFECTLY but many other things do not:silly:
the question is, how can I extract the sound drivers from this .iso and put it on any one of the androids where the sound does not work and so have a perfect android on my Surface 3 ?
https://www.android-x86.org/releases/releasenote-9-0-r2.html
Key Features
The 9.0-r2 release is based on the latest Android 9.0.0 Pie release (android-9.0.0_r54). The features include:
Update to latest Android 9.0.0 Pie release (android-9.0.0_r54).
Update to LTS kernel 4.19.110.
Fix iso cannot boot in UEFI mode.
Fix audio issue of Microsoft Surface 3.
Microphone not working and Unstable WiFi in Surface 3 -Android x86
First of all I would like to thank you for having posted this version of Android x86. In installed on my Surface 3 128gb and worked!!
I have a couple of issues and hope someone can provide assistance.
Micropone not working: the mic doesn't work with any app.
Wi-Fi disconnects: WiFi periodically disconnects and in order to make it connect again I have to enable the hotspot. The screen then turns rapidly off and on and the problem is (temporarily) solved.
Is there anything I can do to solve this issue?
Version: Android x86 9
File sys: ext 4
Surface 3 128gb 4gb RAM
Thanks in advance.
fegato said:
Key Features
The 9.0-r2 release is based on the latest Android 9.0.0 Pie release (android-9.0.0_r54). The features include:
Update to latest Android 9.0.0 Pie release (android-9.0.0_r54).
Update to LTS kernel 4.19.110.
Fix iso cannot boot in UEFI mode.
Fix audio issue of Microsoft Surface 3.
Click to expand...
Click to collapse
Please I have a surface 3 with 64gb 2gb of Ram without type cover and i want to ask you if the installation of android x86 requires a keyboard ? also i want to know if the installation of android X86 will erase my win10 and if the roll back is possible ? thank you inadvance for your help
So I know this is a older post, but I too have a Surface 3 (just to confirm, not a surface PRO 3), I understand these are ARM based processors. Is it possible to install android on this device?
Thanks in advance
deanfourie said:
So I know this is a older post, but I too have a Surface 3 (just to confirm, not a surface PRO 3), I understand these are ARM based processors. Is it possible to install android on this device?
Thanks in advance
Click to expand...
Click to collapse
Just to be clear, the "Surface 3" referenced in this thread is the Atom-based Surface released in 2015 and is the only Surface device to charge via a Micro-USB port.
It's Intel Atom x7-Z8700 is a full 64-bit compatible x86 CPU.
Surface 3 - Wikipedia
en.wikipedia.org
The original "Surface" (2012, later marketed as "Surface RT") and "Surface 2" (2013) are the older Surface devices that use the Nvidia Tegra ARM platform.
The Surface Pro X (SQ1: 2019; SQ2: 2020) is the current-gen Surface device that uses Microsoft-developed ARM SOCs.
Oh I think I have the Nvidia Tegra ARM version