Database Info

[Q] Dead (Left)Speaker

Hi all,
My left speaker stopped working all of a sudden. I guess it was around the time I was tweaking it to flash Jelly Bean (N8010). It is an N8013 and even though I flashed the proper firmware later on, the problem still persists.
However, it might not be related to that different firmware at all and just happened to break then. Is there a way to check whether it is a hardware or a software problem, though it seems to stem from some kind of hardware fault to me. :crying:

Wipe and flash stock firmware is all you can try .
jje

JJEgan said:
Wipe and flash stock firmware is all you can try .
jje
Click to expand...
Click to collapse
And if that doesn't work, shove some cotton wool in your left ear :good:
Does the sound play through headphones? IF it does and IF its the same software that controls the output, I would say it was definitely the left speaker that has gone.

[Q] S3 Camera Breaks Upon Installing Custom ROM

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.

Samsung S4 constantly losing connection, but still shows connected.

My girlfriend's AT&T S4 loses connection, but still shows it connected. So you never know you don't have a connection until you reboot the phone and find that you have missed 2 phone calls, 3 emails, and 15 texts. This happened with the stock Rom. I've tried a couple of different roms, but still the same outcome. I'm thinking I should have to switch to a different modem, but I'm not sure which one to use. Am I wrong and is there another solution? I'm looking for something that will work so I don't have to mess with it again. If anyone has experienced this connection loss and found a solution, please let me know what to do to fix this phone.

definitively you need to update the modem.
2 ways to achieve the update: either by a new rom firmware (http://live.samsung-updates.com/?device=GT-I9505), either by just update gsm modem/wifi fix (http://forum.xda-developers.com/showpost.php?p=50965837&postcount=2627)
But I strongly suggest before, to look at what your device model is. Mine is S4 LTE international = GT-i9505.
Don't know yours.
Hope that helps.

Ahh... a response. Thank you
So if I change the Rom, that will change the modem too? I thought the modem stayed with the phone and you had to change that separately. This can get so confusing at times. But this is good news never the less. The model number of the phone is GT-i9505G running a custom Rom ( Super-Nexus ) 4.4.4, baseband version 1337UCUFNB1, Kernel version 3.4.0-1125940 [email protected] #1
I hope this information helps you understand what I have so you can find a solution. Thank you for all your help

You're right. changing the rom doesn't update your modem unless you flash a stock firmware via odin. But read carefully as samsung at&t version is specific (meaning specific firmware).
You will find bunch of files by looking at "modem galaxy s4 i337" on xda thread. Depend on what you will find, either only modem/wifi fix either the full stock firmware, you need to update via Odin.

also a good start is to take a look at xda thread > http://forum.xda-developers.com/showthread.php?t=2616221
And it seems that AT&T already realease some new stock firmware > http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB419415&cv=820&partner=LinkShare&siteId=TnL5HPStwNw-V7YmgDyzwWW7TSi7CwkqtA

I tried a Note 4 Rom first
I have a Note 3, I've had a Note 2 (I loved the macro setting and wished they'd kept it for the Note 3), so I thought I would try the Note 4 Rom on my girlfriend's problematic S4. It got stuck in a boot loop. I ended up using the link you gave me for the stock (but upgraded) AT&T Rom. I see it brought the phone from NB1 to NJ4 firmware. I'm hoping this improvement will solve the problem of a connection loss bring that is a factory firmware upgrade. She can also get OTA updates again. Thank you for your help. Now it's time to find a different Rom for my Nvidia Tegra Note 7. This thing is terribly slow after the upgrade to Lollipop!

Note 4 has a complete different hardware from S4. That's why you had boot loop.
Don't forget to change the subject by [SOLVED] if applied

Galaxy S6 Speakers' Issue

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.

Samsung galaxys duos (gt-s7562): Soft brick (bootloop)

RECENTLY I STARTED HAVING BATTERY PROBLEMS WITH MY SAMSUNG GALAXY S DUOS
I LOOKED UP ON THE WEB AND SAW THAT CUSTOM ROOM'S MAY SOLVE MY PROBLEMS
I INSTALLED A CYANOGEN OS BUT STILL THE BATTERY PROBLEM PERSISTED
THEN I BOUGHT A NEW CHARGER
IT SEEMED THAT THE NEW CHARGER SOLVED MY PROBLEM
SO I DECIDED TO SWITCH BACK TO MY STOCK FIRMWARE
I THOUGHT THAT WHY NOT TRY STOCK FIRMWARE OF ANOTHER DEVICE
BUT BY DOING THIS I ENDED UP WITH THE-->>"FIRMWARE UPGRADE ENCOUNTERED AN ISSUE. PLEASE" ... BLAH... BLAH... BLAH
THEN I DOWNLOADED STOCK FIRMWARE FOR MY DEVICE ONLY AND FLASHED IT
IT GOT RUNNING
BUT AFTER A FEW DAYS I GOT BORED WITH THE LAGGY STOCK FIRMWARE
SO I SEARCHED XDA FOR ANOTHER CUSTOM ROM FOR GT-S7562
I DECIDED TO FLASH THE PMP LIGHT ROM ESPECIALLY MADE FOR GT-S7562
BUT AFTER FLASHING IT I HAD GSM CONNECTION PROBLEMS
SO BACK TO STOCK ROM AGAIN
BUT THIS TIME WHEN I FLASHED THE STOCK ROM IT GOT STUCK AT THE SAMSUNG LOGO
I COULDN'T GO INTO RECOVERY MODE THEN
SO I CORRUPTED THE DEVICE AGAIN AND INSTALLED THE STOCK FIRMWARE
BUT AGAIN BOOT LOOP NO BOOT SOUND AND NO RECOVERY
I TRIED MANY THREADS
I TRIED http://forum.xda-developers.com/showthread.php?t=2426426
I TRIED http://forum.xda-developers.com/s7562/general/troubleshoot-pit-file-baseband-files-t3246791
AND MORE AND MORE THAN THE NUMBER OF NERVE CELLS IN MY BODY
SO...
PLEASE ANY HELP WOULD BE APPRECIATED
I WROTE THIS WHOLE THREAD WHILE CRYING:crying::crying::crying:

hey download stock rom files alone ..... like pit and csc etc ....
and flsah them this will work
i'm very bad in english ...sorry :silly:

I have tried before but without success any way thanks i will try it once again

boy maztoul said:
hey download stock rom files alone ..... like pit and csc etc ....
and flsah them this will work
i'm very bad in english ...sorry :silly:
Click to expand...
Click to collapse
didn't work !!