Hi, having thought my s3 may have been showing early signs of sds, it certainly has symptoms related to it but there's some other weird stuff going on which I've never seen anyone else mentioning on here.
I've had static come out the internal speaker during the Samsung boot logo, instead of hearing the little tune that plays, I've also had that tune play but at a very low tempo, sounds very weird when it does that. While the phone was idle earlier the speaker decided to throw out more static so while it was happening I started up the music player app and selected an mp3, the static pretty much stopped when the mp3 started playing but the song was playing at a very low tempo, incredibly slow, just like I've experienced during boot with the Samsung logo animation, I tried a few more mp3s, they all played at a very low tempo, each time I stopped the music player the static noise would come back.
Anyway I restarted the phone and now I've got no sound at all, looks like my motherboard has issues but I don't think it's all related to sds.
Has anyone else had issues with random static noise from the internal speaker or sounds playing at a very low tempo.
Sent from my GT-I9300 using Tapatalk
None of that is SDS, which is when your memory controller chip fails and your phone won't boot.
You either have corrupt rom or added mods, so flash a fresh stock rom to cure, or you have a hardware fault in the sound maker.
Only ever ran stock, never been rooted or used any mods, I'm guessing hardware fault. Took the battery out for a few minutes, that got the sound back working correctly but the random reboots and weird sound issues keep happening.
Sent from my GT-I9300 using Tapatalk
Step one back up data.
Step two factory reset.
Step three test .
Step four restore data .
Step five either service centre under warranty
Or flash stock rom see faqs and guides .
JJEgan said:
Step one back up data.
Step two factory reset.
Step three test .
Step four restore data .
Step five either service centre under warranty
Or flash stock rom see faqs and guides .
Click to expand...
Click to collapse
Thanks but those steps I'd already taken, more than once, what I've done now is taken out the official extended battery I was using and gone back to the original one, I'm still testing but so far so good, it's looking like I may have a faulty battery.
Sent from my GT-I9300 using Tapatalk
Related
Another bug i expect
No sound plays, ringtones music nothing, camera says "Camera Failed" on launch and all videos show "cannot play this video"
Rebooted and still the same.
Oh what fun
I have seen the same loss of sound and video stopped playing, but for me rebooting has fixed it (so far )
I also have a suspicion that it's the audio service crashing which might be causing some of my spontaneous reboots...
Roll on the next update from Samsung... hopefully 2.3.4 which fixes some of the battery issues too.
Left it off for an hour and now seems to be ok
Sent from my GT-I9100 using XDA App
Factory reset if problem comes back .
jje
Soundpool error
Just happened again, so I took a look in aLogCat...
Lots of Soundpool (2697) Error creating AudioTrack
My guess is that something is leaking audio streams and this stops any audio playing and the knock on effect is no video either
Not had it happen again (yet) ,
Lost trust in the phone, will it ring? will i miss an important call?, was happy with the G Tab thats the only reason i purchased the SGS2, oh well you live and learn.
relikade said:
Not had it happen again (yet) ,
Lost trust in the phone, will it ring? will i miss an important call?, was happy with the G Tab thats the only reason i purchased the SGS2, oh well you live and learn.
Click to expand...
Click to collapse
I know how frustrating it must be, but it's only one phone out of how many thousands sold?
Just get it exchanged.
Factory reset cures many problems .
jje
BoogWeed said:
I know how frustrating it must be, but it's only one phone out of how many thousands sold?
Just get it exchanged.
Click to expand...
Click to collapse
Cant do an exchange, only option is to send it away for a month for repair
It happened again, so I checked what happens when I get an incoming call...
No ring tone, only vibrate. When you answer the phone you can't hear the other person and they can't hear you... not great for a phone
It's clearly a bug given that the phone works fine for hours and then the audio service fails.
I run with audio clicks turned on, so it's obvious when it's failed, unlike a friend at work who runs his in silent mode...he also won't know when the phone has done a spontaneous reboot (mine did just now...sitting on the desk with screen off and locked).
Roll on XE3!
Mine done the same last night. I have turned on touch sounds for now. Also get reboots with it just sleeping on the shelf.
Strange as i have two SGSII and the other is fine. Both KE2
Sent from my GT-I9100 using XDA App
Done a factory reset as it was getting annoying. Now it's been 24 hours and i've counted 8 spontaneous reboots all while phone sleeping.
Sent from my GT-I9100 using XDA App
Hi,
I love my SGS2, but I've had one problem recurring since I bought it approx 6 months ago: music playback randomly goes into pause mode. It'll pause even when the phone is undisturbed on my desk.
It might happen after playing for a couple of hours, or it might do it after just a couple of minutes.
It occurred both with the stock music player, and also with PowerAmp and UberMusic.
Strangely I can't remember any podcasts played back via Google Listen pausing.
I took my first handset back and got a new one, but that's doing it too - so I'm about to post it off to the UK repair center... but it's obviously only worth doing that if the problem is hardware rather than software.
Does anyone else have this problem? Have you found a fix?
Presume you have tried factory restore before returning phone .
jje
JJEgan said:
Presume you have tried factory restore before returning phone .
jje
Click to expand...
Click to collapse
Yeah, I did it a couple of times with the previous phone, but there didn't seem to be any point with my current one, as it had paused when it was still in fresh-out-of-the-box state. (I should've taken it back straight away then, but then it did go through a long phase of working perfectly... though probably wasn't playing so much music then)
So sometime in the last week or 2, my I9300 started randomly freezing up and/or shutting off by itself.
it's usually a while after booting - i'll come to unlock it, and the LED will be showing Blue. Clicking any of the buttons doesn't do anything, nor does waiting a while.
Holding down the power button for a few seconds boot/reboots the phone though, and it works normally when it starts back up again - although after a while it will die again.
Sometimes it runs for hours, sometimes just minutes.
Occasionally, it will freeze up while i'm actually using it - the screen stays on, frozen in place, but the touchscreen and buttons won't do anything (although oddly, multiple clicks of the home button make the colours invert?).
Anyway, i thought this soundsed a bit like this 'Sudden Death' bug, but how do I know? I installed and ran the eMMC check app and it says:
Phone Model: Samsung GT-I9300
eMMC chip: Type VTu00M, Date 05/2012, CID 15010056545530304df1f900755f5f5f, FwRev oxf1
SGS3 Sudden Death? YES. Insane chip.
My question is - what does this mean? Do i have the problem and just need to make sure i run a kernel with the fix, or is the phone now broken and needs replacing/fixing?
If it does need fixing, do i need to revert it to stock ROM and run triangleaway or anything before i send it in, or is it fine how it is?
It's currently running crDroid 11.1 XXELLC, and it was at the time i started noticing the problem. I'm using Siyah 1.8.9, although i was using an earlier version before (can't remember what).
Same problem here... i don´t know what to do... today i make a lot of things to attempt to restore all but everything fail... i decided to talk with samsung and send the phone to repair, in a few days I hope to come to pick up the phone, I have to say that I had to pay 24 € for the shipping and after playing wait month or month and a half. is frustrating but hopefully come good repair.
One read the SDS thread . Two if you think you have the problem or a problem follow the how to revert to stock post and take to a service centre .
Freeze is more likely rom and or kernel .
???????
although oddly, multiple clicks of the home button make the colours invert AS IT SHOULD .
jje
thanks - have read the SDS thread and the stuff people were talking about there didn't really sound like what's happening for me, which is why i posted this thread.
I also thought that it sounded like the ROM or kernel, which is why I have now tried Siyah, tank, and boeffla kernel latest versions, as well as the foxhound, android revolution, and darky roms.
none have made a difference so far
I'm just looking for some ideas on what to do next - should i try reverting back to an Old rom/kernel, should i try a non-sammy based one, is it possible that my SD card is somehow causing the problem?
i didn't know that the multi-click thing inverted the colours - why does it though? it doesn't seem like something i'd want a shortcut to.
Wipe phone flash stock rom .
jje
Fixed it by moving from ELLA modem & wiping.
This thread is your solution : http://forum.xda-developers.com/showthread.php?t=2091045
so i wiped again and installed the MA2 modem - this made the freezing problem even worse so i wiped again and installed the ELKC modem.
this was on Monday and I hadn't had a single freeze until this morning, when it's frozen 4 times in the space of a few hours.
so i guess i'm flashing back to the factory image...
Lear95 said:
Fixed it by moving from ELLA modem & wiping.
Click to expand...
Click to collapse
Hello,
I'm somewhat new to the rooting world of Android but when I got my Note 2 last year the first thing I did was root it and unlock the bootloader, and kept that through the 4.1.2 (if I recall correctly) update. I knew I wasn't getting 4.2 and jumping straight to 4.3 as was Verizon's plan. I waited patiently and forgot about it entirely, so a couple of days ago I found the stock rooted deodex rom located here. I thought I had made the correct decision, it seemed to be for my phone, it flashed with no issues (both the rom and firmware) and runs fine except for one flaw which has proven to be a pain due to it cancelling my alarm every morning.
Whenever the lock screen comes up, the phone things a touch happens right in the middle of the screen. Nothing's there, but it doesn't matter what happens, I push the power button, plug its charger into it, it will always send out that one little ripple and as a result it cancels my alarm. I looked through the thread, I appear to be the only one with this issue.
Any recommendations?
Wow no wonder Ive been late to work all week. Phones doing the same thing.
Sent from my SCH-I605 using Tapatalk
As an update from my fiddling about this morning, it seems to only happen when the lock screen is set to the Swipe method. If set to a pattern, pin, anything else, this error doesn't occur. A temporary workaround at best, as this no longer allows me to access multiple lock screen widgets.
Wow man.. since my last post I wiped and am running a new rom, kernel, everything.. still doing it ?
Sent from my SCH-I605 using Tapatalk
I believe I've narrowed it down to a few possibilities, between it being the new ripple/ink effects on the lock screen or something to do with the multiple widgets. I can't believe we're the only ones dealing with this. Does anyone have any insight if even a complete reset, rom flash and kernel swap hasn't fixed it?
As another update, I appear to have been mistaken. While delayed slightly, the end result is no matter what, the alarm eventually silences itself after a few seconds, unknown why.
I had the same thing happen using n3bula (4.3) rom. Alarm would turn itself off. Didn't really have time to mess with it so I went back to beans 22 (4.1.2). If you figure anything out, let us know
Sent From My Sticky Note, Too?
As another update from yet more fiddling. I tested it this morning as it would normally be, hooked up to my computer charging, with my bluetooth headset on but also sitting on its charger. The alarm cut out even with pin set as the lock screen. When removed from the cable connecting it my computer and my headset on my ear, it didn't. Going to test further.
So, as yet another update, I believe I found the problem, a reply from prior posters experiencing the same thing would be helpful to see if it was the same issue. I have one of the original sony android smartwatches that connects through Bluetooth. On a hunch, I disabled Bluetooth on my phone before going to bed a few nights and wouldn't you know it, no problems. Did it again with the watch off and just the headset connected, again, no issues. Seems the watch is a bit too dated or butts heads with the MJ9 firmware driving the Bluetooth module.
So as to follow up. In my situation specifically, my music player is Poweramp and I noticed whenever my headset is connected and my alarm is going, it immediately tries to take over and start playing music, I think that's what caused my alarm to go silent. My headset is the Plantronics Voyager Legend, my smartwatch is the original Sony Smartwatch, I don't know if the combination of the three are relevant to the others in this thread having the problem.
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
ForcePhenomenon said:
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
Click to expand...
Click to collapse
when you wipe do you also format internal sd?
MunkinDrunky said:
when you wipe do you also format internal sd?
Click to expand...
Click to collapse
Correct, thought I'd noted that when I said clean wipe. I wiped internal storage, cache, everything you should when flashing a new rom, going to the point of doing it multiple times and even dirty flashing a few times to see if that would fix the problem (as it did fix some issues going on with n3bula and they actually recommend doing it.) But, nothing of the sort happened.
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
MunkinDrunky said:
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
Click to expand...
Click to collapse
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
ForcePhenomenon said:
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
Click to expand...
Click to collapse
have no idea but since it was a variable in this situation I thought to try to rule it out for certain.
Hi, this really has me stumped, and I can't figure out what could be the issue.
Any help would be appreciated.
My S3 (I9300) was running CyanogenMod nightlies, and suddenly I stopped being able to hear or produce sound in calls. I can initiate the calls, and can receive calls, but when I accept the call, there is no sound, and the other end cannot hear me either.
I thought this was an issue with the ROM, and since I was running an older nightly i installed a later one. The issue was still there.
So I did a full wipe and installed the latest M6 CM rom, and the issue still occured.
I did another wipe, and installed a different rom, still the same happened.
So i finally did a full wipe, and installed the stock 4.3 rom from SamMobile. This didn't help
I don't see how it can be a software issue, as my mic is working perfectly, and so is my speaker. It is only in the voice calls that they do not work.
Any ideas?
Thanks in advance
If it still the same on a fresh stock installation then it sounds like a hardware fault.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
If it still the same on a fresh stock installation then it sounds like a hardware fault.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply
I would say it has to be a hardware fault, as I have wiped the phone several times.
However, I really can't see what could be wrong as all the separate things are working. The mic and speaker are fine, and I have full signal and can make and receive calls.
What part in the phone could need replacing?
Unfortunately, the motherboard -nobody replaces component parts anymore.
Sent from my GT-I9300 using Tapatalk
Mine does the same thing, it's a software/hardware problem, do you keep your phone on silent a lot?
Someone gave me a fix in another thread and I've not had the issue since. Basically there#s a software or possibly hardware error that causes this. If you try and make or receive a call without the phone having already played any sound since start up then you get this bug. I rarely restart my phone so for me on the odd time I do, once it's started up I just play a song for a second or two then stop it and calls work fine. Since doing this I've not had the bug. Others have automated a sound on start up with tasker or similar.
Sometime upper noice cancellation mic causes the problem. Little cleaning may fix. If u good @ opening phone then try yourself. Otherwise go to a technician.