yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Original Android Developme] dmb219:
I like Textra, it works well for me and I like the look. Check it out if you haven't already.

---------- Post added at 02:53 AM ---------- Previous post was at 02:20 AM ----------

The boot animation has gone dark thankfully...:p
[AT&T Samsung Galaxy S 4 Original Android Developme] awakener777:
Yeah I figured I'd try this. I get no signal periodically. Not sure how to fix this but it used to be the same on antaresone's cm12 optimized ROM. The last couple updates fixed it, however. There were other reasons I decided to try official. I'd like to know what commits he did to fix it.
[AT&T Samsung Galaxy S 4 Original Android Developme] mikecantreed:
So it's fixed on Antares optimized but not on CM official?
[AT&T Samsung Galaxy S 4 Original Android Developme] awakener777:
That was my experience on the 1/25 build, yes.
[AT&T Samsung Galaxy S 4 Original Android Developme] Vcolumn:
the last few official nightlies from here have greatly improved my cell signal/strength. Prior I a had few complete signal losses in known good areas, but more so i had constant jumping from LTE to H+. The LTE has been very reliable the last few days with no signal drops and the new toggle has been performing properly for me as well.

i did as dmb219 suggested a few posts back, and deleted all the APNs except the 2 main AT&T ones. ATT Phone and ATT LTE. Been dirty flashing about a week.

something elese i noticed is that since i uninstalled Google search, there is a grey box at the top of the recents menu where the search bar was that says, "Couldnt Add Widget". No biggie, just kinda ugly.

MDL bootloader NJ4 modem

there is a zip floating around of the newest alucard jflte kernel ripped from the unified optimized JFLTE of anteresOne and alucard. Works well.

titanium backup has been updated and working properly with the built in SU

:highfive:
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
Have you tried Apex? All sorts of features!

---------- Post added at 07:18 PM ---------- Previous post was at 06:52 PM ----------

Textra is working well... thanks for the tip! Nice app.
[AT&T Samsung Galaxy S 4 Original Android Developme] gho5t82:
Chompsms by far

---------- Post added at 01:12 PM ---------- Previous post was at 01:08 PM ----------

Point me in the right direction for the zip?
[AT&T Samsung Galaxy S 4 Original Android Developme] Vcolumn:
its in the jfltexx thread, is still unified and lokis if needed

http://xdaforums.com/showpost.php?p=58531959&postcount=1065
[AT&T Samsung Galaxy S 4 Original Android Developme] awakener777:
Agreed, greatly improved. I didn't delete any APNs
[AT&T Samsung Galaxy S 4 Original Android Developme] Vcolumn:
404 NOT FOUND for the 02-05 nightly. Verizon and international 02-05 available. jenkins says it completed :confused:
[AT&T Samsung Galaxy S 4 Original Android Developme] FREAK0N:
cm-12-20150206-NIGHTLY-jflteatt.zip is ready :D
[AT&T Samsung Galaxy S 4 Original Android Developme] dmb219:
Did a fresh install of 2/6/15, got everything set up, apps in place, looking good and lost cell service again. Keep trying every few days but no luck. I'm hoping for a fix but thinking maybe this is as good as it will get for the old S4:(
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
No way. CM12 is running better every day. Also, I stream radio for an hour every day and have not run into any network problems. I don't lose service, which leads me to believe that your problem are phone (or modem) specific. Have you tried other modems?
[AT&T Samsung Galaxy S 4 Original Android Developme] jsmith8858:
FYI: CM12 was running very smoothly for me (clean install of 2015-02-04 Nightly with only minimal app restores from Titanium) until I updated to today's nightly (2015-02-07) . After updating the phone completely hung up, and that kept happening even after rebooting 3-4 times and wiping cache.

It may have just been me or something specific to my configuration, but consider avoiding the 2015-02-07 nightly if you are thinking of updating, there may be an issue with it.
[AT&T Samsung Galaxy S 4 Original Android Developme] TLK3:
Anyone else getting stuck at boot logo after dirty flashing 02-04 onward? If a clean flash is needed so be it. But I'm not going through that hassle only to have the same issue. Thanks in advance!
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
hmmm... I have been updating like every other day or so with CyanDelta with no problems at all. Try the newest nightly if you can get into recovery.
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
I ran into something from a commit made on 02-01 or 02-02, I didn't need to do a wipe, I just formatted /system and reinstalled current CM and GApps, and it booted fine.
[AT&T Samsung Galaxy S 4 Original Android Developme] Locoman_:
Other recoveries didn't help and manually wiping the system partition didn't help either. Recovery still thinks its the wrong device, though it isnt. Anyone know exactly where twrp finds the device info so I can flash this rom? This is getting crazy.
[AT&T Samsung Galaxy S 4 Original Android Developme] Vcolumn:
if you reboot to download mode, what does it say in the top left corner next to product name?
[AT&T Samsung Galaxy S 4 Original Android Developme] Locoman_:
it has the right phone there, the I337. and another poster on another thread asked if i have a locked bootloader and i don't. mdl and i vsnd flash every release of dan's gpe. i wonder what the issue is?
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
You could always ODIN your phone back to factory stock MDB. I've never tried this.

http://xdaforums.com/showthread.php?t=2261573
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
You may have gotten into a self-perpetuating loop, where the rom identified itself as jgedlte to the recovery installer, and so the recovery is identifying itself as jgedlte (This is personal speculation, and probably isn't the truth).

The recovery has its own build.prop (for CM12's version of CWM, it is called "default.prop"). If you were able to mount the recovery partition, you could change it directly there; another method is to not use a recovery flasher, but instead download a version of CWM or TWRP that is specifically for jflteatt and flash it using dd (be VERY, VERY careful), which will force flash whatever partition is set as the destination (hence the "be VERY, VERY careful"). Also, if you wanted to confirm what the recovery has set for the ro.product.device or ro.build.product, you can use adb to access a shell while the recovery is running, at least when using CWM (I can't confirm for TWRP). But I would say that your flashing problem is with the recovery, not with the ROM you currently run, so wiping the system partition will obviously have no effect on whether it is allowed.

The safest bet for you to get CM12 for jflteatt installed (as long as your bootloader is MDB or MDL) without going back to stock temporarily is probably changing the values on the first line in updater-script in a CM12 jflteatt install zip from jflte to jgedlte (download the zip to your computer, extract it, modify zip/META-INF/com/google/android/updater-script, re-zip the files in the directory, and copy the modified zip to your phone). This will allow the initial flash of CM12 for jflteatt, after which you should re-flash the recovery so that whatever is flashing it flashes a version with the correct device identification values. After doing that, you should no longer have problems flashing.

NOTICE:

This should only be necessary if your problem is the one shown, where the recovery is not identifying the phone properly. The updater-script modification would allow using this trick to install CM12 on the I337m, but would require modifying the script on all updates as well, and could cause other problems when using your phone.
[AT&T Samsung Galaxy S 4 Original Android Developme] Locoman_:
Thank for this, it makes sense given my experience. I'll try to figure out how to mount and edit twrp. Barring that, I'll conider odin-ing back to stock (ugh). Again, thank you for your help!

Edit: I figured it out! After using Dan's GPE rom, I updated TWRP with Flasher. It must have updated the recovery to a jgedlte specific twrp. That's why it wouldn't allow me to flash a jflteatt rom. So I made the build prop edits changing everything I could to from jgedlte to jflteatt and after a reboot used Rashr's recovery tool (in the play store) to verify that it's flashing an ATT specific twrp and no more problems. Thanks to everyone that offered help.
[AT&T Samsung Galaxy S 4 Original Android Developme] paul4762:
So far this ROM is great! Wanted to say thanks for all the hard work first! I did a full wipe any only have 2 issues that may or may not already be known.

1. In hangouts if I use the front camera after 1 or 2 pica the crashes the front camera.

2. I can't use the google "messenger" app from the play store for MMS. The ROM "messaging" app and hangouts and all other apps work fine for thus. I checked my APNs and they are all configured correctly.

I really appreciate the help, thanks!
[AT&T Samsung Galaxy S 4 Original Android Developme] FREAK0N:
Bluetooth sound fixed

Jumped from cm-12-20150201-NIGHTLY-jflteatt to cm-12-20150209-NIGHTLY-jflteatt and the problem i had with bluetooth speakers got fixed... excellent ROM...

thanks for everything. :):D
[AT&T Samsung Galaxy S 4 Original Android Developme] DeNitE:
I know this was kind of dealt with at the beginning of this thread... But is there any way to get this working on a Canadian variant?

Is it possible to adjust the build prop files to enable it to install?
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
See post 80 in this thread, and post 2 in the Q&A thread. You will want to appropriately edit the build.prop afterwards, and will need to do the same with every update.
[AT&T Samsung Galaxy S 4 Original Android Developme] DeNitE:
Thanx so much, I appreciate it :)
[AT&T Samsung Galaxy S 4 Original Android Developme] ninja_rancher:
Each time I install a nightly, the media scanner creates duplicates of any pictures and videos I have on my external SD card. Not of anything on the internal storage, though. I have to clear data on media storage, restart, wait for it to rescan everything, and then set up all my notification sounds and ringtones again. Kind of a pain.
[AT&T Samsung Galaxy S 4 Original Android Developme] Locoman_:
This isn't happening to me. Obviously your issue isn't getting fixed by dirty flashing a new nightly. You should do a full wipe - as in wipe system/data/both caches/internal and external cards then a clean install.

PIA but it should fix your problem.

.
[AT&T Samsung Galaxy S 4 Original Android Developme] Locoman_:
LOVE THIS ROM! ... is there a chanelog associated with the builds?
[AT&T Samsung Galaxy S 4 Original Android Developme] Lord_Micron:
http://www.cmxlog.com/12/jflteatt/ ;)
[AT&T Samsung Galaxy S 4 Original Android Developme] awakener777:
Alternatively, you can click on an available update in your settings under about phone>CyanogenMod updates to show the changelogs since your current version.
[AT&T Samsung Galaxy S 4 Original Android Developme] mikecantreed:
I'm on 2/12 and still getting the signal drop randomly and always after I end a call. Is the default fix still to delete unused APNs?
[AT&T Samsung Galaxy S 4 Original Android Developme] awakener777:
IDK of a fix. Does that work effectively?
[AT&T Samsung Galaxy S 4 Original Android Developme] awakener777:
Is anyone rise having issues installing apps that are not from the play store? I always get a message saying app not installed.

Edit: issue solved
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
For me CM12 has now become my ROM of choice... good enough to be my daily driver, and with enough options so that it is a pleasure to use. I only mention this for those of you, who like me, were waiting before migrating because CM11 is so darn good there was no good reason to switch. There is a good reason now. CM12 is better. After 2 days I can report no signal drops, no Bluetooth problems, and excellent battery life. I have not had 1 single problem. Even my ir remote works beautifully.

I dirty flashed over CM11 about 2 weeks ago and have been going back and forth between 11 and 12, updating CM12 every other day through Cyandelta without issue.
[AT&T Samsung Galaxy S 4 Original Android Developme] dmb219:
I've tried deleting all apns but ATT phone which my phone uses but I still get the occasional drops. I've also tried 4 different modems with no difference. I've had dozens of roms on my phone and have never seen it drop cell service. We'll see what happens, cm improves every day (or almost). :o
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
So I finally took the plunge and upgraded from CM11 to CM12. Overall the ROM is near perfect. Good battery life, no real unexpected quirks. I have a few very minor things to report. The cLock widget has no settings. They used to be found in the main settings app under lockscreen or something. I searched far and wide and found nothing. I found that if I remove the widget from my home screen and re-add it, it gives me the opportunity to configure it. (crisis averted)

This is also similar to the fact that I can't find a way to add cLock or any other widgets to the lock screen. Again, I'm very new to lolipop and maybe I'm just missing something so I'll keep searching.

Finally, there is no exchange support in the stock email app. It's not the end of the world because Gmail supports exchange and there is an official outlook preview app from Microsoft.

No bluetooth testing yet. President's day off from work. I'll try it tomorrow when I get in the car.

If anyone else has been holding off, I don't see any reason not to jump over to CM12. It has tons of features and customization options now.... rock solid and good battery life.
[AT&T Samsung Galaxy S 4 Original Android Developme] Kevinnme:
Play music wifi problem

Awesome rom, but I don't know if this is rom specific. When I use google play music app, it does not stream songs I have in my library through wifi, but only through mobile data. If I use chrome to open google play music website, it works fine. Just wondering if anyone is having this problem.

Edit: the problem went away, i don't know how...
[AT&T Samsung Galaxy S 4 Original Android Developme] imjohnh:
Did you do anything outside the usual to flash this? I remember back in the Days of CM7 & 9 that the AT&T radios weren't ideal for Canada (Bell/Telus HSPA+ network) so I would flash a different modem. Did you wipe or cache/Dalvik only?

I have an S4 as a secondary device to my OPO, and I would like to upgrade to CM12 if it's not a giant hassle. The radio silence from CM suggests there may not be a maintainer for a Canadian S4 variant for CM12 anytime soon, and I'd like to get both handsets on the same OS version.

T.I.A.

JH
[AT&T Samsung Galaxy S 4 Original Android Developme] *child:
I just edited the updater-script to allow for jfltecan. To my knowledge, the two devices are identical in hardware so I don't think flashing a radio will make much of a difference. Installing CM doesn't change the radio either, so just flash CM, it will keep the current radio there.
[AT&T Samsung Galaxy S 4 Original Android Developme] imjohnh:
in the pre-LTE days on Bell/Telus' HSPA+ network, there was frequency (can't remember what it was, that was used in rural areas in Canada that AT&T didn't use. Obviously w/ LTE things are a little different.

Thanks for the reply.

Cheers,

J
[AT&T Samsung Galaxy S 4 Original Android Developme] imjohnh:
last question I promise. I am assuming you mean editing the build.prop file in the ZIP to replace jflteatt with jfltecan or append jfltecan somewhere?

I've never edited an installer script before and don't want to eff it up. If there is a tutorial post somewhere in here, just let me know and I'll search it.

I wouldn't normally go this deep into mucking around, but I suspect that there won't be a jfltecan ROM for CM12.

thx,

J
[AT&T Samsung Galaxy S 4 Original Android Developme] snakecharmer23:
Bluetooth

So I finally got a chance to test bluetooth. I tried it in my car and with a portable speaker. The portable speaker, a Monster iClarity, never successfully made a connection. It was able to connect phone audio but not media audio. It just sat at connecting indefinitely. I tried rebooting the phone and speaker but got the same thing.

Things worked a little better in my car. I have a Kinivo BTC450 hands-free car kit. I was able to connect and stream music using Google Play music for about 15 minutes. Then between a couple of songs it stopped and a message popped up. "Unfortunately, Bluetooth Share has stopped."

That was the end of that.

I'm not asking for help fixing anything... I'll hunt around and see what I can find. Just reporting my findings.

FYI, clean flash of 02/14 nightly with PA modular micro gapps and no custom kernel.
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
Well

I Did a clean flash of CM12 yesterday on my AT&T phone.

I wish I could say I had as positive experience as some of those above.

Of course I lost root and had to get the zip flashable SuperUser

Which Gave root to Titanium Backup...until I restored my messages,

then TB no longer said there was root.

Re-Installing TB had no effect, trying to un-install SuperUser was a no-go, it would not un-install.

I also flashed the MiniGapps package.

The google Voice Search widget doesn't appear to be removable (I must be missing something)

I was not able to find an option to change the duration of the hard Key lights. (I prefer that they remain on when the screen is on)

When bringing the screen up swiping always went straight to phone (this happened after I installed GApps)

After those problems I Recovered back to CM11.

I will try to dirty flash since someone said that worked swell for them.

Yes...It could be user error...but....
[AT&T Samsung Galaxy S 4 Original Android Developme] Locoman_:
You have to enable developer options, then allow root in the settings.
[AT&T Samsung Galaxy S 4 Original Android Developme] JohnMcW:
ok

OK,,,,so you went through my whole message and determined it was User Error.

I hate it when that happens.

Just Kidding,,,thanks a lot, that fixed everything.

I Started with a clean install and after enabling root in Developer Options Everything seems to be working.

Although I opted to install the pa_gapps-modular-pico this time.

Thank You much for your response.
[AT&T Samsung Galaxy S 4 Original Android Developme] DeNitE:
My WiFi seems to disconnect every night while I sleep... and doesn't connect back again due to an authentication error... When I click my WiFi in the AM, it connects perfectly...

This happens on my tablet with CM12 as well...

Is this just a CM12 bug that needs to be resolved still?
[AT&T Samsung Galaxy S 4 Original Android Developme] ninja_rancher:
I can confirm that this happens to me most every night too. And it's not only the Wi-Fi I'm currently connected to at home, but does the same thing when I get to the office. I plan on starting clean soon to see if some of the other issues I'm having go away.
[AT&T Samsung Galaxy S 4 Original Android Developme] *child:
No. I edited the meta-inf/com/google/android/updater-script file. The line, usually the first line, beginning with assert(getprop("ro.product.device") == ... controls which devices on which the zip can be installed. Comment out this line by placing a # at the beginning and it should allow the zip to be installed on jfltecan.
[AT&T Samsung Galaxy S 4 Original Android Developme] DeNitE:
Here's my updater script for JFLTECAN... Works great :)
[AT&T Samsung Galaxy S 4 Original Android Developme] imjohnh:
thanks muchly!

J
[AT&T Samsung Galaxy S 4 Original Android Developme] Latty:
I didn't have to do this using a unified jflte TWRP... Just flashed jflteatt with no issues =)
[AT&T Samsung Galaxy S 4 Original Android Developme] geomax45:
Where, my friend, did you find such a thing?
[AT&T Samsung Galaxy S 4 Original Android Developme] 1weener:
An i337 is an ATT S4 so of course jflteatt flashes without issue since that's what it's for.

There is no such thing as a unified TWRP. You must be very lucky!
[AT&T Samsung Galaxy S 4 Original Android Developme] leos0000:
Can i flash on i337m canadiaen?
[AT&T Samsung Galaxy S 4 Original Android Developme] Latty:
I'm using AntaresOne's modified twrp for the i9505. It flashes the jflteatt cm12 onto my jfltecan device with no change in the build.prop

https://www.androidfilehost.com/?fid=95916177934533182
[AT&T Samsung Galaxy S 4 Original Android Developme] mikecantreed:
I'm on 2.21 and still getting signal drop. Anyone else? Any new troubleshooting tips?
[AT&T Samsung Galaxy S 4 Original Android Developme] FarmGeek4Life:
Probably because it has the recovery product.name and product.device properties set to jflte.

There are a couple of commits in the works for jfltecan to eventually get it to official nightlies for CM 12, but testing is a problem (for me, anyway). The cm-12.0 branch for jfltecan now exists, and there is a commit up on gerrit to provide the necessary updates for CM 12 (which does build). If/when it gets tested and verified for functionality, it will be submitted and nightly builds should start soon after that.
[AT&T Samsung Galaxy S 4 Original Android Developme] ninja_rancher:
Can't give you any troubleshooting, but I'll chime in that I'm in the same boat. Did a CLEAN (formatted EVERYTHING) install of 2/22 and I get intermittent mobile data signal drops. Doesn't seem to affect Wi-Fi, just mobile data. In addition, I sometimes get the message that the SIM card has been removed and I have to reboot to recognize it again. And, after a reboot, it usually takes upwards of 30 seconds to get a mobile signal at all--Wi-Fi is immediate. I've tried with NC1, NI1, and NJ4 modems with no difference. I had absolutely no issues on CM11, so I'm hoping it's something about Lollipop and the GS4 that just hasn't been ironed out yet.
[AT&T Samsung Galaxy S 4 Original Android Developme] ninja_rancher:
And adding to the list of things that fail intermittently, I lose connection with the front camera at times. Trusted face unlock will stop working and when I launch the camera app and switch to the front camera, it will say unable to connect. A reboot corrects it.
[AT&T Samsung Galaxy S 4 Original Android Developme] dmb219:
I see exactly the same thing. I think it will be corrected, maybe after 5.x for our phone is released. It's an issue that's hard to overlook. :(
[AT&T Samsung Galaxy S 4 Original Android Developme] Lord0KK:
Did either of you try deleting the APNs not used by your phone? I was experiencing signal loss and no lte, but after removing all of the Apns except for Att phone and Att Lte, then rebooting, the signal less problems went away and I have Lte. I'm using the 2/21 nightly on a i337.
[AT&T Samsung Galaxy S 4 Original Android Developme] ninja_rancher:
It's sure worth a try. I will do that and report back. What baseband firmware are you using?
[AT&T Samsung Galaxy S 4 Original Android Developme] dmb219:
I've tried that and expected it to work but still had the random loss of signal.
[AT&T Samsung Galaxy S 4 Original Android Developme] bjbinc:
Could someone help me out and post their libril-qc-qmi-1.so and libril.so file from /system/lib

Thanks in advance! :good:
[AT&T Samsung Galaxy S 4 Original Android Developme] Locoman_:
I haven't noticed any drops. I'm on ATT using NC1. - I did the delete the extra APNs too.