Related
Well, to tell the truth, I like this phone. Dual-core CPU, perfect screen, HDMI output etc.
But as soon as I get this phone, I found it cannot be wake up from sleep.
I heard that LG has released a update software to fix this problem, but after I had connected my phone to the computer and opened the LGMobile Update, it told me there was no newer update available.
So I'm trying to figure out the reason of this problem.
This problem does not happened every time when I push the ON/OFF button to put the phone to the sleep mode. If I just reboot the phone, and then turn off the screen, there will never be any trouble, even I put it on the desk for the whole night.
But if some programs has been run, like the games, map, internet browser, or even a call or SMS, then lock the screen, it will never wake up. Or if I plug in the charger or connect the phone to the computer, it works great with no trouble.
What's more, after the phone has 'dead', the temperature of the phone became high, and even became higher and higher, very strange.
So I try these way to solve the problem with no success:
-replace the battery with another one.
-wipe the battery information by using ClockworkMod and then re-calibrate the battery.
-flash a different version ROM, including MCR ROM and LG Stock ROM.
-flash a different version baseband.
-force the CPU frequency to stay in 800Mhz by using 'pimp my CPU'.
-lower the voltage of the CPU.
-forced the frequency to stay about 400Mhz when the screen is locked.
-remove any applications installed by myself.
-disallow any background applications.
-put the phone in the rom with air conditioner turning on which the air temperature is about 25°c.
Then I guess this problem is caused by power management bug.
There will never be any problem when the phone is awake, or the charger is plugged in, so I don't think it's a hardware bug.
Must be a bad unit. :-(
Sent from my LG-P990 using Tapatalk
As I said before.
When you press power button to wake-up the screen, and the screen is black (bsod), press power button again (so it would power off the screen, even tho the screen is black), count till 20/30sec and press power button again....
There yoy go, phone working again!
Ive overwon my bsod since I know this trick!
Sent from my LG-P990 using XDA App
Nfsking: Did it work?
Sent from my LG-P990 using Tapatalk
Sckank said:
Nfsking: Did it work?
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
No, no work.
Now, after playing games or using Google Map, I must turn off the phone, and then turn it on again to avoid this issue.
OK, now I can almost confirm that this issue is caused by overheat.
I boot the phone, then put it on the desk without any operation, it will remain OK.
Then I put it into my jeans pocket for about 1~2 minutes, it will be dead.
Again, after playing games, I put the phone just near the air conditioner, it will be cooled down very soon, and the issue will not happen.
So, is there any way to make the ‘temperature protection’ or something like that higher? Or just remove it from the Android OS.
I don't think removing any sort of temp failsafe would be a good idea.
I just had a bsod and the phone was really hot. If anything, it needs a proper failsafe put in, so it at least reboots in stead of hanging on the black screen
Sent from my LG-P990 using XDA App
I had a phone with the usual reboots and charge-bugs like everybody else. I shan't claim I've found a 100% solution, but what I can say is that my phone never reboots/bsods anymore, on stock ROM, MCR or CM7. It does get hot to the touch when it's working hard or charging, but still operates reliably.
There are several version of the basebands floating around. Not only are there different versions (02.18, 02.23, 03.15, .04.05, 05.02), but more importantly, there are different versions of the same version-number as well.
I downloaded three original ROMs from the thread here on XDA, all of them including the 04.05 baseband... and all the baseband-files were different.
As you know, if you're already on 0405 or higher, you can't upgrade through the LG update tool, as it claims you're already updated. So to make sure I had the latest "official" baseband I installed a 10a version (baseband 02.18). This allowed me to upgrade through the LG-tool. I still got an 0405-baseband, but... not had a single reboot since, and I've tried every ROM out there. (Am now back on stock waiting for CM7 to become polished.)
So to the ones out there who still suffer reboots, try to smartflash back to and old version, then upgrade via the LG-tool, it worked for me.
(This could of course be entirely coincidental, my phone may just have spontaneously "healed", but it's unlikely.)
::Trym
TrymHansen said:
I had a phone with the usual reboots and charge-bugs like everybody else. I shan't claim I've found a 100% solution, but what I can say is that my phone never reboots/bsods anymore, on stock ROM, MCR or CM7. It does get hot to the touch when it's working hard or charging, but still operates reliably.
There are several version of the basebands floating around. Not only are there different versions (02.18, 02.23, 03.15, .04.05, 05.02), but more importantly, there are different versions of the same version-number as well.
I downloaded three original ROMs from the thread here on XDA, all of them including the 04.05 baseband... and all the baseband-files were different.
As you know, if you're already on 0405 or higher, you can't upgrade through the LG update tool, as it claims you're already updated. So to make sure I had the latest "official" baseband I installed a 10a version (baseband 02.18). This allowed me to upgrade through the LG-tool. I still got an 0405-baseband, but... not had a single reboot since, and I've tried every ROM out there. (Am now back on stock waiting for CM7 to become polished.)
So to the ones out there who still suffer reboots, try to smartflash back to and old version, then upgrade via the LG-tool, it worked for me.
(This could of course be entirely coincidental, my phone may just have spontaneously "healed", but it's unlikely.)
::Trym
Click to expand...
Click to collapse
Thanks for reply dude.
But I've tried almost every version of baseband and rom already.
I'm from China, newest version of baseband I got is V10S, which is a Korean version, and the newest Chinese version is V10K. I have tried to flash the phone back to V10A - a European version ROM, and then update the phone using LG Mobile Update software to V10D, and this did no help to the issue.
As I said, this problem always happen when the temperature of the phone is high. I'm not sure whether the CPU/GPU temperature or the battery temperature will cause this issue (I prefer to believe it's because of the battery temperature, cuz the Google Map won't use too much CPU and GPU resource)
Another interesting thing I found, is that if I leave the music playing in background, then lock the screen, the phone will never meet any issue.
So now, my solution is to avoid the high temperature, or playing the music in background, muted, and then lock the screen. This may drain the battery faster, but at least I will never miss any call.
I have the 16GB Vodafone UK Galaxy S. Today I was in a city trying to use satnav and it was rank rotten. So I thought I'd see if an upgrade would do it. I was using the very first Froyo that Vodafone came out with - I upgraded to that and hadn't upgraded since. I did have it rooted and 1 click lag fix was on it.
I upgraded to Gingerbread just there, sadly I had to do a factory reset, however it's all working.
I have realised that if I am going to put a custom firmware on it then now is just the right time to do it.
Is there one out there that's stable, and an improvement over the Gingerbread I'm using? Particularly I'd like it to fix the lag (if that still needs fixed) and even better would be fixing GPS/Satnav.
Pinpong blockbuster rom - ticks all your boxes. Get faster fix from market.
Your gps will never be 100% satisfactory in the city, in fact it will probably always be poor - no matter what custom rom you use.
Halkus said:
I have the 16GB Vodafone UK Galaxy S. Today I was in a city trying to use satnav and it was rank rotten. So I thought I'd see if an upgrade would do it. I was using the very first Froyo that Vodafone came out with - I upgraded to that and hadn't upgraded since. I did have it rooted and 1 click lag fix was on it.
I upgraded to Gingerbread just there, sadly I had to do a factory reset, however it's all working.
I have realised that if I am going to put a custom firmware on it then now is just the right time to do it.
Is there one out there that's stable, and an improvement over the Gingerbread I'm using? Particularly I'd like it to fix the lag (if that still needs fixed) and even better would be fixing GPS/Satnav.
Click to expand...
Click to collapse
Have you think about CM7? Great Rom, works well on my phone, and add many new things.
Hi Mate, I tried many custom roms and finally settled for
(ROM)GingerCriskeloV77-9LS-CamHack- SIP + NoIncRing I9000/T/M JVP 2.3.4
Cheers
Well, I managed to get it on. Booting up is weird though, it looks for a long time as if the screen is broken, but eventually ti comes on to the Blockbuster lock screen and then everything is fine. It does seem faster - but I'll only really know when I get to one of those situations where I feel the phone is frustratingly slow.
Thanks very much Woolf!
Time allowing I'll give the other roms a shot, although this Blockbuster one does seem to be good enough for me.
Sadly my phone now reboots constantly. it seems to do it when the screen locks
Halkus said:
Sadly my phone now reboots constantly. it seems to do it when the screen locks
Click to expand...
Click to collapse
Check you got the installation right for that rom, maybe you had to flash a jvp stock first or some similar omission?
Sent from my GT-I9000 using XDA Premium App
Sorry to hear you're having issues. Try flashing to a totally stock JVQ first (with repartition) once you've backed up, then if you don't like that, try a custom ROM. I don't think many JVQ custom ROMs are worth trying if you want a taste of custom ROMs. Better to try CM7 or MIUI for something fast and different.
As a side note, the best tip I've seen for fixing the dreadful GPS we have with the i9000 is to buy a Nexus S or just ANY other phone! Yes, some radios appear better than others, but nobody can prove anything and it's almost all subjective feedback. A drop in the ocean of improvement needed for satisfactory function. If you must use it, a bluetooth GPS receiver and 3rd party navigation app seem the best way to deal with it.
I've now stepped away from Blockbuster. Even doing the a perfect install it crashed often and repeatedly. I did try upgrading to the very latest and that crashed several times in the past hour. Part of the problem was the rom starts with a lockscreen that has a messaging unlock on it, but it isn't set to an app that comes with the rom, so it reboots every time. Sadly that wasn't the only problem, as I was still getting loads of reboots.
So that's out of the way.
I'm now a lot more comfortable using Odin so I'll be able to try other options. I'll try the other two suggested in this thread first of all.
Next to test is CM7.
Thanks for the help folks!
CM7 aborted. Instructions are incorrect, the file they say to download doesn't actually match the instructions so that's out. Plus it clearly states it's not suitable for day to day use... so I don't thnk the time in working out how to fix it is justified since it looks like it wouldn't be useful.
I'm going back to the original question in the thread, to say that I'm looking for something stable. I now think that a custom rom is not the way to go. However some modifications may well be.
Can anyone suggest some kind of lagfix/speedup that isn't a complete overhaul like CM7, Blockbuster etc, that is very stable and that'll make my phone faster?
Edit : Part of what I was doing to install Blockbuster was install Speedmod kernel. So I've gone and put that on, and used the clockwork mod to root it, and also convert to ext4. I think things are looking pretty fast so far. I'm not sure if there's a lagfix for this, but I'm quite comfortable just now footering around - unlike the complete rom I don't feel out of my depth. So I think I'll be ok for now.
Hello all,
I've recently purchased a Galaxy Tab 8.9 and of course after a day or two with a stock ROM, I was looking to install a custom ROM to get a better overall experience.
Unfortunately, with every custom ROM I've tried, I get this weird display artifact (see video below). It starts when the bootloader switched over to the boot animation. The artifact will continue after the OS is loaded up and on the lock-screen. If the display is turned off manually or due to time-out and then turned back on, everything is fine. It's doesn't seem to affect functionality at all, it's just really annoying.
It's happened with CM9, Galaxian Soup AOSP, Galaxian Soup AOKP, Overcome 8.9, and AOKP b29-31. When I restore my nandroid backup, it works fine, so I don't think it's a hardware issue, but it's really annoying.
Broken up URL is below (still a newb), please let me know if anyone else has this issue and/or knows what may cause it or fix it.
http: //youtu.be /Xt2OPfy4TOU
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to General
Nobody has seen anything similar?
That unfortunately is a hardware issue. You need to replace the unit :-(
Thanks for the reply, but wouldn't a hardware issue be present with the stock OS as well?
It really depends on what registry is being touched by the custom rom. It looks like the vertical synchronisation of the screen is being screwed up somehow. If this effect is seen only in your device it must mean that something is fishy with a hardware part of the screen controller and the sync if being affected by a value written in some other part of the control registries. I have no idea how I could express this clearer.
That's awkward to be honest. I haven't seen anything like it in my 7310, be it with Stock, or any other custom ROMs I've tried (from the old AOSP Galaxian Soup alphas to the current beta and the old versions of Overcome too). Do you completely wipe your device before flashing any custom ROM?
I did completely wipe data/cache/dalvik before every ROM install.
Unfortunately, I don't know how I'd return it, since the error is only apparent when a custom ROM is installed.
jhhoffma said:
Hello all,
I've recently purchased a Galaxy Tab 8.9 and of course after a day or two with a stock ROM, I was looking to install a custom ROM to get a better overall experience.
Unfortunately, with every custom ROM I've tried, I get this weird display artifact (see video below). It starts when the bootloader switched over to the boot animation. The artifact will continue after the OS is loaded up and on the lock-screen. If the display is turned off manually or due to time-out and then turned back on, everything is fine. It's doesn't seem to affect functionality at all, it's just really annoying.
It's happened with CM9, Galaxian Soup AOSP, Galaxian Soup AOKP, Overcome 8.9, and AOKP b29-31. When I restore my nandroid backup, it works fine, so I don't think it's a hardware issue, but it's really annoying.
Broken up URL is below (still a newb), please let me know if anyone else has this issue and/or knows what may cause it or fix it.
http: //youtu.be /Xt2OPfy4TOU
Click to expand...
Click to collapse
i got the same issue, how did you resolve it?
thanks
I've tried searching other threads/posts but I don't see any solutions at all. I want to first rule out the problem being with the software before I send my Nexus One to a mobile phone technician for hardware repair.
Here's the situation. I got my Nexus One used, at very cheap price but with slight defect that the seller kindly informed me about. The brightness control is not working. He said that it started happening after installing CyanogenMod7 from stock rom.
I still purchased it from him and now it's my problem. I tried looking for solutions. Here's what I did so far:
reset the phone, including formatting the sdcard
installing 3rd party brightness controllers
reinstalling CyanogenMod7 and even used CM6, I've also used nightly and RC CM7
trying other roms (those that do not require modifying hboot [blackrose])
Having said the last item, that is something I have yet to try and really giving it a good thought before finally trying because of some cautions regarding Nexus One having SLCD as indicated by MICROP 0c15.
One thing to consider as well, whenever I run the stock clock app and press the brightness icon, the backlight does get dim so I'm thinking that the brightness can still be controlled.
Any ideas, guys?
Btw, as you can see, this is my first post. Apparently, I cannot find the solution myself so I had to ask.
Thank you in advance.
I have the same issue on both stock rom and the great CM7, Im hoping there is a fix for this.
It seems that only very few experienced this problem and the fact that there aren't any helpful reply means that there is no solution for this issue yet.
I really don't want to believe that this is a hardware failure, though.
dojavanese said:
It seems that only very few experienced this problem and the fact that there aren't any helpful reply means that there is no solution for this issue yet.
I really don't want to believe that this is a hardware failure, though.
Click to expand...
Click to collapse
try screen filter app from play store ..
I've tried using screen filter app and it was able to control the brightness but only to lower it.
Compared to other android phones, the brightness on my nexus one is definitely not on it's highest setting even if the screen filter app says it's on 100%.
It's like it's on 50% brightness.
Could the hboot have something to with this? I'm using 0.35.0017.
Having SLCD on it prevents me from fooling around with hboot flashing.
Any other ideas, guys?
Same problem
i on slim rom 4.3.1 on my LG P990, before the hard reset evrything was fine..n after that brightness controll dailed..
i guess ill have to Hard Reset again
but i dont wnat to..
so i guess lets just stick with it..
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.