Database Info

7" Win CE nav unit

I have a 7" double din in-dash chines made nav unit that runs win ce 5.0. The specs for this unit are:
Detail Specifications
* Operating system: Windows CE 5.0
* GPS Processor: SAMSUNG
* Max. main frequency: 400MHZ.
* RAM Memory: 64MB
* Memory Size: can expand to 4GB
* Supported Maps: IGO, ROUTE66, TOMTOM and so on.
* Voice Guidance Cruise: Yes
* GPS languages: English/French/German/Spanish/Portuguese/Russian
* GPS antenna: 1 GPS antenna interface on the back
* GPS dual zone: You can enjoy music and radio while GPS navigation
DVD Player
* Formats played: MP4, DIVX, DVD, DVD-R/RW, DVD+R/RW, VCD, MP3, WMA, JPEG, etc
* Media: this dvd player reads all popular media including DVD/DVD-R/DVD+R/DVD-RW/DVD+RW/CD/CD-R/CD-RW/MP3/MP4(DIVX)/VCD/SVCD/US
Screen
* Size: 7 " 16:9 TFT LCD wide touch screen
* Digital or Anolog: Digital screen (higher definition than anolog screen)
* Number of Pixels: 480*234 (R.G.B), higher definition due to the RGB signal
* OSD language: English
* Touch panel: yes
* Brightness control: yes
* Picture adjustment (brightness, contrast, color, settings)
Bluetooth
* Version: V2.0, Support AD2P (Bluetooth Stereo Music), can play stereo music through Bluetooth
* Built-in microphone:yes
* Received call: yes
* Dialled call: yes
* Missed call: yes
TV tuner
* Digital TV or Anolog TV: Analog TV tuner
* Video format: PAL/NTSC(SECAM Optional)
* TV antenna:2 TV antenna interface on the back
* Preset stations:100 preset stations
* ATSC: no
Radio
* Radio Frequency: Europe, USA1, USA2, Japan, Russian
* AM Frequency range: 522-1620 (Europe/China), 530-1710 (America)
* FM Tuning range: 87.5-108 (Europe/China), 87.5-107.9 (America)
* FM Medium frequency: 10.7MHz
* RDS: YES (RDS is useful for European buyers)
* Preset stations: 30
iPod control
* YES
USB
* Interface: 1 mini USB interface. Support hot plug.
* Position: front
* Random / Repeat Play: YES
Video in/out
* Camera video in: YES, auto-switch to rear-view status when your car reverses,to the shipping cost when making the payment and tell us via Email, or just send the extra cost directly from your paypal account to us after you pay for this car dvd gps system(Both PAL&NTSC are available)
* 1 AUX video in
* 1 video out
Audio in/out
* 2 pair of RCA out: Front-L out, Front-R out, Rear-L out, Rear-R out
SD
* 2 SD card slots, one for GPS SD, the other for storing MP3, MP4, WMA, AVI, JPEG files.
* Max. capacity: 4G
* You will receive a gps map card with map software(if the map is available for your location) for free. So If you need another SD Card to load Music/Video files, please pay us extra 10 usd. You email us that you need the optional accessories,then wait to receive an invoice including extra/additional cost sent from us. Or just send the extra cost directly from your paypal account to us after you pay for this car dvd gps system and inform us via Email)
Motorized slide-down Face
YES
Detachable Control Panel
YES ,only the border(not key button) can be removed to avoid theft.
Dual zone:
YES, You can enjoy music(in CD/DVD/USB/SD Card) and radio while navigation.
AUX in
AUX R IN, AUX L IN
Games
NO
DTS
NO (DTS is short for Digital Theatre System)
Steering wheel control
Yes
Button Sound:
ON/OFF for sound of screen buttons
MOS-FET Amplifier
YES, Max 4*45W (Stereo)
EQ
POP, ROCK, JAZZ,NORMAL
Portable HDD Compatible
YES. (The size must less than 20GB)
Built-in speaker
NO
Subwoofer output
Yes
Anti-Shock
YES
Operating Envioroment
* Voltage requirment: 12 V DC (allowable range: 10.8-14.5V)
* Max. consumption of current: 15A
* Temperature: -20℃ ~ +70℃
ISO connector
* Yes
Accessories
* Manual (Language: english)
* Remote contorl (Battery included)
* GPS antenna
* Wiring cable set
* USB cable
* 2GB SD card(map preloaded if available for your country)
I wonder if it is possible to flash this unit with win ce 6.0, and how to it?

Why would you wanna do that?

why
win ce 5.0 is already screwed up and I need to re install either win ce 5.0 or better upgrade to win ce 6.0. Appreciate the help.
The unit cam with a chines win ce 5.0, and I do not know chines and I did something that made all serial ports vanish, and the gps receiver is no longer there, as there is no available serial ports.

help, please
guys, I need your help please, need to re-flash this unit with win ce 5.0

Thunderbolt Full Specs List

Features:
Specifications
• Mode: CDMA 2000 1xRTT / 1xEVDO Rev. A 800/1900
• LTE: 700 MHz (Band 13)
• Chipset: MSM 8655, 1 GHz MDM 9600
• Operating System: Android 2.2 (Froyo) (LTE support developed by HTC)
• Size: 122 mm (L) x 67 mm (w) x 13.2 mm (T)
• Weight: 173g
• Memory (emmc/RAM): 4GB*(8GB) / 768 MB (*Verizons Specs Say 4GB, HTC's say 8GB)
• Removable Memory: 32GB
• Battery Type: Li-Ion 1400mAh (std)
• Form Factor: Bar Type Smartphone
• Digital Usage: 398min.
• Digital Standby: 227hrs
• Camera Sensor: CMOS
• Camera Resolution: 8.0 Megapixel w/ Auto Focus
• Camera Flash: Dual LED Flash
• UI: HTC Sense UI
• Speaker Type: mono
• Speakerphone Button: N
• Main Display Type(s) & Resolution: 4.3” 800x480 WVGA TFT LCD with LED Back Light (Capacitive Mult-touch
Screen)
• Messaging: MO / MT, SMS, MMS (Phase 2)TBD
• Predictive Text: HTC
• HTML Browser: Google Browser w/ Flash 10.1
• PTT: N/A
• MIP/DMU: Y
• Data (USB): 2.0: High Speed
• Audio Formats Supported: MIDI / M4A / QCP / AMR / AAC / AAC+ / eAAC+ / WAV / WMA9 / MP3
• Image(Graphic) Formats Supported: JPEG, GIF87a, GIF89a, PNG, WBMP
• Video Formats Supported: MPEG4 / H.263 / H.264 / WMV9
• Languages: 18 languages (Chinese – China, Chinese - Taiwan, Czech, Dutch, English, Finnish, French,
German, Italian, Norwegian, Polish, Russian, Spanish, Greek, Danish, Swedish, Turkish, Portuguese)
• TTY/TDD capable: Y
• ERI: Y
• Camera Type: Rear: 8.0 MP w/ Auto Focus and dual LED Flash (720p recording), Front: 1.3 MP
• HAC: M3
• T-coils: T3
• Other: BT (2.1, 3.0 when available), WiFi (b/g/n), Proximity Sensor, Light Sensor, Compass Sensor, G-Sensor
• Virtual Keys (Home, Menu, Back, Search), 3.5mm Headset Jack. Surround Sound (Dolby, SRS), Noise
Cancellation (in call and Search), USIM/CSIM/ISIM, Wireless charging, FM Radio
• Personalization Capabilities: HTC Sense UI Widget, Shortcut, and Wallpaper customization (7 Home Panels)
• Accessories Supported: HDMI Adapter, Wireless Charging , Extended Battery (3.7VDC, 2750mAh), Audio
Adapter, Car Kit, Car Charger, Mono BT Headset, Standard Battery, USB Sync Cable, AC Adapter, Simple
Pouch
General
• User_Memory: Pooled
• User Memory Size: 1.41GB
• Dedicated Flash Memory: Music /PIC/Video can only be stored on SD card per Google design; E-mail would
be store on flash and the size is up to 123.5 MB
• MP3 Ringtones (supported via SW) Yes
• MMS Ringtone Support: Yes
• MP3 Player: Yes
• ERI Banner: Y (Supported in Lock Screen & Notification Shade)
• ERI Audible Alert: No
• Power Connector: Micro USB
• Headset Jack: 4 pole; 3.5mm
• TTS(Text to Speech – reading text msgs): Yes, engine supported
• Voice Tags (aka Voice Name Dialing): Yes, Speaker Dependent.
• Voice Digit Dialing: Yes
• Voice Commands: Yes
• Voice Commands Scope: Name Dialing, Digit Dialing, Contact Query, Callback, Redail, Call History, Time
Query, Media Player, E-mail, SMS, Calendar Reader.
• VAD Provider: Cyberon
• VAD Version: 3.0
• Voice Commands: Yes
• Voice Dictation: Yes
• Receive Diversity: Y for Cell and PCS bands
• Simultaneous GPS: Y
• A12: Y
• Multiple NAIs: Y
• Slot Cycle Index: 2
• Hard Reset Button: N
• Wi-FI: 802.11 b / g / n
Display Features
• Display Resolution - (width x height) 800x480
• Display Active Screen area Diagonal: 4.3 inches
• Display colors supported: 262K color TFT LCD ( OS support 64K colors only)
• Display Type: TFT - LCD
• Display Active screen area – w x h (inches, up to 2 decimals): 56.16 X 93.60 mm
• Display Pixel Shape: RGB Stripe
• Display Pixel Size - 0.117(H) X 0.117(V) mm
• Display Pixel Pitch - 0.117 mm
• Touch Display Type: Capacitive
• Touch Display Orientation: Both (Portrait / Landscape)
Bluetooth Features
• BT Core Version: 2.1 w/ EDR
• BT Profiles Supported:
• HSP = Head Set Profile (Mono Headset): Yes, Ver.1.2
• HFP = Hands-Free Profile (must support optional settings in profile): Yes, Ver. 1.5
• SPP = Serial Port Profile (AT Commands): No
• Verify if GSM AT commands are supported:
• DUN = Dial Up Networking: Yes
• A2DP = Advanced Audio Distribution Profile: Yes
• AVRCP = Audio/Visual Remote Control Profile: Yes
• OBEX = Object Exchange Profiles
• OPP = Object Push Profile (must support optional settings in profile):
• Identify VCard version supported: No
• Identify additional items supported: No
• FTP = File Transfer Profile : Yes
• Identify additional items supported: No
• SYNC = Synchronization Profile : No
• BIP = Basic Imaging Profile : No
• BPP = Basic Printing Profile : No © 2011 Verizon. All Rights Reserved.
• PBAP = Phone Book Access Profile: Yes
• GAVDP = Generic Audio/Video Distribution Profile: No
• AVDTP = Audio/Visual Distribution Profile: No
• AVCTP = Audio/Visual Control Transport Protocol Profile: No
• HID = Human Interface Device: No
• VDP = Video Distribution Profile: No
• HDP = Health Device Profile: No
• PAN = Personal Area Network Profile: N

so its confirmed only 4gb storage and not the 8 gb?

That's what it shows and it would also make sense with what we are seeing for numbers.
I'm thinking it's correct!

What's wireless charging?
Sent from my ADR6400L using XDA App

If this only has 4 gb emmc, then verizon is straight lying on theri website and I am a little pissed as well. This is straight from their site :
Specifications
Dimensions
* 4.75" x 2.44" x 0.56" inches
* Weight: 6.23oz (with standard battery)
Operating System
* Android 2.2 with HTC Sense 2.0
Display
* 4.3" capacitive touch screen
* 480x800 WVGA display
* Orientation in portrait and landscape
Keyboard
* Touch screen QWERTY Keyboard
Battery
* Usage: 378 mins OR
* Standby: 330 hours
* SAR 1.2 W/kg @ 1g (HEAD)
* SAR 1.46 W/kg @ 1g (BODY)
Memory / Processor
* 8GB eMMC
* 768 MB RAM
* Actual formatted capacity will be less

could be that tbolt has 8gb internal memory but only 4gb is enabled so far. Maybe 4gb will be enabled to the user with ota?

What is the maximum bandwidth the LTE chipset is physically capable of?
Sent from my ADR6400L using XDA App

R1lover said:
Specifications
• Main Display Type(s) & Resolution: 4.3” 800x480 WVGA TFT LCD with LED Back Light (Capacitive Mult-touch
Screen)
Click to expand...
Click to collapse
Well, that settles the debate in another thread over whether or not the display is SLCD.

distortedloop said:
Well, that settles the debate in another thread over whether or not the display is SLCD.
Click to expand...
Click to collapse
S-lcd is actually the name of a company that produces tft lcd screens, its not the type of screen as most think.
This could be a s-lcd screen, but we don't know the manufacturer of the screen at this point.
Sent from my ADR6400L using Tapatalk

madfatter said:
If this only has 4 gb emmc, then verizon is straight lying on theri website and I am a little pissed as well. This is straight from their site :
Specifications
Dimensions
* 4.75" x 2.44" x 0.56" inches
* Weight: 6.23oz (with standard battery)
Operating System
* Android 2.2 with HTC Sense 2.0
Display
* 4.3" capacitive touch screen
* 480x800 WVGA display
* Orientation in portrait and landscape
Keyboard
* Touch screen QWERTY Keyboard
Battery
* Usage: 378 mins OR
* Standby: 330 hours
* SAR 1.2 W/kg @ 1g (HEAD)
* SAR 1.46 W/kg @ 1g (BODY)
Memory / Processor
* 8GB eMMC
* 768 MB RAM
* Actual formatted capacity will be less
Click to expand...
Click to collapse
Why would you be pissed? What difference would it make if there was 8gb total and 4gb total, when in fact there is only approx 2.5gb usable? There is however a 32gb sdcard which was very nice of then to include.
Sent from my ADR6400L using Tapatalk

ilogik said:
What's wireless charging?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
There is a battery door you can buy and use with a wireless charging pad.
Sent from my ADR6400L using Tapatalk

I would be angry because they are advertising it as having an 8gb emmc, when in reality it only seems like it has 4gb. Would you be angry when you bring a tv home from the store that you thought was 1080p and it turns out its only 720?

madfatter said:
I would be angry because they are advertising it as having an 8gb emmc, when in reality it only seems like it has 4gb. Would you be angry when you bring a tv home from the store that you thought was 1080p and it turns out its only 720?
Click to expand...
Click to collapse
Well that would have an affect in quality, this means nothing.... Lol
Sent from my ADR6400L using Tapatalk

wrb123 said:
what is the maximum bandwidth the lte chipset is physically capable of?
Sent from my adr6400l using xda app
Click to expand...
Click to collapse
+1 .

There is 5.00168gbs(or 5121.72mb) on the system partition according to Root Explorer and a calculator. Most of it is free (empty) space, though.
5.00168 + the ~2.5gb user storage partition = ~7.5gb.
This is the same as the MT4G and G2, both of which had the same advertised 8gb internal storage I believe.

how do we get at this space? it seems strange to have it just sitting around there, not being able to be used. perhaps it is possible to rewrite emmc partions to give this an "internal" storage, much like the Dinc had?

madfatter said:
how do we get at this space? it seems strange to have it just sitting around there, not being able to be used. perhaps it is possible to rewrite emmc partions to give this an "internal" storage, much like the Dinc had?
Click to expand...
Click to collapse
Most likely this will be impossible.
The eMMC's generally used by HTC can only be partitioned once, period. At least, this was the case with the G2 and the MT4G which had the same "missing" storage space.
EDIT: Adding a reference link from the G2 wiki. I realize that G2 =/= Thunderbolt, however, it is very likely that HTC uses the same manufacturing process for all of it's phones.
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#The_Missing_2GB

R1lover said:
Well that would have an affect in quality, this means nothing.... Lol
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
This does mean something. I was under the impression that by 8gb emmc, that I would have around 5 gb of internal storage like on the Dinc. Its practically the same phone, so i would assume the android system files take up about the same space on Thunderbolt's emmc.
It appears by unremarked analysis, that there is indeed the space there, it is just unusable. Hopefully if that is the case, there is a way to access this space.
While the 32gb class 4 card is a nice touch. i still prefer the internal memory to store pictures and music on
And btw, no need to act all high and mighty when you are clearly wrong.

madfatter said:
This does mean something. I was under the impression that by 8gb emmc, that I would have around 5 gb of internal storage like on the Dinc. Its practically the same phone, so i would assume the android system files take up about the same space on Thunderbolt's emmc.
It appears by unremarked analysis, that there is indeed the space there, it is just unusable. Hopefully if that is the case, there is a way to access this space.
While the 32gb class 4 card is a nice touch. i still prefer the internal memory to store pictures and music on
And btw, no need to act all high and mighty when you are clearly wrong.
Click to expand...
Click to collapse
The Dinc is a little bit different, though, as it was designed to function without an SD card. Forgive me as I don't recall correctly, but didn't it originally launch without one? I believe the Dinc's eMMC is probably setup more akin to the Nexus S(which is entirely internal storage) than the TB.

Seems like all the various references and reviews I'm reading are saying the Thunderbolt has a screen by Super LCD.

iPazzport Pearl?

Has anyone purchased one of these? Price is up there, but Camera, 1GB RAM 4GB ROM, and looks like it can stream Netflix, and with a remote and keyboard touchpad combo, it might be what I have been looking for, above and beyond the MK808B that I thought would be a good option. WAY better than a Roku, as it has a browser.
Might be a good hackable device(Edit: Hackable ROM?) if some dev has the time, or as-is?
http://unisen-usa.com/product/pearl/ipazzport-pearl/

$109 on eBay: http://www.ebay.com/itm/iPazzPort-P...Wifi-1080P-w-Speaker-Mic-Camera-/200934208105
Specs:
Technical Specs (seems randomly placed between remote and device itself):
· 2.4 GHz Wireless Connectivity with up to 33 ft. Range
· Built-in 802.11 N Wifi and Ethernet Port
· Powerful Dual Core 1.6GHz Processor
· 2 Megapixel Camera
· 1080P HD Video
· 1G DDR3 Memory
· 4G Flash Memory expandable to 20G via SD Card slot
· Keyboard is 6.25” L x 2.25” W x .5” H & weighs only 4 oz.
· Rechargeable Lithium Ion Battery with 400mA capacity
· Charge Voltage: DC 5V/300mA
· Up to 400 Hours of Standby Keyboard Power
· Working Voltage: 3.3V
· Power Supply:5V/2A
Model SY-20-19VC
OS Android 4.1
Main chip 1.6 GHz Dual-Core
Memory 1G DDR3
Storage 4GB, expandable to 20G via Micro SD / TF card slot
Wifi IEEE 802.11 b/g/n
Lan Standard RJ45
HD video decoder [email protected] 60FPS
HD video encoder [email protected] 30FPS
Audio MP3 / WMA / WAV / OGG / AAC / FLAC / 3GP
Video MPEG2/4 / AVI / WMV / MKV / MOV /RM / RMVB
Languages English / French / German / Spanish / Italian / etc.
Ports on command base 2 * USB 2.0, 1 * Micro USB, 1 * Micro SD / TF slot, 1 * RJ45 Ethernet port,
1 * HDMI 1.4, 1 * 3.5mm AV Output, 1 * DC Port
Power supply US Plug Input: 100~240V Output: DC 5V / 2A
Command base size Diameter: Approx.12cm/4.7in Height: 8cm/3.2in
Keyboard size 15.5*5.5*1cm / 6.1*2.2*0.4in
Item weight Command base: 305g/10.7oz Keyboard: 100g/3.56oz
Package size 17.8*17.8*12.2cm / 7*7*4.8in
Package weight 835g / 1.84lb
Package Contents:
· iPazzPort Command Center
· iPazzPort Keyboard/Remote
· A/C Power Adaptor
· 4’ HDMI Cable
· USB to Micro USB Cable
· 3.5 mm A/V to RCA Cable
· User Manual

hello guys. I have purched this from ebay, and after two months working perfect I faced a serious problem and don't know what to do. I installed the Acapella tts voices and after that it stacked and it don't run or unistall any application. it has not a hard reset. It has only from settings but it not working either. Does any know if there is any button combination for hard reset or something to go back to factory settings. Or is it any firmware which I can install to have a fresh OS? thanks for your reply.

Improve Bluetooth audio quality on headphones without aptX or LDAC

The test is over. I'm no longer accepting libraries to patch.
SBC XQ Feature is available in LineageOS 15.1 build created on or after the 31st of March 2019, or a 16.0 build created on or after the 13th of May 2019.
Many note low sound quality and lack of high frequencies when using the standard SBC Bluetooth codec, which is supported by all headphones and other Bluetooth devices. A common recommendation to get better sound quality is to buy devices and headphones with aptX or LDAC codecs supported. These codecs require licensing fees, so devices with them are more expensive.
It turns out that the low quality of SBC is caused by artificial limitations of all current Bluetooth stacks and headphones' configuration, and this limitation can be circumvented on any existing devices.
Everyone interested in Bluetooth audio, please take part in high-bitrate SBC compatibility testing on various headphones, receivers, stereo systems, or automotive head units.
If the vast majority of devices work with high bitrates, I will make a patch for Android and send it to AOSP and third-party ROMs, and high quality Bluetooth audio will be available to everyone on any headphones and smartphones, regardless of codecs with licensing fees.
Short technical information about SBC codec
SBC has lots of different parameters that are negotiated during the connection setup phase:
Audio channel type and number: Joint Stereo, Stereo, Dual Channel, Mono;
Number of frequency bands: 4 or 8;
Number of audio blocks in one packet: 4, 8, 12, 16;
Quantization bit allocation algorithm: Loudness, SNR;
Maximum and minimum bit pool used in quantization process: usually 2-53.
The decoder is required to support any combination of these parameters. Encoder may implement only a part of them.
Existing Bluetooth stacks usually negotiate the following profile: Joint Stereo, 8 bands, 16 blocks, Loudness, bitpool 2..53. This profile encodes 44.1 kHz audio with a bitrate of 328 kbps.
Bitpool parameter directly affects the bitrate within the same profile: the higher it is, the higher the bitrate, and hence the quality.
However, the bitpool parameter is not bound to a specific profile. The bitrate is also significantly affected by other parameters: audio channel type, number of frequency bands, number of audio blocks. You can increase the bitrate indirectly by negotiating non-standard profiles, without changing the bitpool.
{
"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"
}
For example, Dual Channel encodes channels separately, using the entire bitpool for each channel. Forcing the device to use Dual Channel instead of Joint Stereo will get us almost doubled bitrate at the same maximum bitpool, 617 kbps.
To me it feels that bitpool should be an internal variable. It is an A2DP specification design fault that bitpool value is not bound to other codec parameters and only defined as a global value.
These fixed Bitpool and Bitrate values originate from recommended values for high-quality audio. But the recommendation is not an excuse to limit the profile to these values.
A2DP specification v1.2, which was active from 2007 to 2015, requires all decoders to work correctly with bitrates up to 512 kbps:
The decoder of the SNK shall support all possible bitpool values ​​that do not result in the excess of the maximum bit rate. This profile limits the available maximum bit rate to 320kb/s for mono, and 512kb/s for two-channel modes.
Click to expand...
Click to collapse
In the new version of the specification there is no bitrate limitation. It is assumed that modern headphones released after 2015 with EDR can support bitrates up to 730 kbps.
For some reason, all currently tested Bluetooth stacks (Linux (PulseAudio), Android, Blackberry and macOS) have artificial restrictions of maximum bitpool parameter, which directly affects the maximum bitrate. But this is not the biggest problem, almost all headphones also limit the maximum bitpool value to 53.
As I've already seen in my tests, most devices work fine on a modified Bluetooth stack with a bitrate of 507 kbps, without interrupts and crackling. But such a bitrate will never be negotiated under normal conditions, with stock Bluetooth stacks.
How to test on a PC
High bitrate SBC headphone compatibility test is the easiest to perform on the PC with a Bluetooth adapter. I've prepared Ubuntu image with a modified Bluetooth stack, which can be run as in a virtual machine (by connecting Bluetooth adapter as a USB device inside the virtual machine, it also works with the adapters built into the laptops) or by booting from the USB flash drive. This image uses the following profile: Dual Channel, 8 bands, 16 blocks, Loudness, bitpool 2..41, 44.1 kHz, which provides 485 kbps bitrate.
See the attachment in the end of this post.
Running in a VM
Download Virtualbox and Virtualbox Extension Pack: https://www.virtualbox.org/wiki/Downloads;
Install Virtualbox, start it;
Install Extension Pack using File → Preferences → Extensions;
Create new virtual machine: Linux, Ubuntu (64-bit), 1024 RAM. Do not create a HDD.
Navigate to virtual machine settings, in Storage choose Controller: IDE, Empty, press CD icon → Choose virtual optical disk file;
Select downloaded bluetooth-dualchannel-test-ubuntu-18.04.1-desktop-amd64.iso;
Save and close settings window, start virtual machine;
Right-click USB cable icon in the bottom right, select your Bluetooth adapter;
Running on a PC
The image supports BIOS/CSM and UEFI booting.
Burn the image to a USB flash drive using Etcher: https://etcher.io/. This operation will delete all existing files on a USB drive.
Turn off the PC;
Insert USB flash drive, turn on the PC and press boot order button (usually Esc or F12);
Select your USB flash drive.
Performing the test
(optional but recommended) Double click on "Btsnoop Dump" script on the desktop. It will start Bluetooth data capture for later analysis. Do not close terminal window.
Switch the headphones to pairing mode;
Click to the arrow in top right corner, select Bluetooth icon → Bluetooth Settings;
Choose your headphones, wait until pairing is complete and close the window;
Set Ubuntu volume to about 2/3. Also decrease volume using headset buttons as it could be very loud after pairing.
Open "music" folder, play "testrecord1.flac";
(optional but recommended) Close player, close terminal window. This will stop data capture.
(optional but recommended) Open Firefox browser, upload data dump (btsnoop_hci.btsnoop on the desktop) to https://btcodecs.valdikss.org.ru/
You can listen to other music in the music folder, or upload your own;
Post in this topic your headphone model and test results.
There should be no cracklings, audio interruption or other sound distortion in the headphones. If you hear a good high-quality sound, that means your headphones support audio with a bit rate of 485 kbps.
If you upload data to the server, please carefully follow the algorithm above. Especially, if you power off the headphones or disconnect after pairing, it's important to connect to the headphones manually from the bluetooth settings, do not allow auto connection!

How to test on Android device
In order to test from Android smartphone or tablet you need to use modified Bluetooth stack, which requires root privilege.
For regular users
Use PC method if possible.
Create backup before overwriting bluetooth library. Some patched libraries are attached to this post.
Unrestricted/unlimited versions negotiate Dual Channel mode and disable bitrate restriction (617-660 kbit/s will be used). Versions with 482 or 486 prefix negotiate 474-485 kbit/s.
For ROM developers (Android 5-7)
Patchset which increases maximum Bitpool value and adds Bluetooth Dual Channel option is available using the following link:
LineageOS 14.1 (Android 7.1.2)
The following information is outdated and is kept only for historical reasons:
Code:
[b]These modifications are designed only for test and should not be applied to the main ROM repository![/b]
[b]If you're a ROM developer, please provide flashable modified bluetooth library if possible![/b]
These modifications should be applied to stock Android bluetooth stacks Bluedroid (Android 5) and Fluoride (Android 6-7). Qualcomm-modified stack is not supported.
[b]1. Replace Joint Stereo with Dual Channel in standard SBC configuration[/b]
[url="https://android.googlesource.com/platform/external/bluetooth/bluedroid/+/master/btif/co/bta_av_co.c#99"][i]android/platform/external/bluetooth/bluedroid/btif/co/bta_av_co.c:99[/i][/url]
[code]const tA2D_SBC_CIE btif_av_sbc_default_config =
{
BTIF_AV_SBC_DEFAULT_SAMP_FREQ, /* samp_freq */
A2D_SBC_IE_CH_MD_JOINT, /* ch_mode */
A2D_SBC_IE_BLOCKS_16, /* block_len */
A2D_SBC_IE_SUBBAND_8, /* num_subbands */
A2D_SBC_IE_ALLOC_MD_L, /* alloc_mthd */
BTA_AV_CO_SBC_MAX_BITPOOL, /* max_bitpool */
A2D_SBC_IE_MIN_BITPOOL /* min_bitpool */
};
Replace A2D_SBC_IE_CH_MD_JOINT with A2D_SBC_IE_CH_MD_DUAL.
2. Increase Dual Channel priority
android/platform/external/bluetooth/bluedroid/btif/co/bta_av_co.c:411
Code:
if (src_cap.ch_mode & A2D_SBC_IE_CH_MD_JOINT)
pref_cap.ch_mode = A2D_SBC_IE_CH_MD_JOINT;
else if (src_cap.ch_mode & A2D_SBC_IE_CH_MD_STEREO)
pref_cap.ch_mode = A2D_SBC_IE_CH_MD_STEREO;
else if (src_cap.ch_mode & A2D_SBC_IE_CH_MD_DUAL)
pref_cap.ch_mode = A2D_SBC_IE_CH_MD_DUAL;
else if (src_cap.ch_mode & A2D_SBC_IE_CH_MD_MONO)
pref_cap.ch_mode = A2D_SBC_IE_CH_MD_MONO;
Move if with A2D_SBC_IE_CH_MD_DUAL to the top.
3. Disable or increase bitrate restriction
Android bluetooth stack has not only bitpool limit, but also bitrate limit, 328 kbit/s. If the headphones support, for example, bitpool 53 for 48 kHz, Android will decrease the bitpool down to fit into 328 kbit/s limit. This will happen AFTER codec negotiation, on the encoding stage, do not take into account bitpool value in Bluetooth SetCapabilities packet.
android/platform/external/bluetooth/bluedroid/btif/src/btif_media_task.c:172
Code:
#define DEFAULT_SBC_BITRATE 328
Replace with 512.
4. (for experiments only) Disable MTU limit.
This is required for bitrates higher than ~580 kbit/s.
btif/src/btif_media_task.c:174
Code:
/* 2DH5 payload size of 679 bytes - (4 bytes L2CAP Header + 12 bytes AVDTP Header) */
#define MAX_2MBPS_AVDTP_MTU 663
[/code]
For ROM developers (Android 8-9)
Patchset which increases maximum Bitpool value and adds Bluetooth Dual Channel option is available using the following links:
LineageOS 15.1 (Android 8.1)
LineageOS 16.0 (Android 9)
AOSP Master (what will eventually become Android 9.1/10)
If you're a ROM developer, please provide flashable modified bluetooth library if possible!
The following information is outdated and is kept only for historical reasons:
1. Add Dual Channel support into A2DP SBC Source
/platform/system/bt/stack/a2dp/a2dp_sbc.cc:55
Code:
/* SBC SRC codec capabilities */
static const tA2DP_SBC_CIE a2dp_sbc_caps = {
A2DP_SBC_IE_SAMP_FREQ_44, /* samp_freq */
(A2DP_SBC_IE_CH_MD_MONO | A2DP_SBC_IE_CH_MD_JOINT), /* ch_mode */
(A2DP_SBC_IE_BLOCKS_16 | A2DP_SBC_IE_BLOCKS_12 | A2DP_SBC_IE_BLOCKS_8 |
A2DP_SBC_IE_BLOCKS_4), /* block_len */
A2DP_SBC_IE_SUBBAND_8, /* num_subbands */
A2DP_SBC_IE_ALLOC_MD_L, /* alloc_method */
A2DP_SBC_IE_MIN_BITPOOL, /* min_bitpool */
A2DP_SBC_MAX_BITPOOL, /* max_bitpool */
BTAV_A2DP_CODEC_BITS_PER_SAMPLE_16 /* bits_per_sample */
};
add A2DP_SBC_IE_CH_MD_DUAL in ch_mode.
2. Replace Joint Stereo with Dual Channel in default config
/platform/system/bt/stack/a2dp/a2dp_sbc.cc:82
Code:
/* Default SBC codec configuration */
const tA2DP_SBC_CIE a2dp_sbc_default_config = {
A2DP_SBC_IE_SAMP_FREQ_44, /* samp_freq */
A2DP_SBC_IE_CH_MD_JOINT, /* ch_mode */
A2DP_SBC_IE_BLOCKS_16, /* block_len */
A2DP_SBC_IE_SUBBAND_8, /* num_subbands */
A2DP_SBC_IE_ALLOC_MD_L, /* alloc_method */
A2DP_SBC_IE_MIN_BITPOOL, /* min_bitpool */
A2DP_SBC_MAX_BITPOOL, /* max_bitpool */
BTAV_A2DP_CODEC_BITS_PER_SAMPLE_16 /* bits_per_sample */
};
Replace A2DP_SBC_IE_CH_MD_JOINT with A2DP_SBC_IE_CH_MD_DUAL.
3. Increase Dual Channel priority
/platform/system/bt/stack/a2dp/a2dp_sbc.cc:1155
Code:
static bool select_best_channel_mode(uint8_t ch_mode, tA2DP_SBC_CIE* p_result,
btav_a2dp_codec_config_t* p_codec_config) {
if (ch_mode & A2DP_SBC_IE_CH_MD_JOINT) {
p_result->ch_mode = A2DP_SBC_IE_CH_MD_JOINT;
p_codec_config->channel_mode = BTAV_A2DP_CODEC_CHANNEL_MODE_STEREO;
return true;
}
if (ch_mode & A2DP_SBC_IE_CH_MD_STEREO) {
p_result->ch_mode = A2DP_SBC_IE_CH_MD_STEREO;
p_codec_config->channel_mode = BTAV_A2DP_CODEC_CHANNEL_MODE_STEREO;
return true;
}
if (ch_mode & A2DP_SBC_IE_CH_MD_DUAL) {
p_result->ch_mode = A2DP_SBC_IE_CH_MD_DUAL;
p_codec_config->channel_mode = BTAV_A2DP_CODEC_CHANNEL_MODE_STEREO;
return true;
}
if (ch_mode & A2DP_SBC_IE_CH_MD_MONO) {
p_result->ch_mode = A2DP_SBC_IE_CH_MD_MONO;
p_codec_config->channel_mode = BTAV_A2DP_CODEC_CHANNEL_MODE_MONO;
return true;
}
return false;
}
Move if with A2DP_SBC_IE_CH_MD_DUAL to the top.
4. Increase bitrate limit
/platform/system/bt/stack/a2dp/a2dp_sbc_encoder.cc:42
Code:
#define A2DP_SBC_DEFAULT_BITRATE 328
Replace with 512.
5. (for experiments only) Disable MTU limit
This is required for bitrates higher than ~580 kbit/s.
/platform/system/bt/stack/a2dp/a2dp_sbc_encoder.cc:47
Code:
#define MAX_2MBPS_AVDTP_MTU 663
[/code]
For advanced users and ROM developers (Android 5-7 binary patch)
Please refer to this post in Russian (use Google Translate): https://4pda.ru/forum/index.php?s=&showtopic=914135&view=findpost&p=76169677
How to capture Bluetooth data dump on Android
Turn off Bluetooth;
In Developer Settings, enable the "Enable Bluetooth HCI snoop log" switch;
Turn on Bluetooth, connect to your headset using Bluetooth menu (this is important! Do not allow auto connection!);
Play short audio sample;
Open developer settings, disable the "Enable Bluetooth HCI snoop log" switch;
There should be /storage/emulated/0/btsnoop_hci.log or /data/misc/bluetooth/logs/btsnoop_hci.log created. If it's missing, open /etc/bluetooth/bt_stack.conf with a text editor and see the path in BtSnoopFileName option.
Upload btsnoop_hci.log to https://btcodecs.valdikss.org.ru/;
Post in this topic your headphone model and test results.
There should be no cracklings, audio interruption or other sound distortion in the headphones. If you hear a good high-quality sound with the patched library, that means your headphones support audio with a bit rate of 512 kbps.
If you upload data to the server, please carefully follow the algorithm above. Especially, if you power off the headphones or disconnect after pairing, it's important to connect to the headphones manually from the bluetooth settings, do not allow auto connection!
Some of the files attached below have no MTU limit patched. Unlocked/unrestricted versions most probably will introduce cracklings.

Tested devices
Devices which support at least 512 kbit/s SBC
1MORE iBFree
JBL Everest 310
JBL Everest 700
JBL T110BT
JBL E55BT
JBL T460BT
JBL Endurance SPRINT (Claim to not support Dual Channel, but work if forced. Does not conform to A2DP specification.)
Skullcandy HESH 3
SoundPEATS Q30
Sony WH-H900N
Sony WI-C400
Sony MDR-1ABT
Sony MDR-ZX770BT
Sony MDR-ZX770BN
Sony MDR-XB650BT
Sony MDR-XB950B1
Sony SBH50
SVEN AP-B570MV
Syllable G600
Bluedio A/Air (Claim to not support Dual Channel, but work if forced. Does not conform to A2DP specification.)
Bluedio T4s (Bitpool max 39. Claim to not support Dual Channel, but work if forced, 462 kbit/s. Does not conform to A2DP specification.)
Bluedio T5 (Claim to not support Dual Channel, but work if forced. Does not conform to A2DP specification.)
Bluedio T6 (Claim to not support Dual Channel, but work if forced. Does not conform to A2DP specification. Adopt Max 97220 chipset.)
Marshall Major II Bluetooth
Overdrive RealForce D1
DEXP BT-210
DEXP BT-220
DEXP BT-250
DEXP BT-260
DEXP BT-280
Edifier W288BT
Edifier W830BT
Nomi BT 211
LeEco Le Sports BT
Xiaomi MI Portable Bluetooth Speaker
Xiaomi Square Box Bluetooth Speaker 2
Sennheiser HD 4.40BT
AKG K845BT
Beyerdynamic Amiron Wireless
Bowers & Wilkins PX
Bowers & Wilkins Zeppelin Wireless
House of Marley Liberate XLBT
Harman Kardon Onyx Studio 4
Harman Kardon Aura Studio 2
QCY QY8
Panasonic RP-BT10
Jaybird X3
Logitech BT Adapter
TP-Link HA100
Xiaomi Mi Bluetooth Audio Receiver
Overfly Portable Bluetooth Receiver
KZ Wireless Bluetooth Module
Excelvan B7
Hagibis X2
Pioneer SE-E7BT
Automotive DAC Lusya bluetooth 4.0 with AK4490, NE5532
Noname automotive head unit (CSR8645 chip)
Sony DSX-A400BT automotive head unit
Devices which support SBC higher than 512 kbit/s
JBL Everest 310 (617-660 kbps)
JBL T110BT (576 kbps)
JBL Endurance SPRINT (573 kbps)
SoundPEATS Q30
DEXP BT-210 (617 kbps)
DEXP BT-220 (617 kbps)
DEXP BT-260 (617 kbps)
DEXP BT-280 (617 kbps)
Sony WI-C400 (576 kbps)
Sony MDR-ZX770BT (617-660 kbps)
Sony MDR-ZX770BN
Marshall Major II Bluetooth (617-660 kbps)
Overdrive RealForce D1 (730 kbps, dual channel, 4 subbands)
Jaybird X3
QCY QY8 (617 kbps)
Edifier W288BT (617 kbps)
Panasonic RP-BT10 (596 kbps)
LeEco Le Sports BT (617 kbps)
Nomi BT 211 (617 kbps)
Xiaomi Mi Bluetooth Audio Receiver (576 kbps)
Overfly Portable Bluetooth Receiver (617 kbps)
Automotive DAC Lusya bluetooth 4.0 with AK4490, NE5532 (576 kbps)
Devices which don't work with higher bitrates or Dual Channel
Harper HB-202 (cracklings; Beken BK3256 chip)
Sony Ericsson MW600 (high frequency distortion, cracklings; device from 2009)
Sony SBH52 (too slow to handle packet rate)
BlitzWolf BW-F2 (no sound)
Overfly mini Bluetooth receiver (no sound)

Why this is important: SBC 328k and 485k vs aptX
Contrary to popular belief of aptX sound quality, in some cases it can produce worse audio quality than SBC with a standard 328k bitrate.
SBC dynamically allocates quantization bits for frequency bands, acting on a "bottom-to-top" basis. If the whole bitrate was used for the lower and middle frequencies, the upper frequencies are "cut off" (silenced).
aptX quantizes frequency bands with the same number of bits constantly, which makes it a constant bitrate codec: 352 kbps for 44.1 kHz, 384 kbps for 48 kHz. It can't "transfer bits" to frequencies that are mostly needed in them. Unlike SBC, aptX will not "cut" frequencies, but will add quantization noise to them, reducing the dynamic range of audio, and sometimes introducing crackles. SBC, on the contrary, "eats the details" - discards the quietest areas.
On average, compared to SBC 328k, aptX makes less distortion in music with a wide frequency range, but on music with a narrow frequency range and a wide dynamic range SBC 328k sometimes wins.
Let us consider a special case, a piano recording. Here's a spectrogram:
The most energy lies in the 0-4 kHz frequencies, and lasts up to 10 kHz.
The spectrogram of the file aptX file looks like this:
Here is SBC 328k:
It can be seen that the SBC 328k periodically completely cut off the range above 16 kHz, and used all available bitrates for ranges below this value. However, aptX introduced more distortions into the frequency spectrum audible by the human ear, which can be seen on the subtracted original spectrogram from the aptX spectrogram (the brighter, the more distortion):
While the SBC 328k has introduced less distortion the signal in the range from 0 to 10 kHz, and the rest has been сut:
Bitrate 485k for SBC was enough to save the entire frequency range, without cutting off the bands.
SBC 485k on this audio sample is much better than aptX in the range of 0-15 kHz, and with a smaller but still noticeable difference - at 15-22 kHz (the darker, the less distortion):
Switching to a high-bitrate SBC, you will get a sound superior to aptX most of the time, on any headphones.

Bro. The concepts sound amazing.
I have Le Max 2 (Oreo). I have attached Bluetooth .so files.
If you patch I will try on Sony Bluetooth system and share with my friends patched files to see how much it works.
Thanks.

rohit3192 said:
Bro. The concepts sound amazing.
I have Le Max 2 (Oreo). I have attached Bluetooth .so files.
If you patch I will try on Sony Bluetooth system and share with my friends patched files to see how much it works.
Thanks.
Click to expand...
Click to collapse
For some reason I can't download your file, always get 404 not found. Another person with LeEco LeMax 2 (x820) contacted me and I made a patch, but only for 32-bit library. Since your archive is >2 MB, I suppose it contains 32 and 64 bit libraries. Please write your exact OS version and build number.
Would you mind to try? Backup your files first, replace 32-bit library with the file from the archive and rename 64-bit library, so it won't be used, and follow the instructions in the second post to capture the dump and upload it to btcodecs.

OK .
I try. Allow me some time.
Yes both libs were in one file. Now sending you separate libs.

rohit3192 said:
OK .
I try. Allow me some time.
Yes both libs were in one file. Now sending you separate libs.
Click to expand...
Click to collapse
Try these.

I have replaced file in /system/lib with permission.
And renamed /lib64 file as instructed.
Bluetooth switch doing nothing.
After renaming lib64 to original name the Bluetooth switch works and connects.
Build no attached.

rohit3192 said:
I have replaced file in /system/lib with permission.
And renamed /lib64 file as instructed.
Bluetooth switch doing nothing.
After renaming lib64 to original name the Bluetooth switch works and connects.
Build no attached.
Click to expand...
Click to collapse
Please try the latest archive. It includes patched 64 bit libraries.

The new patched 64bit file worked.
Tried 486 one only.
Here is Bluetooth log. (Upload was too slow at given link so sending GD link)
Post edited: thanks @ValdikSS a lot.

rohit3192 said:
Here is Bluetooth log. (Upload was too slow at given link so sending GD link)
Click to expand...
Click to collapse
Yes, it worked, the bitrate is 485 kbit/s. Did you hear any cracklings or interruptions?
The audio you played is of low quality. That's probably an MP3 ~160-192 kbit/s?

There is no crackling. Yes mp3 was of low quality that I tested.
Yet sound seems improved. I will need more time to get proper impression. I will post later here.
Also I have spread the word in few telegram channels.
Thanks

@op here you have my lib from Huawei P9 Android 7.0
Can you check and modded to test. I be test on my LG HBS910 with aptx
https://mega.nz/#!G3gR3RrC!yNysYtkk1DhlBk-ec87bIP56aupCwKvfiWM1k32Qy7k

chudy_85 said:
@op here you have my lib from Huawei P9 Android 7.0
Can you check and modded to test. I be test on my LG HBS910 with aptx
Click to expand...
Click to collapse
Patched version has been added to the second post.
This sound enhancement is only for SBC codec, it won't do anything with aptX. You should disable aptX to test patched version.

Hello
I have 1more ibfree sport headphone that supports AAC HD codec only with apple devices as company has mentioned in their site. (https://india.1more.com/collections...ore-ibfree-sport-bluetooth-earphones-with-mic)
As in your post you have mentioned 1more ibfree, that support aptx codec .
My headphone is newer version of ibfree series.
So the problem is in developer setting I can't change to AAC from SBC codec.
It stays to SBC only so I think I can get help from here from you.
So here the link to those .so files
https://mega.nz/#F!tj5AlahL!yCrNHYB-ft-zaJl2uc7kig
Phone - Le Max2 Lineage Oreo 8.1

AdityaDharewa said:
Hello
So the problem is in developer setting I can't change to AAC from SBC codec.
It stays to SBC only so I think I can get help from here from you.
Phone - Le Max2 Lineage Oreo 8.1
Click to expand...
Click to collapse
Please capture a dump and upload it to https://btcodecs.valdikss.org.ru, you'll see all codec information which the device supports.
And by the way, patched libraries for Le Max2 Oreo are already in the second post, give them a try.

ValdikSS said:
For regular users
Send me your bluetooth stack libraries: /system/lib/hw/bluetooth.default.so and /system/lib64/hw/bluetooth.default.so (if it exists).
Click to expand...
Click to collapse
Hmmm those files don't exist on my device (Pixel 2 XL, Pie 9.0 stock OS)

LeifAlbor said:
Hmmm those files don't exist on my device (Pixel 2 XL, Pie 9.0 stock OS)
Click to expand...
Click to collapse
/system/lib/libbluetooth.so and /system/lib64/libbluetooth.so for Android 9.

ValdikSS said:
/system/lib/libbluetooth.so and /system/lib64/libbluetooth.so for Android 9.
Click to expand...
Click to collapse
Done

Custom Android OS for the Ampire AMX090-4K

Hi,
my uncle has just installed the Ampire AMX090-4K with an android box in hs car and would have a custom rom on it to customize for example the boot logo, etc.
My question is: Is ist possible to install a custom ROM, that will 100% working and without any lags? I'm not sure to look to ROMS for a tablet or android tv or if it's ok, if it's okay to onstall a normal ROM like LineAgeOS.
>>Device<<
Specs:
- Cortex-A53 64bit, Octa-cores CPU
- Android 7.1 operating system
- ARM Cortex-A7 platform
- 2G DDR3
- Integrated 16GB flash memory
- 2 USB / Micro-SD card readers (max.128GB)
Display Specs:
- Digital 22.9cm (9``) LED display (New Grade A)
- capacitive G + G multipoint touchscreen
- Panel Model: YRTD090S40B-IPS
- resolution 1024 (H) x 600 (V)
- Brightness 350 cd / m²
- Contrast 800: 1
- Viewing angle 170 ° horizontally, 170 ° vertically
- 4K video decoder
- NTSC / PAL playback automatically
- The display is subject to ISO 9241-307, pixel error class II

Fleischwurst200 said:
Hi,
my uncle has just installed the Ampire AMX090-4K with an android box in hs car and would have a custom rom on it to customize for example the boot logo, etc.
My question is: Is ist possible to install a custom ROM, that will 100% working and without any lags? I'm not sure to look to ROMS for a tablet or android tv or if it's ok, if it's okay to onstall a normal ROM like LineAgeOS.
>>Device<<
Specs:
- Cortex-A53 64bit, Octa-cores CPU
- Android 7.1 operating system
- ARM Cortex-A7 platform
- 2G DDR3
- Integrated 16GB flash memory
- 2 USB / Micro-SD card readers (max.128GB)
Display Specs:
- Digital 22.9cm (9``) LED display (New Grade A)
- capacitive G + G multipoint touchscreen
- Panel Model: YRTD090S40B-IPS
- resolution 1024 (H) x 600 (V)
- Brightness 350 cd / m²
- Contrast 800: 1
- Viewing angle 170 ° horizontally, 170 ° vertically
- 4K video decoder
- NTSC / PAL playback automatically
- The display is subject to ISO 9241-307, pixel error class II
Click to expand...
Click to collapse
ROMs are built specific to the hardware that it is to be installed on. If no one has built a ROM for the specific model number of the device, you won't be able to install a custom OS on the device.
To determine if a ROM exists for that specific device, do a Google search for:
"Custom ROM for (the specific model number of the device)"
If that doesn't find anything, you're out of luck unless you you build or port a ROM for the device yourself.