If you don't want credit, why do you bother to share your roms with the public? If you find it surprizing that no one asks for help publicly, then you need to take a step back and remind yourself of the obvious: 99% of users don't know and don't care where builds come from, they think they come from outer space or the centre of the earth. I build from whosever repos work at that particular time. As I've told you already, my nougat builds were 100% official repos because only those were able to compile. If you don't want users to wait patiently for your builds, how the hell do you expect to get feedback? This is how the cycle works: you build, we give feedback, you update your repos, and build again.widevine L1 support added. we dont need patched netflix apks anymore
@ripee I make roms for myself and share them with others. What's wrong with that? And yes, I'm helpful and generous when you write me pm. Just curious, nobody asked for help in public. And yes, everything is depends on my spare time.
Nougat builds are really abandoned. You don't believe me or what? Or I should to write anything else there when people ask for update builds?
I see you worry about my git. Calm down, please. Why do you think I upload sources for you? I uploaded sources for you and you published your builds just right after that without understanding what exactly changed and instead of help to fix remain bugs. I told you few months ago to choose one author and try to fix something. You didn't hear me. I don't need any credits. But I don't like liars, if we talk about one person here. And I don't want more "we don't care" teams here. I don't need any daily public builds. It will be disorganized development. At least no one else haven't tried to fix anything in my (nougat) sources...
So, in short, I will do what I want. I will upload builds when I want. I will add/fix/change in builds what I want and in my own priority. I spend my own time for that. Don't like? Don't use. Make something yourself. Stop depend from me and let me do my work. Thanks in advance.
You may not need daily builds, but at this early stage of Oreo development, having irregular builds is more disorganized than regular builds because with regular builds users can keep track of how your gts2 commits go together with community commits in the non-gts2 repos. If you ask me not to share my builds publicly, I won't.
In short, your repos aren't 100% reliable since you take forever to update them. I get that you're busy, but why not push your updated commits right when you start a new build? Even when I give you good feedback you still take forever to make a change: how long ago have I told you about taking this line out of the gts210wifi vendor repo, which you acknowledged as good feedback because it's necessary for compilation to progress properly, yet we're still waiting for you to update your repo!
If you choose to release your repos publicly, then you have to expect the whole world will depend on them. If you don't want to keep them updated, you may as well not share them at all, since outdated repos are as useful as outdated antivirus definitions.
I get that you want me to make my own threads so that users don't bother you with feedback from my builds, but if I make it clear to everyone that I use your repos, then the feedback is directly useful to you going forward. If you don't want too much feedback too often, ask users to post it in the thread not pm. At this early stage, we all just want the basic functions to work. The deep down stuff can wait.
It's hard enough to learn how to fix these bugs myself, but going between qualcomm devices and exynos makes it that much harder. If I knew how to improve upon your repos, I would have take the time to do so myself already, rest assured. I feel proud of myself as it is to have deduced the rotation bug being fixed by a simple change from 270 to 90.
