Related
Hi, I'm considering going back to WMobile phones and seriously considering the Kaiser. I currently have the N73 but had many wm5 phones before, SPV m600, Trinity, XDA Orbit, Wizard etc etc, all had annoying little "bugs".
I know the Kaiser is only just out, but can anyone tell me if you have noticed any of the following?
1) delay in ringing when receiving an incoming call. i.e. people on the other end hears a ring, but my phone takes about 3seconds before it rings...v. annoying!
2) delay in waking up.
3) slow response in dialing, i.e. when pressing a number on the dial pad.
4) Missing incoming comes, i.e. full reception but people unable to get through. Extremely annoying.
5) Rebooting itself
6) Alarm not going off.
Hows the call quality?
Anyone used and have any issues with the T9 pad, think that's what it's called. I use to use this, but gave me problems when i switched back to virtual keyboard, e.g. wouldn't switch back at all.
Sorry for all the questions.
1) Haven't tested this yet, i'm hoping this isn't the case though...!
2) Wakes up pretty quick, no unbarable lag
3) Same as 2) - all seems pretty responsive, no bad lag
4) Never had that issue before, don't expect to get it with the Kaiser
5) Nope, although i haven't installed any other apps etc yet...
6) Same as 4)
I can only really compare with the Universal (as that's the only other WM phone i've owned)... my initial impressions are that it's a lot quicker than the Universal... maybe that's partially due to the fact that i haven't installed any bits yet... or really tweaked it.
The 3 second delay was REALLY annoying.... as i'd have to start every phonecall with: "hello....... hello? heeeelllllllllo?" lol... i hope this isnt the case with the Kaiser!
Also i think a lot of the noticable improvements are also due to the fact that im using a vanilla HTC phone, as opposed to a crappy T-mobile 'runined' one! Also i think WM6 has brought in a lot of changes which are noticeably improved over WM5.
EDIT: oh and the only thing that really 'bugs' me - is that i'm used to the lovely VGA Screen of the Universal, so dropping down to QVGA is rather noticable... text looks blockier and using Cleartype seems to make it alot fuzzier than on the Universal.... but that's my only really negative point so far.... hopefully it'll be the ONLY one
EDIT2: Something else i just thought of.... the fact that when my Universal locked up... if i didnt have my Stylus on me (which i usually didnt) and i didnt have a small pin-like object to stick into the reset hole... i was SCREWED... which REALLY pi**ed me off.... countless times i'd be on the train home from work, about to email a friend... only to have my phone lockup... then i'd have to wait an hour before i could reset it and start writing... GRRRRR. Anyway, the Kaiser actually turns off when you hold down the power button... simple... and GREAT! (the power button on the Universal was so stupid.... in my opinion.... was there any way (except by using 3rd party apps) to actually turn the damn thing OFF?! lol)
Hi
hongsit said:
Hi, I'm considering going back to WMobile phones and seriously considering the Kaiser. I currently have the N73 but had many wm5 phones before, SPV m600, Trinity, XDA Orbit, Wizard etc etc, all had annoying little "bugs".
I know the Kaiser is only just out, but can anyone tell me if you have noticed any of the following?
1) delay in ringing when receiving an incoming call. i.e. people on the other end hears a ring, but my phone takes about 3seconds before it rings...v. annoying!
2) delay in waking up.
3) slow response in dialing, i.e. when pressing a number on the dial pad.
4) Missing incoming comes, i.e. full reception but people unable to get through. Extremely annoying.
5) Rebooting itself
6) Alarm not going off.
Hows the call quality?
Anyone used and have any issues with the T9 pad, think that's what it's called. I use to use this, but gave me problems when i switched back to virtual keyboard, e.g. wouldn't switch back at all.
Sorry for all the questions.
Click to expand...
Click to collapse
1) The delay is/was caused by the CPU/OS coming out of standby. With PDA type Windows Mobile devices they have a standby mode where the whole operating system is suspended. The mobile chip remains powered and when a call comes in it has to send a wake up request to the CPU and OS. It is the time the CPU and OS takes to become responsive that causes the delay. I noticed this delay was quite a lot on the Toshiba G900, several seconds or rings before it had woken up to sound the internal audio to alert you to the call. Sometimes it wouldn't wake at all :-(
The Kaiser wakes very quickly, hardly any delay at all, they have certainly put in a lot of work in this area.
Windows SmartPhones don't have this problem as they remain "always on" so respond without delay even though they may look off.
2) Answer above, very quick, almost instant.
3) Seems okay to me.
4) This is probably the OS failing to wake up, I would doubt this happens on the Kaiser.
5) Okay so far.
6) This again is related to the CPU/OS failing to wake up to a request. It is likely the phone you have experienced this with has some problems waking up when asked and would explain all your concerns.
Hope that helps.
Regards
Phil
I read on another thread regarding the assembly which houses the green and red call buttons being loose. What is the opinion of other users over here. I am asking this as I am considering buying one soon to replace my Touch
Regards
Yes the whole section moves slightly on mine, it must just be where they float on a rubber section underneath.
I hadn't noticed this until now, why is this a problem? If it was fixed two tight the keys would scrape against the sides when pressed. Makes sense there is some space.
Regards
Phil
The buttons feel a bit 'loose' but no more than in any other device (the buttons on my PSP for example).
Thanks for the reply guys, kaiser sounds promising, just hope it continues to impress.
hongsit said:
1) delay in ringing when receiving an incoming call. i.e. people on the other end hears a ring, but my phone takes about 3seconds before it rings...v. annoying!
Click to expand...
Click to collapse
There are two contributors to this:
One is a registry entry, where all of the "standard" options cause a 3 second pre-ring delay and 3 second delay between rings. This can be fixed in the registry.
The second is network delay. The caller will hear ringing before your phone rings (usually 1-2 rings) no matter what phone you use. I've had such delays with every mobile phone I have ever used, smart or not. If you try the registry hack (search around for the exact key, numerous posts on it and I can't remember the exact registry key at the moment) and are still not happy, you have one option to reduce ring latency - get a landline.
Hey there,
it seems that everyweek.. there's a new problem with the Kaiser I have. Starting to hate WM platform. Just like how I hate Windows for PCs.
Well, although I have the Screen Tap Sound setting enabled, my Kaiser doesn't seem to produce a sound feedback. I made sure volume is set on the highest even.
I can hear feedback on my keypad (although I usually have it disabled, I have it on just for testing purposes), I'm unable to hear the screen tap feedback sound.
I'm wondering, what's the screen tap sound file name? I may have deleted it accidentally. Would anyone care upload theirs?
Or perhaps I may have damaged the registry file. What is it binds on?
Thanks in advance.
After further investigation, the issue is caused by FTouchFlo v.1.4.1.
A few other users reported similar issue after installing FTouchFlo v.1.4.1.
I'm not clear whether other users who are expereriencing the same issue are running Kaiser/TyTN II.
Hopefully, efrost (the developer of FTouchFlow), will address this issue in the future release.
I have a slightly different issue. Normally the screen taps remain as I have set them. However I am using PhoneAlarm and when I change to a profile in which I have set all sounds at zero value and then later come back to a normal profile I loose the screen tap sounds. The only solution is to go back to the sound settings and reactivate the screen taps again from there.
hidea said:
After further investigation, the issue is caused by FTouchFlo v.1.4.1.
A few other users reported similar issue after installing FTouchFlo v.1.4.1.
I'm not clear whether other users who are expereriencing the same issue are running Kaiser/TyTN II.
Hopefully, efrost (the developer of FTouchFlow), will address this issue in the future release.
Click to expand...
Click to collapse
Yep I can confirm my screen tap is disabled and I do have FTouchFlo installed on the TyTN II
yeah i got the same problem here...is there a way to get the screen tap sound back...maybe something in the reg??? any ideas???
The other way aroud is more or less the same.
On my device it is turned on and I cannot get it turned off.
Checking, or unchecking does not change anything.
Is there an app that can automatically turn on the speakerphone when the phone is placed face down? I think this would be a pretty cool addition. Any thoughts?
Gyrator can detect when you are using the phone and turn it face down and run a keypress for you. No idea if that could be used to turn on the speakerphone though.
Neat idea until your laying on your bed talking to your gf when your wife walks in!!!
[Note]Not that I would ever do that[/Note]
Would be a neat feature though, as long as you could disable it.
player911 said:
Neat idea until your laying on your bed talking to your gf when your wife walks in!!!
[Note]Not that I would ever do that[/Note]
Would be a neat feature though, as long as you could disable it.
Click to expand...
Click to collapse
Im not married, so no worries there! I just thought it would be convenient if I had to put the phone down for something then it would automatically switch to speaker.
shirreer said:
Ok, if you like the TD2's speakerphone on flip stunt, then here's a cool tip for you...
Using Gyrator:
- Add a new "Rotation" event.
- Set application to Phone on the "Application" tab.
- On the "Orientation" tab check on "Portrait", "Face-down", and "Face-up".
- On the "Actions" tab check on "Simulate Keypress".
- Goto "Advanced" tab and select key "F16,127" which triggers the windows-native "Speakerphone Toggle event".
Done.
Now, starting NOT on speakerphone, whenever you put your phone on a level surface --facing up or down-- during a call, the speakerphone will toggle ON -> Moreover, if you pick it up it should toggle OFF. Good enough?
Cheers
P.S. You can also do the same for a "Stylus Out" event to fire when "Phone" application is focused, thereby simultaneously toggling on the speakerphone and starting up a new Note (default behaviour) whenever you take the stylus out during a call. Aren't we the lazziest lot..
Click to expand...
Click to collapse
here ya go.. I read this in the diamond forum the other day
Fascinating stuff. All of this customization is one of the things keeping the Fuze in my pocket still. Once in a while the bulk and weight drag me down, then I fall back in love the the ability to tinker the thing to exactly how I like it.
Directly related to this. I'd be curious to know how well the speakerphone works on a technical level when face down. I believe the speakerphone microphone is still on the front of the Fuze which I assume will negatively affect the overall performance.
I've tried this but I cant get it to work on a call out. Maybe I just put it in wrong. Let me know if you guys were able to get it to work.
gastric123 said:
Fascinating stuff. All of this customization is one of the things keeping the Fuze in my pocket still. Once in a while the bulk and weight drag me down, then I fall back in love the the ability to tinker the thing to exactly how I like it.
Directly related to this. I'd be curious to know how well the speakerphone works on a technical level when face down. I believe the speakerphone microphone is still on the front of the Fuze which I assume will negatively affect the overall performance.
Click to expand...
Click to collapse
I thought the microphone was at the bottom side ofthe phone. just above the USB port? Am I wrong? Thats what it looks like on my fuze.... otherwise I have no idea what that little hole is!
Aaron McCarthy said:
I thought the microphone was at the bottom side ofthe phone. just above the USB port? Am I wrong? Thats what it looks like on my fuze.... otherwise I have no idea what that little hole is!
Click to expand...
Click to collapse
Yes, that is where the microphone is at. I usually turn my phone face down anyway while on speakerphone since the speaker is on the back and makes it easier to hear.
Aaron McCarthy said:
here ya go.. I read this in the diamond forum the other day
Click to expand...
Click to collapse
I can't get this to work...any ideas?
I was certain this feature was included out of the box and I had just lost it when I flashed new ROMs.
My Touch Incall Screen Tweak can perform this function - just search for it on here - its normally on the first page of this sub-forum. (not in a position to find the link, sorry).
Cheers,
Steve
Aaron McCarthy said:
here ya go.. I read this in the diamond forum the other day
Click to expand...
Click to collapse
Mate, stop reading outdated stuff! Find & use "Touch-InCall-Screen-Tweak" program, it is SUPER cool; its like magic...auto speakerphone whenever the device is not on your ear, very customizable too.
Cheers
hey guys, I'm about to trade my htc desire for a nexus one and have read up on a few problems, and I wanted to find out first hand from you guys wether they're actually problems, or wether they are a load.
Which leads me to my questions.
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired)
3. the touchscreen randomly stops working
4. 3G connectivity issue
5. Wifi problems
6. Proximity sensor sensitivity issue
7. earpiece: insufficient volume
and lastly -
Is there any reason why you would not recommend me selling my desire and buying a nexus?
Thanks,
Brandon
It would be easier to have them numbered
1. Trackball - never heard of it.
2. Power button - never had anything on mine, but there's a good reason to believe there was a faulty batch out there - some had to exchange theirs.
3. Touchscreen - The issue is that it starts "missing" the presses, registering way below. Pressing the power button twice (entering and exiting standby) "cures" it. A real issue, happens very rarely.
4. 3G - opinions are split on it, reported only by vocal minority and only in areas barely covered by 3G, and only long time ago. Personally, never saw anything that could be considered as "issue". Actually, rather good reception and good data rates over bad connections.
5. WiFi - again, depends on what "issue" is. It's not completely flawless, for example, fails connecting to encrypted network w/ Cisco 521G. Haven't had any problems on mine, though.
6. Proximity sensor - never heard of it.
7. Volume - never heard of it.
To the last question - why would you want to do that? You have a device with very similar specs that runs very similar firmware. Froyo is already out for Desire, AFAIK, and that exchange would only bring you the trackball notifications and the future updates (Gingerbread). Is that the reason for you to switch?
P.S. All or almost all of the issues listed above would be similar for both phones, since they're almost identical.
Jack_R1 said:
To the last question - why would you want to do that? You have a device with very similar specs that runs very similar firmware. Froyo is already out for Desire, AFAIK, and that exchange would only bring you the trackball notifications and the future updates (Gingerbread). Is that the reason for you to switch?
P.S. All or almost all of the issues listed above would be similar for both phones, since they're almost identical.
Click to expand...
Click to collapse
Thanks for the reply!
The problem is that the there are only about 4 chefs cooking for the desire (and about 5 others uploading their own version of the 4 roms). And the battery life on the new froyo ROMs are terrible. I used up the whole battery in about 6 hours with 3g not enabled, and brightness at the minimum.
and there seems to be much more support for the nexus. (XDA support that is)
+ there are much more cases available for the nexus, I think it looks better, and I really love the idea of the trackball and how it can change colors
P.S I forgot to ask how are the capacative buttens?
Some have said they don't exactly work (you have to press them a few times before it works)
I remember reading somewhere that you have to press them a bit above the buttons and they work fine. Is this true? or are some devices just randomly screwed?
Thanks,
Brandon
No to all.
Atleast I didn't notice
Any reason not to just keep the Desire? The n1 is great but the Desire is nearly identically and slightly better in some ways.
brandon1108 said:
hey guys, I'm about to trade my htc desire for a nexus one and have read up on a few problems, and I wanted to find out first hand from you guys wether they're actually problems, or wether they are a load.
Which leads me to my questions.
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes- Never had this problem......
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired)- Um, not for me.... But I have heard this happening to people.
3. the touchscreen randomly stops working - NEVER ever has this happened
4. 3G connectivity issue - I only use wifi since it's everywhere. More efficiant and faster!
5. Wifi problems - None for me.
6. Proximity sensor sensitivity issue - Nope
7. earpiece: insufficient volume - Nope, I find it too loud sometimes. But, I do have sensative hearing.
and lastly -
Is there any reason why you would not recommend me selling my desire and buying a nexus? No reasons honestly. They are both pretty similar except for support and design as well as a few other diffs. The only thing I like about the desire is it's hardware keys and chin
Thanks,
Brandon
Click to expand...
Click to collapse
brandon1108 said:
Thanks for the reply!
The problem is that the there are only about 4 chefs cooking for the desire (and about 5 others uploading their own version of the 4 roms). And the battery life on the new froyo ROMs are terrible. I used up the whole battery in about 6 hours with 3g not enabled, and brightness at the minimum.
and there seems to be much more support for the nexus. (XDA support that is)
+ there are much more cases available for the nexus, I think it looks better, and I really love the idea of the trackball and how it can change colors
P.S I forgot to ask how are the capacative buttens?
Some have said they don't exactly work (you have to press them a few times before it works)
I remember reading somewhere that you have to press them a bit above the buttons and they work fine. Is this true? or are some devices just randomly screwed?
Thanks,
Brandon
Click to expand...
Click to collapse
Ugh, I do have issues with the capacitive buttons. Like I said above, I envy hardware keys. It's not that they don't work, they just arent calibrated. You need to touch way above where they are for them to register. If you press the button where its placed exactly they don't work.
NOTE: I should let you know about all the cool things the Menu button does (second button with the lines) I just found out about the Menu button on my Nexus Lol!
I would do that trade and not have any issues at all. The nexus is The most active device right now and will be thru this year at least. Those problems you listed are not a big deal, the power button only fails for some people. Use track ball wake and you have nothing to worry about. Everything else is not really a problem.
brandon1108 said:
P.S I forgot to ask how are the capacative buttens?
Some have said they don't exactly work (you have to press them a few times before it works)
I remember reading somewhere that you have to press them a bit above the buttons and they work fine. Is this true? or are some devices just randomly screwed?
Thanks,
Brandon
Click to expand...
Click to collapse
They're all screwed equally All the capacitive buttons register too high, so you have to press higher to hit them. At least they're consistent.
not a single mention of white notification burn-in. seems common.
brandon1108 said:
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes
3. the touchscreen randomly stops working
7. earpiece: insufficient volume
Thanks,
Brandon
Click to expand...
Click to collapse
yup.
1. get stuck on going "down". kind of annoying but a spazz around with it fixes it.
2 yup, cant get it to unlock sometimes.
3, sort of. wouldnt mind it louder and of better quality. More depth.
mtl171 said:
not a single mention of white notification burn-in. seems common.
Click to expand...
Click to collapse
:O I remember someone talking about it in the desire forum - If I use a black notification bar I should be fine right?
Brandon,
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes No
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired) Yes & Yes gettting repaired by HTC as we speak.
3. the touchscreen randomly stops working No - used to occasionally before Froyo but not anymore
4. 3G connectivity issue No
5. Wifi problems No
6. Proximity sensor sensitivity issue No
7. earpiece: insufficient volume No
8. how are the capacative buttons? Fine, If you swipe them downwards in the opposite direction but the same manner as you would, to select the notification bar. If you tap them with the pad of your finger instead of the point it also a non issue. OTOH tapping with the point of your finger you just need to tap slightly below.
PurpleSmurfLlama
I disagree and do not think the majority of power button failures are due to poor maintenance. Is your poor maintenance theory just a hunch perhaps? I keep my phone nice and clean, no obvious crap beneath the button. In another thread someone who had a failing power button dismantled his phone an reported the power button presses a switch that is connected via a ribbon cable to a circuit board. No amount of cleaning these fixed it for him. Furthermore people who have had their "power buttons" repaired have reported that all these these items appear to have been replaced when they get their repaired phone back from HTC. Same phone comes back with new IMEI because the circuit board has been changed as part of the fix. To me this suggests that on the faulty units the issue goes deeper than just the button and a users maintenance of it. I am just hoping that the FIX is permanent.
I've had my Nexus One for a few months now and I can't say I've had any of those problems, well my WiFi sometimes just disconnects, but I think that's just to do with the distance between my room and the router. As for button and trackball problems there's been none, even after a horrifying ordeal where a friend spilt beer on my N1 then instantly after in the panic I dropped it in the sand :/
The swap in my opinion can only be based purely on aesthetics, IMO the N1 is nicer, not being biased, the Desire is beautiful, I just think the N1 is more sleek. Hope this helps even a little.
Sent from my Nexus One using XDA App
brandon1108 said:
:O I remember someone talking about it in the desire forum - If I use a black notification bar I should be fine right?
Click to expand...
Click to collapse
Yes exactly, just use black color and you'll be fine. That white is such a horrible color anyway.
brandon1108 said:
Does your nexus one have any of the following problems:
1. trackball gets stuck sometimes
2. the on/off/standby switch has stopped working (or you have had to send it back to be repaired)
3. the touchscreen randomly stops working
4. 3G connectivity issue
5. Wifi problems
6. Proximity sensor sensitivity issue
7. earpiece: insufficient volume
Click to expand...
Click to collapse
How about a poll?
1. no
2. switch is "soft" on the replacement I just received (was fine on original phone and 1st replacement)
3. no
4. YES! RECEPTION IS A BIG PROBLEM! AS IS 3G CONNECTIVITY (3 bars and websites won't load WTF?)!
5. no
6. no
7. yes
maybe add:
8. PINK screen - YES. Just keep asking HTC for replacements, screw them for their poor quality control.
9. camera color tint (blue for me) - YES. Ok for me ... but I made go another replacement binge if I find anything at fault with this phone.
10. I also experience bad call quality - got fixed by the replacement.
1. Trackball - NO problems here.
2. Power button - NO problems here.
3. Touchscreen Unresponsive - Roughly once or twice a month. I put it to standby and back, and it's fixed. I've noticed that only certain ROMs do this. I never had the problem on FRF50 or FRF83, but I have once in a while on FRF91.
4. 3G Connectivity - NO issues.
5. Wifi - NO issues.
6. Proximity sensor - NO issues.
7. Earpiece volume - NO issue, but I have always had one of Pershoot's kernels installed, which includes an "audio fix."
I would have no hesitation recommending a nexus. Though, if you're a gamer, I'd say get a Galaxy S phone because of the better GPU.
#3 is the only one that consistently pisses me off.. all the other ones are software and can and are fixed with different roms.
Wondering if someone (hopefully more than one) can check something to see if this is an issue with my particular phone or something related to the software/hardware. It seems that when a call is placed or received, the proximity sensor goes to "far" and won't reset until it is uncovered and then re-covered. I have searched through the Verizon HTC One forums and have not found anything related to this issue.
If the proximity sensor is covered, and I make a call (via bluetooth headset (double click for last dialed)) or receive a call, the proximity sensor goes to the uncovered state. It then stays in that state until I uncover and then re-cover it. How I checked this was using Elixir 2 and checking the sensor data. I also set up variables in Tasker and Automagic.
So, this was my test procedure:
I start the sensor data in Elixir 2 for the proximity sensor. I cover the sensor with my finger (it now shows "near"). I use my bluetooth headset to place a call. The screen comes on with the current call. I back out of the current screen (the phone screen) and get back to Elixir 2 sensor data. The sensor now shows "far". From that point on, until I uncover the proximity sensor and then cover it, it shows far. I set up variables in Tasker and Automagic that show the same results.
I am running the stock debloated ROM. Rooted and S-Off.
EDITED:
So, this is the latest for my issue. I went from stock ROM to ViperOne 5.8.0. I am still getting the same results. So, I think I have eliminated the software side of it. Would that be right? So, it could be the firmware or the hardware? I'm still wondering if it's my phone only or if it is an issue with the HTC One in general. Is there anyone that can check this? Or give me another route to take?
I'm on ViperOne 5.8.0
Android 4.4.2
Senses 5.5
Any other info you might need, please just ask.
Some thing like that happened to me and i posted a thread and no answers.
My problem is that when the phone is in my pocket only one speaker is ringing(the lower one) and when on the desk face up both of the speakers are ringing.I noticed this affects only the call option(if i get a sms/notication and it's in my pocket/desk both of the speakers work).i've made all off the tests i can find am the problem seems to be from software.When i cover with my finger the sensor and some ones call s me only the bootom speker is ringing,when removing my finger from the sensor and receving cal SURPRISE both of the are ringing.
I've change the software ARHD 53 with ELEMENTALX Kernel.
Cid TMOB-101
alex.foto said:
Some thing like that happened to me and i posted a thread and no answers.
My problem is that when the phone is in my pocket only one speaker is ringing(the lower one) and when on the desk face up both of the speakers are ringing.I noticed this affects only the call option(if i get a sms/notication and it's in my pocket/desk both of the speakers work).i've made all off the tests i can find am the problem seems to be from software.When i cover with my finger the sensor and some ones call s me only the bootom speker is ringing,when removing my finger from the sensor and receving cal SURPRISE both of the are ringing.
I've change the software ARHD 53 with ELEMENTALX Kernel.
Cid TMOB-101
Click to expand...
Click to collapse
Well, seems to be the same here. I have this posted under the Verizon HTC One > One Q&A, Help & Troubleshooting as well as here and at the Android forums. It seems that either no one else is having this issue, no on cares or no one can run this test with free programs. I dunno. The problems I have is that I use by bluetooth headset most of the time. I am a blue collar worker and try not to pull my phone out of my pocket when my hands get filthy. But, when I take or make a call using the headset, the display kicks on and then stays on because I can't use the proximity sensor to turn the screen back off. Guess I'll have to try other routes. This sucks. LOL
I haven't heard of the other issue you are referring to. I can tell you that I have not had that issue with my One. Doesn't mean that it's not a problem. Have you checked the Sounds settings for pocket mode and quiet ring on pickup? If so, I think I would try to either get with Verizon about it or maybe even HTC. It definitely sounds like it could be a phone issue. But I'm kind of new to all of this.
Same problem here, when i'm in a call the screen go on, very annoying.
Now i'm trying this app "rezound prox sensor calibrator"
I've tried every possible solution including Pocked mode& Quiet ring.I still think this is a soft bug till further notice.
Lets hope we get a answer soon.Btw same here with the headset,I'm using a hands free and when i answer/call some one i must manually turn off the screen or its turn of by itself after 1-2 min i think.
psicobelico said:
Same problem here, when i'm in a call the screen go on, very annoying.
Now i'm trying this app "rezound prox sensor calibrator"
Click to expand...
Click to collapse
It's not a calibration issue. When the phone rings or you make a call via a headset and the proximity sensor is covered (ie. in your pocket or screen face down), the display kicks on and the prox sensor seems to default to "far" or "uncovered" (whatever term you like). It will remain at that value until you ACTUALLY uncover the sensor and then cover it back again.
alex.foto said:
I've tried every possible solution including Pocked mode& Quiet ring.I still think this is a soft bug till further notice.
Lets hope we get a answer soon.Btw same here with the headset,I'm using a hands free and when i answer/call some one i must manually turn off the screen or its turn of by itself after 1-2 min i think.
Click to expand...
Click to collapse
The problem I have is that while the display is ON and sitting in my pocket, I have a chance of butt dialing someone or starting programs that drain the battery in addition to the dsplay being on. Not to mention, with the display on in my pocket, the heat builds up in the phone. I guess I have a $700 butt warmer? LOL