Ok everyone,
There's been alot of movement both forward and laterally on the vogue-android project lately, and while it's all been great I'm having some concerns.
There has been alot of forking lately of the project. Different builds are great and I can't encourage that enough, but with all of the changes, and great developments being made to the rootfs and kernel we are losing alot of what made this project going great.
There's such a jumble of builds, out there right now it's getting confusing for everyone. So please guys can we move the project back to centralization?
By that I mean build threads are for system images only.
Changes to the rootfs's and kernel's are fantastic, but please can we make a new thread just for those?
As well to all the kaiser guys. Don't get me wrong I think it's great that so many of these files are working so good for you guys but can you keep development of your port to your forum, so there's less confusion for the new people? I've said it lots, if any of the kaiser guys wanna port over the builds I've ported to kaiser's go ahead, but please post them in the kaiser forum.
I'll happily keep the google code page updated with new bundles, that have been tested and confirmed stable, that page is not for specific people's work only, but for vogue/kaiser files that can be considered the standard files to use.
I support this.
well put. i feel the exact same way. i've given up till a bundle comes out cause im confused what is the newest or if it will work(not a fan of the kaiser now that they took over). I'm really hoping for more development on the android rom but im a script kiddie and no developer.. unfortunately
thanks for bringing this up
I could not agree more!
I've actually returned to running WinMo on my phone because I've become so lost in the Android project. There's so many different forks out there, and all sorts of random files being uploaded to Google Code, I have absolutely no idea what is what anymore.
It was going really well when vilord and dzo were working on it, now suddenly it seems both of them are out of it and the "vanilla" Android 1.5 builds are no longer being worked on. There hasn't been a basic "system" update in nearly a month now.
And to make matters worse, there's no clear explanation of what's what anywhere and nobody is posting proper change logs. So all these new files keep popping up with no word on what they're for and what's changed.
I just want to run Android on my phone, with no stupid skins, UI replacements or massive customizations of any kind... and I don't know how to do that anymore.
I'm not really sure why all this work seems to be focused on customizations right now anyways, when there are much more important things to work on like Bluetooth, aGPS, and a flashable ROM.
Yes, this is most definitively needed, not to stifle anyone's creativity, but to allow the maximum number of people to enjoy the project. Otherwise it's far too possible that all the various ports will just turn people off to Android, and it's far too important to allow that to happen. I've already asked mssmison to post whole, relatively stable packages so people don't get overwhelmed with all the various components and builds. Maybe a re-fresh of the packages every 2 or 3 weeks, along with the testing packages for all you brave souls to make it more user friendly.
I'm going to re-organize the google code page for vogue tonight so it should be more clear for everyone. vilord isn't out of the project, he just is moving
I've cleaned up the google code page a bit, I've depreciated some older downloads and the older bundle.
I keep all my builds separate and off the vogue-android page too keep it clean and focused on the main bundle there which is android-1.5-x. The test rootfs.imgs that I put out are only for testing purposes and are my personal experiments related to hero and they stay on vogue-hero. They do not apply to non hero builds and I try to state that in the threads I started for my other two non hero builds. I'm not supporting squashfs right now and I'm not going to be posting builds in squashfs right now. If people think that squashfs is the way to go then all images need to be in squashfs including android-1.5x builds. That would avoid the main squashfs rootfs/kernel/initrd fork thats going on with people downloading the squashfs base files. I don't support kaiser wifi builds of my hero images because they don't work for the vogue. I'll be taking down all kaiser/squashfs related files on vogue-hero until further notice and create vogue bundles of the files that work with each build.
i agree about too many different builds and files mixed together, it's really confusing to an average user like me who's sorta new to android. you devs should package up a zip with all the most stable, needed files for you specific builds so we can't mess up and download something that might not work right. myself i use my phone daily and for work, so i need stability.
mssmison said:
Ok everyone,
There's been alot of movement both forward and laterally on the vogue-android project lately, and while it's all been great I'm having some concerns.
There has been alot of forking lately of the project. Different builds are great and I can't encourage that enough, but with all of the changes, and great developments being made to the rootfs and kernel we are losing alot of what made this project going great.
There's such a jumble of builds, out there right now it's getting confusing for everyone. So please guys can we move the project back to centralization?
By that I mean build threads are for system images only.
Changes to the rootfs's and kernel's are fantastic, but please can we make a new thread just for those?
As well to all the kaiser guys. Don't get me wrong I think it's great that so many of these files are working so good for you guys but can you keep development of your port to your forum, so there's less confusion for the new people? I've said it lots, if any of the kaiser guys wanna port over the builds I've ported to kaiser's go ahead, but please post them in the kaiser forum.
I'll happily keep the google code page updated with new bundles, that have been tested and confirmed stable, that page is not for specific people's work only, but for vogue/kaiser files that can be considered the standard files to use.
Click to expand...
Click to collapse
+1 to this! It's getting cluttered and confusing... BUT AWESOME!
stickus said:
+1 to this! It's getting cluttered and confusing... BUT AWESOME!
Click to expand...
Click to collapse
is it looking better now on the google code page?
whatever is in that new base files package really sped up my build from zen, ill tell you that much, now my phone recieves calls too. the only thing i notice is im back to the old style button map settings for adjusting volume and waking up the phone and such?
things look a lot cleaner on the google code page now... just DL-ing the new bundle you posted and we'll see how things go from there. Glad to hear that that old button layout is back, not really a fan of the newer one.
all i know is there is no lag to my build at all now, WOW...nice work guys!
fixxxer2008 said:
whatever is in that new base files package really sped up my build from zen, ill tell you that much, now my phone recieves calls too. the only thing i notice is im back to the old style button map settings for adjusting volume and waking up the phone and such?
Click to expand...
Click to collapse
All thanks to the bundle of files go to pmos, him and no one else. I just put together the system.
The button thing was accidental, however I have had alot of problems with my camera button not working intermittantly, we are working on a way of it being user selectable at boot.
I would also agree that some sort of organization is definitely needed. I think that system image threads should be condensed or organized in some way also. Having 15 threads, each with not too much information on what the build actually is, and info on the new update on page 15... just makes it hard for everyone. New comers and people who are experienced and trying to help others.
TheKartus said:
I would also agree that some sort of organization is definitely needed. I think that system image threads should be condensed or organized in some way also. Having 15 threads, each with not too much information on what the build actually is, and info on the new update on page 15... just makes it hard for everyone. New comers and people who are experienced and trying to help others.
Click to expand...
Click to collapse
There are 5 threads for builds. One for the kernel.
welll my phone is still running good today with that new bundle that was posted last night.
im still getting used to the old style button mapping but to be honest i like it better this way.
I think this post goes in the wrong direction.
The best thing of Android is that devs from different mobiles are working toguether to improve our phones.
I´m a polaris user and in the development of android for polaris developers with different phones help a lot
What we need is an Android section as it´s being petitioned in order to develop all toguether. Of course with organization.
Let´s think as Android and not only as vogue
iseeka said:
I think this post goes in the wrong direction.
The best thing of Android is that devs from different mobiles are working toguether to improve our phones.
I´m a polaris user and in the development of android for polaris developers with different phones help a lot
What we need is an Android section as it´s being petitioned in order to develop all toguether. Of course with organization.
Let´s think as Android and not only as vogue
Click to expand...
Click to collapse
I agree but remember this is a vogue forum, so for the average user that comes here, they have a vogue. If you guys have a polaris dev get him to contact me and we'll look into making the bundles work right with your phones as well.
Again this is why I posted the poll to move the dev to another forum where we can have proper organization
Related
Just a thought as I'm having trouble locating up to date builds and differentiating between the builds for the vogue.
Why not zip the system files with a read me file with maybe the date and developer/editor name or contact info?
I think this will keep testers more up to date, and the feedback will go back to the right developers.
gnovak99 said:
Just a thought as I'm having trouble locating up to date builds and differentiating between the builds for the vogue.
Why not zip the system files with a read me file with maybe the date and developer/editor name or contact info?
I think this will keep testers more up to date, and the feedback will go back to the right developers.
Click to expand...
Click to collapse
the readme is a good idea. i did that for a couple builds. as far as the dates go the date the build is put up is on the google code site and if you click on the description it says who uploaded it. i also have threads for my builds. and mssmision has one thread covering all of his and vilord has his thread which is the google ion android 1.5 build. If you want i'll add the names to the descriptions in the vogue-android google code page.
yeah maybe adding tags to builds with developers names to the google code page might make it a little more oganized.
I think with threads theres always alot of clutter and new builds get over looked, not really getting the exposure they deserve.
I sell smart phones for Sprint and for Microsoft, this android - Vogue port is amazing and I would like to get more people involved. But i cant do so until its a little more accessable to the common user.
This is a looong overdue set of ideas. If this was JUST a hobby for you guys the disorganization would be ok (I guess) but since your sharing them with the world, anything you can do to make the builds more user friendly is great. It also helps user report bugs, glitches with more precision, and insures that they have a really awesome experience with your hard work.
gjbnh said:
This is a looong overdue set of ideas. If this was JUST a hobby for you guys the disorganization would be ok (I guess) but since your sharing them with the world, anything you can do to make the builds more user friendly is great. It also helps user report bugs, glitches with more precision, and insures that they have a really awesome experience with your hard work.
Click to expand...
Click to collapse
You do realize that you can report bugs on the Google code pages. There has been a lot of hard work getting to where we're at now. We are a group of people from all around the word coming together make android run on the vogue.
And i think what gjbnh is trying to say is that we would like to collaborate with you and maybe make it easier for other people to help as well.
The google page is an AWESOME idea, but truth be told, not everyone goes there to download android on their phone.
Direct links to older versions are sprawled out all over the internet, especially this forum.
When someone runs a search on "Vogue Android" the first three results are going to determine whether they will bother or move on.
gnovak99 said:
And i think what gjbnh is trying to say is that we would like to collaborate with you and maybe make it easier for other people to help as well.
The google page is an AWESOME idea, but truth be told, not everyone goes there to download android on their phone.
Direct links to older versions are sprawled out all over the internet, especially this forum.
When someone runs a search on "Vogue Android" the first three results are going to determine whether they will bother or move on.
Click to expand...
Click to collapse
I understand that and I'm all for organization but it seems right now we might be moving forums and hosting. I agree that from the perspective of a new person coming here and wanting to try android on their vogue/kaiser/polaris that it does seem a little confusing.
What kind of collaboration are you looking to do? dzo and vilord are the owners of the vogue-android google code page and it's their work which has put vogue android on the map. Aside from repackaging the builds with better more complete packages and a readme with clear instructions there isn't really a lot more that we can do. We have the forums here for questions and you can report bugs at the google code page too. I think the vogue-android page is set up quite nicely. The download page can be cleaned up a bit but the main bundles are right up at the top. You have mssmisions package, the google ion package, and the vogue-hero package.
This post is a poll for users who like to test different ROM's to find out which one will be the "winner" over their device. Also it is used as a quick guide to find out which of the "ECLAIR ROMs" are the highest rated of the releases for users (and devs) to pick from the HUGE list of ones available rather than flashing, testing, re-partitioning, then re-flashing, etc etc.
I am not at all trying to flame, bash, or put down anyone's ROM that is less developed than others. I myself as I believe others like myself are interested in finding out which of the great ROM's released are by popular vote more exciting to use than others.
I also understand that different users have different opinions, and I as well as many others I know personally prefer totally different ROM's to use on our devices. So on that note, let everyone know of the list which ROM you believe gives you the best experience on your G1 & Mytouch3G / Dream & Magic devices by popular vote.
If I have left off any other ROM's that may be GREAT but just not posted in the poll please feel free to express the name, who it's by, and why you love it!
Thanks for your vote, I believe this will be of a lot of help to others like myself.
Hopefully this post is not considered "spam" and is more for an informational tool
This should be posted in the Dream/G1 Discussion board...not the G1 Android Development section...
guitarfreak846 said:
This should be posted in the Dream/G1 Discussion board...not the G1 Android Development section...
Click to expand...
Click to collapse
Thanks for the correction, however most ROM users, and Dev's don't use the Dream/G1 discussion forum and i believe the intentions of this post would fall on deaf ears.
Ive found my leo to be more entertaining than my dreams, the 2.5 sense UI rom is a beast on it too.
Seems to be pretty varied so far.....
zimphishmonger said:
Seems to be pretty varied so far.....
Click to expand...
Click to collapse
Yes it does, You can see where the most excitement is drawn from which is neat... The poll has multiple answers enabled which I input due to the fact that myself like probably others like more and enjoy more than only 1 ROM, So if you do like 2 out of the bunch or anything feel free to express it and vote for another
You spelled "ratings" wrong in the title.
Remember, first impressions last a life time.
guitarfreak846 said:
This should be posted in the Dream/G1 Discussion board...not the G1 Android Development section...
Click to expand...
Click to collapse
True indeed, this thread is not specifically dev related, but I find it to be very helpful and informative for those of us that are flashing these roms, gives the user an better idea of what to choose from when looking for a good eclair duplicate. And most users, like I, hardly ever visit the discussion board because they are so busy checking the dev forums for new releases and updates. Therefore I find this thread to be placed in a perfectly good position due to to its purpose. MODS please consider before moving.
Yay! Somebody finally picked up my idea koo well
lets see which rom is the best
This should be reset tho every like week or so, cause constant changes happen and one gets crazy awesome over night..so you should have in the title sometimes (I reset this poll on 1/27) so ppl no to see new results...
wrong info
I use [email protected] Eclair 2.1, with spanish kernel, this is the faster 2.1 ROM for Dream and Sapphire.
I´m waiting for a new update, with N1 features and G1 Dream full working.
http://www.htcmania.com/showthread.php?t=90749
Nice Idea, this poll.
But, i think, there should be also a Poll for the Functions needed, not only which Eclair ROM...
So, for me the Killerfeatures are:
WLan/WiFi working
Bluetooth working
Exchange Active Sync working (including Contacts, Calendar, E-Mail)
Sound working (also with Navigation App like Sygic, nDrive, ...)
Not so urgent, but would be nice:
Google Sync working
Tethering WiFi/USB working
Browser with Flash Support working
Camera working (Pictures & Video)
Video working
as much as possible free system memory ;-)
Of course my respect for all developers, you do great work!
I'll try ~ all Imagereleases, but i stay at the moment @The Original Rogers (modification from kb7sqi). I think it's the only one with working complete ActiveSync/BT/WiFi/Sound.
pychobj2001 said:
This should be reset tho every like week or so, cause constant changes happen and one gets crazy awesome over night..so you should have in the title sometimes (I reset this poll on 1/27) so ppl no to see new results...
Click to expand...
Click to collapse
I like your idea, it's good to always update ratings based upon how certain ROMs enhance faster or more frequent than others.
hey javolin i really think u should add jubeh's 2.1 AOSP ROM to the polls, its really something great, best eclair ROM i used to date.
the Intention ROM comes from a mature dev that doesnt act like a child. He also dosent beg for money
Ill be trying kingklick's rom next!
I don't like eclair roms anymore after I tried CSDIv1 lol....everything seems to be slow as a turtle xD
chim4ira312 said:
hey javolin i really think u should add jubeh's 2.1 AOSP ROM to the polls, its really something great, best eclair ROM i used to date.
Click to expand...
Click to collapse
I would like to add different ROMs to the list, I don't think I can edit the poll once it's posted though.
pretty good turnout with the voting... I think these voting ratings will also help devs in a comptetive state as well... Granted there is the "sharing is caring" attitude, but I'm sure nothing feels greater then having a large fan base that supports your rom
[REF Idea]*Chef input required please* ROM Spec & content - easy choice & comparison.
Hi all HD2 XDA'ers
As we know, the "Which ROM is best" question can be so subjective that no single thread or poll can accurately help you make a decision. Also they get closed and locked pretty quick by the mods.
The users and flashers need some method of selecting ROMs, or at least prioritizing which we try first, based on their individual requirements.
In addition, and perhaps more importantly, the ROM chefs have no standardised way to illustrate or describe exactly what their ROM is like to prospective users. The many posts and threads do not enable any form of comparison.
Here's an idea for anyone willing to take up the challenge:
Unfortunately I can't dedicate the time and effort required, however I know it would be infinitely useful to many users and cooks alike. (Maybe even the mods would find it a useful way of stopping the constant questions, threads and polls of which rom!)
Create a table detailing all the specific (or generic) characteristics of each ROM. Then all chefs, new or experienced, can add their ROMs to the table.
Table would begin with high level details (for a quick overview); then possibly expand to include subtleties and very specific details.
First we would need to create a benchmark using the latest STOCK ROM. This is what the specs of cooked ROMs will be measured against. It should also define all stock apps, etc. for accurate comparisons and to assist the cooks in completing the table for their own ROMs.
For example:
ROM Chef's username
ROM Name/Version
Fully Loaded / Minimalist
Which custom apps included [free text list/csv]
Stock apps cut from Rom [free text list/csv]
What Task Manager used (if any)?
Ringtones stripped? [Y/N]
Media/Wallpapers included
Tweaks included [free text list/csv - or single row for each expected tweak]
Theme changed [description]
Manila version
Cookie/MaxManilla included? [Y/N]
WM Version [6.5 ; 6.5.3 ; 6.5.5]
SYS/XIP build
Free memory after flash (MB)
...and on... (the above is just off the top of my head - it would certainly need more thought, massive expansion and sub-divisions.)
Perhaps start as a thread, work it to a useable format, gathering feedback, comments, suggestions and requests, then move to the Wiki. I recon, if the format and fields are all dimensioned extensively and well enough, the resulting table/wiki would be adopted across all devices.
I would sinserely love to do this myself and regret just pushing the idea out there. I really hope that someone who's heart is really in it, will be willing to take this up to the benefit of all HD2 owners who wish to stick out WM6.5x despite the temptations of other devices, OS's and ports.
All the best,
Hirshy
Information Systems Security Senior Specialist - Networks
T-Mobile (UK) Ltd.
Sounds like a good idea to me.
basically like distrowatch for linux systems? with the package/AKU/radio/Memory/custom apps on the y key, ROM name on the X key. And a blank space in the table where the package is removed?
Just a note - how would someone like you use the data since you work for T-mobile?
chris_ah1 said:
Just a note - how would someone like you use the data since you work for T-mobile?
Click to expand...
Click to collapse
+1 id like to know that too
chris_ah1 said:
Just a note - how would someone like you use the data since you work for T-mobile?
Click to expand...
Click to collapse
quasi_mojo said:
+1 id like to know that too
Click to expand...
Click to collapse
Hmmm, what would you guys like me to do with it?...
I have contacts in the Handset teams for testing and procurement. As my particular job role is impacted by the 'quality?' of their firmware, I regularly feedback required changes and user input. Though to be honest, they're unlikely to care much about any roms other than their own customised garbage!
Have you seen the state of T-Mobile's stock ROMs? At least on Android they get OTA updates quite quickly and in-line with the HTC development branch.
However on WinMo it's the regular old story that they release a device and forget about the bugs and updates.
I work in their Network Security team and am becoming more involved in Terminal Security (devices and whether anything compromises the Network or User Data in terms of confidentiality, integrity and availability). I test all new T-Mobile products, services and network features on their respective platforms.
For example on WinMo, there are the new WnW4 Widgets which run from the Opera run-time environment.
So I guess in that respect, as a favour to the community I would be willing to add my own professional input into whether there are any Security or TMO functionality concerns (from the user's perspective) with the ROMs...
My input here isn't for any professional purposes, I am just a member of the community that has worked at T-Mobile for 11 years and has ties to various contacts.
If there are any concerns for my intentions here (which I hope not) I have personally spoken to Dutty Throy about a year and a half ago to provide him with a contract deal so he could hopefully continue his great work at much less expense. I'm certain he would vouch for me...
Regards,
Hirshy
P.S. (If you read this Throy, it seems that you have since moved to Voda, so maybe T-Mob wasn't cutting it even with the deal - I suppose half-price sh!t is still sh!t !)
Yep, cant believe this hasn't been done yet, would totally reduce wasted threads
Big problem is the rate at which roms get updated.
But i see your point that it would be useful.
It's a helluva lot of work though given the number of roms.
Just off the top of my head I can think of 20roms.
And in the past chefs have been slow to submit their roms to a couple of the rom databases that already exist for swift comparison. I do think that this is better than one of those sites. You would have to get a team together and assign five to ten roms each to watch and update a spreadsheet because it's not going to work relying on the chef's input.
but it really might be useful - e.g. Topix 1.5.8 was based on 21898, but now Topix 1.5.9 is based on 21897 and without the weather function. The build might not be so relevant, but missing weather certainly is!!!
Then you also have the question as to whether to include the htcpedia-only roms in the list.
chris_ah1 said:
Big problem is the rate at which roms get updated.
But i see your point that it would be useful.
It's a helluva lot of work though given the number of roms.
Just off the top of my head I can think of 20roms.
And in the past chefs have been slow to submit their roms to a couple of the rom databases that already exist for swift comparison. I do think that this is better than one of those sites. You would have to get a team together and assign five to ten roms each to watch and update a spreadsheet because it's not going to work relying on the chef's input.
but it really might be useful - e.g. Topix 1.5.8 was based on 21898, but now Topix 1.5.9 is based on 21897 and without the weather function. The build might not be so relevant, but missing weather certainly is!!!
Then you also have the question as to whether to include the htcpedia-only roms in the list.
Click to expand...
Click to collapse
Well, I for one would gladly help with reporting from the roms i test, and it could be nice if a team where assembled to do so, because this whole forum is one big mess, where its impossible to get a little overview with all the threads and all those roms..
One thread to collect information about roms, builds, radios and so on - Would tidy up a lot! And, it would have to be a team of people who are able to stay objective, so that its not a contest of which rom is best..
If this is going to happen - pm me
acdbox said:
Yep, cant believe this hasn't been done yet, would totally reduce wasted threads
Click to expand...
Click to collapse
no it wouldnt, people would still jump the gun and start new pointless threads
Possible way to get started
This could be accomplished using a simple spreadsheet format.
One "Mod" would be in control of the master sheet that would be posted for download.
Team members would be responsible for one or more ROM's as they choose to participate. Submitted to the Mod.
They would get the official blank spreadsheet with labels from the Mod with directions for data consistency.
Only the Mod could add/change the format upon request of the team when new apps or features arise.
Data would be kept as simple as possible in the cells. X=includes, blank=not includes, version number, etc.
Each ROM version would have a column of it's own. Versions could be limited to "last three" or whatever.
Column would have date of posting to show how current the data was.
Most of the work would be front loaded to bring us up to date.
Cut and paste would make this fairly easy for the team and the Mod.
Comparison would then be as easy as reading a chart.
The end user could delete columns and compare ROM's he is interested in.
Start of Col. A labels (add your ideas and let's see if we can come up with a consensus.)
ROM Chef
ROM Name
Version
Build
Language
Radio Required (this could be RadA, RadB, Rad C to Rad F, all picked from a list at the bottom of the sheet)
Theme
Manila version
Cookie
MaxManilla
WM Version
Free memory after flash (MB)
App name 1
App name 2
App name 3
To app infinitum
Well its an awesome IDEA, I am ready to support by all means..!!!
I have already have a site dedicated to filtering roms located at www.xdaroms.com. I am open to ideas to make rom filtering even better.
Great idea!! This is a big hold up for a lot of users: they don't have time to try 20 ROMS, test them and figure out which they want... This is also a hold up for me, I can try some ROMS, like 3 or 4 but I want to know which ROMS I would have to start with... I am not going to take a "risk" flashing HSPL and not having time to install ROMS on it and so....
bowpay said:
I have already have a site dedicated to filtering roms located at www.xdaroms.com. I am open to ideas to make rom filtering even better.
Click to expand...
Click to collapse
+1 that was what I was going to say there is no need for this idea when there is already a comprehensive site that does it.
re xdaroms: at least for the hd2 there are quite a few chefs and roms missing. plus a distrowatch approach where you can see them all lined up is more handy with only one entry for the latest ROM visible.
This means there is room for a seperate glance-database.
chris_ah1 said:
re xdaroms: at least for the hd2 there are quite a few chefs and roms missing. plus a distrowatch approach where you can see them all lined up is more handy with only one entry for the latest ROM visible.
This means there is room for a seperate glance-database.
Click to expand...
Click to collapse
Part of the problem that any website or utility we have is the fact that cooks don't update forum(XDA) or rom(xdaroms) posts correctly. Some like to overwrite old posts or roms and update the build version which causes problems for viewing a history of build versions. I do encourage all the cooks to create new rom posts for each new build. I am also going to allow cooks to import an old rom as a starting point which should make the rom posting a little less tedious.
One solution for showing a build history is to do a group by on the list showing all roms for a paticular version however it will only work if cooks update accordingly.
I don't think this issue can be easily resolved untill I get more cooks on board on xdaroms.com and we can start to formalize a rom posting technique.
Again I am open to ideas and hopefully we can come up with a really nice easy to use way to publish roms.
bowpay said:
Part of the problem that any website or utility we have is the fact that cooks don't update forum(XDA) or rom(xdaroms) posts correctly. Some like to overwrite old posts or roms and update the build version which causes problems for viewing a history of build versions. I do encourage all the cooks to create new rom posts for each new build.
Click to expand...
Click to collapse
Hi bowpay, nice site - sorry I hadn't seen it before.
I think one of the greatest obstacles is exactly that - it is another site. Between XDA-Dev and HTCpedia, users and cooks have enough posts to contend with...
What you state above (quoted) could be mitigated by using a tabular structure instead of posts. New ROM versions would simply be appended to the table, with the old record remaining as a both a history and comparison. The old record would also be the perfect starting point for the cook to update the table (copy the column, paste as new column, update changed details). "Simples!"
I think cooks would find that easier to represent their new roms using this tabular format than constantly changing posts. The single proviso is that is must be complete and total representation of all variables that the ROM might have.
Please can any Chefs reading this, share their opinions/support and post whether they would adopt such a method for keeping users informed of their ROMs and new versions.
In any event, two things could happen:
The cooks utilize a common table for listing ROMs and versions. This would be analogous to a vendor providing a spec-sheet for their product.
Or (if not the cooks) users would create the records and constantly update the fields as they play with the ROM, use it and find the specs. This is comparable to independent reviewers detailing the specs of a product after the vendor has supplied it to them.
Either way would work and be greatly beneficial.
One field per record could even have a hyperlink for download and link to thread for images and discussion.
No objections to XdaRoms assisting the endeavour as it seems to be their speciality - it's all in the title! However for mass exposure and adoption it really needs to be on the cooks first-stop website. I think that is here...?
All the best,
Hirshy
ahirshfield said:
Hi bowpay, nice site - sorry I hadn't seen it before.
I think one of the greatest obstacles is exactly that - it is another site. Between XDA-Dev and HTCpedia, users and cooks have enough posts to contend with...
What you state above (quoted) could be mitigated by using a tabular structure instead of posts. New ROM versions would simply be appended to the table, with the old record remaining as a both a history and comparison. The old record would also be the perfect starting point for the cook to update the table (copy the column, paste as new column, update changed details). "Simples!"
I think cooks would find that easier to represent their new roms using this tabular format than constantly changing posts. The single proviso is that is must be complete and total representation of all variables that the ROM might have.
Please can any Chefs reading this, share their opinions/support and post whether they would adopt such a method for keeping users informed of their ROMs and new versions.
In any event, two things could happen:
The cooks utilize a common table for listing ROMs and versions. This would be analogous to a vendor providing a spec-sheet for their product.
[*]Or (if not the cooks) users would create the records and constantly update the fields as they play with the ROM, use it and find the specs. This is comparable to independent reviewers detailing the specs of a product after the vendor has supplied it to them.
Either way would work and be greatly beneficial.
One field per record could even have a hyperlink for download and link to thread for images and discussion.
No objections to XdaRoms assisting the endeavour as it seems to be their speciality - it's all in the title! However for mass exposure and adoption it really needs to be on the cooks first-stop website. I think that is here...?
All the best,
Hirshy
Click to expand...
Click to collapse
I hear ya I think that its going to be difficult for XDA to adopt this format due to not having things in place and being geared as a forum. I set out to help the XDA community and each day XDARoms is growing. We are going to make it easier to create forum posts by creating a BBCode Generator and our overall goal is to get cooks to post roms first at XDARoms then click the forum post generator link on a paticular rom. The post generator will generate BBCode or HTML for XDA or Pedia or any forum for that matter (Copy and paste).
Our niche is Roms so cooks will naturally want to post roms on the site because we geared the site towards cooks and it will simplify the rom posting for all websites. It may take time but I am dedicated to making rom posting as easy as possible. After all I am not just the president I am also a member (Hair club for men). lol
I really like where this post is going so any other chefs like to chime in and give us your 2cents? Much appreciated.
--Edit--
What you state above (quoted) could be mitigated by using a tabular structure instead of posts. New ROM versions would simply be appended to the table, with the old record remaining as a both a history and comparison. The old record would also be the perfect starting point for the cook to update the table (copy the column, paste as new column, update changed details). "Simples!"
Click to expand...
Click to collapse
When I get a little more time I will take a look at the rom posting process and use some of your suggestions. The database schema is all setup to do exactly that it will just take a little time to make the UI behave.
Well...I think it can be automated... is there a command line tool to extract all such information from a nbh file ? Can someone point me to anything similar ?
My idea : After a upload, automation extracts all such information and automatically appends to the spreadsheet/online sheet...so less work for the webmaster and the chef
ahirshfield said:
In addition, and perhaps more importantly, the ROM chefs have no standardised way to illustrate or describe exactly what their ROM is like to prospective users. The many posts and threads do not enable any form of comparison.
Click to expand...
Click to collapse
Why not use the wiki for that?
chris_ah1 said:
but it really might be useful - e.g. The build might not be so relevant, but missing weather certainly is!!!
Click to expand...
Click to collapse
Don't know how you came to that conclusion but you are certainly wrong. Don't spread wrong information mate.
I have experimented with quite a few different ROM's, and have enjoyed trying them all out.
Just wanted to post a thought out there, and see if this would be worth pursuing or if something like this exists...
A table that compares the ROMs, version, refresh date, developers, features, additional software, bugs, etc, so folks can compare the different ROMs on one page.
Link the name of the ROM to its actual thread.
Just a thought I wanted to throw out there......
Thanks,
-Sf-
The closest thing that we have is this:
http://forum.xda-developers.com/showthread.php?t=649705
But, it doesn't lay it out all that clearly without having to go to each thread and read through. Also, it is about 5 weeks since it was last updated, and we all know how much has been done in the last few weeks (especially Froyo...).
I think this is a pretty good idea. If you want to do something like this, I'd be willing to lend a hand. I am on vacation this week so have a lot of free time anyway.
I think that we could build on that format -
Add major features, bugs, developer name, etc.
Thanks,
-Sf-
It's easier to just link to all of them... you can take the time to go through the Dev's home page. After all, that leaves it up to the topic creator to update every single ROM's bugs and updates, which you can't expect them to do.
Sure, it would be easier to do that...for the posters. But, I feel that the people wanting to check out the roms would appreciate a nice overview of features and bugs then having to wade through some of the toics which can be dozens of pages, if not more. I'll probably start working on this tomorrow, since I've been spending the day figuring out why my parents computer sucks so bad. Found it - 256MB of RAM. ugh lol
this IS a great idea...would be very hard to keep it up to date and what happens if the one guy that posted the topic falls off the face of the earth? as a lot of people seem to do.
not trying to stop it before it begins. i'm willing to comb a topic or two and submit my findings...gonna need a bunch of volunteers to do the same to get multiple ROMs listed.
dusthead said:
this IS a great idea...would be very hard to keep it up to date and what happens if the one guy that posted the topic falls off the face of the earth? as a lot of people seem to do.
not trying to stop it before it begins. i'm willing to comb a topic or two and submit my findings...gonna need a bunch of volunteers to do the same to get multiple ROMs listed.
Click to expand...
Click to collapse
Agreed - I have seen lists on other websites, and they still show evil eris 1.1 as the most up to date. However, that being said, we are the most active android forum out there, especially for the Eris. I think this has the best shot in being the most accurate on the web.
We already have a comparison guide.
Its called xda-developers.com!
Lazy...lazy...lazy....
Just read! Its the best way to fully understand the ROM anyways. Way better than a spreadsheet with checkmarks and whatnot.
But if someone was willing to take the time, which would undoubtedly take A LOT of time, to list pros, cons, features, bugs, versions, updates, and all that jazz, it MAY be worth looking. But we've seen stuff like this before, it gets created, and then never looked at again.
Great idea! Yes people are lazy for not doing their own homework...but there are so many ROMs out there. I have read through almost every page of topics to the 4 or 5 ROMs I have interest in, and often find myself confusing features, bugs, etc of those ROMs simply because there are SO many pages to read through and so much to keep up with(especially when some of these topics are in excess of 200 pages). Among these 200+ pages are maybe 25 pages really worth any knowledge of having about the ROM...the other 175 are filled with redundant information, outdated problems that have been solved, and off topic or unrelated posts.
DO IT!
I was kinda thinking about creating a guide on my website since I can't really think of anything else to do with the domain/server I have lol...
or if someone else wants to, I can give them FTP access to a folder and I'll just host it.
Just an idea.
es0tericcha0s said:
Sure, it would be easier to do that...for the posters. But, I feel that the people wanting to check out the roms would appreciate a nice overview of features and bugs then having to wade through some of the toics which can be dozens of pages, if not more. I'll probably start working on this tomorrow, since I've been spending the day figuring out why my parents computer sucks so bad. Found it - 256MB of RAM. ugh lol
Click to expand...
Click to collapse
Yeah... but what happens if you stop updating? And how will you determine whether bugs are just one persons or all of theirs? And almost every ROM page I've seen has the bugs listed on the first post. I'm just saying the current system isn't just "ok" it's the best way to do it. You don't have to read through the entire thread to know the bugs, you can read the first post.
Well, it looks like interest in this idea is underwhelming at best. I'd be all about putting some time into this, but not for 3 people...
Sounds good to me!
This sounds like a great idea to me. I'll admit it would probably take a great about of effort and time to create and maintain but I'd be more than willing to lend my efforts to put something like this together and help keep it up to date. For all of you who are happy with the current system, it will still be there so keep using it. I don't think this is meant to be a complete list of everything there is to know about a ROM, more of an overview (correct me if im wrong). Plus, this would be GREAT for people who've just rooted and are trying to figure out what to try first. We all know its important to read a thread in its entirety before you flash
Just my $0.02
f z o n g
TheFzong said:
This sounds like a great idea to me. I'll admit it would probably take a great about of effort and time to create and maintain but I'd be more than willing to lend my efforts to put something like this together and help keep it up to date. For all of you who are happy with the current system, it will still be there so keep using it. I don't think this is meant to be a complete list of everything there is to know about a ROM, more of an overview (correct me if im wrong). Plus, this would be GREAT for people who've just rooted and are trying to figure out what to try first. We all know its important to read a thread in its entirety before you flash
Just my $0.02
f z o n g
Click to expand...
Click to collapse
I agree - this list should be an "easy" way to glance over the different ROMs, and do a high level comparison. So if someone prefer's hero ports for example, they can go to the developer's page to determine if that ROM is right for them.
Just like when you research out a new computer, I usually do a high level comparison at first before I start digging into the "nuts and bolts"
I don't think it's a bad idea necessarily, I don't mean to crap all over it but here is what would need to happen:
The poster of the thread would need to understand bugs and things that have to do with the ROM's. They would need to be able to differentiate between one person's bug and a bug that multiple people are having and one that everyone is having.
The poster would need to stay updating this... what happens when they get a new phone? What happens if their computer breaks? Blah blah blah there are a thousand ways you can stop.
Really what you need is a Wiki, that way multiple people could update the information. Developers could submit their own ROM updates if they wanted and users could add reviews, comments etc.
Hungry Man said:
I don't think it's a bad idea necessarily, I don't mean to crap all over it but here is what would need to happen:
The poster of the thread would need to understand bugs and things that have to do with the ROM's. They would need to be able to differentiate between one person's bug and a bug that multiple people are having and one that everyone is having.
The poster would need to stay updating this... what happens when they get a new phone? What happens if their computer breaks? Blah blah blah there are a thousand ways you can stop.
Click to expand...
Click to collapse
+1
for example. . . . what happens when your girlfriend kicks you out and you leave in a rage and forget your computer and storage drives. . . . (was working under the radar on something of the sort but low and behold victim of circumstance.
http://code.google.com/p/erisromtracker/
I'm primarily a web designer but know Rails as well, and a bit of PHP. I'd be willing to put some work into this, but I don't have time to do the whole thing on my own.
I'm thinking of a community-powered web app. Any registered user can edit anything. Edits can be "dugg" by other members to represent validity...I dunno, just some first thoughts.
I made the project page so that people could add ideas/etc and there would be an organized, sane place for figuring out how the whole thing would work, as well as a central repository for any work that actually gets done. It also just doesn't make a lot of sense to use a thread to do this, especially when we're trying to get around people using threads to do this.
^^^^
Eoghann said:
Really what you need is a Wiki, that way multiple people could update the information. Developers could submit their own ROM updates if they wanted and users could add reviews, comments etc.
Click to expand...
Click to collapse
+1
And this
Much better ideas because it's not just one person's job.
Man, I guess I'm one of the lazy ones! Actually, I've been looking through all the ROMs in lust (because I can't root - yet) and I need an easy way to figure out what the main differences are. I'd be in large favor of this!
As it appears people clearly like or dont like HTC Sense, would it be possibly to add these options to the dev forums, its getting really confusing trying to follow/ find anything with the page's updating every second and the random names dev's use to tag there builds
RenZ0R said:
As it appears people clearly like or dont like HTC Sense, would it be possibly to add these options to the dev forums, its getting really confusing trying to follow/ find anything with the page's updating every second and the random names dev's use to tag there builds
Click to expand...
Click to collapse
Sorry for my ignorance but do you need someone to hold your hand while crossing the street too?
inny2 said:
Sorry for my ignorance but do you need someone to hold your hand while crossing the street too?
Click to expand...
Click to collapse
Nope but obviously someone needs help on learning on how to throw together a witty non valid comment... it's a simple suggestion on cleaning up the forums to make them more user friendly, now, back under your rock troll...
I was going to suggest something similar too.Another thought was to not have so much discriptions on the headings,maybe just the basics of what is there.Then more detailed info when the thread is opened,maybe.I find it pretty confusing the differentiate between some of the builds.
I'm almost changing on a two daily basis my android roms and am very grateful for all the hard work being put into this so keep up the good work and thanks
I have to say its rather easy for me to figure out what type of build it is.
maybe its just me. Usually there is something in the header that tips me off.
RenZ0R said:
Nope but obviously someone needs help on learning on how to throw together a witty non valid comment... it's a simple suggestion on cleaning up the forums to make them more user friendly, now, back under your rock troll...
Click to expand...
Click to collapse
hazard99 said:
I have to say its rather easy for me to figure out what type of build it is.
maybe its just me. Usually there is something in the header that tips me off.
Click to expand...
Click to collapse
I hope you see the difference between me (troll) and you. Check the titles, waste some more time to install all the builds and you will find which developer and what build is what with what.
Thank you!
Your correct, Titles tell us everything
[BUILD]Mdeejay FroYo HD v.3.3 beta|1.24.405.1|kernel: hastarin r 7.1
must therefore be a Stock build.... oh wait, its Sense.
I could list various titles for hours with the amount of releases there is on a weekly basis, see what im getting at here ?
The suggestion I made has nothing to do with testing builds, what developer to use, or any other of the random questions about builds that are flooding the forums, its about a creating a simple sub forum so the two variations of releases can be easily distinguished and found by the user looking for it, and probably give a little leeway to the dev's from the constant requests they get to do a alternative build with/without sense, simple organisation allowing less clutter and less load on the xda servers search function.
No need subforums for Sense/Stock, Stock build is dying, in a few days you won't able to find any stock build in the first few pages, there are will be Sense and EVIL Sense...
RenZ0R said:
Your correct, Titles tell us everything
[BUILD]Mdeejay FroYo HD v.3.3 beta|1.24.405.1|kernel: hastarin r 7.1
Click to expand...
Click to collapse
Isn't HD in the title as Rom from Desire HD?
Plus most developers if not all put some screen shots at the end of their first post.
And we are talking for how many android roms in total? 10? Thats nothing compared to WM roms and GTX themed or Max-Sense. Needless to say the mess with the builds for 6.5 and 6.5.x builds. As soon as people get acquainted with what they have its fine.