Database Users

Camera is terrible in low light, under all builds and kernels tested

First of all, I'd like to thank the XDA-Dev community. Without you, my poor Vogue would still be running WM6.1
I've been trying the Android builds for quite some time now, and while I'm in love with the buttery smooth UI, the wonderful responsiveness, and the general geeky goodness of having multiple OSes on a phone, there's still one issue that prevents me from fully embracing Android and flashing it to the NAND.
The camera.
Perhaps it would be better illustrated in picture form. Here are two pictures I took about five minutes ago of the desk beside my monitor. (I've resized them down, of course.) It's not dark here, but there's no light directly shining into the lens. Still plenty to take a decent snapshot, right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'll give you three guesses as to which photo was taken under Android. And the first two don't count.
I've tried virtually every kernel and build I've come across on this site, from 1.5 to 2.0.1, using various zImage dates and combinations of those and the builds, and have still had no luck whatsoever.
Help me, someone. Please point out the obvious solution that I'm overlooking, so that I can use Android as a daily OS.

There is no obvious solution. Recent kernels are better (they have automatic whitebalance) but there are still noise issues. If I had to guess it's probably setting the camera's sensitivity (ISO) incorrectly, or lacking some sort of noise filtering that Windows Mobile's camera driver has, but Martin or another kernel developer would know more.
No magic noise switch, sorry.

bri3d said:
There is no obvious solution. Recent kernels are better (they have automatic whitebalance) but there are still noise issues. If I had to guess it's probably setting the camera's sensitivity (ISO) incorrectly, or lacking some sort of noise filtering that Windows Mobile's camera driver has, but Martin or another kernel developer would know more.
No magic noise switch, sorry.
Click to expand...
Click to collapse
it is seriously noise that causes that?

Have no fear...we have some great devs here! Someone will crack the mystery of the grainy lens! LOL

jamezelle said:
it is seriously noise that causes that?
Click to expand...
Click to collapse
i'm not a camera expert but that 100% looks like a lighting issue! this camera stinks to begin with so i never use it anyways

It's been like this since day one with droid builds on the vogue. So far the only repsonse is " you're lucky it even works" I don't expect a fix anytime soon.

so dzo is the only one that has done work on the camera in the kernel so far (zimage or the .nbh is where the camera code is located). he has singlehandedly brought android to the vogue, and he has be the single most committed developer. I don't know what he is working on now, but if I gave you a list of all the latest updates, you would notice that they are all more important than the camera. and yes, importance is a matter of opinion, but basic features like bluetooth, the phone not crashing after calls, booting from the nand, etc etc, take priority for most.
if you have not followed this project from the beginning, or at least have not taken the time to read through the old forums to see where we came from (BGPS is an example - before gps we all used to be located somewhere in san franscisco driving on some highway out there), save your complaints. it is people who complain about sh** without contributing sh** that causes our good developers to say "fu** it, peace out" and then, guess what? who will make your camera better for you then?
we all know the camera isn't the best. but yeah, here's that response again, AT LEAST IT WORKS. there was a day when it didn't. and there are still things that don't. live with it; or roll up your sleeves, do some reading, and update it yourself. we'll all be waiting for your contribution. and when you give us something to test, instead of complaining how it isn't perfect yet, we'll say great job, thanks for contributing, and we'll help you figure out how to make it better instead of just saying "this sucks."

bri3d said:
There is no obvious solution. Recent kernels are better (they have automatic whitebalance) but there are still noise issues. If I had to guess it's probably setting the camera's sensitivity (ISO) incorrectly, or lacking some sort of noise filtering that Windows Mobile's camera driver has, but Martin or another kernel developer would know more.
No magic noise switch, sorry.
Click to expand...
Click to collapse
Unfortunately neither photo came with ISO numbers in the EXIF data. I'll try hunting down some custom camera apps on both OSes and see if I can replicate the Android results under Windows - that way I'll at least know exactly what's causing it.
Thanks for the suggestion, and thanks Reddog80p, I'm sure one of us can figure it out.
And thanks tatnai for showing me that even Canadians can be pompous, arrogant, and rude. One world, one love.

tatnai said:
so dzo is the only one that has done work on the camera in the kernel so far (zimage or the .nbh is where the camera code is located). he has singlehandedly brought android to the vogue, and he has be the single most committed developer. I don't know what he is working on now, but if I gave you a list of all the latest updates, you would notice that they are all more important than the camera. and yes, importance is a matter of opinion, but basic features like bluetooth, the phone not crashing after calls, booting from the nand, etc etc, take priority for most.
if you have not followed this project from the beginning, or at least have not taken the time to read through the old forums to see where we came from (BGPS is an example - before gps we all used to be located somewhere in san franscisco driving on some highway out there), save your complaints. it is people who complain about sh** without contributing sh** that causes our good developers to say "fu** it, peace out" and then, guess what? who will make your camera better for you then?
we all know the camera isn't the best. but yeah, here's that response again, AT LEAST IT WORKS. there was a day when it didn't. and there are still things that don't. live with it; or roll up your sleeves, do some reading, and update it yourself. we'll all be waiting for your contribution. and when you give us something to test, instead of complaining how it isn't perfect yet, we'll say great job, thanks for contributing, and we'll help you figure out how to make it better instead of just saying "this sucks."
Click to expand...
Click to collapse
+1
[ten character]

My vogue camera exibits the same behavior.
The noise in the android picture is static for me, and it would be easy to fix. I just need to take a picture with the lens blocked (a dark frame that contains just the noise) and substract the noise from the actual picture I want to take. This could probably be implemented on the software side.

tatnai said:
so dzo is the only one that has done work on the camera in the kernel so far (zimage or the .nbh is where the camera code is located). he has singlehandedly brought android to the vogue, and he has be the single most committed developer. I don't know what he is working on now, but if I gave you a list of all the latest updates, you would notice that they are all more important than the camera. and yes, importance is a matter of opinion, but basic features like bluetooth, the phone not crashing after calls, booting from the nand, etc etc, take priority for most.
if you have not followed this project from the beginning, or at least have not taken the time to read through the old forums to see where we came from (BGPS is an example - before gps we all used to be located somewhere in san franscisco driving on some highway out there), save your complaints. it is people who complain about sh** without contributing sh** that causes our good developers to say "fu** it, peace out" and then, guess what? who will make your camera better for you then?
we all know the camera isn't the best. but yeah, here's that response again, AT LEAST IT WORKS. there was a day when it didn't. and there are still things that don't. live with it; or roll up your sleeves, do some reading, and update it yourself. we'll all be waiting for your contribution. and when you give us something to test, instead of complaining how it isn't perfect yet, we'll say great job, thanks for contributing, and we'll help you figure out how to make it better instead of just saying "this sucks."
Click to expand...
Click to collapse
The OP was asking a question. Stop flaming noobs and pick on someone with your same amount of posts. It's because of responses like YOURS that drive noobs away. He deserves the benefit of the doubt, there was nothing rude about his question, he was not expressing any contempt for any developers, he never complained about Android, just asked for help with the camera. He did more than most noobs would, he posted pics, and expressed his attempts at finding the solution himself. People who flame noobs have little man's syndrome, they are bullies. Your answer is completely worthless and makes you look like a jackass.

petermg said:
The OP was asking a question. Stop flaming noobs and pick on someone with your same amount of posts. It's because of responses like YOURS that drive noobs away. He deserves the benefit of the doubt, there was nothing rude about his question, he was not expressing any contempt for any developers, he never complained about Android, just asked for help with the camera. He did more than most noobs would, he posted pics, and expressed his attempts at finding the solution himself. People who flame noobs have little man's syndrome, they are bullies. Your answer is completely worthless and makes you look like a jackass.
Click to expand...
Click to collapse
This shouldn't be a flame fest. Tatnai didn't mean to "flame" anyone I don't think. Nor did he mean to come across as pompous, but he was just preemptively dealing with issues that his forum has seen in the past.
Anyone hurt or insulted, on either side... this is not a big deal. Let's just all settle.
I don't remember this camera getting good results even in WinMo...

yea, my camera never worked passably in WinMo either

Anyone who has ran a NFSfans Win-Mo rom knows the camera is capable of producing pretty decent pictures. When it come to HTC's camera lenses we all know they can improve dramatically.

The camera in android is controlled by our open source libcameraservice.so and in kernel. Here is the code for libcameraservice http://github.com/dzo/VogueCamera

tatnai said:
so dzo is the only one that has done work on the camera in the kernel so far (zimage or the .nbh is where the camera code is located). he has singlehandedly brought android to the vogue, and he has be the single most committed developer. I don't know what he is working on now, but if I gave you a list of all the latest updates, you would notice that they are all more important than the camera. and yes, importance is a matter of opinion, but basic features like bluetooth, the phone not crashing after calls, booting from the nand, etc etc, take priority for most.
if you have not followed this project from the beginning, or at least have not taken the time to read through the old forums to see where we came from (BGPS is an example - before gps we all used to be located somewhere in san franscisco driving on some highway out there), save your complaints. it is people who complain about sh** without contributing sh** that causes our good developers to say "fu** it, peace out" and then, guess what? who will make your camera better for you then?
we all know the camera isn't the best. but yeah, here's that response again, AT LEAST IT WORKS. there was a day when it didn't. and there are still things that don't. live with it; or roll up your sleeves, do some reading, and update it yourself. we'll all be waiting for your contribution. and when you give us something to test, instead of complaining how it isn't perfect yet, we'll say great job, thanks for contributing, and we'll help you figure out how to make it better instead of just saying "this sucks."
Click to expand...
Click to collapse
I did a lot of development for modifications for multiple RTS games like Empire Earth and Civilization III & IV, so to an extent I understand your frustration and even agree with you.
But that was plain out of line and rude. There is a better way of going about giving someone info than that and you really need to work on internet rage dude. Not everyone is a developer and not everyone will have something to contribute. It's the people who test the programs, find the bugs, and then report them that help advance the development process. People saying things like this, hinder it.
Besides all that, I do have the same issues with my camera and only recently did I even manage to get the camera to work. I've been talking with a couple of developers I know here at my school (DeVry for the geekyness win) and we've started working on finding a solution. Hopefully I'll have something to show for it soon.

OP posted a critique of the current android camera, with a hint of sarcasm, and ended with a question that was neither constructive or helpful or focused on future development. The state of the camera in android is nothing new, we have all used it and seen it. Framing his observations about the camera the way he did,
I'll give you three guesses as to which photo was taken under Android. And the first two don't count.
Click to expand...
Click to collapse
and
Help me, someone. Please point out the obvious solution that I'm overlooking, so that I can use Android as a daily OS.
Click to expand...
Click to collapse
in a flippant manner, like it is a bug that needs fixing, is quite disrespectful of the hours of work that dzo put into building the camera driver FROM SCRATCH. A little reading of the forums about android would have brought this to light, and would have produced a post more along the lines of "hey dzo, I see the camera has not been updated in a while, I would love to help take it to the next level with my skills - who wants to pitch in?" rather than "this sucks, who knows a fix?"
We have had developers leave the project due to posts like the OP. Some might say, well that is just childish for people to get their feelings hurt by a simple post. Maybe it is, maybe it isn't. But post after post of thoughtless criticism by people who have not taken the time to see WHY there is an android on the vogue in the first place, wear on the people who pour countless hours of there time into this project. You'll note that the two posts who acknowledge value in my original post are also from people (jamezelle, TheKartus) who have been around to see this happen before.
I love noobs as much as the next guy (we are all noobs in one area or another), and that's why you see me troubleshooting for people in threads all the time. We always need more people giving feedback, but please, give it in a way that is respectful of the time and energy and love put into the project by its creators, and in a way that shows you've taken the time to know the background of the subject you are addressing.

well lets get on track and fix it. the code is open source so anyone can have a look and fix it.

Here is the photo the G1 dev took, using his reverse-engineered Eclair driver. It comes out with very low noise.
Does the G1 have hardware noise-reduction that we don't? Or is there something in their driver? It's been a while since I've written C so I'm still digesting what all the code actually does. I've asked the devs of the G1 driver if they have a guess... hopefully they are not too busy to provide insight.

Cyanogen 6.0. Is it way over rated?

Here is a question for everyone. It's not a trolling question, nor is it designed to provoke anger. As a faithfull user of cyanogen 6 since its inception (nightly updates, RC1, RC2, and Full) Lets boil this down.
Things that work:
1. Its fast as hell.
2. No sense (makes it fast as hell).
3. Highly customizable
4. ADW tweaks are nice.
5. Feel free to add something else in here.
6. Nice screen rotation for car mounting.
7. Oh ya....its fast as hell and, as has been posted in here a million times, "...is buttery smooth."
Things that still don't work at all or work well:
1. HDMI
2. 4G
3. Radio
4. MMS with picture or voice (tried it again yesterday)
5. Voicemail issues (we all know what they are)
So......essentially....except for some modest, user appreciable "non-sense" speed boosts....this ROM actually removes some pretty darn important features.
Explain the logic of this to me?
Cyanogen has done excellent work. I am not trying to squelch that, but he (and his team) seem to be unable to resolve issues EVO users should and do find important.
With the new sense roms out there and their subsequent kernal releases, they perform, user appreciably, nearly the same as this rom with all the above MAJOR FUNCTIONS working. (Linpak, FPS2d, and Quadrant scores for which I can reproduce screen shots)
So, you get a fast rom with few of exceptional functions / features this phone is capable of.
Do you think maybe....the rom is a crutch for the phone.
Just one man's humble opinion. Maybe further versions with the important features useable will kick butt. For now......Come on. What is the obsession?
Would someone please explain my confusion on this seemingly obvious question.
So....Ill keep it as a nandroid backup. For what? I don't know.
-JZ

Pro: Stagefright AAC decoding patch implemented in CM6
Con: Bluetooth prevents phone from sleeping

I agree.. seems ridiculous to me. I wouldn't touch it with a ten foot pole.

I don't really want to get nit picky, but I agree with your points, and it's personally not the rom for me. At least not in its current state.

Didn't you post this in the CM6 thread?

all the features in cm6 currently PWN 4g and hdmi. for those that other are either fooling theirselves or havent really actually played with the rom
-i mean really, hdmi is nice, but you cant even use it to its full extent now...why waste the time? a saying that comes to mind "if you gonna do something, do it big" or "why halfass when you'll just have to come back and finish it up later"
sorry i just dont think a HALF working hdmi in sense or even stock roms for that matter are worth bragging about.
-4g is NICE, however its only ONE phone that has this option as of right now (excluding the samsung epic that just launched today). It makes NO sense at all to focus on a feature that is only exclusive to ONE phone...not to mention the code for 4g is intricately woven into Sense, so it takes some time to remove and code for it
-Radio? Seriously? It just seems like yer being a hater here.... I do realize having the FM radio is nice and all....but even in the stock roms you have to have gay ass headphones.
With all the pandora radio, stitcher radio and other podcast..... is it REALLY that big of a deal? i think not especially since i dont have to be on a leash with headphones and can play through my speaker
-NO other rom has a higher bitpool for bluetooth aka if you use a2dp to stream to your car's stereo...unless your using cm6.... your stream is gonna sound like ****!!! This is a BIGGGG feature
and whas the issue with MMS? the 160 char limit thing? I dont seem to suffer from that problem....maybe its a hit or miss?
as far as the voicemail...i dont use sprint's voicemail on this phone....i link it to my gvoice....but i can definitely understand the frustration not being able to get to your vmail.
i guess people like cm6 because it pwns and own all while not being a bloatware king and slowing **** down

ya....i wasn't sure where the "most appropriate" place to post it was. You know how folks won't answer your question/quandry, but rather say, "this isn't the appropriate place for this." So....pre-empting that I posted it in both places in case one gets deleted.

They do great work for other phones, but I think the EVO 4G was just to complex.

it pwns? with modest appreciable speed increases (seriously.....post some objective data for me....not subjective)?
4g, hdmi, (ill give you the radio), mms (not sending messages with photos or sound or both attached) are not little things. Also....if you have a decent HDMI set it will recognize the settings and accomodate....so come on. OBJECTIVE not SUBJECTIVE.
The sense roms have comprable linpak, quadrant, and BETTER fps2d scores.
Im not hating....just posting OBJECTIVE findings.

rubixmaster said:
They do great work for other phones, but I think the EVO 4G was just to complex.
Click to expand...
Click to collapse
My thoughts exactly.

Nope.
HDMI? Why would I want that in a phone?
4G? I'm not in a 4g area.
Radio? Haha.. why? It never worked right for me anyway and my Zune gets better reception.
MMS - I sent my wife a picture just yesterday. No issues there.
VM - I use GV and always have. No issues.

jasonziter said:
it pwns? with modest speed increases (seriously.....post some objective data for me....not subjective)?
Click to expand...
Click to collapse
Bro, I'm not going to do research for you. If you haven't already, flash CM6 final on your phone. If it doesn't fly compared to a Sense ROM, you are doing something wrong or you need to return your phone.

goodelyfe said:
and whas the issue with MMS? the 160 char limit thing? I dont seem to suffer from that problem....maybe its a hit or miss?
Click to expand...
Click to collapse
That is SMS (aka texting) and the 160 character limit is the CDMA technology limit, has nothing to do with a ROM. MMS (aka picture/multimedia mail) is what he is referring to. But I'm not sure exactly what problems he's referring to, because I though MMS worked fine on my phone when I had CM on it.
You feel it is faster by far then other roms, that is your opinion, hard factual numbers do not necessarily agree with you. I didn't want to get into the nit picky, as I stated before, because honestly I respect CM for doing things I could never dream of doing. But your post reads as if a one sided defensive retort. Prove him wrong in his stance, saying it feels faster does not do so, because that is one of it's few claims to fame.
And yes, I've run multiple nightlies, and ran RC1, I did not care for any of them enough to keep me around long. I am waiting however for 6.1 and look forward to trying it out.

Thats it......too complex. I can't think of anything else. The argument that
1 there really isnt that much 4g out there
2 HDMI really doesnt work
3 who really sends pics / voice MMS anyhow.
4 are you really using your FM radio (no.....im not but thats not the point in the whole picture)
5 voicemail issues - just move to SOMTHING ELSE (gvoice etc)
These are poor agrguments. Post objective findings on why Cyanogen 6.0 for the EVO is such a better rom. Give me some FreakEvo vs Cyanogen quadrant photos (what ever kernal you like to use). Set cpu settings equal and EVO switch settings equal.
Post some photos. Show me why CM6 is better. Don't show me emotionally.....show me with objective data. Then.....ill understand the "non-sense" and stop my silly confusion. Thats my whole point with my silly quandry. I really DO like CM6...I just want the features my phone is capable of (which.....most of them I do use...) to work.

jasonziter said:
Thats it......too complex. I can't think of anything else. The argument that
1 there really isnt that much 4g out there
2 HDMI really doesnt work
3 who really sends pics / voice MMS anyhow.
4 are you really using your FM radio (no.....im not but thats not the point in the whole picture)
5 voicemail issues - just move to SOMTHING ELSE (gvoice etc)
These are poor agrguments. Post objective findings on why Cyanogen 6.0 for the EVO is such a better rom. Give me some FreakEvo vs Cyanogen quadrant photos (what ever kernal you like to use). Set cpu settings equal and EVO switch settings equal.
Post some photos. Show me why CM6 is better. Don't show me emotionally.....show me with objective data. Then.....ill understand the "non-sense" and stop my silly confusion. Thats my whole point with my silly quandry. I really DO like CM6...I just want the features my phone is capable of (which.....most of them I do use...) to work.
Click to expand...
Click to collapse
You're asking him to do the testing to back up his point, when you're the one with the challenge?
BUT
I might have just found something I'm interested in and maybe I'll do the testing you're asking for today during my afternoon at work.
Fresh installed FreakEvo and Fresh CM 6.0 running the gambit.

[email protected] Pao
@Jasonziter
lol dude!!! lol 'dont show me emotionally'
it seems you and maybe another are the ones who are getting upset/emotional
lol
you ask us our opinions, then you 'attack' us for them.....and your rebuttal is back it up with objective data....
dude its not that serious.
"you can lead a horse to the water well..... "

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I understand your curiosity about what makes it measurably better, but I don't undestand what makes you think anyone would be motivated to win you over..
I love CM6 and am very happy to be running it on my phone, it's smooth and reliable and I'm happy with it. I could give a **** if you like it or decide to start using it.
If you don't see the value, and if you prefere a sense based rom then use a sense based rom. If you want to know the difference then flash them both and run your objective tests and share the results with the community. It would be interesting to know but I don't forsee anyone providing you with this data in an attempt to convince you to become a CM6 user.
You want some objective data? CM is powered by unicorns.. does it get any better than that?

Zergburger that is a mighty quadrant score indeed. What were you OC'ed to in that?

nebenezer said:
You want some objective data? CM is powered by unicorns.. does it get any better than that?
Click to expand...
Click to collapse
^this^ lol

Is it just me?

Everything on EVO development is being bombarded with different ports that ultimately have a lot of bugs. What happened to the days of stable roms where EVERYTHING worked such as myn's warm? I know the developers are hard at work but can we just stick to working on one port so bugs can be worked out quicker? Idk just a food for thought when trying to look for a new rom that has everything working.

locoboi187 said:
Everything on EVO development is being bombarded with different ports that ultimately have a lot of bugs. What happened to the days of stable roms where EVERYTHING worked such as myn's warm? I know the developers are hard at work but can we just stick to working on one port so bugs can be worked out quicker? Idk just a food for thought when trying to look for a new rom that has everything working.
Click to expand...
Click to collapse
Stick to Sprint Stock, otherwise build something of your own.

atapia984 said:
Stick to Sprint Stock, otherwise build something of your own.
Click to expand...
Click to collapse
Quit bashing like everyone else.

locoboi187 said:
Quit bashing like everyone else.
Click to expand...
Click to collapse
There was only one post there, and that was mine. I don't see "everyone else." You have asked for a suggestion, I gave you a couple.

atapia984 said:
There was only one post there, and that was mine. I don't see "everyone else." You have asked for a suggestion, I gave you a couple.
Click to expand...
Click to collapse
I never asked for a suggestion, and everyone else bashes a person when somebody says something negative about the EVO ports.

The stable ROMs are all still there. They haven't changed in awhile, because the most stable ROMs are modifications of the stock ROMs. There hasn't been a new stock ROM released in 5 and a half months. Most of the current development activity is around CM7, which while stable overall is much more experimental than a ROM based on stock will be, and around ports of Sense 2.1 and 3.0 along with Gingerbread. Ports will usually (if not always) be less stable than a ROM that HTC actually developed for the Evo. Many of them are impressively stable given the obstacles they have to get over when porting.
Nothing's stopping you from running Myn's RLS5 if that's what you want. We'll get a new stable GB ROM from HTC sometime in the next month or two, and I imagine all the major devs will customize it and create a new batch of ROMs that have that same level of stability. Until then, either stick with something older that's based on the 3.70 stock ROM, or live with the pitfalls of bleeding edge that are inherent in the current ROMs.

bkrodgers said:
The stable ROMs are all still there. They haven't changed in awhile, because the most stable ROMs are modifications of the stock ROMs. There hasn't been a new stock ROM released in 5 and a half months. Most of the current development activity is around CM7, which while stable overall is much more experimental than a ROM based on stock will be, and around ports of Sense 2.1 and 3.0 along with Gingerbread. Ports will usually (if not always) be less stable than a ROM that HTC actually developed for the Evo. Many of them are impressively stable given the obstacles they have to get over when porting.
Nothing's stopping you from running Myn's RLS5 if that's what you want. We'll get a new stable GB ROM from HTC sometime in the next month or two, and I imagine all the major devs will customize it and create a new batch of ROMs that have that same level of stability. Until then, either stick with something older that's based on the 3.70 stock ROM, or live with the pitfalls of bleeding edge that are inherent in the current ROMs.
Click to expand...
Click to collapse
Thanks for that helpful response that was not counterproductive. I will stick with AOSP Gingerbread for now

locoboi187 said:
I never asked for a suggestion, and everyone else bashes a person when somebody says something negative about the EVO ports.
Click to expand...
Click to collapse
You mentioned you want to get something stable with EVERYTHING working. Stick to Sprint Stock.

I'm running Deck 1.2r and have been running Deck since 1.1 and It sseems pretty damn stable to me get around 12hr of battery on moderate use, haven't had to reboot in over a week. Just gotta keep your eyes open.
--In 1938 I killed a Hobo--

You're talking buggy ports of future software versions versus stable available builds?
Yeah, it's just you.
And, no, it's not 'food for thought.'
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

atapia984 said:
You mentioned you want to get something stable with EVERYTHING working. Stick to Sprint Stock.
Click to expand...
Click to collapse
Mentioning and asking are two completely different concepts.

I just recently said the same thing and got jumped on for not knowing: "instead of focusing on one port of software from the "future" Let's just grab everything we can from the "future" and throw it out there and have the first 4 pages of the development section full of non full working roms and jump on anyone that says "what gives"
I mean really you guys don't have to be anal about everything. Take a second to at least explain to the guy the situation at hand because between the 35549 pages of "get your cards partitioned this is going to be huge" and "OMG I'm so excited i'm going to hit f5 til my keyboard falls off" some may not understand that what's coming may actually cause their phone to do nothing more than FORCE CLOSE constantly.
And of course i'll get rebuttals of "Oh gee well use the search feature" and of course we should do that but when we do look at the good old "Known issues in the first post" we see nothing but "ELG drivers the phone may not be 100 percent and may stay on the lock screen for a few minutes" Which seems harmless and when you take the plunge your welcomed to an erratic mess.
And when you get frustrated the "Future port police" come badge flashing and baton swinging as if you should be shot for even saying "where are the stable roms." This place used to have posters who used to have manners. Now instead of trying to understand the frustrations of others, they take opportunities wheever possible to be anal.

imwillzillla said:
I just recently said the same thing and got jumped on for not knowing: "instead of focusing on one port of software from the "future" Let's just grab everything we can from the "future" and throw it out there and have the first 4 pages of the development section full of non full working roms and jump on anyone that says "what gives"
I mean really you guys don't have to be anal about everything. Take a second to at least explain to the guy the situation at hand because between the 35549 pages of "get your cards partitioned this is going to be huge" and "OMG I'm so excited i'm going to hit f5 til my keyboard falls off" some may not understand that what's coming may actually cause their phone to do nothing more than FORCE CLOSE constantly.
And of course i'll get rebuttals of "Oh gee well use the search feature" and of course we should do that but when we do look at the good old "Known issues in the first post" we see nothing but "ELG drivers the phone may not be 100 percent and may stay on the lock screen for a few minutes" Which seems harmless and when you take the plunge your welcomed to an erratic mess.
And when you get frustrated the "Future port police" come badge flashing and baton swinging as if you should be shot for even saying "where are the stable roms." This place used to have posters who used to have manners. Now instead of trying to understand the frustrations of others, they take opportunities wheever possible to be anal.
Click to expand...
Click to collapse
Everyone's a Republican lately ;P

felacio said:
I'm running Deck 1.2r and have been running Deck since 1.1 and It sseems pretty damn stable to me get around 12hr of battery on moderate use, haven't had to reboot in over a week. Just gotta keep your eyes open.
--In 1938 I killed a Hobo--
Click to expand...
Click to collapse
12 hours on moderate use is not good.

imwillzillla said:
I just recently said the same thing and got jumped on for not knowing: "instead of focusing on one port of software from the "future" Let's just grab everything we can from the "future" and throw it out there and have the first 4 pages of the development section full of non full working roms and jump on anyone that says "what gives"
I mean really you guys don't have to be anal about everything. Take a second to at least explain to the guy the situation at hand because between the 35549 pages of "get your cards partitioned this is going to be huge" and "OMG I'm so excited i'm going to hit f5 til my keyboard falls off" some may not understand that what's coming may actually cause their phone to do nothing more than FORCE CLOSE constantly.
And of course i'll get rebuttals of "Oh gee well use the search feature" and of course we should do that but when we do look at the good old "Known issues in the first post" we see nothing but "ELG drivers the phone may not be 100 percent and may stay on the lock screen for a few minutes" Which seems harmless and when you take the plunge your welcomed to an erratic mess.
And when you get frustrated the "Future port police" come badge flashing and baton swinging as if you should be shot for even saying "where are the stable roms." This place used to have posters who used to have manners. Now instead of trying to understand the frustrations of others, they take opportunities wheever possible to be anal.
Click to expand...
Click to collapse
+1
There are stable ROMS, NOT CM7 or MIUI, btw, you just have to look past page one on the Dev forum and read the last few comments.
One of the things I liked about SDX is that when we were dev'ing the moment, there is a section for testing and a section for releases, which usually needed to be stable before they got posted in that forum

What is moderate use anyways normal use for me is being on my phone often which to some would be heavy lol with me using my phone the way I do is moderate heavy imo is like playing a game for a ur or two
Sent from my PC36100 using XDA Premium App

Some of the new ports of the shift are stable, but some of those ports have funky colors! I wished a stock version were released along with the funky color versions
flame on!!!!!!!

lost my job becuase of this phone

i've been running late on my work a few times before
and today i overslept and they fired me
all becuase of my phone that died in my sleep.
yesterday before i went to bed my phone was at 98%
and when i woke it was completly dead!
i have no idea what happend and i tried to tell them with these graphs:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
but it didn't make any difference.
this android bug really starts to piss me off!
sorry to offend anyone with an gsgII but i'm very displeased with this phone.
and it's even running on stock firmware o_0
I understand it can happen when trying to fiddle the heck out of it but an out of the box galaxy?
sure it can perform and sure it has all the bells and whistles but for an 500 euro costing phone, this is fubar.
Before i was still ok with waiting for the official 2.3.4 firmware but now i dont give a damn anymore. i rooting this phone and hoping with a good rom (miui?) to solve this error.

huahuahuhuahuahu... are you kidding?? uhahuahuahuahuahua

busterdev said:
i've been running late on my work a few times before
and today i overslept and they fired me
all becuase of my phone that died in my sleep.
yesterday before i went to bed my phone was at 98%
and when i woke it was completly dead!
but it didn't make any difference.
this android bug really starts to piss me off!
sorry to offend anyone with an gsgII but i'm very displeased with this phone.
and it's even running on stock firmware o_0
I understand it can happen when trying to fiddle the heck out of it but an out of the box galaxy?
sure it can perform and sure it has all the bells and whistles but for an 500 euro costing phone, this is fubar.
Before i was still ok with waiting for the official 2.3.4 firmware but now i dont give a damn anymore. i rooting this phone and hoping with a good rom (miui?) to solve this error.
Click to expand...
Click to collapse
Im sorry to say this, if your not trolling you fail really hard.. First of all, what are you doing here, the bug is known, and you should spend your time looking for a new job right now. Second, if it happened before you could have just bought a dedicated alarm. And if you where a really good employee, they wouldn't have fired you, there are probably other reasons.
My apologies if I sound harsh, but you really need to get some **** together.. (in your head & your life)
Good luck.

All I can do is laugh. Lol

Ok so you relied on a piece of technology not plugged into the wall to wake you up in the morning?
Seriously dude I think you need to think abit more about how this is your fault and not your handset.
It's well documented about the battery life thing, and as for Stock ROMs well there crap, look at Lightening, or Villiian

Next time you have to ask your mum, to awake you in the morning
Cheers
*Im Jahre des Herrn 2011*

ut oh not good news about the job and i hope you find another but blaming the phone is a bit much i really hope you didnt say it to the boss as he wa telling you off .
Surely you had warnings and then thought that maybe the sgs2 wasnt such a good alarm clock till your toubles are solved .
When i read the title i thought it would be because you couldnt put the phone down which would be understandable , but to blame the phone for not waking you because of battery drain is a bit much
On a side note you must have a rouge setting or something as there is no way my sgs2 would drain that much overnight . 98% to zero is quite a big drain and you must have something set up wrong etc

It's your own fault for being an idiot really. Put it on charge overnight? Or you know, buy an alarm clock!

Stitch! said:
Im sorry to say this, if your not trolling you fail really hard.. First of all, what are you doing here, the bug is known, and you should spend your time looking for a new job right now. Second, if it happened before you could have just bought a dedicated alarm. And if you where a really good employee, they wouldn't have fired you, there are probably other reasons.
My apologies if I sound harsh, but you really need to get some **** together.. (in your head & your life)
Good luck.
Click to expand...
Click to collapse
That's what I was thinking too but it's probably less painful to blame a phone than yourself

Go back to your boss and say....Look here ole boy, I'm sure your correct about making my position within this company redundant, but alas it was not my fault, it was my Samsung Galaxy S2 (at this point said person pulls his SGS2 from his inside pocket and projects it forward so as said boss can see it), then walk out of the office singing a happy tune, I'm sure he will then confirm within his mind that he made the correct decision. Advice = Buy an Alarm clock

busterdev said:
i've been running late on my work a few times before
and today i overslept and they fired me
all becuase of my phone that died in my sleep.
yesterday before i went to bed my phone was at 98%
and when i woke it was completly dead!
i have no idea what happend and i tried to tell them with these graphs:
but it didn't make any difference.
this android bug really starts to piss me off!
sorry to offend anyone with an gsgII but i'm very displeased with this phone.
and it's even running on stock firmware o_0
I understand it can happen when trying to fiddle the heck out of it but an out of the box galaxy?
sure it can perform and sure it has all the bells and whistles but for an 500 euro costing phone, this is fubar.
Before i was still ok with waiting for the official 2.3.4 firmware but now i dont give a damn anymore. i rooting this phone and hoping with a good rom (miui?) to solve this error.
Click to expand...
Click to collapse
unbelievable stuff and i hope you are kidding...
you dont sound too depressed ...you have rooting the phone & trying to fix it as a higher priority than sorting your life...
on top off that you are showing your employer the battery graph as an excuse for being late for work...
amazing...
next time dont loose a job due to alarm clock... be it on any device..

His boss obviously had phone envy and sacked him

Sorry to hear this OP. Good luck getting a new job and maybe then you can buy a new device.

wow some harsh replies.
especially kawa636r who replies in "hua" language. really helpful
understandable as this is the lion's den of the sgs2.
but please, im not wanting to stirr something up here. So i leave it at that.
so ok. my own fault. had to rely on an dedicated alarm. should have known about the issues.
but how should i have known that it would have died?
98% full has got to be safe to assume its going to last about 7 hours right.

I'm going to go against the flow and herd mentality and speak up for the OP.
Firstly, I think it is perfectly reasonable for anyone to expect a phone at 98% charge to last throughout the night, especially when it is not in use.
Now, a few of you have came out to say that "It's a known bug". Known to who? Note that the OP is a new user, registered in June 2011. He probably doesn't spend as much time here as you guys who know about the bug.
As for his job performance, we don't know that so let's not make any judgements about that.
On an OT note, it is interesting to me, having taken social psychology last semester, that many of you westerners are making internal dispositions for his behavior, while my first thought as an Asian was to make an external or situational disposition.

Logi_Ca1 said:
I'm going to go against the flow and herd mentality and speak up for the OP.
Firstly, I think it is perfectly reasonable for anyone to expect a phone at 98% charge to last throughout the night, especially when it is not in use.
Now, a few of you have came out to say that "It's a known bug". Known to who? Note that the OP is a new user, registered in June 2011. He probably doesn't spend as much time here as you guys who know about the bug.
As for his job performance, we don't know that so let's not make any judgements about that.
On an OT note, it is interesting to me, having taken social psychology last semester, that many of you westerners are making internal dispositions for his behavior, while my first thought as an Asian was to make an external or situational disposition.
Click to expand...
Click to collapse
Apart from the quack talk, I agree with your post.

Logi_Ca1 said:
On an OT note, it is interesting to me, having taken social psychology last semester, that many of you westerners are making internal dispositions for his behavior, while my first thought as an Asian was to make an external or situational disposition.
Click to expand...
Click to collapse
We are all sorry he lost his job but blaming outside dispositions isn't going to help him because he can't control them but he can control internal ones we are actually empowering him. And if I were I boss I wouldn't fire a good employee who made one mistake

Logi_Ca1 said:
On an OT note, it is interesting to me, having taken social psychology last semester, that many of you westerners are making internal dispositions for his behavior, while my first thought as an Asian was to make an external or situational disposition.
Click to expand...
Click to collapse
Just out of general curiosity, do you call the US folk easterners then? Because they're east of Asia...
Edit: and all the other americans too

Oh, wow.. Lol
Yea. I agree with you OP. When you buy a phone and leave it at 98% overnight it should stay alive. And everyone cant know about this bug. And dosent seem to be on all sgs2's as mine was in standby longer than that when I had stock rom.
Sorry about your job.
Learn from this experience.
I never rely on my phone as an alarm unless its plugged in. As I too learned it this way. Didnt loose any job but missed an exam in school. And I bet many of you other guy have had a similar experience sometime in your life.

Pume said:
Just out of general curiosity, do you call the US folk easterners then? Because they're east of Asia...
Edit: and all the other americans too
Click to expand...
Click to collapse
South Americans you mean?

[POLL] CM9: Worth it?

Alright, so in the last few days I've been complementing whether or not I should give cm9 another try (I tried it on alpha0, but too buggy). I'm aware of the bugs such as "The ringing of death" and others. Most of you are probably wondering "Why don't I just flash it now and see for myself?" While I am considering that, I'm not one that likes to flash things since it takes me time to get everything set up the way I wanted. I figured this way I'd save some trouble and also give others the chance to see whether or not the majority of users here enjoy it.
I've broken it down into reasons why I do and don't want to flash it.
Reasons why I do:
New apps compatible with ICS
The latest android version (along with its features)
Makes my phone feel new
Reasons why I don't:
Battery life (I just need it to last the day)
Video Playback artifacts (how frequent is this?)
Less features than CM7
So I made a poll to see whether or not I should go through with it, and to help those that are complementing the same thing.
Edit: Just realized in the poll I put "No" for the last answer. Meant to put "Neither" lol.

Honestly this poll is kind of a bash to the devs that put so much time and effort to bringing cm9 to our phone so yes its worth it.

jbadboy2007 said:
Honestly this poll is kind of a bash to the devs that put so much time and effort to bringing cm9 to our phone so yes its worth it.
Click to expand...
Click to collapse
Sorry if that's what it appears, but that wasn't my intention. CM9 is great, I respect the devs, and I can't wait to see its potential. I'm just not sure whether I want to flash it only because of issues ICS (not cm9) has. For example, battery life. Battery life on ICS in general is bad, but my question in that aspect is "HOW bad?". I've seen many mixed results with some awful battery life, some decent, etc. I just want to save people the trouble, and myself, of having to flash a ROM they're not sure is right for them just yet.

*Contemplating
Sent from my SPH-D700

|| Acer || said:
Sorry if that's what it appears, but that wasn't my intention. CM9 is great, I respect the devs, and I can't wait to see its potential. I'm just not sure whether I want to flash it only because of issues ICS (not cm9) has. For example, battery life. Battery life on ICS in general is bad, but my question in that aspect is "HOW bad?". I've seen many mixed results with some awful battery life, some decent, etc. I just want to save people the trouble, and myself, of having to flash a ROM they're not sure is right for them just yet.
Click to expand...
Click to collapse
I know where you coming from but you need to remember its an alpha and everything isn't suppose to be fully functional yet although most things are. Consider it more like public bug testing. I need full functionality for business everyday so honestly I know not to try these builds during the week when I expect my phones features to be fully operational.

jbadboy2007 said:
I know where you coming from but you need to remember its an alpha and everything isn't suppose to be fully functional yet although most things are. Consider it more like public bug testing. I need full functionality for business everyday so honestly I know not to try these builds during the week when I expect my phones features to be fully operational.
Click to expand...
Click to collapse
I know and I'm completely aware of what you're saying. I know it's an alpha, and I know there are bugs. I'm just wondering if the majority of users think I should use the alpha as a daily driver or just wait. That's really the issue. Whether I should just wait or not.

Video playback tearing and artifacts in recording can be a pain sometimes. I've noticed in youtube there's barely any tearing in HQ but the same can't be said for the built in video player (even HD videos tear). Call quality has improved with the recent changes but is still far from perfect. Battery life (for me anyway) has been just fine. I hardly ever get the "ring of death" but I've found it's not difficult or impossible to work around without having to reboot. Features are still missing but that will come as cm itself updates for cm9. Peformance and stability (again for me anyway) has been just fine and it seems to handle 3D graphics better than any rom I've ever used. Overall I've been able to deal with it being my daily driver and just waiting for updates. Of course I'm going to hope for certain things to come in due time but I'm overall more satisfied with cm9 than I was with cm7. If there's anything else specific you wanted to know that I didn't cover, ask.
Sent from my SPH-D700 using Tapatalk

Vizzo said:
Video playback tearing and artifacts in recording can be a pain sometimes. I've noticed in youtube there's barely any tearing in HQ but the same can't be said for the built in video player (even HD videos tear). Call quality has improved with the recent changes but is still far from perfect. Battery life (for me anyway) has been just fine. I hardly ever get the "ring of death" but I've found it's not difficult or impossible to work around without having to reboot. Features are still missing but that will come as cm itself updates for cm9. Peformance and stability (again for me anyway) has been just fine and it seems to handle 3D graphics better than any rom I've ever used. Overall I've been able to deal with it being my daily driver and just waiting for updates. Of course I'm going to hope for certain things to come in due time but I'm overall more satisfied with cm9 than I was with cm7. If there's anything else specific you wanted to know that I didn't cover, ask.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Thanks this is exactly the kind of response I was looking for. I rarely use video recording so that's not an issue for me. The biggest thing was the battery life and I think I've decided to wait until alpha4, because I'll definitely flash when the "Ring of Death" is fixed. I make quite a lot of calls, and even though people rarely get it, I'd rather not have to deal with that. Once again, thanks for your response.
Just a question since I'm curious: What CM features have been implemented so far in CM9?

Pssh if you use an alternative kernel and uv like a son of a ...then battery life is decent, I usually pulled 8 hours with 3 hours of display and 2 hours of music note the screen time on was heavy it would be on 20 or 30 minutes at a time.....
On my 3500 I get 6 and a half display and 13 hours overall.. I did 22 hours with just 6 flat.
Just do it I have cm7 miui and tw nandroids and haven't gone back because I love this ROM so much, there are some tips to get things rolling and so forth... so be prepared to make modifications.
Id be happy to let you know how I have my phone setup to my liking and hopefully make this transition easy for ya
Sent From My SPH-D700 Running Android 4.0 :sly:

Worth it....with a proviso about batt life

Biggoron said:
Pssh if you use an alternative kernel and uv like a son of a ...then battery life is decent, I usually pulled 8 hours with 3 hours of display and 2 hours of music note the screen time on was heavy it would be on 20 or 30 minutes at a time.....
On my 3500 I get 6 and a half display and 13 hours overall.. I did 22 hours with just 6 flat.
Just do it I have cm7 miui and tw nandroids and haven't gone back because I love this ROM so much, there are some tips to get things rolling and so forth... so be prepared to make modifications.
Id be happy to let you know how I have my phone setup to my liking and hopefully make this transition easy for ya
Sent From My SPH-D700 Running Android 4.0 :sly:
Click to expand...
Click to collapse
Thanks so much. I guess I'll do it over the weekend (Don't wanna get TOO distracted when I have homework haha). On a normal day, I just keep my phone on airplane mode during school, listen to music for about 2 hours, and then use my phone for half an hour before putting it on its charger when I get home. That usually brings it down to 60-70% depending on what I'm doing. If you have any battery tips, I'd be glad to hear some. (Other than the obvious ones, like lower brightness and stuff). Lastly, what is the "Ring of Death" exactly like? If I were on the phone with someone, would it be so annoying that they would be distracted by it? Just curious.
Edit: Forgot to mention...is restoring apps (and their data) via TB okay to do? I read in the blog that it's not recommended and to have a fresh start, but there's a few games and other apps where I would like to keep my data.

I have used it as a daily rom since alpha 0. On completely stock CM9 and i get 10-15 hours on a OEM battery. I have been blessed and haven't had any video issues ( i take a lot of videos of my 8 month old daughter).
Def. Not up to par with CM7 but with features and battery life but it's only in alpha. I enjoy seeing and appreciating the changes when updates come out. Also saying my Epic has ICS and yours doesn't is fun lol. My co-workers are begging me to completely redo their Epic. (never will happen, none of then know what the term root or odin mean).
Honestly my suggestion flash CM9 with stock kernel and see if you can make it a week or 2. If you can't then see if a 3rd party kernel will please your needs. Then after that if you feel you can't stand the interesting bugs then take the time and go back to CM7.
Sent from my CM9 Epic 4G.

|| Acer || said:
Thanks so much. I guess I'll do it over the weekend (Don't wanna get TOO distracted when I have homework haha). On a normal day, I just keep my phone on airplane mode during school, listen to music for about 2 hours, and then use my phone for half an hour before putting it on its charger when I get home. That usually brings it down to 60-70% depending on what I'm doing. If you have any battery tips, I'd be glad to hear some. (Other than the obvious ones, like lower brightness and stuff). Lastly, what is the "Ring of Death" exactly like? If I were on the phone with someone, would it be so annoying that they would be distracted by it? Just curious.
Edit: Forgot to mention...is restoring apps (and their data) via TB okay to do? I read in the blog that it's not recommended and to have a fresh start, but there's a few games and other apps where I would like to keep my data.
Click to expand...
Click to collapse
Honestly, I have never had the "Ring of Death". I haven't had really any bugs on mine. This, in my opinion, is the most stable alpha rom I've ran.
And yes TB works fine. That's how I restore apps w/ data.
Sent from my Cyanogenmodded Epic4g! Wanna fight about it?

|| Acer || said:
Thanks so much. I guess I'll do it over the weekend (Don't wanna get TOO distracted when I have homework haha). On a normal day, I just keep my phone on airplane mode during school, listen to music for about 2 hours, and then use my phone for half an hour before putting it on its charger when I get home. That usually brings it down to 60-70% depending on what I'm doing. If you have any battery tips, I'd be glad to hear some. (Other than the obvious ones, like lower brightness and stuff). Lastly, what is the "Ring of Death" exactly like? If I were on the phone with someone, would it be so annoying that they would be distracted by it? Just curious.
Edit: Forgot to mention...is restoring apps (and their data) via TB okay to do? I read in the blog that it's not recommended and to have a fresh start, but there's a few games and other apps where I would like to keep my data.
Click to expand...
Click to collapse
Id start just turning off data that will save you a lot and you'll still be able to snext -sneak texting ftw
Don't use any third party apps for "battery saving" they don't work properly and drain more than anything. Keep your running processes low I only have settings and the keyboard running normally when you pull up running processes. Don't sync email manual push for notifications.
Use the dalvik heap tweaks to keep ram available and less battery use, disable touch sounds and lock sounds to keep from audio out from wakelocking. Forgot to mention my screen wasn't at the lowest % it was at least 30 or 40%.
Sent From My SPH-D700 Running Android 4.0 :sly:

seanknighton said:
And yes TB works fine. That's how I restore apps w/ data.
Click to expand...
Click to collapse
Ya it works....BUT the CM team is not recommending it right now if you wish to avoid random issues.
http://epiccm.blogspot.com/p/cm9-install-guide.html

backup ur rom and go for it. battry life on cm7 is not that muchbetter, imho. u could always tweak the settings or even use samurai kernel, and undervolt to maximize battery life. there is also numerous governors with thatand the stock kernel ghat u can playwith. its truly an awesome build. these devs have done some truly amazing work. if ur not convinced, restore ur backup

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

|| Acer || said:
Thanks this is exactly the kind of response I was looking for. I rarely use video recording so that's not an issue for me. The biggest thing was the battery life and I think I've decided to wait until alpha4, because I'll definitely flash when the "Ring of Death" is fixed. I make quite a lot of calls, and even though people rarely get it, I'd rather not have to deal with that.
Click to expand...
Click to collapse
http://code.google.com/p/epiccm/issues/detail?id=33
Please test the build here and report back.

RyleyinSTL said:
Ya it works....BUT the CM team is not recommending it right now if you wish to avoid random issues.
http://epiccm.blogspot.com/p/cm9-install-guide.html
Click to expand...
Click to collapse
Yeah. I've never had any issues, but that is me personally. I don't do a lot of tweaking once I flash the rom
Sent from my Cyanogenmodded Epic4g! Wanna fight about it?

Ha this thread/poll does not bash devs. They work on CM9 for themselves, the prestige and the challenge of doing it too. They'd just use this as motivation. This is a good question. Anyways - I'm on cm9 now and am enjoying it more than I expected too. Battery life does not seem to last as long but I still get through the day. alpha3 seemed to work out some of the more annoying bugs (for me), like fixing the speakerphone.
Honestly, I'd make a backup in clockwork and then flash. Worst that happens you restore the backup.
Sent from my SPH-D700 using xda premium