Database Users

[Q] HELP - Unresponsive Screen

Hope any of you guys can help me on this. Last night my Leo's screen went totally unresponsive.
Could not get past the screen lock. Removed the battery, rebboted ... could not get the PIN code in.
I had seen this already two nights ago, but it got away once I moved in an area where I could get a reasonable signal (ultra-crappy where I am now on vacation).
Now Im'm beginning to think the signal thing was just a coincidence and that the problem is way more serious.
In total despair, I even tried a hard reset. To no avail.
Phone boots up fine. I can even sync to it (so yes, I can get to the registry). But since the only control is the screen ... not really a lot I can do with it.
I need to be in touch for work and I badly need the voice and internet connectivity (right now I'm using the wife's phone ...).
Any ideas besides getting an RMA from HTC?
Thanks a lot in advance.

Update: spoke with HTC support.
It looks like the issue is somehow triggered by the lock screen.
As suggested by HTC, I flashed again the 1.66 ROM upgrade and everything ran smoothly until the phone went in standby the first time.
Then, I was (and still am) unable to unlock the screen. And if I soft reset screen is unresposnsive again.
Right now I can just receive calls (I removed the PIN code from the SIM temporarily).
HTC told me to send it in for repair, but everything in Italy is closed until Aug 23rd and the only option I have is to ship it at my own expense to the UK and back (HTC will collect and deliver free of charge only within the same country).
Total bill some 100+ Euro plus driving 100 KM or so to the nearest courier collection point. A nightmare.
What really troubles me is that the problem surfaces only once the screen locks.
On one hand I follow HTC's support that if flashing 1.66 did not cure the issue, it cannot be software.
On the other hand, if it is indeed hardware, how come it freezes only after the first lock screen? Lock/unlock is a software thing. Screen should behave exactly the same way before or after the lock - shouldn't it?
Anyone here seen/heard of anything like this?

wow, gotta love those "closed for the summer" euro vacations.
If you reinstall the ROM, then why not disable the lockscreen until you can get it fixed?
You can install BSB tweaks and that has an option to disable autolock.

i had the same exact problem; it started freezing only on the lock screen then got worse and started freezing at random times while in use. I finally broke down and sent it in to HTC to check it out. I'm waiting to hear back with there diagnosis and I will pass along whatever they tell me.

Good to know the problem has come up somewhere else (if you're the only one you are most likely to hear it's your fault before they replace the most expensive component in the phone). Where are you located slimster?
How long have you been waiting for? HTC policy should be 7-10 working days from when they receive the phone at the lab (so they told me and I remember reading it somewehere here in xda too).

[HELP] my Omnia7 will not stay in standby! it switchs on alone

Hello guys,
I have a very strange but really bad problem: my omnia7 can't stay in standby.
When I press the power button, to turn off the screen and go in standby (so not the full turn off), my Omni7 wakes up alone, going on the unlock screen. In the same time, the phone rings with the ring that is played when you connect the phone for charging.
I've tried reboot, reset, hardreset, removing the sim-card, turning on/off "battery saver options" ... still that issue :crying:
Anyone has an idea?
I've flashed with a cooked rom (xda-devs Omnia7 Tango V4.0)
my current config :
OS version : 7.10.8779.8
hard version : 3.1.0.4
soft radio version : 2424.11.7.2
hard radio version : 0.0.0.800
loader version : 4.10.1.9
SOC version : 0.36.2.0
Thanks to any ideas, because that problem is killing me

my phone started doing this late last night too! i thorght it was because rain had gone into the power socket but if others are having same problem at the same time maybe not?
has your phone been exposed to water at all recently? is your phone jailbroken? cant realy think of other reasons
the problem stops when the phone is plugged in. is there anything that can trick the phone to thinking it is on charge? I have wphtweaks installed but the options there are not able to stop it

Hi,
I can't remember if my phone has been wet :/ I take care, so my phone never received water. But when I'm outside, under the rain, it's possible.
Today it was better, just a few times my phone wakes up alone.
I'll give you feedback in the next days. Let me know about yours

I managed to trick my phone into silence a few times earlier but it was difficult and then only lasted 5-10 minutes.
if yours didnt get wet it seems unlikely to do with water but I left mine ontop of the aga after removing the battery and over a relativly cool part. A few hours later and it seems to be working fine now.
I will report back if the issue arises again.
EDIT: Ahhhh!! STOP THE RINGING!!! started again this morning

Mine too !
This morning ... the ringing awakening problem !!!!!
But it was better this afternoon.
Really I don't know what happens.
Are we only two persons in the xda world with this problem????

this is realy weird now! mine was doing it in the morning but since about 12pm - 1pm it has been fine! I feel like its something to do with an installed homebrew app maybe.
I also have a custom rom but mine was flashed a long time ago and much older than yours. not sure which version
EDIT (1:10pm GMT): no problems since yesterday
EDIT2 (1:30pm GMT): again i spoke too soon!

Did you guys get this problem sorted out? Had the same problem recently and tried all the suggestions in other threads (bend USB pin, Reset/Restore Device etc) but nothing fixed it, so after being woken at 3am by constant charging tone, took to T-Mobile shop. They said it was a software problem. I said I'd tried all that and the most likely cause I'd seen on the internet was a duff USB port.
Anyway, T-Mobile sent it off for repair and 7 days later - returned and fixed. The repair sheet said software upgrade, but the phone had been reset to bog standard Phone 7, so unlikely. The T-Mobile repair tracking site (excellent) which shows blow-by-blow trace of what and where, showed initial software upgrade/no fix but I used their "contact us" facility to suggest a USB problem and by magic the repair tracking log showed a replacement USB port.
BTW - had to resort to an iphone and HTC android while Omnia was off for repair. Now I know why I like Phone 7 and can't wait for 8. The iphone GUI is so last decade and Android GUI is really just a copy of Windows 6.5 with XDA developers' tweaks isn't it.

Hi Wuzzok,
what do you mean by "bend USB pin" ?
Anyway, it seems like it's finished for me. I didn't get tht strange bug (soft/hard bug???) for a very long time. I just hope it's really over !

Same problem
Hi Folks,
I have the same problem, too. Yesterday afternoon on my way home the phone started ringing with the USB plug sound and always started up itself from standby mode.
As I have a custom ROM (mi7ROM) I first thought it could be a problem with the ROM - although I could not really believe it since it was running stable for months now. I flashed it again and nothing changed - still ringing and starting up itself
I managed to get rid of the sound by deleting the entry in the registry key "Local Machine\Current User\ControlPanel\Sounds\BatteryCharging\Sound" but that does not solve the real problem.
After reading here and in some other WP7 blogs I am sure that this is a hardware problem with the USB plug unit. As my phone is just 11 months old I opened an online ticket at "SAMSUNG online repair service" who promise to answer in the next 24 hours. So I just have to wait and see...

actual state
neutom said:
Hi Folks,
I have the same problem, too. Yesterday afternoon on my way home the phone started ringing with the USB plug sound and always started up itself from standby mode.
As I have a custom ROM (mi7ROM) I first thought it could be a problem with the ROM - although I could not really believe it since it was running stable for months now. I flashed it again and nothing changed - still ringing and starting up itself
I managed to get rid of the sound by deleting the entry in the registry key "Local Machine\Current User\ControlPanel\Sounds\BatteryCharging\Sound" but that does not solve the real problem.
After reading here and in some other WP7 blogs I am sure that this is a hardware problem with the USB plug unit. As my phone is just 11 months old I opened an online ticket at "SAMSUNG online repair service" who promise to answer in the next 24 hours. So I just have to wait and see...
Click to expand...
Click to collapse
Samsung sent me an offer to send the phone in for repair - but what should I say, the problem solved itself. For two days now the phone works normal again. So I had to cancel the service call .

mine hasnt done it in a long time either. looks like its just a temporary thing. I wonder what caused it! For me it started after I was using my phone in the rain and the usb slide was open so thats my suspect.

You may be right. Mine is "quiet" now, since a long time. Water may be the cause.

Update
Hi folks,
mine is mostly quiet again, too. Only few incidents "happen" but they do not last very long - only a few minutes. It's somehow spooky but I do not want to send it in to Samsung now when the error it not constantly reproducible.
I agree with you that there might be a correlation with humidity although I am sure that it did never get wet and I almost always keep the USB-shutter closed. Who knows ...

Sent it in
Finally I sent it in for repair today. It started ringing permananently two days ago...
Now I have to wait and see.

Final state
Okay, I received it back... and it works.
First they did nod find and could not reproduce the failure and wanted to send it back - only with a new flashed image - but fortunately the technician called me and I could describe the problem again. After waiting a few hours, the fault appeared again and they decided to change the mainboard.
I hope, that's all :laugh:

Hello,
Me too it makes me after my omnia 7 is dropped in water, but problem solved.

Me too
WuzzoUK said:
Did you guys get this problem sorted out? Had the same problem recently and tried all the suggestions in other threads (bend USB pin, Reset/Restore Device etc) but nothing fixed it, so after being woken at 3am by constant charging tone, took to T-Mobile shop. They said it was a software problem. I said I'd tried all that and the most likely cause I'd seen on the internet was a duff USB port.
Anyway, T-Mobile sent it off for repair and 7 days later - returned and fixed. The repair sheet said software upgrade, but the phone had been reset to bog standard Phone 7, so unlikely. The T-Mobile repair tracking site (excellent) which shows blow-by-blow trace of what and where, showed initial software upgrade/no fix but I used their "contact us" facility to suggest a USB problem and by magic the repair tracking log showed a replacement USB port.
BTW - had to resort to an iphone and HTC android while Omnia was off for repair. Now I know why I like Phone 7 and can't wait for 8. The iphone GUI is so last decade and Android GUI is really just a copy of Windows 6.5 with XDA developers' tweaks isn't it.
Click to expand...
Click to collapse
Are you really sure that the problem is USB port.. Mine too behave like this. I've tried to remove battery, factory reseting, reflashing ROM. But nothing works. Mine is Samsung focus

post to remove

Sensors and MCU not working

Hi guys,
New owner of a S4 (GT-I9505 international) here with a problem. 2 days ago I noticed the screen wasn't rotating anymore. I used to rotate it portrait/landscape in applications like Camera or Internet (browser). The moment when it started to bother me was when looking at pictures with the phone in portrait and the image was landscape. Trying to rotate the phone didn't help. It was frozen. I called a buddy of mine who has some experience with Samsung devices and told me to verify the "Auto-Rotation" settings. It was all OK and enabled. Then he suggested turning the phone off and pulling out the battery and SIM card for 5 minutes and putting it all back. This didn't help either. Finally we got to the point where he told me to enter *#0*# in the Phone dialing application. As you might already know, this code gives you access to the "testing" hidden utility. There I tested all the options available. Everything was fine except for the Sensors and SensorHub Selftest.
In the Sensors section, all the tests failed, starting with the Accelerometer and ending with the Temperature. I uploaded screenshots taken during the tests. Please remember this started 2 days ago. Before this it was working perfectly. I don't recall making and major changes like updating any OS components or installing/running stress utilities related to sensors or device behavior. After doing some research online and reading about other people's similar problems I got to the point where I started to suspect a problem with the MCU (Micro Controller Unit). This component, according to Samsung, controls all the sensors and reads raw data from them without accessing the AP (Application Processor) this way extending the battery life. I believe the problem is here because it seems odd that none of the sensors are working all of a sudden. Can this component put the sensors into a sleep state and shut them down completely? Might this be the case here?
Below are the solutions I tried in order to revive the MCU and finally the sensors. I was all without success:
1) Turned off the phone and pulled the battery and SIM out. Put the back in after about 5 minutes. Result: sensors not working.
2) Reset to factory-settings from the settings option while the phone was in the working state (turned on). Result: sensors not working.
3) Rooted the phone, installed Clockwork Recovery, made a full system and applications backup and then installed custom ROM (two actually: PACMan, Google Play Edition (4.3)). I did this in order to exclude a problem related to drivers in the stock Samsung ROM, even if it was logical that Samsung being the owner and manufacturer of the device might have the "best" drivers and applications for inquiring the device components/sensors. I am aware this ended the warranty for me, but can I know it can easily be undone. Result: sensors not working.
4) Restored the original stock Samsung ROM. Result: sensors not working.
The utilities used for sensor testing were: Sensor Kinetics and Sensor Tester. Both can be found in the Play Store. On my wives phone, which is an old HTC Desire, both utilities picked up the available sensors and created graphs with the results. On my S4, I only got blank charts/graphics/results. In Sensor Kinetics for the Gyro for example, the message was "Waiting for the Gyroscope sensor...", just that, stuck.
If there are any other guys (or ladies!) out there who encountered this awful experience, please reach out and tell me if you found any practical solution, any other then just taking the device back to warranty. I'm open to any suggestions.
Best regards,
Andrei

Most likely a defective device ... can't you claim warranty and sent it back?

Sounds like hardware failure. This would be an issue for Samsung to solve.
Sent from my GT-I9505

AvelonTs said:
Most likely a defective device ... can't you claim warranty and sent it back?
Click to expand...
Click to collapse
Unfortunately I bought it second-hand and it does not have any warranty. I guess it's one of those moments I wish I had patience and gathered more cash to buy a new one from the store. Anyway, it's my bad luck. I had it working perfectly for weeks after buying it. I will use it like this for the time being..

i´ve got the exact same problem since yesterday...
i think i´ll take it to the shop for warranty

I've got the exact same issue. All sensors are having the same issue. None are working,
I found out because my camera app was not switching between landscape and portait any more. All pictures are saved as landscape...
Called Samsung Netherlands and they told me to wipe my phone (still latest original stock ROM) and try again.
Making a backup now using Kies... and will hard reset it afterward and check the sensors.again.
Probably not going to work... So I have to send it in...

darklord said:
I've got the exact same issue. All sensors are having the same issue. None are working,
I found out because my camera app was not switching between landscape and portait any more. All pictures are saved as landscape...
Called Samsung Netherlands and they told me to wipe my phone (still latest original stock ROM) and try again.
Making a backup now using Kies... and will hard reset it afterward and check the sensors.again.
Probably not going to work... So I have to send it in...
Click to expand...
Click to collapse
Hi there. I had same problem with sensors and MCU test failed, so i took phone to service. They said its hardware failure and replaced main board. Im picking phone tommorow and we will see...

Hi guys,
I took mine to a local phone service, not the official one, but they are an affiliate. They could not figure out exactly what the problem was so they replaced the logic/main board just for testing. It was all working fine. They called and informed me of the findings. Given the fact I don't have warranty for it, they suggested to send it to our main service in Bucharest where they have a more sophisticated testing equipment. It is possible to get a more precise answer regarding the defective component and maybe a less pricey solution to the problem. At this time, the only viable option is to get a new logic board in place, which is about to set me back 250 USD. I will get an answer from Samsung in Bucharest by tomorrow or the day after tomorrow.
I will get back to you with my final solution... hopefully something not so expensive
@darklord, @eweu: please post back you findings. Maybe in the future when some other unfortunate owner finds his way in here, will have a better understanding of whats on the plate for him.
Thanks,

Hard reset did not work as expected. Going to drop it off at a local official repair center....

S4 Sensors failing
I have the same problem with my S4 GT-I9505 device not auto-rotate, air gestures with gyroscope and accelerometer tests failing. S4 been back for 3 weeks to Samsung for repair came back and failed again after 1 week

KSal7506 said:
I have the same problem with my S4 GT-I9505 device not auto-rotate, air gestures with gyroscope and accelerometer tests failing. S4 been back for 3 weeks to Samsung for repair came back and failed again after 1 week
Click to expand...
Click to collapse
After installing some other ROM's and playing with different CSC's I have no sound and even no wireless and only Edge speeds on some ROM's. Restoring from backups, wireless came back and HSDPA+ also, but no luck with sound what so ever. Now, I have a tablet more or less. Thanks Samsung, this is great!

canaris1780 said:
After installing some other ROM's and playing with different CSC's I have no sound and even no wireless and only Edge speeds on some ROM's. Restoring from backups, wireless came back and HSDPA+ also, but no luck with sound what so ever. Now, I have a tablet more or less. Thanks Samsung, this is great!
Click to expand...
Click to collapse
Flashed I9505XXUDMH8_I9505OXXDMHA_BTU, sound and wlan working again. Previous problem with MCU/sensors still there.

i'm tired
canaris1780 said:
Flashed I9505XXUDMH8_I9505OXXDMHA_BTU, sound and wlan working again. Previous problem with MCU/sensors still there.
Click to expand...
Click to collapse
really i'm tired to solve this issue.
when i install new stock software the sensors work fine just a few minutes only yhen return to fail again.
i think its software issue and i'll solve it :good::good::good:

Sensors work again
:laugh: :victory:
Its work right now by itself
:crying:
after uploading the pictures its fail again

abdali_m2 said:
:laugh: :victory:
Its work right now by itself
:crying:
after uploading the pictures its fail again
Click to expand...
Click to collapse
I have the same thing here
all sensors are broken because of SensorHub BIN FW Version: AT0199999
then i try to update firmware with *#2663# it failed.

I have the same problem with my S4 GT-I9505.
Suddenly the device do not auto-rotate, and no air gestures with gyroscope and accelerometer are working.
The SensorHubTest end with FAIL.
Mid december I got one OTA firmware update and I didn't notice any problems first.
A few days after newyear I notice that my auto-brightness adjustment did not work properly.
Can't remember if auto-rotate didn't work when I notice the auto-brightness problem.
But finally I am here because I searched for sensors problems.
I did the SensorsHub Test with *#0*# and it ends with FAIL.
It seems that there is a problem with the 4.3x firmware.
With 4.2x all was fine.
Can anybody confirm my thoughts - that the firmware is broken and not the MCU itself?
What can we try? Downgrade? I read that one was lucky with "factory reset" but it didn't helped to revive the MCU of my device.
Thanks for reading
and answering
___
DK

Hi, i am a owner of a sch-i545 phone, and i have the same problem with the phone: no response of any sensor and a fail on test (or upgrade firmware) of the sensorhub.
At this time i was tried a lot of solutions: i was flashed stock firmware, custom firmware, and of course a factory reset (by the way, the first time with this problem was when i did it a single factory reset), its still broken the communication with the sensors.
I get back to life the phone when i upgrade the phone from 4.2 to 4.3 (sadly) and get lost when i update the binaries in super su (previously rooted with vroot).
Yesterday i give the phone to a technician (a close friend of another best friend), he will test the phone on this weekend to determine what is the problem to try to fix it.
When He fix this phone, i will post any news!
Regards.

remy1004 said:
At this time i was tried a lot of solutions: i was flashed stock firmware, custom firmware, and of course a factory reset (by the way, the first time with this problem was when i did it a single factory reset), its still broken the communication with the sensors.
I get back to life the phone when i upgrade the phone from 4.2 to 4.3 (sadly) and get lost when i update the binaries in super su (previously rooted with vroot).
Regards.
Click to expand...
Click to collapse
Thanks for your answer. I have hope that the next firmware will fix it.
What is strange that none of any reseller/privers know this problem. It seems that also Samsung has no knowledge about this special error.
Well if the next firmware didn't fix the problem, I can replace my model with a working one, that is what the guy at the phone shop offers to me.
___
DK

Same Problem Here
Hi guys, I'm new to this forum so be nice :angel:
I am having the same problem in that none of the sensors are working which indicates that it is a connection issue or the actual hub not working or the firmware and not the individual sensors themselves. I have thought about this and looked around and to me it seems like there are only 3 possibilities for the problem:
1) The SensorHub BIN FW Version is out of date and needs to be updated manually (not through *#2663 as it doesn't work)
2) There is a connection issue e.g. the cable from the sensorhub to the motherboard is loose or broken
3) The sensorhub is broken (not the sensors)
I will try to find the firmware files and see if I can do a manual update. If that fails I will open up the phone and see if the cable is connected/broken. If I still cannot solve the issue, I will have to take it to the shop and hope I can fix it off warranty (I bought it second hand)
Dan

shadowsoulxp said:
Hi guys, I'm new to this forum so be nice :angel:
I am having the same problem in that none of the sensors are working which indicates that it is a connection issue or the actual hub not working or the firmware and not the individual sensors themselves.
[...]
I will try to find the firmware files and see if I can do a manual update. If that fails I will open up the phone and see if the cable is connected/broken. If I still cannot solve the issue, I will have to take it to the shop and hope I can fix it off warranty (I bought it second hand)
Dan
Click to expand...
Click to collapse
Thanks Dan for your reply.
I assume that your S4 shows the same behaviour as my one and the phone is still working fine.
The sensorhubtest failed and your light sensor for automatic adjusting and the sensor for turning the display are not working.
What is really strange that I went to a vodafone shop in Hamburg and ask them if there is any other one having problems with the S4.
You know the answer? They where wondering and telling me that this is wierd and they heard the first time of such an issue from me.
I showed them the device and showed them how I test the sensors. *#0*# funny they didn't know this combo
I hope that you succeed and share your knowledge,
with best regards.
___
DK

[Q] GS5 900F Clock/Time bug?

As per usual, I get the weirdest bugs/faults with my devices!
Just got a new S5 32GB from Singapore (900F variant). Was on holiday there, and they don't have that version in Australia where I live. Anyway, I tested the heck out of the thing while I was there, as the warranty is only valid in Singapore, and I wanted to tease out any hardware faults early.
When I was changing the SIM card once, I noticed that the system time had lagged a significant amount while the phone was off. In fact, if you turn it off and take out the battery for long enough, the time can change to several days in the past! To the best of my knowledge, modern phones, like PCs, keep accurate time even with the phone battery removed. I have confirmed this with my old S3, as well as other Samsung phones at the store.
After several visits to the local service center in Singapore, I finally convinced them to change the mainboard. After the repair, the problem was still present.
Has anyone else experienced this? Or can they test this? I keep the Auto time Update settings always off, and have done that for all my phones.
Changing of the main board would seem to exclude a hardware issue, but then there were some questions as to whether the main board was actually replaced by the repair center. The online tracking of the repair order ended in 'unable to be done due to request cancelled', which made me *really* suspicious, and the IMEI and serial numbers remained the same. Have never dealt with Samsung in Singapore before, so not sure how things work there. That's another story though, I suppose...

Update: Have gotten the phone back in my actual hands, and tinkered more with the problem. Have noticed that after a battery pull, the system time seems to default back to certain points in time (this time, 2118hrs, 18th July 2014).
Can anyone try a battery pull (leaving the battery out for a few minutes) with Auto Time Update off to see if this happens to their S5?
Thanks!

ZenWatch Always-On screen option doesn't work

My newly purchased ZenWatch is set to have Always-On Screen but after 5 seconds it fades a little, then, shows the dimmed version for a second, then goes completely black so I can't see anything until I wake it again.
Wear version 5.0.1
Connecting to Android 4.4.4
This happens the same with any watch face I select: pre-installed or new custom ones. I have tried uninstalling Wear and ZenWatch Manager, resetting the watch and starting over again, same thing happens.
Could an app or watchface I have installed be interfering with the Always-On option somehow??
I don't know if this is related but I had to return my first watch as it didn't charge, so this is the second one connected to my phone (after 'forgetting' the first then pairing the new one).
When I click on the Always-On tick box on my phone, it immediately updates this option showing on the Watch so it's definitely sending the command to it. It shows as Always-On selected on the watch.
Has anyone else had this bug and know how to fix it? Thanks.

Is cinema mode on?

annik1s said:
Is cinema mode on?
Click to expand...
Click to collapse
Thanks, no, cinema mode isn't on.
It's really curious, the screen fades slightly in brightness after five seconds, then goes to the dim version of the watch face, then goes completely black a second later. One tap brings it back so I'm it's like the regular off screen mode.

TheGreatWaldopepper said:
My newly purchased ZenWatch is set to have Always-On Screen but after 5 seconds it fades a little, then, shows the dimmed version for a second, then goes completely black so I can't see anything until I wake it again.
Wear version 5.0.1
Connecting to Android 4.4.4
This happens the same with any watch face I select: pre-installed or new custom ones. I have tried uninstalling Wear and ZenWatch Manager, resetting the watch and starting over again, same thing happens.
Could an app or watchface I have installed be interfering with the Always-On option somehow??
I don't know if this is related but I had to return my first watch as it didn't charge, so this is the second one connected to my phone (after 'forgetting' the first then pairing the new one).
When I click on the Always-On tick box on my phone, it immediately updates this option showing on the Watch so it's definitely sending the command to it. It shows as Always-On selected on the watch.
Has anyone else had this bug and know how to fix it? Thanks.
Click to expand...
Click to collapse
Hi,
I'm very curious to know if you have found a solution to this problem as my new ZenWatch is doing the exact same thing. Asus support has told me it's a firmware issue but that seem odd to me as the feature seems to work for others.

Chewie01 said:
Hi,
I'm very curious to know if you have found a solution to this problem as my new ZenWatch is doing the exact same thing. Asus support has told me it's a firmware issue but that seem odd to me as the feature seems to work for others.
Click to expand...
Click to collapse
Oh thank you for telling me I'm not at least alone! No I haven't found a solution - I have reset the device, removed all the Wear apps one by one from the phone (in case a setting is interfering) and nothing makes it work as it should.
So... firmwear meaning the version of Wear that's installed on the watch? I was considering seeing what options are on the debug? menu but following online instructions I couldn't get this to work (you have to swipe from top left etc). I'm on 5.0.1 build LWX48S bought in the UK, how about you?
Have you had another watch that you replaced? I have and thought maybe settings got confused between watches. On my previous one, the always-on screen worked fine on it. When I booted it up for the first time, it did a software update. It however had a power problem (didn't charge after 2 days), so I replaced it.
The replacement didn't update when booted up, and doesn't update when I reset, so I assumed it shipped with newer firmwear - maybe the always-on problem is caused by this?
One weird problem with the replacement watch is that it notified me that it was almost out of power, despite having about 75% batter left, then it switched off and didn't turn on until charged over night. Only happened once.
I was planning on swapping it for another at the shop but someone else having the issue makes me think it's software. Might wait for an update, but if not solved long term then I'm not happy - I want it to look like a watch rather than a blank screen.

TheGreatWaldopepper said:
My newly purchased ZenWatch is set to have Always-On Screen but after 5 seconds it fades a little, then, shows the dimmed version for a second, then goes completely black so I can't see anything until I wake it again.
Wear version 5.0.1
Connecting to Android 4.4.4
This happens the same with any watch face I select: pre-installed or new custom ones. I have tried uninstalling Wear and ZenWatch Manager, resetting the watch and starting over again, same thing happens.
Could an app or watchface I have installed be interfering with the Always-On option somehow??
I don't know if this is related but I had to return my first watch as it didn't charge, so this is the second one connected to my phone (after 'forgetting' the first then pairing the new one).
When I click on the Always-On tick box on my phone, it immediately updates this option showing on the Watch so it's definitely sending the command to it. It shows as Always-On selected on the watch.
Has anyone else had this bug and know how to fix it? Thanks.
Click to expand...
Click to collapse
Just got my Zenwatch and I am having the same problem... Resetting the watch helped. But, I am still not getting the watch to vibrate on notifications. It vibrates when I set an alarm (on the watch) to it's not the vibrating device itself...

TheGreatWaldopepper said:
Oh thank you for telling me I'm not at least alone! No I haven't found a solution - I have reset the device, removed all the Wear apps one by one from the phone (in case a setting is interfering) and nothing makes it work as it should.
So... firmwear meaning the version of Wear that's installed on the watch? I was considering seeing what options are on the debug? menu but following online instructions I couldn't get this to work (you have to swipe from top left etc). I'm on 5.0.1 build LWX48S bought in the UK, how about you?
Have you had another watch that you replaced? I have and thought maybe settings got confused between watches. On my previous one, the always-on screen worked fine on it. When I booted it up for the first time, it did a software update. It however had a power problem (didn't charge after 2 days), so I replaced it.
The replacement didn't update when booted up, and doesn't update when I reset, so I assumed it shipped with newer firmwear - maybe the always-on problem is caused by this?
One weird problem with the replacement watch is that it notified me that it was almost out of power, despite having about 75% batter left, then it switched off and didn't turn on until charged over night. Only happened once.
I was planning on swapping it for another at the shop but someone else having the issue makes me think it's software. Might wait for an update, but if not solved long term then I'm not happy - I want it to look like a watch rather than a blank screen.
Click to expand...
Click to collapse
I have the same version of Wear with the same build number and I am also in the UK (which may be the common factor here as it is looking quite likely to be a manufacturing batch issue). When I first got the my watch from Heathrow terminal 2 it had an older version of Wear pre installed and the always on mode was not working then either. This would suggest the Wear version is not the issue here but the ASUS firmware which links Wear to the hardware is at fault.
I have also done the uninstall all apps from my Nexus 6 and factory reset the watch thing but ultimately it made no difference.
This the response I received from ASUS BTW,
Thank you for contacting ASUS. We are sorry to hear about this problem. I believe this is due to a firmware bug, it is not a setting that you can choose.
Please be advised that I will forward your feedback to our HQ development department to see if our engineers can resolve this problem in the next firmware update.
We are sorry for the inconvenience caused.
I also share your sentiment that a watch that doesn't tell the time is not much use to me so I will be rolling the dice and returning it for a replacement unit in the hope for a device that works as advertised.

Chewie01 said:
I have the same version of Wear with the same build number and I am also in the UK (which may be the common factor here as it is looking quite likely to be a manufacturing batch issue). When I first got the my watch from Heathrow terminal 2 it had an older version of Wear pre installed and the always on mode was not working then either. This would suggest the Wear version is not the issue here but the ASUS firmware which links Wear to the hardware is at fault.
I have also done the uninstall all apps from my Nexus 6 and factory reset the watch thing but ultimately it made no difference.
This the response I received from ASUS BTW,
Thank you for contacting ASUS. We are sorry to hear about this problem. I believe this is due to a firmware bug, it is not a setting that you can choose.
Please be advised that I will forward your feedback to our HQ development department to see if our engineers can resolve this problem in the next firmware update.
We are sorry for the inconvenience caused.
I also share your sentiment that a watch that doesn't tell the time is not much use to me so I will be rolling the dice and returning it for a replacement unit in the hope for a device that works as advertised.
Click to expand...
Click to collapse
Did you return it in the end?
After several frustrating emails with ASUS support in which they replied with general info on how the Always on-screen setting can be set, then asked me what build number I had even though I told them this in the first place, they concluded it must be a hardware problem.
"Taking in consideration that you have both the settings enabled on your watch as on your connected device and you are using the latest firmware, I also believe this is being cause by a hardware fault. Please return the ZenWatch back to your reseller."
So I took the plunge and exchanged it for the second time with suspicious staff at the shop (it was past their 21 day return policy cut-off, so I had to order another, then swap the new one for mine, on their system they refunded the new one). Hey presto, the new one works fine!
This one shipped with: 4.4w.2, KNX01W, updated to: 5.0.1, LWX48S.
So overall sounds like perhaps just a hardware issue. I know it's a new product but it's lucky I like the look of the watch so much that I'm tolerating quite a few teething problems. The one I have now has a very slight ridge on the right hand side of the screen where it meets the metal frame, which you can feel when swiping right. Hopefully I'm just being overly-fussy now and I won't notice after a while, but it's not as smooth as my previous two watches. On the left of the screen it's completely flush.

TheGreatWaldopepper said:
Did you return it in the end?
After several frustrating emails with ASUS support in which they replied with general info on how the Always on-screen setting can be set, then asked me what build number I had even though I told them this in the first place, they concluded it must be a hardware problem.
"Taking in consideration that you have both the settings enabled on your watch as on your connected device and you are using the latest firmware, I also believe this is being cause by a hardware fault. Please return the ZenWatch back to your reseller."
So I took the plunge and exchanged it for the second time with suspicious staff at the shop (it was past their 21 day return policy cut-off, so I had to order another, then swap the new one for mine, on their system they refunded the new one). Hey presto, the new one works fine!
This one shipped with: 4.4w.2, KNX01W, updated to: 5.0.1, LWX48S.
So overall sounds like perhaps just a hardware issue. I know it's a new product but it's lucky I like the look of the watch so much that I'm tolerating quite a few teething problems. The one I have now has a very slight ridge on the right hand side of the screen where it meets the metal frame, which you can feel when swiping right. Hopefully I'm just being overly-fussy now and I won't notice after a while, but it's not as smooth as my previous two watches. On the left of the screen it's completely flush.
Click to expand...
Click to collapse
I went to take mine back last week only to be told by PC World that this product can only be bought on-line and I would have to buy another one and then return the first for a refund. Which is a bit of a scam to me as the replacement was at a higher price than the first one I bought from Heathrow Duty Free.
I am due to collect the replacement and have an argument about the price difference tomorrow so finger crossed I get a working one as well.

Chewie01 said:
I went to take mine back last week only to be told by PC World that this product can only be bought on-line and I would have to buy another one and then return the first for a refund. Which is a bit of a scam to me as the replacement was at a higher price than the first one I bought from Heathrow Duty Free.
I am due to collect the replacement and have an argument about the price difference tomorrow so finger crossed I get a working one as well.
Click to expand...
Click to collapse
Ha, mine was from PC World too. I guess it's not their fault that your original one was bought duty free & therefore cheaper, but really if it's faulty they should treat it as such. They did offer me the option of booking it in as faulty, then it would have been sent off to ASUS and in all probability replaced with a new one anyways, but he didn't know how long this would take. So I just took the other option of buying another, having it delivered to the store the next day then swapping & refunding the latest transaction.

TheGreatWaldopepper said:
Ha, mine was from PC World too. I guess it's not their fault that your original one was bought duty free & therefore cheaper, but really if it's faulty they should treat it as such. They did offer me the option of booking it in as faulty, then it would have been sent off to ASUS and in all probability replaced with a new one anyways, but he didn't know how long this would take. So I just took the other option of buying another, having it delivered to the store the next day then swapping & refunding the latest transaction.
Click to expand...
Click to collapse
Well the good news is I now have the replacement watch and it works as advertised. I did have to complain a lot to get the difference in price resolved. I ended up complaining so much that the store manager gave me the money out of his own pocket just to get rid of me .