I have flashed FIVE different TW ROMS with MF3 or MGA and they all have severe audio skipping issues when using Bluetooth or just the speaker on the phone. It seems completely random. I have used stock kernels and KT kernel but nothing seems to remedy the issue. I have flashed the ROM and instantly started to stream but the issue remains. Does anyone else have this issue? Has anyone found a fix for the issue?
TechSilver13 said:
I have flashed FIVE different TW ROMS with MF3 or MGA and they all have severe audio skipping issues when using Bluetooth or just the speaker on the phone. It seems completely random. I have used stock kernels and KT kernel but nothing seems to remedy the issue. I have flashed the ROM and instantly started to stream but the issue remains. Does anyone else have this issue? Has anyone found a fix for the issue?
Click to expand...
Click to collapse
See if it happens with an AOSP ROM
It doesnt, it only happens with TW.
TechSilver13 said:
It doesnt, it only happens with TW.
Click to expand...
Click to collapse
What is your baseband, and have you tried a different one?
I have used MF3 and MDL, MF3 is much more usable thats for sure.
TechSilver13 said:
I have used MF3 and MDL, MF3 is much more usable thats for sure.
Click to expand...
Click to collapse
Is your music stored on external, internal, or are you are streaming?
It's also strange that when the screen is on it really doesnt seem to skip but as soon as the screen goes off no matter then kernel the skipping starts, I am going to up the BlueTooth MHz on KT kernel and see if that helps.
It does it with internal, external, and streaming believe it or not.
TechSilver13 said:
It does it with internal, external, and streaming believe it or not.
Click to expand...
Click to collapse
Well damn man, I'm a little lost about what it could be then... It's not the music itself, because it works with AOSP, it's not your SD card since it happens no matter the medium, and it isn't the kernel or ROM since you've changed them a bunch.
I'm not going to give the generic response to ODIN stock and start over because I don't see that fixing it, unless it worked fine on stock.
Now I start to think about your headset, but it happens from the external speaker as well.
Do you have any apps running in the background that may interfere with the playback? Did it work on stock?
If I am on a stock MDL based ROM it doesn't skip at all. It's only with MF3 or above. I have also gave the Odin to stock a shot since one of the OPs said to do that. It's rsally strange.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
On KT kernel did you try raising the screen off min MHz with ktweaker and see if that helped?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
For what it's worth, I have never experienced this on stock MF3.
I reflashed from MDL to raise the screen off and it was still skipping. I went up to 594mhz and bumped the voltage up 50mv across the board. I guess my phone just hates MF3 and up.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Also this happens on WiFi and 4g While streaming music.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
TechSilver13 said:
I went up to 594mhz and bumped the voltage up 50mv across the board.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Did this help at all?
Craptain Krunch said:
Did this help at all?
Click to expand...
Click to collapse
O sorry I guess that would have helped. No, the music continues to skip. I don't know what is different with MF3 and beyond but something is borked for me.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4 Beta
Related
I looked for a solution everywhere but all i got was to change the phone. I have the no audio in-call problem. There is a way to fix it wothout changing the phone? Any help would be appreciate. Sorry for bad english.
ScimmiaUbuntu said:
I looked for a solution everywhere but all i got was to change the phone. I have the no audio in-call problem. There is a way to fix it wothout changing the phone? Any help would be appreciate. Sorry for bad english.
Click to expand...
Click to collapse
Are you running 4.2.2 with a non .48 radio? AKA did you enable LTE on 4.2.2?
i don't know and i don't think so, i was on PA 4.2.2 when i tried 0.47, 0.33, 0.27(?), i tried almost all modems, then i tried stock 4.2.1 (i bought my nexus 4 with 4.2.2), then i tried CM RC1 but never worked. I hope i can make it work without changing it. Thanks for the reply.
up
ScimmiaUbuntu said:
up
Click to expand...
Click to collapse
If you did all that then I guess it is a hardware issue.
First for the sake of trying give it a good shake ,cause the earpiece might have slipped for less than a mm.
If that doesn't help then you will have to either RMA or open the device and perform an earpiece exchange.
Sent from my Nexus 4 using xda premium
mariosraptor said:
If you did all that then I guess it is a hardware issue.
First for the sake of trying give it a good shake ,cause the earpiece might have slipped for less than a mm.
If that doesn't help then you will have to either RMA or open the device and perform an earpiece exchange.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
The problem is that I can make internet calls, so the microphone and the speaker both work. Which part have i to change?
ScimmiaUbuntu said:
The problem is that I can make internet calls, so the microphone and the speaker both work. Which part have i to change?
Click to expand...
Click to collapse
You have to change the earpiece
http://stellatech.com/lg-e960-nexus-4-ear-speaker,a,en,814613.html
Sent from my Nexus 4 using xda premium
mariosraptor said:
You have to change the earpiece
http://stellatech.com/lg-e960-nexus-4-ear-speaker,a,en,814613.html
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thw fact is that my speacker works well in internet call (Tango, skype, etc) so will surely that solve my problem? or will it work only in internet calls again?
ScimmiaUbuntu said:
Thw fact is that my speacker works well in internet call (Tango, skype, etc) so will surely that solve my problem? or will it work only in internet calls again?
Click to expand...
Click to collapse
Before you go swapping hardware I suggest you flash the full 4.2.2 stock image from Google. Bootloader, radio, everything. Then, check if the problem persists.
Sent from my Nexus 7 using Tapatalk 4 Beta
El Daddy said:
Before you go swapping hardware I suggest you flash the full 4.2.2 stock image from Google. Bootloader, radio, everything. Then, check if the problem persists.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I bought the phone with Google's pure 4.2.2, tried also original 4.2.1. Same question as before? Is it possible that the problem will persist?
Its highly unlikely it's a hardware problem if you have audio with internet calling. As I said before, flash the full stock image including an wipe with fastboot.
Sent from my Nexus 7 using Tapatalk 4 Beta
ScimmiaUbuntu said:
Thw fact is that my speacker works well in internet call (Tango, skype, etc) so will surely that solve my problem? or will it work only in internet calls again?
Click to expand...
Click to collapse
The speaker is other spare part and the ear piece is another one.
The main speaker how's with the antenna.
Sent from my Nexus 4 using xda premium
El Daddy said:
Before you go swapping hardware I suggest you flash the full 4.2.2 stock image from Google. Bootloader, radio, everything. Then, check if the problem persists.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
+1
RMA if you can before trying to change any hardware yourself, but this does sound like an earpiece problem
I'll try 4.2.2 stock. I'll keep you updated.
I had the same problem but it was fixed after I flashed the latest radio.
http://forum.xda-developers.com/showthread.php?t=2147194
Nothing worked (flashing/factory reset/downgrading) so I returned back the phone. The new one has no problem.
I had the same problem.. everything working fine in all apps except for normal calls. Even after resetting to stock Google image. After some digging I found the application Soundabout. It has an option to disable the check if a headphones has been inserted or not. After ticking the checkbox to disable the headphone check I could call again with the earpiece.
Funny thing tough, after reflasing my phone with CM 10.1 it still worked. Even on the stock Google image after re-enabling the headphones check I was able to make calls again with the earpiece. Really really strange problem.
You can find the app here: https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix&hl=nl
Altough you already replaced your phone it might be usefull for other people with the same problem.
Ok so I have a problem I am pure stock never rooted my S4 and after I took the MF9 update my phone will get stuck in a bootloop untill I turn on wifi or airplane mode as soon as I connect to data it will happen again reboot I flashed the MDL modem and firmware through odin and it stops it will let me be on data with no problems but as soon as I go back to MF9 same problems happen. Is anyone else having this problem and is there a fix
Sent from my SPH-L720 using xda app-developers app
budde2 said:
Ok so I have a problem I am pure stock never rooted my S4 and after I took the MF9 update my phone will get stuck in a bootloop untill I turn on wifi or airplane mode as soon as I connect to data it will happen again reboot I flashed the MDL modem and firmware through odin and it stops it will let me be on data with no problems but as soon as I go back to MF9 same problems happen. Is anyone else having this problem and is there a fix
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Sounds like it is time for a call to Sprint and make them fix it. What I would do if not rooted.
CCallahan said:
Sounds like it is time for a call to Sprint and make them fix it. What I would do if not rooted.
Click to expand...
Click to collapse
Whats wven more messed up is I have had 3 replacement phones and everyone has this problem i wonder if because the network is so unstable in my area right now if that could cause this to happen?
Sent from my SPH-L720 using xda app-developers app
budde2 said:
Whats wven more messed up is I have had 3 replacement phones and everyone has this problem i wonder if because the network is so unstable in my area right now if that could cause this to happen?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
If your network was unstable you wouldnt be able to get any signal at all but it wouldnt make your phone reboot. Have you tried factory reseting your phone??
Sent from my SPH-L720
ROMANTiC KiD said:
If your network was unstable you wouldnt be able to get any signal at all but it wouldnt make your phone reboot. Have you tried factory reseting your phone??
Sent from my SPH-L720
Click to expand...
Click to collapse
Yeah several times just did one and as soon as it connects to data it reboots. Damn I hate this ****
Sent from my SPH-L720 using xda app-developers app
Whatever is going on its in the kernel i flashed the MDB kernel and everything is working perfectly the only problem im having know is my phone says custom software.
Sent from my SPH-L720 using xda app-developers app
Dude you ain't the only one. The MF9 update has been a major pain the @$$ for a lottt of people. I wonder if Sprint is working on a new update. Hopefully push it out before the end of September. Although I am really liking MF9, I am probably in the minority. My device is smooth as hell and great battery life. Just yesterday I went 20hrs with 3hrs of on screen time!
Im having a similar problem. Random reboots when data is connected. I first thought it was the connection in my area that was causing the problem to (NV just started in Cleveland) until I encountered reboots while on WiFi. It doesn't matter what app I'm using as long is it uses the internet connection my phone may freeze vibrate two to three times then reboot. I even reapplied the MF9 update and the same problem exist.
I'm completely stock!
Thank You Based God!
Joe0113 said:
Dude you ain't the only one. The MF9 update has been a major pain the @$$ for a lottt of people. I wonder if Sprint is working on a new update. Hopefully push it out before the end of September. Although I am really liking MF9, I am probably in the minority. My device is smooth as hell and great battery life. Just yesterday I went 20hrs with 3hrs of on screen time!
Click to expand...
Click to collapse
We must be lucky. I keep reading about all these issues, but MF9 had been awesome for me. Not a single problem, and definitely much better than MDL.
Sent from my SPH-L720 using xda premium
maxpower7 said:
We must be lucky. I keep reading about all these issues, but MF9 had been awesome for me. Not a single problem, and definitely much better than MDL.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
+1 on that. Been on MF9 stock rooted since I got the phone a couple weeks ago and all has been well. I wonder if it could be a hardware issue mixed with something thats in the MF9 update. Sound crazy to anyone?
Sent from my SPH-L720 using xda premium
Yeah it looks like it is for sure the MF9 kernel I flashed mdl kernel and everything is good on that kernel. As soon as I odin mf9 and connect to data it happens again thanks for all the responses
Sent from my SPH-L720 using xda app-developers app
MF9 has given me one reboot so far. Battery life is way better than previously.
Sent from my SPH-L720 using Tapatalk 4
tenaciousj said:
MF9 has given me one reboot so far. Battery life is way better than previously.
Sent from my SPH-L720 using Tapatalk 4
Click to expand...
Click to collapse
Yeah its seems my problem is isolated. I cant find anyone other than 1-2 other people with this problem. I am back on MDL and everything is working perfect. I get my new device on fri I hope it has no problems
Sent from my SPH-L720 using xda app-developers app
Check your source for the MF9 kernel you have and try downloading and installing a different one.
budde2 said:
Yeah its seems my problem is isolated. I cant find anyone other than 1-2 other people with this problem. I am back on MDL and everything is working perfect. I get my new device on fri I hope it has no problems
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
+1 I went back to MDC. Let it update to MDL then let it update to MF9. Same issue. So I just Odined MDL and left it alone.
Thank You Based God!
amwworks said:
+1 I went back to MDC. Let it update to MDL then let it update to MF9. Same issue. So I just Odined MDL and left it alone.
Thank You Based God!
Click to expand...
Click to collapse
That's what I did si mdl works perfect. I will have a new phone hopefully today or Monday
Sent from my SPH-L720 using xda app-developers app
Ok so I go a new device a brand new S4 and still this one does the same **** what the **** is going on this is the 4th one I give up
Sent from my SPH-L720 using xda app-developers app
So, I have my phone rooted running a modified version of CM10.2. Recently, my phone started going into a "sleep of death" while charging overnight, where the phone is still on but is nonresponsive, requiring me to reboot. So I downloaded Safe Charge and it helped... Kind of. Now instead of going SoD every night, it only does it sometimes.
So, is what I'm experiencing part of the infamous JSS ROM deadlocks I've been hearing about? And is there some way to fix this, or am I just going to have to deal with it until KitKat comes out?
Sent from my Nexus 4 using xda app-developers app
jspitzer221 said:
So, I have my phone rooted running a modified version of CM10.2. Recently, my phone started going into a "sleep of death" while charging overnight, where the phone is still on but is nonresponsive, requiring me to reboot. So I downloaded Safe Charge and it helped... Kind of. Now instead of going SoD every night, it only does it sometimes.
So, is what I'm experiencing part of the infamous JSS ROM deadlocks I've been hearing about? And is there some way to fix this, or am I just going to have to deal with it until KitKat comes out?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
flash stock, you wont have to deal with it.
jspitzer221 said:
So, I have my phone rooted running a modified version of CM10.2. Recently, my phone started going into a "sleep of death" while charging overnight, where the phone is still on but is nonresponsive, requiring me to reboot. So I downloaded Safe Charge and it helped... Kind of. Now instead of going SoD every night, it only does it sometimes.
So, is what I'm experiencing part of the infamous JSS ROM deadlocks I've been hearing about? And is there some way to fix this, or am I just going to have to deal with it until KitKat comes out?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
SoD seems to show up randomly... I've heard that JWR ROMs have less SoDs than JSS so you could try one, or if your not into switching ROMs here is an app (free) that could help you. It's called Safe Charge, and the comments say that it works great.
If you read my OP, I already have Safe Charge installed and am still getting sod. I really like the ROM I'm using, but I may just have to switch to avoid this unfortunate issue.
Sent from my Nexus 4 using xda app-developers app
jspitzer221 said:
If you read my OP, I already have Safe Charge installed and am still getting sod. I really like the ROM I'm using, but I may just have to switch to avoid this unfortunate issue.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Oops I guess I missed that part... I'm pretty sure that you can find a near similar ROM/kernel setup for JWR... If all else fails, try stock...
(Oh and if you can still RMA it, do it. People have speculated that its a hardware issue...)
No worries. I'm trying out SlimBean because I hear that doesn't have the issues, but not being able to use Franco with it is a bit of a bummer. In fact I haven't yet found a third party kernel that does work with it.
Sent from my Nexus 4 using xda app-developers app
I had this happen to me with a particular rom. Everything was great until id lock the phone, then try to unlock and see nothing but a black screen. I switched roms and it never happened again.
Sent from my SGH-I317M using xda premium
So I had pacman v22.0.0, and I used survival mode on superSU pro to keep root, and flashed the pacman 4.3 update. My phone started lagging, overheating, and taking forever to charge. On 4.2.2 I had a few apps always running but rarely used more than 800MB of my RAM, but oh 4.3 with all the apps running the same, my RAM usage is normally about 1.4GB.
I'm assuming this has to be 4.3 right? Is it just me that's missing something, or have other people had the same experience with this?
Either way, if you're not completely running out of free ram, you have nothing to worry about.
Nope its not an issue with 4.3. I have few apps running with 800mb used . I am using PA 4.3. Never noticed any lag or overheating problems. It could be certain apps causing the issue?
Sent from my Nexus 4 using Tapatalk 4
Why don't you check in Running apps to see what apps are taking up your rams. I have been using 4.3 custom and now stock and its usually 400mb or less.
I assumed it was the fact that the pacman ROM had so many customizable options. I have the same exact apps running as I did before I updated, but my RAM usage has almost doubled. I know I have nothing to worry about, but when my phone is hitting 120 degrees on average, lagging, and the battery still drains while it's on the charger, I figured it's either the ROM or the fact that I didn't re root, I used survival mode. I checked my app usage, but the apps aren't accounting for most of the usage. Something else is, and I have no idea what.
With stock Rom and sometimes I can see 450mb Ram available.
So what?
Phone runs still flawlessly with no lags.
Don't get upset by numbers.
Unleashed by my Nexus 4
RASTAVIPER said:
With stock Rom and sometimes I can see 450mb Ram available.
So what?
Phone runs still flawlessly with no lags.
Don't get upset by numbers.
Unleashed by my Nexus 4
Click to expand...
Click to collapse
Guess it's rather the overheating and lagging that upsets him
You probably know this already, but it's not because of 4.3. Never had anything like that on PACman or CM10.2 - only once with a different kernel while navigating. But it just overheated, didn't lag or anything.
You should have flashed the factory images instead of just the zip;
http://forum.xda-developers.com/showthread.php?t=2010312
The radios, bootloader etc all need to be updated
Sent from my Nexus 4 using Tapatalk
RASTAVIPER said:
With stock Rom and sometimes I can see 450mb Ram available.
So what?
Phone runs still flawlessly with no lags.
Don't get upset by numbers.
Unleashed by my Nexus 4
Click to expand...
Click to collapse
I'm not upset by numbers, I tried explaining the numbers so that people who were going to respond to me with a worthwhile answer had a better understanding of what was going on. It does not run flawlessly, so if your gonna birch about my question and problem instead of trying to help, then just stfu.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Tom540 said:
You should have flashed the factory images instead of just the zip;
http://forum.xda-developers.com/showthread.php?t=2010312
The radios, bootloader etc all need to be updated
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thank you, I wasn't aware of that I'll try that out and see if it runs better.
Sent from my Nexus 4 using XDA Premium 4 mobile app
sinndissension said:
I'm not upset by numbers, I tried explaining the numbers so that people who were going to respond to me with a worthwhile answer had a better understanding of what was going on. It does not run flawlessly, so if your gonna birch about my question and problem instead of trying to help, then just stfu.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You obviously misinterpreted him. I guess he was trying to help by comparing to his situation. Maybe he just didn't understand completely what your real problem was, but I doubt that he tried to birch you
But as was mentioned here before you should probably flash latest bootloader and modem. Either by flashing the factory image or by flashing a zip that contains both bootloader and modem.
sinndissension said:
So I had pacman v22.0.0, and I used survival mode on superSU pro to keep root, and flashed the pacman 4.3 update. My phone started lagging, overheating, and taking forever to charge. On 4.2.2 I had a few apps always running but rarely used more than 800MB of my RAM, but oh 4.3 with all the apps running the same, my RAM usage is normally about 1.4GB.
I'm assuming this has to be 4.3 right? Is it just me that's missing something, or have other people had the same experience with this?
Click to expand...
Click to collapse
Same here...ever since I updated my PAC 4.2 to PAC 4.3 my average ram usage is 1.4 to 1.8 gb with same number of app usage...previously it used to be 0.8 to 1.2 gb...no lag however..
P.S. it was a clean install with updated modem
Neet said:
Same here...ever since I updated my PAC 4.2 to PAC 4.3 my average ram usage is 1.4 to 1.8 gb with same number of app usage...previously it used to be 0.8 to 1.2 gb...no lag however..
P.S. it was a clean install with updated modem
Click to expand...
Click to collapse
I've also got the same problem. ....
It's bloody annoying! !
Change your rom and kernel.
Sent by reversed alian technology.
Didn't need to change the ROM or kernel, I figured out the RAM bar was showing me running, AND cached processes together. There's actually only about 400mb of running processes. All the other stuff was cached. Didn't notice it till way later.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hi all.
I've been looking at different threads and a few people talk about it but not seen any fixes.
When I receive a call I get a 3-4 second delay before the screen wakes up meaning I don't know who is call or able to answer the call.
I'm running PA4 with r201 FK
If any one knows a fix please share.
Sent from my Nexus 4 using Tapatalk
Even we are facing similar issue on Note 2. Tried few things but issue still persists.
Seemingly got something to do with some service.
So it's not device related then?
Sent from my Nexus 4 using Tapatalk
Was just using my phone and tookna call, even when screen was on it still took a long time to show who was calling!?!
Sent from my Nexus 4 using Tapatalk
Seems to be getting worse! I have to wait for about 5 seconds now, or maybe it already did.
Does no one have a fix?
Thinking about reverting to stock to see if that fix's it then maybe flash each thing one at a time and see when it breaks.
Sent from my Nexus 4 using Tapatalk
If you're playing around with kernel's and under clocking the CPU this can affect how quickly the phone wakes up. But my phone has a delay of a few seconds before I am am aware of a call coming in. Maybe it will be fixed in a future update.
Phone : Nexus 4 /Rom : cataclysm / Kernel : Stock.
I've only installed them the same as others but they don't seem to suffer the same problems.
Any one have any fixes?
Sent from my Nexus 4 using Tapatalk
foxguard said:
I've only installed them the same as others but they don't seem to suffer the same problems.
Any one have any fixes?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
same problem to me !!! i9100g cm11 last update!!!i hope they fix it!!
yohan7 said:
same problem to me !!! i9100g cm11 last update!!!i hope they fix it!!
Click to expand...
Click to collapse
Installed stock and all is fine, have unrooted my phone and now starting fresh to see if helps.... fingers crossed!
foxguard said:
Installed stock and all is fine, have unrooted my phone and now starting fresh to see if helps.... fingers crossed!
Click to expand...
Click to collapse
Aaaaaand what happend? Did you resolved problem? I have problem too on cataclysm and hells b43 kernel.
Deni_NS said:
Aaaaaand what happend? Did you resolved problem? I have problem too on cataclysm and hells b43 kernel.
Click to expand...
Click to collapse
I remember having this issue with franco r201 I think, but it went away when I updated the kernel/changed kernels
lopezk38 said:
I remember having this issue with franco r201 I think, but it went away when I updated the kernel/changed kernels
Click to expand...
Click to collapse
And now your kernel is?
Deni_NS said:
And now your kernel is?
Click to expand...
Click to collapse
It went away for me with franco r203 but I had to restore a nandroid running franco kernel + r200 and I haven't checked for the bug since
lopezk38 said:
It went away for me with franco r203 but I had to restore a nandroid running franco kernel + r200 and I haven't checked for the bug since
Click to expand...
Click to collapse
I'll try then r203. Thanks
I installed a different ROM with stock kernsl and had same prob.
Did a complete wipe and unroofed the phone, took back to stock and all was ok.
Rerooted the phone, installed PA, all fine. Installed r203 and still all good
Sent from my Nexus 4 using Tapatalk
foxguard said:
Hi all.
I've been looking at different threads and a few people talk about it but not seen any fixes.
When I receive a call I get a 3-4 second delay before the screen wakes up meaning I don't know who is call or able to answer the call.
I'm running PA4 with r201 FK
If any one knows a fix please share.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
If you have DU Battery Saver or any similar app which puts your device on low CPU usage upon locking, then uninstall it. It worked perfectly in my case.