Hi,
Could someone kindly provide me with the current settings apk as i was a bit daft and forgot to back it up whilst trying to mess about with lock screens.
Cheers
Please delete thread - worked out how to do it
can you enlighten the rest where to find it?
Yes sure. I Extracted the update-kindle-juniper-35.4.6.1_user_461013820.bin file using 7-Zip and when it creates a folder you need to traverse to:
System > App and voila There are the main APK's so you can keep this as an apk backup area in case you mess up like i did
oh sorry i though this was about replacing the settings.apk witht he stock android one.
No it was putting the currently Amazon one back in - I tried a stock android one and had nothing but problems with it. Whether it is because there are 2 Amazon Settings apks
AmazonSettings.apk
AmazonSettingsPermissions.apk
Also the option to change lock screens does not show visually in the settings menu, but if you add a lock screen it will send you to the hidden settings option (Notification Access) to enable to the change which lock screen receives notifications.
Tried long and hard with this if you add a stock settings.apk lock screen option gets a bit corrupted and you cannot preview edit original one.
I really wanted to mess abit more with lock screen but looking at the apks for the Amazon rom:
LockScreen.apk
LockScreenPreviewer.apk
LockScreenSettings.apk
LockScreenSettingsPreviewer.apk
I didnt know if normal roms has 4 different ones??
Hey Everybody
I have troubles since i clicked a button in my status bar. I removed EVERYTHING from my home and lock screen (i cant even tell witch one i see). There are no Icons at all. only my desktop background is visible and working (animated bubbles). there is no button working except from power button (and its menu to restart). a friend of mine was able to get a screenshot with some button-combination (vol+ + home?)
first: i am not an expert with android, but have a lot of experience in working with Linux shells.
what i have done:
maybe it has something to do with it or not, i don’t know:
i enabled multi view / multi window or extended desktop (sorry i don’t know the name, and as there is nothing shown...)
i opened my status bar and there were some new icons (next to the small watch in the right corner), witch i haven’t seen so far and clicked it. than it opened a "new" screen with only my background.
as i thought it is maybe only a "dead" app i tried to restart my phone. but: there is only that screen working. no PIN question, or something.
i tried to reset dalvic and normal cache. -> no change.
i use RESURRECTION REMIX 5.7.3. on N7100
Recovery TWRP 3.0.2-0 is still working and
i hope somebody can help me to solve my problem without factory resetting. i wont reinstall everything.
thanks a lot
Are you able to restore a TWRP back up? You could try flashing the ROM again without wiping.
theoretically, yes, but i did not have on. so i cannot flash it.
i am searching for an commandline option to change the settings. but i have no clue where to search, and in what files the configuration lies...
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.
Hi All,
Anybody using Tasker on Redmi X2 - Recently migrated from MIUI and facing lot of iffuce in the is color OS 6..1- Want to check for similar mind people
bino_mat said:
Hi All,
Anybody using Tasker on Redmi X2 - Recently migrated from MIUI and facing lot of iffuce in the is color OS 6..1- Want to check for similar mind people
Click to expand...
Click to collapse
Tasker is running fine on my X2 EU version. No problems up to now
Note4Addict said:
Tasker is running fine on my X2 EU version. No problems up to now
Click to expand...
Click to collapse
That is is interesting !! - 2 problems I encountered are
1.Tasker toasts are working only with in Tasker context - I mean if open the tasker and a do a flash message ,it flashes the message- But when on a normal working (Tasker is in background) - no toast message appears.
2.Even if I enable all of the permission,when Tasker tries to switch on the WIfi with in Tasker context as window popes out asking Tasker want to switch on Wifi - Allow or Prohibit -
If Tasker is in background,this window can't appear and nothing happens.
Finally ,I went to Developer options,Disabled the permission monitoring(last option) s- that this started working
Can you please confirm on these 2 points?
Confirm that! I had exactly the same problem with wifi on/wifi off and had to disable permission monitoring to get it working. It was the same for the initial adb permission command you need to get Tasker up and running. Unfortunately, at the moment I haven't got the chance to look into it but from version 5.9.2 Tasker has the new adb wifi commands which give it almost root like power. Perhaps one of these would be able to overcome the permission monitoring problem so that we can keep it active. Try it if you can, I would be very interested to hear if you managed to get that working.
Note4Addict said:
Confirm that! I had exactly the same problem with wifi on/wifi off and had to disable permission monitoring to get it working. It was the same for the initial adb permission command you need to get Tasker up and running. Unfortunately, at the moment I haven't got the chance to look into it but from version 5.9.2 Tasker has the new adb wifi commands which give it almost root like power. Perhaps one of these would be able to overcome the permission monitoring problem so that we can keep it active. Try it if you can, I would be very interested to hear if you managed to get that working.
Click to expand...
Click to collapse
Sorry I didn't get some part of your message _"It was the same for the initial adb permission command you need to get Tasker up and running" - Can you pl elaborate?
" Try it if you can..." - it means the ADB wifi commands ?I couldn't locate any permission disabling commands with adb wifi.
One good news is that I tried out Tasker in Android 10- COlor OS 7 and I see that Toast functionality is working in that
bino_mat said:
Sorry I didn't get some part of your message _"It was the same for the initial adb permission command you need to get Tasker up and running" - Can you pl elaborate?
" Try it if you can..." - it means the ADB wifi commands ?I couldn't locate any permission disabling commands with adb wifi.
One good news is that I tried out Tasker in Android 10- COlor OS 7 and I see that Toast functionality is working in that
Click to expand...
Click to collapse
Good news that Tasker works well in Color OS 7 which will get around March it seems. Regarding the initial ADB permission, I meant the message you get when you first install Tasker on a non-rooted device. In that case you need to execute a specific permission command via ADB to get Tasker up and running correctly.
What I meant with "Try if you can..." is that If you have the opportunity you may want to check if perhaps one of the new ADB wifi commands would be capable of setting wifi on and off despite permission monitor being active instead of disabled as we're doing now. Hope that will work so we can keep permission monitor active.
Guess ,it is more of Color OS issue , with the battery saved enabled,Tasker is missing the Alarm - I did a simple experiment of logging of BAttery level to a file in every 10 minutes.
If I look at the file now ,either the logging is not continuous or stopped after sleeping for one or hour or so !!! -- But this is not the case with MIUI - It's sharp on time with battery saver or not.
More importantly one thing I noticed is that when battery saver is on ,you can't lock the application in memory - Flip side , with battery saver on ,if I invoke recents and clear the memory ,evrything will be wiped and even when battery saver is off,the applications which you want to be in memory in normal condition will not be there!!!
Bluetooth problems with Android 10:
With my Realme X2 and Realme Ui 1.0 (Android 10) i can not start Bluetooth because my smartphone always asks with an popup for an permission ("Tasker needs the following permission: set Bluetooth on/off"). My desktop links give me the error code "action bluetooth failed".
How can i disable this popup asking for an permission? Or can i made tasker to click on yes itself?