Related
First of all, sorry if this thread is out of place, but I'm not sure where else to turn.
My HD2 worked terrifically with FroyoStone 3.2, Hastarin 7.6 up until last Wednesday (5 days) ago. Then I started to experience, and have not been able to fix, serious TS lag issues.
Symptoms: I hit the unlock button, swipe to unlock, and the touchscreen will be responsive if I KEEP using it...if I pause for up to 3 seconds, the screen is no longer responsive. I have to relock the phone, unlock, and then swipe again to get it to work.
The touchscreen works perfectly fine in Windows Mobile 6.5. (Energy 2361X)
Attempts to fix: I've formatted the SD Card inbetween trying all of the following items-
1) Switch to MDJ ROM with MDJ kernel
2) Switch to Bluetopia ROM (0.5, 0.6 & 0.6.1) with Hastarin 8.0 OR 8.1
3) Switch back to FroyoStone 3.2 with kernel that comes with it
4) Update Radio ROM
5) Update to new Energy WinMo ROM -- after running Task 29 first.
Today, I purchased a new SD Card, loaded it with a clean install of Android, still have issues.
Also tried:
1) Turning off all LED notifications
2) Disabling Auto brightness in WinMo and Android
3) Disabled Screen Auto-Rotate
Honestly, I'm all out of ideas, and I hope someone in the community has a way to help out. I find it so odd that the touchscreen works great right after a "wake-up" as long as I keep it constantly stimulated...then fails to respond if I let it sit for more than three seconds. Is this a polling issue?
All ideas are appreciated. Thank you
UPDATE:
Followed another thread that suggests using the exact same WinMo ROM as the Builder -- matched my ROM with cmylxgo's WinMo ROM (author of Bluetopia) after another Task 29...no fix.
More Information
UPDATE 2:
Also tried 32K clusters and 64K clusters when formatting the card. Problem exists with either size.
There are G-Scripts to disable the G-Sensor and then re-enable it without rebooting.
If you want to jump to the extreme and want to remove all the sensors entirely.
Code:
su
rm -rf /system/lib/hw/*.sensors.so
Terminal
Thanks for your quick reply.
Unfortunately, I'm not the best with working with Linux/Terminal commands -- I tried typing in your code, and it returned that there was no such file/folder as -rf, and then I removed that section, and it said that it could not find the system/...
So obviously, there's something I'm missing, or an error in the syntax, that I cannot debug.
Any help is appreciated.
Are you having any data freezes or are you on an area with poor to no signal? I get really bad system lag when I loose signal while my phone is trying to download. Ppp will freeze and the phone will be unresponsive till reboot. Only way I avoid this is to turn off data if I got into a building I know I will loose connection in.
Sent from my HTC HD2 using XDA App
Updates
Thank you for your reply --
I checked into the disconnects being an issue by enabling Airplane Mode and seeing if I still had the same results, and unfortunately I do. I tried by disabling the Wifi and Mobile network separately, and still same issues.
But, here's an update on the issues:
Installed TYTUNG's NexusHD2-FRG83 V1.6, and this thing is very, very lightweight. Great battery life, great data (went to sleep, woke up, and not only was my phone still on...but I didn't have to reset data to check email...nice). The issues still remain. These are the newest things I've tried:
1) Remove Boxwave screen protector
2) Run from Airplane Mode.
I did however notice something really, really important: when the screen freezes, if I simulate a multi-touch gesture (pinch to zoom, etc), sometimes it wakes up! This is not a guaranteed thing (like 60%), but definitely something to work with.
Also, I noticed that one time that the touchscreen stopped responding, I tried the multitouch, no help...but I stayed on it. Multitouch tapped like crazy for a solid 6 seconds...then tried to shut the screen off -- and that button didn't respond. It was as if I saturated some bus of some sort that it had to clear out before it could finally shut the screen off.
Finally, I've noticed that the screen just needs to shut off for the touchscreen to unfreeze -- not go into a full lock situation. So, if the screen goes black, and I hit the lock key immediately, it'll unfreeze the TS.
Thanks to everyone who is trying to think of an idea!
i seem to be having the same issues as you right after i wake the phone up to unlock it. locking the phone is a habit for me to try and save as much battery as possible and also to not press any buttons while in my pocket.
im running a cyanogen rom and i changed the setting to allow me to unlock the phone by pressing the center windows key. i noticed that when the phone will not allow me to unlock it i can press the menu key and unlock it but i cannot use the touchscreen at all until i relock and unlock.
sometimes i have to do this a few times before the touchscreen comes back. i was thinking it could be my sd card but this started to happen today. i have been using android on my hd2 daily for the past 12 days without any problems. its weird that it started all of a sudden.
so it seems we still dont have a fix for the touchscreen freeze yet, right ?
Same problem here
Hi, I am experiencing the same problem.
Tried few versions of Android, The same problem repeated itself.
So I had to return to WM6.5 - there it works good. Only I have to reset the phone twice a day :-(
Hope someone will find brilliant solution for the sad problem that prevents using Android...
Any way to reset it (trying to see how long I can keep the phone on without restarting it)? It says 'Initializing etc. etc.' and the only way I can unlock the phone is by inputing my 4-digit security code. Thanks!
Turn off, turn back on. Motorola recognized that this might be a problem from week one of the device being out. I would assume they are working on a fix. Happened to me a couple times.
EDIT: Didn't see the part about you keeping it on as long as you can. I have not found another way around it as of yet. I didn't try too hard though, I just unlocked with my password to get whatever I needed and then rebooted when I had a chance.
I had the same thing happen once.
I went in to settings and the fingerprint reader off, then back on. Of course I had to rescan my fingers, but its the only way I could find to fix it.
Fingerprint Reader Issues
My fingerprint reader won't load. I have a feeling I restored something that I shouldn't have in Titanium Backup, but I have no idea what I need to remove to get it working again.
My Atrix has the OTA update and is rooted.
I can only get into my Atrix using the unlock code, which I guess I also restored. I'm sure this is a simple fix, but I'm still learning Titanium.
My reader crashed at one point. Restarting didn't work, and erasing my finger prints didn't work either. I wasn't able to input new fingerprints. The only way I could get it working was to remove the battery for a few seconds and the restart the phone.
Bought 2 S7 edge for myself and my wife. The first time we have the same phone, which should make my mis duties easier. We got the phones hours before a trip, so I didn't have much time to play beforehand. I set up my phone including fingerprints and when we arrived at our hotel, I noticed that the always on display no longer was nor did pull from right work anymore. and I'm sure other things broke too. Both features were turned on BUT when I attempted to do anything that required entering a pin? My pin no longer worked. The fingerprint reader still worked, so I was not locked out. I searched for an answer but gave up and reset the phone via recovery. I prodded my wife to add security to her phone and she and use the fingerprint reader and after a couple of hours? He pin no longer works either. The fingerprint still works but poorly and we can't change that anymore. Is there any way I can get back into the phone without a full reset?
Another disturbing thing? While running Waze a few hours ago, my phone spontaneously reboot. I'm digging the speed especially the camera and battery life vs my old G3, but If it reboots by itself one more time? it goes back!
And I just fixed it myself by happy accident. We decided to bite the bullet and do a factory reset via recovery BUT I goofed and went into bootloader instead (vol down instead of up). When the phone rebooted I tried the pin and it works once again. If it happens again, I'll try booting to recovery and then rebooting to system to see if it fixes the issue too. I've had a bunch of Android phones, a few of them Samsungs and this has never happened before.
I've had my phone for a couple of weeks, and the initial PIN I set up still works. Haven't had any problems like that. No spontaneous reboots, either.
meyerweb said:
I've had my phone for a couple of weeks, and the initial PIN I set up still works. Haven't had any problems like that. No spontaneous reboots, either.
Click to expand...
Click to collapse
So far, just the one reboot. I'm hopeful it's just a one-off thing. As for the pin thing? I've added a password just in case. It didn't turn out to be that much of a problem, but I hope leaving this here might help someone else who experiences the same event. Curious that it happened to 2 phones in the same family.
Have had my devices since March 11, PIN code has not changed by itself. Have had at least one UI reboot automatically, but I have a ton of apps so no good way to tell what caused it.
Sent from my SM-G935P using Tapatalk
Wish I would have read this first. I found my pin not working this morning. I thought I was going crazy. I use the same pin on multiple devices and keep them in sync, so I verified my mind was not toast by pinning into another device. I just completed a factory reset...
my Pin changed spontaneously
I've had my S7 for about 1 week and the pin changed on its own. I always use the same pin. I'm really frustrated and stuck in a 2 year contract with this thing. If I have to keep doing a hard reset every time this happens, I'll break the phone and get a new one under warranty.
As an update, after this happened to my wife's phone it happened to mine a couple of days later. After an apparent reboot over night (update?) my password was gone and I was unable to access the phone. Tried everything including contacting both Sprint, Samsung, tried bootloader and recovery, device manager, ect. No luck. Eventually had to reset. After reset, I changed to pattern (least favorite security option) and the issue hasn't reoccurred.(yet?) even with many reboots. I'm giving it another week and I will set up Samsung Pay and play 50 questions with my bank and cc cards.....again. I was in Home Depot with 500lbs of mulch on my cart when I realized I had no wallet. No problem, I can use Samsung Pay.....till I remember that the card info was wiped out with the last reset...DOH! Tech fail! I won't use a pin or password till I'm sure this bug has been squished.
From what I've gleaned, this is a bug specific to Sprint variants of the S7 and Sprint is aware of the problem.
jph8tr said:
As an update, after this happened to my wife's phone it happened to mine a couple of days later. After an apparent reboot over night (update?) my password was gone and I was unable to access the phone. Tried everything including contacting both Sprint, Samsung, tried bootloader and recovery, device manager, ect. No luck. Eventually had to reset. After reset, I changed to pattern (least favorite security option) and the issue hasn't reoccurred.(yet?) even with many reboots. I'm giving it another week and I will set up Samsung Pay and play 50 questions with my bank and cc cards.....again. I was in Home Depot with 500lbs of mulch on my cart when I realized I had no wallet. No problem, I can use Samsung Pay.....till I remember that the card info was wiped out with the last reset...DOH! Tech fail! I won't use a pin or password till I'm sure this bug has been squished.
From what I've gleaned, this is a bug specific to Sprint variants of the S7 and Sprint is aware of the problem.
Click to expand...
Click to collapse
Got bitten by this bug myself. Have had the S7 edge for a week and a half, fortunately still in the "playing" phase so forced to do a factory reset was not to bad...I too have switched to pattern and no issues either.
Yeah, it's the strangest thing. This happened to me as well only it was a password and not a pin. I honestly thought it was a mistake on my part. About a day after initially getting the device and setting up the fingerprint and password, my phone died ( I was using Gear VR and it didn't alert me that battery was even low), and when I rebooted it said something like " enter password for storage encryption" or something of the sort. I assumed it was my unlock password but it wasn't working....
So I looked all over the internet and all I could find were recommendations to try your normal unlock password. I tried and tried until I got the dreaded "you have 9 attempts remaining before factory reset" popped up. That's when I thought back to when I first set up the password and how I wasn't used to the edge of the screen yet. So I kept accidentally hitting keys on the edge while I was typing (because normally you can rest your hand on the edge, but on this if you do that you're pressing the edge of the screen). So I tried my exact password with one of the characters as a common "typo" that I kept making for that letter. And voila! It worked! Now the weirdness continues.
At this point I'm happy I figured it out but found it SO odd that I typed that password so many times and input a typo.... I must had used that password at least 15 times over that day....the odds of me doing a typo every time..slim. So the whole thing felt extremely sketch so I immediately went to change the password (and just turn off security in general, don't need it, just was playing around with fingerprint and needed password) after it booted up. And, of course, even with the typo the pass no longer worked. I tried it until the wait time between each try was an hour, heh. I tried all sorts of typo variations of the password, but to no avail. But, at least the phone was now ON. So I was able to backup my SMS, Apps, Settings, Themes, etc and prepare for the factory reset. What a wild ride.
I have no idea why it even happened in the first place. I never turned on any encryption and I never turned on "require password on boot up." Those settings were even toggled off when I checked while the phone was still on. (couldn't see all settings without password though).
Even weirder, I have no idea why the password with the typo even worked that one time to get it to boot. That same password never worked again.
IDK how widespread this is, but be CAUTIOUS and back up the things that you need to. Also, sign up for a Find My Mobile type service to unlock your phone and give you remote access should happen to you. Or just disable the security altogether until they announce a bug fix for this issue. I thought I was the only one with this issue and chalked it up to a weird freak occurrence. So thanks for the topic as I now know it wasn't just me.
Weird. Wonder what's triggering this. I've had my device since March 11 and haven't had it happen (yet). Hrmph.
Sent from my SM-G935P using Tapatalk
Update RE: my Sprint S7 with spontaneous pin change
Sprint S7 . I bought my phone 2 weeks ago, about 1 week in the PIN # (I had a 4 digit #) spontaneously changed. I could only get in with my finger print which only works 1/2 the time (don't both trying if your hands were just washed or out of the shower).
I decided to do a factory reset on Tuesday night and used a pattern tracing instead of a # pin. The phone worked fine for 2 days and then it happened again this morning. The pattern was spontaneously changed. I called Sprint, they told me they've heard nothing. I called Samsung same story there. I did try to power off the device (which I hadn't tried before) and turned the phone back on, it did recoganize the original password. So try shutting down and restarting...it might recognize it again. or try safe mode. I'm trying to trouble shoot this. I think the ADT app might be to blame?
This happened to me last week as well. A couple reboots cleared it up. Very odd though.
jph8tr said:
And I just fixed it myself by happy accident. We decided to bite the bullet and do a factory reset via recovery BUT I goofed and went into bootloader instead (vol down instead of up). When the phone rebooted I tried the pin and it works once again. If it happens again, I'll try booting to recovery and then rebooting to system to see if it fixes the issue too. I've had a bunch of Android phones, a few of them Samsungs and this has never happened before.
Click to expand...
Click to collapse
Saved my freaking life man! Same thing happened to my wife's phone. I went into Boot Mode (power down, the on power up hold power and volume down button), then selected start phone normally.
Her original PIN worked! She was freaking out!
Thank you!
Not sure if Boot Mode was needed or just a normal reboot... But it's fixed!
Same problem. Luckily I barely use this phone for anything other than calls. I did a hard reset immediately. You guys are not the only ones out there.
My Samsung S7 Edge just did the same thing this AM. PIN changed, no idea what it is. Fingerprint works. Will back it up and do the reboot first. TMobile so this issue is not Sprint specific.
This just happened to my wife's s7 (Verizon) if you reboot the phone for any reason the back up pin or pattern is required it which it was but doesn't work... And of course were not sure if she made a Samsung account cause if you have a Samsung account supposedly you can change the password from a browser through that site. With this and the screen randomly shutting off and not coming back to life til you run through the boot menu I'm not so sure I'll be getting another Samsung phone.
This glitch of auto PIN change occurred on my Verizon S7
:crying: To be clear, this occurs on other carriers as I am using Verizon. Issue: PIN is no longer recognized but fingerprint works only until the device is rebooted. If rebooted, fingerprint no longer works and all you can do is receive calls. Samsung advised me that Verizon has a way to reset password.
As I write, Verizon (a level 2 tier tech named William) was able to show me how to fix this by logging into my Google account, and enabling "lock and erase" and clicking on "lock" I was able to change my PIN and my phone works fine! Now I am updating the software as Samsung released a software update on September 1, 2016, that fixes the problem. A word to everyone: be sure your google account is active and includes your S7. Be sure to download the software update!!!!!!!!!!!!!!!
jph8tr said:
As an update, after this happened to my wife's phone it happened to mine a couple of days later. After an apparent reboot over night (update?) my password was gone and I was unable to access the phone. Tried everything including contacting both Sprint, Samsung, tried bootloader and recovery, device manager, ect. No luck. Eventually had to reset. After reset, I changed to pattern (least favorite security option) and the issue hasn't reoccurred.(yet?) even with many reboots. I'm giving it another week and I will set up Samsung Pay and play 50 questions with my bank and cc cards.....again. I was in Home Depot with 500lbs of mulch on my cart when I realized I had no wallet. No problem, I can use Samsung Pay.....till I remember that the card info was wiped out with the last reset...DOH! Tech fail! I won't use a pin or password till I'm sure this bug has been squished.
From what I've gleaned, this is a bug specific to Sprint variants of the S7 and Sprint is aware of the problem.
Click to expand...
Click to collapse
universityextension said:
:crying: To be clear, this occurs on other carriers as I am using Verizon. Issue: PIN is no longer recognized but fingerprint works only until the device is rebooted. If rebooted, fingerprint no longer works and all you can do is receive calls. Samsung advised me that Verizon has a way to reset password.
As I write, Verizon (a level 2 tier tech named William) was able to show me how to fix this by logging into my Google account, and enabling "lock and erase" and clicking on "lock" I was able to change my PIN and my phone works fine! Now I am updating the software as Samsung released a software update on September 1, 2016, that fixes the problem. A word to everyone: be sure your google account is active and includes your S7. Be sure to download the software update!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
I tried the Google method but every time I try to change the pin it just tells me that Google verified that there is already a lock screen pin so the new pin/password won't be necessary.. l would love to find a fairly simple route as all the adb pin/password removal videos and such are a little different and well it's my wife's phone so it's a little more important to save her stuff then mine
Hi guys, today when i rebooted my Vernee Apollo Lite i got stucked when trying to access my phone supposely because i was putting a wrong pin when trying to access the android system. I'm pretty sure that i was putting the pin well but nothing works. I've even already done a hard reset to the phone but it stills ask me for a pin that i don't know which is. Can anyone please try to help?
Is anyone else experiencing this issue. The device was locked with a PIN and fingerprint recognition. During extensive use last weekend the lock would disengage meaning the device could be opened by merely swiping. I therefore removed the fingerprint recognition and reverted to PIN only. However again after extensive use the lock was bypassed.
When you switched on the phone the screen showed "Swipe screen to unlock" If the padlock was below this phrase it was open and no PIN was required. You could however press the padlock and it would jump to be above the phrase and then required the PIN to unlock. However after switching off the phone it would often revert to be "open".
I can't seem to find anything about this by googling so would welcome suggestions.
Thanks,
Brian
PS If the phone is only used lightly during the day the device remains secure.
That sounds weird. Upon a restart the phone will always ask for the alternative method of unlocking (pin or password for example) rather than simply unlocking with fingerprint. But after that first time it should work fine. Personally, I have mine to set to unlock with only a fingerprint. Perhaps the fact you use both at all times could be causing the issue?
Are you on vanilla stock the phone came with? Have you tried updating it?
Beefheart said:
That sounds weird. Upon a restart the phone will always ask for the alternative method of unlocking (pin or password for example) rather than simply unlocking with fingerprint. But after that first time it should work fine. Personally, I have mine to set to unlock with only a fingerprint. Perhaps the fact you use both at all times could be causing the issue?
Are you on vanilla stock the phone came with? Have you tried updating it?
Click to expand...
Click to collapse
Thanks for the response.
I thought it was weird as well as the S5 never had this problem but of course it did not have fingerprint unlocking.
Yes it is Marshmallow straight out of the box and has had one update so is now running 6.0.1
I did sometimes have a problem with the fingerprint recognition so I would be reluctant not to retain the PIN!!!
S5 did have fingerprint unlocking, it was simply not as good as you had to slide your finger down the button. It did work though.
I recommend an update. Or, if you don't mind tripping knox, install one of the custom roms on this site or one of the other roms off site (like the one listed in my signature). Each new release of these custom roms are normally built on the latest base that is out there so you would hope any bugs like this would be fixed, assuming it is a bug.
Thanks, I'll give it a go. After the Lollipop upgrade bricked my Asus Nexus 7 I have been reluctant to do upgrades unless absolutely necessary.
Hi, first of all I apologise if this question has been asked but I don't know how to search just this place.
I'm using everything stock, no root, stock launcher.
I have my phone set up to ask for the password on reboot. I have my fingerprint reader set up to unlock my phone. I also have the fingerprint reader set up to wake the screen.
However under certain circumstances the fingerprint reader does not unlock the phone. The most reliable way to trigger this behavior is to plug the phone in to charge.
I exclusively lock the screen with the power button.
The fingerprint reader is still responsive and it still wakes the screen but there's no vibration feedback and it does not unlock. After I unlocked the phone with my password and lock it again the reader works again.
So what's going on here? How should I debug this?
After reboot it is normal to ask for password first time. Sometimes i have also seen this but when i unlock with pattern (my backup way) and lock again it works fine. I can not trace this to be related with charging or something else and it happens rarely but i have seen it also. Maybe a software bug.
Looking back to the days when i have LG V10 i remember that i had the same problem with fingerprint sensor not working sometimes. It was more frequently related to heat buildup as it was hot phone anyway.
I had the same problem these days, I think the fingerprint reader won't work if your hands are really cold.
Hmm I don't think my U Ultra is getting particularly hot and, no, my hands are certainly not very cold either. This behavior happens indoors.
It's just extra security plan and simple
Sometimes, not very often though, my fingerprint reader refuses to respond. Not even a misread where you get haptic feedback and not a lot else.
Just using the power button and entering my back up security (pattern in my case) and it comes back to life.
I don't particularly worry about it, but I suppose it's nice to see that it's not just me
Will see if the upgrade to 8.0 fixes it.
I met this problem.The solution was very interesting.I use Yandex.disk app.This problem did occur after the Yandex.disk app is update.I hard reset my phone.The problem was not in my phone.But I setup Yandex.Disk app the problem repeat occur.İf you installed Yandex.Disk, uninstall the application.if you don't use Yandex.Disk,The last apps update uninstall to try.
Good Lord I have so many apps installed though...
Then go to a full factory reset and see if it helps, thats the 1st thing you do when you have problem.
After a bit of experimentation this behavior seems to have stopped after I disabled/removed all Smart Lock Trusted Places -- a feature that is already known to be buggy.
I have it too, once a day it puts me to enter the password, its a security or a bug idk.
No more, no less, every time when its charging. I installed some 3rd party apps, its possible that they are to blame.
We will see when 8.o strikes and i will hard reset.
Garkan said:
I have it too, once a day it puts me to enter the password, its a security or a bug idk.
No more, no less, every time when its charging. I installed some 3rd party apps, its possible that they are to blame.
We will see when 8.o strikes and i will hard reset.
Click to expand...
Click to collapse
8 fixed this bug for me but i found more bugs in oreo so i am thinking to roll back to 7.0 and meet fingerprint sensor bug again because oreo problems are disgusting - car bluetooth does not works as it should - i can't read addressbook in my car head unit - it shows error. i found that is some bluetooth software parts was not included in 8.0 but successfully fixed in 8.1. and i'am pretty sure we will never receive 8.1 for u ultra.
in russian 4pda forum i found some reports (unconfirmed yet) that fingerprint bug disappeared. maybe somebody here can confirmed it?
No i have android 8 and issue still occurs sadly did not found a fix.
I've suddenly had this issue a couple of days ago a couple of times. I didn't do anything (except a couple of reboots) and it was fixed again.
Now after updating to Oreo and again using leedroids ROM, i didn't experience theissue again..
I talked to a htc representative and said to clear credentials from security/encryption and credentials seems to be a conflict in security certificates. For the moment it works.