After unlocking bootloader and restoring TA link, I found album blurred screen! I'm using iovf's kernel to enable double tap to wake.
This could not happen at booting on, would be that for a while after boot
I have this on any dt2w kernel, temporary fix would be disabling HW overlays in developers settings, which needed to be done after each boot. You can use tasker or look for init.d script.
But I would recommend to revert to stock kernel, as if you already have this another glitch may appear, which can be fixed only with reboot.
Related
I recently tried to update to a new version of the kernel I use, but after installing and rebooting I found I my lock screen had changed from pattern to swipe to unlock. I tried changing it back to pattern and even after setting pattern, it would revert back to swipe after I hit confirm. I tried going back to previous kernel. I've gone all the way back to stock 25R using this this:http://forum.xda-developers.com/onep...s-zip-t2820008. That didn't work. Then I formatted all data and installed 38R following this:http://forum.xda-developers.com/show....php?t=2770535.
What do I do? I don't like my phone not being secured
Hi,
I'm using an unlocked Nexus 5, and flashed as soon as the factory image was released. I used CF-Autoroot to gain root access.
The problem that I'm having is that the lock screen does not work. This means that when I lock the phone (power button), it just fades to black, but when I hit the button again (either immediately, or after a wait), I go straight to where I was, the lock screen does not activate no matter what I do. I've tried letting it time out, still no luck.
When I restart the phone, it shows the lock screen, but sounds like something is trying to unlock the phone, and the phone then unlocks and doesn't lock again. I've tried disabling all Device Administrators, with no luck. I tried a factory reset and then a re-flash followed by another factory reset, and the problem still persists. I've also tried toggling Smart Lock on and off, still no change.
If I go to the security settings and re-select a Screen Lock mode, then the lock screen shows up again, but after I unlock, it goes away never to return.
This has been extremely frustrating, since Smart Lock was one of the features I was most looking forward to. Does anyone know what could be causing this?
The current Root apps that I use are:
1. SuperSU (obviously) 2.23 BETA
2. BusyBox Free
3. AutomateIt Pro
4. Greenify
5. Power Toggles
6. AdAway
7. Titanium Backup
Another note: After the factory-reset, wipe, flash, factory-reset that I did, I restored all non-system Apps and data with Titanium Backup. Just putting this here in case you guys know of any app that causes this problem.
Ekitrak said:
Hi,
I'm using an unlocked Nexus 5, and flashed as soon as the factory image was released. I used CF-Autoroot to gain root access.
The problem that I'm having is that the lock screen does not work. This means that when I lock the phone (power button), it just fades to black, but when I hit the button again (either immediately, or after a wait), I go straight to where I was, the lock screen does not activate no matter what I do. I've tried letting it time out, still no luck.
When I restart the phone, it shows the lock screen, but sounds like something is trying to unlock the phone, and the phone then unlocks and doesn't lock again. I've tried disabling all Device Administrators, with no luck. I tried a factory reset and then a re-flash followed by another factory reset, and the problem still persists. I've also tried toggling Smart Lock on and off, still no change.
If I go to the security settings and re-select a Screen Lock mode, then the lock screen shows up again, but after I unlock, it goes away never to return.
This has been extremely frustrating, since Smart Lock was one of the features I was most looking forward to. Does anyone know what could be causing this?
The current Root apps that I use are:
1. SuperSU (obviously) 2.23 BETA
2. BusyBox Free
3. AutomateIt Pro
4. Greenify
5. Power Toggles
6. AdAway
7. Titanium Backup
Another note: After the factory-reset, wipe, flash, factory-reset that I did, I restored all non-system Apps and data with Titanium Backup. Just putting this here in case you guys know of any app that causes this problem.
Click to expand...
Click to collapse
I'm facing the same issue with my NON-rooted Nexus 4.
Anybody having any ideas?
Arijit
arijitmaniac said:
I'm facing the same issue with my NON-rooted Nexus 4.
Anybody having any ideas?
Arijit
Click to expand...
Click to collapse
Mine fixed itself after I manually installed the latest Google Play Services apk. Maybe try that and see if it works for you...
Hi everyone. I have a problem and i hope i can get the solution from you guys.
My oneplus one screen won't turn on manually, either double tap or power button. sometimes i try it randomly and repeatedly with tapping the screen and power button and suddenly turn on. but when the screen turn off (manually or automatic turn off), it won't turn on again.
My phone can still receive call, notification, etc but when trying to turn it on, futile. I try to trigger it with charging it and it's work. but when it turn off, it won't turn on again. i can plug/unplug the usb to turn it on, but i won't do that because you know why.
This is happened when this morning i want to try to install colorOS (http://forum.xda-developers.com/oneplus-one/general/rom-4-4-2-coloros-2-0-36beta-t2955853) and calkulins cm11s rom (http://forum.xda-developers.com/oneplus-one/development/rom-calkulins-oneplus-one-v1-0-t2810365) in multirom using this guide (https://forums.oneplus.net/threads/...ere-are-my-samples.176376/page-3#post-8703604).
My rom at that time are already on calkulins cm11s. but the bad thing is i forgot that my kernel are franco kernel r34 while multirom need kernel with kexec hardboot.
this is my step by step how can i get this:
- nand backup the current rom (calkulins cm11s)
- wipe, flash colorOS
- install multirom manager, download multirom and the recovery without cm11 kernel. reboot recovery
- add rom using my last backup, reboot to colorOS
- install cm11 kernel from multirom manager, reboot.
- try booting to cm11s but won't boot. hard reset and try booting again. it work. play it quite a while. try to turn it on manually but failed. REALIZED that i'm still using franco kernel. reboot recovery. (the problem start from this step)
- wipe 2nd rom, add rom without using backup, same problem (cannot turn on manually).
- wipe 2nd rom again, wipe colorOS, restore backup without add another rom, same problem.
- uninstall multirom, install twrp, restore backup, same problem.
- install new rom without backup, for 15 minutes is working and then same problem.
- Now i'm charging my phone because it's out of battery.
Can someone help me?? and i'm sorry for the long post and maybe for my bad english.
Currently I try flashing colorOS and everything work normally. Can I assume that maybe some colorOS setting stuck on the phone and made the cm11s rom behave like that? and if it is, how can i remove it?
Same Issue
I've found a solution that worked for me with the same issue.
i've disabled 'prevent accidental wake up' ind dsiplay settings
g.tscharf said:
I've found a solution that worked for me with the same issue.
i've disabled 'prevent accidental wake up' ind dsiplay settings
Click to expand...
Click to collapse
worked for me too
flash color os 1.2 (Android 4.3) and flash CM11S
I'm having a odd issue. I just restarted my phone to fix some slow performance issue.s When I reboot I was presented with my lock screen on the "enter pin" screen that pops up after a reboot. But after that screen pops up, I am unable to enter in any lock screen inputs as my lock screen appears to be frozen. I can lock and unlock the phone and use lock screen gestures however, the phone unlocks to the frozen lock screen and there nothing I can do from there. I did not make any edits to any files before this issue popped up.
I can still access fastboot and twrp just fine but I'm unsure what to do as this is a brand new issue.
Any help is greatly appreciated.
Thanks,
Do you have any magisk modules?
@soka said:
Do you have any magisk modules?
Click to expand...
Click to collapse
I'm on XXX but I've diabled that with magisk manager through twrp
Possibly xXx removed something you required for the phone to operate normally, installing your current OOS version on both slots could help.
I tried editing the floating-feature.xml to enable clock animations, but after restarting and entering my SIM card's PIN code, There was only a black screen with my battery percentage and the time displayed on the top. After 30 seconds, it restarted and enters into recovery mode. I'm not sure how to resolve this issue. I managed to get the device into systemui safe mode, and tried editing the floating-feature.xml file again. But, even after fixing what I changed, the issue
is still there. I don't know how I got the device into systemui safe mode, and I don't want to reflash the ROM and lose all my data. I haven't backed up my images and files in a while.
nvm i fixed it by reflashing the same rom but using the home_csc insted of csc