Database Develop

Simple Trick to Force the 4.4.2 OTA

So this is a well-known trick that has worked since the N4 but I wanted to share it anyway. If you go to check for the update and it still says up to date, try this method as it has just worked for my N5 and my N7:
Settings>Apps>All Tab>Google Services Framework>Clear Data>Go back to check update and it should work, if not try the steps again.
Like I said, this has worked for my previous N4, N5, and N7(2013). Each time, I tried the check update button alone at least 5 times in a row with no luck, then trying the trick and checking it worked for each device.
Oh and BTW, this trick if done EXACTLY like this DOES NOT invalidate the tokens like some claim. My play store and GMAIL are completely fine on both devices.
PS: Do this at your own risk/if your new to Android (Butthurt syndrome cured)

A Google employee also explained why you should not do this: http://www.reddit.com/r/Android/com...ear_data_for_google_service_framework/cdiymrp

Oh no you didn't.

myorks1127 said:
So this is a well-known trick that has worked since the N4 but I wanted to share it anyway. If you go to check for the update and it still says up to date, try this method as it has just worked for my N5 and my N7:
Settings>Apps>All Tab>Google Services Framework>Clear Data>Go back to check update and it should work, if not try the steps again.
Like I said, this has worked for my previous N4, N5, and N7(2013). Each time, I tried the check update button alone at least 5 times in a row with no luck, then trying the trick and checking it worked for each device.
Oh and BTW, this trick if done EXACTLY like this DOES NOT invalidate the tokens like some claim. My play store and GMAIL are completely fine on both devices.
Click to expand...
Click to collapse
You're wrong, you shouldn't do that. A quick Google will tell you why

bozzykid said:
A Google employee also explained why you should not do this: http://www.reddit.com/r/Android/com...ear_data_for_google_service_framework/cdiymrp
Click to expand...
Click to collapse
I read that post before and have yet to find a single issue with my devices and never had an issue for my N4 when I did it so I don't see what the big deal is...there is another very similar method that does indeed mess up the tokens but it IS NOT the same by any means.
Please prove me wrong, I will check anything on my phone that you think isn't working now because I did this the quick and easy way instead of wasting my time sideloading...

myorks1127 said:
I read that post before and have yet to find a single issue with my devices and never had an issue for my N4 when I did it so I don't see what the big deal is...there is another very similar method that does indeed mess up the tokens but it IS NOT the same by any means.
Please prove me wrong, I will check anything on my phone that you think isn't working now because I did this the quick and easy way instead of wasting my time sideloading...
Click to expand...
Click to collapse
i'm going to go out on a limb and guess that you don't work for Google, specifically the Android/Mobile division. but since you don't see what the big deal is (going against what a Google engineer says) we should all believe you.
this may not mess up your phone, but it wrecks havoc on the back end of Google's servers... when a Google engineer tells us all not to do something, then thoroughly explains why, it's probably best to heed his advice.

Tried this, took five data clears and it gave me the update. Thanks!
Sent from my Nexus 5 using xda app-developers app

Lucke said:
i'm going to go out on a limb and guess that you don't work for Google, specifically the Android/Mobile division. but since you don't see what the big deal is (going against what a Google engineer says) we should all believe you.
this may not mess up your phone, but it wrecks havoc on the back end of Google's servers... when a Google engineer tells us all not to do something, then thoroughly explains why, it's probably best to heed his advice.
Click to expand...
Click to collapse
It doesn't wreak havok on my end so why would I care?

I'll go out on a limb and say if it caused that much grief for Google the clear data feature would have been gone a long time ago.

Its worked since the nexus s btw
Sent from my Nexus 5 using xda app-developers app
---------- Post added at 06:02 PM ---------- Previous post was at 06:01 PM ----------
I've done it with every update since ICS and never had an issue...and its always worked
Sent from my Nexus 5 using xda app-developers app

Glad I finally have some people backing me up lol, my brother is an engineer for Amazon and he thinks he knows everything too...

And this is how people who don't know better come here to XDA and mess up their devices because they follow bad advice that they read. Don't do this. It can have unintended consequences and according to Google has absolutely no effect on when you will receive an OTA.

muyoso said:
And this is how people who don't know better come here to XDA and mess up their devices because they follow bad advice that they read. Don't do this. It can have unintended consequences and according to Google has absolutely no effect on when you will receive an OTA.
Click to expand...
Click to collapse
People who don't follow the exact directions you mean..and are you saying that this trick worked for 3 Nexus devices I own completely by chance after trying to update over 5 times each before doing the trick and then it working after the trick?

myorks1127 said:
People who don't follow the exact directions you mean..and are you saying that this trick worked for 3 Nexus devices I own completely by chance after trying to update over 5 times each before doing the trick and then it working after the trick?
Click to expand...
Click to collapse
What I am saying is that it doesn't matter how many people like you swear that it works. The people who actually work on Android say it doesn't and that it can have bad consequences. And anyone who actually wants the update can simply sideload it with absolutely no ill effects if they want to force the update onto their devices early. There is absolutely zero reason to do what you swear works.

muyoso said:
What I am saying is that it doesn't matter how many people like you swear that it works. The people who actually work on Android say it doesn't and that it can have bad consequences. And anyone who actually wants the update can simply sideload it with absolutely no ill effects if they want to force the update onto their devices early. There is absolutely zero reason to do what you swear works.
Click to expand...
Click to collapse
The reason to do it is to save time and hassle of doing all the steps needed for side loading, but no worries, I got the update faster and easier than anyone who side loaded with ZERO consequences to me..:good:, your Google knee pads must be pretty worn out by now huh?

Or you can just wait for the update. I'm still on 4.4 and happy about it. 4.4.1 brought radio issues, and 4.4.2 also seems to have a few bugs. Hopefully by the time I get the OTA, the bugs will be fixed.

myorks1127 said:
The reason to do it is to save time and hassle of doing all the steps needed for side loading, but no worries, I got the update faster and easier than anyone who side loaded with ZERO consequences to me..:good:, your Google knee pads must be pretty worn out by now huh?
Click to expand...
Click to collapse
Yes, I am sucking Google's **** because I am telling users who don't know better that Google specifically said not to do this. You got me. My secret is out.

myorks1127 said:
It doesn't wreak havok on my end so why would I care?
Click to expand...
Click to collapse
The problem is you don't know if it does. Because the GCM id changes, things like push messages from different apps will likely stop working (maybe permanently if they don't properly handle a changing id). You might not of noticed this much in the past because not a lot of apps utilized GCM push messages. However, more and more apps are using them today.

It's amazing that people will ignore advice from the people that have written the actual software. Just don't do it. The worst part about doing it is that you may not even know that something has messed up because its not obvious.

Thanks worked for me
Took me straight from 4,4 to 4,4.2 after 4 attempts

Force OTA if not comfortable with sideload...

Settings, Apps, All, Google Service Framework.
Force Stop, Clear Data.
Then check for update in About Phone.
Then repeat these steps, and the update shows up on the second check. Repeated this on 3 phones to get 4.4.2 where 4.4.1 hadn't even popped up previously.
---
Note, this procedure is to be followed at your own risk. I have completed this successfully on 3 x Nexus 5 from v4.4, however I can not test all scenarios or be responsible for any subsequent issues, whether related to this method or not. If you cant accept this, then wait for the OTA.

FunkyMagic-UK said:
Settings, Apps, All, Google Service Framework.
Force Stop, Clear Data.
Then check for update in About Phone.
Then repeat these steps, and the update shows up on the second check. Repeated this on 3 phones to get 4.4.2 where 4.4.1 hadn't even popped up previously.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
http://www.androidpolice.com/2013/1...to-never-clear-google-service-framework-data/

FunkyMagic-UK said:
Settings, Apps, All, Google Service Framework.
Force Stop, Clear Data.
Then check for update in About Phone.
Then repeat these steps, and the update shows up on the second check. Repeated this on 3 phones to get 4.4.2 where 4.4.1 hadn't even popped up previously.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
No. We already had a long thread about this. Please have a mod close this.
And not to sound rude - but if you're uncomfortable with sideload, you probably shouldn't have a Nexus.

I don't believe the Dan M statement is wholly accurate, given I've thoroughly checked the issues he says might arise.
I suspect it's more a case of him protecting Googles roll out schedule planning with a plausible explanation.
Not sure why someone not comfortable with sideloads shouldn't have a Nexus... it's just a regular consumer phone like any other.
Sent from my Nexus 5 using xda app-developers app

FunkyMagic-UK said:
I don't believe the Dan M statement is wholly accurate, given I've thoroughly checked the issues he says might arise.
I suspect it's more a case of him protecting Googles roll out schedule planning with a plausible explanation.
Not sure why someone not comfortable with sideloads shouldn't have a Nexus... it's just a regular consumer phone like any other.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
1. If someone who writes the code for Google tells you not to do something and gives you a list of reasons, I would suggest listening. As pointed out in the thread it can cause problems and it isn't always something you notice.
2. Because there is no danger in sideloading. It will either work or refuse to flash.
3. It's a Nexus. It's meant for that kind of thing. It's EXTREMELY easy.
4. If they aren't comfortable with sideloading, they probably wouldn't know whether or not their device had an issue after the update. They could miss out on certain features, apps not functioning properly, etc. You are essentially telling someone computer illiterate that they should do something that could potentially mess something up on their device instead of doing something that is fool-proof. That's irresponsible. Not to mention - they wouldn't even know how to fix it if it did damage anything

FunkyMagic-UK said:
I don't believe the Dan M statement is wholly accurate, given I've thoroughly checked the issues he says might arise.
I suspect it's more a case of him protecting Googles roll out schedule planning with a plausible explanation.
Not sure why someone not comfortable with sideloads shouldn't have a Nexus... it's just a regular consumer phone like any other.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
What do you mean you've thoroughly checked? You've isolated and tested the behavior of every single app that uses GCM after a framework data clear?
I mean, you are essentially accusing an Android engineer of taking to reddit to lie.. but why? Considering they have provided an officially supported method of sideloading OTA updates the idea they are "protecting roll out schedule planning" is total nonsense.
There are only 2 possible scenarios here
1) Dan Morrill is being 100% truthful
2) Instead of simply disabling the "Clear Data" button in Framework which would be dead simple, Google has chosen to send engineers to social media to spread lies and misinformation

I upgraded from 4.4 to 4.4.2 with 0 problems , if Google says don't sideload what u gonna do no side load?
Sent from my Nexus 5 using XDA Premium 4 mobile app

seriously sideload is about the easiest way to do it other than being able to download it direct to the phone and parse the sdcard like the way phones used to work... i know windows machines and that whole "driver" thing you guys need to deal with can get annoying but it's really not difficult. if you are afriad of command prompts then wait the 2 weeks or so that it takes to get it rolled out.

People spend a good amount of time on making instructional threads, gathering information all in one place, doing everything in their power to make it easy for even a complete beginner to do stuff with their phones, and we still have people wanting them to do it the harder way.
And then they defend their thinking with some ridicilous conspiracy theory that completely contradicts the very nature of how Google DEMONSTRATES that they are 100% behind people sideloading (ie: taking the all of 30 seconds it takes to do) an upate onto their phone) by implying that they have a vested interest in slowing down the number of activations?
Seriously now.

You people crack me up. Before this person from google said do not do this we ALL did it multiple time on multiple devices at least I did. No core meltdowns... yet.
remember these are the same people who thought the Nexus 5 camera was good to go as is...

crachel said:
What do you mean you've thoroughly checked? You've isolated and tested the behavior of every single app that uses GCM after a framework data clear?
I mean, you are essentially accusing an Android engineer of taking to reddit to lie.. but why? Considering they have provided an officially supported method of sideloading OTA updates the idea they are "protecting roll out schedule planning" is total nonsense.
There are only 2 possible scenarios here
1) Dan Morrill is being 100% truthful
2) Instead of simply disabling the "Clear Data" button in Framework which would be dead simple, Google has chosen to send engineers to social media to spread lies and misinformation
Click to expand...
Click to collapse
It's not worth your time trying to explain this. There are those who will always believe they are right. They will continue to ignore knowledge provided by those who are experts on the matter and believe they are right.
The most common excuse I read is "I've been doing it for so long without any issues". The technical explanation clearly states that the issues that happen are more often than not invisible to the user. Then they'll take to XDA to create a bunch of threads about "OMGZZZZ MY PHONE IS BROKEZORZ, GOOGLE IS TURNING INTO APPLE...RABBLE RABBLE RABBLE" and not even think that the issues might be related to breaking GCM in an app or similar.

Who cares if it can be bad. It can often be easier than sideloading, especially if you don't have a computer near by. I did it while waiting for my plane the other day and it was nice to have the camera improvements before I got to my destination. Just plan to do a factory reset after you get the update if it bothers you.
Not to mention, I am fairly sure whenever you install Google Apps after installing a dirty flashing an updated ROM it does the same thing as clearing data on the framework. I have certain apps I always have to reinstall or they stop getting push updates after doing that.

Tony_YYZ said:
It's not worth your time trying to explain this. There are those who will always believe they are right. They will continue to ignore knowledge provided by those who are experts on the matter and believe they are right.
The most common excuse I read is "I've been doing it for so long without any issues". The technical explanation clearly states that the issues that happen are more often than not invisible to the user. Then they'll take to XDA to create a bunch of threads about "OMGZZZZ MY PHONE IS BROKEZORZ, GOOGLE IS TURNING INTO APPLE...RABBLE RABBLE RABBLE" and not even think that the issues might be related to breaking GCM in an app or similar.
Click to expand...
Click to collapse
I don't want to progress yet another thread about this within two days, but I completely agree with your last point. I bet half of the people that do this will post on here in about a week saying their apps aren't syncing/working and "nexus 5 sucks" etc etc. I've already responded to someone who was asking about his gmail not syncing properly on 4.4.2. I asked him if he cleared the framework to get the update. Would be a great example if that's why he's having the problem.

Grims said:
Not to mention, I am fairly sure whenever you install Google Apps after installing a dirty flashing an updated ROM it does the same thing as clearing data on the framework. I have certain apps I always have to reinstall or they stop getting push updates after doing that.
Click to expand...
Click to collapse
That's not the point. He's not telling people who are familiar with these phones to do it. He's telling people who have no idea what the hell they are doing to do it.

PsychDrummer said:
I don't want to progress yet another thread about this within two days, but I completely agree with your last point. I bet half of the people that do this will post on here in about a week saying their apps aren't syncing/working and "nexus 5 sucks" etc etc. I've already responded to someone who was asking about his gmail not syncing properly on 4.4.2. I asked him if he cleared the framework to get the update. Would be a great example if that's why he's having the problem.
Click to expand...
Click to collapse
Alright, the real question here is after someone has cleared the framework, is there a way to recover or go back without restoring a backup or reflashing an OTA from scratch? Or does it just take time for Google to catch up? And DO they eventually catch up to the device? Or is it inevitably doomed once you clear. We can argue about why or why not, but lets figure out how.

Love how people jump on this guy or the one from yesterday who posted it. Been doing this on my past 4 devices. If something clears, wouldn't it be like hard resetting your device. All the information will get populated back. I also believe the engineer said there is a possibility something can go wrong. There is always the possibility something can go wrong with anything!
You can screw up your phone just taking an OOTO. People just need to let it go. We also do not know what his true intentions were for saying that.
If you do not want to clear data, then don't but don't tell others not to do it unless anyone here has experienced a problem first hand in doing so.

[email protected] said:
Love how people jump on this guy or the one from yesterday who posted it. Been doing this on my past 4 devices. If something clears, wouldn't it be like hard resetting your device. All the information will get populated back. I also believe the engineer said there is a possibility something can go wrong. There is always the possibility something can go wrong with anything!
Click to expand...
Click to collapse
It is not a question of 'if'. If you clear the services framework, Gmail notifications are 100% guaranteed to stop working for a time (could be 10 minutes, could be several days). Thankfully, Gmail is one of the few apps that will eventually realize the GCM id has changed and is able to deal with it. That is not the case for other apps.
The problem is people here don't see their phone or apps crashing and think everything is fine. But a week later they realize stuff isn't syncing or notifications aren't coming in and they blame it on the software update.

Again?? REALLY!! Google say no, like it or not they are the experts...
Sent from my Nexus 5 using XDA Premium 4 mobile app

HOXnoo8 said:
Alright, the real question here is after someone has cleared the framework, is there a way to recover or go back without restoring a backup or reflashing an OTA from scratch? Or does it just take time for Google to catch up? And DO they eventually catch up to the device? Or is it inevitably doomed once you clear. We can argue about why or why not, but lets figure out how.
Click to expand...
Click to collapse
His true intentions were to stop people from potentially messing up their phones and then ignorantly going online or on an apps review page and spouting off about how broken the app or phone is. To think differently makes no sense.
Sent from my Nexus 5 using xda app-developers app

I am stuck in boot loop with this method
Sent from **Nexus 5 signal sucks**

Get rid of custom lock pad on reboot

This is what I use to get rid of the custom lock pad sign from the bootloader when you reboot. Some people got it after they rooted and disabled some apps like me. It's in wanam xposed. Below is a pic to show where it is. It works very well. It takes a couple reboots after you enable it for it to take effect. But after that I have not seen it come back at all. Just wanted to share my findings with others. Hopefully it helps others who may have been looking for the same solution.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

First thing i did.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

Greycloak42 said:
First thing i did.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
It's good to know, but a flash of the SM-G900A firmware from here on XDA, minus the BL bootloader file, gets rid of that anyway. It's not that big of a deal whether it's there or not, unless you're taking the phone in for warranty service.

shortydoggg said:
It's good to know, but a flash of the SM-G900A firmware from here on XDA, minus the BL bootloader file, gets rid of that anyway. It's not that big of a deal whether it's there or not, unless you're taking the phone in for warranty service.
Click to expand...
Click to collapse
No one said it was a big deal or not. It's sharing of information that is what xda is all about. And since there is no other post in our forum about it, this is why I shared. Has nothing to do with what way is better or being a big deal.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

freebee269 said:
No one said it was a big deal or not. It's sharing of information that is what xda is all about. And since there is no other post in our forum about it, this is why I shared. Has nothing to do with what way is better or being a big deal.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
I did this and rebooted mine 5 times.. Never went away. Xposed is working fine because i also added screen shot to menu and the reboot options. but cant get rid of the security lock back to normal.

All i did was that i download the latest supersu from chainfire updated su binary reboot and got that lockpad away
Sent from my SAMSUNG-SM-G900A using Tapatalk

That worked thanks!

So how did you get rid of it exactly?
Sent from my SAMSUNG-SM-G900A using Tapatalk

Install the supersu.apk located in the file i just uploaded and update su binary reboot 3 times and it should have remove the padlock

It's not giving me option to update binary
Sent from my SAMSUNG-SM-G900A using Tapatalk

It's always the same thing every time a new Samsung phone comes out. Maybe I can save some people some time and tell you each phone can and will show the custom lock icon at different times no matter what you do. In other words, if you do something that stops it from showing on your phone, there is absolutely NO guarantee that the same method will stop it from showing on someone else's phone. The scan that selects if the custom status or unlock icon is shown or not occurs on each individual phone at the time of boot. Therefore, depending on the current state of each phone, it might show or not show. The only real way to stop it from showing is through a mod (located in the AT&T S4 section) that actually modifies system files. X-posed modules just cover the icon, so the appearance is just graphical. It works for most (though it isn't truly changing anything), but for some it still doesn't. AGAIN. JUST BECAUSE SOMETHING WORKS ON YOUR PHONE,DOES NOT MEAN IT WILL WORK ON OTHERS...it just might.

glad it worked

viperbe said:
That worked thanks!
Click to expand...
Click to collapse
glad it worked for you.

freebee269 said:
well that's just common sense. and nowhere did i say this will work on everyones phone. i just pointed out an option that worked for me. i shared info that worked for me in hopes it helped someone else out. this is what this community is about right? and i see it worked for someone else also. the best thing you can do is to not reply to this topic if you have nothing to bring to it. and that paragraph you typed brought nothing to this topic but complaining.
Click to expand...
Click to collapse
This forum isn't just about you. Posts like yours FAIL to mention that it might not work for everyone trying it so people that it doesn't work for are left wondering what they did wrong. When in fact, they have done nothing wrong. Mentioning what works for you is great, but stop getting so offensive when someone adds more information or states that your solution might not work for everyone. You should be welcoming the addition of useful information instead of acting like "nothing was brought to YOUR thread" because you didn't know about it or mention it. A little research about X-posed and SysScope should be done by anyone wanting to permanently get rid of the custom lock icon.
Not only did I mention that X-posed might not work for some, but I also mentioned a permanent modification to get rid of the custom icon instead of just covering it up with X-posed modules. Now how exactly did my paragraph have nothing to do with this topic?

scott14719 said:
This forum isn't just about you. Posts like yours FAIL to mention that it might not work for everyone trying it so people that it doesn't work for are left wondering what they did wrong. When in fact, they have done nothing wrong. Mentioning what works for you is great, but stop getting so offensive when someone adds more information or states that your solution might not work for everyone. You should be welcoming the addition of useful information instead of acting like "nothing was brought to YOUR thread" because you didn't know about it or mention it. A little research about X-posed and SysScope should be done by anyone wanting to permanently get rid of the custom lock icon.
Not only did I mention that X-posed might not work for some, but I also mentioned a permanent modification to get rid of the custom icon instead of just covering it up with X-posed modules. Now how exactly did my paragraph have nothing to do with this topic?
Click to expand...
Click to collapse
you win man. i'm not on xda to pump my chest and try to sound better than others. i'll leave that to you. i only shared what i found that worked. as i said you could have just moved on instead of starting an argument. but i'm not going to continue to give you attention with this. so anything you have to say from here on out i wont be able to see. have a good night.

Thread is closed at the request of the OP.
XDA appreciates all who share knowledge of things that work, and things that only work for some. With all the different devices and multitudes of "add-ons", what works for some people, might not work for others.
Cheers
MD

LG Please know we hate this. Let us turn this annoying feature off

This right here pisses me off
Sick of this damn call timer when trying to use other apps during a call.

Although that there isnt the main reason why I'm getting rid of this phone, I'll go ahead and add it to the ever growing list of reasons why I'm dumping it and getting a Nexus 6. Screw LG and their locked down pile of garbage. Sad thing is, it's so much wasted potential.

I love it when a new device comes out, and XDA becomes riddled with whiney posts about "this" or "that" which users say they 'hate' or 'can't stand'. Okay, so there's no publicized root method yet, deemed safe for consumerism, but once that's released I'm sure that every little quarky nuance will have a method to remove, hide, or alter in some way. The call timer has an option for hiding in the LG G3 via G3 Tweaksbox. With that example, I stand confident that this phone will have some type of similarities to, as I mentioned, "deal" with the things people complain about. Fact is, this phone is not impressively different from the G3, and there are no real profoundly engineered improvements made in the G4. You may ask, "Apex, y u bye did fone den?" Good question. My answer is this, I like LG's products and I appreciate the work developers are able to do, in order to make something good, great. So, in the meamtime, until root is available, you won't hear me having a hissy fit about (insert whatever) things. Samsung isn't for me, HTC is bunk, Motorola, well... been there, done that. I think most folks would respect those complaints be made on Reddit, or somewhere besides the place that developers afford us the grace of enjoying what they do for the community, free of charge.
Sent from my LG-H811 using XDA Free mobile app

painedglass said:
Although that there isnt the main reason why I'm getting rid of this phone, I'll go ahead and add it to the ever growing list of reasons why I'm dumping it and getting a Nexus 6. Screw LG and their locked down pile of garbage. Sad thing is, it's so much wasted potential.
Click to expand...
Click to collapse
locked down how? seems pretty rooted to me

lobo4806 said:
locked down how? seems pretty rooted to me
Click to expand...
Click to collapse
TWRP now too.. ROMS will be flowing soon.

Meh, I left the steaming pile of hardware failures that is a Nexus 6 for the G4. Volume rockers stopped working on the first one, new phone had screen issues, ya, the N6 isn't the greatest phone ever.

lobo4806 said:
locked down how? seems pretty rooted to me
Click to expand...
Click to collapse
It sure was when I posted, or did you not see the date of the Op? Yay, you got root on a phone that should have been unlocked in the first place.

painedglass said:
It sure was when I posted, or did you not see the date of the Op? Yay, you got root on a phone that should have been unlocked in the first place.
Click to expand...
Click to collapse
Angry much?

painedglass said:
It sure was when I posted, or did you not see the date of the Op? Yay, you got root on a phone that should have been unlocked in the first place.
Click to expand...
Click to collapse
Because clicking a check box to unlock the bootloader is so hard. Root takes time on all modern devices.

Hahaha... Now root being available, I've installed debloated ROM and 3000mah battery serves me really well. Not to mention boost in speed as well. On stock ROM, I was missing my nexus 5 so much.
I hope you stuck around for a little longer. Feels like beasty phone just got injected with the steroid.
Sent from my LG-H811 using XDA Free mobile app

Agreed....I was fed up with this phone.....root came and glory glory amen it's a better phone. Even with just a simple debloated ROM....can't wait till they really tweak the stock ROM like crazy. I probably won't go aosp....because of the camera app...whole reason I bought the phone...it deletes the side car RAW file in the default gallery aosp can't do that...neither can manual camera app or Fv5
---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------
The thermal throttling and stuff needs some crazy tweaking...and a better kernel...my apps have to re draw too much...memory leak somewhere

Kingaries79 said:
This right here pisses me off
Sick of this damn call timer when trying to use other apps during a call.
Click to expand...
Click to collapse
I'm not sure if you figured it out, but since we have root, you can download app ops from play store. Go to the phone section and disable draw on top. It will stop the timer. And so far I have not noticed anything wrong.
Sent from my LG-H811 using Tapatalk

mawells787 said:
I'm not sure if you figured it out, but since we have root, you can download app ops from play store. Go to the phone section and disable draw on top. It will stop the timer. And so far I have not noticed anything wrong.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
this is gold. i dont have a tmobile version, but thanks!!! ahh boo the side effect to this is that when someone calls, you dont see the answer/decline dialog and the notification bar doesnt work

ExTREmE99 said:
this is gold. i dont have a tmobile version, but thanks!!! ahh boo the side effect to this is that when someone calls, you dont see the answer/decline dialog and the notification bar doesnt work
Click to expand...
Click to collapse
I checked and I still get the dialog box, make sure the option is checked in the call settings. I'm not sure what you mean about the notification bar, but I can drag down and click on the call, which brings me back to the call.
Sent from my LG-H811 using Tapatalk

mawells787 said:
I'm not sure if you figured it out, but since we have root, you can download app ops from play store. Go to the phone section and disable draw on top. It will stop the timer. And so far I have not noticed anything wrong.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Thanks for this

Seems like a really silly reason to get rid of an otherwise awesome phone...

What's funny is that the current root methods as dangerous as they are. Are no more dangerous then when I had my Evo4g, and that team didn't have something like "OEM Unlock" to make it easier. No risk, no reward.

Not to mention that you can drag that icon anywhere on the screen so i dont see how it can be so intrucive during other app usage. Also why dont you just talk on the phone, your on a call, pay attention and stop playing with other apps, real easy
Sent from my LG-H811 using XDA Free mobile app

Apex said:
I love it when a new device comes out, and XDA becomes riddled with whiney posts about "this" or "that" which users say they 'hate' or 'can't stand'. Okay, so there's no publicized root method yet, deemed safe for consumerism, but once that's released I'm sure that every little quarky nuance will have a method to remove, hide, or alter in some way. The call timer has an option for hiding in the LG G3 via G3 Tweaksbox. With that example, I stand confident that this phone will have some type of similarities to, as I mentioned, "deal" with the things people complain about. Fact is, this phone is not impressively different from the G3, and there are no real profoundly engineered improvements made in the G4. You may ask, "Apex, y u bye did fone den?" Good question. My answer is this, I like LG's products and I appreciate the work developers are able to do, in order to make something good, great. So, in the meamtime, until root is available, you won't hear me having a hissy fit about (insert whatever) things. Samsung isn't for me, HTC is bunk, Motorola, well... been there, done that. I think most folks would respect those complaints be made on Reddit, or somewhere besides the place that developers afford us the grace of enjoying what they do for the community, free of charge.
Sent from my LG-H811 using XDA Free mobile app
Click to expand...
Click to collapse
your point is?
Would you be so kind as to elaborate on
XDA becomes riddled with whiney posts
Click to expand...
Click to collapse

Possible Stop New Update 60% Battery Limit, Please Help

Hello,
Can someone please explain if its possible to stop the update that lowers your battery to 60 max charge? Im with tmobile, running on the PI4 and have NOT updated yet but I received my first warning. I want to keep this phone, I dont feel I'm at risk and I only charge the phone when Im awake. Please let me know if this is possble, and if you can point me in the right direction. I'm not a complete newbie but Im not pro either.
Thanks in advance for any help

Look for the new thread under questions and answers saying package disable pro. It'll solve your problem. I also got the update but didn't apply it from Tmobile. Using the steps outlined from the user in package disabler pro version number 6.3 it removed the update icon I had received. Again, be sure to follow the instructions from that new thread by not using the newest version. Use the 6.3 that the poster provided.
Link is below.
http://forum.xda-developers.com/tmo...-update-60-battery-limit-please-help-t3494682

Yea im battling this now.
I been trying to exchange my phone but tmobile isnt selling the black s7 edges and i dont want the crappy sliver or gold one.
I have package setup amd havent gotten the update.
But my girl gotten the update today.
I used the package disable and it stop it but we will see how long

Update already installed.
It already installed the update itself. Any way to disable the limit on battery now ?

Pavsberg said:
It already installed the update itself. Any way to disable the limit on battery now ?
Click to expand...
Click to collapse
maybe you should try to odin the latest stock firmware and start from scratch and dont update again

Good thing I blocked all samsung updates.
I wish v2 note 7 can be rooted

I woke up to it instilling it's self this sucks oh well guess Wednesday I'm giving it back until I can get pixel or wait until s8 comes out
Sent from my SM-N930T using XDA-Developers mobile app

phenixof4 said:
Good thing I blocked all samsung updates.
I wish v2 note 7 can be rooted
Click to expand...
Click to collapse
You have to also remember and be careful to not update Package Disabler Pro or EZ Disabler in the PlayStore. Samsung forced them to remove system updates from their apps. Sucks to have to manually update everything, but that is where we are at.

ocjelf said:
I woke up to it instilling it's self this sucks oh well guess Wednesday I'm giving it back until I can get pixel or wait until s8 comes out
Sent from my SM-N930T using XDA-Developers mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmobile-note-7/how-to/updated-limited-to-60-heres-fix-t3495293
Here is the solution if it updated yourself.
---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------
http://forum.xda-developers.com/tmobile-note-7/how-to/updated-limited-to-60-heres-fix-t3495293
Heres how to downgrade and prevent from getting the update again.

Dude just give the phone back and move on.

charlieb620 said:
Dude just give the phone back and move on.
Click to expand...
Click to collapse
I know that wasn't meant for me, but absolutely no can do!! The phone I will get may not be released in the US until January, plus T-Mobile still has my bill jacked up! I'm not going to fight them for a full refund until they stop charging me for a phone I already paid for in full! I've been fighting them since September to correct my bill! Then, they have to clean up that mess of charges for the Tab and everything else. I'm using this baby until the day my refund is clear to be deposited directly back into my account with no problems AND when I can get my hands on the Huawei Mate 9!