Database Users

NVIDIA Tegra DRM Driver Might Appear In Linux 3.8

I don't know if this might be useful for devs, but since the Linux kernel is open source, i guess it might help a little.
Link do the post: http://www.phoronix.com/scan.php?page=news_item&px=MTIyNTc

Staging stuff is the 'corner of crap' of the kernel - beta stuff which does not meet the quality standards of the kernel. In other words, those drivers won't be fun until they stabilize a bit.

Either way problem with atrix is not that we can't use current closed sources drm drivers but that we have to make kernel with support for all internals of atrix like buses, controllers and other devices. And then connect all things together with correct frequncies, voltages, pinmuxes. That makes things hard. Especially because things in 2.6.32 were done dynamically and it's hard to read it from code. Yet I'm working on that
Sent from my MB860 using xda app-developers app

for now, seems to exist no 3D support. But I believe that this mature driver can serve to help.

First someone would have to port our kernel to 3.8 or downport drm driver from 3.8 to 2.6.32. Sooner we'll have port to 2.6.34.9 and HWA.
Sent from my MB860 using xda app-developers app

3.8 ? I think our tablet has 3.08 kernel

It may have 3.0.8. As for 3.8 it's not even released yet, we have now 3.7 as an unstable/development version of 3.8, and Nvidia's DRM driver integration is planned for 3.8. And even then it's not gonna show up in android soon, as android kernel is not fully integrated with mainline kernel yet. So looong road till we have something we can call stable and usable. For now open DRM drivers don't have 3D support, so it basically leave us here where we are currently. It's nice Nvidia is working with opensource community, but these drivers are mainly for embeded tegra2 based systems (like in cars or washing machines). I'm not saying it can't be used in our phone, but you won't gain much. Unless there is Android 7.0 and nvidia no longer supports tegra2 platform and we want it badly then we can use it (i think).

CAF/Non-CAF

I somewhat read what the difference between the two were, but I don't quite understand it completely. I was wondering (based on user preference) which is better.
I was using a ROM that was Non-CAF and now I'm using one that is, and I don't notice a difference really. I was wondering if someone could help me understand better.

+1

TheKnux said:
I somewhat read what the difference between the two were, but I don't quite understand it completely. I was wondering (based on user preference) which is better.
I was using a ROM that was Non-CAF and now I'm using one that is, and I don't notice a difference really. I was wondering if someone could help me understand better.
Click to expand...
Click to collapse
Caf relates to code aurora forum (Google it).. Its where Qualcomm updates its stuff regularly. While aosp is googles kernel branch. Caf has more updates and optimisations for Qualcomm chipsets. The difference... I can't say there is much since our phones are already quite powerful to handle most things thrown at it.. But again, as I mentioned its optimisations and etc, so on paper better performance, battery and what not.
Sent from my Nexus 4 using Tapatalk

CodeAurora (CAF) - These are Qualcomm's reference sources for their platform. This is what they provide to OEMs, and what nearly all OEMs base their software off of. As a result - nearly all non-Nexus devices are running kernels/display HALs/etc. that are derived from a CAF baseline.
Google's software baseline, or AOSP - Usually when Google starts working on a new Android version, they'll fork from CAF at the beginning. Very often Google will be adding "new" features specific to the new Android version, while Qualcomm will continue with performance enhancements and bugfixes against the "old" baseline.
So when a new Android revision comes out, you have two baselines: CAF which is usually "ahead" in performance but "behind" in features, and AOSP which is the opposite.

from what i've noticed CAF is better, i get less stuttering this is the sort of thing that optimizations usually improves on.

Stock vs open source drivers

I don't think I fully understand how ROM's device drivers work. Stock is supposed to be more stable because most manufacturers use closed source drivers, which have to be reverse engineered for any non stock ROM (is that correct?).
But on my Nexus 4, I've had the same problems with stability as any other device, despite the open source drivers. Apps still frequently cause my phone to reboot, which from what I understand can only be caused by driver bugs, otherwise the app would simply crash.
Am I just expecting stability AND features and wondering why I can't have my cake and eat it too? I'm running the stable version of SlimKat atm and usually go for stable versions of ROMs that go for speed and stability, no experimental bleeding edge features or anything.
Could anyone explain what I seem to be missing. I'm an amateur programmer so technical details appreciated.

v1nsai said:
I don't think I fully understand how ROM's device drivers work. Stock is supposed to be more stable because most manufacturers use closed source drivers, which have to be reverse engineered for any non stock ROM (is that correct?).
But on my Nexus 4, I've had the same problems with stability as any other device, despite the open source drivers. Apps still frequently cause my phone to reboot, which from what I understand can only be caused by driver bugs, otherwise the app would simply crash.
Am I just expecting stability AND features and wondering why I can't have my cake and eat it too? I'm running the stable version of SlimKat atm and usually go for stable versions of ROMs that go for speed and stability, no experimental bleeding edge features or anything.
Could anyone explain what I seem to be missing. I'm an amateur programmer so technical details appreciated.
Click to expand...
Click to collapse
I wish someone could answer this because I'm considering one of the new Nexus devices because I thought I could have this best of both worlds that he speaks of. Is this not the case, do open source driver devices like Nexus phones suffer with the same issues as other unlocked phones that have closed source drivers?

LineageOS soon for the Mi A1?

Hello,
When do you think we will have LineageOS for our device? Unofficial or official? Thanks.

That's a good question. Let the experts about ROM development say something
Sent from my Mi A1 using Tapatalk

Well, I'm no expert but Xiaomi needs to release the kernel source before we start seeing custom ROMs. They said they would do it in three months. So, let's wait and see.

The phone is pretty accessible and runs under the android one frechise so, just wait till they release the sources.

When kernel sources are released, im sure custom ROMs will start to roll out.

I really hope guys!

Filip013 said:
Well, I'm no expert but Xiaomi needs to release the kernel source before we start seeing custom ROMs. They said they would do it in three months. So, let's wait and see.
Click to expand...
Click to collapse
Can you please state your source? Thank you.

What we need is a custom Kernel first , This phone is Awesome but the score is worse than Redmi Note 3 ?! That's not fair

Yash98 said:
Can you please state your source? Thank you.
Click to expand...
Click to collapse
Sure. Here.

JoKeRLeE said:
What we need is a custom Kernel first , This phone is Awesome but the score is worse than Redmi Note 3 ?! That's not fair
Click to expand...
Click to collapse
It's because the Redmi Note 3 has a better CPU "Snapdragon 650" vs The Mi A1 "Snapdragon 625"
what's really weird is that Xiaomi downgrade the CPU on the newer phone "Redmi Note 4" to the Snapdragon 625

JoKeRLeE said:
What we need is a custom Kernel first , This phone is Awesome but the score is worse than Redmi Note 3 ?! That's not fair
Click to expand...
Click to collapse
Benchmark score doesn't matter and by the way Redmi Note 3 does have a faster processor but it is not power efficient and heats up more than 625.

Yash98 said:
Benchmark score doesn't matter and by the way Redmi Note 3 does have a faster processor but it is not power efficient and heats up more than 625.
Click to expand...
Click to collapse
The SD625 is built on 14nm process whereas the SD650 is built on 28nm process(older, gets heated after playing for long sessions, and reduces its speed)

venom928 said:
The SD625 is built on 14nm process whereas the SD650 is built on 28nm process(older, gets heated after playing for long sessions, and reduces its speed)
Click to expand...
Click to collapse
I knew that.
Didn't find it necessary to mention the tech stuff.

Why would you asking custom rom when you already have pure android,the stock one is definitely more stable,our software is actually already incredible only need more fixes on camera stability and some minor issues,I'd prefer asking for fixing the issues instead of build from the scratch

afrizal87 said:
Why would you asking custom rom when you already have pure android,the stock one is definitely more stable,our software is actually already incredible only need more fixes on camera stability and some minor issues,I'd prefer asking for fixing the issues instead of build from the scratch
Click to expand...
Click to collapse
There can be multiple reasons. I am waiting for the sources in order to have a clean Lineage install with signature spoofing. That and microg on top to get rid of gapps.
Also, maybe some people like the customisation that exists in some particular roms.

+1, also waiting for LineageOS for this device.
Sent from my iPhone using Tapatalk

waiting for lineageOS

Custom ROM with 3.18 kernel

First of all I would like to thank all the great devs that keep supporting this phone.
But I miss a really bugless ROM. ROMs with 3.18 kernel were almost perfect, but they aren't developed anymore. 4.9 kernel is great too, but it has some annoying (for me at least) limitations. Miui camera doesn't work properly and it's a pity because it's the only app (as far as I know) that can use both sensors at the same time. Nhappyman's camera module isn't working (no smooth videos and no long exposure).
Mtp and vibration aren't working in TWRP custom recovery.
Is there any developer that can build an updated ROM based on 3.18 kernel? I bought a Mi A1 for dual-camera setup and I would like to use his full potential with MIUI camera AND GCam. At the moment it's possible only on 3.18 kernel so I'm wondering if there is any "brave" Dev who wants to go that way. I think that many other users like me are waiting for that. Am I wrong?

You're right, I agree with you. Of course it is quite an achievement for the development of this device, and I actually enjoy the new kernel and it's securities advancements, but it is not stable compared to the officially supported 3.18. For example, I have a Quick charger but can't use it properly because it's not working on kernel 4.9, at least right know.
Not being ungrateful btw, I totally support the continuous development of 4.9, and I hope someday it will be just as stable as 3.18.

sipollo said:
First of all I would like to thank all the great devs that keep supporting this phone.
But I miss a really bugless ROM. ROMs with 3.18 kernel were almost perfect, but they aren't developed anymore. 4.9 kernel is great too, but it has some annoying (for me at least) limitations. Miui camera doesn't work properly and it's a pity because it's the only app (as far as I know) that can use both sensors at the same time. Nhappyman's camera module isn't working (no smooth videos and no long exposure).
Mtp and vibration aren't working in TWRP custom recovery.
Is there any developer that can build an updated ROM based on 3.18 kernel? I bought a Mi A1 for dual-camera setup and I would like to use his full potential with MIUI camera AND GCam. At the moment it's possible only on 3.18 kernel so I'm wondering if there is any "brave" Dev who wants to go that way. I think that many other users like me are waiting for that. Am I wrong?
Click to expand...
Click to collapse
You can use LR v10.0.3 it's still based on 3.18 based kernel. Or go for Revenge OS, it's also 3.18 based

I'm not going to say anything about TWRP installer that was never supported officially by TeamWin or quick chargers that aren't even supported by our device, but I have a few things that I want to say specifically about MIUI Camera (and the reason why I'm always acting cocky when someone talks about it).
Supporting it was and always will be too much of a hassle for developers. It's not because "damn devs don't care about meme camera", but rather because whatever Xiaomi does for their camera features is very far from perfect, tends to break very often and also introduces random issues with third-party camera apps.
Recent switch to the open source camera HAL helped us to get a much more stable and reliable base (as well as fixing some very annoying issues we had before) but it also was the final nail in the coffin of MIUI Camera as it relies on undocumented proprietary features that we can't implement in any possible way.
I know that it can be hard for someone to cope with the lack of some well advertised marketing feature essential camera functionality, but we also have to go to concessions to make our support continuous and more future-proof.

flex1911 said:
I'm not going to say anything about TWRP installer that was never supported officially by TeamWin or quick chargers that aren't even supported by our device, but I have a few things that I want to say specifically about MIUI Camera (and the reason why I'm always acting cocky when someone talks about it).
Supporting it was and always will be too much of a hassle for developers. It's not because "damn devs don't care about meme camera", but rather because whatever Xiaomi does for their camera features is very far from perfect, tends to break very often and also introduces random issues with third-party camera apps.
Recent switch to the open source camera HAL helped us to get a much more stable and reliable base (as well as fixing some very annoying issues we had before) but it also was the final nail in the coffin of MIUI Camera as it relies on undocumented proprietary features that we can't implement in any possible way.
I know that it can be hard for someone to cope with the lack of some well advertised marketing feature essential camera functionality, but we also have to go to concessions to make our support continuous and more future-proof.
Click to expand...
Click to collapse
Totally understandable, it's not rocket science to know that exclusive "features", which is closed source, is really hard (mostly impossible) to port to custom development. Many devices suffers from this, like the implementation on Moto display on Motorola phones, for example. I'm not a developer myself, but I know a thing or two with my experience as android enthusiast, and for development to work it means you're gonna let some "goodies" go in favor of it.
Thanks for your work btw!

Shubham2509 said:
You can use LR v10.0.3 it's still based on 3.18 based kernel. Or go for Revenge OS, it's also 3.18 based
Click to expand...
Click to collapse
Revenge use 4.x now, so the only updated rom with 3.18.x is Lineage 15.1

Never_Sm1le said:
Revenge use 4.x now, so the only updated rom with 3.18.x is Lineage 15.1
Click to expand...
Click to collapse
In the next update ROS will be updated with 3.18

Shubham2509 said:
In the next update ROS will be updated with 3.18
Click to expand...
Click to collapse
Really? Nice, have been looking for an updated pie rom running 3.18

Now that Flex gave us the possibility to use miui camera on 4.9 kernel there's no need of 3.18 anymore (IMHO). To use MTP on TWRP we can boot it from PC and it will work.

Touch screen misbehaves with 4.x kernel
My mi a1 touch screen misbehaves with 4.9 kernel.
So i have to stick with the stock rom even i want to use a custom rom.
Am i the only person facing to this kind of problem?

Same problem here guys, anyone know how to fix this? :crying:

sujiththilakasiri said:
My mi a1 touch screen misbehaves with 4.9 kernel.
So i have to stick with the stock rom even i want to use a custom rom.
Am i the only person facing to this kind of problem?
Click to expand...
Click to collapse
Me too, in fact my screen doesn't work at all with 4.9 kernel. It was a cheap replacement from aliexpress. I was hoping to find some updated ROMs with 3.18 but I will have to just stick to stock. It's a shame.