Develop Bugs

[Q] Answer phone

every other time my phone rings I cant answer it. The accept button just wont move?? is it just me or have anyone else had this error I have a dezire z

Do you have set CPU set to 245MHz @ screen off?

no i dont, why?

Well that could be one cause, maybe it's a bad app causing your phone to temporarily freeze? Can you slide it the other way and ignore the call?

Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.

Utorrent76 said:
Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.
Click to expand...
Click to collapse
why do you suggest this? how do you know hes using kernels? im just trying to see what your connection to the solution is -its quite a specific answer to a problem that hasnt really been examined. what rom is he on, etc before you can start talking about kernels -- so can you clarify?
accept button - do you mean the slider? if you have cmod - just activate settings to disable lock menu/trackball/ whatever --also you could try the no-lock unless you have security issues.
if no cmod -- theres apps to reduce the lockage -- that may help you get your phone calls but still doesnt fix the problem? you could try enomther's and his awesome extra ssettings app has all those options

Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.

jaypeg123 said:
Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.
Click to expand...
Click to collapse
If its a stock DESIRE Z and not a G2 then I think it's safe to assume its got sense on it and not AOSP. Did you try hard resetting it? (power down and pulling the battery for at least 30 sec) other than that id check for any OTA updates in the settings menu. OR if you're willing/know how, you can root it and run CM or virtuous. Both ROMs are excellent. If you do that and the problem persists, it could very well be a faulty unit. You have a lot of options!

I found I had problems answering calls when I had a specific make of screen protector on the phone. As soon as I took that off and went back to a previous one I'd used then it was fine again ! It's a long shot, but I thought I'd throw it in there.

Problem solved, An update did the trick, thanks for helping out my friends,

same problem , cannot answer with swipe keys
I have the same problem, which update did you use

same problem , cannot answer with swipe keys
I have the same problem, which update did you use

Orange Desire debranded and going to 2.3

Hi guys, i've had my orange desire debranded since i got it and its been fine, but recently been having issues with friend stream never updating and phone constantly telling me its nearly full despite me deleting most of my apps and clearing cache and the wifi going dodgy.
So was going to factory reset it, but thought since 2.3 is not out should I just install that instead. Has anyone with a debranded orange desire done this already and noticed any issues?
I heard some one mention that if using the sat nav the phone no longer charges up while using 2.3, because the USB power is limited?

I've gone from debranded orange phone running stock 2.2, to the official 2.33.
Noticed several issues: Random resets, resets if I use the camera whilst touching the screen etc.
Once you've upgraded, you can't go back either.
I would strongly recommend you avoid, until such time as it's possible to root / s-OFF / downgrade HBOOT to install FROYO again (if you experience problems).
EDIT: That beings said, you could install a pre-rooted version which wouldn't upgrade HBOOT. Your choice really

Hey.
I was orange Branded with FroYo. I used the unrEVOked method to root my phone, used alpharev to s-off and then I started playing with ROM's.
I did all this before the gingerbread came out.
I'm currently using RCMixS Evolutionary Sense ROM. Its a mix of sense 2.1 and Sense 3 (the stuff that's on the sensation and such) Its a great ROM.
With official Ginger you are gonna have internal memory problems.
I highly recommend rooting and using RCMixS. Its not perfect, as it suffers from the usual setbacks of Dev GB (such as camcorder image being stretched etc)
but if I'm honest it doesn't bother me.
I've also partitioned my SD card so I have an extra 1gb of memory that the phone can use for the system. It runs very fast now and it is a pleasure to use.
Have a look at this thread for info on RCMixS and see what you think. I made the leap and I have never regretted it. Everything has worked fine for me except for the obvious know bugs, which all GB Devs will be ironing out soon, as soon as they get hold of the Source Code.
Hope this helps.

scarlet_pimp said:
I heard some one mention that if using the sat nav the phone no longer charges up while using 2.3, because the USB power is limited?
Click to expand...
Click to collapse
Hi there, yes I have tried everything but my 'official' HTC charger will only now supply 'Charging USB' since GB update. (NB This only through the car dock, the car charger and lead still charges at AC)
It was an Orange branded Desire on 2.2 prior to update.
Everything else works great and I was glad to get rid of those stupid Orange game demos.

I went from Orange branded to standard HTC froyo, then to gingerbread and I've had no issues at all. No crashing, no reboots, just improvements.
BTW I've never rooted my phone.
Sent from my HTC Desire using Tapatalk

Thanks all for the advice, I've read about a few having problems with 2.3 but also about the same number with people having no problems. The charging thing with sat nav is a little worrying for me as i use it quite often.
I'm going to wait a while I think for a more clear picture to come out.
Out of intreast though does anyone have a link to a down load of 2.3? I guess you have to be a member on the htc developer site inorder to download it.

scarlet_pimp said:
Thanks all for the advice, I've read about a few having problems with 2.3 but also about the same number with people having no problems. The charging thing with sat nav is a little worrying for me as i use it quite often.
I'm going to wait a while I think for a more clear picture to come out.
Out of intreast though does anyone have a link to a down load of 2.3? I guess you have to be a member on the htc developer site inorder to download it.
Click to expand...
Click to collapse
there you go. 2nd one down
http://htcdev.com/devcenter/downloads

scarlet_pimp said:
Thanks all for the advice, I've read about a few having problems with 2.3 but also about the same number with people having no problems.
Click to expand...
Click to collapse
From what I have been able to gather, it's a very few people having issues. I'll be doing the upgrade sometime this week or weekend when I have time as it's my wife's phone now and she doesn't want me messing with it when she needs it for work.
The charging thing with sat nav is a little worrying for me as i use it quite often.
Click to expand...
Click to collapse
I'm not shocked with this change...I found using Google Navigation was taxing on the power supply with Froyo 2.2 as well, so this basically means it won't charge the phone, but it should keep it running when plugged into the car outlet. And when it comes to navigation, I rarely leave it running with the screen on anyway as I don't need to look at it constantly. I use it to find a route to an unknown destination for me and then only look at it when I'm unsure of a turn or similar. While the screen is off, the phone should still charge as it did on Froyo. If not, then you just need to run Navigation with a full battery or intermittently. Remember, it's a phone, not a full blown dedicated GPS device for navigation, so you can't expect it to run and work all day like a GPS.
I'm going to wait a while I think for a more clear picture to come out.
Out of intreast though does anyone have a link to a down load of 2.3? I guess you have to be a member on the htc developer site inorder to download it.
Click to expand...
Click to collapse
You don't need to be a member...they're just not making it available over the air to everyone due to removal of some settings, etc. But I gather any Desire user can download and install it, even those in the "non supported" regions.

Just to add, the removed wall paper and apps (teeter and flashlight) are included with the downloads as APK files should you need them.
Sent from my HTC Desire using Tapatalk

Several very weird heavy bugs (wifi, Bluetooth, calling networks)

Hey guys,
A year after replacing my Desire with an S2, I wanted to set up the old girl again, giving it to a friend of mine as her first smartphone. Well, now, all of a sudden I have several issues.
First of all: it worked absolutely fine before, up and including the day I turned it off for the last time. Back then, I took out the battery, SIM- and SD card and stored it in its box in my desk. It's rooted (no idea how I did it, hell, t'was over a year ago. I do suspect superoneclick though) and was running 2.2 until last night (more on that later).
Put it together, turned it on, sure thing: battery almost dead, so I plugged it in while checking it out. Turned on wifi, set up market so I could install some apps & updates. Well, I was in the middle of downloading some updates, when it told me there's some minor update for 2.2. I had no SD in, which was mandatory for the update, so I decided to turn it off and put in a card (while the app updates where still coming in). Well here's where it all went downhill. After reboot:
- No more wifi ("error", wifi-symbol turnes greyed-out green)
- No more Bluetooth (just won't turn on, no notification whatsoever)
- Calling one of my other phones resulted in the screen turning off, with no way of getting it back on (although the phone kept working fine, left a message on my answering machine with dead screen)
- mobile networks was activated, yet would not show in notification bar/actually connect.
Out of desperation, I then installed the official HTC 2.3.3 Rom, which - hey presto - got rid of the calling screen and mobile networks bugs.
I researched online, read a lot, and I just don't know what's going on. Bluetooth and wifi errors seem to be connected, but there's two kind of threads on that online (and here): People who run custom Roms and have that problem (I am on stock Rom, with no modification other than root) , and people who just had wifi magically turn on again after two weeks. I don't even understand how it can go from totally fine to being this busted. Was it rebooting while updating? All it updated was apps like Flash & Google streetview, after all.
But honestly, without wifi this is as good as a brick to me. I can't figure out what's wrong. I thought it was a hardware issue, because pretty much all communication was shot, but the major update to 2.3.3 sorted out two of the four issues. Well, I really need wifi. If Bluetooth is shot, I can live with that.
Is there anybody who can tell me what's busted and point me towards the next step? I'm absolutely out of ideas and can't seem to find anything that applies on Google and/or xda.
Thanks a bunch for ANY help & suggestion!
Sent from my GT-I9300 using xda premium

And now we have random reboots, without anything non-stock running on the phone and the device being asleep.
The hell?
Oh, of course I did hard and soft resets. Forgot to mention that.
Sent from my GT-I9300 using xda premium

Vortagh said:
And now we have random reboots, without anything non-stock running on the phone and the device being asleep.
The hell?
Oh, of course I did hard and soft resets. Forgot to mention that.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I think it is your best shot to flash custom recovery such as 4ext and to wipe everything (you can flash it via app so no fastboot required, and it is probably best recovery). By everything, I mean every single partition including sdcard. Then try to install some other rom, for example oxygen and then test the phone. If you need instructions just say.

First of all, thanks for the quick reply!
Yeah, I was thinking about flashing cyanogenmod at one point, but all these bugs put doing that at the end of the to-do list.
Regarding instructions, I'm a bit intimidated about formating the whole thing, simply because I've never used anything like 4ext before. So if you could point me to a good tutorial...
Sent from my GT-I9300 using xda premium

Ok, battery is apparently totally dead, so I have to wait till I can borrow one from a friend.
A question though. You mentioned "format everything". I assume this is, what CWM lists as "format boot/system/data/cache/sdcard/sd-ext"? All of that? Including boot? Just making sure here.
Thanks a bunch!

Well, finally got to ordering a new battery. No change. Phone won't start up, no charge light (although the battery, just like the last one, gets warm).
Guess I'm looking at a major hardware failure and thus a brick
Sent from my GT-I9300 using xda premium

Bluetooth not turning off

Hi guys
I've been getting fairly decent battery life, however am now connecting my phone to the car daily via bluetooth.
I've noticed some battery drain and after checking the built in battery stats and also better battery stats app, my Bluetooth is not turning off when I'm selecting it.
IE, connected on the drive to work, get to work, disconnected then turned off, but showing as constantly on.
Any ideas what could cause this?
Sent from my HTC One X using xda app-developers app

I have noticed the same thing when viewing battery stats although I never use bluetooth and it's always off.
Sent from my HTC One X using xda premium

Any updates or anyone else having the same problem?
I also noticed it just a minute ago. gsam monitor tells that bt was on for 6hrs+ which is the exact same time with phone radio.
Earlier this week connected to my boss' car radio for bt aux, this is the first and last time I used bt. Switched it on&off from settings, nothing changed.
SH26CW, running 4.0.4
Might be useful to give the serial no's since it is useful information about the production site and date.
Sent from my HOX via xdapp

thekillingroad said:
I also noticed it just a minute ago. gsam monitor tells that bt was on for 6hrs+ which is the exact same time with phone radio.
Sent from my HOX via xdapp
Click to expand...
Click to collapse
Same issue here, and same Android version. GSam always reports the same Bluetooth on time as the time unplugged, ie. it's saying that BT has been on all the time, while it's clearly off. I've tried different ways to switch off BT (using widget, using settings, going into Airplane mode and back) but to no avail.
Part of me is suspecting that GSam might be reading the wrong value and falsely reporting it as Bluetooth. But perhaps someone with a different battery monitoring app could check on this and confirm?

It is a bug, to solve it you will need to restart your phone.
This is the only way I find to solve this on stock 2.17/Android 4.0.4.
This bug is caused by turning your Bluetooth on and off.

I faced the same problem? But does that use battery? Actually.the Bluetooth is off.
Sent from my HTC One X using xda app-developers app

neuTrue said:
It is a bug, to solve it you will need to restart your phone.
This is the only way I find to solve this on stock 2.17/Android 4.0.4.
This bug is caused by turning your Bluetooth on and off.
Click to expand...
Click to collapse
Hmm, user fault then hheheheueh
the strange thing is, it does not consume battery at all. ok it's not connected to any device but I would think it would consume more than just %1.
may be non-discoverable makes it use less. not broadcasting anything.

neuTrue said:
It is a bug, to solve it you will need to restart your phone.
This is the only way I find to solve this on stock 2.17/Android 4.0.4.
This bug is caused by turning your Bluetooth on and off.
Click to expand...
Click to collapse
A restart sometimes fix the problem but not always. Today I had bluetooth turned off then after restarting by four hours my device reports that bluetooth has been on for 4 hours even though I didn't turn it on and it shows that it's off.
Sent from my HTC One X using xda premium

Glad I'm not the only one
I do find a reboot fixes it, but I don't want to have to reboot my phone every time I get out the car.
I'll get my serial number when I'm home and see if its the same
Sent from my Nexus 7 using xda app-developers app

I'm now having a chat with HTC live support about JB update and also asked the question about BT off issue.
He said, please follow the following steps.. Waiting for what he'll say..
So he suggested booting in safe mode, going to applications? >> manage, uncheck.. ? I'm not familiar with safe mode so I cannot surely say what he is talking about.
Has anyone tried this? Did it work?
So he sad that this will solve if an application is triggering the problem, but I haven't used any applications that use BT.
So, the next suggestion is factory reset, bullsh*t. sorry guys =)
useless post may be, but confirms that HTC official support has no fixing for this.

thekillingroad said:
Hmm, user fault then hheheheueh
the strange thing is, it does not consume battery at all. ok it's not connected to any device but I would think it would consume more than just %1.
may be non-discoverable makes it use less. not broadcasting anything.
Click to expand...
Click to collapse
Hahaha, that's funny and more towards Apple ideology.
Bluetooth was designed to be efficient. But, if its running then it consuming energy ,and that's something I don't like.
I already checked logcat/kmsg ,but nothing about this Bluetooth issue.
I didn't see anyone on JB came to complain about this, let's see what the offical JB has to offer.
hatemk said:
A restart sometimes fix the problem but not always. Today I had bluetooth turned off then after restarting by four hours my device reports that bluetooth has been on for 4 hours even though I didn't turn it on and it shows that it's off.
Click to expand...
Click to collapse
Try to disable "fastboot", and give it a try.
I am afraid nothings more can be done on stock, other option is to wait for JB and hope it already fixed.
thekillingroad said:
I'm now having a chat with HTC live support about JB update and also asked the question about BT off issue.
He said, please follow the following steps.. Waiting for what he'll say..
So he suggested booting in safe mode, going to applications? >> manage, uncheck.. ? I'm not familiar with safe mode so I cannot surely say what he is talking about.
Has anyone tried this? Did it work?
So he sad that this will solve if an application is triggering the problem, but I haven't used any applications that use BT.
So, the next suggestion is factory reset, bullsh*t. sorry guys =)
useless post may be, but confirms that HTC official support has no fixing for this.
Click to expand...
Click to collapse
Safe mode is a mode in Android, that will will disable all the 3rd party installed apps. Similar to safe mode in Windows. After your turned on your phone, just press on the volume key and it will get you there.
Beside that, I never trust customer support, and I never had a good experience with any of them.
The only good thing is about companies offering customer support, is they add job opportunities into the economy.

This problem just crept up on me. I noticed the battery was lower than normal, I checked BBS and it seems like BT never turned off. A reset would solve the problem until I turn BT back on again.
Does anyone know if this has been fixed with 4.1?

sefuwl said:
Does anyone know if this has been fixed with 4.1?
Click to expand...
Click to collapse
It seems so, at least on my One X G Sam is now reporting the correct BT on-time, whereas pre-JB it was continually on, clock ticking even after turning it off.
Sent from my HTC One X using Tapatalk 2

bluetooth
no probs here:good:

Camera not detected at all

So issue started as follows:
a. For a few days, I've noticed that camera will give very blurry photos and videos. I tried a few things (including cleaning laser/camera lens with a cloth), but it wouldn't work.
b. Decided to restart phone today and see if that helps (turn off and on right?)
c. I now get error "Unable to start the camera" when I tap on the camera app.
I have tried the following:
a. install 3rd party app - won't work
b. restart phone (multiple times) - won't work
c. clear data/clear cache, disable, enable, remove permissions and allow permissions for Camera app - won't work
d. reboot phone in safe mode - won't work
e. Go into diagnostic mode using #*#*3434*#*# to test camera. Guess what, there are no options to test camera!
f. Go into diagnostic mode and test flashlight. Flashlight won't turn on anymore. Also, I found that the system's flashlight app is gone.
All this leads me to believe that for some reason the phone is not detecting the camera hardware anymore. I'm out of ideas. I bought the phone overseas, and local HTC told me to return it overseas or pay a handling fee of $100 and they'll look at it, but will probably not be able to do anything anyway.
Phone is just a bit over 1 month old.
Any ideas?

I'm having the same problem. I'm rooted on unlocked HTC 10 on stock 2.41.617.3. I'm S-On. I've tried force stop and delete cache and data. Tried safe mode and tried a 3rd party camera app. I just got by phone back from HTC to repair the camera and it worked before flashing the January security update and rooting it. Afterwards, I now get "unable to start the camera"
Sent from my Galaxy S4 using XDA Labs

NickKG81 said:
I'm having the same problem. I'm rooted on unlocked HTC 10 on stock 2.41.617.3. I'm S-On. I've tried force stop and delete cache and data. Tried safe mode and tried a 3rd party camera app. I just got by phone back from HTC to repair the camera and it worked before flashing the January security update and rooting it. Afterwards, I now get "unable to start the camera"
Sent from my Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
So, I completely wiped data and reset factory settings, but camera still wouldn't start.
Flashed phone back to Taiwanese version, and it's now working, but original issues are back, i.e. blurry camera that can't focus on anything. I restarted phone a few times to see if it would go back to "unable to start the camera", but it's still working, just blurry and unable to focus. I'm still going through the various updates now. Have notification for Nougat. will try that and test camera again.
[UPDATE]
Interesting update: So, I upgraded to Nougat just now, and after restarting, I tested camera, it's not working anymore. Here's my speculation: 1) camera module (hardware) is broken/fkd up/stuffed, but only partly? Whereas Android 6 will let it work, but blurry and no focus, Android 7 just won't let it work at all. That's just my theory that makes a little sense atm. Anyone else?

I think you are correct, i would send it for warranty (if you still have that)
Good luck !

I did a hard reset and the camera started working again.
Sent from my Galaxy S4 using XDA Labs

Mr Hofs said:
I think you are correct, i would send it for warranty (if you still have that)
Good luck !
Click to expand...
Click to collapse
Got mine overseas about a month ago, posting it on Monday.
NickKG81 said:
I did a hard reset and the camera started working again.
Sent from my Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
Lucky! Is yours ANY blurry or is it fully functional? Also, if it stops working again, check whether your flashlight works (mine wouldn't/isn't).

ameel said:
Got mine overseas about a month ago, posting it on Monday.
Lucky! Is yours ANY blurry or is it fully functional? Also, if it stops working again, check whether your flashlight works (mine wouldn't/isn't).
Click to expand...
Click to collapse
It was blurry when I purchased it used. That's why I sent it back to HTC since it was under warranty. It looked like it was a bad auto focus module, although HTC never said so. Fixed and was working well, then today (after the reset I posted about), then today it stopped working. I'm going to RUU tonightor tomorrowand install apps one by one. It seems to be softwa rerelated.
Sent from my Galaxy S4 using XDA Labs

NickKG81 said:
It was blurry when I purchased it used. That's why I sent it back to HTC since it was under warranty. It looked like it was a bad auto focus module, although HTC never said so. Fixed and was working well, then today (after the reset I posted about), then today it stopped working. I'm going to RUU tonightor tomorrowand install apps one by one. It seems to be softwa rerelated.
Sent from my Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
I'm sure it will work if you go to android 6, but it will be blurry. It won't work after you restart in android 7. That's my experience

My wife's 10 was having this issue. Neither a factory reset nor an RUU helped. But randomly it just started working for her. There were app updates from Google for photos and chrome but I have no idea if they're related but nothing else changed. Really strange!
Edit: a day later the camera is not working again.
Sent from my HTC 10 using Tapatalk

I've been experiencing the very same problem and the only thing that helps is hard reset or RUU. It doesn't always work on the first try, but after 3-4 attempts the camera starts working perfectly for a period of time -- sometimes a week, sometimes a month and a half (my personal record, which was set a few days ago, when camera died again). Then I always have one day of the focus getting disabled followed by a complete shutdown with all the symptoms described by OP (no flashlight icon, 'unable to start' message). Has anyone found a permanent solution to this problem?

I have the same problem with my htc

I have the same problem on a non-rooted Verizon HTC 10... the camera app won't open, the flashlight won't work, the camera shortcuts disappeared from the top Nougat menu, and any other app I try says it can't find the camera.
I'm unable to find any troubleshooting or debugging methods yet... any suggestions? I have Android Studio but I haven't learned much of it, I'm wondering if Developer mode or the Studio USB debugging can help...

dhinged said:
I have the same problem on a non-rooted Verizon HTC 10... the camera app won't open, the flashlight won't work, the camera shortcuts disappeared from the top Nougat menu, and any other app I try says it can't find the camera.
I'm unable to find any troubleshooting or debugging methods yet... any suggestions? I have Android Studio but I haven't learned much of it, I'm wondering if Developer mode or the Studio USB debugging can help...
Click to expand...
Click to collapse
A few things that seem to have helped some people are:
removing SD card and restarting the phone without it;
clearing camera app's cache;
uninstalling all 3rd party apps that might be interfering with the camera;
RUU-ing the phone with an official firmware (you don't need root or S-OFF for that, as long as you don't try to downgrade from Nougat to Marshmallow).
Nothing but the last method worked for me. Though it doesn't do the trick every time and even when it does, it is only a temporary solution, as the problem keeps popping up again after a while. Last time the camera in my HTC 10 started working without any software interference from my side: I went on a hike in cold weather and, as I hypothesise, something about it (temperature differential? pressure change?) restored camera functionality for a couple of weeks, after which it died again. This incident led me to believe that this is a hardware problem and the camera module simply isn't securely connected to the motherboard in our phones or something. My wild guess is that RUUing might sometimes help simply because of the heat rewriting firmware produces.

werbliben said:
A few things that seem to have helped some people are:
removing SD card and restarting the phone without it;
clearing camera app's cache;
uninstalling all 3rd party apps that might be interfering with the camera;
RUU-ing the phone with an official firmware (you don't need root or S-OFF for that, as long as you don't try to downgrade from Nougat to Marshmallow).
Nothing but the last method worked for me. Though it doesn't do the trick every time and even when it does, it is only a temporary solution, as the problem keeps popping up again after a while. Last time the camera in my HTC 10 started working without any software interference from my side: I went on a hike in cold weather and, as I hypothesise, something about it (temperature differential? pressure change?) restored camera functionality for a couple of weeks, after which it died again. This incident led me to believe that this is a hardware problem and the camera module simply isn't securely connected to the motherboard in our phones or something. My wild guess is that RUUing might sometimes help simply because of the heat rewriting firmware produces.
Click to expand...
Click to collapse
Oh *smack* sorry I forgot to mention that I already tried clearing the camera app's cache, wiping cache from recovery menu, and factory resetting the phone.
I think it's a hardware issue since I think it got a little wet from sprinklers and I read the phone isn't water resistant, and also that the camera module is flaky anyways... Verizon accidentally cancelled my insurance without telling me and I haven't seen yet that HTC covers it on warranty.
I'll try these other things you suggest, but do you think it would be worth trying to have HTC repair it? It'll be worth it for $350 or less, or I could try a local shop, though I think they'd just do the same thing I would (research it on Google, buy the necessary repair parts, then painstakingly fix it), but I've seen in repair videos that this phone is very fragile and difficult to work with, so I'm not sure all that time and effort would even be worth just buying a new version outright, and I'd like the phone to work for the eclipse!.

Same Problem here, since Saturday... [emoji85]

dhinged said:
I'll try these other things you suggest, but do you think it would be worth trying to have HTC repair it? It'll be worth it for $350 or less, or I could try a local shop, though I think they'd just do the same thing I would (research it on Google, buy the necessary repair parts, then painstakingly fix it), but I've seen in repair videos that this phone is very fragile and difficult to work with, so I'm not sure all that time and effort would even be worth just buying a new version outright, and I'd like the phone to work for the eclipse!.
Click to expand...
Click to collapse
I actually went to a repair shop about a month ago and was told that they were certain part replacement would leave significant marks on the metal body =/ If you carry the phone in a full case, I guess this should not be a big problem. AFAIK, an official HTC repair shop would just replace the phone under warranty in cases like this due to how low simplicity of disassembly was on designers' priority list when 10 was being sketched out, but you're saying Verizon canceled your warranty?

I also face this unable to start camera.
My software no is 2.51.617.11
I live in Myanmar (Burma). No one know this problem including HTC Myanmar.

Apparently there are a handful of us who have faulty cameras. Haven't heard anything from HTC. I have tried everything listed here and more. No luck. The only way my camera works is on older firmware (1.9.xxx.xx) and running Marshmallow.

well my htc 10 started playing up today, camera wont start when you touch the camera app on the screen..ive had this phone for 9 months , my warranty expires in march 2019, ive tried all the above methods none worked, phoned HTC uk up and they said to send it in..i hope they replace it with another unit ?..if they do replace it with another unit will the wrranty be transferred over to that, ie expire in march 2019? i also noticed that the flashlight app doesnt work it just says on screen "loading"..

I have the exact same problem, tried all the suggestions, but still it says 'Unable to start camera'. I even opened up the phone, and replaced the camera with another HTC 10 which had water damage. Problem still exists, which leads me to believe that the camera isn't the issue, it might be the mainboard it's connected to in combination with Nougat? The other case can be that the broken phone I got the camera from might have the same problem.... allthough I think that's unlikely. I'd like to order another camera to make sure its not that, but can't really find one. Anyone got any further with this issue?