Related
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.
Out of the blue yesterday, my AT&T Moto X stopped vibrating. I noticed it first with the soft keys (home, back etc) but it affects everything from vibrating on ringing, to enabling silent mode, to unlocking with active display, to games.
I've tried rebooting and toggling vibration in settings. I've downloaded vibration tester apps from the Play Store. I only have the same ~70 or so apps that most of us use (dropbox, weather channel etc) and I don't run any obscure apps (less than 1000's of downloads), and I hadn't downloaded anything new for hours before the problem started.
I feel I've tried all the basic stuff, except factory reset, I don't think there's anything too obvious I'm overlooking.
So that leaves me facing either a hardware or software problem. I doubt its a problem with the physical vibration motor. Factory defects are so ridiculously rare that it should never be your first course of action. However, if it's a problem with the hardware I could try my local ATT Service Center. If it's a software problem, which seems much more likely, I could try a factory reset on the device. However it seemed a wise idea to post this question to the pros before I go down that road.
Appreciate any help you guys can offer.
AT&T Moto X
4.4
Not rooted
I would try a factory reset if you done everything else. My wife's Galaxy S3 did the same thing after the update to 4.3. A factory reset fixed it.
my gf's at&t motox running 4.2 lost vibration too. after many many reboots it would randomly work, or work very weakly (so it wasn't a problem with the physical motor, maybe it was an electrical connection to the motor?).
it was covered under warranty. they gave her a code, she re-did motomaker, and returned her original broken phone in the box the new one came in.
I hate the vibration in this thing. I would love mine to stop lol
Sent from my XT1058 using Tapatalk
I just performed a standard factory reset on the device and the problem persists... No vibrations, anywhere.
Is there anything else I can try? or am i headed to a service center?
Deenybird said:
I just performed a standard factory reset on the device and the problem persists... No vibrations, anywhere.
Is there anything else I can try? or am i headed to a service center?
Click to expand...
Click to collapse
You can sbf back to 4.2.2. I had a connectivity problem and a factory reset didn't fix it. But going back to 4.2.2 and taking the OTA did.
All the files are in the Dev section. If the links are broken I have copies of everything I can share. Except the 4.2.2 file for att I have Verizon.
Sent from my XT1060 using Tapatalk
If that doesn't work then your only other option is a warranty claim. Or live with it I guess.
The final verdict:
With nothing else working (factory reset, safe mode etc) I took the device to the ATT service center. They replaced the device, attributing the problem to defective hardware. Still find it hard to believe it was actually the hardware, but I don't see any other conclusions to draw.
Thanks for everyone's help.
Deenybird said:
The final verdict:
With nothing else working (factory reset, safe mode etc) I took the device to the ATT service center. They replaced the device, attributing the problem to defective hardware. Still find it hard to believe it was actually the hardware, but I don't see any other conclusions to draw.
Thanks for everyone's help.
Click to expand...
Click to collapse
At least it worked out and you have a working phone again.
I am with this problem right now and i can´t fix it.
After i flashed CM13 without Gapps my Moto X 2nd (xt1097 brazil) all vibration stopped working.
I tried going back to stock rom 5.1, 6.0 and even NX 10.1 but with NX i can hear something vibrating the phone, so i eliminated the possibilite of a hardware malfunction.
I don´t know what to do...
please help
Hello!
Wifi and Bluetooth aren't working anymore When you try turning them on, them just turn off immediately. It has been going on after KitKat 4.4.3 update.
It's the same situation this member described in this thread: >>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-bluetooth-issues-t2808419<<<<
He also uploaded a video about this issue: >>>>youtube . com / watch? v = girqFv6eWnQ<<<<
I also have been reading this threads:
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479<<<<
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308<<<<
and the solution for this would be replace the WCNSS_qcom_wlan_nv.bin in the Persist folder. As my phone is not rooted, it seens impossible I had accidently deleted this file, right? Anyway, the Persist folder of my phone is empty. It's because my phone is not rooted so it doesn't show the files inside the folder? At the wlan/prima, there are the following files:
WCNSS_cfg.dat
WCNSS_qcom_cfg.ini
WCNSS_qcom_wlan_nv.bin (that's the file, right?)
WCNSS_qcom_wlan_nv_calibration.bin
WCNSS_qcom_wlan_nv_regulatory.bin
Is there some possible solution or I really need to send my phone to technical support?
I'm sorry about my English and my poor knowlegde. Thank's a lot!
rafaelrossignoli said:
Hello!
Wifi and Bluetooth aren't working anymore When you try turning them on, them just turn off immediately. It has been going on after KitKat 4.4.3 update.
It's the same situation this member described in this thread: >>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-bluetooth-issues-t2808419<<<<
He also uploaded a video about this issue: >>>>youtube . com / watch? v = girqFv6eWnQ<<<<
I also have been reading this threads:
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/wifi-isnt-t2760479<<<<
>>>>http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308<<<<
and the solution for this would be replace the WCNSS_qcom_wlan_nv.bin in the Persist folder. As my phone is not rooted, it seens impossible I had accidently deleted this file, right? Anyway, the Persist folder of my phone is empty. It's because my phone is not rooted so it doesn't show the files inside the folder? At the wlan/prima, there are the following files:
WCNSS_cfg.dat
WCNSS_qcom_cfg.ini
WCNSS_qcom_wlan_nv.bin (that's the file, right?)
WCNSS_qcom_wlan_nv_calibration.bin
WCNSS_qcom_wlan_nv_regulatory.bin
Is there some possible solution or I really need to send my phone to technical support?
I'm sorry about my English and my poor knowlegde. Thank's a lot!
Click to expand...
Click to collapse
There is no way to prove that persist is vacant as you are unrooted. It is most likely a coinsident hardware failure. But still possible.
Go warranty replacement. Rsd restore is no help as persist is not in the XML.
aviwdoowks said:
There is no way to prove that persist is vacant as you are unrooted. It is most likely a coinsident hardware failure. But still possible.
Go warranty replacement. Rsd restore is no help as persist is not in the XML.
Click to expand...
Click to collapse
For first, thank you for your concern.
I see. It's a poor situation we have been seeing with others Moto X owners, especially after 4.4.3 update. Considering it's not a hardware issue and 4.4.4 update release (my phone is still in 4.4.3), is the 4.4.4 update worth it? I have been reading about increasing battery consumption after 4.4.4 update. I also have read about restoring the stock rom could be a worth try, even if your phone has never been rooted. What you say?
rafaelrossignoli said:
For first, thank you for your concern.
I see. It's a poor situation we have been seeing with others Moto X owners, especially after 4.4.3 update. Considering it's not a hardware issue and 4.4.4 update release (my phone is still in 4.4.3), is the 4.4.4 update worth it? I have been reading about increasing battery consumption after 4.4.4 update. I also have read about restoring the stock rom could be a worth try, even if your phone has never been rooted. What you say?
Click to expand...
Click to collapse
I have a Maxx now on 444, not rooted & 444 is fine. There is much feedback on x 444 around.
aviwdoowks said:
I have a Maxx now on 444, not rooted & 444 is fine. There is much feedback on x 444 around.
Click to expand...
Click to collapse
So I will try to update it on 4.4.4. A last question I forgot asking: my 3/4G is working fine. 3/4G has nothing to do with wifi/bluetooth hardware/software, right?
rafaelrossignoli said:
So I will try to update it on 4.4.4. A last question I forgot asking: my 3/4G is working fine. 3/4G has nothing to do with wifi/bluetooth hardware/software, right?
Click to expand...
Click to collapse
Correct.
I've sent my phone warranty. I'm a previous contact they told me it's probably a hardware issue. The battery comsumption has increased a lot and the explanation is that phone is constantly searching for wifi/bluetooth. Is it possible even with hardware failure?
When I get my phone back tell you what was it's problem and the possible solution.
Wifi and bluetooth had started working from nothing. Then, it stopped again. And it went this way several times since. Now, it's working properly, but it may stop anytime. Could it still be a hardware issue? I just have updated 4.4.4 yesterday. In one of the situations, I found the message "supplicant status: scanning".
rafaelrossignoli said:
Wifi and bluetooth had started working from nothing. Then, it stopped again. And it went this way several times since. Now, it's working properly, but it may stop anytime. Could it still be a hardware issue? I just have updated 4.4.4 yesterday. In one of the situations, I found the message "supplicant status: scanning".
Click to expand...
Click to collapse
Yes. based on the information you have provided, and my personal experience, I would suspect a hardware failure.
samwathegreat said:
Yes. based on the information you have provided, and my personal experience, I would suspect a hardware failure.
Click to expand...
Click to collapse
Well, wifi and bluetooth aren't working anymore since my last post. There's a big battery drain - something like 60% of battery life in 3 hours with phone - supposedly - in sleep mode, even when it is in airplane mode. It seems the system tries to find wifi and bluetooth. When I see my battery status, Android OS and Android System processes are draining more battery life than screen itself. Could it be a hardware failure even if wifi and bluetooth get back working sometimes?
I think I'll buy a lower cost android phone if I decide sending my Moto X warranty. It's complicated staying without a smartphone during 20~30 days.
I appreciate you all for the help and considerations.
Update: sending my Moto x warranty. Tell you what was wrong when I get it back
crappy wifi
rafaelrossignoli said:
Update: sending my Moto x warranty. Tell you what was wrong when I get it back
Click to expand...
Click to collapse
Have you managed to get an update? I think I am having the same exact problems.
Not a developer device so can't unlock the bootloader
Not rooted. \persist\ is empty if that would make any difference at all.
Surprisingly once when I restarted the phone in bptools menu options on the boot menu, the phone came up fine and I was able to turn on my wifi and bluetooth. After about 10 minutes, the phone restarted on it's own and ever since they won't turn on.
Did a full wipe, FDR and also wiped cache but still the same now. Booting using BPTools menu option doesn't help any more.
For the last couple weeks, my phone is just guzzling data on 4G. Having a wifi would help. Please don't suggest me to do a warranty repair That is what I might end up doing in about two weeks. The unlocked device was bought in India but I am now abroad.
Using XT1052 running Kitkat 4.4.4 - AsiaRetail.
mutukrp said:
Have you managed to get an update? I think I am having the same exact problems.
Not a developer device so can't unlock the bootloader
Not rooted. \persist\ is empty if that would make any difference at all.
Surprisingly once when I restarted the phone in bptools menu options on the boot menu, the phone came up fine and I was able to turn on my wifi and bluetooth. After about 10 minutes, the phone restarted on it's own and ever since they won't turn on.
Did a full wipe, FDR and also wiped cache but still the same now. Booting using BPTools menu option doesn't help any more.
For the last couple weeks, my phone is just guzzling data on 4G. Having a wifi would help. Please don't suggest me to do a warranty repair That is what I might end up doing in about two weeks. The unlocked device was bought in India but I am now abroad.
Using XT1052 running Kitkat 4.4.4 - AsiaRetail.
Click to expand...
Click to collapse
For first, thank you for reminding me about this thread. I bring bad news for you, unfortunately. It's 99% a hardware failure. In my case, it really was one. After 25 days, my phone was back from warranty with a new wifi/bluetooth hardware.
My phone was behaving the same way as yours. Sometimes the wifi was back working for a while, then my phone restarted and wifi was unavailable again. So, i recommend you send your phone warranty as soon as possible. Good luck!
rafaelrossignoli said:
So, i recommend you send your phone warranty as soon as possible. Good luck!
Click to expand...
Click to collapse
Well, I don't think I really have a choice here. I would be able to give my device for service only in about another 2 weeks so I have to live with 4G! I'll let you know how it goes. And thanks for the update...
wifi and bluetooth not turning On FIX
Hello everybody.i use a moto x (xt1052) 4.4.4 kitkat not rooted.
A week ago started having problems with wifi communication not turning on and a couple of days later bluetooth couldnt locate any connections
I fixed these problems by switching to ART Runtime from the developer settings.this will reboot your phone and starts upgrading your apps .after that wifi and bluetooth work fine .(for now..)
I am also wondering if anyone has any random reboots or its just my pocket..
Hope it helps for you too.
Cheers,Stelios
Updated: WiFi and Bluetooth stopped working again.leaning more on software issue than hardware.
are.petrakis said:
I fixed these problems by switching to ART Runtime from the developer settings.this will reboot your phone and starts upgrading your apps .after that wifi and bluetooth work fine .(for now..)
Updated: WiFi and Bluetooth stopped working again.leaning more on software issue than hardware.
Click to expand...
Click to collapse
Nope, that didn't help me at all. I think at least my issue is hardware related. Giving the phone for warranty repair on Thursday, let's see what happens.
Update
Been to the service center a week ago. Apparently the moment I explained my issue, they said it is an hardware issue and so the board needs a replacement. Got my phone back and it has been a week with no issues. Fingers crossed...
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
Hi,
I have a N9600 Snapdragon, currently on Pie.
The problem started occurring 3 days ago, for no particular reason, phone wasn't under water or dropped or anything.
When the fingerprint unlock is on, and the phone goes to sleep it shuts off.
Turn off the fingerprint unlock and everything is in order.
The fingerprint scanner functions within apps and for gestures.
Samsung support post here with people having the same problem on all 9s.
https://us.community.samsung.com/t5...f-when-usinf-fingerprint-security/td-p/346174
This cant be a hardware problem when its happening to so many people across models?
And yes, Factory Reset doesn't fix it, Its still there in safe mode as well. Ive even tried flashing a different region firmware, problem still there
Any help will be greatly appreciated.
Send it for repairs until fixed
tyrell22 said:
Hi,
I have a N9600 Snapdragon, currently on Pie.
The problem started occurring 3 days ago, for no particular reason, phone wasn't under water or dropped or anything.
When the fingerprint unlock is on, and the phone goes to sleep it shuts off.
Turn off the fingerprint unlock and everything is in order.
The fingerprint scanner functions within apps and for gestures.
Samsung support post here with people having the same problem on all 9s.
https://us.community.samsung.com/t5...f-when-usinf-fingerprint-security/td-p/346174
This cant be a hardware problem when its happening to so many people across models?
And yes, Factory Reset doesn't fix it, Its still there in safe mode as well. Ive even tried flashing a different region firmware, problem still there
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Either disable FP, or wait for a software update.
A quick search found this:
https://us.community.samsung.com/t5...usinf-fingerprint-security/td-p/346174/page/3
revert back to orio. Orio is most stable version.
Maybe make a factory reset with Odin
i had tried all of these ( Factory reset, back to oreo ) nothing fixes, to be honest, the problem begun on oreo.
Already sent it to samsung, they didn't find any problem, but after 3 times they gave me a new phone since those are the rules in my country
Open a RMA request and see what happens, ppl say that you should turn off FP, but it does make a substantial difference, at least for me, its pretty bad, using another method since i really don't like the iris scanner.
Same
My phone started shutting down on its own while in sleep mode out of the blue just the other day. Found this thread and discovered that this was the problem. This is super annoying. If a software patch is all that is needed, it can't come soon enough.