Right headphone not working - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

I flashed the official CyanogenMod via the official installer and I'm on 4.3 currently as there's no updates yet. The audio was working perfectly but suddenly the right channel has stopped working. I've tried different headphones and different apps. Even the system sounds don't play on the right side.
I hope someone can help.

Maybe You're using some equalizer?
Check for that, else try to flash other ROM and check then. If it works on other rom, then it's just software issue (data may be damaged or rom) else it's hardware.
Sent from galaxy s4 zoom

It might be a hardware issue after all. I've flashed another ROM and wiped every single thing on the device. Still not working.

you need this
http://www.ebay.co.uk/itm/AUDIO-HEA...K_Replacement_Parts_Tools&hash=item4175468b75

salespalace said:
you need this
http://www.ebay.co.uk/itm/AUDIO-HEA...K_Replacement_Parts_Tools&hash=item4175468b75
Click to expand...
Click to collapse
Thanks.
But I already found a local repairing shop that can replace it for like $8

Related

[Q] Camera not working, other solutions?

So my camera force close every time I try to use it..
So far I've tried different roms... like miui, cm7(used cm roms for a while), I've tried pure something roms, blandroid.. camera never worked.. tried one or two kernels too to no avail..
So I've reflashed everything to stock.. I mean STOCK lol.. still force closing..
anything else I might not know to try? Or I can assume it's an hardware issue?
I guess the reps at mobile store will throw a fit once they see the unlocked padlock lol if I ask for some help..
mmm.. i am having the same prob here....
i thought it is because of the ROM...mmm. i have changed to basically All the latest ROMs....failed to make the camera working.
MAYBE it is a hardware issue. My N1 fell from my bed. few times. Im not so sure it was before or after.
FOUND the solution to Camera Not working Nexus One.
You have to go back to Stock ROM
http://forum.xda-developers.com/showthread.php?t=717870&highlight=frf91
1. Go back to Stock RoM
2. Then flash back to your FAV ROM - Mine is Miui AU..
not really the solution....
after 24 hours of working hard..
i failed!
Camera WORKING - when using stock ROM
Camera NOT working - when rooted and custom ROM.
What should i do ?
sadly I've already tried going back to stock.. did not work.. got some suggestions on another forum to try an clear the thumbnails and camera cache..
The Camera cache is stored under sdcard/android/data/com.cooliris.media...
Thumbnails are under sdcard/DCIM/thumbnails...
I had this issue within a month of upgrading to 2.2.3 on a stock Nexus One, and the fix for me was to re-format my SD card. I copied everything off to a PC, formatted and copied everything back and now the camera is working as intended. Hope this helps!
DexNarfux said:
I had this issue within a month of upgrading to 2.2.3 on a stock Nexus One, and the fix for me was to re-format my SD card. I copied everything off to a PC, formatted and copied everything back and now the camera is working as intended. Hope this helps!
Click to expand...
Click to collapse
i tried already....not working...
i changed the Card, it works..!!
and it does nt again...
What radio you on? Try radio 5.0.8 if you're not already on it
Same problem here after flashing CM7 kernel on stock ROM. Did you fix it? Please help.
Did someone solve this problem? I have the same since yesterday (?!?) when i made the 2.3.4 update....
Maybe this problem is older in my n1, but i cant exactly say. I tried starting the camera app when sd-card is unmounted -> no effect, force close....
Actually... had a friend have the same issue. Though... it may or may not be the same as your issue. Brought it to an after service center near us and they cracked it open. They said there was a cable loose inside going to the board with the camera on it that was causing the issue. They put it back together and it has been working fine ever since. I am not exactly sure how a cable was loose inside where it shouldn't ever be moving... but it definitely fixed the problem. Hopefully you guys don't have the same problem.
Prior to going to the service center I backed up and flashed back to stock. Still had the same problem... though I seem to remember the message being odd when trying to use the camera. Was a while back so... >_< sorry.
Hm, i got this error in logcat:
V/CameraHolder( 1122): open camera 0
E/mm-camera( 75): main: MSM_CAM_IOCTL_REGISTER_PMEM ioctl failed for MSM_PMEM_AF type. ioctl return value is -1
E/mm-camera( 75): isp3a_init_ctrl failed
Click to expand...
Click to collapse
Does someone can give me hints?
Ok, i get interesting information within my tests:
camera is ok! works with CM7 and this ROM: http://forum.xda-developers.com/showthread.php?t=1061648
But why not with my stock ROM?
I updated hboot/radio for a test -> No camera
Changed kernel (CM-Kernel, etc.) -> No camera
What else is the problem? I actually love my system and when i flash stock GRJ22 over it, camera works, but alle sd-apps are not avaiable and the memory ist nearly full.

[Q] Help with GPS N7000 with Android Kit Kat

My Galaxy Note was with ROM SlimSaber 4.4.2 and the gps was not working. Then I put Cyanogenmod 11 but the problem continues.
Someone who has any of these two Rom is facing this problem?
I thank for the help. :good::good:
Sorry for my english. I'm from Brazil.
dexterdroid said:
My Galaxy Note was with ROM SlimSaber 4.4.2 and the gps was not working. Then I put Cyanogenmod 11 but the problem continues.
Someone who has any of these two Rom is facing this problem?
I thank for the help. :good::good:
Sorry for my english. I'm from Brazil.
Click to expand...
Click to collapse
CM 11: GPS working fine here.
I am using latest frantisheq cm11 built and gps working fine.
Sent from my GT-N7000 using XDA Premium 4 mobile app
Strange, I've formatted the Note, put the rom Slimsaber and Cyanogenmod 10.2 and gps still not working. I am using GPS Test and Sygic for try to capture the satellites but nothing happens.
Would know tell me a way to check if the gps is actually connected, and if there is any way to fix this?
Thank you for the help of the two.
dexterdroid said:
Strange, I've formatted the Note, put the rom Slimsaber and Cyanogenmod 10.2 and gps still not working. I am using GPS Test and Sygic for try to capture the satellites but nothing happens.
Would know tell me a way to check if the gps is actually connected, and if there is any way to fix this?
Thank you for the help of the two.
Click to expand...
Click to collapse
Try install a stock Samsung rom and check GPS.
I have the same problem for a while. I am using SllimSaber.
I have formatted and reflashed KK several times nothing changed.
Now i will try stock rom as suggested.
I have installed AryaV7 nothing has changed, no GPS signal at all
Any ideas?
nehiryeli said:
I have installed AryaV7 nothing has changed, no GPS signal at all
Any ideas?
Click to expand...
Click to collapse
Does your phone's GPS indicator blink? Maybe your phone's GPS is broken? Have you tried aps named "GPS Test", from google play?
Did you tried to use the app GPSData to download latest AGPS info?
Also you can try to modify gps.conf/gps.xml to choose different time/supl server, that is greatly helpful for fixing GPS.
Try reflashing rom (clean install) - In case there is nothing wrong with your GPS hardware everything should work just fine
I have modified gps config data with Faster Gps. Results did not change.
I have also used AndroiTS Gps test,Gps data, Gps status, Gps essentials none of them was able to catch a satellite.
I have clean install Slim Saber but the result is the same.
I am started thinking that it is not software related.
It could be a hardware issue....
Folks,
Like you I spent days editing gps.conf, installing apps, reflashing ROMS, all to no avail.
There seems to be no magic bullet and what works for one may not work for another, but I eventually stumbled across http://forum.xda-developers.com/showthread.php?t=1973727.
As you will see it requires opening the case and 'tweaking' two contact points. To my surprise it worked for me - although not perfectly. I get about 10 satellite fixes and 6, maybe 7 locks. ('GPS Test' is an excellent freebie to tell you what locks/fixes you are getting.) But a big step in the right direction. There are a few images in the thread that describe the issue/ remedy.
Top (well, average) tips:
1. If you haven't taken a case off before:
a. don't try it just before setting off to a dinner party. It is a bit of a pig and requires some grunt, swearing and patience - but it can be done! There are a few YouTube videos that help explain the process.
b. you will require a size 000 cross-head (Phillips) screwdriver. Go out and buy one if necessary (if you can find somewhere that sells them - I use the one from my spectacles repair kit which just happens to fit; not perfect but does the job - http://www.poundland.co.uk/spectacle-repair-kit. If you try with too big a head you risk stripping the screw heads and that is ......... well, not recommended.
2. Once you have completed the job test your N7000 (with GPS Test) before putting the 9 screws back in. Mine works better with no screws! You may find different.
As I say above this may work for you and may not, so the usual health warning, proceed if you wish.
You can find similar issues on Samsung smartphones, eg http://gs3.wonderhowto.com/how-to/s...-gps-problems-your-samsung-galaxy-s3-0145332/.
Good luck :laugh:
FT
Thank you very much.
Works like charm!!! :good:
The problem was in antenna.
dexterdroid said:
My Galaxy Note was with ROM SlimSaber 4.4.2 and the gps was not working. Then I put Cyanogenmod 11 but the problem continues.
Someone who has any of these two Rom is facing this problem?
I thank for the help. :good::good:
Sorry for my english. I'm from Brazil.
Click to expand...
Click to collapse
Did you solve the problem? I have the same trouble that have arisen after updating to kitkat.I tried everything to solve it, without success (clean installation, downgrading to stock rom, editing the gps.conf file, reinstalling google maps, modem changes, hardware check ect.).
I switched to Lollipop but problem remain unsolved.
Regards
I'm glad I found this thread; I too have tried all possible solutions that may have worked for others (edit gps.config, reflash stock ROM, go back to GB, tighten the screws, bend the antenna contacts and so on), and none have helped. At all.
Now, I read somewhere that what is most likely causing the problem (completely dead gps, gps status apk shows zero satellites) is a corrupted EFS partition. This is a partition that usually is not touched by factory resets, ROM changes and so on. It also contains information that you cannot afford to loose (imei and so on).
So, I managed to backup this partition using KTools. Now, the problem is how do I get a clean, EFS partition? Is there a way to reflash this partition from a hidden backup thru odin? Or some other way?
Any help would be vastly appreciated!
Regards.

[Q] Headphones correctly detected only first time after boot, not detected after that

I am experiencing headphones detection problem with my Xperia Z1. Headphones are correctly detected first time after reboot. If I try to plug them in after that phone doesn't detect them any more (external speaker is used even after I've plugged them in).
I contacted Sony support and they suggested it might be Smart connect. I cleared it's cache. Didn't help. I disabled/removed it. Didn't help either. I downgraded to an older ROM (don't remember if it was 4.2 or 4.3) and it worked as expected. Then I downloaded fresh .ftf of latest rom. Same problem re-appeared. Tried with Kit Slim custom ROM (based on 4.4) and experienced same problem.
It is obviously a SW problem. Is there any app which would allow me to manually direct sound to either destination? I have SSH server running on my phone. Is there any way to do this via shell? Any API call that I could utilize? I have no experience with Android dev but I am SW engineer and I think I could implement a simple app like this if someone would point me in the right direction.
Thanks!
it's definitely something with smart connect. had the same issue some days ago...... unistalled smart connects updates and installed them again -> works!
Tried that already. Didn't help
I contacted Sony support again and they suggested to try PC Companion's repair feature. What will that do? How that relates to the fact I'm running a rooted custom kernel?
Thank you!
hm try to flash .157 with flashtool. after that flash trinity kernel via flashtool and fastboot -> should work like charm dont forger to save your data before that I did the same and it worked for me
Where could I download that?

[Q] "Not registered on network" error. *PLEASE HELP*

Yesterday, my phone just decided it didn't want to be connected to a network anymore. I was running DynamicKat ROM. It just happened out of nowhere and continues today. I've tried flashing different ROMS and they install fine, but I still can't register to a network. I believe I need to update the modem, but I'm not sure. I'm currently on baseband version ANK4, but I think I need to update to BOC4. Does this sound correct? Any advice would be great, and if you might point me in the direction of any files needed it would be greatly appreciated as well. No need to link, but just a general section where I could find the files would be helpful as I seem to have little luck with the search function here. Thank you in advance.
EDIT: Ehhh... Nevermind. It just started working again. I can't explain it. Suddenly I was connected again.
Always a good idea to check your APN settings if you are in a known coverage area with a new ROM. Been my problem 90 percent of the time
Sent from my SM-N910T using Tapatalk
Applejackson said:
Yesterday, my phone just decided it didn't want to be connected to a network anymore. I was running DynamicKat ROM. It just happened out of nowhere and continues today. I've tried flashing different ROMS and they install fine, but I still can't register to a network. I believe I need to update the modem, but I'm not sure. I'm currently on baseband version ANK4, but I think I need to update to BOC4. Does this sound correct? Any advice would be great, and if you might point me in the direction of any files needed it would be greatly appreciated as well. No need to link, but just a general section where I could find the files would be helpful as I seem to have little luck with the search function here. Thank you in advance.
EDIT: Ehhh... Nevermind. It just started working again. I can't explain it. Suddenly I was connected again.
Click to expand...
Click to collapse
Funny you mention this as I run the same ROM and have had this occur to me whilst traveling around my area and in and out of T-Mobile "Dead Spots" which seem to be many...
Even called T-Mobile to report and best they could tell me is go into "More Networks-Mobile Networks-Network operators" and select - Select automatically.
A real PITA when you driving down the road and need to call out or re-connect your call with someone.
Note: I've had numerous issues on different ROMS similar to this so I pretty much blame T-Mobile and their service in my area unless someone else can chime in, I would be curious...
Applejackson said:
Yesterday, my phone just decided it didn't want to be connected to a network anymore. I was running DynamicKat ROM. It just happened out of nowhere and continues today. I've tried flashing different ROMS and they install fine, but I still can't register to a network. I believe I need to update the modem, but I'm not sure. I'm currently on baseband version ANK4, but I think I need to update to BOC4. Does this sound correct? Any advice would be great, and if you might point me in the direction of any files needed it would be greatly appreciated as well. No need to link, but just a general section where I could find the files would be helpful as I seem to have little luck with the search function here. Thank you in advance.
EDIT: Ehhh... Nevermind. It just started working again. I can't explain it. Suddenly I was connected again.
Click to expand...
Click to collapse
I had a similar problem on DK, except that it was unmounting my sim card completely & I had to reboot to get it working again. Happened every hour or so, very frustrating. I tried a different rom & the issue went away, so it's definitely something funky with DK which makes me sad cause that's my favorite rom.
I just reflashed it last night though & I took the precaution of completely reflashing ANK4 through Odin and redoing root & TWRP too, then flashing DK like normal. So far, so good(and it seems to have fixed the battery life issues I was having as well, yay), so you might try that method & see if it helps for you too. But be sure to back up your internal storage first cause odin WILL wipe it. Learned this the hard way, bye-bye all my pictures & titanium backups :/
Files I used can be found here.. BOC4 is for LP, so you should be fine with ANK4.

headset issue - not recognized after mod

Hi.
Im on Viper 800, a sense 6 based rom, 5.0.2, lollipop, firmware 7194012.
I flashed this sound mod - http://forum.xda-developers.com/showthread.php?t=2211163
In the description, my phone appears to be supported, along with the sense rom - M7 international.
After flashing, the result was this - great sound on speakers (as it should be), headset no longer recognized (sound only on speakers).
Ok, as I was doing always when facing this sort of problems, I restored a back-up version using TWRP. No matter how bad the software was messed up, this worked every time.
Not this time = the headset no longer recognized (sound only on speakers).
OK, I am writing an older back-up version = the same result.
Ok, maybe some scripts or libraries are corrupted, I am installing a NEW lollipop rom, after full wipe = the same result.
Ok, I am installing a fresh new rom, Kit Kat based = the same result.
The problem is that the automatic selection of speakers/headset is no longer functioning. I installed Soundabout apk, with allows you to manually route the sound on speakers or headset and it WORKS, but I cannot live with that - I want to repair this process in order to be automatic, as normal.
I need to understand wth is corrupted and how can I fix this...
Thank you in advance.
dabuHTC said:
Hi.
Im on Viper 800, a sense 6 based rom, 5.0.2, lollipop, firmware 7194012.
I flashed this sound mod - http://forum.xda-developers.com/showthread.php?t=2211163
In the description, my phone appears to be supported, along with the sense rom - M7 international.
After flashing, the result was this - great sound on speakers (as it should be), headset no longer recognized (sound only on speakers).
Ok, as I was doing always when facing this sort of problems, I restored a back-up version using TWRP. No matter how bad the software was messed up, this worked every time.
Not this time = the headset no longer recognized (sound only on speakers).
OK, I am writing an older back-up version = the same result.
Ok, maybe some scripts or libraries are corrupted, I am installing a NEW lollipop rom, after full wipe = the same result.
Ok, I am installing a fresh new rom, Kit Kat based = the same result.
The problem is that the automatic selection of speakers/headset is no longer functioning. I installed Soundabout apk, with allows you to manually route the sound on speakers or headset and it WORKS, but I cannot live with that - I want to repair this process in order to be automatic, as normal.
I need to understand wth is corrupted and how can I fix this...
Thank you in advance.
Click to expand...
Click to collapse
Afaik, sounds mod only make changes in the /system partition so restoring a nandroid backup or re-flashing the rom should fix any bug caused by the mod. Maybe its an hardware problem...
One thing that I love about Android is that no matter how deep was the **** I entered when flashing things, I never got stucked. Never, ever, and I had like 12 Android phones, rooting them all. Reading some tutorials, some topics, asking other guys.. I always solved the problems, by myself or with some help, without going to the service.
I fixed this. I wrote a fresh CM12, the result was the same (course), but out of despair, i pulled in/out the handset jack for SEVERAL times, while the music was playing and....it came back to its senses - the selection for sound output is automated again.
Thanks.
PS. It was software, not hardware - I explained above what happend when using Sound About.
The thread can be closed.
dabuHTC said:
I fixed this. I wrote a fresh CM12, the result was the same (course), but out of despair, i pulled in/out the handset jack for SEVERAL times, while the music was playing and....it came back to its senses - the selection for sound output is automated again.
Thanks.
PS. It was software, not hardware - I explained above what happend when using Sound About.
The thread can be closed.
Click to expand...
Click to collapse
Sounds more like an intermittent hardware problem. Flashing a new rom will wipe the sound mod from /system. Maybe there was some dirt in the jack and that pulling the plug in and out several time cleaned it. It might only be a coincidence if it happened after flashing that sound mod. Anyway glad to know its now fixed. :good:

Categories

Resources