kup0 wrote:

Can someone test Sygic!? Does it work? It didn't work on december test built and I need it.

Please also be interested in the me ...

I'm worried about decreased lifetime. Are you sure it is decreased?
After upgrade and factory reset?

I don't think multiwindow feature will be critical, but battery life is a key. N7 has battry usage improvement (oficially).

I'm very active user, so at 22.00 bv6000 has 7-15% usually and I don't want to search for charger at 20:00.

Should I upgrade or better is to wait?

Aftter uptade do 7.0 yesterday phone lost sim selector from top when you are before calling and typing sms

Hi,
I upgraded day before yesterday to android 7.0 and since then my launcher3 is crashing non stop (i installed a google now launcher to replace it). Is that a known issue?

bvbw wrote:

Launcher 3 don't work with N7 for me. I'm searching a other good launcher !
What is Blackview team best suggestion ?

I've the same problem. Now using "google now launcher".

I do not get 7 update until now. How can I do?

I just updated my BV6000 to Android 7.0. After the update, everything when I enter a place with CSL wifi, the phone will keep re-booting. CSL wifi is a kind of anto-connect wifi. How can it be fixed ? Before the update, everything is fine. Can I roll back to Android 6.0 ?

Generally 7 seems working. I think more sensors are reported by system. However, they were not fixed. I didn't report it before, hoping BV known about the issue and will fix it.

First, the magnetic field sensor.



Above is the readout from the sensor. I waved the calibration pattern ant that changed rest values in the same position significantly. There are two bad things:

• every vawing rest values my be different
• there are drops and series of spikes on the Z axis visible also on the X axis

BV6000 can use significant amount of electricity: probably magnetic fields from power lines influence the magnetic field sensor.

Similarly, with Earth magnetic field sensor:



Three times the phone was waived while data were being drawn. Earlier magentic field sensor had been watched and the phone was waived too. Each time the phone had been aligned with the edge of the table - so the orientation was always he same. Readout - did not.

I wander if ability to disable these sensors in system (by the user) wouldn't be good... To avoid bad readouts by programs that could use another metod of setting direction (like GPS position change). It doesn't seem to be fixable by software.

On the other way, the gyroscope could be repaired. Accelerometer might by be recalibrated. There is no such option for the gyroscope. Here are the readouts at rest:



This should not be "Gyrosope" sensor but "Gyroscope uncalibrated". Additionally, the ""Gyroscope uncalibrated" should provide drift data, which, subtracted from the readouot, should give (especially when filtered with low-pass filter) zero. "Gyroscope" should be compensated, showing rest at rest. Now it isn't.

Power consumption has increased by a significant amount.
Wifi usage has decreased a lot, but Bluetooth power usage has gone ballistic
For some reason it's the 20161216 version

Ringtone volume automatically set to vibrate on startup. adjust to say 67% but doesn't hold that, if phone rings it jumps up to max, then back down to 67% setting once ringing stops.
BUG