Hello,
I used XiaomiADBFastbootTools to debloat my Poco F3 but now the Cast option doesn't work anymore. I'm not sure if that's the reason but it seems like it was. When I cast my phone detects my TV and my TV tries to connect for a while until it stops. Tried with two different TVs (Samsung and Hisense).
If debloating was the reason: What should I reinstall to make it work it again?
Here are the remaining services after debloating:
{
"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"
}
Hope anymore can help me.
Without knowing their dependencies... things can go amuck.
Downloads looks like it has potential.
Firewall blocking is a another option before you go full nuke. Karma Firewall uses almost no battery, a freeware VPN based firewall.
I have a Redmi Note 7 which works. I didn't do anything with Firewalls and similar.
I read somewhere that MiShare, MiConnectService and MiPlayClient might caused the problem but it just made Cast visible in the dropdown status bar. Otherwise same problem.
Here is the debloated stuff:
Clear the system cache, try a network reset.
When you disable apks without knowing their purpose/dependencies and especially when you take the shotgun approach, things tend to screw up.
Start from the beginning, again, if you can't ferret it out.
I prefer to use a package disabler app because you can easily enable/disable on the fly.
I cleared cache and reset network. Didn't work. Then I reisntalled all the bloatware. Still no effect. Then I tried to change my WiFi from 5Ghz to 2.4Ghz if that might cause troubles but also nothing.
How can I fix it? What else can I try?
zoocha said:
I cleared cache and reset network. Didn't work. Then I reisntalled all the bloatware. Still no effect. Then I tried to change my WiFi from 5Ghz to 2.4Ghz if that might cause troubles but also nothing.
How can I fix it? What else can I try?
Click to expand...
Click to collapse
So you undid all the changes you made?
Try a hard reboot. Same for the associated devices.
That's why I don't like playing with ADB much.
Is the cause there or is it a setting misconfiguration? The answer may be something simple but finding it may not be.
I don't use casting, check it's Google settings.
Maybe try clearing Google play Services data, it's harmless to do so. I do that a lot.
I think simply hard restarting my TV made the trick. At least that's what I did and it works now.
I still wanna debloat so what is safe to keep this function? This time I will disable instead of uninstall.
zoocha said:
I think simply hard restarting my TV made the trick. At least that's what I did and it works now.
I still wanna debloat so what is safe to keep this function? This time I will disable instead of uninstall.
Click to expand...
Click to collapse
Yay! Well it's your experiment... fun isn't it?
Been nice if all the junk wasn't there but it still beats a bloody ugly iPhone by a country mile
Yes experiment. Debloat app one by one, so you know which app cause the cast to malfunction.
pl1992aw said:
Yes experiment. Debloat app one by one, so you know which app cause the cast to malfunction.
Click to expand...
Click to collapse
Probably a Google app. There's a couple others that look like candidates, and a bunch almost certainly aren't. Start with prime suspects.
You can try using a Google Search to find clues to what each apk does. Sometimes you do.
I tested around but somehow casting doesn't work anymore. I debloated step by step during casting and conncection didn't close. Then later I had same issues like before. I did the same things like before to make it work again (enable everything, restart, reset conenctions) but nothing works. Enabling Certificate of Wireless Display also didn't do anything.
Could a factory reset help? Does a factory reset also revert all my debloating experiments or would uninstalled bloatware stay uninstalled? What would be the best I can do now?
zoocha said:
I tested around but somehow casting doesn't work anymore. I debloated step by step during casting and conncection didn't close. Then later I had same issues like before. I did the same things like before to make it work again (enable everything, restart, reset conenctions) but nothing works. Enabling Certificate of Wireless Display also didn't do anything.
Could a factory reset help? Does a factory reset also revert all my debloating experiments or would uninstalled bloatware stay uninstalled? What would be the best I can do now?
Click to expand...
Click to collapse
A factory reset will get it. I recommend you find the root cause though or you're likely to just do all over again.
zoocha said:
I debloated step by step during casting and conncection didn't close.
Click to expand...
Click to collapse
When you try disable one by one, it will not cut the already connected cast immediately.
Factory reset should help. If you need cast, but don't want to face more issues, then don't debloat.
To see the actual effect of debloat, it's done like this:
1) connect cast -> connected ok
2) disconnect cast
3) debloat 1 app -> then reboot phone
4) connect cast -> to check if that app affect your cast
then repeat.
I did a factory reset but it didn't work for unknown reasons. Then I tried out using Google Home on an Android TV which worked. It also worked on my TV with Fire TV Stick 4K using Airscreen but the casting quality seems worse than Mi cast function. Regular YouTube casting also worked.
Does anyone know why it doesn't work anymore even after a factory reset? Is there maybe something I can still do? Is the culprit maybe something that doesn't change after reset? I also did a factory reset with my TV without success. It just tries to connect all time and stops.
Is this maybe a MIUI problem? I'm using global ROM.
You should have reinstalled all of the debloated apps, then clear the cache using Cleaner and then proceed to do a factory reset.
If you still have the option to do so from the first step, try it out.
Nemix77 said:
You should have reinstalled all of the debloated apps, then clear the cache using Cleaner and then proceed to do a factory reset.
If you still have the option to do so from the first step, try it out.
Click to expand...
Click to collapse
I reinstalled everything before I reset and maybe I did clear cache too. I can't remember. Does the Cleaner app also clear hidden stuff?
Does factory reset hurt hardware much or not worth worrying about it? Otherwise I would give it another try.
Is there maybe another possibilty to fix it?
zoocha said:
I reinstalled everything before I reset and maybe I did clear cache too. I can't remember. Does the Cleaner app also clear hidden stuff?
Does factory reset hurt hardware much or not worth worrying about it? Otherwise I would give it another try.
Is there maybe another possibilty to fix it?
Click to expand...
Click to collapse
Factory resets are a waste of time unless the OS is old or damaged. It pretty hard to corrupt a stock Android OS. 3rd party apps can do it though or alter hidden settings not readily accessible. The only other reason for a factory reset is a major OS upgrade.
Otherwise don't do it; find the root cause and correct it. If you don't find the root cause you'll like just end up chasing your tail as the issue will likely return after the factory reset.
Lazy and inept techs push factory resets because it's easier than doing it the right way
My current OS load is over a year old, still fast and stable despite heavy usage. I had issues that I could have resorted to a factory reset to "solve" but I tracked down the root causes and corrected them. I learned by doing so as well. After being corrected they didn't impact the performance of my heavily optimized system.
All I do is routine maintenance like with SD Maid and occasional scans with Malwarebytes. I check the download folder for crap that doesn't belong there regularly. At some point I will do a factory reset and to that end all my critical data is backup and ready to go.
Android is a very stable and long lived platform if used properly.
What else can I try to find out the root? Undo debloating and factory reset doesn't work and I doubt and hope that I didn't mess up hardware somehow.
Airscreen/Chromecast works and I think TVs use Miracast right? Can this information help for further experiments?
Solution during I wrote this: Enabling "Disable Bluetooth A2DP Hardware" option seems to work. I should be satisfied but what does this mean for my original problem? I didn't do anything with this option before. Is the root of my problem now more traceable?
zoocha said:
What else can I try to find out the root? Undo debloating and factory reset doesn't work and I doubt and hope that I didn't mess up hardware somehow.
Airscreen/Chromecast works and I think TVs use Miracast right? Can this information help for further experiments?
Solution during I wrote this: Enabling "Disable Bluetooth A2DP Hardware" option seems to work. I should be satisfied but what does this mean for my original problem? I didn't do anything with this option before. Is the root of my problem now more traceable?
Click to expand...
Click to collapse
Factory reset completely restores the original OS no matter what you did previously unless you reflashed the firmware.
You found the issue, problem solved.
A 3rd party app may have toggled that setting unknown to you at the time. It can happen during an app uninstall as well.
Just be happy it was an easy fix
Download the latest version of mi cast apk from apkmirror and install it, i also faced this issue with samsung tv, i updated the cast app manually and now its working without any issue.
Related
Anyone running this tablet with the new Kitkat firmware who also uses Spotify app? Can you see if you can repeate my problem or if it works on your device?
The thing is that anytime I run Spotify under restricted profile or any other normal profile besides the main one, it instantly crashes with "Unfortunately, Spotify had stopped" with prompt for report or ok.
I did a dirty upgrade to Kitkat and already tried factory reset after it but no success. Next I will try factory reset and reinstall the fw if somebody confirms they have it working fine.
Co-re said:
Anyone running this tablet with the new Kitkat firmware who also uses Spotify app? Can you see if you can repeate my problem or if it works on your device?
The thing is that anytime I run Spotify under restricted profile or any other normal profile besides the main one, it instantly crashes with "Unfortunately, Spotify had stopped" with prompt for report or ok.
I did a dirty upgrade to Kitkat and already tried factory reset after it but no success. Next I will try factory reset and reinstall the fw if somebody confirms they have it working fine.
Click to expand...
Click to collapse
i just flashed kitkat over 4.3 to keep apps. Spotify works fine for me, have you tried reinstalling app ?
Under restricted profile too? I need to try clean flash I guess.
Co-re said:
Under restricted profile too? I need to try clean flash I guess.
Click to expand...
Click to collapse
DONT, i read your post wrongly and did not paid attention to the part where you stated that it works main account. I thought it was crashing there too, now i checked on second account, it crashes.
Sorry.
Ok, good to know if not the result I was hoping. Need to report this top them.
I'm sure there are other Spotify users around with this new FW installed. Can you please verify if you can run Spotify under secondary or restricted profiles or not.
I'm currently going through a somewhat frustrating discussion with their support where we get back to the cache things and how Android multi user profiles work over and over and I hope they will set up a test device to see if any 4.4.2 multi user system can run it. It'd be nice to get more info but I guess Spotify is not very big outside Scandinavia...
Wow, they eventually actually gave up with the comment: "At this point, Spotify does not support multiple profiles (users, accounts) on the same device on the version of your device." before going back to syncing playlist and other clearly unrelated stuff.
I would have thought that a company of this standing would push a bit harder
I'm quite sure this is not a rom/gapps/kernel related problem as it used to work. The only change to my system that I can imagine having any influence is installing greenify+disable services. Uninstalling them didn't solve the issue. I'm sure it's a messed up setting somewhere but I can'tbfind it. Reflashing rom (not pristine) didn't help. If anyone has an idea where to look for the setting, I'd rather not flash pristine & have to redownload everything again.
Can't change kocation status from quick panel
Can change status slider in settings but gps not working though it's 'on'.
henkmet said:
I'm quite sure this is not a rom/gapps/kernel related problem as it used to work. The only change to my system that I can imagine having any influence is installing greenify+disable services. Uninstalling them didn't solve the issue. I'm sure it's a messed up setting somewhere but I can'tbfind it. Reflashing rom (not pristine) didn't help. If anyone has an idea where to look for the setting, I'd rather not flash pristine & have to redownload everything again.
Can't change kocation status from quick panel
Can change status slider in settings but gps not working though it's 'on'.
Click to expand...
Click to collapse
You can format /data from CWM or restore to factory settings (both methods basically do the same thing) to check if it's a setting issue, as it does look like one. Especially the service disabling part. That would be one thing that you can do.
Note that, with this method, you will loose contacts, calendar entries, messages, and of course, all settings (but that's pretty much the point of the formatting). You won't loose images, videos, downloads since those are saved in another places (your /sdcard0 aka internal memory or /sdcard1 aka external memory).
Another method would be to manually re-enable those services that you turned off. You can do that by either redownloading the app you were using before and undoing everything, then uninstalling the app. Or by going to Settings -> Apps -> All and doing it from there. Though I would recommend the redownload option.
The advantage of this method is, of course, that you get to keep all your data intact. The disadvantage is that, unless the redownloading of the app + undoing the stuff you've done before works as intended, you will have to go through all the processes and see which one you need to re-enable.
Reflashing the ROM without formatting at least /data, won't change anything since it's gonna keep all the settings.
I tried to retrace which settings had been changed but gave up and did a factory restore. Issue solved (though I'll probably never know what setting was messed up)
henkmet said:
I tried to retrace which settings had been changed but gave up and did a factory restore. Issue solved (though I'll probably never know what setting was messed up)
Click to expand...
Click to collapse
Glad to hear the issue is solved now. In the future, I would recommend avoiding disabling services, if you can't foresee the ripple effect that it might trigger or if you don't have enough experience to know exactly what can or cannot be disabled. I, for one, don't know what each of those processes do or how are they related to one another, I never messed with those things and I generally prefer to be safe rather than sorry. So, I do backups of my contacts, messages, calendar entries. In case something goes wrong at some point, even a pristine installation of the ROM won't affect the data that I consider important since I can always restore it.
But we all learn from our mistakes. So, as a general suggestion, if it's not broken, don't fix it. And usually there are different, better, safer ways to accomplish the same thing. If you feel uncertain of the odds of your success, you might consider looking for alternatives before taking a final decision and messing up your phone.
And, as usual, we're here to help. That's what forums are for. So don't be afraid to ask. There will always be someone to help you out.
Hey All, Greetings from Australia.
I am facing some serious issues with my Pixel 6 Pro (well my 2nd brand new device). Looks like I have found a bug which causes the phone to enter a boot loop with no way to fix it. see below steps.
I have done the initial setup on the phone, entered my google account details, phone did its restore thing with no issues.
I activated my eSim service on the device, that seemed to work with no issues (data & calls working as should)
When entering the Call Settings via the Phone App, it immediately crashed, and displayed a Factory Data Reset screen.
It then displayed a recovery screen saying the OS is corrupt, and to perform a factory reset, when attempting this again, it will display multiple errors and continue to restart the phone and prompt for another factory reset
Not sure if the above makes sense, however this seems to be a serious flaw/bug with the new phone/OS, I've attached some pictures for reference and can provide a video of the boot loops.
To repeat, this is my 2nd Pixel 6 Pro device and the first phone was refunded due to the same above issue.
Has anyone experienced this behaviour before, as the phone is still relevantly new, I'm struggling.
Google Support are being absolutely useless thus far.
Looking at the attached video, you can see the eSim service turning off and on, IMO it seems that the eSim component / hardware on the phone is corrupt.
Troubleshooting Steps Perforemed.
1. Performed Full Factory Reset in recovery menu attached
2. Performed a full flash of the Factory Image using the Online Flash Tool - https://source.android.com/setup/contribute/flash
3. I have attempted Erasing the eSim in the Reset Menu, however this does absolutely nothing.
Thoughts??
{
"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"
}
Your browser is not able to display this video.
I just tried to recreate this and I did not get a crash. I'm also using an eSim. Its a weird bug for sure. Maybe it has to do with your carriers eSim. I'm using Google Fi.
Edit*
Just watched your video, that's crazy. Looks like a defective unit in my opinion, but what are the chances you got 2 of them. Have you tried setting it up on wifi, do app updates, then activate service?
eg1122 said:
I just tried to recreate this and I did not get a crash. I'm also using an eSim. Its a weird bug for sure. Maybe it has to do with your carriers eSim. I'm using Google Fi.
Edit*
Just watched your video, that's crazy. Looks like a defective unit in my opinion, but what are the chances you got 2 of them. Have you tried setting it up on wifi, do app updates, then activate service?
Click to expand...
Click to collapse
Hey eg1122
Thanks for attempting to replicate this , I would have felt horrible if you encountered the same issue, but thankfully not.
This definitely seems to be an issue with both my Carrier and eSim provisioning on the device.
To confirm, the behaviour was identical with both phones
Only solution I can think of is a physical sim card, at least until your carrier and/or Google fix it.
simon_mx5 said:
Hey All, Greetings from Australia.
I am facing some serious issues with my Pixel 6 Pro (well my 2nd brand new device). Looks like I have found a bug which causes the phone to enter a boot loop with no way to fix it. see below steps.
Click to expand...
Click to collapse
This just happened to me....aaaarrrrggg...now dealing with google support. Did you ever find a solution? I am with Telstra...so frustrating.
Update: Went to Telstra got a replacement physical sim and phone is back to working as it should...no more esim's for me. I hope this helps someone else.
OzBoy1 said:
This just happened to me....aaaarrrrggg...now dealing with google support. Did you ever find a solution? I am with Telstra...so frustrating.
Click to expand...
Click to collapse
No solution unfortunately, I just gave up on the idea of an e-sim
Not sure how this happened I had used call forwarding before with no issue but this time it was a PITA! I spent a couple of hours with google support and they couldn't help, a replacement was the option they provided.
The physical sim is the fix, I am not sure if you have to use the one that is associated with the eSim account (I did it worked) however I think it just needs a different sim to the eSim to use as set up. When setting up make sure you use the physical sim, not the eSim otherwise back to the boot loop. Once you get the phone set up go to Settings/System/Reset Options/Reset wifi, Mobile and Bluetooth then check the Erase downloaded SIMs, this will remove the problem.
I hope this helps someone else as it was a pain to reset and all the time lost when it was a pretty simple solution to fix....well as long as you have a physical sim handy!
Did you try the dialer commands for call forwarding?
cabagekiller said:
Did you try the dialer commands for call forwarding?
Click to expand...
Click to collapse
I used Phone/Settings/Calls/Call Fowarding.
I had major issues with this. Everything was working ok until i turned on call forwarding which sent the phone into a bootloop as above. I needed to insert a physical sim to get through the factory reset as it hung onto the esim otherwise and went back into another bootloop. Once the factory reset was done, i did another with sim data erase checked - and then when back up and running re-added the Telstra esim.
Whilst things where partially working i still had issues. I noticed that navigating to "Phone -> Settings -> Calling accounts" would crash the phone app.
I also noticed that the Telstra esim appeared as "null" in some places as it was unnamed. I gave the esim a name and now everything is working fine - i can access the Calling accounts menu.
Maybe the blank name causes the issues? This was on a Pixel 6 (not pro)
fish0 said:
I had major issues with this. Everything was working ok until i turned on call forwarding which sent the phone into a bootloop as above. I needed to insert a physical sim to get through the factory reset as it hung onto the esim otherwise and went back into another bootloop. Once the factory reset was done, i did another with sim data erase checked - and then when back up and running re-added the Telstra esim.
Whilst things where partially working i still had issues. I noticed that navigating to "Phone -> Settings -> Calling accounts" would crash the phone app.
I also noticed that the Telstra esim appeared as "null" in some places as it was unnamed. I gave the esim a name and now everything is working fine - i can access the Calling accounts menu.
Maybe the blank name causes the issues? This was on a Pixel 6 (not pro)
Click to expand...
Click to collapse
Sorry to hear about this, I know how frustrating this is. This issue did not go away for me, had ongoing issues, Ended up having to contact google support and they replaced the phone, haven't gone back to esim since. Good luck.
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.
My girlfriend can see everything I do on my phone, even listen in to my surroundings and spy on me with my camera. I've looked at all the running processes and I can't find the malware. Any advice besides a system reset? Thanks
She's probably just has your password mate. Change it or factory reset your device. If that doesn't work find a new gf.
tycox93 said:
She's probably just has your password mate. Change it or factory reset your device. If that doesn't work find a new gf.
Click to expand...
Click to collapse
Believe me it's not just the password. She's installed some kind of parental Spyware like MSpy
If you're sure that's what she has done, and not just a bit paranoid, then you should be able to find it if you got into safe mode. At least I believe so.
tycox93 said:
If you're sure that's what she has done, and not just a bit paranoid, then you should be able to find it if you got into safe mode. At least I believe so.
Click to expand...
Click to collapse
I'm 100% convinced that's what she's done but I'm not that tech savvy when it comes to phones so I'm not sure which processes are part of the Android OS and which processes are the spy app.
Ditch gf.
Factory reset, will purge anything she loaded. The bootloader is locked so the only thing she could hack is the user data partition, a factory reset clears this.
Delete Google and Samsung accounts in settings>factory reset from settings not recovery menu>don't set up your Google account initially>change Google and Samsung account passwords on another computer (PC or Mac), write down passwords and make them complicated, setup the Google account on phone then.
It is clean. Be careful what you then load and who you give access to your phone if anyone.
I had a phone bought on eBay which I think it was cloned
It was the Xiaomi mi mix fold 2. I kept sending me messages please close the screen mirroring ect..I tried to reset it but nothing worked. Someone cracked the ROM in my opinion. eBay refunded me in full. I think you shall better buy a new phone
If you're paranoid:
reset your computer without a network connection.
reset your phone and don't connect to wifi yet.
reset your home wifi modem/router
connect your devices and use a strong password.
After this only a specialist can hack you.
simrag said:
I had a phone bought on eBay which I think it was cloned
It was the Xiaomi mi mix fold 2. I kept sending me messages please close the screen mirroring ect..I tried to reset it but nothing worked. Someone cracked the ROM in my opinion. eBay refunded me in full. I think you shall better buy a new phone
Click to expand...
Click to collapse
No reason to replace the phone if it's a stock Samsung and it factory resets. As long as Knox isn't tripped it's still running with a stock rom and bootloader that haven't been altered and are still secure.
Odinsinces3 said:
If you're paranoid:
reset your computer without a network connection.
reset your phone and don't connect to wifi yet.
reset your home wifi modem/router
connect your devices and use a strong password.
After this only a specialist can hack you.
Click to expand...
Click to collapse
After reset it can't be accessed until account info is entered. My solution bypasses that entirely.
If he factory resets from recovery without first deleting Google and maybe Samsung accounts from the phone he may get locked out by FRP!
FPR is more wicked than any bad gf...
In Samsung's it's always best to factory reset from Settings rather than the boot menu. I redundantly make sure FRP won't be invoked by also deleting the accounts before the reset whenever possible*
*a boot loop or total system crash trashes this option, better hope the account password works...
How to stay away from Hackers?, How they simply get the access to hack our devices.
Everett34 said:
How to stay away from Hackers?, How they simply get the access to hack our devices.
Click to expand...
Click to collapse
They don't; most victims inadvertently install the malware themselves. Social media sites like WhatsApp, Tiktok etc are hunting grounds for hackers. Poor settings and app selection, clumsy browsing habits, side loading, unlocked bootloaders, no firewall in use, being careless what's downloaded, not keeping email in the cloud, allowing others physical access to the device, sharing drives, using unsecured wifi hotspots, not using Android 9 or higher... among others.