yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] wowthatisrandom:
All of those commits are in Euroskank

from his cherry pick list: bluedroid/Bluetooth: Commits 73850-73883, 73940-73973

unfortunately none of those are a fix for our device, they all seem to be improvements for working bluetooth. If i had to guess i would say the fix will most likely come from the kernel or the jflte device tree since its only affecting our device.
[Verizon Samsung Galaxy S 4] FernBch:
I could be wrong but I thought most all the GS4's used jflte?
[Verizon Samsung Galaxy S 4] wowthatisrandom:
Correct they all do

Edit I believe they switched to the jf-common tree now
[Verizon Samsung Galaxy S 4] ahaynes42:
That's weird, I'm getting horrible battery life on M9 lately. I've even been using wakelock detector and can't find anything raising a red flag. Look at my screen on time!!
[Verizon Samsung Galaxy S 4] FernBch:
What do your kernel wakelocks look like?
[Verizon Samsung Galaxy S 4] CyberZion:
Reset your battery stats if all else fails.
[Verizon Samsung Galaxy S 4] ahaynes42:
I'm not seeing an option for kernel wakelocks in wakelocks detector. Also, it's not consistently this bad. Just 2 or 3 times a week it's this bad. Average is about 10 hours with 2 hrs sot.
[Verizon Samsung Galaxy S 4] FernBch:
10 hrs with 2 hrs SOT? As screwy as CM has been recently I currently sit at 14 hrs 52 min, 2 hrs 11min SOT, and 41% battery (Wifi and BT on all day). How are your settings (screen brightness, etc)?

---------- Post added at 11:25 PM ---------- Previous post was at 11:23 PM ----------

On another note, anyone try M11 yet. I am expecting to experience all the recent issues but am curious. I read a couple posts in the int'l forum and some say it's pretty solid, others say the same things we do..........
[Verizon Samsung Galaxy S 4] Danvdh:
reflash m9 on clean wipe and use the latest PA gapps (I use micro modular)

Google services is most likely the culprit, I make sure Velvet.apk (Search) does not get flashed with the ROM as its the number one culprit for terrible and unpredictable battery life, I personally install it as a user app and just greenify it, Greenify is hands down the best app for Android to control apps wakelocking, it allows you to hibernate any user app you want when the screen goes off and the app is closed. iOS does the same thing with all apps with NO exceptions, Greenify allows you to control what gets hibernated though which is a step up from Crapple
[Verizon Samsung Galaxy S 4] vanberge:
Fern asks if anyone has tried M11.. Everyone else is like "Fern hasnt tried M11 yet?" lol
[Verizon Samsung Galaxy S 4] ahaynes42:
Thanks for the suggestions, I will try this out. I had just come to accept subpar battery life as the norm. But hearing others speak of getting through a whole day makes me want to try a clean flash. I've also heard good things about greenify.
[Verizon Samsung Galaxy S 4] dorioo:
Lol. Exactly. I just came to the thread to get my "nightly" Fern report for 10/09
[Verizon Samsung Galaxy S 4] FernBch:
Hey what can I say? It's an M build, not a nightly. Unless CM changed that too the M builds were always "a little behind" the latest nightly. Speaking of which, I'm downloading now. Should have a prelim report in soon. I did see a few WiFi related commits so hopefully things will be better. Here goes nothin.............I'll let you know how it goes.

---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------

Oh, before I flash, just thought I'd say I saw a couple GPS related commits, too........
[Verizon Samsung Galaxy S 4] ahaynes42:
M11

Just flashed M11, it's looking good so far. There's a new kernel dated Oct 8!! Pebble connected immediately through bluetooth. Data handoff from wifi to LTE went well. Looks promising. FernBch, how's it running for you?

edit: GPS looks solid as well
[Verizon Samsung Galaxy S 4] FernBch:
I am up and running.

The handoff from WiFi to mobile data still is not 100%. When I left WiFi it DID connect to mobile data, but only to 3G. I had to cycle airplane mode to get LTE.

I turned BT on then my Jabra and it DID auto connect. But when I turned my Jabra off it still thinks it's connected. Had to cycle BT to get it to reconnect.

Also checked GPS. The orientation part is still not correct. I can get a lock quickly but the compass is slow to respond and orientation is off by 180 degrees.

Logcat attached:

https://www.dropbox.com/s/px5jsj3uxe7ativ/Log_2014-10-09_07-05-36.txt?dl=0

Guess I'll try a reboot and see if things change afterwards. Hopefully it all doesn't go south like it has been.

---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------

Just noticed one thing before I reboot. First boot I had no issue turning WiFi on. But after turning it off it hangs on "Turning WiFi on". We'll see how it goes after a reboot.

---------- Post added at 10:24 AM ---------- Previous post was at 10:19 AM ----------

One other comment. At the moment my Jabra has decided to auto connect/disconnect properly. Don't know why it's being funky. New logcat attached:

https://www.dropbox.com/s/vk9iefoqevabbfx/Log_2014-10-09_07-22-22.txt?dl=0

Also, the wpa_supplicant failed to initiate an AP scan message is back. Here goes the reboot...........
[Verizon Samsung Galaxy S 4] ahaynes42:
Nevermind, there are still issues with Wifi and data, as FernBch pointed out. I was so excited that everything worked fine on the first boot that I didn't give it enough time to fully observe.
[Verizon Samsung Galaxy S 4] vanberge:
Fern did you go with M11 or the latest nightly?
[Verizon Samsung Galaxy S 4] FernBch:
ahaynes42, It's ok, I did that a couple times, too.

Post reboot update.

After a reboot I can turn BT on and off and connect/reconnect to my Jabra correctly BUT I can not turn WiFi on. It hangs at turning WiFi on. Cycling airplane mode has no effect.

After a reboot GPS is now working and orientation is correct.

It seems like BT is currently working but WiFi is now broken. I still think that the whole WiFi/BT/Mobile Data issue have a common denominator somewhere (kernel maybe?).

Post reboot Logcat attached:

https://www.dropbox.com/s/s47czx2e4i0kp65/Log_2014-10-09_07-40-41.txt?dl=0

Guess I'll try another reboot and see if I can get WiFi back.....

---------- Post added at 10:44 AM ---------- Previous post was at 10:44 AM ----------

Edit:

The latest nightly

---------- Post added at 11:04 AM ---------- Previous post was at 10:44 AM ----------

Ok. After one more reboot I have WiFi back. I did have to cycle airplane mode as mobile data will not automatically connect after a reboot. As it stands now everything is "functional" with workarounds (that includes BT). I think I'll leave it as it is for now.

2nd post reboot Logcat attached:

https://www.dropbox.com/s/h3urs9rgjoigqp0/Log_2014-10-09_07-59-25.txt?dl=0

Guess I need to head over to JIRA and update my report there, too.

---------- Post added at 11:22 AM ---------- Previous post was at 11:04 AM ----------

One more note:

I have updated the report over at JIRA in the nightlies regression section. Basically I linked to this thread, referenced post numbers, etc. There are a total of four reports I see over there. When I created my report I referenced three other nightly bug reports numbers as we are experiencing all of them and I believe they are related.
[Verizon Samsung Galaxy S 4] vanberge:
I thought the 10/9 nightly might have fixed everything with a clean flash. I had good wifi/bt for awhile through about 10 reboots.

But, then out of the blue it started back to the old tricks. BT toggle turned off wifi. wifi wouldnt turn back on. airplane mode wouldnt turn off BT/Wifi. Sigh.

Nandroid back to M9 where it feels like I'm going to be until I hit my 2 year.
[Verizon Samsung Galaxy S 4] FernBch:
I made the switch to the NC5+NONHLOS modem. Gonna try things out and see if it's better. Not gettin my hopes up cause I have read that others have issues regardless of modem package. I did notice that when it booted back up it automatically connected to LTE, if that even means anything. May have to wait and see after flashing 10/10 tomorrow morning. At any rate if I don't post up that means there is nothing new to share.
[Verizon Samsung Galaxy S 4] FernBch:
Well, been running NC5 all day and as far as I can tell there is no change in behavior (issues still present). I did look over at my JIRA report and it has been assigned to invisiblek. Nothing will probably get better until the issue is addressed and a fix is merged.
[Verizon Samsung Galaxy S 4] Train88:
I clean flashed 10-7 and haven't had any issues when going from WiFi to lte, and vice versa. Turning WiFi off results in automatic connect to lte, and it will connect to WiFi once it's turned back on. Have not tested Bluetooth though

I've used NC5 for quite a while, and the only big issue I've had in the past is BT connectivity being shotty

Team BlackOut... or Back Out - "These colors that you've shined are surely not your style”
[Verizon Samsung Galaxy S 4] FernBch:
I will agree with NC5 being good. Strangely enough I have had better data handoff behavior today (3G to LTE) plus better service in areas where it previously wasn't so good. I'll know better after some more testing on the other issues but as things sit currently BT is still borked.
[Verizon Samsung Galaxy S 4] FernBch:
I was just browsing the commits for the next nightly.

This looks interesting, possible fix for the wpa_supplicant scan failure issue? They were sign off by someone at Qualcomm. [emoji106]

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

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

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

And maybe some help for battery life too.

http://review.cyanogenmod.org/#/c/74725/
[Verizon Samsung Galaxy S 4] FernBch:
10/10 is up and running. So far the only thing I have noticed is the handoff from WiFi to mobile data seems to be working. No WiFi equals quick and consistent LTE data service for me.

Bluetooth still has the same issue for me but it is usable with a workaround.

Compass is still borked. Orientation is off by 180 degrees.

I think I have commented on this before but for some reason I get "no changelog available" again from the CM update menu. That comes and goes and is on the bottom of my list right now.

Guess I'll install BBS as a system app and reboot.........

---------- Post added at 09:58 AM ---------- Previous post was at 09:15 AM ----------

I have rebooted........and.........and..........wait for it.............nothing has changed.

Upon reboot I disconnected from WiFi and had to cycle airplane mode to get a mobile data connection the first time, BT is borked, compass is borked.

Things are "functional" with workarounds.

Gotta love the predictability. Lol
[Verizon Samsung Galaxy S 4] jkc120:
Yep, all those issues still exist and I am having SoD more frequently again (10/5). 2 times yesterday. A G3 is looking good now, since it's got a custom recovery now. hmmm
[Verizon Samsung Galaxy S 4] vanberge:
I clean flashed 10/10 and again everything worked beautifully through over an hour and 10-12 reboots.

Then again, out of the blue, bluetooth toggles began to make wifi disconnect. And then wifi/bluetooth do not operate correctly. I cycle airplane mode and bluetooth shuts off while wifi turns back on (with airplane mode).

My soul gets crushed a little bit everytime I nandroid back to M9, so I might just run with these nightlies for awhile and leave bluetooth disabled.
[Verizon Samsung Galaxy S 4] FernBch:
The nightlies aren't totally broken, just some things don't work as smooth as they should. My issues do have "workarounds" I just don't get all the functions of some items.
[Verizon Samsung Galaxy S 4] Drogean:
Flashlight app malware?

Any word if the built in flashlight uses any of these apps that have been recently found to send private data to foreign countries?

http://www.snoopwall.com/threat-reports-10-01-2014/
[Verizon Samsung Galaxy S 4] vanberge:
Yo Fern, I think I found a workaround for bluetooth and wifi to pay nice together! At least, it's working for me so far.

You need to get to the app permissions which are now hidden in android. For me, I did this using nova launcher. So you could temporarily install that and launch it if you dont use it. Then follow these steps

Long press empty screen space while in Nova launcher

Click on "Shortcuts"

Scroll down, select "settings shortcut"

Select "App Ops"

Click on your newly added "App Ops" Icon

Click over to the right to "Media" (It's to the right of Location and personal)

scroll down until you see Bluetooth share and select it

I disabled "Data change" permission for bluetooth share in 2 spots

So far, bluetooth starts and wifi stays running. I have not tried to re pair with any BT devices yet though so I'll report back soon.

Try it out ! I'm curious to see if it would help you too
[Verizon Samsung Galaxy S 4] FernBch:
Didn't work. Same BT issue persists for me. Thanks for trying.
[Verizon Samsung Galaxy S 4] ahaynes42:
BT

Has anyone in here tried flashing different kernels over CM11? I can't deal with this horrible bluetooth anymore. I just did a clean flash of M9 this morning and my bluetooth range is still horrible. I get more than 6 feet away from a bluetooth device and it starts to break up. I use bluetooth a lot to play music through speakers and in my car. I tested the same speakers with my wife's Moto X, and I got almost 30 feet (which is supposed to be the standard) without any issue. Also, could I have faulty hardware? Do any of you get the standard 20-30 ft range with your S4?
[Verizon Samsung Galaxy S 4] FernBch:
The third party kernels currently do not work with CM11. They need to be updated.
[Verizon Samsung Galaxy S 4] cambunch:
No, the built in flashlight it completely safe to use.
[Verizon Samsung Galaxy S 4] gonzlobo:
Source?
[Verizon Samsung Galaxy S 4] jkc120:
https://github.com/CyanogenMod
[Verizon Samsung Galaxy S 4] cambunch:
CyanogenMod wouldn't package spyware with their ROMs
[Verizon Samsung Galaxy S 4] vanberge:
Laughed out loud at this...

Nice
[Verizon Samsung Galaxy S 4] gonzlobo:
So, no source then...
[Verizon Samsung Galaxy S 4] jkc120:
It isn't impossible, but obfuscating code so people can't see it's being done to send personal data is FAR from trivial. And with the number of eyes on the cm source, it's just not going to happen. Hiding this kind of thing in an apk is one thing. Hiding it in publicly available source code is entirely different.
[Verizon Samsung Galaxy S 4] vanberge:
If you are worried you could install droidwall and block its mobile/WiFi access
[Verizon Samsung Galaxy S 4] FernBch:
Or Avast, or Webroot, or........

There are many apps that can block data services on a per-app basis.

---------- Post added at 01:24 PM ---------- Previous post was at 01:19 PM ----------

Ok. Call me a glutton for punishment, but, the build finished almost 5 hours ago and it isn't available on the download server yet. What's up with that?
[Verizon Samsung Galaxy S 4] wowthatisrandom:
http://review.cyanogenmod.org/#/c/74892/

this one look interesting...
[Verizon Samsung Galaxy S 4] FernBch:
Looks VERY interesting...............
[Verizon Samsung Galaxy S 4] vanberge:
I kind of want to try building a version with this in there.
[Verizon Samsung Galaxy S 4] FernBch:
I hope it gets merged. Reading through it though looks like it's not quite 100% there yet, but close. {fingers crossed}
[Verizon Samsung Galaxy S 4] phonedawg:
Dan Pasanen	10:21 AM

Patch Set 3: -Code-Review

Pekka - please test this as soon as you can. We have some major bt issues on jf that need fixing.

Yes, it seems to be the answer to our troubles.
[Verizon Samsung Galaxy S 4] FernBch:
Looked again this morning. It is definitely being pushed forward, still under review, but getting closer.
[Verizon Samsung Galaxy S 4] FernBch:
Success!!!

This has been merged!

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

Kudos also to wowthatsrandom for giving me an unofficial test build to try out!! I have hammered it hard and I only had two issues.

On initial boot everything works, including the compass. I had to cycle airplane mode once to get mobile data after disconnecting from WiFi. After that the handoff was good. My Jabra BT is working properly as well.

After a reboot the only issue I have is the compass orientation is back to being off by 180 degrees again. Not sure what is up there. Maybe a kernel tweak or firmware tweak? Everything else is good so far!!!

Make sure you give thanks to wowthatsrandom and invisiblek for all they have done!!

---------- Post added at 04:04 PM ---------- Previous post was at 03:22 PM ----------

Edit:

I knew that being a glutton for punishment would pay off. Never lose faith in our CM Devs!
[Verizon Samsung Galaxy S 4] gunnermike:
Is it in todays build?
[Verizon Samsung Galaxy S 4] FernBch:
No. I wasn't merged early enough. Look for that one and one for the camera in the 10/13 nightly.
[Verizon Samsung Galaxy S 4] CyberZion:
Is VOIP still broken?
[Verizon Samsung Galaxy S 4] FernBch:
Not sure. It's been a couple months but I have had no issues using Tango and Skype, if that's what you mean.

---------- Post added at 08:36 PM ---------- Previous post was at 08:30 PM ----------

Edit:

It's been about 8 hours now and BT still works. I'm pretty confident that this one can be put to rest. When it comes out tomorrow morning flash away! I know I will.[emoji111]
[Verizon Samsung Galaxy S 4] phonedawg:
We should get compass issues sorted out too
[Verizon Samsung Galaxy S 4] FernBch:
I created a bug report in the nightlies regression section a little while ago complete with logcats. For me GPS works fine, compass is off by 180 degrees.

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/NIGHTLIES-258
[Verizon Samsung Galaxy S 4] .Ejekt:
Flashing now! This is exciting. :cyclops:
[Verizon Samsung Galaxy S 4] FernBch:
How you do that? It's about 90 minutes or so before jenkins builds jflte?
[Verizon Samsung Galaxy S 4] vanberge:
10/13? I can't find it yet.
[Verizon Samsung Galaxy S 4] FernBch:
Jenkins builds alphabetically and it's up to i605, I don't know.....
[Verizon Samsung Galaxy S 4] .Ejekt:
Damn. Flashed 10/12. Didn't realize you were talking about 10/13 '- .-
[Verizon Samsung Galaxy S 4] FernBch:
It's OK. I did it too.
[Verizon Samsung Galaxy S 4] vanberge:
What recovery are you all using? I have a 6.5.0 that InvisibleK posted awhile back when they made the massive kernel switch.

I keep thinking about updating the option in CM that says "update recovery" but have never tried it. Anyone in here tried it?

Anyone on anything newer than CWM 6.5.0?
[Verizon Samsung Galaxy S 4] jkc120:
You know, for the compass issue it seems like if it's always off 180 degrees it should be an easy bug to fix or at least work around. Hopefully they six it soon.
[Verizon Samsung Galaxy S 4] FernBch:
6.0.5.0, as far as I know, is the latest. And, unless I misunderstood what I read, the I545 does not have the option as far as recovery goes due to the fact that the bootloader is not unlocked. We only have a custom recovery because of the loki exploit. But I could be wrong on this. So I have never tried it.
[Verizon Samsung Galaxy S 4] vanberge:
http://jenkins.cyanogenmod.com/job/android/87076/

It's building now! I am so happy
[Verizon Samsung Galaxy S 4] .Ejekt:
Does this compass issue have any effect on GPS? If I'm in navigation will the phone think I'm driving backwards?
[Verizon Samsung Galaxy S 4] FernBch:
I've never paid attention to which way the phone thinks I'm driving but navigation has been working for me without issue.
[Verizon Samsung Galaxy S 4] jkc120:
No, because the orientation once you're moving is determined by the movement. It does cause problems when you're walking and trying to use the GPS in a city for example (ask me how I know this....hahahha).

But for driving, it works because although the compass is backwards, once you start moving it uses your trajectory to figure it out. It causes some slightly "off" behavior when you're moving slowly and coming up on weird angled turns, but usually not a huge deal. But for walking directions, it could be problematic.
[Verizon Samsung Galaxy S 4] vanberge:
Hmm... I'm not sure if this change made it into the nightly. Anybody know how to check?

I dont really see anything in the changelog that seems to point to it
[Verizon Samsung Galaxy S 4] jkc120:
It's in there:

http://www.cmxlog.com/11/jflte/
[Verizon Samsung Galaxy S 4] FernBch:
Flashed 10/13. So far it all seems fine. For whatever reason my compass orientation is even correct, but I expect that to change. It's so nice to have properly functioning BT again on CM11.

[emoji106]
[Verizon Samsung Galaxy S 4] phonedawg:
Reboot and recheck
[Verizon Samsung Galaxy S 4] FernBch:
I did. After the first reboot things seemed fine. Now I notice that Bluetooth seems ok for me, but there is still something up with the whole WiFi/BT relationship. My BT device works as it should but if I turn BT off and back on turning WiFi off an on has an issue.

---------- Post added at 01:42 PM ---------- Previous post was at 01:31 PM ----------

I went to my JIRA report and made an update with a logcat.

---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------

Also, the JIRA report I made for the compass has been assigned to invisiblek.
[Verizon Samsung Galaxy S 4] .Ejekt:
10/13 dirty flash over 10/12. No GPS after reboot.
[Verizon Samsung Galaxy S 4] vanberge:
Yeah I clean flashed 10/13 and the issue with BT toggling jacking up wifi is still there. I really had my hopes up that this was resolved. :( What a bummer
[Verizon Samsung Galaxy S 4] FernBch:
From what I'm reading elsewhere most are turning one off before turning the other on as a workaround. I look at it like BT is working so it's a step forward. I may restore my "unofficial" nandroid and see if it's present there. I honestly didn't notice the other issues yesterday. May have just been from being excited that BT was working.
[Verizon Samsung Galaxy S 4] CyberZion:
VOIP on Google Hangouts still does not work for me. Any Ideas?
[Verizon Samsung Galaxy S 4] .Ejekt:
Everyone back to M9! Nothing to see here.
[Verizon Samsung Galaxy S 4] FernBch:
Not me, I'm stayin put! Lol
[Verizon Samsung Galaxy S 4] gonzlobo:
Thanks for saving me time.
[Verizon Samsung Galaxy S 4] vanberge:
I'm staying too. 10/13 is usable as long as I boot with Bluetooth on and turn on WiFi after boot has completed
[Verizon Samsung Galaxy S 4] FernBch:
Don't know what or how much it all means, but there are a BUNCH of new BT related commits merged for tomorrow's build.........
[Verizon Samsung Galaxy S 4] hlxanthus:
. . . and no nightlies tonight . .

https://plus.google.com/117962666888533781522/posts/WJmxq9TUDt1
[Verizon Samsung Galaxy S 4] FernBch:
Bummer
[Verizon Samsung Galaxy S 4] FernBch:
I was doing some reading in threads for other jflte devices and I have come across a couple items that may lessen the impact of current issues.

Those that have turned off both WiFi and BT then rebooted are reporting less issues. I tried the same and things seem to be better after.

I have also seen posts asking about which bootloader and modem is currently being used. Since we are all on MDK that item is a moot point. What I am getting is the ones one the latest or near latest modem are having less impact than those on an older modem. Not sure what impact that has.

For my setup I flashed NC5+nonhlos a couple days ago, turned WiFi and BT off, rebooted, turned WiFi and BT back on, am running 10/13, and things are working well for me. I am not experiencing any issues with WiFi disconnecting when cycling BT, WiFi hanging when turning on, or data handoff between different network types. My BT device (Jabra BT2045 Earpiece) is working as it should be. I have only experienced one time of it not connecting and it may have been due to how fast I cycled BT off and on.

So as it sit currently I know the WiFi/BT/Mobile Data issue may not be 100% fixed but it definitely is much better than it has been recently. That said I am going to stay put on 10/13. It works well enough with very few workarounds, actually am not having to do anything special to use anything right now.