Hi,
I compiled AOSP 4.1 for mako/Neuxs4 so I can apply MIUI-patchrom(if it works) and we'll have MIUIv4.
I can't test it because I still don't have a Nexus4 so you have todo that for me.
Download:
http://d-h.st/Kwj
Installation:
- wipe data and cache
- It's an otapackage which should be installed via Recovery(should work with CWM, too).
Note: For testing purposes only - please do an backup before and tell me if it boots and if something doesn't work.
I'm subscribing to this badboy!
if no risk of bricking, i would test it
and do i need to flash gapps too?
chiensibut said:
if no risk of bricking, i would test it
and do i need to flash gapps too?
Click to expand...
Click to collapse
Yes no gapps in rom
oppsss bad new, bootloop!
@m11kkaa Can I ask why you want use patchwork. This method don't work on Gs3 or in new phone. Can you light my mind?
chiensibut said:
oppsss bad new, bootloop!
Click to expand...
Click to collapse
logcat would be nice. adb should be enabled because it's a userdebug build.
acer73 said:
@m11kkaa Can I ask why you want use patchwork. This method don't work on Gs3 or in new phone. Can you light my mind?
Click to expand...
Click to collapse
Because the porting method is technically very dirty(even if it works).
And with a Nexus there shouldn't be any conflicts patching framework because it uses stock unmodified AOSP.
itching for some miui4 love for the n4
Any news about the ongoing work? Just curious, not asking for eta but just if it's being worked on and any issues we can perhaps identify and try to solve.
Sent from my Nexus 4 using Tapatalk 2
I would LOVE miui on this device.. :thumbup:
Sent from my Nexus 4
I still don't have the device and nobody gave me logcat
I think when I'll get the device official MIUI 4.1 will be already out
m11kkaa said:
I still don't have the device and nobody gave me logcat
I think when I'll get the device official MIUI 4.1 will be already out
Click to expand...
Click to collapse
I'll do it later today.
Sent from my Nexus 4 using xda premium
Naimand said:
I'll do it later today.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I was going to do it right now, then I stopped, because our device runs 4.2 (or 4.2.1) and so did you make a port of an earlier version?
Just asking, because my guess is that MIUI doesn't yet support 4.2, which is why we'd have to port it onto a 4.1 ROM?
Also, it says OTA, is this a full ROM or does it need to be flashed over something else?
Thanks!
Official MIUI can't come fast enough.
Sent from my Nexus 4 using xda app-developers app
m11kkaa said:
I still don't have the device and nobody gave me logcat
I think when I'll get the device official MIUI 4.1 will be already out
Click to expand...
Click to collapse
Do you still need that logcat
---------- Post added at 08:28 PM ---------- Previous post was at 08:06 PM ----------
[/COLOR]
m11kkaa said:
I still don't have the device and nobody gave me logcat
I think when I'll get the device official MIUI 4.1 will be already out
Click to expand...
Click to collapse
Check your pm's.
Thanks, I'm waiting for your good news
i have nexus4 %& i will test your rom
i hope everything will be ok~
Miui on this device... I can only imagine how beast that would be
Sent from my Nexus 4 using xda premium
xxMAGICxx said:
Miui on this device... I can only imagine how beast that would be
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Any news on this?
Sent from my Nexus 4 using Tapatalk 2
The problem was, that there are missing hardware-parts.
But it's complicated to compile the new projects with old AOSP because there changed very much in kernel and libs.
I need more time for this.
m11kkaa said:
The problem was, that there are missing hardware-parts.
But it's complicated to compile the new projects with old AOSP because there changed very much in kernel and libs.
I need more time for this.
Click to expand...
Click to collapse
I guess it's easier to port miui to the latest kernel instead...
Porting backwards feels wrong!
/Edit: Tried porting this to cm10.1 but got bootloop.
But at least i've seen a taste of miui (the bootscreen)
Error is:
...
12-20 05:42:41.534: D/MDnsDS(5154): Going to poll with pollCount 1
12-20 05:42:46.029: I/ServiceManager(156): service 'media.audio_flinger' died
12-20 05:42:46.029: I/ServiceManager(156): service 'media.player' died
12-20 05:42:46.029: I/ServiceManager(156): service 'media.camera' died
12-20 05:42:46.029: I/Netd(5375): Netd 1.0 starting
12-20 05:42:46.039: W/InterfaceController(5375): Warning (Cannot load library: load_library(linker.cpp:747): library "/system/lib/libnetcmdiface.so" not found) while opening the net interface command library
12-20 05:42:46.149: I/mediaserver(5374): ServiceManager: 0x40b63ee8
12-20 05:42:46.149: I/AudioFlinger(5374): Using default 3000 mSec as standby time.
12-20 05:42:46.149: I/CameraService(5374): CameraService started (pid=5374)
12-20 05:42:46.159: I/QCameraHAL(5374): Handle base =0x0x40dad064
12-20 05:42:46.159: I/QCameraHAL(5374): getCameraInfo: numOfCameras = 2
12-20 05:42:46.159: I/QCameraHAL(5374): Handle [0]=0x0x40dad064
12-20 05:42:46.159: I/QCameraHAL(5374): Camera sensor 0 info:
12-20 05:42:46.159: I/QCameraHAL(5374): camera_id: 0
12-20 05:42:46.159: I/QCameraHAL(5374): modes_supported: 1
12-20 05:42:46.159: I/QCameraHAL(5374): position: 0
12-20 05:42:46.159: I/QCameraHAL(5374): sensor_mount_angle: 90
12-20 05:42:46.159: I/QCameraHAL(5374): Handle [1]=0x0x40dad0a8
12-20 05:42:46.159: I/QCameraHAL(5374): Camera sensor 1 info:
12-20 05:42:46.159: I/QCameraHAL(5374): camera_id: 1
12-20 05:42:46.159: I/QCameraHAL(5374): modes_supported: 1
12-20 05:42:46.159: I/QCameraHAL(5374): position: 1
12-20 05:42:46.159: I/QCameraHAL(5374): sensor_mount_angle: 270
12-20 05:42:46.159: I/AudioPolicyManagerBase(5374): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
12-20 05:42:46.159: D/AudioHardwareALSA(5374): hw_get_module(ALSA_HARDWARE_MODULE_ID) returned err 0
12-20 05:42:46.159: D/AudioHardwareALSA(5374): AudioHardware: DLOPEN successful for ACDBLOADER
12-20 05:42:46.159: D/ACDB-LOADER(5374): ACDB -> ACDB_CMD_INITIALIZE
12-20 05:42:46.159: E/(5374): [ACDB RTC]->rtc init done!->result [0]
12-20 05:42:46.159: E/Diag_Lib(5374): actp_diag_init: call diag init function with 40AB6EB5
12-20 05:42:46.159: E/(5374): [ACDB ACPH]->actp diag init done!
12-20 05:42:46.159: D/ACDB-LOADER(5374): No existing ION info in ACDB driver
12-20 05:42:46.159: D/ACDB-LOADER(5374): ACDB -> ION_IOC_ALLOC
12-20 05:42:46.159: D/ACDB-LOADER(5374): ACDB -> ION_IOC_SHARE
12-20 05:42:46.169: D/ACDB-LOADER(5374): ACDB -> MMAP ADDR
12-20 05:42:46.169: D/ACDB-LOADER(5374): ACDB -> register MEM to ACDB driver: 0x40dae000
12-20 05:42:46.169: D/ACDB-LOADER(5374): ACDB -> send_asm_topology
12-20 05:42:46.169: D/ACDB-LOADER(5374): ACDB -> ACDB_CMD_GET_AUDPROC_STREAM_TOPOLOGY_ID
12-20 05:42:46.169: D/ACDB-LOADER(5374): send mbhc data
12-20 05:42:46.179: D/ACDB-LOADER(5374): send tabla anc data
12-20 05:42:46.179: D/ACDB-LOADER(5374): ACDB -> ACDB_CMD_GET_ANC_SETTING
12-20 05:42:46.179: E/ACDB-LOADER(5374): done with conversion, anc config size is 148
12-20 05:42:46.179: D/ACDB-LOADER(5374): ACDB -> ACDB_CMD_GET_ANC_SETTING
12-20 05:42:46.179: E/ACDB-LOADER(5374): done with conversion, anc config size is 148
12-20 05:42:46.179: D/ACDB-LOADER(5374): ACDB -> ACDB_CMD_GET_ANC_SETTING
12-20 05:42:46.179: E/ACDB-LOADER(5374): done with conversion, anc config size is 148
12-20 05:42:46.179: D/ACDB-LOADER(5374): ACDB -> ACDB_CMD_GET_ANC_SETTING
12-20 05:42:46.179: E/ACDB-LOADER(5374): done with conversion, anc config size is 148
12-20 05:42:46.179: D/ACDB-LOADER(5374): ACDB -> ACDB_CMD_GET_ANC_SETTING
12-20 05:42:46.179: E/ACDB-LOADER(5374): done with conversion, anc config size is 74
12-20 05:42:46.179: D/ACDB-LOADER(5374): ACDB -> ACDB_CMD_GET_ANC_SETTING
12-20 05:42:46.179: E/ACDB-LOADER(5374): done with conversion, anc config size is 74
12-20 05:42:46.179: D/ACDB-LOADER(5374): ACDB -> init done!
12-20 05:42:46.179: D/AudioHardwareALSA(5374): AudioHardware: DLOPEN successful for CSD CLIENT
12-20 05:42:46.179: I/ALSAModule(5374): void android_audio_legacy::s_set_csd_handle(void*) csd_handle: 0x401e028c
12-20 05:42:46.179: D/alsa_ucm(5374): Single config file format detected
12-20 05:42:46.299: I/AudioHardwareALSA(5374): ucm instance opened: 1087144840
12-20 05:42:46.299: I/AudioFlinger(5374): loadHwModule() Loaded primary audio interface from QCOM Audio HW HAL (audio) handle 1
12-20 05:42:46.299: D/AudioHardwareALSA(5374): openOutputStream: Lowlatency Output
12-20 05:42:46.299: D/ALSAModule(5374): s_route: devices 0x2 in mode 0
12-20 05:42:46.299: D/ALSAModule(5374): switchDevice: device 2 mode:0
12-20 05:42:46.299: D/ALSAModule(5374): No valid input device: 0
12-20 05:42:46.299: D/ALSAModule(5374): switchDevice,rxDev:Speaker, txDevnull), curRxDev:None, curTxDev:None
12-20 05:42:46.299: D/alsa_ucm(5374): snd_use_case_set(): uc_mgr 0x40cc8388 identifier _enadev value Speaker
12-20 05:42:46.299: E/alsa_ucm(5374): Invalid current verb value: Inactive - -1
12-20 05:42:46.299: D/ALSAModule(5374): switchDevice: curTxUCMDevivce None curRxDevDevice Speaker
12-20 05:42:46.299: D/alsa_ucm(5374): snd_use_case_set(): uc_mgr 0x40cc8388 identifier _verb value HiFi Lowlatency
12-20 05:42:46.299: D/alsa_ucm(5374): Set mixer controls for Speaker enable 1
12-20 05:42:46.299: D/ACDB-LOADER(5374): ACDB -> send_afe_cal
12-20 05:42:46.299: D/alsa_ucm(5374): Set mixer controls for HiFi Lowlatency enable 1
12-20 05:42:46.299: D/ALSAModule(5374): Device value returned is hw:0,14
12-20 05:42:46.309: D/ALSAModule(5374): setHardwareParams: reqBuffSize 1024 channels 2 sampleRate 48000
12-20 05:42:46.309: D/ALSAModule(5374): setHardwareParams: buffer_size 2048, period_size 1024, period_cnt 2
12-20 05:42:46.309: I/AudioFlinger(5374): HAL output buffer size 256 frames, normal mix buffer size 1024 frames
12-20 05:42:46.309: I/AudioMixer(5374): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
12-20 05:42:46.309: E/MonoPipe(5374): Failed to fetch local time frequency when constructing a MonoPipe (res = -32). getNextWriteTimestamp calls will be non-functional
12-20 05:42:46.569: D/MDnsDS(5375): MDnsSdListener::Hander starting up
12-20 05:42:46.569: D/MDnsDS(5375): MDnsSdListener starting to monitor
12-20 05:42:46.569: D/MDnsDS(5375): Going to poll with pollCount 1
...
Click to expand...
Click to collapse
It seems it's something with the sound driver. probably some api changed in 4.2... :/
/Edit: Lol and added the blurry image proove that prooves nothing. That's a must-have on any cutting-edge thread around here.
Related
Has anyone had issues playing videos in recent CM roms? Somewhere between android 1.5 and 1.6 files I've encoded with below broke. While sound plays, the video output is blank:
Code:
mencoder "$2" -o "$2.tmp.mp4" -vf dsize=480:352:2,scale=-8:-8,harddup -oac faac -faacopts mpeg=4:object=2:raw:br=128 -of lavf -lavfopts format=mp4 -ovc x264 -x264encopts bframes=0:bitrate=512:threads=auto:global_header
ffmpeg -i "$2.tmp.mp4" -vcodec copy -acodec copy "$2.and.mp4"
I've checked and it's not the ramhack patch, and it's been tried on multiple players. Oddly a short video ripped from youtube works. I think it's an android 1.5 -> 1.6 change that requires new encoder lines. Can someone post mencoder/ffmpeg/etc commands that produce videos playable in a recent rom?
Logcat output from a failed attempt.
Code:
11-30 08:10:16.625 I/ActivityManager( 331): Start proc com.android.camera for activity com.android.camera/.MovieView: pid=1202 uid=10021 gids={1006, 1015, 2001, 3003}
11-30 08:10:21.515 I/ActivityManager( 331): Displayed activity com.android.camera/.MovieView: 5089 ms (total 5089 ms)
11-30 08:10:21.905 W/QCvdec ( 315): vdec: Creating H264 Decoder [0x9fae0]
11-30 08:10:21.905 W/QCvdec ( 315): vdec: NAL lenght [0]
11-30 08:10:21.905 W/QCvdec ( 315): vdec: START CODE....
11-30 08:10:21.975 W/ADSP_RTOS_SVC( 315): VDL_QDSP_rtos_event_cb
11-30 08:10:21.975 W/ADSP_RTOS_SVC( 315): VDL_QDSP_rtos_event_cb
11-30 08:10:23.066 W/AudioFlinger( 315): write blocked for 83 msecs
11-30 08:10:32.765 W/WindowManager( 331): Key dispatching timed out sending to com.android.camera/com.android.camera.MovieView
11-30 08:10:32.765 W/WindowManager( 331): Dispatch state: {{KeyEvent{action=1 code=66 repeat=0 meta=0 scancode=28 mFlags=8} to Window{43baf640 org.connectbot/org.connectbot.ConsoleActivity paused=false} @ 1259568605596 lw=Window{43baf640 org.connectbot/org.connectbot.ConsoleActivity paused=false} [email protected] fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{43afca90 com.android.camera/com.android.camera.MovieView paused=false}}}
11-30 08:10:32.775 W/WindowManager( 331): Current state: {{null to Window{43afca90 com.android.camera/com.android.camera.MovieView paused=false} @ 1259568632775 lw=Window{43afca90 com.android.camera/com.android.camera.MovieView paused=false} [email protected] fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{43afca90 com.android.camera/com.android.camera.MovieView paused=false}}}
11-30 08:10:34.255 I/ActivityManager( 331): ANR in process: com.android.camera (last in com.android.camera)
11-30 08:10:34.255 I/ActivityManager( 331): Annotation: keyDispatchingTimedOut
11-30 08:10:34.255 I/ActivityManager( 331): CPU usage:
11-30 08:10:34.255 I/ActivityManager( 331): Load: 4.83 / 4.41 / 3.88
11-30 08:10:34.255 I/ActivityManager( 331): CPU usage from 17087ms to 3261ms ago:
11-30 08:10:34.255 I/ActivityManager( 331): mediaserver: 58% = 39% user + 19% kernel / faults: 1703 minor 61 major
[snip: nothing useful]
11-30 08:10:34.835 I/Process ( 331): Sending signal. PID: 1202 SIG: 3
11-30 08:10:34.865 I/dalvikvm( 1202): threadid=7: reacting to signal 3
11-30 08:10:35.035 I/Process ( 331): Sending signal. PID: 331 SIG: 3
11-30 08:10:35.035 I/dalvikvm( 331): threadid=7: reacting to signal 3
[snip:more of the last line]
11-30 08:10:38.965 W/WindowManager( 331): Continuing to wait for key to be dispatched
11-30 08:10:44.245 W/WindowManager( 331): Key dispatching timed out sending to com.android.camera/com.android.camera.MovieView
11-30 08:10:44.255 W/WindowManager( 331): Dispatch state: {{KeyEvent{action=1 code=66 repeat=0 meta=0 scancode=28 mFlags=8} to Window{43baf640 org.connectbot/org.connectbot.ConsoleActivity paused=false} @ 1259568605596 lw=Window{43baf640 org.connectbot/org.connectbot.ConsoleActivity paused=false} [email protected] fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{43b0c3b8 Panel:com.android.camera/com.android.camera.MovieView paused=false}}}
11-30 08:10:44.255 W/WindowManager( 331): Current state: {{null to Window{43afca90 com.android.camera/com.android.camera.MovieView paused=false} @ 1259568644259 lw=Window{43afca90 com.android.camera/com.android.camera.MovieView paused=false} [email protected] fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{43b0c3b8 Panel:com.android.camera/com.android.camera.MovieView paused=false}}}
11-30 08:10:45.485 I/WindowManager( 331): WIN DEATH: Window{43adbe58 com.android.browser/com.android.browser.BrowserActivity paused=false}
11-30 08:10:50.045 I/ActivityManager( 331): Start proc com.android.bugreport for broadcast com.android.bugreport/.BugReportReceiver: pid=1213 uid=10034 gids={1007, 1015}
11-30 08:10:50.275 I/ActivityManager( 331): Process com.android.browser (pid 673) has died.
11-30 08:10:50.675 W/WindowManager( 331): Continuing to wait for key to be dispatched
11-30 08:10:50.675 W/WindowManager( 331): No window to dispatch pointer action 1
11-30 08:10:52.125 I/ActivityManager( 331): Killing process com.android.camera (pid=1202) at user's request
You sure that that *ever* worked? I think I tried something like that once and got the same result as you. And this would have been an older version of android, probably 1.0 or 1.1. As far as I can tell, the only limitation is the decoder chip itself -- the android version shouldn't make any difference.
Anyway, this should work: (notice the -x264encopts...)
Code:
mencoder "$2" -o "$2.tmp.mp4" -vf dsize=480:352:2,scale=-8:-8,harddup -oac faac -faacopts mpeg=4:object=2:raw:br=128 -of lavf -lavfopts format=mp4 -ovc x264 -x264encopts nocabac:level_idc=30:bframes=0:bitrate=512:global_header:threads=auto:subq=5:frameref=6:partitions=all:trellis=1:chroma_me:me=umh
lbcoder said:
You sure that that *ever* worked? I think I tried something like that once and got the same result as you. And this would have been an older version of android, probably 1.0 or 1.1. As far as I can tell, the only limitation is the decoder chip itself -- the android version shouldn't make any difference.
Anyway, this should work: (notice the -x264encopts...)
Code:
mencoder "$2" -o "$2.tmp.mp4" -vf dsize=480:352:2,scale=-8:-8,harddup -oac faac -faacopts mpeg=4:object=2:raw:br=128 -of lavf -lavfopts format=mp4 -ovc x264 -x264encopts nocabac:level_idc=30:bframes=0:bitrate=512:global_header:threads=auto:subq=5:frameref=6:partitions=all:trellis=1:chroma_me:me=umh
Click to expand...
Click to collapse
No dice, the video is still black. Which rom / device have you used this with? If CM, did you merge in the HTC recovery?
Fyi I've tried videos encoded and sucessfully played in earlier roms, still black...so either something broke in the decoder chip driver, the chip itself is kaput or there's a setting somewhere causing this.
Fnorder said:
No dice, the video is still black. Which rom / device have you used this with? If CM, did you merge in the HTC recovery?
Fyi I've tried videos encoded and sucessfully played in earlier roms, still black...so either something broke in the decoder chip driver, the chip itself is kaput or there's a setting somewhere causing this.
Click to expand...
Click to collapse
I wouldn't go near a CM-mod. Too slow/unstable/unreliable/broken. Try a stock ADP1 image. That line I gave you will *definitely* give you a compatible video.
I've problem watching TV :
Video starts, works , stops, start again .. many times and at the end i get a b lack screen
logcat just before last stop :
E/QCvdec ( 151): Flush VDL_stats_q: stats_ptr 0xcfb50
E/QCOmxcore( 151): OMXCORE API : Free Handle ccc6c
E/QCOmxcore( 151): Unloading the dynamic library for OMX.qcom.video.decoder.avc
E/MediaPlayer( 535): internal/external state mismatch corrected
Note : i get this problem with all 2.1 ROM i tried , but it works with Modaco 3.2
Tkx for help
A+
Jpq
Hey all,
Upon no search results, this thread was created. I'm on team tiamat 1.1 and I cannot use any of my THD games like galaxy on fire and fruit ninja. I am wondering if the kernal broke this, but I do not know.
If this thread is in the wrong place, than please move it.
I did a log at and copied everything relating to fruit ninja fc here:
07-23 11:48:01.080 E/InputDispatcher( 152): channel '4108aa58 com.halfbrick.fruitninjathd/com.halfbrick.fruitninja.FruitNinjaActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x8
07-23 11:48:01.080 E/InputDispatcher( 152): channel '4108aa58 com.halfbrick.fruitninjathd/com.halfbrick.fruitninja.FruitNinjaActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
07-23 11:48:01.080 I/ActivityManager( 152): Process com.halfbrick.fruitninjathd (pid 28934) has died.
07-23 11:48:01.080 I/WindowManager( 152): WIN DEATH: Window{41b60f30 SurfaceView paused=false}
07-23 11:48:01.080 I/WindowManager( 152): WIN DEATH: Window{4108aa58 com.halfbrick.fruitninjathd/com.halfbrick.fruitninja.FruitNinjaActivity paused=false}
07-23 11:48:01.090 I/WindowManager( 152): WINDOW DIED Window{4108aa58 com.halfbrick.fruitninjathd/com.halfbrick.fruitninja.FruitNinjaActivity paused=false}
Thanx all!
-craby1925
Sent from my Xoom using Tapatalk
[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
Hi all. Faced with some audio streaming problems in my app when AA activated. I see that AA can research some services for work. From logs:
Code:
CAR.GAL.GAL: Found services:
CAR.GAL.GAL: Service id=1 type=InputSourceService { keycodes=[1,2,3,4,5,6,19,20,21,22,23,84,85,87,88,127,] { touchscreen width=800 height=480 }}
CAR.GAL.GAL: Service id=2 type=SensorSourceService {sensors=[type=13,type=10,] locationCharacterization=null fuelType=[] evConnectorType=[]}
CAR.GAL.GAL: Service id=3 type=MediaSinkService { codec type=MEDIA_CODEC_VIDEO_H264_BP { codecResolution=VIDEO_800x480 widthMargin=null heightMargin=null density=160}}
CAR.GAL.GAL: Service id=6 type=MediaSinkService { codec type=MEDIA_CODEC_AUDIO_PCM audioStreamType=AUDIO_STREAM_SYSTEM_AUDIO { samplingRate=16000 numBits=16 channels=1}}
CAR.GAL.GAL: Service id=4 type=MediaSourceService { codec type=MEDIA_CODEC_AUDIO_PCM samplingRate=16000 numBits=16 channels=1}
CAR.GAL.GAL: Service id=9 type=MediaPlaybackService
CAR.GAL.GAL: Service id=10 type=NavigationStatusService { minimumIntervalMs=250 type=1 height=64 width=64 colourDepthBits=16 }
CAR.SETUP.SERVICE: Got car info nli[dbId=0,manufacturer=Google,model=Desktop Head
If Head Unit is sink for audio, than MediaSinkService with type AUDIO_STREAM_SYSTEM_AUDIO creates, otherwise doesn't. Like in this logs:
Code:
D/CAR.GAL.GAL: Found services:
D/CAR.GAL.GAL: Service id=1 type=InputSourceService { keycodes=[1,2,3,4,5,6,19,20,21,22,23,84,85,87,88,127,] { touchscreen width=800 height=480 }}
D/CAR.GAL.GAL: Service id=2 type=SensorSourceService {sensors=[type=13,type=10,] locationCharacterization=null fuelType=[] evConnectorType=[]}
D/CAR.GAL.GAL: Service id=3 type=MediaSinkService { codec type=MEDIA_CODEC_VIDEO_H264_BP { codecResolution=VIDEO_800x480 widthMargin=null heightMargin=null density=160}}
D/CAR.GAL.GAL: Service id=6 type=MediaSinkService { codec type=MEDIA_CODEC_AUDIO_PCM audioStreamType=AUDIO_STREAM_SYSTEM_AUDIO { samplingRate=16000 numBits=16 channels=1}}
D/CAR.GAL.GAL: Service id=4 type=MediaSourceService { codec type=MEDIA_CODEC_AUDIO_PCM samplingRate=16000 numBits=16 channels=1}
D/CAR.GAL.GAL: Service id=9 type=MediaPlaybackService
D/CAR.GAL.GAL: Service id=10 type=NavigationStatusService { minimumIntervalMs=250 type=1 height=64 width=64 colourDepthBits=16 }
Maybe someone knows that is it possible to create or implement service with AUDIO_STREAM_SYSTEM_AUDIO and manage audio stream?
Or is it possible get access to Android system's audio stream in my app?