I installed Next Lock Screen and desired to get rid of Zen UI's Lock Screen completely, so I rooted my phone and installed Titanium Backup and found its entry "com.asus.lockscreen". I have already removed a few other Asus pre-installed softwares, but I'm not sure if removing this thing will bricked my phone since it has a "com." in front of its name. What do you think, is it OK to remove it?
1st off, don't remove it, just disable it from Settings. Also, all Android apps really have com before it, because of the package name, "com.somebody.appname".
Related
Had perfectly running tablet until I installed the latest recommended update. Now none of the buttons function. I can't even power off device with power button it only restarts. Anyone else having this issue or have a fix other than factory reset?
What have you done?
Nothing so far, problems started occurring after applying latest update. Side power button does not show power options anymore, can only restart after holding button in. Bottom buttons don't work.
I have a kk note 8.0 that I have been messing with on KK issues. Use to backup and freeze the update or remove it. It really does not do any th8ng but disable tweaks and mods from rooting. Many have seen issues from it.
How do you remove update without doing factory reset or is that not possible?
If you have rooted, install ti backup if youhave not already, and search for security, and it should list one with more info in the name.. should have 1.1 or 2.2 near the end of the name.
the file name should be explanitory. depending on what you have installed, you may see more files with security shown in the list. you want to identify the file in red, as red is used fo r system files.
tap on the file and select remove in the upper right.
if ti backup is too complicated... you may find the app in app manager listed in all apps. you may be able to disable the app, as i recall that you are given adisclamer during the install, about how to disable its function.
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??
Greetings dellow xda dev's, I am currently running a Tmobile galaxy note 3, with the newest stock odexed FOL1 firmware, rooted, running twrp 2.8.5.0, I hav been installing apps and setting things up all day as a recent problem has forced me to factory reset my phone. Due to the way I use tasker to lock my phone (using secure settings to set a password) and restoring the old tasker profiles, my password appears to have been corrupted in some form or another as I have entered it a bunch of times and it won't unlock, claiming that the password is wrong. I have spent most of the evening looking at exploits and bypasses but none seem to work with my phone, there is no password.key file in the data/system folder, and deleting the gesture.key doesn't help. Using android device manager I can send a message to my phone and 'lock' it, but there is no unlock option anywhere on the screen; until I hit the home button and it simply sends me back to the normal lockscreen, and whatever new password I punched in with the manager doesn't work. I have tried several flashable zip files (lockscreen security bypass and pattern password disable), I have also tried everything mentioned in :http://forum.xda-developers.com/showthread.php?t=2620456 that article, as well as poking around in adb and in twrp's file manager, as well as some old lockscreen vulnerabilities (sadly copy and paste do not appear on the emergency dialer or the password field).
I am rather desperate to get my phone unlocked without a factory reset, as I just barely recovered from one recently, and need my phone for work tomorrow morning. I do have some tasker and autoremote profiles running that will tell my phone to setoff an alarm through tasker, and that will alert my phone to when my tablets battery life is low, but I don't know if either of those will help. I do not have any trusted bluetooth devices that can unlock the phone, nor do I ever seem to find a password reset/forgot your password option after typing in my password.
Any help or guidance would be greatly appreciated and tried come morning before work.
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
Hello,
I have a weird problem with my phone. Few days ago I've drained my battery and swapped it to the fresh one. But after phone booted up everything is broken.
My wallpaper changed to the one i don't know, it even doesn't look like stock one (Screenshot 1).
Notifications doesn't show up. Probably because upper drawer doesn't work now as well (i can slide it down only once, to show me date. But can't slide it down further to change sound profile, wi-fi etc. Screenshot 2).
Home button doesn't work, square button (the one for switching between applications) doesn't work either.
Half of the settings got reset to factory, some of them stayed unchanged but doesn't work anymore. For example, I've had my lock screen protected by pin. It still shows in the settings that I've set pin code, but there is no actual pin lock when I'm locking my phone (Screenshot 3).
Developer options menu says that they "are not available for this user" (Screenshot 4).
Even my QuickCircle case doesn't work anymore.
I have F400L one with Fulmics ROM 7.6 (6.0 Android).
I've tried to dirty flash it (i was on Fulmics 7.5 before). But after flashing new version of ROM everything still the same.
I've tried to wipe Dalvik + Cache, no luck either.
I don't want to do a full wipe, it will be a huge pain it the ass to reinstall and reconfigure all of my apps. Especially ones like Google Authenticator.
Dear community, do you have any suggestions what happened and how i may fix it?
UPDATE:
Found same problem: https://plus.google.com/u/0/+PaulOBrien/posts/8EGNvpY9jQa
Solution is to type this command (through adb or terminal):
am start -n com.google.android.setupwizard/.SetupWizardTestActivity
At this moment, this command resolved probably all of issues occured.