yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] flroots:
Thanks. If not bug free, which m919 compatible ROM is closest? I've already tried the one here:

http://xdaforums.com/galaxy-s4/i9505-orig-develop/jdcteam-android-source-project-mra58v-t3251663

and it looks promising. Guess I'm wondering if there are other promising candidates. Any suggestions are much appreciated.
[Galaxy S 4 General] Strephon Alkhalikoi:
I'm using the one you linked to. The only other option is Kushan02's unofficial CM13, in the same forum.
[Galaxy S 4 General] flroots:
Thanks. Sounds like I'm on the right track. Guess I need to adjust my expectations :)
[Galaxy S 4 General] anatomality:
Using crDroid for today, seems pretty tight... Lots of features. Haven't tried either Kushan or ASOP yet. Any opinions on how they compare? Using it on my Canadian sgh-i337m

-Glad I ditched GPE for marshmellow. End of an era though.
[Galaxy S 4 General] Strephon Alkhalikoi:
AOSP does not have working GPS, but it's already been fixed for the upcoming build when they choose to release it. Since it's an AOSP ROM, it has none of the features you find in Kushan's ROM, although you can install Xposed and Gravitybox to compensate. It does however use the Alucard kernel and STweaks, so you can customize the kernel. Kushan's ROM is an unofficial Cyanogenmod build, so it has all the Cyanogenmod features people are used to. The kernel however is stock, which isn't necessarily a bad thing, but being able to underclock the CPUs will add to the battery life of the device, especially when coupled with Doze.

It mainly boils down to how much customization you want and how many bugs you want to put up with. People who use the GPS will gravitate to Kushan's ROM, at least until JDCTeam releases their next update of AOSP. If you stream audio through Bluetooth, you're completely out of luck for right now. Other than that, both ROMs I believe are stable enough to use as daily drivers.
[Galaxy S 4 General] Mr.Yawnie:
One more option is crdroid (cm13 based). It mainly competes with kushan's rom rather than aosp. For me bluetooth (in car) calls work perfect with the rom. Haven't tried bluetooth playback yet, but calls work at least in a car (the one necessity for me).
[Galaxy S 4 General] Strephon Alkhalikoi:
I'm aware of that. However, the person I responded to had already put that ROM on his device and was looking for alternatives. Since he had already put crdroid on his S4, there was no point in mentioning it.
[Galaxy S 4 General] jds3118:
Good to see you around my friend! Hope you are well!
[Galaxy S 4 General] Mr.Yawnie:
Here I still am! Echoe times are behind, I was off for a year due to military and idk, was sort of never part of it again. Friedrich didn't respond to my messages anywhere etc.. I've been checking the echoe forums every now and then, seems like it's still going healthy although they completely left xda!

I've been most active in Snapprefs community now [emoji14] helping people (and the dev) there, making custom sticker packs etc (you know me ;) ).

Hope you're well too, say hi to other echoers.
[Galaxy S 4 General] NZgeek:
That sweeping generalisation is incorrect in this case.

The compatibility layer is implemented as a C++ header file, meaning that it is only useful at compile time. In other words, you need the source code of the old audio library to make it work. The code itself is just mapping an older style API to the newer equivalents.

And as for device support, Samsung not releasing new versions isn't necessarily the end of the world. The Qualcomm-based S4's are largely covered by CAF, with only a few components needing Samsung blobs. Those might continue to work with compatibility thunks. The Exynos-based S4's aren't looking as good, and might require the drivers to be reverse engineered.
[Galaxy S 4 General] jds3118:
I will my friend! Say hi next time you pop in the forum. I'll tell the others hi for you. Take care. Good to hear you are doing well.
[Galaxy S 4 General] flroots:
Thanks. Actually I never got to try out crdroid since TWRP refused to install it due to incorrect device type error. I think I'll work with AOSP since I'm more of a minimalist. The 5.1 version I use is gpe (Google Play Edition) which was originally for the Google variant of the S4 (i9505g). Does anyone know if there will be a Marshmallow release for that variant?
[Galaxy S 4 General] robertogl:
There is a way to see the log of cyanogen compilation? I think it should be on jenkins, but I can't find it...

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 General] c-non:
Hello Cyanogenmod developers and especially [MENTION=5464206]AntaresOne[/MENTION] ,i know this is not your job, i dont want to importune you only want to obtain info,we are waiting to verify this commit's for official cm13 since 11 dec. There is only 1 comment :( thanks for your work.

http://review.cyanogenmod.org/#/c/123973/
[Galaxy S 4 General] hakfur5328:
Hey guys android 6.0 rom out for i9500(it test build)

https://www.androidfilehost.com/?fid=24269982087018210
[Galaxy S 4 General] Sunjay140:
Thanks m8. Does it support Doze and is there a thread about it here? Do the radios work? Downloading it right now.

Edit - It put my phone into a bootloop.
[Galaxy S 4 General] Mittaa:
[MENTION=5464206]AntaresOne[/MENTION] take all the time you need and thank you for supporting jfltexx :) :good:
[Galaxy S 4 General] aavil:
Did you wipe dalvik, cache? Using newest twrp?
[Galaxy S 4 General] Cel1n:
I recived black screen after booting.
[Galaxy S 4 General] Alfarcher:
Any published andorid m rom for i9500

---------- Post added at 07:31 AM ---------- Previous post was at 07:28 AM ----------

Cm team says the cm14 will published in first stages of 2016

---------- Post added at 07:35 AM ---------- Previous post was at 07:31 AM ----------

Cm13 i want to say ??
[Galaxy S 4 General] vbajs:
And I am cooking something special for you guys[emoji4] :-

And unofficial pure cm13 builded from cyanogenmod's github source for jfltexx

Since you guys can't wait for cm13 nightlys from cm team so I decided to build my own [emoji1]
[Galaxy S 4 General] krishnakonvict:
Guys please send me link of cm 12.1 for Samsung galaxy s duos 2 s 7582
[Galaxy S 4 General] vbajs:
and yet here is another teaser from me :) :-

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=6.0.1

CM_VERSION=13.0-20151217-UNOFFICIAL-jfltexx

TARGET_PRODUCT=cm_jfltexx

TARGET_BUILD_VARIANT=userdebug

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a-neon

TARGET_CPU_VARIANT=krait

TARGET_2ND_ARCH=

TARGET_2ND_ARCH_VARIANT=

TARGET_2ND_CPU_VARIANT=

HOST_ARCH=x86_64

HOST_OS=linux

HOST_OS_EXTRA=Linux-4.2.0-19-generic-x86_64-with-Ubuntu-15.10-wily

HOST_BUILD_TYPE=release

BUILD_ID=MMB29M

============================================
[Galaxy S 4 General] Cel1n:
Who can properly compile CM13 ROM for i9500?
[Galaxy S 4 General] vbajs:
I guess nobody

The only hope is to wait for CM team
[Galaxy S 4 General] islipfd19:
If I'm not mistaken, your architecture is wrong. I'm fairly sure it should be 'arm' and not x86_64.
[Galaxy S 4 General] vbajs:
That's the host architecture

The target architecture is arm and not anything else

Look closely at my teaser agian
[Galaxy S 4 General] Sunjay140:
Wiped cache and used TWRP.

---------- Post added at 01:37 AM ---------- Previous post was at 01:36 AM ----------

Did you fail to compile it?
[Galaxy S 4 General] vbajs:
I haven't compile it

But they say that its hard to compile for
[Galaxy S 4 General] FernBch:
The Hardware on the I9500 (Exynos) is different than the I9505 (Qualcom).
[Galaxy S 4 General] Kushan02:
EDIT: Deleted as someone is already working on it :)

I guess I am fine with my kind of Optimized builds for better performance, stability and battery life :)
[Galaxy S 4 General] vbajs:
I am already working on it ;)
[Galaxy S 4 General] johnny88:
more governors and i/o scheduler will be appreciate :)

Inviato dal mio GT-N8000 utilizzando Tapatalk
[Galaxy S 4 General] vbajs:
Almost I am not going to do it

As the matter the fact, I am building a pure cm13 for jfltexx which it is aimed at being just the same of cm13 on nightlies (which is currently happening to other devices)

So if you want more governor and i/o schedulers I guess you have to have some Patience because CM team have said that the second stage of cm13 nightlys is going to be on early 2016 and our beloved galaxy s4 might be selected in that nighty stage[emoji4]
[Galaxy S 4 General] johnny88:
ok :)

Inviato dal mio GT-N8000 utilizzando Tapatalk
[Galaxy S 4 General] vbajs:
Well,this is going to be my first ROM for jfltexx

And of course there might be a lot of bugs which I can't mange to fix[emoji20]

So some help might be appreciated[emoji1]
[Galaxy S 4 General] AntaresOne:
Hi guys,

Before shipping Official CyanogenMod 13 nightlies for i9505/i9505G I need to know if Radio is working well.

Please test incoming/outgoing calls (many of them, at least 5/10), network type selection (GSM/WCDMA/LTE) and BT A2DP (audio stream). If everything is fine then I'll manage to start to ship official nightlies.

It's made specifically for i9505/i9505G but will work on jflteatt, jfltecan & jfltetmo too after editing the updater-script. I just need to know if it's working well on jfltexx. I'll test it as well on my jfltexx tomorrow.

Make a clean installation! (wipe /cache, /data and /system, install zip, install GApps (the latter is optional))

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

:)
[Galaxy S 4 General] MarcelRobinson:
So excited!(: -jfltetmo
[Galaxy S 4 General] vbajs:
And cancelled my unofficial cm13 build since [MENTION=5464206]AntaresOne[/MENTION] is now working on cm13 and he is going to ship it to the cm team
[Galaxy S 4 General] vbajs:
Del
[Galaxy S 4 General] bongster:
Hi,

BT A2DP is not working. Clean install. It connects without a problem, but stock music player does not make a sound.

As it is my spare device without a SIM, I couldn't test calling.

Do you need a log?

Best,

Bongster
[Galaxy S 4 General] myawan:
[MENTION=5464206]AntaresOne[/MENTION] calling works OK but 'invalid number' error pops up when the other party hangs up.
[Galaxy S 4 General] vbajs:
That error pops up in all MM ROMs made for our device
[Galaxy S 4 General] ShanLou:
Hi! Calls not working for me...

Works with your JDC Team AOSP 6.0, not working with Kushan's CM13, crDroid 6.0, Synergy's CM13 or in this one.

I tried to make a bug report but don't know how to use it, first it said that it would email the results somewhere but then it started to share it with nearby devices, a bit confusing... Does it save those results in a file somewhere? or should I use some other tool to get logs?
[Galaxy S 4 General] vbajs:
Make sure you have a vaild sim card

Otherwise you will need to replaces your sim card and sdcard module (they both are one module)
[Galaxy S 4 General] Mr.Yawnie:
That error must be on your end. I have working calls on every rom you mentioned. I9505 in Finland.
[Galaxy S 4 General] Mr.Yawnie:
Yes, until now. As [MENTION=5464206]AntaresOne[/MENTION] is the official maintainer of CM for our device, I have no doubt it will get fixed sooner or later.
[Galaxy S 4 General] Mr.Yawnie:
Deleted. Accidental duplicate.
[Galaxy S 4 General] ShanLou:
Hmm, what do you mean by valid SIM card? How can it not be valid if I can make calls with some of the roms? I have never had any problem with SIM or sdcard...
[Galaxy S 4 General] vbajs:
I mean if you can sim card can make calls

To test:-

Insert your sim card in to another device

Call anyone you want (only for testing)

If this device succeeded in making calls:- then you going to replace the sim card module in your galaxy s4 (as it might be damaged)

If this device didn't succeeded in making calls:- check the problem with you sim card provider (you might have an invaild sim card or the sim card is damaged)
[Galaxy S 4 General] ShanLou:
Ok thanks, I will test. But i just mentioned that I can make calls with JDCT AOSP 6.0, doesn't that mean anything?

---------- Post added at 12:30 ---------- Previous post was at 12:28 ----------

Moikka vaan sullekin :)

"(Hi to you, too)"

What's your modem version? I have POJ2...
[Galaxy S 4 General] ShanLou:
Moikka vaan sullekin :)

"(Hi to you, too)"

What's your modem version? I have POJ2...
[Galaxy S 4 General] Mr.Yawnie:
HOD7. nice to see other Finns here from time to time! Rooting is not that common here lol..
[Galaxy S 4 General] Corduroysack:
Ran great till i flashed SuperSu then i just got a bootloop on cm logo. before installing SuperSu i made a phone call sent a text, i dont use bluetooth so couldn't comment
[Galaxy S 4 General] ShanLou:
Ha, I knew it! I just downgraded my modem to HOD7 and now calls are working with this rom, at least. Should test others too. So there wasn't anything wrong physically in my phone... :)

That I don't know why these ROMs aren't working with new modem, maybe Samsung have changed something critical there...
[Galaxy S 4 General] vbajs:
Gald to hear that you have managed to fix

Anyways guys,

As I was cancelling my build,

I somewhat let my laptop continue the build

And then I decided to flash my build and it is completely bug free[emoji4] (incoming calls are working fine,but still that error "invalid number" encounters,Haven't tested Bluetooth yet)

If guys want a download link

Tomorrow I will upload my build to AFH (short cut for android file host)

Good night[emoji4]

---------- Post added at 09:25 PM ---------- Previous post was at 09:18 PM ----------

One last teaser[emoji6] :-
[Galaxy S 4 General] gezze:
Actually I don't know where to ask so I do it here: is there any fix for installing open gapps in stock version ? I always got the error that there's not enough space in system partition...
[Galaxy S 4 General] vbajs:
Hey guys

Well,I tried to upload to AFH but turns out you need a developer status and you also going to write the reason why you want a developer status but I have no idea about how that reason is going to be because this is my FIRST EVER ROM and I don't know what to write

So I am going to be using MEGA for a while until I think of a good and specific reason for AFH

And of course

Here is the link for unofficial cm13:-

https://mega.nz/#!BpNgUB6J!aEeQsUmQD65KnIp4-F5EIOfI8PeK6C3DtLMm2nAaNuk

Hope you guys enjoyed

Its so far so stable

With an excellent battery life

Screenshots coming soon[emoji4]
[Galaxy S 4 General] Latrell567:
Is there an Android 6.0.1 ROM available for the GS4 yet?
[Galaxy S 4 General] metalicfann:
What model of S4 are you using?
[Galaxy S 4 General] a103:
There are unofficial CM based ROMs available if you search in I9505 section.
[Galaxy S 4 General] sanangel:
Does not believe it appropriate to open a new thread with your rom ?

Thanks for your work :good:
[Galaxy S 4 General] xell75:
What's the problem with calls on other MM roms than Aosp? I'm on crDroid and never had call issues, working like a charm.
[Galaxy S 4 General] FernBch:
What variant are we talking about? For me caller id is not working on JDC's AOSP. I have the SCH-I545 (jfltevzw) and different blobs are required than for the jfltexx. CDMA and GSM devices have differences.
[Galaxy S 4 General] vbajs:
EDIT:- thread opened ?

http://xdaforums.com/showthread.php?t=3275283
[Galaxy S 4 General] Mr.Yawnie:
The problem you are referring to according to your quote, was already solved by downgrading modem to latest official modem in Nordic countries (as he's from Finland). Flashing other modems than the ones meant for your area can cause issues with connections, but it really depends on which modem you use. All modems beginning with XX should work internationally, at least in Europe, but modems beginning with other letters may not work well in Europe as they are for totally other region.
[Galaxy S 4 General] cilixan:
try this https://www.androidfilehost.com/?w=profile&uid=95864024717073819
[Galaxy S 4 General] Sunjay140:
Still boot loops. Why does it optimise apps on a clean install?
[Galaxy S 4 General] vbajs:
Its normal to optimise apps in a clean install
[Galaxy S 4 General] FernBch:
App optimisation will occur anytime cache and davlik are wiped so you will see this when flashing a ROM via clean or dirty flash. It s part of the initial boot process.
[Galaxy S 4 General] Sunjay140:
You're right, I forgot about that.
[Galaxy S 4 General] Latrell567:
Never mind. Found it. But the SCH-R970
[Galaxy S 4 General] metalicfann:
I got a bootloop trying to dirty flash the new update on my m919 clean install and now all is well.
[Galaxy S 4 General] JackFedrik94:
Are there kernels in way of development for 6.0???:)
[Galaxy S 4 General] vbajs:
Currently, none

But alucard kernel is coming soon[emoji4]
[Galaxy S 4 General] aavil:
Is he working on it? He changed S4 to LG. Or maybe with AOSP 6.0?
[Galaxy S 4 General] AntaresOne:
Alucard kernel for 6.0 is already in our AOSP MM as default kernel, part of JDCTeam's optimizations

Actually I switched to the LG G4 but still have my S4 around, and [MENTION=4899086]alucard_24[/MENTION] still has the S4 as main phone. :)
[Galaxy S 4 General] :
Doesn't matter if we get one or more in the end.

A pure cm ain't bad as they try to keep it to a normal levels of features they are kinda picky

And [MENTION=5804776]Kushan02[/MENTION] you are going a sperate way continue with that it's good to have different choices rather than only stock cm off crdroid is available but they are just slightly different.

I don't complain if a new cm related comes I sorta think this out are pretty boring but they are good in their own ways :p one rom might have a good feature while other one haven't.
[Galaxy S 4 General] aavil:
[MENTION=5464206]AntaresOne[/MENTION], sorry I always missing you both, somehow both names sounds similar to me. Great to hear it and looking forward to test it!
[Galaxy S 4 General] portaleus:
Does it mean that you will still be the device's maintainer?
[Galaxy S 4 General] MarcelRobinson:
Is there a reason when I flash a jfltetmo ROM its perfect but "jflte" I get no data ?/messaging
[Galaxy S 4 General] FernBch:
Yes
[Galaxy S 4 General] islipfd19:
What tmo ROM are you using? Any jflte or jfltexx ROM is use has no data/radio.
[Galaxy S 4 General] FernBch:
Check ypur APN settings.
[Galaxy S 4 General] islipfd19:
I did that, tried every possible T-Mobile APN available.
[Galaxy S 4 General] MarcelRobinson:
I'm using CM 12.1 and it works perfectly fine but not 13
[Galaxy S 4 General] islipfd19:
Only thing I can summize is that it has something to do with the RIL or blobs; I don't know but it seems I'll have to wait and keep trying new versions as they come out.

I do know that it isn't marshmallow itself as AntaresOne's first initial build and alpha release worked except for bluetooth for me.
[Galaxy S 4 General] MarcelRobinson:
Thanks (:
[Galaxy S 4 General] ahmed.ismael:
official .......... samsung said's no marshmallow for s4 :(

we have good luck with cm 13;):)
[Galaxy S 4 General] Strephon Alkhalikoi:
Once the bluetooth bug is ironed out Android 6 is a ROM my roommate will enjoy. I purchased a brand new Nexus 6 today off Amazon. For $300 I couldn't go wrong. :)
[Galaxy S 4 General] sanangel:
What is the font?... link to new?...
[Galaxy S 4 General] AztecRefreshed:
Source?

Last I saw it was still undecided but highly unlikely.

Anyway, if they do not, I can highly recommend CM13. It's running smoother than the original ROM on my s4. Better battery life as well.
[Galaxy S 4 General] SaulGoodman88:
here are some roms where the bluetooth bug is fixed:

Synergy's cm13

crDroid cm13

in AOSP 6.0 is not fixed already but will be fixed in the next update:

AOSP 6.0 by JDCTeam
[Galaxy S 4 General] Strephon Alkhalikoi:
I've been following this stuff rather closely. Most functions of bluetooth are working, but streaming audio does not. Are you telling me that those ROMs have fixed that particular bug?
[Galaxy S 4 General] a103:
Yes the streaming audio works on Synergy's ROM. I myself did not test it but I read OP mentioned it, however BT still has bugs. Good thing is they're getting fixed day by day.
[Galaxy S 4 General] SaulGoodman88:
streaming audio is working but with some minor bugs.

Look at this post
[Galaxy S 4 General] Strephon Alkhalikoi:
I just checked out crDroid and they've gotten it fixed as well, which means I missed this in trying to keep up to speed on the fixes. So now I get to install a new ROM. Happy days. ;)
[Galaxy S 4 General] islipfd19:
So... Apparently my modem is very old; 2013 actually. The current marshmallow versions are GSM/CDMA dependant so much that they haven't been unified yet. Most iterations are CDMA; T-Mobile uses GSM band. Though I have come across this ROM based on CM13:http://xdaforums.com/newreply.php?do=newreply&p=64459473

At first I did not work for me; but [MENTION=7026254]SaulGoodman88[/MENTION] helped me out on this post on page 13: http://xdaforums.com/galaxy-s4/i9505-develop/rom-synergy-s-cyanogenmod-13-0-jflte-t3272770/post64459473

As long as your SGS4 is jfltexx, download the bootloader and modem he provided. Google for Odin, I used version 3.09 and download / install Kies from Samsung. I found a thread on XDA with instructions to update the bootloader and modem only to be certain I was doing it right (I have don eit in the past). I flashed the ROM and everything is working as expected so far.
[Galaxy S 4 General] ahmed.ismael:
[IMG="time table"]http://www.arbandroid.com/wp-content/uploads/2015/11/Samsung-Android-6.0-Marshmallow-update-roadmap-November1-887x1024.jpg[/IMG]
[Galaxy S 4 General] dylanmc:
so no samsung 6.0 official :(
[Galaxy S 4 General] bongster:
Just to keep my hopes up, but "not approved" is not "cancelled", right?
[Galaxy S 4 General] masterlo3:
well CM13 for i9500 is cooking :D
[Galaxy S 4 General] vbajs:
"Not approved" means planned not cancelled

Maybe the 6.0 update gets leaked soon I guess
[Galaxy S 4 General] grzmot22:
New build

Hi, I have something new, this is mix of Optimized and Temasek ROM. There is link. Changelog is here.

Merry christmas and happy new year
[Galaxy S 4 General] Mr.Yawnie:
Changelogs should be visible to all, not just to people who have access to device info with changelogs (ie. To those who already flashed the rom). What's the point of changelogs if you can't view them beforehand?
[Galaxy S 4 General] vbajs:
Is it for jfltexx? Because it says that its for jfltegsm and it is an invalid variant (I think because I never heard of this variant)
[Galaxy S 4 General] Mr.Yawnie:
Jfltegsm is not an official variant. It means all the jflte devices that use GSM network, not CDMA network. Jfltexx is GSM device, so yes, you can flash it on jfltexx if it says jfltegsm
[Galaxy S 4 General] vbajs:
So its no just for 1 variant, nice[emoji106]
[Galaxy S 4 General] FernBch:
They are not unified because what fixes GSM breaks CDMA. CyanogenMod was a good axample. They went back to variant builds with CM12 because some things just wouldn't work properly when it was CM11.

It's technically not "invalid". All the S4 variants that use GSM bands can use the same build, the same goes for CDMA. The ril info is the key for each.
[Galaxy S 4 General] robertogl:
C'mon, s4 will not see android 6 from Samsung, I'm surprised that on xda there are still people talking about it...

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 General] grzmot22:
There are Changelogs. Sorry for that.
[Galaxy S 4 General] vbajs:
Damm ?

The mini version of our device got cm13 nighties before us
[Galaxy S 4 General] xell75:
That makes no sense, why the hell get the s4 mini offical cm13 first? :(
[Galaxy S 4 General] kubapl66:
Yes, it's a bit unfair. But if you guys rembember SGS4MINI got 12.1 snapshot earlier than ours SGS4 too. So it seems that SGS4MINI is more important for Cyanogen team. But anyway SGS4 got snapshot of 12.1 a few weeks later (about 2/3). So it's near :)
[Galaxy S 4 General] Zeitraffer:
Anything with surveys is always fake.
[Galaxy S 4 General] braulio_holtz:
Any first ROM with Android Marshmallow probably will first be posted on forum.xda-developers
[Galaxy S 4 General] AmyClaraRose:
In a couple of days I will be syncing AOSP to my PC to start working on building for s4 then soon after it will be renamed to the new rom I'm building called EMC rom