NEW - Lollipop - wasser firmware 3.0.6 for Minix Neo X7

[ididid]

Officially ONLY Nexus7 supports HD streaming, according to Netflix themselves
https://help.netflix.com/en/node/237

This is annoying since chromecast stream Netflix content in super HD. And I can understand supporting only specific os version and later, but why support only one specific tablet?

[Phycopat]

This is annoying since chromecast stream Netflix content in super HD. And I can understand supporting only specific os version and later, but why support only one specific tablet?

You could try to spoof device as nexus 7 but I still think you will 480p

[ididid]

You could try to spoof device as nexus 7 but I still think you will 480p

Ok... Thanks
How do I spoof?

[ididid]

You could try to spoof device as nexus 7 but I still think you will 480p

Ok... Thanks
How do I spoof?

[jeroen.wit]

Ok... Thanks
How do I spoof?

Change your build.prop file so that Google Apps store thinks your device is a Nexus 7.
Or install this version of netflix:

http://www.mediafire.com/download/0akdqicniau56uw/netflix2.4.1.bitrate16x.signed.apk

Let me know if its works...

[georget]

I really appreciate all your suggestions, and i don't want to sound rude, but i have no problem configuring routers and whatnot

I am reporting a bug. A bug that more users than me is experiencing. I did it because i hoped that the creator would look into this. I really wish for this kitkat rom to be error-free, for all of us.

I can get by with a workaround, but this may not be very appealing to future users.

Hi Flemming. I could not agree with you more. This KitKat firmware from Wasser is so close to perfect, it is scary. Anything we can do to identify a real issue will benefit others down the road. Of course finding bugs and finding solutions are two different things. Wasser has been amazing at doing both.

Here are the results of my testing...

My first test was to see if the original Minix Jelly bean 4.2.2 firmware would successfully reboot if a Static IP was set. The answer is YES! I rebooted my Minix several times with Ethernet cable connected and Static IP enabled, and it boots up perfectly every time. This was my configuration...

ip address = 192.168.2.118
netmask = 255.255.255.0
gateway = 192.168.2.1
dns = 8.8.8.8
dns = 8.8.4.4

I then flashed Wasser's Kitkat Firmware with Max over clocked kernel from the first page.
"kernel-neox7-cpu1800h-gpu798h-ddr800-1080p.img"
oc-kernels-1.zip

I confirmed that the Minix can boot fine using DHCP with the Ethernet enabled and cable connected.

I then set the Static IP using the same configuration as above. After rebooting the player, it continuously loops through the start up color dots. Nothing I could do would get it to boot up. I needed to re flash firmware.

Hopefully Wasser will be able to identify what is happening when Static IP is selected that is preventing the Minix from booting up. Since most devices using KitKat do not have an ethernet port (smartphones & tablets), it is possible it was never really tested by the OEM.

[Cantenna]

Ok... Thanks
How do I spoof?

Try changing in build.prop (have a Nandroid backup just in case) build.prop edits can lead to boot loop


ro.product.model=Nexus 7
ro.product.brand=Google
ro.product.name=nakasi


I'll try these build.prop edits later with Netflix

[ididid]

Does this ROM support DTS?

[flemming]

Hi Flemming. I could not agree with you more. This KitKat firmware from Wasser is so close to perfect, it is scary. Anything we can do to identify a real issue will benefit others down the road. Of course finding bugs and finding solutions are two different things. Wasser has been amazing at doing both.

Here are the results of my testing...

My first test was to see if the original Minix Jelly bean 4.2.2 firmware would successfully reboot if a Static IP was set. The answer is YES! I rebooted my Minix several times with Ethernet cable connected and Static IP enabled, and it boots up perfectly every time. This was my configuration...

ip address = 192.168.2.118
netmask = 255.255.255.0
gateway = 192.168.2.1
dns = 8.8.8.8
dns = 8.8.4.4

I then flashed Wasser's Kitkat Firmware with Max over clocked kernel from the first page.
"kernel-neox7-cpu1800h-gpu798h-ddr800-1080p.img"
oc-kernels-1.zip

I confirmed that the Minix can boot fine using DHCP with the Ethernet enabled and cable connected.

I then set the Static IP using the same configuration as above. After rebooting the player, it continuously loops through the start up color dots. Nothing I could do would get it to boot up. I needed to re flash firmware.

Hopefully Wasser will be able to identify what is happening when Static IP is selected that is preventing the Minix from booting up. Since most devices using KitKat do not have an ethernet port (smartphones & tablets), it is possible it was never really tested by the OEM.

Gerorget, you are a honey-bunny. Thank you so much for for testing and verifying

We are now 4 users experiencing the same problem. The REAL problem for me, is that each and every time, my X7 has crashed while viewing Netflix... and then endless boot

If just the boot problem with static IP was resolved, i could start to look into the crashing of Netflix afterwards.

[flemming]

Try changing in build.prop (have a Nandroid backup just in case) build.prop edits can lead to boot loop


ro.product.model=Nexus 7
ro.product.brand=Google
ro.product.name=nakasi


I'll try these build.prop edits later with Netflix

I am not sure, but...

- With the right spoofing, the Netflix app would just play HD as is?

or

- With the right spoofing, Google Play market will let you download a special Netflix app for Nexus 7?

Anyone knows anything about this, or can figure out which sounds most correct? I tried a few things myself, but didn't make anything good or extraordinary happen, unfortunately I dream of HD Netflix so much!!!

[astral69]

Does this ROM support DTS?

No
Not yet.
Give the guy a chance and read the whole thread!!!

[flemming]

No
Not yet.
Give the guy a chance and read the whole thread!!!

To be fair, 34 pages is a LOT to read, and it's easy to miss something.

Good practice for such a long thread is for the OP to update the initial post with info on
- What works
- What does NOT work
- Which bugs have been reported
....and so on

That way, a lot of duplicate questions will be avoided, and all important informations is gathered in one single place.

For example on the XDA forums this is mandatory. And they even reserve 2 or 3 posts right of the start of the thread for important stuff. Good practice and discipline!

[Decapper]

To be fair, 34 pages is a LOT to read, and it's easy to miss something.

Good practice for such a long thread is for the OP to update the initial post with info on
- What works
- What does NOT work
- Which bugs have been reported
....and so on

That way, a lot of duplicate questions will be avoided, and all important informations is gathered in one single place.

For example on the XDA forums this is mandatory. And they even reserve 2 or 3 posts right of the start of the thread for important stuff. Good practice and discipline!

Maybe the OP could make me a lovely cup of coffee while he is at it

[flemming]

Maybe the OP could make me a lovely cup of coffee while he is at it

They do that over a XDA also??

[Cantenna]

My practice; please and thank you and alway give the utmost respect to a developer and never critcize the op.
I also think its rude to compare roms to one another i.e. comment one is better than another and I always believed that in all forums its expected that the user will read a thread in its entirety or use the search function to avoid posting a duplicate question that has already been asked before. Anways these are just my practices but I dont think I have ever seen an op post a status list of open/closed bugs on xda.