Next Android 7 firmware (2.0.3?) update

[domifer]

Thanks futeko!
I will try it, but in case my Q10 Pro bricks, what exactly do you mean by "DISASSEMBLY of the Q10 Pro" ? I know it means opening the box, but are you going to post detailed operations list of what exactly has to be done to recover it?

[HereIsTom]

So still no AudioTrack v23 or higher for Kodi 17?   

[futeko.com]

Thanks futeko!
I will try it, but in case my Q10 Pro bricks, what exactly do you mean by "DISASSEMBLY of the Q10 Pro" ? I know it means opening the box, but are you going to post detailed operations list of what exactly has to be done to recover it?

http://www.futeko.com/newforum/index.php?topic=1622.msg14469#msg14469

[futeko.com]

So still no AudioTrack v23 or higher for Kodi 17?   

No. Also no unusual aspect ratio stretched video fix.

These two bugs are the two biggest but both await work from HiSilicon, which evidently hasn't happened in this SDK.

I haven't tested strenuously for all bugs, so those testing it please test for other specific fixes. For instance, I think the subtitle time gap problem has been fixed, but it needs more thorough testing.

[domifer]

Thanks futeko!
I will try it, but in case my Q10 Pro bricks, what exactly do you mean by "DISASSEMBLY of the Q10 Pro" ? I know it means opening the box, but are you going to post detailed operations list of what exactly has to be done to recover it?

http://www.futeko.com/newforum/index.php?topic=1622.msg14469#msg14469

OK, I installed it, and it didn't brick my Q10 Pro , and everything seemed normal after the long setup at the beginning, I started changing my setttings (display, sound, time zone etc) then I logged into my google account to access the Google Store and install some usual apps that I always use with this device, such as Free FTP Server, etc then it started giving me force closes on everything: First Google Store, then the rest.
I rebooted a couple of times, but I am not even able to test audio or video capabilities, because it still force closes on everything, i can start media center but as soon as I access one of my storage drives, it force closes. The most I could do, was to get into a list of video files in one hard drive, but as soon as I tried to start playing any of them, it force closes. So basically the whole Android System seems unstable . I have to go back to 2.0.1 ( I hope I can do that without brickingt it).

[futeko.com]

OK, I installed it, and it didn't brick my Q10 Pro , and everything seemed normal after the long setup at the beginning, I started changing my setttings (display, sound, time zone etc) then I logged into my google account to access the Google Store and install some usual apps that I always use with this device, such as Free FTP Server, etc then it started giving me force closes on everything: First Google Store, then the rest.
I rebooted a couple of times, but I am not even able to test audio or video capabilities, because it still force closes on everything, i can start media center but as soon as I access one of my storage drives, it force closes. The most I could do, was to get into a list of video files in one hard drive, but as soon as I tried to start playing any of them, it force closes. So basically the whole Android System seems unstable . I have to go back to 2.0.1 ( I hope I can do that without brickingt it).

It shouldn't be as unstable as that. We tested it with no forced closes at all.

You can install 2.0.1 the same way as any other Android 7 firmware. Restore button method.

[domifer]

OK, I installed it, and it didn't brick my Q10 Pro , and everything seemed normal after the long setup at the beginning, I started changing my setttings (display, sound, time zone etc) then I logged into my google account to access the Google Store and install some usual apps that I always use with this device, such as Free FTP Server, etc then it started giving me force closes on everything: First Google Store, then the rest.
I rebooted a couple of times, but I am not even able to test audio or video capabilities, because it still force closes on everything, i can start media center but as soon as I access one of my storage drives, it force closes. The most I could do, was to get into a list of video files in one hard drive, but as soon as I tried to start playing any of them, it force closes. So basically the whole Android System seems unstable . I have to go back to 2.0.1 ( I hope I can do that without brickingt it).

It shouldn't be as unstable as that. We tested it with no forced closes at all.

You can install 2.0.1 the same way as any other Android 7 firmware. Restore button method.

UPDATE!

While trying to go back to 2.0.1 I could only achieved a Full wipe and it remained in 2.0.3 , so I tested the media player again and this time it worked. But:

IMPREX engine cannot be switched off! Even If I switch it off, it stayes and I don't like the picture at all.
So It seems  that it becomes unstable if you login into a Google account and use Google Store and start installing store apps.
Anyway I will try to install 2.0.1  back, because even if I manage to get it stable, I really do not like the picture quality with the forced IMPREX engine.

[Eriol]

I haven't tested strenuously for all bugs, so those testing it please test for other specific fixes. For instance, I think the subtitle time gap problem has been fixed, but it needs more thorough testing.

I hope they at least fixed that...

[futeko.com]

IMPREX engine cannot be switched off! Even If I switch it off, it stayes and I don't like the picture at all.
So It seems  that it becomes unstable if you login into a Google account and use Google Store and start installing store apps.
Anyway I will try to install 2.0.1  back, because even if I manage to get it stable, I really do not like the picture quality with the forced IMPREX engine.

I mention that in the opening post.

Imprex is disabled / non-functional in this test firmware. When playing a movie non of the brightness/contrast/etc settings work either.

[domifer]

IMPREX engine cannot be switched off! Even If I switch it off, it stayes and I don't like the picture at all.
So It seems  that it becomes unstable if you login into a Google account and use Google Store and start installing store apps.
Anyway I will try to install 2.0.1  back, because even if I manage to get it stable, I really do not like the picture quality with the forced IMPREX engine.

I mention that in the opening post.

Imprex is disabled / non-functional in this test firmware. When playing a movie non of the brightness/contrast/etc settings work either.

Maybe I didn't understand you well, otherwise I wouldn't have upgraded, not being able to change contrast/brightness etc is a killer for me. The picture quality was simply horrible, colors were washed away, and for me, video and audio quality are at the top of the list of a multimedia player. By the way I managed to go back to 2.0.1 the picture is great again! Only now I finished installing and customizing my Q10 Pro.

[Marvel]

Is it now possible that kodi on the q10pro Dolby atmos exhausted? I have so far 2x q5pro and 2x q10pro I would reluctantly change to the nvidia shield tv. I'm very satisfied with the two options. With the wrapper it is not possible that my philips hue lamps go out at the filmstart. This is very important for my cinema.

friendly greeting

[Pete_Repeat]

I too are disappointed with the change list. No audiotrack, no mention of being able to change default launcher... Hmm. I find my minix u1's play far better for kodi 17. This  was meant to be my main box, and it cost a lot more.. I guess there's no updates yet to when the next firmware will be released and the changes they are changes they are hoping to address?

[ultrasilent]

Did they fix 4k hdr aspect ratio problem at least?

[gesu]

Did they fix 4k hdr aspect ratio problem at least?

No

[ultrasilent]

epic fail and shame on them! 
they should remove 4k hdr sign from this product page till it can play this files properly:

http://www.mehanik99.ru/test/_HDR/_test_crop_UHD_HDR10.rar

 it is lie, we can`t watch hdr movies at this  moment!