I'm having an issue with my phone. I was on a conference called and 2 times at 15:30 or 16, the phone cut off. It still acted like I was connected, but there was no audio. Then last night, I talked with someone for 15:30 minutes and the same thing happened. Anyone else seeing this?
Related
Since I have that blue tooth patch from tobias, (the one with the little problem of no audio on headset) my machine is really saving energy, I am no on the GPRS bar on 8 hours and 30 minutes, before it was only 5 hours and 45 minutes if I took it out of the craddle.
Did anybody else noticed this
*repost from PPCgeeks*
This just started happening within the last couple hours. I haven't recently installed/uninstalled ANYTHING, haven't messed with any settings, no reg. edits, nothing at all. When restarting, I notice that sometimes it takes longer that it usually does to load my today screen. I'm noticing no differences in RAM at startup. I notice, for example, going back and forth between tabs on HTC home, the phone will freeze for a couple seconds and resume working normally after that. When receiving a phone call, it takes FOREVER for it to respond when trying to accept or deny the call. While in a call, it responds terribly slow when trying to raise/lower volume. Sometimes going from portrait to landscape and vice versa even takes longer than normal. I've had ZERO problem with my Mogul since I first got it 4 months ago and now I'm ready to throw it out the damn window. What's the word guys? I can go on about a couple other things that the device is slowing on, but I think you guys get the picture. TIA.
On another note, I first noticed it doing this when I plugged the device into my car charger. After that, regardless of being on battery power or external power, it was sluggish like never before. I noticed today, my battery died faster than usual. About 1.5 hrs ago, it was at 40% charge, and within less than an hour it dropped down to 10%. I had data turned off all that time and I still noticed the battery drop as well as hotter than normal backplate. Could it be something with the power source? I remember once, quite awhile ago, my phone totally died and after I charged it for a bit and turned it back on, it ran the same way, hhhmmmmmmmmm.
Since I have got it (2 weeks ago) i have picked up my phone make a call, and on about 7-8 occasions, have noticed that the phone is turned off, and I can't get it to turn on. The only solution is to take out the battery and put it back in. Has anyone else experienced this. I have updated to JH2 firmware, but it still happens. I even got a new battery for the phone (Bell employee let me swap with another phone that was going back to samsung for gps issues), but the problem still happens once in awhile (like every 2 days, sometimes more sometimes less). Anyone have any ideas? thanks
UPDATE: Someone mentioned for me to call my phone the next time this happens to see if it rings. They said it might stuck in sleep mode? Not sure, i just pullthe battery and then it works
I've had this happen, but only when the GPS was on. If it's happening with the GPS off, I'm guessing you've got a lemon.
So far I've not needed to take the battery out, though. I've always been able to reboot by holding the power button down for 5-10 seconds instead.
Yes I have been experiencing the same problem. From what I can see, it seems like the phone is over heating then it locks up. My only fix was to install a battery temperature monitor and also kill any tasks that are not needed by the phone. My phone hasn't locked like that since I've been doing that.
Sent from my GT-I9000M using XDA App
I have not had this problem. Been on a call for about 1-2 hours one time and the phone was fine. I was able to switch it to speaker, bluetooth, open other apps, and etc without any problems. I don't run task managers. I do have one, but I rarely use it.
Interesting...I experienced this for the first time today. Picked up my phone from teh night stand after having it plugged in all night and it was off. Had to pull the battery to get it to come on. The battery was about 85% charged when it came back on. It worked ok since but the battery drained kinda quick. I am using an aftermarket battery, got the 2 batts and charger on ebay. So I put the other battery in and havn't had any issues. I wonder if it over heated while charging? What apps are you guys running? The one I am running that would be most suspect would be weatherbug elite, and I just installed it a day or 2 before this happened.
I think it is a GPS issue. I got this phone on the first day of release. I’ve never had this problem until just days ago. I hadn't used the GPS extensively before last Thursday and Friday. During my business trip I had the GPS on for almost two days straight and during these two days I experienced the blank screen, shut down twice. I had to cycle the battery to get it to boot.
I had this happen to me while using Set CPU. Check out this thread. http :// forum.xda-developers.com/showthread.php?t=727006
take out spaces and what not.
I had this problem on my g1 but it started to get worst an I soon need too keep my mobile always connected to a charger so out turned into a landline phone lol but it was because I somehow broke a middle cell in my battery and need replacing but I don't know what to say about yours cause you tried a different battery :S
Sent from my T-Mobile G1 using XDA App
Experienced a freeze just a few hours ago while running the navigate application.
Trying to show my wife how uber cool it was and all. Switched on GPS, launched maps, chose directions, method / navigate. GPS locked and had my location pinned down until I reached the corner and suddenly the GPS kicked me to a location about 5 blocks away then froze the phone, requiring a battery pull and reboot.
Sent from my SGH-T959 using XDA App
I had this problem of noticing my phone is turned off at random times (usually once every 2-3 days). I would pull out to use my phone, and its off. I tried calling my phone to see if maybe it was just stuck in sleep, but it went to voice mail. This is very annoying because i cannot rely on my device to be on when it should be (ie- for an alarm) The only way to get it back on was to either re-install battery or hold down power for about 10 seconds. This is my 3rd SGS and it happened on the 1st one and the 3rd (only had 2nd one for a day).
I just realized today (after the 6th time it happened in 12 days), that it only happens to me at places where i have no signal. It happened at work 3 times (where i get no reception), and once in the forest where i was bikeriding. I was in an area that showed no signal, and shortly after the phone was off. (it doesn't make any shutdown noise or anything, I just realize sometimes the phone has randomly turned itself off.
Could reception have something to do with this? Now that I think about it, the 1st phone i had also turned itself off at work....never at home. Will 2.2 fix this problem? Any advice would be greatly appreciated.
check your battery
did you flash any ROMs ?
Were you using SetCPU at all?
SetCPU mischief
My galaxy s was having to be shut down and having to have the battery removed to turn on again in all sorts of situations and I blamed all sorts of causes but in the end it came down to various clock speed issues. Now I'm running a minimum of 200
The phone was charged at 95% or around that percentage. This hasn't happened to me before, I hadn't just installed any apps, I'd barely done anything with it since I'd just woken up.
I had a timer going on the phone, went to check it to see how long I had left and then when I pressed the power button to unlock the phone, it didn't unlock or do anything. Then I did a quick google search and saw people saying that holding it down for about 30 seconds would turn it on.
I did so and it turned on as it it had been shut down (which I didn't do) but the time was 1am (wrong) and the date was sometime in 1970 (definitely wrong)!
Has this happened to anybody else? Does anybody know why this happened? Any solutions? It's never happened to me before so I'm just concerned at the moment.
LPX4 said:
The phone was charged at 95% or around that percentage. This hasn't happened to me before, I hadn't just installed any apps, I'd barely done anything with it since I'd just woken up.
I had a timer going on the phone, went to check it to see how long I had left and then when I pressed the power button to unlock the phone, it didn't unlock or do anything. Then I did a quick google search and saw people saying that holding it down for about 30 seconds would turn it on.
I did so and it turned on as it it had been shut down (which I didn't do) but the time was 1am (wrong) and the date was sometime in 1970 (definitely wrong)!
Has this happened to anybody else? Does anybody know why this happened? Any solutions? It's never happened to me before so I'm just concerned at the moment.
Click to expand...
Click to collapse
I have had my new Nexus 4 turn off on it's own numerous times, but the battery had always been low.. Give or take 40% battery or lower. I ended up calling google up and they are sending me a replacement device. I should be receiving it sometime today actually.