Related
I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
GHII said:
I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
Click to expand...
Click to collapse
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
tiguy99 said:
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
Click to expand...
Click to collapse
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
I'm having the same issue with knock on not working. i've wiped a few times and have flashed diferent roms but it wont turn the phone back on. i'm also having this strange issue where i cant pull the notification bar down.
EDIT: I figured it out. did you install TWRP Recovery? i did and mine was messed up. i flashed back to stock and re-rooted and everything works again. I'm not sure if TWRP is the reason since im on a t-mobile G2 but reflashing to stock definitely worked. also i think you have to do a reset after flashing rom because the changes wont take effect unless you do
GHII said:
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
Click to expand...
Click to collapse
Wow that's a relief, I'm having the same pull down issue too.. Even scrolling here is a dead spot on the screen if I'm scrolling a page or list as I get in that area it "slows". I thought my digitizer was going bad. I found my knock on works but I have to do it extremely slow... Tap... Pause 1-2...tap.
Edit yes to twrp.
Sent from my VS980 4G using xda app-developers app
well i re-rooted and it doesnt work anymore. i deleted stuff so i need to see if its something that is being removed that causes it to not work
I just flashed the stock rom back..shows unrooted again, and it is still doing the same thing. Im still under my 30 days, Im going to return it, hope for the Nexus 5 on verizon by the weekend and if not I guess buy a new G2.
mine still says rooted so i'm kinda screwed right now
Same issue
Same thing with my T Mo G2. Using Nova launcher. Knock on worked flawlessly since new, about 2 months,use Nova gesture for knock off. Suddenly knock on stopped working. Too bad, because I like the feature, got used to using it. Did a restore and wipe using TWRP, kept root access, but still no knock on. Next I'll try going back to stock ROM, but I'd rather go an easier route. Has anyone successfully restored knock on?
Hi i have a dead spot somewhere app in the screen and when i pull down the notification bar it doesnt goind down.Also i tryed to draw with quick memo and i can see that it is a dead spot somewhere near the top of the screen
Does anyone has the probleme and have you fixed it
The only solution is returning the phone
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
rastigo said:
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
Click to expand...
Click to collapse
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
ankurcshah said:
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
Click to expand...
Click to collapse
I read the following posts on some other forum...so essentially its a hardware issue....try stock jb rom kdz, then factory reset and reboot. If this helps solve the problem you are lucky. If not, try getting your phone replaced with 802 model. That is practically most stable with a lot of devlopment and tons of ROMS stable and working.
I will still keep looking for a solution and let you know consulting a few senior xda devs I know... sorry man, it hurts to see a fellow indian in distress.....:crying:
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
That's odd, I have not seen much on this... if running stock
Quote:
Originally Posted by Burkettacb View Post
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Or againg, a ROM you may be using.
More detail would be helpful
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
Good luck with that if the phone is a D800. I took my G2 to the local AT&T store just a couple of hours ago with the same "no knock on" bug. But the sales person (who had bad breath) told me that because there was another way to get the phone to function (the back button), they won't even look at it. The fact that the knock off/on feature was a MAJOR selling point when the phone was released is apparently irrelevant.
He has a ls980 so it might not be the same for him. He can ask for a replacement
Sent from my LG-D802 using XDA Premium 4 mobile app
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Andrew_han said:
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Click to expand...
Click to collapse
Did you try the "Hidden Menu" "Touch firmware update" option? I had this issue and it got fixed with it.
try 3845#*modelnumber# eg: 3845#*800# change model number 800 with your phones model number, then tap on "Settings" and scroll down to "Update Touch Firmware"
I have a few more suggestions to make it work, let me know how it goes.
Since DOK2 is new and there are several hopes from many of the new firmware, I figured it would be best to make a thread about it.
To those on DOK2 (Especially 100% stock, i.e. stock kernels), please post your feedback.
One of the main things to look for is directed at FingerPrint unlock users.
After enabling FingerPrint unlock does the phone randomly lock itself?
Does the FingerPrint crash / TouchWiz crashes?
(This should be apparent with in the first 24 hours of enabling the FingerPrint lock)
The next main thing to look for is just general issues after the phone being on for some time. This would indicate memory management issues and would show up after hours / days with out a restart.
Are you loving the new Firmware? Post about that too!
Your feedback is valuable so please take the time out to post your experiences with DOK2.
Thanks!
I'm loving the new firmware. The phone "feels" faster in switching between applications.
The fingerprint lock-screen bug is gone (for me). Memory management has improved drastically. The only thing that is the same is the battery life in power saving mode. The update is worth it for me, so I'm not as eager as I was before to get marshmallow as I was before.
Note: This phone has never been rooted
I got the update and noticed a few bugs here and there. I fully wiped twice and it resolved everything. It's smoother, faster, same battery life, keyboard and fingerprint bugs fixed. I really like it so far. It runs like it should. I'm a happy camper now.
I've never rooted, full stock.
Remember to go to options > storage and clear your cache after updating! From COG2 to DOK2 I have never had fingerprint unlock issues. If anything it seems more accurate and faster. There is more ram I fall between 1.7-1.8gb (instead of ~2gb) used when everything is cleared. There has been no random reboots since the update. There is no more weather widget re-sizing itself and black shadowed font while scrolling through home screens. My antutu score went from 52000 to 48000 though. I am 100% stock never been rooted.
I've heard tell that you can't downgrade your bootloader back to COG2 after installing DOK2 update. Any word on this? Even through Odin?
^Even if you can't, why would you want to? 5.1.1 is better in every way from 5.0.1
My computer will not recognize my phone via sub after the upgrade
chocolatet said:
My computer will not recognize my phone via sub after the upgrade
Click to expand...
Click to collapse
sub? I assume you mean usb.. Did you wipe/reset everything? Even though this is an official update dirty flashing is dirty flashing. Wiping is still a troubleshooting step.
Love it so far.
The one thing that I have noticed is that the task switching is much faster. When I used to press the button, it would take a few seconds to load, now it's pretty much instantaneous.
I tried turning on the fingerprint unlock, but I was still having too many swipes to get it to unlock, so I turned it back off.
Techngro said:
The one thing that I have noticed is that the task switching is much faster. When I used to press the button, it would take a few seconds to load, now it's pretty much instantaneous.
I tried turning on the fingerprint unlock, but I was still having too many swipes to get it to unlock, so I turned it back off.
Click to expand...
Click to collapse
When you register you finger do you swipe at different angles each pass?
That is a must. My fingerprint scanner (when not crashing) works flawlessly. I never have had a problem with swipes.
DeeXii said:
When you register you finger do you swipe at different angles each pass?
That is a must. My fingerprint scanner (when not crashing) works flawlessly. I never have had a problem with swipes.
Click to expand...
Click to collapse
Yeah, I did that. I did it one time and then I did it a second time with different angles.
Can anyone address if their GPS accuracy has improved?
Test
Sent from my SM-N910T using Tapatalk
Test 2 shy did it add a to my name
Sent from my SM-N910T using Tapatalk
Data speeds are much improved with the update. The device is snappier also. I haven't noticed a difference in GPS - seems about the same as before the update. Haven't had time to gauge battery life fully but that also seems improved.
Over all a very well put together update. I'm pleased.
I haven't rooted yet and I'm not sure I want to take this update yet. How can I turn off the auto update feature? The phone is telling me it wants to download the update and the next time I connect to wifi it will. Is there any way to prevent this?
Thanks
Rootabaga said:
I haven't rooted yet and I'm not sure I want to take this update yet. How can I turn off the auto update feature? The phone is telling me it wants to download the update and the next time I connect to wifi it will. Is there any way to prevent this?
Thanks
Click to expand...
Click to collapse
WARNING if you update your tmobile note 4 from 4.4.4 or 5.0.1 to 5.1.1 lollipop then dont do it. problems are the phone download super slow even if your on the best internet connection or using your own data. and if you like 4.4.4 or 5.0.1 then you will not be able to downgrade back to them. its no way to downgrade at all. im trying to sale mine on craigslist and get another one now
So weird, I installed it yesterday, rooted, and loaded a ported version of Kyubi's ROM. It's an awesome ROM, but too laggy on n910t. Reinstalled DOK2, and I canNOT root it again via Odin 10.7 or 10.3. It loads, and then goes into a boot loop. I've tried like, 5 times. Kinda sucks
Michael in ATL said:
So weird, I installed it yesterday, rooted, and loaded a ported version of Kyubi's ROM. It's an awesome ROM, but too laggy on n910t. Reinstalled DOK2, and I canNOT root it again via Odin 10.7 or 10.3. It loads, and then goes into a boot loop. I've tried like, 5 times. Kinda sucks
Click to expand...
Click to collapse
I just learned this recently, so I guess it's my turn to pass this information to others.
You need custom kernel to be able to root. Flash BeastMode Kernel by @freeza.
Just got this today and it's great besides being a bit smaller than my g6 and because of front camera design only being technically 5.5in screen for most apps especially games.
However since I have had it, it has randomly rebooted itself twice for no real apparent reason. Is this a known issue or something anyone else has experienced? I want to try to get a bit more information on it before contacting the eBay seller. It is a refurbished.
I have never experienced a random reboot. You might want to try factory resetting your phone and then setting it up with the fresh start option instead of restoring from a Google cloud backup. Was your phone on Nougat or Oreo when you received it? Were there any major software updates?
It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.
Nickvanexel said:
It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.
Click to expand...
Click to collapse
Must be rogue app, had mine 3 months and never had a glitch or reboot.
Sent from my PH-1 using Tapatalk
If you are still having the random reboots you might want to boot your phone into safe mode to verify that a third party app isn't causing the problem. Since your phone was refurbished it's also possible that it was damaged by the previous owner or returned for the same issue you are experiencing. I did read that some early PH-1 buyers had to return their phones because of hardware issues like overheating.
Just did it again while using chrome. Just froze up for a few seconds and restarted. Doesn't seem to be overheating and the first time it happened before I installed anything I think. Guess I'll try a reset and go from there.
Factory reset twice now. No 3rd party apps installed. Updated all apps on Google play. The default phone apps.
Now the phone is freezing and rebooting itself constantly. Out of control. I am in safe mode right now and hasn't frozen yet. I don't know what the hell is going on.
Would love to be able to fix this issue myself without having to do return shipping. I have contacted the seller already though.
If it doesn't freeze or reboot at all in safe mode that usually means an app that you downloaded is causing the problem. The normal thing to try would be to factory reset the phone, download one app and see if there are problems. If the phone seems to be fine download a second app and use the phone long enough to see if the phone is stable. If it seems fine download a third app and do the same.
That's obviously very time consuming and if you were running a phone with heavily modded code like OnePlus with Oxygen it would probably be worth the investment of time. But this phone runs stock Android. Unless you are installing something unusual that might cause stability issues what you are describing sounds like a hardware problem. You might have bad memory for example and not enough is going on when the phone is in safe mode to trigger the unstable behavior.
I think returning or exchanging the phone you bought is definitely your best course of action. I really like this phone but it sounds like yours is defective or damaged.
The only other thing that comes to mind is that sometimes if you own more than one phone the Play Store will show apps that aren't compatible with the phone you are actually using. Dialers, messaging apps, camera apps and music players made for a specific phone brand aren't usually compatible with other brands because they need modded framework to function properly. Some apps that definitely are not compatible with this phone do show up in my Play Store Library available for download. Is it possible you are downloading an incompatible app?
I factory reset and haven't installed a single app. Just updated everything that was stock with the phone after reset. I was thinking faulty ram too, seems like it is.
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Grab a BTS zip from the back to stock thread... And flash that...
I'll bet however it was updated had some yuck in it...
Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Someone in the Essential stock ROM dump thread just described the exact same behavior that you are experiencing. He hopes reflashing stock will fix it but since it's identical to what's happening with your phone I think he's going to end up disappointed. You might want to check out his post and see if he has any luck. It was the latest post in the thread so it should be easy to find.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page41
Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.
Nickvanexel said:
Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.
Click to expand...
Click to collapse
Sorry I didn't notice that. I haven't done any flashing on this phone but I know I read that people with the Sprint phones were flashing the regular stock image to get rid of the Sprint apps and get updates from Essential rather than Sprint. But if you don't want to unlock your bootloader you can download official factory images from the Essential website and sideload using a computer. Flashing instructions are on the download site.
https://www.essential.com/developer/current-builds
Alright I reflashed the latest firmware from essential page via adb sideload. I highly dout it worked but I'll see.
What would I need to do from here to do a complete fresh reflash completely overrighting any trace of the old os? I still want to keep it stock but doesn't matter if I need to unlock the bootloader. Just want a complete wipe of the old os and fresh reflash to be sure any traces of corruption are removed to be sure if it's a hardware issue.
That's easy on single partition phones but much more difficult on phones with an A & B partition like the PH-1. You definitely need to unlock the bootloader. On my Pixel XL you needed to flash the factory image separately to partitions A & B to ensure there was nothing left from before but the procedure might be different on this phone. I went through the flashing instructions when I got this phone and think if you flash the full restore stock image it supposedly returns both partitions to stock automatically but that definitely didn't happen on the Pixel. Considering that this phone is supposed to be easy to hard brick (which was virtually impossible on the Pixel) I wouldn't chance it unless you can't return or exchange the phone from the seller.
Well side loading the ota from essential website didn't work. I'd say it's already hard bricked. Still crashing after a while of using it. Last night I loaded as many apps at one time as I could. Got maybe 10 opened at once before it crashed. Seems like faulty ram to me.
Wife just had it happen on her new White one twice today while playing Pokemon GO.
She says she also had her podcast app and hangouts open but minimized and not being actively used in the background.
She's on a fresh install of Oreo 8.1 with the Gcam mod by MGC_5.1.018_Urikill_vXXII.apk using the settings suggested by aer0zer0
Anyhow I hope its just a completely random fluke and not a serious issue as I have a new black one from Amazon in the mail and would really hate to have to return these otherwise wonderful devices.
Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.
Nickvanexel said:
Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.
Click to expand...
Click to collapse
Ouch okay that most certainly sounds like a bad hardware issue as you suspected earlier.
Thankfully in her case the reboots were well apart from one another and the phone was fine after the reboot. Even let her play PKGO.
I mostly came in to comment to hopefully help by voicing that it had happened and the circumstances in which it did for her with the idea it might pinpoint some flaw in the overall system if there was one.
Hi Guys,
I got a brand new OnePlus 6T a few days ago. I installed the latest software update, from November 1st, and set my device up. I registered 2 fingerprints originally which did not seem to work that accurately but I figured this was because the device was still learning my fingerprint. This morning I woke up and tried to unlock the device with my fingerprint but it was not working. I then went into settings and removed my 2 fingerprints and tried to reregister them. However, when trying to reregister them the device was not detecting my finger at all. At this point I rebooted the device but now in Settings there is no longer a fingerprint option at all.
I have seen a few other posts about this, especially after the November 1st patch. Are there any known ways to resolve this issue?
Seanaldo said:
Hi Guys,
I got a brand new OnePlus 6T a few days ago. I installed the latest software update, from November 1st, and set my device up. I registered 2 fingerprints originally which did not seem to work that accurately but I figured this was because the device was still learning my fingerprint. This morning I woke up and tried to unlock the device with my fingerprint but it was not working. I then went into settings and removed my 2 fingerprints and tried to reregister them. However, when trying to reregister them the device was not detecting my finger at all. At this point I rebooted the device but now in Settings there is no longer a fingerprint option at all.
I have seen a few other posts about this, especially after the November 1st patch. Are there any known ways to resolve this issue?
Click to expand...
Click to collapse
Hmmm.. that seems strange. It sounds like you are locked / unrooted, is that right?
Lartsch said:
Hmmm.. that seems strange. It sounds like you are locked / unrooted, is that right?
Click to expand...
Click to collapse
Yes, correct unrooted. I found this thread on the Oneplus forum about it but seems like nobody has a solution: " Fingerprint sensor doesn't show up - OnePlus 6T" (New user so can't post link)
Hey guys I also run into this issue. Does anyone found a solution yet? Haven't try factory reset yet.
risay07 said:
Hey guys I also run into this issue. Does anyone found a solution yet? Haven't try factory reset yet.
Click to expand...
Click to collapse
I haven't found a solution yet. I posted a bug report to OnePlus, and a OnePlus BugHunter had me gather logs to give to the Dev team so it does sound like something they're looking into.
I took a look at the logs myself and gathered the following:
FingerprintService is running without issues and it connects to the Fingerprint HAL (over HIDL) fine. However, it attempts to call setNotify on the HAL and is supposed to receive a non-zero Device ID back but instead it returns "0." Because of this the FingerprintService reports an error. Why does setNotify return 0? That's where I'm a little unsure, it looks like the HAL is operating correctly but the Fingerprint driver failed to initialize properly. I'm not too familiar with the Fingerprint driver (especially since a vendor can diverge from the normal implementation flow) but from what I can gather it is suppose to start by validating 3 GPIO (fp-gpio-id0, fp-gpio-id1, fp-gpio-id2), but it seems like on my device the driver only validates the first GPIO and then nothing:
Code:
01-09 01:41:35.032 0 0 I : @4 fingerprint_detect_probe
01-09 01:41:35.032 0 0 I : @4 fingerprint_detect soc:fingerprint_detect: fp-gpio-id0 - gpio: 91
01-09 01:41:35.032 0 0 E : @4 fingerprint_detect soc:fingerprint_detect: fingerprint_detect_probe: gpio_is_valid(fp_detect->id0_gpio=91)
There might be more in the kernel logs that I'm missing, but that's what I noticed so far.
Seanaldo said:
I haven't found a solution yet. I posted a bug report to OnePlus, and a OnePlus BugHunter had me gather logs to give to the Dev team so it does sound like something they're looking into.
I took a look at the logs myself and gathered the following:
FingerprintService is running without issues and it connects to the Fingerprint HAL (over HIDL) fine. However, it attempts to call setNotify on the HAL and is supposed to receive a non-zero Device ID back but instead it returns "0." Because of this the FingerprintService reports an error. Why does setNotify return 0? That's where I'm a little unsure, it looks like the HAL is operating correctly but the Fingerprint driver failed to initialize properly. I'm not too familiar with the Fingerprint driver (especially since a vendor can diverge from the normal implementation flow) but from what I can gather it is suppose to start by validating 3 GPIO (fp-gpio-id0, fp-gpio-id1, fp-gpio-id2), but it seems like on my device the driver only validates the first GPIO and then nothing:
Code:
01-09 01:41:35.032 0 0 I : @4 fingerprint_detect_probe
01-09 01:41:35.032 0 0 I : @4 fingerprint_detect soc:fingerprint_detect: fp-gpio-id0 - gpio: 91
01-09 01:41:35.032 0 0 E : @4 fingerprint_detect soc:fingerprint_detect: fingerprint_detect_probe: gpio_is_valid(fp_detect->id0_gpio=91)
There might be more in the kernel logs that I'm missing, but that's what I noticed so far.
Click to expand...
Click to collapse
Does that means its a software issue?
I've just done a factory reset and now I'm more stressed. Factory reset does not fix it, at least for me. After the reset, at the first phone setup where we were asked to enter Gmail and setup security, when it comes to setup fingerprint, the fingerprint area does not light up. Put my finger at the fingerprint sensor area and nothing light up. Press Back and enter the fingerprint setup again, now the fingerprint area does light up. It shines when I put my finger, but still detects nothing. It does not vibrate and the screen does not show any progress of the finger being scanned. So I skip the fingerprint setup and finish setup my phone, went into Settings and the option for fingerprint is still missing. Went into *#808# fingerprint test and it showed an error "The application cannot reach the android service for the sensor". Now I'm tempted to send it back for warranty because I'm afraid its a hardware issue.
I'm no expert in this, but it seems the fingerprint "device" isn't being found by the fingerprint HAL. I'm guessing hardware issue is at fault.
Frankenscript said:
I'm no expert in this, but it seems the fingerprint "device" isn't being found by the fingerprint HAL. I'm guessing hardware issue is at fault.
Click to expand...
Click to collapse
I would normally agree, but the kernel logs don't indicate any type of hardware failure. From what I've seen in the logs, the driver just kinda breaks during its initialization. It is pretty unlikely that it's a software issue, but based on the logs there's really nothing that indicates either way. With a quick Google search I have seen a few other people reporting this issue, plus me and risay07 so I would hope it's not a hardware issue because of how common it seems to be.
This may be a dumb suggestion, but: when it doesn't show the fingerprint to unlock, have you tried swiping up from the bottom of the screen? Sometimes I've noticed that when it wants passcode for additional security, it doesn't show the fingerprint and it doesn't show the prompt for the numbers. Huh. Found that in this case fingerprint isnt an option and I was puzzled how to proceed. Eventually swiped up giving me the number pad. After that fingerprint was reenabled.
Just a thought, good luck!
Sent from my ONEPLUS A6013 using Tapatalk
Same thing
I have encountered the same issue today, fingerprint stopped working. While trying to unlock it just kept scanning.
I unlocked with PIN I went to settings>security & lockscreen to see what happened and I noticed that the fingerprint option is gone.
Then I contacted support. They suggested that I do a hard reset and if that doesn't work it means it is a hardware issue and I should apply for service.
So I did the hard reset and still I get the same thing. Unfortunately it means that it's time for service, just after 7 days of use.
We got faulty units I guess.
Mariusvvv said:
We got faulty units I guess.
Click to expand...
Click to collapse
Definitely possible. Since I have an open bug report being investigated I'm holding on to mine for now. The worrying part to me is that the device must have been working out of the factory and was working (though for me kind of poorly) for the first few days of ownership. I wonder if this is an indication of future hardware problems that can come up even on units that are good right now.
I would encourage people with the same issue to reply to my thread here so that OnePlus is aware that this is a common issue: https://forums.oneplus.com/threads/fingerprint-option-missing.975435/
Seanaldo said:
Definitely possible. Since I have an open bug report being investigated I'm holding on to mine for now. The worrying part to me is that the device must have been working out of the factory and was working (though for me kind of poorly) for the first few days of ownership. I wonder if this is an indication of future hardware problems that can come up even on units that are good right now.
I would encourage people with the same issue to reply to my thread here so that OnePlus is aware that this is a common issue
Click to expand...
Click to collapse
For me the fingerprint was working perfectly from the start without any tricks, like registering a finger twice, etc..
Maybe the last day it slowed down if I remember correctly.
Looks like one my OnePlus bug report there are now several people reporting the same issue. I haven't heard anything back from OnePlus since Tuesday (which was just a "we're still looking at it"). I'll ask for an update
One of OnePlus representative contact me after I posted comment at your bug report. He told me to do a log and reproduce the issue. I told him there is no way to reproduce the issue since the fingerprint settings is missing. He told me to start logging then enter settings to set fingerprint. I keep telling him that there are no fingerprint settings at the settings and he just keep telling me to enter fingerprint settings like usual and the log will pick up if it failed to work. I think I'll do log once I'm free but I'm not sure what to do after I start logging.
risay07 said:
One of OnePlus representative contact me after I posted comment at your bug report. He told me to do a log and reproduce the issue. I told him there is no way to reproduce the issue since the fingerprint settings is missing. He told me to start logging then enter settings to set fingerprint. I keep telling him that there are no fingerprint settings at the settings and he just keep telling me to enter fingerprint settings like usual and the log will pick up if it failed to work. I think I'll do log once I'm free but I'm not sure what to do after I start logging.
Click to expand...
Click to collapse
The best way to get logs for an issue like this is to reboot the device and then do the logging instructions that he gave you. Just leave the Log "running" for a few minutes (~2 minutes) and you can then close it and send him the log files. The important part here is rebooting the device because the logs will contain the Device boot, Kernel Init, and it will show the Fingerprint Driver and Service attempting to be initialized.
I am at wits end. Here's how my situation has unfolded:
- Was running OOS 10.3.2 international, bootloader locked stock on a T-Mobile 6T (been running solid since 9.0.11 MSM hack early last year, updated progressively as the "System Updates" have appeared)
- No customization or tweaks
- Starting late last week, phone has been (seemingly) randomly crashing to black screen, then to spinning dots, like its booting
- I have to Vol up + power to turn off, then reboot
- I captured a logcat of the crash, which may be useful to someone, I just see the system handling a notification, then a system level ANR happens, taking out the core system processes?
I have tried:
- Google/OP backup -> factory reset -> restore account, apps, calls, sms and settings -->> still crashing
- OP backup -> factory reset -> add as fresh account, restore OP bu apps, calls, sms and settings -->> still crashing
- OP backup -> MSM downgrade to 9.0.11 -> unlock bootloader -> install TWRP, Magisk, TWRP install 10.3.2 international -> fresh account, restore SMS messages, etc
After the last attempt, ran all morning without crashing (yay!), proceeded to utter the words to my son ,"hey, fixed my phone, no crashes!", phone crashes 5 minutes later
Then I thought, "well I just signed in to Firefox sync, maybe that's it??", uninstall Firefox. Hour later, crashes during a phone call.
Okay, then thought maybe its something goofy with stock kernel? Install Omega kernel. Crashes 2 hours later on another phone call.
It also seems to crash fairly consistently in my pocket, and I have noticed "Pocket Mode" does not work (overlay doesn't appear when covering proximity sense; sensor works, tested with an app)
Am I experiencing a flaking mobo or some other hardware issue? Please tell me no, I am at 16 months with this phone, so factory warranty is out (and 6 months to go on my payment plan/offer).
Before I try LOS 17.1 (and probably still get crashes :silly, thought I'd try asking for insight here. I have tried googling for similar issues and searching forum threads, but no dice. Thanks!
Well, I have an update here. I turned off "Pocket Mode" last night for giggles, and lo and behold, I have 20 hours up time with no crashes. Proximity sensor works, took several calls today and screen turns off when covering it. Also put phone in pocket regularly to test, no crashing.
Hopefully this helps anyone else with this strange issue. Kind of sucks that I am going to potentially butt call people, but, less pocket time these days while we're all stuck at home (COVID-19 "stay at home", for those reading this post years from now wondering what the heck I'm talking about).
Sad news, random reboots persist. Going to try LOS to rule out OOS (which I can't see it being since others would be complaining too). Hopefully its not hardware, but maybe I jacked my phone up by dropping it one too many times. We'll see.
hondoslack said:
Sad news, random reboots persist. Going to try LOS to rule out OOS (which I can't see it being since others would be complaining too). Hopefully its not hardware, but maybe I jacked my phone up by dropping it one too many times. We'll see.
Click to expand...
Click to collapse
LOS 17.1, random reboots persist . Thinking my phone is toast...
hondoslack said:
LOS 17.1, random reboots persist . Thinking my phone is toast...
Click to expand...
Click to collapse
Try this port rom from op7..
Working great ..easy to install and super stable
https://forum.xda-developers.com/oneplus-6t/development/rom-oneplus7-beta-2-t3971383
have the same exact proble mwith my sons onepus 6t tmobil version, it was ported over to oneplus 6t international version, so we could use it one att.. I done system hardware test and it shows no problem.. I too was thinking of installing lineage os, but I'm lost.. anyone chime in on good tutorial...
sderaps said:
have the same exact proble mwith my sons onepus 6t tmobil version, it was ported over to oneplus 6t international version, so we could use it one att.. I done system hardware test and it shows no problem.. I too was thinking of installing lineage os, but I'm lost.. anyone chime in on good tutorial...
Click to expand...
Click to collapse
Unfortunately I've pretty much confirmed mine was a bad motherboard. I bought a used one off eBay, and installed it yesterday. Phone is running so much better, no more crashes, and proximity sensor is working properly again.
If you want to give LOS 17.1 a shot, here's a good place to start: https://forum.xda-developers.com/oneplus-6t/how-to/guide-installing-lineage-t4075955
I found it mostly a frustrating ROM, as fingerprint and face unlock don't work. Call me lame, but I absolutely love picking my phone up, looking at it, and having access immediately. Then there's all the apps that hook into the fingerprint for quickly unlocking that you can no longer leverage (the unlock part, not the app). Anyway, up to you.
Since I upgraded my op to 10.3.2, my proximity sensor IS not working.