Android Pie "Pixel Setup" won't go away - Google Pixel XL Questions & Answers

After the Pie update, my phone was wonky. So I did the sane thing we all do, I did a factory reset.
I then restored all my data and settings in the usual ways. All is well so far. It even seemed to fix the battery drain issue.
BUT!!! I have this stupid thing that won't go away, and I have zero idea what to do or what it is!! It seems to think I want to copy my old data from my old phone, but of course, its the same exact phone. Not sure what to do? Cannot figure out which process it is to kill it. Rummaged around ADB and found nothing
https://lh3.googleusercontent.com/H...A0fSUmMvjQpzm73XCWvPpGMrL017bn8=w587-h1043-no

Just click it and at the bottom it should say "don't copy" click it. It may ask you some other things but other things like changing wallpaper or don't size.
You can try going to your setting and dismissing the "recommended actions" at the top, then restart your phone, but idk if it will help.

Related

Bluetooth on by default at first boot up?!?!?! Need Input

Can you tell me if bluetooth is ON or OFF by default at startup after a factory reset? I swear that it was off the first time I booted up but now it is on. Makes me wonder if it was infected or changed. Anyone know if the default was changed? Thanks
Eutility said:
Can you tell me if bluetooth is ON or OFF by default at startup after a factory reset? I swear that it was off the first time I booted up but now it is on. Makes me wonder if it was infected or changed. Anyone know if the default was changed? Thanks
Click to expand...
Click to collapse
Bluetooth may or may not be "on" but it should not be "connected" or "remember" any devices if you did a factory reset.
However, without wiping internal SD and data, you are subject to "potential weird things" that can happen.
It's why I never report a bug unless I made absolutely sure to wipe data and internal SD before trying to reproduce an issue.
Bluetooth has been turned on by default for all the software versions I've used.
Upon a factory flash or reset, Bluetooth will be enabled but no devices will connect/be remembered.
On a side note, No application can "infect" an android. Most of these antivirus applications are complete bullcrap. Dont get me wrong, there are some dangerous apps out there, but you would still have to give the app permissions and accessibility access For it to do any damage. even then, simply uninstalling them Will remove everything.
Thanks for your responses. I do appreciate it. Well, unfortunately I have had multiple phones infected by ex-neighbors. I literally would lose control over the phone and during calls they would make beeping sounds like I had hit a key. Once I flashed my phone outside of town and they kept messing with it. I had always thought they had a tool which enables persistence even through flashing, but it may be that they are using Signaling System 7 (SS7) and are just reinfecting them remotely. (you can watch a 60 minute special on SS7 if u like, available online) They were using an IMSI catcher when I lived next door to them. With the Pixel XL I was having ALOT of data use and reset the phone after some weird stuff happened that I had come to recognize as likely signs of being compromised, and I think put in a new SIM with a new phone #. It was much better after that. It was a nightmare with them and one of them even followed me home after work a month after I moved away. Not to mention steal things like laundry soap and put them on their side of the street in front of my house. Creeps. At this point it is just pathetic and weird. Just trying to take reasonable precautions now and live my life. If they want to waste their time that is sad.
Really glad to hear the bluetooth being there is not a deviance from default. Thanks

Do Not Disturb Issues

So this is driving me nuts. I just picked up an S7 Active, and restored my data from Samsung Cloud. Everything restored fine except for Settings. That part fails every time. No big deal, I thought. I just set it up again how I like it. As soon as I got everything how I wanted it, Do Not Disturb immediately started acting super-weird. It turns on by itself, and it takes 2-3 times of turning it off to get it to stay off. When I finally get it off, it resets the settings (stays custom, but turns off all alarms, calls, and messages). I want it to allow alarms and calls/messages from favorites, and as soon as I enable those, it automatically turns Do Not Disturb back on. Turning it off again starts the whole loop over. Clearly, my Do Not Disturb settings are corrupt. Is there a way to wipe those settings, without wiping the phone and starting fresh?
Not a super helpful response, sorry in advance, but i think you may have answered your own question. Sounds like something got corupt in the copy over.
With out manually looking at all of the settings and or alot of trial and error... you may just have to reset it and start fresh...
But when you say wiping the phone, i just want to confirm that your intentions arnt to go factory reset... just do a "reset settings" and "reset network settings" dont wipe your whole phone.
Acinko said:
Not a super helpful response, sorry in advance, but i think you may have answered your own question. Sounds like something got corupt in the copy over.
With out manually looking at all of the settings and or alot of trial and error... you may just have to reset it and start fresh...
But when you say wiping the phone, i just want to confirm that your intentions arnt to go factory reset... just do a "reset settings" and "reset network settings" dont wipe your whole phone.
Click to expand...
Click to collapse
Yes, factory reset, or worst case, ODIN flash the firmware. I just wanted to see if it was something anyone else had run into. I'll tackle this over the weekend. Thanks for the response!
bug
I had turned facebook and gmail to silent notifications. DND has not turned on and media volume has not turned to zero since allowing these apps to show with sound again.
Think every time a notification comes in media volume is set to 0 and DND turned on.

A lot of features suddenly disappeared after a reboot.

Hello, everyone.
I had used Oxygen OS 9.0.9 for a fairly long time with no problems.
However, after a recent reboot, suddenly the system started to behave in a strange way.
Namely:
1) Notifications completely disappeared. The notification drawer is always absolutely empty, even the persistent ones are missing.
2) Multitasking disappeared. Tapping the square fake button does nothing.
3) The extended tiles drawer, the one that appears after you slide down the second time, after you have drawn the notification screen, doesn't appear at all.
4) Tapping on the "build number" line in the settings does nothing, no "you are a developer now" message, nothing.
5) The reboot menu shrunk to two entries "reboot" and "off", as if the phone hasn't been unlocked.
The phone is unlocked and rooted with magisk, but not much more, no tuning done.
Any ideas what to do? How to get the missing features back?
lockywolf said:
Hello, everyone.
I had used Oxygen OS 9.0.9 for a fairly long time with no problems.
However, after a recent reboot, suddenly the system started to behave in a strange way.
Namely:
1) Notifications completely disappeared. The notification drawer is always absolutely empty, even the persistent ones are missing.
2) Multitasking disappeared. Tapping the square fake button does nothing.
3) The extended tiles drawer, the one that appears after you slide down the second time, after you have drawn the notification screen, doesn't appear at all.
4) Tapping on the "build number" line in the settings does nothing, no "you are a developer now" message, nothing.
5) The reboot menu shrunk to two entries "reboot" and "off", as if the phone hasn't been unlocked.
The phone is unlocked and rooted with magisk, but not much more, no tuning done.
Any ideas what to do? How to get the missing features back?
Click to expand...
Click to collapse
Why won't you try a re flash and check again ?
Sure. I'd just want to exhaust the less radical measures first.
lockywolf said:
Sure. I'd just want to exhaust the less radical measures first.
Click to expand...
Click to collapse
No idea man . This is first time I am encountering this problem.
Try reflashing and check.
And meanwhile why neglecting A10 ?
Heard about problems with call recordings, and those are vital to me.
lockywolf said:
Heard about problems with call recordings, and those are vital to me.
Click to expand...
Click to collapse
Oh. Great
So, I fixed this problem by doing a clean flash of 9.0.11.
Kinda a radical solution, and I have spent a lot of time on backups and such, but hey...
Curiously, a dirty flash, although succeeded, did not solve the issue, as didn't the "Factory Reset" from the Settings menu.
I had to wipe "system" and "vendor" partitions to proceed.
lockywolf said:
So, I fixed this problem by doing a clean flash of 9.0.11.
Kinda a radical solution, and I have spent a lot of time on backups and such, but hey...
Curiously, a dirty flash, although succeeded, did not solve the issue, as didn't the "Factory Reset" from the Settings menu.
I had to wipe "system" and "vendor" partitions to proceed.
Click to expand...
Click to collapse
Like I expected, clean flash helped .
Bw the call recording issue in the A10 can be resolved by deactivating OK Google command of speech.
I just thought, you should know.
But I guarantee their ram management is ****ty in A10.
Well, a clean flash is not really a proper solution, since we still don't know what was the root cause of such a weird behavior.
The killer feature of A10 for me would be charging from OTG, for doing backups. I need to check though, how much time it takes to make a backup after a clean flash.
lockywolf said:
Well, a clean flash is not really a proper solution, since we still don't know what was the root cause of such a weird behavior.
The killer feature of A10 for me would be charging from OTG, for doing backups. I need to check though, how much time it takes to make a backup after a clean flash.
Click to expand...
Click to collapse
For me it's ram management is ****ty. Ultra garbage.
I am getting 5gb of ram usage from 30 Apps I downloaded from play store

Persistent debris/moisture error

My wife has a G7 Thinq that has been having this problem for a while now. She gets the debris/moisture error when the phone has had no exposure to water at all. There is nothing in the port at all. No amount of drying/cleaning makes any difference. When the error occurs, she gets frequent notifications and can only charge the phone wirelessly. The only fix is to factory reset the phone. Then, it's fine for a while (it was 2-3 months this last time), as long as she does not restart the phone. It often, but not always, recurs after a restart. Once the error occurs, it persists until a factory reset.
Because it goes away after a factory reset, I'm inclined to think it's a software issue, but I've had no luck in identifying an app responsible for it. Has anyone else seen this behavior, or know how to solve it? It has the stock ROM on it, and I've wondered if a custom ROM would fix the problem. However, she likes the stock ROM, so I'm not exactly eager to change that.
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
blackhawk said:
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
Click to expand...
Click to collapse
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
drfarmkid said:
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
Click to expand...
Click to collapse
If it didn't crop up right after the reload it indicates something that was added or a changed setting.
Clearing the system cache can only be done off the boot menu. This can cure many types of erratic behaviors.
For individual apks clearing their data can do the trick when clearing the cache doesn't.
A hard reboot simulates pulling the battery or pull the battery if it's removable.
I run many of my system apks as the factory loaded versions because of issues with their updated versions.
Next reload pay close attention to any updates.
If it's software caused it may prove a challenge to track down.
Could be an internal hardware failure. Try a known good cable and charger. Google the issue, others may have had the same problem and have a solution.
Clearing the cache, factory resetting the phone, etc. didn't work this time around. I was going to try putting a custom ROM on it, until I started looking into it and found out the bootloader can't be unlocked (it's the T-mobile version).
In the service menu (dial *#546368#*710#) there is a setting to shut off moisture detection. That also didn't fix it. However, I did find something in there that I don't understand that might be informative. My daughter has the same phone, so I looked through some things in there comparing the two. Under a menu called "Type-C checker" there is a table where the two phones differ. My wife's phone says:
Supported ModeUFP DFPMODEFAULTPOWER ROLEFAULTDATA ROLEFAULTVCONNN
My daughter's phone says "NONE" where my wife's says "FAULT". Does that mean anything?
I'm now suspecting some sort of hardware fault, perhaps a short in the charging port. I can buy that daughter board with the USB port for ~$15. What are the odds replacing that will fix it?
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
Hopefully it's a permanent change.
Androids wuv attention...
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
hey, can you have found what was the issue because I have exactly same issue like your phone.

Question "At a Glance" no longer showing temperature on the lock screen

Hello,
I've had this issue since launch and I can't figure a way to fix this. Basically, when I first got my phone, the lock screen was displaying the temperature under the time, with a "tap to learn more" button. And after clicking that, it simply vanished from existence, never to be seen again. It does show itself back when there's a Google Calendar event, but the temperature is gone. And after doing a factory reset recently, the temperature is back, with the "tap to learn more" (which I don’t plan to press, now that I know this will make it go away)
Is there a way to fix this? Thanks
That's a lot of overkill
Find the app and clear it's data next time.
There may be a conflict... like with the Google app*. Could be in settings, somewhere, or in notifications. Disable all power management for now... it will cause erratic behavior.
You need to play with it.
* that nasty little permission to change system settings... can be misused.
blackhawk said:
That's a lot of overkill
Find the app and clear it's data next time.
There may be a conflict... like with the Google app*. Could be in settings, somewhere, or in notifications. Disable all power management for now... it will cause erratic behavior.
You need to play with it.
* that nasty little permission to change system settings... can be misused.
Click to expand...
Click to collapse
I get it. But I had to reset my phone anyway.
My problem is that it shows the temperature, but as soon as I press the "tap to learn more" thing, it shows a slide about at a glance and it just goes away.
So I don't think it's a permission issue if it works just fine before clicking on the forsaken text
Andrew8578 said:
I get it. But I had to reset my phone anyway.
My problem is that it shows the temperature, but as soon as I press the "tap to learn more" thing, it shows a slide about at a glance and it just goes away.
So I don't think it's a permission issue if it works just fine before clicking on the forsaken text
Click to expand...
Click to collapse
You need to track down the associated apks first then look them over. It may be a glitch that you can correct or maybe resetting the apk data is the only way to correct it.
Try clearing the system cache.
Try it in Safe mode to rule out 3rd party apps.
blackhawk said:
You need to track down the associated apks first then look them over. It may be a glitch that you can correct or maybe resetting the apk data is the only way to correct it.
Try clearing the system cache.
Try it in Safe mode to rule out 3rd party apps.
Click to expand...
Click to collapse
The question is, does it even work for you? I understood that it will be fixed eventually but nah.
Also what kind of apk are you talking about? This is literally the lock screen
Andrew8578 said:
The question is, does it even work for you? I understood that it will be fixed eventually but nah.
Also what kind of apk are you talking about? This is literally the lock screen
Click to expand...
Click to collapse
I don't have that device but troubleshooting is troubleshooting. You need to dig around for the apk but it's most likely there under system apps.
It's possible the firmware flash was corrupted if so a factory reset won't work. More likey it's a glitch.
Hopefully someone here knows the answer but it's not a major issue. I would tend to just ignore it other then to play with it as a curiosity. No doubt you'll find better fish to fry...

Categories

Resources