fixed - unable to go into deep sleep - Verizon Samsung Galaxy S III

Just putting this out there for anyone who may be having the same issue as a possible fix for them.
The wifes sgs3 would not go into deep sleep mode. as a result the battery was under constant drain.
her phone is set up pretty much like mine is and i wasn't having the issue and I couldn't seem to figure it out.
i did a clean flash but still the same problem. (wiped everything, even data)
I've been looking at BBS and wake lock detector for days but nothing was coming to mind, everything looked as it should.
i started removing apps, till there was nothing. still. same issue. tried different kernels. etc. still same issue.
I was about to move on to another rom (beans 18) to see if that would help. and i decided just for giggles to reflash the modem.
and what do you know upon reboot the phone started going into deep sleep mode.
I think i was running MF1 Modem and Bootchain with Mb1 TZ on her phone. but can't say for sure.
i downloaded the latest (d2vzw_VRBMF1_firmware) and flashed it. couldn't believe that is what the issue was.
anyways, if someone runs into the same issue. try flashing the latest modems or perhaps a previous and see if that helps.

Related

Screen shutting down :(

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?

HELP: Phone locks up and dies at random

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.

Time keeps changing randomly????????

I reinstalled my stock firmware last night with odin (or atlease i think i did..i notice things like my modded recovery still in the system/bin folder, etc) all is working fine but the time seems to change at times, specially after a reboot. I have to go to setting and toggle the the automaic network time box for it to correct the time. my texts are ALL mixed up now due to this. Anyone have any idea whats causing this or how it can be fixed?
I always have this issue as well when I go back to stock, and so far has always been corrected with a factory restore. I consider it the final step when going back to stock now. Hope this helps.

[Q] Team Eos ICS 1.0.0 Wifi Sleep Issue

Just installed this great rom. Definitely much snappier. Only issue I have is that the wifi does not go to sleep. Anyone else having the same issue.
Never mind. It was an app that kept the wifi on.
tj1772 said:
Just installed this great rom. Definitely much snappier. Only issue I have is that the wifi does not go to sleep. Anyone else having the same issue.
Never mind. It was an app that kept the wifi on.
Click to expand...
Click to collapse
my dear friend can you please answer mw which was this program because im having this problem with all the latest nightlies and the 1.0.0.it has a wifi depp sleep issue and after many hous is frozen and i must rebooted with vol up+power button..i asked everybody about this problem but nobody till now told me what is going on..thanks in advance!greetings from greece..
I also have the same problem. Wifi never sleep and no apps or services are running.
This happens to everyone. Battery stats say wifi never sleeps, but it does turn off..although it seems it takes longer than on HC.
Battery life is same/better. It also goes to deep sleep.
I have not had this except when the nightlys got unstable.
did anyone try reverting back to complete factory stock (pushing factory images) and then putting eos on?
I bring this up because I got some crud lock in that factory reset and cach wipes would not clear. afterwards doing the above all was well.
also some live wallpapers and widets can be problematic.
I personally keep a unrooted untouch factory backup around to be able to start from scratch.
the eos 1.0 is rock solid for me except for a few browser crashes. I'm [email protected]

[Q] 5113 Locking up and Strange Behavior

My neighbor's 5113 is having some strange issues I hope I can get some insight on. I've worked with a lot of Samsung phones and am very familiar with flashing, Odin, etc but have not worked with a tablet before.
First, it has 4.2.2 on it. I tried the stock software update function and it says it's up to date. Is that true? Is 4.2.2 the latest official for this device?
Second, It's having lock up issues (see below) so I thought I would "Clear Cache" in stock recovery. It starts going through the process and then errors out. It just flashes ERROR and then goes back to the stock recovery screen. I've never seen that before. Any ideas?
Lastly and most importantly, it locks up regularly. It will lock up with the screen on (although it seems to take longer to lock up with the screen on with some motion.) When the screen goes off it will lock up quickly, normally within 5 minutes and it even locks up when charging up. The charging animation stops and you have to hold the power button for 10 seconds to get it to come back to life. It's very strange. It even seems to freeze when it's off. It won't just start by pushing the power button for a couple of seconds, you have to hold it for 10 seconds until the charging animation pops up and then push the power button for a couple of seconds.
I haven't reset to factory specs because she has a ton of info on the thing and I'm afraid if it errors out clearing cache, what might it do if I try a factory reset?
Thoughts?
Thanks for the help.
UPDATE: I did a factory reset via stock recovery and it did delete all the data. It still will not let me clear cache though. It still locks up whenever the screen goes dark. It will lock up in just a couple of minutes.
Very frustrating.
I would try flashing the stock firmware and see if that clears up the locking problem, after a day or so I would flash CM11 with gapps and take it from there.
After running stock rooted before flashing CM11 do a nandroid b/u just in case it acts up. CM11 IS SUPER stable, have run it on my P5113 for several years starting with cm10.
CM12 is still buggy don't trust it.
Pp.
PanchoPlanet said:
I would try flashing the stock firmware and see if that clears up the locking problem,
Click to expand...
Click to collapse
Thank you very much PanchoPlanet. I factory reset and reloaded stock firmware several times but it would still lock up as soon as it went to sleep. And I still could not wipe cache. Very strange. I went so far as to not set up any accounts and make sure it didn't download any software updates to make sure it wasn't some update that was causing issues.
It would still lock up even when it was off and just supposed to be charging the battery! So I really think it's memory is trashed.
But I would be more than open to listen to any other ideas.
Thanks.
Maybe there could be other issues that you are not aware of, like the tab having been dropped or liquid damage or even voodoo, who knows.
Sometimes people don't disclose all the details.
Pp.
PanchoPlanet said:
Maybe there could be other issues that you are not aware of, like the tab having been dropped or liquid damage or even voodoo, who knows.
Sometimes people don't disclose all the details.
Pp.
Click to expand...
Click to collapse
It looks to be in perfect shape. But in any event, if something like that happened then it's toast anyway.
Yeah, especially the voodoo. Lol.
Pp.

Categories

Resources