yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S22 Ultra] ttnuagmada:
So at some point in the last 3 or 4 months, a lot of my old text messages disappeared. IE there's a few group chats and individual chats where the messages don't go back any further than a year and a half to 2 years. There's not a specific cut off date, and these are threads that go back several years. I've looked through them 3-4 months ago, so i know they were there.

I cannot get them to show back up to save my life. I have a backup of my Note 10+ i had before this, as well as a backup of the note 22 from a few months back. both show 10's of thousands of SMS messages. I factory reset my phone and restored the messages from the note 10 save, but no luck, same issue, they cut off at specific points and wont go back further.

I downloaded SMS backup and restore because I absolutely do not want something like this to happen again, but i noticed that even though my back ups show thousands and thousands of sms messages, SMS backup and restore is only showing 6000 messages. This has me very baffled. Im wondering if one of the recent updates caused this or something? I have made no major changes to anything sms related over the last few months, so for this to just suddenly happen, and me not be able to restore them even after a factory reset just really has me losing my mind. If these messages are gone, then their gone, but it doesnt make sense, and the number that SMS backup and restore says are on my phone vs what should be on there from the restore just don't add up.

Anyone else experience anything like this??

edit: this is an AT&T version
[Samsung Galaxy S22 Ultra] ze7zez:
I can only confirm that SMS Backup and Restore Pro v10.10.001 supports 13692 sms without any problem. I delete the mms because the archive file swells very fast. Currently the archive is 4.7 MB.
[Nothing Phone 1] Tempestgf:
Yesterday I was trying to update the phone with the OTA update of NothingOS (1.1.4) firstly with a sideload in fastboot but then after getting stuck at 47% I decided to flash one by one the images inside the payload.bin of this link:

https://android.googleapis.com/packages/ota-api/package/8841b46d4ec2df9c4c110a6af2e85a34460bba01.zip

Offered by XDA in this thread:

https://www.xda-developers.com/nothing-phone-1-nothing-os-update-tracker/.

After that fastboot flash of all images I restarted the mobile and the screen did not turn on but nevertheless the computer could detect it when it was turned on and as a connected device. rebooted the phone and as a connected device.

Steps to reproduce:

Download the the OTA update from the link gived before.

Extract the folder and dump with payload-dumper-go the payload.bin.

Put my Phone in fastboot mode.

With the platform tools flash all the images.

example: fastboot flash boot boot.img

and so on.

Then reboot my Nothing Phone (1) and get no response from it. Hard Bricked.

I need help because I used as main mobile.

edited as Sib64 Moderator suggested.
[Nothing Phone 1] Sib64:
HI,

Can I suggest you to change the title of your thread by : My Nothing Phone (1) is bricked

instead of your current title, because your NP(1) is not bricked after an OTA update but after you have updated it yourself in another way, which is different.

And in your OP, you explain exactly what you have use as process ;)

The title of your OP is apparently confused for some members.

Use "edit" for modified your title.

Thanks for your comprehension and have a good time to xda (y)
[Touch HD Accessories] ekerbuddyeker:
has anyone ever seen one of these? Do they exist?

I thought about a mini-silicone keyboard that can stick onto / peel off the screen and line up EXACTLY with the keys on the screen. could be a great solution!

Anyone?
[Android Q&A, Help & Troubleshooting] ProIEZRush:
Hello,

I was able to get an update .zip file, I want to edit the update and add some system apps.

I was trying to unpack the system.new.dat but I didn't have any luck, I tried dat2img and several more tools.

How can I do this process?

The update.zip is attached

Thanks
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
Hello and good afternoon, @ProIEZRush

Prior to your next posting please read the guidances that are stuck on top of every forum like

Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

xdaforums.com

and the others. I've moved your thread to Android Genral.

Thanks for your cooperation!

Regards

Oswald Boelcke

Senior Moderator
[Android Q&A, Help & Troubleshooting] ProIEZRush:
bump
[Android Q&A, Help & Troubleshooting] Uniquemobildevicefan:
i will look into it, but i know if you install the rom on a recovery with adb support you can go into adb shell can go to /dev/<by-name directory location>/by-name and copy the partitions after installing, using "cp <partition name> /directory/for/partition/". or "cp <partition name> /directory/for/partiton/name.img" if you want it to be a img immediately and not have to rename it to img. you can also use adb pull for this (most of the times) or you can use dd command, example "dd if=/dev/block/by-name/boot of=/sdcard/boot". but basically all of the methods will copy the whole partition including unused space. you might be able to add options on dd so it wont but as i said i will look into it.
[Touch HD General] Shetlander:
I have used certain CAB files from the Diamond forum to change my clock, icons and windows icons but would like to know if anyone has used the manila customizer to change things.

My reason for asking is that there is a set of icons I like but are only available as a zip file containing the manila folder. Also to remove the curtains I have only found zip files.
[Touch HD General] Mavrick:
Look here:

http://xdaforums.com/showthread.php?t=445497
[Touch HD General] Shetlander:
Thanks for that. Ive read that thread but not taken in fully as I was looking at the screens rather than the how to :rolleyes:.
[Google Pixel 7 Pro] KHANrad_SIN:
So I know we're still in the early stages of this device. But I just wanted to get a thread going for V4A on our device.

For those who came from the 6 Pro like I did, you're probably already aware of this, but for those who did not here's the current situation:

V4A was working fine on Android 12 but when Android 13 came around there were some issues. For most phones they got ironed out and at this point I think basically every other phone on A13 has V4A working EXCEPT for the Pixel 6/6 pro. I tried installing V4A myself on my 7 pro to no avail. I don't know much about the details of why it's not working or what's going on "underneath the hood" so to speak but I can only assume that whatever it is that's causing V4A to not work on my 7 pro is at least somewhat similar to the reason it doesn't work on the 6 pro. There are a few people trying to figure out the issue in a thread over in the 6 pro section on XDA which I will link here if you want to stay more up to date about what's going on:

https://xdaforums.com/t/anyone-get-viper4android-worked-on-a13.4480467/

As a side note, I did manage to get JamesDSP to work on my 7 pro, which is an okay alternative for the time being. Not exactly the same but it's better than nothing for sure. The main thing I don't like about it is that it doesn't auto switch profiles when you change between audio devices of the same type, for example switching from bluetooth earbuds to bluetooth car speakers.
[Google Pixel 7 Pro] Deadmau-five:
I use wavelet and it works really well. Always had trouble getting v4a working
[Google Pixel 7 Pro] Curiousn00b:
Have you tried Viper Android Repackaged?

I just got my device late yesterday, so I haven't bothered rooting just yet, but it's in my plans. There's usually a certain install method to get it working coming from my older devices, but you can try this as well.

GitHub - programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer.

A refined ViPER4Android installer. Contribute to programminghoch10/ViPER4AndroidRepackaged development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] cd993:
The difficulty is now with the Pixel 7 using a different and exclusive cpu architecture, as viper can't even now even attempt to install the driver.

I've reached out to the dev of that one to see what he says....

Update: they got back to me and said as they can't obtain the source code it can't be recompiled to x64.

I see some 'change petition' from 3 years ago asking for it to be updated to x64 but still nothing, and that was years ago.

Ain't looking good for viper on our new pixels by looks of it...
[Google Pixel 7 Pro] sarabraj.singh:
+1 for wavelet. just paid for the full version and the bass booster is prettyy f**king good.

kinda worth the 8CAD$ not to have to deal with Viper issues all the time or everytime the system OS changes.
[Google Pixel 7 Pro] hahimot483:
I found the following program that may be helpful:

Introduction — LIEF Documentation

lief-project.github.io

Maybe it can be used to convert libv4a_fx.so header from 32-bit into a 64-bit library.
[Google Pixel 7 Pro] cd993:
Does wavelet work at a root level? Any additional battery drain using it, or does it work as well as viper?
[Google Pixel 7 Pro] Rolodo334:
Really doubt V4A will ever work again, the project has been abandoned for years.

People try to "patch" it instead, as there has been no real update.

Also the pixel 7 use 64bit only app and drivers, V4A was never updated to use 64bit drivers.

kdrag0n (look on github) has been working on a POC called PhantomAmp to use rootless audio DSP effects.

The app is for patreon sub only for now.

It's in early stage and only a POC so maybe at some point this could be used.
[Google Pixel 7 Pro] KHANrad_SIN:
I honestly always assumed that EQ apps from the google play store were never as good a something like V4A, but I gave Wavelet a shot and I'm really liking it so far. I like that it automatically switches your settings based on what is connected to your phone, a feature I missed from V4A and that was lacking in JamesDSP. I also like that you don't necessarily need to have a persistent notification, it at least gives you the option to swipe it away. Thanks for bringing this to light (can't believe I didn't know about this for so long lol), will be using this now as it seems like a pretty viable alternative to V4A. It's made by the same guy so it's actually quite similar. Will miss spectrum extension and ViPER clarity though.
[Google Pixel 7 Pro] rrusek:
Dolby Atmos works with some success. The issue is that it will take a few reboots to get your pin/pattern working on your lockscreen.

Be sure to enable USB debugging in case you need to disable the magisk modules if you get locked out (adb shell magisk --disable-modules)

https://www.pling.com/p/1908400

RJR
[Google Pixel 7 Pro] Tool Belt:
+1 on your battery drain question.
[Google Pixel 7 Pro] Deadmau-five:
It works without root. I don't see battery drain. Doesn't show up on Accu Battery
[Google Pixel 7 Pro] Ultimoose:
As a long time Viper user, thanks for posting this, it's always a little puzzling to me how audio is a distant priority for Google and how much better it sounds with a little external assistance using the same hardware.

Can't lie, I miss the phones (Samsung?) that let you fine tune both left and right output by playing tones and you indicating if you heard them or not and it adjusting each channel specifically to your abilities to hear each frequency band. As someone with unequal hearing damage this really makes audio better on those phones that provide it.
[Google Pixel 7 Pro] cd993:
A possible light at the end of the tunnel is this project, they are aiming to reverse engineer Viper and modernise the files (hopefully that means using x64!). We'll just have to monitor the progress....

GitHub - AndroidAudioMods/ViPERFX_RE: Reverse Engineering of ViPER4Android FX

Reverse Engineering of ViPER4Android FX. Contribute to AndroidAudioMods/ViPERFX_RE development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] cd993:
Battery Guru here and after only a few mins usage, it's showing up. Not that it's a bad thing of course! Will monitor and see how it goes...
[Google Pixel 7 Pro] iscle:
Hi! I'm one of the guys working on that project, and I can already tell you it's going smoothly :)

We have a few effects already working (although some extra work will be needed to check if they are 1:1, any small change in the code can lead to huge changes in audio quality).

My initial goal was indeed creating a 64 bit version of it, and also removing the need for pathing selinux (and yep, i was able to achieve that, no selinux patches needed amymore).

Overall it's looking good but I don't own a Pixel 7 Pro so I'll need some volunteers to test it once it's ready :)
[Google Pixel 7 Pro] cd993:
This is amazing news!

I'll gladly test it out for you as I've a keen interest in having this working once again! Feel free to send me a message with any contact details, (email or telegram perhaps) if you like and we'll go from there 😊
[Google Pixel 7 Pro] vibrantliker:
I'll gladly test it out also!!!!
[Google Pixel 7 Pro] exocetdj:
Legend!
[Google Pixel 7 Pro] nycdiplomat:
Id like to help test also!
[Google Pixel 7 Pro] Riseaknight:
Just downloaded the new update v0.3.0 and it works now!
[Google Pixel 7 Pro] Schroeder09:
You need AML and busy box for v4a to work? Which version of BB and AML are "official" and work?
[Google Pixel 7 Pro] SchmilK:
Finally got this working with Bluetooth and OMG my ****ty new cars stereo is finally moving some air from the speakers! Here's my dev settings that got it all working!
[Google Pixel 7 Pro] gpvecchi:
Do you know if V4A works on P7Pro with Android 14 beta 3.1? Which version?

Thank you!
[Google Pixel 7 Pro] Lughnasadh:
This one does, but it's still a work in progress so not all the options are enabled just yet.
[Google Pixel 7 Pro] d3viou5:
Without getting into audiophile level of debate, v4a always seems like witchcraft to me. No other EQ I can tweak can match, and I've tried many.

I am by no means clever enough to even understand why viper sounds the way it sounds, let alone how to decompile it. But if someone could package "bass", "clarity" and "dynamic system" into a half decent rootless mp3 player. I would pay whatever the asking price. I'm sure many people on XDA would.
[Google Pixel 7 Pro] iscle:
I've been thinking about this for some time :) I'll probably give it a go, but making a good player requires lots of time...
[Google Pixel 7 Pro] Mrowkarz123:
I've seen there is a rootless version of V4A, but it needs to be installed using TWRP.
[Google Pixel 7 Pro] vibrantliker:
That doesn't make sense. Don't you need to be rooted for TWRP to work?
[Google Pixel 7 Pro] Mrowkarz123:
Hmmm, don't you just need unlocked bootloader to install TWRP and then root using TWRP?
[Google Pixel 7 Pro] d3viou5:
Ok, let me rephrase - a stand alone package that doesn't require an unlocked bootloader. I've done my fair share of custom ROMs over the years and twrp seems to be on the way out. All these hacks to bypass CTS and hardware attestation. Don't get me wrong I love the custom ROM scene, but Viper is more or less my only reason to root these days.
[Google Pixel 7 Pro] Mrowkarz123:
I mean, it's the same for me. I did change the roms on my previous redmi 4X and current redmi note 10 pro, but when I when I get the Pixel 8 Pro I want to stay on stock rom and I don't really wanna go trough the hassle of rooting, but I wanna have the V4A too. I hope there will be a way for it.
[Google Pixel 7 Pro] iscle:
Yep, same here! I root almost only for ViPER! (Although I do use some other things as well from time to time, such as root browser).

Yesterday I started a new project for the audio player, I'll be basing the UI on Spotify since I quite like it and that's what I use daily. If you have any suggestions on features that you frequently use or you find missing from other players, let me know.
[Google Pixel 7 Pro] d3viou5:
Something that plays mp3's, can read and randomise playlists and has Viper built in would be my perfect player.

If you can pull it off you'd be a legend. Just decompiling it alone deserves serious respect. I'm so glad someone with some skills is keeping Viper alive!
[Google Pixel 7 Pro] Mrowkarz123:
Viper built into player would be just part of the thing. The thing with V4A is that it affects all sounds. No matter if you play it on youtube, spotify, from any player, in web browser or any other source, Viper4Android enchances it.

With player, it would only affect audio played in that player.
[Google Pixel 7 Pro] Pixel86:
Does Viper have any affect on Android Auto?
[Google Pixel 7 Pro] d3viou5:
No.... System wide EQ is a bonus for sure, but if it came down to needing an unlocked bootloader or having it built into a player, I'd chose the player every time.
[Google Pixel 7 Pro] iscle:
Viper or any other audio effect can't be fully implemented without root without it's own limitations (check Rootless JamesDSP). I think it'a better to first invest the time in doing a Viper audio player (like I'm doing) and then try to create a more-less working version of the rootless app.

The player can be used by anyone just as any other audio player, while the rootless version is for more advanced public (which knows how to tinker with adb, for example)
[Google Pixel 7 Pro] iscle:
I'm happy to say that I have a working proof-of-concept player which now processes audio with ViPER (it makes use of the new media3 API). :) Looking good! However, looking for media, excluding folders, and handling playlists is harder than I expected to implement...
[Google Pixel 7 Pro] d3viou5:
Holy crap, this is huge!!
[Google Pixel 7 Pro] danw_oz:
I currently use Yaste as an audio player so I can stream my KODI or Plex Music libraries from home in full losseless quality through my phone, makes a huge difference playing any audio, only thing that would make this better would be if I could viper pre out or equalise.
[Google Pixel 7 Pro] iscle:
I'm in the middle of the viper implementation. Would you like a single configuration for all devices (the app won't distinguish between speaker, headphones, bluetooth, etc), or you'd like an specific one for each device that gets selected automagically (like the current ViPER implementation)?
[Google Pixel 7 Pro] d3viou5:
To be honest a single configuration would be fine for me. I'm sure there are others that would disagree, but at the end of the day you're the one with the knowledge and skill to pull this off, so whatever works for you.
[Google Pixel 7 Pro] re_endymion:
Hi iscle,

Thank you very much for this beautiful work that you do and share with the community.

In my personal opinion, the ideal would be to have several profiles depending on the output device on which you want to listen the music. But if at first, it is simpler for you to have only one profile, the multiple profile option could be postponed later.

Thanks again
[Google Pixel 7 Pro] iscle:
I'm writing the "Search" screen which I think is quite important (at least I use it a lot) and I thought I could give a little sneak peek of how the design is looking.

I'm not the best at UI/UX so don't expect anything fancy, I'm getting ideas from other players such as Spotify and adapting it a bit to Material Design 3.

The mini player which is attached to the bottom bar is very close to what spotify has which, for me, can't be any better. It's always displayed, no matter what screen you're on (except when the keyboard is active).

I don't like how the ViPER screen is looking, so any suggestions will be appreciated. Try to follow Material 3 as much as possible.
[Google Pixel 7 Pro] bjevers:
Looking good so far to me. Do you plan on implementing Android Auto support? My music listening mostly occurs in my car.
[Google Pixel 7 Pro] iscle:
Yes! I will support Android Auto, but it will have to be approved by google for it to work (unless you enable developer mode)
[Google Pixel 7 Pro] re_endymion:
Hi Iscle,

it looks good for me, but perhaps it could be possible to collapse disabled features, and only expand the one that are enabled
[Google Pixel 7 Pro] iscle:
Everything is collapsed by default, I only expanded them for the screenshot :)
[Google Pixel 7 Pro] d3viou5:
You Sir are a legend........ if you need a crash test dummy I am ready and willing.
[Google Pixel 7 Pro] Psychlone:
I love the look, I'm not sure what you're looking for, but you've nailed the UI/UX and it appears to be consistent as well as consistent with Google Material You.

Looking forward to this on my Pixel 7 Pro! (already running V4A 5.0 perfectly and without any errors or problems!)
[Google Pixel 7 Pro] A.Priori:
Hoping this will work on P8P
[Google Pixel 7 Pro] bombadier:
Might have to use the Reverse Engineered version as the Pixel 7+ series are 64 bit only, installation is a breeze though just follow the instructions and install both the apk and Magisk module

Releases · AndroidAudioMods/ViPER4Android

ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] iscle:
New update, here's how the player screen is looking, inspired by spotify too (but more closely following material design 3).

PD: If anyone wants to contribute an app icon, feel free to send me a DM. (The app won't be free, so the icon will be payed for, of course).
[Google Pixel 7 Pro] rrusek:
Convolver is grayed out. How do you enable it?

Thanks in advance,

RJR
[Google Pixel 7 Pro] schmeggy929:
As with the other grayed out toggles, they do not work at this time.
[Google Pixel 7 Pro] vibrantliker:
I'm usually the first one for a long time to upgrade devices, software, etc but since the hurdles that Viper experienced once Android 13 hit, I've been staying behind with my Pixel 6Pro on A12.

The 8Pro looks interesting enough to ask if you all feel Viper will work on that device? I'm so dependent on Viper working that I'll stay where I am if I have to.
[Google Pixel 7 Pro] State.of.mind:
Does this work on P7P A14…
[Google Pixel 7 Pro] Lughnasadh:
V4A Reverse Engineered does work on the Pixel 8 Pro, although there are still some options disabled.

The Reverse Engineered version does, although there are still some options disabled.
[Google Pixel 7 Pro] State.of.mind:
Thanks. Is that the GitHub page: "ViPER4Android-RE v0.2.0"
[Google Pixel 7 Pro] Lughnasadh:
Link to the latest version...

Releases · AndroidAudioMods/ViPER4Android

ViPER4Android app configuration files. Contribute to AndroidAudioMods/ViPER4Android development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] mavrovelos:
Any news with your project?
[Google Pixel 7 Pro] iscle:
Hi!

I'm finishing another project first, which is almost ready, and then I'll continue with this. I need to get some help for UI/UX as I'm not that proficient in that field :)
[Google Pixel 7 Pro] vagenrider:
man thanks al lot for all for all the efort you put on this.installed yesterday and works really good if you think that is just an alpha.thanks for giving us the opportunity to have something that we want so much
[Google Pixel 7 Pro] mmarcz:
FYI, If you're running Viper, then download the AMM app for magisk (if you havent already), and download the Pixel Tensor audio decompressor, it really opens up the sound.
[Google Pixel 7 Pro] jake.99x3:
I have no other audio mods installed and flashed the magisk module + installed the V4A APK file yet when I play music I still get this on the Driver status screen:

Suggestions?
[Google Pixel 7 Pro] bombadier:
Try toggling legacy mode, what app you trying to play music with?
[Google Pixel 7 Pro] jake.99x3:
Thank you. Legacy mode fixed it. Using YouTube revanced