Hi all,
I've had this really weird thing happen with my Vibrant for a while now. Whenever I am listening to any kind of audio with the headphone jack, at some point the phone will just.. die. Buttons don't light up, trying to wake the phone doesn't work, etc. I need to do a battery pull to get the phone working again.
It doesn't matter what I'm doing - as long as any kind of audio is being played (mp3s, streaming, etc), at SOME point, the phone will die. Oddly, this is kind of a random thing - while the phone DOES die at some point, guaranteed, there's mixed results in WHEN it dies. Sometimes it's within 10 seconds, sometimes 10 minutes, sometimes 30 minutes.
The logcat doesn't tell anything, either. You can watch the logcat running since the audio is going, then it just... stops.
Anyone run into this before? I'm running Frankin-Twiz Final (although this happened since Update3), JAC OC/UV/Voodoo kernel 1.1 (been going on since 1.0).
I'll try messing with Voodoo/no Voodoo.
EDIT: ([email protected] post) I tried just unplugging the headphone jack - looks like it's an actual audio problem. Playing any audio kills the phone.
Disabling Voodoo does nothing - phone died after about 20 minutes of playback.
Right now I'm underclocking the phone, I'll try disabling SetCPU.
strictlyrude27 said:
Hi all,
I've had this really weird thing happen with my Vibrant for a while now. Whenever I am listening to any kind of audio with the headphone jack, at some point the phone will just.. die. Buttons don't light up, trying to wake the phone doesn't work, etc. I need to do a battery pull to get the phone working again.
It doesn't matter what I'm doing - as long as any kind of audio is being played (mp3s, streaming, etc), at SOME point, the phone will die. Oddly, this is kind of a random thing - while the phone DOES die at some point, guaranteed, there's mixed results in WHEN it dies. Sometimes it's within 10 seconds, sometimes 10 minutes, sometimes 30 minutes.
The logcat doesn't tell anything, either. You can watch the logcat running since the audio is going, then it just... stops.
Anyone run into this before? I'm running Frankin-Twiz Final (although this happened since Update3), JAC OC/UV/Voodoo kernel 1.1 (been going on since 1.0).
I'll try messing with Voodoo/no Voodoo.
Click to expand...
Click to collapse
strictlyrude27 said:
Disabling Voodoo does nothing - phone died after about 20 minutes of playback.
Right now I'm underclocking the phone, I'll try disabling SetCPU.
Click to expand...
Click to collapse
Try a different ROM like Bionix.. Also, there is an edit button for a reason.. No need to double post
I have the same problem. Switched from frankin twiz to bionic. Like it more...but it didn't help. Believe it is a kernel issue. I recommend removing set cpu, that should do the trick. You can also flash back to a stock kernel.
Sent from my Vibrant.
MTC44 said:
I have the same problem. Switched from frankin twiz to bionic. Like it more...but it didn't help. Believe it is a kernel issue. I recommend removing set cpu, that should do the trick. You can also flash back to a stock kernel.
Sent from my Vibrant.
Click to expand...
Click to collapse
I uninstalled SetCPU and tried playing music continuously. Got a good 90 minutes out of this run, but it still fails as expected.
I'll try switching to a stock kernel in the morning. Thanks for the insight.
Related
I am from Hong Kong, using vibrant.
I found that my vibrant will get easily hanged/not responding, occasionally.
No matter which rom I flashed, stock, roms from eugene. (Applied/not Applied lagfix)
When my vibrant is not responding, the back of vibrant near the camara or next to the camara, will get hot and hotter.
After a long press of the power button, for a hard reboot of the vibrant, the vibrant will be fine again. However, the situation repeat.
So, I want to figure out that is there anybody encountering the same situation.
Thanks.
I have not had this exact problem, but I have had mine randomly go black. It's done it 3 times in the 4 days I have had it. When it goes black, you can't turn it on, power does nothing, and you have to pull the battery to start it again. I have never let it sit long enough to see if it gets hot.
I have heard mixed thoughts, some people claim it's hardware problem, some say its a firmware problem =/
I've seen my screen turn black with just the key backlights remain on. The device becomes and remains hot to the touch as if working very hard (drawing heavily on the battery and CPU) but it never responds again. Holding down the power button for a full five seconds resets it.
In my case, I typically see this happen while I'm trying to use Google Navigate (GPS) while also running Pandora (streaming radio) in the background. Often it works, but often it doesn't, especially on days with warm weather. I've monitored battery temperatures around 114 degrees F after rebooting.
I suspect it is related to the problems with the GPS (fixed to use supl.google.com) and very much hope it will be fixed with the promised OTA upgrade. Although I may have seen it a few times (very few times) without GPS. My other suspicion turns toward a process called mmcqd which seems to run heavily at times. Perhaps the lagfix will help with this "Multimedia Card Queue Daemon" process. ::shrug::
Just offering this as notes to compare. I'm curious if others see the problem with GPS disabled? Or if you notice the mmcqd process maxing your CPU?
I've noticed that when using GPS, only when the GPS gets confused.. say for instance that I'm driving, get out of my car with a Navi program still running and walk inside of a building/house.. bam, phone is dead with the buttons lit.. I've decided to not bother with GPS.
If you're having those types of issues try avoiding background sync with the forever sluggish stock eMail app, and don't load up the internal memory with a lot of junk.
having the same prob... cant find the solution .. do u have any?
This happens to me on my stock vibrant everytime I try to use the maps program. On the off chance I get it to start working, as soon as it shifts orientation to landscape mode the whole thing will lock up. Usually I have to remove the battery to get it to reset. As was said, it appears to be caused by the faulty gps, so I usually just leave mine off.
However, I haven't noticed it happening while doing anything else and I'm hoping the upcoming ota update fixes these issues. (Don't want to bother with rooting stuff until I'm on stock 2.2)
The solution is to install the leaked update that we should be getting officially very soon. No freezing, no serious lag (installing apps will lag almost any Android device), no black screen freeze ups, much improved GPS, I'm lovin' it.
I installed Cyanogen Mod7 on samsung vibrant, after reboot the set not started, only samsung logo shows but not booted further, plz give the solution.
heygrl said:
The solution is to install the leaked update that we should be getting officially very soon. No freezing, no serious lag (installing apps will lag almost any Android device), no black screen freeze ups, much improved GPS, I'm lovin' it.
Click to expand...
Click to collapse
Hey, did u get the update or solution?
I noticed that my NT seems to emit a faint "clicking" noise every few seconds when the tablet is on but in sleep mode.
Anybody else experiencing this?
Does not seem to happen while the screen is on, only when the screen is off. Also seems to disappear when WIFI is turned off.
Just wondering if somebody can check their NT and see if they hear the same thing... need reasonably quiet surroundings.
Now that you mention it, I have also noticed that. I believe I was running stock 1.4.1 at the time. Currently back on 1.4.0 and I haven't heard it...
Thanks for the info, I am on 1.4.1 myself (out of the box). I'll wait in hope for some more feedback and if it seems to be the case, I'll drop down to 1.4.0.
Haven't heard it but it could very likely be a B&N program that is running in the background. Perhaps it has something to do with the 1.4.1 update and the frequency of the wi-fi checking for updates?
Actually, I need to retract my earlier statement. I was just listening to music so I had my headphones in. Sure enough, when I kicked it into standby, the clicking came back.
Going back to 1.4.0 does not solve the issue.
My OTA timer is disabled...
So that makes two cases now... I am wondering if all NT's are doing this. I kinda PO'd I just got my Otterbox and spent great effort getting my screen protector on nearly perfect.
Never heard this before because my NT's speaker sat flat on whatever it was sleeping on. But the Otterbox elevates it, so I started hearing the clicking when it was sleeping on the table beside me.
If it's a common bug on all NT's... hopefully CM7 will resolve it!
Ok I am hearing it and it is not a constant click either its quite random for me. But I am not going to let it bother me at all to be honest.
I haven't heard anything like that with mine I'm running CM7 and i get a slight pop in my earphones when audio kicks in but nothing major.
Probably because CM7 has different WiFi settings... it's definitely tied to the WiFi. AdamOutler suggested tweaking the Wifi .INI file and it has made the clicks more apparent (it's the WiFi kicking in and out).
Hopefully he can find the way to get it to sleep properly... and thus save battery!
Rooted 1.40 and I have not noticed any clicks.
Bill
Bill, if you can try plugging in some headphones and then going into standby/sleep... the clicks are more pronounced through headphones.
I noticed the click as well, this also happens to my PC LG monitor and my LG Optimus 2x when using the headphones.
Rooted 1.4.0
F. Gacrux said:
I noticed the click as well, this also happens to my PC LG monitor and my LG Optimus 2x when using the headphones.
Rooted 1.4.0
Click to expand...
Click to collapse
Does yours occur about once or twice every 2 seconds or so?
quid246 said:
Does yours occur about once or twice every 2 seconds or so?
Click to expand...
Click to collapse
No, only when I press wake up button or when the sound stop/begins.
I'm not sure, but maybe it's the headphones? Too much coincidence to happen on 3 different devices here.
I user Razer Moray earphones, it has noise canceling something built in, maybe this is the culprit. I have other Philips earphones laying around, I'll test them on the tablet to see if this happens too.
Hi I am rooted...not running the CM7 yet...but I have noticed it when I have the the sound muted and I am playing words with friends. This was also doing it before I was rooted as well. I have not noticed it sleep mode. this only happens though for me when I have all sounds and notifications muted.
F. Gacrux said:
No, only when I press wake up button or when the sound stop/begins.
Click to expand...
Click to collapse
Put the tablet into sleep/standby mode (using short power button press) with WiFi on and no music playing and see if you get the click every few seconds.
quid246 said:
Put the tablet into sleep/standby mode (using short power button press) with WiFi on and no music playing and see if you get the click every few seconds.
Click to expand...
Click to collapse
No clicks on sleep/standby mode under these conditions.
Either it's a problem on some NT's or not everybody has good ears.
hmm ok now I am not getting the clicking and I have not changed any of the settings or anything on the tablet. So I do not know how it vanished but it has for now.
Rooted 1.4.0 and I hear the clicking with either headphones or if I plug it into an external speaker.
Just bought a second hand GS3 from ebay, the screen had a small crack but otherwise was meant to be OK. I put Foxhound ROM on (I'm just used to having to upgrade the rom) and am finding that the sound will work fine after a restart, but then, after it has gone to sleep all sound will stop working.
I've tried clean wipes/formats etc. and also checked all relevant settings I could find (including turn off all sound in accessibility, what an odd option).
I've tried two ROMs and three kernels.
I've tried searching google and xda for hours but haven't found anything that wasn't related to the headphone port; this affects both speaker and headphone, although when the headphone is in and the sound has died I can hear some strange static noises when it's meant to play sound, could be interference or a clue.
I've dismantled the phone and inspected for damage, nothing obvious. While dismantled I tried applying pressure to the speaker flex cable and various other IC's to no effect.
It really seems like a software glitch since it only happens when the device goes to sleep;
You can turn the screen off and unlock within 3 seconds and it will be OK.
If you wait 5 seconds with the screen off - boom, no sound.
Any ideas? Is there some deep idle sleep setting that kicks in after 3 seconds I can disable or some way to log audio errors or... something?
Thanks
defroster said:
Just bought a second hand GS3 from ebay, the screen had a small crack but otherwise was meant to be OK. I put Foxhound ROM on (I'm just used to having to upgrade the rom) and am finding tht the sound will work fine after a restart, but then, perhaps after it has gone to sleep once or twice (never more than a few minutes unless I'm plying a game, in which case it stays on just fine) the sound, all sound, will stop working.
I've tried clean wipes/formats etc. and also checked all relevant settings I could find (including turn off all sound in accessibility, what an odd option).
Any ideas?
Click to expand...
Click to collapse
May Be The Phone Was Damaged, Try Stock ROM
i'm downloading a different ROM now but it takes hours (rural australian phone lines...)
same result with a different ROM =/ I've fixed many phones, computers etc before but not sure what to investigate here, guess i'll dismantle it and see.
A second rom and kernel same result.
Seems to lose sound as soon as it goes to sleep (screen off), really seems like a software problem but can't find any other reports on this phone similar.
Help!
Anyone?
Looks like a software problem but can't say where you can look.. If kernel is not the cause..
Maybe hardware after all..
sent from here, there, somewhere!!
The only way I can imagine it being hardware is if it's heating an audio ic during boot to make a connection and then when sleeping it cools and the connection is lost. It's a long shot but if it's software why is it not happening to anyone else? No weird software installed or anything.
defroster said:
The only way I can imagine it being hardware is if it's heating an audio ic during boot to make a connection and then when sleeping it cools and the connection is lost. It's a long shot but if it's software why is it not happening to anyone else? No weird software installed or anything.
Click to expand...
Click to collapse
Does the sound still work through headphones (after the sound stops working)?
Sent from my GT-I9300 using Tapatalk 2
no, it doesn't seem to be headphone jack related.
the only thing I changed (aside from the rom) that I can think of that MAY have done something is some network setting for my carrier (vodafone .au) - there was an option in foxhound rom or something, but I can't for the life of me remember what it was called, I googled it at the time to see what it was but have since lost the browser history, it was some feature of the phone network that stops sending requests to the network when the phone is sleeping or some such... I'm really grasping at straws there though.
can't seem to find a stock rom for Australia either?
updated OP with more info, sorry for the bump, i'll let this die if no-one's got any ideas.
defroster said:
no, it doesn't seem to be headphone jack related.
the only thing I changed (aside from the rom) that I can think of that MAY have done something is some network setting for my carrier (vodafone .au) - there was an option in foxhound rom or something, but I can't for the life of me remember what it was called, I googled it at the time to see what it was but have since lost the browser history, it was some feature of the phone network that stops sending requests to the network when the phone is sleeping or some such... I'm really grasping at straws there though.
Click to expand...
Click to collapse
I think you are talking about fast dormancy toggle.. But I do not think it will cause any problems.. Also as you have already done factory resets an app should not be a problem..
I can only think of hardware faults..
sent from here, there, somewhere!!
yes i just finally remembered it and tried disabling, you're right, no difference.
I'm having trouble figuring out how hardware could be the culprit though, since it's triggered by the screen off for more than 3 seconds, there's something in software causing it.. but you're right, why does it persist over a wipe then? argh!
Downloaded stock rom, problem remains
I've had my phone for a few months now and up until recently it had no issues. It's unlocked but not s-off and I had been running cyanogenmod 10.1. When the 10.2 nightlies came out I began using them and until around 9/15 these worked great. I didn't suffer from the flickering or radio issues at all. Around that time I started noticing that my phone would occasionally shut off on its own. I thought that it was an overheating issue at first but as the problem worsened it became clear that it would happen cold. It's now at the point where it predictably happens within a minute of the phone being on, leaving the phone essentially useless. I've tried narrowing the CPU frequency range and going back to the stock ROM, neither of which has resolved the problem. Investigating logcat and bugreport didn't reveal any hints to me as to what was happening. I'm worried that it's a hardware issue but recovery and bootloader seem to be able to stay on indefinitely which gives me some hope. Does anybody have some input on additional things that I could try?
Start simple... Battery good? Battery contacts good?
j13smiley said:
Start simple... Battery good? Battery contacts good?
Click to expand...
Click to collapse
Yeah, I'm fairly sure that it's not a battery issue. The same thing happens when it's plugged into a charger and the phone will stay on in recovery regardless of me moving it around or letting it sit for long periods of time.
I have noticed something new though. If I don't enter my Google account information (doing so starts app syncing) then the phone is much more stable. It seems that I can do a simple task like turning on wireless tethering and then if I don't do anything else the phone will be stay on for hours. If I open the browser, the play store, or start moving icons around then I only have a minute or two before it will shutdown.
Removed
foobster said:
Yeah, I'm fairly sure that it's not a battery issue. The same thing happens when it's plugged into a charger and the phone will stay on in recovery regardless of me moving it around or letting it sit for long periods of time.
I have noticed something new though. If I don't enter my Google account information (doing so starts app syncing) then the phone is much more stable. It seems that I can do a simple task like turning on wireless tethering and then if I don't do anything else the phone will be stay on for hours. If I open the browser, the play store, or start moving icons around then I only have a minute or two before it will shutdown.
Click to expand...
Click to collapse
Updating to a newer 10.2 nightly might fix the problem. Otherwise get the last_kmsg file when it shuts down next time and post it here. Someone might be able to diagnose the problem.
durgis said:
Updating to a newer 10.2 nightly might fix the problem. Otherwise get the last_kmsg file when it shuts down next time and post it here. Someone might be able to diagnose the problem.
Click to expand...
Click to collapse
Thanks for the input. I'll give a newer 10.2 nightly a shot but I am seeing the issue on builds that had previously worked fine (stock and 10.1). I have no /proc/last_kmsg after an unplanned shutdown. Based on what I'm reading this might mean that it's locking up before there's a kernel panic?
two options
j13smiley said:
Start simple... Battery good? Battery contacts good?
Click to expand...
Click to collapse
Flexcard usb or your mainmotherboard is or going out
Hi all
I've got a strange issue with the headphone jack, I've searched and can only find people complaining about one channel not working.
I'm getting sound out of both channels but after 30sec - 1 min the sound cuts out, the music app still shows it's playing but no sound, it doesn't matter if i pause and resume, remove the headphone and re insert.. the only way to get it back is to reboot and then it works for another ~30 seconds.
I thought it was to do with dirty flashing 10.2 nightlies, but i did a clean install and it still happened, I've got omnirom installed now and it's still happening with that..
I'm not using any custom kernal. (maybe i should try one)
I don't think it's a connection issue, becuase if i keep the phone completely still without moving he headphone cable, it still happens
I did pull the phone apart and check the flex ribbon and connection just to be sure, but didn't see anything strange.
I have tried 4 different pairs and it's happening with all of them.
Not sure if it's hardware either, I thought the amp chip might be faulty. the loud speaker works fine, does anyone know if they are using the same chip to drive them?
I'm all out of idea's as to what it could be..
last thing i was going to try was to restore the phone back to 100% stock and start from scratch.
Have the same problem here:
If with headphones i put the volume to max, in some time we have the same problem, no sound at all, but... if i use 10 or less volume in the headphones is working without problem.
Sometimes just don't have any sound at all, whyout doing anyting, and all i can do is leave playing some music with headphones and in minutes i recover sound.
Sometimes hear something like interference or distorted sound.
djmickyg said:
Hi all
I've got a strange issue with the headphone jack, I've searched and can only find people complaining about one channel not working.
I'm getting sound out of both channels but after 30sec - 1 min the sound cuts out, the music app still shows it's playing but no sound, it doesn't matter if i pause and resume, remove the headphone and re insert.. the only way to get it back is to reboot and then it works for another ~30 seconds.
I thought it was to do with dirty flashing 10.2 nightlies, but i did a clean install and it still happened, I've got omnirom installed now and it's still happening with that..
I'm not using any custom kernal. (maybe i should try one)
I don't think it's a connection issue, becuase if i keep the phone completely still without moving he headphone cable, it still happens
I did pull the phone apart and check the flex ribbon and connection just to be sure, but didn't see anything strange.
I have tried 4 different pairs and it's happening with all of them.
Not sure if it's hardware either, I thought the amp chip might be faulty. the loud speaker works fine, does anyone know if they are using the same chip to drive them?
I'm all out of idea's as to what it could be..
last thing i was going to try was to restore the phone back to 100% stock and start from scratch.
Click to expand...
Click to collapse
evilkenshin said:
Have the same problem here:
If with headphones i put the volume to max, in some time we have the same problem, no sound at all, but... if i use 10 or less volume in the headphones is working without problem.
Sometimes just don't have any sound at all, whyout doing anyting, and all i can do is leave playing some music with headphones and in minutes i recover sound.
Sometimes hear something like interference or distorted sound.
Click to expand...
Click to collapse
I will try with the volume lower, I'm sure I've done this but I'll recheck.
And, I'll try leaving it running for a few minutes.
EDIT: just tried it now and it still happens at lower volumes, if i leave it on it does come back after 1-2 minutes but only stays on for a few seconds, the lower i have the volume the quicker it does seem to return but only for a brief moment..
I'm flashing the Siyah kernel now with Omnirom.. i'm out of idea's.
Sent from my GT-I9300 using Tapatalk
Please post questions in q&a. General is not for support threads
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
Please post questions in q&a. General is not for support threads
Click to expand...
Click to collapse
how can i get it moved there?
djmickyg said:
how can i get it moved there?
Click to expand...
Click to collapse
118 use the red report button