Screen wake up lag - Xiaomi Mi A2 / 6X Questions & Answers

Recently when I unlock my phone using the fingerprint sensor, it lags(the screen lights up after about 2 seconds), does anyone else have the same problem?

yup, experienced it lately, no new app installed since this thingy appeared and dont have the cpu stuck bug. Yet I have the superslow mmc bug, I've heard of a batch of A1's (yes, one) mmc fail completely after one year. Considering the fact that the bug is there after a gazilion updates and even showing up on pie, I call dibs on first sign of failure of mmc, but who knows this phone is full of surprise, one thing is for sure, the phone had less bugs in the first moth after release than now ... great job xiaomi I hope the budget pixel release is near ...

Had the same symptoms. I've just rooted so had to do a factory reset and now everything's fine... Installed Trimmer app for easy fstrim and would you look at that, it trimmed 34GB. My bet is that the system just doesn't call fstrim... We'll see

Same problem it take too much time to wake up

Related

[Q] Random Reboots

Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.
I noticed it yesterday once (and I just got the phone then too ;-; ), and it was while I was opening the camera app, I decided to open the keyboard for some reason (I don't know why), the phone locked up for a minute and then just rebooted. I also had a temporary lockup while opening up the keyboard while opening Handcent, but it regained responsiveness after about 15 seconds. For me it happens to be something to do with the keyboard while opening apps. We need more people to reproduce this problem so we can get down to the root cause :|
Got two droid 3`s in my house and haven't experience any random boots.
Sent from my DROID3 using XDA Premium App
Happened to me while talking on the phone a few times. Got a replacement and it happened again. Never with the keyboard though. Very troubling especially with the second handset.
I have experienced reboots with the camera and camcorder apps lagging, and just general issues with those apps anyway.
Sent from my DROID3 using XDA Premium App
I haven't had it happen since I originally posted until today. Today it rebooted in my pocket.
Perhaps it could just be a heat issue. I noticed that another thing along with my other conditions I posted was that the phone felt really hot.
Immolate said:
Perhaps not random, but possibly keyboard related. I believe I have experienced at least three, perhaps more reboots at various times. I just had one a minute ago when I opened my keyboard from a sleep state (dark screen). My lockscreen had what looked like a Droid X background which caught my attention, then after a couple of seconds, it rebooted.
As I mentioned, this has happened at least twice before, but always when I was trying to do something and (I believe) involving the keyboard. I've never had it reboot in the middle of anything, so the impact is negligible. Add to that how FAST the D3 reboots, it's a very minor annoyance. My old Tbolt used to do that as well, but the reboot time was probably three or four times as long, and it sometimes did it in the middle of something.
Has anyone else experienced this? If you have, sound off and perhaps we can get Moto's attention. If it's just me, then that's great news and I doubt I'll do anything about it since the impact is so minor.
It's hard not to notice since it makes the "Droid" noise when it reboots. Assuming you don't have the same sound assigned to a notification of course.
Click to expand...
Click to collapse
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.
justinsaunders57 said:
The Droid 3 has a dual core 1 ghz processor processor built inside which is why it starts up so fast. Its probably having these problems because of the new android OS gingerbread 2.3.2 because of how new this operating system is. The first phone designed with the new OS for verizon wireless was the sony xperia which produced surprisingly a very good battery life with the processer designed for gaming built inside that phone.this reminds me of the first droid on Verizon the Motorola Droid A855 where there where some flukes where it would freeze up every now and then. But there were updates that eventually solved the problem. Because this is a relatively new OS there is deffinittely going to be some flukes in the software and there will be updates to solve these most likely coming soon. And especially as more and more users are buying this phone.
Click to expand...
Click to collapse
1. Everyone knows that it's dual-core.
2. It runs Android 2.3.4. (Hence no root yet)
3. To the OP, no reboots. Had it since the 13th.
Sent from my DROID3 using XDA Premium App
I haven't seen another reboot since the 28th but I did have the odd experience last night of not being able to get a new wallpaper to take. In fact, I noticed that it had one of the stock wallpapers on it, the diagonal black and grey bars, but couldn't change it. Then this morning I thought about it and rebooted the phone. The last wallpaper I'd tried to change it to came up on reboot. Interesting but not alarming... unless it starts doing that frequently.
FYI I haven't noticed it running hot at any point.
Thanks for all the input everyone.
Probably seen it do it half a dozen times. IIRC it's not a full reboot, just the Android stack (i.e., same Linux kernel instance).
Have a logcat of one and don't seen anything that suggests where the problem is..just a whole bunch of "com.xxxxxx.xxxx has died" followed by normal restart log messages.
Odd that you all are experiencing this. I have not had a single reboot.
Sent from my DROID3 using XDA Premium App
This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.
I went into wifi settings and chose to forget all the connections. No more random rebooted.
rustynutzz said:
I went into wifi settings and chose to forget all the connections. No more random rebooted.
Click to expand...
Click to collapse
I wouldn't count on that being the issue.
I've had the problem out in the field (not connected to WiFi) and have had random reboots as well.
Heres a tip for troubleshooting this issue which i 90% guarantee - factory reset your phones put zero apps on them and tweaks, use it for a week and see if u get a reboot.
Then each week after add a single tweak or app(install/uninstall/freeze), may take a yr for some of us since we can't seem to stop downloading random badly coded apps lol...
-smc
For me at least SMC, I've had random reboots from stock during the first week. I'm putting it down to bad software for now.
I usually get 1 a week, sometimes less.
tliebeck said:
This issue is starting to cause me a good bit of frustration. Most of the time it occurs when waking the phone (sliding out keyboard seems to make it particularly likely). Also seeing complete freezes now which require battery pull.
Phone is now more than 30 days old. It was purchased online. Anyone know the odds of getting a *NEW* (not refurbished) if attempting to return it now? I'm still pretty certain this is a software issue, but may try replacing it in the chance it isn't.
Click to expand...
Click to collapse
The same thing was happening to me, the whole rebooting and I went to Verizon for a replacement and got a refurbished DROID 3 Not a New :\
I really hope they fix this because its really bugging me. >:\
-eXsoR
Sent from my DROID3 using XDA App
I get a random reboot usually once a week or sometimes twice a week. It depends on how often I use my camera too.

[Q] Touch buttons dont work after call

Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks
coola71 said:
Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks
Click to expand...
Click to collapse
Same problem here! I don't need to take out battery, just reboot device
Any idea? Root? What ROM?
This thing has too many troubles for users. Just got mine but haven't used it yet. Samsung hasn't made a good phone so far. Problems left to right. Note could be my last Samsung phone.
i have noticed the same thing too, but i am running Sheep Rom, it seems intermittent. what rom are you running?
coola71 said:
Hi everyone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
Click to expand...
Click to collapse
I used to have issues with my prior android phone if I got dirt or whatever over the proximity sensor.
Android phones disable the touchscreen/buttons during a phone call so your cheek doesn't hang up the phone.
If your phone is dirty, however, it gets confused, and keeps things disabled after the call.
This happened to me fairly often when I had a case/screen collector that tended to collect pocket lint.
- Frank
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
CyberGhos said:
This thing has too many troubles for users. Just got mine but haven't used it yet. Samsung hasn't made a good phone so far. Problems left to right. Note could be my last Samsung phone.
Click to expand...
Click to collapse
You can't be bleeding edge without some bleeding.
The GNote ain't perfect and it's a bit rough on the edges, but there's no way I would trade it for any other phone.
- Frank
ChodTheWacko said:
I used to have issues with my prior android phone if I got dirt or whatever over the proximity sensor.
Android phones disable the touchscreen/buttons during a phone call so your cheek doesn't hang up the phone.
If your phone is dirty, however, it gets confused, and keeps things disabled after the call.
This happened to me fairly often when I had a case/screen collector that tended to collect pocket lint.
- Frank
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
You can't be bleeding edge without some bleeding.
The GNote ain't perfect and it's a bit rough on the edges, but there's no way I would trade it for any other phone.
- Frank
Click to expand...
Click to collapse
This. You shouldn't go Samsung or Android if you don't want to do some finetuning. If you want an out of the box solution take buy an iPhone. Then you can wait for Apple to release updates instead of being able to fix it yourself the same day.
i agree, its not even a hardware problem, its a software problem. i can accept small glitches as long as i can fix them, unfortunately you cant fix a hardware malfunction with software, unless of course the patch your applying is going directly over the antenna like a certain iGadget4
coola71 said:
Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks
Click to expand...
Click to collapse
Hi
Even i am facing the same issue n need to know what is the sol. If it is a hardware issue should i get my phone replaced. I bought it only yesterday.
For me too it happens occassionally and requires restart of the phone.
Please help someone.
Just a guess - if all users r not facing it is it a hardware issue
I had this happen once after about 4weeks of using sgn. I don't know if i had made a call prior or what, just before it happened. A reboot made the problem go away for an hour or so. It came back.
I had installed an app a few hours earlier (dell store mobile app). I removed it - not really expecting to fix it. . . It didn't.
After some futzing, I rebooted into cwm recovery: flushed dalvic cache and fix permissions and rebooted. .. it has been working ever since.
This has happened only once, a few days ago. I'd wager it is a software issue.
Sent from my GT-N7000 using xda premium
Even I am also facing the same issue on Sheep ROM
Is this a ROM specific issue or Kernel ?
Same problem here !
I have been using the SGN for the past 4 days. I had this problem in the Stock ROM and it remains even after rooting the phone.
This phone/tablet seems to be a premature release with loads of small problems here and there. I guess they plan to remove these errors directly in ICS.
I believe the problem is on the kernel, try to get some that is stable.
If you are on original stick with it, if you have it rooted try to get the newest kernel.
What happen is that the proximity sensor closes the phone screen, and lower the speed of the cpu, in some times the cpu have some collapses and forget, what you need is to control the cpu or turn off the proximitor sensor, something like that.
I dont have that problem, with both official rom and rooted phone with abyssnote.
I hope this help.
It happened with me too, 2-3 times. Few hours ago I was checking a pdf document and I received a call and the other party couldnt hear me well. While he was calling me again everything froze. Neither touch buttons nor the screen was working. I had to take the battery out, since I couldnt turn it off because of the unresponsive screen. This is really bugging me off.
I've had this occur to me twice, first time I was fidgeting with some app I can't even remember which, second time just a while ago (and that's why I went in here searching), right after making a call.
Using the S-Pen to swype-gesture back and menu they work though, it's just the buttons themselves that are dead.
Wouldn't think the proximity has anything to do with it (nice idea anyway) because then the whole screen should be unresponsive to touchm, wouldn't it?
BTW I am using xlite rom now, and maybe I could go for the cache wiping.
EDIT: I had cleared cache partition and dalvik cache this morning, ths afternoon the note has been sitting idle on the desk, 2mA drain according to battery monitor widget estimates, and without any calls the buttons stopped working again...
xinato91 said:
I believe the problem is on the kernel, try to get some that is stable.
If you are on original stick with it, if you have it rooted try to get the newest kernel.
What happen is that the proximity sensor closes the phone screen, and lower the speed of the cpu, in some times the cpu have some collapses and forget, what you need is to control the cpu or turn off the proximitor sensor, something like that.
I dont have that problem, with both official rom and rooted phone with abyssnote.
I hope this help.
Click to expand...
Click to collapse
+1 I'm using Abyssnote kernel too - no problems with soft buttons yet.
anyone find a fix for this yet? i have to reboot my phone after pretty much every call to get the buttons working again. starting to get really annoying
forgot to mention im on stock rom unrooted
Reset and Root - CFKernel and AbyssNote worked for me
n0thingr3mains said:
anyone find a fix for this yet? i have to reboot my phone after pretty much every call to get the buttons working again. starting to get really annoying
forgot to mention im on stock rom unrooted
Click to expand...
Click to collapse
I had rooted and applied CF Kernel to my rom and had faced a few problems. But after wiping and applying CFRoot (latest) again I did not face any problems.
I have had no problems in the past 24 hours.
You can use the guide by Chainfire to root and apply CF Kernel (the best guide ever) and test for a day or two. then try moving to AbyssNote1.4 (I moved because I wanted to test OC)
Before you root and flash kernel, I will recommend factory resetting(since you are unrooted at the moment) and do not install any apps - because that is what actually worked for me.
UPDATE :
I havr started facing button issue on 1.4 AbyssNote as well.
Same problem here not woking :-( :-( :-(
---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------
How to fix this bug???
So, some news. I've been fighting with a nasty battery drain due to the phone being unable to keep the deep sleep status. In the process I've tried flashing AbyssNote kernel 1.2 (people were saying 1.4 suffered from high drains, and I haven't seen this problem since then... but it's been just a few, so it may be too soon.
ephestione said:
So, some news. I've been fighting with a nasty battery drain due to the phone being unable to keep the deep sleep status. In the process I've tried flashing AbyssNote kernel 1.2 (people were saying 1.4 suffered from high drains, and I haven't seen this problem since then... but it's been just a few, so it may be too soon.
Click to expand...
Click to collapse
I can confirm high battery drains with Abyss 1.4 (revert back to 1.2). But it is the only kernel which don´t suffer "touch buttons bug"

[Q] Galaxy NOTE SOD problems.

My brother's galaxy note have been facing serious sod problems since he bought the phone at Nov 2012. After he faced it the 1st time , he sent to SC and got it back. After 1-2months the problem came again and he asked for my help. I persume it was because the malaysian firmware of the ICS was somewhat unstable from what i read from forums here and there. So i changed the firmware to JB duno from which country when it came out in MAC. After a week or so. The problem reappeared . So I just decided to root and chnge the kernel and also the ROM. Changed the ROM to a stock rom and a kernel. Still the problem persist. I'm out of options. Went to the ****ty SC and the idiots just factory reset the phone and give u back. BUNCH OF RETAR*S . (sorry for my languange)
Hope someone here may help me out with my problem. Thanks a million :laugh:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
abhinav quietly brilliant said:
Check all the apps you have installed maybe you find the bad one whose causing it as you have mentioned it comes after sometime of installing a fresh rom and have you tried any aosp rom maybe that will fix the issue
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I just installed an aosp rom (PA) and I hope it fixes the problem. Well I've seen the amount of apps installed in the note and its jst a quarter the amount I have in the Galaxy S2 and my S2 works like a charm. The note has been giving me headache ever since I got it from my brother. Hope this does solve it , if not I guess its something else maybe hardware
Phone sod twice on paranoid android. FML! Guess im visiting SC tmrw again.
Same problem with me..
My Note 1 has SOD since 1st time bought it..
be patience to install JB --> still SOD
change kernel to SpeedMod 5.3 --> SOD again
change kernel to PhilZ --> sometimes SOD
I have read many information that related with SOD in galnote 1, my opinion it is related with hardware too.. sometimes
or it is related with kernel... it can not wake from deep sleep..
anyone have another better suggestion to cure this ?
if u're using pure stock rom still facing the same problems then definitely is hardware issues!
if ur device still under warranties suggest bring to SC ask them do a thorough check on it n let them know what's going on actually...
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
psywarx said:
Yes, I use stock ROM still has SOD,
so it's hardware issue for sure...
but I will keep the phone for now because sometimes SC doesn't give solution to this..
Click to expand...
Click to collapse
Yeah and they will give your phone back only doing a factory reset lol
Sent from my GT-N7000 using Tapatalk 2
I too get this SOD once a week on my GT-N7000
Phone status when this happens:
stock JB(earlier ICS), non-rooted, data connection, wifi, GPS, bluetooth all disabled. Battery mostly above 80%.
Gmail, Google+, Facebook and all other social n/w apps disabled (yes, i am an oldtimer )
During SOD, if a third party calls my number, he hears it ringing, but my handset is dead as dodo (quite dangerous as the calling person may think i am not answering it)
i used to get this when it was on ICS and still getting it after i upgraded to JB.
Most of the time, SOD occurs during wee hours in morning ( i used battery monitor app that logs battery stats every 10 minutes to check the time when this happens).
Sometimes it occurs when the phone is in my jeans back pocket. phone needs a 10 second press on pwr switch to restart it.
Turning off the "power saver" mode seem to reduce the probability of SOD.
i have taken this phone to SC and they re-flashed the JB.
i told the SC chap that i have already done this and couple of factory resets, but he said that they do "much more" than just re-flashing through kies like calibrating camera, bluetooth )
does anyone in the know, know if this is indeed true ?
Thanks
-mprab
updates...
After 2 days of re-flashing at a samsung authorised service center, i got SoD 2 times in a period of 12 hours.
once last night and second time when i was traveling to office.
Last night i installed some bare-minimum apps back after waiting 2 days for any SoD to happen in "stock" condition.
Well.... i did not pay 30K to use the GNote as just a phone, so installed some basic apps (Battery monitor, Bangalore BMTC, RealCalc, GPS Test, ES File explorer and a first time app StatusLogger)
phone went dead at 1:00 am in morning and as usual there was no wakeup alarm.
phone was warm to touch when it was lying dead. The battery which was 96% at 00:30 AM had gone down to 54% at 7:00 AM.
Status logger did not show any loss of GSM signal which might have resulted in phone transmitting at higher power/hunting for signal etc.
The "radio" seemed working, because when i made a call to the dead phone from my landline, i could hear the phone ring instead of expected "phone is switched off" message i was expecting.
So this has to do with application processor going in some infinite loop.
Uninstalling all apps is NOT an option.
anyone know if we can establish any debug connection to phone and know what the hell CPU is up to in this situation ?
any processor logger that will periodically log all the processes running on phone ?
SOD resolved... not a single one since 6 months.
Hey guys, just wanted to share this info with you, I had SOD's like anything and did all freakingly possible things right from flashing roms to kernels, speed up CPU, banging my head in front of the dumb witted morons at samsung service... to get rid of that pain. What helped me was an app called "WAKELOCK" by darken which is merely 72kb in size but works wonders, not a single SOD after that. What u need to do is.... it has a list of presets that makes sure your cpu stays up. You need to select the preset called "partial wake lock" which is at no. 4, and viola...
It ensures that the CPU is running. No SOD ever after. Also, you need to make it autorun on boot from the options. Yea, it does eat up batter a bit more but its definitely manageable. I still need to charge my note only at night.
Just to be sure, I uninstalled it and guess what, SOD returned. So, do try it, I hope it helps...

too many problems with this phone.

Seems once again Sony can't seem to get a stable phone. Shame as it offers so much potential with good design and great specs but failing on software again.
Constant app crashes, phone freezing,
Just goes to show you can't just chuck all the latest bits in a package and think it will work.
Going to have to return this unless there is a sudden fix in the next few days as I only have a 14 day change or mind.
That hasn't been my experience at all. I got the US phone and flashed the UK firmware. I haven't had any issues whatsoever. You should try a factory reset before returning the phone.
I have it for 2 weeks now, no freeze or reboots whatsoever... European Firmware here...
My phone was purchased from O2 in the UK. Don't think there is much bloat on there so don't think it's O2 that's screwed it up.
Phone is completely standard with just a handful of apps on it.
So far I have had numerous '' email has stopped working' to Google stopped working to music not working errors.
OK Google seems to hardly ever work. Almost seems like it can't hear the hot word.
I also think that many of the push services are being put to sleep which is why the battery life is so could as I often don't get notifications until I wake the phone yet the same accounts on my old s3 always come through first.
So far had one update come out for the phone. Don't know if it's the latest firmware though.
I can totally not agree with you.
Well I guess all I can do is try reset then but it's such a pain in the ar#e putting all your info back in again.
hpsauce37 said:
Well I guess all I can do is try reset then but it's such a pain in the ar#e putting all your info back in again.
Click to expand...
Click to collapse
Does the launcher you use rebuild your home screens after a reset? I still use Google Now Launcher, and after a reset, when I reinstall GNL, everything is put back in its proper place, even web browser page links.
I am using the US firmware, and have not experienced any of the problems you mention. You may have a defective unit. Then again, if you're not happy with the phone for other reasons (and there certainly are things that could be better), you certainly don't want to wait past the return date!
I'm running the UK firmware with the US OEM file to have Volte and fingerprint sensor on T-Mobile and has been rock solid since day one. I would reset.
Have reset the phone and just setting it back up.
Will see how it goes over the next few days.
One thing I did think that was odd previously when it was playing up was when it would crash and reset itself was that when it started up it was on the Google keyboard set up screen. I had installed the Google keyboard as I preferred it to SwiftKey. Maybe the issues were linked to that somehow.
Wow too many errors there... Probably a faulty unit... Or maybe u should do a software repair with Sony pc companion
Don't forget it runs Android Orea 8.0 by means a lot of third party apps may not fully compatible at this moment, consider not many phones running Oreo hence the app developers are not in hurry to tweak their app to run smooth in Oreo. That's what causes the occasional app crashes I believe.
OK so after the full reset and initial impressions are good. Seems smooth with no crashes. I'm back running nova launcher (previously instilled this as thought it might be linked) ive also not installed Google keyboard yet and giving SwiftKey a go.
Only issue that really remains is the one with the ambient sensor. Find my self having to switch the adaptive brightness off at night when using the phone as it jumps around. Need to then switch it back in on the day where it seems fine. Hopefully a fix comes for this soon.
hpsauce37 said:
OK so after the full reset and initial impressions are good. Seems smooth with no crashes. I'm back running nova launcher (previously instilled this as thought it might be linked) ive also not installed Google keyboard yet and giving SwiftKey a go.
Only issue that really remains is the one with the ambient sensor. Find my self having to switch the adaptive brightness off at night when using the phone as it jumps around. Need to then switch it back in on the day where it seems fine. Hopefully a fix comes for this soon.
Click to expand...
Click to collapse
On reddit someone write that he downloaded LUX https://play.google.com/store/apps/details?id=com.vitocassisi.luxlite and everything was working much much better. Maybe later i will find the post. (https://www.reddit.com/r/SonyXperia/)
No single reboot or app crash for me.
The only thing that crashes on me on occasion is Google Photos, other than that, rock solid so far.
Just had an a 3rd party app crash but as someone mentioned above it might be because the developer has not updated yet for oreo???
Other than that been much better so far
Davka said:
No single reboot or app crash for me.
Click to expand...
Click to collapse
Same for me. 3 weeks i have got it 100% stable.:good:
Uhm ok I guess now it's my turn.
Today the "touch" went crazy. 2 times. Like for example keeping pressing recent button ? will result in multiple touches. Basically every touch is not a "pressing" touch. So I can't do swiping or other keep pressing relative touching. First time happened, a reboot fixed. Second time nothing worked. I have to SHUT DOWN THE PHONE AND WAIT A LITTLE BIT, then turn it on and everything was OK...
Is it just me?
P.s. UPDATE: I tried everything, safe mode, total reset, even software repair through PC companion...nothing. Its obviously a hardware problem, not software related. I returned this morning to assistance. They should give it back to me within a week...
My first week with XZ1C, 100% working, perfect, no reboot or other problems. One of the best phones I ever bought...
Phone's stable, no software/hardware issues. Working away reliably, battery consistently giving me expected results (ending day with 25%-50%, depending on use), connectivity perfect, performance smooth as butter.

Phone Got restarting on opening Camera

Hi,
After updating to June Security Patch , I have some problems
First The Camera ,
When I open camera after a few seconds Phone will got restart , it doesnt matter its Nokia Pro camera or Google Camera app
I tested both
and another problem is Sound , when the media volume is high playing in musics or videos sound will be laggy (it will be mute for a bit and playing , and this will repeat)
I tried Factory Reset , anyone else has this problems?
or Solution to fix
A guide for Downgrade will be great
mygamers said:
Hi,
After updating to June Security Patch , I have some problems
First The Camera ,
When I open camera after a few seconds Phone will got restart , it doesnt matter its Nokia Pro camera or Google Camera app
I tested both
and another problem is Sound , when the media volume is high playing in musics or videos sound will be laggy (it will be mute for a bit and playing , and this will repeat)
I tried Factory Reset , anyone else has this problems?
or Solution to fix
A guide for Downgrade will be great
Click to expand...
Click to collapse
Well I have same problem right now... Did you solve it somehow?
Mitoush said:
Well I have same problem right now... Did you solve it somehow?
Click to expand...
Click to collapse
unfortunately No
I sent device to guaranty and they couldn't do anything with problem
at least I bought Nokia 7 Plus
mygamers said:
unfortunately No
I sent device to guaranty and they couldn't do anything with problem
at least I bought Nokia 7 Plus
Click to expand...
Click to collapse
Well now even my speaker is beginning to have problems with high sounds. Dream phone ? I will try to send it on warranty and I will see...
I also have this problem, noticed it after i updated to october security patch, tried reformatting multiple times but to no avail.
In my case not only the camera app force reboots my phone.
Speakers also have the same problem, at a certain volume level the sound breaks /lags.
Hopefully this is just a software problem, my phone doesn't have warranty anymore...
Did you try factory reset? Did it help? I am going to try it cause I need my phone for work and I don't want to be 30 days without phone.
No factory reset did not work, but I noticed that keeping the phone plugged into a charger keeps it from restarting.
Yes I have it same... It can be only problem with battery maybe.
Yeah, best to have the battery checked and replaced, hopefully I can find a service center here in the Philippines
markleoibo1994 said:
I also have this problem, noticed it after i updated to october security patch, tried reformatting multiple times but to no avail.
In my case not only the camera app force reboots my phone.
Speakers also have the same problem, at a certain volume level the sound breaks /lags.
Hopefully this is just a software problem, my phone doesn't have warranty anymore...
Click to expand...
Click to collapse
i too have the same problem, did you get it fixed???
Same problem here
Hi I am from India I am also getting same problem s
1)when I open the camera phone is restarting
2) when I try to play music in his volume it's breaking.
And I done hard reset also still it's not resolved, can you show me way to fix it?
Hello, I brought mine to the service center and they replaced the battery and now its fixed, good thing i was under warranty so it was free of charge
mygamers said:
Hi,
After updating to June Security Patch , I have some problems
First The Camera ,
When I open camera after a few seconds Phone will got restart , it doesnt matter its Nokia Pro camera or Google Camera app
I tested both
and another problem is Sound , when the media volume is high playing in musics or videos sound will be laggy (it will be mute for a bit and playing , and this will repeat)
I tried Factory Reset , anyone else has this problems?
or Solution to fix
A guide for Downgrade will be great
Click to expand...
Click to collapse
I try to fix it from the care center.
They need to replace the mainboard, battery, and the loudspeaker. South Borneo, Indonesia needs approx 3 weeks for the indent parts. Fortunately, i still have the guarantee. Tomorrow i will give the device to them to fix the problems. Hopefully it works best result.
Just FYI, from my experience.
Yeah, same problem here. Phone restarting on opening camera, and when while watching video with volume above 66%
I've tried factory reset, and even reflash stock room but still doesn't work. Maybe it only happened with android pie? Anyone try downgrade to oreo?
ghostwalkergamma said:
Yeah, same problem here. Phone restarting on opening camera, and when while watching video with volume above 66%
I've tried factory reset, and even reflash stock room but still doesn't work. Maybe it only happened with android pie? Anyone try downgrade to oreo?
Click to expand...
Click to collapse
I did every possibilities, did not work.
Downgrade too, manually by my self.
Downgrade by the care center also did not fix it.
Sorry to say it.
Its the hardware, dont know what cause it. Best possible its caused by the update. May the software cause the hardware broken..? ??
HMD, please... R u serious 2 produce a flagship phone?
Same problems here. HMD is crap!
I purchased this device in October 2017 and the problems have just amplified like crazy.
After the April update, random reboots, distorted audio, ultra slow charging.
A lot of money down the drain as this phone has NO RESALE VALUE either.
This is not a flagship. This is a phone made of all the leftover reject cheap hardware materials and hence it sounds good on paper.
The only credibility it has is because of Google and Qualcomm.
Honestly, after 20 months of use, I can say I've never used such a horrible device ever. This phone is pure headache.
what a disappointing phones by Nokia, disaster, disgraceful to users. I think this i s my last Nokia phone (at least last by HMD)
Guess what..?
Ive been waiting for 3 weeks for the repair.
The care center said rhat i must wait for 2 more weeks and then they will tell me the approx time to wait for more.
So,
3 weeks passed,
2 weeks more to wait an info,
Dont know if that after the 5th week the device is ready for use or not.
Wasting much money to buy this one.
I feel sick at once
Nothing like this. HMD is the only one who did this ever.
I too facing this problem for the past 3 weeks or so. Random restarts especially when starting the banners camera. Someimes 2or 3 such episodes. The problem with the sound cracking at high volumes I've been having for 2 months now. The problem increases when the battery guess below 40%. And decreases when it is being charged. ?? A battery issue. Maybe not because otherwise I've a decent battery life.

Categories

Resources