Related
I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed
I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.
what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.
Try to flash a custom kernel and see if it the problem is still there
can you tell me or give information what's is 'flash custom kernel' ?
I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.
Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.
Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4
Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...
Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.
Anyone???
Maybe theres another forum that this problem should be posted at??
I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.
hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...
Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).
Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.
hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you
madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.
try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html
Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know
my turning off issue went back and it's getting every time more annoying, I don't know what to do...
Ok well I had a post before that I was having problems texting after update and root. well we thought it was the phone so verizon sent me a new one. I can receive perfectly fine but I cant send even on the new phone. I got the phone yesterday afternoon got it all set up on gingerbread rooted it then flashed with gingervolt v 1.2. Everything was working great last night then first thing this am bam no texting again. I got the v7 tot file and re flashed and it seems to be working again. For how long who knows but I am hoping someone may have a little info. Verizon has a ticket on it but something tells me it wont go anywhere.
jfl14609 said:
Ok well I had a post before that I was having problems texting after update and root. well we thought it was the phone so verizon sent me a new one. I can receive perfectly fine but I cant send even on the new phone. I got the phone yesterday afternoon got it all set up on gingerbread rooted it then flashed with gingervolt v 1.2. Everything was working great last night then first thing this am bam no texting again. I got the v7 tot file and re flashed and it seems to be working again. For how long who knows but I am hoping someone may have a little info. Verizon has a ticket on it but something tells me it wont go anywhere.
Click to expand...
Click to collapse
Are you using any 3rd party programs for texting or just stock?
I've had this problem before but only with a single person, my uncle, who uses AT&T (Only person with AT&T I text. AT&T has horrible service in my area so almost no one has them here) To make it so he'd receive my texts, I would have to completely delete my text thread and send a new message. He's the only person I've had problems with and deleting the thread fixes it every time.
Perhaps Re-flashing is working because in the process it is deleting your thread? Hope this helps!
I wish it were that simple when it goes it goes and i cant text anyone
So I am guessing no one has this issue with rooting or gingervolt? I am just curious because I love the speed and stability of gingervolt but I have been afraid that its somehow the cause. Now using the tot file v7 restores it to stock right so if it were a problem with the root or gv 1.2 this would get rid of it because its 100% stock right?
http://forum.xda-developers.com/showthread.php?t=1331603
Your previous post (For other users)
I've been lurking the gingerbread mod forums a lot and this is the first I've heard of this specific problem. Though that doesn't mean someone else isn't having the same problem.
You only get stuck when going into Gingervolt, but V7 seems to work for you? Have you tried staying in V7 w/o gingervolt for a few days just to see if the problem comes back or not?
Been on just straight v7 and it did it again man this is getting frustrating
I've had this problem on and off with the phone ever since i got it (so stock v4, R1.5, GV1.2). For me, it occasionally sits with the outgoing arrow moving, as if it were trying to send in area with no service. The workaround that i've used has been going to airplane mode which sometimes works, or more frequently, eating a reboot. Sometimes this results in them receiving duplicate texts. when i complained to Verizon they claimed it was common...
pendragon11 said:
I've had this problem on and off with the phone ever since i got it (so stock v4, R1.5, GV1.2). For me, it occasionally sits with the outgoing arrow moving, as if it were trying to send in area with no service. The workaround that i've used has been going to airplane mode which sometimes works, or more frequently, eating a reboot. Sometimes this results in them receiving duplicate texts. when i complained to Verizon they claimed it was common...
Click to expand...
Click to collapse
I used to have this issue, but it either resolved itself or something I did fixed it, but I have no idea what that something might have been.
I'm currently waiting on a replacement phone due to my USB connection no longer working, so we'll see if this problem makes a comeback. If you see me on IRC feel free to hit me up...I have some vague ideas as to what I might have changed that eliminated the issue, that's not a service guarantee though.
Looks as though its time to change forums. Verizon is switching me to a droid charge cant wait to see how this goes
I'm running 4.3 rooted on ML2, stock ROM. Within the last week I started experiencing a strange problem - after every single phone call made or received, I lose all network connection for about ten seconds. I get the circle with the line through it. Going into settings shows actual connection drop, not just the icon. Then, the connection reappears. I've made no modifications since rooting it in April, nor do I recall removing or freezing any apps any time recently. Powering down and/or removing the battery has done nothing to help.
Any ideas what would cause this? I can't find any threads here, or through a google search, discussing this problem. Any help is appreciated.
Update - same problems when running in safe mode.
Well, this seems to have been a local network problem, as the issue has magically disappeared. Nothing exciting to report.
fullboogie said:
Well, this seems to have been a local network problem, as the issue has magically disappeared. Nothing exciting to report.
Click to expand...
Click to collapse
Remove SIM card and clean?
Yep - did every trick in the book. Even reflashed via Odin to be sure I didn't have a corrupted radio file. It just started working again. I"ve seen the same problem reported in other parts of the country, apparently the result of something AT&T was doing to the network.
I'm hoping someone has experienced the same situation as I.
For some reason after making a phone call I get stuck on the screen that says the redial or message for like 30 seconds to a minute before I can make another call or back to home screen.
This Issue has happened On Rapture and Hyperdrive Tom. So that's telling me most likely an App is the cause of this issue. The weird thing is I haven't installed nor updates any apps for a couple days.(Auto update turned off in google Play. Everything was normal then out of no where this issue started.
Any help/ ideas/ fix will be appreciated and thanked
Any xposed mods that might cause this installed???
Also was this a clean install??
Which includes wiping the internal?
Flash.
Part of the Solution
Looking for help on this one. Every 3-5 days my Ultra gets into a state where no voice can be heard by either myself or the person on the other phone when a call is made or received, but I can hear the ring tone if I'm calling prior to the person answering, and my phone rings as normal if someone calls me. But when answering the call it's just silence on both sides. A reboot fixes this only for it to happen again 3-5 days later, requiring another reboot.
At first I assumed it was a corruption of the rom I had installed, so I flashed back to my stock image with Odin, including a fresh VOD CSC install. Unfortunately, it's still happening after this. Speaking as an engineer, it's unusual but not unheard of for a device to have a hardware issue of this type and it be rectified each and every time with a reboot, that would normally point to a software/firmware error of some sort. However, the fact it's continuing to happen after a completely fresh re-flash of stock Android suggests my worst fears that it is hardware. I could try some things, like not installing Magisk or even re-locking my bootloader, but I don't believe either would be a factor. I only used Magisk for rooting and don't install additional modules. I've also ruled out the sim card or sim slots by swapping to an e-sim, only for it to still happen.
Anyway, any suggestions would be welcome, especially if you have suffered something similar. There is an easy fix, which is to schedule a reboot every morning at around 3am, but I'd sooner not have to do this before working out what the underlying cause is.
I don't have a solution for you but I just wanted to share that I am having the same issue. But I'm not using Magisk and not unlocked, or rooted. The only thing I did was flash stock Samsung and disable some bloat.
I was having the issue the other night (for the second time) when calling my carrier (AT&T) about an order. I just assumed it was them at first. I disabled wifi calling (after them not hearing me several times) then tried again and it worked.
Were you using wifi calling at the time? I haven't been able to reproduce the issue yet so I don't know if disabling wifi calling had anything to do with it working.
Just to clarify, you say you're using Magisk but you're not unlocked or rooted? That isn't possible, but perhaps you just worded it wrong and you meant you're not using Magisk.
Funny you should mention Wifi-Calling, when it happened a few weeks back I force closed Wifi calling in an attempt to track down any potential services that might be causing the problem. And when I did that the calling started working again without a reboot. I thought I'd tracked it down and thought I'd test it again once it happened again a few days later, I would then freeze wifi-calling (something I never use) which would hopefully stop it ever re-occurring. However, the second time I force stopped wifi-calling it didn't fix the issue.
Beefheart said:
Just to clarify, you say you're using Magisk but you're not unlocked or rooted? That isn't possible, but perhaps you just worded it wrong and you meant you're not using Magisk.
Funny you should mention Wifi-Calling, when it happened a few weeks back I force closed Wifi calling in an attempt to track down any potential services that might be causing the problem. And when I did that the calling started working again without a reboot. I thought I'd tracked it down and thought I'd test it again once it happened again a few days later, I would then freeze wifi-calling (something I never use) which would hopefully stop it ever re-occurring. However, the second time I force stopped wifi-calling it didn't fix the issue.
Click to expand...
Click to collapse
I missed a word when I first replied. I added "not" to Magisk but you must have seen it before I fixed it.
I've had many work meetings (on phone) since then and haven't had it pop up. I haven't changed anything and even have wifi calling back on, so I'm at a loss.
OK, traced this to possibly be linked to the attached logcat. Any suggestions?
Also, contrary to my claim in the opening post, the dial tone can only be heard sometimes.
An additional oddity, whilst the fault is occurring (prior to a reboot), voice calls on WhatsApp work fine.
Perhaps a form of modem fault?
I give up on this. I flashed the stock VOD rom in Odin and relocked the bootloader to take it as close to stock as possible (minus the knox flag being tripped which is unavoidable at this point) and it still showed the issue after a couple of days. I've also disabled Bluetooth at a service level to no avail as I thought it might be a glitch with that.
It's clearly a hardware issue that will only be resolved with a logic board replacement. Which currently aren't available.
One good thing is that a full reboot isn't required to fix it, a soft reboot seems to do it. So I've got a link to do that on my home page, only takes 10-15 seconds.
Beefheart said:
OK, traced this to possibly be linked to the attached logcat. Any suggestions?
Also, contrary to my claim in the opening post, the dial tone can only be heard sometimes.
Click to expand...
Click to collapse
Hi, sorry to re-open this old topic. My S21 has the same problem from the beginning, but I have the stock rom. Did you get this log using *#9900# tool? Which log level did you use? Which file is the attached one? BTW, I'm almost sure that it's an hardware failure, did you solve it? Thanks
nrg84 said:
Hi, sorry to re-open this old topic. My S21 has the same problem from the beginning, but I have the stock rom. Did you get this log using *#9900# tool? Which log level did you use? Which file is the attached one? BTW, I'm almost sure that it's an hardware failure, did you solve it? Thanks
Click to expand...
Click to collapse
I'm afraid not, I ended up selling it as parts or repair a few weeks after that post.
Beefheart said:
I'm afraid not, I ended up selling it as parts or repair a few weeks after that post.
Click to expand...
Click to collapse
Thanks anyway, I will try to bring mine to the repair center.