HI All,
Had my bip for 2 weeks, all working fine until now. Major issue in that the brightness doesn’t adjust when I amend the settings and the backlight (i.e. lift wrist) function doesn’t work, the screen doesn’t light up at all, ever, even when I press the button or flick through the screen menus. Over the 2 weeks I’ve worn it constantly, washed dishes a few times otherwise just your usual day-to-day activities. Everything works apart from this which is a major issue as means the watch is only useful during the day, in dark can’t make anything out.
Can anyone help please?
holidayinning said:
HI All,
Had my bip for 2 weeks, all working fine until now. Major issue in that the brightness doesn’t adjust when I amend the settings and the backlight (i.e. lift wrist) function doesn’t work, the screen doesn’t light up at all, ever, even when I press the button or flick through the screen menus. Over the 2 weeks I’ve worn it constantly, washed dishes a few times otherwise just your usual day-to-day activities. Everything works apart from this which is a major issue as means the watch is only useful during the day, in dark can’t make anything out.
Can anyone help please?
Click to expand...
Click to collapse
Is there anything I can try to test the backlight? Whether it is the light itself or some function I may have disabled?
Can I somehow reinstall an OS on the watch itself?
I don't have any warranty or options to return as bought from someone who no longer wanted it (open box but otherwise new).
Hi,
I've got the same issue. After contacting Amazfit support, they say that my product may have a default. So I have to contact Gearbest to have another unit
Do you have any new information ?
Unfortunately not, I did contact amazfit support who told me to video the issue and send it in. I haven't had a chance and as I have no option to return, the watch is just basically gathering dust. When it worked, it worked really well but for the £ I might just purchase a mi band instead.
this seems to be caused by non official faces. put an official face back on and it works.
That didnt work for me either, tried rebooting/restoring to default, different apps on the mobile, as someone not too techy feel like exhausted all options and left disappointed the screen does not increase/decrease brightness never mind illuminate the backlight. Thanks though!
Looks like a recent issue
I got my watch already for a while. Never had any issues until now. Backlight is done after swimming. All the rest still works. Factory reset didn’t work. Adjusting brightness to its maximum neither. So anyone experience with the after sale service?
I’ve bought my watch with gearbest and am trying to send them a technical ticket
my amazfit bip backlight is not working now as well help please!
Related
Hello all and please forgive my poor english
I really love this tablet (thickness, battery, weight, screen) BUT i have a major problem with it : i often need to tap 2 or 3 times on something in order to launch/select it and it ruins my global experience with the tablet :crying:
Do you guys have this problem and is there a way to alter the sensivity of the screen ?
Thanks
yanouch said:
Hello all and please forgive my poor english
I really love this tablet (thickness, battery, weight, screen) BUT i have a major problem with it : i often need to tap 2 or 3 times on something in order to launch/select it and it ruins my global experience with the tablet :crying:
Do you guys have this problem and is there a way to alter the sensivity of the screen ?
Thanks
Click to expand...
Click to collapse
Yes, I have the same problem. Some say, it's software issue, and suggest to wait until tab gets updated.
xbad1 said:
Yes, I have the same problem. Some say, it's software issue, and suggest to wait until tab gets updated.
Click to expand...
Click to collapse
Yeah that's what i expected but wanted just to know if others had the same problem and if there was already a workaround for this
Many people have this problem, including a number of reviewers.
Nevertheless Sony refuses to acknowledge the existence of the issue. When I called them, the guy said "You are the first to report such a problem". (Probably he lied and was advised "from above" to say so...)
The customer is left in the cold!
Some people have a return policy - what if one waits for a software update, the return period expires, the update comes, but it doesn't fix the problem and it turns out to be a hardware problem??
The information politics of Sony and other companies (yes, Google, you too!) is an absolute PILE OF S**T!!
Yup, me too. The annoying thing it is difficult to document. Yesterday my tablet was charging and I turned the screen on using power button - lock screen didn't react at all to my inputs. Tried switching screen on/off a few times but it didn't help. Also tried double-tap to wake with no success. Went to get my camera to document, then of course it started working...
I've written this elsewhere, but this is how I notice the touch screen problems:
For me the tablet randomly doesn't recognize touches during the below instances. In all cases either going to the home screen and relaunching the app or turning the screen off/on will solve the problem. The problems occur several times per day but not constantly.
Sometimes opening apps will cause everything but the bottom android-buttons to be non-responsive. This can happen in any app it seems, including native ones such as Google Play.
Sometimes the lockscreen doesn't recognize touches at all.
While charging I've had issues getting the touchscreen to recognize touches, disconnecting the charger has helped.
Double-tap to wake seems to be very moody, sometimes working sometimes not. Sometimes it turns the screen on even by me just holding the tablet with my palm resting against the screen.
While not a bug per se, also the android-buttons seem very picky that you have to hit them right on the spot to work.
Other threads on same topic:
http://talk.sonymobile.com/t5/Xperia-Z2-Tablet/Touch-screen-problem/m-p/620325
http://community.sony.fi/t5/Tablets/Xperia-Z2-tablet-touch-screen-issue/td-p/1582051
http://www.android-hilfe.de/sony-xp...screen-reagiert-nicht-immer-zuverlaessig.html
Damn ! i'm not alone....
One forumer said he thinks that switching OFF Stamina mode helped a little bit...
I don't have my tablet with me, can someone test this ?
"A little bit" help is NOT enough.
The touchscreen MUST work perfectly, whether with Stamina Mode on or off or whether with Mode XY on or off. No discussion.
Sony HAS to fix this.
Already solved in .55 firmware
hasenbein1966 said:
Nevertheless Sony refuses to acknowledge the existence of the issue. When I called them, the guy said "You are the first to report such a problem". (Probably he lied and was advised "from above" to say so...)
Click to expand...
Click to collapse
The same experience with Z1 compact and support. Told them the camera is really broken - they told me there is absolutely nothing wrong with the camera and I'm the first one who got this problem. That was some weeks before, now they officialy added that maybe some devices are defect.
But that´s Sony, they give a **** about u, don't even try to contact the support.
I'm also having this issue, if I'm using the Sony sleve it's impossible to use the touchscreen as it will tip over when I press hard enoug for the screen to actually register it.
No problem here.
Only early days yet. The only prob I've got atm is Dropbox isn't showing up in the Album.
Edit: Fixed the Dropbox problem by using the Dropsync app.
I also seem to get this. The tablet works fine when tilted at an angle but for some reason can be completely unresponsive when it's laid flat. Would this suggest a hardware issue or a software bug?
I also get this, sometimes it's like I just need to press harder (so hard the tablet falls over when using the cover as a stand), but other times it seems that no matter how hard I press or how many fingers I apply it doesn't register a thing for periods at a time.
I'm lead to believe that this is either software or firmware considering the intermittent nature. Are there any custom ROMs out yet that we could flash to eliminate the software aspect?
I have same problem, most noticeable in Chrome, switching tabs fails to register 10% of time. I can only think Sony have a hardware quality control issue with the digitizer as if it was firmware related, surely everyone would be suffering. Strange none of the reviews have picked this up, but I'm going to have to return mine.
No, no, no.
It's most surely a firmware problem!
The electric current threshold for registering a touch is set too high. So if the tablet lies on a non-conducting surface, and especially if it was not touched for a longer time, there will be touch problems. Also touching the tablet with a fingernail will not suffice because nails conduct current worse than skin. Other tablets which have a lower current threshold also accept fingernail touches.
I'm very sure: If you hold the tablet with one hand and touch with the other (and don't accidentally use fingernails), touch will be OK! Right? This is because more current will flow.
The .55 firmware which is out for LTE devices already and will follow for WiFi devices lowers the threshold and thus fixes the problem.
Up to then always take the tablet in your hands when operating it.
Interesting theory, just gave it a go, inclusive, but does seem worse in case. However if Sony aware, why have they not rushed out firmware as otherwise initial user experience is ruined.
QUOTE=hasenbein1966;52005720]No, no, no.
It's most surely a firmware problem!
The electric current threshold for registering a touch is set too high. So if the tablet lies on a non-conducting surface, and especially if it was not touched for a longer time, there will be touch problems. Also touching the tablet with a fingernail will not suffice because nails conduct current worse than skin. Other tablets which have a lower current threshold also accept fingernail touches.
I'm very sure: If you hold the tablet with one hand and touch with the other (and don't accidentally use fingernails), touch will be OK! Right? This is because more current will flow.
The .55 firmware which is out for LTE devices already and will follow for WiFi devices lowers the threshold and thus fixes the problem.
Up to then always take the tablet in your hands when operating it.[/QUOTE]
POTENTIAL FIX FOUND (ROOTED ONLY)!
Rooted users can try this fix, works for me! Touch seems to work perfectly now, also when tablet not in hands and lying on non-conducting surface!
Edit the file
/system/usr/idc/clearpad.idc
and alter these two lines:
Code:
touch.pressure.scale = 0.0001
(original value: 0.1)
and
Code:
touch.filter.level = 1
(original value: 2)
Don't forget a nandroid before
Please report whether it helped! :good:
P.S.: just for the curious - on the first Tablet Z, the two values are also lower: touch.pressure.scale is 0.0074, and touch.filter.level is also only 1.
Thanks for suggestion but dont wish to root (I use it to watch Sky which wont work if rooted) - seems there is more assistance on this forum to the issue than from Sony. I'll give it another week for a firmware fix before returning it.
elaborate...
nos1609 said:
Already solved in .55 firmware
Click to expand...
Click to collapse
If this is fixed in the 55 firmware then how do you get it?
I haven't had a firmware update?
I'm using 16GB Wi-Fi only in the UK
---------- Post added at 09:17 PM ---------- Previous post was at 09:11 PM ----------
homme_fromage said:
If this is fixed in the 55 firmware then how do you get it?
I haven't had a firmware update?
I'm using 16GB Wi-Fi only in the UK
Click to expand...
Click to collapse
My bad, didn't read all the way through, ignore me.
Now after a few days I can say:
With the root fix described above, my tablet works like butter. Simply perfect. :good:
Only instance where I have still problems is when the tablet was lying around for a while and I try to operate the touchscreen without taking it in my hands. Then sometimes (not always) the screen doesn't react, but only for a short time.
The problem seems to be related to static electricity.
Hi, i have had my tablet for about 1 week, straight after starting it up i had a fw update which is 17.1.1.A.0.402 which i am assuming is the latest?
anyway i have read a lot about the new fw was supposed to fix the touch issues?
I also have the z1 which i still have and is perfect. ive recently updated to 4.4.2 on that and all my issues are fine on there.
my z2 is acting very strange, if i leave it alone for a while sometimes i will go on it and everything on the screen will be frozen, i can't tap anything, i have to press the power button and then swipe to open it again, it is then fine after that.
also i have noticed, and i think its happening a lot when my tablet is a little angled using the case, the screen will be a bit jittery, where as my z1 is really smooth, and i also sometimes have to really tap icons a few times before they register.
i play clash of clans a lot and its been a bit difficult to play as troops aren't selecting as i am tapping on them.
has anyone got any advice?
I have done a factory reset to see if that would fix any issues from the fw update but its still exactly the same.
Thanks
James
anyone?
james_lpool said:
anyone?
Click to expand...
Click to collapse
I installed the new firmware yesterday. While I notice an improvement with the touch problem it's still present. Just install an multitouch app (like this one: https://play.google.com/store/apps/details?id=com.easylabs.multitouch), let your finger trail on the screen and it's definitely obvious (the number on the top right should be the number of fingers touching the screen and it's often not). I tried the same thing on my old Iconia A500 and that's the one thing where it's WAY better than the Z2.
I don't experience anything as strange as you do though, it's mostly usable and I hardly notice it with the new firmware.
I did experience something very strange just BEFORE updating with one specific charger and one specific USB cable , the tablet wouldn't register any touch at all while it's was plugged in. As soon as I unplugged it it would work. The cable was fine with another charger and vice versa;
Weirdest of it all:
This happened while I was testing the output current for each combination of cable/charger and this particular couple was the one giving the "best" results; consistently between 1.1A and 1.2A
I can't reproduce this behaviour with the new firmware. All in all, it's usable for me. Biggest bug would be it not charging while playing power consuming games.
I have found mine goes more weird when it goes to sleep and i then wake it up, the screens sensitivity seems to be terrible, i have topress the off button and then start it again then its fine.
it will then mostly stay fine until the screen times out again then the same thing will happen when i wake it.
James: Same with my 521...
Touchscreen response was REAL BAD after updating to .402, then it went better and better day by day; strange phenomenon.
I also occasionally experience some touchscreen "numbness" after waking up the table with a double-tap, sometimes touch sensitivity suddenly becomes quite low just without any reason; touchscreen has problems detecting touches near the screen corners or doesn't react to touches at all. Solution: Switch to standby, and back on.
At the same time, the Android symbols (Back, Home, last apps) again become difficult to hit.
You can test this by slowly swiping your finger up from the lower bezel towards one of the symbols: If the touchscreen is ok, symbols get highlighted right after your finger reaches the lower edge of the symbol. If the touchscreen malfunctions, you need to move your finger up to the center of the symbols to get them highlighted.
So it smells like a software issue.
Touchscreen problems usually occur two to three times a day of normal use; so I regard it as acceptable - but the problem still isn't fully solved.
I would say it's a hardware issue which Sony attempts to counterbalance with software patches.
Just like on the Nexus7 (2013). There sfhub released a touchscreen fix which made the problem bearable for most users (with some experimenting with different versions of the fix, because each device is different).
I wrote a PM to sfhub asking him whether he could disclose how his fix works so that Z2 Tablet users perhaps could apply a similar, variable, tailor-made fix to their individual device.
No response, unfortunately.
Perhaps some of you could send the same request to him, and perhaps then he reacts?
every now and then, after double tap to wake, the tablet is extremely unresponsive.
I also just sleep/wake up again via power button and it's fine after that.
So my but feeling it's a software issue, not hardware issue.
- Frank
I never had touch problems but after updating to the latest firmware, the tablet is unusable from time to time
what's annoying me is that Sony wont seem to admit that there is an issue, i was talking on their live chat to support and they said that's the first time anyone's mentioned that and isn't on any list of any known issues
Which doesn't fill me with confidence on how quick this may get fixed.
The speed in which is gets fixed may determine if i just send the tablet back to Amazon for a full refund, unfortunately i have bought the Sony case and magnetic charger now as well
I'm just really puzzled what to do, what can i do apart from sent it back if Sony wont even acknowledge they are aware of the problem and will release a fix soon
The only thing is because i have now bought the charger and case, i kinda want to keep it.
It was a direct replacement for my Z1 which i still have, and that is also updated to 4.4.2 now, but that shows no touch issues at all.
What's very interesting and revealing:
When Sony was addressed a few days ago regarding battery problems on Tablet Z and a few phones after the Kitkat update, they immediately reacted!
They readily explained that it is a problem with the Google Play Services running amok and that a fix will come.
But it seems that just because this here is a Sony problem (and not one for which another company can be blamed like in the above one), Sony simply doesn't react at all and obviously orders the service employees to lie and say that they haven't heard at all of a touch problem.
Boooo, Sony, shame on you!
james_lpool said:
what's annoying me is that Sony wont seem to admit that there is an issue, i was talking on their live chat to support and they said that's the first time anyone's mentioned that and isn't on any list of any known issues
Click to expand...
Click to collapse
HAHA ! Exactly the same in Germany. Even after talking about that issue with the SAME person three days in a row, I still was told the problem was totally unknown.
Later, I had a more private talk with one of the support guys. He revealed to me there was an order from Sony to tell callers exactly that.
Ah, as I thought.
This is abysmal behavior by Sony, period.
Also on the Sony support forum, none of the official support staff has replied to any of the topics about touch screen issues. It seems they are just completely burying their heads in the sand...
FW .402 didnt fix the touch screen issue. It is noticeably better than any FW from before.
Gosh, the touchscreen keep going back to home when i'm in a middle of fb conversatuion.
I was testing with chromecast +youtube: those swibe action to enlarge or fade out afe 99% imprecise...
Really wondering if I can return the item to amazon to fix this problem...
Diomorgan said:
Gosh, the touchscreen keep going back to home when i'm in a middle of fb conversatuion.
I was testing with chromecast +youtube: those swibe action to enlarge or fade out afe 99% imprecise...
Really wondering if I can return the item to amazon to fix this problem...
Click to expand...
Click to collapse
Are you sure you're not just accidentally touching the home button while typing? That happens to me from time to time, which is a downside of having the navigation buttons centered compared to having them in the corner like on pre-4.4 Android tablets. I actually think Google should add a setting to choose if the navigation buttons on tablets are in the left corner, centered, or in the right corner. Having them centered also makes it awkward to reach these buttons when holding the tablet with two hands.
I have an LG G Watch with 5.0.1 since a few days and I tried and sent back an identical LG G watch on 4.4W.1 a while ago and didn't experience it. Basically, I am noticing that after leaving the watch alone lying somewhere (I don't wear it at home) for some time (can't really say how long but at least an hour, I think) the display turns OFF. A single tap and it wakes up and then works "normally" until the next time...
The other G Watch with the older Wear version didn't have this behaviour so is this a feature of the latest Wear version (or possibly an LG-exclusive mod to squeeze even more battery life) or is it maybe an "issue"..?
I am saying this especially because I installed the Slumber app to automatically turn the display OFF while charging but realized that it's easier and more elegantly done by simply choosing the new "Theater mode" in Android Wear 5.0.1 and uninstalled the app. I don't know if what I am seeing is due to having installed Slumber but I really don't think so.
Does anybody know for sure what it is and how it exactly works..?
TIA
I was just about to post about this I think it's a bug though... I don't use a Slumber app or anything, I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Anyone know what the problem is or how to fix it?
philessthanthree said:
I think it's a bug though... I don't use a Slumber app or anything,
Click to expand...
Click to collapse
Just to be clear, I don't use it anymore and uninstalled it just after getting the 5.0.1 update with its Theater mode. My worry was that having had it installed triggered this behaviour but since you get it without ever installing it I can put that to rest.
I want my screen truly to be always on. But it will turn off occasionally and I don't like that!! I definitely did not have this issue on 4.4W.2
Click to expand...
Click to collapse
Have you ever got it while it is on your wrist..?
Reading this I just removed my g-watch and after a few minutes I see that my screen was OFF. Never happen when I have watch on my wrist the last 2 days. Screen alaways ON and turn on with movement OFF. So yes it is a new feature of the last update 5.01.
Same here, it happened twice on the table, and once on my wrist this morning.
Must be something like the ambient mode in Moto 360 that does this. For one moment I thought I accidentally triggered the cinema mode.
I always take my watch off at work and the screen keeps turning off after 30 minutes. I did a full reset in case it was an overhang from the old version but it's still turning off.
So based on all of the above replies it seems it's a feature of the latest Android Wear. I am not calling it a bug because, except for a single reported case from our friend with the Moto 360, it seems to never happen while wearing it, so the logic appears to be "save the battery when not in use".
Just to "investigate" it some more, I am trying to time it and confirm it's 30 minutes for me too like StuBFrost says, and may you all please confirm you have Ambient turned ON (i.e. the display is always ON) and state whether you have the new Tilt to wake up setting ON (i.e. the Display lights up from its dimmed state when you tilt your wrist).
My settings are Display always ON and Tilt to wake up OFF.
It would be good to have some more reports from owners of different Wear smartwatches, to this end I posted also in the general Android Wear forum but no replies so far. I am going to update that post with our findings and see if we can understand what exactly is this behaviour we are seeing...
Actually, I think it might be a good feature to keep ON in many cases but it absolutely should be an *option*!
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
StuBFrost said:
I have both options switched on and both work fine except for this new stupid sleep mode that quite clearly hasn't been thought out properly. Surely the theatre mode allows people to turn the display off should they need to and for everythimg else it should do what it did before and stay on.. If it doesn't get "corrected" soon, I will be rooting my watch and putting a custom ROM on it.
Click to expand...
Click to collapse
Trying to time it, I think I can say (I am still trying to cover all of the different scenarios) that any event which normally wakes the display up to normal brightness (i.e. an incoming call) resets the countdown. BTW, I think you are right and it's 30 minutes off the wirst with no movement, no tapping on it and no event like the ones just mentioned. "Normal" incoming notifications don't seem to reset the countdown.
Like I said, I don't think it's a bad idea in and of itself (I would use it in most cases) but they should have made it an option! And, ideally, they would let us set the time after which the display turns itself off.
I use and *strongly* prefer Android instead of limited and dumbed down Windows Phone and even worse Apple's useless crap exactly because of its customizability and powerfulness...
"Funny" thing is that from further testing, this feature doesn't kick in while on the charger (which could actually be pretty useful for most people...) LOL
ADDENDUM: the kind of events which resets the countdown to this "deep sleep" state (i.e. an incoming call) also wakes the display up from "deep sleep".
I am running the LG G Watch, version 5.0.1 with accompanying Android Wear app on my phone version 1.0.5
Screen is set to ALWAYS ON.
Tilt to wake is OFF.
It happens BOTH on my wrist and off my wrist. The timing is variable from my limited observation, but I haven't tried to directly time it.
on my lg g watch too
may I ask something related? on mine, it happened to be able to stop display (full black) with a swype from bottom to the top, never been able to do it again. Anybody faced that?
My heart sensor and the pedometer and the light sensor stop working all together after sometime. Even the auto screen brightness stops working. But all apps and phone calls work. I am using Sprint and my gear is paired with my Note II. Can anyone help on this I hate having to reboot the watch ever time I want to take my heart rate. And auto screen brightness stops working.
From the dial screen, type *#0*#, you will get to the hardware diagnostic screen for the gear S, select sensors, run the test for those sensors you have an issue with. You may also try *#7353# to execute some self test.
All the sensors are unresponsive with the test codes you give me. If I reboot the watch and do the codes again it works fine. Seems to freeze after I receive a notification. Seems to be a software problem. I just wanted to know if anyone else is having this problem.
At least yours works with a reboot. I have been using mine since I bought it from best buy in early March. Yesterday I noticed during a trail run that my screen would not wake and my steps were not being counted. I rebooted several times and did a full reset of the device. Luckily Best Buy honored the 1 year warranty and let me exchange. I'm really concerned about this happening because I just got it a couple months ago and had hardware problems without ever mishandling my watch. I sure hope I don't have to constantly exchange it every few months.
I have the same problem since the last software update. I have bought my Gs directly from a Samsung store. You resolved your issue?
I haven't run across this issue since exchanging it. However I had two additional exchanges since then due to screen flickering and another time my screen started going black.
Hey xda-community,
i've registered, because i have a strange problem with my LG G5 (H850) European Edition. If this is of any use, it's the Vodafone-Edition. Sorry for my language, i'm not a native speaker .
I got my G5 yesterday and was really pleased with the build quality (i was afraid, i was about the get some of those flawed devices as seen on the internet) and the raw power of the whole package. At first i didn't notice but then i realized, that the automatic brightness didn't work. Then i noticed, while having a conversation, that the display was'nt turned down. Up to this point it sounds like the known bug.
What i think (and please, push me into the right direction if i'm wrong - i'd love to take the shame not beeing able to look properly) makes the difference is, that after installing several sensor test apps from playstore, i always got the information, that both sensors are missing.
I took a trip into service menu and tried to calibrate (or better so say, to see if there was any sign of them) those sensors, but nothing happened. No reaction while covering the area where they are supposed to be, nothing.
Firmware is v10c-262-02. Tried to reset the phone and check while having nothing installed - same problem. I tried safe mode - same problem. I can check autobrightness but it doesn't have any effect whatsoever.
What really makes me shake my head is, that when i'm called and i turn the the display downwards to stop the sound, it works after 2 up to 3 times trying to cover the display.
I'd hate to send it in - maybe i'm just too stupid to look for answers, i'd really appreciate any efforts to help.
Thanks in advance and have a nice day.
Nero
Hey there,
short follow up to the problem. Yesterday evening i got a notification about an firmware update and wanted to install it. After hitting the proceed button nothing happened. Nothing. No installation, nada. I shook my head, deceided to return the damn brick and forgot about it. After an hour i noticed that my soft keys had changed their appearance. They got smaller. I asumed a kind of silent update (? nothing is shocking me anymore concerning this phone), checked the brightness control - no change. An hour ago i wanted to unlock my phone and got no reaction. I was about to hard reset it when it unlocked. I scrolled down the notification bar to check something when i noticed that the brightness was different from my setting. I hit the auto brightness button and bazinga. It changed by itself and since then everything works like a charme. The firmware version hasn't changed. I don't have the knowledge to explain anything or to know if something like this is even possibe (something was definitly new because all those vodafone apps where there again - which i deinstalled yesterday). Okay, long story short - either i'm officially going insane or they fixed it. Don't know, don't care.
Have a nice weekend!
Update: And it's gone again. I have no idea what to do anymore. I don't know if anyone is interessted in this, but i share the info anyway...
With Sensors (Umgebungslichtstärkesensor = Ambient light sensor, Näherungssensor = Proximity Sensor)
fs5.directupload.net/images/160508/459jqzhk.png
Without Sensors
fs5.directupload.net/images/160508/wiazcglk.png
nero
It certainly sounds like it *might* be defective, as you say that you have tried a factory reset.
It is a strange problem you have as it only appears to happen occasionally. It also sounds quite annoying. I know it is a pain to have t return it, but it might be better to do that and have a fully functional device, than to keep on facing this problem.
Sorry not to be able to give you a more satisfactory solution.
Good luck.
nobnut said:
Good luck.
Click to expand...
Click to collapse
Hello,
thank your very much for your reply. I agree, i think it'll be the only option i have. I'll try to do return it, it's quite easy in Germany but, nevertheless, connected to some time without a phone.
Have a nice sunday,
Nero
I have this same issue with the proximity sensor and in my case it is because of the Lifeproof case is causing this, many others with this case report the same thing. Try taking out of the case and test again - mine works fine with no case; If this still happens, with no case on, then maybe the phone
jrhlaser said:
I have this same issue with the proximity sensor and in my case it is because of the Lifeproof case is causing this, many others with this case report the same thing. Try taking out of the case and test again - mine works fine with no case; If this still happens, with no case on, then maybe the phone
Click to expand...
Click to collapse
Thank you for trying to help Sensor was damaged, send it in for repair and got it back. One can be sure that it's not a matter of blocked access to the sensors when a sensor test shows, that there are no sensors.
Told about this in so many forums that i forgot to tighten the loose ends. Sorry.
Kind regards