The other day I updated my phone to 2.3.4 using odin. after that I had a horrible wifi signal and i kept losing my data connection all together. So I flashed back to Froyo 2.2.1. I am so confused because my phone kept force closing, I did a factory reset and it stopped but it says my kernal version is 2.6.32.9...is that normal? Also how do I go about flashing a good rom to my phone? The way it is now it is soooo slow which is why i updated to the 2.3.4...any information would be helpful as I am ready to throw my phone out the window.
pammiecaykz said:
The other day I updated my phone to 2.3.4 using odin. after that I had a horrible wifi signal and i kept losing my data connection all together. So I flashed back to Froyo 2.2.1. I am so confused because my phone kept force closing, I did a factory reset and it stopped but it says my kernal version is 2.6.32.9...is that normal? Also how do I go about flashing a good rom to my phone? The way it is now it is soooo slow which is why i updated to the 2.3.4...any information would be helpful as I am ready to throw my phone out the window.
Click to expand...
Click to collapse
Which 2.3.4 ROM did you flash via ODIN? KG4/KG6 both show less wifi signal but I actually haven't seen a difference in speed. I'm on this one right now:
[ROM] Stock Deodexed T959VUVKG4 with Root [Gingerbread 2.3.4][7.26.2011]--Whitehawkx
http://forum.xda-developers.com/showthread.php?t=1187293
The way to properly get to that is by doing the following:
1. ODIN
[ROM-Leak][ODIN] Gingerbread 2.3.4 T959VUVKG4
http://forum.xda-developers.com/showthread.php?t=1183413
2. Then boot up like normal and wait for it to load up into the system.
3. Turn off your phone again (shutdown) and put it back into download mode.
4. ODIN this to get CWM+Root http://forum.xda-developers.com/showthread.php?t=1194032 (use the ODIN version)
5. Keep lagfix disabled via the voodoo menu in recovery after you flash the CWM+root+Voodoo EXT4 package in the link in step 4.
6. Boot into the system. It's up to you, I flashed this
[ROM] Stock Deodexed T959VUVKG4 with Root [Gingerbread 2.3.4][7.26.2011]--Whitehawkx
http://forum.xda-developers.com/showthread.php?t=1187293
Which is a deodexed build which allows you to theme etc.
Some people have had issues getting onto EXT4 partitions while on a gingerbread ROM. I had a few issues myself. Needless to say there are several places to read about how to get EXT4 working on all partitions if you want to.
Best of luck, hope this helps.
Well to be completely honest, I don't know anything about partitions. All I know is that I updated my phone and then all of a sudden I had a horrible wifi connection and my data connection would just drop out all together and say "searching". I would have to reboot my phone 2 or 3 times to get it working again. What is a good rom to update to? Is have the kernal build that I do going to be an issue?
pammiecaykz said:
Well to be completely honest, I don't know anything about partitions. All I know is that I updated my phone and then all of a sudden I had a horrible wifi connection and my data connection would just drop out all together and say "searching". I would have to reboot my phone 2 or 3 times to get it working again. What is a good rom to update to? Is have the kernal build that I do going to be an issue?
Click to expand...
Click to collapse
Please read the post above and follow the steps and links and you will be fine
Ok so for the last few months, I have been switching between roms, looking for something with good battery life.
Every rom i tried, the battery life often was awful (10-12 hours light use) until pinnacle came around. With pinnacle, the standby drain was around 1% per hour, and it just kicked ass.
After pinnacle i went and tried cyanogenmod again, and to my dismay, the battery life still sucked. So back to pinnacle i went.
Then someone said to me that i dont have to go through all the hassle of flashing back to jf6 and having old bootloaders and all that crap was unnecessary, so i decided to see if i got better results in CM coming from pinnacle.
Well IT WORKED!!!!!!!!!!!! Battery life is on par with pinnacle as far as i can tell.
My previous method was:
flash back to jf6 via one click odin
root phone and install rom manager
install cwm for captivate
then choose mtd 2xx
then boot into recovery
wipe data, cache, and dalvik cache
install cm7 zip and gapps zip
My new method:
follow pinnacles instructions to install pinnacle
boot into recovery
wipe data, cache, dalvik cache, battery stats
install cm7 and gapps
So my possible conclusions are:
-That one click jf6 package sucks, theres no reason to every flash back to it. I plan on finding a different one click if i ever need to flash back to stock. Ill probably use a 2.2 or 2.3 one click
-CM is not completely wiping everything when it installs, and somehow performs better when coming from a gingerbread rom, than coming from eclair.
-I have wiped the battery stats in the past, but maybe doing it right away helps?
-cm7 build 181 is wayyy better than 179 - (not likely)
Not sure what else it could be. The same apps are always installed. I tried both the stock kernel and glitch v12 last time and both had bad results. This time im using stock with great results, and i havent had the urge to switch, because i dont wanna mess it up.
Hopefully this helped someone, or at least shed some more light on way some people get terrible battery life with some roms. I bet using this same method, I would get better results with roms I've tried in the past (APEX, MIUI, any other i9000 based roms)
They should really change the directions to CM if this is the case. Maybe this isnt the best for everyone, but the gingerbread bootloaders that come with pinnacle seem to work fine with CM, so why make people waste their time.
Under what usage conditions are you getting 1%/hr?
With data and wifi off I get about 1%/hr
all on 10%/hr
The big battery killer for me seems to be when the phone is searching for data signal. I had my phone at a customer site with no AT&T 3G coverage and no wifi to tap into. My drain was about 22% an hour. I almost crapped my pants when I checked the time about two hours into my day and I was at 55% (first time I looked at the phone in two hours).
When I get to work, if I forget to connect to wifi, I get around 10% per hour drain because the 3G signal in my building isn't that great. That's with minimal use.
If I get to work and connect to wifi, my battery drain is about 5% an hour with minimal use.
lourivellini said:
Ok so for the last few months, I have been switching between roms, looking for something with good battery life.
Every rom i tried, the battery life often was awful (10-12 hours light use) until pinnacle came around. With pinnacle, the standby drain was around 1% per hour, and it just kicked ass.
After pinnacle i went and tried cyanogenmod again, and to my dismay, the battery life still sucked. So back to pinnacle i went.
Then someone said to me that i dont have to go through all the hassle of flashing back to jf6 and having old bootloaders and all that crap was unnecessary, so i decided to see if i got better results in CM coming from pinnacle.
Well IT WORKED!!!!!!!!!!!! Battery life is on par with pinnacle as far as i can tell.
My previous method was:
flash back to jf6 via one click odin
root phone and install rom manager
install cwm for captivate
then choose mtd 2xx
then boot into recovery
wipe data, cache, and dalvik cache
install cm7 zip and gapps zip
My new method:
follow pinnacles instructions to install pinnacle
boot into recovery
wipe data, cache, dalvik cache, battery stats
install cm7 and gapps
So my possible conclusions are:
-That one click jf6 package sucks, theres no reason to every flash back to it. I plan on finding a different one click if i ever need to flash back to stock. Ill probably use a 2.2 or 2.3 one click
-CM is not completely wiping everything when it installs, and somehow performs better when coming from a gingerbread rom, than coming from eclair.
-I have wiped the battery stats in the past, but maybe doing it right away helps?
-cm7 build 181 is wayyy better than 179 - (not likely)
Not sure what else it could be. The same apps are always installed. I tried both the stock kernel and glitch v12 last time and both had bad results. This time im using stock with great results, and i havent had the urge to switch, because i dont wanna mess it up.
Hopefully this helped someone, or at least shed some more light on way some people get terrible battery life with some roms. I bet using this same method, I would get better results with roms I've tried in the past (APEX, MIUI, any other i9000 based roms)
They should really change the directions to CM if this is the case. Maybe this isnt the best for everyone, but the gingerbread bootloaders that come with pinnacle seem to work fine with CM, so why make people waste their time.
Click to expand...
Click to collapse
That´s great news!
Wich Pinnacle version were you in before flashing CM7?
minduka said:
Under what usage conditions are you getting 1%/hr?
With data and wifi off I get about 1%/hr
all on 10%/hr
Click to expand...
Click to collapse
everything on connected to wifi. I will post screenshots when i get home. I dont install too many apps, but i use facebook, twitter, beautiful widgets, and doggcatcher - which are apps that may possibly run in the background.
10 percent seems like a lot.
KreepyKen said:
The big battery killer for me seems to be when the phone is searching for data signal. I had my phone at a customer site with no AT&T 3G coverage and no wifi to tap into. My drain was about 22% an hour. I almost crapped my pants when I checked the time about two hours into my day and I was at 55% (first time I looked at the phone in two hours).
When I get to work, if I forget to connect to wifi, I get around 10% per hour drain because the 3G signal in my building isn't that great. That's with minimal use.
If I get to work and connect to wifi, my battery drain is about 5% an hour with minimal use.
Click to expand...
Click to collapse
yea i would definitely try reflashing. Try my method, and let me know if you get better results with that. Mine has been worse in the past, but never that bad.
alecao said:
That´s great news!
Wich Pinnacle version were you in before flashing CM7?
Click to expand...
Click to collapse
I was running pinnacle 1.2. I never felt the need to update to 1.3, and didnt want to risk it with the results i was getting.
Anyone who thinks the captivate sucks on battery should definitely try out pinnacle. And from there try out cyanogen again.
Hmm... I'll have to try that. I've been getting pretty terrible battery life with just about everything recently. Thanks for the tip.
Mr. Dr. Prof. Sean said:
Hmm... I'll have to try that. I've been getting pretty terrible battery life with just about everything recently. Thanks for the tip.
Click to expand...
Click to collapse
yea please try it and do exactly the same thing as i did. I would like to see if people get the same results as i did.
What ROM you're on before a flash does not matter. The script completely wipes the OS before the flash. So either way it's writing to an empty partition...
The only difference between both methods is the bootloaders, which may or may not be the reason for the results you're seeing.
studacris said:
What ROM you're on before a flash does not matter. The script completely wipes the OS before the flash. So either way it's writing to an empty partition...
Click to expand...
Click to collapse
thats exactly what i thought, so why should it even matter if i was on stock jf6 or not? (like it says in the instructions)
Somehow it is affecting it though, and i definitely have experienced better results. If i get a chance i will try flashing back to jf6 and doing it that way, and then doing it my way again. But im just listing what i did, and what my results were.
Thats why i was asking if it made sense.
Isolate the variables and test them individually. Like I said, the only difference is the bootloaders...so when you flash cm7 from jf6 again after you find out what the drain is like, flash JUST the gingerbread bootloaders while still running cm7 and see if it changes...
Jf6 one click doesnt suck, its just pointless and potentially harmful now.
I have been using uckf1 /w pit file to flash back to "stock" (if i need to repartition) but i removed the bootloaders from the package to avoid cataclysmic destruction.
Generally you don't need to flash back to stock at all anymore because most ROM's are full wipe.
studacris said:
Isolate the variables and test them individually. Like I said, the only difference is the bootloaders...so when you flash cm7 from jf6 again after you find out what the drain is like, flash JUST the gingerbread bootloaders while still running cm7 and see if it changes...
Click to expand...
Click to collapse
will try it out probably this weekend.
Question though: Should i just flash the gingerbread bootloader included in the pinnacle install, and then never touch the bootloader again? Ive heard the 2.3 bootloaders work universally, and that its a bad idea to flash bootloaders.
I used to always use the odin one click to jf6 whenever i would change roms. From now on i may use the 2.2 hemidall package i found. The only problem i see with that is it doesnt delete the data partition, and i think the last time i used it, it didnt delete apps i had installed, and i had force closes that made my phone unusable.
Why is flashing a rom on a phone more difficult than installing a OS on a computer.
Basically, i just want to completely format and do a fresh install everytime i put a new rom on. I dont see why things like data and cache arent wiped by default.
I personally like the odin one-clicks that end up erasing EVERYTHING and changes it exactly how it should be. Why are more roms available as odin one-click?
You only need Odin or heimdall as a recovery option from a soft brick, or to go back to a touch wiz based ROM from an aosp ROM (cm7/miui) as you need to repartition.
Just flash the Ginger boots and leave them alone, corrupted bootloaders from a bad flash is the only way to hard brick, so to minimize that risk flash bootloaders as minimally as possible (I only suggested that earlier as a suggestion for to to figure out if that was what helped), unless you have done the unbrickable mod then by all means flash your boot loading butt off with no worries.
So if you are on a touch wiz ROM, I897 or I9000 all you should have to do to is just flash over it. And if that goes sour and you can't boot back into cwm then, and only then, should you resort to Odin.
Think about it, if a ROM can flash over a stock ROM what is different about flashing over a custom ROM? Nothing.
If you want to make extra extra sure it's a "clean flash" you can wipe data/factory reset, wipe cache and dalvik cache and then flash, but the ROM should do that.
studacris said:
You only need Odin or heimdall as a recovery option from a soft brick, or to go back to a touch wiz based ROM from an aosp ROM (cm7/miui) as you need to repartition.
Just flash the Ginger boots and leave them alone, corrupted bootloaders from a bad flash is the only way to hard brick, so to minimize that risk flash bootloaders as minimally as possible (I only suggested that earlier as a suggestion for to to figure out if that was what helped), unless you have done the unbrickable mod then by all means flash your boot loading butt off with no worries.
So if you are on a touch wiz ROM, I897 or I9000 all you should have to do to is just flash over it. And if that goes sour and you can't boot back into cwm then, and only then, should you resort to Odin.
Think about it, if a ROM can flash over a stock ROM what is different about flashing over a custom ROM? Nothing.
If you want to make extra extra sure it's a "clean flash" you can wipe data/factory reset, wipe cache and dalvik cache and then flash, but the ROM should do that.
Click to expand...
Click to collapse
So if i decide to go back to pinnacle - i shouldnt one click jf6? But i at least need to hemidall - which doesnt flash bootloaders. And going from cm, i really dont even have to go back to jf6, i should probably at least go to one of the newer stock froyo roms.
Or even better - i should flash to a rom through odin that is already rooted and has cwm installed, so when i flash to a new rom, i dont have to manually root, and then install rom manager/cwm everytime. Right?
There are Odin packages without bootloaders...and heimdall ones with them.
Yes from cm7 you need to use Odin/heimdall. If using a non 1 click Odin you must place a .pit in the pit slot and a .tar in the pda. Which ever you use is up to you.
Serenity 6.1 seems to have a long life, contrasting with OR5 or Continuum6.2.1
Are you using the same modem that comes with CM7 (JL3) or did you flashed another one?
alecao said:
Are you using the same modem that comes with CM7 (JL3) or did you flashed another one?
Click to expand...
Click to collapse
Everything stock.
Sent from my SGH-I777 using Tapatalk
hie frndz....
i hve a nexus s i9023( from india) purchased back in august.... everything was going well before i got an official ics update.... in december i got ics update and thts the day the problem started.
before the update i used to get up to 24 hrs of battery backup..but nw i just get max of 12 or 13 hrs....
and the phone performance is also reduced nw.... the phone works a lott slow than before...
many apps are not working... even the gmail app has stopped working.. everytym i open it, the msg comes "unfortunately gmail has stopped working"..
is thre anyone who is facing problemsss....
should i downgrade back to gingerbread or wait for google to fix it??
plzz help me.... suggestions are always welcome....
flash aosp v3 codename it has very good battery life i get 20 - 24 hours battery per charge
dessi_007 said:
flash aosp v3 codename it has very good battery life i get 20 - 24 hours battery per charge
Click to expand...
Click to collapse
does it require rooting???
Do you have a lot of apps and don't wanna lose the settings?
if not or if you don't care about setting them up again why not do a factory data reset and just erase everything and start from scratch?
i would suggest a you make a backup first but you're probably not rooted and even if you do, the backup might not work since it might also back up any wrong settings or something like that (i might be wrong here)
Why not root your phone? you can always unroot and relock the bootloader if you are worried about warranty.
edit: BTW any custom ROM requires you unlock your bootloader and install ClockworkMod recovery. so you would have to do that first in order to flash the AOSP roms.
but what abt the battery issue...
it is the main problem of all...
sbandaly said:
but what abt the battery issue...
it is the main problem of all...
Click to expand...
Click to collapse
Have you looked at the battery usage under system settings > battery?
it likely is be a misbehaving app since you say several apps don't work correctly.
this should also go away with a flash of a ROM or doing the factory data reset.
Edit:
My wife has having similar problems after the ICS OTA update. she had a lot of apps and a bunch of widgets on the home screens, the phone was sluggish and some apps didn't work right or were FC'ing. In the end she just did a factory data reset and started from scratch and the phone is stable and feels faster and all apps are working fine now.
i rooted my nexus s ystrday with cwm5.0.2... vl it b enough to save my battery or shall i flash roms..
i dnt knw how to flash roms.. so plzzz tell me how to do tht
dessi_007 said:
flash aosp v3 codename it has very good battery life i get 20 - 24 hours battery per charge
Click to expand...
Click to collapse
is it a kernel or a rom...
and i saw the screenshots of this rom- CodenameDroid-(MOD)-1.2.0-NS
is this rom a good one....with faster performance and a good battery
tried ICS stock rom.
No battery problem. similar life compared with 2.3: about 1.5 days
but ICS is running slower than 2.3. Though speed still acceptable, but I want the 2.3 speed
@colocynth
Try the Matr1x Kernel und you will be fine....
Hi cloedu, I tried mv 2.1.28, using matrix kernel, if my memory is correct. Still not speed up, just like stock.
Sent from my Nexus S using XDA App
Formatting everything (system , boot , cache , data .....) in CWM recovery , then reinstalling stock ICS ROM made a day and night difference in battery life for me .... From 15 hours avarage to almost 1.5+ days ... Highly recommended...
sbandaly said:
is it a kernel or a rom...
and i saw the screenshots of this rom- CodenameDroid-(MOD)-1.2.0-NS
is this rom a good one....with faster performance and a good battery
Click to expand...
Click to collapse
yes it ia with the matrix rom
hello, i have uploaded my rom to ICS and have it been using for the past 4 months
last week i came in to the issue of the battery status being unknown, 999% or 1000% battery power
i've fixed this issue in the past by flashing the rom
but this time i have trouble, it seems that ever time now that the phone is powered off and powered back on the battery status returns to 999%
i have uploaded the rom egb-nightly-2012-07-01-signed on my phone and no matter how many times i flash the battery status is lost
so i am here wondering if there is a simple fix to this, downloading a apk file or anther way to configure the phone so it will read my battery status or do i have to simply buy a new battery?
please help and thank you in advance
You sure you did the flash right?
Sent from my G2X using EaglesBlood build 5
Did you reset batt stats in recovery?
Also when this did happen to me, i was always told to just cycle AP mode, and it did work.
Yours seems more persistant though.
I would make sure batt is fully charged (charge it with phone off if your that unsure) and than first boot goto cwm and clear batt stats.
Sent via G2x on temasek CM7 b135.2, Trinity TD158 kernel on xda premium
TMK216 said:
You sure you did the flash right?
Sent from my G2X using EaglesBlood build 5
Click to expand...
Click to collapse
ok im flashing right now as we speak, this is what i am doing
wiped data/factroy reset - Done
wipe cache partition - Done
wipe dalvike cache - Done
and this time im also wiping battery stats - Done
installing egb-nightly-2012-07-01.zip - Done
wiped again in rom install file
installing gapps-ics-20120420=signed.zip - Done
phones first boot----battery status set 100%
unplugging phone now and rebooting - battery still reading 100%
reboot #2 - battery reading 100%
reboot #3 - battery reading 100% problem maybe fixed
if issue continue i will carry on with this forum
i seem to be having trouble with the quick reboot now... seems to be just powering down my phone....
I've had trouble with the reboot before in eaglesblood and to be frank I think its normal to some degree for most roms. As for the battery problem I've noticed in my experiences that if something like that were to occur it usually dealt with my kernel but I mostly run 7.2 and not ICS so there maybe some differences here.
deathmaker06 said:
I've had trouble with the reboot before in eaglesblood and to be frank I think its normal to some degree for most roms. As for the battery problem I've noticed in my experiences that if something like that were to occur it usually dealt with my kernel but I mostly run 7.2 and not ICS so there maybe some differences here.
Click to expand...
Click to collapse
thank you for the response
last night i modded the dpi and installed the market mods and rebooted the phone and the phone battery info crashed again...
anyways today i flashed my phone loaded a older version of ICS, reboot my device and the battery status is still working after i changed my dpi, for some reason i feel the issue is fixed now but i will post in the future if this issue carries on
thank you
ok i was updating framework animations and yet my battery went back to 999%... WTF
why is it doing this?
ive never had so much trouble with my phone
what am i doing to the phone that it makes it do this
i ask again could this be just battery issues?
I had a lot of issues with the phone reboot myself. That sounds crazy. My only issue I had was the date and time would not sync off my Sim card. Seems like a lot of people don't like the eb rom and I don't know why cuz I love it.
Sent from my G2X using EaglesBlood build 5
The battery shows you 999%?, maybe a baseband problem...
but like iron man would say... 999%??? cool....