Patch Request: Disable Proximity Sensor - Samsung Galaxy Mini

Is anyone able to disable the "gp2a - proximity/light sensor" from within "sensors.default.so" and/or "sensors.goldfish.so" so that people suffering from White Screen bug don't get white screen when answering or making a phone call. This is in regards to CM11 port by TheWhisp.
I tried using app "Hardware Disabler" to disable the driver which worked however it also crippled the phones processing speed and was too slow to be usable.
Would greatly be appreciated if someone could upload/attach the modified file/s

Related

[APP]Touch InCall Screen Tweak v1.2.0 - Updated 3 Sep 09 - Battery Drain Fix

Welcome to the Touch InCall Screen Tweak thread. This app is a collaboration between 600GOL (of changeScreen fame) and Steve Pritchard (of the lesser StartTomTom fame).
Release notes are in the second post.
What does it do?
The purpose of the application is to switch on your screen during a call if you don't have it against your ear. This is useful if you need to enter digits for voicemail or telephone banking, etc. The screen will be switched off if the phone is against your ear (since v1.0.10 this will include as you a making a call, as well as during the call). From v1.0.11 if you put the phone face down, it will switch off the screen, and turn on the Speakerphone (from v1.0.19 this is now an option).
How does it work?
The application, once installed, doesn't actually run until you make or receive a call, so it won't impact normal performance of the phone. When you are in a call, the application runs, and monitors the orientation of the phone, and will switch the screen on if the phone has been in your hand for around half a second or so. If you put the screen against your ear, the screen will go off again. You can repeat this cycle as many times as you like.
So it doesn't use the light sensor then?
From v1.0.6 it DOES use the light sense to detect if it is against your ear. This is really a double check to back up the orientation. It doesn't use it to determine if it's away from your ear because the sensor doesn't seem to work when the screen is off, so it's of no use for switching the screen back on.
Will it work with my Phone?
This app is only compatible with Windows Mobile based HTC phones. It is developed and tested on a HTC Touch Pro, but should function on Touch Diamond and Touch HD models, although it looks as though non-TP models don't use their light sensors during a call, so Diamond and HD owners might want to disable the use of the sensor using the config app. It is not compatible with Android based phones, e.g. HTC Hero, or with Samsung phones, including the Omnia i900.
You can install the application from the attached cab file. You need to soft reset after installation for the application to work.
The second post in this thread will contain release information. Please resist the urge to tell everybody that you are downloading and trying the software by posting to this thread. By all means let us know if it works for you, along with what ROM you are using, and obviously let us know if you have any problems.
Cheers,
600GOL and Steve.
If you would like to consider making a donation, it is by no means necessary, but it is appreciated.
Many thanks to Hilaireg who has taken the time to provide a user manual, and Kitchen packages for TICST.
The files available for download:
- TICST Manual v1.1.3.pdf.zip - User Manual
- Touch_InCall_Screen_Tweak v1.2.0.CAB - Regular installation CAB
- Touch_InCall_Screen_Tweak v1.2.0 with UC.CAB - CAB for inclusion in UC startup installations
- Marzens_TouchInCallScreenTweak_1_2_0_0.zip - Visual Kitchen OEM Package
- PACKAGE_Marzens_TouchInCallScreenTweak_1_2_0_0.zip - Legacy Kitchen OEM Package
[size=+1]Release Notes[/size]
The logging option is provided for people who find they have problems with odd behaviour. The log file will be written to the Touch_InCall_Screen_Tweak.txt in the root of your device. It will get pretty big, pretty quick so if you make/receive lots of calls the best idea might be to switch it on for a short while, use the phone, make a copy of the log file to upload to this thread, and then switch it off if you are filling up your storage space.
3 Sep 2009 - v1.2.0 - Bugfix Update
- This version addresses a bug that has been around for a while, but has been difficult to track down. It appears that an early beta introduced an excessive battery drain for some users, and this has now been tracked down, and addressed.
6 Aug 2009 - v1.1.3 - Update
It's been a while, but this minor update has the following changes:
- Fixes a bug with the "switch off after Bluetooth" call function.
- Fixes a bug which caused the left soft key to be pressed at the end of a call.
- The "switch off for Bluetooth", and "switch off after Bluetooth" facilities (which switch the screen off during, and after a bluetooth headset based call respectively) are now applicable to wired headset calls too.
31 May 2009 - v1.1.2 - Update
This version includes an option to turn off the AutoDeviceLock during a call, as described in this post, for better compatibility with SPB Mobile Shell 3.
21 May 2009 - v1.1.1 - Update
This version fixes a bug with the "Ignore first screen off" function. This bug is most noticeable in the situation where the phone canvas/utility/whatever turns the screen off before TICST gets the chance to. This version has been tested with PhonEx from IconSoft, and works as long as you switch ON the screen off during conversation facility.
17 May 2009 - v1.1.0 - Update
This version provides a number of new features:
- It will allow the switching between APM and non-APM (Advanced Power Management) mode via the config application. Non-APM will give the better experience, but you may find that your battery runs down quicker in this mode. If the option is greyed out, then you are already running in Non-APM mode, and you can't change it.
- An option to prevent the auto-unlock has been added
- The option to switch the screen off after a Bluetooth call has been added.
- The "Show phone at screen on" option has been changed slightly in that it will attempt to activate the existing instance of cprog.exe, rather than spawning a new one. This will hopefully help some people who were having problems with different dialers - most people won't notice any difference.
- Minor logic alteration to try and prevent too much "flashing" of the screen in some circumstances.
16 Apr 2009 - v1.0.20 - Update
This version provides a couple of new features:
- If the screen is locked with the WM Lock when the app switches the screen on, it will attempt to automatically unlock it.
- The app goes into an override mode if the speakerphone is switched on manually, or if the call type is a video call. NB. This is not the same override mode as if the screen is switched on/off manually, and the override timeout isn't applicable.
8 Apr 2009 - v1.0.19 - Update
This version provides a number of new features:
- More configuration for the use of the Speakerphone. You can define whether putting the phone face down should switch it on, and what action, if any, the phone should take with the Speakerphone when you have it in your hand, i.e. switch it on, off, or take no action.
- The ability to show the phone canvas has an extra option of auto-pressing the left soft key, which should put it into dialpad mode.
- You can define a timeout, in minutes, for the override mode. This option hasn't been tested thoroughly, so feedback would be useful.
7 Apr 2009 - v1.0.18 - Update
This version adds the facility to force the phone canvas to be displayed when the screen switches on. This could be useful if you find that when the screen switches on, you are back at your Today screen.
6 Apr 2009 - v1.0.17 - Includes UC Friendly installer
This version adds the facility to always switch off the screen when you are taking a call via bluetooth.
There is also a UC Friendly installer which doesn't run the config app, or give the option to soft reset after installation. However, please be aware that you will still need to soft reset after the app is installed in order for TICST to function correctly.
2 Apr 2009 - v1.0.16 - AppToDate release
There is no change to the application itself, but the installation now supports AppToDate. Also, the config utility will now try and detect the phone type, and select suitable defaults with regard to ignoring the light sensor, and the first screen-off.
2 Apr 2009 - v1.0.15 (beta) - Consolidated Release
Another Minor release - this version handles sensors that give readings greater than expect more sympathetically. In the past, if a sensor produced a reading higher than expected, it could be misread. This has been corrected. The "Always On" feature has been added. This will keep your screen on all the time, regardless of orientation.
24 Mar 2009 - v1.0.14 (beta) - Consolidated Release
Minor release - this version fixes a bug which stopped the speakerphone from being switched back on. Polling frequency has been increased from 4 to 5 times per second.
21 Mar 2009 - v1.0.13 (beta) - Consolidated Release
Minor release - this version loosens the definition of "face down" for switching the speakerphone on. People having problems getting the speakerphone to come on, should try this version.
21 Mar 2009 - v1.0.12 (beta) - Consolidated Release
This release adds the option to switch the speakerphone off once you put the phone into the "in your hand" position, i.e. when the screen comes back on again. The option is "Switch speakerphone off" in the config utility.
Bug Fix - This version should no longer switch the screen off if making a data connection.
20 Mar 2009 - v1.0.11 (beta) - Consolidated Release
This release adds functionality to switch the screen off, and speakerphone on if you put the phone face down on a flat surface.
[Earlier version release notes have been removed due to post size]
Wow, thanks for the APP! Will have to try this one
Works Great!
Installed on Sprint TouchPro Stock ROM, works great.
maybe in future releases you can make a toggle switch or a small program to enable or disable it
thanks
I'll test when I get home from work.
Thanks
Installing right now.
Hi -- works great so far! Thanks for this, I know people have been asking for this for some time. I found it works best if you sort of "flick" the phone when you bring it down from your ear to turn the screen back on. It turns on very quickly and responds quite well. So far, in just a few minutes of testing, I really like it. Great job and thank you !!
installed..testing..
doesnt work on eneryrom 2.0
http://forum.xda-developers.com/showthread.php?t=481402
tested it...love it...gave a shoutout: http://www.fuzemobility.com/in-call-screen-timeout-solved-really/
great work guys
Not working for me. Screen still turns off immediately using NATF's 4.2
D3TH METAL said:
Not working for me. Screen still turns off immediately using NATF's 4.2
Click to expand...
Click to collapse
Did you soft reset?
D3TH METAL said:
Not working for me. Screen still turns off immediately using NATF's 4.2
Click to expand...
Click to collapse
same here. screen stays off. i shake the **** out of the phone..nothing
aonavy said:
same here. screen stays off. i shake the **** out of the phone..nothing
Click to expand...
Click to collapse
What ROM are you using? It's just a question of orientation... I just installed it on a Touch HD (stock ROM) and it worked there as well...change the screen orientation and you change he backlight as advertised.
bugsykoosh: I would guess he is using energyrom 2.0
aonavy said:
doesnt work on eneryrom 2.0
http://forum.xda-developers.com/showthread.php?t=481402
Click to expand...
Click to collapse
Edit: Just for the record I am using the same rom on my fuze and my screen still turns off during a call. I installed the cab to the main memory and rebooted when it wanted me to.
Goatmaster said:
bugsykoosh: I would guess he is using energyrom 2.0
Click to expand...
Click to collapse
aahhh- reading...interesting
D3TH METAL said:
Not working for me. Screen still turns off immediately using NATF's 4.2
Click to expand...
Click to collapse
It works! Just wasn't angling the phone right....It's still not perfect but it works
If I move the phone away from my head, it will flash on/off real quick sometimes, Also their is a bit of lag between the on/off function as well.
bugsykoosh said:
tested it...love it...gave a shoutout: http://www.fuzemobility.com/in-call-screen-timeout-solved-really/
great work guys
Click to expand...
Click to collapse
I love your site! Excellent gossip site for us Fuzers!
bugsykoosh said:
What ROM are you using? It's just a question of orientation... I just installed it on a Touch HD (stock ROM) and it worked there as well...change the screen orientation and you change he backlight as advertised.
Click to expand...
Click to collapse
its in my sig.
D3TH METAL said:
I love your site! Excellent gossip site for us Fuzers!
Click to expand...
Click to collapse
Thanks - it's like an AA meeting but instead you just get to come in and keep drinking

[Q] CM7s 'CM Extra' as stand-alone app? Auto Brightness with Milestone/Froyo

Hi!
I'm new in this Forum and want to thank all you for your helpful posts!
I searched a lot, but I didn't find any solution for this problem (which seems to irritate also other users):
After upgrading to Android 2.2.1, 'Auto Brightness' does not work anymore. The problem is, that the Display gets brighter in the sun, but it does not reduce brightness in shade - which is very battery intense and irritating while driving in tunnels.
What I did so far:
+ checked and unchecked the 'Auto Brightness' setting many times ;-)
+ used widgets like 'extended controls' in the hope their settings will overwrite the problematic system-settings
+ was searching for the app "Auto Brightness" (SIMMO Publications) - which might be able to overwrite system settings. But downloading this app is not available for me (maybe because of country restrictions)
+ I rooted the phone - also for other reasons. With root I hope I can also reduce the minimum brightness level of 'Auto Brightness', which would be helpful using it as an alarmclock next to the bed.
Does anybody have an idea?
Best wishes from Austria!
No ideas to the Auto-Brightness Problem? People from Android-Pit-Forum didn't find a solution. So I changed to the forum with the best reputation ....XDA.. ;-)
It seems, that the light-sensor works well... because the button-light goes on and off according to the surrounding light intensity ...
Any idea or hint?
that's not a bug, that's a feature!
anyway - CM7 has the option just like you ask for - auto adjusting brightness to lower setting. there are also hysteresis options so you can prevent the brigtness going up and down all the time.
MuF123 said:
that's not a bug, that's a feature!
anyway - CM7 has the option just like you ask for - auto adjusting brightness to lower setting. there are also hysteresis options so you can prevent the brigtness going up and down all the time.
Click to expand...
Click to collapse
Thanx MuF123 for your answer!
This feature sounds great ... but I feel not ready to install CM7. All in all I am happy with my system right now. I learnded in the last two Android-years, that big changes for solving small problems can cause even more problems and time-intense problem solving actions... especially for me as a beginner.
So, does anybody know about a root-app or a module (eg. out of CM7) just for solving this auto brightness bug/feature ;-) ?
It would be very helpfull for me and others ...
this feature is in
Settings > CM Extra > Display > Automatic backlight > "Allow light decrease"
I wanted to tell you just so you can ask someone else about this exact feature, maybe the "CM Extra" can be installed as stand-alone app? Dunno, try to ask in CM7 thread.
MuF123 said:
this feature is in
Settings > CM Extra > Display > Automatic backlight > "Allow light decrease"
I wanted to tell you just so you can ask someone else about this exact feature, maybe the "CM Extra" can be installed as stand-alone app? Dunno, try to ask in CM7 thread.
Click to expand...
Click to collapse
Yes! This could be a possibility ... I will try!
Sent from my Milestone using XDA App
Hi!
Unfortunately I am not allowed to post into the developement-forum...
Senior User 'MuF123' informed me, that CM7 has this feature, which I miss a lot (Settings > CM Extra > Display > Automatic backlight > "Allow light decrease").
My questions:
Can the app "CM Extra" be installed as stand-alone app in my rooted Milestone with Froyo 2.2.1?
Or is there another solution for me?
Not possible. Its integrated to the framework.
Sent from my Milestone using Tapatalk
Thanx for the fast response!
Any idea what could help me?
Ronald W said:
Thanx for the fast response!
Any idea what could help me?
Click to expand...
Click to collapse
You mentioned an app "Auto Brightness" (SIMMO Publications) before. try to download that app after faking your network using "marketenabler" from market.
just my 2 cents
You can try the widgetsoid app from market.
Great idea!
Thanx. First I have to reanimate my milestone ... I killed it with deinstalling all Launchers ... stupidity pure
sileshn said:
You can try the widgetsoid app from market.
Click to expand...
Click to collapse
I tested widgetsoid ... but it didn't work.
The app "Auto Brightness" (SIMMO Publications) is not in the market any more ...
... hmm any ideas, how to solve this problem? See my starting post below...
Best wishes
Ronald
I searched a lot, but I didn't find any solution for this problem (which seems to irritate also other users):
After upgrading to Android 2.2.1, 'Auto Brightness' does not work anymore. The problem is, that the Display gets brighter in the sun, but it does not reduce brightness in shade - which is very battery intense and irritating while driving in tunnels.
What I did so far:
+ checked and unchecked the 'Auto Brightness' setting many times ;-)
+ used widgets like 'extended controls' in the hope their settings will overwrite the problematic system-settings
+ was searching for the app "Auto Brightness" (SIMMO Publications) - which might be able to overwrite system settings. But downloading this app is not available for me (maybe because of country restrictions)
+ I rooted the phone - also for other reasons. With root I hope I can also reduce the minimum brightness level of 'Auto Brightness', which would be helpful using it as an alarmclock next to the bed.
Does anybody have an idea?

HTC Sensation XL Black screen during calls [SOLVED]

Hey SXL-Users,
for all they have a black screen during calls, because the proximity sensor seems to be covered. (e.g. roms based on cyanogenmod)
I solved this by the app "Proximity Sensor Finder" (you find it in app store) in which I set the "proximitiy value when covered" at 0.0
Now I can display switch on/off with the power button ! Finaly! I can end a call by myself!
I hope it helps someone else
... In addition, no, the hardware is not broken! The light sensor and proximity sensor are reversed through the custom ROM.
FORGET THE FIRST POST!!!
The solution was this app !! A description can be found in YouTube at:
"Disable proximity sensor on android" by tech 4tress
I can't post a link. Maybe an other one can link the Video.

videos pulsing problem

Just got my mi A2 - love it. but noticing big issues with regular video recording - I am seeing this pulse or pop often once per second - a pulsing on all my videos - not sure if it is the auto focus or what. It is a regular endless pulsing on all videos where slow closeups show it the best. Looks like a defect and I would return. Or suggestions of how to fix?
See videos of what it looks like:
https://photos.app.goo.gl/iEqVUjq6jNt2zUjk6
https://photos.app.goo.gl/aSp9jBFoB7vmEd368
is there a setting that can help here - or is it a defect. ( bad autofocus)
anyone seen this problem - should I return it?
steveblue said:
Just got my mi A2 - love it. but noticing big issues with regular video recording - I am seeing this pulse or pop often once per second - a pulsing on all my videos - not sure if it is the auto focus or what. It is a regular endless pulsing on all videos where slow closeups show it the best. Looks like a defect and I would return. Or suggestions of how to fix?
See videos of what it looks like:
https://photos.app.goo.gl/iEqVUjq6jNt2zUjk6
https://photos.app.goo.gl/aSp9jBFoB7vmEd368
is there a setting that can help here - or is it a defect. ( bad autofocus)
Click to expand...
Click to collapse
Looks like a problem with either the cameras or the software. I'd probably RMA it.
I have the same Problem.
I have the same problem. It's an issue with the autofocus. It's searching for something to focus on and it does that. It can probably be fixed with a software update.
Does everyone have this problem - or just a bunch of us? Is there a way to force the autofocus to turn off for certain shots? This is a deal breaker for me as I do allot of closeup work with nature.
steveblue said:
Does everyone have this problem - or just a bunch of us? Is there a way to force the autofocus to turn off for certain shots? This is a deal breaker for me as I do allot of closeup work with nature.
Click to expand...
Click to collapse
I'm hoping the October update fixes it.
Can anyone using a camera mod - like gcam, let us know if there same autofocus pulsing happens on those apps?
-steve
In bright daylight i dont have this pulsing Problem.
But in Darkness with synthetic Lights on it happens.
gcam, same Problem. You need an Videoapp with "Autofocus Lock"
Same issue here with low light indoor shoots.
did the new update fix this issue ( raining here - hard to test) - or does anyone know of a autofocus lock app or technique to get around it.
steveblue said:
did the new update fix this issue ( raining here - hard to test) - or does anyone know of a autofocus lock app or technique to get around it.
Click to expand...
Click to collapse
I use the "open camera" app, which is free and lets you block the focus.
I have the latest October patch (2nd) and encountering the pulse problem using the native cam app. Using the Open Camera app I am not seeing the pulse issue.
Hi, same problem ..... very bad for video recording, issue or solution ? sorry for my english, i'm french
cabe_porsho said:
I use the "open camera" app, which is free and lets you block the focus.
Click to expand...
Click to collapse
how do you block focus on open camera - do not see option. am i missing it.
yes - open camera app - does work. in that it has a focus lock. How do we let Xiaomi know about this problem it it can be fixed (is there a offical way)?
open camera app
I did find how to do it: (https://opencamera.sourceforge.io/help.html)
Focus - Controls the focusing method used. Available options depend on your device. These may include:
Continuous focus iconContinuous (default) - The camera focuses continuously. This is generally the best mode - the preview will usually always be in focus, and taking photos is quick when the preview is already in focus. Note that you can still manually focus by touching the screen.
Auto focus iconAuto - The camera focuses when you take a photo, or when you touch to focus.
Infinity focus iconInfinity - The camera focus will be fixed for objects far away.
Macro focus iconMacro - This behaves similarly to auto focus, but is optimised for close-up objects.
Locked focus iconLocked - The camera does not focus, unless you manually touch to focus.
Manual focus iconManual - A slider appears allowing you to manually control the focus distance (only available if Camera2 API is used).
Fixed focus iconFixed - The focus remains fixed.
Fixed focus iconEDOF - Extended depth of field (EDOF). Focusing is done digitally and continuously.
Is there anyone who can confirm that issue has solved with android pie, or not.
Isue with video pulsing isn't solved with pie update. I have also made wipe data/factory reset after pie update but problem stil exist.
You can lock focus on stock camera app by holding on any spot of the screen

Question thinking about making a rear screen app

i don't want to have to change the fingerprint anytime i want to mirror the rear screen.
I've been researching and i have a theory there might be a way to override the subscreen but i don't know which service or app causes the screen to be pitch black when com.xiaomi.misubscreenui is killed.
I'm trying to make an app which suspends xiaomi's rear screen implementation whenever an app on a whitelist is detected to be in the forefront and vice versa.
if anybody can help me with where to go, it'd be greatly appreciated.

Categories

Resources