[newbiee]

Mine is back to light and prox issue, I think the files in the dev sensor used by apps to access particular sensor. You can try using BBVE which should show not supoorted message for the missing files.

[Arunv]

This is really annoying not able to figure out how to get this back to work... please someone find a way

Posted via CB10

[brunolovesbrit]

Hoping the rumors about 10.2.1 being released on January 28th are true.

Posted via CB10

[eldricho]

Still no clue as to why this happens
Guess my friend got lucky, cause after I updated to .1925 the problem hasn't returned (knock on wood)

Posted via CB10

[fishpot]

Forgive me if I'm a bit off the topic, but does anyone know if this also affects the shortcut for phone, search and camera shortcuts at the bottom of the live app screen?


Posted via CB10

[mak2xt]

I have some problem. I'm used 10.2.0.1791(could be wrong, not remember, full stock os) and first time(~15 January I caught the bug) have this bug only when plug-in headphones, reboot solved this problem. After upgrading to 1925 sometimes reboot don't solved this problem. Now I reboot my Z10 STL100-2 3 times in a row and haven't results :C. I also haven't light/proximity files in /dev/sensor. I specifically did not connected headphones 2 days in a row(20,21 January on 1925) and proximity/light sensors worked fine. Today I used headphones and can't fix this ordinarily. And when you connect headphones (if sensors work), the device begins a long time to wake up (backlight, the panel is lit as usual) and BBVE writes nothing about the sensors, they seem to have, but do not give evidence.

Posted via CB10

[newbiee]

I have some problem. I'm used 10.2.0.1791(could be wrong, not remember, full stock os) and first time(~15 January I caught the bug) have this bug only when plug-in headphones, reboot solved this problem. After upgrading to 1925 sometimes reboot don't solved this problem. Now I reboot my Z10 STL100-2 3 times in a row and haven't results :C. I also haven't light/proximity files in /dev/sensor. I specifically did not connected headphones 2 days in a row(20,21 January on 1925) and proximity/light sensors worked fine. Today I used headphones and can't fix this ordinarily. And when you connect headphones (if sensors work), the device begins a long time to wake up (backlight, the panel is lit as usual) and BBVE writes nothing about the sensors, they seem to have, but do not give evidence.

Posted via CB10

I have exactly same experience.

[brunolovesbrit]

My headphones have always been kinda problematic, when I plug then they skip songs, start the vocal control, etc.
I hope that didn't ruin the sensors :/

Posted via CB10

[mak2xt]

My headphones have always been kinda problematic, when I plug then they skip songs, start the vocal control, etc.
I hope that didn't ruin the sensors :/

Posted via CB10

I'm haven't problems with headphones but my sensors don't work :C. I guess this is software failure occurred a week ago on 10.2, upgrading hasn't brought fix

Posted via CB10

[Javid Gozalov]

My headphones have always been kinda problematic, when I plug then they skip songs, start the vocal control, etc.
I hope that didn't ruin the sensors :/

Posted via CB10

Forever had this with the BB headphones.

Posted via CB10

[brunolovesbrit]

Forever had this with the BB headphones.

Posted via CB10

Which sucks big time!
At this point it's not possible that nobody at BlackBerry knows about it.

The CrackBerry team needs to get in touch with BBRY and do something!!!!!

Posted via CB10

[FF22]

Frankly, if at this point your phone is NOT WORKING PROPERLY, it may be time to investigate repair/replacement. Waiting for an OS upgrade which may or may NOT fix the problem is wishful thinking. Do not let your warranty expire while waiting for potential software/firmware fixes. Use your warranty if you have one.

[heading4tomorrow]

So this problem is present only in Z10? No such a thing with Z30 on same OS versions?

[mak2xt]

Has anyone tried to write in blackberry support/dev support?

Posted via CB10

[newbiee]

I tried direct message to @blackberryhelp and provide my pin to them.
Since I m using the leak OS, this is their reply.
"Sorry for the delay. By checking your PIN we found the software on your device is higher that the supported version from your carrier
This might be the reason why the sensor is not working. Please contact your carrier in order to get the supported version."

[heading4tomorrow]

I tried direct message to @blackberryhelp and provide my pin to them.
Since I m using the leak OS, this is their reply.
"Sorry for the delay. By checking your PIN we found the software on your device is higher that the supported version from your carrier
This might be the reason why the sensor is not working. Please contact your carrier in order to get the supported version."

You guys honestly expected BB to help when you are running a leak?
There is a reason these are not official releases. Reasons like serious bugs and issues.
I would be running a latest available version on my Z10, don't get me wrong but BB won't help.
You guys should use bug report or get on touch with BB engineers and developers who are on BB official boards.
I would ask JSanders to relay any bugs you find. There are few others who have access to BB bug swatters.



Sent from my LG-D800

[Javid Gozalov]

Confirmed fix

Posted via CB10

[heading4tomorrow]

Confirmed fix

Posted via CB10

10.2.1 is what you are already running. I wish you pushed him for in what sub-version/release of 10.2.1 is this fixed?

[Javid Gozalov]

10.2.1 is what you are already running. I wish you pushed him for in what sub-version/release of 10.2.1 is this fixed?

Unfortunately I'm not the no one having the conversation. But it's fairly new. My name is not Ben

I recon they did something on the official version, small change(s)?

Posted via CB10

[heading4tomorrow]

Unfortunately I'm not the no one having the conversation. But it's fairly new. My name is not Ben

I recon they did something on the official version, small change(s)?

Posted via CB10

So, non of you guys who had proximity sensor issues were able to grab VZ's official release and see if it fixed anything?
I know you are in EU but what about the others with same problems?

[FF22]

Again, if your warranty is close to expiring, do NOT wait for an OS to potentially fix the problem. If it is not the OS, and your warranty expires you will be in deep doodoo!!!

Or download the 1925 Leak and see if it fixes it.

[mak2xt]

You guys honestly expected BB to help when you are running a leak?
There is a reason these are not official releases. Reasons like serious bugs and issues.
I would be running a latest available version on my Z10, don't get me wrong but BB won't help.
You guys should use bug report or get on touch with BB engineers and developers who are on BB official boards.
I would ask JSanders to relay any bugs you find. There are few others who have access to BB bug swatters.



Sent from my LG-D800

But I have this problem when running on 10.2.0.424 offical for my MegaFon Rus operator(еhe problem arose after several months of using this firmware). 10.2.1.1925 leak don't fix this problem

[heading4tomorrow]

But I have this problem when running on 10.2.0.424 offical for my MegaFon Rus operator(еhe problem arose after several months of using this firmware). 10.2.1.1925 leak don't fix this problem

Sorry, you are right, I see older version users had same problem.I wonder what broke the functionality?


Sent from my LG-D800

[FF22]

But I have this problem when running on 10.2.0.424 offical for my MegaFon Rus operator(еhe problem arose after several months of using this firmware). 10.2.1.1925 leak don't fix this problem

Then fix the phone. Call carrier and use your warranty.

[mak2xt]

Sorry, you are right, I see older version users had same problem.I wonder what broke the functionality?


Sent from my LG-D800

I myself wonder, lol

Posted via CB10