NEW - Lollipop - wasser firmware 3.0.6 for Minix Neo X7

[Pluto]

Every Vid has the title on the top, inside the vid box. Pressing it (or double pressing it) will seek the external/native player.

[Molle]

Every Vid has the title on the top, inside the vid box. Pressing it (or double pressing it) will seek the external/native player.

The thing is, when I actually go to http://www.youtube.com, I don't see any titles on the videos. Just the frame representing the video and then the textual link below (or beside) it. Clicking either of them starts playback in the browser (and I would like to use the app for all YouTube content).

[Guest]

Hello.

This is patch for enable USB audio and enable USB audio volume control.

Topic: http://forum.xda-developers.com/show...029728&page=36
Link to audio patcher for 4.4.2: http://forum.xda-developers.com/atta...6&d=1388958466
Mirror off my website: http://altijdslimmer.nl/usb-audio-patcher.rar

Also can you please check the settings in

https://android.googlesource.com/platform/system/core.git/+/android-4.4.1_r1/rootdir/init.usb.rc

If this is included in your rom?

• # audio accessory configuration
• on property:sys.usb.config=audio_source
• write /sys/class/android_usb/android0/enable 0
• write /sys/class/android_usb/android0/idVendor 18d1
• write /sys/class/android_usb/android0/idProduct 2d02
• write /sys/class/android_usb/android0/functions ${sys.usb.config}
• write /sys/class/android_usb/android0/enable 1
• setprop sys.usb.state ${sys.usb.config}
• # audio accessory configuration, with adb
• on property:sys.usb.config=audio_source,adb
• write /sys/class/android_usb/android0/enable 0
• write /sys/class/android_usb/android0/idVendor 18d1
• write /sys/class/android_usb/android0/idProduct 2d03
• write /sys/class/android_usb/android0/functions ${sys.usb.config}
• write /sys/class/android_usb/android0/enable 1
• start adbd
• setprop sys.usb.state ${sys.usb.config}
• # USB and audio accessory configuration
• on property:sys.usb.config=accessory,audio_source
• write /sys/class/android_usb/android0/enable 0
• write /sys/class/android_usb/android0/idVendor 18d1
• write /sys/class/android_usb/android0/idProduct 2d04
• write /sys/class/android_usb/android0/functions ${sys.usb.config}
• write /sys/class/android_usb/android0/enable 1
• setprop sys.usb.state ${sys.usb.config}
• # USB and audio accessory configuration, with adb
• on property:sys.usb.config=accessory,audio_source,adb
• write /sys/class/android_usb/android0/enable 0
• write /sys/class/android_usb/android0/idVendor 18d1
• write /sys/class/android_usb/android0/idProduct 2d05
• write /sys/class/android_usb/android0/functions ${sys.usb.config}
• write /sys/class/android_usb/android0/enable 1
• start adbd
• setprop sys.usb.state ${sys.usb.config}

Thank you

[adfurgerson]

How do you watch YouTube videos on YouTube's site with this ROM (or KitKat in general)?

When I click on a YouTube link on e.g. Google, I get a popup for choosing whether to play the clip in the browser or with the YouTube app. If I go to YouTube and click on a video, each browser I have tested starts to play the video within the browser with no option to redirect to the app. Since Flash support is removed from KitKat 4.4, I can't easily just browse YouTube for videos.

This is what works on my phone, haven't tried 4.4 on MINIX ( stoopid Windows 8.1).
Try Dolphin browser with Jetpack addon and this flash apk.

https://app.box.com/s/9rd6bt1qha9s9l6whgab

[Molle]

Try Dolphin browser with Jetpack addon and this flash apk.

Thank you for the suggestion. The hacked player does indeed enable Flash support in Dolphin under KitKat. However, I'd still like some solution on how to enable sending all YouTube videos to the app if I so choose.

[queonda]

Re: KitKat-4.4.2 for Minix X7

Thank you for the suggestion. The hacked player does indeed enable Flash support in Dolphin under KitKat. However, I'd still like some solution on how to enable sending all YouTube videos to the app if I so choose.

Is that just program associations within android under settings applications manage applications?

Sent from my HTC PH39100 using Tapatalk

[Pluto]

The thing is, when I actually go to http://www.youtube.com, I don't see any titles on the videos. Just the frame representing the video and then the textual link below (or beside) it. Clicking either of them starts playback in the browser (and I would like to use the app for all YouTube content).

thats probably the case with the youtube.com homepage, but embedded links have that title which is clickable.

@wasser, besides kernel updates, will the rom be updated? im just curious if there is anything left to be done.

[Molle]

thats probably the case with the youtube.com homepage, but embedded links have that title which is clickable.

I actually managed to find a pretty decent solution. I installed 'Boat Browser for Tablet' and this YouTube app:

http://www.minixforums.com/threads/recommended-youtube-version.2670/

With this combo, Boat Browser presents an "Open in YouTube app" menu item when a YouTube clip/link is long-pressed. I used to have the GoogleTV YouTube app installed but Boat doesn't recognise it as a valid YouTube app.

Boat Browser for Tablet is actually a nice browser in its own right. It allows defaulting to desktop mode and is quite fast. I'm currently using it as my default browser.

[dk0r]

wasser, should we expect to see support for the minix neo a2 remote?

does the neo a2 remote not work in the 0.92? Could you please add more infos ?thanks

Wasser, thanks again for your work on this build.
The following are my findings w/ the Minix Neo A2 Remote:



1.) Mute button does not function.
2.) Switcher button does not function
3.) Menu button does not function
4.) App-drawer button does not function
5.) The volume-up and volume-down buttons only allow the selection of 0%-volume and 100%-volume.
I think this is a known issue w/ the build and may be independent of the remote. Regardless, no intermediary volumes can be selected.

6.) Rewind and Fast-forward do not function in ES Media Player(3.0.91), Hulu+(2.12.2.201519), Video(1.82-20131121-4.4), Video Player (Gallery Version 1.1.400300) and Youtube(5.3.32). However, when using Avia(7.0.27594), rewind and fast-forward both skip to the beginning of a video. When using MX player(1.7.22), only rewind skips to the beginning of a video.

7.) There are two enter buttons on the keyboard. The enter button on the front of the remote functions properly. However, the enter button on the keyboard side of the remote does not. Within certain applications, after placing text into a search field and hitting enter, the characters "mn" are appended to the search. For example, if I input "hermitian operator" into a text field and then hit enter, the application performs a search for "hermitian operatormn".
This issue occurs when performing searches via Chrome(32.0.1700.99), Chrome-Beta(33.0.1750.31), Play Store(4.5.10) and Root Explorer(3.1.6). When searching Youtube(5.3.32), searches are completed correctly, but after the results are displayed, a new search of the "m" character is automatically started.
Please note again that the enter button on the front of the remote always works properly.

8.) The Neo A2 has both an integrated speaker and microphone.
Under the current build there is no speaker or microphone functionality.

Also, not related to the remote are the following:
1. Trying to queue more than one installation in the Playstore(4.5.10) results in the os becoming unresponsive and automatically rebooting.
2. Whatever app is assigned to the rightmost position of the stock launchers dock (aka "hot seat") will disappear after each reboot. Each reboot leaves the rightmost slot empty.
--Perhaps these are isolated to me. Anyone else?

p.s. I'm new here and without merit but would greatly appreciate for the discussion in this thread to remain on topic; i.e. pertaining to issues specific to this rom. I'm confident that those of us subscribed to the thread find it a nuisance to receive email updates about ancillary topics which would be better discussed elsewhere. This will likely only solicit snarky responses and more useless email. Oops.

[danfozzy]

Wasser, thanks again for your work on this build.
The following are my findings w/ the Minix Neo A2 Remote:



1.) Mute button does not function.
2.) Switcher button does not function
3.) Menu button does not function
4.) App-drawer button does not function
5.) The volume-up and volume-down buttons only allow the selection of 0%-volume and 100%-volume.
I think this is a known issue w/ the build and may be independent of the remote. Regardless, no intermediary volumes can be selected.

6.) Rewind and Fast-forward do not function in ES Media Player(3.0.91), Hulu+(2.12.2.201519), Video(1.82-20131121-4.4), Video Player (Gallery Version 1.1.400300) and Youtube(5.3.32). However, when using Avia(7.0.27594), rewind and fast-forward both skip to the beginning of a video. When using MX player(1.7.22), only rewind skips to the beginning of a video.

7.) There are two enter buttons on the keyboard. The enter button on the front of the remote functions properly. However, the enter button on the keyboard side of the remote does not. Within certain applications, after placing text into a search field and hitting enter, the characters "mn" are appended to the search. For example, if I input "hermitian operator" into a text field and then hit enter, the application performs a search for "hermitian operatormn".
This issue occurs when performing searches via Chrome(32.0.1700.99), Chrome-Beta(33.0.1750.31), Play Store(4.5.10) and Root Explorer(3.1.6). When searching Youtube(5.3.32), searches are completed correctly, but after the results are displayed, a new search of the "m" character is automatically started.
Please note again that the enter button on the front of the remote always works properly.

8.) The Neo A2 has both an integrated speaker and microphone.
Under the current build there is no speaker or microphone functionality.

Also, not related to the remote are the following:
1. Trying to queue more than one installation in the Playstore(4.5.10) results in the os becoming unresponsive and automatically rebooting.
2. Whatever app is assigned to the rightmost position of the stock launchers dock (aka "hot seat") will disappear after each reboot. Each reboot leaves the rightmost slot empty.
--Perhaps these are isolated to me. Anyone else?

p.s. I'm new here and without merit but would greatly appreciate for the discussion in this thread to remain on topic; i.e. pertaining to issues specific to this rom. I'm confident that those of us subscribed to the thread find it a nuisance to receive email updates about ancillary topics which would be better discussed elsewhere. This will likely only solicit snarky responses and more useless email. Oops.

Scan codes for these buttons are:

Button 3 on picture (menu button) - 60
Button 2 on picture (multi window) - 240
Button 1 on picture (mute button) - 113
Button 4 on picture (app locker button) - 59

[Guest]

Wasser,

I was searching around for resolutions on the hdmi blocking that some apps have (Showtime). I found out that potentially if we set the following file in /sys/devices/virtual/switch/hdmi/state file value to "0" instead of the default "1" that apps which check hdmi and block output should work. I tried but couldn't change that value using es explorer and I have heard that even if you could change it, it will revert back to "1" on reboot.

So could you cook up a test version with your next round, with this value set to "0" so I can see if that will remove hdmi block, persist reboot, and not break other hdmi functionality? Or if there is a way to provide an option to turn this to 0 or 1 some other way that will persist.

Thanks

[Batfink32]

So I flashed back to 4.2 just go try out the new quickshot ROM.The quality of the video just isnt as good as 4.4.2 with 4.4.2, the video has rich colours and looks great! Is there a reason for this? is there new drivers in 4.4.2 or something?

Sent From My Nexus 7 (2013) Using Tapatalk

[wasser]

Wasser,

I was searching around for resolutions on the hdmi blocking that some apps have (Showtime). I found out that potentially if we set the following file in /sys/devices/virtual/switch/hdmi/state file value to "0" instead of the default "1" that apps which check hdmi and block output should work. I tried but couldn't change that value using es explorer and I have heard that even if you could change it, it will revert back to "1" on reboot.

So could you cook up a test version with your next round, with this value set to "0" so I can see if that will remove hdmi block, persist reboot, and not break other hdmi functionality? Or if there is a way to provide an option to turn this to 0 or 1 some other way that will persist.

Thanks

if you set state to 0 your LCD will be disconnected!

i don't think it's good idea to set it to 0

[dk0r]

If that isn't working then go to play store and download terminal emulator and keyevent display.

With the A2 plugged in go into terminal emulator and type lsusb
It will give you an output. Look at the end of the row at each device and one will be the id for your A2 that corresponds to the kl file I gave you. Is yours the same id?

Next you want to go into keyevent display and click on the buttons that don't work and look at what the scancode is for each of the buttons that don't work. If they are not displaying anything on key press then it will need to be fixed in kernel. If they show scancodes then in can be fixed.

I have the same id as that in your .kl file name (Vendor_0c40_Product_7a18.kl)

$ lsusb
...other devices...
Bus 002 Device 004: ID 0c40:7a18

I also verified that the scan codes for buttons that do not work on my A2 remote match what was entered in the Vendor_0c40_Product_7a18.kl that you supplied.

Additionally, I tried deleting every *.kl in /system/usr/keylayout/ and left only your Vendor_0c40_Product_7a18.kl in the directory. Upon reboot the only buttons that worked were the back button, the select button in the middle of the d-pad (the one w/ the android logo) and the button which enables/disables the air remote. No other buttons worked; not even a single button on the keyboard side of the remote. Upon clicking inside a text field, the on-screen keyboard appeared.

I then deleted the only remaining .kl (/system/usr/keylayout/Vendor_0c40_Product_7a18.kl) and rebooted.
The remote displayed the same non-functional behavior that I've noted above.

I'm not experienced w/ Android but it seems to me that there is some .kl being used which is not associated with the usb device id shown with lsusb.

[wasser]

So that's what it is!? Thanks Molle

Sent from my Nexus 5 using Tapatalk

as i know strick mode is disabled by default in 0.92. COuld you please check it in Settings->Development->Strict mode

thanks