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.
Related
Hi all,
I've recently upgraded from a Samsung Galaxy S3 (i9300) to a Samsung Galaxy S5 (SM-G900F). Phone seemed to be working as desired so decided to go ahead, root, and install a custom ROM for enhanced functionality and customisation. Root process went smoothly, just running a simple CF-AutoRoot with Odin3 (voids KNOX, but no other problems), then installing PhilZ Advanced CWM Recovery.
From there I decided to install an unofficial build of CyanogenMod 11; found information on this forum. Flashing worked perfectly (and took rather little time!), but upon installation I noticed a strange problem. If I hard reboot (power off, power on) the device, with Wifi & Mobile Data off, the time and date are reset to incorrect values. Usually 01/01/xxxx and the time around 00:00. Same problem occurs even if when I turned off Network-allocated time and tried and set time manually.
The same problem occurred with other similar CyanogenMod based builds such as [AICP] and [AOSB]. I decided to restore back to the stock ROM and noticed that the clock and date were set correctly on reboot (and also on custom versions of 4.4.2 such as SpeedROMv7).
I checked with the terminal the value of the 'hwclock' (from BusyBox) and it reported an odd date somewhere in 1970, but different to the ones in found on CyanogenMod etc.
Does anyone have any idea what could cause this kind of problem and how to fix such an issue? If anyone wants any additional information about my device, please don't hesitate on commenting in this post. Would be grateful for any feedback. Thanks! :good:
PS: Also seem to be experiencing a problem with WiFi randomly disconnecting after a period of time. Not seen many threads with this said explicitly however. Problem with no voice in phone calls with headphones still persists but I've acknowledged that this is a known bug at the moment.
A.
Bump
*bump* // Problem still not resolved. Anyone know if it's device chain related?
Anyone?
AlfieJPalmer said:
*bump* // Problem still not resolved. Anyone know if it's device chain related?
Click to expand...
Click to collapse
Same Issue.
I have been encountering this very same problem for a while now, in fact, I am expriencing the same issue with my Galaxy S4 (i9505). So this must really be an issue of the CM code I guess.
Any ideas on how to solve this would be welcome since it is a really annoying issue
remove me
Hi, I have a OnePlus Two which reboots to the second bootanimation when ever I try to uninstall a app. Also when I go to security in settings the settings app crash's too.
I was on oxygen OS with the same issue so I decided to clean install recrunstruction remix ROM on my phone which I did, still with the same issue. Also I had this issue in both of the Roms where as I set a password it woint let me (when I set a pin on my phone it asked me to confirm the pin which I did and it woint let me press the confirm button) I believe that this issue might had happened maybe when I fixed my bricked phone first aid kit, and after that I started to get the problem. I have thread on that too that you can visit with this link "http://forum.xda-developers.com/oneplus-2/help/bricked-1-2-help-please-t3326037" So please help me and thanks.
Never Mind, I Solved The Problem By Flashing The Stock OTA
So I've been searching all the internet regarding my problem and found none to have my problem.
I was using popwiz rom and after a while my fingerprint sensor stopped working with the error "An error has occureed with the fingerprint sensor. If this message appears repeatedly, restart your device."
Because I needed my G900FQ, I ignored the issue for a while. Found S7 insanity which has a fingerprint bug and forgot about the problem.
Yesterday wanted to check out official MM for my S5, and had to reflash stock lollipop. Then I remembered my fingerprint problem so I tried to set it up. I kept getting that nasty error, tried deleting cache, tried deleting data with Titanium. Reflashed stock 2 times again, nothing worked. Until I was ready to give up and go to bed. Then it suddenly started working. Managed to set it up and activate fingerprint unlock.
Now is the bummer!
I CAN UNLOCK with fingerprint if waiting about 3 seconds after turning screen on.
I CANNOT ADD FINGER through settings, I get the nasty error message.
Tried to enter factory tests and under NormalScan button says Version 0.0.0.0 and in SensorInfo says Ready and stays that way.
I tried to enter factory tests very fast after unlocking with fingerprint and I got, only once and for a brief moment, the right Version and SensorInfo, and Normal Scan showed data and graph.
Now I will try to install official MM firmware with Odin.
Anyone has any ideas to what the cause may be ? And maybe a solution ?
Thanks in advance
L.E. I installed official MM firmware and now fingerprint sensor works when unlocking and adding fingers, but when I try to unlock my phone while it is connected to a power source I get the nasty error message again and prompts me for my backup password. Any advice would be deeply appreciated.
Flash a stock ROM and factory reset?
It seems you did not read the whole thread before suggesting me this...
I did that many times. Lollipop and MM official stock... Its like the sensor is not responding in some situations , but in other situations it does. And this seems to be pretty random..
*Detection* said:
Flash a stock ROM and factory reset?
Click to expand...
Click to collapse
laurent.siku said:
It seems you did not read the whole thread before suggesting me this...
I did that many times. Lollipop and MM official stock... Its like the sensor is not responding in some situations , but in other situations it does. And this seems to be pretty random..
Click to expand...
Click to collapse
It seems you don't even know what you typed, nowhere in your OP did you mention factory resetting and then flashing a stock ROM
Only that you flashed stock ROMs, flashing stock ROMs does nothing to reset anything and will leave behind bugs from the previous ROM if the issue is with an app / data etc
Before getting clever, read what you type
It's obvious that by flashing a stock rom over a custom one will leave bugs. Did full wipe (system, data, cache&dalvik, even phone internal sd) before flashing stock, every time. Thanks anyway..
*Detection* said:
It seems you don't even know what you typed, nowhere in your OP did you mention factory resetting and then flashing a stock ROM
Only that you flashed stock ROMs, flashing stock ROMs does nothing to reset anything and will leave behind bugs from the previous ROM if the issue is with an app / data etc
Before getting clever, read what you type
Click to expand...
Click to collapse
Well maybe next time add that fairly important info to your main post, instead of hoping everyone is psychic, and then throwing a hissy fit when they suggest something you have not stated you already tried.
Hello,
I have posted this on the cyanogenmod forum but everyone seems to be on holiday as I'm getting no replies. I'm hoping someone on here can help.
I recently had CM12.1 running on my S5 SM-G900F for about six months with no problems. I then switched over to CM13 and used that for about a month without any problems.
I decided to go back to CM12.1, I flashed the same CM12.1 Snapshot file that I had been using previously and it installed without error but when I rebooted the phone it would crash and reboot in a loop during start up. I wiped the phone and tried the install again about four or five times having the same problem until on the final attempt it managed to load the OS. Now that I have the OS running I cant connect to WIFI, the 'back' and 'recent apps' buttons on the phone don't respond (the home button does work), the camera app doesn't work (I get the error 'Can connect to Camera') and it keeps crashing and restarting on reboot. Everything else seems to work but the phone seems sluggish and there may be other errors that I haven't come across yet.
I thought that there may be a problem with the zip file I was flashing so I downloaded it again but it did the same thing. I've tried wiping and reinstalling several times but I get the exact same problems. The file I'm flashing is:
cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
If I go back to CM13 everything works fine so the problem is only with CM12.1.
I'm at a lost to explain why this keeps happening as I've had this running fine on my phone previously and wiping the phone and starting again doesn't do anything to solve the problem.
Any ideas please?
Come on people! Have a guess, I'm really stuck here!
I myself have not installed any custom roms on my s5 yet (bc of knox 0x0 lol) but try reverting back to the stock rom and then install cm12.1 again, maybe it could work.
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Can you tell what bothered you to go away from cm13 back to cm 12.1?
caned_monkey said:
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Click to expand...
Click to collapse
ezantera said:
Can you tell what bothered you to go away from cm13 back to cm 12.1?
Click to expand...
Click to collapse
CM13 sucks!!! snapchat and instagram keeps on crashing, now I'm using resurrection remix 5.7.3, that sucks too!!
have a nice day
Third-party rom has this error;
finally, i found the reason why the phone restarted itself
reboots when keys are pressed for a long time,
I'm experiencing this error especially in the fingerprint reader
for your information..
my device oneplus5..
always the most current firmware was installed.
i encountered this error.
Third-party rom error;
Codename Phoenix
Pixelexperience
Havoc-Os
hopefully, can be corrected
thanks all..
SqooK said:
have a nice day
Third-party rom has this error;
finally, i found the reason why the phone restarted itself
reboots when keys are pressed for a long time,
I'm experiencing this error especially in the fingerprint reader
for your information..
my device oneplus5..
always the most current firmware was installed.
i encountered this error.
Third-party rom error;
Codename Phoenix
Pixelexperience
Havoc-Os
hopefully, can be corrected
thanks all..
Click to expand...
Click to collapse
And you're sure that this issue is a rom fault? Do you have any logs or steps to reproduce? You are the only one with this issue?
At which roms does this not happen?
strongst said:
And you're sure that this issue is a rom fault? Do you have any logs or steps to reproduce? You are the only one with this issue?
At which roms does this not happen?
Click to expand...
Click to collapse
I'm sure the error is a rom error because I don't encounter this problem in oos rom
remember that there was a mistake in the past. The screen was locked and only the led light was on,,He wasn't making a move on the phone.
I get an error when I tap the keypad area repeatedly or when the phone is in a closed area (pocket mode)..
this error is more of a problem I have encountered in the last 2-3 months.
for example aex romda and unofficial pixelexperince mod did not have this error...
SqooK said:
I'm sure the error is a rom error because I don't encounter this problem in oos rom
remember that there was a mistake in the past. The screen was locked and only the led light was on,,He wasn't making a move on the phone.
I get an error when I tap the keypad area repeatedly or when the phone is in a closed area (pocket mode)..
this error is more of a problem I have encountered in the last 2-3 months.
for example aex romda and unofficial pixelexperince mod did not have this error...
Click to expand...
Click to collapse
As I wrote before: please take logs and steps to reproduce. Then post is within the specified rom thread, cause here no developer takes care of it and I can't remember to read a similar issue somewhere.
ok, thanks
Random Reboots
I had the problem of my One plus 5 rebooting over and over from first initial set up to updating the phone from stock to 9.0.4. I unlocked it and flashed crDroid hoping it would fix it, initially it didn't until I just thought of trying to disable the hardware keys in the crDroid settings and chose to use onscreen software keys and so far no forced reboots since toggling the hardware buttons off. So maybe it is an issue with the system getting confused between a screen tap and hardware key press if someone can confirm this helped their one plus 5 rebooting on its own even after updating to latest ROMs from official updates.
Hello
there is an error I've encountered in a long time
I encountered this error in other roms with havoc-os
restarting in the phone pocket
oneplus 5
I think the source of this error is caused by double-clicking on the lock screen
(I don't have a problem when I close the settings)
when I open the setting, I'm having this problem, so my idea is why.
Can you check the code order?