yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Themes, Apps, and Mods] Infy_AsiX:
If you're dirty flash updating only a minor update then Magisk won't change. Anything installed to system will be lost and need to be reinstalled.

The Dolby link was updated into a Unity Magisk module that simplifies installation, it actually fixes it to work on newer O Treble ROMs too. It can be installed like any of the other Unity mods as long as Audio Modification Library is reinstalled last to patch them all together. It's still the same N port at it's base.

By the way for anyone updating to Treble ROMs. The AK4490 patch required after this Dolby doesn't install on Magisk 17.1 I found. So I copy pasted an update with it to use Treble vendor too, find it attached. Credits all to Skrem339
[ZTE Axon 7 Themes, Apps, and Mods] Infy_AsiX:
A heads up to stop using Ainur Sauron since Treble, as for me on L15.1 it increases audioserver processes CPU usage by an extra several to a dozen percent. This isn't really a loss as I hadn't really noticed any discernible audio difference with it.
[ZTE Axon 7 Themes, Apps, and Mods] Infy_AsiX:
so I was still missing Surround Virtualiser because how it had been broken on Dolby Digital Plus since its original ports. I decided to search A7 forums again and GSI chat for any improvements regarding Dolby. Nothing, yet searching XDA forums I found info about repey version has Surround working fixed to only affect speaker. Why no one has mentioned this I don't know, been missing out for months.

https://xdaforums.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192

Apparently since 2.5 surround is fixed. From 4.X uses newer Unity 3.3. From 6.X uses Unity 4.X. Light means no widget.

I'm still on L15.1 8.1 and haven't bothered updating Magisk past 17.3 yet. So I'm still on the last compatible for Magisk 17.3 which is V4A 3.4.2 and AML 1.9.4 which are still Unity 3.3, therefore Dolby 4.5 should work but for some reason it doesn't, I'm on 2.7 instead. When it doesn't work it broke V4A from functioning too. Just test and find the latest among those that should be compatible for you.

edit: Tip, beware the custom presets on flat equaliser have aren't actually flat. Instead I just use music preset and modify. The app does remember states for plugged/unplugged surround only.
[ZTE Axon 7 Themes, Apps, and Mods] ibphantom:
I'm on Liquid Remix ROM-Pie, Baddar 1.1 Kernel, Magisk 19.1 and the lastest DDP-6.4 light is working for me.
[ZTE Axon 7 Themes, Apps, and Mods] Infy_AsiX:
I updated to the latest linked dolby, magisk and v4a legacy. Dolby now does surround on headphones too now, it can still remember last used preference. I really don't like the new v4a 2.7 development for a few various reasons.

Just wanted to leave a useful tip. I found the new updated Audio Compatibility Patch magisk module fixes an old feature that used to work on B32 based O that was lost since Treble. It allows using audio effects while apps use the microphone or rather more specifically enter a voip call type scenario. I tried ACP as a fix when first moving to Treble but it couldn't help back then.

Fast forward to now. Trying ACP again it seems the new developments fix the feature I require. When installing I skipped original audio policy patching and everything else seeming unrelated to me except volume_listener. Lo and behold that feature I long missed and sought is back.
[Moto G6 Questions & Answers] Celludroid:
Hi! I've been waiting for the Moto G-series to finally get proper Camera2 API support so 3rd party camera apps can access more manual controls like ISO and shutter speed. While the G5 still had poor Camera2 support, I was hoping that would change with the G6. So could someone with the Moto G6 run this free Camera2 test app "Camera2 probe" and post screen grabs of the results here? I'm mostly interested in the "Hardware level support category" - it would be fantastic if it came out "Full" or "Level 3" instead of "Legacy" like on the G5. Thanks!
[Moto G6 Questions & Answers] kemoti:
[MENTION=8329178]Celludroid[/MENTION]

Please
[Moto G6 Questions & Answers] Celludroid:
Thank you! Very good news! :)
[Xiaomi Redmi Note 5 Pro Questions & Answers] tlf55:
Hi, I'm actually on 8.8.2 and my battery is draining very fast.. I can see that Android System is always on top in my battery usage ..

Here's some screenshot

Can someone help me ?

It's clean flash and i'm still ARB 3 , with Magisk 16.7 installed (tried uninstalling it but it doesn't come from there)

Edit : here is some mirror for the screenshot as xda sometimes fails to show picture : https://ibb.co/iybtYz

https://ibb.co/cwUDYz

https://ibb.co/fwGGmK

https://ibb.co/cj8U6K
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] richaardvark:
So I was using a fairly well-known app that lets you live-stream audio from a Windows PC to various devices, including Android tablets, and was being very careful to not strain/overload the speakers when, in classic Windows form (?), my PC briefly lagged/spasamed and unmuted the audio channel/flooded my HD 10 with terrible feedback at like 400% volume level, instantly destroying the speakers. They sound god-awful now, barely making any sound and, if they do, it's a very tin-y and crackled sound :-/

I've spent so much time customizing my device, rooting it, etc. and the thought of backing up my data, flashing the stock settings again, mailing it to Amazon, waiting for a repair or replacement, reinstalling and reconfiguring everything makes me :(. Is this probably my best option though?

I've been trying to see if there are any replacement speakers sold online anywhere, but I guess the current model is too new to have replacement parts for sale out there, or just isn't something that will ever really happen for a relatively inexpensive device like this. Does anyone know if previous HD 10 models had the same speaker components or if the 2017/7th generation 10 speakers are specific to this version?

Thanks for your advice/knowledge!
[Huawei Nova 3 Guides, News, & Discussion] dkionline:
Huawei Nova 3, the package for users missing SD card slot in 2018 flagship devices. Is that device ever useful in mather of options and updates compared to last Nova models, or is it only a dead ship for unused hardware before new Board arrives in Mate 20?

Does the line ever get 2 major updates?

Huawei starts to mess the market with so called better devices, but only add or left some features, nothing special.
[Huawei Nova 3 Guides, News, & Discussion] amontakhabi26:
unlock bootloder code for nova 3 PAR-LX1M
[Touch Cruise ROM Development] Olipro:
Hi,

Is there anyone out there with their Polaris trapped in Tri-colour (and not running a .Olipro/.OliNex SPL). if so, PM me.
[Touch Cruise ROM Development] v1zca1n0:
Me

Program stopped in percent screen (in 0%) and don´t run more. After if you unplugged the PDA (an HTC Polaris, of course) and swich on don´t pass of the Tri Color screen and you can read "POLARIS. SPL-1.25.0000.CPLD-2" and in the rigth corner "RUUNBH" but nothing began, no OS or programs, nothing... Any suggestions and help??? Thank You.:confused::mad::(
[Touch Cruise ROM Development] hangloose59:
Can't flash SPL, Polaris FRA ROM; was bricked...solved,can't flash

Hi Olipro,

last week-end I tried flashing hard SPL v2 on my French Polaris, before planning to flash the new radio 1.64, then bepe's 0.66 ROM.

I spent the first part of Saturday night trying numerous times, recovering, taking battery away, and trying agin - never worked. Then I tried flashing the 1.64 radio, it went up to 99%, then stopped, error message: from then on my Polaris went to boot-loader only, after soft reset or even hard resets. Until dawn I tried to fix this (I'm not a developper, I'm a power user travelling 4 days a week by plane accross Europe). Couldn't fix it.

On Sunday I called a friend of mine who imports HTC and sells the channel: I gave him my Polaris and he took it with him to fix it. Result was very surprising: I had given him your hard SPL v2, and a few nice ROM's from this site, specailly bepe's, as well as all the radio versions listed here for POlaris; well none of all that worked with him, and he could only reflash the official ROM and radio, and return it back to me...(which was very kind as it took him some time).

BUT, overall I'm very frustrated as I'm an early adopter, and I would so much like to try cooked ROM's on this fabulous device.

What do you think I should do? Any idea?

Is there a way to guide me though a custom process or is there a real issue on ALL French ROM's out there? (can't believe that).

Your inputs would really be appreciated.

Thx many, HangLoose.

23:45 > it finally worked !! (I must have been doing something wrong previously, sorry for bothering Olipro).

And thx for enabling us to use best in class cooked ROM's from this site.

I'll be loading bepe 0.67 just now. !!

Regards, HangLoose59
[Touch Cruise ROM Development] vidaloka102000:
My cruiser not leaving the screen tricolor

:confused:My cruiser not leaving the screen tricolor, Tried to replace the original language (Spanish) by the English and upgrade stopped in 14%, dai then not leaving the screen tricolor.

Some hint.
[Touch Cruise ROM Development] v1zca1n0:
FIXED! :D at last the problem was I used a SPL for HTC ELF not Polaris and, I don´t know why, that makes OS stopped in an eternal bug... Whem I use again the same Hard SPL for Elf Voilá! Do it!:p And know all works fine. I promisse: I will never change the BootSplash be sure:rolleyes:
[Touch Cruise ROM Development] Diagorn:
I have the same problem My Pc has scrached and now my polaris is blocked to the bootloader

Is some could you help us ?
[Touch Cruise ROM Development] Mahmood:
Hard reset the device and it can take u out of bootloaer mode. To hard reset:

GPS/MESSAGING and INTERNET EXPLORER buttons, and at the same time, use the stylus to press the RESET button at the bottom of your device.

2. Release the RESET button, but continue pressing the GPS/MESSAGING and INTERNET EXPLORER buttons until you see a message on the screen

Release the buttons, and then press SEND on your device to perform the hard reset, or press any other button to cancel the reset.
[Touch Cruise ROM Development] Diagorn:
Hello thanks for your help but I have already tried this :(
[Touch Cruise ROM Development] v1zca1n0:
Try with this program do a Hard SPL and tell me how gone:D
[Touch Cruise ROM Development] Olipro:
the Elf is a DiskOnChip device, the Polaris is plain NAND.

you can try it, but frankly, I think it's not really the smartest move
[Touch Cruise ROM Development] v1zca1n0:
You are rigth Olipro as always, but I left because I have the experience of used badly and block the PDA until I use again and unblock the machine. Maybe the diferent chip make a kind of bug than only can be fixed with Elf Hard SPL I don´t know but with me works. Let see if is the same with Diagorn :p
[Touch Cruise ROM Development] Olipro:
could be a side-effect, but the file should be blocked from flashing anyway.
[Touch Cruise ROM Development] hyson:
i have the problem too. waiting for the solusion:(
[Touch Cruise ROM Development] v1zca1n0:
Curiously Elf SPL unblock the flash and I don´t know why:confused: Anyway I stopped flashing anymore because I don´t want have the same problem again. Only I explain what happend to anyone that can have the same problem and attach the Elf Hard SPL if they want use and probe:rolleyes:
[Touch Cruise ROM Development] mix23:
BT Problem

The BT LED styed ON and after hardware reset (removing the battery, the reset button wasn't working) only the bootloader screen. It revived after I flashed the Radio ROM. And what bugs me is that BT button remains ON in TouchCommander, but NO BT. any ideas???
[Touch Cruise ROM Development] mix23:
BT Problem

After synchronising with the PC i noticed the BT LED goes OFF ...

BTW

HardSPLv2.2

ROM 1.28Aserg.1WWE

RADIO 1.64.08.21
[Touch Cruise ROM Development] IndoGuy:
Cruise stuck in 3-color screen

Hi,

My Cruise just frooze, during GPRS synch with Exchange server. Soft reset and hard reset do not work anymore. If I take out the battery, and then switch on the device it stops in the 3-color screen. BT light stays on.

I have not made any changes to my Cruise, only added a 8 Gb SD card.
[Touch Cruise ROM Development] hoawell:
me too...somebody help !!! sorry my english
[Touch Cruise ROM Development] nemestniy:
Strangely enough it works!!!

I was really frightened when my TC got stuck in Tri-Colour screen. MY Polaris came to standstill, trapped in. :(

Over and over ROMUpdateUtility.exe shows ERROR [262 or 284]: UPDATE ERROR while trying update. :eek:

And only this strange RUU gave me other ERROR [296]: UPGRADE ONLY that helped me to quite out the three-color screen and installed new radio successfully.

:)
[Xperia Z5 Compact Q&A, Help & Troubleshooting] doeternietoe:
Hi all,

I wonder if somebody could help me.

At the moment I have a Z5 compact with a broken screen (totally black) and touch. I know it still can boot, because it responds to my fingerprint when booted up. However, it does respond to my finger, but still needs a patern on first boot, which I cannot do on account of the broken touch screen. Also, my computer detects the phone.

I want to access my data, but for that I would have to use the onscreen menu which pops up when I connect the phone with usb. That's impossible.

I looked around on the internet and it is possible to remotely control the screen or access via adb. However, for that I either need to install some app on the phone, enable usb-debugging or authorise access via adb. All of those are impossible.

My phone has un unlocked bootloader and is rooted, so as a last resort I've tried to flash a modified kernel to enable usb debugging by default. This fails. Probably because I make some mistake in modifying the kernel, but I don't know. There's not a lot of response from my phone, as you understand ... :) Besides, I've absolutely no experience modding myself.

Anybody any idea, please?
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Nutchos:
So I just fixed the same issue you're having this week. It required opening up the phone.

Basically the ribbon cable that connects the screen to the motherboard had become unseated and needed to be plugged back in for me.

The Z5C isn't the easiest phone to take apart but it's not that difficult either. Just requires some basic tools (Hair dryer, tweezers and some precision screw drivers). There's a bunch of videos showing you how on ifixit or youtube. You just have to go all the way to the part where they flip over the motherboard and unplug the two ribbon cables, one of those two will be the culprit.

This is the first and only phone I've taken apart so any amateur can do this.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] mlleemiles:
Boot to recovery and connect your phone to PC
[Xperia Z5 Compact Q&A, Help & Troubleshooting] doeternietoe:
Yes, actually I've had problems with a broken backlight before and opening the phone and re-adjusting the cable solved that. Not in this case however. Thanks for your suggestion, anyways.

Would recovery provide me with some way to enter my pattern via a PC, e.g. with ADB?

Actually, I'm not sure I had any recovery installed at all. I've tried this before and just tried it again. I press the on/off-button while holding volume down. After that no response whatsoever. My computer does not see any device when connected. I suppose my recovery does not work properly, but without screen I can't be certain.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] doeternietoe:
mlleemiles, you are a _hero_! :D

After reading your post I decided to try flashing another recovery to try if that might work. Now I can access my files without ever having entered any pattern :D.

Nevermind that it turns out my files weren't encrypted and I thought they were.

If anyone has a similar problem in the future, this is what worked for me:

My exact situation:

- My phone runs a stock rom (downloaded from XperiCheck) with version 32.4.A.1.54. When my phone was still running ok I had the bootloader unlocked and my device rooted with Rootkernel.

Working solution:

- I downloaded Twrp, version 3.2.1, from this page:

https://xdaforums.com/z5-compact/development/twrp-twrp-3-2-1-z5-compact-t3748952

- Shut down my phone by disconnecting the battery and reconnecting it again

- Started my phone in fastboot mode and flashed recovery to my phone with:

fastboot flash recovery recovery_suzuran_220218_2.img

- Booted my phone in recovery with volume down + on/off-button.

- Connected my phone to my PC, et voila.

Turns out I can also access my phone with ADB as root, so after backing up the entire internal memory, I might try to get some remote screen tool working.

So thanks for the help and if I find something interesting and new, I'll post that too.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] doeternietoe:
Small update:

After successfully flashing Twrp I backed up the internal memory, so must of the important stuff was safe by then.

However, it turned out that my phone now wouldn't boot into anything other then Twrp. I decided to flash my rom again. First I installed my apb keys using Twrp:

adb push adbkey.pub /data/misc/adb/adb_keys

It turned out I already had usb debugging enabled.

I then flashed my original firmware again, and connected with adb. This time it connected correctly, without me having to click any dialogue on my phone. I fiddled with several remote control Android tools most of which didn't work. Finally, it turned out Vysor does exactly what I want to do. It is a bit unstable, but workable.

Anyways, I've finally managed to copy all the stuff I wanted from my phone.
[Xiaomi Mi 8 Questions & Answers] Padlite:
Scroll down over this post to see anwer!

Hey there! I just got my Xiaomi Mi8 from HK Goldway at Aliexpress. It came with its bootloader already unlocked and a Global ROM flashed.

I wanted to install Magisk but failed horribly . I've already done that to several phones (my last one was a Moto X Play, and it worked without major complications). But with this one, it seems I can't get past the bootlogo.

Stock Fastboot image used:

dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global

This is what I've tried so far:

First try

Flashed TWRP for Mi8 version 0711.

Flashed Magisk.

Got a bootloop.

Reflashed stock image via Fastboot.

Second try

Booted (not flashed) TWRP.

Tried to install latest global weekly from this thread.

Also got a bootloop.

Reflashed stock image via Fastboot.

Third try

I thought that those flashable ZIP firmwares were too small for them to be a full-fledged OS. So I went and downloaded this other one. Global version.

I read somewhere that I needed to format data before flashing a new image, so I did.

Booted TWRP.

Formated data (not Wipe)

Installed that ZIP from TWRP and booted correctly.

Booted TWRP again and flashed Magisk.

Got bootloop.

Back to stock image via fastboot.

Last try

Booted TWRP.

Formatted data.

Installed MIUI via TWRP.

Without rebooting, flashed Magisk and no-verity-opt-encrypt-6.0.zip.

This got past bootlogo ("Unlocked" message changed to "powered by Android") but got stuck there. Not booting at all.

Right now I'm back to the last try, booting MIUI successfully but without Magisk nor no-verity-opt-encrypt.

I kinda have no more ideas left. I understand this is a new device but I can't understand why people claim the have been able to install Magisk and I can't! Other thoughts were, maybe they were running MIUI 10 Beta and it only works with that version? I'm unsure about that.

Can someone lend me a hand? What am I missing?

Thank you!!

EDIT: FIX!

Over here, user [MENTION=4936669]richardyusan[/MENTION] helped me out with an extra step.

What I did:

Installed Magisk V16.7.

Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.

Performed fastboot format userdata.

Rebooted.

And I got my phone booting with Magisk Installed!

Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!

Hope this works out for everyone having this problem!
[Xiaomi Mi 8 Questions & Answers] gulp79:
have you tried to use Magisk 16.4,

if not, try to follow this guide:

https://www.theandroidsoul.com/xiaomi-mi-8-root/
[Xiaomi Mi 8 Questions & Answers] Padlite:
Thank you for the fast reply!

I followed that guide and tried these steps:

fastboot boot mi8-twrp-3.2.2.img

Unencrypted via Pattern

Flashed Magisk v16.4 + DM verity disabler file

Reboot

But I'm still stuck at "powered by Android" bootlogo.

Normally it boots within 5 seconds but now it's taking forever. I'll wait a few minutes to see what happens.

I'm attaching some screenshots of the install process.
[Xiaomi Mi 8 Questions & Answers] gulp79:
Ok,

but if you install Magisk 16.4, don't install also DM verity disabler.

DM verity disabler is needed if you don't want to root (see poin 14 in the linked guide).

Hope it works...
[Xiaomi Mi 8 Questions & Answers] Padlite:
If I only flash Magisk 16.4, then phone shows "Powered by Android" and instantly reboots into stock recovery.

Only way to get it back booting, is performing fastboot flash boot boot.img from stock dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global image :eek:

I read somewhere about official and unofficial bootloader unlock. I didn't unlock the bootloader myself. Maybe it has something to do with it?

PS: Anyone had any luck using Magisk with MIUI 9.5.13?
[Xiaomi Mi 8 Questions & Answers] punk84z:
Did you try with a newer magisk version ? ... 16.7 was released 15 day ago

https://github.com/topjohnwu/Magisk/releases

Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-v16.7.zip

It´s a good practice to use magisk_uninstaller before flash new one if you had problems.

Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-uninstaller-20180719.zip

Please tell us if it´s works
[Xiaomi Mi 8 Questions & Answers] gulp79:
Seems that also others users have this problem

https://xdaforums.com/showpost.php?p=77234924&postcount=6312
[Xiaomi Mi 8 Questions & Answers] Padlite:
I just tried that. Uninstalling and re-installing v16.7. Although it seems now it's doing a few more steps, I'm still getting the recovery bootloop.

Install log screenshot attached.

Exactly that. Maybe we'll need to wait for a supported Magisk version. I'm still wondering what's the difference between our Mi8's that some can get Magisk working and some not. ?
[Xiaomi Mi 8 Questions & Answers] bassbounce:
I am running Magisk stable and tmiui 10 from Xiaomi. Eu without any problems.
[Xiaomi Mi 8 Questions & Answers] soreldc:
I have a Mi 8 se and i install the eu rom boot the phone , reboot to twrp wipe and factory reset and installed magisk 16.4 .this is how works for me
[Xiaomi Mi 8 Questions & Answers] broken514:
i have the same problem too..when using china stable rom 16.7 magisk can be installed successfully tried many times...

flashing global version seems to have this issue...

tried all this steps too but no luck in global rom...
[Xiaomi Mi 8 Questions & Answers] -fluffy-:
i allso hade that problem

wen i got my phone it was with global rom

then i flashed twrp

didt like they said

wipe dalvik cache an cache an factory reset

flashed miui eu rom

then flashed twrp again rebooted into recovery

flashed magisk 16.4

ended up in staying on android logo

then i try format data an didt it all again

still android logo an nothing more

well then i didt what i allways didt on my other devices

i wiped dalvik cache

cache

data

system

then i flashed eu rom

an twrp again rebooted into recovery again

then flashed magisk 16.4

rebooted system an now it booted up

REMEMBER to manke a backup before flashing all off thise things otherwice u wont have the option to go back if something goes wrong
[Xiaomi Mi 8 Questions & Answers] Padlite:
Well maybe the critical step is to wipe everything, including System.

Did you Format anything instead of Wipe this last try?

Also, could you please share a link from that working MIUI rom?

Thank you!