Related
Im really really hoping that someone can help me here
It started this morning around 10:00 or so - I took my phone out to check my messages, everything is working fine. I lock the phone and put it standby (power button) and *surprise*, it locks up and wont come out of standby
So i just re-set it (like im forced to do 20 times a day) and instead of booting it went straight to this red/green/blue screen. At the bottom of the screen it just says "Serial" but doesn't actually give a serial.
I instantly thought it was bricked, so i removed the battery and left it out for a few mins. Then i put the batt back in, and it booted normally. I used it throughout the day with no problems.
Fast forward a few hours and it does it again but now it wont boot at all (ive reset the thing like 100000 times in the last hour ive been working on it).
WTF is going on?? Im really really hoping that it isnt too screwed to fix
The last program I installed was the SPB pack, but that was over a month ago, and i use the phone every day, multiple times a day.
Oh, and to make things worse i was planning on relying on my TomTom tomorrow
and the text on that screen says:
Kais1*0
SPL-1.56.0000
CPLID-8
And at the bottom it just says "Serial" but none is given.
This blows
Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.
Do you see "USB" instead of "Serial" if you connect your sync cable to your phone when in the bootloader?
If so, I would download the latest carrier-branded rom and flash it to your device. As long as the rom is designed for your device, then you do not need to do anything special prior to running the file from your PC.
grandpareza said:
Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.
Click to expand...
Click to collapse
I have never flashed it but i have spilled water near it (on the counter, the phone got wet but that was months ago and has no relation to this).
Can they check if it has been wet before?
When i plug it into my computer it says USB instead of serial. Should I try to re-flash with an updated rom and see if it fixes it or just take it in?
If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.
GSLEON3 said:
If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.
Click to expand...
Click to collapse
Thanks, ill give you a buzz.
I need to finish and email a few things first (shouldnt take more than 30mins).
Actually, ill just message you tomorrow or something.
Ive been really busy this week.
well did you get it fixed? what did you do?
Yikes, that happened to a friend of mine, but he flashed his and then had to reflash it. I think there is a place on the back under the battery that they use to tell if it's been wet. I would take it back, even if flashing it fixes it, you don't want it to happen again.
oh and it doesn't mean serial like a serial number, it is a serial connection.
I havent been able to get it fixed.
I think ill try to flash it this weekend and see if that fixes it
You'll only make problems worse if you reflash. I've analyzed the MTTY output you've sent me & you have a bad NAND storage blocks.
You need to follow the directions I sent to your email account via MSN IM.
DO NOT REFLASH UNTIL YOU'VE TAKEN CARE OF THE BAD BLOCKS!!!
this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
dockular said:
jackjohnson said:
dockular said:
Sup Jack, my Tilt is doing the
Kais1*0
spl-1.56.0000
cpld-8
Serial
problem that you had talked about. I read that huge thread, lots of great info in there. Although its unfortunate what happened to you, I'm really grateful of all the troubleshooting that you've done before me, so I know what works and what doesn't. Interesting to note that I have had the Tilt since the day it came out, and never cooked/ flashed my rom. I have been using the Tilt rom the whole time with no problems. Otherwise I'm a huge power user and have a ridiculous amt of software installed.
So after everything was all said and done, did you end up just replacing the device? Thanks again man
-Anthony
Click to expand...
Click to collapse
Anthony,
Yea I went ahead and replaced it. No matter what I did to reflash the original bootloader, and flash the original rom, I always ended up with that same problem. Did you notice that if you can't get it out of the bootloader, but you connect it to your computer, and while it's connect, you soft reset, that it boots? Just curious. that's what happened to me. Either that or I would have to yank the sim and battery, then try.
My tilt was working fine for about a month with a flashed rom, up until I started installing gobs of software on it. Just a thought. If I were you, I would get the device replaced. Especially if you've never flashed a new rom on it - it definitely should not be doing that.
Scott
Click to expand...
Click to collapse
My computer has been broken for a month or two. To answer your question - I haven't been connecting it to anything other than an AC outlet. Anything installed in the last couple months was installed OTA... I usually just obtain a CAB by downloading it directly onto my device.
Also, its weird but sometimes after I drain the batter with the RGB screen then recharge it (this process takes about a day) then hit the reset button, it will actually boot correctly. I am on the third time this has happened. It was bricked for a couple days, then after a combination of charging / depleting got it to boot into windows. Then it happened again, then again.
As long as I don't restart the phone it will stay in windows... If I restart then I lose it for a day or so. Interesting to note that since this has happened, phone calls connect, but I can't hear the other party and they can't hear me.
Also, I use the mini usb out to a 3.5mm stereo jack to stream shoutcast into my car stereo while driving. Last week (at the onset of my problem) the music was playing from the Tilt's speakerphone, and not going through the headphone jack as it normally would. A restart fixed this, but when it happened again a day or so later, the next restart is what got me to that boot screen for the first time.
One of us should post this in the forum...
Click to expand...
Click to collapse
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse
dockular said:
this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse
Umm... GOOD FOR YOU!!!
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse
dude i wasn't telling him to not follow your advice. was just letting him know my story. as a matter of fact, after reading your original post I have decided to check for bad blocks on my phone.
GSLEON3;2021681
[B said:
Umm... GOOD FOR YOU!!![/B]
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse
Well, this has happened to one of our phones. Can you just post the fix here instead of requiring the email/IM rotuine?
Hello all,
Firstly, I hope this is the right place to put this thread. I did a search and did not find anyone else having this issue so I decided to put my post here. I am having a problem with my note 4 randomly restarting a few times every hour. It goes through its shutdown procedure and turns right back on. Occasionally it will shutdown and stay off. It seems to be software related, but I'm no expert on these things. I did however download 'Device Temperature' from the play store to check to see if it might be overheating. As far as I can tell it has stayed a cool 24-25 degrees Celsius (77 Fahrenheit) the entire time.
It does this at unpredictable times, whether or not the phone is in my pocket, in my hands, or laying flat on a desk with or without the charger plugged in.
I don't think I can take it back to Tmobile to have it replaced as I bought it from a friend a few weeks ago to use on cricket. This just started 2 days ago.
The device is SIM unlocked, but not rooted with stock everything. It's still in mint condition and to my knowledge has never been dropped.
Can anyone help?
More Information
I did a Google search for "Galaxy Note 4 Random Reboot" and I found some information saying to reformat my SD card or try doing a factory reset on the phone.
I tried both (I actually removed the SD card completely instead of just reformating it), and about a half hour later... boom restart again. FML.
Once again I turn to the wonderful folks at XDA for help. Thanks to all in advance.
Sounds like it could be bad eMMC flash memory. Go with your friend and have Tmobile replace it. Also get Square Trade insurance if you can.
Got it fixed
I called Samsung about the issue and after some brief troubleshooting they recommended having it reflashed at a samsung experience center. The closest one to me was in a Best Buy. I dropped it off, after explaining what was happening, and an hour later it was ready to be picked working good as new. I haven't noticed it restart even once since.
Samsung offered to replace the entire unit but it would cost me $28 for 2 day shipping (assuming that they had my model in stock). I will go that route if the issue returns. I'm hoping not to go this route because I already paid for this phone to be unlocked once - I'd rather not pay again if I don't have to.
I'll keep you guys updated if the rebooting issue returns again.
Also check to make sure the battery is properly seated and contacts are not bent/damaged.
railshot said:
Also check to make sure the battery is properly seated and contacts are not bent/damaged.
Click to expand...
Click to collapse
This. I kept having this issue with my Note 3 and could not figure it out. Eventually I just took out the battery, cleaned the contacts, put it back in, and it never had a random reboot after that.
Are you guys running any custom roms, or is it still stock?
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
quaxer said:
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
Click to expand...
Click to collapse
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
bothgoodandbad said:
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
Click to expand...
Click to collapse
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
Thanks, hopefully your info helps someone help you better or hopefully it can help/spark someone truly seasoned in android/moto x etc to chime in
To check your manufacture date boot into your fastboot menu, check image to verify you're there.
Then choose BP Tools and then once that menu loads choose the option for UPC/Manufacture date read out, check for the date when it appears on the screen, maybe you are on a batch that has specific issues.
I've never heard of this issue, yuk sounds terrible. Goodluck! If you do end up finding answers somewhere else can you please come back here and post the resolution?
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
maybe static electricity?
or do you use any cases?
maybe wrong charger?
Multiple devices, different Android versions, Sounds like an app issue to me.
If it happens frequently, then that is good in a way... You could factory reset and don't install a single app. If it doesn't act up for a couple days ..... Install about 5 apps. Go a couple days.... Install 5 more, etc... Etc. When it starts to act up, you know it's an app you recently installed, so it'll be easier to narrow down.
A logcat could help too. Search on that for how. It would likely show what happened at the time of the reboot /shutdown.
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
quaxer said:
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
Click to expand...
Click to collapse
use the volume +up button (once BP Tools is highlighted) and not the power button to select BP Tools I'm assuming that's what's happening, hmm
I would send it back to Motorola again. If the issues continue, tell them you want it replaced with something else like the 2014 Moto X.
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
quaxer said:
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
Click to expand...
Click to collapse
This thread is awesome.
Also, I recommend leaving your phone on your desk/home/car when you work
Or maybe a full-body armor case or something.
Statics & electronics = bad idea. Even if you can drain it and it works, it's still hurting the components inside.
So, it's been a bit, but I just came back to this phone. I never did send it in to Moto, though it seemed to have died completely. It sat in the drawer for a couple of weeks, and now on a whim I plugged it into my computer, and it started up! I had never tried plugging it into a computer, just chargers...
BUT,
In the last 10 minutes it's been sitting here rebooting itself every 2 minutes... I guess I'll try wiping it again (It didn't do the trick last time), but this phone has serious problems.
Hi , ive done all i can before coming here for help but this is my last resort as im stumped. About a month ago i updated my phone to the latest Android version on my Nexus 6. Literally straight after the update my phone began to play up. It started turning itself off at random times , not when i did a specific thing it could be anything and at any time. Spoke to Motorola and they were no use , so cleared my phone did a reset and still the same occurrence, as it was still on the newest version. But what i found was when the phone was plugged into the mains it didn't go off at all, but then again this problem happened right after the update. SO the next thing i have done is custom ROM but again the device will turn off randomly .I really need help as ive only had this phone since January and ive not been able to use it.
Thanks in advance
Sounds like battery defect. Has same issue on my n4 with regards to being ok when plugged in
Sent from my Nexus 6 using Tapatalk
benthebratt said:
Hi , ive done all i can before coming here for help but this is my last resort as im stumped. About a month ago i updated my phone to the latest Android version on my Nexus 6. Literally straight after the update my phone began to play up. It started turning itself off at random times , not when i did a specific thing it could be anything and at any time. Spoke to Motorola and they were no use , so cleared my phone did a reset and still the same occurrence, as it was still on the newest version. But what i found was when the phone was plugged into the mains it didn't go off at all, but then again this problem happened right after the update. SO the next thing i have done is custom ROM but again the device will turn off randomly .I really need help as ive only had this phone since January and ive not been able to use it.
Thanks in advance
Click to expand...
Click to collapse
Yes, absolutely sounds like the battery issue that is somewhat common. Best to RMA at this point because the next step is that the battery starts to expand.
You can, in the meantime, boot into bootloader, and select bootloader logs. Press power to select and then reboot. This clears and calibrates the battery stats. Most likely, the issue will return.
Evolution_Tech said:
Yes, absolutely sounds like the battery issue that is somewhat common. Best to RMA at this point because the next step is that the battery starts to expand.
You can, in the meantime, boot into bootloader, and select bootloader logs. Press power to select and then reboot. This clears and calibrates the battery stats. Most likely, the issue will return.
Click to expand...
Click to collapse
Thanks for the reply, what does RMA mean ? ive done that calibrating but didnt turn on . Also i spoke to Motorola and they said as i have a cracked screen they will have to replace that before reparining costing £120
benthebratt said:
Thanks for the reply, what does RMA mean ? ive done that calibrating but didnt turn on . Also i spoke to Motorola and they said as i have a cracked screen they will have to replace that before reparining costing £120
Click to expand...
Click to collapse
Return merchandise authorization.
I've had it since Saturday and so far its done it 3 times.
Once yesterday just when I was trying to open the phone with the fingerprint sensor and twice now today when trying to do something with the phone connected to Bluetooth.
This morning I was trying to set up the connection to my in car TomTom Toyota 2 unit for the first time. Got part way through the process then it failed then when i tried again the phone rebooted then it worked.
This afternoon I turned on my Bluetooth connected to the car but it wouldn't do anything then the phone froze and rebooted but then it all worked fine.
I'm not giving up yet but its making me a bit nervous having these issues so soon (better now than later i guess). If it happens more this week ill take it back and might see about a different phone.
Just curious if anyone else has had similar?
This Bluetooth device worked fine previously with my Nexus 5X also on Oreo so its fine software compatibility wise.
Oblox said:
Just curious if anyone else has had similar?
Click to expand...
Click to collapse
I haven't, and I use BT in the car everyday.
Thanks. I'll see if it happens again this week and take mine back if so.
No, I haven't had a single reboot in the 6 days that I own the device.
Oblox said:
I've had it since Saturday and so far its done it 3 times.
Once yesterday just when I was trying to open the phone with the fingerprint sensor and twice now today when trying to do something with the phone connected to Bluetooth.
This morning I was trying to set up the connection to my in car TomTom Toyota 2 unit for the first time. Got part way through the process then it failed then when i tried again the phone rebooted then it worked.
This afternoon I turned on my Bluetooth connected to the car but it wouldn't do anything then the phone froze and rebooted but then it all worked fine.
I'm not giving up yet but its making me a bit nervous having these issues so soon (better now than later i guess). If it happens more this week ill take it back and might see about a different phone.
Just curious if anyone else has had similar?
This Bluetooth device worked fine previously with my Nexus 5X also on Oreo so its fine software compatibility wise.
Click to expand...
Click to collapse
Have you tried performing a factory reset? It might fix your problem. If it persists, then you can send it back for a replacement.
Rebooted again today just in the camera.
Not tried a factory reset yet, will take it into store today and see what they say is best to do. Don't mind doing a reset but then its waiting again to see if it does it again after which isn't something I can easily replicate.
If i can get a new unit id prefer that so i can see if its just my current one with an issue, even with the pain of having to buy a new screen protector.
Lazaros_K said:
Have you tried performing a factory reset? It might fix your problem. If it persists, then you can send it back for a replacement.
Click to expand...
Click to collapse
If the factory reset doesn't work, install the Sony Companion software and run a software repair on it. That may fix the issue. Mine hasn't restarted at all in the 24 hours I've had it, even after using Wifi, Bluetooth, installing lots of apps, using 3G and 4G... However, I installed Newpipe via F-Doid and it crashed at least 4 times on me when I left the video I was watching and came back to it.
No reboots. Two days of heavy use.
I factory reset it soon as I received it and firware update poped up.
Oblox said:
Not tried a factory reset yet, will take it into store today and see what they say is best to do. Don't mind doing a reset but then its waiting again to see if it does it again after which isn't something I can easily replicate.
Click to expand...
Click to collapse
No reboot, have had phone for over a week now.
What did the store recommend you do? Here, they always suggest you factory reset first, same with going to the service center, they actually do that first thing when you send in for repairs.
What did you eventually do? Did it solve your problem?
mhaha said:
No reboot, have had phone for over a week now.
What did the store recommend you do? Here, they always suggest you factory reset first, same with going to the service center, they actually do that first thing when you send in for repairs.
What did you eventually do? Did it solve your problem?
Click to expand...
Click to collapse
I took it into a store the other day and they had no stock so i'm taking it to a different one today. The store i went to said it would be no problem though as id not had it long. Its been rebooting still a few times just when sitting in my pocket doing nothing, ive had the must enter pin after reboot message.
Well on the way to store speaking to my wife (also with XZ1 compact) her phone froze mid call and rebooted. When she rang back she said she was showing a software update. Checked mine when parked and i had it too.
Sony rep happened to be in store today so told him the issue, he had one himself and hasn't experienced or heard of this but said to do a repair with xperia companion to clean flash the new firmware on both our phones. If still having issues then theres nothing more we could do ourselves and bring back to store to swap.
I have another week in which i can change phone or another 3 weeks to swap for a new XZ1 compact.
Will do repairs tonight and hope the problem goes away.
Repaired friday evening, phone rebooted randomly again after freezing sunday. Taking in today to swap for a new unit.
If any similar problems this week with the new one ill ask to swap to a different phone entirely.
Probably need a software update. Mine is running fine on 47.1.A.2.324
Sent from my G8441 using Tapatalk
No i updated that on friday before repairing and the repair had that version too and it still rebooted sunday and today.
Me and my wife got a new unit now so will see how these ones go.
got my first reboot today after plugging the headphone... weird...
profyler said:
got my first reboot today after plugging the headphone... weird...
Click to expand...
Click to collapse
Not good if others are getting this too, lets hope it was a one off for you.
So far just setup and listened to music on my new phone and all is good but there's no pattern to what causes the reboot so will see how the next few days go.
My XZ1 Compact also has the reboot-issue...
Mine has just done the fourth reboot in just a little more than one week. In different situations, with bluetooth in use and without. Once when I tried to call someone, once when I was searching for wifi networks and the other two times in pretty normal "just using it" situations.
As not everyone is having those issues, I think it is some hardware defect and I need to get the phone replaced, right?
Harry
flyhigh79 said:
Mine has just done the fourth reboot in just a little more than one week. In different situations, with bluetooth in use and without. Once when I tried to call someone, once when I was searching for wifi networks and the other two times in pretty normal "just using it" situations.
As not everyone is having those issues, I think it is some hardware defect and I need to get the phone replaced, right?
Harry
Click to expand...
Click to collapse
Difficult to tell. A hard reset might help but it could also be a problem with Android 8 on xz1 that wasnt very well optimized..
Id get the handset replaced, 'repairing' didn't do anything for my issue. Only time will tell if my new handset has the same issues and same for you.
Well this morning I got in the car to go to work and went to turn on bluetooth. Tried OK google no response at all, went to manually unlock and it sat on the lock screen my finger prints not working and wouldnt swipe up for PIN entry. Mic and camera toggle reacted to swipes but didnt do anything. Then it rebooted.
Bye bye Xperia XZ1 Compact, the potential was there but rebooting and dodgy camera is too much to hope for a fix for.