Hey all!
Just started this thread to explain something about SOD and phone SHUT DOWNS by itself.
I was NEVER BEFORE have these problems, like SOD or SHUT DOWN phone by itself, till now. I sure that it was related to one WIFI program, what I downloaded yesterday(Unlock With Wifi). Today I activated the app and I have phone SHUT DOWN by itself, like 3 times in hour. If I disabled the app, I solved the problem(for now I already UNINSTALLED that app).
Now I sure, that our SOD and S.DOWN problem not hardware problem, but SOFTWARE related problem.
I want to say you all, who have SOD or S.D...., look what app you have installed(what can use wifi) or in phone settings and try several times to configure your wifi(one of most: dont but your wifi to sleep, when screen is OFF), untill you solve you problem.
If you too know some examples, from you experience, then share with us here!
THX for reading!
Hope it will HELP someone.
CHEERS!
I'll try if turning off wifi will help. It should if this is wifi related problem.
JiiJii said:
I'll try if turning off wifi will help. It should if this is wifi related problem.
Click to expand...
Click to collapse
Hey!
Like I sayed, just try different things with WIFI settings. I think turning OFF wifi, will solve the problem, until you turning it back(when you have the problems). We will see, dose it solve the problem, if you turn OFF WIFI.
CHEERS!
You got the nail on spot. I was also in the same impression with SOD. Till now I'm not able to Figure out the app which cause this. But yes this is software issue rather than hardware. I also read else where that the SOD cause because of the lower voltage supplied to processor during sleep with which its not able to get itself up from sleep. Not sure...
I have a app that turns the wifi off when I lock the screen (dont remember which one of my apps!) so I havent experience it for awhile.
Sleep as an droid has a feature that shuts down the sleep tracker at a certain procentage (I chose 20%), instead of shutting the sleep tracker down, it shuts down the whole phone. Both of the times that i got SOD my phone had 20% left of its battery, so it was pretty obvious what caused it.
Sleep bot tracker is a great app if you forget to shut down your wi-fi before going to bed. Make it a habit to track your sleeping time, in the same time ull make it a habit to turn you wifi off. It has a built in function that shuts off the wifi when u start tracking your sleeping time. This app does not bring you and SOD.
What, but the general advise to sod had always been to check wifi always on...
XDA ♥
consegregate said:
What, but the general advise to sod had always been to check wifi always on...
XDA ♥
Click to expand...
Click to collapse
The topic been active in other threads so that's why the OP is taking this up I believe.
casiocas said:
Hey all!
Just started this thread to explain something about SOD and phone SHUT DOWNS by itself.
I was NEVER BEFORE have these problems, like SOD or SHUT DOWN phone by itself, till now. I sure that it was related to one WIFI program, what I downloaded yesterday(Unlock With Wifi). Today I activated the app and I have phone SHUT DOWN by itself, like 3 times in hour. If I disabled the app, I solved the problem(for now I already UNINSTALLED that app).
Now I sure, that our SOD and S.DOWN problem not hardware problem, but SOFTWARE related problem.
I want to say you all, who have SOD or S.D...., look what app you have installed(what can use wifi) or in phone settings and try several times to configure your wifi(one of most: dont but your wifi to sleep, when screen is OFF), untill you solve you problem.
If you too know some examples, from you experience, then share with us here!
THX for reading!
Hope it will HELP someone.
CHEERS!
Click to expand...
Click to collapse
I noticed that this problem is only for those who are using the older firmwares including XXKPH or the ROMs whose base are 2.3.4 KPH.
Haven't encountered this problem in the Samsung July 2011 release of 2.3.3 (KPN). But I guess, this is a good post for those who are still experiencing this.
For now, I'm just happy with KPN (that's why I'm not as active before here in the forums).
Before I flashed to 2.3.4 KPH, my Wifi worked flawlessly.
Now my Wifi reception is extremely limited (I have to be in direct line of sight to the router within 2 meters to be able to get a stable connection)
and
I get those dreaded SoDs (sleep of deaths).
My question:
Is it possible to flash only the modem file of 2.3.3 to try whether that works?
If yes, will my current system be wiped if I only flash the modem file?
kiudee said:
Before I flashed to 2.3.4 KPH, my Wifi worked flawlessly.
Now my Wifi reception is extremely limited (I have to be in direct line of sight to the router within 2 meters to be able to get a stable connection)
and
I get those dreaded SoDs (sleep of deaths).
My question:
Is it possible to flash only the modem file of 2.3.3 to try whether that works?
If yes, will my current system be wiped if I only flash the modem file?
Click to expand...
Click to collapse
If you don't use the video chat in Google Talk, then why not just flash 2.3.3 KPN?
The only new feature in 2.3.4 is the video chat in Google talk. Most bug fixes are now in the July 2011 release of 2.3.3 KPN.
Yes, I'm contemplating to do that.
But as I've spent a bit over a weeks time to set my system up, I would like to know if it's possible to just flash the modem without touching the already working system.
edit: I see KPN is a single file flash, so I won't be able to flash only the modem. Ok, backup and downgrade it is.
I've only experienced SOD once... But I always have wifi off. Just on when I'm going to use it. Afterwards I turn it off and good bye SOD issue
Sent from my GT-S5830B using XDA App
kiudee said:
Yes, I'm contemplating to do that.
But as I've spent a bit over a weeks time to set my system up, I would like to know if it's possible to just flash the modem without touching the already working system.
edit: I see KPN is a single file flash, so I won't be able to flash only the modem. Ok, backup and downgrade it is.
Click to expand...
Click to collapse
Hey!
Dont know exactly, but I think that you can restore your system settings and other system things, with TITANIUM BACKUP. Backup the ALL SYSTEM DATA in batch menu. Go to TITANIUM BACKUP>Menu>batch. Pick: backup all system data and RUN THE BATCH. After that, flash you ROM(what ever you want) and try to restore all system settings from TITANIUM B.. Ofcourse, what ever happens, I suggesting you do NANDROID BACKUP from CWM recovery, before you start anything. If nothing works(or **** happens), you can RESTORE ALL FROM NANDROID BACKUP.
CHEERS!
Update: I flashed 2.3.3 KPN and did a factory reset.
The SOD problems are gone now,
but
the bad wifi reception still remains. (Connection to router only works within an extremely close range)
If I cannot find a fix for this problem I might try out a froyo firmware.
Did anybody have a similar problem? Would really appreciate some hints.
kiudee said:
Update: I flashed 2.3.3 KPN and did a factory reset.
The SOD problems are gone now,
but
the bad wifi reception still remains. (Connection to router only works within an extremely close range)
If I cannot find a fix for this problem I might try out a froyo firmware.
Did anybody have a similar problem? Would really appreciate some hints.
Click to expand...
Click to collapse
Hey!
I think its not ROM-s problem. Try look your Router settings and phone settings. I think something is not right in PHONE or ROUTER settings. Not seen this kinde of problem YET, with ANY ROM. Try to look.
One question: dose you not DROP you phone or similar? I seen little problems can happen, even nothing SERIOUS was done(like speaker, wifi and other HARDWARE problems).
CHEERS!
kiudee said:
Update: I flashed 2.3.3 KPN and did a factory reset.
The SOD problems are gone now,
but
the bad wifi reception still remains. (Connection to router only works within an extremely close range)
If I cannot find a fix for this problem I might try out a froyo firmware.
Did anybody have a similar problem? Would really appreciate some hints.
Click to expand...
Click to collapse
Froyo will not help i think. I had all the mentioned problems in Froyo aswell. That's why i flashed to KPH and now KPN for eventually.
From my 3 days experience with Froyo i never experienced SOD.
I don have any sod problems.
BUT,sometimes my phone vibrates 3 times n then goes to Samsung bootlogo,den homescreen comes up n mediascanner starts.. (I ges this is called soft resetting)
Any solutions to get rid of this???
M in stock froyo rom..
Any help ll b appreciated...
Thanks
Sent from my GT-S5830 using Tapatalk
i had SOD with bluetooth turned on((((((((((((((((((((((((((
apps i downloaded are:
whatsapp
twitter
Facebook
im+ pro
dolphin browser
barcode reader
go launcher ex
my phone was rooted and running on 2.3.4 KPH. i had 3 SODs today but i never have any sods when i am at home. i have no idea which one(s) cause SOD.
today i flashed with coderom v2 (formatted sd and wiped internal memory and cache) i will see if sods keep on coming. if they do happen, then i am going to try KPN
I'm currently running a rooted Sprint stock 2.3.4 and from time to time i have notice that the screen would not timeout or go to sleep. I can push the power button and put it to sleep but it wont do it on its own. I did check and screen timeout change to "never". Has anyone else ran across this issue and/or maybe have a solution?
nunyabiziz said:
I'm currently running a rooted Sprint stock 2.3.4 and from time to time i have notice that the screen would not timeout or go to sleep. I can push the power button and put it to sleep but it wont do it on its own. I did check and screen timeout change to "never". Has anyone else ran across this issue and/or maybe have a solution?
Click to expand...
Click to collapse
um, to clarify, you have it set to never and you're asking why the screen wont timeout?
The evo changed to never on its own.
Sent from my Xoom using XDA App
nunyabiziz said:
The evo changed to never on its own.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
um, cant you just simply change it from never to like 15min or another interval?
Sorry that I was not totally cleared. My phone would randomly change from 1 minute timeout to never. So the issue is that if im not careful and check after im done using my phone, the screen would remain on and drain my battery.
nunyabiziz said:
Sorry that I was not totally cleared. My phone would randomly change from 1 minute timeout to never. So the issue is that if im not careful and check after im done using my phone, the screen would remain on and drain my battery.
Click to expand...
Click to collapse
Did you do a clean install of the ota? Because if you didn't then it could have caused that problem. I suggest you do a full wipe (after you backup) and then install the ota afterwards. See if the problem persists and if it doesnt then restore your apps.
Hope this helps
Sent from my rockin 3D
Thanks for the help. I had applied superwipe and installed rooted stock ota before posting. Of course still the same random issue. However I will use RUU and go back to stock then start all over from the beginning.
Sent from my Xoom using XDA App
I'm currently running Siyah 2.6.6i and Shep's MIUI 2.1.6v2. I'm having a weird issue that I've seen mentioned in the dev forums for the Siyah kernel, but nobody has mentioned a fix or suggested anything to try. Basically, when the screen on my device turns off while running on battery, the data connection turns itself off will not re-enable itself until I wake my phone, and sometimes I have to toggle airplane mode to get it to come back. This would be fine, as I'm on wifi 95% of the time, except when the data connection gets disabled, I no longer receive text messages, even on wifi. I've tried running both the OnDemand and Lulzactive scalings, but neither have made a difference. The only thing I've been able to do to fix this myself is to flash back over with the default MIUI kernel that comes with the build and not use the Siyah kernel.
Does anyone have any suggestions on how to fix this?
Looks like nope
Sent from my páhhōniē
roll back to 2.6.6... seems that 2.6.6i is nothing but trouble for a lot of people.
2.6.7 works fine..
Sent from my SAMSUNG-SGH-I777 using xda premium
It must have been an issue with 2.6.6 and 2.6.6i. I installed 2.6.7 this morning, and it seems to have fixed the issue with text messages, however my battery life is suffering a little bit. I don't mind, as long as I can keep communications coming in.
Thanks for the suggestions!
Today i wiped cache/dalvic cache/battery stats, then i started browsing the XDA Forum, suddenly the phone froze,then for two seconds a continious clicking noise appeared near the camera /cpu?/,after that the device restarted,but very quickly-without showing the siyah logo...This has happened once before, i was using ICS 4.0.4 with stock kernel...
Currently i'm with JB/siyah 6.0b5;
The device seems to be working just fine now,but i'm a little worried.Have you encountered this one before?
Sent from my GT-I9100 using xda app-developers app
umex said:
Today i wiped cache/dalvic cache/battery stats, then i started browsing the XDA Forum, suddenly the phone froze,then for two seconds a continious clicking noise appeared near the camera /cpu?/,after that the device restarted,but very quickly-without showing the siyah logo...This has happened once before, i was using ICS 4.0.4 with stock kernel...
Currently i'm with JB/siyah 6.0b5;
The device seems to be working just fine now,but i'm a little worried.Have you encountered this one before?
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Nope, the only time I've ever heard a clicking noise was using the CM torch, I decided to try the 'high' setting. Clicking started so I turned the torch back to normal brightness. Never had it since. Keep an eye (ear?) on it.. If it happens again then I'd flash a fully stock ROM & see if it happens on full stock. Have you undervolted/overclocked at all? Could be something to consider if you have.
Hopper8 said:
Nope, the only time I've ever heard a clicking noise was using the CM torch, I decided to try the 'high' setting. Clicking started so I turned the torch back to normal brightness. Never had it since. Keep an eye (ear?) on it.. If it happens again then I'd flash a fully stock ROM & see if it happens on full stock. Have you undervolted/overclocked at all? Could be something to consider if you have.
Click to expand...
Click to collapse
Yes, I have undervolted with two steps, using CPU ADJUSTER, but for the last three days the phone was OK.And the first time this thing happened to me I didn't even know what is undervolting...It could be from the kernel, I just flashed JB with Siyah 6.0b4 (the previous version)...I'll see how the device behaves without undervolting...If it happens again, i'll flash fully stock rom...
Hey
I own an S2 i9100, using CM 10.1 (latest stable). I haven't made any ROM/kernel change for as long as the stable came out.
Yesterday out of nowhere, my phone started boot looping, and I have no idea why. The phone boots completely and after a few seconds just crash.
I've looked at the logcat during a crash and couldn't make something out of it.
I've read the last_kmesg and couldn't find any leads.
My biggest clue is that I can totally prevent this from happening when I shut down the network (both wifi and GSM). A few seconds after one of those start, the phone reboots.
Bluetooth tethering for internet access doesn't crash the device. It sounds weird, so: Are there any operations that don't run on BT and do run on other types of networks? I might be able to narrow it down this way.
Also, I'd love to hear other suggestions, but I don't want to hurry up and wipe the device just yet.
Thanks!
Asaf.
Asaf try to flash another ROM and test network again to try or it was ROM related hardware related or something with baseband
Sent from my GT-I9100 using xda app-developers app