I bought an S9+ on launch day long story short it lasted 2 weeks before it would just shut down itself anytime you put it to sleep (screen off). I figured out after doing some tests and research that it would only do it when the fingerprint scanner was turned on. I sent it to Samsung which if anyone has had the pleasure of dealing with their customer service knows it's a nightmare to say the least. At least 2 week turnaround time but in the end they did come through and send me a brand new in box s9+.
Fast forward about a month later the new one is doing the EXACT same thing. If I turn the fingerprint scanner off and just use facial unlock it works fine. I really don't want to go through their customer service again and be without a phone for 2 weeks. I think this very well could be a software issue though factory reset does not solve the issue neither does erasing fingerprint and re entering them.
Has anyone else experienced this? I saw searching google that it is actually an issue others have had and like me, their replacements have all done the same thing. I am yet to find a thread with a solution though. What do you guys think? I'm actually wondering if perhaps rooting it and putting a custom rom on it would help.
Honestly, I have not heard of this before. After you try with fingerprint can you turn the device on at all?
Do you have any apps that may in the background that captures button inputs or fingerprint apps that capture slide movements or anything?
Scott said:
Honestly, I have not heard of this before. After you try with fingerprint can you turn the device on at all?
Do you have any apps that may in the background that captures button inputs or fingerprint apps that capture slide movements or anything?
Click to expand...
Click to collapse
Nope it seems to go off within seconds with the fingerprint scanner enabled. Even if I try to wake it up with the power button it seems to be dead. I've had the phone for about a month now and haven't recently added any new apps. I don't believe I have any apps that would be capturing anything. Is there any app I could use to check and see if perhaps I have something app related thats causing this?
I do believe it's gotta be software related.
You can type *#0*# in the dialer, then go to sensor and scroll down to find fingerprint test
Related
Hello guys,
Its my first post here, and my first android phone, and already i have a annoying problem.
I have searched these forums and many others but didnt find any similar problem or solution for it so here it is:
I bought Samsung Galaxy S2 15 days ago, from the local mobile service provider with contract. It runs OS Gingerbread 2.3.3 (adjusted to my mobile service provider settings), not rooted, under warranty.
Ive downloaded and installed many apps. Among them some free games from android market - demos, lite, free.
Sometimes, while i play, not often, game freezes. When it does only thing that is lest working is sound, and home button. Than i go to home screen, kill the game via android task manager, and than i see that screen auto rotation isnt working. Its stuck in landscape mode mostly, or portrait, even the auto rotation option is on. If it is in landscape mode, when i uncheck auto rotation then it goes to portrait mode. If i try some other game that supports sensor controls, like driving (accelerometer?).... u know...... when u tilt the phone to turn right or left......... and its not working.
Ive discovered 2 possible temporary solutions for the problem:
1. Turn off and on the phone, and its back to normal;
2. Wait for a 10 min or so, and its back to normal by itself;
I have one year warranty and i took the phone to service where they assumed that it is a software problem and flashed OS (ive recorded the behaviour of the phone with camera and showed to the service guy).
Ive got the phone back after a day with flashed OS. On a fresh instal of OS ive installed just one app, one game that it tends to freeze and cause problem - "Cordy" free trial. After just 20 sec of playing problem occurred again. It happened just that one time in last two days.
Any opinion on this matter is most welcome.
Tnx in advance.
If the phone is stuck then Restarting it is the option, not a temporary one. Now what's causing the freeze? I don't know.
Regards.
Tnx for answering. Im a bit disappointed with lack of answers because it just saying that my problem is not something common and with easy solution.
Im saying that restarting the phone is a temporary solution because i want find one that will prevent the problem for happening at all. Game freeze and accelerometer not working r connected in this case
It happened just now.
After that I checked in the app called sensor test that i instaled ffrom android market, and also that testing menu typing *#0*#.
in both cases it shows that acceleration sensor is not working. It came to normal by itself after 5 min or so.
What do u think? Software or hardware problem?
OK, update.
Its not caused just by the games, it happens even when not using any apps.
Accelerometer, orientation sensor and magnetic field sensor just stop working for a 5-10 min. Dont know whats causing this.
Tommorow is going back to service and im afraid that guys there r clueless.
Anyone have some suggestion pls.
Update on a problem.
My friend bought same phone from same service provider 3 days after i did and he is having exactly same problem.
He didnt had time before to test it but we did it yesterday, and after a hour of so trying to reproduce problem we succeded.
My phone is at service and i called today and the service guy said that the work on my phone is completed, they replaced sensors part (which apparanty comes with touch screen).
Im picking it up tommorow and i will test it and see if the problem is solved. But, im pesimistic.
How likely is that me and my friend have same hardware problem?
Here it is on video. Pls watch it and give any kind of oppinion, im getting desperate.
www.youtube.com/watch?v=Vym3cRHFjuw
Ok so I want to convey all the relevant information without this being a mile long.
I have a o2 UK SGS2 running on a 3 sim. I have flashed on Lite'ing 6.1 with ninphetmaine 2.0.5. Up until the following, everything has been 100%.
This morning I downloaded Destinia and played it for a while. Before quitting I took a quick look at in app purchases to see if they charge ridiculous prices (they do). I'm not interested so I quickly spam back to close everything. This is when **** ****s up. OS becomes unresponsive immediately and I have no choice but to pull the battery. (power menu disappears instantly, no registered actions from soft keys or menu button in OS). No change on reboot.
I try reflashing Lite'ning. Mostly no change but I got the chance to get into task manager and uninstall Destinia/Launcher Pro.
I reinstall launcher pro, and now it works most of the time except:
1. Quite frequently the voice action app will load itself, and the unlock notification will pop up.
2. MTP notification will appear occasionally and phone will act like it's plugged in
3. Random Launcher/OS crashes. Sometimes screen on but no response from apps or OS. Sometimes screen won't turn on at all, just softkeys and darkness.
4. at first unlock after boot, camera makes standard focusing sound.
5. on boot, little popup dialog will read "in app purchases not supported in this version of android".
Really I doubt there's going to be any solution other than "wipe and reflash" but I'm really interested if anyone knows what would cause all these problems.
Cheers
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
JJEgan said:
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
Click to expand...
Click to collapse
what this means is that pressed back from the game's in app purchases screen, back to the main menu and then back to the Launcher, I'm sure everyone has done basically this countless times.
Fine but my dictionary defines spam as a different meaning .
But as posted that's where it all went wrong for whatever reason .
jje
Right I wipe-flashed stock 2.3.5 and it's STILL doing this. Voice actions popping up at random, all sorts of apps crashing and hanging all the time.
This has to be a hardware problem now, right?
just a stab in the dark but run a virus check.
I've never had a virus in my life, but I checked anyway and nothing.
Right so I've been watching my phone today. It's still doing random voice action popups. If I leave the phone on standard standby it will be fine for a while. It will then randomly turn on the screen by itself. The screen will stay on, if i leave it long enough the whole thing become totally unresponsive. If I press power the phone will wait a few seconds, then restart. If I don't touch it, it will just restart on its own eventually.
Can anyone recommend at least, some logging software that will let me look at the underlying OS and see what's happening when this is going on.
Is there any possibility your phone also goes to car-mode by itself?
spare parts app??
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Im getting random voice talk and mtp etc. phone is all ovr the place. flashed litening and nimphet last week and seemed fine. used mhl hdmi cable and problems seemed to start from there.
millia90 said:
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Click to expand...
Click to collapse
Read your thread http://forum.xda-developers.com/showthread.php?t=1278790 and your problems are down to the letter the same. I've resigned myself to it being a hardware fault and put in a service request with samsung. Wish I had better news.
Yea me too. My issue is that my SGSII was manufactured in UK so I'm at odds seeing as how I'm in America. The people at the Samsung call center referred me to the UK number so I guess I will have to bits the bullet.
Hi, I would know if you have this issue too.
My fingerprint sensor works well, no problem about the speed or recognition.
But, often, it just wont work, I mean there is the vibration but it wont unlock the phone, at the bottom there is: can not use the fingerprint (I don't know in english it's in french).
I have to unlock with my code or layout. I lock again and now it works!
It works for a moment, and maybe one hour later it doesn't work again I have to unlock manually to make it work again.
Try removing and re-adding your fingerprint, make sure you scan all parts of your finger.
It is not recognising your finger as often as it should.
I have a same problem. If I turn off/restart my phone the fingerprint stop working. I must re-adding or again restart the phone to start work again. But if working, he work good until next restart. Sometimes after turn off/restart he continues to work. I think it has its own opinion when to work and when not
When I say there is an issue, it's not about the recognition.
When it doesn't, the screen don't turn on and double vibration, it's ok.
But sometimes, the screen turn on, and just say that is not possible to use fingerprint (with one vibration)
I just deleted and set again my fingerprint, and the problem is still here.
So it recognize my fingerprint (screen on and one vibration) but doesn't want to unlock, just say it's not possible to use fingerprint..
This happens to me only first time after reboot.
I think that's a security, and a will from LG. So it's not a bug, it's a feature
RealLordK1 said:
This happens to me only first time after reboot.
I think that's a security, and a will from LG. So it's not a bug, it's a feature
Click to expand...
Click to collapse
yes I think that happen when the state change, like wifi, BT or other.
But it's annoying when it happens 20 times per day.
I hope I'll be able to change that with root..
anych said:
I have a same problem. If I turn off/restart my phone the fingerprint stop working. I must re-adding or again restart the phone to start work again. But if working, he work good until next restart. Sometimes after turn off/restart he continues to work. I think it has its own opinion when to work and when not
Click to expand...
Click to collapse
As others have said. I think it's a security feature that makes you use the lock code after a reboot. My G5 does the same things as well as my iPhone 5S.
As for the fingerprint scanner misfiring. I noticed that while I'm using the always on display. When I first take the phone out of my pocket. It takes a second for the always on display to pop up. It seems like the fingerprint won't read my print until that display pops on.
You're issue sounds a little different. I'd just figure I'd mention some of my findings.
I just want to remember that my issue is not about a reset. But all day long.
So at this moment I'm the only one who have this issue.
(I also have the 10c update and issue still here)
Thanks for your replys anyway.
I get it about 2 or 3 times a week & like you, not after a reboot. It works again after pin entry.
Strange but infrequent enough not to bother me.
Sent from my LG-H850 using Tapatalk
If in future you actually face any fingerprint sensor issue then this link would help you:
http://recomhub.com/blog/lg-g5-fingerprint-sensor-not-working/
Anyone else experiencing lag on their g5 mine continually struggles to wake sometime needing a good thirty seconds to spring to life?
Also the you tube app continually stutters and freezes up the phone whether connected to fibre broadband or 4g?
jonny_blagwind said:
Anyone else experiencing lag on their g5 mine continually struggles to wake sometime needing a good thirty seconds to spring to life?
Also the you tube app continually stutters and freezes up the phone whether connected to fibre broadband or 4g?
Click to expand...
Click to collapse
Yes, I actually made a solution for it in the Questions forum, but nobody else seemed to have the issue or care. I found that the wake lag occurs when you try to wake too soon after locking.
I found a very strange solution, but it works: Everytime your phone turns on from being off, you must change your lockscreen wallpaper. This can be to anything. You can even set the same one again. This process has to be repeated at every boot, but it completely solved the issue on my Verizon G5.
To test it out, just lock your screen and double tap to unlock immediately. Shouldn't be lag.
ryanpm40 said:
Yes, I actually made a solution for it in the Questions forum, but nobody else seemed to have the issue or care. I found that the wake lag occurs when you try to wake too soon after locking.
I found a very strange solution, but it works: Everytime your phone turns on from being off, you must change your lockscreen wallpaper. This can be to anything. You can even set the same one again. This process has to be repeated at every boot, but it completely solved the issue on my Verizon G5.
To test it out, just lock your screen and double tap to unlock immediately. Shouldn't be lag.
Click to expand...
Click to collapse
Have you also had the problem with the you tube app? I'm Also finding a lot of other apps crash resulting in an error report and restart of the app?
jonny_blagwind said:
Have you also had the problem with the you tube app? I'm Also finding a lot of other apps crash resulting in an error report and restart of the app?
Click to expand...
Click to collapse
No I haven't, sorry! You may need a factory reset or could have downloaded a bad app, not totally sure.
Hi,
sorry for posting here without being a developer myself. It seems like nobody on the other boards knows enough about android to be able to help me with this particular problem - which is the most strangest problem with electronic devices I have experienced so far:
The tends to "loose" sensors after a while. This mostly happens when in sleep mode, but can also happen during charging, sometimes after half a day, sometimes after a few seconds. The following sensors are affected: Accelerometer (including auto rotation), light, magnetic field, orientation and GPS. The sound and battery sensors keep going.
Now, while this is very annoying, it is not really strange. The strange part is the following: Two times I thought to have found the problem and get it back working normally, only to learn better 2 days later:
1) when I uninstalled the Dolphin browser - which never really worked on this device - the problem disappeared for more than a day and I thought it solved. Alas, it returned about two days later. So, Dolphin may have been a cause, but something new jumped into its place after 2 days.
2) at some point, I decided to uninstall Smart Launcher 3, which I had installed right at the start. E voilà: problem gone, the sensors worked perfectly without a single glitch for 2 days. So Smart Launcher must have been the culprit, right? -> wrong! Two days later the problem reappeared, worse than ever! All it takes now is putting the tablet to sleep for ~ 1 minute and the sensors are gone. If I want to use the sensors, I have to either prevent the sleep mode or restart the tablet whenever I want to use it.
So far, I haven't found another solution to make it work for 2 days (or even longer than a couple of minutes). But anyway, it doesn't make any sense. Why would uninstalling an app make the problem disappear, but only for 2 days? Then the same story again, when uninstalling another app?
Any kind of hint or suggestion is greatly appreciated, I am desperate and have no more ideas what else to try. All pleasure in the device is gone, it's just frustrating.
Thank you a 7'200 times (seconds in 2 hours)!
- spitfire
It just got more weird. I figured out, that enabling the power save mode caused the tablet to work somewhat normally, meaning sensors would still work after sleeping most of the time.
But guess what: 3 days later even that workaround doesn't work anymore. Restarting the tablet brings the sensors back, but switching the screen off (sleep mode) for 5 seconds is enough to disrupt them, always. This doesn't make any sense at all. Why does the device always find a way to counteract my workarounds after 2-3 days? Is the thing alive and doing it on purpose? It starts to drive me really mad :crying:
Please, does anybody have an idea? I am looking for
ways to restart the sensors without having to reboot the tablet. There must be some service to kill and restart, right?
ways to identify the cause of the problem. There must be some kind of event log where the sensor crash and what happened before is recorded.
I am sure somebody must know about those things, at least in this forum. Otherwise I don't know what to do, I run out of workarounds, the evil device wins this battle and will soon target the world - welcome Skynet.
Thanks very much for any kind of help
Pesche
edit: I noticed that when the problem occurs, it takes the tablet longer to wake up than the few times when everything is fine. This indicates that there is something going wrong with the wake up process. It must be possible to see in some kind of log what exactly happens, but my sparse knowledge of android isn't deep enough. I already tried OS monitor to access the catlog and I do see some warnings (pink W), but they don't tell me much. E.g.: OpenGLRenderer: Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without. Or: Syste: ClassLoader referenced unknown path: /mnt/expand/.../com.eolwral.osmonitor... (which rather sounds like a problem of OS monitor itself than a problem of the system).
i installed termux... ran top... i see a /system/vendor/bin/sensorhubd
i assume thats the process not "waking up"
is there a way to monitor that? or to tell it to restart? so we dont have to reboot everytime.............
isak.sr said:
i installed termux... ran top... i see a /system/vendor/bin/sensorhubd
i assume thats the process not "waking up"
is there a way to monitor that? or to tell it to restart? so we dont have to reboot everytime.............
Click to expand...
Click to collapse
I think i found whats killing it: google play services... disable body sensors permission in settings-->apps-->google play services-->permissions--> body sensors
also uninstall mcafee.