yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] jkc120:
Did you ever install/use a different app?

This is a REALLY nasty issue.

Here's what I have found:

1. restore my 3/13 cm11 build nandroid, and the stock messaging app and also 8sms version 1.24 work fine

2. install 8sms 1.26 (update it from play store), and the issue occurs

Now this is the really annoying part. If I then uninstall 8sms and delete all my sms messages, now the stock messenger has the problem! I have found NO WAY to fix it, other than restoring a nandroid.

So whatever 8sms is doing, it's corrupting something and I can't fix the issue.

I think I'm going to restore my 3/13 nandroid, uninstall 8sms and use a different app at this point. :(
[Verizon Samsung Galaxy S 4] jkc120:
Created a google docs spreadsheet to track it. It seems this issue ONLY occurs with the newer 8sms OR stock messaging sometime after the 3/13 nightly:

https://docs.google.com/spreadsheet/ccc?key=0Aqb5UP2-CgaGdHc5ZnFDdmo2dXg5X2dyRlFUUzhrQ1E&usp=sharing

I am using hangouts for now, but really would rather not. Guess I'll give it a few days and see if it grows on me for use as my SMS client. Two issues:

1. can't get a different color for sms notifications (without lightflow, but meh)

2. nova launcher doesn't show an unread count for hangouts :(
[Verizon Samsung Galaxy S 4] mangalo2004:
Do you happen to be flashing a google dialer zip? I had the same problem, and found that the Google dialer was causing it.
[Verizon Samsung Galaxy S 4] crookedview:
I used hangouts as my SMS app for about a week, bit did not have the unread issue at the time. This was more than a month ago.
[Verizon Samsung Galaxy S 4] jkc120:
Hangouts doesn't have the problem, it appears to be only with the stock messenger in recently (anything later than 3/13) nightlies or with stock-based messengers like 8sms.

I flashed 3/19 and was using Textra instead, which works nicely. But then I noticed I have a massive wakelock issue "weatherupdateservice" wakelock or something. I could find nothing to disable/check related to it, so I have rolled back to my 3/13 nandroid for now and plan to use Textra there until I hear word of wth is going on with this "sms unread" issue.
[Verizon Samsung Galaxy S 4] swordmastr54:
I Odined back to MDK stock and redid all of that(for the first time i bought the phone with it all ready) and clean installed the 19th build with KT kernel and I see no issues as of yet, its pulling down all of my apps.
[Verizon Samsung Galaxy S 4] jkc120:
Well, I don't see any commits that look remotely like they would fix the "sms marked unread" issue. So this begs the question - how do we get such bugs fixed since we can't report bugs on nightlies? I'll try to see if I can get some confirmation that this affects non-jflte but still I am wondering what the proper way to make sure an issue like this gets fixed is. I mean, surely there are people using the stock messenger right? Guess I'll stick to 8sms version 1.24 or textra/hangouts for now.
[Verizon Samsung Galaxy S 4] jorceshaman:
You're reporting it by commenting here but I believe it was previously mentioned that Invisiblek is on vacation right now. I'm not sure when he's coming back or if he already has but just hang tight and as long as it's actually a CM issue, it'll be fixed eventually. It's just the downside of nighties. No promises of stability.
[Verizon Samsung Galaxy S 4] scarmon25:
He is back. Also. Its weird. Buildbot shows it built a new build for 3/20. But there is no output build to Download. ?(
[Verizon Samsung Galaxy S 4] jkc120:
Yep, I know of the caveats of running a nightly. My issue is that once this sms unread bug starts happening you can't fix it without a nandroid restore for some reason, at least with 8sms and the issue appears identical in behavior. So basically, I can't switch to a newer nightly unless I use a different sms app, or I risk corrupting whatever it is that causes this :/
[Verizon Samsung Galaxy S 4] bsimpson1:
does anyone know why the mic used in apps like guitar tuners or voice recorders is so quiet?
[Verizon Samsung Galaxy S 4] Black6spdZ:
CM guys have really fubared the S4 since the recent unification of ROMs.. I may be a minority using my VZW phone full time on a GSM network, but the only way I was able to properly get incoming calls was to flash the ATT builds.. well now they have brought back this problem with the unified build with no fix in sight I'm sure. This has been an issue in ALL jfltevzw builds as far back as CM10.1 with no resolution!
[Verizon Samsung Galaxy S 4] papstar:
These lockups are getting ridiculous. Getting at least a dozen a day, mainly when just pulling down the notification bar.
[Verizon Samsung Galaxy S 4] jkc120:
Hmm I haven't seen any but I rolled back to 3/13 until the unread sms issue is fixed.
[Verizon Samsung Galaxy S 4] bsimpson1:
I wonder to what degree the use of ART over dalvik could be responsible for the recent issues people have been describing. I've been using dalvik and haven't had any issues with the primary functions (phone calls, texting) of the phone. I'm also on Verizon and completely unfamiliar with the concept of GSM, which from what I've read seems to be much more affected by the recent changes than CDMA/LTE
[Verizon Samsung Galaxy S 4] jkc120:
Interesting question. I am indeed using ART. I wonder if the other(s) reporting the unread sms thing are also on ART?

---------- Post added at 10:01 PM ---------- Previous post was at 09:39 PM ----------

Nope:

1. from 3/13 nightly, switched from art to dalvik

2. rebooted back into cm, let the dalvik cache rebuild

3. booted to recovery, flashed 3/19

4. sms unread issue persists in the stock messenger

So at least for that issue, ART isn't the cause (I wasn't expecting it to be, but figured I would test anyway).
[Verizon Samsung Galaxy S 4] SamXp:
Good grief, what a mess. The single most popular and iconic ROM in the business, combined with the single most popular and iconic phone in the business, and it is in shambles.

I've been running Gummy and SlimKat and having a few annoying problems. Thought I would come back to ole reliable CyanogenMod, but now the problems I've been experiencing on Gummy and SlimKat seem trivial, by comparison!
[Verizon Samsung Galaxy S 4] scarmon25:
I noticed the search from dialer was put in this build. No 3G still but I've come to expect that. Everything else works for me fortunately

Too many bills, Too little cash. Story of my life.

Jflteusc CM11 Latest Nightly.
[Verizon Samsung Galaxy S 4] DalekCaan:
I'm also using a VZW phone on GSM. Is there a specific ATT build you would recommend?

Thanks.
[Verizon Samsung Galaxy S 4] jkc120:
8sms has a fix for unread sms issue

I've been in communication with the 8sms dev, and he has a version he's working on that avoids the unread messages things.

Basically, the reason hangouts and some other mms apps don't have the issue is because they "cheat" and look at the messages table in the SMS sqlite DB to see if a thread is unread or not, but Android docs say you should use the threads table to check if a thread should be shown as unread.

Somehow, there's a bug in the way group SMS is handled, because by nature of how it works, what is happening is a message from person X is first going to show up in your individual thread with that person, then it gets kind of post-processes or evaluated and is moved into the group SMS thread if appropriate. For some reason in the newer 8sms and the Messaging app in the newer cm11 nightlies, this is causing the bug because the individual thread is being left unread.

So 8sms is working around this and sort of "cheating" like some of the other apps.

I imagine since it's pretty prevalent, CM will have to resort to something similar. Though I don't know how widespread the issue is yet.

FWIW, I flashed the 3/21 nightly and the debug 8sms version the dev provided me works now! I'll report back in a bit of any other issues I see coming from the 3/13 nightly.

---------- Post added at 09:18 AM ---------- Previous post was at 08:49 AM ----------

The weird wakelock issue I had in 3/19 hasn't re-appeared so far.

Camera, Camcorder, LTE, GPA all work well. Don't have a bluetooth headset here to test BT with.

I haven't noticed anything broken in it so far. I imagine the sms unread thing still exists, but I'm using the pre-release/fixed 8sms app anyway, which is working well.

Any other common issues I can check out for people or report back on?
[Verizon Samsung Galaxy S 4] dmarden:
Important to keep in perspective that people without issues post far less than people with issues. Just like anything else in life, for the most part.

I have a Verizon S4 on the Verizon network. No issues with MMS/SMS, 3G/LTE, freezing or lockups, reboots, slowdowns, or anything else. My phone is extremely stable, runs great, and with the AVRCP fix... I have no more remaining issues.

This is not mean to minimize or devalue anyone else's struggles, but certainly the do not represent all of the CM S4 userbase.
[Verizon Samsung Galaxy S 4] FernBch:
What is the "AVRCP fix"?
[Verizon Samsung Galaxy S 4] dmarden:
https://jira.cyanogenmod.org/browse/CYAN-3154

http://review.cyanogenmod.org/#/c/61245/

It was merged for the 3/19 build and forward.
[Verizon Samsung Galaxy S 4] jkc120:
WeatherUpdateService wakelock is still there in 3/21 :(

I take it back. I am still having the WeatherUpdateService wakelock in 3/21 :(

I don't even have the lockscreen enabled, so I really don't know why it'd be causing a wakelock. I enabled slide lock, tapped on weather to bring it up, then quit out. And I think that stopped the wakelocks.

Anyone else seeing this?
[Verizon Samsung Galaxy S 4] jkc120:
Well, I think it was the lock screen weather widget, despite me not using the lock screen. So I tried:

- enable slide for lock screen

- change weather widget update period to manual

- disable weather widget

- disable lock screen

I'll see if I continue to see this wakelock or not. The two times it started and kept going today were when I went into a signal area where I dropped from LTE to 3g (or perhaps 1x or no data briefly). So that could be related.
[Verizon Samsung Galaxy S 4] swordmastr54:
I clean flashed the 19th build yesterday and I checked my wakelock and see no weather related stuff and I have it on my lockscreen and I go from lte to 3g anytime I'm at work.
[Verizon Samsung Galaxy S 4] jkc120:
Probably coincidence. Since I disabled the weather updates, haven't see. it.
[Verizon Samsung Galaxy S 4] Train88:
Hmm... Clean flash, latest nightly on vzw S4, nothing special like APNs added...I have no issues whatsoever
[Verizon Samsung Galaxy S 4] efaden:
Anyone have a fix for the not sending sms thing?
[Verizon Samsung Galaxy S 4] jkc120:
Haven't had that problem. What app are you using and what network are you on?
[Verizon Samsung Galaxy S 4] Kevin M:
Same issue. Take a look here. No solutions yet though.

http://xdaforums.com/showthread.php?t=2654822
[Verizon Samsung Galaxy S 4] jkc120:
Man that's a nasty bug. Sounds weird in that it happened to someone who hadn't touched their ROM at all out of the blue.
[Verizon Samsung Galaxy S 4] scarmon25:
You aren't using whisper push or have it enabled do you? I was having the weirdest text issue where it wouldn't send to the one person. Turned out it was that.
[Verizon Samsung Galaxy S 4] Kevin M:
It could be the old MJ7 (and MDK?) baseband no longer functions correctly? Trying to find things we all have in common.
[Verizon Samsung Galaxy S 4] heath2805:
Can't see how baseband would have an effect on texting. I always stick with MDK baseband since I have better signal with it. I've tried them all and always flash mdk radio/modems back.

Strange I had texting issues a while ago but now its gone. Not sure if its an area code problem or not. Mine is (717)

I'm on 3-22 build and so far its flawless.
[Verizon Samsung Galaxy S 4] efaden:
Nope... I was actually happy as a clam on 10.2... then WHAM... stopped working. CM 11 ... same thing.
[Verizon Samsung Galaxy S 4] scarmon25:
Well damn. Hate to hear that man. I know how annoying those issues like that can be.
[Verizon Samsung Galaxy S 4] Kevin M:
Here's a pretty good theory on the texting issue: http://xdaforums.com/showthread.php?t=2654822&page=18#post51307315
[Verizon Samsung Galaxy S 4] JaeKay:
Getting a calendar storage stopped error message on the latest nightly
[Verizon Samsung Galaxy S 4] dmarden:
I'm not saying anything there is outright false, but it at least isn't true for me. I didn't read that whole thread, but the post in questions seems to say it should be effecting everyone?

I have no texting issues.
[Verizon Samsung Galaxy S 4] jorceshaman:
I agree. And I like how it continues with "and now, onto speculation" when almost everything before that was speculation. Lol

I'm not having the issues either.
[Verizon Samsung Galaxy S 4] Kevin M:
It's the most comprehensive summation I've seen so far.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
The one thing he doesn't mention is that it seems to be isolated to some PA area codes, a few others in VA, and maybe some in other states but I can't remember.

In my opinion, any statement he makes saying Verizon is doing this on purpose to break custom ROMs is complete speculation. They close or ignore the tickets as they won't support modified phones...I'm no fan of Verizon but we really shouldn't expect them to.

I'm personally still convinced its a network change (not necessarily a wrong one) rolled out in the stated areas that surfaced a longtime bug in the CM codebase. Ever since i experienced the bug I've been running the custom Google Play Edition ROM with no issues.
[Verizon Samsung Galaxy S 4] Kevin M:
Definitely possible. I have an MD area code so that could be related.
[Verizon Samsung Galaxy S 4] samoid:
Yup, MD area code here too. Same issue.
[Verizon Samsung Galaxy S 4] asianrage:
I got this as well, but I was on Bluetooth. Same inactive dialer and all.
[Verizon Samsung Galaxy S 4] yooeee:
i'm a MD area code too, so that's three of us
[Verizon Samsung Galaxy S 4] bsimpson1:
I hope this is all just a strange coincidence. If not, I definitely won't be a Verizon customer anymore. The idea of a service-based company convinced they have the right to such precise control over how their services are used is absolutely ridiculous. Imagine a gas company intentionally engineering its product to fail when it's used in certain contexts.
[Verizon Samsung Galaxy S 4] jkc120:
While I doubt they're doing it purposely/maliciously, I also wouldn't put it past Verizon to pull some BS like that.
[Verizon Samsung Galaxy S 4] budies3:
Moving Files?

I did some searching around, and couldn't find really much, so here's my question. I go with nightlies, because I love to beta test:) As of almost 2 weeks ago, I can not get es file explorer to move files from either the phone to sd or vise versa. Is this just me, or does someone else know what this might be? Thanks for any help:)
[Verizon Samsung Galaxy S 4] jorceshaman:
I don't know about ES but Solid Explorer is working great for me. I've been able to move between the internal and micro SD as well as using the OTG cable to transfer to/from a full size SD using a USB adapter and 8, 16, and 64 GB flash drives.
[Verizon Samsung Galaxy S 4] griffsterb:
Thought I would chime in here to say that I am on 3/24 nightly and have had zero issues. SMS works fine although I am using Hangouts. Voice mail dial pad words, GPS lock, no freezing - overall working great.
[Verizon Samsung Galaxy S 4] budies3:
Moving Files

It looks like some how my sd card got set to read only? How does this happen? I guess I had better read on how to fix it....lol
[Verizon Samsung Galaxy S 4] yooeee:
You're lucky man. Hope it stays that way.
[Verizon Samsung Galaxy S 4] budies3:
May I ask why he's lucky?
[Verizon Samsung Galaxy S 4] yooeee:
You're lucky man. Hope it stays that way

Quoted the wrong person before
[Verizon Samsung Galaxy S 4] griffsterb:
Now I'm starting to see the unread SMS bug on Hangouts. So not so lucky anymore.
[Verizon Samsung Galaxy S 4] yooeee:
another member just told me their a MD area code also. also, I have a MD area code but am in Tucson, so I don't know if it a pure area code thing or towers
[Verizon Samsung Galaxy S 4] yevgenydev:
Doubt its an area code issue. I am in MD, but I have friends with VA codes having the same issue.

A temporary solution is to toggle Airplane Mode On, Then Off. This allows you enough time to send 1 txt.
[Verizon Samsung Galaxy S 4] yooeee:
Thanks, yeah, the airplane toggle is a temporary solution. also you can switch to 1x and things will send . I've read almost every forum here on this topic and almost everyone effected is central PA, Virginia and MD, some in Southern California. It could be that we're just all from those areas, but the point is no one knows the real issue, it's all speculation, so all we have is observation.
[Verizon Samsung Galaxy S 4] yooeee:
i was looking at the Verizon S3 page (http://xdaforums.com/showthread.php?t=2657822) on this issue and they were reporting that if you go back to stock and do a key code factory reset *2767*3855#, then made a nvbackup, it could fix it. I flashed back to MDK JB and the codes weren't working. Dug some more and found out how to enable hidden menus, but the factory reset / re-provisioning still doesn't work. Anyone have any idea of reprovisioning is possible from out end?
[Verizon Samsung Galaxy S 4] hlxanthus:
Anyone else have WiFi in their battery stats as always on even if its off ? I have noticed it on all ROMs I have tried lately, slim, PAC, and now cm11

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] BaronLager:
I can confirm that 3/26 eliminated the voicemail dial pad freezing.
[Verizon Samsung Galaxy S 4] jorceshaman:
I noticed that as well but since I'm still getting great battery life I didn't figure it was worth reporting.
[Verizon Samsung Galaxy S 4] yooeee:
In regards to the SMS sending fail issue, and subsequent conspiracy theories against Verizon

http://xdaforums.com/showthread.php?p=51384688

We found a possible fix by clean flashing GPE and configuring LTE from there. I think this forces the phone to be reprovisioned. My texts work on LTE and stick after multiple flashes and reboots on CM or CarbonRom

No clue on why this problem happened in the first place. Less likely a intentional move by Verizon, more likely a update on their end that unintentionally broke SMS. Either way, I'm the third to have confirmed fix. Just showing what I did and my results
[Verizon Samsung Galaxy S 4] Logano520:
My GPS has been working fine until today. For some reason today when I used it for navigation it sent me around the whole city and it didn't have any idea where I was going. Anybody else experience this in today's nightly?
[Verizon Samsung Galaxy S 4] asianrage:
Is your Location status set to Battery Saving or Device Only?
[Verizon Samsung Galaxy S 4] shortstuff_mt:
Have you gone into Settings->Wi-Fi->Advanced and unchecked "Scanning always available"?
[Verizon Samsung Galaxy S 4] BaronLager:
I installed today's nightly and don't have any issues with GPS.
[Verizon Samsung Galaxy S 4] ahoslc:
Saw this on another thread and so far 3 people have reported text working again so I thought id leave this here. I don't have the issue but figured id let you all know what's working for people.

1. Factory reset and wipe system

2. Flash the GPE rom

3. Send multiple texts and saw them go through

4. Rebooted & set hangouts to default (text still working)

5. Clean flash slim, cm11, or liquid smooth

6. Tested text and all is well.
[Verizon Samsung Galaxy S 4] yooeee:
Yep, and you can also do a nandroid backup restore after the GPE lash instead of a clean cm or other aosp rom
[Verizon Samsung Galaxy S 4] hlxanthus:
I have never had to adjust these settings previously . .

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] shortstuff_mt:
The default is to always allow WiFi to scan for available WiFi networks even when WiFi is turned off. That's been the default since Android 4.3...

http://www.androidpolice.com/2013/0...canning-unless-you-find-the-special-checkbox/
[Verizon Samsung Galaxy S 4] twiz0r:
Has anyone gotten Viper4Android to work recently. It's been a while since I have lol
[Verizon Samsung Galaxy S 4] hlxanthus:
I am well aware of this. Been part of android for a while now. But WiFi still shouldn't be reading as on all the time. It never did in the past

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] jorceshaman:
I never knew about this before. Thank you for the info!
[Verizon Samsung Galaxy S 4] jkc120:
I've had this 3 times now, two times back to back and once on an earlier build (3/17 I think): go to Google now (disabled, just doing a search) and start typing "weather" and get to weat and it locks up and the screen stops updating. If I turn the screen off, I can't get the screen to show anything else and a battery pull is my o my option. The long press power menu works but that's it.
[Verizon Samsung Galaxy S 4] Logano520:
Thanks for your response! I don't know what was going on yesterday, but I restarted my phone and the GPS (along with everything else) started working fine again.
[Verizon Samsung Galaxy S 4] civichater:
Loving this rom and battery seems Ok, but my phone had 100% awake and wake lock detector says it the Google calendar. Anyone have this? I am running PA gapps and ART
[Verizon Samsung Galaxy S 4] scarmon25:
I haven't had any wake lock a from calendar. Really haven't had any at all now that I think about it.
[Verizon Samsung Galaxy S 4] FernBch:
I've been using betterbatterystats to track battery usage, but it doesn't seem to be working like it should. I think I know why now.....
[Verizon Samsung Galaxy S 4] bakobitz:
CM11 vs. Gummy

Thinking of flashing this, and have had good experiences with CM in the past, but I'm enjoying Gummy's 4.4 rom, which seems relatively bug-free at this point.

Any benefits of this CM build over Gummy, from those who switched over?
[Verizon Samsung Galaxy S 4] OMsupp:
root access

did a clean install of cm11 and i opened up titanium backup and it's telling me my device is not rooted. i checked all my other apps and they said the same thing, including Root Checker. i have android debugging enabled, under root access i have it enabled for apps and adb. the first thing i did after flashing and setting up was install superSU and updated my binary... could that be the issue. im going to try uninstalling superSU, see if thats the problem.

tl;dr how come my device is "not rooted"
[Verizon Samsung Galaxy S 4] scarmon25:
Yeah. Don't flash any root package. Just flash cm and gapps
[Verizon Samsung Galaxy S 4] OMsupp:
ok superSU was the cause of my "device not rooted" smh
[Verizon Samsung Galaxy S 4] brizey:
What worked for me (on kk cm11, but this may work here, too):

Go into dev settings and toggle root access to apps (and abd if you are so inclined)

Go back to supersu and toggle root (disable then enable root)

Try to get root access in titanium again
[Verizon Samsung Galaxy S 4] ItsAaronR:
Good morning, I had a hangout yesterday and the other person couldn't hear me, has that happened with anyone else?

Thank you.
[Verizon Samsung Galaxy S 4] kholy:
Hi,

I don't post to often and i was having a hard time searching through all the pages so maybe this was already answered. With CM-11 12-12 my top notification is slightly cut off, and as its not a big issue it just seems like one of those little annoyances that i can most likely fix myself. Below is a screenshot of how it looks on my phone.

Thanks,

kholy
[Verizon Samsung Galaxy S 4] br125:
The wallpaper is not sized correctly. Change the wallpaper to something else, then back to the original one if you want to use the stock wallpaper and you'll see the transparent notification bar.
[Verizon Samsung Galaxy S 4] kholy:
This solved my issue

Thanks!
[Verizon Samsung Galaxy S 4] pandit1975:
SIP calls microphone and dialer mute.

Are SIP calls with native microphone working on this build?

Is mute button on regular calls working on this build?

I haven't found any rom that has both fixed. Anyone know a ROM that has both issues fixed?