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
Related
In theory wouldn't we be able to take an ics Rom from the prime, get drivers working for our tegra to achieve hardware acceleration? Not completely sure of the differences between both devices other than the processor.
Sent from my PC36100 using Tapatalk
It would take time in order for developers to translate the drivers.
Put it this way. It would be quicker, and easier, to wait even a month for the TF101 to receive ICS rather than trying to translate from the Prime to the TF101.
Rumor mill has it that the TF101 will be receiving ICS at the end of the month.
I heard a rumor about an ICS rom already out there on the web, but that's just a rumor. You have to ask yourself if it's worth it to risk your tablet's life or just wait a month. Don't do like me...
Fellas, they're already working on porting the Motorola xoom's ICS over to the TF101 as we speak. Working out a few bugs now, could possibly be here before the official ICS build if noobs will quit asking them how to flash the unfinished product and other development-unrelated questions (in other words, have a peek, but don't bug the big guys at work )
BTW TF201 has the Tegra 3, while Xoom has a tegra 2..much easier to port from what I understand..so don't hold your breath on the Prime's ICS coming to roost on your OG TF any time soon..
I saw something from Asus that said we won't be getting it until February. I'll be looking forward to the Xoom port!
brando56894 said:
I saw something from Asus that said we won't be getting it until February. I'll be looking forward to the Xoom port!
Click to expand...
Click to collapse
I personnally think it's stupid to take risks to get what you can get in one month, in a more adapted way. Who knows! Maybe you'll end up bricking your device...
Xoom has most of the same hardware....so they're just taking the items that aren't for our device and replacing them with proper drivers.
Sent from my PC36100 using Tapatalk
Horclok said:
I personnally think it's stupid to take risks to get what you can get in one month, in a more adapted way. Who knows! Maybe you'll end up bricking your device...
Click to expand...
Click to collapse
For one, it isn't a risk once the devs have gotten it right to flash if you know what you are doing, there will have been 100 people who flashed the ROM repeatedly while testing before you ever gt your hands on it.
Second point- the official ICS update will almost surely take some time to Root, if your device wasn't rooted before the update, and no such problem will exist with a dev ICS ROM since it will be rooted in the source.
Final point- ICS is ICS, if the hardware works, and software functions, there isn't much difference between the official build and a ported build, except for the ported build is at the mercy of the devs to put whatever goodies and extras the official ICS build didn't include..
ICS official = wait and get stuck without root
ICS dev ROM = be here soon and have root + extras.
Which one do you prefer now?
Horclok said:
I personnally think it's stupid to take risks to get what you can get in one month, in a more adapted way. Who knows! Maybe you'll end up bricking your device...
Click to expand...
Click to collapse
Outside of proprietary hardware drivers, I have yet to see an OEM ROM exceed performance of a community ROM. OEMs have nowhere near the amount of people working on their ROMs as a community version, and nowhere near the amount of eyes checking for bugs.
Cheers!
-M
Xda member since 2007
luna_c666 said:
For one, it isn't a risk once the devs have gotten it right to flash if you know what you are doing, there will have been 100 people who flashed the ROM repeatedly while testing before you ever gt your hands on it.
Click to expand...
Click to collapse
There is always a risk when you flash a rom, always. Now I had your opinion before I bricked my device, and I knew what I was doing. Then again, you have to choose between security and variety.
dragon_76 said:
Outside of proprietary hardware drivers, I have yet to see an OEM ROM exceed performance of a community ROM. OEMs have nowhere near the amount of people working on their ROMs as a community version, and nowhere near the amount of eyes checking for bugs.
Click to expand...
Click to collapse
This is so true. Even if the OTA ICS update were to be released, I would still wait for a Dev to mess around with it before I updated. Call me crazy, but I'm not a fan of OEM skins and their performance is always lacking.
Horclok said:
There is always a risk when you flash a rom, always. Now I had your opinion before I bricked my device, and I knew what I was doing. Then again, you have to choose between security and variety.
Click to expand...
Click to collapse
How did you get a brick? Flash failed halfway through or something? I've probably flashed 100 ROMs, from xbox to android, the only device I ever bricked was a windows phone, and its just soft bricked now. I didn't know what I was doing with that thing...I've had plenty of close calls don't get me wrong, heck I lifted up a trace on my xbox motherboard and had to repair it on the spot with solder within 10 minutes or the clock-capacitor would have discharged forcing me into clock-loops (death for an xbox)..'know what you're doing' has very different levels of complexity
There is always a risk, to be sure, I should have worded myself better. But the same amount of risk as any ROM, not specific to this one..I've never heard of an OTA update failing and bricking a device, but I'm sure it can happen as well..anytime you are flashing onboard firmware there's always a chance something can go wrong. I was just saying that a Dev rom will have been flashed and booted and reflashed 100 or 1000 times by the devs during the build process before any of us 'outsiders' gets a taste of it. In my opinion, that's about as risk-free as it gets with modding these things..and in the end, who is going to upgrade to ICS without wanting it rooted? At least, who on this site?
I feel much more confident loading an already rooted ICS rom from the community than I do flashing the OTA update and wondering if I'm going to lose root/recovery etc. It is a personal opinion though..
luna_c666 said:
I feel much more confident loading an already rooted ICS rom from the community than I do flashing the OTA update and wondering if I'm going to lose root/recovery etc. It is a personal opinion though..
Click to expand...
Click to collapse
This.
OEM updates of any kind are more known for borking a system than a community version and again, it is because there are many more eyes on a community version. OEM versions are seen as a necessary evil for them. The life cycle of the product is usually over or already over and they do not want to devote any resources to an endeavour that now only costs money instead of makes money.
Asus may be a little different with the TF101 because they still are selling a fair amount of them. Best Buy still keeps restocking the 16GB version and with the TF201 problems they may push the TF101 as a sort of "budget premium" since ICS completely re-invigorates older hardware (my Atrix is running an alpha build without OC and GPU accel and it is just as smooth as full GPU and OC).
I still plan on waiting for Gnufabio's ICS Revolver release.
Cheers!
-M
Xda member since 2007
dragon_76 said:
I still plan on waiting for Gnufabio's ICS Revolver release.7
Click to expand...
Click to collapse
I just tingled at the thought.
ICS does breathe a lot of new life in to old hardware. My old Incredible runs it fairly smoothly, just laggs a bit on transitions. But it did make me more interested in my old phone.
maybe....
http://au.ibtimes.com/articles/5034...veals-android-4-kitkat-os-11.htm#.UicpuH-I68A
here's a quote from the article:
Android 4.4 KitKat Features
Google hasn't revealed any features yet of the upcoming Android 4.4 KitKat but instead, the company said: "our goal with Android KitKat to make an amazing Android experience available for everybody."
With this statement from Google, it is expected that KitKat will become accessible to Android-running devices with lower RAM such as 512MB and older Android version such as 2.3 Gingerbread. This optimisation has been rumoured to be included in Android 5.0 Key Lime Pie.
Click to expand...
Click to collapse
What...
http://signatures.mobile-overload.com/wp-content/uploads/2013/07/sig-cm-5.png
I would not hold my breath.
Sent from my SCH-I545 using XDA Premium HD app
lol no. Unless if it was created by an awesome person here, but there's no point in that. This phone is long dead, earlier this week I finally moved on, and oh my gosh, its been great having a Nexus 4 over this phone that was out-dated before it was even released back in Spring 2011.
Nope
You'll probably never see a KitKat version on the Charge. The main reason is the same that you never saw ICS or JB on the Charge. The code for the radios was never released. I've tried JB on the Charge, it runs well; however the camera and data don't work. Also, while I still use the Charge as my primary phone, there's not many of us left.
ICS and all versions of JB work fine on this phone already... we are just missing the radios.
I doubt anyone cares about this phone anymore anyways...
10amla said:
You'll probably never see a KitKat version on the Charge. The main reason is the same that you never saw ICS or JB on the Charge. The code for the radios was never released. I've tried JB on the Charge, it runs well; however the camera and data don't work. Also, while I still use the Charge as my primary phone, there's not many of us left.
Click to expand...
Click to collapse
I'm inclined to agree, though it would be awesome to be proven wrong!
JihadSquad said:
ICS and all versions of JB work fine on this phone already... we are just missing the radios.
I doubt anyone cares about this phone anymore anyways...
Click to expand...
Click to collapse
Yeah not many folks left that's for sure... still a few that care though
dwitherell said:
I'm inclined to agree, though it would be awesome to be proven wrong!
Yeah not many folks left that's for sure... still a few that care though
Click to expand...
Click to collapse
I agree with both assessments. Thanks for all the work you've done on Tweaked, Dwith. My wife and I love it on our charges.
P.S. One problem I had with Tweaked Lite, when I installed it, it didn't install file manager(I think that's what it's called on stock) and when I went to select a sound(not ringtone) for a ringtone it would show and error. I went to tweaktools and installed the file manager and it works fine. Not sure why it wouldn't work with my other file management programs.
10amla said:
I agree with both assessments. Thanks for all the work you've done on Tweaked, Dwith. My wife and I love it on our charges.
P.S. One problem I had with Tweaked Lite, when I installed it, it didn't install file manager(I think that's what it's called on stock) and when I went to select a sound(not ringtone) for a ringtone it would show and error. I went to tweaktools and installed the file manager and it works fine. Not sure why it wouldn't work with my other file management programs.
Click to expand...
Click to collapse
Yeah I am not a fan of MyFiles, and for better or worse the call to that for ringtone selecting is hardcoded... at least tweaktools brings it back quick enough - forgot about that tbh, sorry for the troubles!
dwitherell said:
Yeah I am not a fan of MyFiles, and for better or worse the call to that for ringtone selecting is hardcoded... at least tweaktools brings it back quick enough - forgot about that tbh, sorry for the troubles!
Click to expand...
Click to collapse
I agree with your take on MyFiles, one of the first thing I did was replace it with something else(currently FX File Manager). I wasn't a big deal, I had planed on copying my few ringtones to system anyway.
while I agree that the we are more likely to see Republicans and Democrats agree on something, would still be interesting to see if this holds true. I really would not be surprised though, if older devices do get upgraded to the latest OS - that could mean larger revenues for Google. more folks would be able to use their apps, services, etc. without having to get a new device.
however, after then, they could see how slow their device is, and then they decide to upgrade. but still, worth keeping an eye on.
Google and Verizon both agreeing to do this? Hell will freeze over first.
Sent from my SCH-I510 using xda app-developers app
From my understanding of several stories posted from Android sites since KitKat was announced, It sounds like either Google is going to update phones to KitKat silently like they have been doing everything else without the help of Samsung or Verizon or perhaps we just get these features without ever actually upgrading to KitKat
Hangouts is supposed to be replacing the stock Messaging app-If Google can do that then why would they need anything from Samsung/Verizon??
http://www.androidpolice.com/2013/1...msmms-integration-video-sharing-capabilities/
http://mobilesyrup.com/2013/10/08/h...uts-will-almost-certainly-integrate-with-sms/
4.4 "Google Experience" Launcher Launcher could be released from the Play Store (which would replace touchwiz??)
http://www.androidpolice.com/2013/1...re-some-things-we-are-expecting-to-see-in-it/
The truth of the matter is this. The Motorola Droid 1, a phone I bought as a media/mp3 player for 50 bucks and fixed up, is working better than a phone I paid 300 new and had nightlies and better support. I loved my charge, the battery sucked. And the phone I use now is the Verizon note 2 and sprint note 3 as a business phone since I now work for the sprint corporation. Do I miss my charge? Yes. Do I wish it had some cyanogenmod support being a phone 1 1/2 years newer than the droid 1? yes. As soon as I can learn how to make a rom for the charge, I plan to make an ics or jb nightly that will support a wifi only support on this relic. It was my first 4g phone. I have it in my desk and feel sad since it helped me achieve so much.
asacado said:
The truth of the matter is this. The Motorola Droid 1, a phone I bought as a media/mp3 player for 50 bucks and fixed up, is working better than a phone I paid 300 new and had nightlies and better support. I loved my charge, the battery sucked. And the phone I use now is the Verizon note 2 and sprint note 3 as a business phone since I now work for the sprint corporation. Do I miss my charge? Yes. Do I wish it had some cyanogenmod support being a phone 1 1/2 years newer than the droid 1? yes. As soon as I can learn how to make a rom for the charge, I plan to make an ics or jb nightly that will support a wifi only support on this relic. It was my first 4g phone. I have it in my desk and feel sad since it helped me achieve so much.
Click to expand...
Click to collapse
That's exactly what I was thinking - even if the radios weren't released, having the phone to use over wifi would be good enough for me. I guess that's the question - would it be possible to work up a kitkat ROM that was just purely wifi?
zereoue said:
That's exactly what I was thinking - even if the radios weren't released, having the phone to use over wifi would be good enough for me. I guess that's the question - would it be possible to work up a kitkat ROM that was just purely wifi?
Click to expand...
Click to collapse
I've seen an ics rom that was floating around, but support for this phone was always limited. It came and went faster than any other phone I saw. Hell, the bionic I owned had support and nightlies all the way up to the day I got the note 2. I digress. I am looking into it as soon as I can get a linux kitchen set up.
asacado said:
I've seen an ics rom that was floating around, but support for this phone was always limited. It came and went faster than any other phone I saw. Hell, the bionic I owned had support and nightlies all the way up to the day I got the note 2. I digress. I am looking into it as soon as I can get a linux kitchen set up.
Click to expand...
Click to collapse
I am learning how to build for android. Starting with the fascinate since there is a lot of support so I can gain familiarity and then I'm going to do a build for the charge. I intend to only use it as a media device. I can't promise or guarantee anything but, I will try my best to deliver a bootable kitkat rom. This is all pretty difficult. We shall see what happens.
pyroman512 said:
I am learning how to build for android. Starting with the fascinate since there is a lot of support so I can gain familiarity and then I'm going to do a build for the charge. I intend to only use it as a media device. I can't promise or guarantee anything but, I will try my best to deliver a bootable kitkat rom. This is all pretty difficult. We shall see what happens.
Click to expand...
Click to collapse
I have a Fascinate as well, but haven't installed any of the KK offerings for it yet. I did notice that when updating the Fascinate to KK you have to flash a 4.1 or 4.2 rom first, to get the file system setup, right? Then flash the 4.4 rom. Would the steps be the same for the Charge?
zereoue said:
I have a Fascinate as well, but haven't installed any of the KK offerings for it yet. I did notice that when updating the Fascinate to KK you have to flash a 4.1 or 4.2 rom first, to get the file system setup, right? Then flash the 4.4 rom. Would the steps be the same for the Charge?
Click to expand...
Click to collapse
AFAIK you shouldn't have to flash any rom first.. I could be wrong. I don't keep up with all the fascinate development. I did flash a 4.4 rom in the past from cm10.1.
I have a build enviroment set up and I am running into problems building cm11 for the fascinate. I think by the errors that I need to increase the system partition. Because the build always fails at making the system.img. The build guides make it seem like you should run into no errors at all.
I'll start building for the charge soon. I'm too much of a noob to actually develop for it right now, but I think I can atleast boot it once I figure out how to build it.
pyroman512 said:
AFAIK you shouldn't have to flash any rom first.. I could be wrong. I don't keep up with all the fascinate development. I did flash a 4.4 rom in the past from cm10.1.
I have a build enviroment set up and I am running into problems building cm11 for the fascinate. I think by the errors that I need to increase the system partition. Because the build always fails at making the system.img. The build guides make it seem like you should run into no errors at all.
I'll start building for the charge soon. I'm too much of a noob to actually develop for it right now, but I think I can atleast boot it once I figure out how to build it.
Click to expand...
Click to collapse
not sure if I mentioned this earlier, but it could be the fact that the charge is based on RFS system (GB 2.3). I believe android went EXT4 with ICS and higher. there are some kernels that can convert the Charge to EXT4 - so not sure if that would help ya.
Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag
There will be peace in the middle east first. :banghead:
Sent from my SM-N900V using XDA Premium 4 mobile app
Just because they say it could run on lower end phones doesn't mean it will run w/o lag and so on. I heard the chez won't be getting kit Kat so what does that tell you about the older phones.
Sent from my HTC6500LVW using Tapatalk
The only thing that will run on lower end devices is the new launcher and Google apps. The new ui is supposed to be included in the new launcher and make lower end devices feel and look more like newer ones.
Sent from my ADR6425LVW using Tapatalk
lazarus0000 said:
Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag
Click to expand...
Click to collapse
The problem with an upgrade to any newer OS on the Charge is the radios. I don't see KitKat and an exception.:crying::crying:
Interesting how they had it where you could use Hangouts as your default SMS App with all the Emoji smileys on phones with Gingerbread including the Charge on the leaked version from the Nexus 5. It was fully working and I tried it. However, now that it's released to everybody through the Play Store, the SMS option is for Android 4.0 Only.
just got kitkat on my razr.... wish I knew how to port, b/c then I would attempt to port this great ROM over to the old Charge....
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2284985
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
I think you're on the right track, though I think I'd stick with CM11 rather than CM10.2.
Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs
pyroman512 said:
Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs
Click to expand...
Click to collapse
good luck brother... i'd be glad to test for ya.
some tips that you may/may not already know:
my understanding is that OS 4+ require EXT4 rather than RFS, so it might help to start with a kernel that allows this conversion. there are a few floating around that work.
someone (JT) has successfully (and I guess relatively easily) ported ICS and JB to the charge, the key aspects not working though were mobile data and camera.
I'm told the key road block is the RIL for the kernel in order to get those aspects functioning properly.
as for me, I'd be happy with just a working camera, as the Charge is used by my son as a WiFi-only media player/gaming device. he likes to take pictures/videos, so this is the only thing preventing me from converting it the latest JB port.
again, good luck, and let us know how the progress goes!
Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.
pyroman512 said:
Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.
Click to expand...
Click to collapse
As a previous owner of a droid charge, I honestly hope I can squeeze some use out of it as a media device.
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...
A Few months ago, OPO and Cyanogen, said 90 days after the official Lollipop release from Google, the OnePlus One OS would get the big Lollipop date. So that puts it end of Jan / early Feb. But is that still on track of happening ?
But...with the all the news lately of Cyanogen and OPO not getting along, and the whole India deal, etc...
What will OPO official release as far as the Lollipop update ? Will there still be a CM12S made specific for the OnePlus by Cyanogen ? Or will OPO just release their in house Lollipop ROM they made themselves without CM ?
The last I read, there is a big update coming in January, which would presumably be CM12S Lollipop. OnePlus also has announced that they are on the verge of releasing their own, house built ROM, so it's possible that is also coming in that time frame.
Sent from my iPad using Tapatalk
There's not much point in asking that here, nobody here can answer the question properly. Plus, even if CM were reading here, they don't respond to requests for ETA's.
Transmitted via Bacon
timmaaa said:
There's not much point in asking that here, nobody here can answer the question properly. Plus, even if CM were reading here, they don't respond to requests for ETA's.
Transmitted via Bacon
Click to expand...
Click to collapse
Not really asking for an ETA. I know they both said 90 days after Lollipop code release.
But my question is more about if it will even come at all now ? Due to the rocky relationship between OPO + Cyanogen.
Sent from my A0001
Zorachus said:
Not really asking for an ETA. I know they both said 90 days after Lollipop code release.
But my question is more about if it will even come at all now ? Due to the rocky relationship between OPO + Cyanogen.
Sent from my A0001
Click to expand...
Click to collapse
Yeah but unfortunately the answer remains the same; nobody here knows, we can only speculate. The only people who know are CM, and they won't comment on it. There's the "big" update coming in January but I'm not putting any money on it being 5.0, they haven't even hinted to that.
As with everything when it comes to ROMs/Kernels/OTAs... no one knows and employees don't release release dates because then they'll feel pressured that they'll NEED to have it done.
Would you rather have a rushed release with bugs causing your phone not to work properly? Especially if its a person who does not involve themselves with rooting/flashing?
Or would you rather have a release where it works and is tested thoroughly.
If you can't wait, try a Lollipop ROM. If you want to stay as close to stock as possible, flash CM12.
I am not asking for a specific CM12S release date.
This thread is more about asking if there will even be a CM12S released period, ever ? With all the recent bad press between OPO and Cyanogen. I am worried there might not ever be an official OnePlus One CM12S OS release at all now in a couple months ?
Sent from my A0001
And the answer is still (and always will be) nobody here can answer that.
Transmitted via Bacon
Zorachus said:
I am not asking for a specific CM12S release date.
This thread is more about asking if there will even be a CM12S released period, ever ? With all the recent bad press between OPO and Cyanogen. I am worried there might not ever be an official OnePlus One CM12S OS release at all now in a couple months ?
Sent from my A0001
Click to expand...
Click to collapse
That is specific to the market of India. I'm sure that oneplus and cyanogen have a contract that they need to abide by otherwise therell be lawsuits.
I wouldn't worry about it, I'm sure there will be a cm12s. When? Don't know.
If you can't wait, flash cm12 unofficial. Now if we talk about the oneplus two (or whatever they plan on calling it, I wouldn't be surprised if they did abandon CyanogenMod in favor of their own rom.)
Sent from my Nexus 6 using Tapatalk
zephiK said:
That is specific to the market of India. I'm sure that oneplus and cyanogen have a contract that they need to abide by otherwise therell be lawsuits.
I wouldn't worry about it, I'm sure there will be a cm12s. When? Don't know.
If you can't wait, flash cm12 unofficial. Now if we talk about the oneplus two (or whatever they plan on calling it, I wouldn't be surprised if they did abandon CyanogenMod in favor of their own rom.)
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
For the OnePlus One, you're darn right there will be lawsuits if we don't keep getting CM branded official updates. That was what the phone was marketed as, printed with Cyanogen branding, and I as a customer bought it for. If they abandon CM branded official upgrades, I'd be forced to kick off or join a class action lawsuit against both OnePlus and Cyanogen. I won't tolerate bait and switch.
maybe in february
They are suppose to deliver CM12s in Jan(this month) ..at least at the very end, it's the 90 days they promised us. Feb is too late as it won't be 90 days but more
Don't promise if you can't deliver, also I'd like a pure android experience as a second option, something as pure as it can get(it performs better on benches ..at least their alpha version from what I've seen)
evronetwork said:
They are suppose to deliver CM12s in Jan(this month) ..at least at the very end, it's the 90 days they promised us. Feb is too late as it won't be 90 days but more
Don't promise if you can't deliver, also I'd like a pure android experience as a second option, something as pure as it can get(it performs better on benches ..at least their alpha version from what I've seen)
Click to expand...
Click to collapse
Steve Kondik has said it will be out later next month. Check his Google+ profile. Sorry I can not post a link.
freelancer1988 said:
Steve Kondik has said it will be out later next month. Check his Google+ profile. Sorry I can not post a link.
Click to expand...
Click to collapse
I believe this is the link:
https://plus.google.com/app/basic/stream/z13evbgalmvfdffve220xb2reqilvvbw504
evronetwork said:
Don't promise if you can't deliver, also I'd like a pure android experience as a second option, something as pure as it can get(it performs better on benches ..at least their alpha version from what I've seen)
Click to expand...
Click to collapse
You people and your benchmark scores. Give it up already
Sent from my A0001 using XDA Free mobile app
Mr Patchy Patch said:
You people and your benchmark scores. Give it up already
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I just made a pointless fact(from other people's tests) about that no need to act like that, be polite man ..you should try it next time.
I really don't care about benches, I prefer if it feels smooth-liquid, runs fast and not with 20fps at games and have 1000 points on antutu rather than having a sci-fi 80.000 points and be garbage
Just interested in
Guys can someone describe me difference shortly of CM11 and CM1s. Coz I'm on CM12 Nightly builds on my OPO atm and it's working fairly good.
Qwsazy said:
Guys can someone describe me difference shortly of CM11 and CM1s. Coz I'm on CM12 Nightly builds on my OPO atm and it's working fairly good.
Click to expand...
Click to collapse
There's very little difference except CM11S has the fancy lockscreen and camera. CM11 receives nightly updates whereas CM11S received periodic updates.
Transmitted via Bacon
Yeah it confuses me why people still beg for the same product with an S attached to it as it will make things better for them. This phone is a developer type of phone for people who will try rooting and flashing. With the recent updates in CM getting closer to stable why do we care about an 11s.
Also lets be honest if we do not have all the proper working features in a nightly you cant expect to see a stable release.... At least a 12M or something has to be put out for our phones too me before we say an 12S
@Zorachus - step back and think for a second why are you asking your question. No one associated with giving you an answer will come here and give it to you. You can Google it and see whats out there and draw your own conclusion. I feel this is what others were trying to get across to you. You are asking a question that can't be answered no matter how you slice it up
playya said:
Yeah it confuses me why people still beg for the same product with an S attached to it as it will make things better for them. This phone is a developer type of phone for people who will try rooting and flashing. With the recent updates in CM getting closer to stable why do we care about an 11s.
Also lets be honest if we do not have all the proper working features in a nightly you cant expect to see a stable release.... At least a 12M or something has to be put out for our phones too me before we say an 12S
Click to expand...
Click to collapse
Because for some people it's a matter of principle. CM stated very clearly that this device would receive official updates for two years, if the S branch is dropped they're reneging on that agreement.
Because this isn't strictly a dev phone, this is a developer-friendly phone. Not everyone wants to unlock and root their device, in fact the majority of the user base most likely don't want to. So if support is dropped then those people are left with a device that isn't receiving the updates it was promised to have, those people have a right to expect those updates.
Transmitted via Bacon