Related
Hi!
Since last week, I've been working on an usable kernel for the HTC Vox. I guess you've already looked at this post: http://forum.xda-developers.com/showthread.php?t=368014&page=5
More or less, I have a working kernel. I've tested some images against the modified kernel, and both Gpe and Opie get to the welcome screen (without getting stucked). Nothing is really usable, as they're not even compiled for this specific platform (cannot get to compile opie for arm by myself... yet), but as a base, it's not bad at all.
As I've seen on my previous post, there's people interested on this (3300 views make me believe that), what I would want to know is, are there more developers interested on building a linux port for the Vox? Testers will be needed also, but later, when we get to something useful for testing
If you're interested, reply!
Cannot help u develop anything here, but would be a willing tester for it... thoroughly
I'd love to help, but I'm in the middle of moving to a new place and won't have internet most of the time next 2 weeks.
Do you have a Wiki or other place for collaberating? SourceForge perhaps?
I do have a wiki, but upload is no faster than around 80kB/s
In case you haven't seen it, you have a new build of the kernel on the other post, along with links and a little manual to start a graphic environment on the vox.
@barth666, @StefanHamminga
I've been thinking about it, and... I don't know what to do I mean, I think Sourceforge is the best place to dump it all, and it gives us a wiki too. On the other side, here is the xanadux wiki, and maybe it would be a good idea to let sourceforge host the files, and leave the wiki in here with other HTC phones... what do you think?
Oh! For GPIO dumping, the only thing I've seen working is the linwizard project's Haret_Omap.exe (in case you want to try to guess where the damned keys are )
PS: Anyone has an HTC Tornado? I'd love to know if the tornado kernel makes the leds and vibrator flash, I can't find where they are!
biktor_gj said:
PS: Anyone has an HTC Tornado? I'd love to know if the tornado kernel makes the leds and vibrator flash, I can't find where they are!
Click to expand...
Click to collapse
I have a tornado (and vox and wings), so tell me what to test
I know from the ml_iPod wiki (I am the admin) that SourceForge is really slow and the Php and Sql versions are old, in case you want to set up something like MediaWiki! You might want to try http://code.google.com/ , it has a built in Wiki and you can host files!
Just a suggestion
Keep up the good work
EDIT: I could even set one up, if you want, but I am not into coding at all!
Hi! Sorry for the delay, but I'm having lots of work this week and I've been unable to keep on with this...
@Walram: On the following days I'll try to build a kernel for you, wich should put all the lights on and makes the phone vibrate until you take the battery out Obviously just for testing, it shouldn't break anything, but I need to know if the originally-made-for-the-tornado vibrator and led drivers actually work on the tornado... Thanks!
@Frauhottelmann
Didn't know that google gave that service too! will look at it this weekend and post back when I have something done with this.. thanks for the feedback!
walram said:
I have a tornado (and vox and wings), so tell me what to test
Click to expand...
Click to collapse
Hi!
Ok, here's what I want you to try. If you haven't downloaded it yet, download the Linux Test Image:
http://rapidshare.com/files/93938763/test.zip.html
Then, download the kernel for the tornado:
http://rapidshare.com/files/96145010/kernel_tornado_driver.tar.gz.html
Dump the contents of the first file to the memory card, and then overwrite the file "zImage", with the one from the second link. Run haret, and hit "Run".
It should, at least, boot. If it doesn't, tell me where it gets frozen (could be that you only se some dots on the screen, whatever appears, just tell me )
If it boots, don't stop looking at the leds (charge/bluetooth leds mainly), they should, at least, flash -theorically they should stay on all the time-. It also should vibrate, at least for a quarter of second
I just need to know what it actually does!
Thanks!
So what about a dev-page? Then you don't need to upload it to Rapidshare and you can see the progress better!
Hi frauhottelmann,
I'm going to tell you the truth. I think it would be better if it's you who admins a site for this project than if I do, for various reasons:
1. I started all this thing, but I'm no owner of anything, by now I just hacked four things to make this phone boot a kernel, but no more.
2. I've seen your work at the ml_ipod sourceforge page, and think it's usable, clean, and nice, and I think that's exactly what we would need (even if it's a little slow just as you stated in your previous post). I could make the graphics for the web (I'm quite decent at photoshop), but I have never built a wiki, or a project anywhere else, and I don't know a sh** about it, so that would be another big thing to learn, and for now, I gotta learn more about the linux kernel, and that itself it's huge.
3. I don't think I can handle work, classes, building patches, kernels and bootstrap images and administrate a site, it feels like too much for me
Conclussion? I think it's better to let people do what does better, and I'm quite sure you'll do it better than I, so if you want, it's all yours
PS: In any case, we will need a name for the project, any suggestions?
What I have heard from the ml_iPod developers is that upload to SF is not a nice process either. I still think Google code is better, although it's not as customizable as SF.net. But we could also set up a page on Googlepages (pages.google.com) and then point to the Google code site with the Wiki and downloads!
I can offer my technical know-how (SPL, GPIOs, etc.)
Since I have little time you should ask me precise questions for which I can try to find the answers.
Sorry for the delay...
frauhottelmann said:
What I have heard from the ml_iPod developers is that upload to SF is not a nice process either. I still think Google code is better, although it's not as customizable as SF.net. But we could also set up a page on Googlepages (pages.google.com) and then point to the Google code site with the Wiki and downloads!
Click to expand...
Click to collapse
So we can start using google code, and stick with it if it goes well. We can always change the hosting if something goes wrong! About the wiki, the easiest thing is start with google code too, and simply link the xda wiki to it...
i can't code, but i can keep you company maybe
i am here if help is nedeed
But what name do we want to use?
Linux for Vox?
LinVox !
how does that sound ?
just kidding
waiting to get linux running on my vox....
But what name do we want to use?
Click to expand...
Click to collapse
Hooked on Vonix!
vonix sounds ok
can also try "Mobile TUX"
wow
this is an incredible news ! linux on the Vox !
I'd love to flash mine with a movibuntu distro =)
How do you guys feel about splitting the project up in several subprojects?
Like:
Kernel and driver work: TI OMAP HTC Vox board patch and perhaps drivers
Base system: minimal rootfs and toolkit to utilize all Vox functionality
Usability: GUI and (for instance) Android support
This would also enable us to share the base system & usability work with other 'linux on smartphone' and embedded projects.
I do have a suggestion for the base system:
www.emdebian.org
Very up to date build toolchain for arm (GCC 4.x toolchains) and you can have apt support on the base rom. This would allow access to a huge amount of packages that can be used with relatively little effort. Others I've checked out are the new mobile ubuntu (system requirements way to high), MontaVista (severe lack of proper documentation to get up to speed quickly), uClinux (uses ulibc instead of the faster full fledged one, in my opinion we'd better trade some storage for more speed) and some others I can't remember now...
PS. I've got internet at my new place and I've recovered my bricked wizard from the 'spare electronics bin', so finally I can spend some more time on this
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
*** PLEASE READ CAREFULLY BEFORE INSTALLING OR FLASHING ANY SOFTWARE POSTED IN THIS THREAD ***
The software posted here is for TESTING purposes only, The Polaris Android Linux development team or any of the posters of software or links to software on this thread, take absolutely no responsibility or liability for damage caused by the result of installing or flashing software or links to software found on this thread - correctly or otherwise, you do so on the sole understanding that you do so at your own risk. A final version will be posted on completion of a version 1 kernel at which point testing and support for the kernel will be moved to a suitable thread. Please do NOT post support questions on this thread - this is a development thread ONLY.
Development work is sometimes done in the irc channel: #htc-linux. To follow the latest developements please read the daily logs which can be found at: http://irclog.iclem.net/?chan=htc-linux&day=13
Lastly, Please do not use bad language in your posts, I have my little girl with me most times and do not need her to read such things. Appreciate your understanding.
Update: We now have a few threads devoted to userspace (system images), This is a KERNEL DEVELOPMENT thread which is starting to get too big for devs to follow. The purpose of a good development thread is to serve as an archive and a blueprint for future developers and that is hard to do when you have hundreds of non-related posts. I have therefore asked the moderator to move all non-kernel posts to their appropriate threads.
-----------------------------------------------------------------------------------------------------------------------------------------------
01-09-08 - new link to files for working wifi
http://www.4shared.com/dir/19593527/3cb53c3a/sharing.html
24-07-09 - If anyone is interested in making themed system images, he's posted this link to help you learn how to do it:
http://forum.xda-developers.com/showthread.php?t=471586
19-07-09 - New kernel with changes from Vogue branch released. I am currently testing radios and resolutions. List of resolutions from kaiser thread
15-07-09 - A revival in our development as meant we are now catching up with the other devices with development on the project. Thank you to all who donated to the purchase of development Polaris that will be used by vilord, from vogue forum to help us with the project.
Current developers:
Life02 - Fixed GPS, Working on Battery issues.
Vilord - On holiday, now in possession of a Polaris. Also working on Bluetooth.
Newbie16 - Fixed Wifi - need to add irq's.
05-07-09 - New 1.5 ION build of Android for the Vogue has been reported to work well for the Polaris and can be found on the Google Vogue repository. The new 1.5 builds are noticeably also faster and smoother than previous builds. Some troubleshooting info can be found at the Androidhtc website for these builds (thanks freddycs). APN details can be found on Wikipedia - (thanks Mormy)
Things that do NOT work at present:
Bluetooth - No - Working partially for Vogue
Wifi - WORKING! *NEW* - thanks to a lot of effort by my friend Newbie16 - thanks mate
Camera - No - Working for Vogue
GPS - now working thanks to life02! - Well done my friend
---------------------------------------------------------------------------------------------------------------------
A new thread for budding designers has been set up by Venigo, (thanks matey!) who will lead the design side of the Polaris Android project (kind of makes you a little emotional thinking we're at that stage where we can start thinking about wallpapers and themes doesnt it?) Thread can be found here: Polaris Linux Android - Wallpapers, Themes and Icons
UPDATES: - Please check the WIKI for up-to-date progress updates here: Android on Polaris WIKI (Thanks excogitation)
NEW TESTING AND BUG THREAD ANNOUCEMENT:
marcelkordek has kindly started a thread for testing and bug reporting as we now have an almost usable Android image which can be found here: Polaris Android Project - Testing and Bug Reporting The thread will also be used to provide updates on the progress of the Android kernel as well as providing feedback to the devs on the latest posted images. Please ensure that the Testing and Bug Reporting thread is used for reporting user experiences and enable to keep the development thread cleaner and make life easier for the devs, whom you will all agree are doing an excellent job to support our beloved device.
18/1/09 - Working Radio with calls at last! Audio and SMS still not working but GPRS does but with a bit of fiddling.
16/1/09 - SMD code is nearly fixed by DZO, Rogro82 will be making a new image soon. Most of the development at this time is being reported in the Kaiser forum: UPDATED!!! - Google Android and Linux for KAISER!! as DZO was sent a Kaiser and he is working on the issues on it.
5/1/09 - DZO is working to bring the Kaiser and Polaris branches together so that the kernel will work on all our devices. Waiting to see what changes are made.
1/1/09 - Rogro82 uploaded a "booting" 1.0 SDK along with source files and instructions (below). Although this is very much a work-in-progress, it is the first bootable version of the 1.0 SDK for the Polaris.
11/12 - DZO and rolk worked out some changes that may help us resolve the SD Card stability issue. Dwaradzyne posted up a Zimage with the changes for testing.
CPLD Handbook
GPIO Manuals
LATEST FILES USED FOR DEVELOPMENT:
1/1/09 - Latest files are packed in this archive - to boot simply unpack to the root of your sd card and run haret (included).
A big THANK YOU to Rogro82 for getting the 1.0 SDK booting on the Polaris
Enjoy!
-----------------------------------------------------------------------------------------------------------------------------------------------
FIRST POST
I'll start with another simple question I cant find an answer to:
WHY CANT WE JUST PORT THE G1 ROM TO THE POLARIS?
#2 reserved for update
I will try to search too
I will try to put as simple as possible. Building a ROM requires combinig two parts:
1. Kernel/drivers part.
2. Applications and stuff.
In case of Windows Mobile part 1. in practice always comes from official HTC Polaris ROM. Part 2 comes from other official HTC ROM (could be other phone) and it can be modified by cooker.
We do not have a full working Polaris Android ROM, and we cannot just cook without part 1. Part 2 is available as Android sources are open.
The reason why we did not have 3d driver working on Polaris immediately after first Diamond ROM was available is that part 1. is not transferrable from one model to another.
Part 1. in Android is Linux kernel. We must get involved in Linux kernel developement for Polaris to bring Android to our phones.
why do we always want our phones to look like other phones. why cant we just be unique. we are windows mobile. TOP DOGG. i like windows mobile theme especially when its black. i like g1 but the design looks ancient. its not 2008 more like 1998
dortyboy said:
why do we always want our phones to look like other phones. why cant we just be unique. we are windows mobile. TOP DOGG. i like windows mobile theme especially when its black. i like g1 but the design looks ancient. its not 2008 more like 1998
Click to expand...
Click to collapse
absolutely agree. Copying iPhone was fun the first 2,3 months. Why not trying to develop really good apps with nice UIs and make own ideas into real interfaces for throttle launcher, M2D etc etc - posibilities are nearly endless.
i absolutely agree. i havent seen not one cool program thats actually usefull in our daily life for windows mobile not since i had a treo way back.
programs like directory; that could look at your number and tell u the owners name and adress
stuff like that. maybe tell u when zip code the call is coming from. useful programs. not the crappy programs that just try to make your phone look pretty.
thats why people go to iphone, the programs are useful in peoples daily life but not windows mobile
Here we go
ROM download :
Code:
http://rapidshare.com/files/155612986/Android_dump.rar
I think its a probleme with the boot loader and some part of the android code which isn't public
Have look here :
Code:
http://www.limofoundation.org/en/limo-press-releases/limo-foundation-statement-on-the-google-android-g1-handset.html
dortyboy said:
why do we always want our phones to look like other phones. why cant we just be unique. we are windows mobile. TOP DOGG. i like windows mobile theme especially when its black. i like g1 but the design looks ancient. its not 2008 more like 1998
Click to expand...
Click to collapse
Are you new to the mobile device world?
We are not trying to get it to "look like the G1". We are talking about using a completely different operating system.. lol.. and you are talking about a black windows mobile theme and how the hardware of the G1 looks ancient.. lol..
Oh.. and "being unique" in this case would be having Android on a non G1 phone.. that would be unique. Windows mobile is not unique.
m.schmidler said:
absolutely agree. Copying iPhone was fun the first 2,3 months. Why not trying to develop really good apps with nice UIs and make own ideas into real interfaces for throttle launcher, M2D etc etc - posibilities are nearly endless.
Click to expand...
Click to collapse
Developing apps and trying to use resource hog throttle launcher is nothing close to having a brand new stable device operating system.
m.schmidler said:
absolutely agree. Copying iPhone was fun the first 2,3 months. Why not trying to develop really good apps with nice UIs and make own ideas into real interfaces for throttle launcher, M2D etc etc - posibilities are nearly endless.
Click to expand...
Click to collapse
Maybe we can develop better apps under Android?
Look at the apps currently available for iphone - hopefully Android will get better market penetration than Windows Mobile, and, because it's open source it opens up a whole range of possibilities for developers.
I say if it can be done, it should be done!
dwaradzyn said:
I will try to put as simple as possible. Building a ROM requires combinig two parts:
1. Kernel/drivers part.
2. Applications and stuff.
In case of Windows Mobile part 1. in practice always comes from official HTC Polaris ROM. Part 2 comes from other official HTC ROM (could be other phone) and it can be modified by cooker.
We do not have a full working Polaris Android ROM, and we cannot just cook without part 1. Part 2 is available as Android sources are open.
The reason why we did not have 3d driver working on Polaris immediately after first Diamond ROM was available is that part 1. is not transferrable from one model to another.
Part 1. in Android is Linux kernel. We must get involved in Linux kernel developement for Polaris to bring Android to our phones.
Click to expand...
Click to collapse
Thanks for the idiots guide dwardzyne!
So that very clearly explains the kernel level requirement.
OK. Second question:
With regard to part 1 - Kernel/Drivers - Can we convert the vogue version since it seems to have the most work done to it? What would need to be done to it to make it work?
imfloflo said:
I think its a probleme with the boot loader and some part of the android code which isn't public
Click to expand...
Click to collapse
a boot loader :
Code:
http://www.denx.de/wiki/U-Boot/WebHome
bally3 said:
Thanks for the idiots guide dwardzyne!
So that very clearly explains the kernel level requirement.
OK. Second question:
With regard to part 1 - Kernel/Drivers - Can we convert the vogue version since it seems to have the most work done to it? What would need to be done to it to make it work?
Click to expand...
Click to collapse
Indeed kernel developement for Kaiser and Polaris is based on Vogue work. It slowed down because of SD stability issue.
dwaradzyn said:
Indeed kernel development for Kaiser and Polaris is based on Vogue work. It slowed down because of SD stability issue.
Click to expand...
Click to collapse
I believe the sd card issue has been resolved on vogue and they've moved onto other things (camera etc). but it seems like its the end of the road for the Polaris - apart from rumors that someones supposed to be sending a kaiser or a polaris to dzo for him to work from. This kind of points to that dzo is the only person on xdevs capable of working at kernel level with a kaiser or polaris?? That cant possibly be true - can it?
bally3 said:
I believe the sd card issue has been resolved on vogue and they've moved onto other things (camera etc). but it seems like its the end of the road for the Polaris - apart from rumors that someones supposed to be sending a kaiser or a polaris to dzo for him to work from. This kind of points to that dzo is the only person on xdevs capable of working at kernel level with a kaiser or polaris?? That cant possibly be true - can it?
Click to expand...
Click to collapse
He already has the knowledge... He wants to share his knowledge, if someone send him a Kaiser or Polaris, and will make it work... I thought there were plenty of users willing to send there old or half bricked kaiser or polaris... but still nobody send him one... as far as I know...
Nobody keeps nobody up to date in the kaiser thread... So I really don't know what is going on... But they still don't have a decent fix for the DMA (SD-Card read/write) problem (as far as I know).
Porting the G1 rom isn't a possibility, you first have to have drivers for our device, since we haven't got a driver to read/write to the internal memory (not the RAM), it still cannot boot .
I hope this project will really come of the ground finally... It's half way there... but still not finished (if you ask me, due to miscommunication and not working together of users, because they all want to be the first who got it working to show off with it... (so they are all working on the same piece of code, which is a waste of time if you ask me)).
Maybe one of us can contact DZO, check what he needs to continue our development. Because without the SD-Card driver we can't continue...
dubbeld00 said:
Maybe one of us can contact DZO, check what he needs to continue our development. Because without the SD-Card driver we can't continue...
Click to expand...
Click to collapse
I'll contact him, I dont think there are many users who would just send a device worth a couple of hundred euros to a complete stranger though many would tell you they would at the time. With the P3D driver their was only one person who was willing to loan a unit for development - and that was only because they were in the same country. I was asking for ages before that.
is their any other way we could help him? surely the internal workings of a polaris rom coupled with the specs could be used if dzo would do what NuShrike did on the p3d driver which was tell us to try things he worked on? I'm sure there would be willing volunteers including myself who he could talk through it on the forums or on the #android room.
I can't offer to donate my polaris as its the only mobile I have.. but I would be more than willing to try things out on my xda or provide any other help possible to get this project moving.
Hopefully one day a fully working Android will be a reality on polaris
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