I've been having this problem for about a month now. The phone would soft reboot. I think it soft reboots because I see the following:
1. Phone locks up for a few seconds.
2. All apps restart including my LauncherPro.
3. All widgets try to update.
4. Cell Signal is lost for a few seconds.
5. Media Scanner starts to scan for media files.
6. I hear the boot sound, eventhough the phone doesn't completely reboot.
My phone is rooted and has Voodoo V0.2 Kenrel installed (not the OC one).
I also noticed that it soft reboots more often after I turn Bluetooth off in my car when the phone is connected to the car stereo and streaming audio.
I wonder if anyone know what is wrong with my phone or if they have experienced this issue before on the Samsung Fascinate or any other android phone.
I see the same thing sometimes when turning off bluetooth when connected to my car stereo. In addition to the symptoms you mentioned, I hear the boot sounds, even though the phone doesn't appear to completely restart. My phone is completely stock, never rooted.
Yes, I do hear the boot sound too. I forgot to mention that.
Maybe try one of Dirk's D02 kernels? My phone soft rebooted yesterday, but that was because I flashed the ota radio. It's been fine since.
However, it COULD be a problem with the DI01 update, since it is happening to a non-rooter as well.
Just some thoughts.
Sent from my Fascinate using the XDA app
This issue has been fixed in the DJ05 update.
Related
Hi,
I have seen this in some threads, but I have not seen any solution.
I have rooted my X10a phone to R2BA023 and now, the phone takes a long time to recognize I have inserted a headphone, routing the audio to the external speakers.
I do not have this issue when I am using bluetooth, jst my normal headphones.
Anybody has a solution for this?
It happens to me too. It is kindda fixed (version 20 had a huge problem with headphones) but it is really slow to pickup the headphone signal
I don't know if it is time based or software based
Things I do that SEAM to work sometimes:
force close mediascape and re-open
boot with headphones connected,
turn media volume all way down, pause, play and turn it back all the way up.
wait for a minute or so
I don't get what turns it on. I thought it was fixed.
I'm having no problem, of course I force close most apps, including mediascape as soon as I boot up.
By the way, I do not use mediascape. I use 3 (cubed).
I usually force close most of my apps also.
I have not use the delete step of the rooting tutorial.
mine is working fine b4 and after rooted! is there something wrong with your headphone jack?
I'm rooted on R2BA023, using 3(cubed) as well. Use it everyday for 3 hours or so (1hr drive to work each way) it works instant for me, I did a check yesterday after seeing your thread. Might be a hardware issue??
I'm having the same issue. I know my headphones worked with the first root, but when I upgraded to R2BA023 is when they stopped working.
I noticed that if you restart the phone with headphones plugged in, they work, or if you leave them plugged in for like 2 minutes, they start working fine.
chris_knows said:
I'm having the same issue. I know my headphones worked with the first root, but when I upgraded to R2BA023 is when they stopped working.
I noticed that if you restart the phone with headphones plugged in, they work, or if you leave them plugged in for like 2 minutes, they start working fine.
Click to expand...
Click to collapse
I don't know about the restart with the phones plugged, but my headphones worked just fine with the R2BA020 root and they start working just after sometimes, this happenning not moving the phone or the headphones at all.
Just tried the restart. It just works after some time also.
I have no probs whit mine done rooting and did it at the first time
Sent from my X10a using XDA App
My rooted EVO 4G running baked snack 1.8 is having the following issues, and they seem related as they started happening at the same time:
Cannot change headset volume (when volume rocker is pressed, graphical slider moves, but audio stuck at a low-to-medium level)
Car Mode launches sporadically without reason, even when phone is locked (had to turn off "auto launch" to stop it from popping up...it's as if the phone thinks it's being plugged into a car dock, which I don't own)
When sending/receiving a call, the external speaker turns on, I have to shut it off each time I answer a call (SO DAMN ANNOYING):
SOME MORE INFO:
This all started happening at once while I was walking down the road listening to music on my phone (i.e., no software was downloaded/changed)
I have done a nand restore to a previous point where there were no problems and the issue persists
It's not because of baked snack. This happened to me once before when I was running the stock ROM, but one day it just suddenly fixed itself. But it's been weeks and I'm tired of it.
ANY IDEAS??
auto speakerphone
I'm having the SAME issue with the speakerphone...
Almost got into BIG trouble today when called for an interview WHILE AT ANOTHER JOB!!!
PLZ HELP! I'm running Vaelpak ReMastered 3.0
I FIXED IT!! Just yesterday actually. If your problem is the same this might help you too...
First: Are you running a custom ROM like baked or fresh?..
I was running baked snack 1.8. I figured this was a hardware issue from the start....This problem became REALLY obnoxious so I finally decided I wanted to take the damn thing back to Sprint to get a warranty exchange. But, in order to not void my warranty I had to unroot the device (obviously). So here's what I did:
[link got crushed, I'll give you my email if you want the link to the 2 Step Unrooting Method]
That's a two step method to unrooting the EVO. I followed it to a T but ran into an issue: For some reason if flashed the S-ON file and THEN flashed the Stock RUU provided (as the directions TELL you to do) it would give me an error message that read: "Failed! Main Version is Older!" ... Try it their way first, and if you have that same problem, do this:
Run unrevoked in order to turn S-OFF again.
Put the PC136IMG.zip on the root of your SD card
Boot into Bootloader
Your S will still be OFF but at least you can flash the original image to back to stock (which will give you the chance to see if it's a hardware or software issue). Once I did this, the problem was resolved!! So, I got antsy and reflashed Baked 1.8 on the phone, and it worked perfectly until about 15 minutes in when Car Mode activated and calls were suddenly going automatically to speakerphone again. I was pissed. I assumed, once again, a hardware failure.
SO! Just to confirm, I reflashed the stock image AGAIN, and left it there. I've been running the phone for 24 hours so far and it lets me adjust volume, doesn't go into car mode, AND best of all the calls start (and STAY) on the internal speaker as they should.
I'll update if the problem comes back again, but it doesn't appear that it will. I still have S-OFF, but i think i'll stick with the stock image for a while considering the problems baked snack gave me (or so I hope).... Let me know if you need more help.
I just flashed myn's new ROM and car mode does the same thing to me! It's starting to make me so mad!
Does anyone else's MT4G randomly restart on them? Mine does it all the time...I'll click on messages and the phone will freeze and then restart...it will do this 1-2 times a week, and it isn't just when I click on "messages" either, it'll do it randomly.
Sometimes I'll have my phone in my pocket and feel it vibrate and take it out and it's on the "MT4G" loading screen.
It happens to me too, but it seems to happen much more in CM7 than the stock ROM. Not sure what causes it, but I don't know if there's any fix at all.
Well I'm on stock rom...so that really sucks cause I was just lookin into flashin a rom LOL
What i've seen is that it's a memory overload glitch in CM7 I haven't heard about it in stock. but for instance on cm7 your running music gps and want to make a phone call then boom it resets. It thinks it's out of memory so it reboots to close all processes and to regain RAM. I personally don't think it's running out of memory I think it has a mis configured default but that's just me. Hope that helps
-Nic
Mine does it in CM7 when I'm listening to music with either the headphones plugged in, or the ipod cable in the car plugged in.
I know I have seen a thread about this before but I can't recall if it was on XDA or perhaps Droid Life; XDA seems to be the generally more knowledgeable group of people so I thought I would ask here.
I experience frequent lockups and or reboots (I know one causes the other, so...) when doing most anything media related. They are related but come in two different varieties:
1. Music Playing. I typically only play music while on an airplane and most of my flights are at night, so I will try and load a playlist then lock the screen. Almost always I will get through about half a song and the phone will reboot. Testing has revealed the reliable way to cause this is simple: Start a song, lock the screen, turn the phone. It wont wake back up and if it does it will freeze until it reboots or you pull the battery.
2. Movie Playing. Since I obviously don't turn off the screen while the movie is playing, the above is not an issue. Sometimes - but not all the time - while using the built-in movie player the phone will be completely unresponsive. I cannot pause, stop, or change volume. The movie will continue to play just fine though. I haven't tested what happens when the file ends as I usually notice it near the beginning of a file and must have the ability to pause it. There's no reliable way to get this to happen, although it almost always happens while in-flight (again, the only time I really use it, so that doesn't mean anything).
I know other people have experienced these issues before, but are there any reliable SOLUTIONS? I have rooted before, before the 2.3 update. The 2.3 update bricked the phone and I SBF'd my way back - root was gone. I re-rooted some time later, then undid the root in order to use Flixter. Just yesterday I did the .621 update and again bricked the phone, SBF'd back to life again. I'm not ruling out the history of rooting to have causes these issues, but I'd like to fix it if I can.
Thanks to all!
Hi all,
Hopefully someone can help me out with this issue I've been having with my Galaxy S3 Neo.
Some time ago my phone started to randomly crash internal android services and processes. It kept working after reboots until up to a point. The things that didn't work properly were Music apps, phone and (so I figured) all apps that somehow are connected to audio. A factory reset did not fix my issue.
I brought my phone to a local repair shop and they fixed it with some sort of factory reset, which they told me was done over reinstall by PC.
It worked for a few months and I had no problems at all.
Now, since a few days, my phone starts acting up again.
I don't get the crash reports like I used to get, but it's 'dying' nonetheless.
It started with the Facebook app not working anymore, it kept 'looping' the 'setting up facebook'-message and crashing the locations process, so I deleted the app.
That helped for a bit.
Now:
- I can't call anymore, it hangs.
- I can't listen to music, it hangs.
Again, any sound/audio related apps make my phone crash or hang.
The Music app, I can start it up, press play and it just doesn't respond. It says it's playing, but the counter remains on 0:00.
The weird thing is, that when I hook my phone up to my Bluetooth car stereo, it plays music fine.
It seems that whenever the phone is trying to connect to the speaker, it has issues...
A factory reset through settings didn't fix it, and neither did a hard reset in recovery mode..
Help is required!!! Please!!!!
I tried CWM, wiping everything, put CM12 on it, but no luck. Could it be that the speaker(s) is (are) dead and Android can't work properly when that happens?