Just a few gripes and anomalies I have found with the OneX
MOST of these are "problems" I feel, with a couple (3 & 6) being "wants".
Wonder if anyone else has had similar problems??
1) Start tone/Close tone. HTC always have a start-up tone, and close-down tone. The "HTC Signature" tone, if you like. My handset plays NO start-up or close-down tone. My handset is Vodagroan branded, if that makes a difference? Something Vodafone have done (wrong) by removing the tone??
2) "Auto screen brightness", becomes DISABLED after a reboot of the phone. It SHOULD (of course) remain enabled.
3) The “continuous spin” of the home screens (where one could just keep flipping horizontally, as on the DesireHD with Gingerbread)) has been disabled? (is this correct) One may only now go as far as the last screen, then back in the opposite direction.
4) Screen capture (Power+Home key). Previous HTC Devices (where screen dump possible), one would press the key sequence, and hear a “camera click” sound when the screen image was captured. There is NO screen capture sound on the OneX (having said that, I am SURE it did happen ONCE the other day!!). Is this correct, that there is no indication sound now?
5) After a reboot of the device (the ONLY time I re-boot is when there is a problem!), I have found that the NAMES of SOME of the icons on my HOME screens disappear. The icons on the application list remain with their names (as they should), but some of the icons on my HOME SCREENS disappear (see attached screen dumps). To get the names back, one has to DUMP the icons (from the Home screen) and then re-add to the Home screen.
6) Video. When one starts to video, there is a lag of a couple of seconds before recording starts. It isn’t instant, as it was with previous HTC models when video recording. There is no timer shown either, when one if videoing. Again, this WAS a “feature” of previous HTC’s
7) When one puts the phone on charge, or indeed takes the phone OFF charge, previous models would illuminate the screen (come off sleep mode). When one plugs/unplugs the OneX, the screen remains black. Is this correct?
There ya go.. Anyone else have these problems?
Cheers
Those things are so trivial, I can't answer.
And... Your point is??
HTC whore said:
Those things are so trivial, I can't answer.
Click to expand...
Click to collapse
Yes, Thanks "HTC Whore". Is that how you managed to get to 134 posts??
As far as I am concerned, all but 2 of the items I have listed are relevant. I am asking if anyone else has had similar problems (as you MAY be able to read).
The question may be "trivial" to you, but "Hey", we all need to ask questions sometimes (with the exception of some people no doubt?!).
Thanks for your contribution anyhow, on "congratulations" in getting yourself another post number....
Forgive me. I will try and answer your questions, as my device is running pretty sweet.
Nah sorry, fell asleep.
Screen shots are now power and volume down
And the 'carousel' has now been disabled
My screen also stays off once I unplug it from the mains - doesn't bother me tbh
EddyOS said:
Screen shots are now power and volume down
And the 'carousel' has now been disabled
My screen also stays off once I unplug it from the mains - doesn't bother me tbh
Click to expand...
Click to collapse
Screenshot is still Power + Home here, also the sound is gone. Shame, it was handy for conformation.
Hmmm, power volume down works for me
HTC whore said:
Screenshot is still Power + Home here
Click to expand...
Click to collapse
One is ICS screenshot, the other Sense screenshot. Think they're saved in different file locations.
Regarding the carousel, that's a Sense 4 thing, although I think some devs/chefs are working on bringing it back on Sense 4.
EddyOS said:
Hmmm, power volume down works for me
Click to expand...
Click to collapse
Doesn't work for me. Very strange!
Oh and continious spinning is indeed disabled, and my unbranded X has a startup tone, although it's not the same one as the older Desire models.
HTC whore said:
Doesn't work for me. Very strange!
Oh and continious spinning is indeed disabled.
Click to expand...
Click to collapse
Hold power and volume down together, for about a second, and there is a click
So there is Basil! Nice one. I was holding Power and tapping Vol-. I prefer the Power+Home method personally.
HTC whore said:
Forgive me. I will try and answer your questions, as my device is running pretty sweet.
Nah sorry, fell asleep.
Click to expand...
Click to collapse
Thanks "HTC Whore". You've been really helpful.
Now, where's my chocolate teapot??
Oh, that's right. HTCW is using it as a mentor..
HTC whore said:
Doesn't work for me. Very strange!
Oh and continious spinning is indeed disabled, and my unbranded X has a startup tone, although it's not the same one as the older Desire models.
Click to expand...
Click to collapse
HTC changed the start up tone for the One series - I prefer it personally
In regards to illumination and the charger, my phone works the same as yours, only the LED changes.
And video lag is the same here, the screen goes black and a white camcorder symbol appears. Only for a second or so.
Is that redemption I smell?
EddyOS said:
Screen shots are now power and volume down
And the 'carousel' has now been disabled
My screen also stays off once I unplug it from the mains - doesn't bother me tbh
Click to expand...
Click to collapse
Hi EddyOS. Fancy seeing you here
Power+Home DOES (with mine) take the screen-shot, but there is no sound with this. Prev models had an associated "click" so one knew when it had been captured. Just a small thing, but thought there may have been a problem. Or are you suggesting Power+VolDown invokes the click? Just tried with mine, and Power+VolDown simply turns the volume down..
Okay on the Carousel, Thanks for the confirm.
Again, the screen remaining off when one plugs in, unplugs, was another query as to whether the screen SHOULD in fact illuminate, as previous and most handsets do. Doesn't WHOLLY bother me, but again a niggle, in case something was awry.
Cheers
You need to hold Power and VOL- down together for a second or so
HTC whore said:
In regards to illumination and the charger, my phone works the same as yours, only the LED changes.
Click to expand...
Click to collapse
HTCW.
Thanks for that confirm, as EddyOS also verified. But it's "good to know" there isn't a fault.
Thanks
HTC whore said:
And video lag is the same here, the screen goes black and a white camcorder symbol appears. Only for a second or so.
Is that redemption I smell?
Click to expand...
Click to collapse
Okay on the video lag. I wouldn't say my screen "goes black and white", but upon pressing the video button it just has that lag of a second or so. Coming from my DHD, where the video button was selected, which simply put the camera into "video mode" standby. Pressing the button again, would instantly start recording (with a timer I hasten to add!).
With the OneX, as you are aware, once the video button is selected it immediately (with that second or so pause) starts recording.
Cheers again for verification of this.
EddyOS said:
HTC changed the start up tone for the One series - I prefer it personally
Click to expand...
Click to collapse
HTCW/EddyOS
One of you mentioned the change in the "start-up tone", and the fact you had an UNBRANDED unit....
I think the fact that you have an UNBRANDED unit makes a little difference here. Initially I was informed (by HTC) that the tone had been removed. Period.
I was then later informed by another HTC agent that their stock unit (vanilla) had the start tone, and he "suggested" that Voda branded handsets may have (inadvertently) lost the tone on the Voda software. Seems you have just confirmed this.
NB/ Whilst this isn't a BIG issue, it's from its absence that it seems there may be "something wrong". At least when there is a start tone, one knows when the phone is "ready to run", audibly..
Cheers
Related
Hi folks, I've had my phone for two weeks, can't really seem to find any documentation on this, but the hang up/power button always seems to be lit up red. I'm not sure if the light is bleeding through, or if the rest simply are not as bright, but the back, start menu, and dial buttons seem to be lit all the time too, regardless of the situation unless off.
I'm assuming everyone else sees this too?
This was something I liked about my Touch Pro, very minnimal. I sort of miss the gentle swoosh of the d-pad on a reminder event, or when charging.
Any thoughts?
what about pressing enter?
Actually none of my buttons at the bottom light up when the device is on unless I hit one of the 4 buttons. Then they only stay lit for about 5 seconds before all going off again.
Ohh, I thought that was odd. Staying on for 5 seconds would make a lot more sense..
Enter? You mean on the keyboard?
Anyone else on a Telus Touch Pro2, can you confirm whether the four bottom buttons stay lit all the time?
Oh, now it turns out it looks like the three left buttons stay dim, but still on, unless one is pressed, but then they dim after 5 seconds or so like mentioned, but the hangup button is always bright red.
I also have the telus touch pro 2 and I have the same problem, I think its just the power/hang up button that stays on but I know what you mean about the light bleeding through to the other bottem buttons as well, I have been searching for a solution to this problem since I got it and have had no luck.
I returned the phone for another NEW one since it was DOA. Both HTC and Telus agreed. That is not a normal operation for the phone to do that, but it's odd that two are doing it.
It gave me a noticably better battery life too, so get on top of that replacement right away. The replacement phone works perfectly.
Ya my battery life hasn't been great and I thought that could be a large factor in it, so I will try to get it replaced then if thats not a normal function of the phone.
matt608 said:
Ya my battery life hasn't been great and I thought that could be a large factor in it, so I will try to get it replaced then if thats not a normal function of the phone.
Click to expand...
Click to collapse
Exactly. I thought the same thing. When actually working properly, it has a long battery life for a phone like that. Significantly longer than my touch pro, which is even more than the p4000
Did you set HKLM/system/currentcontrolset/control/power/batpoweroff to 0, and not 180?
I think that might be what caused it
Icepick66 said:
Did you set HKLM/system/currentcontrolset/control/power/batpoweroff to 0, and not 180?
I think that might be what caused it
Click to expand...
Click to collapse
Its currently set to 0, thats what it should be?
The one I have now that works is set to 0. Not sure about the one that I had that was having the issue.
Hey guys, I'm new here - so Hi! *Waves*
I've searched and couldn't really see anything like my issue, so thought I'd post:
Having some weird issues with my HTC desire... earlier this morning I heard my phone randomly restart (was just sitting beside my bed) and for some reason it started in safe mode.
The power button wouldn't work so I could turn off / restart. So I removed the battery and put it back in, the phone went to the white screen with Hboot on it.
The Up / Down buttons do not work so I can't select anything, neither does the power button.
Everytime the phone boots up not it goes straight to hboot. I don't press anything, it just automatically starts when the battery is in and I can't do anything or even turn it off.
Now it has decided not to power back on - mainboard stuffed maybe?
Any ideas? :s
phil_boy said:
Hey guys, I'm new here - so Hi! *Waves*
I've searched and couldn't really see anything like my issue, so thought I'd post:
Having some weird issues with my HTC desire... earlier this morning I heard my phone randomly restart (was just sitting beside my bed) and for some reason it started in safe mode.
The power button wouldn't work so I could turn off / restart. So I removed the battery and put it back in, the phone went to the white screen with Hboot on it.
The Up / Down buttons do not work so I can't select anything, neither does the power button.
Everytime the phone boots up not it goes straight to hboot. I don't press anything, it just automatically starts when the battery is in and I can't do anything or even turn it off.
Now it has decided not to power back on - mainboard stuffed maybe?
Any ideas? :s
Click to expand...
Click to collapse
check whether you power/volume up/down buttons are stuck inside as if it is pressed.
Are you rooted and s-off? what did you do to your mobile before this issue?
is your SD card working properly? try to post the screenshot of your phone screen with that issue you are trying to explain
sounds like you none working up/down buttons are actuallly but stuck in the down position taking you to hboot on power up. need to free them
http://forum.xda-developers.com/showthread.php?t=1331493&page=2 same ****, different toilet, no way to flush.
bortak said:
http://forum.xda-developers.com/showthread.php?t=1331493&page=2 same ****, different toilet, no way to flush.
Click to expand...
Click to collapse
you really had made detailed trouble shooting guide (came to know from your signature). most of the issues encountered by the users are there. keep it up.
kmaq said:
you really had made detailed trouble shooting guide (came to know from your signature). most of the issues encountered by the users are there. keep it up.
Click to expand...
Click to collapse
I know ^_^ tis the point.. good guide = less threads about the same thing.
Hi i m having the same problems here with my desire dunno if its a bit late but
have you managed to fix your desire is not could you try some thing when it loads to HBoot try pressing all of the lower buttons on the desire (home menu track pad back and search) and see if you have any response because once doing this for a few seconds in a random order frantically pressing them my desire had response but would only move up the list? cheers
My HTC One X dropped (from about 50cm) and landed on it's screen. The screen isn't broken, but it was frozen. So I switched the phone off, since it didn't respond.
Now my HOX won't turn on anymore! After pressing the power button it vibrates shortly (like when starting up). That's it.
Nothing on the screen, it stays blank. Nothing on the soft-touch buttons, the stay dark. When connected to the adapter the charging led doesn't turn on.
The only thing I seem able to do is hold the power button for about 10 seconds, to restart the phone, but then only a short vibration follows. Nothing else.
Anybody got any ideas what to do myself? Befor I can contact HTC on monday...
:crying:
Niels-je said:
My HTC One X dropped (from about 50cm) and landed on it's screen. The screen isn't broken, but it was frozen. So I switched the phone off, since it didn't respond.
Now my HOX won't turn on anymore! After pressing the power button it vibrates shortly (like when starting up). That's it.
Nothing on the screen, it stays blank. Nothing on the soft-touch buttons, the stay dark. When connected to the adapter the charging led doesn't turn on.
The only thing I seem able to do is hold the power button for about 10 seconds, to restart the phone, but then only a short vibration follows. Nothing else.
Anybody got any ideas what to do myself? Befor I can contact HTC on monday...
:crying:
Click to expand...
Click to collapse
Can you get into hboot if you hold power and volume down button for about 20 seconds?
Sent from my fauxed HOX running CMX Alpha 2 by tbalden
Tingelholm said:
Can you get into hboot if you hold power and volume down button for about 20 seconds?
Click to expand...
Click to collapse
I can't tell. My screen stays blank.
BTW: I am able to open my HOX. Perhaps somebody might know what to check if it's hardware related?
(A few weeks ago I've opened my HOX to fix the well known WiFi issue, but this is definitely not related to the blank screen issue.)
Trying to connect by USB to a PC also doesn't work.
Anybody any ideas?
Sounds like you knocked something when it fell. Id call HTC and say one day you couldnt see the screen and send it off to them. They should be able to replace the screen/motherboard.
ste1164 said:
Sounds like you knocked something when it fell. Id call HTC and say one day you couldnt see the screen and send it off to them. They should be able to replace the screen/motherboard.
Click to expand...
Click to collapse
+1 as long as there's no big scuffs and you just say you took it out of your pocket and it was black they'll fix it, even with unlocked bootloader you'll be ok. Phones theses days should be able to take 50cm drops
Sent from my HTC One X using xda premium
ste1164 said:
Sounds like you knocked something when it fell. Id call HTC and say one day you couldnt see the screen and send it off to them. They should be able to replace the screen/motherboard.
Click to expand...
Click to collapse
If Sunday doesn't bring a solution, that's what I'm going to do on Monday...
Today I received my HTC One X back from HTC repair No costs :laugh:
I called HTC on Monday, they picked up my HTC One X on Tuesday and I got it back one week later (on Tuesday).
They've given it a boardswap and replaced the battery (don't know why) and put the latest software (rom) on it.
I did loose all my data, apps and settings, but fortunately I had a very recent back-up available, so I'm happy again!
As we all know(or should know if you read around the forums) that there is an issue with "sod". Now these sods are not the same as the sod i was familiar with before 4.2. Before 4.2, the device(s) were for all intensive purposes not alive. Sure you could connect to adb, but the device was "dead" until you pulled the battery and rebooted. But with these 4.2 "sods", the device is alive, with the exception of the screen not being able to turn on. Phone calls and messages still come in. notification sounds still play, and you can use the volume buttons to raise/lower the volume. But you still have to pull the battery and reboot for the screen to come back on. Running logcats via adb doesnt seem to show anything related. Well, ive found a way to reproduce these 4.2.X "sods" while the device is awake with the screen on. I can reproduce it at will, and have had other users confirm this. What i do is this.. I go into the main settings, display, then brightness. Turn off automatic brightness if its on. Now adjust the brightness, up, then down, then up(back and forth, but take your finger off the slider when you go up then down). now press ok to set the brightness. Go back into the brightness setting and repeat. Eventually(sometimes seconds, sometimes minutes) the screen goes completely black, like its off, but the device is completely awake. same as these 4.2 sods, phone calls and messages come in, notifications sound, etc. Only difference is the device screen is on when it goes black instead of it being off. The symptoms are the same. This behavior leads me to believe that it most likely isnt a kernel issue like many believe. I believe that its related to some coding that controls the screen. As we know, every rom/kernel has shown this behavior, even stock and unrooted(some more, some less). Personally, i had 3 of these sods last month(trinity kernel/rasbean rom), but i know that some users have them many times a day unfortunately. What could it mean that i can replicate this behavior on an awake device? Any more thoughts about this?
maybe someone using another kernel/rom can try to reproduce this?
I haven't tried your method yet. I'll and post my results here. I was able to replicate it using another program (check the links below)
But reading your post, I'm sure now that SOD has to do with autobrightness or brightness control (knowing that, maybe it is easy to solve?)
Check my posts:
http://forum.xda-developers.com/showthread.php?p=35205418#post35205418
http://forum.xda-developers.com/showthread.php?p=35496824#post35496824
Check my post here:
[URL="http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638"]http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638[/URL]
whre I answered to that phenomen. I was on RBJ + franco r348 that time
I can't reproduce (force) it now with RBJ + franco r360, I tried about 100 times.
Just wanted to post my results, maybe it's too early to tell as r360 is too young.
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
Maybe because OMAP is abandoned at 3.0.
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Jessie-James said:
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
if your device wakes, even after a few presses, its not sod.
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
pressing and holding the power button for 10-20 seconds will force reboot those devices.
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
MondoMor said:
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
Click to expand...
Click to collapse
wouldnt it be easier to just pull the battery? thank you for your observations btw.
simms22, I actually think it is a kernel issue. I only experience SOD problems when i use a custom kernel. Also yesterday I flashed stock 4.2.1 and tried for 10 min to replicate SOD using your method - I could not. Today I tried again - nothing.
simms22 said:
wouldnt it be easier to just pull the battery? thank you for your observations btw.
Click to expand...
Click to collapse
My phone is in an Incipio case, and it's more of a pain to separate the case, especially if I'm in my car or out hiking or whatever. I've gotten pretty good at doing it blind. Also, years of running Windows have made me anal about doing orderly shutdowns. :laugh:
Forgot to add earlier: I was unable to replicate with the technique described in the OP. But as long as someone can get this to happen on demand, it ought to be solvable.
Edit: although I got the SOD in normal usage a few minutes after trying the technique in the OP. Maybe the display SODs on some specific number of brightness changes? That would explain it happening more often with autobrightness, also.
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
Just hold down the power button for several seconds. Continue to hold down the power button until the screen blinks off and the boot logo appears.
We are flooding here.. lets discusse this other place and leave the devs alone here
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
andQlimax said:
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
Click to expand...
Click to collapse
When I was running the first few nightlies of CM10.1 it still did the "sod" on me. By default the animation settings are at 1.0. Not sure if it's different on stock.
I've had several sod's daily for last few day's and today finally flashed RBJ from the beginning plus dax's modified kernel and now i'm in watching phase. So far so good.
I have time without any sod... Maybe because I'm trying not to use auto brightness or because of the lastest versions of Francos kernel... Stock ROM
Sent from my Galaxy Nexus using xda app-developers app
I have a problem with One V. The 'Ring Key' which has to be slid upwards to unlock the phone is not functioning smoothly. It takes multiple efforts to unlock, which means when a phone call comes, by the time I fiddle and unlock the call is dead.
Another problem, the Red DECLINE and Green ACCEPT buttons to decline/accept phone calls are dead.
I was till now unlocking the phone by pulling the ring upward and activating/answering the call. Now it has become difficult to answer a call.
The phone is out of warranty. Is there any software solution I can look for? I tried WidgetLocker but it does not allow you to answer a call by unlocking.
bayankaran said:
I have a problem with One V. The 'Ring Key' which has to be slid upwards to unlock the phone is not functioning smoothly. It takes multiple efforts to unlock, which means when a phone call comes, by the time I fiddle and unlock the call is dead.
Another problem, the Red DECLINE and Green ACCEPT buttons to decline/accept phone calls are dead.
I was till now unlocking the phone by pulling the ring upward and activating/answering the call. Now it has become difficult to answer a call.
The phone is out of warranty. Is there any software solution I can look for? I tried WidgetLocker but it does not allow you to answer a call by unlocking.
Click to expand...
Click to collapse
you rooted? or on stock?
if rooted, try MyOneVrc9.5
Sent from my Katana
Seraz007 said:
you rooted? or on stock?
if rooted, try MyOneVrc9.5
Sent from my Katana
Click to expand...
Click to collapse
Yes, it is rooted. Will try your suggestion.
Has your touchscreen been damaged in any way?
Sent from my One V using Tapatalk 4 Beta
Seraz007 said:
you rooted? or on stock?
if rooted, try MyOneVrc9.5
Sent from my Katana
Click to expand...
Click to collapse
Actually, I have MyOneV RC9.5 FX+ rom and that same problem happens to me quite often (several times per day). Phone starts ringing and when I try to slide unlock ring or either green or red phone symbol, touch doesn't seem to register anything. Only thing that works is switching the screen off with power button and switching it back on. And the phone works like nothing happened.
Deontologist said:
Has your touchscreen been damaged in any way?
Sent from my One V using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, screen has one long crack that splits it in two pieces. However, until I installed that custom rom ~3 months ago i haven't had any problems with digitizer. My screen has been cracked for almost a year now and that would be the only problem with it.
Tyrannar said:
Actually, I have MyOneV RC9.5 FX+ rom and that same problem happens to me quite often (several times per day). Phone starts ringing and when I try to slide unlock ring or either green or red phone symbol, touch doesn't seem to register anything. Only thing that works is switching the screen off with power button and switching it back on. And the phone works like nothing happened.
Yes, screen has one long crack that splits it in two pieces. However, until I installed that custom rom ~3 months ago i haven't had any problems with digitizer. My screen has been cracked for almost a year now and that would be the only problem with it.
Click to expand...
Click to collapse
When you get a call, instead of grabbing the ring and pulling it to the phone, try grabbing the phone (green or red) and pulling it to the ring... not sure if that'll work, but then you don't have to unlock Then answer, it just answers
lilrob1213 said:
When you get a call, instead of grabbing the ring and pulling it to the phone, try grabbing the phone (green or red) and pulling it to the ring... not sure if that'll work, but then you don't have to unlock Then answer, it just answers
Click to expand...
Click to collapse
Nope, whole screen is dead to the touch and so is the volume rocker. Only responsive key is the shut down key. I turn of the screen and turn it back on and everything works like nothing happened. One more thing, when i listen to music, and try to change song on the lock screen widget by pressing on screen buttons, they react like i have missed them and lock ring shakes. However if i press some 5 mm above them they react like they should, almost as if the screen isn't calibrated. that didn't happen on stock rom. And yeah during calls whole screen is dead to the touch, I tried pressing above those green and red phone symbol, but lock ring doesn't shake and that would mean it doesn't register a touch. Minor things really but they can be annoying
Tyrannar said:
.... One more thing, when i listen to music, and try to change song on the lock screen widget by pressing on screen buttons, they react like i have missed them and lock ring shakes. However if i press some 5 mm above them they react like they should, almost as if the screen isn't calibrated. that didn't happen on stock rom.....
Click to expand...
Click to collapse
When you don't even bother to read at least the first page of the ROM thread, it is best for you to restore to a stock ROM or try other ROM... you'll save the headache.
Tyrannar said:
Nope, whole screen is dead to the touch and so is the volume rocker. Only responsive key is the shut down key. I turn of the screen and turn it back on and everything works like nothing happened. One more thing, when i listen to music, and try to change song on the lock screen widget by pressing on screen buttons, they react like i have missed them and lock ring shakes. However if i press some 5 mm above them they react like they should, almost as if the screen isn't calibrated. that didn't happen on stock rom. And yeah during calls whole screen is dead to the touch, I tried pressing above those green and red phone symbol, but lock ring doesn't shake and that would mean it doesn't register a touch. Minor things really but they can be annoying
Click to expand...
Click to collapse
All you need to do is read the MyOneV thread.. Dev has fixed all the issues in the rom.
Sent from my One V using xda app-developers app
was mvalt
ckpv5 said:
When you don't even bother to read at least the first page of the ROM thread, it is best for you to restore to a stock ROM or try other ROM... you'll save the headache.
Click to expand...
Click to collapse
No headaches man, I wouldn't be using it for 3 months if i wasn't satisfied with it and satisfied I am. I did read on the latest update (from march 2013) that RC9.5 FX+ has all the previous fixes included (for example my Bluetooth works fine) so i didn't bother reading on. Anyway, my fault.
Deontologist said:
Has your touchscreen been damaged in any way?
Sent from my One V using Tapatalk 4 Beta
Click to expand...
Click to collapse
Touchscreen has no obvious damage, but the stock Android buttons stopped working a while back (I have an app which replaces) and this might be connected with the above issue.