I tried to download an .xls file from a gmail I received. It failed initially when I chose "save". I tried again and it worked second time.
However I am left with a scrolling blue bar in the notifications like its an active download trying to complete. when will it time-out and fail. I cannot clear it. I tried restarting phone twice. The attempted download still scrolling.
any ideas?
Go to downloads within the apps tray and clear the download from there
That didn't work, but thanks for the suggestion.
finally found out how to kill a stuck/looping download from gmail etc.
go to settings / apps / all
Find the process called "download manager" and clear data.
simple yes, but frustrating when I could not find it and restarts didn't work to kill it. Thought timeout might have kicked in.
Ah that's good to know if it ever happens to me.
ty
mcgon1979 said:
That didn't work, but thanks for the suggestion.
finally found out how to kill a stuck/looping download from gmail etc.
go to settings / apps / all
Find the process called "download manager" and clear data.
simple yes, but frustrating when I could not find it and restarts didn't work to kill it. Thought timeout might have kicked in.
Click to expand...
Click to collapse
shiet man thank you very much i keep deleteing 6 downloads for 2 weeks... FINALLY!!!!!!!!!!!!!!!!!!!!!
I rooted without any issues and then went to turn off OTA by entering 3845#*yourversionnumber# and pressing Disable in WLAN OTA.
I am still getting the notification that the Upgrade is downloaded and ready to be installed. Is there a way to get rid of this? I tried to find the file (looked in Cache folder) but could not find it.
Thanks in advance
Doc
DocEsq said:
I rooted without any issues and then went to turn off OTA by entering 3845#*yourversionnumber# and pressing Disable in WLAN OTA.
I am still getting the notification that the Upgrade is downloaded and ready to be installed. Is there a way to get rid of this? I tried to find the file (looked in Cache folder) but could not find it.
Thanks in advance
Doc
Click to expand...
Click to collapse
Try clearing data on "download manager" in application manager.
I just got the notification and can't get rid of it either. Long press on notification -> app info takes me to Google Play Services.
I'm not sure how I can clear out the notification. I've already renamed LGFOTA.apk and cleared cached and DISABLED OTA in hidden menu.
Hello,
I just got my One Plus 3 a day ago and I have setup Nova Launcher as my Home Launcher. Installed my necessary apps. For some reason I cannot figure out, everytime I go into Settings, when I press the Home button, it asks what launcher to use as default. I always select Nova Launcher but when I go back to settings, it happens again. What is wrong with my Settings?
I have read that some apps act as a launcher so I installed Launcher Switcher and found that there are 3 launchers to choose from, OnePlus Launcher, Nova Launcher and File Manager. What is this File Manager App? I tried to go into Settings > App > File Manager but I cannot disable this.
Also I have read some apps that when they uninstalled those apps, the problem went away. For example is the Hotmail app. I don't have this app installed and so far, I just notice the problem after going in Settings App. Also, I have read that Nova Launcher will detect which app is causing the problem but I cannot see that on my side. No notification by Nova Launcher informing me of problematic apps that is causing the default home launcher to reset frequently.
I am not rooted, no custom recovery installed but I think my bootloader is unlocked because when I power ON my phone, I get the "It cannot be trusted" thing on boot up. OS version is 3.1.3
Thanks for the help.
[UPDATE]
1. I also encounter the problem after switching apps via Recents App button. For example I open Facebook, when I press Home button, its fine. I open Spotify, and press Home, its still fine. When I access Facebook via Recent Apps button, and then click Home, the problem occurs. Please help.
You can make your choice of launcher as default app by selecting in settings - home and select your default launcher
I had this exact same problem.
Your device has been flashed with a an unofficial rom (thats why you get that warning when switching the phone on for 5 seconds).
It was most probably done by whoever you bought the phone from. They usually do it to move from Hydrogen to Oxygen, but in the process they load in some crapware.
You need to flash your device to stock Oxygen using the official Rom.
allansy said:
Hello,
I just got my One Plus 3 a day ago and I have setup Nova Launcher as my Home Launcher. Installed my necessary apps. For some reason I cannot figure out, everytime I go into Settings, when I press the Home button, it asks what launcher to use as default. I always select Nova Launcher but when I go back to settings, it happens again. What is wrong with my Settings?
I have read that some apps act as a launcher so I installed Launcher Switcher and found that there are 3 launchers to choose from, OnePlus Launcher, Nova Launcher and File Manager. What is this File Manager App? I tried to go into Settings > App > File Manager but I cannot disable this.
Also I have read some apps that when they uninstalled those apps, the problem went away. For example is the Hotmail app. I don't have this app installed and so far, I just notice the problem after going in Settings App. Also, I have read that Nova Launcher will detect which app is causing the problem but I cannot see that on my side. No notification by Nova Launcher informing me of problematic apps that is causing the default home launcher to reset frequently.
I am not rooted, no custom recovery installed but I think my bootloader is unlocked because when I power ON my phone, I get the "It cannot be trusted" thing on boot up. OS version is 3.1.3
Thanks for the help.
[UPDATE]
1. I also encounter the problem after switching apps via Recents App button. For example I open Facebook, when I press Home button, its fine. I open Spotify, and press Home, its still fine. When I access Facebook via Recent Apps button, and then click Home, the problem occurs. Please help.
Click to expand...
Click to collapse
you can reinstall the firmware from official oneplus website and after flashing the latest firmware, go into developer options (you have to enable them first by going to about phone and tapping the build no. 7 times, then enable advance reboot and usb debugging.) do not personalise your phone or set it up. reboot into bootlader and using adb and fastboot run the command "fastboot oem lock" this will erase all your data and reset your phone again and you wont get the splash screen message again.
After months of trying I managed to change launcher on RKa701 device.
As owners of this device already know, another launcher can be installed on this device but you cannot set it as default because it will stuck, or wont launch or will not be displayed correctly. It simply conflicts with factory launcher and make unit unusable.
Factory launcher is very ugly but the problem with it is not just that , but unit needs it because radio, music, bluetooth and other apps wont work without it. As you can swap factory music app with another one you cant do that with radio and bluetooth.
Im not responsible if you mess something with your device. Proceed at your own will.
So here we go:
1. Root your device with latest kingroot ( i used latest 5.2 version) . Dont worry we will uninstall it later
2.When rooted it will ask for all kind of permission allow
3. With root explorer or some other app go to system/priv app and make a backup of launcher2.apk-copy it somwhere.
4. Download apk file of some launcher (can be any-we wil install our main launcher later) and put it in system/priv app. I used nova and renamed it to "launcher2" just in case. Install nova.
5. reboot or (if you want to uninstall root for good-choose factory reset) . After boot up nova launcher should be loaded instead main launcher. But WE ARE NOT FINISHED.
If you try to start radio, bluetooth or music app you will find that it cant be done because you removed factory launcher. The good thing is it should be booted, but it is not necessary for it to work in the background all the time.
6. So, install launcher2 that you backed up in step 3. It is now installed but it is not system app anymore.
7.Now. If you dont want to stick with nova launcher install the one you will use. I find car launcher pro best one out there.
8. Now, from google play download "autostart and Stay" app from google play. Install it.
9. Set service toggle of "autostart and Stay" to on.
11. In the app settings check "smart service on boot" and "pooling interval" on 5 seconds.
10. By usign "+" sign add launcher2.apk and launcher you choosed to use. On launcher2 make sure that "autostop" on boot completed is choosed and for the launcher you choosed "autostart" and "stay".
11. If you didnt do it already, using system app remover uninstall kingroot.
11. Reboot.
Thats it.
What we did?
With "autostart and Stay" we loaded but then stopped factory launcher and by checking "stay" we ensured that launcher we choose to use cant be stopped in the background by any other process-If you want you can choose "persist" instead of "stay" and set pooling interval on 60sec. It means that after using any other app more than 60 sec , you will be kicked out on home screen, but other apps you started wont be killed. It means that you can start radio or music, choose your track or tune and it will be working in the background even after you have been kicked to home screen. If you want to watch video, just extend pooling interval. 60 sec is enough for everyday use.
Thats it. Bye
Alright, this is a weird one! Only of few instances of the mystical "pixel is starting..." screen show up online and I'm mostly out of ideas at this point.
First, some background:
I was still on the December 5th update (QQ1A.191205.008). Stock, unlocked, rooted with Magisk. I hadn't yet flashed the patched Magisk boot image, it was running only by fastboot boot pachted.img. The only root-related App I had installed was Battery Charge Limiter.
What happened:
I created a custom theme & changed my wallpaper. I then used Activity Launcher to launch the "hidden" System UI Tuner. While in there I disabled the clock in the system tray. I also went into the "Plugins" menu and toggled the "enable" toggle on, then off (I thought more plugin options, whatever they may be, were hidden since they were not enabled...). I fiddled with a few more settings hiding/showing icons and hit the home button.
When I returned back to the homescreen, my wallpaper had changed back to the default Pink/purple Pixel 3 wallpaper. "Huh? System UI Tuner must have reset this." I changed the wallpaper again but it didn't even change. After a few more attempts (tried changing just lockscreen wallpaper, just homescreen, both; nothing would actually change), I rebooted the phone.
Upon booting back up, I was greeted with a "Pixel is starting..." screen that won't go away. This occurs before the lock screen, prior to letting me enter my PIN.
Attempted recovery steps already taken
Rebooted many times. (Which which would have booted the factory boot.img; see above background)
Tried booting into "safe mode." (Same "Pixel is starting..." screen comes up with the words "Safe mode" in the bottom left)
sideloaded the most recent OTA for my device (QQ1A.200105.002)
Booted corresponding Magisk patched boot.img
Has this happened to anyone before? Can anyone think of a way recover anything at this point? Luckily I had adb enabled before this happened and it still functions; logcat doesn't show anything that seems helpful, though. Since I cannot unlock the device, I can't use adb to recover any data. I really wish adb had a means of unlocking via PIN!
My next step is likely going to be to flash a factory image (probably QQ1A.191205.008 as that was what I was using prior to this happening) with "-w" removed and praying I can at least unlock the phone.
Data recovered!
Edit: Wow! I wasn't able to fix the "Pixel is starting..." issue, but I was able to use adb to recovery all my data. I will follow up with what I did shortly! Dodged a bullet... unbelievable!
I couldn't fix the "Pixel is starting..." issue. Factory Flashing (after removing -w) QQ1A.191205.008 resulted resulted in being stuck at the "G" screen. I flashed the QQ1A.200105.002 factory image (again with -w removed) and was left in the same "Pixel is starting..." state.
Here is where things get interesting:
Over adb I launched the Settings app:
Code:
adb shell am start -a android.settings.SETTINGS
Next, I went into "Security," which prompted for my PIN, and then removed the screen lock. After doing this, I was able to get into /sdcard in the ADB shell, something that was not possible before.
Back in the settings app, I enabled USB File Transfer and copied all my files & photos off. I was also able to launch apps from within the apps list in Settings. This let me export settings/data from other apps that allowed it. :good:
So it seems that entering your PIN in the Settings app also unlocks the phone!
Thanks for describing this and how you ended up resolving it. I am seeing the same "Pixel is starting". Flashing the (March 2020) factory image didn't fix mine either.
I was able to get into Settings by pulling down the notification shade while the "Pixel is starting" message shows. I removed my fingerprints and PIN.
I don't seem to be able to launch apps from within the apps list in Settings. Can you describe how you did that?
I've tried this:
Settings-->Apps & notifications-->App info--> {select any app and tried clicking on icon at top of screen} Nothing. Poked around a bit and tried various things but couldn't figure out how to launch an app from here. Thanks in advance.
docdl said:
I don't seem to be able to launch apps from within the apps list in Settings. Can you describe how you did that?
Click to expand...
Click to collapse
There should be a "Open" shortcut just below the app icon to the left of "Uninstall" (or "Disable" if it is a built-in app).
_Ra1n_ said:
Alright, this is a weird one! Only of few instances of the mystical "pixel is starting..." screen show up online and I'm mostly out of ideas at this point.
First, some background:
I was still on the December 5th update (QQ1A.191205.008). Stock, unlocked, rooted with Magisk. I hadn't yet flashed the patched Magisk boot image, it was running only by fastboot boot pachted.img. The only root-related App I had installed was Battery Charge Limiter.
What happened:
I created a custom theme & changed my wallpaper. I then used Activity Launcher to launch the "hidden" System UI Tuner. While in there I disabled the clock in the system tray. I also went into the "Plugins" menu and toggled the "enable" toggle on, then off (I thought more plugin options, whatever they may be, were hidden since they were not enabled...). I fiddled with a few more settings hiding/showing icons and hit the home button.
When I returned back to the homescreen, my wallpaper had changed back to the default Pink/purple Pixel 3 wallpaper. "Huh? System UI Tuner must have reset this." I changed the wallpaper again but it didn't even change. After a few more attempts (tried changing just lockscreen wallpaper, just homescreen, both; nothing would actually change), I rebooted the phone.
Upon booting back up, I was greeted with a "Pixel is starting..." screen that won't go away. This occurs before the lock screen, prior to letting me enter my PIN.
Attempted recovery steps already taken
Rebooted many times. (Which which would have booted the factory boot.img; see above background)
Tried booting into "safe mode." (Same "Pixel is starting..." screen comes up with the words "Safe mode" in the bottom left)
sideloaded the most recent OTA for my device (QQ1A.200105.002)
Booted corresponding Magisk patched boot.img
Has this happened to anyone before? Can anyone think of a way recover anything at this point? Luckily I had adb enabled before this happened and it still functions; logcat doesn't show anything that seems helpful, though. Since I cannot unlock the device, I can't use adb to recover any data. I really wish adb had a means of unlocking via PIN!
My next step is likely going to be to flash a factory image (probably QQ1A.191205.008 as that was what I was using prior to this happening) with "-w" removed and praying I can at least unlock the phone.
Data recovered!
Edit: Wow! I wasn't able to fix the "Pixel is starting..." issue, but I was able to use adb to recovery all my data. I will follow up with what I did shortly! Dodged a bullet... unbelievable!
Click to expand...
Click to collapse
Hey! I just ran into the same dilemma. I toggled the "plugins" setting in System UI tuner (by mistake), and my wallpaper went black. Then I decided to just reboot. I'm in the same "Pixel is starting" loop you described. I'm also stock, rooted with Magisk, on the January update. I just found that I can get into adb, but I'm a loss of what do to from here. I can't believe toggling a system UI tuner setting could cause a catastrophic crash. How did you end up solving this? Were you able to flash the full factory image while preserving your data? I honestly have no idea what do to at the moment. I'm gonna have to use an older device and research this more after work.
Edit: I was able to remove my security PIN via launching Settings through ADB, and therefore getting into some apps. I guess I'm more bothered by having to set up the device from scratch then I am losing any data. So time consuming. I'm assuming you ended up wiping the phone entirely and flashing a full factory image in the end? Geez. I miss my Moto devices and TWRP...
Ditamae said:
Hey! I just ran into the same dilemma. I toggled the "plugins" setting in System UI tuner (by mistake), and my wallpaper went black. Then I decided to just reboot. I'm in the same "Pixel is starting" loop you described.
Click to expand...
Click to collapse
Interesting! Exact same order of events.
Ditamae said:
Edit: I was able to remove my security PIN via launching Settings through ADB, and therefore getting into some apps. I guess I'm more bothered by having to set up the device from scratch then I am losing any data. So time consuming. I'm assuming you ended up wiping the phone entirely and flashing a full factory image in the end? Geez. I miss my Moto devices and TWRP...
Click to expand...
Click to collapse
Yes, I wiped completely. Used it as an excuse to flash LineageOS, something I had been planing on doing for a while anyway. I load very little on my devices to begin with so really its just typing in a few passwords.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
If so, take a look at the files within; that should be where SystemUI Tuner saves the settings you have selected. Maybe rename the directory & reboot so the settings can't be loaded?
Edit: Don't try messing around with anything until you're sure you got all of the data off the device though!
_Ra1n_ said:
Interesting! Exact same order of events.
Yes, I wiped completely. Used it as an excuse to flash LineageOS, something I had been planing on doing for a while anyway. I load very little on my devices to begin with so really its just typing in a few passwords.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
If so, take a look at the files within; that should be where SystemUI Tuner saves the settings you have selected. Maybe rename the directory & reboot so the settings can't be loaded?
Edit: Don't try messing around with anything until you're sure you got all of the data off the device though!
Click to expand...
Click to collapse
That's a great idea about renaming the directory. When I'm home from work I will try to figure out how to copy internal user data to my PC and then I'll look into that directory. Do you know how to enable file transfer via adb or thru the Settings app (launched via adb)?
I did utilize the system UI tuner to disable my alarm icon from showing in the status bar, so I'm hoping I can perhaps find the file associated with the plugin specifically and rename that. Hmm. Only this is systemless... Might not be possible. This is my first rooted device without full read/write capabilities. Not sure how I feel about systemless.
Otherwise, other than time, the only bummer to all this is that I think I'm going to lose the Magisk module YouTube Vanced, as it's not longer supported.
Anyway, thanks very much for your help so far.
Ditamae said:
That's a great idea about renaming the directory. When I'm home from work I will try to figure out how to copy internal user data to my PC and then I'll look into that directory. Do you know how to enable file transfer via adb or thru the Settings app (launched via adb)?
Click to expand...
Click to collapse
If your luck is as good as mine, you should be able to just plug in the device and enable file transfer (Settings > Connected Devices > USB > "Use USB For ... File Transfer."
Note that, as explained above, I had to remove my security PIN in settings before that worked, though.
_Ra1n_ said:
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
Click to expand...
Click to collapse
I was able to backup my data, and use Solid Explorer with root to search through system files. But, I don't see that directory. I see: data/data/com.android.systemui but no systemui.tuner. Any other idea where those systemui tuner files might be lurking? I'm an RN with a kindergartener home from school, and as much as I love tinkering with Android, now is not a good time.
_Ra1n_ said:
Interesting! Exact same order of events.
Since you have root, if you want to mess around with trying to fix it without resetting, does the following directory exist on your device: /data/data/com.android.systemui.tuner
Click to expand...
Click to collapse
Just wondering if you have any other troubleshooting ideas before I install a full factory image...
My device boots now, partially. It seems that after I disabled lockscreen security, my phone boots, but without all gesture navigation, status bar, notification overlay. Essentially all SystemUI elements appear missing. The devices behaves as it did immediately after I accidentally toggled the UI tuner "plugins" setting, before I rebooted. It's unusable as a daily, but I did get my data. As I said previously, I could not find the directory: /data/data/com.android.systemui.tuner. Seems odd. I wonder where those setting preferences are hiding. Any help/ideas would be much appreciated.
Ditamae said:
Just wondering if you have any other troubleshooting ideas before I install a full factory image...
My device boots now, partially. It seems that after I disabled lockscreen security, my phone boots, but without all gesture navigation, status bar, notification overlay. Essentially all SystemUI elements appear missing. The devices behaves as it did immediately after I accidentally toggled the UI tuner "plugins" setting, before I rebooted. It's unusable as a daily, but I did get my data. As I said previously, I could not find the directory: /data/data/com.android.systemui.tuner. Seems odd. I wonder where those setting preferences are hiding. Any help/ideas would be much appreciated.
Click to expand...
Click to collapse
Sorry for the slow reply. Unfortunately I'm mostly out of ideas.
I'd ask in the general Android Help subforum: https://forum.xda-developers.com/android/help
You'll likely get more eyes on the question (where does SystemUI Tuner store it's settings & how to reset them) and hopefully someone with better knowledge on Android settings/preferences can provide some incite.
Homeboy76 said:
Guide
Do #4 'keep data', then #9 to root.
Make sure you have the latest SDK platform-tools, there is a link in the guide.
Click to expand...
Click to collapse
Flashing the factory image with -w removed to keep the data won't help. The issue is that SystemUI Tuner saved some setting (related to enabling the mysterious "Enable Plugins" option) that prevents the phone from completely booting up. A factory flash retaining data will retain the setting that SystemUI Tuner screwed up.
_Ra1n_ said:
Flashing the factory image with -w removed to keep the data won't help. The issue is that SystemUI Tuner saved some setting (related to enabling the mysterious "Enable Plugins" option) that prevents the phone from completely booting up. A factory flash retaining data will retain the setting that SystemUI Tuner screwed up.
Click to expand...
Click to collapse
@Ditamae Rain is correct. I have edited my post.