BV9900Pro Shuts down Everyday

Bugstir · Fri Sep 11, 2020 8:21 pm

I have a new BV9900 Pro that seems to be shutting down 4-5 times each day.

I saw on a forum approx 3 years ago Blackview was having issues with that.....Any soultions?

Sat Sep 12, 2020 7:59 am

Bugstir wrote:
I have a new BV9900 Pro that seems to be shutting down 4-5 times each day.

I saw on a forum approx 3 years ago Blackview was having issues with that.....Any soultions?

Hello, Is it shut down automatically?

Mariusbei · Tue Sep 15, 2020 6:02 am

he phone also shuts down for me.
i am very disappointed on the phone
Android 10
BV9900Pro_EEA_S900AA_V1.0_20200817V05

Tue Sep 15, 2020 7:47 am

Bugstir wrote:
Yes it would shut down automatically.

UPDATE 09/13/2020 @ 12:30pm est :
1. I performed a factory reset and only had the native APPS installed on the phone. The phone has been ON for over 24hrs without shutting down.
2. I slowly installed aftermarket APPS about 5 at a time and restarted the phone each time.
3. I let the phone sit powered on for every 5 APPS installed. Trying the see if an APP was causing the shut off issue.
4. I currently have over 75 APPS installed with NO ISSUES at all....

I believe in my experience this is what caused my shut down issues :

1. I received my Blackview BV9900Pro
2. With my current Android/Google account, I RESTORED all my APPS and settings from a backup I had done before with my Samsung Galaxy 8 Active.
3. After this was complete with no errors, this is when I started having the shut down issues each day.
4. I believe my backup that I restored to the Blackview, installed data, settings, configurations that may have NOT been compatible with the Blackview

Finally, With a clean Factory Reset, with Directly installed APPS...I currently have NO ISSUES with the Blackview BV9900Pro. There was a reason I bought this phone and I am happy that I bought it instead of another brand.

Tue Sep 15, 2020 7:49 am

Mariusbei wrote:
he phone also shuts down for me.
i am very disappointed on the phone
Android 10
BV9900Pro_EEA_S900AA_V1.0_20200817V05

Hello, We don't suggest that update the phone to android 10, because the software is not stable right now after some users updated it and feedback some questions to us, our engineer is checking.
Please keep your phone on android 9.

Tue Sep 15, 2020 7:54 am

Maximusgsx wrote:
Where is admin?
It is important.
Regards.

Good day. What can I do for you?

Bugstir · Tue Sep 15, 2020 9:26 am

Even though I did a clean APP install, it has not fixed the problem. Phone still shuts down.

Also, if Android 10 is "un-stable" why was it pre-installed on the this phone?

If there is no fix,,,,we all need to know, so we can send these phones back for a refund

Shawn

Bugstir · Tue Sep 15, 2020 7:53 pm

Below are the log files after a Blackview shut down on it's own. As you can see, it looks like it shut down due to No cell service. I drive through many counties and cell service switches all the time. Maybe an issue in the Android 10 or Blackview software?? Please send to your Engineers. ASAP

--------- beginning of crash
09-15 06:53:10.751 F/libc ( 6916): Fatal signal 31 (SIGSYS), code 1 (SYS_SECCOMP) in tid 6916 (dmesg), pid 6916 (dmesg)
09-15 06:53:10.783 F/DEBUG ( 6920): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-15 06:53:10.783 F/DEBUG ( 6920): Build fingerprint: 'Blackview/BV9900Pro_EEA/BV9900Pro:10/QP1A.190711.020/1575266475:user/release-keys'
09-15 06:53:10.783 F/DEBUG ( 6920): Revision: '0'
09-15 06:53:10.784 F/DEBUG ( 6920): ABI: 'arm64'
09-15 06:53:10.784 F/DEBUG ( 6920): Timestamp: 2020-09-15 06:53:10-0400
09-15 06:53:10.784 F/DEBUG ( 6920): pid: 6916, tid: 6916, name: dmesg >>> dmesg <<<
09-15 06:53:10.784 F/DEBUG ( 6920): uid: 10209
09-15 06:53:10.784 F/DEBUG ( 6920): signal 31 (SIGSYS), code 1 (SYS_SECCOMP), fault addr --------
09-15 06:53:10.784 F/DEBUG ( 6920): Cause: seccomp prevented call to disallowed arm64 system call 116
09-15 06:53:10.784 F/DEBUG ( 6920): x0 <private info omitted>a x1 <private info omitted>0 x2 <private info omitted>0 x3 <private info omitted>0
09-15 06:53:10.784 F/DEBUG ( 6920): x4 <private info omitted>1 x5 <private info omitted>0 x6 <private info omitted>0 x7 00000000001f0000
09-15 06:53:10.784 F/DEBUG ( 6920): x8 <private info omitted>4 x9 <private info omitted>0 x10 0000007fd1d729f0 x11 0000007fd1d72a28
09-15 06:53:10.784 F/DEBUG ( 6920): x12 0000007fd1d72a70 x13 00000070c440a010 x14 <private info omitted>0 x15 00e8000000000000
09-15 06:53:10.784 F/DEBUG ( 6920): x16 0000005eb50a2ed8 x17 00000070c4d011c0 x18 00000070c5f64000 x19 0000005eb50a8000
09-15 06:53:10.784 F/DEBUG ( 6920): x20 <private info omitted>0 x21 00000070c51f6020 x22 0000005eb50a8028 x23 0000005eb50a5000
09-15 06:53:10.784 F/DEBUG ( 6920): x24 <private info omitted>0 x25 <private info omitted>0 x26 <private info omitted>0 x27 <private info omitted>0
09-15 06:53:10.784 F/DEBUG ( 6920): x28 <private info omitted>0 x29 0000007fd1d74b10
09-15 06:53:10.784 F/DEBUG ( 6920): sp 0000007fd1d72ac0 lr 0000005eb5060550 pc 00000070c4d011c8
09-15 06:53:10.786 F/DEBUG ( 6920):
09-15 06:53:10.786 F/DEBUG ( 6920): backtrace:
09-15 06:53:10.786 F/DEBUG ( 6920): #00 pc 00000000000cd1c8 /apex/com.android.runtime/lib64/bionic/libc.so (klogctl+8) (BuildId: 5a6c251dd7f052103e6e6cbe6a051f8b)
09-15 06:53:10.786 F/DEBUG ( 6920): #01 pc <private info omitted>c /system/bin/toybox (dmesg_main+404) (BuildId: 5b9d354f6dd79389db09e66d59f08b91)
09-15 06:53:10.786 F/DEBUG ( 6920): #02 pc 0000000000030b98 /system/bin/toybox (toy_exec_which+76) (BuildId: 5b9d354f6dd79389db09e66d59f08b91)
09-15 06:53:10.786 F/DEBUG ( 6920): #03 pc 00000000000307ac /system/bin/toybox (toybox_main+44) (BuildId: 5b9d354f6dd79389db09e66d59f08b91)
09-15 06:53:10.786 F/DEBUG ( 6920): #04 pc 0000000000030c70 /system/bin/toybox (main+112) (BuildId: 5b9d354f6dd79389db09e66d59f08b91)
09-15 06:53:10.786 F/DEBUG ( 6920): #05 pc 000000000007d470 /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: 5a6c251dd7f052103e6e6cbe6a051f8b)
09-15 09:55:46.388 F/libc (15778): Fatal signal 31 (SIGSYS), code 1 (SYS_SECCOMP) in tid 15778 (dmesg), pid 15778 (dmesg)
09-15 09:55:46.408 F/DEBUG (15781): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-15 09:55:46.408 F/DEBUG (15781): Build fingerprint: 'Blackview/BV9900Pro_EEA/BV9900Pro:10/QP1A.190711.020/1575266475:user/release-keys'
09-15 09:55:46.408 F/DEBUG (15781): Revision: '0'
09-15 09:55:46.408 F/DEBUG (15781): ABI: 'arm64'
09-15 09:55:46.408 F/DEBUG (15781): Timestamp: 2020-09-15 09:55:46-0400
09-15 09:55:46.408 F/DEBUG (15781): pid: 15778, tid: 15778, name: dmesg >>> dmesg <<<
09-15 09:55:46.408 F/DEBUG (15781): uid: 10209
09-15 09:55:46.408 F/DEBUG (15781): signal 31 (SIGSYS), code 1 (SYS_SECCOMP), fault addr --------
09-15 09:55:46.408 F/DEBUG (15781): Cause: seccomp prevented call to disallowed arm64 system call 116
09-15 09:55:46.408 F/DEBUG (15781): x0 <private info omitted>a x1 <private info omitted>0 x2 <private info omitted>0 x3 <private info omitted>0
09-15 09:55:46.408 F/DEBUG (15781): x4 <private info omitted>1 x5 <private info omitted>0 x6 <private info omitted>0 x7 00000000001f0000
09-15 09:55:46.408 F/DEBUG (15781): x8 <private info omitted>4 x9 <private info omitted>0 x10 0000007fc8888770 x11 0000007fc88887a8
09-15 09:55:46.408 F/DEBUG (15781): x12 0000007fc88887f0 x13 0000007bcf20a010 x14 <private info omitted>0 x15 00e8000000000000
09-15 09:55:46.408 F/DEBUG (15781): x16 0000006013dd8ed8 x17 0000007bcfe751c0 x18 0000007bd10ac000 x19 0000006013dde000
09-15 09:55:46.408 F/DEBUG (15781): x20 <private info omitted>0 x21 0000007bd0145020 x22 0000006013dde028 x23 0000006013ddb000
09-15 09:55:46.408 F/DEBUG (15781): x24 <private info omitted>0 x25 <private info omitted>0 x26 <private info omitted>0 x27 <private info omitted>0
09-15 09:55:46.408 F/DEBUG (15781): x28 <private info omitted>0 x29 0000007fc888a890
09-15 09:55:46.408 F/DEBUG (15781): sp 0000007fc8888840 lr 0000006013d96550 pc 0000007bcfe751c8
09-15 09:55:46.415 F/DEBUG (15781):
09-15 09:55:46.415 F/DEBUG (15781): backtrace:
09-15 09:55:46.415 F/DEBUG (15781): #00 pc 00000000000cd1c8 /apex/com.android.runtime/lib64/bionic/libc.so (klogctl+8) (BuildId: 5a6c251dd7f052103e6e6cbe6a051f8b)
09-15 09:55:46.415 F/DEBUG (15781): #01 pc <private info omitted>c /system/bin/toybox (dmesg_main+404) (BuildId: 5b9d354f6dd79389db09e66d59f08b91)
09-15 09:55:46.415 F/DEBUG (15781): #02 pc 0000000000030b98 /system/bin/toybox (toy_exec_which+76) (BuildId: 5b9d354f6dd79389db09e66d59f08b91)
09-15 09:55:46.415 F/DEBUG (15781): #03 pc 00000000000307ac /system/bin/toybox (toybox_main+44) (BuildId: 5b9d354f6dd79389db09e66d59f08b91)
09-15 09:55:46.415 F/DEBUG (15781): #04 pc 0000000000030c70 /system/bin/toybox (main+112) (BuildId: 5b9d354f6dd79389db09e66d59f08b91)
09-15 09:55:46.415 F/DEBUG (15781): #05 pc 000000000007d470 /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: 5a6c251dd7f052103e6e6cbe6a051f8b)
--------- beginning of main
09-15 15:45:59.671 V/PhoneWindow(21028): DecorView setVisiblity: visibility = 0, Parent = android.view.ViewRootImpl@446ca7d, this = DecorView@d847d72[FragmentMainActivity]
09-15 15:45:59.687 D/Surface (21028): Surface::connect(this=0x733a529000,api=1)
09-15 15:45:59.688 D/Surface (21028): Surface::setBufferCount(this=0x733a529000,bufferCount=3)
09-15 15:45:59.688 D/Surface (21028): Surface::allocateBuffers(this=0x733a529000)
09-15 15:46:02.812 V/SysLog (21028): Path: /data/user/0/com.tortel.syslog/cache/logs/2020-09-15_15.46/
09-15 15:46:02.820 V/SysLog (21028): Done grabbing logs
09-15 15:46:02.838 W/m.tortel.syslo(21028): Reducing the number of considered missed Gc histogram windows from 367 to 100

eli2525 · Mon Sep 21, 2020 12:48 am

I been trying to return my phone because of the same issue, it came with Android 10 from the factory but I have the same situation. Where is the admin? Is this page legit? Does this company stand for their products? I feel like I made a mistake buying this phone.

Mon Sep 21, 2020 6:51 am

eli2525 wrote:
I been trying to return my phone because of the same issue, it came with Android 10 from the factory but I have the same situation. Where is the admin? Is this page legit? Does this company stand for their products? I feel like I made a mistake buying this phone.

Sorry for this inconvenience caused to you, about the Android 10 problems, the engineer is checking it, and here is something wrong, so at present, we don't suggest to update it again. Please wait for our news.

BV9900Pro Shuts down Everyday

BV9900Pro Shuts down Everyday

Re: BV9900Pro Shuts down Everyday

Re: BV9900Pro Shuts down Everyday

Re: BV9900Pro Shuts down Everyday

Re: BV9900Pro Shuts down Everyday

Re: Where is Administration bbs.blackview.hk?

Re: BV9900Pro Shuts down Everyday

Re: BV9900Pro Shuts down Everyday

Re: BV9900Pro Shuts down Everyday

Re: BV9900Pro Shuts down Everyday

Who is online