I know CM10 has been made "stable" on this device but I just have a few questions regarding it. My wife has been using the nightlies since the first previews were available and I'm not sure if our issues are common or something I am doing wrong.
She is currently on a nightly from a few days ago but these issues have persisted for about a month. I have done a full wipe and flash multiple times and we still have the same issues.
Skype: She can't barely here the other user and the other user hears nothing but static. I have tested with multiple other users. I have wiped data for Skype and reinstalled it, still has the same issue.
Force Close - Many apps. Happens randomly and it's not the same apps every time. I feel it is an OS issue and not an app issue.
Speakerphone is randomly activated by default. She usually has to tap the mic button a few times (deactivate, reactivate, deactivate) in order to get it switched to the handset.
Depending on what nightly she flashes the caller on the other end gets echo. It hasn't been happening with recent flashes but every couple weeks it pops up again for a nightly and then disappears.
I understand there are many issues due to Samsung not releasing sources, etc, just want to verify I am not alone. I have looked through the forums and see some people have some of the issues from time to time but I am hoping for some verification.
Thanks for everything.
I noticed the same thing a few days ago on Skype but didn't think much of it at the time.
Just checked again and sure enough I'm having the same experience you are with static.
Flashed back to stock and the problem disappears.
Must be a problem with CM10.
Ever try flashing the Stable version? Or a different rom for that matter? Maybe AOKP?
The issue existed before Stable and it exists in Stable. I just tried [ROM] AOKP(Jellybean 4.1.2)Task & Ktoonsez (11/18) and the issue with Skype exists there as well. If anybody knows of a AOKP or CM build that doesn't have any issues I would swap over. I have been wiping and flashing roms like crazy lately and I we really can't stand stock samsung rom. I may end up selling the phone and picking up something different, it's quite frustrating. Last time I buy a Samsung phone, that's for sure. They basically **** on devs.
DarthDerron said:
Ever try flashing the Stable version? Or a different rom for that matter? Maybe AOKP?
Click to expand...
Click to collapse
I see you have the same phone as my wife. Any chance you have time to test Skype on your current rom? If so thanks in advance, I appreciate it.
Sent from my LG-E973 using xda app-developers app
Thanks guys. Just going to return her to stock and sell it. Going to find a device with better support from manufacturer.
Sent from my LG-E973 using xda premium
Related
Every time I root my phone install custom ROMS or Kernels it will always Crash or reboot it self every time. I have tried unrooting the device several times I also tried Tried very popular ROMs like AOKP & CM and still they end up crashing within a day of use. I don't know what I am doing wrong here... I assumed it was the phone so I called Verizon to send me a replacement one but if anyone knows why this is only happening to me and not all the rest of my friends even Fiance then please let me know....
At the moment I am on stock ROM and Stock Kernel and still rebooting and crashing every time and its rooted so if anyone has any idea please let me know i am about to give me on this Phone....
P.S. If you have recommendations on ROMS or Kernels I can try besides Franco or Trinity that will be great, I also tried them and also the same problem
My gnex has recently started to do this as well. I think its an overheating issue because it'll "crash" when it feels really hot.
Sent from my Galaxy Nexus using xda premium
Greetings,
First post here, I hope this is the appropriate section for it. I have google'd and forum searched extensively and have yet to find a thread dedicated soley to this issue. Many people have reported it within various ROM threads only to have the next poster state he doesn't have the issue and the problem get buried in a 500 page thread.
Having gotten my feet wet with the stock ICS ROM that came with my Galaxy S3, I was happy to enter the world of custom ROM's and flashed CM 10 M2 as my first custom ROM. I was very much enjoying CM 10 when I received my first phone call after switching. Being an exclusive speakerphone user, I answered the call and enabled the speakerphone as usual. The caller stated they couldn't understand me as there was an echo on the line. I turned speakerphone off and they stated the problem was fixed. After finishing the call, I called my cell phone from my landline and enabled the speakerphone on my S3, then walked to the other side of the house to minimize any close vicinity interference. When I spoke into my landline I could hear myself echo making a conversation almost impossible. I disabled the speakerphone on my S3 and the problem went away.
I restored my stock ICS ROM and was unable to duplicate the problem. I assumed the bug was specific to CM 10 and tried AOKP JB milestone 1 and had the same issue. Today I tried Task and Ktoonsez's latest AOKP JB 4.12 ROM and The Collective's AOCP ROM with the same results. All the problem ROM's were JB builds so perhaps it's a JB related issue. I will be trying a touchwiz based JB ROM next to see if I still have the issue.
I think alot of people assume when they read this bug report they blow it off as they can't actually hear the echo unless the person on the other line reports it. Maybe alot of people don't use speakerphone? I don't think it's a universal problem or more people would be reporting this but it's not intermittent either. I can reproduce it 100 percent of the time and it goes away when I recover to stock. I also removed my case when testing this and it had no effect. If there is a workaround or fix for this I would be very thankful to learn of it as I very much enjoyed the custom ROM's but I just can't give up speakerphone. Thanks in advance! :fingers-crossed:
I'm having the same issue...
+1
Follow up
kenrothman said:
I'm having the same issue...
+1
Click to expand...
Click to collapse
So today I tried newest builds of Parandoid Android, and Liquid Smooth with the same result. Pretty much all the popular ROM's in the "AT&T Galaxy S III Original Android Development" contain this bug, I'm assuming because they share alot of code. Seems like they base alot of work off of Cyanogen Mod so perhaps that's where it lies, I don't know.
What I do know is I installed DrewGaren's Jellybean 747 Milestone 7 ROM which is Touchwiz based and the speakerphone echo went away. So my stock ICS ROM and this one do not contain the issue but every other JB based ROM I have tried does. I don't have the knowledge to troubleshoot this issue I just wanted to share what I've found and hopefully someone with the knowledge can help track it down.
I do prefer the CM 10 style ROM's over the stock experience but I can't live without speakerphone so hopefully this issue gets resolved, thanks for listening!
I have the problem too. I bought my S3 3 weeks ago and within a few days rooted it and installed the latest CM10 nightly. The first time I used the speakerphone I became aware of the echo problem with the it. So I switched back to the stock rom and the problem was gone, so I knew it wasn't a hardware problem with my phone. I've tried every nightly CM10 rom including the recently released stable build. I also tried the latest official AOKP as well as Task and Koonsez's latest build and they all produce the echo.
My buddy suggested I try the black jelly rom, and that's the only one I've been able to use that doesn't have any echo, but it's a touchwiz/Samsung based build. It's not bad, but it doesn't support wifi tethering and it's not as smooth as CM or AOKP. I really want to run CM but can't live without speakerphone.
On a side note, I rooted and rom'd my wife's and friends S3 the exact same way as mine and neither of theirs have the speakerphone echo problem. I suspect there are some hardware differences with Samsung phones. Maybe different parts suppliers that aren't playing properly with the drivers in the CM10 build.
From my tests this bug sounds like the mic is turned up max when speakerphone is on so it's super sensitive. Also, the volume level doesn't have any effect on the speakerphone volume whether you raise or lower it.
Really hope the dev's can fix this so I can run CM or AOKP once and for all.
On a final note, my phone is blue, while both my wife's and my buddy's are white. I don't want to conclude that the white phones don't have the speakerphone echo problem with CM roms. Hope it's just a coincidence.
for cm10 there is an official bug ticket for it here : https://code.google.com/p/cyanogenm...on Model Network Owner Summary Stars Priority
Randomacts said:
for cm10 there is an official bug ticket for it here : https://code.google.com/p/cyanogenm...on Model Network Owner Summary Stars Priority
Click to expand...
Click to collapse
thanks for pointing that out. looks like it's not really a popular issue, or popular enough to get them focussed on fixing it
anyone have any thoughts as to why identical phones don't behave the same, ie some S3's have the echo and some don't? I have 3 days left (30 day purchase return policy) to exchange my phone, and am contemplating getting it swapped to see if I get lucky with another unit which won't have an echo problem running CM10 or AOKP.
gots54 said:
thanks for pointing that out. looks like it's not really a popular issue, or popular enough to get them focussed on fixing it
anyone have any thoughts as to why identical phones don't behave the same, ie some S3's have the echo and some don't? I have 3 days left (30 day purchase return policy) to exchange my phone, and am contemplating getting it swapped to see if I get lucky with another unit which won't have an echo problem running CM10 or AOKP.
Click to expand...
Click to collapse
Hi, just wondering if anyone has found a fix for this or any other AOSP JB Roms that has the speakerphone echo fixed?
ladd76 said:
Greetings,
First post here, I hope this is the appropriate section for it. I have google'd and forum searched extensively and have yet to find a thread dedicated soley to this issue. Many people have reported it within various ROM threads only to have the next poster state he doesn't have the issue and the problem get buried in a 500 page thread.
Having gotten my feet wet with the stock ICS ROM that came with my Galaxy S3, I was happy to enter the world of custom ROM's and flashed CM 10 M2 as my first custom ROM. I was very much enjoying CM 10 when I received my first phone call after switching. Being an exclusive speakerphone user, I answered the call and enabled the speakerphone as usual. The caller stated they couldn't understand me as there was an echo on the line. I turned speakerphone off and they stated the problem was fixed. After finishing the call, I called my cell phone from my landline and enabled the speakerphone on my S3, then walked to the other side of the house to minimize any close vicinity interference. When I spoke into my landline I could hear myself echo making a conversation almost impossible. I disabled the speakerphone on my S3 and the problem went away.
I restored my stock ICS ROM and was unable to duplicate the problem. I assumed the bug was specific to CM 10 and tried AOKP JB milestone 1 and had the same issue. Today I tried Task and Ktoonsez's latest AOKP JB 4.12 ROM and The Collective's AOCP ROM with the same results. All the problem ROM's were JB builds so perhaps it's a JB related issue. I will be trying a touchwiz based JB ROM next to see if I still have the issue.
I think alot of people assume when they read this bug report they blow it off as they can't actually hear the echo unless the person on the other line reports it. Maybe alot of people don't use speakerphone? I don't think it's a universal problem or more people would be reporting this but it's not intermittent either. I can reproduce it 100 percent of the time and it goes away when I recover to stock. I also removed my case when testing this and it had no effect. If there is a workaround or fix for this I would be very thankful to learn of it as I very much enjoyed the custom ROM's but I just can't give up speakerphone. Thanks in advance! :fingers-crossed:
Click to expand...
Click to collapse
+1
speakerphone echo
I also have this problem. using baked 8. with kt747 and its awesome!! They seem to be aware and working on it. tried a different kernel but no dice. Ive been in every setting cant seem to get rid of it. my phone is white so its not that. hope someone can figure this out soon. tw roms dont have this problem and I like the aosp feel.It would be nice to know if anyone even an idea of the cause, maybe the users could check files and find something.
I confirm that I LOVE these ROMs, but absolutely need a working speakerphone too.
Some other thread said something about changing the radio to ULVA3 or something like that... not sure if anyone had any luck with that.
Anyways, thought I'd break my lurked tendencies and post for my 1st time here.
Love my GS3!
So I've been very happily using the Samsung-based ROM called Devils Reject since Dec 2012, and have been on V7 since it came out a few months ago and have been really happy with it. It's pretty smooth and stable, has great battery life, has tethering, custom toggles, various battery icons, AOKP lockscreen, power button menus, plus a bunch of other stuff I can't remember, and of course, there are no speakerphone problems.
But I've always been curious about giving CM another chance with CM10.1 and especially with the latest RC2 out.
Does anyone know if the speakerphone bug still exists with it?
speakerphone echo bug in CM10.1 RC2 for quincyatt
gots54 said:
So I've been very happily using the Samsung-based ROM called Devils Reject since Dec 2012, and have been on V7 since it came out a few months ago and have been really happy with it. It's pretty smooth and stable, has great battery life, has tethering, custom toggles, various battery icons, AOKP lockscreen, power button menus, plus a bunch of other stuff I can't remember, and of course, there are no speakerphone problems.
But I've always been curious about giving CM another chance with CM10.1 and especially with the latest RC2 out.
Does anyone know if the speakerphone bug still exists with it?
Click to expand...
Click to collapse
I have the speakerphone echo bug on my Samsung Galaxy Note with CM10.1 RC2. This has happening on earlier versions as well, but I thought a reset/wipe fresh install would fix it. Would like to stay on CM10.1 but I really depend on my speakerphone.
Hello and thank you in advance to all. I have a t989,
I run AOKP Galaxysbean V_12
KKO Kernel Governor is Smartass V2 and I/O is deadline
UVLI4 Radio
Problem: I know for a fact this is not a hardware problem, because I have went through 3 phone replacements because of stupidity and learning how to root phone, flash roms, yada, yada, etc. And with each of these phones this persistent problem occurs where all of the sudden at any given time, I will go to make a call and nothing. I can't hear the ring of another person's number, my voicemail, etc. The person does get the call, and when they answer, I still cannot hear them, and they cannot hear me.
Resolution: Ways I have fixed this before are with the first and second phone I flashed over a new radio, (previously UVLE1, UVLH1, 4G Blaze) and it fixed the calling upon reboot. Also I had flashed custom roms, or restored previous Nandroid backups and it worked again. (Little annoying doing this every 3 or 4 days. Though today, this happened with my newest phone, and flashing a radio did not work nor did restoring a Nandroid. This time I had to flash a new custom rom, then it worked. Then I flashed back over the Nandroid and it still works as of now.
Question: Could this be because of the kernel? Or the rom?
deleted
same here
Me and my wife have the same issues. We both have GS2s but hers is stock unrooted and mine is running CM10.1. Been dealing with Tmobile for months without success, swapping out cut down on how often its happening but did not fix it. Tmobile is stumped, very annoyed by this issue.
Not sure what's causing the problem but it seems jellybean 4.2 has fixed this issue. Try flashing AOKP 4.2 and make sure noise suppression is enabled and call this number 9143388802. The third option is an echo test and fourth option let's you record a playback to listen to how you sound. If you sound normal and people are still complaining then its their phone.
Sent from my SGH-T989 using xda app-developers app
I've come to the conclusion that its a rom problem because for me it happens with only certain roms. Ive tried all the rom kernel combinations and different radios but the only fix I've found is to retire that particular rom, no matter how good it is. Smoothness aint gonna get the cops or the fireman to your house. The only roms that have worked for me as far as call quality are, for some reason all of TheLastSidekick's Kangs, Darkside evolution 3, Sky Jellybean, Rushing's Bulletproof,and both of the 10.1 variants we have. The strange thing is I can't recall any call quality issue's when flashing roms from the Skyrocket thread. For instance I get the worst call quality ever using Jedi Jelly, but I'm crystal clear using Embryo from the Skyrockets thread, so much so I wont even try our version of the same rom.
I blame T-Mobile network. This would happen to me all the way back to my old flip phones. Every other call or so would do this. I've always put up with it cuz I like T-Mobile customer service.
Sent from my SGH-T989 using xda app-developers app
bonetweeter122 said:
I blame T-Mobile network. This would happen to me all the way back to my old flip phones. Every other call or so would do this. I've always put up with it cuz I like T-Mobile customer service.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I wouldn't go that far because I never had a problem on the Sensation no matter what rom I was using. I blame sammy
You know.. Now that I think about it.. My old flip phones were Samsung! Lil..
Sent from my SGH-T989 using xda app-developers app
I actually just realized this problem persisted when I would turn on the phone and try to make a phone call to quickly. After becoming aware of this. I turned the phone off and allowed it to fully boot back up, and it worked again.
deleted
WatchGintama said:
I can confirm that this is the problem. I rebooted my phone, called someone right away, and couldn't hear anything. Next I let it load for 40 seconds after boot, and I can hear fine.
Now we have to tell t-mobile this.
Click to expand...
Click to collapse
This is not the issue, it also happens to phones that have been on for minutes/hours/days.
Is there any updates on this issue? My wife is having this problem on her phone, and it seem like it's been getting worse...
gwuhua1984 said:
Is there any updates on this issue? My wife is having this problem on her phone, and it seem like it's been getting worse...
Click to expand...
Click to collapse
I found out with my problem. It was when I tried to make a call to soon. It would do this. As long as I have let the phone load for a minute or two after boot, I haven't had any more problems. My problem may be different from yours tho. Hope this helps.
I'm having this issue, and its not from calling too quick after a boot.
It came on out of the blue the evening of March 6 ...
I have the Tmob phone but it's unlocked and I'm using a Straight Talk AT&T SIM, connected to the AT&T network in Sierra Vista, AZ.
Ok... I need help. I am such a novice at this stuff but I find myself so very interested in the world of root, and the freedom that it brings. Basically my entire knowledge of computers..... Is Android, and worse than that, I'm self taught... Please don't run!! I'm a super quick study. Ok now to my problem, I started off rooting my T 989 surprisingly enough with absolutely no issues at all, or at least that I could tell. Ran beautiful and super smooth, then I went app hoarding and installed A fonts package installer, opened it, it installed about 85 prcnt. done and crashed. Never made it back. The novice, and the dumbass in me, FREAKED! and did an uneducated, no experience attempt to make recovery....... 4 times needless to say that I COMPLETELY wiped the entire phone. I had a friend bless me and show me a thing or two and I successfully managed to flash one of your Roms to it and I must tell you that I supremely thankful to all who n these projects.... MAD RESPECT to all of you. So the one issue I am clearly having is everyone I speak to says I sound like I'm on speaker or just can't generally hear me. Been through the settings a couple of times and I am pretty sure that I have them correct, and I have not touched anything that I wasn't sure about, and I definitely have completely refrained from pimpin my kernel. I really just need someone who can spend a little time setting me straight on some unfamiliars. Also just have a few stupid questions that won't be the least bit stupid after I get them answered. Any time any one can lend would be greatly appreciated and someone's good deed for the day. Thanks for allowing me to vent guy's
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
---------- Post added at 05:03 AM ---------- Previous post was at 04:54 AM ----------
And no, issue definitely is not exclusive to happening on reboot, mine has been that way ever since flashing, and on every call. But I can hear the other end perfectly......
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
neilc300 said:
Ok... I need help. I am such a novice at this stuff but I find myself so very interested in the world of root, and the freedom that it brings. Basically my entire knowledge of computers..... Is Android, and worse than that, I'm self taught... Please don't run!! I'm a super quick study. Ok now to my problem, I started off rooting my T 989 surprisingly enough with absolutely no issues at all, or at least that I could tell. Ran beautiful and super smooth, then I went app hoarding and installed A fonts package installer, opened it, it installed about 85 prcnt. done and crashed. Never made it back. The novice, and the dumbass in me, FREAKED! and did an uneducated, no experience attempt to make recovery....... 4 times needless to say that I COMPLETELY wiped the entire phone. I had a friend bless me and show me a thing or two and I successfully managed to flash one of your Roms to it and I must tell you that I supremely thankful to all who n these projects.... MAD RESPECT to all of you. So the one issue I am clearly having is everyone I speak to says I sound like I'm on speaker or just can't generally hear me. Been through the settings a couple of times and I am pretty sure that I have them correct, and I have not touched anything that I wasn't sure about, and I definitely have completely refrained from pimpin my kernel. I really just need someone who can spend a little time setting me straight on some unfamiliars. Also just have a few stupid questions that won't be the least bit stupid after I get them answered. Any time any one can lend would be greatly appreciated and someone's good deed for the day. Thanks for allowing me to vent guy's
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
---------- Post added at 05:03 AM ---------- Previous post was at 04:54 AM ----------
And no, issue definitely is not exclusive to happening on reboot, mine has been that way ever since flashing, and on every call. But I can hear the other end perfectly......
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Just leave me some thanks. Under your phone settings, there should be a noise surrpression box. Make sure it is check marked. Every time I do that people have said I sound better. What do you want to do? Change it back to custom rom? P.S. ALWAYS MAKE A NANDROID BEFORE YOU DO ANYTHING.. ALWAYS ALWAYS ALWAYS!.. Google will solve many questions too. If nothing helps or you need to be walked through some processes, message me.
Enable noise suppression in phone settings. Fixed my problem.
[ NEXUS⁴ / VANILLA ROOTBOX / APEX PRO / TAPATALK ]
dEris said:
Enable noise suppression in phone settings. Fixed my problem.
[ NEXUS⁴ / VANILLA ROOTBOX / APEX PRO / TAPATALK ]
Click to expand...
Click to collapse
I'm running cm10.1 nightlys as and I cannot find that setting.
Trbobuick said:
I'm running cm10.1 nightlys as and I cannot find that setting.
Click to expand...
Click to collapse
Open phone dialer, menu settings, and it's in there.
Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
heartspains88 said:
Hey all,
I've had this issue with everything but the stock rom. After a certain amount of time the phone either locks up to where I have to pop the battery, or will graphic glitch on the screen for a second and then auto reboot. Happens maybe 2-4 times a day depending on the day.
I've done a full wipe and full factory reset. I've been modding phones for ages and this is the first time I've encountered this issue. Everything else seems to run completely fine.
I'm running resurrection rom, but it's done this on several other roms I've tried. However all roms are AOKP/AOSP based if that's relevant.
If there is anymore information I can offer please don't hesitate to ask. I searched the forums and couldn't seem to find anyone else really talking about this. It can be a giant headache so hopefully I can get it sorted.
Click to expand...
Click to collapse
If this has just started recently in would say it is indeed apart of the cm base, and related to kernel issue. Since the kernel devs are using cm and their kernel base most ROMs kernels have the same base, which means in a round about way they may react the same way on your device. To me, you said graphic glitch, then reboot. I would bump up your voltage little by little and see if it stops, I also would change govs in the kernel.. I'm assuming it happens on any cm kernels you've tried? Yank555 has an awesome cm kernel I would highly recommend, or even imoseyon always has a solid stable cm kernel as well.
How are you transferring the firmware? The heavy cable with the heavy plug? If so, it might have damaged your device's USB port and is causing intermittent disconnections which are corrupting the data as it is transferred. Try a lightweight cable and make sure it is firmly seated, then don't let it move during the transfer.
If this solves it then maybe look into replacement due to faulty design.
Frank
It is happening on all roms, however the only custom roms I've tried are CM based. I'll take a look at these other kernels and see if that resolves. Thanks for the help and idea's so far guys.
I've been having the same issues. Hellish reboots though. 10+ a day... Keep me posted. Thanks
Sent from my SM-N900T using XDA Premium 4 mobile app
So I have a CM 10.2 on my T989 Hercules for a while, and since couple of days every time I pickup the call or try to call back I can't hear jack sh*t unless I reboot the phone. Is this something that can be fixed or should I be looking for a new ROM ? There is so many of them I'm getting confused :silly:
i have this issue as well, but i am using pa 4.6 beta 1. any fix to this?
same problem here on mine and my girlfriends phones (Hercules) on either CM10.2 or PA 4.6 beta. restarting didn't help for the CM but did on the PA rom. only thing is, I don't know whats causing it. my phone could ring and when I answer I hear nothing and they don't hear me and vice versa when I call out. yes, both were clean installs on both phones with double wipes before flash with either roms.
Same Issue!
I am actually getting the same exact issue, at times I cannot hear anything on either end and the only remedy is to reboot and it only fixes it for a little bit.
Anyone know anything about this?
I've no issue with PA 4.5 Beta 1 (most stable in my case) nor 4.4 Final. Ran into the same issue with 4.5 Beta 4 once tonight but I was playing with disabling google play services and install the new Hangout.
I am curious too...anybody have a working solution yet?
I feel I've run into this problem before on jb. I'm curious to know which BASEBAND in installed on your devices.
I think there is a newer radio (modem) needed for jellybean and odd sound/wifi/data issues arise if you're using an older radio.
I'm using UVMC6 on CM11.
http://direct.xda-developers.com/wiki/Samsung_Galaxy_S_II/SGH-T989/Radios
I just flashed CM11 ROM from Sultanxda on my 2 T989's I have. One is having this issue the other is not. They were purchased at the same time. Not sure why this is happening. I have also had this issue on the previous CM10.2 version.
I have updated the Radio on the one that didn't work, but alas it still does not fix it. If the phone is rebooted, it magically works for a while.
I'm hoping that @Sultanxda will have a look at this issue.