Root [T-Mobile] [possibly considering rooting] phone switches to silent when receiving a call

[lhuge]

I'm guessing this might be a general problem and not specific to HTC One, but if I really should be posting this on the HTC forum let me know.

My T-Mobile HTC One (Android 4.1.2, Sense 5.0, bootloader 1.44) is having serious ring problems. It will usually (maybe always) switch itself from audio to silent mode when I receive a call, and remain in silent mode afterward. If it is in Silent mode already, it will sometimes ring anyway, but will not switch back to Non-silent mode.

I've removed all apps that seem like they might be messing with ring volume, but obviously I might be missing something. I have rebooted the phone. I don't seem to have a "Quiet Time" setting under settings (but that wouldn't explain the behavior).

There are a handful of posts I've seen describing similar problems, but not the same pattern. I've seen several suggestions about apps that might help with similar problems people have posted, but I really would like to figure out what is going wrong before I do that.

It is my intention to S-OFF, root & update the phone very soon. If someone with more knowledge than me (ie 90% of the people reading this) can tell me that this is very likely a SW problem that will go away when I update/root, I'll take your word for it and embark on the rooting process.


Thanks for any assistance you can provide...

 

[Thom]

You could try running in Safe Mode (disabling all apps you added without uninstalling them) and if the problem stopped it is caused by an app that you added.

... Thom

 

[marctronixx]

adding a custom rom will set the device up to your needs, plus it opens up other opportunities to tailor the device to what you want beyond just notification settings.

this is the forum to discuss rooting and there are a few methods to use to install them. there is a diverse rom section on this site that may be of help to you.

just to help on some other things:

if you have a cover on your phone or a screen protector, these could be interfering with the proximity sensor on the device. remove these and test.

as mentioned above, could be a rogue app. i ASSume this issue had not been happening since day one of you owning the device, so remove apps one by one that can interfere with the led settings, notification settings, any 3rd party dial apps.

factory reset will nearly guarantee the problem will go away, but if its an app, you may reinstall it back to the device, then chasing your tail.

 

[scotty85]

I would definately go ahead and s off,then allow the phone to update to current software/firmware. You're on a pretty old build,wich was definately not without bugs.

 

[lhuge]

You could try running in Safe Mode (disabling all apps you added without uninstalling them) and if the problem stopped it is caused by an app that you added.

... Thom

if you have a cover on your phone or a screen protector, these could be interfering with the proximity sensor on the device. remove these and test.

as mentioned above, could be a rogue app. i ASSume this issue had not been happening since day one of you owning the device, so remove apps one by one that can interfere with the led settings, notification settings, any 3rd party dial apps.

factory reset will nearly guarantee the problem will go away, but if its an app, you may reinstall it back to the device, then chasing your tail.

Thanks both of you for the replies.

I just now sat down to try Safe Mode, but now my phone is not exhibiting the behavior - lol.

I tried removing the cover yesterday with no change (though it is a measure of my ignorance that I have no idea how that could make a difference - I'll have to go and educate myself on this proximity sensor you refer to).

I think at this point I'll just do the S-OFF & root & update process and hope the problem goes away.

Can anyone confirm that, because I have bootloader/uboot 1.44 I cannot use rumrunner to do the S-OFF and should use revone or moonshine to do that? I asked on XDA, but don't have a reply yet, so I thought I would ask here while I'm on a roll (and this place is a little less intimidating for lowly noobs). I'll go out and try to find the answer myself now, but I'm still happy to get confirmation/guidance...

thanks again
lh

 

[scotty85]

Thanks both of you for the replies.

I just now sat down to try Safe Mode, but now my phone is not exhibiting the behavior - lol.

I tried removing the cover yesterday with no change (though it is a measure of my ignorance that I have no idea how that could make a difference - I'll have to go and educate myself on this proximity sensor you refer to).

I think at this point I'll just do the S-OFF & root & update process and hope the problem goes away.

Can anyone confirm that, because I have bootloader/uboot 1.44 I cannot use rumrunner to do the S-OFF and should use revone or moonshine to do that? I asked on XDA, but don't have a reply yet, so I thought I would ask here while I'm on a roll (and this place is a little less intimidating for lowly noobs). I'll go out and try to find the answer myself now, but I'm still happy to get confirmation/guidance...

thanks again
lh

There is a "universal" rumrunner tool that prolly will work if you unlock the bootloader and Install a custom rom with an insecure kernel.

Having said that,there's no real reason to use rumrunner over moonshine or revone. Bootloader needs to be unlocked no matter wich method you use. I personally used revone,but I like doing things in a command window. Moonshine is prolly a slightly more user friendly tool.

 

[lhuge]

There is a "universal" rumrunner tool that prolly will work if you unlock the bootloader and Install a custom rom with an insecure kernel.

Having said that,there's no real reason to use rumrunner over moonshine or revone. Bootloader needs to be unlocked no matter wich method you use. I personally used revone,but I like doing things in a command window. Moonshine is prolly a slightly more user friendly tool.

Thanks Scotty, and everyone ... I believe I now have a rooted, unlocked, S-OFF phone! But not without a *lot* of struggle ... When I can write it up I'm going to put a new post up, since my issues/questions now have nothing to do with the ring/silence problem in the title (hopefully gone). But I have a specific followup question to Scotty that I'll fire off here:

I would definately go ahead and s off,then allow the phone to update to current software/firmware. You're on a pretty old build, which was definitely not without bugs.

OK, that is what I'd like to do next, but I just want to double-check that it's safe to do an OTA update to 4.3 without messing up all the work I just put into getting root/S-OFF. Specifically I am now on:

Android 4.1.2
Sense 5.0
HBoot 1.4.4
SW# 1.27.531.8 (downgraded from .531.11)
HTC SDK API level 5.12

So ... if I go ahead and OTA update, I won't inadvertently update anything that needs to avoid updating? (I used the "temporary" recovery method, to preserve OTA update possibility).

Thanks!

 

[scotty85]

Thanks Scotty, and everyone ... I believe I now have a rooted, unlocked, S-OFF phone! But not without a *lot* of struggle ... When I can write it up I'm going to put a new post up, since my issues/questions now have nothing to do with the ring/silence problem in the title (hopefully gone). But I have a specific followup question to Scotty that I'll fire off here:




OK, that is what I'd like to do next, but I just want to double-check that it's safe to do an OTA update to 4.3 without messing up all the work I just put into getting root/S-OFF. Specifically I am now on:

Android 4.1.2
Sense 5.0
HBoot 1.4.4
SW# 1.27.531.8 (downgraded from .531.11)
HTC SDK API level 5.12

So ... if I go ahead and OTA update, I won't inadvertently update anything that needs to avoid updating? (I used the "temporary" recovery method, to preserve OTA update possibility).

Thanks!

As long as you've got the stock recovery and havent removed any bloat,your fine to ota.

Your s off will remain

 

[lhuge]

As long as you've got the stock recovery and havent removed any bloat,your fine to ota.

Your s off will remain

OK that was frighteningly fast ...

I used openrecovery-twrp-2.6.3.3-m7.img from techerrata.com - I'm assuming that counts as Stock. I'm not aware of removing any bloat, but then I wasn't even aware of that possibility so hopefully I didn't clean anything out by accident.

Thanks once again...

 

[scotty85]

OK that was frighteningly fast ...

I used openrecovery-twrp-2.6.3.3-m7.img from techerrata.com - I'm assuming that counts as Stock. I'm not aware of removing any bloat, but then I wasn't even aware of that possibility so hopefully I didn't clean anything out by accident.

Thanks once again...

twrp is a custom recovery,and not able to install HTCs OTA packages. i think i answered your questions in the other thread,just holler if youve any others