Related
The Problem:
Updated my ROM the other night and I tried to set Pattern as my Screen Lock security and it just stayed on "Slide" I tried every other lock screen choice and none of them would stick.
Troubleshooting:
1. I cleaned flashed the latest nightly I was using and the problem persisted
2. I wiped my phone completely and reinstall stock images and flashed Carbon ROM and the problem still persists.
3. Flashed another ROM and the problem still persists.
I don't know if anyone secures their phone but to me this is an URGENT matter, if anyone has any suggestions, Im open to fix this ASAP.
SOLVED!!
N4Solomon said:
The Problem:
Updated my ROM the other night and I tried to set Pattern as my Screen Lock security and it just stayed on "Slide" I tried every other lock screen choice and none of them would stick.
Troubleshooting:
1. I cleaned flashed the latest nightly I was using and the problem persisted
2. I wiped my phone completely and reinstall stock images and flashed Carbon ROM and the problem still persists.
3. Flashed another ROM and the problem still persists.
I don't know if anyone secures their phone but to me this is an URGENT matter, if anyone has any suggestions, Im open to fix this ASAP.
Click to expand...
Click to collapse
UPDATE: I figured it out, turns out that it was the "PROFILES" option set to home with an "Unsecure" lock screen
Hi, I never root my phone or flash a custom ROM.
The problems was started when I flashed a new ROM from sammobile of another country, my phone comes with 4.2 and I flashed a 4.3.
I flashed newer ROM from only Vodafone-Spain (only those really are my official supplier), and then I update ever with Samsung KIES, (no Knox counter)
So, with Andorid 4.3 I had more problems than now with 4.4, now the only problem is with WIFI
I can use normally, with screen ON, the problem is when sleep for a long time (more than 1 hour) when I touch a button I see the unlock screen, but does not seem to work the touch screen, and screen go off after a seconds, if I touch other button the screen don't go on. And then, after aprox 30s it reboot itself, and show a window telling that the Process System is not responding, do you want to close?, and two buttons, close or wait.
I tried to start my phone in Secure Mode and I have the same problem, so it is not an app, it is the ROM.
I do at least 2 Factory Reset, but the problem is still there.
I think it is a software problem and not a hardware problem, because the problem start when I update to Android 4.3
I tried the trick WIFI Power save Mode OFF (on dialer, *#0011# -> WIFI -> Power save mode OFF) and never reboot automatically, so the problem I think it is with this power save mode. But if I turn off, when WIFI is ON, the battery drain fast.
In the samsung shop they tell me that first will format my phone to see if the problem solve and try for a time, if not solve, then I have to send by mail... and I will not send it because I know the time it will take to repair it is about 1-2 months and I need the phone for my work.
So is there another solution or something to try?
Napalm Candy said:
So is there another solution or something to try?
Click to expand...
Click to collapse
Try reflashing the Firmware once again mate and Here you can follow the tutorial from here
Repulsa said:
Try reflashing the Firmware once again mate and Here you can follow the tutorial from here
Click to expand...
Click to collapse
Since the first ROM (4.2) I flashed 3 or 4 ROMs from SamMobile, so I am not very optimistic. But I don't lost nothing, I will try it
I flash again the ROM, and after 2 days testing, the problem is still there.
Any other thing to try before send to samsung?
Please, give me another idea to try. I really have a problem with WIFI
This is how Wifi (some times) drain my battery when are not connected to a network. But the problem is worst when is connected, because it freeze and reboot.
Hello! You could fix the problem? I took suffering the same problem as your months, and I have not been solved, I'm for kicking the **** mobile! As may give so many problems with the wifi?
regards
manguila said:
Hello! You could fix the problem? I took suffering the same problem as your months, and I have not been solved, I'm for kicking the **** mobile! As may give so many problems with the wifi?
regards
Click to expand...
Click to collapse
Yes I solve. So.. I don't solve it, it solve it self. One day I saw that I don't had wifi connection, then I saw that I don't any WIFI names stored, all was erased automatically, I don't know how.
But the result it, I don't have anymore a freeze or a reboot because wifi. ALL, absolute ALL run fine now. I had a lot of WIFI names stored, about 30-50, maybe this was the problem, a conflict with some of these names, but I'm not sure
No one update, reflash, factory reset, or start in safe mode was solve any problem, the problem solve it self... very strange.
If you try a factory reset, then don't restore all your mobile config. Try to install all apps manually, one by one. I ever restored my backuped config, and I think this was the problem.
Hope you can solve it
Napalm Candy said:
Yes I solve. So.. I don't solve it, it solve it self. One day I saw that I don't had wifi connection, then I saw that I don't any WIFI names stored, all was erased automatically, I don't know how.
But the result it, I don't have anymore a freeze or a reboot because wifi. ALL, absolute ALL run fine now. I had a lot of WIFI names stored, about 30-50, maybe this was the problem, a conflict with some of these names, but I'm not sure
No one update, reflash, factory reset, or start in safe mode was solve any problem, the problem solve it self... very strange.
If you try a factory reset, then don't restore all your mobile config. Try to install all apps manually, one by one. I ever restored my backuped config, and I think this was the problem.
Hope you can solve it
Click to expand...
Click to collapse
Thank you very much for answering so quickly.
Happens to me exactly what you do, but seems to have no solution.
I have tried more than 8 roms, stock or mods, and always fails.
At first I thought it would issue the modem or kernel, but after many tests, I do not ****ing know what is causing the problem.
I'm running out of solutions, anyway thanks for telling your case...
I'm glad that in the end one way or another, you have it fixed.
:good:
manguila said:
Thank you very much for answering so quickly.
Happens to me exactly what you do, but seems to have no solution.
I have tried more than 8 roms, stock or mods, and always fails.
At first I thought it would issue the modem or kernel, but after many tests, I do not ****ing know what is causing the problem.
I'm running out of solutions, anyway thanks for telling your case...
I'm glad that in the end one way or another, you have it fixed.
:good:
Click to expand...
Click to collapse
What happens when you fully wipe, flash a 4.4.2 rom, don't restore anything, not even your google account and don't install any apps.
Lennyz1988 said:
What happens when you fully wipe, flash a 4.4.2 rom, don't restore anything, not even your google account and don't install any apps.
Click to expand...
Click to collapse
Thanks for your interest! The truth is that it is very strange ...
If I remember correctly, already try what you mention me, but I kept going ... It's like at some point something had happened which change roms not seem to solve..
I'm considering installing a rom with 4 files and pit file, but do not know if this will help in something
Let's see if I can come up with the bug because it is becoming a pain in the ass
:good:
I would try what say Lenny1988. So the only change before solution and after solution, was a big crash on WIFi drivers/app/modem (don't sure) it self, and was deleted all my stored wifi access points that I had. It was a problem related to Wifi power save, if I disabled it then I had no reboots/freezes.
So, I would try a factory wipe and DON'T restore anything, and try for a couple days. If work, then you know a way to solve it.
Tell us if it works.
Hello there! I will update with the latest news!
I tried the recommended advice, but no luck...Not seem to affect him leave without restoring.
The only thing that seems to work and keep it running, is to disable wifi power saving system
you know....
Code:
1. Go to your phone dialer
2. Dial *#0011#
3. When you see the "ServiceMode" screen, press the left menu button
4. Select "WiFi"
5. See that "Wifi Power Save Mode" button that is "ON" - well turn it "OFF"
But this way drain your battery much faster,so it does not seem a good solution to the problem.
Curiously, the same phone, some people suffer this problem and others do not....
It may be hardware? or software?
If I find something, I'll note here.
Regards
I am using the T-Mobile Samsung Galaxy S5 (SM-G900T)
So, I got bored of CyanogenMod and started looking at what else was out there, and I ended up starting with Resurrection Remix. I was going through all of the settings and what ends up happening is using the "Quick Unlock" feature, caused my password to NEVER be right. I may be forgetful, but I literally had it set as "1234" and it wouldn't let me enter it in any way. I tired just putting it in so the feature would kick in, and nothing happened. Tried pressing the checkmark and it would tell me "You've entered your password incorrectly 1 time, please wait 20 seconds a try again" I ended up wiping a bunch, and left to Blisspop. Same exact issue. Could this be my phone? Is there a fix? I like this feature, but I can go without it. Thanks!
What does quick unlock do?
It seems that you're the only one having this issue. I've used Quick Unlock many times on CyanogenMod and ResurrectionRemix and never experienced the same problem you're having right now. If the problem persists, I suggest you shouldn't turn it on for now.
Vineen said:
It seems that you're the only one having this issue. I've used Quick Unlock many times on CyanogenMod and ResurrectionRemix and never experienced the same problem you're having right now. If the problem persists, I suggest you shouldn't turn it on for now.
Click to expand...
Click to collapse
I used CyanogenMod quick unlock and it worked, but RR and Blisspop gave me issues.
ResurrectionRemix is based from CyanogenMod so I don't get how come it would give you issues. I suggest you report directly to the device developer for ResurrectionRemix.
(Edit 1) Found a fix already! Read post 2!!!
Hello there,
I've been having a OnePlus Two since 4 months already, and had like 2 or 3 home button not working issues.
They used to fixed by themselves after a couple of days of not working, but not this last time.
I tried already the reinstalling system (after formatting system via TWRP), clean it several times, hard reset (hold power button for more than 20 seconds), complete drain battery and fully charge it again, force stop fingerprint service, take out the tempered glass screen protector, and none of those solutions worked.
I here attach (copy the link, can't upload a video directly to this post) a video in which you can see that whenever I power on the screen (still locked), the home button works for several times, but as soon as I unlock it (pattern lock) it stops working. This makes me think that the problem is software, not hardware, but as I said before, already tried reinstalling OOS 3.0, wiping system, cache, data, internal storage, etc.
I compressed the video so it wouldnt be too big, but quality is good enough, just rise the volume so you can listen to the "vibration" that the home button produce.
Any help would be appreciated.
Sincerely,
Daniel Castro
Fix for the issue!
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
I have the same problem
Tomorrow i'll try your method
I've posted a questione about this issue,
I think the One plus team should find a solution to this problem that afflict many users
Also, don't forget to rotate your phone 720 degrees, counter clock wise! ? hocus pocus....
DCastro555 said:
Forum people, I found a fix!
Ok, the solution for making the home button work again (with fingerprint sensor) is the following.
-Factory reset while in OOS 3.0
-Set up everything up and then reboot into fastboot mode
-Install OOS 2.1 via fastboot (you will need to search the forums for it)
-Set up everything up and try to set up fingerprint (it wont work)
-Copy OOS 3.0 (Beta) in the root of the phone
-Reboot into stock recovery and flash OOS 3.0 (beta)
-Factory reset it and set up everything again
-Voila!
Feel free to try this method and reply to this threat or P.M. me for any help.
Sincerely,
Daniel Castro
Click to expand...
Click to collapse
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
LOL9988 said:
Will it erase my internal storage during that fast boot step? So I can backup all my data.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It will erase everything, make a backup before starting the process.
faustin95 said:
these fixes are all coincidences... we need to request a definitive fix from One plus team if is a software issue.
Click to expand...
Click to collapse
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
pitrus- said:
Most probably hardware design fault, solution would be to redesign the phone and release a fixed design, will probably not happen unless oneplus3 is the solution.
And I second that it's just coincident behind these back and forth flashing of firmwares "solving" it, almost religious. But what are people to do when oneplus is not a company that takes responsibility for they're mistakes.
Click to expand...
Click to collapse
If it works, its worth a try . And yeah, but we are not in any OnePlus Forum, neither debating about if they are gonna do anything about their own issue, we are trying to fix what an irresponsable company wont.
can we make together an official request to one plus to give us an answer or explanation about this? a lot of users are facing this issue, it's not normal
This is my second opt I bought that this problem has happened
sorry for my english
I had also tried lot of things but home button is not responsive at all.. H2os,exodus,oxygen 2.1 ,3.0 same everywhere
---------- Post added at 04:01 AM ---------- Previous post was at 03:59 AM ----------
Error is: when i open fingerprint setting
Enrollment not working try differnt finger or try again ... Nd fingerprint autotest not starting also
i've turned to stock i've updated to oxygen 3.0 bet and the button worked again
i think rooting installing twrp and installing different roms may be the cause of this issue
faustin95 said:
i think rooting installing twrp and installing different roms may be the cause of this issue
Click to expand...
Click to collapse
Unfortunately that is not the case, it's a hardware design bug.
However you can f-k up your finger scanner by damage your persistant-partition if you flash up and down between different ROM/bootloader revisions. But it's easily fixed by flashing the image file for that partition again.
pitrus- said:
Unfortunately that is not the case, it's a hardware design bug.
Click to expand...
Click to collapse
it's a driver issue
faustin95 said:
it's a driver issue
Click to expand...
Click to collapse
50/50 moisture sensitivity and driver issue.
Home button has been working fine for a year, installed 3.0.1 today and suddenly home button only works in OOS 3.0.1. No longer works in CM 13, yet works fine in OOS 3.0.1. Definitely a driver issue.
Tried installing OOS 2.2.1, wiping, then installing Grarak's CM 13 and home button refuses to work. Wiped system, data, cache, installed OOS 3.0.1 and home button works again. Tried wiping again and installed CM 13, home button stopped working. Wiped and reinstalled OOS 3.0.1, home button works again.
Odd thing, my phone will only work with CM13 roms and OOS 2.2.0 or less for fps and home button. Nothing will fix or ever work.
For me, the home button stopped working for a short while on Graraks, then it just jumped back to life again and I haven't had any more home button blackouts after that. If it's a driver issue, it's an extremely intermittent one.
The fingerprint scanner has stopped working from time to time at lockscreen, but this is acceptable for an official hackjobb supported scanner until official sources are released ?
Need Help with this!
Hi everyone!
I have a OP 2 for more than one and a half years now and never had any issues with it(stayed stock...) until recently. I didnt update the phone to the latest version and was putting it off, and today in the afternoon when I tried to unlock my phone it said the 'Fingerprint hardware is not available' and after unlocking the phone with the pattern, it IMMEDIATELY LOCKS ITSELF BACK !!! after split second it just locks the screen while everything is working like connection, wifi, messages, notifications, etc. but due to this I cannot access anything on the phone, can't go to settings and switch to onscreen nav bar buttons, can't force stop/wipe cache the com.fingerprints.serviceext either, tried restarting it several times, downloaded the update but can't even install it because the phone just locks! I have no idea what would fix it and I am avoiding a full reset and wipe on the phone(also based on all i have read, dont think it would fix it anyways)
If anyone knows whats the problem or has dealt with it or knows someone who has, please help me out here on how to fix this and what to do. I did not root it or flash custom ROM's on it yet so literally dont know why it happened.
Thanks,
Max
I don't know what is wrong with my phone, I've searched the web for answers only to find nothing, I've asked in other threads and got no answers, I need help. So basically my issue is Magisk on my Mi A1 this issue happens with both 16.0 and 16.4, on the stock Mi A1 rom occasionally when I reboot my baseband and IMEI is unknown and when I reboot it fixes it's self temporarily I know this is not an issue with EFS partition as when I uninstall Magisk everything is fine and on custom ROMs I don't get this issue but a whole other different one. Also on the stock ROM Magisk causes bootloops sometimes which is fixed by rebooting.
When I use Magisk on a custom ROM I get a different issue, whenever I use Magisk to do anything on my device it causes an issue where sometimes when I power off my device it shows the boot animation before powering off.
I'm really sick and tired of these issues and any help would be really appreciated.
I have the same issue with the no imei/baseband in stockrom with magisk
created a thread like you asking for a solution, got not answers, not sure if is because not enough people mod this device or is something else
I for once as soon as I got it, unlocked bootloader and installed magisk and xposed, everything else is stock
issue still persist, you need to reboot again for imei/baseband to comeback
Sent from my Nexus 6 using Tapatalk
CrazyAndroidModder said:
I don't know what is wrong with my phone, I've searched the web for answers only to find nothing, I've asked in other threads and got no answers, I need help. So basically my issue is Magisk on my Mi A1 this issue happens with both 16.0 and 16.4, on the stock Mi A1 rom occasionally when I reboot my baseband and IMEI is unknown and when I reboot it fixes it's self temporarily I know this is not an issue with EFS partition as when I uninstall Magisk everything is fine and on custom ROMs I don't get this issue but a whole other different one. Also on the stock ROM Magisk causes bootloops sometimes which is fixed by rebooting.
When I use Magisk on a custom ROM I get a different issue, whenever I use Magisk to do anything on my device it causes an issue where sometimes when I power off my device it shows the boot animation before powering off.
I'm really sick and tired of these issues and any help would be really appreciated.
Click to expand...
Click to collapse
If you want people to help you, you need to give more details. A logcat maybe.
Rowdyy Ronnie said:
If you want people to help you, you need to give more details. A logcat maybe.
Click to expand...
Click to collapse
I'm currently running a custom rom and I've discovered that the issue I'm facing there has nothing to do with Magisk, its when I open an app like Titanium backup, even unrooted the app want root permissions causes the boot animation at power off, anyway I'll make a logcat when I get chance.