yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] 5upperZZZ:
Thank you very very much, I've been frustrated with How BADLY Whatsapp handling migrating to new s22. As I need those chats for work and I have 4 GB of data (those images and document that I'm to lazy to organize aka delete), so I need to locally restore while Whatsapp give me no choice but restore from Google Drive (zzzzzz).

I specially register to write this thank you messages. That's how much helpful your post is.

As for me to counter DATE being wrong. I use 'My Files' inside old Galaxy phones to compress Whatsapp Folder to 7zip, then copy those to S22 using 'Nearby Shares'. All the DATE is intact after extracting.
[Android Q&A, Help & Troubleshooting] kidb1t:
hi,

i just found this forum and thread.

your post seems helpful.

however, I got stuck on part 6,

"If next part does not work for immediate backup: When it asked you to grant access to your files for Google drive, ignore the message and instead close the app (press □ and wipe Whatsapp away" ->

what is the button you refer to? in this step, i choose button 3 horizontal line, then wipe it all running application, then open again, it show same message, then I tap back button, then it just ask profile name.

what I missed

thanks in advance
[Android Q&A, Help & Troubleshooting] Yuvan 445:
whatsapp uninstall local backup files delete

Sent from SM-M025F using ReLabs
[Galaxy Note 3 Q&A, Help & Troubleshooting] carlitos01:
will it work? thanks
[Galaxy Note 3 Q&A, Help & Troubleshooting] JJEgan:
No as one is Qualcom and one is Exynos .
[General Questions and Answers] ingtatarequena:
please how rootear android 10 motorola g8 power lite?
[OnePlus 10 Pro] galaxys:
FYI....note pre order looks kinda strange?

OnePlus 10 Pro global launch officially scheduled, US pre-orders live right now

The highly anticipated global launch of the OnePlus 10 Pro is finally right around the corner, and the company is teasing some kind of a surprise.

www.phonearena.com
[OnePlus 10 Pro] jcsww:
Considering the US versions had the physical second SIM slot removed in the 9's. I wonder if OnePlus is going to continue that with the 10's. JerryRig's video of the Chinese version breaking easily during his bend test really doesn't inspire me to want to pre-order it, even with only a dollar down.
[OnePlus 10 Pro] terlynn4:
Good question about dual SIM. I bought a dual SIM tray for my 9 Pro but never managed to get it fully working. It'd be nice if the 10 Pro at least has a way to enable it.
[OnePlus 10 Pro] Poloasis:
No 12G/256G variant in the US for now. I'll pass!
[OnePlus 10 Pro] BoboBrazil:
Reading reviews it seems worse than the 9 Pro in alot of ways and better in a couple. I don't think it's worth getting it especially with Oxygen being basically Color OS now.
[OnePlus 10 Pro] jcsww:
All of the cameras are the same as the 9 Pro with the exception of the ultra-wide. For the US market, it's a downgrade in terms of RAM with only the 8GB/256GB version being released currently. I doubt we will see any bend tests on it until close to the Easter launch date in the US. OnePlus is definitely pulling a Samsung here, in my opinion. New model, same old hardware from the previous device for the most part. US models will more than likely not be possible to convert to dual-SIM just like with the 9/9 Pro's. The b/s marketing speak about not being able to deliver 80W fast charging in US models is purely a crock!

Personally, to get me to buy a new device from OnePlus. I want 16GB/512GB variant T-Mobile US model that is possible to convert to dual-SIM. Why? I need to domestically roam on to the US Cellular network as a T-Mobile customer and only devices purchased directly from T-Mobile are permitted to roam on US Cellular (US Cellular roaming requirement). I also carry a Canadian SIM that roams in the US and I don't like carrying two phones. All of the cameras need to be significantly improved and no more stupid holes in the screen. A larger 6.8" screen or maybe even a 6.9" would be something I would hope to eventually see. They have pretty much been using the same screens since the 7 Pro's for the Pro devices. The SnapDragon Gen 1 throttles due to excessive heat on almost all devices using it.
[Samsung Galaxy S22 Ultra] s3fan:
Hi

I'm trying to get more stats from gsam Pro but the adb line won't work. Anybody had any joy with this.

I'm using the line in the app but nothing happens
[Samsung Galaxy S22 Ultra] s3fan:
Sorted.

I'm an idiot who can't follow instructions.

I was typing gsmlabs and not gsamlabs.
[Samsung Galaxy S22 Ultra] hand-filer:
Welcome to my world. :ROFLMAO:
[Samsung Galaxy S21 Ultra] alexman505:
Hi! After 4.1 update, every ringtone in my S21 Utra 5G SM-G998B/DS, starts with incremental sound :mad:

I've tried with a factory reset but nothing change... samsung tell me to take it to service center but I think it's no sense for a software issue!

There's someone who can help me?

It's very annoying thing:cry:
[Redmi Note 10S] averagexiaomiuser:
I recently downloaded arrowOS, aosp. I have tried to fix the headphone jack + bluetooth, bluetooth is the vendor.prop method and didnt work, tried abd shell, didnt work. Wired headphones require 2 apks, called RosemaryTelephony and RosemaryFramework. But none of them are available and justs sends to a 404. If anyone could provide help for either the wired headphones or bluetooth headphones (preferably bluetooth) or the apks, it would be appreciated. Thanks.

View attachment 5570255

For mods : I am not going to link the website nor am advertising the website ^^. I am just showing the fixes it tells me to do but none of them worked.

Thanks!

EDIT : The system/build.prop leads me to a infinite bootanimation.
[Redmi Note 10S] J6idot:
k so

to fix headphones jack:

move /system/overlay to /product

fix bt headphones:

build.prop
[Redmi Note 10S] averagexiaomiuser:
tried it and now i keep booting into recovery unless i flash stock, gsis and arrowOS just send me to orangefox?
[Redmi Note 10S] J6idot:
did you try to modify the build.prop aswell?

because if i remember correctly system is read only
[Redmi Note 10S] averagexiaomiuser:
no, i modified the one in /vendor
[Redmi Note 10S] averagexiaomiuser:
ok so : i follow all the steps for a gsi and the zip for arrowOS, after i reboot, it shows redmi, then it blacks, boots into orangefox beta and basically i flash stock, and it sometimes boots into fastboot from there but only did it once.
[Redmi Note 10S] averagexiaomiuser:
after I do, the console says it failed to mount /vendor , /product /vendor ( it tries to mount vendor twice, it updates partition details and is unable to mount storage, updates, fails to mount, full selinux support is present then it is unable to mount /data/media/Fox/.foxs, says the storage is encryopted and says im on android 13 and sdk 33?
[Redmi Note 10S] averagexiaomiuser:
update : trying twrp and normal fastbootd says this View attachment 5571089
[Shift General] datacrime:
Hi everyone,

I searched the forums and did not find anything... Sorry if it has been discussed before...

I just got a fido data plan (1gb $30), I set it up on the winMo sode and it works great but I have no idea on how to set it up on the vista side... Can anyone help me out... I called Fido and they have no idea and told me to call htc which said to call fido. Basically I getting the run around.

If anyone can tell me how to set it up in vista it would be greatly appreciated.

Thanks
[Shift General] thaihugo:
Do you have the data icon on in the vista side in HTC control center? Do you use a custom rom?
[General Questions and Answers] Malberd:
So as the title says I'm encountering this Download Fail: Sahara Fail: QSaharaServer Fail: Process fail. I'm using the QPST version and proper firmware. This phone is a Chinese version with Global Rom flashed. Is it possible the guy who has done it messed some partitions so it can't be flashed in Qfil?
[Android Head-Units] apa00011:
I need to know if there is any update for this car radio
[Android Head-Units] apa00011:
or some mod

thank
[Android Head-Units] Anton TNT:
Hi, contact your dealer this is an unbranded and unknown device.

First thing is to ask for update or firmware from your dealer or reseller.
[Android Head-Units] apa00011:
It does not have it, it is a Chinese radio adapted to an opel astra with a screen like the Tesla
[Android Head-Units] Anton TNT:
Look for firmware by your build number over ineternet and see if you can find something
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] torekiki:
Thanx! I must flash gsi via Odin over AP?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] agreenbhm:
If by GSI you mean the Lineage .tar file I linked to, then yes. That particular file is more than a GSI, it is a super partition including the GSI, vendor, product, and odm partitions. Flash this via Odin to AP and in the future you can install standalone GSIs of Lineage using TWRP with the instructions at the bottom of the post.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
After formatting data, tablet just keeps booting to TWRP. Won't boot to system.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] agreenbhm:
Read the op. I specifically address this.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] hakkers420:
Hi thanks for all your work. Question , I do step 3 successfully and it boots to OS, but step 4 when I try to install TWRP it fails and when trying to boot I get error "Only official released binaries are allowed to be flashed(vbmeta)" and I need to reinstall stock OS for it to boot again. Any Suggestions what I may be missing or doing wrong?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] agreenbhm:
When you do step 3 and boot to the os make sure you verify that bootloader unlock is still enabled in Developer Options. If it is, I suggest reinstalling stock and then starting over.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] hakkers420:
When I check OEM Unlock it's selected to ON its 'greyed out' bootloader is already unlocked.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] agreenbhm:
Good, that's what it should be. Try reflashing the vbmeta disabler again and then flashing TWRP.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] hakkers420:
So I tried that but it fails in Odin.

<ID:0/004> Added!!

<ID:0/004> Odin engine v(ID:3.1401)..

<ID:0/004> File analysis..

<ID:0/004> Total Binary size: 0 M

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> NAND Write Start!!

<ID:0/004> SingleDownload.

<ID:0/004> vbmeta.img

<ID:0/004> FAIL! (Auth)

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] agreenbhm:
I know I ran into this once the past few days but am having difficulty remembering exactly how I resolved it. I think your best bet is to start from scratch, reinstalling stock and doing a factory reset.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] hakkers420:
Thanks will give it another shot see what happens.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] hakkers420:
On the page for unlocking bootloader that you provided are you supposed to do all 7 steps or can I just do up to step 3 and not worry about 4-7?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] agreenbhm:
Correct, you can stop after 3.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] hakkers420:
Figured it out, before step 4 boot to OS and reenable developer options and USB Debugging.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] hakkers420:
Now step 6 when trying to boot to TWRP it boots to the stock recovery for some reason. I think I may have to take a break for a bit.

edit: after a break and a reinstall of twrp all seems to be good now 🤞
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Noskilldode:
I am a huge fan of GSI but doesnt realy understand what it is and how to use it ( this isnt my first account just forget my pw XD) so it would be a pleasure for me if you would write a few words about it thanks in advantage :_)
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Noskilldode:
thank you you did a amazing work
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] agreenbhm:
In short, a GSI is a special type of system image that is made to work across multiple devices. It stands for generic system image. The ROM that I included in the op is a super image which contains not only the system partition but also the vendor partition, which includes device specific drivers and things like that, plus a couple other partitions.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] lewmur:
What is the syntax to push the fix_brightness file? I have it on the extternal SD card. Can I just copy to a directory on the internal SD?
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] agreenbhm:
Regarding flashing that: this is correct, if you don't have a version with a writable system partition then you won't be able to use that script. However, does the brightness adjustment not work by default? Originally that script was written for my LOS 18.1 release but when doing some kernel development a few weeks ago I found that it didn't seem to be needed after I reflashed the GSI. But then again I had so many changes going on with my device it's possible something else caused that. Anyway, if the brightness slider does work then you don't need to worry about the script.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Mister Monday:
No it doesnt work by default; you have to run the script then format data.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Kudalufi:
No, when I flashed the GSI it was bvS.img, normal vanilla. Specifically lineage-19.1-20220410-UNOFFICIAL-arm64_bvS.img

No, unfortunately the slider is not working for me.

The problem is the new Android-only ext4 feature flag that Google is using called EXT4_FEATURE_RO_COMPAT_SHARED_BLOCKS. It's almost impossible to find any kernels that have ext4 with that feature built in.

I was able to manually apply the patch, though it was with some difficulty:

Take an image of /dev/block/dm-0 onto microsd and move it to a real workstation

Mount it ro, copy off the /system/bin/phh-on-boot.sh script, make the changes to it, and pad it with zeros to 4096 bytes (not strictly required to pad it, but I like to make sure it's exactly one block size)

Find the offset of the phh-on-boot.sh script's block in the filesystem (in my case 0xE1A60000)

dd bs=4096 count=1 seek=57766 conv=notrunc if=ph-on-boot.sh of=system_root.img

Get the image back onto the sdcard and use TWRP to dd it on to /dev/block/dm-0

Which worked to get phh-on-boot.sh patched and on my tablet. But even that still does not make my brightness slider work. It would only take moderate cleverness to automate the above steps into a new fix_brightness.sh, which I would be happy to do, but I don't have the knowledge to debug the slider further.

There is a "PHH Treble" settings that has a bunch of hardware/build settings that I've gone through, hoping that maybe it would tweak something, but nothing seems to make the slider work for me.

The slider isn't a show stopper. TBH, I'm more disappointed that LOS's kernel doesn't have wireguard support, which was 50% of the reason for me doing this (was supposed to be in all Android 12 kernels). But I'm happy to test out any fix if you come up with one, and build a script that will get it into filesystems regardless of whether it can be mounted rw or not.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Kudalufi:
I got the slider working. When I manually patched phh-on-boot.sh by editing its disk blocks before, I made the mistake of altering its data blocks without changing the file size recorded in its inode. Because of this, the OS didn't even see the added slider-fix code in the file because it thought the file was still its old size. Once I went back and disk edited the inode to increase the file size and reimaged that back to my device then the brightness slider began to work on my tablet.

Now that I realize my mistake, I see that scripting this process into a new fix_brightness.sh that automates the process is probably not a good idea.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Kudalufi:
I've found some issues in the first few days of using this. Here is my list and the workarounds I've found for some of them.

Issues and resolutions:

Tablet plays over speaker even when Bluetooth headset (A2DP) is connected

Some A2DP devices will connect, but the tablet won't redirect audio to them. In other cases, attempting to use bluetooth audio causes the device to reboot.

Workaround:

Go to Settings->Phh Treble Settings->Misc Features->Force-disable A2DP offload, checkmark it and reboot. The similar "Disable A2DP offload" setting located in developer settings does

NOT

fix the issue. However, once you have done the above and rebooted, then you can go into developer options and enable the bluetooth HD Audio feature and use the advanced codecs if your headset supports it.

Magisk Causes Reboot when "MagiskHide" is enabled

Once you you enable MagiskHide in Magisk's settings, even if no app has been hidden, then after the next time the tablet is restarted it will begin to spontaneously reboot approximately 90 seconds after booting.

Workaround: Unfortunately the only workaround is for "MagiskHide" to not be enabled when the tablet boots. Every time you want to use MagiskHide you have to enable it globally in Magisk's settings, enable it for the app you need it for, use that app, then disable MagiskHide globally again in Magisk's settings. If MagiskHide is left enabled and the tablet is rebooted, the tablet will enter that reboot cycle and the only way to stop the cycle is to disable MagiskHide in the 90 seconds the tablet works after booting. The tablet will still reboot itself one more time, but after that should be stable again.

Screen Casting (miracast) will never discover other display devices

If you try and enable screen casting, it will search for other devices forever and not find them.

Workaround:

No workaround yet

Brightness Slider Not Working After GSI Flash

The brightness_fix.sh script isn't working for those who don't use a vmdklite image

Workaround:

Flash a vmdklite GSI image. Otherwise this is difficult to fix. The system_root filesystem on non vmdklite GSI images is ext4 that is made with a special flag that isn't widely used or supported. No normal Linux box has support for this flag, and the TWRP kernel apparently doesn't either. To fix this, you have to take an image of your system_root and sector edit it with the patch that fix_brightness.sh would normally do. If you don't already know how to sector edit an ext4 partition to change a file, then this isn't the solution for you. Just flash a vmdklite image.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rhtb4theeyeblnks:
:P wrong post
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] rhtb4theeyeblnks:
I resolved the unknow command error on the VBMETA install step.

So, even though you did it before, you have to go back and enable OEM unlock.

I found on another site that there was a bug maybe that hid the setting all together.

What happen was that you ventured into boot land after unlocking bootloader. It will reset the OEM switch and debugging.

1: do factory reset from twrp

2: boot into stock

3 when asked to set up WIFI DO IT! I know you are going to wipe it in just a sec with the liniage install but this part is crucial. The OEM unlock will be missing if you dont. I skipped everything at first including the wifi and keep getting this issue. Finding report on bug, I was able to see the grey switch of OEM unlocking.

4: Now you can install the vbmeta install as normal.

Thoughts. Seems like its not just graphical. The system doesnt have a variable at all that allowing said commands until the wifi pops up. It doesnt think its BL unlocked until there is a variable (which is unlocked) If the device shuts down without the oem on or off variable, it translates to "not unlocked" and seems to block our elevated commands.

Hope this helps, I was stuck here for 6 hours.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Kudalufi:
This is really interesting since this build has no swap by default. It got me thinking, though, since I've run into the same sluggishness issue...

... and my experience was similar.

I have an FP3 with /e/ on it, and I recently noticed it's configured with zram swap by default. I wouldn't normally have considered zram, but seeing as I've been unknowingly using it for a year already and am really happy with its performance, your observation about kswapd inspired me to try it here.

I used the "stock" magisk zram module with its default config and since I installed it, I have yet to notice any similar responsiveness issues.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] mystifuzz:
From where did you get the "stock" magisk zram module? 🤔
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Kudalufi:
Sorry, you're right - I was doing so many things with Magisk between this and getting microG working, I thought it was just in the list of Magisk modules. But no, it isn't and yes, I did download it. The official location is here.

Also, it doesn't install quite as cleanly as I first thought. It installs fine, but it doesn't auto-start, you have to either manually start it in termux, or make a small change to it to fix the autostart. The reason why this is so is interesting though.

First, getting it installed:

Download the most recent version (as of right now it's zsm_magisk_2022-01-09_10.31.01.zip) and go to Magisks modules tab and install it from storage.

Reboot

At this point the module is installed, but won't run automatically (why below). You can leave it like this and just use something like termux to start it manually. For example, if you want to experiment with how the3 system behaves with it on vs off. To start it manually fire up termux and:

$ su

$ zsm -n

Once it's running, you have to reboot to turn it off. Specifically, zsm -f and zsm -r don't work to turn it off or reset it (more below)

Skip to step 8 if you don't want the zram swap to start automatically at boot

To get it to start automatically with the tablet, use a root-enabled file manager (I use Material Files myself) and navigate to:

`/data/adb/modules/zram-swap-manager`

Tap on "service.sh", if you are using Material Files, it will let you open it in a text editor

Change the switch on line 4 from "-dr" to "-dn". When you're done the line will look like:/data/adb/modules/zram-swap-manager/zram-swap-manager.sh -dn > $log 2>&1

Save your changes and reboot

Log into termux and verify you have your swap:

$ free

So, from what I can tell, the reason that the zsm module isn't working out of the box to start the swap automatically, and the reason zsm can't turn it off, is that this LOS image is already making (and failing at) an attempt at starting a zram swap itself. If you don't install zsm at all, you can use termux to see that a /dev/block/zram0 already exists:

$ su
$ ls -l /dev/block/zram*
brw------- 1 root root 254, 0 1970-12-28 06:31 /dev/block/zram0

This will only exist if something somewhere has used sysfs hot add mechanism at /sys/class/zram-control/hot_add to add a zram device and it's the existance of this failed attempt which is interfering with zsm's ability to turn zswap off. And I think the lack of this zswap is what is causing LOS to choke at even moderate memory usage, because it is configured to expect the zswap to be there. I'd be interested in @agreenbhm 's thoughts on this.
[Samsung Galaxy Tab A series ROMs, Kernels, Recover] mystifuzz:
Aight, thanks. I'll try to install it tomorrow.

EDIT: After proper installation (like in your post) swap does indeed work! I'm going to see if it makes the tablet run better.

EDIT 2: No crashes and freezes after 30 hours, it is finally possible to browse the internet with more than 1 tab! 😄