Develop Bugs

Confirmed: 3.1 kernel with 4.0.4 UPDATE: LINK TO NVIDIA

Just Got Confirmation from a very recognized developer in china that is developing for the One X (xda-zgf). He confirmed that though the leak build of 2.0 doesnt contain the newer kernel, he said that with the final OTA, we will see a 3.1 kernel for our One X. He seemed quite sure, maybe he'd done a lot of digging in the codes or something. But lets all hope for the best, as 3.1 would really mean that we are on the same front line hardware and software spec wise as any competitor in the market.
UPDATE LINK: http://developer.nvidia.com/linux-tegra
//""Linux For Tegra
OVERVIEW
NVIDIA is pleased to announce that Linux for Tegra release 15 is now available. The NVIDIA Tegra Linux Driver Package supports development of platforms running:
NVIDIA Tegra 3 series computer-on-a-chip (Cardhu)
NVIDIA Tegra 2 series computer-on-a-chip (Harmony* and Ventana)
3.1.10 Linux kernel
* Additionally, developers should note that support for Harmony devices is deprecated, provided for reference only. Harmony will transition to community-supported Linux kernels, and Ventana is now the Tegra 2 reference platform.
New Features
This release fixes some issues that were found during continued testing and adds/enhances the following features:
Preliminary U Boot support. For more information, see U-Boot support is preliminary in this release in the Implementation Notes section of the Release Notes.
Adds Ventana kernel support for u-boot
Adds source_sync.sh script to sync kernel and u-boot source code
Supported Features
Kernel version 3.1.10
Media APIs:
OpenGL ES 2.0
OpenGL ES 1.1
Open GL ES path extensions
EGL 1.4 with EGLImage
X Resize, Rotate and Reflect Extension (RandR) 1.3
X11 ABI 5, 6, 7, 8, 10, 11, 12 support
HDMI console support and expanded list of modes (refer to documentation for default resolution and tested modes)""//

Really? Good to hear finally..

This is is promising. Gosh I hope it's true, the one x would then be a true developers haven.
Sent from my HTC One X using Tapatalk 2

theROMinator said:
This is is promising. Gosh I hope it's true, the one x would then be a true developers haven.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
With its lack of soff and HTC locking down their bootloaders? Bit of an overstatement but I get you
Sent from my HTC One X using xda premium

with football and mike1986 on the case....im certain soff is just a matter of patience now....we just need to support and aid them as much as we can.
Sent from my HTC One X using Tapatalk 2

New kernel not in the test build but released ota? Seems very unlikely.

I was also told by someone close to HTC that we should have a 3.x kernel.
He however isn't sure if it will be for the next OTA but it should appear someday

thread title says confirmed and OP puts a question mark at the end !!!!!!!!!!!!!!!

kryptoner said:
thread title says confirmed and OP puts a question mark at the end !!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Quite confusing indeed

Hopefully by 1st week of July !!

tooney said:
New kernel not in the test build but released ota? Seems very unlikely.
Click to expand...
Click to collapse
Also havn't seend a new test version yet...
But only time will tel.

I don't think that 2.xx line will have 3.x kernel. They started 2.05 rom with 2.6.3.9 kernel, so it doesn't make sense.

I dont think its 'confirmed' just because one guy said so,
I think its best to assume that 2.05 will not arrive with the kernel as the test build doesn't have it.
Only 'hope' the kernel is included.
When does the regular folk get the official RUU? - we usually get it at least a week prior to official OTA.
Sent from my Xoom using Tapatalk 2

What benefits will the kernel 3 bring over our current ones ?

rik-sik said:
What benefits will the kernel 3 bring over our current ones ?
Click to expand...
Click to collapse
a bigger number

stesa said:
a bigger number
Click to expand...
Click to collapse
Lol, would actually have been quite funny if that was the case. The kernel 3.x is supposed to bring performance updates and will also mean the nvidia will be updated which in theory should bring massive gpu performance increase.
Sent from my HTC One X using xda premium

tooney said:
New kernel not in the test build but released ota? Seems very unlikely.
Click to expand...
Click to collapse
Football said:
I don't think that 2.xx line will have 3.x kernel. They started 2.05 rom with 2.6.3.9 kernel, so it doesn't make sense.
Click to expand...
Click to collapse
Nvidia released 3.1.10 linux kernel code recently.

jerrylzy said:
Nvidia released 3.1.10 linux kernel code recently.
Click to expand...
Click to collapse
where have you seen this news?

timlambo said:
Lol, would actually have been quite funny if that was the case. The kernel 3.x is supposed to bring performance updates and will also mean the nvidia will be updated which in theory should bring massive gpu performance increase.
Click to expand...
Click to collapse
Anything specific you can add to this?
I know that some Android code has been taken upstream into the kernel, and that much of the arm code has been reworked to have less duplication across architectures.
But what specifically has been changed to provide much better performance for our phones?

Nvidia drivers Tegra R15 for 3.1.10 - developer.nvidia.com/linux-tegra
Sent from my HTC One X using xda premium

[Q] Why havent we seen any source built ROMs thus far?

Hi All,
Seeing as the source code for the M8 sense and GPe's various open source components has been released for over a month now, why havent we seen any source built ROMs yet? Things like a Paranoid port or a CM11 port would be welcome on our devices (i know not all of you want it but some of you certainly do). I ask because i am considering building something from source for the M8 and modifying various aspects in order to solve what i perceive as the problems with Android on our device.
Kind of half expected a Tizen or Ubuntu Touch port in the pipes at this point also. But its probably early days for that.

Cm is being worked on for the m8. Most of those roms are based on or use components of cm so I imagine once cm puts a working rom up many more will follow.
Sent from my HTC One_M8 using XDA Free mobile app

6.0 port

NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious

cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.

cell2011 said:
NExus factory images live today. We are suppse to get it but end of this year or start of next. Is anyone out there planning on porting this maybe to both models of our phone? Im on Z008 Just curious
Click to expand...
Click to collapse
Hate to be the bearer of bad news...
Ports assume the two devices (the base device, and the one to port to) are very similar (same chipset, et cetera). A good example (I used to use HTC) is the Sensation was a very good base for the MyTouch 4G Slide (they even shared the same battery design/size).
Unfortunately the Zenfone 2 and either of the new Nexus devices are worlds apart from each other. They don't share the same architecture, let alone chipset. We would be better off piggybacking off the work of the ASUS Fonepad 7 FE375CG (Z3560 Chipset) or the Asus Memo Pad 8 ME581CL (Z3580) - but in reality, in terms of updates - it's more likely we would be the base for those devices in a few months time.
Sorry.
---------- Post added at 20:36 ---------- Previous post was at 20:33 ----------
AkiroX said:
If the source code isn't released we can't do anything. So it's probably not even the dev's fault as much as it is Google's.
All we can do is wait.
Click to expand...
Click to collapse
That's right, all we can do is wait, then build from source once available.
Porting has it's place, but it can be a gong-show.

Source already available
We should wait for devs to build it ?

AL_IRAQI said:
Source already available
We should wait for devs to build it ?
Click to expand...
Click to collapse
AOSP is available, but now we have to wait to have CM13 in a manageable state. I don't imagine cpalmer and jrior001 will put on the brakes with CM12.1 to build straight from AOSP.
ROMe wasn't built in a day, and it will be months before CyanogenMod will be able to have the AOSP source modified for the new CM13 and reach the coveted milestone one.

Yap, waiting for you too @joel.maxuel for working on it

allasca said:
Yap, waiting for you too @joel.maxuel for working on it
Click to expand...
Click to collapse
Why am I being thrown under the bus? :silly:
In all seriousness, if CarbonROM continues to base their stuff off of CM (which I heard talk of that changing), this time around they may be once again months behind CM in terms of an official product (e.g, none of their devices have hit official status yet this round, or at least as of last night).
Not to speak ill of course, which is why I am curious of the route that does not involve basing off of CyanogenMod.
No guarantees with my involvement to 6.0, but I am interested in the job. I just can't predict what my life demands are going to be like in the spring (time seems tight right now, but I manage).
My short and medium term plans is to keep the 5.1 builds going, hopefully even after Carbon calls it quits for this branch to focus on the new one. The only possible things stopping me are:
Carbon leaves lp5.1.1 branch perfect, meaning I don't even have to do monthlies anymore (also means no future security issues)
CyanogenMod breaks their sources badly (has happened recently when Carbon couldn't keep up)
I get the official stock 6.0 image which ends up breaking modem usage - leaving me unable to properly downgrade to 5.1 to test
It feels like with this plan, someone is going to beat me to the punch by building a CarbonROM mm-6.0 ahead of me. Which is why at some point, I will (probably) be doing builds in parallel. But we shall see when we get there.

Just read this: http://arstechnica.com/gadgets/2015/10/android-6-0-marshmallow-thoroughly-reviewed/
Doesn't seem much for us CM12.1 users to get very excited about anyway. Material design not changed from Lollipop, Google Now launcher already updated with the changes, selectable app permissions already included in CM12.1 via Privacy Guard, fingerprint api and 4K display stuff irrelevant to our zenfones...
Personally, I think a stable CM12.1 (5.1.1) build is more important. In fact, the unofficial build we already have is stable and very nearly there, but I would rather see the last few kinks ironed out and official status before any time is put into 6.0

Most importantly, it should support 64bit for the z00a. Any news on this?
Sent from my iPhone using Tapatalk

The next month, asus update android 5.1 for zenfine 2, maybe 6.0 ? I don't know this,

"Android O - 8.0" PossIble for Zenfone 2?

Hello everyone, it is possible to receive custom ROM "Android O" for our Zenfone 2 ???

O was just announced, we're going to have to wait a little longer before we can know if it's possible, and a lot longer before it's actually built.

adobrakic said:
O was just announced, we're going to have to wait a little longer before we can know if it's possible, and a lot longer before it's actually built.
Click to expand...
Click to collapse
It's a good thing you answered first. I would not have been as diplomatic. Lol
Sent from my ASUS_Z00A using Tapatalk

Here comes ETA posts

Yes, it is posible but first need the sources and the sources are released after the official version is pushed to Nexus devices, maybe in October September will have and alpha version of Android O

Completely possible, thru custom ROMs
Sent from my Zenfone Max on AOKP N

mrichiem said:
Completely possible, thru custom ROMs
Sent from my Zenfone Max on AOKP N
Click to expand...
Click to collapse
I wouldn't say completely. Google is laying out minimum hardware requirements for stuff like audio, vr and ar which our old phone may not mean.
But do I have confidence that our devs will make everything else work? Yes, completely. Although it's gonna take a long time. I will be elated if N hits stable.

Since the question of this topic can't really be answered, someone knows how long statistically can a device be supported by custom roms? I mean maybe Android Z is too far fetched, but android P for example?

distant_thunder_89 said:
Since the question of this topic can't really be answered, someone knows how long statistically can a device be supported by custom roms? I mean maybe Android Z is too far fetched, but android P for example?
Click to expand...
Click to collapse
Same answer as before, it all depends on hardware requirements
Sent from my ASUS_Z00A using Tapatalk

Thanks all for different opinions and answers

blazzer12 said:
I wouldn't say completely. Google is laying out minimum hardware requirements for stuff like audio, vr and ar which our old phone may not mean.
But do I have confidence that our devs will make everything else work? Yes, completely. Although it's gonna take a long time. I will be elated if N hits stable.
Click to expand...
Click to collapse
well my current daily driver is an AOKP 7.1.1 Nougat on my Zenfone Max ZC550KL with no bugs so we can hope the same for O when Lineage OS releases its own version.
Sent from my Zenfone Max on AOKP N

kenbo111 said:
Same answer as before, it all depends on hardware requirements
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Hardware is the least of our problems, considering the one in Zenfone 2 (ZE551ML for example) is more than adequate.
Google making up it's own hardware requirements is nothing more than pandering to the idea of planned obsolescence to be honest so that they can sell newest phones.
I think that if the devs can get their hands on viable drivers that support the hardware in our devices and are compatible with Android 8, then technically, it shouldn't be an issue.
For Oreo, google would be pushing certain updates (fixes, etc.) not as a standalone feature, but something that would work in the same way as Windows and MacOS system updates do within the same OS version.
We know Windows updates usually work on a variety of hardware if the Windows as an OS is the same... the only thing that you also need are drivers to properly support the hardware in question (which can be difficult if the hardware is ancient, but I doubt this would apply to Zenfone 2) - this especially applies to upgrading from say Windows 7 to Windows 10 for example as some features like a microphone might stop working if the hardware in question was say from 10 years ago. Works on say Windows 7 for example because Vista drivers were made for the hardware in question which were compatible with Windows 7 to a point, but for Windows 10, compatibility between drivers for older Windows was not maintained and new drivers need to be written.
So, large OS replacement would likely depend on hardware drivers support and updating the OS sequentially shouldn't be an issue if the drivers exist - if they don't... then it's a problem.
Manufacturers tend to stop supporting hardware after a certain time... OEM's are even worse.
If we can find drivers independently from a company that produced it, then it might be possible to find more recent drivers that work.
In case of GPU's (or any other hardware inside your PC), you wouldn't rely on the OEM for drivers. You'd go to AMD's or Nvidia's websites to download latest drivers.

issou la chancla ?
:highfive:

PX5 kernel sources

Is there any repo for the PX5 kernel sources? I've looked all over the place, but so far, somehow have managed to miss it if it's out there. USB audio and the DWC USB OTG issues are my primary concern here. Not a whole lot that can be done about that w/o the ability to build new kernels (or modules at the very least).

No.

Has anyone contacted the various manufacturers regarding this? Seems like a GPL violation if they're not distributing the source. Granted, that (GPL non-compliance) has been a long standing problem, but still.

cwz said:
Has anyone contacted the various manufacturers regarding this? Seems like a GPL violation if they're not distributing the source. Granted, that (GPL non-compliance) has been a long standing problem, but still.
Click to expand...
Click to collapse
I got the 4.4 source code from here to build for the px5. I'm waiting to build a USB cable for recovery before i test my kernel. I haven't tried pushing any modules to it yet over adb but will once my USB video adapter comes in.
https://github.com/rockchip-linux/kernel
I don't think we're going to get a fully working proper source release, especially for Android just because of the GPU the px5 uses. They've historically never released a Linux or android driver for it. They have two GPU drivers in this source but they don't build. And wouldn't work without the android device files either.

notime2d8 said:
I got the 4.4 source code from here to build for the px5. I'm waiting to build a USB cable for recovery before i test my kernel. I haven't tried pushing any modules to it yet over adb but will once my USB video adapter comes in.
https://github.com/rockchip-linux/kernel
I don't think we're going to get a fully working proper source release, especially for Android just because of the GPU the px5 uses. They've historically never released a Linux or android driver for it. They have two GPU drivers in this source but they don't build. And wouldn't work without the android device files either.
Click to expand...
Click to collapse
They're supposed to provide the kernel sources that they used to produce the kernel images that they're shipping. The GPU drivers (last time I checked anyhow) weren't subject to the GPL because they're written as modules. This is no big deal though -- it's that way for a lot of devices of similar ilk. What I'm more interested in is getting better USB support for USB DACs. The Synopsys DWC USB controller is notorious for the extreme interrupt load it causes (and other issues). There have been some recent improvements to the driver, but without kernel source, it's going to be pretty difficult to even attempt to get a better driver in.