Database Info

The past is in the past!

Dear XDA and XDA fans..!
I would like to open up the discussion of Galnet MIUI here on XDA, and hopefully get adult responses, instead of the normal we can't talk about Galnet here.
Over the last year XDA and Galnet have had a battle over what is right and what is wrong, and users of XDA being confused about why Galnet is not allowed to be talked about considering other MIUI released can be posted without any issue.
The true factors of the matter is that ALL SGS I9000 MIUI roms in general should be banned from XDA, as the base rom which was used to continue the development was one developed by Galnet (MIUI V4 1.12.19 Dated 19th December 2011). However I'm not worried about who uses my work, it's great to see I've allowed a development to grow and be used daily.
This was the turning point for MIUI v4 on the I9000, thus allow developers to work, repair and release better builds for the benefit of the end users to enjoy, the whole point to XDA..!
Then not forgetting our major break through with ICS which was printed on the XDA home page: http://www.xda-developers.com/developments/ice-cream-sandwich-ported-to-the-samsung-galaxy-s/ This brought light and hope into users that ICS could run on the I9000, and leap frogged the I9000 ICS development, something of which can't be denied..!
In reality I (GALNET), do not do this for money making, I do this as a hobby, and my means of collecting cash from people may have been untoward, however on being shown that this wasn't acceptable, I changed my thinking, and also redesigned the feel and look of our website in order to remove what seemed like a forced payment option, which was never meant to be..! I'm taking about the Groupies section of our site, this was removed and banned, all users were treated the same, and as you all know the roms came flying out the door weekly, without the need for any payment whatsoever...!!!! It was all funded with my cash, without quibbles.
I also used custom kernels as the believe was MIUI didn't release the source for the Kernels they were using (Breach of the GPL), however if any of the Moderation team took the time to check, every kernel MIUI used, excluding the MI-One was either a CM kernel or a stock kernel which obliged with the GPL rules. This is still true with MIUI Version 4.
At it's peek Mamboo, Currydude and Galnet MIUI was brining over 1,000 visitors an hour (Maybe more) on the XDA boards, it was the most active board on XDA, and was considered the best rom for the I9000 excluding CM7. The developments, rewrites and tweaks were taken and used by other developers to better their roms, same with help modifying the Kernels (Vorbeth) and source being made available, again never breaching the GPL rules.
I think it's time that the XDA management took a look at what Galnet (I) have done for the community and android development in a whole on the Samsung devices, and accept the fact that the past is in the past. I've moved on, and so has everyone else. No matter how hard you try to close a Galnet thread, another one appears (Not by me, nor do I ask users to post) as the users feel it should be shared.
I ask that all moderators think seriously about what I have done for the community, and forget the STUPID groupies arguments, is constantly closing a thread down, or blocking the word Galnet the mature thing to do?
I accept and apologise for anything that I have done, so can't XDA do the same?
My Two Cents,
Mathew.

I'm having a hard time comprehending this. You're apologizing for people admiring your work?
Sent from my iPad using Tapatalk HD

KayxGee1 said:
I'm having a hard time comprehending this. You're apologizing for people admiring your work?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
No I'm apologising for any rules that I may have broken.

It's sad to see the Galnet website nowadays Matthew. I don't know anything about these 'problems', but Galnet MIUI was by far the best equipped and most stable variant of GB MIUI on my HTC Desire S.
Hopefully one day you will be back and I'll be able to see what you can do with ICS.

tldr
Sent from my Samsung Galaxy S III via Tapatalk II.

Well I hope that everything gets resolved. As SimonTS said above, Galnet has been the most stable MIUI I've run, and in fact the most stable Rom period of all that I've used. I've been running MIUI V4 lately because of some of the little UI tweaks but still nothing beats Galnet in terms of overall usefulness. It would be great if you could do some work on V4 for the community.

Moved to proper section

So any moderators have any feedback?
It would be nice to know if xda accept the above and allow me to post my modified roms.
Sent from my GT-I9300 using Tapatalk 2

Can someone explain the difference between all the aokp builds?

Sorry if this was answered already. At the moment there is 4 you could choose from. I've read countless posts in each thread but that may be the reason why this goes over my head. I'm just trying to understand the difference between them all. I also thought I read that xoomdev said the devs couldn't make their own builds and could only release the official bricks. I know this was answered over in one if the rootz threads too but there's so many posts it would be like finding a needle in a haystack. So if anyone has the time and would like to elaborate, thank you in advance.

I am confused by this as well - it seems like there are multiple aokp and CM10 builds going around.

Very simply put you have the official builds of each which is how the main developers want the ROM to act/feel/look/etc... They also provide the code for these builds so any other developers that want to can add/subtract little tweaks here and there to make it how THEY want it to act/feel/look/etc... And that is what the unofficial builds are, "aftermarket" developers tweaking it.
EDIT: Also, if you have a bug on the official build of either then there's a 99% chance it's on all the other ones too.

Brian Gove said:
Very simply put you have the official builds of each which is how the main developers want the ROM to act/feel/look/etc... They also provide the code for these builds so any other developers that want to can add/subtract little tweaks here and there to make it how THEY want it to act/feel/look/etc... And that is what the unofficial builds are, "aftermarket" developers tweaking it.
EDIT: Also, if you have a bug on the official build of either then there's a 99% chance it's on all the other ones too.
Click to expand...
Click to collapse
Thank you!

Unofficial CM10 - IMPORTANT - Please Read.

As im sure most of you all know, I have locked the Unofficial CM10 thread. It isnt because of one person or one event, but something that has been coming for a long time. I have been stressing myself with this build and making sure that everyone was happy and doing pretty much everything i could do, but it didnt seem to be enough. While i appreciate the feedback, it is very disappointing to release cm10.1 when pretty much no other phones have released it (due to the lack of source merged and changes necessary for jellybean 4.2.1) and have nothing but post after post of this doesnt work and this doesnt look right and this is running horrible and blah blah blah even after i made it absolutely clear time after time that there may be issues since there is alot of source changes that are missing. You would think that since i took the time to merge the needed changes and work tirelessly to make changes and get the changes merged into our device/kernel trees to get CM 10.1 built and IMO running nicely, there would be alot of positive feedback and alot of understanding from the community that there may be little issues here and there since not everything was completely merged in on the CM side, but that was not the case as everyone expects perfection right and nothing else. Anyways, with that said, Building CM10 was becoming more of a job instead of something fun that i loved to do. And believe me... I havent had nearly enough donations to be ok with considering this a job... Nor do i expect alot of donations and for those of you who have supported me, I greatly appreciate it. I WILL CONTINUE to build CM10 and posting new builds on my goo page found HERE. I will not however be unlocking the CM10 thread. So... If you like my work and like my builds, keep an eye on my goo page and download when you are notified there is an update. If you like the build, great... if not, flash something else.

scott.hart.bti said:
As im sure most of you all know, I have locked the Unofficial CM10 thread. It isnt because of one person or one event, but something that has been coming for a long time. I have been stressing myself with this build and making sure that everyone was happy and doing pretty much everything i could do, but it didnt seem to be enough. While i appreciate the feedback, it is very disappointing to release cm10.1 when pretty much no other phones have released it (due to the lack of source merged and changes necessary for jellybean 4.2.1) and have nothing but post after post of this doesnt work and this doesnt look right and this is running horrible and blah blah blah even after i made it absolutely clear time after time that there may be issues since there is alot of source changes that are missing. You would think that since i took the time to merge the needed changes and work tirelessly to make changes and get the changes merged into our device/kernel trees to get CM 10.1 built and IMO running nicely, there would be alot of positive feedback and alot of understanding from the community that there may be little issues here and there since not everything was completely merged in on the CM side, but that was not the case as everyone expects perfection right and nothing else. Anyways, with that said, Building CM10 was becoming more of a job instead of something fun that i loved to do. And believe me... I havent had nearly enough donations to be ok with considering this a job... Nor do i expect alot of donations and for those of you who have supported me, I greatly appreciate it. I WILL CONTINUE to build CM10 and posting new builds on my goo page found HERE. I will not however be unlocking the CM10 thread. So... If you like my work and like my builds, keep an eye on my goo page and download when you are notified there is an update. If you like the build, great... if not, flash something else.
Click to expand...
Click to collapse
you have a charachter flaw. you're a people pleaser. once you get over that and become a true asshole you will be much happier in life.

Dani897 said:
you have a charachter flaw. you're a people pleaser. once you get over that and become a true asshole you will be much happier in life.
Click to expand...
Click to collapse
Lol! So true!
Sent from my SGH-I997 using xda app-developers app

Just wanted to put my two cents in...I've been an avid user of the roms from this site for quite awhile now & have never felt the need to register because any issues I've ever had,I've been able to rectify with some searching or have been on roms that have clearly stated they were beta's & expected to have flaws. That being said...after watching what happened on your infuse board, I just wanted to let you know the fact that you're continuing to develop & keep our phones updated with the best features gave me the first true reason to register so I could say thanks...
Sent from my SGH-I997 using xda app-developers app

Thank You.

I don't blame Scott for having the thread closed, not one bit.
And Dani is correct, Scott's character flaw is only that he's missing the "asshole" gene that some tend to have.
Now on to the good part...
I'm getting back into the swing of things as far as porting and development goes. My first attempt is going to be a nearly pure AOSP build using Aries repos and some Maguro/Takju code base, with parts from the most recent CM10.1 base. I have an idea of what I want to incorporate, but it should be light and clean, with a smooth interface.
Scott, I will be in touch with you shortly on this, as I need to finish and finalize my SDK installs and get everything going correctly for a first build.

Just checked Scotts goo link. Can I safely assume the development continues? If so hallelujah the infuse lives on.
Sent from my SGH-I997 using xda app-developers app

Most of the people that posted just wanted insight on their issues. Personally, I posted there because I felt I wasn't getting any response in the Q&A thread.
I think we should learn from the miscommunication.
One of the bigger problems we faced was that the build thread was the most responsive place to get an answer, and the bugs people had weren't clearly documented somewhere (you can't tell someone to search 500+ pages, find a bug, match it to their build, etc) so they could find and know NOT to post about it.
Going forward, maybe we can have:
Build thread- keep updated on the status of the build
Bug thread- to review / report the current build bugs
Q&A thread- how do I rotate the screen, why is this doing that, etc
Thoughts?

hattrickinc said:
Most of the people that posted just wanted insight on their issues. Personally, I posted there because I felt I wasn't getting any response in the Q&A thread.
I think we should learn from the miscommunication.
One of the bigger problems we faced was that the build thread was the most responsive place to get an answer, and the bugs people had weren't clearly documented somewhere (you can't tell someone to search 500+ pages, find a bug, match it to their build, etc) so they could find and know NOT to post about it.
Going forward, maybe we can have:
Build thread- keep updated on the status of the build
Bug thread- to review / report the current build bugs
Q&A thread- how do I rotate the screen, why is this doing that, etc
Thoughts?
Click to expand...
Click to collapse
But Scott specifically asked multiple times not to post bugs on the 4.2/cm10.1 releases due to the fact that source is still being merged -cm said themselves that the 4.2 code would be buggy and that you probably wouldn't be able to build anything with it...for the most part Scott proved both of those wrong
However I do like the idea of the three threads
Sent from my HTC Holiday using Tapatalk 2

openwheelracing said:
Just checked Scotts goo link. Can I safely assume the development continues? If so hallelujah the infuse lives on.
Click to expand...
Click to collapse
scott.hart.bti said:
I WILL CONTINUE to build CM10 and posting new builds on my goo page found HERE. I will not however be unlocking the CM10 thread. So... If you like my work and like my builds, keep an eye on my goo page and download when you are notified there is an update. If you like the build, great... if not, flash something else.
Click to expand...
Click to collapse
Yes, he will keep developing, but don't expect to see updates on this forum, which is a shame. His CM10 thread was actually the only reason I got on XDA.

Thanks for the update, Scott. Don't let the drama llamas get you down
Sent from my SGH-I997 using xda app-developers app

hattrickinc said:
Most of the people that posted just wanted insight on their issues. Personally, I posted there because I felt I wasn't getting any response in the Q&A thread.
I think we should learn from the miscommunication.
One of the bigger problems we faced was that the build thread was the most responsive place to get an answer, and the bugs people had weren't clearly documented somewhere (you can't tell someone to search 500+ pages, find a bug, match it to their build, etc) so they could find and know NOT to post about it.
Going forward, maybe we can have:
Build thread- keep updated on the status of the build
Bug thread- to review / report the current build bugs
Q&A thread- how do I rotate the screen, why is this doing that, etc
Thoughts?
Click to expand...
Click to collapse
For the most part I agree with you. Its why I probably pissed a bunch of people off defending the late comers and those that just don't know about logcats and such.
However, it was stated multiple times by not just Scott but the more senior and knowledgeable members that the 4.2 was going to have problems.
I agree searching through 1000 plus posts can be a daunting task and maybe I just don't have a life but I've done it for every ICS/JB rom I've flashed.. But I was there at the beginning of that development so it made it easier. But you didn't have to read more than 2 pages between warnings for the 4.2.
I'm on Scott's side on this one.
If nothing else click on the op's profile and just read all their posts.
Personally I think only devs should be allowed to post on a dev thread but I don't see that happening anytime soon.
Sent from my SGH-I997 using xda app-developers app

I agree. I think there should be a minimum post count of 100 and a requirement to agree to a separate 'contract' to post in dev. threads. I read dev threads to find out what's going on in development not the rubbish that appears in most dev threads. The infuse forums have been fairly tolerant of this kind of thing. Other forums on xda, much less so.
Sent from my SGH-I997 using xda app-developers app

Changelog
I think another part of the problem is that very little actual development discussion happens here. It seems that people release their stuff here, and respond to bug reports, but that's about it. You can learn a lot about Linux by reading the archives of the Linux Kernel Mailing List (LKML). It's not quite the same situation here, learning about android is much harder (i have yet to find an android equivalent for the LKML)
Anyway, Thanks for continuing development! Will you be posting a change log between releases? I just like to know what I'm flashing ahead of time
Thanks,
woody

Scotts just released CM10.1 on goomanager 12/10 build go check it out
Sent from my SGH-I997 using xda app-developers app

Scott,
Glad to see you will be still be developing. Will there be some type of change log somewhere that we can view? I agree with some of the past. 500 pages of posts to read/search is alot. possibly a better brake down would have keep people posting in the correct places. Also with the 4.2 merge MY opionion would have been to make a separate thread as the last 4.1.2 was stable and really usable as its still my current daily. If the items arent merged maybe it isnt a good idea to even make a realease unless its to a few beta testers. That way 100s of people dont whine and complain about known or dumb issues.
Either way keeep up the good work.

Not sure how it would be accomplished, but a good idea would be to remove all posts from the cm10 thread and only scott could post in it (updates/changelog).
I have no idea how feasible that would be though.

Many thanks to scott
Hi scott, I never felt the need to comment in your thread because I never had any problems with your ROM.
But now I feel the need to comment here to express my gratitude for all the hard work that you have put into this ROM.
Your ROM is the first one that I tried, and also the best one I've seen/used. I'm VERY glad that you will continue your work for the Infuse.
Again, I thank you for your work, and I will be looking forward to future updates!

UnhoIy said:
His CM10 thread was actually the only reason I got on XDA.
Click to expand...
Click to collapse
This^
hovin1988 said:
Hi scott, I never felt the need to comment in your thread because I never had any problems with your ROM.
But now I feel the need to comment here to express my gratitude for all the hard work that you have put into this ROM.
Your ROM is the first one that I tried, and also the best one I've seen/used. I'm VERY glad that you will continue your work for the Infuse.
Again, I thank you for your work, and I will be looking forward to future updates!
Click to expand...
Click to collapse
And this^
I generally just read through the thread reading peoples issues if i ran into one rather than post. Issues were always sorted out if i kept reading. But thanks for all your hard work in creating roms, I know i'd be really bad off without them :good:

I think the communication and forum issues are simply a result of using a forum for "developer collaboration". Then to top it off, many are using tapatalk, which has the most useless search feature ever. I've heard the argument that a proper browser should be used, but many just won't.
As long as a forum is used for xda development, it will continue to be more like a ROM forum than anything else intended without ridiculous amounts of moderation (even judicious use of temp bans without warning).
Forums are good for arguing lol. Bugtrackers are good for tracking bugs, especially since they are easy to police. If you want feedback as well, make a special category for that. Duplicates and invalid reports can be easily identified and marked as such. For all other forums(general, q&a, accessories, etc.) a forum makes sense to me. For the development forum, a forum, IMO, makes little sense.
If the forum format is used in order to foster community, fine. You can expect a lot of drama, arguing, complaining, and everything else that goes along with it.
Just my opinion. I could be completely wrong.
Sent from my SGH-I997 using xda app-developers app lol

[ROM][AOSP][Nightly/Release] CarbonRom KitKat [d2vzw]

About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
​
XDA:DevDB Information
[ROM][AOSP][Nightly/Release] CarbonRom KitKat [d2vzw], ROM for the Verizon Samsung Galaxy S III
Contributors
CarbonDev, BigShotRob22
ROM OS Version: 4.4.x KitKat
Based On: AOSP
Version Information
Status: Beta
Created 2014-02-03
Last Updated 2014-06-07

Reserved

Reserved

I love you guys....

Good to see. Will be flashing this tonight. Thanks Carbon.

Finally! Thanks Team Carbon!

Where is dark carbon?

Just leaving my finger prints here real quick...
Sent from my SCH-I535 using Tapatalk

Love the Rom, can't wait to watch it get better and better........ great job devs!!!
Sent from my SCH-I535 using Tapatalk

BrUhNiGGs said:
Just leaving my finger prints here real quick...
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Stop fondling it!
Sent from my SCH-I535 using Tapatalk

OK, couple issues, I think I've forgotten a couple. WIFI decided to stop working, it turns on, but won't find any SSIDs. My softkeys decided to stop working, I had to go into settings and turn the softkey lights back on (I prefer them off all of the time). This is on the latest nightly.
Edit: I'm just going to try reflashing

uberbdon said:
OK, couple issues, I think I've forgotten a couple. WIFI decided to stop working, it turns on, but won't find any SSIDs. My softkeys decided to stop working, I had to go into settings and turn the softkey lights back on (I prefer them off all of the time). This is on the latest nightly.
Edit: I'm just going to try reflashing
Click to expand...
Click to collapse
Both are non issues for me and I'm on the 02-03 build. So Yeah reflash. This is an awesome rom.
Sent from my KitKat Galaxy S3.

How's the camera?
Sent from my SCH-I535 using Tapatalk

o0BlacknesS0o said:
How's the camera?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Froze once (switching between camera and camcorder).
Sent from my KitKat Galaxy S3.
---------- Post added at 01:28 PM ---------- Previous post was at 01:19 PM ----------
goatman101 said:
Where is dark carbon?
Click to expand...
Click to collapse
With kitkat roms, you can theme them through the Play store. Search for cm11 theme. I'm running a free one that blacks out messaging, play store, phone, etc. To apply go to settings>theme.
Sent from my KitKat Galaxy S3.

Can't wait to flash this later tonight
Sent from my SCH-I535 using xda app-developers app

goatman101 said:
Where is dark carbon?
Click to expand...
Click to collapse
I thought the same thing! I'm us i G thyrus holo theme. It's really nice.
https://play.google.com/store/apps/details?id=com.template.theme.ThyrusHoloBlack
Sent from my SCH-I535 using Tapatalk

Kind of a general question, but if I enable voice+, do I still have to have the Google voice app installed for hangouts to work properly ?
Sent from my SCH-I535 using Tapatalk

Most stable, best battery life of any 4.4 ROM I've tried. I <3 Carbon. Can't wait until all the little kinks are worked out.

Running 2/4 running very good had two random reboots. Really liken carbon just miss halo.
Sent from my SCH-I535 using xda app-developers app

Error message
I've downloaded nightly 2-2 today and placed it on my sd card, but when I attempt to install it I am receiving an error message and it is aborted. Does anyone know why this may be happening.
Also, I went back to the download page to try to download another nightly or the 4.3 stable copy and the list of devices are not showing anymore. Is it me or has it disappeared?

[ROM][unlocked][douglas] Lineage-14.1 [OCT 27 2020]

Removed For Lack of Initial TimeLine Knowledge And To Not Step On Toes

Reserved..

What's the point of this? Why you're sharing the ROM without my permission? Couldn't you just create a post in the LineageOS 12.1 thread with the link (instead creating the new thread - what I was going to do soon..-)?
At this point I'll release LineageOS 14.1 as-is tonight (and yes, I'll create my own thread - which was the initial idea.. -) because people doesn't seems to be able to wait for it.
Thanks for sharing my work (can we also say steal?) without my permission :good:
---------- Post added at 09:59 AM ---------- Previous post was at 09:46 AM ----------
btw,
12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Dev Relations team (listed below) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;
Click to expand...
Click to collapse

Rortiz2 said:
What's the point of this? Why you're sharing the ROM without my permission? Couldn't you just create a post in the LineageOS 12.1 thread with the link (instead creating the new thread - what I was going to do soon..-)?
At this point I'll release LineageOS 14.1 as-is tonight (and yes, I'll create my own thread - which was the initial idea.. -) because people doesn't seems to be able to wait for it.
Thanks for sharing my work (can we also say steal?) without my permission :good:
---------- Post added at 09:59 AM ---------- Previous post was at 09:46 AM ----------
btw,
Click to expand...
Click to collapse
Let me just clear the air here. Fisrtly, one cannot "steal" something that is openly, publicly and freely available on github. In regards to the legal mumbo jumbo you posted, makes 0 sense to me and means nothing, since that is not the case we have here. I never once re-released anything, nor said anything about taking credit for the work you did. I simply put the rom together from open source materials, just as anyone in the world can /could do and released something that was not built and released. Big differences there. Now, had I hacked your github and started building and releasing your private folders, then what you are talking about would be on par with what you are posting. Long story short, I found the source, built the rom and tested it. I then uploaded the Rom and was in the middle of making this Main post when I came across your cm12.1 post mentioning 14.1. I then tagged you out of mutual respect for your work and personal feelings so that I would make sure that I wasn't stepping on your toes. I now know your feelings and that I am stepping on your toes. Because I have respect for you and your work, I have no problem deleting this thread and the Rom. Just didn't make sense to me at the time that somebody had done all that work and released no rom, so I thought I would be nice and help people out. The better thing to maybe have done, for the benefit of others confusion, is to make the 14.1 thread ahead of time, even if it's blank until release. Silly one would have to read hundreds of pages of cm12.1 stuff to get the gist of what's going on with unrelated 14.1 stuff. I do Apologize for any confusion on my part and any bad feelings you may now harbor. The Rom is your work and now that I know the timeline of things, I'll back off and let you handle it. I will be focusing on getting out more recoveries to compliment your rom. The recovery kernel is built using your sources but the device tree for it was fully made by me, so no confusion there. Again, sorry for basically beating you to the punch of your own release. Like I said, had I not read the cm12.1 posts, I never would have had a clue to any of this. Hopefully you can accept my apologies, move forward and be friends...

PizzaG said:
Let me just clear the air here. Fisrtly, one cannot "steal" something that is openly, publicly and freely available on github. In regards to the legal mumbo jumbo you posted, makes 0 sense to me and means nothing, since that is not the case we have here. I never once re-released anything, nor said anything about taking credit for the work you did. I simply put the rom together from open source materials, just as anyone in the world can /could do and released something that was not built and released. Big differences there. Now, had I hacked your github and started building and releasing your private folders, then what you are talking about would be on par with what you are posting. Long story short, I found the source, built the rom and tested it. I then uploaded the Rom and was in the middle of making this Main post when I came across your cm12.1 post mentioning 14.1. I then tagged you out of mutual respect for your work and personal feelings so that I would make sure that I wasn't stepping on your toes. I now know your feelings and that I am stepping on your toes. Because I have respect for you and your work, I have no problem deleting this thread and the Rom. Just didn't make sense to me at the time that somebody had done all that work and released no rom, so I thought I would be nice and help people out. The better thing to maybe have done, for the benefit of others confusion, is to make the 14.1 thread ahead of time, even if it's blank until release. Silly one would have to read hundreds of pages of cm12.1 stuff to get the gist of what's going on with unrelated 14.1 stuff. I do Apologize for any confusion on my part and any bad feelings you may now harbor. The Rom is your work and now that I know the timeline of things, I'll back off and let you handle it. I will be focusing on getting out more recoveries to compliment your rom. The recovery kernel is built using your sources but the device tree for it was fully made by me, so no confusion there. Again, sorry for basically beating you to the punch of your own release. Like I said, had I not read the cm12.1 posts, I never would have had a clue to any of this. Hopefully you can accept my apologies, move forward and be friends...
Click to expand...
Click to collapse
Hi,
Yes, you're completely right there (my bad): you can't actually steal something that is public in the web (I'll try to keep my future work in private repos until it's stable then). I was just really pissed off to see someone shared the ROM that I was working on (so hard for almost 6 months) in a new thread without even waiting for me to allow you or something. But whatever, no offence here (I accept your apologies) and as I previously said (telegram) thanks for understanding my decision and thanks for deleting the ROM. I'll try my best to get stable 14.1 working as fast as possible and I'll release it once it's ready. If people really wants to try the beta of LineageOS 14.1 I'll create an special post in the 12.1 thread with all the stuff later.
About the recoveries I know you just used my kernel tree, I was talking about the device tree/vendor tree you used to build 14.1 (which are the ones I've been working on this months).
Regards and sorry for the confusion.

Hey Rortiz2.
Rortiz2 said:
If people really wants to try the beta of LineageOS 14.1 I'll create an special post in the 12.1 thread with all the stuff later.
Click to expand...
Click to collapse
That would make sense. If you do not want to publish your ROM yet fire at least a non-open beta to get the ROM faster and more stable. Let me know if I can support you here in any way.

I would love to be able to test lineage 14.1 on this device, I have been using 12 on it since it released