yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Official sources do not received any update from AntaresOne... the nightly is the first official compiled from pure sources of cyano.

Optimized version is still a unified build for all variants, and has to be considered as a custom rom (as it was before)... Optimized is Alucard kernel based... and other fixes provided by dev...

As I posted before, Official CM12 will receive updated from dev to improve basic source code (because of cm rules, it will be ONLY for JFLTEXX), and Optimized will continue to be Unified and optimized... they are two diffrerent roms.
[Galaxy S 4 i9505 Original Android Development] s3icc0:
I would emphasize few words: FIRST .... NIGHTLY .... STABLE .... - answer yourself

full wipe would be recommended as you have to consider it different ROM ...
[Galaxy S 4 i9505 Original Android Development] KrAzYtHeBoY:
Thread for official CM12 for jfltexx??

Enviado desde mi GT-I9505 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Guys... AntaresOne has officially get the role this night (few hours ago)... don't you think it will take some time to organize all stuff (included the new CM12 OFFICIAL thread for jfltexx)?

Please stop asking the obvious that need obviously time to be done.
[Galaxy S 4 i9505 Original Android Development] KrAzYtHeBoY:
Ok bro :)

Enviado desde mi GT-I9505 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] exynoss:
Thanks for clarification in detail.

What about Kernel. Currently alucard doing the Kernel part.

for official cm 12 cm who will take responsibility for Kernel ??
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Official kernel on cm will be anyway responsability of AntaresOne... but it will stay a stock version.
[Galaxy S 4 i9505 Original Android Development] KrAzYtHeBoY:
for flash official cm12 is need flashed superSU updated? or not?
[Galaxy S 4 i9505 Original Android Development] Duck4Cover:
I installed this nightly this morning waiting for this optimised one to be updated. Its good! Looking stable so far as they state.
[Galaxy S 4 i9505 Original Android Development] jstath1972:
Official vs optimized

The most differences

i can see

are the EXT4 partitions instead of F2FS, 3.4.105 cyanogenmod kernel instead of Alucard24's kernel and finally the SELinux is in enforcing. And here's the link http://download.cyanogenmod.org/?device=jfltexx&type=nightly
[Galaxy S 4 i9505 Original Android Development] KrAzYtHeBoY:
CM12 Official flashed in F2FS partition and not work. Bootanimation loop 20 minutes
[Galaxy S 4 i9505 Original Android Development] jstath1972:
CM12 Official nead EXT4 partitions instead of F2FS and try TWRP
[Galaxy S 4 i9505 Original Android Development] grzwolf:
jfltexx vs. jflte

http://xdaforums.com/showpost.php?p=58094872&postcount=6910

GT-I9505 is good to go with both:

- jfltexx (official CM12)

- jflte (Antares&Alucard optimized CM12)

stability comparison

So far no decisive answer.
[Galaxy S 4 i9505 Original Android Development] KrAzYtHeBoY:
Not work on F2FS???

edit

-----

Im formated system/cache/data to ext4 again and work perfect.
[Galaxy S 4 i9505 Original Android Development] AntoineAc:
Green tint bug on official rom, dont flash it if you dont like it..
[Galaxy S 4 i9505 Original Android Development] Tobirexy:
The bottom is like a lockscreen. Is this a bug ? (5/1)
[Galaxy S 4 i9505 Original Android Development] AntoineAc:
It is fixed with alucard kernel flashed
[Galaxy S 4 i9505 Original Android Development] Elkhardioui:
green tint

Flash alucard kernel and green tint bug will gone.
[Galaxy S 4 i9505 Original Android Development] Metalazzo:
Hi,

is there a requirement for bootloader and modem to run this rom ?

on cm11, i know my actual bootloader or modem does not work so i don't want to waste time flashing something that won't work :/

thanks :)
[Galaxy S 4 i9505 Original Android Development] sronweb:
Have you flashed official CM12 over last optimized CM build?
[Galaxy S 4 i9505 Original Android Development] Duck4Cover:
The Official Nightly CM12 Rom.

Yes I just got the green tint screen on wake. Also I have had the Bluetooth share crash on me, the phone dialer crash and the camera does work in the HDR function. Battery is good though been abusing it all morning had a phone call for two hours which was also using a Bluetooth speaker and played tunes since and had the screen on a lot and only used 49% battery. That also includes the battery used flashing the ROM and downloading my apps from the store.
[Galaxy S 4 i9505 Original Android Development] knuckles1978:
I'd try a different modem yeah. Remember to have a backup of your efs before you play with modems. And do you know that most of the time you have to flash then twice to make them stick? Once with auto reboot unchecked, then remove battery, boot back into download mode, flash again leaving auto reboot checked.

They should flash fine first time, but they don't on mine anyway, and I've seen others have the same problem.

You can try just flashing it once with auto reboot checked first, but if you go to about phone and you're still on your old modem, then do what I said above.
[Galaxy S 4 i9505 Original Android Development] ed_bracam:
Same for me, I need always to flash twice via odin . I never had problem with efs .

---------- Post added at 03:01 PM ---------- Previous post was at 02:59 PM ----------

I don't install official cm because I don't want to convert again my partitions to ext4 . I wait for AntaresOne update.
[Galaxy S 4 i9505 Original Android Development] jcdeoferio:
Alright, I'll try a new modem.

Thanks!
[Galaxy S 4 i9505 Original Android Development] KaszasM:
[MENTION=4780406]knuckles1978[/MENTION] [MENTION=3020373]jcdeoferio[/MENTION]

because your first flash is pointless start with second step :D

MEENS you need to FORCE power off = take out battery , or hold power button until screen goes black--->go directly in download /dont let boot up /--->flash>reboot/odin makes it if you tick/ and enjoy your new BL or modem after first,one flash :D
[Galaxy S 4 i9505 Original Android Development] Inelukis:
The issue causing the need to flash modem twice it's that to make odin working properly you have to boot in "Download Mode" by volume down + power and not by advanced reboot.

Trust me, I updated both modem and baseband just yesterday.
[Galaxy S 4 i9505 Original Android Development] cyberspaceguy:
Me too ... Stay good on f2fs
[Galaxy S 4 i9505 Original Android Development] ed_bracam:
Why F2fs is not integrated in the official cm? There is rights on it?

Only change the kernel is not enough to support it? Because it is just a file system handle by read write functions of the kernel?
[Galaxy S 4 i9505 Original Android Development] jcdeoferio:
I see. I did use Advanced Reboot and had to flash twice.
[Galaxy S 4 i9505 Original Android Development] vt0r:
Yes, flashing a kernel with F2FS support is usually all you need to do to use it - I believe the ROM has the F2FS binaries already. At least that's how it was in CM11... As for the why question, only CM devs can answer this.

Don't forget to use the Q&A thread next time, please!
[Galaxy S 4 i9505 Original Android Development] knuckles1978:
Ahhhh.... That makes sense. That will save me an extra flash in the future, cheers :)

Edit: but on second thoughts, I always use the advanced reboot menu to get to recovery, but I don't think I've ever used it to get to download mode. I always do that manually. But I'll try it anyway..

Backing up efs is purely a safety precaution. If you're ever in the position where you've lost your IMEI, you'd be very glad that you did.
[Galaxy S 4 i9505 Original Android Development] Inelukis:
Odin doesn't recognize properly the device if you enter download mode by Advance Reboot Menu. So, the first time you flash the modem/baseband you only reboot the device cause Auto-Reboot is ticked and only then the phone is recognized. That's all ;)
[Galaxy S 4 i9505 Original Android Development] TLK3:
Boo. I saw this commit RE: mounting F2FS volumes and thought it might work.

http://review.cyanogenmod.org/#/c/84604/

---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------

There are flashable files for CWM/TWRP that make this way easier. At least for jflteatt. Flash, reboot, done. No backup, multiple flashes, etc.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
This commit is related to recovery mounting of F2FS partitions... so is related to CWM Recovery, not to the rom.
[Galaxy S 4 i9505 Original Android Development] jeancca:
switching

Guys,

I'm seeing lots of comments on the nightly version of CM 12, when this thread is meant to be about optimized version. We should stick to the latter in this thread.

By the way, I have a jfltexx s4 and would like to know which ROM should I go with, optimized or nightly.

Thanks.
[Galaxy S 4 i9505 Original Android Development] TLK3:
Where does it say anything about recovery?
[Galaxy S 4 i9505 Original Android Development] vt0r:
The commits were made to the android_bootable_recovery repo (CWM).
[Galaxy S 4 i9505 Original Android Development] michelino.chionchio:
To guys that asked about f2fs support.

http://review.cyanogenmod.org/#/c/84675/

Read the comment in patchsets
[Galaxy S 4 i9505 Original Android Development] grzwolf:
GT-I9505 is good to go with both:

- jfltexx (official CM12)

- jflte (Antares&Alucard optimized CM12)
[Galaxy S 4 i9505 Original Android Development] jeancca:
Yeah but which Rom will AntaresOne keep working on?
[Galaxy S 4 i9505 Original Android Development] crossen0:
Didn't mean to thank you.

If you read, he clearly says that both will continue to be maintained.
[Galaxy S 4 i9505 Original Android Development] BakedTator:
I just have to say thanks for this...I don't believe there is a maintainer for the jflteusc and this is just about the only lollipop ROM I get to use!
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
New build coming in approx. 15 minutes :)

I want to remember you that this is more like a custom ROM based on CM12, it's not almost pure CM12 anymore like my first November builds.

As custom ROM, and since I'm now jfltexx maintainer, I'll keep alive both projects.

By the way, since these are unified builds there are issues (nightmares) because due to Lollipop updates S4 variants should be now deunified to fix some errors (like custom APNs on CDMA variants). I don't know about the future of this ROM, maybe I'll keep it unified or I'll deunify (and try to make at least 1 build/week for all variants)

Anyway, in the upcoming build kernel's ramdisk is fixed to work natively with GT-I9505G too
[Galaxy S 4 i9505 Original Android Development] Jsilver73:
LOL AntaresONE was much faster!
[Galaxy S 4 i9505 Original Android Development] Tobirexy:
How is it to be a part of CyanogenMod? ;)
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Soooooo..... New build online!!

Changelog:

Device:

Added native boot.img support for GT-I9505G

SELinux updates

Kernel:

Built with [MENTION=4825437]Christopher83[/MENTION]'s Linaro GCC 4.9.3 2014/12

Various code updates

ROM: (tiny changelog)

Added Lockscreen quick unlock

Clean up default profiles

Various code updates

Everything already merged here

Download: https://www.androidfilehost.com/?fid=95897840722641042

Official CM12 doesn't support F2FS yet, if you switch from this to it remember to convert back to ext4 if you're currently using F2FS!
[Galaxy S 4 i9505 Original Android Development] Soufiansky:
You mean this is like a slimkat rom or pac rom ?

It is just based on cyanogen right ? :)

Thanks your hardwork , thank you so much :)
[Galaxy S 4 i9505 Original Android Development] newtom:
Antares, if you like you can use my Thread-Header picture which i have created for my ROM-Thread in a german board for your optimized cm12 custom rom. If not, it's ok too ;)
[Galaxy S 4 i9505 Original Android Development] wonsky21:
Is GPS fixed in this build?
[Galaxy S 4 i9505 Original Android Development] Aldideos:
So I don't understand very well... The new build doesn't work with f2fs?
[Galaxy S 4 i9505 Original Android Development] JLopez149:
This build does. If you switch to the official cm 12 "pure" it does not.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
It's working

Yes, this works with F2FS. I said about the Official CM12 :)

Official CM12 doesn't support F2FS

This ROM supports F2FS

If you want to try Official and you currently are on F2FS, you must convert back to ext4 before installing Official CM

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] sronweb:
GPS is working since some couple of releases. I remember that GPS fix is already included on this rom.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Thank you bro, changed here and in Official thread with official builds' pic :)

I made that zip lol and it was only for my testers, but [MENTION=5528810]Jimsilver73[/MENTION] decided to do a favor to everyone

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] michelino.chionchio:
[MENTION=5464206]AntaresOne[/MENTION] you should change the thread title

:)
[Galaxy S 4 i9505 Original Android Development] blk_jack:
SlimRoms roms aren't based on CyanogenMod at all actually. SlimRoms has arguably as much if not more custom original code than any other AOSP based ROM, including CM.

Most ROMs (including this one and ROMs like Carbon, LiquidSmooth, etc) have literally no original code and are just include other people's cherry picked code/features.

It's probably the biggest misconception XDA users make, but ~95% of ROMs on here aren't maintained by actual developers. The term "dev" gets thrown around a lot but an original feature that's more complex than changing a toggle or two is actually few and far between.
[Galaxy S 4 i9505 Original Android Development] Galaktyko:
Bluetooth doesn't work for me either :(

EDIT: I reflashed and it worked properly :) Great room. :D
[Galaxy S 4 i9505 Original Android Development] ed_bracam:
Call over Bluetooth headset seems broken. It swith to the phone and the dialer crash forever. I must reboot the phone to close the call. Music is OK. I use V4A sound driver. Someone can confirm the problem?
[Galaxy S 4 i9505 Original Android Development] gkkovacs:
Proximity does note wake up during a call

Good to see there is a new build every week! Keep up the good work!

Unfortunately, the most annoying bug is still present: the proximity sensor does not work during calls. When I hold the phone to my head, the screen goes dark, but never turns on again - one of the physical buttons need to be pressed to wake up the phone.
[Galaxy S 4 i9505 Original Android Development] woooson:
I'm running as it is everything's fine ,no ...,...It's GREAT

GPS ,Bluetooth, WiFi ;)
[Galaxy S 4 i9505 Original Android Development] hypnobabes:
If you are completely sure that there is no physical issue (by this i mean you have blown air into the ear speaker) then you could always try a simple fix like this

https://play.google.com/store/apps/d...imityfix&hl=en

Make sure you have tried blowing compressed air into earpiece the earpiece resides in a similar location to the sensor which is to the side of it,

so blowing air can remove pocket dust and such that may be the issue. Good luck.
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
I would not do this... Risk of breaking earpiece is real and very high

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] hypnobabes:
I have fixed p sensor issue in 2 S4 phones using a can of air, but as AntaresOne says THERE IS A POSSIBLE RISK OF DAMAGE

I should have said so my fault sorry.

By default try the app i linked to. I have used that to fix psensor in my personal phone and many other S4 i have had through my hands

for others for flashing roms etc.

Thank you for info AnteresOne
[Galaxy S 4 i9505 Original Android Development] dcillusions77:
Took a picture with Google camera and sent it through messaging and when it compressed it, it turned the picture sideways
[Galaxy S 4 i9505 Original Android Development] Zehlek:
How good are the pictures compare to tw camera
[Galaxy S 4 i9505 Original Android Development] Jchef:
Look up proximity sensor fix s4 on YouTube. Involved taking apart phone and gently cleaning the proximity sensor, speaker, and front camera. Very easy and takes very little time. Proximity sensor works very well since doing this.
[Galaxy S 4 i9505 Original Android Development] awakener777:
Not sure what you're using but I'm on att and have noticed this in every build. This is the only lollipop ROM I have used however. I have the most recent modem. Not sure what causes this but it cuts out for no reason, never for very long periods of time. Luckily it doesn't happen DURING phone calls for me so far. Would love to get to the bottom of this.
[Galaxy S 4 i9505 Original Android Development] koheen:
I think there actually might be something wrong with the proximity sensor because I use the app gravity screen and it's pretty much useless it doesn't recognize that I've picked my device up when I'm in a lighted room. This also happens when I'm in a call when I bring the phone to my ear the screen turns off but when I take of away it does not turn the screen on
[Galaxy S 4 i9505 Original Android Development] cyberspaceguy:
Continually fc if try to active Bluetooth on i9505
[Galaxy S 4 i9505 Original Android Development] gkkovacs:
Your link was malformed, so I searched for "proximity fix" and installed this app:

https://play.google.com/store/apps/details?id=com.vrognaas.proximityfix&hl=en

This app indeed fixed my proximity sensor issue during calls, and the fix persists through a reboot. I don't have the slightest idea what happened here or what this app does, but thanks for your help!
[Galaxy S 4 i9505 Original Android Development] dcillusions77:
Not bad actually
[Galaxy S 4 i9505 Original Android Development] tomurbanowicz:
With native camera app in CM12 is worse than TW. With Camera KK (Play Store) is the same.

Problem with camera in CM11/12 is audio drivers - audio in camera in CM11/CM12 is fatal...
[Galaxy S 4 i9505 Original Android Development] devilyuri:
Try to use L camera.it uses the new Lollipop API's
[Galaxy S 4 i9505 Original Android Development] tomurbanowicz:
Give us the link to L camera.
[Galaxy S 4 i9505 Original Android Development] jazenf:
I just installed it on my phone an it says that it's not supported by my phone then the camera closes.

Here is the link

https://github.com/PkmX/lcamera/releases/tag/v0.3
[Galaxy S 4 i9505 Original Android Development] vedko:
One potential bug: with waking by home button activated, every second time the button not only wakes the phone but also registers the normal home button behaviour. Meaning, if I have an app open, turn off the screen and then press the home button, the screen is turned on but I get taken to the home screen; if I'm already on the home screen, the default action of my launcher gets activated.

I experience this exactly every second time, i.e. first press behaves as expected (home button only wakes the phone), after turning screen off, the button behaves as described above, and so on.

I've tested the behaviour with 3 different launchers, with the same result.

Further info: I've got password lock activated,10 minutes after the screen is turned off.
[Galaxy S 4 i9505 Original Android Development] fedef12evo:
clock is not working, cant set alarm xD
[Galaxy S 4 i9505 Original Android Development] franzyroy:
CM12 Dark Theme AntaresOne Rom (20150111)

​

Changes (in the latest)

:

Updated to the latest (20150111)

Improvement in the displaying of Settings/Battery (it seems to me -it's sure, I confirm ;))

Alwayys in the fifth post...

ENJOY!!!
[Galaxy S 4 i9505 Original Android Development] Duck4Cover:
Don't use HDR setting in camera as it crashes the program. Once it has crashed unable to get the camera working again as it says it can't connect to camera. Also once this is done no other camera app will work until phone is rebooted and the HDR is switch off.
[Galaxy S 4 i9505 Original Android Development] rakhan01:
Happened to me as well. Go to App manager and force stop the App and clear it's data, cache etc..
[Galaxy S 4 i9505 Original Android Development] jcdeoferio:
On Philippines (Globe), I was originally using a DXUAMDE modem, switched to XXUEMKE. I'm not getting any signal drops in the XXUEMKE modem. This is also the only Lollipop ROM I've tried.
[Galaxy S 4 i9505 Original Android Development] bleez99:
GPE / Nexus(?) 5.0 boot animation

This was pulled from my GPE 5.0 OTA system dump.

I enjoy it, hope you do too.

All credit goes to Google/Samsung, I just packaged it up as a flashable zip.
[Galaxy S 4 i9505 Original Android Development] Francismori7:
[MENTION=5464206]AntaresOne[/MENTION] You forgot to edit the thread's title for the new build!
[Galaxy S 4 i9505 Original Android Development] vkumar2695:
Anyone on AT&T getting Google Messenger to send MMS messages? An APN for that would be just dandy!
[Galaxy S 4 i9505 Original Android Development] BakedTator:
May not be an APN issue... Did you clean or dirty flash?

And when was the last build MMS was working for you?
[Galaxy S 4 i9505 Original Android Development] vkumar2695:
Clean flash and I solved it.

Kind of weird, but the way I solved the issue was by deleting all the other un-used APN's and BINGO!
[Galaxy S 4 i9505 Original Android Development] Im_Gumby:
minor bug on new release

After a dirty flash, when playing songs over Pandora, after song A is finished, the volume jumps up from wherever it currently is set to at least 50%.

Did a clean install and tried again. The volume jumps up only for a brief moment now in the middle of songs at random times. Not a big issue, but weird.
[Galaxy S 4 i9505 Original Android Development] clshores:
My review/issues for 1/11 build.

First of all I tried a clean flash and got the ever popular Bluetooth Share has stopped error so I had to revert to my backup and then dirty flash for 1/05. Everything seems to be working as expected so far and I can say that after trying a couple of other LP ROMs this is the on of choice for me and probably the rest f the S4 community. No official nightlies for the jfltespr yet so everything is either an unofficial or a GPE port.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Running 20151101 on Sprint. It is running almost perfect have 2 problems both have been plaguing for awhile on cm12 and cm11. The first is intermittent MMS issues. Someone posted a work around that sort of works. See attachment 1. In my case, I turned off wifi, but wouldn't download MMS with LTE. Set to 3G and then download worked. If I go to Hangouts settings|sms|access point names, I have page after page of see attachment 2. The second problem is wifi turns off when I start BT. No big deal easy workaround, turn bt off turn wifi on. I use bt mainly in car for phone. I can collect logcats if they would help.
[Galaxy S 4 i9505 Original Android Development] ed_bracam:
I got 3 freeze after switch off display by the power button. I was also not able to restart the phone having charger connected. With the charger the boot seems incredibly longer than without the charger connected. Bluetooth stays not usable for calls. This version seems very fast but not stable comparate with the 05/01 version.
[Galaxy S 4 i9505 Original Android Development] dcillusions77:
I can't tell with mine I've been using Google camera.
[Galaxy S 4 i9505 Original Android Development] Duck4Cover:
I hate this ROM it's tooo good!

I have actually started to use it as an actual phone.

Battery is brilliant and it runs like butter of a hot knife.
[Galaxy S 4 i9505 Original Android Development] tibaland:
camera stop working if use many times in whatsapp.
[Galaxy S 4 i9505 Original Android Development] woooson:
I've been using a better camera of the play store saves to SD .. No bugs so far

Edit :- using camera in HDR mode it gets stuck taking pictures in a loop ! Then no camera till restart !

Works fine in standard mode