Related
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Happens to me too, but I don't manage to hang up or mute the calls normally. I'd love a solution as well!
Magicadder said:
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Click to expand...
Click to collapse
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
m00nshake said:
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
Click to expand...
Click to collapse
I'm using Stock firmware with bamf 4.3a Kernal
I've reset this thing too many times... installing different roms and such.. but I can verify that this is happening to another phone. My wife's phone does exactly the same thing. we purchased out tbolts on launch day ( if that helps )
The proximity sensor is located were the Verizon V is at
In between the big V is the sensor. Very hard to see go under a light a tilt the like you would if you want to find scratchs on your phone it really is between the V or I'm you can not find it. Make a phone call and get your index or any finger. And again make sure your under light and make the shadow of your finger go on top of the proximity sensor. Mine is very sensitive also.
-Monky_1
-Monky_1
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
calbruc said:
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
Click to expand...
Click to collapse
This is exactly what's happening. It's nice to see that I'm not the only one having this issue... even tho I'm sure it's annoying for everybody. Hopefully we'll be able to get some relief from this.
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
rizzomegav said:
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
Click to expand...
Click to collapse
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
BAMF 1.5 is based on the new leak, which includes a fix for the proximity sensor. If the rom you are running isn't based on the recent leak for our phones, then you don't have the fix, and will most likely have problems with it.
Check this thread out at droid forums! It fixed my "problem" with the proximity sensor. Simply blow out the sensor with air. Apparently dust gets in there and jacks it all up. I can confirm big time results with this method.
http://www.droidforums.net/forum/thunderbolt-tech-support/142050-thunderbolt-proximity-sensor-issue.html
Edit: All those kernel switches and setcpu tweaks over pocket lint!!! Damnitman!
Magicadder said:
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Click to expand...
Click to collapse
Well the fix is only to hold the phone correctly unfortunately. My gf has no problem using either phone (hers or mine) but if I touch them its muted hang up bam.
One of my coworkers has the same problem as me another dosent. Its absolutely user errorish IMO.
It works with my thunder bolt sort of the home key still works. I don't mind it, moreso than buggered calls.
this is not a signature I type it in every time maybe sent from my phone or my computer
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
A screen protector was an issues for me. The first one I put on did not fit perfectly, so the top of the protector cut directly threw the center of the sensor and collected dust and gave me some issues. The second one i used was applied from the top down to not obstruct the sensor. Solved my problem.
My phone sensor will black out when I am on a call and the phone is against my face, but when I pull the phone away the screen won't come back up for some reason..
I find that it seems to reflect off the arm of my glasses, which is kinda glossy like. When the IR LED reflects back at it, it seems to assume infinite distance. Same thing happened on my Droid.
There was also a case that lacked the cutout for the proximity sensor on the Droid... screen would never turn off because it reflected the IR.
I'm glad to see I'm not the only one with this problem. It's been happening to me for a few weeks now. I've run the majority of available ROMs and kernels (pre- and post- radio update) in multiple combinations so, I believe its safe to say they are not to blame.
I'm not using a screen protector so, that can't be to blame. And I don't have any scratches on my screen either. I'm curious about this dust theory though. It may be the best one I've heard yet. Has anyone else put the air hose to their Thunderbolt yet? I think I'm gonna give it a go asap. But, in the meantime, I'd love to hear whether anyone else has had positive results. If not, I fear I may have to move on to the glasses theory. I really hope it isn't that one though. I don't want to choose between having my Thunderbolt or my sight!
Mine still does it and I'm using the leak , so I don't think there is a fix in it. If so it doesn't work. Locking the screen seems like a pain but that's the best bet for now.
Sent from my ADR6400L using XDA Premium App
dzigns said:
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
After trying many ways to work around this problem with the proximity sensor I have found that this is actually works the best .... And I can't thank you enough..... I've grown used to this method and so far its flawless.
Thank you again
Sent from my ADR6400L using XDA App
So im running CM7 i believe and it is rooted everything is good on my phone just a couple of quick questions about things that seem to be annoying me.
1. Does anyone else's phone seem to heat up pretty quickly with extended use? For example if i've got the screen on and I'm texting for like an hour straight it gets pretty warm to a hot sensation right on the metal part that holds the SIM card in and the SD card. The phone also heats up when its charging too, i'm assuming that is normal.
2. I have ADW Launcher and the Cyanogen Mod or whatever it's called. The issue is that when I'm playing music and get a text my audio will completely pause (but the song keeps going) and then keep going which tends to get annoying when I'm enjoying a part of the song and I miss it entirely because of a notification. I've tried to set it up so that it ducks the audio 4db but it doesn't seem to work for me. Does anyone know how to fix this?
3. Sometimes when I receive texts i can hear it through my speakers of my computer coming but my phone will never fully "receive" it so it sits in limbo forever. Does this happen to anyone else?
4. Battery problems, it seems to die a little quicker than i'd like. I've got it on the lowest brightness, no internet, no bluetooth, no gps, wifi usually on but when i'm not near a wifi hotspot i turn it off. Is there a solution to this?
Thanks for any help in advance
jerfy said:
So im running CM7 i believe and it is rooted everything is good on my phone just a couple of quick questions about things that seem to be annoying me.
Click to expand...
Click to collapse
I'll try to answer them inline if I can....
jerfy said:
. Does anyone else's phone seem to heat up pretty quickly with extended use? For example if i've got the screen on and I'm texting for like an hour straight it gets pretty warm to a hot sensation right on the metal part that holds the SIM card in and the SD card. The phone also heats up when its charging too, i'm assuming that is normal.
Click to expand...
Click to collapse
Overheating is pretty much the norm on the G2X. Perhaps there are other ways to deal with this, but one way for sure is to go to settings-->applictions-->development and click stay awake. This reduces the overheating while charging. If you get a lot of overheating it might be the battery.
jerfy said:
. I have ADW Launcher and the Cyanogen Mod or whatever it's called. The issue is that when I'm playing music and get a text my audio will completely pause (but the song keeps going) and then keep going which tends to get annoying when I'm enjoying a part of the song and I miss it entirely because of a notification. I've tried to set it up so that it ducks the audio 4db but it doesn't seem to work for me. Does anyone know how to fix this?
Click to expand...
Click to collapse
Use another music player: https://play.google.com/store/apps/details?id=com.jrtstudio.AnotherMusicPlayer&hl=en
jerfy;297955263. Sometimes when I receive texts i can hear it through my speakers of my computer coming but my phone will never fully "receive" it so it sits in limbo forever. Does this happen to anyone else?[/quote said:
no help on this one sorry.
jerfy;297955264. Battery problems said:
Known g2x problem. I took the extreme solution and ordered an oversized battery from amazon(http://www.amazon.com/EZOPower-Exte...d=1344178238&sr=8-2&keywords=battery+g2x+3500) but you might want to just bring your charger with you....
Click to expand...
Click to collapse
Click to expand...
Click to collapse
jerfy said:
So im running CM7 i believe and it is rooted everything is good on my phone just a couple of quick questions about things that seem to be annoying me.
1. Does anyone else's phone seem to heat up pretty quickly with extended use? For example if i've got the screen on and I'm texting for like an hour straight it gets pretty warm to a hot sensation right on the metal part that holds the SIM card in and the SD card. The phone also heats up when its charging too, i'm assuming that is normal.
2. I have ADW Launcher and the Cyanogen Mod or whatever it's called. The issue is that when I'm playing music and get a text my audio will completely pause (but the song keeps going) and then keep going which tends to get annoying when I'm enjoying a part of the song and I miss it entirely because of a notification. I've tried to set it up so that it ducks the audio 4db but it doesn't seem to work for me. Does anyone know how to fix this?
3. Sometimes when I receive texts i can hear it through my speakers of my computer coming but my phone will never fully "receive" it so it sits in limbo forever. Does this happen to anyone else?
4. Battery problems, it seems to die a little quicker than i'd like. I've got it on the lowest brightness, no internet, no bluetooth, no gps, wifi usually on but when i'm not near a wifi hotspot i turn it off. Is there a solution to this?
Thanks for any help in advance
Click to expand...
Click to collapse
1. What kernel are you using?
2. Settings > Cyanogenmod Settings > Sound > Notification Focus?
3. Never heard of this...
4. Download this and check wakelocks and see what is running...
djvoleur said:
1. What kernel are you using?
2. Settings > Cyanogenmod Settings > Sound > Notification Focus?
3. Never heard of this...
4. Download this and check wakelocks and see what is running...
Click to expand...
Click to collapse
Kernal is [email protected]
I've tried to notification duck but it doesn't work. It's on right now but when im watching a youtube video or something it still cuts the audio out completely but still plays it while i listen to my notification ring
Also, once a phone is unlocked it is unlocked for good right? Even if i put different ROMs and such? Cause i bought this phone 2 months ago unlocked with it rooted and flashed with this stuff. I'm asking because I'm scared that if i try putting a different ROM on it that won't be unlocked anymore. I don't know the unlock code or anything lol
Edit: And i know the G2X camera is bad so I'm wondering if there is a way to make it permantly increase the exposure to +1 or +2 instead of me having to change that every time i open the camera app or is that not possible?
also im thinking of ditching the g2x all together for the samsung galaxy s2 do you guys think it is worth it? I don't know if the S2 has any problems as bad as this phone. It's going to cost me 100 dollars to upgrade to it in the end. Thoughts?? or maybe the samsung galaxy nexus
jerfy said:
also im thinking of ditching the g2x all together for the samsung galaxy s2 do you guys think it is worth it? I don't know if the S2 has any problems as bad as this phone. It's going to cost me 100 dollars to upgrade to it in the end. Thoughts?? or maybe the samsung galaxy nexus
Click to expand...
Click to collapse
I was going to do the same when I have the money to buy a new sgs2
Dustin Bieber said:
I was going to do the same when I have the money to buy a new sgs2
Click to expand...
Click to collapse
yeah i think im just going to get the nexus
jerfy said:
Also, once a phone is unlocked it is unlocked for good right? Even if i put different ROMs and such? Cause i bought this phone 2 months ago unlocked with it rooted and flashed with this stuff. I'm asking because I'm scared that if i try putting a different ROM on it that won't be unlocked anymore. I don't know the unlock code or anything lol
Click to expand...
Click to collapse
If your phone was unlocked (not the same as rooted) it will stay that way. ROM away as you wish.
Unlocked = can use on any SIM based carrier
Rooted = means you can do whatever you want to your phone software-wise.
I myself have the heat problem but it was partially fixed when I decided to mess the overclocking and undervolting made available by custom kernels. To fully fix this problem with my phone overclocked to 1.4ghz and undervolted I took some aluminium foil layered a few pieces together and cut it to the size of the back. I added a bit of extra aluminium to where the sim is because it seems like that is where most of the heat comes from and now my phone becomes warm but not warm to the touch now that it can disparate heat faster.
Very nice idea but wouldn't the aluminium retain the heat to the battery causing it to overheat
Sent from my LG-P999 using xda premium
I don't know but I have not had any problems with it so far and its been almost 3-4 months with this small mod.
I rooted a friend sgs2 for him. its through sprint. so far it doesn't seem very great semi laggy and I would not want 1. Sprint internet seems very slow as well. My g2x puts his sgs2 to shame. I did leave him on stock rom though so maybe it would be better if I souped it up
Sent from my LG-P999 using xda app-developers app
Hello everyone,
I recently obtained an S3 i535. At first, it was working very well. Suddenly the audio became wonky. Now, all audio that emanates from the phone speaker "stutters". This includes ringtones, notifications, music...even the boot audio on startup cuts in and out. Audio through the headphones works perfectly.
I am not completely sure when it started, but it seems that it was right around the time that I rooted.
I HAVE Odin'd back to 4.1.2, with no luck. The stuttering persists.
Also, FYI - at one point, this phone had shattered glass. . I had the glass replaced just before rooting....
Any ideas out there? Thanks in advance...
Mac
ripdoozer said:
Hello everyone,
I recently obtained an S3 i535. At first, it was working very well. Suddenly the audio became wonky. Now, all audio that emanates from the phone speaker "stutters". This includes ringtones, notifications, music...even the boot audio on startup cuts in and out. Audio through the headphones works perfectly.
I am not completely sure when it started, but it seems that it was right around the time that I rooted.
I HAVE Odin'd back to 4.1.2, with no luck. The stuttering persists.
Any ideas out there? Thanks in advance...
Mac
Click to expand...
Click to collapse
Can you provide us a little more detail? Stuff like:
Software:
What ROM are you running?
Are you running any audio mods?
Have you tried re-rooting?
What root method did you use?
Hardware:
Have you recently dropped the phone?
Have you tried to clean the phone's speaker with canned air?
Etc.
Thanks!
Sorry, I left out some info.
Running stock 4.1.2... just flashed back to stock. (problem has ocurred on multiple roms)
First time around used Casual root method.
I have not rerooted.
I have not dropped the phone recently and have not tried to clean the speaker with compressed air.
Thanks for helping.
Sent from my SCH-I535 using xda app-developers app
Kelter said:
Can you provide us a little more detail? Stuff like:
Software:
What ROM are you running?
Are you running any audio mods?
Have you tried re-rooting?
What root method did you use?
Hardware:
Have you recently dropped the phone?
Have you tried to clean the phone's speaker with canned air?
Etc.
Thanks!
Click to expand...
Click to collapse
Also, I just discovered that the sound works MUCH better when the phone is plugged in and charging. Not perfectly...but very nearly perfect.
If I unplug the charging cable. The audio barely works, if at all.
Though maybe this info might help with the mystery...
Thanks again
Mac
ripdoozer said:
Also, I just discovered that the sound works MUCH better when the phone is plugged in and charging. Not perfectly...but very nearly perfect.
If I unplug the charging cable. The audio barely works, if at all.
Though maybe this info might help with the mystery...
Thanks again
Mac
Click to expand...
Click to collapse
SOunds like maybe you broke something internally when you dropped it.
DigitalMD said:
SOunds like maybe you broke something internally when you dropped it.
Click to expand...
Click to collapse
If its charging and sitting on my night stand like it is right now, it works well. If I touch the screen, even without picking it up, it starts to cut out. Do you think it sounds like a hardware problem?
Could installing TWRP have anything to do with it? I installed it right after rooting/unlocking.
I am going to try to flash back to the first 4.1.2 ota. If that doesn't work, I will try to flash to 4.1.1. Personally, i think something got messed up during the root process because it didn't go smoothly the first time....I had to try a second time to get it to work, then the problem started.
Btw, this was my friend's phone. She dropped it, shattered the glass and wanted to get an iPhone. I convinced her to give me the phone, then I had the glass repaired. The speaker was working perfectly until around the time I rooted.
ripdoozer said:
If its charging and sitting on my night stand like it is right now, it works well. If I touch the screen, even without picking it up, it starts to cut out. Do you think it sounds like a hardware problem?
Could installing TWRP have anything to do with it? I installed it right after rooting/unlocking.
I am going to try to flash back to the first 4.1.2 ota. If that doesn't work, I will try to flash to 4.1.1. Personally, i think something got messed up during the root process because it didn't go smoothly the first time....I had to try a second time to get it to work, then the problem started.
Btw, this was my friend's phone. She dropped it, shattered the glass and wanted to get an iPhone. I convinced her to give me the phone, then I had the glass repaired. The speaker was working perfectly until around the time I rooted.
Click to expand...
Click to collapse
Software is never intermittent , hardware is. I suspect you have a lose connector to the speaker inside, I can;t tell you how to fix it, but I'm sure you can find some disassemble instructions that will show you the connectors.
DigitalMD said:
Software is never intermittent , hardware is. I suspect you have a lose connector to the speaker inside, I can;t tell you how to fix it, but I'm sure you can find some disassemble instructions that will show you the connectors.
Click to expand...
Click to collapse
Thanks MD. I pulled the back off the phone and reseated the speaker connection. All is working well...for now at least.
Thanks again.
Mac
And now....the stutter is back....great!
Sent from my SCH-I535 using xda app-developers app
ripdoozer said:
Thanks MD. I pulled the back off the phone and reseated the speaker connection. All is working well...for now at least.
Thanks again.
Mac
Click to expand...
Click to collapse
I have discovered that, after a battery pull, the speaker works much better, then deteriorates over time. I am confused.
So I rooted my Skyrocket last week and I screwed something up and since than I've had problems with the audio on the phone part. So I'm running Odin and even after double and triple checking I managed to screw it up by not having Auto Reboot checked. In a panic (and after waiting a long time) I unplugged the phone and powered it down. I booted into Recovery and did a wipe and installed CM 10.1.2 and I swear it worked fine for a week but all of a sudden I started having this weird issue with the phone audio. I'll call a number up and I won't be able to hear anything but I can put it on Speaker and it comes through fine or if I use my Bluetooth Headset it works fine.
I reloaded CM 10.1.2 and still nothing. I tried a nightly, I tried 10.1, I tried Beanstalk, and I now I'm back to stock and no luck on the phone audio. I have no idea what to do. I've tried Google searching and I'm coming up with a bunch of things but not what I'm looking for. I've even found some people having similar problems but they got no answer as well and I'm waiting to hear back from them (I found at least three people reporting the problem over on Cyanogenmod's Skyrocket Forum). I found some reference to it possibly being a Kernel problem. Thoughts?? I'll do some reading up on that tonight.
As a last resort I'm looking into buying a used Skyrocket to replace this one because I'm still 6 or 7 months till I'm eligible for an upgrade. HELP!
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
jd1639 said:
Edit, sounds like a hardware problem.
Have you tried to odin back to stock?
Click to expand...
Click to collapse
Oh and yes I've tried back to stock with no luck.
dfwjose said:
Oh and yes I've tried back to stock with no luck.
Click to expand...
Click to collapse
Seems like you have your answer then. If the problem persists regardless of which ROM or kernel you're using then logically it would seem that it can't really be software related, right?
Brought to you but time and relative dimensions in space.
dfwjose said:
Well I wondered about the hardware problem myself but it was working fine before I flashed everything and was working fine for a while afterwards. But I do have an issue with hardware. A few months ago I ran over the tip of my headphones at work with my chair and broke it off. Without thinking about it I put the tip back and reinserted it back on the phone again. I immediately realized what I had done and when I pulled the headphone jack out the tip remained inside the phone. I'm pretty sure it's caused some odd issues with my phone when trying to play audio using the speaker as sometimes it would play and other times I would hear anything unless I played it through Bluetooth. I took the phone apart thinking I could get to the tip that's inserted in there but it really can't be reached.
With the new phone audio problem I didn't think it was related because it was working fine before and for a little while afterwards. Plus I've seen other people post on the Cyanogenmod Forum about having the same problem so I'm not sure.
So no thoughts on it being a Kernel issue or some other software problem?
Click to expand...
Click to collapse
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
And just like that I'm up and running again and my phone works. I had given up and was having problems with a CM nightly so I did another wipe and loaded a stockish AT&T ROM that I've installed before and no my phone is working fine. I'm going to leave this thing alone until I pick up a spare phone!!
xcrazydx said:
You have to get the piece out dude. It's making contact intermittently and killing the audio.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I'm sure it is and that's why I took the phone apart to see if I could get to it. I tried all kinds of things to get that tip out before tearing the phone down and I had no luck. I should have taken some pictures but I've tried tweezers (everything I had was to big or to weak to pull it out) and even glue before resorting to taking the phone apart. Unfortunately with the design it's enclosed all the way around with no way to really get to it. I even thought about replacing it but that piece looks to be soldered on.
In the end, I might just send it back to Samsung and see if they will fix it. Not sure if it's worth it but I never got serious about it because I didn't have a spare smart phone other than my work iPhone.
I shouldn't have spoken so soon. Rebooted the phone and it's locking up now. I give up. I can't find anything that will work. I either have sound with a phone that locks up or have to live with Speakerphone/Bluetooth and be able to reboot.
Hi all,
I wasn't able to find any threads related to this in the S6 forums but I wanted to see if anyone else has this. When I open my camera app, sometimes the camera takes 1-2 seconds to initially focus and during that time it makes a loud buzzing sound. It sounds like a focus motor or something in the camera and the camera output on screen flutters while it focuses. Once it focuses, everything is normal and it doesn't make any more noise to refocus. This also doesn't happen every time I open the camera app, seems mostly random. Has anyone else experienced this? I am already on my 2nd S6 since the first was defective for different reasons and I'm starting to get very disappointed with Samsung quality control.
I have the dame problem.
I don't know if this is normal.
I don't think so
Waiting for some explanations
Sent from my SM-G920F using XDA Free mobile app
going to bumps this too because after having the phone for a month this problem has just started to show its face.
I've first noticed a small buzzing just after a boot for 3/4 times and than I had a long one opening the camera. After that it's gone...
I have it also! Started a couple of days ago. I have dropped my phone a couple of times. What about you?
Had this happen for the first time today also. Had hdr off, switched back on and it went away. Coincidence? Phone never dropped.
rakh1 said:
Had this happen for the first time today also. Had hdr off, switched back on and it went away. Coincidence? Phone never dropped.
Click to expand...
Click to collapse
Relax...is the mechanism of optical stabilization.
Mine is doing that too...
https://www.youtube.com/watch?v=W1svaTxBY6o&feature=youtu.be
I have the same problem. It is also sometimes accompanied by the picture wiggling in wave patterns.
flu13 said:
I have the same problem. It is also sometimes accompanied by the picture wiggling in wave patterns.
Click to expand...
Click to collapse
Yup...exactly.
poweroutlet said:
Hi all,
I wasn't able to find any threads related to this in the S6 forums but I wanted to see if anyone else has this. When I open my camera app, sometimes the camera takes 1-2 seconds to initially focus and during that time it makes a loud buzzing sound. It sounds like a focus motor or something in the camera and the camera output on screen flutters while it focuses. Once it focuses, everything is normal and it doesn't make any more noise to refocus. This also doesn't happen every time I open the camera app, seems mostly random. Has anyone else experienced this? I am already on my 2nd S6 since the first was defective for different reasons and I'm starting to get very disappointed with Samsung quality control.
Click to expand...
Click to collapse
Try to clean up your camera lens.
Did your device take some damage in the past?
Did you take it underwater? (The S6 isn't waterproof anymore...)
---------- Post added at 18:59 ---------- Previous post was at 18:58 ----------
sdfsdfsfs said:
Relax...is the mechanism of optical stabilization.
Click to expand...
Click to collapse
But it's not that loud.
Otherways, you can't record videos properly, because the microphone records those sounds.
AfroCreame said:
Mine is doing that too...
https://www.youtube.com/watch?v=W1svaTxBY6o&feature=youtu.be
Click to expand...
Click to collapse
Same problem here since last week.[emoji26]
I tried hard reset and another camera app (Google photo), nothing work.
I think it's a hardware problem, it occurs after shaking the phone and launching the camera.
I feel that the OIS makes more noise when app is off.
flu13 said:
I have the same problem. It is also sometimes accompanied by the picture wiggling in wave patterns.
Click to expand...
Click to collapse
This started happening with my S6 today. I think it's the OIS that poops out. I can make this happen with a light tap with my finger on the backside of the phone with the camera open and using the rear camera. And this happens with all camera apps: Samsung's bundled camera, Snap Camera and Camera FV-5.
Update: ..and just as sudden this started happening, it went away again. I hope it's a bug - with a fix in 5.1.1.
Update 2: No, it didn't go away. It comes and goes. I may need to take the phone to the service centre.
Mine has gotten worse. Almost every time I open the camera now, I have the buzzing.
Just checking in to say that mine started doing this, too, about four weeks after getting it. It does it randomly when I open Snapchat, too.
I am having this problem too on the Sprint version sometimes it is pretty loud. I'm planning on taking to service center I think.
I also get the waves before it focuses. I read on another forum that someone said they went to a Samsung service center and Samsung replaced their OIS sensor so I'm guessing this may not be something that is simply part of the design.
*Update #1*
I just got off the phone with Samsung customer service. The representative actually heard the buzzing from my phone over the phone while I was talking to her. Since the phone is still under factory warranty they are emailing me a shipping label to send the phone back for repair.
I also have Asurion insurance through Sprint but do not want a refurb for a phone that is less than a month old with no damage caused by me.
Unfortunately the turn around time from Samsung is about a 5 business days and that was after they told me 9-11 days in which I said I couldn't be without a phone that long.
So, I plan on going to Sprint to see if they will swap out my phone for a brand new one. I think if it is a manufacturer defect they will replace the phone without going through insurance for a refurb but I am not positive. It they won't swap it out for a new one I will go through Samsung.
Sent from my SM-G920P using
Tapatalk
what about focus struggle and a buzzing , it's a hard ware issue also ? or what ?
sonasteel said:
what about focus struggle and a buzzing , it's a hard ware issue also ? or what ?
Click to expand...
Click to collapse
Yes it appears to be hardware related.
Sent from my SM-G920P using Tapatalk
any one try to set another mega pixel like 12 , 8.9 ,8 ... etc ., and the focus struggle and buzzing still there ?
sona4steel said:
any one try to set another mega pixel like 12 , 8.9 ,8 ... etc ., and the focus struggle and buzzing still there ?
Click to expand...
Click to collapse
I tried and initially it doesn't seem to happen when the mega pixels are lowered but I haven't tested extensively.
I went to Sprint today and the technician concluded that he was ordering me another phone so definitely seems hardware related.
Sent from my SM-G920P using Tapatalk