So I posted about this previously but here's more info and a clearer summary
The Issue:
Phone randomly reboots about an average of once per day. Screen freezes, goes black, comes back on for 3 seconds still frozen, then proceeds to reboot. I've kept track and 100% of of the time this seems to happen when I'm typing. Initially I thought it was Textra, but it has happened in Snapchat, and Twitch whenever the google keyboard is up. Google sent a replacement phone and the issues persists, and I find it hard to believe that both phone would have the exact same hardware issue. Furthermore it very much seems like a software issue considering it ONLY happens when the google keyboard is up.
My hope is that someone might have encountered this and has a simple solution although I doubt it. Unfortunately since I don't have another phone, I have to wait to obtain one before I do a safe mode test. And even if I do it's not realistic for me to test it that way because I'd have to spend hours typing away just to try to get the issue to occur (since it's not frequent like every 5 minutes).
I'm suspecting some data or a setting is getting transferred over from my previous backup that's affecting google keyboard or something of the sort. My next step will be a factory reset, and then reinstalling everything bit by bit manually. Of course I have to link my google account, but I won't have it automatically restore the backup. If that doesn't help then I'm at a loss. At that point I'd probably pick up a cheap Pixel 2XL as my daily, and use my P6Pro in safe mode as much as I can to try to trigger the issue I guess?
The Phone:
Pixel 6 Pro
Not Rooted
November 5 Update
Set up done using my google account to restore all apps and settings, not cable
Remind me since I don't recall if it was brought up in your other thread about the issue, did you try Official Google Android Flash Tool yet?
Agree with edor, Android flash tool, flash both slots, start all over
roirraW edor ehT said:
Remind me since I don't recall if it was brought up in your other thread about the issue, did you try Official Google Android Flash Tool yet?
Click to expand...
Click to collapse
I have not tried this. What would this be used for?
ne0ns4l4m4nder said:
Agree with edor, Android flash tool, flash both slots, start all over
Click to expand...
Click to collapse
Not sure what that means sorry, can you elaborate?
MarkAnthony121 said:
I have not tried this. What would this be used for?
Click to expand...
Click to collapse
To wipe the phone and start back fresh.
MarkAnthony121 said:
Not sure what that means sorry, can you elaborate?
Click to expand...
Click to collapse
Just that. To start back fully fresh. Then if you do that take my advice from the other thread, don't restore backups from Google or anywhere, and initially only install your most critical apps. Once you determine you're not having the problem, install some more. Verify, repeat.
ne0ns4l4m4nder said:
Agree with edor, Android flash tool, flash both slots, start all over
Click to expand...
Click to collapse
Not sure what that means sorry, can you elaborate?
roirraW edor ehT said:
To wipe the phone and start back fresh.
Just that. To start back fully fresh. Then if you do that take my advice from the other thread, don't restore backups from Google or anywhere, and initially only install your most critical apps. Once you determine you're not having the problem, install some more. Verify, repeat.
Click to expand...
Click to collapse
Yes but I don't understand what "flash both slots" means. And wouldn't I get the same result by simply doing a factory reset and then proceeding with the method of installing everything manually and not from a backup? Why use the google flash tool vs factory reset?
MarkAnthony121 said:
Not sure what that means sorry, can you elaborate?
Yes but I don't understand what "flash both slots" means. And wouldn't I get the same result by simply doing a factory reset and then proceeding with the method of installing everything manually and not from a backup? Why use the google flash tool vs factory reset?
Click to expand...
Click to collapse
At this point, that's more information than you really need to know to try to fix your phone. I don't want to overcomplicate things. You can look at Google search results for "Pixel flash both slots" if you really want to go down that road right now.
Spoiler: Some of the details you're asking for, but you don't need right now
In short, starting with the Pixel 1 in 2016, they have two copies of almost everything (except only one copy of user data). On a Pixel, and another phone that employs dual slots, when you receive an OTA update, it updates the copy of Android that you're not currently running, then reboots into the one it just updated, and once rebooted it goes ahead and updates the copy that you're no longer running, so they're both now updated.
Not all OEMs use the dual partition strategy, which is frustrating. When I briefly had the Note 10+ before the P6P came out, I was amazed that Samsung still hasn't adopted the method. It beats the old style OTA method that Samsung still uses to this day as far as I know where it takes 15-20 minutes or more to run the update while your phone is unable to be used at all, and then even when it boots up the next time Android has to finish the job "optimizing" your apps for the new update. Dual partitions for Android save a lot of time when updating the phone.
In some manual flashing processes, you end up with one slot with a different copy of what you have in the other slot - and you don't want that. The slots are referred to as Slot A and Slot B.
I can go further into detail but you don't really need that to fix your phone.
All you need to know right now is Official Google Android Flash Tool.
If you haven't already tried the factory reset, et cetera, which we had recommended to you at least once in the other thread, then by all means, you can try that. But if you're going to try that, you might as well just use the Official Google Android Flash Tool and ensure you are 100% stock. Official Google Android Flash Tool has fixed a good dozen or two folks' issues (I haven't been keeping count) in these forums in the past 2+ months.
So if the factory resetting doesn't solve things then you'll still have to try Official Google Android Flash Tool to be closer to sure that you tried everything that you could. We had already suggested the Factory Reset to you in the other thread. Since you created a new thread, I figured you might be looking for information you hadn't been given yet.
So the short answer is because Official Google Android Flash Tool will do an even more complete job of putting your phone back to 100% stock, with a lot less doubt than a simple factory reset. Sure, a factory reset, in theory, should get you the same thing, but there are all sorts of circumstances where a factory reset won't. Something is wrong with your phone and we don't know what it is.
There's the Factory Reset idea and then there's the Official Google Android Flash Tool idea - either coupled with the staggered manual installation of apps until you narrow down if it was a particular app causing the issue. It doesn't matter which one you choose to try first. If you try just a Factory Reset, and things still go haywire, then you'll still have to try Official Google Android Flash Tool after that. It's your choice, now pick one and go forth and hopefully reboot no more.
Also, I wasn't going to mention this but I will now. Forums generally discourage users from creating multiple threads about the same issue or posting about the same issue in multiple threads. You can always update the OP (opening/first post) if you need to, and give an update as a reply to your existing thread.
MarkAnthony121 said:
So I posted about this previously but here's more info and a clearer summary
The Issue:
Phone randomly reboots about an average of once per day. Screen freezes, goes black, comes back on for 3 seconds still frozen, then proceeds to reboot. I've kept track and 100% of of the time this seems to happen when I'm typing. Initially I thought it was Textra, but it has happened in Snapchat, and Twitch whenever the google keyboard is up. Google sent a replacement phone and the issues persists, and I find it hard to believe that both phone would have the exact same hardware issue. Furthermore it very much seems like a software issue considering it ONLY happens when the google keyboard is up.
My hope is that someone might have encountered this and has a simple solution although I doubt it. Unfortunately since I don't have another phone, I have to wait to obtain one before I do a safe mode test. And even if I do it's not realistic for me to test it that way because I'd have to spend hours typing away just to try to get the issue to occur (since it's not frequent like every 5 minutes).
I'm suspecting some data or a setting is getting transferred over from my previous backup that's affecting google keyboard or something of the sort. My next step will be a factory reset, and then reinstalling everything bit by bit manually. Of course I have to link my google account, but I won't have it automatically restore the backup. If that doesn't help then I'm at a loss. At that point I'd probably pick up a cheap Pixel 2XL as my daily, and use my P6Pro in safe mode as much as I can to try to trigger the issue I guess?
The Phone:
Pixel 6 Pro
Not Rooted
November 5 Update
Set up done using my google account to restore all apps and settings, not cable
Click to expand...
Click to collapse
I've heard of freezing problems from others related to gboard. This would indeed appear to be a software flaw. I've never really used gboard since the first step for me was google-free AOSP, then put in my sim card and start using it (I don't like spyware).
Simplest solution for you would likely be to try a different soft keyboard. Personally, I would suggest finding one on f-droid rather than play store because open source.
For what it's worth, I've been using GBoard for 5+ years and have never had a problem.
96carboard said:
I've heard of freezing problems from others related to gboard. This would indeed appear to be a software flaw. I've never really used gboard since the first step for me was google-free AOSP, then put in my sim card and start using it (I don't like spyware).
Simplest solution for you would likely be to try a different soft keyboard. Personally, I would suggest finding one on f-droid rather than play store because open source.
Click to expand...
Click to collapse
I used to root back in the day and use a custom ROM. If I do that there's no automatic updates right? Have to reload a new ROM for updates?
MarkAnthony121 said:
I used to root back in the day and use a custom ROM. If I do that there's no automatic updates right? Have to reload a new ROM for updates?
Click to expand...
Click to collapse
Depends on the ROM. I believe GrapheneOS has OTA updates. I know some others over the years have had that, too. Certainly not most custom ROMs but some.
roirraW edor ehT said:
Depends on the ROM. I believe GrapheneOS has OTA updates. I know some others over the years have had that, too. Certainly not most custom ROMs but some.
Click to expand...
Click to collapse
Thanks for all the help. (sorry for posting twice, I tried to delete the other) And I did appreciate the extra info so that I understood WHY I needed to do it this way and how it all functions. Two final questions. On modern phones like this one, does running a custom rom really improve battery/performance much? It's already pretty snappy for me, so I feel if I don't care about customizability it's probably not worth the effort for minimal reward. And second question, will the flash tool give me the option to clear both slots ?
Oh and third, is it ok to link my google account, (to get my contacts and such) as long as I'm not restoring any backups from it?
MarkAnthony121 said:
Thanks for all the help. (sorry for posting twice, I tried to delete the other) And I did appreciate the extra info so that I understood WHY I needed to do it this way and how it all functions.
Click to expand...
Click to collapse
You're very welcome!
MarkAnthony121 said:
Two final questions. On modern phones like this one, does running a custom rom really improve battery/performance much?
Click to expand...
Click to collapse
In my opinion, no, but the object of some ROMs (like GrapheneOS) are more geared towards very much increased security and avoidance of all the Google data-collecting that goes on with everything Google, although you can use some or most Google apps with GrapheneOS if you choose.
I've never actually tried GrapheneOS, though - I've only kept up with the two threads about them because I was curious about it. To me, starting with my first Pixel (I never owned a Nexus device), I liked stock Android way better for my purposes.
But just as for a lot of phone-related subjects, the answer to this question is very subjective. What's right for me isn't right for everyone. Everyone's needs are different. The only way of knowing for sure is to try it. You might try something and very quickly say "to heck with that, I'm going back", or you might say "oh, I like this loads better". I'm not a betting man unless something is a near 100% chance, so it's really a toss-up whether you would like a different ROM or not.
Also, how I handle my battery works great for me - but it wouldn't for everyone. I don't charge the phone until it gets down to 25%, and I try not to let it get any lower than 25%. I only charge the phone up to 75% when I can. I never charge overnight, and I never quick charge. That 50% range of battery still lasts me about 24 hours. My Pixel 1 battery is in great shape because of this habit. My wife's, on the other hand, since she didn't do this - her battery on her old Pixel 1 is relatively shot.
MarkAnthony121 said:
It's already pretty snappy for me, so I feel if I don't care about customizability it's probably not worth the effort for minimal reward.
Click to expand...
Click to collapse
Sounds as if you already have made up your mind to me. I mean, that's how I feel, and I like using Google's services for the most part. I'm more a function over form person. While I don't want something downright fugly, I really don't care what things look like - only how they do what I want them to do. Yet again, "how they do what I want them to do" is very subjective. The Samsung Galaxy Note 10+ didn't do what my wife and I wanted it to do, but we were both spoiled on the Pixel 1 before that. We don't regret our choice to go back to Pixel via the 6 Pro. For others, the Samsung phones are what they need.
MarkAnthony121 said:
And second question, will the flash tool give me the option to clear both slots ?
Click to expand...
Click to collapse
You don't want to "clear" both slots, you want to flash both slots. In answer to your question, I don't think you'll have a choice via the site (or offline flashing the full factory image). In other words, both slots are going to get flashed whether you like it or not. You would have to go to extra efforts to *not* flash both slots. Hence yet another reason why you don't have to worry about that aspect.
Google's official methods would never flash only one slot by default. That would be just plain idiotic of them.
Before you ask, the reason I recommend the site rather than offline flashing of the full factory image is:
It's more user-friendly.
It has solved problems when manually flashing the full factory image has not for some others with particular problems.
MarkAnthony121 said:
Oh and third, is it ok to link my google account, (to get my contacts and such) as long as I'm not restoring any backups from it?
Click to expand...
Click to collapse
Yes, absolutely, although in some cases I've recommended going completely fresh and not even doing that, at least before testing long enough to see if you have the issue. You certainly could go without putting your Google account in, etc, but I don't feel that's warranted at this point. The only time I think you should do that, in this case, is if you do it the other way (with your Google account), and you still have the same problem right away (without installing any additional apps).
Just remember don't install any additional apps to start with, long enough to be sure that the problem isn't happening. I know it's a painful process - I've done this before on several devices for different reasons. Usually, the cause of issues becomes evident but it's possible it won't be completely obvious.
FYI, just putting your Google account in will, I believe, possibly still automatically restore your phone's most basic settings but I could be wrong about that. You could always try it without your account at first, use the phone in it's limited state for long enough to know there's no problem, and only then put your Google account in.
Related
ok recently when im using my evo, and i do some multitasking, the freaking phone keeps turning off and restarts itself, at the beggining i thought ok maybe it frost or something, but now every other day im using it and im in the internet and facebook and other apps, it freezes for a bit and restarts itself. which is annnnoyyyying me cuz i loose everything i was doinggggg....ANY SOLUTIONS WHATS THE PROBLEM, IS IT THE PHONE???
Are u rooted.... if u are have u tried other roms with multiple wipes before the flash? Also my old evo did that after i rooted it and i could not find a fix but luckily i broke the screen an got a new one that dosent have that issue!
i forgot to ask are u saying a full reboot or just to the boot screen?
My first guess would be that you deleted something that the system needs to run. I believe you cannot delete friendstream, calender, etc some stupid apps that you might believe are completely useless but somehow HTC integrated them into the system as necessary system files.
Also did you fiddle with your SetCPU or kernals? Using setcpu to alter your CPU frequency can result in system crashes and different kernals have different set vcores. If the vcore is too low for your chip it does not have enough juice to operate properly and therefore crashes.
If you are stock then I'm not sure what it could be...
no this phone is not rooted (itz cuz i dont know how too lol), and its exactly how it came when i first got it,
the only things im running is
launcher pro plus as my default launcher. and just normal widgets like fancy widget and custom icons nothing major.
everything works perfect, but it keeps restart itself after a do alot of multitasking, cuz usually a app will get the "Force close" when its not working but for me it just freezes and restart itself , it goes to the "Sprint logo & 4g start up" just like how it would do when you first start your phone, the only thing is doesnt do is that it doesnt shot the HTC EVO 4G IN THE BEGGINING, JUST THE SPRINT AND 4G LOGO, than everything reloads itself on the screen.
and it was like this before u switched to the new launcher?
Interesting... Have you scanned your phone for any malware? Perhaps there is something there that should not be.
Here is what I would do:
Factory reset and run the phone stock without any apps for a day. If you still have issues - switch phones ASAP.
If you do not have issues after the reset, start installing one app at a time till you find the one that is buggy.
Hope this helps.
lgevo said:
and it was like this before u switched to the new launcher?
Click to expand...
Click to collapse
yes, i install and uninstall the launcher and did a factory reset to the phone and it still the same way.. just seeing if other ppl have had this problem, if its the phone itself or the sprint service connection.
I'm really surprised your phone is not rooted. I was going to guess you were OC'd just a little too high. My Dad had similar problems with his unrooted EVO before the 2.2 update. I never narrowed it down but I think it was a problem with Beautiful Widgets. I loaded a bunch of non-root apps on his phone (LP, handcent, BW, etc.), trying to set him up, and he was plagued with reboots so he wiped it all and went back to 100% stock. I still can't convince him to root.
aalopez10 said:
yes, i install and uninstall the launcher and did a factory reset to the phone and it still the same way.. just seeing if other ppl have had this problem, if its the phone itself or the sprint service connection.
Click to expand...
Click to collapse
Its a combination of things really.
1) HTC is not known for having the best build quality. Motorola, for example, is light years ahead.
2) The Android marketplace is not regulated like the Appstore. You will frequently get force closed apps because 1) Apps are regulated by the devs, not Google and 2) there is just a huge abundance of Android phones with many differences between them.
Your phone should not be resetting itself. A force close is different than a reboot. I would call HTC/Sprint and ask for a different phone. Might want to add the fact that none of your friends Evos do this so it is singled out to yours specifically.
thanks, i might just do that but all sprint ever freaking does is that they gonna do a reset of the phone and i already did that, I KNOW WHAT IM DOING WITH MY PHONE,
and it would be nice to learn how to root, cuz i been thinking of doing for a whileeee after 2.2 update...and see if i can fix this problem.
aalopez10 said:
thanks, i might just do that but all sprint ever freaking does is that they gonna do a reset of the phone and i already did that, I KNOW WHAT IM DOING WITH MY PHONE,
and it would be nice to learn how to root, cuz i been thinking of doing for a whileeee after 2.2 update...and see if i can fix this problem.
Click to expand...
Click to collapse
My 2 cents:
Don't root with a problem already present. 99% of the members here will not be able to help you with any of the issues you might run into. Only the developers will be able to help with real issues. That being said, since you already have a problem the worst thing you can do is void your warranty by rooting.
werxen said:
My 2 cents:
Don't root with a problem already present. 99% of the members here will not be able to help you with any of the issues you might run into. Only the developers will be able to help with real issues. That being said, since you already have a problem the worst thing you can do is void your warranty by rooting.
Click to expand...
Click to collapse
This is not accurate..
80% of the members here ARE able to help, but 90% of those members will choose not to if you are rude and disrespectful like some other people choose to be.
Rooting your phone may very well fix your problems.
It may not help at all, but many of the roms available are far more stable than stock.
Uninstall all of your non-stock apps and see if the problem persists. If it does not then you know it was a software problem and you can either take the plunge and root and go from there, or reinstall your apps one by one and see when you start having problems again. If you uninstall all non-stock apps and you still have issues then you may have a hardware problem in which case you should try to get your ohone replaced especially if you are still in your 30 days.
Keep in mind that even if you root and technically void your warranty a) your warranty being void is at the discretion of the CS rep you talk to and b) rooting does NOT void your insurance and your insurance covers manufacturing defects at no cost to you.
Try to learn some basic troubleshooting habits and avoid things like: homophobic comments, advising members to kill themselves, excessive swearing, calling people trolls when you are clearly being a troll yourself, and you will get all the advice you ask for.
Unrevoked has been pulled temporarily for some bugfixing so rooting 2.2 is actually not possible right now until they re-release it, or you find a copy of Unrevoked 3 somewhere (which is a bad idea, only use an official copy made available by the Unrevoked team) so take some time to read up, ask questions and understand some of the fundamentals of what you are getting into before you do something like break your wifi and not realize it's an easy fix then come on here and freak out.
Rooting is intimidating before you do it the first few times, but if you follow the guides to the letter and stay calm you'll be just fine. Just don't forget the staying calm part. There isn't much you can do to your phone that is irreversible, it's just a matter of preparing for potential problems and knowing what steps to take to recover from them.
If you are remotely inclined to learn how to root your phone then do it!! But only if you have enough time to devote to what will soon become your new hobby/obsession, it's that much fun
werxen said:
When was the last time you actually gave anything to a thread or these forums? Honestly bro everything I have seen you post is useless and non-technical in every aspect. Not trying to be mean to you but stop trying to help when you don't give good advice. We get it, you have a high post count. Good for you.
Click to expand...
Click to collapse
You're an idiot, the only posts of mine you've probably seen are responses to your offensive drivel. I don't care what you think of me, and am not about to provide you with proof that I know my ****. I don't care about post count and the advice I give is sound.
Look in a mirror.
No offense, but why is this still an issue? If OP did a factory reset, which is assumed to bring the phone back to a clean stock, and this problem still persists then the obvious solution would be to get a replacement. Yes, a replacement could take some time to arrive, but if this is a hardware issue, any amount of troubleshooting on the software side wouldn't matter. Then again, maybe you have a faulty micro-sd card and could be simple as swapping for a new one. Anyways, if you did a MSL/factory reset to a clean slate and your phone still intermittenly reboots, go get a new one. Good luck.
mizzos4 said:
No offense, but why is this still an issue? If OP did a factory reset, which is assumed to bring the phone back to a clean stock, and this problem still persists then the obvious solution would be to get a replacement. Yes, a replacement could take some time to arrive, but if this is a hardware issue, any amount of troubleshooting on the software side wouldn't matter. Then again, maybe you have a faulty micro-sd card and could be simple as swapping for a new one. Anyways, if you did a MSL/factory reset to a clean slate and your phone still intermittenly reboots, go get a new one. Good luck.
Click to expand...
Click to collapse
Agreed! Refrain from rooting because that will void your warranty.
aalopez10 said:
yes, i install and uninstall the launcher and did a factory reset to the phone and it still the same way.. just seeing if other ppl have had this problem, if its the phone itself or the sprint service connection.
Click to expand...
Click to collapse
I think what he meant was weather or not this still happens without installing launcherpro at all, when you're just running the default launcher. Also, does it still happen if you remove/uninstall all of your widgets/apps? If yes, and this still happens with no widgets running, and no apps installed, you may want to talk to Sprint about an exchange.
Sent from my blah blah blah blah
Hi all,
bit of an emergency here. I am running rooted Chroma rom, just went into twrp to backup my EPS, and upon reboot it is saying I need to enter my password. I have done this several times. Now, it keeps saying the password is incorrect, and after the 5th time, there is no option to reset it! Help please!! Don't feel like wiping my phone again...
greves1 said:
Hi all,
bit of an emergency here. I am running rooted Chroma rom, just went into twrp to backup my EPS, and upon reboot it is saying I need to enter my password. I have done this several times. Now, it keeps saying the password is incorrect, and after the 5th time, there is no option to reset it! Help please!! Don't feel like wiping my phone again...
Click to expand...
Click to collapse
You can search that but might as wipe in the meantime. Get yourself a working phone.
bobby janow said:
You can search that but might as wipe in the meantime. Get yourself a working phone.
Click to expand...
Click to collapse
Thanks for the reply. Going through the post-wipe setup now. Grrrr. It's just that I entered the password a bunch of times, and it always worked. Just on reboot from recovery it didnt. Now I'm afraid to go back into twrp...
Anyone know if this could be caused by some android security feature that doesnt like systemless root, xposed, etc.
greves1 said:
Hi all,
bit of an emergency here. I am running rooted Chroma rom, just went into twrp to backup my EPS, and upon reboot it is saying I need to enter my password. I have done this several times. Now, it keeps saying the password is incorrect, and after the 5th time, there is no option to reset it! Help please!! Don't feel like wiping my phone again...
Click to expand...
Click to collapse
I assume this is the same problem as the Nexus 6P. You need to disable the security before making a TWRP backup. The fix is:
After restoring the nandroid, boot into twrp and then delete /data/sytem/locksettings.db. If that doesn't fix it, delete the locksettings.db-shm and locksettings.db-wal in the same location. If that doesn't fix it either, delete gatekeeper.password.key and gatekeeper.pattern.key in the same location.
Click to expand...
Click to collapse
KennyG123 said:
I assume this is the same problem as the Nexus 6P. You need to disable the security before making a TWRP backup. The fix is:
Click to expand...
Click to collapse
Thanks for this fix. I'll keep it in mind next time. My broader question is now about security in general, since there seems to be a way to remove security from our roms?? For example, if someone got ahold of your phone, couldnt they just follow these steps to get in? Is this just a side-effect of unlocking the phone that is unavoidable? If I'm missing something about how to maintain security in the unlocked/rooted environment, please let me know. I've looked around but I haven't found any great guides for best practices regarding nandroids/security, etc. Thanks all!
greves1 said:
Thanks for this fix. I'll keep it in mind next time. My broader question is now about security in general, since there seems to be a way to remove security from our roms?? For example, if someone got ahold of your phone, couldnt they just follow these steps to get in? Is this just a side-effect of unlocking the phone that is unavoidable? If I'm missing something about how to maintain security in the unlocked/rooted environment, please let me know. I've looked around but I haven't found any great guides for best practices regarding nandroids/security, etc. Thanks all!
Click to expand...
Click to collapse
Rooting is in itself the biggest security risk. This is why carriers are working with manufacturers to make many phones fully locked and unrootable. Our main security expert Jcase does not use a rooted phone. He recommends if you need to root, go ahead, make the changes you want, then quickly unroot. So sure, if someone stole your phone they could follow that procedure to get into it. They could also just force a fresh stock version on it to wipe everything. Security and locks are meant to keep out honest people and slow down the dishonest.
KennyG123 said:
Rooting is in itself the biggest security risk. This is why carriers are working with manufacturers to make many phones fully locked and unrootable. Our main security expert Jcase does not use a rooted phone. He recommends if you need to root, go ahead, make the changes you want, then quickly unroot. So sure, if someone stole your phone they could follow that procedure to get into it. They could also just force a fresh stock version on it to wipe everything. Security and locks are meant to keep out honest people and slow down the dishonest.
Click to expand...
Click to collapse
Just so I'm clear, the only thing keeping a stock phone safe is that when its locked, it can't be unlocked/rooted because the option to allow oem unlocking/adb connections are not (or should not be) checked in the developer options, is that correct? From what you're saying, as long as those two boxes are checked, there is essentially nothing stopping someone from wiping out your password and getting into your device. I'd love to run unrooted, but would adaway still have an effect? I'm thinking that the definitions are already applied, so maybe it would work unrooted. But cf.lumen, which I love and can't find the same functionality anywhere else, seems to always "enable interactive shell" on boot. Would this work unrooted? But again, as long so you're doing all this stuff, you can't lock your bootloader again, can you? Or can you lock it on a stock rom with the kind of modifications I'm talking about. I read that locking bootloader while having a custom rom loaded can cause a brick, although I'm not quite sure why. Couldn't you just always get into fastboot to unlock it again?
greves1 said:
Just so I'm clear, the only thing keeping a stock phone safe is that when its locked, it can't be unlocked/rooted because the option to allow oem unlocking/adb connections are not (or should not be) checked in the developer options, is that correct? From what you're saying, as long as those two boxes are checked, there is essentially nothing stopping someone from wiping out your password and getting into your device. I'd love to run unrooted, but would adaway still have an effect? I'm thinking that the definitions are already applied, so maybe it would work unrooted. But cf.lumen, which I love and can't find the same functionality anywhere else, seems to always "enable interactive shell" on boot. Would this work unrooted? But again, as long so you're doing all this stuff, you can't lock your bootloader again, can you? Or can you lock it on a stock rom with the kind of modifications I'm talking about. I read that locking bootloader while having a custom rom loaded can cause a brick, although I'm not quite sure why. Couldn't you just always get into fastboot to unlock it again?
Click to expand...
Click to collapse
Pfew...so many questions...there are always vulnerabilities out there that hackers can find..like Stagefright...but a rooted phone is the most vulnerable. So having a phone with a locked bootloader and unrooted is the best security...still not guaranteed against every possible thing. But it is the best...now what are you trying to protect? Your data...or someone being able to wipe and use the phone as their own? All you can do really is try to protect from a phone being hacked remotely...and a rooted phone is like leaving the safe door open. But if someone steals your phone, there are always nefarious ways to make it usable.
KennyG123 said:
Pfew...so many questions...there are always vulnerabilities out there that hackers can find..like Stagefright...but a rooted phone is the most vulnerable. So having a phone with a locked bootloader and unrooted is the best security...still not guaranteed against every possible thing. But it is the best...now what are you trying to protect? Your data...or someone being able to wipe and use the phone as their own? All you can do really is try to protect from a phone being hacked remotely...and a rooted phone is like leaving the safe door open. But if someone steals your phone, there are always nefarious ways to make it usable.
Click to expand...
Click to collapse
Yeah, sorry for the wall of questions. I am just trying to wrap my head around some of these issues. At the end of the day, I don't really keep sensitive data on the phone, although it would not be good if a bad actor got into my gmail, for instance. I suppose I should migrate the last of my sensitive accounts to a secondary email, so no password resets could be initiated from a stolen phone. It's always a tradeoff between convenience and security I know. It's also a little worrysome that simply unlocking the phone activates it for androidpay. An unlocked phone stolen out of someone's hand is essentially the same as stealing all the credit cards in their wallet. It would be nice if android pay allowed an additional fingreprint/pin/password to make the transaction. Anyway, I'm now taking my own thread way off topic. Thanks for the insights though.
greves1 said:
Yeah, sorry for the wall of questions. I am just trying to wrap my head around some of these issues. At the end of the day, I don't really keep sensitive data on the phone, although it would not be good if a bad actor got into my gmail, for instance. I suppose I should migrate the last of my sensitive accounts to a secondary email, so no password resets could be initiated from a stolen phone. It's always a tradeoff between convenience and security I know. It's also a little worrysome that simply unlocking the phone activates it for androidpay. An unlocked phone stolen out of someone's hand is essentially the same as stealing all the credit cards in their wallet. It would be nice if android pay allowed an additional fingreprint/pin/password to make the transaction. Anyway, I'm now taking my own thread way off topic. Thanks for the insights though.
Click to expand...
Click to collapse
For most phones that have fingerprint security Android Pay can be set up that way. I won't use it anyway because it would be crazy to hand a waiter your unlocked phone, or to have to follow him to the register. It would only be useful to me in the supermarket but I am carrying a credit card anyway. But that is one thing people forget, rooting a phone means removing the main security.
KennyG123 said:
For most phones that have fingerprint security Android Pay can be set up that way. I won't use it anyway because it would be crazy to hand a waiter your unlocked phone, or to have to follow him to the register. It would only be useful to me in the supermarket but I am carrying a credit card anyway. But that is one thing people forget, rooting a phone means removing the main security.
Click to expand...
Click to collapse
N5X and android pay seems to tell me to just "unlock your phone" and hold it close to the reader. No need for an additional fingerprint. And no option to require this in settings...
greves1 said:
N5X and android pay seems to tell me to just "unlock your phone" and hold it close to the reader. No need for an additional fingerprint. And no option to require this in settings...
Click to expand...
Click to collapse
Yes, that should get you to the authorization screen and then if you have fingerprint set up should ask you for the fingerprint to authorize. Android Pay also now works on phones without fingerprint sensors so that is why they provide those simple instructions. Final authorization instructions will appear on your screen.
KennyG123 said:
Yes, that should get you to the authorization screen and then if you have fingerprint set up should ask you for the fingerprint to authorize. Android Pay also now works on phones without fingerprint sensors so that is why they provide those simple instructions. Final authorization instructions will appear on your screen.
Click to expand...
Click to collapse
Ah, great to know. Thanks.
greves1 said:
Ah, great to know. Thanks.
Click to expand...
Click to collapse
Unfortunately I can't test that theory since I am on a custom ROM and also Xposed. But everything I read says it should utilize the fingerprint if available.
KennyG123 said:
Unfortunately I can't test that theory since I am on a custom ROM and also Xposed. But everything I read says it should utilize the fingerprint if available.
Click to expand...
Click to collapse
Real word use shows that android pay does not ask for an additional fingerprint at the time of use. It's just as the instructions say, as long as your phone is unlocked at the time it is held up to the scanner, androidpay will work. I kind of wish they allowed for the additional security of an at-scan fingerprint read, but oh well. I have yet to test if the password/pin can be removed by the methods discussed in this thread, and androidpay working after defeating this security. If it does, then this is obviously a major security vulnerability of having an unlocked phone and using androidpay at the same time. Probably not more dangerous in terms of protecting against CC thieves, since they can just swipe a card stolen from your wallet at a terminal, but you probably wouldn't want to keep too many cards on your phone. Again, I haven't tested this out, if a fingerprint is still required to get in after a password database defeat, but someone should do this test.
If you have your phone lost or stolen just cancel your cards as if it happened to your wallet. Simple no?
Hello,
The vibration motor has suddenly failed on my phone. It now hardly vibrates at all and is extremely loud.
The problem seems more or less identical to this one watch?v=ZPqGD2uGG4o if you are curious.
The sound doesn't come from the speakers and I have no reason to believe it could possible be a software issue. Ie no recent installs or updates.
First thing I did was contact google. They had me boot into safemode to see if the problem persists. It does. However they now require that I reformat the phone.
This leads me to my question on how I can backup ALL app data. I have 400+ apps and it would suck to have to reset them all and or lose data.
I can sync phone contacts and such but without root I don't have a way of backing everything up.
Or is there another way to get Google to actually get me a replacement?
Thank you for your time.
If you're bootloader unlocked then root it and use Titanium backup, save it to the computer afterwards. Then unroot and factory reset as they ask. I'd probably not do that but if you have to get a new device, well then you have to. Maybe there is another way, but I've not seen it. Non root backup apps don't backup and restore your data reliably. If you are bootloader locked then I do believe you're out of luck. Pretty lousy of them to make you do that. If they just sent you a new one then you could copy from the old to the new. Maybe suggest that to them.
When you set up the new pixel using info from an old device, how much data is transferred? That may be an option.
I just went from rooted with custom ROM to full stock unrooted. All of my apps restored from the play store. I had to log into a few, but others seemed to retain app data, like Strava for instance. Google's back up seems to be getting better and better. I use SMS backup and restore for SMS/MMS because Google's backup service does not support MMS.
Well in case anyone is wondering... I bit the bullet and did the factory reset. The problem still exists of course.
Rant ahead, sorry/
There is an odd sound coming from within the device itself (not the speakers) and Google blames software? Is there some hidden second speaker inside?? It quite dumb and infuriating.
Even if there was doubt you would think running in safe mode which disables all the third party software would be enough to prove it.
It took me hours to copy everything and make sure everything was backed up. I don't blame the rep, he told me he HAD to make me do this. Honestly, I kinda wish I would have just told him I did it and it didn't work since there was no way it could have been software.
Well now a refurbished replacement is on the way. Which isn't ideal either. It has an issue that isn't too uncommon. I can find a dozen posts online about it which means there is probably hundreds of people with this problem at least. Now I have to put up with a refurbished which probably has a battery worse off as well as who knows what else.
This whole phone feels rushed, to be honest, and I regret buying it.
I won't be buying any more google hardware unless either they change in the future or the particular device has months of reviews.
/End rant
bobby janow said:
If you're bootloader unlocked then root it and use Titanium backup, save it to the computer afterwards. Then unroot and factory reset as they ask. I'd probably not do that but if you have to get a new device, well then you have to. Maybe there is another way, but I've not seen it. Non root backup apps don't backup and restore your data reliably. If you are bootloader locked then I do believe you're out of luck. Pretty lousy of them to make you do that. If they just sent you a new one then you could copy from the old to the new. Maybe suggest that to them.
Click to expand...
Click to collapse
I didn't know you could unroot and make it seem like it didn't happen. This is what I should have done. Thanks for the suggestion.
"If they just sent you a new one then you could copy from the old to the new. Maybe suggest that to them" I suggested this to them several times. One guy told me he wasn't allowed to even rma it until I reformat despite there being no way its a hardware issue.
mlin said:
When you set up the new pixel using info from an old device, how much data is transferred? That may be an option.
I just went from rooted with custom ROM to full stock unrooted. All of my apps restored from the play store. I had to log into a few, but others seemed to retain app data, like Strava for instance. Google's back up seems to be getting better and better. I use SMS backup and restore for SMS/MMS because Google's backup service does not support MMS.
Click to expand...
Click to collapse
If I had the replacement phone up front then transfering is easy. Google even has a built in mechanism, but google wouldn't RMA it and have one sent out until AFTER resetting it. A lot of data is synced but my 400+ apps, none of them seem to sync via the backup and restore feature. I also have 80+gbs of other files beside pictures. I bought the 128gb for a reason... Thanks for the suggestion.
Can anyone tell me details of what can be transferred from an old phone to a new P6P using the provided quick switch adapter? Can it transfer all apps and their data or only the ones with Google backup capability?
Thanks in advance!
The "ordinary" transfer won't restore your app settings, like your passwords/logins/in-app data.
Google One Backup is supposed to do that, even though it never worked for me. In the end I had to use swiftbackup whilst having root to have a decent backup/transfer experience.
--
There is some sort of auto-login system that some apps support, so Google logs you in automatically into the app once you first open them after transfering all your stuff, but that has nothing to do with the transfer/backup. Sadly, only very few apps support that.
Morgrain said:
The "ordinary" transfer won't restore your app settings, like your passwords/logins/in-app data.
Google One Backup is supposed to do that, even though it never worked for me. In the end I had to use swiftbackup whilst having root to have a decent backup/transfer experience.
--
There is some sort of auto-login system that some apps support, so Google logs you in automatically into the app once you first open them after transfering all your stuff, but that has nothing to do with the transfer/backup. Sadly, only very few apps support that.
Click to expand...
Click to collapse
Thank you, that's what I was afraid of. I can't believe that Google doesn't want to create a proper backup or transfer solution. So bad. I guess SwiftBackup it is...
mko000 said:
Can anyone tell me details of what can be transferred from an old phone to a new P6P using the provided quick switch adapter? Can it transfer all apps and their data or only the ones with Google backup capability?
Thanks in advance!
Click to expand...
Click to collapse
Been into android since the T-Mobile G1 days and I'm a firm believer in setting up a new phone from scratch. Did my wifes from her OnePlus 7 Pro and the screen would freeze every 4-6 hors. Did a FDR and it's been running great for the last 3 days. Your always going to get bits and pieces from the last OS that don't belong on your new OS when transferring from another phone.
ggrant3876 said:
Been into android since the T-Mobile G1 days and I'm a firm believer in setting up a new phone from scratch. Did my wifes from her OnePlus 7 Pro and the screen would freeze every 4-6 hors. Did a FDR and it's been running great for the last 3 days. Your always going to get bits and pieces from the last OS that don't belong on your new OS when transferring from another phone.
Click to expand...
Click to collapse
This makes more and more sense now a days!
Google wants to sell the cloud as much as possible. I restore GoogleOne backups from the cloud and I'm usually satisfied with the results.
I used to start from scratch but I stopped at some point several years ago. I just want my phone to work the way I'm used to. I don't use the stock launcher anyway, I use Nova Launcher Prime. Later on, I integrate elements from the new Android version and widgets/capabilities into my current Nova setup.
I never used the quick switch adapter and Google's transfer tool. I always root my phone and use Titanium Backup to restore my apps. Although, on Android 12, I think I'm gonna go for Swift Backup which I've heard good things about!
I'm still using my 4 XL for now, not sure if I want to jump on the 6 Pro with an unofficial alpha version of Magisk :/
Ghisy said:
I never used the quick switch adapter and Google's transfer tool. I always root my phone and use Titanium Backup to restore my apps. Although, on Android 12, I think I'm gonna go for Swift Backup which I've heard good things about!
I'm still using my 4 XL for now, not sure if I want to jump on the 6 Pro with an unofficial alpha version of Magisk :/
Click to expand...
Click to collapse
I'd advise you to wait at least for the first or second rollout of bug fixes if you are keen on root, as of now there are a lot of software quirks that might be firmware related; if you root now, upgrading to the next monthly update might be a nightmare. As far as I can see right now, every successful root requires a full factory reset (not the bootloader unlock reset!). And every "update" will aswell (maybe the community will find a way around that, but we don't know right now).
ggrant3876 said:
Been into android since the T-Mobile G1 days and I'm a firm believer in setting up a new phone from scratch. Did my wifes from her OnePlus 7 Pro and the screen would freeze every 4-6 hors. Did a FDR and it's been running great for the last 3 days. Your always going to get bits and pieces from the last OS that don't belong on your new OS when transferring from another phone.
Click to expand...
Click to collapse
100% on board with this. Whenever I clean flash (new phone or new OS update) I start from scratch. Download or sideload all my apps anew. Takes several hours to set up but well worth it in the long run.
Morgrain said:
I'd advise you to wait at least for the first or second rollout of bug fixes if you are keen on root, as of now there are a lot of software quirks that might be firmware related; if you root now, upgrading to the next monthly update might be a nightmare. As far as I can see right now, every successful root requires a full factory reset (not the bootloader unlock reset!). And every "update" will aswell (maybe the community will find a way around that, but we don't know right now).
Click to expand...
Click to collapse
Yeah, I've been reading as much as I can about root and it's not super fun right now. It remains to be seen if we can update monthly without wiping. Otherwise, that would be a MAJOR pita.
I'm gonna be traveling in about 2 weeks and I was hoping to bring my 6 Pro with me. My 4 XL is perfectly fine but not sure the battery will last while traveling. We'll see.
Back a couple of weeks ago or so at least two people mentioned they weren't receiving automatic updates to their apps. I can't find the thread now when I search for it - was probably posts buried in one of the existing threads.
I was having a problem with one particular app yesterday, and I was wondering if it needed an update. It didn't, the problem was probably the particular company's, but I noticed there were over 40 apps that needed updates, and just now I received a notification that 24 apps had updates available.
I chose to update them all, and then after they updated I started checking each of them one by one on the Play Store, and they were all set to not Auto update. I've had this before but only work select apps, not a bunch.
I don't know if it's related to me using Swift Backup to restore only some apps' data or what could do this. Even Swift Backup was set not to auto-update.
It's frustrating that after all this time there's no way to just get a list of those set but to auto-update and not, and be able to toggle a bunch all from one screen instead of each individually.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I keep getting 'unable to update' or whatever. Some apps only update by manual update
Hmm, that's an oddity. I'll start with some simple guesses for what could potentially be causing such an issue.
This hasn't happened to me yet, however, I don't use any backup apps after a full wipe or a phone swap; so that could potentially be affecting your device's apps. But also - and this probably isn't related to the problem - but do you disable verity and verification each time that you flash an update? So many people have been saying that it is no longer necessary, however, I have been doing it every single time just in case. Lastly, you are definitely using the correct factory image from Google's site, right? If you purchased the phone directly from Google, you're not supposed to use the image labeled as "For US Carriers" (although I'm not sure that using that image anyway would cause this issue)... These are all things that I've learned/started doing just to play it safe.
*Edit* - Oh, and which Google Play system update are you rocking?
fil3s said:
I keep getting 'unable to update' or whatever. Some apps only update by manual update
Click to expand...
Click to collapse
Interesting! Have you looked at any of those apps' individual checkboxes to see if they're set to auto-update?
NippleSauce said:
Hmm, that's an oddity. I'll start with some simple guesses for what could potentially be causing such an issue.
Click to expand...
Click to collapse
Hi, thanks for your suggestions on the subject.
Update of sorts: I scrolled through all 256 apps (not all of them user apps, and now uninstalled two) and didn't detect any particular pattern to the ones which had the checkbox set and which didn't. I believe among stock (in the firmware) installed apps that they were usually checked but I didn't pay close attention if any of those were not. I believe there were a few that were not.
At least 75% of the apps, but definitely not all - even not all of the user-installed apps, had auto-updates disabled.
As a side note, besides the usual pain of having to check that setting for each individual app, it's especially a pain to try to hit the 3-dot menu button right beside the curved edge of the screen, 250+ times. There was more than one app that it took several trials and errors to click the menu button.
NippleSauce said:
This hasn't happened to me yet, however, I don't use any backup apps after a full wipe or a phone swap; so that could potentially be affecting your device's apps.
Click to expand...
Click to collapse
The most recent time I factory reset, I only restored backups through Swift backup for particular apps that don't implement Google's cloud backup for the app data. I didn't restore the actual apps, just the data. Previous to that, I had actually had Google's cloud backup restore everything. I always do and have never had any obvious problems for several years now.
NippleSauce said:
But also - and this probably isn't related to the problem - but do you disable verity and verification each time that you flash an update? So many people have been saying that it is no longer necessary, however, I have been doing it every single time just in case.
Click to expand...
Click to collapse
I did disable them the last time that I flashed because I knew I was going to be flashing the updated CleanSlate kernel and I wasn't sure if it was still going to be necessary. At this point, I don't remember if I later flashed verity and verification without disabling them (to enable them).
When the January update arrives, I plan on not disabling verity and verification. I know that the CleanSlate kernel has been updated to not require those being disabled.
NippleSauce said:
Lastly, you are definitely using the correct factory image from Google's site, right? If you purchased the phone directly from Google, you're not supposed to use the image labeled as "For US Carriers" (although I'm not sure that using that image anyway would cause this issue)... These are all things that I've learned/started doing just to play it safe.
Click to expand...
Click to collapse
I am on raven-sq1d.211205.017-factory-bf3da4b2 - for all U.S. Carriers.
You are the second or third person who has said in this section that the US Carrier image isn't the correct one if using the factory unlocked variant. I'd like to know what the source is of this information, as no one has pointed to an article or official Google source saying one way or the other.
At this point, over two months since my wife and I received our P6Ps, I don't remember the exact firmware that was on it, nor the exact OTA version that was available immediately - either one of the following two:
SD1A.210817.019.B1, Oct 2021, AT&T
or
SD1A.210817.019.C2, Oct 2021, T-Mobile (US), USCC, Google Fi, CA, & TW carriers.
I tend to keep things simple when possible and my interpretation and advice to everyone who has asked what update they should flash is simply, whichever one matches your carrier. After all, they contain radio optimizations geared towards the carrier(s) available in those areas. Certainly, all of the firmware versions work on any bootloader unlocked Pixel, but without evidence to the contrary, I have no reason to think I shouldn't be flashing the one for U.S. Carriers, and the December one that didn't specify a particular place would be for "everywhere else" other than the three others which did specify.
If you can lead me to the solid information that says I shouldn't, I'd greatly appreciate it. I'm not trying to be contrary or argumentative - I'm just genuinely curious what the source is for this information. It would have to be a very solid source for me to change my thought on the matter.
NippleSauce said:
*Edit* - Oh, and which Google Play system update are you rocking?
Click to expand...
Click to collapse
I am on the November Play System update, with no update available.
Before I accidentally factory reset my phone three weeks ago, I had gotten the December Play System update. I remember reporting at the time in a thread here which someone made about the Play System update that the phone reported the update to December was ~650 MB, which was tons larger than what most were reporting as ~50 MB or so. As others have speculated, there are probably multiple updates available in the same month sometimes, so perhaps I was on an older October update before that, and most others were already on November - just speculation, though.
I didn't root right away because I was waiting on all the positive reports on success and methods, and then I had to wait for a time I felt comfortable taking the time necessary to set everything up on the freshly factory reset phone. I believe I had unlocked the bootloader immediately, as I knew that would factory reset and would be necessary for rooting, but of course then there was the disabling verity and verification which I didn't know about when I unlocked the bootloader, anyway, so I did that later, and then I had to factory reset yet again.
For the record, I haven't had any other problems, like others have.
Interesting! Have you looked at any of those apps' individual checkboxes to see if they're set to auto-update?
Click to expand...
Click to collapse
Yeah it's setup to automatically update as I have unlimited wifi. I just get one or two apps fail to update about once a day.
fil3s said:
Yeah it's setup to automatically update as I have unlimited wifi. I just get one or two apps fail to update about once a day.
Click to expand...
Click to collapse
You took a look at my screenshots in the OP? I just want to make sure you and I are talking about the same thing. My Play Store settings, in general, have always (or at least for many, many years) been set to auto-update over both Wi-Fi and mobile data connections (I used to do Wi-Fi only a long time ago as well), however, each app's page in the Play Store has its own individual checkbox for auto-update located in the upper right corner's 3-dot menu, which is independent of the overall Play Store settings for auto-update, and takes overrides it, at least when the general setting for the Play Store is to auto-update.
I haven't had the issue you're having with 'unable to update' or anything similar, for what it's worth.
roirraW edor ehT said:
You took a look at my screenshots in the OP? I just want to make sure you and I are talking about the same thing. My Play Store settings, in general, have always (or at least for many, many years) been set to auto-update over both Wi-Fi and mobile data connections (I used to do Wi-Fi only a long time ago as well), however, each app's page in the Play Store has its own individual checkbox for auto-update located in the upper right corner's 3-dot menu, which is independent of the overall Play Store settings for auto-update, and takes overrides it, at least when the general setting for the Play Store is to auto-update.
I haven't had the issue you're having with 'unable to update' or anything similar, for what it's worth.
Click to expand...
Click to collapse
I use swift backup Pro also, but haven't used it on my p6pro yet.
Yeah sorry about that I didn't read your post properly. Blame the psyche meds I'm on, or my frontal lobe damage
fil3s said:
I use swift backup Pro also, but haven't used it on my p6pro yet.
Yeah sorry about that I didn't read your post properly. Blame the psyche meds I'm on, or my frontal lobe damage
Click to expand...
Click to collapse
LOL!!! No sweat.
I've been noticing the same. However I also saw this issue on my OP8T running LOS18.1. I do manually disable auto-update on YouTube (since I use Vanced) all other apps are set to auto-update. I wonder if it has to do with having even one app not set to not auto-update or if it is Swift (since Google doesn't restore my 2FA Authenticator data and until recently you couldn't export).
As for the question about Verity, mine is off from when I rooted right after Dec update when it was required.
Based on your response, I'm going to guess that this could either be due to the incorrect factory image use or due to the use of SwiftBackup. We're both on the Play System update from November - so that seems like an unlikely cause.
I, personally, never backup anything before wiping my phone. Does that make it a real pain in the arse to setup again? It definitely does =(.
As for my information regarding the correct factory image to use, I don't have the links to where that information was discussed, however, it was stated by a Google employee on the Google forums and was also (I believe) discussed on Twitter from a Google rep. I may not be 100% correct on the other discussion happening on Twitter as I don't fully remember discovering everything related to the factory image confusion being that it was one of the first things that I had corrected after getting this phone. But, when I went to the correct factory image, a lot of the odd things that my phone would experience (such as an abnormally high usage temperature no matter what) were resolved. Perhaps the different P6 variants have a slightly different hardware design that isn't mentioned anywhere?
Also for the disable verity and verification stuff - I still don't think it could be causing the issue, however, I've been sure to disable it with every single factory image update. So perhaps this has more of an impact on stability than was previously thought .
Regardless, my apologies for my crummy formatting in this response and also for possibly missing some details. I'm on mobile right now and have had a severe traumatic brain injury about a year and a half ago. After reading the short message from @fil3s , it seems that XDA is the safe ground for us brain injury nerds, haha =)
NippleSauce said:
Based on your response, I'm going to guess that this could either be due to the incorrect factory image use or due to the use of SwiftBackup. We're both on the Play System update from November - so that seems like an unlikely cause.
Click to expand...
Click to collapse
Of those two choices, I would lean towards Swift Backup, however, I doubt if it's that either since I definitely didn't restore anything using Swift for so many of my apps - I only restored very select apps' data after I had restored from Google Backup. Hell, it could be a Google Backup/Restore bug for all I know. I've had nothing (else) but good experience with restores from Google over the last five years or so.
NippleSauce said:
I, personally, never backup anything before wiping my phone. Does that make it a real pain in the arse to setup again? It definitely does =(.
Click to expand...
Click to collapse
I prefer to manually over-backup and restore only what I need to as I need it - any app data that Google's Cloud Backup didn't restore for apps that are slightly more painful to remember how I had them set up. It's better for me to not need the data but have it backed up, then need it and not have it backed up.
NippleSauce said:
As for my information regarding the correct factory image to use, I don't have the links to where that information was discussed, however, it was stated by a Google employee on the Google forums and was also (I believe) discussed on Twitter from a Google rep. I may not be 100% correct on the other discussion happening on Twitter as I don't fully remember discovering everything related to the factory image confusion being that it was one of the first things that I had corrected after getting this phone. But, when I went to the correct factory image, a lot of the odd things that my phone would experience (such as an abnormally high usage temperature no matter what) were resolved. Perhaps the different P6 variants have a slightly different hardware design that isn't mentioned anywhere?
Click to expand...
Click to collapse
I'll definitely need more than that before I switch my thinking on that subject, but thank you for sharing what you do know or remember. The easy way to find out, of course, is for someone who's completely on stock unrooted, preferably even bootloader still locked, running on AT&T like me to share with us which December OTA they received - for those relatively few who actually received it.
I may go ahead and make a question thread/XDA poll on the subject: Poll only for non-rooted factory unlocked P6P owners running on any US carrier who received the December over the air update, not manually flashed
NippleSauce said:
Also for the disable verity and verification stuff - I still don't think it could be causing the issue, however, I've been sure to disable it with every single factory image update. So perhaps this has more of an impact on stability than was previously thought .
Click to expand...
Click to collapse
I doubt if it is a factor for stability, or at least only indirectly through the increased security they provide. See the section on that subject with information that other more knowledgeable folks in the first four posts in my P6P thread that I have in my signature below if it's information you're not already aware of.
NippleSauce said:
Regardless, my apologies for my crummy formatting in this response and also for possibly missing some details. I'm on mobile right now and have had a severe traumatic brain injury about a year and a half ago. After reading the short message from @fil3s , it seems that XDA is the safe ground for us brain injury nerds, haha =)
Click to expand...
Click to collapse
I'm very sorry to hear about your brain injury. I hope you cope as well as possible. Don't worry about formatting - even if it's not easy to read/digest XDA's newer software makes it easier to break up into chunks and respond to individual portions, from what I remember over the old software. My brain issues are more psychological (so far), however, the Army did feed us beef that was potentially from mad cows in Britain in the mid-1980s, but the only way anyone will ever know if I was exposed to it is if I die from it - at least that was the information that was given to me when I found out about that almost 20 years ago when I went to give blood.
roirraW edor ehT said:
Back a couple of weeks ago or so at least two people mentioned they weren't receiving automatic updates to their apps. I can't find the thread now when I search for it - was probably posts buried in one of the existing threads.
I was having a problem with one particular app yesterday, and I was wondering if it needed an update. It didn't, the problem was probably the particular company's, but I noticed there were over 40 apps that needed updates, and just now I received a notification that 24 apps had updates available.
I chose to update them all, and then after they updated I started checking each of them one by one on the Play Store, and they were all set to not Auto update. I've had this before but only work select apps, not a bunch.
I don't know if it's related to me using Swift Backup to restore only some apps' data or what could do this. Even Swift Backup was set not to auto-update.
It's frustrating that after all this time there's no way to just get a list of those set but to auto-update and not, and be able to toggle a bunch all from one screen instead of each individually.
View attachment 5503665
View attachment 5503667
Click to expand...
Click to collapse
I've been noticing the same with my Pixel 3 and 6 Pro. When I upgraded my 3 to Android 12, I had trouble updating apps and checked the setting. It was turned off, for almost every app (I never did turn any of these boxes off manually). I guess it's an Android 12 thing-y / bug. Since my P6 Pro also had several of these settings turned off, it has probably nothing to do with upgrading to Android 12, but Android 12 in general just being a buggy mess.
Morgrain said:
I've been noticing the same with my Pixel 3 and 6 Pro. When I upgraded my 3 to Android 12, I had trouble updating apps and checked the setting. It was turned off, for almost every app (I never did turn any of these boxes off manually). I guess it's an Android 12 thing-y / bug. Since my P6 Pro also had several of these settings turned off, it has probably nothing to do with upgrading to Android 12, but Android 12 in general just being a buggy mess.
Click to expand...
Click to collapse
Thanks! That does sound more likely. I guess I can officially list myself as having one problem.