The intent of this thread was to provide a consolidated answer to all of those waiting patiently (some, not so patient) for a complete Android ROM for the SE Xperia X1.
Many perceive Android as "a hacker's OS" because it is both open source, and supported on so many other HTC devices. Because of this, I suspect many of the "spectators" here (like me) incorrectly assumed that Android on Kovsky (or, any HTC smartphone) would be a straight forward affair, considering some of the amazing work done here with the Windows Mobile ROMs.
It seems, however, that creating a usable Android ROM for Xperia is far more difficult than creating WM6 ROMs? Android has been out for quite some time and there's still no widely available Android ROM for Xperia X1. It is for this reason that I've started this thread.
I'd like to hear from those that have/are working on Android about the challenges in putting together an Android ROM for Xperia X1. What has contributed to this being a difficult OS to port to Kovsky?
Is it driver support? Perhaps Kovsky has a unique selection of hardware that complicates the process? Or, has much of the effort been directed towards Haret vs. a native ROM? If so, why? Can the Haret work be merged into an effort to create an Android ROM or are these different approaches completely exclusive to one another?
Perhaps there are IP/DRM/license issues that are complicating the effort? I'd very much like to hear from ROM chef and devs working on this port.
While it may seem like a idealist perspective, I wonder if some dialog on the issues surrounding an Android port/ROM might result in greater community involvement, and ultimately a stellar Android ROM for one of HTC's most beautiful smartphones. I'm certain that interest in Android on Kovsky is very high. Are there areas where the community might be able to assist with direct hardware, financial or other contributions?
So please, sound off. I'm very interested to hear about chefs/devs experiences with Android and I'm certain there are many here that would like to hear more about this port.
I just didnt know how to tell all you told here... I really want to know because I love my x1 and I love Android.. but i can"t help
i have just check out the Kovsky project from Gitorious, but still don't know how to work on it. 'cause i don't have much knowledge about develop kernel and open source, why don't we have a tutorial thread about this?
You people asking when a Android rom is coming just about every day are so funny. First of all their are still major issues that need to be worked out. Android running from haret is not even every day usable yet so what is the freakin point of expecting a rom now or asking about it? Do you guys want a rom where you phone won't even last 2-3 hours, GPS dosen't work along with the camera etc......? We need All the issues fixed before we can even be thinking about a rom. When Android from Haret is everyday usable then lets start talking about a rom. So can we please give the Devs a break about this rom nonsense and let them work in peace, when their ready to release a Android rom they will release a Android rom.
wphoenix said:
i have just check out the Kovsky project from Gitorious, but still don't know how to work on it. 'cause i don't have much knowledge about develop kernel and open source, why don't we have a tutorial thread about this?
Click to expand...
Click to collapse
would like that too, i've only been reading for some good time about the advances, and would like very much to take part in the development of the kernel, but don't really know where to start from
Also, what Viper says its very true... the work is probably a long way from done, depending on how much help the dev's get, which is, from what i've seen, not much.
about Toe_Cutter's comment "I wonder if some dialog on the issues surrounding an Android port/ROM might result in greater community involvement, and ultimately a stellar Android ROM for one of HTC's most beautiful smartphones" ... well, yeah, i think it could... at least i hope so.
xD
cool down all your heads and lets just help in every way we can
...as (ilgreco112) does xD... cheering up isn always bad hahaha
ps: first post!! ... Hi!
Viper89 said:
You people asking when a Android rom is coming just about every day are so funny. First of all their are still major issues that need to be worked out. Android running from haret is not even every day usable yet so what is the freakin point of expecting a rom now or asking about it? Do you guys want a rom where you phone won't even last 2-3 hours, GPS dosen't work along with the camera etc......? We need All the issues fixed before we can even be thinking about a rom. When Android from Haret is everyday usable then lets start talking about a rom. So can we please give the Devs a break about this rom nonsense and let them work in peace, when their ready to release a Android rom they will release a Android rom.
Click to expand...
Click to collapse
As a dev, I bet it IS tiring hearing all the spectators asking about an Android ROM.
But what do you expect when spectators ask about the issues, and receive nothing in response?
In my original post, I chose my words very, very carefully, because if you go back and read it again, I never asked when, I only asked the why and how.
Why is it that no one can provide a response to this question? I searched the forum, and read thru dozens of posts trying to understand what this port might require, and I got nada (except several polls asking about an Android ROM, and a few more posts telling the spectators to quit asking about an Android ROM).
Anyone care to break the cycle and help the community understand the issues?
Well, the problem is that you can never guess what's required and how to achieve it. First of all, developers really know nothing about the hardware before they begin hacking it. Until you finish the job, you can't estimate the time it takes to complete. The major problem is that most of us devote just a tiny bit of our time to the porting, because there are lots of interesting things to learn and to do except it, but mostly because everyone's either studying or working (or even both).
But if you really want to know what's needed.. well
1. Fix the LCD panel (add the initialisation code)
2. Fix the power saving (that's the greatest PITA right now) and 3D (the latter should be easy and is not really critical)
3. Implement Bluetooth, FM Radio, Camera (Should not be really hard on the driver side, but rather on the RPC protocol side)
4. Fix USB (should be easy.. actually, everything's done on the device driver side, the problem seems to be with the msm usb driver itself.. just needs real debugging)
5.Make a version of rom that boots from NAND (well, once you get the LCD to work correctly it's not a problem. It actually boots very well off nand, but without LCD and USB working it's not much fun, to tell the truth)
6.Clean up the code, drop the ****ty-droid and head forwards to SHR/Maemo MER/Meego or some other real linux distro with X11 and other things
7.Write up misc stuff (like optical joystick, illumination, new keypad driver and others)
But really, it you want to help, just begin researching everything yourself and exploring wince drivers. You know, Theo de Raadt once said: "shut up and hack", and that's the only way to get things done.
full ack
@sp3dev
full ack your post. the main problems ar not at android 2.x this source we have. but the kernel an its's modules (for kovsky) are the problem.
regards
Toe_Cutter said:
As a dev, I bet it IS tiring hearing all the spectators asking about an Android ROM.
But what do you expect when spectators ask about the issues, and receive nothing in response?
In my original post, I chose my words very, very carefully, because if you go back and read it again, I never asked when, I only asked the why and how.
Why is it that no one can provide a response to this question? I searched the forum, and read thru dozens of posts trying to understand what this port might require, and I got nada (except several polls asking about an Android ROM, and a few more posts telling the spectators to quit asking about an Android ROM).
Anyone care to break the cycle and help the community understand the issues?
Click to expand...
Click to collapse
The ROM question has been answered time and again throughout various threads on xda-dev.
There is no real issue "porting" Android to kovsky. Android is a virtualized environment running on a linux
kernel and it is that kernel that has to be ported. "Android" runs 100% on kovsky with minimal modification.
So. There is only one issue with the linux kernel - that issue is when the linux kernel for kovsky
is good enough for someone to make the effort to pack up a ROM with that kernel,
a bootloader and the android system.
Now, the consensus is the kernel isn't as yet good enough for daily use -
if someone with the skills decides it is and makes a ROM, then they will
obviously do so.
The list of kernel stuff to be fixed is broadcast all over this board and asking kernel devs
to repeat themselves ad nauseum won't get it done any faster
Related
I'm looking in every now and then following up on development av new ROMs, but it seems as this has stopped.
alcaline no longer develops his ROM and there hasn't been any resent updates in arpy's thread either. Have I missed someone? Are there more ROMs out there for the Wings that I don't know of?
If you know, post some info or maybe some links to new ROMs that are compatible with the Wings (s730).
TIA
http://forum.xda-developers.com/showthread.php?t=397164
And i am going to upload the kitchen for wings
because i don't have this phone.
Excelent!
Must have passed right beneeth my nose
thx!
Not much going on for the Wings (cooked ROMs)
I think the development of cooked roms for the Wings are fainting. Unfortunately I would say because I think there is lots to gain if someone develop a better and faster WM6.1 ROM for our unit. There are 2 ROMS available now and for both ROMS counts that there is not much going on in terms of development.
I currently use Alcaline's cooked ROM. It does a fine job but there are some glitches to work on. Unfortunately Alcaline stops working on the project.
True. Seems sad, as this is a great unit.
I'm thinking about taking up development of a ROM but I have to read up on a couple of things first. I'm no programmer but a amature hacker. So don't expect any miracles (or speed for that matter).
Any input from the already enlightened would be nice.
To me it seems that there is no more exciting things to work on for this phone.
The speed (or lack of speed) is due to the crappy phone itself. So not much to do about this
Except disabling the home screen, with increases the overall usage quite a bit for me at least.
But disabling this makes the whole interface ugly.
So I am holding on to this phone just hoping that a unit with Google Android will pop up in near future,
where everything is customizable
Hi folks. Sorry to start a new thread but there's something bugging me around here. If by any chance you mods think this post is useless please close it and accept my apologies.
It's known to the most of you that the first version of drivers didn't worked on all roms. That issue forced the developers to do a workaround and slow down the process to get it working on those roms and created a new set of drivers that is not so fast as the first one.
So... i was thinking on this and decided to start a poll in order to give a hand to the developers in wich way they should follow. What do you prefer?
A Gold XDA based ROM with fastest drivers and less compatibility with all roms? (forcing all XDA members to flash their phones - not a big deal i presume)
Or a set of drivers compatible with most of the roms but with slower performance?
I know this is a controversial issue and the urge of the drivers working on our kaisers is huge but i think we would have more if we had a custom GOLD XDA rom
Just My 2 cents
Cheers,
Draco
kinda seems like a no-brainer honestly (unless you're petrified to flash or just despise 6.1). They will develop said drivers and you have a million chefs making a million roms from them...
Fared said:
kinda seems like a no-brainer honestly (unless you're petrified to flash or just despise 6.1). They will develop said drivers and you have a million chefs making a million roms from them...
Click to expand...
Click to collapse
I have no problems at all flashing my phone. I assume that there are some people who are not comfortable doing that but.... this is XDA. And if they are here that's because we all want to get the most out of our phones. And that is the tricky part of this poll. Developing the drivers based on one specific rom ( a ported one form Diamond or Raphael or an official kaiser one ) will be the more accurate and fastest way to get there.
Again... just my 2 cents
Draco
first:
flashing rom is a non-trivial task for a huge majority of users. leaving them out in the cold sounds like a very selfish position. If not for this reason, maybe avoiding a flood of "I bricked my tilt, help !!!!" threads may be a better one.
second:
Anyway, as i understood it what is slowing down FPS in the new version is the enabled VSync, which yields less tearing and improved smoothness (sounds like a shaver commercial, i'm afraid). I don't know what the refresh rate of a kaiser LCD is, but anything higher than 75fps (ie 15ms refresh rate) is a complete waste.
draxredd said:
second:
flashing rom is a non-trivial task for a huge majority of users. leaving them out in the cold sounds like a very selfish position.
Click to expand...
Click to collapse
Not at all draxredd. Although i'm a junior member this is the second time i'm on XDA. I'm here for almost 7 years. Believe me, this is not a selfish position. As i was able to get some help to start flashing all of the members here on XDA will get that help too. The first time i flashed my first phone i was scared to death but... it's all the same. It only hurts the first time.
As i stated before this is just my opinion. The more roms the developers must include in the drivers development process, the more difficult it will be and much more time will be wasted.
Draco
haste... makes waste.
And if only one rom was to be designated as a target for the driver, it has to be the official HTC one, for two reasons:
- enabling driver support for a huge majority of users
- sticking it to HTC, deep.
draxredd said:
And if only one rom was to be designated as a target for the driver, it has to be the official HTC one, for two reasons:
- enabling driver support for a huge majority of users
- sticking it to HTC, deep.
Click to expand...
Click to collapse
What about performance issues? Doesn't that count as well?
Anyway.... i've started the poll just to check your opinion against wide compatibility among all the roms versus one specific rom fully optimized. Let's not get far from the main question
By the way... my kaiser has the official 6.1 rom from HTC... for now
cheers,
Draco
I'm for Flashing myself, but the in the ideal world both sollutions would be best so no one comes off short. However the kind developers should be aiming at the most stable of the 2 first.
Looking at the driver progress it looks like theyre slowly getting there and getting the driver to work on the latest 6.1 roms
I voted for compatibility with the official ROM, simply because it's an identifiable standard that everyone recognises, and which everyone has on their phone by default. Cooked ROMs are great, but they're all individual, designed by individuals and used by individuals with the same tastes/needs - not one of them will suit everyone else, with or without drivers, whereas drivers released for the official ROM should work with pretty much everything else.
It's too early to say whether drivers developed for the standard ROM will always be slower than those for a cooked version, and I'm sure the very brilliant developer of those drivers will do their best to minimise any performance loss, assuming their is any in the longterm.
Vastly improved performance for the majority (and what that means for sales of the Touch Pro etc) has to take priority over a marginally improved performance in a niche ROM, aimed at an elite few, surely? At the end of the day it's entirely down to the developer what they do, irrespective of any poll here, but that's my take on it anyway.
Maybe i didn't expose correctly my idea.
There isn't any XDA Gold rom nor any kind of perfect ROM. The XDA Gold rom is just a concept and the first name that crossed my mind.
This is a big community and has some big brains around here. The exchange of knowledge bettween everyone is a plus and that opens a big wide world to explore.
So.... let's just imagine this scenario, ok?
The developers will pick a base rom. It really doesn't matter if it is a ported rom or a Official one. Preferably one that is fast and stable enough. The driver will be written over that rom. Users (those who want obviously) will test the rom for bugs and then chefs will try to cook out a 100% clean (note that by clean i mean a rom just as close as an official rom regarding to apps) fast and stable rom.
Of course this is just a crazy ideia but that i was thinking of. Create the first genuine XDA rom based on one device.
Note that there are many roms out there based on diferent releases. Make the drivers compatible with all of them will make the development process slow down and eventualy fail. That's the main reason i started this thread.
Now that the concept of the "XDA Gold rom" was properly explained (i hope) let's get on with the poll.
Draco
DracoLX said:
Now that the concept of the "XDA Gold rom" was properly explained (i hope) let's get on with the poll.
Click to expand...
Click to collapse
As long as "XDA Gold" = HTC Latest Official version I cant see a problem. It's when drivers are developed for anything other than the official ROM that we'll encounter problems. All the chefs can base their designs starting with official ROMs and work out from there. In the end it will depend on whether those developing the drivers want to satisfy the larger number using official ROMs or those using Custom ROMs where the chef has not saught to maintain driver compatibility. I've therefore not voted because it depends whether "XDA Gold" does in fact = HTC Latest Official version - we weren't told.
Are you even sure that theifference is that huge?
They might be able to provide two sets to cover all ends without much additional work.
DracoLX said:
Note that there are many roms out there based on diferent releases. Make the drivers compatible with all of them will make the development process slow down and eventualy fail. That's the main reason i started this thread.
Now that the concept of the "XDA Gold rom" was properly explained (i hope) let's get on with the poll.
Draco
Click to expand...
Click to collapse
IMO, The drivers only need to be compatible with an official based rom. It's up to the chefs to make the drivers work with their rom. Now, if the root of the compatibility issue can be resolved, I think things can progress forward at a faster rate.
DracoLX said:
It's known to the most of you that the first version of drivers didn't worked on all roms. That issue forced the developers to do a workaround and slow down the process to get it working on those roms and created a new set of drivers that is not so fast as the first one.
Click to expand...
Click to collapse
FALSE. Two separate issues.
First, is dlls load differently between stock or hacked/cooked roms due to memory mangling by G'realoc going into cooked roms. An attempt to fix that was in the updated release.
Two, the screen update style in the first release was really just a hack that hijacked DDI's screen refresh routines. The 2nd release finally got the 'official' way to work so the hack was removed.
I voted faster...there isn't any other reason I came to XDA other than customizing.
Anyone who doesn't want a faster cellphone won't appreciate the new D3D drivers anyway.
There are may reasons the XDA Gold Rom (HTC Original 6.1) may be slower. Cooks reduce the software on the rom and use newer software versions, these may be faster than the previous ones.
Also this software is not from the Kaiser sometimes these may be causing the incompatiblity problems with the drivers.
The HTC original rom is slower to start than most cooked roms anyway, so way wouldn't the 3d drivers also run slower.
I decided not to vote, I think speed is a non issue as long as the drivers work on the HTC original rom, and are stable. You will always get rom's that perform faster, that's what cooks do round here.
I also don't think you would get a big jump in performance writing for just one rom, the hardware is the same in all the HTC Kaiser's handsets. Software can only make small difference to the performance of hardware if the drivers are written correctly.
personally i would love the drivers in a rom like dutty's diamond v1, but i think building them into a standard(ish) htc rom is best for the comunity; it sticks it to htc best as it shows u guys can do what they couldn't(or wouldn't), and makes flashing a rom feel safer to noobs.
and anyway we all know within hours of a rom with the drivers being released there will be dozens of cooked versions for all tastes with the drivers included too.
All,
I know there are a bunch of folks out there with Tattoo and Hero 2.1 dumps cooking up some great new things. I was wondering, though - does any of this, especially Hero 2.1, offer hope to get BT working on G1s or will we face the same problems we did with the previous versions?
Thanks,
Vj99
firstly, this should really be in the QnA section
it is possible that bluetooth will be working to some extent now that the heros kernel source has been made open source
but we will probably need to wait for HTC to make the source available for 2.1
so probably not til its officially released unless there is some jiggery-pokery that can be done to make it work
I never could understand people's need to install proprietary UI's on their phones. And that is the only reason for possibly trying to install one of those incompatible builds.
Just stick with a build designed for DREAM and your bluetooth (as well as everything else) will work perfectly. No reason to beat your head against the wall when there is nothing to gain from it.
Always welcome people weighing in, but that said I have to say that any value of the replies is tempered by unnecessary comments about one's opinion that this should be elsewhere or wondering why someone would want something.
In short, I could phrase the same question 10 other ways and make it a development question. I also find other capabilities in these other firmwares that I value, so it is much more than a UI update.
What I miss at this forum, is a ROM with a honest, complete list of known bugs/non-working stuff.
Would like to see some quality-control, and know what I install - before I do.
Everybody is cooking ROM's (and that's nice) but there's no way to know how they will work before trying.
-its impossible to read thru >200 posts and figure out which of those are about the current version.
-recent posts are sometimes about earlier versions too...
Please: I hope some of you that des this nice job will focus on information about quality, and keep a "buglist" for each version..
AlCapone said:
What I miss at this forum, is a ROM with a honest, complete list of known bugs/non-working stuff.
Would like to see some quality-control, and know what I install - before I do.
Everybody is cooking ROM's (and that's nice) but there's no way to know how they will work before trying.
-its impossible to read thru >200 posts and figure out which of those are about the current version.
-recent posts are sometimes about earlier versions too...
Please: I hope some of you that des this nice job will focus on information about quality, and keep a "buglist" for each version..
Click to expand...
Click to collapse
I agree 100% Buglists are a must. Roms shouldn't be released with alot of bugs unless stated by the op.
husker91 said:
I agree 100% Buglists are a must. Roms shouldn't be released with alot of bugs unless stated by the op.
Click to expand...
Click to collapse
I think the point you're missing is that the bugs only become apparent after others flash the ROMs and do some testing.....
cr1960 said:
apparent after others flash the ROMs and do some testing.....
Click to expand...
Click to collapse
nope - the author/or a helper is in the ultimate position to read the feedback, verify, and make a list in the first article containing these bugs.
i did not say that the cook should know about every bug before releasing.
maintain a list, and verify it against next version.
-the only way to have some quality control...
I agree with the sentiment - for those of us who only flash their phones maybe once a month, it would be nice to know a ROM is ultra stable and all known bugs / oddities have been sorted. (or if not, then a comprehensive list of things that are broken, with any workarounds etc) Reading through thousands of posts takes hours and not everybody has the time or inclination for that.
For instance both WM and Manila (and others) are under very active development, there are always new versions coming out. While it would be unreasonable to expect the beta WM builds (23xxx, 28xxx) to be 100% stable, it would be nice for a cook or two to say "right, this combination of components is stable, I'm going to stick with these for a while" instead of always following the very latest cutting edge "LOOK, SHINY TOYS!" at the risk of stability.
As for stability I am currently on JoshKoss's latest (1.7) and have yet to experience a single error, crash or hang. And Josh's seem to be the fastest ROMs, definitely of the ones I have experienced anyway. There are a few minor inconsistencies but these are in no way critical. If you want stable I would not even consider Manila 2.5 or any of the "start menu at the bottom" ROMs.
Have you tried AthineOS ROMS? Very fast, very stable. The current Leo 2.02 based ROM is the fastest Sense 2.5 ROM I've tried (and I've tried them all) and stable enough for hassle-free day to day use.
Guyz As far as my experience goes no cook likes to hide the bug list, rather they work to bring more in the light. Users like us are expected to give our submissions. Thats how it works. Things like quality control is not what we have seen here since its not GM factory but a place to share & experiment & success & failure is part of that place.
AlCapone said:
nope - the author/or a helper is in the ultimate position to read the feedback, verify, and make a list in the first article containing these bugs.
i did not say that the cook should know about every bug before releasing.
maintain a list, and verify it against next version.
-the only way to have some quality control...
Click to expand...
Click to collapse
I completely disagree. At the rate new builds are released, and with so many new tweaks and items going into ROMs, I think it would take forever for the chef and a select few beta testers to try and figure out all or most bugs in a ROM. I use Arrups ROMs, and he discloses everything that he can, but ultimately its not the chefs responsibility to create a "perfect" rom for Al Capone is it? Everyone uses different applications which can affect the stability of a ROM completely-for example Opera beta 10. I think its much more efficient to have them release the ROMs and let lots of people try and break them, then come back and fix it. And when bugs arise the are put on a "bug list" to be fixed.
We would never see new ROM releases for months if we waited for chefs to perfect stuff. So the people who just flash and leach ROMs cant help out a little?
Since you are so anxious about having a perfect ROM, why dont you have a go at it? Or is *****ing easier?
MadBeef said:
As for stability I am currently on JoshKoss's latest (1.7) and have yet to experience a single error, crash or hang. And Josh's seem to be the fastest ROMs, definitely of the ones I have experienced anyway. There are a few minor inconsistencies but these are in no way critical. If you want stable I would not even consider Manila 2.5 or any of the "start menu at the bottom" ROMs.
Click to expand...
Click to collapse
X2, This is a very stable ROM. I have been running it close to 2 weeks with no real issues & haven't had to soft reset because of a glitch or hang up.
I have to chime in here and agree with the sentiment of this thread. The application of it is much more difficult that it seems. I have been down this road before, trying to get the chefs to post a comprehensive bug list for their ROMs and while they are willing to do it, it is VERY difficult to tell what is a real bug and what is OE (operator error), confusion caused by loading some application, etc that really isn't a bug or a real bug.
For example, I have been running Sergio76's EVO 3 ROM for sometime now, and have absolutely nothing bad to say about it. Stable as hell, fast, good memory, good battery etc. But some of the other users of the same ROM find 'bugs' mostly caused by putting different shells on, or trying to icon sets.
So, my point is BRAVO! this needs to be done, but let's have a good discussion of how to categorize what is a bug, what is an incompatibility, etc. Because, if we simply list all these things as bugs then we run the risk of scaring folks off of flashing a potentially GREAT ROM all because one or two guys muck it up by hacking the registry and it gets put on a bug list.
I would also like to see a 'standard' way all the chefs list bugs, etc.
Russ
iceman4357 said:
why dont you have a go at it? Or is *****ing easier?
Click to expand...
Click to collapse
bit harsh tbh
MadBeef said:
bit harsh tbh
Click to expand...
Click to collapse
I was actually holding back a lot. Unfortunately 90% of people on here dont contribute anything and just expect stuff to happen perfectly. If its so easy, then instead of creating an entire thread to talk about problems, why not make a "perfect" Rom and contribute.
iceman4357 said:
Since you are so anxious about having a perfect ROM, why dont you have a go at it? Or is *****ing easier?
Click to expand...
Click to collapse
your own *****ing certainly does not help.
read my lips:
-I do NOT ask for a "perfect" ROM
-I just ask for the cook/helper to browse thru the reply-posts, and add known bugs they can confirm, to the first post - the one that contains the ROM
-So any ROM can have a list of known errors, (the the author confirms)
AlCapone said:
your own *****ing certainly does not help.
read my lips:
-I do NOT ask for a "perfect" ROM
-I just ask for the cook/helper to browse thru the reply-posts, and add known bugs they can confirm, to the first post - the one that contains the ROM
-So any ROM can have a list of known errors, (the the author confirms)
Click to expand...
Click to collapse
So the chef should worry about reading the 200 posts that you were worried about reading instead of working on ROMs? I am sure that chef mailboxes are full of people reporting bugs on a daily basis.
There are people other than the chefs that have a good deal of experience that help within the thread posts, that free up the chef to continue experimenting and cooking ROMs.
A lot of "common" bugs are specific to builds, such as the landscape issues vs touchflow(sense), or GPS lag which take a lot of time and programming to figure out. These are commonly known across ROMs and builds.
A lot of smaller bugs are from individual customization errors like with S2U2, Opera Beta, lack of knowledge, or custom tweaking.
Chefs, in my opinion, are here to provide a decent platform ROM for us to costimize individually; not to help each individual person with each custom problem they have.
x2
Montea said:
X2, This is a very stable ROM. I have been running it close to 2 weeks with no real issues & haven't had to soft reset because of a glitch or hang up.
Click to expand...
Click to collapse
can u link me up with the x2 rom u speak about?thanks
oyebee said:
can u link me up with the x2 rom u speak about?thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=572938
We were on about JoshKoss's ROMs.
I've said this for years, something like bugzilla would be good. Not that I have ever used it but something with a bit of structure you know? Flag bugs by component (ie. Manila footprints tab, lock screen, or whatever) then by ROM so the system will know already if it is ROM specific or not. But it still relies on people adding good data, as the saying goes, "Garbage In Garbage Out". An automated config dump tool would be a good step towards that. (an end-to-end "report bug" app would be awesome) After all I don't know what point release of Manila I'm running (1921? 1922??) because I don't really care unless it breaks, or a newer version has more shiny.
Anyway I said this a while ago and we are still "*****ing" about ROMs at a fairly disorganised level, and yet the cooks continue to work their magic, so it can't be all that bad
From another guy who comes on here with not very much to offer yet continues to leech a new ROM once a month or so
Stop the Madness...
Oh Geez....
Yes, I am one of the lurkers here at XDA, having been flashing my phones for years and not really contributing much to the community.
I have made a New Year's resolution to change that, so I am posting more now.
But look at some of the most popular ROMS....
Within hours of a Chef releasing a new version, there are hundreds of posts about it.
From what I gather, 95% if not more of these guys/gals cook up these ROMs in their spare time. They do it because they like to do it. I don't think anyone here is getting rich cooking up a ROM for my TP2. They all have lives and when there can be 40+ pages of posts within a couple days after they release a new version, I don't expect them to read every single one. Especially where a vast majority are people asking how to flash the ROM, how to change the theme or other posts that a simple search would provide the answer.
Most Chefs do post what was fixed, what was improved and a lot of them post issues in their ROMS.
I have spent hours reading page after page trying to figure out an answer to a issue I have had...knowing I was probably not the only one having it.
Do some Chef's not post as much info as I would like? Yes.
Am I going to berate those Chefs for not doing so? No.
Some of the responsibility has to be on the users. Period.
For example, I was and am a fan of the Energy ROMs. But I SMS an insane amount and the newest Leo interface with the HTC messaging client sucked, period. Not to say NRGZ28's ROMs sucked, quite the contrary, they are great. But did those ROMs fill every need that I specifically had? No.
So, I did some research, and I found in a thread where Agent_47 suggested his ROM because he didn't even cook in the HTC SMS messaging client. So, I looked at his thread, flashed the ROM, and realized that I have had no issues with it and am very happy. Stable, works and I don't have to wait 7 minutes sometimes to send a text to someone!
We are all very lucky to have XDA. We are all very lucky to have the Chefs that spend their own time, and a lot of it, to cook up these excellent ROMs for us to flash.
Instead of complaining about the lack of 'bug lists'...perhaps you could create a tool or set something up to help the Chefs better manage those said lists?
That is the spirit that has and continues to make XDA great, if there is something you want, something that you see lacking, then create a tool to fill that void.
If you don't want to do that, then I suggest getting an iPhone, where you are locked into your OS and a slave to Apple and their constant updates and static interface. Cool device, granted, but I prefer the freedom of flashing, the excitement of trying new interfaces, experimenting with new features and lastly, the great folks here at XDA.
\.end rant
Spankmeister said:
I suggest getting an iPhone
Click to expand...
Click to collapse
Let's not get silly
I was wondering if dual booting would be possible on our phone? I've seen that the HD2 got winmo + android boot... But having some kind of Stable partition and a second "dev" one would be quite amazing...
Thanks!
I asked the same question, and my post was moved to Q and A. Most responses were that WinMo is not worthy of the hardware. WP7 didn't attract quite the same disdain.
I would really love to run WP7 on the captivate, and I think eventually someone will make it happen. I think WinMo would run amazingly smooth, but I doubt we'll ever find out.
The HD2 won't quite run android ROMs, you have to boot into WinMo, then restart in Android, but it is really easy to swap what "ROM" you are using. If the HD2 was capable of AT&T 3G, I would have one by now.
Sent from my SAMSUNG-SGH-I897 using XDA App
Yes please to WP7 on Captivate. If nothing else i want to be able to run it for a few days to see how I like that new software. And check out the Xbox Live integration
yes, i only have one phone but would like to learn to do some basic development and it would be nice to have a stable rom to switch back to on the fly. i've had problems using nandroid and titanium backup. if anyone knows of a way to change to or add a secondary boot loader so multiple os's can be launched that would be awesome.
minmo might be a bit impractical but multiple android installations would be cool sweet.
Ok.. well get a checklist started on what you would need:
A custom bootloader that would work with the Captivate.. And I'm sure people would want the choice to pick the OS upon bootup instead of having to go into the recovery screen and booting up from there.
It would also have to be compatible with working Android and Win7
Someone would then have to find the source code to Win7 - or at least the SDK for it and develop in whatever language its written in.
Then someone would have to code the drivers for the Captivate and Win7 mobile.
Pretty much.. it wouldn't be any type of "take n' bake" task and would be quite the project involving a ton of work.
I'm sure someone out there in the world will come up with it.. I mean someone took the time to port Android to the iPhone - so it "could" happen.. but most likely won't due to the huge amount of work it will take.
avgjoegeek said:
Ok.. well get a checklist started on what you would need:
A custom bootloader that would work with the Captivate.. And I'm sure people would want the choice to pick the OS upon bootup instead of having to go into the recovery screen and booting up from there.
It would also have to be compatible with working Android and Win7
Someone would then have to find the source code to Win7 - or at least the SDK for it and develop in whatever language its written in.
Then someone would have to code the drivers for the Captivate and Win7 mobile.
Pretty much.. it wouldn't be any type of "take n' bake" task and would be quite the project involving a ton of work.
I'm sure someone out there in the world will come up with it.. I mean someone took the time to port Android to the iPhone - so it "could" happen.. but most likely won't due to the huge amount of work it will take.
Click to expand...
Click to collapse
At least there's a Samsung Omnia 7. It has a 4" SAMOLED like ours. I hope it has more in common with us as well so it would make the process easier.
JayPhill89 said:
At least there's a Samsung Omnia 7. It has a 4" SAMOLED like ours. I hope it has more in common with us as well so it would make the process easier.
Click to expand...
Click to collapse
if winmo gets ported great, if not oh well, if you read the op it was not to get winmo but just used the hd2 as an example of dual boot on a phone. a boot loader is a starting point so can the topic go in that direction? i just dont want naysayers to get confused and tell us every reason we wont get or dont want winmo.
You cannot just take the source code for WP7. It is not open source. You can port android to things, but not the other way around.
nbs11 said:
You cannot just take the source code for WP7. It is not open source. You can port android to things, but not the other way around.
Click to expand...
Click to collapse
As Dani897 said, the thread is not about porting WP7 to our phone, but just having dual boot to be able to have (lets say) one stable rom and one dev rom on the same phone...
seriously want this to happen figure it out