yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] FernBch:
CM has addressed some of the SD card issues, but maybe not all. When I had the issue on 10 mine were on the SD, too.
[Verizon Samsung Galaxy S 4] fireattack7:
That's funny. The last time I was on CM10, it had the issues. I didn't have them on CM11, but now they are back with CM12.

I moved the ones I wanted to use to the internal storage and it seems to work.

Anyone have any issues with the volume not being as loud as it was on CM11?

---------- Post added at 05:41 PM ---------- Previous post was at 04:55 PM ----------

Also, on today's nightly (3-3), when rebooting I get a "System UI has Stopped" error. I have to flash back to 3-2 for it to go away.
[Verizon Samsung Galaxy S 4] snakecharmer23:
There are similar reports in the AT&T thread and international thread. Do use cyan delta? If so, try an install from the full zip.
[Verizon Samsung Galaxy S 4] fireattack7:
I tried downloading via the updater and downlaoding via my PC and transferring the file. Both I rebooted to recovery and installed.
[Verizon Samsung Galaxy S 4] fireattack7:
The latest nightly seems to run ok.

The custom sounds didn't stay when I flashed the latest nightly however. I had to copy them back to the internal storage, reset permissions, reboot, then reset them to where they go.
[Verizon Samsung Galaxy S 4] efaden:
Anyone ever seen an error about failed activation? My phone was working fine before switching to cm12 now I get an error and I can't get anything through cell/lte. Ideas?
[Verizon Samsung Galaxy S 4] yzf600:
Bluetooth woes

First off, I'd like to say thanks for all the hard work it took to get CM12 running so well on the S4. It's nice to be able to run a lean CM12 compared to the VZW bloated Touchwiz OS. I also enjoy being able to upgrade to the latest Android way before VZW gets around to qualifying the latest versions.

Don't take this as complaining, but I'm just wondering if the Bluetooth issues folks have been reporting for weeks are actually being looked into? I've been flashing the latest nightly at least once a week for a month hoping for a fix. No luck so far. I'd rather not go through the flash thrash unless I know it's being addressed.

ls there anything I can do to help get Bluetooth fixed? Would starting a bounty help get focus on it? I'd easily chip in at least $10. I'm not a newbie with GIT and android programming, but diving into the code and debugging intermittent bluetooth issues is above my current skill level.

Are my expectations are too high? I know 5.0 was a major change and it's been 4 months since it was released. Maybe CM12 support for the S4 is near end of life since it's an "older" device now. I could live without a working compass. I just want reliable Bluetooth connections again.
[Verizon Samsung Galaxy S 4] FernBch:
If it's something that has gotten worse file a report at JIRA. Make sure it includes a clear description of the issue and a logcat. If it is an issue that has been present since day one either wait for the first M release and post a bug report with a logcat or give a good description here with a logcat. A bounty is not needed and honestly the idea offends the devs.
[Verizon Samsung Galaxy S 4] andyc2d:
Is anyone else having issues with today's nightly getting mobile data to work. I can't get it to work but if I restore to my backup from 2/22 or factory it works fine.
[Verizon Samsung Galaxy S 4] lx1907:
Looks ok to me, but just did a quick test as I've been home most day today.

I seem to have issues with smart lock based on geo tho. I think it broke for me on previous flash (2/25 ish).
[Verizon Samsung Galaxy S 4] rajones19:
YES. I have been dirty flashing for awhile, but this morning decided to wipe and clean flash the 3/4 build, which is the most recent I see available on the site. No mobile data whatsoever. I was on 3/4 before, but had flashed up to it over previous builds. I am just remembering now, I ran into this back about February 22 or thereabouts; I had to restore a 2/19 build, and flash over that, because no mobile data. I forgot all about it until this morning. Definitely something amiss.
[Verizon Samsung Galaxy S 4] andyc2d:
Thank God I'm not the only one! I was starting to worry that I was having a hardware issue. I've tried setting back to factory, refreshing and changing APN settings, toggling airplane mode, flashing different modems, everything I can think of nothing works. If I'm running my 2/22 backup or touchwiz it works beautifully, though. I'll attach a logcat.
[Verizon Samsung Galaxy S 4] rajones19:
Definitely not the only one. Seemed odd to me, though - I can dirty flash all the builds up to 3/4, and it works no problem - but if I clean flash anything after about 2/22, I am screwed. I also tried everything. Thank God for nandroids!
[Verizon Samsung Galaxy S 4] eikoo:
Clean install of today's build works fine
[Verizon Samsung Galaxy S 4] FernBch:
Flashed today's build a few moments ago. All was fine until my GS4 went to sleep. Upon waking it the screen has this yellowish tint that I just can't seem to get rid of. Logcat attached.

https://www.dropbox.com/s/kovxu4jjyz4w8iv/Log_2015-03-08_21-09-52.txt?dl=0
[Verizon Samsung Galaxy S 4] .Ejekt:
On 3/8; dirtied from last Sunday - all systems go.

---------- Post added at 10:33 AM ---------- Previous post was at 09:47 AM ----------

The display issue definitely seems to be tied to the LiveDisplay implementation. Too bad there's no option to disable it yet.
[Verizon Samsung Galaxy S 4] FernBch:
That's what I figured. Once it is enabled the only way to undo it (for me) was restore my nandroid and reflash then don't enable the new display feature.
[Verizon Samsung Galaxy S 4] .Ejekt:
Still on 3/8, geting full lockups/restarts when trying to make calls. Gonna flash whatever is new and see if it's fixed.
[Verizon Samsung Galaxy S 4] vanberge:
I just clean flashed 3/10 and I feel like I have that yellow tinge that Fern mentioned earlier.

I'll run for a bit and see how she acts.

Edit.....

I don't think that yellowish tint is a bug actually. If you go into display settings, check out the adaptive brightness and liveDisplay color temperature.
[Verizon Samsung Galaxy S 4] .Ejekt:
Yellow tint is definitely still present on 3/10.
[Verizon Samsung Galaxy S 4] vanberge:
Try disabling adaptive brightness... Mine looks way better after that
[Verizon Samsung Galaxy S 4] .Ejekt:
Okay, this is bad. Hopefully someone else is getting this issue with the past few builds. My in call audio gets disabled when the screen turns off. As in, when I bring the phone to my ear and the screen automatically turns off, so does the audio. There's also considerable lag in the Phone app. It's completely unusable.
[Verizon Samsung Galaxy S 4] rajones19:
Same here - and restoring 3/8, dirty flashing to 3/10 as FernBch suggested did not help in my case. Going to restore back to 3/8 again and sit tight. One good thing - when I clean flashed 3/10, I did have mobile data. Clean flashing any of the builds from about 2/22 to 3/8 I could not get mobile data.
[Verizon Samsung Galaxy S 4] .Ejekt:
I actually found that changing the APN settings to:

MMSC to*http://mms.vtext.com/servlets/mms

MMS Port to 80

APN Type to default,supl,mms​

fixed the data issue.​
[Verizon Samsung Galaxy S 4] vanberge:
If the yellow tint is the only thing holding you back, you can either disable adaptive brightness or change the color temperature under the live display.

I messed around with the settings in there and got it to something i'm satisfied with. 3/10 clean flash no phone audio issues here.
[Verizon Samsung Galaxy S 4] .Ejekt:
Back on 3/4, still getting unacceptably heavy lag when placing a call. No idea why I'm only noticing this issue now.
[Verizon Samsung Galaxy S 4] musicfreak190:
Kind of off topic but I can't wait for 5.1 source to be dropped and CM12 to update it's base!
[Verizon Samsung Galaxy S 4] traco1:
Official like OTA

From the videos I've seen the OTA lollipop has the screen backgound in the app drawer not white. All the videos I've seen for this rom shows a white app background. Is it interchangeable? If not I would not touy it as OTA.
[Verizon Samsung Galaxy S 4] traco1:
Maybe I should back track. I was reading an article in "TrueAndroid" that refers to the ROM as OTA but doesn 't specifically say so.

Sorry.

But can this ROM be used on my s4 without major problems?
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 3/11. All seems good so far with the exception of the color bug. I turned adaptive backlighting off, set my daytime color temp to 9000K, and slid the brightness slider all the way left. I can accept the view right now. It's actually pretty good until the devs sort it out.
[Verizon Samsung Galaxy S 4] vanberge:
I'm confident that I got the wierd yellowish tinted color back to "stock". Here are my settings:

Adaptive Brightness: Enabled

LiveDisplay: Display mode - Automatic

LiveDisplay: Color Temperature - 6500k day/4500k night (stock, I believe)

LiveDisplay: Color Calibration - Set all colors to 55%, vs their default of 100.
[Verizon Samsung Galaxy S 4] .Ejekt:
You're a ****ing rock star.
[Verizon Samsung Galaxy S 4] Triscuit:
Awesome, worked for me!
[Verizon Samsung Galaxy S 4] phonedawg:
much better. Thanks
[Verizon Samsung Galaxy S 4] phonedawg:
anyone getting the nexus 6 releasing this week? I want to get it except it is slightly(0.25 inches) too big for one handed use. Note 4 and iphone 6 plus seem to be the limits for max phone size for one handed use.
[Verizon Samsung Galaxy S 4] indolent:
Thanks, this seems to have worked for the color. But, for me, the max brightness seems worse. It made it harder to see the screen in the sun.
[Verizon Samsung Galaxy S 4] phonedawg:
latest nightlies let you disable livedisplay. I did that.
[Verizon Samsung Galaxy S 4] Nydalxy:
How stable have the latest nightlies been? I've been on 1-23 and it's starting to give me a lot of issues with freeze ups and crashes. I'm looking to clean flash today
[Verizon Samsung Galaxy S 4] phonedawg:
03/14 has been good.
[Verizon Samsung Galaxy S 4] griffsterb:
Since coming to lollipop I've had some recurring issues... battery drain (only at night somehow) and my GPS will not work with tracking apps (SportsTracker). Although, I'm still on 2/16...

Overall how are the newer Nightlies? I'm thinking of going back to 4.4, I believe I had been using a build from late summer 2014 and it was flawless.
[Verizon Samsung Galaxy S 4] phonedawg:
03/14 has been flawless. The only issue is that I have been experiencing accelerated battery drain during use on lollipop. I think this is probably due to the manual brightness level setting.

The automatic brightness adjustments made by 'adaptive brightness' are limited by the brightness level setting on your phone and the entire brightness range that the phone display is capable of is not used. Therefore, I think this new brightness management is less energy efficient.
[Verizon Samsung Galaxy S 4] indolent:
I wouldn't go so far as to say it is flawless, but it is pretty good. I have had really good battery life, with no excessive drain for a while now. My main issue is bluetooth share errors still happen quite often, requiring cycling bluetooth off and on again. GPS has been working fine for me with no issues.

My other issue isn't against CM, but how lollipop manages brightness settings. The auto brightness used to just work without me ever having do anything with it. With how it handles brightness now, I find myself having to manually adjust it all the time when I'm in a dark room or in sunlight. I feel it is a step backwards in usability.
[Verizon Samsung Galaxy S 4] griffsterb:
I just dirty flashed 3/18 and GPS still won't track for me within an app. It finds my location but it won't move. I'll have to test later today in the car and see if Maps turn by turn works.
[Verizon Samsung Galaxy S 4] doubleflusher:
I've been getting an SMS error since the 3/12 nightly.

Anytime I open up the native messaging app, I get an error "Message not sent" "Touch to review the message and try again"

All of my messages have been sent successfully, yet I get this error message.

When I touch to review, it brings up a blank message, without a recipient.

Clearing cache and/or data has no effect.

Is anyone else experiencing this, or have they in the past? It's rather annoying.

Is there something else I can do?

Thanks in advance.
[Verizon Samsung Galaxy S 4] phonedawg:
I have not had any GPS issues. Try checking with https://play.google.com/store/apps/details?id=com.chartcross.gpstest&hl=en
[Verizon Samsung Galaxy S 4] griffsterb:
Oy... app just displays "No Fix" when my GPS is turned on. 3/18 nightly. Any ideas? Wonder if I should just flash back to an older release.
[Verizon Samsung Galaxy S 4] phonedawg:
I remember some people posting about similar issues in the thread. I think they had to go back to touchwiz and come back to CM to get a GPS lock. Search this thread to be sure.
[Verizon Samsung Galaxy S 4] FernBch:
I'm running 3/17 and see this, too. For me the issue is tied to when I receive a group SMS (group SMS has a bug, too). Once I reboot the error message goes away.
[Verizon Samsung Galaxy S 4] checho408:
I flashed back to Carbon Rom 4.4 locked on gps and Restored CM12 it fixed it for me.
[Verizon Samsung Galaxy S 4] doubleflusher:
I deleted all of my messages, cleared app data and cache. Then I rebooted my Phone.

The issue persists.

I am able to send messages. It's just that the error message is annoying.

Thanks
[Verizon Samsung Galaxy S 4] Alarbus:
I ordered a nexus 6 from Motorola two months ago to use on Verizon. You get used to the size after a week or two, now the S4 feels tiny. Some stuff is hard to do one handed, but the curved back makes two handed use really comfortable.

There was a brief run of CM nightlies for the nexus 6 that would flash the old bootloader over the 5.1 version, which resulted in a brick. Abhisek even deliberately bricked his in testing. Those nightlies were removed, and it's been corrected in the new ones.

Regarding the messaging thing - it's something with CM's messaging app, it started in mid-February. It did it to me on the nexus 6 and the S4, using Google's messenger app avoids it, once you blow away the local message database. Hangouts also avoids it, if you'd rather go that route. Clearing app data doesn't really do it, the db to delete is in data/data/com.android.providers.telephony/databases if you're rooted.

It took me several wipe and restores to figure that part out, what a pain in the ass.
[Verizon Samsung Galaxy S 4] riphamilton:
try downloading an older version of handcent (i use 5.9.1 for this issue). i'm not sure of exact instructions, but [temporarily] enable handcent as the default SMS app, and then go into the outbox/unsent folder. there should be a message sitting in there which is causing your error. delete that message, and you're all set. just go back and set your preferred SMS app back to the default.
[Verizon Samsung Galaxy S 4] doubleflusher:
This, plus rebooting, has worked so far.

Thank to everyone for their help.
[Verizon Samsung Galaxy S 4] phonedawg:
I was searching the GPE ROM thread and found this post. It seemed like it might help. Once again, thanks for your time and effort.
[Verizon Samsung Galaxy S 4] FernBch:
I have created a report over at JIRA regarding the SMS not sent error. Maybe it will help it get fixed. For me it comes back no matter what I do. When it does come back I just swipe the message away from the pull down it I won't see it for a while.
[Verizon Samsung Galaxy S 4] phonedawg:
How much screen-on time does your phone report before one full charged battery gets discharged?
[Verizon Samsung Galaxy S 4] FernBch:
If I go 12-14 hours between charges I get around 3 to 3-1/2 on the avg.
[Verizon Samsung Galaxy S 4] phonedawg:
I am getting about the same. I remember getting over 4 hours of screen-on time on 4.x. That said, this is not too bad.

However, I think batteries should last much longer so that I can use my phone generously without worrying about battery.
[Verizon Samsung Galaxy S 4] FernBch:
If I understood what I have read recently correctly 5.1 is supposed to address some issues, including battery life. Just have to wait for it to get merged.
[Verizon Samsung Galaxy S 4] fireattack7:
Has the issue with custom sounds being on the SD card been fixed? Mainly, if you have a custom sound set that is stored on the SD card, it defaults back to a tone that is built into CM.

I like CM12, except for this issue. I know it was fixed in CM11 very early. I'm hoping it gets fixed in CM 12.
[Verizon Samsung Galaxy S 4] .Ejekt:
Nuts. GPS isn't working. I've been flashing nightlies for a while but only just tried using GPS yesterday. I get a lock but I lose a signal shortly after Maps starts running. Anyone know for certain that GPS is working in the latest builds?
[Verizon Samsung Galaxy S 4] Hawksfire:
I have heard lots of "solutions" to this problem, but none of the easy ones worked for me. To fix it I had to clean flash CM11, went in and made sure I actually had GPS lock, then I dirty flashed CM12 over it. I used an app mentioned earlier in this thread called GPS Test to make sure it was actually working. The app took a few minutes to confirm I had a lock. Now my GPS is working perfectly, but it was a hassle.
[Verizon Samsung Galaxy S 4] FernBch:
GPS has been an issue since CM11 did the big kernel revamp last August. The compass has also been screwy since then (orientation is off by 180° and many third party apps that use the compass don't work 100%). Last I heard the devs were looking into it and know it has something to do with the kernel and how it doesn't initialize something but that's all I know.

Also, currently on CM12, there is a bug in the messaging app that causes an error to pop up when a SMS is sent or received. The messages send and receive ok but the error pops up anyway.

There is also a bug in group messaging. If you get a group message AND have an individual message from someone in the group it will mark them as unread until you send/receive a message to/from the individual.

I have also been experiencing issues connecting to saved WiFi networks. When I come into range of one it usually will not auto connect. Toggling the tile does nothing. When you go into WiFi settings it will show the network in question as having an "authentication problem". Manually connecting from there works every time.

The latest "live display" additions also needs some tweaking. Brightness settings below 50% don't work well, if at all, and until you find the right settings you may have a yellowish tint to your display (that work around is posted a few pages back).
[Verizon Samsung Galaxy S 4] phonedawg:
It might be a good idea to make the jump to moto x or nexus because CM started distancing itself from google. I have been using the S4 because it can run CM. I have been using CM because it was nexus like with minimal and useful-customization capabilities. Now that it has been announced that CM will fork AOSP and install non-google services, I dont think I want to be using it anymore.

Nexus-6 with the Xposed module Gravitybox will give you everything that CM has been offering.
[Verizon Samsung Galaxy S 4] riphamilton:
i've been experiencing this on CM11 for months. not super annoying, but an obvious bug that hopefully gets squashed at some point.
[Verizon Samsung Galaxy S 4] FernBch:
I'm waiting for the first "M" release cause there's a couple things I've noticed that don't fall under the "Nightly Regressions" category.
[Verizon Samsung Galaxy S 4] focus242:
Please fix the BT issues.
[Verizon Samsung Galaxy S 4] phonedawg:
Whom is this directed to?
[Verizon Samsung Galaxy S 4] .Ejekt:
So, I'm wondering if anyone has been keeping track. When was the last build that any user is certain they had everything (aside from the compass) functioning properly? Last I can remember was before the addition of the Live Display functions, but I never marked my calendar :P
[Verizon Samsung Galaxy S 4] FernBch:
It's been at least 3-4 weeks. The BT Share FC started around the end of February and the screen tint showed up before Live display was introduced.
[Verizon Samsung Galaxy S 4] .Ejekt:
Haha, damn. CM12's getting somewhat bloated. Would be nice if the devs stopped adding features and focused on fixes. :good:
[Verizon Samsung Galaxy S 4] FernBch:
Agreed. Although I'm not sure what the future may hold if they ditch Google, or so I have heard.
[Verizon Samsung Galaxy S 4] FernBch:
Just noticed something with CM earlier today. I decided to go into the live display and reset everything with color correction to default. I have yet to see the yellowish tint return. I have noticed that the brightness slider still does not work below 50%.
[Verizon Samsung Galaxy S 4] iamjerry123:
I'm sorry for such a noob question, but how do I get Google Play Store? I went onto http://wiki.cyanogenmod.org/w/Google_Apps and downloaded their CM 12 package, went onto TWRP and installed it. When I booted my phone again, it kept saying that ALL the Google apps were crashing. Can someone shed some light?

Thank you,

Jerry
[Verizon Samsung Galaxy S 4] FernBch:
Find the Paranoid Android Gapps thread. The OP has links to all the flavors of Gapps packages from full (everything) to micro mini (minimal) and everything in between. Boot into recovery, wipe cache and davlik, flash, reboot, and enjoy.
[Verizon Samsung Galaxy S 4] iamjerry123:
I went onto http://xdaforums.com/showthread.php?t=2397942, and http://xdaforums.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900 but he closed it... Can someone repost a link? :/

EDIT:

http://d-h.st/users/TKruzze/?fld_id=44393#files

Found it! Available until 3/31!
[Verizon Samsung Galaxy S 4] FernBch:
Ninja'd lol. I use this, PA micro mini and just add what I use.

https://www.dropbox.com/s/ul2drwgxq61j7z6/pa_gapps-micro-5.0-ALPHA1-20141117a-signed.zip?dl=0
[Verizon Samsung Galaxy S 4] fernandw:
Battery Drain

Anyone see significant battery drain over the last few days? From 98% to 2-3% in a 4-5 hours.

I'm still running 2/8 and haven't taken a nightly since I got my GPS and compass working. MMS is also working well and I didn't want to take a step back. It looks like it may be Google+ but I am not sure. Any insight?

Wade
[Verizon Samsung Galaxy S 4] rajones19:
What did you do to get your compass working?
[Verizon Samsung Galaxy S 4] phonedawg:
I am not seeing any battery drain. View your battery usage and see which app is causing the drain
[Verizon Samsung Galaxy S 4] d33dvb:
so bummed i bought a locked bootloader version.
[Verizon Samsung Galaxy S 4] kd-:
Cross-posting from another AOSP-based thread since I think it's of interest here as well. Regarding the Bluetooth Share FC issues, I've captured a "bug report" which looks like it has a logcat and a dump of the dmesg output, among other things. If any devs think it would help them out, shoot me a PM and I'll send it your way.
[Verizon Samsung Galaxy S 4] lnxus:
MMS half working

Anyone else have issues with MMS failing to work after a while? MMS messages don't come in (no notification) and they hang while going out. It doesn't seem to matter what app is used, even stock messaging. Upon reboot of the phone, MMS messages that had been sent come in almost immediately. A few days later the problem returns and requires another reboot.

I've messed with APN settings per suggestions in this thread to no avail.

Any ideas?
[Verizon Samsung Galaxy S 4] .Ejekt:
I went all the way back to 3/12. I've clean flashed up to 3/22 and still no GPS. Seems like it's been broken for a while now.
[Verizon Samsung Galaxy S 4] lnxus:
I'm running 03/25 with no GPS issues. Clean flash wasn't enough for me - I ended up flashing a TW based ROM, locking GPS, then clean flashing CM12 and it started working for me. I know it's a ton of work, but give it a shot.
[Verizon Samsung Galaxy S 4] .Ejekt:
It's also been suggested that I flash a CM11 beforehand to fix the GPS, so that's not a surprise. Which TW ROM did you use? I'll try both methods tonight and see if I have any luck.
[Verizon Samsung Galaxy S 4] lnxus:
I don't remember 100%, but I think I used Hyperdrive
[Verizon Samsung Galaxy S 4] FernBch:
I have a stock MDK nandroid for those occasions.