Database Develop

6.7.244 ics

And another one leaks. Same deal as 242...Security doesn't allow downgrade to 905 yada blah blah. This is getting old now. We've been on ics leaks since June and no ota in sight. House of Bionic has support for 244 for those who've already jumped to 235+. Those on 232 should continue to wait. At this point those on 232 are pretty much getting as much use out of it as they did 905. Maybe even more so. Lol.
Sent from my Xoom using Tapatalk 2

I think at this rate those of us on the Bionic will see Key Lime Pie out on the Nexus before we see ICS.

It's certainly getting to that point. If this build gets rejected then it's going to be October before we have any hope of seeing ota. Ugh!
Sent from my Xoom using Tapatalk 2

I am not that certain the Bionic will see ICS officially. Maybe there will declare it at EOL and quit.

Reason #2 why I will never, never, never buy another Moto device of any sort. This is totally absurd.

Has nothing to do with Moto. This is 100% on VZW. Moto has put out _9_ builds that VZW has rejected. *9*! That's unheard of. The ONLY issue left to fix is the stupid flash thing which NO moto ICS build works properly with. It's ridiculous but it's not Moto's fault.

Underwater Mike said:
Reason #2 why I will never, never, never buy another Moto device of any sort. This is totally absurd.
Click to expand...
Click to collapse
In the future, Motorola will be offering developer editions of their phones so that is my reason for continuing to remain with them, along with the quality of build typically being superior to the other companies (I say typical, as in not being 100% but for the most part).
With them releasing developer editions, this shouldn't be a problem anymore because it basically will turn all of their future devices into nexus's as far as being able to develop for.
Sent from my DROID BIONIC using Tapatalk 2

smokedkill said:
In the future, Motorola will be offering developer editions of their phones so that is my reason for continuing to remain with them, along with the quality of build typically being superior to the other companies (I say typical, as in not being 100% but for the most part).
With them releasing developer editions, this shouldn't be a problem anymore because it basically will turn all of their future devices into nexus's as far as being able to develop for.
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
And let's not forget the most important aspect. Right in the middle of our ICS update being developed, Google went in and cleaned house at Moto. You can't deny that Moto is going to be a very different company moving forward with Google now owning them and installing an ex-Google ceo as the new Moto ceo. We're already starting to see massive changes and I for one think it's going to get a lot better. I'm on board with a new dev device from Moto as soon as they release the one I want. Samsung lost that bet with me back in July. The Samsung unicorn never materialized. Moto already has the devices up on the unlock page so we're not talking unicorns here. The RAZR M dev phone is up for preorder and I think coming this week. So, let's forget about the old Moto run by an idiot and focus on what direction Google is pointing the ship now.

I agree. I watched their press conference on YouTube and they definitely seemed like a new company. They specifically mentioned people wanting to tinker with their phones and changing things. It's been no secret that google follows the development community, especially considering some of the newer features of android were originally developed by the root community back in the old days of android (2009-2010).
On a side note, did anyone read about how nobody who works at apple actually uses SIRI (at least none of their developers). I found it amusing since I've seen the apple fanboys brag about SIRI. I think google and Android manufacturers should look into suing apple over some of the things they took from Android, such as voice search and folders. If you ask a fanboy, I'm sure they would tell you that android stole those from apple as well, even if we did have them first.
Sent from my DROID BIONIC using Tapatalk 2

smokedkill said:
On a side note, did anyone read about how nobody who works at apple actually uses SIRI (at least none of their developers). I found it amusing since I've seen the apple fanboys brag about SIRI. I think google and Android manufacturers should look into suing apple over some of the things they took from Android, such as voice search and folders. If you ask a fanboy, I'm sure they would tell you that android stole those from apple as well, even if we did have them first.
Click to expand...
Click to collapse
Share a link... I'd love to read about that bit of news.

A curiosity about this release... Some folks (including myself) found out that tethering was borked, even with FoxFi, after a certain leak release version. I'm not sure which one but I know tethering wasn't working for me on .232 and it doesn't work on my install of Liquid ICS 1.5 ROM, but I started from scratch and put .223 back into my non-safe side and FoxFi worked. Any idea if .244 still blocks tethering?
The obvious answer would be "yes" if we follow the logic that some version after .223 blocked it, but I just wanted to make sure

FoxFi hasn't stopped working for me in any of the builds. Still kicking for me in 244, as well.

Its in the article on USA today about a former executive talking about the siri commercials detracting from the product. I believe it made other news outlets also. I'll see if I can find a link.
Sent from my DROID BIONIC using Tapatalk 2
---------- Post added at 07:32 PM ---------- Previous post was at 07:29 PM ----------
Vnvjeep said:
Share a link... I'd love to read about that bit of news.
Click to expand...
Click to collapse
Here is a link. The part about apple employees not using it is near the end.
http://mashable.com/2012/09/10/ex-apple-exec-pull-siri-ads/
Sent from my DROID BIONIC using Tapatalk 2

.244 change log
-the boring 2 has been changed to an awesome 4
-new "chiwawa barking dog" default ringtone
-phone now actually taste like a ice cream sandwich
-leaves breath minty fresh

ROFLMAO! That about sums it up.

Its VZW causing the delay
SamuriHL said:
Has nothing to do with Moto. This is 100% on VZW. Moto has put out _9_ builds that VZW has rejected. *9*! That's unheard of. The ONLY issue left to fix is the stupid flash thing which NO moto ICS build works properly with. It's ridiculous but it's not Moto's fault.
Click to expand...
Click to collapse
I agree, this is 100% VZW. My Motorola Xoom tablet received Android 4.1 back in July, because they did not have to go through VZW to release to the field. The XOOM and Bioinc run the exact same processor.

LMDude said:
I agree, this is 100% VZW. My Motorola Xoom tablet received Android 4.1 back in July, because they did not have to go through VZW to release to the field. The XOOM and Bioinc run the exact same processor.
Click to expand...
Click to collapse
Actually they don't. The Bionic uses an OMAP 4400. Nonetheless, VZW is what's holding up the OTA. Moto has done everything they can do to try to please them. I mean, how do you fix a problem with a plugin that's never going to get another update by the people who made it? It's clear that Adobe would have to fix it on their end not on Moto's. So it's just stupid.

SamuriHL said:
Actually they don't. The Bionic uses an OMAP 4400. Nonetheless, VZW is what's holding up the OTA. Moto has done everything they can do to try to please them. I mean, how do you fix a problem with a plugin that's never going to get another update by the people who made it? It's clear that Adobe would have to fix it on their end not on Moto's. So it's just stupid.
Click to expand...
Click to collapse
I value your opinion SamuriHL so let me ask you this. Is VZW's delay why you have chosen to go down the can never go back path (.235-.244)? I've been sitting idle at .232 and I'm ready to move on. Now with the news that we will get JB OTA at some point should I just wait another month for the ICS OTA or do what you have done down the leaked path. Do you think we'll get JB leaks too? I don't mind making the jump but I have to live with this phone for at least another 14 months and honestly i don't think I'll need to upgrade when the time comes. I'm pretty darn content with the Bionic. I just don't want to go down this road to end up at a dead end. Can we keep going forward?

zoompastu said:
I value your opinion SamuriHL so let me ask you this. Is VZW's delay why you have chosen to go down the can never go back path (.235-.244)? I've been sitting idle at .232 and I'm ready to move on. Now with the news that we will get JB OTA at some point should I just wait another month for the ICS OTA or do what you have done down the leaked path. Do you think we'll get JB leaks too? I don't mind making the jump but I have to live with this phone for at least another 14 months and honestly i don't think I'll need to upgrade when the time comes. I'm pretty darn content with the Bionic. I just don't want to go down this road to end up at a dead end. Can we keep going forward?
Click to expand...
Click to collapse
I can't give you any guarantees. Please understand that point as it's VERY important to what I say next.
I chose to originally go to the 235+ path because at the time I THOUGHT I was within a couple weeks of getting a new Samsung S3 Developer phone (what I now call the Samsung unicorn). However, I also wrote the House of Bionic and knew that I could keep moving forward as new leaks came out. Little did I know there'd be so many to test my code on. LOL! The HoB is pretty rock solid at this point....literally being "tested" by hundreds of users. But the warning about 235+ holds...we can't go back to any builds pre-235. That includes 905 which is a very big deal since all ICS updates ONLY update 905. The HoB will flash what parts of 905 it can (system, preinstall, webtop) and then the boot img of the update you're trying to install which allows us to move forward. And in fact allows us to move down, as well. Just no further down than 235. I bring that up for a reason. A lot of us have gone to 244 and we like it. A lot. But should VZW decide to OTA 242, as an example, those of us that have moved forward would be screwed without the ability to move back to 242 to get back on the OTA path. The HoB can do that for us. So I'm not personally concerned with my own phone getting back to the OTA path. Once we get a new ICS FXZ we'll be fine regardless. My warnings are for people that haven't been as blessed as I have to learn from some of the best people in our community. I like to make sure that others have options. Which is why I recommend the majority of people stick with 232. Unless you know the risks, and understand what the process does to your phone to move from one update to another (hint...it involves soft bricking until the update you're trying to install is successfully applied....not for the faint of heart since there's no FXZ safety net to fall back on should something go wrong), then 232 is the "safest" place to be. It gives you ICS but gives you the option of FXZ'ing back to 905 and taking the OTA should you need to go that route. Those on 235+ have only one option available to them...And that is the process I outlined that Matt Groff gave to us for moving between updates. I'm confident enough in the code and method that I believe it'll work. Now, go read the very first line of this post again, cause it's an important point to understand.

SamuriHL said:
I can't give you any guarantees. Please understand that point as it's VERY important to what I say next.
I chose to originally go to the 235+ path because at the time I THOUGHT I was within a couple weeks of getting a new Samsung S3 Developer phone (what I now call the Samsung unicorn). However, I also wrote the House of Bionic and knew that I could keep moving forward as new leaks came out. Little did I know there'd be so many to test my code on. LOL! The HoB is pretty rock solid at this point....literally being "tested" by hundreds of users. But the warning about 235+ holds...we can't go back to any builds pre-235. That includes 905 which is a very big deal since all ICS updates ONLY update 905. The HoB will flash what parts of 905 it can (system, preinstall, webtop) and then the boot img of the update you're trying to install which allows us to move forward. And in fact allows us to move down, as well. Just no further down than 235. I bring that up for a reason. A lot of us have gone to 244 and we like it. A lot. But should VZW decide to OTA 242, as an example, those of us that have moved forward would be screwed without the ability to move back to 242 to get back on the OTA path. The HoB can do that for us. So I'm not personally concerned with my own phone getting back to the OTA path. Once we get a new ICS FXZ we'll be fine regardless. My warnings are for people that haven't been as blessed as I have to learn from some of the best people in our community. I like to make sure that others have options. Which is why I recommend the majority of people stick with 232. Unless you know the risks, and understand what the process does to your phone to move from one update to another (hint...it involves soft bricking until the update you're trying to install is successfully applied....not for the faint of heart since there's no FXZ safety net to fall back on should something go wrong), then 232 is the "safest" place to be. It gives you ICS but gives you the option of FXZ'ing back to 905 and taking the OTA should you need to go that route. Those on 235+ have only one option available to them...And that is the process I outlined that Matt Groff gave to us for moving between updates. I'm confident enough in the code and method that I believe it'll work. Now, go read the very first line of this post again, cause it's an important point to understand.
Click to expand...
Click to collapse
I understand completely. One thing I just learned was If lets say .244 (or .242 as you used as an example) is the OTA release then we are back on the path as long as our version matches the current verizon version. Or did I totally miss interput that. HoB script is Awesome and is what I've used for moving from .2233-.232 and I fully trust myself to use these tools properly to move forward. Sounds like you're in the know of where to locate updates and are a reliable member of the Bionic XDA Community. Since there MAY be a way for us to move forward I think I'll take the plunge this weekend when I have some down time. Thank You

Why am I not getting the lollipop update ota yet?

Hi guys
Sorry if this is a dumb question. I have a totally stock 2012 nexus 7 on 4.4.4. It's wireless not 3g and I'm in the UK.
If I check for updates it says I'm up to date. I'm not rooted and running stock android. It had never been tampered with in any way.
Am I missing something?!
Cheers!
Robsa.

Because it has not been pushed yet.

Note10.1Dude said:
Because it has not been pushed yet.
Click to expand...
Click to collapse
Really surprised it hasn't been pushed yet, even though the factory image and the OTA image are our there already.

An, OK! Many thanks. I take it they pulled the first lollipop release then?
Sent from my Nexus 7 using XDA Free mobile app

As far as we can tell, and other complaints in other forums seem to confirm, they stopped pushing the update to Nexus 7. Why? We can only speculate. The ways of the Great Google are Mysterious. We are mere children and should not question the Great Google in His Infinite Wisdom.

If Google pulled off the update to fix performance issues some people have been reporting, I'm completely ok with that.

Know it took my wife's N7 2013 quite awhile to update to lolli. Think it was just a few days ago. Just have to be patient as it will come.

D_wolf said:
If Google pulled off the update to fix performance issues some people have been reporting, I'm completely ok with that.
Click to expand...
Click to collapse
I totally agree.

Are you really in THAT big of a hurry to turn your Nexus into a useless piece of garbage? Because that's what will happen after you put 5.0 on it. Hopefully the 5.0.2 image they pushed today will resolve the performance issues.

Pushed to who? Nexus 7 2012?

iolinux333 said:
Pushed to who? Nexus 7 2012?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2978329
Sent from my XT1060 using Tapatalk

The 5.0.2 update definitely fixes the performance issues from the initial update to 5.0. Happy with the performance I'm getting. Pretty much the same as what I was getting under KK, which wasn't bad at all.
Initial boot into 5.0.2 might seems slow and laggy, but give it a few hours and it definitely clears up. That's with a clean update.
I didn't get the OTA. I just went to the Google images site and downloaded the official Google image and flashed it. I never got the LP OTA pushed to my device for whatever reason.

Agreed, 5.0.2 seems to have fixed the performance issues I was having.
Sent from my XT1060 using Tapatalk

Wade-0,
Although "push" is a misnomer given how the tech actually works, in common parlance, available for download and manual installation is typically not considered a push. Just sayin.

iolinux333 said:
Wade-0,
Although "push" is a misnomer given how the tech actually works, in common parlance, available for download and manual installation is typically not considered a push. Just sayin.
Click to expand...
Click to collapse
Considering I used the same terminology from the XDA homepage posting on the topic, maybe you should lighten up there skippy.
http://www.xda-developers.com/android/android-5-0-2-factory-images-nexus-7-wifi/
"Android 5.0.2 has just been pushed into Google’s AOSP repos."

The 4.4.4>5.0 OTA is probably cancelled due to the known reasons.
The 5.0>5.0.2 OTA for the affected people on 5.0 is rolling out, check the other thread for the link.
They will probly wait to see if 5.0.2 fixes the stuff and add some OTA from 4.4.4 to 5.0.2.

Confused - Root and Revert back to 5.0.2

I am not having an easy time finding a clear cut way to root my phone. I know that since 5.1.1 came out like 2-3 weeks ago that I need to be on 5.0.2. So I need to know how to revert back to that. And then I also know that you need to do some weird **** from what I am used to to just simply root our phones. Something with the OE2 to OF3 and some other things related to that. Really weird to me when I am used to more or less pressing a button and I am rooted...... This being said I need to know how to root my phone too. And if it is possible to root 5.1.1 then those instructions would be preferred(saying it is stable/tested/etc.
I ultimately want to be able to use either XtreStoLite ROMs. Preferably the Odex Pure Edition though but from what I've read when you do the 5.0.2 version there was some call audio problems...which is no good for a phone lol.
Last phone I really tried to do **** with was the HTC Aria. Had an S3 for awhile but didn't feel like doing anything with it since it was so old at the time I received it(almost 2 years ago now)
/startrant
I feel like XDA is way more confusing than it used to be. Either that or the community for the S6 isn't the best from other phones I've used, personally. This new UI for XDA is also weird to me as well(doubt it is very new though).
Used to seeing a clear cut:
How To Root thread(s)
List of Custom Roms thread(s)
other useful threads that make going around the phones forum so much easier than having to use the search engine.
it definitely doesn't help that more or less all other versions of the phone work with each other easily vs ATT being ****ing douchebags and can't even just release the current OS right when literally every other company does.
Conclusion.... **** ATT... Long ago I wanted to go to verizon but wasn't in a position to but figured at this point in time(3-4 years later, maybe more) that things might have changed. **** ATT
/endrant

arokace said:
<lots of complaining>
Click to expand...
Click to collapse
There is no way to root your phone, the bootloader is signed we don't have the keys.
In addition it would behoove you greatly if you learned to both search and to be knowledgeable as to what your 'one click' solutions do. Without knowing what your clicking you'll find it hard to fix when things go wrong.
In short though your SoL here, unless your phone is on an exceptionally early build you can't root, and I doubt it's on that early of a build unless you made an effort to keep it from updating and bought the phone close to launch.
Sent from my SAMSUNG-SM-G920A using Tapatalk

OP asked about reverting to 5.0.2, so it's pretty safe to assume he's on 5.1.1.
OP - at this point, as posted above, all you can do is wait and hope. There is no way to revert to a rootable build from 5.1.1, nor root 5.1.1, on an ATT branded device, at this time. If you are committed to wanting root and custom ROMs, don't buy any AT&T or VZW branded devices, and don't buy devices that are running anything other than mainstream processors. Nexus is your friend. Or revert back to your Aria - I'm still using mine, running CM11, as a media player.
Sent from my SAMSUNG-SM-G920A using Tapatalk

I know 5.1.1 can't be rooted but I thought 5.0.2 can be. But from the sounds of it once I have 5.1.1 installed then my bootloader is changed? And reverting back doesn't change the loader? Oh, after reading the last part of the 1st reply. It sounds like all those people that say they've rooted there 5.0.2 version was just because they purchased at launch?
As for understanding the 'one click' solutions. At the times I did know what they did. The forums for the phone(s) I was using at the time were a lot more neat and straightforward(this is apparently one word, didn't know...) to understand. Like I said, this new layout of XDA(it is new to me even if it might be 2 years old or something) isn't as nice/useful personally. And as for searching, I do but once again the searches are different than how other forums do searches. Or maybe it is just the cluttered feeling I get from the S6 forums maybe. Not sure.
P.S.(_Dennis_) No **** it is a lot of complaining...granted I basically got the phone for free because of how AT&T does there plans and ****...this still makes me hate AT&T even more than I used to...at least with my older phones there was hope for someone to make ROMs/Roots/etc for the phone, just took longer because AT&T rides the short bus... So yes I will complain. But I still genuinely had questions I wanted answers. I know you had to read what I wrote but you didn't take it in I guess. Because the only way I would have some of that info is if I was searching. I just didn't know about only the launch models basically can be rooted and no others. Which is why I was asking about reverting to 5.0.2
I will thank you both for actually posting and answering my questions though. Versus in the normal S6 forum people just completely ignored me. So I do appreciate you guys answering me.

WARNING: PingPong Root Users Do NOT Update to 5.1.1

I have gotten a few private messages plus some people have posted on the threads with the updates.
Do NOT update to 5.1.1 if you want to maintain root.
After days of tinkering, here are your possible outcomes (none of which are what you want):
A. Continuous soft reboot after upgrading via FlashFire updates.
B. Use ODIN to flash the system/boot partitions or properly done FlashFire update... Hoorah! You're on 5.1.1, but your fingerprint sensor and LTE are dead - plus no root.
C. You try to downgrade after B, and you no longer have signal under any circumstance.
Personally, I am now just going to flash the OI2 ODIN files in full and be done with it until a new root method is available. Sorry guys, I have tried everything that I can think of. As you can see above that something in the 5.1.1 kernel/system images require the latest bootloader which is what allows us to downgrade and get root from OE2 using PingPong.
There is a possibility of a new solution soon enough... see progress here for other models of S6: UniKernel

Yeah I ended up tripping knox in my attempts at working something out. Fortunately I was able to revert but thats only because I didn't dare try and flash the bootloader or modem. Man this is like a sick mind-game. I wish I would have had more experience with Samsung and AT&T before I bought this damn phone. This is my first phone on AT&T and my first Samsung. It was the perfect **** storm... I never anticipated this bull****, after this long... And I can't even get rid of the damn thing. Nobody wants it.

wesgarner said:
I have gotten a few private messages plus some people have posted on the threads with the updates.
Do NOT update to 5.1.1 if you want to maintain root.
After days of tinkering, here are your possible outcomes (none of which are what you want):
A. Continuous soft reboot after upgrading via FlashFire updates.
B. Use ODIN to flash the system/boot partitions or properly done FlashFire update... Hoorah! You're on 5.1.1, but your fingerprint sensor and LTE are dead - plus no root.
C. You try to downgrade after B, and you no longer have signal under any circumstance.
Personally, I am now just going to flash the OI2 ODIN files in full and be done with it until a new root method is available. Sorry guys, I have tried everything that I can think of. As you can see above that something in the 5.1.1 kernel/system images require the latest bootloader which is what allows us to downgrade and get root from OE2 using PingPong.
There is a possibility of a new solution soon enough... see progress here for other models of S6: UniKernel
Click to expand...
Click to collapse
Forgive my ignorance here...I've not kept close track of the progress of unikernel. But it was my impression that without a custom recovery option, we are entirely SOL regarding custom kernels. Am I misunderstanding things, or did something change? I didn't see anything in the recent posts there that got my hopes up...
Sent from my SAMSUNG-SM-G920A using Tapatalk

Well technically you can flash the kernel using FlashFire however a screen will stop you from booting.. Says something about at&t detecting modified software on your device please take to repair center blah blah

timde9 said:
Well technically you can flash the kernel using FlashFire however a screen will stop you from booting.. Says something about at&t detecting modified software on your device please take to repair center blah blah
Click to expand...
Click to collapse
Lol. Well not bootable is not useful! ?
Sent from my SAMSUNG-SM-G920A using Tapatalk

Gah! I don't even use custom roms. Stupid Textra App has this ****ty ghost notification that does not work on 5.0.x android. I would go to 5.1 unrooted but I just can't stand the thought of not being able to get rid of annoying notifications (wifi, etc). Plus all the custom easy hacks. So lame. Never going AT&T again. Why do they make it so difficult anyways? Tmobile doesn't.

They make the majority of their money from enterprise customers. These customers desire the locked bootloader as to avoid security risks. Since this is AT&T's main source of profit this is their main consideration. In short this phone and its software was not designed with our consumer use cases in mind. We are merely an after thought. I have waited too long I am jumping ship, just ordered a Moto X Pure and as soon as it gets here I am leaving this phone behind. Had it since launch and haven't been able to accomplish my original intention since then. Never buying from AT&T and also I am staying far away from anything with an Exynos chipset. Touch Wiz is a lag fest nightmare. For this to be pretty much the most powerful chip in the mobile space and to experience such a lag on it is truly unnerving. Samsung is all too eager to jump the Android band wagon all together and probably intend to do so as soon as they feel their tizen offerings stack up. And I sincerely hope they fail miserably. They are a good hardware company but they should just give up on software. They just don't get it at all.

timde9 said:
Yeah I ended up tripping knox in my attempts at working something out. Fortunately I was able to revert but thats only because I didn't dare try and flash the bootloader or modem. Man this is like a sick mind-game. I wish I would have had more experience with Samsung and AT&T before I bought this damn phone. This is my first phone on AT&T and my first Samsung. It was the perfect **** storm... I never anticipated this bull****, after this long... And I can't even get rid of the damn thing. Nobody wants it.
Click to expand...
Click to collapse
Amen. Well said. Bravo.... I feel your pain. My first real SmartPhone was the Fire Phone with AT&T, exactly a year ago, and I took its enema for 10+ months before I finally decided to just add payments for the S6 and finally have a good phone I could root. So now I'm paying for both, and the more I search for help and answers on here, the more I feel like my kind aren't welcome. Not by the community, but by ATT and Samsung. Gee thanks.
Well, at least I have a new phone... I'm totally down to build and burn a 5.1.1 effigy with you, if you want.

Well I have already given up on this phone. See my post above. My sister has already agreed to take over the line and the phone payment and I just bought a Moto X Pure outright yesterday. Just waiting for it to arrive now.

I've been thinking of just doing an Odin back to stock (unrooted) and OTA update up to the newest 5.1.1 on my 925a for a week or so now. For anyone that is already on OI2, how is it working out for you? Is the phone still slow at times? Does the memory issues still exist?
I recall seeing an app a little while ago that is able to freeze/disable apps without root. What was that app? Has anyone tried doing something like this? How did it work out?

sirdizzle415 said:
I've been thinking of just doing an Odin back to stock (unrooted) and OTA update up to the newest 5.1.1 on my 925a for a week or so now. For anyone that is already on OI2, how is it working out for you? Is the phone still slow at times? Does the memory issues still exist?
I recall seeing an app a little while ago that is able to freeze/disable apps without root. What was that app? Has anyone tried doing something like this? How did it work out?
Click to expand...
Click to collapse
Package disabler. Works like a charm.

anneoneamouse said:
Package disabler. Works like a charm.
Click to expand...
Click to collapse
Thanks! Is it the "for Samsung" one? or do you have another one in mind?
How is OI2 working out for you?

Don't have oi2, I have an s6 active, no update yet.

Still on Oct Security Patch

Hey All,
When I bought my N6 in September, it was already enrolled in the Preview program. I got 7.0 immediately after release... but I have yet to receive any of the security patches.
I know, I can find the factory images and such and flash, but this is the first device in 14+ years (going back to the Toshiba e800) that I haven't tinkered with... yet. Google is supposed to keep OTA'ing them for another year or two, is my understanding
So, just wondering, anyone else still stuck on 10/16 security patch?

cameraddict said:
Hey All,
When I bought my N6 in September, it was already enrolled in the Preview program. I got 7.0 immediately after release... but I have yet to receive any of the security patches.
I know, I can find the factory images and such and flash, but this is the first device in 14+ years (going back to the Toshiba e800) that I haven't tinkered with... yet. Google is supposed to keep OTA'ing them for another year or two, is my understanding
So, just wondering, anyone else still stuck on 10/16 security patch?
Click to expand...
Click to collapse
Umm no. The nexus 6 is EOL. The only thing you ma get is security patches but as you can see those are not always available. If you want to stay up to date you will need to flash the image.

zelendel said:
Umm no. The nexus 6 is EOL. The only thing you ma get is security patches but as you can see those are not always available. If you want to stay up to date you will need to flash the image.
Click to expand...
Click to collapse
I know that. And that is what I said. I know I can flash the images... I'm asking if anyone else is still stuck on the Oct patch through the OTA system. Google supposedly promises them for another year past EOL.

cameraddict said:
I know that. And that is what I said. I know I can flash the images... I'm asking if anyone else is still stuck on the Oct patch through the OTA system. Google supposedly promises them for another year past EOL.
Click to expand...
Click to collapse
I know a few people that have never even gotten a single OTA the entire time they have owned the device. Yet they are not worried about it. Most of the security updates are a joke really.

zelendel said:
I know a few people that have never even gotten a single OTA the entire time they have owned the device. Yet they are not worried about it. Most of the security updates are a joke really.
Click to expand...
Click to collapse
I mean absolutely no offense, but your answers aren't very helpful. Perhaps some people could care less about the OTAs, but I do- and I'm sure that I am far from the only one. As to their efficacy, I'd rather have an official security patch than not.

cameraddict said:
I mean absolutely no offense, but your answers aren't very helpful. Perhaps some people could care less about the OTAs, but I do- and I'm sure that I am far from the only one. As to their efficacy, I'd rather have an official security patch than not.
Click to expand...
Click to collapse
Then by all means flash the update. OTA have always been touchy. I have been sitting right next to someone else when they got an OTA to the same device and I never saw it.
That is why we here at XDA long ago gave up on OTA and advise people to do it for themselves if they have the ability (nexus users).
No offense taken at all. Been around to long to take offense to things posted on the interwebs