Related
Seeing how this is a nexus device, there should be proper source release right? But this is Samsung, who have in the past proved to be one of the worst offenders in terms of releasing source. I originally had the note 10.1 but returned due to the terribly laggy software and insanely bad build quality. I'm unwilling to buy another device that lacks developer support, especially from Samsung.
mysystem said:
Seeing how this is a nexus device, there should be proper source release right? But this is Samsung, who have in the past proved to be one of the worst offenders in terms of releasing source. I originally had the note 10.1 but returned due to the terribly laggy software and insanely bad build quality. I'm unwilling to buy another device that lacks developer support, especially from Samsung.
Click to expand...
Click to collapse
Forget who makes it, a Nexus runs Googles software and will get direct updates from them. No kies, no waiting
My old n7 got the 4.1.2 update ** the day ** it was released worldwide.
Sent from my GT-I9300 using xda premium
Kernel source is already available at https://android.googlesource.com/kernel/exynos/ . It's going to run Linux 3.4 and the codename is manta.
ben1066 said:
Kernel source is already available at https://android.googlesource.com/kernel/exynos/ . It's going to run Linux 3.4 and the codename is manta.
Click to expand...
Click to collapse
Kernel is not enough! Samsung has to release the kernel because the law says so.
I'm with the OP. I have the SGS3 and things look pretty bad with the sources problem.
Even if stock is great many of us like to experience other possibilities, and CM on a tablet would be so sweet.
So yeah. I'm very very very worried about this issue on the nexus 10. My guess is we won't have the sources. Samsung won't release them.
Didn't they release them for the Nexus S? I don't count the Galaxy Nexus since that was a TI/PowerVR SoC.
This is actually a big moment for Samsung. They've got their Exynos processor and drivers on the Google update list which should mean it'll be faster to update all their other devices (at least from what I've read concerning Exynos drivers).
Am I missing something here? The updates come from Google, so the sources will be in the Android source tree.
alias_neo said:
Am I missing something here? The updates come from Google, so the sources will be in the Android source tree.
Click to expand...
Click to collapse
This.
All Nexus devices should have source for building the ROM and kernel posted online by Google for people to build from
EniGmA1987 said:
This.
All Nexus devices should have source for building the ROM and kernel posted online by Google for people to build from
Click to expand...
Click to collapse
Is that not what I just said? They're in the source tree. If they're not public at the moment, they should be soon after the device is released, just as they have been for all past nexus devices.
The fact that Samsung built the hardware here is irrelevant.
alias_neo said:
Is that not what I just said? They're in the source tree. If they're not public at the moment, they should be soon after the device is released, just as they have been for all past nexus devices.
The fact that Samsung built the hardware here is irrelevant.
Click to expand...
Click to collapse
he actually agree with you, not the opposite
I read some posts on G+ and noticed all cyanogen i9300 mainterners complain about samsung sources policy, they release out-dated, imcompatible source code. I want know what samsung have released after Open Exynos petetion.
On originboard.com, I have only found 4x12 sources for ICS, not JB.
They've given is squat. Broken, useless crap which requires a sh*t ton of hackery to even work.
Nothing.
Just like the life left in this beaten horse.
After some research I found something.
Samsung actually released some exynos sources (camera, mali) after petetion, but they are outdated and can't be used with Jelly bean HWA.
We have only extracted pre-built JB HWA, and older sources (probably ICS compatible)
But can ICS sources be updated to support Jelly bean?
At this point of time only mali (OLD), camera (OLD), thermal control, barometer, LED are open-source (I found them on github and originboard.com).
GR0S said:
After some research I found something.
Samsung actually released some exynos sources (camera, mali) after petetion, but they are outdated and can't be used with Jelly bean HWA.
We have only extracted pre-built JB HWA, and older sources (probably ICS compatible)
But can ICS sources be updated to support Jelly bean?
At this point of time only mali (OLD), camera (OLD), thermal control, barometer, LED are open-source (I found them on github and originboard.com).
Click to expand...
Click to collapse
They have been analyzed, looked over, poked at, cursed at, burned and hacked by CM team.
I'm pretty sure that the actual quality of 10.1 is very close to as good as it gets (without the damned sources).
Please search and see how this saga has evolved and progressed to. I hold no hope of seeing sources and neither should you or anyone.
If the sources Samsung is throwing out every now and then are so out dated, crappy and bad documented, what the hell do GM, AndreiLux, AndiP and all the other kernel devs work with??
I don't get it.
AW: Exonys jellybean sources
*Exynos
Sent from my GT-I9001 using xda app-developers app
According to the devs, what's really needed is the userspace sources, so until those are released, all this is useless. Samdung is under no obligation to release these, so they probably never will.
harise100 said:
If the sources Samsung is throwing out every now and then are so out dated, crappy and bad documented, what the hell do GM, AndreiLux, AndiP and all the other kernel devs work with??
I don't get it.
Click to expand...
Click to collapse
Samsung do release the latest kernel sources because they are legally obligated to. But AOSP ROMs such as CM require more than just working kernels.
XeLLaR* said:
*Exynos
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
+1
Mimsy said:
Samsung do release the latest kernel sources because they are legally obligated to. But AOSP ROMs such as CM require more than just working kernels.
Click to expand...
Click to collapse
Yeah, codeworkx said that kernel source is always free, but they need userspace
Enviado desde mi Tamagotchi usando Tapatalk
without userspace source development is limited
Hi! This is my first post on XDA.
As a user of CM for more than a year ago on my i9300, and after enduring a lot of bugs, I wonder: What happens to CM?
It's a known fact that the Exynos platform is a headache for developers because there is no documentation or open sources from Samsung. So, things like the camera, the sound system, the HDMI output and the GPU do not work as they should.
However, here are many good developers who have fixed these bugs, or at least improve them a bit. And most of these fixes are open source and accessible by everyone on Github.
So, what is waiting CM to implement them? Giving credit to their authors, obviously.
CyanogenMod announces itself as an alternative to the stock firmware that lets you take full advantage of your smartphone, making it better and more stable. Now they are also a company: Cyanogen Inc. As a reputable brand, it should offer a higher quality firmware. ROMs like Nameless (I'm using it right now) works better even being "not official".
This is just an opinion as a user. I'm not criticizing or forcing anyone to do anything. But if there are hundreds of people using a ROM with bugs that were fixed, why not implement them? I would be the first to help, but my skills are just about webdev.
Respect and thanks for i9300 developers on XDA, and sorry about my bad English. When I use my native language I express myself MUCH better. Trust me. lol
Thanks for reading.
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
Thanks for answering my topic. The opinion of a developer like you is very appreciated.
This situation only seems to give more reasons for not buy a Samsung phone again. This lack of support from the manufacturer is a disrespect to the user's investment. And fragmentation strikes again. Sad but true.
Thanks again for your great work of keeping this device alive for all of us.
StephenJSweeney said:
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
Click to expand...
Click to collapse
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
ouch01 said:
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
Click to expand...
Click to collapse
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
i feel you
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
StephenJSweeney said:
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
Click to expand...
Click to collapse
The thing with Motorola is that their stock roms are basically just stock android. No laggy touchwiz skins, just a google launcher. Bloatware is at a minimum. A low spec phone like the moto G still is great because of how vanilla its experience is.
Rumours have it that the galaxy S6 international variant will have an exynos processor. I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch. As it is now, phone's are so fast, that it's very hard to find a way of improving them. Like who compares app opening times nowadays? That will be much the case for 2015's flagships as well. I doubt I'd be disappointed if I had the next Samsung release if I thought I'd be in for a laggy UI, it's just whether I can tolerate the touchwiz experience or if I wanna switch to a vanilla aosp rom. That's where the problem arises.
arashvenus said:
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
Click to expand...
Click to collapse
But only in your imagination. There is noone at slimrom. Just check their gerrit.
whatsgood said:
Rumours have it that the galaxy S6 international variant will have an exynos processor .... I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch.
Click to expand...
Click to collapse
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Correct.
Eleve11 said:
Correct.
Click to expand...
Click to collapse
Well then, no more Samsung phones for me, then. Not unless they use Qualcomm..!
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
whatsgood said:
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
Click to expand...
Click to collapse
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
JustArchi said:
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
Click to expand...
Click to collapse
Yeah +1 for that. My next Phone will be definitly a Sony or a One plus. I think both are the developer friendliest in android ...
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
khanmein said:
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
Click to expand...
Click to collapse
Yeah you are right but i think the most decent phone is the htc one......i would buy a windows phone rather than an iPhone
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
whatsgood said:
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
Click to expand...
Click to collapse
its useless even if they port it to our i9300..1gb of ram..maybe its time to upgrade to more stronger phone..
Seems obsoletism is occurring faster & faster.
upon release Feb 14 I upgraded to the galaxy s 5, now regret that move, at&t won't allow custom Rom! It's been getting glitchy, no clean up?! That's why I bought the dam thing... So last week I said f it. I bought the flagship iPhone, 6s plus 64... And again I'm regretting it's typical non functionality . Dam! oh well at least I look cool, right?. I hate the bloat of the quickly outdated Androids, they need to be replaced sooner & sooner.
Anyone tell me if custom Rom Is the way to go, on which device? I'm thinking about ditching my new iPhone 6s plus, but just learned that the nexus 6p has a fuse denying custom Rom to be ran. ? boo!
Another quick question, is there a particular forum that I might be interested in reading?
What does this have to do with the custom ROM called Paranoid Android?
Pirateghost said:
What does this have to do with the custom ROM called Paranoid Android?
Click to expand...
Click to collapse
I've been reading up once again, so paranoid android is custom Rom? Is it meant for any particular device, or anything goes? (Ask except for the galaxy s5 on the at&t network I presume)
Who is using paranoid android on which device and which is it working the best?
Oh, to clarify, I'm looking for a new & best device so far that I can use I the at&t network. I'm now on this new iPhone and I'm having a hard time navigating to find some good reads on relevant information. Which is the best device? And what is paranoid droid, open source for a community of developers?
great2c4me said:
I've been reading up once again, so paranoid android is custom Rom? Is it meant for any particular device, or anything goes? (Ask except for the galaxy s5 on the at&t network I presume)
Who is using paranoid android on which device and which is it working the best?
Click to expand...
Click to collapse
Paranoid Android officially only supports nexus devices.
A custom ROM has to be developed specifically for a device, there isn't a universal ROM that you can download to just any device. You need a build made specifically for your device.
If you want advice about a particular device, you need to go to that devices forum section.
If you want advice about general Android usage, visit the general Android forum section.
This forum section is dedicated to the Paranoid Android project.
Pirateghost said:
Paranoid Android officially only supports nexus devices.
A custom ROM has to be developed specifically for a device, there isn't a universal ROM that you can download to just any device. You need a build made specifically for your device.
If you want advice about a particular device, you need to go to that devices forum section.
If you want advice about general Android usage, visit the general Android forum section.
This forum section is dedicated to the Paranoid Android project.
Click to expand...
Click to collapse
Are you saying that you don't know of an existing forum discussing good better best devices & builds?
In addition, I'm real impresses with galaxy s5 hardware , great camera, processor, expandable memory, good com', terrible that there doesn't seem to be a successful build Fite it on the at&t network
great2c4me said:
Are you saying that you don't know of an existing forum discussing good better best devices & builds?
In addition, I'm real impresses with galaxy s5 hardware , great camera, processor, expandable memory, good com', terrible that there doesn't seem to be a successful build Fite it on the at&t network
Click to expand...
Click to collapse
XDA has how many users across how many forum sections?
I have no idea what's out there. Nonetheless, this discussion doesn't belong in this forum section.
Just thought I'd make a thread about discussing the next version of Lineage OS. Lineage OS 15 is going to be out officially for our Axon 7 soon after the source code for Android 8.0 is released.
Haha how do you know that? I doubt that.
If past experience is any indication, I wouldn't expect it until about November.
Delete
OrdenKrieger said:
Haha how do you know that? I doubt that.
Click to expand...
Click to collapse
Just from common sense - why wouldn't it be? Lineage is officially maintained for our device. It makes a TON of sense that we would get it as soon as the first official nightly builds of lineage OS 15 starts rolling out.
ethanscooter said:
Just from common sense - why wouldn't it be? Lineage is officially maintained for our device. It makes a TON of sense that we would get it as soon as the first official nightly builds of lineage OS 15 starts rolling out.
Click to expand...
Click to collapse
Doesn't mean that there is always some1 to maintain the device.
Edit: BTW I don't think that blogspot pages like http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/ being the best source.
Mod Edit: (non-English comment removed)
请仅用英文发表。谢谢。
Qǐng jǐn yòng yīngwén fābiǎo. Xièxiè.
Please post in English only. Thank you.
ethanscooter said:
Just from common sense - why wouldn't it be? Lineage is officially maintained for our device. It makes a TON of sense that we would get it as soon as the first official nightly builds of lineage OS 15 starts rolling out.
Click to expand...
Click to collapse
I don't think you understand how Android development work.
Google has to release the source (done 8-21)
SOC vendor has to adapt and do the BSP (required for this phone -- last time if they upgrade us to Treble support, but unlikely since we also need drivers for the DAC -- otherwise every release)
ZTE has to get that package and adapt it to our specific hardware devices and port of their UI and internal software
ZTE release the kernel source for the compatible version
Then there is the Lineage side
Lineage devs import AOSP
devs port all of the Lineage code and features over to new base
willing dev(s) take our device kernel source and merge over to Lineage and start doing device bring up and bug fixing
device has to be working fully before it's allowed to be called "official" on Lineage
That's a lot of steps. There is no guarantee ZTE will release the necessary support for us to even get LOS 15. Now, since the HW is similar, we might be able to get it from other devices that do (namely the OP3/3T), but that still leaves lots of issues for our more custom hardware (camera and audio). We will probably have unofficial builds that boot not super far in the future after QC release the 820 BSP, but getting the full hardware up will depend on ZTE doing a release.
This should get vastly easier once a device has Treble support (so O-launching devices and newer and the few that get backported) as long as Lineage also supports that feature.
OEM's are now required to provide support for two full yrs
TeutonJon78 said:
I don't think you understand how Android development work.
Google has to release the source (done 8-21)
SOC vendor has to adapt and do the BSP (required for this phone -- last time if they upgrade us to Treble support, but unlikely since we also need drivers for the DAC -- otherwise every release)
ZTE has to get that package and adapt it to our specific hardware devices and port of their UI and internal software
ZTE release the kernel source for the compatible version
Then there is the Lineage side
Lineage devs import AOSP
devs port all of the Lineage code and features over to new base
willing dev(s) take our device kernel source and merge over to Lineage and start doing device bring up and bug fixing
device has to be working fully before it's allowed to be called "official" on Lineage
That's a lot of steps. There is no guarantee ZTE will release the necessary support for us to even get LOS 15. Now, since the HW is similar, we might be able to get it from other devices that do (namely the OP3/3T), but that still leaves lots of issues for our more custom hardware (camera and audio). We will probably have unofficial builds that boot not super far in the future after QC release the 820 BSP, but getting the full hardware up will depend on ZTE doing a release.
This should get vastly easier once a device has Treble support (so O-launching devices and newer and the few that get backported) as long as Lineage also supports that feature.
Click to expand...
Click to collapse
You are acting like we don't have aosp working at all. LOS 14 is working great and from there its not nearly as much work as you describe to get LOS 15 working. Yes, in the beginning it did take a lot of work but now that aosp is established, its not nearly as difficult.
Jaredsk74 said:
You are acting like we don't have aosp working at all. LOS 14 is working great and from there its not nearly as much work as you describe to get LOS 15 working. Yes, in the beginning it did take a lot of work but now that aosp is established, its not nearly as difficult.
Click to expand...
Click to collapse
It's not about AOSP , you can't build for non Google devices without CAF which hasn't been brought up yet.. It'll be a good month or so
kdp162 said:
OEM's are now required to provide support for two full yrs
Click to expand...
Click to collapse
No they are not, it's optional, there is no incentive for them to do so
TeutonJon78 said:
I don't think you understand how Android development work.
Google has to release the source (done 8-21)
SOC vendor has to adapt and do the BSP (required for this phone -- last time if they upgrade us to Treble support, but unlikely since we also need drivers for the DAC -- otherwise every release)
ZTE has to get that package and adapt it to our specific hardware devices and port of their UI and internal software
ZTE release the kernel source for the compatible version
Then there is the Lineage side
Lineage devs import AOSP
devs port all of the Lineage code and features over to new base
willing dev(s) take our device kernel source and merge over to Lineage and start doing device bring up and bug fixing
device has to be working fully before it's allowed to be called "official" on Lineage
That's a lot of steps. There is no guarantee ZTE will release the necessary support for us to even get LOS 15. Now, since the HW is similar, we might be able to get it from other devices that do (namely the OP3/3T), but that still leaves lots of issues for our more custom hardware (camera and audio). We will probably have unofficial builds that boot not super far in the future after QC release the 820 BSP, but getting the full hardware up will depend on ZTE doing a release.
This should get vastly easier once a device has Treble support (so O-launching devices and newer and the few that get backported) as long as Lineage also supports that feature.
Click to expand...
Click to collapse
How come my Moto G 2013 still gets newest LOS then? Does that mean that Motorola still does the above things? Not questioning you, just wondering.
Jaredsk74 said:
You are acting like we don't have aosp working at all. LOS 14 is working great and from there its not nearly as much work as you describe to get LOS 15 working. Yes, in the beginning it did take a lot of work but now that aosp is established, its not nearly as difficult.
Click to expand...
Click to collapse
You can compile AOSP for just about anything. It's getting ALL the hardware working correctly on a new release that's a problem. Sure, it might boot, but if you don't have audio or accelerated graphics, that's an issue. Once you have a working version from the vendor, then it's a lot simpler than just putting it together before that. And nothing happens if you don't have the drivers from the SoC vendors. That's why Project Treble is such a big deal, because if it works as intended, it will remove the need for those new drivers to get a new version of Android, because the HW abstraction layer will make the older drives work.
Waancho said:
How come my Moto G 2013 still gets newest LOS then? Does that mean that Motorola still does the above things? Not questioning you, just wondering.
Click to expand...
Click to collapse
It could be that Motorola is releasing the drivers/SW updates. It really depends on the underlying hardware. If there is another device with the same hardware getting updated, those drivers can be pulled over and incorporated (the A7 has pulled a lot from the OP3). Or there are open source driver versions that could be pulled in.
Our biggest issue is that the audio chip we have isn't really on any/many other devices. So getting fully working drivers for that is a more limiting factor, than a Moto G 2013, which probably doesn't have anything outside of the standard QC SoC stuff.
And in the end, it comes down to the devs keeping stuff up to date. The Galaxy S2 is still running official LOS 14.1, because there are some crazy ass devs out there still getting stuff working on it. The more popular and easy to work a phone is, the more likely it will see longer 3rd party support. Sadly, the A7 is a little limited in both fronts combined with custom HW bits. The devs have done amazing work so far.
Jaredsk74 said:
You are acting like we don't have aosp working at all. LOS 14 is working great and from there its not nearly as much work as you describe to get LOS 15 working. Yes, in the beginning it did take a lot of work but now that aosp is established, its not nearly as difficult.
Click to expand...
Click to collapse
I disagree that LOS on 14.x works great. I tried various builds and kernels for about 6 months. I dropped back to a rooted stock since the gpu and audio support was awful. I have a much better experience than I had on LOS or RR. I could barely even use my daydream with it.
therock11 said:
I disagree that LOS on 14.x works great. I tried various builds and kernels for about 6 months. I dropped back to a rooted stock since the gpu and audio support was awful. I have a much better experience than I had on LOS or RR. I could barely even use my daydream with it.
Click to expand...
Click to collapse
For gamers and daydream users that could be true.
When it comes to usability, privacy and customizations the LOS based ROMs are the first choice.
The audio issues are just minimal when you combine Dolby Atmos mod with custom rom.
So have you guys taken a look at Ordenkriger's post on the boot up of Lineage 15 with all the progress and what not?
We are getting LOS 15 a.k.a Oreo for our device http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/
Cyberwolf2 said:
We are getting LOS 15 a.k.a Oreo for our device http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/
Click to expand...
Click to collapse
That's not an official source
bkores said:
That's not an official source
Click to expand...
Click to collapse
Ordenkrieger and Unjustified Dev think's otherwise..https://forum.xda-developers.com/axon-7/how-to/oh-lineageos-15-t3668956