yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
Flashed both the Aroma and the nano OpenGApps versions, they both crash in flames (something about some wizard crashing etc.), which prompts me to raze the phone and do a clean CM installation. Did I, by any chance, choose the wrong OpenGApps package (ARM 6.0)?
[AT&T Samsung Galaxy S 4 Original Android Developme] awakener777:
Haven't had a problem with Bluetooth
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Do you use a device that has both phone audio and media audio? There's where I keep seeing BT issues. If I disable media audio for my Jabra device, then calls are fine, but if the speakerphone is connected to both phone and media audio, the only way to hang up the phone is to reboot it.
[AT&T Samsung Galaxy S 4 Original Android Developme] awakener777:
So the issue occurs when you are connected to your device and you attempt to use speakerphone? I can test this in an hour and report back.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Yeah, if all settings are checked for the device's bluetooth connection, and a call is made with the speakerphone, the phone acts like it's dialing. It does dial. However, neither side hears any audio (I tested this with my work desk phone and my s4 with my Jabra Freeway sitting on my desk). The only way to hang up the S4 was to reboot it. This happens on every MM rom I've tried so far, and I've even seen that issue reported in Nexus forums, so I know it's not device specific.
[AT&T Samsung Galaxy S 4 Original Android Developme] awakener777:
Oh I follow. I'm not sure that's actually a Bluetooth issue. It happens without as well. I was told if you turn the Google now always listening feature off it won't do that anymore.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Interesting.. I'll give that a try tonight.
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
C'mon folks, am I the only one who's getting this "Setup Wizard has stopped" error? Like I said, I did a clean install of the latest CM13, and then flashed the latest OpenGApps. Upon startup, the "Setup Wizard" crashes, and renders the phone completely unusable. (Could this be because I do not have a valid SIM card? Crossed my mind...)
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
Okay, everyone who is having issues with gapps: IF you read the instructions for flashing gapps 6.0 on Android 6.0 roms, you will find them all saying to NOT REBOOT between flashing the rom and flashing the gapps package. Not only is it not needed, it directly leads to FCs/crashes when trying to use the phone. If you are having problems, you don't need to wipe/factory reset your phone, you just need to format /system, and flash CM-13.0, then flash gapps (TWRP makes chaining them together easy). Sorry that I didn't mention that caveat here, but I have read it multiple places already. See https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Anyone else go from 12.1 to 13 and lose their user dictionary? Google Keyboard is set to sync, and it synced on 12.1. However, even with Google Keyboard set to sync now, it doesn't sync down words.

I even used User Dictionary Backup. No user dictionary moved over to 6.0 :/

Anyone have any helpful tips?

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] gravenailz:
What's with the MOD attached preceding all text on the 4/1 update? Is it an April fools joke?
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Screenshot?
[AT&T Samsung Galaxy S 4 Original Android Developme] MrTravis:
Yes it's a joke. It will be gone in the next nightly or you can go back to the previous nightly.
[AT&T Samsung Galaxy S 4 Original Android Developme] stefan75:
Sorry for the noob question but I haven't flashed a ROM in forever. Is there anything different then going into twrp and backing up, then wiping, flash rom, gapps? Should I update twrp? (I don't remember which version I have) I'm on MDL baseband. Any help would be much appreciated.

Thank you in advance.
[AT&T Samsung Galaxy S 4 Original Android Developme] topiratiko:
Can some direct me to kernels for this device? I cant find anything dev looks dead. I'm on Team Bliss lollipop 5.1.1
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
Has anyone managed to do full remote control of the phone using TeamViewer's Host app? Looks like Host requires an add-on that simply does not want to get installed! (Throws a "No matching activity found" error, whatever that may mean.) And yes, root access has been enabled. Any advice welcome.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
I emailed TeamViewer support for the very same thing. It downloads an addon apk to the downloads folder, but the apk fails install each time.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
Here's another riddle for the connoisseurs: Got an unlock code from AT&T, but I can't seem to be able to get to the point where I can punch it in and unlock the phone (no, I do not have a SIM card). Any advice? I tried a bunch of codes to get it to unlock mode, none works.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Ready for this? It's going to suck. You need to go back to stock TW! AOSP/cm ROMs don't have the necessary apps/libs.. That's what I had to do, too!

Backup via TWRP. Once you flash stock TW (maybe [MENTION=1670609]shoman94[/MENTION] might still have a copy of shostock 8.1 or so archived somewhere) you put in a non ATT SIM card, pop in the unlock code, and it completes, you can restore back to your current ROM setup. It's time intensive, but it works.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
You mean, it won't just work by sticking in a non-ATT SIM card?
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
No, that won't work. I am on ATT, and borrowed my co-workers T-Mo sim. It doesn't work unless you're on a stock rom, due to dependencies with certain apps not found in AOSP and CM.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
Gosh! Thanks! Can you please point me to a recovery-flashable stock ROM?
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
http://xdaforums.com/showthread.php?t=3098197

Yeah, it sucks. When you try a network unlock code on CM/AOSP ROMs, you can input the code, but all it'll do is flash really quickly and fail. There is something system-level that handles it on stock ROMs.

I know it's what worked for me, and I've read it on a few other sites, as well.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
I got an official response from TeamViewer Support.. >.<

>>

Thanks for contacting us. I'm afraid the Add-On, which is needed for remotely viewing and controlling the screen, doesn't work on CyanogenMod or other third-party ROMs.

If you have any further questions about TeamViewer, please feel free to contact us again.

Best regards,

Jeremy Fairbrass

Support Technician

-----------------------------

www.teamviewer.com

TeamViewer GmbH * Jahnstr. 30 * 73037 Göppingen * Germany

Registration Ulm HRB 534075 * CEO: Andreas König, CFO: Stephan Kniewasser

Phone*+49 (0)7161 60692 50** Fax*+49 (0)7161 60692 79

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Additional response from TeamViewer:

it's because the Add-On needs to be digitally signed by the device manufacturer - in this case, Samsung - and the manufacturers will not allow the Add-On to run on their devices with custom ROMs.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] awakener777:
Just posting to say I'm very pleased with the ROM!
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
12.1 is still better than 13 as far as I can tell. The only problem I have run into is that my i337 drops the signal about twice a week. It seems totally random.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
I've been running AOSP 6.0 to see if it has similar issues to CM13. So far, so good.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] cesande:
Link please ?
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
http://xdaforums.com/showthread.php?t=3251663

There are a few issues being reported. Not everyone is experiencing them. The only one I'm having is that if I'm connected to my Bluetooth speakerphone, and disconnect, I won't get sound notifications unless I power cycle the phone.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] MadGoat:
Updated to cm13 and phone app died... Where is our cm13 thread?
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
We kind of just transitioned this one into it, really..

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] lambition:
Which gapps should I install with CM 12.1 20151116 ?

I have tried latest version of open gapps ARM, 5.1 mini and micro and both of them have issue with the keyboard. "unfortunately, Android Keyboard (Aosp) Has Stopped."

Tried CM 13 and gapps worked without any issue, but have issue with bluetooth.

Tried JDCTeam AOSP 6.0.1, have stability issue (usable, but little unstable) and poorer battery life compared to CM 13. :(

Also, for some weird reason, notification from Outlook app isn't working. (Doesn't appear to be syncing automatically).

So, I'm planning on just falling back to CM 12.1 if I can get gapps to work.
[AT&T Samsung Galaxy S 4 Original Android Developme] MadGoat:
So what's this Bluetooth share crashing thing all about...
[AT&T Samsung Galaxy S 4 Original Android Developme] MadGoat:
So far CM13 is great with the one exception of anything bluetooth. Hoping soon for some love there... cmxlog.com/13/jflteatt/
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Good luck with that.. It's every MM ROM, AOSP/CM has some Bluetooth things going on. I'm back on the last CM12.1 build, because I need Bluetooth to work flawlessly. On a few other threads, I've heard that dirty unicorns uses an older Bluetooth commit, so their ROM works. AOSP/cm uses the newer commits, which are having issues for almost everyone.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] MadGoat:
Now there is some handy information! Good to know, thank you! That is a bummer to not have bluetooth working. I really only use bluetooth to steam music in my car and make calls. I found that it works for music streaming if I shut off the call functions of the cars profile. for now that is not a deal breaker. The functionality and speed of the rom otherwise (I feel) makes up for this for right now.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
I know the quick fix for my Bluetooth issues is to turn off media audio when i connect to my Bluetooth speakerphone, but media audio is important for the apps I'm using for work. Maybe I'll give DU a go.. not sure yet.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] |V3nom|:
sorry if this is the wrong place but i didnt want to start a new thread.

is there a thread for cm13 for the att s4? im having a hard time finding a way to put any cm on my phone due to this (from cyanogenmod downloads site):

WARNING:

This guide is for advanced users and does not come with support. It is provided as a means to install CyanogenMod. A working adb connection as well as adb being in your PATH is required for this guide and users should not proceed without this. Additionally,

you must be on build I337UCUAMDB or I337UCUAMDL or this will not work

. In fact, if you try to use this method on a newer revision, you will almost certainly brick your device. Seriously don't try it. Downgrading won't work either. If you've updated, a qfuse is already tripped and any attempt to downgrade will also result in a brick.

my phone is on Build Number LRX22C.I337UCUOC4 and i have yet to find a guide on how to root or put any version of cm on it because its on 5.0.1 already. there are current cm13 nightlies available though as well as a cm12.1 snapshot.

again sorry if this is the wrong place for this but i cant figure this stuff out and any help is greatly appreciated. thanks.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Download CPU X and check the bootloader line. If it doesn't say I337UCUAMDB or I337UCUAMDL, then you're stuck on stock, or safestrap. Search xda for safestrap for more info.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] Tourney3p0:
I've got a couple of pretty severe bugs on the latest 12.1 final. They're severe enough that I would think surely they'd have been mentioned, so maybe someone can chime in as to what I'm doing wrong.

The most important is that sometimes I'll wake up and have no cell service at all even though I should. If I put it into airplane mode, I'm not given the option to come out of it. It's just grayed out. I have to reboot, and then cell service is fine again.

Secondly, bluetooth seems to randomly crash. There are no message boxes or warnings. It just turns off and then won't turn on again. Once again I have to reboot in order for bluetooth to come back.

The bluetooth thing happens once every other day or so. Losing cell service happens maybe once a week, usually while I'm asleep. Any ideas? I'd be glad to provide logs if it would be helpful. Although it sounds like 12.1 development is dead, and 13 bluetooth isn't much better.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
I've been noticing that, too. I'm running 12.1, 0316 nightly, as development of lollipop is totally dead. My cell service will sometimes totally go flatline, and then I get sim card errors. CM13 Bluetooth is the reason I'm still on 12.1. I was going to try the JDCTeam 5.1.1 ROM, but I'm seeing errors still popping up in those threads.. The sim card issue has me worried.. Once that starts, it's only a matter of time before it stops working altogether.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] MadGoat:
Following the CM13 nightly changrlog and I'm beginning to get the feeling that there is not a rush to squash the major bugs with this device and ROM. Really a bummer. I was willing to forgo some Bluetooth connectivity for awhile, but now a dialer and phone problem have come up. Sucks to be on a low dev phone. Stupid new phones stealing all the S4s dev time. :) I guess I'll roll back to 12.1. Are the 12.1 nightlies doing good?
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
There are no 12.1 nightlies anymore. The only download available on the JFLTEATT CM download page is the snapshot from November.
[AT&T Samsung Galaxy S 4 Original Android Developme] MadGoat:
Right... That makes sense. So CM for jflte is dead or broken. Good times.
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
If you want to go back to a lollipop setup, look into JDCTeams' builds. They're in the i9505 forum, but they have a stable 5.1.1 AOSP ROM. They also have an [EOL] optimized CM12.1 ROM that fixed some 12.1 issues.

Sent from my TARDIS
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
What do I do if I get the dreaded "Google Play has stopped working" (or similar) error message? Is this a sign that I need to flash the latest OpenGApps?
[AT&T Samsung Galaxy S 4 Original Android Developme] |V3nom|:
it shows im running I337UCUGOK2 (recent update).

guess ill check out safestrap now.
[AT&T Samsung Galaxy S 4 Original Android Developme] Aqua1ung:
Ugh, I flashed the newest OpenGApps, and now I can't get rid of this pesky Startup Wizard crash. I then tried flashing both the latest CM13 + OpenGApps in one session, to no avail. Please help!
[AT&T Samsung Galaxy S 4 Original Android Developme] MadGoat:
Thanks again!

Running JDCTeams 12.1 and it is smooth. Even went as far as to format F2FS. I am much happier to have a device running the way it should. Dont think I would have found it on my own, so thanks a million.

:good:

~G~
[AT&T Samsung Galaxy S 4 Original Android Developme] mattgyver:
Welcome! Yeah, I went looking because of some issues with CM13. I stumbled upon JDCTeam, and their 5.1.1 AOSP is my fall back for when some MM issues are too much to handle.
[AT&T Samsung Galaxy S 4 Original Android Developme] sjamie:
Anyone having luck with any of the official CM 13 nightly builds?
[AT&T Samsung Galaxy S 4 Original Android Developme] lambition:
Anyone having issue with "SIM card removed" error with CM or other CM based roms?

I read this is hardware issue, so I thought that was the case with me as well. However, suddenly I was getting this error every 10 min or so (random). I never had this issue before switching to CM rom, so I decided to switch back to touchwiz rom and no more issue.
[AT&T Samsung Galaxy S 4 Original Android Developme] MrTravis:
Yeah, I'm getting this to and I can't make or receive calls. My data works fine though so I just use Hangouts and my Google voice number to make my calls.
[AT&T Samsung Galaxy S 4 Original Android Developme] sjamie:
Now may be the time for you to move up to the JDCTeam Optimized CM13 ROM which is running very, very well for me.
[AT&T Samsung Galaxy S 4 Original Android Developme] MrTravis:
Thanks I'll check it out.
[AT&T Samsung Galaxy S 4 Original Android Developme] lambition:
I found that SIM card removed error does occur in original Samsung rom as well, but not as often as in CM12. I did not use CM13 long enough to see how it is.

I had bluetooth issue with CM13. Has bluetooth issue been fixed?

I ended up moving on to Galaxy S7 anyway. I haven't decide what to do with S4 yet. I might use as wifi only phone or sell it. The phone is in perfect shape other than SIM card removed error.

Too bad I ended up buying AT&T version and it has bootloader locked. No rooting method has been found yet. :(
[AT&T Samsung Galaxy S 4 Original Android Developme] sjamie:
Yes, Bluetooth is now stable on the Optimized CM13. My S4 is the AT&T version (jflteatt) and everything is running smoothly with OptCM13. It is the only ROM I've found with stable Bluetooth which is important to me considering I make 97% of my calls via my BT earpiece.
[AT&T Samsung Galaxy S 4 Original Android Developme] |V3nom|:
im having this issue on the stock rom, happens once or twice a day now.
[AT&T Samsung Galaxy S 4 Original Android Developme] Ashyford:
NM
[AT&T Samsung Galaxy S 4 Original Android Developme] FREAK0N:
My BT does turn on and connect with devices... i use a BT Speaker wish worked great before LP...

Now it connect to the speaker and it sounds but sound is horrible...

just flashed 01/26 and problem persist :(

I did a clean install, fullwiped, Nano Gapps and flashed SuperSu.
[AT&T Samsung Galaxy S 4 Original Android Developme] bigal1542:
Has anybody over here tried the unified version of this build? (http://xdaforums.com/galaxy-s4/i9505-orig-develop/rom-cyanogenmod-12-nightlies-qcom-intl-t2999570)

I am just moving over to CM and wondering which one to start with.

Thanks!
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
I don't think that is a unified build. CM moved away from it because of all of the problems different S4 variants had with it on CM11. Anyway that's what I read.

If you are with ATT and have an i337, you need this JFLTEATT build... loki is included, which we need.
[AT&T Samsung Galaxy S 4 Original Android Developme] TLK3:
That's not a unified version. It's for the i9505 only. Will give you an error if you try to flash on anything else.
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
That is for the official build of Cyanogenmod 12 for jfltexx and other nearly identical variants (includes the international S4 and Google Play Edition); AntaresOne has a separate thread that is for a unified unofficial build here. However, you will find some slightly different features, since it has a different kernel, and you will also lose the use of the built-in updater, at least if you want to continue to use that same version of the rom. You will find that some changes may be slightly delayed on that version, and there may be features that are not currently available on official CM12. Also, there may be issues switching at a future point, I can't confirm as I have not used AntaresOne's unified build (unless you switch partitions to f2fs, which at least right now doesn't work with the official build that I am aware of (there have been many commits concerning f2fs recently, but I haven't seen anything that says "yes you can use it" (but I may have missed it)).
[AT&T Samsung Galaxy S 4 Original Android Developme] paul4762:
Anyone having issues with MMS with the Messenger app? Works fine in hangouts just not with the messenger app

Thanks,
[AT&T Samsung Galaxy S 4 Original Android Developme] kswa1987:
none here. t-mobile SIM. works on every nightly I've tried up to 1/27
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
Check your APN settings. Hangouts, just like many other 3rd party messaging apps, can have its own setting for APN. Messenger uses whatever is set in the phone settings. Most MMS messaging problems I've had on smartphones have involved APN issues (which includes my wife's iPhone 6, although I had to change the APN settings there in a very roundabout way). See post 17 on this thread (I'll add that information to the second post later).
[AT&T Samsung Galaxy S 4 Original Android Developme] mikecantreed:
Is anyone having issues with data cutting out periodically?
[AT&T Samsung Galaxy S 4 Original Android Developme] dmb219:
I get "no signal" occasionally if that's what you mean. During that time I have no connection to my phone service. The apn is correct, I tried deleting all the apns except the one I use but it still happened. Pretty much a deal breaker for me. Using an i337 with the latest modem.
[AT&T Samsung Galaxy S 4 Original Android Developme] paul4762:
I checked what hangouts uses vs my standard APN and they are different. I tried to change my APNs to match hangouts with no luck. Online I'm seeing all sorts of different APN configurations. Any chance you know what I should be using for at&t?

Really appreciate the help. Thanks
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
Generally the "ATT Phone" (phone) APN is what should work, it is the current standard APN for new phones (as far as I know); when the Galaxy S4 was released the "ATT LTE" (pta) APN was the default, so it should also work. The "ATT" (wap.cingular) APN was the default for many devices that were released in and before 2011, but whether it will work with the Galaxy S4, I don't know.
[AT&T Samsung Galaxy S 4 Original Android Developme] paul4762:
Here's what my APN says:

APN: phone

Proxy: Not set

Port: Not set

Username: Not set

Password: Not set

Server: Not set

MMSC: http://mmsc.mmobile.att.net

MMS proxy: proxy.mobile.att.net

MMS port: 80

MCC: 310

MNC: 410

Authentication type: Not set

APN type: default,supl,mms

APN protocol:IPv4

APN roaming protocol: IPv4

Bearer: Unspecified

MVNO type: None
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Messaging

I receive but don't seem to be sending. Anybody notice that, or should I just get the next nightly and see if it's working then?
[AT&T Samsung Galaxy S 4 Original Android Developme] mikecantreed:
Are you using the messenger app? I've never been able to get SMS/MMS to completely work with that app.
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
I'm using the one that comes with GAPPS or the ROM. I don't know who provides it cause I've never flashed a ROM without gapps.... anyway, yeah, the stock messaging.

Any of you know of a better SMS apk?
[AT&T Samsung Galaxy S 4 Original Android Developme] paul4762:
I'm having the issues with the messenger app as well for MMS. Can't send or receive them. Works fine in hangouts though