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**
Related
Didn't see this anywhere, so I thought I would try and hopefully save at least one person some time/frustration. I, like many people on this site own multiple devices and swap my Sprint service back and forth between them. I normally do this through Sprint.com. I just got my GS4 and spent hours testing what launcher would be the fastest with this SOC, and setting everything up exactly the way I wanted it.(I always keep things stock for the return period so I had no real way of making a backup) After I got everything the way I wanted, I activated this beauty...but upon doing this, I didn't see the fine print that the profile update triggers a factory data wipe.. **POOF** and all my app/prefs/etc. were gone. Needless to say, I was LIVID. I waited until I was calmed down to call customer care. The rep I spoke to advised that they changed it to require a factory data wipe when switching service online and you need to call customer care to attempt a manual IMEI/DEC/HEX swap.
glassjosh said:
Didn't see this anywhere, so I thought I would try and hopefully save at least one person some time/frustration. I, like many people on this site own multiple devices and swap my Sprint service back and forth between them. I normally do this through Sprint.com. I just got my GS4 and spent hours testing what launcher would be the fastest with this SOC, and setting everything up exactly the way I wanted it.(I always keep things stock for the return period so I had no real way of making a backup) After I got everything the way I wanted, I activated this beauty...but upon doing this, I didn't see the fine print that the profile update triggers a factory data wipe.. **POOF** and all my app/prefs/etc. were gone. Needless to say, I was LIVID. I waited until I was calmed down to call customer care. The rep I spoke to advised that they changed it to require a factory data wipe when switching service online and you need to call customer care to attempt a manual IMEI/DEC/HEX swap.
Click to expand...
Click to collapse
TiBu is your friend
rawintellect said:
TiBu is your friend
Click to expand...
Click to collapse
Word.
Sent from my SPH-L720 using xda app-developers app
glassjosh said:
Didn't see this anywhere, so I thought I would try and hopefully save at least one person some time/frustration. I, like many people on this site own multiple devices and swap my Sprint service back and forth between them. I normally do this through Sprint.com. I just got my GS4 and spent hours testing what launcher would be the fastest with this SOC, and setting everything up exactly the way I wanted it.(I always keep things stock for the return period so I had no real way of making a backup) After I got everything the way I wanted, I activated this beauty...but upon doing this, I didn't see the fine print that the profile update triggers a factory data wipe.. **POOF** and all my app/prefs/etc. were gone. Needless to say, I was LIVID. I waited until I was calmed down to call customer care. The rep I spoke to advised that they changed it to require a factory data wipe when switching service online and you need to call customer care to attempt a manual IMEI/DEC/HEX swap.
Click to expand...
Click to collapse
Had you already activated the device at least once before you attempted the online activation that resulted in the factory reset?
So I can confirm that this is indeed the desired behavior of chameleon. Whenever activation info is changed through HFA, then the device is now supposed to hard reset.
While this is certainly inconvenient if you didn't know it would happen (as us here in the store didn't know this was going to be the behavior going forward either), the reasoning behind it is sound: chameleon is put in place so that identical models of phones that are different sprint channels (sprint post paid, prepaid, boost, etc.) can run the same firmware; chameleon handles the bloatware payload for each channel. In other words, sprint no longer has to have different software packages for the same phone just because one gets sprint zone etc. and the other gets boost stuff etc.
Now, hopefully we get to a point to where chameleon is smart enough to recognize the current payload and decide whether a hard reset is necessary, but...baby steps I suppose.
EDIT: also, profile updates on their own don't require a reset. It's part of the whole HFA process that does it.
Sent from my SPH-L720 using xda premium
Nope, it was a new device I wanted to set up and play with on wifi before activating it. Now I just have to call CC and have them swap the devices manually.
rawintellect said:
TiBu is your friend
Click to expand...
Click to collapse
It's only your friend if you're rooted, I always keep stock FW for the return period of a device since you never know. I have always had mixed experiences with restoring app data as well.
glassjosh said:
It's only your friend if you're rooted, I always keep stock FW for the return period of a device since you never know. I have always had mixed experiences with restoring app data as well.
Click to expand...
Click to collapse
I've never had ONE bad experience with TiBu. Ever. If you know what you're doing it's fine. And why wouldn't you root? You can always unroot at any given time. And yes the counter can be reset.
The debate for rooting belongs elsewhere, I'm well aware you can reset counters, unroot, however, it's not worth the time when the risk of returning is high IMHO. You don't have to know what you're doing in TiBu, that's the beauty, but you still have a better chance of stability when using new app data, and it only takes 1 bad experience with some things..
glassjosh said:
The debate for rooting belongs elsewhere, I'm well aware you can reset counters, unroot, however, it's not worth the time when the risk of returning is high IMHO. You don't have to know what you're doing in TiBu, that's the beauty, but you still have a better chance of stability when using new app data, and it only takes 1 bad experience with some things..
Click to expand...
Click to collapse
LOL! You're not going to change my mind. I'm not going to change yours. I know from my own personal experience of MANY years of tinkering with android devices that you DO have to know what you're doing in TiBu or you're screwed. If you backup the wrong thing (say a system app from a different release of android) and restore it to an entirely new system you've just borked your device and are on a one way trip to bootloop city, population: YOU. And you'll have a full restore in your future.
As for "debating" on rooting? I'm not. Why even come on to XDA if you won't root? If you want stock apps stick to Google Play and sprint community forums. But don't come on to XDA and tell me or anyone else that rooting your phone is inferior to not rooting it. It just isn't. Period.
Stability is only as good as the person that coded it. That INCLUDES stock OEM ROMS or updates. I can count on two hands updates from manufacturers that have gone terribly wrong and been fixed by the devs in the XDA community LONG before they were fixed by the manufacturer. So your point about "new app data" is wrong as well.
And finally the "risk" isn't high. At all. Stop scaring folks. If your phone boots into the bootloader it's recoverable. Period. Even if it DOESN'T boot into the bootloader you can still recover it. I've had 8 HARD bricks. All of them recovered. Some even required EMMC_RECOVER to rewrite the bootloader. Don't know what that is? I'm not suprised. Let me google that for you. The WORST EVER required JTAG (again let me google that for you) to fix. But it WAS fixed.
I'm all done with this back and forth and I'll just place you on ignore and hope people see that you really have no clue what you're talking about.
Enjoy.
rawintellect said:
LOL! You're not going to change my mind. I'm not going to change yours. I know from my own personal experience of MANY years of tinkering with android devices that you DO have to know what you're doing in TiBu or you're screwed. If you backup the wrong thing (say a system app from a different release of android) and restore it to an entirely new system you've just borked your device and are on a one way trip to bootloop city, population: YOU. And you'll have a full restore in your future.
As for "debating" on rooting? I'm not. Why even come on to XDA if you won't root? If you want stock apps stick to Google Play and sprint community forums. But don't come on to XDA and tell me or anyone else that rooting your phone is inferior to not rooting it. It just isn't. Period.
Stability is only as good as the person that coded it. That INCLUDES stock OEM ROMS or updates. I can count on two hands updates from manufacturers that have gone terribly wrong and been fixed by the devs in the XDA community LONG before they were fixed by the manufacturer. So your point about "new app data" is wrong as well.
And finally the "risk" isn't high. At all. Stop scaring folks. If your phone boots into the bootloader it's recoverable. Period. Even if it DOESN'T boot into the bootloader you can still recover it. I've had 8 HARD bricks. All of them recovered. Some even required EMMC_RECOVER to rewrite the bootloader. Don't know what that is? I'm not suprised. Let me google that for you. The WORST EVER required JTAG (again let me google that for you) to fix. But it WAS fixed.
I'm all done with this back and forth and I'll just place you on ignore and hope people see that you really have no clue what you're talking about.
Enjoy.
Click to expand...
Click to collapse
I'm not trying to change anyone's mind, only warn others to possibly help someone out; which is the whole purpose of this site. I certainly don't have time to troll anyone's posts. Before you get more butt-hurt, read what I said. I know from my "MANY YEARS" of android tinkering and development, that you only need time to read, not to truly know what you're doing. Apparently we have different ideas of what that means. Never did I state that rooting was inferior, that's absurd. And how would you know the risk of me returning the phone in the return period? You obviously don't read or comprehend well. As stated before, I'm well familiar with the process for tweaking android devices, especially Samsung since I have 6 of them. I'm so super impressed with your vast knowledge though..
Wow. That escalated quickly for no reason. You ignores someone for having an opinion about not rooting a phone in the first seven days of owning it. I'm sure there are plenty of people on here that don't root in that first week, that includes me as one of them.
Sent from my SPH-L720 using xda premium
rawintellect said:
LOL! You're not going to change my mind. I'm not going to change yours. I know from my own personal experience of MANY years of tinkering with android devices that you DO have to know what you're doing in TiBu or you're screwed. If you backup the wrong thing (say a system app from a different release of android) and restore it to an entirely new system you've just borked your device and are on a one way trip to bootloop city, population: YOU. And you'll have a full restore in your future.
As for "debating" on rooting? I'm not. Why even come on to XDA if you won't root? If you want stock apps stick to Google Play and sprint community forums. But don't come on to XDA and tell me or anyone else that rooting your phone is inferior to not rooting it. It just isn't. Period.
Stability is only as good as the person that coded it. That INCLUDES stock OEM ROMS or updates. I can count on two hands updates from manufacturers that have gone terribly wrong and been fixed by the devs in the XDA community LONG before they were fixed by the manufacturer. So your point about "new app data" is wrong as well.
And finally the "risk" isn't high. At all. Stop scaring folks. If your phone boots into the bootloader it's recoverable. Period. Even if it DOESN'T boot into the bootloader you can still recover it. I've had 8 HARD bricks. All of them recovered. Some even required EMMC_RECOVER to rewrite the bootloader. Don't know what that is? I'm not suprised. Let me google that for you. The WORST EVER required JTAG (again let me google that for you) to fix. But it WAS fixed.
I'm all done with this back and forth and I'll just place you on ignore and hope people see that you really have no clue what you're talking about.
Enjoy.
Click to expand...
Click to collapse
Please don't feed the trolls...
Sent from my SPH-L900 using xda app-developers app
I'm pretty experienced with setting up Android devices, mainly because I get a new one every month or so (it's a real problem). I had the Nexus 4 and recall allowing it to restore from a backup. When I did that on the Nexus 5, it started downloading random apps from other devices that I don't even use anymore. I don't know what backup it was pulling from, but it was messy.
The worst part was, it kind of froze in the middle and refused to keep downloading apps. I cleared the cache on the Play Store app and started again. It downloaded a few apps, then quit again. I tried clearing data on Google Play, downloads, and Framework and nothing would work. When I tried to download apps manually, it would just give me an error and say it couldn't download. It wouldn't even update my existing apps.
Finally, at the recommendation of someone in Google groups, I logged out of Hangouts, then tried to log back in. It wouldn't let me log back in, even after several restarts.
Ultimately, after trying pretty much everything, I had to do a factory wipe and start over from scratch. I went through something similar (though not as bad) restoring from a backup a few months back. The moral of the story is, I will probably never restore from backup again.
After about an hour of setting up my accounts and downloading my apps manually, it's finally up and running. What a ride.
Cool story, bro.
Sent from my Nexus 5 using Tapatalk
I'll be restoring from my TB backup.
danjbry said:
Cool story, bro.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for your valuable input, bro. Consider yourself reported.
Sent from my XT1058 using Tapatalk
marinierb said:
I'll be restoring from my TB backup.
Click to expand...
Click to collapse
Yeah, I was rooted, too. I don't understand Google's backup system. It doesn't work anywhere near as well as iCloud. They really need to work on that.
Sent from my XT1058 using Tapatalk
greyhulk said:
allowing it to restore from a backup. When I did that on the Nexus 5, it started downloading random apps from other devices that I don't even use anymore. I don't know what backup it was puling from, but it was messy.
Click to expand...
Click to collapse
it started downloading apps i have backed up on my nexus 7, which i agree is quite annoying
while i know it's popular to complain about complainers, OP has a valid point imo. i agree that they need to get it cleaned up, or at least allow you to choice individual devices.
greyhulk said:
I don't understand Google's backup system. It doesn't work anywhere near as well as iCloud. They really need to work on that.
Click to expand...
Click to collapse
+1
greyhulk said:
I'm pretty experienced with setting up Android devices, mainly because I get a new one every month or so (it's a real problem). I had the Nexus 4 and recall allowing it to restore from a backup. When I did that on the Nexus 5, it started downloading random apps from other devices that I don't even use anymore. I don't know what backup it was puling from, but it was messy.
The worst part was, it kind of froze in the middle and refused to keep downloading apps. I cleared the cache on the Play Store app and started again. It downloaded a few apps, then quit again. I tried clearing data on Google Play, downloads, and Framework and nothing would work. When I tried to download apps manually, it would just give me an error and say it couldn't download. It wouldn't even update my existing apps.
Finally, at the recommendation of someone in Google groups, I logged out of Hangouts, then tried to log back in. It wouldn't let me log back in, even after several restarts.
Ultimately, after trying pretty much everything, I had to do a factory wipe and start over from scratch. I went through something similar (though not as bad) restoring from a backup a few months back. The moral of the story is, I will probably never restore from backup again.
After about an hour of setting up my accounts and downloading my apps manually, it's finally up and running. What a ride.
Click to expand...
Click to collapse
Pay a few dollars and get Titanium Backup Pro or Helium Premium. Google's backup and restore is horrendous; no one with any sense actually uses it. The paid versions of TiBu and Helium are well worth it. TiBu was my go-to for a long time, but I use Helium now. It has a much more user-friendly interface, and it doesn't require root.
greyhulk said:
Thanks for your valuable input, bro. Consider yourself reported.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Haha you are on the Nexus 5 forum posting about something that has pretty much nothing to do with the Nexus 5 and is 100% user error. What kind of responses do you expect, especially considering the 500 worthless threads people have posted today complaining about irrelevant things. You totally brought this on yourself, and reporting someone for pointing that out is a waste of your time. Look around this forum; the mods let anything fly here.
greyhulk said:
Yeah, I was rooted, too. I don't understand Google's backup system. It doesn't work anywhere near as well as iCloud. They really need to work on that.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure that if you uninstall apps outside of the playstore, then upon a backup restore it will restore that app again. If you uninstall from the store, it won't restore it again. This is just my guess on things I think i've noticed.. I never actually tried to prove my theory right.
Basically there's no way for us to force it to sync a current setup. If you start flashing nandroids and roms will mess it up as well.
greyhulk said:
Yeah, I was rooted, too. I don't understand Google's backup system. It doesn't work anywhere near as well as iCloud. They really need to work on that.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
In the Play Store it keeps track of every app you download, if you no longer want them backed up you have to delete them from "my apps."
Sent from my Nexus 5 using XDA Premium 4 mobile app
Paddington said:
Pay a few dollars and get Titanium Backup Pro or Helium Premium. Google's backup and restore is horrendous; no one with any sense actually uses it. The paid versions of TiBu and Helium are well worth it. TiBu was my go-to for a long time, but I use Helium now. It has a much more user-friendly interface, and it doesn't require root.
Haha you are on the Nexus 5 forum posting about something that has pretty much nothing to do with the Nexus 5 and is 100% user error. What kind of responses do you expect, especially considering the 500 worthless threads people have posted today complaining about irrelevant things. You totally brought this on yourself, and reporting someone for pointing that out is a waste of your time. Look around this forum; the mods let anything fly here.
Click to expand...
Click to collapse
How, pray tell, was a Google backup failing to restore "user error"?
Sent from my XT1058 using Tapatalk
I have no science behind this statement but I've always thought that restoring TB backups to different devices was extremely risky.
Sent from my SPH-L720 using Tapatalk
Paddington said:
Haha you are on the Nexus 5 forum posting about something that has pretty much nothing to do with the Nexus 5 and is 100% user error. What kind of responses do you expect, especially considering the 500 worthless threads people have posted today complaining about irrelevant things. You totally brought this on yourself, and reporting someone for pointing that out is a waste of your time. Look around this forum; the mods let anything fly here.
Click to expand...
Click to collapse
are you kidding me? nexus 5 may not have much to do with it, but this is a very legitimate bug in the current backup/restore system google has in place. i'm sure in time further revisions with work things out, but right now it sucks.
fwiw, i have everything backed up in titanium, but i'm not rooted and i don't wanna mess around with that right now. having the ability to easily move from android to android is something that has been sorely missing for some time for the average user.
---------- Post added at 03:22 AM ---------- Previous post was at 03:22 AM ----------
mjs2011 said:
I have no science behind this statement but I've always thought that restoring TB backups to different devices was extremely risky.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
it can be, you're often not supposed to restore app data but...
greyhulk said:
How, pray tell, was a Google backup failing to restore "user error"?
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Because Google backup doesn't work. You said yourself you've had problems with it before. For someone "experienced in setting up Android phones," I am surprised you haven't been using TiBu/Helium all along. Trust me, it's well worth spending the few dollars if you switch phones or ROMs more than once a year. Relying on Google backup to restore anything more than your contacts is user error.
Paddington said:
Because Google backup doesn't work. You said yourself you've had problems with it before. For someone "experienced in setting up Android phones," I am surprised you haven't been using TiBu/Helium all along. Trust me, it's well worth spending the few dollars if you switch phones or ROMs more than once a year. Relying on Google backup to restore anything more than your contacts is user error.
Click to expand...
Click to collapse
system error brah
Paddington said:
Haha you are on the Nexus 5 forum posting about something that has pretty much nothing to do with the Nexus 5 and is 100% user error. What kind of responses do you expect, especially considering the 500 worthless threads people have posted today complaining about irrelevant things. You totally brought this on yourself, and reporting someone for pointing that out is a waste of your time. Look around this forum; the mods let anything fly here.
Click to expand...
Click to collapse
It is not that we let anything fly here, it is just that with around 90 device forums to monitor we are spread around.
Feel free to use the report button when you see something that should not "FLY"
the information has been given,
thread closed
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
Hi all, appreciate best practice is always to read posted guides but I'm getting kinda old and too many threads are only relevant at particular points in time when the 5th Gen Fire was newer. So basically I'm lost in conflicting info on the guides and need some direction.
Starting point is i) I've got 'basic' experience of rooting and flashing roms, so my PC has got ADB drivers etc. ii) I have a stock OS 5.4.0.0 5th Gen Fire which is my elderly mothers and the intention is to get the crap OS removed and make it a simple Nexus 7'like device.
Can somebody please give me some step-by-step advice. I'm at the point where the device is developer enabled and ABD enabled. But the guides I've seen are all based on old OS's so I fear the whatever I try next will just brick the unit.
Thx in advance
As of now, 5.3.2.1 - 5.4.0.0 can not be rooted, much less have the bootloader unlocked to install a custom ROM.
aww bummer
OK second question : How should I treat the term "As of now"? Do you think there is any likelihood of a 5.4.0.0 root solution happening soon? i.e. weeks or months?
If its not gonna be a while, then I might just install the non-root google-play stuff and just shift the bloaty stuff out of sight if I can.
ebod said:
aww bummer
OK second question : How should I treat the term "As of now"? Do you think there is any likelihood of a 5.4.0.0 root solution happening soon? i.e. weeks or months?
If its not gonna be a while, then I might just install the non-root google-play stuff and just shift the bloaty stuff out of sight if I can.
Click to expand...
Click to collapse
EDIT: The usual warning: I am not responsible for any damage done to your device. If using ANY of these guides, you're doing so at your own risk.
That's about your only option at the moment. You can use the guide here, which will install the appropriate google services needed. You can then use this guide to manually 'uninstall' system/Amazon applications (you aren't really uninstalling them, just disabling them). Or use the automatic tool here, which will uninstall a significant number of the Amazon 'bloatware' and install the Google services and a few other Google related apps.
I CANNOT STRESS THIS NOTE ENOUGH: Whether you uninstall apps manually or automatically, please be aware you have to replace the Amazon apps BEFORE you uninstall them. For example, if you want to use contacts, you should install the necessary Google Contact APKs, open 'Contacts' then uninstall Amazon contacts. DO NOT UNINSTALL the Amazon Contact Storage APK or no contact applications will function properly, if at all. There is a guide here where you can install Google Contacts and get a fun little surprise as a result of doing so.
A factory reset will bring back all system apps you uninstall whether you uninstall them manually or automatically. So if anything stops working or you uninstall something that broke something else, factory resetting will fix the tablet, but you'll have to start over.
If you want to use a custom launcher like Nova Launcher, you can read this post which will describe how to do so. In this post I explain how to disable Fire Launcher without breaking the home button. Please read the WHOLE post, including the very bottom where there's a link that describes a 'fix' for the recent apps button (square button) which has a fit when you uninstall Fire Launcher (even on rooted devices). Just tap on 'hide Fire Launcher BEFORE' at the bottom which will take you to a page where you can activate widgets. Read the very bottom and it will tell you how to 'fix' the recent apps button. When you swipe closed apps using the recent apps button, swiping the last one will kick you to the lock screen or black you out for a moment. The fix is kinda cheesy, but it is a fix. I use it on my HD 8.
In this post I describe what Amazon apps I did NOT uninstall. Note this list of apps will differ slightly from the ones installed on the HD 7, but not by very much. This list MIGHT allow you to use Gmail (which doesn't work on any tablet model) and a few other apps.
Very soon, I plan to make a thread with a detailed tutorial on how to do all of this, so it's in one single spot for everyone to find.
Jake1702_ said:
As of now, 5.3.2.1 - 5.4.0.0 can not be rooted, much less have the bootloader unlocked to install a custom ROM.
Click to expand...
Click to collapse
For awareness/clarity: root and SuperSU (no other root manager) are the only prerequisites for installing a custom ROM on this device via FlashFire. The bootloader does not need to be unlocked.
Davey126 said:
For awareness/clarity: root and SuperSU (no other root manager) are the only prerequisites for installing a custom ROM on this device via FlashFire. The bootloader does not need to be unlocked.
Click to expand...
Click to collapse
Thanks Davey, yeah I'm not ultimately looking for a rooted device, I just want a clean Nexus'like rom with no bloated crap on it. As a plan-B I will follow the other guide notes that DragonFire kindly provided. But primarily if you are still staying I can get Flashfire to install a custom Nexus rom, then please can you guide me to the appropriate instructions to make Flashfire come to life.
I have Flashfire installed...but it just warns there are no permissions etc.
Thanks
ebod said:
Thanks Davey, yeah I'm not ultimately looking for a rooted device, I just want a clean Nexus'like rom with no bloated crap on it. As a plan-B I will follow the other guide notes that DragonFire kindly provided. But primarily if you are still staying I can get Flashfire to install a custom Nexus rom, then please can you guide me to the appropriate instructions to make Flashfire come to life.
I have Flashfire installed...but it just warns there are no permissions etc.
Thanks
Click to expand...
Click to collapse
A custom ROM (ie: Nexus) can not be installed on this device without root. I do not foresee that happening anytime soon with the so you're stuck with FireOS for a bit. It's not a bad skin once you get used to it.
@DragonFire1024 provided a nice summary of the available tweaks and associated caveats. I suggest going slow; start with the Google Play Store and some light visual customizations. Save the all-or-nothing 'debloat script' until have have a better idea of what to keep.
Most importantly, enjoy your new device and don't fret over what could have been.
This list MIGHT allow you to use Gmail (which doesn't work on any tablet model) and a few other apps.
Click to expand...
Click to collapse
Ummm... Gmail works fine on my Fire.
Davey126 said:
For awareness/clarity: root and SuperSU (no other root manager) are the only prerequisites for installing a custom ROM on this device via FlashFire. The bootloader does not need to be unlocked.
Click to expand...
Click to collapse
I did not know that. If that's the case, as soon as root is obtainable I'm installing the Fire Nexus ROM.
Jake1702_ said:
Ummm... Gmail works fine on my Fire.
Click to expand...
Click to collapse
You're lucky then. Many users have had issues with Gmail either force closing or not working at all. Hope the rest was somewhat helpful.
---------- Post added at 05:48 PM ---------- Previous post was at 05:47 PM ----------
Jake1702_ said:
Ummm... Gmail works fine on my Fire.
I did not know that. If that's the case, as soon as root is obtainable I'm installing the Fire Nexus ROM.
Click to expand...
Click to collapse
*IF* it becomes available. I've had my tablets almost a year, maybe a months or so under one. That's how long I've been waiting. Some have been waiting longer.
Jake1702_ said:
Ummm... Gmail works fine on my Fire.
Click to expand...
Click to collapse
Initially and for many months after the Gmail app worked fine on 5th-7th gen devices with Google Play Services/Store installed. The app started crashing on launch following a silent update (lasted about 2 months) then started working again a few weeks ago.
Davey126 said:
Jake1702_ said:
Ummm... Gmail works fine on my Fire.
Initially (and for many months after) the Gmail app worked fine on 5th-7th gen devices with Google Play Services/Store installed. The app started crashing on launch following a silent update (lasted about 2 months) then started working again a few weeks ago.
Click to expand...
Click to collapse
I read somewhere where quite a few people had put a bug report in or something to that effect. A few days later there was an update to Gmail. That's about the time I installed it and it worked perfectly for me. I'm willing to bet Google did something that that made it possible to use again. Did Amazon do something to block is from using it? In my opinion, not likely. But what caused it? Not a clue. There is some speculation it had to do to with a permission, but that's only speculation. This is something we'll likely never get the answer to.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Jake1702_ said:
... as soon as root is obtainable I'm installing the Fire Nexus ROM.
Click to expand...
Click to collapse
Don't get your hopes up. There's a reason securing root on Amazon and other manufacturer devices has become more difficult over the past 12-18 months. While I appreciate the euphemistic optimism shown by some the tightened security and legacy code cleanup initiated by Google is actually a good thing for the general Android user community. Of course, XDAers hate it (spare me the sermon on someone controlling *your* device) but they don't represent the much larger community that Amazon and other market driven companies are targeting. Business/capatolism 101.
Davey126 said:
Initially and for many months after the Gmail app worked fine on 5th-7th gen devices with Google Play Services/Store installed. The app started crashing on launch following a silent update (lasted about 2 months) then started working again a few weeks ago.
Click to expand...
Click to collapse
Might just have been the perfect period of time during when I had mine sitting and not being used. Guess I'm just lucky.
Davey126 said:
Don't get your hopes up. There's a reason securing root on Amazon and other manufacturer devices has become more difficult over the past 12-18 months. While I appreciate the euphemistic optimism shown by some the tightened security and legacy code cleanup initiated by Google is actually a good thing for the general Android user community. Of course, XDAers hate it (spare me the sermon on someone controlling *your* device) but they don't represent the much larger community that Amazon and other market driven companies are targeting. Business/capatolism 101.
Click to expand...
Click to collapse
It is definitely possible, just not enough people spending time on this device, they are all focused on more popular brands/devices.
Jake1702_ said:
Might just have been the perfect period of time during when I had mine sitting and not being used. Guess I'm just lucky.
It is definitely possible, just not enough people spending time on this device, they are all focused on more popular brands/devices.
Click to expand...
Click to collapse
This I will actually agree with. But to be honest, I really thought we'd have a good chance after Prime Day. I really thought we'd have gotten it then, but I still have hopes.
That being said, the tricks and hacks we've discovered over the last few months are pretty amazing. The method of 'uninstalling' I mentioned a few posts ago, was never intended nor expected to work on these tablets. It had sat on XDA for a couple days before I literally said out loud: "oh what the hell. I can't break anything." So gave it a shot and was incredibly surprised to see it really did disable Amazon Video.
With the tricks and hacks I also mentioned a few posts back, really does go a long way in terms of a custom ROM. Aside from the technical aspects and apps, in my opinion it's pretty much a custom systemless ROM. Though some may disagree with me very much.
Feel free to ask any question you like. We'll do our best to help.
DragonFire1024 said:
This I will actually agree with. But to be honest, I really thought we'd have a good chance after Prime Day. I really thought we'd have gotten it then, but I still have hopes.
That being said, the tricks and hacks we've discovered over the last few months are pretty amazing. The method of 'uninstalling' I mentioned a few posts ago, was never intended nor expected to work on these tablets. It had sat on XDA for a couple days before I literally said out loud: "oh what the hell. I can't break anything." So gave it a shot and was incredibly surprised to see it really did disable Amazon Video.
With the tricks and hacks I also mentioned a few posts back, really does go a long way in terms of a custom ROM. Aside from the technical aspects and apps, in my opinion it's pretty much a custom systemless ROM. Though some may disagree with me very much.
Feel free to ask any question you like. We'll do our best to help.
Click to expand...
Click to collapse
Funny how for months now this device still hasn't been rooted, yet a few days after the release of the Samsung Galaxy S8, it was already rooted. Simply, those devices have much more people willing to take time to find exploits for, whereas the Fire does not. It's a shame really.
Sent from my KFFOWI using Tapatalk
Jake1702_ said:
Funny how for months now this device still hasn't been rooted, yet a few days after the release of the Samsung Galaxy S8, it was already rooted. Simply, those devices have much more people willing to take time to find exploits for, whereas the Fire does not. It's a shame really.
Click to expand...
Click to collapse
There just may not be any at the moment. Amazon has done a lot to this OS, so much so, I've seen posts where users don't even consider it an Android base anymore. Depending on what you read, I've seen other sites where some say its too butchered.
Also keep in mind when an exploit is found, some have been around for a very long time. So one may exist, but no one has either found it yet so no method exists or as you say, may not care enough to take the time to make a method. Every Android device is different. The OS is customized and programed to a manufacturers liking who also add their own customization, then is passed off to a service provider who further customizes it. In that period exploits are patched or simply don't work because what's exploited in certain devices, may not exist in other devices. The list and possibilities really could go on.
DragonFire1024 said:
There just may not be any at the moment. Amazon has done a lot to this OS, so much so, I've seen posts where users don't even consider it an Android base anymore. Depending on what you read, I've seen other sites where some say its too butchered.
Also keep in mind when an exploit is found, some have been around for a very long time. So one may exist, but no one has either found it yet so no method exists or as you say, may not care enough to take the time to make a method. Every Android device is different. The OS is customized and programed to a manufacturers liking who also add their own customization, then is passed off to a service provider who further customizes it. In that period exploits are patched or simply don't work because what's exploited in certain devices, may not exist in other devices. The list and possibilities really could go on.
Click to expand...
Click to collapse
I wonder if it would be possible "break" the bootloader, so-to-speak, to a point where it "works" but is flawed, allowing the installation of a custom ROM.
Jake1702_ said:
I wonder if it would be possible "break" the bootloader, so-to-speak, to a point where it "works" but is flawed, allowing the installation of a custom ROM.
Click to expand...
Click to collapse
Not likely. I have a list of things to try on my head. Some simple, some outrageous. Truth is this HD 8 has been through hell. I've reset it more times than I can count. I've nearly disected it and to be honest I'm absolutely amazed I haven't broken it yet. So I'm giving her a break from that right now.
With that said, I have an HD 7 that's rooted. I have an idea to try some things using it, that could work on non rooted 7 and up tablets, that would be totally systemless that could open up the possibilities to some things. I've been disecting the HD 7 for some ideas and plan to do some testing very soon. I'm the type that will immediately look at all settings and functions and then look through every file, folder and directory I'm able to, so we can do what many of us have already achieved. Keep an eye on me
DragonFire1024 said:
Not likely. I have a list of things to try on my head. Some simple, some outrageous. Truth is this HD 8 has been through hell. I've reset it more times than I can count. I've nearly disected it and to be honest I'm absolutely amazed I haven't broken it yet. So I'm giving her a break from that right now.
With that said, I have an HD 7 that's rooted. I have an idea to try some things using it, that could work on non rooted 7 and up tablets, that would be totally systemless that could open up the possibilities to some things. I've been disecting the HD 7 for some ideas and plan to do some testing very soon. I'm the type that will immediately look at all settings and functions and then look through every file, folder and directory I'm able to, so we can do what many of us have already achieved. Keep an eye on me
Click to expand...
Click to collapse
If someone were to go so deep to a point where they took it apart, maybe it would be possible to modify the bootloader by setting up a custom one.
Sent from my KFFOWI using Tapatalk
I know it stores media scan db. Unlike previous Android versions, the OS does not let one wipe it's data or even force stop it. Using "pm clear com.android.providers.media" from ADB is, apparently, still allowed but doesn't seem to fix anything. It seem to recreate the db, judging by all the ringtones/notification tones getting reset everywhere, but it's data size remains about 3.8gb, which is insane. Media scanner apps show 401 total media files found, 355 images, 22 video and 24 audio files, those amounts should be far cry from being a big deal. What in the world is going on?! I don't have root, so i can't peek in /data/data/com.android.providers.media. I absolutely do not want to hard reset either.
Any ideas?
False alert. System UI seems to report the entire shared storage at "data" of that app, which has mislead me. Not sure if i should delete this thread now, or keep it in case someone else happens to notice this and wonders.
I had telegram do that to me before, kind of. Like, how did all these pictures get here and stuff...
Sent from my Pixel 5 using Tapatalk
It was a false alarm from my side, it didn't actually blow that db out of proportions, it just mistakenly shows everything on the "internal storage" as belonging to that app data. Guess it just counts everything created by whatever Linux user MTP runs on, and everything there belongs to that user.
BTW, since when did they disable wiping the data on it? Is it new on Android 11, or did i skip too many Android versions, lol. Still possible over adb, with pm, though. Gladly, doesn't follow the same logic the counting does!
InfX said:
BTW, since when did they disable wiping the data on it? Is it new on Android 11, or did i skip too many Android versions, lol. Still possible over adb, with pm, though. Gladly, doesn't follow the same logic the counting does!
Click to expand...
Click to collapse
I've not got an answer. I remember that on like ics or honeycomb gingerbread.
A while ago, anyway.
Well good news on your findings! When things like that happen it's crazy strange
Sent from my Pixel 5 using Tapatalk
There's the reset option under settings system now I guess
dirtyreturn said:
I've not got an answer. I remember that on like ics or honeycomb gingerbread.
A while ago, anyway.
Well good news on your findings! When things like that happen it's crazy strange
Click to expand...
Click to collapse
Indeed it is crazy strange. I've had this db getting huge before on older devices, but my first though was "how the hell, the phone is a week old", second thought "screw it, wipe and let it rescan", and then i see it still huge, lol.
Keeping this thread instead of deleting it, who knows, maybe in a month from now someone is going to wonder about the same thing.
InfX said:
Indeed it is crazy strange. I've had this db getting huge before on older devices, but my first though was "how the hell, the phone is a week old", second thought "screw it, wipe and let it rescan", and then i see it still huge, lol.
Keeping this thread instead of deleting it, who knows, maybe in a month from now someone is going to wonder about the same thing.
Click to expand...
Click to collapse
I'd sure not delete it.
If you think starting this thread was bad.
Man, I've posted worse, unfortunately. Being a super noob once
.
Sent from my Pixel 5 using Tapatalk
InfX said:
Indeed it is crazy strange. I've had this db getting huge before on older devices, but my first though was "how the hell, the phone is a week old", second thought "screw it, wipe and let it rescan", and then i see it still huge, lol.
Keeping this thread instead of deleting it, who knows, maybe in a month from now someone is going to wonder about the same thing.
Click to expand...
Click to collapse
And I just did, LOL. Good that it was not closed xD
InfX said:
False alert. System UI seems to report the entire shared storage at "data" of that app, which has mislead me. Not sure if i should delete this thread now, or keep it in case someone else happens to notice this and wonders.
Click to expand...
Click to collapse
It is not a false alert. You're partially right. The data isn't actually used by mediastorage because it just links to media files on the system. The problem is that Android is stupid enough to not have an exclusion for mediastorage's usage report.
In other words, Android is dumb enough to think that mediastorage is actually using all that space which will lead to a lack of storage space on your phone.