I updated my phone (moto g xt1033) to lollipop yesterday. I got 5.0.2. Working fine till today, no apps installed but now the volume keys have stopped changing volume. I mean they work, like I can use it to take screenshot, but they aren't changing the volume. Yesterday it was fine. The only thing I did was to charge the phone to 100%. After that, this happened. I don't know what to do as I can't listen to songs, though I've downloaded a volume control widget. And yeah, I rebooted and all but no change
Very strange issue. If it is still there, try a factory data reset. Before jumping to that backup all of your data. :thumbup:
Sent from my XT1033 using XDA Free mobile app
same issue here
i have karbonn sparkle v. now I have android 6.0.1 os. still doesn't work volume buttons, but can capture screen shots
Related
2 roms 2 diferent problems... LG P920
When I use the last CM7 mod i have the following problem.
- the ring (media) volume is very low, on max it is still very low. Tried every thing cannot get it loud enough to hear properly
- when tried some buttons/options the volume does get louder but after a while the sound is suddenly low again.....
(using the original rom i had no problems)
The phone is btw a completely default CM7 installation, there no apps installed!
When I try to upgrade to CM10 (nightly) the phone crashes.
It installs without any problem (after swipe cache etc) but as soon as CM10 is started and the home screen is shown the phone goes after a 1 or 2 minutes completely dead. Looks like the power/batt is pulled out when it goes dead....
No buttons works, screen is black (phone does not get hot when left on)
I cannot get it to switch on again by using the power button, only when i remove batt and place it back it starts normal again.
Booted again normally within 2 min the same problem etc etc....
Here also, a completely default CM10 installation.
I tried all availabe CM10 (nightly) builds, all have the same problem, when using CM7 i have no problems of this kind.
Does anyone reqonize these problems and knows a fix so it works with good sound in CM7 or stable in CM10?
Anyone having the same issue and have found a solution?
Phone suddenly stuck at some instances even with non-extensive usage.
Yesterday I was only using Facebook app. When messenger bubble pop up, my phone suddenly spiked. Moved once and then it got stuck already. You'll notice that it's not Facebook app only that's not functioning since nav. buttons are also stuck. You can't go press home and clear recent apps/hibernate apps. Power and volume buttons are also not functional.
So I assume the main system crashed. I only did a long press on power button to restart.
I installed Franco kernel r73, and thought that issue would only occur with stock kernel.
However, it occurred again today, I was viewing photos in Stock Photos app. I haven't started viewing the first 10 images yet, so memory should not be consuming that much. I turned on the auto rotate to view the image larger. When I turned the phone landscape, it reacted like it's about to rotate. And suddenly it got stuck. This time, power button is functional. It turns the screen on and off but it still turns to the same stuck screen, not the lock screen.
I've been experiencing this since 5.0.1. and almost everyday since I updated to 5.1.
I'm not sure if this is a hardware issue on my unit since mine is already about 1 year and a half old. I don't want to buy another phone yet!
Or is this a common issue nowadays due to Lollipop upgrade. If so, then could you provide temporary fix before they update this on 5.1.1.
Thanks a lot!
I had something similar . When I put forward the curtain hangs notice and then everything worked fine
Meh
I've seen this behavior on my Nexus 5 only on 5.1, and I'm pretty sure, it was introduced with that specific lollibug version. It's really annoying, that you have to reboot the phone every two or three days to avoid the freezes.
There's already in issue for that, it has got the ID 161032.
Hi guys,
Last night i was listening to music in my t2 ultra and i locked it. But when i tried to unlock it the display didnt work and the music kept playing. I thought the ram was used up a lot and it hung. But when i waited and tried nothing happened. While holding the screen the touch was working and other things were functioning normally. Today morning the display worked and i locked it and again tried to unlock it but the same problem occured again . The display works with only long intervals.
Please help me out.
I just noticed this recently. Whenever I set the brightness level to "15" via the touch control gesture, the brightness lowers instead of increase. Moving it upwards from 1 to 14 seems fine then the brightness drops at 15, I believe it's the same brightness level you set on the phone's notification drawer.
Anyone with similar issues?
~~
Moto X (2015) Pure Edition
Android 6.0 Marshmallow
I'm having similar issues since I upgraded my LG G3 to 6.0. With the difference that even on levels 1 to 14 the player uses the phone's auto brightness.
Same goes btw for QuickPic with settings to view pics at maximum brightness.
All this does not happen on my Nexus 7 running pure 6.01...
Sent from my LG-D855 using Tapatalk 2
So I'm guessing this really is a bug for flat 6.0 owners. It's either wait for my 6.0.1 to arrive or just hope a quick fix to MX would come
thanks for the reply!
@valXypher & @itenos
I have tested on Moto E2 with 6.0 (Official Private Test build).
But, I can't reproduce the issue. Seems that device specific issue. Not android version specific.
Sent from my SM-G900H using Tapatalk
After long time testing I finally found the culprit. In my specific case it was an app that didn't allow MX player and even Quick Pic to automatically raise the brightness to max.
The name of the app is CPU temp.
I've been using it already long time but never noticed this behavior because the app always got killed by android memory management soon after that I used it.
Since being on marshmallow the app did not get killed automatically anymore instead.
I did a test on a complete different phone running kitkat and it behaved the same.
As your symptoms are different from mine it might be a different app that causes your problems. Only way to find out is to factory reset, install one app at a time and after each install check MX player again. Took me 2 full days to do this job...
Sent from my LG-D855 using Tapatalk
Thanks! Right now I don't have the time to actually do a factory reset since I use my phone as my daily driver and I can't afford to reinstall some apps. If I manage to do so then I'l reply back again.
UPDATE:
I had the time to do a factory reset earlier so I finally tested MX Player without any other apps installed aside from the pre-loaded ones. Unfortunately the issue still persists. I guess this is indeed a device specific issue.
Hi,
My configuration is:
Android Version: 6.0.1 (MMB29V)
Kernel Version: 3.4.0-gbaedb01
NO ROOT - Stock ROM
Problems:
1) Microphone: when I make calls, my voice seems a little electronic and not clear to the other end
AFAIK this problem is there from the beginning (lollipop or JB I don't remember)
2) I cannot use speakerphone because there is a lot of noise (seems I'm in the middle of an hurricane)
AFAIK this problem is there from the beginning (lollipop or JB I don't remember)
3) Sometimes when pressing the on/off button (while locked), it vibrate and the camera app appears.
From this moment the front camera is unavailable and I have to restart the phone to get it working again.
This problem appared after upgrading to Andorid 6.0
I searched the internet and found only some suggestion to disable OK Google (for the mic problem).
I tried it, (also tried to disable google now), the situation is a little better, but my voice is still disturbed.
Hope you can help me...
Rooting and installing a custom rom could possibly resolve the situation?
Thank in advance...
Was the phone new when you purchased it? Has it always had these problems? Was the phone dropped or bumped?
These problems are not normal based on my experience with the N5.
The phone was refurbished from google (I received it jan-15) and these problems were there from the beginning, except for the on/off button (which came in after the marshmellow upgrade)...
Sounds like a hardware problem that cannot be fixed via software.
The third problem is probably cause of the shortcut to open the camera (pressing Power button twice to open the camera).
Although it is weird that it freezes your phone, perhaps you could turn the setting off by going into Settings > Display.