Database Develop

[Q] Why my Galaxy S locks up?! (Comatose Syndrome on going investigation)

Hi Guys,
Could someone tell me why my 2 weeks old Galaxy S (Service Provider: Bell) turns it self off out of the blue?
It happend twice already, the phone was on my pocket, I pushed the on/off side botton and nothing happens, the screen is pitch black!!
This is an irritating issue as I'm forced to physically take out the phone from the case and remove the battery and put it back on to turn on the phone.
Does anybody whats causing this issue? and how to fix it ?
Your help is much appreciated!
Cheers

Also, I was wondering if I do a factory reset to try solving the random shutting down problem, will I have to re-purchase all the apps I bought from the Market?

Send for warranty is needed I think
Sent from my GT-I9000 using XDA App

Essayli said:
Also, I was wondering if I do a factory reset to try solving the random shutting down problem, will I have to re-purchase all the apps I bought from the Market?
Click to expand...
Click to collapse
No, the info that you purchased the apps is stored in your Google account. So if you use the same Google account as you're using now as your primary account after reset, you can download all those apps for free. (Primary account is the Google account you first associated with the device.)

i had the same problem with 3 different bell vibrants. About 6 days ago, i bought a new sim card from bell for $5, and it has not happened since. I bought my phone from Bestbuy, but bought my new sim card from Bell store because perhaps the bestbuy sim cards are outdated. Hopefully it stays ok.
One thing i did notice was that when my phone would turn off by itself, it was always in an area where there was bad reception. Maybe a link.

I found that it happened when I installed a different launcher other than Touchwiz. I was using LauncherPro, uninstalled it and everything worked fine. I installed ADW and everything is fine so far.

I saw this thread yesterday and was thankful mine hadn't developed this issue. And then last night after about two hours idle time, my SGS switched itself off and the power button wouldn't respond at all. The only way to revive my beloved phone was to do a hard reset (i.e. removing the battery).
For what it's worth, the only "mods" I've made are installing a handful of apps. No new launcher, no custom ROMs etc.
I'm tempted to give Voda a ring and ask for a new SIM. But this really smells more like a hardware fault to me. A faulty SIM shouldn't result in a handset switching itself off, I'd think...

i'v encountered smailar problem , first i thought my phone turned itself off, later i suspected some apps i'v installed ( setCPU, autokiller etc), after while and digging, i found that i'v installed "Android Tweak" , it has an option to disable screen dim, and i'v used that option, so i changed it back and the problem is gone.

in Spain we have the same problem and no solution by now
http://www.htcmania.com/showthread.php?t=126937

Same thing happened to me last night. Maybe a bug with the date?

Rc-Blob said:
Same thing happened to me last night. Maybe a bug with the date?
Click to expand...
Click to collapse
Mine just died again ten minutes ago. I guess it's a possibility, but considering the number of bugs that we're all discovering with the hardware and software, I'm suspecting it's yet another dodgy batch of phones from Samsung.

I just bought two Galaxy S and I am having same problems with both. I called Belll and they said they never had this kind of problem before. I had installed few apps and thought may be those apps were causing the problem, but even after deleting the apps..phones are powering off itself...
Did any one find the solution yet??

Same problem here, and from what i am hearing is becoming frecuent among galaxy owners. Im amazed something this important hasnt made the news , i mean, its a huge malfunction issue .

I had the same issue.
I called up Samsung support and they asked me to do a phone reset. I didn't try that, but I upgraded the firmware and it's gone now. I suspect resetting the phone will also solve the issue.

This happened to me for the first time today as I woke up and it wasn't dark outside. When I looked to see what time it was my phone (that I use as an alarm) was off!!
This is the first blemish on an otherwise outstanding experience. But it is a major one. I will assume that it is somehow related to something I've installed. But I'm not looking forward to figuring it out, since I've got a lot of apps

lockpick said:
This happened to me for the first time today as I woke up and it wasn't dark outside. When I looked to see what time it was my phone (that I use as an alarm) was off!!
This is the first blemish on an otherwise outstanding experience. But it is a major one. I will assume that it is somehow related to something I've installed. But I'm not looking forward to figuring it out, since I've got a lot of apps
Click to expand...
Click to collapse
Good luck. I did a factory restore the other day to see if that would help. It didn't. Like you I use my SGS as an alarm... I woke up two hours late this morning because my phone had switched itself off in the middle of the night.
I'm currently waiting for a replacement handset. I'm not holding my breath that the new hardware won't have exactly the same bug though...

Mine started doing this yesterday...same with a bunch of coworkers that have the same phone. We think it may be related to bad reception.

Sigh
My phone just started doing this in the last couple of days.
I've also noticed sometimes it gets into a state of continuously saying "usb debugging connected" and then "usb connected" and just continuously keeps displaying those even though it has no usb cable anywhere near it..
Havent flashed the phone for about a week now and it was fine for 3-4 days after the flash so no idea what is going on..
Anyone else seen those usb messages? They come and go.. but it seems when they come its usually when my phone turns off..

Kilack said:
Sigh
My phone just started doing this in the last couple of days.
I've also noticed sometimes it gets into a state of continuously saying "usb debugging connected" and then "usb connected" and just continuously keeps displaying those even though it has no usb cable anywhere near it..
Havent flashed the phone for about a week now and it was fine for 3-4 days after the flash so no idea what is going on..
Anyone else seen those usb messages? They come and go.. but it seems when they come its usually when my phone turns off..
Click to expand...
Click to collapse
I've not seen anything like that myself but then I have stuck with stock firmware.

robbiev80 said:
Mine started doing this yesterday...same with a bunch of coworkers that have the same phone. We think it may be related to bad reception.
Click to expand...
Click to collapse
Thats funny...because the only time it has happened to me is at work, where the phone is struggling for reception. It has turned off a total of about 8 times over 1 month. It has never turned off anywhere else (except one other time i was getting bad reception in the forest, and a few minutes later it was off)...strange

[Q] Recurring wifi error

I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?

seventieslord said:
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
Click to expand...
Click to collapse
I would sbf and stay on stock, if it reappears, bring it to verizon. Im afraid I've never heard of this problem before. Since it happened with 2 separate roms, it seems more like hardware. Otherwise the sbf should have fixed it.
Sent from my XT860 using xda premium

Odd. I know that this was a problem on most ICS roms. Haven't heard of it happening on a GB rom. This happens to me on Gummy 1.2. Same symptopms: wifi kills with no cause and no pattern. I toggle airplane and keep browsing as I only turn on wifi when I am actively using it.
Sent from my DROID3 using xda premium

[Q] A very strange rebooting problem.

Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.

Kirbs82 said:
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Click to expand...
Click to collapse
No one? I guess this really is a tough one.

Kirbs82 said:
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Click to expand...
Click to collapse
Sorry to hear about this man!
I am completely stumped on this one! You've basically done all the basic solutions but to no avail. I had a problem similar to this where my device would reboot randomly, whenever it wanted to and in my case, the solution was to buy a new battery and that actually worked. I've had the battery for almost 2/3 months now and it's still going strong.
Back to your problem, I honestly don't know of a solution. I really wish I could be of help but as I said, you've already tried the basic solutions.
Again, sorry to not be of much help!

Sn0wdune said:
Sorry to hear about this man!
I am completely stumped on this one! You've basically done all the basic solutions but to no avail. I had a problem similar to this where my device would reboot randomly, whenever it wanted to and in my case, the solution was to buy a new battery and that actually worked. I've had the battery for almost 2/3 months now and it's still going strong.
Back to your problem, I honestly don't know of a solution. I really wish I could be of help but as I said, you've already tried the basic solutions.
Again, sorry to not be of much help!
Click to expand...
Click to collapse
I think I have the same problem as you did. After suddenly dropping and rebooting, my battery level jumps back up when the phone starts, and again, and again. The phone is functioning normally only when plugged in. I also presume that it is a battery problem, but the fact that the battery level rises back after dropping, makes me wonder.
EDIT: Problem solved with buying a new battery.

Sorry to jump in, just curious, did you solved this? If you do, hope to hear your solution, might help others in future
SGs3n SlimKat9.0(Android-Andi)

[Q] Hard briked S3 mini out of nowhere

I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.

ScrewedImei said:
I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.
Click to expand...
Click to collapse
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.

Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030

bejunk said:
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.
Click to expand...
Click to collapse
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
CrashOverride93 said:
Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers

ScrewedImei said:
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers
Click to expand...
Click to collapse
this guide useless for you. how u want flash things with odin if u cant enter download mode at all??
im really sorry for you that this phone is dead. just can give you 1 advice, dont buy samsung in future.

I have been repaired my phone successfully!!!
I just needed to change two capacitors on its motherboard, and that's it.
Here the video where I have found the info and how to do that. It's in Spanish but easy to understand for you I think. But if you need some help, send me a PM.

can you take a picture from the location of the 2 capasitors and the types of it

Hi everyone.
I have some news. It took me a while but I followed CrashOverride93's advice on that video. It actually solved one issue, as I now can turn it on, but now I have a second problem, I'm stuck on a boot loop, with acess to Download mode ONLY. No recovery.
Considering where my issue started, and where I am now, I have tried the following:
- Flashed via Odin stock ROM, kernel;
- flashed Wipe;
- flashed PARAM;
- three button combo.
So far I couldn't get it pass the boot loop. Any thoughts?

Anyone had their Xz1 compact reboot itself?

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.