yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Z Fold 4] _GRIZZLY_:
Hi everyone.

I am still user Fold 2 from 2 years, before was N9>N20U. Previous year I bought S22U which from 7 months now my girlfriend have and I back to my Fold 2.

I was happy with him but want try again back to Note sereis with S23U.

This is great device, excellent battery life, cameras but from 7 days back to F2 for fun (still good power with S865+ and not bad battery life for me) and back again to S23U is hard. Foldable screen is great feature which I use with pleasure.

S pen use from time to time. I know about s pen and case for it to F4 but I don't have experience with convenience this solution - especially carry in jeans pocket this brick.

Now I don't know what will can do... Wait to 2024 after Fold 5 for good come on the market?

It's hard to me sell only 2 months old S23U.

Or maybe don't tired with s23u and replace it for F4?

F2 cover screen is narrow but F4 have little wider and easy use with one hand.

Maybe is here user above both devices and can advice me?
[Samsung Galaxy Z Fold 4] Antyhaker:
Wait, just in case.
[Samsung Galaxy Z Fold 4] sbcdk:
Depends on your local price? I got the Fold4 three weeks ago. Not because I think it is the better device, but because I got it at 50% the price and I highly doubt the new stuff in Fold5 will make it worth double.
[Samsung Galaxy Z Fold 4] _GRIZZLY_:
In guarantee shops still almost 3/4 start price for new and 2/3 for outlet so still high in my country like Poland.

My fold 2 2 years ago bought for 55% start price for new.

So thanks for advice. Maybe when I found discount similar to situation with F2, then worth buy it but if not, so easy wait for coming to market F5
[Samsung Galaxy Z Fold 4] sbcdk:
Yeah. And perhaps even check out the pixel fold being presented on wednesday? The wider front screen seems nice
[Samsung Galaxy Z Fold 4] _GRIZZLY_:
Yes, good proposal. Unfortunately Pixel fold mybe is intersting but it's not for me because this is first fold from pixel and like usually will be a lot of bugs in for example construction or software.

I need device for work so need rely in my device in every situation.

Moreover I very like samsung Ui, which is for me very intuitive. I had Pixel 4XL and after almost 2 years I don't get used clean android. My last clean was Nexus 4 (but I liked this) and next only Galaxy Note series for today.

In pixel fold front screen looks nice but interal have very thick frames and not look good.

And what most important in Poland pixel series isn't official accessible so are issues with purchase and respect guarantee.
[Samsung Galaxy Z Fold 4] sbcdk:
We had issues with Nexus/Pixels not being here in Denmark officially too, for a very long time.

I have used iPhone since 2008, but have had Samsung mobiles at the same time too, ever since Note 1 was released. Didnt enjoy the tiny 3.5” of the iPhones and that is about the same reason I have a Fold now. Apple is just doing everything they can to save money, by selling antiquated hardware…

At some point Samsung decided that Denmark didnt need the Note series anymore, so I more or less stopped buying from them.

My number one issue with Fold4 is the narrow front screen, and that it for that reason unfolds to a square, instead of landscape. But very nice device, besides from that. And yes, I actually think they made the right choice with the cam underneeth the inner screen. Neither screen nor cam is perfect, but a good compromise.

Think you could be right, that first gen folding from Google could have issues. Good point.
[Samsung Galaxy Z Fold 4] joancolmenares:
I'll be honest. I had the zfold 4 and then tried out the S23U for a couple months. Only two things I loved were the camera setup and the screen size (quite different than the ZF4 outer screen), but overall, I went back to the ZF4 as it provides a better work tool I got quite used to the form factor and the inside display is a treat to use once you learn all the tricks
[Samsung Galaxy Z Fold 4] _GRIZZLY_:
Thanks for replies. I like S23U, this is great device but overall is booring.

Fold series give me more fun and look difference compare to other devices.

Now I looking for good pricing F4 and still wait for F5.

I need for daily use 2 simcard and sometimes swap my private simcard to old F2 which still have.

I consider buy F3 because is for good price in my country but shapes, especially front screen are very similar to my F2. Only difference is S Pen support and this is too little
[Samsung Galaxy Z Fold 4] propov8:
I have a F4. Im with Fold since F2. Meanwhile I have tried a couple of ..Pro and ...Ultra devices but like you said all they become boring to me for a couple of days in use. And more important - super uncomfortable because I carry my phone always in the pants pocket. For me the comfort of use is more important than all. Fold is a Transformer. Stage 1 - one hand super friendly. Stage 2 - mutimedia and multitasking beast like no other. I think I cant go back to a bar phone. I have tried with the bests on the market but no chance.
[Samsung Galaxy Z Fold 4] mickliq:
I have both the ZF4 and S23U. The S23U is totally boring next to the ZF4 other than the cameras (which is the only reason I have/keep the S23U). Also, the S23U is super wide and not comfortable to hold (if you have "normal" hands). Even though the S23U has the SD 8 Gen 2, you don't really notice the difference in day to day use. So, ZF4 remains my daily driver, I'm not planning to get the ZF5. If you can swing it, you'll probably be able to trade the S23U for a ZF5 at a great value. Otherwise, get a deeply discounted ZF4 and sell your S23U.
[Touch HD General] michael_r:
Pressing power button all the time is annoying

Thanks
[Touch HD General] Abram:
Just take the stylus out (with gyrator I think).
[Touch HD General] michael_r:
thanks.

But still, what about buttons?
[Touch HD General] staged2:
try this

Do this reg edit and then you can press the up or down volume key and it will wake up from sleep-no need to hit power button anymore

HKEY_CURRENT_USER\ControlPanel\Keybd

set key: defaultkeylock

from 1

to 0

softreset - that's it.
[Touch HD General] CEPi:
Nice quick fix, but it will show the sound level for a few seconds
[Touch HD General] efla:
Hello, indeed looks very nice, but is this fix really wake-up the device from a "power off" state, or just from a "screen off state ?
[FYT Android Head Units] vitdaika:
Hello,

I have CarLink version 2.23.0228.0844 installed on my OledPro head unit.

If I use CarPlay via CarLink, when making or receive calls, the sound suddenly get very loud after 1-2 beeps. And the whole call was very noisy. I believe the problem is from CarLink, as the sound is still normal if I call over the default Bluetooth connection of the head unit.

I tried searching every solution with CarLink but no luck.

Has anyone had the similar problem?
[FYT Android Head Units] 03hdfatboy:
Not familiar with your unit, Mine, carlink Uses Wi-Fi for everything but phone, it uses Bluetooth You might be able to use a config,txt file to correct volume levels and bluetooth version.

you'll need fat32 formatted sd card with the "Isec6315update" out of the full update zip and a config.txt with this on it.

#test

ro.fyt.launcher=com.android.launcher4

ro.fyt.amp_type=0

sys.fyt.bluetooth_type=0

persist.sys.zlink.mic.vol=9.9

sys.fyt.ec_version=6
[FYT Android Head Units] vitdaika:
Thanks bro,

Where can I find the “lsec6315update”?
[FYT Android Head Units] 03hdfatboy:
check inbox
[FYT Android Head Units] marchnz:
Is it an FYT unit, post Android system information including MCU version
[FYT Android Head Units] vitdaika:
Yes. It's a OledPro 12.3 Android head unit.

Android version: 10

Build Number: QP1A. 190711.020 release-keys

System Info: APP 1920×720 2023-03-04 15:37:04

CPU: UIS7862 Octa-Core 1.8GHz@3.0 GB(Memory) + 32 GB(Storage)

MCU Version: 2021.10.09 10:12:29 YIN_53_L6315_G23P48F64_E60_V:1.0
[FYT Android Head Units] surfer63:
Being an Oledpro, where I have never heard off, doesn't tell us it's a FYT.

We can only derive from your MCU that it is a YIN type FYT with manufacturer code 53.

And CarLink is a reverse engineered piece of software to mimic the Android Auto layer in OEM units as good as possible.

Anyway, just like @03hdfatboy already mentioned: As far as I know also under Android Auto the BT connection is used for phone calls.

What might be an option to check is if your phone is set to "use WiFi for phone calls" and try to switch that on/off.
[FYT Android Head Units] vitdaika:
I think OledPro is a new 12,3 inch Android unit in Vietnamese market, since 2022.

As your suggestion, I tried to switch mode of "Call over WiFi" to On then Off on my iPhone 14 Pro, but it doesn't solve the problem.

I backed up the system using your guide post, and forgot the line "don't backup 360 camera". After backed-up, I modified the config.txt with the lsec6315update, and have successfully applied the config.txt, now the sound becomes a little bit better.

But, the system swiped my Camera 360 app. Is there a Camera 360 apk file to re-install it?
[FYT Android Head Units] vitdaika:
please see it installed on my Toyota Corolla Cross 2022
[FYT Android Head Units] surfer63:
So far my backup script did not backup the 360 camera part as the script crashed on units without it.

I will now simply create two scripts: one for 360 camera and one for units without 360 camera.

In the mean time I wrote a script that should (re)install the 360 camera software.

For others: It will install the software, but it will of course only work if your unit really has the (hardware) 360-camera chip installed.

Please try the script: 360_installer.zip and let me know if it works.

As usual: unzip to a clean USB-stick and flash it.
[FYT Android Head Units] surfer63:
Just did that and added them to post #4 of the "General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware" forum thread.
[FYT Android Head Units] vitdaika:
It does not work 😢
[FYT Android Head Units] surfer63:
Strange. The apk should simply be on your system and this script only restores the 360res folder and contents.

My system does not have the 360 configuration so I can't check.

Someone else here with a 360 system and more knowledge about it?
[FYT Android Head Units] thericksizzler:
Same problem….
[FYT Android Head Units] surfer63:
To prevent fragmented info I will answer your cross-posted question here:

What helps a tiny bit is to add the following lines to a config.txt:

persist.sys.zlink.mic.vol=9.9
persist.audio.mic.senstivity=1
persist.btmic.gain=10
persist.btspk.gain=7

Simply put that config.txt and an lsec7862update for a uis7862, or an lsec6316update for a sui8581a, on a blank usb-stick and flash it.

As said: this only helps a little bit. It is just that the internal microsophone sucks. (like I already mentioned in another topic by you where you asked exactly the same).

Also @louforgiveno mentioned above solution a few days ago in a post.
[FYT Android Head Units] thericksizzler:
#callquality

ro.fyt.amp_type=0

sys.fyt.bluetooth_type=0

persist.sys.zlink.mic.vol=9.9

persist.btmic.gain=10

persist.btspk.gain=7[

persist.audio.mic.senstivity=1

sys.fyt.ec_version=6

Would it be enough for me to add these codes?
[FYT Android Head Units] surfer63:
Yes, but the bottom line (ec_version) is not needed.
[FYT Android Head Units] thericksizzler:
I did as you said and changed the config file. but there is no change. I haven't tried it on bluetooth, I just tried it on carplay. the caller's voice is very scratchy. as if the speakers were blown. In my previous tests, the sound in bluetooth was better than carplay, but still not very good.

as a result the config settings did not make any changes.
[FYT Android Head Units] surfer63:
They did make a change if you check your properties.

But I already mentioned that it would be a very minor improvement. It is going from terrible to slightly less terrible.
[FYT Android Head Units] thericksizzler:
I have a question for you, why does the voice of the person on the call sound scratchy to me, related to the internal microphone?
[FYT Android Head Units] surfer63:
You are right. That has nothing to do with the microphone. So far all posts were about noisy, bad sound in general for calling. That is also what the question of the OP and the second person and even your question in post #15 was about: call quality in general.

And in post #17 you even add "#call quality" in the top of your "script".

Anyway, w.r.t. your question: I really have no idea.
[FYT Android Head Units] thericksizzler:
Sorry if I expressed myself wrong. Because, as I said, the call quality in the bluetooth application is not bad at all. but when talking in Carplay, the sound quality suddenly becomes bad.
[FYT Android Head Units] thericksizzler:
Now I compared the call sound quality in bluetooth and carlink applications again.

Sound levels in bluetooth and carplay are not equal. The volume in Carplay works independently of the unit's volume. ( that is, when the volume is at 20 in bluetooth, it starts from 1 again in the carlink application.)

Another issue I noticed is that while the call sound sounds like mono in bluetooth, stereo sounds in carlink.

so in carlink, it feels like the sound is coming from more than one place. maybe it is, I'm not sure, but in the bluetooth application, the sound seems to come from a certain point.
[FYT Android Head Units] j0hn83:
Did your head unit come with this setting or have you added it yourself? If you added it yourself, for what purpose?

I'm curious why you have it under a list labelled #callquality
[FYT Android Head Units] thericksizzler:
No it was an example. There was such a suggestion in the previous comments, so I added it.

OG CODES:

#test
ro.sf.swrotation=0
qemu.hw.mainkeys=0

sys.lsec.navi_bar_height=144

ro.build.fytisbootopen=1

sys.fyt.bluetooth_type=1
# 配置蓝牙类型
# 0：内置蓝牙；
# 1：RDA；
# 2：IVT；
# 3：WQRDA；
# 4: WQBC5

sys.fyt.ec_version=6
ro.fyt.splitscreen=0
persist.fyt.zh_frontview_enable=false

MY EDIT :

#test
ro.sf.swrotation=0
qemu.hw.mainkeys=0
ro.fyt.amp_type=0
sys.fyt.bluetooth_type=0
persist.sys.zlink.mic.vol=9.9
persist.btmic.gain=10
persist.btspk.gain=7
persist.audio.mic.senstivity=1

sys.lsec.navi_bar_height=144

ro.build.fytisbootopen=1

sys.fyt.bluetooth_type=1
# 配置蓝牙类型
# 0：内置蓝牙；
# 1：RDA；
# 2：IVT；
# 3：WQRDA；
# 4: WQBC5

sys.fyt.ec_version=6
ro.fyt.splitscreen=0
persist.fyt.zh_frontview_enable=false
[FYT Android Head Units] j0hn83:
Looks like you have both sys.fyt.bluetooth_type=0 and sys.fyt.bluetooth_type=1

You should only set 1 or the other.

If your unit originally had sys.fyt.bluetooth_type=1 and you have no Bluetooth pairing issues then you should leave it as such.
[FYT Android Head Units] thericksizzler:
Thanks for your respond. I'll fix it as you said. Do you have any other idea about the problem?
[FYT Android Head Units] j0hn83:
I've never used carplay.

Occasionally I've used Android Auto but that uses Bluetooth for audio so the sound is the same as all other calls.

Do you get the same issue with both wired and wireless carplay?
[FYT Android Head Units] thericksizzler:
Tbh I haven't tried wired
[FYT Android Head Units] thericksizzler:
I just tried wired and wireless. There is no difference.

Maybe I'm delusional, but I noticed something.

When i call someone who has an iphone call sound is much better quality. I can say that there is almost no noise.

But even the call sound (beep beep sound) is noisy in android and others. I don't know if it was a coincidence.
[FYT Android Head Units] louforgiveno:
I'm not 100% sure what you're experiencing but I'll mention on my factory headunit with tmobile service I'd get bad audio, the fix was to disable Volte (voice over lte/voice over data transmission basically)

If your phone/service has a similar functionality try playing around with turning it off and testing
[FYT Android Head Units] thericksizzler:
I'll try that ! Thanks for suggestion.

persist.sys.zlink.mic.vol=9.9 and persist.sys.carlink.mic.vol=9.9 whats the difference between them?
[FYT Android Head Units] surfer63:
Actually there are two Carplay/AA apks. One is called carlink and the other zlink, depends on the unit and from which reseller you buy.

If you have carlink, you don't need zlink, and vice-versa.
[FYT Android Head Units] thericksizzler:
Thank you for your explanation. Then as I understand persist.sys.carlink.mic.vol=9.9 is enough don't need zlink
[FYT Android Head Units] surfer63:
Yes, correct.
[FYT Android Head Units] thericksizzler:
Just tried and still same
[OnePlus 8 Pro Questions & Answers] stell52:
Hello there. Do you know if its possible to delete the wifi toggle from the shortcut menu ?. After deleted when i do a reboot it appears back to me.View attachment 5904201
[HTC Excalibur] stickyfingers293:
Ok i might be late with this question, but does anyone know how to use Fring for SIP calling on Dash and have the audio come through the earpiece and not loudspeaker? i cant seem to get a fix for this problem.
[HTC Excalibur] tuppaacc:
no one does! try using a bluetooth or yet Iskoot instead of fring you will get your audio like a a regular call…
[HTC Excalibur] jdoggraz:
Yah or there might be a regestry tweak to fix that...
[HTC Excalibur] stickyfingers293:
Much appreciated. Thanx
[Android Head-Units] the baz:
I have recently installed a TS10 head unit into a Toyota Prado and all is good and works well. All my previous Android head units have remained on during a call if the ignition was turned off and then will stay in hands free mode until the call was ended. On the head unit the call is transferred back to the phone and the head unit shuts down when the ignition is turned off. Is this something that can be changed in a setting or is it a characteristic of the software on the head unit? This is a feature that old Sony handsfree kits had and then when I changed to Android I just took it for grated that all head units would work in the same way, and they did till now.

Hope someone can shed some light on this.
[Realme X2 Pro Questions & Answers] Sudheerdarling:
Hello xdaians, I have a Realme X2 pro that has built-in 90hz that works excellently. all available games can be playable @ 90 fps. But when I try to record the screen using a built-in screen recorder or any third-party screen recorder or any screen share activity causes suddenly falls back to 60hz which gives not more than 60 fps. I think it's an os level fps lock that activates when the screen shares with the recorder app. Is there any way to bypass this? I need to record gameplay @ 90fps and same time able to play @ 90fps. is there any way to achieve this? please Help me out. Thanks in advance.
[Realme X2 Pro Questions & Answers] Sudheerdarling:
i think no one active on this realme x2 pro thead. if any one can see this. give me your suggestion on this please.
[OnePlus Pad] kouzelnik3:
Is there anyone who has any boot.img or knows the correct procedure to root this thing? :)
[OnePlus Pad] ethical_haquer:
I would install Magisk by following the official installation instructions. Let me know if you have any questions after reading through them. :)
[OnePlus Pad] kouzelnik3:
Yeah, that's what I know, but I don't have that boot img or something, yet. :)
[OnePlus Pad] w1nst0n sm1th:
If you can dd the right partition from the tablet, you can have the boot image:

From adb shell, launch the comand "lsblk". You will get a list of partition currently on the tablet. The boot partition should be indicated one way or another.

From adb shell, "dd if=/dev/[insert-boot-partition-name] of=/storage/emulated/0/boot.img"

Tranfert the saved boot.img to your computer.
[OnePlus Pad] kouzelnik3:
Well, by this command I cannot see any boot.img partition, only few others, which is weird. :D

Also according to the "dd" command, it didn't work (screenshots) because of Permission denied.
[OnePlus Pad] w1nst0n sm1th:
Error message
[OnePlus Pad] w1nst0n sm1th:
There is an error in your command:

It's "lsblk", not "ls -blk"

See here for a linux version:

lsblk

You may need to set developer options on the device before being able to run such a command :

Develloper Options

And here an explanation of the dd command:

dd

If you're not sure about dd (you should be very cautious with that command), post a picture of the result of the lsblk command and I will tell you the exact command for dd.

I long quit the android space, but I'm interrested by this tablet since Android 13 has a hypervisor normally included (able to run a virtual machine).
[OnePlus Pad] kouzelnik3:
I have set up the Developer options before, but when I use "lsblk" command, it says "/system/bin/sh: lsblk: inaccessible or not found" which is why I used "ls -lbk". Do you know what be an issue here?

I got same results even with my rooted OnePlus 10 Pro.
[OnePlus Pad] w1nst0n sm1th:
Well. Apparently, lsblk is not included.

You will have to wait for an update to be available on the telegram channel, unpack the update to extract the boot.img (init_boot.img).

See :

https://xdaforums.com/t/guide-magisk-unlock-root-keep-root-oos-13-a-10.4571171/
[OnePlus Pad] kouzelnik3:
I thought that. By the way, which telegram channel has those files?
[OnePlus Pad] horsecharles:
Too bad it's not the variant with more RAM & storage. I'm also very intrigued but know very little apart from couple YouTube videos.
[OnePlus Pad] dreisus:
While we try to gain root. Can we get instructions on how to unlock the bootloader so I don't have to have my storage wiped again when we do get root
[OnePlus Pad] kouzelnik3:
I assume it is basic proces as on any other OP device. OEM unlock, fastboot mode and other fastboot flashing unlock, then yes. Someone can try.
[OnePlus Pad] XxBigBuckxX:
Fastboot oem unlock does not work , Fastboot flashing unlock threw an error but said it was successful but did not wipe data. Manually wipped data and got stuck in a boot loop. Windows will not detect it in recovery mode and I can not get it back into bootloader mode.
[OnePlus Pad] kouzelnik3:
Did you turn on OEM Unlock in developer options? And as you are stuck in bootloop without bootloader mode, I think the only option is service center.
[OnePlus Pad] XxBigBuckxX:
Yes I turned it on before unlocking bootloader, I paniced after it started to bootloop and relocked the bootloader after manually trying to wipe data which could be why I cant get into bootloader. I reached out to support hoping for a remote fix like the oneplus 10T but nothing. I could only get my pc to detect it in edl mode. I'm mailing it in today they didn't have any troubleshooting steps just going to RMA it.
[OnePlus Pad] kouzelnik3:
Well, trying to relock it was definitely the wrong move. RMA will solve it anyway.
[OnePlus Pad] kouzelnik3:
Right after that? You basically just rebooted to bootloader, fastboot and then back to the system, but instead of booting, bootloop again? That's even more weird. 🤔
[OnePlus Pad] XxBigBuckxX:
Yeah , I am pretty confused. Service center is not able to help me again yet (Only provide refund which is not what I want) because the previous service request is still open stuck on the device inspection stage. I am just trying to figure out stuff on my own at the moment untill that gets resolved.

I was able to figure a few more things out but not familiar with MTK as I am edl but I went down that path. I was able to get into preloader mode and also downloader mode. I switched over to linux and used mtkclient and it was detecing the device but giving watchdog errors. 😫
[OnePlus Pad] dreisus:
Has anyone solved the root situation yet.
[OnePlus Pad] CommunistPandaX:
Oxygen Updater supports the OnePlus Pad now, should be able to get the boot.img from that.

OnePlus Pad is supported by our app; A.12 (13.1.0.519) OTA ZIPs are available

It brings the March 2023 security patch along with a few bug fixes

oxygenupdater.com
[OnePlus Pad] poofdragon:
I just unpacked the boot.img, patched, and flashed. Device came back up and I had root according to Magisk. Confirmed with SwiftBackup.

Example commands:

adb reboot-fastboot
fastboot devices
fastboot flash boot_a ./magisk_patched-26100_6jGPY.img
fastboot flash boot_b ./magisk_patched-26100_6jGPY.img
fastboot reboot

Including vanilla boot.img and patched version.