Database Info

KitKat?

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

CM has pretty poor update waiting times.

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...

[Q] Custom ROM

As many us experienced, the OPO seems to be riddled with issues.
My biggest issues are:
-Multi-touch
-Ghost touch/Typing issues
-Camera. Often says it is not connected.
OPO has said the Multi-touch and touchscreen related issues are software. I was wondering if any custom ROM as already figured out the solution. Not being able to type quickly and correftly is extremely aggravating.

I know the issues with ghosting. It's really annoying. I've just slowed down my typing speed but it still gets annoying. It's likely a software thing. The camera issue is the camera driver failing to start. Happened on my lg g2 however the kernel dev added a button to his app that restarted the camera driver. I get the error when I use snapchat a lot. Besides those I'm really liking this phone!
Sent from my A0001 using Tapatalk

osmosizzz said:
I know the issues with ghosting. It's really annoying. I've just slowed down my typing speed but it still gets annoying. It's likely a software thing. The camera issue is the camera driver failing to start. Happened on my lg g2 however the kernel dev added a button to his app that restarted the camera driver. I get the error when I use snapchat a lot. Besides those I'm really liking this phone!
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Have you tried any custom ROMs? Found any solutions? Seems to be getting worse.. Really sucks.

The only way you're going to find out is to flash a ROM for yourself. Make a backup first, that way if you need to go back out only takes a couple of minutes to restore it.
Transmitted via Bacon

Well I am pretty sure Camera issue is due to incorrect GApps installed (if you are on custom ROM), for me I have moved from CM to PA to Mahdi and never had any issues. In terms of typing issues there was a fix made on Mahdi (from CM commit I guess) and it has improved but no 100% gone yet. But as far I know it should be fixed relatively soon with CM update (big one) pending. Apart for multi touch i find the phone pretty nice actually Just my $.02

cd69 said:
Well I am pretty sure Camera issue is due to incorrect GApps installed (if you are on custom ROM), for me I have moved from CM to PA to Mahdi and never had any issues. In terms of typing issues there was a fix made on Mahdi (from CM commit I guess) and it has improved but no 100% gone yet. But as far I know it should be fixed relatively soon with CM update (big one) pending. Apart for multi touch i find the phone pretty nice actually Just my $.02
Click to expand...
Click to collapse
I've heard good things about Mahdi. Now seriously considering!
Is there an eta on the next cm update?

You_got_owned123 said:
I've heard good things about Mahdi. Now seriously considering!
Is there an eta on the next cm update?
Click to expand...
Click to collapse
They don't ever give ETA's, just like any other dev, and it's rude to ask them.
Transmitted via Bacon

timmaaa said:
They don't ever give ETA's, just like any other dev, and it's rude to ask them.
Transmitted via Bacon
Click to expand...
Click to collapse
Awe bummer.. No time line for my suffering.
Although I agree with not asking for eta when it comes to a freelance developer, I do think this is different as they are no longer a developer that does it for their leisure and pleasure, but cm now does it for a profit, profit that comes from our pockets as we pay for the phone. So in my opinion, we have a semi right to know when what we're paying for, will be fixed
Not trying to argue. I agree it's rude to ask other developers for eta

You_got_owned123 said:
Awe bummer.. No time line for my suffering.
Although I agree with not asking for eta when it comes to a freelance developer, I do think this is different as they are no longer a developer that does it for their leisure and pleasure, but cm now does it for a profit, profit that comes from our pockets as we pay for the phone. So in my opinion, we have a semi right to know when what we're paying for, will be fixed
Not trying to argue. I agree it's rude to ask other developers for eta
Click to expand...
Click to collapse
True, although we never get eta for updates from samsung, lg, HTC or really even Google for that matter. Lol.
Sent from my SM-N900T using Tapatalk

drmacrofish said:
True, although we never get eta for updates from samsung, lg, HTC or really even Google for that matter. Lol.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I think we've given up on them haha

[CM] won't officially support!

CM is not too keen on Bumping their nightlies etc.....
http://review.cyanogenmod.org/#/c/76552
thecubed's response
thecubed said:
Hi there, Let's be a bit careful about calling Cyanogen stupid here for this. I'll be 100% honest and say I understand their apprehension to having a device (their buildboxes) make external calls to a web service they don't control.
Can't say I blame them for saying no, either.
That said, it does indeed look like for the time being there will only be Unofficial builds available, which isn't a big deal. I'm happy to set up nightlies on my buildboxes too.
I'm hoping @invisiblek hasn't abandoned the project either, as he's extremely talented when it comes to getting this stuff working.
Click to expand...
Click to collapse

Wow..

Not gonna go read the entire Bump! thread right now, but wasn't Codefire thinking of making the process (meaning, I guess, the code) available to developers so they could bump locally?

Hi guys, let's not go off and freak out over this. Discussion is still ongoing, and even if CM doesn't decide to officially build for this phone, we still can have builds done externally by anyone who wants to do so.
Bump has an API that anyone can use as long as they have an account, so there's no reason to be upset.
Keep calm and carry on

Darn that's a bit disappointing. But I'm perfectly fine with anything; official or unofficial as long as it works.

I hope to build Pac for d850 soon! Sucks cm takes this kind of approach to it.

4ndroid99 said:
Darn that's a bit disappointing. But I'm perfectly fine with anything; official or unofficial as long as it works.
Click to expand...
Click to collapse
Yup. The same way I feel. If it works, I don't care if its unofficial.

objektive_1 said:
CM is not too keen on Bumping their nightlies etc.....
http://review.cyanogenmod.org/#/c/76552
thecubed's response
Click to expand...
Click to collapse
What I think is retarded is that Brint has no reason for not doing it. He's literally being a nazi-like figure just blocking it because he doesn't like it. I'm sorry, how does this make any sense? The worst that would happen is that the bump service (external site) goes down and the build fails. Brint, get over your ego...
CM keeps going down hill with stupid mistakes (like this). First with the One+ One; you gotta be invited to buy a phone? wtf? The hardware is already second grade at this point, who wants a One+ now when you get an N6?

I'll be happy with a solid AOKP rom or a pure Google Lollipop build with xposed/gravitybox

I'll wait to see how this plays out. Hopefully CM will become comfortable with the bump process. I can understand the initial hesitation since it requires something that they cannot control. If they end up not supporting it, honestly it will be CMs loss. The G3 is a very popular phone and there will be plenty of ROM choices out there. So if CM doesn't support it, I'll still have lots of options (and I'm sure someone will unofficially support it too).

Yeah that's really a load of crap especially seeing how Dan already had the script ready to autobump. It's not like it's really that much more work on cyanogenmods part or was Brent just too pansy to have a call out to another server.
I guess we will all have to annoyingly go download and update manually from the forums unless lg actually decides to release a legit boot unlock.

Yeah, I don't really get it!

Hmm, so it seems there be some sort of process they can use still. Keep your hopes up guys

Care to elaborate?

Regardless we will have unofficial with the devs (probably timmytim)pulling commits and upgrading it just as good.
2SHAYNEZ

This is now false.
Sent from my LG-D850 using XDA Free mobile app

There is now offical support and an offical nightly.
cm11

IEatKittys! said:
There is now offical support and an offical nightly.
cm11
Click to expand...
Click to collapse
I know that now. :victory::victory::victory::victory:
Anyone using it? Thoughts?

objektive_1 said:
I know that now. :victory::victory::victory::victory:
Anyone using it? Thoughts?
Click to expand...
Click to collapse
Ive been using it all day. And so far so good. Battery life has been better than expected

IEatKittys! said:
Ive been using it all day. And so far so good. Battery life has been better than expected
Click to expand...
Click to collapse
Running it right now.

Official Nougat 7.0 soak test starts in Brazil

Motorola has finally started the Nougat soak test in Brazil. Let's hope it won't take too long for them to release the final version. However, the screenshots say it's Android 7.0 and not 7.1. Also, to make us believe it's really happening, we can have a look at the comments posted below the post. Few comments say they have received it and it's working smooth as of now.
Source: http://www.androidpit.com.br/teste-nougat-moto-x-force-e-style-comecarao-em-breve
Update 1: Motorola send out soak test invitations to US users
Update 2: Android Headlines reports Moto X Style Is Receiving Android 7.0 Nougat In India
Update 3: Moto X Style and X Pure Nougat update spotted on GFXBench (Yes, again. The last time it was spotted on 7.1 was in last week of December.)
Update 4: A user on reddit who is located near Chicago states he received the Nougat update.

Soak test is going on in India also.

This is a good news !!!!!!

soak test is only available for limited users and if anyone who will break their rules will be out of the soak test permanently so don't expect that someone might just end up sharing the files !! all we need to do is just wait for that moment when it gets as stable as a daily driver and we all are good to go
its most likely 7.0 but i hope we get a 7.1.1 or 7.1.2

Why not get it now?
Google "AICP clark"
I've been running it since Dec 2015 on Republic Wireless with no problems.

I got bored waiting for official nougat and went to AICP 7.1
It's pretty good, can't see myself going back to stock tbh

Put me down for Dirty Unicorns. Last things for me were camera functioning well (which it seems to be if using OpenCamera) and torch working well (which it seems to be improved).

Sagar_1401 said:
its most likely 7.0 but i hope we get a 7.1.1 or 7.1.2
Click to expand...
Click to collapse
no chance for that

iks8 said:
no chance for that
Click to expand...
Click to collapse
Doesn't matter so much. We're interested in the N blobs, i think they are the same between 7.0 and 7.1. this will at least mean better custom ROMS

josdehaes said:
Doesn't matter so much. We're interested in the N blobs, i think they are the same between 7.0 and 7.1. this will at least mean better custom ROMS
Click to expand...
Click to collapse
Even on this forum not everyone is interested with custom roms. I used to mod my phones a lot but thoose were crapy low end devices and custom roms were really adding some performance but with this phone I don't see a reason to install custom rom. Even on my old moto e I went back to stock after trying few roms, moto software is really well made imo, so it's sad that their updates are way slower than they used to be and that they relase already obsolete software ;\.
btw from my expierience there is always something broken in custom roms, and if it's not broken now it will be in next relase xd

iks8 said:
Even on this forum not everyone is interested with custom roms. I used to mod my phones a lot but thoose were crapy low end devices and custom roms were really adding some performance but with this phone I don't see a reason to install custom rom. Even on my old moto e I went back to stock after trying few roms, moto software is really well made imo, so it's sad that their updates are way slower than they used to be and that they relase already obsolete software ;\.
btw from my expierience there is always something broken in custom roms, and if it's not broken now it will be in next relase xd
Click to expand...
Click to collapse
I'm with you here. I have no desire leave the stock ROM for any reason other than updates. It's been bug-free and smooth sailing for me with Motorola's software ever since 2015, no doubt because they stick to AOSP.
The only way I'd be interested in a custom ROM is if the developers were on a very long release cycle where they spent months ironing out every tiny bug before tinkering with new things, similar to how OEMs approach stock ROMs. That seems rare these days, though I don't follow things too closely anymore. "Man this ROM is amazing... except, oh yeah, Bluetooth breaks and requires a reboot... oh, and calls drop a lot... and, uh, call volume randomly goes to max/silent for no reason... oh yeah, and MMS just doesn't show up sometimes, and the camera crashes every 3rd open requiring another reboot" seems to be the way of the world, and I don't have patience for it. Putting up with random bugs can be worth it if it frees you from TouchWiz or Sense or LG UI, but when the stock ROM is already AOSP and fast/fluid, I don't see the point.

http://www.androidauthority.com/moto-x-style-pure-edition-nougat-758023/

I have to agree that stock rooted ROMs are my way of going now. Of course that also means I won't buy from makes like Samsung who overburden their ROMs with too much frill. Besides, with manufactures like one plus, the is really no reason to revert.

good news

ptn107 said:
Google "AICP clark"
I've been running it since Dec 2015 on Republic Wireless with no problems.
Click to expand...
Click to collapse
I'm on RW too. Are you using a certain version that's working good? I just don't wanna messed up my service, but would love to try 7.1.1.
Sent from my SM-P600 using XDA-Developers Legacy app

Official Android 7.0 Nougat out for Moto X Style (Pure) in India and Brazil
AsquareX said:
Motorola has finally started the Nougat soak test in Brazil. Let's hope it won't take too long for them to release the final version. However, the screenshots say it's Android 7.0 and not 7.1. Also, to make us believe it's really happening, we can have a look at the comments posted below the post. Few comments say they have received it and it's working smooth as of now.
Saw the same on another website this morning. I wonder how long after the soak test that it will be released in the US?
Click to expand...
Click to collapse

About time. I see that the Android O developer preview is out and we don't even have 7.0 yet. Grrr!

strafer69 said:
About time.
Click to expand...
Click to collapse
not really, it's way too late imo. Start of soak test doesn't mean a lot, I guess in some regions you will have to wait like more than month since now, I guess everyone willl get it in may as it was said before, that's way too long for not so old flagship phone... We should have 7.0 already and 7.1 in may but it's not going to happen ;\ shame on you moto

iks8 said:
not really, it's way too late imo. Start of soak test doesn't mean a lot, I guess in some regions you will have to wait like more than month since now, I guess everyone willl get it in may as it was said before, that's way too long for not so old flagship phone... We should have 7.0 already and 7.1 in may but it's not going to happen ;\ shame on you moto
Click to expand...
Click to collapse
Not Moto's fault. Blame it all on Lenovo, as the Moto's work force is pretty much non-existent.

Rmsalt said:
AsquareX said:
Saw the same on another website this morning. I wonder how long after the soak test that it will be released in the US?
Click to expand...
Click to collapse
Honestly, a while... It usually goes Brazil, India, Europe, then US and UK (sometimes US/UK flip-flop). To be honest, Lenovo doesn't see the US as a major market, these phones are not carrier subsidized so their market penetration is minimal at best. US is always the last to get Moto (Lenovo) updates in the last 12-18 months. Not likely to see that change anytime soon. Each region will have it's own beta if history repeats, we are at minimum 2-3 months out in the US.
Click to expand...
Click to collapse