First I would like to point that I had these issues since 10.3/.1 leaked days. It makes me more disappointed that these issues are still present on my device with the official 10.3.1 version.
1. Thin transparent line when swiping the Quick Settings. Making the small portion of items in Quick Settings visible on a thin line when Swiping Up or Down the Quick Settings.
2. Proximity & Light Sensors are not working. Both BBVE and real time (E.g. the screen do not dim when making calls, Advanced Interaction do not work.)
3. Flat Shadows/Window Borders
I don't have these issues on the latest 10.2.1 build. I am sure that there is no issues on my Hardware (defects). This problems ONLY OCCURS WHEN RUNNING 10.3
You don't have these...? Well, Lucky You & Congratulations!
Calling the STL100 - 1 Community. Can you please post a Screenshot similar on the first post? It will help me & us to determine if this affects the STL100 - 1 versions or just a device specific issue.
I have an stl100-1 z10 and I got a problem with proximity sensor.
My proximity is not working but the test is successful in the BBVE. Screen doesn't din while calling. Any has any solutions?
Have the same problem with the proximity sensors. Why do people keep assuming that it's been dropped or or hardware failure. IT WORKED 3 DAYS AGO BEFORE UPDATING!!! THE UPGRADE HAD MESSED THINGS UP!!!
He probably means switch it off and then test and then switch it back on. People with Passport have noticed that these type of problems occurred after restoring settings from a different device (e.g. Q10). The solution was to go back to the factory OS and then upgrade to the latest without restoring settings.
He probably means switch it off and then test and then switch it back on.
Correct.
It appears to be only for turning on and off vibrate during (receiving?) a phone call, not as the poster is suggesting for all 'vibrating notifications'. There is a section for 'vibrate only profile'.
Using STL 100-1 here. Have not experienced issues raised here in CB. The battery calibration was fixed in 10.3 leaks and it's doing fine since the last os update.