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
Related
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?
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)
Well ,it has happened before but I didn't want to exaggerate it ,so I left it just as it was until today .It's completely stock ,with custom recovery .It has happened to me since 5.0 and up until now 5.1 .
It doesn't happen always ,just "occasionally" when there is an incoming call ,Nexus 6 turns off itself .It happened now that I didn't even hear that it rang ,it just turned off ,but I know that my dad called me .
Has anyone ever experienced such issue ,is there a fix ?
To mention that it also gives an odd sound befire turning off :/
Same thing happening for me also with Nexus 6
And this keeps happening more frequently over recent months. This also happens when battery is below 30% and I am taking HDR+ photo. Maybe related to aging battery and apps getting more and more power hungry..?
@pauliusz: First, kudos for actually searching for a thread related to your problem. Too many don't bother. Second, replace your battery, as the shutdowns are in fact a direct result of the battery's age.
So I got the Android Pie update in Dubai a few days ago. then I did a factory reset as I like to have a fresh clean start with a new OS. Setup everything but now I noticed on 2 different occasions when I am in the middle of a phone call, I would stop hearing anything nor does the other part hear me. I'd then have to call them again and the call is back to normal for a couple of minutes then gets muted automatically. A restart fixes this sometimes but it's very annoying. Anyone else getting this?
i have a nokia 7 plus and after the pie update i noticed that some calls just end out of the blue. It can be 10 seconds into the conversation or 5 minutes. I cant see a pattern that would cause this. I once tried to call my GSM operators call center, it took me 7 attempts until i could finish my request. each time waiting 3-4 minutes to talk to somebody. Really annoying.
I had a simillar issue with a nokia 7 plus. After a carrier service update on the playstore, the issue disapeard.
No issue with my Sirocco, but i buyed it after the carrier update.
Anyone had this problem? The setting is toggled in the menu, it makes a noise on key press, but the call recipient doesn't seem to receive it.
Had this problem with my last handset (P20 Pro), and now realise I have the same issue again.
I will contact Pixel support tomorrow when they're open again, and currently on a slow web chat with Vodafone.
Just tried a few things, appears that they do work on ear piece, but not when on loudspeaker. Vodafone suggests the phone is faulty. I'll speak to Pixel support tomorrow.
If anyone has a few minutes spare, could you see if you have an issue with this?
mushtafa said:
Just tried a few things, appears that they do work on ear piece, but not when on loudspeaker. Vodafone suggests the phone is faulty. I'll speak to Pixel support tomorrow.
If anyone has a few minutes spare, could you see if you have an issue with this?
Click to expand...
Click to collapse
Has the same issue and came up with the same results. Speakerphone caused it to fail. I think the tone is being heard and picked up at the same time maybe. Switching to ear piece solved it.
Seems a very odd 'bug'. Wonder if there is a fix for it?
Used the Pixel support chat thing today.
I was told to force stop the phone app, uninstall all updates, and clear the cache from the app.
Install update for Phone app from Play Store, reboot phone and test.
Tried it twice and working at the moment.
Might help someone out.
After having this issue for over a year, I finally found a (so far) permanent fix. Update/change your APN settings on the phone. I am a T-Mobile customer so I went to the site to get the correct settings. I added a new one and everything has been going well.
I'd tried every fix I could find via googling, but nothing stuck longer than a day. It's been over a week and I'm still working. I hope this helps someone because this was the worst issue to have in this current video meeting era.