Please release kernel sources for H.33

[Mr1008]

Hello @OnePlusOSSAdmin Please, can you update and release respective kernel for the latest firmware version H.33? The latest released is for H.26.

Thanks in advance

[RajanPalaniya]

Bump

[RajanPalaniya]

@OnePlusOSSAdmin

[krak3n77]

+1 here as well

[OnePlusOSSAdmin]

The lateset code would be released in about two weeks.

[ghost]

The lateset code would be released in about two weeks.

Thank you!

[Shyleshbare]

The lateset code would be released in about two weeks.

Any updates sur?

[xdevs23]

Where code 🐵

[ghost]

Just wait for it guys 🙏😄

[xdevs23]

If the kernel is available in binary form then you're required to provide the source code according to the GPL.

[N0m4n904]

If the kernel is available in binary form then you're required to provide the source code according to the GPL.

@OnePlusOSSAdmin

[harshparmarx]

If the kernel is available in binary form then you're required to provide the source code according to the GPL.

@OnePlusOSSAdmin

[ghost]

Stop spamming guys. And wait in patience!

[xdevs23]

@lordgregorymsk There's no excuse and no patience. The GPL clearly mandates that source code must be made available. Too much time has elapsed. If OnePlus doesn't release the source code, legal action can be taken against OnePlus by contributors or authors of the Linux kernel.

[N0m4n904]

The lateset code would be released in about two weeks.

@OnePlusOSSAdmin it's been 3 weeks now. Where is the code?

[xdevs23]

[xdevs23]

[harshparmarx]

[ghost]

Stop spamming!

[w311ang]

please release latest H.40

[N0m4n904]

The lateset code would be released in about two weeks.

@OnePlusOSSAdmin it's been 4 weeks now. Where is the code?

[OnePlusOSSAdmin]

Sorry for our delay, update for H.28 is on the way. Please wait for a few days.

[ghost]

Sorry for our delay, update for H.28 is on the way. Please wait for a few days.

Thank you, we are waiting 🙏

[N0m4n904]

Sorry for our delay, update for H.28 is on the way. Please wait for a few days.

H.28? The issue asked for H.33 and we are now at H.40. You are required to make the source code public once you distribute the kernel according to the GPL. Anything other than the source code of H.40 is unacceptable.

[ghost]

Sorry for our delay, update for H.28 is on the way. Please wait for a few days.

H.28? The issue asked for H.33 and we are now at H.40. You are required to make the source code public once you distribute the kernel according to the GPL. Anything other than the source code of H.40 is unacceptable.

I think they mean H38

[N0m4n904]

I think they mean H38

Even then, they do not release the latest code they have distributed via update. The GPL clearly mandates that source code must be made available. To release anything other without releasing H.40 as well is a license violation of the GPL. If they don't release the source code, legal action can be taken against them.

[xdevs23]

In fact, OnePlus has to release all source code for all kernel binaries ever distributed. Users who are running or have run these binaries have the right to receive the source code. Hence all versions need source code, not just one.

[OnePlusOSSAdmin]

Now the released code is for H.26. We're updating code by per version. So it's H.28, then next version till to the latest version.

[ghost]

Now the released code is for H.26. We're updating code by per version. So it's H.28, then next version till to the latest version.

Sooo when code will be updated to the latest version? H40

[N0m4n904]

Now the released code is for H.26. We're updating code by per version. So it's H.28, then next version till to the latest version.

Sooo when code will be updated to the latest version? H40

I hope for their sake that they don't take such long breaks between versions as they have in the past. The longer they wait until the latest code is released, the more likely it is that someone will take action against OnePlus.

[luk1337]

Now the released code is for H.26. We're updating code by per version. So it's H.28, then next version till to the latest version.

Sooo when code will be updated to the latest version? H40

I hope for their sake that they don't take such long breaks between versions as they have in the past. The longer they wait until the latest code is released, the more likely it is that someone will take action against OnePlus.

Have you ever seen someone taking action against Android OEM? Honestly, I think OnePlus could just never update the source and nothing would have happened.

Now the released code is for H.26. We're updating code by per version. So it's H.28, then next version till to the latest version.

Was it really H.26? In https://github.com/OnePlusOSS/android_kernel_modules_and_devicetree_oneplus_sm8150/issues/2 I complained that supposed H.26 code release was missing code that was present in H.26 builds.

[ghost]

Have you ever seen someone taking action against Android OEM? Honestly, I think OnePlus could just never update the source and nothing would have happened.

Agree

[OnePlusOSSAdmin]

@N0m4n904 It's expected to be done in about two weeks. We should pick up the work from where it was interrupted.

[xdevs23]

@luk1337

Have you ever seen someone taking action against Android OEM? Honestly, I think OnePlus could just never update the source and nothing would have happened.

I have reported this to the Software Freedom Conservacy. Someone has to do something. It is clearly a GPL violation which is enforcable by the authors/contributors. And a GPL violation is also a copyright infringement.

[OnePlusOSSAdmin]

Code has been updated for H.40

[N0m4n904]

Code has been updated for H.40

Thanks!

[harshparmarx]

H.41 is still pending...

[ThepuncheXD7]

@OnePlusOSSAdmin Please release kernel for update HD1905_11_F.22 Also I don't see nothing kernel source 7t t-mobile version hd1907_11_f.03 we need that too much

[N0m4n904]

H.41 is still pending...

Isn't that the same as H.40? The changelog is at least the same.

[harshparmarx]

H.41 is still pending...

Isn't that the same as H.40? The changelog is at least the same.

they don't know themselves. improves system stability and performance is their almost always in changelog. but most of the times they get confused and replace the word decline with improve. it's on the user to find it.

in the community post, they mentioned H.32 will be the last build, with their same changelog. this downgrade was realized by them after 2 months, and they released H.36 with same changelog. but their "internal technical reasons" made them to release another "update" with H.38. again the downgrade and same changelog. they keep adding "plus one" in their "last update" then released H.40/H.41, and guess what was the changelog.

because they had to do "never settle" so they made phone so hot, we couldn't sit putting the phone inside pockets. they had increased stability and performance so much that, device always kept running. running out of battery and running out of network, so most custom rom developers had to shift from oos12 firmware base to oos11 firmware. now, bootloader unlocking is not possible on oos12. whereas on oos11, bootloader unlocking while maintaining widevine L1 is possible.

in the past, they had released a "software update" so incredible that hardware replacement was required. an initial ota of oos11 with much changelog was released and that costed me replacement of my phone's motherboard because widevine L1 changed to L3, and motherboard replacement was their only solution.

this all is typed on the same phone which is running oos 10.3.8. and this same phone, was the last phone from oneplus to win an award from mkbhd and all others...