yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] klisp:
Ive searched around but came up empty. Is there a method or an app that could let me look at my stuff on my ext sdcard?
[Verizon Samsung Galaxy S 4] SonicJoe:
There's a built in file manager.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
For the no audio thing...as soon as you notice it hang up, toggle Bluetooth on then off, and call them back...always fixes it for me the few times that I've got that.
[Verizon Samsung Galaxy S 4] DipRip:
yeah i have been toggling airplane mode to fix both bugs right now. It is still very frustrating as I always lose that call.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
Agreed...that's what we get for living on the bleeding edge though :P
[Verizon Samsung Galaxy S 4] the.snks:
+1 for the bluetooth issues. I also noticed that I can't fast forward or rewind using the car deck (no response when I try).
[Verizon Samsung Galaxy S 4] bikeboy:
Starting with the 7/6 build I have a small issue with Whatsapp. With each reboot I'm forced to adjust the date/time settings...are you seeing this? When I reverted to the 7/4 build the issue is gone. It has continued with each subsequent build, even after clearing the Whatsapp data.
[Verizon Samsung Galaxy S 4] kreemerz:
I cant seem to get my photos in my contacts to sync or update themselves with this ROM. Anyone know what I can do? I've re synced and restarted but nothing at all. My texts, contacts have blank photos... ugh.
[Verizon Samsung Galaxy S 4] SonicJoe:
What are you syncing with? If its local, you shouldn't have a problem. If its Facebook, you need Haxsync.
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
Google should sync that. Check u your sync settings
[Verizon Samsung Galaxy S 4] Jon8RFC:
Is there a way to check on the status of this issue? Were my posted logs not of any use?
[Verizon Samsung Galaxy S 4] kreemerz:
I thought so. I ran the sync several times and it's not doing it. So, I may need to reflash again? Not sure.
[Verizon Samsung Galaxy S 4] bik2101:
try deleting your google account and re-adding it. worth a shot before totally reflashing
[Verizon Samsung Galaxy S 4] alixyz:
UnOfficial 7/10 Nightly with IR Blaster

After many failed attempts, just compiled an unofficial 7/10 build with the IR Blaster.

cm-10.1-20130710-UNOFFICIAL-jfltevzw.zip
[Verizon Samsung Galaxy S 4] AzureShadow:
Do we have a difinitive existing bug list for the current nightly? I have been thinking of switching but I wanna make sure most functions are working before I do.
[Verizon Samsung Galaxy S 4] teknoprep:
S4 VZW Hang Up Issue

i can replicate this issue 70% of the time

Make a call to any number.. before the timer for the call starts hit end call

Make another call and it won't go through

i have 4 S4's on our corporate account and it happens every time on any ROM of CM on every nightly

This issues does happen randomly also where you won't be able to place a call anymore unless your reboot or you put it airplane and back out
[Verizon Samsung Galaxy S 4] SonicJoe:
How did you do it? I haven't been able to make a build that has working data since 7/4. I even wiped my build environment and started over thinking that something got corrupted.
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
The audio bug got to me so im running a unofficial AOKP rom and haven't had any of the issues that regular cm has.
[Verizon Samsung Galaxy S 4] fallingup:
logcat or it didnt happen.
[Verizon Samsung Galaxy S 4] Delakit:
Lmao. If a tree falls when nobody is around it didn't fall, right?
[Verizon Samsung Galaxy S 4] kclantz:
I have attached a log of the issue, which also includes the work around of switching to airplane mode.

I am pretty sure logs have been posted of this (I might have even posted one myself, I don't remember), so I am sure the devs are aware of the issue. But here is a log for anyone interested.
[Verizon Samsung Galaxy S 4] mattpd00:
Google Voice Issues

Is anyone else having an issue with Google Voice placing phone calls. I'm able to place 2-3 consecutive calls and then the next attempt causes the phone app to lock and never complete the dial. I'm then forced to reboot to regain the use of the phone app. Weird thing is i can receive calls all day with no issue.

I use Google Voice as my primary number and place all calls using GV. From my testing the issue doesn't seem to affect using your provider #. I was curious if anyone is having a similar issue. I will try to post a log file soon.
[Verizon Samsung Galaxy S 4] kreemerz:
Anyone having an issue with the camera freezing up or not responding?
[Verizon Samsung Galaxy S 4] sppatel:
i can reproduce this every time
[Verizon Samsung Galaxy S 4] drt054:
Not a huge deal but the home button no longer wakes up the phone. Anyway to change this? Think it last worked on 7/6.
[Verizon Samsung Galaxy S 4] alixyz:
What OS are you using? and Where did you run into problems?
[Verizon Samsung Galaxy S 4] SonicJoe:
OpenSuse 12.3 x64 is my Linux OS right now. I was building fine from almost day one up through 7/4. The first issue I had with my 7/5 build was that it would not boot. I got stuck at the Galaxy S4 image. So I thought that maybe a vendor blob got updated. I updated to the latest official and tried running extractfiles.sh, but it kept failing on two files (libqm-client-qmux.so and libwvm.so). I tried building without those files, with versions of those files pulled from the GED port, and with versions pulled from the official Samsung stock ROM. I then dug through an official build, and found that libqm-client-qmux.so isn't in the directory that extractfiles.sh is looking in, so I modified it to pull from vendor/lib (which is where the file is located in the official release). I still can't find libwvm.so in the official builds, but because the former file is related to radios, I'm more inclined to think that is my problem. As I said prior, I even tried deleting everything in my build environment and re-initializing.

The problem with my builds is my baseband is listed as unknown and I get no Verizon signal at all. I've been sticking to my 7/4 build for the remote, but testing nightlies here and there ever since. I'm trying a new build tonight. We'll see how it goes.
[Verizon Samsung Galaxy S 4] alixyz:
I got the files from a Stock image, I zipped up all the relevant files that need to be extracted and uploaded them. You can unzip and use the following command for your extract (adjust for directory structures)

./extract-files.sh ~/android/jfltevzw_files/

jfltevzw_files
[Verizon Samsung Galaxy S 4] SonicJoe:
Thanks. Its too late for me to run another build tonight, but I'll try tomorrow.
[Verizon Samsung Galaxy S 4] kluster1999:
Bless you, my friend! Your build is running smoothly, and most importantly, temps are low and my fingers don't burn holding the phone (no case).

:beer::beer::thumbup::thumbup:
[Verizon Samsung Galaxy S 4] durrell12:
I flashed the most recent build and the only issue I'm having so far is the camera. Sometimes it works and sometimes it doesn't. Auto focus is instant sometimes and other times it takes up to 3 seconds. Pretty much unusable. Which really sucks because the rest of the ROM is brilliant.

I haven't had a chance to try Bluetooth in my car yet either.

Hoping once it reaches stable I can run it daily because I hate TW SO MUCH.
[Verizon Samsung Galaxy S 4] noobnl:
call bug issues are fixed.

now fixing lte signal strength: http://review.cyanogenmod.org/#/c/45374/
[Verizon Samsung Galaxy S 4] DipRip:
Oh sweet jesus! I was about to throw the phone through a wall today with the call bug problems. I look forward to installing the next nightly now!
[Verizon Samsung Galaxy S 4] alixyz:
Updated with 7/11 build and bug fixed from previous build.

cm-10.1-20130711-UNOFFICIAL-jfltevzw.zip

Mirror

---------- Post added at 04:00 AM ---------- Previous post was at 03:53 AM ----------

I was able to replicate the no signal issue. Not the smoothest fix, but after the compile completed, I copied the radio files and some additional from the official nightly into my unofficial build and that did the trick.

Below is the link to the files I replaced in my build with the official nightly set:

System_Files

---------- Post added at 04:04 AM ---------- Previous post was at 04:00 AM ----------

You need the following:

http://review.cyanogenmod.org/44580

http://review.cyanogenmod.org/44691

http://review.cyanogenmod.org/44783
[Verizon Samsung Galaxy S 4] teknoprep:
here is the logcat

logcat attached

P.S. i am on the latest 7/11 nightly for JFLTEVZW
[Verizon Samsung Galaxy S 4] danstah:
I am having this same issue. The worst part about the issue where you hit call and it ends that call right away is it will actually call that person and ring 1-2 times. Very annoying. I also get the problem where I go to place a call and I cannot hear anything but the person on the other end can
[Verizon Samsung Galaxy S 4] Cwoomer:
I am not saying that you are crazy , or that I don't think your issue is real. I am on the 7/11 nightly and tried my hardest at least 12 or so times to get this to happen and I can not replicate your issue. I also have not had the random "not able to place a call until I reboot" issue that you spoke of.

Is it possible that this is due to an app that you have installed? As I stated I have tried this on a fresh install of the 7/11 nightly. Coming straight from a freshly rooted back to stock ODIN flash.
[Verizon Samsung Galaxy S 4] tithefug:
I had the "can't make calls issue" this morning. I rebooted and it worked. It may have been Google Voice interfering, but I don't know. Oddly enough, this hasn't happened all week.

Running the 07/06 nightly.
[Verizon Samsung Galaxy S 4] danstah:
Unistalled GVoice and still had the problem on my side. Damn I was hoping this was it. I also found a way to permenantly make it have the issue. Not sure how I did it exactly but I was playing with pimp my rom and did a couple minor tweaks (in the phone section, I think it was the call quality and then another of the checkbox items) and all of a sudden it would do that all the time. I had to actually reflash as I couldn't get it to work again.
[Verizon Samsung Galaxy S 4] teknoprep:
I'll flash back to stock.IMG.

Then flash cm after root process

Then test without installing any additional applications

I'll let everyone know tomorrow

Btw I did get a new phone through Verizon warranty and I had the same issue. That was two days ago and I can replicate this issue on demand as others can
[Verizon Samsung Galaxy S 4] drunkfatjew:
I have had the same issue , Google Voice is not installed. Reboot always fixes. Airplane mode recycle usually does.

Typed with my fat fingers on my Verizon Galaxy S4
[Verizon Samsung Galaxy S 4] DipRip:
I have this same problem sever times a day. I use gvoice and flex dialer. Uninstalled each and the problem still exists
[Verizon Samsung Galaxy S 4] mbh87:
Use a different ROM with the options you are looking for......
[Verizon Samsung Galaxy S 4] gfro9191:
Well, OBVIOUSLY, that's what I've been doing but I don't see how this ROM outperforms others when it lacks such a basic feature in my opinion. I was hoping there was some kind of app or mod that I could apply to do that.
[Verizon Samsung Galaxy S 4] DipRip:
Is words with friends unable to connect and force closing for anybody else?
[Verizon Samsung Galaxy S 4] kratos2027:
Call audio not working when increase call volume is checked under Settings>advanced>sound
[Verizon Samsung Galaxy S 4] Nschneider7:
Anyone having trouble connecting to lte? I've been to two places now where I normally get lte but I'm still on 3g.
[Verizon Samsung Galaxy S 4] SonicJoe:
I'm in a fairly covered 4g area, so I haven't lost it yet. I did notice that on stock, my mobile network is shown as "LTE:14" while on CM it says "LTE:13". But I compared signal on CM and stock and its the same.
[Verizon Samsung Galaxy S 4] Prindle19:
Will nightlies be pushed to goo.im / Rom Manager like they are for the TMO / CAN versions?

I have TWRP working as my recovery and Rom Manager doesn't have support for jfltevzw yet, so hoping that they'll show up in Goo.im and I can grab them through there.
[Verizon Samsung Galaxy S 4] viceversa:
Its built into the rom.

settings-->about phone-->cyanogenmod updates

edit: holy crap member since march 2007. first post today! nice.
[Verizon Samsung Galaxy S 4] spy890:
Anyone else getting excess battery drain? I lost 8% in 2.5 hours of my phone just sitting idle.

Also BetterBatteryStats reports no mobile signal when (I think) the phone is deep sleeping. I wonder if these things are related.
[Verizon Samsung Galaxy S 4] gonzlobo:
Good to see CM for the S4. I'll wait for the Euroskankers to kang this before moving over.
[Verizon Samsung Galaxy S 4] czonin:
I noticed android system took up a ton of battery a few times yesterday.

Also it seems that launchers begin to slow after making a call for some reason. Experienced with both nova and apex on this and aokp.
[Verizon Samsung Galaxy S 4] dobo84:
Battery has been pretty good... But then again I don't really worry about it that much either
[Verizon Samsung Galaxy S 4] vue:
I am having fast battery drain issues as well - haven't seen launcher using it actually most was being used by the Screen, haven't upgraded to latest nightly still on the 06-01.

A very drastic decrease from the stock ROM - not sure what the root cause is.

Using Nova launcher, haven't tried not using one yet.
[Verizon Samsung Galaxy S 4] THATTON:
Fitsnugly already put out one build of Euroskank on Twitter that needed testing. So they're definitely coming. Don't know if it ever got tested. He just needed confirmation that it booted.
[Verizon Samsung Galaxy S 4] dobo84:
Update to the newest nightly and try to let it settle. Seems like the first day setting it up and constantly worrying if everything is working kills the battery fast. The further along they get the better the ROM will get. Really no sense worrying about it till than that's what the bug trackers are for.
[Verizon Samsung Galaxy S 4] keithce:
I agree.

I've been using it like a fiend setting it up and customizing it, but I'm very happy with the battery life even doing that! I've gotten over 3 hours of screen on time using only 75% of the battery. I look forward to settling into a rhythm of updating the nightly and daily use. So far its very promising!
[Verizon Samsung Galaxy S 4] vue:
Another +1 on the battery issue make sure you are using the LATEST nightly build - I installed the 06/02 build and have stopped customizing (as i am all setup now) and battery life is GREATLY improved, almost seems normal, will keep an eye out but seems like all is well with the world again.

:good:
[Verizon Samsung Galaxy S 4] bd1212:
My Messaging app doesn't seem to be functioning correctly and/or is missing some features. When I get a text, it takes about a minute for me to receive the notification from the stock messaging app, while 3rd party messaging apps notify me instantly. Also, there seems to be quick reply options missing that I remember seeing before.

Anyone know how to fix this? It's pretty annoying. Goo was down when I tried to download gapps so I just flashed the gapps package that I used with the unofficial AOKP builds. It was gapps-jb-20130301-signed.zip which I believe is the same gapps that CM used.. or am I mistaken?

I just pulled the MMS.apk from the AOKP builds and overwrote the CM10.1 MMS.apk with the one from AOKP and pushed it to /system/app using root explorer, then changed the permissions to exactly how they were before and rebooted. The new messaging app is now in my launcher, but upon opening it, it force closes. I've done fix permissions in recovery and it still crashes. Any suggestions?
[Verizon Samsung Galaxy S 4] eleazar123:
I was only on stock for about 8 hours, but I think battery life has been incredible on CM compared to my DNA. I've been off charger for 15hours and screen on for 2.5hrs and i'm at 43%. On my DNA i'd be at 10% or less by now.
[Verizon Samsung Galaxy S 4] puma1:
Not sure why, but when I boot into recovery, I don't get a "install from sd" or anything,i get wipe data/factory reset, apply update from adb, apply update from external...

any have any ideas?

When I went into recovery setup in rom manager.. i did not see samsung s4 in the device list either.
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
Try a different rom
[Verizon Samsung Galaxy S 4] danstah:
I've also tried Carbon and AOKP with similar results
[Verizon Samsung Galaxy S 4] Chuckleb0ne:
The latest nightly is running flawlessly.
[Verizon Samsung Galaxy S 4] djdmbrwsk:
What's the date of the build you're running...maybe I'll give that a go.
[Verizon Samsung Galaxy S 4] the.snks:
Second that. A lot of issues were fixed for me (namely Bluetooth).
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
Aokp unofficial 7/7 build

http://rootzwiki.com/index.php?/topic/41529-[ROM]-[4.2.2]-AOKP-::-jb-mr1-::-jfltevzw#entry1258186
[Verizon Samsung Galaxy S 4] junkimchi:
Everything is getting better and better but I still have one very small bug I found

When both lockscreen widgets are disabled so:

- Widget paper unchecked

- Camera widget unchecked

When music is playing, the lockscreen defaults to a screen with music controls on the wrong page and a BLANK page when you wake the phone. This oddly happens even when lockscreen music controls is left unchecked also. And when widget paper and camera widget are checked (3 pages on the lockscreen) everything is ok.

I keep reading about a log file but does that pertain to bugs like this? If so I'll gladly somehow provide one.

So in summary to recreate the issue:

- leave both widget paper and camera widget unchecked in lockscreen menu

- have music playing in google play, spotify, w/e

- lock the phone and rewake, more times than not you'll get a blank screen with the music controls actually on a different page.
[Verizon Samsung Galaxy S 4] Cwoomer:
I can replicate this issue. I am on 7/11 nightly. What nightly are you running?
[Verizon Samsung Galaxy S 4] dickenam:
I used to have this issue. Running http://fitsnugly.euroskank.com/?rom=cm10&device=jfltevzw and it seems to be gone now. I am no longer able to replicate this issue.
[Verizon Samsung Galaxy S 4] The Amorphist:
Problems with 0712 Nightly

Since flashing the latest nightly through Rom Manager, Mighty Text no longer plays nice with my phone.

Worse yet, my text messages themselves are acting VERY odd. Most of my texts will always say "Sending..." now, even thought he recipient responds, clearly having received it.

Mighty Text's symptoms include the PC app claiming the message isn't sent, not seeing the message com up in my Messenger App, but the recipient responding like they've received it. Sending is VERY erratic though; maybe 1 in 2 texts I send from the PC actually get to where it is going.

I have wiped cache and davlik and reinstalled the ROM and Gapps. Trying to avoid the factory reset if I can.

Cheers,

Amorphist

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

FTR, reverting to the 07/11 build without any other flashes fixed everything in a flash.
[Verizon Samsung Galaxy S 4] phonedawg:
I use my homescreen in landscape a lot. I can't do that with CM 10.1(for Verizon GS4) because of what seems to be a bug.

In Settings>Launcher>General, check 'Auto-rotate Screen'

Then, when the homescreen is in landscape, dock icons do not respond to touch.

Can someone confirm this bug by replicating?

I have attached the log where I tried to touch(open) the 'app drawer' icon from the dock.
[Verizon Samsung Galaxy S 4] junkimchi:
The lock screen music control issues are happening for me on 7/11 nightly also

EDIT: Once again the devs are phantoms. The issue seems to be solved on 7/12 nightly

EDIT2: There is even a stranger bug in the 7/12 nightly now though. Like Amorphist mentioned, in Messager, when you send a text, it forever says "sending" even when the message has been sent and the other person replied! Looks like it is already resolved in the next nightly thought: http://review.cyanogenmod.org/#/c/45444/
[Verizon Samsung Galaxy S 4] Alexithymia2010:
I flashed the 7-12 nightly quickly today to see if it ran well, and I experienced the same issue. It was a FRESH flash too, since I was running TW before. I'm sticking to TW as usual until this gets fixed. Apparently it's been fixed in 7-12 but I'm gonna compile an unofficial build tonight and see if it's fixed.
[Verizon Samsung Galaxy S 4] rexdog1888:
Just saw this but it still does it so I'll answer.

Open Messenger, choose conversation, click the plus in the bottom left corner, click take photo
[Verizon Samsung Galaxy S 4] Cwoomer:
OK. Now I see it. I never post pictures that way. I was able to reproduce the issue however.
[Verizon Samsung Galaxy S 4] phonedawg:
Issue still exists on the 07/13 nightly. It is actually a major and very annoying bug. I cannot use this phone in my car(in landscape) at all since I can't access(open) the dock(icons).
[Verizon Samsung Galaxy S 4] dorioo:
Consider using Nova Launcher (replacement Launcher) while you wait for a fix. Icons work in landscape now with it.
[Verizon Samsung Galaxy S 4] teknoprep:
Where it's the tracker or bug list for this phone

I don't want to post this stuff on the forums anymore as its not really what it's for
[Verizon Samsung Galaxy S 4] SellswordShev:
Got a weird problem with streaming A2DP to my car's bluetooth audio adapter (worked perfectly fine on my old Galaxy Nexus). I'm having some trouble reproducing it, Ill post a logcat next time it happens. The issue occurs when I hit play on any media app (so far tried youtube , play music, pocket casts), the entire UI will freeze until something forcloses, or I turn off the bluetooth adapter to kill it's connection. This seems to happen pretty randomly, as I've had cases where hitting play just works and no interruptions for 1+ hour. I'm on the 7/09 build where everything else is running fine for me so I am hesistant to upgrade since people seem to be having issues with calling etc on following nightlies.
[Verizon Samsung Galaxy S 4] SonicJoe:
Thanks for your help. I used your zip as a guide and replaced files in my unofficial 0713 build (with IR) from the official 0713 nightly and its working fine now. I wonder why its not building right anymore though? I was fine until 7/4.
[Verizon Samsung Galaxy S 4] alixyz:
I'm no expert to answer that :) The 7/10 and 7/11 were my first 2 builds which I've compiled.
[Verizon Samsung Galaxy S 4] manofcolombia:
So... I flashed today's nightly and then chronic kernel over top came out oc then went to benchmark and then said I wasn't rooted...? Went back to system tuner... The oc stuck and the gov too but now I can't change the settings...? And root checker said the same?

---------- Post added at 03:00 PM ---------- Previous post was at 02:51 PM ----------

I reflashed the kernel... Still have twrp... But it told me I'm not rooted blah blah blah would you like twrp to install su user... I hit no because I hadn't backed up a couple pictures yet and yea so... What's going on? Kinda bizarre... I did skip a couple nightlys this week and went from 6 to 13...?

I'm thinking it's Chronic's problem but... I'll probably flash cm stock and see if that's the issue
[Verizon Samsung Galaxy S 4] km8j:
I'm on the 07/05 and HDR doesn't work for me??
[Verizon Samsung Galaxy S 4] danstah:
I don't think I've had HDR work on any AOSP ROM I tried.
[Verizon Samsung Galaxy S 4] juanzho11:
07/12/13 It's working for me. Not sure what's supposed to do but I click on it and the definition gets better.
[Verizon Samsung Galaxy S 4] phonedawg:
Try taking a HDR picture. A blank(unrenderable) picture gets taken and the camera screen (viewfinder) hangs right after.
[Verizon Samsung Galaxy S 4] OneNutShort:
I second this. You shouldn't see any "definition" change when HDR is enabled. It only becomes apparent after you've taken the image and the three exposures are merged. And then it has nothing to do with definition, but tonal range, showing a wider range of tones than a normal picture could capture.