I've installed a stable version of cyanogenmod 11, also i've downloaded some apps and cause i care about my privacy and don't want to a stranger or my girlfriend see that particular apps, so i've hidde'em! At this moment i don't remember the sequence of the lock screen, i've removed the gesture.key file but that only take affect on the inital lock screen! I'm here to request some help in orther to fix the problem!
Related
Dear All,
First of all, I'm a junior developer in android field, So expect some beginners questions .
I'm working on a Lg G2 D802 phone .. CM 11 KK ROM.
All I want to do is destroy all apps and services on that ROM and make only sinle APK app to run.
Don't need any apps, dialer, bluetooth, wife, welcome screen, launcher ... Etc..
When I tried to do this, I had no problems removing apps from system/app folder, but after I tried to remove some apps from system/priv-app which I don't need like contacts and dialer etc..
It crashes and made a lot of popup errors .
Also failed to remove the welcome screen and launcher, I really want them to not to appear at all .
Just need some help to remove the apps, services, welcome screen and launcher,, And launch only single APK directly after booting.
Another question please ,, Before showing the boot animation ,, I always see LG logo stays on screen after switching on the phone...
I really want to know how to remove this logo .. Just need the boot animation after switching on the phone.
Thanks a lot for your help in advance guys .
Moto E LTE stuck in "just a sec" screen of "SetupWizardTestActivity"
Moto E LTE stuck in "just a sec" screen of "SetupWizardTestActivity" :crying:
1) Any suggestion on how to cancel/escape this "first time init" application so that i can reach the settings and give the required permission to this app.
2) If above not possible then any other suggestion to get back phone in working condition without factory reset/wipe from recovery.
*Apps are still working in background , i am getting notification sound and pushbullet notification on desktop
*tried the cache cleaning from recovery. it took quite some time but after reboot also the stuck in same situation
*Completely stock phone. bootloader unlock and root not done. since bootloader unlock wipes the device i do not want to do it at the moment.
*I have installed moto usb drivers and SDK to execute adb but phone is not visible with 'adb devices' command.
* apps are excuting in background since i am getting pushbullet update of phone notifications on desktop browser but the first time setup app has captured the screen and does not alow any other activity from touchscreen.
* for some reason the Paytm app also runs at startup and runs on top of "SetupWizardTestActivity" app but only thing i can do is back soft button till it exits. cant open notification
Context and back story
I triggered the "home button not working, empty notification" of lollipop/marshmallow as detailed in the following post on my Moto E 2015 LTE surnia by trying to manage space by using the migrate data option in storage. it tried to perform migrate in opposite direction i.e. from sdcard to internal and ran out of space mid operation probably.
"http://forums.androidcentral.com/android-6-0-marshmallow/600742-nexus-5-marshmallow-home-button-not-working-many-more-problems.html"
This issue is also reported here along with adb fix by koush
https://plus.google.com/u/0/110558071969009568835/posts/BL8XtUDcDCZ
Nova launcher workaround if abd not available . 3rd last post at the bottom.
http://forums.androidcentral.com/moto-e-2015/673227-problems-marshmallow-moto-e2-any-help.html
After this the behavior was as specified in above issue posting. home button not working (i could reach home screen by using back key till all open application as closed.), empty notification drawer, not able to reach the quick shortcuts in notification area etc.
So I tried thought some space issue
A) so i installed a few apps and cleared data of chrome, play books etc. to free up 500mb.
still same home button issue
B) then i thought it is some notification permission issue and checked various options in notification option in setting.
still no change
C) then i thought some other permission issue. So in the apps option in setting i reset the apps permission to factory. (dont remember exact menu option but it was in the 3 dots option on top right in apps setting). it gave a warning that all permissions will be reset to factory for apps
after this all apps lost all permissions and everything was asking permission when app was started. e.g. data manager app wanted permission to access data, sms app wanted sms access and so on.
**This will be one main reason for my issue at the end.**
After that I searched the issue and found above link.
so i tried the guest user login and cancel from that and the notification drawer got recovered. it was showing app notifications for whatsapp, SMS etc.
but home soft button was still *not* working
Since i haven't done any bootloader unlock and root operation on this phone i was not confident of the adb command success since it mentioned in one post that it required 'su'
So i tried Nova launcher workaround to invoke 'SetupWizardTestActivity' and it did execute asking me for
Now the initial factory inti app is running and stuck in following loop
language->sim select-> wifi login-> \
/-----------------------------------|
->privacy option->|software update check->-\
|------------------------------------------|
|-> account added -> "just a sec" ---------^
it hangs and crashes at the saving "just a sec" screen and goes back to "Account added" screen
This is due to the permission issue i created in step "C" of permission reset explained above.
This issue is also reported here along with adb fix by koush
https://plus.google.com/u/0/110558071969009568835/posts/BL8XtUDcDCZ
Nova launcher workaround if abd not available . 3rd last post at the bottom.
http://forums.androidcentral.com/moto-e-2015/673227-problems-marshmallow-moto-e2-any-help.html
Please if someone can help with ideas and suggestions to kill the fitst time installation app. :fingers-crossed:
NOTE. im new to Moto E but have been playing around with my older phones samsung s2, lg g2 and changing roms and trying out various options like CM, AOKP res remix etc.
any ideas on how to unset the flag that causes this first time installation screen to run at bootup
so apparently the bootloader unlock requires us to have a "" toggle set from devleoper option.
but we dont have a phone booting into a state that allows this toggle to be selected then we cant unlock bootloader as well.
fastboot oem unlock XXXX
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.011s
as explained in http://www.droid-life.com/2014/11/0...nable-oem-unlock-option-in-developer-options/
and http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312
So if someone has an idea on how to cancel the flag i somehow enabled by executing 'SetupWizardTestActivity' from nova launcher wizard.
The wizard cant complete because it doesn't have permission and i cant give permission as it is not allowing me to enter into the phone setting.
Did you ever find a way aroudn this issue? I've just run into it too..
Hello guy`s
i`m searching since days for a solution for my Android car system.
It has Android 8.1.0 installed, i can access the filesystem via adb root, the system itself is not rooted.
I have two issues with the device.
since a factory reset, when booting the system it does start into the "normal" slide to unlock screen, before the reset it booted directly into the Car GUI.
I searched also for disabling this, but only found how to reset or delete the passwords, and disable it on old Android 2.3 4.0 or 5, but not on Android 8.
it would now be easy said to just disable it at the system security settings under Display lock, but here is the second issue, the option seems to have been disabled by the manufacturor.
the same is with some other Option menu`s that are missing at settings.
i`m not that firm with android os itself, so i can`t finde the right command or modification to change this.
can someone help me how to disable slide to unlock, and how to reactivate deactivated system settings ?
sincerely Chri
Hi all,
I have a Poco F1 with the latest LineageOS rom found elsewhere on XDA. I had to do a factory reset because of some weird problem, assuming that my backup to Google Drive could be restored during the setup wizard.
The backup turns out to be encrypted with my lock screen pattern, a policy introduced last year. Unfortunately, I was using a 6x6 unlock pattern, but the setup wizard only allows me to enter a 3x3 pattern. Unlike other pattern screens, there is no 3x3/4x4/5x5/6x6 selector on the bottom of the screen. In other words: I cannot unlock mt backup.
Things I tried:
- Skip the restore process in the setup wizard, go to the system settings first to configure the exact same 6x6 lock pattern, and then return to the restore process. This did not help.
- Running adb shell bmgr restore also failed:
Code:
$ adb shell bmgr restore TOKEN
Scheduling restore: POCO F1
restoreStarting: 82 packages
restoreFinished: -1000
done
(I know, it says "done", but nothing changed and this happened much faster than I would expect a restore process to be.)
What can try next? All help is appreciated.
i think we are out of luck
pretty much the same thing happened to me with 4x4 pattern yesterday.
in my opinion this is a big no-no for the pattern size feature in the lineageos and there should be warning about all of this in big bold letters when you are changing pattern size
if there is anyone with an idea how to fix it, please share but for now i think the only theoretical chance of ever retrieving the data is for google to add "forgot my pattern" functionality into the backup restore procedure.
also, i found out that the pattern i set up originally still unlocks the phone during boot when it restarts.
once the system runs i have now just plain 3x3 pattern but somehow the old one is stored somewhere even though i did full wipe of the phone in twrp
Agree.
zivel said:
in my opinion this is a big no-no for the pattern size feature in the lineageos and there should be warning about all of this in big bold letters when you are changing pattern size
Click to expand...
Click to collapse
Exactly, I completely agree. The grid size feature was probably added to LineageOS before backups started to be encrypted with the pattern, but still I am surprised that this feature is still present in the code base while it cripples the backup restore process. A big fat warning is the bare minimum I would expect.
There isn't much information about this problem on the web, so I gave up on the thought of restoring my backup and built up my phone from scratch. Needless to say, I am using a 3x3 pattern now... Fortunately contacts and calendar have their own storage so the most important data (for me) is still safe.
Issue
I created an issue in the LineageOS issue tracker: https://gitlab.com/LineageOS/issues/android/issues/937.
same :crying::crying::crying::crying: the situation here, there isn't even an option to postpone the restore, all things gone....
This makes me cry. No warning anywhere. All that stuff gone now. Thought I was being a good boy by making a backup. Nope, screwed anyway. So many hours lost.
Hi,
I have a Pocophone F1 that recently upgraded to MIUI 12 (Global stock ROM). The password and fingerprint functioned normally until removing the password. Now when I try to set a password (pattern, PIN or password) a fingerprint is requested, the sensor doesn't recognize my finger and gets stuck on this screen.
I have already cleared all data from the applications below and restarted the device:
- POCO Laucher
- FingerprintExtensionService
- Fingerprint test
I also tried to create a Second Space, but the password is requested and I can't move forward.
In the Fingerprint input test option, the finger is not recognized. The sensor works normally, it vibrates (except on the screen to set the fingerprint) and I can take pictures with the sensor. I don't believe it's hardware because the problem started at the moment when I removed the password and fingerprint.
Any ideas what I can do to resolve without restoring the device?
Bro, Don't worry about your hardware.
It's a software bug and many MIUI 12 users are facing it.
I faced issue in setting up fingerprint in MIUI 12 too.
So I downgraded to MIUI 9 and it works like a charm.
You have two ways, either wait for next update to fix the issue or downgrade to lower MIUI version.
To set password etc boot in twrp and select advance, then file manager, in file manager select data, in data select system and in system delete lock setting files (3 files or may be one only).
Reboot and set your password.