Hi buddies,
I know maybe It is a wrong place to ask this, but I've got a strange problem regarding to speaker.
My speaker in my S6 gets some ticks and lags during the play. I mean constantly the music stops and plays over and over.
I have the issue frequently and at the moment when I check the hardware with *#0*# there is no problem with the speaker.
I have the problem in games softwares and music players, and just recently got it.
I've tested different ROMs and kernels, both stock and unofficial, in both Lollipop and marshmallow, but the problem is still keeping up.
Attachment I've uploaded you an instance to better understand the problem.
I really appreciate if you just give me a hand with this.
Thanks.
https://drive.google.com/file/d/0B684uiQkcfJZbVJGWXYzeXVxQkk/view?usp=docslist_api
What model S6 do you have?
Might have installed the wrong model, can you please try to flash an original stock rom and see if that works then go from there to see where you went wrong
Valkiry said:
What model S6 do you have?
Might have installed the wrong model, can you please try to flash an original stock rom and see if that works then go from there to see where you went wrong
Click to expand...
Click to collapse
I've got the international version (G920f).
I've flashed stock ROM bunch of times from different bases, and now I am on stock marshmallow ROM with stock kernel. Still have the issue.
If you've tried different stock roms I'd say your speaker is faulty? If you haven't triped Knox send it back?
Valkiry said:
If you've tried different stock roms I'd say your speaker is faulty? If you haven't triped Knox send it back?
Click to expand...
Click to collapse
But I test during the issue, the speaker is allright, (using *#0*#)
And also I don't enable the Knox at all.
When I use that code I goto imie viewer. Knox is always active on stock rom regardless, it sounds hardware related not software, since you've tried other roms and it's still the same issue it doesn't make sense that you broke your device speaker.
Valkiry said:
When I use that code I goto imie viewer. Knox is always active on stock rom regardless, it sounds hardware related not software, since you've tried other roms and it's still the same issue it doesn't make sense that you broke your device speaker.
Click to expand...
Click to collapse
Oh, I really sorry that was a blunder
I meant *#0*# ...
So How can I really make sure that It's a hardware issue?
Does flashing ROM with box helps?
Well if you keep flashing different roms and nothing is working to fix the problem, which is including kernel issues on stock and custom I'd say it's hardware related.
Related
my GF has a SGS I9000...i updated her via Kies to the latest firmware because it was performing like crap. The update fixed that but every now and again it stops responding and the screen goes black...lights are still working on the buttons.
You can't power it off with the power button and the only way to fix it is to remove the battery. I've just updated her the the latest ROM from XDA for the SGS from http://forum.xda-developers.com/showthread.php?t=1102881 XWJVZ/XXJVT/OXXJV9/Sbl (MultiCSC) but it still does it...any ideas??
I've seen a few posts but no fixes..any ideas...HW vs. SW..was fine before the updates.
tia
First thing to do is isolate the problem as a hardware or software one. Simple task: flash stock, and see if it happens. If it does, you know it's hardware.
If it isn't, ask the developer (if it's a custom rom), or post under the appropriate phone of the forum. Chances are, if it is software, someone else with the same device has had it before.
NType3 said:
First thing to do is isolate the problem as a hardware or software one. Simple task: flash stock, and see if it happens. If it does, you know it's hardware.
If it isn't, ask the developer (if it's a custom rom), or post under the appropriate phone of the forum. Chances are, if it is software, someone else with the same device has had it before.
Click to expand...
Click to collapse
Tried a stock ROM straight from the Telco, now flashed to a stock ROM from XDA. Happening on 2 phones, both SG2 i9000. Both have different ROMS from different Telco's both were fine before the latest ROM updates.
One appears better with the latest official stock ROM from XDA but just monitoring it at the moment...just wanted to know if it was a know issue before spending too much time on it
ta
Hi,
I'm having trouble with my Nexus S, and it might have started after installing Jelly Bean (though probably not). The phone is somtimes unable to connect to 3G, and sometimes unable to call/receive calls. More often not working than working, both of them. I tried factory resetting and I also tried my SIM card in another phone (and another SIM card in my phone), with the same result. Something must be wrong with my phone, the only question is if it is a software error or hardware error.
Anyone have any tips? Perhaps how to check if the radio hardware is working (some app perhaps?)? Any ideas on what else I might try? The phone has been working perfectly for more than a year, so it's really odd it suddenly has problems. Anyone had similar problems?
Thanks in advance!
1. Are your NS is rooted...??
2. did you try another JB Custom Rom..???
or
3. is it still working good when you downgrade to ICS or other ICS Custom ROM...???
Then, if thats way still have same result, its might be hardware problem.
novelys said:
1. Are your NS is rooted...??
2. did you try another JB Custom Rom..???
or
3. is it still working good when you downgrade to ICS or other ICS Custom ROM...???
Then, if thats way still have same result, its might be hardware problem.
Click to expand...
Click to collapse
I rooted it yesterday to be able to try custom roms (tried Cyanogenmod 9). Same problem. I then returned it to stock, which made it reflash everything, and still the same problem. I'm starting to believe it's a hardware error. Are there any diagnostic tools available to check the radio module?
Thanks for answering!
jeinor said:
I rooted it yesterday to be able to try custom roms (tried Cyanogenmod 9). Same problem. I then returned it to stock, which made it reflash everything, and still the same problem. I'm starting to believe it's a hardware error. Are there any diagnostic tools available to check the radio module?
Thanks for answering!
Click to expand...
Click to collapse
Well, just try a radio that's for your model, search for nexus s radios in xda you should be able to find a thread which has all The radios, and choose appropriately.
Xxx oops! accidentally beamed from my awesome NEXUS S! xxX
Maybe you have to get the correct access point name from your provider. If I do a clean flash I have to input it by hand as otherwise I cannot connect as well.
Sent from my Nexus S
kwibis said:
Maybe you have to get the correct access point name from your provider. If I do a clean flash I have to input it by hand as otherwise I cannot connect as well.
Sent from my Nexus S
Click to expand...
Click to collapse
That may explain the data connection but not the calls.
Xxx oops! accidentally beamed from my awesome NEXUS S! xxX
Billchen0014 said:
That may explain the data connection but not the calls.
Xxx oops! accidentally beamed from my awesome NEXUS S! xxX
Click to expand...
Click to collapse
True, I read the post to quickly!
Sent from my Nexus S
Thanks everyone for all tips, help and suggestions! I ended up replacing my Nexus S (a... questionable reseller bought it for $120, maybe to use for spare parts for other phones becuase I told him about the problems I was having) with a used Galaxy Nexus. Must have been a hardware error.
Sorry for the late reply/checkback!
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
tfc87 said:
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
Click to expand...
Click to collapse
I'm going to go ahead and help myself out and respond to my own question. Upon even further research (yes, I know everyone says people don't look hard enough), I believe the issue relates to the Firmware version. Supposedly the newest firmware breaks the camera unless it's on the stock rom. There are modified firmwares out there that change the part that breaks the camera, but I believe I am going to downgrade the modem and all from what was pre-installed and see if it works.
tfc87 said:
I'm going to go ahead and help myself out and respond to my own question. Upon even further research (yes, I know everyone says people don't look hard enough), I believe the issue relates to the Firmware version. Supposedly the newest firmware breaks the camera unless it's on the stock rom. There are modified firmwares out there that change the part that breaks the camera, but I believe I am going to downgrade the modem and all from what was pre-installed and see if it works.
Click to expand...
Click to collapse
if its a custom Rom (Stock but maby some extras such as overclocking or somethin) they are Sometimes Broken They will try to fix it sometimes, upgrading to a higher android version it is sometimes is Quite hard to Fix everything.
Trozzul said:
if its a custom Rom (Stock but maby some extras such as overclocking or somethin) they are Sometimes Broken They will try to fix it sometimes, upgrading to a higher android version it is sometimes is Quite hard to Fix everything.
Click to expand...
Click to collapse
I downgraded the firmware to VRBMB1 and went back to that custom rom and the camera works flawlessly. I read in the firmware forum that the new firmware is doing this to a lot of people...I just happened to have one of the phones that came with it pre-installed. Problem solved and hopefully this post will help someone out...if not...it helped myself out at least.
tfc87 said:
I downgraded the firmware to VRBMB1 and went back to that custom rom and the camera works flawlessly. I read in the firmware forum that the new firmware is doing this to a lot of people...I just happened to have one of the phones that came with it pre-installed. Problem solved and hopefully this post will help someone out...if not...it helped myself out at least.
Click to expand...
Click to collapse
maby just wait till next firmware and they will fix it?
Trozzul said:
maby just wait till next firmware and they will fix it?
Click to expand...
Click to collapse
Yeah I'm sure it will be fixed. Either way, I don't recommend that newest firmware...signal seems to be the worst out of all of the ones I've tried...for me at least. Seems to be a lot of complaints out there with it anyways.
Similiar issue?
I am having a similiar issue with my US Cell GS3. I bought the donor version of mskip's Samsung Galaxy S3 Unified Toolkit and rooted my device yesterday now my camera is doing the same thing...fires up to a black screen, hangs a few seconds then says camera failed. I'm running Android 4.1.2, build R530UVXAMD4. I've read in a few places that I may have to either downgrade my kernel or flash with some sort of alternate firmware.
Any assistance provided is greatly appreciated!
Sterling8356 said:
I am having a similiar issue with my US Cell GS3. I bought the donor version of mskip's Samsung Galaxy S3 Unified Toolkit and rooted my device yesterday now my camera is doing the same thing...fires up to a black screen, hangs a few seconds then says camera failed. I'm running Android 4.1.2, build R530UVXAMD4. I've read in a few places that I may have to either downgrade my kernel or flash with some sort of alternate firmware.
Any assistance provided is greatly appreciated!
Click to expand...
Click to collapse
did you figure this out?
im having same problem
I had the same problem while flashing one of my friend's S3...i just did the whole process once again..and everything works fine
Sent from my Galaxy Note II using xda premium
tfc87 said:
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
Click to expand...
Click to collapse
I have had the same problem when I installed a certain custom rom (can't remember the name ) on my s3. But later I found that during installation of the rom, there was an option to choose one of four kernels, and if I chose Boeffla kernel (included in the options) my camera wouldn't work. So I just reverted back to the stock kernel and walah! My camera works again.
Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!
I've tried a handful of Nougat roms now, and I keep having the same issue with all of them: no call, text, or data. I've tried a few mods that are supposed to fix the issue, and even a ROM where, in the aroma settings, it gave me an option to fix the issue. I'm not sure as to where the point of failure is, but I think it's just an issue with this model of phone in particular. The Marshmallow ROM I currently have is having some issues with app compatibility, so if anyone knows how to flash back to the stock firmware, I'd greatly appreciate it.
BioBelac said:
I've tried a handful of Nougat roms now, and I keep having the same issue with all of them: no call, text, or data. I've tried a few mods that are supposed to fix the issue, and even a ROM where, in the aroma settings, it gave me an option to fix the issue. I'm not sure as to where the point of failure is, but I think it's just an issue with this model of phone in particular. The Marshmallow ROM I currently have is having some issues with app compatibility, so if anyone knows how to flash back to the stock firmware, I'd greatly appreciate it.
Click to expand...
Click to collapse
You cant really unroot because of the knox bug. You can flash back stock firmaware via odin and get recovery and flash the latest super su so the bug will be gone or flash a custom kernel.
N-DroidMod v6
Ohhdayumm said:
You cant really unroot because of the knox bug. You can flash back stock firmaware via odin and get recovery and flash the latest super su so the bug will be gone or flash a custom kernel.
Click to expand...
Click to collapse
I kind of have the same issue, except I can text and have mobile data. I just can't hear calls, and no one can hear me during calls.
I have note 5 SM-N920T, and I am using the N-DroidMod v6 custom ROM (it changed my model number to SM-n920c). I can't tell which kernel will fix the issue, and is compatible with the ROM.
Can you help?
UMAA19 said:
I kind of have the same issue, except I can text and have mobile data. I just can't hear calls, and no one can hear me during calls.
I have note 5 SM-N920T, and I am using the N-DroidMod v6 custom ROM (it changed my model number to SM-n920c). I can't tell which kernel will fix the issue, and is compatible with the ROM.
Can you help?
Click to expand...
Click to collapse
That's the audio bug, try to look in the thread for the audio patch where you flash. Usually provided by the developer if not then you may need to change to another rom that has that patch or a rom that was made for the t mobile version.