creating a ROM repository for organization - G1 General

Hi guys,
I have an idea in mind and would like to know what do you think of it:
Why not create a site/blog/page where every developer can upload his rom (with all the info) devided by categories (G1, mt3g (A, B), nexus, etc)
and people can report only bugs (not general questions like it happens here).
This threads can still be used for general questions, discussion etc, but the roms, compatibility and bugs can be easily find on other page!
I'm willing to help with it!

Android Spin?

on android spin you cannot add your rom instantaneously, cannot report bugs etc.
my idea is a more interactive thing...

MMartins said:
Hi guys,
I have an idea in mind and would like to know what do you think of it:
Why not create a site/blog/page where every developer can upload his rom (with all the info) devided by categories (G1, mt3g (A, B), nexus, etc)
and people can report only bugs (not general questions like it happens here).
This threads can still be used for general questions, discussion etc, but the roms, compatibility and bugs can be easily find on other page!
I'm willing to help with it!
Click to expand...
Click to collapse
That's a good idea.. but to be honest, I think devs are too busy atm with the 2.1 ROM bug fixes, etc. to go and sign up to a whole new page to check up on everyday.. I'm sure they already get private messages when it comes to bugs. Maybe your idea will work when the dust settles.. But right now, it's far too hectic around here to advertise and use a new dev page.

Related

Petition for a new Child board named: Builds

I noticed that a lot of builds are lost in the chaos of topics here in development, I was wondering if there being a separate child board solely for builds would be a good idea...I'm not sure who runs that, but I think it would help with the clutter.
Delete this topic if it is too off-topic...
how about making it a read only for non devs? in my head im seeing a change log like thread for each build. where the devs can comment, and post common fixes and such on each others build, im not sure how easy of a feat this would be, but the mods are all mighty and I believe they can do this.
I'll third that motion
It can be difficult to find builds sometimes if I can't remember the devs name (which often isn't even a real word.)
The only problem I forsee is who decides what is and isn't a build. If I package JF1.51 with a few custom wallpapers and new ringtones who decides whether or not I'm a dev? Where do you draw the line as to what is development and what is just end user customization?
I figures that would be an issue.
Maybe established builds like the thedudes and cyanogen. Twistedumbrella has done some serious work in android as well. They have my vote as being in the build section

Status of the Vogue-Android Project, please read

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

[POLL] Eclair ROM ratings for users & devs 01/26/10

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.

[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.

Mod-connect.

Well,the rules to abide by in this forum...Hope to keep every member in there safe.
Use the Smartphone General forum for GENERIC posts, hacks, tutorials, questions!
If you have a question / tip / hack / trick also applicable to (most) other Smartphone models, please PLEASE post it to the brand new General Smartphone forum. Few Smartphone users check out the forums of other Smartphone models and, therefore, your questions / tips / other stuff will be read by a LOT more people if you post it to a general forum than in just a model-specific one.
As has already been pointed out, everything should be posted to the new General forum that isn’t ONLY related to the particular model. Some examples of what should be posted to the General forum and what should stay in a device-specific one:
* posts like “the HTC Opal has a very bad-quality Camera" should stay in the device-specific Opal subforum because it’sonly the Opal that is affected by this problem. The same stands for problems with the bootloaders of a given model or specific ROM upgrades, ROM versions, unlocking etc. only applicable to a given model (and nothing else).
* posts like Live Messenger CAB’s , OpenVPN hacks hacking etc. should go to the General forum because these hacks, information etc. can be used on (almost) ALL Smartphone models.
* if you have a question that you feel can be answered by other Smartphone users, do NOT post it to a device-specific forum, but to the generic one. Generic questions are “What Web browsers should I use?”, “How do I configure my e-mail client?”, “How do I install Flash on my device” and so on. ONLY post questions like “What about ROM version X.Y for Smartphone model XY”, “How do I enable HSDPA in model XY”, “Where should I get WM6.1 for model Opal”, “I have problems with the Camera of my Opal”, “My Opal’s buttons are hard to press” – that is, questions you’re absolutely sure about belonging to model-specific forums.
Also, make sure you continuously monitor the forum because I’ll post a lot of brand new Smartphone-related information in there.
Again and again,
1. POST ALL your questions / tips / hacks in the General forum if you find it can also apply to / answered by the owners of other Smartphone models
2. frequently visit the new forum for new tips / questions and, last but not least, my tutorials / roundups
thanks to Menneisyys for the rules...
Dun Dun Welcome to the modding community shreyas!
User Experience.
Well,this thread is dedicated for the users of Opal.I would like every member to express his/her problems regarding the forum,problems if any ranging from irritating members to topics in the forum,how to use,help and so on...If any user experiences something really annoying at this forum and needs to report it,s/he may do it over here...this thread is for the members.If any one under moderator scanner feels that s/he is being ill-treated with the mod actions or if s/he feels that his/her point is stronger,do express your concerns over here.
Dont unnecessarily start a post.This thread is for a better user experience over the forum.Enjoy posting here.Use the smileys to denote what you feel as sometimes,texts don't express things as they are needed to be expressed.As always,please do follow the rules!won't like to lose a member atleast from this forum...I would also like the users to report if they feel any insecurity,threat,misunderstandings and/or any serious problems from the fellow users...I may take action or report that to the higher authorities.thank you!
Looking forward on enhancing the User Experience over here.Have a nice time.
Pajerm's RC1 & RC2 ROMS MERGED.
ALL THOSE WHO ARE FINDING IT DIFFICULT TO LOCATE PAJERMS RC2 ROM,WATCH THIS SPACE.LINK: http://forum.xda-developers.com/showthread.php?p=8211495#post8211495
Evolution ultimate beta.
ALL THOSE WHO WERE WAITING FOR JAGANS EVOLUTION ULTIMATE...WELL,HERES THE BETA FOR IT...ENJOY...http://forum.xda-developers.com/showthread.php?t=782119
For Members too...
Well,id be happy if members post their thoughts about this forum...and also,this thread can be used for chatting..there's no restriction here!!!
Ban
Having my exams this month.will be banned for some time!!!have a great month ahead!!!
Notice to New members.
Well,if you are a NEW member on XDA,please READ the FORUM RULES.its a sincere request from the top brass of this forum.We don't like to delete,ban or remove any members from this forum..Just spend a few minutes reading them.Its all for your betterment
Well, to all the Members of the hTC Opal General/Development/Accessory Forum, this is the Moderator for this forum.Requesting all the Members here to feel free to report posts and seek help from me(shr) and I'd assure action on them.If you have any problems with this forum or suggestions to make, please contact me. I cannot promise to act on every suggestion that is made but it will receive my attention.
Thanks.
Things of the Past!
It hurts to see that there is No-Activity going on in this forum...The forum was active at one time!
But now,i guess all of the shine is gone....The wait for Jagan's evo series,Pajerms fabulous ROM's,some or the other development and innumerable Q & A's...What fun it was...Some crazy tantrums,Mod-Edits,Personal Messages,Application requests,frequent checking in and out of the forum....It doesn't happen these days!
Well,I am keeping this thread open...Please do post your concerns! How much ever silly they are...
Keep this forum alive guys...We need you all!
Thanks!
Jagan's busy regarding his exams, Pajerm bricked his Opal, Android not yet fully functional, no news except from this thread?! Argh! I guess Opal's really dying
Bad show!
What are the other members doing???We don't have only Jagan and Pajerm as the heart and soul of this forum...We had a really good team of beta testers (for all ROMs)..A good Italian discussion thread(later asked to continue and translate in English)...I guess the device had a shorter life span...May be people upgraded their devices or are rather not interested to develop due to limited functionality of the device...Bad show guyz...
shr said:
What are the other members doing???We don't have only Jagan and Pajerm as the heart and soul of this forum...We had a really good team of beta testers (for all ROMs)..A good Italian discussion thread(later asked to continue and translate in English)...I guess the device had a shorter life span...May be people upgraded their devices or are rather not interested to develop due to limited functionality of the device...Bad show guyz...
Click to expand...
Click to collapse
You really can't blame others for this, with a lot of new devices coming out, it just show that Opal is really limited with regards to its hardware capabilities. *sigh* I just learned how to flash my Opal recently, but I guess it ends here
golokipok said:
You really can't blame others for this, with a lot of new devices coming out, it just show that Opal is really limited with regards to its hardware capabilities. *sigh* I just learned how to flash my Opal recently, but I guess it ends here
Click to expand...
Click to collapse
Well,thats what i just said!!!
The Opal does have some limitations and i think all the members must have migrated out to a new device and forum!!!
I have an idea, look at my signature, if what I wrote goes against the rules of the forum then tell me and I remove everything at once.
Good little phone
Yes, the Opal might be a bit older, but I have found that it is a great little phone especially when you upgrade the ROM to a WM6.5 or greater.
It doesn't have a large screen or isn't as fast as some of them out there, but if you don't have a data plan or don't do much on-line and want a good Pocket PC / Cell Phone it works just fine.
And I for one will be happy to help Pajerm get another Opal.
United We Stand-No One Dares To Divide Us!!!
Well, yes Pajerm,I'd like to help,all you can do is tell me the procedure...And 1 more thing.Can you organise a you tube thread which shows us how to install,use[kitchen] and make ROM's for Opal using kitchens???
I'd help you with the thread...I mean everyone will help...You be sure to record and take screenshots and you may mail them to me if you are busy!
I'd post it here...
Thanks!
shr said:
Well, yes Pajerm,I'd like to help,all you can do is tell me the procedure...And 1 more thing.Can you organise a you tube thread which shows us how to install,use[kitchen] and make ROM's for Opal using kitchens???
I'd help you with the thread...I mean everyone will help...You be sure to record and take screenshots and you may mail them to me if you are busy!
I'd post it here...
Thanks!
Click to expand...
Click to collapse
I can make some tutorial, but I need your help because my English is very bed...
pajerm said:
I can make some tutorial, but I need your help because my English is very bed...
Click to expand...
Click to collapse
Well, ok,i will help...! I also have Mr.zeus's gmail id through which we are intending to discuss some android stuff..If you can,please PM your gmail id so that we can video chat if you have a web camera!
Thanks!
New life for opal?
Looks like we're gonna see new ROMS again in the future. Keep it coming guys, I wanna help with the testing

Categories

Resources