Related
Over at Desire development we had a great idea. The idea is to organize ROMs for all phones on a website. Chefs can post their ROM's features, different versions, etc. The website will allow users to compare different roms using a sophisticated comparison tool. Much like this: h t t p://clips.srious.biz/WindowClippings_bd156b9be2ef4749a0bac8ca541cb0ee.png
Currently, it's really hard to find a decent ROM. There is no place where you can find different ROMs and compare their features.
I am wondering if there is any incentive for chefs to maintain their ROMs on such a website.
As new ROMs are released every day, and there are so many phones, it is really hard to keep track of for staff of such a website.
I will build this website myself if there are enough people to support this idea.
art0rs said:
Over at Desire development we had a great idea. The idea is to organize ROMs for all phones on a website. Chefs can post their ROM's features, different versions, etc. The website will allow users to compare different roms using a sophisticated comparison tool. Much like this: h t t p://clips.srious.biz/WindowClippings_bd156b9be2ef4749a0bac8ca541cb0ee.png
Currently, it's really hard to find a decent ROM. There is no place where you can find different ROMs and compare their features.
I am wondering if there is any incentive for chefs to maintain their ROMs on such a website.
As new ROMs are released every day, and there are so many phones, it is really hard to keep track of for staff of such a website.
I will build this website myself if there are enough people to support this idea.
Click to expand...
Click to collapse
I know NRGZ28 cooks a lot of Roms for a lot of Devices and i do not think he would have time to be posting anywhere else, Plus i do not think its right to compare Roms to each other, last thing a cook wants to see is his hard work being being compared and told its not as good as X its up to each individual to see what they like the best as the same ROM can run differently on the same two devices depending on where they live how old is the battery what they are running, just my 2p worth
lufc said:
Plus i do not think its right to compare Roms to each other
Click to expand...
Click to collapse
How do you pick your ROMs? Randomly? Isn't that what you do with any other piece of software? Pick the best? If they do not want their roms to be compared to others, there is no reason to post them.
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).
Guys,
I have forked some aries AOKP device and CM9 Kernel repos.
As I stare at the screen, is there any possibility of assistance.
Also, if anything, can you tell me where you guys started in order to port from aries.
I figure that this is better than trying to port a rom. (Using source)
I guess as I have stared at Acid repos, i have learned a bit, and I think I might be ready to take on such a project.
Again, any help would be appreciated. Especially from our 2 heroes, Max Fierke, and Bryan Hundven, who have helped us turn our phone's development rate in a few months from 0 to 10(based on a scale of 10).
What I plan to do is add the defconfig from the existing gb source code. Later, I will start modifying the source files to our needs.
anyone?
airfluip1 said:
anyone?
Click to expand...
Click to collapse
I'm not from team acid but try looking at vibrant/i9000 ICS source and study it as their phone is similar to ours.
-sent from an UNBRICKABLE force
I don't think we should bite off more than we can chew.
Have you tried sending the members a pm? That might be more effective.
adobrakic said:
I don't think we should bite off more than we can chew.
Click to expand...
Click to collapse
are you portraying that I can't do it.
Well, i want to learn if anything.
Also @ trolls, i am just playing with adobrakic, not being mean.
No, that's not what I was implying. If you, or other members, have the time to devote to this then great. But I feel that Max, Bryan, and the majority of other developers of our phone, are already working with a lot as it is. Perhaps our efforts should be concentrated on those ROMs at the moment. That's just my opinion, however.
Sent from my SGH-T959V using XDA
adobrakic said:
No, that's not what I was implying. If you, or other members, have the time to devote to this then great. But I feel that Max, Bryan, and the majority of other developers of our phone, are already working with a lot as it is. Perhaps our efforts should be concentrated on those ROMs at the moment. That's just my opinion, however.
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
Every week someone requests aokp, ics, lewas, miui, etc...
Everyone on team acid has their own skill sets and projects. We try to work together to complete big projects.
The other side is like I've said before. We all have our daily lives to live as well.
Everything we've learned about the phone is in the device tree for cm7 and our initramfs. To explain our phone would be to walk through kernel and device tree commits and by reading the source.
I'm still working hard on porting the device specific changes that make our phone work to the aosp samsung gingerbread branch. After that is done, I'm going to attempt to merge and port to the ics branch in that tree.
Raver also has some diffs for ics aosp.
So as we progress, I see no harm in anyone else trying to make their own attempts, but if we have more people help for common causes, we can reach goals faster.
If you want to help, just fork the git repo of choice, commit your changes, push your changes, and do a pull request. If the change(s) look good, we'll merge it. If not, we won't harsh you. But we will help guide you to getting your changes merged.
Sent from my SAMSUNG-SGH-I717 using xda premium
bhundven said:
Every week someone requests aokp, ics, lewas, miui, etc...
Everyone on team acid has their own skill sets and projects. We try to work together to complete big projects.
The other side is like I've said before. We all have our daily lives to live as well.
Everything we've learned about the phone is in the device tree for cm7 and our initramfs. To explain our phone would be to walk through kernel and device tree commits and by reading the source.
I'm still working hard on porting the device specific changes that make our phone work to the aosp samsung gingerbread branch. After that is done, I'm going to attempt to merge and port to the ics branch in that tree.
Raver also has some diffs for ics aosp.
So as we progress, I see no harm in anyone else trying to make their own attempts, but if we have more people help for common causes, we can reach goals faster.
If you want to help, just fork the git repo of choice, commit your changes, push your changes, and do a pull request. If the change(s) look good, we'll merge it. If not, we won't harsh you. But we will help guide you to getting your changes merged.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Yep you're right bhund and completely off topic u got the Note! Lol bad ass! Lol
It would be nice if someone put up some descriptions on how to build AOSP/CAF for Falcon. I think it would help development allot defiantly now because of al the drame caused by CyanogenMod Inc. by not respecting @dhackers29´s hard work, and instead of helping doing the opposite.
CyanogenMod was fun but economics tend to destroy everything, we need to move on now.
Hello everyone,
Over the past few years the custom ROM scene has been dwindling. The Nexus and Pixel devices are suppose to be the crown jewl of development but that has began to fade. I was thinking of committing to a new ROM for Pixel devices (and possibly Essential devices down the road) since these are the easiest to maintain. The ROM wouldn't be packed with the most features, but take an approach similar to Oxygen OS: only add meaningful features and maintain the AOSP look and feel. I would also make it a point to keep the ROM up to date with the latest security patches and bug fixes from Google (security and stability would be priority). I have quite a bit of development experience from the past and was wondering how much support and "want" there is for a project like this? Anyone who would be interested in a ROM like this just like this thread and comment any feedback/suggestions/questions. If there is enough support for this project I will commit to it but I want to gauge public response first.
Cheers,
Shawn
Edit: It's worth noting the project would be open source.
Edit 2: If you would like to be an Alpha Tester for this project visit the following post: Link
o/
Yes I've been saying this and it kinda sucks cuz I love flashing different roms , mods etc lol so a new rom for Pixel 3xl (my device) with features from various roms and being stable would be cool. Any requests feature wise I won't mind letting you know. Hope you do decide to make one soon. Thanks and good luck!
All roms welcomed!
Hell yea! So lacking right now in terms of ROMs for these devices.
c_86 said:
Hell yea! So lacking right now in terms of ROMs for these devices.
Click to expand...
Click to collapse
I would love another custom ROM that has support for 3minite battery given that I haven't been able to get it working on any custom ROM.
Sent from my Pixel 3 XL
I'd go for it. I would like to see something for oreo
It would be fantastic to have some more options. I came from Pixel 2XL to Pixel 3XL and the ROM flashing choices dropped, DRAMATICALLY. Luckily I've been getting my fill by testing for the AquariOS team, so that fulfills my need to flash regularly but it'd be great to see some more action in the forum. I'm sure there will be plenty of support for your decision, if you decide to move forward with it.
I'd love to see a really minimal and stable AOSP with a really active mod/flash community for those that like to add sprinkles.
Mos Def Interested!!!
It would be something I would be interested in for sure.
:good:
Of course. Variety is the spice of life.
Maybe you can figure out why Sprint devices can't send MMS.
I would like to see LOS. I used Cyanogen for years.
I really wish this could happen and be made possible.
Sent from my Pixel 3 XL
Shawn5162 said:
Hello everyone,
Over the past few years the custom ROM scene has been dwindling. The Nexus and Pixel devices are suppose to be the crown jewl of development but that has began to fade. I was thinking of committing to a new ROM for Pixel devices (and possibly Essential devices down the road) since these are the easiest to maintain. The ROM wouldn't be packed with the most features, but take an approach similar to Oxygen OS: only add meaningful features and maintain the AOSP look and feel. I would also make it a point to keep the ROM up to date with the latest security patches and bug fixes from Google (security and stability would be priority). I have quite a bit of development experience from the past and was wondering how much support and "want" there is for a project like this? Anyone who would be interested in a ROM like this just like this thread and comment any feedback/suggestions/questions. If there is enough support for this project I will commit to it but I want to gauge public response first.
Cheers,
Shawn
Edit: It's worth noting the project would be open source.
Click to expand...
Click to collapse
The biggest reason for lack of development is the cost of the device, I gave almost $1200 for mine, after the "insurance".
Going back to Nexus days, the things were less than half that price, hopefully the A series will bring some life back....
Alpha Testers
Hello all,
Thanks for all the positive responses and feedback. I am strongly leaning towards committing to the project but wanted to see how many people would be willing to be Alpha Testers for the project.
More information on the various ROM release types and what to expect in Alpha builds, visit: http://bit.ly/2Zz9Koa
Finally, if you are interested in helping test the ROM fill out the following form: https://forms.gle/ypr2yu9jbX6MwBZZ9
- Shawn
Shawn5162 said:
Hello all,
Thanks for all the positive responses and feedback. I am strongly leaning towards committing to the project but wanted to see how many people would be willing to be Alpha Testers for the project.
More information on the various ROM release types and what to expect in Alpha builds, visit: http://bit.ly/2Zz9Koa
Finally, if you are interested in helping test the ROM fill out the following form: https://forms.gle/ypr2yu9jbX6MwBZZ9
- Shawn
Click to expand...
Click to collapse
Just FYI, making people have a Slack account to participate is a no no, nothing else wrong with your application though
I have Slack, but it's only for work..I would rather not provide that. Any other way? Perhaps Telegram instead? Or give us an organization to use outside of our likely employers?
NepoRood said:
Just FYI, making people have a Slack account to participate is a no no, nothing else wrong with your application though
Click to expand...
Click to collapse
Thank you for pointing that out! I've adjusting the form, removing that question!
jbarcus81 said:
I have Slack, but it's only for work..I would rather not provide that. Any other way? Perhaps Telegram instead? Or give us an organization to use outside of our likely employers?
Click to expand...
Click to collapse
I have removed the Slack option from the form so you can fill it out now without any issue. For now we can just XDA Private Messages and go from there towards an alternative in the future.
Are you still working on it?