Related
Hello all!
I have noticed that recently, my phone has been doing a very odd thing while charging. When it has been plugged in for a little while, and the screen is on and in use, sometimes the phone will crash. When it crashes in this manner, the backlight on the screen is turned on on full brightness, the screen gets a yellowish hue, and horizontal black bars start appearing on the screen. More black bars keep appearing until I reset the phone (hold the power button), and then there is no evidence of any screen problems. I also generally have to unplug it for a while, as if this happens once, it generally happens multiple times until I unplug the phone and wait. These problems seem to be occurring at odd times (a lot at night, before I am going to sleep), and have just started happening (I also recently made the upgrade from the latest version of GB to 4.0.4). I have had this device for about a year now (the second device, the first one had a physical design flaw and was replaced), and I am out of warranty right now, so any help would be appreciated!
a_p3rson said:
Hello all!
I have noticed that recently, my phone has been doing a very odd thing while charging. When it has been plugged in for a little while, and the screen is on and in use, sometimes the phone will crash. When it crashes in this manner, the backlight on the screen is turned on on full brightness, the screen gets a yellowish hue, and horizontal black bars start appearing on the screen. More black bars keep appearing until I reset the phone (hold the power button), and then there is no evidence of any screen problems. I also generally have to unplug it for a while, as if this happens once, it generally happens multiple times until I unplug the phone and wait. These problems seem to be occurring at odd times (a lot at night, before I am going to sleep), and have just started happening (I also recently made the upgrade from the latest version of GB to 4.0.4). I have had this device for about a year now (the second device, the first one had a physical design flaw and was replaced), and I am out of warranty right now, so any help would be appreciated!
Click to expand...
Click to collapse
That was happening to me (for a weird reason, my devicewas new, its seems that problem is more common in the rogers version dont know why) but, if your problem is the same problem that i had, then, just install stock ICS with oneclick (dont remember the name very well)
lorddavid said:
That was happening to me (for a weird reason, my devicewas new, its seems that problem is more common in the rogers version dont know why) but, if your problem is the same problem that i had, then, just install stock ICS with oneclick (dont remember the name very well)
Click to expand...
Click to collapse
Superoneclick? That's the closest I found, and it doesn't say that it supports the Glide. And, I am running a fully stock version of 4.0.4, unrooted and everything. I might need a little more help here, haha.
I mean, oneclick, is the firmware,and is about 700 mb, give me amoment a will search it
EDit: i found it: http://www.androidauthority.com/captivate-glide-sgh-i927-att-android-4-0-4-ics-uclg9-leak-110365/
I use that, when I install it, that problem gone away, try it. And then, you can flash the custom recovery and install custom roms
lorddavid said:
I mean, oneclick, is the firmware,and is about 700 mb, give me amoment a will search it
EDit: i found it: http://www.androidauthority.com/captivate-glide-sgh-i927-att-android-4-0-4-ics-uclg9-leak-110365/
I use that, when I install it, that problem gone away, try it. And then, you can flash the custom recovery and install custom roms
Click to expand...
Click to collapse
Isn't that a different version though? The build number on that is UCLG9, not UCKJ3 (which is what I have right now).
I am not sure, but, if with that your problem persist, maybe is hardware, but I only do that. When I did it, that was the latest version, now there is another version but not sure what is it
I was having the same problem, except it was happening frequently after my phone had warmed up due to normal use. If the phone was already hot it wouldn't even get past the splash screen.
I put it down to hardware fault, and was successful in getting it replaced under warranty. The new one has been totally fine.
Hopefully yours isn't a hardware issue - but from how it sounds it very well could be
davidpartay said:
I was having the same problem, except it was happening frequently after my phone had warmed up due to normal use. If the phone was already hot it wouldn't even get past the splash screen.
I put it down to hardware fault, and was successful in getting it replaced under warranty. The new one has been totally fine.
Hopefully yours isn't a hardware issue - but from how it sounds it very well could be
Click to expand...
Click to collapse
I really was hoping it was a OS issue, as it hadn't ever done this on GB. If I flash a new rom then, it would be fixed?
Also, I too noticed that my phone is abnormally warm when it does this. I do have a cover on my phone, but I noticed that it seems to be centered about on the horizontal center of the phone, about a half-inch below the camera. If this is related, what do you think it is?
My phone did this as well. Luckily it happened just before I rooted. The att guys said it was a hardware fault and that fault also killed my battery. I'm assuming it was a short. It started as something infrequent, but it eventually escalated to the point the second I turned it on my screen turned completely green and got really hot.
Exxon02 said:
My phone did this as well. Luckily it happened just before I rooted. The att guys said it was a hardware fault and that fault also killed my battery. I'm assuming it was a short. It started as something infrequent, but it eventually escalated to the point the second I turned it on my screen turned completely green and got really hot.
Click to expand...
Click to collapse
Just great, a possible hardware problem while out of warranty. Did yours do it only when charging as well?
a_p3rson said:
Just great, a possible hardware problem while out of warranty. Did yours do it only when charging as well?
Click to expand...
Click to collapse
Didn't have to be charging to do it. Could have been on the street holding it. (I was on GB as well)
Exxon02 said:
Didn't have to be charging to do it. Could have been on the street holding it. (I was on GB as well)
Click to expand...
Click to collapse
Your issue sounds similar, but slightly different. Mine only happens while I am charging it, and it has only done it since a while after I made the upgrade to 4.0.4. Although, they sound similar, and my phone also gets concerningly warm, so I have no idea if it is the same thing or not...
If it's out of warranty, then you have nothing to lose by doing a backup and a clean ROM installation, which is what I would do. I guess if you do it when fully charged and while the phone is cold you should be fairly safe, especially if you use a small ROM. I've found the latest M3 10.1 ROM installs fairly quickly, so that might be worth a shot even just to see if it fixes the problem.
The only risk you're taking is that the phone might die and get bricked in the process if it's a hardware fault, so I guess it's really your call.
EDIT: On that thought, perhaps experiment with seeing if you can charge after leaving it in the fridge for about 15 minutes? It's a trick we used to use to recover data from failing hard drives, if you get them cold enough they can work for long enough to get away with things
davidpartay said:
On that thought, perhaps experiment with seeing if you can charge after leaving it in the fridge for about 15 minutes? It's a trick we used to use to recover data from failing hard drives, if you get them cold enough they can work for long enough to get away with things
Click to expand...
Click to collapse
I like that idea, as it should fix the overheating issue. However, the times that it actually has this malady aren't regular - it seems to happen more at night, but not every night. I could try putting it in the freezer when it does it though, and see if it works. If it is overheating, could it be a hardware issue then? I also noticed that my battery that I have in my phone does appear to have a slight dent near the bottom, and it is only happening when it is charging, so I am wondering if it could be a problem with the battery? When I pull the battery out after it has done this, the battery itself isn't that warm, but the phone is, so I'm thinking it isn't the battery, but does anyone else have any ideas?
I just got this tablet (to replace the garbage SGH-I467) a few days ago (Thu., May 15th). For the first couple of days it worked like a dream. However, the last 4 nights/3 days, I have been encountering some strange issues. What I will do here is describe the issues I've been having, what I have done in attempts to fix them, list some of the things I think may have caused it, and include any additional info/questions.
Before all that though, I would like to mention that I am not a developer, but I am a bit 'tech savvy' and am more familiar with/knowledgeable of technology than the average user. Also, I have spoken with Samsung tech support and even had the support guy access my Tab Pro 12.2 remotely (I will explain what I learned from that below). So, without further ado (I apologize in advance for the long winded nature of this post, but I want detailed):
The Issues:
1) Screen "flickering"—By flickering I mean that it is shutting off and turning on rather rapidly and sporadically, though inconsistently.
I first encountered the problem 3 days ago (the 18th).
Four nights ago (the 17th), before going to bed, I plugged the device into the same outlet I have used for all my mobile devices, when I woke up (on the 18th) the screen was doing exactly what I described. I hit the home button a few times and it stopped.
That night (the 18th) I plugged it back in to the usual spot before going to bed. The next morning (yesterday, the 19th), the screen was "flickering" again. I tried to press the home key a few times, as well as both the soft keys, nothing. In between "flickers" you can see the lock screen, where I have to enter a pin, but even while visible I can't type anything. So this time, to try to solve the problem, I held the power button + volume up to get to recovery and wiped the cache partition, rebooted the device, and viola, it worked again. Thinking that I may have to factory reset the device if the problem persists, I used Kies to backup all my data. I used the tablet the rest of the day, even plugged it in (in a different outlet than the one next to my bed) for a while and had no issues.
Last night (the 19th) I did pretty much the same thing, but this time, thinking that it might be an issue with the device getting too much power (the Quick Start Guide says: "Note: Connecting the travel adapter improperly may cause serious damage to the device."), I used a travel adapter from one of my other, USB 2.0 devices (the only difference between the adapters is the output: 2.0 = 5.0V—2.0A vs. 3.0 = 5.3V—2.0A, and output was specifically what I was concerned with). This morning (the 20th) the problem has returned, but now includes my second issue: the hard home button and both soft keys, back and recent apps, no longer function. So I immediately tried to wipe the cache partition and reboot, but this time it didn't work. Thankfully I had anticipated this yesterday and had that Kies backup, so I wiped the entire device back to factory settings. But alas, it was unsuccessful and the problem persists, including the loss of button functionality, with the exception of the power and volume buttons.
It is important to note that when I first got the Tab Pro 12.2 and set up the lock screen, I used the option that delays the actual locking of the device 10 minutes after screen timeout, but set it so that if I lock the screen with the power button it ISN'T delayed and immediately locks. That being said, a couple of times when the "flickering" stopped long enough to momentarily use the device, I was able to enter my pin and unlock. But when the screen starts flickering again, it locks the device, so the power button must be affected as well. Though since the first factory reset of the device, I haven't set up a pin. I have done several factory resets and none of them have worked. The best result has simply been limited (no back, recent apps or home key) and momentary functionality. I tried using Kies to do emergency firmware recovery, but every time I click the option it disconnects the device.
When Samsung tech support remotely accessed by device (I used one of the momentary functionality windows to download the required application) the agent was able to utilized soft and home key functionality, even though I couldn't. This tells me that it was hardware related, not related to UI/software.
So there are a couple of things I think may have caused/contributed to the problem:
The first, which I vaguely touched on above, is the power issue. Perhaps I have shorted the device out somehow. The outlet I use to charge things while I'm sleeping is on the wall behind my bed, so I have to use a common extension cord, one that has 3 outlets at the end. I have a light plugged into that and in the past have charged both my SGH-I467 (AT&T Note 8.0) and my SGH-I747 (AT&T S4 Active) with that cord and outlet. That is the only place I have charged the SM-T900 overnight, but none of the other power sources I have used have caused these issues.
The second possibility is a virus some sort. I have never used the Samsung app store on any of my other devices, but in order to update the Hancom Office suite I had to. Since I had an enjoyable time using it to that end, I decided to see what else I could find on Samsung's store. I downloaded a couple of things (the "Official Captain America game" and a couple wallpaper/theme apps) and was looking around the store to see if there was anything else I wanted to download. I found several apps that had reviews claiming they were trojans, so I immediately checked the reviews for the apps I had downloaded, but none of them had similar reviews. However, that does not mean they didn't have viruses.
So, what do the resident Android gurus of XDA think about these issues?
I tried searching all over the forums and elsewhere online for people having the same issues, but couldn't find anything. Have any of you ever encountered something similar to this?
Until recently, I hadn't ever heard of anyone getting a virus on an Android device. Are they common? What is the nature of Android viruses?
If these issues do have something to do with overcharging/shorting the device, how can I mitigate that problem? Tonight when I charge the tablet, instead of using the USB 3.0 charging cable, I am going to try just using the 2.0 cable. As I understand it, that can be done by simply plugging it into the right side of the port. Hopefully that will stop exacerbating the problem.
Again, I apologize for such a long winded post. I would like to thank you all in advance. If ever I have problems with an Android, you guys are the ones to ask!
*UPDATE* Before I started typing this I was attempting to run the Kies 'Firmware Upgrade and Initialization', as opposed to 'Emergency Firmware Recovery', to see if that too would disconnect the device. Unfortunately it said that my device needed to be charged first. So I shut it down and plugged it into a surge protected strip and began typing this post. Occasionally I would go over an check the charge. While it was shut down and charging I was able to use the home key to bring up the green battery. Once the charge looked like it was about 75% complete I turned it back on and lo and behold, the "flickering" issue looks resolved and so does the button issue. I can go back, enter the recent apps and task manager, and use the home key functions. For how long this will last, however, is unknown. I guess we'll see in the morning. I'll post what happens tomorrow.
What kind of case are you using? Some users have seen issues with some cases that use magnets for auto-sleep-wake. When the front of the cover is flipped back behind the tablet, the magnets seem to activate the auto-sleep feature
Sent from my SM-P900 using Tapatalk
RE: Case?
dodo99x said:
What kind of case are you using? Some users have seen issues with some cases that use magnets for auto-sleep-wake. When the front of the cover is flipped back behind the tablet, the magnets seem to activate the auto-sleep feature
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I am not using a case or cover at all...
same issues here
Sounds exactly as the same issue I have had the last week. I have done several factory resets triad to avoid installing as many applications as I had prior the factory reset (to see If it was an app causing the issue). No solution yet but I will try your way with kies described above. I have a tab pro 8.4.
VeinkWiles said:
So, what do the resident Android gurus of XDA think about these issues?
Click to expand...
Click to collapse
I am no guru, but it sounds like a loose connection. Maybe it is affected by temperature. Try it on a (not too) hot water bottle or on freezer packs.
Mike Austin said:
I am no guru, but it sounds like a loose connection. Maybe it is affected by temperature. Try it on a (not too) hot water bottle or on freezer packs.
Click to expand...
Click to collapse
It's not overheating. It can get warm, but it's never gotten hot. And I've had other devices that have seriously overheated and still functioned, albeit slowly.
**UPDATE**
After I got it working the night I originally posted I let it fully charge (it's important to note that I got it up to about 75% while it was off; green battery the only thing on the screen, and I had home button functionality), then disconnected it and disabled all the radios, put it in power saving and left it over night without power. Doing that I was able to use it all day yesterday. But while I was full-charging it, after it reached 100%, I noticed that it started acting up almost immediately. The sound was on and kept making the lock screen sound (that's how I noticed it from across the room). So it is tied to the power/lock key. But disconnecting it before it could get out of control mitigated the problem. Last night I was going to try to charge it over night with USB 2.0, but I fell asleep before changing the cable out, so it charged on 3.0 all night and is back in poor repair. I'm currently trying to full charge it while off to see if that gives me functionality again.
Either way, each time I fix it the solution becomes more difficult/timely than the previous one. It's clearly not getting better, so I'm going to have to send it in to repairs.
Sent from my SAMSUNG-SGH-I537
VeinkWiles said:
It's not overheating. It can get warm, but it's never gotten hot. And I've had other devices that have seriously overheated and still functioned, albeit slowly.
**UPDATE**
After I got it working the night I originally posted I let it fully charge (it's important to note that I got it up to about 75% while it was off; green battery the only thing on the screen, and I had home button functionality), then disconnected it and disabled all the radios, put it in power saving and left it over night without power. Doing that I was able to use it all day yesterday. But while I was full-charging it, after it reached 100%, I noticed that it started acting up almost immediately. The sound was on and kept making the lock screen sound (that's how I noticed it from across the room). So it is tied to the power/lock key. But disconnecting it before it could get out of control mitigated the problem. Last night I was going to try to charge it over night with USB 2.0, but I fell asleep before changing the cable out, so it charged on 3.0 all night and is back in poor repair. I'm currently trying to full charge it while off to see if that gives me functionality again.
Either way, each time I fix it the solution becomes more difficult/timely than the previous one. It's clearly not getting better, so I'm going to have to send it in to repairs.
Sent from my SAMSUNG-SGH-I537
Click to expand...
Click to collapse
Sorta sounds like a screen grounding problem. I had a nexus seven with this issue and the charger seemed to really make it act up. Needless to say I gave that to my wife and bought this. If the digitizer is not grounded properly it will act up.
Turning on developer settings and set it to show touches on screen. See if when charging the screen registers more touches than you are doing.
Sent from my SM-T320 using Tapatalk
Re: developer settings; display touches
dottat said:
Sorta sounds like a screen grounding problem. I had a nexus seven with this issue and the charger seemed to really make it act up. Needless to say I gave that to my wife and bought this. If the digitizer is not grounded properly it will act up.
Turning on developer settings and set it to show touches on screen. See if when charging the screen registers more touches than you are doing.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Damn! That's an outstanding idea! The only downside is that last night I sent the tablet to Samsung's repair department, so I can't test that out. But once I get it back, if the problem persists I will definitely be doing that first. Thanks for the advice dottat.
Fw:Re: developer settings; display touches
mikegbg said:
Sounds exactly as the same issue I have had the last week. I have done several factory resets triad to avoid installing as many applications as I had prior the factory reset (to see If it was an app causing the issue). No solution yet but I will try your way with kies described above. I have a tab pro 8.4.
Click to expand...
Click to collapse
Hey dude, check out dottat's reply. He's got a really good idea that may shed some light on the source of the problem. Unfortunately, I can't try it out. If you do it, let me know how it goes. Maybe you can take some screenshots? Either way, hopefully you can get something out of it.
I was looking and looking for a thread with a similar issue before posting but I had no luck.
My issue is that when I turn off my Note 3 I have a really hard time getting it to boot back up. This happens every time every single time I shut it off. I hold the power button for about a minute with the battery removed to supposedly drain any power as I've read around but that doesn't help. I'm pretty tech savvy and internally the phone looks perfectly fine. The weird thing is that I don't actually have any issues once the phone is up and running to make me think it's a hardware issue. It charges fine, I get data, S pen is fine, no other issues what so ever. I haven't been able to pin point what I'm doing to bring it back but eventually it does end up booting like normal. I try to pull the battery multiple times with no success. I eventually get frustrated and just leave it alone with the battery removed. When I return it boots up just fine.
Anybody else having this issue or heard of it?
Forgot to mention that the phone is stock. I don't have it rooted or a custom rom installed.
Thats weird. Have you tried reseating the SD card. Sometimes it might bethe memory card.
Why turn it off?
Just let it sleep. I can't remember when I ever turned my phone off.
Pp.
steve_togo said:
Thats weird. Have you tried reseating the SD card. Sometimes it might bethe memory card.
Click to expand...
Click to collapse
I have indeed. I was thinking it was that but it occurs either way.
PanchoPlanet said:
Why turn it off?
Just let it sleep. I can't remember when I ever turned my phone off.
Pp.
Click to expand...
Click to collapse
Well my phone's back camera was broken and I was replacing it. Although the issue started occurring well before replacing the camera.
Im having same issue. Replaces camera now phone wont turn on. shows chargering though.
yotaking said:
Im having same issue. Replaces camera now phone wont turn on. shows chargering though.
Click to expand...
Click to collapse
I noticed you also have a thread which states the same thing and I'm not sure if you figured it out yet, but just out of curiosity did you happen to ground yourself while you were working on your Note 3? This goes for any device in general but it's pretty amazing how much damage the static electricity from just your clothes can cause if you're not grounded while working with an exposed main board. If you weren't grounded while working on it though it also doesn't mean that something automatically happened, I'm just saying it's always a possibility at least. One thing I would try if you're having problems powering it up even just in general, is to make sure it's plugged in and charging first and then hold the volume up and power buttons down together at the same time (and keep them held down) until you feel a vibration and then let go. It will take at least 10 - 15 full seconds (and sometimes even longer) to happen, but that should usually get it to power it up whenever it's being stubborn. Another thing I'd definitely check, especially if it was working fine before disassembling the phone, is the alignment of the power button itself (the button you press with your finger) and the actual power button which is located behind it on a data ribbon that connects to the main board. It's actually kind of a flimsy setup so whenever you reinstall the back frame plate you have to make sure the power button data ribbon doesn't shift, or it can cause all kinds of weird problems when trying to power on or off the phone. Anyway good luck and hopefully this helps [emoji106] [emoji106]
Sent from a modified ColecoVision
---------- Post added at 04:07 AM ---------- Previous post was at 03:47 AM ----------
MexicanGeekian said:
I was looking and looking for a thread with a similar issue before posting but I had no luck.
My issue is that when I turn off my Note 3 I have a really hard time getting it to boot back up. This happens every time every single time I shut it off. I hold the power button for about a minute with the battery removed to supposedly drain any power as I've read around but that doesn't help. I'm pretty tech savvy and internally the phone looks perfectly fine. The weird thing is that I don't actually have any issues once the phone is up and running to make me think it's a hardware issue. It charges fine, I get data, S pen is fine, no other issues what so ever. I haven't been able to pin point what I'm doing to bring it back but eventually it does end up booting like normal. I try to pull the battery multiple times with no success. I eventually get frustrated and just leave it alone with the battery removed. When I return it boots up just fine.
Anybody else having this issue or heard of it?
Forgot to mention that the phone is stock. I don't have it rooted or a custom rom installed.
Click to expand...
Click to collapse
I just mentioned this in my response to someone else in this thread, but it actually sounds like yours has the same kind of alignment issue with power button that I was talking about. I'm not sure if you've ever disassembled yours for any reason or not, but even if you haven't it's still totally possible that it could've happened from the factory and especially if you got a refurbished phone for whatever reason. It's a pretty poor design choice in my opinion because it's such a "fragile" setup, and even the slightest misalignment of the power button itself and the button on the data ribbon can cause the exact same problems your having. Anyway if if you haven't messed with it and it's still under warranty I'd say just get a new one, but if you have taken it apart I'd say first thing to check would be the alignment of those buttons (once you take the back off). I've even had to make a tiny little "shim" and wedge it behind the power button on the data ribbon in order to get it to line up right with the button itself a couple of times, so I'd say it's a fairly common problem with these phones. Anyway good luck and hope it helps! [emoji106] [emoji106]
Sent from a modified ColecoVision
So something quite unfortunate happened to me last night. I factory reset my watch since I installed a new rom on my Moto G, and ever since I did that, the screen is black. Nothing else. The power button isn't doing anything regardless of how long I hold it in or whatnot, and it's just not doing anything, it's a brick. It's not rooted or boot loader unlocked or anything either. When it place it on the charging dock though, the light at the bottom of the dock lights up so I know it's charging at least, but I just really don't know what happened to it. Do you guys think it's toast?
--Edit--
So I spoke to Motorola's live assistance, and if this issue arises for anyone else, hold the power button down for about 2-3 minutes and it should boot into the bootloader, from there you can either attempt a fastboot reboot command or a normal powerup.
I tried your solution. But nothing happened. I think i have the same problem. Mine won't show anything, but when i tried charging, the light on the dock light up. Do you have any other solution? Thanks
fireball0093 said:
So something quite unfortunate happened to me last night. I factory reset my watch since I installed a new rom on my Moto G, and ever since I did that, the screen is black. Nothing else. The power button isn't doing anything regardless of how long I hold it in or whatnot, and it's just not doing anything, it's a brick. It's not rooted or boot loader unlocked or anything either. When it place it on the charging dock though, the light at the bottom of the dock lights up so I know it's charging at least, but I just really don't know what happened to it. Do you guys think it's toast?
--Edit--
So I spoke to Motorola's live assistance, and if this issue arises for anyone else, hold the power button down for about 2-3 minutes and it should boot into the bootloader, from there you can either attempt a fastboot reboot command or a normal powerup.
Click to expand...
Click to collapse
Raging_Ken said:
I tried your solution. But nothing happened. I think i have the same problem. Mine won't show anything, but when i tried charging, the light on the dock light up. Do you have any other solution? Thanks
Click to expand...
Click to collapse
I'm experiencing the issue. And my situation is same as @Raging_Ken. Is there any alternative way to manual/force restart? Since we only have 1 physical button. :crying:
presario3839 said:
I'm experiencing the issue. And my situation is same as @Raging_Ken. Is there any alternative way to manual/force restart? Since we only have 1 physical button. :crying:
Click to expand...
Click to collapse
Anybody got solutions? At this point, i have no problem for paying for replacement, the problem is i got mine from USA, and i'm from Indonesia. Huff
Raging_Ken said:
Anybody got solutions? At this point, i have no problem for paying for replacement, the problem is i got mine from USA, and i'm from Indonesia. Huff
Click to expand...
Click to collapse
Hi @Raging_Ken ! We're at the same boat. Do you any friend that have same situation as ours?
@presario3839
You also got yours from the states? I only know one other people who use the moto 360 and he also got it from the US. I'll check with him tomorrow. Can you check how much will it cost to ask for a replacement in Malaysia? Going there on middle of May, if it's cheaper, i'd rather pay the replacement there. Hehehe
presario3839 said:
I'm experiencing the issue. And my situation is same as @Raging_Ken. Is there any alternative way to manual/force restart? Since we only have 1 physical button. :crying:
Click to expand...
Click to collapse
I know it took a few tries for it to do that but at the same rate if you've tried it a few times then that's quite odd, It's also quite a pain how there's just one button to do it with. Hopefully you get it fixed, I really don't have too much else advice sadly D:
fireball0093 said:
I know it took a few tries for it to do that but at the same rate if you've tried it a few times then that's quite odd, It's also quite a pain how there's just one button to do it with. Hopefully you get it fixed, I really don't have too much else advice sadly D:
Click to expand...
Click to collapse
I just found out that motorola doesn't have any service center in South East Asia, hence we'rwe're screw. Unless somebody in this forum has an answer that can help us, the best that we can do is put it as an ornament in the bed. Huff. @presario3839
fireball0093 said:
I know it took a few tries for it to do that but at the same rate if you've tried it a few times then that's quite odd, It's also quite a pain how there's just one button to do it with. Hopefully you get it fixed, I really don't have too much else advice sadly D:
Click to expand...
Click to collapse
Raging_Ken said:
I just found out that motorola doesn't have any service center in South East Asia, hence we'rwe're screw. Unless somebody in this forum has an answer that can help us, the best that we can do is put it as an ornament in the bed. Huff. @presario3839
Click to expand...
Click to collapse
:crying: we're doomed! any acquaintance you have in this forum? Anyone can help us? @fireball0093 maybe?
I think there can be three reasons for the black screen.
1. The watch has hung and needs the 2-3 minute bottom press as posted by the OP.
2. You use Watchface or Watchface Pro like myself. It has occasionally crashed on me. After several taps, I eventually have the menu come up and can get to settings/reset. I then have the default Moto face and can reselect Watchface. Hope this bug is fixed soon.
3. Hardware failure. LCD displays have a single backlight and if it fails so does the display.
I hope it's either #1 or 2 that you are running into.
this happens to me whene android wear crashes on the watch. i was able to notice the force close notification before it went to a black screen and did not respond until the battery died. once the battery was dead i placed it back on the charger and eventually it turned on. this has only happened maybe three times since i bought the watch at launch.
SeaFractor said:
I think there can be three reasons for the black screen.
1. The watch has hung and needs the 2-3 minute bottom press as posted by the OP.
2. You use Watchface or Watchface Pro like myself. It has occasionally crashed on me. After several taps, I eventually have the menu come up and can get to settings/reset. I then have the default Moto face and can reselect Watchface. Hope this bug is fixed soon.
3. Hardware failure. LCD displays have a single backlight and if it fails so does the display.
I hope it's either #1 or 2 that you are running into.
Click to expand...
Click to collapse
I've tried #1 but failed to force restart the watch. #2 seems not applicable to me since I'm using Facer.
[Solved]
Hi,
I faced the same issue suddenly (black screen) since yesterday, i came across your thread today trying to find a solution, and tried every solution posted here (e.g. holding 2~3 min on power bottom) several times, but no success!!
I put the watch at charging dock and the charging LED in the dock is ON.... but the watch is just showing black screen ... until i thought it might be from the USB cable... so i change it with its original USB cable which comes with it in the box (while unaware; i used a cheap USB cable from the market 2 days ago while organising chargers/cables in electricity outlet, without realising that i changed the USB cables), and once i used the original USB cable... it's started to work/charge immediately.
Solved
fireball0093 said:
So something quite unfortunate happened to me last night. I factory reset my watch since I installed a new rom on my Moto G, and ever since I did that, the screen is black. Nothing else. The power button isn't doing anything regardless of how long I hold it in or whatnot, and it's just not doing anything, it's a brick. It's not rooted or boot loader unlocked or anything either. When it place it on the charging dock though, the light at the bottom of the dock lights up so I know it's charging at least, but I just really don't know what happened to it. Do you guys think it's toast?
--Edit--
So I spoke to Motorola's live assistance, and if this issue arises for anyone else, hold the power button down for about 2-3 minutes and it should boot into the bootloader, from there you can either attempt a fastboot reboot command or a normal powerup.
Click to expand...
Click to collapse
I hold the power button for 3 minutes, however nothing happened.
Soon after holding i put it back on the charger and it restarted itself and everything was perfect.
hope this works for you.
Yeah. I'm having the same issue. The only thing that allows me to turn the watch back on is to put it on the charger. Been dealing with this for a few months.
after I changed rom I can not associate my bike away bluethoot.
the Debug:
cached bluetooth device for device not found
E / bluetoothDevice (3177) getBluetoothClass () COD is 526 084
E / bluetooth Event Manager Settings (13790) Got bonding been changed fo Mac-addres wareble, but device not added into cache.
someone has this problem?
I have the same thing! Really frustrating.
If I put it on the charger there is nothing. If I put it in a "funny" way the light on the duck is on and I can even see the battery sign shown but it disappeared after a few seconds.
I used different chargers and cables and outlets in my house and other places - same thing.
I even tried a friend's charger (original moto 360 charger) but nothing.
I did try the "holding" (3 min is a bit much, no?) - nothing happens. I do have a blister on my hand from doing that 5 times
Any other ideas?
I bought this watch because I was curious and now i can't be without it. I will buy another one if there is no resolution.
I have the same issue. I put the watch aside for a few days (still haven't exhausted the battery), and then put it on its original charger, a few minutes later, the display come back! Don't know why, and don't know whether it will happen again...
Wireless charging has recently stopped working on my Pixel 3 xl. It has been fine for about 2 months, but all of a sudden, wireless charging keeps kicking in and turning off intermittently. On my Pixel Stand it will start up for about a second then stop, and an orange notification light pops up on the base of the stand. I have noticed that sometimes, when I lightly shake my phone, it will start up and work again until I move it, so I'm thinking there might be something loose inside.
It is not charger related, as the problem exists on my Pixel Stand, my Anker charger, and multiple other chargers. It is not case related as it continues with or without a case on the phone.
It does not work in safe mode, and a full factory reset has done nothing for the issue.
Has anyone else experienced anything like this, and better yet, has anyone found a solution?
explodingscotsman said:
Wireless charging has recently stopped working on my Pixel 3 xl. It has been fine for about 2 months, but all of a sudden, wireless charging keeps kicking in and turning off intermittently. On my Pixel Stand it will start up for about a second then stop, and an orange notification light pops up on the base of the stand. I have noticed that sometimes, when I lightly shake my phone, it will start up and work again until I move it, so I'm thinking there might be something loose inside.
It is not charger related, as the problem exists on my Pixel Stand, my Anker charger, and multiple other chargers. It is not case related as it continues with or without a case on the phone.
It does not work in safe mode, and a full factory reset has done nothing for the issue.
Has anyone else experienced anything like this, and better yet, has anyone found a solution?
Click to expand...
Click to collapse
It sounds like a hardware problem like a loose connection at the charging pad that will have to be repaired at a shop. Definitely contact Google if you haven't already, it dose not sound like something that can be fixed on the software side.
Stupid question, but are you using a case while it is on the stand? Does the case happen to have something potentially blocking the middle of the phone where the charging coils are?
dcorrea said:
Stupid question, but are you using a case while it is on the stand? Does the case happen to have something potentially blocking the middle of the phone where the charging coils are?
Click to expand...
Click to collapse
I thought the same but OP said it recently stopped working, which made me think it was a phone issue. Also said shaking the phone can get it to work again, which seems more like an internals issue. Also possible that the case is right on the cusp of being too thick and sometimes it works if it's in just the right spot.
fury683 said:
I thought the same but OP said it recently stopped working, which made me think it was a phone issue. Also said shaking the phone can get it to work again, which seems more like an internals issue. Also possible that the case is right on the cusp of being too thick and sometimes it works if it's in just the right spot.
Click to expand...
Click to collapse
It also says "It is not case related as it continues with or without a case on the phone."
Misterxtc said:
It also says "It is not case related as it continues with or without a case on the phone."
Click to expand...
Click to collapse
Ah, missed that.
Yeah. I took it in to ubreakifix, a Google licensed repair partner in Canada and they confirmed that it is broken. They don't know what is broken, but it's broken. I will need to get it replaced through Rogers since I got it from them, which is a pain because they are super incompetent.
explodingscotsman said:
Yeah. I took it in to ubreakifix, a Google licensed repair partner in Canada and they confirmed that it is broken. They don't know what is broken, but it's broken. I will need to get it replaced through Rogers since I got it from them, which is a pain because they are super incompetent.
Click to expand...
Click to collapse
Just curious, does it happen when you put it on sideways? Sometimes that happens to my phone too, the orange light, but I didn't know what it meant. I would just take it off the charger and put it back on and it was ok but I didn't have to shake it. I sometimes wonder about the employees at ubreakifix. I brought my Pixel 2 in and got completely different diagnosis from 2 people there. And you're sure it's not the stand? Can you test it out on another stand, not a 3rd party one? I'm just offering suggestions since you might have some trouble returning it to a vendor that is not forthcoming in solving problems.
Long story short, I sent my phone in for repair through Rogers. It took them about 3 weeks to get it back to me but they ended up just replacing the device. No word on what was actually wrong with it.