[GPL] OOS 4.0 Source Not Released
Closed this issue · 33 comments
This is breaking GPL. It takes minutes to upload the source, which you needed to release the update in the first place.
Please, #NeverSettle.
Do we need this much issues about GPL compliance?
There is already #3 and #26
Let's just tag everybody.
@JayFan1201 @leonfish77101 @brucechiu1113 @aaronqiuchiu @OnePlusOSSAdmin @OnePlusOSS
If I have forgotten someone. Tag them too. Wish I could tag Carl Pei here as well.
I think we do if we and OnePlus want the brand to be known for being developer friendly. It can influence buying decisions for people - yes, not by much - but it can really detract people.
OnePlus want to be developer friendly, so a friendly nudge that they are not is needed. If they can send a 3T out to Sultan, they can release the source code.
The other thread recently put up isn't descriptive, so I thought I'd tag it better.
I'm sure OnePlus is well aware of the GPL. One issue for the same thing is enough. It has only been 2 or 3 days now, and there was a holiday as well. I would like to have it as well but give them a little time especially considering the holiday.
That may be so, and I really do appreciate the short amount of time, but hopefully with a correctly titled issue and short description (and the mentions of developers), they can push the code. Hopefully it'll be this week.
I imagine they are working on the next update after they have tested, but as mentioned, source code pushes take virtually no time.
I already spoke to them on numerous ocasions about this. I also provided a big list of why code must be dropped day 1, why it should be commits based and not a big ass diff stash, the implications etc. Nevertheless they'll only update the source code ~7 days after the OTA has been out. Creating these issues here won't do anything. If you want things changed reach out to their teams and explain the whys. Creating noise like this won't do anything, if else it'll just fuck with them.
Don't forget in the end this is a chinese company, there's no such thing as open source and license compliance in their minds.
😕.....
Nougat is not even released globally look here: http://downloads.oneplus.net you see no OxygenOS 4.0 either.
That's not even an argument. They could have released kernel sources on day 1.
That link isn't up yet for the same reason this isn't up yet: they do the big things first, and the small things later. It hasn't fully rolled out yet, but anyone who would look to download from there would just head over to XDA or the forums.
Methods for upgrading are documented (albeit on a third party website - in any case proceeding with caution is advised): http://www.androidbeat.com/2017/01/how-to-get-android-7-nougat-oneplus-3-3t-right-away/ and OnePlus are already distributing this in their OTA system.
I already answered that. They only release the source when it's released globally. Nothing we can do at this point, and posting here won't change a thing. If you want things changed send them e-mails, nag them on Twitter, their forums, e-mail country managers, community managers, spam Carl and their rom/Kernel team developers. Posting here is a waste of time.
@franciscofranco If you can prepare template message
@GriefNorth uh? why would I possibly do that? Write the message and deal with it yourself like the rest of us.
looks like we will be waiting longer now that the 4.0.1 OTA is rolling out
I believe that OTA is just for developers, is it not? I hear it only fixes a proximity bug and some carrier issues in India.
Either way, you'd hope with a developer release there would be code...
It seems to be official
Does now. Let's leave this thread alone now, it's for development issues.
Unless a Dev responds there's little point causing noise here.
Quote from Carl Pei
M: Right. To be frank, I did find some of the criticisms were valid regarding the colours, the grayscale banding. I didn’t find them too offensive, some people are very picky with colours, but I do feel like the sRGB mode, you guys launched it quick. It was in the review builds and I tested it, and it was like “That’s it. That’s really good crisis management.” Better than certain OEMs lately.
C: It’s “listening to feedback”. And if you look at future products you’ll see that, like… even the developer community, right? It wasn’t that we try to cater to the developer community. It’s just that we listen to a whole bunch of feedback and we also happen to also implement some of the feedback from the dev community and that’s why we have things like zero-day kernel source releases; people want us to do it and we thought about it, “Okay let’s do it. It’s good feedback.” Same with AMOLED, the first thing we said was “Hey, maybe we have missed something when it comes to displays, maybe different people have different preferences when it comes to color saturation and tuning.” So this is just a matter of reacting to feedback, and that’s kind of what the beta program helps us to do in a more structured way.
Ok I snapped on Twitter today: https://twitter.com/franciscof_1990/status/819657428950192132
It's been long enough.
@franciscofranco Lol. You know they stopped the 4.0.1 roll out too? 4.0.2 is supposed to begin next week. They are all kinds of screwed up.
@dustin84 I really don't care about their roll outs or their screw ups. Binary is out, source needs to be out, period. I'm not sure they understand they can be sued by not complying with the GPLv2.
@franciscofranco I agree with you. It should have been out day one. We had marshmallow sources before the phone was in peoples hands. I was just pointing out that since this time they say they are waiting till it's rolled out globally, they will probably keep bull crapping about it.
FYI:
Just now, a company that doesn't mark itself as "developer friendly" released kernel sources of their N beta, 1 day BEFORE official global OTA(Scheduled: Jan. 17th).
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-G935F
Iirc, Oneplus already started N OTA several days before but kernel sources are still not available.
I think a "developer friendly" company should feel shame about this. XD
OnePlus is a joke. License compliance is nil.
I'm still pushing them, hopefully things will change, I'm doing my best.
We definitively need the sources!
@franciscofranco I can imagine that the communication and the "results" are frustrating so far, but keep your work up. They can not ignore us. At least I'll hope so.
For those, you are interested - here is the corresponding topic in the OnPlus-Forum: https://forums.oneplus.net/threads/kernel-sources-for-nougat-oneplus-3t.484531/#post-15627752
Your MM kernel was based off of HB 1.3.2/1.3.1, anyhow I have a HTC10, and it was based off the same source.. when we got N, our source was based off the UM 5.5 C1 Series..........
So chances are, yours will be too..............
@DevriesL That commit made me cringe...
C'mon Oneplus get your act together and just push the sources already!
Is it safe to assume that it will be one commit for both 3 and 3t?
It's up guys
Well done all involved in pushing them.