What I mean is, it seems to me that it would be more efficient to put any/all files that may be upgraded as packages and instead of flashing cooked roms, we could flash a generic rom and uninstall old/reinstall new packages
Am I making sense to anyone?
I understand you
I believe this is part of what chefs who create "lite" or "unbloated" or "clean" or "naked" (in Garmin's ROMs) are trying to achieve.
I personally like the idea, and hope we see more of them.
My personal favorite ROM of all time was the very first Hyperdragon III
mbarvian said:
I understand you
I believe this is part of what chefs who create "lite" or "unbloated" or "clean" or "naked" (in Garmin's ROMs) are trying to achieve.
I personally like the idea, and hope we see more of them.
My personal favorite ROM of all time was the very first Hyperdragon III
Click to expand...
Click to collapse
Up until recently the problem has been that cooks either created loaded ROMs with tons of stuff added to them, or lite ROMs, where they stripped this out.
The issue was however that it is quite easy to strip things out of a ROM. Making CAB packages out of those stripped out files however can be one of the more time consuming tasks and cooks didn't always offer those packages. In addition, CABs which were made available from other sources weren't always packaged in entirety and wouldn't always install.
Cooks have been getting better at this recently however. My new set of ROMS follows these concepts precisely:
http://forum.xda-developers.com/showthread.php?t=429117
I have been calling and advocating for this too basically since the dawn of UC
Previously I didn't post much under different nick, but I have "put up together" this concept in THIS thread finally, albeit with somewhat misleading "temporary" title, but it is good discussion if anyone is interested.
Granted, few apps have to be cooked-in in order to function properly, but those are really just very few. But as you can read there, most objections against this kind of "real lite" ROMs (where any "upgraedable apps" are NOT cooked-in) come from people who don't understand it, or don't know much about UC or Sashimi (BTW I'm for UC rather than Sashimi because UC is much easier for any newbies), or just don't know/have no clue how it works and are affraid it would make troubles to them if they don't have the same apps cooked-in.
Perhaps any of you could add your input there, since there isn't much sense in starting new thread about basically same thing.
Bengalih, I will test your ROMs with pleasure when I have bit m,ore time (or actually a second Kaiser would be great ).
But I can already give you my sincere congratulations now if you have created such ROMs
I have made ROM based on hang.tuah's ROMeOS (it was going to be an update, but ended in another ROM, LOL - not quite "lite" as I would want it, but I can't change the things that were "always there" now ). I try to steer its users into UC and use "extended packs" for things like dialers, comm managers etc. They'll have best proof that "cooked-in" is *worse* than "installed" soon, when they will have i.e. choice of Opal or Kaiser dialer in the extended pack - which obviously would be impossible if the dialer was cooked-in in the ROM...
@bengalih: your post is what got me to thinking about this again
I'm happy to see that you others share my attitude towards efficiency
I have not completely read thru both of your threads but I suppose what needs to be done is to create a universal standard
The way I see it, this type of system would be beneficial to cooks and end users alike. End users need a minimal variety of options to install these collections and a minimal variety of each basic rom release to install the collections to. Cooks need a simple system to adhere to that requires no more work to put together their collections than the current amount of work they do to create their roms.
Here is a sample proposal (what I'm thinking right now with a minimal knowledge of rom cooking )
A base rom of each flavor could be made available to download. By each flavor, I mean a different rom with each combination of files that must be cooked in to work. I haven't read anything like that before so if there are more than a couple combinations then no more than 4-5 with typcal combinations should be considered.
I need to do some reasearch to learn what benefits and/or caveats are associated with UC and Sashimi. I suppose cooks should be the ones to decide whether to make their collection(s) combatible one installer or the other.
selyb said:
@bengalih: your post is what got me to thinking about this again
Click to expand...
Click to collapse
In the future it might just be best to post in the thread about this then. As a topic that has been tread over several times putting additional input into an existing thread would be more effective.
selyb said:
I have not completely read thru both of your threads but I suppose what needs to be done is to create a universal standard
Click to expand...
Click to collapse
Perhaps you should read through the threads that are already out there before staring a new one that re-hashes the same information.
selyb said:
The way I see it, this type of system would be beneficial to cooks and end users alike. End users need a minimal variety of options to install these collections and a minimal variety of each basic rom release to install the collections to. Cooks need a simple system to adhere to that requires no more work to put together their collections than the current amount of work they do to create their roms.
Click to expand...
Click to collapse
Good luck trying to get cooks to follow anything you propose. Not that it might not be a brilliant idea, but cooks are going to do their own thing. I decided to take matters into my own hands and cook my own ROMs according to the principles I thought best. I put the ROMs and my principles out there in hopes others will adopt them, but that's the best you can do...
selyb said:
A base rom of each flavor could be made available to download. By each flavor, I mean a different rom with each combination of files that must be cooked in to work. I haven't read anything like that before so if there are more than a couple combinations then no more than 4-5 with typcal combinations should be considered.
Click to expand...
Click to collapse
Again, pretty much what I have done already with the HTC and AT&T official 6.1 releases. A base ROM for each with a set of CAB file to customize to your desires.
selyb said:
I need to do some reasearch to learn what benefits and/or caveats are associated with UC and Sashimi. I suppose cooks should be the ones to decide whether to make their collection(s) combatible one installer or the other.
Click to expand...
Click to collapse
No offense, because I realize I am coming off a bit gruff in this post, but you do need to do alot of research. I agree with alot of what you are saying, but it has been said before (by myself and others). Also, there is no reason that a collection of CAB files wouldn't work with SASHIMI instead of UC or vice-versa. To your own admission, you don't understand how these installers work, but when you do your research you'll see that in essence they are both just installing CAB and XML files (and with SASHIMI the capability for much more).
Again, please don't take anything here as a personal attack. I can see that you are coming off of inspiration from my posts and I don't disagree with your basic ideas. However you will get better reception from all if you do these things:
1) Research what is out there before posting so you don't retread old ground.
2) Don't just "propose" ideas, put them into action. Even the best ideas are unlikely to be adopted unless you put effort into implementing them youself.
I say these to you for your own protection before someone not as nice as me begins to bash you for not doing research
Ok, well, I will quit posting to this thread before someone not so nice does come along.
selyb said:
Ok, well, I will quit posting to this thread before someone not so nice does come along.
Click to expand...
Click to collapse
Heh... well seriously, take some time and learn more of what is currently out there and see where it is lacking.
I generally invite user feedback on my development projects. If you go back through the older threads, and take a look at what I am trying to do with my BRR ROMs, please feel free to comment in there about what additionally you would like to see and why.
Trust me, I very much welcome an open debate about what would be an effective way to do things. I just wanted to burst your bubble a little bit (seeing as you are a newer member) that your aspirations, although maybe valid, are most likely not going to get implemented by a majority of the cooks throughout the site.
I don't mean to shut down your thread, and you should continue posting if you see it as the best place to do so. I just feel that if you contribute to some existing projects that already have momentum then your ideas are more likely to get some attention.
Related
hey guys,
I'm a regular on the HTC tytn part of this board and have been quite active in updating the wiki and making it functional.
I thought i'd wonder over to this board and took a look at the wiki and have to admit, was sort of shocked. it's one enormous page that's not very intuitive!
I'm going to shift around some stuff to make the wiki for your device easier to browse and navigate, would love for you guys to help out with this venture!
I've started with this:
http://wiki.xda-developers.com/index.php?pagename=wizard_WM_6
WM6 definitely deserves a page of its own, complete with download links, links to threads etc. it does not deserve to be in the middle of some enormous page where most people can't even see it! it's linked back to the main wiki page under the contents page, which is easier to follow.
suggestions welcome, and please help in overhauling the poor state of the wizard's wiki!!
cheers
I don't know about others here in this forum, but I think you're doing us all a huge favor. Good start on the Wizard WM6 material so far.
Hi!
Ofcourse great job. I've learn from this site
I need to suggest to put some information about Not Big Deal 5.1.
I think, this rom is realy good. Realy. Not many ppl use it, but almost all of my friends that tried this rom, confirmed, that it's very ok.
You should probably rename the page to reflect the device it is for. The current name implicates it is a general WM6 page - which is not in fact.
Chatty said:
You should probably rename the page to reflect the device it is for. The current name implicates it is a general WM6 page - which is not in fact.
Click to expand...
Click to collapse
awesome suggestion, silly of me. i've renamed the page to wizard_wm_6
I've updated the Wiki (Thanks for setting this up) with information and download links to my Crossbow Released rom.
Also I would like to make an observation... I disagree with the description of The Core, in that it says this is the best rom for Newbies (or thats how I read it)... Since this is a Clean / "core" rom, I don't know that I would call this a good general starting rom for someone new. Don't get me wrong, I'm not saying The Core 2.0 isn't good, I'm just saying the claim that its the best rom for newbies is maybe misleading as many newbies want more than just a base rom. XPlore 1.1 (IMO) is actually a better rom for someone just starting out as it comes with some apps in it. Then Wizard Mobile 6 Business Edition is very nice with the set of apps in it too... Its just all of the roms have strengths and weaknesses, so to me calling a single rom the best for Newbies may be misleading. Let them choose what fits for them (or setup some type of Matrix to compare the roms).
BTW: This isn't criticism of this new WiKi page at all? I just wanting to provide feedback so this can become a valuable resource for the Wizard community (and I really appreciate you starting this project for us. Now I need to get back to working on the WM6 Cooking wiki pages I was setting up)
mfrazzz - good point. there should be no "favouring" of roms, it should be up to the end user to decide.
I've removed the whole best rom bit. let the person choose themselves
Hi all,
This topic is particularly directed towards ROM chefs, although anyone who has an answer pertaining to it by all means should participate.
I would like to create a chef-friendly ROM, like Laurentius' released a while back. The reason for this would be that I would have my base if I ever managed to mess it up, and I could share my bases with this wonderful community.
I've heard that the .rgus and .dsms must be included, but do not have a clue how to do this.
Any help?
thanks guys
Yes, i would like to participate.
In the diamond forums i posted some sort of question also, about why the current roms are locked down.
Some guys say that is for space en free memory reasons, but why do i see the message "Go build your own rom" in allmost every rom when i dump it?
I don't intend to steal, and if i get a package out of someones rom i'll ask it first.
I'd like to see a more open forum(like the good old days) not that every dev is hiding their findings.
So i'm in for it!
Gr. bram
bram_smulders said:
Yes, i would like to participate.
In the diamond forums i posted some sort of question also, about why the current roms are locked down.
Some guys say that is for space en free memory reasons, but why do i see the message "Go build your own rom" in allmost every rom when i dump it?
I don't intend to steal, and if i get a package out of someones rom i'll ask it first.
I'd like to see a more open forum(like the good old days) not that every dev is hiding their findings.
So i'm in for it!
Gr. bram
Click to expand...
Click to collapse
precisely,
thanks for the support
sorry for the bump you guys, but is there anyone here that knows how to do this?
Send a PM to Its Right. He makes the TNT roms. He resides mostly in the hermes and wizard forums. He knows the answer to your question.
I totally agree with what your doing. I remember the good old days when packages and roms were shared freely. My kitchen is so far out of date its sad.
I would love to see a nice happy base. I would also love to see a new set of packages available.
I wouldn't mind participating in this "project" at all. I would love to share my base and even make OEMs if needed. Perhaps we can make a huge list of most commonly used OEMs (latest version) and split them among the chefs who would like to participate in this.
I honestly think a collection of OEMs is long overdue. I have a few newer packages that I would gladly contribute. I have been working on a new rom which will be the first one ive publically released.
my roms are always dumpable
look at the new manila2d roms they were looked but we managed to get everything out of it anyway just took us alot more time to get it the realy nesasary.
and by removing the rgu and dsm files you free maybe areound 1 mb prob less.
ok the windowsfolder loads faster but how often are we looking in the windows folder? I rarely do.
I only look there when i have to edit stuff like the start menu and i actually tend to test the speed of a ROM by going there and seeing how fast it loads. Anyhow, it opens up a lot faster in Reso Explorer since it omits system, rom, etc. files.
kareem9nba said:
I wouldn't mind participating in this "project" at all. I would love to share my base and even make OEMs if needed. Perhaps we can make a huge list of most commonly used OEMs (latest version) and split them among the chefs who would like to participate in this.
Click to expand...
Click to collapse
Great idea.
I would go step further - common web place for all OEMs (bases etc) where everyone could contribute to and dnld from.
I think we should make a kitchen pantry, just like in the wizard forums.
A place where we enlist bases, oems, cabs, tweaks, and cooking tricks.
A place where users can post their oems to rapidshare or whatever, and post the links here.
Then the mods or threadstarters post those links with info on the first page.
idea?
lets work it out.
I'll setup the base thread within a short hour.
so keep in touch
gr. bram
I have had this feeling since I bought the Kaiser over a year ago. It seems like all the main chefs on here for some reason do not want anyone to open their ROM up and look.
I am completely in on assisting in making OEM's. I would be happy to upload all my packages if someone has a place for them.
Count me in on this....
I have a ton of space left on my 4 share account. Once I get home from work today Ill open a public folder so anyone can upload to it. That way anyone that dosent have a place to put files can use it. I will also upload my packages to it.
Ill post links to my OEMs in Brams thread after work as well
aruppenthal said:
I have a ton of space left on my 4 share account. Once I get home from work today Ill open a public folder so anyone can upload to it. That way anyone that dosent have a place to put files can use it. I will also upload my packages to it.
Click to expand...
Click to collapse
ooh, I've got a TON of packages I'll upload for you guys!
mbarvian said:
ooh, I've got a TON of packages I'll upload for you guys!
Click to expand...
Click to collapse
Folder is created.
OEM Packages Folder
Decided to do it real quick from the office. The folder should be public with 4.5 gb of space to fill. If we should by chance run low on space I will gladly upgrade. Send me a PM if there are any issues with upload. I will link all of the packages to Brams Thread once I get home tonight if they arent linked already.
mbarvian said:
ooh, I've got a TON of packages I'll upload for you guys!
Click to expand...
Click to collapse
And i've got a TON of time to enlist all you packs, haha, we have TONs of fun with this ****
BTW, heres my link to the pantry thread:
http://forum.xda-developers.com/showthread.php?t=426712
REAd first, don post stupid questions, and keep it clean guys!
gr. bram
Hello everyone,
I'm not new to this forum, i have used it for many years now. Yet i have never made any contribution to the community.
I was fiddling with my G1 again when i found out my rom folder was a complete mess filled with update.zip packages, roms i didn't even know i downloaded. So i though, hey lets develop an application to manage all my roms and radio's with a quick button to upload a rom or radio to my g1.
Something like this:
Sorry i could not post a link, it's restricted. My account is still blocked for that. Admin??
I wonder if anyone would be interested in such an application? And if you are interested could you come up with suggestions to make it better/ help me debugging (i'm a student, i don't have a lot of spare time).
If anyone is interested i will seriously think about further developing this app,
it's now in pre-pre-alpha stage or so .
Greetings from holland.
zuenaerox said:
Hello everyone,
I'm not new to this forum, i have used it for many years now. Yet i have never made any contribution to the community.
I was fiddling with my G1 again when i found out my rom folder was a complete mess filled with update.zip packages, roms i didn't even know i downloaded. So i though, hey lets develop an application to manage all my roms and radio's with a quick button to upload a rom or radio to my g1.
Something like this:
Sorry i could not post a link, it's restricted. My account is still blocked for that. Admin??
I wonder if anyone would be interested in such an application? And if you are interested could you come up with suggestions to make it better/ help me debugging (i'm a student, i don't have a lot of spare time).
If anyone is interested i will seriously think about further developing this app,
it's now in pre-pre-alpha stage or so .
Greetings from holland.
Click to expand...
Click to collapse
First off, I am not sure if this is in the right section...perhaps putting it under General might be a better option, as it does not have to do specifically with developing a ROM.
Secondly, the idea seems promising. I am not fluent with ADB, but if you can flash roms with it (IE: boot the phone into recovery, and use adb to flash the rom), then yeah, I think it would be a great idea. And again, depending on what ADB can do, haev it control nandroid/bart as well for backing up and restoring. I know ADB has the shell command, so if you can use stdin/stdout to read/write to that shell prompt, it would be feasible.
But that is forcing every user to go ahead and keep a db of the ROMs they download...perhaps using an external host to manage the images (keep a listing, changelogs, etc) of the individual roms would be an idea...then you can have the application pull roms directly from that repo. This, of course, would require you to manage the remote repository and keep it up to date.
Thats my $0.02
jmhecker said:
First off, I am not sure if this is in the right section...perhaps putting it under General might be a better option, as it does not have to do specifically with developing a ROM.
Click to expand...
Click to collapse
This is ANDROID Development, not ROM Development.
My $0.02.
Bavilo said:
This is ANDROID Development, not ROM Development.
My $0.02.
Click to expand...
Click to collapse
Thats why I said "I'm not sure"...I stand corrected though.
If we want to get technical, this is Htc Dream (G1) Android Development. If we want to be nitpicky this should be in Android development unless it is only for the Dream (G1) and will not work for any other Android phone, which I doubt. But who's being nitpicky anyway?
JAguirre1231 said:
If we want to get technical, this is Htc Dream (G1) Android Development. If we want to be nitpicky this should be in Android development unless it is only for the Dream (G1) and will not work for any other Android phone, which I doubt. But who's being nitpicky anyway?
Click to expand...
Click to collapse
First off, I love the last line of your signature...classic
I just know that the mods and certain 'Senior Members' like to trash talk about threads in the wrong section, rather than simply stating that it would be more appropriate elsewhere. I was just trying to stop the bashing before it started, heh.
This thread is getting sidetracked though. I do think that the idea is a good one, whether it be strictly for G1, or across the board for all Android devices.
Sorry...
Sorry for posting this in the wrong section, i thought it should be in this section becouse it involves rom's.
Putting up a rom repo, would involve PHP and Mysql(a large one, saving all roms and radio's).
I would be very interested starting this project. I could use some help however. I don't mind building such a repo, but the content should be community managed.
I think android is going to be the mobile future so building such a repo would pay off since we're getting more and more rom's. Ill experiment with php and mysql tonight. I don't have a host, i run it locally.
Maybe someone with mysql/ bandwith to spare?
greetings
zuenaerox said:
Sorry for posting this in the wrong section, i thought it should be in this section becouse it involves rom's.
Putting up a rom repo, would involve PHP and Mysql(a large one, saving all roms and radio's).
I would be very interested starting this project. I could use some help however. I don't mind building such a repo, but the content should be community managed.
I think android is going to be the mobile future so building such a repo would pay off since we're getting more and more rom's. Ill experiment with php and mysql tonight. I don't have a host, i run it locally.
Maybe someone with mysql/ bandwith to spare?
greetings
Click to expand...
Click to collapse
It wouldn't necessarily have to be done with MySQL/SQLite/etc...XML would work just as well, but can be a bit more tricky to manage. SQL probably would be the better option now that I think about it.
This idea would have 2 parts to it then, correct? The backend (database hosted online somewhere), and the frontend for the user desktop.
As far as the bandwidth required, there are plenty of places on the net that are geared towards hosting of open source projects...perhaps you could use one of their offerings.
The idea first involved a client managed application only. However the idea in the other post about a web based repo liked me better . Ill try to develop a simple web application to add rom's,track changes. I will try to put a test application online tomorrow.
I hope this repo will be used and managed. I like this forum very much and the community could not live without it. This repo would absolutely be and addition to xda!
Using the repo, you could view all available rom's, installation instructions, track changes.
Check the thread tomorrow. Ill try to upload an example
Have a nice day
zuenaerox said:
The idea first involved a client managed application only. However the idea in the other post about a web based repo liked me better . Ill try to develop a simple web application to add rom's,track changes. I will try to put a test application online tomorrow.
I hope this repo will be used and managed. I like this forum very much and the community could not live without it. This repo would absolutely be and addition to xda!
Using the repo, you could view all available rom's, installation instructions, track changes.
Check the thread tomorrow. Ill try to upload an example
Have a nice day
Click to expand...
Click to collapse
I think anything is better than what we have now: Threads scattered all over the place with new ROMs getting posted. We need something more centralized.
bro you look like a fake maxisma .. hahahhaha .. sorry had to point that out
@georgegreco86
Well thank you for your kind reply...
@jmhecker
I've put together a quick php,mysql script on a temporary host. It's not possible to add roms. But you can view rom information in an organized way.
This is just an example of what is possible. Never mind the layout.
Its just a quick preview.
androidrepo.zxq.net/index.php
Greetings
Great idea!!!
im not a developer, but im a flashaholic he he, cant wait for this info....
zuenaerox said:
@georgegreco86
Well thank you for your kind reply...
@jmhecker
I've put together a quick php,mysql script on a temporary host. It's not possible to add roms. But you can view rom information in an organized way.
This is just an example of what is possible. Never mind the layout.
Its just a quick preview.
androidrepo.zxq.net/index.php
Greetings
Click to expand...
Click to collapse
The one thing to think about with this is when you allw people to add/update/delete their roms. You will have to have some sort of permission system in place that would prevent UserA from deleting a ROM that was created and uploaded by UserB.
Also, this creates another login/password that the rom creators need to remember.
Yeah i thougt about that, unfortunatly we live in a world where you can't trust people. So yes i need to build an user auth system
This was just preview
I'm going to bed now, ill be working on it tomorrow
have a nice day
I like to help
well I am just putting a new linux server online in the next day or so
toss one of my google adds on the page and you can host it there
and as space requirements grow I can add more np
it would at ther very least get it hosted so you guys can get it off the ground
by the way I have been lurking around here for months
some of the stuff you guys have done is truely sweet my phone
will never be the say again unless rogers has its way
Hello guys,
I've been working very hard on the repo and i'm glad to announce that the admin part is allmost fully finished!!
@Broncosis
Thank you for your reply!!!!
i hope your host can run php, and mysql. I use the mysql to upload foto's and roms are saved to the server harddisk. Will this be possible?
Thanks in advance for helping get this project off the ground !!
greetings
zuenaerox said:
Hello guys,
I've been working very hard on the repo and i'm glad to announce that the admin part is allmost fully finished!!
@Broncosis
Thank you for your reply!!!!
i hope your host can run php, and mysql. I use the mysql to upload foto's and roms are saved to the server harddisk. Will this be possible?
Thanks in advance for helping get this project off the ground !!
greetings
Click to expand...
Click to collapse
If I may make a suggestion: When you are working on the frontend (what the users (not devs) will see, code it using proper XHTML standards, and utilize classes from within your CSS. The reason I say that is I would be willing to make a desktop application that would scrape your webpage at load, and obtain the ROM categories, rom information, download links, etc, and the user would then be able to simply choose a ROM from the application, which in turn would download it, and create a nandroid backup of the phone, move the ROM over, and flash it, without any user interaction. (thats assuming I can work out a few of the troubles I am running into with ADB and Fastboot)
zuenaerox said:
Hello everyone,
I'm not new to this forum, i have used it for many years now. Yet i have never made any contribution to the community.
I was fiddling with my G1 again when i found out my rom folder was a complete mess filled with update.zip packages, roms i didn't even know i downloaded. So i though, hey lets develop an application to manage all my roms and radio's with a quick button to upload a rom or radio to my g1.
Something like this:
Sorry i could not post a link, it's restricted. My account is still blocked for that. Admin??
I wonder if anyone would be interested in such an application? And if you are interested could you come up with suggestions to make it better/ help me debugging (i'm a student, i don't have a lot of spare time).
If anyone is interested i will seriously think about further developing this app,
it's now in pre-pre-alpha stage or so .
Greetings from holland.
Click to expand...
Click to collapse
You may want to partner with the guy who built Droid Explorer. This sounds like a natural extension to that tool (if it's not already baked in). I know you can push things like APKs to the phone from Droid Explorer.
maxawesome said:
You may want to partner with the guy who built Droid Explorer. This sounds like a natural extension to that tool (if it's not already baked in). I know you can push things like APKs to the phone from Droid Explorer.
Click to expand...
Click to collapse
Do we know who it was that created Droid Explorer? I would love to be able to improve upon what he has already done.
Important: The docs are up. The live copy can be found on http://docs.insertcoin-roms.org/ and the Git repository on https://github.com/Manko10/InsertCoin-Docs/. For information on how to participate, see the wiki.
Hi,
This thread is related to the InsertCoin ROM by baadnewz (see this thread: http://forum.xda-developers.com/showthread.php?t=1198684). Since I haven't written 10 postings yet, I can't post to that thread nor create a new one in that forum.
InsertCoin has become a quite popular ROM for the HTC Sensation. It has had 200,000 downloads yet and numbers still raise. With increasing popularity it becomes more and more difficult to get hold of information you need concerning installation, problems, modification, tweaking etc. The result is a very high number of redundant questions on the forums and confused newcomers.
The project
Thus being said, it is time to create a good and centralized knowledgebase which helps new users to dive straight into using InsertCoin, keeps the development thread cleaner and helps to push the project forward since energy can be focused more on implementing new features and fixing bugs than on answering the same questions all over again.
baadnewz attempted to launch a Wiki once, but it ceased and shut down (as well as the whole baadnewz.eu server which was the last more or less valuable resource for help outside XDA-Developers.com).
Now my idea is to create a new official InsertCoin documentation project. I talked to baadnewz and he assured it would be promoted and integrated into the official website once it comes to life. The project I'm heading for is a community-driven one. I would work for it as much as I can but I can't do it alone. I'm not experienced enough in many (especially technical areas) of InsertCoin development and Android development in general. There are many things to learn about InsertCoin. And to be honest: I also don't have the time to write all the stuff by myself. Once I had written everything, it would already be outdated. So this project is only possible if other people participate actively.
How shall the documentation be implemented?
I thought of a project hosted on GitHub. Users can fork the project, make changes and send pull requests. For infrequent submissions, we could also provide a special submission form.
A staging server would then pull the HEAD revision regularly, format it and publish it as a website.
Sounds complicated? But it isn't. Git is pretty much straightforward and also users without technical knowledge can learn it very quickly (yes, there are great graphical tools for it). And of course, the documentation would also include a noob-proof guide to contribution.
But why Git? Why not a Wiki?
A Wiki might seem to be easier, but in fact a Wiki has to be updated regularly. Patches for bugs and security holes have to be applied. Additionally, we had to fight spam. Especially when we use some well known software such as MediaWiki, spam bots would love it. That can be a lot of work.
But the main reason is portability. A Wiki is a Wiki, nothing more. Exporting the contents into other formats would be a tedious process. However, when using plain text files with a simple markup language such as Markdown, they can be exported to all formats we like. Not only can the staging server parse it to HTML, but it can also be exported to PDF, CHM files (does anybody still use these?) and many more formats.
All right, but what is to be documented?
Well, a lot. Things I have though of are
Installation
Where to get InsertCoin ROM?
Which version?
How to flash InsertCoin?
How to upgrade from previous versions?
To wipe or not to wipe (and when)?
Kernels
Which Kernels are there?
Where to get them?
What are the differences?
Advantages/disadvantages of specific Kernels
How to install a new Kernel/revert to stock?
What is a Kernel and why can't I install it via the Market? (dumb question, yes, but important to know)
Known problems
Any reported bugs still present in version X?
How do I report my own bugs?
Why does feature Y not work (and never will)?
Features
Why to choose InsertCoin?
How to submit feature requests?
Requirements
What do I need to run InsertCoin?
Which baseband version do I need?
Where do I get a new baseband version and which one to choose?
Does it work on device X, too?
Which is the oldest supported version for custom kernels?
Add-ons
Which add-ons are there?
Where to get them?
How to flash them?
What to be aware of?
How to get rid of malfunctioning add-ons?
Customization
Which themes are there?
How do I install them?
How do I revert back to the default theme?
How to set up custom boot splash and boot animation?
FAQ
Things users ask all the time
Things users might ask regularly in the future
Milestones
Any planned features for future releases?
How many ROMs to release tomorrow?
Participation
How to submit patches?
How to improve the documentation?
How to pay a round for baad?
General information
What else could be valuable information?
How do I backup and restore my data most efficiently and least time consuming for upgrades which force a full wipe?
etc.
The list goes on. It's up to us how much it'll grow. Make suggestions please. Don't hesitate!
And now you come into play!
Do you think, such a project could become a success? Do you have suggestions, ideas, criticism? Post it here. Please.
Would you like to contribute? Post an answer. You would be one of the glorious pioneers.
If I get enough positive feedback and support by people who want to contribute I will start working on the base system, set up the Git repository, write the staging software and launch the project. If not, it would have been at least worth the effort. But you would contribute and give something back to the community, wouldn't you? Sure, indeed...! ;-)
Cheers
Manko10
Do you think, such a project could become a success? Do you have suggestions, ideas, criticism? Post it here. Please.
Would you like to contribute? Post an answer. You would be one of the glorious pioneers.
Click to expand...
Click to collapse
of course it'll succeed cause it'll be much easier with plain updated steps (n00b proof )
I would like to contribute if u may allow
THIS IS AWESOME
Of course you can contribute. Everyone is pretty much welcome to do that.
For Baad and InsertCoin itself, I think it would be a perfect success. I myself have been looking for a central resource database for InsertCoin, but always resort to just searching the thread, which is not exactly the most efficient method.
I don't know much on the technical ROM-based side of things, but I am a web developer, so I'm sure I'd be able to help in the deployment of such a website. I also happen to have a vBulletin license I'm not using. If Baad wants to expand his ideas even further and have a sort of official InsertCoin forum, all to himself, I could most definitely lend a hand for that.
I'm thinking large scale here; and upon writing this, further ideas have just popped into my head, but I'll save that for later, but hey, Baad is largely-awesome.
If you happen to have an MSN or Skype, Manko, I'd love to talk to you further
i have a better idea for talking / chatting in a more centralized way: IRC
#baadnwz-roms on freenode
I don't know much on the technical ROM-based side of things, but I am a web developer
Click to expand...
Click to collapse
So am I.
I'm quite sure, baad will help us as good as he can but he is of course very busy with the ROMS. So it's better to have many guys in the project who know more about the technical stuff.
I would try to help too, if You like. If You don't need IC pro's only
We need everyone (IC pros are needed, but not only).
First of all we need people who have fun writing and maintaining (!) good and understandable documentation.
Guys
if you do this - it will be bloody FANTASTIC!
noobproof guide needed badly
Make it so. Sounds like it could become a great resource.
It will, but only if enough people participate.
why not add chatbox on the coming site, isnt much better? 24/7 we can have conversation as like me, am from the philippines, and my time is different to others
Well, the documentation would also be there 24/7. I think for live talking we should better use IRC (#baadnwz-roms on irc.freenode.net). Embedded chats on websites consume a lot of bandwidth.
lol!, i guess so, yeah, maybe irc is much better. anyways, maybe i can contribute some design for future use.
Just jeep in mind that IC is also made by baadnewz for the Desire (and the wildfire too?). I'd like to write some things for the Desire version of IC.
koenvbeek said:
Just jeep in mind that IC is also made by baadnewz for the Desire (and the wildfire too?). I'd like to write some things for the Desire version of IC.
Click to expand...
Click to collapse
yes once the project starts, desire will be there too
for wf i made 2 roms long time ago, and then i sold the phone
Ill contribute if i can I love this rom
wow... this sounds freaking awsome. i would most definately help with coding once the repositories are set up ^_^
I think it would be really beneficial for everyone especially for the folks who are new to the ROM. 600+ pages of comments are a LOT to read through!
Make it so. (with Jean Luc Picard's Voice ) Nice idea.
Would like to contribute sth, though I have a really tight schedule lately...
Hi, I was wondering if there was a list of HTC One S (Ville) Build.Prop tweaks. I did some searching and saw some lists in other forums, but I wasn't sure if the build.prop was the same for all devices, I guess I'm assuming not as some organizations are totalitarian and such.
In any case, I think we should create a list of build.prop tweaks specifically for the One S that are very effective, saying what the tweak changes and how it effects the device, also what other settings you can give it and what those effects do. Maybe I'm thinking of to much information, but I think a lot of people would be interested in the other information as well.
Maybe I just don't know enough about the build.prop file yet, but if someone could give me any links about more information on it that would be great. Or if anyone has a link to a list already like this that would be great as well. Sorry if I'm being a noob, but I've done quite a bit of searching and haven't found anything yet.
Thanks in advanced for any posts,
Cobra
It doesn't matter which phone, android is android.
But everyone uses other build.prop edit's, there are no original one's..
Thanks for that information.
So if there aren't any original ones, are there possibly ones that work well specifically for the One S? I know the Fast.Dormancy one is supposed to be effective for some carriers. And though, this may be a setting that could be effective for many devices, does it not make sense to maybe start a thread or some sort of page listing all the settings that effect this device in particular in certain ways and which carriers they work effectively on?
I ask these questions because, yes I am a newb and I feel like these things could be helpful to other noobs. it's almost as if I'm trying to learn some sort of ITIL based thing I guess. I guess to me it just seems effective to have a list of things that can help make your device work more effectively. For instance, have one page, say the wiki, linking to different things to help you setup your phone how you want it, and to make it so it will work as effectively as you want it for yourself.
Now I realize that the Wiki currently has things such as how to unlock, root, flash roms, lists of roms, etc. But, it doesn't really say, "Hey, here are a list of things you can do to make your phone more efficient without having to flash a new ROM, and here are ways you can make your own ROM, here are some paths to certain things specific to this phone.
I know the Wiki is new, but I guess what I'm saying is if nobody else is working on this stuff, can someone give me a hand in finding all this information so I can start adding it to the Wiki?