As we go around rooting and experimenting with our phones, sooner or later we'll experience a freeze, and be forced to take out the battery to pursue.
I have not seen this posted anywhere within the MyTouch 4G Slide forum, so just to inform you guys that in case you experience a freeze, in order to Force Restart you could simply press
POWER + VOLUME DOWN + TRACKPAD for about 5 seconds. Your phone will then be revived without the necessity of removing your battery.
EDIT: Might not work with the newest devices.
Bump. Maybe this can help somebody.
overhauling said:
As we go around rooting and experimenting with our phones, sooner or later we'll experience a freeze, and be forced to take out the battery to pursue.
I have not seen this posted anywhere within the MyTouch 4G Slide forum, so just to inform you guys that in case you experience a freeze, in order to Force Restart you could simply press
POWER + VOLUME DOWN + TRACKPAD for about 5 seconds. Your phone will then be revived without the necessity of removing your battery.
Click to expand...
Click to collapse
That's great I have been here a while and never figured that out would have saved me probably a total of 12 hours of my life spent on battery pulls lol
Sent from my myTouch_4G_Slide using Tapatalk 2
Haha! that was my case. Until I started playing with the buttons and figured the combination out. It's super useful so I thought I should share.
I wish I had known this earlier, I have used it at least 5 times since you posted this. Thanks.
I've used it hundreds of times. I wonder why HTC doesn't tell us these sort of button patterns and tips? they're kinda like an Easter egg, lol!
Unless it's stated somewhere in the manual, I wouldn't know but I doubt it.
I've gotten a new MT4GS (to replace the one where the keyboard and all the buttons died) and this combo doesn't work for me now. I'm running roughly the same ROM (one of the CM9 alphas), but the difference is that this one came with the latest OTA and is S-ON unlocked with the newer radio and HBoot while the old one was S-OFF (via Revolutionary). Could that make a difference somehow? Are there other ways it might not work (I've even tried when my phone isn't frozen and nothing)?
I'm not aware of any other ways, I've had my MT4GS since the week it came out, so it's loaded with the first Radio & HBoot (S-OFF Revolutionary) and I still use this method frequently - it even works when the screen isn't frozen. I'm not sure if the new devices prevent this method from working, are you still able to access your bootloader by powering on your device and holding the volume down key? If not, then it could be a defective button (I doubt it, hopefully not) or the new HBoot prevents these actions from triggering anything.
If anybody else who's reading this has a newer S-ON device with the newer Radio and HBoot, can you please test this quick-restart method for me?
overhauling said:
I'm not aware of any other ways, I've had my MT4GS since the week it came out, so it's loaded with the first Radio & HBoot (S-OFF Revolutionary) and I still use this method frequently - it even works when the screen isn't frozen. I'm not sure if the new devices prevent this method from working, are you still able to access your bootloader by powering on your device and holding the volume down key? If not, then it could be a defective button (I doubt it, hopefully not) or the new HBoot prevents these actions from triggering anything.
If anybody else who's reading this has a newer S-ON device with the newer Radio and HBoot, can you please test this quick-restart method for me?
Click to expand...
Click to collapse
Just upgraded to a 4GS a little more than a month ago and attempted this a few times. With the phone turned on, all I succeeded in doing was taking a few screenshots (CM9 Alpha 5, S-ON). Booted into recovery and attempted it again and all it did was return me to the CWM recovery options. Learned something new here though, I thought pressing the power button while in CWM froze the phone up but all you have to do is press the power button again and you return to the options...lol.
Not sure if there's a way to purposely cause the phone to freeze up but if you have any ideas on how to do this without jacking my phone, I'll give it a try.
In that case I believe this method doesn't work with the newest HBOOT Devices. Thanks, I will update the OP.
Related
Hi, I'm new here so don't know if i'm posting this in the right place but here it goes... Ok i gave my HTC Inspire to a friend to install the MIUI ROM to it. Afterwards it was running smoothly and had no problems with it. A few days later my Inspire notified me that it had an update to the ROM. At first i wasn't sure to install it because it is a custom ROM and not the default one, but did the update anyways through the phone. Again, the phone worked normal all day, but at some point the screen started glitching untill it turned completly off.
The one strange thing is that the phone seems to function normally because when charged and "turned on" i can hear the sounds and notifications(like email, text and app notifiactions). Also when i connect it to my computer, it recognizes the device.
That happened about three days ago and I have not been able to discover what really is the problem and how to fix it. If there's anyone that could help me i would REALLY appreciate it.
Thanks in advance,
Marialo
most likely was a bad update.
You should boot into recovery and reinstall miui everything should be back.
Keep in mind the devs have to set miui for each device, chances are you updated to the wrong base.
That's what i thought but can't boot into recovery because i can't see the screen... Any advice on that?
Btw, thks for the quick response
Try shutting off the phone completely and booting into your bootloader the old fashioned way by holding down the volume down key, press power, and release volume down once you see the bootloader screen.
If your screen doesn't work during that, you may have a hardware problem on your hands.
Ok thanks; will try that then.
marialo said:
Ok thanks; will try that then.
Click to expand...
Click to collapse
or while the phone's on, if you have ADB installed - open a cmd prompt and navigate to where ADB is and type "adb reboot recovery"
Yup try what they said that should work. If not ruu the ruin and really root
sent from the dark obelisk
Ok, tried with the volume and power button, but nothing happened. Thanks for the advice, but I'm kind of new with all this and don't really know how to do the other stuff that you guys told me to do... :S Should I get someone that knows a bit more or is it something that i could do with a little info. from the internet?
anudist said:
Try shutting off the phone completely and booting into your bootloader the old fashioned way by holding down the volume down key, press power, and release volume down once you see the bootloader screen.
If your screen doesn't work during that, you may have a hardware problem on your hands.
Click to expand...
Click to collapse
I don't know if you would know but... If it were hardware problems; you think I could claim that to htc? Since the phone hasn't had any accidents or anything... :/
marialo said:
I don't know if you would know but... If it were hardware problems; you think I could claim that to htc? Since the phone hasn't had any accidents or anything... :/
Click to expand...
Click to collapse
If its rooted warranty won't cover this. Get the ruu (stock exe) from the HTC support site and run it. If the phone still has a black screen after its been returned to stock then the problem is hardware related
sent from the dark obelisk
Quick background: I purchased a One X from AT&T a few weeks ago. It came with the 2.20 firmware, so I used the X-Factor Exploit and unlocked the bootloader via HTCDev. From there I flashed TWRP Recovery and then AOKP.
Pretty much everything was fine at that point, except for the fact that once or twice a day I would pull my phone out of my pocket and it would be completely unresponsive. None of the buttons would wake the phone up, plugging it in didn't do anything, and it wouldn't receive calls. I would then have to do a hard reboot (Power + Volume Down) to get anywhere.
I thought maybe it was an AOSP problem, so I flashed a Sense-based ROM (CleanROM 5). I experienced the same issue.
From there, I re-locked the bootloader and ran the latest RUU. That was 4 days ago and I have yet to experience the problem again.
Has anybody else experienced this, and is there any way to prevent it?
power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?
redpoint73 said:
power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?
Click to expand...
Click to collapse
I would just select reboot and it would boot normally. Power alone would also work, I believe. I usually just did power and vol down out of habit I guess.
GPS and WiFi were always on.
What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app
c5satellite2 said:
What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
HBoot 1.14. Didn't mess with the radio, so the stock AT&T 2.20 one (0.19as.32.09.11_2_10.105.32.25L).
Yes, I flashed the correct kernel. It did it with both the plain AOKP kernel and rohan's kernel.
Cleared caches several times.
GPS on when this happens, by any chance?
redpoint73 said:
GPS on when this happens, by any chance?
Click to expand...
Click to collapse
I hardly ever disable it, so it was likely on. No idea if it was actually in use any of the times.
I can say one time it happened immediately after a call, one time it was immediately after a SMS notification, and the rest just seemed to be randomly in the middle of the day.
Try going straight to CR5 directly from the stock ruu rom and see if it persists. Maybe the aokp Rom borked something along the way and the ruu has restored it now. I have seen issues similar to this that only the ruu will fix.
Sent from my HTC One X using xda app-developers app
Have the same issue.Try going to ViperXl and see what happens.My phone constantly reboots and enters sleep of death.I always have the gps disabled.have 1.09 hboot.And currently I am on 1.85 stock at&t.This issue is kikling me
I only mention GPS, since my old phone (Desire Z) had an issue where leaving the GPS on, would make the phone shutdown, and only a battery pull would start it (never tried going into hboot). Which sounds similar to what you were seeing. In my case, no ROM, kernel, or radio flashing ever remedied it. And I could isolate the issue to the GPS being on. If the GPS was used, the phone was going to black screen within a couple hours, without fail. But rebooting the phone after using the GPS (and shutting off GPS) prevented it every time. A few other owners of the DZ had the same problem. One guy sent his into HTC, and they told him it was a defect of the GPRS module, and replaced the motherboard, which fixed the problem.
Hopefully, its not a similar hardware issue in your case. But the fact that you have the GPS on all the time, and the black screen hasn't cropped up like clockwork (like it did in my case) seems to point to the fact that it might not be the exact same issue.
These types of issues tend to be really hard to troubleshoot (and pinpoint the cause). In my case, it took me a couple months to realize it was the GPS, since I usually have it off, and don't use it all that often (usually just when travelling). And I also suffered a lot of "placebo effect" type incidents while flashing various ROMs and kernels trying to fix the issue. If the issue doesn't crop up again after running the RUU, I'd consider myself lucky, and leave it well enough alone.
No it is not the same problem redpoint73.This only happens on Custom ROMS.I have tried every combo on the 3 ROMS i flashed.Could it be an int.d problem???My only is this.
nighthawk696969 said:
No it is not the same problem redpoint73.This only happens on Custom ROMS.
Click to expand...
Click to collapse
Yeah, I already said its probably not the same problem. But it doesn't hurt to check everything. As I mentioned, its easy to get sucked into thinking you have the cause isolated, when you really do not.
I understand what you're saying but i have checked it,i'm sure..
nighthawk696969 said:
I understand what you're saying but i have checked it,i'm sure..
Click to expand...
Click to collapse
It also doesn't sound like your problem is exactly the same as the OPs. You mention reboots, while OP does not (just BSOD, or shutdown requiring rebooting in hboot).
No my main problem are the Sleeps of Death.There are no BSODs in android
nighthawk696969 said:
No my main problem are the Sleeps of Death.There are no BSODs in android
Click to expand...
Click to collapse
Some people have been calling this condition BSOD = Black screen of death. Yes, its a little too derivative of things like Windows blue screen, XBox RROD etc. But you get the idea.
Update: I re-unlocked the bootloader and flashed CM 10.0.0 upon its release. I've yet to encounter this issue, so I'm thinking my stint on CleanROM might have buggered something. I probably forgot to wipe something somewhere along the line. D'oh.
I am, however, having a pretty severe albeit unrelated problem with an app called Voxer. Every time I listen to a message it kills the microphone until I Force Stop the app. I guess I'll pop over to one of the other AOSP ROMs and see if it persists.
I was having a similar problem on king kang and pacman. I could turn the phone on and off with the power button, but the touch screen was completely unresponsive. Happened randomly, I would have to hold the power button down and watch the lights flash until the phone shut down, and would be fine after a reboot. When I tried installing viperxl, I had the same issue during the aroma installer, I had to try flashing it 7-8 times, because it kept freezing during the install. No issues running it after a successful install. I was using king kang and rohans b5 kernel when it was happening most often
I began posting this problem in a previous thread but am starting a new one to avoid clogging said thread.
Here are my phone details at the moment:
S-Off
SuperCID
HBoot 2.14
Radio 0-24p.32.09.06
Open-DSP-v34.1.0.45.1219
I bought the phone used off kijiji. It was stock when I got it. Rogers, Android 4.1, 3.17 firmware. I unlocked the bootloader, got SuperCID and S-Off, flashed TWRP and flashed a custom ROM - CleanROM. Things were okay for a bit.
Then I started getting random restarts and losing signal. I realized I was on 2.14 hboot so I updated to 2.15. I thought it fixed the problem but no- before long, more random reboots--though I did fix the signal issue.
So I flashed Beastmode kernal. Now, I did this without doing a full wipe - just threw it on top of CleanRom. Possibly a bad idea because everything kinda got all screwy at this point. The phone started acting really oddly--freezing a lot, restarting even more often, and sometimes the touchscreen would act up.
Next step: I tried to do a full wipe and flash a different ROM: KickDroid. Only thing was, it wouldn't flash. The installer would crash, most of the time at 30%. The phone would then restart, though it wouldn't boot (obviously), so I'd have to hold down the volume to put it into the bootloader.
Tried flashing CleanROM then - no go. It wouldn't flash either - phone would just power down.
This became a theme. The phone would just start turning itself off all the time. Even sometimes when I was doing a wipe in TWRP, the thing would just crash partway through and turn off. Somehow, this morning, I DID manage to get CleanROM to flash, but then it wouldn't boot- froze at the Google splash screen and turned off...
On timmaaa's suggestion at this point I went to an RUU and tried to get the phone back to stock. Went with the 3.18 Cingular RUU. For whatever reason, it didn't work the first time (might have been my fault - I forgot to uninstall HTC Sync Manager) but when I tried it again, it did. I was excited - phone was, hopefully, back to its old self, after all!
Booting to splash screen: freezes on the HTC logo. Turns off, randomly. AAGGHH!!!
So I try again, knowing, at this point, it's futile. The phone BEGINS to boot up. Gets to the Cingular screen and then just enters into Android - says it's going to start refreshing apps or whatever... and then it turns off.
Note that I have it sitting in the bootloader right now and it is not turning off. The bootloader itself seems to work well enough.
Even now, I tried to boot the thing up just one more time, and it again just nearly got into Android but turned off before fully loading.
I'm at a loss. It's not like I've been just randomly flashing things on here - I only used ROMs that worked for the phone. Maybe my dirty flash (is that the right terminology) of Beastmode was the problem, but I feel like it shouldn't continue to persist this long, after using an RUU. I'm wondering if perhaps it's a hardware issue at this point.
Any thoughts, ideas, suggestions, etc. are amazing... thank you.
At this point I believe you've tried pretty much everything you could try. It's possible you have a faulty motherboard.
Sent from my Evita
timmaaa said:
At this point I believe you've tried pretty much everything you could try. It's possible you have a faulty motherboard.
Sent from my Evita
Click to expand...
Click to collapse
Darn. Anything that can be done about that? Is it feasible or even worth it to try to replace it?
Get this - it just booted to Android, and seems to be staying there. For the time being, anyway.
Edit: never mind. lol. Turned right off again after connecting to wifi.
It all depends on whether you think it's worth the money to repair it, or just to buy a new device.
Alright. Thanks a lot for your help. I'll try to consider my options.
Try running a different RUU. Not sure of it will help just a suggestion
Sent from my HTC One XL using xda app-developers app
johnnyp12321 said:
Try running a different RUU. Not sure of it will help just a suggestion
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yeah, I'll give that a shot, too. Thanks. Though I'm not that optimistic at this point, lol.
On a related note: I have the opportunity to buy an HTC One XL with a broken screen for cheap. What do you guys think the options are for me (a) taking the mobo out of the broken one and using it in mine or (b) replacing the screen on the broken one with the working one from mine? Do you know how difficult/manageable either process is?
The phone seems to be more or less completely dead now. It will occasionally power up but can't do much beyond the bootloader. Anyone have any experience replacing motherboards on the HTC One XL? Is it possible to swap one out from a working phone? Or is it possible to use my screen to replace one on a phone with a broken screen?
Out of nowhere my power button magically no longer works. Kind of a huge deal since I use my phone for work a TON. At first I thought it was the ROM but then I rebooted into recovery and discovered it doesn't work in there either...... but by some sort of miracle though my phone magically boots itself up when I swap batteries in it....
I am rooted and running Beans 20.
Any help/ideas would be greatly appreciated!!
Sent from my SCH-I535 using Tapatalk 2
You can get an app called button savior from Google play that allows you to create on screen keys to turn off your screen.
Various xposed modules allow you to remap your physical keys. If you don't know about the xposed framework I highly suggest looking into it.
Furthermore I believe some custom roms have key mapping built in.
Sent from my QMV7A using Tapatalk
ImUnderTheBed said:
You can get an app called button savior from Google play that allows you to create on screen keys to turn off your screen.
Various xposed modules allow you to remap your physical keys. If you don't know about the xposed framework I highly suggest looking into it.
Furthermore I believe some custom roms have key mapping built in.
Sent from my QMV7A using Tapatalk
Click to expand...
Click to collapse
Yes I already got an app that will shut my screen off and lock it but what happens when my phone stops magically booting up all by itself??
Then I'm screwed.
:crying::crying:
flooritnfly said:
Yes I already got an app that will shut my screen off and lock it but what happens when my phone stops magically booting up all by itself??
Then I'm screwed.
:crying::crying:
Click to expand...
Click to collapse
Mine started doing the same thing.
flooritnfly said:
Out of nowhere my power button magically no longer works. Kind of a huge deal since I use my phone for work a TON. At first I thought it was the ROM but then I rebooted into recovery and discovered it doesn't work in there either...... but by some sort of miracle though my phone magically boots itself up when I swap batteries in it....
I am rooted and running Beans 20.
Any help/ideas would be greatly appreciated!!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
My power button just started malfunctioning too. I'm on Odin barebones 4.1.2 stock and the problem persists.
It sounds like a lot of people are getting this problem. If you use that knowledge to your advantage, I've heard people convince Samsung it's a manufacturing problem and got it repaired outside of Warranty. The power button itself is sautered onto the motherboard, so unless you really trust a mobile repair company, best option is work directly with Samsung.
That being said, I'm going to look for an Xposed Framework module that can remap the power button.
I looked for one, didn't really find what I was looking for... selling mine on ebay now to pay for my new phone...
Sent from my HTC6525LVW using xda app-developers app
Wow. My power button just stopped working also.
My phone is stock.
I did replace the glass myself a couple months ago and it's been working fine until about a week ago. Was wondering if that had anything to do with it.
Interesting to see I'm not the only one having issues.
Kind of timely now that the S5 is coming out this week.
usho said:
Wow. My power button just stopped working also.
My phone is stock.
I did replace the glass myself a couple months ago and it's been working fine until about a week ago. Was wondering if that had anything to do with it.
Interesting to see I'm not the only one having issues.
Kind of timely now that the S5 is coming out this week.
Click to expand...
Click to collapse
This is happening to a lot of people. I'm sure the s4 will start having this problem followed by the s5 after a year and some months. Im done with samsung phones until they start using different parts. Actually thinking about the next nexus phone and hack a msata drive into it with a custom vacume formed case. The only reason I haven't owned one is because of the storage limitation. I think a 200+ gigabyte msata strapped to the back would fix that problem.
tmettler5 said:
Mine started doing the same thing.
Click to expand...
Click to collapse
sweeds said:
My power button just started malfunctioning too. I'm on Odin barebones 4.1.2 stock and the problem persists.
It sounds like a lot of people are getting this problem. If you use that knowledge to your advantage, I've heard people convince Samsung it's a manufacturing problem and got it repaired outside of Warranty. The power button itself is sautered onto the motherboard, so unless you really trust a mobile repair company, best option is work directly with Samsung.
That being said, I'm going to look for an Xposed Framework module that can remap the power button.
Click to expand...
Click to collapse
usho said:
Wow. My power button just stopped working also.
My phone is stock.
I did replace the glass myself a couple months ago and it's been working fine until about a week ago. Was wondering if that had anything to do with it.
Interesting to see I'm not the only one having issues.
Kind of timely now that the S5 is coming out this week.
Click to expand...
Click to collapse
Hey guys, mine originally starting messing up on Saturday, and then Sat night and all day Sun is was fine, and now it is doing it again. I even installed a new rom and it is still doing it so now I am convinced it is purely physical and not rom-related. What are you guys going to do?
I have the Wireless Phone Protection for my phone and am thinking about using that to my advantage to get a new device....question is I've never done it before. If I say I have a physical problem with my phone then won't Verizon want it returned? That will make me have to unroot it and bring it back to out of box state which is a big headache. What if I just say I lost it or it got stolen? Am I better off going that route?
EDIT: Also forgot to mention that along with these power button issues my S3 also will not reboot on its own. If I select Reboot (be it from the power button menu, notification pulldown, etc) it will just shut off and not reboot.....but if I yank the battery and put it back in it will then reboot to recovery. Same deal if I do a normal reboot, haven to yank and replace battery. You guys having these issues too?
So a couple of days ago my power button started acting wonkie as well. I would push it and it basically acted sticky. I would push once but it would register twice or as a long press. Either turning the screen on and off or bring up the reboot menu. So I did the xposed button remapping. Worked pretty well, but if I restarted the phone it would do a weird haptic feedback thing every couple of seconds before finally booting up.
So I wasn't satisfied with just living with it being a hardware issue. So I downloaded latest cleanrom to flash from cm11. I rebooted recovery and now it just vibrates every couple of seconds. Would not make it to twrp. It will get to cm Samsung boot screen but then just goes back to vibrating black screen. I took out battery and popped out power button but same results.
Any suggestions? Think power button can be fixed by repair shop or is it time to go back to my trusty droid incredible until I can upgrade.
Sent from my Nexus 7 using xda app-developers app
luland said:
So a couple of days ago my power button started acting wonkie as well. I would push it and it basically acted sticky. I would push once but it would register twice or as a long press. Either turning the screen on and off or bring up the reboot menu. So I did the xposed button remapping. Worked pretty well, but if I restarted the phone it would do a weird haptic feedback thing every couple of seconds before finally booting up.
So I wasn't satisfied with just living with it being a hardware issue. So I downloaded latest cleanrom to flash from cm11. I rebooted recovery and now it just vibrates every couple of seconds. Would not make it to twrp. It will get to cm Samsung boot screen but then just goes back to vibrating black screen. I took out battery and popped out power button but same results.
Any suggestions? Think power button can be fixed by repair shop or is it time to go back to my trusty droid incredible until I can upgrade.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It can be fixed. There is also a way of temporarily making the power button work but I don't feel like explaining it again. If you do some searching there are at least 20 threads that have the temp fix in it.
ThePagel said:
It can be fixed. There is also a way of temporarily making the power button work but I don't feel like explaining it again. If you do some searching there are at least 20 threads that have the temp fix in it.
Click to expand...
Click to collapse
Link to the temp fix please?
Sent from my SCH-I535 using Tapatalk
I've had three unexpected restarts in the last 5 days, two of them when I wasn't actually using the phone (one just after I put it on charge).
ISTR this happening in the early days of the HTC 10 or U11, but it went away after an update.
What software version do you have?
Any apps that might be the cause?
I have the US unlocked running .617 and haven't had any issues at all so far.
Tachi91 said:
What software version do you have?
Any apps that might be the cause?
I have the US unlocked running .617 and haven't had any issues at all so far.
Click to expand...
Click to collapse
I'm UK, unlocked, on 1.15.401.2.
Can't think of any apps that would cause a problem (such as?), and it's stock, not rooted.
Luckily, it's very fast to boot up, so not a major problem.
Can you try figuring out a pattern? See if it might be caused by something you're overlooking.
Maybe try pulling log files see what happen before it crashed. Adb tools from Google have logcat and a program I forget what it's called that lets you see all kinds of information from the device when connected.
dlorde said:
I'm UK, unlocked, on 1.15.401.2.
Can't think of any apps that would cause a problem (such as?), and it's stock, not rooted.
Luckily, it's very fast to boot up, so not a major problem.
Click to expand...
Click to collapse
Wait you really got version number 1.15.401.2!?!?
As far as I know, and see on my device retail software should be on 1.15.401.4!!
Sent from my HTC U12+ using XDA Labs
Theres a thread that has RUU posted on a Google spreadsheet.
It has 401.4 as a flashable zip. If you really do have 401 either try checking for an OTA update. Or down the zip from that thread. Backup all your data and flash the 401.4 using an SD card or OTG.
Maybe whatever issues you're having is caused by a bug that HTC fixed in . 4
Tachi91 said:
Can you try figuring out a pattern? See if it might be caused by something you're overlooking.
Maybe try pulling log files see what happen before it crashed. Adb tools from Google have logcat and a program I forget what it's called that lets you see all kinds of information from the device when connected.
Click to expand...
Click to collapse
I'm running exactly the same apps in the same way as on my U11.
I did look at Logcat, but frankly I can't make head or tail of it. I'm not familiar with Android internals - I was a C++ & Java developer until 10 years ago, but that was on corporate financial software
5m4r7ph0n36uru said:
Wait you really got version number 1.15.401.2!?!?
As far as I know, and see on my device retail software should be on 1.15.401.4!!
Click to expand...
Click to collapse
Heh - I just checked again, and it's showing 1.15.401.4.
It did restart last night, but unless it's stopped notifying of system updates, I guess I have to apologise for making a typo... (is there an easy way to check when the last update occurred?)
Anyhoo, HTC support are now following their script on it via email - getting me to run the diagnostics.
dlorde said:
Heh - I just checked again, and it's showing 1.15.401.4.
It did restart last night, but unless it's stopped notifying of system updates, I guess I have to apologise for making a typo... (is there an easy way to check when the last update occurred?)
Anyhoo, HTC support are now following their script on it via email - getting me to run the diagnostics.
Click to expand...
Click to collapse
So you're running the retail version just as I am. Got the device for two weeks now and never had any problems regarding restarts. Let's hope this little glitch will be fixed with the upcoming OTA update. Shouldn't be long till it hits actually.
Sent from my HTC U12+ using XDA Labs
5m4r7ph0n36uru said:
So you're running the retail version just as I am. Got the device for two weeks now and never had any problems regarding restarts. Let's hope this little glitch will be fixed with the upcoming OTA update. Shouldn't be long till it hits actually.
Click to expand...
Click to collapse
Yeah; I'm not too bothered really.
HTC support sent instructions to run the diagnostics for the charger confused, and the battery (which doesn't appear on the diagnostics menu!). They also asked me to "press on Volume up key + Power on/off Key holding them together for at least a minute" which doesn't work with the U12+ haptic keys... They also asked me to run it in safe mode for a day to see if an app is causing the problem; I can see the idea, but the phone is unusable in safe mode, so it's not so easy. I did ask whether they had a way to report the system logs, or other useful data after a crash/restart, but they just ignored the question.
I don't think I'm going to have much joy from them. If it only happens once a day or so, I can live with it.
dlorde said:
Yeah; I'm not too bothered really.
HTC support sent instructions to run the diagnostics for the charger confused, and the battery (which doesn't appear on the diagnostics menu!). They also asked me to "press on Volume up key + Power on/off Key holding them together for at least a minute" which doesn't work with the U12+ haptic keys... They also asked me to run it in safe mode for a day to see if an app is causing the problem; I can see the idea, but the phone is unusable in safe mode, so it's not so easy. I did ask whether they had a way to report the system logs, or other useful data after a crash/restart, but they just ignored the question.
I don't think I'm going to have much joy from them. If it only happens once a day or so, I can live with it.
Click to expand...
Click to collapse
In which country do you live? Can't see as I'm on XDA labs currently.
Sent from my HTC U12+ using XDA Labs
I'm in the UK (England).
Sent from my HTC U12+ using Tapatalk
Did you know that if you press the corners of your phone, while pressing with another finger from the back, it acts like a power button press. Means, if it's in a pocket of a tight jeans and it press and hold the corner, it makes a force restart. That's what happens to me a lot. Got now a harder case to prevent this.
Edit: I use a WWE Unlocked HTC U12+. Latest firmware.
MirageBlader said:
Did you know that if you press the corners of your phone, while pressing with another finger from the back, it acts like a power button press. Means, if it's in a pocket of a tight jeans and it press and hold the corner, it makes a force restart. That's what happens to me a lot. Got now a harder case to prevent this.
Edit: I use a WWE Unlocked HTC U12+. Latest firmware.
Click to expand...
Click to collapse
Mine doesn't do that - at levels of force I'm comfortable with applying. It has restarted a couple of times in my pocket, which I thought might be due to the sensitive power button, but it's also restarted a couple of times just sitting on a table.
Sent from my HTC U12+ using Tapatalk
dlorde said:
Yeah; I'm not too bothered really.
HTC support sent instructions to run the diagnostics for the charger confused, and the battery (which doesn't appear on the diagnostics menu!). They also asked me to "press on Volume up key + Power on/off Key holding them together for at least a minute" which doesn't work with the U12+ haptic keys... They also asked me to run it in safe mode for a day to see if an app is causing the problem; I can see the idea, but the phone is unusable in safe mode, so it's not so easy. I did ask whether they had a way to report the system logs, or other useful data after a crash/restart, but they just ignored the question.
I don't think I'm going to have much joy from them. If it only happens once a day or so, I can live with it.
Click to expand...
Click to collapse
What do you mean you can live with it?
Restarting everyday?
You are happy paying a **** load of money and happy to put up with daily restarts.
No one should put up with that kind of major problem
dieselhazza said:
What do you mean you can live with it?
Restarting everyday?
You are happy paying a **** load of money and happy to put up with daily restarts.
No one should put up with that kind of major problem
Click to expand...
Click to collapse
Maybe I should have said I can live with it until the next update - if it persists after that I'll want a replacement. So far it hasn't restarted while in use (and not at all yesterday), so it's not been a significant problem. YMMV.
But you're welcome to jump up and down on my behalf [emoji6]
Sent from my HTC U12+ using Tapatalk
dlorde said:
Maybe I should have said I can live with it until the next update - if it persists after that I'll want a replacement. So far it hasn't restarted while in use (and not at all yesterday), so it's not been a significant problem. YMMV.
But you're welcome to jump up and down on my behalf [emoji6]
Click to expand...
Click to collapse
I would definitely put the phone through intensive usage to make sure it doesn't restart unexpectedly. First of all if it is hardware issue no software update would fix that.
dieselhazza said:
I would definitely put the phone through intensive usage to make sure it doesn't restart unexpectedly. First of all if it is hardware issue no software update would fix that.
Click to expand...
Click to collapse
Then sent it back ,u have garantie.
Dont wait for software update .
Grtz
So far, no further problems for a couple of days, despite unusually high temperatures and heavier than normal usage.
Sent from my HTC U12+ using Tapatalk
Mine did it yesterday, but it was in my shorts pocket. They're mesh, so I think it was pressing the power button, or it was the corners power cycle. Never heard of that before. Where did you hear that?