Database Develop

[Q] Screen not waking up while on phone call

Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?

hmmm
carlosmeldano said:
Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?
Click to expand...
Click to collapse
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:

really?
madhukarmohan said:
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:
Click to expand...
Click to collapse
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?

yes
carlosmeldano said:
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?
Click to expand...
Click to collapse
Yeah, few r experiencing that. i hv seen complaints in sony blog and here too. I asked this question few days back. but, I didnt get reply.

I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas

thx
UltraWelfare said:
I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas
Click to expand...
Click to collapse
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see

carlosmeldano said:
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see
Click to expand...
Click to collapse
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)

UltraWelfare said:
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)
Click to expand...
Click to collapse
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.

carlosmeldano said:
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.
Click to expand...
Click to collapse
I hope everything goes fine

no success
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...

carlosmeldano said:
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...
Click to expand...
Click to collapse
Bring it to a sony service(or how's it called to your country)

it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.

carlosmeldano said:
it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services are just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.
Click to expand...
Click to collapse
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug

UltraWelfare said:
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug
Click to expand...
Click to collapse
yes, that's another option. the other option is to cry off from purchase (I can do it within a week), they return the money, and I buy another one. I'll see as this is not that disturbing problem and I have no other problems with the phone like wifi bug or anything else.
someone said it's a bug so I hope 4.3 next month will solve it.

6.0.1 Changes for LG G Watch R

So my watch updated last night, and now I am trying to figure out all the changes.
I see that we have new gestures. I don't really use them, so Meh.
I also see that my battery projection jumped from 50 hours to 3 days, so that I freaking awesome if it pans out.
Anyone see anything else?
-Chris

cdaly1970 said:
So my watch updated last night, and now I am trying to figure out all the changes.
I see that we have new gestures. I don't really use them, so Meh.
I also see that my battery projection jumped from 50 hours to 3 days, so that I freaking awesome if it pans out.
Anyone see anything else?
-Chris
Click to expand...
Click to collapse
No more reboot watch.. Have to turn it off and on again.

matejilic said:
No more reboot watch.. Have to turn it off and on again.
Click to expand...
Click to collapse
Yeah I noticed that. Find this odd as to why they removed that

Hawke84 said:
Yeah I noticed that. Find this odd as to why they removed that
Click to expand...
Click to collapse
I think Google's reason was: "Why? Because F**k you, thats why!" It also baffles me that they still haven't incorporated custom canned responses to declined phone calls; you are stuck with the default ones even though you set up custom ones on the phone - the reason was probaby the same as the reboot omisson.

matejilic said:
I think Google's reason was: "Why? Because F**k you, thats why!" It also baffles me that they still haven't incorporated custom canned responses to declined phone calls; you are stuck with the default ones even though you set up custom ones on the phone - the reason was probaby the same as the reboot omisson.
Click to expand...
Click to collapse
but how to make a factory reset now? there is no item in menu.

Hawke84 said:
Yeah I noticed that. Find this odd as to why they removed that
Click to expand...
Click to collapse
Just hold down the button until it buzzes and reboots. Hardware reboot.

shobull.eu said:
but how to make a factory reset now? there is no item in menu.
Click to expand...
Click to collapse
Have you tried 'Unpair with phone'? To me that sounds like it would do a factory reset since an unpaired watch is basically useless.

Big change
Hi all,
Also got marshmallow, and biggest change for me is that it won't pair with phone. It comes up alright, and after accepting the Bluetooth code the phone wear app says "couldn't connect with ...". I tried factory resets (via unpair phone setting item), fresh install of wear phone app, and what not - still no luck.
Will try to downgrade and see if that helps.
Yours,
Christian

Hawkeye3 said:
Have you tried 'Unpair with phone'? To me that sounds like it would do a factory reset since an unpaired watch is basically useless.
Click to expand...
Click to collapse
From what I understand factory reset is "Unpair with phone" now, as when you select it asks: "are you sure you want to unpair and factory reset watch.
Interesting thing, is the new Reminders app, doesn't seem to work it asks to update android wear on phone when I open it, but nothing happens.

cholm said:
Hi all,
Also got marshmallow, and biggest change for me is that it won't pair with phone. It comes up alright, and after accepting the Bluetooth code the phone wear app says "couldn't connect with ...". I tried factory resets (via unpair phone setting item), fresh install of wear phone app, and what not - still no luck.
Will try to downgrade and see if that helps.
Yours,
Christian
Click to expand...
Click to collapse
I replied to you in the other thread but will post here as it may be useful to others..
I have the same issue. After OTA , i factory resetted and now it will not pair. I get "failed to pair...." I have tried multiple resets and cleared the data on the android wear app but no joy. I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.

Downngrade wakes up watch
Hi there,
mhacin said:
I replied to you in the other thread but will post here as it may be useful to others..
...
I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.
Click to expand...
Click to collapse
I also went back to 5.1.1 and things now work again - recovery flash also worked.
Seems the problem is really on the phone end. I have a Nexus 4 with "Fake stock" ROM (marshmellow). I could get the watch to pair with my Nexus 7 running stock 6.0..1 and that paired just fine. I also see other problems with the same Nexus 4 ROM with other bluetooth devices - e.g., my Jabra Tag II bluetooth audio RX/TX. I've posted on the ROM bug report forum.

My watch gives an error about a muted microfone although the mike is enabled everywhere in the settings where possible.
" Microfone disabled, waiting for injected audio."
Any suggestions?
Edit: Also the screen goes off after some time although I haven't enabled it anywhere?
Maybe I'll just reset it...

The biggest change for me - now we have native vibration when the watch disconnects (on connects) ... it was about f'in time ...

cholm said:
I have a Nexus 4 with "Fake stock" ROM (marshmellow).
Click to expand...
Click to collapse
I also have nexus 4 running Chroma MM. I will wait for OTA again and this time I wont factory reset to see how it goes

Manually updated mine to 6.0.1 using adb and now my iPhone (9.3 beta3 and latest android wear app) constantly looses connection. Have to pair as new device, restarting phone and/ or watch won't help.
Does anybody experience the same?
Might have to go back to 5.1.1 ...
Gesendet von iPhone mit Tapatalk

Hmm, well thats a disappointing. The removal of the reboot and reset is moronic and the new gestures are useless.
For the most part I cant get them to work, and even if I could why would I want to look like I was a nutter because I was randomly flapping my arm around trying (usually unsuccessfully) to control my damn watch?

delete me

mhacin said:
I replied to you in the other thread but will post here as it may be useful to others..
I have the same issue. After OTA , i factory resetted and now it will not pair. I get "failed to pair...." I have tried multiple resets and cleared the data on the android wear app but no joy. I have gone back to 5.1.1 using the first post of the factory image thread. I was able to flash boot.img and system.img but recovery.img failed due to a partition error. Now everything is working again. Paired and synced on first attempt.
Click to expand...
Click to collapse
Which 5.1.1 is better?

SharpSA said:
Which 5.1.1 is better?
Click to expand...
Click to collapse
I used the one at the top of the list. I don't know what the differences are between 5.1.1 versions

Speaker phone automatically turning on while receiving call

Hi,
I have started to get this weired issue after the 8.1 update.
Whenever I receive a call, after picking up the speaker phone turns on automatically. I have to manually turn off the speakerphone, also it does not indicate that the speakerphone is turned on.

shashankkp12 said:
Hi,
I have started to get this weired issue after the 8.1 update.
Whenever I receive a call, after picking up the speaker phone turns on automatically. I have to manually turn off the speakerphone, also it does not indicate that the speakerphone is turned on.
Click to expand...
Click to collapse
Solution is mostly the same for all of the problems.
Do full factory reset.
Setup Google account
Don't install any apps just yet.
Try if problem still exists
In most cases this will help.
What I've learned since my first android device, all of the custom ROMs etc, is that the updates are causing loads of problems.
Once in a while, especially after version upgrade, is worth doing full reset just after updating.
This doesn't apply not only to android, but pretty much every single device on the market.

TeddyBeers said:
Solution is mostly the same for all of the problems.
Do full factory reset.
Setup Google account
Don't install any apps just yet.
Try if problem still exists
In most cases this will help.
What I've learned since my first android device, all of the custom ROMs etc, is that the updates are causing loads of problems.
Once in a while, especially after version upgrade, is worth doing full reset just after updating.
This doesn't apply not only to android, but pretty much every single device on the market.
Click to expand...
Click to collapse
Thanks for the suggestion, But by full factory reset do you mean the hard reset from the recovery menu or just the factory reset from settings menu -> factory reset..?

facing same issue please help
i am facign the same issue please help me out

Still no solution for the problem...I have made an habit to turn speaker phone on and off immediately after calling .

Try Macrodroid app to set an automatic task, to turn speaker off 1 or to seconds after receiving call.

I am also facing Same issue, can any one give suggestions

Somehow that happened to me when I just got the phone a few months ago. I think that was still on 8.0.
But tapping the speaker phone button 2 times everytime I have a call became nature for me and eventually after a few days, I no longer have that issue.
Are you still having that speaker phone issue now?

Yes...but while it was consistent on 8.0 it has become a random occurrence after 8.1 update

same issue
factory reset solution is not acceptable.

Nokia 7 Plus - Screen Freeze - Lock and Unlock to make it work

Hi Folks,
I have got a Nokia 7 plus and since the day I have bought it, I am facing a strange problem.
Every now and them the screen freezes and only way to make it work again is locking and unlocking the phone.
I can say the screen do not respond to touch because the buttons are working properly in this case.
Tried resetting the phone, installing Android P, Rolling back to O, but nothing works. the problem still persists.
Curious to know if anyone else is facing such problem or if anyone has got any solution to fix this issue?

It a hardware problem i believe. Coz even i had the same issue. I immediately sent it to service center which was luckily nearby my home. They took a video of that issue and sent it to Nokia for replacement. They approved my replacement and gave me a approval letter and requested me to visit the shop where i had purchased the phone. The shopkeeper took my old phone back along with all the accessories and approval letter and within 5 mins they gave me a new unit.(note: the service center person told me that if you have purchased the phone from a store then you have 14 days replacement guarantee in case if any issues persist post format or tests).

I have the same issue, tried all methods you mention to make it work normally without succes. I dont know if it is a touch hadware problem because it happens very ramdomly and works instantally and normally again if I lock and unlock the screen
Some days not happens, another days happens very frequent.
Another fact, every time I installs some Factory image (Android P developer preview, Android 8.1), the touch not give problem at all for aprox 2 days or more.
I'm very frustrated with this issue.

sid_25 said:
Hi Folks,
I have got a Nokia 7 plus and since the day I have bought it, I am facing a strange problem.
Every now and them the screen freezes and only way to make it work again is locking and unlocking the phone.
I can say the screen do not respond to touch because the buttons are working properly in this case.
Tried resetting the phone, installing Android P, Rolling back to O, but nothing works. the problem still persists.
Curious to know if anyone else is facing such problem or if anyone has got any solution to fix this issue?
Click to expand...
Click to collapse
This is the Nokia 7+ quality problem, go to the after-sales service to replace the screen for free.

So i got my device replaced and for sometime, it did not give the problem but after 3 weeks, i started experiencing the same problem. New device also becomes unresponsive at times and then i have to switch off/on again to use it. I updated OS to Android P DP3 last week but issue still persists.

Tapas87 said:
So i got my device replaced and for sometime, it did not give the problem but after 3 weeks, i started experiencing the same problem. New device also becomes unresponsive at times and then i have to switch off/on again to use it. I updated OS to Android P DP3 last week but issue still persists.
Click to expand...
Click to collapse
I think we can clearly consider this as a hardware problem in that case.

i have same problem with my Nokia 7+, I gave a chance to nokia but I'm already starting to change my mind, the bootloader can not be officially unlocked and now the problem with the touchscreen, a bit disappointed, I hope hmd solve these issues and if not, buh bye nokia.

sid_25 said:
I think we can clearly consider this as a hardware problem in that case.
Click to expand...
Click to collapse
Surprisingly there is no issue now once i updated Nokia 7 plus to Android 9 pie yesterday. No screen freeze or lag at all. Its working smooth now.

Tapas87 said:
Surprisingly there is no issue now once i updated Nokia 7 plus to Android 9 pie yesterday. No screen freeze or lag at all. Its working smooth now.
Click to expand...
Click to collapse
Sadly, this is not the case here. I did a clean install of the latest developer preview, and I still experience an unresponsive system. Right after lock/unlock it works again.
Sent from my Nokia 7 plus using Tapatalk

bvanaerde said:
Sadly, this is not the case here. I did a clean install of the latest developer preview, and I still experience an unresponsive system. Right after lock/unlock it works again.
Click to expand...
Click to collapse
Seriously ur device need a service centre

It happens to me sometimes while uninstalling an app. Device freezes and doesn't respond. After like 10-15 seconds, it uninstalls the app and start responding.

Rowdyy Ronnie said:
It happens to me sometimes while uninstalling an app. Device freezes and doesn't respond. After like 10-15 seconds, it uninstalls the app and start responding.
Click to expand...
Click to collapse
I have similar problem.
When I want to clear data for the chrome through the settings, device goes mad, most of the time freeze and its difficult to restart it.
I thought they fixed with august security patch, but no.
Sent from my Nokia 7 plus using Tapatalk

spaha-bih said:
I have similar problem.
When I want to clear data for the chrome through the settings, device goes mad, most of the time freeze and its difficult to restart it.
I thought they fixed with august security patch, but no.
Click to expand...
Click to collapse
Yes, it happens to me as well. Let say Chrome has 200mb cache and if I click on Clear Cache, device freezes.

I used to face this problem quite frequently, but I haven't seen it in quite a while. For this reason, I'm pretty sure it was a software related issue and not a hardware one, as a hardware problem would be unlikely to go away, but a software one could be fixed with updates.

It started to happen on ly device today. I have the august security patch and my model is ta 1055 so i don't think the problem is solved yet

Cleared chrome cache. Device freeze for 15 minutes and rebooted. On Pie dev 4

There are so many seemingly random issues with this phone, I can safely say that I hate it. I never know if it's going to take a call (unresponsive soft button), or if the person on the other end will be able to hear me (mic just randomly stops working at least once a week). Freezes a few times every day. Won't allow push email notifications after (or during) sleep, have to reboot. The list goes on......

Going to turn in my device for repairs. It's taken Nokia long enough to come up with a software solution. On the Nokia forums there are several people who were helped with a touch panel repair.
Sent from my Nokia 7 plus using Tapatalk

Already sent back the device for repairs twice, each time they sent it back with just a reinstall of an older Android version... claiming it would be fixed.
In Europe, there's no Nokia repair, so another party is taking care of the repairs. It seems like they are not really aware of the ongoing bugs/problems of the device, which makes it extremely difficult to get them to actually repair the device properly.
First time they even told me they "replaced defective hardware", when in fact the hardware was not touched at all.
I managed to record the issue with another device, and showed it to the vendor.
Now they're offering me a refund. It looks like this is the best option I can get from them.
Really sad though. I was hoping for them to just fix it. Apart from this problem, it is a really good device. There's not really a good alternative in the same price range.
Sent from my Nokia 7 plus using Tapatalk

Im having trouble unlocking my device, I tried the finger touch to unlock but it did not unlock and the phone is unresponsive even on pressing the power button. I tried to force restart by pressing and holding the powerup button and power nutton simultaneously but still no result. Also I could see a red led light at the lefthand side of speaker on top.
Note: The device was fully charged.
can someone help me with this Issue please

S10 Random reboot problem.. :crying: hellllllp

hello guys
I have an issue on my S10 and thats just rebooting randomly, even sometimes when im not using it and its standby on the desk.
i search about it and saw someone elese have same problem, so i want to know what is the problem and how to fix it.
i found someone who fixed it with some solution at this topic but that is not my phone model :crying:
i just change my android version to 10 and its not fixed..
i tried home csc and csc files and even tried pit files too..
please hellllp
thanks

Did you try a data factory reset? It might be a hardware issue, I would take it to a local repair shop or contact Samsung on it.

StoneyJSG said:
Did you try a data factory reset? It might be a hardware issue, I would take it to a local repair shop or contact Samsung on it.
Click to expand...
Click to collapse
yes i did and not worked..

Justphemy said:
yes i did and not worked..
Click to expand...
Click to collapse
get the factory firmware from sammobile.com and flash it in Odin. be sure to factory reset from within the settings first or the FRP might crop up. This is the nuclear bomb method that 99% of the time fixes any glitches caused by software. You might have a hardware issue, but this will help rule that out

Youdoofus said:
get the factory firmware from sammobile.com and flash it in Odin. be sure to factory reset from within the settings first or the FRP might crop up. This is the nuclear bomb method that 99% of the time fixes any glitches caused by software. You might have a hardware issue, but this will help rule that out
Click to expand...
Click to collapse
Thanks man i will try it soon, so is it different from that what I did? I tried update to android 10 with odin, with 4 files

Justphemy said:
hello guys
I have an issue on my S10 and thats just rebooting randomly, even sometimes when im not using it and its standby on the desk.
i search about it and saw someone elese have same problem, so i want to know what is the problem and how to fix it.
i found someone who fixed it with some solution at this topic but that is not my phone model :crying:
i just change my android version to 10 and its not fixed..
i tried home csc and csc files and even tried pit files too..
please hellllp
thanks
Click to expand...
Click to collapse
I had this issue with rooted Android 9, too. But it it very strange you get this problem on Android 10 because the kernel panic problem is fixed there. When you are not rooted, you should not have this problem anyway. Try restore your software in Odin like the other users already suggested.

ThomaSEK said:
I had this issue with rooted Android 9, too. But it it very strange you get this problem on Android 10 because the kernel panic problem is fixed there. When you are not rooted, you should not have this problem anyway. Try restore your software in Odin like the other users already suggested.
Click to expand...
Click to collapse
i just checked my phone for update with Smart Switch app on pc, and that show me an update with a pda and csc codes to update.. i just do it, is it ok right now?

It should be okay, yes.

Justphemy said:
i just checked my phone for update with Smart Switch app on pc, and that show me an update with a pda and csc codes to update.. i just do it, is it ok right now?
Click to expand...
Click to collapse
Please let me know if this has worked for you. I'm having a similar problem that only started when i updated to android 10.
I have a totally stock, Verizon S10. Never had a problem with it on 9. After updating i started noticing after about 8-12 hours phone starts getting very sluggish, gets hot, has trouble even doing processor intensive things like opening camera and taking a picture without it crashing back to the OneUI launcher. Launcher would show up blank and take 5-10 seconds to restore my icons and widgets. Lock Screen lags really bad and face rec hardly works if at all. Phone gets really hot and if i look at the CPUs (Antutu BM) they are usually all maxed out.
A reboot fixes everything and then it will be fine again for another 8-12 hours and then, like clockwork, it starts up again. I've done a factory reset with data restore. Didnt fix it. Did another one without data restore and it is still happening. Would an Odin flash be different than a factory reset from the settings menu?

razen_kain said:
Please let me know if this has worked for you. I'm having a similar problem that only started when i updated to android 10.
I have a totally stock, Verizon S10. Never had a problem with it on 9. After updating i started noticing after about 8-12 hours phone starts getting very sluggish, gets hot, has trouble even doing processor intensive things like opening camera and taking a picture without it crashing back to the OneUI launcher. Launcher would show up blank and take 5-10 seconds to restore my icons and widgets. Lock Screen lags really bad and face rec hardly works if at all. Phone gets really hot and if i look at the CPUs (Antutu BM) they are usually all maxed out.
A reboot fixes everything and then it will be fine again for another 8-12 hours and then, like clockwork, it starts up again. I've done a factory reset with data restore. Didnt fix it. Did another one without data restore and it is still happening. Would an Odin flash be different than a factory reset from the settings menu?
Click to expand...
Click to collapse
no thats not worked..
i have similar problem sometimes

Perhaps reflash the same firmware with home csc

Justphemy said:
no thats not worked..
i have similar problem sometimes
Click to expand...
Click to collapse
I think I may be onto something. Do you have any battery monitoring apps? I had Accubattery, better battery stats, and gsam battery monitor installed. Gsam and BBS had battery_stats permissions granted via adb. I was beginning to wonder if they were causing some kind of memory drain so I wiped their data and uninstalled them. Immediately after that I rebooted and after 46 hours of uptime there was absolutely no problem. Phone flies and runs cool as ice.
I'm currently installing them one at a time and waiting 48 hours after each install to see if and when the problem comes back.
---------- Post added at 12:16 PM ---------- Previous post was at 12:06 PM ----------
And I'd just like to add that when my phone starts acting up it gets worse and worse to the point it won't even unlock and go to the home screen. Then it will actually reboot itself. I assume it panicked because it just doesn't have enough ram to complete any tasks.

so maybe its about the battery for you? btw my problem still alive

Guys, I got the same problem, did you guys find a way to fix it? Just realised today that even the system data, i.e fingerprints have been corrupted, what exactly is happening and how to fix this, it has been driving me crazy for the past couple of months.