yashsingh1/xdaforums huggingface dataset:
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
With Lineage and DU, because they make lots of changes, they can pull all right /build/core/version_defaults.mk with the latest date for security patches, but when it comes to actual commits, it takes sometimes weeks to manually implement, because of conflicts or build erros. And that's what I was referring to...
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] nathanchance:
With all due respect, you don't know how git works, do you? When you merge, you may merge clean or have conflicts. Fixing conflicts doesn't make the merge less "legit". The end result is still the same. How do you merge updates in?
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
I am not talking about legit or less legit. I am talking about time lapse: you can pull /build/core/version_default.mk fine, but not the others, where you have to go in and resolve conflicts. Last year, for example, I noticed that CM implemented some February security patches as late as May. And some they didn't implement at all, because they broke their other things. And my point was their build.prop read February security patches, but some of them were either not implemented at all or implemented in May...

As far as how I do it: I am not going to have the device read February, unless all February commits are in...

Edit: anyway. Good night, everybody...
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] mosimchah:
It takes hours to implement, not weeks (usually, sometimes it might take a couple days if it's a huge merge like 7.1.2 on 7.1.1, but that's very very rare), these merge conflicts and build errors are only hard to fix if you're a total noob

That's just not true (at least not for du and literally every other ROM)... Show proof
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
Relax. You want me to show you the proof at 12:15 am? I saw Google's February 2016 commits implemented by CM in May, while their version_defaults.mk said February 2016 on February 5-6....

Good night. I'll show you the proof later...
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] phantom-1402:
And the guy is RC *_*

That's so cool
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] anupritaisno1:
Just because you're a recognised contributor doesn't mean whatever comes out of your mind is correct

You are making false claims of other ROMs not merging security patches (and if you actually check gerrit they are doing it just fine) and also showing how great you are by putting others down

Here's why people will agree to what you'll say

Many developers say that lineageOS is **** (it isn't). If you say lineage doesn't merge security patches, people basically will believe you

Fact: lineageOS is properly merging the patches

Du doesn't merge the patches

This is funny. This is exactly the kind of lie I'd see from an expert. What you did was say the lineageOS doesn't merge the security patches. People believe that. You bundle du with lineageOS.

Mentality of the people reading your post: lineageOS and du, lineageOS is ****, many devs say so, this means what you're saying is right and DU also doesn't merge the patches. "I (the user using your ROM) have come to the assumption that DU doesn't merge the patches because lineageOS (apparently) doesn't (while they are actually doing it)"

Basically using lineageOS's bad reputation to spoil it further. Once it's spoiled and people believe you, they'll assume that what you said about du is true

The argument "go ****ing read the code"...

I just love this argument. Basically when you don't want to explain anything to the user you can easily get away with this. It's like showing your openness in development but actually you're not open, not in the slightest. You're just saying so because your users don't know the code (they don't even know what a security patch is) and they'll assume that your recognised contributor title means that you already know what is going on with these big name ROMs and the user trusts you because of this argument. If asked to show proof you'd call me dumb instead of showing proof because you don't have proof. Trust me there is no proof

You are basically trying to put others down to show how good you are when they haven't even done anything wrong and you're getting away with it thanks to how your reply is phrased

---------- Post added at 19:27 ---------- Previous post was at 19:22 ----------

You did a small mistake, fine! Don't ****ing show how others are bad to show how right you are
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
Show me where I called anyone dumb, because they asked for proof. You can search for 24 hours and won't find any example. Now, here is some proof, I didn't have to go far back in the past:

This is DU. Look here: https://github.com/DirtyUnicorns/android_frameworks_base/commits/n7x?after=1975ec222c6ed5bf2c239d3cf4a42ce328641e74+34

This is a DU commit: MountService: Prevent NPE with DropBoxManager. It was implemented on May 27, 2017. Now, we click on it, shall we? https://github.com/DirtyUnicorns/android_frameworks_base/commit/a3a59a5316dd456bb7db36880f88469693b18091 : the original commit was done on November 18, 2015. Now, let's go to May 20, 2017. There is a commit Fix crash by IllegalStateException; click on it https://github.com/DirtyUnicorns/android_frameworks_base/commit/7401ca2b66abc8fb1f3f5e92124c8ec6b9e32531 - the original commit dates back to April 2016.

I have promised and I will show examples of CM implementing security patches several weeks/months later, while their version_defalt.mk was saying the patches were in on original date. That's just gonna take more time.

Now, I may not like Lineage, but DU is one of my favorite roms and the reason I have said they are sometimes late in implementing patches was in response to someone making a joke that I, instead of implementing security patches, just change the date in build.prop. That's false and also dumb, especially when said by people who change a wallpaper, few icons, copy-paste a few commits and call their project a development. Or, when they do a kernel for Lenovo Zuk 2, they pull 100s of useless commits for MIPS devices, which are not even used in Zuk 2, because it is an ARM device.. It just shows that person has no clue what he is doing. However, I never came to his thread and made a post about it. He, on the other hand, came here screaming I was a thief (he was deleted by the moderators) :)

Also, show me a single instance where I would come uninvited to someone's thread and start bad mouthing them or their development. And that's exactly what these 'developers' do...

Cheers...
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] akhilnarang:
Seriously?

How is the commit picked related to merging of security patches late, that commit isn't even merged in AOSP, https://android-review.googlesource.com/#/c/245931/

If you go through DU's repos, they have merged all security patches properly, not manually changing the patch level or anything
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
As I said before, I saw with my own eyes Google February 2016 security patches implemented by CM in May, while their version_default.mk was saying February patches on February 5-6. I will find and post that too.

And by the way, none of pulling/merging/cutting/pasting has anything to do with real programming. CM wanted to take on Google. LOL. Other than their SDK and device trees (which they heavily copy from Google devices or pull from actual devices) is creating. That's why they are where they are today, although, they are clearly the leader in after market development.

This is real programming: https://github.com/CopperheadOS/platform_bionic/commits/nougat-mr2-release

Anyway, this discussion is useless and I am asking everyone uninviated to leave in peace. Asking nicely. :)
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] Surge1223:
lmao bro you so right, can't believe du crew didn't do that. Also given the fact they are time travelers(because you know, their n7x branch was out in 2015) and they still didn't merge that commit....so lame bro

Also damn bro pls tell me how you low key getting thee secret security patches from Google? I might be able to use them to fix those substratum security that you still haven't told me of yet.

But you doing great dev work bro, your github is tight!! :good::good: Those 3 repos with original edits are so lit!

lmao compile warriors with repos on their git with original commits, so lame

get back to me on those subs security flaws tho if you can bro, preferably link me to some code, lll try to compile and understand, Thx sir
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] Myself5:
The amount of false information in this post is amazing. The commits you linked are not merged on AOSP, they were picked by DU in advance. DU merges the latest Android security patches, usually the day they drop. A merge, in case you wouldn't know implements ALL of the commits.

There is not to implement the security patches in a merge. And if you would finally use the common sense that you've proven not to have before, you would see that nobody manually bumped any security version in that file. https://github.com/DirtyUnicorns/android_build/commits/n7x/core/build_id.mk

All bumps were done by the upstream merges. So please. Instead of pissing of people like you usually do, finally start using common sense and stop being paranoid, Leo.

Oh, and if you want to learn about how to merge AOSP upstream to get the latest security commits, check this out https://gist.github.com/Myself5/0222b9edb3e792f05a7369821ca21c90

You appear to really need it, so that things like this don't happen again https://xdaforums.com/showpost.php?p=72700634&postcount=1153
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] luca020400:
You came here posting github links while you barely know how git works.

In these posts you wrote like the author date must match the security bulletin month. that's wrong.

Google is either picking commits from their internal branch or an external branch ( linux kernel ) or commits crafted specifically for this android release, where author date may vary for many factors ( backports for example are usually pretty new, but picks from the internal branch may vary ( a lot ) ).

Merging newer security releases implies using the "git merge" command that preserves the original merge date & commit id from the google release in aosp, so you're saying that google itself is lying, great.

Aside from that, I never seen anyone manually editing the BUILD_ID.

Hope to don't see you soon, Luca.
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
Have I ever come to your thread uninvited with ridiculous statements? No, I haven't. In fact, I supported you a few times, but you didn't even comprehend what I said, until explained. I did critisize Sony, though. Sorry, I didn't know you were an official Sony developer.

Now, what I said in my previous post applies to you too.

Other than providing proof of CM being late a few times in implementing Google security patches, which is relevant here, I am not going to participate in this circus. Enjoy the floor and grow up. I am going to enjoy my Sunday. Cheers...
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] zakaria12:
152k antutu score ????
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] krizto:
Thanks to OP's rude attitude towards other members I'm off from Jaguar for good.
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] Magz Heaven:
Was he? I dont know. I think he isn't rude. He's just trying to explain his side of the story, and he is just also defending his territory and work. That's it.

El Psy Congroo
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] Surge1223:
what official LOS dev whos not just a maintainer on xda? FINALLY. I have so many questions.

1. Who runs the show now, out of curiosity?

2. Can you guys open a thread for general support here? Im tired of answering questions about why cmsdk and devicesettings, cmhw, and cm encryption are needed for most device trees (they're not)

3. Can you not make cmsdk and cmactions into one dependency? Also device tree independent ?

com.cyanogenmod.settings.device

and

org.cyanogenmod.internal.util

share the hierarchy of "com.cyanogenmod" so they can easily be put into one. Right now every device that needs two files from cmsdk in the "com.cyanogenmod.internal.util" package class has to add cmsdk to their dependencies. It would make more sense to create a lib thats seperate from cmsdk that uses just the "com.cyanogenmod" name space.

4. Why did you make dtbtool have to have the CM suffix? And was there a practical reason to move the build dir entirely?

5. Is there a better method/person to contact to ask these questions to without having to go to gerrit? if so can you refer me?

Thanks
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
It would an exellent idea to take this discussion somewhere else...
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] Surge1223:
Sorry, You're absolutely right, I will do that, speaking of which did you ever find which security flaws substratum has that you were referring to earlier? I'd be happy to look into them.
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] anupritaisno1:
I think post 1 was not enough to make you stop. All you're doing right now is

You are now publicly proven wrong

Your users are watching

You're trying to protect yourself

Trust me there is no truth about whatever you said. Stop trying to protect yourself you'll dig your grave deeper

---------- Post added at 10:29 ---------- Previous post was at 10:27 ----------

Could we not just ask for mod help and cut the crap already?
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] Animel:
Everyone get along.:angel: as a user I don't want ROMs getting wrecked by unwanted hate. If you are a good developer and know your stuff show us by helping this device get better. peace.
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
You come here uninvited, spewing hateful nonsense making threats and you are asking ME to stop?! May I suggest that you go back where you came from and stay there. With great respect and cheers. :)
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] anupritaisno1:
With all due respect (I've lost all I had), it's not just me. Neither have you shown definitive proof to back your statement nor have you actually realised your own mistake . I am not the only one here who said you are wrong, several people did

It is useless talking to you. Have fun misleading users
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] faizauthar12:
[MENTION=5842226]anupritaisno1[/MENTION]

You're right, a new corner member got manipulated by optimum word( 1 page behind )

Anyways,XDA is an open forum .. you're welcome to zuk z2 plus :). I hope you enjoy your current trip
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] palgaurav00196:
Anyone tried airdroid with the latest version it is not working for me...or am I doing something wrong?

P.S. wifi/data is working fine after I installed afwall app.
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] zakaria12:
I get this popup while working with this app
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
You have to submit a log to app developer. Also, give him this link:https://stackoverflow.com/questions/20141538/mylib-so-has-text-relocations-this-is-wasting-memory-and-is-a-security-risk-pl

It will help him fix the problem...
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
First, you should ask yourself why anyone should help and give you any input, when you come uninvited to a thread and make jokes about the OP. Not that it matters to me. Also, this topic is clearly irrelevant to the thread purpose, which is development of Jaguar rom. So, take it as a one time exercise.

Here are a few observations:

You might want to check your modified sepolicy, https://github.com/SubstratumResources/platform_system_sepolicy which developers must implement for Substratum to work. Then put it together with Substratum privacy policy: and the picture ain't pretty at all. Although, you guys claim everywhere that the processes Substratum or Themes use are 'sand-boxed', which implies that everything is firewalled and no damage to system or data could be done. However, when one looks at your sepolicy, things are a bit different. You have modified sepolicy to allow virtually device wide read and sometimes write permissions. Let's set aside write permissions and talk about read only. What this means is that Substratum has read access to user's data. And here comes your "clever" privacy policy, as posted on Googleplay: https://www.iubenda.com/privacy-policy/7983041

First, it says that Data Owner and Controller is substratum project teem. Then it goes on to say that Substratum collects "Personal Data: various types of Data as specified in the privacy policy of the service." However, if you want to find out which data is collected, here is what you get: "Types of Data collected The owner does not provide a list of Personal Data types collected." So, according to this privacy policy, nothing prevents Substratum in theory from, let's say, collecting user's private data, such as passwords, login info, credit card info etc. I am NOT saying Substratum does that, but the policy tells the user Substratum is collecting all kinds of private info and they are not telling the user which info. But that's not all. It gets even more interesting: "Users are responsible for any Personal Data of third parties obtained, published or shared through this Application and confirm that they have the third party's consent to provide the Data to the Owner." You know what that means, folks? That means they can grab your contacts. Moreover, according to this policy, you/user, not Substratum, are responsible for getting consent from your contacts. You/user, must warn and get consent from all your contacts listed in the phone that their information could be collected/shared by Substratum. And that applies to ALL your contacts including facebook/what'sup/skype/telegram and whatever else your have on the phone.

This is just a little example. I can go on for hours about it, but you get the gist...
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] zakaria12:
OK thanks
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] Knoth:
I do not understand how you then plan to integrate Substratum into the ROM, [MENTION=5075064]optimumpro[/MENTION] :) It's clear it's crap.
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
Well. This one is easy: I have no plans of integrating substratum... :) Let's wait for Slim's version...
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] asithiou:
I'm loving this ROM so far. I seem to only have one issue after flashing Magisk v12 and installing Magisk Manager. When I open Magisk Manager and go to settings to tick "Enable BusyBox" and "Magisk Hide" then head back to the status screen of Magisk Manager to check SafetyNet it always fails and says "CTS profile mismatch"

If anyone could help me out with this I'd greatly appreciate it. Thank you in advance!
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] sykopompos:
Please do go on.
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
New Safetynet update broke Magisk. But, according to other users, Magisk 12 still works with SafetyNet, if in Magisk/Settings you enable Magisk Core Mode Only...
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] abhimanyu.singh:
Use magisk 13. It will be passing.
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] singhvishvendra:
This is problem of magisk now google updated services ...if you want to pas safty net then use magisk 13 beta file...

Dowload beta flash

Then install it after uninstalling magisk 12

Then try
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] sykopompos:
I'm still waiting for you to go on for hours and try to explain how firebase which is Google allows us to steal users data and not for analytics and crash reports when changes are made so bugs can be tracked down and we just use the permissions required for it.

https://firebase.google.com

I'll let others explain that your assumptions are wrong about sepolicy and it doesn't give blanket read write access to any app.

I get you are trying to support slim but everything with slim is done, over and resolved between teams and we have been working with them with secure assets while having their system go through the Google licensing checks.

A healthy dose of paranoia is ok but rambling on here and g+ when you really haven't done the research on your claims and how they are easily disproven and just completely wrong is not helping you among your peers in the development community
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
Oh. Now I get it: that is why Substratum forces users to certify that people listed in their phone contacts consent to Substratum's collecting their data too. For crash reporting... Got it. Now, if I had any doubt about your creepy data collection policy, you have totally cleared that up. Lol...

Assumptions? No, they are not: "we just use the permissions required for it." I take you for your word on this...

And don't you worry: I don't consider anyone with the above data collection practices and "privacy" policy as my peer.
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] zakaria12:
In every boot I get this
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
Delete it with Titanium or root file manager...
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] zakaria12:
Done!!
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] anupritaisno1:
This is nonsense. Where does substratum have the permission to read contacts?
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] nameless--:
Can someone point me to where is the options to change the battery profiles that are shown on one of the screenshots?

Has it been removed?

Also, there´s no "Zuk extras" tab on settings...

Sorry if I´m asking for something that has already been answered, but on search I could not find anything.

Thanks
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
Didn't you just say the other day it was useless to talk to me? Change of heart?

Well. I trust Substratum team when they tell users they do and they also force users to obtain consent from third parties (phone contacts) for their information to be collected and shared with Substratum. :)

You don't have to trust me, just click the link to Substratum "privacy" policy and read it for yourself...
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] optimumpro:
Yes. They were in Zuk extras and they were removed. They were overriding Android standard battery profile, which is much better. But AKT profiles are available as a separate app. You can get it on XDA....
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] the.D:
I would assume being installed as a system app or explicitly having root permissions (legacy mode) allows for it. Still, I'm not claiming they do read contacts but it's not off limits.
[Lenovo ZUK Z2 (Plus) ROMs, Kernels, Recoveries, & ] simarpreet:
fling/pulse???