Hi Everyone,
I wanna ask my fellow Zenfone MPM1 users, what they think about current development on our device. With so many Roms indeed there are different options and it may seem ( Few devs have done a tremendous job on this device ) that development is going in the right direction. But really it is enough?
Before sharing my views on development direction I like to thanks for all those authors for big/little mods and those who invested time in this device and generous enough to share their work to our community.
I am a really old Xda user registered in 2009 with this id and but following Xda even before ( when it was famous for windows device), so keep this in mind before becoming judgmental on my thoughts ( Take me as an old guy) I totally respect all the work shared on this platform.
In old time (When Android developers started to share their work on this forum ), we in that time had few primary goals for development like having a properly supported CWM Recovery (obsolete now), having fully working AOSP and of-course having fully working, officially supported CyanogenMod( CM7 is still my best Rom I have ever used on any device at the given time ).
Things changed CWM replaced by TWRP as recovery of choice, Cyanogen becomes dead and LineageOS born... BOOM Today.
So why I am sharing this?
Because I want to highlight a few missing things( take it as a pinch of salt ) in current development equation, not a long list so stay with me.
OFFICIAL TWRP: Current latest TWRP which is working almost, but it still has few issues like sideloading didn't work and no decryption support. A fully working custom recovery is a necessity for any Rom development. We have an UNOFFICIAL TWRP thread which is dead right now, so I don't know what are the hopes for official TWRP.
PURE AOSP: Not tested Pure AOSP love yet on this device, I know everybody wants feature filled Rom with hundreds of features, but a pure working AOSP is really important. It is helpful for beginners devs who can create their own spin of custom roms with (few or more)cherry-pick features on top of AOSP. I am not saying that gives me AOSP right now but I miss the thing that a developer is constantly working on an AOSP base to fix small and big issues in device tree and framework.
ESSENTIAL ROMS: We have so many custom roms and I love to see that, we also have an OFFICIAL LineageOS 15.1 ROM but no major rom of next cycle ( Android Pie) LineageOS 16 or OMNI ROM in development ( unofficial or official doesn't matter as long as it is in development). These are the basic roms with a distinctive set of features and everyone knows that almost every other rom use source of these roms. So stable essential roms are necessary for a bugless custom spinoff of these roms. I don't see any of this in current time, as devs started projects and abandon them quickly either to work on another rom or their schedule doesn't allow to work on that rom anymore. There are few instances that few users spam those threads for the unnecessary feature request, ETA, improper language and this may have discouraged devs to work on those roms anymore.
BUGS Handling: There is nothing perfect and everyone knows that but I really miss that major bugs are not mentioned on many ROM's intro post, they all seem copy pasted that everything works but in reality, not everything works. I understand that features availability do differ on a different device, few common features may never work, every device has bugs common in every rom and can never be fixed. I understand that there is no point to mention those things, but there are issues which are constantly discussed in threads but have no mention on the original post. I am not saying that everyone should do it right now or it is really necessary, but I am sure will certainly help for many folks.
That's it folk those are things I have in my mind. But I really want to know others take on this, What you have to say on my points. You can also throw the above points in the trash if you want and share yours.
NOTE: Above points are not demands but are few pointers for our community to think on, which I think would be helpful for everybody. You have every right to discard those points or correct me If I am wrong.
Same feeling here..!
Yes,.. well said,
Need support for Official TWRP. need adb sideload feature.
Please developers and maintainers, consider lineage 16.0 and omni rom, these two are major famous os distro, but not maintained for our device.
All the points are true and devs should at least try to fix the recovery. I remember once my old device had a problem with Cwm when reboot to recovery was performed the phone bootlooped so a stable recovery is a basic need for development.
Also now a days devs seem to make telegram groups and post their work there by giving reason that xda has a lot of rules, the rules are for everyone's good and if you find a rule which should be changed or modified ask the community they'll help.
On xda devs get to show their skills in front of an open audience instead of a closed group. It's like driving on a empty track vs driving in a formula league. The league has more rules than no rules empty track but one can outshine only in a league.
So try to support the xda community and also have great time. Happy developing.
navjottomer said:
Hi Everyone,
I wanna ask my fellow Zenfone MPM1 users, what they think about current development on our device. With so many Roms indeed there are different options and it may seem ( Few devs have done a tremendous job on this device ) that development is going in the right direction. But really it is enough?
Before sharing my views on development direction I like to thanks for all those authors for big/little mods and those who invested time in this device and generous enough to share their work to our community.
I am a really old Xda user registered in 2009 with this id and but following Xda even before ( when it was famous for windows device), so keep this in mind before becoming judgmental on my thoughts ( Take me as an old guy) I totally respect all the work shared on this platform.
In old time (When Android developers started to share their work on this forum ), we in that time had few primary goals for development like having a properly supported CWM Recovery (obsolete now), having fully working AOSP and of-course having fully working, officially supported CyanogenMod( CM7 is still my best Rom I have ever used on any device at the given time ).
Things changed CWM replaced by TWRP as recovery of choice, Cyanogen becomes dead and LineageOS born... BOOM Today.
So why I am sharing this?
Because I want to highlight a few missing things( take it as a pinch of salt ) in current development equation, not a long list so stay with me.
OFFICIAL TWRP: Current latest TWRP which is working almost, but it still has few issues like sideloading didn't work and no decryption support. A fully working custom recovery is a necessity for any Rom development. We have an UNOFFICIAL TWRP thread which is dead right now, so I don't know what are the hopes for official TWRP.
PURE AOSP: Not tested Pure AOSP love yet on this device, I know everybody wants feature filled Rom with hundreds of features, but a pure working AOSP is really important. It is helpful for beginners devs who can create their own spin of custom roms with (few or more)cherry-pick features on top of AOSP. I am not saying that gives me AOSP right now but I miss the thing that a developer is constantly working on an AOSP base to fix small and big issues in device tree and framework.
ESSENTIAL ROMS: We have so many custom roms and I love to see that, we also have an OFFICIAL LineageOS 15.1 ROM but no major rom of next cycle ( Android Pie) LineageOS 16 or OMNI ROM in development ( unofficial or official doesn't matter as long as it is in development). These are the basic roms with a distinctive set of features and everyone knows that almost every other rom use source of these roms. So stable essential roms are necessary for a bugless custom spinoff of these roms. I don't see any of this in current time, as devs started projects and abandon them quickly either to work on another rom or their schedule doesn't allow to work on that rom anymore. There are few instances that few users spam those threads for the unnecessary feature request, ETA, improper language and this may have discouraged devs to work on those roms anymore.
BUGS Handling: There is nothing perfect and everyone knows that but I really miss that major bugs are not mentioned on many ROM's intro post, they all seem copy pasted that everything works but in reality, not everything works. I understand that features availability do differ on a different device, few common features may never work, every device has bugs common in every rom and can never be fixed. I understand that there is no point to mention those things, but there are issues which are constantly discussed in threads but have no mention on the original post. I am not saying that everyone should do it right now or it is really necessary, but I am sure will certainly help for many folks.
That's it folk those are things I have in my mind. But I really want to know others take on this, What you have to say on my points. You can also throw the above points in the trash if you want and share yours.
NOTE: Above points are not demands but are few pointers for our community to think on, which I think would be helpful for everybody. You have every right to discard those points or correct me If I am wrong.
Click to expand...
Click to collapse
Very thoughtful! Resonate the same things brother.
Most annoying - 'Bugs - you tell me' when they are crawling around about to eat your eyes out!!
Oh and the spammers - next level entitlement for free stuff.
Note - Same as OP and with all due to respect to devs/contributors.
Can we request the developer community to focus on quality and not on quantity, found more than 20 roms, but not one which can maybe support OTA and be used as a daily driver for non flashoholic community?
Ie flash once (or dirty flash forever) and forget type of use cases, we had during resurrection remix days.
Other than that I completely agree with the opening comment of the thread.
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
Due to the insane quantity we find similar bugs on different roms, that's kinda futile..
Not one is working on lineage 16 i absolutely don't understand why.
I just bought a new ZF MPM1 and roaming around the forms ,i feel like you are absolutely right!
navjottomer said:
Hi Everyone,
I wanna ask my fellow Zenfone MPM1 users, what they think about current development on our device. With so many Roms indeed there are different options and it may seem ( Few devs have done a tremendous job on this device ) that development is going in the right direction. But really it is enough?
Before sharing my views on development direction I like to thanks for all those authors for big/little mods and those who invested time in this device and generous enough to share their work to our community.
I am a really old Xda user registered in 2009 with this id and but following Xda even before ( when it was famous for windows device), so keep this in mind before becoming judgmental on my thoughts ( Take me as an old guy) I totally respect all the work shared on this platform.
In old time (When Android developers started to share their work on this forum ), we in that time had few primary goals for development like having a properly supported CWM Recovery (obsolete now), having fully working AOSP and of-course having fully working, officially supported CyanogenMod( CM7 is still my best Rom I have ever used on any device at the given time ).
Things changed CWM replaced by TWRP as recovery of choice, Cyanogen becomes dead and LineageOS born... BOOM Today.
So why I am sharing this?
Because I want to highlight a few missing things( take it as a pinch of salt ) in current development equation, not a long list so stay with me.
OFFICIAL TWRP: Current latest TWRP which is working almost, but it still has few issues like sideloading didn't work and no decryption support. A fully working custom recovery is a necessity for any Rom development. We have an UNOFFICIAL TWRP thread which is dead right now, so I don't know what are the hopes for official TWRP.
PURE AOSP: Not tested Pure AOSP love yet on this device, I know everybody wants feature filled Rom with hundreds of features, but a pure working AOSP is really important. It is helpful for beginners devs who can create their own spin of custom roms with (few or more)cherry-pick features on top of AOSP. I am not saying that gives me AOSP right now but I miss the thing that a developer is constantly working on an AOSP base to fix small and big issues in device tree and framework.
ESSENTIAL ROMS: We have so many custom roms and I love to see that, we also have an OFFICIAL LineageOS 15.1 ROM but no major rom of next cycle ( Android Pie) LineageOS 16 or OMNI ROM in development ( unofficial or official doesn't matter as long as it is in development). These are the basic roms with a distinctive set of features and everyone knows that almost every other rom use source of these roms. So stable essential roms are necessary for a bugless custom spinoff of these roms. I don't see any of this in current time, as devs started projects and abandon them quickly either to work on another rom or their schedule doesn't allow to work on that rom anymore. There are few instances that few users spam those threads for the unnecessary feature request, ETA, improper language and this may have discouraged devs to work on those roms anymore.
BUGS Handling: There is nothing perfect and everyone knows that but I really miss that major bugs are not mentioned on many ROM's intro post, they all seem copy pasted that everything works but in reality, not everything works. I understand that features availability do differ on a different device, few common features may never work, every device has bugs common in every rom and can never be fixed. I understand that there is no point to mention those things, but there are issues which are constantly discussed in threads but have no mention on the original post. I am not saying that everyone should do it right now or it is really necessary, but I am sure will certainly help for many folks.
That's it folk those are things I have in my mind. But I really want to know others take on this, What you have to say on my points. You can also throw the above points in the trash if you want and share yours.
NOTE: Above points are not demands but are few pointers for our community to think on, which I think would be helpful for everybody. You have every right to discard those points or correct me If I am wrong.
Click to expand...
Click to collapse
bro...devs are also humen, they also have life...
they are doing what u cant do..
building a rom take about 10-12 hrs ( if not using gclouds), with gclouds 3-4 hrs(if less error occurred).
they are developing when they get free time.
give them time, not a big thread to read.
And it will be great if you provide them LOGCATS, so that they can look and fix those bugs.
saurabh1234 said:
bro...devs are also humen, they also have life...
they are doing what u cant do..
building a rom take about 10-12 hrs ( if not using gclouds), with gclouds 3-4 hrs(if less error occurred).
they are developing when they get free time.
give them time, not a big thread to read.
And it will be great if you provide them LOGCATS, so that they can look and fix those bugs.
Click to expand...
Click to collapse
first of all i thank my dear X00TD's ROM developers for the quick and active development.,
Bro,
we are not pesking developers to add this thing and that thing. we are requesting necessary thing that needed for stable development. every month we are getting new rom project or port rom. but nothing is different.
I am custom rom user since samsung galaxy pop( galaxy mini). previously every community build the cwm recovery (project closed) and make it stable and make it compatible with all the roms. and parallely start developing CyanogenMod (now lineage). then otherr rom developers are uses cyanogenmods sources to build their own custom rom.
firstly,
stable recovery needed. our twrp is still in beta stage.
and still in unofficial release. the following problems i faced, adb sideload, otg support not stable, aroma also not working.
secondly,
lineage os is traditional one and best aftermarket os. and the root for the many custom roms. but we are not concentrating on this os.
nxp amplifier not yet fully supported for current release of pie custom roms. i dont know what is the problem behind this issue. but none of the thread mentioned about it. may be asus not released source for it(idk).
anyone can build rom and fix bugs and release here. sorry to say, most of us don't know this android custom rom development.
and telegram groups are not worth. mostly some guys talking off topics. and i mostly ignore if unread msg is more than 500( mostly it goes above 1000 per day). so i miss what developers told and published news.
anyone,
please make a thread to how to take a logs, because most of us dont know how to take logs.
please make a index thread for list roms and kernel and about their present bugs, last release, current development status.
please make a single thread for noob guide/new user, and mention all the common problems and its solutions,
please make a thread for common bugs in roms and kernels and talk there for what we need to do solve this bugs.
if possible, update possible reason for the bugs
sorry i dont know english much. ya i know did more grammer mistakes.
i'm really sorry if i hurt anyone.
#OnlyRequesting
#NotDemanding
What else can you expect? Phone has been marketed as a mid-to lower middle tier device (price <$200/€180) i.e. it will not attract big (known / reputed) devs. phone was released in few countries so lower economic tier ppl in these countries will flock to this phone....natural to expect slovenly behaviour, rude attitudes in the community and lack of stability and direction of growth for the phone's rom development, since these ppl (students, mostly) have little knowledge of ethics, professionalism, and are likely to throw the device away for the next shiny fondleslab in the same price range within a year. Some devs are there, but the general populace they pander to is reckless, raging, mercurial youth with little respect for their work and little concern/care for whom they offend, so they can't stick to these guidelines as you speak of....after all they too hold some other work/profession as their main job and rom development is just an after-work thing....
Eat whats on table coz you aint paying ****.
I agree with what you said.
I've been longing for a stable Pie LineageOS or stable AOSP for months. But so far it's been no news.
well, it can't be helped
My actual plan was to just use the stock rom (since it was pure aosp, kinda), but since the pie version still buggy I have to use the custom version, which is pretty meh than my previous devices (xiaomi)
Related
Hi all,
I really appreciate the work of all ROM cookers, even if I don't use a ROM from XDA anymore. (I was using some german releases here for quite some time)
I don't know much about ROM cooking, since I'm a SAP and Web-Deveopment guy, but I always asking myself:
Why is ROM cooking not like open source stuff?
Why is everyone/every group cooking it's own little stuff?
Why not working together on few versions to provide a ultimate, stable, bugfree, nice documented and "perfect" ROM?
Newbies are totally overloaded with 1337 ROM releases, which they should take? Where to find help for your decision? Not everyone has the time/KnowHow to try out 5+ ROMs...
There are so many many advantages if they would do so:
+ bugfixes are done only one time, not many times for many different roms
+ bugfixes are always up to date
+ mistakes are not done multiple times
+ more manpower to test/optimize/develop roms (since everyone works together)
+ clean and clear buglist and release history
+ bugtracking (easier for community to post bugs via bugtracker, easier to develop for cookers)
+ better for newbies (a stronger/bigger community is maybe not a bad thing?) - people know what to download (stable/beta/nightly builds releases - maybe light and full ROMs)
+ many many more, maybe even better reasons
And you can still release ROMs weekly and in multiple version (nightly builds, betas, alphas) but you also can make rock solid milestone releases for the community.
My feeling is SOMETIMES (not in all cases!), that cookers try to compete against each other, than working together.
As I said, its just a feeling... nothing personal against anyone.
Of course there are also disadvantages in organizing such a "structure", but in the end if a cooker would stop developing and invest this time into organizing the rest in to a developer group, that would be a benefit everyone. Means, a bit less "development power", but a lot more efficient developing. The big picture counts.
Just wanted to start a discussion about this thing. It is not like I'm totally experienced in this topic.
Because to be honest... much of the work (which is great and I really appreciate) is done multiple multiple times.
And many many ROMs are more or less the same. Different languages and "feature" levels like Light/Full would be sufficient.
It does seem like a good idea. Certainly, it would allow the chefs to develop an amazing Manilla X1 ROM, and a non-Manilla ROM, 6.1 ROM and a 6.5 ROM, light/full versions and other languages quite effectively. However, I'm not sure how much the chefs would like it. It would however, be excellent for the community. Would be interesting to hear the chefs views on this.
rom are developed really fast. too much people, too much organizations will slow down development.
most part of developers has trusted betatester and bug solver, working in small groups. afaik, looking at whole forum productions, this model works pretty well
yes I have the same question
if we all put our knowledge / findings together @ the cheffs share centre thread it would be A high mile achievement
guap said:
rom are developed really fast. too much people, too much organizations will slow down development.
most part of developers has trusted betatester and bug solver, working in small groups. afaik, looking at whole forum productions, this model works pretty well
Click to expand...
Click to collapse
I'm not too sure if you can call this situation "well". I would say it "kinda works".
And yes, in the short run, the development is slower, but in the long run the development is faster, because it is more efficient and there is less work which is done multiple times. As I said, it is the big picture you have to see, in the long run this would be much better.
Additionally to that "new" cooks who maybe have a new bugfix and want to release that, they have to do many of the other fixes again to release a new ROM (additionally to that they lack experience and will make "new" bugs).
In a single project, they simply post their fix, and the main developers check and integrate the fix ... done. Next build it is included.
And that's much faster!! And it is double checked for mistakes for more stable releases.
---
For the user it is unthinkable to update the ROM every week. There is a need for some "stable"-like ROM for general users.
The level of final release ROMs here are more or less like "Firefox RC" or even "Beta" Versions.
this is not the 1st time someone like u come up with this......loads of ppl had the same request. even i saw atleast a couple of such thread in this x1 thread!!!
but they neva work in most cases.....i only saw one such successful project!!!
That's not a bad idea at all.
I have been active for sometime with XDA equivalent for AVM Fritz modems (ip-phone-forum), together they made a compiler tool (Freetz.org) for all avm fritz modems, users download one tool, launch and select what features they want in their router, and build a new firmware/ROM, and there is a huge forum for support.
well, i don't say to make such a tool (while it will be so interesting to have, at least one per smartphone model)
having a xda organized in the way mentioned, many bugs can be resolved easily.
in the current state, a newbie will have much difficulty to read a 200 page thread about some custom ROM to find that in post 1232 describes the issue he encountered and later has been fixed in post 1325....
i was going to ask about making a sub forum per each custom rom, with threads divided per subjects, so if someone encounter an SMS issue will have to read one thread completely about sms issues rather than a very long one about all issues in that custom rom.....
if something could be done, then it will become much easier for everybody !!!
great idea.
There is one issue though: people have strong personal flavors of ROMs. Some might want a fast and lean ROM while others might want a mighty one.
I guess some kind of sophisticated branching is needed to accommodate these requests
yes, different tastes, but same bugs
I am down on a common knowledge database, willing to share and learn
It would be great indeed to have a common project but all chefs would need to aim to the same release that would take time to come to a common design and implementation.
Hope this can happen though!
Maybe a cooperation of some chefs would help to reach something here.
mercuriussan said:
And yes, in the short run, the development is slower, but in the long run the development is faster, because it is more efficient and there is less work which is done multiple times. As I said, it is the big picture you have to see, in the long run this would be much better.
Click to expand...
Click to collapse
The problem is there is no long run for rom cooking.
Most of us (users or cook) seldom use a single phone longer than a year and we moved to a next device and start everything from the ground up again.
Even you keep the same device for a long time, newer WM build or other components comes very frequently and there's always a tradeoff between "new features" vs "stability". And every cook has their own perference and it natural to see varies roms among cooks. Therefore, it will never have an easy solution for rom user.
For cooks, we could open threads for individual components and work together. I did open a threads for TF3D v2 (landscape), and HD Camera as a project base, and Itje already create a chef discussion thread and I think this model works pretty well for cooks.
agree with jackleung in some points
I've created a Topic for cooking with windows mobile 6.5, too.
Everyone was invited to discuss their bugs and help each other.
But none like it really.
Or none got bugs
Basically what everyone wants is a ROM with PURE Windows Mobile as Microsoft gives it to manufacturers(No HTC, Sonyericsson stuff), cabs/packages of different applications and a program that combines all of them together according to individual needs.
Hi,
Firstly, I don't want to sound unrespectful to developers. It is just a few complains but I admire the time each one spend for creating new roms. There are lots, lots of roms/kernels in the android development section. It's a complete jungle! For a non technical user, I find it really difficult to choose a rom because:
There are no standard table stating what is different with the other. The list described by each developer is not always clear. Especially when he or she sees "aroma", "CRT", "ram hack", "zipalign" without explication. Wouldn't one nice and small sentence be sufficient to explain these terms?
The issues for each rom are not tracked. I think there should be a tracking system like JIRA so that we can confirm if a bug is already described and if it is still present in future release.
It should be clear if a rom is based from stock or AOSP rom (edit: it's not always obvious).
There is no centralized topic explaining the differences. But I have seen there is topic listing roms.
To my mind, there should be in each rom description something like a history, a short sentence like "I have based this rom on this other rom because I feel it lacks this and that." (not always the case), instead of just throwing "hi, [screenshot], how to install this rom?". ^^
I believe what happen is that one user will check the 3 or 4 first roms and will get confused.
Generally speaking, I feel that when you read a rom description from the author, it is addressed to technical people. I think a centralized JIRA (each rom = one project) idea would be very helpful to compare but I don't know if it is easy to implement.
What do you think?
ergosum said:
Hi,
Firstly, I don't want to sound unrespectful to developers. It is just a few complains but I admire the time each one spend for creating new roms. There are lots, lots of roms/kernels in the android development section. It's a complete jungle! For a non technical user, I find it really difficult to choose a rom because:
There are no standard table stating what is different with the other. The list described by each developer is not always clear. Especially when he or she sees "aroma", "CRT", "ram hack", "zipalign" without explication. Wouldn't one nice and small sentence be sufficient to explain these terms?
The issues for each rom are not tracked. I think there should be a tracking system like JIRA so that we can confirm if a bug is already described and if it is still present in future release.
It should be clear if a rom is based from stock or AOSP rom (not always the case).
There is no centralized topic explaining the differences. But I have seen there is topic listing roms.
To my mind, there should be in each rom description something like a history, a short sentence like "I have based this rom on this other rom because I feel it lacks this and that." (not always the case), instead of just throwing "hi, [screenshot], how to install this rom?". ^^
I believe what happen is that one user will check the 3 or 4 first roms and will get confused.
Generally speaking, I feel that when you read a rom description from the author, it is addressed to technical people. I think a centralized JIRA (each rom = one project) idea would be very helpful to compare but I don't know if it is easy to implement.
What do you think?
Click to expand...
Click to collapse
Actually always or it is baseed on stock or aosp or cyanogenmod it's pretty much in every thread i see. it's always described in the information they write.
and a centralized topic where is everything written well. it's for everybody else some like Lg stock ui and some like more clean android
Issue tracking jira i dont really understand i only know that developers are just wanting a catlog if there is a problem so they can see from what the problem is coming from or what it is related.
and that from a short sentence well. every rom misses something it's for everybody different and in almost all roms they are describing where it is based on and they have permission to use other work (the base) but some people are not asking it like the miui team who just took kowalski kernel without permission and they don't even give credit or something like that.
this post is just my opinion how i think it is
ergosum said:
...
Generally speaking, I feel that when you read a rom description from the author, it is addressed to technical people.
Click to expand...
Click to collapse
I do support the idea of asking the developers for more detailed info of their ROM / kernel features, however keep in mind that this is an Android development site - members are expected to have some level of knowledge and / or the will to learn stuff by themselves.
On the other hand, I've seen developers who care enough to spend time writing detailed documentation about their work and yet you'll find people asking questions or posting stuff without even reading the OP or using the search function. This obviously discourages the developer. Who will want to spend hours or even days writing how their stuff works or what are its main features if people won't take the time to read it?
DrummerMuppet said:
I do support the idea of asking the developers for more detailed info of their ROM / kernel features, however keep in mind that this is an Android development site - members are expected to have some level of knowledge and / or the will to learn stuff by themselves.
On the other hand, I've seen developers who care enough to spend time writing detailed documentation about their work and yet you'll find people asking questions or posting stuff without even reading the OP or using the search function. This obviously discourages the developer. Who will want to spend hours or even days writing how their stuff works or what are its main features if people won't take the time to read it?
Click to expand...
Click to collapse
I understand, but I don't ask for hours of well descriptions. One sum-up sentence and one link to a topic where other people has already spent the time should be enough. Example: an developer says "here are the 3 kernels [links]" and the only difference you can tell when looking at the links was "32rh", "16rh", "0rh". I had to guess that "rh" is ram hack and search for what it is. While with just "the ram hack is taking memory from GPU for the CPU", it's a clean and quick explanation. Otherwise people are bound to ask questions when they see this.
As for the JIRA system, it's just more obvious to see, for a newcomer:
how much issue a rom has at the moment
if a troubling issue important for you is described and prevent you from using the rom (so you don't waste time)
help the developer to see easyly what is wrong (instead of navigating through all the post)
help the developer by centralizing all the relevant information for one issue in one page, instead of having these spread everywhere
Hi boys and gals and older fellows:
So, I have been following this forums for some weeks. I own a Redmi 2 Pro here in Mexico (2014819, 16 GB ROM and 2 GB RAM) and I wanted to test a fair amount of ROMS, I never had had a cellphone with so many custom ROMS available and I am very enthusiastic about it, so, I first went to CM13, then AICP, AOKP, DU, RR and even MIUI 8 Betas, until I found this ROM I still want to build called Paranoid Android. But I never compiled a ROM from source (I have been using Linux for many years, but never compiled an entire OS) and while I was trying to build AOSPA (or Paranoid Android) I realized it was too hard for my skills.
You see, I am only a user not a developer, and I see a lot of guys here developing and mantaining at the very same time, using their free time, processors, internet connection and patience for all of us, the users. So, I finally managed to compile CM13 from source and it runs pretty well (everything works) and it feels really great, like an achievement, but then I thought "Now what? Is it possible I can help other users? How can I learn more?". I know this is not a great achievement fro a developer, I did not create a device tree or developed a custom ROM or part of it or write a driver, I know too I can't really help any much more than I have helped to other users (as much or few as it can be). So, what do you think? I wanna learn more, I want to custom CM13 to my own needs as a learning exercise (add, remove, tweak governors; that sort of things).
||||||||||
TL;DR: I want to help people with a lot of work in his/her hands helping Redmi 2 community. I am a regular GNU/Linux user and I can compile CM13 from source. Is there any way I can help you to help others while I learn something more? Suggestions on what to do from now on are also welcome, keeping in mind I am not a developer and I do not want to be one.
Wrong place bro
You can get help from @s.sawrav and @pirej,these are sort of devs who could help you.
Btw if you can,please try to compile also nougat if you can.
And use Google for things you want to learn like oc,governors and stuff there are some pretty good threads here on XDA on how to build kernels and add features to it like this here http://forum.xda-developers.com/android/software/ultimate-guide-compile-android-kernel-t2871276 .
Wish you best luck?
Great, one more Dev for our little beast. Try Paranoid next ...
CENTSOARER said:
Hi boys and gals and older fellows:
So, I have been following this forums for some weeks. I own a Redmi 2 Pro here in Mexico (2014819, 16 GB ROM and 2 GB RAM) and I wanted to test a fair amount of ROMS, I never had had a cellphone with so many custom ROMS available and I am very enthusiastic about it, so, I first went to CM13, then AICP, AOKP, DU, RR and even MIUI 8 Betas, until I found this ROM I still want to build called Paranoid Android. But I never compiled a ROM from source (I have been using Linux for many years, but never compiled an entire OS) and while I was trying to build AOSPA (or Paranoid Android) I realized it was too hard for my skills.
You see, I am only a user not a developer, and I see a lot of guys here developing and mantaining at the very same time, using their free time, processors, internet connection and patience for all of us, the users. So, I finally managed to compile CM13 from source and it runs pretty well (everything works) and it feels really great, like an achievement, but then I thought "Now what? Is it possible I can help other users? How can I learn more?". I know this is not a great achievement fro a developer, I did not create a device tree or developed a custom ROM or part of it or write a driver, I know too I can't really help any much more than I have helped to other users (as much or few as it can be). So, what do you think? I wanna learn more, I want to custom CM13 to my own needs as a learning exercise (add, remove, tweak governors; that sort of things).
||||||||||
TL;DR: I want to help people with a lot of work in his/her hands helping Redmi 2 community. I am a regular GNU/Linux user and I can compile CM13 from source. Is there any way I can help you to help others while I learn something more? Suggestions on what to do from now on are also welcome, keeping in mind I am not a developer and I do not want to be one.
Click to expand...
Click to collapse
wow great!!!! i have some request. please build cm11. i know is oldschool, but its pretty light and stable for me
Keep up mates,... You are awesome!!
Great Work Bro
CENTSOARER said:
Hi boys and gals and older fellows:
So, I have been following this forums for some weeks. I own a Redmi 2 Pro here in Mexico (2014819).....
Well down bro... Great to go.. There are developers here who may help you to grow. I wish you all developers good luck and hearty THANKS for all your works here..
Thanks & Regards,
Ashok M
Click to expand...
Click to collapse
CENTSOARER said:
Hi boys and gals and older fellows:
So, I have been following this forums for some weeks. I own a Redmi 2 Pro here in Mexico (2014819, 16 GB ROM and 2 GB RAM) and I wanted to test a fair amount of ROMS, I never had had a cellphone with so many custom ROMS available and I am very enthusiastic about it, so, I first went to CM13, then AICP, AOKP, DU, RR and even MIUI 8 Betas, until I found this ROM I still want to build called Paranoid Android. But I never compiled a ROM from source (I have been using Linux for many years, but never compiled an entire OS) and while I was trying to build AOSPA (or Paranoid Android) I realized it was too hard for my skills.
You see, I am only a user not a developer, and I see a lot of guys here developing and mantaining at the very same time, using their free time, processors, internet connection and patience for all of us, the users. So, I finally managed to compile CM13 from source and it runs pretty well (everything works) and it feels really great, like an achievement, but then I thought "Now what? Is it possible I can help other users? How can I learn more?". I know this is not a great achievement fro a developer, I did not create a device tree or developed a custom ROM or part of it or write a driver, I know too I can't really help any much more than I have helped to other users (as much or few as it can be). So, what do you think? I wanna learn more, I want to custom CM13 to my own needs as a learning exercise (add, remove, tweak governors; that sort of things).
||||||||||
TL;DR: I want to help people with a lot of work in his/her hands helping Redmi 2 community. I am a regular GNU/Linux user and I can compile CM13 from source. Is there any way I can help you to help others while I learn something more? Suggestions on what to do from now on are also welcome, keeping in mind I am not a developer and I do not want to be one.
Click to expand...
Click to collapse
Good job :good: but this is not the right section to post this,ask a moderator to move this thread to appropriate section,also checkout the chef central in android section of XDA and then there's google,it'll help you out a lot.
Thread belongs in Discussing forum not Development, moved as requested by OP
CENTSOARER said:
Hi boys and gals and older fellows:
So, I have been following this forums for some weeks. I own a Redmi 2 Pro here in Mexico (2014819, 16 GB ROM and 2 GB RAM) and I wanted to test a fair amount of ROMS, I never had had a cellphone with so many custom ROMS available and I am very enthusiastic about it, so, I first went to CM13, then AICP, AOKP, DU, RR and even MIUI 8 Betas, until I found this ROM I still want to build called Paranoid Android. But I never compiled a ROM from source (I have been using Linux for many years, but never compiled an entire OS) and while I was trying to build AOSPA (or Paranoid Android) I realized it was too hard for my skills.
You see, I am only a user not a developer, and I see a lot of guys here developing and mantaining at the very same time, using their free time, processors, internet connection and patience for all of us, the users. So, I finally managed to compile CM13 from source and it runs pretty well (everything works) and it feels really great, like an achievement, but then I thought "Now what? Is it possible I can help other users? How can I learn more?". I know this is not a great achievement fro a developer, I did not create a device tree or developed a custom ROM or part of it or write a driver, I know too I can't really help any much more than I have helped to other users (as much or few as it can be). So, what do you think? I wanna learn more, I want to custom CM13 to my own needs as a learning exercise (add, remove, tweak governors; that sort of things).
||||||||||
TL;DR: I want to help people with a lot of work in his/her hands helping Redmi 2 community. I am a regular GNU/Linux user and I can compile CM13 from source. Is there any way I can help you to help others while I learn something more? Suggestions on what to do from now on are also welcome, keeping in mind I am not a developer and I do not want to be one.
Click to expand...
Click to collapse
Just start from doing the green thing
That's the best way to learn, and when/if you are happy with the modifications you made, and you think that the rom you made is different enough to be posted as a different/new/your rom, then post it.
pirej said:
Just start from doing the green thing
That's the best way to learn, and when/if you are happy with the modifications you made, and you think that the rom you made is different enough to be posted as a different/new/your rom, then post it.
Click to expand...
Click to collapse
I'm not familiar with the meaning of "the green thing", I love plants, so it would be great it is a plant-related saying. Care to elaborate a little? At the moment I am learning some useful repo parameters and attempting to build Resurrection Remix which seems going just OK.
I am downloading too all the source code from CM11, I think that's gonna be doable for a newbie like me, AOSPA is just too much right now, so I gave up with that for now, even documentation is hard to get.
CENTSOARER said:
I'm not familiar with the meaning of "the green thing", I love plants, so it would be great it is a plant-related saying. Care to elaborate a little? At the moment I am learning some useful repo parameters and attempting to build Resurrection Remix which seems going just OK.
I am downloading too all the source code from CM11, I think that's gonna be doable for a newbie like me, AOSPA is just too much right now, so I gave up with that for now, even documentation is hard to get.
Click to expand...
Click to collapse
in my quote of your post... i used GREEN color to mark something..
pirej said:
in my quote of your post... i used GREEN color to mark something..
Click to expand...
Click to collapse
Oh, I see now, thanks for the advice. This XDA Forums app can't parse color tags, so I was lost.
Hey I Was hoping you could build and Maintain a stable Cyanogen 12.1! A lot of people are still using 12.1 and kumajaya has stopped active development on that ROM. Plus the Sailfish OS community would really benefit from your support
Hello all, this is nothing more than a rom request that runs on android 7.1 nougat for the oneplus 3t. Ideally the rom should also be able to support daleski's pixilify v 10 mod for the oneplus 3 (which can be found with a quick search). The rom would also ideally include many of the features in oxygen os such as loclscreen gestures, 3 finger swipe, dark mode, oneplus camera, and app locking. I know that it takes time to build roms and everything I ask for may not be possible, so please take your time and include whatever is possible. If I had any knowledge on building roms, I would, but alas I am but a noob when it comes to these things. I just want to be able to have most of the same features that come with stock and cyanogen mod but also be able to have the pixel launcher and Google assistant on my 3t. Thanks in advance to the developer who puts in the work for this.
Lmao. Oh boy.
Lol.
First and foremost, this is a development forum. This is a place for developers to post ROM's, kernels, recoveries, etc. It is not a request forum.
Secondly, the developers here do not work for you. They do what they do mostly as a hobby, in their spare time, with little to no compensation outside of any donations they may receive.
If you are interested in ROM development, I suggest you check out XDA University here on the site.
Thread closed.
Hallos,
I seen alot of wonderull roms but it seems that people find it more important to get the latest greatest uploaded as soon as possible.
But there are bugs in your old releases. Maybe it would be good to FIRST fix the issues in your roms like AOD and fingerprint and what not
and THEN release your next one because as of lately we get new roms but the existing issues never get fixed.
Just my 2cp
But you're aware that this is a developers' forum, right? That means a) that one of the purposes of people posting their ROMs is to get testers and b) that bugs are normal and c) the developers don't owe you (or me or any of us) anything, apart from compliance with the licensing requirements.
If you demand finished products, there quite simply won't be that much going on here anymore, except for a few larger projects maybe. Can't really be the aim, I think.
Of course, it's great to get a fully working and bug-free ROM, but if I'm bothered by the problems, then I'd simply stick to my stock ROM (for which you could expect a bug free experience, insofar as you've at least paid for it).
I have no experience in ROMs whatsoever, but considering how long the aforementioned bugs have gone unattended, it's because they're preposterously difficult if not impossible to fix due to closed source and differences in hardware.
Putting that aside, don't you think it'd be better to tackle the problem yourself instead of complaining about it not having been done by anyone else?
Devs dedicate a lot of hardwork and precious time to make(port) Roms,they most times ended up with various types of bricks including permanent bricks just to put smile on our faces.
Can we comprehend the dreaded risks of soft and PERMANENT damages to our phones while testing core fixes for our relentless Developers?
caved said:
Hallos,
I seen alot of wonderull roms but it seems that people find it more important to get the latest greatest uploaded as soon as possible.
But there are bugs in your old releases. Maybe it would be good to FIRST fix the issues in your roms like AOD and fingerprint and what not
and THEN release your next one because as of lately we get new roms but the existing issues never get fixed.
Just my 2cp
Click to expand...
Click to collapse
Your post is inconsiderate. If you have a problem with bugs, stick to stock and send your complaints to Samsung. You are not doing anyone here a service by complaining about the work that devs donate free of cost. Please don't troll the dev community again because we don't want to discourage people from sharing their work.
caved said:
Hallos,
I seen alot of wonderull roms but it seems that people find it more important to get the latest greatest uploaded as soon as possible.
But there are bugs in your old releases. Maybe it would be good to FIRST fix the issues in your roms like AOD and fingerprint and what not
and THEN release your next one because as of lately we get new roms but the existing issues never get fixed.
Just my 2cp
Click to expand...
Click to collapse
Ah, the good ol "I came to XDA to pimp my phone" as if devs intentionally release roms with bugs. "FIRST fix the issues in your roms like AOD and fingerprint" No you fix them. go the route and learn android development so you can understand why some issues wont go. go to amazon and buy a new phone and stop complaining about what you get for free on a 3 year old device.