One of the big issues I have noticed is that there is no rationale behind the version number assignment for a lot of the mod firmware. There are different modders using their own versioning, and there isn't even a hint of what version of android they are using, so we have things like;
"KiNgxKxROM Version 1.1r1"
"The Official Blur - Hero-V1.5.7 by Drizzy"
"JACxHEROSkiv2.2"
"CyanogenMod 4.1.11.1"
*** these all have the same problem... what version of android do they correspond to? How new IS each one of them?
I would like to propose a new standard to be adopted by everyone.
name-officialversion-modversion.
Of the form i.e.
"superxmod-1.6.DRC83-0.1.0.0"
***WHERE the modversion RESETS TO ZERO each time the official version increases, so for example, "CyanogenMod 4.1.11.1" should be called "CyanogenMod-1.6.DRC63-0.1.11.1".
* this will allow the user to immediately know where this rom comes from in terms of the official android versions and approximately how old it is.
I do my best
I do my best ... with the "limited space" we're given for Thread Titles on the forum.
~enom~
I support this though I find it unnecessary. The new beginner user will most likely READ atleast the first post of the thread and they will know what the ROM is based off of. The end user will of course know to read the thread before doing any flashing of any kind so organizing mod rom versioning isn't a necessity. It's convienent but not necessary
I support this because it would make ROM catalogs easier to build, which would benefit the whole community.
why not just post what android version the rom is based on in the first post. First post should always hold the most info anyways.
Since this thread hasn't been moved from the Dev section so far.
+1 for the versioning.
Also, how about we all stick to one benchmarking app (or is there any one app that we CAN rely on)
to test performance of ROMs, so that there's an objective way of figuring out
whether the latest frankenROM (thanks devs! ) is faster than X or Y?
Benchmark Pi has a score that's difficult to figure out, seeing as it throws up an
awesome number on a fairly sluggish HERO whereas the score for a fast-as-light
cyan ROM is way way worse. I know that Benchmark Pi isn't the answer,
not by a long shot. So is there a better alternative out there?
I'm tired of posts that go "THIS IS WAY FASTER! THANKS!" only to find
that the supposed speed increase is more rooted in perception than in
reality.
We need definitive numbers for ModelNumber+ROMVersion+CC/SwapSettings combinations.
Any help?
alritewhadeva said:
The end user will of course know to read the thread before doing any flashing of any kind
Click to expand...
Click to collapse
rofl. Funniest thing i've read all week.
+1
how about shorthand naming such as
for example:
CyanogenMod = CM-AOSP1.6r1-v4.20
If you're talking about cyanogen mod, you might want to add a couple more zeroes at the end. Anyway, I had proposed this too a while ago. I like your format, and I'll go one better; let's do cook-androidVersion-buildVersion-feature.bugfix
for example, the build I made this morning would be "jm-1.6-Donut eng.jubeh.20090930.070211-0.0"
jm is what I use for my builds (short for jubehMod)
1.6 is the current android branch (as per build.prop, no 1.6_r1 yet)
Donut eng.jubeh.20090930.070211 is the build number the compiler assigned to my build, people who work off of modding factory releases or build for dream_open are the ones who usually come up with things like CRC or DRC etc, I build for "AOSP for Dream" (it's a new "vendor" added)
first 0 is feature number, at this point my build is nothing but stock AOSP donut, no Google apps, no a2sd, no netfilter, no compcache, no bfs, just stock donut, so say I were to add a2sd, then I'd go up to 1, as I would have added one or more features (and this would be listed at the change log), basically, anything added that improves the build (and that's not a fix) is a +1 to feature
second 0 is bugfix. For example, right now my build works correctly in every sense, but I have a problem with the video camera where video is of very poor quality (real problem, I'm trying to figure it out), so say i get it fixed, then my bugfix number would go up 1, so basically, anything changed in the build strictly because it didn't work as intended is a bugfix
the last two numbers would be allowed to go past 9, so no more pressures to add .1s at the end like cyanogen was doing to prevent jumping to build # 4.2
karthikjr said:
+1 for the versioning.
Also, how about we all stick to one benchmarking app (or is there any one app that we CAN rely on)
to test performance of ROMs, so that there's an objective way of figuring out
whether the latest frankenROM (thanks devs! ) is faster than X or Y?
Benchmark Pi has a score that's difficult to figure out, seeing as it throws up an
awesome number on a fairly sluggish HERO whereas the score for a fast-as-light
cyan ROM is way way worse. I know that Benchmark Pi isn't the answer,
not by a long shot. So is there a better alternative out there?
I'm tired of posts that go "THIS IS WAY FASTER! THANKS!" only to find
that the supposed speed increase is more rooted in perception than in
reality.
We need definitive numbers for ModelNumber+ROMVersion+CC/SwapSettings combinations.
Any help?
Click to expand...
Click to collapse
yes just bench mark. its much better than benchmark pi only test the cpu really
by the way, I've been saving pretty much all roms that have been posted here (notable exceptions are haykuro's, jf's, and theduded's roms, I haven't been here THAT long) and I have them all saved on my computer separated by /cook/build/ for the Dream roms and /build/cook/ for the Hero ports. I guess I could run a quick filesystem lister and upload that list for people to see so they can sort of get an idea what mod release corresponds to what build
Here we go, I had to upload it inside a zip because of the stupid 2kb limitation on text files (this is 10kb)
lbcoder said:
One of the big issues I have noticed is that there is no rationale behind the version number assignment for a lot of the mod firmware. There are different modders using their own versioning, and there isn't even a hint of what version of android they are using, so we have things like;
"KiNgxKxROM Version 1.1r1"
"The Official Blur - Hero-V1.5.7 by Drizzy"
"JACxHEROSkiv2.2"
"CyanogenMod 4.1.11.1"
*** these all have the same problem... what version of android do they correspond to? How new IS each one of them?
I would like to propose a new standard to be adopted by everyone.
name-officialversion-modversion.
Of the form i.e.
"superxmod-1.6.DRC83-0.1.0.0"
***WHERE the modversion RESETS TO ZERO each time the official version increases, so for example, "CyanogenMod 4.1.11.1" should be called "CyanogenMod-1.6.DRC63-0.1.11.1".
* this will allow the user to immediately know where this rom comes from in terms of the official android versions and approximately how old it is.
Click to expand...
Click to collapse
................................
Hi jubeh,
Thanks, this kind of cataloging is exactly why the OP's suggestion will be helpful.
karthikjr said:
We need definitive numbers for ModelNumber+ROMVersion+CC/SwapSettings combinations.
Any help?
Click to expand...
Click to collapse
I'm not so sure that we do...
I think that that should be more of a "details" thing.
Maybe we can go with "name-officialversion-modversion[-custom]" (square braces mean optional). Name might be a good place to keep modelnumber (I assume you mean by that "dream", "magic", "hero", etc.),
i.e.: supercustomrom(DREAM)-1.6r1-0.0.0.0.0.0.0.1-cc_swap_a2sd
Related
First and foremost, my hats (the whole rack of 'em) off to all the chefs in their respective kitchens. I've personally been a silent, yet happy customer for quite some time, and have been checking the forum daily for the next flash.
However, I've found that different ROMs will, obviously, have their list of capabilities and limits. Some support SIP better than others, some can't run iGo, etc. Mostly I flash, then find out during my installations, etc., and by that time I'm too lazy to flash back and just live with what I have. I would probably not flash ROMs that didn't support iGo and SIP if I knew that up front.
Having that in mind, I thought we could (as a group of continous beta testers and their respective gurus) try to formulate what would be a "check-list" for ROM releases, thus allowing the newbies (that don't know what to expect) and the old bees (buzzing along from ROM to ROM) to pick the right ROM flavor.
An example would be:
ROM Details
=========
ROM Name / Version: xxxx (Dutty's ..., Schap's ..., etc.)
CE Version: xxxx
Radio Versions Supported: xxxx ( So we know what we should have before flashing )
Based on: HTC WWE Release xxx (So we know if we got the new "hardware acceleration, etc")
Compatability
=========
SIP: [Not/Is] Supported, configured by ...
Skype: [Not/Is] Supported
iGo v7: Works out of the box / Requires removal of HTC Home
iGo v8: Not Supported
etc.
Thoughts about what this should include?
- SiteLister
Well I'm gonna jump on this first since chances are others won't be very nice about this thread
Not that I think your idea is a bad one, but to be honest most cooks already provide this information when they release a ROM.
If application compatibility isn't listed then the first 20 posts will bring it out....
If what you are asking is to compile a whole list of all these ROMs in one place. OK, good idea...but no one is going to do it for you.
If you like the idea...do it youself, or at least make a good start. Putting a post out like this is more likely to draw animosity since you are asking others to provide information that has been put out there numerous times. Good idea or not, you should make the initial effort and if you build something nice, people will contribut and thank you. Otherwise, they will just flame...
In addition, the Wiki would be the best place to do this.
not to say that this is a bad idea but there is one major flaw with the idea, most chefs cook for themselves and then release. with that said most of the chefs do not sit and try every possible application that can be put on your Kaiser, if you want to know what roms work with what applications and you also want to be the first to flash it and have the latest then you just have to try it for yourself. if you don't mind waiting you can wait a few days for the members that do use the programs you use to see if they say it works. i personally like to take a rom cooked by a chef, dump it and recook it for myself with the cabs my UC would usually install into the rom where i want them to be. sorry if this seems like a **** response but as far as i can see there is no way for the chefs to tell you what does and doesn't work and that's why we have threads after the rom release for people to tell others what does and doesn't work.
tubaking182 said:
not to say that this is a bad idea but there is one major flaw with the idea, most chefs cook for themselves and then release. with that said most of the chefs do not sit and try every possible application that can be put on your Kaiser, if you want to know what roms work with what applications and you also want to be the first to flash it and have the latest then you just have to try it for yourself. if you don't mind waiting you can wait a few days for the members that do use the programs you use to see if they say it works. i personally like to take a rom cooked by a chef, dump it and recook it for myself with the cabs my UC would usually install into the rom where i want them to be. sorry if this seems like a **** response but as far as i can see there is no way for the chefs to tell you what does and doesn't work and that's why we have threads after the rom release for people to tell others what does and doesn't work.
Click to expand...
Click to collapse
Most of this is true... however I don't think he is asking the chef's to do anything different, it just looks like he wants an encyclopedic reference of all ROMs and their features. Again, good idea...but just do it if you want it. Others will contribute if they find it worthy, if they don't...then oh well, at least you learned for yourself.
sitelister said:
An example would be:
ROM Details
=========
ROM Name / Version: xxxx (Dutty's ..., Schap's ..., etc.)
CE Version: xxxx
Radio Versions Supported: xxxx ( So we know what we should have before flashing )
Based on: HTC WWE Release xxx (So we know if we got the new "hardware acceleration, etc")
Click to expand...
Click to collapse
Im hip to this.. well mainly must of us do that already in one form or another just not in that pretty format
sitelister said:
Compatability
=========
SIP: [Not/Is] Supported, configured by ...
Skype: [Not/Is] Supported
iGo v7: Works out of the box / Requires removal of HTC Home
iGo v8: Not Supported
Click to expand...
Click to collapse
Not a bad idea, however this would require us to manually test a billion pieces of software in order before giving it out.
Now how about a better idea, someone should start a kaiser wiki page on bug fixes, etc... In all of my beta roms when someone points out an issue i will ask them to provide a link for a fix if i dont know it already, i actually do this for a couple of reasons.
1. it helps promote interactivity between forum members and helps to get people communicating, etc. This also helps to hinder the n00b factor and provides links for other people.
2. it provides me reference point, before i release each beta i go through the previous threads and make sure that i have fixed everything that was broken prior.
sitelister said:
First and foremost, my hats (the whole rack of 'em) off to all the chefs in their respective kitchens. I've personally been a silent, yet happy customer for quite some time, and have been checking the forum daily for the next flash.
However, I've found that different ROMs will, obviously, have their list of capabilities and limits. Some support SIP better than others, some can't run iGo, etc. Mostly I flash, then find out during my installations, etc., and by that time I'm too lazy to flash back and just live with what I have. I would probably not flash ROMs that didn't support iGo and SIP if I knew that up front.
Having that in mind, I thought we could (as a group of continous beta testers and their respective gurus) try to formulate what would be a "check-list" for ROM releases, thus allowing the newbies (that don't know what to expect) and the old bees (buzzing along from ROM to ROM) to pick the right ROM flavor.
An example would be:
ROM Details
=========
ROM Name / Version: xxxx (Dutty's ..., Schap's ..., etc.)
CE Version: xxxx
Radio Versions Supported: xxxx ( So we know what we should have before flashing )
Based on: HTC WWE Release xxx (So we know if we got the new "hardware acceleration, etc")
Compatability
=========
SIP: [Not/Is] Supported, configured by ...
Skype: [Not/Is] Supported
iGo v7: Works out of the box / Requires removal of HTC Home
iGo v8: Not Supported
etc.
Thoughts about what this should include?
- SiteLister
Click to expand...
Click to collapse
Ah configuration management then maybe ISO accreditation................
Flash, enjoy, read, explore, reflash again and again.
Remember this isn't someones job its their hobby that they share.
Remember to say thankyou every now and then.
Thanks
usually it's the base rom that isn't compatible with the software. Most chefs just take the base rom and strip it out to remove bloated software and add in their own personal software. There are some chefs that go out of their way and add in the necessary dlls and files to make certain software work, but it is really difficult for chefs to do such a thing. Maybe a specific thread for each software to work on a particular rom would be helpful.
Thanks for your replies, y'all.
To be clear (and I can see where I may have not been there), I was fishing for interest. The next thing up would be to set it up in one format or another (Wiki, whatever) - I'm just not usually for building something before there is a market for it. When I said "we could" I meant it would be something that people could contribute to (myself, amongst others), in a format better appealing than, or more appropriate than those 105-long pages mostly containing praises, bashes, and little information (there's quite the picking to do when you're actually trying to decypher what a ROM's capabilities are).
If there is an interest, I'd be happy to put in the initial effort, but I'm also fishing for content requirements - that is, I've put forward some kind of basic format, but what other information would cause people to make a judgement? what kind of apps are important, etc.
Quick replies:
bengalih - I'm hanging on the fact that people are, inherently, nice. Hopefully at a higher ratio in this forum .
tubaking - Agreed, most users will give the feedback back to the cook or the forum. I'm actually not asking anyone to do more work than they already are. My thoughts are that the feedback is sometimes lost in (or hard to gather from) the forum. Fixes are also all over the place (for example - the iGo version compatability thread). I believe it's because the tool is incorrect (discussions).
bengalih - Agreed.
shogunmark - Sounds good. Wiki then as the solution? - Possibly have one page per release, and a summary in a top-level page that contains a comparative table?
halon - I'm sure I don't say it enough --> THANKS!
thomassster - I believe that the concept is good, but you're back to trying to nitpick for each application you're interested in, in hopes that people organize it in that fashion. Additionally, you're still back into reading a bunch of acknowledgments, accreditations and bashes (which take up a good chunk of the forum content).
... Thoughts?
inconsistencies in "support"
This is a good idea (or a bugzilla-type thread/wiki) and as ShogunMark stated in his first post, the first 20 posts (pages!) bring out the main probs. the only issue there is that some posters inevitably state that something or everything is working for them (perfectly) out of the box, while others experience major dysfunction, creating a confusing morass of info.
How bout a survey page - everyone votes for what works or not?
Cheers-
Yes this sounds like a good idea for someone as a side project to document in the wiki. But really most of this information can be found in the first 20 to 30 posts. And most roms, are quickly superceded by another new version. So if you want to do it, I am sure someone will read it. But asking the chef's things like does IGO work or Skype, If they don't use them they should not be expected to test them...IGO who cares if it works or not, only the people that use it..not everyone..
SO if you want to create a wiki page with this info; go ahead and do it and maybe someone will read it...Maybe good idea, but it will quickly be outdated.
This is my 3rd post ever here, so please be gentle.
Crogon said:
I can't seem to find it now, but didn't there used to be a list of pre-cooked ROMs here somewhere?
I think what I'm aiming at is a fully patched / hacked 6.1 HTC ROM with everything fixed and no bugs. Preferably minus any bloatware. If it has recommended utilities pre-installed great, if not, no big loss. Did they ever finish hacking a video driver together? I lost track of that thread, and can't seem to find any current info.
Click to expand...
Click to collapse
Update: I found a tidbit somewhere that says the newest video driver updates should be cooked into the newest ROMs.. but how do I figure out which ones have all the bug patches and hacks installed, and etc. like I mentioned above? I know there USED to be a list of pre-cooked ROMs, but I can't find it now.
Hmm.. Am I maybe thinking of a list of pre-cooked ROMs for the Wing, or some other HTC? If I am, I'm DEFINITELY going to need some ROM recommendations.
Here are my stats, if it helps any:
rom version 3.57.502.2 WWE
rom date 7/17/08
radio version: 1.65.21.18
protocol version: 25.88.40.05H
tri-color screen
KAIS1*0
SPL-3.56.Hard
CPLD-8
.
.
Serial
image version 3.57.502.2
R 1.65.21.18
G 25.88.40.05H
D 3.57.00.00
Thanks again for any help!
if u really want a good cooked rom i suggest you try Garmins roms....they have the latest htc drivers built in...
thats all i can say
mazin13 said:
if u really want a good cooked rom i suggest you try Garmins roms....they have the latest htc drivers built in...
thats all i can say
Click to expand...
Click to collapse
he DOESN'T WANT a cooked rom he is looking for a pre-cooked rom.
@op did you check the kaiser wiki or htc's website?? 'cuz that is where you will find all the latest roms for your device that aren't cooked by a chef.
Also, look around for mbavrian's Kitchen Elements.
The "Base ROMs" on which our Chefs makes their gourmet meals are difficult to locate. Some chefs refuse to share like little playground children.
Others, Like NotATreoFan, have released their base for other people to use to make ROMs. Great Contributors.
Woops!
I guess I stated that incorrectly. Sorry!!
Actually I DO want a custom 'Cooked' ROM. My main purpose of reflashing the ROM is to get rid of all known bugs and bloatware. So I WANT all the custom registry hacks and patches to make everything run smoothly. I want the hacked video drivers (as they appear to currently be stable) and etc..
SO.. I'm looking for:
1) 6.1 OS with fast drivers and all known hacks and patches to have as few bugs as possible. UNLESS 6.1 has introduced some known bugs that can't be fixed (wouldn't surprise me with an MS product). IF there's a bug free FASTER version 5 OS, that will run on the Tilt, I'll be happy with that. One time I installed Win95 on a 1.6Ghz T-bird. Power on to fully loaded desktop was like 2 seconds flat.
2) bloatware removed so as to free up space, and I assume cleaning crap out of the registry wouldn't hurt with speed. Is there a system cache, and would it be beneficial to move it to the SD card? I've read that moving the IE cache to the SD card is asking for trouble, not sure that there's a concensus on that or if it's just opinion though.
OK.. that's going to get confusing. Scratch that and start over:
1) All known bugs hacked or patched.
2) All known speed enhancements (that don't compromise system integrity).
3) Rip out MS (or HTC ..or both?) crapware that COULD be replaced with faster / more functional counterparts.
4) Optional: pre-installed or at least packaged (cab?) applications to enhance functionality. My priority in applications is utility enhancement. Example: I can download 200 Flash / Java / MAME games to the SIM card some day if I get bored, don't need it in the OS. However, if there's a remedial photo editing utility that will allow me to edit my pics before I upload them somewhere, I want it.
I did manage to stumble across a wiki page last night: http://wiki.xda-developers.com/index.php?pagename=Kaiser_Cooked_ROMs
32 Developers and countless ROMs without any comparison isn't much help though. Can I assume all current ROMs are posted there?
Browsing through them, I recall that Alex's ROMs used to be the last word in ROMs, apparently dutty's were until he switched gears. HyperDragon seems to be terribly popular at the moment, but popular doesn't mean better.
I suppose I could try to gather all the available info into a giant spreadsheet, but the fact that about half the ROMs link out to a feature list is slightly discouraging. I think dutty's list of registry hacks ends in '.. and a bunch of other stuff I forgot', which is TERRIBLY discouraging (when trying to compare features).
Anyway, sorry if I'm rambling on here. Please don't take anything I'm saying as judgemental, I'm sort of thinking out loud trying to decide how best to proceed.
Say, has anybody considered building a CVS tree of sorts? I don't suppose you could have actual CODE stored in a repository without violating some sort of copyright or reverse engineering crap.. but a list of known code changes and etc. would seem to be a good idea. Since neither MS nor HTC has stepped up to the plate over the years, due to corporate greed, some sort of XDA-Dev code change tracking system seems like 'the last best hope' to get a decent OS. Ever.
That's why I'm jumping ship to try out the G1 after this. I don't believe MS will ever invest the effort to give us a 'business class' reliable bug free solution. ..let alone one that's innovative or even exceptional. They're style would lead me to expect them to wait till we have 800mhz handhelds, then 'patch' over top of everything they don't like to make it appear to behave better. ..and of course they would deem it necessary to add another programming layer to the OS to 'increase functionality' (read: bog down the OS).
Yup.. I'm definitely babbling now, so I'll just cut myself short.
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using? ..or one which already compares all the features, so I don't have to?
Better yet, Is there a ROM build specifically to fit what I'm looking for? I seem to recall Alex's were built somewhat similar, but the newest one is quite old now. Hmm.. there is no Windows Mobile revision list is there? I have no way of knowing which older versions would be good, and when bug patches were introduced and etc.
Oh well, guess there's nothing to do but dive in head first and start putting together the best feature list I can with what resources I have.
Thanks for any help! ..and if you read this whole thing, thanks for putting up with my rambling, lol.
Crogon said:
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using? ..or one which already compares all the features, so I don't have to?
Click to expand...
Click to collapse
I've never seen one and I don't believe one exists. You'll just have to do your own research.
Crogon said:
I guess I stated that incorrectly. Sorry!!
Actually I DO want a custom 'Cooked' ROM. My main purpose of reflashing the ROM is to get rid of all known bugs and bloatware. So I WANT all the custom registry hacks and patches to make everything run smoothly. I want the hacked video drivers (as they appear to currently be stable) and etc..
SO.. I'm looking for:
1) 6.1 OS with fast drivers and all known hacks and patches to have as few bugs as possible. UNLESS 6.1 has introduced some known bugs that can't be fixed (wouldn't surprise me with an MS product). IF there's a bug free FASTER version 5 OS, that will run on the Tilt, I'll be happy with that. One time I installed Win95 on a 1.6Ghz T-bird. Power on to fully loaded desktop was like 2 seconds flat.
2) bloatware removed so as to free up space, and I assume cleaning crap out of the registry wouldn't hurt with speed. Is there a system cache, and would it be beneficial to move it to the SD card? I've read that moving the IE cache to the SD card is asking for trouble, not sure that there's a concensus on that or if it's just opinion though.
OK.. that's going to get confusing. Scratch that and start over:
1) All known bugs hacked or patched.
2) All known speed enhancements (that don't compromise system integrity).
3) Rip out MS (or HTC ..or both?) crapware that COULD be replaced with faster / more functional counterparts.
4) Optional: pre-installed or at least packaged (cab?) applications to enhance functionality. My priority in applications is utility enhancement. Example: I can download 200 Flash / Java / MAME games to the SIM card some day if I get bored, don't need it in the OS. However, if there's a remedial photo editing utility that will allow me to edit my pics before I upload them somewhere, I want it.
I did manage to stumble across a wiki page last night: http://wiki.xda-developers.com/index.php?pagename=Kaiser_Cooked_ROMs
32 Developers and countless ROMs without any comparison isn't much help though. Can I assume all current ROMs are posted there?
Browsing through them, I recall that Alex's ROMs used to be the last word in ROMs, apparently dutty's were until he switched gears. HyperDragon seems to be terribly popular at the moment, but popular doesn't mean better.
I suppose I could try to gather all the available info into a giant spreadsheet, but the fact that about half the ROMs link out to a feature list is slightly discouraging. I think dutty's list of registry hacks ends in '.. and a bunch of other stuff I forgot', which is TERRIBLY discouraging (when trying to compare features).
Anyway, sorry if I'm rambling on here. Please don't take anything I'm saying as judgemental, I'm sort of thinking out loud trying to decide how best to proceed.
Say, has anybody considered building a CVS tree of sorts? I don't suppose you could have actual CODE stored in a repository without violating some sort of copyright or reverse engineering crap.. but a list of known code changes and etc. would seem to be a good idea. Since neither MS nor HTC has stepped up to the plate over the years, due to corporate greed, some sort of XDA-Dev code change tracking system seems like 'the last best hope' to get a decent OS. Ever.
That's why I'm jumping ship to try out the G1 after this. I don't believe MS will ever invest the effort to give us a 'business class' reliable bug free solution. ..let alone one that's innovative or even exceptional. They're style would lead me to expect them to wait till we have 800mhz handhelds, then 'patch' over top of everything they don't like to make it appear to behave better. ..and of course they would deem it necessary to add another programming layer to the OS to 'increase functionality' (read: bog down the OS).
Yup.. I'm definitely babbling now, so I'll just cut myself short.
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using? ..or one which already compares all the features, so I don't have to?
Better yet, Is there a ROM build specifically to fit what I'm looking for? I seem to recall Alex's were built somewhat similar, but the newest one is quite old now. Hmm.. there is no Windows Mobile revision list is there? I have no way of knowing which older versions would be good, and when bug patches were introduced and etc.
Oh well, guess there's nothing to do but dive in head first and start putting together the best feature list I can with what resources I have.
Thanks for any help! ..and if you read this whole thing, thanks for putting up with my rambling, lol.
Click to expand...
Click to collapse
You have to spend some time and TRY each ROM and see which one is suited for you.
Again, READ and spend time.
Read WIKI especially.
There is no 100% perfect ROM even if it is official one.
Crogon said:
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using?
Click to expand...
Click to collapse
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Cooked_ROMs
If you want a newest list, you are always welcome to Update the wiki
I'm heading for the aspirin bottle just now. I spent like 3 hours reformatting the info on the wiki page into a spreadsheet.. when I discovered that some of the authors are still releasing, but it's not on the list!
AAHHH!!
So basically, A full up to date list is needed. Let alone version comparisons or features and bug fix lists.
Good grief.
No wonder most people opt to install ROMs randomly till they happen across one they like.
.. I think I'll make a new wiki page eventually. Something along the lines of a Kaiser ROM Feature Comparison page.
Do I get a XDA-Dev decoder ring if I actually finish it? lol
ROM modders/developers!
I'm the developer behind ROM Updater. It's meant to be an universal ROM updater (which means, it doesn't really care if you're on CyanogenMod or you're on the "whitelist"-free of ROM Manager). There is even a PHP script (on the website) which will automatically create incremental updates, cool feature of my app which lets both you and users save a lot of bandwidth. Please consider "adopting" it, it's free ^^
elegos said:
ROM modders/developers!
I'm the developer behind ROM Updater. It's meant to be an universal ROM updater (which means, it doesn't really care if you're on CyanogenMod or you're on the "whitelist"-free of ROM Manager). There is even a PHP script (on the website) which will automatically create incremental updates, cool feature of my app which lets both you and users save a lot of bandwidth. Please consider "adopting" it, it's free ^^
Click to expand...
Click to collapse
Nice work Elegos
Fantastic, consider me a supporter.
I think u have delivered it pretty well
Update: I've released incremental.jar and relative sources. Go to the website and check
New in version 1.8 (from version 1.7):
- Tried to fix a Null exception error, received via Market (thanks for reporting!) (please test)
- Added incremental.php and incremental.jar (plus sources) in the git repository to easily create incremental updates
- Moved common variables in a singleton (SharedData class) and more comments for easier understanding of the code and less variables around
PLEASE NOTE:
You don't have to mess up with the ROM name anymore, the program will check for the ro.build.display.id (MOD name) and ro.build.version.incremental (!!!INTEGER!!! version number), as well as ro.product.model (for future releases, in our case be sure is "Nexus One"). The repository main.json file has a new variable, "model" which is, indeed, the same of ro.product.model. Future versions of the app will make impossible to download updates not for your phone.
DEVELOPERS:
You have no excuses now ! I've talked with some other modders who say, for example, their updates are changing rather all the files, and I say you it's not true. Making some tests I saw that using incremental updates make the update 50~75% smaller, even with MIUI weekly releases. This means "bye bye" to the bandwidth problems, both for hosters and users.
Just added your page as my favorite. Will study and use it later, hehe ,need some time to know about it~~~~
So how do I set up repository for. CM7 nightlies? Do I have to enter it manually?
Sent from my Nexus One using XDA App
I'll give it a go. I have been using ROM Manager and it works very well but I was getting concerned with the bandwidth used for the CM7 nighties.
This does support CM7 nighties right?
Also, what about getting notifications when there is a new build for ClockworkMod Recovery and backup/restore options for ROMs that I keep on my phone?
Wow, as a themer, I would have to say that the idea behind this is amazing. I would love to see it adopted by everyone. I would like to be able to see what exactly has changed between updates, it would save me a lot of time personally. I commend you for your work on this. Woot
@apratomo: you need someone who sets up a CM7 nightly repo. I can't, as it would mean I should support every ROM out there, and my bandwidth is limited (I can host one ROM if you want, not 1000 ). By the way you should edit the build.prop file in order to edit the incremental value and make sure the ROM name is allways the same (display.id).
@pfran42: it supports any ROM you want, this is why I made it
It actually don't check for new recovery images, as it relies on external repositories only, I may create a different application for that though. As of backup/restore, it currently has an option to backup the current ROM wherever you want (see options). When I discover how to restore a nandroid backup via command line, I'll add that feature too.
This is a great idea, however adoption may be slow. Even though its an AWESOME idea, it may be a good idea for you host a popular ROM elegos to get the ball rolling. I'd hate to see this die...
Ok so I have to launch a poll. Problem is that:
1. In the generic Android Development forums (where this really thread should stay) is overcrowed with posts, most of them are just publicity for apps on the market.
2. I'd love to have the attention of all the android people to partecipate to the poll. Of course I MAY create a CM7 nightly repo, but it would mean daily work for me (and a lot of space on my host).
I'm working on a system that should keep a list of repositories automatically updated every time you download a ROM with the app (accepting to send anonymous data). It's ready in the git repository, I'm waiting to push it live 'cause I want to create an interface to grab that data too (a sort of list ordered by phone model).
I think that just for starting I'd love to host a Nexus One Gingerbread AOSP, just like MicroMod777's one (TBH I already have that repo online, but it's frozen at version 20 as MicroMod is focusing on CM 7 custom builds, which I dislike for its too many customizations (both CM itself and MicroMod's)). Alternatively an AOSP 2.3 with no apparent changes (i.e. maybe CM with standard launcher). Any idea?
Sometimes you just have to prove how good your ideas are, because people are lazy... good luck my friend.
Sounds interesting.
I'm going to release a "major" update: all the times a user downloads a ROM and accepted to send anonymous data, the repository, ROM name & version and phone model will be sent to a database, which will return back a list of repositories directly in the settings menu!
I've released version 1.9 and made a Enomther Nexus One repository. Enjoy!
Version 1.9.1
- Fixed an untranslated italian string
- Fixed the import of a repository URL via the repositories list (new line at end of repository)
- Made the application more solid when there are connectivity problems / no internet available (no crash anymore)
awesome work!!
have tagged the link shall go thru it...gr8 job elegos ..!! ..PeacE
Awesome ^-^
AerialX said:
Alright, thanks for the results everyone. I asked because I wanted to decide which framebuffer method would be selected as the default... I decided on the "slow" version - 8bdefb7e - as it's the most compatible option. The "fast" version can be chosen as a preference for those who prefer the speed. It may not work on all devices, and seems to produce artifacts and some tearing, though it probably is preferable for most simply due to the speed.
So, here you go, latest version: Download
Built for ARM and ARMv7, does not include the NEON extensions. You may want to uninstall the old one before installing this.
EDIT: Fine, have a NEON build too: Download
Hint: the main change is the inclusion of settings. I consider this build to be very close to the initial release for the application on the Android Market. Just a few things remain...
What's Left
In order of priority...
Filtering of non-white-screen presets. The app will include the projectM preset library by default, excluding any that just result in a white screen. I don't believe I will be able to distribute any of the Winamp/MilkDrop library itself, as awesome as it is.
Stability enhancements. It's probably still somewhat crashy. I'm not sure how much, though. I'd love to get some detailed reports on how stable/crashy it is for you guys.
snoop() support, otherwise the wallpaper requires 2.3... I don't have anything older though. Would anyone be able to test on an older OS for me if I supplied a build?
x86 support. Means writing a few missing STL pieces.
NEON detection, and the loading of an appropriate optimized library. I get the feeling that this is just a placebo, but will try to get it in.
Optimizations. Would be nice if it didn't essentially restart every time you visit your home screen. I'm probably leaving this for a 1.1 release though.
Localizations. If anyone wants to help translate the settings page into their native tongue, I'll happily include them.
Anything else I forgot...
What I Need
It would be great if anyone who tries it can comment on its stability. Whether it often dies, reverts to some other wallpaper, completely kills your system, or whatever. Just give me your overall experience with the wallpaper. I'm not necessarily interested in hearing about its performance at this point - if it runs slowly on your phone, I suggest switching to the "fast" render method and only using presets that run speedily. Of course, miscellaneous suggestions / comments / criticism are welcome as well!
Another thing I was hoping someone could do is go through all the presets and filter out the bad "white" ones. The new settings page makes it easy to test a single preset at will. So if anyone is willing to do this, I could really use two zips: one containing all working presets from the projectM set, one containing all from the MilkDrop set.
As a base for the projectM set, please use this: Download
For the base MilkDrop set, find the attachment from a few pages ago.
You may also want to note any that run particularly slow, but please don't exclude them from these packages.
EDIT: As a test, feel free to try the exact same preset on both the non-NEON and NEON builds and see if there's any noticeable improvement there.
Click to expand...
Click to collapse
Hands down best app ever
Sent from my LG-P999 using XDA App
Any screenshots?
Um seems to be a few post missing in this thread... Usually when something starts like this:
Alright, thanks for the results everyone. I asked because I wanted to decide which framebuffer method would be selected as the default...
Click to expand...
Click to collapse
What results are we talking about here? What is this exactly? Kinda like writing a book that starts:
But when the baby came out looking like death on a hot tin roof, Jim finally found the nerve to call her out and say, "Devil wench, I will not accept that thing as my my spawn! I know you have been sleeping with your brother!"
Hi guys,
I've written a completely new Android binder driver (for IPC), which is targeted to solve some fundamental issues in the existing driver. One main improvement is to make concurrent IPC calls possible. Some background info can be found in my earlier post on Android kernel group:
http: slash slash groups.google.com/group/android-kernel/browse_thread/thread/c57874670e4decb1
(oops external urls are not allowed for new users
There weren't many people interested due to low volume of the group. Now that I have completed the first version, which is back compatible with the existing driver, and fixed a few bugs. I've tested on the ICS emulator and my phone U8150 Froyo. It seems to be running quite well, but I want to see how it runs on other Android devices while I'm getting my new phone. Test results, bug/issue reports, and of course community comments will be very welcomed, which are important for me to determine how the code should further move on.
Although not proven, I'm expecting not only those dual core phones, but single core ones will get an overall smoother response in various parts of the system.
Okay if this still somehow interests you, you can find my project on github
https: slash slash github.com/rong1129/android-binder-ipc
and just dive into the release directory, use the latest version (0.4 so far) to patch your kernel source tree, then upload the new kernel image to your device and see whether it works for you.
Note this is still an early release and has very limited tests so far. Please make sure you understand the risk before you hack your phone and always back up everything before you started. As other disclaims go, I'm not responsible for any damage may be caused by or related to using or in the process of using the driver
Lastly, happy hacking!
Cheers,
Rong
*subscribing to this thread*
Hi Rong,
thank you so much
our phones, tablets, etc.
can't have too much smoothness
I hope that I'll find some time within the next weeks to also give this a test on the Xoom and see whether it works (with ICS; Team Eos kernel)
there at least seem to be issues with ICS on the SGS (galaxys s1)
http://forum.xda-developers.com/showpost.php?p=23937103&postcount=2502
I found this thread . Is this driver the same on all android devices and roms? Or do you have to mod it for every single device/rom?