yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] almahix:
Mod edit: Thread closed as duplicate of

https://xdaforums.com/t/traditional-3-button-navigation.4382631/

Oswald Boelcke

When using the toolbar with The three button control, I am finding difficulties navigating. Often the open app button is unresponsive and clicking on "see more" buttons on the Facebook app is unresponsive. Everything works fine with gesture navigation but not the toolbar. I've tried it with 3 different launchers at it makes no difference. Anyone else experience this?
[Google Pixel 6 Pro] roirraW "edor" ehT:
This is a duplicate of your other post Traditional 3 button navigation. You should report your own duplicate post to a moderator for them to delete.
[Touch Diamond, MDA Compact IV General] tommyboybid:
I have just started using ms voice comand, but the volume is very low

I have looked about and done a reg hack to change

HKEY Current User - Control panel - Sound Catagories - Voice Command -

Change:

Attenuation Catagory - Value 1

InitVol - Value 3

and also tried

HKEY Current User - Control panel - Sound Catagories - Voice Command -

Change:

Attenuation Catagory - Value 2

InitVol - Value 8

but neither of these make it any louder

anyone using voice command, that has been able to fix this on a diamond?

I am only using it on the speaker and not a bt headset

Also i noticed that the speach is not as clear as cyberon VC, as it is alot faster. But i prefer the features of MSVC with regards reading the email subjects and caller id
[Touch Diamond, MDA Compact IV General] Pumpiron579:
7. *Adjusting Volume of Announcements -* There are two values that seem to influence the volume of announcements. They are stored within the following key:

*HKCU\Control Panel\Sound Categories\Voice Command1*

The values are:

*AttenutationCategory*

*InitVol*

There are apparently different default setting based on your device. In general the values are generally around 1-4 for *AttenuationCategory* and 1-5 for *InitVol*. Some research shows that setting *InitVol* to 40 and *AttenuationCategory* to 1 provide the best results. In my testing I have found the *InitVol* to do nothing. The *AttenuationCategory* definitely does something, it seems the lower the number the lower the voice. When set it to 0 the announcements were very faint. Setting it higher made them higher, although I can't say that anything over 4 or 5 got any louder.

In my findings I would say set both of these to 5 (I have read some other posts that lead me to believe setting InitVol over 5 is pointless, in addition, the posts that recommend setting it to 40 don't specify if that is decimal or hex).

Got this out of the Kaiser Forum.
[Touch Diamond, MDA Compact IV General] tommyboybid:
do i need to restart the device for these settings to become active?
[Touch Diamond, MDA Compact IV General] Pumpiron579:
What I do is shut the phone down...Power Button, and then take out the battery for a second or two, then I put the Battery back in and start it back up. Some reg settings you change revert back when you just soft reset.
[Touch Diamond, MDA Compact IV General] AnaZ:
I would love to make voicecommand louder BUT i can't. I changed the values but the volume is still down....

How do i do???

Someone???

I read in one post that if I remove S2A, the voicecommand will be louder...but i still don't know how to remove S2A....

HEEEEEELLLLP!!!
[Touch Diamond, MDA Compact IV General] d8389:
The loudest volume level on HTS HD2 i got with:

indows Registry Editor Version 5.00

[HKEY_CURRENT_USER\ControlPanel\SoundCategories\InCallFeedback]

"AttenuationCategory"=dword:00000001

"InitVol"=dword:00000005

"DefaultSound"="\\Windows\\HTCTone\\Midi2Wave_079_4098.wav"

"Directory"="\\Windows\\"

[HKEY_CURRENT_USER\ControlPanel\Sounds\TTSAnnounce]

"Category"="InCallFeedback"

"Sound"="\\Application Data\\Volatile\\\\TTSCallerID.wav"

"Script"="p"

Not tested on BT headset yet.
[Google Pixel 6 Pro] almahix:
Anyone beside me still use the 3 button navigation option? I often find the current apps (right most) button unresponsive, and often the "learn more" button on facebook pages unresponsive. Using gesture navigation works fine but not button navigation. I've tested this with 3 different launchers to verify it is not my Apex launcher I've be using for ages. Anyone else observe this?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I did still use 3-button navigation until my Pixel 6 Pro. I think my wife still uses the 3-button navigation, though.

I *might* have briefly had 3-button navigation enabled on the P6P, and it sounds familiar that I might have seen issues like what you describe with Recents. I didn't notice any problems regarding "learn more" on Facebook. I use Nova Launcher Prime.
[Google Pixel 6 Pro] 96carboard:
Fakebook? People actually use that? I always blacklist all their domains on my DNS servers, pure hostile privacy invading trash.
[Samsung Galaxy A50s Questions & Answers] izu123456:
Long story short, I decided to flash a zip file of the CatOs 1.2 into my stock firmwarevIt doesn't have it.

I really need that for some work but don't know if that is possible?

Or is there any software or a .zip that I can flash to install this component of the stock firmware
[Android Q&A, Help & Troubleshooting] s80_gad:
Hi everyone and Happy New Year,

I am trying to open ROM_0 file created with SP Flash tool. I have tried ROM explorer 0.9.1, I have tried various option converting with simg2img and opening with 7zip but nothing has worked so far.

The file is about 100GB and it is a SP Flash tool backup of my userdata on which I have a lot of images which i need to save.

I was using Dot OS 5.2 general image and a message popped up about trying Android 12 and I have clicked on it just to get rid of it but I assume it has triggered a download. My phone crashed yesterday evening when I started the cmera app and once restarted it was in a boot loop mode stuck on the dot os logo.

So far I have tried various options unsuccessful - I have reflashed the image which I originally flashed, I have set the partitions active - a and b and reverted to the initial active one which was "a".

I have also flashed system.img (with the treble general image) but still it is in a boot loop mode.

I have just decided to flash back the super.img image from the stock and guess what - still stuck.

Flashed the stock boot.img again thinking there might be an issue with the kernel but that didn't help.

I understand that it is the case of fully flashing back the stock ROM which will lock the bootloader and delete all my userdata in order to have the phone back.

However the phone IS NOT important, the ONLY IMPORTANT thing are the images in the userdata.

I have created the backup of it straight after the boot loop appeared. Tried to read here on XDA but it is not clear what format is that file and how I can access the data on it.

Looked for a recovery partition but there is none. Potentially hidden as you can get into stock recovery via fastbootd. But the options there are only to wipe the partitions/reset.

The phone is Umidigi Bison Pro and I have been having all but troubles with it.

Any help greatly appreciated it.

Regards
[Android Q&A, Help & Troubleshooting] SubwayChamp:
May I'm wrong, but I guess that if you didn't give it an extension then the file doesn't have a format; when you make a backup of a partition using SP Flash tool you should give it an extension, for example userdata_backup.img will work, in some devices, for some partition the .bin extension is used.

And to restore the device to a working state without losing data you could flash the stock ROM unchecking the userdata partition and using Download only option won't re-lock your bootloader.

If actually your userdata was not overwritten you still can try a second attempt to preserve it using mtk-client, search for it in GitHub, also consider what I stated about re-flash your original ROM preserving the userdata partition.
[Android Q&A, Help & Troubleshooting] s80_gad:
Thanks SubwayChamp, I appreciate your comment.

I have tried .img, .bin, ext4 etc but cannot open it - I am not sure if there is another application that can convert it in a readable format or maybe if we can mount it and access the files.

I had the impression that if you flash the stock rom the bootloader is locked and you loose everything.

But thanks for your advice - I will flash everything apart from the userdata partition which is last in the order anyway. Should I select or deselect the preloader partition- will that make a difference?

Regards
[Android Q&A, Help & Troubleshooting] s80_gad:
Just flashed the full stock rom without the userdata partition - still stuck on the logo in a boot loop :confused::cry:. I really need to open the userdata backup file from SP flash tool as I feel I have to do a full reset/wipe.

Any other suggestions about explorer for the sp flash dump file, please?

Regards
[Android Q&A, Help & Troubleshooting] SubwayChamp:
No, I didn't say to change the extension now and try it in various format, unfortunately I feel that if you didn't give you the extension at the time to make a backup then the file is unreadable, what I mean is that when you make the dump through SP Flash tool you have to give to the file a name and an extension, not letting it as is offered by SP Flash tool, for example you did see the name ROM_0 or similar, but you have to give it a name and an extension, in this case userdata_backup.img would work.

Did you check mtk-client?, you can read (dump) the userdata partition through this CLI tool, and after that you can restore it at any time.

Using the download option (only) you never re-lock your bootloader.

But wait a minute, keep in mind that your device is A/b, so you have to double-try all the things, for example, if you want to flash a specific partition like boot you have to be sure in which partition you are right now BUT unfortunately you don't know which partition is the working one, so better use fastboot to flash the missed partition, target to both slots.

And what about the option to get to a custom recovery? (I guess you had it previously to flash CR Droid) either taking a backup of userdata or re-flashing the same CR Droid that was functional previously.
[Android Q&A, Help & Troubleshooting] s80_gad:
Thanks SubwayChamp for your reply.

So I will try to dump the userdata again then - I still haven't touched it so I hope the partition and the data on it is fine.

I assume it is that mtkclient you are referring to. Will see if I can get some time today to try the live cd first as I am on Windows at this moment.

So my device is indeed A/B - the system is on "a" and I have flashed dot os using fastbootd and overwriting the system.img within the super.img. It worked fine for about 20 days until that crash (I only assume it is due to the update - nothing else has happened that could create trouble).

Also tried to set the b partition active but didn't help so switched back to "a".

Unfortunately there is no recovery partition, from what I learned the recovery is within the boot img. I have tried to load temporary unofficial twrp - fastboot boot twrp.img - and the first step is ok, but then it crashes. so no luck to load custom recovery even temporary in order to save the userdata on sdcard.

Tried to get to the contents trough adb shell but while some directories are listed, I get access denied to the userdata - I think maybe the links are broken?

I will try with the mtk to see if I can back it up - and what I'll do is I'll flash the full stock rom including the userdata and potentially will try to flash the old userdata through fastboot or sp flash or mtk.

TBH I don't understand why the phone is still in a bootloop - can't be only because I haven't cleared the userdata?

Regards
[Android Q&A, Help & Troubleshooting] SubwayChamp:
It works on Windows though.

The issue was originated due to the lack of the other system files that also occupy this space; vendor, odm, product (may vary depending on the device), can be fixed flashing the super.img using fastbootd again.

Yes, this device doesn't have a dedicated recovery partition, but it is placed in a tiny portion of the boot image (usually the ramdisk) you can try by flashing the TWRP image onto the boot partition (flashing, not booting only) then boot to it, do the stuff you need through TWRP, from there you could solve the bootloop. To can boot to Android again you should need to flash a boot image.

No, it's encrypted.

When you flashed a system image onto the super partition the other partitions that are set dynamically didn't find a place to be recreated or couldn't play its role, added to this, a different system image that which is contained in the super image can differ in sizes either logical and/or dynamical (virtual sized).
[Android Q&A, Help & Troubleshooting] s80_gad:
Flashed already the original stock rom super. img and everything else apart from userdata - it doesn't work.

see below

View attachment 5499133

Tried to flash it - it just restarts the phone straight away - in fact replaced it with sp flash tool as well which recognises only the "a" partition and flashes it there.

I see

I am guessing this is why I have to reflash the whole rom incl userdata in order to make the phone usable.

What I'll do is I'll try to dump userdata with mtk and then will reflash everything with the stock rom ()hopefully the phone will boot) and then will flash the dumped userdata with mtk. Hopefully that will work.

I'll see if I can somehow mount the mtk .bin file to see if I can get to the contents of it

Will have to use the live dvd as I have win 7 and python 3.9 cannot run on win 7.

EDIT: Can't start anything through the live dvd - is there any workaround for win 7 or is there a direct executable file which I can get to start the mtkclient?

Regards
[Android Q&A, Help & Troubleshooting] Werve:
Hello,

I also have an Umidigi Bison Pro that I am going to use as a daily driver. (It's a pity that it's unpopular it would be a great device for modding, it's cheap, rugged and has source code availability of the official ROM and kernel). I created a Telegram group about this phone if you want to join is https://t.me/UmidigiBisonPro

About your problem you can read this guide (it describes how to backup and extract from the file created by SP Flash Tool even the partitions that not visible such as the b slots) https://www.hovatek.com/forum/thread-21970.html

To give you an idea on my Bison Pro a total of 52 partitions were extracted.

If you have the full backup from before the bootloop (before the upgrade, when it was still working) my advice is to restore all partitions.

I consider myself a novice regarding modding but it is likely that after the upgrade the userdata partition is no longer readable.

I have read that you should not update the GSI ROMs but repeat the whole flash sequence.

I also recommend removing the forced encryption of the userdata partition (you can do this when rooting) to avoid exactly these problems where you have the partition backup but not the decryption key.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Sorry for delay, I didn't receive any notification on this (or I didn't notice it), I hope you sorted out your issue, if not, let me know.
[Android Q&A, Help & Troubleshooting] Werve:
I didn't received notification too on your message and I found out on profile account that the notification for new message on a thread are default disabled.

I recently had some problems and experimented with partitions.

Reducing the possible cases I think the decryption key for the userdata partition might be in these partitions: super , misc , nvdata , nvcfg , md_udc

and I noticed that if one of them is corrupted/different version the dm-verity check fails (in my case it is written on the screen) and it was necessary to reflash all partitions except userdata (I don't know if there is a faster combination, from the few tests done in this case I didn't find any)

Do you have more information about where the decryption key might be between those partitions?

I have made a brief description of the role of all the partitions encountered but I still don't know some of them:

boot_para

gz_a (/ gz_b)

md_udc

otp

spmfw_a (/ spmfw_b)

sspm_a (/ sspm_b)

teksunhw_a (/ teksunhw_b)
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Why do you think userdata has a decryption key? Unless the user set it in a backup done through a custom recovery or through the device itself, I don't think so, may I'm wrong, but which is your scenario?
[Android Q&A, Help & Troubleshooting] Werve:
Since the userdata partition is now usually encrypted either with FBE or FDE but once the system loads the files are readable and moveable even externally then it is clear that somehow the data has been decrypted precisely using the relevant decryption key, AES encryption usually.

So if the user has not specified any key this must be derived from the information already in the partitions from the factory.

Then by restoring the right combination of partitions the system can boot correctly by decrypting the userdata partition. Hence the tests and the report I wrote in my last post.

At the moment I was able to remove the forced encryption of the userdata partition by modifying super (specifically fstab present in the /vendor sub partition) but I would like to achieve the same systemless modification using Magisk (to be OTA compatible). Unfortunately, the options to remove dm-verity and forceencrypt have been hidden in the latest versions of Magisk to avoid problems with inexperienced uses.

Since I don't have a custom recovery on the Umidigi Bison Pro I can't force flag those options in the .magisk file so I have to find another way.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
Well, what I said is a different thing, the other user had a different interest than this. They did want to access to some data from a backup in a non-booting device, I referred to that, the userdata image backed up doesn't have an encryption by default, unless the user set one through a custom recovery, suppose that someone did take a backup from the userdata partition, this userdata image can be opened/readable for anyone with minimum skills and the appropriate tool.

In regard to your issue, I don't think, the userdata partition has any kind of restrictions to take OTA updates, most likely this resides in the bootloader, kernel or even a "silent/hidden" partition with no more functions than that.

As a side note, you should check some custom recoveries, specially in Xiaomi devices that easily allow taking OTA updates, for example I always can take OTA, when I use Orange Fox recovery, although I'm not interested, so I make updates manually, to be sure that all run fine.
[Android Q&A, Help & Troubleshooting] Werve:
The methodology I was referring to that is not OTA supported is to modify the super partition (the dynamic partition that from Android 8? contains system, vendor, product--for Project Treble) to disable the forced encryption of the userdata partition. In my case FBE (File Based Encryption) Android 11 encryption.

Even having disabled the dm-verity if you apply an OTA update the super partition is replaced with the one that does not have the modification to remove the forced encryption and from the tests I have done this refuses to read unencrypted partitions and asks to do a factory reset.

So, the userdata partition makes the OTA update problematic (it doesn't block it, but you lose your personal data).

I am sure that instead of modifying the super partition to disable encryption you can achieve the same result via Magisk and a modified boot partition.

Unfortunately despite many trials due to my inexperience with Magisk I could not do it.

I wanted to do all this to avoid problems as described in the case of this thread that is, have the userdata partition intact but not the rest to be able to describe it. But seems I must let the encryption and do a backup after every OTA update.
[Android Q&A, Help & Troubleshooting] SubwayChamp:
If you want to apply an OEM vendor stock update then it is a restriction from the OEM itself, and if you want to apply a GSI based update, it's a different approach, not sure if the restriction is FBE related or if the userdata is encrypted or not but probably related to AVB.

There are some tools/scripts you should search for, that can unpack and repack super partition, maybe you find something in the ODM or product image, this is assuming that the super partition it is the culprit.

Just know that it's a nonsense that an order (script) to restore a specific partition, be placed just there, but in other partition.

You should check what the OTA update contains, try to catch the OTA update through some ADB script, then unpack it, and see inside.

Also, you can try backing up every partition, and restoring them one by one, seeing if it boots.
[Android Q&A, Help & Troubleshooting] Werve:
I have already done these tests, not with an OTA update but with a different version of the firmware for all partitions, and set out the conclusions.

Obviously it's an OEM restriction since it left the forced FBE encryption on and the way it was created (so I guess also from AOSP) it refuses to read the userdata partition if it doesn't find it encrypted.
[Samsung Galaxy S21 Questions] Droiderat:
I purchased a Galaxy S21 (SM-G991U) which was sold by and is SIM-locked to T-Mobile. The IMEI is clean, and the phone is paid off.

I need a professional service to assist in unlocking the phone (and, yes, I can tether the phone to an Internet-connected Windows PC with a USB-C cable).

I have located a number of services via a Google search, and find that most are quite expensive. I am hoping that someone has an economical, trusted favorite.

Recommendations please.
[Samsung Galaxy S21 Questions] goattee:
Maybe I am missing something but T-mobile will unlock a phone on request if you've been a customer for 90 days. Are you not a customer? If not, is the seller still a T-mobile customer?
[Samsung Galaxy S21 Questions] Droiderat:
Neither I nor the seller is a current T-Mo customer. The seller was eligible to have the phone unlocked before he got off of the T-Mo network, and failed to exercise that right. He tried to get them to unlock it after he left, but they won't do that.

Asking T-Mo to unlock the phone is not an option. It has already been explored.
[Xiaomi Poco X3 Pro] Alisson1397:
​

Havoc-OS 4.x is based on AOSP, inspired by Google Pixel.​

Has a refined Material Design 2 UI crafted by @SKULSHADY.​

Many useful features that provide a smooth premium experience.​

Just flash and enjoy...​

https://photos.app.goo.gl/WSbmYy7QeB6K9CSn6​

Founder & Lead Developer:​

SKULSHADY (Anushek Prasal)​

​

DevOPS & Scaling:​

Irongfly (Sukeerat Singh Goindi)​

​

Support Team:​

theo.j22 (Tushar Jain)​

​

If you like our work and would like to support this project then please consider donating.​

PayPal: https://www.paypal.com/cgi-bin/webs...ss=WFJG3Q8VUF49U&currency_code=BRL&source=url​

UPI: anushekprasal@okhdfcbank​

ROM: https://havoc-os.com/device#vayu​

About Us: https://havoc-os.com​

Recovery: https://twrp.me​

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

Telegram Support Group: https://t.me/+xesyU34aI7k2NWM1​

Telegram Announcements Channel: https://t.me/Havoc_OS​

Code Review: https://review.havoc-os.com​

1. Download the ROM, GApps (Optional), Magisk (Optional) from the links above.​

2. Wipe System, Data, Dalvik, Cache.​

3. Flash the ROM, GApps (Optional), Magisk (Optional).​

4. Reboot and Enjoy.​

LineageOS (https://github.com/LineageOS)​

Crdroid (https://github.com/crdroidandroid)​

Pixel Experience (https://github.com/PixelExperience)​

And all the other Developers, Testers, Donators and Users.​

https://github.com/Havoc-OS​

GitHub - Havoc-Devices/android_kernel_xiaomi_vayu: Kernel Tree for POCO X3 PRO

Kernel Tree for POCO X3 PRO. Contribute to Havoc-Devices/android_kernel_xiaomi_vayu development by creating an account on GitHub.

github.com

​
[Xiaomi Poco X3 Pro] eyebiz:
There's official Havoc-OS available for vayu here: https://havoc-os.com/device#vayu
[Xiaomi Poco X3 Pro] nasrhamho:
View attachment 5708801

good afternoon, tell me how to make the reading function work, it does not respond to pressing at all