Sudden Shutdown - Moto G4 Plus Questions & Answers

Hey, about 2 week ago i tried update my phone to Android 8.0 ROM but i happen to crash (i messed up somewhere), then i go downgrade it Android 7.0 and reflash. It worked fine until it suddenly start to shutdown randomly, sometimes when i was calling, opening youtube, etc and it was so irritating. I thought it was ROM Issue, so i try to flash other ROM but it keeps randomly shutdown. Tried to unroot and use stock but nothing change. The issue still happening. I will try to upload the logcat when it happen again.
Here some basic info
Device : Moto G4 Plus
ROM :
It first happen on RR 7.1.2 After failing to upgrade to 8.0.
AEX
LOS
AOKP
Stock
Kernel : Stock
G.App : open_gapps-arm-7.1-pico-20171119
Flash : Clean
And heres some info before failing to upgrade
ROM : RR 7.1.2
Kernel : ElementalX
Underclocked
No Xposed

its probably your battery faulty try unpluging and repluging the battery connector i was having the same issue and i did the same and now everthing is good.
all the best

I am facing same issues sudden shutdowns at the time of network going up down, or while on call, or playing music.
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
sohail_23 said:
its probably your battery faulty try unpluging and repluging the battery connector i was having the same issue and i did the same and now everthing is good.
all the best
Click to expand...
Click to collapse
Battery connector? Sorry, i didnt get you.

saurabh8263 said:
I am facing same issues sudden shutdowns at the time of network going up down, or while on call, or playing music.
---------- Post added at 10:47 AM ---------- Previous post was at 10:46 AM ----------
Battery connector? Sorry, i didnt get you.
Click to expand...
Click to collapse
You need to open your device just go to the local phone repair shop and ask him to open the device then remove the battery and press the power button for 10 seconds while the battery is removed, then re insert the battery and you are good to go!

Change the battery it will be fixed

I did this a couple months ago and it worked perfectly

Problem Battery too
My moto g4 plus is turning itself off after the battery reaches 50%, when playing, turns off after reaching 50% when watching videos on youtube, turns off from 30%. Could it be ROM problem? I opened the cell phone, and I removed the battery and put it back, I saw many videos on the internet explaining several things about how I could solve it, I did it all and unfortunately I did not succeed. I'm using the original Moto G4 plus ROM ... What could be the problem ROM? If I change the Rom, will I succeed, and solve the problem?

Same random shutdowns after battery change
I have the same issue (random shutdowns when receiving calls, watching videos, etc) since I changed to a new battery in my G4 Plus XT1644 (old one was draining fast but never failed).
I have tried with STOCK ROM, LineageOS, Kernel Adiutor tweaks, nothing seems to work. Please help!!!
Should I buy another battery?

Stock Nougat 7.0 saved a phone from the bin
For the last few months I've been hopping from the Nougat and Oreo versions of Lineage and Omnirom and getting no joy. First I noticed that after turbo charge my phone would drain on idle from 100% to 80% in literally a few minutes. So, I stopped using the turbo charger and that seemed to remedy it. Then, the phone would reboot itself once it got below 60%. As I said, all of this was on both Nougat and Oreo versions of Lineage and Omnirom.
A few days ago I was ready to bin the entire phone out of rage. I hated the sight of it and didn't want to chance changing the battery in case something else with the phone was to blame. For whatever reason, I came across https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367 and since being on stock Nougat have not had a single problem regarding the battery. I can not believe it. Turbo charging works fine now and I am getting just over a day's use out of my phone.
One happy Moto G4 Plus user again

Related

Camera stops working leads to long Awakes = Steep Battery Drains :(

Hello Droid Geeks & Devs, a sincere advice/help needed .. just fed up off two major issues with my N4. Already tried many of the things available on forums but still the problem persists since 3 months now. So it's time I share my saga and possibly get the suggestions/fix or atleast a workaround.
OK, I'll start from the beginning.. I was and still am fully stock on Kitkat 4.4.4 and bootloader locked. I guess it was September during which i
updated my Google camera app from play store. And since this small update my N4 is ruined, my camera stopped working after a few hours ..only solution was to do a reboot & it would work fine for few hours and again "can't connect to camera". I thought a update might fix it but it didn't ..just forgot i had a camera in my phone for few months.
But guess what since October,the camera not working cycle was as it is, but the added problem was sudden infinite awake times in battery stats showing the cause of drastic battery drains (40% drain in nights to wakeup to drained dead phone in morning).again the temp fix was a reboot. But when i closely looked at the trends, I found the relation that while my camera is working the wake-locks are just fine, but the moment the cam stops working the continuous long Awake starts till it eats up all the battery and eventually lead to a reboot to be back to normal.Screenshots attached.
The upcoming Android 5.0 update in Nov was a major hope for me, that this should fix the bug.I happily sideloaded the lollipop update but still no luck ..in fact i have got added lollipop bug of WiFi drops for no reason.Also trying my luck with the new 5.0.1 lets see how it turns out.
Please help me with this issue. Thanks in advance.
Still no luck with 5.0.1
Please Anyone can suggest something ??
Sent from my Nexus 4 using Tapatalk

Everything is running in slow motion on my S4

I've had this issue for months now and I've started countless threads in countless forums attempting to solve it:
my S4 (GT-I9505 jflte) is basically running in "slow motion". What I mean by that is that no matter what I do, about 50% of the time all animations will play back at about half the speed they normally would and any kind of input will be registered with a delay of about half a second. Animations still look smooth at about 60fps and the phone doesn't crash, it's just... slow. Really slow.
I used to think this had to be an issue with Cyanogenmod (was running the Optimized CM12.1 rom from AntaresOne & Alucard), but after trying several different builds and clean flashing countless times, nothing changed. Now I just flashed an entirely different ROM (Resurrection Remix) and although it ran buttery-smooth for the first hour or so, after restoring all my apps it has now started doing the same thing.
The fact that the problem persists even with a completely different ROM leads me to believe it must be something to do with the apps I have installed. But how do I troubleshoot this? I have way too much stuff on my phone to go through deinstalling every single app and making sure it wasn't causing the problem.
I have no idea how to approach this problem. Any help would be greatly appreciated.
EDIT:
I'm not sure if this has been happening before with CM12 or if it just started happening now with Resurrection Remix, but I just noticed that it seems to happen mostly when the device is charging. When I unplug it, 9 times out of 10 the slowness will instantly go away... is that an indication of anything?
EDIT 2
I think I just solved the issue. After discovering that the problem appeared to be caused by the charging, I tried a different charger. My original Samsung charger started having horrible coil whine a few months ago, so I threw it out and started using a generic one I had laying around. Come to think of it now, that must have been when the problem started.
I just found another charger for a Samsung phone and plugged my phone in: everything fine. Switched back to the generic charger: everything slow. So it must have been the charger. Just out of curiosity, is this a known issue? Could some kind of electrical noise from the charger be interfering with the touch screen? Seems almost bizarre that a simple charger would cause a phone to run slow...

device randomly switches off XT1643

i have the moto g4 plus 3/32 gig model, its around 1.5 months old running the soak test nougat, it recently started giving me a weird problem, it will randomly shutdown while in use, heating doesnt seem to be the issue, can anyone tell me what the issue might be.
P.S. i live in germany and this phone was bought in india so i am not so sure if the warranty will be valid
go back to stock mm or install cm14
I am on stock mm and even i do experience these random shutdowns many a time. But i noticed that when this happens the rear part near the camera becomes very hot. Also a low pitch bursting sound can also be heared just before the shutdown.
Also to mention recently i did a factory reset and i have not experienced this problem yet after that.

Battery going up and down + reboot

Hi,
My wife's gti9505's has an issue with the battery that I cannot seem to fix. One second it's at 75% then all of a sudden it's a 5%, then it goes to 50% and some times it reboots. I don't know if this might be related but she mostly feels this happens when she uses the uber app. She has the latest official android version (5.1..), I've tried installing a new rom with 6.0 but the problem persisted. I've bought her a new battery but the problem persisted. At this point I'm thinking that this MUST be a hardware problem. Any other solutions I may try?
The reboot problem might be a power button issue.

Nexus 6 speaker issue POSSIBLE fix

I had retired my Nexus 6 a while ago due to the speaker issue that's been plaguing these devices. I decided not to sell it as it would be an issue for the next user, so I instead kept it in case of an emergency.
Certain issues have lead me to recommission the device, so I decided I'd see what's new. So far it is clear that there was never a fix, and some people swear that pressing on the speakers fixes the problem (whether temporarily or permanently). I never believed this as the only thing that seemed to fix it (temporarily) when touching the speakers is tapping on the speakers, but that seems to be related to the device rotating (which has also been known to let the volume go back up) and something within the gyroscope (something that some have brought up as well). My Nexus 6 unlike many others has the bigger problem where the volume will go down regardless of battery percentage, and it was terrible as there was never an instance in which I could truly use the speakers.
Reading around I have seen other "solutions" emerge, but never anything concrete. On a YouTube video's comment sections I saw one person mention that Franco.Kernel fixes this, for me this did nothing. On another forum I read a guy who said his issue stopped using Lean Kernel, and that it may have something to do with mp_decision. Unfortunately for me, I like to stick to the latest version that was officially released (in this case 7.1.1) and Lean Kernel doesn't seem to have made it that far. I gave up on experimenting for the sake of the speakers at this point and settled on my favorite rom which is Dirty Unicorns, using the final 7.1.1 build (somebody was nice enough to provide links as I could not find it anywhere and their official page only has their Oreo based builds). Obviously the speaker issue persisted here. At this point I wanted to see if there was a Kernel with good features and battery life and came across a thread that mentioned BL4CKB1RD Kernel. I flashed that and was a happy camper as my phone runs cooler (no difference has been made to my 4 hour average screen on time) and ultimately lag free. Reading the maker of the kernel's current set up using the kernel, I decided to copy it a bit by limiting my maximum CPU frequency to 2.5GHz and using said governor profile. I came across the mp_decision setting and turned it on just out of curiosity (I have no clue what it does). Later on, I went to watch a YouTube video and before I could connect my headphones, the video was playing...with perfect sound. I thought I was going crazy, so I let it play for a bit longer. No volume drop. I picked up the phone, moved it around, rotated it, blasted the volume to the max and still not a single drop. For literally an hour I watched videos and absolutely no volume issues. I decided to undo all kernel changes and reboot to see what would happen. Still no volume changes. I also decided to lock the CPU and GPU maximum frequency to produce more heat, still nothing. I played Subway Surfers which was a guaranteed instant volume drop, nothing. Rebooted several times more, let the battery die, speakers are still perfect. Could this kernel have fixed my issue? Maybe. It is also worth noting that before flashing the kernel, I ran a command via terminal emulator (requires root) that I read about BEFORE flashing the custom kernel, and I never rebooted my Nexus 6. The command can be found here (there was another thread that also included it but also linked to this thread):
https://forum.xda-developers.com/nexus-6/devs-only/speaker-amplifiers-nxp-tfa9890-research-t3236518
Anyone with the speaker issue should perhaps start by this command, reboot and see what happens. If not, try using BL4CKB1RD kernel and see what happens? If still nothing, try toggling mp_decision on and then test.
Crossvxm said:
I had retired my Nexus 6 a while ago due to the speaker issue that's been plaguing these devices. I decided not to sell it as it would be an issue for the next user, so I instead kept it in case of an emergency.
Certain issues have lead me to recommission the device, so I decided I'd see what's new. So far it is clear that there was never a fix, and some people swear that pressing on the speakers fixes the problem (whether temporarily or permanently). I never believed this as the only thing that seemed to fix it (temporarily) when touching the speakers is tapping on the speakers, but that seems to be related to the device rotating (which has also been known to let the volume go back up) and something within the gyroscope (something that some have brought up as well). My Nexus 6 unlike many others has the bigger problem where the volume will go down regardless of battery percentage, and it was terrible as there was never an instance in which I could truly use the speakers.
Reading around I have seen other "solutions" emerge, but never anything concrete. On a YouTube video's comment sections I saw one person mention that Franco.Kernel fixes this, for me this did nothing. On another forum I read a guy who said his issue stopped using Lean Kernel, and that it may have something to do with mp_decision. Unfortunately for me, I like to stick to the latest version that was officially released (in this case 7.1.1) and Lean Kernel doesn't seem to have made it that far. I gave up on experimenting for the sake of the speakers at this point and settled on my favorite rom which is Dirty Unicorns, using the final 7.1.1 build (somebody was nice enough to provide links as I could not find it anywhere and their official page only has their Oreo based builds). Obviously the speaker issue persisted here. At this point I wanted to see if there was a Kernel with good features and battery life and came across a thread that mentioned BL4CKB1RD Kernel. I flashed that and was a happy camper as my phone runs cooler (no difference has been made to my 4 hour average screen on time) and ultimately lag free. Reading the maker of the kernel's current set up using the kernel, I decided to copy it a bit by limiting my maximum CPU frequency to 2.5GHz and using said governor profile. I came across the mp_decision setting and turned it on just out of curiosity (I have no clue what it does). Later on, I went to watch a YouTube video and before I could connect my headphones, the video was playing...with perfect sound. I thought I was going crazy, so I let it play for a bit longer. No volume drop. I picked up the phone, moved it around, rotated it, blasted the volume to the max and still not a single drop. For literally an hour I watched videos and absolutely no volume issues. I decided to undo all kernel changes and reboot to see what would happen. Still no volume changes. I also decided to lock the CPU and GPU maximum frequency to produce more heat, still nothing. I played Subway Surfers which was a guaranteed instant volume drop, nothing. Rebooted several times more, let the battery die, speakers are still perfect. Could this kernel have fixed my issue? Maybe. It is also worth noting that before flashing the kernel, I ran a command via terminal emulator (requires root) that I read about BEFORE flashing the custom kernel, and I never rebooted my Nexus 6. The command can be found here (there was another thread that also included it but also linked to this thread):
https://forum.xda-developers.com/nexus-6/devs-only/speaker-amplifiers-nxp-tfa9890-research-t3236518
Anyone with the speaker issue should perhaps start by this command, reboot and see what happens. If not, try using BL4CKB1RD kernel and see what happens? If still nothing, try toggling mp_decision on and then test.
Click to expand...
Click to collapse
I just ordered a nexus 6, is this issue common? Does it affect stock rom or custom roms? I have a Moto X Pure at the moment, Nexus 6's brother, it has a similar issue where the sound cuts out when the phone is switched from portrait to landscape and vice versa but only affects custom roms. Its doesnt lower the volume though
DerrickTight said:
I just ordered a nexus 6, is this issue common? Does it affect stock rom or custom roms? I have a Moto X Pure at the moment, Nexus 6's brother, it has a similar issue where the sound cuts out when the phone is switched from portrait to landscape and vice versa but only affects custom roms. Its doesnt lower the volume though
Click to expand...
Click to collapse
Yes it is common and does effect custom ROMs as well
DerrickTight said:
I just ordered a nexus 6, is this issue common? Does it affect stock rom or custom roms? I have a Moto X Pure at the moment, Nexus 6's brother, it has a similar issue where the sound cuts out when the phone is switched from portrait to landscape and vice versa but only affects custom roms. Its doesnt lower the volume though
Click to expand...
Click to collapse
For most the issue occurs at low battery, and the drop isn't major. I've seen some videos of people with this specific problem and I laugh because they don't know have it as bad as us with the major drops regardless of battery life. So pretty much the low battery volume issue is more common than the worse one, and you could say it is a common issue.
We had a white one that had absolutely no issues except a faster battery drain (perhaps because the speakers worked?!).
Crossvxm said:
For most the issue occurs at low battery, and the drop isn't major. I've seen some videos of people with this specific problem and I laugh because they don't know have it as bad as us with the major drops regardless of battery life. So pretty much the low battery volume issue is more common than the worse one, and you could say it is a common issue.
We had a white one that had absolutely no issues except a faster battery drain (perhaps because the speakers worked?!).
Click to expand...
Click to collapse
If you're using any of the oreo roms, try my kernel (popcorn kernel in the development section) and have a look at my post here
https://forum.xda-developers.com/showpost.php?p=76858120&postcount=29
athulele said:
If you're using any of the oreo roms, try my kernel (popcorn kernel in the development section) and have a look at my post here
https://forum.xda-developers.com/showpost.php?p=76858120&postcount=29
Click to expand...
Click to collapse
My Nexus 6 arrives tomorrow and I'll be flashing it right away. If I have a volume issue I'll definitely keep your kernel in mind. Thank you
athulele said:
If you're using any of the oreo roms, try my kernel (popcorn kernel in the development section) and have a look at my post here
https://forum.xda-developers.com/showpost.php?p=76858120&postcount=29
Click to expand...
Click to collapse
Dumb question does your kernel already have these included?
xconwayx said:
Dumb question does your kernel already have these included?
Click to expand...
Click to collapse
Yes.
For what it is worth, mp-decision is Qualcomm's own hotplug: it turns the processor cores on and off depending on need. I guess it may use other tricks as well, to optimize power / performance.
No obvious reason that it should affect the speakers, but you never know.
Does this thread address the issue with SEVERAL 8.1 ROMs I've used, in which the speaker phone does not function during calls... and during calls alone. I can play media just fine... IMMEDIATELY after the speaker not working on the calls. I CAN however plug a headset in and communicate normally . Just desperately seeking an answer or I guess I'll go back to 7.1.2
So now nexus 6 is running pie roms nearly perfect . Unfortunately this sound problem persists… it is truely fristrating
So is there any kernel that can fix it in pie roms? Thanks
I have been using my nexus 6 for a couple of years now and had the speaker issue about a year ago and went into recovery and wiped cashe and the. Did a factory reset. Did an OTA update and everything was fixed.
Last weekend I finally flashed TWRP and then rooted with Magisk. Went to install myself5's Bata version of Carbon room running pie... Not sure what happened but had error code 7 and bricked the phone. Had to wipe it out and went though Google to get an old OTA and reflashed and thankfully got my phone back. Tried the process 3 other times and got the same result. Each time no speaker issue.
The last time I tried it I left it alone and didn't even put TWRP on it but now the speaker problem comes and goes.
5 min agot I was playing YouTube music with no issues, made a phone call, then back to YouTube and now the bottom speaker quit and the top speaker is very quiet.
Any ideas on what could have cause my issues and can someone direct me to where Ii can find more information or what I'm doing wrong on on flashing new roms?
Currently running Android 7.1.1 build NGI77B
Suffeln said:
I have been using my nexus 6 for a couple of years now and had the speaker issue about a year ago and went into recovery and wiped cashe and the. Did a factory reset. Did an OTA update and everything was fixed.
Last weekend I finally flashed TWRP and then rooted with Magisk. Went to install myself5's Bata version of Carbon room running pie... Not sure what happened but had error code 7 and bricked the phone. Had to wipe it out and went though Google to get an old OTA and reflashed and thankfully got my phone back. Tried the process 3 other times and got the same result. Each time no speaker issue.
The last time I tried it I left it alone and didn't even put TWRP on it but now the speaker problem comes and goes.
5 min agot I was playing YouTube music with no issues, made a phone call, then back to YouTube and now the bottom speaker quit and the top speaker is very quiet.
Any ideas on what could have cause my issues and can someone direct me to where Ii can find more information or what I'm doing wrong on on flashing new roms?
Currently running Android 7.1.1 build NGI77B
Click to expand...
Click to collapse
I've honestly encountered this problem a couple times but rebooting/flashing fixed the problems. Worst case scenario go back latest Google ROM with WUG's software, then you can install TWRP, then a custom ROM like Nitrogen ROM.
Sent from my shamu using XDA Labs
I know nothing about what anyone is saying, but I would like to add that using Viper4Android, and using "eXtra loud" at "Moderate" with the max gain at 4x and the max output at 0db completely gets rid of the low volume problem. Viper works system wide so it fixes it for Netflix, etc
Hope this helps guys
athulele said:
If you're using any of the oreo roms, try my kernel (popcorn kernel in the development section) and have a look at my post here
https://forum.xda-developers.com/showpost.php?p=76858120&postcount=29
Click to expand...
Click to collapse
Sorry for the late reply, I had to put the Nexus 6 on hold due to another issue with it. I tried your kernel with the latest official version of Dirty Unicorns, but unfortunately it does not boot. It will boot fine without flashing the kernel.
mahir555 said:
So now nexus 6 is running pie roms nearly perfect . Unfortunately this sound problem persists… it is truely fristrating
So is there any kernel that can fix it in pie roms? Thanks
Click to expand...
Click to collapse
Having this same issue using the NitrogenOS Pie rom. Updated from 7.1.1 (didn't have this issue with 7.1.1).
Is it better with the Oreo 8.1?
centerpide said:
Having this same issue using the NitrogenOS Pie rom. Updated from 7.1.1 (didn't have this issue with 7.1.1).
Is it better with the Oreo 8.1?
Click to expand...
Click to collapse
No . I can confirm that all oreo roms got the same bug .
For me am using android x unofficial pie rom with popcorn kernel. This combination seems to fix this bug !
Try them or even try the kernel with nitrogen os rom .It may work..
El Gunslinger said:
Does this thread address the issue with SEVERAL 8.1 ROMs I've used, in which the speaker phone does not function during calls... and during calls alone. I can play media just fine... IMMEDIATELY after the speaker not working on the calls. I CAN however plug a headset in and communicate normally . Just desperately seeking an answer or I guess I'll go back to 7.1.2
Click to expand...
Click to collapse
Unfortunately no. Mine WAS working perfectly. The charge port broke after about two weeks after I made this thread (my luck), and after having it repaired, the problem seems to have gotten worse. For one, it no longer works in the configuration I mentioned in this thread (mind you, I did not reset it or anything). It also now varies from rom to rom, with the bigger issue now being that the top speaker ceases to function on certain roms, including the way I had it. Now, it drops volume for everything, and most of the time the top speaker will be weaker for the slight moments both decide to work.
New problem
Hi Crossvxm. I have had a Nexus 6 for two years. When I wiped it to sell it, the audio problem started. I had PureNexus.
I did what you suggested. I turned on mpdecision with BlackBird kernel and kernel auditor. I installed su terminal, to execute these commands with root access:
echo 1 > /sys/bus/i2c/drivers/tfa9890/8-0034/force_calib
echo 1 > /sys/bus/i2c/drivers/tfa9890/8-0035/force_calib
And the full volume audio came back! Videos, youtube, all working again! But, the audio in calls worked no more. So, after that, I wiped all, installed PureNexus 7.1, Nitrogen 8.1, stock 7.1... I tried everything, but the audio in calls never returned. When I reinstalled all these roms, the low volume problem appeared again, but the audio in calls never came back. Even WhatsApp calls have no audio. The microphone still works, because the other person indeed can hear you.
Do you have an idea about how can I solve it? At least to leave it usable as phone. Thank you very much for sharing your knowledge and time.
Butifarra said:
Hi Crossvxm. I have had a Nexus 6 for two years. When I wiped it to sell it, the audio problem started. I had PureNexus.
I did what you suggested. I turned on mpdecision with BlackBird kernel and kernel auditor. I installed su terminal, to execute these commands with root access:
echo 1 > /sys/bus/i2c/drivers/tfa9890/8-0034/force_calib
echo 1 > /sys/bus/i2c/drivers/tfa9890/8-0035/force_calib
And the full volume audio came back! Videos, youtube, all working again! But, the audio in calls worked no more. So, after that, I wiped all, installed PureNexus 7.1, Nitrogen 8.1, stock 7.1... I tried everything, but the audio in calls never returned. When I reinstalled all these roms, the low volume problem appeared again, but the audio in calls never came back. Even WhatsApp calls have no audio. The microphone still works, because the other person indeed can hear you.
Do you have an idea about how can I solve it? At least to leave it usable as phone. Thank you very much for sharing your knowledge and time.
Click to expand...
Click to collapse
This sounds like what happened to me recently. The configuration I mentioned in the very first post worked perfectly. After taking it to have the charge port fixed, the top speaker stopped working, and you could not hear the top speaker at all during calls. I thought the store broke it, but after giving up using it for some time, I realized that it would randomly try to output sound from the top speaker. After starting all over (flashing back to stock and flashing my same configuration again), the problem changed to where the top speaker was very low in sound when both speakers felt like working. I flashed the latest Dirty Unicorns based on 8.1 along with Popcorn Kernel by athulele but unfortunately it did not boot (as mentioned in his thread, the kernel is Lineage based).
I gave up on the Nexus for a few more days. When I decided to give it another go, I flashed the latest LineageOS (along with root for it via their own separate flashable zip), flashed Popcorn Kernel, installed Kernel Adiutor from Google Play (yes, it's spelled that way), installed the Terminal Emulator for Android and ran the command as well as checking the kernel settings to ensure MP Decision was on, capping the max frequency to 2.4Ghz (feels much less hot) and making sure everything was set to "set on boot". Unfortunately it did not work. The only way I got it to work again was to give up again, flash back to stock and flash Lineage and Popcorn Kernel exactly as I explained in this second paragraph.
So why did it work this time around? Everything was done the same, what could possibly make it work? I have a theory. When it was taken to the shop for repair, the battery died since it was already at 20%. As you can see I mentioned a few times "I gave up" on it, meaning I stopped bothering to fix it, and eventually it would run out of battery mainly from wifi and notifications. Every time it was dead, it was usually dead for at least 24 hours. Each time around, the issue would change. I don't know what it has to do with anything, but I do believe it plays a key role. Try letting your battery die, charge it back up to 100% and then try the process from either paragraph two or from my original post. After it began working again, I abused the heck out of the speakers, rebooted the phone, tried calls, etc. all without letting the battery die and it has not stopped working. I recently sold it as is and was contacted by the person who purchased it who was confused as he did not experience any sound drops either. He was originally buying it to replace the screen on his but decided to stick with mine since it was working perfectly so far.

Categories

Resources