Database Users

Beyond XBMC 3.4

{
"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"
}
Beta 3.4
Updated librtmp.so to make more streams work (Thanks RedPenguin).
Changed default OSD button to Play/Pause instead of Subtitles.
Updated all Addons.
Hopefully Fixed Controller settings in OUYA version.
Minor Bug Fixes.
Beta 3.3
Updated Common Plugin Cache to hopefully fix the few having problems.
Updated Metadata TheMovieDB plugin.
Beta 3.2
Removed build.prop check completely (Thanks kandilak).
Fixed some remote control key bindings on non-standard remotes (Thanks alexagr).
Updated SuperRepo.
Added Fanart Slideshow option to Screensavers.
Removed Language button from OSD keyboard. It will be back in Gotham.
Brought back OpenGL Spectrum Visualization as an option.
Beta 3.1
Fixed missing dependencies.
Updated Subtitles.
Beta 3
Here is a list of some of the changes since Beta 2.9.
Fusion, Xfinity and Mashup sources are included by default. SuperRepo also included.
1Channel, Much Movies HD and Youtube are preinstalled and configured. I have included my own proxy to get around the 1Channel block in the UK, just select it from the 1Channel settings if you need it.
Lyrics, Subtitles, XBMC Backup, Missing Movie Scanner and Key Editor are installed and configured.
Main screen now has the Karaoke option and also has the Karaoke plugin installed and set up.
Option to use MX Player as the playback device in context menu (Local and Streams only, SMB does not work)
Family screen will now have main menu plus 2 sub menus (Animation and HD Family) which will auto populate as you add your Movies. The main Family menu contains only Family and Animation Genres, the Animation sub menu contains only Animation Genre and the HD Family sub menu contains only HD films of Family and Animation Genres.
Videos will only show the needed sub menus as sources are added to the Library(Movies, TVShows, etc).
Pictures now has a Slideshow sub menu and links to the backgrounds folder as an example.
The default layouts of each Window have been altered to use what looks best in my own opinion. You can set what you want afterwards.
Music Playback will now animate fanart automatically once you have some.
New cache settings which hopefully will be more compatible for everyone.
Update all addons.
Various other tweaks and changes.
Beta 2
Ok, here we go. Quite a few fixes and I have not had time to fully test all of it.
Fixed remote control movement in on screen keyboard.
Fixed context menu on long click of mouse/airmouse.
Added Fusion and Xfinity.
Changed RssFeed to BBC World News.
Changed Icons.
Changed Music Wallpaper.
Added Keymap Editor to Programs.
Added advancedsettings for cache.
Updated all addons.
Various other bug fixes.
Beta 1
Hardware Decoding
Mouse wheel support
New Graphics (Not finished yet)
A fully customizable version of Confluence skin as default. All other skins removed. (If you want it faster then enable minimum spec option in skin settings)
Audio offset by 250 ms to fix audio lag.
SuperRepo Included.
All addons brought up to date.
Install Instructions
Just install it like any other APK now with whatever build.prop you like.
If 720P does not work for you then this is not meant for your hardware. It was tested on RockChip Devices but appears to work on a lot of others.
Launcher version is only for roms that don't have a system bar. Auto hide function in any rom hides everything except anything classed as a launcher so it will show system bar if used on a normal rom. You could always rename SystemUI.apk to SystemUI.old and it will remove the bar completely but I don't advise it unless you know what you are doing.
It takes a long time on first run (about 2 minutes) while it sets everything up. The screen will go black and then it will go thru a few backgrounds, Just wait it out. It will launch normally after the first time.
If you find that the Interface it too slow on your device then go to Skin Settings and under "General" click on "Enable Minimum Specifications Settings".
Downloads
Beyond XBMC Beta 3.4
Beyond XBMC Beta 3.4 (Launcher Version)
Ouya Users
Here is a test version for OUYA users only. This should enable smooth HD playback for OUYA users where the normal version doesn't but some old SD content might not work.
Beyond XBMC Beta 3.4 (OUYA Version)
Thanks
XBMC
Koying
Mudislander
......and you guys for using my XBMC and giving me something to do. Thank you.

best xbmc ever!!

Gonna give this a try on a Mk808 (original) over the weekend...
Sent from my TF300T using Tapatalk

definitely deserves a sticky, Flumpster has put some good amount of time on it. Great app

Beyond XBMC 3.3!!
@flumpster I glad you're giving us some love with this amazing app Beyond XBMC 3.3!!,
hope more Dev from FreakTab keep coming...

el_easy said:
@flumpster I glad you're giving us some love with this amazing app Beyond XBMC 3.3!!,
hope more Dev from FreakTab keep coming...
Click to expand...
Click to collapse
I've always been on xda mate and have my own roms released here. I just post on freaktab because that's where everyone is with these stick/box's. Xda is dead with these devices.
Glad you're enjoying it mate.

flumpster said:
I've always been on xda mate and have my own roms released here. I just post on freaktab because that's where everyone is with these stick/box's. Xda is dead with these devices.
Glad you're enjoying it mate.
Click to expand...
Click to collapse
I have to say though Freaktab has a bit more freedom and tolerance level, you can get smashed up here in XDA for giving an opinion .
The sticks are going to be very Mainstream pretty soon, the Chinese manufacturers need standardize a bit and be more consistent and open. They fear being copied and yet all they do is copy around.
The overall "Android Stick Computers" may need a Freaktab moderator, that way no rights would be disturbed and a proper list of roms for devices would make it even in a single thread.

PlutoDelic said:
I have to say though Freaktab has a bit more freedom and tolerance level, you can get smashed up here in XDA for giving an opinion .
The sticks are going to be very Mainstream pretty soon, the Chinese manufacturers need standardize a bit and be more consistent and open. They fear being copied and yet all they do is copy around.
The overall "Android Stick Computers" may need a Freaktab moderator, that way no rights would be disturbed and a proper list of roms for devices would make it even in a single thread.
Click to expand...
Click to collapse
I've never been afraid to give my opinion
As for the copying going on I don't even take much notice of it. You have companies like Minix who are purposely going against GPL 2 and releasing custom versions of XBMC locked to their devices and wont supply the source code. They wouldn't get away with that on XDA for a second. The only thing I can do is inform people of their tactics and advise them against supporting them.

Problem on EVOLVEO Smart TV box Q4
Hi!
Yesterday evening i installed on my box the Beyond XBMC Beta 3.3.
On first run it seems all normaly. But if the startup process was finished and the menu appearing if i choose something the app goes black and nothing..
I waited 5 min and after i go back to home screen. try start again but only black screen.
After reboot i click on app icon it comes a black screen and immadietly close.
I can't start. Only after if i delete the user data and cache for application is possible to start again.
I try'd to "Enable Minimum Specifications Settings". One time i turned successfully this option, but after go back to menu frozen again...
Any idea?
Thankseter

iwpeter said:
Hi!
Yesterday evening i installed on my box the Beyond XBMC Beta 3.3.
On first run it seems all normaly. But if the startup process was finished and the menu appearing if i choose something the app goes black and nothing..
I waited 5 min and after i go back to home screen. try start again but only black screen.
After reboot i click on app icon it comes a black screen and immadietly close.
I can't start. Only after if i delete the user data and cache for application is possible to start again.
I try'd to "Enable Minimum Specifications Settings". One time i turned successfully this option, but after go back to menu frozen again...
Any idea?
Thankseter
Click to expand...
Click to collapse
I have absolutely no idea why it would do this for you. I have installed this on over 10 different bits of hardware and it worked on every one for me (except the amlogic playback but I knew that wouldn't work). There are loads of posts over on freaktab also and no one has brought up anything similar. The first install does take a long time and you have to wait it out but after that it should launch quick.
Lets try and find out what is different for you. What machine is it? What OS is it running? What chipset is it?

flumpster said:
Lets try and find out what is different for you. What machine is it? What OS is it running? What chipset is it?
Click to expand...
Click to collapse
Hi!
Thank You for reply.
My device based on RK3188 chip.
The official XBMC nightly is running without any problem, but i watch'd your demo video and i find your version more comfortable And i want to try because your is directly optimized for rk chipset. ;
On the about page on my device i see the following:
Model number: EVOLVEO Smart TV box Q4
Android version: 4.2.2
Kernel version: 3.0.36+ [email protected] #17 Fri Dec 13 13:53:39 CST 2013
Build number: rk31sdk-eng 4.2.2 JDQ39 eng.root.20131213.135342 test-keys
Vendor software version: RK3188_R-BOX_ANDROID4.2.2-SDK_V1.0.0_130514
Specification:
• Android 4.2.2 Jelly Bean operating system
• Quad Core 1.6 GHz ARM Cortex-A9 processor
• Quad Core 3D Mali-400 GPU
• 2 GB ram
• 8 GB built-in internal memory
• possible to extend using a microSDHC card, up to 32 GB
• built-in microphone
• built-in WiFi with enryption support
• network card for computer network compatibility, 10/100 RJ45
• built-in memory card reader
• HDMI 1.4
• Google Play support
• Miracast/DLNA support
• 2.4 GHz wireless keyboard and mouse support
• flash USB drive or external HDD support
• size 97 x 97 x 22 mm
• weight 197 g
Interface:
• microSDHC memory card reader
• 2 x USB 2.0 HOST
• HDMI
• LAN RJ45
• microUSB
• power supply input
Thank You!
Peter

iwpeter said:
Hi!
Thank You for reply.
My device based on RK3188 chip.
The official XBMC nightly is running without any problem, but i watch'd your demo video and i find your version more comfortable And i want to try because your is directly optimized for rk chipset. ;
On the about page on my device i see the following:
Model number: EVOLVEO Smart TV box Q4
Android version: 4.2.2
Kernel version: 3.0.36+ [email protected] #17 Fri Dec 13 13:53:39 CST 2013
Build number: rk31sdk-eng 4.2.2 JDQ39 eng.root.20131213.135342 test-keys
Vendor software version: RK3188_R-BOX_ANDROID4.2.2-SDK_V1.0.0_130514
Specification:
• Android 4.2.2 Jelly Bean operating system
• Quad Core 1.6 GHz ARM Cortex-A9 processor
• Quad Core 3D Mali-400 GPU
• 2 GB ram
• 8 GB built-in internal memory
• possible to extend using a microSDHC card, up to 32 GB
• built-in microphone
• built-in WiFi with enryption support
• network card for computer network compatibility, 10/100 RJ45
• built-in memory card reader
• HDMI 1.4
• Google Play support
• Miracast/DLNA support
• 2.4 GHz wireless keyboard and mouse support
• flash USB drive or external HDD support
• size 97 x 97 x 22 mm
• weight 197 g
Interface:
• microSDHC memory card reader
• 2 x USB 2.0 HOST
• HDMI
• LAN RJ45
• microUSB
• power supply input
Thank You!
Peter
Click to expand...
Click to collapse
Now that should work for you perfect. It is basically the same device as most of mine.
Which beta did you download, the normal one or the launcher version?

Hi!
The normal version.
Sent from my GT-P3110 using xda app-developers app

Hi people, I discovered this version a short time ago, and I've to say it's the best I had trying ever. I strongly recommend to all of you to try it.
But only have a doubt, I can't do the "extrafanart thing" work, I mean, while I am selecting a chapter in a TV show, show a slideshow of different fanarts... I look for in all the settings and not find how it works. Can anybody help me? I hope you can understand me... My English level is awful . Thank you all, and specially for the developer for such a great job!
Enviado desde mi GT-I9300

will beyond XBMC work (can it be installed) on a windows PC?
will beyond XBMC work (can it be installed) on a windows PC?

Another perfect work by the amazing Flumpmiester

Downloading.....

Parse error
There was a problem parsing the package.
I can not install from a TF card (I can install another apps)
Any idea?
---------- Post added at 08:05 PM ---------- Previous post was at 07:52 PM ----------
JaviR said:
Parse error
There was a problem parsing the package.
I can not install from a TF card (I can install another apps)
Any idea?
Click to expand...
Click to collapse
Reply to myself...
I connected the ZERO Devices Z4C Quattro to the computer as Massive Storage, copied the APK directly by USB and installed successfully from there.

Nice version of xbmc and lets hope this fixes my py errors in some addons.

I don't know why the official gotham version isn't up to scratch, but mate, you saved the day! The entire purpose of my buying the MK908 was to get XBMC on it. When the videos started lagging with the official version, I thought my money and efforts were wasted. But YOU SAVED THE DAY!
Any ideo how to get the media center remote working with MK908.

[MUSIC] Poweramp, Audio Tuner's alternative ?

Hello,
As some people who installed H2Os or another ROM, i was missing Audio Tuner from OOs
I know there's V4A, i tried different settings but i'm not satisfied with result,
So I heard Poweramp is testing a new build with their "new audio engine" or something like that, I sign it to try and what a good surprise !
I suggest you to try it and tell you experience with it ! :fingers-crossed:
Apk's URL :
http://forum.powerampapp.com/index.php?/files/file/21-poweramp-alpha-build-703-uniapk/&do=download&csrfKey=2d56c5db9eb0fdee00bab34719a2952b
When you install it ,
Go in Audio's settings -> Output -> Hi-Res Output (Experimental) -> Wired-Headset / Aux ON
PS : Sorry for my english :angel:

It's not a new information. Poweramp is testing alpha builds for a long now. I joined the program since their alpha v1 build (currently on v3), they announced it in /r/Android subreddit long time back. Later, there was discussions on Oneplus forums about this since OOS 3.0 beta released without audio tuner.
Poweramp is not system wide, still you can enable Hi-Res(works along with Snapdragon) plugin for good music experience with headphones. I'm using this feature whenever I'm on headphones,with customized equalizer. For system wide experience, V4A is the best until now.

Djarenga said:
Hello,
As some people who installed H2Os or another ROM, i was missing Audio Tuner from OOs
I know there's V4A, i tried different settings but i'm not satisfied with result,
So I heard Poweramp is testing a new build with their "new audio engine" or something like that, I sign it to try and what a good surprise !
I suggest you to try it and tell you experience with it ! :fingers-crossed:
Apk's URL :
http://forum.powerampapp.com/index.php?/files/file/21-poweramp-alpha-build-703-uniapk/&do=download&csrfKey=2d56c5db9eb0fdee00bab34719a2952b
When you install it ,
Go in Audio's settings -> Output -> Hi-Res Output (Experimental) -> Wired-Headset / Aux ON
PS : Sorry for my english :angel:
Click to expand...
Click to collapse
Found it
New link.
http://forum.powerampapp.com/index.php?/topic/8810-poweramp-alpha-build-703/

[KB-Article] Troubleshooting Bluetooth Issues on LineageOS 14 devices

Note: This post summarizes the experiences I had when fixing Bluetooth on the sltexx device.
Even though parts of the following are device specific some fixes may also be ported to other device overlays after testing.
Also the shared audio HAL in android_harware_samsung might be used by other devices.
Please do not use this thread to report any issues you are having on your device. This is an advisory for fellow developers only!!
Short description of known Bug Reports:
1) Some BT features are not working, such as: Receiving files, Bluetooth tethering, OBEX, etc.
Reported as: BUGBASH-653
Affects: Bluetooth.apk
Devices: Possibly all, but caused by a rare condition, port to your device if neccesary​2) The phone does not connect to cars / bt-headsets using the hands-free profile for calling
Reported as: BUGBASH-308
Affects: Bluetooth.default.so
Devices: Possibly all Devices with WBS=off in combination with bt-device relying on WBS​3) The phone connects, media working, but in-call sound is completely garbled or muted on both ends
Reported as: BUGBASH-302 / BUGBASH-264
Affects: build.prop, libbt-vendor.so, Bluetooth.default.so, audio.primary.universal5430.so
Devices:
a) Samsung devices using qualcomm HAL msm8974 (klte)
b) Samsung devices using android_hardware_samsung audio HAL (sltexx, and devices with: TARGET_AUDIOHAL_VARIANT := samsung, see list in 3rd post)
c) Samsung devices using qualcomm HAL msm89** (jfltexx)​
4) While connected to bt-headset systems sound such as volume change and ringtone are played on speaker and headset simultaneously.
Reported as: none, fixed internally
Affects: mixer_paths_0.xml
Devices: sltexx specific, maybe other Samsung behave similar​
Detailed background description and fixes in next post….

1) Description: https://jira.lineageos.org/browse/BUGBASH-653
Background: The registration of the "EMAIL Message Access" Service seems to be faulty.
The MAP: MSE MAS Email Instance Support was added to CM14.1 but not CM13!
https://github.com/LineageOS/androi...mmit/819847bb7f72a69a7d7fc662bcd37625247fceec
There is also a switch to disable all new non-aosp bt data features:
https://github.com/LineageOS/androi...mmit/96a55efb0edac3c2af523f938b338dd16d4f8ac4
However it might be useful to fix the originating issue which I assume is the SDP registration of those features: -> No one has checked this until now..
Fix: https://review.lineageos.org/#/c/177998/
2) Description: https://jira.lineageos.org/browse/BUGBASH-308
Background: The BMWs (and probably other cars also) check the available codecs first:
Code:
BTA_AG_AT_BAC_EVT /* avablable codec */
and expect the wide-band speech [WBS] profile. Because that is not enabled on compile level the BMW sends a BTA_AG_CLOSE_EVT.
The connection is terminated and phone_state_change tries to continue with an invalid idx because the SLC connection is already down.
If you look at the logcat of the motog closely, you can find the following:
Code:
bt_btif : btif_hf_upstreams_evt: event=BTA_AG_WBS_EVT
audio_hw_primary: adev_set_parameters: enter: bt_wbs=on
Therefore the build must have been compiled with: BTM_WBS_INCLUDED
Code:
#if (BTM_WBS_INCLUDED == TRUE )
#define BTA_AG_WBS_EVT 31 /* SCO codec info */
#endif
Fix: https://review.lineageos.org/#/c/177996/
NOTE: If you are experiencing mute calls or garbled incall sound after this, continue with 3a/3b depending on your device
3a) Description: Garbled /mute incall sounds on bluetooth (msm8974)
Background:
The sample rate for calls is usually 8k, however for wide-band speech it is 16k. It seems that some devices cannot handle this sample rate and will only work on WBS with 8k.
This behavior was confirmed on the klte. The fix might be ported to other devices:
Fix: https://review.lineageos.org/#/c/178371/
3b) Description: Garbled /mute incall sounds (Universal HAL)
Background: Unlike the klte, many Exynos devices have a shared audio HAL that supports 16k WBS however there was a small misuse of the sample rate constant resulting in garbled sound.
The usage of audio_hal.force_voice_config = (wide or narrow) is usually not required (add if needed)
If the fix from 3a has been applied or was previously set, remove any definitions of SCO_WBS_SAMPLERATE in the vendor config.
Fix: https://review.lineageos.org/#/c/182054/
Right now this in in testing. We are looking for more affected devices that are using android_hardware_samsung as audio HAL.
Update: See the detailed list of possible affected devices below, as far as I see all of them have not yet enabled WBS yet.
3c) Description: Garbled /mute incall sounds on bluetooth (msm89** / jfltexx)
 @jorgemiguel4 Found out what fixes the mute calls: Thanks to you!
#define BTM_WBS_INCLUDED TRUE
#define BTIF_HF_WBS_PREFERRED FALSE //With this set to TRUE there is no sound on my side.
Click to expand...
Click to collapse
This will enable WBS (for the car support) but it will use the default codec instead which does not have the WBS samplerate issue.
Therefore audio quality might not be perfect but at least it works.
4) Description: Ringer & notification sounds through headset and speaker
Background:
When pressing volume up/down buttons or on incoming calls the sound is played on both headset and speaker which seems to be an odd behaviour. This is not only for bluetooth, also for wired headsets and headphones. The issue seems to be quite old and some might say it works as designed: https://forum.xda-developers.com/showthread.php?t=2320446
However as this is a custom firmware we can change the corresponding audio routes!
Fix: https://github.com/Harinus/android_...mmit/f104a3d9775e6c6cfdfbb6e61f16b036d207c18b (will need modification for other devices)
Wrote this with my best knowledge and belief. If there is any incorrect information, please let me know.
Special thanks to @akk29, @side and everyone on webchat, gerrit and jira who provided help/logs

Collection of all TARGET_AUDIOHAL_VARIANT := samsung Devices I could find on github!
sltexx ...........Samsung Galaxy Alpha / SM-G850F....... [exynos5430]
#LineageOS/
noblelte-common ..Samsung Galaxy Note 5................. [exynos7420]
zero-common ......Samsung Galaxy S6..................... [exynos7420]
k3gxx ............Samsung Galaxy S5 / SM-G900H.......... [exynos5422]
hero-common ......Samsung Galaxy S7 Edge................ [exynos8890]
gts2-common ......Samsung Galaxy Tab S2................. [exynos5433]
#others/
klimtlte .........Samsung Galaxy Tab S 8.4 / SM-T705.... [exynos5420]
ja3gxx ...........Samsung Galaxy S4 Exynos / GT-I9500... [exynos5410]
lt033g ...........Samsung Galaxy Note 10.1 3g / SM-P601. [exynos5420]
on5xelte .........Samsung Galaxy J5 Prime....... ....... [exynos7570]
zenlte-common ....Samsung Galaxy S6 Edge +.............. [exynos7420]
chagalllte .......Samsung Galaxy Tab S 10.5 / SM-T805... [exynos5420]
chagallltetmo ....Samsung Galaxy Tab S 10.5 / SM-T807T.. [exynos5420]
j7elte ...........Samsung Galaxy J7 / SM-J700........... [exynos7580]

. The usage of audio_hal.force_voice_config = (wide or narrow) is usually not required (add if needed)
If the fix from 3a has been applied or was previously set, remove any definitions of SCO_WBS_SAMPLERATE in the vendor config.
Click to expand...
Click to collapse
On code review I read ur the discussion with shevt regarding using "audio_half.force_voice_config". So using this line in build.prop will always force hal to use wideband or narrow whichever specified OR
But removing this line I believe will allow audio hal to decide wide band or narrow based on network. I may be wrong.
When shevt removed force.voice.config I assume audio hal may be using "pcm_config_voice_sco" and not "pcm_config_voice_sco_wb" in which has been defined .rate 8000 which may be causing the problem for shevt.
I just want to understand. I have seen in pcm_config_voice_sco_wb rate defined as "SCO_WB_SAMPLING_RATE". what is value passed when you define this. Is it .rate=16000 or .rate=0?

@Harinus hope you can help me
i have same issue on BUGBASH-96 but WPS didn't fix it
i have this lines on logcat :
Code:
08-12 13:40:24.866 6824 6861 D bt_btif : A2DP-CTRL-CHANNEL EVENT UIPC_RX_DATA_READY_EVT
08-12 13:40:24.866 6824 6861 D bt_btif : a2dp-ctrl-cmd : A2DP_CTRL_CMD_START
08-12 13:40:24.866 6824 6861 W bt_btif : btif_recv_ctrl_data: A2DP command A2DP_CTRL_CMD_START while AV stream is not ready
08-12 13:40:24.866 6824 6861 D bt_btif : ## a2dp ack : A2DP_CTRL_CMD_START, status 1 ##
08-12 13:40:24.866 6824 6861 D bt_btif : a2dp-ctrl-cmd : A2DP_CTRL_CMD_START DONE
08-12 13:40:24.866 371 6892 I bt_a2dp_hw: a2dp_command: A2DP COMMAND A2DP_CTRL_CMD_START DONE STATUS 1
08-12 13:40:24.866 371 6892 E bt_a2dp_hw: a2dp_command: A2DP COMMAND A2DP_CTRL_CMD_START error 1
08-12 13:40:24.866 371 6892 E bt_a2dp_hw: start_audio_datapath: Audiopath start failed (status -1)
08-12 13:40:24.877 371 6892 I bt_a2dp_hw: start_audio_datapath: state 3
08-12 13:40:24.878 371 6892 I bt_a2dp_hw: start_audio_datapath: state AUDIO_A2DP_STATE_STOPPED
08-12 13:40:24.878 371 6892 I bt_a2dp_hw: a2dp_command: A2DP COMMAND A2DP_CTRL_CMD_START
my device tree links : https://github.com/LG-K10

@macs18max
You basically got it right.
The HAL consists of 2 parts:
android_hardware_samsung (1, audio HAL)
android_hardware_broadcom_libbt (2, bluetooth RIL)
Both must handle the sampling rate of the incoming and outgoing audio streams.
For the WBS codec both 8k and 16k are valid by specification. Other codecs may use only 8k.
1) PCM Config / force_voice_config
The audio HAL (pcm config) uses 16k for WBS (after my fix) and 8k for the other codecs.
It decides which sample rate based on the wb_amr_type that it gets from the RIL.
When setting "audio_hal.force_voice_config" it overrides the wb_amr_type and therefore the samplerate of the pcm config.
(pcm_config_voice_sco_wb or pcm_config_voice_sco)
voice_session_init registers a RIL callback for WB. That wont be registered when "audio_hal.force_voice_config" is set at all. https://github.com/LineageOS/android_hardware_samsung/blob/cm-14.1/audio/voice.c#L444
2) SCO_WBS_SAMPLE_RATE
The value is used in hw_sco_i2spcm_config https://github.com/LineageOS/android_hardware_broadcom_libbt/blob/cm-14.1/src/hardware.c#L1516 and defines the sample rate on hw layer.
The values 0 and 1 are used. -> SCO_WBS_SAMPLE_RATE is a macro, documented here: https://github.com/LineageOS/androi...bt/blob/cm-14.1/include/bt_vendor_brcm.h#L262
3) Conclusion.
From what I experienced both values on RIL and HAL must be equal. Otherwise the audio will be garbled.
However some HALs (e.g. klte) seem to not support 16k, so we force 8k there.
Maybe it does not work for @ShevT without the line in build.prop because the wb-amr callback is not working properly on that device.
Can not answer that without a device for testing.
@erfanoabdi
The issue looks like something not related to WBS. Do you have a full log?

Harinus said:
@erfanoabdi
The issue looks like something not related to WBS. Do you have a full log?
Click to expand...
Click to collapse
tnx for reply
yeah, logcat attached
interested thing is i can see this error is passed by using prebuilt audio hals but still no sound :
Code:
A2DP COMMAND A2DP_CTRL_CMD_START DONE STATUS 0
i don't want to use prebuilt hals, need to find way for fixing this.

erfanoabdi said:
tnx for reply
yeah, logcat attached
interested thing is i can see this error is passed by using prebuilt audio hals but still no sound :
Code:
A2DP COMMAND A2DP_CTRL_CMD_START DONE STATUS 0
i don't want to use prebuilt hals, need to find way for fixing this.
Click to expand...
Click to collapse
The origin of the error is: https://github.com/LineageOS/android_system_bt/blob/cm-14.1/audio_a2dp_hw/audio_a2dp_hw.c#L569. android_hardware_bt is the bluetooth stack that has changed quite a lot for the last versions of android.
Your build config of the stack(https://github.com/LG-K10/android_device_lge_m216/blob/cm-14.1/bluetooth/bdroid_buildcfg.h) is using definitions that seem to be obsolete since Android M (and also Nougat)
Check the related motorola https://github.com/LineageOS/androi...mmit/69feab615584f2b8bf7f51c0fd12817181453e02 repository!
Some parameters were renamed:
Code:
BLUETOOTH_QCOM_SW -> BLUETOOTH_QTI_SW
BTC_INCLUDED -> BLE_VND_INCLUDED
The currently missing "BLE_VND_INCLUDED" enables several CTRL feature callbacks that seem to be related to: "A2DP_CTRL_CMD_START"
I suggest porting the current version from motorola with all its defines:
Code:
#define BLUETOOTH_QTI_SW TRUE
#define MAX_ACL_CONNECTIONS 7
#define MAX_L2CAP_CHANNELS 16
#define BLE_VND_INCLUDED TRUE
#define BT_CLEAN_TURN_ON_DISABLED TRUE
plus the WBS enabling..
Code:
#define BTM_WBS_INCLUDED TRUE /* Enable WBS */
#define BTIF_HF_WBS_PREFERRED TRUE /* Use WBS */
I can not guarantee that this will fix the issue, but it is surely a good idea to fix the parameters.

I posted a AOSP Bluetooth patch to the jira bugtracker under issue
https://jira.lineageos.org/browse/BUGBASH-717
And here is the xda thread where the dev built this patch...
https://forum.xda-developers.com/go...m-dark-rom-t3492150/post73199372#post73199372
...maybe helpful !?!

lulli1 said:
I posted a AOSP Bluetooth patch to the jira bugtracker under issue
https://jira.lineageos.org/browse/BUGBASH-717
And here is the xda thread where the dev built this patch...
https://forum.xda-developers.com/go...m-dark-rom-t3492150/post73199372#post73199372
...maybe helpful !?!
Click to expand...
Click to collapse
See my comment on jira.. For axon7 its clearly the WBS issue that has been described above.

On jfltexx got it working in my car with the following, hope it helps somebody
#define BTM_WBS_INCLUDED TRUE
#define BTIF_HF_WBS_PREFERRED FALSE //With this set to TRUE there is no sound on my side.
and
SCO_WBS_SAMPLE_RATE = 0 or SCO_WBS_SAMPLE_RATE = 1 //worked fine with both. 0=8Hhz and 1=16kHz

Harinus said:
See my comment on jira.. For axon7 its clearly the WBS issue that has been described above.
Click to expand...
Click to collapse
Yes you were right. Thanks a lot. We solved the issue on the Nexus 5 by setting
BTIF_HF_WBS_PREFERRED to FALSE

Using HFP several users of the herolte got distorted sound when calling. See regression 1194. The problem occurred after enabling WBS in LOS nightly. What has to be done to apply a workaround? Is it sufficient to change the build.prop? Issue is really annoying.

nostromo12 said:
Using HFP several users of the herolte got distorted sound when calling. See regression 1194. The problem occurred after enabling WBS in LOS nightly. What has to be done to apply a workaround? Is it sufficient to change the build.prop? Issue is really annoying.
Click to expand...
Click to collapse
LOS Version: lineage-14.1-20171018-nightly-herolte-signed
Baseband: G930FXXU1DQF1
Kernel version: 3.18.14-gadb2bc5
I have Samsung Galaxy S7 G930F running latest nightly and have the voice distortion issue.
audio_hal.force_voice_config = wide [This is default, I didn't change this]
---------- Post added at 01:30 PM ---------- Previous post was at 12:33 PM ----------
padraigdoran said:
LOS Version: lineage-14.1-20171018-nightly-herolte-signed
Baseband: G930FXXU1DQF1
Kernel version: 3.18.14-gadb2bc5
I have Samsung Galaxy S7 G930F running latest nightly and have the voice distortion issue.
audio_hal.force_voice_config = wide [This is default, I didn't change this]
Click to expand...
Click to collapse
I got it working on my S7 by changing to the following:
audio_hal.force_voice_config = narrow
The audio person on the other end says they can hear me fine, but I think the audio quality of the incoming voice isn't that great. The voice is very understandable, just not super clear.

I tested
audio_hal.force_voice_config = narrow
on herolte with same nightly , but older baseband G930FXXU1BPJG. But it did not work. There is absolutely silence. No dial tone. No partner voice. Nothing. I have sadly to go back to nightly 20170919.

I've got a problem with Bluetooth on my Note 4 with Lineage OS 14.1. I've paired my android wear watch with my phone and can receive notifications and data from apps on the phone, but the watch can't access the internet through the Bluetooth connection. It worked fine on my old Touchwiz ROM. Is this related to problem 1 or something else?

none of these are the problem I have, my problem is that bluetooth doesn't even turn on

@Harinus
I have got issues with Call Audio on zerofltexx (S6). We are using the common audio HAL. Well the issue is I have got a pair of Beats Solo 3 Wireless Headphones which require WBS for Calls. Media audio works great. However there is no call audio whatsoever. Now I have tried many of the fixes you mentioned in your previous posts and non have solved this issue. I have tried the prebuilt audio HAL on LineageOS and it works fine with these headphones. Even the one by @macs18max for the same device works. I will attach a log when making a call. I have BT WBS as ON but PREFERRED to FALSE when this log was taken.

LG G6
this is what bluetooth does on my LG G6: The phone connects, media working, but in-call sound is completely garbled or muted on the other end
No idea on how to fix this. Phone is rooted and has the nightly from 20180206 with the microG-Patch. Same issue with previous versions.
any help would be appreciated
thnx lemonskater

I have this exact problem...
I'm now looking for the "How To" push code or config changes to my device? In the thread, there are a couple of fixes to try, and some files... but I don't have a single clue about what to do with them, how to "install" those fixes on my LOS 15.1 Galaxy S7. Im guessing I need an app on my phone to run and apply the changes... but I didn't find exactly how to.
I'm an experienced Windows sys admin, but I'm a total N00b as when it comes to Android. I want to learn to exploit the maximum of my phone, but I gotta start by making it work normal again. Can you help me with this? I'm totally lost as how I can solve my Bluetooth problem with the thread linked a little earlier!
Thank you SOOOOO much for every bit of help you could provide me.

Fire OS 5.6.2.0 changes default camera video-recording bitrate?

I've been using my Fire 10 HD tablet to record videos of myself for a vlog. I use the front-facing camera and record segments approximately 15 minutes long. I've been doing this for a couple weeks. Usually, 10 minutes of video translates to a file of approximately 100MB.
Today I shot a video and, surprisingly, a 13 minute video consumed 1.14 GB of space - a ten-fold increase! I've changed nothing - there are no options in the Camera app for this device to adjust bitrate, resolution or fps of the front-facing camera. The only difference is that last night, my Fire tablet took an upgrade to the latest 5.6.2.0 Fire OS. I assume this has changed the system-wide bitrate for any camera capture, as the same change occurs using any other camera app from the Amazon store!
Here is some output from ffprobe. First, the video taken two days ago, showing a bitrate of 1402 kb/s:
Code:
C:\Users\grkenn\Desktop>ffmpeg-3.4.1-win64-shared\bin\ffprobe.exe VID_20180703_162653.mp4
ffprobe version 3.4.1 Copyright (c) 2007-2017 the FFmpeg developers
built with gcc 7.2.0 (GCC)
configuration: --disable-static --enable-shared --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-cuda --enable-cuvid --enable-d3d11va --enable-nvenc --enable-dxva2 --enable-avisynth --enable-libmfx
libavutil 55. 78.100 / 55. 78.100
libavcodec 57.107.100 / 57.107.100
libavformat 57. 83.100 / 57. 83.100
libavdevice 57. 10.100 / 57. 10.100
libavfilter 6.107.100 / 6.107.100
libswscale 4. 8.100 / 4. 8.100
libswresample 2. 9.100 / 2. 9.100
libpostproc 54. 7.100 / 54. 7.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'VID_20180703_162653.mp4':
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: isommp42
creation_time : 2018-07-03T21:26:53.000000Z
Duration: 00:12:38.52, start: 0.000000, bitrate: 1534 kb/s
Stream #0:0(eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p, 640x480, 1402 kb/s, SAR 1:1 DAR 4:3, 10.01 fps, 10 tbr, 90k tbn, 180k tbc (default)
Metadata:
creation_time : 2018-07-03T21:26:53.000000Z
handler_name : VideoHandle
Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 128 kb/s (default)
Metadata:
creation_time : 2018-07-03T21:26:53.000000Z
handler_name : SoundHandle
And then the one for today, showing that the new recorded bitrate is 12298 kb/s:
Code:
C:\Users\grkenn\Desktop>ffmpeg-3.4.1-win64-shared\bin\ffprobe.exe VID_20180705_152646.mp4
ffprobe version 3.4.1 Copyright (c) 2007-2017 the FFmpeg developers
built with gcc 7.2.0 (GCC)
configuration: --disable-static --enable-shared --enable-gpl --enable-version3 --enable-sdl2 --enable-bzlib --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-cuda --enable-cuvid --enable-d3d11va --enable-nvenc --enable-dxva2 --enable-avisynth --enable-libmfx
libavutil 55. 78.100 / 55. 78.100
libavcodec 57.107.100 / 57.107.100
libavformat 57. 83.100 / 57. 83.100
libavdevice 57. 10.100 / 57. 10.100
libavfilter 6.107.100 / 6.107.100
libswscale 4. 8.100 / 4. 8.100
libswresample 2. 9.100 / 2. 9.100
libpostproc 54. 7.100 / 54. 7.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'VID_20180705_152646.mp4':
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: isommp42
creation_time : 2018-07-05T20:26:46.000000Z
Duration: 00:13:14.93, start: 0.000000, bitrate: 12429 kb/s
Stream #0:0(eng): Video: h264 (Baseline) (avc1 / 0x31637661), yuv420p, 640x480, 12298 kb/s, SAR 1:1 DAR 4:3, 10.01 fps, 10.01 tbr, 90k tbn, 180k tbc (default)
Metadata:
creation_time : 2018-07-05T20:26:46.000000Z
handler_name : VideoHandle
Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, mono, fltp, 128 kb/s (default)
Metadata:
creation_time : 2018-07-05T20:26:46.000000Z
handler_name : SoundHandle
I don't know of any way to control this quality setting, either through the Camera app itself or the device System Settings. Just wanted to put this information out there in case anyone else stumbles across the same problem or happens to find a fix for it.

hornpipe2 said:
I've been using my Fire 10 HD tablet to record videos of myself for a vlog. I use the front-facing camera and record segments approximately 15 minutes long. I've been doing this for a couple weeks. Usually, 10 minutes of video translates to a file of approximately 100MB.
Today I shot a video and, surprisingly, a 13 minute video consumed 1.14 GB of space - a ten-fold increase! I've changed nothing - there are no options in the Camera app for this device to adjust bitrate, resolution or fps of the front-facing camera. The only difference is that last night, my Fire tablet took an upgrade to the latest 5.6.2.0 Fire OS. I assume this has changed the system-wide bitrate for any camera capture, as the same change occurs using any other camera app from the Amazon store!
:
I don't know of any way to control this quality setting, either through the Camera app itself or the device System Settings. Just wanted to put this information out there in case anyone else stumbles across the same problem or happens to find a fix for it.
Click to expand...
Click to collapse
File size is ridiculous given HD 10 FF camera quality. Something went horribly wrong; perhaps video compression failed. FWIW bitrate can be controlled with Open Camera and many other apps. But me thinks the problem lies elsewhere. Reboot to see if the issue persists.

I did try a reboot (power off, power on) but it continues to have unneccesarily large bitrate.
I don't have Open Camera. I see there's an app on the Amazon store called "Simple Camera". which seems to be just a renamed build of Open Camera. but it costs 99 cents.
I asked Amazon Support about it but the customer service rep knows nothing and will forward it to the developers.
Has anyone else with this version noticed a similar / same issue?

hornpipe2 said:
I did try a reboot (power off, power on) but it continues to have unneccesarily large bitrate.
I don't have Open Camera. I see there's an app on the Amazon store called "Simple Camera". which seems to be just a renamed build of Open Camera. but it costs 99 cents.
I asked Amazon Support about it but the customer service rep knows nothing and will forward it to the developers.
Has anyone else with this version noticed a similar / same issue?
Click to expand...
Click to collapse
See below for (safe) link to Open Camera:
https://www.apkmirror.com/apk/mark-harman/open-camera/

Are you using a stock tablet or have you done the mod to put Google Play store on it? I checked a while ago and got an update notice, but when I clicked Install, it just went back to the check screen and said no updates available. I'm thinking maybe the tablet needs to be stock to get the update.

pixelpop said:
Are you using a stock tablet or have you done the mod to put Google Play store on it? I checked a while ago and got an update notice, but when I clicked Install, it just went back to the check screen and said no updates available. I'm thinking maybe the tablet needs to be stock to get the update.
Click to expand...
Click to collapse
It's a stock tablet, no mods or anything. I don't think this update is widely distributed yet... the release notes on Amazon's site still point to previous (5.6.1.0) version.
Code:
amazon.com/gp/help/customer/display.html?nodeId=202194760

hornpipe2 said:
It's a stock tablet, no mods or anything. I don't think this update is widely distributed yet... the release notes on Amazon's site still point to previous (5.6.1.0) version.
Click to expand...
Click to collapse
You can 'side load' Open Camera or any other compatible camera app and still retain your "stock" status. Perfectly legit; Amazon fully supports this capability and provides a slider in FireOS settings that permits installations from sources other than the Amazon Store. Probably the quickest fix to your problem.

Premier AN-740 (witson w2-k7xxx) info. thread

After a lot of searching here and elsewhere I was not able to find a unit that matches these parameters. The unit was branded as Premier AN-740 which is obviously just a sticker label. Any help with identifying this unit will be greatly appreciated.
About Device LINK http://ibb.co/nMEroA
About vehicular platform 1/2 LINK: http://ibb.co/nBWU8A
About vehicular platform 2/2 LINK http://ibb.co/hyiFgV
Update: The stock ROM for this unit accepts 8888+OK as "secret code" to get to the opening logo customization screen. Maybe this provides a clue?

Update #2: Droid HW report
DEVICE
Model: evb3561sv_w_65_m0 (full_evb3561sv_w_65_m0)
Manufacturer: TS356XXPH-
Baseband Version: MOLY.LR9.W1444.MD.LWTG.MP.V94.P6, 2017/05/15 10:24
RIL Version: mtk gemini ril 1.0
Build Number: full_evb3561sv_w_65_m0-userdebug 6.0 MRA58K 1510921099 test-keys
Build Fingerprint: alps/full_evb3561sv_w_65_m0/evb3561sv_w_65_m0:6.0/MRA58K/1510921099:userdebug/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 240 dpi (hdpi)
Refresh Rate: 57.44 Hz
PROCESSOR
CPU Architecture: AArch64 Processor rev 4 (aarch64)
Board: unknown
Chipset: MT3561S
Cores: 4
Clock Speed: 221 MHz - 1248 MHz
Instruction Sets: arm64-v8a
CPU Features: fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU Governor: Not Available
Kernel Version: 3.18.19
Kernel Architecture: aarch64
GRAPHICS
Renderer: Mali-T720
Vendor: ARM
OpenGL Version: OpenGL ES 3.0
RAM
Total: 1897 MB
Java Heap: 128 MB
STORAGE
Internal: 11 GB
External: 7.2 GB
PRIMARY CAMERA
Resolution: 0.4 MP
Flash: No
Video Resolution: WVGA, 800x480
Supported Resolutions:
Image:
800x480
Video:
800x480 (WVGA)
SECONDARY CAMERA
Resolution: 0.4 MP
Video Resolution: WVGA, 800x480
Supported Resolutions:
Image:
800x480
Video:
800x480 (WVGA)
FEATURES
Bluetooth: Yes
Bluetooth LE: Yes
GPS: Yes
NFC: No
USB Accessory: Yes
WiFi: Yes
WiFi Direct: Yes
BATTERY
Technology: Li-ion
Health: Good
SENSORS
Not Available
Created by Droid Info

Update #3: ROOT!
I was able to root my device using the procedure outlined here:
https://forum.xda-developers.com/android-auto/android-head-units/ownice-c500-root-t3558760
Using the longer password and with some minor command line alterations (see screenshot here https://ibb.co/njSw5q). Hope this helps someone.
My next goal is to get to the factory settings. If anyone gets the code for that please post it here.

head unit info
Hello, it seems that I have the same head unit. Mine is unbranded and it's shaped to fit a 2008 suzuki swift, however all the codes seems the same.
What I got until now is that 8888 is the boot logo code selection and I can access to the engineering mode menu by dialing *#*#3646633#*#*
I'm trying to perform a factory reset because I accidentally delete the "su" executable and I cannot access it anymore even with the password, howevere there is a factory reset password that I can't find on the net. The next step will be trying to access the "RST" button and check what it does.

Hi Mr. Purple,
Thanks for your code
MrDeepPurple said:
I can access to the engineering mode menu by dialing *#*#3646633#*#*
Click to expand...
Click to collapse
I can confirm that it works for me as well. I was not however able to locate the FM Radio settings I was looking for (let me know if you find those).
Good luck with the factory reset, and let us know how it turned out.

Updates
I have some news:
The actual model seems to be the witson w2-k7xxx (in which xxx is the code of the shape of the front panel, mine is w2-K7658).
schwrz said:
l. I was not however able to locate the FM Radio settings I was looking for (let me know if you find those).
Click to expand...
Click to collapse
I managed to access the system menu with the code 3711 and here there are the FM settings!
Here follows what I discovered by trying and trying again and searching on the net:
CODES (to be inserted in Settings > software version > small gear icon near HMI):
3711 -> factory settings
8888 -> boot logo settings
6666 -> a chinese text that reports "no update files where found" appears (probably the update code)
7777 -> a chinese text that reports "no update files where found" appears (probably the update code)
0 -> MCU update page
How to access the engineering mode:
dial *#*#3646633#*#*
How to access the firmware update page:
Click the RST button
touch the screen (and move your finger) until a writing appear on the top left
if a binary file is present in the root of the SD card, then the update begins
How to perform a factory reset: (/system partition is left unchanged, only user data is wiped)
Click the RST button
touch the screen with five fingers (and move them) until a writing appears on the top left
The factory reset procedure will begin. It lasts for 10 minutes
I mailed witson for a firmware update (in order to override the /system partition and restore the su executable) but they ask me for a serial number that is written on the unit. I will disassemble it in a couple of days and if I manage to get this update, I will post it there. However it seems that each model has its own custom firmware that supports only one button layout. If I flash a firmware of the same family (w2-k7xxx) but from a different model, the buttons may not work.
Maybe you can find your own model on witson website

MrDeepPurple said:
I have some news
Click to expand...
Click to collapse
Wow man, you've really been busy! I'm definitely going to try out those codes and knowing who the manufacturer is will help as well. The user interface here definitely looks familiar, though I'm a bit confused as to how you were able to discover the XXX code in the W2-K7XXX part number of your unit. In any case thanks again for all the info and keep us updated, especially if you manage the much needed firmware update...

schwrz said:
though I'm a bit confused as to how you were able to discover the XXX code in the W2-K7XXX part number of your unit.
Click to expand...
Click to collapse
Well, my HU has the panel that fits only in the 2008 suzuki swift, so I used the search engine on their site to look for "Suzuki Swift" and there I got the part number!
However if you have a standard panel maybe you can go in product page, then on the left column select "+ For Universal All-in-one" and see if one of the model is the one you own. In that page I see only 4 Android 6.0 headunit: W2-K7900G, W2-K7927G, W2-K7902 and W2-K7924 (I can't send link because I'm new on XDA, but you can easily find them)
From the photos you posted, it seems that your HU is the W2-K7927G

MrDeepPurple said:
From the photos you posted, it seems that your HU is the W2-K7927G
Click to expand...
Click to collapse
Yes, I think so too ( Link for anyone interested). It would be nice to be able to confirm that this is indeed the exact model before we attempt a firmware update as flashing the wrong firmware is almost guaranteed to brick the unit (i'll try to search for th exact P/N in the "hidden" menus). Besides, now that I have all these secret menus to play with, maybe I can fix the problems I experience without a firmware update. The biggest two issues are speaker noise while idling (even when radio and music player are off) and waaay too jerky FM reception (unit is constantly trying to find a better frequency for the current station - I was told that I need to lower the FM sensitivity in the technician menu to fix that). If I can fix these two issues, I can definitely live without a F/W update. Did you experience any of these issues or is it just my particular model / unit?

schwrz said:
Did you experience any of these issues or is it just my particular model / unit?
Click to expand...
Click to collapse
yes, the idle background noise is too loud too on mine. The reception seems fine, just a little worse than the suzuki stock radio definitely usable. However if you find a solution for both, I think I will try it too! At the moment I'm stuck to solve the "su" problem!

sorry to hear that.
i assumed the factory reset took care of the SU problem.

Other updates
schwrz said:
sorry to hear that.
i assumed the factory reset took care of the SU problem.
Click to expand...
Click to collapse
Unfortunately the factory reset only reset the user partition, but the /system partition is left unchanged.
However after two weeks of mails, I finally got a firmware update binary from Witson.
I don't know if it's compatible to your radio, however i mailed to [email protected], they asked me for a product code placed on top of my Head unit and then sent me the update after I provided the code.
Here a picture of the location of the product code on my unit (it's the top side of the box):
{
"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"
}
Maybe you can ask for a firmware too with your serial and then we can check if it's the same file.
Now I'm trying to fixing a network bug that made my cellular network connect to a roaming operator (TIM) instead of my operator (three) due to a wrong priority assignment.

As always nothing but helpful information from MrDeepPurple (seen them in concert not too long ago hehe). I feel kind of ashamed for not contributing anything.
MrDeepPurple said:
... they asked me for a product code placed on top of my Head unit and then sent me the update after I provided the code.
Click to expand...
Click to collapse
I plan to take apart the center console in my car during this weekend so I'll be sure to check for that code - in addition to a few other things I've been saving for this event such as debugging that horrible background noise we talked about. I plan to disconnect the HU from all peripherals one by one until I find the culprit. If the HU itself is generating that noise I'll need to rethink my strategy. As for the radio reception, I did find the radio sensitivity setting thanks to your help and lowering it did help a little, but it turns out I've been kind'a stupid not noticing how short the antenna the previous owner put on the car was. With that size it was physically impossible to get good reception, so I just ordered an OEM antenna from the car manufacturer and hope to be done with this problem. The moral of this, I think, is that even though this HU is pretty sh**ty, we shouldn't be so quick to blame everything on it as there are other components in the system. One thing to note to anyone fiddling with the system settings from the codes MrDeepPurple provided, be aware that saving the settings will RESET YOUR HOME SCREEN TO STOCK so if you want to try out different settings do it all in one go, otherwise you'll end up having to replace all your widgets and things to the way you like them about a zillion times.
MrDeepPurple said:
Now I'm trying to fixing a network bug that made my cellular network connect to a roaming operator (TIM) instead of my operator (three) due to a wrong priority assignment.
Click to expand...
Click to collapse
It seems that the problems never end with this HU - is this bug due to the firmware update?
At this pace by the time we get them to perform adequately they will be outdated.
Anyways good luck and keep updating.

schwrz said:
It seems that the problems never end with this HU - is this bug due to the firmware update?
At this pace by the time we get them to perform adequately they will be outdated.
Anyways good luck and keep updating.
Click to expand...
Click to collapse
yes, this happens on a random OTA update I received a month ago. I didn't even know that this HU can have OTAs. However I'm not able to select network type (2G, 3G, 4G) anymore because the menu is greyed and instead it appeared a menù with PLMN editing. I didn't even know what a PLMN was before that.
However this menù is totally useless, the selection and the editing of PLMNs is resetted when you exit this menu. The PLMN which has the highest priority is TIM, then comes three UK (why uk? iI'm in italy!!). I read that there is a sqlite db accessible only with root permission that contains those informations so I need root to access it.
schwrz said:
As always nothing but helpful information from MrDeepPurple (seen them in concert not too long ago hehe). I feel kind of ashamed for not contributing anything.
Click to expand...
Click to collapse
You contributed to find the correct way to root this HU that is the most useful information to me by now!! Thank you!

well, it seems that the root procedure doesn't work on mine.
After all the steps on Ownice C500 post (even with the short password on forfan executable and the long one with the su executable) it seems that the root doesn't work. When I try to run the su command on a terminal emulator it returns 1. It's a generic error code, so there should be something missing. However I'm not scared to test it now that I have the firmware update files.
Did you use the su executable in the Ownice C500 post?
Are the other file useless (libsupol.so, sukernel and supolicy) ?

MrDeepPurple said:
well, it seems that the root procedure doesn't work on mine.
Click to expand...
Click to collapse
so with the firmware update they also patched the system against rooting?
makes me think twice before updating...
MrDeepPurple said:
Did you use the su executable in the Ownice C500 post?
Are the other file useless (libsupol.so, sukernel and supolicy) ?
Click to expand...
Click to collapse
Having performed the root two months ago I'm sorry to say I don't really remember much. However two things are clear from the screenshot (third post in this thread):
1. I used the longer password.
2. Only the actual su file is copied and given execution permissions.
Not sure what's the source of that 'su' executable but it's probably from the link given as I can't recall doing otherwise.

Today I received a new update binary, I will try to upload it soon and check if it solves my problem

schwrz said:
DEVICE
Model: evb3561sv_w_65_m0 (full_evb3561sv_w_65_m0)
Manufacturer: TS356XXPH-
Baseband Version: MOLY.LR9.W1444.MD.LWTG.MP.V94.P6, 2017/05/15 10:24
RIL Version: mtk gemini ril 1.0
Build Number: full_evb3561sv_w_65_m0-userdebug 6.0 MRA58K 1510921099 test-keys
Build Fingerprint: alps/full_evb3561sv_w_65_m0/evb3561sv_w_65_m0:6.0/MRA58K/1510921099754[/U]:userdebug/test-keys
Bootloader: unknown
Java VM: ART 2.1.0
OS Version: Marshmallow (6.0)
SDK: 23
DISPLAY
Resolution: 1024x600 pixels
Software Density: 240 dpi (hdpi)
Refresh Rate: 57.44 Hz
PROCESSOR
CPU Architecture: AArch64 Processor rev 4 (aarch64)
Board: unknown
Chipset: MT3561S
Cores: 4
Clock Speed: 221 MHz - 1248 MHz
Instruction Sets: arm64-v8a
CPU Features: fp asimd evtstrm aes pmull sha1 sha2 crc32
CPU Governor: Not Available
Kernel Version: 3.18.19
Kernel Architecture: aarch64
GRAPHICS
Renderer: Mali-T720
Vendor: ARM
OpenGL Version: OpenGL ES 3.0
RAM
Total: 1897 MB
Java Heap: 128 MB
STORAGE
Internal: 11 GB
External: 7.2 GB
PRIMARY CAMERA
Resolution: 0.4 MP
Flash: No
Video Resolution: WVGA, 800x480
Supported Resolutions:
Image:
800x480
Video:
800x480 (WVGA)
SECONDARY CAMERA
Resolution: 0.4 MP
Video Resolution: WVGA, 800x480
Supported Resolutions:
Image:
800x480
Video:
800x480 (WVGA)
FEATURES
Bluetooth: Yes
Bluetooth LE: Yes
GPS: Yes
NFC: No
USB Accessory: Yes
WiFi: Yes
WiFi Direct: Yes
BATTERY
Technology: Li-ion
Health: Good
SENSORS
Not Available
Created by Droid Info
Click to expand...
Click to collapse
I just buy and new android head Units is name DynaVin 2GB 16GB with 4gLTE .
The "Droid info" i get only 2 was difference from yours as below shown .
1)build number difference from 1510921099 mine 1511340754
2)build fingerprint difference 1510921099754 mine 1511340754
I Found 2 Bug
1) Minor Noisy Sound when in idle mode .
2) Waze Hang when using 4G Lte . Reseat 4G Card then be ok again
Anyone can provide some ideal ?

k5235 said:
I just buy and new android head Units is name DynaVin 2GB 16GB with 4gLTE .
The "Droid info" i get only 2 was difference from yours as below shown .
1)build number difference from 1510921099 mine 1511340754
2)build fingerprint difference 1510921099754 mine 1511340754
Click to expand...
Click to collapse
I think it's the same head unit, probably the differences are only on firmware release version
k5235 said:
1) Minor Noisy Sound when in idle mode .
Click to expand...
Click to collapse
This is a common bug, schwrz was trying to solve that but it seems to affect all the radios with the MTK3561
k5235 said:
2) Waze Hang when using 4G Lte . Reseat 4G Card then be ok again
Anyone can provide some ideal ?
Click to expand...
Click to collapse
I've never tried waze on it, only google maps and sygic and they both works fine! Well, sygic is a bit slow and laggy but still usable.

MrDeepPurple said:
I think it's the same head unit, probably the differences are only on firmware release version
I've never tried waze on it, only google maps and sygic and they both works fine! Well, sygic is a bit slow and laggy but still usable.
Click to expand...
Click to collapse
The main reason I've put Android in the car is be able too use Waze properly (i.e. no weird phone holding gadgets) so yes, I can confirm that Waze works fine on this HU. Otherwise I'd have replaced it long time ago.
As for the idle noise, I currently tend to think it's a hardware rather than software issue. I'm going to take apart the center console and see what's what as soon as I receive some parts I'm waiting for (for which I also need to take apart the center console - no sense in doing it twice). Will report my findings.