yashsingh1/xdaforums huggingface dataset:
[Google Pixel Questions & Answers] Averagepanasonichifi:
So

So by wiping nvdata baseband would just not operate anymore(no signals sent, not just not visible to device)? If I wanted to return baseband support, could I remake nvdata?
[Google Pixel Questions & Answers] SubwayChamp:
Some of the mentioned partitions will make the trick, remember always to have a backup, in case you change your mind.
[Google Pixel Questions & Answers] Averagepanasonichifi:
I know that when deleting some baseband related things, the baseband still runs its own microcode. So even with some partitions removed, it still contacts cell towers but just not visible to the device (because baseband firmware runs lower level). Do you know if nvdata fully stops that kind of collection or only makes it inaccessible to the device?
[Google Pixel Questions & Answers] SubwayChamp:
Baseband running at its primary/low level does nothing, because what they can capture needs to be modulated, it´s like a lot of non-sense pieces, they are not collected not stored, in a way that they couldn´t be "reconstructed". This is where the codes take action.
[Google Pixel Questions & Answers] Averagepanasonichifi:
Than

Thank you, i will look into how to do that ( not too sure)
[Xiaomi Mi Pad 5] Rbk.rishabh:
My Xiaomi pad 5 isn't connecting oppo enco m32 neckband. It's specifically not connecting to this device only, not even showing in search.
[Xiaomi Mi Pad 5] Choochter:
Sounds like it might be a neckband problem - try connecting to it with your phone to see if that's the case
[Xiaomi Mi Pad 5] Rbk.rishabh:
Yes it is connecting to other devices smoothly only pad 5 not connecting.
[JASJAR, XDA Exec, MDA Pro General] 71ama7:
Hi, to everybody, i'm using mtty 1.42 and mtty 1.16 and does not have USB port in the combo box, only the mtty 001 but when i try to extract the ROM of my XDA EXEC, in the prompt "USB>" i type "d2s" with my memory card inserted but appear another prompt very fast and don't make nothing in my memory card maybe could be the version or maybe i'm wrong in a procedure.

because the only thing who i can make with my XDA EXEC is use another ROM to make more space in the memory and use more applications. Then i would like extract all the ROM to backup and then try to use another ROM.

Could somebody help me ???

i read the wiki of htc universal and other forums but don't extract all the ROM only a part of them.

the procedure that i'm using is:

- put the XDA EXEC in bootloader mode

- kill process wcecomm of the active sync

- connect XDA, put memory card, run mtty and put combo box in USB

- appears "USB>"and type "d2s" and wait until copy the rom a memory card

- reset the XDA, put the memory and read it

- but appears a message "format "memory" say NO (because is in RAW format)

- use ntrw in DOS mode typing "ntrw read nombrerom.nb0 x:" when nombrerom.nb0 is the image of the ROM and x: is the drive

and other question is: wich process i need to kill in win vista to stop working the active sync?

thanks so much
[General Questions and Answers] godlich:
I installed LineageOS on my pixel 2 without google apps (using lineageOS for microG).

For some applications as duolingo, I am missing speech to text to be able to learn with duolingo by speaking. I was able to use the built-in speech recognition feature in the past with lineageOS, but lost the support when Upgrading. I remember I installed some app, but do not remember which one. I do not want to install the whole Gapps, only the apps needed for this specific feature.

Can someone help me out here please?
[General Questions and Answers] OPaçoca:
Se euIf I'm not mistaken, I downloaded droidx to my s10e and had the opportunity to back up the modified voice synthesis. I tried to install the original version of the synthesis and it is not working even with permission. If you want the mod version I can call you on dm
[General Questions and Answers] conceded:
Follow this guide, also you might need to reboot (I needed, the option to play was disabled)

Text-to-Speech on Android

Guide on how to make TTS work on Android

organicmaps.app
[FYT Android Head Units] lynx_nz:
I've read through a few threads around obd connection issues and such, but this is just generally using Bluetooth to connect to my phone via the Bluetooth app.

The Bluetooth app doesn't seem to save any inputs for name or password, i tried the reset button but that just comes up with "reset unsuccessful"?

Also tried clearing storage under the app, that didnt help :(

Unsure what to try next?

View attachment 5909661
[FYT Android Head Units] louforgiveno:
Device name will be the name of your phone head unit when scanning detects your phone...set phone bluetooth to scan, set head unit to scan (slide down at top of screen to make sure bluetooth is toggled on then enable BT scanning....the Device field should auto populate with phone name detected while scanning....password is 0000....that also should auto populate
[FYT Android Head Units] lynx_nz:
thanks for the response, i tried all kinds of combinations to pair the phone with the headunit. Including other phones. Even the TEYES OBD2 device is never found.

Also, i think those settings are to do with the headunit and not already paired devices. I've seen a few other videos where these fields have TEYES and 0000 predefined. This TEYES video has it called CARKIT

I've tried a few more things;

factory reset (from settings -> user -> backup and reset)

removing and re-plugging in the cabling with Bluetooth antenna

Still no luck, stuck scanning with nothing showing up... (even TEYES OBD2 devices doesn't show) View attachment 5910157

Is this normal ?

View attachment 5910159
[FYT Android Head Units] lynx_nz:
ok, so i think it is resolved... what i did;

followed instructions here, assuming this is a hard reset - https://teyes.co.nz/pages/cc3-2k-april-2023-29-04-2023?shpxid=23b36055-992d-4ddd-8fba-327143c7af43

obtained latest firmware for CC2 2K

modified config.txt updating sys.fyt.bluetooth_type=0

inserted usb stick, let the update run

fixed, bluetooth working again - headunit is named TEYES, code 0000

View attachment 5910173
[FYT Android Head Units] lynx_nz:
one more note, i have heard from another user that pressing the "Reset Bluetooth" button in the Bluetooth app as seen above can actually cause the problem. The only recovery is a full re-flash as above.
[FYT Android Head Units] Scoty42:
You can actually just have that line in the config txt file and it will reset the blue tooth without factory reset or reloading firmware.

I’ve just done it.
[FYT Android Head Units] ponkotsu67:
I just wanted to say thank you for posting this solution! I had the exact same issue and was able to fix it by adding that single line in the config.txt and doing a config-only flash since I'm not rooted.
[FYT Android Head Units] j0hn83:
What number did you both replace with a zero?

Most of the older FYT devices (including the older Teyes) used sys.fyt.bluetooth_type=1 and this could be changed to sys.fyt.bluetooth_type=0

The newer devices seem to use sys.fyt.bluetooth_type=7, or sys.fyt.bluetooth_type=0

I'm wondering if your newer units were set to 1 by mistake. It's odd that the included Teyes odb wouldn't even connect.
[FYT Android Head Units] ponkotsu67:
I wasn't able to check on my actual unit before flashing and the latest firmware update config.txt file didn't have that line at all so I added it myself.

In this older firmware update from October 2022, the number seems to be set to 1 so I assume that was the value on my unit when the issue happened. (forgot to mention, I have just the regular CC3)

Is there any documentation that might explain what bluetooth_type 0, 1, or 7 might mean?
[FYT Android Head Units] j0hn83:
It's my belief that 0 uses the Bluetooth module built in to our Unisoc chipsets.

1 uses an additional Bluetooth module installed on our motherboards and 7 uses a newer Bluetooth module on the newer motherboard's (like the CC3 2K and Mekede M6 Pro).

So for your older cc3 you can use 0 or 1 and the newer units can use 0 or 7
[FYT Android Head Units] soundahcker:
double post, sorry !
[FYT Android Head Units] soundahcker:
Hi ! I have the same problem just 3 days after installation...

There is solution without full re installation ?

Or it s possible to modify the text file directly from the unit?

Thanks a lot !

CC3 2k 3+32gb
[FYT Android Head Units] soundahcker:
Hi!

Could you give the steps ?

Thanks a lot !
[FYT Android Head Units] Leapin_FJ:
Can you please tell me how to just change the config txt file with out reloading the firmware?

Thanks in advance
[FYT Android Head Units] Scoty42:
Have everything on the USB except the zip file.

in the config file ensure you set the Bluetooth to either 0 for standard CC3 or 7 for CC3 2K version.

Plug in USB and allow it to do upgrade as normal.

if you are concerned then leave the zip file in there. It takes just as long to complete.
[FYT Android Head Units] Leapin_FJ:
Thanks, appreciate the knowledge
[FYT Android Head Units] j0hn83:
Upload your modified config.txt and your lsec6315update file to a USB flash drive and plug it in to your head units USB port and watch it flash.

No need to add any other files or to do full firmware flash.
[FYT Android Head Units] prokiller1199:
I have same issue of Bluetooth connectivity sometimes on my 7862 unit (not teyes), the name and password is blank. Had to do 2 reboot of system to make it work again. So, I just put those 2 files in the root of USB drive and let it update right. I think the issue happens after I update the firmware.

Another question: Do firmware updates always wipe all my apps settings? I saw this in my updatecfg.txt. According to the explanation, yes it does wiped all my settings and config except my internal storage. It is quite troublesome to set everything back after firmware update. I scare after a full firmware flash will lose my 360 config.
[FYT Android Head Units] j0hn83:
Delete the line twipe_data from updatecfg.txt

If you flash anything that has an AllAppUpdate.bin file then it will wipe the unit. There's nothing you can do about that as it happens automatically if AllAppUpdate.bin is detected.

However you can flash the 6315_1.zip and config.txt without the unit being wiped.

AllAppUpdate.bin = apps/firmware

6315_1.zip = kernel/core
[FYT Android Head Units] prokiller1199:
Ok, noted and thanks.

Regarding my first question, it is correct right if I just wanted to repair my bluetooth connection?
[FYT Android Head Units] j0hn83:
Don't use a config.txt with just that line like in the image you posted.

It should be your full config.txt, which includes many more lines than just sys.fyt.bluetooth_type=X

It contains other important parameters like the orientation of your unit. You can break things by uploading a config.txt with missing lines.

Take a config.txt from a firmware for your exact unit or backup your current config.txt.

This should already contain the sys.fyt.bluetooth_type=X line. If it doesn't have that line then that's probably your issue.

The Bluetooth type number varies depending on your unit and what Bluetooth chip it contains.

sys.fyt.bluetooth_type=0 makes your unit use the Bluetooth built in to the 7862 SoC (works on all units)

sys.fyt.bluetooth_type=(1 to 7) makes your unit use additional Bluetooth chip on the motherboard. This number varies depending on the installed Bluetooth chip.

It's usually 1 on the older Mekedes/Teyes and 7 on the newer Mekedes/Teyes but some units like Atotos can use other numbers.
[FYT Android Head Units] prokiller1199:
Oh, sorry. I misunderstand assuming it only needed the first line.

Yes my model came with 7 type (Mekede M6 Pro Plus). I extract the config.txt from the latest firmware zip.

Thanks again j0hn83 for guiding me through my errors, I'm still learning these stuff.
[FYT Android Head Units] jsensation:
Hello, I have a problem with a newly installed Teyes 2k unit.

I always have the Bluetooth audio option on the phone to only connect for calls and not for multimedia audio. If I disconnect the multimedia audio, the Bluetooth is disconnected. Have you had any more?

In my other uis7862 it went as I wanted. With the oem car radio too.

Thank you
[FYT Android Head Units] AlinBoy:
Hello

I have too cc3 2k 6/128gb

Bluetooth call is some noise in background I can heard and list of my contacts is from A to C but I have over 400 plus contacts this unit have some many issues! :(
[Touch Pro, Fuze General] fadywwf316:
Hi all, after searching with no luck, i'm hoping i can get some help from the great crew on this forum. im not sure what i installed or did with a tweak or cab or whatever but now in drop downs and in some programs, the text is super squished and cannot be read. further, when typing in text boxes in WM (gladly not in this text box), it comes out as white text so i cant read what im writing, any ideas how i can fiz or reset this without a hard format? Wierdly enough, idk when it started or how, thx in advance.
[Touch Pro, Fuze General] m.carroll:
check and see if you enabled landscape cleartype in schaps advanced config 3.3. on my fuze if i enabled landscape cleartype, the text rendering got messed up like you said.
[Touch Pro, Fuze General] g2tl:
a minute late :p
[Touch Pro, Fuze General] callmemoe:
My Fuze does that when clear type is enabled for landscape. Did you by chance enable that option in some tweak program?
[Touch Pro, Fuze General] fadywwf316:
wow ty ty ty, ur all right it seems. i think that fixed it. I shoulda just posted sooner, i've been frustrated with this for weeks! thanks again all!
[Sony Xperia 1 IV] Pandemic:
Also for xperia 1 iii with A13 ?
[Sony Xperia 1 IV] Doom Slayer:
You have different frequencies and no Xperia Stream support, but we can use profile for endurance mode.

Share your config I will take a look.
[Sony Xperia 1 IV] Doom Slayer:
V 0.2 Update

Slightly raised screen temperature limit (it was lower in gaming mode) and modified general camera profile (non stock app?)
[Sony Xperia 1 IV] Doom Slayer:
0.3 Update

Disabled screen fps drop for other game profiles (unless screen itself is hot)

Returned kill switch (previous version will not stop unless other sensors show high temp)

Raised temperature till 64C for camera and game performance profile (same as endurance mode)

P.S.

Seems like Sony maxed out all the frequencies without any throttling and then just shut it it off after it reaches 55C during video recording. No wonder why it overheats lol
[Sony Xperia 1 IV] Orof:
Thank you! just installed v0.3, you actually made me root my phone AGAIN just to enjoy this. wow.

i was wondering if i should keep stock and buy a stick for endurance mode or just root for free, and i chose the free and comfortable option.

ps. i also tried seeing what will happen if i flash different region firmware (54 on 72) - it seemed to work, and i could scan barcodes for e-sim cards, but unfortunately reception wasn't working with the different region firmware. now when i am rooted, i will see if it is possible to flash different MBN files to get VOWIFI working (LET+5G works)
[Sony Xperia 1 IV] Doom Slayer:
Haha, I rooted just to see if it will be possible to implement this mod and pure black background in apps.

Unfortunately you can't just buy any stick and enable endurance mode, device needs to be connected to some external device via usb/hdmi. It almost seems like a way to encourage people to buy compatible accessories. :)

As for different regions I don't think you can enable e-sim on the device that doesn't has the module. Also if you flash Japanese firmware you will have voice recording for calls, but nfc module will break, because they use different technology.

As for enabling VOWIFI it might be possible. You newer know if the difference is in hardware or just limited by software. For example I converted my XZ premium to dual sim by flashing firmware and replacing sim tray.

You can either experiment with newsflasher or manually.

With overlayFS you can "write" to system partitions(unless it's root folder like system or oem), I think I saw something related to connectivity in /product partition.

Just use unsin tool to unpack part of firmware in open it with 7zip.

In case a failure it's nice to have a bootploop protector module, or you can boot in safe mode to disable magisk and start over. However my mod will need reinstallation too. :P
[Sony Xperia 1 IV] Orof:
Suggestion - a couple of changes to the throttle behavior.

this is how phone throttles after 20 mins of CPU test with a fan on the case. as you can see - no dips, very high performance.

View attachment 5915607

however, this is how the phone behaves when there is no fan attached to the phone (and the phone is without a case):

View attachment 5915613

this suggest that some throttling adjustment is in order, as playing games with this amount of throttle will surely be noticeable.

for reference, this is how the phone throttles on stock profile:

View attachment 5915617

if we can make the temp more consistent and less frame drops - it will be great :) (not needing to use a fan as well)

EDIT - Throttling behavior from stock is from the original firmware. it should be possible to extract the thermal engine from the initial catches of the Xperia 1 IV and apply them to the current software (currently the phone throttles more than it did in the past, to around 170k points)

app is CPU Throttling Test
[Sony Xperia 1 IV] Doom Slayer:
@Orof , thank you for your tests! Frame drops are unavoidable, that's the "kill-switch". Without it temperature will keep rising and rising, CPU needs to cool down somehow. :)

How many threads do you use in CPU Throttling test? I don't think default is enough, as with Burnout Benchmark I was able to trigger modem overheat warning when I disabled kill-switch.

I am working on the new version based on endurance mode with throttling at 57C and kill switch at 66C( max for endurance). It may restrict modem when the temperature will be high enough (Happened during 30 minutes recording 4k@120fps). Gonna do couple of tests and upload it.

View attachment 5915781
[Sony Xperia 1 IV] Doom Slayer:
New version is up!

There are two files inside archive now, same logic applies with replacing and setting permissions.
[Sony Xperia 1 IV] Orof:
Annnd still hitting the kill switch for some reason (using the new files)

View attachment 5916741

I wonder why. I wish the throttling was more aggressive so that the kill switch wouldn't be met, while still gaining more performance than stock (215,000 according to gsmarena)

*EDIT -changed the threads amount from the default value (20) to 60, still the same.
[Sony Xperia 1 IV] Doom Slayer:
I used 20 threads.

Maybe you have higher ambient temp?

Also it seems that every device is different for some reason. Some people can film for 15 minutes 4k120fps, others see the thermal warning while just taking photos.

Did you try limiting frequencies with FKM?
[Sony Xperia 1 IV] Orof:
I reckon that the higher ambient temp is the issue here, though it doesn't mean that it throttling cannot be initiated sooner or harder to avoid the kill switch, for those who live in a higher temp locations

Will try limiting via FKM. Can already confirm that via the default perf setting (without the mod), score stabilize at around 170-180k with no sudden jumps, so it is something we should be able to do with a bit more tinkering.

Thanks for all the work! I really appreciate it.
[Sony Xperia 1 IV] Doom Slayer:
With aggressive throttling it will be very similar to kill switch. It will lower frequencies until device will slightly cool down and will do it again after it will heat. On stock it just happens very soon a major performance cuts that's why it's stable on the benchmark. Same can be achieved by locking frequencies with FKM for a specific app/game.
[Sony Xperia 1 IV] Orof:
Thanks for the explanation, I understand now why it behaves this way on stock

I wonder if I can fine-tune the frequencies by editing the thermal-engine.conf (and maybe the change file as well) without needing to use FKM. already tried to make some changes to version 0.3 with no meaningful success. will have to dig deeper :)

Cheers!
[Sony Xperia 1 IV] ragu24:
Try the uperf mod in combination with the modified thermal config file!

It's dynamically able to adjust the frequencies on the fly - just like FKM but dynamic! Combined with the higher thermal limits it should allow for a smoother experience
[Sony Xperia 1 IV] Orof:
Thanks for the suggestion, but when trying to install it on the Xperia using Magisk, installation failed because "Taro is not supported". will try different versions of it ans report back
[Sony Xperia 1 IV] Doom Slayer:
You can try, just make sure to reuse the frequencies from the config like from game save profile.

Basically we have a choice either to have a higher performance with a little bit of drops or lower performance, but more stable.

On default profiles CPU just cust performance in half when it reaches 53C. Which happens like after 1 minute of CPU Throttling Test.

Anything below that reduction will not prevent CPU from building up the heat, but will slow it down. Without external cooling best you can do is to prolong that performance drop moment or castrate your CPU and "enjoy" stability.

Drops are necessary to keep device from going above maximum temperature (when I completely disabled thermal engine it easily went above 70C) because device sucks at getting rid of heat passively.

Main motivation to create this mod was to prolong video recording time, get rid of annoying screen refresh rate switch, as it causing flickering and squeeze a bit more fps out of emulators with prolonging the moment when the CPU gets castrated.

These synthetic tests do not reflect normal usage. If any game or app behaving like that it means poor optimization with an exception of emulators. It's up to users to configure each game to find a balance between stability and better graphics/more fps.

I'am planning to eventually edit balanced and battery safe profiles inside game enhancer, but don't expect miracles.

Meanwhile if anyone wanna contribute, you may lock frequencies with FKM and run the thermal throttling test on each, to find the one which is more stable, so I can use this data in modified balanced game profile.
[Sony Xperia 1 IV] ragu24:
I use this one - one of the latest
[Sony Xperia 1 IV] Doom Slayer:
New version is up!

Basically it eliminates the need to have FKM, as balanced and battery life profiles in game enhancer will castrate frequencies as soon as possible , which will slow down heating (what the point of having maximum performance for a minute anyways? :D) and result more stability.

Frame drops may appear sooner or later, depending on your ambient temperature, if you are using my undervolting profile, phone case (all my tests run in aramid carbon fiber case) and in general it seems that it's random for each device.

Battery safe profile

View attachment 5918081

Balanced profile

View attachment 5918083
[Sony Xperia 1 IV] tronganhha29:
Is there any function that won't work if the bootloader is unlocked for rooting?
[Sony Xperia 1 IV] Doom Slayer:
Widevine L1, video streaming apps like netflix won't have hd quality or won't work at all.
[Sony Xperia 1 IV] Doom Slayer:
New version is up with dynamic frequency adjustment!

Also seems like new overlayFS stopped working, so I uploaded latest working version as well.
[Sony Xperia 1 IV] Orof:
Can confirm new version works better stability wise, test taken with a case on (!)
[Sony Xperia 1 IV] Orof:
Just ran it for an hour without the case. stable as a rock. room temp 20.2C.

TAHNKS!
[Sony Xperia 1 IV] Doom Slayer:
Wouldn't be possible without healthy criticism and excessive testing, so thank you as well :)
[Sony Xperia 1 IV] AJHutchinson:
Hey wish I seen this while I was still using my Xperia 1IV (I kinda give up looking on here as Sony doesn't get much love) any chance you got anything planned with the Xperia 1 V? 🙌
[Sony Xperia 1 IV] Doom Slayer:
Updated to 1.2

This update addresses the heat problem during normal usage (default profile for apps other than camera and games). Should slightly improve battery life
[Sony Xperia 1 IV] hasztagL:
can somebody send me orginal settings? i forgot to backup.