Database Develop

Eonon GA2163 Tegra T3 rom available roms and tweaks - Android Auto General

After reading a few threads, I see that these units are actually knock offs of other units. Me being me, I am not happy with the bugginess of Eonon's stock firmware. Since technically, this is a standard double din Android 6.0 unit, which firmwares could I use? The screen is just extra, so I know that doesn't affect anything. THX

I just ordered today, how is din working, please give feedback thanks

yellaboyla said:
After reading a few threads, I see that these units are actually knock offs of other units. Me being me, I am not happy with the bugginess of Eonon's stock firmware. Since technically, this is a standard double din Android 6.0 unit, which firmwares could I use? The screen is just extra, so I know that doesn't affect anything. THX
Click to expand...
Click to collapse
No, not a single one of these units are "knock offs", there are also no "standard" Android headunits, there are many different types.
Eonon have no firmware, they are not manufacturers they are sellers, they sell lots of units from different manufacturers, without knowing what unit youre talking about no one can help, the MCU version will tell you and us what unit youre talking about.
Read the wiki in my signature for more info on MTCB/C/D headunits.

here it is..thx!!

yellaboyla said:
here it is..thx!!
Click to expand...
Click to collapse
Its not an MTC headunit due to the lack of "MTC" in the MCU field, looks like a new Tegra3 unit.
Thread has been moved from the MTCB headunits forum to the general forum, I would search this forum for more info, theres probably a thread (more likely several) for your unit in there.

Looking. Pickings are sparce on this unit

yellaboyla said:
Looking. Pickings are sparce on this unit
Click to expand...
Click to collapse
You may be better of changing the title of the thread to "Help Identifying Tegra3 Headunit" or something - Eonon are simply sellers and they wont be the only people selling these, so more people are likely to respond with that title.

koti said:
I just ordered today, how is din working, please give feedback thanks
Click to expand...
Click to collapse
Missed your post. Did you get it?

typos1 said:
You may be better of changing the title of the thread to "Help Identifying Tegra3 Headunit" or something - Eonon are simply sellers and they wont be the only people selling these, so more people are likely to respond with that title.
Click to expand...
Click to collapse
Yea, I just figured this out. Will do. I found the main thread on this unit. Now to figure out the rest. Having problems getting phoenixloader to create my SDCARD image. I am rooted, and I need to remove EONON's junk firmware.

Allwinner seems to be the forerunner on keeping updates on their unit flying. EXACT SAME AS EONON
https://forum.xda-developers.com/an...nroad-c1067106a3-allwinner-quad-core-t3565236
Allwinner firmware links
https://yadi.sk/d/07ru92rb3HEh73/Allwinner T3_P3

yellaboyla said:
Yea, I just figured this out. Will do. I found the main thread on this unit. Now to figure out the rest. Having problems getting phoenixloader to create my SDCARD image. I am rooted, and I need to remove EONON's junk firmware.
Click to expand...
Click to collapse
I ve already told you that there is no such thing as "Eonon firmware" - Eonon are just retailers, the firmware they gave you will be from the manufacturer.
yellaboyla said:
Allwinner seems to be the forerunner on keeping updates on their unit flying. EXACT SAME AS EONON
https://forum.xda-developers.com/an...nroad-c1067106a3-allwinner-quad-core-t3565236
Allwinner firmware links
https://yadi.sk/d/07ru92rb3HEh73/Allwinner T3_P3
Click to expand...
Click to collapse
Allwinner are a cpu manufacturer, they dont make any units, there are lots of manufacturers making units with Allwinner chips and any firmware will come from manufacturers of those units, but you cant just bang any ANY Allwinner firmware you have to make sure that its for your unit type . . . which it definitely isnt because you have a unit with an Nvidia Tegra3 cpu, so it aint gonna help.
Also Eonon retail units from lots of manufacturers so you have to specify what unit is the "exact same as Eonon" - Eonon also sell MTCB, MTCC and MTCD head units, so saying "the exact same as Eonon" really doesnt make sense.

typos1 said:
I ve already told you that there is no such thing as "Eonon firmware" - Eonon are just retailers, the firmware they gave you will be from the manufacturer.
Allwinner are a cpu manufacturer, they dont make any units, there are lots of manufacturers making units with Allwinner chips and any firmware will come from manufacturers of those units, but you cant just bang any ANY Allwinner firmware you have to make sure that its for your unit type . . . which it definitely isnt because you have a unit with an Nvidia Tegra3 cpu, so it aint gonna help.
Also Eonon retail units from lots of manufacturers so you have to specify what unit is the "exact same as Eonon" - Eonon also sell MTCB, MTCC and MTCD head units, so saying "the exact same as Eonon" really does'nt make sense.
Click to expand...
Click to collapse
OK. I think it is semantics. Regardless of who actually manufactures these units, they come from 1 place. I understand Allwinner and Eonon are just resellers.
I wouldn't have referenced the thread if I wasn't sure it matched my unit. I used HARDWARE INFO from the PlayStore and my unit is exactly the same as the 1 in the thread, down to the resolution settings.
The unit can be loaded with any firmware that is coded for the T3, as long as the components are the same. I am a Network Admin. The same goes with pcs and servers. Dell builds them (IBM Compatible), and you can load Novell, Windows, Linux, VMWARE, etc on them. The software just has to be coded for the CPU and the hardware.
I will have it done today, with the steps.............

yellaboyla said:
OK. I think it is semantics. Regardless of who actually manufactures these units, they come from 1 place. I understand Allwinner and Eonon are just resellers.
I wouldn't have referenced the thread if I wasn't sure it matched my unit. I used HARDWARE INFO from the PlayStore and my unit is exactly the same as the 1 in the thread, down to the resolution settings.
The unit can be loaded with any firmware that is coded for the T3, as long as the components are the same. I am a Network Admin. The same goes with pcs and servers. Dell builds them (IBM Compatible), and you can load Novell, Windows, Linux, VMWARE, etc on them. The software just has to be coded for the CPU and the hardware.
I will have it done today, with the steps.............
Click to expand...
Click to collapse
No its not semantics, they DO NOT come from 1 place at all, thats total nonsense.
No app on the playstore will give you the full hardware info of the mobo and the components, they can ONLY give you the hardware info of the Android SoM, this is an Android car stereo we re talking about not a phone or a tablet or a pc, things are very different and if youre not careful you will brick your unit.
Allwinner IS NOT a reseller, Allwinner is a chip manufacturer, but just cos a unit has an Allwinner chip doesnt mean you can bung any Allwinner firmware on it.
Sure some headunit types can take firmware from different manufacturers, such as the MTCB/C families and MTCD families, you need to check for your unit.
If you think that Dell builds all pcs you are seriously mistaken.

My info from HARDWAREINFO
Allwinner T3
System (Android 6.0.1)
Model t3
Manufacturer Allwinner
Device t3-p3
Product t3_p3
Brand Allwinner
Android Version 6.0.1
API Level 23
Build ID MMB29M
Fingerprint Allwinner/t3_p3/t3-p3:6.0.1/MMB29M/20170607:eng/test-keys
Display (1024x600)
Size 1024x600
Refresh Rate 60 Hz
Default Orientation Landscape
Physical Size 7.42" (18.84 cm)
Logical Size Large
Density 160 dpi (Medium)
Pixels Per Inch X: 160; Y: 160
Processor (ARMv7)
Processor ARMv7 Processor rev 5 (v7l)
Cores 4
Max Frequency 1200 Mhz
Instruction Sets armeabi-v7a, armeabi
SIMD Instructions NEON
Memory (1768 MB)
System RAM 1768 MB
JVM Max Memory 192 MB
Internal Storage 3967 MB
External Storage 8297 MB (Emulated)
Back Camera
Back Camera
Back Camera
Back Camera
Back Camera (0.3 megapixel)
Summary
Max Picture Size 720x480
Zoom 3x
Autofocus Not supported
Orientation 0°
Picture
Cancel_continuous_picture False
Continuous Picture Path
Is_continuous_picture_fast False
Picture Format Jpeg
Picture Format Values Jpeg
Picture Mode Normal
Picture Size 640x480
Picture Size Values 720x480
Preview
Preview Format Yuv420sp
Preview Format Values Yuv420sp, Yuv420p
Preview Fps Range 5000, 60000
Preview Fps Range Values (5000, 60000)
Preview Frame Rate 30
Preview Frame Rate Values 30
Preview Size 640x480
Preview Size Values 720x480
Preview_capture Size Height 480
Preview_capture Size Width 640
Video
Preferred Preview Size For Video 720x480
Video Frame Format Yuv420sp
Video Size 640x480
Video Size Values 720x480
Video Snapshot Supported True
Focus
Focus Areas (0, 0, 0, 0, 0)
Focus Distances 0.10, 1.20, Infinity
Focus Mode Fixed
Focus Mode Values Fixed
Zoom
Max Zoom 100
Smooth Zoom Supported False
Zoom 0
Zoom Ratios 100, 102, 104, 106, 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, 128, 130, 132, 134, 136, 138, 140, 142, 144, 146, 148, 150, 152, 154, 156, 158, 160, 162, 164, 166, 168, 170, 172, 174, 176, 178, 180, 182, 184, 186, 188, 190, 192, 194, 196, 198, 200, 202, 204, 206, 208, 210, 212, 214, 216, 218, 220, 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, 242, 244, 246, 248, 250, 252, 254, 256, 258, 260, 262, 264, 266, 268, 270, 272, 274, 276, 278, 280, 282, 284, 286, 288, 290, 292, 294, 296, 298, 300
Zoom Supported True
Exposure compensation
Exposure Compensation 0
Exposure Compensation Step 0
Max Exposure Compensation 0
Min Exposure Compensation 0
Misc
Camera Hal Version 3000130327_V1.0
Capture Format 825382478
Capture Size Height 480
Capture Size Width 640
Focal Length 3.43
Horizontal View Angle 51.2
Jpeg Quality 95
Jpeg Thumbnail Height 240
Jpeg Thumbnail Quality 90
Jpeg Thumbnail Size Values 320x240, 0x0
Jpeg Thumbnail Width 320
Max Num Detected Faces Hw 15
Max Num Detected Faces Sw 0
Prop Facing Back
Prop Orientation 0
Recording Hint False
Rotation 0
Snap Path
Vertical View Angle 39.4
Back Camera
Back Camera
Back Camera (0.3 megapixel)
Summary
Max Picture Size 720x480
Zoom 3x
Autofocus Not supported
Orientation 0°
Picture
Cancel_continuous_picture False
Continuous Picture Path
Is_continuous_picture_fast False
Picture Format Jpeg
Picture Format Values Jpeg
Picture Mode Normal
Picture Size 720x480
Picture Size Values 720x480
Preview
Preview Format Yuv420sp
Preview Format Values Yuv420sp, Yuv420p
Preview Fps Range 5000, 60000
Preview Fps Range Values (5000, 60000)
Preview Frame Rate 30
Preview Frame Rate Values 30
Preview Size 720x480
Preview Size Values 720x480
Preview_capture Size Height 480
Preview_capture Size Width 720
Video
Preferred Preview Size For Video 720x480
Video Frame Format Yuv420sp
Video Size 720x480
Video Size Values 720x480
Video Snapshot Supported True
Focus
Focus Areas (0, 0, 0, 0, 0)
Focus Distances 0.10, 1.20, Infinity
Focus Mode Fixed
Focus Mode Values Fixed
Zoom
Max Zoom 100
Smooth Zoom Supported False
Zoom 0
Zoom Ratios 100, 102, 104, 106, 108, 110, 112, 114, 116, 118, 120, 122, 124, 126, 128, 130, 132, 134, 136, 138, 140, 142, 144, 146, 148, 150, 152, 154, 156, 158, 160, 162, 164, 166, 168, 170, 172, 174, 176, 178, 180, 182, 184, 186, 188, 190, 192, 194, 196, 198, 200, 202, 204, 206, 208, 210, 212, 214, 216, 218, 220, 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, 242, 244, 246, 248, 250, 252, 254, 256, 258, 260, 262, 264, 266, 268, 270, 272, 274, 276, 278, 280, 282, 284, 286, 288, 290, 292, 294, 296, 298, 300
Zoom Supported True
Exposure compensation
Exposure Compensation 0
Exposure Compensation Step 0
Max Exposure Compensation 0
Min Exposure Compensation 0
Misc
Camera Hal Version 3000130327_V1.0
Capture Format 825382478
Capture Size Height 480
Capture Size Width 720
Focal Length 3.43
Horizontal View Angle 51.2
Jpeg Quality 95
Jpeg Thumbnail Height 240
Jpeg Thumbnail Quality 90
Jpeg Thumbnail Size Values 320x240, 0x0
Jpeg Thumbnail Width 320
Max Num Detected Faces Hw 15
Max Num Detected Faces Sw 0
Prop Facing Back
Prop Orientation 0
Recording Hint False
Rotation 0
Snap Path
Vertical View Angle 39.4
OpenGL 1.1 (Mali-400 MP2)
General
Renderer Mali-400 MP2
Version OpenGL ES-CM 1.1
Vendor ARM
Limits
Texture Size 4096x4096
Texture Units 8
Viewport Size 4096x4096
Modelview Stack Depth 32
Projection Stack Depth 32
Texture Stack Depth 32
Lights 8
Compressed Texture Formats
ETC1, Paletted
Extensions
GL_EXT_debug_marker GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_matrix_get GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_point_size_array GL_OES_point_sprite GL_OES_texture_npot GL_OES_vertex_array_object GL_OES_query_matrix GL_OES_matrix_palette GL_OES_extended_matrix_palette GL_OES_compressed_ETC1_RGB8_texture GL_EXT_compressed_ETC1_RGB8_sub_texture GL_OES_EGL_image GL_OES_draw_texture GL_OES_depth_texture GL_OES_packed_depth_stencil GL_EXT_texture_format_BGRA8888 GL_OES_framebuffer_object GL_OES_stencil8 GL_OES_depth24 GL_ARM_rgba8 GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_rgb8_rgba8 GL_EXT_multisampled_render_to_texture GL_OES_texture_cube_map GL_EXT_discard_framebuffer GL_EXT_robustness GL_OES_depth_texture_cube_map GL_OES_vertex_half_float GL_KHR_debug GL_OES_mapbuffer
OpenGL 2.0 (Mali-400 MP2)
General
Renderer Mali-400 MP2
Version OpenGL ES 2.0
Vendor ARM
GLSL Version OpenGL ES GLSL ES 1.00
Limits
Texture Size 4096x4096
Texture Units 8
Vertex Textures 0
Combined Textures 8
Viewport Size 4096x4096
Renderbuffer Size 4096x4096
Cubemap Size 4096x4096
Vertex Attributes 16
Vertex Uniforms 256
Varying Vectors 12
Fragment Uniforms 256
Vertex Numeric Precision
Int [-2^24, 2^24]
Float [-2^127, 2^127], 2^-23
Fragment Numeric Precision
Low Int [-2^11, 2^11]
Medium Int [-2^11, 2^11]
High Int Not available
Low Float [-2^15, 2^15], 2^-10
Medium Float [-2^15, 2^15], 2^-10
High Float Not available
Compressed Texture Formats
ETC1
Extensions
GL_EXT_debug_marker GL_OES_texture_npot GL_OES_vertex_array_object GL_OES_compressed_ETC1_RGB8_texture GL_EXT_compressed_ETC1_RGB8_sub_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 GL_ARM_shader_framebuffer_fetch GL_ARM_shader_framebuffer_fetch_depth_stencil GL_OES_mapbuffer
Graphic Modes (RGBA 32bit)
RGB 16bit (565)
RGB 16bit (565), Depth 24bit, Stencil 8bit
RGB 16bit (565), Depth 24bit, Stencil 8bit, Samples x4
RGB 16bit (565), Depth 24bit, Stencil 8bit, Samples x16, Non-Conformant
RGB 32bit (888)
RGB 32bit (888), Depth 24bit
RGB 32bit (888), Depth 24bit, Stencil 8bit
RGB 32bit (888), Depth 24bit, Stencil 8bit, Samples x4
RGB 32bit (888), Depth 24bit, Stencil 8bit, Samples x4, Non-Conformant
RGB 32bit (888), Depth 24bit, Stencil 8bit, Samples x16, Non-Conformant
RGBA 32bit (8888)
RGBA 32bit (8888), Depth 24bit, Stencil 8bit
RGBA 32bit (8888), Depth 24bit, Stencil 8bit
RGBA 32bit (8888), Depth 24bit, Stencil 8bit
RGBA 32bit (8888), Depth 24bit, Stencil 8bit
RGBA 32bit (8888), Depth 24bit, Stencil 8bit, Samples x4
RGBA 32bit (8888), Depth 24bit, Stencil 8bit, Samples x4
RGBA 32bit (8888), Depth 24bit, Stencil 8bit, Samples x16, Non-Conformant
Sensors (1)
Temperature sensor
Vendor AW.
Range 125.0°C
Resolution 1.0°C
Power 0.35 mA
Delay On Trigger
Codecs (43)
OMX.google.mp3.decoder
Media type: audio/mpeg
OMX.google.amrnb.decoder
Media type: audio/3gpp
OMX.google.amrwb.decoder
Media type: audio/amr-wb
OMX.google.aac.decoder
Media type: audio/mp4a-latm
OMX.google.g711.alaw.decoder
Media type: audio/g711-alaw
OMX.google.g711.mlaw.decoder
Media type: audio/g711-mlaw
OMX.google.vorbis.decoder
Media type: audio/vorbis
OMX.google.opus.decoder
Media type: audio/opus
OMX.google.raw.decoder
Media type: audio/raw
OMX.google.aac.encoder
Media type: audio/mp4a-latm
OMX.google.amrnb.encoder
Media type: audio/3gpp
OMX.google.amrwb.encoder
Media type: audio/amr-wb
OMX.google.flac.encoder
Media type: audio/flac
OMX.google.gsm.decoder
Media type: audio/gsm
OMX.allwinner.video.decoder.avc
Media type: video/avc
Color Formats: YUV420Flexible
Profiles: Baseline(1, 11, 12, 13, 1b, 2, 21, 22, 3, 31, 32, 4, 41, 42, 5, 51) Main(1, 11, 12, 13, 1b, 2, 21, 22, 3, 31, 32, 4, 41, 42, 5, 51) High(1, 11, 12, 13, 1b, 2, 21, 22, 3, 31, 32, 4, 41, 42, 5, 51)
OMX.allwinner.video.decoder.hevc
Media type: video/hevc
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.mjpeg
Media type: video/jpeg
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.mpeg1
Media type: video/mpeg1
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.mpeg2
Media type: video/mpeg2
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.mpeg4
Media type: video/mp4v-es
Color Formats: YUV420Flexible
Profiles: Simple(0, 0b, 1, 2, 3, 4, 4a, 5) AdvancedSimple(0, 0b, 1, 2, 3, 4, 5)
OMX.allwinner.video.decoder.h263
Media type: video/3gpp
Color Formats: YUV420Flexible
Profiles: Baseline(10, 20, 30, 40, 45, 50, 60, 70)
OMX.allwinner.video.decoder.vp6
Media type: video/x-vnd.on2.vp6
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.vp8
Media type: video/x-vnd.on2.vp8
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.vc1
Media type: video/wvc1
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.msmpeg4v1
Media type: video/x-ms-mpeg4v1
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.msmpeg4v2
Media type: video/x-ms-mpeg4v2
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.divx
Media type: video/divx
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.xvid
Media type: video/xvid
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.s263
Media type: video/flv1
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.rxg2
Media type: video/rvg2
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.wmv1
Media type: video/wmv1
Color Formats: YUV420Flexible
OMX.allwinner.video.decoder.wmv2
Media type: video/wmv2
Color Formats: YUV420Flexible
OMX.allwinner.video.encoder.avc
Media type: video/avc
Color Formats: YUV420Flexible YUV420SemiPlanar
Profiles: Baseline(1, 11, 12, 13, 1b, 2, 21, 22, 3, 31, 41, 42, 5, 51) Main(1, 11, 12, 13, 1b, 2, 21, 22, 3, 31, 32, 4, 41, 42, 5, 51) High(1, 11, 12, 13, 1b, 2, 21, 22, 3, 31, 32, 4, 41, 42, 5, 51)
OMX.google.mpeg4.decoder
Media type: video/mp4v-es
Color Formats: YUV420Flexible
Profiles: Simple(0, 0b, 1, 2, 3)
OMX.google.h263.decoder
Media type: video/3gpp
Color Formats: YUV420Flexible
Profiles: Baseline(10, 20, 30, 45) ISWV2(10, 20, 30, 45)
OMX.google.h264.decoder
Media type: video/avc
Color Formats: YUV420Flexible
Profiles: Baseline(0x10000, 1, 11, 12, 13, 1b, 2, 21, 22, 3, 31, 32, 4, 41, 42, 5, 51) Main(0x10000, 1, 11, 12, 13, 1b, 2, 21, 22, 3, 31, 32, 4, 41, 42, 5, 51) High(0x10000, 1, 11, 12, 13, 1b, 2, 21, 22, 3, 31, 32, 4, 41, 42, 5, 51)
OMX.google.hevc.decoder
Media type: video/hevc
Color Formats: YUV420Flexible
Profiles: 0x1(0x1, 0x10, 0x100, 0x1000, 0x10000, 0x4, 0x40, 0x400, 0x4000)
OMX.google.vp8.decoder
Media type: video/x-vnd.on2.vp8
Color Formats: YUV420Flexible
OMX.google.vp9.decoder
Media type: video/x-vnd.on2.vp9
Color Formats: YUV420Flexible
OMX.google.h263.encoder
Media type: video/3gpp
Color Formats: YUV420Flexible YUV420Planar YUV420SemiPlanar
Profiles: Baseline(45)
OMX.google.h264.encoder
Media type: video/avc
Color Formats: YUV420Flexible YUV420Planar YUV420SemiPlanar
Profiles: Baseline(1, 11, 12, 13, 1b, 2, 21, 22, 3, 31, 32, 4, 41) Main(1, 11, 12, 13, 1b, 2, 21, 22, 3, 31, 32, 4, 41)
OMX.google.mpeg4.encoder
Media type: video/mp4v-es
Color Formats: YUV420Flexible YUV420Planar YUV420SemiPlanar
Profiles: Core(2)
OMX.google.vp8.encoder
Media type: video/x-vnd.on2.vp8
Color Formats: YUV420Flexible YUV420Planar YUV420SemiPlanar
Profiles: Main(Version0, Version1, Version2, Version3)
Features (38)
Graphics
OpenGL 2.0
Android Hardware
android.hardware.audio.output
android.hardware.bluetooth
android.hardware.bluetooth_le
android.hardware.camera
android.hardware.camera.any
android.hardware.camera.front
android.hardware.ethernet
android.hardware.faketouch
android.hardware.location
android.hardware.location.gps
android.hardware.location.network
android.hardware.microphone
android.hardware.screen.landscape
android.hardware.screen.portrait
android.hardware.sensor.accelerometer
android.hardware.sensor.ambient_temperature
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
android.software.app_widgets
android.software.backup
android.software.connectionservice
android.software.device_admin
android.software.home_screen
android.software.input_methods
android.software.live_wallpaper
android.software.midi
android.software.sip
android.software.sip.voip
android.software.verified_boot
android.software.voice_recognizers
android.software.webview
Created with Hardware Info 4.2.6

yellaboyla said:
My info from HARDWAREINFO
Click to expand...
Click to collapse
Bit of an unnecessarily long post.
No info on the MCU which is what it important for head units. As I said, no hardware info app can tell you anything about the MCU side of things.

Would you please get off my post. I am uploading information for others that may want to know. As I research it, I am allowed to upload it here. I don't recall asking you to weigh in every time I post. For anyone that HAS this unit, I will continue to update as I get further in the process. Feel free to ask or post, as the forum ALLOWS.
typos1 said:
Bit of an unnecessarily long post.
No info on the MCU which is what it important for head units. As I said, no hardware info app can tell you anything about the MCU side of things.
Click to expand...
Click to collapse

MCU info
VW(T5.3.19, CONFIG, RDS, BC6, NODVD, 1DIN FZ, Rohms37XXX, TEF66BX

yellaboyla said:
Would you please get off my post. I am uploading information for others that may want to know. As I research it, I am allowed to upload it here. I don't recall asking you to weigh in every time I post. For anyone that HAS this unit, I will continue to update as I get further in the process. Feel free to ask or post, as the forum ALLOWS.
Click to expand...
Click to collapse
yellaboyla said:
MCU info
VW(T5.3.19, CONFIG, RDS, BC6, NODVD, 1DIN FZ, Rohms37XXX, TEF66BX
Click to expand...
Click to collapse
You asked for help, I gave it, you didnt ask for help from anyone except from me, with an attitude like that I m not sure you ll get much help from anyone, I have helped you and you are rude, unbelievable. BTW I have not broken any rules, but you have - the one that says you need to be courteous.
As I said before you need to go through the threads in the Android Headunits General forum to try and find people with similar units.

Geez.....I am just trying to find on general information about my head unit. I thanked u with points on your help. It seems you are more concerned about correcting me, than helping. That is what's rubbing me the wrong way. Even when I posted my hard info, you called my post LONG.
So to be clear;
Manufacturer is ALLWINNER
Resellers are EONON, BONROAD, SILVERSTRONG (so far)
Unit is not MTCB, MTCC, or MTCD
Got rushed to ER Friday in A FIB. Just got my heart rhythm back. Post more later.
typos1 said:
You asked for help, I gave it, you didnt ask for help from anyone except from me, with an attitude like that I m not sure you ll get much help from anyone, I have helped you and you are rude, unbelievable. BTW I have not broken any rules, but you have - the one that says you need to be courteous.
As I said before you need to go through the threads in the Android Headunits General forum to try and find people with similar units.
Click to expand...
Click to collapse

yellaboyla said:
Geez.....I am just trying to find on general information about my head unit. I thanked u with points on your help. It seems you are more concerned about correcting me, than helping. That is what's rubbing me the wrong way. Even when I posted my hard info, you called my post LONG.
So to be clear;
Manufacturer is ALLWINNER
Resellers are EONON, BONROAD, SILVERSTRONG (so far)
Unit is not MTCB, MTCC, or MTCD
Got rushed to ER Friday in A FIB. Just got my heart rhythm back. Post more later.
Click to expand...
Click to collapse
Sorry to hear of your illness.
I m still trying to help and I m the only one, you cant identify your unit on the processor alone, you need the MCU as well, lots of units use Allwinner processors but if they use different MCUs then they are different incompatible units. The sellers are really not relevant. And as I have said before the manufacturer is NOT Allwinner, they just make the processor, they do not make the unit, their chips are used in many different devices, tablets, TV boxes, head units etc.
No one has come forward to say exactly what unit you have, so this is why I keep suggesting that you go through threads in the general section to see if there are threads about your unit to help you identify it.

Related

I noticed that some people have set their touch priority to relatively high values, I am not sure if this is the intent, but lower values actually raise the priority (although if you go too low, bad things can happen).
Here is some info:
>>>>
The priority system has 256 Priority Levels numbered 0 (zero) through 255. Priority level 0 is the highest priority level. The original eight priority levels for Windows CE 2.12 are mapped to levels 248 through 255.
Applications and device drivers should use the CeGetThreadPriority and CeSetThreadPriority APIs, instead of the legacy APIs, GetThreadPriority and SetThreadPriority. The legacy APIs are still available with the same interfaces as before, but those APIs have access to only the original eight priority levels.
The priority level system is divided into four ranges. The following table shows these ranges.
Levels Description
0 through 96
Reserved for real-time above drivers.
97 through 152
Used by the default Windows Mobile device drivers.
153 through 247
Reserved for real-time below drivers.
248 through 255
Mapped to non-real-time priorities.
The following table shows the default priority levels that are associated with device drivers. You can override these values by changing the source code for the drivers or by setting values in the registry. The registry paths in the table assume that the root Drivers key is HKEY_LOCAL_MACHINE\Drivers\BuiltIn; the registry uses hexadecimal values for the priority levels.
Decimal priority Hexadecimal priority Device driver Override
99
0x63
Power Manager resume thread
HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Power\ResumePriority256
100
0x64
USB Function
None
101, also uses +1 and -1 relative priorities
0x65, also uses +1 and -1 relative priorities
USB OHCD
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\OHCI\Priority256
101, also uses +1, +3, +5 and +7 relative priorities
0x65, also uses +1, +3, +5, and +7 relative priorities
USB UHCD
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\UHCI\Priority256
103
0x67
Serial
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial\Priority256
105, also uses +1 and +2 relative priorities
0x69, also uses +1 and +2 relative priorities
PCMCIA
HKEY_LOCAL_MACHINE\Drivers\PCMCIA\Priority256
109
0x6D
Touch
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch\Priority256
110, also uses +2 and +4 relative priorities
0x6E, also uses +2 and +4 relative priorities
IRSIR
HKEY_LOCAL_MACHINE\Comm\Irsir1\Parms\Priority256
116, also uses +2, +4, +6, +8, +10 and +12 relative priorities
0x74, also uses +2, +4, +6, +8, +10, and +12 relative priorities
NDIS
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\NDIS\Priority256
131
0x83
KITL
Override in the OEM Application Layer
. In OEMInit, set g_dwKITLThreadPriority (extern DWORD) to the desired priority before calling KitlInit.
131
0x83
VMINI
HKEY_LOCAL_MACHINE\Comm\VMini\Priority256
132
0x84
CxPort
HKEY_LOCAL_MACHINE\Comm\Cxport\Priority256
145
0x91
PS/2 Keyboard
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\KEYBD\Priority256
148
0x94
IR Comm
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\IrComm\Priority256
150
0x96
TAPI (Unimodem)
HKEY_LOCAL_MACHINE\Drivers\Unimodem\Priority256
210
0xD2
WaveDev
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev\Priority256
248
0xF8
PM (Power Manager)
HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Power\Priority256
249
0xF9
PS/2 Mouse
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\MOUSE\Priority256
249
0xF9
Power Manager device registration thread
HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Power\PnPPriority256
249
0xF9
Power Manager system management thread
HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Power\SystemPriority256
249
0xF9
Power Manager activity timer thread
HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Power\TimerPriority256
250
0xFA
WaveAPI
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WAPIMAN\Priority256
251
0xFB
Power Manager battery monitor thread
HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Power\PowerPollPriority256
Remarks
Threads in Normal (as apposed to Privileged) applications can use thread priorities 248 through 255.
Threads in Privileged applications can use any thread priority.

hi... i have a problem.
i download the 1080p mp4 video from youtube, and copy to my o2x. But it cant played with HW or HW+ decoding (i using MX player). i tried many new ics bootloader rom. ex : django KOB, aroma, miuJB. but all of them not support HW/HW+ decoding to file what i downloaded before. i remember, when i use old bootloader with official cwm10, i have no problem to play 1080p video...
please,what should i do? only SW decoder could play that 1080p format,and it damn laggy
ps: sorry for my bad english

the new bootloader ics have not supported the 1080p video.. it only works on gb and froyo,. not yet time for ics..

vEget7 said:
the new bootloader ics have not supported the 1080p video.. it only works on gb and froyo,. not yet time for ics..
Click to expand...
Click to collapse
ok... i must back to old bootloader :crying:

i already at old bootloader and have installed miu JB for old bootloader.
but it just the same. and what make me confuse is , i have 2 1080p mp4 video. first is play with smooth on my o2x use HW acc. but the another one cant play with HW, just SW.
here the video detil that i can play smooth with HW :
C:\Users\okta\Downloads\Video\Tegra_genesis_hd_demo_1080p.mp4
General
Complete name : C:\Users\okta\Downloads\Video\Tegra_genesis_hd_demo_1080p.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42
File size : 89.9 MiB
Duration : 1mn 14s
Overall bit rate mode : Variable
Overall bit rate : 10.1 Mbps
Encoded date : UTC 2010-12-11 02:29:27
Tagged date : UTC 2010-12-11 02:29:27
Writing library : Apple QuickTime
Video #1
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : No
Format settings, ReFrames : 2 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 1mn 14s
Bit rate mode : Variable
Bit rate : 10.0 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 fps
Standard : Component
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.161
Stream size : 88.7 MiB (99%)
Language : English
Encoded date : UTC 2010-12-11 02:29:27
Tagged date : UTC 2010-12-11 02:29:27
Audio #2
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 1mn 14s
Bit rate mode : Variable
Bit rate : 128 Kbps
Maximum bit rate : 132 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 44.1 KHz
Compression mode : Lossy
Stream size : 1.14 MiB (1%)
Language : English
Encoded date : UTC 2010-12-11 02:29:27
Tagged date : UTC 2010-12-11 02:29:27
and this video ,i cant play with HW. whats wrong?
C:\Users\okta\Downloads\Video\The Script - Hall of Fame ft. will.i.am - YouTube.mp4
General
Complete name : C:\Users\okta\Downloads\Video\The Script - Hall of Fame ft. will.i.am - YouTube.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42
File size : 119 MiB
Duration : 3mn 52s
Overall bit rate mode : Variable
Overall bit rate : 4 270 Kbps
Encoded date : UTC 2012-08-21 01:04:26
Tagged date : UTC 2012-08-21 01:04:26
gsst : 0
gstd : 233105
gssd : B76626F04HH1355206059542239
gshh : r1---sn-2uuxa3vh-jb3d.c.youtube.com
Video #1
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : Yes
Format settings, ReFrames : 1 frame
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 3mn 52s
Bit rate : 4 076 Kbps
Maximum bit rate : 7 241 Kbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.082
Stream size : 113 MiB (95%)
Tagged date : UTC 2012-08-21 01:04:27
Audio #2
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 3mn 52s
Bit rate mode : Variable
Bit rate : 192 Kbps
Maximum bit rate : 202 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 44.1 KHz
Compression mode : Lossy
Stream size : 5.33 MiB (4%)
Title : IsoMedia File Produced by Google, 5-11-2011
Encoded date : UTC 2012-08-21 01:04:27
Tagged date : UTC 2012-08-21 01:04:27

If you would use google, you can find everywhere hw decode possibilities of Tegra 2. It supporsts only baseline profile with 1080p and baseline, medium and some hightprofile of 720p video, but no all high. It depends on settings when you encode the video.

tomsi91 said:
If you would use google, you can find everywhere hw decode possibilities of Tegra 2. It supporsts only baseline profile with 1080p and baseline, medium and some hightprofile of 720p video, but no all high. It depends on settings when you encode the video.
Click to expand...
Click to collapse
Right, the playable video is [email protected], but the not working one is [email protected]
Either
-reencode the video to [email protected] (I think even [email protected] should work)
-redownload a smaller video
-or get tegra 3+ ^^

oktagun said:
ok... i must back to old bootloader :crying:
Click to expand...
Click to collapse
I wouldnt downgrade just for watching 1080p vids on your tv or 2x or whatever. :sly:
Sent from my LG-P990 using xda premium

ergosum said:
Right, the playable video is [email protected], but the not working one is [email protected]
Either
-reencode the video to [email protected] (I think even [email protected] should work)
-redownload a smaller video
-or get tegra 3+ ^^
Click to expand...
Click to collapse
yep you absolutely right. i re-encode with [email protected] . and 1080p video run smoothly

oktagun said:
yep you absolutely right. i re-encode with [email protected] . and 1080p video run smoothly
Click to expand...
Click to collapse
What program you use to re-encode video to low profile?
Sent from my LG O2X using DM 1.7.1

asmerito said:
What program you use to re-encode video to low profile?
Sent from my LG O2X using DM 1.7.1
Click to expand...
Click to collapse
Gom video converter. Make sure u use bitrate and resolusion like the original video. So u will get video with same size ,resolution, and quality :good:

uh..
the best our o2x can do is playing High Profile 4.0 720p
1080p must be baseline

squall0833 said:
uh..
the best our o2x can do is playing High Profile 4.0 720p
1080p must be baseline
Click to expand...
Click to collapse
yep... i think so...

Has anyone tried 3rd party video recording apps to get higher bitrate 4k video recording on an LE s2 or S3 like the X626?
I know these do 4k recording out of the box, but bitrate is low , probably no more than 35Mbps.
There are 3rd party apps....free with limited recording time....
Cinema 4k
Lumio Cam (switch to pro mode) free but limited recording time...
Wondering if the above apps can do at least 100Mbit 4k recording mode at 30FPS.
Anyone? Thanks

poog said:
Has anyone tried 3rd party video recording apps to get higher bitrate 4k video recording on an LE s2 or S3 like the X626?
I know these do 4k recording out of the box, but bitrate is low , probably no more than 35Mbps.
There are 3rd party apps....free with limited recording time....
Cinema 4k
Lumio Cam (switch to pro mode) free but limited recording time...
Wondering if the above apps can do at least 100Mbit 4k recording mode at 30FPS.
Anyone? Thanks
Click to expand...
Click to collapse
Try opencamera 1.40 or below versions.
mediainfo:
4k video recording on x520
Code:
General
Complete name : VID_20171130_180558.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (isom/mp42)
File size : 236 MiB
Duration : 20 s 458 ms
Overall bit rate : 96.8 Mb/s
Encoded date : UTC 2017-11-30 10:06:19
Tagged date : UTC 2017-11-30 10:06:19
com.android.version : 7.1.2
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : [email protected]@Main
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 19 s 777 ms
Source duration : 20 s 10 ms
Bit rate : 98.4 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Rotation : 90°
Frame rate mode : Variable
Frame rate : 29.285 FPS
Minimum frame rate : 3.736 FPS
Maximum frame rate : 30.769 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Bits/(Pixel*Frame) : 0.405
Stream size : 232 MiB (98%)
Source stream size : 235 MiB (100%)
Title : VideoHandle
Language : English
Encoded date : UTC 2017-11-30 10:06:19
Tagged date : UTC 2017-11-30 10:06:19
mdhd_Duration : 19777
Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : mp4a-40-2
Duration : 20 s 458 ms
Bit rate mode : Constant
Bit rate : 156 kb/s
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 390 KiB (0%)
Title : SoundHandle
Language : English
Encoded date : UTC 2017-11-30 10:06:19
Tagged date : UTC 2017-11-30 10:06:19
mdhd_Duration : 20458

Here's an example:
Let me know if you'd need the original MP4 video file (13.5 MB).
Here's the file info.:
Code:
General
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (isom/mp42)
File size : 13.5 MiB
Duration : 2 s 762 ms
Overall bit rate : 41.1 Mb/s
com.android.version : 9
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings : 1 Ref Frames
Format settings, CABAC : No
Format settings, Reference fra : 1 frame
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 2 s 762 ms
Source duration : 2 s 761 ms
Bit rate : 38.6 Mb/s
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 228.904 FPS
Minimum frame rate : 114.213 FPS
Maximum frame rate : 236.220 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.183
Stream size : 12.7 MiB (94%)
Source stream size : 12.7 MiB (94%)
Title : VideoHandle
mdhd_Duration : 2762
Codec configuration box : avcC
Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 2 s 688 ms
Bit rate mode : Constant
Bit rate : 192 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 63.3 KiB (0%)
Title : SoundHandle

Any ideas, ladies and gentlemen?

King Mustard said:
Any ideas, ladies and gentlemen?
Click to expand...
Click to collapse
My S7 would do this if I just copied the raw file across, I had to export the slow-mo from the phones video editor and copy that across to have it play in slow mo on PC
EDIT -Doesn't seem to be the case with the P30, just made a Slo-Mo and copied it directly over and it played in slo-mo on the PC fine

*Detection* said:
My S7 would do this if I just copied the raw file across, I had to export the slow-mo from the phones video editor and copy that across to have it play in slow mo on PC
EDIT -Doesn't seem to be the case with the P30, just made a Slo-Mo and copied it directly over and it played in slo-mo on the PC fine
Click to expand...
Click to collapse
The P30 Pro must have just created a corrupted video file.

During playback of your slow-mo vid on your phone, press the burger menu (3 dot button) on the upper right corner; then at the bottom, there is an option saying SAVE SLOW-MO FILE, just click that and save the video

Although this does (once again) highlight the irksome reality of Huawei's slow motion only being 240fps and not the 960fps claimed... *sigh*

Is this a Mistake from DevCheck softwere or My phone is not an orginal phone?
I have Mi 9t pro with 48MP primary Cam and 20Mp selfie but I check that with DevCheck application and I confused!!
See This Exported INFO:
Code:
DevCheck Report
Xiaomi
Mi 9T Pro
Nov 25, 2019 12:26
Uptime: 1d 17h 45m 27s
Deep sleep: 14h 53m 54s (35%)
HARDWARE
Qualcomm Technologies, Inc SM8150
Cores: 8
null
null
Frequencies:
300 MHz - 1785 MHz
710 MHz - 2419 MHz
Governor: schedutil
GRAPHICS
Vendor: Qualcomm
GPU: Adreno (TM) 640
OpenGL: OpenGL ES 3.2 [email protected] ([email protected], I3763001aef) (Date:03/07/19)
Resolution: 2340 x 1080
Screen density: 403.95105 ppi
Screen size: 6.38 in / 162 mm
RAM
RAM size: 6.0 GB
OTHER HARDWARE
Bluetooth support: yes
Bluetooth LE support: yes
USB host support: yes
Infrared transmitter: no
NFC support: yes
DEVICE
Model: Mi 9T Pro
Codename: raphael
Manufacturer: Xiaomi
Serial Number: b333c815
SYSTEM
Android Version: 9 (Android P)
Build: PKQ1.181121.001
MIUI: V10.3.1.0.PFKMIXM
Security patch: July 1, 2019
Architecture: aarch64 (64-bit)
Instruction sets: arm64-v8a armeabi-v7a armeabi
Kernel: 4.14.83-perf-g86c91b91
BATTERY
Technology: Li-poly
Health: Good
Capacity (reported by system): 4000 mAh
NETWORK
MAC address: E0:DC:FF:EC:B3:9B
5GHz band support: no
Operator: IR-MCI
Phone type: GSM
Dual SIM: yes
CAMERA
Resolution: 12.0 MP (4000x3000)
Focal length: 4.77 mm
35mm equivalent focal length: 25.8 mm
Sensor size: 6.40x4.80 mm
Crop factor: 5.4x
Field of view: 67.7°
Pixel size: 1.60 μm
Aperture: 1.75
Focus modes: infinity, auto, macro, continuous-video, continuous-picture
Flash modes: off, auto, on, torch, red-eye
ISO sensitivity range: 100-12800
RAW capable: yes
Image format: JPEG
Front Camera: 5.0 MP (2592x1940)

Don't worry, you are probably fine.
The Mi 9T's main and selfie camera are so called Quad Bayer sensors. That means they can shoot either in max resolution (48/20MP) when you want maximum detail, or when the lighting isn't good they can combine four neighbouring pixels into one "big pixel", effectively creating a lower resolution but more sensitive sensor.
For some reason, Xiaomi only supports the lower resolution, more sensitive camera modes in the standard android Camera2 API, which is the system that other apps (like your DevCheck) can use to access the camera. The higher-res modes are implemented in some proprietary way so that only the stock camera app can use them.