So I have seen a few threads depicting this bug/error/whatever it is, that when starting Android it asks for a PIN, no keyboard shows up at all.
I recently changed my password, and I guess absentmindedly checked yes to asking for a password on boot. However, after the device's first reboot with the new password, I can't enter anything when it asks me to. On the bottom of the screen, there is an 'Emergency Dialer' button, but I cant even press that. Is there any way to fix this? I can decrypt the system through TWRP with the password just fine, so I know it's the right password, I just cant enter anything on the Android side of things. I saw some suggestions being flashing a keyboard (no idea how to do that), reflashing the ROM, even using an OTG cable (which I have, no keyboard though) but I don't want to mess up the device any more by doing any of these if it was somehow to mess with the password or encryption. Any suggestions, or idea as to why this happens? Any help is much appreciated.
Update: I tried to flash a Nandroid backup from before I started having this issue, and its still asking for a PIN.
Update 2: Wiped /system/, flashed ROM and STILL have the pin screen. TWRP still decrypts with the current password, not the one from the Nandroid backup.
I'm currently using Gboard, and this happens very rarely. In my case, it always resolves if I turn off the screen and turn it back on.
If nothing else is working, you could try dirty-flashing your current ROM to restore its stock keyboard.
Dirty-flashing your current ROM will not cause you to lose any data. It will only re-install any stock system apps that you may have deleted.
Anova's Origin said:
I'm currently using Gboard, and this happens very rarely. In my case, it always resolves if I turn off the screen and turn it back on.
If nothing else is working, you could try dirty-flashing your current ROM to restore its stock keyboard.
Dirty-flashing your current ROM will not cause you to lose any data. It will only re-install any stock system apps that you may have deleted.
Click to expand...
Click to collapse
Gave that a shot, reflashed my ROM both dirty and clean, restore from a very old nandroid backup, nothing has worked..
Did a system wipe and I'm still having the issue.
If you've already wiped your phone, then this probably won't work, but give it a shot anyways:
Use a physical keyboard connected to OTG to unlock your phone, then wipe the app data in all of your keyboard apps.
Edit: Nevermind, missed the fact that you don't have a physical keyboard.
Anova's Origin said:
If you've already wiped your phone, then this probably won't work, but give it a shot anyways:
Use a physical keyboard connected to OTG to unlock your phone, then wipe the app data in all of your keyboard apps.
Click to expand...
Click to collapse
If a physical keyboard is the last option, I'll have to wait until tomorrow to get one I guess (I only have a laptop).
I know there's a way to use adb to input keyboard commands, but although I know I had debugging on it doesnt work on whatever this screen is called.
Thanks for the help though!
Anova's Origin said:
If you've already wiped your phone, then this probably won't work, but give it a shot anyways:
Use a physical keyboard connected to OTG to unlock your phone, then wipe the app data in all of your keyboard apps.
Edit: Nevermind, missed the fact that you don't have a physical keyboard.
Click to expand...
Click to collapse
Would deleting the Swiftkey folder from /system/app or /data/app mess up anything? I'm pretty sure that Swiftkey is the culprit here.
No, uninstalling Swiftkey shouldn't mess up anything; just make sure you have another keyboard app installed.
Swiftkey is just bloatware if you don't plan on using it.
I've had Swiftkey uninstalled using a root explorer since I started using the phone and it hasn't been a problem.
Anova's Origin said:
No, uninstalling Swiftkey shouldn't mess up anything; just make sure you have another keyboard app installed.
Swiftkey is just bloatware if you don't plan on using it.
I've had Swiftkey uninstalled using a root explorer since I started using the phone and it hasn't been a problem.
Click to expand...
Click to collapse
Uninstalled it through file manager, and still no keyboard came up.
This is the most stubborn issue I have ever encountered, quite literally done everything.. except using a physical keyboard but even then, this issue shouldn't have persisted if I've wiped this many times..
You could try flashing a new keyboard through recovery.
I found this generic keyboard app that was packed in a flashable-zip.
Btw, have you already wiped all your user data? If so, you might as well format your /data and /system partitions and start from scratch. This should remove any encryption.
Anova's Origin said:
You could try flashing a new keyboard through recovery.
I found this generic keyboard app that was packed in a flashable-zip.
Btw, have you already wiped all your user data? If so, you might as well format your /data and /system partitions and start from scratch. This should remove any encryption.
Click to expand...
Click to collapse
Flashed a brand new rom instead, got keyboard up but it's telling me that my pin is incorrect. Still stuck
Wrong password at boot is a far more common problem. Fix
For me, turning off display and turning it back on popped up a keyboard, when it was an issue. Somehow fixed at one point.
Luckily i recently acquired the oneplus 3t and in one of my actions in preparing the device for daily use i had the same issue after I install a [MOD] zip, the only quick fix that work 4 me was boot in twrp recovery and wipe factory reset system dalvik / art cache, install oneplus 3t firmware
http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.0.3/
just keep good 1 or 2 backups b4 u go crazy (or look for revert file) :fingers-crossed:
did you guys figure this out
Related
yesterday, I pluged in my charger and started browsing.
at one moment phone freezed, purple led flashed and phone rebooted
after that a lot of apps I had installed are missing. among them are gmail, google search widget, play store, titanium backup, some office from market (can't remember which) ...
and one widget I use can't be loaded on startup but if I remove it and add again it works.
I tried all I can think off except factory reset.
I tried deleting cache, dalvik cache, switched app2sd off (which were on, although I remember leaving it off), fixed permissions from recovery ...
I even reinstalled kernel and ROM and gapps, but no change at all which is really strange.
I use MiniCM7-2.2.0 ROM and 2.6.29.6-nAa-11 kernel
SD card is working, I can browse files and swap is working.
It also seems that rebooting doesn't work well. Sometimes, I choose reboot but it doesn't boot up until I pull out battery and press power button.
I'm not sure if this is connected because I didn't reboot much phone with this kernel and ROM
Any ideas before I wipe data?
Overclocked ?
Sent from my E15i using XDA
Apps2sd that's why ur apps r gone. Full wipe and reflash rom. Reboot issue can be fixed with latest flashtool reflash kernel with that. Worked for me no reboot problems no more
Hit thanx if I helped
Sent from my E15i using XDA
thank you for fast replies
phone is not overclocked.
I also guess it has something to do with app2SD
but I do not use it.
when I installed ROM I wanted to use Link2SD but it couldn't work because of build in App2SD.
I tried that App2SD but I couldn't control which apps to move, I even didn't exactly understood how it works, so I gave up of it.
Everything worked until yesterday.
and I only browsed internet when this happened. what could go wrong?
Is there a way to fix this before I wipe the whole thing?
I would like to make some backups and for that I need missing apps.
thank you
Oh,
and the strangest thing to me is that even after I reflash gapps, I don't have any google apps (at least which I use) except google talk
Try this:
Root again your phone with SuperOneClick.
Go to Settings >CM Settings >Performance >a2sd, and deactivate it. Then, activate it again.
Reboot.
Hopefully... it will fix your problem (worked for me ).
any particular version of superoneclick I should use? I tried one I have (which I used to root my phone a long time ago) and it fails to root it.
but why do you think I should root again? This is custom room and it is already rooted.
I tried turning on and off app2sd but there's no change, except some files are in one case in sd-ext directory and in other arent. but that are not missing apps :-(
Use the newest version, it will work. If not... use any method to root your phone again and follow the above guide (YES, I know that your ROM is rooted, just do it).
Why you should root again? Well, I already had that problem and all root apps were having problems (I dunno if you are having problems too, try it), so I rooted again my phone and all the problems were solved.
I repeated this with superoneclick 2.3.3 but no difference.
I had to full wipe the phone.
thanks all for suggestions.
EDIT: just to be clear, it did root this time, but no difference about this apps.
My school is implementing new security measures, and they're requiring that all university-owned devices are encrypted (they're using an app called AirWatch). My phone isn't required to be encrypted, but it seemed like a good idea . . . After encrypting, my phone is so slow that it's almost unusable (~30 seconds to open an email, for instance). I uninstalled the app, but I can't figure out how to decrypt.
My phone is rooted and I have Titanium Backup, so I am completely fine with wiping everything from my phone and reinstalling it all. I attempted to do a wipe data/factory reset from ClockworkMod Recovery v6.0.3.3, but it failed ("Error mounting /data!" and "Error mounting /sdcard/.android_secure!"). I reinstalled the CWM and tried to flash the recovery again but my phone can't seem to find the .zip file - maybe because it's encrypted?
Again, I am okay with losing all data on my phone, I just need to get rid of this encryption!!
I have S-OFF, CWM 6.0.3.3.
Thanks for any advice you can give me!
mayo44 said:
My school is implementing new security measures, and they're requiring that all university-owned devices are encrypted (they're using an app called AirWatch). My phone isn't required to be encrypted, but it seemed like a good idea . . . After encrypting, my phone is so slow that it's almost unusable (~30 seconds to open an email, for instance). I uninstalled the app, but I can't figure out how to decrypt.
My phone is rooted and I have Titanium Backup, so I am completely fine with wiping everything from my phone and reinstalling it all. I attempted to do a wipe data/factory reset from ClockworkMod Recovery v6.0.3.3, but it failed ("Error mounting /data!" and "Error mounting /sdcard/.android_secure!"). I reinstalled the CWM and tried to flash the recovery again but my phone can't seem to find the .zip file - maybe because it's encrypted?
Again, I am okay with losing all data on my phone, I just need to get rid of this encryption!!
I have S-OFF, CWM 6.0.3.3.
Thanks for any advice you can give me!
Click to expand...
Click to collapse
It sounds like running the RUU may fix your issue
**edit** http://forum.xda-developers.com/showthread.php?t=2576995 Just download and run from your PC. it WILL wipe everything.
Thanks. I think I did this once before, but do you know if there's a way to do it on a Mac?
I tried it on an old PC and got the error message "Program too big to fit in memory" when I tried to relock the bootloader. Is my computer too late, or am I doing something wrong?
mayo44 said:
Thanks. I think I did this once before, but do you know if there's a way to do it on a Mac?
I tried it on an old PC and got the error message "Program too big to fit in memory" when I tried to relock the bootloader. Is my computer too late, or am I doing something wrong?
Click to expand...
Click to collapse
I am not familiar working in MAC, sorry. In theory you could dual boot windows on your Mac though. On a windows PC you need to install HTC sync first, none of this "PDA net" driver bull **** the tool kits try and tell you works. Then you need the android SDK so you can properly flash the stock recovery and relock your bootloader. Then just run the RUU.
As far as your "program too big" error this makes me wonder the hardware specs on your PC.
mayo44 said:
My school is implementing new security measures, and they're requiring that all university-owned devices are encrypted (they're using an app called AirWatch). My phone isn't required to be encrypted, but it seemed like a good idea . . . After encrypting, my phone is so slow that it's almost unusable (~30 seconds to open an email, for instance). I uninstalled the app, but I can't figure out how to decrypt.
My phone is rooted and I have Titanium Backup, so I am completely fine with wiping everything from my phone and reinstalling it all. I attempted to do a wipe data/factory reset from ClockworkMod Recovery v6.0.3.3, but it failed ("Error mounting /data!" and "Error mounting /sdcard/.android_secure!"). I reinstalled the CWM and tried to flash the recovery again but my phone can't seem to find the .zip file - maybe because it's encrypted?
Again, I am okay with losing all data on my phone, I just need to get rid of this encryption!!
I have S-OFF, CWM 6.0.3.3.
Thanks for any advice you can give me!
Click to expand...
Click to collapse
Did you encrypt using the stock encryption in the settings of the phone or by using an app?
davidwritesmusic said:
Did you encrypt using the stock encryption in the settings of the phone or by using an app?
Click to expand...
Click to collapse
I used an app called AirWatch that walked me through some process, but I'm not sure exactly how it was encrypted.
Have you tried to format the data partition instead of doing a wipe?
Sent from my HTCONE using Tapatalk
mayo44 said:
I used an app called AirWatch that walked me through some process, but I'm not sure exactly how it was encrypted.
Click to expand...
Click to collapse
It appears that the encryption can be removed via AirWatch desktop application.
As for how? I have no idea friend.
If it is yours, you could break it, and have it replaced.
From what I was reading, you'll have more control and should be able to login online and decrypt
davidwritesmusic said:
From what I was reading, you'll have more control and should be able to login online and decrypt
Click to expand...
Click to collapse
I contacted someone from my university and they said to use AirWatch's desktop management page. I tried to factory reset from there and nothing happened. Well, I think my phone is moving faster but it's still encrypted (and I still can't actually factory reset it). Very perplexing!
mayo44 said:
I contacted someone from my university and they said to use AirWatch's desktop management page. I tried to factory reset from there and nothing happened. Well, I think my phone is moving faster but it's still encrypted (and I still can't actually factory reset it). Very perplexing!
Click to expand...
Click to collapse
What happened when you tried using the desktop page?
davidwritesmusic said:
What happened when you tried using the desktop page?
Click to expand...
Click to collapse
It said the factory reset message had been sent to my phone, and about 15 minutes later my phone restarted - still encrypted. Pretty anticlimactic. Now it no longer appears on the management page.
Yet the phone still shows as encrypted?
There are applications on windows (and MacOS) that will straight up wipe everything on any device. I know CCleaner will. Matter of finding the right program. It also depends on the encryption. But one question, if the app encrypted it, why can't it decrypt it? They didn't give you a key?
Sent from my HTCONE using xda app-developers app
Hi All,
Running stock but rooted (with Xposed modules) 4.4.4 on Verizon Moto X with an unlocked bootloader. (Flashed this stock ROM: http://forum.xda-developers.com/showthread.php?t=2829123 )
Any time I try to do any activity with voice I get the error, "Can't reach google at the moment."
I get this error if I click the mic in google now and by clicking the voice text mic on the keyboard. Also, Touchless Controls doesn't respond.
After searching around forums I've tried some suggestions that worked with similar problems on other phones, but to no avail. I've tried:
- clearing data and cache of google search app and force stopping (lost my google now launcher set up in the process)
- removing my google account from the phone, rebooting to recovery, clearing cache and dalvik, rebooting and adding my account back
Thanks for any suggestions.
hi, had the same issue with one of the modules in xposed, ended up wipping the device and started fresh, installed xposed and gravity box, no other modules, all is good now.
ericizzy1 said:
hi, had the same issue with one of the modules in xposed, ended up wipping the device and started fresh, installed xposed and gravity box, no other modules, all is good now.
Click to expand...
Click to collapse
Hmm, interesting...
I'm thinking it's not a specific Xposed module... I just tried uninstalling xposed framework altogether and then wiping cache and dalvik for good measure. No luck.
But out of curiousity, these are the modules I have installed: GravityBox, Exchange Bypass For Xposed, SingalIconsAOSP, Unicon. Besides GravityBox, did you have any of these installed when you had the issue?
I hope this doesn't come down to just wiping, which it most likely will.
My droid maxx has had the same problem since the update to 4,4,4 I have tried everything including a fdr ( through twrp ). Nothing has worked ! Moto has offered me a new phone but I don't want a new one as mine is unlocked and rooted ( otherwise stock ). I think I'm going to unroot it, put back in the stock recovery and try a fdr through that...POS !!!
This may not help at all....but maybe worth a shot. If you try and it doesn't help, post back here and let everyone know so nobody else tries it.
You might have some luck by erasing baseband cache with fastboot:
fastboot erase modemst1
fastboot erase modemst2
You might have to re-activate afterwards. It is the only suggestion that might be relevant that you haven't tried already...
Good Luck....that would be a frustrating issue... :good:
Unfortunately I gave up and just wiped and did another clean flash and its working again. It was very frustrating not having touch less controls or voice to text...
Thanks for the help though anyway.
leffer said:
Unfortunately I gave up and just wiped and did another clean flash and its working again. It was very frustrating not having touch less controls or voice to text...
Thanks for the help though anyway.
Click to expand...
Click to collapse
I agree touch less control wasn't something I cared about when I got the phone. But after getting used to it its hard to go without.
When you say you wiped and flashed. Can you elaborate. I tried fxzing ( saving data ), 2 FDR's everything .. Did you unroot then use HOM ? I will try anything at this point . Thanks in advance
tombaldwin6 said:
I agree touch less control wasn't something I cared about when I got the phone. But after getting used to it its hard to go without.
When you say you wiped and flashed. Can you elaborate. I tried fxzing ( saving data ), 2 FDR's everything .. Did you unroot then use HOM ? I will try anything at this point . Thanks in advance
Click to expand...
Click to collapse
My bootloader is unlocked so I was able to simply factory reset and reflash the stock 4.4.4 ROM from the thread I linked to in the OP...
leffer said:
My bootloader is unlocked so I was able to simply factory reset and reflash the stock 4.4.4 ROM from the thread I linked to in the OP...
Click to expand...
Click to collapse
I will try both methods and post back. Thanks for you help !
So I took both suggestions tried them 1st. I tried erasing the the baseband cache's via fastboot. No luck. 2nd I reflashed the current 4.4.4 stock rom via HOM, Full FXZ ( no data saved). !st off what a pain in the ass it is to reset up these phones from scratch. I setup my Google account but I didn't let Google reinstall all my previous apps and there data. I then went into settings and arranged things how I like them. Cleared off my home screens, put a few of the apps where I wanted them. I then went into the play store and allowed all apps ( preloaded ) to update. I then went back into settings and went to touchless control. To my surprise it worked ! I then went about loading all my apps.The usual 1's everyone has ie: Elixir2, FX filemanager,Poweramp, MX Player,Chromecast Panasonic tv remote 2, Google Wallet, UE Miniboom and Few other nondescript. Then I checked touchless control again and It was still working. Then I decided to install twrp and its recovery via fastboot ( 2.6.31 ) let it root the phone for me. Here's where it gets dicey.. It was late and I had had it with this friggin phone. I went and loaded all my apps that required root,Superuser pro, Dsploit, Busybox pro,Android terminal emulator, Wakelock(full) all the usual's. Then I went through and disabled all of the bloat. Rebooted and switched the phone to ART The following morning I went to show a friend how I had fixed my phone and It no longer worked ?
So I FXZ'd again not saving any data. Reinstalled twrp , rooted . Then 1 by 1 I reloaded every single app back into the phone and checked google now between every single install. Also this time I didn't let any of the bloatware update. I planned on disabling it anyways so why bother. I didn't install any apps that require root except twrp, busybox, Dsploit and #mirrorenabler . Also it's currently back on Dalvic. So as my phone sits now touchless control and all of its functions are working again. It's obviously a rouge app or ART Runtime that did this and I will narrow it down in the next few days and report back.
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk
It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
minnuss said:
It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
Click to expand...
Click to collapse
You may want to clean the dalvik-cache first. (Install TWRP and clean it from there) the system is storing tons of thing in there, and *for my case* wiping it was like a deliverance ?
minnuss said:
It started to happen to my phone after I flashed only system.img to my rooted phone, tried to get the phone back to stock like some sort of a shortcut, to try to get OTA update.
I did not recognize it right away, but it started to happen from time to time and in all random occasions.
The phone will literally freeze for about 5-10sec and then everything will go back to normal.
The standard android message will appear that app is not responding do I want to kill it or wait.
I flashed the whole phone with stock images, temporarily rooted the phone again to enable camera2, uninstalled root, and it still happens from time to time.
Any suggestions, what can I do, what to check, where to look ?
I had kernel "Kernel Adiutor (ROOT)" previously installed, but I changed nothing major, just cpu governor to ondemand, and messed a little bit with entropy. This was installed on the phone before flashing.
Click to expand...
Click to collapse
Is the phone writing big files to the disk like an automatic Backup? That's when my phone becomes unresponsive..
dodjob said:
You may want to clean the dalvik-cache first. (Install TWRP and clean it from there) the system is storing tons of thing in there, and *for my case* wiping it was like a deliverance
Click to expand...
Click to collapse
Hmm, i will try this when I get home from work, thanx.
Benjamin_L said:
Is the phone writing big files to the disk like an automatic Backup? That's when my phone becomes unresponsive..
Click to expand...
Click to collapse
No custom installed auto backup aps, only default Android syncs.
I think that it has to do something with the kernel, or something deeper then stock images, maybe dodjob is right, I will try with dalvik erase, and if I remember correctly twrp has another option to clean something else, will check it today...
Is there a way to flash default stock kernel again ?
minnuss said:
Hmm, i will try this when I get home from work, thanx.
No custom installed auto backup aps, only default Android syncs.
I think that it has to do something with the kernel, or something deeper then stock images, maybe dodjob is right, I will try with dalvik erase, and if I remember correctly twrp has another option to clean something else, will check it today...
Is there a way to flash default stock kernel again ?
Click to expand...
Click to collapse
Let us know!
dodjob said:
Let us know!
Click to expand...
Click to collapse
Nope, it did not work, freeze remains.
Now I need to check what Benjamin said, about internal storage, format system, and do all over again, but now without restoring backup, starting with fresh droid install.
minnuss said:
Nope, it did not work, freeze remains.
Now I need to check what Benjamin said, about internal storage, format system, and do all over again, but now without restoring backup, starting with fresh droid install.
Click to expand...
Click to collapse
That sucks big time ? the only time I got a freeze was as I wanted to empty chrome beta cache. After the reboot, all went back as it should be...
I did it, finally, flashed all images again stock, and then don't restored backup of the phone offered by google, but do the clean new phone installation.
It works now, everything is setup and works as it should be, except camera2api, I did not enable that one yet.
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
This has started to happen to me since yesterday. I've had the phone to a couple of weeks and it's completely stock and un rooted. I rebooted the phone last night cause I thought it was some ram issue but it remains today. I'll give it a few days and hope it fixes itself.
minnuss said:
I did it, finally, flashed all images again stock, and then don't restored backup of the phone offered by google, but do the clean new phone installation.
It works now, everything is setup and works as it should be, except camera2api, I did not enable that one yet.
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
Click to expand...
Click to collapse
Adb root shell. Can't think of a way this could damage anything if you just set the one property
hacktek said:
This has started to happen to me since yesterday. I've had the phone to a couple of weeks and it's completely stock and un rooted. I rebooted the phone last night cause I thought it was some ram issue but it remains today. I'll give it a few days and hope it fixes itself.
Click to expand...
Click to collapse
Did you have device rooted for a while, or it was always stock ?
Benjamin_L said:
Adb root shell. Can't think of a way this could damage anything if you just set the one property
Click to expand...
Click to collapse
Thanx, I needed that confirmation, then my problem was probably caused by some application that wanted to take root actions, without root enabled, and causing havoc to the system, because I was restoring backup last two times, backup from rooted phone.
I had rooted phone, then flashed only system.img, then the problem started, I don't know...
I will use the phone tomorrow for work without camera2, to make sure that I don't have any more problems.
minnuss said:
Did you have device rooted for a while, or it was always stock ?
Thanx, I needed that confirmation, then my problem was probably caused by some application that wanted to take root actions, without root enabled, and causing havoc to the system, because I was restoring backup last two times, backup from rooted phone.
I had rooted phone, then flashed only system.img, then the problem started, I don't know...
I will use the phone tomorrow for work without camera2, to make sure that I don't have any more problems.
Click to expand...
Click to collapse
It's always been stock.
I had never rooted this phone and I am on September security patch, from September 6th, but for 2 days, 1-2 times a day I get some freeeze for 1-3 minutes. Today I tried to clear manually the cache from Facebook, and it took me 1 minute after I click the button "Clear cache". And then I got everything freezing. After a black screen for 10 seconds I got an error as you can see in the screenshot attached. I will repeat, never touched the phone's system. Does anybody meet this problem???
kaiwanted said:
I had never rooted this phone and I am on September security patch, from September 6th, but for 2 days, 1-2 times a day I get some freeeze for 1-3 minutes. Today I tried to clear manually the cache from Facebook, and it took me 1 minute after I click the button "Clear cache". And then I got everything freezing. After a black screen for 10 seconds I got an error as you can see in the screenshot attached. I will repeat, never touched the phone's system. Does anybody meet this problem???
Click to expand...
Click to collapse
Yes this happens when lots of I/o is done on the internal disk. I hope this is just a missing optimization and not a hardware issue. But let's bug xiaomi with it. I assume you also have the 64GB version?
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
minnuss said:
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
Click to expand...
Click to collapse
I read a lot regarding how people brick their phone with TWRP and rooting, so for now I will not use this future. But to reset my phone I will think about. Anyway I need this phone to use all my applications, not only a couple of them, because of this freezing (.
Thanks for suggestions.
minnuss said:
@kaiwanted, I had that, but not 2 times per day, but almost constantly and the stops were about 10-15 sec, not for a whole minutes.
Clean flash, clean new start a phone procedure when the phone boots, no restores of backup.
And erased Dalvik cache in TWRP.
Or, if you don't want to do this, try with uninstalling all unnecessary apps that you have in the phone, try the day use with minimum, to see what happens.
Click to expand...
Click to collapse
So I uninstalled about 5-6 applications and freeze disappear. From which I remember, I uninstalled: Spendee, XDA Dev app, Zugo Wallpapers etc.
Still when I clear the cache manually from Applications in settings, it takes about a minute or more to clean 100-500mb. This is weird.
Anyway, thank you for the suggestion.
kaiwanted said:
So I uninstalled about 5-6 applications and freeze disappear. From which I remember, I uninstalled: Spendee, XDA Dev app, Zugo Wallpapers etc.
Still when I clear the cache manually from Applications in settings, it takes about a minute or more to clean 100-500mb. This is weird.
Anyway, thank you for the suggestion.
Click to expand...
Click to collapse
I did the same thing. Went through my application list, uninstalled everything I didn't need and the issue went away. I cleared like 5% of storage space with still over 50% left but it seems to have helped.
reflashed all stock, enabled camera 2 api using mi a2 toolkit (magisk method) and I have the same. Cleared everything and run flash_all.bat. enable cam 2 api again and still have the same issue. clean install of apps doesn't fix it. Any idea on how to fix the sudden freeze?
Thanks
---------- Post added at 07:52 PM ---------- Previous post was at 07:28 PM ----------
if I completely root the device, I will still have the random freeze?
also, if I factory reset the device in the settings, the camera 2 api will be gone? thanks
minnuss said:
Maybe, just maybe, the problem was with the way how camera2 api was enabled, I did it via adb shell.
How did you guys did it, if you have it enabled ?
Click to expand...
Click to collapse
I did it via twrp and adb shell setprop persist...
No issues here at all.