I've been looking for several days, and can't seem to find a solution. I've tried Hardware Disabler from the market. I can't figure out which driver it is, and also have seen some people complain about phones getting hot or battery drain while using it. I don't want to have to disable every time I boot.
What I'm looking for, is someone to tell me which file to edit to completely disable it from loading. This way I can continue using AOSP roms.
Right now, I am stuck on a TW rom with the sensor disabled in the dialer menu. Maybe one of you gurus can help a guy out??
Related
Hi Guys,
I am currently using a Cell Pro Rom and I find that my it keeps flipping to landscape too often when I have my phone in portrait.
I always have to give it a shake to fix itself and it does get a bit annoying.
Does anyone know how to fix this?
(I remember I may have (not certain) that I might have changed the Sensor registry when I first got it, but I am not certain, does anyone know the default measurements?)
Any ideas are welcomed.
Many thanks in advance!
Did you ask in the Cell Pro ROM thread? Seems a more logical place to ask. I tried that one out and did not have the issue you are describing. Good ROM too.
There is a G-Sensor Calibration in Settings- System.
kimtyson said:
Did you ask in the Cell Pro ROM thread? Seems a more logical place to ask. I tried that one out and did not have the issue you are describing. Good ROM too.
There is a G-Sensor Calibration in Settings- System.
Click to expand...
Click to collapse
I'm fearing the fact that I may have changed something in the registery as I got all excited the day i got the phone and went through the tweaks in the wiki.
I am not certain if I made any changes regarding the g sensor so I was wondering if anyone knows the defaults or if there is a .cab or ROM to flash to system restore.
Any clues?
Many thanks in advance
To me the g-sensor is a gimmick. I find it annoying and totally useless so I've turned mine off altogether. If I want the screen to rotate I push the keyboard out. I really don't see any use for it.
I did think the only use I had for it was the face down hands free thing but have since decided that I'd be quite happy to push a button for that. Hardly a hassle.
I've been using the "DK Custom Froyo V4.5.2" ROm for a while now, and it's been behaving quite well. But I just made a call and when it was over the display just stayed black, it has happened a few times before. It's quite annoying since the only solution seems to be to rip out the battery and put it in again.
I'm not sure it's the ROM that's causing this, in fact I don't think it is, but you never know. So wondering if anyone else have experienced this with the wildfire and have a solution for it. I'd rather stay with the current ROm but if a change to another one would fix this problem I'm willing to try it. But I rather stay with a "Older" ROM, just for thefact that wildfire isn't the most powerful mobile out there and I imagine it's more suited and can perform better with a little older ROM.
Greatful for any help.
EDIT: Just found this topic:
http://forum.xda-developers.com/showthread.php?t=921103
Can that be it? I do have a "rubber protection" on it.
http://forum.xda-developers.com/showthread.php?t=674847
Seems like it indeed is the cover that causes it.
Mods can remove this if they like, maybe I shouldn't post it when I have already found the answer but it's been bugging me for a while and maybe someone else will find it useful.
I've seen a similar post to this way back in the day when I first rooted my phone, but since then have been unable to relocate said post, so I'll just post here as I've noticed this to be a constant problem, perhaps GB related.
Days where I don't make any phone calls I get decent battery life, about 1% every 2 hours and that's listening to music. But god forbid I have to make a phone call because then Dialer remains on consuming my sensor in spare parts. I've disabled just about everything in call settings related to sensors and even tried turning my BT on as I read it might fix it, no dice. The only way to fix atm is to restart or perform a hot reboot.
Anybody else experiencing this or have found a fix? Currently running Decks 1.3d and thinking of going back to a Sense rom cuz I never dealt with this crap before I tried AOSP, even though I love and prefer AOSP over Sense.
Naturesretard said:
I've seen a similar post to this way back in the day when I first rooted my phone, but since then have been unable to relocate said post, so I'll just post here as I've noticed this to be a constant problem, perhaps GB related.
Days where I don't make any phone calls I get decent battery life, about 1% every 2 hours and that's listening to music. But god forbid I have to make a phone call because then Dialer remains on consuming my sensor in spare parts. I've disabled just about everything in call settings related to sensors and even tried turning my BT on as I read it might fix it, no dice. The only way to fix atm is to restart or perform a hot reboot.
Anybody else experiencing this or have found a fix? Currently running Decks 1.3d and thinking of going back to a Sense rom cuz I never dealt with this crap before I tried AOSP, even though I love and prefer AOSP over Sense.
Click to expand...
Click to collapse
I would look for the topic about wake lock, there is a possible fix in there if I remember right. Also could try to reflash decks, I've never had a problem.
Sent from my PC36100 using xda premium
I agree with the guy above me, you should check the thread of whatever ROM your using as well, and for a quick fix you could always just push the Power/Screen Lock button
http://forum.xda-developers.com/showthread.php?p=14814224
Sent from my PC36100 using xda premium
Hi guys
I know this question has come up quite a few times, but i have just spend the last hour searching all the threads and not really come up with any results. Does anyone know how to get rid of the black screen during/after call issue? I have tried adding ro.lge.proximity.delay=25 and mot.proximity.delay=25 to build.prop but this does not get rid of the issue properly. There is only ever been 1 rom that i have used that managed to get rid of this problem, but they wont tell me how they did it and i cant fidure it out lol. Anyone?
thanks
brezzz
I'm not 100% certain what causes it, there seem to be various reasons. I found it was cured by ram management, something like the supercharger script and/or a cache cleaner resolved it. Most, if not all, custom roms don't have the problem due to being stripped of bloatware.
ah ok, everytime i used v6 it seemed to cause problems, just seems weird that it only causes problems when in-call. SE-Tweaked is the only rom that seemed to completely fix the problem but it seems weird that some roms only do it now and again. I used to think its was proximity sensor that caused the problem but it seems worse in sunlight so maybe light sensor?
There's a few things that can cause it, sometimes grease on the sensor or a cover. The fix you used works, but I found it was more like the phone hanging on the call process. Tried increased cpu frequency during call and even an app on the market, but decent ram management does the trick.
sinkster©
brilliant, thanks for your help buddy
Hi, Which ROM has the problem solved. I would like to try this, please name the ROM. Thanks
Getting a weird overheating message on the stock 4.4.2 rom (XWDNF1)
It basically says 'your device is overheating some apps will be closed'.
Then it may pop up again and say 'X amount of apps were closed you can only use the phone and contacts'.
The warning is bogus though as I can feel the device to the touch and tell it's not overheating. Even if it was, I don't want my rom making the decision to stop on it's on.
Does anyone know how to deactivate this warning?
I'm using the: Stock Samsung rom, Rooted with a Stock Kernel.
Here is a screenshot, I'd appreciate any insight. I figure this is a stock kernel "safety" thing. But, is there a way to disable it? Do I just need to use a different kernel?
apollostees said:
Here is a screenshot, I'd appreciate any insight. I figure this is a stock kernel "safety" thing. But, is there a way to disable it? Do I just need to use a different kernel?
Click to expand...
Click to collapse
This happened to me on civato's custom rom/kernel once as well. Not sure how to disable it. Probably baked into the kernel code somewhere. I only got the message that one time so have not really been concerned with it. Was not the same message though because it didn't close any apps automatically or make me do anything. I shut it down for a bit and restarted at later time. My tablet was not hot either as all I was doing was browsing with Dolphin.