U9-H-CE FW001 Android 7.1.2 20191120 [Community Edition Nougat Firmware]

good morning guys .... I installed the "official" version ...... I repeat these can be my problems ..... but if I want to go back to the factory version of some apps ... you can't do it .. .. I do not find a landscape option for many streaming apps ... if one is sitting on a sofa ... one does not necessarily have to raise to take off eternet cable .... the optimal use is not that ...... then I repeat ... app settings often crashes ... I am not at ease ..... android 6 kept me on the couch ... like it should be .....
 
@fabzilla
Hi. Good morning. If it works better for you stay then with android 6.
For me and for the apps that i use is working good and this ROM is stable.

I made downgrades myself because was working better.
I have a old smartphone and i have installed the first of three firmwares because it also works better for me.

One disavantage is that apps need a particular android version to work and you may have to update (in the future) because that apps you need don't work anymore.

Example:
kodi v17 and later requires that android devices runs at least Android 5.0 and later.
 
Last edited:
@gufone & @KAR .....

Hey guys,

I know you've worked very hard on this for the community for some time now :). Well done. Hopefully the majority will be happy with it :).

I flashed my beta U9-H for test the new CE FW001 ROM today but something has changed with HDMI/display compatability with AVR's unfortunately.

Connected through my AVR I can't get a reliable display. After the display eventually connected I appeared to be able to use the device as normal but I had to restart the device & I haven't got the display back via the AVR since then. (Previous/BETA CE ROM's
worked absolutely fine connected through my AVR for both the visual & audio components without any problems at all.
Obviously something wasn't changed for the better for this final ROM in that regard & this is a completely new problem I haven't experienced before!!!)

If I direct connect to my TV, then the display works fine & it kicks in normally straight away :). It's really weird, I've never seen anything like this before or with the beta CE ROMs!! I've tried hot swapping & other usual tricks too without any luck so far :(

( @pusb87 . Any chance you can try this new ROM through your AVR to confirm if it's universal or not please? (I've tried "hot" disconnecting/reconnecting the HDMI like we did with the X39 but that old trick isn't working in this instance.))
 
Last edited:
@ArcticWolf Hi.
Yes . if @pusb87 can test AVR or other user that we know if the problem remains.

One user had problems (sound) with tv connected to minix by HDMI (default output device) but only for now one user (@Datore).

I edited my post because i wrote wrong but i was thinking right ☺
 
Last edited:
Last edited:
( @pusb87 . Any chance you can try this new ROM through your AVR to confirm if it's universal or not please? (I've tried "hot" disconnecting/reconnecting the HDMI like we did with the X39 but that old trick isn't working in this instance.))
Don, I installed the new ROM yesterday evening and connected up through my AVR and Im sorry but i dont have any of the video issues you have experienced. o_O
 
Did you try previous beta CE ROM ? And With AVR? I don't remember if you tried ☺

If was working for you previous Beta CE ROM it is easier to fix.

I edited my previous post.


(Previous/BETA CE ROM's
worked absolutely fine connected through my AVR for both the visual & audio components without any problems at all.
Obviously something wasn't changed for the better for this final ROM in that regard & this is a completely new problem I haven't experienced before!!!)

If I direct connect to my TV, then the display works fine & it kicks in normally straight away :). It's really weird, I've never seen anything like this before or with the beta CE ROMs!!

Rui please, I mean no disrespect, but if you're going to direct everything that every one else posts on the forums, at least actually read what they're posting beforehand!!! Otherwise, these continual "double posts" or additional posts just causes unnecessary clutter, & in some cases, unnecessary confusion!!

Forum members can read this information for themselves without the need for an additional summary & the required information was already there in my original post :).

So, let's just leave it at that OK :). I've already tagged those I needed the information to get to. Until @gufone or @KAR have any input on the matter, there's really nothing more to be said unless you can try your device with an AVR or actually possess the information to rectify this situation.

Don, I installed the new ROM yesterday evening and connected up through my AVR and Im sorry but i dont have any of the video issues you have experienced. o_O

Thanks for the confirmation Dave. Glad yours is all working fine :). (It actually took me by surprise, the previous beta's/RC didn't have this issue at all. It's almost acting like a beta X39!!)

We'll just have to hope that it's a small number of AVR's that are affected or it's something I've maybe not done correctly!!!!??????

-----xxx-----

I've tried re-flashing 3 times, no change. It wasn't a bad flash & the direct to TV connection is of course still there, & the device then works fine.

One thing that others can correct me on in case I've caused this issue!!.... When @gufone specifically says in the installation instructions "do a clean install & clear the cache before & after"..... Obviously, I'm flashing using the established procedure with the USB Burning Tool, (I'm using the default
USB Burning Tool options & I also tried the "wipe all" option as well, still no change). I'm also clearing the cache from the U9-H's "recovery menu" before & after installation. Should I be clearing the cache by another method elsewhere that I am missing please?

Thanks :).
 
Rui please, I mean no disrespect, but if you're going to direct everything that every one else posts on the forums, at least actually read what they're posting beforehand!!! Otherwise, these continual "double posts" or additional posts just causes unnecessary clutter, & in some cases, unnecessary confusion!!

Forum members can read this information for themselves without the need for an additional summary & the required information was already there in my original post :).

So, let's just leave it at that OK :). I've already tagged those I needed the information to get to. Until @gufone or @KAR have any input on the matter, there's really nothing more to be said unless you can try your device with an AVR or actually possess the information to rectify this situation.



Thanks for the confirmation Dave. Glad yours is all working fine :). (It actually took me by surprise, the previous beta's/RC didn't have this issue at all. It's almost acting like a beta X39!!)

We'll just have to hope that it's a small number of AVR's that are affected or it's something I've maybe not done correctly!!!!??????

-----xxx-----

I've tried re-flashing 3 times, no change. It wasn't a bad flash & the direct to TV connection is of course still there, & the device then works fine.

One thing that others can correct me on in case I've caused this issue!!.... When @gufone specifically says in the installation instructions "do a clean install & clear the cache before & after"..... Obviously, I'm flashing using the established procedure with the USB Burning Tool, (I'm using the default
USB Burning Tool options & I also tried the "wipe all" option as well, still no change). I'm also clearing the cache from the U9-H's "recovery menu" before & after installation. Should I be clearing the cache by another method elsewhere that I am missing please?

Thanks :).
Hi ArticWolf.

Weird behavior.

Compared to the RC's and this version not much changed. Pls send me a pr and I'll send you a brand fresh created img to see if it differs..

Kar

Verstuurd vanaf mijn SM-G960F met Tapatalk
 
Hi ArticWolf.

Weird behavior.

Compared to the RC's and this version not much changed. Pls send me a pr and I'll send you a brand fresh created img to see if it differs..

Kar

Verstuurd vanaf mijn SM-G960F met Tapatalk

Thanks dude :).

Yup, very strange this one as it just wasn't present before today. Will PM :).
 
FYI,
I have now flashed and tested these FW:
U9-H-Android7.1-FW001
U9H-CE-1905-B1-1557411873

Same problem with the sound via HDMI as with U9H-CE-191120-FW001-1574239461, but no problem via OPTO or BT.

Then I flashed U9-H-FW008-Android_6.0-20180209 and no problem at all with the sound via HDMI.

So something in 7.* (Nougat) doesn't work with my LG OLED55C7V via any of its HDMI-port.

Anyway, except this problem I really like U9H-CE-191120-FW001

Thank you!

Have been following this for a bit as I have an LG55C9 and recently installed the CE FW001 ROM to try out for you with my setup.

I normally use an AVR but just tried connecting the Minix u9 running CE FW001 directly to the TV using a different HDMI INput.

I had to change the sound output on the LG55C9 to the TV speakers, but apart from that did nothing more and the sound was fine with no loss at all after several hours play.

I suspect that the LG's firmware are slighty different across the two models but not radically so.

I can only suggest that you ensure that the minix and TV audio settings are aligned with each other.


Other than that if all was well on FW008 Android 6 than go back to that unless there is something you specifically need from Android 7.
I dont find i need android 7 at all for the apps i use and on FW008 Android 6 everything is rock solid.
 
Hi. First of al thanks to the community for creating this rom.

I’ve just installed it, and noticed that the navigation in the settings is still nog working properly.. Without an airmouse I’m not able to navigate treu sub-menus.. Is this correct?
 
Hi. First of al thanks to the community for creating this rom.

I’ve just installed it, and noticed that the navigation in the settings is still nog working properly.. Without an airmouse I’m not able to navigate treu sub-menus.. Is this correct?
Yes, unfortunately not all settings menus will work without an airmouse :(
 
So we can still call it beta
No. It is a stable version but not final.
One example you have is gmail that was many time in beta phase and now it is stable.

One app or ROM could always be improved but it depends on many factors, development, etc....

Another example is one particular app could even disappear or replaced by another....
 
Back
Top