Netflix / Amazon 5.1 on HDMI ARC / Optical - Shield Android TV Original Android Development

Netflix / Amazon 5.1 on HDMI ARC / Optical - Shield Android TV Original Android Development

2019-09-17:
- Added 8.0.0 version
2019-05-05:
- Updated 7.2.3 DTS version
2019-03-16:
- Added 7.2.3 version
- Added 7.2.3 version that also transcodes DTS, for those having a TV only supporting AC3
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Having a non HDR enabled AVR, I became pissed to have to choose between HDR on my AC3-only TV or 5.1 on my AVR, so I hacked through the Nvidia android sources to implement on-the-fly EAC3 to AC3 conversion.
Although Nvidia does not provide the full sources to the shield, still thanks to them for making it easy to hack it.
Prerequisite:
rooted shield, obviously. If you don't plan to do anything fancy, just stick to the rooted firmwares provided by NV itself at https://developer.nvidia.com/shield-developer-os-images
Concept:
Netflix and Amazon are using the Android provided "AUDIO_FORMAT_E_AC3" file format, which Android transforms into IEC61937 packets suitable to be streamed to the AVR/TV.
I hacked this encoding process to transform EAC3 to AC3.
You have to set your Shield on "Surround = Always" for this to work!
Issues:
- Not having the full sources, I had to keep code modification very localized. The only actual development is done in libaudiospdif.so
- If your TV/AVR provides more than AC3, even setting the shield surround setting to "Always" does not actually present EAC3 to Netflix. I dissassembled libaudiopolicymanagerdefault.so and did binary edit to fix this.
- EAC3 is output at 192khz, while AC3 is at 48khz. I dissassembled libaudioflinger.so and did binary edit to fix this.
- Shield ships both arm32 and aarch64 versions of those libs, but it seems only the arm32 is actually used by the system and/or the apps.
Code:
- Nvidia provides partial sources of the Shield at https://developer.nvidia.com/shield-open-source
- The modifications to libaudiospdif are available at https://gitlab.com/koying/android_platform_system_media
- The ffmpeg version I used is the one from https://osdn.net/projects/android-x86/scm/git/external-ffmpeg
- I won't go into more details, as I'm not even sure I remember all the steps
Binary edits (vs. 7.2.2 original binaries from Shield pro)
- /system/lib/libaudiopolicymanagerdefault.so
Code:
old: 00 20 b8 f1 0e 0f 18 bf 01 20 40 ea 07 00 10 f0 01 0f
new: 00 20 b8 f1 0e 0f 18 bf 01 20 40 f0 00 00 10 f0 01 0f
- /system/lib/libaudioflinger.so
Code:
old: 00 bf fe 88 01 00 01 00 00 00 04 00 00 00 01 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00
new: 00 bf fe 88 01 00 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00
Binary edits (vs. 8.0.0 original binaries from Shield pro)
- /system/lib/libaudioflinger.so
Code:
old: 49 00 00 00 66 00 00 00 46 00 00 00 41 00 00 00 01 00 00 00 04 00 00 00 01 00 00 00 04 00 00 00 04 00 00 00 04 00 00 00 A0 26 6B E4 DD DD DB 11
new: 49 00 00 00 66 00 00 00 46 00 00 00 41 00 00 00 01 00 00 00 01 00 00 00 01 00 00 00 04 00 00 00 04 00 00 00 04 00 00 00 A0 26 6B E4 DD DD DB 11
For 8.0.0, go to "Device Preferences - Display & Sound - Advanced sound settings - Available formats", select "Manual" and enable "AC3" and "E-AC3" (+ DTS if your TV supports it).
Binaries
Attached. Those are certified working on Shield pro 7.x and 8.0.0.
Worst case, just revert with the backup you surely did
Use with scripts similar to :
Backup:
Code:
adb pull /system/lib/libaudioflinger.so libaudioflinger.so.bak
adb pull /system/lib/libaudiopolicymanagerdefault.so libaudiopolicymanagerdefault.so.bak
adb pull /system/lib/libaudiospdif.so libaudiospdif.so.bak
Push:
Code:
adb root
adb remount
# Not for 8.0.0
adb push -p libaudiopolicymanagerdefault.so /system/lib/
adb push -p libaudioflinger.so /system/lib/
adb push -p libaudiospdif.so /system/lib/
adb push -p libavcodec.so /system/lib/
adb push -p libavformat.so /system/lib/
adb push -p libavutil.so /system/lib/
adb push -p libswresample.so /system/lib/
adb shell sync
adb reboot
Enjoy

excellent work as usual.
this doesn't apply to me, as I only have bog standard stereo, but would you mind distributing this as a magisk module?
Most people will probably use magisk for root anyway.

Sorry, no magisk experience here. Anyone is free to package the binaries, obviously

I have a non HDR enabled AVR and am planning to buy a new 4k HDR TV. I'm not sure if I understood how this is intended to work.
Hook up Shield directly to TV via HDMI cable to get HDR. Now TV hooked up to AVR out via hdmi sends 5.1 sound to the AVR via ARC. Is that correct?
I now wonder if your hack is a universal solution also for other apps....
What about kodi app? Could you try if it also works for playing back HDR 5.1 content via kodi app?

Yep. Shield->TV (AC3 enabled)->AVR (via ARC or SPDIF).
Kodi and derivatives do the transcoding from anything to AC3 5.1 themselves. They don't need this hack.
It will work for any app using the Android EAC3 format (not IEC). Works for Netflix and Amazon Prime for me.

Tried with my Shield TV and works perfectly. Netflix and Amazon have both Dolby 5.1 in my Sonos system. Plex will still transcode anything that has EAC3 as it says the format is not supported. Many thanks!

Hi
This looks interesting.
While I've no need for this as I have DD+ /'EAC3 AVR, do you think this approach will help shield output unadulterated digital stream over USB? The tidal app does master audio, as does the Kodi addin. But shield resamples to either 44.1, 48, or 192 before sending over USB depending on whether you've picked stereo, high quality stereo, or multi channel.
How'd you go about finding the binary edits needed, was that by comparing to other binaries?
Thank you
Chris

No clue. What's the issue with USB audio?

It works like a charm! I can finally enjoy the 5.1 also on Prime and Netflix with a very old Thomson 5.1 home theater.
Thank you very much!

@Koying you are my super-hero 2019!!!!
No joke, I search for about 3 years for a solution to this! I am having a old Sound system wich only can handle DD & DTS.
I will try this and if it is working I will buy you a coffe, or did you prefer beer? Sorry I see you are from brussel. Beer shouldn't be ypir problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Greetings by Idijt

i have just purchased a shield tv and ran straight into this issue... time to root

Koying said:
No clue. What's the issue with USB audio?
Click to expand...
Click to collapse
Sorry for late reply...went AWOL for a bit. (Cracked elbow so couldn't hold tablet so internet capability was reduced)
The shield upsamples/dowmsamples audio output via USB.
To 44.1 kHz always if stereo picked in settings, 48kHz if high quality stereo picked or 192 if multichannel.
Does this from both Kodi ignoring the Kodi settings (including both standalone flac files and Kodi addon) and the official Tidal app and any number of other media players...so assuming is driver issue.
In adb logs when connecting the DAC you can see handshake with correct capabilities up to say 384kHz but those are ignored over USB.
My problem is that embedded in the data is higher resolution audio and resampling in this way is breaking the ability of the DAC to expand that audio.
Cheers
Chris

Thank you very much, works perfect
Sonos Beam (+2x Sonos one) --Tos Link --> HDMI Splitter
HDMI Splitter --HDMI--> Samsung TV
Shield TV --HDMI--> HDMI Splitter
Now i get Dolby Digital from the Shield TV Prime/Netflix app through my sonos setup!

wow this is just what i needed to make proper use of my shield. Is there anything lost by rooting with the official images? For example does 4K HDR netflix still work?
Thanks

No, nothing lost. The point of this was exactly to have 4k + HDR + 5.1 on Netflix

Koying said:
No, nothing lost. The point of this was exactly to have 4k + HDR + 5.1 on Netflix
Click to expand...
Click to collapse
Cool thanks. I'll give this a go on the weekend then. The root/image installation process seems quite complicated though.

Does this work for all audio? Not just Netflix / amazon. I have a plex library and would love to use this

Quick question on the root for this. Can I just follow the nvidia steps to install their dev images or must i install magisk or twrp?
Thanks

Brthrmanbill said:
Does this work for all audio? Not just Netflix / amazon. I have a plex library and would love to use this
Click to expand...
Click to collapse
It works for all EAC3 using https://developer.android.com/reference/android/media/AudioFormat.html#ENCODING_E_AC3
I'm pretty sure Plex transcodes by itself if needed, though

jarayn said:
Quick question on the root for this. Can I just follow the nvidia steps to install their dev images or must i install magisk or twrp?
Click to expand...
Click to collapse
See OP. If you root just for this, the Nvidia way is the simplest and safest, IMO

Related

[Q] "Forced upload by key pressing" - ?

I have Galaxy 3 (i5801), but there isn't any topic for this device, so I'm writing here.
When I try to enter into recovery mode (VolUP+Home+Power) the device shows me this message.
When I try to enter to recovery via ADBs reboot recovery command the phone restoring the factory settings.
I want to root the device, but I can't get into recovery mode.
i5801 is the Orange branded version of i5800, the hardware is same, but the software is fully "customized".

That is not a Galaxy S
it is a Samsung I5801 Galaxy Apollo
totally different hardware spec
http://www.gsmarena.com/samsung_i5801_galaxy_apollo-3432.php
General 2G Network GSM 850 / 900 / 1800 / 1900
3G Network HSDPA 900 / 2100
Announced 2010, June
Status Available. Released 2010, July
Size Dimensions 113.5 x 55 x 12.6 mm
Weight 113 g
Display Type TFT capacitive touchscreen, 16M colors
Size 240 x 400 pixels, 3.2 inches
- Touch Wiz 3.0
- Accelerometer sensor for UI auto-rotate
- Proximity sensor for auto turn-off
- Multi-touch input method
Sound Alert types Vibration; MP3, WAV ringtones
Speakerphone Yes
- 3.5 mm audio jack
- DNSe (Digital Natural Sound Engine)
Memory Phonebook Practically unlimited entries and fields, Photocall
Call records Practically unlimited
Internal 512MB ROM, 256MB RAM
Card slot microSD, up to 32GB, 1GB card included, buy memory
Data GPRS Class 10 (4+1/3+2 slots), 32 - 48 kbps
EDGE Class 10, 236.8 kbps
3G HSDPA, 3.6 Mbps
WLAN Wi-Fi 802.11 b/g/n
Bluetooth Yes, v3.0 with A2DP
Infrared port No
USB Yes, v2.0 microUSB
Camera Primary 3.15 MP, 2048x1536 pixels, autofocus
Features Geo-tagging, face and smile detection
Video Yes, [email protected]
Secondary No
Features OS Android OS, v2.1 (Eclair), upgradable to v2.2
CPU 667 MHz processor
Messaging SMS(threaded view), MMS, Email, Push Mail, IM
Browser HTML
Radio Stereo FM radio with RDS
Games
Colors Black, White
GPS Yes, with A-GPS support
Java Via third party application
- Orange Application Shop
- Orange Maps, Orange TV, Orange Push Email
- Contact Back & Restore, Orange Photo
- Digital compass
- MP4/DivX/XviD/WMV/H.264/H.263 player
- MP3/WAV/eAAC+ player
- Organizer
- Document editor(Word, Excel, PowerPoint, PDF)
- Google Search, Maps, Gmail,
YouTube, Calendar, Google Talk integration
- Voice memo
- T9
Battery Standard battery, Li-Ion 1500 mAh
Stand-by Up to 620 h (2G) / Up to 480 h (3G)
Talk time Up to 15 h 30 min (2G) / Up to 7 h 15 min (3G)
Misc SAR EU 0.58 W/kg (head)
... weird i just checked, we do not have a forum for this phone yet but this phone is so old already

I know, but there isn't any topic for Galaxy 3, and the software is very similare to SGS (also the GPS had the same problem).

[Q] Video Quality in "New Experience 9.9.1" [CLOSED][UNRESOLVED][NEW DEVICE]

[Q] Video Quality in "New Experience 9.9.1" [CLOSED][UNRESOLVED][NEW DEVICE]
As a newbee i'm not allowed to post in the Developers thread of this rom so I'm asking here :
I flashed the New Experience 9.9.1 rom and it's working great, but when I record video with the camera app the quality is very low. Also the sound quality is very bad in the resulting video files.
I noticed the files are .3gp and it used to be mp4. I checked the file with avconv and it showed 176x144
I've set the quality to 'wide'
Any help is appreciated.
Code:
avconv -i VID_20130630_122508.3gp
avconv version 0.8.6-4:0.8.6-0ubuntu0.12.04.2+codecs1, Copyright (c) 2000-2013 the Libav developers
built on Apr 6 2013 02:05:22 with gcc 4.6.3
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x9ff9a0] multiple edit list entries, a/v desync might occur, patch welcome
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'VID_20130630_122508.3gp':
Metadata:
major_brand : 3gp4
minor_version : 0
compatible_brands: isom3gp4
creation_time : 1947-06-30 10:25:32
Duration: 00:00:23.06, start: 0.000000, bitrate: 372 kb/s
Stream #0.0(eng): Audio: amrnb, 8000 Hz, 1 channels, flt, 5 kb/s
Metadata:
creation_time : 1947-06-30 10:25:32
Stream #0.1(eng): Video: mpeg4 (Simple Profile), yuv420p, 176x144 [PAR 1:1 DAR 11:9], 247 kb/s, 8.60 fps, 1k tbr, 90k tbn, 1k tbc
Metadata:
creation_time : 1947-06-30 10:25:32
At least one output file must be specified

EZONETRONICS Android 4.4 Quad Core Universal 2DIN Car Stereo GPS Navigation Wifi Radi

Hi Guys, i am in the search of a new Android HU for my Hyundai Accent 1.5 CRDI (2007) model...
After searching several Quadcore Android HU on ALibaba, Aliexpress, and also on Ebay and Amazon, finally i saw many threads on Android HU here with custom ROMs... just like for a Phone with Rooting, customisation etc etc...
All i want to ask here is which is the best 2Din Quadcore RK3188 chipset Android HU with good custom ROM support.
http://www.aliexpress.com/item/EZONETRONICS-Android-4-4-Car-GPS-Navigation-2DIN-Car-Stereo-Radio-Car-GPS-Bluetooth-USB-SD/32521236138.html
Here is the cheapest 2Din quadcore RK3188 Android HU available for 185$ including shipping. It is Universal type.
All i want to ask that is it better or should i go for Joying/Klyde( little costly) or any other famous brand here..
Pls guide me on this...
Thanks in advance...

It is not seem a good quality item, I suggest you try to find some famous brand item as you mentioned, for KLD unit,you can easily find from the seller Pumpkin who sold a lot of RK3188 Android units from KLD

you have a link bro ? thanks for your answer ...

plikmuny said:
you have a link bro ? thanks for your answer ...
Click to expand...
Click to collapse
Hi there
Sorry for replying you late, I'm away these days!
I can't do that as it is like self promotion action, but you can search on google by Klyde pumpkin stereo, you may find their website and ask.
Wish you luck!

hello
i ve the same product
i search the best update /firmware for us
can you help me please ?

i confirm it's a good product but the firmware is bad
my bluetooth doesn't function for the moment
it's a rk3188T
with 1 go ddr3
1024x600
---------- Post added at 07:40 PM ---------- Previous post was at 07:35 PM ----------
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
anyone for help me ?

not answer ?

caraudio30000 said:
not answer ?
Click to expand...
Click to collapse
Hello,
I'm thinking to buy it. I asked if it supports stering wheel control.
I saw your firmware is old. Did you check the firmware update Ezonetronics published 17th February?
Good luck.

alphyl said:
Hello,
I'm thinking to buy it. I asked if it supports stering wheel control.
I saw your firmware is old. Did you check the firmware update Ezonetronics published 17th February?
Good luck.
Click to expand...
Click to collapse
nothing stering wheel control possible
the firmware of february 2016 is bug so a lot of people can't install it
i speak with someone in china , he give me the plan electronic , and he will see if he has a module bluetooth
(my pairing bluetooth doesn't function ) maybe i must to changed it

New firmware but still same problems
what about this firmware , somebody check it?
http://forum.xda-developers.com/showpost.php?p=58249825&postcount=7614

i have the same unit and the same problem plus problem with usb

miloscy said:
New firmware but still same problems
what about this firmware , somebody check it?
http://forum.xda-developers.com/showpost.php?p=58249825&postcount=7614
Click to expand...
Click to collapse
i think the ezonetronics is not an MTCB-device. so the FW from the thread you mentioned will not work (i guess).
oh yeah and i think my thread over at connected car is the same unit as this one.
http://forum.xda-developers.com/gen...t-wifi-gps-t3321263/post66321138#post66321138
cheers!
if anyone dares to try and is successful, im happy to follow. but i donit want to brick my device (yet).

Hi
this is new product base on 3188 , tech spec you can find here
http://www.gearbest.com/car-dvd-player/pp_312578.html

so i installed the new april 2016-firmware.
BT works again for me, at least A2DP and HFP.
finally going to test the unit in my car soon. my guess is that the viewing angle in my car is going to be a problem with this unit... but we will see.
at first, everything needs to work OK.

So here's some pictures i just made.
comments are welcome. the power draw is what my power supply tells me, might not be accurate. im guessing with radio/music playback and GPS running at the same time the draw might be higher.
i also connected a backup camera, the screen switches instantly to its image once you give +12V on the Back-Car wire so its not an app, also works while the unit's android is still booting. by the way boot-time for me is around 45seconds with the 2016-April-05 firmware.
about the installed software i am not too happy so i did the following:
-KingRoot for root. (supersume doesnt seem to work. any ideas?)
-NovaLauncher to replace the non-(or badly)customizable stock one
-CoPilot Live Premium (purchased this a ong time ago, had to make a titanium-backup from my tablet)
-AdAway (through F-Droid)
-SwiftKey Keyboard. i just like it better plus you can at least set the layout a little
- Dimly to manage brightness easier
-Total Commander for pushing files around
-HERE-Maps dos NOT install. Even the pulled APK (titanium backup) does not work.
about the device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
general settings menu
factory setings menu. code for this is: 1 2 3 4 5 6
max power draw with brightness at max. i use the app dimly to quickly change brithness.
power draw on minimal brightness
max power draw on Antutu 3D-benchmark. my score is 19958
copilot GPS navigation running
CPU-Z screens
AIDA64-Dump
<<< System >>>
Hersteller: rockchip
Modell: rkpx3
Marke: rockchip
Board: rk30sdk
Gerät: rkpx3
Hardware: rk30board
Produkt: rkpx3
Seriennummer: OPDPV0EG3M
Gesamter Speicher: 1024 MB
Verfügbarer Speicher: 425 MB
Interner gesamter Massenspeicher: 6354 MB
Interner freier Massenspeicher: 5561 MB
Geräte Besonderheiten: android.hardware.bluetooth
android.hardware.bluetooth_le
android.hardware.camera
android.hardware.camera.any
android.hardware.camera.front
android.hardware.faketouch
android.hardware.location
android.hardware.location.network
android.hardware.microphone
android.hardware.screen.landscape
android.hardware.screen.portrait
android.hardware.sensor.accelerometer
android.hardware.touchscreen
android.hardware.touchscreen.multitouch
android.hardware.touchscreen.multitouch.distinct
android.hardware.touchscreen.multitouch.jazzhand
android.hardware.usb.accessory
android.hardware.usb.host
android.hardware.wifi
android.hardware.wifi.direct
android.software.app_widgets
android.software.device_admin
android.software.live_wallpaper
<<< CPU >>>
Kern Architektur: 4x ARM Cortex-A9 @ 1200 MHz
Befehlssatz: 32-bit ARMv7
CPU Revision: r3p0
CPU Kerne: 4
CPU Taktbereich: 312 - 1200 MHz
Kern 1 Takt: 1200 MHz
Kern 2 Takt: 1200 MHz
Kern 3 Takt: 1200 MHz
Kern 4 Takt: 1200 MHz
CPU Auslastung: 6 %
Skalierender Regler: interactive
CPU ABI: armeabi-v7a
CPU ABI2: armeabi
AES: Nicht unterstützt
NEON: Unterstützt
SHA1: Nicht unterstützt
SHA2: Nicht unterstützt
<<< Anzeige >>>
Bildschirm Auflösung: 1024 × 600
Bildschirm Größe: 154 mm × 86 mm
Bildschirm Diagonale: 6,94 zoll
Pixel Dichte: 171 dpi (mdpi)
xdpi / ydpi: 169 / 177 dpi
GPU Hersteller: ARM
GPU Renderer: Mali-400 MP
Auffrischungsrate: 60 Hz
Standard Ausrichtung: Querformat
OpenGL ES Version: 2.0
GPU Version: OpenGL ES 2.0
OpenGL ES Erweiterungen: GL_EXT_debug_marker
GL_OES_texture_npot
GL_OES_compressed_ETC1_RGB8_texture
GL_OES_standard_derivatives
GL_OES_EGL_image
GL_OES_depth24
GL_ARM_rgba8
GL_ARM_mali_shader_binary
GL_OES_depth_texture
GL_OES_packed_depth_stencil
GL_EXT_texture_format_BGRA8888
GL_OES_vertex_half_float
GL_EXT_blend_minmax
GL_OES_EGL_image_external
GL_OES_EGL_sync
GL_OES_rgb8_rgba8
GL_EXT_multisampled_render_to_texture
GL_EXT_discard_framebuffer
GL_OES_get_program_binary
GL_ARM_mali_program_binary
GL_EXT_shader_texture_lod
GL_EXT_robustness
GL_OES_depth_texture_cube_map
GL_KHR_debug
<<< Netzwerk >>>
<< Telefonie >>
Telefon Typ: Keine
<< Wi-Fi >>
Festgestellt: Aktiviert
SSID: "schmutzfink_EXT"
BSSID: 60:e3:27:2d:14:63
Versteckte SSID: Nein
MAC-Adresse: 7c:c7:09:ac:ea:44
Signalstärke: -60 dBm (sehr gut)
Link Geschwindigkeit: 72 Mbps
Netzwerk ID: 0
Gateway: 192.168.0.1
Netzmaske: 255.255.255.0
DNS1: 192.168.0.1
DHCP Lease Dauer: 24 Stunden
Wi-Fi Direkt: Unterstützt
<<< Akku >>>
Stromquelle: A/C Ladegerät
Wert: 50 %
Status: Entlade
Allgemeinzustand: Gut
Technologie: Li-ion
<<< Android >>>
Android Version: 4.4.4 (KitKat)
API Level: 19
Rooted Gerät: Ja
Android ID: 1c990ca8c8ada191
Bootloader: fastboot
Build ID: rkpx3-eng 4.4.4 KTU84Q eng.zhw.20160401.111308 test-keys
Code Name: REL
Fingerprint: rockchip/rkpx3/rkpx3:4.4.4/KTU84Q/eng.zhw.20160131.111308:eng/test-keys
ID: KTU84Q
Zunehmend: eng.zhw.20160131.111308
Java Runtime Version: Android Runtime 0.9
Java VM Version: Dalvik 1.6.0
Java VM Heap Size: 64 MB
Kernel Architektur: armv7l
Kernel Version: 3.0.36+ ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #5 SMP PREEMPT Mon Mar 28 22:17:52 CST 2016
Tags: test-keys
Typ: eng
Google Play Services Version: 8.7.03 (2645110-032)
OpenSSL Version: OpenSSL 1.0.1e 11 Feb 2013
ZLib Version: 1.2.8
ICU CLDR Version: 23.0
ICU Library Version: 51.1.0.1
ICU Unicode Version: 6.2
Android Sprache: Deutsch (Deutschland)
Eingestellte Zeitzone: Mitteleuropäische Normalzeit (UTC+01:00)
Laufzeit: 00:04:40
<<< Geräte >>>
<< Hintere Kamera >>
<< Vordere Kamera >>
Auflösung: 2,1 MP (1920 × 1080)
Video Auflösung: 2,1 MP (1920 × 1080)
Video Schnappschuss: Nicht unterstützt
Video Stabilization: Nicht unterstützt
Zoom: Nicht unterstützt
Glatter Zoom: Nicht unterstützt
Auto Belichtungssperre: Nicht unterstützt
Auto Weißabgleichssperre: Nicht unterstützt
Flash: Unterstützt
<< USB-Geräte - Linux 3.0.36+ dwc_otg_hcd DWC OTG Controller >>
Hersteller: Linux 3.0.36+ dwc_otg_hcd
Produkt: DWC OTG Controller
Seriennummer: usb20_otg
Geräte ID: 1D6B-0002
Geräteklasse: 09 / 00 (Full-Speed Hub)
Geräteprotokoll: 00
Unterstützte USB Version: 2.00
Momentane Geschwindigkeit: 480 Mbps
<< USB-Geräte - Linux 3.0.36+ host20_hcd DWC OTG Controller >>
Hersteller: Linux 3.0.36+ host20_hcd
Produkt: DWC OTG Controller
Seriennummer: usb20_host
Geräte ID: 1D6B-0002
Geräteklasse: 09 / 00 (Full-Speed Hub)
Geräteprotokoll: 00
Unterstützte USB Version: 2.00
Momentane Geschwindigkeit: 480 Mbps
<< USB-Geräte - Realtek 802.11n NIC >>
Hersteller: Realtek
Produkt: 802.11n NIC
Seriennummer: 7CC709ACEA44
Geräte ID: 0BDA-8179
Geräteklasse: 00 / 00
Geräteprotokoll: 00
Unterstützte USB Version: 2.00
Momentane Geschwindigkeit: 480 Mbps
Maximale Leistung: 500
Keine OpenCL geräte gefunden.
Keine CUDA Geräte gefunden.
Keine PCI Geräte gefunden.
<<< Temperatur >>>
Keine Temperatursensoren gefunden.
<<< Sensoren >>>
Gravity sensor:
Compass Magnetic field sensor:
Orientation Sensor:
Gyroscope sensor:
Proximity sensor: 9,0 cm
Light sensor:
Pressure sensor:
Temperature sensor:
Rotation Vector Sensor:
Gravity Sensor:
Linear Acceleration Sensor:
<<< Apps >>>
AdAway: org.adaway(v3.1.1)
AIDA64: com.finalwire.aida64(v1.35)
BusyBox Pro: stericson.busybox.donate(v35)
CoPilot EU: com.alk.copilot.eumarket.premiumeupan(v9.6.4.144)
CPU-Z: com.cpuid.cpu_z(v1.19)
Dimly: es.richardsolano.filter(v0.6.1)
F-Droid: org.fdroid.fdroid(v0.99.2)
FasterGPS: org.fastergps(v1.11)
Fing - Network Tools: com.overlook.android.fing(v3.02)
Google Play Musik: com.google.android.music(v6.6.2612Y.2725627)
Network Info II: aws.apps.networkInfoIi(v0.7.1)
Nova Launcher: com.teslacoilsw.launcher(v4.2.2)
Nova Launcher Prime: com.teslacoilsw.launcher.prime(vD)
Quick Reboot: phongit.quickreboot(v1.6.4)
SwiftKey Tastatur: com.touchtype.swiftkey(v6.3.2.53)
TeslaUnread: com.teslacoilsw.notifier(v5.0.6)
Titanium Backup: com.keramidas.TitaniumBackup(v7.3.0.2)
Titanium Backup PRO: com.keramidas.TitaniumBackupPro(v1.3.0)
Total Commander: com.ghisler.android.TotalCommander(v2.72)
TotalCmd-FTP (Dateitransfers): com.ghisler.tcplugins.FTP(v2.08)
Trimmer (fstrim): com.fifthelement.trimmer(v1.32)
TWRP Manager: com.jmz.soft.twrpmanager(v8.12)
<<< Codecs >>>
OMX.rk.video_decoder.avc: video/avc
OMX.rk.video_decoder.m2v: video/mpeg2
OMX.google.vp8.decoder: video/x-vnd.on2.vp8
OMX.google.vp9.decoder: video/x-vnd.on2.vp9
OMX.rk.video_decoder.h263: video/3gpp
OMX.rk.video_decoder.m4v: video/mp4v-es
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
OMX.google.amrnb.decoder: audio/3gpp
OMX.google.amrwb.decoder: audio/amr-wb
OMX.google.aac.decoder: audio/mp4a-latm
OMX.google.g711.alaw.decoder: audio/g711-alaw
OMX.google.g711.mlaw.decoder: audio/g711-mlaw
OMX.google.vorbis.decoder: audio/vorbis
OMX.google.mp3.decoder: audio/mpeg
RkAudioDecoder_DTS: audio/vnd.dts.hd
RkAudioDecoder_WMA: audio/x-ms-wma
RkAudioDecoder_WMAPRO: audio/x-ms-wmapro
RkAudioDecoder_AC3: audio/x-ms-ac3
RkAudioDecoder_RA: audio/vnd.rn-realaudio
RkAudioDecoder_AAC: audio/mp4a-latm
RkAudioDecoder_WAV: audio/wav
FLACDecoder: audio/flac
AACDecoder_MIRRORING: audio/mp4a-latm
OMX.google.vp8.encoder: video/x-vnd.on2.vp8
OMX.rk.video_encoder.avc: video/avc
RkOn2Encoder: video/avc
OMX.google.h263.encoder: video/3gpp
OMX.google.mpeg4.encoder: video/mp4v-es
OMX.google.amrnb.encoder: audio/3gpp
OMX.google.amrwb.encoder: audio/amr-wb
OMX.google.aac.encoder: audio/mp4a-latm
OMX.google.flac.encoder: audio/flac
AACEncoder: audio/mp4a-latm
OMX.rk.video_encoder.avc: video/avc
OMX.google.h264.encoder: video/avc
RkOn2Encoder: video/avc
OMX.google.raw.decoder: audio/raw
OMX.google.mp3.decoder: audio/mpeg
RkAudioDecoder_DTS: audio/vnd.dts.hd
RkAudioDecoder_WMA: audio/x-ms-wma
RkAudioDecoder_WMAPRO: audio/x-ms-wmapro
RkAudioDecoder_AC3: audio/x-ms-ac3
RkAudioDecoder_RA: audio/vnd.rn-realaudio
RkAudioDecoder_WAV: audio/wav
RkAudioDecoder_AAC: audio/mp4a-latm
FLACDecoder: audio/flac
AACDecoder_MIRRORING: audio/mp4a-latm
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
RkOn2Decoder: video/x-vnd.on2.unknow
HEVCDecoder: video/hevc
<<< Verzeichnisse >>>
Daten: /data
Root: /system
Java Home: /system
Download/Cache Inhalt: /cache
<< Externer Massenspeicher >>
<< Mount Points >>
/: Gerät: rootfs
Dateisystem: rootfs
Nur lesen
/dev: Gerät: tmpfs
Dateisystem: tmpfs
Lesen-Schreiben
/dev/pts: Gerät: devpts
Dateisystem: devpts
Lesen-Schreiben
/dev/cpuctl: Gerät: none
Dateisystem: cgroup
Lesen-Schreiben
/proc: Gerät: proc
Dateisystem: proc
Lesen-Schreiben
/sys: Gerät: sysfs
Dateisystem: sysfs
Lesen-Schreiben
/sys/fs/cgroup: Gerät: none
Dateisystem: tmpfs
Lesen-Schreiben
/sys/fs/cgroup/memory: Gerät: none
Dateisystem: cgroup
Lesen-Schreiben
/sys/kernel/debug: Gerät: /sys/kernel/debug
Dateisystem: debugfs
Lesen-Schreiben
/acct: Gerät: none
Dateisystem: cgroup
Lesen-Schreiben
/mnt/secure: Gerät: tmpfs
Dateisystem: tmpfs
Lesen-Schreiben
/mnt/asec: Gerät: tmpfs
Dateisystem: tmpfs
Lesen-Schreiben
/mnt/obb: Gerät: tmpfs
Dateisystem: tmpfs
Lesen-Schreiben
/system: Gerät: /dev/block/mtd/by-name/system
Dateisystem: ext4
Nur lesen
/cache: Gerät: /dev/block/mtd/by-name/cache
Dateisystem: ext4
Lesen-Schreiben
/metadata: Gerät: /dev/block/mtd/by-name/metadata
Dateisystem: ext4
Lesen-Schreiben
/data: Gerät: /dev/block/mtd/by-name/userdata
Dateisystem: ext4
Lesen-Schreiben
/mnt/shell/emulated: Gerät: /dev/fuse
Dateisystem: fuse
Lesen-Schreiben
/storage/emulated: Gerät: tmpfs
Dateisystem: tmpfs
Lesen-Schreiben
/mnt/external_sd0: Gerät: /dev/block/vold/179:1
Dateisystem: vfat
Lesen-Schreiben
/storage/emulated/0: Gerät: /dev/fuse
Dateisystem: fuse
Lesen-Schreiben
/storage/emulated/legacy: Gerät: /dev/fuse
Dateisystem: fuse
Lesen-Schreiben
<<< Systemdateien >>>
Buddy Info: /proc/buddyinfo
Build Properties: /system/build.prop
Character and Block Devices: /proc/devices
Befehlszeile: /proc/cmdline
CPU Informationen: /proc/cpuinfo
Ausführende Domains: /proc/execdomains
Dateisystem: /proc/filesystems
Frame Buffer Devices: /proc/fb
GPS Konfiguration: /system/etc/gps.conf
Hosts: /system/etc/hosts
Interrupts: /proc/interrupts
Eingabegeräte: /proc/bus/input/devices
I/O Ports: /proc/ioports
Kernel Version: /proc/version
Auslastungs Durchschnitt: /proc/loadavg
Gesperrte Dateien: /proc/locks
Speicher Informationen: /proc/meminfo
Speicher Karte: /proc/iomem
Sonstige Treiber: /proc/misc
Partitionen: /proc/partitions
Statistik: /proc/stat
Swap Spaces: /proc/swaps
hope this helps with some questions.
cheers!

with your latest firmware update is the sound quality any better? i am thinking about getting rid of my old pioneer avic-d3 in place of an android auto or pandora capable double din i can use with my Note 5 but not break the bank and from what i have seen all these chinese made devices are great except sound quality

illsaveyou said:
with your latest firmware update is the sound quality any better? i am thinking about getting rid of my old pioneer avic-d3 in place of an android auto or pandora capable double din i can use with my Note 5 but not break the bank and from what i have seen all these chinese made devices are great except sound quality
Click to expand...
Click to collapse
the sound appears better, but as i said, i have not installed the unit to my car yet. i do not want to rush it.
basically i think the idea behind this specific device is great. but they realized that it has flaws and this is why its being sold so cheap.
technically (i tore it apart once) it is an android tablet. not a bad one. but of course tablet lack what you need for a car stereo, that is an amp and FM-radio.
plus this specific tablet-hardware used here has no built-in Bluetooth. so this is connected via some kind of (undocumented) serial connection (not USB!) and this is why it is not generally available to android, only to the installed BT-app.
what i am actually thinking is getting my old 16gb Nexus7-2012 to fit my dashboard and fit the "classic" stereo-headunit somewhere else...
and then again im already happy with my N7 in a fixed-installation-holder (brodit.se) connected through AUX to my radio...
and even further, if i forget my N7, i just use my 1+1 ... and its big enough... plus live traffic data through mobile data...
im still going for the fixed installtion anyway just to have something to fiddle around with

elchmartin said:
the sound appears better, but as i said, i have not installed the unit to my car yet. i do not want to rush it.
basically i think the idea behind this specific device is great. but they realized that it has flaws and this is why its being sold so cheap.
technically (i tore it apart once) it is an android tablet. not a bad one. but of course tablet lack what you need for a car stereo, that is an amp and FM-radio.
plus this specific tablet-hardware used here has no built-in Bluetooth. so this is connected via some kind of (undocumented) serial connection (not USB!) and this is why it is not generally available to android, only to the installed BT-app.
what i am actually thinking is getting my old 16gb Nexus7-2012 to fit my dashboard and fit the "classic" stereo-headunit somewhere else...
and then again im already happy with my N7 in a fixed-installation-holder (brodit.se) connected through AUX to my radio...
and even further, if i forget my N7, i just use my 1+1 ... and its big enough... plus live traffic data through mobile data...
im still going for the fixed installtion anyway just to have something to fiddle around with
Click to expand...
Click to collapse
so not to beat a dead horse, i know you dont have your headunit in the car yet but on the topic of sound quality. you said you took it apart and it basically was just a bit tablet, so if i had to guess the sound is crap because of the DAC the unit uses, think getting an external DAC could beef up how these chinese made units sound?

illsaveyou said:
so not to beat a dead horse, i know you dont have your headunit in the car yet but on the topic of sound quality. you said you took it apart and it basically was just a bit tablet, so if i had to guess the sound is crap because of the DAC the unit uses, think getting an external DAC could beef up how these chinese made units sound?
Click to expand...
Click to collapse
yeah, but i do not know ho this would be done. if you like i can provide photos from the inside of the unit.
there is only 1 USB in the front, so a USB-DAC kind of rins the looks.
some russian guys were talking about another DAC on 4PDA, at least thats what i understood from the google translator (russian is terribly translated by google, i guess the grammar is just nowhere close to english, german, latin....) i do not know if anyone was successful there.
the sound quality appears better with the latest FW (April '16), first thing to do ere is boost treble on the EQ. the middle setting i think is just cutting down from normal.
the sounds from the CPU-load does not really irriate once you have music playing. i guess with my 15 year-old car it will not be a problem @200kph
ah and i figured how to get HERE maps to it: used titanium backup on my phone and copied that to the unit. works fine.
cheers!

so, here's and update.
GPS was fine, recieving an OK signal but not as good as my phone (although i had the antenna placed directly at the windscreen... also tried other locations... same result). CoPilot GPS ran fine and the viewing angle was better than i was afraid it woud be.
playback through google play music works, the sound is terrible. even when turning the treble all up and bass -1 its still... somehow not clear. since i enjoy music very much while driving this is a deal-breaker for me...
an absolute no-go is the FM-reception. i got 0 stations on auto-tuning, and 1 very bad with static tuning manually. i do not use external antenna-power, but my current radio (Alpine) finds like 10 stations where i live in excellent quality.
so i guess i'll try to return/refund the device or sell it on ebay. learned my lesson.
maybe ill just build a case around it and use it as a kitchen radio ... hey, might actually be worth a shot
cheers!

Chinese 2 Din 7 inch DVD GPS NAVIGATION CAR STEREO TOUCH

I'm trying to figure out my new Chinese DVD GPS software and hardware . the issue here is I want to install new software or eve upgrade the current system to play all types of videos .mp4 and .mpg etc.
thanks
API Ver: TL-1-C0-V2.01
MCU Ver: TL_30_C0L_5000_CAN(A)
NK Ver: C0-0-CHS-L-R1P1-V2.30
EBOOT Ver: C0-4-L-R1P1-V2.30
DVD Ver: R-86C-096I-NC-NP-1.0-IPOD
FLASH CAPACITY28 /59 Byte
RAM Capacity: 62/96 Byte
SN: 00000000
GPS Port: COM2 9600

Well I have a similar unit, and it plays those file types right out of the box using the "Videos" native app.
Have you looked into possibly updating to the Malaysk ROM? Its in the MTCB Development sub-forum...

thewesman said:
Well I have a similar unit, and it plays those file types right out of the box using the "Videos" native app.
Have you looked into possibly updating to the Malaysk ROM? Its in the MTCB Development sub-forum...
Click to expand...
Click to collapse
thanks for your reply , I believe the software is wince 6.0 now i'm looking for cecmd.exe to log to the windows system itself

4D vibration supported games

Does anyone know about any supported games for 4D vibration? So far I had no luck finding any

Dude I Think And I Have It. Game For Peace (Chinese PUBG Mobile Version). It Has 4D Vibration.

Database Develop

welcome