Why still in beta? - Verizon LG G3

Most of the official ROMS are still in alpha, beta or nightly with no milestone version. Why is that?

Because most people don't rely on roms....xposed framework has greatly impacted my usage of roms.
I dunno why. Most of what I have used certainly didn't feel like a beta.
I am pretty gosh darn thankful we have what we have considering the limited number of newer devices with Verizon that can be tinkered with.

Exactly,
You should be thankful for what you have and not question what you don't.
A lot of devs and myself have jumped to the nexus 6, yet we still come here and build for you guys.

jfriend33 said:
Because most people don't rely on roms....xposed framework has greatly impacted my usage of roms.
I dunno why. Most of what I have used certainly didn't feel like a beta.
I am pretty gosh darn thankful we have what we have considering the limited number of newer devices with Verizon that can be tinkered with.
Click to expand...
Click to collapse
I'm only curious because it's over a year old and they are still in this stage. That's all.
bweN diorD said:
Exactly,
You should be thankful for what you have and not question what you don't.
A lot of devs and myself have jumped to the nexus 6, yet we still come here and build for you guys.
Click to expand...
Click to collapse
What was the purpose of your reply?

digitallure said:
What was the purpose of your reply?
Click to expand...
Click to collapse
What was the purpose of your question? To piss of the few devs that still build for the g3?
Because thats how it came off, as ungrateful.

bweN diorD said:
What was the purpose of your question? To piss of the few devs that still build for the g3?
Because thats how it came off, as ungrateful.
Click to expand...
Click to collapse
Well you need some perspective glasses. My question was just that, a question. If you have a problem with my question, maybe you should've asked someone else what they thought I'd the question instead of jumping to the conclusion that my question was other than a question. Don't be a troll.

Why would you insult someone who is contributing to the community? He was just saying that you shouldn't worry about the state of the roms here just be thankful that there is something for you to flash since a lot of developers have moved on from this device. I don't think your original question was wrong but the way you handled the responses were. Again just be thankful you have what you have or install Linux and compile the roms yourself.

Wow... His question didn't seem too insulting to me, just a bit ignorant and curious.
Most 'Unofficial' ROMs are work that someone has ported to the device; they are not supported by the teams that made the original.
Official ROMs are created by and most supported by the team on the specific device; the download is usually a link to the team's website. However, in many cases, they may only have one device among them and have not tested everything to the extent that either a test group or the public at large would, naturally. Development is always a WIP, so the BETA indicator is almost universal in custom ROMs where there is not major funding. More often, stock-based ROMs are called stable, because they are working with the base of a stable product that includes all the proprietary drivers and frameworks, vetted by a commissioned dev team at the OEM and another at the carrier.
Some devs/teams here are able to do more testing than others, but the BETA is often an exemption for anything that might not have been found in limited testing. In short, a ROM is often in beta because it has not been thoroughly tested by numerous testers on a specific device, providing detailed feedback and some debugging to the dev team. The more that users here dig in and try to help as opposed to saying "Does this work on this?" or "Why this don't workee??", the more stable those Beta ROMs tend to be--and some are rock solid or only have a few niggles.
Also, if the codebase that a dev starts with is a beta or nightly release (e.g. CM or PA), the child/forked ROM will most always carry over the alpha or beta label.

smartguy044 said:
Why would you insult someone who is contributing to the community? He was just saying that you shouldn't worry about the state of the roms here just be thankful that there is something for you to flash since a lot of developers have moved on from this device. I don't think your original question was wrong but the way you handled the responses were. Again just be thankful you have what you have or install Linux and compile the roms yourself.
Click to expand...
Click to collapse
But I wasn't complaining. Simply asking a question about alpha and beta ROMs for the device. How is that insulting? If that was insulting, then every post made should be insulting. Why go any deeper? I just asked a question.
epidenimus said:
Wow... His question didn't seem too insulting to me, just a bit ignorant and curious.
Most 'Unofficial' ROMs are work that someone has ported to the device; they are not supported by the teams that made the original.
Official ROMs are created by and most supported by the team on the specific device; the download is usually a link to the team's website. However, in many cases, they may only have one device among them and have not tested everything to the extent that either a test group or the public at large would, naturally. Development is always a WIP, so the BETA indicator is almost universal in custom ROMs where there is not major funding. More often, stock-based ROMs are called stable, because they are working with the base of a stable product that includes all the proprietary drivers and frameworks, vetted by a commissioned dev team at the OEM and another at the carrier.
Some devs/teams here are able to do more testing than others, but the BETA is often an exemption for anything that might not have been found in limited testing. In short, a ROM is often in beta because it has not been thoroughly tested by numerous testers on a specific device, providing detailed feedback and some debugging to the dev team. The more that users here dig in and try to help as opposed to saying "Does this work on this?" or "Why this don't workee??", the more stable those Beta ROMs tend to be--and some are rock solid or only have a few niggles.
Also, if the codebase that a dev starts with is a beta or nightly release (e.g. CM or PA), the child/forked ROM will most always carry over the alpha or beta label.
Click to expand...
Click to collapse
Thank you! Ignorant, yes. Curious yes, that's all. Ignorant because I don't know. Curious because I want to know why.

digitallure said:
Thank you! Ignorant, yes. Curious yes, that's all. Ignorant because I don't know. Curious because I want to know why.
Click to expand...
Click to collapse
I get it, but you have to know your audience a little. Here, it's a bunch of developers and enthusiasts who freely give their time, skills, and work. While your question was about labels and versioning, the way that it is written, some may take it as "Why isn't your contribution further along and/or more stable than it is? Hell, it's been a year! How do you account for this?"
That BS isn't right when it's coming from someone who is paying you thousands for your work.

Related

Wouldnt this be interesting

I just saw that people are arguing on different rom threads and saying oh yours is better since you made this first but I tweaked it. (I mean no disrepect in that comment.)
Point being here is a interesting thing I thought of just to see what anyone else thought of. We have four main froyo roms Tazz, Kaos, Sheds and Conaps.
If people are fighting over whos to choose I was thinking maybe the four of them should make a combined rom since everything they use to build them is a combined effort anyway. I just personally think it would be interesting to see what they all would contribute and it would be the best rom all around due to it has everyones input. Its nice how they all are unique by themselves but it would be awesome to have them all mashed together if that makes sense. It would be fast, stable, and could probably even be updated more due to whomever had more time would be able to work on it.
I am not posting this to make people mad or to say one rom is better than the other I just think it would be rather neat to have one huge awesome rom to choose from. I know it would probably never happen but its a interesting thought.
I do not mean any disrespect or harm in this post either. I just figured maybe it would cause less arguments.
I just wanted to share an idea I had. What do you all think? Negative or positive.
sounds cool they all do seem to work together enough, lending each other things and being really quite friendly to each other on their posts. to have them together on a test ROM would be cool but i think they all have their individual ideas that keep them just different enough to make everyone happy no matter what their style i'm using Nonsensikal 16.1 now but i'm about to switch to Tazz... i'm not sure Vanilla or Gingerbread... overall though lol yeah i think that would be a great idea!! sorry i rant >< xD!
labnjab said:
I just wanted to share an idea I had. What do you all think? Negative or positive.
Click to expand...
Click to collapse
Having things in public view surely makes "who did what first" a non-argument - because one merely needs to look at the commits to find out who did what when.
As a reminder, devs who work on AOSP ROMs are under a GPL obligation to release their sources.
Without a doubt though, asking that cooks/devs publicly document their trickery increases their workload (in addition to build & test, add some "documentation" tasks) - so, the trade off might be better documentation - but fewer ROM updates per developer.
It is possible that having more information available about methods which are Eris hardware specific might encourage more people to participate in ROM "porting" activities, e.g. hacking of backlights, notification delivery, gps/sensor, and "pre-built" library requirements.
It is my impression that devs have shared some of this informally in private communications/IRC, but you would be hard-pressed to find explanations or mini-tutorials on most of these topics here on XDA (Eris) forums. That makes it more challenging for any would-be "ROM porting developer" - because they must re-invent those same wheels from scratch, or go begging to devs that have worked through those issues before. The latter certainly won't happen if they view the devs as combative or secretive.
I would suggest that if you can gain any traction with the devs on this, the baseline ROM should be AOSP - that way the GPL disclosure requirements align well with the benefit of making information readily available. (Perhaps never in the form of tutorials, but at least in the form of public source code).
bftb0
labnjab said:
Its nice how they all are unique by themselves but it would be awesome to have them all mashed together if that makes sense.
Click to expand...
Click to collapse
Well a lot of people don't like Sense UI so... But I think it could be a good idea. It's just hard to have to download the latest and greatest version anytime a dev wants to make a change, and two could never change it at the same time unless they were like teamviewing or something.
Yes it is hard having to switch versions everytime they make improvements & I didnt mean the sense ui. I meant i hoped the sentence made sense. Meaning all the newer froyo non sense roms rolled into one. Sorry for any confusion.
Sent from my FroyoEris using Tapatalk
I think Tenzo and Tazz have slowed down some of their development until they can get some common problems worked out.

Think we can get aosp now?

exactly like the op says, now that we have s-off, do you guys think we will get official aosp support sice some devs arent really willing to deal with s-on? im not requesting. i'm just interested in what others think
My question is what does the one have to do with the other? Or put it this way what does S-Off have to do with AOSP? just wondering, thanks.
Stryker1297 said:
exactly like the op says, now that we have s-off, do you guys think we can get official aosp support soon? im not requesting. i'm just interested in what others think
Click to expand...
Click to collapse
My personal opinion, i'm sure others will. I won't compile an AOSP rom for the DNA. My reason. I happen to love sense. Reason I stick with HTC phones. I don't like touchwiz (earth, haze, whatever they keep changing the ui name to) and moto ui is too much like stock. I like personality in my phone.
Stryker1297 said:
exactly like the op says, now that we have s-off, do you guys think we can get official aosp support soon? im not requesting. i'm just interested in what others think
Click to expand...
Click to collapse
Not to sound like a jerk but it seems like you should know your way around....
We always have AOSP thats why its called android OPEN SOURCE project. The question is will someone be able to port it to the DNA.
Go to the Orig. Android Dev section for the DNA and you will see drewx2 an others have been working tirelessly on porting CM10.1 (AOSP) to the DNA. Instead of asking a question that has been answered in the thread you should go check it off.
And S-OFF has nothign to do with porting AOSP. It might make a difference considering other devs may get the phone now that the bootloader is fully unlocked. But it has no DIRECT effect.
How many of these threads do we need?? You could not have posted in the AOSP thread right below yours?? Besides if you people wanted AOSP you should have bought a Nexus. SMH
zone23 said:
My question is what does the one have to do with the other? Or put it this way what does S-Off have to do with AOSP? just wondering, thanks.
Click to expand...
Click to collapse
My dear Zone. I think the question was, now that there's no security whatsoever, does it mean now we have the capability to modify the device even further.
The S-off feature allows us to upgrade the firmware (ie, bootloader ver, radios) on our devices. The software is capable after root is achieved. Root in lamens terms is giving yourself administrative rights over your phone, ,much like you have administrative rights on your windows computer. BUT, linux does not have administrator priveleges, it has root priveleges. Thats why Zone is confused by your queston.
Unphazed MD said:
Not to sound like a jerk but it seems like you should know your way around....
We always have AOSP thats why its called android OPEN SOURCE project. The question is will someone be able to port it to the DNA.
Go to the Orig. Android Dev section for the DNA and you will see drewx2 an others have been working tirelessly on porting CM10.1 (AOSP) to the DNA. Instead of asking a question that has been answered in the thread you should go check it off.
And S-OFF has nothign to do with porting AOSP. It might make a difference considering other devs may get the phone now that the bootloader is fully unlocked. But it has no DIRECT effect.
Click to expand...
Click to collapse
number 1, yes you sound like a jerk. number 2, some people dont have time to search for a partial answer to somebody else's question. 3, i asked for OPINIONS on the subject. not answers or eta's. 4, i have seen the thread, i asked for speculations on official ports, and i am very aware of the hard work devs put in (donated to jcase and beaups). and 5, s-off has a LOT to do with aosp ports, since many devs refuse to support locked phones, which is an effect. not direct, but still an effect.
honestly i know now why xda's rep is such crap now. when i try to start a conversation on this site all you get is a bunch of trolls with nothing better to do than act condescending and sarcastic.
and thank you dragonstalker for being just about the only person on this thread that even attempted to act sensible and polite
Memnoch73 said:
How many of these threads do we need?? You could not have posted in the AOSP thread right below yours?? Besides if you people wanted AOSP you should have bought a Nexus. SMH
Click to expand...
Click to collapse
where's the fun with nexus phones? number one, i am a strict lte user. two, i dont really like nexus because you dont get to really choose other oem skins. some days i like sense/touchwiz, and other days i like aosp. and no wont post in the other thread. they arent looking for the same conversation/info i am, and i'm not gonna add another question to a question thread. SMH
well some devs might be more interested in getting the phone now that it has s off. I don't think it has a direct effect either but making things more convenient for the end user to install kernels should entice more people, including devs looking for a new toy.
Stryker1297 said:
number 1, yes you sound like a jerk. number 2, some people dont have time to search for a partial answer to somebody else's question. 3, i asked for OPINIONS on the subject. not answers or eta's. 4, i have seen the thread, i asked for speculations on official ports, and i am very aware of the hard work devs put in (donated to jcase and beaups). and 5, s-off has a LOT to do with aosp ports, since many devs refuse to support locked phones, which is an effect. not direct, but still an effect.
honestly i know now why xda's rep is such crap now. when i try to start a conversation on this site all you get is a bunch of trolls with nothing better to do than act condescending and sarcastic.
and thank you dragonstalker for being just about the only person on this thread that even attempted to act sensible and polite
Click to expand...
Click to collapse
Theres nothing wrong with "XDA's" rep. Its people posting/asking the same quesitons over and over again without taking the 5 minutes to browse the forums or 30 seconds to do a search. Theres been like 800 S-OFF/AOSP related threads/questions when in truth they honestly arent that related. S-OFF is essentially disabling a security check. AOSP is the source.
You could of also just posted like someone else said in one of the other threads on the front page of DNA Q/A asking about S-OFF/AOSP. I dont post a lot but honestly all of these questions being asked over and over again is really silly.
Same with asking about an ETA. The ETA is when the devs finish it. If you want it faster help out. Its not easy.
Maybe you should have reworded your question to something like "Now that we have S-OFF is porting AOSP and easier/quicker which would speed up the eta?"
Im sorry but after the whole debacle with people bugging devs and almost driving them out of the scene and taking them for granted I am not trying to have this widespread post spam happen.
and btw official CM10 support usually happens after somone has a stable and organized build. Then CM10 will usually ask them to become the official maintainer for that device. DrewX2 posted about it in the CM10.1 DNA thread I am not giving that great of an explanation.
dragonstalker said:
My dear Zone. I think the question was, now that there's no security whatsoever, does it mean now we have the capability to modify the device even further.
The S-off feature allows us to upgrade the firmware (ie, bootloader ver, radios) on our devices. The software is capable after root is achieved. Root in lamens terms is giving yourself administrative rights over your phone, ,much like you have administrative rights on your windows computer. BUT, linux does not have administrator priveleges, it has root priveleges. Thats why Zone is confused by your queston.
Click to expand...
Click to collapse
Ya I get confused a lot thanks for cleaning that up for me.
Technically we have AOSP but with Sense skin. If you want AOSP feel then flash a deSensed rom (Sence isn't completely removed, only as much as possible) and use an AOSP theme.
orangechoochoo said:
Technically we have AOSP but with Sense skin. If you want AOSP feel then flash a deSensed rom (Sence isn't completely removed, only as much as possible) and use an AOSP theme.
Click to expand...
Click to collapse
Let me clarify something... AOSP is nothing like sense... Sense isn't a skin it's a full OS. HTC didn't theme AOSP, they built from ground up an os based on android kernel / Linux kernel
Sent from my HTC6435LVW using XDA Premium HD app
Nevermind, you're right.
http://www.xda-developers.com/andro...d-skins-aosp-sense-touchwiz-xda-developer-tv/
orangechoochoo said:
Nevermind, you're right.
http://www.xda-developers.com/andro...d-skins-aosp-sense-touchwiz-xda-developer-tv/
Click to expand...
Click to collapse
Yea that's exactly what I was referencing from lol
orangechoochoo said:
Nevermind, you're right.
http://www.xda-developers.com/andro...d-skins-aosp-sense-touchwiz-xda-developer-tv/
Click to expand...
Click to collapse
Wow, someone who admits they're wrong. I didn't know that existed on the Internet.
Sent from my HTC6435LVW using xda app-developers app
Unphazed MD said:
Theres nothing wrong with "XDA's" rep. Its people posting/asking the same quesitons over and over again without taking the 5 minutes to browse the forums or 30 seconds to do a search. Theres been like 800 S-OFF/AOSP related threads/questions when in truth they honestly arent that related. S-OFF is essentially disabling a security check. AOSP is the source.
You could of also just posted like someone else said in one of the other threads on the front page of DNA Q/A asking about S-OFF/AOSP. I dont post a lot but honestly all of these questions being asked over and over again is really silly.
Same with asking about an ETA. The ETA is when the devs finish it. If you want it faster help out. Its not easy.
Maybe you should have reworded your question to something like "Now that we have S-OFF is porting AOSP and easier/quicker which would speed up the eta?"
Im sorry but after the whole debacle with people bugging devs and almost driving them out of the scene and taking them for granted I am not trying to have this widespread post spam happen.
and btw official CM10 support usually happens after somone has a stable and organized build. Then CM10 will usually ask them to become the official maintainer for that device. DrewX2 posted about it in the CM10.1 DNA thread I am not giving that great of an explanation.
Click to expand...
Click to collapse
did you not read how i just said i didnt ask for eta's or roms. do you know how to read. also did you read how i said i donate to devs when possible. also did you read how i said i wasnt asking for progress updates. i said i was looking for CONVERSATIONAL OPINIONS ON THE SUBJECT
Bigandrewgold said:
Wow, someone who admits they're wrong. I didn't know that existed on the Internet.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
It doesn't hurt to be wrong, it's a learning experience :good:
No s off won't make CM10 any easier to build. Fixing not being able to push or pull system files while phone is booted makes things much easier to work with and in my opinion was way more helpful to the devs on general.
If you look at some of the recent HTC devices, a good number of those devices are s off, and the AOSP developers went back to s on because of safety concerns for the device after a few mishaps building from source.
To build AOSP for a device like this requires some serious skill on the RIL (radio interface layer) department especially. Using the command line for a few things like boot.img isn't challenging to someone that can build from source for AOSP. And definitely is a skill someone porting AOSP roms and especially trying to crack RIL would have acquired a long time ago. While on the surface it seems so advantageous to the end user, to port AOSP over to a brand new device, my 2 sense is that s on is the least of their worries.
And yeap the guys above me are right, sense is built as sense from the ground up. And unlike AOSP, most of sense is proprietary so unlike AOSP Android, it has to be reverse engineered and then built to work on the hardware in our phones. The linux kernel used by HTC is open source and they comply with the GPL and release kernel source code for it. But everything proprietary is kept pretty locked down to prevent Samsung from using sense 5 and calling it "Samsung inSense"
There may be
Sent from my DNA... S-Off like a baws
Why do so many people buy HTC phones which all come with some form of Sense and then spam XDA with questions about when can we get AOSP? The answer to the question by the OP is no because S-Off has nothing to do with getting AOSP. As Charles put it the biggest hurdle on every HTC device I have had for the devs to get AOSP working is RIL and kernel.

Ready for some WAVES...

Theres something that was pointed out to me by a new friend, that I had to vent about.. so HERE IT IS!!1
Why are some people too good to hang out in their threads and answer questions about the builds they post???
It seems to me that it builds credibility, to help the people using your build, so why not hang out and answer questions, address issues, help finding solutions, offer advice... BE HUMAN
Sure its great that new builds are being pushed out constantly... BUT IF YOURE NOT TALKING TO THE PEOPLE RUNNING THE CURRENT ONE AND EXPERIENCING PROBLEMS WHAT GOOD IS IT????
Step down from the clouds, and walk barefoot on the grass with the rest of us.. its cool and refreshing on your feet
WOW Man..
pitbull8265 said:
Theres something that was pointed out to me by a new friend, that I had to vent about.. so HERE IT IS!!1
Why are some people too good to hang out in their threads and answer questions about the builds they post???
It seems to me that it builds credibility, to help the people using your build, so why not hang out and answer questions, address issues, help finding solutions, offer advice... BE HUMAN
Sure its great that new builds are being pushed out constantly... BUT IF YOURE NOT TALKING TO THE PEOPLE RUNNING THE CURRENT ONE AND EXPERIENCING PROBLEMS WHAT GOOD IS IT????
Step down from the clouds, and walk barefoot on the grass with the rest of us.. its cool and refreshing on your feet
Click to expand...
Click to collapse
Could not have said it better.... You hit the nail right on the head.. People respect those who back their work with support:good::good::good:
This DOES seem to be in SHORT reserve.. WELL STATED
Impressive
I have noticed this too.. Its like these people are too GOOD for Q&A and sometimes even respond to questions like they are PETTY and an inconvenience.. There ARE some who DO help, and those people deserve to know they are appreciated.. You in particular, have helped me a ton, so thanks.. Maybe you'll start a movement, and more people will start doing their part to help their followers...
+1
There is a SERIOUS shortage of helpers and an overage of shovelers
All these builds keep coming, and still the same problems on the one they put out before with a different NAME for the ROM.. Its like they change the name and recycled it..
I read through threads now, and if the OP doesn't hang out and help their users, I wont use their builds anymore.
Couldn't agree more!! Nicely said too
Be proud of your work.. Stick around and make sure people can..ya know, enjoy it too..
It's quality not quantity that matters. Stepping on other teams and developers to rush something out just to say "FIRST" will get you no where.. So while timely updates are important, if that's the only thing you post in your own thread.. "New build is up" when there's been 10 pages of people asking questions... I'll never support you, both publicly or financially.
I understand new enthusiast can be quite frustrating or maybe you just aren't a people type of person.. team up with someone that is... pass the q&a on to them, but do fricking something, people want support for YOUR roms and if you put out 20..that means all 20.
Exactly, how dare these developers not spend any time in the forums answering the same useless non-informative questions over and over. How dare they spend countless hours building a ROMs for free and then share it for others to use. How dare they spend time with their families and go to their actual job and have a life. How dare they….. (/sarcasm)
mapatton82 said:
Exactly, how dare these developers not spend any time in the forums answering the same useless non-informative questions over and over. How dare they spend countless hours building a ROMs for free and then share it for others to use. How dare they spend time with their families and go to their actual job and have a life. How dare they….. (/sarcasm)
Click to expand...
Click to collapse
Yea, I'm somewhere between this and the op. They shouldn't be 100% absent, but on the same note, some consideration for the above quote is in order too.
While were venting, its possible the devs haven't figured out how to fix some of these issues, but it doesn't do a dam bit of good for 50 people to complain about the same thing and no one is posting logcats. So don't complain about things not getting fixed, if your not attaching logs to every post about issues.
Just my 2c, add 97c more and go buy a cheeseburger.
Sent from my G3, Unlocked by Team Codefire
mapatton82 said:
Exactly, how dare these developers not spend any time in the forums answering the same useless non-informative questions over and over. How dare they spend countless hours building a ROMs for free and then share it for others to use. How dare they spend time with their families and go to their actual job and have a life. How dare they….. (/sarcasm)
Click to expand...
Click to collapse
Then why put out 20 instead of 1 that they can handle is the point!!
Variety is the spice of life. I'd rather have 20 that will get fixed eventually than just 1 that works perfectly. If they are all too similar for you then just move on to another one, build your own, or just wait for fully featured lollipop which will be here soon enough. If a thread is maintained or not - I'm just happy to have a thread. A couple devs have walked away already and it'd suck if more left. Just be grateful for what we've got and be patient.
Kris Nelson said:
Then why put out 20 instead of 1 that they can handle is the point!!
Click to expand...
Click to collapse
The same person is not releasing 20 different versions. Also, most are all based off of the AOSP core source, but each dev might add their own touch/flare to it. But, since each one is based off of AOSP, then more than likely, they will all have the same issues, unless the dev has made some changes.
I'd rather have a lot of choices than none. Believe me, when there is NO dev support (that is, a lot of ROMs being release), then you get even MORE whining of "Why isn't there any ROMs/dev support for this?"
Maybe you're not a dev, but I am (not for ROMs but that is my full-time job). Development takes a lot of time. I do it at work and to do it at home as well, especially for something that is free, takes a lot of time and dedication. Especially, ROM development is NOT an easy task. Rebuilding ROMs takes at least 90 minutes or more, depending on the speed of your machine, the size of the source code, etc. Heck, I've pulled down the git for CM12 and it's 12gb in size (source code only, not compiled) and it took hours to download over my high-speed internet connection at home.
I can understand wanting support if you PAID for it, but this is free, people. Free. They don't ask for anything in return monetarily, and yet, we see people demanding support as if they paid for it. You get what you pay for, and in this case, it's free. But I feel the support most devs give is very good, considering it's free. Also, for things like CM, it's usually not just one dev, but several who have responsibilities for different parts of the Android code base. So, just because one guy posts about it, doesn't mean he's the only dev on it. He might be sending your findings back to the other devs.
Also, you DON'T have to flash these custom ROMs. They all have disclaimers that the dev is not responsible for any damages that may occur to your phone. They don't guarantee support, but it's there for you to use. However, who is to say they aren't monitoring the forums? Just because they don't respond, doesn't mean they aren't looking into the issues you report.
Yes, I understand how you want a response from them, but in the end, it is your choice whether you want to flash or not. They didn't twist your arm to do it.
Keep posting your defects. Most devs, the good ones, do monitor the forums and take note of the issues. However, they know about other major issues that they are probably trying to work on. Again, for most, it is done in their spare time.
I myself would like to build and release ROMs, but right now, I don't have the time. it's not just "make a change, compile, release". There is a lot of researching, debugging, etc that must go on. Those that are programmers understand this. And, once you fix a bug, you don't just go and release it (under normal circumstances). You have to go through a complete testing cycle, retesting previous tests along with any new tests to ensure you didn't break something else. It's not that simple.
However, with these free releases, WE are the testers. WE are the ones that report back the issues so they can be addressed. Post them here, or even some devs have Twitter pages where you can post defects. Not all, but some.
In the end, be thankful you have so many choices. Yes, it may seem as if they are all the same, and in some cases they are and some are from people who just want to say "look I released a ROM" and then you never hear from them again. But, in the case of XDA, to post about a ROM in the dev forum, I believe you have to be an identified developer, so they do have to go through some vetting process. So, more than likely, they are legit developers, not a fly-by-night person.
Just wanted to get that off my chest. I understand what people feel, but you have to understand, this is not an easy thing to do. Maybe a lot of you understand that, but I find that a lot don't. Or, they say they understand, when they really don't. They just "think" they understand.
Wow. Off the soapbox. It just burns me as a developer when I see things like this. Yes, I understand where you are coming from, but sometimes, I think you need to hear it from the other side as well.
Ciao!
If you're a good parent, when you bring a child into this world, you raise it, and nurture it... creating it is not enough...
noun
1.
the act or process of developing; growth; progress:
iBolski said:
The same person is not releasing 20 different versions. Also, most are all based off of the AOSP core source, but each dev might add their own touch/flare to it. But, since each one is based off of AOSP, then more than likely, they will all have the same issues, unless the dev has made some changes.
I'd rather have a lot of choices than none. Believe me, when there is NO dev support (that is, a lot of ROMs being release), then you get even MORE whining of "Why isn't there any ROMs/dev support for this?"
Maybe you're not a dev, but I am (not for ROMs but that is my full-time job). Development takes a lot of time. I do it at work and to do it at home as well, especially for something that is free, takes a lot of time and dedication. Especially, ROM development is NOT an easy task. Rebuilding ROMs takes at least 90 minutes or more, depending on the speed of your machine, the size of the source code, etc. Heck, I've pulled down the git for CM12 and it's 12gb in size (source code only, not compiled) and it took hours to download over my high-speed internet connection at home.
I can understand wanting support if you PAID for it, but this is free, people. Free. They don't ask for anything in return monetarily, and yet, we see people demanding support as if they paid for it. You get what you pay for, and in this case, it's free. But I feel the support most devs give is very good, considering it's free. Also, for things like CM, it's usually not just one dev, but several who have responsibilities for different parts of the Android code base. So, just because one guy posts about it, doesn't mean he's the only dev on it. He might be sending your findings back to the other devs.
Also, you DON'T have to flash these custom ROMs. They all have disclaimers that the dev is not responsible for any damages that may occur to your phone. They don't guarantee support, but it's there for you to use. However, who is to say they aren't monitoring the forums? Just because they don't respond, doesn't mean they aren't looking into the issues you report.
Yes, I understand how you want a response from them, but in the end, it is your choice whether you want to flash or not. They didn't twist your arm to do it.
Keep posting your defects. Most devs, the good ones, do monitor the forums and take note of the issues. However, they know about other major issues that they are probably trying to work on. Again, for most, it is done in their spare time.
I myself would like to build and release ROMs, but right now, I don't have the time. it's not just "make a change, compile, release". There is a lot of researching, debugging, etc that must go on. Those that are programmers understand this. And, once you fix a bug, you don't just go and release it (under normal circumstances). You have to go through a complete testing cycle, retesting previous tests along with any new tests to ensure you didn't break something else. It's not that simple.
However, with these free releases, WE are the testers. WE are the ones that report back the issues so they can be addressed. Post them here, or even some devs have Twitter pages where you can post defects. Not all, but some.
In the end, be thankful you have so many choices. Yes, it may seem as if they are all the same, and in some cases they are and some are from people who just want to say "look I released a ROM" and then you never hear from them again. But, in the case of XDA, to post about a ROM in the dev forum, I believe you have to be an identified developer, so they do have to go through some vetting process. So, more than likely, they are legit developers, not a fly-by-night person.
Just wanted to get that off my chest. I understand what people feel, but you have to understand, this is not an easy thing to do. Maybe a lot of you understand that, but I find that a lot don't. Or, they say they understand, when they really don't. They just "think" they understand.
Wow. Off the soapbox. It just burns me as a developer when I see things like this. Yes, I understand where you are coming from, but sometimes, I think you need to hear it from the other side as well.
Ciao!
Click to expand...
Click to collapse
Thank you.. Just to correct you though.. There ARE the same persons that are putting out 20 different versions (1 developer. releasing 20 different roms.) That was just the point i was making..
I do personally research before i ever flash a rom or anything..and trust me i donate!! LOL
Kris Nelson said:
Thank you.. Just to correct you though.. There ARE the same persons that are putting out 20 different versions (1 developer. releasing 20 different roms.) That was just the point i was making..
I do personally research before i ever flash a rom or anything..and trust me i donate!! LOL
Click to expand...
Click to collapse
I see who you are talking about. If you read the OP, at the bottom, he gives thanks to the devs on these ROMs. I don't think he's a developer at all. At least, his profile doesn't say so. I think he just finds all these ROMs and posts links to them. I could be wrong, and I apologize if I am if that person is reading this thread, but I don't see where the OP of the 5+ ROM threads is the actual developer for them. It's almost like he does the "announcing" for the devs of those ROMs.
And since it does appear that you do not have to be a developer to post in the standard DEV forum, then that makes even more sense.
I do know that in another forum I frequented a lot, you were given developer status and only developers could create new threads in the DEV/ROM forum. That was to prevent a lot of "spam" postings of ROMs.
Makes me wonder if that's what is happening here.
iBolski said:
I see who you are talking about. If you read the OP, at the bottom, he gives thanks to the devs on these ROMs. I don't think he's a developer at all. At least, his profile doesn't say so. I think he just finds all these ROMs and posts links to them. I could be wrong, and I apologize if I am if that person is reading this thread, but I don't see where the OP of the 5+ ROM threads is the actual developer for them. It's almost like he does the "announcing" for the devs of those ROMs.
Click to expand...
Click to collapse
I wish you were correct but nope, he is the builder and maintainer. Trust me many more than 5+ when you include other carriers as well.. But not just the one, others have started as well... It's very frustrating that after 1 week, several messages of a very specific problem (not mine just someone i was helping) on different sites where they are posted.. I have to track down someone that i know can help but has NOTHING to do with any of these roms...and gets zippy cash.. Though he should..lol
Anyway, i truly value great developers and have learned who to support and who not to. I like to help people so the developers can build awesome stuff and its my way of keeping the simple crap of your plate so you can do just that..but when i can't even find the answer, the developer should be available.
Just saw your edit.. Yes i think that is happening too. I was always under the assumption that builders/maintainers did so for the actual devise and carriers they use.. I guess that's no longer the case.
Oadam11 is a builder of various roms for our G3's from source repositories available for anyone to build from, and anyone to commit to. He may or may not be doing any commits/merge requests - and even if he did those contributions might not be accepted into the various G3 forks.
In any case, he might not be in a position to contribute to feature requests or bug fixes. He might not be running his own builds of all these roms, past checking to see if they will boot and more or less work.
Say Team Vanir does a fork of their work for the G3, an official one. Ok, then you would ask for support from members of Team Vanir, sure, though you might not get much, depending on a lot of factors (including your attitude...) Then consider the possibility that someone just builds something like Commotio from publicly available sources, with just enough tweaks from somewhere to get it to compile and run, unofficially, on one or more G3 variants. I suspect that is where oadam11 is coming from. He doesn't create the roms, he builds them for G3's. He watches the repositories for each rom he has built for us, and when he sees that rom's devs have checked in and merged useful updates, then he rebuilds for us when he has time. Builds take a while. Then he makes them available for us users to download and install them, after some degree of testing.
The point is that he is in no way responsible for supporting the builds he produces of these team's work. It would be impossible for him to anyway. I am sure he gets permission and some degree of cooperation from any team project he builds from, but he is NOT a team member, or major contributor, for all of them. He is a noble builder and distributor, and you should expect nothing more from him than What he is already providing.
If you want to get a problem or new feature dealt with on any given rom, you must deal with the team's source contributers by raising issues on their gerrit or maybe working on an outstanding and team-prioritized bug as a contributor.
Sent from my VS985 4G using Tapatalk
Thank you..you actually confirmed the point I was making. However, is the average person going to know all this? Of course not...should they do their research prior, of course but they don't... I see good teams being hurt by this as well.. Vanir just had an issue the other day.. Something is being lost in translation and by no means was i only referring to Adam.
I understand. It is interesting that in G+ just a little why ago someone asked David Kessler of Team Vanir who was their maintainer of the G3 Vanir and he replied that they don't have one.
There was also discussion about someone providing support, like answering questions. The idea of supporting a clueless user who had tried to flash TouchWiz onto a Vanir device, by beating the user over the head with an iPhone6+ was suggested. The devs have no patience with such users, generally.
That said, Holy Angel seems exceptional.
Sent from my VS985 4G using Tapatalk
The problem I have, is that when a person POSTS a Rom, and are the OP, they need to support what they post, and help the people posting questions in the thread, or BOW OUT!!! There are people posting and dumping... DONT Post a ROM if you're not willing or able to help the team you are Posting links to... Dont post it and then say "Any problems, contact THEM"
THAT PERSON mentioned, has a lot of them, all as OP, none supported other than.."New build up"
Raising the age limit for COPPA
The amount of entitlement exhibited in this thread is phenomenal. Yes, by all means don't use a build if the developer (who has actually done some REAL WORK) won't support you to your liking.
That will really teach those mean developers a lesson.
Don't forget to complain about the slow speeds of free downloads as well.
It's also a good idea to stop using a build if the developer won't add features you want, and soon, too.
DeanGibson said:
The amount of entitlement exhibited in this thread is phenomenal. Yes, by all means don't use a build if the developer (who has actually done some REAL WORK) won't support you to his/her liking.
That will really teach those mean developers a lesson.
Don't forget to complain about the slow speeds of free downloads as well.
It's also a good idea to stop using a build if the developer won't add features you want, and soon, too.
Click to expand...
Click to collapse
Just because you want a feature, doesn't mean it's a good feature to add. If you did that, you would end up with something that could eventually become impossible to maintain.
There are SO many bugs right now in the AOSP code that these devs are trying to fix to make it work on this phone. I would rather those get fixed first.
And, do you think you are the only one to ask for features?
I'm a developer, not for android, but I write code for a living. And what you are asking for is what we call "scope creep". We have to weed out the "must haves" with the "wants". Must haves are the things that they user must have in order to perform their job. This is usually adding functionality that isn't there currently that is needed to complete their job. The "wants" are "I would like to have the ability to clear out all background apps with a single button or swipe". That is NOT needed on this phone, but it's a nice "to have" option, but it doesn't affect the overall performance of the OS itself. Yes, you might say it does because you can clear out the background apps, but in reality, those apps are NOT running. I don't want to get into the specifics of android app management, but those apps you see in the "recent apps" history are NOT running. They are suspended and not taking up ANY CPU cycles, what-so-ever. If they happen to be, then it's a poorly written app, and it means the dev knowingly circumvented the Android OS app management process which is a big no-no. In that case, you should go back to the dev of the app and demand they fix that.
But, you are free not to install the ROM. That's fine and that's your choice, but it just irks me when I see people make complaints like this who probably have no idea what the software development life cycle is all about. To me, fixing bugs right now is the main issue, not adding pretty enhancements to the OS.
And who's to say they aren't working on what you ask, especially if you ask for fixes to major issues (such as battery life, radio, etc)?
Remember, these are UNOFFICIAL releases. They are based off of AOSP source which is pretty much device-agnostic except when it comes to Nexus devices since those are Google devices and therefore, the AOSP source is built for those type of devices.
Android is completely different from iOS. iOS is built for a set of hardware that doesn't have much variance like Android does. Hence, that is why Apple controls both the software AND the hardware of iPhones. It means less fragmentation across devices, but it also means, they decide what is best and you have no way of getting the source.
Google releases the source for Android so you CAN have these custom ROMs built. But, because one Android device has a different hardware configuration from another (CPU and GPU's being the biggest ones), then anything that can take advantage of the hardware architecture for a particular phone means having to change the AOSP source to use any of those "advantages" from that hardware. Which then means, that source no longer works on other phones, only for the phone they modified it for.
So, give the devs some slack, please. They are working hard on it and it's not one dev. If it were, then give the guy even MORE slack. The source for Android is over 12gb along. That is where it's not even compiled. And, compiling the android source generally takes about 90 minutes. So, each "fix" they do requires recompiling (90 minutes) and then testing.
Then, more than likely, the "fix" either didn't work or it possibly broke something else. That means, going back, determining the issue, fixing it, recompiling (wait another 90 minutes) and test again.
That all takes time, people. We developers are NOT magicians, even though it might seem like it.
So, try to imagine trying to fix all the big bugs that you know about, then have to come here, read through ALL the posts and then log those requests down, prioritize them based on all the other work you have, make those changes, recompile, test, etc. It's not a easy and it gets frustrating. But believe me, when we do fix an issue or are able to give the users what they want, we get an extreme amount of satisfaction knowing that we were able to satisfy the "customer".
So please, be careful what you state about devs. Those that do read here usually have thick skins, but complain enough, and they might just quit and then you have nothing.
I understand where people are coming from, but you've been blaming the devs when it's not their fault. Again, the android source is huge and it takes more than one person to work on it. Especially if they are responsible for more than one device. Some devs are working on source for more than just this phone. So, add that to what I already stated and hopefully, you can begin to understand what the devs are going through.

Discontinued

Deleted
Reserved
Deleted
Reserved
Fingerprint sensor and laser auto focus , can you please add those?
Yes thats only stopping me from flashing roms
I ask this with respect, but are you even the original developer of this ROM? Or the other 3 ROMs that you've posted here? It feels like you might have just copied and pasted OPs, and then provided people with an untested version you just compiled and uploaded.
LiquidSolstice said:
I ask this with respect, but are you even the original developer of this ROM? Or the other 3 ROMs that you've posted here? It feels like you might have just copied and pasted OPs, and then provided people with an untested version you just compiled and uploaded.
Click to expand...
Click to collapse
I'm not the 'original' developer of this ROM.I build ROMs and release them on XDA after the testers test it and report to me.So technically there's no way that my ROMs won't boot.You can look at my other ROMs that I've posted in XDA and take the feedback from the users that are using it.
aniket.lamba said:
I'm not the 'original' developer of this ROM.I build ROMs and release them on XDA after the testers test it and report to me.So technically there's no way that my ROMs won't boot.You can look at my other ROMs that I've posted in XDA and take the feedback from the users that are using it.
Click to expand...
Click to collapse
Is there a reason why your "testers" are consistently missing the fact that things like the fingerprint sensor aren't working, and that you don't seem to have a "Known Issues" list on any of the four ROM threads that you created within 2 hours?
LiquidSolstice said:
Is there a reason why your "testers" are consistently missing the fact that things like the fingerprint sensor aren't working, and that you don't seem to have a "Known Issues" list on any of the four ROM threads that you created within 2 hours?
Click to expand...
Click to collapse
The bugs are same as that of CM12.1 by Grarak.There's no stable device trees other than Grarak's,now you're insisiting so much,I'll put them in the OP.
aniket.lamba said:
The bugs are same as that of CM12.1 by Grarak.There's no stable device trees other than Grarak's,now you're insisiting so much,I'll put them in the OP.
Click to expand...
Click to collapse
I'm not "insisting so much". There is a standard of development that most of XDA's developers abide by. If you're really going to simultaneously maintain 4 different ROMs at once, the least you can do is give your users a bit more information than that which you blindly copy from another thread's OP, especially if you have no intention of running any of them yourself (I assume you at least have the device itself, but now, I'm not so sure)
I looked through your started threads, it seems you have a habit of compiling a bunch of different ROMs and putting them up with little to no testing whatsoever. I'm not sure if you thought no one would notice that the only 4 ROM threads in this section are all from you and they were all posted within an hour or two.
Good luck with your "development". I don't think I need to add anything else to this thread.
LiquidSolstice said:
I'm not "insisting so much". There is a standard of development that most of XDA's developers abide by. If you're really going to simultaneously maintain 4 different ROMs at once, the least you can do is give your users a bit more information than that which you blindly copy from another thread's OP, especially if you have no intention of running any of them yourself (I assume you at least have the device itself, but now, I'm not so sure)
I looked through your started threads, it seems you have a habit of compiling a bunch of different ROMs and putting them up with little to no testing whatsoever. I'm not sure if you thought no one would notice that the only 4 ROM threads in this section are all from you and they were all posted within an hour or two.
Good luck with your "development". I don't think I need to add anything else to this thread.
Click to expand...
Click to collapse
Nevermind,I updated the first post with the bug list so the users can take a look at the bugs in the original CM12.1 thread.
I agree to what @LiquidSolstice said.It's not a big deal to build a bunch of ROMs and post them over the development forum.Maintaining them are difficult. It would've been much better if you maintain a single ROM and work with it.Now you have like 3-4 WIP ROMs without proper testing and it seems like you doesn't own the device
Tapped from my ①+②=❸
Sorry if I'm being a douchebag
I maintain all of my ROMs thoroughly.I still say,maintaining is NOT an issue for me.I give out the ROMs to the testers,they test the ROM and report me back with their issues/bugs (if any).I've been building ROMs since 5 months and I like sharing my work with all the people.Yeah,sure thing,anyone can take a look at the ROM building guides out there and make builds and post here,just like me.I've been working on other development projects too (other than building ROMs) but they're not ready yet.You see,interacting with other developers and tech people increases your morale and confidence to do pull yourself deep into the core of the stuff you're working on.For some other guys,I'm just a douchebag who got a good PC with some decent specs and builds all day.Yeah,hell yeah I'm a noob with little development skills,but I'm learning stuff day by day,incorporating and applying that knowledge into my development.I try to maintain all my projects so the users don't get disappointed.I don't have enough money to buy a server so I got a decent PC and start building on it.My only motive is to spread my projects all across the XDA,sharing stuff with people makes me happy.It's just a start,I'm reaching out to the most valuable and efficient developers here in XDA so that I can gain more knowledge.Ofcourse,I am not the greatest dev here but I want to become like one of them.Even though I might be the sh*ttiest maintainer in this whole XDA,but I try to maintain all of my ROMs so that the users don't get disappointed.
@aniket.lamba In other forums,users may ask you to build multiple ROMs and maintain them.But IMO the best way to be a good dev is to properly maintain one good ROM for the community,giving regular updates and interacting with the users.As you know the OPT dev forum will be as popular as the OPO or Nexus ones,the best way to satisfy users is to concentrate on one good ROM and provide your valuable support for it.This is my personal opinion!
Tapped from my ①+②=❸
I respect your opinion but I'd still consider it my way,expanding my base and providing more support of ROMs to the community.I just wanna make sure that nobody makes a buzz about me maintaining multiple ROMs while I build on my little machine.
@aniket.lamba In other forums,users may ask you to build multiple ROMs and maintain them.But IMO the best way to be a good dev is to properly maintain one good ROM for the community,giving regular updates and interacting with the users.As you know the OPT dev forum will be as popular as the OPO or Nexus ones,the best way to satisfy users is to concentrate on one good ROM and provide your valuable support for it.This is my personal opinion!
Click to expand...
Click to collapse
+1
Sooo.. hold on... OP is a copycat and the HW features of the phone are not working ?
Thanks for being supportive to everyone who used my ROMs.Appreciate it!
Thread closed per OP request.

Attention Play device ROM Developers and Maintainers:

Please pay a bit more attention to the reason why most of us bought this phone: https://www.androidauthority.com/motorola-moto-z3-play-review-885207/
Must I stress this? I'm sure I am not the only one getting annoyed by the lack of Moto Mod support in most current Custom Roms.
(Pixel Experience and Lineage 15.1 implementing it the best when it comes to 8.1)
There is even an entire sub redit complaining about this...
I am no developer myself, but here it is laid out on how to make a ROM that supports most Moto Mods, this seemed a bit buried and hard to find, but seems extremely useful as if someone has already done the nitty gritty work:
There is a detailed Mod Porting tutorial at the bottom of this thread:
> https://forum.xda-developers.com/showpost.php?p=72601804&postcount=2 <
And I don't know if this is possible but it would also be great to have something like a flashable zip or base that supported Moto Mods for treble or/GSI ROMS in the future.
If anyone can get a Pie rom working with MODS soon enough, you'll beat Motorola to it. Think about that... you could work for them, because sadly it's something they haven't accomplished yet lol.
This should be in MOTO Z2 PLAY GUIDES, NEWS, & DISCUSSION.
Try looking, it has been explained before why we only have battery mod support. Besides, development is dead, there are no Devs now.
Cupcake 1.5 said:
Try looking, it has been explained before why we only have battery mod support. Besides, development is dead, there are no Devs now.
Click to expand...
Click to collapse
I looked and I found that it is possible to have more than the battery mod support, hence this post. The ROM I am on now, lineage 15.1 (Oreo 8.1 with November security patch)> works with my projector mode also.
Past custom Roms have also supported more than the battery mod.
I hope I don't have to explain the concept of looking to you, there are no Devs currently, development is not dead, they are waiting for/working on Pie. That you would know if you have been looking and reading the forums and posts by Devs.
moonlightdrive said:
This should be in MOTO Z2 PLAY GUIDES, NEWS, & DISCUSSION.
Click to expand...
Click to collapse
Tell me, where is it more likely to be seen by Devs?
MusicAlleyInc said:
I looked and I found that it is possible to have more than the battery mod support, hence this post. The ROM I am on now, lineage 15.1 (Oreo 8.1 with November security patch)> works with my projector mode also.
Past custom Roms have also supported more than the battery mod.
I hope I don't have to explain the concept of looking to you, there are no Devs currently, development is not dead, they are waiting for/working on Pie. That you would know if you have been looking and reading the forums and posts by Devs.
Click to expand...
Click to collapse
For your information, one of the old Devs here said only battery mod for z2 play because the other mods caused too many problems on custom ROMs. Also, nobody is working on pie on xda for z2p. The Devs that where here all left, they are not waiting, they moved on.
Cupcake 1.5 said:
For your information, one of the old Devs here said only battery mod for z2 play because the other mods caused too many problems on custom ROMs. Also, nobody is working on pie on xda for z2p. The Devs that where here all left, they are not waiting, they moved on.
Click to expand...
Click to collapse
Even tho I have proof of the projector mod working very stable on my phone on lineage 15.1 January security update???? And other mods in the link I supplied in the post??? Cool story...
The whole point of this post was to help devs like that accomplish it. I am guessing this is one reason why many give up...You have no idea how incorrect you are obviously, I have read 2 devs for these mod compatible ROMS state they were waiting for Pie. Because 8.1 is sufficiently accomplished now. Waiting= no current activity/posts/8.1 updates. I just technically had a dev here work on lineage 15.1 for me yesterday, compiling the new security update.
Want the link to this best ROM for the phone right now or can you LOOK for it by yourself? Thanks to me it's really not hard to find.
MusicAlleyInc said:
Even tho I have proof of the projector mod working very stable on my phone on lineage 15.1 January security update???? And other mods in the link I supplied in the post??? Cool story...
The whole point of this post was to help devs like that accomplish it. I am guessing this is one reason why many give up...You have no idea how incorrect you are obviously, I have read 3 devs for these mod compatible ROMS state they were waiting for Pie. Because 8.1 is sufficiently accomplished now. Waiting= no current activity/posts/8.1 updates. I just had a dev here work in lineage 15.1 for me yesterday, compiling the new security update.
Want the link to this best ROM for the phone right now or can you LOOK for it by yourself? Thanks to me it's really not hard to find.
Click to expand...
Click to collapse
I was going to respond to your misunderstandings but, had to much of a giggle at your progressive edits to further attack me. Goodbye, no time for you.
Please explain this misunderstanding of mine:
https://forum.xda-developers.com/z2-play/development/rom-lineageos-15-1-t3731228/page42
And look where that got me. 2 stable mods, 8.1 64 bit, January security patch and even a microg version.
Again I will add another screenshot taken from the post about mod compatibility.
...
Fact: A Dev compiled a security update for lineage albus yesterday. Another made a microg variant a few weeks ago.
Fact: the link in this post is how stable mod support can be accomplished.
Cupcake 1.5 said:
Try looking, it has been explained before why we only have battery mod support. Besides, development is dead, there are no Devs now.
Click to expand...
Click to collapse
K.O.
This was your original comment, you were clearly claiming we only have battery mod support now, and why that is.
On a post containing information to why that is not, and how we can achieve more than that.
Like wow...
MusicAlleyInc said:
K.O.
This was your original comment, you were clearly claiming we only have battery mod support now, and why that is.
On a post containing information to why that is not, and how we can achieve more than that.
Like wow...
Click to expand...
Click to collapse
Correct, I was claiming based on the last information I had from a Dev. And you seem to have found the answer, I stand corrected. Finished?
Cupcake 1.5 said:
Correct, I was claiming based on the last information I had from a Dev. And you seem to have found the answer, I stand corrected. Finished?
Click to expand...
Click to collapse
Sure, please enjoy the ROM.
I was initially perturbed mostly because you told me to go look, when I had already spent countless hours looking and finding. Thanks for acknowledging this.
MusicAlleyInc said:
Tell me, where is it more likely to be seen by Devs?
Click to expand...
Click to collapse
It's gonna be more likely to be seen in the right thread section (as now). Otherwise it looks like you believe that you are higher than the rules we all here try to respect (the convenient thing is to keep each section ordered).
Have a nice day. :good:
guys, guuuys !! You done bickering, have you?
Now please have a look back at your posts, they look better, don`t they?
Further inflammatory posts containing disrespectful and useless remarks like "stupid, idiotic, butt-hurt" and so on will be removed and not only edited would also unleash some "respectful" pm`s straight to your inbox.
-=-=-
MusicAlleyInc said:
Tell me, where is it more likely to be seen by Devs?
Click to expand...
Click to collapse
if it is a discussion then it must take place in this section, and "to be more visible" this is up to the level of conversation, what needs to be seen it will be always seen.
-=-=-
Please keep it civil and enjoy the forums.
Thank you!
as long as the topic has drastically changed its direction and no one is interested anymore, I`ll be closing it.
I have nicely requested to keep it civil but it seems that no one cares. @MusicAlleyInc message me please when you think this thread can continue on the topic that has been created and I will reopen it.
Thanks for understanding
-=-=-
thread cleaned once more and reopened @MusicAlleyInc

Categories

Resources