Xiaomi broke thermals/max frequencies in a recent update.
github.com
Hey. I would guess this has to do with the device hardware (which was built and optimised to work better in Europe, if you bought it there). In Mexico, there may be different LTE bands mainly used than in Europe. If your device modem is only capable of using some of those used in Mexico, it may have less connectivity options. This may lead to worse signal reception and higher power expenses to keep the connectivity as good as possible. Just a guess, though.
Sorry for the late response, but LineageOS for MicroG is an *unofficial* fork.LineageOS for microG
lineage.microg.org
actually since I M very stubborn I finally found a solution to get full 3,2 ghz on snap 870 I simply replaced the two files marked in the screenshot and set correct permission ,everything was very smooth no bootloop or eccessive heatXiaomi broke thermals/max frequencies in a recent update.
This commit sets dynamic thermal on boot to fix frequencies being underclocked:
sm8250-common: set default thermal profile on boot completed · AICP/[email protected]
* As parts are removed, including dynamic thermals, set the default thermal profile (dynamic) on boot completed and let mi thermals do the rest Change-Id: Ia22ac19e3458157393ca5d34d5c81a497238e406
or just use FrancoKernelManager, activate Thermal Profiles and set Dynamic profile
since you don't have Google Services on your phone, GMaps may not work properly, I also get "poor accuracy" location on my other MicroG'd LineageOS but it's good enough for me
What happens to people with no root? Or people that just don't know about it? ^^
Thanks for the info on this. It works perfectly. Nevertheless, it is reset with each update. It seems that we would need a magisk module for this or we need to convince the maintainer to adjust the vendor files to better ones.Thanks for the support of LOS on the Poco F3
The default minimum volume settings are a bit too high as the Poco F3 has some powerful speakers.
I suggest lowering the volume values in audio_policy_volumes.xml and default_volume_tables.xml.
These values worked fine for me...
audio_policy_volumes.xml:
<volume stream="AUDIO_STREAM_VOICE_CALL" deviceCategory="DEVICE_CATEGORY_SPEAKER">
<point>0,-3600</point>
<point>33,-2400</point>
<point>66,-1200</point>
<point>100,0</point>
</volume>
<volume stream="AUDIO_STREAM_VOICE_CALL" deviceCategory="DEVICE_CATEGORY_EARPIECE">
<point>0,-3600</point>
<point>33,-2400</point>
<point>66,-1200</point>
<point>100,0</point>
</volume>
<volume stream="AUDIO_STREAM_RING" deviceCategory="DEVICE_CATEGORY_SPEAKER">
<point>1,-4455</point>
<point>33,-3015</point>
<point>66,-1530</point>
<point>100,0</point>
</volume>
<volume stream="AUDIO_STREAM_ALARM" deviceCategory="DEVICE_CATEGORY_SPEAKER">
<point>1,-4455</point>
<point>33,-3015</point>
<point>66,-1530</point>
<point>100,0</point>
</volume>
<volume stream="AUDIO_STREAM_NOTIFICATION" deviceCategory="DEVICE_CATEGORY_SPEAKER">
<point>1,-4455</point>
<point>33,-3015</point>
<point>66,-1530</point>
<point>100,0</point>
</volume>
default_volume_tables.xml:
<reference name="DEFAULT_SYSTEM_VOLUME_CURVE">
<!-- Default System reference Volume Curve -->
<point>1,-3120</point>
<point>33,-2340</point>
<point>66,-1560</point>
<point>100,-780</point>
</reference>
Man been looking for a solution for this. I've been using this rom for months and very often where i keep my hand in my pocket then i find later that i've open differnt apps, browser, and one time pr0n page •~•
Be aware of the Important Note of post #2: * Required * firmware version must be based on MIUI 12.5.3.0 builds.
I can confirm the bootloop with latest update, came from 20220115, I think...
Thank you for this, maybe I'll try to update.
That's what I did. Now I'm wondering if it's because my firmware is old.
What is your--
LineageOS version:
LineageOS Download URL:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
