Hello,
I am using a Non rooted Rogers canada samsung captivate.
I recently upgraded through KIES to Froyo.
The two issues I am having are:
1) Wifi, i use juice defendor, so when i enter my house wifi is enabled automatically, many times, there is an error, and i cant click wifi on until a reboot, then it works fine for a while until it will happen again.
2) The notification bar doesn't slide down at times, and the only way to fix this is by rebooting. These two things are very annoying as they happen on a daily basis, or every other day.
I have seen these issues happen to others, so I know im not the only one, but I cant find a solution anywhere.
Any help would be appreciated.
anything i can do? would a factory reset help and a full reinstall?
Bigal77 said:
anything i can do? would a factory reset help and a full reinstall?
Click to expand...
Click to collapse
It might but to be honest I have never seen a stock rom that is not buggier then any custom rom i have run. What you could try is start from scratch and see if the prob happens on an out of the box set up. If it does then it is an issue with the rom, if not then install your apps one by one to see if one of them is covering it. My advice? Grab one of the custom roms build from the Rogers 2.2 update like Cog or Firefly.
Try uninstalling juice defender.
I had the same problem with notification panel not sliding down after installing juice defender. I uninstalled it and the problem went away.
Did you solve the problem with the notification dropdown? Was it Juice Defender? I am experiencing the same issue.
I have problem number 2 too. No juice defender or any power saving tool or what not running in the background. Happens only once in a while although so its not killing me
Same problem here. I can't pin it to a specific program. But I think it has something to do with a certain notification because it always does it when I download a program or install a new program.
I've experienced both but after OCLF (which requires root) the notification bar issue doesn't happen. I've recently moved on to a stock kernel injected with voodoo lagfix (courtesy of supercurio) after having tried speedmod which gave me horrible battery life.
My battery life is good enough that I just leave wifi on all the time to avoid issue #1. When the wifi issue happened, going to airplane mode and back would fix it too without a full reboot.
k the best thing to do in your situation as people new to xda is if you are unrooted and want to stay that way go into the rogers store and say your touchscreen is buggy which to me seems like the issue you are having. also if your on the stock rogers 2.2 as i was for a coupple months all i can tell you is that its super buggy (as you could probobly tell from that terror they called an install). if your confident and want to get your feet wet with a great custom rom i would go with firefly that should fix any issues you have its a fuly stable final release and best part its based on rogers software not at&t so it will work flawlessly with the network and most likley fix any problems you are having
Don't use 100% pure stock
Use tweaked - with EXT4 LagFix, OC/UV, Sideloading enabled, rooted, VoodooSound, with GPS fixes.
Older Cognition 3.4 was Rogers based - I can recommend that.
Related
I am getting random reboots and I am unable to figure out what is causing the problem and I have not found any thread about random reboots with the Captivate.
haojan said:
I am getting random reboots and I am unable to figure out what is causing the problem and I have not found any thread about random reboots with the Captivate.
Click to expand...
Click to collapse
Provide us with more information. Is your phone rooted, on a custom ROM maybe, what have you been doing to your phone, when did this start happening, etc.
History
I started with stock, rooted, non-market apps, unhelpful kernel v1.2, removed AT&T bloatware. LCD density @ 180. Tried One Click Lag Fix v1.0 and v2.2 and uninstalled. Juice Defender to manage 3G. Juice Plotter to track battery.
After messing around with it, I encountered a reset of the default launcher selection each time I long pressed the home button to bring up the recently used programs. I then did a hard reset and that fixed that problem. After the hard reset, my Captivate ran great! I found it responsive and fast enough without the need to try and apply any lagfix.
I then reinstalled my selected applications. My phone started to randomly reboot about once a day. I noticed Juice Plotter's data would be lost and it had to rebuild. It also happened to reboot on me once while I was using it. Other than that, it has not really affected my usability.
If it hasn't affected your usability, do you want to fix it?
If you do want to fix it, then the best way is to restore to Stock and add things slowly until you determine the problem. If you return to Stock and it still reboots, then you have a hardware issue.
It doesn't "quite" affect usability but it is not working "normally" either.
Was hoping to see if anyone else have experienced random reboots and how to troubleshoot it. If not, I will try out Odin one-click flash to stock...
Hi, I've rooted my mesmerize with z4root and have installed a couple root apps. One being ROM Manager, which I flashed clockworkmod for fascinate.
Now sometimes my screen just freezes, and when I try to the screen off, then on. It doesn't turn back on. It's still actually on because I was listening to music, and the music kept playing. Anyone know how I can fix this?
Might be a hardware issue (but I doubt it).. some people have been reporting screen trouble. If you want to be 100% sure it's not software then use Odin v3 to get it back to stock and then see if the problem persists. It shouldn't be software though. My phone is working fine and I have both those "apps".. If it does continue just take it back to the store and they should swap it for you (if you can get it to do that for them). However, they'll probably just do a factory reset first. So, in general, I always make sure I can get a problem to happen when I'm on a factory reset device running a stock rom and kernel before I take it into the store.
Also, does this happen often? Or has it just happened once or twice. Now that I think about it I may recall having to pull my batter a few times because it was frozen.. but that was back when I was on the stock ROM and kernel.
Perhaps you might want to try the Voodoo lagfix kernel. It may be a combination of the buggy/slow RFS and frequent use..
dcow90 is right, how often do you reboot the phone within a weeks use?
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Sounds like a warranty replavement to me.
Caution swyping! Read at your own risk.
TheSopranos16 said:
I've been having a weird issue for the past few weeks where my phone will lock up and the screen won't turn on anymore. Often, it happens with the phone in standby in my pocket. I'll feel a vibration (sometimes just 1 vibration, sometimes followed by the usual 3 fast vibrations of a force close) and then the phone is gone. I have to hold all 3 buttons to reset it and then it boots up fine like nothing is wrong. I've had this same issue on various roms I've used lately (Serendipity, Firefly, Cog4, etc.) and on my last flash I've even done the full flash to stock and master clear. Is anyone else having any issues like this?
I'm guessing this is 1 of 3 things:
1) I have a hardware problem with my phone and need a new one.
2) This is an issue with custom kernels with lagfix and I have to live with it or use a stock kernel. I know some custom kernels have had charging death issues (I've seen that happen to me also but idk if its from charging or the same thing as when its in my pocket)
3) Some app I installed is causing this. I have a hard time believing this can be the problem only because any app issues I've seen in the past just show up as a FC and don't take out the entire phone. If this is in fact an app issue, IDK how I'll ever figure out which one is causing it since it just dies and I don't get a chance to see a FC message or anything like that.
Any thoughts or suggestions are appreciated as I really don't know what to do at this point. My next step is probably going to run pure stock froyo for a few days to see if I still have the issue but I suspect I will since its been present on every rom config I've used. Whats even worse is, if it happens and I don't notice for a while, when I finally reboot it the battery is severely drained. Its like something gets in an infinite loop and kills the battery depending on how long I leave it like that (the phone also warms up when its been in this state for a while).
Thanks in advance for any help!
Click to expand...
Click to collapse
What kernel are you running? And are you OC/UV?
If so, try a different kernel (like speedmod k13e) that doesn't have OC/UV option. Black screen is usually a UV setting problem.
If it's not the case, warranty?
EDIT: Have you flashed over different ROM with lagfix/ OC/UV enabled?
Right now I'm running lastest Cog 4 with the included kernel (which doesn't support UV). I was OC but once I had this issue I reset the clocks to stock but then it happened again. Before I installed Cog 4 I flashed stock and master cleared...
1. Did u restore any data using TiBu when u flashed the ROM? Did u happen to restore any system data?
2. Did u put on any kind of under volting?
Flash any ROM, say Firefly, and use it for a day or two without restoring any of ur apps, and see if the issue is coming up again.
If yes, try changing kernel, say to onix, and keep on for a day or two see if the issue is recurring.
Just to be sure, can u do this:
1. Revert to stock
2. Format internal SD (similar to master clear to clear out SD card; I never did a master clear so far, only this)
3. Copy the ROM u want to use to SD
4. Flash Firefly 3.0 (this formats all system partitions, so no need to master clear)
Firefly has hardcore's kernel by default, and this kernel does not apply lagfix by default. Same with onix kernel too, and this is the reason I am recommending this combination of ROM and kernels. I use onix cos I have some wifi issues on hardcore's kernel.
5. Do NOT restore of ur data or apps
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
TheSopranos16 said:
I did restore data using TiBu but only app data. The only system stuff I restored was bluetooth pairings and wifi access points. Other than that only app data. I don't have any UV right now...
Click to expand...
Click to collapse
I would NOT recommend ANY system data, except for contacts storage. This is the only one system data I personally found not to cause any issues.
Its easier to connect BT and wifi again, than go through the pain restoring this data sometimes creates. I faced issues with my phone not being paired to my car when I tried to restore bluetooth settings. It shows my car, but doesn't pair. I had to restart phone, delete the connection, and then reconnect. I found it easier to add back, than restore and go through all this trouble.
This time, pls try to refrain from restoring any of ur data from TiBu and a day's run for the ROM and see how it goes. If it goes well, u can restore data. But, before u restore data, I would recommend taking a nandroid backup just in case restoring apps starts creating issues again. This could save some time by getting u back to current state with no apps, instead of flashing all over again.
Before doing any of those things, I would check out your IMEI number and compare it to the one in this link,
http://www.captivateforums.com/sams...random-shutdown-issues-on-att-captivate-1272/
I dont pay for any warranty through AT&T, but I brought my phone in to a device replacement center and they replaced mine with a brand new phone!
Its worth a shot if you ask me.
So, I am pretty new to this whole flashing/rooting thing and I apologize if I have already made a stupid mistake. I have tried to read and understand everything thoroughly, but I am not a terribly smart person
Anyways:
I had a stock Infuse with Froyo and used the Heimdall One Click Return to Stock 2.3.6 and everything seemed to have gone over pretty well, but I keep getting force closes for random things, and I can't even open half of my apps. I click on them, they just sit there and hang, then force close. I tried to update them all in the marketplace, but still, nothing.
Also, when typing in landscape mode, sometimes the delete key seems to hang a bit or won't do it at all.
I tried searching around and found no answers, so if anyone has one, please let me know!! Thank you
Other than the force closes and mild delete issue, everything on that rom has been wonderful!
One final question: This isn't a problem, but I was under the impression that 2.3.6 would allow you to change texting layouts or colors? I tried sifting through most menus that I could think of, but can't find an option. Am I just missing something or is it not included in Gingerbread?
Actually...it seems like my battery life is shot, as well.
About 2 hours ago, my battery was at 100 from charging. I unplugged it and sent 3 text messages and nothing else. I even used the task manager to close any open apps after, but now I'm at 90 percent battery. Before the update, my phone could easily last 48 hours or so without a charge if I used it very little.
I was curious if there is a setting or something I am missing somewhere that is causing the battery drain? I know that sometimes when you root it, you have the option to change what speed the cpu is at, and it will drain your battery quicker.
Could that be the issue?
I am sorry for all of the questions, I'd just like to figure this out so that I don't have to factory reset it and go back to froyo :/
Have you tried doing a factory reset from the settings menu may help with force closes and crappy battery be warned you will lose everything on your sd card when you factory reset may want to take out your external or back everything up on your computer
After every new rom flash and re-sync, I think there is an intense demand and cpu and regeneration of background cache and data builds.
This would seem like a battery drain. In most instances, battery life will even out over several cycles. - Assuming that the settings on the custom rom is placed properly.
I have seem some bad tweak settings when I have looked over many claimed tweaks to save battery when they do the exact opposites.
Pure Stock rom have many monitoring crap and background running apps collecting data that it will take up a lot of battery from just sitting.
I don't know which stock package you've used or which heimdall version or if you ran the heimdall frontend on the leaks.
If flashed properly with re-partition using the 1click adam outler created for the uckj4 and my uclb3, there should be no FC's.
It should be pure stock with everything working "perfectly" as intended by AT&T.
rooting only gives you access to your phone..it has no bearing on battery.
Overclocking - OC - may increase battery consumption/ Running stock - should not be an issue.
qkster said:
After every new rom flash and re-sync, I think there is an intense demand and cpu and regeneration of background cache and data builds.
This would seem like a battery drain. In most instances, battery life will even out over several cycles. - Assuming that the settings on the custom rom is placed properly.
I have seem some bad tweak settings when I have looked over many claimed tweaks to save battery when they do the exact opposites.
Pure Stock rom have many monitoring crap and background running apps collecting data that it will take up a lot of battery from just sitting.
I don't know which stock package you've used or which heimdall version or if you ran the heimdall frontend on the leaks.
If flashed properly with re-partition using the 1click adam outler created for the uckj4 and my uclb3, there should be no FC's.
It should be pure stock with everything working "perfectly" as intended by AT&T.
rooting only gives you access to your phone..it has no bearing on battery.
Overclocking - OC - may increase battery consumption/ Running stock - should not be an issue.
Click to expand...
Click to collapse
I used your One-Click back to stock 2.3.6.
As far as battery, I figured it out. I went to check battery usage and apparently google music (the cloud music app) had used up a whopping 87% of my battery. I never use it, so I just uninstalled it and my battery has gone back to normal.
I still have force closes, but it seems to be less frequent if I don't restart the phone and just leave it idle.
As far as rooting it, I just used superoneclick, then installed the one-click return to stock 2.3.6.
Dr_Derpy said:
I used your One-Click back to stock 2.3.6.
As far as battery, I figured it out. I went to check battery usage and apparently google music (the cloud music app) had used up a whopping 87% of my battery. I never use it, so I just uninstalled it and my battery has gone back to normal.
I still have force closes, but it seems to be less frequent if I don't restart the phone and just leave it idle.
As far as rooting it, I just used superoneclick, then installed the one-click return to stock 2.3.6.
Click to expand...
Click to collapse
hmmm..I'm not sure how you did it but the package I made w/ UCLB3 is not rootable with SOC. UCKJ4 is possible, but I don't think you want to run that build.
If you wanted to run a rooted uclb3, dman has made a rooted rom already.
If you're running stock uclb3..completely att, not deOdexed, there is no root on that...there is recovery if you used an insecure kernel...but no root...unless you installed busybox and superuser binaries yourself.
fc's is not right on stock uclb3...you may want to start over.
qkster said:
hmmm..I'm not sure how you did it but the package I made w/ UCLB3 is not rootable with SOC. UCKJ4 is possible, but I don't think you want to run that build.
If you wanted to run a rooted uclb3, dman has made a rooted rom already.
If you're running stock uclb3..completely att, not deOdexed, there is no root on that...there is recovery if you used an insecure kernel...but no root...unless you installed busybox and superuser binaries yourself.
fc's is not right on stock uclb3...you may want to start over.
Click to expand...
Click to collapse
Hmmm. I must have done something wrong then
I just ran the executable .jar file in the one-click return to stock thread, but maybe it's force closing BECAUSE I had rooted it before? I don't even care to have it rooted, I was just under the assumption that I had to have it rooted to install anything like 2.3.6 on it, but I think I must have misread something. I just want GB because I am tired of waiting for ATT to roll out the updates haha.
I'll try starting over, but does that mean that I have to format to stock, then use the 2.3.6 install?
Again, I apologize for all of the questions.
just run the package. it should take care of everything else.
if you want to run a custom rom, run the entropy in post #2, go into recovery, wipe and flash the rom you want.
it's that simple.
read the op's
qkster said:
just run the package. it should take care of everything else.
if you want to run a custom rom, run the entropy in post #2, go into recovery, wipe and flash the rom you want.
it's that simple.
read the op's
Click to expand...
Click to collapse
Okay, I'll give that a go!
Okay, well I reset my phone back to factory state and tried again, and everything seems to be working this time. No silly force closes, all of my apps work and my battery life is back to normal.
It must have had something to do with the root that I did before. Either way, things are going smoothly! Thank you thank you thank you!
Pretty much every time I flash a JB ROM my infuse is fine for a few days. Sometimes even a week. Perhaps a bit laggy, but I guess that's expected given the outdated hardware.
Then eventually I start getting having these two issues
1) random shut offs - in this case the phone sometimes will not boot unless I pull the battery and put it back in.
2) or an error that reads something like "unfortunately System UI has stopped"
I can press "okay" and then get the error again over and over. I can only get out of it by pulling the battery, or holding the power button down.
I did go back to GB for a while and did not have any of these problems.
All my apps are installed from the play store, not restored from a backup. I do not overclock or undervolt.
I'd simply blame hardware, except I don't seem to have problems with GB.
This has always happened to me as well. I would say that its due to incompatibility with JB. Wasn't so bad on ICS but I found that on JB I would be reflashing after only about 2 weeks because it got so bad.
-Sent from that.... you know.... thing that sends these things-
DarK_DemoN said:
This has always happened to me as well. I would say that its due to incompatibility with JB. Wasn't so bad on ICS but I found that on JB I would be reflashing after only about 2 weeks because it got so bad.
-Sent from that.... you know.... thing that sends these things-
Click to expand...
Click to collapse
Try Paranoid Android 4.1.2 pa_infuse4g-2.53-04NOV2012-152548 . I have been using that with no issues except the Video camera being crap (photos just fine though), and you have to toggle wifi on and off to get it working. 4.2.2 roms don't work that well on really any phone I have tried even the Gnex I own had issues. I upgraded from AEON straight to Paranoid Android using their upgrade steps listed on their page. No problems no errors didn't even loose my IMEI.
I have tried the newest 4.2.2 roms from liquid, Cyan, and paranoid android. 4.2.2 roms acted badly for me in general I can't remember if I ever got that exact error. I Keep on wiping and going back to my 4.1.2 PA nandroid backup. I kinda think it might be a general 4.2.2 issue dunno.
Also saw this on the latest Beanstalk out 4-10 (so I think you should stick to 4.1.2 roms which of course don't get updated anymore)
Trouble Alerts/Workarounds:
Status bar/Notification Drawer - There seems to be a bug with the 4.2.2 status bar/notification drawer freezing. It is happening on numerous phones at random and there is not a fix available yet. Workaround - Numerous ways to workaround this issue, but easiest in my opinion is to go to settings - system settings - PIE - Enable/Disable PIE. This restarts systemUI and unfreezes the status bar.
Does anyone know what sh means? Android os is destroying my battery life.
Sent from my SGH-I997 using xda app-developers app
Use cpuspy
Sent from my SGH-I997 using Tapatalk 2
I hope you have now the latest JB ROMS update, and every thing is working fine.
I hope you have now the latest JB ROMS update, and every thing is working fine.
for me, Beanstalk latest build 1.205 is working awesome, battery life is like i do not need to charge for two days.
Yianaki said:
Try Paranoid Android 4.1.2 pa_infuse4g-2.53-04NOV2012-152548 . I have been using that with no issues except the Video camera being crap (photos just fine though), and you have to toggle wifi on and off to get it working. 4.2.2 roms don't work that well on really any phone I have tried even the Gnex I own had issues. I upgraded from AEON straight to Paranoid Android using their upgrade steps listed on their page. No problems no errors didn't even loose my IMEI.
I have tried the newest 4.2.2 roms from liquid, Cyan, and paranoid android. 4.2.2 roms acted badly for me in general I can't remember if I ever got that exact error. I Keep on wiping and going back to my 4.1.2 PA nandroid backup. I kinda think it might be a general 4.2.2 issue dunno.
Also saw this on the latest Beanstalk out 4-10 (so I think you should stick to 4.1.2 roms which of course don't get updated anymore)
Trouble Alerts/Workarounds:
Status bar/Notification Drawer - There seems to be a bug with the 4.2.2 status bar/notification drawer freezing. It is happening on numerous phones at random and there is not a fix available yet. Workaround - Numerous ways to workaround this issue, but easiest in my opinion is to go to settings - system settings - PIE - Enable/Disable PIE. This restarts systemUI and unfreezes the status bar.
Click to expand...
Click to collapse