Open vczilla opened 1 year ago
@OnePlusOSSAdmin Have a roadmap to realease? Updated source? Waiting Android 14 release? Plz, tell us.
This week when come?
We're looking at a GPL violation at this point.
@OnePlusOSSAdmin ??
@OnePlusOSSAdmin this is becouse i hope Never continue buy oppo/oneplus/realme device after merge oneplus still bad and not listen community
@OnePlusOSSAdmin this is becouse i hope Never continue buy oppo/oneplus/realme device after merge oneplus still bad and not listen community
No more OnePlus phones for sure
The fact is the old and gold OnePlus died a lot of time ago ...
We all fooled by OPPO ...
OPPO used OnePlus name to sell this piece of shit to us 😑 R.I.P. OnePlus
This has been my first and for sure will be the last OPPO phone I'll ever buy. And I'm going to make sure that no one around me buys another phone from this joke of a company.
We could release part of work this week. Here‘s our plan. 1, release build script 2, release tool chain or download link. 3, release manifest
This is joke?
Its been a year...
We could release part of work this week. Here‘s our plan. 1, release build script 2, release tool chain or download link. 3, release manifest
...............
Lo and behold the Android 13 kernel source still doesn't compile. Several different reasons for it: the building system is picking the wrong .config fragments or rather the incomplete ones because some files that are referred to are not there. (build.config.msm.wapio.oplus ( note that waipio was also misspelt) , modules.list.oplus being also conscipcuously absent ). Even what's there wouldn't allow to build the kernel since you end up with a defconfig that lacks both CONFIG_QCOM_SMEM and CONFIG_OPLUS_FEATURE_OPROJECT that will prevent the linking phase to work.
Also talking about project_info the same annoying bugs are still there when it's trying to compile against the QCOM variant: it's using a struct file_operations for the project_info_fops variable instead of using a struct proc_ops and it's also using boot_command_line instead of saved _command_line.
Plus obviously the stock kernel is actually using gki/project_info.c and not qcom/project_info.c even though the last one gets picked up because of a config setting CONFIG_OPLUS_KERNEL_QCOM How difficult would it be to release the source to a fully working kernel ? Answer not whatsoever since Asus was able to do it .