yashsingh1/xdaforums huggingface dataset:
[Sony Xperia 1 III] einhuman197:
Thanks for this info, working fine for me!

I played a bit around with this and tested the brightness values with 150; working fine in terms of short term heat development.

Edit 2: After a few days I start to notice a very slight discoloration of the diffusor with a value of 150. Its not affecting anything and barely visible, but I'd recommend to go lower than 150, because I suspect the LED may get too warm for the diffusor. I changed the guide to use 30 for now (which equals double the brightness compared to stock), please test your values for yourself, its probably better to not exaggerate it.

Make sure you type in the values right! Too high values and the LED Diffusor may melt, or the LED might die. Do this modification at your own risk, no matter at which brightness you target! I am not responsible for side effects resulting from the mod.

With Terminal Shortcut Pro and assigned Root Priviliges I made myself a Home Screen Icon that will boost the values for me in the current "Torch session" once the LED is turned on before. Other terminal emulator apps will work too.

In the Shortcut I set Run with Root and used the following command

echo 30 >> /sys/class/leds/led:torch_0/brightness && echo 30 >> /sys/class/leds/led:torch_3/brightness

Basically just a command that writes the 30 brightness value to the 2 files.

If someone can find a terminal command that turns on the flash in the first place, we could combine the commands to potentially make a simple but working replacement quick settings for the torch.

Edit: Thanks to the XDA Community and a Tool I was able to recreate the Torch experience with a Quick setting

You need https://play.google.com/store/apps/details?id=com.quinny898.app.customquicksettings

You have to buy the premium in app purchase for 1,29€ to unlock Root Command Running. Then you configure your quick setting (choose the Advanced -> Root Command under Preset) and paste the following script (credits to https://xdaforums.com/t/increasing-torch-power-with-root.3637773/post-73098701, modified by me for 1 III)

#!/system/bin/sh

toggle=$(cat /sys/class/leds/led:switch_0/brightness)

if [ "$toggle" = "0" ];then
echo 30 > /sys/class/leds/led:torch_0/brightness
echo 30 > /sys/class/leds/led:torch_3/brightness
echo 1 > /sys/class/leds/led:switch_0/brightness
echo "on"
else
echo 0 > /sys/class/leds/led:torch_0/brightness
echo 0 > /sys/class/leds/led:torch_3/brightness
echo 0 > /sys/class/leds/led:switch_0/brightness
echo "off"
fi

Once again, make sure you type in the values right! Too high values and the LED Diffusor may melt, or the LED might die. Do this modification at your own risk, no matter at which brightness you target! I am not responsible side effects resulting from the mod.

Then you get rename the toggle, give it a nice Torch Icon and set the color to grey. It will function like the normal quick setting: Tap once, it turns on, Tap again, turns off. Even works locked.

Good luck and best regards.
[Sony Xperia 1 III] lollilol:
If you want to use the Google Assistant Button as a torch toggle and also have Quick Settings Toggle (sadly its always toggled on) i found an app that can do both.

You need:

LSposed/Xposed

Root Shell access (adb shell)

Xposed Edge pro

Busybox for Android NDK (Magisk Module)

XperiaGAButtonRemap (Magisk Module)

Open a cmd or powershell

execute adb shell

execute su

accept root permissions on your phone

execute vi /bin/torch

press the key i

paste the script:

press ESC

type :wq and press ENTER

execute chmod +x /bin/torch

Now you can execute /bin/torch as root and it will toggle the torch with higher brightness values.

In Xposed Edge enable "Keys" toggle and open it. Tap on "+ Add" at the bottom, press the Google Assistant Button, it should be recognized as "KEYCODE_PROG_BLUE", then set the action of either click/double click/long press (whatever you prefer as the torch toggle) to execute a Shell command, enter /bin/torch in the input field and enable the "Root access" toggle.

If you want, you can also set other custom things to the Google Assistant button for the other 2 states.

For the quicksettings menu tap on "Quick settings tiles" in the main menu of Xposed Edge and enable the first tile and open the settings for that tile. Set the action, again, to a shell command, input /bin/torch and enable Root Access. You can set the label to "Torch" and choose the Torch icon found in "Built-in icons". As i already said, the toggle will always be turned on for some reason. It just executes a shell command after all.

Good luck
[Sony Xperia 1 III] MK73DS:
Amazing, thank you everyone.

However, please let me insist that this may damage your phone if you put values too high... trust me. I accidentally put a brightness of 350 instead of 150 while trying the script in a terminal, and a few seconds were enough for the plastic underneath the glass to melt... Thankfully, it is still transparent so I can still use my flashlight, but no doubt it could have done a lot more damage if I let it run for longer. So please, use this with a lot of care (and double check what you write).

That's why in lots of countries, rooting voids your (hardware) warranty, you can do physical damage to your device so again, please be careful. Thankfully, this plastic bit and even the LED underneath are easily replaceable (the plastic bit is separated from the rear glass and the LED is on a separate ribbon cable). However, there don't seem to be a lot of OEM replacement parts for this phone yet.
[Sony Xperia 1 III] jaseman:
Seems like a lot of work for little return and added threat of damage to an expensive phone. I agree that the brightness is dimmer than other phones I have had...but I did a test in a completely dark room and it actually is bright enough to find "whatever" you may be looking for. So I can live with it. Maybe Sony will do something to improve it a little?
[Sony Xperia 1 III] einhuman197:
Sony could definitely improve it. But it seems like they had a history for compareably dim Flashlights.

I edited my explanation post to adapt lower brightness, because 150 as value starts to slightly discolor my diffusor, so I suspect we should run it lower.
[Sony Xperia 1 III] MK73DS:
You can't say I didn't warn you! :P
[Sony Xperia 1 III] decomposed:
Indeed flashlight in mark 3 and older xperias is very bad.

I compared it to an iPhone and it's like day and night. Many aspects xperia brand is suffering like front camera, flashlight, no 21:9 pics, missing 4k 60fps recording in main app with stabilization, poor screen brightness, insufficient battery capacity, no any cooling system (especially at this price there should be vapor chamber or any other advanced cooling and not throttling cpu as a solution...), Not to mention regular software apps like Album, email and others :/
[Sony Xperia 1 III] darken5404:
View attachment 5518429View attachment 5518447I got it fixed through sony aftermarket and has ip68,fixed the screen for me by the way
[Sony Xperia 1 III] BlazingKahn35:
On android 12 after rebooting the function stops working.
[Sony Xperia 1 III] cheesepuff:
So I got to the area of the phone you guys specified, but as of today, the default values are WAY different that what yall found. Let me take a few screen shots
[Sony Xperia 1 III] cheesepuff:
Here is the systems default peramitors. Any idea why they are so different?

Edit- Okay, so extra piece to the puzzle. When torch is off, the brightness file is 0, but when it is on the file is set to 15.

editing the file while the torch is on does nothing.

Edit 2 - Just wanted to note that for those who just want a demonstration of the changes possible, the fallowing app will do just that

Release v1.4.6 · BRoy98/GodlyTorch

Merge pull request #2 from TheDorkKnightRises/patch Fix LED file path for OnePlus One (bacon), proper device names for OP Merge pull request #3 from TheDorkKnightRises/patch Fix default double-...

github.com

this app needs root. Run it as a HTC 10 and it works just fine. However, I would like to recommend NOT going over the half way point. its VERY bright and will probably kill your LED if you do. You have manual control over the brightness. You can add it as a shortcut in the drop down menu of your phone. simply use the standard torch button, and then click the godly torch button to activate whatever preset you gave it.

Edit 3 - setting the brightness in Godly Torch to 50% Intensity sets the brightness to 135. Given that we know damage starts to happen at 150, I set the brightness in Godly to 15% (under the "toggle Intensity" shown in the screen shot), which brings the brightness to a value of 45. Its easily double as bright. I would not recommend going past this point.
[Sony Xperia 1 III] Ainz_Ooal_Gown:
I would say by using godly torch as a HTC 10 worked...mind you I double checked the brightness by just hitting the quick toggle and then messing with godly torch. The lower setting is matching just turning on the quick toggle the higher setting is what I'm comfortable with, but idk how long I'm comfortable running it at that brightness.
[Sony Xperia 1 III] darkjake:
For those on stock who use the assistant button :

If it stops working after reboot, copy the binary file to somewhere safe on your sd card, then using XPosed edge just add a long press gesture to your assistant button that recopys the file from your sd card, then sets the permissions again (make sure to check run as root)

cp /sdcard/torch /bin/ | chmod +x /bin/torch
[Sony Xperia 1 III] dschneider5900:
Hello. I have a question. How do you edit the values? I use another folder: sys/class/flashlight and i edit it with root browser. I couldn't edit the files that you said.
[Sony Xperia 1 III] MK73DS:
Use Termux or adb shell and these commands as root

# Set brightness to 150 (change the value for more or less brightness)
echo 150 > /sys/class/leds/led\:torch_0/brightness
echo 150 > /sys/class/leds/led\:torch_3/brightness
# Turn on the flashlight
echo 1 > /sys/class/leds/led\:switch_0/brightness
[Google Pixel 6] aymuhamm:
Hi I am getting an error when trying to relock the bootloader, I reboot into bootloader put in the command to lock "Fastboot flashing lock" get the error below in the image. Any idea why?

View attachment 5475895
[Google Pixel 6] foobar66:
Have you restored the full stock firmware? If not then do that first using: https://pixelrepair.withgoogle.com/carrier_selection
[Google Pixel 6] V0latyle:
I don't recommend using the Pixel Repair Tool unless absolutely necessary.

If you are trying to return your device to absolute stock, I recommend using the Android Flash Tool. You can choose which factory build to flash, whether to wipe the device, and whether to relock the bootloader.
[Google Pixel 6] VozerCozer:
It is likely that you rooted your phone at one point, or perhaps flashed an alternative operating system which does not support verified boot.

Traditionally but not in all cases, re-locking your bootloader requires you to be unequivocally 100% stock. If you plan on being on stock and you are not (which I am assuming), you can either follow the # Flashing Instructions steps on the Nexus/Pixel Factory Images page. If you find that a bit tedious, there is always the flash-all.sh/flash-all.bat which will do this all for you.

After this, your device will be set straight back to factory, and you can follow the steps to re-lock your bootloader.
[Google Pixel 6] V0latyle:
This is why I like to recommend the Android Flash Tool - simply from a perspective of ease of use, and the fact it's practically impossible to get wrong; additionally, the user can elect to lock the bootloader during the process when choosing the flash options. This removes the need to do anything else manually; the tool takes care of the entire process.

It's also very useful for updates.
[Sony Xperia XZs Questions & Answers] abdellahboughrom:
HELLO PLEASE SOMEONE IS POSTING THIS FOR SALE AND HE SAID IT NEED DECODING NO SIGNAL. I WONDER IF I CAN SOLVE THIS PROBLEME BECAUSE IT IS A GOOD DEAL. THANKS.
[Sable] mrs2008:
Hello

Used hp 614c and dont knov how to contact ordered - only sync contact, not sim contact, T9 disebled, htc home screen, and theme for my fon.:confused:

sory for my bad english:mad:

best regards:)

MrS
[Android Stick & Console Computers General] doanga2007:
I have link to manually download Xiaomi Mi TV Stick latest official Android TV ROM becuase Xiaomi Mi TV Stick present ROM to PI.832 ROM and I have newest ROM (with link - https://sites.google.com/site/tweak...sor41EZTUf95ALX-JcGuYBct0KLhpNzaj8WOTuOnhzX1Y and https://dumps.tadiphone.dev/dumps/x...FGnJ4cUrVMsvIrx5KtTsCpzkrsKt84364fU9aH2vCMCeQ) to update Android TV ROM due to I update Xiaomi Mi TV Stick ROM with system update but have the latest software (no update).
[Android Stick & Console Computers General] Selmerz:
Can you help me with a tutorial to flash the stock rom on my device??
[Android Stick & Console Computers General] Kristof120701:
Same problem with my device.
[Android Stick & Console Computers General] jsoaresjun_BRZ_Ce:
Também estou enfrentando o mesmo problema. Como atualizar via adb?
[Android Stick & Console Computers General] nanaychris:
Hi, i´ve updated my Xiaomi mi tv stick to Build PI.1727 via OTA and have lost the hdmi cec functionality and device stability in general, there is a way to downgrade to prior build? Thanks.
[Android Stick & Console Computers General] jsoaresjun_BRZ_Ce:
How did you update via OTA? My upgraded via wifi, plus it only works with a cooler turned on cooling it.
[Android Stick & Console Computers General] nanaychris:
Sorry, my bad, upgraded via wifi, but without a cooler. I guess there is not a way to downgrade...

Now seems to work well.
[Android Stick & Console Computers General] Ankitroy07:
I have the same issue. But now I got the solution.
[Android Stick & Console Computers General] Evilcasa:
Can you post how you did it?? im having the same problem
[Android Stick & Console Computers General] canstb:
and the solution is???
[Xperia Z5 Q&A, Help & Troubleshooting] abdellahboughrom:
HELLO PLEASE SOMEONE IS POSTING THIS FOR SALE AND HE SAID IT NEED DECODING NO SIGNAL. I WONDER IF I CAN SOLVE THIS PROBLEM. I WANT TO GET THIS DEAL IF THE SIM CARD UNLOCK IS SOLVABLE. THANKS
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] companyja:
Hello,

I've been having a terrible problem ever since I tried the ArrowOS Android 12 ROM. I noticed that my phone was notably less smooth when scrolling and it had an ever so slight delay to touch that was infuriating, it's not really that visible but it makes the phone feel very sluggish. Scrolling/flinging would result in a lot of stuttering as well.

I poked around and inspected the kernel, and it seems like there's something wrong with the values for the CPU since the maximum the CPU will go to is 2750 on the fastest core instead of 3.2 and 2250 on the big cores (the LITTLE cores are at 1.8ghz max as intended). Now of course this still shouldn't mean the phone should lag as a snapdragon 870 even at those speeds is plenty fast for things like reddit and youtube and such, but I think this might be related to my problem with the smoothness of the UI.

I've since tried going back to official LineageOS 18.1 but the CPU was still stuck to the lower values and the UI was still not smooth. I've tried going back to the latest global fastboot ROM as well but even on full stock, when installing the fastboot rom through Miflash and doing everything clean, the CPU is stuck at these lower values and the smoothness is affected.

What exactly is wrong with my phone? I also tried a few different kernels and none of them were able to go back to the default SD870 settings. The kernel manager shows the maximum values in the dropdown but if I choose to set them as the maximum CPU frequency, they just revert back as soon as the screen refreshes. Setting the scheduler to performance just sticks the frequency to 2750/2250/1800 at all times, it just won't go to 3200/2500/1800 at all.

Is there any way this can be remedied? Has anyone ever experienced this with a phone? I tried goggling it and found nothing...

Thanks for any answers!
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] m0lly.:
the freqs that you report are normal. Most of the roms that i have tried do not go above 2750. They are underclocked a lil. So no issues with your device
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] companyja:
I understand that default kernels might want to underclock a little but I am literally unable to change these settings and my UI is not smooth at all so I am having a problem, I don't want to unlock the frequencies just for benchmarks or whatever. I am unable to change these frequencies even on the stock global ROM on a fresh fastboot install, I don't think that's normal?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] m0lly.:
that happened with me too. Simple fix was to flash china fastboot *pls do not lock the bootloader on china* just flash and see. The freqs came back to normal for me and switching between freqs works. btw take it easy it'll def be back to normal, try this out^^^
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] companyja:
I actually just started downloading the Chinese rom to try this...thanks for the heads up now I feel a bit more confident in this stupid idea :) just to be sure I am downloading the Redmi K40 fastboot rom from here - I can't find the development ROM for alioth otherwise; am I doing it wrong?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] m0lly.:
yep looks good just don't lock it
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] TheBrutalLicker:
Will this reproduce when flashing anything else than china fastboot rom? Or is it some particular ROMs that will bottle CPU freqs? Sound serious if true, can we actually confirm any of this?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] companyja:
I can confirm that the latest chinese ROM also has these same frequencies. The only time I was able to get the proper CPU values out of my CPU and a smooth experience is when booting a copy of 15.2.1.0 - it's not related to any app since I tried multiple apps to display CPU info, and when using the CPU throttling test, only 12.5.1.0 allows the CPU to get up to 3.2/2.5.

I tried installing LOS over 12.5.1 but it still locks to 2750/2250. Flashing over 12.5.1.0 firmware onto the LOS install also does nothing. I tried putting the 12.5.4.0 kernel (boot.img) over the 12.5.1.0 ROM to see if the kernel alone makes the difference, but aside not being able to use the network with the 12.5.4.0 kernel, the speeds are still unlocked on 12.5.1.0 with the 12.5.4.0 boot.img. It's smelling awfully like Xiaomi locked down the performance of the SD870 to increase battery life/reduce temperatures at some point between 12.5.1.0 and 12.5.4.0 (I haven't tried 12.5.2.0 yet). I remember LineageOS not having this problem when I switched to Arrow in early novermber but Arrow had it out the gate (but I decided to stick with it to try Android 12 out).

Barring some strange inconcievable problem with my device alone it seems awfully like something Apple would do backhandedly, restricting your CPU through the software just-cause. It doesn't seem like it's a kernel or a firmware change but something deeper, as flashing over both from other versions do not change this behavior - it's locked down on some level that doesn't seem as easy to unlock. I don't want to be alarming but I am at a loss right now and I'll probably use 12.5.1.0 till I can find a more sensible solution. I might try installing an old version of LineageOS later to see whether it locks the speeds down, and to try and see which version triggers the newer values.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] m0lly.:
brah those are the freqs on all roms 2750 is super normal

btw china flash was only to fix switching between freqs if they were stuck
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] companyja:
I'm really happy that it's normal however for me it's causing stuttering which is obviously a problem. And either way being fine with your device being arbitrarily locked down is absolutely bizarre to me but maybe that's just me
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] m0lly.:
the change that you're talkin abt from 3.2 to 2750 was always the case with custom roms iirc
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] m0lly.:
stuttering happens on my end too but thats dynamic refresh rate and other things btw stutter happens even on stock meme
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] companyja:
I'm really not sure what your specific issues are but I think I was pretty clear in my first post that the device was working smoothly till I switched to Arrow OS with Android 12, and it works smoothly on stock 12.5.1.0 for me. I'm sure a lot of ROMs stutter a lot (I haven't installed a custom ROM yet that doesn't allow you to force the refresh rate to 60/90/120 anyway) but this wasn't the case with roms such as LineageOS for me before but it seems to be now; sadly the earliest build I can download is 13/11, I wish I saved some of the old builds I had
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] m0lly.:
so you still have max freqs on 12.5.1.0?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] companyja:
Yes 12.5.1.0 has the stock frequencies; 12.5.4.0 has locked down frequencies. Haven't tried 12.5.2.0 (this is all Global ROMs)
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] m0lly.:
i will try flashin 12.5.1.0 and see
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] companyja:
After updating I can confirm 12.5.2.0 is the last known good version with the default maximum clocks. The ROM runs super smoothly and it's a joy to use, if only you could disable dynamic refresh on MIUI...

I've tried two other roms but they both had the new values. I really don't know why there is no option to boost the clocks manually via a kernel manager/different kernel, but even aside from the advertised clocks and all that this has really affected the smoothness of my F3; does anyone have an up-to-date AOSP ROM that has normal clocks? You can check with a kernel manager/downlod CPU Throttling Test and see the maximum clocks you get as soon as you press start.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] m0lly.:
can confirm 12.5.1.0 *tried the indian one* max freqs on all cores btw there are some thermals that do you help you get max freqs on cpu and dynamic clocks on gpu you'll have to check tg for that
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] erghezi:
I also had this issue with arrow 12 and a bunch of other AOSP roms (with terrible antutu and geekbench results), but it's OK with latest version of xiaomi.eu (12.5.18.0.RKHCNXM)

Here is the antutu results. in arrow it was around 602000!

View attachment 5476701
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] lolo9393:
Is that correct?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] jefffrom:
Very interesting thread I'm on arrow 11 and it does come up at 2 .7 but I also don't notice any lag or stutter going back to unlock frequencies do you notice a big hit the battery life?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] TheBrutalLicker:
Thanks for contributing! 2750 freq I suppose?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] TheBrutalLicker:
Maybe we could attempt to create a list of all confirmed 3.2 ghz roms? :)

AFAIK not a single AOSP manages to workaround this issue(al tough would be joyful if we could find one!), how about custom MIUI Rom based 3.2 Ghz builds?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Chalkingwhites:
Was facing this on 12.5.18 vn

Apparently toggling on performance mode sets it back to 3.2
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] michelD:
No problems at all here with MMX MIUI A12 v21.12.1

All the CPUs can go to the max frequency.

Cheers.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] 3zozHashim:
did you try Performance Mode?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] michelD:
Yes sir: in performance mode (in ROM parameters) it still shows the same, while with performance governor CPU 8 is continuously at 3.18 GHz as you can see attached.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Bosstek:
Hey! Are you able to overclock the GPU by any means? People say it is locked and will put you in a bootloop.