Since there is no way in a GSI (without recompiling stuff) to add proper support for the screen slider, I'm going to see if I can write a shell script to run on update of the value for the sensor that detects the position of the display, however,I don't actually know what sensor this is.
After a bit of testing, I believe there's a magnetic field sensor that detects the change in the field as the screen moves (since moving a magnet over the device can activate the slider detection ) however I am unsure about this.
ambitiousButRubbish said:
Since there is no way in a GSI (without recompiling stuff) to add proper support for the screen slider, I'm going to see if I can write a shell script to run on update of the value for the sensor that detects the position of the display, however,I don't actually know what sensor this is.
After a bit of testing, I believe there's a magnetic field sensor that detects the change in the field as the screen moves (since moving a magnet over the device can activate the slider detection ) however I am unsure about this.
Click to expand...
Click to collapse
I'm not sure how useful it will be to identify the hardware. Somewhere, there must be a driver, and there must also be some way, in the stock rom/kernel, to register an action associated with that driver.
It's a magnetic sensor
and I know this because when i slide it into my magnet dash holder, it activates the slide.
then I tried just sliding a magnet across the back, and yes it activates the slider lol
invisiblewave said:
I'm not sure how useful it will be to identify the hardware. Somewhere, there must be a driver, and there must also be some way, in the stock rom/kernel, to register an action associated with that driver.
Click to expand...
Click to collapse
if i can identify the sensor, i can try to find the file associated with its value in the 'sys' partition, and read this to detect changes, when it changes, this can be used to assign an event etc...
in the same way that i did my flashlight fix for huawei phones with GSIs, this would just be a bash script running accessing the specific files associated with the hardware, as remember android is linux (is unix), so everything is a file, this includes the state of the sensor, so it can be read
ambitiousButRubbish said:
if i can identify the sensor, i can try to find the file associated with its value in the 'sys' partition, and read this to detect changes, when it changes, this can be used to assign an event etc...
in the same way that i did my flashlight fix for huawei phones with GSIs, this would just be a bash script running accessing the specific files associated with the hardware, as remember android is linux (is unix), so everything is a file, this includes the state of the sensor, so it can be read
Click to expand...
Click to collapse
i understand. I'm not an Android developer, but i work in a similar industry
There is also the possibility that the magnetic switch actually pushes some sort of "button" inside the phone, it could even be some sort of magnetic film where a magnet pushes two membranes together to complete a physical circuit like a button.
would "show input touches" or some sort of log viewer be able to see what that input is?
i killed tupac said:
i understand. I'm not an Android developer, but i work in a similar industry
There is also the possibility that the magnetic switch actually pushes some sort of "button" inside the phone, it could even be some sort of magnetic film where a magnet pushes two membranes together to complete a physical circuit like a button.
would "show input touches" or some sort of log viewer be able to see what that input is?
Click to expand...
Click to collapse
judging by the teardown, there's no physical switch.
ive tried aida64, but it doent list all sensors, there is however a hall sensor that does not display a value, that looks somewhat promising, i will investigate this more.
the input is over gpio or similar so show input touches wouldn't work, however, a logcat output might
It's in kernel:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/perseus-p-oss/drivers/halls/halls.c
AndroPlus said:
It's in kernel:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/blob/perseus-p-oss/drivers/halls/halls.c
Click to expand...
Click to collapse
Thanks! As I suspected. All we need now is a kernel programmer who can merge it into the AOSP kernel for the MM3!
I'll still see if I can 'hack' a temporary solution, I'm not a kernel dev (and know very little C) so will try my bash script solution.
Anyways, flashing a GSI doesn't alter the kernel, it's down to the system to communicate with kernel modules, if the system doesn't implement the features, even if it's in the kernel, it won't work.
ambitiousButRubbish said:
I'll still see if I can 'hack' a temporary solution, I'm not a kernel dev (and know very little C) so will try my bash script solution
Click to expand...
Click to collapse
But without the driver in the kernel, there'll be no external notification.
invisiblewave said:
But without the driver in the kernel, there'll be no external notification.
Click to expand...
Click to collapse
True for a custom kernel, but not if you flashed the GSI onto a stock kernel since the driver already exists, it's down to Android to communicate with the kernel, if the communication methods don't exist in the Android system then it doesn't work, conveniently it may however be possible to read the value of the hall sensor through a bash script, and subsequently an app. In the same way that you can turn on an off the flashlight by changing the values in /sys/class/LEDs, regardless of what system (stock kernel though) you are running, will work the same for the hall sensor.
I just need to find what file the system uses as it's interface with the kernel driver, looks like it's over GPIO, which means finding it will be 'fun'
ambitiousButRubbish said:
I just need to find what file the system uses as it's interface with the kernel driver, looks like it's over GPIO, which means finding it will be 'fun'
Click to expand...
Click to collapse
Would the event not be logged in dmesg or kern?
invisiblewave said:
Would the event not be logged in dmesg or kern?
Click to expand...
Click to collapse
i can view events written to logcat, but its simply a log stating the sensor was polled when the screen slides, not what io is being checked, though, looking at the kernel source, gpio 49 and 113 are used, which i cant find in /sys/class/gpio, there is a 'halls' folder under /sys/devices/virtual/misc, which corresponds to the sensor, but it doesn't contain anything of any use, apart from the uevent details, which i cant do nything with anyway
ambitiousButRubbish said:
i can view events written to logcat, but its simply a log stating the sensor was polled when the screen slides, not what io is being checked, though, looking at the kernel source, gpio 49 and 113 are used, which i cant find in /sys/class/gpio, there is a 'halls' folder under /sys/devices/virtual/misc, which corresponds to the sensor, but it doesn't contain anything of any use, apart from the uevent details, which i cant do nything with anyway
Click to expand...
Click to collapse
That's one step further, at least you know the kernel knows about the sensor. I checked dmesg on mine (non-GSI) and I don't see any sign of it. The "everything is a file" mantra is great, but I spend half my life trying to find files in Linux when I have a problem...... I wish IBM would take it and rework it all to make it logical and useable, or better yet, make the IBM i run Linux apps.
invisiblewave said:
That's one step further, at least you know the kernel knows about the sensor. I checked dmesg on mine (non-GSI) and I don't see any sign of it. The "everything is a file" mantra is great, but I spend half my life trying to find files in Linux when I have a problem...... I wish IBM would take it and rework it all to make it logical and useable, or better yet, make the IBM i run Linux apps.
Click to expand...
Click to collapse
im on stock checking all of this, but since im looking in /sys, flashing a GSI or any other system image doesn't affect that, so i know, if i can make it work on stock, chances are, it will work on non stock too, however, should your system flash overwrite /sys, then you may have an issue.
ambitiousButRubbish said:
im on stock checking all of this, but since im looking in /sys, flashing a GSI or any other system image doesn't affect that, so i know, if i can make it work on stock, chances are, it will work on non stock too, however, should your system flash overwrite /sys, then you may have an issue.
Click to expand...
Click to collapse
Yes. Hence my previous comment about merging the driver into the AOSP kernel. It'll be a cold day in hell before I go back to MIUI.
invisiblewave said:
Yes. Hence my previous comment about merging the driver into the AOSP kernel. It'll be a cold day in hell before I go back to MIUI.
Click to expand...
Click to collapse
i understand your point now, theres quite a bit more than just the slider implementation you need though for the device to function correctly with an AOSP kernel. To be fair to MIUI, having come from an honor 9, i only suffered EMUI for a month before i got rid of it, becasue it was so unbearable, MIUI, i dont really mind that much, its actually designed well, and is pretty nice to look at, obviously i still prefer stock android, hence the idea of this, because i could just flash a GSI and still have a somewhat semi functional slider.
ambitiousButRubbish said:
i understand your point now, theres quite a bit more than just the slider implementation you need though for the device to function correctly with an AOSP kernel. To be fair to MIUI, having come from an honor 9, i only suffered EMUI for a month before i got rid of it, becasue it was so unbearable, MIUI, i dont really mind that much, its actually designed well, and is pretty nice to look at, obviously i still prefer stock android, hence the idea of this, because i could just flash a GSI and still have a somewhat semi functional slider.
Click to expand...
Click to collapse
Yes, I know, but the work has already been done on the AOSP kernel, since we have a bunch of non-GSI roms now running (I'm assuming they don't use the OEM kernel, otherwise the driver would be present and the interrupt would work). With the driver merged into the whatever kernel the non-GSI roms are running, we'd then be at the same point with the non-GSI roms as we are with the GSI, at least as far as detecting the slider action goes. Then your app/script would work on either.
invisiblewave said:
Yes, I know, but the work has already been done on the AOSP kernel, since we have a bunch of non-GSI roms now running (I'm assuming they don't use the OEM kernel, otherwise the driver would be present and the interrupt would work). With the driver merged into the whatever kernel the non-GSI roms are running, we'd then be at the same point with the non-GSI roms as we are with the GSI, at least as far as detecting the slider action goes. Then your app/script would work on either.
Click to expand...
Click to collapse
as i said earlier, the GSI (im talking about where you just flash the SYSTEM image, nothing else) ROMs wont detect the event since its handled by the MIUI framework, so whilst the event does take place, the only way of knowing it takes place is having something poll the data the kernel outputs for the event, which would either mean a third party program, or somehow getting the MIUI framework working on AOSP, but you then have the issue of it being MIUI, which you want to get rid of. maybe its worth me looking a the code for the slider implementation in the MIUI framework, if its open source.
ambitiousButRubbish said:
as i said earlier, the GSI (im talking about where you just flash the SYSTEM image, nothing else) ROMs wont detect the event since its handled by the MIUI framework, so whilst the event does take place, the only way of knowing it takes place is having something poll the data the kernel outputs for the event, which would either mean a third party program, or somehow getting the MIUI framework working on AOSP, but you then have the issue of it being MIUI, which you want to get rid of. maybe its worth me looking a the code for the slider implementation in the MIUI framework, if its open source.
Click to expand...
Click to collapse
You've already proved that it's not the ROM detecting the event, it's the kernel. GSI - Xiaomi kernel, slider event detected, no framework in ROM to handle the event. Non-GSI - AOSP kernel, slider event not detected, no framework in ROM to handle the event. If the driver is merged into the AOSP kernel, then GSI & non-GSI roms are in the same boat, needing either an app or your script to handle the event.
So we know the 120hz is only enabled for FHD+ and limited to 60hz on QHD, but there's been some talk from leaks leading up to today saying it may still be possible to get 120hz in QHD using a developer mode option, can anyone confirm this is still possible?
arvz said:
So we know the 120hz is only enabled for FHD+ and limited to 60hz on QHD, but there's been some talk from leaks leading up to today saying it may still be possible to get 120hz in QHD using a developer mode option, can anyone confirm this is still possible?
Click to expand...
Click to collapse
I'd like to know this as well. Hopefully you get an answer from someone who has knowledge within the phone. I pray if there isn't an option that XDA finds a way to do it through ADB like the force 90hz option on OnePlus 7 Pro.
hopefully that exists
I really hope we can Atleast do 90Hz on 1140p.,
arvz said:
So we know the 120hz is only enabled for FHD+ and limited to 60hz on QHD, but there's been some talk from leaks leading up to today saying it may still be possible to get 120hz in QHD using a developer mode option, can anyone confirm this is still possible?
Click to expand...
Click to collapse
Can you try this tasker profile.
Import this little profile here to tasker. You need to give tasker the permissions it asks for within adb please report back
https://taskernet.com/shares/?user=...WrgmW2Mlw=&id=Profile:Selective+120hz+Per+App
Kevtrejo37 said:
Can you try this tasker profile.
Import this little profile here to tasker. You need to give tasker the permissions it asks for within adb please report back
https://taskernet.com/shares/?user=...WrgmW2Mlw=&id=Profile:Selective+120hz+Per+App
Click to expand...
Click to collapse
Anyone tested ? Does this work ?
Thread title is a bit misleading
Hi guys,
Simply question, IT is possible to change refresh rate or software overclock display to more Hz?
Or any APPS on this?
Unlock 90hz or 120hz anything else?
Thanks for answer
:good:
Kasp3rsky said:
Hi guys,
Simply question, IT is possible to change refresh rate or software overclock display to more Hz?
Or any APPS on this?
Unlock 90hz or 120hz anything else?
Thanks for answer
:good:
Click to expand...
Click to collapse
nope , that app used for s20 not work for n10+ , i think n10+ locked to 60hz
Sent from my SM-N975F using Tapatalk
Kasp3rsky said:
Hi guys,
Simply question, IT is possible to change refresh rate or software overclock display to more Hz?
Or any APPS on this?
Unlock 90hz or 120hz anything else?
Thanks for answer
:good:
Click to expand...
Click to collapse
No, if it was the relevant option(s) would be visible and available to us on the phone.
Currently people are using activity launchers to run a menu option for the S20 that is hidden on the Note 10+. While it can be toggled it appears to not work at all on the Note 10+ due to hardware limitations.
scottusa2008 said:
No, if it was the relevant option(s) would be visible and available to us on the phone.
Currently people are using activity launchers to run a menu option for the S20 that is hidden on the Note 10+. While it can be toggled it appears to not work at all on the Note 10+ due to hardware limitations.
Click to expand...
Click to collapse
Do you have a link?
Reaper1337 said:
Do you have a link?
Click to expand...
Click to collapse
Hi,
https://forum.xda-developers.com/galaxy-note-10/how-to/toys-oneui-2-1-update-t4077297
Tried the activity launcher and I assure 100% note 10+ locked to 60hz...
I installed the app and applied the setting as well. Not so much as a placebo effect. Checked at testufo and can confirm only 60hz. Is there anything useful anyone has discovered in this app?
The Problem will be the drivers for the display
To achieve more than 60hz you would have to create a custom resolution and refresh rate
Effectively overclocking the display
Anyone ever checked what resolution and refresh rate the Note 10+ can actually use, by running the shell command “dumpsys display,” in adb?
According to this article the setting option was a mistake.
https://piunikaweb.com/2020/04/07/s...-120hz-refresh-rate-but-dont-get-too-excited/
by the fact the display was launched as purely 60hz it is probably a hardware limitation.
LCD/LED/other panels are manufactured to work at a maximum speed, it will be hardware controlled through the display chips, so unless you can swap out the controller chip and the panel is actually capable of altering the individual points at that speed you are likely never getting past 60hz. so unless the hardware was designed for 120hz and Samsung chose to just massively underclock the screen (but why would they do that when it would have been a good brag?) there is likely no way past 60hz as since the change from CRT the only way to overclock a screen is if the screen is shipped underclocked by the manufacturer.
so the reason it doesn't show up in the standard settings without extra steps should tell you this option being there is a mistake of them not removing the setting deep enough in the software.
Guys im noticing colour shift on the display when the refresh rate switches from 120hz to 60hz in Mi11x.Its so noticeable and i don't know if it's a hardware or software issue and if anybody knows the fix then plz tell .
Sorry to state the obvious, just keep display at 120!!! Sorted
reg66 said:
Sorry to state the obvious, just keep display at 120!!! Sorted
Click to expand...
Click to collapse
Is my phone defective or is this present in every mi11x cause this is a software bug ?
Clear the data of Battery and performance app. That should do the trick. But it will return when you reboot. I do that in mine a few days and it somehow fixed it self. Now I don't do clear data trick. I'm on 120fps all the way with no color/brightness shift.
LynnnXDA said:
Clear the data of Battery and performance app. That should do the trick. But it will return when you reboot. I do that in mine a few days and it somehow fixed it self. Now I don't do clear data trick. I'm on 120fps all the way with no color/brightness shift.
Click to expand...
Click to collapse
I frequently clear the data of Battery and performance app but after some time it goes back to it's original behaviour and im not able to understand if this is a issue with hardware or software and if it's with software is it gonna get fixed miui 13 update or not any idea about this ?
Syed Qaiser Abbas said:
I frequently clear the data of Battery and performance app but after some time it goes back to it's original behaviour and im not able to understand if this is a issue with hardware or software and if it's with software is it gonna get fixed miui 13 update or not any idea about this ?
Click to expand...
Click to collapse
I'm not sure, but try disabling "Smoothen transitions" and "Sunlight mode" in Settings > Display > Brightness level, as well as disabling "Adaptive colors" in Color Scheme section.
I remember doing some of this fixed the problem.
Please share your results with us.
No bro it doesn't help it's still the same.
Is this problem fixed in miui 13 ?
Or is this a hw issue which means my unit is defective ?
I have tested in my phone, I can see color changes in the lapse between 60-120hz transition if the color scheme is saturated and adaptive colors is enabled. You need to try with a hard reset, I know is annoying, but we decide to get a Mibuggi phone.
It's happens to me when on arrowos 12 but setting the minimum refresh rate to 120hz fixes it for me, would prefer to have the minimum set the 60hz but this is my only work around
ErickBls said:
I have tested in my phone, I can see color changes in the lapse between 60-120hz transition if the color scheme is saturated and adaptive colors is enabled. You need to try with a hard reset, I know is annoying, but we decide to get a Mibuggi phone.
Click to expand...
Click to collapse
So is this a software issue that's present on every device or hardware issue thats present on limited devices
Syed Qaiser Abbas said:
So is this a software issue that's present on every device or hardware issue thats present on limited devices
Click to expand...
Click to collapse
I have been reading about and it's not clear at all.
Look to the next thread:
New - Subtle change in screen apperance/color with 120hz enabled
Since I installed Xiaomi EU weekly 21.12.8 (MIUI 12.6) I noticed that the apperence of the screen changes in a subtle way sometimes. For instance, dark elements of the background change to darker shade when I stop scrolling on the google now feed. The screen flickers for one millisecond and than...
xiaomi.eu
Syed Qaiser Abbas said:
Guys im noticing colour shift on the display when the refresh rate switches from 120hz to 60hz in Mi11x.Its so noticeable and i don't know if it's a hardware or software issue and if anybody knows the fix then plz tell .
Click to expand...
Click to collapse
Well I have just spent the past half hour or so trying to reproduce your issue. With 'show refresh rate' enabled in dev options I see no change at all with whatever settings I try. I cannot see or reproduce you issue with my poco f3. However, I am running a custom rom - AICP 16.1.....
I'm not sure if this is the sole reason I don't have your problem, and I'm not saying you don't have a hardware problem. But, why not try a custom rom to see if you can reproduce th issue. I see you have been around XDA for a while so should know your way around flashing a custom rom to check... Might be easier and quicker than sending your phone off for possible repair. Also, one of the first things the repair center may well say (I'm assuming) is to try and factory reset you phone after backing up.
SO, my point is, if you are that worried its a hardware issue, and assuming the service center will just ask you to factory first of all, why not backup as much as you can and try a custom rom... see if it persists.
You can always make a note of what rom version you are running now and download it just in case. Then flash the custom rom and if the problem is still there and you need to send your phone off to the service center, just reflash the original rom locking the bootloader during flash. The service center will never know it has been flashed etc
Syed Qaiser Abbas said:
Is my phone defective or is this present in every mi11x cause this is a software bug ?
Click to expand...
Click to collapse
[CLOSED] Serious Poco x4 pro problems even after latest update ?
I saw this video focusing on various Poco X4 Pro problems including problems with display, camera, fingerprint scanner, microphone and lagging problem on the phone. : Self-promoting video link deleted. Can someone explain the...
forum.xda-developers.com
i got poco x4 pro too and same issue screen flickering and **** POCO needs to do something about this I'm never going to buy a POCO phone.....
reg66 said:
Sorry to state the obvious, just keep display at 120!!! Sorted
Click to expand...
Click to collapse
thats not possible even when one sets the the refresh rate at 120 it automatically reverts it to 60 randomly
RDNRHM said:
thats not possible even when one sets the the refresh rate at 120 it automatically reverts it to 60 randomly
Click to expand...
Click to collapse
same issue brother btw what Phone do u have mine is POCO X4 PRO 5G Global
Syed Qaiser Abbas said:
Is my phone defective or is this present in every mi11x cause this is a software bug ?
Click to expand...
Click to collapse
MIUI one of the best operating system
Bikrommani said:
MIUI one of the best operating system
Click to expand...
Click to collapse
That's totally theoretical....
Syed Qaiser Abbas said:
Guys im noticing colour shift on the display when the refresh rate switches from 120hz to 60hz in Mi11x.Its so noticeable and i don't know if it's a hardware or software issue and if anybody knows the fix then plz tell .
Click to expand...
Click to collapse
I'm facing same problem or bug you say, My device is 11i 5g, it's seems like a software issue to me, allmost all amolet 120hz mi device with OEM miui facing this issue.
same here My device is POCO X4 PRO 5G (Veux)
Good day. Please can someone give advice - i got CN X80pro V2185A 12\256.
When i set screen refreshrate to smart switch i get only 60 and 120 real refresh rate via counter.
if i touch screen 120hz, after 3-4 sec it drops to 60 and never less.
i make full restore, update last firwware, but no changes.
MrDiegoSPB said:
Good day. Please can someone give advice - i got CN X80pro V2185A 12\256.
When i set screen refreshrate to smart switch i get only 60 and 120 real refresh rate via counter.
if i touch screen 120hz, after 3-4 sec it drops to 60 and never less.
i make full restore, update last firwware, but no changes.
Click to expand...
Click to collapse
You're in dark mode I bet. It doesn't work in dark mode it seems. Annoying
nope, not in dark
MrDiegoSPB said:
nope, not in dark
Click to expand...
Click to collapse
OH I see! That looks messed up. Funtouch os? I think that'll probably be fixed with an update cause you seem to be on all the correct options.
You're using auto brightness?
lawtq said:
OH I see! That looks messed up. Funtouch os? I think that'll probably be fixed with an update cause you seem to be on all the correct options.
You're using auto brightness?
Click to expand...
Click to collapse
yes auto brightness
Wish I could help, but I have the China dimensity 9000 version with no issues
asked vivo CN customer service, this is their refresh rate strategy for dark mode, so it wont be fixed, probably they have their reason behind for it
so its looks like
1) 1-120 wont work in dark mode theme
2) 1-120 wont work in low brightness
3) 10-120 work in 30%+ level
4) 1-120 work in 70% levels
If I set my refresh rate to 120hz should it stay there wherever I am or whatever I am doing woth my phone? Coz even in homescreen or using chrome it still goes down to 10.