I'm very surprised that Samsung have started to officially push out Lollipop to the S5 and OPO has not yet.
Considering the Touchwiz overlay which we all know is heavy and would require loads of work, where as CM12 doesn't have much of a change over stock Lollipop.
I've been using the CM12 nightlies for a few weeks now and they can be used as a daily driver for me, but there are still little bugs that need to be ironed out.
How has Samsung pipped CM to the post? I'm not sure if CM has just been slow or Samsung has picked up it's act.
Patience mate it will come in due course. CM usually take a while to release stable builds. Other devices are still waiting it will come in due course.
shure2 said:
I'm very surprised that Samsung have started to officially push out Lollipop to the S5 and OPO has not yet.
Considering the Touchwiz overlay which we all know is heavy and would require loads of work, where as CM12 doesn't have much of a change over stock Lollipop.
I've been using the CM12 nightlies for a few weeks now and they can be used as a daily driver for me, but there are still little bugs that need to be ironed out.
How has Samsung pipped CM to the post? I'm not sure if CM has just been slow or Samsung has picked up it's act.
Click to expand...
Click to collapse
It's not so surprising when u think about the number of developers/programmers in Samsung as a multi-billion company compared to cyanogen. +I think there may have been some deals between Google and Samsung, LG etc so they get the source code sooner before official release. But that's only what think, no evidence backing up this statement.
shure2 said:
I'm very surprised that Samsung have started to officially push out Lollipop to the S5 and OPO has not yet.
Considering the Touchwiz overlay which we all know is heavy and would require loads of work, where as CM12 doesn't have much of a change over stock Lollipop.
I've been using the CM12 nightlies for a few weeks now and they can be used as a daily driver for me, but there are still little bugs that need to be ironed out.
How has Samsung pipped CM to the post? I'm not sure if CM has just been slow or Samsung has picked up it's act.
Click to expand...
Click to collapse
How has Samsung beat CM to the chase? Money. Samsung are rolling in cash and they have a ridiculous amount of it to throw at developing the OS for their devices. Don't forget CM is a tiny (miniscule) company. Plus, the major OEM's get early release access to Android releases. You'll get your Lollipop, just be patient.
Transmitted via Bacon
shure2 said:
I'm very surprised that Samsung have started to officially push out Lollipop to the S5 and OPO has not yet.
Considering the Touchwiz overlay which we all know is heavy and would require loads of work, where as CM12 doesn't have much of a change over stock Lollipop.
I've been using the CM12 nightlies for a few weeks now and they can be used as a daily driver for me, but there are still little bugs that need to be ironed out.
How has Samsung pipped CM to the post? I'm not sure if CM has just been slow or Samsung has picked up it's act.
Click to expand...
Click to collapse
Samsung probably got off there ass, they have always received new code from google way in advance of it being released to the public.
When it goes public that's when cm gets it.
Please understand all the variables before doing a shame post
I believe they got the code sooner
Sent from my A0001 using XDA Free mobile app
Now shouldn't the One plus and CM get it as soon as other OEMs get it? I mean CM is no more bunch of dev doing this part time. I am still not convinced.
Sent from my TouchPad using XDA Free mobile app
viny2cool said:
Now shouldn't the One plus and CM get it as soon as other OEMs get it? I mean CM is no more bunch of dev doing this part time. I am still not convinced.
Sent from my TouchPad using XDA Free mobile app
Click to expand...
Click to collapse
Even if they did get it at the same time, CM would still be behind. It's all about money. Think about it, HTC, Samsung, Sony, LG, they all have squillions of dollars and countless employees to sink into their devices. CM? Nope. CM are a tiny (and new) company, with just a fraction of the money and manpower that the big players have. I really don't understand why everyone is so confused about this.
Transmitted via Bacon
timmaaa said:
I really don't understand why everyone is so confused about this.
Click to expand...
Click to collapse
Because most consumers have no clue what's going on behind the scenes of these businesses, and ironically this leads them to think they know enough to legitimately criticize them. In America we call them arm-chair quarterbacks. They watch the game on TV the day after it's played completely removed the circumstances of the game, yet somehow they think they know everything and the guy on the field is stupid even though they've never even played the game.
timmaaa said:
Even if they did get it at the same time, CM would still be behind. It's all about money. Think about it, HTC, Samsung, Sony, LG, they all have squillions of dollars and countless employees to sink into their devices. CM? Nope. CM are a tiny (and new) company, with just a fraction of the money and manpower that the big players have. I really don't understand why everyone is so confused about this.
Transmitted via Bacon
Click to expand...
Click to collapse
I understand that but the only thing which is kind of icky to me is that CM being the primary OS provider for this phone, should provide the first stable versions for our phone. May be I am not seeing it correctly but looks like everyone gets CM stable releases at the same time. I just got this phone a month so may be I am missing something.
Not complaining or anything, just trying to understand the process.
Sent from my A0001 using XDA Free mobile app
---------- Post added at 09:52 AM ---------- Previous post was at 09:46 AM ----------
CafeKampuchia said:
Because most consumers have no clue what's going on behind the scenes of these businesses, and ironically this leads them to think they know enough to legitimately criticize them. In America we call them arm-chair quarterbacks. They watch the game on TV the day after it's played completely removed the circumstances of the game, yet somehow they think they know everything and the guy on the field is stupid even though they've never even played the game.
Click to expand...
Click to collapse
Not trying to start an argument here. But you do understand that the american football is played for the consumer's money (TV rights, stadium fees, ads etc). So if those arm chair QBs are paying to watch the game, they have a right to complain. If the teams or the players have a problem with it then they can go and play in private where no one will ever say a word.
It is similar situation here. The oneplus strategy was to attract consumers by using CM' OS. So I and others have a right to ask questions. You cannot criticize them and call them names. Go take out your frustration on someone else. You don't like this thread? Don't read it and don't comment on it.
Sent from my A0001 using XDA Free mobile app
viny2cool said:
It is similar situation here.
Click to expand...
Click to collapse
You missed the point. Paying to watch something makes nobody an expert or even knowledgeable about the matter. One is free to complain about the phone one bought, but that gives no understanding about what's going on in the offices of OnePlus or CyanogenMod, or the processes involved in the two of them outing a ROM compared to Samsung.
CafeKampuchia said:
You missed the point. Paying to watch something makes nobody an expert or even knowledgeable about the matter. One is free to complain about the phone one bought, but that gives no understanding about what's going on in the offices of OnePlus or CyanogenMod, or the processes involved in the two of them outing a ROM compared to Samsung.
Click to expand...
Click to collapse
Exactly and that is what being discuss here. Some people like me are not sure about the things which goes in CM/One Plus office and we are confused on why CM can't get it out sooner then other big OEMs. Small company or not, they are getting paid.
No one goes complaining directly to the players or the teams (or companies in this case). America is a free country and people like you are trying to suppress the freedom of speech. I am going to sit here and ask million questions and you cannot stop me. Exactly like I can't stop you from replying to my messages .
If you want to contribute to answering then the question, then please do. If not then please stop creating arguments here.
Cyanogenmod have releases for a boat load of different phones with different hardware, they get the lollipop source as it's released to the public and they're are a very small company. Unlike Samsung, HTC, LG and Sony which have many developers and early access to the android source code so they can develop the next android version with their respective skin on top. If you want to complain about cyanogenmod, feel free to do so just know they're a small niche operating system compared to the big OEM's. But you can take a look at cyanogenmod's Gerrit and see they're working hard on the CM12 branch, that's something you can't see with the big OEM's
Sent from my A0001 using Tapatalk
viny2cool said:
Exactly and that is what being discuss here. Some people like me are not sure about the things which goes in CM/One Plus office and we are confused on why CM can't get it out sooner then other big OEMs. Small company or not, they are getting paid.
No one goes complaining directly to the players or the teams (or companies in this case). America is a free country and people like you are trying to suppress the freedom of speech. I am going to sit here and ask million questions and you cannot stop me. Exactly like I can't stop you from replying to my messages .
If you want to contribute to answering then the question, then please do. If not then please stop creating arguments here.
Click to expand...
Click to collapse
So if I don't say what you want to hear, I just stop posting... I get it now. I guess I misunderstood what freedom of speech was before. :silly:
No point.
Why care about a Galaxy Sx getting lollipop before? It sucks anyway...:silly:
shure2 said:
I'm very surprised that Samsung have started to officially push out Lollipop to the S5 and OPO has not yet.
Considering the Touchwiz overlay which we all know is heavy and would require loads of work, where as CM12 doesn't have much of a change over stock Lollipop.
I've been using the CM12 nightlies for a few weeks now and they can be used as a daily driver for me, but there are still little bugs that need to be ironed out.
How has Samsung pipped CM to the post? I'm not sure if CM has just been slow or Samsung has picked up it's act.
Click to expand...
Click to collapse
You forgot something, it's only officially available to the S5 in... Poland. Otherwise you still would have to root/ROM the Lollipop update onto the S5 no differently than a CM12 nightly and then it will only work on the international version. For the vast majority of S5 users they won't see an official OTA update for months, well after CM has delivered Lollipop to the OPO. Once it's made available to the US carriers expect massive delays again so they can 'certify' the ROM before pushing it out. If you really think that the extremely limited, country specific, release 'beat' CM to Lollipop you either have never played in the Android world or you have massively misplaced expectations.
BrianDigital said:
Samsung probably got off there ass, they have always received new code from google way in advance of it being released to the public.
When it goes public that's when cm gets it.
Please understand all the variables before doing a shame post
Click to expand...
Click to collapse
Could you please provide a source to show Samsung get the code early?
rcook55 said:
You forgot something, it's only officially available to the S5 in... Poland. Otherwise you still would have to root/ROM the Lollipop update onto the S5 no differently than a CM12 nightly and then it will only work on the international version. For the vast majority of S5 users they won't see an official OTA update for months, well after CM has delivered Lollipop to the OPO. Once it's made available to the US carriers expect massive delays again so they can 'certify' the ROM before pushing it out. If you really think that the extremely limited, country specific, release 'beat' CM to Lollipop you either have never played in the Android world or you have massively misplaced expectations.
Click to expand...
Click to collapse
So you can root and anyone with a European S5 can get a genuine released Lollipop. At the moment we are flashing a pre nightly version of an aftermarket ROM, not even a nightly, let alone anywhere close to an official CM12S.
Sure Samsung have money and they should need it to adapt TouchWiz, but this is basically a stock Lollipop we are waiting for.
I've yet to see anyone quote a reliable source about Samsung getting the code early, but if the do then that would obviously be a good reason for CM appearing slow.
CM are slow look into previous CM releases go back to when Kit Kat was released, or Jelly Bean etc. CM support a number of devices each with different drivers and such CM access the code once it's released to public as mentioned on many posts here. Now that's CM. If OPO wanted to I assume they could release an AOSP version of Lollipop if they wish to like how they did with Kit Kat. CM won't rush and roll out a semi working CM12S for the sake of it we haven't even got official nightlies yet. We are still within the 90 day promise so there's plenty of time left still.
shure2 said:
So you can root and anyone with a European S5 can get a genuine released Lollipop. At the moment we are flashing a pre nightly version of an aftermarket ROM, not even a nightly, let alone anywhere close to an official CM12S.
Sure Samsung have money and they should need it to adapt TouchWiz, but this is basically a stock Lollipop we are waiting for.
I've yet to see anyone quote a reliable source about Samsung getting the code early, but if the do then that would obviously be a good reason for CM appearing slow.
Click to expand...
Click to collapse
It doesn't matter even an iota that it's stock Android that we're waiting for. That doesn't make it any less work to get it working for a device. You should look into exactly what is involved in getting a new version of Android running on any non-Nexus device, because clearly you're under the false impression that it's a sinch to do, which it most definitely is not. This is all about money and resources.
Related
(1)
I think it is insulting how Samsung released the Froyo update. This was not a mass update... this was a "lets shut the people complaining up update!"
Updating through Kies ALWAYS = people posting about problems/issues.
Why is it they could not do an OTA? I personally assume it's because it was not ready (hence the KA7 leak) and THAT will be an OTA for the masses to froyo (or an update to those who used Kies). This is my assumption.
But shame on Samsung/T-Mobile for this...
I would STRONGLY urge new people to NOT update to froyo via kies. I WOULD encourage rooting your phone and flashing the new custom roms that are based off the newest builds (even newer than KA6 which was the "official update").
(2)
I think a thread dedicated for the new ROMs in the Q&A section would be awesome. Consider it an "ask a dumb question and expect a quick answer" thread. The less crap/clutter from the development section the better.
I imagine hardly any posts in the development section are of benefit to the developer.
I feel the Nero V4 sticky is a good example. Though I feel a sticky is a bit much.
(3)
Anyone want to create a thread (or show me one) with all of the stock system apps attached? It would ne nice for those times when someone is asking for them....
(4)
Does anyone have the skills to make the dropdown "mute" button also mute Media. I hate that currently it will mute everything but media... as it inevitably always leads to me making noise when I think I am muted.
I now use Widgetsoid to mute my phone completely.
Thanks!
I don't care how they released froyo, as long as they also release source code soon since it was an "official" release.
Sent from my SGH-T959 using XDA App
dcpetterson said:
I don't care how they released froyo, as long as they also release source code soon since it was an "official" release.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
They have 60 days. Should not take that long. I just question why it was not an ota. Consider me skeptical of Samsung.
Want source? Request it: @SamsungMobileUS should work.
I agree that this was to shut people up, however, as a person who hasn't flashed a rom yet, I commend them for it. I really didn't know what I was missing, and if KA6 is laggy, I can't wait to see what isn't laggy. I'd like to root my phone next, but I have no idea if I'm hardware locked, so I'm inspired to do more reading.
Mini Kies is not difficult to use. People just don't read.
ETA: I agree that there will eventually be an OTA for fixes to KA6 and for people who did not even know about this.
mrsbelpit said:
I agree that this was to shut people up, however, as a person who hasn't flashed a rom yet, I commend them for it. I really didn't know what I was missing, and if KA6 is laggy, I can't wait to see what isn't laggy. I'd like to root my phone next, but I have no idea if I'm hardware locked, so I'm inspired to do more reading.
Mini Kies is not difficult to use. People just don't read.
ETA: I agree that there will eventually be an OTA for fixes to KA6 and for people who did not even know about this.
Click to expand...
Click to collapse
Check and make sure that your phone is hardware locked now as I know that one of the ROMs took care of this issue.
Sent from my SGH-T959 using XDA App
Isn't it that updating through kies is faster than ota? People wouldn't have to wait, unless you're a mac user. The JI6 took forever for them to send it. I waited like 2 weeks then i just flashed it through odin because i was really tired of waiting.
Sent from my SGH-T959 using XDA App
Personally, I do believe that KA6 was suddenly delivered via Kies to shut us all up.
However, I don't really mind how updates are released. They don't have to be OTA. As long as Samsung releases timely updates, even if it is via Kies, then I will be a happy customer. (Oh and they still need to fix the hardware gps flaw)
If they release Gingerbread via kies in a timely manner, I will even somewhat forgive them, but I still will not buy another Samsung made product again for a very long time if ever.
im glad atleast samsung decided to give us froyo... i mean now we can get a little bit of work on our roms since we have a official now.
but i think that "official" rom was made in 2 days, because if you notice, its laggy as hell, and the only difference is theres wifi calling and a few other apps, thats IT.
s15274n said:
They have 60 days. Should not take that long. I just question why it was not an ota. Consider me skeptical of Samsung.
Want source? Request it: @SamsungMobileUS should work.
Click to expand...
Click to collapse
I have the same opinion. I believe this was just a "shut them up" maneuver and the easier softer way for them to do it. Also from what I have read in the threads there seems to be a number of people with problems from the Keis fiasco.
xriderx66 said:
im glad atleast samsung decided to give us froyo... i mean now we can get a little bit of work on our roms since we have a official now.
but i think that "official" rom was made in 2 days, because if you notice, its laggy as hell, and the only difference is theres wifi calling and a few other apps, thats IT.
Click to expand...
Click to collapse
Well, it actually has the Dalvik Jit Compiler which somewhat improves the Hummingbird cpu performance, there is also Flash player.
SamsungVibrant said:
Well, it actually has the Dalvik Jit Compiler which somewhat improves the Hummingbird cpu performance, there is also Flash player.
Click to expand...
Click to collapse
well i guess all that lag takes away from the dalvik jit
also the flash, we've had for like months so you know,
S15274N Great Posting
I agree on your general Ideas. I really like the Idea of posting a fast Q & A
I like the Idea of Making a thread that lists all the stock apps (with apk attached etc.) for those who want that sort of thing.
And, I agree Samsung is just trying to avoid a Gun Fight with the customers. We customers Really are making it hard for Tmo and Samsung to continue their personal "*****-match"
We need to continue to Keep the Pressure on Samsung to keep them adhering to the open source licensing agreement thet agree to when installing Android.
Yeah, I was not trying to say I am upset they released froyo... but more picking on them for HOW they released it. They know 99% of Vibrant users are not even going to know it was released, and if they did, they wont bother with Kies.
Them releasing source will be huge. I hope they release it as fast as they did for the canadian fascinate once froyo was released for it. I'm still a skeptic of Samsung and expect a future release to be the next "official froyo"
s15274n said:
Yeah, I was not trying to say I am upset they released froyo... but more picking on them for HOW they released it. They know 99% of Vibrant users are not even going to know it was released, and if they did, they wont bother with Kies.
Them releasing source will be huge. I hope they release it as fast as they did for the canadian fascinate once froyo was released for it. I'm still a skeptic of Samsung and expect a future release to be the next "official froyo"
Click to expand...
Click to collapse
they'll probably release it on like the 60th day waiting till its like 11:59PM then they upload. lol.
Based off your #1 statment I can only say that this is exactly why they released the "official update". The thing is after the first rumor was released and the **** hit the fan causing multiple threads and 1,000's of post, among other things, there was a small thread and article that was covered and only happen to receive less then 50 post that stated:
The same credible source that gave the first rumor added the reason why samsung and/or tmobile haven't given the update Is because samsung is charging the carriers for OS updates. This means samsung was expecting each carrier to pay per handset sold(later to be denied by samsung).
You can have your own take on samsung or tmo, but the remainder stays the same. That is if the sites which released the rumors spoke to the same source and one rumor is true, then possibly the second Could be also. This also shows 2 other things that will forever fault the android community and the Internet alike. The mob mentality and the feeling of some type of entitlement will cloud the truth or fuel rumors and/or other things that none of use are entitled to know or understand.
One good thing that has come out of this is the fact that now samsung is responsible to release the 2.2 source.via the GPL. Going forward id say Let's try and not let this happen with the real ota, if that ever really happens... lol.
Moral of the story:
Becareful what you wish for. You might just get it... kinda.
This is the unofficial thread to find the list of developers for the Samsung Galaxy Note II.
If you are a developer and or ROM maker/cooker would like to confirm that you are going to dev on this device please send me a pm, and I will add you to the list. In past experiences these types of threads have shown to be very helpful to build dev support for a device, and also to help people decide on a device.
What, actually is the list for?
Basically its for people and devs to see all the dev support the device will have. This sometimes is the deciding factor for getting a phone. If there's huge dev support more people will come. This makes it easier for people to find information on what devs will be supporting the note 2.
To pm me and get added to the list Click Here.
Let's make this Galaxy Note II community awesome!
Confirmed Developers
1.Utacka
2.thering1975
3.DakiX
4.::indie::
5.m3dd0g
6.Crash 1976
7.g.lewarne
8.toxicthunder
9.awesomehacker
10.KashaMalaga
11.-Viperboy-
12.lennyuk
13.Dexter_nlb
14.DocRambone
15.imilka
16.f3w1n
17.kristofpetho
18.mike1986.
19.Stavr0s91i
20.wanam
21.xator91
22.Beukhof1
23.ptmr3
24.Anas M.I
25.cpu999
26.AndreiLux
27.Chainfire
28.Patrics83
29.Chenglu
30.bigbiff
Hi,
Thanks for starting this thread. I just want to ask "Do you think there be a lot of development for this phone?" Particularly for Note II, in general for future Samsung phones.
I just finished watching this video here or here and I just heard about some developers leaving Samsung altogether? Samsung locking bootloaders? Samsung getting too big for their own ego?
I currently own the Int'l N7000 and I found the development to be good for what I want. I didn't check out the i717 thread but I assume they are fair.
I'm not really experienced in rooting but I found Samsung Note to be fairly straight forward. I recently rooted an HTC Amaze 4G and the numerous steps plus the lack of info made me never to buy an HTC phone (even if I do like the HTC One X, my friend has the North American version and he said development is low there).
This is one reason why I'm holding out on the Note II until Feb 2013, maybe even Sept 2013 (in case Note 3) comes out because I want to see how the development plays out.
I know the phone just came out, but I assumed International Note development should be all hunky dory but I never know. Makes me not want to switch devices. I had an Int'l Galaxy S2 previously and development for that is great!
I hear Sony development is awesome. But then, I think I'll just go get a Nexus for ease of development (but the screen is so small!)
What do you guys think?
cincyelite22 said:
Confirmed Developers
1.Utacka
2.thering1975
3.DakiX
4.::indie::
5........
Click to expand...
Click to collapse
thanks leafsacc, I wasn't aware of this until now. I'm still not sure what's going on but I assumed there would be a way around a bootloader, as coders always find a way :highfive:
but reading the below, says it could have been verizon which was the cause of the bootloader, not samsung. so why is xdadevtv directing his video to samsung? is it because no open source was given for the s3? has it still not been released? will it be? anyone care to sum it up for some of us who aren't in the know? :>
Based on Samsung’s track record of always shipping devices with unlocked bootloaders, we can all safely deduce that Verizon is the one to blame here.
Click to expand...
Click to collapse
http://www.xda-developers.com/android/verizon-samsung-galaxy-s-iii-unlocked/
For starters cm will not support n7100 if samsung dont change their ways. atleast the current dev team in cm will not support newer samsung exynos devices. i9300/n80xx was the last. Only way to get n7100 supported is if samsung cooperate or a new dev join cm dev team.
Without cm support i cannot do my paranoidandroid from source as I do with n7000. Time will tell if some new dev join cm samsung team or samsung get their act together. Dont look good though.
Skickat från min GT-N7100 via Tapatalk 2
Utacka said:
For starters cm will not support n7100 if samsung dont change their ways. atleast the current dev team in cm will not support newer samsung exynos devices. i9300/n80xx was the last. Only way to get n7100 supported is if samsung cooperate or a new dev join cm dev team.
Without cm support i cannot do my paranoidandroid from source as I do with n7000. Time will tell if some new dev join cm samsung team or samsung get their act together. Dont look good though.
Skickat från min GT-N7100 via Tapatalk 2
Click to expand...
Click to collapse
Whoops not good news :crying: i need also sources...
Well I don't get it because it is sharing most of the hardware with S3 so the stuff should be at least ported easily.
Now I understand Samsung being a complete ass with their proprietary drivers
Sent from my GT-N7100 using xda premium
jbounours said:
Well I don't get it because it is sharing most of the hardware with S3 so the stuff should be at least ported easily.
Now I understand Samsung being a complete ass with their proprietary drivers
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
You still need one of the dev maintaining exynos devices to buy n7100 and then maintaining it... we can hope for someone to step up but its their freetime and money. Entropy512 told me he would be buying at&t version which is nearly identical if samsung would change their behavior. All we can do for now is to sit and wait...
Skickat från min GT-N7100 via Tapatalk 2
Hi guys, my ROM is finally finished and now uploaded at 89%.
I need a tester! My Note 2 has not arrived yet
Please write via PM.
You forgot chainfire..
Sent from my HTC One X using Tapatalk 2
This is a great thread. I hope more chefs will chime in.
I am considering a Note II but it is absolutely vital that CM is developed for it, together with Paranoid Android. Especially since Key Lime Pie (CM11?) is be around the corner.
I also think it is important with AOSP/AOKP development for it.
So I hope the issue will be sorted during this month. If not, I am afraid that I have to consider a different game plan.
Buying a device without proper developer support is a no go for me.
For everyone woundering about my sources here is a statement from Entropy512:
Entropy512 said:
Not likely to happen. If CM comes to the Note 2, it will only be if a new maintainer steps up.
Most of the current Exynos maintainer team (myself, espenfjo, codeworkx) and others have all decided that our current devices will be our last non-Nexus Exynos devices. I'm not sure about xplodwild, but I have a feeling he's highly unlikely to take up another Haxxinos with the rest of us gone and given his prior experiences with it.
If Samsung changes their attitude towards developers, this might change, but their attitude lately (zero documentation, zero platform source code, a trend towards bootloader locking - Only the Verizon S3 has a locked bootloader now, but Samsung has had the infrastructure in place since the S2 and they are constantly adding more checks) has led to the current Exynos maintainer team deciding that enough is enough. I don't think any of us are going to do anything to make Samsung's Exynos devices more attractive to any particular market segment until they provide assistance (in the form of technical documentation and source code) in return. I don't know about the others, but if they offer me a free device I'll say no - I refuse to participate in a PR stunt like the I9100 donations were.
Pretty much the only way I'll go back is if I see reference platform source that is up to the same standards as CAF and omapzoom, or they actually start providing real documentation and source code for the devices I'm currently working with.
Click to expand...
Click to collapse
Skickat från min GT-N7100 via Tapatalk 2
Thanks entwicklun,
I Googled "verizon locked bootloader samsung galaxy note" and from what I understand that it was Verizon's request to lock the bootloader. Not sure what I would do if I was Samsung but my guess is, if it helps sell more phones on Verizon then lock the boot loader. Money talks, right?
But then I'm hearing news about Samsung not giving developers this and that, just like the example below.
jbounours said:
Well I don't get it because it is sharing most of the hardware with S3 so the stuff should be at least ported easily.
Now I understand Samsung being a complete ass with their proprietary drivers
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
And I also need a phone that will have Paranoid Android (and the odd CM here and there), but it must also a 5" phablet. I guess there is nothing wrong with my current Note, but again by searching on Google there's a possibility that the "next big thing" might be the HTC Google Nexus X+. If that has an expansion card slot, that's it, I'm not getting the Note 2.
E90 Commie said:
This is a great thread. I hope more chefs will chime in.
I am considering a Note II but it is absolutely vital that CM is developed for it, together with Paranoid Android. Especially since Key Lime Pie (CM11?) is be around the corner.
I also think it is important with AOSP/AOKP development for it.
So I hope the issue will be sorted during this month. If not, I am afraid that I have to consider a different game plan.
Buying a device without proper developer support is a no go for me.
Click to expand...
Click to collapse
Thanks for all the work the dev's put in. I'm just saying, my next phone is where the developers are. Samsung doesn't own us. :laugh:
I'll be here when I get my note2 in December
For those that don't know, TW ROM, aokp and multi booting kernel (or at least 2 sesperate kernels )
Myself and utaka could probably come up with a aosp supporting kernel for the device if official CM does not materialise.
Crash Rom will be here to
Sent from my GT-N7000 using Tapatalk 2
cheers, I'm sure those browsing like me will know what's up now.
I've already ordered my note 2, but I would fully support the dev crew. even if that means selling my note 2 at a loss and buying what's being developed, pending though. I do like phablets and if the x+ doesn't have an exspansion slot then I probably wouldn't buy it.
I also hope aokp devs on the note 2. I certainly love their ROMS
leafsacc said:
Samsung getting too big for their own ego?
I currently own the Int'l N7000 and I found the development to be good for what I want. But then, I think I'll just go get a Nexus for ease of development (but the screen is so small!)
Click to expand...
Click to collapse
+ 1
g.lewarne said:
I'll be here when I get my note2 in December
For those that don't know, TW ROM, aokp and multi booting kernel (or at least 2 sesperate kernels )
Myself and utaka could probably come up with a aosp supporting kernel for the device if official CM does not materialise.
Click to expand...
Click to collapse
Are noobs like me allowed to jump in please?
Utacka sir is so kind to us all in his PA thread
Anyways, I think devving for this device would initially start with kanged TW based ROMs. With CM wary on supporting the device, it does seem a bit dark but hey, I am sure there are others to step up.
But then again, you can never be too sure.
Sent from my GT-N7000 using xda premium
---------- Post added at 08:55 AM ---------- Previous post was at 08:54 AM ----------
BTW, next nexus device is perhaps open to all OEMs.
Might be an Optimus from LG but from what I've read other manufactures are welcome to jump in and join the party.
Sent from my GT-N7000 using xda premium
I am the same, an expansion card slot is a big plus.
development support is also a big factor.
I would flash aokp right now but i'm so scared of emmc bug (which I assume will not be in the Note 2 just like it did not exist in GB ROM Notes. But who knows if "Key Lime Pie/Kandy Kane" might have a similar brick bug) on ICS kangs that I just stay far, far, away.
My ultimate fav is CassiesXtraLite so it's good to see thering1975 on the list.
entwicklun said:
I do like phablets and if the x+ doesn't have an exspansion slot then I probably wouldn't buy it.
I also hope aokp devs on the note 2. I certainly love their ROMS
Click to expand...
Click to collapse
I might bring VillainRom to the Note2, but only if/when we can get our OTA update/optional mods app up and running to a high enough standard.
Would be nice to know for wich model is going to work each developer.
- f3w1n -
Hey i'm Chriss-not an owner of Find 5 but wish i was....
I love Find 5....even it's website lists that it supports XDA,which is like a "Loyal King".
I want to buy it and i 'm trying,i checked out the xda tread and i saw official CM10.1 which really cool but there's nothing else except
AOSP.I mean if you guys can make a some-what stable CM10.1....you guys could easily make more roms like Paranoid,PAC,MIUI would be awesome on 1080p display,and many other roms....more you make better,try out-of-box like firefox os...These things make news and make the device more popular,which brings in more support,donors etc...:good:
So dev who are try hard to fix cm bugs and are stuck build some other roms also ....don't mind the bugs that arise which can be fixed later
I would like to wish the team Best Of Luck! :victory:
Just be patient.
The cm10.1 rom was only released yesterday.:good:
With working and stable CM10.1 and AOSP Roms it's easier to port other Roms that are based on either of them.
I'd much rather have those two up and running in a near perfect state before we get a bunch of people that bricked their phones because they jumped on an alpha of Paranoid Android and they have no clue how to restore them.
Aerys said:
Just be patient.
The cm10.1 rom was only released yesterday.:good:
Click to expand...
Click to collapse
Yeah. CM kangs almost never appear until CM is mostly complete for a device, and we didn't release until yesterday.
This device has only had kernel source available for sometime around a month, and isn't exactly widely available. Good development takes time.
FYI, CM went from "developers received the device" to "95% working" in less than two weeks, with the first week of that being research and laying the groundwork for a port. Most of the actual coding was done over the past weekend. Of course, this was only possible due to devices that came before us, like the Xperia Z.
It's amazing how much easier Qualcomms are to work with than Exynos.
Good lord.
Okay, you have two approaches to encourage development chrissmartin.
1) Knock yourself out and build a ROM of your own
2) Donate money to an existing developer who's working on a ROM / kernel... whatever you think is of value to you.
I don't know if you've done either, but short of those two options, please don't be 'that guy'. It's a new device in many respects, as Entropy pointed out. You want a ton of ROM's ASAP...go hop on the Sammy bandwagon.
charlatan01 said:
Good lord.
Okay, you have two approaches to encourage development chrissmartin.
1) Knock yourself out and build a ROM of your own
2) Donate money to an existing developer who's working on a ROM / kernel... whatever you think is of value to you.
I don't know if you've done either, but short of those two options, please don't be 'that guy'. It's a new device in many respects, as Entropy pointed out. You want a ton of ROM's ASAP...go hop on the Sammy bandwagon.
Click to expand...
Click to collapse
Not gonna get that on Exynos BTW.... All of the Exynos4 CM maintainers are barely touching their devices, and so far, not a single person with maintainer experience has expressed interest in the Exynos5-based GS4. (As to Qualcomm-based GS4s - Some CM people are getting them, but myself and the other ex-Teamhacksung guys are going elsewhere.)
Edit: Obviously, other people can pick up the ball and take a crack at the Exynos5 GS4, but so far, I have not encountered anyone with an interest. All of the people with AOSP-on-Exynos experience I've talked to are done with the platform, and expect Exynos5 "Octa" to be even worse than the Exynos4 was. There's always the possibility we'll get a pleasant surprise from Samsung, but I have very little hope given that they completely failed to deliver on their promises made at the Big Android BBQ.
^ very good to know, thanks Entropy!
First of all!
I'm sorry....i thought cm10.1 had been released weeks or months before...so that's why,i asked
Xiaomi themselves have described the Find 5 as " most likely next" and I'd prefer if miui was made by them.
Allanitomwesh said:
Xiaomi themselves have described the Find 5 as " most likely next" and I'd prefer if miui was made by them.
Click to expand...
Click to collapse
You won't see any discussion of their port here due to their rampant GPL noncompliance.
They're kangers of the worst sort.
I'm sure the ROMs are coming, wait til CM 10.1 is mostly stable, I'm impressed how quickly development is proceeding already.
^^ same. CM came quick! This phone is just barely starting to grab peoples attention. Its a slow start because its not an HTC or a Samsung, or a Sony... or an LG lol. This is their first international phone ever and it's the first time anyone has even heard of OPPO in the mobile world.
sent from my
CM10.1 Rocks!
https://plus.google.com/107247846330688142975/posts/8K7jsbFcwPu
Sent from my C6506 using Tapatalk 2
Things are really starting to flow now, can't wait to try out al the current custom roms
Rule one is to not ask for ETF, and perhaps make a donation.
Sent from XDA app
I just built Jellybeer, but I haven't got my Find 5 yet so can't test it yet
PAC ROM rocks! Working camera now
There's been a lot of speculation about just how Nexus-like the Galaxy S4 and HTC One Google Play edition phones will be, particularly from a technical / software update standpoint. Now, we have some relatively concrete information that sheds light on these issues.
First and foremost, Google will not directly handle software updates for Google Play edition devices. This has been reported as true, false, and generally disputed quite a lot in the lead-up to the launch. We know for a fact now (thanks to Anandtech) that while Google will supply the necessary Android builds to OEMs, the OEMs will be responsible for maintenance of kernels and all the various drivers and firmware pieces necessary for their specific device. The result is that Google gives the OEMs the Android build, and it's then up to the OEMs to make that build work on their Google Play edition device and perform the act of actually updating the phone. Google has issued an official statement that works very hard to not expressly deny that they won't be handling the updates (Droid-life):
What's this mean for you? It means that at the end of the day, the onus to update these phones will still be on Samsung and HTC. They will be able to circumvent the carrier certification runaround, and will in theory have much less work to do in maintaining these devices, but the responsibility still falls to them, not Google. This could mean any number of things. It could mean these phones will get updates within days of their Nexus counterparts. But more likely weeks, and possibly even months depending how much attention these phones are actually given by HTC and Samsung. I wouldn't say months is what we should expect, but I'm also saying such a gap is entirely within the realm of possibility. You have to remember, these phones will sell in miniscule quantities compared to their skinned brethren, and that means they aren't as high up on the value chain for software update attention. While it's certainly worth being optimistic about the update process, there's still plenty of reason to temper those expectations until we see these devices receive their first major Android release update.
he second thing we've learned is that Google will not host factory OS images for Google Play edition devices (see JBQ's post on this topic here). This will be up to Samsung and HTC, if they choose to do so. Google will also not be hosting any proprietary binaries (essentially, drivers) for these phones (again, see JBQ). Release of any binaries is, once again, up to Samsung and HTC. Taken together, all this information - as you may already have guessed long ago - means there is very little chance we'll ever see these phones supported in AOSP. It's not impossible, but it is extremely unlikely.
So there you have it: that's basically the nuts and bolts of what doesn't make the Google Play edition HTC One and Galaxy S4 Nexuses. Does this put a damper on the situation, or is it immaterial? Let us know in the comments.
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
welp this sucks !
I am not flashing this until first update comes out to see how fast they actually are, ridiculous decision.
H-Streety said:
I am not flashing this until first update comes out to see how fast they actually are, ridiculous decision.
Click to expand...
Click to collapse
Since we will probably be on 4.2.2 for a while you're going to be waiting.
Sent from my HTC One using Tapatalk 2
Possibly, but I am not losing my IR blaster and camera app for half-supported stock Android. If HTC will push out the update within a week or two after it comes out for Nexus devices, then I will definitely flash it, if not then I don't see the point of it. I would rather do S-OFF + Super Cid and still enjoy all these things than losing too many good things for basically just stock Android.
Nexus Experience Device not Nexus Device
That's really unfortunate.
Pretty ridiculous actually.
-Sent from Marino's One-
Did you really expect more? Google never said they would be Nexus devices or supported by AOSP. They are Nexus "Experience" devices... hence they offer the same feel without being the same.
Sorry to burst your bubble.... that said I think there will be dedication on the part of HTC and Samsung to get updates.. there isn't any excuse and you know if the device is on Google Play then el'Goog will be pressuring them to not delay
Sent from my Nexus 10 using Tapatalk HD
It states in Google play that both devices will get automatic updates of the latest android version.
I believe that more that others guessing about it.
Sent from my HTC One using xda premium
donharden2002 said:
It states in Google play that both devices will get automatic updates of the latest android version.
I believe that more that others guessing about it.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Zero timeline given. It will get it. The second it's released? No. A month after? Maybe.
Yep, OP...sure this is stock AOSP, but if anyone thinks the S4 and One will be updated the instant the Nexus line is, they are smoking some serious ****.
Samsung and HTC still have a role in this, ala Verizon (CDMA) Galaxy Nexus. It will slow things down. It's on HTC and Samsung to instantly update their proprietary apps to play well with AOSP. We've all seen that movie before, now have we?
Sigh. Can of worms. I called it. Once you integrate manufacturer specific features into AOSP (Beats, Zoe, etc) it WILL slow down the instant (expected) release of AOSP to "OMG PURE GOOGLE) phones. Psst: they aren't Nexi.
Just deal with it. I cringe for the blasting posts from those who got the One/S4 AOSP editions once the newest Android OS is pushed out...to the Nexus line first.
I see it now:
"THE NEXUS 4 JUST GOT 5.0. WHERE IS MY KLP ON MY ONE/S4 GOOGLE!??? PETITION STARTED!!!!1111"
And so on. Grabs popcorn.
Edit: thought I'd paste in a quote I just read that summarizes this situation quite well:
I don't see the point of these devices anymore. You lose out on the few customization that OEMs provided that weren't useless (fully functional Beats, camera software, improved text messaging and browser apps, etc.) for a vanilla experience that is nearly indistinguishable from the OEM version running a custom launcher. And no guarantee of fast updates.
You'd have to be a dummy to buy these phones from the Play store.
Thankfully I have an unlocked T-Mobile One. I'll just use it or flash whatever, whenever. Paid $450 for it and am very happy with my gamble.
So the question still remains, could someone possibly take whatever HTC releases for the GE version and put that on a carrier locked or Dev edition phone? Sorry for my lack of understanding here, but I'm just trying to figure out which phone to buy at this point.
donharden2002 said:
It states in Google play that both devices will get automatic updates of the latest android version. I believe that more that others guessing about it.
Click to expand...
Click to collapse
Automatic = sent directly to the phone.
Updates = it'll be updated.
Latest Android version = it'll get newer versions of Android.
The key words that are missing are "when" and “from whom.” I guess people can read in to that statement what they want but nothing in it makes what OP posted untrue. With so many phones orphaned on old versions of Android that statement could be as benign as "your phone will keep up with Android releases."
BarryH_GEG said:
Automatic = sent directly to the phone.
Updates = it'll be updated.
Latest Android version = it'll get newer versions of Android.
The key words that are missing are "when" and “from whom.” I guess people can read in to that statement what they want but nothing in it makes what OP posted untrue. With so many phones orphaned on old versions of Android that statement could be as benign as "your phone will keep up with Android releases."
Click to expand...
Click to collapse
google is the only one who can update aosp devices..nobody else
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
david279 said:
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
Click to expand...
Click to collapse
you are a thick one aren't you lol
hello00 said:
google is the only one who can update aosp devices..nobody else
Click to expand...
Click to collapse
The first post says it isn't an AOSP device, Google isn't managing the proprietary drivers, they aren't posting the s/w images, and they aren't responsible for pushing out updates. So your statement is true; for Nexus devices. "Play Edition's" aren't Nexus devices.
The fact that it doesn't say the below which Google says about their devices probably means what OP posted is true.
M
Argenist said:
So the question still remains, could someone possibly take whatever HTC releases for the GE version and put that on a carrier locked or Dev edition phone? Sorry for my lack of understanding here, but I'm just trying to figure out which phone to buy at this point.
Click to expand...
Click to collapse
You can flash whatever you want. Nothing new here.
I say get the phone with the most bands for resale and every day use. Hint. It isn't the Google or Dev one.
Unlock it for $7 and never look back.
Sent from my HTC One using Tapatalk 2
ericshmerick said:
You can flash whatever you want. Nothing new here.
I say get the phone with the most bands. Hint. It isn't the Google or Dev one.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Understood, but would matter then to get the GE version over the Dev?
Argenist said:
Understood, but would matter then to get the GE version over the Dev?
Click to expand...
Click to collapse
They don't ship until July 9 so no one knows.
Sent from my HTC One using Tapatalk 2
hello00 said:
google is the only one who can update aosp devices..nobody else
Click to expand...
Click to collapse
Not true..
This situation has been done before. The OG Droid (Sholes) was not a Nexus but ran vanilla software. Updates came but abit later. They came from Motorola.
Sent from my HTC One using Tapatalk 4 Beta
well guys i just came up with this news and i have heard this before but i never saw any news today sombody on fb shared this so i am really dissapointed by OnePlus :/ i was thinking to get one plus on and i m trying my best to get an invite but i guess now i have to wait for a official word on it
What do you think guys should they make their own ROM or use CM use the poll .!!
Source: http://www.tech-feed.com/technology/oneplus-abandon-cyanogenmod-coloros/
We still need the confirmation to this rumor, but if it's true, there will always be a CM rom for the OPO! All we need to do is root it and flash it.
A Tech blogging site, that doesn't quote any form of source in their article, or postulate why it might be in a company's best interest to skin their own version of Android, OR do anything other than say, they are working on their own version.... That's high school level rumor mongering. Sure it's possible.... but hey, guess what, it's already a CM compatible phone, who cares if they skin their own version of Android?
theres so many stupid fake rumors coming out of the rumor mill lately. they couldnt abandon cm if they tried. thats what happens when you sign paperwork and cm run the fastboot software and recovery.
there will be 2 years of support from CM for this device, so do not worry ^_^
funCrash93 said:
there will be 2 years of support from CM for this device, so do not worry ^_^
Click to expand...
Click to collapse
Thank you guys well the site does provide a valid Source and this news came a week ago when people in china said that they don't like CM UI so OPPO started making its own UI
Its not 100% and not 100% true as the blog says
Even if they make their own there will still be cm officially. Its likely they may just want their own skin but only provide it as an optional alternative.
This is assuming the unlikely rumor actually turns out true. But assumptions on a rumor aren't reliable so take it lightly.
tiny4579 said:
Even if they make their own there will still be cm officially. Its likely they may just want their own skin but only provide it as an optional alternative.
Click to expand...
Click to collapse
yeah this is what i read but i am a CM fan and getting special treatment from CM is always welcome as the speed of development of CM will be faster for 1+1 as compared to others
I call bs. Color os is about as Chinese as you can get.
Sent from my One using XDA Premium 4 mobile app
Doesn't bother me. I install Apex launcher and then I like ColorOS. I even install Apex CM11, i hate the stock Android and Trebuchet launchers. ColorOS has some nice features that I miss when running CM.
So long as CM doesn't stop supporting it. It's all good lol
Sent from my One A0001 using XDA Free mobile app
They already released an AOSP rom available to flash via the Development category on the oneplus forum. The only thing it's missing is the gapps.
Don't believe it!
Oneplus i very highly doubt would switch ROMs so suddenly. And Color OS is getting pretty popular for phones in China it seems, do not lose hope friend!
vladashram said:
They already released an AOSP rom available to flash via the Development category on the oneplus forum. The only thing it's missing is the gapps.
Click to expand...
Click to collapse
There's a reason they made the aosp ROM and not someone else, there aokp and paranoidandroid but there's no aosp group. The only way there would be an official aosp ROM would be if oneplus made it. It's based off cm source, oneplus has done no software development for the device. And the fact that gapps is separate actually says a lot. You can't just put on aosp and sell the device. The phone would not be Google certified. It took weeks for them to fall in line with Google's new strict standards.
Shipping ask that cyanogen inc. Works very closely with them. I think Steve klondik technically works for both companies. There's is no way they would ever end there partnership. The whole company is based around it. It's yet another fake rumor like the OnePlus tab and OnePlus two and onewatch. Best just to ignore it.
Sent from my One using XDA Premium 4 mobile app
The OP twisted topic name of the thread.
OnePlus is dropping ColorOS for their own ROM but international will still have CyanogenMod as the default ROM.
Read more, http://www.cnet.com/news/oneplus-to-drop-color-os-in-china-to-develop-its-own/
I heard a rumor that OnePlus was licensing TouchWiz from Samsung
Seriously, garbage rumors like this get floated all the time to force companies to make statements denying or clarifying the rumor. OnePlus is better off ignoring it.
new rom x oneplus one?
CafeKampuchia said:
I heard a rumor that OnePlus was licensing TouchWiz from Samsung
Seriously, garbage rumors like this get floated all the time to force companies to make statements denying or clarifying the rumor. OnePlus is better off ignoring it.
Click to expand...
Click to collapse
Touchwiz people are already tortured by that ****ty UI and if OnePlus adds that then samsung will sue them
jatin059 said:
Touchwiz people are already tortured by that ****ty UI and if OnePlus adds that then samsung will sue them
Click to expand...
Click to collapse
So will I
:good:
CafeKampuchia said:
So will I
Click to expand...
Click to collapse