Has anyone noticed that google started working with the 3.10 mainline kernel?
Do you guys believe that we may get lucky and get android 4.4 with all the performance fixes of 3.10 or even 3.11?
Kernel(Google Source)
I hope so *crossing fingers*
Sorry but no. Couple reasons I know this: #1: as of two months ago, the nexus 5 was still using 3.4, so I doubt they'd change this late in development meaning the N4 wouldn't either. Also, Qualcomm got rid of support for 8960 and 8064 devices and has not updated their arch specific drivers. I highly doubt that Google would update a Qualcomm chipset that is deprecated. That would be a lot of work for them and the SOC manufacturer creates the majority of the kernel. I am working on 3.10 myself, but don't expect it from Google and Qualcomm for awhile. Qualcomm is only targeting APQ8084, MSM8974, MSM8610, and MSM8226 in 3.10. They explicitly removed support for other chipsets such as our 8064.
Related
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
What about use a base of stock roms and make the things work??? I know Cm its for armv, but all its adaptable,
Enviado desde mi XT890 usando Tapatalk 2
as for MIUI (there already is a MIUI port on the razr i, not complet I think, but it exist). MIUI is mostly a framework mod.. this is platerform independant AFAIK.
I don't think CM & Cie are so dependant of the SoC architecture. There's lot of différences between some ARM SoC .. maybe more than you can imagine. If CM can be adapt to so many device with so many ARM SoC witch a so différent, why not for a x86 Soc ?
I think you're a little bit pessimist here...
I didn't say it's impossible but it's more complex then a normal port for an ARM device. The issue is it requires more knowledge on the issue and will eat far more time. A CM port to x86 is a very unlikely goal for a single dev , and I'm saying this because a few months ago I discussed this issue with the people behind Android x86.
So a talented DEV will be able to achieve this but it will take time and a bigger struggle , that's why to start of developing for this device it would be more reasonable to look at Android code already ported to x86.
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
Sure there is some ARM dependent code in the repos but most of android doesn't really depend on the arch (like apps using the sdk dont need to be recompiled for working on the I, see play store apps). I have worked with o1 and android-x86 and there isn't really that much change from CM and android-x86, just some extra optimizations for x86 which can be added in later.
There are plenty of device on where even custom rom seems to be impossible. mostly because of a locked bootloader.
Look at the Motorola Defy. At the beginning, the development of a custom rom like CM was pretty impossible.... but they did it. They did it so far that the Defy became one of must used device with Cyanogenmod. And you now the most astonishing? It's thanks to only 2 devs.
I think bypassing a locked bootloader like the Moto one is far more tricky than adapting a CM ROM to a x86 SoC (while the device is natively unlocked).
AFAIK, android-x86 project is not so close to the Android we have on our phone.
When you develop a custom rom you can either take the AOSP source and try to put it on your phone : the tricky way. Mainly when you don't have access to the source of the drivers (ARM or x86 .. same fight)
Or you can take the official rom and mod it to reach the AOSP/CM/MUI/etc level. And I think on most device it's the way to go (unless the manufacturer release all the source code of the device.... something that never appends).
lgstoian said:
THIS IS NOT A ARM DEVICE ! This is x86. Porting CM to this device would be an incredibly complex task as alot of CM code is ARM dependent. You are going about this the wrong way , these are two completely unrelated CPU architectures , you need to look at the Android X86 projects that are out there which I will link too at the end of the post.
ARM is vastly different from x86 and you can't run code designed for one on the other.
NO ROM for ARM will work on this , meaning no CM , no AOKP , no MiUi , and not even AOSP etc.
You need to work with the Android x86 sources provided by either Intel or the community x86 port.
Links :
http://www.android-x86.org
https://01.org/projects/android-intel-architecture
http://androvm.org/blog/
All these projects are FORKS of android highly modified to work on x86 !
Click to expand...
Click to collapse
You really know what you are talking about? As others already mentioned above CM is in most a framework - porting android to x86 seems to be not such a big gap as motorola did it already and for sure you can run android on your pc - do you own an arm pc (in this case i think an rasperry pi...). The toolchain remains the same so why you make such a story out of it? Are you a razr i owner or do you just want to frighten all razr i devs and owners awaiting a CM port??
ARM architecture is different in some points but most of the work will do the compiler and to be honest i think there will be some more x86 phones in the future, intel never developed it for one or two phones....
So what is your intention with this topic??
kind regards.
lord0815 said:
So what is your intention with this topic??
Click to expand...
Click to collapse
That's what I'm wondering. Any dev that's taking on this task obviously knows it's going to take a bit of extra work. It would have been different had the OP offered some help and advice, but he just posted the obvious while making it seem like a bigger deal than it is (at least I'm guessing it's not as big a deal as he makes it seem, considering the other posts in this thread). Nothing but fear mongering and pessimism at this point. Sure, we will have to wait a bit for the devs to figure things out, but I know enough of them picked up this phone that something will eventually come. Plus, there seems to be a bit of dev interest in the Intel Yolo as well.
I don't know much about porting or developing and getting cm to run with all the necesary source and drivers is probably not easy but I do know that one of the basic options when running the build/make command for AOSP and CM is an x86 build for emulation. So basic x86 infrastructure exists does that ensure compatibility with this phone maybe not but it might help and certainly it would still require SOC and device optimization drivers but its probably the better place to start then tackling trying to port ARM based code and drivers.
However in the meantime my thinking is maybe a CM style rom could be achieved by first stripping down the rom making it "blurless" and then porting CM features especially since the latest Moto ROM's are comparatively closer to stock then sense or touchwiz. Of course I don't have the phone yet its in England waiting to be brought to me.
Hi,
I currently use a custom TW based firmware for my 910F based upon POF2 firmware. I'm a software developer and developer an app that uses OpenGL ES 3.1. Now I have a problem which seems to be connected to the old version of the Qualcomm Adreno 420 drivers that came with the ROM. Every shader I want to compile fails with the error: "Built-In invariance mismatch". Those shaders worked on the same phone with all 4.4.x based ROMs before. So I now wondered if I can use Adreno 420 drivers for the Nexus 6 (Uses Adreno 420 as well) downloaded from the Qualcomm developer page (drivers from August 2015) and just flash the file to my phone? I already looked inside my system folder and the files on my phone are the same just much smaller and older versions. I'm a little scared if a break everything if i try this. So maybe someone with a little experience with Android drivers for GPUs can tell me if this will be possible?
Best Regards,
CommanderXXL
I guess most people don't care about which driver is included in ROMS as new ROMS are always coming out or being improved upon and with all of the details and specs being listed, driver versions are never mentioned. Is the v84 driver all that we can hope for, nothing newer? I've flashed countless ROMS an never saw anything newer.
Driver versions do matter, I wish they would be listed somewhere in the ROM description.
Somebody has to develop these drivers. You can't just go to a website a download them like nvidia drivers.
And as far as I know, Qualcomm only release the source code for the chips, leaving the development up to whoever is interested.
Is there not an updated driver newer than v84 that already works with the S4? The S4 has gotten official Lolipop OS upgrades, isn't there better drivers already made to work?
Surely Marshmellow OSs have better drivers. Are those drivers not able to be used on the S4? I understand someone has to do the work, but every other aspect of custom roms are being made to function, are GPU drivers just being overlooked as not being important enough to spend time on?
I don't know how this works. But if they could I think they would.
Obviously, Qualcomm has to update the drivers, as it's their chip. So maybe they dropped support for the Snapdragon 600 chips. I don't know.
Tommy807 said:
Is there not an updated driver newer than v84 that already works with the S4? The S4 has gotten official Lolipop OS upgrades, isn't there better drivers already made to work?
Surely Marshmellow OSs have better drivers. Are those drivers not able to be used on the S4? I understand someone has to do the work, but every other aspect of custom roms are being made to function, are GPU drivers just being overlooked as not being important enough to spend time on?
Click to expand...
Click to collapse
drivers from another GPU wouldn't be any use to us.
according to Qualcomm (not sure how reliable the resource is)
http://m.pocketnow.com/2016/08/26/qualcomm-snapdragon-800-801-no-android-nougat-support
Sent from my A0001 using Tapatalk
Yes, this is somewhat old news now. Qualcomm dropped drivers for the Adreno 3xx series used on the 800/801, so we have no Vulkan support and thus cannot pass CTS. Therefore, we will have no official Nougat builds. I'm sure people are working on making the drivers from Marshmallow work (maybe not with Vulkan, but still at least be able to boot and have graphics work, etc.).
Oneplus One is in the official list of devices that will receive cm14, so i guess that driver support won't be a problem
effry said:
Oneplus One is in the official list of devices that will receive cm14, so i guess that driver support won't be a problem
Click to expand...
Click to collapse
"Official" list? Source? AFAIK CM hasn't posted anything since Nougat source dropped
is the chipset and the kernel versions are related to each other ?
I have observed that phones using Snapdragon 617 chipset are you using the kernel version of 3.10 checked with Moto G4 Plus and on other phones like nubia , BlackBerry dtek, etc
while phones using Snapdragon 430 chipset are using kernel version 3.18.. for ex redmi 4, etc
so my question is kernel versions like 4.4 and other newer versions can't be developed by manufacturer or what? for Snapdragon 617 chipset
ajaikumarnadar said:
is the chipset and the kernel versions are related to each other ?
I have observed that phones using Snapdragon 617 chipset are you using the kernel version of 3.10 checked with Moto G4 Plus and on other phones like nubia , BlackBerry dtek, etc
while phones using Snapdragon 430 chipset are using kernel version 3.18.. for ex redmi 4, etc
so my question is kernel versions like 4.4 and other newer versions can't be developed by manufacturer or what? for Snapdragon 617 chipset
Click to expand...
Click to collapse
They are not at all related to each other. Even in high ended smartphone you will notice 3.18 or above. As it is the minimum requirement for oreo build to function.
They are updated by oems and are maintain by company and are updated via ota.
As lenovo owned Motorola has officially announced oreo for moto g4 plus. As a pain in **s they have to update kernel first(which takes hell amount of time) n then have to push oreo update.
I think i was clear here.[emoji6]
DgnrtnX said:
They are not at all related to each other. Even in high ended smartphone you will notice 3.18 or above. As it is the minimum requirement for oreo build to function.
They are updated by oems and are maintain by company and are updated via ota.
As lenovo owned Motorola has officially announced oreo for moto g4 plus. As a pain in **s they have to update kernel first(which takes hell amount of time) n then have to push oreo update.
I think i was clear here.[emoji6]
Click to expand...
Click to collapse
thanks for the wonderful explanation.. i hope they bump kernel to 4.4 or newer..
ajaikumarnadar said:
thanks for the wonderful explanation.. i hope they bump kernel to 4.4 or newer..
Click to expand...
Click to collapse
If you're referring to Moto, not a chance. It's too much work to rework the kernel to a such a new version. I suspect that is the same reason there's a much higher delay around with phones that release with Oreo (very few at this time, even the OP5T comes with Nougat).