yashsingh1/xdaforums huggingface dataset:
[Android General] jman0:
If you are talking about this Youtube video: Blackview BV8000 Pro waterproof test/drop test/screen/sound speakers under water/camera (IP68)

why tell a lie? On that video, the guy from techutopia literally says: "A true IP68". That's not what I call "exposing blackview's lie".

He drops the phone inside a bucket full of water, which music player running, and says (several times) that Blackview, even if the phone has IP68 rating, recommends to dry the phone's ports, speaker, etc each time it gets in contact with water. You can notice the music in the video comes distorted from the phone, since the grid over the speaker still has some drops of water on top of it. That's very different from not being IP68.

If that's not the video you were talking about, accept my apologies, but if it is, you said a whole different thing than what is actually said in the video.

---------- Post added at 12:15 PM ---------- Previous post was at 12:12 PM ----------

Looks like that ROM is not meant for Blackview BV8000 Pro, but Samsung Galaxy S5. The install script first checks whether the phone you're using is one of the Galaxy S5 variants, and when it finds it isn't, doesn't let you flash it.

If you're sure the ROM is for BV8000, I can help you remove the check from the install script, but you'd risk bricking the phone.
[Android General] agreo:
[youtube]g7Mg6jXEgc8[/youtube]

Make some research on Google on you'll find other users complaining about it, even on kimovil comments and I got censored on blackview's forum when I posted a thread just asking about this issue, this is not good. Also I wasn't talking about auto brightness adjustment but AAL. Now I'm done, I just wanted to warn you.
[Android General] jman0:
Ok, these are my findings/impressions after a few hours with the phone.. I'll eventually write a review after a week of use:

1) About the root issue. This phone can be rooted. The only thing that happens (and happens all the time on other new phones, too) is that SuperSu can't update the su binary. That doesn't mean the phone is not rooted, just that the su binary you're using is not up to date and may need an update, but not doing so doesn't prevent you from using apps that need root. It's like saying that on Windows you can't write documents with Microsoft Word 2000, just because there are newer versions. None of my root-enabled apps failed. I've already tried Busybox, Greenify, Kernel adiutor, Quick Reboot Pro, Total Commander and Titanium Backup.

About the Busybox issue, if you use Stericson's Busybox, you may get an error when you first try to install, but that's just because, on this phone, you can't install Busybox on the default location it suggests you (/su/xbin). Ok, that's a minor issue, since Busybox can be installed (and will work) on /system/xbin, /system/bin, /su/xbin and even a custom path. I just chose /system/xbin, and it worked like a charm. So Busybox IS working. I know because Titanium Backup needs it and it restored 100+ apps without issues.

I first tried to root using Kingoroot, but, besides not working, it also install a lot of garbage apps, so I went for the traditional method and flashed the latest SuperSu beta zip from TWRP. By the way, after unlocking bootloader, I managed to flash TWRP using fastboot. The only nuisance in that case is that now I get a "your phone has been modified and can't be trusted" message over the Blackview logo on every boot, but that's something I've seen on almost all the phones I've used (Chinese and brand phones like Samsung) when I unlocked the bootloader.

2) The red/pink issue on the stock camera is there, but appears to only happen when the red object is under direct light . Anyway, I tried Open Camera and Snap Camera HDR and both worked well.

3) After flashing the November ROM, I've noticed something others reported on Blackview forums, about the back key not responding. It's not exactly that it doesn't respond, but that it's a bit "tilted" to the right, so it works well if you touch it on the right rather than exactly on the middle. A bit annoying, but it's something I've seen on other phones, Chinese or not. I'll get used to it.

These are just a few things. Everything else seems fine, but, as I said, I'll write a longer and more detailed review later.
[Android General] jman0:
Just one more thing I had forgotten to mention, but I think is very important, since others (at least on Blackview forums) reported this as an issue, and I think it really is a new feature or at least an updated way to use one.

My phone came with an August ROM, but before flashing the latest November version, I decided to test everything. The fingerprint scanner worked like a charm, very very fast.

After flashing the November ROM, the fingerprint scanner looked to have gotten worse, and it seemed like it was only able to detect the tip of my fingers while registering them.

I finally found that, on the August version, I was keeping the fingers parallel to the body of the phone while registering the fingerprints, and it worked, but that doesn't seem to work on the latest version.

On this one, the fingerprints are also instantly detected, but only if I lay them on the sensor with the fingers put perpendicularly to the body of the phone and the sensor itself.

I've tried several times and it works. Then, when unlocking, you can put the finger in any position you want, since it's a 360º fingerprint reader, and the phone will also unlock instantly.
[Android General] jman0:
Two more things, one bad and one good.

The bad one, but this one is due to TWRP, and not the phone. TWRP time calculation is wrong. I don't know if anyone has reported this earlier, but in my case it's 26 minutes back. Every time I reboot to TWRP my time gets screwed, and also automatic time setting on Android. I've had to download an app, called Clock Sync, that can sync with an atomic clock via NTP, and this fixes it. I've set it up to refresh on every boot, so when I come back from TWRP, the time is fixed.

And the good news. The phone can also be rooted from TWRP using Magisk. Just installed 14.0 and it's working fine. I still have to flash the Universal SafetyNet fix module, to see if it lets me pass SafetyNet check, but all root requests worked and the phone seems stable. I had to restore stock boot image first (thankfully I did a backup from TWRP just before setting anything else up) but it's working. And no more annoying "su binaries need to be updated" message, since I don't need SuperSu anymore.
[Android General] anvitiousky:
I think my image is still a bit modified from attempts at rooting with supersu.

I never installed TWRP on the device, only fastboot unlocked, and booted TWRP when needed.

How would I go about restoring everything to real standard image using fastboot? can i flash the stock rom from their "mega" using fastboot?

I also btw get the "your device is untrusted", which I dont care about, I do wonder though, do those who rooted via spflash not get this?
[Android General] jman0:
In order to get the system as it was brand new, the easy way, you should use SP Flash Tool, although I'm not sure whether that would relock your bootloader. If it doesn't, you'll have to lock it again, which is as simple as unlocking, using "fastboot oem lock" this time. But, as it happens when unlocking, you loose all data, so if you flash the stock ROM using SP Flash Tool, relocking the bootloader should be the following step, not to loose your hard set up data again.

To flash stock ROM's via fastboot, you should unzip the ROM file and issue several "fastboot flash" commands, for each partition (.img files). I haven't studied the partitions and .img files in this phone's ROM files, so I can't help you. SP Flash Tool is the best way to go. Look for tutorials on the Blackview fiorums.

If you relock the bootloader with TWRP still installed, your Android will stop booting (it will always boot to TWRP) and you loose all data. I know because I tried today. Usually, it's not a good idea to relock the bootloader and not restore at least the stock recovery. On Xiaomi models, for example, you risk bricking the phone.

I'm not sure if the people who installed TWRP via SP Flash Tool got the security warnings, but I'd bet they did, because, according to Google's directives, rooting also makes the device untrusted and non-certified, since rooting, either with SuperSu or Magisk, modifies the boot partition, something Google considers a security threat.
[Android General] neo9596:
Hi, it's possible to put the speed data in the status bar?

Thanks
[Android General] poganytamas:
I tried that Magisk, but the 14.3 beta version. It is SafetyNet compatible. The only issue it has, that it can not use /dev/block/loop0 device, therefore can not mount /magisk, can not install any modules. Hopefully they will fix it soon.
[Android General] jman0:
That's really good news, since with Magisk 14.0 you can't pass SafetyNet check, at least on BV8000

---------- Post added at 02:36 PM ---------- Previous post was at 02:28 PM ----------

For those who can't use their wired headphones, I followed the advice of a Blackview forum user and, with the help of the included USB Host cable, I managed to connect an old USB sound card I purchased some time ago, for a laptop I'm not using anymore. I connected the device and hooked my headphones, and they worked, even better than the Blackview earphones. The main con is that you can't charge the phone and use them at the same time. You can get a USB sound card like that for less than $1 on Aliexpress Something like this:

https://www.aliexpress.com/item/201...32776869448.html?spm=a2g0s.9042311.0.0.O9M5VC
[Android General] neo9596:
I made a bit bigger 6mm drill with de dremel and can use all the 3,5mm jacks. and I used a dust cover to not enter water when I wash the telephone (that's not necessary but it's look really good).
[Android General] Gazlee:
Blackview bv8000pro screen sensitivity

Hi all. Don't know if I'm on the right thread but do apologize if I'm not. I recently purchased a blackview BV8000 pro and find the screen sensitivity is shocking making it hard to text. The bv6000 had a glove mode but this newer model doesn't. Is there anyway of solving this as I can't cope with it missing out multiple letters when typing!!! Ahhhhh!
[Android General] jman0:
Well, if you're using the BV8000 with gloves on, it won't work properly. On the BV6000, Blackview removed the glove mode in one of the latest upodates, so I guess it wasn't working, either. I use the phone with my bare hands and find the screen sensitivity just fine. No lags,.
[Android General] Pappmann:
Hello,

i rooted my phone with Magisk 14.3 and i want to use my phone with a second user profile for buisness, on the second profile is the Device policy App installed.

I tried several options to hide root for this device policy app on the second user profile without success, root cloak is not available for android 7 yet.

Anyone have an idea to hide root/modified kernel for this google device policy app?
[Android General] Throbin_Wood:
[MENTION=2386505]Alberto96[/MENTION]

Thanks for making this thread and thanks for the tutorials I was up running 30 minutes after getting the bv8000 out of the box.

[MENTION=7816370]serg2327[/MENTION] thanks for the help with root and other mods

Guys this thread is starting to get a bit fragmented

While we wait for a dedicated device forum I’ve made a temporary one >>> here <<< with the same template.

I know it’s a pain to sign up to yet another service but do you think it could be useful?

I can easily add other devices not yet supported by xda
[Android General] jman0:
I finally found a way to get a fully functional audio adapter, even microphone, but not a completely easy one.

I had purchased these on Amazon: https://www.amazon.es/FosPower-Conception-4-Conductor-connecteur-Smartphones/dp/B016E5PEXC

These are quite long, but still wouldn't fit. Someone suggested following the advice on a Youtube video, where a guy enlarges the hole to the 3.5 mm socket with a knife, something I wouldn't recommend, since you will loose warranty, and probably the phone will surely not meet the IP68 standards afterwards.

Yesterday I had an idea, and, using a small precision file, I was able to carefully smooth a bit around the lowest part of the connector, in order to remove the bump that would prevent it from going further into the socket. Well, it worked, and I'm now using the adapter perfectly well.

It's not an ideal solution, and sanding metals takes some time, but I can now use some adapters that I had almost discarded.
[Android General] jman0:
And now, xposed

Last night I installed xposed 88.2 and the GravityBox module to tweak the interface and functions.

It seemed to work, and I was able to tweak things like the number of quick setting tiles per row, double tap to sleep on the status bar, quick opening all the quick settings panel swiping from the right side, etc.

I say that it seemed to work because I was forced to uninstall it, since it apparently broke A2DP. I hooked the phone to my bluetooth speaker, and as soon as I tried to play some music, the phone hanged and then rebooted. Calls over bluetooth worked fine, but music hanged the phone. After just disabling GravityBox, everything went back to normal, so I ended up uninstalling it. Maybe it was just due to a certain tweak I had activated, but I didn't want to test all of them again.

I'm still using xposed, but had to look for modules that had the functions I needed and try them. I still have to find something to be able to change the number of quick setting toggles, or to activate and deactivate wifi and bt with a single tap, but I got almost everything I needed. I'm currently using these modules:

- Amplifly: similar to Greenify, to further tweak battery saving. I still have to test it longer, it's my first time with it

- Lock screen widgets [L-M]: although it says "L-M", it work on N. It lets you add your own widgets to the lock screen. I've used it to add a widget to toggle the flashlight

- NeoPowerMenu: It replaces the stock power menu with a material styled one. You can also edit the options, to add things like rebooting to recovery or bootloader

-Physical button music control: lets you set up volume button long press to skip tracks while playing music with the screen off. In the current version, it also allows the remapping of other button. It seems to be able to detect presses of the SOS button, o I think it could be able to disable it, or at least change its behaviour

- StatusBarSleep: Set up double tap to sleep on the status bar

- VolumeSteps+: Adds volume steps to calls, alarm, music, etc. so you can better control the volume

EDIT:

I have successfully disabled the SOS button, both single and long press, with Physical button music control module, so no more annoying beeps because of accidental presses.
[Android General] anvitiousky:
anyone that has problems with magisk and "permission denied" ? I have detailed it here https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post74602879#post74602879
[Android General] poganytamas:
Same here
[Android General] jman0:
Yes, I have that too. How would that affect us? Superuser works, but maybe Magisk hide won't? I don't know
[Android General] anvitiousky:
as far as i can see, it means that magisk modules wont work.
[Android General] jman0:
Ok, that's why I handn't notice. I'm not using any: just flashed Magisk for superuser
[Android General] mac3001:
Hi

I bought BV8000 a week ago and have problem with battery, it discharges in 2 days of standby and phone doesn't enter deep sleep mode. I contact with seller (Blackview official store), but it seems to me that I talk with bot. Moreover phone restarts itself sometimes.

On official forum I see some people with same problem. Anybody have such problem? Any suggestions what I can do?
[Android General] jman0:
Still no news on the official forum, other than the admin suggesting people should disable duraspeed, in case they had it enabled.

I never used duraspeed and have no reboots, other than the ones I had two days ago, when I installed xposed and Gravitybox, but that was due to Gravitybox, and disappeared when I disabled the module.

I did also have battery drain while idle (10% overnight in 6-7 hours, 5% with battery saving enabled) but it looks like it is more stable now, after a few charging cycles. Tonight it was just 5%, with battery saving disabled.

Are you on latest firmware?
[Android General] mac3001:
I'm on 20170803_20170906-1035 firmware and wireless update says that device is up to date. There is slight better than on first charge cycle, but after one day in standby battery is at 57%. Can you tell if xposed and Gravitybox help?
[Android General] jman0:
Not really. In fact, last night I had to uninstall xposed completely, since the phone became very unstable with it. I saw your post because I came here to tell all of you about the problems I had with xposed installed. Everytime I played a video, either downloaded or online, the phone would appear to be frozen. It would eventually respond in a few saeconds, but sometimes, it would also soft reboot (the UI got restarted). And video playing speed was awful, almost unusable. After uninstalling xposed, eveything went back to normal. We'll have to see if the magisk issues get resolved and then we can try with magisk modules instead on xposed.

Regarding the high battery drain while idle, we'll have to wait for a solution from Blackview, unless someone makes a custom rom which solves it, but I don't know if Blackview realeased the kernel sources, because there will be no custom roms until they do so.

BTW, even if wireless update says there's no new firmware, there is. I had to download and install manually to get the latest update from November 1st. The links and instructions are on the official Blackview forum.
[Android General] mac3001:
Today I've downloaded new firmware through wireless update 20170803_20171114-1146, but it didn't help on battery drain. 5 hours after update 7% loss.
[Android General] alexpu1u:
I searched everywhere, I see that every body has this issue with bv8000 pro, when you use it with a Bluetooth device/headset, it stutters every 2 minutes, connection drops, can't have a decent phone call, asked them on their official forums, they just sayed to update and factory reset, I tried all softwares they posted, updated and factory reset, every time the problem persists, tryed multiple Bluetooth devices, they all stutter on bv8000 pro, but no issues on there phones.

The only way I can stop the stop the stuttering when I use Bluetooth calls, is to keep the phone screen on during the call/or listening to media, otherwise every 2 minutes it stutters.

I guess is some kind of battery saving setting that interfers with the Bluetooth connection.

Still to this day I didn't find a setting/solution for this issue, any help appreciated

http://bbs.blackview.hk/viewtopic.php?f=191&t=333190&p=592795#p592795
[Android General] jman0:
7% in 5 hrs, with which usage? Even if standby, it's quite good. It's 1.4% every hour, so you'd get alomost 72 hrs. standby (3 days). I don't think it's such a high battery usage. This is not a Kindle Paperwhite, which can last up to a month on standby.
[Android General] mac3001:
With absolutely no usage, even without SIM card and it lasts around 2,5 days on battery. I think that this isn't good result. My BV5000 with two hours of GPS usage every day can last 5-7 days on battery.
[Android General] jman0:
You're trying to compare with a cell phone which has a slower and less power consuming processor and higher capacity battery (5000 mAh). That's not comparable.

On the other side, if you need just a GPS and are not going to use a SIM card, why not buy just a GPS, which will surely have better battery life?
[Android General] mac3001:
I don't have nano SIM yet so this is why I don't use this phone. I'm using BV5000 as phone, GPS, some internet and it works 5-7 days. Specification of BV8000 tells 26 days of standby, so I think that real value should be aroound 10 days.

I installed simple system monitor and it shows half of the time cpu is on 2,39GHz or 2,34GHz and it cannot enter deep sleep so it isn't right for sure.
[Android General] serg2327:
Here's to compare my phone bv8000 (mt6757CH)

there are no SIM cards, all modules are disabled .. in this mode, it can work for about 30 days
[Android General] serg2327:
in the Internet was found firmware 0т 20171206 under the flasher

the working capacity of the firmware has been verified but I do not know if it is official

About the changes, no one knows

link {Mod edit: Link to turbobit removed! Oswald Boelcke, Senior Moderator}
[Samsung Galaxy Nexus] dipok300:
Having trouble with DNScrypt

this is what it shows in terminal

someone:/ $ su -c dnscrypt enable

Enabling dnscrypt-proxy...

Sun Aug 6 20:13:08 2017 [INFO] + DNS Security Extensions are supported

Sun Aug 6 20:13:08 2017 [INFO] + Provider supposedly doesn't keep logs

Sun Aug 6 20:13:08 2017 [NOTICE] Starting dnscrypt-proxy 1.9.4

Sun Aug 6 20:13:08 2017 [INFO] Generating a new session key pair

Sun Aug 6 20:13:08 2017 [INFO] Done

Sun Aug 6 20:13:08 2017 [INFO] Server certificate with serial #1502012698 received

Sun Aug 6 20:13:08 2017 [INFO] This certificate is valid

Sun Aug 6 20:13:08 2017 [INFO] Unsupported certificate version: 2.0

Sun Aug 6 20:13:08 2017 [WARNING] Safety margin wider than the certificate validity period

Sun Aug 6 20:13:08 2017 [WARNING] The certificate is not valid for the given safety margin (1502028788-216000 not within [1502012698..1502012698])

Sun Aug 6 20:13:09 2017 [WARNING] This system doesn't provide enough entropy to quickly generate high-quality random numbers

Sun Aug 6 20:13:09 2017 [WARNING] Installing the rng-utils/rng-tools or haveged packages may help.

Sun Aug 6 20:13:09 2017 [WARNING] On virtualized Linux environments, also consider using virtio-rng.

Sun Aug 6 20:13:09 2017 [WARNING] The service will not start until enough entropy has been collected.

Sun Aug 6 20:13:09 2017 [INFO] - [okturtles] does not support DNS Security Extensions

Sun Aug 6 20:13:09 2017 [INFO] + Namecoin domains can be resolved

Sun Aug 6 20:13:09 2017 [INFO] + Provider supposedly doesn't keep logs

Sun Aug 6 20:13:09 2017 [NOTICE] Starting dnscrypt-proxy 1.9.4

Sun Aug 6 20:13:09 2017 [INFO] Generating a new session key pair

Sun Aug 6 20:13:09 2017 [INFO] Done

Sun Aug 6 20:13:10 2017 [INFO] Server certificate with serial '0001' received

Sun Aug 6 20:13:10 2017 [INFO] This certificate is valid

Sun Aug 6 20:13:10 2017 [INFO] Chosen certificate #"something" is valid from [2017-01-25] to [2018-01-25]

Sun Aug 6 20:13:10 2017 [INFO] The key rotation period for this server may exceed the recommended value. This is bad for forward secrecy.

Sun Aug 6 20:13:10 2017 [INFO] Server key fingerprint is "blah blah blah"

Sun Aug 6 20:13:10 2017 [WARNING] This system doesn't provide enough entropy to quickly generate high-quality random numbers

Sun Aug 6 20:13:10 2017 [WARNING] Installing the rng-utils/rng-tools or haveged packages may help.

Sun Aug 6 20:13:10 2017 [WARNING] On virtualized Linux environments, also consider using virtio-rng.

Sun Aug 6 20:13:10 2017 [WARNING] The service will not start until enough entropy has been collected.

Done​

tried every possible solution as a newb

I dont know what to do anymore

If anyone could help it would be much appreciated

Thanks in advance

And plz somebody invite

menhir (https://xdaforums.com/member.php?u=523526) and

qwerty12 (https://xdaforums.com/member.php?u=235313) for me.
[Samsung Galaxy Nexus] dipok300:
I am using cynogenmod 13-(snapshot) on Galaxy nexus (maguro)
[Samsung Galaxy Tab A series Guides, News, & Discus] PJng89:
I have been waited few month for Samsung mid range tablet with 7 or 8 inch

on more that one month ago GSMArena posted this, and last week I try google search T385 found this, maybe a placeholder for new device?
[Samsung Galaxy Tab A series Guides, News, & Discus] afblangley:
I'd like an 8 inch version of the Tab S3...