Hello Community,
Sorry to ask a seemingly dumb question. I don't have many posts because generally I can figure things out on my own. I've been rooting since OG D1 days. I had the OG D1, Incredible, and now I have the Thunderbolt. I am rooted, s-off, with cwr, but for some reason with my Auto-Rotate checked it just stays in landscape mode like if I go to Settings, or Mail, or Gmail... It's weird. I did a search and found nothing on it. Has this happened to anyone?
I'm not rooted. Just bought the phone, and having an auto-rotate issue myself. When I turn my phone over for landscape mode, it takes anywhere from 3-10 before it'll switch into it. I do know what I your talking about thiugh, because the demo phone I was playing with at the store was doing just what you said.
Have you tried a battery pull yet?
I've noticed the same thing, it keeps going into landscape mode and is reluctant to go back into portrait mode...
I wonder if it's hardware or software.
Have you tried calibrating the sensor using "settings>display>G-Sensor calibration" ???
Joeviocoe said:
Have you tried calibrating the sensor using "settings>display>G-Sensor calibration" ???
Click to expand...
Click to collapse
I did this myself immediately and haven't noticed any issues you guys are talking about. I would recommend trying this as well.
Hi all
If you have your phone w A/C plugged in the screen doesn't respond too well when u rotate. Try to rotate the phone out anything plug in.
Give it a shoot.
Sent from my ADR6300 using XDA App
nosympathy said:
I did this myself immediately and haven't noticed any issues you guys are talking about. I would recommend trying this as well.
Click to expand...
Click to collapse
That did it, thanks.
I've tried the G-Sensor Calibration and a battery pull, and restarting it multiple times and I'm still having the same issue.
I had this same issue with my phone - pretty sure its a broken sensor, i returned mine to a verizon store for a new one.
Related
I was installing some apps on my phone and suddenly the screen turned off. When I tried to turn it on, nothing happened. I then let the phone sit for a minute and still nothing would happen until I noticed the buttons turning on and off. I tried swiping where the unlock would be when the buttons come on and it worked. I could tell from the tactile feel. I then rebooted the phone by pressing and holding the power button and guessing where restart would be. The screen works again.
Has anyone else experienced this problem? First time for me.
hpcolombia said:
I was installing some apps on my phone and suddenly the screen turned off. When I tried to turn it on, nothing happened. I then let the phone sit for a minute and still nothing would happen until I noticed the buttons turning on and off. I tried swiping where the unlock would be when the buttons come on and it worked. I could tell from the tactile feel. I then rebooted the phone by pressing and holding the power button and guessing where restart would be. The screen works again.
Has anyone else experienced this problem? First time for me.
Click to expand...
Click to collapse
I had it happen to me once, when I first got the phone. Exactly as you described, except I had to battery pull. I was using an app called Screen Filter, so I could dim the capacitive lights. I figured it had to do with that app, so i removed it. I haven't had it happen since. I'm not sure if it was Screen Filter that caused it or not, but I haven't had it happen again since I removed it. Either that, or just a coincidence.
Happened to me once when I was messing with a root script that had a bug. Ended up clearing some of my app data too. Seems like a common "brain death" state that the phone can get into. I'm pretty sure it's software related and nothing to worry about.
Mike
it happens to me often, and I too have screen filter... but that isn't the cause of the problem (i got it to dim the buttons but it doesn't work on those yet).
I'm not sure what the problem is, but you can eventually turn the screen back on and reboot it - just keep at it. Do you have anything plugged into the headphones jacks BTW? If you do, and you try to reboot, it'll hang. It's done that to me a few times so I unplugged the headphones everytime
Started happening to me after i installed either switkey x or the amazon app, i am not sure but i think that's what caused it
SwiftKey works fine for me... try reinstalling it. Same far any other apps that cause issues, make sure the download was good and reinstall.
If the phone freezes, remember that the only ways to get a try restart is a dead battery or battery pull. Wifes phone froze and shut off, would not restart until a battery pull.
Good luck!
Sent from my phone
Happens to me too and it is really irritating.
GhettoBSD said:
it happens to me often, and I too have screen filter... but that isn't the cause of the problem (i got it to dim the buttons but it doesn't work on those yet).
I'm not sure what the problem is, but you can eventually turn the screen back on and reboot it - just keep at it. Do you have anything plugged into the headphones jacks BTW? If you do, and you try to reboot, it'll hang. It's done that to me a few times so I unplugged the headphones everytime
Click to expand...
Click to collapse
It works perfect for dimming (well turning off) the buttons, check your settings!
so i keep having the same problem even without the swiftke y installed tried to reboot and even factory reset no luck. did you find any solutions.
used to happen a lot when i had aosp roms on my old hero
Are you guys overclocked?
I am not overlooked and I exchanged to another phone.
Sent from my PG86100 using XDA App
iliapiano said:
I am not overlooked and I exchanged to another phone.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Damn....I may have to do that. Sprint allowed you to exchange with no hassle? It seems to happen so randomly that I don't think my Sprint Store will exchange it if they can't reproduce it.
freeza said:
Are you guys overclocked?
Click to expand...
Click to collapse
My wife was oc when hers froze
Sent from my phone
I'm overclocked but the issue @ hand is software related. When I had the OG Evo, certain kernels would cause the screen to act in the same matter stated in the op. A lot of bugs that people report would be resolved once we get perm. Root.
My ''xDU4L C0R3 SH00T3Rx'' shot you down in 3D!
SO this has happened to me and I am freaking out thinking its the aosp rom. how long did it take for the screen to light up again. it been like two hours for mine.
Has anyone had a problem with this? Since I got my 3vo two days ago I've had it freeze twice and i had to do a battery pull each time, I also just had my phone not be able to wake up, tried holding the power button down because I thought maybe it shut down randomly but nothing would happen. I ended up doing a battery pull, is anybody else having trouble?
Also, Apps like launcher pro and music beta seem to be lagging...
Sent from my PG86100 using XDA Premium App
adianlorenzana said:
Has anyone had a problem with this? Since I got my 3vo two days ago I've had it freeze twice and i had to do a battery pull each time, I also just had my phone not be able to wake up, tried holding the power button down because I thought maybe it shut down randomly but nothing would happen. I ended up doing a battery pull, is anybody else having trouble?
Also, Apps like launcher pro and music beta seem to be lagging...
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Do the capacitive buttons turn on and off? when you press the power button.
No they didn't
Sent from my PG86100 using XDA Premium App
Damn and i just found dust under my screen
Sent from my PG86100 using XDA Premium App
iliapiano said:
Do the capacitive buttons turn on and off? when you press the power button.
Click to expand...
Click to collapse
Mine did that last night. Had to do a battery pull. Any thing significant about the capcitive buttons coming on and off only when hitting the power button?
adianlorenzana said:
Has anyone had a problem with this? Since I got my 3vo two days ago I've had it freeze twice and i had to do a battery pull each time, I also just had my phone not be able to wake up, tried holding the power button down because I thought maybe it shut down randomly but nothing would happen. I ended up doing a battery pull, is anybody else having trouble?
Also, Apps like launcher pro and music beta seem to be lagging...
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
I had this exact issue and I had to do a 30 day exchange, sprint tech support said it was hardware issues.
Brandon
Mine did that, the capacitive buttons came on and off but the screen didn't, sometimes they wouldn't i made an exchange, i have a strong feeling it's hardware related, so I would recommend you exchange.
Mine has had this problem since day one but ever since I started traveling internationally and running it in airplane mode with the WiFi left on, I can't get it to crash!!! Now the only thing that's bothering me is the camera freezing after taking a shot. I don't know why the phone has decided to play nice, the only big change besides the airplane mode business is that I uninstalled Text Battery Widget.
soopermarkus said:
Mine has had this problem since day one but ever since I started traveling internationally and running it in airplane mode with the WiFi left on, I can't get it to crash!!! Now the only thing that's bothering me is the camera freezing after taking a shot. I don't know why the phone has decided to play nice, the only big change besides the airplane mode business is that I uninstalled Text Battery Widget.
Click to expand...
Click to collapse
Mine was crashing and freezing with out any apps installed on the phone.
Brandon
Same thing happened to me, I exchanged and my new one has been working perfectly.... plus the speaker is louder than the last one for some reason which is a +
I had my razr for about 2 weeks, and this problem already happen to me a few times.
The touch screen will suddenly not responding to ANY touch, only the the buttons are still working(include the 4 buttons on the bottom).
I had to hard reboot my phone to get it working again.
Does anyone face the same issue?
Sent from my XT910 using XDA App
WongJames said:
I had my razr for about 2 weeks, and this problem already happen to me a few times.
The touch screen will suddenly not responding to ANY touch, only the the buttons are still working(include the 4 buttons on the bottom).
I had to hard reboot my phone to get it working again.
Does anyone face the same issue?
Sent from my XT910 using XDA App
Click to expand...
Click to collapse
Yes I also face this type of problem while playing games. Screen become unresponsive while playing but can solve by pressing power button(no need to reboot).Not on 2.3.5 base only on 2.3.6.
I also face this problem, after updating my rom to arctic 2.0 rom, which uses some stuff from 2.3.6.....power does not help, have to hard reboot. any idea why?
I've had this problem happen to me on my Droid RAZR (CDMA Verizon), can't remember if its before or after I was rooted... I just had to hard restart and its only happened once since then.
pswin09 said:
Yes I also face this type of problem while playing games. Screen become unresponsive while playing but can solve by pressing power button(no need to reboot).Not on 2.3.5 base only on 2.3.6.
Click to expand...
Click to collapse
The power button does not work for me
I had try to press the power button, but then the screen still not responding, so I cannot pass through the lock screen, and have to hard reboot......
I am on stock rom, 2.3.5, the Asian version.
But it seems it does not matter to different region's razr since the cdma one had the same issue
Sent from my XT910 using XDA App
I get this too. I had 3 razrs, first two had dead pixels so I had them replaced, all had this issue. Has not happened in awhile and I can't remember if it was always with a game, but at least one time it was with a game. Anyway, I don't think this has to do with rooting because my first one I never rooted and it did this. Don't remember if power button worked or not, but I had to reboot as well with power and volume down, or up, whatever it is, to get it to respond again.
No problems here.
I have had this happen about 4 or 5 times for me as well - got it day of launch. Mine says it is the XT912 though - is that right?
XT912 is the Verizon specific one, so yes.
Seems to be a fairly common issue. What is the chance that this is a software problem as opposed to a hardware one and so will be fixed with an update?
I had it happen for the first time yesterday after about 5 weeks or so, strange cause I wasn't doing anything. Battery was at about 15% though...
I only encounter this bug when I open Rom Toolbox for the first time and the superuser permissions screen shows up. My screen doesnt respond to touch anymore. I have to use the power button to make it work. Thats it. It happens nowhere else.
I've been using ROM Toolbox since day one, can't say it's the issue.
Sent from my XT910 using xda premium
opensourcefan said:
I've been using ROM Toolbox since day one, can't say it's the issue.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
Happened to me today...any need to panic?? On official Stock ROM 2.3.5...
Also, is this a hardware issue or software??
My problem is bit different, on a 4 month old unrooted razr.
Touch screen will start to fail recognizing my sywpe typing and start jumping all over the place, or it will end the word while I'm still sywping the word...
Sometimes it types in different letters (1/2 keyboard away) when I'm not sywping to avoid this BS when it happens.
Unfortunately, I cannot reproduce this result whenever I want to, I'm currently trying to reproduce the situation.
I believe this happens more often when my battery is low... or when I have been using it for an extensive time.
I go to draw program to test if it is the hardware problem and it is jumpy too, but not by much.
The problem does get better with reboot, but not 100% of the time, so I can't conclude it is SW problem
I also have issues with this. I think the problem is software side. It seems to be poorly responsive often after I unlock my phone and try to swipe screens.
Also while typing quickly with two hands it often does not input all the letters I type, although it flashes the keys and acknowledges that I touched them (this one might be a keyboard issues, not sure yet)
And ya, on an all black screen, I'm noticing some dead pixels- a lot of rectangular patches of dead pixels. I don't really notice it anytime else except when it's all black.
Been making me double think my choice, but I will wait for ICS update and possibly bootloader bypass. But.. I might be getting another phone shortly just because of the size (bezel mostly), these touch screen issues, and the performance isn't exactly where I anticipated it to be.
Razr XT910 touchscreen randomly jumping or not responding
I'm having all the problems mentioned earlier:
- touchscreen stops working randomly
- touch "jumps", like someone is touching it in random places
- some letters on the keybord stop working randomly
- phone gets quite hot at the top
My XT910 is not altered in any way, stock android 2.3.5, as updated as possible.
This happened when it was up-to-date and the very clean one.
This happens really irregularily. At first it happened when I played multitouch games - at some point the touchscreen just stopped responding and could only go back or lock the screen (but not unlock it, obviously).
Twice it happened when I was just going through messages or contacts.
I sent it to Motorola to fix it - they just reset it, benchmarked it for 45seconds and sent it back.
The very evening I got it back I tried to "heat" it myself - I installed a lot of apps, played a lot multitouch games on 3d graphic and voila! - it started freaking out like never before (vidoe in zip file attached).
My last idea is that it happens because of a low quality generic anti-scratch foil on the screen. So I threw it away and tried to "heat" the phone again - nothing.
I used a different foil - anti-reflecting + benchmarking apps - nothing.
If it happens again I'll send it with this video + the one I'll make then.
Hope it gets Motorola specialists off their ass and back to work .
Hey there, my maxx has this weird issue with it's screen too.
Take for example, a game with on screen controller like reckless racing. If i push the screen too long, it won't recognize my press anymore in the pressed area. I tried to go back home, thinking this is the game issue, but it's not, the home launcher button that coincidentally in the same location with game control button is unclickable. i tried with phone tester app and it show the same symptom, the pressed area indicator will disappear within 1-2 minutes.
The only solution is to turn off display and turn it on again. Should i bring it to service center?
Sent from my XT910 using xda app-developers app
Hello, I've recently having this exact same problems with my Motorola Droid Razr Maxx.
The screen sometimes doesn't respond as it should:
-Random touches.
-Not detecting swipes.
-Not detecting anything at all after long press.
-Detecting the touch location wrongly...
When this happens, sometimes a reboot fixes everything. Others, I just have to stop using the phone, and come back later.
Has anyone managed to find a possible cause and/or solution to this problem?
I've tried diferent roms, full reset, rsd flashes... But still the same problem
I'm brand new to HTC devices so I'm unsure if the dialer is sense or if this is a ICS dialer were dealing with. (My old phone was a Droidx, so my exp is with blur and asop 2.3 from liberty).
Either way though i seem to have come across an interesting "bug" or at least unusual behavior.
I've noticed on almost every other call, weather it's incoming or outgoing, the MOMENT you dial/answer the screen goes dark. Now i can press the power button to wake it up again and it will stay on for exactly 5 seconds before going dark again. If i flip on speaker phone the screen will stay on, however the moment i turn off speaker phone it goes dark again.
Whats really annoying is if i go back to the home screen it still goes dark after 5 seconds but now when i wake it up it's at the lock screen. If i try to unlock it the moment i touch the screen it goes dark. No matter where i touch the screen the phone is now perma locked until the call is finished.
Now like i said this happens every other call so far in the 6 times I've tested this, which i thought was really odd. The other times the screen stays on and acts completely normal no matter what i do while a call is active. Fresh reboot makes no difference. I haven't done a factory reset yet as I'm trying avoid that.
What i have done so far is unlocked the bootloader, Flashed recovery, and the root from con247's thread in the dev section. I don't think that has anything to do with it though since i noticed the screen going black during a call before i started messing with bootloaders/recovery/root. I just didn't test it as well before doing those things cuz i didn't think anything of it.
Is anyone else seeing this behavior and does anyone have any suggestions?
Void4ever
void4ever said:
I'm brand new to HTC devices so I'm unsure if the dialer is sense or if this is a ICS dialer were dealing with. (My old phone was a Droidx, so my exp is with blur and asop 2.3 from liberty).
Either way though i seem to have come across an interesting "bug" or at least unusual behavior.
I've noticed on almost every other call, weather it's incoming or outgoing, the MOMENT you dial/answer the screen goes dark. Now i can press the power button to wake it up again and it will stay on for exactly 5 seconds before going dark again. If i flip on speaker phone the screen will stay on, however the moment i turn off speaker phone it goes dark again.
Whats really annoying is if i go back to the home screen it still goes dark after 5 seconds but now when i wake it up it's at the lock screen. If i try to unlock it the moment i touch the screen it goes dark. No matter where i touch the screen the phone is now perma locked until the call is finished.
Now like i said this happens every other call so far in the 6 times I've tested this, which i thought was really odd. The other times the screen stays on and acts completely normal no matter what i do while a call is active. Fresh reboot makes no difference. I haven't done a factory reset yet as I'm trying avoid that.
What i have done so far is unlocked the bootloader, Flashed recovery, and the root from con247's thread in the dev section. I don't think that has anything to do with it though since i noticed the screen going black during a call before i started messing with bootloaders/recovery/root. I just didn't test it as well before doing those things cuz i didn't think anything of it.
Is anyone else seeing this behavior and does anyone have any suggestions?
Void4ever
Click to expand...
Click to collapse
Sounds like the proximity sensor is going wonky. You might try a factory reset and without installing anything else see if you get the same issue. Also, make sure that any programs you have installed are not affecting it for some reason.
blazingwolf said:
Sounds like the proximity sensor is going wonky. You might try a factory reset and without installing anything else see if you get the same issue. Also, make sure that any programs you have installed are not affecting it for some reason.
Click to expand...
Click to collapse
Just factory reset it, skipped setup completely and started making calls, same issue. You maybe right about the sensor though. The first call acted up like i explained. The second call the screen was staying on like i expected, but once i switched speaker phone off and then back on the screen shut off and started acting like call one again.
I just got this phone 6 hours ago i wonder how hard it will be to convince verizon there's a hardware fault. I guess i'd better unroot it and remove recovery so i can call in the morning.
Void4ever
I just wanted to make sure i understand this before i do it.
To remove the root i need to install the RUU for the phone, which i found at http://themikmik.com/showthread.php?13550-Asian-Shooter-goes-ICS-and-a-VZW-Fireball-RUU (second link i assume).
I haven't downloaded it yet, but it's an exe. Will it flash the phone via USB, or does it just extract something i can use recovery to flash with?
Once i get the root removed i just need to flash back the original recovery and i should be good to go right?
Void4ever
void4ever said:
I just wanted to make sure i understand this before i do it.
To remove the root i need to install the RUU for the phone, which i found at http://themikmik.com/showthread.php?13550-Asian-Shooter-goes-ICS-and-a-VZW-Fireball-RUU (second link i assume).
I haven't downloaded it yet, but it's an exe. Will it flash the phone via USB, or does it just extract something i can use recovery to flash with?
Once i get the root removed i just need to flash back the original recovery and i should be good to go right?
Void4ever
Click to expand...
Click to collapse
There are directions in the RUU that will explain all of the steps. You will connect your phone with the USB cable.
It shouldn't be to hard to convince them. Just show them the steps you did to reproduce the issue. Good luck.
On the phone right now and the guy is setting up overnight sat delivery to my house. We are a fairly large business account so i'm glad they are going that extra mile.
Just to note I've noticed the sensor doesn't shut off after a call is complete. In fact it stayed on last night for around 6 hours before finally turning off. I did another test this morning and once again the sensor is stuck on, so good call. Thanks so much for your help, i never would have thought sensor, it seemed like a software issue to me!
Void4ever
void4ever said:
On the phone right now and the guy is setting up overnight sat delivery to my house. We are a fairly large business account so i'm glad they are going that extra mile.
Just to note I've noticed the sensor doesn't shut off after a call is complete. In fact it stayed on last night for around 6 hours before finally turning off. I did another test this morning and once again the sensor is stuck on, so good call. Thanks so much for your help, i never would have thought sensor, it seemed like a software issue to me!
Void4ever
Click to expand...
Click to collapse
No problem. Glad you got a new one coming.
replacement came today and it works like a dream now, got custom recovery and root going! It was def a bad prox sensor on the other one. Thanks again for your help wolf!
Void4ever
Good to hear man. Enjoy that puppy.
void4ever said:
replacement came today and it works like a dream now, got custom recovery and root going! It was def a bad prox sensor on the other one. Thanks again for your help wolf!
Void4ever
Click to expand...
Click to collapse
Awesome.
Sent from my ADR6410LVW using Tapatalk 2
Has anyone else had airplane.mode just turn on by itself during calls? its beeN happening often and also happened on my first EVO LTE that I exchanged...ill be on a call and all of a sudden it will hang up..ill look at the screen and airplane mode is activating..its drivin me nuts and is happening a lot..like everyday
firmbiz94 said:
Has anyone else had airplane.mode just turn on by itself during calls? its beeN happening often and also happened on my first EVO LTE that I exchanged...ill be on a call and all of a sudden it will hang up..ill look at the screen and airplane mode is activating..its drivin me nuts and is happening a lot..like everyday
Click to expand...
Click to collapse
Still doing it months later wtf
You don't have an app installed called more bars do you? That app automatically enters airplane mode during low signal to conserve battery.
Sent from my A500 using Tapatalk
ishh happen to me the other day.. i just turned my screen on and i watched it happen.. i was running mean rom forget what version.. i watched my radio's turn off and airplane mode turn on.. it hasnt happend again
U must have a something wrong with it or something. I have never had this happen
Sent from my EVO using xda premium
HTC One
So I'm having this problem as well, on my new HTC One... it goes into airplane mode nearly every call I have... I'll probably have to go back to my iPhone if I can't resolve the issue. As stupid as it sounds, I'm fairly confident it's my ear touching the screen that's "navigating" into settings and turning airplane mode on... if I'm 100% concentrating on not touching the phone's screen at all, I don't have the problem. But if I'm talking normally, it never fails, the call drops, I look at the phone, and I'm sitting on the settings page with airplane mode on. I honestly don't know how this doesn't happen to everyone... I *THINK* my ears are normal!? Anyone come up with a solution??
markzaa said:
So I'm having this problem as well, on my new HTC One... it goes into airplane mode nearly every call I have... I'll probably have to go back to my iPhone if I can't resolve the issue. As stupid as it sounds, I'm fairly confident it's my ear touching the screen that's "navigating" into settings and turning airplane mode on... if I'm 100% concentrating on not touching the phone's screen at all, I don't have the problem. But if I'm talking normally, it never fails, the call drops, I look at the phone, and I'm sitting on the settings page with airplane mode on. I honestly don't know how this doesn't happen to everyone... I *THINK* my ears are normal!? Anyone come up with a solution??
Click to expand...
Click to collapse
Is your proximity sensor working fine? Is it covered with a screen protector?
Check this out:
https://play.google.com/store/apps/details?id=com.tigermonster.proxfinder
Good luck!
Sent from my Evo 4G LTE
jocarog said:
Is your proximity sensor working fine? Is it covered with a screen protector?
Check this out: (link removed)
Good luck!
Sent from my Evo 4G LTE
Click to expand...
Click to collapse
Thanks... I installed the sensor app... seems to be working ok... it's showing "all or nothing" (9cm or 0cm) and seems to indicate the duration I hold the phone to my head. If I move my head around (not necessarily away from the phone) it indicates that the sensor thought I wasn't in proximity the full time... so perhaps there are brief moments the OS thinks I've pulled the phone away from my head. Maybe that algorithm needs tweaking (e.g. maybe wait 1-2 seconds of nothing in proximity before turning on screen?).
I don't have a screen protector.
markzaa said:
Thanks... I installed the sensor app... seems to be working ok... it's showing "all or nothing" (9cm or 0cm) and seems to indicate the duration I hold the phone to my head. If I move my head around (not necessarily away from the phone) it indicates that the sensor thought I wasn't in proximity the full time... so perhaps there are brief moments the OS thinks I've pulled the phone away from my head. Maybe that algorithm needs tweaking (e.g. maybe wait 1-2 seconds of nothing in proximity before turning on screen?).
I don't have a screen protector.
Click to expand...
Click to collapse
found this on the htc one forum: http://forum.xda-developers.com/showthread.php?t=2259526
I didn't read it, but it looks like you are not the only one having issues with the proximity sensor...
So I know this doesn't help much but wanted to add I'm having this issue as well. Not every call but maybe every couple of days or so. Does seem to happen when I'm using the phone, not an ear piece, and I'm moving around a lot. So might be something with the proximity sensor, though there is not quick button I could be hitting with my face to turn airplane mode on even if the screen was on. I have also noticed a lot of strange network issues where my single bounces between 4g, 3g and hsdpa often, which I've never had a phone do this much before. I can actually sit there and watch flip back and forth. So I'm really thinking the HCT One has some manufacture issues that are not being addressed. I'm about ready to send this thing in.