yashsingh1/xdaforums huggingface dataset:
[Pixel C Q&A, Help & Troubleshooting] hartiberlin:
How can one check, which Codecs are used over Buetooth ?

On my Xiaomi Mi A2 Lite I can somehow enable under Developper Mode the APT-X and LDAC Codecs,

but how can I test it, if it being used e.g. in Skype for Android or other Voice Applications ?

My Blootooth Stereo Headset has Apt-X , but during Skype calls or a Wireless Video Recorder app, it still uses only the 8 Khz SBC bad audio codecs...

Any idea how I can test it and how to enable the Wideband Audio Codecs ?

Many thanks.

Regards., Stefan.
[Pixel C Q&A, Help & Troubleshooting] SoNic67:
It has to support mSBC for handset:

https://www.rfwireless-world.com/Terminology/SBC-vs-mSBC-codec.html

An app like Bluetooth Monitor might show more info about the actual connection.
[Pixel C Q&A, Help & Troubleshooting] mirhl:
Android did definitively support HFP 1.6 by lollipop, if not even earlier (and by nougat it even had 1.7, plus or minus some bugs).

The problem google alleged is that the pixel C wireless controller (a BCM43540LKUBG according to teardowns) lacks SCO, which should be kinda essential for HFP.

But they were wrong, you just need some extra hoops (which funnily enough, they were already half-way through doing).

And it wasn't until 2019 that their engineers finally managed to put up everything together.

I'm afraid they never really plugged it into their older official downstream kernels though.
[Xiaomi Mi 4C] alterbang:
Hello everybody,

I have finally completed version 1 of my device tree for our device.

You can find it at

https://github.com/alterbang/android_device_xiaomi_libra

If you have a working CM local source you can lunch && mka otapackage for the glory :)

A few details:

I forked from xiaomi-dev, xiaobai's testing repo

Copied include folder from https://github.com/CyanogenMod/android_device_xiaomi_cancro

Edited AndroidBoard.mk with an "#alterbang" section with dir creation and patched files copy

Edited BoardConfig.mk with TARGET_SPECIFIC_HEADER_PATH := $(LOCAL_PATH)/include

Added "#alterbang" section with missing files to proprietary-files.txt, and removed a couple files.

BONUS: i have added a script "extract-files-from-miui-zip" to extract files from a miui.zip file (like the roms over at xiaomi.eu) so you can extract them without having to flash miui to your phone :)

ANY COMMENT OR COLLABORATION IS WELCOME

It's the first time i work actively with CM, so have mercy on me :D

I created this project because i believe in collaboration and openness, so get your hands dirty!

Thank you!

alterbang

Build 20160129 DOWNLOAD LINK

https://mega.nz/#!wBVlUJ4D!E-TDy01wNqBuLQvbznNfOd6bfkpPvaAcSePWZdlDXbY

-works: everything

-bugs: wakeup is sometimes slow. if you know how to fix, please tell me :)
[Xiaomi Mi 4C] muff99:
Wow, awesome work!!

I'm not a dev, but I build CM 12.1 for klimtlte and CM 13 for mako (before I got my shiny new Mi 4c ...).

Double thumbs-up for your work on the extract-files-from-miui-zip.sh. Have you thought about uploading the files to TheMuppets github? Would make it even easier to build, and aries and cancro are already there.

Also I like that you shared your findings and how you got it to work and what you used to get it to work, much appreciated!! This is the way to do it in my opinion!

I very much like the idea of running my own build on my phone, however I am not sure if I should put too much effort into 12.1 any more with all the nice CM13 roms getting better and better (Team Superluminals cm13 builds work great on my phone) ... I will keep an eye on your github, though, and might ask your for your local manifest in the future :p

Again, you did great work so far!

Oh, one mroe thing: Whats the state of SELinux with your build? Is it permissive? Or did you or xiobai have an enforcing SELinux working?
[Xiaomi Mi 4C] alterbang:
Thank you muff99!

As for your question: i saw SELinux permissive removed in the mk files, but i don't know if that's enough. I'll let you know!

For Marshmallow / CM13: the idea is to do the same thing also for that branch :)
[Xiaomi Mi 4C] DFurax:
Hey !

Somebody could explain me what are the differences of this version between the Xiaobi one ?

Ty
[Xiaomi Mi 4C] Rhyn:
You can compile this to yourself, you can take part of the development with this tree.
[Xiaomi Mi 4C] AndropaX:
Here are non open source binaries :

https://github.com/AndropaX/proprietary_vendor_xiaomi_libra

Pull requests with updates (from dev version please) are welcome.

Wysłane z mojego Mi-4c przy użyciu Tapatalka
[Xiaomi Mi 4C] dexxa05:
Hi,

I'm new in building ROM, so i'm trying to build rom but it seems local_manifest.xml needed ?! Where i can found it?!

Thx in advance
[Xiaomi Mi 4C] muff99:
I am trying to put together a cm 13 build, this is how my local manifest looks so far:

<manifest>
<remote name="ghub" fetch="git://github.com/"/>
<!-- <project name="thune-xiaobai/android_device_xiaomi_libra.git" path="device/xiaomi/libra" remote="ghub" revision="cm-13.0"/>-->
<project name="xiaomi-dev/android_device_xiaomi_libra.git" path="device/xiaomi/libra" remote="ghub" revision="cm-13.0"/>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="ghub" revision="cm-13.0"/>
<project name="AndropaX/proprietary_vendor_xiaomi_libra" path="vendor/xiaomi/libra" remote="ghub" reviSion="master"/>
...
</manifest>

It seems like Xiaobai is not using his thune-xiaobai Github any more, but he is contributing to xiaomi-dev, so I chose that device tree as did [MENTION=3965705]alterbang[/MENTION].

[MENTION=479071]dexxa05[/MENTION]:

Thnx! You sure the dev roms are a good source? After this locked-bootloader news I am hesitant to use dev rom files ...

Got until this one:

make: *** No rule to make target `/home/freddi/android/system/out/target/product/libra/obj/KERNEL_OBJ/usr', needed by `/home/freddi/android/system/out/target/product/libra/dt.img'. Stop.

Seems like [MENTION=3965705]alterbang[/MENTION] ran into this here:

http://xdaforums.com/mi-4c/developm...12-1-mi-4c-t3226541/post64204905#post64204905

Which dependencies did you add to fix this?

Oh btw, I dont wanna hijack your cm 12.1 thread to talk about cm 13 ... should I open another thread?

UPDATE: Oh I just saw all the stuff that you did to your device tree in /include, have to work through that ... cancro already has cm13, looks like there is even a kernel source.
[Xiaomi Mi 4C] alterbang:
that is just a missing dir, search my repo :) and yes please open a new thread! so we can start together on cm13
[Xiaomi Mi 4C] dexxa05:
Hi Guys,

Small issues i'm trying to build 12.1 but the system try to build 13.0

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=6.0.1
CM_VERSION=13.0-20160119-UNOFFICIAL-libra
TARGET_PRODUCT=cm_libra
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=cortex-a53
HOST_ARCH=x86_64
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.2.0-4-amd64-x86_64-with-debian-7.9
HOST_BUILD_TYPE=release
BUILD_ID=MMB29T
OUT_DIR=/home/dexxa05/android/system/out
============================================

Do you know how to change that?!

Thx in advance
[Xiaomi Mi 4C] muff99:
How did you init your repo? You have to do it like this, I guess:

repo init -u https://github.com/CyanogenMod/android.git -b cm-12.1

Also, check the "revision" attribute in your .repo/local_manifests/*.xml files, it should be "revision="cm-12.1" " for you
[Xiaomi Mi 4C] croperas:
Is that from the latest MIUI?
[Xiaomi Mi 4C] AndropaX:
From china dev rom 6.1.11

Wysłane z mojego Mi-4c przy użyciu Tapatalka
[Xiaomi Mi 4C] AndropaX:
Ok, now updated to 16.1.14
[Xiaomi Mi 4C] alterbang:
Great job AndropaX :)
[Xiaomi Mi 4C] polovinamozga:
Where you got kernel sources for mi4c?
[Xiaomi Mi 4C] alterbang:
Nowhere, i'm still using a prebuilt kernel...

We're still waiting for Xiaomi to comply to GPL.

And unfortunately nothing seems to indicate that's happening soon.
[Xiaomi Mi 4C] alterbang:
sup :)
[Xiaomi Mi 4C] alterbang:
Updated the first post with the flashable zip :)
[Xiaomi Mi 4C] ermacwins:
Is it possible to have the snapdragon camera on cm12.1?
[Xiaomi Mi 4C] alterbang:
sure, the flashable zip was already posted somewhere in other threads.
[Xiaomi Mi 4C] s2k7:
Not boot

:crying:

Thanks for your great effort.

Following your device tree, I built a rom myself, but it DID not boot.

After comparing your flashable ROM and my rom, I found there were some files missing.

Please confirm the attached pictures.

May I ask you to modify your device tree ?

Here is the list.
[Xiaomi Mi 4C] alterbang:
It's really strange, the zip i posted was build with my device tree.

I'll double check my commits to github to see if there's something missing in the device tree, or maybe in other folders.

Thank you for the feedback!
[Xiaomi Mi 4C] technoking2020:
Thanks for your Great Work!

Will try your Rom and revert back here!
[Xiaomi Mi 4C] alterbang:
[MENTION=358669]s2k7[/MENTION]

I found some differences in vendor folder, so i have uploaded my skeleton (to fill with proprietary files).

I also decided to include xiaobai's kernel folder (which doesnt'contains kernel source, but it does have includes and header files) to provide a more-than-complete build environment.

I committed changes so sync my repo, and also please add these to your build environment and let me know!

android-vendor-xiaomi-libra

android-kernel-xiaomi-libra

Good luck :)
[Xiaomi Mi 4C] s2k7:
Cannot finish compiling. End with errors.:crying:

Please help.
[Xiaomi Mi 4C] HiroyukiIkezoe:
The reason why the image did not boot is that libEGL_adreno.so is placed at a wrong position. It should be /system/vendor/lib64 instead of /system/vendor/lib64/egl/.
[Xiaomi Mi 4C] s2k7:
I reverted your latest commit, then the compiling finished well.

The phone booted without WIFI.:crying:

But I can check if my two sims work.

The base rom is xiaomi.eu_multi_libra_V7.1.4.0.LXKCNCK_v7-5.1.zip.
[Xiaomi Mi 4C] HiroyukiIkezoe:
You need to create a symbolic link qca_cld_wlan.ko to wlan.ko in somewhere. init.qcom.wifi.sh. is commonly used for the purpose. Like this:

--- a/misc/init.qcom.wifi.sh

+++ b/misc/init.qcom.wifi.sh

@@ -497,6 +497,11 @@ case "$target" in

msm7630*)

;;

+ msm8992*)

+ rm /system/lib/modules/wlan.ko

+ ln -sf /system/lib/modules/qca_cld_wlan.ko \

+ /system/lib/modules/wlan.ko

+ ;;

*)

;;
[Xiaomi Mi 4C] wolkenjaeger:
I really hope you all keep this little project running. I am currently not able to do any build by myself, but really appreciate the time all you guys invest here! :laugh:

(Speaking of, is it possible to update the image always with the latest Android Security Patch Version, to have the security features enabled?)
[Xiaomi Mi 4C] emfox:
any progress on cm13 tree?
[Xiaomi Mi 4C] alterbang:
none at the moment.

i'm testing TS CM13 roms and until we have kernel sources (official or not) i guess another tree it wouldn't be much of use, their roms are already pretty good.

so...any progress with the kernel? :)
[Xiaomi Mi 4C] emfox:
Not yet. kernel hacking is a little difficult for me and I have no much time to devote into it.
[T-Mobile Samsung Galaxy Note5] fozzy501:
Hello all, I found this post regarding Samsung Pay

...........Link removed.......... ~~~ moderator

http://xdaforums.com/showpost.php?p=64758413&postcount=55

It looks like a good way for a fix, however I am currently went from root to stock.

Can anyone confirm?
[T-Mobile Samsung Galaxy Note5] guaneet:
I claim for it to be fake. Triangle away does not support new sammy devices since they introduced e-fuse. Hasn't been updated since 2014.
[T-Mobile Samsung Galaxy Note5] Ducter:
Misleading post title wouldn't you say? We can follow the thread about samsung pay in the post you refer to without having this one.
[T-Mobile Samsung Galaxy Note5] oka1:
From the Moderator

Not real .......... So ...

.................Thread Closed................
[Moto G 2015 Q&A, Help & Troubleshooting] ucimad:
Hey everyone, i always read the the forum for answers but for the first time i havent find the answer for my problem.

So i have a Moto g 2015 and while trying to unlock and root, i ended up with a bricked phone.

I can get to the recovery mode and i can also use ADB & Fastboot on my PC.

the message that fastboot mode show on my screen is the following.

AP Fastboot Flash Mode (Secure)

Bl: 80.90 (sha-1e3d83c, 2015-06-05 09:55:30)

Baseband: (not available)

product/Variant: osprey xt1540 8gb P2B

serial: Zy2222JH6H

CPU: MSM8916

eMMC: 8GB Micron RV=06 PV=12 TY=17

DRAM: 1024MB Elpida S8SDRAM DIE=4Gb

Console [NULL]: null

Battery OK

Device is UNLOCKED. Status Code: 3

Software status: Official

Transfer Mode: USB Connected

Any ideas on how to Restore it back to life?

Thanks in advance
[Moto G 2015 Q&A, Help & Troubleshooting] vinz244:
How did you bricked it? Also, have you tried to flash stock?

Envoyé de mon MotoG3 en utilisant Tapatalk
[Moto G 2015 Q&A, Help & Troubleshooting] B00j:
Flash stock rom 5.1.1 and then update to 6.0. I ended up in the same position when I tried to root my phone. Find the osprey thread and follow the instructions how to flash stock rom
[Moto G 2015 Q&A, Help & Troubleshooting] just_another_guy:
Similar Problem Here

I too need help with my soft bricked moto g3 (xt 1550, Indian dual sim 16 gb version).:D

I officially upgraded to 6.0.0 via ota and my objective was to root my phone and use xposed modules. I am not interested in any other custom rom (I'd rather keep stock rom just for moto displayand ota upgrades) or custom recovery like twrp(I'm afraid it may cause ota upgrades to fail).

I used the method described here in the question- http://android.stackexchange.com/qu...rsu-using-play-store-versus-a-custom-recovery

So I first successfully unlocked my bootloader using the official motorola method.

I then proceeded to use google's backup settings to re-install all the apps that were uninstalled due to unlocking the bootloader. I also put supersu.zip version 2.46 on internal sd card.

I then proceeded to (without rebooting) enter fastboot where i used minimal adb to temporarily boot into twrp version2.8.7 r5 (link - http://xdaforums.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537 ).

Once in twrp, I located and flashed the supersu.zip. It flashed successfully. I procceded to clear dalvik cache and then after clearing cache I tried to reboot my phone using twrp.

However, it did not go beyond the "Warning - Bootloader Unlocked" screen that you get on unlocking a motorola bootloader.:( I left it for over 10 minutes (usb was still plugged in, I had >80% battery) but it did not proceed.

Long -pressing the power button causes the phone to vibrate and again attempt to boot, stuck at the same initial screen. Adb quite understandably does not work here.

I can press vol down+power and enter fastboot , where adb works fine.

I can enter stock recovery from the fastboot sceen too.

Using adb in fastboot, I am able to boot twrp . In fact, I tried to re-install supersu.zip. I retried version 2.46 and then tried version 2.56. On all occcassions, it was able to successfully flash it, but gets hung on the initial boot screen.

USB Debugging is also enabled, and I have a backp of my sd card data.

I tried taking a backup of the system and apps in twrp (3 gb in total) and tried to reflash it, but it still hangs at the same screen.

Is there any way I can unbrick my device and- (in decreasing order of preference)

1. Keep my stock rom and recovery?

2. Keep stock rom with twrp? (It should not be a problem)

3. Custom rom with custom recovery - perhaps official cm. Least preferred as I want Moto Display and stock/vanilla android.

Also, is SELinux involved anywhere with my phone getting bricked? :confused:I also read that a custom kernel is required for rooting 6.0, which I don't have. Supersu Version 2.56 is said to prevent soft bricks if the kernel is incorrect (systemless root), yet even after flashing the newer one it is still bricked. Where am I going wrong? What should I do? Thanks in advance! :good: :D
[Moto G 2015 Q&A, Help & Troubleshooting] Yousvel:
I've just flashed MM factory image for XT1544 on my XT1540 and it's working perfectly good. Just give it a try!

I used these commands in one go:

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system system.img_sparsechunk.6

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn

fastboot erase cache

fastboot erase userdata

fastboot reboot
[Moto G 2015 Q&A, Help & Troubleshooting] MrTooPhone:
I am in the exact situation. I fortunately made a backup prior to flashing SU. I was successful (only once) to fastboot a TWRP image. When trying to restore backup, TWRP said “cannot restore system–mounted read only”. So when I retried to boot TWRP, I no longer can fastboot. In linux, adb indicated unknown device (only after selecting ”Apply update from ADB”). Windows ADB does find the device. But fastboot does nothing in either OS. I still have the option to factory reset. Looking for advice.

Update, using TWRP, selected mount and unchecked read only, backup was restored. Still trying to decide best method/version for systemless SuperSU

Update2...SuperSU 2.62-3 successfully flashed with no issues.
[Moto G 2015 Q&A, Help & Troubleshooting] Mendelyeev:
Did you use fastboot erase all??
[Moto G 2015 Q&A, Help & Troubleshooting] MrTooPhone:
What does "fastboot erase all" do?

If a nadroid backup exists, that will bring you back.
[Moto G 2015 Q&A, Help & Troubleshooting] Mendelyeev:
"fastboot erase all" erases all partitions on android. (imei and modems too), so, NEVER USE IT.
[Moto G 2015 Q&A, Help & Troubleshooting] vinz244:
Jus a silly question: if you make a fastboot erase all can't you just restore everything if you backed up all partitions previously using nandroid backup?

Envoyé de mon MotoG3 en utilisant Tapatalk
[Moto G 2015 Q&A, Help & Troubleshooting] Mendelyeev:
Any question is not a silly question! ;) The nandroid does not backup the efs partition (where imei is stored). If you want backup, you can search forum. There are many posts offering scripts to do this without major problems.
[Moto G 2015 Q&A, Help & Troubleshooting] sieze.s:
I also soft bricked my phone but got it back.

Follow below steps and you are good to go -

1. Download and install Motorola Moto Drivers

2. download stock firmware from http://xdaforums.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639

3. download TWRP from http://xdaforums.com/devdb/project/?id=11051#downloads [ i used twrp-osprey-2.8.7-r5.img version ]

4. download SuperSU from http://xdaforums.com/showpost.php?p=64161125&postcount=3 [make sure you download BETA-SuperSU-v2.62-3-20151211162651.zip version only else you'll again brick your phone]

Now as you have all required things to get your phone back, now follow below steps -

Now flash stock ROM, Instruction here -> http://xdaforums.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750

Now flash TWRP - fastboot flash recovery your_recovery_name_here.img

now start your phone (takes 15 minutes around)

now go to recovery and flash BETA-SuperSU-v2.62-3-20151211162651.zip and start your phone [ do not allow TWRP to root your phone when it asks you to root your phone just tap not now (or whatever i don't remember right now)]

Starting up phone now takes 25-30 minutes approx.

Rooted :)

[Don't brick and blame me :D , do it at your own risk ]
[Moto G 2015 Q&A, Help & Troubleshooting] theankitkulkarni:
First flash system firmware.. then flash TWRP recovery.. then Flash BETA-SuperSU-v2.62-3-20151211162651.zip SuperSU Package.. Done..
[Moto G 2015 Q&A, Help & Troubleshooting] DPJulien:
try this guys

http://xdaforums.com/2015-moto-g/help/tuto-fastboot-erase-signal-t3451362#post68445534
[Shield Tablet Q&A, Help & Troubleshooting] sthetix:
Fixed by reflashing the stock firmware.

thanks!
[Huawei MediaPad X2] bark1234:
**************

Currently it seems there is no way to update incremental files in emui 4.0, unless you get it from huawei directly. Updater has no option of local update now. Some people told me that unzipping zip file and placing update.app from zip in dload folder and then pressing power+volup+volminus during boot, they are able to install update. Can someone confirm this.

Btw i have successflly updated these files as i got it from huawei direclty(my imei is on beta list)

***********

Update : 24th March

EMUI 4.0 is out of beta now. B209 is out, exepct to receive direct update from huawei soon. Meanwhile you are welcome to update from file i am sharing. You need to be on B208 to apply this update.

link : http://bit.do/B209zip

Whats new : quite stable.

----------------------------------------------------------------------------------------------------------------------------------

Update : 12th Mar

B205 to B208 update has come. This is again beta build. You need to be on B205 to upgrade using this zip. Process to goto B205 is written below. Rooting and other processes are all same.

link : http://1drv.ms/24W4VU2

----------------------------------------------------------------------------------------------------------------------------------

Update :4th Feb

Here is beta build for GEM 703L only.

You need to be on B112 to apply this update zip.

Process :

- Be sure you are on B112 and unrooted.

- reame the downloaded file to update.zip and place it in dload folder in sd card.

- Goto Updater > Menu > Local Update > apply update.

- thats it.

Whats new :

- Android 6.0 beta.

- Will update anything else if i come to know.

How to Root :

- Get SuperSu 2.67 from here : http://download.chainfire.eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip

- Install twrp recovery. For process search this forum.

- Before installing supersu zip, in twrp go to Advanced and enter Terminal Command and type in "echo SYSTEMLESS=true>>/data/.supersu"

- This will force SuperSU to use systemless root which will patch the bootloader instead of the system and work root properly.( Thanks to ajsmsg78 for pointing out)

How to get back to 5.1 :

- After installing twrp, make sure you have any twrp installable rom on sd card.

- Goto twrp recovery and wipe system(must), data, cache.

- install twrp installable zip rom. reboot.

Note : This is beta build and may not be perfect. If you screw up your device, only you are responsible.

Download link : http://1drv.ms/1X52Vna

----------------------------------------------------------------------------------------------------------------------------------

Many of you would be aware 1 batch of beta(B202) is already released. I was not one of them to get the update. Hoping to be in the second list.

Meanwhile if anyone has got hold on the update file, please share it here.

Btw i am expecting to get in 1 week or so.
[Huawei MediaPad X2] bark1234:
Reserved
[Huawei MediaPad X2] mcdhol_24:
OMG I love it already despite being a beta version. The display can be fully switched to a tablet experience without any bugs on icons. It is looking good already but I'm sure bugs on other elements (e.g. camera) will be fixed with each update. :)
[Huawei MediaPad X2] mtyler7807:
Installing now.
[Huawei MediaPad X2] ajsmsg78:
Hmm......to install this and rom it, or not to install it yet. That is the question. I hope they don't encrypt the boot.img on Marshmallow on the X2. The Mate 8 ships with an encrpyted bootloader and although I have a rom for it there are a few major bugs I haven't been able to figure out how to fix yet. Someone let me know if TWRP works on this and I'll put together a ROM.
[Huawei MediaPad X2] hagba:
Is this reversible back to B112, just in case..??