Related
I purchased a Nexus 4 8GB on launch day. The device consistently (multiple times per day) would be non-responsive to my touch on the lock screen when I pushed the power button to do a PIN unlock. I had to cycle the power button to get it to respond to my touch.
I called in an RMA the other night, Google overnighted a new phone to me. The same problem occurs, I haven't installed ANY programs. What are the odds it's hardware and not software?
Does nobody else have this problem???
I can replicate it: Turn the screen off, put five fingers on the screen, at the same time push the power button to bring up the unlock screen. My screen will usually not respond, or it delays a response by a couple seconds. It can take a couple attempts to get it to do it.
The only thing I added was the Google News and Weather widget to the main screen.
crazeco said:
I purchased a Nexus 4 8GB on launch day. The device consistently (multiple times per day) would be non-responsive to my touch on the lock screen when I pushed the power button to do a PIN unlock. I had to cycle the power button to get it to respond to my touch.
I called in an RMA the other night, Google overnighted a new phone to me. The same problem occurs, I haven't installed ANY programs. What are the odds it's hardware and not software?
Does nobody else have this problem???
I can replicate it: Turn the screen off, put five fingers on the screen, at the same time push the power button to bring up the unlock screen. My screen will usually not respond, or it delays a response by a couple seconds. It can take a couple attempts to get it to do it.
The only thing I added was the Google News and Weather widget to the main screen.
Click to expand...
Click to collapse
did it hppen will charging???mny facing this problm....with quad core cpu 2 gb ram so smooth it should be...have try install launcher???i watch the video in other web...it so frustating..mayb upgrade/update jelly bean solve the problem..i dont know just guessing...mayb that y it upgradeable...
crazeco said:
I purchased a Nexus 4 8GB on launch day. The device consistently (multiple times per day) would be non-responsive to my touch on the lock screen when I pushed the power button to do a PIN unlock. I had to cycle the power button to get it to respond to my touch.
I called in an RMA the other night, Google overnighted a new phone to me. The same problem occurs, I haven't installed ANY programs. What are the odds it's hardware and not software?
Does nobody else have this problem???
I can replicate it: Turn the screen off, put five fingers on the screen, at the same time push the power button to bring up the unlock screen. My screen will usually not respond, or it delays a response by a couple seconds. It can take a couple attempts to get it to do it.
The only thing I added was the Google News and Weather widget to the main screen.
Click to expand...
Click to collapse
I just tried doing that around 10 times and I couldn't get my screen to not respond. Have you tried flashing a different rom to see if it helps? Switching roms is the best way to pinpoint software or hardware as a culprit.
yoft1 said:
I just tried doing that around 10 times and I couldn't get my screen to not respond. Have you tried flashing a different rom to see if it helps? Switching roms is the best way to pinpoint software or hardware as a culprit.
Click to expand...
Click to collapse
I updated to 4.2.2 ... I can still get it to become non-responsive. Try hitting numbers very quickly after you hit the power button. Make sure all five fingers are on the screen when you hit the power button.
I also have this issue. I press the power button to turn the screen on, and it will be unresponsive until I turn the screen off then turn it on again and all is fine. Sometimes it is just really laggy for 10 seconds, then it returns to normal. I am thinking this may be a bug in the stock kernel, but I'm not sure.
What programs do you have installed and which widgets do you use? Give me a complete list.
How many Google email accounts are added to your phone?
Sent from my Nexus 4 using Tapatalk 2
crazeco said:
What programs do you have installed and which widgets do you use? Give me a complete list.
How many Google email accounts are added to your phone?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I use apex launcher, have the Google now widget and clock, and only one gmail account. I still think it is the stock kernel, I have flashed Franco's kernel this morning, and have yet to encounter the issue. I will report back at the end of today of the results.
I am rooted and have been encountering this in stock 4.2.1 and 4.2.2 and CM 10.1.
Why do you think so few people notice it? Now that I've had it on two separate devices... It has to be software/kernel. Please do update.
Sent from my Nexus 4 using Tapatalk 2
Franco's kernel didn't work. Still have the issue, though less occurring.
---------- Post added at 06:25 PM ---------- Previous post was at 05:59 PM ----------
Okay, so if there is any multi-touch on the screen when it is turned on, it will be unresponsive. The OP says put five fingers on the screen and turn on the screen (while still holding the fingers on the screen). However, the same results can be replicated by only having two fingers and turning on the screen. What this means is, say, if you are holding the phone, and your thumb and finger are on the screen (on the sides, even barely) and turn on the screen, you will get an unresponsive touchscreen.
Multi-touch still works so it isn't a defective touch panel. I don't think this is any hardware issue other than the hardware used in the few affected phones could be of a different revision number, so the kernel isn't working with it the same as the commonly used panel. I could be wrong, but this is just the conclusions I can draw from this.
Is there an official Google thread or report on this issue?
I can confirm it will do it with just two fingers.
Sent from my Nexus 4 using Tapatalk 2
Same thing here. Just don't touch the screen when turning it on.
Sent from my Nexus 4 using xda premium
crazeco said:
Is there an official Google thread or report on this issue?
I can confirm it will do it with just two fingers.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I don't think there is an official Google thread for this issue yet.
crazeco said:
Why do you think so few people notice it? Now that I've had it on two separate devices... It has to be software/kernel. Please do update.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I don't know what to tell you. I've tried it with every number of fingers from 1 to 5 on the screen when I turn it on. I've tried it with and without a PIN. In no way shape or form can I get my screen to lag. I told you before to wipe and try flashing a different rom as that is the most comprehensive way to separate a software issue from a hardware issue. Not updating, but root, wipe, and flash.
Sent from my Nexus 4 using xda premium
yoft1 said:
I don't know what to tell you. I've tried it with every number of fingers from 1 to 5 on the screen when I turn it on. I've tried it with and without a PIN. In no way shape or form can I get my screen to lag. I told you before to wipe and try flashing a different rom as that is the most comprehensive way to separate a software issue from a hardware issue. Not updating, but root, wipe, and flash.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well it's a lot problem that exists for other people in the thread as well. I've had two separate devices, both factory settings with no software installed that do it.
I wish I could try out your device...
Sent from my Nexus 4 using Tapatalk 2
Using Franco's kernel, I have only run into the issue while turning on the screen once, where as I have encountered it many times a day before. I could also be that I know what causes it, so I subconsciously attempt to turn it on with nothing touching the screen, but I don't know.
It seems I have found the issue. I have deleted all lock screen widgets and it seems to fix it. Google, next update please fix this.
Hi guys,
Anyone encountered your Note 3 hanged and you unable to swipe or press the back button.
The only way to swipe again is to press off and on and you be able to do that.
My phone is brand new and even after I factory reset it still hanged.
Same Hangups with me
The same happens to me with an unchanged Note 3 9005, Vodafone Germany branded; Suddenly the especially the screen freezes.
some buttons still work. Sometimes it works again, sometimes only a reboote works.
johrub said:
The same happens to me with an unchanged Note 3 9005, Vodafone Germany branded; Suddenly the especially the screen freezes.
some buttons still work. Sometimes it works again, sometimes only a reboote works.
Click to expand...
Click to collapse
And i thought it was a launcher that causing this. Seems like I'm not the only one.
Note 3 hanged
I use the Nova Launcher ...
Anyone facing the same issue?
anyone? no one having this issue?
My T-Mobile Note 3 did it once, so far.
NOT rooted, stock launcher and browser.
Sent from my Nexus 10 using xda app-developers app
Yes, same problem here with a completely stock and non-rooted international (Germany) Note 3. I have had the device now for a little over a week, and the problem occurs quite frequently several times a day. Very annoying, so any fix would be VERY appreciated!
German Unbranded LTE... Apex Launcher, no such issue so far.
Try cleaning your system cache in Recovery.
I get the same problem.
No response to back, menu, home or power button.
If I wait about 10-20 seconds, it will start responding again.
It happens several times a day.
Very annoying. Never had this problem with the Note 2.
N900 in Thailand, not rooted using Nova launcher.
Sent from my SM-N900 using xda app-developers app
Its happened to me, Stock and No root, Its look like touchwiz is suck.
Sent from my GT-I9300 using XDA Premium 4 mobile app
I have the same problem. My situation is described in my thread:
http://forum.xda-developers.com/showthread.php?t=2473622
Do have a look and see if it's similar!
I've yet found a solution.. =(
DesmondL said:
I have the same problem. My situation is described in my thread:
http://forum.xda-developers.com/showthread.php?t=2473622
Do have a look and see if it's similar!
I've yet found a solution.. =(
Click to expand...
Click to collapse
Seems like I still have that issue.
ShadowLea said:
German Unbranded LTE... Apex Launcher, no such issue so far.
Try cleaning your system cache in Recovery.
Click to expand...
Click to collapse
I tried this yesterday, but I'm afraid it didn't fix the problem. A couple of hours after cleaning the cache partition I got the next hang.
I gave up on this and decided to ask for a replacement phone. Bummer.
Sent from my SM-N900T using Tapatalk
My non-rooted N9005 crashed several times as described below. However I can't replicate them on purpose. It just happened randomly.
On boot-up, when the lockscreen is shown, the device keeps restarting on its on, non-stop. To resolve, I'll need to quickly unlock the phone when the lockscreen is shown. Sometimes it would just keep restarting before the locksreen is shown. When this happens, I'll need to remove the SIM card and the phone would start normally. Then turn it off, reinsert the SIM card, boot-up and quickly unlock the lockscreen. This occurs randomly, but when it occurs, the would keep restarting. Else, phone would boot-up with no issue.
Recorded a video and stopped the recording. Camera hang. From then onwards, can't use camera until reboot.
Enabled the "one-handed operation - use for all screens". Switched to one-handed mode. Not sure what happened, but camera was started when I exit camera, screen is reverted to fullscreen. It should remain in "one-handed" mode. Touch responded to area where the "one-handed operation" window should be. No response to area outside this area. To resolve, re-enter "one-handed" mode and exit.
Phone just hang when games are started which the audio loop playing repeatingly.
My Note3 got hang when I was using facebook...
I m curious it related with RAM... when I check the RAM (after it responds again) it was 2,4 GB of 2,66 (max available)..
After I clear the Memory, then problem stops...
Same issue here..
i'll be scrolling facebook or browsing and i cannot click on links or scroll
weird thing is i can press the back button to close the app or the home button..
there are some other major glitches as well such as Gallery opening VERY SLOWLY.. quick pic is my work around..
waking up the phone with the power button takes longer then expected as well..
coming from a Z10 with less specs and listening to people bash it.. the 3GB quadcore Snapdragon 800 chip with 4.3 jelly bean is deeming to be disappointing..
don't get me wrong i love the device.. just didn't expect so many glithces and slow downs and hangups
Same issue on exynos.
Sent from my SM-N900 using xda app-developers app
I tried something new today, I've been clearing the Ram memory every 15-30 minutes of constant usage and every time I start using the phone and it seems that I haven't had that problem yet. Makes me think it is related to a process.
Sent from my SM-N900T using Tapatalk
This issue started long ago and has continued across several different ROMs. At the lock screen, often times I can't swipe the lock icon (nothing happens) until I swipe the current widget left or right. This happens with DashClock, ROM default, AOSP, etc. And it's not consistent. Sometimes I can unlock just fine. Any ideas? It's the strangest thing.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
TLK3 said:
This issue started long ago and has continued across several different ROMs. At the lock screen, often times I can't swipe the lock icon (nothing happens) until I swipe the current widget left or right. This happens with DashClock, ROM default, AOSP, etc. And it's not consistent. Sometimes I can unlock just fine. Any ideas? It's the strangest thing.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app[/QU
Does the screen freeze for a while sometimes when waking the phone up? At least on my phone it does. Sometimes when turning the screen on I have to wait up to 10 seconds or so before it lets me do anything. Are you rooted and using any custom roms? EDIT. Just saw where u said it happens on other roms. I think the problem is originating from screen off/on settings somewhere.
---------- Post added at 02:40 PM ---------- Previous post was at 02:25 PM ----------
megamanDJ said:
TLK3 said:
This issue started long ago and has continued across several different ROMs. At the lock screen, often times I can't swipe the lock icon (nothing happens) until I swipe the current widget left or right. This happens with DashClock, ROM default, AOSP, etc. And it's not consistent. Sometimes I can unlock just fine. Any ideas? It's the strangest thing.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app[/QU
Does the screen freeze for a while sometimes when waking the phone up? At least on my phone it does. Sometimes when turning the screen on I have to wait up to 10 seconds or so before it lets me do anything. Are you rooted and using any custom roms? EDIT. Just saw where u said it happens on other roms. I think the problem is originating from screen off/on settings somewhere.
Click to expand...
Click to collapse
The reason I say that is because lately when the screen comes back on after moving the phone away from my face to hang up a call it will sometimes freeze up and i can't hang the phone up unless I press the power button to do so. This happened when i was on MF3 and still does on MK2 and I'm still on stock rom. We can't use custom kernels because of the locked bootloader and the stock kernel doesn't have unit.d support so any modifications that are usually set during the initial boot are possibly being applied when the screen turns off and on...idk. You can try using the "universal init.d" app to get a similar effect and see if it makes a difference. I'm just going out on a limb here and it may not have anything to do with your problem or mine, but it's a thought.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I'm not on a phone with a locked bootloader. Running KT kernel. Doesn't matter how long I wait, I can't unlock until I swipe the screen left or right - THEN the lock becomes accessible. Its almost like there's an invisible window blocking that part of the screen. I had an issue with Lux where it prevented my from being able to approve Dropbox access. However, even with Lux disabled I'm still having occasional problems.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
TLK3 said:
I'm not on a phone with a locked bootloader. Running KT kernel. Doesn't matter how long I wait, I can't unlock until I swipe the screen left or right - THEN the lock becomes accessible. Its almost like there's an invisible window blocking that part of the screen. I had an issue with Lux where it prevented my from being able to approve Dropbox access. However, even with Lux disabled I'm still having occasional problems.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Are you on the AT&T i337 model? If so you must be one of the luck ones that didn't take the MF3 ota! It sounds like an issue I had before with Touchwiz compatibility with other roms. But if your phone doesn't have a locked bootloader that wouldn't be a problem for you. I haven't found anything yet that explains why my phone acts the way it does, but I'm still looking so if i come accross a solution for you before you fix it ill let you know.
Yeah I've been running a custom ROM since the bootloader was unlocked. I noticed if I hit the power button and turn the screen off then back on, it works. Starting to think this is related to KT kernel. That's the only thing consistent between ROMs.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I'm having a bit of a weird issue with my new Verizon GS5.
Scenario: I am doing something such as reading a text, decide I'm done and lock the screen, and then a second or two later realize I forget to check something and hit the lock button again to turn it back on. Most of the time when I do this the physical buttons will light up but the screen will stay black, and a few seconds later the physical buttons will turn off. This will happen a few times until finally the screen turns on and I see the lock screen.
I had a similar issue with my Galaxy Nexus (rooted and running Kit Kat) phone prior to the GS5 and figured it was my old hardware- is this some Kit Kat bug?
Thanks for any input
Same issue here. But I can't figure out if it was due to switching to ART or not.
We can wait others reply with this i hope someone will post a tip on this kind of problem.
I switched to art after installing apps and I'm ha ing this issue didn't really play with phone much until after switching to ART. Is anyone having this issue not on ART?
Sent from my SM-G900V using Tapatalk
kameleongt said:
I switched to art after installing apps and I'm ha ing this issue didn't really play with phone much until after switching to ART. Is anyone having this issue not on ART?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Yes this is happening to me running Dalvik.
Happened just now to me. It has happened a few times.
Sent from my SM-G900V using Tapatalk
Had this a time or two. It's like the power button doesn't register or something. Yes I switched to art.
I have found though that if I hold power for a second it pretty much fixes itself without having to do anything crazy like yanking the battery or restarting the phone.
Imo: not a big deal, doesn't seem to happen a lot for me.
Sent from my SM-G900V using xda app-developers app
tehgyb said:
Had this a time or two. It's like the power button doesn't register or something. Yes I switched to art.
I have found though that if I hold power for a second it pretty much fixes itself without having to do anything crazy like yanking the battery or restarting the phone.
Imo: not a big deal, doesn't seem to happen a lot for me.
Sent from my SM-G900V using xda app-developers app
Click to expand...
Click to collapse
Is it kind of bugged?
Lodaserves said:
Is it kind of bugged?
Click to expand...
Click to collapse
This is actually becoming quite an annoyance to me and happens very often. I'm still on Dalvik. Could this be caused by an app?
I feel like half the time I go to use my phone the screen doesn't turn on.
tehgyb said:
Had this a time or two. It's like the power button doesn't register or something. Yes I switched to art.
I have found though that if I hold power for a second it pretty much fixes itself without having to do anything crazy like yanking the battery or restarting the phone.
Imo: not a big deal, doesn't seem to happen a lot for me.
Sent from my SM-G900V using xda app-developers app
Click to expand...
Click to collapse
I'm having the same issue for the past two days; although, I am not switching between apps or anything (only trying to use the phone). No display, but get sound/vibration from buttons and LED lights from soft keys. Unfortunately, both times required me to yank the battery. My S5 is completely stock (not using ART) and have manually reinstalled my apps from old device. Any suggestions?
I am not experiencing this and I have switched to ART...
Lodaserves said:
I think your phone have a problem and others don't have this kind of problem.
Click to expand...
Click to collapse
I hope this isn't the case. Once again I experienced these EXACT same issues with my Galaxy Nexus running 4.4.2. I can't help but think it might be some app causing it since not everyone has it.
I am noticing this every once in a while. But it's mostly right after I shut the screen off after a large processed app or task, and then remember something I forgot to do and try and turn it back on and there is some lag bringing up the screen again.
Black screen when quickly pushing lock
Lodaserves said:
Try to ask the person where you bought it.
Click to expand...
Click to collapse
I was about to return my S5 to Verizon for this very reason. I haven't switched to art and have been having the screen go black on me, you can tell the phone is on because the physical buttons are lit. It seems to happen to me alot when I take the phone off the charger and hit the on button. I will hear the phone rebooting, but not see the boot animation. Thats when I do a battery pull. Holding the button doesn't do it. I also have had a few random reboots. Thats ok...I'm going to try every root method under the sun..gggrrrr..lol
I've started to try to uninstall apps to see if I can narrow down the issue. It still plagues me at least half the time I try to use my phone.
This is happening to me as well. Not as often. I'd say once a day, but I have to pull my battery to restart it. I did 2 factory resets and am now using a new google account as per verizons request and I added apps slowly. I have been fine until I put a second launcher on. I installed the GEL launcher but did not use it just to see if having multiple launchers could cause this glitch. Could it be this? Is everyone else using a different launcher? Also the only time I ever had it happen while messing with the phone was two times while working in light flow. Any one else connected to those two happenings? Trying to narrow down what could be causing this.
Running ART here, I'm not sure if I'm getting this problem, but I have realized some latency from pressing either the home or power button and the screen turning on. Not sure what causes that lag, but it's a good almost full second whereas my S4 would be instant
eagle132 said:
I'm having a bit of a weird issue with my new Verizon GS5.
Scenario: I am doing something such as reading a text, decide I'm done and lock the screen, and then a second or two later realize I forget to check something and hit the lock button again to turn it back on. Most of the time when I do this the physical buttons will light up but the screen will stay black, and a few seconds later the physical buttons will turn off. This will happen a few times until finally the screen turns on and I see the lock screen.
I had a similar issue with my Galaxy Nexus (rooted and running Kit Kat) phone prior to the GS5 and figured it was my old hardware- is this some Kit Kat bug?
Thanks for any input
Click to expand...
Click to collapse
I would assume this is NOT the physical hardware issue, but the software, I heard somewhere that Samsung version of KitKat 4.4.2 is quite buggy and glitchy.
Njzkrish said:
Same issue here. But I can't figure out if it was due to switching to ART or not.
Click to expand...
Click to collapse
I had the issue before and after switching to ART
Anyone have any further ideas yet? I'm not running ART bit I was able to have it happen again when I had Google experience launcher installed. Removed it and it hasn't happened for two days. I'm installing Google launcher again now to see if that was causing the issue.
Anyone else with further developments?
Let me preface this by saying this is my experience. I am passing this off to see if others are experiencing the same thing. I am not dissing this phone because I really like it.
I have seen more than 10 random reboots with this phone. The crazy part is when the phone reboots, I lose settings.... Like a lot of them. I recently experienced and my notification bar started malfunctioning where the settings would not pull up and I could not long press panels. I finally had to factory reset my phone.... After that, it rebooted again this morning while I was listening to the radio.
At this point I am going to have start a log to try to correlate where the problem might be.
This is very concerning. I have never experienced anything like this even with custom Roms.
Please let me know if anyone else is experiencing this.
Sent from my SM-G935T using Tapatalk
I've read that other people are experiencing this too. Hopefully mine doesn't come like this. I would recommend returning it and getting a new one. This is ridiculous that this is happening
Try removing all apps you installed and see if you cant pin it down to an app but if all said and done and phone is stock meaning you installed no additional apps and still see it happen then to me sounds like a Hardware problem and you should return it for a replacement.
anrchy666 said:
Try removing all apps you installed and see if you cant pin it down to an app but if all said and done and phone is stock meaning you installed no additional apps and still see it happen then to me sounds like a Hardware problem and you should return it for a replacement.
Click to expand...
Click to collapse
Unfortunately, I think you are right.
Sent from my SM-G935T using Tapatalk
I'm having the exact same issues. Once or twice a day, usually in USA Today or IHeartRadio, it reboots. Once I experienced that loss of settings also and had to factory reset. I'm going to return the phone.
Try wiping the cache partition
Sent from my SM-N920T using Tapatalk
rocolema said:
I'm having the exact same issues. Once or twice a day, usually in USA Today or IHeartRadio, it reboots. Once I experienced that loss of settings also and had to factory reset. I'm going to return the phone.
Click to expand...
Click to collapse
I also experienced this in iHeartRadio... Do you use bluetooth?
Sent from my SM-G935T using Tapatalk
[email protected] said:
Try wiping the cache partition
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Is there a way to do this on a non-rooted phone?
Sent from my SM-G935T using Tapatalk
Go into recovery mode with phone completely off .volume down+home button+power button.If that doesn't work factory reset and if that doesn't work return the phone or if possible reflash stock firmware through ODIN.
Sent from my SM-N920T using Tapatalk
Yes, I use bluetooth to listen to IHeartRadio. I tried clearing the cache thru recovery. It did not work.
rocolema said:
Yes, I use bluetooth to listen to IHeartRadio. I tried clearing the cache thru recovery. It did not work.
Click to expand...
Click to collapse
I have been watching watchespn for about an hour with my bluetooth headphones... No problem. I need to test iHeartRadio some more. With that said, I think there is a deeper issue here just because I've never seen settings get changed like that.
Sent from my SM-G935T using Tapatalk
My Bluetooth streaming was janky got this notification and restarted the phone. Problem gone. Dunno the relevance but this was a system notification
Just switched back to iHeartRadio on bluetooth, I was coming here to read a reply so I clicked the home button and rebooted.
Sent from my SM-G935T using Tapatalk
The beta version (6.0.0) of the IHeartRadio app seems to have fixed my reboot problem (which was happening on both bluetooth and earphone modes).
Update, it is still rebooting, even using the beta.
First reboot of the day. IHeartRadio and Bluetooth. I am already running 6.0.0 of the app.
Sent from my SM-G935T using Tapatalk
(note that I don't typically do iHeartRadio and Bluetooth on the weekends.)
Sent from my SM-G935T using Tapatalk
My experience was different. I didn't have any random reboot but I did get the phone just hang.
Before my Springbreak trip I was testing out a sport camera and downloaded an app that could remotely control the camera. Everything seemed to be working smoothly during the test. Then when I was done, I shut down the camera, turned off the phone and started packing up.
Then I needed to use the phone, so I turned it on.. it's turned on but I couldn't do anything, the screen was unresponsive.. I couldn't swipe or press anything... I attempted to reboot it... the power button still worked... the reboot menu came on but I couldn't press anything... I still could turn the screen on and off and brought up the reboot menu.. but jsut couldn't do anything with it..
Only one option was available which is to force it reboot by holding Power and Down volumne.
That was weird, especially on a brand new device.
I've seen it reboot a few times, and it is especially annoying when you are trying to show your device off and it reboots...in front of people...randomly. I am not sure if I want to return it just yet because it is a Touchwiz/android bug that I have experienced on other devices as well. It MAY be an app issue but I can't pinpoint it yet.
I was trying to launch my DJI Phantom app and it just hung/restarted - got stuck on tmobile screen and it wouldn't let me do a hard-reset! Had to wait a few mins and it recycled.
vnguyen972 said:
My experience was different. I didn't have any random reboot but I did get the phone just hang.
Before my Springbreak trip I was testing out a sport camera and downloaded an app that could remotely control the camera. Everything seemed to be working smoothly during the test. Then when I was done, I shut down the camera, turned off the phone and started packing up.
Then I needed to use the phone, so I turned it on.. it's turned on but I couldn't do anything, the screen was unresponsive.. I couldn't swipe or press anything... I attempted to reboot it... the power button still worked... the reboot menu came on but I couldn't press anything... I still could turn the screen on and off and brought up the reboot menu.. but jsut couldn't do anything with it..
Only one option was available which is to force it reboot by holding Power and Down volumne.
That was weird, especially on a brand new device.
Click to expand...
Click to collapse
This is exactly what happened to mine, I was going to return it and put it on the charger and it rebooted. Knock on wood, No problems since. I'm going to keep a close eye on this in case I need to exchange.
Yes, same here. Bluetooth headset with iHeartRadio makes the phone reboot and lose some settings. Maybe a bug with iHeartRadio and 6.0.1.