Related
WARNING:
This update zip use write mot_boot_mode as shell script to run bootmenu,
don't modify it. otherwise, maybe you will get stop at M logo.
NOTICE: This update zip is ONLY for mb511, if you want to update, please check your stock rom.
If you use this update zip at charm(mb502), is unstable, mb502 and mb511 still has some different.
My STOCK ROM VERSION:
Code:
RUTEM_U3_01.14.16_DEBLUR_SIGNED_USARUTH15ND0RTINT056.0R_PDS000_USARUTHEHKTWEMARA_P011_A010_HWp3_1FF.sbf
If you try to call, but can't hear sound or can't registration of the carrier network, try this ROM version to update RC version.
RC version 5: v0.7.4
configure sources
NOTICE:If you want update fix zip, you should use bootmenu to update.When boot at motologo,click click and click "vol -" to enter bootmenu.
->because bootmenu executed by mot_boot_mode, so /system can't umount, only can remount.
--and update zip have to modify updater-script, remount /system.
[2013/11/13]:
last update:
Seems we can use the command of telnetd to do emergency rescue.
I write telnetd as shell script. It's only to execute bootmenu, if someone modify mot_boot_mode maybe cause bootmenu can't execute.
The telnetd will execute by eclair's init_mapphone30_umts.rc. But it's only can use bootmenu to execute adb to do some things (ex. modify mot_boot_mode).
These days, I try using 2ndboot, but still freeze on hbootmod, I don't know why we can't execute hbootmod.
I can't find anything solution, and can't get more message.
For me, it's hard to debug, I'm not kernel developer. I try to understand the source code of hbootmod, should stuck on do_branch.
But I still can't get any idea to solve this question.
Hope someone can complete it, let we can use new kernel.
RC version 5 should can be a stable version.
[2013/10/04]:
RC version 5:
Seems when I try fix camera, has incorrect modify of sensors. Fix incorrect modify.
write shell script /etc/init.d/07cphostapconf, copy /system/etc/wifi/softap/hostapd.conf to /data/misc/wifi/hostapd.conf
modify updater-script, clear /data/dalvik-cache. if already upgraded previous version update zip, should can direct flash RC5, skip double wipe.
[2013/09/26]:
20130926.zip:
I forget modify configure sources of buttonblink.sh.
old buttonblink.sh file will get bad battery life.
[2013/09/19]:
20130919.zip:
According to this, use smartass is more stable, thanks edgarsongla.
modify init.mapphone30_umts.rc, set smartass as default and delete cpufreq_interactive.ko.
[2013/09/18]:
for traditional chinese user:
fork tcime unofficial for flipout.
upload tcime.apk for flipout.
source code
[2013/09/16]:
baseband:
use and modify cyanogenmod4milestone's configure files of mmparts.
but I'm not do full test, should be ok.
reduce reboot times:
seems wakelock cause reboot, I guess.
these steps maybe can reduce reboot times.
disable wi-fi or don't set wi-fi sleep policy at never.
disable Android debugging.
but maybe still has reboot problem. I can't find solution.
[2013/08/28]:
camera:
use and modify CyanogenKobe's configure of libcamera.
fix part of camera. Take picture is normal, solved rotation 90 degree problem. But video recorder still rotation 90 degree.
wifi:
use stock rom's files.
media:
add libraries of 720p files. but 720p still has problem.
[2013/08/15]:
fix part of magnetic sensor, tested by google map.
modify lights code. when enter standby to check notification, if exist set buttons backlight on.
and if already standby when get notification, set blink and backlight on.
delete /system/etc/init.d/99buttonblink, modify /system/xbin/buttonblink.sh(for enter standby and exist notification use).
[2013/08/08]:
seems write to Android services will get bad use of battery.
so write to /system/etc/init.d/99buttonblink, to start service (check blinking of buttons backlight).
[2013/08/01]:
fix notification blinking of buttons(menu, home and back) backlight.
[2013/07/03]:
find the way to compile tiap_drv.ko
-->if get error, try this command then reboot.
Code:
cp /system/etc/wifi/softap/hostapd.conf /data/misc/wifi/hostapd.conf
modify overlay of auto brightness and notification LED.
[2013/06/26]:
use CyanogenModXT720's libaudio.so, ril should be normal.
use CyanogenModXT720's dsp directory.
get some kernel modules from CyanogenModXT720.
-->seems tiap_drv.ko can use, but still has problem, try to fix in next version.
[2013/06/23]:
define open keyboard of orientation by overlay.
modify BoardConfig.mk.
use cyanogenmod4milestone's apns-conf.xml.
use "mka bacon" to compile cm7.
separate gapps:
-->attachments gapps.zip for bootmenu use.
can work:
camera
battd
fmradio
bluetooth
gps
sensors
usb connect
audio
half work:
video
-> 720p has problem.
wifi
->I only use 2G service, so I can't test softap.
ril
->I only use 2G service, so I can't test 3G.
use mknod to replace mv /dev/xxx
[2013/04/01]:
resume original parameter in init.mapphone30_umts.rc
->symlink /dev /dev/netmux
I don't know why I deleted it...
modify /system/bootmenu/2nd-init/init.rc:
/mnt/sdcard -> /sdcard
modify void.fstab:
/mnt/sdcard -> /sdcard
delete /system/etc/init.d/02movedevice
fix sdcard mount question.
replace files by upload zip, and delete /system/etc/init.d/02movedevice. Or wait release new version.
fix in preview version 2.
In terms of audio recorder, following information may help:
Flipout uses Sample Rate '16KHz' or "22KHz" to record sound, NOT '44KHz'. This is why flipout cannot use skype >_<. If you guys are using a recorder that uses Sample Rate "44KHz" (which almost all recorders set as default Sample Rate), you have to change the setting.
No phone to test
>.<
Sorry guy I can't help
May be I can help to fix this bugs.audio,fmradio,sensors,camera,ril&wifi,look this:https://github.com/xn-Dream/android_device_motorola_sage-1,and you can pm me else.
Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.
sim unlock problem
Hi, first thanks for do this ROM :good:
I install but when start now the system want to give a sim unlock code, I was use before so do u have any idea or something that i have to do to solve this problem
Sorry for my english is not my native language
Best regards
phchshow said:
Seems use mb508's libaudio.so can use video(low quality,landscape orientation) and audio recorder.
-- hard decoding still problem, can use some player (like mxplayer) to play with soft decoding.
-- Spirit FM will be no sound.
-- call phone number still no sound.
[2013/04/02]:recompile cm7 with mb508's libaudio.so
Now we can hear sound from the other side , but the other side can't hear what I say .
But use speaker it's no problem.
Click to expand...
Click to collapse
error log
about 3G
3gw.Service 7225 Mobile Network not connected - not roaming
about codec
Error TIOMX_CORE 2045 dlopen libOMX.TI.720P.Decoder.so failed because Cannot load library: load_library[1111]: Library 'libOMX.TI.720P.Decoder.so' not found
Info TI_Video_Decoder 2045 TI Video Decoder
Error OMXCodec 2045 Profile and/or level exceed the decoder's capabilities.
Error MediaPlayer 16597 error (1, -2147483648)
Error MediaPlayer 16597 Error (1,-2147483648)
Error MX.Player.Joint 16597 1st error: what=1 extra=-2147483648
Use 508 libOMX.TI.720P.Decoder.so put into system/lib
Error OMXCodec 2048 [OMX.TI.720P.Decoder] ERROR(0x80001009, 1)
I'm impressed that you finally got it working, but i have a evil kind of Bug around here!
The Play Store vanishes every Reboot, Titanium says it is Frozen and im unable to unfreeze it.
If i can i would provide a logcat in the next hours!
Anyway, awesome to finally see 2.3.7 on MB511 ^^
//EDIT: I connected the Device with the Internet, now it is working fine ^^
everything is working except that when phone reboot version is still 2.1 and nothing changed :/
adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Integrate to fix-20130413.zip.
phchshow said:
adout keylayout:
unzip keylayout.zip
--init.mapphone30_umts.rc
--init_prep_keypad.sh
to /system/bootmenu/2nd-init/
chmod 0644 /system/bootmenu/2nd-init/init.mapphone30_umts.rc
chmod 0755 /system/bootmenu/2nd-init/init_prep_keypad.sh
Click to expand...
Click to collapse
Is This QWERTZ?
Should be QWERTY.
There are two files, ruthp0-keypad.kl and ruthp1-keypad.kl.
use this command
"cat /proc/device-tree/[email protected]/[email protected]/name"
My device get ruthp1-keypad.
If you want to use QWERTZ, you can try replace ruthp0-keypad.kl, ruthp1-keypad.kl, ruthp0-keypad.kcm.bin and ruthp1-keypad.kcm.bin.
Get from QWERTZ version.
ShockBuddy said:
Is This QWERTZ?
Click to expand...
Click to collapse
Maybe can solved Turn on USB storage problem.
Integrate to fix-20130413.zip.
if replug usb, maybe has problem, use killall com.motorola.usb to reset usb.
Hi to all,
Thanks to all that are working on this rom.
Since both models are merged in the same post because the same hardware, I wonder if I can deploy this rom into a Motorola Charm, or if I got to make changes on code, I guess at least have to change some files where refers to 511 to 512, and where refers "Ruth" to "Charm".
What other changes should I do to make this model work?
Thanx for response.
Please help
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!
just the key pad related files, I was unable to compile this ROM from source using charm files, I think an update file to replace keypad files with charm should do the trick.
I shall try it and let you know.
there are so many attachments here
please put them into #1
Great job, men!
netmanmac said:
Please help me, How do i do to work because i have not service,
The problem is SIM NETWOR UNLOCK PIN
Please HELP!!!!
Click to expand...
Click to collapse
I dont have the Issue and i haven't inserted any SIM Card, it should be enough to reboot without Sim Card.
If you get to Homescreen, use a Root Explorer and edit /system/build.prop, check if
Code:
keyguard.no_require_sim=xyz
is set to "false", if it isn't in there, add it!
Hope i helped :fingers-crossed:
finally installed.is the screen orientation working good?when i flip out the keyboard the screen orientation remains protrait,pretty annoying!anyway great job,never though i'd have seen cm on flipout!love this device,unlike any other
** DoPa6 (AOSP - Marshmallow) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
** DoPa5 (AOSP - Kitkat) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
DoPa v2.7 is a ROM for Sero 7 Pro owners everywhere. Whether bought in the US, Britain, Australia, Germany, or elsewhere, your tablet is supported.
The ROM starts with well-tested AOSP code and adds core functions where needed but skips the frills that are easy to add on - and remove when they cause problems. It's aimed at people who want to choose their own features and not have them imposed by the developer.
New / Improved
International Support - a single ROM for all Sero 7 Pros sold worldwide
New in v2.7 - support for the German model of the Sero 7 Pro (m470bsg)
Speed Control - a unified kernel provides speed when you need it and stock performance when you don't.
Use the new Performance page in the Settings app to control it
exFAT - support has been moved into the kernel for improved performance
Boot Animation - a handsome new DoPa animation thanks to @mikembley, our first-ever UK user
To get you started customizing your ROM, v2.7 offers these add-ons:
built-in: SuperSU, Xposed Installer GravityBox, Phab7
optional: have your tablet claim it's a Nexus7 to get more apps in PlayStore
The package does not include any Google apps (e.g. Playstore). See this thread for links to the latest GApps packages.
Installation
UK / AU / DE / First-time Users
If you're upgrading from a stock ROM (any variety), please click the "show content" button and read the instructions very carefully - they're long but your tablet's continued good health may depend on it!
STEP 1: Install Philz Touch Recovery
Users outside the US must use this version of Philz to install the ROM - neither the stock recovery nor other versions of CWM or Philz will work. Users in the US should use it just to avoid problems.
Stock Recovery
If you still have the stock recovery program you'll have to use the 'fastboot' program to install Philz. On Windows, this requires installation of the 'ADB' USB drivers while in fastboot mode (see below). A package containing the drivers, fastboot, adb and other files can be found in the 2nd posting on the DoPa Stock ROM thread. Note: there are several batch files (*.bat) in the package - do NOT run them.
put fastboot.exe in a convenient directory, then unzip sero7pro-philz6.58.0-dopa-v2.7.zip and put the file philz.img in the same directory (you won't need the other files)
unplug any USB cable, then press and hold Power+VolumeUp; the word "fastboot" should appear on the screen (nothing further will appear)
plug the USB cable from your PC into the tablet, then install the driver (open Device Manager, right click on "Other Devices->Fastboot", then select "Update Driver Software")
after installing the driver, open a command prompt ("DOS window") and change to the directory containing the files
enter fastboot flash recovery philz.img
when done, force the tablet off, remove the USB cable, then reboot into recovery: Power+VolumeDown - you should see the word "recovery", then the Philz menu
CWM
If you have CWM installed, copy sero7pro-philz6.58.0-dopa-v2.7.zip to an SD card, insert it in the tablet, then:
remove any USB cable, then boot into recovery: Power+VolumeDown
select "Install Zip", then "Choose zip from /storage/sdcard1"
select the file, then OK the selection
when done, back out to the main menu, select "Advanced options", then "Reboot recovery"
after the initial "recovery" screen, you should see the Philz menu
Regardless of how you install Philz, the result should be the same. If it boots OK, compatibility is assured
STEP 2: Backup
I can't emphasize this enough: you must make a backup of your existing ROM. If something goes wrong, there's no way to get your device working again other than to restore it using the backup you've made. There's also another reason to do a backup: before installing the new ROM, you will have to reformat your /data partition. This will wipe out your apps, your settings, and most importantly, all the music/photos/etc stored on your "internal SDcard". These last items can be restored if you follow the instructions below:
ROM
You must do your backup onto a real SD card that you can remove because your "internal SDcard" will be erased in the next step. In fact, it wouldn't be a bad idea to do two backups (preferably to different cards) just in case one is faulty.
on Philz main menu, select "Backup and Restore"
next, select "Backup to /storage/sdcard1" (the 6th item on that menu)
if there's enough space on the card, the backup will start without any further prompt; it could take anywhere from 3 to 15+ minutes depending on the amount of data and the speed of your card
if needed, you can enable compression to create a smaller backup: select "Misc Nandroid Settings -> Default Backup Format -> tar + gzip", then on the previous menu, tap on "Compression" to set the appropriate level
Internal SD card
This is optional but worthwhile if you have files you value stored on the tablet:
on Philz main menu, select "Backup and Restore"
next, select "Custom Backup to /storage/sdcard1" (the 9th item on that menu)
on the next screen, deselect everything, then select "Backup /data/media" (the next-to-last item)
finally, select "Start Custom Backup Job"
STEP 3: Install the DoPa ROM
Before you begin, you may want to download a Google Apps ("Gapps") package that you can install after the ROM. See this thread for a selection of packages. To avoid complications, I'd suggest choosing the "Nano Modular Package" to get just the basics - you can always upgrade later. Put your Gapps package along with the ROM zip on an SD card and insert it into the tablet - you can use the same card you're using for your backups.
on Philz main menu, select "Wipe and Format Options", then "Custom Format Options"
select "format /data and /data/media (/sdcard)" (the 8th item), then OK your choice
back on the main menu, select "Install Zip -> Choose zip from /storage/sdcard1"
select sero7pro-aosp444-dopa-v2.7.zip, then OK your choice - the install process should take about 40 seconds
next, install your Gapps package
return to the main menu, select "Reboot System Now", then hold your breath for the next 3-4 minutes
the Hisense screen should be up for less than a minute, followed by the DoPa boot animation for another 2-3 minutes
when the Google setup screen appears, you'll probably get a warning that "Bluetooth Sharing" has stopped - after you clear it, you'll never see it again
If the boot animation is still running after 5+ minutes, force the tablet off, then reboot. If that doesn't fix it, try formatting /data again. If it still doesn't work, restore your tablet from your backup ("Backup and Restore -> Restore from /storage/sdcard1"), then post a message here. If everything works out as hoped for, re-read the first posting in this thread for details on some of the features (and problems) of this ROM.
Upgrades
While any SELinux-enabled version of CWM or TWRP can be used to install the ROM, the companion Philz Touch CWM-based recovery is highly recommended if you use exFAT-formatted SD cards.
from DoPa AOSP Kitkat ROMs (v1.0-v2.6) - no need to wipe or format anything!
from pre-Kitkat (v4.4.x) or any CM-based ROMs - wipe your /data partition before installing to avoid unnecessary problems.
install sero7pro-aosp444-dopa-v2.7.zip
- the installer will wipe (but NOT format) /cache and dalvik-cache for you
install your preferred Gapps package
- upgraders: this is required to prevent your downloaded Google apps from crashing
optionally, install the Nexus7 spoof (sero7pro-nexus7spoof-dopa-v2.7.zip)
reboot (ignore any "fix root" prompt - it's incorrect)
f2fs / ext4 Migration
This DoPa ROM gives you the flexibility to format any of your built-in partitions using either the f2fs or ext4 file systems.
As part of your install - or at any time - you can switch formats without losing any data. Click "show content" for instructions.
If you haven't already installed Philz Touch Recovery, please do so first. Philz has gotten complicated, so read this carefully!
make a nandroid backup to your external SD card
select Wipe and Format Options, then Custom Format Options
select toggle f2fs <-> ext4 migration
- be sure there's a confirmation message at the bottom of the screen
select each partition you want to convert or wipe, then select the format and OK your choice
Important: to convert your /data partition, you must select format /data and /data/media (/sdcard)!!!
use Custom Restore from /storage/sdcard1 to restore the contents of the partitions you reformatted
Notes
Speed Control - this version uses a redesigned kernel that caps processor speeds at stock levels during start-up, then adjusts them once the tablet is up and running. Go to Settings->Performance to enable this feature, and to set the top speeds for the CPU (1.0-1.5ghz) and GPU (448-520mhz). When disabled,the processor will remain at stock speeds (1.2ghz/448mhz) unless changed by a 3rd-party app.
Encryption - the first time you formatted your /data partition, you lost the ability to encrypt your tablet's data. Using the companion Philz Touch Recovery to reformat /data (using either filesystem) will restore that ability. To preserve your existing data, do a backup first, then restore just /data when done. Note: you must select "format /data and /data/media (/sdcard)" when reformatting.
OTG Charging Support - this kernel supports charging the tablet while an external device (flash drive, keyboard, etc.) is attached to the USB port. This feature requires either an OTG 'Y' cable or an OTG USB hub, and the AC adapter that came with the tablet. For this to work, power must be connected to the cable or hub before plugging it into your tablet. The OTG device(s) can be attached/detached at any time.
WiFi Display (a.k.a. Miracast) - video works but its performance may depend upon your TV; audio does not work.
Bluetooth Sharing - on the initial boot, this service will FC due to a timing issue. The system will restart it and you should never see this error again.
Added/Changed in v2.6
International Support - added support to the kernel for the British and Australian models of the Sero 7 Pro
Overclocking - replaced separate standard and overclocked kernels with a unified kernel that uses less power when overclocked; added a new Performance page to the Settings app to control it
exFAT Support - moved exFAT support to the kernel for improved performance
Boot Animation - added a custom boot animation created by @mikembley
Added/Changed in v2.51
Flexible Formatting - added F2FS support for the /thirdparty and /mnt/modem partitions
Bug Fix - enabled Philz Touch Recovery to format the /thirdparty and /mnt/modem partitions using EXT4
Added/Changed in v2.5
Flexible Formatting - enabled use of either F2FS or EXT4 for any of the built-in partitions
External Storage - added support for F2FS, and for devices formatted without a partition table (i.e. Windows-style "super-floppies")
Android version - upgraded from AOSP 4.4.4_r2 to AOSP 4.4.4_r2.0.1
Recovery - added a DoPa version of Philz Touch Recovery
Added/Changed in v2.1
SD Cards - added support for SD cards formatted with the NTFS or exFAT filesystems
Android version - upgraded from AOSP 4.4.4_r1 to AOSP 4.4.4_r2
Added/Changed in v2.0
Google Now - voice activation (i.e "OK Google") now works in the Google Now launcher
kernel - added OTG charging support.
Credits
ziddey
randomblame
davepmer
the CM team
Downloads
sero7pro-aosp444-dopa-v2.7.zip the full ROM
sero7pro-nexus7spoof-dopa-v2.7.zip identify tablet as a Nexus7 to (possibly) show more apps in PlayStore
sero7pro-philz6.58.0-dopa-v2.7.zip a customized version of Philz Touch CWM-based Recovery v6.58.0
sero7pro-format-thirdparty.zip - only needed if you are downgrading from DoPa6 (Marshmallow) to previous versions (i.e. this one)
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
Thanks man been running it since day one no problems and very stable.
Can We call these the Semi OFFICIAL ROM ?
I installed v1 after it booted up play store wasn't installed. Did any one else experience this? I did a dirty flash and a full wipe.
Sent from my Sero 7 Pro using xda app-developers app
How much free space should there be on a system after a fresh install?
datboy143 said:
I installed v1 after it booted up play store wasn't installed. Did any one else experience this? I did a dirty flash and a full wipe.
Sent from my Sero 7 Pro using xda app-developers app
Click to expand...
Click to collapse
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that. I still have some testing to do and will report back later.
Gazoo119 said:
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that. I still have some testing to do and will report back later.
Click to expand...
Click to collapse
Ok will do thanks
Sent from my SGH-I777 using xda app-developers app
GPS and Google music
I noticed on version 0 that GPS could take awhile to lock on, and if you turned it off and back on that sometimes it wouldn't lock on at all. I also noticed an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build? Otherwise, this is one of the cleanest KitKat builds I've used
gotshores said:
I noticed on version 0 that GPS could take awhile to lock on, and if you turned it off and back on that sometimes it wouldn't lock on at all. I also noticed an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build? Otherwise, this is one of the cleanest KitKat builds I've used
Click to expand...
Click to collapse
Don't use Google music but I do use scanner radio and whenever I switched streams the tablet would freeze and I would have to hold the power button to turn the tablet off.
Now its working like it should. So this latest build might fix Google music.
Another issue I was having is when I opened the calendar it would not close hitting the back button. Its closes fine now.
The GPS doesn't seem to load any slower for me than it did with the stock ROM but I don't use it much.
Anyway I would recommend trying this latest build. Just make sure you wipe cache and dalvik cache and flash the latest gapps. Everything should still be the same as before when you boot with the new ROM and hopefully you will notice some improvements.
---------- Post added at 07:31 PM ---------- Previous post was at 07:22 PM ----------
dolorespark said:
This is a plain-vanilla build of KitKat for those who prefer their enhancements added on rather than built in.
Click to expand...
Click to collapse
Just want to thank you for fixing the sound bug. V4A is working perfectly and as far as I can tell so is everything else. I will keep testing and if I run across anything strange I will post here. Your work on this is very much appreciated
dolorespark said:
This is a plain-vanilla build of KitKat for those who prefer their enhancements added on rather than built in. The only changes to the AOSP and kernel code are those needed to ensure compatibility or to enable standard features Hisense omitted (e.g. USB-OTG support). Because it relies on well-tested AOSP code, it is likely the most stable KitKat ROM available for this tablet. For the same reasons, it is almost certainly not the fastest KitKat ROM either.
To make it more functional, the package includes a handful of apps most people find useful: SuperSU, ES File Explorer, Xposed Installer, GravityBox, and my Phab7 UI switcher. To avoid the wrath of Google, it does not include any GApps; see this thread for links to the latest packages.
Installation
Having an SELinux-enabled version of CWM or TWRP installed is a prerequisite. You can find versions built by randomblame here or by davepmer here.
If you're upgrading from v0 of this ROM, clearing cache and dalvik-cache should suffice. Otherwise, do a full wipe of both your data and cache partitions. As always, a backup of your existing setup is recommended.
Notes
All features should be present and work as expected with these exceptions:
WiFi Display (a.k.a. Miracast) - video is enabled but very slow; audio is disabled because it doesn't work and generates 45 error messages per second when enabled
SELinux - the kernel runs in permissive mode due to missing entries in its configuration.
As these issues are resolved, the ROM will be updated accordingly.
Credits
randomblame
davepmer
the CM team
Download
sero7pro-aosp442-dopa-v1.zip
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
DoPa
Click to expand...
Click to collapse
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)
chopin_k said:
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)
Click to expand...
Click to collapse
This is normal..
Sent from my Sero 7 Pro using XDA Premium 4 mobile app
enfermo said:
Can We call these the Semi OFFICIAL ROM ?
Click to expand...
Click to collapse
Generic, yes - (semi-)Official, no.
datboy143 said:
I installed v1 after it booted up play store wasn't installed.
Click to expand...
Click to collapse
Gazoo119 said:
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that.
Click to expand...
Click to collapse
As noted in the OP, none of the GApps (e.g. Playstore) were included in this ROM. I have updated its verbiage to be even more explicit. As to GMail crashing, I'm a little puzzled how that could happen if it wasn't included - did you mean the generic Email app?
gotshores said:
I noticed on version 0 [...] an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build?
Click to expand...
Click to collapse
I hope not: v1 wouldn't have been released if that bug were still present. The problems you encountered were caused by enabling sound effects, either built-in or 3rd-party - the notes for v0 said as much. Perhaps Google Music enabled them automatically.
chopin_k said:
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)
Click to expand...
Click to collapse
I ran into that too - and something even odder. SuperSU's su and daemonsu program files should have a flag that marks them as authorized to give root access. That flag is now missing but I can still get root whenever needed. I don't know if this is to be expected with SELinux in place or just something specific to SuperSU. I'll investigate...
tinybeetle said:
How much free space should there be on a system after a fresh install?
Click to expand...
Click to collapse
After installing the ROM, the "Gapps Standard" package, and Antutu, Settings->Storage says I have 5.48gb available. This is the free space on your /data partition and includes the space used by your emulated SD Card (which is actually just a subdirectory of /data).
"Smart ass alert"
Not only was playstore not installed, it doesn't give me the winning lottery numbers for next week! What gives?
Ok, being serious, Thank you for your time and effort. This weekend I am going to finally give this a try.
Dolorespark,
I haven't messed with any sound effect settings, so it must be Google Music messing with things. Have you noticed any issues with GPS? I can run any of the other rom's, including CM11, and it locks on immediately, but it seems random with AOSP. Sometimes I'll wait a coupled of minutes and it'll get a lock, and other times it won't lock on at all. Anyway, thanks for all you do. I'll keep testing, and keep my trusty backup of DOPA v2.
Working brilliantly so far. V0 to V1 smooth after adding gapps back to the mix. Sounds like time to reinstall V4A and sync some commute podcasts!
Thanks Dolorespark!
envygreen said:
Working brilliantly so far. V0 to V1 smooth after adding gapps back to the mix. Sounds like time to reinstall V4A and sync some commute podcasts!
Thanks Dolorespark!
Click to expand...
Click to collapse
intermittently get google services has stopped.... only that but everything looks good so far.... anything to fix google services stopping? also had a root fix need after rebooting, did yes and everything is ok... thanks DOPA....
dolorespark said:
I hope not: v1 wouldn't have been released if that bug were still present. The problems you encountered were caused by enabling sound effects, either built-in or 3rd-party - the notes for v0 said as much. Perhaps Google Music enabled them automatically.
Click to expand...
Click to collapse
I had this issue on v0 as well and it seems that it's not gone yet. I only wiped dalvik & cache coming from v0 so I'm not sure if that's part of the problem, but I'm still experiencing the Google Play Music crash. It only seems to crash when playing content that hasn't already been cached locally. Attached is a logcat.
dolorespark said:
As noted in the OP, none of the GApps (e.g. Playstore) were included in this ROM. I have updated its verbiage to be even more explicit. As to GMail crashing, I'm a little puzzled how that could happen if it wasn't included - did you mean the generic Email app?
Click to expand...
Click to collapse
No it was gmail. It would close followed by the message "unfortunately this application has closed" or something like that. It wasn't really crashing but rather would not stay open. Anyway flashing the latest gapps fixed that and all is good for me so far.
I played with the tablet extensively last night and did not experience any problems. Even movies, streaming or local using XBMC play using a bluetooth headset. There is no stuttering as there was in all of the previous Jelly Bean roms, stock....DoPa1 and DoPa2. I don't know if that was a KitKat fix or what but I am very happy with the stability of this rom and the fact the XBMC bluetooth bug was fixed is icing on the cake. Of course V4A makes it even better.
I will continue to run the rom and will post if I find any bugs. Thanks again.:good:
Been running since v1 was posted. Have to say the music bug is no more! Listening to lucky mixes all day today and email, g+, and everything my wife and kids have done on it. No problems! Thanks You have really taken your time to make this rom perfect!!!!
Gazoo119 said:
[gmail] would close followed by the message "unfortunately this application has closed" or something like that. It wasn't really crashing but rather would not stay open. Anyway flashing the latest gapps fixed that and all is good for me so far.
Click to expand...
Click to collapse
nccruz said:
intermittently get google services has stopped.... only that but everything looks good so far.... anything to fix google services stopping?
Click to expand...
Click to collapse
Did you use the latest GApps package? As Gazoo119 noted, that fixed a problem with another app that uses Google Play Services. If the problem persists, you may want to go to Apps->Google Play Services, then tap the "Manage space" button. On the next screen it lets you clear all data.
gotshores said:
Have you noticed any issues with GPS? I can run any of the other rom's, including CM11, and it locks on immediately, but it seems random with AOSP. Sometimes I'll wait a coupled of minutes and it'll get a lock, and other times it won't lock on at all.
Click to expand...
Click to collapse
I hadn't tried GPS at all until you mentioned it. I installed Google Maps but couldn't get a lock at all. It's raining here, so I couldn't get fully in the clear. Instead I sat in my car and it still did nothing. Finally, I forced-stopped the app, cleared data and cache, then retried. This time it only took a few seconds to find me. I then turned off GPS, rebooted, and moved to my semi-covered patio. After getting everything going again, it took 10-15 seconds to get a rough fix (off about 70 feet) and it continued to hold it even after I went inside. You may want to try clearing Maps' data (if that's what you're using) to see if that helps.
unomar said:
I had this issue on v0 as well and it seems that it's not gone yet. I only wiped dalvik & cache coming from v0 so I'm not sure if that's part of the problem, but I'm still experiencing the Google Play Music crash. It only seems to crash when playing content that hasn't already been cached locally. Attached is a logcat.
Click to expand...
Click to collapse
Whatever crash you're seeing isn't the one that I fixed. That one was produced a full-blown hardware crash with a register dump. Your logcat doesn't show a register dump or even a Java runtime exception dump. There were two errors that caught my eye but I don't know if either would cause an "Unfortunately..." popup.
Code:
04-08 09:40:24.213 E/DownloadTaskImpl( 3156): Download failed because of IO Error: Socket closed
04-08 09:40:24.213 W/DownloadTaskImpl( 3156): Experienced error when trying to download: [mId=[7871, DEFAULT] mTrackTitle="Le onde" mRemoteId=9ea5817b-9753-348e-af52-ea7c0947c6cb mSourceAccount=1954430662 mPriority=3 mOwner=MUSIC_PLAYBACK mSeekMs=0 mRetryAllowed=true mFileLocation=[mFullPath=/data/data/com.google.android.music/files/music/mplayback_7871.tmp mStorageType=INTERNAL mCacheType=2] mExplicit=false]
Here, the (software) communication link being used to download "Le onde" was broken. Later on, you got this error:
Code:
04-08 09:40:57.133 I/wpa_supplicant( 618): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:1a:30:e4:64:00 reason=0
[...]
04-08 09:40:59.803 E/DownloadTaskImpl( 3156): Download failed because of IO Error: recvfrom failed: ETIMEDOUT (Connection timed out)
04-08 09:40:59.803 W/DownloadTaskImpl( 3156): Experienced error when trying to download: [mId=[363, DEFAULT] mTrackTitle="Black Hole Sun" mRemoteId=8076a782-8454-3fd8-899d-213bb23836ac mSourceAccount=1954430662 mPriority=0 mOwner=MUSIC_PLAYBACK mSeekMs=0 mRetryAllowed=true mFileLocation=[mFullPath=/data/data/com.google.android.music/files/music/mplayback_363.tmp mStorageType=INTERNAL mCacheType=2] mExplicit=true]
This download failure is a lot easier to understand: your WiFi connection had dropped. I don't know that either of these is something I can fix. As above, you may want to try the obvious fixes if you haven't done so already: use the most recent GApps package, clear the app's cache and data, and play with the app's caching options.
Hey, my H7 is rooted, and running Emui 4.0 (B320).
I love the phone but i think the sound volume is just too low. I've download Xtreme music package as long as viper4android, but the volume is still too low.
I've try to modify mixer_paths.xml, like i did with my galaxys, but i can't find it with root browser on this phone.
I've tried to modify local_prop in CUST/hw/Eu/prop to remove the volume limitation but there is not the line ro.config.hw.security_volume as it is on other phones. (tutorial for other phones including this technique here: http://forum.xda-developers.com/showthread.php?t=2531673 )
There is no codec folder either, so i can't try the solution by removing it.
There is an Audio folder tho, under system/etc/ and within it, there are a dozen of folder, and one called Hi6402 containing a lot of mixer_paths files like CARRERA DAVINCE GRACE etc, and a lot of mixer_volumes files with the same name. Both have a default version.
There is no line allowing to modify the volume in the mixer_paths.xml file, but there are plenty in the mixer volume one. Could this be it? I don't know what to change, as all the others file have this lines too, and there are plenty of them.
Thanks for the help.
There is a file with a volume security in HW_OEM/PROP, but changing the values didnt change a thing. I'm doing further investigations.
Dude, you're going to break your ears![emoji14]I don't know about managing maximum volume but quick question : you successfully installed Viper4Android?? Last time I tried, drivers won't install correctly and nothing changed when I activated equalizers..
Envoyé de mon PLK-L01 en utilisant Tapatalk
Haha don't worry i'm used to it. Did you instal busybox and/or selinux? They are both needed for the application to work.
Try to download a different version of the application if you still can't install drivers, and check if you are properly rooted.
I couldn't get V4A working either.. Can you tell how it is done? I'm on B320 rooted and busybox installed. I downloaded and installed the Marshmallow-version of the V4A. Do I have to enable it somehow in honor's audio settings because there seems not to be a place where i can choose what audio effect to use? I have also tried several audio players, but does it matter which to use? Driver status says "abnormal" so that's probably the problem..?
kiroileva_fossiili said:
I couldn't get V4A working either.. Can you tell how it is done? I'm on B320 rooted and busybox installed. I downloaded and installed the Marshmallow-version of the V4A. Do I have to enable it somehow in honor's audio settings because there seems not to be a place where i can choose what audio effect to use? I have also tried several audio players, but does it matter which to use? Driver status says "abnormal" so that's probably the problem..?
Click to expand...
Click to collapse
I flashed v4.6 stock from this thread http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
I have Busybox and SElinux changed to permissive and V4A works fine in Lollipop
btb55 said:
I flashed v4.6 stock from this thread http://forum.xda-developers.com/nexus-6/themes-apps/viper4android-t2952137
I have Busybox and SElinux changed to permissive and V4A works fine in Lollipop
Click to expand...
Click to collapse
how do you change selinux to permissive
magnea said:
how do you change selinux to permissive
Click to expand...
Click to collapse
Search in this forum for SElinuxModeChanger app.
Sent from PLK-TL01H
Hello,
since I'm not qualified (yet) to post this in the developer thread for the X compact - here's a LineageOS 14.1 ROM for the device to be flashed with fastboot as stated on Sony's website for the AOSP ROM (fastboot –S 256M flash boot boot.img etc).
filefactory.com/file/5wfgwk1cmzw9/LineageOS-05-03-2017-kugo.zip
Things that don't work so far:
* AudioFX (use PowerAMP or VLC for mp3 replay with bass boost/EQ)
* FM radio (no stations found at all)
Big thanks to the LineageOS team, the SonyLOS guys and Sony itself
Enjoy,
jtk_de
jtk_de said:
Hello,
since I'm not qualified (yet) to post this in the developer thread for the X compact - here's a LineageOS 14.1 ROM for the device to be flashed with fastboot as stated on Sony's website for the AOSP ROM (fastboot –S 256M flash boot boot.img etc).
filefactory.com/file/5wfgwk1cmzw9/LineageOS-05-03-2017-kugo.zip
Things that don't work so far:
* AudioFX (use PowerAMP or VLC for mp3 replay with bass boost/EQ)
* FM radio (no stations found at all)
Big thanks to the LineageOS team, the SonyLOS guys and Sony itself
Enjoy,
jtk_de
Click to expand...
Click to collapse
Hi! Thanks for this rom. I will try it when i am at my home pc. But, a question. It's got a built-in-root? Or we use the add on root package? Or use magisk phh superuser? I'm a little confused about the root process.
Re:
lba810701 said:
Hi! Thanks for this rom. I will try it when i am at my home pc. But, a question. It's got a built-in-root? Or we use the add on root package? Or use magisk phh superuser? I'm a little confused about the root process.
Click to expand...
Click to collapse
To install, as with the Sony AOSP ROM, your bootloader must have been unlocked. After installation via fastboot root access can be enabled in the developer options.
If you want to build the ROM yourself init the LineageOS sources from github (cm14.1 branch) and add the local_manifests folder from SonyLOS (also on github) to the .repo directory to have a device profile and the binary blobs for the X compact aka kugo. Then repo sync, and brunch lineage_kugo-userdebug.
Hi!
I flashed your homemade rom. My first impression, is it's very smooth. But I found some little bugs? First is a LineageOS recovery. I must flash OpenGapps twice, to install it correctly. ( second time i mount the system inside advanced settings... maybe thats the key ) Second one is a fingerprint sensor. I can't make it to work. Neither on first run, neither later in the settings. Phone calling working, but sometimes it's dialer force stop in middle of the voice calling. ( but you could speak, just a notification came up about the FC ). Bluethooth seems ok, about music listening and about calling. Camera with the roms app is working. But, google cam doesn't start. On selfie picture, the picture is upside down. Root is inside developer settings, and it seems working fine. ( except flashfire... ) I'm using kernel toolkit ( v 1.2.1 ), and it's showing me the big cores allways off, and the phone doesn't go to deep sleep. About the battery life time i can't say too much, because the roms is nearly one day on my phone. I think it's a good start the LinageOS 14.1 to our phone. Thanks again.
Re:
lba810701 said:
Hi!
I flashed your homemade rom. My first impression, is it's very smooth. But I found some little bugs? First is a LineageOS recovery. I must flash OpenGapps twice, to install it correctly. ( second time i mount the system inside advanced settings... maybe thats the key ) Second one is a fingerprint sensor. I can't make it to work. Neither on first run, neither later in the settings. Phone calling working, but sometimes it's dialer force stop in middle of the voice calling. ( but you could speak, just a notification came up about the FC ). Bluethooth seems ok, about music listening and about calling. Camera with the roms app is working. But, google cam doesn't start. On selfie picture, the picture is upside down. Root is inside developer settings, and it seems working fine. ( except flashfire... ) I'm using kernel toolkit ( v 1.2.1 ), and it's showing me the big cores allways off, and the phone doesn't go to deep sleep. About the battery life time i can't say too much, because the roms is nearly one day on my phone. I think it's a good start the LinageOS 14.1 to our phone. Thanks again.
Click to expand...
Click to collapse
Thank you for testing. You're right there's some more issues. I was able to unlock the phone with the fingerprint sensor once but I guess this should work a little bit more smoothly. Face camera image is vertically flipped. Normal phone operation seems to be OK, battery runtime also. Didn't examine core load nor install Google apps so I can't say anything about it. All in all it looks quite usable but needs a little bit of fine tuning
Flashed your ROM yesterday (coming from an unofficial cm14.1 build) and till now everything runs smooth. I didn't flash recovery.img since I already had twrp flashed and flashing opengapps was also successful. Fingerprint sensor is working too. The camera quality is bad, but that's what I have with every custom ROM.
Issues I found out so far:
- registering the fingerprint sensor for purchases in the play store doesn't work, play store closes upon trying to set it up
- the volume when calling can't be changed
Maybe there's something else but I'm really satisfied. I hope you keep on updating the rom jtk_de
can you give us a short update on this?
Still Progressing?
Is this still being developed?
The thread seems to have been continued here: https://forum.xda-developers.com/x-compact/help/rom-lineageos-14-1-sonylos-7-1-binaries-t3584504/
jtk_de said:
If you want to build the ROM yourself init the LineageOS sources from github (cm14.1 branch) and add the local_manifests folder from SonyLOS (also on github) to the .repo directory to have a device profile and the binary blobs for the X compact aka kugo. Then repo sync, and brunch lineage_kugo-userdebug.
Click to expand...
Click to collapse
@jtk_de
Is there currently any place where can I find the source code?
The reason I ask this question is that SonyLOS (github.com/SonyLOS) has been removed.
This tutorial was made by Craftingmod
Thanks so much for helping us.
Original Post: HERE
--------------------------
Note:tested only on GSI ROMs 9.0
1. Bluetooth audio connection fix
Backup the file /vendor/overlay/BluetoothResCommon.apk
Simply remove /vendor/overlay/BluetoothResCommon.apk via root explorer
2. aptX HD
Install "Bluetooth stack audio bitrate changer for SBC + aptX & aptX-HD enabler" from Download of Magisk Manager or Download Here (APTX for Android Oreo & Pie NOT WORK)
3. build.prop
Open /vendor/build.prop and find "persist.vendor.bt.a2dp_offload_cap=sbc-aac" and replace "sbc-aac" to "sbc-aac-aptx-aptXHD" (Add -aptx-aptXHD)
Note: if you don't find the add "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD"
4. Restart device and test
Note: if it doesn't work undo everything you did thanks for trying
Hello my magisk cannot seem to find the module you were referring to. Do you have another link where i can download the module?
Hi There, and many thanks for you guides https://forum.xda-developers.com/member.php?u=9792389
This guide made bluetooth audio and connectio work, but bluetooth calling is not working. Can call but no sound is transmitted, so i cant use it. Any suggestions as how to proceed?
thorvall said:
Hi There, and many thanks for you guides https://forum.xda-developers.com/member.php?u=9792389
This guide made bluetooth audio and connectio work, but bluetooth calling is not working. Can call but no sound is transmitted, so i cant use it. Any suggestions as how to proceed?
Click to expand...
Click to collapse
try this , hopefully it will do the trick:
https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5
I worked.
Fillint said:
try this , hopefully it will do the trick:
https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5https://forum.xda-developers.com/showpost.php?p=79191978&postcount=5
Click to expand...
Click to collapse
Thanks :good: . I actually did look at the thread before, but had the impression that the GSI Treble roms were of the ASOP variant, contrary to the note: 'NOTE: This works only on CAF based custom roms. It doesn't work on AOSP.'
Am I wrong, or is it the note that does not apply in this case?
it looks like not both ways aren't working for 9.0 Havoc.
we need better solutions.
I tried these solutions on the Lenovo Z5 pro GT, but the Phone won't recognise any bluetooth IEM's. The sound keeps playing over the speaker. Does anyone have a solution?
When I change vendor to r/w it goes back to file system read only and I can't save the build.prop file afterwards
If someone was able to make it work can you please show me the build.prop permissions!!
this ROM is awesome. but there's a problem. my BT headphone no sound.
in developer options, "disable bluetooth A2DP hardware" can't be turned off. any solution?
And for xiaomi devices?
What is the apk that I have to delete if my device had miui?
in all the GSI images i installed audio BT is not working.
And BluetoothResCommon.apk is not in that path, why ?
build.prop is there but there is no "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD" entry
Any help to fix bluetooth for this case ? I can pair, to headphones connect, for a moment seems to work, but finally audio get played in the phone itself.
kidronvalley said:
in all the GSI images i installed audio BT is not working.
And BluetoothResCommon.apk is not in that path, why ?
build.prop is there but there is no "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD" entry
Any help to fix bluetooth for this case ? I can pair, to headphones connect, for a moment seems to work, but finally audio get played in the phone itself.
Click to expand...
Click to collapse
Overcame the lack of sound in BT headphones on android 10 by replacing system / lib / libbluetooth.so and system / lib64 / libbluetooth.so with stock firmware
AllexBast said:
Overcame the lack of sound in BT headphones on android 10 by replacing system / lib / libbluetooth.so and system / lib64 / libbluetooth.so with stock firmware
Click to expand...
Click to collapse
im gonna try this too because my Maxpad i10 plus as this issue
blaze2051 said:
im gonna try this too because my Maxpad i10 plus as this issue
Click to expand...
Click to collapse
Teclast M40 How to unlock bootloader?
I have found a method of Teclast P20HD to unlock bootloader which can be found in "https://forum.xda-developers.com/android/help/teclast-p20hd-android-10-tablet-4g-t4141997" and "https://forum.hovatek.com/thread-32287.html", but I'm not sure if...
forum.xda-developers.com
@AllexBast
by any chance have you experianced slow command response with ADB? I just install win10 1803 pro and its so so slow to even run adb devices command. does it make a difference if my device is running GSI Phh A11?
Did the trick for me! Thank you
SrCDA said:
This tutorial was made by Craftingmod
Thanks so much for helping us.
Original Post: HERE
--------------------------
Note:tested only on GSI ROMs 9.0
1. Bluetooth audio connection fix
Backup the file /vendor/overlay/BluetoothResCommon.apk
Simply remove /vendor/overlay/BluetoothResCommon.apk via root explorer
2. aptX HD
Install "Bluetooth stack audio bitrate changer for SBC + aptX & aptX-HD enabler" from Download of Magisk Manager or Download Here (APTX for Android Oreo & Pie NOT WORK)
3. build.prop
Open /vendor/build.prop and find "persist.vendor.bt.a2dp_offload_cap=sbc-aac" and replace "sbc-aac" to "sbc-aac-aptx-aptXHD" (Add -aptx-aptXHD)
Note: if you don't find the add "persist.vendor.bt.a2dp_offload_cap=sbc-aac-aptx-aptXHD"
4. Restart device and test
Note: if it doesn't work undo everything you did thanks for trying
Click to expand...
Click to collapse
Thanks, but editing /vendor/build.prop reaquires writing onto /vendor, so what are the apps to offer rw for /vendor?
hd_scania said:
Thanks, but editing /vendor/build.prop reaquires writing onto /vendor, so what are the apps to offer rw for /vendor?
Click to expand...
Click to collapse
It can be done with root or in TWRP.
But now most phones have aptx-aptXHD support in original firmware, so there's a high possibility you don't need this step. By the way, it is not worth it to fix A2DP though, cause for now it's almost not possible (at lease I didn't solution) to fix bluetooth in call and A2DP offload at the same time. For me bluetooth in call is more important, and there's actually no side effect to turn off A2DP offload as far as I understand.
Anyways, to make bluetooth in call and Aptx (of course others like LDAC) both work, you'll need to:
1. remove /vendor/overlay/BluetoothResCommon.apk (if presented) (if presented and deleted, do a factory reset)
2. remove /vendor/etc/a2dp_audio_policy_configuration.xml
3. Enable "Force-disable A2DP offload" in phh settings
4. Enable "use alternate audio policy" in phh settings if your volume adjustment have any problems (if you got multi ones in different feature category, try different combination until it behave normally)(may require reboot)
5. flash Magisk module "aptx-HD-magisk-10_arm.arm64.zip" to fix aptx support
Now both sbc-aac-aptx-aptXHD-LDAC and bluetooth in call should work. Tested on 2 Qualcomm setups recently with phh android 12 based rom.
Hope this could help you and others having same issues.
XT19443 said:
And for xiaomi devices?
What is the apk that I have to delete if my device had miui?
Click to expand...
Click to collapse
Tho Xiaomi's MIUI really modified the whole aosp crazyly,but the device itself is still treble-compactible
the file is called MIUIbluetoothres.apk(probably,on miui 12.5's vendor)
BUT you dont need to del it.
To Fix: TURN ON "force disable a2dp offload" in phh treble settings.
that's it.(worked on redmi 10a.(MTK))
(ps: actually aptx is a qcom thing so it probably wont work on mtk devices.)