Hey fellas, new to modding. Have a samsung captivate. Cutting right to the chase.
So i got this phone about 1 week ago. Used the stock ROM (2.3.5) for about 2 days. Then flashed CM 10. Then flashed CM 10.1. Now today flashed "Captivating (Xperia)" ROM. I've been facing one single problem in all the ROMS (That i didn't notice in the stock ROM), the colors are not proper in the custom ROMS. Like, pixelation (on a big level) at the regions where screen's black region meets any coloured region. (I know, difficult to understand & difficult to explain as well, so i've attached 2 images to show it).
I first noticed it on the CM 10 boot animation. It was highly pixelated at edges (both inside & outside the ring). Ugly to look.
& i know that it's not the resolution problem. (My friend is using the SGS 2, flashed CM 10.1 last night, has crisp clear graphics, same res & larger screen than captivate)
It's present EVERYWHERE. In bootanimation, wallpapers, videos, apps, etc. wherever black meets any color.
What is it.? How to fix it.? Is it any soft problem or a hardware problem.?
P.S. Going to setting -> advanced -> Color Tuning -> & setting-
Red - 1.000 (Default value)
Green - 1.000 (Default value)
Blue - 1.000 (Default value)
Red Gamma - -40
Green Gamma - -40
Blue Gamma - -40
does solve it a little, still the problem is there.
Moreover, it doesn't solve the prob of the bootanimation.
What to do.?
I have followed the same path from GB to CM10 to 10.1.
Never had any color shifting or LCD problems in months of use with CM. At one point I get a yellowish tint on a Semaphore kernel. I restored an earlier CM10.0 and the problem never repeated itself.
Do you have the problem on straight, stable CM10.0?
When you got the phone on GB, did it have the Corn kernel? What were the settings in Voodoo color? That might help you understand how to tweak JB settings.
ishandigipunk said:
Hey fellas, new to modding. Have a samsung captivate. Cutting right to the chase.
So i got this phone about 1 week ago. Used the stock ROM (2.3.5) for about 2 days. Then flashed CM 10. Then flashed CM 10.1. Now today flashed "Captivating (Xperia)" ROM. I've been facing one single problem in all the ROMS (That i didn't notice in the stock ROM), the colors are not proper in the custom ROMS. Like, pixelation (on a big level) at the regions where screen's black region meets any coloured region. (I know, difficult to understand & difficult to explain as well, so i've attached 2 images to show it).
I first noticed it on the CM 10 boot animation. It was highly pixelated at edges (both inside & outside the ring). Ugly to look.
& i know that it's not the resolution problem. (My friend is using the SGS 2, flashed CM 10.1 last night, has crisp clear graphics, same res & larger screen than captivate)
It's present EVERYWHERE. In bootanimation, wallpapers, videos, apps, etc. wherever black meets any color.
What is it.? How to fix it.? Is it any soft problem or a hardware problem.?
P.S. Going to setting -> advanced -> Color Tuning -> & setting-
Red - 1.000 (Default value)
Green - 1.000 (Default value)
Blue - 1.000 (Default value)
Red Gamma - -40
Green Gamma - -40
Blue Gamma - -40
does solve it a little, still the problem is there.
Moreover, it doesn't solve the prob of the bootanimation.
What to do.?
Click to expand...
Click to collapse
As for I can see with the pics, your gamma is off the hook. That's not by default though, there's something that was changed. Did you play with Voodoo or color settings before and after flashing?
Did you try going back to stock and reflashing? (clean flash)
Did you try using different color temperature? (cold, warm, normal)
I see you reduced your gamma by quite a lot but there should be a better solution. Unless you have some overpowered digitalizer lol. Which brings me to think, was the screen replaced?
First off, the phone came with the official samsung 2.3.5 gingerbread ROM. At that time, i didn't notice any such issues (so i guess i can conclude that they were absent at that time).
Then i put in the speedmod kernel. Flashed cm10 (stable). Had this colour problem. I've now had this color problem ever since i flashed cm10.
On an unrelated note, m getting very poor battery life. I charge the phone till 100% (I've been leaving it at charging overnight since the last 2 charges, still the problem persists), & i remove the charger at about 7 in the morning. No music. A little (& very light) gaming (temple run, subway surfers, etc) for about 30 minutes total throughout the day. Screen brightness at lowest at max times during the day. very little calling. very little messaging. Oh, & NO cellular data connection (No GPRS, EDGE, 3G or anything for internet). Only wifi. That too for around 1 hour total. & still my battery goes flat to zero in about 12 hours (or even less). Is this normal.? I don't really remember how my battery was at the stock ROM, but it's like this on CM 10. Is this normal at all.? Is there any way to check battery.? Is it just a bad battery.? Or is this just the normal battery life of this phone.? (Cuz i read samsung galaxy S review on gsmarena, which is basically the same phone, & it manages to squeeze out around 3.5 days of battery life under their tests, which include pretty heavy usage with 3g enabled all the time)
& no, i got a new phone. So i really don't think the screen was replaced. Is it possible i was cheated through the dealer somehow.? I got it over at ebay.in.
M gonna flash stock ROM in a few hours. M currently downloading this one. Is this the correct one.?
http://forum.xda-developers.com/showthread.php?t=731989
M confused, in settings now (in cm10), it shows Baseband version - I9000UGKG3. That ain't correct. Right.? How to know which stock rom i have to flash now.? I forgot to check my stock rom's baseband. I have to use the phone in India over the Indian baseband.
EDIT: Oh & i didn't change any settings (or any voodoo settings) for any kernel or anywhere at all. i noticed that colour problem in CM 10 boot animation. Many times. Then played around with display settings in cm10.
ishandigipunk said:
First off, the phone came with the official samsung 2.3.5 gingerbread ROM. At that time, i didn't notice any such issues (so i guess i can conclude that they were absent at that time).
Then i put in the speedmod kernel. Flashed cm10 (stable). Had this colour problem. I've now had this color problem ever since i flashed cm10.
On an unrelated note, m getting very poor battery life. I charge the phone till 100% (I've been leaving it at charging overnight since the last 2 charges, still the problem persists), & i remove the charger at about 7 in the morning. No music. A little (& very light) gaming (temple run, subway surfers, etc) for about 30 minutes total throughout the day. Screen brightness at lowest at max times during the day. very little calling. very little messaging. Oh, & NO cellular data connection (No GPRS, EDGE, 3G or anything for internet). Only wifi. That too for around 1 hour total. & still my battery goes flat to zero in about 12 hours (or even less). Is this normal.? I don't really remember how my battery was at the stock ROM, but it's like this on CM 10. Is this normal at all.? Is there any way to check battery.? Is it just a bad battery.? Or is this just the normal battery life of this phone.? (Cuz i read samsung galaxy S review on gsmarena, which is basically the same phone, & it manages to squeeze out around 3.5 days of battery life under their tests, which include pretty heavy usage with 3g enabled all the time)
& no, i got a new phone. So i really don't think the screen was replaced. Is it possible i was cheated through the dealer somehow.? I got it over at ebay.in.
M gonna flash stock ROM in a few hours. M currently downloading this one. Is this the correct one.?
http://forum.xda-developers.com/showthread.php?t=731989
M confused, in settings now (in cm10), it shows Baseband version - I9000UGKG3. That ain't correct. Right.? How to know which stock rom i have to flash now.? I forgot to check my stock rom's baseband. I have to use the phone in India over the Indian baseband.
EDIT: Oh & i didn't change any settings (or any voodoo settings) for any kernel or anywhere at all. i noticed that colour problem in CM 10 boot animation. Many times. Then played around with display settings in cm10.
Click to expand...
Click to collapse
Oh god I hope I'm not too late. The Odin you've downloaded is a old version and contains froyo bootloaders.
You'll want Odin KK4 without Bootloaders to get back to stock.
If you already flashed the other one, you're most likely back on froyo or Eclair. You'll need Odin KK4 with Bootloaders to get back to stock GB.
As for the dealer, yes, it's possible that the phone isn't actually new or that the screen was replaced.
BWolf56 said:
Oh god I hope I'm not too late. The Odin you've downloaded is a old version and contains froyo bootloaders.
You'll want Odin KK4 without Bootloaders to get back to stock.
If you already flashed the other one, you're most likely back on froyo or Eclair. You'll need Odin KK4 with Bootloaders to get back to stock GB.
As for the dealer, yes, it's possible that the phone isn't actually new or that the screen was replaced.
Click to expand...
Click to collapse
Phew. Thank god i've crossed my FUP limit & have an epic slow internet connection right now.
the file was still downloading. Otherwise i would've flashed with that. Thanks for the warning man.
Anyway, do u think stock ROM will solve the battery problem.?
Saw this page too..
http://forum.xda-developers.com/showthread.php?t=1300843
Do i need to flash "I897UCKK1" "Without Bootloaders" .??
EDIT: Oops. Sorry. Just read your complete message. Downloading that file now. Thanks.
ishandigipunk said:
Phew. Thank god i've crossed my FUP limit & have an epic slow internet connection right now.
the file was still downloading. Otherwise i would've flashed with that. Thanks for the warning man.
Anyway, do u think stock ROM will solve the battery problem.?
Saw this page too..
http://forum.xda-developers.com/showthread.php?t=1300843
Do i need to flash "I897UCKK1" "Without Bootloaders" .??
EDIT: Oops. Sorry. Just read your complete message. Downloading that file now. Thanks.
Click to expand...
Click to collapse
Battery problems are user specific, not ROM specific. I'd highly suggest you get BetterBatteryStats to see what's draining your battery. Also, after flashing, it does take a couple full battery cycle to get the best outta your battery.
BWolf56 said:
Battery problems are user specific, not ROM specific. I'd highly suggest you get BetterBatteryStats to see what's draining your battery. Also, after flashing, it does take a couple full battery cycle to get the best outta your battery.
Click to expand...
Click to collapse
Hmm. Alright. But.. Really.. I've read some reviews.. (& also, i've written my usage above, is that even real.? Cuz a few weeks ago i was on motorola Defy+ & i could easily get 2 days of battery life at heavier usage than my current usage) & according to reviews, m supposed to get even more battery life on captivate.! That's why i was asking. Cuz gsmarena claims it gets 3.5 days of battery life under normal average load (Which m not even putting on it most of the time.!) & with 3g ENABLED.! (which m not enabling at all, infact no data connection via sim, only wifi, that too very less). Still just 12 hours of battery life.
Anyway, flashing stock ROM soon. Will use that for a week i think. To test out my phone. Then will see what to do.
EDIT: Another (& probably the most important) question.! Will the device still stay unlocked after flashing it back to stock ROM (i bought it factory unlocked)
the i9000 baseband is correct for cm10 captivatemtd build. captivate is a variant of galaxy s series, as is i9000.
that isn't to say that you should go flashing an i9000 rom.
captivate lacks several pieces of hardware that are in other galaxy s phones.
ishandigipunk said:
Hmm. Alright. But.. Really.. I've read some reviews.. (& also, i've written my usage above, is that even real.? Cuz a few weeks ago i was on motorola Defy+ & i could easily get 2 days of battery life at heavier usage than my current usage) & according to reviews, m supposed to get even more battery life on captivate.! That's why i was asking. Cuz gsmarena claims it gets 3.5 days of battery life under normal average load (Which m not even putting on it most of the time.!) & with 3g ENABLED.! (which m not enabling at all, infact no data connection via sim, only wifi, that too very less). Still just 12 hours of battery life.
Anyway, flashing stock ROM soon. Will use that for a week i think. To test out my phone. Then will see what to do.
EDIT: Another (& probably the most important) question.! Will the device still stay unlocked after flashing it back to stock ROM (i bought it factory unlocked)
Click to expand...
Click to collapse
Unlock is permanent so you don't have to worry about that.
Getting 3.5 days with data enabled is nearly impossible with how old the phone and battery is. That would mean no sync, extremely low brightness, no widgets, no GPS/location access, perfect signal (4 bars) at all time and absolutely no gaming.
I would personally get about 2.5-3hrs on screen with my cappy, that was with data, sync, auto brightness enabled and medium usage. Back when I didn't have data though (Froyo days, with Firefly ROM), I would get at least 2 days with medium usage.
You gotta keep in mind that if that gsmarena is on a old firmware, he has about a 1/4 of the features CM has right now and well, more features = more battery drain. Also, battery highly depends on your apps/widgets, the more apps that sync, the more drain you get.
One last thing, CM isn't the only 4.2 ROM out there, feel free to try a few of them.
BWolf56 said:
Unlock is permanent so you don't have to worry about that.
Getting 3.5 days with data enabled is nearly impossible with how old the phone and battery is. That would mean no sync, extremely low brightness, no widgets, no GPS/location access, perfect signal (4 bars) at all time and absolutely no gaming.
I would personally get about 2.5-3hrs on screen with my cappy, that was with data, sync, auto brightness enabled and medium usage. Back when I didn't have data though (Froyo days, with Firefly ROM), I would get at least 2 days with medium usage.
You gotta keep in mind that if that gsmarena is on a old firmware, he has about a 1/4 of the features CM has right now and well, more features = more battery drain. Also, battery highly depends on your apps/widgets, the more apps that sync, the more drain you get.
One last thing, CM isn't the only 4.2 ROM out there, feel free to try a few of them.
Click to expand...
Click to collapse
Alright. Right now m back to stock (2.3.5). Will keep this ROM for a few days. Check out the battery life. The max battery life i can get out of it.
& i don't know if the colour problem is still here in this ROM, but.. i really can't see it anymore. So gonna play around with this ROM. Thank you for your help people.
Oh.! Now i understand it.! M getting what is commonly called "Black Crush".!
Here's a video demonstrating it (In galaxy note & comparing it with a normal captivate)
http://www.youtube.com/watch?v=0a8aIGeLERg
That's why my screen colors were problematic.! & maybe still are problematic. Although i don't think m getting the black crush at THAT level. Any way to solve this issue.? :\
ishandigipunk said:
Oh.! Now i understand it.! M getting what is commonly called "Black Crush".!
Here's a video demonstrating it (In galaxy note & comparing it with a normal captivate)
http://www.youtube.com/watch?v=0a8aIGeLERg
That's why my screen colors were problematic.! & maybe still are problematic. Although i don't think m getting the black crush at THAT level. Any way to solve this issue.? :\
Click to expand...
Click to collapse
First time I hear about this so I dunno if there's a fix or not (other than getting another digitalizer).
BWolf56 said:
First time I hear about this so I dunno if there's a fix or not (other than getting another digitalizer).
Click to expand...
Click to collapse
M not gonna get a new digitalizer for it. Definitely not. I bought this phone just for general usage plus listening music. The colour problem has almost vanished ever since i flashed the stock ROM. The battery has also considerably increased.
I will live with the colour problem if i have to. It won't be worth buying a new digitalizer & replacing the old one.
ishandigipunk said:
M not gonna get a new digitalizer for it. Definitely not. I bought this phone just for general usage plus listening music. The colour problem has almost vanished ever since i flashed the stock ROM. The battery has also considerably increased.
I will live with the colour problem if i have to. It won't be worth buying a new digitalizer & replacing the old one.
Click to expand...
Click to collapse
After your testing, feel free to try another custom ROM, maybe other than CM this time and see if you get better results.
BWolf56 said:
After your testing, feel free to try another custom ROM, maybe other than CM this time and see if you get better results.
Click to expand...
Click to collapse
Okay. will do.
just confirmed another thing. I just flashed cm10.1 (directly from stock)
Now, I can see the color prob. only in the videos though. not images. anyway, it's confirmed new w.. the problem is not there on the stock ROM, but present in the cm 10, 10.1, n the xperia ROM.
n I've also noticed changing gamma values (all to -40) will reduce the prob by a large margin. dunno what the issue is here.
anyway, flashing semaphore kernel with voodoo colour settings now. will post the result in a few hours (or maybe tomorrow morning). all of your help is really appreciated.
EDIT: Flashing with the semaphore kernel with voodoo settings made it much worse. It made that colour problem MUCH MORE noticable. I mean i could literally see thousands of flawed pixels in every frame.!
Will stick with CM 10 stock kernel.
Hello all, this is my first post on Android Central! I wanted to see if anyone had similar problems after converting their T-Mobile HTC One to GPE. I've been tinkering around with my phone for the last few weeks, first by rooting my One and trying out different roms, including a 4.3 GPE rom. When using this rom in particular, my phone would perform beautifully early in the day and in the evening (or sometimes after 50% battery) swiping between the home screen, scrolling, and opening apps would be noticeably slower and less buttery. Resetting the phone would normally correct the issue, at least until the next day.
Needless to say, this was the only downside of running stock Android so I decided to try out full GPE conversion to see that fixed the issue. I did a full wipe and ran the OEM RUU before rerooting, went S-OFF, and finally converted my phone to GPE. I installed the OTA update and everything was working fine until the slowness issues returned, essentially the same as before I converted?
Has anyone else had this problem? Is this being caused by a particular app or process? What kind of screenshots/logs would be helpful to find out what the issue is?
I have a TMO version and a few months ago i did the GPe conversion and mine is working very well. No sluggishness or or battery issues.
josetheman said:
Hello all, this is my first post on Android Central! I wanted to see if anyone had similar problems after converting their T-Mobile HTC One to GPE. I've been tinkering around with my phone for the last few weeks, first by rooting my One and trying out different roms, including a 4.3 GPE rom. When using this rom in particular, my phone would perform beautifully early in the day and in the evening (or sometimes after 50% battery) swiping between the home screen, scrolling, and opening apps would be noticeably slower and less buttery. Resetting the phone would normally correct the issue, at least until the next day.
Needless to say, this was the only downside of running stock Android so I decided to try out full GPE conversion to see that fixed the issue. I did a full wipe and ran the OEM RUU before rerooting, went S-OFF, and finally converted my phone to GPE. I installed the OTA update and everything was working fine until the slowness issues returned, essentially the same as before I converted?
Has anyone else had this problem? Is this being caused by a particular app or process? What kind of screenshots/logs would be helpful to find out what the issue is?
Click to expand...
Click to collapse
Had some issues because I triggered some developer options.. I don't know which it was.. but try to turn them off! ALL of them! Then look if you still experience such performance problems
Thanks for all of your comments. I spent last night deleting apps I didn't use to see if I could find a culprit. As it turns out, the CPU management option in Battery Doctor was turned on. I never thought of turning this off and, frankly, Battery Doctor did little for my battery life in general. I uninstalled the app completely, rebooted, and have actually seen a better battery life and NO sluggishness whatsoever all day today.
Hopefully this wasn't just a temporary solution to my problem!
Good follow up. Keep an eye on it and if its ok for a few days you "should" be out of the woods.
Hi Everyone
Bit of help please.
Having problems over the last 20 days or so. The phone keeps powering down completely at random.
I had flashed No Root Stock Debloated/Deodexed N6 ViPER|Atmos Audiophile 1.6 and after a week the above started.
Fully wiped (including data) the N6 and re-installed from a OTG USB through TWRP. After a week the same random shut-downs began again.
Another full wipe and installed ver 1.7 from the above and within a couple of days the shutdowns started again.
Today thought a different ROM may be the answer. Full wipe and tried [MMB29U/Q][6.0.1][STOCK][OMNI][MOKEE][CMTE][LAYERS] FLUENCE HD9 and the shut-downs are still here.
Seems to be getting worse.
Not using layers or anything abnormal - nova launcher and popular apps, nothing strange. No Kernel optimizations.
Really stumped as to what I have done. Wondering if I have a HW fault rather than custom rom or apps. Going to un-root, lock the BL and give Google stock image a go, unless anyone has a suggestion.
TIA
Any water damage that you can think of? Any parts of the phone getting extremely hot?
You could try ordering a new battery, and see if that fixes the issue, as it is not a software issue.
I'm also having a similar issue, but it occurs when trying to open camera and having relatively low charges(%20). I could not pinpoint my issue exactly but generally complete shutdowns caused by battery problems(temperature, voltage, mis-feedback). Like flyeyes says it is probably a defected battery unit.
Grab some logcats or a crash message. Without them the only thing I can advise is that it is one of your apps causing it or a hardware issue.
Have you tried complete stock firmware from Google with no customizations? If so, does it happen then? If it happens on complete stock from Google you might be looking at a hardware issue. If it only happens on custom ROMS after you set them up, then it might be an inconsistency with whatever apps/changes you make to it.