Related
Hi,
I have a big problem with my HTC Touch Diamond. The volume of the external speaker, the one in witch you can here the ring tone or if you play a audio file in media player, is extremely low , you can barely hear it if you put the phone near your ear.
This symptom appear after I've install the MEMO 2.5.2.1-FULL ROM.
yesterday I was reading on this site an I found a thread about sound volume problem and there were a suggestion to try to replace AudioPara3.csv, I've did that and for a couple of minutes everything was back to normal but after I've perform a soft restart the sound was very low again. I've try to overwrite again the file but with no result.
I've reinstall the official ROM from the HTC support site but the situation persist.
No I'm out of ideas and I hope that you can give me a hint.
Thanks,
Sorin
hey sorin
there are two things here:
1. this is not rom dev related
2. the problems started apparently with the MEMO rom installation
so you should have
a. checked MEMO rom thread for similar issues/available solutions in the first place
b. asked there otherwise instead of opening a new thread
as the problem persists even after going back to stock I will just move the thread to general, next time you have rom specific issues pls post in the respective rom thread
thx and gl
Mod. edit: not dev related, moved to general
So I've not been a member here for very long but I've been following the nexus one, nexus s, and now the galaxy note forums since their inauguration. Up until now I've not had an issue with rooting, installing and tweaking roms etc. I've not made a post yet because I've felt it unnecessary to add to all the b.s. in these forums and if I have an issue I'll search and find an answer or figure it out myself.
I've run into a problem with Stunner 1.4.26 ..
yes. yes. yes. I have gone through the ringer - full wipe, properly done etc. etc.
On a fresh install I cannot access the internal sdcard. The rom does not see it.. I can't post the bug and whats happening in the dev forum as I haven't made enough posts yet, so now I'm getting started.
Hopefully someone else is experiencing this as I type and I'll be able to sort it out soon.
If I can figure out what is going on rest assured I won't keep it to myself. You'll be the first to know. Oh and I wont just say, 'Hey I fixed it!' I'll actually tell you how I did and what the problem was and why I think my fix is valid..
.damn forums.
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
LibertyMarine said:
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?
Click to expand...
Click to collapse
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
anibjoshi said:
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
Click to expand...
Click to collapse
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!
anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
Try flashing a Sense ROM, like ARHD or MaximusHD?
Enviado de meu HTC One usando Tapatalk
LibertyMarine said:
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!
Click to expand...
Click to collapse
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.
well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?
IINexusII said:
well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?
Click to expand...
Click to collapse
No I rooted the device but did not install any root apps...i unrooted the device to install the GPE Rom(not necessary i know, but it seemed like a proper way) and found that it started giving problems immediately. Can non-root regular apps also cause such problems? I had installed only a limited number of apps anyway, updated the pre installed apps, facebook, twitter, whatsapp, some games..thats it..nothing wierd..
Might be a Screen-Off max. frequency issue. Like the phone gets only 500Mhz in sleep mode at maximum. Which is to low for an incoming call. Could you install a app like Android Tuner or Trickster Mod to check your Screen-Off Max frequency. If it`s that low, set it to ~1000Mhz.
anibjoshi said:
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.
Click to expand...
Click to collapse
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One
LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again
Yup try installing kernel and custom rom.
Remove the case and try ( i know this is stupid thing but can give it a try)
Jvov said:
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One
Click to expand...
Click to collapse
Thanks for your help buddy! I really appreciate it!
anibjoshi said:
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again
Click to expand...
Click to collapse
Thanks ! That's awesome and gives so much motivation! If you find out that you have a hardware defect and that you have to send it to HTC, I'll give you some information how to deal with those guys that you get your warranty.
I am running the lite Marshmallow ROM from this thread:
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
I think it is pretty much a stock ROM, so I don't think my problem is specific to that ROM.
I use a Bluetooth headset to listen to podcasts. It works perfectly in my car and most of the time works fine in my house. But as soon as I step out of the car or out of the house, it breaks up terribly. Sound will break up to the point where it is not listenable. Sound will go away for many seconds, come back, break up some more. The bluetooth is unusable outdoors for media. But if I make a phone call it works fine. The problem is the same whether I use my Plantronics Explorer 50 or my Kinovo BTH220, so I don't think the problem is in the headset.
Anyone have any ideas on what is happening and how to solve the problem?
It's not a stock rom.
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.
Without getting a logcat there is nothing anyone can do except guess what the issues is.
donnyutx said:
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.
Click to expand...
Click to collapse
Thanks. It has been happening for a while, I think I've clean flashed the ROM and it still happens, but last update I dirty flashed. I'll try a clean flash and/or the stock ROM next time I get a bit of time to do it.
zelendel said:
Without getting a logcat there is nothing anyone can do except guess what the issues is.
Click to expand...
Click to collapse
I was hoping someone who had the same problem might chime in. What should I look for in the logcat?
johninor said:
Thanks. It has been happening for a while, I think I've clean flashed the ROM and it still happens, but last update I dirty flashed. I'll try a clean flash and/or the stock ROM next time I get a bit of time to do it.
Click to expand...
Click to collapse
I just clean flashed the latest version of the Lite ROM and it did not fix my problem.
donnyutx said:
I looked it over, and my intuition says either reflash this rom - or flash a new rom. Many of these roms are "adjusted" here and there by well meaning folks, and yes I've flashed some roms that were really messed up.
I look at the bottom line and here is a rom that is definitely not stock with some alterations that probably are good, so maybe a reflash will get it right. 10 years of software troubleshooting here on my part. Roms do not always flash right the first time.
I have personally had this happen. It's probably a great rom, give a reflash a try.
Click to expand...
Click to collapse
I tried a clean flash of the Lite ROM. That didn't solve the problem. I then flashed the latest factory image (MOB30W). I did not restore anything or install any apps except Google Play Music and Podcast Addict, which I am using to reproduce the problem. I still have the same problem. Bluetooth media audio is working indoors, but as soon as I step outside it breaks up and goes out completely for 20 or more seconds at a time.
I think that rules out the Lite ROM as the problem. Anyone have any ideas for me?
I googled looking for bluetooth audio breakup issues and I found a few things that were suggested to fix it. They were turning off the WiFi and and turning off GPS. I tried both and they did not help my problem. I didn't expect them to because they were fixes for people reporting general bluetooth breakup on specific devices, while I am seeing the breakup on Media Audio, but not Phone Audio.
If anyone knows of a better place to ask my question, please let me know. I've been searching and can't find an answer or a better place to ask the question.
After some research here may be a fix...
johninor said:
I am running the lite Marshmallow ROM from this thread:
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
I think it is pretty much a stock ROM, so I don't think my problem is specific to that ROM.
I use a Bluetooth headset to listen to podcasts. It works perfectly in my car and most of the time works fine in my house. But as soon as I step out of the car or out of the house, it breaks up terribly. Sound will break up to the point where it is not listenable. Sound will go away for many seconds, come back, break up some more. The bluetooth is unusable outdoors for media. But if I make a phone call it works fine. The problem is the same whether I use my Plantronics Explorer 50 or my Kinovo BTH220, so I don't think the problem is in the headset.
Anyone have any ideas on what is happening and how to solve the problem?
Click to expand...
Click to collapse
I believe this may help. When I flash a phone, I like to use Nexus Root Toolkit, as there are different areas of the phone that can be flashed manually. When I recommended to flash your phone, the "Nexus toolkit by wugfresh" was what I use to flash with. You'll see what it can do. This is a quote from reddit: "Not long after I got my 6P I started having some severe audio problems while streaming over bluetooth. I connect to my car's stereo via bluetooth and stream GPM every time I drive, and the audio would sort of stutter and skip, sometimes 5 times within a few seconds. It was insufferable for me, as there are few things I find more irritating than skipping audio.
***If you are having similar issues, going into recovery and wiping the cache partition completely eliminated the skipping/stuttering problems for me. Obviously, I don't know the nature of any issues you may have, so YMMV, but this saved my sanity.*** I was coming close to trying to RMA it, thinking it was a hardware problem as every attempt I had at finding a software solution had failed.
This gave me sweet relief, I hope it does the same for someone else!" *** Look at the second link for the Nexus toolkit, You'll see that there are 7 - 8 different flashable areas: Boot, Bootloader, Radio/Baseband, Recovery, System, Userdata, Cache, & Vendor. *** (Make sure to get the latest wugfresh nexus toolkit 2.16)***
https://www.reddit.com/r/Nexus6P/comments/42j4r6/psa_if_you_are_having_issues_with_prevalent/
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
donnyutx said:
I believe this may help. When I flash a phone, I like to use Nexus Root Toolkit, as there are different areas of the phone that can be flashed manually. When I recommended to flash your phone, the "Nexus toolkit by wugfresh" was what I use to flash with. You'll see what it can do. This is a quote from reddit: "Not long after I got my 6P I started having some severe audio problems while streaming over bluetooth. I connect to my car's stereo via bluetooth and stream GPM every time I drive, and the audio would sort of stutter and skip, sometimes 5 times within a few seconds. It was insufferable for me, as there are few things I find more irritating than skipping audio.
***If you are having similar issues, going into recovery and wiping the cache partition completely eliminated the skipping/stuttering problems for me. Obviously, I don't know the nature of any issues you may have, so YMMV, but this saved my sanity.*** I was coming close to trying to RMA it, thinking it was a hardware problem as every attempt I had at finding a software solution had failed.
This gave me sweet relief, I hope it does the same for someone else!" *** Look at the second link for the Nexus toolkit, You'll see that there are 7 - 8 different flashable areas: Boot, Bootloader, Radio/Baseband, Recovery, System, Userdata, Cache, & Vendor. *** (Make sure to get the latest wugfresh nexus toolkit 2.16)***
https://www.reddit.com/r/Nexus6P/comments/42j4r6/psa_if_you_are_having_issues_with_prevalent/
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
Thank you. I hadn't found that thread when I searched. I tried the several suggestions in that thread. One was clearing caches, which, of course, I had already done as a result of testing clean installs of the ROM I use and the latest stock ROM. So that didn't solve the problem. The other suggestion was turning off bluetooth scanning in location settings. I hadn't even known that was a thing. I tried turning off bluetooth scanning and wifi scanning this morning and used my phone all day as usual. It didn't solve my problem - no change at all. I had in an earlier test turned off the GPS and that hadn't helped either.
The second link, I believe is just a different way of installing ROMS and managing related stuff. I don't think that tool is going to do anything that I didn't do by installing the latest stock ROM with the flashall.bat script.
Looking for help on this one. Every 3-5 days my Ultra gets into a state where no voice can be heard by either myself or the person on the other phone when a call is made or received, but I can hear the ring tone if I'm calling prior to the person answering, and my phone rings as normal if someone calls me. But when answering the call it's just silence on both sides. A reboot fixes this only for it to happen again 3-5 days later, requiring another reboot.
At first I assumed it was a corruption of the rom I had installed, so I flashed back to my stock image with Odin, including a fresh VOD CSC install. Unfortunately, it's still happening after this. Speaking as an engineer, it's unusual but not unheard of for a device to have a hardware issue of this type and it be rectified each and every time with a reboot, that would normally point to a software/firmware error of some sort. However, the fact it's continuing to happen after a completely fresh re-flash of stock Android suggests my worst fears that it is hardware. I could try some things, like not installing Magisk or even re-locking my bootloader, but I don't believe either would be a factor. I only used Magisk for rooting and don't install additional modules. I've also ruled out the sim card or sim slots by swapping to an e-sim, only for it to still happen.
Anyway, any suggestions would be welcome, especially if you have suffered something similar. There is an easy fix, which is to schedule a reboot every morning at around 3am, but I'd sooner not have to do this before working out what the underlying cause is.
I don't have a solution for you but I just wanted to share that I am having the same issue. But I'm not using Magisk and not unlocked, or rooted. The only thing I did was flash stock Samsung and disable some bloat.
I was having the issue the other night (for the second time) when calling my carrier (AT&T) about an order. I just assumed it was them at first. I disabled wifi calling (after them not hearing me several times) then tried again and it worked.
Were you using wifi calling at the time? I haven't been able to reproduce the issue yet so I don't know if disabling wifi calling had anything to do with it working.
Just to clarify, you say you're using Magisk but you're not unlocked or rooted? That isn't possible, but perhaps you just worded it wrong and you meant you're not using Magisk.
Funny you should mention Wifi-Calling, when it happened a few weeks back I force closed Wifi calling in an attempt to track down any potential services that might be causing the problem. And when I did that the calling started working again without a reboot. I thought I'd tracked it down and thought I'd test it again once it happened again a few days later, I would then freeze wifi-calling (something I never use) which would hopefully stop it ever re-occurring. However, the second time I force stopped wifi-calling it didn't fix the issue.
Beefheart said:
Just to clarify, you say you're using Magisk but you're not unlocked or rooted? That isn't possible, but perhaps you just worded it wrong and you meant you're not using Magisk.
Funny you should mention Wifi-Calling, when it happened a few weeks back I force closed Wifi calling in an attempt to track down any potential services that might be causing the problem. And when I did that the calling started working again without a reboot. I thought I'd tracked it down and thought I'd test it again once it happened again a few days later, I would then freeze wifi-calling (something I never use) which would hopefully stop it ever re-occurring. However, the second time I force stopped wifi-calling it didn't fix the issue.
Click to expand...
Click to collapse
I missed a word when I first replied. I added "not" to Magisk but you must have seen it before I fixed it.
I've had many work meetings (on phone) since then and haven't had it pop up. I haven't changed anything and even have wifi calling back on, so I'm at a loss.
OK, traced this to possibly be linked to the attached logcat. Any suggestions?
Also, contrary to my claim in the opening post, the dial tone can only be heard sometimes.
An additional oddity, whilst the fault is occurring (prior to a reboot), voice calls on WhatsApp work fine.
Perhaps a form of modem fault?
I give up on this. I flashed the stock VOD rom in Odin and relocked the bootloader to take it as close to stock as possible (minus the knox flag being tripped which is unavoidable at this point) and it still showed the issue after a couple of days. I've also disabled Bluetooth at a service level to no avail as I thought it might be a glitch with that.
It's clearly a hardware issue that will only be resolved with a logic board replacement. Which currently aren't available.
One good thing is that a full reboot isn't required to fix it, a soft reboot seems to do it. So I've got a link to do that on my home page, only takes 10-15 seconds.
Beefheart said:
OK, traced this to possibly be linked to the attached logcat. Any suggestions?
Also, contrary to my claim in the opening post, the dial tone can only be heard sometimes.
Click to expand...
Click to collapse
Hi, sorry to re-open this old topic. My S21 has the same problem from the beginning, but I have the stock rom. Did you get this log using *#9900# tool? Which log level did you use? Which file is the attached one? BTW, I'm almost sure that it's an hardware failure, did you solve it? Thanks
nrg84 said:
Hi, sorry to re-open this old topic. My S21 has the same problem from the beginning, but I have the stock rom. Did you get this log using *#9900# tool? Which log level did you use? Which file is the attached one? BTW, I'm almost sure that it's an hardware failure, did you solve it? Thanks
Click to expand...
Click to collapse
I'm afraid not, I ended up selling it as parts or repair a few weeks after that post.
Beefheart said:
I'm afraid not, I ended up selling it as parts or repair a few weeks after that post.
Click to expand...
Click to collapse
Thanks anyway, I will try to bring mine to the repair center.