Related
Dear all
Got my HTC HD2 today,Need ur help guys to share best working rom without any bugs,I want to dual boot my HTC HD2 with Windows 6.5 & Android
Thanks in Advance
munishjoshi said:
Dear all
Got my HTC HD2 today,Need ur help guys to share best working rom without any bugs,I want to dual boot my HTC HD2 with Windows 6.5 & Android
Thanks in Advance
Click to expand...
Click to collapse
Congrats bro and welcome aboard.
Just wanted to point out, this is the Dev forum, Q&A going in the General Section.
Anyhow, you Have Sense rom, Sense 2.1 and CM7 (no Sense, other ui such as LaunchPro or ADW).
You got too many choice.
Pick which you want to test first and enjoy flashing once you get addicted.
You could also put more than one Android build on your SD card. So you can test more than one at once without deleted the other.
Whichever you choose, Good luck
PS: Most famous are CM7 builds
Thanks Bro for replying
i m not new into flashing..already flashed so many phone..m already flashing addicted...i saw so many roms in this forums...i just would like to know that which one is bugs freeee
Thanks
munishjoshi said:
i m not new into flashing..already flashed so many phone..m already flashing addicted...i saw so many roms in this forums...i just would like to know that which one is bugs freeee
Click to expand...
Click to collapse
Anyone who knows anything about software(or real life for the matter) will tell you - "it does not exist"
You will have a better luck asking what ROMs people are using and would recommend.
it's hard to say which rom doesnt have bugs... try first. i like the rom from MCCM HD 4.0. i'm using it at this time.
I can personally recommend the AmeriCan Android rom, been using it past months and updates makes it better and better ^^
Personally though, uninstall the NetFlix thing right after putting the rom on, it made my HD2 uber slow, the second it was gone, it was back to super speedy
Hi, could somebody please link me the thread where the multiple versions of abdroid is expaned? Thanks
Sent from my GT-P1000 using XDA Premium App
Just buy a HTC phone with Android like DHD.. That is not any bug.
I personally like and use JAGUARMIUI 5.
Sent from my HTC HD2 using XDA App
manhktqd said:
Just buy a HTC phone with Android like DHD.. That is not any bug.
Click to expand...
Click to collapse
I´ve been running AmeriCanAndroid GB2.3.3 on my HD2 for over 2 months now and have less bugs than my friend with a stock (updated) DHD.
I could recommend this one and version 2.3.4. I suggest you try that one and give it a go. I can't imagine that this ROM is not good. Be sure to read the last 10 pages of the ROM thread to be sure. I think that´s the best way to check if the latest version doesn´t have any significant bugs. Good luck!
American android. You wont look back
Sent from my GT-P1000 using XDA Premium App
I have used the following SD Builds during the last 3-4 months. Do not want to switch to NAND as I still have some use for WM. Even tried some of the older RAM builds like Darkstone's SuperRAM Froyo. I am giving my preferences below and check my sig for other info.
1. AmericanAndroid, have tried almost every build since it came out.
http://forum.xda-developers.com/showthread.php?t=957652
The two most recent Builds, 05172011, 05192011 and 05212011 have given me the most issues with significant screen lag and persistent wait periods when using these. I tried them with three different SD cards (4G C2, 8G C4, 8G C6) and still had issues. I am now back to the 05032011 Build which runs superbly on two different SD cards (4G C2, 8G C4). I was surprised to find that the Class 2 SD card was the smoothest although I am sure there are variations based on other factors beyond the scope of my intelligence. Everything works like a charm on 05032011 build except Market acts up sometimes. Follow the link for all Builds by date here: http://uploading.com/linklists/debamfea/ACA
2. May 14 BOYPPC Build
http://forum.xda-developers.com/showthread.php?t=970542
is good too but as is usual we all have our personal preferences and I feel more comfortable with AmericanAndroid. This would be my backup if AmericanAndroid goes loopy.
3. Have used MccMBoxMaX Build too.
http://forum.xda-developers.com/showthread.php?t=1038694
I have kept it on a separate SD just in case. Pretty solid build but I am sticking to AmericanAndroid for the time being.
I have tried at least 8 releases for the past 6 mths. From one chef to another chef. But for the past 3 mths, I m using MCCM SE V3.3 . I must say it is stable n fluid. I have also recently tried other GB version from MCCM n other chefs..... but I guess its not really that stable yet. Probably someone can recommend me a stable GB version. Would LOVE to get my hand on one of em.
this isn't to mislead anyone...i feel i've gotta say.....mccm doesn't compile his builds from source. his is completely reliant on switching files around....i have yet to see anything i'd trust for a second from him. he's had previous problems with actual chef's and even developers because he breaks xda's rules and steals builds....this isn't just a warren dislikes mccm thing.
use those builds if you wish......but those very builds are 100% reliant on the taking of someone elses compiled source. if he at least built from source code, he'd get some credibility from me.
warrenb213 said:
this isn't to mislead anyone...i feel i've gotta say.....mccm doesn't compile his builds from source. his is completely reliant on switching files around....i have yet to see anything i'd trust for a second from him. he's had previous problems with actual chef's and even developers because he breaks xda's rules and steals builds....this isn't just a warren dislikes mccm thing.
use those builds if you wish......but those very builds are 100% reliant on the taking of someone elses compiled source. if he at least built from source code, he'd get some credibility from me.
Click to expand...
Click to collapse
@warrenb213, thx for letting us know about this issue. I wasn't aware of it but will treat MccM's work cautiously. I'm going to head over to the AmericanAndroid thread to give you thanks which I should have done some time ago.
warrenb213 said:
this isn't to mislead anyone...i feel i've gotta say.....mccm doesn't compile his builds from source. his is completely reliant on switching files around....i have yet to see anything i'd trust for a second from him. he's had previous problems with actual chef's and even developers because he breaks xda's rules and steals builds....this isn't just a warren dislikes mccm thing.
use those builds if you wish......but those very builds are 100% reliant on the taking of someone elses compiled source. if he at least built from source code, he'd get some credibility from me.
Click to expand...
Click to collapse
Hi... Warrenb long time no see. How can u give comments without thinking . Any proof that i stealing your build ? In xda rules u can post build if the other dev give u permissions . Just after giving permissions then give fake info to Moderator after u realized that i better tweaker than u . I got ban because of warez , big 'thanks' to u . But at the end just live with it . If u want to give comment think carefully please.
Edit: This is your comment on 'NexusHD2-Gingerbread V2.7 [GRJ22/Android2.3.4][Kernel:tytung_r10]' thread :
Warrenb213
14th May 2011, 09:51 PM
ReTweet this post# 24
I feel like I've got to ask....
Did Tytung approve of this SD-build? I ask because Tytung has experience in this already, I don't know why he/she wouldn't convert the build themselves? lol
Click to expand...
Click to collapse
This is the reply from the man him self :
tytung
15th May 2011, 10:37 AM
ReTweet this post# 29
Originally Posted by warrenb213
I feel like I've got to ask....
Did Tytung approve of this SD-build? I ask because Tytung has experience in this already, I don't know why he/she wouldn't convert the build themselves? lol
Yes, I approve it.
Thanks to HaPeWe for the time and effort to convert it from NAND ROM.
I have no time to install WM just in order to test SD build.
And I won't like to release a SD version without testing.
That's why I don't release it myself.
Click to expand...
Click to collapse
OH man ... feel hurt right
mccmjoon76 said:
Hi... Warrenb long time no see. How can u give comments without thinking . Any proof that i stealing your build ? In xda rules u can post build if the other dev give u permissions . Just after giving permissions then give fake info to Moderator after u realized that i better tweaker than u . I got ban because of warez , big 'thanks' to u . But at the end just live with it . If u want to give comment think carefully please.
Edit: This is your comment on 'NexusHD2-Gingerbread V2.7 [GRJ22/Android2.3.4][Kernel:tytung_r10]' thread :
This is the reply from the man him self :
OH man ... feel hurt right
Click to expand...
Click to collapse
You were banned for good reason, not once....but twice.
You are NOT CURRENTLY stealing the ACA build because the mod's gave you the choice to take it down or be banned. Wouldn't get too confident. Most of the time, including in our case, you acted before getting permission. I wouldn't be surprised to find out most of your "builds" are the same.
If Tytung approved one of your "hack" builds then that is one example where you did in fact get permission.
What you do though in messing with builds has been observed as quite sloppy, and has proved you to be more of a "theme" applier than anything. I have never seen evidence of anything more than a theme applied. You never have shown source code for the majority of your projects, and when you do it's typically been to a place of no actual value for other folks to check out the source. You can't post people to look @ CM code when your using another dev's compiled source which stems AWAY from the stock CM repo's, for example. But the mod's have been lenient in that regard.
I think carefully before I respond, each and every time. I've not said anything which you could refute, mccm. Or was there something I said more specifically about your technique which you wanted to address?
Tweaker? Sir, if that is what you are then we should give folks like you your own subforum under here, called "Tweaked builds from people that have never compiled a build themselves." ACA is a compiled AND tweaked build, and our files can be found in builds across the HD2 forums.
Any developer which would accept the idea that a fellow not building from source code could make their ROM better than they could themselves, would be kidding themselves and they'd know it.
Nuff said, moving on.
warrenb213 said:
You were banned for good reason, not once....but twice.
You are NOT CURRENTLY stealing the ACA build because the mod's gave you the choice to take it down or be banned. Wouldn't get too confident. Most of the time, including in our case, you acted before getting permission. I wouldn't be surprised to find out most of your "builds" are the same.
If Tytung approved one of your "hack" builds then that is one example where you did in fact get permission.
What you do though in messing with builds has been observed as quite sloppy, and has proved you to be more of a "theme" applier than anything. I have never seen evidence of anything more than a theme applied. You never have shown source code for the majority of your projects, and when you do it's typically been to a place of no actual value for other folks to check out the source. You can't post people to look @ CM code when your using another dev's compiled source which stems AWAY from the stock CM repo's, for example. But the mod's have been lenient in that regard.
I think carefully before I respond, each and every time. I've not said anything which you could refute, mccm. Or was there something I said more specifically about your technique which you wanted to address?
Tweaker? Sir, if that is what you are then we should give folks like you your own subforum under here, called "Tweaked builds from people that have never compiled a build themselves." ACA is a compiled AND tweaked build, and our files can be found in builds across the HD2 forums.
Any developer which would accept the idea that a fellow not building from source code could make their ROM better than they could themselves, would be kidding themselves and they'd know it.
Nuff said, moving on.
Click to expand...
Click to collapse
Your right man. Move on! Stop interfere the members that want to share about build.. let them judge by their own.
Banned twice! I make history
U should know the ROM or Build is come from Google we are making it works for HD2. U your self are not builder. Or else u won't be here. U will working with Google.
XDA site is about sharing. I don't mind some one here can come out better build then me. i congrat them. Cause members can enjoy the build daily..
By the way,I being thinking to post up my GB build back here again it will be nice right?
Sent from my HD2 Gingerbread using XDA App
I see this has turned into a bad conversation.
I don't know why you need to quarrel guys, I mean I have no business of meddling but since you've startet arguing I feel I should add a small opinion, knowing I don't have much right to do so:
MCCM's builds don't even run on my device, and Warren's ones work for 5 minutes then corrupt my SD! and yes that includes AmDroid.
it's not SD-related since I'm already using a build that's stable enough to handle 3 days of constant work on the same card.
Both of you guys are great in what they do really, considering the number of users you serve, but I don't think a public thread is the right place to argue. PMs were created for a reason, and there are MODs to complain to and stuff like that.
In my opinion, no matter who's right here, you both are looking bad.
HD2one
It is an older build, but very stable. I get 2970 on quadrant so it takes full advantage of the HD2's power. I've tried new builds, but i always come back.
I am a long time ROMer, mainly sticking to MIUI, as I like the interface. I like to try and test many ROMs, as I'm sure many people here do.
I am finding it very frustrating that every release seems to have some critical flaw. I tell myself not to worry, that the next release will fix it, and usually it does. And brings in a new bug. Every release seems to fix something and break something else. Things that are most often broken:
- Call recording only records one side of the conversation
- WiFi tethering
- Camera issues
- Theme handling
I used to use Galnet for a while, as he paid a lot of attention to stability and bug fixing rather than inclusion of bleeding edge kernels or untested mod packages. Unfortunately, I have not been able to find another ROM cook like that since he left the scene. MIUI.us is my current ROM of choice, but they seem to be more a loosely knit group some of whom care about stability, others care more about givning you an AROMA installer that allows you to choose between half a dozen 0-day kernels, none of which have much field testing.
Is it really that hard to fix all of these things all at once? Is ROM cooking really that much of a totally random game of whack-a-mole? Are there any ROM devs out there that actually pay attention to basic functionality and stability of the system rather than switching to some new, bleeding edge kernel package that came out 27 seconds ago and therefore must be included right now?
mrnaz said:
Is it really that hard to fix all of these things all at once? Is ROM cooking really that much of a totally random game of whack-a-mole?
Click to expand...
Click to collapse
NOPE. It is easy. and you have my personal permission (I think that most devs would agree with me) to cook the ROM with the properties you want, as well as fixes.
No one wants to argue with you, and anyone is accepting your position that it is so easy.
Therefore - do it for yourself:fingers-crossed:
Samsung doesn't release all source codes for the hardware. To develop the whole thing from scratch, you'd probably have to write codes again for these, as the original code would only work with other Sammy-based codes. It's kinda difficult expecting it to work first time round when you're building from scratch.. At least this is my guess.
MIUI is based in CM, so would include any bugs that CM has. If you want stability, use one of the Sammy custom roms.
spamtrash said:
NOPE. It is easy. and you have my personal permission (I think that most devs would agree with me) to cook the ROM with the properties you want, as well as fixes.
No one wants to argue with you, and anyone is accepting your position that it is so easy.
Therefore - do it for yourself:fingers-crossed:
Click to expand...
Click to collapse
So what you're saying is that it is easy, but nobody has done it because I'm the only one that wants a working, stable phone.
Are you serious, or on drugs?
Dude devs put a lot of hours and hard work into making custom ROMS, they don't get paid (apart from donations) and when someone comes along and says these things it is very disrespectful.
I'm sure these bugs annoy the devs a lot more than they annoy you!
If you want a perfect, stable, super ROM then make one.
Sent from my GT-I9300 using xda app-developers app
mrnaz said:
So what you're saying is that it is easy, but nobody has done it because I'm the only one that wants a working, stable phone.
Are you serious, or on drugs?
Click to expand...
Click to collapse
YOU have stated that it is EASY. YOU need the changes you mentioned.
So, if it is so easy, but you do not want to do it - using your friendly wording:
are you too stupid or too lazy?
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.
Please Start work on CM12.1 or CM13 - Fully working - OxygenOS is soooo Basic
I know there are partially working versions out there, but we need the Laser AF and FP working - These two functions made me buy the phone.
Anyone know why we don't have the same level of support on the OPT as the OPO?
hahahahahaha.
Man, please, you don't know what you're talking about. So wait and see whats going on. And stop such stupid Threads.
Have a nice day
Then consider learning to build your own ROMs...?
We have a few people working on it, redirect there (Ex: http://forum.xda-developers.com/oneplus-2/general/cm-13-oneplus-t3237443) , It does no good for the forums to post useless threads demanding the newest version of Android for your needs.
Consider doing any of the above, but this thread should be closed.
Take care.
gaz_0001 said:
Please Start work on CM12.1 or CM13 - Fully working - OxygenOS is soooo Basic
I know there are partially working versions out there, but we need the Laser AF and FP working - These two functions made me buy the phone.
Anyone know why we don't have the same level of support on the OPT as the OPO?
Click to expand...
Click to collapse
Already ive seen developers working it there's an another thread where they are discussing on cm13 they are getting errors but they are working hard to fix them if they continue their work we can have a bootable rom soon
Opo is very old and its sources are available opt has been launched just months ago and no fingerprint sources yet however all we need is one rom wuth fp fixed then every other thing gets it as well
gaz_0001 said:
Please Start work on CM12.1 or CM13 - Fully working - OxygenOS is soooo Basic
I know there are partially working versions out there, but we need the Laser AF and FP working - These two functions made me buy the phone.
Anyone know why we don't have the same level of support on the OPT as the OPO?
Click to expand...
Click to collapse
Seriously? You made a thread asking someone else to start development on a ROM? I guess some people tend to forget that developers do this work mostly as a hobby, in their free time, with no compensation outside of any donations they might receive. As suggested above, if you're so adamant about this, feel free to learn development for yourself and build your own ROM. Please do not make any more threads of this nature.
Thread closed
Moderator Please Delete!
move it to development section
Hi !!
On the latest build, no Ril works... Fixing it as I write ... Also, Hardware keys don't work (fixed and coming in next build)
I am not creating thread as it is not official
Naman Bhalla said:
Hi !!
On the latest build, no Ril works... Fixing it as I write ... Also, Hardware keys don't work (fixed and coming in next build)
I am not creating thread as it is not official
Click to expand...
Click to collapse
Ok man.?
So we can expect RIL and hardware keys in next build?
It has layers right? If I'm not wrong....
All bugs reported till now, fixed. Build coming very soon.
#staybroken
Used this on my OPO. Time to try on my OPT.
Broken-v4.2-oneplus2-6.0.1-UNOFFICIAL-20160216.zip
The new one with all fixes you told?
https://www.androidfilehost.com/?fid=24421527759880262
vergilbt said:
Broken-v4.2-oneplus2-6.0.1-UNOFFICIAL-20160216.zip
The new one with all fixes you told?
https://www.androidfilehost.com/?fid=24421527759880262
Click to expand...
Click to collapse
physical keys not working on this build.
Is this Broken AF?? Pun intended. Lel.
Inb4 someone asks for what's broken in this ROM, OP can gladly say it is literally EVERYTHING.
Happy to see a new ROM emerging though. Props!
Sent from my ONE A2003 using Tapatalk
Sim Card
Naman Bhalla said:
All bugs reported till now, fixed. Build coming very soon.
Click to expand...
Click to collapse
Rom does not recognise my sim card, can you tell me how to fix please.
walkim61 said:
Rom does not recognise my sim card, can you tell me how to fix please.
Click to expand...
Click to collapse
I don't think new build is out yet.
Sent from my ONE A2003 using Tapatalk
First of all, let me state that I am thrilled to see Broken in development for the OP2, the lack of which was probably the second biggest reason I've refrained from switching to my OP2 as a daily driver (the first being a serious lack of decent kernel development). So what I'm about to say, I'm only saying due to my desire to see Broken development for the OP2 continue and my faith in @Naman Bhalla's ability.
I would highly recommend the OP request this thread to be closed to prevent a war from breaking out. @Naman Bhalla has already acknowledged that there was a reason for him to omit making a thread, and that reason is a good one. I reckon it'd be wise to respect that decision for the benefit of all of us who enjoy this ROM despite it's territorial lead dev team.
As many of you may already be aware, the BrokenOS team tend not to take kindly to threads created by unofficial device maintainers, if at all. Broken build distribution is more or less relegated to the BrokenOS GPlus group and dysfunctionalroms.net by their own choosing and I would recommend that it remain there (or be posted, if not already) and that we leave it in Naman's hands to usher the development of this ROM along through the proper channels with the consent of Broken's dev team which he seems to be well on his way of doing.
It's probably the best shot we have of ensuring that Naman's efforts are not lost amidst a flame war as well as his potential recognition as an official maintainer going forward. Again, I say this considering the official dev's contempt for unofficial build threads, the oneplus community to an extent, and most if all xda in general. On the flip side, BrokenOS threads on XDA have a long-history of not ending so well.
While I, and I'm sure many of you, are less than pleased and may not agree with some of the actions and stances taken by BrokenOS' temperamental team in the past.. many of us also recognize it to be a stellar ROM all the same. For those of us, the best course of action here would be to respect the content creator's wish of how things of this nature should be handled.
return.of.octobot said:
First of all, let me state that I am thrilled to see Broken in development for the OP2, the lack of which was probably the second biggest reason I've refrained from switching to my OP2 as a daily driver (the first being a serious lack of decent kernel development). So what I'm about to say, I'm only saying due to my desire to see Broken development for the OP2 continue and my faith in @Naman Bhalla's ability.
I would highly recommend the OP request this thread to be closed to prevent a war from breaking out. @Naman Bhalla has already acknowledged that there was a reason for him to omit making a thread, and that reason is a good one. I reckon it'd be wise to respect that decision for the benefit of all of us who enjoy this ROM despite it's territorial lead dev team.
As many of you may already be aware, the BrokenOS team tend not to take kindly to threads created by unofficial device maintainers, if at all. Broken build distribution is more or less relegated to the BrokenOS GPlus group and dysfunctionalroms.net by their own choosing and I would recommend that it remain there (or be posted, if not already) and that we leave it in Naman's hands to usher the development of this ROM along through the proper channels with the consent of Broken's dev team which he seems to be well on his way of doing.
It's probably the best shot we have of ensuring that Naman's efforts are not lost amidst a flame war as well as his potential recognition as an official maintainer going forward. Again, I say this considering the official dev's contempt for unofficial build threads, the oneplus community to an extent, and most if all xda in general. On the flip side, BrokenOS threads on XDA have a long-history of not ending so well.
While I, and I'm sure many of you, are less than pleased and may not agree with some of the actions and stances taken by BrokenOS' temperamental team in the past.. many of us also recognize it to be a stellar ROM all the same. For those of us, the best course of action here would be to respect the content creator's wish of how things of this nature should be handled.
Click to expand...
Click to collapse
Sorry for late reply but you mean I should close the thread?
If yes then ok
LOL9988 said:
Sorry for late reply but you mean I should close the thread?
If yes then ok
Click to expand...
Click to collapse
Yeah that would be better