Related
All, having a weird issue. I was on the phone yesterday using an automated menu system and my phone restarted. No rhyme nor reason why. It did that repeatedly throughout the day. I tried flashing a new ROM version, Phoenix 6.0!!, with no luck. I tried a normal restart, power down and then up, running a virus scan, pulling the batter for 30 minutes and no difference. The phone continued to restart. I finally got fed up and my battery was almost dead so I turned the phone off.
The phone was off for probably 5 hours and I charged it while off. I restarted the phone and transferred all of my content off, expecting to Odin back to stock and reflash Phoenix. The phone seemed to be behaving so I left it alone and plugged it into the wall for the night.
I got up this morning and everything appeared to be good. Went to work and still no problems, phone had an uptime of over 12 hours. Which would be what I would expect. Had the phone on my desk and I noticed it had restarted. When I mean it restarted, it went back to the boot animation and then loaded to the android screen and performed media scan and all my apps loaded on the home screens and services started up.
I went back to Settings->About->Status and the uptime was 18 hours now. So even with the restart, the uptime was still counting. Needless to say, I'm at a lose. Can't isolate any event that causes this reset or any app. Could I have gotten something from the automated call system? Is something just weird. I had been running Phoenix 5.2 for a few weeks with now problems so I'm confused. Any suggestions would be appreciated. I will probably flash back to stock and start again but I'd like to isolate this problem if possible.
To the best of your knowledge, no apps were just added, our settings adjusted?
Either way I would odin flash master clear. May even run stock for a but to see if behavior stops
Sent from my Captivate using XDA Premium App
sounds like a problem with the infamous 850-1900mhz handoff....
if your signature is accurate, that modem you are using is 1900mhz only i believe....it doesnt support 850, so if you are in an area where its trying to hand off to 850, it will cause a soft reboot.....i have seen it a million times myself when playing with the first run of i9000 roms
Pirateghost said:
sounds like a problem with the infamous 850-1900mhz handoff....
if your signature is accurate, that modem you are using is 1900mhz only i believe....it doesnt support 850, so if you are in an area where its trying to hand off to 850, it will cause a soft reboot.....i have seen it a million times myself when playing with the first run of i9000 roms
Click to expand...
Click to collapse
Hmmm...I have been using an i9000 roms for a few months with no issues. The last modem I was using was I9000UJK4, I think? I don't know without flashing back, whatever came with Phoenix 5.2 ROM. I had zero problems. I only flashed to that modem/ROM, Phoenix 6.0, in an attempt to fix the soft reboot.
flash just the JK4 modem and i bet the soft reboots stop. what you have listed there is i believe a 1900mhz only modem....
Pirateghost said:
flash just the JK4 modem and i bet the soft reboots stop. what you have listed there is i believe a 1900mhz only modem....
Click to expand...
Click to collapse
I will try that, when I can find it to download but the problem started with the JK4 modem. I was running Phoenix 5.2 with a JK4 modem and only flashed to the new one in an attempt to wipe whatever was causing the data.
Flashing UGJK4 right now, I'll see if that fixes anything however I'm not super confident since the problem occurred originally with a JK4 modem.
Update: Rebooted once after modem flash. Going to wait for a bit and see what happens.
if that doesnt work, i would think its a problem with your hardware
Pirateghost said:
if that doesnt work, i would think its a problem with your hardware
Click to expand...
Click to collapse
If the modem switch doesn't work, I'm first going to flash to stock and master clear. If the problem goes away, I'll flash to Phoenix again. If the problem comes back, it'll have to be part of my SW. If the problem persists at stock, back to AT&T for a refurbished phone.
Update: Looks like things are pretty stable right now. I'm not super in-tune with how the modems work but is there a way to allow the JK4 modem to use 850 or 1900 speeds, like an auto setting that will choose the best one. I use SGS tools for secret codes so if its in there let me know. So far so good, thanks pirate.
Reviving an old thread because I am also having soft reboot issues.
Unlike the previous poster, I am not using an i9000 based kernel. I am running the latest leaked Gingerbread for the i897 (JK3), rooted via Fugu kernel swap method; the only other tweak to stock has been to freeze via TiBu the AT&T Tethering Manager. I am even using the stock launcher as I try to isolate what is causing this.
The phone goes through spells where it will soft reboot every 10 minutes or less, and then periods where it will go days where it is stable. I have had this issue with multiple versions of the 2.3.3 and 2.3.5 leaks and am nearing wits end figuring out the cause.
Before each flash (and I have flashed multiple times with different stock leaks) I am wiping data and cache via recovery (I do not have CWM installed), then restoring apps only via TiBu. I have tried to be judicious about what I reinstall, but have not been able to identify if there is a misbehaving one yet.
I suspect this is software and not hardware, since I had this problem on my first Cap and have already done one warranty exchange; the external SD card, though, is the same for both.
I've looked for kernel panic logs and have not seen any, and have yet to find a good way to trap what is causing this.
This is my work issued phone (does Exchange sync and has company policies sent to it), so I am loathe to go all the way to a custom ROM, even though I realize that I voided the warranty when I rooted and went to leaked ROMs.
Anyone have an ideas as to what could be causing this, how I can isolate the problem, and hopefully resolve it once and for all? Worst case, I could go back to Froyo until AT&T finally drops the promised Gingerbread update, but I had different issues with Froyo with Market updates not always finishing and apps on the SD card not always being recognized.
Hey guys-
Kinda a weird problem.
So my captivate won't play any system sounds at all. It's particularly weird, since all media apps work just fine. This was fresh from Samsung's repair center, and had a new install of official 2.2 on it. It wasn't even rooted when this problem started, and after a flash to 2.3.3 it still has the problem. I've tried changing the ringtone, notifications, and every other sound; same thing with turning everything up all the way. Nothing has changed and there is no silent mode active anywhere. It seems to only vibrate when a message comes in. I'm fairly confident that it's not a software problem, due to the updated firmware and kernel. Has anyone had this problem? Do they know of a workaround?
lisurgec said:
Hey guys-
Kinda a weird problem.
So my captivate won't play any system sounds at all. It's particularly weird, since all media apps work just fine. This was fresh from Samsung's repair center, and had a new install of official 2.2 on it. It wasn't even rooted when this problem started, and after a flash to 2.3.3 it still has the problem. I've tried changing the ringtone, notifications, and every other sound; same thing with turning everything up all the way. Nothing has changed and there is no silent mode active anywhere. It seems to only vibrate when a message comes in. I'm fairly confident that it's not a software problem, due to the updated firmware and kernel. Has anyone had this problem? Do they know of a workaround?
Click to expand...
Click to collapse
Mabey an odin one click, then keys update to froyo might work ??? !! I'M NOT TELLING YOU TO DO THAT, I'm just suggesting that might work. If it came with froyo then you might get a bootloop so I would suggest getting a jig if try this way
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
jig
in all cases the jig is your lifeline lol. I SUGGEST having a jig handy when any new roms are installed. There are alot of good roms out there having no phone for a couple days changes the perspective and for you to make a jig is under 10$ .... Did I mention lovin the new Serendipity 7, good clean rom.
Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign
^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.
I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.
A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.
Hi Guys and Gals
Hoping someone can help meor point me to somewhere/one who can please
Recently picked up an i9000 which is on the orange network and was running:
PDA: i9000bvjm5
PHONE: i9000bvjm1
CSC: i9000orajm3
everything worked just fine, i was getting tons of battery life out of it in idle, until i noticed that when i had 'anti-shake' ticked in the camera mode, it wouldnt allow me to adjust the exposure, so i contacted samsung and they told me that upgrading my firmware to 2.3.3 via Kies would solve the problem, i promptly did so and yes, it fixed the problem (hurrah!)
HOWEVER!
i now have a much larger issue with my phone in that before updating the firmware it would eat about 5% of my battery in 24hrs if not in use
Now i need to charge this thing twice a day minimum even when im not using it!!! aaaaaaaarrrggghhh!
i've shut off all unneccessary services like background data etc etc etc still no help, digging into the battery stats themselves tells me its the android OS thats eating 78% of my battery, while its idling! WTF! previous to this it was the display that ate the battery, but it cant be that when the displays off can it!
How on earth can i get back to my original firmware (eclair) or update to a newer version where this problem is fixed please?
i am a bit of a nob/noob at this so please try to K.I.S.S.
I cant live like this!!!! lol
will a factory data reset do the trick? or doesn't that affect the firmware?
Any help greatly appreciated
Yours in desperation x
Dan
If you google "Android OS bug" you'll see that this is a common problem. You said you upgraded to 2.3.3, but I believe they didn't correct this issue until 2.3.5—although I may be wrong about that.
You can update to whatever firmware you want by flashing your phone. This will void your warranty. Likewise, you can flash back to 2.2 if you so please. You can flash your device using a program called Odin or Heimdall. Search for tutorials, you'll find plenty.
As for the actual bug, in my times of testing a ROM that was susceptable to the Android OS bug, I usually just restarted my phone and saw it go away. Clearing the cache may help as well, but I really couldn't say for sure. Try a simple reboot and see if the problem persists.
big props upichie!
i had exhaustively googled this problem before troubling you guys but it appears i was using the wrong words, doh!
alas im still none the wiser ( all the guides i can find 'assume' i know too much already about their terms for things and im lost
i turn my phone off, within 5 minutes of restarting it the OS is once again draining my battery completely
i clear my cache every 5 minutes and within 2 minutes its flippin eating me again
is odin or heindall another thing i install onto my pc (not my phone?) like kies to revert back to the old firmware? eclair 2.1 i had nailed! if it aint broke dont fix it, why dont i listen to myself!
and why the funk would they release a firmware that does this in the first place?
my head is spinning with the retardedness of all this, i come from a background where testing things exhaustively is part of the job, so i cant for the life of me understand why they would launch with something that sucks sooo bad!
im also at a slight disadvantage because i have the orange firmware and slightly different settings to most who have eclair, i think
jesus wept i just dont know anymore lol i think ill just throw the thing in the bin and go back to my old sony w810i cos that lasted 7 days on battery!
funk this firmware, funk this nonsense and funk this 12 hrs battery drain when not even using it, what a funkin palava!!!!
oh and funk you too samsung for telling me to upgrade my firmware you funkers!!!!!
im going to cry now lol
No worries! We've all been there. The terminology is confusing, but once you get a good grasp of it, you realize how simple it is to know what you need to know. I'm here to help.
Odin and Heimdall are programs for your PC, although I don't believe either need to be installed (they're just standalone executables). They both are programs designed to flash a new firmware onto your phone. You simply download the firmware files (for Odin it comes in 1 to 3 files, but Heimdall if I recall correctly only uses 1 file) and then use the program to flash the new firmware.
Just so you're aware, if your Android OS is showing a high percentage, that percentage will not go away until you fully recharge the phone, as it would keep the record of the Android OS previously draining your battery.
I'm honestly not entirely sure how to help you. You could download the app called BettterBatteryStats and do some digging to find out what is causing your phone to not be able to enter/maintain deep sleep (otherwise known as a "wakelock"), but you sound slightly inexperienced and probably wouldn't be thrilled with that idea.
Alternatively, is there any option in Kies to downgrade to 2.1 again? Maybe contact Samsung and see what they have to say. You upgraded from 2.1 to 2.3 because of their suggestion, and now your phone is getting unusable battery life. It only seems logical they'd have a way to downgrade.
If you have any questions about terminology, how things work, or anything at all related to your i9000, please do not hesitate to ask! We're here to help in any way that we can.
Try to flash xxjvt with semaphore 1.8.2 kernel. If i not use my i9000 just for calls/maild and music my battery lasts 2 days with 3g and wifi on.
Try to wipe your battery stats after a full charge.
Sent from my GT-I9000 using xda premium
Hi
I am new to Android world. So please handle with care
I used to use an iPhone. Recently (bout 3 weeks ago) I bought a galaxy note and am loving it.
I was going through a lot about Android system and found out 'rooting a phone'.
so I rooted the note and installed Rocket rom v22, GoLauncher Ex and few apps like Setcpu, Adfree, Bank, Xchange etc. I don't have games or many apps on my phone.
My phone turns itself off randomly every now and then. during phone conversation it rebooted itself once so far. and when my phone is stand-by, I found my phone is turned off.
I am not sure why it's happening. Is there any settings i shouldn't set?? or ???
Could anyone please tell me how to fix this issue?
If the phone is faulty, I need to make my phone as the same as when I first got which I am not sure how to :-( yet
The first thing to do is go completely stock. Flash the lastest stock rom and see if that fixes the problem.
When using ICS ROMs there's a known bug called Sleep of Death (SOD) that is similar to what you're experiencing. The phone simply won't turn on the screen and you have to press the power button for several seconds to turn it on again.
Almost all GNote users experience this issue so don't worry about it. Going back to stock will not solve the problem.
Hi
Thanks for the reply.
Before the rom v22, I had v19. my phone still did turn itself off several times. after flash the room v22, it didn't happen as many as v19 so I am not sure that the ICS causes the issue.
anyway, I will try the one you suggested and see how I go.
Thank you
kelvin fong said:
Almost all GNote users experience this issue so don't worry about it. Going back to stock will not solve the problem.
Click to expand...
Click to collapse
I am more worried about the alarm. if the phone turns itself off while i am in sleep, i won't be able to hear the alarm going off.
well if that happens again, i might have to get a alarm clock.
i was thinking of setcpu app might cause the issue... not sure though.
Thanks for your help
I experience the same issue when i was running stock. I've tried several stock versions but the problem still exists.
Sent from my GT-N7000 using XDA App
I have definitely never ever experience SOD when the phone is stock and lock.
The only time i did experience SOD is when i change to modded kernel.
I'm running stock with cf root and have never ever experienced this, so not all notes are affected. That would really suck!
Sent from my superior GT-N7000 using Tapatalk
Never had Sleep of Death on stock rom.
I am on stock ICS Rom n it has happenedwith me twice.
My GNote goes dead randomly and only starts up after pulling out battery.
Weird!
Install an ICS from Clean
Start from a Stock ICS rom using PC Odin, then follow my Post as follow :
http://forum.xda-developers.com/showpost.php?p=26772618&postcount=12
Try another rom other than that you had, or a higher versionof it.
The MIDTEAM v1.4.2 is Good and Stable.
Good Luck
I had this problem most of ICS ROMs on my Galaxy Note. SO I guess it's an ICS related bug and it is very uncomfortable to have to reset it to unlock it .
I too have tried several Stock ROMs but it still gets into the Sleep of Death at least once a day.
I guess that it should help to have a Kernel that changes the Deep Sleep settings...
Of my 2 GNotes, one of them had this problem. Happens when you put the note on the table with small drop or whatsoever.
The problem disappeared when inserted 3-fold 80g paper between battery and the edge of battery compartment. The battery tolerance is not so tight so when small drop (like putting on the windowsill) happens, the phone shut down.
The problem completely disappeared after inserting paper.
Of course, more professional would be go to Samsung repairs and show it and ask for replacement - either battery or phone internal casing. You can reproduce the problem by turning the screen on and dropping phone 10cm into hard surface.
But I did not bother.
I won't say that yours has exactly the same problem. But check the tolerances of battery 1st. Sometimes solutions are too obvious to see 'em.
I upgraded from stock to CM9 3 days ago and my Note has turned off several times a day since then. Never before upgrade, so I don't think it has to do with battery being loose in its compartment - not in my case.
I am loving ICS, but I will have to downgrade to gingerbread to get rid of this irritating bug.
this is happening to my galaxy nexus!!! yeah it turns off at random like sleep of death and small drops can trigger it. if i knew this could happen i would have never rooted
lol root itself has nothing to do with it.
if small drops cause it, and paper adding in compartment fixes it. its the gap between battery and whatever should fixate it.
if it occurs during deep sleep, dig into logs what you can find there. Also check roms/kernels feedback if others have it with that version. Many ways to illiminate possibilities.
I miss some good analyzes in this is issue from those experiencing stuff. Android I guess is not user friendly that way.
Sent from my GT-N7000 using Tapatalk 2
Galaxy Note Sleep of Death on 4.1.2 JB
I'm still trying to figure this out... I had hoped that with Samsung Stock upgrade to 4.1.2 it would be fixed but its not... anybody still experiencing this problem?
Things that I have tried
Move all apps from Internal SD Card (USB) and format
Factory Reset
Paper wedge between battery
Opened and re-connected all connectors to Motherboard
Install CPUSpy (deep sleep is OK)
I'm at wits end now, and this problem is very apparent. I havn't wanted to flash to a custom rom, because I've seen reported that it still happens with whatever ROM whether stock or custom
Any more ideas on how to make the Sleep of Death go away?
rasielbz said:
I'm still trying to figure this out... I had hoped that with Samsung Stock upgrade to 4.1.2 it would be fixed but its not... anybody still experiencing this problem?
Things that I have tried
Move all apps from Internal SD Card (USB) and format
Factory Reset
Paper wedge between battery
Opened and re-connected all connectors to Motherboard
Install CPUSpy (deep sleep is OK)
I'm at wits end now, and this problem is very apparent. I havn't wanted to flash to a custom rom, because I've seen reported that it still happens with whatever ROM whether stock or custom
Any more ideas on how to make the Sleep of Death go away?
Click to expand...
Click to collapse
What is the status of your phone now :
Working or not?
It works then it turns off by itself
Bootloop
Stuck on the white Samsung logo
Completely Off?
It does work but it turns itself of, the longest its gone without restarting is 44 hrs. I contacted Amazon where I bought and they are offering s full refund, so I , might send it back but I love it and had wanted tho keep it if the problem is fixed.
Sent from my GT-N7000 using xda app-developers app
Turning off problem too
I don't know if it is exactly the same problem, but my GNote keeps turning off every time, but not seem to be randomly. Looks like ti shut down every time a high performance is required. I tested several roms, ICS and JB, custom and stock, but the problem still goes on.
Please, any ideas?