Database Users

[Info][WIP] LET's FIGURE OUT the sleep of Death!!!! [NOT A ROM]

Does anyone have a logcat from their dead transformer, during/around the time when it died?
Has anyone noticed any trends in when it happens? I saw something about 82% battery but I think that's just a coincidence.
Please post here so we can get to the bottom of this.
Jcarrz1
I think this is dev, unless it's a hardware issue. But hopefully we'll be able to discern that.

I have had multiple sleep of death issues after rooting. When I flashed back to the stock Blob, they stopped. Every time I root to Blob V5 (I am on the most recent firmware), they come back. I tried MoDaCo's Rom - they still occurred. Trying Prime's Rom now - so far it's working without any sleep of deaths.

I was on MoDaCo's Hr4 for a few days and never had a sleep of death. Since installing Prime 1.2 I've had 3 or 4.
Since we've had completely opposite experiences I think we can safely rule out that this issue is ROM related.

I've used both those roms and never had a sleep of death. But I also used the root method without the v5 blob, just the standard GingerbreakBB.

I've had one sleep of death incident, using unrooted stock Transformer configuration.

mine case: downgrade back to 8.2.2.6 using SD method (EP101_SDUPDATE.zip) then Gigerbreakbb then the BLOBV5 => lots of SOD issue.
May be we must update to the latest 8.2.3.9 before break using gingerbreakbb and install BLOBV5?
BR

Blob 5 is made to work with 8.2.3.9... It will most definitely have issues with the old firmware.
I am beginning to think the issue is with one of my apps and its settings. When I am rooted, I use Titanium Backup to restore my data and maybe the reason for the SOD is because something in an application isn't playing nice with Honeycomb... Obviously when I am not rooted, I cannot restore the settings and thus no SOD.
I just flashed back to root with Blob V5. Going to see if there are any SOD issues before installing apps... Will probably install one by one to try to see if I can find the problem - A PITA, but I really want the SOD to stop.

Had it with latest asus Update, no root and 40% brightness + wifi sleeps while screen is off. Lockscreen was enabled.
Sent from my Nexus One using Tapatalk
Edit:
Had another one after changing wifi sleep policy. I think it is wifi related.

The-Nazgul said:
Had it with latest asus Update, no root and 40% brightness + wifi sleeps while screen is off. Lockscreen was enabled.
Sent from my Nexus One using Tapatalk
Edit:
Had another one after changing wifi sleep policy. I think it is wifi related.
Click to expand...
Click to collapse
Other threads are pointing to the WiFi scanning be enabled. I have flashed back to MoDaCo Hr4 (because it was more stable for me than Prime 1.2) and also disabled WiFi notifications and will report back if/when I get a SOD.

Unrooted, getting about one or two of these a day depending...... seems to happen more if I've left it sleeping for an hour or more.

Putzy said:
Unrooted, getting about one or two of these a day depending...... seems to happen more if I've left it sleeping for an hour or more.
Click to expand...
Click to collapse
this could relate to wifi scanning as well. were you connected, and what are your current settings?
Thanks for participating everyone, so far there isn't a conclusive answer.
However, could someone install log collector from the market, and leave it there until the BlackSOD happens, and then upload the file? that would be super awesome. preferably someone who gets them all the time. if the last thing in the logcat is consistently wifi-related, then we're on to something.
is there any firmware version on which NOBODY has EVER had a BlackSOD? This could be worth looking in to as well.

Well, I rerooted and have installed about 80% of my apps. So far no SOD. I have a few more apps to install and I usually freeze some of the unwanted apps. Will post an update later. Also, I read on other forums that fancy widget caused issues like this on other tablets. I had been using beautiful widgets I wonder if the way that tries to access wifi causes issues.
The apps I have yet to install are:
Watchdog lite, beautiful widgets, adfree android
Sent from my Transformer TF101 using Tapatalk

Just had one while wifi was disabled! I guess that makes it less likely that wifi causes the problem.
Next time I will upload a logfile!
Sent from my Nexus One using Tapatalk

I've had 2 so far, both with Hr4 and blob v5. Battery has been at different levels, so I think thats a coincidence.

Has anyone tested on a 100% Factory reset device (either with a custom or stock ROM?) That should help rule out any apps which may cause the problem.
FWIW, never had this issue (have run Stock, HR1 -> HR4 & Prime V1.2)

so far no SOD after a clean tstart

Had a SOD this morning on Hr4 so I will run Log Collector today and hope to catch another. I'm assuming that Log Collector is continually writing to my Gmail draft so it should be there after the full reboot? Doesn't seem like it will let me mirror logcat to a file on sdcard...
sent from a device using an app

I realize this isn't the least bit helpful, but after having several SoD issues, and trying all the fixes (and then undoing them), I haven't had the issue for a week now. Mine would do it sporadically -- it would happen once in a day, and then 3 times in a day -- and the only thing I've left changed is disabling the lock screen, but I think that's just coincidence. This will be a hard one for Asus to nail down.
Hopefully someone produces a helpful log for Asus, I'm sure some non-XDA people may think they have a dead tablet rather than one they have to force power down and reboot.

had my firs SOD today.
running prime 1.2 US. battery at 96%. wifi on.

spuniun said:
Had a SOD this morning on Hr4 so I will run Log Collector today and hope to catch another. I'm assuming that Log Collector is continually writing to my Gmail draft so it should be there after the full reboot? Doesn't seem like it will let me mirror logcat to a file on sdcard
Click to expand...
Click to collapse
So it does not seem that this app will work because it only collects logs in real-time, does not store them for later analyzing. What else can I use other than leaving adb logcat running?
sent from a device using an app

Knock on problems (proximity sensor?)

Hi all,
EDIT2: MAIN PROBLEM FIXED!
I was incredibly frustrated last night, so I figured I'd just re-root as I have a copy of the stock flash tools and a TOT file sitting on my PC should I need to return.
I rooted (again), installed binaries, uninstalled Superuser, installed Super SU, and (just for fun) installed Greenify.
Lo and behold, I rebooted three times now and NO KNOCK LOOP!
I'm still having issues with knock-on not waking the phone sometimes, but once I hit the power button everything works fine.
As I posted above, the proximity sensor app seems to have a huge delay when uncovered. 3-15 seconds at totally random intervals. This might explain my still present knock-on delay issues.... ?
EDIT: Not Greenify causing this, but some other combo of rooting and system file changes. Could also be the proximity sensor misbehaving or just a bad copy of the phone.
Just a friendly PSA, but Greenify (the popular hibernation app that is really awesome) will gimp your knock-on feature for good. As in: returning to stock does not fix it. Myself and at least one other user have had this problem. I'm now having to swap out my phone after just getting it how I like it, which is infuriating.
I'd rather wait until somebody gets a fix up, but I'm within 14-days so I'm not risking it.
Note: This is CLEARLY not the fault of Greenify. It's some bizarre file system/sensor error. Greenify is great.
Related thread where the problem was thought to be fixed... but is not for people who installed Greenify.
I'm using the Verizon variant, so I don't know if this applies to GSM models.

From a dev standpoint this makes zero sense to me, so I'm kind of curious if anybody has better insight. Greenify, for the most part, is just leveraging system-level features to disallow the start-up of a particular program when the screen is off.
I am personally using Greenify on a number of apps with success and no ill side-effects. There are a number of code dependencies involved in its use, but mainly it is the knock-on related apk/odex in /system/app - so is it possible these people are Greenifying the wrong things?
Also, I would question their return to stock, Greenify doesn't work on a hardware level. If they didn't return the right files and/or kernel to stock, yeah, it might have lingering ill-effects. I would say that merely flashing a stock ROM is not returning to stock. It isn't clean enough.
tl;dr: There is no logical reason in my mind that Greenify would permanently break knock-on. I need more proof.

I've been using greenify since the day after I got the phone and rooted it, so 2 weeks now, and knock on works perfectly every single time.
Sent from my VS980 4G using Tapatalk 4
---------- Post added at 12:14 PM ---------- Previous post was at 12:14 PM ----------
and I'm on the Verizon version. what app are you guys hibernating that's causing this?
Sent from my VS980 4G using Tapatalk 4

burningembers said:
From a dev standpoint this makes zero sense to me, so I'm kind of curious if anybody has better insight. Greenify, for the most part, is just leveraging system-level features to disallow the start-up of a particular program when the screen is off.
I am personally using Greenify on a number of apps with success and no ill side-effects. There are a number of code dependencies involved in its use, but mainly it is the knock-on related apk/odex in /system/app - so is it possible these people are Greenifying the wrong things?
Also, I would question their return to stock, Greenify doesn't work on a hardware level. If they didn't return the right files and/or kernel to stock, yeah, it might have lingering ill-effects. I would say that merely flashing a stock ROM is not returning to stock. It isn't clean enough.
tl;dr: There is no logical reason in my mind that Greenify would permanently break knock-on. I need more proof.
Click to expand...
Click to collapse
I'd have to agree with this!!
Sent from my GT-N7100 using xda app-developers app

Knock on seems to work on mine (most of the time anyway) while using Greenify for a couple of weeks now. If it was going to gimp it, I'm thinking it would have by now. I have the T-Mobile variant. Its basically just hibernating apps from the market, not any system apps so I guess I don't see the correlation.

Greenify works for me
I'm stock rooted and I heavily use Greenify with my Verizon G2. No problems with Knock On at all!
Edit: Stock rooted (not the chinese way), no OTA, auto-hibernation feature works perfectly too.

um question... did you guys who have the problem use the Chinese root method? someone brought it up and now I'm curious....
i did but then flashed back to stock to reroot the good way. you guys who aren't having the issue with me, you use Chinese or regular?
Sent from my VS980 4G using Tapatalk 4

I only froze Facebook and Twitter. Have completely Re flashed stock and BlackHole ROM to no avail. Read the thread, it seems to be vexing even advanced users. The fix of changing screen effect does not resolve it.
YMMV
Sent from my VS980 4G using XDA Premium 4 mobile app

lattiboy said:
I only froze Facebook and Twitter. Have completely Re flashed stock and BlackHole ROM to no avail. Read the thread, it seems to be vexing even advanced users. The fix of changing screen effect does not resolve it.
YMMV
Click to expand...
Click to collapse
When you say re-flashed stock, what does that mean?
Are all affected users on Verizon and using BlackHole ROM?
I'm just trying to narrow this scope down, because this still makes no sense to me.

burningembers said:
When you say re-flashed stock, what does that mean?
Are all affected users on Verizon and using BlackHole ROM?
I'm just trying to narrow this scope down, because this still makes no sense to me.
Click to expand...
Click to collapse
1) I rooted
2) installed Greenify
3) bug happens the next morning.
4) went back to stock, using these instructions.
5) bug happens again
6) re-rooted and installed BlackHole ROM.
Everything was (seemingly) cool for a bit, but last night it happened again. Twice this morning I've had the weird behavior sited in the original thread and I'm going to take it into VZW and leave stock in until this gets figured out.
Again, not trying to cause alarm or panic. I'll update my post to reflect the YMMV nature of this issue.

You should really rename this thread. I have not experienced any knock issues and I've installed this app since I bought the phone. False psa
---------- Post added at 12:44 PM ---------- Previous post was at 12:40 PM ----------
lattiboy said:
1) I rooted
2) installed Greenify
3) bug happens the next morning.
4) went back to stock, using these instructions.
5) bug happens again
6) re-rooted and installed BlackHole ROM.
Everything was (seemingly) cool for a bit, but last night it happened again. Twice this morning I've had the weird behavior sited in the original thread and I'm going to take it into VZW and leave stock in until this gets figured out.
Again, not trying to cause alarm or panic. I'll update my post to reflect the YMMV nature of this issue.
Click to expand...
Click to collapse
Are you using a custom launcher or does the rom install a custom launcher? That would surely affect the knock on feature.

SysAdmNj said:
Are you using a custom launcher or does the rom install a custom launcher? That would surely affect the knock on feature.
Click to expand...
Click to collapse
Nope, using stock home, never even installed Nova or anything else.
I added a big YMMV to it, but because the outcome seems quite dire on such an expensive device, I feel this is warranted.

lattiboy said:
Nope, using stock home, never even installed Nova or anything else.
I added a big YMMV to it, but because the outcome seems quite dire on such an expensive device, I feel this is warranted.
Click to expand...
Click to collapse
You went back to stock, rooted, installed greenify and still the same issue? Which root method did you use, the chinese one?

The issue might be caused by misuse of Greenify. Have you greenified any system apps related to the Knock-on feature?
Greenify should never "damage" your device in a non-recoverable way since it never touches any system files. Just simply de-greenify the app and manually relaunch it once to restore everything to normal.
Hope one of you G2 users could find out that key greenified app which caused this terrible issue, thus we could warn others in a more effective way.

lattiboy said:
Nope, using stock home, never even installed Nova or anything else.
I added a big YMMV to it, but because the outcome seems quite dire on such an expensive device, I feel this is warranted.
Click to expand...
Click to collapse
Yeah, it is an expensive device, but when you go rooting it and mucking around with system files, it is kind of a risk you take. My real issue is two-fold 1) Bad publicity for Greenify when I still don't believe it to be a problem with Greenify and 2) That LG/Verizon are taking a loss on time/cost because users are essentially breaking their own device. I put this on-par with you putting your phone in a bucket of water and then going back to Verizon and getting a new one because it doesn't work.
Now, that said, maybe this truly is a HARDWARE bug/issue with the Verizon model. On AT&T I have Facebook, Humble Bundle, Keep, OfficeSuite, Reddit News, Series Guide, and Google Search greenified. I've modified system APKs. I've flashed some ROMs. I've toggled Knockon off/on in settings. And my phone is fine.
Someone needs to start data collecting. What model phone do these users have, did they take the OTA, did they at some-point use Chinese root method, are they in a dark room, did they toggle Knockon on/off, does toggling knockon on/off on an in-store device result in a similar issue, are they all on Verizon, etc. etc.
One thing someone mentioned the other day was that the latest Verizon OTA changed the scheduler from CFQ to ROW. Is it possible that this is borking the knockon application from staying in the queue properly to register the knockon events?

burningembers said:
Yeah, it is an expensive device, but when you go rooting it and mucking around with system files, it is kind of a risk you take. My real issue is two-fold 1) Bad publicity for Greenify when I still don't believe it to be a problem with Greenify and 2) That LG/Verizon are taking a loss on time/cost because users are essentially breaking their own device. I put this on-par with you putting your phone in a bucket of water and then going back to Verizon and getting a new one because it doesn't work.
Now, that said, maybe this truly is a HARDWARE bug/issue with the Verizon model. On AT&T I have Facebook, Humble Bundle, Keep, OfficeSuite, Reddit News, Series Guide, and Google Search greenified. I've modified system APKs. I've flashed some ROMs. I've toggled Knockon off/on in settings. And my phone is fine.
Someone needs to start data collecting. What model phone do these users have, did they take the OTA, did they at some-point use Chinese root method, are they in a dark room, did they toggle Knockon on/off, does toggling knockon on/off on an in-store device result in a similar issue, are they all on Verizon, etc. etc.
One thing someone mentioned the other day was that the latest Verizon OTA changed the scheduler from CFQ to ROW. Is it possible that this is borking the knockon application from staying in the queue properly to register the knockon events?
Click to expand...
Click to collapse
I did take the OTA, but before flashing the current version of TWRP.
I feel bad about it and I should've waited until these kinds of things were worked out.
I'm trying one last flash back to stock to make sure it isn't a user generated problem with flashing incorrectly.

lattiboy said:
I did take the OTA, but before flashing the current version of TWRP.
I feel bad about it and I should've waited until these kinds of things were worked out.
I'm trying one last flash back to stock to make sure it isn't a user generated problem with flashing incorrectly.
Click to expand...
Click to collapse
So flashing back to pre-OTA doesn't clear the problem at all?

burningembers said:
So flashing back to pre-OTA doesn't clear the problem at all?
Click to expand...
Click to collapse
No, I just flashed to stock (yet again) and I got the weird wake-lock freeze thing within 30 minutes.
Super annoying.

lattiboy said:
No, I just flashed to stock (yet again) and I got the weird wake-lock freeze thing within 30 minutes.
Super annoying.
Click to expand...
Click to collapse
What's your Baseband and Kernel version in Software Information?
I know for a *fact* that the OTA changed the cpu scheduler. What I'm curious is if their scheduler changes have somehow caused service-level applications like the KnockOn APK to die/hibernate during a lengthy deep sleep. This makes way more sense to me than merely using Greenify causing a permanent breaking of software/kernel interactions.

burningembers said:
What's your Baseband and Kernel version in Software Information?.
Click to expand...
Click to collapse
This is it. No root, fresh stock 15 minutes ago.

Choppy bluetooth audio. .....

So apparently the choppy bluetooth audio issue is on the Note 4. Has anyone found or know of a solution to the problem? It pretty much only happens when playing games.

Are you using Wanam Exposed?

Yes indeed.

This problem is covered in other threads. Start by disabling exposed then go read up on the rooting thread.

I consider myself to be a thorough user of google search and also did a thorough search through xda, and found no indication this is linked to wanam. If you really wanted to help you could posted a link to where I could read up on this, instead of giving a general statement. You disposition is the reason why there are many posts on forums asking questions about things. If you cant given a confident answer, I would suggest not getting involved. But thanks at least on helping pin pointing this to wanam at least, assuming that is the case. So excuse me while I go do some searching for bluetooth issues and wanam.

So sorry I couldn't spoon feed you the answer. Good luck.
---------- Post added at 06:13 PM ---------- Previous post was at 06:02 PM ----------
Sitting waiting for a food order, found the post. This worked for me: http://forum.xda-developers.com/showthread.php?p=56122331
---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------
Oops, copy and paste fail there, disregard.

I hate wasting space and time on pointless things and also jumping to conclusions, but its obvious you have nothing to offer except smart butt comments lacking the smart part. I hate being short, but your link lead to the auto root thread saying dont install xposed because of shealth issues which were resolved with another xsposed module already. Even did a search through the whole thread for bluetooth, which yeilded no results. Even did a google search for choppy bluetooth and wanam and it brought me to this post I created. So do the forum a favor and stop wasting space with useless statements about things you dont know. Thanks.

The choppy Bluetooth has nothing to do with exposed. Having the same issues with non-rooted device. No solution though, sorry.
Sent from my SM-N910F

I'm not having any issues from either a Bluetooth headset or Bluetooth speakers. I'm rooted and user Xposed. Exynos version.
Sent from my SM-N910U

Yeah i guess it could be either related to being rooted or having xposed intalled. I contacted the developer of the rom I am using, which is dynamic kat. He is working with me now to find a resolution. Sad thing is I had the same problem with my note 3 running stock rom with xposed and root too.
BTW, the issues only kick in when playing any of the games I have installed.

It's a chronic issue with Samsung Phones (I had it on S3 even). Most common cause is phone going to sleep when the screen is off. That's obvious not the case with you, since you are playing games when it happens. One suggestion I saw that might work is turning WiFi off.

Same problem for me. Non rooted. I noticed it more using Deezer.

I found a fix. Does this happen when screen is off? When I changed kernel CPU Governor to ondemand, all Bluetooth choppiness has disappeared.

Brava27 said:
I found a fix. Does this happen when screen is off? When I changed kernel CPU Governor to ondemand, all Bluetooth choppiness has disappeared.
Click to expand...
Click to collapse
Will try with screen off. From memory my screen was on.
Where do u change this setting? Is this a root only change?

No issue for me stock on T-Mobile. I have noticed a very small chop - not even a chop, more like a slight immediate skip in the audio - randomly and very infrequently. I've been using a bluetooth speaker and my car's Uconnect system for several hours with this phone.

Just to keep things clear, I dont want to get this thread cluttered with random things that may not apply. But I have owned over 10 samsung devices and never had this problem until I rooted and installed xposed on my note 3 and 4. So I am sure it is because of either xposed or root. I doubt it is root. I will try going through different xposed modules to see if I can find the root cause. Also as I stated originally this only happens when playing games and only games. Not when the screen is off or playing any thing by audio other than games. If you have connection issues I would suggest making sure your bluetooth device is fully charged and there is no obstructions in the signal. Most bluetooth devices work best within 25 feet line of sight and keep in mind not all bluetooth devices are built the same. Some get less than 10 feet till they start having connection issues.

Same issue here...
On a completely stock 910U, no root - I get very intermittent Bluetooth connections to my car stereo. (My old S4 was / is perfect).
I also get intermittent function with my Fitbit. Most of the time the phone call notifications don't come through to the fitbit with the Note 4.
Very frustrating - both are key functionality for me.
If it looks like this is a phone issue then I'll probably return it and go back to my S4 until it's properly fixed - I am not interested in workaround with root or custom ROMs.
Cheers - N

sniickers said:
Just to keep things clear, I dont want to get this thread cluttered with random things that may not apply. But I have owned over 10 samsung devices and never had this problem until I rooted and installed xposed on my note 3 and 4. So I am sure it is because of either xposed or root. I doubt it is root. I will try going through different xposed modules to see if I can find the root cause. Also as I stated originally this only happens when playing games and only games. Not when the screen is off or playing any thing by audio other than games. If you have connection issues I would suggest making sure your bluetooth device is fully charged and there is no obstructions in the signal. Most bluetooth devices work best within 25 feet line of sight and keep in mind not all bluetooth devices are built the same. Some get less than 10 feet till they start having connection issues.
Click to expand...
Click to collapse
Did you find a solution?

Unfortunetly no. Only way to prevent it is running stock at this point. Not sure whats causing the issue, whethet it is root, custom rom, xposed, or any xposed modules. Maybe someone will eventually post a sound fix. I have heard of developers fixing it in their custom roms. But no posting of how the fix is created.

JagDave said:
The choppy Bluetooth has nothing to do with exposed. Having the same issues with non-rooted device. No solution though, sorry.
Sent from my SM-N910F
Click to expand...
Click to collapse
+1 same here haven't rooted yet its randomly choppy heard it was a Bluetooth 4 issue

SMS issues- not receiving all messages, people not receiving all of mine

Like the topic says, I am having major issues with SMS messages. I am not receiving all messages that are being sent to me, and people aren't getting all of mine. It's not an issue I can reliably reproduce, it's just very sporadic. I'm on AT&T and I've called them a few times and every time they tell me they corrected something and the issue should be resolved, but I'm still having problems. Is anyone else having issues like this? I am starting to think it's a problem with the phone and not the network, which would be a damn shame because I REALLY like this thing.

_MetalHead_ said:
Like the topic says, I am having major issues with SMS messages. I am not receiving all messages that are being sent to me, and people aren't getting all of mine. It's not an issue I can reliably reproduce, it's just very sporadic. I'm on AT&T and I've called them a few times and every time they tell me they corrected something and the issue should be resolved, but I'm still having problems. Is anyone else having issues like this? I am starting to think it's a problem with the phone and not the network, which would be a damn shame because I REALLY like this thing.
Click to expand...
Click to collapse
I'm on AT&T as well and was having a similar issue but was when I changed my default SMS app, such as Evolve/Go/etc.. I don't really like the stock app. Found Textra and has been working with no issues.
Are you completely stock... app/rom/etc?

Which APN are you using?

khaos64 said:
I'm on AT&T as well and was having a similar issue but was when I changed my default SMS app, such as Evolve/Go/etc.. I don't really like the stock app. Found Textra and has been working with no issues.
Are you completely stock... app/rom/etc?
Click to expand...
Click to collapse
Stock ROM but not kernel, but that shouldn't affect it I wouldn't think. Still using the stock messenger app, I never liked using 3rd party apps for that stuff. I'm gonna go and get a new SIM card tomorrow I think and try that. If that doesn't work, I might call Oneplus and try to exchange the phone.
Edit: Tried Textra at yours and my friend's recommendation and I am never going back. It is vastly superior to the stock messaging app. It remains to be seen if it solves my problem though.

lilbluemirage said:
Which APN are you using?
Click to expand...
Click to collapse
I set my own based on info I found online because I couldn't get LTE to work otherwise. What do you recommend?

_MetalHead_ said:
Stock ROM but not kernel, but that shouldn't affect it I wouldn't think. Still using the stock messenger app, I never liked using 3rd party apps for that stuff. I'm gonna go and get a new SIM card tomorrow I think and try that. If that doesn't work, I might call Oneplus and try to exchange the phone.
Click to expand...
Click to collapse
I understand the 3rd party stuff.
Kernel shouldnt.
I use ATT Phone APN, I get LTE though I still have an iPhone 6 imei registered with my number, but the settings look pretty much the same.
If haven't already try dirty flashing Oxygen... 2.1.2? Doubt it will change anything as it working sometimes...but never know.
Also a semi last resort maybe factory reset and flash but don't sign into your main Google account to make sure it doesn't pull any settings or anything so it's like a brand new phone. Confirm ATT Phone APN is set and do some testing...
I noticed some xposed stuff, while unlikely maybe there could be something there that could be conflicting with it??
If none of that works, not sure...
I would try a family member/friend's sim first as you know they aren't having issues with it or their service. Then depending on that, a new sim.

I've had similar issues before. I was running on OOS, rooted, with XPOSED installed. I noticed that it had something to do with some XPOSED modules. I believe PowerNap Xposed was behind it. I had to flash back to stock since wiping data, caches, and etc won't fix it for me.

saywhatt said:
I've had similar issues before. I was running on OOS, rooted, with XPOSED installed. I noticed that it had something to do with some XPOSED modules. I believe PowerNap Xposed was behind it. I had to flash back to stock since wiping data, caches, and etc won't fix it for me.
Click to expand...
Click to collapse
Welp, I do have power nap installed. Seeing as though I have noticed absolutely zero improvement in battery life with it I have no problem ditching it. But you don't think uninstalling it will be enough?

_MetalHead_ said:
Welp, I do have power nap installed. Seeing as though I have noticed absolutely zero improvement in battery life with it I have no problem ditching it. But you don't think uninstalling it will be enough?
Click to expand...
Click to collapse
I haven't tried just uninstalling it. Hehe I flashed everything back from a clean slate just to be sure

saywhatt said:
I haven't tried just uninstalling it. Hehe I flashed everything back from a clean slate just to be sure
Click to expand...
Click to collapse
Well I uninstalled it and it is entirely possible my problem is solved, to which I owe you a debt of gratitude. I haven't had an issue with SMS since doing it so keeping the fingers crossed.

Phone freezing when playing music?

Hello,
I originally posted this in the Pure Nexus Project thread because I thought it might have had something to do with the rom, however, I don't think that's the case judging from the other replies. I still haven't found the solution, so I figured I should try posting it here:
Anyone having issues with the phone randomly freezing when playing music? Actually, i'm not sure if it applies to all music apps, but for me, it happens when using Spotify. Really random too. Sometimes I go days without freezing, whereas other days, it's just constantly freezing one after another.
I do have V4A installed and maybe it's due to that. Anyone else have this problem and can confirm that it is V4A? or even Spotify?
Click to expand...
Click to collapse
One user stated that disabling battery optimization for the app in the battery settings fixed it for him. I tried this, but still get the random freezes. Has anyone possibly found out what's causing the issue and if there is a workaround? Thanks in advance :good: