Devs should collaborate.
More choice more consume:d
have you tried teamwork before? it's kinda a hard skill, you know.
Also most of the roms is already made by multiple devs (AEX, Lineage etc...), for our device sources there's also a group (ZUK-DEVS), what are you asking for?
every rom have his own focus, every dev have his own focus, so it doesn't happen
Related
Hi, developers.
I think that maybe we are losing focus on building a stable and nearly all-functional version of android for kaiser.
Everyone of us has a new app, new feature, requiring an all new mod or version to be installed. We are just replicating the millions of flavours of linux.
That means different energies that, in my opinion, could be collate in one or two major version. This is the spirit of open source community and xda community.
Why simply stopping developping hundreds of mods, backgrounds, subversiones, etc. etc. and focalize on making camera working ? And voice search ? The new google voice maps uses it and having it fully working should be awesome.
Thanks for attention. Just my 2 cents, as someone said
TheMac
Myn's Donut is 100% working as far as I know. There are bugs still, but everything works.
The problem with a lot of Android builds is that they focus too much on a customized UI, rather then fixing existing issues and improving stability and performance.
Dukenukemx said:
Myn's Donut is 100% working as far as I know. There are bugs still, but everything works.
The problem with a lot of Android builds is that they focus too much on a customized UI, rather then fixing existing issues and improving stability and performance.
Click to expand...
Click to collapse
its the same as in WIMO dev. builds are easy. you take the tree and add some tweaks or themes or apps.
fixing problems requires work on the kernal and experience. dont complain about current status unless you intend to do something about it. the people releasing builds usually dont dev the kernal. i know i cant do either.
donate money (to dzo) or do some work or quit complaining
BTW if you spend time reading you would know that there are only two major trees. MOST come from cmod 5.0.7 and mmissions work porting them. wyn seems to be using another branch closer connected to his donut work.
Constructive criticism is not the same as criticism. For example, this thread expresses the concern over charging.
There lots of developers who deserve praise and more, and then there's people who like to put Donate buttons in their sig for no good reason. Not pointing out anyone.
Dukenukemx said:
and then there's people who like to put Donate buttons in their sig for no good reason. Not pointing out anyone.
Click to expand...
Click to collapse
id say most people here dont deserve donation, especially me
still fun to hope i guess
The problem with a lot of these popular high maintenance ROM's is that if the Dev's ever get taken away from their work on the ROM at any time, the project can collapse. This seemed to be to me, kind of what happened with AOKP.
What I've suggested in the past and still wondering if it's possible... is to create an app with access to "mount /system..." root privileges etc that is able to add mod's as installable updates/patches? If we had a system like this then all the developers could create mod's instead of an entire ROM and base it off a AOSP, which is technically what all ROM's are based off of anyway.
Then you could install each mod as you wish, just making sure it's compatible with your current firmware/software version.
This would be somewhat of a Cydia approach, the way jailbroken iPhones apply patches to the ROM.
I personally think this is a better idea than having a dedicated Developer OR Set of Developers for each ROM that continually have to be relied upon in order to maintain updates.
Does anybody think I'm speaking any sense here??
AOKP, first off, is very much alive.
Secondly, projects LIKE this exist.
FNV, for example, where everyone is encouraged to push their commits over for review.
There is no "lead developer" and it is the closest you'll get to what you're describing.
As far as just...installing patches and such to get a "flash what you want" type experience...
It isn't that simple.
Even if an open commit is left alone for a few days; it may need rebasing to merge into the branch.
Each little piece of each commit has to build on the previous merges and not interfere with them.
It's a cool thought, bit I can't see it being even slightly plausible.
Jubakuba said:
AOKP, first off, is very much alive.
Secondly, projects LIKE this exist.
FNV, for example, where everyone is encouraged to push their commits over for review.
There is no "lead developer" and it is the closest you'll get to what you're describing.
As far as just...installing patches and such to get a "flash what you want" type experience...
It isn't that simple.
Even if an open commit is left alone for a few days; it may need rebasing to merge into the branch.
Each little piece of each commit has to build on the previous merges and not interfere with them.
It's a cool thought, bit I can't see it being even slightly plausible.
Click to expand...
Click to collapse
Yea I see what you mean, im just wondering how Cydia for iOS interacts with the ROM to apply patches then..?? how have they managed to implement this kind of system?
FNV looks interesting but a little dead. On the other hand, I like how actively updated CM10 is, and it doesn't look like support is going to stop there anytime soon which is a big plus.
UKROB86 said:
The problem with a lot of these popular high maintenance ROM's is that if the Dev's ever get taken away from their work on the ROM at any time, the project can collapse. This seemed to be to me, kind of what happened with AOKP.
What I've suggested in the past and still wondering if it's possible... is to create an app with access to "mount /system..." root privileges etc that is able to add mod's as installable updates/patches? If we had a system like this then all the developers could create mod's instead of an entire ROM and base it off a AOSP, which is technically what all ROM's are based off of anyway.
Then you could install each mod as you wish, just making sure it's compatible with your current firmware/software version.
This would be somewhat of a Cydia approach, the way jailbroken iPhones apply patches to the ROM.
I personally think this is a better idea than having a dedicated Developer OR Set of Developers for each ROM that continually have to be relied upon in order to maintain updates.
Does anybody think I'm speaking any sense here??
Click to expand...
Click to collapse
Remember, the performance of a jail broken iPhone once you install those tweaks, let's just say, all hell breaks loose. My friends who jailbreak and use the simplest of jailbreak scripts and stuff all complain of lag on their iPad 2/3. I personally think its a hack job.
We have the source code unlike iOS, in the spirit of open source, developers download the source, make modifications, compile and make ROMs. They also give out the source to the public again so if anyone wants to base off any existing work, its okay. A great example is cm and perhaps Paranoid Android. And this method is flawed as other devices don't have AOSP support. I'm talking about S2/S3/HTC One X, etc. How are we supposed to make a single stable rom for them that's a clean aosp rom? Usually lots of hacking and tinkering and waiting for kernel sources is required to get AOSP on those devices. Its unlike the nexus where we have everything (source, proprietary drivers, etc) straight from Google. Anyway, that's my view. From the practical standpoint, you have to talk with other developers as ROMs come with their own framework and things.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------
And another note, have a problem with a dead rom? Its probably stable enough for the developer. Or the developer has other important things in life. You can't blame them. What you can do is switch your ROM easily. If your looking for AOKP like ROMs, there's slimbean, CNA and Sourcery and even more that cram in all the tweaks. If you want a clean and minimal ROM, fast and stable, there are roms like Minco and rasbean jelly. Its seriously a different ecosystem than the apple cydia stuff, but it isn't a bad thing.
Sent from my Galaxy Nexus using Tapatalk 2
akash3656 said:
Remember, the performance of a jail broken iPhone once you install those tweaks, let's just say, all hell breaks loose. My friends who jailbreak and use the simplest of jailbreak scripts and stuff all complain of lag on their iPad 2/3. I personally think its a hack job.
We have the source code unlike iOS, in the spirit of open source, developers download the source, make modifications, compile and make ROMs. They also give out the source to the public again so if anyone wants to base off any existing work, its okay. A great example is cm and perhaps Paranoid Android. And this method is flawed as other devices don't have AOSP support. I'm talking about S2/S3/HTC One X, etc. How are we supposed to make a single stable rom for them that's a clean aosp rom? Usually lots of hacking and tinkering and waiting for kernel sources is required to get AOSP on those devices. Its unlike the nexus where we have everything (source, proprietary drivers, etc) straight from Google. Anyway, that's my view. From the practical standpoint, you have to talk with other developers as ROMs come with their own framework and things.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 01:31 PM ---------- Previous post was at 01:27 PM ----------
And another note, have a problem with a dead rom? Its probably stable enough for the developer. Or the developer has other important things in life. You can't blame them. What you can do is switch your ROM easily. If your looking for AOKP like ROMs, there's slimbean, CNA and Sourcery and even more that cram in all the tweaks. If you want a clean and minimal ROM, fast and stable, there are roms like Minco and rasbean jelly. Its seriously a different ecosystem than the apple cydia stuff, but it isn't a bad thing.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yea I get what your saying.
Im not complaining about dead ROMs just was trying to think if there was a workaround. But yes I see your point about how a ROM developed from source would be less likely to lag.
I've been on CNA for awhile now, since AOKP slowed right now, and CNA is amazing. I guess CM10 is always a good backup if any of these ROM's stop updates.
thanks anyways.
Dont worry, you'll get your precious roms - this is an aosp device, after all.
Sent from my i9250
Hi Guys,
First of all I must appreciate of all developers who work on Gnexus.
I have a main question and this is: Why no one (of developers) try to complete his/her project?
I mean most of them decided to get right of his/her Rom while there are some f.. bugs in these Roms, especially about 5.1.1 for Gnexus. I know that our Gnexus maybe has low ram, weak CPU or ... but there are a lot of developer in XDA who work on older phone than ours and are successful to make or cook a bugless Rom. You can easily look around.
I think either our developer couldn't Fix main bugs or it is not worth to Fix them for people that are waiting to use their creation and enjoy 5.1.1 or 6 Android.
I hope someday someone appears and solve all of bugs in this phone.
Unfortunately I have no knowledge to develop a Rom.
So I have unlocked bootloader and really enjoy being able to flash CM The only thing which is missing is the availabilty of custom kernels for CM 13. SuperExe Kernel is only in testing phase and I don't know whether it will be developped further, and I'm not sure about GoogyMax Kernel in this case, too. The only really "active" kernel is Llama Sweet. My wish is to have another, batteryfriendly, fully customizable kernel, which supports many governors, undervolting, hotplugging and so on and so on.
I really would like to develop it by myself, but I read the doc about kernel building and just realized that I don't really have an idea about this
So I just wanted to ask if:
-there would be any interest in having another, new kernel for the G4, based on CM/AOSP
-anyone has the time and the interest to help me/to build a new kernel.
I hope this sounds not too crazy or too demanding, it's only a request and furthermore, I want to excuse my limited English
Thanks in advance for many views and perhaps some interested people/replies, hopefully.
Noone?
As you can see, many of us read your thread, but the problem is that you can't simply tell "Let's build another Kernel". This requires time,patience and a lot of knowledge in building it, as you said ("but I read the doc about kernel building and just realized that I don't really have an idea about this" ). You see, there are only 3 options : Support the actual kernels,the developers like @codeworkx and @genesixxbf3 and so on(SuperEXE,Googy,Imeperium and so on so on) knew what our device really need (btw, Llama Sweet kernel is going R5 and there will be lots of improvements!) (the best one in my opinion),hope that other kernels will come or will be updated with what you need or start building one, which is the hardest one. You can ask some developers to help you ( I can help you too, but I'm noob at building kernels),but remember, it takes time and a lot of effort! Hope that I answer to your question, see you
azZA_09 said:
As you can see, many of us read your thread, but the problem is that you can't simply tell "Let's build another Kernel". This requires time,patience and a lot of knowledge in building it, as you said ("but I read the doc about kernel building and just realized that I don't really have an idea about this" ). You see, there are only 3 options : Support the actual kernels,the developers like @codeworkx and @genesixxbf3 and so on(SuperEXE,Googy,Imeperium and so on so on) knew what our device really need (btw, Llama Sweet kernel is going R5 and there will be lots of improvements!) (the best one in my opinion),hope that other kernels will come or will be updated with what you need or start building one, which is the hardest one. You can ask some developers to help you ( I can help you too, but I'm noob at building kernels),but remember, it takes time and a lot of effort! Hope that I answer to your question, see you
Click to expand...
Click to collapse
Thank you for your kind answer! Yeah it's right, Llama Sweet will get an update and I'm looking forward to it! SuperEXE is dead, the developer said he is on iOS right now. And GoogyMax didn't receive an update for a long time and it hasn't additional governors when I'm right. And yeah that's my problem too, I would know what the kernel should be able to, but I have no knowledge in building. Perhaps any developer will have time in the future : [fingers crossed)
Day by day Mi A2 lite Rom developers stop releasing newer versions of their Rom. Only Few Developer still show their love for this device. Thanks to them. We appreciate their work.
You do realize people work on project for this phone in their own free time right? You don't need access to every single rom a youtuber decided to show off on his poco or what ever else is trendy to flash bull**** on right now.
The community should be happy that people like Linkboi and Giovanni still work on this device because they are the one's doing the majority of the hard work and bug fixes right now.