I been patiently waiting for kernel versions that brought us to a more modern Linux core ie 3.4+, but for what ever reason I keep seeing all the kernel devs using 3.1 still.
Does anyone know why the devs are sticking to 3.1 sources? Is it because they can't get their hands on the source files for newer kernels or something else? 3.8 is supposed to have native support for our android devices so it makes me wonder when will we get access to 3.8. I know it's rumored to be the version for Android 5.0 but isn't the sources already available to use now?
Any idea what the hold up is? Thanks
Sent from my Nexus 7
Related
The father of Linux (Linus Torvalds) announced today an update to the linux kernel to a new version 3.0 and Android OS is based on the linux kernel.
Once this new kernel will be released i feel a lot of hot fresh and interesting development going on, dont you think ??
p.s.: for those that dont know what a kernel is .. the linux kernel is the core which is used on ALL LINUX based distributions.
"So what are the big changes?
NOTHING. Absolutely nothing. Sure, we have the usual two thirds driver
changes, and a lot of random fixes, but the point is that 3.0 is
*just* about renumbering, we are very much *not* doing a KDE-4 or a
Gnome-3 here. No breakage, no special scary new features, nothing at
all like that. We've been doing time-based releases for many years
now, this is in no way about features. If you want an excuse for the
renumbering, you really should look at the time-based one ("20 years")
instead."
Linus
Click to expand...
Click to collapse
So, nothing special as you see
oops! current stable kernel is 2.6.39.2
I would really like to get the OS updated on this device, I'm sure I'm not alone.
I've been following many of the guides on this forum, or youtube videos, but with no luck.
Is there anyone who can help me to figure this out better?
Building AOSP or Porting Cyanogen mod would be ideal, is this possible?
I have had the original a7 since it was released and the major hangup has always been, the kernel. The kernel source for 2.2 froyo has been released, but, no one has made or ported a kernel past that. Dexter the great did a lot with only that kernel, CM7 and Honeycomb, but limited because the old kernel. We need a 3.0 kernel for CM9/10 to really move. There are similar tegra devices that have Honeycomb and beyond, but swapping kernels has been reported to only partially work. I hope that it will happen one day, this baby is powerful.
So beyond my ranting we need, device tree, drivers, and a kernel.
I have been trying myself to push all sorts of Linux for Tegra (ubuntu, gentoo, and geexbox) as well as trying to figure out how dexter had started running ICS on his before he dropped the project.
What is known: this is an abnormal Harmony tegra 2.
What you need to know for APX: A7+ uses hsmmc interface, so all nvflash designed for nand or emmc will inherently fail (or at least has been the case thus far)
I dont know how exactly this is, but due to its odd nature most prepackaged or script made bootloaders will fail. I'd love to see ICS or JB on this device for sure, but making an APX backup would need a new bootloader, or at least a new boot.img for sure.
I'm a tinkerer, with very little programming skill. I can google as good as anybody though lol.
Somebody needs to design an uber cross-compiler that can just transform the kernel to 3+ so we can stop wishing for new firmware and just have it lol
So we have ICS which runs on 3.0.8 and previously ran on 2.6.35, also I've seen a lot of devices running ICS on 2.6.32 kernel. So my questions are:
How to know what changes must be done in kernel to make it compatible with higher versions of android? (for example 4.2.2 with .32 kernel)
How to know whether kernel modules (drivers) are compatible with higher versions of android or not?
Why don't we still have a JB port if it's all is possible?.. Just joking.
Thanks in advance!
P.S.: Excuse me if I name anything wrong or if I'm saying anything wrong -- I'm not a developer, I'm trying to learn.
would like to know that too, dunno why there is just one developer working on wifi drivers for jelly bean huawei x5...
rukadesigns said:
would like to know that too, dunno why there is just one developer working on wifi drivers for jelly bean huawei x5...
Click to expand...
Click to collapse
Because there is an exhaustion of developers for the u8800? I'm going to release something soon as well, been playing with AOSP Gingerbread tree for a few weeks now.
There aren't really _many_ changes required to upgrade the kernel, you most likely just need to apply the upstream kernel patches for it. It will surely cause problems, but most of them shouldn't be too hard to fix if you have some programming knowledge. I might look at this later myself.
I think we dont have a proper port of JB just because there is a lack of real developers. People seem to be trying to port roms from Honor/Desire, but they will never be as functional as roms built from the real device tree. I think Blefish is the only one working on a real rom.
Hi, I have seen news about Oppo releasing the Kernel Source and supporting the AOSP community (the same Sony and HTC right now).
My question is, when Android 5.0 and a CM11 is released, does this source or information already released today about the device works for future releases of AOSP based ROMs without the support of the company?
Trying to be clear, Oppo (Sony and HTC too...) release some source today, but the next year they don't support this model, can the AOSP ROMs implement a new stable version using that last year released source from a prior Android version?
Thanks
pedroren said:
Hi, I have seen news about Oppo releasing the Kernel Source and supporting the AOSP community (the same Sony and HTC right now).
My question is, when Android 5.0 and a CM11 is released, does this source or information already released today about the device works for future releases of AOSP based ROMs without the support of the company?
Trying to be clear, Oppo (Sony and HTC too...) release some source today, but the next year they don't support this model, can the AOSP ROMs implement a new stable version using that last year released source from a prior Android version?
Thanks
Click to expand...
Click to collapse
No one knows. We would hope so, but no one would really know. Maybe.
Sent from my Oppo Find 5
kernel-wise - the cyanogenmod team has been able to merge it with the Qualcom sources, so if Qualcom keeps it up to date (most likely yes), then that's no problem (also, nexus 4 shares a lot of the same underlying hardware: CPU/SoC, GPU... that device will get updates, which could be ported over)
http://forum.xda-developers.com/showpost.php?p=40671515&postcount=5
proprietary library-wise - maybe? sometimes, they're compatible cross-android version, sometimes not, and you have to do workarounds to make it work on the new version.... could also steal libraries from other devices (see nexus 4 again)
Sony released remote play for all Android phones this week with compatibility from Android 5.0 onward but it's recommend to have Android 10 to use a DS4 due to better compatibility drivers. Is there any chance you could rip the drivers from the OnePlus 7 or 7 pro on OOS 10 put them in a zip and flash them through TWRP or magisk?
I think you just need to wait since the official update is coming this month of October.
Graffiti Exploit said:
I think you just need to wait since the official update is coming this month of October.
Click to expand...
Click to collapse
Not to argue specifics but the beta comes out this month and the full release is next month. But I understand your point. I still want to know if it's possible to do it though.
Drivers are in the kernel in Linux based systems. You can't just 'rip' the drivers. You have to find a kernel Dev willing to work this with a soon deprecated Android version... with yet unpublished oos kernel sources, only AOSP ones. Not easy
That's why it will be more easy to wait beta / official OOS. Or perhaps be ready to try one of the Android 10 ROMs floating around there
Striatum_bdr said:
Drivers are in the kernel in Linux based systems. You can't just 'rip' the drivers. You have to find a kernel Dev willing to work this with a soon deprecated Android version... with yet unpublished oos kernel sources, only AOSP ones. Not easy
That's why it will be more easy to wait beta / official OOS. Or perhaps be ready to try one of the Android 10 ROMs floating around there
Click to expand...
Click to collapse
Understandable thanks for the answer, I thought it was more like the adreno drivers that you could update through TWRP or magisk I forget which one I just remember doing it on my V20.