yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] Bleedos:
And mine been stuck on the boot animation for more than 10 minutes (even after reboot and battery pull). Will wait for "Official statement" :) heheh

Edit --

I'm not ot AT&T!

Edit -2-

A "No go" for me for right now. Stuck on the boot animation. Will wait for 5.0.1 to come out and for things to "Stabilize".

Was hoping for this GPE ROM to anihilate the bluetooth drain issue i'm getting on the CM12 UNOFFICIAL build I'm playing with right now.

With bluetooth off, WiFi on and LTE on I managed to get 2hours of screen time with 33% battery left and almost 24 hours of unplugged time which I hardly was able to get 1 time (YEAH 1 TIME :) ) with KK and Greenify and Amplify and 2x battery and.... :) Lollipop is really promising in term of battery life but with BlueTooth off for right now :)

Edit -3-

yeah LP doesn't have XPosed but every modules I installed to customize my KK experience are now built-in in LP. I know it won't be everyone's case!
[AT&T Samsung Galaxy S 4 Android Development] ksmkk3:
Yeah, you're right. I must have flew past the "AOSP" when I read it the first time. It DID prevent me from getting the triangle though...
[AT&T Samsung Galaxy S 4 Android Development] cldot:
I too was stuck at boot. I changed file system from F2FS to EXT3 and that seemed to make it work.

Best of luck
[AT&T Samsung Galaxy S 4 Android Development] webbie2:
Man I saw this post and got so excited haha. Backed up and made sure I had loki and supersu ready. Went to download and no mirror. I will have to wait.
[AT&T Samsung Galaxy S 4 Android Development] spd_rcr:
Just wanted to say thanks for continuing to work on the AT&T GS4 ROM's. Sounds like I should wait for the servers to be sorted out, but I look forward to trying it out.

For reference, I had an issue with a 4.4.x update ROM when it came out and was convinced I had bricked my phone, but it turned out to just need about ~15+ minutes for whatever it was doing and I didn't have the patience. Gave up and walked away, Got my fingers crossed that this one gets sorted out, Dan's ROMs have always been first rate!
[AT&T Samsung Galaxy S 4 Android Development] lauterm:
Yeah, I would be surprised if Sammy kernels support f2fs.

---------- Post added at 12:22 PM ---------- Previous post was at 12:22 PM ----------

Loki didn't work on this one anyway.
[AT&T Samsung Galaxy S 4 Android Development] Spacemonkie4207:
Working perfectly on my I337M

Tested pretty much everything.

Here are the steps I took

Full wipe

Installed my stock firmware N1S

Installed twrp 1.8.1.0

Advanced wipe, wiped everything

Flashed ROM and SuperSU

(Took about 5 minutes on boot screen to load)

After boot I let it sit for 5 minutes while the kernel does is thing.

Wiped data in settings.

Lollipop!
[AT&T Samsung Galaxy S 4 Android Development] kriEv:
which kernel did you use?
[AT&T Samsung Galaxy S 4 Android Development] Spacemonkie4207:
Just Stock. My boot loader is not locked.

For those with locked boot loader give it a couple of days until kernel sources are released in guessing. Usually they are released a day before ota. HTC released the sources after lollipop this time as well.
[AT&T Samsung Galaxy S 4 Android Development] JLopez149:
Googy made a GE5 kenerl. should beable to boot up with that.

http://xdaforums.com/showthread.php?p=52414749
[AT&T Samsung Galaxy S 4 Android Development] thesummoner101:
Unfortunately, didn't work.
[AT&T Samsung Galaxy S 4 Android Development] JLopez149:
Bummer. Sorry i thought it was going to do the trick.
[AT&T Samsung Galaxy S 4 Android Development] purdone:
Do you mean "for Safestrap users" by this comment? I'd love me some Lollipop.
[AT&T Samsung Galaxy S 4 Android Development] thesummoner101:
No worries, I thought the same. Thanks for looking out though.
[AT&T Samsung Galaxy S 4 Android Development] CyberManiaK:
Where you got twrp 1.8.1.0 ? mind sharing the link ?
[AT&T Samsung Galaxy S 4 Android Development] Spacemonkie4207:
Go to the twrp web site and on the top right you click get twrp for my device.
[AT&T Samsung Galaxy S 4 Android Development] CyberManiaK:
Thanks.. I want it to try flashing first using CWM and it's working good :)

The only problem i'm having is it's not connecting to LTE even if my APN for LTE is selected.
[AT&T Samsung Galaxy S 4 Android Development] Spacemonkie4207:
I've always liked CWM nice and simple. Just recently started getting comfortable with twrp (got tired of using the volume buttons to select :p)
[AT&T Samsung Galaxy S 4 Android Development] thesummoner101:
Has nothing to do with recovery, our radio is for kitkat. I was able to use LTE on cm12 unofficial by going into testing menu (*#*#4636#*#*) and fiddling with radio settings. It too seemed to have trouble with catching LTE.
[AT&T Samsung Galaxy S 4 Android Development] CyberManiaK:
Well the CWM that i have is also touch. I'm with you i like how easy and simple is, I guess I will still be using cwm until i start to have problems when flashing lol.

Yeah I know that recovery is not the problem. I forgot to put on a side note. But well yeah i guess the modem is the problem because i'm loosing signal a lot my S4 is on baseband i337MUMUEMK6. Do you remember which option you selected there? There are tons of options, currently mine is LTE/GSM Auto (PRL)
[AT&T Samsung Galaxy S 4 Android Development] thesummoner101:
Sadly, that's the setting that worked for me. When I first checked, it was on wcdma preferred. I changed it to lte/gsm/evdo auto prl and it worked. When I went back to check, it was on lte/gsm auto prl so I didn't bother.

Try going into settings, preferred network and change to 2g then back to LTE. I think that did the trick for me too.
[AT&T Samsung Galaxy S 4 Android Development] param.006:
Using cwm, theres nothing extra apart from the op installation instructions when flashing? Im running unofficial cm12 currently so do i need to do anything other than flashing the rom and superuser?
[AT&T Samsung Galaxy S 4 Android Development] CyberManiaK:
Well i don't know what did the trick but now i have LTE i changed to 2G and back to LTE and did nothing it was on HSPA still. Then on that menu i changed to the last option TD-SCDMA,LTE,CDMA,EvDo GSM/WCDMA and it went to LTE then i reverted back to LTE/GSM Auto. And I'm getting 40mb down !!

Yeah nothing special to do just the usual procedure to flash a rom.

Make a full backup, wipe factory reset, wipe cache, wipe dalvik cache, flash rom, flash super su and reboot.
[AT&T Samsung Galaxy S 4 Android Development] orlandoxpolice:
Doesnt work for me either. Yellow triangle. Followed instructions perfectly. Does anyone have a workaround for this yet?
[AT&T Samsung Galaxy S 4 Android Development] param.006:
Thanks for your help! Running smoothly with no issues!
[AT&T Samsung Galaxy S 4 Android Development] orlandoxpolice:
Just tried it 10 minutes ago and I am getting the yellow triangle.
[AT&T Samsung Galaxy S 4 Android Development] iB4STiD:
figured i would lend [MENTION=4830253]Danvdh[/MENTION] a hand!

i337 loki users .. the loki patch isnt working as of now, to save u guys tripping the evil att yellow triangle i figured i would mention this as Dan has a i337m he may not have been aware of this :good:
[AT&T Samsung Galaxy S 4 Android Development] orlandoxpolice:
Yea... I found out the hard way :(

Glad I made a backup. This should be added to the OP (once Dan sees it) to save other people the trouble.

Does the googy kernel provide a workaround?
[AT&T Samsung Galaxy S 4 Android Development] iB4STiD:
no... tried that as well .. im sure Dan will add it to the OP poor guys probably busy :good:
[AT&T Samsung Galaxy S 4 Android Development] thesummoner101:
Tried googy with and without loki, doesn't work. Messaged ktoonsez, he mentioned it would be difficult until sources become available. Waiting to try Alucard kernel, but not expecting anything until things settle.
[AT&T Samsung Galaxy S 4 Android Development] iB4STiD:
none will work, the issue is the loki patch.. if ur a i337 loki user flashing a kernel without it will trip the triangle of hell ;)

sammy may have patched the exploit if so .. not good for tw roms and future lollipop.. but hey we shall see!
[AT&T Samsung Galaxy S 4 Android Development] thesummoner101:
Yeah, I figured it was going to be something like that. Thanks for the input.
[AT&T Samsung Galaxy S 4 Android Development] duckredbeard:
I flashed with no problem. ROM then th SU update. It looked like the lokifying didn't happen until after the SU. It went through the boot animation for about 3 mins, then black, then boot animation for another 4, then the updating. After all boot up and sign in and app restore was done I took a quick tour. Seems to be missing a lot of what I'm used to. I'm just not excited about all this change, so I'm back to my previous ROM.

But I had no issues with the install. Did not check network connection, but the status bar did show AT&T.
[AT&T Samsung Galaxy S 4 Android Development] orlandoxpolice:
Guessing you have an I337M?
[AT&T Samsung Galaxy S 4 Android Development] Spacemonkie4207:
Seems to work fine in T-Mobile and I337M variants

---------- Post added at 07:49 PM ---------- Previous post was at 07:48 PM ----------

Kernel sources should be released any day now. I'm surprised they are not released already.
[AT&T Samsung Galaxy S 4 Android Development] iB4STiD:
anytime man !

ya.. hmm i thought it did .. thought googy's kernel was built from source, if not we with a i337 may have some hope ..
[AT&T Samsung Galaxy S 4 Android Development] Jose0726:
Stuck on boot on i337m :/
[AT&T Samsung Galaxy S 4 Android Development] TRusselo:
{FACE}<---[PALM]

doesnt matter.

the dev (OP) lives in toronto (canada).... he has the 337m

and the dude you were replying to says right in his sig AT&T S4. so no not an M
[AT&T Samsung Galaxy S 4 Android Development] s3nr1:
i377m, just let wait for it too finish booting, around 5-6m, no more than 10m or if your phone gets hot just turn it off.

Anyway, it's working well enough but for some reason the su binary is in a different path than the busybox and some app like TitaniumBackup doesn't work, complaining that it's trying to use xbin/su but can't.

su is in /bin

busybox is in /xbin

Every root checker app says they're in different dirs, I compared it to my rooted nexus7 and both are in the same dir.

Any ideas?
[AT&T Samsung Galaxy S 4 Android Development] Danvdh:
yes, clean flash this

UPDATE IN THE OP

-Phone should now always boot properly on first boot

-Rooted

-Added busybox and init.d via archi kitchen

-Integrated Superuser into settings

-Added touchkey light binary script to turn lights off (type SU to get root then touchkeys in terminal)

-ROM ships with stock launcher now

-Added Google MMS

-Updated Google Camera

-Updated GoogleTTS

-Removed Android Debugging notification

-Made HSPA visable in the status bar

-Menu no longer unlocks the lock screen

-Updated build.prop

Note: Chainfire wants you to update the binary via supersu app, just do it the normal way as you still

have root even without updating the binary

AT&T cannot use this yet until a kernel dev somehow unlocks loki patching so for now Android 5.x is only for i337m and t-mobile
[AT&T Samsung Galaxy S 4 Android Development] a_rocklobster:
Ugh if only I saw this Loki issue a few hours ago :/

I do appreciate the port though

Thanks Danvdh
[AT&T Samsung Galaxy S 4 Android Development] Jose0726:
Edit: flash with twrp and booted un 3 mins
[AT&T Samsung Galaxy S 4 Android Development] Danvdh:
yep the new build fixed it
[AT&T Samsung Galaxy S 4 Android Development] s3nr1:
What is the normal way? So we can't update when a toast from supersu comes out?
[AT&T Samsung Galaxy S 4 Android Development] CyberManiaK:
My 337m is loosing phone signal constantly and can't pickup lte after a reboot, any idea on how to fix this?
[AT&T Samsung Galaxy S 4 Android Development] s3nr1:
Probably need new modem. I can't seem to find any 5ghz APs.
[AT&T Samsung Galaxy S 4 Android Development] Ruturaj001:
waiting for safestrap version :(
[AT&T Samsung Galaxy S 4 Android Development] Jose0726:
Actually i didnt noticed a new build was up xD just mánage getting old build setle lol
[AT&T Samsung Galaxy S 4 Android Development] Bleedos:
Don't know if the guy who made a Safestrap version out of Dan's 4.4.4 version will do the same for 5.0.
[AT&T Samsung Galaxy S 4 Android Development] MATHReX:
Hi! I Flashed This Firmware On SGH-I337M

Everything Is Working Great Except Sound !

No Sound Anywhere In The Rom.

I Tried Many Other Roms Too But They Had Sam Issue Of No Sound.

I Dont' Know Whats Wrong With My Phone.

When I Bought It , It Came With Some I9500 Android 4.3 OS.

I Thought It Might Be A Software Fault. So I Flashed Android 4.4.2 Stock Odin I337M Firmware And It Failed More Than 10 Times.

After That Phone Never Booted.

So I Installed Custom Recovery From Download Mode And Started Trying Different Roms.

In Some Roms , Phone Did Not Booted And In Others It Booted And Everything Was Working Well Except The Sound.

Can I Get Any Help In This Issue ?

Thank You.
[AT&T Samsung Galaxy S 4 Android Development] CyberManiaK:
You bought your S4 from ebay ?
[AT&T Samsung Galaxy S 4 Android Development] HockeyNinja:
Same here. My AP is not appearing on the wifi list. i337m
[AT&T Samsung Galaxy S 4 Android Development] ma678:
I had the same issue in the first few hours. My 5ghz ac band didn't show. I was able to find it later. By the way, I am on NI2 modern.
[AT&T Samsung Galaxy S 4 Android Development] dennis nai:
Wish someone can make this work for it I 9500 thanks
[AT&T Samsung Galaxy S 4 Android Development] duckredbeard:
Nope. US version. AT&T. I337UCUAMDL.
[AT&T Samsung Galaxy S 4 Android Development] Miyamato:
Anyone else having it download not as a ZIP file, but as a .exe?
[AT&T Samsung Galaxy S 4 Android Development] thesummoner101:
Tried the other download button? There are usually two or three buttons, but only one actual one. The others are usually ads.
[AT&T Samsung Galaxy S 4 Android Development] Miyamato:
Derp. I could have sworn I tried both. Just attempted again and the file is downloading properly now. :/
[AT&T Samsung Galaxy S 4 Android Development] lauterm:
How did you get it to work? I can't get past the triangle screen on my AT&T S4.
[AT&T Samsung Galaxy S 4 Android Development] MATHReX:
Yeah. Any help?

---------- Post added at 06:53 PM ---------- Previous post was at 06:52 PM ----------

Yeah. Any Help?
[AT&T Samsung Galaxy S 4 Android Development] lauterm:
If you've never had sound with any ROM, I would guess it is physically broken. Can you return it? Otherwise find a repair shop or start searching Google for how to fix it.
[AT&T Samsung Galaxy S 4 Android Development] s3nr1:
Hi, same problem. SU is still in /xbin while busybox is in /bin. Should I install another busybox inside xbin? I rather not waste the space.
[AT&T Samsung Galaxy S 4 Android Development] bikoman1:
I am in same boat MDL boot loader flashing yellow att triangle. Stupid att vzw and their locked bs.

Will probably work when someone gets a gpe custom kernel. KToonez please.
[AT&T Samsung Galaxy S 4 Android Development] orlandoxpolice:
Yea...what's going on with this? Not sure how this is possible if true.
[AT&T Samsung Galaxy S 4 Android Development] macwindows:
Hi,

Thanks for the detail steps.

Please do not take the following question incorrectly. I would like to update my i337M (on Koodo) with latest stock firmware, before proceeding to Lollipop.

Is it stock firmware NI2? Or would you please point to link for N1S?

Is it 1.8.1.0 or 2.8.1.0

I presume it could be typo.

Thanks in advance
[AT&T Samsung Galaxy S 4 Android Development] Locoman_:
if you want to run 5.0, Lollerpop works well with Ks asop kernal. Works so well its my DD.

Once this GE rom is sorted out, I'll give it a try.
[AT&T Samsung Galaxy S 4 Android Development] Aqua1ung:
Would you please ad this to the OP, just so you don't get pestered with questions every other post? Thank you!
[AT&T Samsung Galaxy S 4 Android Development] orlandoxpolice:
It is in the OP, just not very obvious.
[AT&T Samsung Galaxy S 4 Android Development] Bleedos:
Had that weird bug where the screen would be flashing when pressing the power button or the home button while the phone is charging. Had this issue on a previous cm12 build. Latest Cm12 build is OK.

I also had that screen freeze bug that I had on GE KK ROMS. Phone becomes non responding when I press the home or power button while the phone sleeps. Screen lights up but I can't unlock the phone. If I press the power button the phone screen goes off and I can't light it back.
[AT&T Samsung Galaxy S 4 Android Development] Sigurd02:
Hey everyone,

I'm currently experiencing an issue with the screen turning off during calls. I can hit the home button a few times and it will bring me to lock screen.

With the screen off, i am not able to end calls or use the keypad for call selections.

I noticed the screen only turns off when i switch to the phone app during a call.

Is there a solution to this? Thank you so much!!
[AT&T Samsung Galaxy S 4 Android Development] webbie2:
Development removed post from of that says no ATT? Does it work if you are. Able to loki? Still on MDL! So I have always been able to flash with twrp! Anyone able to run this on ATT with no issues?
[AT&T Samsung Galaxy S 4 Android Development] thesummoner101:
No. Doesn't work on AT&T. Won't work until loki is fixed or AT&T kernel source is available.
[AT&T Samsung Galaxy S 4 Android Development] Ruturaj001:
That's the main concern for me.
[AT&T Samsung Galaxy S 4 Android Development] duckredbeard:
I just might flash it again just to see what ain't working. I know it booted up and restored apps. Didn't try to make a call or SMS. Prolly be tomorrow. Need to clean out my external to make room for a backup.
[AT&T Samsung Galaxy S 4 Android Development] param.006:
I had flashed the first 5.0 build yesterday, and I have had no issues :S

On the sgh-i337, loki'd before. Is there something I'm missing? Cuz it works perfectly fine for me..
[AT&T Samsung Galaxy S 4 Android Development] hammer7t:
hmm, interesting. What were the exact steps you followed if you don't mind sharing...same as OP? I and many others get the "Unauthorized" message and yellow triangle...thanks.
[AT&T Samsung Galaxy S 4 Android Development] param.006:
Yup nothing special. As per the initial instructions, I just backed up, wiped, flashed the Rom, flashed superuser, wiped cache and dalvik and reboot. On Cwm. Was running lollerpop Rom prior to flashing this Rom. Regarding Loki I had done it last year and never had to do it myself again. The Cwm always "fixed" it (I guess?).

I'm not sure what's changed since that build since I did it following a couple of posts by others saying it was running well.
[AT&T Samsung Galaxy S 4 Android Development] hammer7t:
Ok, the only difference I see is that I used TWRP 2.8.1.0. Are you on CWM 6.0.4.7?
[AT&T Samsung Galaxy S 4 Android Development] param.006:
Cwm 6.0.0.4

I haven't updated recovery in a while :P if ain't broke, don't fix it!
[AT&T Samsung Galaxy S 4 Android Development] reade0871:
Some of the CWMs auto-loki any time a .zip is flashed. Oudhs cwm always did that and was my recovery for a long time.
[AT&T Samsung Galaxy S 4 Android Development] jdonk:
Probably just me but.... Does anyone else notice the charging seems slower?
[AT&T Samsung Galaxy S 4 Android Development] Spacemonkie4207:
Give the kernel a few charging cycles. It's only been out for a day.
[AT&T Samsung Galaxy S 4 Android Development] hjkimbrian:
anyone having problem with bluetooth audio on the latest build? I only have one device so can't pinpoint the issue, but audio is cutting in and out (almost like CD skipping) when connected to bluetooth in my car. I have NI2 modem on I337M.
[AT&T Samsung Galaxy S 4 Android Development] lauterm:
I tried with oudhs. I couldn't get it past the samsung splash screen. No triangle screen. Just the samsung splash screen, and then it would reboot to recovery again. I haven't been able to locate a copy of cwm 6.0.04 yet.
[AT&T Samsung Galaxy S 4 Android Development] duckredbeard:
Just an update on I my install. I am on US AT&T I337UCUAMDL. I just flashed this again without issue. I am using a CWM Recovery 6.0.4.8 mildly modded by jeboo. His version 2.4.

I did the usual backup, then my typical factory data reset, wipe cache, wipe dalvik. Then I flashed the ROM then the SU update. Just to be sure, I manually on flashed the Loki, even though jeboo's recovery usually covers that.

I had no issues on first boot. I skipped all of the account setup, as I was only interested if the device could get on the LTE network and make calls. I was able to make a call. (Hall & Oates hotline is my preferred test 719-266-2837). I did notice that the default network is 3G, I had to manually select LTE. Every time I selected LTE, it would revert back to 3G. Could be an APN setup issue. Work on that tomorrow.
[AT&T Samsung Galaxy S 4 Android Development] scloutkst:
Can you link to recovery and kernel you are using please? I am on att handset which is mdl, and nothing will work for me currently. Thanks.
[AT&T Samsung Galaxy S 4 Android Development] s1l3nt:
it might be this one that he is referring to. Might give this a try tomorrow. http://d-h.st/etX
[AT&T Samsung Galaxy S 4 Android Development] thesummoner101:
Thanks for the link, would I simply flash this in current recovery and reboot into it?
[AT&T Samsung Galaxy S 4 Android Development] lauterm:
It worked for me too! Thank you so much for the detailed instructions!

Thanks for the link!

Yes!

I can confirm it works! I'm at the welcome screen now! Maybe a dev can figure out what the difference is and get it to work in all recoveries again.
[AT&T Samsung Galaxy S 4 Android Development] s1l3nt:
yeah just flash it, reboot back to recovery and you'll see the new recovery.

---------- Post added at 11:37 PM ---------- Previous post was at 11:36 PM ----------

thanks for confirming, looks like i will be sleeping late tonight. Going to flash this right now
[AT&T Samsung Galaxy S 4 Android Development] Shawn7656:
I'm going to assume anyone who is on AT&T is used to having things auto-lokied. This rom wasn't during early builds of kitkat and probably isnt again. Are people trying to manually flash loki-doki? I am and will report back shortly. That's the easiest way to explain why its working for some since certain recoveries auto patch and others do not.
[AT&T Samsung Galaxy S 4 Android Development] thesummoner101:
No.

Manually flashing loki patch isn't working. Many, including myself, have tried and exhausted all possibilities.

The two people that were able to get it working on AT&T, were using an old recovery (jeboo cwm) which auto loki'd. There might be some changes in the code which aren't working for manual loki patch.

So, the only way to get it working on AT&T MDL seems to be to going with that recovery. If you find another way, please share your findings.
[AT&T Samsung Galaxy S 4 Android Development] juju2011:
Does this ROM support f2fs or I have to switch all to ext4?
[AT&T Samsung Galaxy S 4 Android Development] EpicMango:
Download Galaxy Charging Lite and make sure that when you charge, you're charging at the full 1990mah
[AT&T Samsung Galaxy S 4 Android Development] lauterm:
I'm going to guess that it doesn't since it uses a sammy kernel.
[AT&T Samsung Galaxy S 4 Android Development] EpicMango:
This uses the stock kernel
[AT&T Samsung Galaxy S 4 Android Development] thekrush:
[MENTION=2870669]duckredbeard[/MENTION]: did you figure out the APN issue? I was able to flash this using your method but am having the same 3G default issue. Thanks in advance!

EDIT: Nevermind. Found it! NOW HAVE LTE! :)

4G LTE PTA/HSPA+:

Name: PTA

APN: pta

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

MMS Proxy: proxy.mobile.att.net

MMS port: 80

MCC: 310

MNC: 410

Auth: none

APN type: default,mms,supl,hipri
[AT&T Samsung Galaxy S 4 Android Development] lauterm:
Sammy = Samsung. Sorry for the confusion.
[AT&T Samsung Galaxy S 4 Android Development] cholywell:
Yes I was having this problem this morning in my car as well. I will try it on my soundbar when I get get home later this today.
[AT&T Samsung Galaxy S 4 Android Development] jdonk:
Thanks.