Explain Life I'm 5: Besides CM acting like a$$hats, why do we care if they don't support the OPO anymore? Will we not continue to have every single Android update on Slim. PA, crRom and all the other awesome ROMS out there? I haven't received my OPO yet so I'm just trying to keep up while I patiently wait at the mail box everyday hoping to get it before the new year
If CM do decide to completely stop supporting this device, dropping CM11S/CM12S and CM11/CM12, you can wave goodbye to pretty much every custom ROM too because they basically all rely on CM at some point during their development. That isn't likely to happen though.
If CM decide to just drop official support for this device (CM11S/CM12S), it means there's some kind of a breach of contract happening because this phone was guaranteed to receive updates from CM for at least two years. Many people decided to go with this phone because it has CM on it, because it runs a ROM that's much more customisable than any other stock ROM on the market. It's like buying a Mercedes only to be told after six months that they're switching the AMG engine out for a Kia engine, nobody would be happy about that.
Transmitted via Bacon
timmaaa said:
If CM do decide to completely stop supporting this device, dropping CM11S/CM12S and CM11/CM12, you can wave goodbye to pretty much every custom ROM too because they basically all rely on CM at some point during their development. That isn't likely to happen though.
If CM decide to just drop official support for this device (CM11S/CM12S), it means there's some kind of a breach of contract happening because this phone was guaranteed to receive updates from CM for at least two years. Many people decided to go with this phone because it has CM on it, because it runs a ROM that's much more customisable than any other stock ROM on the market. It's like buying a Mercedes only to be told after six months that they're switching the AMG engine out for a Kia engine, nobody would be happy about that.
Transmitted via Bacon
Click to expand...
Click to collapse
Obviously I'm no dev, but could a CM based ROM be compiled independent of CM just by having the source code. I just assumed in my few years of flashing crap that how it worked. As long as you had the source code from Google/OEM you could compile what ever you needed. Again, I have never tried to develop anything.
TigerDNA said:
Obviously I'm no dev, but could a CM based ROM be compiled independent of CM just by having the source code. I just assumed in my few years of flashing crap that how it worked. As long as you had the source code from Google/OEM you could compile what ever you needed. Again, I have never tried to develop anything.
Click to expand...
Click to collapse
OnePlus is reportedly working on a CM-free version of a ROM for their phones, including their flagship, the One.
About the independent developers, yes, they are basing their builds on Cyanogen "base", but wouldnt be the end of the world if CM would stop developing their version, since Cyanogen is actually basing on a base Android ROM too, this means that somebody would take over the same features and develop them from scratch or even base from some of the open source from Cyanogen since, Android is Open and most of their developemt community is open too, and who knows, while it would take time, maybe will come with something better, not that i believe CM is bad.
Come on Oneplus, employ the guys over at slim roms or PA, let them make the roms for the phone if CM wants to be jackholes. My only concern is that, is it now possible that CM would push crappy updates to the phone just to be dicks, full of bugs and problems or worse, brick some phones?
TigerDNA said:
Obviously I'm no dev, but could a CM based ROM be compiled independent of CM just by having the source code. I just assumed in my few years of flashing crap that how it worked. As long as you had the source code from Google/OEM you could compile what ever you needed. Again, I have never tried to develop anything.
Click to expand...
Click to collapse
Satorikn said:
OnePlus is reportedly working on a CM-free version of a ROM for their phones, including their flagship, the One.
About the independent developers, yes, they are basing their builds on Cyanogen "base", but wouldnt be the end of the world if CM would stop developing their version, since Cyanogen is actually basing on a base Android ROM too, this means that somebody would take over the same features and develop them from scratch or even base from some of the open source from Cyanogen since, Android is Open and most of their developemt community is open too, and who knows, while it would take time, maybe will come with something better, not that i believe CM is bad.
Click to expand...
Click to collapse
That isn't the case. There's so much stuff that relies on work done by CM, I'm not sure you're quite grasping exactly how integral to development CM are. It isn't just a base. It's the kernel, it's the device trees, the list goes on and on. Yes, if CM were to disappear there would still be development, but there'd be a massive hole to fill.
Transmitted via Bacon
---------- Post added at 01:34 PM ---------- Previous post was at 01:34 PM ----------
amd-dude said:
Come on Oneplus, employ the guys over at slim roms or PA, let them make the roms for the phone if CM wants to be jackholes. My only concern is that, is it now possible that CM would push crappy updates to the phone just to be dicks, full of bugs and problems or worse, brick some phones?
Click to expand...
Click to collapse
You're not serious are you?
Transmitted via Bacon
timmaaa said:
That isn't the case. There's so much stuff that relies on work done by CM, I'm not sure you're quite grasping exactly how integral to development CM are. It isn't just a base. It's the kernel, it's the device trees, the list goes on and on. Yes, if CM were to disappear there would still be development, but there'd be a massive hole to fill.
Click to expand...
Click to collapse
I do, i am aware they its just not putting a base rom and skinning it, there's a lot of hardware architecture and software architecture (kernel) involved. But in this era, and open software, it would be a matter of time before somebody else can take charge, would not be the end of the world.
Kinda, I mean it's not impossible for CM to be childish and push bug filled software (after all their responses toward oneplus have not exactly oozed trustworthy)
amd-dude said:
Kinda, I mean it's not impossible for CM to be childish and push bug filled software (after all their responses toward oneplus have not exactly oozed trustworthy)
Click to expand...
Click to collapse
Honestly, it's a pretty ridiculous notion. The fact that they've had a falling out with OnePlus doesn't even for a second suggest that they'd take it out on the end user, and that's all they'd be doing.
Transmitted via Bacon
timmaaa said:
Honestly, it's a pretty ridiculous notion. The fact that they've had a falling out with OnePlus doesn't even for a second suggest that they'd take it out on the end user, and that's all they'd be doing.
Transmitted via Bacon
Click to expand...
Click to collapse
Well by screwing the end user they would screw oneplus, I honestly won't put anything past any company these days in the pursuit of money.
timmaaa said:
That isn't the case. There's so much stuff that relies on work done by CM, I'm not sure you're quite grasping exactly how integral to development CM are. It isn't just a base. It's the kernel, it's the device trees, the list goes on and on. Yes, if CM were to disappear there would still be development, but there'd be a massive hole to fill.
Transmitted via Bacon
Click to expand...
Click to collapse
I really don't know how much we rely on CM. I just think of it like, CM is free, once they release their stuff, anyone can take it and do what ever to it.
amd-dude said:
Well by screwing the end user they would screw oneplus, I honestly won't put anything past any company these days in the pursuit of money.
Click to expand...
Click to collapse
They have no reason to do so though. They would not benefit from it at all.
Transmitted via Bacon
I rather plain nexus like experience any cm is just too buggy and has been on every device I have owned and ran with their roms
Related
Just saw this on CM site thought i could share
http://forum.cyanogenmod.com/topic/16699-sgh-i897-cm7-first-look/
It is almost there.
Nice! Can't wait for it to go on beta.
Swyped from my Froyo-ed Captivate.
hunkyn said:
Just saw this on CM site thought i could share
http://forum.cyanogenmod.com/topic/16699-sgh-i897-cm7-first-look/
It is almost there.
Click to expand...
Click to collapse
Look nice, can't wait for a release that we can flash.
Is this version built for Captivate? Or ported from vibrant or I9000?
Sent from my PHOENIX PHONE!!!
This looks sweet, Ive not flashed my phone before to another ROM but this looks like the ROM im gonna go with.
Pardon on my ignorance, but what is the difference between Cynogen compared to other ROMs available (e.g. Firefly, Serendipity, Cognition...)
hadoyama said:
Pardon on my ignorance, but what is the difference between Cynogen compared to other ROMs available (e.g. Firefly, Serendipity, Cognition...)
Click to expand...
Click to collapse
CyanogenMod is completely open source and built from source, based on google's AOSP code drops. Firefly/Serendipity/Cognition are merely repacked (and de/recompiled) versions of Samsung's code. It's like asking the difference between linux and windows
Kaik541 said:
CyanogenMod is completely open source and built from source, based on google's AOSP code drops. Firefly/Serendipity/Cognition are merely repacked (and de/recompiled) versions of Samsung's code. It's like asking the difference between linux and windows
Click to expand...
Click to collapse
I've pledged to donate my organs few years ago. Thanks.
Jerky video is jerky. :S
I'll wait until something reliable and stable comes out. Don't want to be all:
"DUUUURRPP A HUUURRPPPP GOT ME SOME CYANOGEN MODZ!!1!"
On the first day, only to have it crash or form a singularity or something. Though, it IS a wonder as to how these developers haven't been offered jobs or something.
Verfassergeist said:
Jerky video is jerky. :S
I'll wait until something reliable and stable comes out. Don't want to be all:
"DUUUURRPP A HUUURRPPPP GOT ME SOME CYANOGEN MODZ!!1!"
On the first day, only to have it crash or form a singularity or something. Though, it IS a wonder as to how these developers haven't been offered jobs or something.
Click to expand...
Click to collapse
to be honest, a lot of them already do have jobs. also, I know from personal interactions with him that atinm actually works with a group of people and makes a lot of startup businesses and then sells them
I'm pretty sure they're all set up in terms of careers for the most part.
the cm7 build i did from last night is actually pretty stable, there are some werid qurks like cant charge your phone off and wifi sleep might causes crashes, otherwise its pretty damn usable as a daily driver. i hope they will bring out a beta release soon
what a long boring blurry video.....;
have been using the 2/25 CAPTIVATE build and like stated above its very very close to stable. Aside from the mentioned wifi, charging, camera, external usb mounting bugs and the tilt sensors being a bit flakey this thing kicks a$$! It so smooth its makes the lagfixes so far seem like childplay. also i freaking love turning the screen off!
I can see why they are urging people not to post repo builds yet but im glad they posted a "test" version for people that feel comfortable with odin and cwm. Id like to take this moment to thank the cyanogen team for putting up with the constant 'clutter' the last week with "when is it ready, why doesnt this work, will you put this in?" GAH! for that alone i plan to donate 20 dollars when this things done lol.
OH, and just as a VERY early warning, dont be surprised if MKV/other codec video files dont work even AFTER the first actual release. Basically to skim the argument the sources for these codecs are NOT open source and NOT a part of the AOSP design..so we might just be out of luck. Like i care thou lol
Kaik541 said:
to be honest, a lot of them already do have jobs. also, I know from personal interactions with him that atinm actually works with a group of people and makes a lot of startup businesses and then sells them
I'm pretty sure they're all set up in terms of careers for the most part.
Click to expand...
Click to collapse
Well I meant jobs with Google or the phone companies, but one would guess that being forced to create bloatware or something along those lines wouldn't agree with their ideals of life, liberty (from bloatware) and the pursuit of happiness.
Looks pretty decent, other than the god awful theming and other undesirable cm bits.
Sent from my Captivate.
Cyanogen had applied at google but didn't get the job.
Sent using smoke signals.
Connor1 said:
Cyanogen had applied at google but didn't get the job.
Sent using smoke signals.
Click to expand...
Click to collapse
Because Cyanogen is more open source then Google...
Sent from Xda Premium on a Captivate running Paragon 6
Kaik541 said:
CyanogenMod is completely open source and built from source, based on google's AOSP code drops. Firefly/Serendipity/Cognition are merely repacked (and de/recompiled) versions of Samsung's code. It's like asking the difference between linux and windows
Click to expand...
Click to collapse
And it's also 2.3 Gingerbread instead of Froyo.
man, I can't WAIT for this to go beta!!!
When should we expect the release of KitKat for the Relay?
When TeamApexQ deems fit to release it.
Sent from my Amazon Kindle Fire2 using Tapatalk 4
Nardholio said:
When TeamApexQ deems fit to release it.
Sent from my Amazon Kindle Fire2 using Tapatalk 4
Click to expand...
Click to collapse
Nardholio, do you expect any major innovations, and most importantly, any major sources of bugs or instabilities with KitKat?
Thanks!!
Guiyoforward said:
Nardholio, do you expect any major innovations, and most importantly, any major sources of bugs or instabilities with KitKat?
Thanks!!
Click to expand...
Click to collapse
That's a question we won't really be able to answer until there is more solid information on KitKat generally available.
Looks like CM is setting up the KitKat AOSP code for there builds Check out @CyanogenMod's Tweet: https://twitter.com/CyanogenMod/status/396000889011326976
Sent from my SGH-T699 using Tapatalk
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
Cyanogenmod Google+ post " Android 4.4 Source
Source is now being pushed to the AOSP trees. Of course, when it is all there we will begin the process of figuring out what changed, needs work, and/or is no longer feasible or needed.*
We are not in a rush to get 4.4 builds out. We are going to continue the process of working on CM 10.2 M1 - getting that out the door and onto your devices. Further, we will 'finish' the 10.2 code base, similar to what we did with 10.1.*
As a friendly reminder, please don't flood us with requests for 4.4 - we all want new and shiny things, but we will not do so at the expense of abandoning the hard work our contributors have put into 10.2.*
Final note, a lot of folks are reading into the "512mb" item on the release notes. No, this does not mean a sudden resurrection of older hardware, there are dependencies beyond the RAM (and CM has enforced that minimum since ICS)."
Sent from my SGH-T699 using Tapatalk
pst @Magamo this thread was best ended with a simple "when I say so" response and nothing more
Sent from my SGH-T699 using Tapatalk
Nardholio said:
pst @Magamo this thread was best ended with a simple "when I say so" response and nothing more
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
I actually was referring to an official KitKat OTA update from T-mobile.
How long did it take them to release a JB update after it was first introduced?
I have no interest in a CM ROM full of bugs and things that don't work.
andrewsfm said:
I actually was referring to an official KitKat OTA update from T-mobile.
How long did it take them to release a JB update after it was first introduced?
I have no interest in a CM ROM full of bugs and things that don't work.
Click to expand...
Click to collapse
Given that we never got upgraded to 4.2 or 4.3 by T-mobile/Samsung, I kinda doubt we'll be getting an official 4.4. And our CM rom, which has been built for us by a couple of people working for free, currently has fewer bugs than the official ROMs.
Jax184 said:
Given that we never got upgraded to 4.2 or 4.3 by T-mobile/Samsung, I kinda doubt we'll be getting an official 4.4. And our CM rom, which has been built for us by a couple of people working for free, currently has fewer bugs than the official ROMs.
Click to expand...
Click to collapse
4.2 and 4.3 were minor updates with no name change. JB was a major update and they did update to it.
4.4 KitKat being a major update, I've got my fingers crossed considering the wide range of devices that it's being planned for.
Was just hoping to see if there was any news on a KK update for this model.
CM is fun to play with and all, but it's not something I would trust on an everyday phone.
I use CM as a daily driver every day, and have been doing so since 10.2 became CyanogenMod official - everything just works. Now I'm not one of those people who demands a LOT of my phone, but I use it in the course of doing my job daily and it performs better, and more efficiently (with regards to battery consumption) than it did on the debloated stock rom, so much so that I deleted my Nandroid of that setup.
Sent from my SGH-T699 using the XDA-Developers app.
onebornoflight said:
I use CM as a daily driver every day, and have been doing so since 10.2 became CyanogenMod official - everything just works. Now I'm not one of those people who demands a LOT of my phone, but I use it in the course of doing my job daily and it performs better, and more efficiently (with regards to battery consumption) than it did on the debloated stock rom, so much so that I deleted my Nandroid of that setup.
Sent from my SGH-T699 using the XDA-Developers app.
Click to expand...
Click to collapse
I'm not sure if I fall into the category of demanding alot from my phone, but if there are issues like, Wifi and BT can't be on at the same time, that's not good enough. That's a serious issue. So if I forget to turn one of them off, stuff stops working? That's not okay...
I want my camera to work, for videos and photos. I want the phone to do everything the hardware is supposed to do.
andrewsfm said:
I'm not sure if I fall into the category of demanding alot from my phone, but if there are issues like, Wifi and BT can't be on at the same time, that's not good enough. That's a serious issue. So if I forget to turn one of them off, stuff stops working? That's not okay...
I want my camera to work, for videos and photos. I want the phone to do everything the hardware is supposed to do.
Click to expand...
Click to collapse
Awesome! And you want that for free? You don't seem to appreciate a lot the effort that other people are putting into this...
The wifi/bluetooth issue isn't that bad. It only falls apart when WiFi is on and connected to a 2.4GHz access point, and bluetooth is on and connected to a bluetooth device. If you have an N wifi access point that operates at 5Ghz, you can just connect to that instead of the 2.4Ghz node and then the two play nice. It's what I do.
Jax184 said:
The wifi/bluetooth issue isn't that bad. It only falls apart when WiFi is on and connected to a 2.4GHz access point, and bluetooth is on and connected to a bluetooth device. If you have an N wifi access point that operates at 5Ghz, you can just connect to that instead of the 2.4Ghz node and then the two play nice. It's what I do.
Click to expand...
Click to collapse
I would do this if I had a 5GHz AP, but what I'm saying is that I don't want to have to worry about stuff like that.
Guiyoforward said:
Awesome! And you want that for free? You don't seem to appreciate a lot the effort that other people are putting into this...
Click to expand...
Click to collapse
I don't want anything for free, except a stock KitKat update from T-Mobile/Samsung for the hardware I paid for... At no point did I say I was interested in CM. I've been explaining why I'm not, the whole time.
I started this thread to find out how long historically after the release of a new OS, does it usually take Samsung/T-Mobile to release an OTA?
andrewsfm said:
I would do this if I had a 5GHz AP, but what I'm saying is that I don't want to have to worry about stuff like that.
I don't want anything for free, except a stock KitKat update from T-Mobile/Samsung for the hardware I paid for... At no point did I say I was interested in CM. I've been explaining why I'm not, the whole time.
I started this thread to find out how long historically after the release of a new OS, does it usually take Samsung/T-Mobile to release an OTA?
Click to expand...
Click to collapse
Normally only after the Samsung high-end phones get the update and they are just barely getting Android 4.3. It also depends if they decide to update this phone at all. I have been asking t-mobile and Samsung that and they keep blaming each other or referring me to the forum for the phone on there websites.
Sent from my SGH-T699 using Tapatalk
chris122380 said:
Normally only after the Samsung high-end phones get the update and they are just barely getting Android 4.3. It also depends if they decide to update this phone at all. I have been asking t-mobile and Samsung that and they keep blaming each other or referring me to the forum for the phone on there websites.
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
I guess Windows has spoiled me, because I don't understand how it's so hard to port Android to each device.
AMD or Intel, they both use the same instruction set, so they work on any x86/x64 processor, and then you install drivers for your hardware peripherals.
Shouldn't Android run on any ARM processor, and then just have drivers that need to be plugged into it for each component of the phone to work?
Apparently it's a lot more complicated than that, but why...
andrewsfm said:
I guess Windows has spoiled me, because I don't understand how it's so hard to port Android to each device.
AMD or Intel, they both use the same instruction set, so they work on any x86/x64 processor, and then you install drivers for your hardware peripherals.
Shouldn't Android run on any ARM processor, and then just have drivers that need to be plugged into it for each component of the phone to work?
Apparently it's a lot more complicated than that, but why...
Click to expand...
Click to collapse
A lot of the complexity comes from the manufacturers of the SoCs not opening up the workings of their drivers to the wider world that makes porting to new devices, and to new versions of Android so difficult. Things work on one kernel, or one interface, and that's it, and we have no way of tweaking it to work in other ways. Back to the subject at hand. I personally suspect that the Relay will get no official update to KitKat. The Relay is over a year old, T-Mobile has been trying to dump it since 2013 began, and they are the only retailer. The 4.1.2 Jelly Bean updates were rolling out to the then mainline Samsung phones within a week of the Relay's release in September 2012, and we didn't get our update (which frankly is a broken PoS, ESPECIALLY when held up against any CM build for the Relay) until March or April of '13, so expect another 6 months before we MIGHT (and likely won't) get an official 4.3 update.
Looks like coding for CM 11 has started. Check out @CyanogenMod's Tweet: https://twitter.com/CyanogenMod/status/397817644650205185
Sent from my SGH-T699 using Tapatalk
Magamo said:
A lot of the complexity comes from the manufacturers of the SoCs not opening up the workings of their drivers to the wider world that makes porting to new devices, and to new versions of Android so difficult. Things work on one kernel, or one interface, and that's it, and we have no way of tweaking it to work in other ways. Back to the subject at hand. I personally suspect that the Relay will get no official update to KitKat. The Relay is over a year old, T-Mobile has been trying to dump it since 2013 began, and they are the only retailer. The 4.1.2 Jelly Bean updates were rolling out to the then mainline Samsung phones within a week of the Relay's release in September 2012, and we didn't get our update (which frankly is a broken PoS, ESPECIALLY when held up against any CM build for the Relay) until March or April of '13, so expect another 6 months before we MIGHT (and likely won't) get an official 4.3 update.
Click to expand...
Click to collapse
Ah k I see. The hardware vendors are mostly to blame it seems.
I may try a stable CM11 if that ever sees the light of day, but I won't hold my breath.
I've heard about the official JB ROM being problematic, so I plan to stay on ICS the phone originally shipped with.
I'm just glad to be getting rid of my Droid3 and Gingerbread.
andrewsfm said:
Ah k I see. The hardware vendors are mostly to blame it seems.
I may try a stable CM11 if that ever sees the light of day, but I won't hold my breath.
I've heard about the official JB ROM being problematic, so I plan to stay on ICS the phone originally shipped with.
I'm just glad to be getting rid of my Droid3 and Gingerbread.
Click to expand...
Click to collapse
True, there have been some bugs. However, I use the official nightly of cm10.2 as a daily driver. I'd rather put up with the MINOR issues that are left (hardware is stable for the most part) than have a manufacturer ROM. IMHO, the stock ROM that comes with the phone is usually full of crap bloat ware that I don't use and takes up space, and a UI that is SEVERELY limited in customization.
Also, the more people participate and report problems, the faster it takes TeamApex to fix and push out. At least team apex RESPONDS to their users. As mentioned before, it can take as long as 6-8 months after an android release for the manufacturer to roll out an update...still full of crap ware that's NOT used and cannot be uninstalled without root privileges or botching up the UI further.
These people who work tirelessly to provide to us, the end user, an updated version of Android, do so out of their own free will, and don't get a penny. These devs are here to proudly share what they have created, and I applaud and give my utmost respect to them.
You don't wanna install aftermarket firmware? Don't want to aid in bug reporting? Fine, put up with the crap that the manufacturer pushes onto you. Plus, Samsung & T-Mobile don't get any more of your hard earn dollars rolling out an Android update for our year-old device. They'd rather you dump it and buy the latest phone. THAT'S THEIR BUSINESS MODEL! So they have no interest in rushing an update to something as "old" as the Relay.
If you want JB or KK and are unwilling to wait for & install after-market firmware, I suggest you pony up the dough and buy a nexus 5. Better still, learn how to dev and make your own version of JB or KK for the Relay. That's the beauty of open source.
Your rant and *****ing about when "they are going to develop Kit Kat" makes you come across as arrogant, snobbish, and child-like.
Sorry for MY ranting, but it's unappreciative asshats like andre that just piss me off.
Sent from my SGH-T699 using XDA Premium 4 mobile app
I have all kinds of Android devices and I use Cyanogenmod on all of them. I like to have the same exact system on each; saves me time, to have to learn only one. Plus I very much like CM.
But on this device, for some reason, most of the development effort seems to go to the *toad releases. Could someone elaborate why? Secondly, why use a *toad instead of the "real" Cyanogenmod?
hardy81 said:
I have all kinds of Android devices and I use Cyanogenmod on all of them. I like to have the same exact system on each; saves me time, to have to learn only one. Plus I very much like CM.
But on this device, for some reason, most of the development effort seems to go to the *toad releases. Could someone elaborate why? Secondly, why use a *toad instead of the "real" Cyanogenmod?
Click to expand...
Click to collapse
Because the official releases are posted in the CyanogenMod website under downloads>official devices...the device maintainer for cm on apexqtmo was also banned from xda
Sent from my R3L4Y 4G using xda-developers app
Ummm, What? The official device maintainer for CM is @Nardholio who is definitely still here.
The HypnoToad images started as TeamApexQ's test bed, as time went on, there were tweaks that were made that were not accepted by CM for one reason or another, but we liked them. They became part of our internal builds, which as that stabilized and diverged more from CyanogenMod, we made available as FatToad. OmniToad is based on Omnirom, not CyanogenMod. The majority of TeamApexQ likes the Omni base better, so that has become our development platform.
One of the tweaks that are part of FatToad have bitrotted a bit, and the developer of that tweak has moved on to OmniToad, and has no intention of going back and maintaining said tweak, so FatToad likely will not be seeing any more releases.
Fear not though, the work on HypnoToad DOES still benefit the official CyanogenMod builds, as fixes are freely ported from one to the other.
Magamo said:
Ummm, What? The official device maintainer for CM is @Nardholio who is definitely still here.
The HypnoToad images started as TeamApexQ's test bed, as time went on, there were tweaks that were made that were not accepted by CM for one reason or another, but we liked them. They became part of our internal builds, which as that stabilized and diverged more from CyanogenMod, we made available as FatToad. OmniToad is based on Omnirom, not CyanogenMod. The majority of TeamApexQ likes the Omni base better, so that has become our development platform.
One of the tweaks that are part of FatToad have bitrotted a bit, and the developer of that tweak has moved on to OmniToad, and has no intention of going back and maintaining said tweak, so FatToad likely will not be seeing any more releases.
Fear not though, the work on HypnoToad DOES still benefit the official CyanogenMod builds, as fixes are freely ported from one to the other.
Click to expand...
Click to collapse
XDA refuses to ban me
Nardholio said:
XDA refuses to ban me
Click to expand...
Click to collapse
i thought it was lbcoder....well thats what i was told anyway....grats on being a good maintainer Nard
hi
The difference between the original ROM and Kastvm
Magamo said:
Fear not though, the work on HypnoToad DOES still benefit the official CyanogenMod builds, as fixes are freely ported from one to the other.
Click to expand...
Click to collapse
This is good to hear. Programmers of free software tend to jump ship pretty quickly and get bored with anything that is not new & cool. But Cyanogenmod should be seen as cool, since it's just awesome to have the same system on so many devices.
Thanks for the clarifications.
hardy81 said:
This is good to hear. Programmers of free software tend to jump ship pretty quickly and get bored with anything that is not new & cool. But Cyanogenmod should be seen as cool, since it's just awesome to have the same system on so many devices.
Thanks for the clarifications.
Click to expand...
Click to collapse
As a very agreeable argument...the same could go for other great ROMs too and not just CyanogenMod..just takes developers to bring em to the device including CM...to each his own and that's why there is a variety to choose from
Sent from my R3L4Y 4G using xda-developers app
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
In an interview of Kondik, he said that now that they're a company and this is their product, they have actual paid devs working on the updates, which should make their code more higher quality and updates faster (though now that they have to make it stable means that it will slow updates down, I hope there will be a nightly channel)
mannu_in said:
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
Click to expand...
Click to collapse
Don't bet on that. Look at how poorly the community CM builds (i'm talking official nightlies, those are "community" builds from the point of view of Cyngn) for the Oppo N1 are. It's Cyngn's official position that they don't care at all if the community builds are completely broken and that users should have no expectations whatsoever from them.
Use nightline updates and you'll be happy :laugh: it helps a lot to devs make CM better and better
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
MrAndroid-HD said:
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
Click to expand...
Click to collapse
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
floepie said:
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
Click to expand...
Click to collapse
Remmember this is a special verison of CM, there is nothing like it used to that you can rely on. I know how things where in the past, but this is really one of their first projects where they are the main system on the phone from start - I know they where on the Oppo N1 also from the beginnign, but as far as I know, there weren't made a set deal like with the OnePlus..
Here OnePlus have a 2 year contract on a special version of CM.. Only time will tell us how much it differs from their normal releases..
As said before, the Cyanogen transition from a hobby to a company might give a huge benefit here.
It's true that the waiting time between stable releases has historically been quite poor, but I have extremely good experiences with CM nightlies. I'm running nightlies on my Galaxy Nexus and Nexus 7, and I can't really complain about anything. Hopefully we'll have an easy opt-in to the nightlies (like there is currently) and that the first nightlies get pushed out fast as Android is updated.
Also, we'll always have community builds.
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
LiquidSolstice said:
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
Click to expand...
Click to collapse
That's done via touchscreen controller firmware - which isn't itself opensource (it's just a blob encoded into a header file within the kernel), but will work no matter what you're running on the device with a only a few tweaks to the frameworks/kernel. Plenty of projects have experience with these tweaks since the Oppo N1 had the same capability.
floepie said:
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Click to expand...
Click to collapse
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
maxver0 said:
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
Click to expand...
Click to collapse
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Entropy512 said:
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Click to expand...
Click to collapse
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
maxver0 said:
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
Click to expand...
Click to collapse
That's bull****. The only thing they can blame Oppo on is the initial O-Click fiasco - nothing beyond that. (And I'm letting them slide for the O-Click mess, that really wasn't their fault)
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
dracinn said:
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
Click to expand...
Click to collapse
We're not talking about nightlies here, since there's no guarantee for users that they'll be anything but crap. Cyngn is ADAMANT about this position. If community builds (nightlies) for a Cyngn device are broken, you're SOL.
Entropy512 said:
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
Click to expand...
Click to collapse
Well that someone prefer more one rom than the other doesn't prove anything. I prefer custom rom Slimkat on my Nexus 4 even if stock is super stable or even a cyanogenmod rom on my phone. I tried OmniRom on my N4 tho but I couldn't find multiwindow at all in rom so I flashed over something else...
I've used a few other androids before with custom ROMs, and a major obstacle to stability seems to often be the fact that manufacturers typically don't include open source drivers, which leads to reverse engineered open source drivers being developed on xda, which often aren't as good as the binaries that can only be used with stock based ROMs.
Since the n5 is a Google phone, are the drivers open source as well?
v1nsai said:
I've used a few other androids before with custom ROMs, and a major obstacle to stability seems to often be the fact that manufacturers typically don't include open source drivers, which leads to reverse engineered open source drivers being developed on xda, which often aren't as good as the binaries that can only be used with stock based ROMs.
Since the n5 is a Google phone, are the drivers open source as well?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/drivers
https://android-review.googlesource.com
As far as I know, the stock ROM on the Nexus 5 doesn't use any proprietary binaries so it stays closer to AOSP, which is why it also seems to perform "worse" in benchmarks and makes some people buy other devices because they have "better performance", lol.
the nexus 5 is a nexus, those drivers are made directly for the nexus 5, no hacking needed. other androids are different, they arent nexus.
Sorry for delayed reply
Sounds like you guys are basically saying that since the N5 comes with real, untampered stock android so custom Roms are only marginally beneficial.
I'm gonna have to try this out, it sounds like Android the way it's supposed to be without all the carrier and manufacturer crap destroying it.
The fact that the CM thread is so quiet on this board really days a lot.
v1nsai said:
Sorry for delayed reply
Sounds like you guys are basically saying that since the N5 comes with real, untampered stock android so custom Roms are only marginally beneficial.
I'm gonna have to try this out, it sounds like Android the way it's supposed to be without all the carrier and manufacturer crap destroying it.
The fact that the CM thread is so quiet on this board really days a lot.
Click to expand...
Click to collapse
yea, there are better roms than cm, almost all aosp based, not as bloated and much faster.
v1nsai said:
Sorry for delayed reply
Sounds like you guys are basically saying that since the N5 comes with real, untampered stock android so custom Roms are only marginally beneficial.
I'm gonna have to try this out, it sounds like Android the way it's supposed to be without all the carrier and manufacturer crap destroying it.
The fact that the CM thread is so quiet on this board really days a lot.
Click to expand...
Click to collapse
If CM thread is quiet, it's being overshadowed by superior ROMs. Unsure why anyone would choose it for a Nexus.
Stock ROM works but has zero options. Couldn't stand it without Xposed. Don't want Xposed because I want ART.
I'm saying flash SlimKat for ROM. Then flash Code_Blue kernel. My opinions are subject to change... several times a month. And TWRP or PhilZ for recovery. Stay away from stock CWM.
So the stock drivers can be used for any aosp ROM because the stock is aosp? Or are there licensing issues with that?
v1nsai said:
So the stock drivers can be used for any aosp ROM because the stock is aosp? Or are there licensing issues with that?
Click to expand...
Click to collapse
one and the same in this case