• 3

U11 如何啟用 DayDream

如題,前幾天去買了套 DayDream 頭盔及遙控器,然後發現 U11 雖然有
Google VR 服務,但卻顯示與 DayDream 不相容。參考下圖:

U11 如何啟用  DayDream

去搜尋了一下,硬体規格是符合 DayDream 基本要求的,似乎 HTC 將之
屏敝掉了而已。 好吧,HTC 也許是為了想推自己的 HTC Link,但問題是 LINK台灣
也不賣啊... 所以還是得想辦法解決。 研究之後,發現似乎只能:

把手機 Root 後修改/system/etc/permissions/handheld_core_hardware.xml
然後加上 <feature name="android.software.vr.mode" />
<feature name="android.hardware.vr.high_performance" />

有人有實做過嗎? 我不是太想 root 手機(現在用 Mac,要 root 我得先去找
一台 PC,然後才能 adb/twrp/supersu.... 實在挺麻煩的)

=======================
8/23 補充:
實際root 並修改配置文件後的確是可行的。DayDream 就在 Play 裡出現了。
2017-08-22 9:44 發佈
文章關鍵字 U11 Daydream
leedashone wrote:
如題,前幾天去買了套...(恕刪)


你從哪裡看到U11支援Daydream的?

正常情況下是不支援的,因為Daydream最基本的要求是AMOLED...U11因為是用IPS LCD光這關就過不去了。

leedashone wrote:
如題,前幾天去買了...(恕刪)

U11無法使用Daydream功能
可參考以下網址
Daydream Ready的手機列表
如二樓所言...
Daydream需要OLED的銀幕才有機會符合規格
clse945111 wrote:
你從哪裡看到U11...(恕刪)


您好,我的認知是 DayDream 是基於 Google VR 的平台,AMOLED 並不是剛性需求。
PS:在頭盔這樣的全遮光(環境亮度為0)環境下,OLED沒什麼條件表現比 LCD好。
而 Google 高性能 VR 的硬体要求,Google 官方文件中寫的是:

7.9.2. Virtual Reality High Performance

Android handheld device implementations MUST identify the support of high performance virtual reality for longer user periods through the android.hardware.vr.high_performance feature flag and meet the following requirements.

Device implementations MUST have at least 2 physical cores.
Device implementations MUST declare android.software.vr.mode feature.
Device implementations MAY provide an exclusive core to the foreground application and MAY support the Process.getExclusiveCores API to return the numbers of the cpu cores that are exclusive to the top foreground application. If exclusive core is supported then the core MUST not allow any other userspace processes to run on it (except device drivers used by the application), but MAY allow some kernel processes to run as necessary.
Device implementations MUST support sustained performance mode.
Device implementations MUST support OpenGL ES 3.2.
Device implementations MUST support Vulkan Hardware Level 0 and SHOULD support Vulkan Hardware Level 1.
Device implementations MUST implement EGL_KHR_mutable_render_buffer and EGL_ANDROID_front_buffer_auto_refresh, EGL_ANDROID_create_native_client_buffer, EGL_KHR_fence_sync and EGL_KHR_wait_sync so that they may be used for Shared Buffer Mode, and expose the extensions in the list of available EGL extensions.
The GPU and display MUST be able to synchronize access to the shared front buffer such that alternating-eye rendering of VR content at 60fps with two render contexts will be displayed with no visible tearing artifacts.
Device implementations MUST implement EGL_IMG_context_priority, and expose the extension in the list of available EGL extensions.
Device implementations MUST implement GL_EXT_multisampled_render_to_texture, GL_OVR_multiview, GL_OVR_multiview2 and GL_OVR_multiview_multisampled_render_to_texture, and expose the extensions in the list of available GL extensions.
Device implementations MUST implement EGL_EXT_protected_content and GL_EXT_protected_textures so that it may be used for Secure Texture Video Playback, and expose the extensions in the list of available EGL and GL extensions.
Device implementations MUST support H.264 decoding at least 3840x2160@30fps-40Mbps (equivalent to 4 instances of 1920x1080@30fps-10Mbps or 2 instances of 1920x1080@60fps-20Mbps).
Device implementations MUST support HEVC and VP9, MUST be capable to decode at least 1920x1080@30fps-10Mbps and SHOULD be capable to decode 3840x2160@30fps-20Mbps (equivalent to 4 instances of 1920x1080@30fps-5Mbps).
The device implementations are STRONGLY RECOMMENDED to support android.hardware.sensor.hifi_sensors feature and MUST meet the gyroscope, accelerometer, and magnetometer related requirements for android.hardware.hifi_sensors.
Device implementations MUST support HardwarePropertiesManager.getDeviceTemperatures API and return accurate values for skin temperature.
The device implementation MUST have an embedded screen, and its resolution MUST be at least be FullHD(1080p) and STRONGLY RECOMMENDED TO BE be QuadHD (1440p) or higher.
The display MUST measure between 4.7" and 6" diagonal.
The display MUST update at least 60 Hz while in VR Mode.
The display latency on Gray-to-Gray, White-to-Black, and Black-to-White switching time MUST be ≤ 3 ms.
The display MUST support a low-persistence mode with ≤5 ms persistence,persistence being defined as the amount of time for which a pixel is emitting light.
Device implementations MUST support Bluetooth 4.2 and Bluetooth LE Data Length Extension section 7.4.3
.

連 AXON 7 那種 82x 的機子都支援了,我相信 U11 不支援的原因只在 Config 上面
(政策),而不在實体性能上面。

leedashone wrote:
去搜尋了一下,硬体規格是符合 DayDream 基本要求的,似乎 HTC 將之
屏敝掉了而已。...(恕刪)


雖然我不會寫程式...
不過這問題怎麼看都應該是DayDream擋U11,不是HTC擋DayDream吧

BESCHWA wrote:
雖然我不會寫程式....(恕刪)


嗯嗯,其實我不介意是誰擋誰啦,我只是在找一個可行的 VR 方案。
個人挺喜歡 HTC LINK 的,但他在日本只搭 AU 賣, 如果能上 Amazon.jp
的話我還可以簡單的買回來...

而 CardBoard 平台太輕量了一點,所以找才會退而求其次想用 DayDream 平台。
明天再看看了,沒人弄過的話就只好自己下海了。
leedashone wrote:
您好,我的認知是 D...(恕刪)


Axon 7可以用的原因是硬體820已經夠強,再加上螢幕是 AMOLED.

LCD 沒有理由比 AMOLED 差是絕對的,我個人也是喜歡LCD 多於 AMOLED,可是 Google在這方面的要求就是LCD 因為每秒更新率比 AMOLED 來的低才只支援後者。

由於這件事情是 Google擋U11比U11擋daydream 可能性更高,可以試試root 之後把手機的 id改成有daydream support 的手機試試,像是 pixel之類的...不保證可以用就是了
加那兩行代碼是不難,不過沒有DayDream來測試。
希望你修改測試後OK
leedashone wrote:
您好,我的認知是 D...(恕刪)

有一點你沒有考慮到,那就是畫面更新率,amoled 的畫面更新率可以到達90貞,可以讓畫面更流暢,應該是這樣吧!

leedashone wrote:
您好,我的認知是 DayDream...(恕刪)


The display MUST update at least 60 Hz while in VR Mode.
The display latency on Gray-to-Gray, White-to-Black, and Black-to-White switching time MUST be ≤ 3 ms.
The display MUST support a low-persistence mode with ≤5 ms persistence,persistence being defined as the amount of time for which a pixel is emitting light.
這三點是現階段LCD無法符合Daydream規格需求的主因
會這樣要求是有原因的
主要是要降低暈眩感
當然...
如果硬是從底層去修改程式
讓Daydream可以執行
那確定是可行的
之前S8剛上市的時候
只支援三星VR
也是有網友修改出可讓S8執行的Daydream版本
直到最近才正式支援新聞連結
  • 3
內文搜尋
X
評分
評分
複製連結
Mobile01提醒您
您目前瀏覽的是行動版網頁
是否切換到電腦版網頁呢?