Database Info

Nexus s problems

What's up xda forums.had a couple of concerns with my phone. my nexus s stock running 2.3.2 rooted and unlocked. Here are some of my issues so far
While driving and on the phone, sometimes the call drops after making a nasty sound and stays stuck on the hanging up screen and I can't make or receive a call till I reboot.
When turning the phone off sometimes and turning back on, the screen hangs for a while and 4 seconds later ill feel the phone vibrate 2-3 times and go back to normal in which its not lagging.
When opening my gallery the phone takes about 5 seconds to show me my thumbnails of my photos.it does this every time. Also when I take pictures it takes about 10 seconds to see the photo I took. When talking on the phone I drop alot of.calls or I hear the person sound like a chipmunk lol.
Is my phone messed up? Is the stock rom messed up? I flashed a stock image thru clockwork after I tried a alpha cm7build. Was it corrupted or is my phone a pos. My nexus one never gave me this many problems.
Any help would be great
Sent from my Nexus S using XDA App

No one has had these problems?

thejedimex said:
No one has had these problems?
Click to expand...
Click to collapse
Well, yeah, most of your problems have been mentioned by someone here at one point or another. Some of them have workarounds, some are waiting for fixes from Google.
I think if you try a few searches with the search button in this and the General section you'll find already lengthy discussions on most of those issues.

These problems started after you flashed back to stock?
Try clearing caches and reflash I guess.
Sent from my Nexus S using XDA App

Hostile89 said:
These problems started after you flashed back to stock?
Try clearing caches and reflash I guess.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Maybe even a fastboot oem unlock again to force a TOTAL WIPE of the phone. Be careful, sdcard contents are wiped too.

distortedloop said:
Well, yeah, most of your problems have been mentioned by someone here at one point or another. Some of them have workarounds, some are waiting for fixes from Google.
I think if you try a few searches with the search button in this and the General section you'll find already lengthy discussions on most of those issues.
Click to expand...
Click to collapse
The only major issue I've had only happened once, and it happened for the first time yesterday: Without me touching the back button it started flashing and going back through the app I was in at great speed. It was rather frustrating but its only ever happened the one time.

What some people forget is that the Nexus One also had a lot of problems apon release,
All was ironed out by google
JD

distortedloop said:
Maybe even a fastboot oem unlock again to force a TOTAL WIPE of the phone. Be careful, sdcard contents are wiped too.
Click to expand...
Click to collapse
Im gonna try this right now. thanks for your help

I was able to make one of the problems repeat.. seems cause of the case i have everytime i hit the power button my thumb seems to hold down the volume rocker right in the middle. i then unlock the phone while its still tying to catch up from something.. cause 4 seconds later it will vibrate 2-3 times and the phone is back to reg speed.. there something wrong with my rom or can ya make this happen too?

Yup I get most of these issues too, it really spoils the experience. Next time I'm not gonna get a google phone straight upon release, it's really not worth the hassle. Also does anyone have problems with the wifi? Mine is horribly weak its a joke, struggles with wifi from my bedroom which my laptop and old Iphone 2g handled fine
Sent from my Nexus S using XDA App

Capacitive Buttons Glitch

Hey guys,
So I just bought a 2month used Infuse 4G originally locked to AT&T.
I've been noticing some issues and will try to explain it as clear as I can. Supposedly the person I bought it from said it was an OS issue...Hope you all can shed some light!
So pretend you're using your lovely android Infuse 4G and you're texting. All of a sudden you find yourself at the home screen, interrupted from your messaging. A couple of "huh's?" and "...wtf"'s you resume re-typing your text message.
Later you're on the highway driving to a new joint. The GPS signal has finally locked and you're cruising. All of a sudden, your GPS asks you if you want to end navigation. You look at your phone as if its a zombie and you quickly tap the 'cancel' option. Moments later, you notice the phone is back at the home screen and Google maps navigation is running in the background. You bring it back up. A few minutes later, the menus at the bottom come up. You tap the screen to make it go away and keep driving. This happens many more times while you drive even though you've already taken off the phone case.
So it seems like a ghost is touching the capacitive buttons. Not just one of those, ALL of them (Menus, home, search, back) while using the phone. It's not very frequent, but its enough to be aggravating.
Please advise, thanks!

Is there a case or screen protector on the phone? if so try removing and see if the problem persists
Sent from my SAMSUNG-SGH-I997 using XDA App

No offense but maybe when you hold your phone in landscape mode your palm touches them. Happens to me all the time.
Sent from my SGH-I997 using XDA App

Most likley a kernel issue.Go to your about section and check your kernel and rom version....if your already on a custom rom/kernel, then you might have to Odin back to stock.
Sent from my SGH-I997 using XDA App

aznacid said:
Hey guys,
So I just bought a 2month used Infuse 4G originally locked to AT&T.
I've been noticing some issues and will try to explain it as clear as I can. Supposedly the person I bought it from said it was an OS issue...Hope you all can shed some light!
So pretend you're using your lovely android Infuse 4G and you're texting. All of a sudden you find yourself at the home screen, interrupted from your messaging. A couple of "huh's?" and "...wtf"'s you resume re-typing your text message.
Later you're on the highway driving to a new joint. The GPS signal has finally locked and you're cruising. All of a sudden, your GPS asks you if you want to end navigation. You look at your phone as if its a zombie and you quickly tap the 'cancel' option. Moments later, you notice the phone is back at the home screen and Google maps navigation is running in the background. You bring it back up. A few minutes later, the menus at the bottom come up. You tap the screen to make it go away and keep driving. This happens many more times while you drive even though you've already taken off the phone case.
So it seems like a ghost is touching the capacitive buttons. Not just one of those, ALL of them (Menus, home, search, back) while using the phone. It's not very frequent, but its enough to be aggravating.
Please advise, thanks!
Click to expand...
Click to collapse
It's not an O/S issue .... well, it may be on YOUR device but not a general issue. If you do an Odin full restore to stock and still have the problem you now know why the guy sold it after 2 months.

00mred00 said:
Is there a case or screen protector on the phone? if so try removing and see if the problem persists
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
There is and I've tried removing it. Not the problem, but thanks!

joshf2 said:
No offense but maybe when you hold your phone in landscape mode your palm touches them. Happens to me all the time.
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
None taken! I've actually left the phone w.o a case on a table. Its pretty scary to see your phone randomly show the menu from the home screen as if you pressed the button and then close that menu itself as if you were to press the back button...

Aussti said:
Most likley a kernel issue.Go to your about section and check your kernel and rom version....if your already on a custom rom/kernel, then you might have to Odin back to stock.
Sent from my SGH-I997 using XDA App
Click to expand...
Click to collapse
Firmware 2.2.1
Baseband I997UCKE3
Kernel 2.6.32.9
Buil FROYO.UCKE3
I hope its a kernel issue and not a physical....

MisterEdF said:
It's not an O/S issue .... well, it may be on YOUR device but not a general issue. If you do an Odin full restore to stock and still have the problem you now know why the guy sold it after 2 months.
Click to expand...
Click to collapse
Not sure what an Odin full restore is, but i'll look into it and give it a shot. Not surprisingly, my Infuse 4G is also among the few that have a GPS signal issue. The phone locks after 30 mins if Im lucky...
I didn't pay $434 for a phone that doesnt work properly/involves tweaking just to make simple features work...*sigh*

[Q] Problem with Samsung phone performance

Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.

What firmware are you running?
Is it the same firmware on both phones?
What is the launcher?
Have you tried a different modem?
Are you using a battery saver like juice defender?
Are you using an ad blocker?
Are you using a specific kernel? Oc? Uv?
Need for specific info

ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
You know, for the rather lengthy post, you really have not explained any detail about your issue.. You have a generic 'I have an issue, the Infuse sucks' post and its not going to help anyone resolve your issue. I find it EXTREMELY hard to believe that you have 2 infuses having the SAME EXACT ISSUE. Yes, there will be times when you get a defective phone or it isnt working up to your standards, but to have 2 defective phones with the same defect? You need to play the lottery. Also, i suggest you send the phones back. It sounds like youve already made your mind up and have pretty much bashed the samsung infuse in that entire post. The same samsung infuse that myself, and plenty of other people live with day to day and have absolutely 0 complaints.

I will give you $20.00 a piece for them!!!!

ssa2204 said:
Been contemplating for a while whether to post this as it will come off as rather trollish. Had my Infuse for over a year now. When I first got it I noticed there were some "issues". I remained patient hoping or thinking maybe when GB was released it would improve. It did not. Later I needed to root this phone and came here, found a ROM that had all the AT&T junk stripped out. Phone worked better, but still had these issues.
I got to the point that I knew I would never again purchase either a Samsung phone or Android. Did not know what the culprit was. Just recently I had the chance to really take a look at an HTC EVO, and I realized that Samsung is the problem, not Android.
Number one issue is that this phone is sluggish, and sometimes unresponsive. I will touch whatever button and get that vibrating acknowledgement, but nothing happens. I will be in the app menu and wish to exist and the home button just does not respond.
Yesterday I missed a call because the bloody phone just did not respond, even though I touched the answer button. Other times I just can not make a call. I dial number, and the phone just sits there doing nothing. Eventually I just pull out the battery and restart the phone to make a simple bloody call. I had a HTC WinMo phone for years and never once experienced this. No matter how farked the OS could get with some app or whatever, the phone function always worked.
I do not run a lot of apps, and recently have experienced these issues with almost literally no apps installed. I will then add something like GO taskmanger just to confirm that the unresponsive behavior is not due to some app taking up memory/CPU etc..
Sorry for the long post, but I am at my wits end with this bloody phone. The fact that I miss calls when the **** phone is right in my hand is unacceptable. So before placing this phone in a box filled with C4 and shooting this to the moon, hoping that maybe a solution is out there.
p.s. I have 2 Infuse in use, both have the same issue.
Click to expand...
Click to collapse
Simple . Hack it and put cm7 on it if you really need speed. Maybe its your screen protecter. Wipe the screen off. Cm9 can be sluggish, for speed go to miui on gingerbread or cm7

Id be willing to buy one of the infuses
Trust me...sounds like you got two defective units...which like Scott, I find hard to believe...but hey its possible-idk when you got hem.but if it hasn't been a year then put them back to stock with gtgs unbrick and file a warranty claim with Samsung...the infuse is a great phone and I never had the problem you described...I do have a question though...did you get them both at the same time? Cause I don't see why you would get a second if your first was having problems
Anyways...if you wanna sell one hmu...I may buy one depending on the price and if I can get the money (I think I already may have one lined up for $170 just need to get the money)
Sent from my HTC PH39100 using xda app-developers app

Never really had any problems with samsungs beside the only issue I have ever had with ALL Samsung phones .. They have the worst RF signal/strength out of any company! I miss the days of my old Nokia RF ..
Sent from my SAMSUNG-SGH-I997 using xda app-developers app

Android Law #1: Costum ROMs are ALWAYS 10x better than stock.

Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium

Prometh1216 said:
Wow an i cant find one issue. Always great signal never inresponsive u sure u have an infuse
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Hehehe, what ROM u running?
Sent from my SAMSUNG-SGH-I997 using xda premium

qkster said:
What firmware are you running?
Click to expand...
Click to collapse
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
qkster said:
Is it the same firmware on both phones?
Click to expand...
Click to collapse
No
qkster said:
What is the launcher?
Click to expand...
Click to collapse
Both stock
qkster said:
Have you tried a different modem?
Click to expand...
Click to collapse
No, thought never occurred to me that I should look at this as a solution.
qkster said:
Are you using a battery saver like juice defender?
Click to expand...
Click to collapse
Neither.
qkster said:
Are you using an ad blocker?
Click to expand...
Click to collapse
Nope
qkster said:
Are you using a specific kernel? Oc? Uv?
Click to expand...
Click to collapse
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
qkster said:
Need for specific info
Click to expand...
Click to collapse
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).

are you completely wiping before every flash youve done? have you tried a complete wipe and start from fresh?

ssa2204 said:
One is using the GB posted by jscott30 here, the other is the plain official Samsung GB via Kies. Mine is then UCLB3
No
Both stock
No, thought never occurred to me that I should look at this as a solution.
Neither.
Nope
2.6.35.7-I997RUXK53-CL366622 for mine (GB rooted ROM) the other would be whatever came with the official Samsung GB release.
Again this has been a recurring problem since purchase, and during this time I have had stock Froyo, rooted Froyo ROM, GB update, and for one now a the GB rooted ROM.
When the slow to unresponsiveness occurs there does not appear to be any specific cause. Prior to updating to the rooted GB I had used GO Taskmanager, and long before that some other app I long since forgot the name of. Point was that they had shown that neither CPU was excessive, or memory was used up. Both phones have data services disabled and are strictly Wifi only. There are no tasks or extra programs run in the background (though did install Connectbot today). I no longer use any Live wallpaper. After updating to the rooted GB I left the phone in that state (no software installed) for a week or so, and the problem still occured.
This occurs when calling or answering calls, but as previously posted occurs sometimes just opening the Applications menu as an example. So it is not a specific task or program that is slow or unresponsive. Earlier this evening I got a call, slide the bar across to answer and the screen just hung there for a few moments. This time it was at least not long enough that I missed the call. When the call was done I looked and there simply was nothing running on the phone. No apps, no web browser or mail, in fact I was not even connected to the wifi (I have data 3G/4G service disabled on the phone).
Click to expand...
Click to collapse
Task manager is NOT the best app to tell you what is running in the background.
Maps and other location apps may not be listed but will consume resourse that can be the cause of your lag.
The fact that stopping wallpaper or live wall paper off alleviate the condition may suggest that the phone is running at max capacity. Steps to reduce the load improves it. Live wp, facebook, maps, stock email and other device manager from stock att was one of the first @#$% I took out on any rom I run.
Having a large amount of apps installed can also cause this lag. The OS may only be able to handle so many.
Have a poor signal at the time of the call may also be an issue, especially if both of your phones have this issue occasionally but not consistently.
Lock screen can also be a factor. Some sleep setting may also cause the phone to wake up poorly. I get around this by turning off my lock screen. On the call settings, you can also change the answering options so that it will override others and make it easy to answer.
On any firmware - stock or modded, after you have the phone running for an extended period of time without a reboot, you may start to see some lags. This may be across all devices. You may need to reboot it occasionally or boot into recovery and wipe the cache.
These issues may or not go away once you have a device with more power or resources..ex: dual or quad core, 1gb or 2gb ram etc..my guess is when a device has more power, programmers will come up with more resourse intensive apps that may hinder the phone as well.
Lastly, pay attention to your battery meter. As the power dips below 30%, there are steps taken by the OS to conserve the battery. This may give you lags as well..possibly one of the reason why it seems random also.
If you wanted to test out the lag issue due to background apps, go to settings/account and sync. turn off background data. You will retain the (radio) phone and text but there will be no email/facebook, weather, widgets/market/amazon etc updates unless you manually update them. If this runs smoothly but lags when you turn it back on, you can start the process of narrowing down your culprit.
gl

Touchscreen doesn't work for first few seconds

This was one of the similar threads found, but it didn't give me a solution. I messed around with the different CPU governor's but none of them solve my problem. When I unlock the phone, it doesn't respond well to my touch for a few seconds. I'm using CM10 and I've never had this problem before. It only came up recently when I replaced my lcd and digitizer because I was having touchscreen problems. Now the problems are mostly gone except at the lock screen. I've tried 3 different roms (one was a Sense 3.6 rom) and they all had this problem. Outside of the lock screen, it mostly worked well except inside the "phone app" in the sense rom. I called someone and they didn't hear it ringing, so it went to voicemail. I didn't want to record a message so I pressed end call like 30 times but it didn't work until i took out the battery. It happens in CM10 too, but its not as bad, usually ends the call after the 3rd or 4th time.
To troubleshoot the problem, I turned on "Show touches-show visual feedback for touches" under Developer options. I also made this video so you guys can see what it looks like.

Ir0nMa1deN said:
This was one of the similar threads found, but it didn't give me a solution. I messed around with the different CPU governor's but none of them solve my problem. When I unlock the phone, it doesn't respond well to my touch for a few seconds. I'm using CM10 and I've never had this problem before. It only came up recently when I replaced my lcd and digitizer because I was having touchscreen problems. Now the problems are mostly gone except at the lock screen. I've tried 3 different roms (one was a Sense 3.6 rom) and they all had this problem. Outside of the lock screen, it mostly worked well except inside the "phone app" in the sense rom. I called someone and they didn't hear it ringing, so it went to voicemail. I didn't want to record a message so I pressed end call like 30 times but it didn't work until i took out the battery. It happens in CM10 too, but its not as bad, usually ends the call after the 3rd or 4th time.
To troubleshoot the problem, I turned on "Show touches-show visual feedback for touches" under Developer options. I also made this video so you guys can see what it looks like.
Click to expand...
Click to collapse
Take a look at this thread, maybe it helps. I would say update your firmware to 3.33, and try cleaning and pulling out the gray pin on the back of the phone. Hope it helps

Did you replace the digitizer yourself? If yes, I'd go back and make sure nothing is wrong. Make sure everything is properly put back together. Hope this helps. best wishes.
Sent from my HTC Sensation using xda premium

realsis said:
Did you replace the digitizer yourself? If yes, I'd go back and make sure nothing is wrong. Make sure everything is properly put back together. Hope this helps. best wishes.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I did replace it myself and I think that's probably the problem but my dad is refusing to help me take it apart again. We're going to go to a cell phone repair store to see if they can give us some advice, then he'll probably agree to open it up again and see what's going on.

Ir0nMa1deN said:
I did replace it myself and I think that's probably the problem but my dad is refusing to help me take it apart again. We're going to go to a cell phone repair store to see if they can give us some advice, then he'll probably agree to open it up again and see what's going on.
Click to expand...
Click to collapse
It looks like you've opened 2 treads for the same problem, so here's what I answered you earlier - http://forum.xda-developers.com/showpost.php?p=34955821&postcount=3

Ah yes, I made some new discoveries since then and I forgot to check on that thread so I ended up making a new one. The digitizer/lcd I bought is supposedly new, and it's the one that says HTC in the middle (no T-Mobile logo on the side) I'm updating Cyanogen Mod to the newest version and flashing new firmware, so if that doesn't fix it then that'll rule out software issues. After that, I'll re-install the lcd/digitizer and see if I can get it to work.
Also, you said "when you change displays it's never the same as the original" I've been looking through hundreds of forums and many people have successfully replaced their screen only for the problem to come back again a few weeks later. I'm thinking it has something to do with static buildup caused by third-party batteries or chargers, as seen in this thread that i forgot to mention. I've changed my charger so all that remains is taking apart the screen again.

Thanks to dennis8, my screen is now fixed. He linked me to this thread and it worked right away after that. Finally my freaking phone works :laugh::laugh::laugh::laugh::laugh::laugh::laugh:

Ir0nMa1deN said:
Thanks to dennis8, my screen is now fixed. He linked me to this thread and it worked right away after that. Finally my freaking phone works :laugh::laugh::laugh::laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
glad for you man:good:

Anyone else had unexpected restarts?

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?