Since it seems to be a general problem throughout many Moto devices, has anyone gotten to find a way to fix the volume settings without having to use a custom ROM or to set it with an app? The first volume step is way too high, comments on Moto forum suggest that step is at 36% of maximum volume. I had that problem already on the first Z Play and other comments suggest it's a problem on the G series too at least.
The only ways to fix it seems to be switching to a custom ROM (I would miss Moto display very much, there is just no replacement out there, so I might consider it when we finally have a Pie ROM in here) or using a volume changer app, but that's cumbersome and seems to be only working when setting it to 9%, which sounds like there is still no step between 9 and 36%.
Related
I've been having problems with my Nexus 7 (2013) for about a week now.
The problem consist of it not rotating between portrait and landscape mode, even though "auto-rotate" is enabled. This happens regardless of the application opened. However opening an application that forces the orientation will change it without issues, exiting the application then results in that setting being the new setting.
For instance, opening Google Play Books forces my tablet into portrait mode, then opening Chrome keeps this setting and I am unable to change it by rotating my device, then opening a video or similar in MX Player forces it into landscape and this setting will be kept until it is again forced into another orientation by some other app.
The weird part is that rebooting the device will result in the functionality being restored for random amounts of time. It is probably not random as there must be something that causes it, however I have been unable to determine the cause of it.
Is there anyway to see what "calls" are being made to change the rotation, or what is preventing these from executing?
Device information:
ROM: Nexus FLO KOTH49H Stock
Rooted: Yes
Kernel: 3.4.0-Bulletproof-2.1+ by flar2
Xposed modules:
BubbleUPnP
GravityBox [KK] [2.9.9]
XHaloFloatingWindows [2.22 Beta]
XPrivacy [2.0.2]
Have the same problem. It comed and goes away for a while. And then again rotation not working (a few hours max in my case). Found several Google Discussion Group topics 4-6 months ago and it seems to happen a lot /sometimes on all Nexus devices. Even some Google developpers responded there. Facory resets or reflashing stock rom did not help. Most likely a firmware-problem otherwise rotation would never work
Untill firmware solution comes, I now use Rotation Control Pro for the time being. That is only few times a month. This app has free version too with less options (and maybe ads which are blocked on my device). Ultimate Rotation Contol is nicer app but it has only time trial and can not be switched off within app unlike Rotation Control Pro/Free.
You can look for other rotation control app. Then choose one still being updated. Most rotation apps haven' been updated for year(s) And the app must have option 'force' rotation to work when Android's own rotation control freezed.
Verstuurd vanaf mijn Nexus 7 (2013) met Tapatalk
juliatan said:
Have the same problem. It comed and goes away for a while. And then again rotation not working (a few hours max in my case). Found several Google Discussion Group topics 4-6 months ago and it seems to happen a lot /sometimes on all Nexus devices. Even some Google developpers responded there. Facory resets or reflashing stock rom did not help. Most likely a firmware-problem otherwise rotation would never work
Untill firmware solution comes, I now use Rotation Control Pro for the time being. That is only few times a month. This app has free version too with less options (and maybe ads which are blocked on my device). Ultimate Rotation Contol is nicer app but it has only time trial and can not be switched off within app unlike Rotation Control Pro/Free.
You can look for other rotation control app. Then choose one still being updated. Most rotation apps haven' been updated for year(s) And the app must have option 'force' rotation to work when Android's own rotation control freezed.
Verstuurd vanaf mijn Nexus 7 (2013) met Tapatalk
Click to expand...
Click to collapse
I've looked around a bit and I probably stumbled upon the same thread you did. However I have yet to find a solution for it. I'm also curious to know if anyone else has been experiencing this problem, as that would suggest a real firmware/hardware problem.
You also mentioned that you only have this issue occasionally, like once or twice a month? I can hardly go a few hours after reboot until the issue occurs.
There are ways around it of course, but I am suspecting that my device might be defective on a hardware basis. In addition my left speaker has been starting to crackle a bit at certain frequencies... I might have to RMA this one.
Grorbabrag said:
I've looked around a bit and I probably stumbled upon the same thread you did. However I have yet to find a solution for it. I'm also curious to know if anyone else has been experiencing this problem, as that would suggest a real firmware/hardware problem.
You also mentioned that you only have this issue occasionally, like once or twice a month? I can hardly go a few hours after reboot until the issue occurs.
There are ways around it of course, but I am suspecting that my device might be defective on a hardware basis. In addition my left speaker has been starting to crackle a bit at certain frequencies... I might have to RMA this one.
Click to expand...
Click to collapse
I don't think a hardware error rotatating otherwise never rotation. But not 100% shure. And if speaker cracks certainly a good reason to RMA if you can not find solution for that.
I am planning to RMA my Nexus just before warranty expires. Little screen bleed next to volume buttons. Hopefully (but probably not) receive a brand new one after been using it for almost a year...
But 1st buy new bigger phone or extra tablet/convertable. Since this tablet can't live without. Using laptop these days often feels like punnishment.
Verstuurd vanaf mijn Nexus 7 (2013) met Tapatalk
Here's a thought. I would start with disabling XPosed Framework, and reboot. If that doesn't solve anything, then backup your rom (if you like), and perform a clean wipe, and also a clean flash. That way, anything installed to /system is removed as well. Install Chrome, and check the auto rotation. One by one, install other apps that might be the problem, and reboot in between them. While this will be time consuming, you need to know if your gyroscope went bad or not.
Side note: A factory reset (data wipe) through TWRP does NOT remove any apps/mods installed to the /system partition.
After the upgrade to 6.0.0 Marshmallow the wired-headphone output volume is limited at around 40% of the max according to the volume slider. The speaker-volume is not affected. I can't find a preference anywhere to change this behaviour. My old father used to enjoy watching videos and listening to music on his tablet, but the volume that can be achieved with his set of closed headphones is now so weak it is almost useless. One of the applications he relies on is one related to his cable-TV subscription that refuse to work on a rooted device. If it wasn't for this I would have rooted the device and/or installed some other OS long time ago. Is there a solution to this problem that does not require rooting or installation of some alternative OS-image?
Edit: Seems like i jumped the gun. The OTA update to 6.0.1 that got installed a couple days ago seems to have done the trick. The tablet now gives a warning as it did in the past, but does no longer impose an absolute limit to the headphone-volume like it did with 6.0.0 installed.
Don't think so, sorry. Easiest way I can think of to do this would be to flash Ex Kernel and change headphones gain, but that requires root as well.
You could try to hide root from the application that checks for it - there are some xposed modules that can work sometimes.
Hello xda,
I've rooted my M9 the other day, I'm currently running stock Sense [5.1, I believe the latest update] with Xposed. One of the many things I did with it was changing the amount of volume steps (when you've got a phone this loud, 15 steps is a joke imo). I did so through GravityBox as XVolume 30 I've used on my Nexus 4 doesn't seem to work here.
The thing works perfectly when I use the phone, however in Dotview things start to break.
As any dotview case user knows, upon changing the volume with physical buttons an icon of a speaker is shown alongside with a blue volume bar. However the said bar apparently has been programmed by HTC to show no more than 15 steps and changing the volume to any more than that just literally freezes the dotview interface to a point where the only thing you can do with the phone is restarting it via Power+Vol Up (everything under dotview works but there is no way of accessing it).
I've searched through XDA and found nothing on the topic, but I can't believe this is something very uncommon. Maybe I'm just searching it wrong . Has anybody found a fix for this? I've decompiled the HtcDotMatrix.apk out of curiosity (the code is not obfuscated) but I'm not a java dev so I didn't understand much and even if I did, I wouldn't really be able to do anything.
Thanks in advance for the replies
Ever since I got my Oppo Find X2 Pro, it's never remembered my ringtone/notification settings. Whether I choose an inbuilt option or do the 'Select From Files' thing, within minutes it's always reverted to Calm as the ringtone and Emerge as the notification sound.
Despite having just received the new Android 11 OTA update (CPH2025CPW_11_C_57), this problem still persists.
I reported it to Oppo many months ago, so am dismayed that it's not yet been resolved.
Are other users experiencing the same issue? Am I missing something simple? It might sound trivial, but it's not. Apps that allow me to select their notification sound work fine, but I'm missing calls and notifications because Calm and Emerge just blend into the background in noisy environments.
Help please!
John N G said:
Ever since I got my Oppo Find X2 Pro, it's never remembered my ringtone/notification settings. Whether I choose an inbuilt option or do the 'Select From Files' thing, within minutes it's always reverted to Calm as the ringtone and Emerge as the notification sound.
Despite having just received the new Android 11 OTA update (CPH2025CPW_11_C_57), this problem still persists.
I reported it to Oppo many months ago, so am dismayed that it's not yet been resolved.
Are other users experiencing the same issue? Am I missing something simple? It might sound trivial, but it's not. Apps that allow me to select their notification sound work fine, but I'm missing calls and notifications because Calm and Emerge just blend into the background in noisy environments.
Help please!
Click to expand...
Click to collapse
Hi, I've had the same issues. Only factory reset helped me. Since that all good.
Even I myself have no problem there are not all the functions presented I have resumed but Ulla I called Oppo answer that in Europe they are not yet present perhaps it is not convenient to spend so Even I myself have no problem there are not all the functions presented I have resumed but Ulla I called Oppo answer that in Europe they are not yet present perhaps it is not convenient to spend so much money For an incomplete device
hunhool said:
Hi, I've had the same issues. Only factory reset helped me. Since that all good.
Click to expand...
Click to collapse
Thank you - I was trying to avoid that because, however well I backup as much as possible, do screenshots of all my home pages etc., it still seems to take several days to get everything set up properly again. Thank goodness for password managers!
Anyway, I bit the bullet, did a factory reset and now everything is working as it should.
same problem from indeed if you notice even after the update the phone and even lowered on the ringing sounds and also on the hands-free call I reported everything but you see that Oppo does not have the to correct immediately this is why in the future I will not take any Oppo more they are very far from Samsung, Huawei, and Xioni I believe that Oppo will have a bad end in the European market
Hi all,
Hoping someone brighter than me can figure this sound issue out.
THE PROBLEM:
Half of my sounds don't work, rendering my phone useless in the current state. As the title says, Ring, Notification, & Alarm sounds do not work. You know, as in the important stuff that makes your phone, a phone? And makes you wake up in the morning? None of these respective sliders under Sound & Vibration settings make any noise when making adjustments. By contrast, my Media and Call volume sliders DO make noise when adjusting. And sure enough, once on a phone call, I hear things just fine (Call). And YouTube, Spotify, et al. (Media) also work just fine.
Because some sounds work but others don't, this has to be a software issue, right? This would be easy if it was hardware and 0% of sounds worked, but nope, it's partial.
BACKGROUND:
This pixel 3 xl is relatively new to me, but has ran A10 and A11 with a few different ROMs with 100% of sound working flawlessly. But out of nowhere, sounds suddenly stopped working correctly as described above. And it didn't occur immediately or shortly after a new rom flash or update or anything like that. Just stopped working, months into a well-running ROM.
I've tried a couple different ROMs now to fix the issue from a completely clean install (/format data + flash latest google factory image as 1st step) but none have fixed the issue. Specifically, pixeldust (A11) and evolutionX (A11) were my latest troubleshooting attempts with no avail. Pixeldust was the ROM that was formerly working and then after months of 100% sounds working, suddenly stopped.
It's odd that searching throughout the ROM threads that no one else seems to be having this issue. Again, this would be easy if it was a hardware failure. But that doesn't explain how it works for Youtube/Spotify but not for other things, so it has to be software.... I think?
I figured I'd start a thread here rather than start posting in each and every ROM I've tried to troubleshoot this. Thank you!
This might not be relevant because I'm using stock Android on a Pixel 4a but my notifications have gone silent and this report was the only similar search result I found. I tried changing the notification tone and none of them played a short snippet so I'm wondering if the problem is there.
I have not found a solution for this issue.
One thing I noticed recently is that when I'm on a call using the regular "earpiece" or whatever it's called (which works fine), if I switch to speaker phone, I can't hear anything. I have to switch back to the non-speaker ear mode and I can hear the call again.
xdateddybear said:
This might not be relevant because I'm using stock Android on a Pixel 4a but my notifications have gone silent and this report was the only similar search result I found. I tried changing the notification tone and none of them played a short snippet so I'm wondering if the problem is there.
Click to expand...
Click to collapse
ManImCool said:
I have not found a solution for this issue.
One thing I noticed recently is that when I'm on a call using the regular "earpiece" or whatever it's called (which works fine), if I switch to speaker phone, I can't hear anything. I have to switch back to the non-speaker ear mode and I can hear the call again.
Click to expand...
Click to collapse
I think I may have finally found the solution!! Sometimes it's the simple things in life that work, rather than reflashing a billion different ways that finally gets things working again.
In this case, I simply cleared the cache and storage for the 'Sounds' apps under Settings -> Apps & notifications -> See all apps -> Click 3 dots in upper right corner -> Show system. Then, I deleted cache and storage for TWO apps, both called 'Sounds' with 2 different icons. I'm not sure which is the system app and which is not nor do I know if clearing only one of them was necessary, but this is what has worked for me and has survived several restarts thus far. Good luck!