yashsingh1/xdaforums huggingface dataset:
[Google Home] xdvitoriom:
Is anyone else having audio issues?

I'm trying to run a game (Alto's Adventure), and none of the sound effects or music play through the speaker. (The game runs fine otherwise.) When I connect a Bluetooth speaker, all the system sounds come out of the ThinkSmart View speaker, and all the game audio comes out of the Bluetooth speaker.

It seems to be something about that whatever kind of audio that game is generating, as I can manually upload an MP3 and hear it on the built-in speaker through the Files app.

Using Magisk, I've tried patching audio_policy_configuration.xml, audio_platform_info.xml, and audio_platform_info_extcodec.xml to force various routes to use the speaker (or wsa-speaker, whatever that is) backend, but no dice. I've compared those files across the different firmwares posted in OP and didn't find any material differences. I've also installed acp 2.5, which didn't seem to make a difference.

Anyone else experienced this? Any resolution? Is there something else I should try patching?

Edit 8/23: I've attached logcat and dumpsys media.audio_flinger logs, after a fresh firmware flash, nothing installed except for Alto, one set run after a reboot without a Bluetooth speaker connected, the other run after a reboot with a Bluetooth speaker connected, both after launching Alto. There are definitely a bunch of ACDB, audio_hw_primary, msm8916_platform, audio_route, etc. messages in the no-Bluetooth logcats which aren't present in with-Bluetooth. The most obvious difference in the dumpsys is that the Bluetooth outputs have AUDIO_OUTPUT_FLAG_NONE on their AudioStreamOuts, whereas the speaker outputs all have various flags set, but I don't really know what I'm looking at.
[Google Home] KacperA:
Anyone managed to start notifications bar? I've modiffied build.prop and have softkeys back, but can't find out how notification bar is blocked
[Google Home] marszyszk:
Are somebody tried to run Google Assistant on it , are that possible? I tried Alexa Voice Assisatnt and only Ultimate Alexa app is working ok.
[Google Home] jalohax:
Do you have any idea where configuraiton of kiosk app is? Is there any way to keep it but start with Mozilla/Chrome browser "as" kiosk mode?
[Google Home] Dismal.:
Can you use treble on this device?
[Google Home] Dismal.:
Has anyone tried qemu.hw.mainkeys=0
[Google Home] randomraffa:
I recently got one on Amazon, shows some developer options already but it doesn't show developer permission when I tap 7 times compilation and cannot flash or anything since it won't be detected by adb. Am I missing something or newest devices come blocked. Help, please
[Google Home] randomraffa:
It is a zoom version za69
[Google Home] Duongnguyen96:
This method can apply for JBL link view

I had it stuck on demo mode
[Google Home] deadman96385:
You used the firmware from here? Or from somewhere else? That is very surprising its similar
[Google Home] Duongnguyen96:
From here

I can’t find fw original for JBL link view
[Google Home] Duongnguyen96:
So, can i use this rom for JBL link view?
[Google Home] deadman96385:
Oh I see what happened you typo'd your message and said "This method can apply for JBL link view" instead of "this" is should have been "Can this". I would not flash the firmware from this device on yours.
[Google Home] D200P13:
2024-01-26 20:13:22.895 20:13:22: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.

2024-01-26 20:13:22.896 20:13:22: ERROR: function: sahara_main:924 Sahara protocol error

2024-01-26 20:13:22.897 20:13:22: ERROR: function: main:303 Uploading Image using Sahara protocol failed

2024-01-26 20:13:22.898 Download Fail:Sahara Fail:QSaharaServer Fail:process fail

i cant seem to flash it. just got it out of the box and tried it. am i doing something wrong? i have a macro and a smart switch so as soon as it detects the device, the button is clicked like 002 in time difference from the log above

where do i put Firehose/Rawprogram ?

the semi works tho i just want to root it!
[Google Home] Jagsta211:
are you on windows? i had to use:

bcdedit /set testsigning on

in cmd to get it to flash without error
[Google Home] D200P13:
yes tried both without it i dont see a com connection
[Google Home] adeelmysore:
Try different port and cable. That worked for me
[Google Home] deadman96385:
I have added 2 more firmware zips to the OP for completeness sake, as well as updated the bootloader section to remove the warning because it can be used to more easily flash the device. You just need to bootloader unlock, fastboot flash whatever you need to and then fastboot flashing lock and the device will bootup fine because it does not validate the partitions when locked.

Firmware added:

200809.091 Teams & Others (Untested but probably ADB is turned on by default)

200423.074 Teams & Others (ADB Turned on by default)
[Google Home] D200P13:
what is the difference between 201006.099 and 200628.084 ? are they different android versions?
[Google Home] deadman96385:
It is the same android version for all of them, I haven't looked in depth but most likely minor bug fixes and updated apps.
[Google Home] Xi07:
Finally got my hands on it and I installed a full android!!!

The steps I've been taking:

1) replace recovery.img with the modified recovery.img in the folder with the installation files (CD version-18781Y.210228.109_Teams)

2) flash via QFIL

3) at the first launch, load IMMEDIATELY into twrp (vol+)

4) transfer from a computer to a tablet

open_gapps-arm-8.1-pico-20220215.zip

downloaded from

https://opengapps.org /

ARM platform, Android:8.1 Variant: pico

5) on the tablet in twrp, install - open_gapps-arm-8.1-pico-20220215.zip

6) delete dalvik cash, boot up the system

7) download - the welcome screen with an error, BUT! ADB works, if not, turn off and turn on the USB wire (from this moment on, do not restart the tablet!)

8) run ADB shell - write commands

am start -a android.settings.SETTINGS

pm uninstall -k --user 0 com.microsoft.skype.teams.ipphone

pm uninstall -k --user 0 com.kingston.kioskmodeapp

pm uninstall -k --user 0 jp.co.fsi.fskaren.lenovo

pm uninstall -k --user 0 com.microsoft.windowsintune.companyportal

pm uninstall -k --user 0 com.microsoft.teams.ipphone.admin.agent

pm uninstall -k --user 0 com.kingston.devicesettings

9) run ADB install

NavigationBar.apk

(and activate the NavigationBar in the settings - accessibility - NavigationBar - ON)

Nova+Launcher_v7.0.57(70057).apk

10) Disable Google Play, Google Play servisis and Google Settings Assistant in the application settings.

11) connect the tablet to wifi (if an error pops up again - run the ADB shell on the computer - write the command

am start -a android.settings.SETTINGS)

12) IMPORTANT! set the correct time and date (according to your GMT) - and use the network time

13) go to the settings in applications and notifications - default applications

- select the main application OOBE

14) press the middle key on the control panel

15) there is a standard launch - language selection - connection to WiFi

16) Nova+Launcher is loading

17) Enable Google Play, Google Play servisis in the settings. google Settings assistant delete.

added photos to the instructions

Sorry for the low quality
[Google Home] Lassic:
Hello all! I just got one of these and started out trying to flash it but im getting this issue:

13:33:09: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.

2024-02-09 13:33:09.726

2024-02-09 13:33:09.727 13:33:09: ERROR: function: sahara_main:924 Sahara protocol error

2024-02-09 13:33:09.727

2024-02-09 13:33:09.728 13:33:09: ERROR: function: main:303 Uploading Image using Sahara protocol failed

Firmware: CD-18781Y.210507.111

Turned off driver signing?: yes

Tapping on firmware doesn't do anything

did "bcdedit /set testsigning on"

tried a couple of the different firmware options

adb shows no devices and fastboot device just sits on waiting for any device.

using QFIL 2.0.1.9

have tried multiple cables and USB ports

Anything else I can try?
[Google Home] Pjtruslow:
power cycle it again holding the volume up and down buttons. usually this happened to me because I had just flashed something and didn't fully power cycle it before. I have my testing tablet plugged into a smart plug to make this easier.
[Google Home] Lassic:
Yea have been powering it up while holding vol up and down and having it booting in to the black screen with the PC recognizing it (does the bloop) but still getting the same issue :/
[Google Home] tylerknowsnothing:
I was having the same issues. The COM port started working after I ran optional updates in Windows 10, which apparently updates a component related to that function. Note, however, that none of the other drivers will be fixed or apparently work. Just the COM port. It was enough for me to get mine to sideload the necessary apps for semi-working status. HTH! :D
[Google Home] giga8yte:
I spent a day with the same issue using my sons windows 10 desktop pc. finally realized it only had USB 3.0 ports.... Dug out an old laptop with a few USB 2.0 ports and installed windows on it. Flashed perfect the first time. If you dont know how to tell the inside "tongue" of the usb port is blue if its 3.0
[Google Home] desidude2000:
Alright guys. I’ve done it. After mucking with it quite a bit, I have a brick on my hands on. Unit will no longer even power on to the Lenovo logo. How do you open this thing? Any tear down pics or videos ?
[Google Home] vel0x:
Does it boot into EDL mode? If yes you can restore one of the images from the first post.

Here's a video of a teardown:

Not sure what you're expecting to find though.

There are EDL testpoints but it's probably easier to just get an EDL Cable (aka "Deep Flash Cable") off Amazon or Aliexpress and force it into EDL mode that way.
[Google Home] desidude2000:
Not able to get into the EDL mode either with the standard “press both volume buttons and release” at boot time. Will search Amazon for the cable mentioned. If you have any additional detail on “forcing it into an EDL mode”, please let me know. What does the cable you mentioned do differently than the usually usb-c cable and hold both volume buttons down sequence?

Thanks again !
[Google Home] Xi07:
Have you tried to unlock the bootloader with these commands

fastboot flashing unlock_critical

fastboot oem unlock ?

If so, all you need is to lock the bootloader.
[Google Home] desidude2000:
It is hard bricked. No adb. No fastboot. No EDL. Unit acts like it doesn’t even power on and i have a meter (kill-a-watt) that confirms that adapter isn’t drawing any current when attempting to power on the unit.

Hopefully a “force EDL” cable can get the unit to talk to flash chip at least and I can program it.

FWIW, I never unlocked the boot loader. I was mucking with it quite a bit, especially through Magisk that likely put it on this state. Oddly, it booted a couple of times just fine before rebooting right away and dying a miserable death, never to wake up again.

Very very odd behavior indeed!
[Google Home] Xi07:
Does the power supply itself work?
[Google Home] desidude2000:
Yes. It’s able to power on another device (requiring similar voltage), specifically an ASUS router. And when the router is plugged in, wattage used jumps to 4 watts as the router is powered on, hence the power supply is good as far as I can tell.
[Google Home] Xi07:
As far as I know, in Qualcomm Emergency Download mode, the electricity consumption is very low, less than 1 watt. Moreover, what needs to be done to break a chip with a locked bootloader? I would recommend checking the power supply and USB connections again before disassembling the device.
[Google Home] ramkhcts:
After flashing the Zoom firmware 210602.2103 its boots up fine but does NOT allow any functions and prompting to upgrade zoom .. is there a latest firmware for Zoom ? / any alternatives . btw great work to bring life in to otherwise dead CD-18781Y :)
[Google Home] deadman96385:
With the zoom one flashed you may be able to use the Lenovo rescue/smart assistant to flash the latest zoom firmware. I know the teams one can so I assume zoom as well.

Rescue and Smart Assistant (RSA) - Lenovo Support US

support.lenovo.com
[Google Home] protechtedd:
FYI there is a conversation going on on the Home Assistant forum regarding building ROMs for this Lenovo ThinkSmart device: https://community.home-assistant.io/t/lenovo-thinksmart-view-rom-os-development/676324
[Google Home] shizlkazizl:
Has anyone encountered this error in the logs:

mymac@MYs-iMac edl % ./edl qfil bin/rawprogram.xml bin/patch0.xml flash/ --loader=bin/prog_emmc_firehose_8953_ddr.mbn
Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2023.
main - Using loader bin/prog_emmc_firehose_8953_ddr.mbn ...
main - Waiting for the device
main - Device detected :)
sahara - Protocol version: 2, Version supported: 1
main - Mode detected: sahara
Device is in memory dump mode, dumping memory
sahara
sahara - [LIB]: Error: Invalid mode switch

mymac@MYs-iMac edl % ./edl qfil bin/rawprogram.xml bin/patch0.xml flash/ --loader=bin/prog_emmc_firehose_8953_ddr.mbn
Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2023.
main - Using loader bin/prog_emmc_firehose_8953_ddr.mbn ...
main - Waiting for the device
main - Device detected :)
main - Mode detected: sahara
Traceback (most recent call last):
File "/Users/mymac/edl/./edl", line 393, in <module>
base.run()
File "/Users/mymac/edl/./edl", line 295, in run
version = conninfo["data"].version
AttributeError: type object 'req' has no attribute 'version'

Do you think I've got a hardbrick? This occurred while attempting to flash on 200628.084 after A11.
[Google Home] vel0x:
This looks like the device didn't initialize correctly with EDL.

In general these errors can be fixed by using EDL in the following way:

1. Turn device off

2. Start EDL, it will wait for the device to appear

3. Hold down Vol+ and Vol- again before turning the device on and keep holding them until EDL finds the device

Especially the last error happens to me regularly when I start EDL after the device has already been in EDL mode.
[Google Home] shizlkazizl:
Oh, the same error:

sahara - [LIB]: Error: Invalid mode switch
[Google Home] nowakos:
what can I do if the Microsoft selection is not displayed and then when I want to skip bluetooth I get the message that it can't find configuration
[Google Home] shawngmc:
Trying to flash a newly purchased device, running into... issues. So far, I've tried/observed:

I've tried multiple tool/OS combinations:

QFIL 2.0.1.9 (from the post) on Windows 11

This fails with a com port handle error (see below)

QFIL 2.0.3.5 on Windows 11

Same com port handle error

bKerler's EDL tool on Windows 11

Ran into issues with USBDkcontroller. I get "NotImplementedError: Operation not supported or unimplemented on this platform", so I think I'd need to get USBdk working.

bKerler's EDL tool on Fedora 40 with a conda Python

Ran into issues with PyLZMA compilation

QDL on Fedora 40 (see instructions below)

sits at 'Waiting for EDL device'; never triggers

My Teams unit has a newer firmware:

In Device Settings, mine shows CD-18781Y.210507.111

I cannot get mine to enable ADB by clicking on the Firmware version repeatedly. This isn't a surprise, since mine is newer than the latest Teams firmware you have (which is also No ADB).

I've tried a few other troubleshooting steps:

Disabling driver signature verification doesn't seem to make a difference

I've tried 2 Win 11 machines

I've tried multiple USB cables

I've tried USB2 and USB3 ports on my desktop

Any recommendations?

Spoiler content hidden.

Spoiler content hidden.
[Google Home] shlomi490:
Can't get through the Bluetooth settings, I connected 6 devices and it won't let me continue
[Google Home] shlomi490:
Hi, who can help me? I've done all the steps and I can't continue the bluetooth setup, it won't let me continue even though I added a device
[Google Home] Kianouch:
Thank you so much !

I just bought this thing and the setup worked perfectly :)

It's going to replace my crappy Google Nest Hub, I now need to buy a few more ^^

Edit : I only have one annoying issue: I'm blocked in portrait mode for launchers. Same issue with Niagara or Nova, it won't go to portrait mode.

Weird thing is, other apps do not have this issue..
[Google Home] firemanjd:
Web searching I found this thread - I have flashed my Teams Edition to Zoom, but the version of the Zoom app is too old. Has anyone figured out how to update it?

"Zoom Rooms must be upgraded to join this meeting. Please contact IT for assistance."

I can see the device in my Zoom account, there's no option to push an update, not is there any option to update locally on the ThinkSmart itself that I can find.
[MTCD Software Development] VAHID:
hi friends

Dasaita release android 11 in img file

Dropbox

www.dropbox.com

M.I.C ANDROID 11 image file :

https://mic-deutschland.de/Update/3399_Android11_Update.zip

And tools to update:

Dropbox

www.dropbox.com

HCT8 ANDROID 11 OTA UPDATE (20220412 )

update.zip

drive.google.com

telenav_vivid_rk3399_11.0_ota(20220428)

Dropbox

www.dropbox.com

HA3_rk3399_11.0_ota(20220412)

Dropbox

www.dropbox.com

Instructions:

After update you can update your device to any android 11 ota update file
[MTCD Software Development] lagos911:
any way to install from sdcard?
[MTCD Software Development] VAHID:
no yet
[MTCD Software Development] maxiauer:
Besides the usual security patches, and whatever Google added to Android 11 vs Android 10 under the hood... have you noticed any new feature that would be applicable to a Car Stereo?

Also, any noticeable impact on responsiveness?
[MTCD Software Development] localos:
This is ota firmware and can be installed from sdcard

The firmware has not been verified and is used at your own risk

I do not bear responsibility for the bricks!!!
[MTCD Software Development] lagos911:
i dont if you can upgrade the unit just like that... only with the update file...

you need to make the sd card bootable with the bootload of android 11.
[MTCD Software Development] itsfitts:
The unit in the video is max6 1280x720. Will this work for the older 1024x600 model too?
[MTCD Software Development] VAHID:
Yes
[MTCD Software Development] ikepy23:
I've got the PX6 RK3399 1024x600 version too, but on android 9. Will this work to go straight to version 11?

Or should I follow the guide to go to 10 first.

Thanks all.
[MTCD Software Development] marchnz:
Is it an mtcd device post screenshot of MCU from Android system information
[MTCD Software Development] btrcp2000:
do i have to have a usb a to usb a cable to connect the a laptop to the px6? No other way?
[MTCD Software Development] Mauro1950:
Ciao, MCU versione 3.78 va bene per l'aggiornamento da Android 10 ad Android 11 al mio PX6, giusto? Grazie Mauro

Mod translation via GT: Hi, MCU version 3.78 is fine for upgrading Android 10 to Android 11 to my PX6, right? Thanks Mauro
[MTCD Software Development] zyxraid55:
hi mauro where i can find the versio 3.78 please ? thanks Peter
[MTCD Software Development] VAHID:
yes
[MTCD Software Development] lagos911:
Can somebody upload a screenshot of the launcher of those roms. Thanks.
[MTCD Software Development] freeeeenco:
Hi I have this model

View attachment 5625589

View attachment 5625591

can use these files to upgrade?

The radio has never made any updates
[MTCD Software Development] VAHID:
hi friend

yes you can
[MTCD Software Development] freeeeenco:
For the upgrade I have to use

1-FactoryTool

2-HCT8 ANDROID 11 OTA UPDATE (20220412)

3-HA3_rk3399_11.0_ota (20220412)

correct?

You can follow the video for all the steps.
[MTCD Software Development] freeeeenco:
I wanted to know if the same update is possible on a (friend's) PX5 device.

Instead as I wrote above in addition to FactoryTool which rom is recommended for a PX6 device with MCTE_MX_v.3.78
[MTCD Software Development] lagos911:
where do you find hct8 for android 11?

The best way is to create a bootable sd card with the img file with launcher HA3
[MTCD Software Development] freeeeenco:
Hi, so it is better to change the recovery.

I take the file HA3_rk3399_11.0_ota (20220412), and update via sd.

For second I take the file HCT8 ANDROID 11 OTA UPDATE (20220412) always copied to SD and I update to android11.

So you can also not follow the video guide posted.

Thank you
[MTCD Software Development] lagos911:
No you can't do that. To run android 11 your unit must update the bootloader as well. To do that you have to use the img file and create a bootable SD card and make the installation. After that you will be able to use the update.zip with android 11.
[MTCD Software Development] HSaber:
Will this work with any headunit that utilize PX6? and if yes do I have to pay extra care for specific requirements in my headunit ?
[MTCD Software Development] marchnz:
No, is your unit an mtcd or variant
[MTCD Software Development] lagos911:
I try to the img to a sd card but nothing happend. Unit cant boot at all.
[MTCD Software Development] HSaber:
What do you mean by Variant? and I guess mine is MTCD it runs Android 10 out of the box
[MTCD Software Development] marchnz:
Not all rockchip devices are MTCD devices.

What is the MCU version, post screenshot
[MTCD Software Development] HSaber:
Attached the MCU version
[MTCD Software Development] Bettman66:
No MTCD device
[MTCD Software Development] rigattoni:
https://xdaforums.com/t/klyde-px4-p...n2-csn2_d-csn2_8600_d-android-8-9-10.3912413/
[MTCD Software Development] HSaber:
So mine is is not MTCD device and I have to follow the mentioned steps in related thread to do any kind of upgrade to the headunit
[MTCD Software Development] rigattoni:
Yes, exactly
[MTCD Software Development] skezza:
So this won't work with update.zip?
[MTCD Software Development] VAHID:
No
[MTCD Software Development] mistralivo:
buy installer pro 2 from hal9k is the best way to install android 11
[MTCD Software Development] abdelhak01:
hi freind,

please can i update with this file my px6 android 9 six core?

thank you in advance
[MTCD Software Development] P2.nl:
I read this topic with great interest about a possible android upgrade for my PX6 RK3399 / MTCE_MX device.

As the topic video isnt working - can i upgrade my device by simply put both file's on a usb thumb stick ?
[MTCD Software Development] marchnz:
There are free factory methods
[MTCD Software Development] marchnz:
No, see forums
[MTCD Software Development] ikerg:
Depending on your Bluetooth chipset. Some old BT chips are not longer compatible with A10 or A11
[MTCD Software Development] lucky2888:
Hi, so can I update my px6 with these files too? thanks
[MTCD Software Development] marchnz:
Try and tell us your results
[MTCD Software Development] Mc_IZAR:
Hi @VAHID , the link to watch the video is becoming private. Do you have a link to use factory tools and put android 11 on my PX6 because the system is on android 11 on MTCH_MX_V3.80_1. So i want to put the last version. Thanks for reply :)
[MTCD Software Development] ikerg:
If you are already on android 11 ....probably the full image that @VAHID posted (without Dasaita's consent - they removed t

If you are already on android 11 ....probably the full image that @VAHID posted (without Dasaita's consent - they removed the links for.a reason) is older. The way for upgrading within same android version is by means of OTA update. Ask your seller/manufacturer for the latest upgrade available.
[MTCD Software Development] Mc_IZAR:
@ikerg

Sorry, the system is on android 10, and i want to upgrade in android 11, but the video post by Vahid is not available and private, so inaccessible