[Q] Face unlock stops working on EOS Stingray Nightly 40 - Xoom Q&A, Help & Troubleshooting

Hi everyone...
Face unlock is pretty cool... but for me it stops working after a day or so. Running EOS Stingray nightly #40. It has been doing it on every nightly I've played with starting from the mid 20's.
For instance, right now, when I unlock I get a black box and the camera doesn't turn on. Other times I won't get a box at all... that is until I reboot and things work again for a while. I can't tell if perhaps the rotation (going from landscape to portrait) is what's screwing it up, or if its just being buggy.
Anyone else experiencing this symptom?
Thanks
-Mike

always work fine, try a factory reset and latest

liftman- said:
always work fine, try a factory reset and latest
Click to expand...
Click to collapse
Thank you for the advice... I tried that going from 25 to 27 to 30... didn't seem to make any difference.

Vnvjeep said:
Thank you for the advice... I tried that going from 25 to 27 to 30... didn't seem to make any difference.
Click to expand...
Click to collapse
do you have a folder /system/vendor/pittpat

liftman- said:
do you have a folder /system/vendor/pittpat
Click to expand...
Click to collapse
I do... it takes up about 22.57mb. I have 10.6mb free on my system rom partition.

sorry haven't read anyone else with this problem

liftman- said:
sorry haven't read anyone else with this problem
Click to expand...
Click to collapse
What is your Xoom overclocked to? Are you allowing it to switch between portrait and landscape automatically?

Vnvjeep said:
What is your Xoom overclocked to? Are you allowing it to switch between portrait and landscape automatically?
Click to expand...
Click to collapse
1504 and yes on autorotate.
did you open the camera and make sure both work?

liftman- said:
1504 and yes on autorotate.
did you open the camera and make sure both work?
Click to expand...
Click to collapse
I'm running with the same settings. I can open the camera just fine without issue. Going back to the lockscreen,its just a black square... when I reboot, its fine again...

try this.
delete /system/vendor/pittpatt folder
turn off facelock
reboot into recovery.
clear cach and dalvik cach
reflash gaps (should be ver 10.4)
reset up facelock.

liftman- said:
try this.
delete /system/vendor/pittpatt folder
turn off facelock
reboot into recovery.
clear cach and dalvik cach
reflash gaps (should be ver 10.4)
reset up facelock.
Click to expand...
Click to collapse
I like your thinking liftman! Just did it... time will tell. I'll check in later with an update on if it sticks... thanks!

Vnvjeep said:
I like your thinking liftman! Just did it... time will tell. I'll check in later with an update on if it sticks... thanks!
Click to expand...
Click to collapse
.............

liftman- said:
.............
Click to expand...
Click to collapse
Nope. :-( It worked all last night. Took it off the charger this morning and I don't even get a black box. When I unlock it, I get a message that says "unfortunately face unlock has stopped" or something like that. Ughh. Good try. :-(

Related

CWM Recovery feature "Fix Permissions"

Not sure if many of you know this but there is a feature in CWMR called fix permissions. This is a handy feature to use if you're getting FC's that can't be cleared by going to /settings/applications/manage applications/name of app/clear data.
For examply, I just did a restore of RebelROM and the first time I went to open ICS Camera I got a FC. Cleared data, restarted the app, FC. So I booted into CWMR and fixed permissions and upon reboot the camera now works fine. Just a heads up for those who aren't familiar with this feature.
916x10 said:
Not sure if many of you know this but there is a feature in CWMR called fix permissions. This is a handy feature to use if you're getting FC's that can't be cleared by going to /settings/applications/manage applications/name of app/clear data.
For examply, I just did a restore of RebelROM and the first time I went to open ICS Camera I got a FC. Cleared data, restarted the app, FC. So I booted into CWMR and fixed permissions and upon reboot the camera now works fine. Just a heads up for those who aren't familiar with this feature.
Click to expand...
Click to collapse
What's an "FC"?
I tried the "Fix Permissions" feature just to see how it worked. It completed after a few minutes and everything seems to be working just as well as it did before.
daihard said:
What's an "FC"?
Click to expand...
Click to collapse
Force close
Sent from my MB865 using XDA
bigTINY779 said:
Force close
Click to expand...
Click to collapse
Ah, got it. Thanks!
daihard said:
I tried the "Fix Permissions" feature just to see how it worked. It completed after a few minutes and everything seems to be working just as well as it did before.
Click to expand...
Click to collapse
If you had no problems before fixing permissions, you won't see anything different. This is only for those having fc issues or other app related issues that arent fixed by more standard means. It's not a guarantee this will fix it either, just another thing to try along the way.
via Atrix 2/VictoryROM/XDA app
running counter
Hi there there is a counter running after the 'done!' message, any idea what is this?
Thanks man! fixed my problem
Gadgetz said:
Not sure if many of you know this but there is a feature in CWMR called fix permissions. This is a handy feature to use if you're getting FC's that can't be cleared by going to /settings/applications/manage applications/name of app/clear data.
For examply, I just did a restore of RebelROM and the first time I went to open ICS Camera I got a FC. Cleared data, restarted the app, FC. So I booted into CWMR and fixed permissions and upon reboot the camera now works fine. Just a heads up for those who aren't familiar with this feature.
Click to expand...
Click to collapse
gibbe2001 said:
Thanks man! fixed my problem
Click to expand...
Click to collapse
You got it!
Sent from my MB865 using XDA App
Just how long does it actually take? because mine has been at it since the past 5 minutes. :S
ryandigweed said:
Just how long does it actually take? because mine has been at it since the past 5 minutes. :S
Click to expand...
Click to collapse
It's taking long?
Mine just got through within like 10 seconds.
LIFE! IT'S WHAT YOU MAKE OUT OF IT!
Lifehacker7 said:
It's taking long?
Mine just got through within like 10 seconds.
LIFE! IT'S WHAT YOU MAKE OUT OF IT!
Click to expand...
Click to collapse
Mine was not 10 seconds but it did get done with 3 or 4 minutes (Galaxy S3 CWM v5.5.0.4). I realized after posting that this was not a thread for my phone, but I thought I'd let you know that it was not instantaneous even on my device (also you can thank Google for sending me to this thread instead of my normal lurking grounds (S3 / Nexus 10)).

Notifications after Root!

I get these annoying pop up notifications about nfc not working and other stuff and certain apps freeze for a sec then start up again. I have the screen shots that i will attach. I used the new method on this site after i got the stock JB update from VZ OTA.
Also, im a noob even though i got this done using VM and a cracked version of windows xp.
Please help!!!
FingerBlastJ said:
I get these annoying pop up notifications about nfc not working and other stuff and certain apps freeze for a sec then start up again. I have the screen shots that i will attach. I used the new method on this site after i got the stock JB update from VZ OTA.
Also, im a noob even though i got this done using VM and a cracked version of windows xp.
Please help!!!
Click to expand...
Click to collapse
I take it you are running a custom recovery? Boot into it and clear your cache and dalvik cache and then fix permissions. Usually force closes are permission issues. If it doesn't fix it maybe a factory reset? If that don't do anything either then just flash the JB rooted image with odin from here
x714x said:
I take it you are running a custom recovery? Boot into it and clear your cache and dalvik cache and then fix permissions. Usually force closes are permission issues. If it doesn't fix it maybe a factory reset? If that don't do anything either then just flash the JB rooted image with odin from here
Click to expand...
Click to collapse
how long does it normally take to fix permissions? its been doing it for 5 mins and it almost seems frozen and this is my 2nd attempt. i took out the battery and tried again. what should i do now?
FingerBlastJ said:
how long does it normally take to fix permissions? its been doing it for 5 mins and it almost seems frozen and this is my 2nd attempt. i took out the battery and tried again. what should i do now?
Click to expand...
Click to collapse
ok now i have a bigger problem, "unfortunately, touchwiz hom has stopped" flashes every5 secs and i cant even use my phone. what do i do?
FingerBlastJ said:
ok now i have a bigger problem, "unfortunately, touchwiz hom has stopped" flashes every5 secs and i cant even use my phone. what do i do?
Click to expand...
Click to collapse
Download that stock rooted JB image I linked to and flash it with odin. If you don't know how to use odin follow step 5 in this guide. Fixing permissions should only take a couple mins tops on a stock rom so something is probably corrupted and causing issues.
x714x said:
Download that stock rooted JB image I linked to and flash it with odin. If you don't know how to use odin follow step 5 in this guide. Fixing permissions should only take a couple mins tops on a stock rom so something is probably corrupted and causing issues.
Click to expand...
Click to collapse
yea i know how to flash with odin, im gonna try it right now with the non wipe version of the latest JB
FingerBlastJ said:
yea i know how to flash with odin, im gonna try it right now with the non wipe version of the latest JB
Click to expand...
Click to collapse
odin isnt allowing me to flash that image, attached is a screen shot
What does the error say? I can't read it that small.
x714x said:
What does the error say? I can't read it that small.
Click to expand...
Click to collapse
it says vmware-host\shared folders\desktop\root files\root66 file ..... then all these special characters that look like boxes
i tried running a different launcher, and they work a lil better but touchwiz is by far superior but i still get the nfc stopped message and everything is much slower
Ya i dont know what what that refers too either, you have a windows computer you can run it on then inside a VM?
x714x said:
Ya i dont know what what that refers too either, you have a windows computer you can run it on then inside a VM?
Click to expand...
Click to collapse
im using a mac so im forced to use windows xp on VM
FingerBlastJ said:
im using a mac so im forced to use windows xp on VM
Click to expand...
Click to collapse
ok i just did a factory reset and i still have the nfc issue along with the com.android.phone issue and i cant get into the mobile networks, any ideas of what i can do?
this thread here says its an nfc fix i just dont know if it will ruin my nfc capabilities
http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367
please help.
Something is corrupt on the system is my guess. Im thinking your only option is to flash the os again.
x714x said:
Something is corrupt on the system is my guess. Im thinking your only option is to flash the os again.
Click to expand...
Click to collapse
by flashing you mean formatting? why would that do anything when it didnt do much the first time?

[Q] Camera error Can't connect to the camera

Title says it all. I have flashed, reflashed, stuck boot, fixed and flash again, flashed 4.2 camera, and nothing is working. Started after installing official CM10 XMas eve nightley.
try to restore or flash an other rom, or in current rom make a full wipe and see what happens
Hi, for CM10, i remeber that was fixed search for camera fix and install it. It will stop that buggy cam
Is there a way to do a hardware analysis?
GRG13 said:
try to restore or flash an other rom, or in current rom make a full wipe and see what happens
Click to expand...
Click to collapse
I have installed several different ROMs, including ICS and JellyBeans, and none work for the camera.
blogodoblogodo said:
Hi, for CM10, i remeber that was fixed search for camera fix and install it. It will stop that buggy cam
Click to expand...
Click to collapse
I tried the 4.2 camera fix already.
BUMP
just bumping this up to see if anybody is any good suggestions.
http://forum.xda-developers.com/showthread.php?p=37072484#post37072484
no operation
Hello,
The camera stopped working.
I did hard reset and nothing worked.
Installed rom (gt-i9500 ROM mkt6589) and also not caught.
I need help
juniorcurtis said:
Hello,
The camera stopped working.
I did hard reset and nothing worked.
Installed rom (gt-i9500 ROM mkt6589) and also not caught.
I need help
Click to expand...
Click to collapse
It is a hardware issue, not a software issue. Mine is with HTC right now for the THIRD time for the camera...... Now they want to charge me $145 to fix it. Needless to say, never again will I have an HTC device.
Same Problem
I have the same problem, did a factory reset, fresh install of CM 10.2 but nothing.
Always getting the "can't access camera" error.
I'm thinking it is indeed a hardware issue unfortunately, but if anyone finds a solution I'm happy!
Pikaman said:
I have the same problem, did a factory reset, fresh install of CM 10.2 but nothing.
Always getting the "can't access camera" error.
I'm thinking it is indeed a hardware issue unfortunately, but if anyone finds a solution I'm happy!
Click to expand...
Click to collapse
did you use a ruu.exe?
rzr86 said:
did you use a ruu.exe?
Click to expand...
Click to collapse
Nope, not yet, will this likely solve the problem?
Pikaman said:
Nope, not yet, will this likely solve the problem?
Click to expand...
Click to collapse
restores everything back to stock
if the issue persists then probably it is a hardware issue
rzr86 said:
restores everything back to stock
if the issue persists then probably it is a hardware issue
Click to expand...
Click to collapse
Thanks for the tip! did an ruu.exe still doesn't wokr so probably a hardware issue
Pikaman said:
Thanks for the tip! did an ruu.exe still doesn't wokr so probably a hardware issue
Click to expand...
Click to collapse
probably

[Q] Display shaking?

Hi, my display seems to shake, seeming on random. The picture will shake up and down and it makes it impossible to type or do anything until it stops. I don't have any Xposed modules installed and i am running Cataclysm rom with Elemental X kernel. It even does does on the recovery menu and when turning on. Any idea what is causing this and possible fix? Thank you.
I attached a picture of the problem.
I would do a factory reset and wipe the dalvik cache and cache.
Use helium to backup your stuff
Well, if it does it even in recovery and at boot, I would think that it's an hardware issue...
mistahseller said:
I would do a factory reset and wipe the dalvik cache and cache.
Use helium to backup your stuff
Click to expand...
Click to collapse
Tried that, no difference. Flash back to stock?
bradt94 said:
Tried that, no difference. Flash back to stock?
Click to expand...
Click to collapse
Have you tried going back to the stock kernel?
Display Shake
bradt94 said:
Hi, my display seems to shake, seeming on random. The picture will shake up and down and it makes it impossible to type or do anything until it stops. I don't have any Xposed modules installed and i am running Cataclysm rom with Elemental X kernel. It even does does on the recovery menu and when turning on. Any idea what is causing this and possible fix? Thank you.
I attached a picture of the problem.
Click to expand...
Click to collapse
I had the same problem last week. It’s a hardware issue. Kindly visit your nearest service center if possible asap.
vanessaem said:
Have you tried going back to the stock kernel?
Click to expand...
Click to collapse
Yes i have, thank you. I'm guessing that due to it happening even on stock that like others have said that it is hardware related so i will give Google a call and hopefully sort out a RMA. Thanks for the help!
joannn said:
I had the same problem last week. It’s a hardware issue. Kindly visit your nearest service center if possible asap.
Click to expand...
Click to collapse
Thanks for the reply, i will try get in touch with Google to ask about a RMA. Thanks!

Wifi unable to reconnect when coming back in range

I have this rather annoying problem with my OPO: When I'm on WiFi and go out of range and get within range of another WiFi (eg leaving from home in the morning and getting on the train where there's also WiFi) my OPO will not connect.
I've tried switching WiFi off and back on, tried forgetting network and connecting again but the network just displays as "Saved". Only thing that works is a reboot. Funny thing is that it actually detects open WiFi's and displays the question mark in the notification bar.
I've read that themes can cause WiFi problems so I haven't changed that. I'm using the Apex launcher with no visual changes.
I've rooted my phone but left the bootloader locked.
Any advice?
I'm rooted with the TWRP custom recovery installed. I had the same thing happen to me. If you toggle airplane mode on/off, it will reconnect. But, as for a solution, my fix was to restore a previous TWRP backup of my phone. I also had heard that the problem could be coming from a theme. What themes have you used? I bought the Flux theme and have been using its style and fonts. I was running the stock CM11s when this happend just a few days after getting my OPO. I would try a factory reset first. If that does not work, there is a thread in the OPO forums about flashing a factory image and getting back to 100% stock.
I have switched to the CM11 nightlies as of a couple of days ago. I will probably refrain from messing around with the theme packs for now.
kevinga said:
If you toggle airplane mode on/off, it will reconnect...
Click to expand...
Click to collapse
Works for me too
kevinga said:
What themes have you used?
Click to expand...
Click to collapse
None as I've read reports about themes causing WiFi problems.
kevinga said:
I would try a factory reset first.
Click to expand...
Click to collapse
Will probably unlock the bootloader. Then a factory reset should be taken care of I guess...
Anyone have a solution to this? My OPO is having this problem too and it is rather annoying...
GoTexan20 said:
Anyone have a solution to this? My OPO is having this problem too and it is rather annoying...
Click to expand...
Click to collapse
Have you taken the OTA update yet?
kevinga said:
Have you taken the OTA update yet?
Click to expand...
Click to collapse
I'm now on KTU84P and the problem is still there
Yesterday I failed to flash MAHDI and ended up clearing everything from my phone. I had to follow this guide:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
to get back to pre-KTU84P (can't remember the build number).
So I guess it's safe to say that my phone has had all sorts of memory cleared. And the problem is still there...
kroogar said:
I'm now on KTU84P and the problem is still there
Yesterday I failed to flash MAHDI and ended up clearing everything from my phone. I had to follow this guide:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
to get back to pre-KTU84P (can't remember the build number).
So I guess it's safe to say that my phone has had all sorts of memory cleared. And the problem is still there...
Click to expand...
Click to collapse
I really hate to hear that you are still having the wifi issue. One would think that if you flashed all partitions with a factory image that it would solve the problem. You might want to have a look at this thread. This guy was unsuccessful in fixing his efs and bluetooth problems until he flashed Color OS and then went back to CM. Have a read: http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Keep us posted.
kevinga said:
Keep us posted.
Click to expand...
Click to collapse
Will have a look at the ColorOS thread. But I think I'll give Mahdi another go first to see what that brings me.
Thanks for the link.
Flashed Mahdir ROM yesterday and though the rom works just fine my WiFi reconnect issue has not been resolved
I find flashing yet another rom (ColorOS) sounds a bit drastic. Really no way of debugging what's wrong?
GoTexan20 said:
Anyone have a solution to this? My OPO is having this problem too and it is rather annoying...
Click to expand...
Click to collapse
Have you been able to fix your wifi problem?
---------- Post added at 06:28 AM ---------- Previous post was at 06:24 AM ----------
kroogar said:
Flashed Mahdir ROM yesterday and though the rom works just fine my WiFi reconnect issue has not been resolved
I find flashing yet another rom (ColorOS) sounds a bit drastic. Really no way of debugging what's wrong?
Click to expand...
Click to collapse
Although is sounds drastic I think it would be worth trying.
kevinga said:
Have you been able to fix your wifi problem?
No. I'm waiting for the update to hit my phone and install it to see if that solves it. In the meantime though, I installed an app called Smart WiFi Locker that seems to keep the issue solved (for now)
Click to expand...
Click to collapse
GoTexan20 said:
kevinga said:
Have you been able to fix your wifi problem?
No. I'm waiting for the update to hit my phone and install it to see if that solves it. In the meantime though, I installed an app called Smart WiFi Locker that seems to keep the issue solved (for now)
Click to expand...
Click to collapse
Thanks for sharing. I think there are two things that can produce a major restore/fix to a phone - a nandroid restore and a major rom update. I hope it fixes yours. The nandroid restore is what saved mine.
Click to expand...
Click to collapse
kevinga said:
Although is sounds drastic I think it would be worth trying.
Click to expand...
Click to collapse
Been there. Done that. Read the book. Got the t-shirt.
Flashed ColorOS.
Factory reset.
Booted and got through into ColorOS (skipped account setup).
Booted into recovery.
Factory reset.
Restore backup of CM11S.
No dice :'-(
What are my options now?
A couple of days ago I completely wiped my OPO - radio, modem, everything and flashed a new stock image. Nothing has helped.
I really find it hard to believe this to be a hardware issue.
GoTexan20 said:
kevinga said:
I installed an app called Smart WiFi Locker that seems to keep the issue solved (for now)
Click to expand...
Click to collapse
Could it be Smart WiFi Toggler?
Click to expand...
Click to collapse
kroogar said:
Been there. Done that. Read the book. Got the t-shirt.
Flashed ColorOS.
Factory reset.
Booted and got through into ColorOS (skipped account setup).
Booted into recovery.
Factory reset.
Restore backup of CM11S.
No dice :'-(
What are my options now?
A couple of days ago I completely wiped my OPO - radio, modem, everything and flashed a new stock image. Nothing has helped.
I really find it hard to believe this to be a hardware issue.
Click to expand...
Click to collapse
Just for clarification - after flashing Color OS, did you turn on wifi and use it to see if the problem was still there while in Color OS?
If your WiFi 2.4 or 5GHZ?
Sent from my A0001 using Tapatalk
kevinga said:
Just for clarification - after flashing Color OS, did you turn on wifi and use it to see if the problem was still there while in Color OS?
Click to expand...
Click to collapse
Eh... nopes - should I have...?
fr4c said:
If your WiFi 2.4 or 5GHZ?
Click to expand...
Click to collapse
My phone is set to auto but I have tried setting it to 2.4 and 5 GHz respectively. Nothing works.
kroogar said:
Eh... nopes - should I have...?
Click to expand...
Click to collapse
Yes. I would recommend you consider doing that. If it works then I would flash a fresh Cm11s rom, not a nandroid backup. Flash the Color OS and do a full check of the Wifi.
Sent from my A0001 using XDA Free mobile app
kroogar said:
My phone is set to auto but I have tried setting it to 2.4 and 5 GHz respectively. Nothing works.
Click to expand...
Click to collapse
I was having the same issue, but here's what I did and it seems to have resolved my issue.
1) Updated firmware on my ASUS AC68 router
2) Boot into recovery mode (volume down+power), wipe cache and media, then factory wipe
3) When setting up phone, did not apply CM theme on the options after logging into CM account.
It seems like WiFi might drop when you get to homescreen, just reboot phone and Wifi should reconnect. Make sure to go into your WiFi settings and remove any networks that was saved, and re-add.
Still not ideal (since it seems like themes might be killing WiFi for some users), so hopefully a new OTA update will solve this problem.

Categories

Resources