[CAF/AOSP][LA.BF.1.1.3-01310-8x74.0][6.0.1][STABLE]AOSParadox Project 2.1 - 20160413

[joaoennes]

sorry but tri state keys means?

alert slider

 

[Thecrazyskull]

Hum ... But in my understanding, when Google released a new version, it is based on CAF + new features not CAF. And then, CM works on that right? Adding also no CAF features...
In your case, you are totally CAF based (except if you introduce specific features...)
Then, in some times, CAF will release a CAF android N version which will be the starting point of Android O ...

Am I right?

No.
Google creates the operating system called android aka AOSP in the dev world.
CAF is aosp made to work (good) with qcom devices.
What cm does is initially base on CAF, when a new android version comes out then they just merge AOSP updates instead of waiting for CAF.
Obviously every new android version is based off off the last one, so android N is based on android M.

 

[mousse04]

No.
Google creates the operating system called android aka AOSP in the dev world.
CAF is aosp made to work (good) with qcom devices.
What cm does is initially base on CAF, when a new android version comes out then they just merge AOSP updates instead of waiting for CAF.
Obviously every new android version is based off off the last one, so android N is based on android M.

Thanks, but if we think about timing :
Google releases its code (AOSP) : this first release can't be CAF oriented as qcom doesn't know what's inside the new AOSP, right ?
CAF works on it to optimize it for com devices, then release it.

What I don't understand is that Google and CM must use CAF code at a moment right? When exactly ?

Edit : and what about OEM using qcom SOC? Do they start from AOSP from Google or AOSP from CAF? And supposing they use CAF, all features they will add will not be CAF oriented. Can they request to the CAF consortium to optimise their code?
Do you know if Mediatek has same kind of consortium?

 

[Thecrazyskull]

Thanks, but if we think about timing :
Google releases its code (AOSP) : this first release can't be CAF oriented as qcom doesn't know what's inside the new AOSP, right ?
CAF works on it to optimize it for com devices, then release it.

What I don't understand is that Google and CM must use CAF code at a moment right? When exactly ?

Edit : and what about OEM using qcom SOC? Do they start from AOSP from Google or AOSP from CAF? And supposing they use CAF, all features they will add will not be CAF oriented. Can they request to the CAF consortium to optimise their code?
Do you know if Mediatek has same kind of consortium?

Aosp doesnt need any CAF code, cm does in fact cm is based on CAF.
Usually OEM'S with a qcom SOC base on CAF.
No idea about MTK, doubt they have something like this.

 

[h2o64]

Thanks, but if we think about timing :
Google releases its code (AOSP) : this first release can't be CAF oriented as qcom doesn't know what's inside the new AOSP, right ?
CAF works on it to optimize it for com devices, then release it.

What I don't understand is that Google and CM must use CAF code at a moment right? When exactly ?

Edit : and what about OEM using qcom SOC? Do they start from AOSP from Google or AOSP from CAF? And supposing they use CAF, all features they will add will not be CAF oriented. Can they request to the CAF consortium to optimise their code?
Do you know if Mediatek has same kind of consortium?

As you may imagine, Google and Qualcomm (CAF) are good friends. And I bet Qualcomm already made Android N Tags for its chipsets. And that's great, because OEMs could get the caf tags before us.
Mediatek also have an equivalent to CAF

 

[anshu goel]

I may have missed this but can I install supersu in this rom?

 

[loveboy_lion]

Yes u can install supersu

Sent from my ONE E1003 using Tapatalk

 

[mousse04]

As you may imagine, Google and Qualcomm (CAF) are good friends. And I bet Qualcomm already made Android N Tags for its chipsets. And that's great, because OEMs could get the caf tags before us.
Mediatek also have an equivalent to CAF

So, finally, what you are proposing with your ROM, is a "stock AOSP CAF" ROM, am I right?

 

[h2o64]

So, finally, what you are proposing with your ROM, is a "stock AOSP CAF" ROM, am I right?

So in the custom roms world you have (basically) those options :
- AOSP roms for Nexus devices (or omnirom)
- CM roms for every devices (based on caf)
We propose our own ROM based on caf that isn't cm based. And our goal is to keep it AOSP.

 

[mousse04]

So in the custom roms world you have (basically) those options :
- AOSP roms for Nexus devices (or omnirom)
- CM roms for every devices (based on caf)
We propose our own ROM based on caf that isn't cm based. And our goal is to keep it AOSP.

Thanks you so much for all your explanations guys.
One last question however, when you said "AOSP for Nexus devices", it is because Google release AOSP code after testing it on their Nexus family right? Because AOSP code can be adapted for any devices ...

 

[h2o64]

Thanks you so much for all your explanations guys.
One last question however, when you said "AOSP for Nexus devices", it is because Google release AOSP code after testing it on their Nexus family right? Because AOSP code can be adapted for any devices ...

Yes. But AOSP code can't be adapted to every devices.

 

[mousse04]

Yes. But AOSP code can't be adapted to every devices.

OK, got it.

Thanks again @Thecrazyskull and @h2o64 for answering all my stupid questions

 

[mousse04]

So, if we summarize our discussion, the best, if you want an optimized ROM, is either to take:
CM based ROM (but we do not know how percent of the code is not from CAF)
your ROM
all others AOSP based ROM are good, for sure, but not CAF optimized ...

 

[Mithrandir_]

Hey, i'm pretty sure that there isn't the Debug over tcp/ip in this rom, will it be implemented? I'm always using it for test my applications. (I know there's also the cable, but over wifi was better for me)

 

[s3r3tin]

is "double tap to wake" function going to be implemented ?

 

[joaoennes]

is "double tap to wake" function going to be implemented ?

Its already available. Install kernel adiutor and enable it on the wake control option.

Sent from my OnePlus using XDA Labs

 

[s3r3tin]

Its already available. Install kernel adiutor and enable it on the wake control option.

Sent from my OnePlus using XDA Labs

thank you

 

[mousse04]

Its already available. Install kernel adiutor and enable it on the wake control option.

Sent from my OnePlus using XDA Labs

Doesn't work perfectly ...

 

[h2o64]

New build !

Hello,
a new build is available!

CHANGELOG :

- Adress all the RIL related issue
- Full vendor blobs rebase
- Adress deep sleep issue
- Improvements on code base

Download
http://download.aosparadox.org/AOSParadox/onyx/

This should fix all the RIL/Radio issues faced.
Next step is the KeyHandler : as this is a very important and tricky thing that I'm not very good at. So I made this repository (https://github.com/AOSParadox/keyhandler) where anyone can make a pull request, and we can do our own KeyHandler there ( @OldDroid)

Enjoy

 

[Jude Aranha]

Hello,
a new build is available!

CHANGELOG :

- Adress all the RIL related issue
- Full vendor blobs rebase
- Adress deep sleep issue
- Improvements on code base

Download
http://download.aosparadox.org/AOSParadox/onyx/

This should fix all the RIL/Radio issues faced.
Next step is the KeyHandler : as this is a very important and tricky thing that I'm not very good at. So I made this repository (https://github.com/AOSParadox/keyhandler) where anyone can make a pull request, and we can do our own KeyHandler there ( @OldDroid)

Enjoy

Any news on Tristate or Gestures ? I'm downloading the build anyway, cant wait any longer <3
Thanks @h2o64 <3 <3