yashsingh1/xdaforums huggingface dataset:
[Sony Xperia PRO] Oswald Boelcke:
Hello and good afternoon, @Sner78 Welcome to XDA! I hope you'll always get the support you require and have enjoyable times on our forums.

However, I've closed this thread as duplicate of

Sony xperia x audio optimization problem

Merhaba arkadaşlar, Konular ve modeller eski ama umarım çözüm bulurum. Geçen hafta, xperia x flashtool stok rom'umu en son hale getirdim ve çalışması için kulaklıkları takmam gerekiyor. Birbiri ardına 3_4 parça müzik dinlemek...sesi değiştirmek...

xdaforums.com

Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation, and remember you agreed to adhere to the forum rules when you registered on our private website a few hours ago.

Regards

Oswald Boelcke

Senior Moderator
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] cascous:
Hi,help me pliiiiiiiiz!!!!!

1-my herm100 stuck on windows screen

2-i tried mtty : CMD>task 32

Level=FF

how can i turn it ==>Level=0?????

infos:bootloader:2.03

error 'NO GSM' ???

i tried installing a lot of RUU ROM WM5&WM6 ==>error at 1%

what can i do pliz??help me
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] skeeve666:
hi anf evils

u using a vista pc?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] cascous:
no im using win xp
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] ultramag69:
Try reflashing the SHIPPED STOCK ROM - the rom it came with. This may fix your No GSM problem.

Please note though that once the radio rom gets stuffed it is a SERIOUS pain to get working with a very low success rate. :(

Good luck...:)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] cascous:
how can i do it, i think that my phone should boot to do it?

my herm stuck on windows mobile screen:(

and thanks for your replay!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] ultramag69:
Try a hard reset, hold both soft keys in and reset with stylus. Hold all buttons in until it asks if you wish to reset to factory. Follow directions.

If you haven't already, install Hard SPL, quick search will find it. Then you have to find the ORIGINAL ROM YOUR HERMES CAME WITH... Good luck as this is probably the hardest part...

No guarantees it will work though...

Cheers...:)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] cascous:
i can not install any hard SPL because i have Level=FF so i can not downgrade to SPL 1.09 or 1.01 (i have now 2.03)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] chocogsm:
is there solution of this problem

Level=FF??????????????
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] bendeer:
LEVEL=FF

means that your device is CID locked. I've got the same issue
[Samsung Galaxy A32 4G] tuongg_vietnam:
I'm follow all step in zFont 3 but doesnt work

OS: LumiRom 2.1 ( OneUI 6 )

Phone: Galaxy A32

Model: SM-A325F
[Nothing Phone 2] Snze1:
Has anyone come across a bug with audio notes on Google keep? The app transcribes the speech ok, but the recording that is saved to the note sounds really muffled. All other recording apps work fine...

I'm on unrooted 2.5.2, keep version 5.24.012.06.90
[Nothing Phone 2] MetaP:
If you're experiencing muffled audio recordings in Google Keep while other recording apps work fine, it might be an issue specific to Google Keep's audio processing or a compatibility issue with your device's microphone settings and the app. Ensure Google Keep is updated to the latest version, and try clearing the app's cache. If the problem persists, consider reporting it to Google Keep's support team for further assistance.
[Nothing Phone 2] dlads:
I agree with @MetaP could be it's down sampling the audio to save space perhaps?

Is the audio the same crap quality on pc / browser / other devices?
[Nothing Phone 2] Snze1:
Thanks

Confirmed updated to latest version: yep

Tried clearing the cache: no change

Tried installing keep fresh as a cloned app: no change

Tried on other Android phone: works fine

I'll contact support...

Could anyone confirm whether they have the same issue?
[Nothing Phone 2] dlads:
Where did the audio originate from? So I can replicate the fault?
[Nothing Phone 2] Snze1:
My mouth lol - when you poke the microphone button on the app, it records your voice, transcribes it into the note and attaches the voice recording
[Nothing Phone 2] dlads:
Ah ok so a voice note from your phone...oky dokey...stock app? Could try another voice recorder then save it to keep by attachment
[Nothing Phone 2] dlads:
Yea same for me, not great audio...very scratchy.
[Nothing Phone 2] Snze1:
Yep, all stock 🫤

Thanks for the suggested work around - not super convenient though really; convenience is what makes the standard feature so useful.

No worries, it'll probably start working after the next update... (Google support have been no help at all!)

@dlads - thanks for testing
[Nothing Phone 2] dlads:
I think the problem is it's using a secondary mic..not the main one, report it to the developer... I don't see another way round it tbh.

Strangely I just tried to make a recording and save that to keep but it failed, so not sure what else to suggest.
[Android Auto General] SOFO888:
Hello,

Let's say I want that the media player is always the first app to be open on the head unit.

I have a specific question: is there an intent to start a specific app on the head unit? Is there a way to emulate the touch inputs on the head unit?

Thanks.
[Android Auto General] Renate:
Yes and yes. Although emulating touches is the lowest of the food chain.

input keyevent 209 should start a music-playing app if you have one.

You can check the AndroidManifest.xml on your music app and do something similar:

am start -n com.loud.music/.MusicActivity

Or even start -d file:///sdcard/Music/favorite.mp3
[Android Auto General] SOFO888:
I tried with the activity. But unfortunately the app opened on the phone and not on the head unit.
[Android Auto General] Renate:
Well, then you have to run the Intent on where you want it to run.

You could make a little app on the HU to start the music on Boot Completed.

Or use Tasker. I don't, but some people do.
[Android Auto General] SOFO888:
Thanks for the idea. Unfortunately it is an OEM head unit and I use the Android Auto function.

I can't make any changes on the head unit (proprietary system).

I hope to find a way by an intent to tell the screen manager on Android Auto on the phone to change the app.
[Google Pixel 7 Pro] thegios:
Sometimes, when phone is idle for a while, I get notifications only when I turn on the screen.

It happens for sure with the surveillance home-camera: my wife gets notifications immediately, I get it only if I turn on the screen.

Batt optimization is off for the camera app.
[Google Pixel 7 Pro] TheMystic:
Which phone is your wife using?
[Google Pixel 7 Pro] thegios:
IPhone
[Google Pixel 7 Pro] cldkrs:
this is not the Iphone forum.
[Google Pixel 7 Pro] thegios:
I am complaint about my phone, a pixel 7 pro
[Google Pixel 7 Pro] TheMystic:
Your phone is going into Deep Sleep. Check your general battery settings, and turn off all smart features relating to battery.
[Google Pixel 7 Pro] thegios:
That's what I thought bu cannot find any specific setting
[Google Pixel 7 Pro] TheMystic:
I don't have a Pixel to tell you exactly which menu to look into, but this is definitely caused by the phone going into Deep Sleep, where the phone turns OFF internet, causing background activities to stop/ slow down.

Also, many apps use Google Play Services to push notifications, so you check the settings for that too.
[Google Pixel 7 Pro] simplepinoi177:
You know....this kinda was happening to me until i realized I had "flip to shh" Do Not Disturb enabled and was constantly keeping my phone face down (old habit going back from Motorola Droids)....

I wonder if this could be something so simple....
[Google Pixel 7 Pro] Psych0t1c20:
If you're rooted use a terminal app and type su -c dumpsys deviceidle disable

Then you'll get your notifications instantly. You have to retype the command after every reboot tho.
[General Questions and Answers] Yusuf.H:
Hello I have Samsung Galaxy S5 Mini g800h

I rooted it with ch-root via odin.

Now I want to install TWRP to backup my device.

But in Official site there is 2 way. apk or img/tar

Is there is difference between this methods?

I installed via apk but still I dont know how to use it?

Can someone show me a tutorial for it?

And can I edit my TWRP backup and re-flash it? (for making custom rom)
[General Questions and Answers] EllieCat:
This might explain in

What is the difference between twrp-[version]-[phone].img and twrp-installer-[version]-[phone].zip?

I know I can flash the image and boot it. But what are the zips used for? I'm asking this because I noticed that images are often accompanied/listed with corresponding zip files - not just for TWRP...

android.stackexchange.com

How to use TWRP

TWRP: A Complete Guide to the Custom Android Recovery

TWRP is the most popular custom recovery for Android. It's used to root your phone, flash custom ROMs, unbrick your device, and much more.

www.makeuseof.com

Editing TWRP backup

Edit TWRP Backup (nandroid)

I was looking for a way to edit a TWRP backup. Basically doing a debloat on it. To where it would just contain my apps and data I installed not all the samsung apps and all the other stuff that does not need to be backed up. I have seen where...

xdaforums.com
[General Questions and Answers] xXx yYy:
Here's a simplified comparison:

TWRP backups (nandroid): These comprehensive backups capture entire partitions of your device's storage, including the system, boot, data, and others. They are created within TWRP and used for recovery purposes in case of software malfunctions or data loss.The backups are stored with either .IMG or .TAR file extension.

.ab files: These files usually refer to Android Backup System ( used by ADB ) backups, a different data backup method designed for specific apps and data on supported devices. This backup system is distinct from TWRP and uses ".ab" as its file extension. ADB-created .ab files are not simply compressed data like .TAR files.
[General Questions and Answers] Yusuf.H:
thanks for replies I will check them
[Xperia Z5 Compact Android Development] Berni-0815:
Due to ongoing development, this ROM may be updated frequently.

Please report any unexpected behaviour.
[Xperia Z5 Compact Android Development] Berni-0815:
New version available; see 1st post.

Enforced SELinux mode working

Mobile Data working
[Xperia Z5 Compact Android Development] steve8x8:
Thanks for your ongoing effort. From checking the OP notes, I get that Bluetooth and Camera aren't working for 20.0+ - are the reasons known to be unfixable or will there be hope to get at least BLE support with 20 or/and 21 before 19.1 becomes unsupported?

I'm using a Z5 (and a Z3, and some Galaxy S4minis) as (BT) "remote controllers for Borg implants" and would like to keep them as such for longer...
[Xperia Z5 Compact Android Development] Berni-0815:
The camera is actually not repairable from today's perspective. We simply don't have the ability to "work around" Qualcom and Sony's "closed source" drivers or perform software reverse engineering.

BT is a different story. It works, but you can't connect another device (I tried with an older headset).

But I'm working on it...
[Xperia Z5 Compact Android Development] Berni-0815:
New version available; see 1st post.

Bluetooth now works in theory. It no longer crashes and no longer gives an error message.

But I'm not sure if it really works because I can't test it to the end.
[Xperia Z5 Compact Android Development] steve8x8:
Kudos for getting BT to a state that can be tested, I'll give it a go when the device doesn't have to serve as a Borg controller ;) Any chance to backport that to 20.0?
[Xperia Z5 Compact Android Development] Berni-0815:
As I've written, I'm not very sure that BT is really working. It should be at the same level as in LineageOS 20.0.

If it works there, it will work here and if not... Vice versa.

It's always the same problem with closed-source drivers from Sony and Qualcom that we can't wrap or reverse engineer...
[Xperia Z5 Compact Android Development] Berni-0815:
I have noticed that the battery consumption is very high and that the device always stays slightly warm for this reason.

I still don't know why, I need to investigate this further.

Any help in this matter is greatly appreciated!
[Xperia Z5 Compact Android Development] Eris_Geryrat:
Thank you for resurrecting my long-sleeping z5c
[Xperia Z5 Compact Android Development] Berni-0815:
If anyone is wondering where the March version is... There are changes on the part of LineageOS that are currently preventing the successful creation of a ROM. :oops:
[Xperia Z5 Compact Android Development] Berni-0815:
I am sorry to inform you that I am not able to create a working ROM at the moment.

I can create a ROM, but it crashes immediately after going through the boot animation. The screen stays dark and there is a kernel panic.

I can't see any reason for this.

If someone is able to read the dump files (console-ramoops, dmesg-ramoops-0 and pmsg-ramoops-0) and can draw conclusions about the reason for the kernel panic, I can send them these files.
[Xperia Z5 Compact Android Development] alex009988:
Have you tried to disable livedisplay? Maybe you need this commit https://github.com/Alex009988/andro...mmit/ea4adadf9b1f69271de8b2e6e813505a89545f90
[Xperia Z5 Compact Android Development] Berni-0815:
No. But I'll give it a try when I have a little bit more time. Currently I'm very busy...
[Xperia Z5 Compact Android Development] Berni-0815:
Unfortunately, this does not change anything!

BUT, disabling livedisplay in my device-common.mk file prevents the kernel panic! (y)

Unfortunately, the device still does not boot, but keeps trying to start a service “vendor.lineage.livedisplay”. I don't know how to prevent this at the moment. :cry:
[Xperia Z5 Compact Android Development] alex009988:
So it means the problem is connected to livedisplay. I would try to disable livedisplay completely, at devide-common, manifest (hidls) and def config (some mdss flags), use minimal-sepolicy with permessive mode and apply above livedisplay commit to kernel and see if it works.

I now trying to build los20 for my z4 tab, so it means I need around two months before I move to los21 and see if I have the same problem.
[Xperia Z5 Compact Android Development] Berni-0815:
I've disabled livedisplay completely and I don't think is bothers any longer. There is no trace of livedisplay in the LOG's.

In the meantime I can successfully build QPR2 and it boots, but crashes immediately after the boot animation with a kernel panic: Pastebin

addr2line points to this place in the code.

Any idea what this could be?
[Xperia Z5 Compact Android Development] alex009988:
The same result with sepolicy-minimal and permessive kernel?
[Xperia Z5 Compact Android Development] Berni-0815:
I'm always developing in permissive SELinux mode (in my BoardConfigCommon.mk file):

# Enable permissive SELinux mode
BOARD_KERNEL_CMDLINE += androidboot.selinux=permissive

But another build points to another "kernel BUG". It's so weird and frustrating...

kernel BUG at /opt/build/bernhard/los21/kernel/sony/msm8994/mm/slub.c:2495!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
CPU: 1 PID: 3959 Comm: main Tainted: G W 3.10.108-ga4aec17cee4 #1
Hardware name: SoMC Suzuran-ROW (DT)
task: ffffffc01fb02000 ti: ffffffc02e758000 task.ti: ffffffc02e758000
PC is at kmem_cache_alloc_trace+0x144/0x298
[Xperia Z5 Compact Android Development] alex009988:
@Berni-0815 maybe we need to take a look at these commits https://github.com/LineageOS/androi...mmit/4853041f3f85593509677e90626d14255d91466c
[Xperia Z5 Compact Android Development] Berni-0815:
That's a 4.4 kernel... :unsure:

But I'll give it a try.

I don't think that's a good idea! A quick look at the commit shows files that are not present in my kernel sources and that are very different.
[Xperia Z5 Compact Android Development] Berni-0815:
Today my ROM boots up to a certain point in the setup process and then reboots with a “Rebooting now...” message and no kernel panic.

Something is going terribly wrong!
[Xperia Z5 Compact Android Development] Berni-0815:
How do I have to interprete this lines?

Call trace:
[<ffffffc000b25428>] binder_enqueue_work_ilocked+0x2c/0x34

I know, that "ffffffc000b25428" is the program counter, with which I can fetch the line, where the crash occurs:

addr2line -f -e vmlinux ffffffc000b25428
__list_add
/opt/build/bernhard/los21/kernel/sony/msm8994/include/linux/list.h:44

But, what does "binder_enqueue_work_ilocked+0x2c/0x34" means in detail (specially "+0x2c/0x34")?
[Xperia Z5 Compact Android Development] alex009988:
I remember you make a lot of optimizations for los18 in the kernel (binder changes). Maybe some of these have to be reverted, maybe it help. Is it still kernel panic?
[Xperia Z5 Compact Android Development] Berni-0815:
Yes, at the mentioned point: Klick
[Xperia Z5 Compact Android Development] Berni-0815:
At the moment it is important for me to know what “+0x2c/0x34” means!
[Xperia Z5 Compact Android Development] alex009988:
The message you provided "+0x2c/0x34" typically refers to a memory address offset within the kernel code where the error occurred.

"0x2c" and "0x34" are hexadecimal numbers.

"+0x2c" represents the offset from the beginning of the function where the error occurred.

"/0x34" indicates the total size of the function in hexadecimal.

So it should help to pinpoint exactly where in the code the issue occurred. However, without further context or a stack trace, it's challenging or even impossible to determine the specific cause of that kernel panic.
[Xperia Z5 Compact Android Development] Berni-0815:
Ok, here is what I have:

Spoiler content hidden.
[Xperia Z5 Compact Android Development] alex009988:
@Berni-0815 Tarkzim kernel is without binder changes. Is result the same with Tarkzim kernel?
[Xperia Z5 Compact Android Development] Berni-0815:
I've tried it somewhen in the past. Dunno remember if there are changes.
[Xperia Z5 Compact Android Development] Berni-0815:
Tried TarkZim's kernel a moment ago. Same kernel panic, same process-counters (pc), but they're pointing to other lines-of-code.

Nevertheless: The result is quite the same.

Back to my own kernel... ;)
[Xperia Z5 Compact Android Development] alex009988:
Is it possible to get logcat, not only dmesg? One way to get it is to flash last working rom, activate autoconect adb and flash unworking rom. If there is a boot animation there is a chance to get log cat via adb.
[Xperia Z5 Compact Android Development] alex009988:
What if to try to disable these flags

CONFIG_ANDROID_BINDER_DEVICES="binder,hwbinder,vndbinder"

CONFIG_ANDROID_BINDER_IPC=y ?
[Xperia Z5 Compact Android Development] Berni-0815:
Unfortunately, there is no adb access at all. The device is not displayed in the "adb devices" list.

Or have I misunderstood you?
[Xperia Z5 Compact Android Development] Berni-0815:
CONFIG_ANDROID_BINDER_IPC is set to "y" in every config file I found. CONFIG_ANDROID_BINDER_DEVICES not...
[Xperia Z5 Compact Android Development] Berni-0815:
Removing this entry changes nothing. I have another plan, but this will take longer time.
[Xperia Z5 Compact Android Development] Berni-0815:
How can I find out which point in the source code is EXACTLY +0x2c? Counting characters is not helpful...
[Xperia Z5 Compact Android Development] Berni-0815:
I was able to compile the ROM and it boots, but “com.android.bluetooth” crashes fatally, and very often “com.android.nfc” crashes fatally, which is very annoying in normal operation. I need to investigate this further.
[Xperia Z5 Compact Android Development] retiredtab:
Post your adb logcat for the two errors above please.
[Xperia Z5 Compact Android Development] Berni-0815:
com.android.bluetooth

com.android.nfc
[Xperia Z5 Compact Android Development] retiredtab:
I have the exact same error message

#00 pc 0000000000abd420 /apex/com.android.btservices/lib64/libbluetooth_jni.so (__system_property_get+0) (BuildId: fbab5b3cb634e74f515b0fdd6044768c)

on a different platform (msm8976). I suspect the problem is upstream. Before QPR2, my bluetooth worked fine. After QPR2, I get the above error message.

There's a bunch of changes pending on AOSP.

https://android-review.googlesource.com/q/project:platform/packages/modules/Bluetooth

https://android-review.googlesource.com/q/libbluetooth_jni

I don't have nfc so I can't help there.
[Xperia Z5 Compact Android Development] retiredtab:
I should mention that I don't have this problem on my arm32 QPR2 builds. The msm8976 is the ONLY arm64 bit platform I have.

As you can see in the error message, it's in the lib64 path library.
[Xperia Z5 Compact Android Development] Berni-0815:
Same here. I really have no idea how to fix it.

Right. Really weird...
[Xperia Z5 Compact Android Development] Berni-0815:
I am starting to need active help. I don't know if my device is slowly dying or if there really are uncontrollable kernel panics.

Here you can download my latest 21.0 ROM: Klick

And here you can download the corresponding executable kernel (7z-compressed; decompress before use): Klick

If your device also crashes, you can get LOG's by following the steps described in my 1st post; section "trouble shooting".

With this LOG and vmlinux you can trace where (and if) a crash occurs.

Just look for a line called “pc:”:

<6>[ 68.762677] pc : [<ffffffc000b2fd48>] lr : [<ffffffc000b30200>] pstate: 60000145
[...]
<6>[ 68.762817] Call trace:
<6>[ 68.762824] [<ffffffc000b2fd48>] binder_enqueue_work_ilocked+0x2c/0x34

This is a program counter and for kernel related program counters you can find out the point of the code by entering this line:

addr2line -f -e vmlinux ffffffc000b2fd48

It would be nice if as many errors as possible could be identified in this way.

But beware: This ROM cannot be played over an older one, as the structure of /data has changed. So be sure to make a backup beforehand!

However, if your device is running without errors *), it must be connected to a charger, otherwise it will restart after a few seconds with a “RescueParty” error message!

*) In this case, a LOG can be taken with a Magisk-rooted device.
[Xperia Z5 Compact Android Development] retiredtab:
This commit allows bluetooth to work for msm8976.

https://android-review.googlesource.com/c/device/linaro/hikey/+/2902255

I did NOT have to recompile the entire code. I just booted into TWRP, mounted system and the edited /system/build.prop to include

ro.zygote.disable_gl_preload=1

rebooted and now bluetooth works.

The reason I didn't see this earlier is because I didn't click on

https://issuetracker.google.com/issues/302408537

In the above, it clearly shows

F DEBUG : #00 pc 0000000000a57680 /apex/com.android.btservices/lib64/libbluetooth_jni.so (__system_property_get+0) (BuildId: cc51eaccc13d4d2280072593f1217b1e)

Let me know if that fixes it for your device.
[Xperia Z5 Compact Android Development] Berni-0815:
Many thanks for this tip!

I will try it as soon as I have a working kernel again!

At the moment I keep struggling with the same kernel memory issues that always point in a certain direction: Linked lists:

struct list_head {
struct list_head *next, *prev;
};
[Xperia Z5 Compact Android Development] Berni-0815:
Unfortunately, com.android.bluetooth still crashes.

But that's not my biggest problem at the moment; the memory errors in the kernel are more serious.
[Xperia Z5 Compact Android Development] retiredtab:
Same bluetooth error message or different one now? Strange, adding that ro.zygote.disable_gl_preload=1 worked for me.

Sorry, I can't help you there as I don't have this Sony device.
[Xperia Z5 Compact Android Development] Berni-0815:
Exactly the same; with the same program counter value.

I understand.

What I don't understand is why this kernel has worked for years in all previous ROM's?