yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] :
Gapps Not Responding

I have been trying to get this rom to work for a few days now. The latest version I have installed in the 1/15 nightly build. The Rom installs fine, and without gapps it runs perfectly. The problem is that I obviously need gapps installed in order to get many standard features.

I have tried multiple different LP gapps packages, both downloaded from my PC, and directly to my phone. None of them seem to work. They install fine, but as soon as I boot the phone, I am getting "Unfortunatly, Google Play services has stopped." over and over again. This happens with any gapps package I install.

Any help would be greatly appreciated as my phone has been unusable for almost a week. I just dont understand what is going wrong everytime I install Google Apps Package.
[Verizon Samsung Galaxy S 4] JadedRedDragon:
[MENTION=5424488]DeeeM508[/MENTION], are you using the PA Google apps linked by OP? I am using PA Pico which works like a charm. I tried PA stock and it fails to flash.
[Verizon Samsung Galaxy S 4] FernBch:
My Gapps flavor of choice is the modular mini, also works like a charm.
[Verizon Samsung Galaxy S 4] :
Yes I have tried the Pico, Mini, Full, I have even tried Gapps from euroskank and basketbuild. None of the zips fail to flash though. They all flash fine, I wipe cache and dalvik, reboot, and then get unending error messages about google play services stopping.
[Verizon Samsung Galaxy S 4] bswides412:
Have you tried wiping internal storage under advanced wipe settings in TWRP? There may be some lingering old app data between installs. If you do this, beware that it will wipe EVERYTHING on your internal memory including pictures, ROM backups, etc. I know Dan recommended it in his GPE thread a couple of weeks ago. Just be sure to back up!
[Verizon Samsung Galaxy S 4] dansan382:
have you updated to the latest version of TWRP?
[Verizon Samsung Galaxy S 4] Nydalxy:
So are the current nightlies dd worthy? I need wifi, bluetooth and gps to work. Thanks
[Verizon Samsung Galaxy S 4] bswides412:
From the sounds of it, people seem to be having the most success with the 1/11 build in terms of stability and reliability.
[Verizon Samsung Galaxy S 4] :
I actually have. Every time i try a new install I completely wipe the phone using the advanced wipe in TWRP and wipe everything but my external SD card. Thanks for trying though.

I am on version 2.6.3.0. It is not the latest but not too old either. Do you think that might be the issue? I will update and see if that helps. Thanks for troubleshooting with me guys!
[Verizon Samsung Galaxy S 4] Alarbus:
Yeah, Jenkins is the build bot, and it seems to be rather broken.
[Verizon Samsung Galaxy S 4] Alarbus:
Something with Jenkins is still not right, it seems to require specific access to view build progress, but it IS working, and there's a 1/18 jfltevzw build up. And somewhere in there they fixed the cmupdater, I was able to download and update it from the phone, rather than downloading on the desktop and manually flashing.
[Verizon Samsung Galaxy S 4] :
I feel like it's a bug with the newly implemented them engine, but does anybody know a way to change the lock screen background?
[Verizon Samsung Galaxy S 4] vanberge:
Clean flashed 1/18 and I can't change keyboard due to settings fc
[Verizon Samsung Galaxy S 4] drt054:
I dirty flashed and did the same thing when Choose Keyboard is pressed.
[Verizon Samsung Galaxy S 4] FernBch:
Same here.

On a side note. Does anyone have any idea if CWM is gonna get updated to work with Lollipop? I've tried TWRP but not Philz. I am just use to CWM and keep wanting to go back with it.
[Verizon Samsung Galaxy S 4] Nydalxy:
Is there a way around it to change your keyboard at all? I was about to flash the new nightly but being without SwiftKey is a deal breaker for me
[Verizon Samsung Galaxy S 4] vanberge:
I can't find a way to. Stuck on aosp keyboard
[Verizon Samsung Galaxy S 4] Nydalxy:
Damn, thanks. I'll probably just flash the 1/11 build
[Verizon Samsung Galaxy S 4] drt054:
Disregard :P
[Verizon Samsung Galaxy S 4] vanberge:
Dirtied 1/19, the keyboard settings FC are still happening. Can't change away from AOSP keyboard.
[Verizon Samsung Galaxy S 4] gonzlobo:
As a last resort, you might try freezing the AOSP keyboard with tibu.
[Verizon Samsung Galaxy S 4] vanberge:
No luck... Good idea though. Left me with only voice input
[Verizon Samsung Galaxy S 4] crossen0:
I was unsuccessful in getting anything to work as well. I flashed skank's 1/19 build over 1/19 and have had no problems.
[Verizon Samsung Galaxy S 4] vanberge:
Dirty flashed 1/20 and keyboard settings/changes work now
[Verizon Samsung Galaxy S 4] FernBch:
Confirmed working.

Now just have to go through the settings and find where to turn lockscreen weather off. Lol
[Verizon Samsung Galaxy S 4] phonedawg:
is 01/20 all good?
[Verizon Samsung Galaxy S 4] vanberge:
Seems good to me so far
[Verizon Samsung Galaxy S 4] FernBch:
Been good all day for me.
[Verizon Samsung Galaxy S 4] jackburnt:
Clean flashed today's and I lost both my home button and notifications, then I tried to clean flash Skank's with the same results. Anyone else have similar issue?

I just restored a backup and it's working again, so it's definitely something in the flashing and not hardware.
[Verizon Samsung Galaxy S 4] kingramon0:
Dirty Flashed

I just dirty flashed 1/20 over a later nightly of CM11.

The first attempt didn't work (all apps kept crashing). Then I updated to the latest CWM Recovery and tried again (after a restore). Apps don't crash anymore, I can access the Internet and make calls. I still need to test Bluetooth. On the upside, I was having trouble with the proximity sensor before such that I could not get the screen to come back on during a call to use the number pad. Now, I can press the home button to turn the screen back on and go back to the phone app to use the number pad, so that's some progress.

So far it's going okay, but Holy Battery Drain, Batman! "Miscellaneous" is using up battery at twice the normal rate. I'm going to fully charge, reboot, and try not to start any apps to get a baseline on battery usage.
[Verizon Samsung Galaxy S 4] doubleflusher:
I just clean flashed 1/20 and lost root.

I'm coming from CM11 1/18.

I have a nandroid, so it's not that big of a deal to go back to 1/18.

Is there a quick fix, or do I need to root again?

---------- Post added at 02:58 PM ---------- Previous post was at 02:50 PM ----------

Nevermind.

I had a brainfart.

I installed SuperSU and all is well in the world.
[Verizon Samsung Galaxy S 4] rajones19:
A few builds back, they added an option in Developer Settings to turn root off/on. I found this out the hard way after doing exactly what you just described.
[Verizon Samsung Galaxy S 4] FernBch:
When you say latest CWM is it newer than 6.0.5.0? Is so, where did you get it?
[Verizon Samsung Galaxy S 4] kingramon0:
Maybe not the newest, after all. It is only 6.0.4.7, but it was good enough.
[Verizon Samsung Galaxy S 4] FernBch:
I have verified that there is a bug in messaging/group messaging.

If you send a text to person A, B or C, then send a group text to person A, B, and C it goes through fine. The bug shows up when one of the group recipients send a reply. The reply shows up in the group message and any individual message from one of the recipients is marked as unread. The individual messages will remain marked as unread until a message is sent to or received from the individual regardless of it being read beforehand or not.

Hope that made sense.
[Verizon Samsung Galaxy S 4] :
I think this has been a bug for awhile. I remember it happening in cm11. It was mostly the reason I stopped using the stock messaging app.
[Verizon Samsung Galaxy S 4] kingramon0:
Battery

My battery usage seems to be back to, what I consider, normal. By the end of the day it should be at close to 50% charge.

Looks like a decent DD for now.
[Verizon Samsung Galaxy S 4] FernBch:
I must agree. Battery life has been good. My personal best is 38 hours between charges.
[Verizon Samsung Galaxy S 4] crossen0:
If I didn't have problems with BT as much as I seem to I'd say it's pretty solid as is.
[Verizon Samsung Galaxy S 4] natec003:
Are you getting force closes when connected? I did for the first day... I used titanium backup to clear cache for Bluetooth share, then rebooted immediately. I haven't had any issues today with 1.5 hours streaming music in my car.

Sent from my S4
[Verizon Samsung Galaxy S 4] kingramon0:
Lock Screen

I'm a little disappointed with the new lock screen. It looks and feels good, but I can no longer set my phone to vibrate by long-pressing the home button on the lock screen, and I can't launch commonly used apps with the circle launcher thingy.
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 1/23. So far so good. The severe lag and UI freezes seem better, but time will tell. Only been on it about an hour or so.
[Verizon Samsung Galaxy S 4] SinfulRoad:
So, what's the consensus so far? Is it stable enough for daily use? And how is Bluetooth and GPS doing so far? Need those desperately.

Sent from my Cyanogenified S4.
[Verizon Samsung Galaxy S 4] FernBch:
I have DD since initial release. BT has been good for me. As for GPS it work flawlessly (for me) when used with navigation. The issue is with any app (like geocache) where the compass is used when walking. When driving orientation is computed via GPS sats and direction of travel, so it works as it should. Behavior is basically the same as with CM11.
[Verizon Samsung Galaxy S 4] drt054:
GPS stinks for me.. I had to go to the GPE-ROM for now.
[Verizon Samsung Galaxy S 4] crossen0:
I always get a lock on whatever ROM I'm running right before booting recovery to flash another. No issues whatsoever.
[Verizon Samsung Galaxy S 4] drt054:
My fault, I was like 3 baseband version behind. I will flash CM12 and see if it fixes it
[Verizon Samsung Galaxy S 4] FernBch:
1/24 is up and running. New boot ani (previous is better), new status bar mods, and CyanogenMod account has been reintroduced. Since 1/23 the lag seems much better. I know a commit was merged to address a race condition in 1/23.
[Verizon Samsung Galaxy S 4] drt054:
Flashed 1/24 and can't get gps again??? :(
[Verizon Samsung Galaxy S 4] Outlaw08Torn:
I'm currently on 1/23 and I have been having gps issues for the past few nightlies too. Everything works great and it locks onto my current starting location but then it doesn't move from there as I'm going down the road. I may give a clean install a go tomorrow.
[Verizon Samsung Galaxy S 4] FernBch:
On 1/24. GPS locks in moments but, as expected, the compass is off by 180°.
[Verizon Samsung Galaxy S 4] mirceab:
GPS is working for me too just fine on 1/24. The compass has been messed up for a long time, I don't even care about it anymore.
[Verizon Samsung Galaxy S 4] FernBch:
Yeah, compass has been hosed for a while but I still wish someone would fix it so it works as it should. Then my third party apps that rely on it would work right.
[Verizon Samsung Galaxy S 4] drt054:
I have used all of the tricks that I'm aware of. Copied the GPS.conf from the GPE ROM, got a lock on the GPE ROM then restored cm12 and nothing. Used GPS status & toolbox.. Nothing. Any other tricks I am missing? [MENTION=2385005]invisiblek[/MENTION]
[Verizon Samsung Galaxy S 4] thorrules:
Is there a way to change the notification weather units to Celsius? Btw, awesome job on this ROM
[Verizon Samsung Galaxy S 4] FernBch:
The ability to change settings or turn off lockscreen weather hasn't been merged yet. It's still a WIP.

---------- Post added at 02:38 PM ---------- Previous post was at 01:58 PM ----------

I just noticed weather is not on the lockscreen on 1/25.
[Verizon Samsung Galaxy S 4] rajones19:
Funny, I just noticed the exact same thing, and was about to wipe/clean flash to see if that fixed it. I guess I will not bother with that now, since everything else seems to be working fine (except the compass, of course!) .
[Verizon Samsung Galaxy S 4] phonedawg:
the compass can be fixed. Otherwise, it would not be working on 3rd party kernels with CM11.

Maybe, we should start a bounty.
[Verizon Samsung Galaxy S 4] rajones19:
That has always been my assumption, also, but it's been a long time now and no sign of progress. And as the saying goes, you know what happens when you assume ....
[Verizon Samsung Galaxy S 4] Loop4zil:
Mystery Unlock sound

There is a sound that is playing when ever I unlock the device. Not the normal 'tick' sound that can be enable and disabled on the Sounds>other sounds>lockscreen sounds toggle

I cannot figure out how to stop from playing...other than silencing my phone. Also, I went thru all of the notification sounds and could not find it either.

Are any of you experiencing the same thing?

1/23 Nightly - CM Kernel - google launcher
[Verizon Samsung Galaxy S 4] phonedawg:
I am willing to start a bounty with $50 for the compass. Anyone interested to chip in? If people join me, we can go ahead
[Verizon Samsung Galaxy S 4] carlbettag:
Well, seems like it may depend on your phone. Obviously, some people seem to be using it as their DD. However, did not work on my phone. I wiped completely & clean installed 1/21 and the PA GAPPS package. The new OS is great - love the interface. However, I had major problems (see below) which rendered it unusable & went back to CM11 M12 snapshot. Problems:

1. Mega battery drain - was getting less than 6 hours from a full charge. Battery was being drained by 'Misc' (??). Drain was constant & ongoing. Possible I could have debugged it; did not spend much effort on this due to complication 2.

2. Unstable phone & data connections. On M12 I have zero problems with reception (data & voice) & roaming. But after installing CM12 1/21 my connection was non-existent / unstable as I traveled outside SF up to Tahoe for the weekend. Again, possible I could have fixed this but in combination with the unusable battery life decided that reverting was in my best interests.

Taken in combination, the above problems made CM12 unusable for my phone at the moment.

That having been said, I will definitely keep my eyes open for CM 12 M1 & beyond, because the actual OS interface improvements were substantial and I'm really looking forward to the Android 5.0 upgrade.

Your mileage may vary.
[Verizon Samsung Galaxy S 4] invisiblek:
A bounty is absolutely not necessary. If someone would care to point me in the direction of a kernel that this is working on, I'd be happy to take a look into it.
[Verizon Samsung Galaxy S 4] rajones19:
The last time the compass worked correctly for me was on CM11 M9, build 08/04, using Faux123's kernel - faux123-018u. Compass was working on CM10, broken on CM11 unless you replaced the kernel. Functionally was permanently broken when the change was made that disallowed 3rd party kernels in August of last year. I still have that kernel, if it would be of help to you.

The compass appears to work when you are moving, since the GPS actually provides directional data when in motion. When you are standing still, relying on the magnetic sensor for directional data, that is when the problem begins. Compass apps like GPS Status and Toolbox report compass headings in any number of directions, none of which are correct. The directional data provided to other apps that access the compass - the geocaching app, for example, or any of the astronomy apps like Google Sky, is always 180 degrees off. If this was ever fixed, I would be the happiest man in southeast Michigan :)

In any case, thanks for all you do. It is much appreciated.
[Verizon Samsung Galaxy S 4] FernBch:
Now we're talkin, rajones has pretty much summed the issue up. Now the question is to find something it works with. I hae never used a 3rd party kernel with CM. Mainly because the devs have asked us not to report issues if you are using one. I did report it as an issue under nightly regressions with CM11 and to my knowledge it is still open.

Does anyone know of a CM12 kernel that has working compass. I don't believe it works on KT's. I have also heard of Alucard? and one or two others. I have not tried them and am not sure if they are current.

I was playing around with a couple apps today. GPS Toolbox seems like it wants to show proper orientation but I don't know if I can trust it. I guess I need to see. My Geocache app also looked like it wanted to work, for about 15 seconds, then it went all screwy. I may mess around and see if I can repeat it. I have been messing with the compass for about a week now. Recently, depending on which nightly it is, GPS status will show proper orientation when stationary. Today on 1/27 it seems like it's trying to work.

My personal feeling is it has something to do with the magnetic sensor and how well or even if it is working properly. When I open the compass (GPS status) it starts off 180° off and will slowly rotate around to what should be the correct rotation. This only works if the phone is resting on a flat surface, in "portrait" position, with the top of the phone point to what should be north. If you pick it up to look at it like if you going to walk, turn it sideways, or even flip it upsidedown (lay down and look up at the screen) the compass is off. Now that a compass tile has been added to CM12 I enabled it and tried it out. The tile works but the compass pointer it shows has the same behavior. I have not calibrated the compass yet. I am honestly kinda afraid to cause it usually makes it worse when I do.

At any rate here is a logcat. Hopefully it shows where I have been experimenting and helps.

https://www.dropbox.com/s/6bfnymxhyfcstyz/Log_2015-01-27_09-56-09.txt?dl=0

---------- Post added at 01:13 PM ---------- Previous post was at 12:58 PM ----------

One other tidbit.

I was looking at sensors using Advanced Sensor Tester and I noticed the three bars for the gyroscope hardly move when rotating the device, they move, just not very much.

The other thing I noticed is with the orientation sensor. There are three bars, the second and third move quite freely when rotating the phone. The first one is very sluggish. There is some movement but it is only in certain positions but usually is all the way to the right.

I wonder if multiple sensors should play nice together but aren't. Thoughts?
[Verizon Samsung Galaxy S 4] phonedawg:
Thanks a lot of looking into this. Rajones19's post has information on the kernel that got the compass working on CM11.
[Verizon Samsung Galaxy S 4] drt054:
[MENTION=2026117]FernBch[/MENTION] Alucard does not work for compass as I was running AntaresOne's (I9505 forum) Optimized cm12 and compass was at least 180 degrees off.. But good for getting a GPS lock.
[Verizon Samsung Galaxy S 4] FernBch:
Thanks for the info. I heard it mentioned elsewhere but was unsure. I have done some searching but it seems that rajones has hit the nail on the head. It has been some time since the the compass has worked on CM.
[Verizon Samsung Galaxy S 4] rajones19:
I can confirm. Yesterday I tested the three most prevalent 3rd-party kernels: Alucard, KT, and Googy-Max. None of them fixed the compass issue (I was pretty sure of this already), and two of them screwed up other things like bluetooth calling; one of them locked the screen in portrait orientation, and would not auto rotate. These are reasons I rarely mess with 3rd-party kernels - unless they fix the compass. I'm back on stock kernel now, with no sense of direction. :)
[Verizon Samsung Galaxy S 4] dansan382:
just read through the thread to catch myself up, everything with the ROM looks solid. really don't care about the compass not working as long as GPS directions are fine (which they seem to be). Only problem I'm having right now on my CM11 build is MMS is just jacked up, im constantly getting notifications from Textra that it couldnt receive an MMS and its driving me nuts. Didn't see much mention about it, but hows the MMS holding up on this ROM before I completely wipe and flash this?
[Verizon Samsung Galaxy S 4] .Ejekt:
It's inconsistent for me, but more stable than other CM12 ROMs I've tried. I'm on 1/27 now and picture messages go through most of the time, but group messaging has been a struggle.
[Verizon Samsung Galaxy S 4] FernBch:
This pretty much sums up messaging (stock app).

I have verified that there is a bug in messaging/group messaging.

If you send a text to person A, B or C, then send a group text to person A, B, and C it goes through fine. The bug shows up when one of the group recipients send a reply. The reply shows up in the group message and any individual message from one of the recipients is marked as unread. The individual messages will remain marked as unread until a message is sent to or received from the individual regardless of it being read beforehand or not.

Individual SMS or MMS works fine. If you're having send/receive issues go into APN settings, edit VZWINTERNET (change port to 80, MNC to 310, MCC to 012 and save), the VZWINTERNET will disappear, restore defaults and immediately reboot. This worked for me.
[Verizon Samsung Galaxy S 4] dansan382:
I'm not using the stock messaging app so I haven't experienced that bug you have. Mostly I just won't get the MMS... ever...

I will try that fix and see if it improves. thanks
[Verizon Samsung Galaxy S 4] phonedawg:
MMS fix is easy. Use the attached APN settings
[Verizon Samsung Galaxy S 4] ViperZ28:
Are all the install instructions the same? Use F2FS, not ext4?
[Verizon Samsung Galaxy S 4] musicfreak190:
Whats is it going to take for thr miscellaneous battery drain issue to go away? :( 5.0 s4 kernel source code?
[Verizon Samsung Galaxy S 4] indolent:
I've had better battery life on the CM12 nightlies compared to CM11. Are a lot of people having issues?
[Verizon Samsung Galaxy S 4] FernBch:
26 hours off the charge with 25% remaining here, bone stock.
[Verizon Samsung Galaxy S 4] musicfreak190:
You guys don't have Misc. battery drain under battery stats?

I wonder if It is my Google Experience Launcher...
[Verizon Samsung Galaxy S 4] indolent:
Nope, I have nothing related to, "misc battery," in the battery stats.

I use Nova Launcher
[Verizon Samsung Galaxy S 4] FernBch:
I quit going by the battery app in settings, i didn't tell me what the wakelock was when CM12 first came out. I use BBS and spend most of my time at 384 Mhz or in deep sleep. FWIW I did look at the battery app in settings and misc is on top of the list at about 18% but it is very misleading. Battery life has been outstanding for almost a month, for me anyway.
[Verizon Samsung Galaxy S 4] .Ejekt:
I have this. Usually at the top.

I've also noticed that the Battery Stats shows my battery as 2600 mAh, even though I have a larger battery in the phone.
[Verizon Samsung Galaxy S 4] invisiblek:
Well dang, you guys had me excited for the compass stuff =P

Its definitely the magnetic sensor that's jacked up. I actually wonder how well it works in stock.

Wonder if we need some updated firmware that we can't use because of the locked bootloader...

I'm thinking it may be an issue with our driver being updated in the kernel and our firmware not supporting it or something. I'll do some digging through the old stock kernel source, maybe I can hack something in for us.

Unrelated, misc battery drainage is kinda what I thought it was all along (a non-issue). Its been fixed: http://review.cyanogenmod.org/#/c/86775/
[Verizon Samsung Galaxy S 4] dansan382:
awesome to hear! guess I'll be flashing the build for tomorrow! do I still have to reformat the SDcard before flashing to make it see it or has that been resolved/changed?
[Verizon Samsung Galaxy S 4] rajones19:
Invisiblek, thanks for at least looking into this. With the current state of the ROM, device performance is just fantastic. Great battery life, especially in the last few weeks. Everything has been great - the stupid compass is the one single frustration. When this all first came to light, there was talk of needing blobs from Samsung, and then we got excited late last year when Samsung released some firmware, and 'blobs' were mentioned. I am not even sure I am using the correct terminology at this point in time. Anyway, to us oblivious non-developers, it sounded like we should be home free. Ever hopeful!