Database Develop

Samsung - CM - Exynos... whats all the fuss about?

Hello
I'm reading a lot of comment about people never buying a SAMSUNG phone again on this forum.
I believe it has something to do with CM team ( who are these guys? ) and the CPU type and source code.
Could you please care to elaborate? As I am planning on upgrading to GN2 but ofc I need root access and the latest OS all the time
Thank you.

Which post are you refering to? I just seem to see post saying how awesome the Note 2eand SIII are!

Dmwitz said:
Which post are you refering to? I just seem to see post saying how awesome the Note 2eand SIII are!
Click to expand...
Click to collapse
It's not just 1 post,
All around the forum , especially in the GN forum ( where I spend most of my time ) I see people complaining about Samsung devices in the future and how they will never buy another samsung again ...

I guess it all depends whether or not you want to run CM custom roms on your device.
Furthermore Samsung promised to release the Exynos sources...So we'll just wait and see

Problem ist that the source code is no available and without no new CM AOSP AOKP Roms possible. The company said in the past that they will release the code, but till today they don't.
Other companies like Sony did it better and supports the community. That's also a reason why great Dev won't work for our Note...

It's not impossible to bring new roms without sourcecode - we still have CM10 and will get CM10.1 - but the experience is not the best, and devs have to put A LOT of work to even make it work.
Samsung promised they will release their sources - yet untill today - they didn't. So it's simple as that, if they release sources - devs might finally fix some bugs and push CM10 into stable. Without sources we might never go out of nigthlies because some bugs might never get fixed.
As for SONY, yes they release all their sources, but remember that they used to be like Samsung untill their market share shrinked, so now they're most likely just trying to appeal to customers with that. Hope they won't change their mind about it when/if their sales go high again ( I'm looking at you Xperia Yuga )

User_99 said:
Problem ist that the source code is no available and without no new CM AOSP AOKP Roms possible. The company said in the past that they will release the code, but till today they don't.
Other companies like Sony did it better and supports the community. That's also a reason why great Dev won't work for our Note...
Click to expand...
Click to collapse
Very true, but I think they don't give a ....about a few devs and users being frustrated when they sell millions of devices...Like most of the big selling companys

bebseh said:
It's not just 1 post,
All around the forum , especially in the GN forum ( where I spend most of my time ) I see people complaining about Samsung devices in the future and how they will never buy another samsung again ...
Click to expand...
Click to collapse
I think u r talking abt this thread..especially this one..

a pall of gloom has descended on the community it seems
check out CM 10 thread
i hope its a temporary phase -
http://forum.xda-developers.com/showpost.php?p=35210934&postcount=1651

Samsung didnt want the devs to work for the android community because in the end it gives an advantage to google and its os. Samsung wants people to buy its phones because of their new features added in their TW that are not available on true android. They in the future wants their devices ti be free from the android pool. Because of the tiring update process. No source code release is just what keeps dev from moding their devices so they can market their new phones and limit those features in the old models. I dont think they will care about dev going to other vendors. Because once they got hold of a new indigenous OS. they will market its dev kits and hardware for developers and they know how to bring them back.
Sent from my GT-N7000 using xda app-developers app

[Q] CyanogenMod on the z?

I want this hardware with cm or pure aosp software, and I'd love it if you all could share some of your knowledge:
What are the challenges, obstacles, and chances of cm on this device happening?
I don't know much about Sony and their way of locking or unlocking the bootloader, so what can we expect here?
Codeworkx praise Sony for their recent contribution to the community, can we expect this to continue?
Are there any new proprietary additions to this phone compared to the other xperia line, something new that will prevent cm running smoothly?
How are the free xperia team going with their work?
Please share and enlighten me.

Just wait for FXP http://code.google.com/p/freexperia/
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Also
http://freexperiaproject.com/

dioggo92 said:
Just wait for FXP http://code.google.com/p/freexperia/
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Also
http://freexperiaproject.com/
Click to expand...
Click to collapse
Cool, but have they succeed with proper ports of cm to xperia, no battery issues, no camera issues, all hardware working properly?
The z has the new "dual camera thingy" (i can't remember what the press release called it) for proper hdr, and considering this is a somewhat new invention, will Sony give out proprietary sources/drivers to create open source versions?

CyanogenMod went well for my arc S, and is coming alon great for my Xperia T.
I can't imagine why the XZ will be any worse.
I think it will actually be better as the XZ will be released on 4.1, with the promise of 4.2 coming soon after.
I can't see poor development being an issue with this device.

You never know until release what the exact problems with a device are going to be.
That said, given how Sony is diverging less and less from reference sources for various platforms with each generation and the fact that it has the exact same SoC as the Nexus 4 - it's looking VERY promising.

Entropy512 said:
You never know until release what the exact problems with a device are going to be.
That said, given how Sony is diverging less and less from reference sources for various platforms with each generation and the fact that it has the exact same SoC as the Nexus 4 - it's looking VERY promising.
Click to expand...
Click to collapse
So exciting! really looking forward!

cant wait to see this phone..also cant wait to see stock Android on this.

Entropy512 said:
You never know until release what the exact problems with a device are going to be.
That said, given how Sony is diverging less and less from reference sources for various platforms with each generation and the fact that it has the exact same SoC as the Nexus 4 - it's looking VERY promising.
Click to expand...
Click to collapse
Cyanogen launched M builds, which are most stable builds and a few phones launched them. Do you know what is reason, why M builds aren't available on any Sony phone yet (for example Xperia T) ? I thought M builds will be available on phones, which are easier to develop - for example, Nexus, US SGS3, latest Sony phones etc. Thanx

-A-P-M- said:
Cyanogen launched M builds, which are most stable builds and a few phones launched them. Do you know what is reason, why M builds aren't available on any Sony phone yet (for example Xperia T) ? I thought M builds will be available on phones, which are easier to develop - for example, Nexus, US SGS3, latest Sony phones etc. Thanx
Click to expand...
Click to collapse
Hmm, wonder if cm doesn't officially support Sony, that it is only the free xperia TM that does the conversion. But I dunno for sure
Edit: nope, never mind : http://wiki.cyanogenmod.org/index.php?title= Devices
A lot of Sony officially supported. I just never read the list

Eddiemc said:
Hmm, wonder if cm doesn't officially support Sony, that it is only the free xperia TM that does the conversion. But I dunno for sure
Edit: nope, never mind : http://wiki.cyanogenmod.org/index.php?title= Devices
A lot of Sony officially supported. I just never read the list
Click to expand...
Click to collapse
Fxp are the official maintainers for Sony devices for cm. Once the build is stable it is approved by cm and supported, that's how it works for now.
But I'm guessing it'll change as more people will buy Sony and with more developer support who knows might speed up. For now only 4 people (Fxp) manage over 25 Sony devices to get cyanogenmod on them.
Sent from my Xperia S running 4.2.1 using xda premium

mzr7 said:
Fxp are the official maintainers for Sony devices for cm. Once the build is stable it is approved by cm and supported, that's how it works for now.
But I'm guessing it'll change as more people will buy Sony and with more developer support who knows might speed up. For now only 4 people (Fxp) manage over 25 Sony devices to get cyanogenmod on them.
Sent from my Xperia S running 4.2.1 using xda premium
Click to expand...
Click to collapse
How's your xperia s running with that rom (assuming you're running cm, aosp, or aosp)?
I'm asking to get an idea of what to expect in terms of cm/aosp on the z.
I looked at a few videos of Sony's 4.1.1 rom on the pre prod models of the z and i was not very impressed with their work.
I "need" to be able to run cm or any aosp rom as soon as it's in my hands. Yea, I know it's a bit stupid then to not buy a nexus, but i want z hardware (and water proof) and expandable memory. Since nexus won't give me that, perhaps Sony can..?
I'm willing to sacrifice some functions, as long as the camera works (don't need effects, just clear pics) and the battery is good. (bravia and stamina can be sacrificed too, as long as cm doesn't drain more than stock sony)
Atm I'm on sgs3 and cm doesn't work very well battery wise (with 6-9% idle drain pr hour) and also too many camera issues. Having to cripple all the "smart" functions of a smartphone to get acceptable battery just doesn't make sense, so please share some of your views on Sony/cm in this regard.

mzr7 said:
Fxp are the official maintainers for Sony devices for cm. Once the build is stable it is approved by cm and supported, that's how it works for now.
But I'm guessing it'll change as more people will buy Sony and with more developer support who knows might speed up. For now only 4 people (Fxp) manage over 25 Sony devices to get cyanogenmod on them.
Sent from my Xperia S running 4.2.1 using xda premium
Click to expand...
Click to collapse
Im not familiar with Sony's dev community, because Xperia Z will be my first Sony's Android phone. Im wondering If Codeworkx get Xperia Z, he will became official maintainer with Fxp for Xperia Z ? Is Codeworkx's CM10 build for Xperia T different to Fxp's CM10 build, or they work together?
Thanx

-A-P-M- said:
Im not familiar with Sony's dev community, because Xperia Z will be my first Sony's Android phone. Im wondering If Codeworkx get Xperia Z, he will became official maintainer with Fxp for Xperia Z ? Is Codeworkx's CM10 build for Xperia T different to Fxp's CM10 build, or they work together?
Thanx
Click to expand...
Click to collapse
Codeworkx is different from Fxp. Anywho Fxp has listed z in its supported devices now on its website so yeah i think you can count them in.
It'll depend on codeworkx if he wants to join Fxp or not. I don't have the Xperia t so can't be sure about what you asked. I'll check the thread out and let you know.
Sent from my Xperia S using xda premium
---------- Post added at 09:40 AM ---------- Previous post was at 09:28 AM ----------
Eddiemc said:
How's your xperia s running with that rom (assuming you're running cm, aosp, or aosp)?
I'm asking to get an idea of what to expect in terms of cm/aosp on the z.
I looked at a few videos of Sony's 4.1.1 rom on the pre prod models of the z and i was not very impressed with their work.
I "need" to be able to run cm or any aosp rom as soon as it's in my hands. Yea, I know it's a bit stupid then to not buy a nexus, but i want z hardware (and water proof) and expandable memory. Since nexus won't give me that, perhaps Sony can..?
I'm willing to sacrifice some functions, as long as the camera works (don't need effects, just clear pics) and the battery is good. (bravia and stamina can be sacrificed too, as long as cm doesn't drain more than stock sony)
Atm I'm on sgs3 and cm doesn't work very well battery wise (with 6-9% idle drain pr hour) and also too many camera issues. Having to cripple all the "smart" functions of a smartphone to get acceptable battery just doesn't make sense, so please share some of your views on Sony/cm in this regard.
Click to expand...
Click to collapse
Oh my version! Well this new group popped up they made cm10.1 for Xperia S can't be used as a daily driver as of now was just testing it they launched it about a week ago still fixing it up . Other than that i am running cm10.
As far as your questions go Sony supports developers! If you want to get cm on your device don't get it from a carrier! Get it unlocked like me unlock the bootloader and start flashing!
Xperia z shares many similarities in hardware with the nexus 4 so I'm guessing that would mean faster development. The only issue I can think of is camera since its a Sony proprietary! Like with the Xperia S. Had to wait till Fxp got a hold of a leaked beta jb driver. Still doesn't support 1080p video. But it works! On the other hand xperia T has full camera I think and cm10.1 is being worked on.
Bottom line you won't get it asap but you'll get it! Cause here is the thing Sony supports developers and stuff but mostly people go out get a Samsung or htc. Maybe that's why development is a bit slow paced.
If I were you I'd wait a month maybe? Just to see how things go over here in the development forum.
Keep visiting xperiablog.com (everything related to xperias)
And also http://freexperiaproject.com
You'll get an idea of how it's going.
Or you could get it play with the stock Sony rom! Till development kicks in Ps you'll fall in love with the media apps I'm telling you!!
http://forum.xda-developers.com/showthread.php?t=2099499 (here's the rom I'm running right now)
Sent from my Xperia S 4.2.1 using xda premium

AW: [Q] CyanogenMod on the z?
For you to know.
We work together on the CM trees for Sonydevices with codeworkx. There is no difference between FXP releases and CM releases except the buildserver and the more updated FXP releases, because wr dont push our changes everytime directly to git.
So no difference between codeworkx work and FXP work. We all on the same ship and work TOGETHER on the stuff. Sometimes more sometimes less, because anyone can have private problems or just no time for the hobby.
Dont worry about CM support. We will support any WORLD phone from Sony in CM asap.
Regards

Bin4ry said:
......
Dont worry about CM support. We will support any WORLD phone from Sony in CM asap.
Regards
Click to expand...
Click to collapse
Bin4ry, perhaps you can share some thoughts on cm on this device: Proprietary camera sensor.., battery workings, bootloader and customization, what to expect..?
Support is one thing, working rom is another. Are there any major issues to be expected, or do you reckon this will be smooth sailing? Also, how are the other sony/xperia devices running with cm now? Any big issues?
Thanks mate

I'm sure that CM will run on Z pretty much the same as it runs on nexus 4 . Tell you why . The main point is that they use the same SoC , next, quallcom's documentation is open source because Q has a developer friendly policy :thumbup:
Though some hardships might be faced when dealing with telephone part and camera which will obviously need some time to get fully working. However considering the coding level of CM developers I beleive that thet will put things on right places in a couple of builds .
Sent from my GT-I9300 using xda premium

-A-P-M- said:
Cyanogen launched M builds, which are most stable builds and a few phones launched them. Do you know what is reason, why M builds aren't available on any Sony phone yet (for example Xperia T) ? I thought M builds will be available on phones, which are easier to develop - for example, Nexus, US SGS3, latest Sony phones etc. Thanx
Click to expand...
Click to collapse
I covered this a few weeks ago on Google+, but mainly:
A decision was made to "pull an aries" with CM10.1. That means rebasing as much as possible onto the Mako kernel base, just like the Galaxy S (aries) family device maintainers rebased onto the Nexus S kernel base.
The bad: In the short run, when the effort is underway, the device will appear to be behind others.
The good: Once the effort is complete, it should be MUCH easier to keep the device up to date. See the original Galaxy S (aries) family of devices. You know, "the device that just won't die".
There was a pretty big influx of new developers to the platform a month ago, and some of us are still getting up to speed and learning things. For example, I've been focusing on what could best be described as "polishing" on CM10... Taking those little minor annoyances and squashing them. I'll transition over to 10.1 when I'm done. It's kind of nice that I can actually do something like this... Instead of fighting generic platform brokenness all over, I'm working on polishing up a few very minor annoyances. Seriously, my list of things to work on is "broken scaling of anamorphic videos over HDMI"... That's a lot better than "HDMI no worky" on Samsung Exynos devices.
Bin4ry said:
For you to know.
We work together on the CM trees for Sonydevices with codeworkx. There is no difference between FXP releases and CM releases except the buildserver and the more updated FXP releases, because wr dont push our changes everytime directly to git.
So no difference between codeworkx work and FXP work. We all on the same ship and work TOGETHER on the stuff. Sometimes more sometimes less, because anyone can have private problems or just no time for the hobby.
Dont worry about CM support. We will support any WORLD phone from Sony in CM asap.
Regards
Click to expand...
Click to collapse
As I understand it, the FXP builds will sometimes contain things that have yet to be merged into the main CM baseline via Gerrit.
For those coming from Samsung devices that codeworkx or I or any of the other CM people have worked on - Think of it as the difference between nightlies and the occasional experimental "test build" from maintainers. With the main difference being that FXP builds are always built each week whether or not there might actually be a difference.
(Correct me if I'm wrong here please.)

Entropy512 said:
You never know until release what the exact problems with a device are going to be.
That said, given how Sony is diverging less and less from reference sources for various platforms with each generation and the fact that it has the exact same SoC as the Nexus 4 - it's looking VERY promising.
Click to expand...
Click to collapse
Exactly, with key lime pie coming up, all we can do is wait

beeboss said:
I'm sure that CM will run on Z pretty much the same as it runs on nexus 4 . Tell you why . The main point is that they use the same SoC , next, quallcom's documentation is open source because Q has a developer friendly policy :thumbup:
Though some hardships might be faced when dealing with telephone part and camera which will obviously need some time to get fully working. However considering the coding level of CM developers I beleive that thet will put things on right places in a couple of builds .
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I'm also absolutely sure it will be smooth as nexus 4

after 3 weeks
We have everything working,... according to changelog...backlight is ok now, even the FMRadio is working now...
So Can we expect made working the last thing - CAMERA ?:victory::good:
PS: i know this is "headshot" question...but i would like to know whether there is some problem and there will be NO camera...or if i just should wait for some weeks ?

[Q] Ubuntu Touch for Galaxy S4 Active (i9295)

Hi all.
Anybody knows if Ubuntu Touch for Galaxy S 4 Active is being made?
Can we use the standard galaxy S4 build, if they manage to get it working on their system?
It is basically the same (same Processor, sound device, etc.), except for the camera.
I am willing to give 10 USD to the person who creates the first working beta
(I know its not much, but i am a student, so i dont have much money right now.. )
All the best,
Toby

Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM

TobiasFP said:
Hi all.
Anybody knows if Ubuntu Touch for Galaxy S 4 Active is being made?
Can we use the standard galaxy S4 build, if they manage to get it working on their system?
It is basically the same (same Processor, sound device, etc.), except for the camera.
I am willing to give 10 USD to the person who creates the first working beta
(I know its not much, but i am a student, so i dont have much money right now.. )
All the best,
Toby
Click to expand...
Click to collapse
It also has a different screen amongst other things, meaning it needs a different kernel - different drivers. I wouldn't hold my breath on ANY more roms coming to the i9295. It simply didn't gain enough traction!

Cederic said:
It also has a different screen amongst other things, meaning it needs a different kernel - different drivers. I wouldn't hold my breath on ANY more roms coming to the i9295. It simply didn't gain enough traction!
Click to expand...
Click to collapse
Thanks for the pick me up
But shouldnt all that needs changing be the blobs for the CM build?
Since Ubuntu touch relies on CyanogenMod to work, and since we have a pretty stable CM rom going, couldnt we just use the blobs from the i9505 build with minor adjustments to get going?
or have i misunderstood the build process?

TobiasFP said:
Thanks for the pick me up
Click to expand...
Click to collapse
Heh, yes I'm a bit bitter. I'm planning to sell my active and get a nexus 5 instead thanks to the lack of developments, so I can't help but rub it in a bit on the way out. While there's been some upswing lately for the i537 thanks to safestrap, none of that translates to the i9295.
TobiasFP said:
But shouldnt all that needs changing be the blobs for the CM build?
Since Ubuntu touch relies on CyanogenMod to work, and since we have a pretty stable CM rom going, couldnt we just use the blobs from the i9505 build with minor adjustments to get going?
or have i misunderstood the build process?
Click to expand...
Click to collapse
Well, I'm using the CM build from this forum as my daily user, and "pretty stable" is a good description. Not stable enough really, and the most pressing issue is the lack of official CM support to make it so. I don't know how easy it is, but quite obviously there's more to it than you'd think or it would have happened already. Samsung is (apparently) notorious for not making it easy in any way, so... I wouldn't hold out hope. Not since this device turned out to be so slowly adopted that there just doesn't seem to be enough developers interested.
Perhaps this will change over the year to come, but I doubt it, and I for one don't have time for it.

Cederic said:
Heh, yes I'm a bit bitter. I'm planning to sell my active and get a nexus 5 instead thanks to the lack of developments, so I can't help but rub it in a bit on the way out. While there's been some upswing lately for the i537 thanks to safestrap, none of that translates to the i9295.
Well, I'm using the CM build from this forum as my daily user, and "pretty stable" is a good description. Not stable enough really, and the most pressing issue is the lack of official CM support to make it so. I don't know how easy it is, but quite obviously there's more to it than you'd think or it would have happened already. Samsung is (apparently) notorious for not making it easy in any way, so... I wouldn't hold out hope. Not since this device turned out to be so slowly adopted that there just doesn't seem to be enough developers interested.
Perhaps this will change over the year to come, but I doubt it, and I for one don't have time for it.
Click to expand...
Click to collapse
No, of course it is not easy, but what i was saying is, that when the i9505 gets going, which i believe it will, since they have been working on it for about a month now, i believe it could "easily" be converted to the i9295.
The i9505 is a lot more similar to the i9295 than the i537, they both share the same Krait processor, and the screen is already fully supported in the current CM build of the i9295, so i dont see that as a problem.
Of course it will take some time, but i believe (okay, a better word would be "hope") that when the i9505 has Ubuntu Touch ready, it will not take long for us.
See the development status here:
http://forum.xda-developers.com/showthread.php?t=2274387&page=4

[Q] What is the situation of CyanogenMod?

CyanogenMod recently pushed out stables for CM10.2 on a select range of devices announcing that, with this, their efforts would be solely focused towards the CM11 code branches. However, they also announced that any devices which received that RC1 of CM10.2 would too continue into CM11.
My question, considering we are still unfortunate enough to be on somewhat unstable nightlies (the notification sound delay, UI issues, application crashes) is, what will be the future of CyanogenMod on the O4x? Will we even make it to stable CM10.2?
Hopefully we can! This is such a brilliant device as you all know well, and the hardware restrictions of KitKat are supposed to be lowered anyway
For clarification, this is not a complaint, the work of the CyanogenMod Team is always much appreciated. I, and so many of you, have donated and thanked them and tested their software for them. This is merely to gain an understanding of where our device is headed so as to aid everybody here in the decision of whether to stick with the device or, should worse come to worse.... look for another :-/

csfrank271 said:
CyanogenMod recently pushed out stables for CM10.2 on a select range of devices announcing that, with this, their efforts would be solely focused towards the CM11 code branches. However, they also announced that any devices which received that RC1 of CM10.2 would too continue into CM11.
My question, considering we are still unfortunate enough to be on somewhat unstable nightlies (the notification sound delay, UI issues, application crashes) is, what will be the future of CyanogenMod on the O4x? Will we even make it to stable CM10.2?
Hopefully we can! This is such a brilliant device as you all know well, and the hardware restrictions of KitKat are supposed to be lowered anyway
For clarification, this is not a complaint, the work of the CyanogenMod Team is always much appreciated. I, and so many of you, have donated and thanked them and tested their software for them. This is merely to gain an understanding of where our device is headed so as to aid everybody here in the decision of whether to stick with the device or, should worse come to worse.... look for another :-/
Click to expand...
Click to collapse
probably no official CM11 for us, or 10.2 stable/rc, atleast in forseeable future. thankfully, we have some very skilled devs working on unofficial version of CM, & Vanir&Omni.

Flying_Bear said:
probably no official CM11 for us, or 10.2 stable/rc, atleast in forseeable future. thankfully, we have some very skilled devs working on unofficial version of CM, & Vanir&Omni.
Click to expand...
Click to collapse
Thank you, I was just wondering about the state of the official ROMs, it seems like the P880 has been forgotten about by CM
But, as you say, we are very lucky to have these fantastic devs building even better custom ROMs

Flying_Bear said:
probably no official CM11 for us, or 10.2 stable/rc, atleast in forseeable future. thankfully, we have some very skilled devs working on unofficial version of CM, & Vanir&Omni.
Click to expand...
Click to collapse
If everything is working right we should be able to submit it to cyanogenmod to get our nightlies back, but im not 100% sure

JoinTheRealms said:
If everything is working right we should be able to submit it to cyanogenmod to get our nightlies back, but im not 100% sure
Click to expand...
Click to collapse
Hopefully we can have the issues fixed
Can't wait to see the community development though, the new Android RunTime looks very fascinating :3

why dont u enter cyanogenmod and see with your eyes ? anyway. of course we dont see any support. its a miracle that we had that much support too. who will support a phone which doesnt even has the support of the official company ? LG only had 4.0.3 and 4.1.2 and thats all. isnt it already a miracle that we have 4.3.1 ? and we have also so many good developers that work for 4.4 ?

I don't understand why people want 4.4 so bad when it's one of the worst upgrades from Google i have ever seen. They had to launch 4.4.1 updates right away. You want a better software I agree thats needed but 4.4 isn't a solution.
Sent from my OptimusX4HD using xda app-developers app

Zhus06 said:
I don't understand why people want 4.4 so bad when it's one of the worst upgrades from Google i have ever seen. They had to launch 4.4.1 updates right away. You want a better software I agree thats needed but 4.4 isn't a solution.
Sent from my OptimusX4HD using xda app-developers app
Click to expand...
Click to collapse
Everyone wants KitKat because... Well, because it's new! Why not? I believe that pushing one's expectations beyond what is already achieved represents a strong impulse to improvement. Experimenting, trying new solutions, feeling the awesomeness of something that did not exist before is a powerful spring to the change, the change in itself is something that animates the developers and makes them work with no reward as if this was their job.
It has happened with all Android versions, and always there had been someone who felt amazed and wondered why should we need a new version.
kK can be (and probably is, but who am I to judge) one of the worst Android versions, but I am happy to see people trying to overcome all the problems related with making it work on a relatively old device, and I am happy if by testing what is being developed, and by giving my opinion I can be of some help to somebody.
Want to call it a game? Why not! Want to consider people like me as grown up kids that need something to play with? Well, yes, I am, and will always cheer a new Android version working on one of my devices with grateful heart.

Ricardo Cerqueira is no longer the maintainer of our device?
there is no one who will replace him?

It should be possible to join the CM team, if the 4.4 is running.
The tegra3 problems will hopefully not be a trap for it.
If there is a maintainer who can update CM once, there will be no real reason not to get official support.

Good news everybody!
On the CyanogenMod website, the P880 has been listed officially as one the devices to receive support further than the CM10.2 nightlies, which will be a win-win for everyone

Bye Bye CM !

DarkFantasy6 said:
Bye Bye CM !
Click to expand...
Click to collapse
Why do you say that? :-/

csfrank271 said:
On the CyanogenMod website, the P880 has been listed officially as one the devices to receive support further than the CM10.2 nightlies, which will be a win-win for everyone
Click to expand...
Click to collapse
I saw the latest list the have revealed now, this is great!!
Noticed though that they said MOST of the devices that have CM10.2 builds will move into CM11 nightly during the next weeks.. "Most" hopefully means the P880 as well!

faabak said:
I saw the latest list the have revealed now, this is great!!
Noticed though that they said MOST of the devices that have CM10.2 builds will move into CM11 nightly during the next weeks.. "Most" hopefully means the P880 as well!
Click to expand...
Click to collapse
Yes, hopefully!
But hey, a stable CM10.2 would even be fantastic, the community devs would appreciate it surely

We never got the m1 and stable so i hardly belive it that we get cm11. And without a good 3.4 kernel source from lg we wont feeo many adventafes of 4.4. but the awesome awesome optic would be nice Maybe im going to buy a Nexus 5. Im so frustrated of my lg optimus 2x and 4x. ONE update -.-

Developer Support

Just wondering what other developers have decided or shown interest in grabbing a OnePlus 3. I am thinking of getting one, but the cost is a bit steep to just support a device that I may not even use as a daily device. If there is a small amount of developers, I will be more likely to get one because I believe that users deserve to use their phone how they want, not how the OEM wants them to. This is more or less a roll call to see who will be supporting the device from a dev standpoint.

read something about
- Grarak already release unofficial CM13
- martin from Ground zero roms, finished tipsy but not having the phone yet
- paranoid android should bring out rom in next couple of days (new team)

Dinjesk said:
read something about
- Grarak already release unofficial CM13
- martin from Ground zero roms, finished tipsy but not having the phone yet
- paranoid android should bring out rom in next couple of days (new team)
Click to expand...
Click to collapse
Anyone kernel side?

DespairFactor said:
Anyone kernel side?
Click to expand...
Click to collapse
untill so far i have only seen or heard about @haikalizz
doubting @Boeffla will consider as he is taking kernel development a notch down.

Dinjesk said:
untill so far i have only seen or heard about @haikalizz
doubting @Boeffla will consider as he is taking kernel development a notch down.
Click to expand...
Click to collapse
I am considering it, I have plans to bring kexec hardboot to the device if I get it

DespairFactor said:
I am considering it, I have plans to bring kexec hardboot to the device if I get it
Click to expand...
Click to collapse
Yes, please consider - early adopters will lure more and more devs for sure.
And OP is dev-friendly too (according to the OP - you won't void your warranty by flashing custom ROMs/Kernels).
I was fully surprised to see the first unofficial CM13 ROM from Grarak one hour after the announcement yesterday

_PrEzi_ said:
Yes, please consider - early adopters will lure more and more devs for sure.
And OP is dev-friendly too (according to the OP - you won't void your warranty by flashing custom ROMs/Kernels).
I was fully surprised to see the first unofficial CM13 ROM from Grarak one hour after the announcement yesterday
Click to expand...
Click to collapse
My problem is the price point still for a device that I I'll likely be supporting to ensure users get what they want rather than using it as a daily driver for a while. I support several Nexus devices and have done a bit on each OnePlus device in the past. I just want it to be a feasible purchase considering how large my support roster is already.

DespairFactor said:
My problem is the price point still for a device that I I'll likely be supporting to ensure users get what they want rather than using it as a daily driver for a while. I support several Nexus devices and have done a bit on each OnePlus device in the past. I just want it to be a feasible purchase considering how large my support roster is already.
Click to expand...
Click to collapse
I can perfectly understand that. You - like me - do like to do things either perfectly or at least v. good or better leave them be if they are only 'ok'.
Nevertheless - please do consider. I am not promising anything but my guts tell me OP3 will have a larger userbase than the OP2.
And again - no promises - but I like beer and also like to send 'virtual beer/pizzas' to the devs I feel are putting big efforts to keep the users happy. Probably other humble users too :highfive:

Would be killer to have you onboard.

Yes come on board. I like your kernel.
Gesendet von meinem Nexus 6P mit Tapatalk

DespairFactor said:
I am considering it, I have plans to bring kexec hardboot to the device if I get it
Click to expand...
Click to collapse
Do you intend to bring Ubermallow/Uberstock to OP3 as well?If your answer is yes, I'm ordering this phone right away.
Sent from my Nexus 5X using XDA-Developers mobile app

To be honest, I'm pretty sure that this device will attract a lot of devs, both kernel and rom wise. So while I'd love to have the dark side on board, you shouldn't stress your budget when you're not planning to use the phone. Just my $0.02.

gururoop said:
Do you intend to bring Ubermallow/Uberstock to OP3 as well?If your answer is yes, I'm ordering this phone right away.
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
derdjango said:
To be honest, I'm pretty sure that this device will attract a lot of devs, both kernel and rom wise. So while I'd love to have the dark side on board, you shouldn't stress your budget when you're not planning to use the phone. Just my $0.02.
Click to expand...
Click to collapse
inzaghi75 said:
Yes come on board. I like your kernel.
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
For right now I will blind build a kernel and try to get kexec working. If I somehow get the budget to grab one, I will. I hear there is a BrokenOS coming, but do not ask anyone about it, just wait for a release. I will not bring UBER ROMs to this device because we do not run CAF based sources.

OFFICIAL BeanStalk ROM and Temasek is comming on Saturday by me
Regards,
Taker

Taker18 said:
OFFICIAL BeanStalk ROM and Temasek is comming on Saturday by me
Regards,
Taker
Click to expand...
Click to collapse
Just a friendly request, please keep on One rom and maintain it well. I am sure that many devs will come for OP3 because of its open nature and having a unofficial port of their rom might discourage them. So, please, focus on quality rather than quantity. I don't doubt that you can maintain 2 roms. But, as you are more with Beanstalk, please continue with it. You can go for maintaining more roms one source for custom roms gets stable and no dev from a particular rom comes. Don't take it wrong but just a friendly request.
Thanks.
And BTW, better if you maintain only for the devices you have. And if you are maintaining for a device you don't even have, maintaining more than 1 rom for it becomes too weird and not good for the device users as you won't be able to contribute much to device specific stuff that way. So, if you don't own device, for now, it will be better if you just maintain one rom at max so that some developer who owns device can maintain and he doesn't get discouraged (happened with op2 and happens with opx too)
Sent from my OnePlus2 using XDA Labs

Naman Bhalla said:
Just a friendly request, please keep on One rom and maintain it well. I am sure that many devs will come for OP3 because of its open nature and having a unofficial port of their rom might discourage them. So, please, focus on quality rather than quantity. I don't doubt that you can maintain 2 roms. But, as you are more with Beanstalk, please continue with it. You can go for maintaining more roms one source for custom roms gets stable and no dev from a particular rom comes. Don't take it wrong but just a friendly request.
Thanks.
And BTW, better if you maintain only for the devices you have. And if you are maintaining for a device you don't even have, maintaining more than 1 rom for it becomes too weird and not good for the device users as you won't be able to contribute much to device specific stuff that way. So, if you don't own device, for now, it will be better if you just maintain one rom at max so that some developer who owns device can maintain and he doesn't get discouraged (happened with op2 and happens with opx too)
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
I agree, it is hard to maintain several projects at once for one device, let alone a few. IIRC, a lot of you come across from other OP devices too, not sure if you are dropping support on previous devices.

Well, I'm too working on a kernel for this phone (albeit don't have device)
Sent from my Moto X using Tapatalk

##W4TCH0UT## said:
Well, I'm too working on a kernel for this phone (albeit don't have device)
Click to expand...
Click to collapse
Good. Though I think for better support to users, one, especially a kernel developer, must have the device. Users can't always get the best of bug reports and it becomes a lot hectic to support devices (like it happened on OP2 ) Infact, it doesn't give a good pressing on a developer's image to be honest. Take your decision but believe me, it will be better if you get the device and maintain.
Thanks.
Best Regards
Sent from my OnePlus2 using XDA Labs

Naman Bhalla said:
Good. Though I think for better support to users, one, especially a kernel developer, must have the device. Users can't always get the best of bug reports and it becomes a lot hectic to support devices (like it happened on OP2 ) Infact, it doesn't give a good pressing on a developer's image to be honest. Take your decision but believe me, it will be better if you get the device and maintain.
Thanks.
Best Regards
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
OnePlus 2, was a bad device, I actually had it, they just did a poor job, but either way, if you don't want my support that's fine as well.

DespairFactor said:
OnePlus 2, was a bad device, I actually had it, they just did a poor job, but either way, if you don't want my support that's fine as well.
Click to expand...
Click to collapse
I think you know me. Remember me from one group we created ? I think of you can get a device, do support it. Infact, in one way, people support of you support them. So, get a device, support the device and a lot chances are that people will support you and you might be able to overcome all expenditures on the device. And believe me, many devs told me this too. And I know your kernel from 6P. Will be great if you can support, and prolly you *might* have a surprise too (I am not saying anything, but, well) . We do need your support, but it will be best if you can support when you have a device too. It will generate people's trust upon you and also you won't need to get with wrong bug reports.
Sent from my OnePlus2 using XDA Labs