Hi, i have some problems with my galaxy s3 (i9300) international version. I don't have a warranty.
Android version: 4.3, stock
Problems:
-keeps restarting (very often)
-no sound at all, speaker or earphone
-microphone not working (not working in call, google now said that cannot connect to microphone)
I tried reflashing stock, same problems, i tried 3 custom roms including cm11, same problems. I cleared cache, dalvik, wipe data, nothing changed.
In my noob opinion, i think the motherboard is the problem, i don't think it's a software issue after all i've tried, but before i order a new motherboard for replacing, i would like to hear other opinions.
Thx in advance for your replies.
bump... anyone?
otonnel said:
Hi, i have some problems with my galaxy s3 (i9300) international version. I don't have a warranty.
Android version: 4.3, stock
Problems:
-keeps restarting (very often)
-no sound at all, speaker or earphone
-microphone not working (not working in call, google now said that cannot connect to microphone)
I tried reflashing stock, same problems, i tried 3 custom roms including cm11, same problems. I cleared cache, dalvik, wipe data, nothing changed.
In my noob opinion, i think the motherboard is the problem, i don't think it's a software issue after all i've tried, but before i order a new motherboard for replacing, i would like to hear other opinions.
Thx in advance for your replies.
Click to expand...
Click to collapse
I agree with your assessment. You have tried various roms and it didn't fix the problem so this on points to hardware.
Hardware seems the likely culprit here.
Related
Dear all!
Two or three weeks ago I have started expecting some annoying problem. Not sure what is the source but whatever.
During incoming call with disabled screen there are some lags/breaks with call sound and even vibration up to enabling screen. The call sound is built-in so it is not due to extcard problems.
I am expecting almost the same when playing music by any player - from stock to Poweramp: when screen comes off the sound is terrible: it breaks a lot. Enabling screen eliminates the problem.
The problem is completely absent with stock radio player.
Enabling/disabling locking and/or energy saving mode does not affect - the problem persists.
I have tried to remove any modification excepts root: I have installed stock XXEMA2 with wiping dalvik - it doesn't help.
Do you have any idea what can be the source of problem and how to solve it? Please do not recommend data wipe (I expect it is the first idea for everyone )
Do you have any idea what can be the source of problem and how to solve it? Please do not recommend data wipe (I expect it is the first idea for everyone
No usually is to post here then get told to factory reset .
Personally i would backup data format system cache data sd card in recovery .
Flash the correct stock rom for your phone and test .
Fails then remove root traces and return to a service centre .
Or don't wipe data/ factory reset and just return to service .
jje
As far as I see the problem is only software/firmware based. It is not due to hardware or the problem would be constant disregard display status.
So I would be very happy to see some ideas what software/hardware parameters can influence on this.
I found the source of problem. It was caused by god damned DX Battery Saver 3.0.0 (previous versions were OK).
The topic can be closed now.
Hello everyone,
I have a samsung Galaxy S2 and facing quite enough issues with it.
Problem started when one fine day "Media scanner" kept running. I googled for that problem, uninstall few doubtful apps,
cleared off other data but all in vain.
Finally, I did factory reset to get rid of this. After factory reset, I got below problems :
1. Lag in Samsung keypad
2. No audio at all (alarm, incoming calls, music, FM Radio etc etc.)
3. Camera failed.
4. And some times, face issue while rendering.
To solve first one I install swiftkey app which is working fine.
For audio issue, I googled but nothing was useful for me.
Currently, my device has Android version 2.3.4 , i.e. as it was shipped.
I am thinking to update to Ice Cream Sandwich (thinking that can solve all issues) but before that need opinion of experts.
If anybody can "pinpoint actual issue which caused all this or give some direction in solving this" , that would be great help to me.
Thanks in advance for help
With Regards
Neha
First don't go to ics 4.0.4 stay well away from that firmware :thumbup: flash lsw 4.1.2 and report Bk mate. You can use ics 4.0.3 if you want though.
andrewwright said:
First don't go to ics 4.0.4 stay well away from that firmware :thumbup: flash lsw 4.1.2 and report Bk mate. You can use ics 4.0.3 if you want though.
Click to expand...
Click to collapse
Firstly, Thank you for suggestion.
Secondly, I want to mention, my device has started working smoothly its own. Today morning it got fully discharged and got shut down, after charging it is working without any issue. I am not sure, whether battery charging/ discharging has some link to all those issues because I had rebooted it many times.
Anyways OS upgrade is required, hope my experience can help somebody else also
Hello,
first... im a noob, and have only a little clue about android systems.... i will try my best
second the problem:
I flashed an old S2 with gingerbread with a lot of firmwares and got nearly evry image to wort without NeatRom -> no respons -> recover with odin...
but the problem is that as i select the camera-app the flash-led is going on, and i cant switch it off. its buring the whole time the camera app is active..
with the flashlight-app i can switch it on and off as i like.
this problem exists in RR_JB_V3.1.3_AOKP_4.2.1_I9100 as in pac_i9100_4.2-milestone.1.release_20130806-205645 and in sentinelrom_v4_80_i9100
does anybody know if this is an ROM fault or is it in the cam app?
yours Platonshead
PS: my actual image is the pac one...
Have you bin formatting before flashes? I have used aokp 4.1.2 "my trusty nandroid" as this is perfect rom and faultless and I have used pac 4.2 and that didnt do this either. What I would do Is format system, data, cache, wipe dalvki and then flash rom and see if this fixes this problem.
andrewwright said:
Have you bin formatting before flashes? I have used aokp 4.1.2 "my trusty nandroid" as this is perfect rom and faultless and I have used pac 4.2 and that didnt do this either. What I would do Is format system, data, cache, wipe dalvki and then flash rom and see if this fixes this problem.
Click to expand...
Click to collapse
no i have only made a factory reset, a cache wipe and a dalvki wipe and flashed the roms...
but... today i tried it with formating and got the same problem. (also with pac)
i also tried another firmware: stock pda: I9100XXLPJ with phone: I9100XXLPJ and an unknown CSC whatever that means.....
and there the cam is also showing this strange behaviour.
the funny thing is that i dont think its a hardware problem as i can swich the light on and off as i like per software app.
does anyone know a way to test the hardware-function of the phone just to exclude this source of failure?
thanks sofar
EDIT:
1. my girlfriend just told me that this "feature" was always there and so i think maybe it IS a hardware bug.
2. i just tried to figure out why the app "flashlight" can handle the LED whereas "camera" cant.
i can listen (with a silent room and my ear near the LED) that if i turn on the flashlight, the camera just open up the lens (it just sounds like that) and when i switch it off i hear a similar sound.
-> is the flash somewhat connected to the camera or "exposure" function?
Update 2:
i Tried another camera firmware with *#34971539# (from ocef02 to ocee0? to te??28) but nothing happend. -> also the Version of ROM (GB, ICS) changed nothing...
seems like HARDWARE....
but: I think the flash-LED is mounted on the mainboard. changing the cam-module will not change the LED. right? has anybody solved this type of "damage"?
Hi all,
I have a Galaxy S" i9300 and I've been using NeatRom since a long time now, maybe 2 years or more without any issue, but since few weeks I'm having problem with phone calls, I can't hear and they can't hear me, so the speaker and the microphone are not working during call. While if not in a call they work fine, I can record my voice, listen to music...
I've tried many thing, full wipe, flash the latest NeatRom but nothing worked.
I've flashed also the latest stock rom but the issue remain the same.
Any idea please?
Thanks
Flash a stock rom via odin and boot it up. Go to the dialer and press *#0*# for factory test mode.
From there you can test the hardware. Factory test mode is not accessable via custom roms.
shivadow said:
Flash a stock rom via odin and boot it up. Go to the dialer and press *#0*# for factory test mode.
From there you can test the hardware. Factory test mode is not accessable via custom roms.
Click to expand...
Click to collapse
Tried that already.
Nothing looks wrong from *#0*#
Then the problem has to be software.
Most likely it is an hardware problem.
Search on google for: samsung i9300 no sound during calls
I have two S3 devices that have the same problem.
Tried factory reset, flash original rom, flash Cyanogenmod (CM11 & CM 13) and flashing modems. Nothing seems to be working.
Some people tried to apply pressure on the Audio IC chip. Maybe you can try this. More information about this can be found here.
[email protected] said:
Most likely it is an hardware problem.
Search on google for: samsung i9300 no sound during calls
I have two S3 devices that have the same problem.
Tried factory reset, flash original rom, flash Cyanogenmod (CM11 & CM 13) and flashing modems. Nothing seems to be working.
Some people tried to apply pressure on the Audio IC chip. Maybe you can try this. More information about this can be found here.
Click to expand...
Click to collapse
Not true. I had this issue and it was software related.
Also, op states "no fault" with factory test mode.
shivadow said:
Not true. I had this issue and it was software related.
Also, op states "no fault" with factory test mode.
Click to expand...
Click to collapse
What I said was "Most likely". That doesn't exclude software.
After my tablet is on for a few hours it makes a weird sound with any audio output. I thought it was a lollipop issue but after flashing marshmallow image the problem is still there. I'm on stock and unrooted. I've tried factory resetting after every update, clearing cache, deleting user data, etc...Not sure what to do next. I'm thinking about relocking the bootloader and contacting HTC before my warranty is up. You guys have any ideas what I should try? The only temporary fix I have is powering it off and on. thanks
https://youtu.be/rs2908dkDZY
https://youtu.be/8HWEyJKnCTs
I have the same issue and have found no fix for it thus far.
Tried Safe Mode?
Life is poker, risk being happy
Thanks for the suggestion, issue still happens in safe mode for me.
Contact HTC/Google it looks like hardware problem if its still apears in Safe Mode
Life is poker, risk being happy
In my case it happens in Marshmallow but flashed a week ago a 5.1.1 ROM and all seems ok. Anybody has a clue to fix it?