yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] petrus764:
Guess it wasn't as smooth as they'd hoped for. Yes, it's only from CM12 onwards, CM11 is still unified.

I know Sprint had a lot of issues after the builds went unified, I assume trying to merge all snapdragon variants into one single build didn't go as well as planned, considering VZW and Sprint are CDMA carriers, while others being GSM one would imagine that could have something to do with it. Lots of different modems and bootloaders out there aswell.
[Galaxy S 4 i9505 Original Android Development] worktorest:
Alright, no biggie, back to what it was before. [emoji2]
[Galaxy S 4 i9505 Original Android Development] mikecantreed:
Lol. Moving to a completely different version of Android and to an un-unified build without wiping sounds pretty cool.
[Galaxy S 4 i9505 Original Android Development] jcasares:
Yes, I moved to another phone after that kernel change as it was quite unstable (not that it was perfect before). I sold my phone and the one using it now has issues with WiFi and Bluetooth among other unstabilities with current nightlies.

For 08/03 you have the M9 snapshot release. It's based on older code from the end of July. I wasn't able to get from the web a nightly release before the kernel change. I'm also looking for someone with the zip file to go back to that version for the one using that phone now.

Anyone can help?
[Galaxy S 4 i9505 Original Android Development] drewsky208:
Yeah there was some code commits in there after M9 that were pretty noteworthy and needed, which is why I'm searching for the 8/3 nightly just so I have some stability.
[Galaxy S 4 i9505 Original Android Development] foxbatul:
guys....03.01.2015 it s perfect. ( as 99% from CM product ) ,

M9, 10, 11 are OLD ( CM work DAILY) so there are more then 100 ( onehundred ) builds since.

Please let us know what error have on latest nightly ? We are very close from CM12 and you are still almoust 6 month late :)
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
So, invisiblek will only support the vzw jflte?

How about us? jfltexx int. Model? Any perspective?

Come back invisiblek. Dont leave us :'(
[Galaxy S 4 i9505 Original Android Development] Me Gusta:
Just wait. They support so many devices. They can't upload them all at the same time

Me Gusta!
[Galaxy S 4 i9505 Original Android Development] Soufiansky:
Agree , i think the next nightly will be CM12 ;)
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
From what dev? invisiblek? Who will be our new developer?
[Galaxy S 4 i9505 Original Android Development] Me Gusta:
Cm itself. Cm just had building bots. Invisiblek does not build a build personally every evening. The whole team develops code and the bot builds it into a rom

Me Gusta!
[Galaxy S 4 i9505 Original Android Development] drewsky208:
It's not perfect. It may work for you because you are not using parts where instabilities are manifested but they are still there. I asked if anyone had the august 3 nightly build around for a specific reason. If not then thanks please move along.
[Galaxy S 4 i9505 Original Android Development] foxbatul:
@ drewsky208 - please give us more details about your problems - where did you find issues ?

thank you
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
LoL, M13 final build is on the door before the kk code freeze and people still having problems...

Its over guys, were done with KK branch... Move on:)
[Galaxy S 4 i9505 Original Android Development] mikecantreed:
See you bums back at Square 1.
[Galaxy S 4 i9505 Original Android Development] drewsky208:
Sure...due to the obvious end of development of CM11 I haven't dug super deep to find exact cause but from what I've dug out of the logcats, it is centered around kernel<->radio interface, specifically wifi and bluetooth radios.

On the wifi side: Under certain circumstances wifi will hang (no data connection) even though it shows "on", attempting to off/on wifi will result in settings saying wifi=off but wifi bar still visible. Eventually there will be a kernel error logged in logcat that there was an exception. Other times wifi will just drop and come back continuously until you restart.

On the BT side: best I can describe is that BT hangs up sometimes. Restarting BT will sometimes get it fixed but it's rare: usually requires a reboot to make it 100% again. I can manage one good connect with BT to car or headset or something, after that BT will sometimes go "deaf" and not connect to a device again unless forced. On occasion I've also see where when I disconnect a BT connection, phone still thinks it is connected. This introduces some deadlock in the kernel space leaving the kernel spinning at 100% forever. It will suck a full battery dry in about 90 minutes and will make the phone burning hot. I've got several BT LE devices (fitness trackers) and they sometimes can't be connected to after connection to headset- or car-type connection.

These all started occurring when the kernel changes were made around Aug 6 nightly and I sat back and waited, figuring development would nab it. Then lollipop came out and development on CM11 all but stopped. So all I want to do is revert my daily driver to the Aug 3 build until CM12 becomes viable. I know Aug 3 is good as I was on it for a long time while they sorted the critical problems with that kernel change, which I want to say was a month or so. I use BT *alot* and I know that my use case isn't probably typical, which is why I suspect I get the chorus of "it's perfect!" when I say it isn't so hot :)

Hope that helps.
[Galaxy S 4 i9505 Original Android Development] Soufiansky:
I miss cyanogen , i think i will flash it again :((
[Galaxy S 4 i9505 Original Android Development] O-T:
I think he has provided a thorough explanation some posts back. Here's one more.

All jflte builds, nightlies & M*, after beginning of August 2014 has this flaw:

Searching for networks operators fails: "error while searching for networks"

http://xdaforums.com/showthread.php?p=56857814

https://jira.cyanogenmod.org/browse/CYAN-4902

really bad when auto connect to operator with highest price rate. You just can't choose. Impact all QualComm phones like htc M8 and several unified S4 models, ticket assigned to invisiblek (last visited this thread around post #4500'ish) , probably never solved.

So - I understand [MENTION=1397915]drewsky208[/MENTION]. He's not alone.
[Galaxy S 4 i9505 Original Android Development] Cozmos23:
As long as LP stays this ugly and space-wasting I will not switch to CM12.

Afaik the only improvement is the better battery standby management where I excuse me for my hash words but don't give a **** :p

A really big improvement would be easy access and uservconfiguration of wakelocks, background processes and a smart option to change colors. F.e. everything which is black to white and the opposite.

An stock operating system should not be themed in my opinion. It should be in the basic functions showing.

The look of the Interface should completely be a user based choice.
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
agree. and [MENTION=2385005]invisiblek[/MENTION] was a great OP for us for CM11, especially when we had those random reboots ages ago. Hope [MENTION=2385005]invisiblek[/MENTION] will be opening the new CM12 LP thread for jfltexx.
[Galaxy S 4 i9505 Original Android Development] foxbatul:
thank you

Oki doki.. seems to be not on all device, - I use BT for data trasfer and audio call with no problems at all ( and wi fi too ).

You are right with those issues, I almoust forget about because my phone doesn't have .

It's dificul for roaming connections, indeed...

Thank again for your response. have a great day.
[Galaxy S 4 i9505 Original Android Development] kaott:
+10000. so much white is meh. i wont install LP until i can paint it black.
[Galaxy S 4 i9505 Original Android Development] !crazy:
It is obvious that M do not receive any special attention from developers. They do freeze the code at one point, and try to fix bugs (or just hope upstream developers will fix them.), but they do the same (bug fixing) with nightlies, while new features do not come at the rate which is really troublesome. Sometimes they do come at the rate and bad things can happen, but for us, people who follow the situation this is not an issue. When it happens we just wait, or go backwards (restore nandroid) if we first figured how bad things are.

From my experience nightlies get bug fixes at faster rate, so sticking until next M doesn't make sense. Only for people who visit forums once in a while and have no time to follow how situation develops, only for them M makes sense, because the probability to hit the nightly where things went bad is smaller.

When everyone and his dog report nightlies to be stable, as the current situation, sticking to M is nonsense.

On the other side, software is strange animal, so it can be that some strange bug will hit me or you exactly b/c of the specific way you, or I use our phones, but the current builds are in general quite stable.
[Galaxy S 4 i9505 Original Android Development] worktorest:
I like how fast it is to turn off and reboot phone on cm11. With art running, everything is smoothhhhh.
[Galaxy S 4 i9505 Original Android Development] pa3dpl:
On irc about sgs4 20:49:01 <•invisiblek> not that it'd be hard, but i'm no longer supporting/maintaining devices that i don't personally own

Verstuurd vanaf mijn GT-I9505 met Tapatalk
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
And no Cm12 for jfltexx yet... We need a new dev. :-\
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
OMG... :rolleyes:
[Galaxy S 4 i9505 Original Android Development] measel:
How about we collect some dough to get him one if [MENTION=2385005]invisiblek[/MENTION] would support that?!
[Galaxy S 4 i9505 Original Android Development] !crazy:
With other words, this device has no maintainer any more (for cm 11), or there is another point I am not able to get?

If yes, some people do take a bit care if someone make it easy for them, I think , b/c here and there one can see a commits which target jflte devices.

And it works so well for me. Until I hear for some security issues Ill probably stick with this until CM 12 or another alternative become stable enough (what maybe already happened ☺? But I still have no will to switch. My intuition tells me this is still more stable than Android 5 based ROMs.
[Galaxy S 4 i9505 Original Android Development] 135Shadowsoul:
No E anymore :(

Hi every1,

perhaps any1 of you have any idea about the strange behavior of my GT-I9505

Since a few weeks, my device do not want to enter Edge-MobileNetwork anymore. 3g, h+, LTE working. I thought about, it may be a problem of my provider, german Telekom/T-Mobile, cause there was a mobile network problem where i am. But now, it seems to be fixed, and even a friend has E with his Samsung Stock GT-I9505.

Do you know, if there is any chance to test if GSM-Adapter is ok/damaged? Or any idea how to workarround?

Tested following: sim-card in other I9505 => working E, other sim into my device => 3g, h+, lte working (maybe there was no E). Tryed some reboot and reset APNs. With a CM-flashed device it would be hard to get it repaired, even its 13month old... :(

About my Device: XXUBMGA Bootloader (non knox), XXUBMH1 (latest non-knox) GSM modem (flashed already a few min b4 this post), XXUGNF1 LTE-Modem, CM11 M12

If you need any more information, just ask and i will answer.
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
Please someone help us. We need a maintainer...

Invisiblek, come back man... We need CM 12.

We are ortans now...:'(
[Galaxy S 4 i9505 Original Android Development] O-T:
You have MGA bootloader version mismatch with NF1 LTE-modem.

http://xdaforums.com/showthread.php?p=57926628

... will soon edit post to show what LTE-modem

: no-knox bootloader MGA need LTE-modem MH1.

This modem is NOT any WiFi-fix, it's the correct LTE-modem for YOUR bootloader version.

Basically you will undo the update you did to NF1. Latest KitKat LTE-MODEM on JellyBean bootloader will trash WiFi and/or sound.

http://xdaforums.com/showthread.php?p=50787570

MK9 is also possible, LTE-modem built 2013 November release 9 =MK9 letters decoded.

http://xdaforums.com/showthread.php?p=57993230
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
I want to request to become the new maintainer but still don't know how, who I should contact...

[MENTION=2385005]invisiblek[/MENTION] can you give me some straight?

Inviato dal mio GT-I9505
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
One vote for you. Thanks for this. Would be great!

Anyone please help us.
[Galaxy S 4 i9505 Original Android Development] O-T:
Abandon this? http://xdaforums.com/showthread.php?p=56833480

or loads of time to dedicate [emoji4]
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
He can handle it! Please Antares One be our maintaner!

Will be our salvation! No more orfans! :D
[Galaxy S 4 i9505 Original Android Development] Soufiansky:
I support [MENTION=5464206]AntaresOne[/MENTION] too :)
[Galaxy S 4 i9505 Original Android Development] Heathered:
Me too... :)
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
AntaresOne was also my first thought!
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
if original OP [MENTION=2385005]invisiblek[/MENTION] can't be our maintainer, then agree [MENTION=5464206]AntaresOne[/MENTION] would be EXCELLENT.
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
Now Im seeing a light in the end of the tunnel!

Antares is our maintainer now! invisiblek need to talk to the moderator of this forum and is ok :)
[Galaxy S 4 i9505 Original Android Development] Yousvel:
@AntaresOne would be a good choice!

I support [MENTION=5464206]AntaresOne[/MENTION] too. He is one of the great developers I know.
[Galaxy S 4 i9505 Original Android Development] worktorest:
Awesome. I just want cm11 to reach code freeze and stable build.
[Galaxy S 4 i9505 Original Android Development] stephendt0:
Me too. I'm still having terrible trouble with my i9505 even after all these months. I'm really liking what [MENTION=5464206]AntaresOne[/MENTION] has been doing with CM12 development.
[Galaxy S 4 i9505 Original Android Development] 135Shadowsoul:
Thanks for answer.

whts is strange for me now: only Edge wont work, 3g, h+, LTE are working. And eben E was working for month, only last time it wont work :(

About the 2 link you posted: Old bootloader: Any GSM modem, and MH1 LTE Modem (like i have). But im trying to Update to MK9

€dit: THANKS MAN!!! Flashing MK9 Helped (for the moment!!)
[Galaxy S 4 i9505 Original Android Development] worktorest:
What kind of trouble u having? I got no major issues with the recent nightlies, just unable to open the stock camera from time to time. [emoji16]
[Galaxy S 4 i9505 Original Android Development] lucsbran:
Yep, he's the best. Already run his awesome ROM unofficial CM12.
[Galaxy S 4 i9505 Original Android Development] foxbatul:
yes, I have no issues on latest nightly as well..what " terrible "? I hope that it's not a joke..
[Galaxy S 4 i9505 Original Android Development] timstanley1985:
Email devrel@cyanogenmod.org
[Galaxy S 4 i9505 Original Android Development] Yousvel:
Good news for the T-mobile users!

There is official cm12 available for T-Mobile Galaxy s4. Here's the link:https://download.cyanogenmod.org/?device=jfltetmo
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
Email sent, just wait for an answer now
[Galaxy S 4 i9505 Original Android Development] Soufiansky:
Great , so excited [MENTION=5464206]AntaresOne[/MENTION] :D

But what a maintainer do exactly ? He answer our questions on the thread ? because when the other maintainer was here i wasn't suscribed in xda so i don't know :D

Thanks and good luck !
[Galaxy S 4 i9505 Original Android Development] snakecharmer23:
If I recall, Mr. CyanogenMod himself uses a T-Mobile Galaxy S4 so he's probably the device maintainer. My fingers are crossed for other variants.
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=5464206]AntaresOne[/MENTION] since your unofficial CM12 is unified will you try to maintain the official as unified also? SPH-L720 here, I am afraid you are our only hope :(
[Galaxy S 4 i9505 Original Android Development] dcillusions77:
Have you heard anything yet?
[Galaxy S 4 i9505 Original Android Development] !crazy:
Why not? If he starts maintaining official CM 12 why would anyone need unofficial thread? Who wants can flash alucard kernel, and he will be in the position to add a feature or two from alucard, or to use settings he prefers.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Unofficial has been changed time ago to Optimized... the official CM12 will be ONLY for JFLTExx... Optimized is a Unified build for all variants... this is the reason why the 2 roms will be available and will be different... I hope this will solve any doubt...
[Galaxy S 4 i9505 Original Android Development] worktorest:
If cm makes Antares the official dev, will he get paid or smth?
[Galaxy S 4 i9505 Original Android Development] stephendt0:
This ROM has been very buggy for the last few months. I get the odd camera issue too and it is very annoying when you NEED your phone to just work right there in the moment and it just crashes. I'm still getting intermittent bad battery drain, intermittent proximity sensor issues and intermittent WiFi issues. I'm honestly sick of it, I know I'm ranting but I just can't trust my phone on CM11. The M9 was the last build I've tried that was acceptable as far as stability goes. I've done 3 factory resets since then and it's pretty annoying.

Should I do another factory reset or just move to CM12? I just want a phone that works properly without having to stuff around flashing new nightlies and kernels all the time, rebooting and resetting etc. On the 5th Jan nightly which is very unstable for me.
[Galaxy S 4 i9505 Original Android Development] worktorest:
I'm on the 3rd Jan nightly and everything is fine except for the camera issue from time to time. I don't use my camera a whole lot so I wouldn't know how often it happens.

Battery life has been good. I'm using 2g network with wifi on most of the day. If I'm on 3g/lte outdoors, it would drain faster which is normal, but nothing unusual.

Did you wipe system/cache/data/dalvik cache (full wipe)?
[Galaxy S 4 i9505 Original Android Development] stephendt0:
I haven't done a full wipe for a few weeks. Nor should I have to but it's looking like I should. It's just a major annoyance for me, I have a lot of settings and configurations that can't easily be backed up with titanium
[Galaxy S 4 i9505 Original Android Development] dcillusions77:
Ya they get professional developer status level pay. They quit sleeping as well, they only eat, ****, and develop ROMs at that level
[Galaxy S 4 i9505 Original Android Development] worktorest:
You should then. I normally just configure the settings all over again, doesn't take v long tho. Just backing up the apps and dictionary would be enough for me. But thankfully I don't have to full wipe v often. [emoji41]

That's cool. Win-win situation. Hope he gets the approval.
[Galaxy S 4 i9505 Original Android Development] Soufiansky:
What ?? You mean it will be no more CM12 rom for the jflte ? The last nightly is the 05/01.

I think it's impossible ...
[Galaxy S 4 i9505 Original Android Development] smeroni68:
I belive you haven't read properly my answer post to !crazy post...
[Galaxy S 4 i9505 Original Android Development] AntaresOne:
OT

Lol...
[Galaxy S 4 i9505 Original Android Development] radz_:
Wheres the CM12
[Galaxy S 4 i9505 Original Android Development] DevastatorTNT:
Still hasn't been found... Maybe you could look in the fridge, last time it was there...

Inviato dal mio GT-I9505G utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
my guess is Monday or Tuesday we will have it.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
... nightly will start to be back when this commit will be merged!!

EDIT: Obviously from that moment dev will be officially the maintainer of cyano jfltexx...
[Galaxy S 4 i9505 Original Android Development] simonbigwave:
the reviewer Dan Pasanen, is invisiblek.
[Galaxy S 4 i9505 Original Android Development] !crazy:
Do you officially represent CM team, or you read that somewhere?

Everything is subject to change. If he starts maintaining CM 12 officially, he can change things, like he could start making unified builds. Or there is an argument against?
[Galaxy S 4 i9505 Original Android Development] smeroni68:
I'm in the dev team of AntaresOne and Alucard... if you check in OP of CM12 Optimized by AntaresOne, you can read the contributors usernames...

What I post here, is the underground that is ongoing and not yet public...

EDIT: contributors names has been cleaned... but no problem... me, Jimsilver73 and franzyroy are testers of the team...
[Galaxy S 4 i9505 Original Android Development] drewsky208:
Yeah welcome to my world. It is funny you you say it that way because the phone always seems to bork right when you really need it to work right :) I'm trying to find the Aug 3 nightly as that has more recent commits than M that is before the nasty kernel change that messed it all up. Clean wipes and reinstalls won't fix it: you can either get by for the next few days and hope that CM12 on jfltexxx will be 100% on its first release or install an older version. Nightly Aug 3 is what we need.
[Galaxy S 4 i9505 Original Android Development] Yousvel:
[MENTION=5464206]AntaresOne[/MENTION], this would be the results of your hard and long work! So, you can smile because you deserve even more than that. My prayers for you, my bro!
[Galaxy S 4 i9505 Original Android Development] !crazy:
Thanks for your answer.

---------- Post added at 06:20 PM ---------- Previous post was at 06:14 PM ----------

Lay nightly in general work well for me, and of you look the thread you'll see I'm not the only one which claims so.

Yes, it happens sometimes (but sure rare) that the device misbehave, but that is even true for stock not rooted devices with Touchwiz, or whatever. As a matter of fact Note 3 of my wife, all stock used to reboot and freeze here and there. It did had encryption on, and that probably made the things more complicated, but on the and it hit the ground from the fifth floor and now it behaves as expected.
[Galaxy S 4 i9505 Original Android Development] smeroni68:
Commit has been merged... Nightly of CM12 for JFLTEXX will start from this night to be online... Thanks Mattia (AntaresOne)!!
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
Nice! How about our maintainer? Will be Antares?
[Galaxy S 4 i9505 Original Android Development] smeroni68:
At this point... it seems true!!
[Galaxy S 4 i9505 Original Android Development] foxbatul:
http://youtu.be/zVT5VdteT8E

i9505 black ,

almoust 5 days battery life ( please add 10 more hours to the timer in movie )

low to moderate usage. ( ~ 2.5 - 3 hours talk time, mail , igo primo )
[Galaxy S 4 i9505 Original Android Development] Soufiansky:
Screen on time , i think it's 1hour :D

Every one can do that , you simply didn't use the phone.

Pst : next time do a good video please , half of the time we saw just the nap.
[Galaxy S 4 i9505 Original Android Development] foxbatul:
ok, no problem, I keep my promises so this it 's why a made this movie

and " the nap" it's here only from privacy reason, not by mistake. As you can see . all the time it's about the same phone, otherwise I can only post pictures. :)
[Galaxy S 4 i9505 Original Android Development] L.F.B.:
CM 12 Countdown for our jfltexx...

Cant wait.

Edit. Is out!

http://download.cyanogenmod.org/?device=jfltexx&type=nightly

Im thinking if Ill go to 5.0 abd loose my xposed... Its very dificult after a long time with xposed... We get used to it...:D
[Galaxy S 4 i9505 Original Android Development] Yousvel:
@AntaresOne is officially the new maintainer for jfltexx!

https://download.cyanogenmod.org/?device=jfltexx
[Galaxy S 4 i9505 Original Android Development] akne:
Is this suppose to work on all Samsung 4 models like the cm11 builds?