Related
Ok guys, it's been brought to my attention that my post was
1. Cantankerous.
2. Seemingly disrespectful of devs great work on here.
3. Taken too seriously for being an internet forum.
I would like to say sorry, and explain what I mean I tihnk it would be awesome to pull together the necessary funding for our very talented developers to create an XDA exclusive, completely original ROM. I'm not sure if it is possible, but something that is just for the Thunderbolt alone and isn't sense, isn't AOSP, isn't MIUI, and DEFINITELY not like Motorboat... I mean Motorblur. I think we really are on to something with the work that the Dev's are doing with taking different roms and porting them/using other roms as bases and then building from them; lets see what we can do to completely change the way that this stuff is done(if possible) by polling ideas(not unreasonable wishlists) and putting it all together. Possibly coordinating between Team BAMF, Chingy, and some other the other recognized DEV's.
What does everyone else think?
htcdesirezgeorge said:
I'm not sure if it is possible, but something that is just for the Thunderbolt alone and isn't sense, isn't AOSP, isn't MIUI, and DEFINITELY not like Motorboat...
Click to expand...
Click to collapse
If it isn't sense/blur/touchwiz, it is AOSP. Miui is just modified AOSP (with no sources given back), just like all the other roms not sense/blur/touchwiz are also based on AOSP. You do know what AOSP means right? Android Open Source Project as in the android operation system that is the basis to all android phones just modded by the OEMs. What you're asking is similar to saying:
"Hey, I'm bored with linux, unix, osx and windows, can we make a new operating system totally not based on any of those for our computers?"
Perhaps rephrase your question one more time in a way that makes more sense? Third time is a winner
yareally said:
If it isn't sense/blur/touchwiz, it is AOSP. Miui is just modified AOSP (with no sources given back), just like all the other roms not sense/blur/touchwiz are also based on AOSP. You do know what AOSP means right? Android Open Source Project as in the android operation system that is the basis to all android phones just modded by the OEMs. What you're asking is similar to saying:
"Hey, I'm bored with linux, unix, osx and windows, can we make a new operating system totally not based on any of those for our computers?"
Perhaps rephrase your question one more time in a way that makes more sense? Third time is a winner
Click to expand...
Click to collapse
Ya got a point, I actually didn't know that! BUT, regardless of how its phrased, what do ya think it would require to do somethig like I mentioned? I, personally would love to see something excitingly new put out here. Like with the miui project, any chance of people putting their heads together to figure it out?
You've got OS's and you have UI's. Obviously it is entirely possible to custom build a UI, but its FAR more difficult than porting one over or mixing and mashing parts of Sense together. UberBAMF is definitely something new and out of the box. That's more radical than anything I ever expected... Or have ever seen elsewhere. UIs do a lot to sell a device, so its worth it for HTC or Samsung to invest in building one. Not so much for a team of volunteer devs.
htcdesirezgeorge said:
Ya got a point, I actually didn't know that! BUT, regardless of how its phrased, what do ya think it would require to do somethig like I mentioned? I, personally would love to see something excitingly new put out here. Like with the miui project, any chance of people putting their heads together to figure it out?
Click to expand...
Click to collapse
Chances are unlikely to get a new user interface geared to only one phone built from the ground up from the android source by a team for a few reasons:
1) Lack of like-minded (knowledgeable) developers for one device that are currently free. Developers are very opinionated (just from my own experience even if they don't want to admit it). What should/shouldn't go into it would be a mess to deal with and debate alone, especially since the opinions of developers are generally not the same as those that don't develop. The ones already developing most likely don't want to give up their current projects as well. Basically, the developers that want to develop already have their projects and most treat them like it's their "baby" and most likely not willing to give them up or put them on hold. That moves into issue #2
2) Time. It would take considerable amount of time and organization to do that. Probably to get something stable that's original would take longer than most people would keep their Thunderbolt. Guys that work on their phones do this part time for fun as well and that combined with other side projects would press for time.
3) True developers & designers. There's a big difference between hacking some already made stuff to work with things and actually writing object oriented software from scratch. Obviously some guys putting stuff out for the thunderbolt are true developers that code professionally and others are just hacking around making things work done by others. Both have their uses, but you need real development for something like this and I don't think there's enough of those willing.
Forgot to add that the only way change happens is to build interest, so don't let my pessimistic observations detour anyone from posting their thoughts and ideas in this thread
I've heard many things, all great, about CM since the beginning of time (...well, close to it.). Frequently, before a real android phone was obtainable via the average pathways here in the U.S. of A, and the iPhone was the only real option for a smartphone, I found myself pulled towards CM-even though I had no way of actually using it at the time. The open-source, power-to-the people feel has always appealed to me...and my journey, starting from the age of 12, when I started crashing my parents computer so I could spend more time with the boutique builder that would fix it, later fixing it myself, then exploring the down-and-dirty innards of my gadgets-- this journey, has always felt like home to me.
My personal tinkering with phones and the like started with my sisters HTC Tilt, which I skinned to look like an iPhone for her. This was one of the first phones with Wi-Fi (Ha!), and trying to get it work was just as fun as using it.
Moving on, I received, for my birthday, a palm PDA (one of the first with a camera and a color screen...the device itself was blue), but I had to return it due to an exploding display.
Finally, a couple years ago, I got my first smart-phone. An iPhone. And within an hour after getting it, I had it jailbroken and themed. But the innards were still off limits. While searching under terms lie? "Hack phone" and "tethering, I always came across posts speaking of Cyanogenmod...In fact, I'd say that an astounding 50% of my searches relating to customizing or modifying--in some way or another, led to a post or thread--sometimes a whole article, on how to do something with android, and specifically CM. This proved fruitful for my later endeavors.
When I was doing better financially, I bought my first android device, and have never felt so empowered, and have never had such a strong ownership of my devices. That device was the Transformer.
Again, after just an hour of owning the device, I was looking up terms...and searching XDA for every bit of relevant information I could find. Some of the questions I had: What is Clockwork Mod? What is Clockwork Mod Recovery? What's the difference? NVflash? What's a B70 serial number mean for my prognosis? What's a Nandroid? How do I choose a ROM?
Although there was a metric ten of terminology I needed to learn to know what I was doing--and even though there was almost a complete vacuum of centralized information--- at least authoritative information (any questioned asked in forums led to me being booted and marked as a noob), things eventually worked out.
I learned about the Boot loader situation for the transformer, the status of honeycomb as a sort of non-open-source open source operating system, and about the battery issues....about kernels, and speaker mods, about modules and root apps-and along the way I learned almost the full metric ton of terminology, and had a metric ton of fun...with you guys.
Which brings me to today...I own a brand new galaxy note, but am once again in the dark. Only this time, its far worse...because my questions pertain to CM, the gold reference when it comes to running a custom rom, and its structure...that is to say, the structure of the ROM, the team that builds it, and the community that helps support it...all relevant to understanding the dearth of work and choice that we find in this very forum. And because its been around for so long, the staple that CM has become, assumes that all things and all people know what's happening.
Which brings me to my real questions....which I've searched, and searched, and searched again for answers to, but have found no conclusive, or concise and relevant answers. I've searched the cyanogenmod site, the forum, this forum, and Google. And while I found half-answers, and although I'm confident I can root any device I, or my friends can buy, and I can install custom roms, edit props, change permissions, dump radios, flash pre rooted kernels and other kernels, and backup and edit every settings app and image I can find, I still find myself lacking a fundamental understanding of Cyanogenmod and Cyanogenmod work, official, and unofficial--information that would make my life complete, and help me bear the fruit of this journey I'm on.
That journey ends with a device that I own...one with cyanogenmod on it...specifically...a device in the near future that runs a version of CM that I helped contribute to-either officially or unofficially to.
And the beginning of the end to that journey, and the desired end game--developing, begins here. With my ASUS Transformer. And my questions.
Note: I illustrated this story in-depth, for a reason. To let you know that I've searched long and hard for clear answers, and that I plan to contribute significantly in the future to Android, and to XDA. I just need a teeny bit of help...a little direction. And so do a lot of us. I haven't found anywhere, a discussion of this subject--a significant one when it comes to understanding our community, our choices, and how to contribute...that subject is the structure of Cyanogenmod: the ROM, the team, and the community that constitutes them. The following questions are relevant to, and seek to address this fundamental lack of understanding.
Since the release of IcS, we've seen an explosion of CM in the Transformer forum. And while I understand how to read a change log, and a list of "what's working" and "what's not working", and can rely on a search find out what "Cornerstone" is, its still damn near impossible to define the relationship that constitutes all of the CM builds that are available. It might be clear, after a search, what the term "Kang" is, but what isn't clear, is what this means for the end-user. Its not clear what's official, what's parallel work, and what makes up the night lies that we can find on the CM repository. Is it one man aggregating work from forums like this, and throwing all of the features and fixes into a centralized build? Are the ROMs that we find in the Development section of the Transformer section off-shoots of CM to be worked on and differentiated in the future? Because where it stands now, I don't see a ton of differentiation. Maybe its because there's just been a new release, and I'm seeing the beginning of a process here. But I'm still unaware of what makes up a CM team. Its not clear how these things work-- if there is one man from the team working on the transformer, another working on the Epic 4g...and so on, or if everyone works on the same thing, and the feature or fix is distributed by a magic machine, or if each person on the team works on the same thing, and then a designated person ports it to his device. It's context like this that makes an informed overview of the current situation possible. And without that context, I'm stuck.
Most know that nightlies come before the release candidate(s), and that a stable release follows. But what I don't know, is why I never hear about an actual release, and almost always hear people speak of night lies, and in general, they're almost categorically excited.
So, if we were to examine my complete and utter lack of knowledge together, wed conclude that it's impossible for me to understand where XDA, and the ROMs that are available in the development section fit in to the grander-scheme of things. Is it better to get a nightly from CM? Is the nightly made up of the very fixes and developments we find in the various ROMs here in the development section?
How does someone go about deciding which of the dozen ROMs to install? Because the threads for ROMs don't explain anything when it comes to explaining an end goal, and a developers intent for the ROM, and the reasons why he/she is making one, I find myself stuck in the quick-sand of change-log after change-log, feature list after feature list.
Give me the 411. Explain to me what I'm missing in my Rosetta stone of the big picture..the grand scheme of things. Maybe I'm looking at this all wrong...maybe I'm just an idiot. Maybe you'll rage at me. But maybe, just maybe, I'm missing only, one small, key, piece of information here, and I spent a couple pages typing on the touchscreen of my transformer for thirty five minutes to find the answers that I badly need.
I'm sorry if I wasted your time. Thank you very much for reading this.
If you have a problem with my post, or a suggestion, attack, or complaint, please Private Message it to me...unless it pertains to the questions I posed...in which case I would very, very much appreciate your comment, your input, you sharing your knowledge, or even a question of your own.
Thanks.
Seriously? All that wall of text to ask the same question that everyone else asks?
This is how you divide up the custom ROMs to make your choice easier:
Do you want cornerstone or no?
If you want cornerstone, you pick between Team EOS or CM9
If you don't want cornerstone, you have these to pick from(in no particular order):
Revolver
Android Revolution HD
Codename Android
AOKP
CM9 no cornerstone version
Just try them and see what you like. I don't understand why people are so cautious before picking a ROM as if it's a permanent choice that can't be reverted.
If you don't like it, you can quickly flash a different ROM.
It's better for you to make your own decision based on your own experience with the ROMs rather than rely on someone else's recommendation whose needs and personal preference might not match yours.
Thank you, actually a nice read, there is also official cm support for our tf, on the cm website, last i seen there were 3 nightlies, since ics iv flashed the official cwm modded rom, then revolutiin, then team eos, then cm9, back to revolution, then codename android, now back on krakd hc rom until jcarrz releases his ics rom.
Sent from my R800i using xda premium
You gotta keep in mind that all ICS development now is in an early stage. Every rom is new, we don't have a solid stable one. Even stock asus have problems with rebooting, dock integration and so on.
CM is fragmented in 2 or 3 builds, and what diferentiates then is only the commits from CM repository and some dev preferences, like cornerstone or full support for the dock.
All roms that aren't Asus based (AOSP) suffers from some aditional issues, like:
- Dock won't be fully working, except on CM9 by ricardopvz and Codename Android. The touchpad still works different from stock asus.
- Some Wi-fi and GPS issues, probably driver related
- Screen rotation have a lag issue (all AOSP roms)
- Dock battery info missing, even with widget.
- Battery drain issues.
I have tested almost all roms and can say most of then is pretty usable. But if combined with overclock kernel, you can certainly expect problems.
[noobquestion]What is this cornerstone everyones talking about? lol [/noobquestion]
Im personally running team EOS nightly build (no cornerstone) with blade's OC kernel running at 1.4Ghz.
I think the ROM works very well. It hasnt really given me any issues except 2 random reboots and 1 semi-freeze (all on the same day lol). Its been running perfect for 3 days now though.
Don't worry about hondroid he is kind of a troll no hard feelings
I have not used CM for quite some time but here is my understanding from having worked with the captivate and transformer for over a year now.
Cyanogen mod is based off of the true source code of andorid taken directly from google and with no OEM's getting their greasy little fingers over them and polluting them with bloatware and skins. From there cyanogen set up a git repository where they have the main android tree as pure as it is and then branches for each device. Then there are plenty of devs working directly on the tree optimizing the core android and adding features which can then be accepted or regected by the otehr devs. Then there is a smaller team of devs on each "Branch" which normally consists of a certain type of processor or chipset. Ex Hummingbird or Tegra 2
The job of the devs there is to integrate that to make it work smoothly and they have the same peer approval system. There are also smaller branches which contain the drivers for most pieces of hardware (Speakers, Screens ect). Then finally there is the device dev there are normally about 5 from my experience but once all the work is done the team can be cut to 1 or 2. They are the people that get it up and running on the device writing missing drivers fixing device specific bugs ect. And once they are done there work they can compile it all together and there we have our nightly.
Then if there is a change in the core all the device devs have to do is recompile and build the rom and there is your next nightly.
The RC happens when they hit a stable nightly or when development has slowed enough that all of the bugs have been fixed
Hope this is helpfull
Thanks to all of your for your responses. I think this is a beautiful conversation that isn't happening enough. All of you have provided great information, that when combined helps to depict the structure of the community we have all grown to love.
Wondering if anybody could provide compelling reasons to be utilizing Cyanogenmod or Liquidsmooth over the other? I believe that Liquidsmooth is based on the CM tree, but am having trouble finding differences between the two at this point (with both using JellyBean 4.2.1 builds). Does anybody have experience with one of these recent builds running more stably than the other?
FYI, I'm running an unlocked Verizon Galaxy S3 (and loving it!).
Thanks in advance!
IMHO, Liquid is more stable. The difference with their rom is that they add their own tweaks and apps and such. Cm is like the base 4.2 for all aosp roms. They each have their own unique features but with my experience, Liquid has been more stable
Sent from my SCH-I535 using Tapatalk 2
um i dont think we can choose between the 2 if im not mistaken liquidsmooth is Cyanogen based
Alright, I'll be the bad guy.
Most notorious thiefs in the biz. Refuse to give credit (even when asked numerous times by mods -- I've seen the PMs) and basically a paid service with the sheer amount of times they ask for donations. Almost begging -- pathetic.
If you've been around long enough, you'd know their OP did NOT read like it does now. That took years. I used to run Liquid on my D1, then I heard (and saw) from a little birdy what they're all about. Saw the evidence and my eyes were opened.
I swiftly blocked both Liquid team members from my gtalk and haven't ran it since. I pity the fool who gives them a dime. Way better alternatives that don't beg for money like a panhandler...
Flame on.
Sent from my SCH-I535 using Tapatalk 2
1ManWolfePack said:
Alright, I'll be the bad guy.
Most notorious thiefs in the biz. Refuse to give credit (even when asked numerous times by mods -- I've seen the PMs) and basically a paid service with the sheer amount of times they ask for donations. Almost begging -- pathetic.
If you've been around long enough, you'd know their OP did NOT read like it does now. That took years. I used to run Liquid on my D1, then I heard (and saw) from a little birdy what they're all about. Saw the evidence and my eyes were opened.
***SNIP***
Click to expand...
Click to collapse
Thanks 1ManWolfePack - I appreciate the candid response. Hopefully the LS team is operating a bit more honestly these days, but I'll give base CM another go and hope I can get it to run stably. I've actually had similar experience so far as BraddahBoi808 in that the LS 4.2.1 builds have been more stable, but I'm looking for better battery life and hope recent CM builds will provide it (perhaps in conjunction with a new kernel).
In my experience, I've found CM to be a lot smoother than Liquid. In fact, I never really found Liquid to be as "LiquidSmooth" as they say. I only used it when I did because it was one of the only roms available at first on the N7 and Verizon GN.
Of course I'll choose the Big Three over Liquid anyday.
SwiftLegend said:
In my experience, I've found CM to be a lot smoother than Liquid. In fact, I never really found Liquid to be as "LiquidSmooth" as they say. I only used it when I did because it was one of the only roms available at first on the N7 and Verizon GN.
Of course I'll choose the Big Three over Liquid anyday.
Click to expand...
Click to collapse
Thanks SwiftLegend - really appreciate the feedback. I've installed the latest nightly of CM10.1 successfully, but it's still got a bluetooth issue so I'm looking around at other options (which I enjoy doing anyway). Excuse the question, but what are the big three that you've referred to? One is clearly Cyanogenmod, guessing a second is AOKP, and is the third by chance MIUI?
I ran Liquid ICS and 4.1 on my Nexus for a while. Was nice, didnt have any issues and had a little more of the customization pulls included.
Have run CM also. Would have liked a little more customization, but again no big issues here either.
Try both.What do you have to lose? 30 min
BTW, where do you see a liquid build for our device?
Sir-Lancelot said:
**SNIP**
BTW, where do you see a liquid build for our device?
Click to expand...
Click to collapse
I actually did run both... have used CM in the past and was using LS recently. Couldn't really find any significant differences and was wondering if others had found them.
Sorry to have gotten your hopes up re: a LS build for the Galaxy Note II - I realized after the fact that I posted in the wrong device forum (I'm using a Galaxy SIII) but still got relevant responses so left the thread as-is. Hope a build comes out for the Note II soon for you though!
carpdeeem said:
Thanks SwiftLegend - really appreciate the feedback. I've installed the latest nightly of CM10.1 successfully, but it's still got a bluetooth issue so I'm looking around at other options (which I enjoy doing anyway). Excuse the question, but what are the big three that you've referred to? One is clearly Cyanogenmod, guessing a second is AOKP, and is the third by chance MIUI?
Click to expand...
Click to collapse
CyanogenMod, AOKP, and Paranoid Android (PA)
This is the Note II section
I will move to the S3 for you
Thread moved
kennyglass123 said:
This is the Note II section
I will move to the S3 for you
Thread moved
Click to expand...
Click to collapse
Thanks Kenny - realized my error after the fact. I appreciate your assistance!
SwiftLegend said:
CyanogenMod, AOKP, and Paranoid Android (PA)
Click to expand...
Click to collapse
Very interesting... hadn't noted PA before... looks like a VERY interesting ROM, but unfortunately not available (as I can tell) for the VZW G3, and certainly not in 4.2.1 flavor yet.
In the meantime, I think I'll be monitoring CM & LS for the first stable 4.2.1 build that includes functional bluetooth, GPS, and streaming audio. LS beta 1 version A has actually been the closest I've found thus far, but the battery life was horrendous.
CM 10.1 works a lot better on my phone than liquid smooth. The latest of liquids betas freeze up my phone, won't let it wake up, and I have to keep toggling data on and off to keep it.
Well this is an interesting thread.
I'm the team liquid communications guy. Here's what I can tell you about what we do. Bear in mind, I'm not a dev - I'm here specifically to handle releases, etc.
The team is made up of a few core devs. Liquid0624, nocoast, and winner00. Occasionally hiemanshu as well but lately I think he's travelling. By far Liquid0624 makes up the core of what this rom is.
We were based on CM briefly for 4.1.2, but are back to AOSP. We didn't care for the CM base. Here's what we do - we take the AOSP code, and optimize the hell out of it. Our roms are ~100mb. We then start to add in features. We tend to go for the same popular features everyone else likes. Generally more than CM, but not so jammed with features as AOKP can be. Sometimes too much of a good thing is too much.
Credit is always given. If we miss it, it's an oversight. Given I'm not really a dev, I can see that happening and I shall endeavor to ensure that better care is taken for such things. I absolutely agree that such things deserve credit, always.
Do we need donations? You bet. We're a tiny little team, and Liquid0624 does this as his job. He works at least 12 hours a day on this, and is often pestering me at all hours of the night about new releases, etc. This is his life. So yeah, we need donations. Without them Liquid (whose name is Ryan, by the way) can't afford to keep doing this, and that means the rom dies. I'm doing this for free simply because I saw a need for a dedicated communications guy and wanted to keep that from happening. I know there's a rep. I understand why. I even agree that in the past things were stated in such a way as to make it seem like this was a pay-for-play operation. That's why I joined the team - I knew how it was on the inside and I saw the perceptions, and they didn't match.
That's the thing, really. This is not a pay-for-play operation. Literally the second a release is completed, I'm getting pings from Ryan. He doesn't like to hold onto things. I wish he would sometimes, and have actually started a group that helps to address that - more on that later. But there is no release we've ever held onto or not released to the public. Ever. Never, ever, ever. This is an open source based rom, and our code is freely available, our builds are freely available - always will be.
I'm always working on ways to make things even better. We created a "producers" group for folks who donate a certain amount. These folks get slightly better access to our devs via a google groups community - mostly chitchat back and forth. I've taken to posting builds there a little (couple hours) sooner, just to get some early testing done, but I think I've done that a total of twice. Most of the time Ryan is hot to get things out the door and into your hands. It's a way of us to say thanks to our supporters. We also are working on other ways to do so as well, because without our supporters we wouldn't exist. One of these days we'd like to have a paid app of some kind so folks can donate that way as well if they want. Maybe we will.
So that's the deal. We're in a place that all devs are in who can't afford to do this for free. We're passionate about android, we want to bring you the best rom possible - this is our daily driver too - but we need to literally keep the lights on and keep Ryan's family fed. So we need to ask for donations constantly. Would we rather not? You bet. But it is what it is, and it's a line we walk. Believe me when I say that no one is making retirement money, here. I have a family myself, and sometimes I think Ryan might be insane. There's zero doubt that he's passionate about this stuff, or he wouldn't be doing it.
But 1ManWolfePack, I'm going to argue to the end that we're a team of thieves. We work with other devs, we contribute code, we use code and credit it - just like the rest of the dev community. If you want to converse more about this privately, I'm more than willing. I will always take suggestions. It's a difficult line to walk - we think we've got something great, and want to give it to the world - but we do need to get something for the amazing amounts of time we spend, or we physically can't do it anymore.
Derek
Team Liquid
You don't have to donate if you don't want to.. It's free to the population... And imo its the best out there.. They get my money because I like the rom and it's my gift of gratitude back...
I don't know if you're broke or cheap, but to slander them for something that is technically free? You don't wanna donate? Don't.. Simple as that
Sent from my galaxy nexus using Xparent Purple Tapatalk 2
You must be rich. Maybe you should make a rom and give it for out free. Fail to understand your "Most notorious thiefs"
Your comment is worth a grain of salt.
1ManWolfePack said:
Alright, I'll be the bad guy.
Most notorious thiefs in the biz. Refuse to give credit (even when asked numerous times by mods -- I've seen the PMs) and basically a paid service with the sheer amount of times they ask for donations. Almost begging -- pathetic.
If you've been around long enough, you'd know their OP did NOT read like it does now. That took years. I used to run Liquid on my D1, then I heard (and saw) from a little birdy what they're all about. Saw the evidence and my eyes were opened.
I swiftly blocked both Liquid team members from my gtalk and haven't ran it since. I pity the fool who gives them a dime. Way better alternatives that don't beg for money like a panhandler...
Flame on.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I just want to chime in the LS will have many more useful features than CM will have. CM is a great ROM, and I have ran it much more recently than I have ran liquid, but if I had to choose one it would probably be liquid. The team is very engaging and kind.
Yes, they ask for donations, but there are reasons for it, and it has no affect on your access of the ROM. I am running AOKP JB M1 at the moment, but once liquid has their first stable version of 4.2.1 ready for the GNex I will probably jump on.
Also, they base off of AOSP more often than not, and yes...I have been around since the D1 days.
Best,
RC3
Liquidsmooth on Gnex has been stellar for me. Everytime I stray to a different ROM I always end up back to Liquidsmooth. Everything else has been laggy and slow for me. Can't answer for the SIII.
As far as the begging for money comment, I have never felt any kind of pressure to donate. When I do donate, I don't expect anything, just saying thanks to their team for the countless hours spent on putting the ROM together and they sure appreciate it.
Edit: Just to add, they don't treat me any different than anybody else whether I donate or not. I still get the ROM's in a timely manner either way. Matter of fact, just when I finished setting up Beta1D, here somes Beta2.
This may not be my place to chime in but i will anyways. I've been using LiquidSmooth roms since the OG Droid days, they were always what i expected back then and deeply contributed to my keeping that phone for so long. I donated a few times simply because i wanted to show my appreciation for there work (its like when doormen at hotels carry your bags to your room and you give them a few bucks, its to show appreciation, its not mandatory but it helps them) did i ever receive benefits for these donations? Hell no, did i expect them? Hell no. I simply did it because i wanted to show my appreciation for there work its that simple.
Now onto this "team of thieves" i see plenty of credits given in there posts.
Example A:
toxicthunder said:
Ours is an open source project. Please feel free to look at our code on LiquidSmooth GitHub
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project.
Furthermore, we also extend our gratitude to AOKP, Team CNA and Team EOS for parts of their code that we have incorporated.[/SIZE][/FONT]IMPORTANT NOTE:
Click to expand...
Click to collapse
Now that doesn't look like a post that's 'stealing' its giving credit to others code that has been incorporated into the rom. Its not stealing at all. They also leave there entire project as open source, again if somebody is stealing why leave it open source? They leave it that way so if another developers see's something they like, they can contact them about using it in there rom. EVERY single rom created is almost guaranteed to have some idea borrowed from another developer, why? Because its open source, and each developer wants to try and give the users what they want. Stealing would be taking code without asking and then not giving credit, but this is the opposite. So again are they thieves? Nope, you might wanna get your facts checked, and knowledge checked, and evidence checked before making outrageous accusations.
Onto the "begging" thing, where in there thread are they begging for money? Posting a release with a link to the rom, gapps and donation link is NOT begging at all. Posting on twitter that liquids computer died and asking for donations to help him fix that so roms can continue to be developed is NOT begging. Its simply reminding "hey we have a donation link just in case you're feeling generous" when have they ever said "No donation, no rom!" lets see.... never, because that's not how it works. If you want to donate then that is your choice, you don't have a gun to your head, and you aren't paying for the rom. I still donate because i appreciate the work, and know how much time and effort goes into it. I also know that computer parts aren't cheap and that every donation helps. Asking for a simple donation that's a DONATION (not mandatory, not required, etc) is nowhere near begging. Sitting on the corner everyday on your hands and knees asking people for money that's begging. Telling someone "you can only have the download link if you donate 5$" is considered "pay to use", saying "Here's the link, gapps, and donation link" that's not 'pay to use' that's free to use with an option to donate.
And my finally, for somebody who claims liquid is this big bad terrible thieving team, i see no evidence of it, and i highly doubt there is any because its not true. You made some pretty big claims with nothing to back it up except "a little birdy told me" okay well a little birdy also told me that i could fly if i jumped off a bridge, but we both know that's not true Anyways i'm done <3
***I am in no way affiliated with team liquid, and do not represent them in any way, i'm simply chiming in my opinion***
<3 NeverEndingXsin
I think we all realize that making these ROMs is just a hobby for most, but doesn't anyone want to make a fully stable one? From what I've seen since this phone rolled out, is that someone will make a ROM, update it a few times, and then it's just dust in the wind. Also the only 100% stable ROM is the stock ICS ROM; no? My point is not to criticize anyone for their hard work,but to rather ask the question; what is the point of tinkering with a ROM and never getting it to 100% before moving onto the next one? I know everyone is very appreciative of what goes on in this community, me included. I was just wondering if someone could shed some light on this question for me.
Also, just my two cents; It would be nice for someone to maintain a custom ICS ROM just so there can be an up to date ROM with nice features and wifi calling. =)
Instead of giving your 2 cents, do it yourself. What's your definition of stable. I've been on PAC since it's come out and have zero complaints. Your want stable? Don't root, don't flash, don't modify. There, perfectly stable. Saying "my point is not to criticize" doesn't absolve you from being completely ungrateful for the hard work it takes to do this. Do it yourself. XDA is a development forum, not completely 100 percent stable forum. Don't like it? Go get an iPhone.
Sent from a Blazing PACMAN devouring ALL...
Most of the roms are stable. You can find things to ***** about on any rom, including stock.
When it comes to something not getting fixed it can come down to the dev not enough time, or its not worth the effort, or they moved on to a different device. I mean is it really worth fixing a bug that 2 people are experiencing if it is going to take a few weeks away from your family, I don't think so. And that is about how solid 95% of the roms are. Give some props.
There are probably 25 ROMs over 4 revisions of android... Its our job as USERS to spend the time and effort to find one we like, and that suits us. If a ROM has a bug that is detrimental to the use you need, look at another one. So try not to criticize devs when you haven't done your due diligence as a user.
csssc said:
I think we all realize that making these ROMs is just a hobby for most, but doesn't anyone want to make a fully stable one? From what I've seen since this phone rolled out, is that someone will make a ROM, update it a few times, and then it's just dust in the wind. Also the only 100% stable ROM is the stock ICS ROM; no? My point is not to criticize anyone for their hard work,but to rather ask the question; what is the point of tinkering with a ROM and never getting it to 100% before moving onto the next one? I know everyone is very appreciative of what goes on in this community, me included. I was just wondering if someone could shed some light on this question for me.
Also, just my two cents; It would be nice for someone to maintain a custom ICS ROM just so there can be an up to date ROM with nice features and wifi calling. =)
Click to expand...
Click to collapse
Fully stable is damn near impossible, man. There is sooo much involved in coding these ROMs it's literally staggering. These devs aren't software developers (not most of them) but just regular guys, working regular jobs like you and me. If you want completely stable best to stay stock rooted (so you can drop all that bloatware bull****) Most of these developers have day jobs that don't involve android and do this in their spare time, for us. To be frank, man, you did come across EXTREMELY critical, and the folks around here don't take kindly to that (just breath @njstein) What's the saying? Beggars can't be choosers? My point, if you want to run 4.3 your're gonna have to take the good with the bad, just suck it up and deal with the FEW bugs. I've been on 4.3 for a couple months now with no serious issues.. Just a few bugs. And for future reference, keep this kind of thing to yourself
I had no intention a dragging this into what it has become. Obviously no one understands the point I was making or the question I was asking. I'm not going to further this conversation anymore.
I don't understand why you are making a statement in general to all ROMs. The reason why the older ROMs are unsupported is because there is no reason to waste time updating them as the guy above explained. That's why you will never see halo on ICS. Now, 4.3 roms are supported at the moment. If you like an iPhone then congratulations.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
anactoraaron said:
Because if every dev stayed on ICS we'd have loads of folks asking if 'such and such device' will ever get a jb or kk rom. Seriously re-read the posts about how difficult it is to code. Your post is akin to asking someone to rebuild a car engine multiple times because every 5000 miles the thing misfires. Why did it misfire? Was it a plug/wire? Something in the valves/cylinder? Electrical? Fuel delivery? How many hours do you expect someone to waste tracking and rebuilding (sometimes rebuilding everything) for every bug in a rom- even the bugs properly reported with a log?
And I've yet to see any device from Sammy to HTC to lg or any device at all that's 100% stable - even on stock. And that's from companies that have software development teams.
And don't listen to those folks about getting an iPhone- that platform isn't 100% stable or perfect either. What you are looking for is a dumbphone.
Sent from my BN NookHD+ using xda app-developers app
Click to expand...
Click to collapse
Yup.... Why keep rebuilding that 4 banger (ICS) when with the same amount of work you can drop in a V6 (jb 4.1). And the same when a V8 (jb 4.3) is available to drop in. Then the 4 and the 6 get scrapped for some extra beer money, and you tinker with the latest and greatest again.
Deleted.
Haven't been on in awhile and I see an argument going on? C'mon guys. Okay, about maintaining ROMs, when maintaining there are nightly's based off the latest changes. The more changes lead to more better features (and maybe some bugs). Not all are stable. In fact, there is no such thing as a "fully stable" ROM. Even stock from Samsung isn't stable. And please, don't argue on here. Take it to PM or some other way to communicate. Not on here on a public thread. May I include, that I have an iPhone . Don't hate because the OS is not controllable. Its a nice OS and lots of great apps. But Android is specifacally better in my opinion. Don't hate me for that lol. Also, if you'd like to learn on how to dirty port a ROM just google it and let's see if you can make a "stable" ROM. Move on everyone. lol
Edit: I don't want the mods to come on here and waste their time. Keep it clean next time
xWolf13 said:
Haven't been on in awhile and I see an argument going on? C'mon guys. Okay, about maintaining ROMs, when maintaining there are nightly's based off the latest changes. The more changes lead to more better features (and maybe some bugs). Not all are stable. In fact, there is no such thing as a "fully stable" ROM. Even stock from Samsung isn't stable. And please, don't argue on here. Take it to PM or some other way to communicate. Not on here on a public thread. May I include, that I have an iPhone . Don't hate because the OS is not controllable. Its a nice OS and lots of great apps. But Android is specifacally better in my opinion. Don't hate me for that lol. Also, if you'd like to learn on how to dirty port a ROM just google it and let's see if you can make a "stable" ROM. Move on everyone. lol
Edit: I don't want the mods to come on here and waste their time. Keep it clean next time
Click to expand...
Click to collapse
You're right. It's important to remember that no one here is under ANY obligation to share anything - roms, root, recoveries, mods, etc - with anyone. So lets just appreciate what we have. :thumbup:
Let's also get a mod to close this thread, nothing more good can come of it.
This trollfest has gone on long enough. The sheer amount of disrespect flying around astounds me. Read the rules folks.
Thread closed.
With Kitkat being ported to so many older devices because of the lowered system requirements, I figured its time we get one on the ThunderBolt. I by no means can do this on my own, so that is why I am starting this thread. I will try to reach out to as many devs as possible to get this going. Just a little about myself, Ive done basic ROM developement on a few devices, the most notable being the 2 generations of the Nexus 7. Over the past few months I have greatly expanded my knowledge and capabilities with android. The extent of my coding knowledge is basic Java, a little bit of C++, and arduino, which is why I need help for this. I see this as both a learning opportunity for me as well as a chance to participate in expanding the Thunderbolt dev community. I'm mainly looking for somone who can help with kernel and radio develpement, and someone who can help with porting the actual software over. The reason I need these people is because I have no experience in kernel development, and as for the actual developement of a KitKat rom, I'm sure its more complex then downloading KitKat source and throwing in the Thunderbolt device trees. I've been researching the topic and havent found much useful information. If you feel you can help support the effort please contact me.
Email: [email protected]
Developers willing to contribute:
(will add as people offer)
frap129 said:
With Kitkat being ported to so many older devices because of the lowered system requirements, I figured its time we get one on the ThunderBolt. I by no means can do this on my own, so that is why I am starting this thread. I will try to reach out to as many devs as possible to get this going. Just a little about myself, Ive done basic ROM developement on a few devices, the most notable being the 2 generations of the Nexus 7. Over the past few months I have greatly expanded my knowledge and capabilities with android. The extent of my coding knowledge is basic Java, a little bit of C++, and arduino, which is why I need help for this. I see this as both a learning opportunity for me as well as a chance to participate in expanding the Thunderbolt dev community. I'm mainly looking for somone who can help with kernel and radio develpement, and someone who can help with porting the actual software over. The reason I need these people is because I have no experience in kernel development, and as for the actual developement of a KitKat rom, I'm sure its more complex then downloading KitKat source and throwing in the Thunderbolt device trees. I've been researching the topic and havent found much useful information. If you feel you can help support the effort please contact me.
Email: [email protected]
Developers willing to contribute:
(will add as people offer)
Click to expand...
Click to collapse
im waiting for a long time,thank you a lot!!!!!!!!!!!!!!!!!!!!!!!!
you can also try to transplant from msm8655 device，thats easier than bulid it.
chongbos said:
im waiting for a long time,thank you a lot!!!!!!!!!!!!!!!!!!!!!!!!
you can also try to transplant from msm8655 device，thats easier than bulid it.
Click to expand...
Click to collapse
I assume by transplant you mean just try to flash a rom for another device with simmilar specs? (Same MSM8655 CPU, Same amount of ram, etc)
Kitkat would be awesome!
I'll test whatever you throw up here.
That's about all I'm good for. Sorry.
you can try contact santod here, but need register
http://forums.infectedrom.com/forumdisplay.php/79-Thunderbolt-Android-Development
He's last man standing Thunderbolt expert developer...
but i hear He already switch to HTC One project n leave Thunderbolt.
it very exciting news if can be true:good:
Ive contacted a few members who have experience with either porting or the thunderbolt, none of wich have responded as of yet.
her you can try :
http://forum.xda-developers.com/member.php?u=4310221
http://forum.xda-developers.com/member.php?u=4471805
http://forum.xda-developers.com/member.php?u=4395946
hope they reply...
guinzo said:
you can try contact santod here, but need register
http://forums.infectedrom.com/forumdisplay.php/79-Thunderbolt-Android-Development
He's last man standing Thunderbolt expert developer...
but i hear He already switch to HTC One project n leave Thunderbolt.
it very exciting news if can be true:good:
Click to expand...
Click to collapse
Santod was the reason why I loved my thunderbolt. I still have it but rarely use it. Sadly the screen is cracked but it was always a reliable phone.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
I'm sure there are more than a few people who would contribute to the cause of getting AOSP and CM11 on this phone. My old fascinate has it and so do all my other phones since.
Sent from my XT1060 using Tapatalk
TtWEAK said:
I'm sure there are more than a few people who would contribute to the cause of getting AOSP and CM11 on this phone. My old fascinate has it and so do all my other phones since.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
There definitely are, but the difficulty of getting data on AOSP for this device, coupled with the age, current ownership/userbase, and developer interest translates to probably not. It's okay though, it was a great ride while it lasted.