yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] invisiblek:
Clearly you haven't seen some of my rants on other development threads :D

I've linked thejondude's Q/A thread in the OP. If you have a question, that's where it should be. If you'd like to report a bug, with appropriate logs, this is the place for it.

We all know that by the time anyone reads this, it will be buried about 3 pages back in a place nobody will ever see, so its going to continue to happen, always does. Let's be respectful of the people who do post things here that shouldn't be. Clearly they are in the wrong by not reading the forum rules, but we can help by politely pointing them in the right direction.
[Verizon Samsung Galaxy S 4] Jon8RFC:
Gotcha, thanks! Yeah, I couldn't find repositories for a lot of new commits, such as those marked "proprietary."...obviously :(

I attempted connecting to Channel 13, "Jon8RFC", and I disabled authentication and encryption. I booted up, turned on wifi, adjusted the region code. It defaults to US on each reboot (this is not unique to these problematic builds), and disabling wifi then rebooting will seemingly retain the prior region code, falsely, until you enable wifi again:

http://jon8rfc.homeip.net/android/s4/2013-07-01_dmesg01.txt

http://jon8rfc.homeip.net/android/s4/2013-07-01_logcat01.txt

(please let me know if I did something wrong here)

And to clear up things, for those concerned that Channels 12 and 13 illegal here in the 'States, only Channel 14 is forbidden for use. Fewer people will tinker with 12/13 and unknowingly over-boost their signal if it's more cumbersome, and I bet having different gain requirements isn't an easy regulation to explain to the general public, to enforce, or for manufacturers to deal with false complaints and RMAs.

Page 1, Figure 1 shows that 12 and 13 are within the regulated ISM band; Page 2 paragraph 2 details that they are, in fact, legal if your net output is within regulation:

https://apps.fcc.gov/els/GetAtt.html?id=134138&x=.

EDIT: Also, if someone (who is actually a dev) wants to remote in to my machine, I'm happy to make that happen--phone on usb, and you can tinker with my router's wifi if that's helpful for diagnosis. I have a 5ghz as well you can connect to, if that's of any cross-compatibility assistance. I'll purchase the BBQ screen app.
[Verizon Samsung Galaxy S 4] xs11e:
I'm using the stock CM camera, it won't save to SD so I set it to internal storage and it won't save there, either.

Grabbed another camera from the market, it saved the first pic, none after that.

Weird, back to a TouchWiz ROM for now... Can the CM team take a look at this or am I the only one having this problem?
[Verizon Samsung Galaxy S 4] odub303:
The cm camera saves to external sd. Your problem is being caused by something else.
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
You probably have a bad flash.

I would do a clean flash.

Truckin's Galaxy S4 (cm 10.1)
[Verizon Samsung Galaxy S 4] xs11e:
You are correct, it has the option to save there but did not do so. The problem was caused by something else and now we'll never know what????

I switched to my favorite TouchWiz ROM and checked the camera which worked as it should, then rebooted and restored my backup of CM, the June 30th version. The camera worked and saved to the SD card so..... I again tried the July 1st nightly but this time, rather than allow the script to run and do the update, I rebooted into recovery, installed the .zip file and then did a Dalvik wipe before rebooting. So now I'm running CM, the camera works and saves to the SD card.

Whatever the failure might be it was caused by the combination of the July 1 nightly and the auto install script.

Weird problems can often be fixed by rebooting into recovery after getting a nightly update, wiping the Dalvik cache, and then rebooting back to the CM ROM. Previously that's fixed WiFi issues with nightlies, I guess it works for camera gremlins as well.

Devs, would it be possible to modify the update script to do the update and then take one back to the recovery screen (in TWRP) that allows wiping the Dalvik cache before rebooting?
[Verizon Samsung Galaxy S 4] :
I wan't to say that dalvik cache is wiped since on the first boot after an update through cm updater, system "updates" all the apps again, something that always happens after dalvik cache is wiped ( i could be wrong please don't hurt me)
[Verizon Samsung Galaxy S 4] manofcolombia:
If your watching the phone update just wait for the phone to reboot of its done flashing and as soon as it buzzes smack and hold the volume up and boom your back in twrp. I've done it every time so it saves a couple mins of time.
[Verizon Samsung Galaxy S 4] tluley51:
I brought this up awhile ago and did a search and didnt find anyone else with the same problem so I will give it a try again...

I ran CM for about 4 days and switched off. I was getting bad battery life but that wasnt even my main issue.

For some reason, I get terrible lag when trying to lock or shut off the screen of the phone and with CM, it got worse over time. I am finding this to be the case on every AOSP rom though. I cannot believe that it hasnt been addressed or talked about much and this has been around since the Galaxy nexus days. I find myself always locking the phone and in a quick motion putting in my pocket and while doing that, pressing a button before the screen actually shuts off and next time I unlock my phone, something is always pulled up or opened. It is quite frustrating. I am actually on Liquid 2.8 right now after just being on CM and is still doing it. It has to be an AOSP thing now, I figured with my Nexus it could have been limited by hardware but that obviously is not that case with the GS4.
[Verizon Samsung Galaxy S 4] <:GeeK:>:
It seems the only issue I personally have with these builds has been buried and forgotten over the last week. This post is a 'bump' for the issue.

*** In call audio via wired headset does not work on any aosp build for this device, including cm. ***

This bug has been confirmed by many.

Does anyone have any new news?
[Verizon Samsung Galaxy S 4] odub303:
Your bump is pointless without a log. It's been stated time and again to not submit bug reports without logs. If you need to know how to grab a log, ask in the q and a thread.
[Verizon Samsung Galaxy S 4] kclantz:
This was actually fixed on the 6/27 build, and works great. If you are running a build later that and still having the problem then you might want to post a log, as it is likely not related to the previous problem.

http://changelog.bbqdroid.org/#/jfltevzw/1372323055
[Verizon Samsung Galaxy S 4] bik2101:
anyone flash the 7/1 nightly? is it just me or is there a pretty bad echo on phone calls?
[Verizon Samsung Galaxy S 4] jacobk:
yeah, thats the only bug that ive come across. ive been using the wired headset to hear and just speaking into the phone. annoying at best.
[Verizon Samsung Galaxy S 4] mzrdisi:
Anyone else noticed an issue with the stock CM camera, when using another app to post a photo. For instance, using Foursquare and attaching a photo. The camera app loads and the picture review doesn't show. You can hit the confirm button and the picture is there. It just doesn't show for review. I'll try to get a log, if that helps.
[Verizon Samsung Galaxy S 4] <:GeeK:>:
Well apparently you have not looked at the original report. I submitted a log already and so did a few other users, there are plenty of logs showing this issue.

Thank you. This is what I was looking for. I have not flashed a nightly since the unofficial build with IR etc was posted. Will update now.
[Verizon Samsung Galaxy S 4] Jetdr:
7/1 Nightly seems to be running very smooth for me. Phone is not running hot. I have made several calls with no complaints of echoes. I've even made a conference call with no complaints of echo.

Who needs the GE when we have CM. This phone runs so well on CM I might just keep it.
[Verizon Samsung Galaxy S 4] twiz0r:
Known aosp bug...
[Verizon Samsung Galaxy S 4] Sydman:
Sorry
[Verizon Samsung Galaxy S 4] manofcolombia:
Q&A on this thread please.

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

Please leave this thread for developers and big reports WITH logs.

Not only will you get your questions answered better but it will also help the devs by not cluttering this thread up.

Thank you
[Verizon Samsung Galaxy S 4] Sydman:
Apologies, thanks for the direction.
[Verizon Samsung Galaxy S 4] blackhand1001:
The google edition benefits all variants of the 9505 since the drivers from it can be used on all of the snadragon 600 s4's. I prefer CM over vanilla aosp anyway even on my nexus phone.
[Verizon Samsung Galaxy S 4] Jetdr:
I am very aware it helps and has already helped with our phones. The GE edition currently being porting is still in its infancy where as CM is getting very close to being flawless. I was merely reporting how well 7/1 is running for me.
[Verizon Samsung Galaxy S 4] rexdog1888:
I have noticed this as well when using Messenger. The buttons change with the check, refresh/new picture, and x but there is no preview, it just keeps showing what the camera sees. The buttons all perform their functions correctly though.

EDIT: will grab any logs anyone wants when I have access to a computer
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
What are the bugs?
[Verizon Samsung Galaxy S 4] cybereclipse:
Dude...read the OP and/or post on the Q/A Thread. :p Bugs are mainly No IR and a couple misc things here and there.
[Verizon Samsung Galaxy S 4] kclantz:
I have been running the 7/2 nightly heavily since yesterday morning, and have run into a few issues. I did not get a chance to look thoroughly at the Gerrit to see if these are issues being worked on, so I apologize if they are--but hopefully the logs can be of use if they are.

---

The first issue is happening with Chrome, and may not be related to CM at all. It has happened a few times where website will freeze up. The content will be displayed but I cannot scroll, click links, or refresh the page. Killing Chrome takes care of it. It has happened across various websites, so I know it isn't just a glitchy website. The log is attached below (2013-07-03_05.04ChromeIssue.zip) when it happened to me this morning. This very well may just be a problem with Chrome and not the ROM but I thought I might as well get a log and report it in case it is related to CM.

-----

The second issue I found only seemed to start this morning. I made and received several calls yesterday with no problems, however, this morning I experienced the following:

1. First, I made a call, not using a headset. I had no audio at all. See 2013-07-03_05.59.zip below.

2. After this, I made another call, again no headset. This time I had audio in, but no audio out, as the person I was calling could not hear me. See 2013-07-03_06.01_No_Audio_Out.zip.

3. I then received an incoming call and again I had audio in but no audio out. See 2013-07-03_06.01Incoming_Call.zip.

So the audio out issue exists on both incoming and outgoing call.

4. After the income call I restarted the phone and was able to make a successful outgoing call, with audio working correctly. I attached a log of that as well, for comparison (2013-07-03_06.04With_Working_Audio.zip).

I know there were some call audio issues in earlier builds but I haven't experienced those problems over the last several builds. I am about to flash the 7/3 nightly and will test for the problems on it.

Casey
[Verizon Samsung Galaxy S 4] sppatel:
running 7/3 and appears to be running much warmer again.
[Verizon Samsung Galaxy S 4] Cwoomer:
I have been posting pictures of my house to Facebook for the last 3 days using the facebook app and have not had this issue. I have also sent pictures using Twitter and MMS and have not had this issue.

Explain your exact process for posting so that I can try to duplicate.

Thanks:highfive:
[Verizon Samsung Galaxy S 4] DipRip:
I am getting the same no audio issues when answering calls as well as chrome freezing up periodically.
[Verizon Samsung Galaxy S 4] dstreng:
can anyone else confirm or deny these issues? clean wipe or dirty flash?
[Verizon Samsung Galaxy S 4] manofcolombia:
Bump:

Q&A on this thread please.

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

Please leave this thread for developers and big reports WITH logs.

Not only will you get your questions answered better but it will also help the devs by not cluttering this thread up.

Thank you
[Verizon Samsung Galaxy S 4] stackz07:
What is the most stable nightly right now? 7/1? I am coming from Slimbean and am very excited to update to a stable [almost] fully functional rom.
[Verizon Samsung Galaxy S 4] SonicJoe:
I've had no issues with any nightly, but there is a stable release if you want stable.
[Verizon Samsung Galaxy S 4] stackz07:
No call issues? I'll flash the latest and see what's up. In slimbean there is shortcuts on the lockscreen to goto programs from there, does CM have that? I mean the shortcuts above the lock circle..
[Verizon Samsung Galaxy S 4] snagg641:
I had a number of issues with 7/2 in regards to call quality. 7/3 has been fantastic.
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
There isn't a stable release from cyanogenmod. I checked, I don't think there is one yet.
[Verizon Samsung Galaxy S 4] SonicJoe:
You're correct. I lost track of which forum I was in. Derp. :rolleyes:
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
Have you ran into audio issues, or lag?
[Verizon Samsung Galaxy S 4] snagg641:
I haven't run into any noticeable issues. I only use apollo and pandora though.
[Verizon Samsung Galaxy S 4] kvirus11:
Does anyone know where I can find a working volume hack for this phone on CM? I tried one I found through searching and it killed the phone audio altogether and rebooted into a loop.

IF not, then it's a quiet speaker conference call later this afternoon. Thank you in advance for any assistance.

LOVE this after retiring my GNex.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
The 7/3 build has been pretty good for me so far. I had one issue where I answered a call and had no audio...but I hung up toggled Bluetooth and it was back after that. Not sure if the Bluetooth toggling actually fixed it...just a trick I used to do on a past CM phone.
[Verizon Samsung Galaxy S 4] Phobophobia:
I just installed 7/4 after being on 6/8 for a while and have about a 20dBm (!) improvement in signal. I haven't used it for very long but I see no obvious problems so far.
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
If you find anything let me know because I want to flash if its good.
[Verizon Samsung Galaxy S 4] mikeyinid:
If you put your phone next to another s4 you'll see that since the new ril has been merged DBm isn't reported correctly. I've mentioned this before. I always have full bars on any build after I think the 26th of June .
[Verizon Samsung Galaxy S 4] jacobk:
There is no 7/4 build
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
Truckin's Galaxy S4 (cm 10.1)
[Verizon Samsung Galaxy S 4] junkimchi:
There is a 7/4 build... I'm on it right now.

Also a weird note. So I have camera on my lockscreen slider shortcuts, however if I disable slide to the right for camera on lock screen, I can't put the camera shortcut on the slider. Weird right? Not sure if this is a bug or intentional for some reason.

Really would like to just have a clean lockscreen, no widgets on the left and camera on the right, and just a camera shortcut on the slider but as of now its not possible?
[Verizon Samsung Galaxy S 4] gotroot801:
You may be in luck. This change is part of the 7/5 nightly:

http://review.cyanogenmod.org/#/c/45083/
[Verizon Samsung Galaxy S 4] whiteout7942:
I've noticed if I'm streaming music in my car via A2DP and I turn the screen OFF, then I will get occasionally have the audio stutter. It's definitely something with Bluetooth because using line in doesn't reproduce the issue. It's not a lot of stutter but it's enough to be a little annoying. If the screen is on its fine though. Using Poweramp and 7/5 nightly, been happening throughout all the nightlys I've flashed.
[Verizon Samsung Galaxy S 4] jacobk:
so dumb of me, i opened the repo link via pocket which i guess does not refresh the url.
[Verizon Samsung Galaxy S 4] lordgodgeneral:
I ran into an issue, I don't know if it's a bug or not. It concerns the built in Profiles Function and several apps, Email, Outlook and Yahoo. In Profiles, when setting one up there is an option for Lock Screen Mode. My system default is PIN, but I have one profile setup for home that uses insecure. What I've found is when I change from from one Profile to another it messes up settings. Everything works great under the setting they were setup on, but when I change to a profile with a different Lock Screen setting the following happens.

My exchange account quits giving me audibles or the LED on notifications (it will vibrate instead for some reason). Also when I change, it deletes all my accounts on the Outlook app and Yahoo Mail app. Has anyone else seen any behavior like this?
[Verizon Samsung Galaxy S 4] junkimchi:
The lockscreen camera issue has been fixed with the latest nightly 7/5!

You guys are awesome!
[Verizon Samsung Galaxy S 4] v3rn:
Does anyone know of a fix for the Network Extender issues yet?
[Verizon Samsung Galaxy S 4] RGSPro:
A week ago or so the notification sound (like during turn by turn directions or receiving a text message) would simply turn down the playing music while playing, and now it doesn't do that it pauses the music plays the sound then resumes playback. Is there a way to change it back so its more iOS style like it was in last weeks builds?
[Verizon Samsung Galaxy S 4] Berzerker7:
That's semi-dependent on the player being used. GoneMAD still ducks audio for me properly.

On another note: the BT/WiFi issue has been fixed and will be in the 7/5 nightly.

http://review.cyanogenmod.org/#/c/45150/
[Verizon Samsung Galaxy S 4] :
Just a friendly reminder that this section is for posting bug reports with logs. thejondude created a Q/A thread for everything else :)

http://xdaforums.com/showthread.php?t=2346808
[Verizon Samsung Galaxy S 4] ero79:
Is anyone else having GPS locking issues? I'm usually a day or so behind on the nightlies (just put on the 7/5 nightly today) and for the past week or so I'm unable to get a GPS lock.

Went from 6/24 to 6/27 to 7/3 to 7/5 ... feel like it might have stopped around the 6/27 build and hasn't come back.

EDIT: moving this to the Q/A thread...
[Verizon Samsung Galaxy S 4] ThorSkaagi:
Is there a camera app (with photosphere) that works with this ROM? Someone made a flashable zip from June 27th and while photosphere works, every time I go to edit a photo, it force closes.
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
Anyone try the latest nightly?
[Verizon Samsung Galaxy S 4] TheBiles:
Would it be possible to get another unofficial build with the IR blaster working?

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
A official with ir would be better
[Verizon Samsung Galaxy S 4] SonicJoe:
They're working out a way to make it work for all manufacturers. Right now it will only work on Samsung devices. Once they sort it out, it will merge.
[Verizon Samsung Galaxy S 4] km8j:
anyone know how far we are from a release/stable version?
[Verizon Samsung Galaxy S 4] :
http://xdaforums.com/showthread.php?t=2346808

but probably after they fix the IR blaster then we will start seeing some stable releases? just a guess.
[Verizon Samsung Galaxy S 4] theboo7:
Don't forget call sound bugg

---------- Post added at 11:47 PM ---------- Previous post was at 11:46 PM ----------

Source? Not questioning you, just wanna brush up on my knowledge.
[Verizon Samsung Galaxy S 4] barnacles10:
One of the commits for IR can be round in review here.

http://review.cyanogenmod.org/#/c/44580/3

It works and can be cherry picked into current builds but Samsung devices are currently the only mfg supported.
[Verizon Samsung Galaxy S 4] <:GeeK:>:
Compile from source and include the cherry pick linked on post 2.
[Verizon Samsung Galaxy S 4] theboo7:
Thanks, never really went into patch talk.

I'm currently compiling a build with the IR cherrypicked. My source is cm10.1 base, latest commits as of 3:00am Central.
[Verizon Samsung Galaxy S 4] dstreng:
could you possibly post a dl link when done? :)
[Verizon Samsung Galaxy S 4] theboo7:
Will do, was under the impression no one else was up so I was browsing other open commits. I went ahead and started building for ya.

LMK if you have any other requests.
[Verizon Samsung Galaxy S 4] theboo7:
PM Sent
[Verizon Samsung Galaxy S 4] ZonicTH:
Good hearing about an IR blaster build. Can't wait to see the download.

Also. If anyone could point me in the direction of building cm10.1 from source for this device, it'd be appreciated.
[Verizon Samsung Galaxy S 4] barnacles10:
http://wiki.cyanogenmod.org/w/Build_for_jfltevzw
[Verizon Samsung Galaxy S 4] <:GeeK:>:
Why not just post it?
[Verizon Samsung Galaxy S 4] calikorban:
Can you share the dl link or pm me as well..
[Verizon Samsung Galaxy S 4] manofcolombia:
Find it on the first post...
[Verizon Samsung Galaxy S 4] km8j:
Just loaded up the latest nightly after wiping 3x. Everything works great except the camera. It just freezes at a black screen onload. How do I fix?
[Verizon Samsung Galaxy S 4] Crossoverdoc:
Asked this in the Q&A thread and searched for the answer to no avail, so I'm posting this here.

Okay, no idea what's going on. Titainum Backup is saying that the backup directory is not available and it's not giving me any option to backup or restore anything. This is the first thing I tried after flashing and restoring the ID through TiBu.. HELP! Hahah
[Verizon Samsung Galaxy S 4] Seano.:
did you change the original backup directory to something else? if so you need to goto preferences and point it towards that directory.
[Verizon Samsung Galaxy S 4] crookedview:
If you are coming from TouchWiz, you need to change the backup location in TiBu preferences.
[Verizon Samsung Galaxy S 4] Crossoverdoc:
Interesting, thank you both!
[Verizon Samsung Galaxy S 4] Jhvoorhies:
I flashed the chronic kernel and it fixed that issue for me.

via my Samsung Galaxy S IV
[Verizon Samsung Galaxy S 4] sppatel:
try clearing app data and cache
[Verizon Samsung Galaxy S 4] theboo7:
Although that does have IR blaster etc, it is based off a couple weeks old nightly.
[Verizon Samsung Galaxy S 4] noobnl:
Hardware HDR patches are coming to jf

http://review.cyanogenmod.org/#/c/45098/
[Verizon Samsung Galaxy S 4] js2shanks:
Any way you can add widescreen youtube videos for non hd videos? I keep getting grey bars around non hd videos
[Verizon Samsung Galaxy S 4] manofcolombia:
You realize if they stretch that crappy rez image that it's going to look even worse...?

Anyway it's Google own app go complain to them not the cm team.
[Verizon Samsung Galaxy S 4] km8j:
Definitely a bug in 07/05 where if you use wrong pattern, the phone lags so much it is unusable.
[Verizon Samsung Galaxy S 4] DipRip:
Is there any update on the no audio bug (no audio when answering a call periodically) and the call ended bug (call disconnect right when you hit send)? I have been upgrading to each new nightly and both bugs make using the phone very frustrating. Have wiped everything several times with no improvement.
[Verizon Samsung Galaxy S 4] sppatel:
I'm having the following issue where when I'm on a call, (with phone to ear) the screen goes off, but does not turn back on when I move the phone away from my face. After doing some more investigation, I noticed that if I exit the phone app prior to placing the phone to my ear, then I don't have the issue. Screen turns on/off as expected instantly. Only when I place the phone to my ear when the dialpad screen is active is the phone screen unable to wake back up.

Can anyone else reproduce this?
[Verizon Samsung Galaxy S 4] SonicJoe:
I notice the screen turns off while in the phone app, period. Even if you don't put it up to your face, like when using speaker phone, so your issue doesn't surprise me.
[Verizon Samsung Galaxy S 4] Cwoomer:
Does anyone have access to their backed up pics in their gallery? The ones that are not on the phone but are only on google servers?