As a long time Rogers 32A user, my experience with most "ported" roms has been rather shoddy. Namely, the issue of camera FCs on most Dream/32B ported roms (Cyanogenmod has been a long time pain for this one).
For those of you who are unfamiliar with the bug, it essentially causes the camera to load properly about 3/5 times. Factors such as unplugging the phone or extended use cause the camera to open to a black screen before rebooting the phone. I've attempted to isolate the problem using logcat, but most of the time it doesn't really show anything useable.
The issue is mostly in all Donut roms that I have tried (Cyanogenmod, RA Donut, SuperD) as well as some of the new Ecalir ports (xRom). The only roms which don't seem to have this problem are any Sense based roms (Cursordroid, Hero ports), Sanpei's AOSP Eclair, and the stock Fender rom by Cursordroid. At first, I thought it was an issue with software (maybe something with Barcode Scanner/Google Goggles/etc.) but I found that this problem still exists on even fresh installs.
Now, this has led me to start thinking about what factors could possibly lead to this outcome. I was wondering, is it possible that there is some part of the rom that is still specific to Dream boards that causes the camera FC? Is there maybe something that we could be doing different in our ports to maybe fix these issues?
It seems that roms that were either made specifically for 32A devices (Fender) or those that use HTC's camera (Sense roms) are the only ones that seem to be immune to this behavior (at least for me and probably another dozen users or so). If some of the dev's could weigh in on this, maybe we could finally stamp out this bug.
have we looked at the difference between the kernels from the htc dev site? i'll take a look now and tell you what differences i spot
nevermind it's not as simple as the hero one... doesn't come with a premade config
Related
Hey... I'm a little confused regarding which ROM to pick for my 32A magic.
I really like the new officialli feautures (Sense and look--- Home screen, weather animations etc etc) on the HTC legend and Desire.
That's why i wan't to pick a rom which look like the "feel" of Legend / desire.
But what roms is like that?
What's important is:
- Stable
- Fast
What can you recommend? Unfortunately there are very little screens of the different version / comparisons... Thats why i'm asking here
Recommend: Read this before starting a thread, Most Question Asked are Answered
Q- Which ROM is best for me/ Which ROM is the best for 32A/B?
A- Take some time on the forums, look at the ROMs available for your device and individually assess what works for you by reading the various issues affecting them and make a decision. If that still doesn't work out for you, hey, that's what makes XDA great, try a different one and so on, till you find one that YOU'RE happy with. It's very subjective since what my needs are could be totally different from what yours are.
Yes but instead of testing all the roms... Then i know that many doesn't meet my requirements..
"I really like the new officially feautures (Sense and look--- Home screen, weather animations etc etc) on the HTC legend and Desire." Therefore i will like a rom based on that..
And without to many screens on the site :/ it could be very easy for someone just to recommend me a couple based on that..
You can start your search here, it even includes some ratings for stability/speed etc. Just make sure it's the correct type (32A/32B) and that your radio version is correct for that rom.
hxxp://forum.xda-developers.com/showthread.php?t=668090
(replace "hxxp" with "http")
I'd recommend Senpei's Legend rom. It's 2.1 with all the Sense UI goodness without too many crazy mods to unbalance it. It's for 32A w/ 6.35 radio.
For SenseUI on 32A magic, I suggest CursorSense. It's cupcake, but everything works, it's fast and perfectly stable. I still find alot of the eclair sense ROMs for new radio are still a bit unstable and some things like camera and BT may or may not work.
The problem about a topic like this is that we get one every week or so. And since it doesn't have anything to do with development of phone OS related stuff it would probably fit better in another category
Anyway
32A Cupcake with HTC sense go for CursorSense.
32A Eclair with HTC sense go for Senpei's Legend or CapySlide.
Alan090 had a decent port of the my touch slide rom here recently. Old radio.
Only thing not working decently appeared to be bluetooth. But this is a sense issue affecting android 2.1 ports to magics apparently.
I Think you would find that this rom had alot of what you want.
Personally im hoping he keeps updating it with the new cm kernel ports and the pershoot improvements. I Would like to move to it soon as my second rom.
Otherwise I agree with ronni.
The only problem I had with any new radio sense port was the fact that usb tether doesn't work properly for me.
-------------------------------------
Sent via the XDA Tapatalk App
I have tried really many different roms.
Currently i am stuck with "CyanogenMod 5.0.7t3 - Fastest Eclair 2.1(05/11/2010) OC/UV (576Mhz)" (http://forum.xda-developers.com/showthread.php?t=673394) which really is very fast and stable.
twigster said:
Alan090 had a decent port of the my touch slide rom here recently. Old radio.
Only thing not working decently appeared to be bluetooth. But this is a sense issue affecting android 2.1 ports to magics apparently.
I Think you would find that this rom had alot of what you want.
Personally im hoping he keeps updating it with the new cm kernel ports and the pershoot improvements. I Would like to move to it soon as my second rom.
Otherwise I agree with ronni.
The only problem I had with any new radio sense port was the fact that usb tether doesn't work properly for me.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
and capyslide for new radio
twigster said:
Alan090 had a decent port of the my touch slide rom here recently. Old radio.
Only thing not working decently appeared to be bluetooth. But this is a sense issue affecting android 2.1 ports to magics apparently.
I Think you would find that this rom had alot of what you want.
Personally im hoping he keeps updating it with the new cm kernel ports and the pershoot improvements. I Would like to move to it soon as my second rom.
Otherwise I agree with ronni.
The only problem I had with any new radio sense port was the fact that usb tether doesn't work properly for me.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
just cus u asked so nicely I will grant your request and add pershoots kernel
was waiting for an update to the rom from chiefz but he seems to have been on cyanogenmod 5 or something I know thats what I am using
also this is either suited for the general section - or like above - try out a bunch
see what works for you
Thank you very much... I will look into the different Roms listed here...
But one major thingh missing.. Is screenshots of the rom's. Ex just a screendump of the homescreen and menu screen could be VERY usefull...
Man, I'm so frustrated.
On other forums some people have mistakenly thought I'm against flashing custom ROMs. I'm not. I'd flash a custom ROM in a heartbeat. In fact, the reason I hang out here is I'm watching for "That ROM". I'm just not comfortable with the state of things on the Captivate. Here's the deal... it seems every single ROM is a compromise. I'm not talking about differences in themes, or what apps are included, etc... I'm talking basic functionality. Sometimes it's little things, sometimes it's big things... but always, you need to give stuff up. And I'll get the response, "yeah well stock is buggy too, so what's your point?". You know... sometimes the little things count. The details add to the experience. Maybe we want all the little things to actually work. Maybe you don't care about bluetooth, but I do. Etc.
Bluetooth. Haptic feedback. Battery life. Cell reception. GPS. Stability. Performance. Voice quality/Audience support. Pick the 3 you don't care about and are willing to give up.
Frustrating.
And a lot of it seems to come down to these "modem" files. Dozens floating about... everyone has their favorite like they have a favorite color. And they themselves come with compromises... use one, and A B and C work but X Y and Z don't. Use another, and it's the other way around... or maybe there's D E and F now. What works for one person doesn't work for another... and yet these are the same model phones. Oh, but wait... now it's passe to say "every phone is different". Like they are? They're the same hardware. But now we just accept for some reason that every Captivate is some random assembly of different chips and so using a ROM is an assumed matter of modem-roulette and deciding what features you want and what ones you're willing to sacrifice.
Why is this "ok"?
It's important to mention at this point that this is absolutely nothing against the hard-working developers here. I don't doubt for a moment that they are doing their absolute best with what they have available to them. It's not that, it's the culture... the community... the mindset. Are we being hypocrites? I mean, if we're just accepting now that every Captivate is unique hardware and no one ROM/modem will work ideal on all of them, why do we hold Samsung to a higher-standard like they themselves could ever produce an official and universal 2.2 firmware for the Captivate where everything actually works for everyone?
Something's not right here. I don't doubt that people get different results with different files... but these are different environments, and the testing not done consistently or scientifically. I don't think it's appropriate to act like the differences come from varying hardware when it's far more-likely that it's differences in other more-random things. Some people are in a primarily 1900 MHz area, some primarily in an 850MHz area. GPS is also environment-specific and someone with a modem that offers below-average GPS performance might report that the GPS is "amazing" simply because they're in an ideal spot. The hardware is the least likely aspect to vary. Surely there must be a solution... a better answer... a potential for a modem that actually works amazing for everyone. Where all bands are supported, GPS works amazing, Audience chip is supported, etc etc.
I just felt the need to vent. I'm not sure what the solution here is... I just feel we've gotten to casual just "accepting" a situation as something it's not, and shouldn't be. One shouldn't have to play modem-lotto just to get basic decent performance from their ROM, or decide what basic features they're willing to sacrifice. I know this is a huge discouragement for me, and why I'm still on stock. I want to flash so badly... but every ROM thread I read through I eventually hit at least one (if not several) deal-breakers, and the casual acceptance of them is just frustrating.
Anyone feel the same way? Thoughts?
I think your over analyizing.....im a flash junkie and I've flashed everything on the forums....I don't use my phone for business so almost every rom I use has everything I need functional...haptic feedback is not a reason for me not to use a rom but camera is.....along with flashing roms I mix matched different kernels and modems.....its all preference.....with the modem situation I just flash one and test it out until I have an issue then move onto the next...I thought jk4 was the best for me until I decided to try jk3. I've noticed I get reception in areas where I didn't with jk4....so ill test this one out for awhile....you can't sit and read until u read that u found the best......u just have to test it out for yourself...it sucks but that's what u get. I feel things wont get better for us until we get our official froyo release by att. Well have our noise cancellation chip working as well as a modem built for att usa. I had better cell service with captivate roms n modems then I do with i9000 ones but the i9000 roms are leagues ahead of any captivate ones
Sent from my SAMSUNG-SGH-I897 using XDA App
Did you try Serendipity? It seems to do quite well on every item in your list.
I have not flashed for mostly the same reasons as you. It seems that every combination has different things that work and things that do not work. I want every function of my phone to work properly. That includes hardware noise cancellation and proper bluetooth support, which seem to be a major issue on i9000 ROMs/kernels/modems. My biggest issue with Captivate ROMs/kernels/modems is the apparent lack of support for bluetooth voice dialing. Now it is a fair argument that bluetooth voice dialing does not work on the AT&T 2.1 ROM, but it is not a supported feature of 2.1. It is a supported features of 2.2, so why shouldn't I (we) expect it to work? If a feature that is supposed to work in 2.2 does not work, that doesn't give me the best feeling about flashing the ROM.
I came over from the Windows Mobile side and I flashed custom ROMs on my Fuze without thinking twice, but there were never core or standard features of the phone or OS missing in the ROMs I flashed. I had bluetooth + voice dialing, good battery life, good cell reception, good working GPS, extremely good stability, great performance (for the hardware), and good voice quality with working noise cancellation in all the ROMs I ran.
I think that overall the devs here are doing a good job, and I think things will improve after the release of 2.2 sources for the captivate, but it seems that right now, there is a compromise involved in any of the custom ROMs.
I can accept the fact that the current ROMs don't meet my expectations, but when people say, "just start flashing" to people like myself who have higher expectations, it gets a little old. The attitude that only people willing to accept these compromises should be reading/contributing to the xda-developers forum is also annoying. I think it is great that there are people working on custom ROMs and there are people willing to run them with the compromises they have to make, but that does not mean that everyone should just be willing to make those compromises and if they are not willing they should not post.
I have made very few posts in the Captivate forum, I guess it could be said that I have been lurking and reading up on each new custom ROM as it comes out, waiting for one that seems to meet my expectations. I have not been vocal, or complained about the fact that we need to make compromises. But others that ask questions about whether certain things work, seem to get flamed and told to just accept the way things currently are, or they are completely ignored. If the devs don't want to answer questions such as, "does bluetooth voice dialing work," or "how is bluetooth voice quality in this ROM," then they should put this type of information directly in the first couple of posts. The newest Cognition ROM thread has this type of information and I greatly appreciate that DG included it. For most ROMs you can't find out if certain items work properly without reading the first 10-20 pages of posts.
Maybe the main issue for people like me (with higher expectations from my phone) is that good information about what works and what does not work often does not float to the top of the ROM dev threads. I started using xdandroid on my Fuze as my first introduction to Android and each phone that it ran on had a thread and on the first page was a listing of each major functional piece (sound, camera, bluetooth, etc) and whether or not it was working yet. Each developer can do as they choose, but if the status of functional items and known bugs was listed in the first page, it would save on questions and some of the less than helpful responses that the questions cause.
People also have to remember that only a leaked/unfinished Captivate 2.2 ROM has been made available as a base for some ROMs so there's no other choice for a complete Froyo ROM without resorting to i9000 ROMs. Expecting things to work from a unfinished leak is a bit different from having high standards.
GPS is also broken for some people whether they're on a stock ROM or not to begin with, devs can't magically make it work for everyone.
Cell reception is not 100% determined by a ROM, if I flash the "most amazing bestestst rom ever" and live in a remote forest with lead leaves, reception might just suck a little because it mainly depends on location.
No phone is the same believe it or not, maybe unless it's an iPhone. If you want something that works as it should perfectly, you probably shouldn't be flashing ROMs, because they are essentially in infinite beta until a dev doesn't want to work on it anymore. Either stick to the stock ROM, get an Aria or some other unlocked phone, or even an iPhone since that's probably most stable thing out there right now.
The ROM threads grow dozens of pages every hour, and posts will always get overlooked whether they are important or not. It still amazes me that people get confused when they start seeing an H instead of 3G. This is a development community and has several thousands and thousands of users at any given time. It is busy.
tysj said:
People also have to remember that only a leaked/unfinished Captivate 2.2 ROM has been made available as a base for some ROMs so there's no other choice for a complete Froyo ROM without resorting to i9000 ROMs. Expecting things to work from a unfinished leak is a bit different from having high standards.
GPS is also broken for some people whether they're on a stock ROM or not to begin with, devs can't magically make it work for everyone.
Cell reception is not 100% determined by a ROM, if I flash the "most amazing bestestst rom ever" and live in a remote forest with lead leaves, reception might just suck a little because it mainly depends on location.
No phone is the same believe it or not, maybe unless it's an iPhone. If you want something that works as it should perfectly, you probably shouldn't be flashing ROMs, because they are essentially in infinite beta until a dev doesn't want to work on it anymore. Either stick to the stock ROM, get an Aria or some other unlocked phone, or even an iPhone since that's probably most stable thing out there right now.
The ROM threads grow dozens of pages every hour, and posts will always get overlooked whether they are important or not. It still amazes me that people get confused when they start seeing an H instead of 3G. This is a development community and has several thousands and thousands of users at any given time. It is busy.
Click to expand...
Click to collapse
For the American SGS phones, I was not trying to suggest that the developers can "fix" the GPS (though it is worth noting that Da_G has made some good progress http://forum.xda-developers.com/showthread.php?t=881941).
I don't completely disagree with many of your points, which is why I am still running the stock ROM. If I had two phones, I would be willing to beta test unfinished software and ROMs, but since I only have 1 phone that I expect to work (or more accurately, my company who pays for it expects it to work) I have not flashed any of the current firmwares that are available.
I think cell reception has a lot more to do with the Radio/Modem than the ROM. If you have a working modem and that modem functions with the ROM, then it should give you the same reception. I think one of the main points the OP was making was that there is no apparent consistency, and some modems work with some ROMs, and not with others. It does not even seem to be accurate to say that any i9000 modem will work with any i9000 ROM, as some combinations cause poor voice quality or other issues.
I do disagree with your statement that "no phone is the same." Any Captivate in the same batch/build should have identical hardware and should function identically (assuming Samsung has good quality controls in place). There is the potential for slight differences between batches, but I can't believe that any of those differences is significant enough to cause software running on the phones to behave differently. If that is the case, there is no way that Samsung can release a working Froyo build, or even a working Eclair build that would function as intended on every captivate. If Samsung was unable to produce identical products consistently, they would be out of business because none of their products would function as intended consistently.
As far as "expecting things to work from a unfinished leak is a bit different from having high standards," I don't think it is unreasonable for better visibility to what works and what does not work in the first page of a ROM thread. I am not saying that I expect everything to work 100% on all ROMs, especially without 2.2 sources, and I am not saying I expect the devs to be able to test every possible things, but I don't think it is unreasonable to hope that as bugs or problems or ROM/Kernel/Modem combinations that do not work are discovered, that information could be made more accessible without reading 100 pages of a ROM thread.
Hopefully most of this is just growing pains as Android is evolving and as we wait for 2.2 sources for the Captivate. For Windows Mobile, much of the OS and functionality of the OS was pretty much set between ROMs. The biggest differences were in the frameworks (Sense vs. Non-Sense, etc) and theming of the ROMs. That is why I have said in the past that if we could get a solid, working AOSP ROM with all drivers, etc for the SGS, it would give a good base for additional ROM development.
It seems like no matter how many roms I try, when I flash a Sense rom my phone seems to work best.
GPS locks on fast, not a lot of freezes, just all around a good experience.
So are HTC phones meant to go hand in hand with Sense?
mikejet said:
It seems like no matter how many roms I try, when I flash a Sense rom my phone seems to work best.
GPS locks on fast, not a lot of freezes, just all around a good experience.
So are HTC phones meant to go hand in hand with Sense?
Click to expand...
Click to collapse
Sense OSs are de-tox'd versions of other OSs ports or built strictly from code.
Long and short of it, Sense OSs are from HTC directly. Yes they will work "better".
Personally i've not had any of the symptoms you are having with CM252
neidlinger said:
Sense OSs are de-tox'd versions of other OSs ports or built strictly from code.
Long and short of it, Sense OSs are from HTC directly. Yes they will work "better".
Personally i've not had any of the symptoms you are having with CM252
Click to expand...
Click to collapse
same here, been running CM252 without any issues since it was released. IMO Sense roms run a little "slow" for me (damn bloatware )
ive run both cm7 and miui and neither one have given me any issues. sure, you may have an odd happening once in a while, but no more than the stock rom. in fact, after running the miui build im on now, i wouldnt even consider going back to stock
Most likely Sense builds are just more polished and bug-free than CM and/or MIUI, even when ported from another phone. Since this phone is essentially the same as other MSM8x55 siblings (Desire HD, Desire S, etc), not a lot of things can go wrong in porting, given a proper kernel (which is released and available for ROM developers), excluding the porting from phones with different resolution (Sensation).
cm7 and miui - agreed, no problems here either.
... and for Sense ROMs have started using ROM Cleaner which is excellent IMHO
Quick question, I don't know if anyone here would be able to answer, or if this is a dumb question, but with official ICS on our phone, what is breaking the camcorder on many of the ICS roms? Is it a kernal issue, or something more in depth?
When "vanilla" AOSP (CM9) or AOKP ROMs are ported over, there are no drivers to make the hardware work with the ROMs. I think the drivers are hacked. So often some hardware does not work. Hacking drivers to make them work is a time consuming process. If/when HTC released the kernel source code, it may help (I'm not sure).
That's my non-developer understanding of the issue.
In the CM9 thread theres a link to "Camcorder.zip" that you can flash after installing Alpha 4 that enables your camcorder. It "sometimes" corrupts the video, but 8 times out of 10 it will work, and records in 720p and SD modes.
Not a perfect fix, but it's something. Probably works with AOKP too but haven't tried it yet.
Thanks for the feedback guys, it reminded me that HTC is pretty bad about releasing source... I've been using samsung products for so long that I had forgotten it was still an issue but unfortunately my infuse broke recently so I bought a one x from someone in the mp. Hopefully I'll get my infuse replaced and have a backup!
so essentially the kernal is still closed source, which is understandable now why there are still some hardware issues.
So, i know its a newer device, and if thats the reason, great! But i was wondering why there is such a lack of available Kernel options (especially for AOSP roms)? Even Sense Kernels are few and far between. I just was wondering if its something HTC has not released ( i know they havent released the source for US Kernel, but wouldnt the international one be VERY similar?) or done that they should be or if it was just that its new and these things take time?
It just seemed like every other phone that i had, even newer phones, had kernels being developed almost immediately which i am really not seeing for the one s.
Again, not *****ing, just curious. THANKS.