Aeron wrote:

Why won't you release source codes ? AOSP is open source, and additionnaly, it would benefit the users a lot while lightening the workload for your tech team. No drawbacks for BlackView, a huge amount of advantages for both you and the customer. Refusal indicates something weird going on.

Why isn't there any kind of prioritization for older phones ? You keep releasing new phones while older phones have a lot of bugs. It seems really a bad way to make users come back when they need a new phone while giving a clear impression that you don't give a damn about user experience and only care about selling more and more phones. There is no way you will ever be able to fix all older phones bugs + the newer phones bug without letting the community work on the code.

Why is there absolutely no transparency about planning and delay ? Any company has deadline and should be able to reliably let curstomers know when an update is coming. In my "Oreo" example, there were several contradictory announcement: first, no oreo. 3 weeks later, Oreo. First release date, October (I think, not sure, not gonna use it against you). Then release in june. That is a great lot confusing and gives the impression that nobody has any idea about what they're doing. I'm not asking for 100% public planning (that I know is not possible), but just be reliable when announcing a release date instead of saying "I don't know".

Last note: I'm not complaining about you, "blackview_admin" as a person, not even about your answer themselves. I'm pretty sure you're just following your company policy, and it is that policy that I question. I think it is deeply flawed (based on your answers and updates) if your objective really is consumer satisfaction. Just for your information, I bought my BV8000Pro last year, early July (so not so long after release) and the phone is still sitting in my drawer because I'm really (really really...) disapointing in it. This means unless there is a big change in the way BV customers are dealt with, this is my first and last BV device (and I can't recommend a device that I'm not using). I thing there is nothing good about this situation for BlackView's commercial future.

VADUS wrote:

Dear BlackView Admin,

Is there any estimated time-frame for getting the fixed Oreo release? It is almost the middle of October now, and we have been waiting for it since the beginning of September.

blackview_admin wrote:

1) Source codes can't be released by Blackview. That's because policies regarding out developer/tech team. I can't share more details about that with you, as these are classified. i'm sorry, i hope you'll understand.
2) I know and understand what you are saying... but we don't have unlimited resources. We can't stop focusing on the development of new (and always better) phones. 
3) As stated many times, our internal development roadmaps are very very dynamic. Our deadlines are dynamic. I know that BIG companies have sharp deadlines (..and not always..), but we can't be compared to them at the moment. We will improve and get better. We are not Microsoft.
4) Your disappointment on the Bv8000 pro is a bit excessive in my opinion. I use my BV8000 pro as my primary phone since one year. It isn't perfect, but definitely far from "being unusable" as you state.