yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] FernBch:
I had issues with the MJ7 radio as well. I flashed the MK2 modem.bin+nonhlos.bin and haven't had an issue since.

The reason for the clean flash from CM10 to CM11 was simple. Android code change from JB to KK.
[Verizon Samsung Galaxy S 4] Lw00d:
1/29 nightly is out, would like to read what you guys think, about the experience.
[Verizon Samsung Galaxy S 4] jkc120:
Working great so far, and you can save to external sdcard again with the Camera! :good:

Only issue for me is the same one that was on previous builds (not surprised, as again I don't think anyone has acknowledged it) and that is that the software nav bar misses taps/lags. :( Unfortunately, I can't stand the hardware buttons, so the inability to use the software buttons reliably is a deal breaker for me.

Wish I knew how to get a dev to look into the issue. Maybe I'll poke around on irc.

---------- Post added at 09:55 AM ---------- Previous post was at 09:37 AM ----------

Strike that, just had a freeze and now the screen won't come on. it's "alive" because the software keys light up and the charging light works, but the screen won't come on.

Annnnd it finally came back about 30-45 seconds later :/
[Verizon Samsung Galaxy S 4] swordmastr54:
The pics to external is there and it works! And I haven't had the lag yet but I expect its still there other then that its fine so far.
[Verizon Samsung Galaxy S 4] rpitera:
Actually MJ7 was working great for me; my problems only started when I tried the MDK build, so I'm back on MJ7 and all is well (and clear)...

Maybe I'll try the MK2 package you are using. Did you flash it in recovery or Odin it over?
[Verizon Samsung Galaxy S 4] SinfulRoad:
Flash it in recovery.

Sent from my Unicorn'd S4
[Verizon Samsung Galaxy S 4] eikoo:
when will cm11 support landscape mode in launcher 3?
[Verizon Samsung Galaxy S 4] FernBch:
Flashed in recovery. I used the modem+nonhlos package since it goes with the build/kernel.

---------- Post added at 09:48 PM ---------- Previous post was at 09:20 PM ----------

I think I made a discovery. Earlier I posted up asking about wifi download speeds. When I d/l a new nightly it takes 15-20 min to complete. Today I tried downloading the 1/29 build and speeds were around 150-200kb/sec. For S&G's I went through the web browser to download instead and download speeds are up around 3-5mb/sec. I think the issue is with the CM updater. Thoughts?
[Verizon Samsung Galaxy S 4] jorceshaman:
I don't know, I just click directly from the change log to download and it usually downloads just fine so you might be onto something.
[Verizon Samsung Galaxy S 4] FernBch:
Download speeds through the updater slowed around the first week of January. I thought it was wifi related until today.
[Verizon Samsung Galaxy S 4] JaeKay:
I'm still having wifi problems. Spotty at times
[Verizon Samsung Galaxy S 4] vdefender:
WORKING AVRCP on CM11

Alright folks... I have GREAT news. Tonight I finally had the free time to do a full wipe and clean flash to the latest nightly. I also mentioned that I'd report back about getting AVRCP working if you flash back to 10.2 then wipe and flash 11. YES. BOOM. I have AVRCP fully working on todays build of CM11. My car stereo even shows track time and how far into the song I am as well as title album and artist info.

Again here is how to get it working (twice now this has worked):

1: First download the stable build of CM10.2 and download the Google app package for it

2: Then download whichever cm11 nightly you want at the KK gApps package.

3: Reboot to recovery

4: Full wipe

5: Flash cm10.2 and gapps

6: Reboot

7: Connect your phone to your car stereo via BT

8: Log into my Google account and download Play Music app from the market and play a song

9: You should see the AVRCP track info on your car stereo

10: Disconnect your car stereo

11: Reboot to recovery and full wipe

12: Flash cm11 with KK gApps

13: Reboot, sign into Google, get the Google music app, connect to your stereo

14: Play a song and you should have working AVRCP :victory:
[Verizon Samsung Galaxy S 4] KB!:
Wi-Fi Speeds

This is what I am experiencing with wifi... You can see by the screen shot something is not right.... Wifi should be faster than LTE right?
[Verizon Samsung Galaxy S 4] dmarden:
This really makes no sense to me... but, if it's working then it's working. Let us know if it lasts. I just don't see how any of that helps. It's not like you're holding on to stuff from 10.2. Well... unless it is. Beats me.

Either way, appreciate your involvement in testing.
[Verizon Samsung Galaxy S 4] crossen0:
Not necessarily. LTE is way faster in my area than my wifi is. That is until Google Fiber is finished being installed.
[Verizon Samsung Galaxy S 4] vdefender:
It doesn't make sense to me either. The only thing I can correlate it to is the old GPS issues where if you didn't have a lock on 10.2 you could flash back to touchwiz and get a lock then flash 10.2 and get a lock. For reason it seems like the Bluetooth module or the GPS module can be left in a bad state if the ROM thats talking to it is buggy. Buy since cm10.2 is known for having good working avrcp you can sort of preload the Bluetooth module with a good state to give cm11 a JumpStart to work with. But who knows. All I know is that its working and I emplor others to try what I did and get it to work too if they really want it.
[Verizon Samsung Galaxy S 4] rexdog1888:
Only if the internet connection to the router is faster than LTE. Do you get better speeds on other devices connected to that WiFi network?
[Verizon Samsung Galaxy S 4] KB!:
Yes here is a screenshot of my wife's phone... Same wifi...same server... Same S4 but all stock.... So I dont know... I did notice my LTE speeds seem better than hers though so ? Maybe others can test it out and see.... Thanks for the replies
[Verizon Samsung Galaxy S 4] vdefender:
I saw your post this morning so I checked mine. Seems very solid for me. I clean flashed 1/29 nightly last night though.

I will mention that the last couple days I've been having really bad wifi issues, but I have been dirty flashing nightlies for months now and figured I'd just clean flash before assuming it was an issue. After my clean flash last night everything is working great!

Edit: I should mention I was connected to my AC wifi. I didn't try my N wifi.
[Verizon Samsung Galaxy S 4] brandonair95:
Be Grateful for the LTE speeds you have breh. Mine are terrible. Running MDK Modem tho.
[Verizon Samsung Galaxy S 4] Lw00d:
im so jealous
[Verizon Samsung Galaxy S 4] KB!:
I guess I will try a clean flash when I get the time. Thanks for the input.
[Verizon Samsung Galaxy S 4] JaeKay:
I'm having trouble when I reboot. I always have to clear cache and dalvik whenever I reboot
[Verizon Samsung Galaxy S 4] isaacfinnegan:
Anyone having a problem with vibrate mode? I have my phone set to vibrate, but I'm still getting audio reminders firing (for calendar, etc...)
[Verizon Samsung Galaxy S 4] brandonair95:
What trouble are you having? When I reboot it hangs on the white Samsung Galaxy S4 boot logo. A battery pull fixes it. If that's your problem then try that
[Verizon Samsung Galaxy S 4] FernBch:
Which recovery are you both using? There was an issue with this on earlier builds and the solution that fixed it for most was to install the latest recovery (CWM is best but users with TWRP are ok too).
[Verizon Samsung Galaxy S 4] JaeKay:
Twrp 2.5.0.2 I believe

---------- Post added at 05:51 PM ---------- Previous post was at 05:50 PM ----------

Yea i have to battery pull and go back into recovery.

---------- Post added at 06:01 PM ---------- Previous post was at 05:51 PM ----------

Am I the only one with wifi problems? I have to toggle airplane mode to fix it.
[Verizon Samsung Galaxy S 4] brandonair95:
I got CWM Touch and its rebooting again thanks.
[Verizon Samsung Galaxy S 4] FernBch:
I know there was actually a commit to address this, but it may not be a 100% fix. Are you running after a clean flash or dirty flash? If it is a dirty flash make sure to do a factory reset after wiping data, cache, and system. That will guarantee a clean start.
[Verizon Samsung Galaxy S 4] invisiblek:
boot hangs fixed

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

now i can continue on with my life

this should be in tomorrow's nightly (20140201)

EDIT: we also cherry picked it to 10.2, so the immanent 10.2.1 release will have it fixed as well.
[Verizon Samsung Galaxy S 4] jkc120:
So I enabled "show touches" and "pointer location" in developer options and sure enough, tapping on the soft home button shows the tap every time from the debug pointer, but does NOT always register.

As I'm not currently running the build, can someone confirm this is the case if they have sw nav enabled? And if you can reproduce it, is it reproducible in other areas of the screen or only on the sw nav buttons?

Thanks!
[Verizon Samsung Galaxy S 4] mjforte:
How do you enable software navigation anyways?
[Verizon Samsung Galaxy S 4] jkc120:
Standard /system/build.prop edit. Add this line:

qemu.hw.mainkeys=0

To disable, just remove the line.

Reboot is required, naturally. :)
[Verizon Samsung Galaxy S 4] brandonair95:
This actually worked :good:
[Verizon Samsung Galaxy S 4] Stealth Pope:
Hi, I've noticed that when I have my phone in car mode and I access Google Now for navigation or to request a song, I am having problems hearing the Google now voice speaking back. When I use a normal TW rom, I can usually hear it just fine, "Navigating to..." "Playing request...", but when I use the CM11 rom, it very, very, faint or non existent? Is there a fix for that? It's pretty annoying.
[Verizon Samsung Galaxy S 4] jkc120:
Yep it still works fine in kitkat :) Only issue is that the nav buttons don't always "see" the taps. :/
[Verizon Samsung Galaxy S 4] FernBch:
I, personally, think that CM11 is coming along quite nicely. Battery life just seems awesome the last couple days. Right now I'm sitting at 55% battery after 15hrs and 35min of normal usage.

Yeah, there's still a couple quirks. I do occasionally experience the "missed" button touch issue, didn't mention it cause it's has been brought up about 50 times in the last 8-10 pages (ok, ok. They heard about it). And any app that uses the orientation sensor is borked (I'm sure it'll get addressed soon enough). But overall I give it a BIG thumbs up!!
[Verizon Samsung Galaxy S 4] jkc120:
If you are referring to my software nav issue:

a) no, it hasn't officially been ack'd and may not be since it's not an officially supported feature and

b) I'm trying to provide additional info to narrow it down, sorry :/
[Verizon Samsung Galaxy S 4] FernBch:
Not trying to bash or be rude. These are nightlies, and as such, bug reports are not officially collected. This thread is to talk about our issues and experiences which you are fine doing. The developers do visit the thread from time to time, so they are aware of the issue. What usually will not happen is a formal acknowledgement of an issue being reported. You also will not see an ETA on when something will happen. It just happens when it happens. It's just the way it is. If you like you can visit the CM "next nightly" page. It will list what commits are to be included in the next build. Remember CM11 is still relatively young (about 7 weeks) and great progress has been made. I'm sure what you have noticed will be addressed, just can't say when. My mention of it was just to acknowledge that you aren't the only one. Also, FWIW, I have not made the build.prop mod you have and I do see what you speak of from time to time.

Added info:

I see it the most in Gmail. When I open it to see new messages and I load a message I often have to hit the deleted icon twice to delete the message and when selecting multiple messages from the list I often have to select the first message twice before it will highlight.
[Verizon Samsung Galaxy S 4] jkc120:
Thanks! I didn't mean to sound unappreciative or combative. Thanks for the info, that's actually really good info! That means it is not specific to the nav buttons but in the surface flinger itself then?? I am not on cm11 ATM but if you or someone else can test it - would you mind enabling "show touches" and see if you notice a discrepancy between what an app like multi touch test and show touches see?
[Verizon Samsung Galaxy S 4] FernBch:
Experienced something I haven't had on CM in a long time today. I flashed the 2/1 build and got bootlooped. :(
[Verizon Samsung Galaxy S 4] dwhitman:
I got really excited to see this, but...

I do now consistently get through the Samsung logo that often made me do a battery pull, but now I get stuck on the cyanogenmod loading screen and haven't successfully booted this nightly after about 10 tries. Tried clearing cache and dalvik, have not attempted a factory reset. Reverted to an earlier version.
[Verizon Samsung Galaxy S 4] FernBch:
Had the same problem. I just booted into recovery and went back to the 1/31 build.
[Verizon Samsung Galaxy S 4] swordmastr54:
Likewise on bootloop I tried dirty flash then clean install then without KT kernal all of it just bootloop until bat pull but nice to see I'm not alone keep up good work really excited about the next nightly.
[Verizon Samsung Galaxy S 4] eikoo:
yep I factory reset and still fails to boot.
[Verizon Samsung Galaxy S 4] scarmon25:
Same on jflteusc. Know this isn't the right thread for that. But VZW and USC are a lot alike and that's what I'm running now.
[Verizon Samsung Galaxy S 4] FernBch:
At least your on a CM powered GS4. We'll accept 2 out of 3, lol.
[Verizon Samsung Galaxy S 4] JaeKay:
Yup. Bootloop here as well
[Verizon Samsung Galaxy S 4] scarmon25:
Still can help out in here. Did go to the moto x for a minute. But googles sale of moto to lenovo was a ball kicker. So I came back to good ole trusty Samsung. Good thing on USC. No locked boot loader.
[Verizon Samsung Galaxy S 4] SinfulRoad:
Bootloops as well. Don't flash it people.

Sent from my Unicorn'd S4
[Verizon Samsung Galaxy S 4] jfu:
Also get boot loops here.
[Verizon Samsung Galaxy S 4] Lw00d:
boot loop for me too
[Verizon Samsung Galaxy S 4] 32BitWhore:
Same here. With and without KT kernel.

Sent from my CM11/KT Powered Galaxy S4
[Verizon Samsung Galaxy S 4] scarmon25:
Yeah. Its doing it for pretty much all the CDMA builds from what I can tell.
[Verizon Samsung Galaxy S 4] JCBiznatch:
Is there working Wi-Fi hit spot on this Rom?
[Verizon Samsung Galaxy S 4] suoirotoN:
get stuck in bootloop as well.. so I just flashed the 1/31 nightly instead of this one.... dont flash it people.
[Verizon Samsung Galaxy S 4] scarmon25:
I'm not seeing any changes for tonight a build so far. Not sure if there will be last minute fixes to fix the boot loop for tomorrow. I'm gonna keep an eye on it.
[Verizon Samsung Galaxy S 4] MustGoFast:
I'm seeing a fix in the nightly's to fix a race condition on boot... wonder if that's a fix for the bootloops being seen all over.
[Verizon Samsung Galaxy S 4] scarmon25:
I hadn't seen any merged yet. Gotta link. Probably the cm xlog website not working right.
[Verizon Samsung Galaxy S 4] brandonair95:
That was for the 2/01 Nightly and it was to fix the hang on the Samsung Logo when the phone reboots
[Verizon Samsung Galaxy S 4] jorceshaman:
And I don't know but I wouldn't be surprised if that's actually what broke it.
[Verizon Samsung Galaxy S 4] scarmon25:
Yeah. It doesn't take much. Whatever it was it would have had to be a jf common change I would think. Cause it seems to be effecting all the JF builds.
[Verizon Samsung Galaxy S 4] TMYINC:
Basically Samsung's init is horrible. It was limiting the CPU cores being used during the boot up process causing the boot hangs. I'm guessing trying to fix this may have caused the bootloops but that's just speculation on my part.
[Verizon Samsung Galaxy S 4] scarmon25:
I see a commit merged that might fix the booting issus.
[Verizon Samsung Galaxy S 4] linuxthinker:
My experience with 10.2.1 isn't going well and am thinking of switching to cm-11-20140104-SNAPSHOT-M2-jfltevzw. What's the recommended baseband/radio for this? I have an original MDK device running an MJ7 baseband right now. All sorts of stuff when running in GSM mode is broken :(

Thanks.
[Verizon Samsung Galaxy S 4] scarmon25:
I would flash the full mk2 modem package. You can get everything you need from Surges modem thread in general.
[Verizon Samsung Galaxy S 4] linuxthinker:
Thanks for the tip. Full means with non-hlos, is that right?
[Verizon Samsung Galaxy S 4] invisiblek:
Yea...so apparently yesterday's build was boot looping..../me cries

It was completely unrelated to our boot hang fix, this bug appears to have been on a larger scale (at least d2 was affected as well)

I was afk most of the day yesterday, so I didn't get a chance to look into it.
[Verizon Samsung Galaxy S 4] coldhardtruth:
What's the most current KK GApps?
[Verizon Samsung Galaxy S 4] scarmon25:
Yupp

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

So we may wanna hold off on flashing today's build as well?
[Verizon Samsung Galaxy S 4] FernBch:
I have the 2/2 nightly up and running.

Edit:

Working fine so far. Seems to be good to go!
[Verizon Samsung Galaxy S 4] swordmastr54:
That's odd I just tried and it was odd it didn't seem to show my inputs and then I couldn't get it to load back up after bat pull,did you dirty flash or clean install?
[Verizon Samsung Galaxy S 4] scarmon25:
Same here. Did the same thing to me.
[Verizon Samsung Galaxy S 4] FernBch:
Dirty flashed over 1/31.
[Verizon Samsung Galaxy S 4] scarmon25:
Its like the touchscreen just stops responding a few seconds after boot. Weirdest thing I've ever seen.
[Verizon Samsung Galaxy S 4] FernBch:
Kinda sounds like the touch issue is still there. I thought it did the same thing, too. I haven't rebooted yet (didn't think to). I've seen touch issues in Gmail (trouble selecting items) and, now that I think about it, when using the keyboard, too (misses letter when I know I typed it).

---------- Post added at 11:48 AM ---------- Previous post was at 11:47 AM ----------

One of the commits did say something about a 350ms delay, wonder if it's related.
[Verizon Samsung Galaxy S 4] scarmon25:
The 1/31 build works great, haven't had any issues with touch on it.
[Verizon Samsung Galaxy S 4] FernBch:
Hmmm. One of the other users was reporting issues, too. Maybe saying "touch" related isn't the right way to describe it. What I have experienced is every once in a while I have to choose (touch?) an icon twice before the desired action takes place. I can see it highlight the first time, but nothing happened until the second time around. If that makes sense.
[Verizon Samsung Galaxy S 4] scarmon25:
OK. Yeah now I can say that I have seen.
[Verizon Samsung Galaxy S 4] FernBch:
OK, I take back everything I said about the 2/2 build. After reading about turning off and on, I tried it. I turned my GS4 off, then back on. The display is totally unresponsive after a reboot. If I touch an icon all I got was move, edit, delete, etc. But I was done. Only way out was a battery pull. If I revert back to 1/31 and dirty flash 2/2, it works fine as far as I can tell until a reboot. After the reboot you're done.

That said, I have reverted back to 1/31 and, IMHO, I would recommend not flashing today's build either.

---------- Post added at 12:27 PM ---------- Previous post was at 12:10 PM ----------

I just noticed something, i just had a FC with Trebuchet. Problem with that is I don't use it, I use APEX (has a few features that Trebuchet doesn't).

Could the build issue be Trebuchet related? Wasn't it brought back into the build recently? I have seen a few commits for it the last couple days. (Just curious and I could be waaaaaaaay off base here)
[Verizon Samsung Galaxy S 4] scarmon25:
I wouldn't think that would effect touch issues. I may be wrong tho.
[Verizon Samsung Galaxy S 4] FernBch:
Just curious. I'm not a dev and after what happened with 2/2 today I was curious. Probably wrong, but still curious.

Anyway. Thought I'd link to a logcat. Don't know if it caught anything from the 2/2 build or not but here it is.

https://drive.google.com/file/d/0BzP9_0-z4CyhU3hLTFI1S0RzUEU/edit?usp=sharing
[Verizon Samsung Galaxy S 4] brandonair95:
Hopefully tomorrows nightly will be good.
[Verizon Samsung Galaxy S 4] FernBch:
They'll get it, even if it takes another day or two. I haven't seen this kind of trouble since CM9 was ported over to the Photon 4G. Mind you, though, the P4G was a port and there were driver issues cause Moto broke their promise and pulled the ICS release and refused to issue drivers.
[Verizon Samsung Galaxy S 4] linuxthinker:
Thanks! Updated to CM 11 Snapshot (20140104) and MK2 HLOS and Radio -- GSM support is working much better now. Unfortunately, I don't seem to be able to hang up any phone calls. Hanging up leaves it stuck in "Hanging up" until I switch to airplane mode.

Is this fixed in newer builds?
[Verizon Samsung Galaxy S 4] Logano520:
Does anyone know how to fix the problem caused by today's build?
[Verizon Samsung Galaxy S 4] brandonair95:
Just flash the 1/31 Nightly. It's been the best so far and has been the go to build for people who flashed the 2/01.

The problem I had was the screen not coming on during a call. And that's not fixed yet so that might not be either.
[Verizon Samsung Galaxy S 4] scarmon25:
I don't make a whole lot of calls but I haven't really seen the no screen on issue during the calls I do make.
[Verizon Samsung Galaxy S 4] rexdog1888:
I don't know if this is related but when I flashed the 2/2 nightly I had the same problems as y'all and after turning the screen off and back on it was telling me the phone had stopped(com.android.phone or whatever the package is called). After a reboot I still had all the rest of the problems but no phone FC. So again, probably not related but I figured I'd share just in case.
[Verizon Samsung Galaxy S 4] FernBch:
The best fix is to wait for the CM team to fix it. I would imagine that will happen fairly quick (not giving an ETA). They normally don't have long running issues with builds not booting.
[Verizon Samsung Galaxy S 4] scarmon25:
Just had the in call screen issue.
[Verizon Samsung Galaxy S 4] brandonair95:
I can only get the screen to turn on if I have headphones plugged in. If u still have the problem then try that
[Verizon Samsung Galaxy S 4] scarmon25:
So anyone see anything in the chx log that will address the crazy input issue of today's build? Not sure what's causing it so kind of hard to know what to look for lol.
[Verizon Samsung Galaxy S 4] phonedawg:
Are you able to receive any incoming calls? This has been a longstanding issue with GSM.
[Verizon Samsung Galaxy S 4] scarmon25:
Just flashed 2/3 nightly. Seems like everything is good to go
[Verizon Samsung Galaxy S 4] jkc120:
I had one UI freeze (menu button worked, could turn screen off/on), but no taps/swiping worked. After a reboot, haven't had it happen again yet.

Regarding the issue with software nav missing taps, I thinks it's a different issue from the other one reported where you have to hit the delete button multiple times in gmail for example. The reason being, I can't reproduce a missed tap in multitouch test but it does miss my taps to nav buttons (not just home) about I'll say 20-25% of the time. Really bizarre, not sure what would cause that.

I haven't experienced the other issue w/missing taps in apps, only the software nav one.

Other than that, everything seems to work great! :) I just have to decide if I want to live with flaky sw nav buttons or not use 'em and get used to the hardware keys. :eek:
[Verizon Samsung Galaxy S 4] scarmon25:
I've just come to use the hardware keys.
[Verizon Samsung Galaxy S 4] jkc120:
I can't bring myself to do it hahahah!

Well, here's a video showing the issue in case it wasn't clear:

https://dl.dropboxusercontent.com/u/28717002/missed_taps.mp4

And I just had the "system freeze" issue again :(
[Verizon Samsung Galaxy S 4] scarmon25:
When I was on the Moto X I loved em. But personally don't see wasting the screen real estate if I already have em. They are nice though.