yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Original Android Developme] ledhed.jgh:
No. Just installed lokidoki and rebooted. I did have to reinstall TWRP via TWRP Manager (download from play store).

---------- Post added at 08:43 PM ---------- Previous post was at 08:19 PM ----------

FYI, I installed tonight's (3/24/2014) and same thing. Looks like the dev isn't I auto lokiing anymore.

So I recommend putting loki doki in the after flash dir of OpenDelta.

-LedHed
[AT&T Samsung Galaxy S 4 Original Android Developme] Pulga89:
I'm also having this issue, but it's easily solved by using loki-doki. However, today I got the latest nightly 03/25 and my phone won't charge anymore. I put the charger and it says not charging and keeps draining battery... Anyone else having this issue?
[AT&T Samsung Galaxy S 4 Original Android Developme] jamng:
Just booted up the 03/25 image to test this and it says its charging for me.
[AT&T Samsung Galaxy S 4 Original Android Developme] Pulga89:
After I posted here I did some more testing and apparently my phone's USB board went bye-bye. I restored to an earlier version of OmniROM, I installed a few other ROMs and nothing worked. I had all my hopes on the problem being a kernel error or a conflict on the drivers, but apparently it wasn't any of that. Oh well, off to eBay to purchase a new USB board.
[AT&T Samsung Galaxy S 4 Original Android Developme] Pulga89:
Ok, so I changed the USB board and the problem was fixed. Apparently the other board had some damaged pins.

Anyway, I have a concern about the latest OmniROM nightlies. Since about a week ago, after an OpenDelta update I got the big yellow triangle saying that AT&T detected unauthorized software on my phone, so I went into TWRP and flashed Loki-Doki and I was able to boot into OmniROM again...

My concern is: ever since that day I got the Samsung Custom bootscreen on every single boot, and subsequently, every time I try to flash a new nightly or a TWRP update I get the yellow triangle again. I've been reading here that Triangle Away does the trick, but I need a stock kernel for it to work. Does anyone here know what can I do get rid of the custom bootscreen and be able to flash things again without getting the triangle? Or if I can use Triangle Away on Omni?

Thanks!
[AT&T Samsung Galaxy S 4 Original Android Developme] sileniusmike:
Flash stock firmware with Odin. Root and run triangle away.
[AT&T Samsung Galaxy S 4 Original Android Developme] MrMarkEdward:
download and flash skyfall rom its a stock att rom
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
I'll get this fixed ASAP, working on it right now. Initially removed Loki support from the msm8960-common repository as it was moved to the jflte repository with the unification.

As I have come to find out, the unification process was done half-assed and incomplete, thus leading to these Loki issues.

Some general information for those that experienced the Loki issues:

If you get stuck on the Yellow Triangle screen again (this happened to me hundreds of times):

Power off the device (removing the battery is fine)

reboot the device directly into recovery

wipe system, data, cache, dalvik

flash another, LOKI'D ROM, or re-flash the ROM and be sure to flash Loki_Doki

If you cannot reboot back into recovery use a tool such as heimdall to flash stock images

TriangleAway *should* be able to reset the binary counter back to 0x0, thus removing the Padlock Custom splash screen and restoring the normal splash image

FLASH LOKI_DOKI BEFORE BOOTING and you should not have any issues.

I have updated all of the device trees and will be having them tested thoroughly before merging anything

I am totally and completely re-doing the entirety of the jflte repositories tonight. hopefully all of these stupid issues will be resolved. A test build will be posted on OmniROM's G+ Community Page when it is available.

I apologize for my absence here, I had to get rid of the device several months ago. I did not request ownership change of this thread because the other jflte maintainers didn't want it, as they were monitoring here, but they have since quit omnirom.

I will be working on the jflte repositories again until a full-time device maintainer is found for omni's jflte support.

Again, I sincerely apologize for any inconveniences here.
[AT&T Samsung Galaxy S 4 Original Android Developme] Pulga89:
Thank you for the input! I do have a question though: If I use Triangle Away on Omnirom you said it should clear the binary counter, but when do I flash Loki_Doki? Does Triangle Away run on TWRP or something? I'm sorry, but I'm confused and I don't want to mess anything up.
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
Triangle Away is an app from the PlayStore. So basically this is a general order of operations you'll want to follow:

Flash ROM

Flash Gapps

Flash LokiDoki

Install and use TriangleAway
[AT&T Samsung Galaxy S 4 Original Android Developme] Pulga89:
And when you say ROM you mean a stock one?
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
To be on the safe side, yes. I have used Triangle Away while on AOSP ROMs before, but there is a huge warning in the app recommending that you are using a stock ROM kernel in order for it to work properly.

So for safety's sake, flash a stock-based ROM first, preferably one as close to unmodified stock as possible, use Triangle Away, and then when you flash OmniROM, flash loki doki BEFORE leaving recovery

Test build is posted in the OmniROM Google+ Community - Samsung Galaxy S4 Section
[AT&T Samsung Galaxy S 4 Original Android Developme] Pulga89:
Thank you for your help!

Just one last thing: after using Triangle Away, do I have to flash Omni and start from scratch, or can I just restore from a Nandroid backup? I believe the binary counter is not affected when doing backups/restores, right?
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
Correct, restoring from a backup is fine, just be sure to flash loki doki before booting
[AT&T Samsung Galaxy S 4 Original Android Developme] Pulga89:
Thanks again! I'll check it out tonight and report back.
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
looks like my Mac OS X environment still produces non-booting builds; i'm rebuilding on my linux machine right now that works perfectly fine. link will be posted on the G+ community post

Full custom kernel support is back as well ( a user just reported that KToonsez's kernel works
[AT&T Samsung Galaxy S 4 Original Android Developme] jamng:
Just to be sure I understand. This build will no longer NEED loki-doki but you're recommending we use loki-doki anyway just to be safe?

ETA: Thanks for helping especially since you said you don't have this device anymore. What are you using now?
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
we just had a new roommate move in (an old friend)that has one, and is looking for a new device so he said I can flash and test anytime on it.

That's correct, you should no longer need to loki, but just make sure you have loki doki flashable zip on your sdcard just in case
[AT&T Samsung Galaxy S 4 Original Android Developme] Pulga89:
[MENTION=3878813]jakew02[/MENTION]: Success!! I made a backup on TWRP, then wiped /system, /data and both caches, flashed Skyfall ROM (the AT&T one) and installed and ran Triangle Away. Everything went well: the binary is back at 0 and it says Official again. No more padlock bootscreen! I then restored from the backup and flashed loki_doki. All is good! Thanks again for all your help!
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
LOKI FIX IS PUSHED. LOKI DOKI SHOULD NO LONGER BE NEEDED.

Individual variant build will also be stopped ,and only jflte unified will be built once I merge the changes. YOU MUST, MUST, MUST CONDUCT A FULL-WIPE WHEN SWITCHING FROM A VARIANT BUILD TO THE UNIFIED BUILD. DO NOT POST ABOUT BUGS IF YOU DIDN'T DO A FULL WIPE/CLEAN INSTALL

Test build here: https://plus.google.com/101979049437785027733/posts/2J2iqvb2UGj

Leave feedback ON THAT POST. thanks.
[AT&T Samsung Galaxy S 4 Original Android Developme] stefan75:
What skyfall ROM did u use? And did u pay for the triangle away app from the play store? I want to get rid of the Samsung custom boot screen and I don't want to brick my only device, just making sure I do everything right.
[AT&T Samsung Galaxy S 4 Original Android Developme] Pulga89:
I used the one that says ATT. Triangle away it's free on XDA: the paid version it's just a donation.
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
i need a tester to PM me please, att or can variant does not matter, thanks:good:
[AT&T Samsung Galaxy S 4 Original Android Developme] Pulga89:
One quick question: Can I update through OTA without triggering the flash counter again? I still haven't installed the experimental build from G+.
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
just wait for the nightlies to build tonight; the consolidated jflte build will be built and posted at dl.omnirom.org. all support for individual variant builds is officially dropped, as they have all been consolidated into one jflte build.

You

MUST

do a full wipe / clean install or you WILL have issues
[AT&T Samsung Galaxy S 4 Original Android Developme] blackwing182:
i have a gs4 jfltecan let me know
[AT&T Samsung Galaxy S 4 Original Android Developme] Droidmissionary:
Sent pm if needed as well
[AT&T Samsung Galaxy S 4 Original Android Developme] Pulga89:
I checked the download page, and I see the variants. Which one is the consolidated build, the jfltexx one? Or is that the international version?
[AT&T Samsung Galaxy S 4 Original Android Developme] jamng:
I don't see any of the variants with a build date of yesterday or today so I'm guessing it isn't ready yet or I'm missing it as well :)
[AT&T Samsung Galaxy S 4 Original Android Developme] Chartmän123:
Here you are: http://dl.omnirom.org/jflte/
[AT&T Samsung Galaxy S 4 Original Android Developme] Pulga89:
The jflte section is now live. The nightly says 20140410. Can't wait to get it running later tonight. If anyone installs it and tests it, please let us know how it goes!
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
Please make sure to forward all bug reports to JIRA, NOT HERE, and to add the device as Samsung Galaxy S4 , thanks.
[AT&T Samsung Galaxy S 4 Original Android Developme] BakaB:
battery performance seems noticably worse after changing from jfltecan 04/07 to jflte 04/16. Anyone else notice that?

I'm using ondemand governor in both cases.
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
For the sake of simplifying the unification, I pushed up an otherwise unaltered CM kernel; all I did was strip out the Flo adreno commits. I do still have the previous kernel that was included with Omni (that also, does not have the Flo drivers, making it compatible) so I can build and post a test build if you and/or others willing to test and get back to me
[AT&T Samsung Galaxy S 4 Original Android Developme] Pulga89:
I've been running the unified build since yesterday and everything is working great. Battery life seems to be normal.
[AT&T Samsung Galaxy S 4 Original Android Developme] BakaB:
seems fine now. sorry, not sure what the original issue was. first day after the flash, phone lasted only 5 hours after full charge. now things seems to be better ~14 hours with my typical usage.

has anyone seen this problem before with youtube? i've tried reflashing gapps (04/17) but it didn't fix the issue... not sure what else to do.
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
yes, this is a known issue and has nothing to do with Gapps, it's something with the CAF stuff. it's taking longer to fix because i'm swamped with my classes right now, and midterms are in a week
[AT&T Samsung Galaxy S 4 Original Android Developme] BakaB:
cool, no rush. thanks for the update
[AT&T Samsung Galaxy S 4 Original Android Developme] Serfma:
I don't want to sound like a noob, but for some reason, my "Ok Google" hotword detection isn't working. I attempted to uninstall Google Search through Titanium but it immediately reinstalls back.

Anyone know the reason why the detection may not work?
[AT&T Samsung Galaxy S 4 Original Android Developme] AKdballs:
You don't want to uninstall Google Search through Titanium, you want to change it from a system app to a user app and then back to a system app. I can't explain why it works but I had exactly the same problem with it after flashing but doing that fixed it for me.
[AT&T Samsung Galaxy S 4 Original Android Developme] borillako:
Where is the new forum at? Theres nothing in the galaxy s4 (solo variant), or atleast nothing in the search, is there a forum for the unified version at all to subscribe too or do I have to just download from the website.
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
just download from dl.omnirom.org/jflte

i have to talk to the moderators and see where we can put this, i might end up posting it in the omnirom forum, posting a link here in the OP, and closing this and the other variant threads as they're quite irrelevant, and a huge inconvenience to monitor, but i'm not sure yet.
[AT&T Samsung Galaxy S 4 Original Android Developme] borillako:
Ok cool, thanks for the clarification, was killing myself searching all around.

Phone: Samsung SGH-i337 (jflteatt)

Rom: Dirty Unicorns

Kernel:

Overclock: why would you?
[AT&T Samsung Galaxy S 4 Original Android Developme] BakaB:
any update on the video issue?
[AT&T Samsung Galaxy S 4 Original Android Developme] AKdballs:
My video is still broken too since the unification.
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
i'll just leave this here then..

https://plus.google.com/101979049437785027733/posts/RnEE335YKUk
[AT&T Samsung Galaxy S 4 Original Android Developme] AKdballs:
Thank you Jake-- I installed the nightly and it fixed YouTube! I did NOT do a full sweep afterward and it just started working after I rebooted.
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
sounds good :highfive: now to fix that annoying camera preview freeze..
[AT&T Samsung Galaxy S 4 Original Android Developme] jamng:
Wifi working ok for people on the last 2 nightlies? I can't seem to ever connect even though it sees the SSIDs. Going back 2 nightlies and it comes right up.
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
try full wipe
[AT&T Samsung Galaxy S 4 Original Android Developme] Airtioteclint:
How do i disable the backkey and menu light? Also is there a way to toggle hotspot on my notifications drawer i seem to be missing it.
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
Settings > Buttons.. Omni's settings layout is pretty literal in the sense that things will be in categories to which they pertain
[AT&T Samsung Galaxy S 4 Original Android Developme] Airtioteclint:
Sorry my question wasn't clear. I don't want to disable their functionality, i just want to turn off their light. I find them unnecessary and a waste of battery thanks:D
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
Yes so that would be a button related setting.

Settings > Buttons. it's right there..
[AT&T Samsung Galaxy S 4 Original Android Developme] Airtioteclint:
Found it thanks. As far as the hotspot toggle in notification i found a shoertcut app in the playstore that does the job. Im all set now great rom!
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
Thread closed.

Please refer to the unified forum here: http://xdaforums.com/showthread.php?t=2765216
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
awesome.. just shoot me a PM and we'll talk:highfive::good::victory:
[AT&T Samsung Galaxy S 4 Original Android Developme] matrixzone:
Please something for d2att. Lol
[AT&T Samsung Galaxy S 4 Original Android Developme] blackwing182:
lets see what i can do as i dont own the device anymore :(
[AT&T Samsung Galaxy S 4 Original Android Developme] matrixzone:
Happy to test any number of builds for you
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
d2att build is in the works, i've been talking to the guy working on it. :good:
[AT&T Samsung Galaxy S 4 Original Android Developme] matrixzone:
Thanks man, this is awesome news
[AT&T Samsung Galaxy S 4 Original Android Developme] herbzilla:
I keep coming back to this ROM just can't wait for all the features coming.

Sent from my SGH-I337 using Xparent Green Tapatalk 2
[AT&T Samsung Galaxy S 4 Original Android Developme] xerythul:
As this rom is 4.3 based I know its a pipe dream to attempt a flash while stuck on the mf3 firmware, but is there any chance to see a 4.2.2 build for those of us chained down by at&t's tyrannical policies? I would gladly act as a build tester as I use most of the major functions in a variety of conditions on a daily basis. A pm or reply here would be awesome, thank you!
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
A 4.2.2 build wouldn't be possible because OmniROM source only goes back to 4.3.. They don't even have the source for a 4.2.2 build for me to work with..
[AT&T Samsung Galaxy S 4 Original Android Developme] xerythul:
Well that answers that, and makes me sad all at once. I will patiently wait for official 4.3 and a new root exploit then. Thank you for your dev work, and prompt reply!
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
Bad News:

I spent the day doing homework, and a lab prep for my chemistry lab. Didn't get much done on the ROM side of things.

OmniROMs gerrit went down over the weekend, and just went back up early early Sunday morning. Due to that, there has been no progress on getting officially supported other than me having a conversation with pulser about it.

Also in the Bad News side, MultiWindow lost 10 patch sets when the gerrit servers went down, so for the sake of sanity, I'm not going to include it in my builds until they have a change to restore it back to where it was.

On that note, this next build will have less "apparent" features, and more fixes under the hood. I had to remove MultiWindow for reasons stated above, and I also took out VolumeButton Music Controls, since it was conflicting with VolumeButton Wake. That will be sorted out soon though. There's quite a few cool things coming up.. stay tuned! https://gerrit.omnirom.org

Good News:

I got TWRP flags properly set into the device trees with the help of [MENTION=4922752]mithun46[/MENTION], so now every time I compile a build, it will also create an up-to-date build of TWRP, so I can also include (in a separate zip, of course) an up-to-date release of TWRP as well with my ROM releases :good::highfive::fingers-crossed:
[AT&T Samsung Galaxy S 4 Original Android Developme] mithun46:
Glad to hear that
[AT&T Samsung Galaxy S 4 Original Android Developme] blackwing182:
i think im going to attempt a 4.4 build based of OmniRom to see if it compiles. i hope it does
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
aaaand, jflteatt, jfltecan, jfltexx are officially supported by OmniROM now folks.
[AT&T Samsung Galaxy S 4 Original Android Developme] LamboDroid19:
Still can't get it to build. Will try again later today. Let me know if I'm missing something.
[AT&T Samsung Galaxy S 4 Original Android Developme] lauterm:
Yay! Congratulations!
[AT&T Samsung Galaxy S 4 Original Android Developme] Vcolumn:
thank you very much! :highfive:
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
hey shoot me a PM whenever you have time, and i'll get you setup and building :good:
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
-_-
[AT&T Samsung Galaxy S 4 Original Android Developme] blackwing182:
what happen?
[AT&T Samsung Galaxy S 4 Original Android Developme] RagingHarry:
That means that we can flash the jflteatt build or can we try to build a kang for jfltexx, just to be sure.

And are you using "TheMuppets" github for proprietary files?
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
That means that device trees for jflteatt, jfltecan, and jfltexx are now in omnirom source at https://www.github.com/omnirom

As well as all needed repositories for those devices

And yes I'm using that for vendor blobs currently.

So, I pretty much hate my English class, so I'm going to spend it working on something cool.. We'll see ;)
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
i must say, this is the calm before the storm ;):highfive::good::victory::cool:

WAO...
[AT&T Samsung Galaxy S 4 Original Android Developme] matrixzone:
Man this is awesome.. Hope we can have the same on d2att soon. Lol
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
i know the dude working on d2spr is pretty well along the process of getting device and it's required trees merged in. basically, once that's done, it'll just need a bringup and merge for the other d2 variants. soon enough :good:
[AT&T Samsung Galaxy S 4 Original Android Developme] blackwing182:
i was digging these files now :(
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
sorry it's been slow in here folks, been swamped with school -- exams and papers and lab reports and studying to top it off.. not a lot of time for android. to top that off, I use my macbook for building since it's faster than my old desktop, and i can't really get any work done while it's building (building takes up all the computer's power and trying to write papers and use eBooks doesn't work well).

I have another exam this morning (wednesday morning) and once that's done, i dont have too much else for school for a few days (hopefully)

I HAVE been refining the 4.3 build though, and i'll be building and posting one tomorrow forsure unless something drastic comes up.

4.4 is looking good, just trying to iron out some bugs before posting it up and moving the main focus of this thread to OmniROM 4.4.

currently the builds are succeeding and flashing, just not booting. I'm convinced there's some minor changes i've been overlooking in my brief investigation, but i'll be back at it strong again tomorrow.

Also, I'll be posting a build for jfltecan as well, as promised (again, sorry for the delays.. tell my university to lay off on the work load!!)

until then, cheers for study beers :good:
[AT&T Samsung Galaxy S 4 Original Android Developme] jumoog:
We had success now 4.4 will follow
[AT&T Samsung Galaxy S 4 Original Android Developme] blackwing182:
i see ril is giving problem right?
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
Nope, everything should be good to go

I have 4.4 building right now for jflteatt, and jfltecan is queued and waiting :good::good:
[AT&T Samsung Galaxy S 4 Original Android Developme] jumoog:
[MENTION=5346995]jumoog[/MENTION]
[AT&T Samsung Galaxy S 4 Original Android Developme] Gandalf:
OP Updated

Well the 4.4 build is fully functional. To prevent avoidable errors please ensure you do the following:

WIPE SYSTEM/DATA/DALVIK/CACHE

YOU MUST MUST MUST USE 4.4 GAPPS

I'm going through now and making a new screenshot library, so they'll be up soon enough

In light of the 4.4 release, I will not be posting 4.3 builds anymore. I will still provide support for 4.3 though, so if you don't upgrade(not sure why you wouldn't, 4.4 is AWESOME) then you can still post 4.3 questions/issues here, just know that 4.3 is pretty much deprecated in this thread :good:

As always, please report any bugs here with proper logs and a description of the issue

Enjoy! :highfive:

P.S. - expect official nightlies soon :good:

P.S#2 : jfltecan is compiling a 4.4 build now and will be posted. I would like to maintain both devices in this one thread. So PLEASE make sure you choose the right download link for your device when downloading!!
[AT&T Samsung Galaxy S 4 Original Android Developme] pfoxdizzle:
Is the camera working? I noticed it wasn't mentioned in the op