Cyanogenmod Info. - Eee Pad Transformer Q&A, Help & Troubleshooting

Cyanogenmod Info. - Eee Pad Transformer Q&A, Help & Troubleshooting

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.

Related

[PLEA] I'm so confused about all the similar ROMs now!

I've been a regular reader of these forums since researching my first Android purchase. Over this time I have seem many new ROM projects born. I would like to argue that many of these projects are so similar that they are pointless.
I'm calling out anyone whoever made a new Hero/HTC-Sense ROM. Seriously. When you saw the 10 other Hero guys out there, what made you think it was better to release your own flavour instead trying to participate in an existing project?
I've taken a look, and as far as I can tell, there should only be 3 non-factory ROM projects:
- CyanogenMod, because of the effort Steve goes to stay 100% legal and teeter on the bleeding edge of Google's source code
- 1 Hero/Sense UI ROM, because we actually only need 1, why don't you guys work together, sheesh
- 1 Blur rip-off ROM, because goodness knows there are going to be people who actually think it's a great idea
Just because Android is based on Linux, doesn't mean we have to make all the same mistakes that has dogged and doomed Linux from the beginning. We don't need to splinter into a billion different distributions, at least not yet. Looking at the feature lists for many of these similar ROMs, the only thing that is different is additional locales or small bug fixes, hardly worth the effort of repackaging. /sigh
*end nerd rage*

i doubt they end. its their project, they build it how they like it and they share it. people do not have to download it. there are many reasons why they release their own, they have more freedom to do what they want. in past rom devs work together then they split up due to differences. working together is all fine and good but this isnt a utopian world haha, people have different opinions on how to move forward with a project.
just because you dont want to download and try different builds dont mean they should stop

jokeyrhyme said:
I've been a regular reader of these forums since researching my first Android purchase. Over this time I have seem many new ROM projects born. I would like to argue that many of these projects are so similar that they are pointless.
I'm calling out anyone whoever made a new Hero/HTC-Sense ROM. Seriously. When you saw the 10 other Hero guys out there, what made you think it was better to release your own flavour instead trying to participate in an existing project?
I've taken a look, and as far as I can tell, there should only be 3 non-factory ROM projects:
- CyanogenMod, because of the effort Steve goes to stay 100% legal and teeter on the bleeding edge of Google's source code
- 1 Hero/Sense UI ROM, because we actually only need 1, why don't you guys work together, sheesh
- 1 Blur rip-off ROM, because goodness knows there are going to be people who actually think it's a great idea
Just because Android is based on Linux, doesn't mean we have to make all the same mistakes that has dogged and doomed Linux from the beginning. We don't need to splinter into a billion different distributions, at least not yet. Looking at the feature lists for many of these similar ROMs, the only thing that is different is additional locales or small bug fixes, hardly worth the effort of repackaging. /sigh
*end nerd rage*
Click to expand...
Click to collapse
As a regular reader you should know that there are about 5 different versions of Hero floating around to base off of. There are 2 different versions of blur. There is also pulse, donut, cupcake, and variations on them.
Hero includes: Tattoo (a specialized mix of donut and sense), the sense ui merged with magic, the official release Hero, the non-official beta Hero, and the Sprint Hero. (And if you ever read the threads, we do all work together) There are also multiple opinions on BFS and a2sd, which allows for variations.
Blur has both a Hero and a Cyanogen based version, depending on which way they decided to go to get the supporting files for the main system.
The rest are obvious, and I don't feel like going into that much detail.
If we all followed your beleif, updates would take twice as long and not have nearly as many features. Rather than Drizzy, JustAnotherCrowd, Cyrowski, and myself all waiting for the one day we all have 2 hours to meet on google talk, share files, and build an update... JAC relelases an update, Cyrowski writes a new boot image, I restructure the way a2sd operates, and Drizzy comes along and adds in some new apps he restructured to work on that build. Some people choose to stop somewhere along the path and stick to that ROM, others go all the way down the road. If there were only one update, most Devs would spend half the day just telling people how to disable, remove, or add the feature they integrated.
I just dont see how less is more in this case. If you don't like all the updates, do what I do. I have the ones I actually read followed, and I only ever take a quick glance at the first page of posts before checking those. If I miss anything important, it is only ever by a day. If it's that important, it inevitably gets bumped to the first page long before it becomes so old that I surely learned it somewhere else.
*end informed response*

twistedumbrella said:
*end informed response*
Click to expand...
Click to collapse
Hehe.
Okay, I get that there's a matrix of every possible version of Android against every different sort of UI (ie Hero+Donut, Blur+Cupcake, etc). My shortlist is obviously too short. But it's difficult to pick out, for example, the best Hero ROM. And I can see the same thing happening with Blur as it becomes more and more in vogue.
Watching 3 different Hero versions, you might decide that ROM A almost perfectly suits your needs except for the bug that only got fixed in ROM B. And ROM C has both the features and the bug fix, but has an ugly custom UI somewhere. So then you think to yourself "why don't I just make package D?". The only way you'll know anything for sure is to spend time trying out however many different ROMs knowing very well that there's a chance you'll be forced to compromise. The only differences between many of these ROMs seems to be the Android version, pre-installed applications and custom kernels.
I know I came off fairly irate and impetuous in my original post. But when you can see all these talented developers producing so many different forks and reproducing so much effort, it can be very frustrating for an enthusiastic end user.

twistedumbrella said:
As a regular reader you should know that there are about 5 different versions of Hero floating around to base off of. There are 2 different versions of blur. There is also pulse, donut, cupcake, and variations on them.
Hero includes: Tattoo (a specialized mix of donut and sense), the sense ui merged with magic, the official release Hero, the non-official beta Hero, and the Sprint Hero. (And if you ever read the threads, we do all work together) There are also multiple opinions on BFS and a2sd, which allows for variations.
Blur has both a Hero and a Cyanogen based version, depending on which way they decided to go to get the supporting files for the main system.
The rest are obvious, and I don't feel like going into that much detail.
If we all followed your beleif, updates would take twice as long and not have nearly as many features. Rather than Drizzy, JustAnotherCrowd, Cyrowski, and myself all waiting for the one day we all have 2 hours to meet on google talk, share files, and build an update... JAC relelases an update, Cyrowski writes a new boot image, I restructure the way a2sd operates, and Drizzy comes along and adds in some new apps he restructured to work on that build. Some people choose to stop somewhere along the path and stick to that ROM, others go all the way down the road. If there were only one update, most Devs would spend half the day just telling people how to disable, remove, or add the feature they integrated.
I just dont see how less is more in this case. If you don't like all the updates, do what I do. I have the ones I actually read followed, and I only ever take a quick glance at the first page of posts before checking those. If I miss anything important, it is only ever by a day. If it's that important, it inevitably gets bumped to the first page long before it becomes so old that I surely learned it somewhere else.
*end informed response*
Click to expand...
Click to collapse
twisted your roms are always the most polished and daily functionable
i appreciate your input on these forums as well as drizzys and jac's
im glad there are multiple possibilities so i can see which one runs the best for my intended uses
party a may use their phone for internet texting and facebook
when party b may use their phone for calls email and business
party A is using XXXHerorom that runs his needed functions the quickest and most efficient way possible
party b is using XXXherorom that runs his needed functions the quickest and most efficient way possible

Unfortunately each Rom runs differently on each phone. My friend has the blurry screen problem while I dont. He can only run a few selected roms some of which doesn't do what he wants to do. I have gone though about 30 different roms before settling on one and quite frankly I think its pretty fun. I am on the bleeding edge of. techology.
I wish I would make a Rom. I have so many ideas for one.

The concern about multiple builds makes sense, but other folks have mentioned that different builds fix different things.
I've tried many of the Hero flavors, but sadly (unless I simply missed it) none of them have fully gotten bluetooth to work. I prefer using bluetooth for calling, and so far only Cyanogenmod's roms seemed to be able to nail this on the head. It's what I've been using for quite some time, and has proven to be the quickest and most stable.
It would be great if they all worked on just one version of the Hero rom, but it won't happen. Just imagine how many more are going to pop up when the official SenseUI shows up for the Saphire.
Eh

I completely disagree with the OP. Everyones needs are different and having a build thats just right for you is a luxury that you wouldn't get on most other types of phones. I really don't see an issue with having multiple builds even if they are fairly similar. Its not like we are wasting development time, there is no downside. Some may argue it makes it harder for users to find a good rom, but the bottom line is anyone who is flashing their android phone has an interest in technology and is going to enjoy trying out different builds. And once you've tried a few builds you get a pretty good idea of what your looking for in your ideal build making it much easier to choose. Using your Linux example, between work and home I use 3 different distributions everyday, the reason being each has strengths that make it ideal for specific applications, its not a problem or a mistake, its simply not everyones needs are the same.

Even for the novice like me it is not too hard to make sense out of what is available. I never liked when people do not read full thread before posting a question. Is it a problem of impatient generation or just a simple laziness? IDK.
Also, it has been a exiting jorney for me to learn everything about my phone and tremendous possibilities. Fear of bricking and yet the desire to try new stuff.
There are useful bits and pieces in almost every thread except yours, sorry to say that. There is nothing that can replace user's feedback and their own disoveries that are not necessarily coming from devs or people remotely in the field of android development.

Cease the proliferation of similar ROMs!
Click to expand...
Click to collapse
I also disagree with this thread. More choice is better for everyone!
Also if there are 2 similar roms, as a user rather than a dev you can still take the bits you like from both and make it your own.

jokeyrhyme really? have you made any roms or customized anything for your personal use? if so did you like it? if not, how come you didnt make one custom rom? is it because you dont know how or just rely on others to do it for you? there are soooooo many ppl with different "styles, perceptions and ideals" that one extra rom might be their next rom of choice!! whats wrong with a larger amount of variety? who gives you the right to try and call everyone out when they are the ones spending the time to learn, make and fix all the bugs for everyone when it started off for them selves?!?!? this thread is a joke and is taking up space in development. request for it to be moved to the trash or general. which ever is easiest.

WTF?
Ok at this point i'm kinda getting sick of this whole android forum. Way to much fighting, ignorance, complaints like damn who gives a **** (sorry just vex) who does what or doesnt do what or makes what or doesnt make what. If you dont like something...move onto the next. I mean those who alert the devs/cookers (whatever you choose to call them ) to issues with the rom only for the betterment of the rom are in the right. But when i see dumb **** like "this person's rom does this and that" i get pissed..just reflash that rom sit down shut up and think about that little life of yours that obviously is worthless since you can spend time downing people's work and yet you can make a rom or troubleshoot a rom on your own. Y'all need to relax yourselves find **** that works for you and stick wit hit. If it aint what you want..move on silently. dont fault the creator just move the hell on. Dont post dumb threads like this and most off DONT SAY ****!!! it's these very same forums dedicated to development of our devices that make our devices that much more amazing so dont flood the forum with dumb ****!!!. Show respect to our developers, give em props for taking time out of their lives to make our android experience benificial and super amazing.

I also disagree with OP's sentiment. I'd rather there be as many ROMs as possible than to have my choice restricted to a handful.
And daeshawn you're right, some people are so rude and unappreciative. I just ignore the douchebags and try to contribute as positively as I can.

I completely understand what you're saying. These forums can be really overwhelming at first. But honestly, I enjoy switching between different builds of Android just to see what they're like. Some people want APPS2SD, some don't. Some people want to split FAT32/EXT3/Swap, some don't. There are simply too many combinations for a small set of ROMs to handle.

sigh..... guess well never find the middle of the tootie pop

If a middle ground were to exist it could go something like this:
Everyone can do whatever they want as far as their ROMs go. Perhaps, for new people who might otherwise be overwhelmed with choices, the Q&A (if it doesn't already) could link to a few long-running, stable ROMs that typically accomplish the very basics. And once people get a chance to try those, figuring out what you want becomes a little simpler and the tons of threads start making some coherent sense.
It's like "which is better, Cyanogen's rendition or Enom's" and the answer, for a lot of people, is that it depends. There might be similarities and both ROMs ultimately accomplish a lot of the same things (root, A2SD, compcache, linux swap, etc.) but preferences remain. I like one, you like another. There's no reason both developers, each of whom presumably likes their own, can't go on making what they want to make and offering it out there. More over, the experienced users are already aware of the alternatives.
It's really newbies that might find the choices overwhelming.
As for reinventing the wheel with every ROM, many threads already provide credit to a variety of developers, so clearly the work gets around. Just because they all do it at their own leisure and in the order of their choosing doesn't mean the developers are living in closed bubbles. Maybe the colab work that needs to be done is already being done even if it's not obvious. More over, even if two ROM cookers decide to both implement similar changes apart from each other, the choice to do so is totally in their court. Their time and their money and their brains.
There is kind of, for me, a question of stability. I have a fair confidence, for example, that Cyanogen is not going to drop Android development entirely any time soon and his ROMs will continue to exist with updates and bug fixes. Other developers share this sense of stability, but it's not an all around type of thing. There are ROMs out there now that are interesting because they are cool and new, but will they still be maintained a year from now is another question entirely. And I think that's a legitimate concern and reason for wanting at least a few long-lasting ROMs. Because, essentially, if 5 devs work on something and one gets bored, there's still 4 left. Conversely, if there's only one dev and he/she decides they're done, now what?
Just my $.02

I've no issue with the number of roms.
however, what is missing is a simple resource that lists them and a summary of features.
trying to wade through all the post to see what does what is a total ball ache. I think this is more the problem than the number of roms.
An up to date one pager that showed the current status of what was available would be perfect.

Well, I totally deserve all the hate this thread has brought my way.
*bows head in shame*
I agree that if there was ever a place to test out dozens of difference features, then this is that place. So it's totally appropriate to have as many different ROMs as there are demands for different features and such.
I do think more could be done to draw new users towards stable and long-term projects, as has been suggested by sleepykit and moa77. Maybe that's really the solution I was after. An update to the listing or something perhaps?
Sorry about being a poohead, I'll be good now.
*hugs all round*
PS. I changed the topic title to be less evil and more open.

Why are the devs shying away from cornerstone?

Is it me or does it seem like most of the devs are shying away from cornerstone? Yeah, they have nightly cornerstone build, but it's completely unsupported and, according to the devs, is just for fun.
Why are the devs so hesitant to include cornerstone in their builds?

Lack of experience, first time most devs have seen ics, more work, etc.
Yeah its cool and has great features but there isn't an uproar by the users to have it now.

There is a lot of desire for this damn feature, but most of the threads are by people who don't look for the original threads.. etc. I agree though, most devs probably want to fix ICS first THEN work on extra features. IMO though, this multi-task feature should have been a big update for tablets.

goodintentions said:
Is it me or does it seem like most of the devs are shying away from cornerstone? Yeah, they have nightly cornerstone build, but it's completely unsupported and, according to the devs, is just for fun.
Why are the devs so hesitant to include cornerstone in their builds?
Click to expand...
Click to collapse
I'm interested as well, though I can understand some hesitation. I had heard that it has been a WIP for a while, I don't believe it's a close to a finished product yet. IIRC there was just a big code rewrite for it and the window swap feature isn't included currently. It's a shame really, I think the majority of the development is going to be with onskreen for a while until they can put out a stable code base. Either way, there are nightlies now.. its only been a few days.

goodintentions said:
Is it me or does it seem like most of the devs are shying away from cornerstone? Yeah, they have nightly cornerstone build, but it's completely unsupported and, according to the devs, is just for fun.
Why are the devs so hesitant to include cornerstone in their builds?
Click to expand...
Click to collapse
You would think that if cornerstone requires so much work why not do it from the start instead of slapping it in after all the bugs are ironed out then breaking evreything.
Oh and i wil be ssticking with the cornerstone roms even with all the bugs. Of which there arent many... if you count a text file one bug report.
Mostly i think it will be the people who like a challenge and dont mind if your tablet reboots or you are typing on the keyboard and the virtual kbd is up.
I personally love it and CM9 together it's like a damn hallmark card.
Sent from my Transformer using Tapatalk

its not a feature everyone wants and how many versions with onskreen do we really need? kinda boring if they all do it. although i personally think its the best feature on my tf ive used!
early days and i know jcarrz1 thinks its a cool feature but from what was said it would be done as a seperate rom from Frozn........ IF he does it and IF asus ever get his charger back to him lol.

Exactly what is the difference between the EOS and CM9 roms with cornerstone at the moment? I'm going to flash one of them over the weekend to play with cornerstone, but I'm not sure which to use now..

I am willing to bet that the new tablets coming out this year will have something like cornerstone, but probably much much better.
Windows 8 is coming to tablets. Windows itself is a multitasking OS due to the "windows".
Android will come up with something of their own too, they have no choice.
This reason alone is enough for me to ditch my dual core tab and get a more powerful one later on.
(because I know this is coming)
And no, tablets have not hit a plateau at measly 1.2ghz dual core. You won't convince anyone with that other than your grandmother.

asdfuogh said:
Exactly what is the difference between the EOS and CM9 roms with cornerstone at the moment? I'm going to flash one of them over the weekend to play with cornerstone, but I'm not sure which to use now..
Click to expand...
Click to collapse
Go with EOS + v9 gapps. A lot more stable and a lot less bugs. The onscreen keyboard even goes away when you plug into the dock.

goodintentions said:
Go with EOS + v9 gapps. A lot more stable and a lot less bugs. The onscreen keyboard even goes away when you plug into the dock.
Click to expand...
Click to collapse
Weird cause for me I had lots of crashes with eos. Although I do agree about the dock. Cool I will check it out.
Sent from my Transformer using Tapatalk

I personally prefer waiting for an official Google solution (in Jelly Beans?), but maybe if cornerstone is incorporated in one of the common ROMs I'll try it just for fun.

i'd wager most of the devs are just chefs.
Sent from my SGH-I897 using xda premium

goodintentions said:
Is it me or does it seem like most of the devs are shying away from cornerstone? Yeah, they have nightly cornerstone build, but it's completely unsupported and, according to the devs, is just for fun.
Why are the devs so hesitant to include cornerstone in their builds?
Click to expand...
Click to collapse
Currently?
I would love to support it. I really would.
However in its current state, cornerstone introduces a wide range of bugs.
There are only so many hours in a day I can dedicate to rom development, and unfortunately cornerstone doesn't make the cut.
-- solarnz,
Lead developer and founder of Team Eos.

solarnz said:
Currently?
I would love to support it. I really would.
However in its current state, cornerstone introduces a wide range of bugs.
There are only so many hours in a day I can dedicate to rom development, and unfortunately cornerstone doesn't make the cut.
-- solarnz,
Lead developer and founder of Team Eos.
Click to expand...
Click to collapse
From what I understand, the cornerstone source is a mess? Anyone have any examples of what is wrong with the cornerstone source and why it conflicts with Android in such a way?
If it is so messy, then it would seem some of our better devs here could (if motivated) write their own windowed overlay, similar to but not based on Onskreen. That way the code would be much cleaner, but it would only be a matter of time to devote, which I have high suspicions that the better devs here have very little of..

If anyone follow Steve Kondik on Google+,
He made this comment about cornerstone
Steve Kondik - Running this on my 10.1 right now. Definitely needs a bit of a tune-up, but lots of potential and I look forward to having it in CM9
Click to expand...
Click to collapse
This was a reply to his Cornerstone comments.
Not sure if this Dianne Hackborn is part of the Conerstone dev team or not
Dianne Hackborn - Okay, let me please please beg you not to do this. I can guarantee you this introduces all kinds of application compatibility issues. We work really hard to give our developers a consistent environment where their apps will operate correctly across all the devices Market runs on, not being impacted by negative reviews from bad devices that they should not have to deal specially with.
If you start making your own distributions of Android behaving in such fundamentally different ways, I suspect we are going to need to start doing things to prevent you from impacting our app ecosystem. I'm not sure what, but I could imagine things such as restricting how users can interact with Market apps on these devices (not allowing reviews or such).
We have let a lot of things in this area slide -- for example to be allowed to include Market on your device you are supposed to fully pass CTS. However, if you start really diverging from the core Android platform (I would argue this takes you well into the realm of a fork rather than a customization) then some deep issues are going to come up about how we handle these custom builds.
We have been putting a lot of thought and work for a number of years into how to let Android applications run on increasingly diverse and dynamic screens. Doing this correctly, without impacting our app developers in a negative way, is a really challenging problem. I also think it is something that needs to be done at the mainline platform level, not as a customization, because doing it right is going to require new well defined interfaces with applications for them to interact with it, possibly starting with just a facility they need to use to opt in to it.
Click to expand...
Click to collapse

baseballfanz said:
If anyone follow Steve Kondik on Google+,
He made this comment about cornerstone
This was a reply to his Cornerstone comments.
Not sure if this Dianne Hackborn is part of the Conerstone dev team or not
Click to expand...
Click to collapse
Diane Hackborn is part of the Google team
Does this mean that 'open source' Google doesn't like people diverting from their source too far? She says cornerstone alters the way Android OS functions..cornerstone is almost another fork on the source tree than a customization on the Android OS (wow) I had no idea it was that involved..and apparently, Google does not like cornerstone (or at least some of the higher-ups that work for Google).

[Q] Cyanogenmod vs. Liquidsmooth (JB 4.2.1 Comp)

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

[Q] Question about maintaining ROMs

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.

New to Android ROM dev, have much kernel/driver development experience. Need protips

Hi, I started researching and messing with custom ROM/Kernel development 3 weeks ago. I've successfully compiled the kernel for my s5 neo Exynos 7580/MALI 200 (no hardware acceleration yet but I'm a kernel developer and reverse engineer so I can get that working given enough time, and have chosen all the apps I want to include in my first ROM. I made the ROM into and Odin flashable image and bricked my phone because I didn't adjust for the differences between the s7 and the s5 neo's power requirements. I bought 3 more S5 Neo's though, fixed the kernel, and all 3 devices have been 100% stable for 3 days with some minimal usage to test all the features. I am a kernel/driver developer, and as of now have taken over a dozen kernel MOD's from other people's kernels, and applied them to mine. There are more mods I could extract and apply, but I don't care to add them because I don't think they suit the goals of my ROM.
I would like to know things that aren't documented or easy to find that I will have to work with as I progress in the complexity of ROM development. So most of my ROM right now is apps I extracted from other ROMs and the play store and f-droid. But I am a coder and am working on my own settings app is suited for my ROM, including providing all the functionality of the root requiring apps I have installed now, also, I have about $80 of premium paid apps in my current setup, and want to put all the things they do into my custom settings app. I eventually plan on turning this into an android fork but for now, I'm starting out with baby steps to learn at a pace I can handle without overloading myself.
Please, any ROM/Kernel/App developers provide me any things you have learned from experience that I can't find on google and will be useful to know for my project.
Also, I have 2 questions. A) is UBER GCC better than Samsung eabi GNU compiler collection compilers?
B) Is deodexing really so good? because I've looked at the pros and cons and I don't think deodexing is worth the tradeoffs, but I feel like there's a reason almost every custom ROM does it. I know the tools to deodex ROM's don't work on Samsung android or other not AOSP based ROMS, but I already wrote a python script that deodex's my phone perfectly, I tried it, but I wasn't happy with the differences in response time and boot time and I believe it was causing a lot more memory to be used although I'm not sure why. Is deodexing better than I think it is, or is it just the cool thing to do for people who don't know how it really works?
Links, tips, polite criticisms, are all welcome. Also, this is my first post and I'm pretty sure these forums are the only place I can find people with the skill level to do these things well or at all.
I see some very knowledgeable people post here so I hope they find my post and reply with some tips. I tried the Freenode android channels and they are all plebs. They actually made fun of me for claiming I could make a custom ROM for this phone, they said it's impossible, and in 3 hours I had a screenshot of my about device showing my own compiled kernel running on my phone, no mods, just proof this been stuff is doable. Then I told them off about pretending to be experts but really knowing nothing and calling me a fool because they are too ignorant, then I left all 3 Freenode android channels and came here. In the channel for android ROM's and rooting, 99% of them were people who needed help rooting their phone or installing a custom ROM, not people I can learn from and grow to become a member of their community like I hope to do here.
if you didn't stop reading by now because of tl;dr, thanks for taking the time to read my post and please respond if you have helpful info. I've already read all the stuff I can find from google and these forums, I'm looking for the tips that aren't documented or that I may have written off as not important.
-zerorax, AKA Will O
Also if anyone wants to join forces to help me, I'm open to contributions and will give credit for them where it is due.

Database Info

welcome