Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.
Taran3105 said:
Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.
Click to expand...
Click to collapse
Also the volume keys are not working.
no brothers both the capacitive buttons and volume rockers work flawlessly on 4.1.0
all is working for me :-/
Working fine for me.
Working fine for me. Seems like a temp issue or a wrong flash to me. You can try wiping system and flash full zip. If you are fully stock, i would advise to perform a factory reset.
Taran3105 said:
Hardware buttons not working after the 4.1.0 update .
Only Touch ID is working . Nothing else.
Click to expand...
Click to collapse
Sounds like a firmware issue. I suggest a full reflash.
I did a clean flash 4.0.3&4.1.0 OTA. Sometimes pulling down the notifications doesn't darken the background.
Clean flash ..stop making up bs posts
I cannot launch Google Assistant by voice with the screen off, whereas I could before the update
croques said:
I cannot launch Google Assistant by voice with the screen off, whereas I could before the update
Click to expand...
Click to collapse
As i have been saying repeatedly, the OTAs from OnePlus suck.
Clean flash the full ROM.
andrneumann said:
I did a clean flash 4.0.3&4.1.0 OTA. Sometimes pulling down the notifications doesn't darken the background.
Click to expand...
Click to collapse
Please PM me if you ever find a fix for this.. it forced me to use another ROM
Never call it Touch ID... This is not Apple.
works fine here clean flash
azaidi said:
Please PM me if you ever find a fix for this.. it forced me to use another ROM
Click to expand...
Click to collapse
Clean flashed again, now with OOS full zip 4.1.0, same thing. Pulling down notifications not always darken the rest of the screen. Still looking for a fix.
Factory reset solved the problem.
croques said:
I cannot launch Google Assistant by voice with the screen off, whereas I could before the update
Click to expand...
Click to collapse
I could never do that
andrneumann said:
Clean flashed again, now with OOS full zip 4.1.0, same thing. Pulling down notifications not always darken the rest of the screen. Still looking for a fix.
Click to expand...
Click to collapse
Did u find anything?
having the same issue
guess very few are having this issue (not many reported)
Anyone who's shortcut to for example a document on the home screen doesn't work anymore?
I already deleted the shortcut and made a new one, but still doesn't work
Ronak Chandak said:
Did u find anything?
having the same issue
guess very few are having this issue (not many reported)
Click to expand...
Click to collapse
I have the same issue...
Related
Hi,
I just got my Galaxy Nexus (European ver., 4.1.1) few days ago and it randomly crashes all the time, especially when using apps with calling function (eg. dialer, viber, walkie talkie app...etc). It works fine sometimes and it crash and reboot automatically sometimes....
I have tried to flash it to CM10 and CM9, but the problem is still there.
Does any body know what's the problem?
I have two nexus (one for my family), and they both have the same problem.....
sorry for n00bness, but how to do reset to factory settings with customs rom? i tried settings>> backup and restore>> factory restore, but it didn't work.
Thank you
secretiff said:
Hi,
I just got my Galaxy Nexus (European ver., 4.1.1) few days ago and it randomly crashes all the time, especially when using apps with calling function (eg. dialer, viber, walkie talkie app...etc). It works fine sometimes and it crash and reboot automatically sometimes....
I have tried to flash it to CM10 and CM9, but the problem is still there.
Does any body know what's the problem?
I have two nexus (one for my family), and they both have the same problem.....
sorry for n00bness, but how to do reset to factory settings with customs rom? i tried settings>> backup and restore>> factory restore, but it didn't work.
Thank you
Click to expand...
Click to collapse
Well, if you have a custom rom, you probably have a custom recovery such as TWRP or CWM (ClockWorkMod Recovery), reboot to recovery, and select wipe data/factory reset, yes, and you are done.
If you are having problems rebooting to recovery, just power off the phone, hold volume up + volume down + press power, press volume down until you see the word "Recovery" and then hit power.
Wiping from a custom recovery (ClockWorkMod or TWRP) will not wipe your internal SD (pictures,music) but it will wipe your apps/settings. Wiping from a stock recovery will wipe your pictures/music/everything in addition to your apps/settings.
EDIT: What I find funny is that your phone reboots and both of them. Flash stock google factory image and see if it reboots. If it does, probably its a faulty phone. It would be a great idea to lock the bootloader with stock rom and return the device.
akash3656 said:
Well, if you have a custom rom, you probably have a custom recovery such as TWRP or CWM (ClockWorkMod Recovery), reboot to recovery, and select wipe data/factory reset, yes, and you are done.
If you are having problems rebooting to recovery, just power off the phone, hold volume up + volume down + press power, press volume down until you see the word "Recovery" and then hit power.
Wiping from a custom recovery (ClockWorkMod or TWRP) will not wipe your internal SD (pictures,music) but it will wipe your apps/settings. Wiping from a stock recovery will wipe your pictures/music/everything in addition to your apps/settings.
EDIT: What I find funny is that your phone reboots and both of them. Flash stock google factory image and see if it reboots. If it does, probably its a faulty phone. It would be a great idea to lock the bootloader with stock rom and return the device.
Click to expand...
Click to collapse
yes, they both rebooted with google stock rom when i got them! so i thought maybe it was something do with comparability or bugs from the stock rom...so i flash them with CM10, not working. then i thought...maybe it's the jelly bean? so i flash CM9....and it still happens...
Thanks for your suggestion, reli appreciate that
secretiff said:
yes, they both rebooted with google stock rom when i got them! so i thought maybe it was something do with comparability or bugs from the stock rom...so i flash them with CM10, not working. then i thought...maybe it's the jelly bean? so i flash CM9....and it still happens...
Thanks for your suggestion, reli appreciate that
Click to expand...
Click to collapse
I've also heard, some phones don't like Jelly Bean. But you have issues with CM9 too, so its really weird. Only solution for them was to return the device. There are reports of people having difficulties with any Jelly Bean based ROM (even stock)
akash3656 said:
I've also heard, some phones don't like Jelly Bean. But you have issues with CM9 too, so its really weird. Only solution for them was to return the device. There are reports of people having difficulties with any Jelly Bean based ROM (even stock)
Click to expand...
Click to collapse
oh...really??? guess we are just the unlucky minors...everybody is so happy with their nexus
it really irritates me cause i like my nexus, but it just have its spontaneous psycho flicks
after rebooting, it doesn't work right away...if i use those calling apps right after it finishes reboot, it will reboot again :crying:
I have to wait for some moments for it to work.......
sure im gonna return it, and buy another one from other stores... *sighs*
secretiff said:
oh...really??? guess we are just the unlucky minors...everybody is so happy with their nexus
it really irritates me cause i like my nexus, but it just have its spontaneous psycho flicks
after rebooting, it doesn't work right away...if i use those calling apps right after it finishes reboot, it will reboot again :crying:
I have to wait for some moments for it to work.......
sure im gonna return it, and buy another one from other stores... *sighs*
Click to expand...
Click to collapse
Sorry to hear man. Looks like it is a faulty one. However, Viber if you don't know, doesn't work on Jelly Bean. If you don't mind waiting, maybe you should use a spare phone in the mean time and wait for the next Nexus. :good:
akash3656 said:
Sorry to hear man. Looks like it is a faulty one. However, Viber if you don't know, doesn't work on Jelly Bean. If you don't mind waiting, maybe you should use a spare phone in the mean time and wait for the next Nexus. :good:
Click to expand...
Click to collapse
I tried to go to my cwm recovery and chose wipe data/factory reset but it's still CM9...
I would like to flash back to the stock rom, unlockbootload and unroot it so i can return. is there any way to do that? there isn't many tutorials online....
(Im using mac.)
Thank You
secretiff said:
I tried to go to my cwm recovery and chose wipe data/factory reset but it's still CM9...
I would like to flash back to the stock rom, unlockbootload and unroot it so i can return. is there any way to do that? there isn't many tutorials online....
(Im using mac.)
Thank You
Click to expand...
Click to collapse
nvm, i have already done it with my frds pc!
Hi, there are thousands of people with the same problem, its not the rom(JB)... but the proximity sensor that crashes the kernel, during calls, make the phone freeze/reboot.Search in google groups issue 37485, there are no solution, google and samsumg, dont say a word...It happens in nexus s too.
I have the same problem
firestruck said:
Hi, there are thousands of people with the same problem, its not the rom(JB)... but the proximity sensor that crashes the kernel, during calls, make the phone freeze/reboot.Search in google groups issue 37485, there are no solution, google and samsumg, dont say a word...It happens in nexus s too.
Click to expand...
Click to collapse
What shall one do then? I have such behaviour as well i think where phone has difficulties to come back from deep sleep.
I had this problem too
Random crashes which got worse, my phone would crash every 15 minutes.
I took the battery out and put it back and it didn't want to boot anymore.
Had to send it back to Samsung -> broken motherboard which got replaced
firestruck said:
Hi, there are thousands of people with the same problem, its not the rom(JB)... but the proximity sensor that crashes the kernel, during calls, make the phone freeze/reboot.Search in google groups issue 37485, there are no solution, google and samsumg, dont say a word...It happens in nexus s too.
Click to expand...
Click to collapse
OMG what the hell????? how come i never heard it before???
can't believe this is happening...how can they put the phone on the market without thoroughly testing it???
frandel said:
I had this problem too
Random crashes which got worse, my phone would crash every 15 minutes.
I took the battery out and put it back and it didn't want to boot anymore.
Had to send it back to Samsung -> broken motherboard which got replaced
Click to expand...
Click to collapse
is your phone new? or have been used for awhile??
firestruck said:
Hi, there are thousands of people with the same problem, its not the rom(JB)... but the proximity sensor that crashes the kernel, during calls, make the phone freeze/reboot.Search in google groups issue 37485, there are no solution, google and samsumg, dont say a word...It happens in nexus s too.
Click to expand...
Click to collapse
found a post discussing this issue on other forum:
http://code.google.com/p/android/issues/detail?id=38595
he temporarily solved the problem with using headphone when calling.
cuz the sensor is disabled when headset is plugged in
here are five conditions that proximity sensor disable during a phone call.
These conditions is default settings of Phone application in android.
You can find the source code in PhoneApp.java,
boolean screenOnImmediately = (isHeadsetPlugged()
|| PhoneUtils.isSpeakerOn(this)
|| ((mBtHandsfree != null) && mBtHandsfree.isAudioOn())
|| mIsHardKeyboardOpen
|| mOrientation == AccelerometerListener.ORIENTATION_HORIZONTAL);
(1) isHeadsetPlugged(): When user headset is plugged, proximity sensor will be disable
(2) isSpeakerOn: When user turn on the speaker, proximity sensor will be disable
(3) BT device is connected and audio path is On
(4) Hardware Keyboard is opened.
(5) DUT is at Horizional state.
Click to expand...
Click to collapse
Please read forum rules before posting
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
Google, has just moderated me, for complain about have a useless Phone, see?? They dont have a solution, and they dont want to pay for people who spent 400$, in a useless phone...So they shut up us...Really sad became google policy...
---------- Post added at 02:22 PM ---------- Previous post was at 02:17 PM ----------
Yep, with phones it works, but its a pain in the ass have all the time the headphones conected, even in your pocket...
secretiff said:
is your phone new? or have been used for awhile??
Click to expand...
Click to collapse
I have it since it came out in December last year
frandel said:
I had this problem too
Random crashes which got worse, my phone would crash every 15 minutes.
I took the battery out and put it back and it didn't want to boot anymore.
Had to send it back to Samsung -> broken motherboard which got replaced
Click to expand...
Click to collapse
I have such problem with my Nexus S, I heard it was something wrong with bootloader for JB that Google released, which have caused countless Nexus S to be bricked.
I have tried everything even some hardware level modification provided by XDA member to save it but with no success so only solution is motherboard replacement...
Hope same thing won't happen to Galaxy Nexus... because if it does, I will try to buy 4th generations of Nexus series and I will be killed by someone because it would be very expensive and I just brought GNex 2 months ago...
Sent from my Galaxy Nexus using xda premium
frandel said:
I have it since it came out in December last year
Click to expand...
Click to collapse
so...it crashes randomly while it was new :cyclops: ?
This has been happening for a week or so now and I can't seem to work out why! It seems random that when I open the messaging app it just crashes, then sometimes that seems to cause a chain reaction and everything starts crashing meaning I have to reset it with the power button. The problem tends to persist unless I power down, wait and turn the phone back on. I didn't have the problem on the rom for a long time (Jellybean 4.1.2 for Endeavoru AOSP Build [JZO54K]) it just seemingly started happening at random. I tried a new rom with a new boot.img (aokp_endeavoru-ICJ-V3.4) which seemed to hold the problem off for a few hours but now its started on that one! I've also ruled out any apps because I made sure I didn't restore anything from my gmail account.
Any ideas?
[★] said:
This has been happening for a week or so now and I can't seem to work out why! It seems random that when I open the messaging app it just crashes, then sometimes that seems to cause a chain reaction and everything starts crashing meaning I have to reset it with the power button. The problem tends to persist unless I power down, wait and turn the phone back on. I didn't have the problem on the rom for a long time (Jellybean 4.1.2 for Endeavoru AOSP Build [JZO54K]) it just seemingly started happening at random. I tried a new rom with a new boot.img (aokp_endeavoru-ICJ-V3.4) which seemed to hold the problem off for a few hours but now its started on that one! I've also ruled out any apps because I made sure I didn't restore anything from my gmail account.
Any ideas?
Click to expand...
Click to collapse
hi mate, i had this issue with phonebook, try flashing a different gapps zip
Cheers for the quick reply man,
I thought it might be gapps; i've tried 20120726 and 20121011 but still had the same problem. Which one are you on?
[★] said:
Cheers for the quick reply man,
I thought it might be gapps; i've tried 20120726 and 20121011 but still had the same problem. Which one are you on?
Click to expand...
Click to collapse
no worries,
im back on ARHD now but i was using inverted gapps, pretty sure it was this one -
http://forum.xda-developers.com/showthread.php?t=1911887
ARHD?
And cheers buddy, this is the one which worked for you? or gave you trouble? Also can I just install this from CWM over my existing rom+gapps or do I need a clean wipe?
[★] said:
ARHD?
And cheers buddy, this is the one which worked for you? or gave you trouble? Also can I just install this from CWM over my existing rom+gapps or do I need a clean wipe?
Click to expand...
Click to collapse
yeah android revolution - not the jelly bean version though... i always end up back on this rom.
yeah just flash that and erase cache & dalvik and you should be good to go
cleancorekiller said:
yeah android revolution - not the jelly bean version though... i always end up back on this rom.
yeah just flash that and erase cache & dalvik and you should be good to go
Click to expand...
Click to collapse
Fair enough broo, i'll check it out.
Thanks! I'll let you know the outcome once i've flashed it and tested for a bit
[★] said:
Fair enough broo, i'll check it out.
Thanks! I'll let you know the outcome once i've flashed it and tested for a bit
Click to expand...
Click to collapse
no problem
cleancorekiller said:
no problem
Click to expand...
Click to collapse
Good so far, although my phone app is no longer installed :S
[★] said:
Good so far, although my phone app is no longer installed :S
Click to expand...
Click to collapse
hmm thats weird, its in the package... could try re flashing, if that doesnt work then im really not sure.....nothing like that has ever happened to me before.
cleancorekiller said:
hmm thats weird, its in the package... could try re flashing, if that doesnt work then im really not sure.....nothing like that has ever happened to me before.
Click to expand...
Click to collapse
Apps are still crashing and the phone didnt appear with a reinstall i'm just gonna go to a new rom I think, maybe that Android revolution one
Hello,
I have a fairly new samsung S3 on AT&T. The phone is rooted and the new jellybean update applied.
Everything has been fine until this morning it started showing "UNFORTUNATELY, NFC SERVICE HAS STOPPED".
I can hit OK and it goes away but within 5 seconds it's back. It is making my phone unusable.
I went into titanium backup and froze all NFC services - that didn't help anything.
Any ideas?
Thanks!
1naylor said:
Hello,
I have a fairly new samsung S3 on AT&T. The phone is rooted and the new jellybean update applied.
Everything has been fine until this morning it started showing "UNFORTUNATELY, NFC SERVICE HAS STOPPED".
I can hit OK and it goes away but within 5 seconds it's back. It is making my phone unusable.
I went into titanium backup and froze all NFC services - that didn't help anything.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Did you have the NFC google wallet fix install before updating or installed it after?
crystalstylez said:
Did you have the NFC google wallet fix install before updating or installed it after?
Click to expand...
Click to collapse
I haven't done any google wallet fix. Is that my problem?
1naylor said:
I haven't done any google wallet fix. Is that my problem?
Click to expand...
Click to collapse
No, Did you try factory reset/wipe to see if that fixes it?
crystalstylez said:
No, Did you try factory reset/wipe to see if that fixes it?
Click to expand...
Click to collapse
Not just yet - I'm reflashing the jellybean rom at the moment to see if it works after that.
Same thing after rom flash. Argh!
1naylor said:
Same thing after rom flash. Argh!
Click to expand...
Click to collapse
that fine that you reflash but go in to 3e Recovery by holding down Power+Vol Up+Home until you see the blue writing in the top left corner of the screen. Then let go. From there Factory Reset/ Wipe Device (Warning this will wipe data/pictures). Then Reboot.
1naylor said:
Same thing after rom flash. Argh!
Click to expand...
Click to collapse
I can't see NFC in my network settings to even try to turn it off. That and Sbeam are gone.
crystalstylez said:
that fine that you reflash but go in to 3e Recovery by holding down Power+Vol Up+Home until you see the blue writing in the top left corner of the screen. Then let go. From there Factory Reset/ Wipe Device (Warning this will wipe data/pictures). Then Reboot.
Click to expand...
Click to collapse
About to do a TI backup ... otherwise once I wipe it will take me forever to get this phone set up again.
Then I will wipe the phone. Ack. Thanks for the suggestion.
1naylor said:
About to do a TI backup ... otherwise once I wipe it will take me forever to get this phone set up again.
Then I will wipe the phone. Ack. Thanks for the suggestion.
Click to expand...
Click to collapse
Whenever you have issues like this. It is best to Wipe. Not really any way around that. I am willing to bet this will resolve all issues.
crystalstylez said:
Whenever you have issues like this. It is best to Wipe. Not really any way around that. I am willing to bet this will resolve all issues.
Click to expand...
Click to collapse
Well you were definitely right - thanks for the help!
Ti Backup couldn't back up with the error popping up like crazy - so I wiped the device, re-rooted, and now I'm restoring from an older Ti Backup.
Hopefully it won't take me too much longer to get all set up.
Thanks again for the help!
try this
http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367
indianx said:
try this
http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367
Click to expand...
Click to collapse
Fantastic! Now I don't have to wipe.
crystalstylez said:
Whenever you have issues like this. It is best to Wipe. Not really any way around that. I am willing to bet this will resolve all issues.
Click to expand...
Click to collapse
I'm having the same issue, but wipe does not work, I am unable to turn the phone on really, it just gets to Welcome screen, where you choose your language, followed by Unfortunately, S Note has stopped, I press ok, then Unfortunately, NFC as stopped, and it does a few others and then repeats, over and over.
How can I fix?
samaraki said:
I'm having the same issue, but wipe does not work, I am unable to turn the phone on really, it just gets to Welcome screen, where you choose your language, followed by Unfortunately, S Note has stopped, I press ok, then Unfortunately, NFC as stopped, and it does a few others and then repeats, over and over.
How can I fix?
Click to expand...
Click to collapse
And how are you wiping. What are your steps?
Same here
Problem fixed just delete the Nfc and tag.apk from the room then install it
mercerudy said:
Fantastic! Now I don't have to wipe.
Click to expand...
Click to collapse
samaraki said:
I'm having the same issue, but wipe does not work, I am unable to turn the phone on really, it just gets to Welcome screen, where you choose your language, followed by Unfortunately, S Note has stopped, I press ok, then Unfortunately, NFC as stopped, and it does a few others and then repeats, over and over.
How can I fix?
Click to expand...
Click to collapse
indianx said:
try this
http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367
Click to expand...
Click to collapse
Thanks very much, we work too.
mercerudy said:
Fantastic! Now I don't have to wipe.
Click to expand...
Click to collapse
How were you able to by pass the "Unfortunately, nfs has stopped working" pop up? I'm guessing you need to download the zip file they provide at this link onto your phone, no?
my phone says nfc service has stopped and if i click on ok it comes back so i have no idea
any ideas i will thank you
zenon.brian said:
my phone says nfc service has stopped and if i click on ok it comes back so i have no idea
any ideas i will thank you
Click to expand...
Click to collapse
Well, I never had this happen, so try this:
1: BACKUP, BACKUP, BACKUP. Nobody wants to lose data.
2: Grab the CyanogenMod you want (I recommend the latest, based on Nougat, catching cats is another reason)
3. Grab Odin, I have a copy BUT my computer is out of commission (Using my Pi 3 )
4. GET A RELIABLE USB CABLE. Any issues can make you own a Samsung brickwich.
5. Flash CM using Odin, and also flash TWRP for good luck.
Done, and hope it works.
Guys, do not take OTA update April (375 MB), it has issue with the lock screen.
You will not able to go to homescreen once you put the phone locked (or screen off) , you need to forced reboot the phone to be able to go to homescreen.
I'm downgrading to earlier version
SOLVED, update the firmware (July Security update) and then Go HERE
I can the update and no problem for me. All works ok
mythras73 said:
I can the update and no problem for me. All works ok
Click to expand...
Click to collapse
something wrong with my phone? I flashed earlier firmware then took the ota update still got the same issue.
I can update and all iits o.k.
my lock screen issue
Had the issue on the lock screen too. Just had to go into custom features to turn off peek display and turn back on for it to work properly
Blade^ said:
Had the issue on the lock screen too. Just had to go into custom features to turn off peek display and turn back on for it to work properly
Click to expand...
Click to collapse
nice info.. I will try it
Blade^ said:
Had the issue on the lock screen too. Just had to go into custom features to turn off peek display and turn back on for it to work properly
Click to expand...
Click to collapse
just try it, and keeps doing the same issue.
Hi! I also have a lock screen issue, and now I can only downgrade
Blade^ said:
鎖屏也有這個問題。只需進入自定義功能即可關閉窺視顯示並重新打開以使其正常工作
Click to expand...
Click to collapse
這個方法沒用
zlebors said:
nice info.. I will try it
Click to expand...
Click to collapse
This method is useless
Blade^ said:
Had the issue on the lock screen too. Just had to go into custom features to turn off peek display and turn back on for it to work properly
Click to expand...
Click to collapse
I just flashed a XT2201-6 firmware to avoid the OTA updates from XT2201-2 firmware.
build number S1SF32.22-16-14-19, everything looks good.. still retcn btw.
zlebors said:
I just flashed a XT2201-6 firmware to avoid the OTA updates from XT2201-2 firmware.
build number S1SF32.22-16-14-19, everything looks good.. still retcn btw.
Click to expand...
Click to collapse
NFC use or not
Download the XT2201-6 firmware there
zlebors said:
I just flashed a XT2201-6 firmware to avoid the OTA updates from XT2201-2 firmware.
build number S1SF32.22-16-14-19, everything looks good.. still retcn btw.
Click to expand...
Click to collapse
KenHuang2022 said:
NFC use or not
Click to expand...
Click to collapse
NFC Working
KenHuang2022 said:
This method is useless
Click to expand...
Click to collapse
Weird it worked for me. But I also tried changing the peek display from weather display to just battery. Can try that too.
Had the same issue 1st reboot after update, had to reboot via long press power. But since then seems to be working ok.
BTW, it looks like "Google Play System Update" disappeared from Security menu, now i see only stock security update here.
A long press on the power button doesn't respond to any mechanism. You can only reboot by volume and power on mechanism.
Maybe the baseband is broken, because I have flashed dozens of times
zlebors said:
I just flashed a XT2201-6 firmware to avoid the OTA updates from XT2201-2 firmware.
build number S1SF32.22-16-14-19, everything looks good.. still retcn btw.
Click to expand...
Click to collapse
where do you download the firmware S1SF32.22-16-14-19?
Hello, i have a a5y17lte (samsung galaxy a5 2017) phone running custom rom. When i turn up the volume on anything(notifications, media or even alarm) its extremely loud. why does this happen please if anyone knows, help. it is driving me crazy. i have had this issue for far too long.
Install Volume Manager and see if each slider works separately.
ze7zez said:
Install Volume Manager and see if each slider works separately
ze7zez said:
Install Volume Manager and see if each slider works separately.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
THANK YOU A LOT BROOO
i flashed other roms on my sm a520f phone and when i flashed magisk the volume got messed up again. i factory reset it and it is still very loud and messed up. i tried everything from volume manager to trying to find a video on youtube. nothing is working. if anyone knows how to fix this please respond to this tread. i am loosing my mind. I also tried with other roms (without magisk) and that didnt help.
Before installing the custom ROM, format the data partition.
ze7zez said:
Before installing the custom ROM, format the data partition.
Click to expand...
Click to collapse
I do that before i install any rom. I tried it and it didnt work, volume was still insanely loud
If you go back to the stock ROM and the problem remains, it could indicate a hardware failure.
ze7zez said:
If you go back to the stock ROM and the problem remains, it could indicate a hardware failure.
Click to expand...
Click to collapse
ok
use [vol-down + power] to force reboot!