yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] scarmon25:
Others getting an error when enabling WiFi tether? Just want to know if its just me or not.
[Verizon Samsung Galaxy S 4] Zmnypit:
12\16 was working the best for me. Until I went to open the camera today. Getting the error "can not connect to camera" is there a fix for that?
[Verizon Samsung Galaxy S 4] scarmon25:
Yeah. Use a root explorer and navigate to system/lib/HW and change the camera.msm8960 to vendor-camera.msm8960 and reboot
[Verizon Samsung Galaxy S 4] drt054:
Haven't tried WiFi Tether app, but native tether (built in) works fine
[Verizon Samsung Galaxy S 4] scarmon25:
Hmm. Mine just turns back off and says error. Using built in. 12/16
[Verizon Samsung Galaxy S 4] jorceshaman:
I'm using 12/16 with Ktoonsez 12/12 kernel and having no issues with wifi tether.

Looking forward to the 12/19 update so I can use the 12/18 kernel. Love all the OSE tweaks!

Edit: Just realized this was the official thread, not the OSE thread. Just so my comment about OSE makes more sense.
[Verizon Samsung Galaxy S 4] scarmon25:
Sure enough it is now working. I guess it knew I was about to tackle it lol
[Verizon Samsung Galaxy S 4] jorceshaman:
This didn't work for me. Renamed and restarted, same error.
[Verizon Samsung Galaxy S 4] Zmnypit:
Thanks! Worked like a charm...
[Verizon Samsung Galaxy S 4] jorceshaman:
Do you now have 2 of the vendor-camera files with the same name, 13KB and 210KB?

Not sure why it didn't work for me.
[Verizon Samsung Galaxy S 4] scarmon25:
You only do the lowercase one.

---------- Post added at 03:45 PM ---------- Previous post was at 03:45 PM ----------

Also I saw some sensor commits in this coming build for today. Hoping it fixed proximity :)
[Verizon Samsung Galaxy S 4] jorceshaman:
I tried several different ways with no luck. Just reflashed the ROM and it's working again. Oh well. Thank you for the info/help.
[Verizon Samsung Galaxy S 4] scarmon25:
Looks like today's build failed.
[Verizon Samsung Galaxy S 4] Chris123NT:
That kernel commit fixes sensors.
[Verizon Samsung Galaxy S 4] scarmon25:
Yeah. Unfortunately it failed out on build :(
[Verizon Samsung Galaxy S 4] Schoat333:
I'm still on the 12/13 build, and from some of the responses, I'm glad I waited to update.
[Verizon Samsung Galaxy S 4] chilewile007:
Updated from 12/13 through CyanDelta, no new problems.

However I started out on the 12/13 nightly from stock, and the camera has never worked right. If I take pictures using the camera app they appear solid grey, and the gallery spits an error when I try to view them.

Is there a fix for this?
[Verizon Samsung Galaxy S 4] .Ejekt:
Mic during video calls still doesn't work. Is this device specific or an issue across all CM11?
[Verizon Samsung Galaxy S 4] Zmnypit:
I have camera.msm8960.so that 210kb and vendor-camera.MSM8960.so 13.46kb
[Verizon Samsung Galaxy S 4] wowthatisrandom:
i still dont think its fully working, even on the latest CM i can get that same thing. it should just say "connected." do voice commands work for you? i find they work very rarely and know its bc bt isnt fixed. i have confidence invisiblek will fix it soon
[Verizon Samsung Galaxy S 4] HowardZ:
I am using the Oct 2nd nightly of CM.

I can not flash new versions until the recovery is fixed, or I wipe data and sdcards to eliminate encryption. So it is something I can get out of.

I have tried the latest TWRP, and the non-touch CWM recovery.
[Verizon Samsung Galaxy S 4] gonzlobo:
Thanks for the heads up. I'll flash the next Euroskank build after I heavily use my GPS tomorrow.
[Verizon Samsung Galaxy S 4] FernBch:
This has not been merged yet, still under review.

On another note.

Been running 10/3 all day today. The BT, WiFi, Mobile Data connect handoff issue persists. Have to cycle airplane mode to get mobile data to connect. Handoff from WiFi to mobile data is broken (again, still, or whatever you wanna call it). If WiFi is off and I turn it on it just hangs on turning WiFi on. If I reboot WiFi is on and will connect afterwards.

At this point I really see no point in going back a couple days. All I'll get is what I have now.......

[emoji22]
[Verizon Samsung Galaxy S 4] Alarbus:
Yeah, I haven't budged from M9. I'm not even going to bother with M10. If there are substantial enough kernel or bluetooth changes, I might give something a try, but it's not really appealing.
[Verizon Samsung Galaxy S 4] gunnermike:
Man I would punch a kitten for some working Bluetooth. I may have to try the euroskank version.
[Verizon Samsung Galaxy S 4] vanberge:
Considering this as well.
[Verizon Samsung Galaxy S 4] FernBch:
This may be a little off topic, but

http://www.dailytech.com/Report+Cya...om+Google+Wants+1B+Valuation/article36659.htm
[Verizon Samsung Galaxy S 4] vanberge:
Are Euroskankers getting builds here?

http://fitsnugly.euroskank.com/?rom=cm11&device=jflte
[Verizon Samsung Galaxy S 4] gunnermike:
Punching a kitten? Yeah, I freaking hate cats.
[Verizon Samsung Galaxy S 4] FernBch:
I'd just take something promising to test the crap out of........
[Verizon Samsung Galaxy S 4] gonzlobo:
That's them.
[Verizon Samsung Galaxy S 4] vanberge:
Alright... I'm trying something new. Instead of the official nightlies and cyanogenmod gapps, I'm going to latest euroskank with pa gapps.

Just clean flashed, we'll see how it goes
[Verizon Samsung Galaxy S 4] gonzlobo:
Here's the link to their forum, but there hasn't been traffic for a few weeks.

http://xdaforums.com/showthread.php?t=2385271

It goes without saying, backup before flashing fitsnugly's ROMs (but then again, you already backup before any flash, right).
[Verizon Samsung Galaxy S 4] gunnermike:
The latest Euroskank is working great.
[Verizon Samsung Galaxy S 4] MustGoFast:
I agree BT isn't working properly, but the correct msg is "connected running sync loop". I see that w/ my 360 on ROMs with no BT problems or stock.

FYI: euorskank has the same BT issue.

Slimroms 7.x is working great (no disrespect to CM).
[Verizon Samsung Galaxy S 4] vanberge:
Man fern... You rule. Great testing.

I'd be curious to see how skanks runs for you. I'm going that route until further notice
[Verizon Samsung Galaxy S 4] FernBch:
Thanks Dude. I still have faith that invisiblek and the team over at Cyanogenmod will get these issues knocked out. It just seemed weird that I saw what I thought I saw (if that makes sense), and that I was actually able to repeat it. Something low level is definitely up when you flash, all seems better, the you reboot and things go south afterwards.

At any rate. I went back a few days and reflashed things. Now I'm back to the point I was before rebooting on 10/4. Everything is mostly working again and I REFUSE to reboot this time.

I hate to flood the place with a bunch of info but here's a logcat of my current state.

https://www.dropbox.com/s/qpejq3q23bv8def/Log_2014-10-04_11-25-45.txt?dl=0
[Verizon Samsung Galaxy S 4] rajones19:
Except for the compass, which is still borked (for me, anyway). Seems like anything built from the CM base is going to have this problem, and sadly, I don't think there is anything 'AOSP' now that isn't built from CM's base.
[Verizon Samsung Galaxy S 4] jkc120:
Hmm, I have no issues (just flashed 10/4 on top of 9/25) with BT and WiFi turning on/off or data hand offs. I wonder if your HLOS is the culprit? You're still on an old one, right? invisiblek told me on irc he recommended the latest HLOS. I'd note what MDM and HLOS you currently have (so you can grab and re-flash them if need be) and then try grabbing the NC5 MDM+HLOS zip from here and flash it in recovery.
[Verizon Samsung Galaxy S 4] HowardZ:
I can not undo the encryption. A factory reset from CyanogenMod reboots into the custom recovery which then displays errors that it can not mount partitions.

So, it seems that encrypting the S4 with cyanogenmod leaves me stuck on the Oct 2nd nightly with no way to flash another nightly.

Another thought was Odin. I tried to flash the factory MDK recovery using ODIN and it failed to flash. I might be doing something wrong with Odin, and it is not certain that the MDK recovery will be able to factory reset to turn off the encryption.
[Verizon Samsung Galaxy S 4] gunnermike:
Omni isn't CM based and doesn't have the problems CM has had. It also doesn't have the theme engine. I am ok with the other issues CM has, I can wait, but the BT is a big deal for me as I use it all day everyday.
[Verizon Samsung Galaxy S 4] vanberge:
I have nc5 with hlos or whatever and I have the same issues as fern described. Data handoffs mainly is what bit me. I'd go a half day and be like "why don't I have any email"

Edit...

I'm having it a bit even on skanks latest too actually
[Verizon Samsung Galaxy S 4] jkc120:
Well data handoff could just be my area's coverage being better or that I usually manually turn off/on WiFi, so I may have that problem. But I did the exact steps Fern described after flashing 10/4 and have no issues turning BT/WiFi off or on.
[Verizon Samsung Galaxy S 4] FernBch:
I'm on MK2+nonhlos, maybe I should flash a later and see.....
[Verizon Samsung Galaxy S 4] jkc120:
Can't hurt, you can always flash back to MK2 :)
[Verizon Samsung Galaxy S 4] FernBch:
True but the weird part still exists. Everything worked perfectly until AFTER a reboot. That is twice in the last week that this has happened....
[Verizon Samsung Galaxy S 4] jkc120:
Maybe it's something to do with the state of your WiFi and BT after you reboot for the first time? Are they enabled and connected or enabled but not connected, etc?
[Verizon Samsung Galaxy S 4] FernBch:
I'm not sure that it matters. I've had both off, on and not connected, etc. After flashing I can turn things on/off and connect/disconnect at will and in any order. If I reboot things get funky. BT is the best example. After flash and before reboot I can turn BT on/off from the tile or settings menu, turn my Jabra on/off before or after turning on BT and it will function exactly how it is supposed to without any type of workaround or set order of doing things.

After a reboot the only way to get my Jabra to work "mostly" correct is to only turn it on and connect it from within the settings menu after turning BT on. Even then the button on the side will only answer a call and not end the call. If I connect from the tile I have to turn the Jabra on then cycle BT. Also connecting to it this way and the button on the side of it does nothing. The S4 will also "forget it" sometimes with this method, too. When that happens I have to unpair it and start over.

Whatever has made things go south with the whole WiFi/BT/Mobile Data relationship happened sometime in the last two weeks, give or take.

Around the release of the 8/30 nightly when I reported finally beating the SoD issue (haven't had one since then) everything was fine. Data handoff and all worked properly and, for me anyway, BT worked flawlessly, too.
[Verizon Samsung Galaxy S 4] jkc120:
I still get SoD, just had one today in fact on 10/4 and it's seems to be LED or audio related is my guess as it always happens when I receive a notification.
[Verizon Samsung Galaxy S 4] FernBch:
That was my exact conclusion when it plagued me. When I flashed 8/30 I factory reset from the settings menu, booted into recovery and factory reset from there, restored my MDK nandroid, booted-setup-etc, booted into recovery and factory reset again, and clean flashed CM. Haven't had one since and have no clue why doing that fixed the issue for me.
[Verizon Samsung Galaxy S 4] vanberge:
Yeah I am having horrific issues with bluetooth/wifi/mobile data. Seems pretty consistent with what fern has said already.

As Fern noted, It gets worse after a reboot. Bluetooth toggling jacks up wifi. Wifi wont cycle. Wifi comes on when airplane mode is enabled. It's just nuts.

I clean flashed 10/4 and then also clean flashed skanks 10/4 latest and it happens on both.
[Verizon Samsung Galaxy S 4] FernBch:
Exactly what I have seen. Now if I knew how to track the boot process, or more precisely the reboot process, something could be detected to help zero in on what goes wrong.
[Verizon Samsung Galaxy S 4] phonedawg:
Is this an issue with all phones or just this model - what about the other S4 models?
[Verizon Samsung Galaxy S 4] wowthatisrandom:
from what i understand, when CM made the move to unified builds they all have the issues. things like mms/apns etc would be per carrier, but things like bluetooth and wifi etc would be a device issue
[Verizon Samsung Galaxy S 4] FernBch:
^^^^^^^^^^This would be a more accurate description^^^^^^^^^^

When the builds were unified it made everyone run one and the same across the carriers. It was screwy at first but was corrected. The unified build is not the cause of the problem, it just made everyone see the same problem at the same time.

I was reading through some posts on other GS4 forums (TMO, ATT, SPR, etc). Most everyone seems to be having the same issues and it all went to crap in mid August when the big kernel revamp went down. At the same time the third party kernels no longer worked with CM as well. I have also read that koontz and a few others have moved on to the GS5. So there is no guarantee that a new third party kernel is coming soon but I could be wrong. Many of the other ROMs have all the same problems cause they take CM and use it for their base.

I personally am going to be posting more info over at JIRA as it does not seem to be making it out of XDA. We know what is broken but not much seems to be happening.

And yes, I am guilty of it too. I can read logcats and pull info about errors but I don't know how to fix it. I have the desire to fix things but lack the skills and time. Having a full time job and a family doesn't leave time to learn Android at that depth. So I do like many and wait for a fix.

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

I guess what I am trying to say is I need working. I can deal with some instabilities. What I can't deal with is broken. There has to be a place where this info can be conveyed and seen and I'm not going to switch to a half broken M build that is waiting for a few things already in the nightlies just to be able to do official bug reports. The nightlies are loosing their luster and Cyanogenmod is doing things a little differently now. But hey, Google offered to by them so I guess that's what happens when you make the jump to the mainstream.

Sorry, just am feelin the need to rant a little...........
[Verizon Samsung Galaxy S 4] vanberge:
yeah I feel the same as you fern. I might just ride M9 into the sunset on this device
[Verizon Samsung Galaxy S 4] FernBch:
I hear ya there. I'll get to something that mostly works again...........one day.
[Verizon Samsung Galaxy S 4] phonedawg:
GS4 is a popular phone. It is comforting to see that all GS4 models are having these troubles. CM will fix this if we petition hard.

GS4 -> GS5 is not worth the upgrade and moreover most GS5 phones don't have custom recovery and hence don't have CM.
[Verizon Samsung Galaxy S 4] FernBch:
This is my thought as well. Hopefully it will happen.....
[Verizon Samsung Galaxy S 4] gonzlobo:
S5 isn't the only phone out there. If I was shopping, *I'd* look at the latest from Moto, HTC & LG. I think I'd lean to the Nexus6, but I don't want a 6" phone.
[Verizon Samsung Galaxy S 4] jkc120:
None of them, with the exception of the m8 perhaps, have a custom recovery and thus cm11 (on vzw). I'll take an s4 with cm11 over an s5 with touchwiz any day.
[Verizon Samsung Galaxy S 4] FernBch:
Unless you fork over the $$ for a developer edition and I'm not sure that option is available on all devices.
[Verizon Samsung Galaxy S 4] phonedawg:
My thoughts, exactly.

---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------

I am not aware of a flagship android phone on verizon except M8(which has a bad camera and is too big - it is the size of LG G3) that allows custom recovery and has a CM ROM. S4 is still the best choice for CM users. Moto X(2014) is also a good choice with its pure android.
[Verizon Samsung Galaxy S 4] Stan42:
<deleted>

---------- Post added at 10:18 PM ---------- Previous post was at 10:16 PM ----------

Im on TMobile - same issues with wireless communication since early August builds. WiFi is weird, Bluetooth is all but broken - some pairing can take place, but a reliable BT link cannot be maintained between the phone and device.
[Verizon Samsung Galaxy S 4] FernBch:
You're not alone. Everyone using jflte has the same issues.
[Verizon Samsung Galaxy S 4] vanberge:
I wonder what the point was of that kernel revamp. Especially if its breaking multiple devices
[Verizon Samsung Galaxy S 4] jkc120:
I think it was to address the UI lockups and crashes and SoD. But in the process it seems to have introduced BT/wifi/data issues that weren't there before :/
[Verizon Samsung Galaxy S 4] FernBch:
The breaking multiple devices part is easy, most all the GS4's now run jflte. Even the Qualcomm international S4 runs it. It's like "all the eggs are in one basket".

There has been some speculation that this may help but it is still under review.

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

I have noticed something else today, may be nothing but again it may be something. I have seen a little activity at JIRA and I just looked over at the changrlog at CM. It has been close to 10 hours since 10/5 hit the buildbot and there is not a single change listed for the next nightly. Maybe we have gotten someone's attention. I would like to hope that something is at least being investigated.

---------- Post added at 11:10 PM ---------- Previous post was at 11:07 PM ----------

At any rate I posted a ton of info over there. Basically I copy and pasted the last two or three big posts I made here over there. Complete with the same detailed descriptions and links to logcats and such. I hope someone finds it useful..........
[Verizon Samsung Galaxy S 4] FernBch:
So much for hopes here.......this has been abandoned.

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

Looks like BT will remain borked for a while. [emoji20]
[Verizon Samsung Galaxy S 4] wowthatisrandom:
I'm taking it as a good thing. That commit didn't fix it and I told him that. At least he acknowledged that and hopefully will look for a real fix
[Verizon Samsung Galaxy S 4] FernBch:
The guys over in the int'l forum are hopin for the same thing.
[Verizon Samsung Galaxy S 4] RustyNailz:
Been running the 10/4 euroskank build for a few days (dirty flashed). Tested BT yesterday and it appeared to be working as expected.
[Verizon Samsung Galaxy S 4] vanberge:
Have you rebooted yet?
[Verizon Samsung Galaxy S 4] RustyNailz:
Yes... multiple times including this morning. I just checked and my BT connect / disconnect is very snappy w/ Ford Sync.
[Verizon Samsung Galaxy S 4] vanberge:
What modem? I had terrible issues on skanks 10/4 with bt and wifi toggling
[Verizon Samsung Galaxy S 4] wowthatisrandom:
skank is CM with a few cherry picks from the CM gerrit, i find it hard to believe skank would have any diff results than stock CM.
[Verizon Samsung Galaxy S 4] RustyNailz:
NC5.

Obviously YMMV, but I'm happy with the results thus far.
[Verizon Samsung Galaxy S 4] djhotpocket:
I'm having good luck with BT myself with euroskanks builds but my GPS is totally screwed and I can't use google maps. Have you tried Google maps?
[Verizon Samsung Galaxy S 4] RustyNailz:
Just did. Initially it showed my position was about 1.5 blocks off. But I walked outside and it quickly locked onto the satellites and corrected the location.
[Verizon Samsung Galaxy S 4] KennyG123:
Probably an Original Development thread is not the best place to be discussing other ROM options

Maybe someone should start a discussion in General regarding other AOSP options and the differences

Let this thread die a slow death but at least let it be on topic

Thanks

FNSM
[Verizon Samsung Galaxy S 4] .Ejekt:
Link to NC5?
[Verizon Samsung Galaxy S 4] phonedawg:
This thread wont die easy - A lot of S4 users use CM - There are many more dedicated threads for each of the other qualcomm variants of this phone and these issues/fixes affect them all
[Verizon Samsung Galaxy S 4] FernBch:
http://xdaforums.com/showthread.php?t=2487298

I'm gonna do everything possible to keep it breathing. And if I can't I will ride the Titanic until the stern disappears under the waves......

I wonder if this will fix the missing mcc, mnc error I saw in Logcat.

http://review.cyanogenmod.org/#/c/73293/
[Verizon Samsung Galaxy S 4] KennyG123:
That's fine. But as rule 15 states, then keep this thread on topic. If you want to talk about other ROMs, take it to the suggested General section. Maybe a lot of other users want to try this and discuss their experience and issues...instead they find a couple of pages of people talking about other ROMs. So please keep this thread on topic.
[Verizon Samsung Galaxy S 4] lx1907:
Anyone else running M9 and using moto360? I was on M10 but reverted back to m9 (flashed clean) due to bluetooth issues. seem to be having pretty crappy battery life both on moto360 and s4 even on m9.
[Verizon Samsung Galaxy S 4] gonzlobo:
With m9, I plug in at the end of an 18 hour day with 40% battery remaining every night.
[Verizon Samsung Galaxy S 4] lx1907:
That's with Moto360 paired ?
[Verizon Samsung Galaxy S 4] FernBch:
Just flashed 10/7. Preliminary status report.

Upon initial boot Wifi and Bluetooth turned on without issue. When WiFi was turned off mobile data would not connect until airplane mode was cycled off and on. Subsequent checks by turning WiFi off resulted in mobile data connecting automatically.

When Pairing my Jabra to my S4 it took two attempts before my S4 detected it. After being paired my Jabra would not connect unless I turned it on first then turned BT on afterwards. After cycling airplane mode I could disconnect/reconnect when turning the Jabra off and back on at will (proper Jabra tone sequence played).

I did see some BT related messages in logcat that indicate all is not 100%, but it is currently functional.

I have not rebooted to see if things are working after. Because I suspect BT is not fixed completely I am not risking a reboot at this time. Past experience (over the last week) has been the whole WiFi/BT/Mobile Data function gets borked and I am not risking loss of functionality. I still think that the three problems are all related.

I also checked GPS and compass. First GPS lock took about 5 seconds. Subsequent locks are very quick. The orientation also seems to be working properly again. Correct orientation locks on quickly and stays correct when the S4 is rotated.

I am also posting this over at JIRA in the nightliey regression section.

Logcat attached:

https://www.dropbox.com/s/pur2t8sa0p9bun5/Log_2014-10-07_19-18-39.txt?dl=0

---------- Post added at 11:19 PM ---------- Previous post was at 10:36 PM ----------

Link to new report @ JIRA

https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/NIGHTLIES-245

---------- Post added at 11:37 PM ---------- Previous post was at 11:19 PM ----------

Auto connect of my Jabra has quit already. It does work to talk and hear in calls but BT has to be cycled if I turn it off while BT is still on (S4 thinks it's connected after I turn it off).
[Verizon Samsung Galaxy S 4] wowthatisrandom:
Looks like m11 is rolling out. Still not fixed based on commits
[Verizon Samsung Galaxy S 4] FernBch:
Agreed. I have only seen one BT related commit and I can attest to the fact it still is not working correctly.

---------- Post added 8th October 2014 at 12:23 AM ---------- Previous post was 7th October 2014 at 11:52 PM ----------

A little tidbit for those waiting for M11, make a nandroid before you flash. Just sayin.............
[Verizon Samsung Galaxy S 4] gonzlobo:
A bit soon for M11 isn't it? I thought they were a monthly gig.
[Verizon Samsung Galaxy S 4] O-T:
There's a massive list of Bluetooth commits added, still pending, waiting to be merged.

http://xdaforums.com/showthread.php?p=55819812
[Verizon Samsung Galaxy S 4] vanberge:
I wonder if it's possible to compile a build with those commits. That'd be sweet to try.
[Verizon Samsung Galaxy S 4] FernBch:
I have seen that list, many are waiting for review and verification.