I have been using the mighty Samsung galaxy Note for over a month now. Great phone and futuristic features. but there is one small software hitch. Whenever i answer a call from an unknown number, the moment i end the call, the two touch buttons at the bottom end stop responding. They start working well after i switch off and turn on the phone. However, this does not happen every time. Is anyone else also facing the same problem? Any solution?
Related
Hello Guys,
a Friend bought a used i9000 on ebay for 130€ from a business man, which got a ne phone from his company and sold hin mobile on ebay and he asked me for a litte work around of his "new" phone.
Optically is the phone perfect BUT if I take a call on Android 2.3.6 display stays black (with backlight) and I can make the call. But I can't do anything more, hang up etc. If the opponent hangs up, I hear the hang up sound but display stays black and thephone wount do anything. So it's needet to pull battery, put it back and restart the phone. On doing a call, the phone has similar problems, it freezes.
After a couple of re-flashes with odin nothing changed.
So I tryed to switch to actual android OS. I flashed SlimBean 2.7. Every thing workes well. but even call-issues. If i receive a call, the phone woun't do anythin and it keeps ringing and "holds" the call for exactly 32 seconds. Now I can talk with the caller. But most callers don't wait 32 seconds to call to me If I do a call in JB I can talk from the first second on, but display freezes and I can't hang up. Thats the state for around 28 seconds and then phone will response normally and I can hang on and do everything I whant.
Even in Slim I tryed reflash a fiew times with no cahnge.
Has anyone an idea?
I think thats a hardware related problem. But in fact its possible to do a call, but only with that issues/delays. So I need a solution, that JB (SlimBean 2.7) don't "hold" the call/freezes for 32 seconds. I think because its every time 32 seconds, thats a fix value in JB. so I need something to cahnge the value from 32 secs to may be 0 oder maximum 5. But thats only guessed by me so I need help of a PRO here to solve that nerving issue.
I also tryed to install other dialers, but thats not a good solution, because the use for calling the stock rom dialer (phone.apk), damn
Please help me guys (sorry for my bad english )
UPDATE: I did read a litte in web and found, that the light sensor could cause issues in calling (start and end). So I downloaded a app whitch will show me he values of the light sensor. Ands its true, the sensor will show me whole time same values. I changed the sensor od the device of my friend and mine but that does not solve the problem. same issue.
In second Post I'll load a some Pictures of both devices up. My device shows around 30 lux and the one of my friend around 5.
UPDATE 2: After some more reading in web I found more guys with same call problem but no solution. May be it could help to disable GP2A Driver oder better only to overwrite the lightsensor value with a fix one.
UPDATE 3: OK I tested with 3 apps and the proximity sensor of the phone is broken ...now i need a solution to disable it or set a fix value in android so that the sensor is unused.
Any ideas?
UPDATE 4: I downloaded the "Hardware Disable" app from Play store and disabled GP2A.
It works for now, I just have to switch off the screen manually by pushing power button at a call and turn it on by pushing power again. But thats no problem for me anf my friend and much better as the call related freezes.
But I need at every startup to confirm to disable the sensor. So I'm looking for a permanent solution for this. Also because the device feels a little bit laggy now.
Pics
SOLUTION
So Guys I found a good working solution fpr proximity sensor delay, 32 second freeze by taking a call.
I wrote my Solution in SlimBean thread
http://forum.xda-developers.com/showpost.php?p=32809014&postcount=4406
Schould work on any ROM (GB, ICS and JB) because they all use the same Hardware .so (sensors.aries.so in this case)
My S5 seems to be possessed. Its not rooted (cant anyway) no rom, have done absolutely nothing out of the ordinary to the phone other then install my normal apps from the play store.
Yet the phone is constantly, about 20x a day just going to the 'call logs' screen. I've rebooted the phone, logged in and with nothing open poof call logs. It seems to happen more when my fingers are hovering near but not touching the screen, is there some sort of air gesture for call logs that I dont know about ? Its never any other screen, its not like its accidentally hitting the 'back' button. It is starting to get a bit annoying ..
I notice mine opens apps "on its own". Not sure if its a gestures or hover thing or what. Usually gallery or phone, which are right next to each other on my home screen (all the way left). Must have something to do with it.
trichert said:
My S5 seems to be possessed. Its not rooted (cant anyway) no rom, have done absolutely nothing out of the ordinary to the phone other then install my normal apps from the play store.
Yet the phone is constantly, about 20x a day just going to the 'call logs' screen. I've rebooted the phone, logged in and with nothing open poof call logs. It seems to happen more when my fingers are hovering near but not touching the screen, is there some sort of air gesture for call logs that I dont know about ? Its never any other screen, its not like its accidentally hitting the 'back' button. It is starting to get a bit annoying ..
Click to expand...
Click to collapse
YES!!! My Rogers (SM-G900W8) does it too! I thought it was probably because I installed something, but, now that I see you have the issue !!
I posted this same question in the Q&A section regarding the call logs. Ultimately , I factory reset my phone. That fixed whatever the problem was. It was annoying the crap out of me.
Sent from my Nexus 7 using XDA Premium 4 mobile app
peaster3 said:
I posted this same question in the Q&A section regarding the call logs. Ultimately , I factory reset my phone. That fixed whatever the problem was. It was annoying the crap out of me.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I found the problem, it was my galaxy gear 2, every time it 'checked' my phone for new messages it would leave the phone on the call log. I turned off the option to open content on my phone from my gear and all is well now !
I have been experiencing this issue since upgrading to Lollipop on my S5. I too have a Galaxy Gear 2. I have just disabled 'Smart Relay' in the Gear App (which is what I presume you were referring to) and so far all seems good Thanks.
I have owned pretty much every Galaxy phone so far and though I've loved each one, there's a few completely annoying issues that I end up having solve through a custom ROM, launcher, a developer script, or something along those lines. I thought for once with the Note 4 I would be able to for once keep everything stock besides having it rooted but it looks like I was wrong.
The issue I'm having right now is driving me through the wall. My phone answers phone calls AUTOMATICALLY ON ITS OWN when connected to BLUETOOTH.
It happens consistently, the exact same way, every single time. When I'm connected in my car it answers after exactly 2 rings (2 seconds). It is getting ridiculous and sometimes I just want to toss the phone out of the window while I'm driving down the freeway. Its extremely annoying to have your phone answer a call that you absolutely no intention of answering, ESPECIALLY WHEN I'M DRIVING. I'm tremendously busier in the past year and don't have time to sit and tinker like I used to or I'm sure I would've either solved this or gotten a new phone by now.
I already made sure auto-answer is OFF: Settings > Call > Call Accessories > Automatic answering [Box is not checked]
THIS IS DEFINITELY AN ISSUE WITH THE PHONE BECAUSE IT HAPPENS ON ALL 3 OF MY CARS & 2 OTHER CARS I'VE TRIED.
Please, if anyone knows how to fix this issue or anything about this completely ridiculous issue, please share.
Hi,
Recently I've started to experience call issues. During the call (not always) after some time (sometimes half miunte, sometimes 4 minutes, pretty random) audio is gone, we can't hear each other. After ending the call and calling other side again, there is some issue, call cannot be set up, i have to wait like 30sec/1 minute, and even after that audio is missing sometimes. My Note 5 is N920K, yesterday I've flashed latest official firmware (but there was DRK missing error), and flash Dr Ketan ROM after, and it didn't fix the problem.
Does anyone have any idea what could cause it? Is it hardware problem? If so, what i should change or how i can diagnose it?
So problem was with S8 port ROM
So here's a wierd one. Have a SM-N960U1 on Android 9. Everything's been fine but as of last Friday every time it pairs with a Bluetooth device (headphones, car, etc.) it starts calling itself? I re-paired all devices, turned BT off and back on, restarted phone, etc., but this behavior persists. Music is also terrible during this time, but realized by accident when I press Device Care widget to optimize phone the BT device announces 'Call Ending', and music again sounds great. However there's no record of any outgoing call in Phone App. I didn't realize what # was being called until I got in my car and saw it was dialing itself, but again, this phantom call does not show up in Recent Calls history? Any ideas?
Ugh... Same
Same man. Just letting you know you're not alone and following for a resolution.
smart lock on?
Removed all trusted devices from smart lock and it still happened.
Did a support Chat with Samsung, they recommended a soft reset (Vol dn + Power, similar to a Battery pull) which solved it temporarily when I turned on Bluetooth but since then the bug continues. No new updates or setup changes I'm aware of before this started happening. They also suggested running in safe mode and disabling Apps one at a time to see if the issue can be isolated (aren't these supposed to 'be' smartphones? Evidently there's no log of what it's doing) Will try that or another Chat session when I get some time again.
Ive been having this issue for a week or so as well. Every time I get in my car, I have to end the call. Its got to be a software update that caused the issue.
I'm thinking now it could be related to Bixby. I don't use it (remapped to google assistant & flashlight on long press using bxActions) but I recall I allowed it to update recently in case it gets better in the future.
Same issue here ... Sprint Note 9 on Pie ... Bluetooth headphones even has issues. I have to make a phone call and end it to be able to control volume from the headset (changing it from in-call audio to media audio).
Yup, those are the symptoms. Bluetooth headphones sound terrible and has no device control until the 'phantom' call that starts on it's own is manually ended.
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
ogretech said:
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
Click to expand...
Click to collapse
Awesome tip!
I use Ring Central App for keeping up with work phone messages. A few days ago started the phone in safe mode and had no BT issue, then back in 'un-safe' mode at first it didn't happen but cycling the headphones on and off it did occur again so I was faced with narrowing it down to which App. After reading your post I went into RC Phone settings, Mobile App Settings, Default Launching, and turned off 'Call From Android Dialer' since I don't use that feature and so far no issue!
Thanks for the tip, hopefully this setting change continues to solve this.
Still good after a couple days and weekly auto phone restart (Sat @ 3:00 AM). So nice not to have to end a phantom call that interrupts the stereo after 10 seconds every time I start the car.
Thanks again for the RC Phone tip.
You guys are definitely not alone. I unfortunately do not use the ring central app so I am not sure what is causing it for me...
I'm on the note 10 and have only had this problem pop up recently out of nowhere... I have no idea what could be my problem as I do not have RC Phone installed on my phone
Possible Solution
Hey, I posted a few days ago about having this same problem and not being a user of ring central. I got to thinking and tested this out. The Voxer app was the issue for me. I uninstalled this app and I haven't had any problems since. I am not sure about why the most recent Voxer update caused my phone to start doing this but I hope this helps someone else.
Possible Solution
Some may have tried this. Let me know.
My wife has Honda Hands Free 2016. In the past 30 days it started this same freaky behavior as all of you list.
She has a Samsung s9+.
She also has had Voxer installed on her phone and has had for many years. I will have to check to see if a recent update hit.
But, this is what seems to work for me at this point........
Told Honda Hands Free to completely forget her s9+. Then disabled blue tooth on the s9+.
Turn Entire Honda car off.
Turn Honda back on, told it to connect to my Samsung phone SM-J320A. Verified Honda was connecting properly to my SM-320A with no issues. All good with no freaky behavior. As info Voxer is not installed on my SM-320A.
Turned bluetooth back on s9+ then added the Samsung s9+ back to Honda Hands Free and told it to completely forget my SM-320A.
So far this has stopped the freaky behavior. If it comes back I will update here and then I will try uninstalling Voxer.