hey folks,
i have encountered an annoying problem that has made using the s2 quite an unpleasant experience recently.
I bought my s2 about 4 months ago. after 2 weeks or so i switched to miui (galnet) and have stuck to miui ever since. later i switched to langthangs releases as well as siyahs kernels (loving both, major props to them).
around mid of december, my phone suddenly started to crash. up till then i had a couple of freezes here n there, maybe once or twice a months. but since then, even though i did not change anything, my phone has been crashing more often, like 5-10 times a week. updating kernel and rom didnt help.
i experience two types of crashes:
a) freeze: phone just stops working. i have to take out the battery to reboot
b) reboots: phone just reboots out of the blue. sometimes it reboots 3-4 times in a row, like after the first reboot the phone does nothing for 2-3 minutes, then reboots again and so on
i am not sure if that helps, but most of the time the freezes occur while using the internet, the market and playing games. reboots occur randomly, even if the phone is not used at all.
i haven't done any overclocking, just undervolting using voltage control. but i had been using the reduced voltages for weeks, long before the crashes started to occur. and yes, i did try switching back to the stock voltages.
i may have dropped my phone a couple of times, but none of the drops was really bad as it has no scratches or dents.
Anyone else having the same experience?
Is there a way to check if -maybe- the ram/rom is defect? If nothing helps, i think i ll have to flash a stock rom and submit a warranty claim
I would go on a limb saying its MIUI's fault. Wich version of Syiah are you using? Try to reflash different version, I found that 2.6.2 is stable. Also the new one 2.6.6 wich I'm currently testing is stable to, other ones were kinda buggy.
Also are you undervolting or UC'ing ?
If all else fails flash different ROM, after testing many of them I found the latest Criskelo to be stable as a rock.
The only way to really tell is to flash back to a stock rom and see if the freezes/reboots still occur...
Sent from my GT-I9100 using Tapatalk
well, i have tried different roms. and yeah, i am undervolting and underclocking (200-1000).
but isnt it strange? i have been using miui for months without any problems, and baaam ... suddenly the phone starts crashing? i mean at the time the freezes and reboots started to occur, i had been using the same system (kernel,rom,setting,apps) for weeks without any problems.
i ll try going back to stock. if that doesnt help, ill send it in.
btw. i have flash stock via odin, will the exclamation mark during the bootup process vanish?
dabrain23 said:
btw. i have flash stock via odin, will the exclamation mark during the bootup process vanish?
Click to expand...
Click to collapse
Yep, hence you flashed original firmware the dredded(by some) yellow triangle will dissapear.
It will reapear as soon as you root your device.
that last sentence was supposed to be "if i flash stock via odin ..."
ok. ill try that and report back.
BUT
if flashing a stock rom helps, the problems much likely lies with the custom rom. but if so, why did they work perfectly fine until recently?
i may have dropped my phone a couple of times, but none of the drops was really bad as it has no scratches or dents.
Logic says that is the answer .
jje
u think so?
the phone just slipped out of my hand a couple of times, but it never fell on the floor (lets say 30cm or more).
and why would sth like that cause freezes like that? i mean my sisters ace has a totally shattered glass and its still working perfectly fine.
anyway, backing up all my stuff and trying a stock rom tmr
Related
I'm posting this here because I hope some devs might be able to get a handle on the problem. I think it has something to do with the launcher.
Since I upgraded my phone to a 2.3.4 ROM, I've had constant problems with its randomly rebooting, or occasionally just freezing. (I say "rebooting", but it always gets stuck in a boot loop, and so it might as well be frozen.) The first ROM was Synergy, but I've had the same trouble on Warm, and with three or four different kernels (OC'ed and not OC'ed) on each of those ROM's. In some configurations it's better, and in some it's worse, but I've nearly always had the reboots happen at least once a day. Sometimes it happens while charging, sometimes while it's not; sometimes it happens while I'm touching it, and sometimes when I haven't touched it in hours (kind of annoying when it's my alarm clock--I missed a meeting last week). There's not a lot of consistency in when it happens, though I should say, for the record, that I've been using Launcher Pro the whole time.
Obviously, I'm not the only one with this problem: for some, like me, it started with 2.3.4 (including, in many cases, the stock OTA); for others, it started when the phone was first released; while for others, it's never happened at all. The fact that some people haven't experienced it at all may mean hardware has something to do with it, and I even read one account of a guy who took five different phones back to Sprint for replacements before finding one that worked right.
After searching high and low, I found a thread on the Sprint Community forums that suggested editing the data.prop file to keep the launcher in memory constantly (Look here and scroll down to post #9.). I tried this a couple of days ago, and it hasn't fixed the problem, but it did dramatically reduce it: I went from rebooting every two hours to rebooting once or twice a day.
I've noticed one other interesting thing: a couple of months ago, I started playing Godville, and I've been propping the phone up next to me and letting it idle with the screen on (while on USB), so that I can glance over every once in a while to see if anything is happening in the game. I've noticed that, every few minutes, the home screen wallpaper briefly replaces the app I have open; it happens so fast that I can't tell for sure if the whole launcher is coming up, but I suspect it is. I wonder if this constant yanking of the launcher into the foreground might be the source of the instability.
my mind is like..... blowwwwn
---------- Post added at 01:37 AM ---------- Previous post was at 01:28 AM ----------
no but on a serious note man... many people have had problems with reboots since the launch of the 3D, which was 2.3.3 based. I doubt that was the issue (launcher, your update, your games... gnomes...)
i would say flash the RPM PGIMG86423million update whatever that number is for the bootloader update.zip, and see if that rids you from the reboots.
for me, i fixed my reboots by getting a new SD card... i had the same issue when i first got my 3D late in july. Did it both on 2.3.3 base, and 2.3.4... it occurred to me one day that a bad disk would cause system reboots... and not being able to change out the one built into the phone... i opted for the SD card because it was cheap and i wanted a better one anyways. reboots went away immediately.
it also never occurred to me initially that my SD had been bad for a long time... not just when i had my 3D.. on my previous phone (samsung moment with froyo), whenever i would move apps to the SD card, i would always get some kind of error message. trying to move them a couple times would always successfully move the app(s) to the SD card.. i figured this was a problem with the rom i was on (speaking of my samsung moment)...
then when i transferred my card to my 3D, same problem, along with the reboots, and a light clicked on in my brain and said "***k-tard, your SD card is bad. derp."
haven't had a single reboot since then. i even wonder if the paramount number of people having reboot issues on the 3D was due to HTC possibly shipping them with defective SD cards...
just something to mix around in your brain for a bit...
Yeah, I considered the SD card as a problem, but the reboots happen even when the SD card is mounted as a USB drive. Also, a bad SD card wouldn't explain why keeping the launcher in memory dramatically reduces the problem.
I'll be giving it a try.
Just a side note. I've been using the stock kernel lately and havn't had a single reeboot. I'm on synergy rom and since he put back in the stock kernel w/ no OC I've had no issues.
I may try that, but it would be sad to not to able to OC a rooted phone. I'm starting to wonder if it's a bad internal flash drive, though.
You should try a stock ROM to see if that solves your issue if that's doesn't work maybe you have defective phone
Sent from my PG86100 using xda premium
All my problems went away when I used Senseless ROM. I think the kernel in the ROM is stock. It's been over two weeks since my phone has frozen on me and no more random reboots.
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Sent from my PG86100 using Tapatalk
I'm having the same reboot issues. I've noticed a few things:
1. Doesn't matter what sd card or how new, my phone reboots unexpectedly
2. Phone ONLY reboots RIGHT when the screen times out. Only on Android 2.3.4 w/ sense! It does not matter what kernel. Whatever I do, all reboots are directly related to sense on 2.3.4.
3. The only solution I have found is to deactivate the screen time out or gut HTC proprietary sense from the ROM.
P.s. I DO NOT have problemswith any ota based off 2.3.3
bloodrain954 said:
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Click to expand...
Click to collapse
Tiamat isn't stable for me.
MTKnife said:
Tiamat isn't stable for me.
Click to expand...
Click to collapse
Nor for me. It causes daily hard lockups that require a battery pull on my phone. Tiamat exhibited this on multiple ROMs for me.
I think trying a largely stock rom is a must as a start to tracing your problem. So is incremental additions of apps, tweaks, etc. Basic debugging and defect isolation stuff.
bloodrain954 said:
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
What about bcblend by mwalt? Senseless rom has been using that for quite some time and I haven't had any issues. When it was switched to tiamat for a short time (2.5 & 2.6, i believe) I had problems with lockups and reboots. Reboots would occur when the screen timed out every once in a while.
Just curious OP - have you tried the phone on a newly installed rom without installing any side apps for a day or so and seeing if you have any problems? Back on my old nexus S 4g i had issues with a particular battery app that would give similar problems to what you are experiencing.
Tiamat has not been stable for me either. I tried many different rom and kernel combos and am still having the issue. I noticed it is mostly happeneing when the phone is plugged in. but it also happens sometimes when im on a call. So there has to be more than one issue one being the proximity sensor and i cant figure out the other ive hset charging profiles to 384max and 198 min and other low clock speeds to see if it would help. Also set a temp profile to underclock when its over 38.0 celsius. Right now im running olympus trinity xe titan i ran it for a few days with mild anthrax and it only froze/rebooted a few times a day. I tried the anthrax kernel and it rebooted twice the first half hour so i flashed tiamat last night. Im trying to give it time to settle in but it just rebooted again when i plugged into pc. I bought my phone used and rooted before i even activated it so i dont know if this is something kernel/rom related. I started another thread a few days ago about this and the few responses i got were people running stock romand kernel not rooted. So i guess all we can hope for is the devs to figure it out or sprint to give us an ota that fixes it since im starting to belive its a hardware issue.
If you're on titan freezas is recommended.
Sent from my PG86100
I saw a few people talking about that but I thought they were talking about for when he released Hades. I'm gonna find the dl link now thanks.
Sent from my PG86100 using XDA App
Cabe24i said:
Just curious OP - have you tried the phone on a newly installed rom without installing any side apps for a day or so and seeing if you have any problems? Back on my old nexus S 4g i had issues with a particular battery app that would give similar problems to what you are experiencing.
Click to expand...
Click to collapse
Not for that long a period, no--unfortunately, I haven't been in a position where I could give up most of the use of my phone for that long. Once I have grades submitted next Monday, I can probably do more methodical testing.
I'm still freaked out by the way the launcher pops up every few minutes, though--has anyone else ever seen anything like that?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to General
One of my favorite rom and kernel combo's is infected eternity with anthrax but random reboots are common for me with any sense based rom. I run MIUI with whatever aosp kernel and everything is flawless. Other than experimenting with kernels to find battery life, MIUI is the most stable rom I have used so far and is my new daily driver!
Sent from my HTC EVO 3D using xda premium
My evo also reboots and i havent rooted my phone at all. I did get a new SD card and that reduced the amounts of reboots i get! . Although, i still get a few every week.
hope sprint/person finds a fix for this soon.
Mine did it stock / rooted stock and viper ROM I an on fresh and so far smooth as butter ... Stock rooted was awful every time it would time out bam reboot
Sent from my PG86100 using XDA App
I've only had this happen a few times and was wondering if anyone had this happen to them also. I'm rooted and run custom roms, it doesn't seem to be rom or kernel dependent.
For example, I had my phone on since noon and haven't really used it since then except a few times to check the time. I just pulled my phone out of my pocket and hit the power button... nothing. I held it down and it started to boot up. When this happens the battery is never dead (it was at 68% with the ext. battery this time), it just wants to turn itself off. It seems to happen when the phone is "sleeping", it's never done it when I'm actively using the phone so it's not an overheating issue.
It's not really annoying since it doesn't happen often, it just confuses me.
brando56894 said:
I've only had this happen a few times and was wondering if anyone had this happen to them also. I'm rooted and run custom roms, it doesn't seem to be rom or kernel dependent.
For example, I had my phone on since noon and haven't really used it since then except a few times to check the time. I just pulled my phone out of my pocket and hit the power button... nothing. I held it down and it started to boot up. When this happens the battery is never dead (it was at 68% with the ext. battery this time), it just wants to turn itself off. It seems to happen when the phone is "sleeping", it's never done it when I'm actively using the phone so it's not an overheating issue.
It's not really annoying since it doesn't happen often, it just confuses me.
Click to expand...
Click to collapse
still you might want to check the rom and kernel just in case, either re-flash or change.
if the problem still happens, use your warranty and get a new phone.
what rom, kernel, and recovery are you using?
I actually just happened earlier again. Got a text from a friend that she was here, so I went down and let her in, came back up and went to check my phone a few minutes later and it was off. WTF.
I'm currently using Nils newest business sense with the OC'd ICS kernel and the latest Amon Ra recovery. This used to happen on GB also so it's not a rom/kernel problem IMO.
It happens so sporadically (except for tonight apparently) that it's maybe happened 5 times since I got it on release day.
Maybe I have the governor in cpu master set too low? I have it at the lowest of 384 MHz, I've always wondered this: whats the difference between conservative and powersave?
did it happen while you were on stock GB or on a custom rom and kernel? maybe try relocking and running stock for a while and see what happens?
I honestly don't remember, it's been too long lol. It's not worth it to go back to stock and relock considering I like ICS too much.
brando56894 said:
I actually just happened earlier again.
I'm currently using the OC'd ICS kernel
Click to expand...
Click to collapse
that's the issue right there, run the stock kernel at stock speeds.
How could it be the ICS kernel when it's happened on GB also?
Which OC? I've read that the 1.8 causes random stuff like this, but 1.7 doesn't.
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
3.0.16-g4a9c8a3 SebastianFM #1 is what the kernel info says
The zip name is Overclocked_kernel_v1.20_1836_MHz_by_sebastianFM.zip
Not all phones can handle overclocking.
Mine is stable about 98% of the time, it may actually be the extended battery that is causing the issue.
brando56894 said:
Mine is stable about 98% of the time, it may actually be the extended battery that is causing the issue.
Click to expand...
Click to collapse
9x out of 10 random reboots are from either undervolting too low or overclocking too high.
I went back to the stock kernel since it seemed to be a little choppy with the oc'd kernel. That may have been the problem after all.
Sent from my Transformer TF101 using Tapatalk
Hi,
I have a Galaxy S2 on TMobile in the UK. Not rooted, just been upgraded to ICS with the official firmware through Kies.
Ever since then I've been randomly getting a black screen - i.e. phone doesn't respond to any of the buttons to turn the screen on. Only way to get the phone to work again is a battery pull. Haven't installed any apps from prior to ICS, and prior to ICS I didn't have this problem.
As well as getting a black unresponsive screen it seems to get really warm. Not the normal been playing a game warm, but bordering on really hot. When I do the battery pull and restart there's also been a big battery drain - have lost half the battery before and the phone warning is on screen saying it's about to run out of battery when it was 60% charged before.
I'm guessing no one's going to have a simple answer to this (although it would be great if anyone does, but I've searched and haven't found anything) - but any tips on trying to identify what the cause is? Could it be a bad app maybe?
I tried logcat but didn't really understand it (!) and I wasn't sure if it would record what happened before a battery pull anyway. What's a way of recording what's going on that will stay recorded after a battery pull?
Any tips to help get the bottom of this would be much appreciated
Many thanks
Andrew
First backup data and factory reset .
Still a problem reinstall the firmware.
Checkfus will let you download it and flash via Odin .
Or take it to a service centre is the other choice .
jje
factory reset m8 if ur carrying ur bckup frm gb ,than some apps r not fine wiv ics...jus use ur ics wivout ur bckup of apps and download betterybattstat and some apps to c wats draining,ull get some idea.
magosalas said:
Hi,
I have a Galaxy S2 on TMobile in the UK. Not rooted, just been upgraded to ICS with the official firmware through Kies.
Ever since then I've been randomly getting a black screen - i.e. phone doesn't respond to any of the buttons to turn the screen on. Only way to get the phone to work again is a battery pull. Haven't installed any apps from prior to ICS, and prior to ICS I didn't have this problem.
As well as getting a black unresponsive screen it seems to get really warm. Not the normal been playing a game warm, but bordering on really hot. When I do the battery pull and restart there's also been a big battery drain - have lost half the battery before and the phone warning is on screen saying it's about to run out of battery when it was 60% charged before.
I'm guessing no one's going to have a simple answer to this (although it would be great if anyone does, but I've searched and haven't found anything) - but any tips on trying to identify what the cause is? Could it be a bad app maybe?
I tried logcat but didn't really understand it (!) and I wasn't sure if it would record what happened before a battery pull anyway. What's a way of recording what's going on that will stay recorded after a battery pull?
Any tips to help get the bottom of this would be much appreciated
Many thanks
Andrew
Click to expand...
Click to collapse
I am having exactly the same problem. This has started just after upgrading to ICS. (I have an unlocked S2 CSC:XEU). Never had this problem before. I tried hard reset but the problem is still there.
I have upgraded using Kies.
I have the same problem on unlocked S2 CSC:XEU. not rooted...
reset didn't work. full wipe - the same problem
ics problems
hi, i have the following problems after updating to official ICS,
wifi sometimes gets stuck between on/off
sometimes phone goes to sleep and does not respond
wake up is slower than in GB
after numerous hard resets and re-flashing ICS with odin these issues persist.
I recommend re-flashing the official GB version and wait till samsung sort their crap out.
all these issues are kernel related. the wifi issue is reported to be a faulty stock kernel and the black unresponsive screen also is a kernel issue I faced with some beta kernels.
my tip, before you hesitate to go back to GB, give one of the custom kernels a try. Siyah, Speedmod, ... just for the moment don't tweak anything and make sure you really flash an ICS kernel (!!). Just flash one of these kernels and give it a try, you don't even have to do it with odin and thus increase the counter, but you can use that variant. When you are in CWM, instead of flashing the SU zip file, flash the custom kernel zip which will root your phone, too.
Now give the custom kernel a try and see if your issues are gone.
If you don't like it, just flash the stock kernel with odin and uninstall SU and Busybox, and you are back to stock ICS.
I had the same problem. Kernel. Flash the latest siyah kernel and sleep of death will dissapear
Sent from my GT-I9100 using XDA
I'm getting the exact same issue running Siyah 3.3.2 and CM9. Also happened with stock ICS.
First few times it happened the phone was in my pocket and I felt it get warm. Only way to recover it was to hold power button in for about 10 seconds and it then reboots. I thought the screen was unlocking in my pocket and it was switching off due to overheating... but
Happened again today whilst I was using the phone. Screen went black and phone started getting hotter and hotter. I now think something is causing some kind of loop that causing the lockup / heat up and the phone is actually still on until I press and hold the power button.
I'm currently trying a "record" with CatLog but I can reproduce the problem easily apart from it happening 4 times in the 4 weeks I've had the phone.
(Its a I9100P if that makes any difference)
I have two galaxy s2s. one is i9100 and the other one is i777 on at&t.
SoD happened once on each phone. The i777 was running stock gingerbread and the i9100 was running resurrection remix 1.9.1 with the siyan kernal I believe.
The screen just wouldn't turn on so I just pulled the battery out (is it safe for the phone?)
This doesn't happen often,well just once each on each phone as stated before, but it does bug me as it makes me think there's something wrong with my phones, and pulling the battery out doesn't seem like it's good for the phone.
I searched around the forum a bit and saw other people are having this issue as well. And not just the galaxy s2, but other phones too.
only sleep of death in almost 10 months of use is when i tried xwlp9.
so no its not common
It's fairly common yes, a lot of people running non-stock ROMs get this. I had this ~25 times on numerous Resurrection Remix ROMs, but since v1.9 I haven't had this issue fortunately. If it's causing you a big problem, try fixing permissions from CWM recovery, that seemed to make a big difference when I was having the problem.
SOD usually occurs when the kernel UV the CPU or GPU a little to much. Not every device is the same and not handle same kernels, UV values etc
Sent from my GT-P6810 using XDA Premium HD app
From the sound of it, it seems to be a software problem.
I got it on the i777 which wasn't running a custom rom. But I think it could be caused by that battery management app that I installed.
anyway, my main concern is that if there's anything wrong physically with the hardware. ( having the SoD caused by software problem is much easier to swallow as to it being caused by hardware problem, as I can just reflash the kernal, roms, factory reset, etc. )
and did removing the battery while in SoD mode damage the phone?
It's normally a firmware issue, or a conflict between an app & the firmware. You'd find it's pretty rare for an 'untouched' (I.E not modded) phone running stock firmware to have SOD's. And obviously if you're flashing custom firmware that's constantly evolving/changing, then sometimes you're going to get SOD's, tho with most well crafted firmware these are fairly rare.
I reckon I've probably had <10 in the 8 mths I've had my phone & I've been running non-stock firmware the whole time save for the week I got my phone, which is nothing when stacked up against all the mucking around I've with my phone.
Edit to add - One way you can test to see if SOD's you're having are possibly hardware related is to do a completely clean install of stock firmware & see if they still happen. If they don't, then it's obviously whatever firmware you were running. If they do, then it might be hardware-related. Re: your question about pulling the battery after a SOD, normally this shouldn't cause you any problems (it's sometimes the only way you can successfully reboot the phone).
The only known SOD issues on I9100 are the old 2.3.3 (don't remember which one) and the XWLP9 kernel.
Custom roms... well. No need to elaborate I guess.
Most of them have undervolted settings as default.
victorator said:
The only known SOD issues on I9100 are the old 2.3.3 (don't remember which one) and the XWLP9 kernel.
Custom roms... well. No need to elaborate I guess.
Most of them have undervolted settings as default.
Click to expand...
Click to collapse
Im pretty sure i rooted my phone on the we with LP9 kernel. Since Sunday, I've had about 10 sods and never had one before... no doubt here as to what's causing it. I plan to change the kernel on the we and hopefully no more sod.
Ray_Grey said:
Im pretty sure i rooted my phone on the we with LP9 kernel. Since Sunday, I've had about 10 sods and never had one before... no doubt here as to what's causing it. I plan to change the kernel on the we and hopefully no more sod.
Click to expand...
Click to collapse
Or just flash the newer build. No SOD there.
wanewon said:
anyway, my main concern is that if there's anything wrong physically with the hardware. ( having the SoD caused by software problem is much easier to swallow as to it being caused by hardware problem, as I can just reflash the kernal, roms, factory reset, etc. )
and did removing the battery while in SoD mode damage the phone?
Click to expand...
Click to collapse
How about this?
I answered your question. Read the edit I made to my post.
wanewon said:
How about this?
Click to expand...
Click to collapse
MistahBungle said:
I answered your question. Read the edit I made to my post.
Click to expand...
Click to collapse
Thank you for the answer.
Since it's kinda hard to recreate the SOD. I'll reflash the rom and kernal and do a wipe and see if the SOD still happen
victorator said:
Or just flash the newer build. No SOD there.
Click to expand...
Click to collapse
Victorator, forgive my ignorance, but are you saying i should just flash the latest build, XWLPD, onto my fone rather than re-rooting it using a different kernel (i.e. CF-Root-SGS2_DX_SIN_LP9-v5.4-CWM5.zip) in order to stop the SOD?
Never faced such issues ever.
Sleep of death
Hi all, the SLEEP OF DEATH on android phones has even become worse; somebody said this issue is resolved in ICS 4.0.3; thats not true. As of now; i have a galaxy S2 i900, 1 month and 2 weeks old, running ICS 4.0.4 and I have been experiencing this problem lately and took back my phone for repairs last week, got back the phone yesterday and this morning the sleep of death happened 3 times in 1 hour. I took the phone for repairs again later this evening and i made it clear to them that problem still hangs around and i told them that if it comes back with the same problem, they got to give me a new one because it happens on some devices only and im dead serious because SAMSUNG knows about this issue very well and they do nothing. NOW CHECK THIS OUT: the new SAMSUNG GALAXY S3 features this disease too; i was in the queue with two S3 clients reporting this problem. Android is really bad at times; im moving to APPLE
Will keep you Updated
MALCOM
MX 007 said:
Hi all, the SLEEP OF DEATH on android phones has even become worse; somebody said this issue is resolved in ICS 4.0.3; thats not true. As of now; i have a galaxy S2 i900, 1 month and 2 weeks old, running ICS 4.0.4 and I have been experiencing this problem lately and took back my phone for repairs last week, got back the phone yesterday and this morning the sleep of death happened 3 times in 1 hour. I took the phone for repairs again later this evening and i made it clear to them that problem still hangs around and i told them that if it comes back with the same problem, they got to give me a new one because it happens on some devices only and im dead serious because SAMSUNG knows about this issue very well and they do nothing. NOW CHECK THIS OUT: the new SAMSUNG GALAXY S3 features this disease too; i was in the queue with two S3 clients reporting this problem. Android is really bad at times; im moving to APPLE
Will keep you Updated
MALCOM
Click to expand...
Click to collapse
bah bye
SOD
im having the same trouble with stock android 4.0.3 and know with
super nexus rom, the only way to solve it, is to use a program that
prevent phone lock, at the costo of more batery use
?
darkm1st87 said:
im having the same trouble with stock android 4.0.3 and know with
super nexus rom, the only way to solve it, is to use a program that
prevent phone lock, at the costo of more batery use
Click to expand...
Click to collapse
Could u please test something for me...because i am trying to solve this problem since a long time..
Could u put your phone while open screen on refrigerator for 30' .There is no fear of destroy the phone.I have test already 2 phones with sod and both are doing it with low temp.I want to see if it is sw or hd problem
tkrokod said:
Could u please test something for me...because i am trying to solve this problem since a long time..
Could u put your phone while open screen on refrigerator for 30' .There is no fear of destroy the phone.I have test already 2 phones with sod and both are doing it with low temp.I want to see if it is sw or hd problem
Click to expand...
Click to collapse
Hi,
I'm also trying to solve this problem, since weeks.
My observations:
SOD happens most on higher battery status (e.g. more SOD's at 80% battery then at 20%
The Phone gets hot after SOD and also before the SOD comes.
While loading the Phone SOD's happen more often
The battery status drains rapidly while SOD (cause of the resulting heat)
My SOD's are independent of kernel, rom, firmware or what ever.
I think it's a hardware problem, but I've no warranty and what to solve the problem without changing the mainboard. It couldn't be a really defective of an important part, cause the phone works apart of this SOD-problem.
Maybe we could find out together howto solve these anoying sod's
Hey. Im trying to solve the SOD problem myself cause its been happening every day and its really annyoing since the phone isnt even a month old.
I got the newest cyanogen mod running.
The phones model is GT-i9100
Android is 4,2,1
I still have warranty on it, do you think I should go back to stock, go exchange my phone where I got it and see if the new one has SOD too or should I just try fixing it first.
Also apps I use constantly : go launcher and dragonvale
I have a 8 gb micro SD inside as well, dunno if that could cause this.
First of all, my phone is running jellybomb version 2, freeza beastmode kernel 2.0 and cpu running at 2.7. I've never had problems before until one day I downloaded a file that had a virus, so I decided to do a restore using twrp. The restore failed and my phone and it got screwed, I've tried several methods to get it running again and I finally found the solution. I flashed the brickbug file and it was fixed. Now I noticed that sometimes when I restart the phone, it won't restart, it just powers off. There are also times when my phone just blacks out and freezes and I have to do a battery pull. There are also incidents where after boot up from a restart or battery pull, my touch screen won't respond. It's really weird. I dirty flashed to jellybomb version 2 from version 1, I doubt that's the issue since these problems started happening after I flashed brickbug to fix my phone. Anyone know what could be wrong or a fix? It's not a huge issue since my phone works fine most of the time, but it gets a bit annoying when the problem does happen. Last resort would be wipe absolutely everything and start over..
Sent from my SM-N900P using XDA Premium 4 mobile app
vizi0nz said:
First of all, my phone is running jellybomb version 2, freeza beastmode kernel 2.0 and cpu running at 2.7. I've never had problems before until one day I downloaded a file that had a virus, so I decided to do a restore using twrp. The restore failed and my phone and it got screwed, I've tried several methods to get it running again and I finally found the solution. I flashed the brickbug file and it was fixed. Now I noticed that sometimes when I restart the phone, it won't restart, it just powers off. There are also times when my phone just blacks out and freezes and I have to do a battery pull. There are also incidents where after boot up from a restart or battery pull, my touch screen won't respond. It's really weird. I dirty flashed to jellybomb version 2 from version 1, I doubt that's the issue since these problems started happening after I flashed brickbug to fix my phone. Anyone know what could be wrong or a fix? It's not a huge issue since my phone works fine most of the time, but it gets a bit annoying when the problem does happen. Last resort would be wipe absolutely everything and start over..
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Honestly my phone does the same with occasional random reboots and lock ups requiring battery pulls (Even the power button-menu-power up didn't restart to twrp) and even then restarting doesn't usually go without a hitch. Even when I was running stock root my phone would get stuck at the yellow sprint screen from time to time and I'd have to go TWRP and wipe Dalvik and Cache, then Dalvik again to get it to reboot.. The only reason I didn't unroot was was because even when my phone was new and out of the box, stock it wouldn't reboot cleanly all the time.
It got a little better after the firmware updates but it still hasn't gone away entirely.
I do expect it to get cleared up eventually but for now just take it as a fact of life with this phone.
demetrios3 said:
Honestly my phone does the same with occasional random reboots and lock ups requiring battery pulls (Even the power button-menu-power up didn't restart to twrp) and even then restarting doesn't usually go without a hitch. Even when I was running stock root my phone would get stuck at the yellow sprint screen from time to time and I'd have to go TWRP and wipe Dalvik and Cache, then Dalvik again to get it to reboot.. The only reason I didn't unroot was was because even when my phone was new and out of the box, stock it wouldn't reboot cleanly all the time.
It got a little better after the firmware updates but it still hasn't gone away entirely.
I do expect it to get cleared up eventually but for now just take it as a fact of life with this phone.
Click to expand...
Click to collapse
Yeah, I've been wiping dalvik and cache too, to get my phone back to normal at times too.
Sent from my SM-N900P using XDA Premium 4 mobile app
vizi0nz said:
First of all, my phone is running jellybomb version 2, freeza beastmode kernel 2.0 and cpu running at 2.7. I've never had problems before until one day I downloaded a file that had a virus, so I decided to do a restore using twrp. The restore failed and my phone and it got screwed, I've tried several methods to get it running again and I finally found the solution. I flashed the brickbug file and it was fixed. Now I noticed that sometimes when I restart the phone, it won't restart, it just powers off. There are also times when my phone just blacks out and freezes and I have to do a battery pull. There are also incidents where after boot up from a restart or battery pull, my touch screen won't respond. It's really weird. I dirty flashed to jellybomb version 2 from version 1, I doubt that's the issue since these problems started happening after I flashed brickbug to fix my phone. Anyone know what could be wrong or a fix? It's not a huge issue since my phone works fine most of the time, but it gets a bit annoying when the problem does happen. Last resort would be wipe absolutely everything and start over..
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sounds like its the beastmode kernel issues. Flash version 1.8 and see if that fixes your issues.
I would run the MJ4 tar via Odin to start totally fresh.
I am having a similar issue. my phone will just reboot on its own and freeze up a lot. i dont think its the kernel because it has been happening ever since i first installed the jellybomb rom and had a lite kernel installed. now switched to beast 2.3 and still having the same issues. im gonna flash 1.8 and see if it gets any better. but people are posting positive results on the 2.3 . dont know what to do. its frustrating
sillykaos said:
I am having a similar issue. my phone will just reboot on its own and freeze up a lot. i dont think its the kernel because it has been happening ever since i first installed the jellybomb rom and had a lite kernel installed. now switched to beast 2.3 and still having the same issues. im gonna flash 1.8 and see if it gets any better. but people are posting positive results on the 2.3 . dont know what to do. its frustrating
Click to expand...
Click to collapse
Before going through all that mess, toss on a stock kernel and see if your issues go away. You'll narrow down the issues right quick.
Compusmurf said:
Before going through all that mess, toss on a stock kernel and see if your issues go away. You'll narrow down the issues right quick.
Click to expand...
Click to collapse
Ill give it a shot when i get home. barely have service here at my office. ill post my results back.
Compusmurf said:
Before going through all that mess, toss on a stock kernel and see if your issues go away. You'll narrow down the issues right quick.
Click to expand...
Click to collapse
My phone has been doing this from the time i took it out of the box on October 4. It was ever worse then, so much so that I returned the phone exchanged it for a new one. The problems continued and I questioned my decision to upgrade to the Note 3 but then the firmware upgrades improved things a little.
I can tolerate the issues now and I do expect them to go away on future updates
edgar360 said:
Sounds like its the beastmode kernel issues. Flash version 1.8 and see if that fixes your issues.
Click to expand...
Click to collapse
I flashed 2.3 kernel and it seemed to fix most problems.. I just get Internet shutdowns here and there.. So far that's the only problem.
Sent from my SM-N900P using XDA Premium 4 mobile app
vizi0nz said:
I flashed 2.3 kernel and it seemed to fix most problems.. I just get Internet shutdowns here and there.. So far that's the only problem.
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
2.3 is the shiz, bro. I know some have issues with it, but for me it far exceeds even 1.8. Even with no overclocking, 1.8 would do odd stuff, like go to off when I'd selected restart (plugged in or not), &c. With 2.3, I've yet to run into any issues, the phone behaves as I've directed it. I overclock it using profiles in SetCPU, and the cores stay cool. With 1.8, no such luck.
As to Internet shutdowns, I have found that the browser plays a role in things. Having never used the stock browser, I switch mainly between boat browser and chrome, and both will occasionally freeze. Long back press to kill is my fallback.
Sent from my SM-N900P using Xparent BlueTapatalk 2
what your describing
Your phones should run flawlessly all the time. I would take issue that when the phone starts acting buggy, it's just normal for this phone.....I disagree with that, there is a issue somewhere if you have these issues occasionally.
Just my 2 cents
Well it took my slack ass a couple weeks to flash the stock kernel due to my issues. and after a few days my phone hasnt randomly rebooted. So i take it my phone is not liking the BEAST right now? This is just some poopoo.