Database Users

phantom button press causing screenshot

I've had this issue since the update to ED01 (or maybe before, I can't remember). Anyway it's darn annoying. I froze the screenshot apk to keep the screenshots from happening but there is still the issue with random back/return button presses. Sometimes it's the home key. Sometimes the search key will long-press and cause voice search to come up. It's mostly the return/back key.
I've had this problem on two Fascinates (the modem died on my first one and was replaced about a month ago). It happened with ED05 and it is now happening (although less frequently) with PWGB EH09 ROM v2.0b3 running ED05 modem. My daughters fascinate was having the same problem on stock ED05.
I've searched through several forums and it seems that lots of people have the same or similar symptoms with the fascinate/captivate as well as with the Nexus S.
I see that google tracked it as a problem earlier in the year and claimed to be working the issue and had a fix that was supposed to be rolled out. Never happened.
I think I've narrowed it down to only happening when the phone is using 3G data.
I'd like to locate and fix the problem but I could use some help getting started. For starters, I'd like to get a development environment set up and running so that I can build and test kernels. I can do this on my own but if someone could guide me so that I don't have to go through that learning curve, it would be appreciated.
My first thought is that it's a driver issue. In the source code there's a folder under src/kernel/drivers named "input" that has a bunch of drivers. Does anyone know which driver is used for this phone?
Thanks,
Dale
UPDATE: 15 Mar 2012:
I added a 100pf capacitor to the interrupt line on the cypress touchkey chip today. Everything works fine now. dmesg shows that I'm no longer getting any false interrupts. I downloaded a 6meg file over 3G and had zero false interrupts. Without the cap there would have been at least a couple of hundred (I use dmesg to check for false interrupts since I have printk statements in my code). I'll keep testing but I think this is it. I'll try to get some pics of the tack on showing where I added the cap. It's some tiny sh-t to work on. I had to do the soldering under a microscope. It was not easy. The cap I put on is a 100pf 50v X7R I bought from Digikey. Digikey part number 445-6856-1-ND. I got a 100 of them for <$6 with shipping.
I'll go back to the driver and remove the software fixes to see if the hardware fix takes care of the problem completely.
The parts are $0.028 each if you buy a hundred. They're less than a penny if you buy thousands. Seems a shame that Samsung couldn't pony up an extra penny to keep this problem from happening in the first place.
For those of you who don't want to crack your phone open, there's still the software (read: duct tape) fix.
Here's a link to the thread showing the hardware mod http://forum.xda-developers.com/showthread.php?p=23725671#post23725671

Yeah a lot of people have tried to fix this but nothing has ever worked. It's a well-known issue.

sageDieu said:
Yeah a lot of people have tried to fix this but nothing has ever worked. It's a well-known issue.
Click to expand...
Click to collapse
Yeah, that's why I'd like to try to fix the problem. Not to dismiss the skills of the other people who have tried, but I'm pretty good at finding bugs in hardware.

Well more power to ya, if you fix it then you will make a LOT of people very happy. You should absolutely get in contact with some developers of kernels (jt1134, sixstringsg, Tk-Glitch, sswek2, etc) if you have any ideas or get anything fixed. I'm sure they will be glad to help you out with the issue and use any of your changes in their kernels.

i have a SGS I9000. my problem is phantom presses of menu and back button. tried flashing to stock firmware etr (original was xeu). installed ics. all with no result. FINALLY found that it occurs only when using packet data (edge) we dont have 3g yet. i ve tried disabling packet data and using wi-fi and there is no preblem.
the diagnosis finally comes to this - problem related with packet data and may be (most probably be) related to software bug in the touch button firmware.

It only seems to happen to me at my house, which is in a low signal area. I'm betting it is buried somewhere in the tower switching code, as my phone switches towers constantly at home.
Sent from my SCH-I500

Yes the problem only seems to occur for me when on 3g and not wifi. I've verified this with the three other fascinates in my house. I'm digging through the interrupt routines now using the kgb kernel source.
Does anyone know which interrupt line on the processor the cypress touchkey device is connected to?
I'm almost ready to break open the phone and start probing with an o'scope.

electric bill said:
Yes the problem only seems to occur for me when on 3g and not wifi. I've verified this with the three other fascinates in my house. I'm digging through the interrupt routines now using the kgb kernel source.
Does anyone know which interrupt line on the processor the cypress touchkey device is connected to?
I'm almost ready to break open the phone and start probing with an o'scope.
Click to expand...
Click to collapse
Hey Bill (I'm also a Bill, heh) :
You'll probably want to check out the changes I did for the V13.1 Glitch kernel. They seem to have at least severely limited the phantom keypresses. I did find some GPIO pins that were configured differently by the dpram driver and the mach-aries.c gpio (and gpio while sleeping) settings, and making those match up seemed to help a lot.
I'm an embedded guy, but more on the software side. I don't particularly want to tear my phone apart and hit it with a scope, but hey .. if you do that and find anything, go for it!
FYI, I was able to determine that the IRQ number used for the cypress-touchkey driver, and the one that's firing during the phantom key events, is IRQ 334 (0x14E). Without having a schematic to look at, though, I wasn't able to figure out what might be causing it to fire, nor even begin to guess why it has something to do with poor signal strength.
Anyway .. I've been beating my head against this problem for a long time .. so if there's anything else you'd like to pick my brain about, let me know.

Downgrade
I have found that the only thing that works is to downgrade. I am however through uscellular so my phone is the mesmerize. I tried talking to a representative about my problem but all they would say is to upgrade. After multiple tries and different methods I downgraded to DI14 from EH09 and I have not had one problem since. Besides one with random menu flashes but it turned out to be the application Zedge. Hope this helps. If not at least I can say I tried.

ssewk2x said:
Hey Bill (I'm also a Bill, heh) :
You'll probably want to check out the changes I did for the V13.1 Glitch kernel. They seem to have at least severely limited the phantom keypresses. I did find some GPIO pins that were configured differently by the dpram driver and the mach-aries.c gpio (and gpio while sleeping) settings, and making those match up seemed to help a lot.
I'm an embedded guy, but more on the software side. I don't particularly want to tear my phone apart and hit it with a scope, but hey .. if you do that and find anything, go for it!
FYI, I was able to determine that the IRQ number used for the cypress-touchkey driver, and the one that's firing during the phantom key events, is IRQ 334 (0x14E). Without having a schematic to look at, though, I wasn't able to figure out what might be causing it to fire, nor even begin to guess why it has something to do with poor signal strength.
Anyway .. I've been beating my head against this problem for a long time .. so if there's anything else you'd like to pick my brain about, let me know.
Click to expand...
Click to collapse
What? _I_ found out that it is interrupt 334! )
Sent from my SCH-I500 using Tapatalk

electric bill said:
What? _I_ found out that it is interrupt 334! )
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Yes, yes you did, lol. And you're probably going to end up fixing the whole thing before i get a chance to look at it again, lol.

ssewk2x said:
Yes, yes you did, lol. And you're probably going to end up fixing the whole thing before i get a chance to look at it again, lol.
Click to expand...
Click to collapse
I've been testing the code for about a day. I added the int test to the interrupt handler just now and I'll test for awhile. I'll prob also put it on my daughters phone since she uses hers about 10x what I do.

Excellent. You're welcome to drop by the glitch kernel thread, btw. I've got some folks testing there with good results so far.

Superclean Rom has screenshot removed. Also Geewiz 2.4.2 has a mod to remove the screenshot, just flash this in recovery:
http://db.tt/xERensX3
It happens when you have a low signal. It's was so annoying but no longer have that issue.
Keep me Fascinated.

It's not just the screenshot that's annoying. When using navigation, the phone will keep saying "this will end the navigation" as if the back button keeps getting pressed. Sometimes the menu comes up as well. Really annoying and kind of dangerous to have to keep hitting cancel while driving. Removing the screenshot app will not fix this. I'm really hoping someone finds a true fix for this. Otherwise I'm getting a new phone soon.
Sent from my SCH-I500 using XDA App

SnrSuave said:
It's not just the screenshot that's annoying. When using navigation, the phone will keep saying "this will end the navigation" as if the back button keeps getting pressed. Sometimes the menu comes up as well. Really annoying and kind of dangerous to have to keep hitting cancel while driving. Removing the screenshot app will not fix this. I'm really hoping someone finds a true fix for this. Otherwise I'm getting a new phone soon.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I actually just re-enabled screenshot on my phone. The glitch kernel ( http://forum.xda-developers.com/showthread.php?t=1252871 ) has a fix that they're testing that seems to work pretty good. I'm not sure if it's in their release or just in testing. I think comradesven is putting the code into the kgb kernel too http://forum.xda-developers.com/showthread.php?t=1364912
I've been running my own butchered up kgb kernel for a few days with the fix and it seems to help quite a bit.

electric bill said:
I've had this issue since the update to ED01 (or maybe before, I can't remember). Anyway it's darn annoying. I froze the screenshot apk to keep the screenshots from happening but there is still the issue with random back/return button presses. Sometimes it's the home key. Sometimes the search key will long-press and cause voice search to come up. It's mostly the return/back key.
I've had this problem on two Fascinates (the modem died on my first one and was replaced about a month ago). It happened with ED05 and it is now happening (although less frequently) with PWGB EH09 ROM v2.0b3 running ED05 modem. My daughters fascinate was having the same problem on stock ED05.
I've searched through several forums and it seems that lots of people have the same or similar symptoms with the fascinate/captivate as well as with the Nexus S.
I see that google tracked it as a problem earlier in the year and claimed to be working the issue and had a fix that was supposed to be rolled out. Never happened.
I think I've narrowed it down to only happening when the phone is using 3G data.
I'd like to locate and fix the problem but I could use some help getting started. For starters, I'd like to get a development environment set up and running so that I can build and test kernels. I can do this on my own but if someone could guide me so that I don't have to go through that learning curve, it would be appreciated.
My first thought is that it's a driver issue. In the source code there's a folder under src/kernel/drivers named "input" that has a bunch of drivers. Does anyone know which driver is used for this phone?
Thanks,
Dale
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
I had the same problem...I went to big red and exchanged my phone...well they actually sent me a refurb... this was last week

electric bill said:
I actually just re-enabled screenshot on my phone. The glitch kernel ( http://forum.xda-developers.com/showthread.php?t=1252871 ) has a fix that they're testing that seems to work pretty good. I'm not sure if it's in their release or just in testing. I think comradesven is putting the code into the kgb kernel too http://forum.xda-developers.com/showthread.php?t=1364912
I've been running my own butchered up kgb kernel for a few days with the fix and it seems to help quite a bit.
Click to expand...
Click to collapse
Thanks all u guys. I 'd really appreciate if u could find a standalone fix for this issue i.e. no modded kernel only the touchkey fix. Thanks again.

th3b3 said:
Sent from my SCH-I500 using XDA App
I had the same problem...I went to big red and exchanged my phone...well they actually sent me a refurb... this was last week
Click to expand...
Click to collapse
yeah, I'm on my third phone. there's been some speculation that phones built early (ie when they just started making them) don't have the problem. the data code on mine is 08/05/2011.

dff_jx said:
Thanks all u guys. I 'd really appreciate if u could find a standalone fix for this issue i.e. no modded kernel only the touchkey fix. Thanks again.
Click to expand...
Click to collapse
technically if we change the driver code, which is in the kernel then it's been modded...
If you want to run fully stock ROM and see this problem go away then I think you can add a 120pf cap from the interrupt pin on the cypress chip to ground. I haven't tried it yet but I'm going to as soon as I get done testing the s/w fixes.

[Q] Random Reboots?

Hello everyone, my Nexus 7 (32gb Wi-Fi Model) has been randomly rebooting itself. I have unlocked the boot loader on it, but I have not installed any custom ROMs yet. I've mainly noticed it rebooting when I'm watching YouTube or using Google Chrome. Any idea on how to fix it? Thanks.

Just a test.

same here...
you know...
i would watch youtube, then put it down to go somewhere, when i come back to turn on screen ,
Quick tap of power button, no response... well not reboot but, shut down,
Im guessing it takes time from going back from deep sleep and i have no patience, or when i turn off the screen i push it a little bit too long...
Yours reboot?, like just WOah , rebooting device kind of thing...
unstable? overclocked?

Best app to help figure this out. Go into the options and check the top 3.LINK

Might be a shot in the dark but I had experienced reboots that was caused by HD Widgets (was acknowledged by them) and possibly Beautiful Widgets. uninstalling them cured my nexus 7 rebooting syndrome.

gokart2 said:
Best app to help figure this out. Go into the options and check the top 3.LINK
Click to expand...
Click to collapse
Currently giving this app a try. Hopefully this will shed some light on the situation. Thanks.

Jomari29 said:
same here...
you know...
i would watch youtube, then put it down to go somewhere, when i come back to turn on screen ,
Quick tap of power button, no response... well not reboot but, shut down,
Im guessing it takes time from going back from deep sleep and i have no patience, or when i turn off the screen i push it a little bit too long...
Yours reboot?, like just WOah , rebooting device kind of thing...
unstable? overclocked?
Click to expand...
Click to collapse
On my new 1 week old stock Nexus 7 32GB I've had a few random reboots too. Been reading around and trouble-shooting diagnosing the cause for it the past few days and my findings after viewing my debug log traces shows that the OS will reboot when it encounters a null pointer or invalid argument to a function call (or method call for you java programmers). When this error happens due to what seems to be any old app that was not developed for the new Android v4.2.x OS then the system will reboot itself to clear itself up. Ideally the new OS should be catching (detecting) when this invalid null argument or pointer situation occurs and gracefully clean up and terminate the offending app and the OS should just continue staying alive going along its merry way. But Google's new OS methods are not catching these sorts of errors it seems and thus the error is passed all the way up the chain of command to the main OS critical error handler which forces a reset and reboot. That's what is causing it. The solution I believe for now is to find all the old apps that you loaded onto the new device and by process of elimination remove them all. They are not 100% compatible to run on the new OS as of yet. Also report it to the app developer so that they can update and recompile their apps to work with the new v4.2.x java libs. That's my take and fix for now until Google developers add the try{} catch{} blocks to the proper places in their new OS implementation and release a new firmware to users.

Infobits said:
On my new 1 week old stock Nexus 7 32GB I've had a few random reboots too. Been reading around and trouble-shooting diagnosing the cause for it the past few days and my findings after viewing my debug log traces shows that the OS will reboot when it encounters a null pointer or invalid argument to a function call (or method call for you java programmers). When this error happens due to what seems to be any old app that was not developed for the new Android v4.2.x OS then the system will reboot itself to clear itself up. Ideally the new OS should be catching (detecting) when this invalid null argument or pointer situation occurs and gracefully clean up and terminate the offending app and the OS should just continue staying alive going along its merry way. But Google's new OS methods are not catching these sorts of errors it seems and thus the error is passed all the way up the chain of command to the main OS critical error handler which forces a reset and reboot. That's what is causing it. The solution I believe for now is to find all the old apps that you loaded onto the new device and by process of elimination remove them all. They are not 100% compatible to run on the new OS as of yet. Also report it to the app developer so that they can update and recompile their apps to work with the new v4.2.x java libs. That's my take and fix for now until Google developers add the try{} catch{} blocks to the proper places in their new OS implementation and release a new firmware to users.
Click to expand...
Click to collapse
Awesome! Thanks for the tip! I spent the last week slowly removing apps and re-installing them and I think I've solved the problem.

[Xiaomi-MI2][ROM][JB][4.3] CyanogenMod 10.2

Ok, say goodbye to xiaomi - you have a Google Nexus device now!!
Well, CM10.2 is nice but that's not all this is about.
I've build this with the aim to have max compatibility with Nexus 4 sources and that really was a success.
I'm using device repository, kernel source and 90% of the proprietaries from Nexus 4.
What does that mean to the Users?
You have maximum stability, security and speed and you'll get the latest Android versions at least as long as Google supports the Nexus 4.
What does that mean to the Developers?
Google did a very good job with the code style of the device. It's clean and easy to understand.
The changes that we need for MI2 are that minimal that we should be able to port any Nexus 4 ROM or kernel within hours.
Messages to xiaomi:
1) IN YOUR FACE!!
2) Your hardware is great but if you want a quality product you should talk with your software developers about their code style.
It's NOT ok to replace drivers with old versions to "fix" them.
And it's also not good to keep tons of old useless stuff inside the code which is bad for performance.
And please stop giving proprietary binaries root permissions for no reason!!!
Back to topic:
Issues:
1) http://miuiandroid.com/community/threads/dev-opensource-kernel.19934/ (everything should work except MHL and cameras)
2) on Android side everything is working except FMRadio.
Installation:
Just flash the zip via CWM
Downloads:
CM-10.2: http://d-h.st/users/M1cha/?fld_id=24416#files
Google Apps: http://goo.im/gapps
Sourcecode:
Device-Tree: https://github.com/M1cha/android_device_xiaomi_aries
Proprietaries: https://github.com/M1cha/proprietary_vendor_xiaomi
Kernel: https://github.com/M1cha/android_kernel_xiaomi_aries
Quote from CM team which apply's to my work, too:
"If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't meant Out-of-Respect!!!"
Donations:
Changelog:
Code:
[COLOR=#141414][FONT=Georgia]2013-10-22:[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- update to 4.3.1[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- switch to new CM kernel[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- fix earpiece poweron delay[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- massive cleanup and rewrite[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- fix typo in Italia operator name[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- fix setting cpu frequency in power menu[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- maybe more :P[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia] [/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]2013-09-30:[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- updates from cm10.2 for mako[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- use CM libril[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- fix headset buttons[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia] [/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]2013-09-22:[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- use cm-10.2 audio HAL[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- fmradio support[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- wlan improvements[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia] [/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]2013-09-15:[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- fixed audio which was temporary broken[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia] [/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]2013-09-14: !!audio broken!![/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- add support for Synaptics RMI4 touchscreen[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- add support for setting vibrator intensity[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- fix vibration patterns(for touch keys and some other things, too)[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia] [/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]2013-09-09:[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- fix boot on MI2S[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- fix transients when turning on screen[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia] [/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]2013-09-08:[/FONT][/COLOR]
[COLOR=#141414][FONT=Georgia]- initial release[/FONT][/COLOR]
We should have a party to celebrate 8 months of hard work ...

Great work !
Does anyone use this device ?
some screenshot about this ROM

More than u would expect
Look at http://xiaomi.eu/community/ for more information.
I've just created this thread because I like xda and I wanted to inform you about development on this device

test ROM
this rom is smooth !
but why no camera app ?

Because the camera is not yet supported kernel side. This will be fixed once xiaomi released their kernel sources(its official already that this will happen)

m11kkaa said:
More than u would expect
Look at http://xiaomi.eu/community/ for more information.
I've just created this thread because I like xda and I wanted to inform you about development on this device
Click to expand...
Click to collapse
yeah.i wish XDA have Xiaomi box coming soon

cvncbn said:
yeah.i wish XDA have Xiaomi box coming soon
Click to expand...
Click to collapse
He he he, What phone do you use bro ?
You have no idea how popular this device is ! & how good the software development support & update release are for this device....
As M11kka said, have a look at that forum once...

Nokia N82 and xiaomi Mi-2

Thanks, M1cha!!!

Micha! Happy to see you after a long time (defy world xD).
Good luck kid!
Enviado desde mi GT-I9300 usando Tapatalk

Impressive work m11kkaa! :good:

like your message to xiaomi :good:
many root permission mean ... more opportunities for them to make a hole....

bullghost said:
like your message to xiaomi :good:
many root permission mean ... more opportunities for them to make a hole....
Click to expand...
Click to collapse
And apps could make use of security holes in the binaries.

m11kkaa said:
And apps could make use of security holes in the binaries.
Click to expand...
Click to collapse
But luckily Mi2 has same hardware as Nexus4 and mi3(intl version) nearly same as mi3.
And xiaomi will start releasing kernel sources soon.
That means that we'll always be able to port some Nexus magic to these phones

https://github.com/MiCode/mi2_kernel
Finally the kernel is opensource. I request a XDA subforum RIGHT NOW.

Great M1cha (linuxx from xiaomi.EU)

Am I the only one who has random wakelock issues with this rom? the latest (10.22) and also previous version had issues with deep sleep... I couldn't determine exactly what caused it using Gsam and similar stuff, only see that it's kernel related..
The latest I experienced is a RILJ (Phone) wakelock upon boot and it stays until I manually kill and restart the Phone process.
Anybody have similar issues?
Any ideas how to find out what causes these wakelocks? (can't see any relevant in "dumpsys power" output, also these battery monitoring application say it's from "Android kernel"
I'd like to use this rom, even with no Camera but these wakelocks are killing me :S

k.geree said:
Am I the only one who has random wakelock issues with this rom? the latest (10.22) and also previous version had issues with deep sleep... I couldn't determine exactly what caused it using Gsam and similar stuff, only see that it's kernel related..
The latest I experienced is a RILJ (Phone) wakelock upon boot and it stays until I manually kill and restart the Phone process.
Anybody have similar issues?
Any ideas how to find out what causes these wakelocks? (can't see any relevant in "dumpsys power" output, also these battery monitoring application say it's from "Android kernel"
I'd like to use this rom, even with no Camera but these wakelocks are killing me :S
Click to expand...
Click to collapse
The deepsleep problems are i2c problems. It kills audio, backlight and touchscreen until reboot.
In latest update I switched to another kernel - which was a mistake because I get random i2c errors, battery lifetime isn't as good and some graphical glitches can happen.
I'll switch back soon(when camera works).
Click to expand...
Click to collapse

great, can't wait it

Veri nice to see Miui sources for Kernel. Hope in short time we can expect stable CM Rom for Mi2s

Porting 4.4.4 to VS985

I am trying to port to LG-VS985. I have successfully compiled and flashed and it boots, but video recording(camera works), auto brightness and accelerometer are not working.
Also, it reports "Baseband: Unknown". But I can call and text and have data.
I am using the device tree from CM modified for OMNI.

Couple of screenshots. I have a logcat I will post also.
Sent from my LG-VS985 using Tapatalk

I don't think anyone on the team is going to waste time with the 4.4 branches unless you have a good reason why absolutely, positively, there is no way to move to 5.1 (I have yet to see this for any device - all devices getting dropped with 5.x in Omni are due to the maintainers disappearing or dropping the device due to lack of time.)

Entropy512 said:
I don't think anyone on the team is going to waste time with the 4.4 branches unless you have a good reason why absolutely, positively, there is no way to move to 5.1 (I have yet to see this for any device - all devices getting dropped with 5.x in Omni are due to the maintainers disappearing or dropping the device due to lack of time.)
Click to expand...
Click to collapse
I just need a point in the right direction on why they are not loading.

Chevelle1768 said:
I just need a point in the right direction on why they are not loading.
Click to expand...
Click to collapse
Camera is a *****, 3427990734209 different dependencies on qcom devices, and on all devices all sorts of fun interactions with the graphics stack. Almost always the last thing on any device to be brought up. Sensors - not sure, look through logcat.

I think I found the sensor issue, but no clue how to fix it.
Code:
<3>[ 19.312158 / 06-29 14:57:55.300] msm_ipc_router_send_to: permission failure for sensors.qcom
<3>[ 19.312172 / 06-29 14:57:55.300] msm_ipc_router_sendmsg: Send_to failure -1

Chevelle1768 said:
I think I found the sensor issue, but no clue how to fix it.
Code:
<3>[ 19.312158 / 06-29 14:57:55.300] msm_ipc_router_send_to: permission failure for sensors.qcom
<3>[ 19.312172 / 06-29 14:57:55.300] msm_ipc_router_sendmsg: Send_to failure -1
Click to expand...
Click to collapse
hmm... Might be missing irsc_util and there's some sort of sec_config file too IIRC...
https://github.com/DonkeyCoyote/pro...mmit/27d790bf4ac5ebe376040567609bd1a3f8365ac1 and https://github.com/omnirom/android_...mmit/6aa8a009f3e2ed7ce7ff36d404b353783a76a142 for examples from another device is my guess

Fingerprint Option Missing

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.