Hi guys,
Sometime you got blur picture when using Camera even you took it with steady hand.
This is happen because gyro sensor in G2 is not working/calibrate
Here is how to check it whether is working or not
1) Go to hidden menu by dial 3845#*80X#, replace X with your phone model. This is only for models 800/801/802, etc, for other models search this forum how to enter Hidden Menu
2) Choose Device test -> Individual item -> camera OIS, put your phone and flat surface, don't move it and then click Start
3) The result should be Gyro : PASS, Hall : PASS, Driver : PASS
If you get Gyro : FAIL, then you should calibrate your sensor. Go to Settings -> General -> Gestures -> Motion sensor calibration.
After calibration, check again your camera OIS, now it should be pass all test.
htcm7 said:
Hi guys,
Sometime you got blur picture when using Camera even you took it with steady hand.
This is happen because gyro sensor in G2 is not working/calibrate
Here is how to check it whether is working or not
1) Go to hidden menu by dial 3845#*80X#, replace X with your phone model. This is only for models 800/801/802, etc, for other models search this forum how to enter Hidden Menu
2) Choose Device test -> Individual item -> camera OIS, put your phone and flat surface, don't move it and then click Start
3) The result should be Gyro : PASS, Hall : PASS, Driver : PASS
If you get Gyro : FAIL, then you should calibrate your sensor. Go to Settings -> General -> Gestures -> Motion sensor calibration.
After calibration, check again your camera OIS, know it should be pass all test.
Click to expand...
Click to collapse
when i in ois test and select start i got failed ! (invalid vendor ) ! i'm on rayglobe flex v4 !
+1
Sent from my LG-D802 using xda app-developers app
ali_ign said:
when i in ois test and select start i got failed ! (invalid vendor ) ! i'm on rayglobe flex v4 !
Click to expand...
Click to collapse
I guest flex ROM doesn't have hidden menu apk since this is not based on stock firmware.
Wow, that's a pretty cool and easy trick, worked on my side, thank you !
it did work. thanks mate!
When i enter hiden menu i choose device test and that message showed up "press ok to run aat device will be restared" i press ok and nothing happen and the message still appeared, i'm on cloudy g3 1.2.
---------- Post added at 09:01 PM ---------- Previous post was at 08:27 PM ----------
When i select device test this message showed up "press ok to run AAT device will be restarted" then it stay like that when i press ok nothing heppen till i forced it to stop,i'm on cloudy g3 1.2. D802
Related
Is there a way to calibrate the touch screen?
Thanks
d12bn said:
Is there a way to calibrate the touch screen?
Thanks
Click to expand...
Click to collapse
Menu -> Settings -> Lang&Keyboard -> Touch Input -> Text Input -> Calibration Tool
First do the "Reset Calibration" then do your own calibration is how I did it.
mrrogers1 said:
Menu -> Settings -> Lang&Keyboard -> Touch Input -> Text Input -> Calibration Tool
First do the "Reset Calibration" then do your own calibration is how I did it.
Click to expand...
Click to collapse
That's for the HTC Keyboard ONLY. THat has no effect on anything else.
And no, there is no way (or need) to calibrate the screen.
The dialog says for the tool says "Calibrate your screen for a better touch experience".
While I did not design the phone or interface, I don't know 100% either way and luckily, it can't hurt.
*If you did code the interface and know for sure, thank you. ;-)
Thanks
mrrogers1 said:
Menu -> Settings -> Lang&Keyboard -> Touch Input -> Text Input -> Calibration Tool
First do the "Reset Calibration" then do your own calibration is how I did it.
Click to expand...
Click to collapse
Thanks that's what I needed
I wish there was a way to calibrate the touch screen. Anyone else having issues where you press the top thread of SMS and it goes to the 4th one down and then it locks the screen like it's touching there so I can't press anything else? No back button, home button. Only thing that works is locking it then unlocking but sometimes you have to do that 3 to 4 times before it will stop "touching" that same spot. I haven't hard reset yet but if that doesn't work I'm going to have them replace it.
That happened to me a lot with the original evo, not as bad with this one, but it has been off a few times
What does this do? Menu > Settings > Display > G-Sensor calibration
scramer said:
What does this do? Menu > Settings > Display > G-Sensor calibration
Click to expand...
Click to collapse
Are you daft? It calibrates the G-sensor, as in the sensor that reads the G forces the phone is being exposed to.
flyingwolf said:
Are you daft? It calibrates the G-sensor, as in the sensor that reads the G forces the phone is being exposed to.
Click to expand...
Click to collapse
he he he... "daft".
I had MAJOR touch screen problems (not keyboard) and this seems to have fixed them!
Seetings > display> calibration unless thats only in the rom im using
Nevermind only an option on my rom
Sent from my PG86100 using xda premium
Nope I have the option as well. The feature is offered on most stock based roms I believe.
#Root_Hack-Mod*Always\
i am having problems using the keyboard in portrait mode.. it wont touch the p, or 0. also, it dont always catch on the sides anymore in landscape mode.. when playing games and stuff..
dgrobe2112 said:
i am having problems using the keyboard in portrait mode.. it wont touch the p, or 0. also, it dont always catch on the sides anymore in landscape mode.. when playing games and stuff..
Click to expand...
Click to collapse
It sounds like your digitizer (touchscreen interface) may be going out. Try to calibrate in the keyboard settings and then calibrate the "g" (accelerometer) sensor. If you're still having issues with p,0 put your phone in landscape mode where the home button is on top and confirm that area of the screen by pressing the comma or space bar. Good luck.
intrlude
dgrobe2112 said:
i am having problems using the keyboard in portrait mode.. it wont touch the p, or 0. also, it dont always catch on the sides anymore in landscape mode.. when playing games and stuff..
Click to expand...
Click to collapse
You might also try a Gingerbread Rom as I've noticed the accuracy to sometimes be off on ics Roms, especially near the screen edges. Or, maybe try a different keyboard.
Sent from my PG86100 using Tapatalk 2
how to calibrate keyboard on jellybean ?
i think ... calibrating touchscreen is important to....how to do that on ICS and JB ?
FXP045 released, http://forum.xda-developers.com/showpost.php?p=16822404&postcount=4
Current Issues (FXP045) and unofficial fixes
Hardware keyboard layout scrambled - Old keyboard file is no longer in this ROM but appearently just pasting the old stock file (attached) to /system/usr/keychars/ fixes the layout. The included keyboard changer app force closes.
LEDs under soft keys Return and Menu - Replace /system/etc/hw_config.sh with the attached file.
Screen flicker upon turning on - New issue in fxp045.
can this work on Ray?
the flash does not work either
and the keyboard light does not work when use (when charging, it works)
and the max brightness is not very bright
xutienan9520 said:
can this work on Ray?
the flash does not work either
and the keyboard light does not work when use (when charging, it works)
and the max brightness is not very bright
Click to expand...
Click to collapse
I believe these fixes will work on Ray but you should find the stock values from Ray ROM because there probably are some differences.
Basically, only one issue you're having can potentially be fixed using SK17i fixes and that is max brightness by applying the fix for screen flicker. If you can't get a hold of Ray's stock values, try SK17's stock ones, but do a backup in recovery just in case.
thanks～
i changed the light.semc.so in system\lib\hw from stock 2.3.3, now i have the max brightness, but the keyboard light is on for ever! i can't close it!!!!the colour is always pink!
i think i can edit the file, i am in Mac, so is there a way to edit it without linux?
xutienan9520 said:
thanks～
i changed the light.semc.so in system\lib\hw from stock 2.3.3, now i have the max brightness, but the keyboard light is on for ever! i can't close it!!!!the colour is always pink!
i think i can edit the file, i am in Mac, so is there a way to edit it without linux?
Click to expand...
Click to collapse
i'm editting these files on the phone. copy the file to sdcard to edit it, with any kind of text editor. i use edit function of Total Commander. then i copy over the original file in system with Root Explorer. backup original file to sdcard just in case.
dont know about Mac much, sorry.
root explorer is a paid app but i think ES file explorer has the required functionality
LEDs under soft keys Return and Menu on maximum brightness - distractingly bright, in almost all environments. SOLUTION posted here: http://forum.xda-developers.com/show...&postcount=178
can't open it，need help
xutienan9520 said:
LEDs under soft keys Return and Menu on maximum brightness - distractingly bright, in almost all environments. SOLUTION posted here: http://forum.xda-developers.com/show...&postcount=178
can't open it，need help
Click to expand...
Click to collapse
oh, i messed up the links. will be fixed in a moment =)
Per someones suggestion I've added modified files and instructions on how to replace the original CM ones.
yepsky!!
I found the background ligths for the keyboard
Code:
echo 100 > /sys/devices/i2c-0/0-0040/leds/keyboard-backlight/brightness
I tested 100 and found it adequate.
We just can add it to the config file in /system/etc/hw_config.sh
I do not know if it stays lit when slided back, but it works as a first atempt
PoedelPCS said:
yepsky!!
I found the background ligths for the keyboard
Code:
echo 100 > /sys/devices/i2c-
0/0-0040/leds/keyboard-backlight/brightness
I tested 100 and found it adequate.
We just can add it to the config file in /system/etc/hw_config.sh
I do not know if it stays lit when slided back, but it works as a first atempt
Click to expand...
Click to collapse
Thank you good Sir! Testing it later!
PoedelPCS said:
yepsky!!
I found the background ligths for the keyboard
Code:
echo 100 > /sys/devices/i2c-
0/0-0040/leds/keyboard-backlight/brightness
I tested 100 and found it adequate.
We just can add it to the config file in /system/etc/hw_config.sh
I do not know if it stays lit when slided back, but it works as a first atempt
Click to expand...
Click to collapse
Amazing job! I'm gonna test it out now in a super dark place to see if i can check whether it stays on when closed. =)
I'll be updating original post with results and updated files in a bit.
Edit: Unfortunately keyboard lighting stays on and not only when keyboard is closed but even when phone is locked. Which means, its lit at all times. Won't be updating the files yet, because I don't know how much of a battery drain it is, but i'll put in information about it, so people can decide for themselves.
Nice to see process.
Now i need to find the button light for RAY
sulkie said:
Unfortunately keyboard lighting stays on and not only when keyboard is closed but even when phone is locked. Which means, its lit at all times. Won't be updating the files yet, because I don't know how much of a battery drain it is, but i'll put in information about it, so people can decide for themselves.
Click to expand...
Click to collapse
I thought that
Okay, there is a binary called slidercounter that or something similar sets a system var. If you take your dev Tools app and look unter Configuration there it is mentioned:
hardKeyboardHidden=2 <- if closed
hardKeyboardHidden=1 <- if opened
We now just have to find out where it occurs and if not we make a background script that ech0 x (100) or 0 into the node depending on the state.
But there must be a system process watching this we could use.
Don't hide, I'll find you anyway
---------- Post added at 06:16 AM ---------- Previous post was at 06:14 AM ----------
xutienan9520 said:
Nice to see process.
Now i need to find the button light for RAY
Click to expand...
Click to collapse
did you look, if in ray the nodes under /sys are similar to the pro mini?
you can test using adb shell or terminal app cat'ing the node to see what's in it and echo'ing a number to see what happens.
You meant progress, didn't you
as I am using Scriptmanager anyway I made 2 oneliners besides the shebang that echo either 0 or 100 into the node called
liteon.sh
and
liteoff.sh
put the scripts into root of sdcard, start scriptmanager, choose liteon.sh and check run as root and save
Do this either way with liteoff.sh
Go to your Mangos Homescreen, add a widget, choose Script Manager and choose liteon.sh and in the next step liteoff.sh
You´ll have to Widgets, one puts light on, on off.
This is of course a workaround an will be implemented into lights module. Fxp knows about the fact already.
PoedelPCS said:
as I am using Scriptmanager anyway I made 2 oneliners besides the shebang that echo either 0 or 100 into the node called
liteon.sh
and
liteoff.sh
put the scripts into root of sdcard, start scriptmanager, choose liteon.sh and check run as root and save
Do this either way with liteoff.sh
Go to your Mangos Homescreen, add a widget, choose Script Manager and choose liteon.sh and in the next step liteoff.sh
You´ll have to Widgets, one puts light on, on off.
This is of course a workaround an will be implemented into lights module. Fxp knows about the fact already.
Click to expand...
Click to collapse
not the most elegant solution but it'll do until the fix is in =)
good job though
If I had more time I would have searched where the system keeps the var keyboardHiddenState or how it was called and build a condition of if it's open and not bright enough to switch in on/off
But how I understood fxp the fact about the light seems to be enough to get this working ..I hope so
new issue:
km launcher disturbes camera module.
I use the KM Launcher to determine which keyboard to use in which state.
Portrait: swype
Landscape: thumb keyboard
Keyboard open: hardware keyboard
This is a very cool application that worked perfectly on my rooted stock. If it is active the cam works in the cam app, but not in many other apps that use the cam, e.g. barcoo barcode scanner. I have to disable KM Launcher before using these apps. Hope it'll be fixed automatically in the next release.
I just cannot guess why that happens.
Hey guys I still have the problem with the over sensitive lcd backlight, whenever I'm in a brightly lit room the backlight starts going crazy and sometimes goes so dark I can't see the screen, it then goes super bright.
It repeats this several times a day
I've tries the fix in this thread but it doesn't work
Could someone attach the fix to this thread? As I've tried the the fix using terminal emulator
Thanks
EDIT: it started doing this while I was writing this
Sulkie did append the script to the first post of the thread. Did you test it?
send from a fruit called mango using xda app.
I did it before but it didn't work, I found the reason it didn't work was because I didnr change the permissions.
Sorry I got confused
---------- Post added at 12:51 PM ---------- Previous post was at 12:43 PM ----------
Its still going crazy, I followed the instructions properly though,
When I get home ill upload a video of it happening
So I'm using the CM11 4.4 Kitkat on my Galaxy S4 and recently found out that my proximity sensor isn't working (when I dial the screen goes black and won't turn on until the call is over). I've read many threads about fixing it but I think it's broken. So all I want now is to disable it but there isn't such option in the Cyanogenmod. Is there anyway to disable it, like with a terminal or something?
bump
bump!
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
kg2128 said:
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
Click to expand...
Click to collapse
glad someone found this useful.
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
sjschoo said:
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
Click to expand...
Click to collapse
Yeah I noticed that, the best solution is to get the proximity sensor fixed in the end. Then you don't have to disable anything. If your lucky it doesn't even need to be replaced, just cleaned. For me I can live with no rotation, because the screen off during calls is a ridiculous PITA by comparison. Also apps can force landscape mode even with the gyroscope not working. I use force landscape for videos through mx player, and mango reader for manga.
I finally broke down and took the phone apart. There were no warranty stickers to break so assuming you don't mess up royally, it shouldn't effect your resale value. All it took was an eye glass screw driver and a q-tip. Once I was inside I tried the can of air first, but didn't help. Swabbed the back of the glass with the q-tip and that finally provided lasting relief.
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
khudko83 said:
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
Click to expand...
Click to collapse
Changing the rom isn't going to do anything, even factory roms (I've tried it). If a replacement sensor doesn't fix it for you, then it's going to be hard to fix it yourself. All the posts I've seen so far have cleaned the sensor or replaced the sensor and fixed the problem. Otherwise people like me just turn the sensor off.
You were right, proximity software fix didn't help! But how is it possible to work in this (the same wrong) way with changed sensor? Can it be some main board hardware problem? But it doesn't look like this...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Maybe somebody knows how to fix the issue???
Finally fixed
Thanks so much qman66 I have had problems with my proximity sensor on my JFLTEXX pretty much since I got it. Had been using the xposed disable proximity sensor module but xposed doesn't work with CM12. Your simple system tweak has given me use of my phone know call options again
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
Hi, I tied to do this but it says I can't save the changed so file... Can you let me know which root explorer and text editor you are using?
Thanks massively
Not a text file
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I found sensors.msm8960.so with many references to proximity sensor but it is not a text file!!
Samsung S4 Active w LOS 15.1 (a&Droid 8.1) - how to disable HW sensor(s).
Hi All
Hope some here will help me stay afloat long enough to learn to surf by myself; bit of a noob in this wild ocean here (more of a 'fresh water/indoor pool' kinda dude I guess) - but trying to break out of tis little pond and learn to 'surf'. Anyway, to the point:
1. HW spec
Samsung Galaxy S4 Active
GT - i9295
TWRP 3.3.0-0
Lineage 15.1 20180227 jactivelte
(sometimes with opengapps pico and addonsu15.1 but mostly just LOS and addonsu nothing else)
2. Have the sensors on phone covered up with black electrical tape - all but the notification light are covered and it's gonna stay that way - NOT negotiable!
Obvious Issue: Have the blank screen during phone call problem. Can end calls using power button but I need to use the keypad quite often so need the screen to stay on. How? Ideally want to (SW) disable most if not all hardware sensors - how?
Tried a few fixes but no luck, e.g.:
(a) adding 'the' fix/control many sensors apk no good as not suported under 8.1 (plus want to find out how to do manually myself not use 'hand outs').
(b) edit selected sensor etc ".so" (eg in system hw) files - so far not resulting in the disabled ProximitySensor.
So, I really want to hack this myself at cmd line level, am ok with that (many years IT ops/admin experience in 'fresh water commercial space'). Can mount system using TWRP then adb shell to connect and find and grep for stuff in files but cannot find setttings I need to change to disable sensors for good. Where to look/find more info?
What do I want to achive:
Make calls and have keypad stay on all the time or give me manual option to turn screen on/off with a hw button during call.
How:
I am happy to disable pretty much all sensors (proximity, gyro, compass etc) in system or firmware memory so that I am free from the overlords and really want to be able to use the keypad during calls - and have option to manually turn screen off/on during call would be cool.
Constraint:
Really want to do this from (a) cmd line or (b) edit code/recompile (learning curve) the LOS 15.1 or whatever to disable sensors for good. I will be using this old thing mostly for just call and txt not much else - and cannot be asked to buy an old Nokia handset.
Thanks,
iHAL8999.999... (hi dave...)
Hi all,
i used this https://github.com/Domi04151309/AlwaysOn AllwaysOn app i like it! and i decide to mod a few things to work better with our OnePlus 8 Pro.
needless to say. BIG Thx to Domi04151309 for his work.
changes:
- Fingerprint on AllwaysOn. longpress and keep the Finger on screen until its unlocked
- doublepress takes you to lockscreen
- Mediainfo on Lockscreen (doubleclick for play/pause; longpress next track)
- Notificationicons are colored
based on his version 3.7 and keep in mind earlybeta
have fun
inteks
yesterday i was happy by the low batteryusage of alwayson. then i started "wizards unite" and just locked the screen. in 20min i got 4% battery lost BUT this was counted as batteryusage of alwayson !!!
it seems while alwayson is running and its the "app" in foreground. EVERTHING that runs and use battery in background is counted as batterusage of alwayson !!!
so pls dont trust the usage in batteryinfo....
ps: does NOT work together with apps like aodNotify or arc Lightning....
ps: version 2 .... found a few bug if installing first time. now it should work
sourcecode: https://github.com/int3ks/AlwaysOn/
update version beta 0.3: changelog -> https://forum.xda-developers.com/showpost.php?p=82779667&postcount=14
updated to version 0.5 (still beta) changelog -> https://forum.xda-developers.com/showpost.php?p=82794149&postcount=24
updated to 0.7 changelog -> https://forum.xda-developers.com/showpost.php?p=82811659&postcount=33
updated to 0.8 changelog -> https://forum.xda-developers.com/showpost.php?p=82822155&postcount=41
update 0.9 changelog -> https://forum.xda-developers.com/showpost.php?p=82887131&postcount=47
update 9.1:
-fixed the doubletap powerbutton start camera bug
Will this work with the Energy Ring App?
Gesendet von meinem IN2023 mit Tapatalk
Fails to install on OOS 10.5.8 EU.
Edit V2: works perfectly, wish there was an option to disable FP icon, also the position of icon is a bit off.
MarcoG: said:
Will this work with the Energy Ring App?
Gesendet von meinem IN2023 mit Tapatalk
Click to expand...
Click to collapse
pls test. but i dont think...
areyouanand said:
Fails to install on OOS 10.5.8 EU.
Click to expand...
Click to collapse
i had posted the unsigned debugapk... pls try download again.
version 2 .... found a few bug if installing first time. now it should work
I have to root the op and install riru or something? Can you make a easy guide for everyone? Thanks ?
vuoshino said:
I have to root the op and install riru or something? Can you make a easy guide for everyone? Thanks [emoji172]
Click to expand...
Click to collapse
I believe it's a magisk module
Sent from my IN2025 using Tapatalk
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
Does the fingerprint icon remain on the screen always?
Sent from my IN2025 using Tapatalk
czerdrill said:
I believe it's a magisk module
Sent from my IN2025 using Tapatalk
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
Does the fingerprint icon remain on the screen always?
Sent from my IN2025 using Tapatalk
Click to expand...
Click to collapse
just install. its an apk. but yes its better with root.
the fingerprint remains... to know where to press and hold
Gesendet von meinem IN2023 mit Tapatalk
I tried and works without root. The stuff on the screen moves sometime or not? Because if are fixed i think the burn in is easy.
Edit: i saw that there is an option to prevent it but the finger doesnt move. There is a option to unable it?
vuoshino said:
I tried and works without root. The stuff on the screen moves sometime or not? Because if are fixed i think the burn in is easy.
Edit: i saw that there is an option to prevent it but the finger doesnt move. There is a option to unable it?
Click to expand...
Click to collapse
the finger also moves! but only max 10dp... dont know how many pixel that is.
but it has to be near to the sensor to work
with root it need less battery. because of a cmd that put the phone into low power mode. this only works with root!
Gesendet von meinem IN2023 mit Tapatalk
Any chance of removing the light for finger print
c_86 said:
Any chance of removing the light for finger print
Click to expand...
Click to collapse
Or replace it with a very transparent icon and only have the actually icon pop-up when the screen is touched. Overlay a black box with the icon and when screen is touched/updated it removes the box and shows the original icon
like the others have said, i would very much like for the option to set the fingerprint icon as a transparent image , due to the image retention nature, im very leery of burn in
hi..
ok here is a new beta. changed a few things:
1. mediacontrol: to avoid unwanted input. now you have to doubletap on mediainfo to enable control. after that single tap is play/pause and swipe left or right for next/prev track
2. animation time: i changed the timeinput from 2min to 120sec. so you can test with i.e. 2 sec and see the controls moving if you worry about burnin.
3. fingerprint: you can set a alpha value from 0 to 10 ... 0 you see no fingerprint and 10 is full
4. you can enter low_power mode without root !!! you have to grant permission with adb shell ->
Code:
adb shell pm grant io.github.domi04151309.alwayson android.permission.WRITE_SECURE_SETTINGS
the is also a batchscript in "Dieser PC\IN2023\Interner gemeinsamer Speicher\Android\data\io.github.domi04151309.alwayson\files\_Always"
to explain. the original version use this
Code:
Root.shell("settings put global low_power 1")
Root.shell("dumpsys deviceidle force-idle")
to go into lowpower state
this ->
Code:
Settings.Global.putInt(this.contentResolver, "low_power", 1)
is possible without root if you grant the WRITE_SECURE_SETTINGS permission
i'll attach the new version in First post
Running good.
I don't know if it's by design. But whenever it's on I put my finger near the finger print icon (which is not in the same location as the actually reader) but it sometimes will then wake and scan my finger other times it just doesn't respond and takes for me to constantly tap on the screen to get some sort of action.
Also
It's draining battery like no tomorrow. I had it installed. Had quite a few notifications come in and didn't touch my phone for 2 hours. And I dropped 25% in battery life and was quite noticibly warm. This was with all the battery saving switches on.
c_86 said:
Also
It's draining battery like no tomorrow. I had it installed. Had quite a few notifications come in and didn't touch my phone for 2 hours. And I dropped 25% in battery life and was quite noticibly warm. This was with all the battery saving switches on.
Click to expand...
Click to collapse
i got 8% in 3 hours... witch is not so bad... maybe something else is going wrong
what settings did you change from default in alwayson ??
inteks said:
i got 8% in 3 hours... witch is not so bad... maybe something else is going wrong
what settings did you change from default in alwayson ??
Click to expand...
Click to collapse
Need to check the refresh rate, from what i have heard, it runs at 60. if this can be controlled, the battery consumption and the heating issue will be solved.
I might be completely wrong.
areyouanand said:
Need to check the refresh rate, from what i have heard, it runs at 60. if this can be controlled, the battery consumption and the heating issue will be solved.
I might be completely wrong.
Click to expand...
Click to collapse
next version will force 60hz on alwayson
adb shell settings put global oneplus_screen_refresh_rate 1
and set userselected refresh on exit
im testing at the moment. update soon
Hi there,
I am on non rooted. I have obeserved this strange behavior: If you use it in a pocket, a reminder goes on that you are in pocket mode. This reminder stays on while you are inside the pocket and causes battery drain and potential burn in. Can you check it please: Just cover the brightness sensor with your hand.
When u go to edl mode through test point, sometime battery strip from main board should be remove to do it and then connect again
When i was setting up my device again to use, i realized fingerprint not working and device speaker volume was low in all system and third party apps also, i thought i damaged something on board
But no that was not the case
When u remove battery from board or maybe when u goto edl mode through test point
Phone needs some calibrations again
I found a video how to calibrate fingerprint
Goto About phone > all specs , click on kernal version 4/5 times it will goto cit settings, click on 3 dot menu and find "fod fingerprint calibration" and follow instructions
And "calibration speaker PA" for speaker clibration
I see many complains about low volume of mi 10 on google search but found no solution, hope this will help someone