yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Q&A, Help & Troubleshooting] hell_storm2004:
So will Qualcomm's get Cyno mod?
[Galaxy S 4 Q&A, Help & Troubleshooting] mwazeer:
Re: codeworkx will no longer make CM for the S4.

Still s4 is not relesed and see the response on xda for s4, so cm should reconsider there decison; as with or without cm s4 will rock:D
[Galaxy S 4 Q&A, Help & Troubleshooting] Marvos:
This. Will it?
[Galaxy S 4 Q&A, Help & Troubleshooting] vyrus973:
I hope someone else will do the same great work D:
[Galaxy S 4 Q&A, Help & Troubleshooting] shoman94:
Re: codeworkx will no longer make CM for the S4.

As far as I know gpl compliance is only fire the kernel....nothing else. Also the link to the article about CM has an update that CM has not announced either direction officially. As entropy512 stated.... cyanogen himself uses Samsung so let's not jump to conclusions because of a few statements taken to far. They didn't announce the n4 support until they released for it. Some are acting like it's the end of the world. Lol

So until the phone is released and Cyanogen makes an official announcement..... let's just relax.
[Galaxy S 4 Q&A, Help & Troubleshooting] hell_storm2004:
This is so true!! But i guess everyone is disappointed.
[Galaxy S 4 Q&A, Help & Troubleshooting] :
To everyone that complains that CM won't build for S4 in this post:

http://xdaforums.com/showpost.php?p=39255132&postcount=27

Here is a communication from CyanogenMOD:

Like they say:

Source:

https://plus.google.com/+CyanogenMod/posts/7jywLJdswki
[Galaxy S 4 Q&A, Help & Troubleshooting] doodads:
no reason why not
[Galaxy S 4 Q&A, Help & Troubleshooting] Entropy512:
Nothing is ever guaranteed or set in stone until it happens, however:

I believe Cyanogen himself is picking up the AT&T version. I wouldn't expect it to be too problematic to do the bringup due to being Qualcomm-based.

International version probably doesn't have a maintainer lined up yet

No, the CM team is not retiring. The CM team is 80+ people.

However, the majority of the work on the Exynos 4210 and 4412 devices (I9100 and I9300 and close relatives) were done by a core team of about 4 people (5-6 if you count atinm and others that retired back in the Gingerbread days), with maybe 5-10 other frequent routine contributors. All of those core people and the routine contributors that worked on Exynos4 devices are going to other devices from other manufacturers, or outright retiring for a while.

The Qualcomm-based devices have a completely different maintainer team and those people are likely to pick up USA GS4 variants.

Yeah... A lot of the articles had AWFUL headlines... There's a big difference between the Qualcomm and Exynos devices, and there's also a major difference between "future looks bleak" and "absolutely not".

For Qualcomm-based GS4s, the future of CM on those devices looks quite positive. No guarantees, of course. If having stable CM is important to you, wait until stable CM is released for a given device before you purchase it.

For Exynos-based GS4s, the future of CM on those devices looks very bleak. No one has yet to express interest in doing a bringup/being a maintainer for it. The maintainers who have worked with previous devices have said that they absolutely not will be moving forward. But if someone else steps up to the plate, it could get support. I personally don't think that's likely - look at the Note2, codeworkx held back for a few months with the LTE variants before picking one up in order to try and give someone else a chance to step up to the plate. Similarly, it's been known that the Exynos GS2/GS3 family were on minimal life support for ages, but we're still active enough to review patches as they come in... There have been light contributions for minor fixes, but not major work being done by anyone.

The only time so far CM has definitively said NO to support of devices has been the announcement that devices with the Snapdragon S1 series of processors would end the line at CM7 due to lacking proper graphics hardware for CM9 and later. Down the line the team will probably have to make similar announcements for other devices (Tegra2 is barely hanging in there due to lacking NEON support, but that architecture's fate is not final yet.)
[Galaxy S 4 Q&A, Help & Troubleshooting] howtomen:
Re: codeworkx will no longer make CM for the S4.

So the big question is where is the big entropy going?:D always been a fan of ur work :P

trolol and awayyy!! Expect typos this is my phone.
[Galaxy S 4 Q&A, Help & Troubleshooting] LordManhattan:
Not making this into a geography thread, but you're wrong. It's:

- Russia

- Antarctica

- Canada

- China

- USA

Source: Wikipedia

He's moving to the Sony Xperia Z, if i'm not mistaken. (If he can get his hands on the c6602 version)
[Galaxy S 4 Q&A, Help & Troubleshooting] funkyblue04:
Re: codeworkx will no longer make CM for the S4.

It's really a shame that Samsung do not embrace the development community.

Imagine full CM on the Galaxy 4? Xperia Z is ok but crap battery life. No ability to swap if needed. Sigh. Unless you want to carry a Note your stuffed for battery life.
[Galaxy S 4 Q&A, Help & Troubleshooting] AMDPOWERFIST:
I think there will be a great deal of developers flocking to the S4. If the predictions of how many of these devices are going to be sold by samsung this year come to pass (100mill), then the S4 development section will be flooded with users looking for customizations...

A great developer wouldn't sit back and see the Exynos chipset as impossible, its rather a challenge.... A great developer would take on the challenge. Why only do things that are easy in life? Why not spread your wings and be one of the first developers to play with the Kernels of the brand new Octa 5 processor....

And because of this, i believe there WILL be a great deal of developers who cant wait to get their hands on this device, and to see what they can pull from it... Theres ALWAYS someone who is looking for a challenge, and sees a need and meets that need. So dont fret...
[Galaxy S 4 Q&A, Help & Troubleshooting] funkyblue04:
Re: codeworkx will no longer make CM for the S4.

No point developers flocking if there are no proper drivers or sources to work with.

You'll end up with a buggy port like the s3.
[Galaxy S 4 Q&A, Help & Troubleshooting] howtomen:
Re: codeworkx will no longer make CM for the S4.

You cant play with something u no nothing about.... Imagine having a 20k piece puzzle but u have no idea what the picture is supposed to be and u have to be blind folded... Not a fun challenge

trolol and awayyy!! Expect typos this is my phone.
[Galaxy S 4 Q&A, Help & Troubleshooting] AMDPOWERFIST:
With 100 million users + of a device there will be alot more people flooding to XDA forums, they will learn the process required for the CM port, and how Samsung doesnt release these sources... they will sign the petition thats been floating around for a few months, more pressure means more leverage.

And just because the CM team dont think they are up to the job, doesnt mean others arent, you'll get plenty of customisable Stock Sammy ROMs coming out and plenty of Custom Kernels.... DorrimanX (creator of an amazing S2 Kernel) has already said hes coming over to the S4...

You peeps need to just sit back, relax, chill, it'll all happen, this device is too big and too amazing to be left behind in the development world.
[Galaxy S 4 Q&A, Help & Troubleshooting] funkyblue04:
Re: codeworkx will no longer make CM for the S4.

The S3 was left behind. What makes the S4 so special?
[Galaxy S 4 Q&A, Help & Troubleshooting] howtomen:
Re: codeworkx will no longer make CM for the S4.

I make custom tw roms and trust me a lot of the stuff trickles down from cm.... Cm isnt up to the challenge because many good kernel devs and rom.devs from hacksung tried... Petitions where made... Ask dorrimanx how many cm patches hes used.... Its a key part of the dev scene. Kernel developing isnt fun if you have another superbrick fiasco or other stuff.... Thats why im getting the Qualcomm version

trolol and awayyy!! Expect typos this is my phone.
[Galaxy S 4 Q&A, Help & Troubleshooting] Entropy512:
There's challenging (any device is challenging - look at the current Xperia T modem bootup situation, I spent almost all weekend on that and all of the past 2 weekday evenings. No, I'm not blaming Sony for it, because there's more and more evidence that we broke it somehow when pulling in graphics patches for 4.2... It's less frustrating because it involves digging through massive piles of code and patches to figure out why two things are behaving differently, instead of "why the hell is this stupid blob misbehaving"), and there's "stickman vs. the wall" levels of frustration.

When you are lied to multiple times by a manufacturer and they break every promise they make, it goes WAY beyond mere challenge.
[Galaxy S 4 Q&A, Help & Troubleshooting] giajp:
R: codeworkx will no longer make CM for the S4.

Also The european s4 with snap!!!! :D

Sent from my Google Nexus 4 using CyanogenMod 10.1
[Galaxy S 4 Q&A, Help & Troubleshooting] AMDPOWERFIST:
I totally understand dude. I have done some programming in the past, but not for Android.

But looking at this from a NEED to NUMBERS ratio, the S4 is going to be the most widely distributed Android device on the planet... Therefore there will be a much bigger user base, with this, many developers from other devices will flock to this device, and new developers will arise, its the natural order of things.

This is why i am not too fussed about the CM team not taking up on this. And dont get me wrong, i luv the CM groups work, i have used it on my S1 and my S2 for over 3 years now. But i am very confident that someone will step up to the plate for this fantastic device and create some wonders for it.

Also, with such a larger user base, comes more pressure ON samsung as well... So who knows, the S4 might be the tipping point where samsung goes.... Alright, lets give these developers what they want for the Exynos chipset...

So basically since this device is going to be developed for, it has the sheer numbers to venture much further than the S3 (this is all based on the assumption that it sells as much as Samsung has planned, which i believe it will)
[Galaxy S 4 Q&A, Help & Troubleshooting] fix-this!:
Ill say this again. Please don't buy a phone just in hopes it will get aosp. If you need those types of roms get a nexus.
[Galaxy S 4 Q&A, Help & Troubleshooting] SeaFractor:
Steve Kondik knows ;)

http://www.theverge.com/2011/08/15/samsung-hires-cyanogenmod-founder-steve-kondik/

Too bad he's not going to be able to share since Samsung is his employer. But perhaps he can help work to generate a state of mutual collaboration between AOSP coders like CM and Samsung.

Could also explain why Samsung is excited about the S-Apps if they've got really talented folks like Steve working hard.
[Galaxy S 4 Q&A, Help & Troubleshooting] AMDPOWERFIST:
VERY NICE !!!

Even better
[Galaxy S 4 Q&A, Help & Troubleshooting] eksasol:
You can't demand it because the developers are not getting a salary to make it for you. I suggest a couple things:

-Create a bounty or do some donation.

-Buy the S4 for a developer.
[Galaxy S 4 Q&A, Help & Troubleshooting] Entropy512:
He works for Samsung USA, who are fairly insulated from the Koreans that call the shots. As a result, his employment with Samsung has been of little to no benefit to CM... Steve the Samsung employee and Steve the CM founder/maintainer are almost two entirely separate people.
[Galaxy S 4 Q&A, Help & Troubleshooting] REVERSiN:
sometimes i wish i could get my hands on that LTE version only cause of its Processor, i honestly can say i used to be a CM fan back when i had the GS2 but since i bought the Note 1 i had many disappointment (iam saying this not to offend anyone i respect all Devs) but that device never got the real attention it took nearly a year to have CM9 i think it even was way after we had the China Leak based on ICS back then... true dream, i admit the brick bug was scary and a badass chip but what can i say we got through it at least most! and community found a solution with many options, Devs used sources to build KERNELS others patched and repacked well in the end we had it done and hush... none complained more.

the issue is the Note never got the gestures support as it should have been and neither did its Pen (it worked but not with button functionality) a user developed an APP to fix this GREAT but still lacks too much support, i know Xplowild is having a hard time on exynos but they didnt giveup on Note 2 ? neither GS3 ? so whats wrong, we cant have a bugfree CM but WTH lets try help out i remember members *****ing on the devs to fix bugs other said its not stable most complained of features - screw that we need CM sometimes but not quite the appearence but the performance thats all, i dont care for theming neither for looks at all its fine as long as it Works :)

anyway my opinion so dont FLAME on me its what i learned by being a samsung user for a long time and iam not sorry about it.

free to agree and dis...if you have a problem with what i said then answer and quote me i wouldnt mind hearing other people's thoughts as long as they are cevilised!

Thanks ;)
[Galaxy S 4 Q&A, Help & Troubleshooting] BarryH_GEG:
Here's something to ponder. Based on their market share, 70% of Android devices sold in 2013 will be Samsung. If the most recognized and largest development supporter of the Android platform (CM) boycotts Samsung their relegating themselves to 30% of the market. Since enthusiasts (us) make up 5% of device sales, even if every enthusiast boycotted Samsung too, it wouldn't mean a thing to Samsung. And since nature abhors a vacuum, leaving 70% of the Android market unsupported by a credible entity (CM), some enterprising soul or group will create one to capture what CM left behind. And that new larger-than-CM entity will support 70% of the market while CM will be left with the fragmented pieces of what's left. CM's smart. You can see it in the wording they used in their recent statement about not supporting the SGS4. I'm sure there not going to self-immolate to prove a point no matter what any of their individual team members or groups may say to the contrary.
[Galaxy S 4 Q&A, Help & Troubleshooting] slaphead20:
Re: codeworkx will no longer make CM for the S4.

Best conspiracy theory thread ever! ;):D
[Galaxy S 4 Q&A, Help & Troubleshooting] Kremata:
Ah Slapheap you're finally here. We need some of your slap in the head. ;)
[Galaxy S 4 Q&A, Help & Troubleshooting] slaphead20:
Re: codeworkx will no longer make CM for the S4.

Not getting involved in this one, ignorance is bliss! :D
[Galaxy S 4 Q&A, Help & Troubleshooting] Entropy512:
Except you forget we're a volunteer organization. Not supporting a device would not cause us to self-immolate. Supporting a device consumes a valuable resource: Time. It doesn't provide any significant benefit to CM as a whole whether a single given device is well-supported or not.

Has the fact that all Exynos4 devices are stuck at bugridden nightlies despite them being on the order of 10-20% of our installed devices caused CM to implode? No.

Has anyone replaced the CM Exynos4 maintainers that have throttled back their Exynos4 work to only a tiny fraction of their free time? No... We get occasional contributions from others, but they're rare.
[Galaxy S 4 Q&A, Help & Troubleshooting] Jeremy:
Well entropy I hope you indulge my slightly selfish question here:

I am going to purchase the snapdragon version just so I may have CM support.

1) What are the chances that a couple of months down the road, the exynos variant gets equally good CM support, and I'm left lamenting the fact that I gave up a better processor for nothing.

2) Or in a even worse case scenario, the Snapdragon variant doesn't get CM support as well.

I'm merely a layman about to dump a serious amount of money on a cellphone. I just pray that my decision won't be a regretful one.

Thanks in advance for bearing with me.
[Galaxy S 4 Q&A, Help & Troubleshooting] Kremata:
Could this be the reason why Samsung didn't care so much about the S3 developement and is not helping CM?

Source->http://www.forbes.com/sites/greatsp...-end-market-ambitions-strikes-at-apples-core/
[Galaxy S 4 Q&A, Help & Troubleshooting] hell_storm2004:
My first wish is that Samsung streamline all phones across the world. Not release tons of versions of the same phone everywhere. I find myself lost in the model numbers soon after Samsung releases a phone. Happening since Galaxy S days!
[Galaxy S 4 Q&A, Help & Troubleshooting] Kremata:
I think they would also like that but the problem is with the parts. Apple's minions are willing to wait in line for months but Samsung wants to flood the market and deliver everywhere in the same time so they can't have enough parts to have a unified model.
[Galaxy S 4 Q&A, Help & Troubleshooting] hell_storm2004:
Well maybe. I wish by now they would have been able to manage that. I think Samsung is going in for that quick launch times to tackle Apple. Normally Apple has a solid 1 year gap between their releases. How successful it will be, no clue.
[Galaxy S 4 Q&A, Help & Troubleshooting] DJCrapsody:
Re: codeworkx will no longer make CM for the S4.

Other countries in Asia are indeed getting the Snapdragon ones.
[Galaxy S 4 Q&A, Help & Troubleshooting] hell_storm2004:
Rumors are for $650 detail. How true... ask Samsung! :)

http://www.ibtimes.com/samsung-galaxy-s4-release-date-coming-us-price-set-650-1137029

http://www.android.gs/samsung-galaxy-s4-production-price/
[Galaxy S 4 Q&A, Help & Troubleshooting] TingTingin:
Re: codeworkx will no longer make CM for the S4.

See this

www.sammobile.com/2013/03/20/your-c...variant-of-the-galaxy-s-4-we-have-the-answer/

S4 INFO
[Galaxy S 4 Q&A, Help & Troubleshooting] hell_storm2004:
How come England is getting both version?? This is unfair. And i hope all Pool fans end up with 9505! :p
[Galaxy S 4 Q&A, Help & Troubleshooting] Kremata:
In China we get the Exinos (Officially) but we can get all of them. he he he
[Galaxy S 4 Q&A, Help & Troubleshooting] Entropy512:
1) Pretty low. And the "Octa" isn't really a better processor. It's really only a quad. The extra four cores are a power management feature, which is far less necessary with the Kraits because they're significantly more efficient power-wise than the A15 and also due to Qualcomm's ability to clock each core independently. It looks like Exynos5 has the same limitations as Exynos4 - you can't even enter any of the deeper idle states if more than the first core is online.

2) Fairly unlikely, but it depends on carrier variants. Some carrier variants may be very poorly supported if no one picks them up. This will be the first time Samsung ever distributes Qualcomm devices heavily outside of the US, so it's all a big unknown. I suspect at least one or two of the Qcom variants will be well supported, but I'm not sure about whether they will ALL be supported. For an unsupported variant, it'll probably be far less effort for a new maintainer if a few variants are supported, but again, the key unknown is always: Will a device have a maintainer?

I've said it before, and I'll say it again: If having stable CM on a device is critical to you, don't buy it until it has stable CM. Also, even if it has stable CM, check to make sure the maintainer team isn't disgruntled and approaching burnout (see CM9 on Exynos4...) - if you see the maintainer constantly ranting about the device it's a bad sign. It's a REALLY bad sign if the maintainers for every device with a similar SoC are disgruntled (Exynos4).

Doesn't really make sense, since the best thing for both parties would be to reduce the costs for the most important CM resource: Time.

That way, both sides win. Samsung gets lauded for being friendly to developers, and their devices are viable for those who want to run operating systems other than touchwizz. Seriously, a little bit of documentation and source code and they would have made their devices significantly more attractive to 200,000 or more people (that was the number of confirmed installs on Exynos4 devices back last September or so), with most of the heavy lifting done by volunteers. Big reward (200k+ happy customers, who may recommend Samsungs to friends and family that will stay with Touchwizz, increasing the numbers even more), very low cost to them. We weren't asking for anything related to the special Touchwizz features, we just wanted to get core platform functionality working reliably like what was possible with Qualcomm and OMAP devices thanks to CAF and OmapZoom.
[Galaxy S 4 Q&A, Help & Troubleshooting] BarryH_GEG:
What is CM? A common methodology, some infrastructure, some (very) smart people, and some name recognition. None of those things are either irreplaceable or not replicable. Hell, CM melted down over an internal turf war and lost their original domain. It's no different than if your favorite restaurant moves 20 miles further away. Some people would make the drive while others would find a new restaurant. How many posts have you seen in forums started for new phones that say “Hey (insert developer), I’m glad you’re supporting (insert phone). I really missed your work from when I had a (insert phone)." So if CM decides to boycott Samsung it’ll be interesting to see what the impact is. To people’s buying decisions, development support for Samsung devices on the whole, and to CM itself. If I were to bet I’d say a small percentage of conscientious objectors buying phones this year will follow in CM’s footsteps while the majority will ***** about the absence of CM, buy new Samsung phones anyway, and use ROMs from non-CM developers which should still be plentiful. And aside from driver/documentation issues Samsung's still the most "dev friendly" when it comes to unlocked bootloaders, tolerance of third parties hosting their s/w, and warranty support. It'll be interesting to see what the outcome of all this is.
[Galaxy S 4 Q&A, Help & Troubleshooting] FinancialWar:
Yet, I have two people thanking my post. personally I couldn't care if it doesn't not come to S4, won't affect my purchasing decision.

CM isn't that good, the true hurts, doesn't it?

Just because others and I don't like what you like, doesn't make us ignorant.
[Galaxy S 4 Q&A, Help & Troubleshooting] BarryH_GEG:
Kind of begs the question "at what?" and "for whom?" CM has a loyal following and a lot of developers use their s/w as a launching point for their own. They also have an enormous talent pool and have solved problems even the OEMs themselves couldn't or ignored.To people wanting to run non-stock s/w the absence of CM is a big deal and it's kind of disrespectful telling them it shouldn't be or that it shouldn't matter.

But you are bringing up a trend I've noticed across a bunch of different forums for newer devices where people who used to flash custom ROMs are sticking to stock s/w. I have no idea how big a group that is but it’s noticeable. Back in the day, h/w was slow, RAM, was scant, Android was evolving, overlays were huge, and OEM s/w was crap. With faster SoCs, more RAM, higher quality more functional stock s/w, and the vast improvements in the OS itself there's less motivation to flash. And with HTC, Asus, and Motorola making you give up your warranty to do it I think that's giving some people pause.

So, different strokes...
[Galaxy S 4 Q&A, Help & Troubleshooting] Kremata:
No, it make you an ignorant because you don't even realize that without CM your beloved NeatRom Lite might not even exist. Yes the CM itself for the S3 was (and still is) not 100% but the team are a platform that most all AOSP ROM devs are using. CM is not just another ROM. This is why you are ignorant because someone just shoot you in the face and you don't even realize it.

ha ha ha

are you 8 years old?
[Galaxy S 4 Q&A, Help & Troubleshooting] SilentEYE:
The most important thing on CM Roms are the security patches like Openpdroid.

If you prefere security and dont want to use chinese security tools like LBE, then especially CM is the right ROM for you.
[Galaxy S 4 Q&A, Help & Troubleshooting] FinancialWar:
Might? Can you be more accurate?