[Q] How to fix proximity sensor in custom roms? - Moto G Q&A, Help & Troubleshooting

Hello, I have a XT1033 and since I have flashed a lot of custom roms, and no one had proximity sensor working. Is there a fix or something?
And sorry for my english.

thelegendofzeth said:
Hello, I have a XT1033 and since I have flashed a lot of custom roms, and no one had proximity sensor working. Is there a fix or something?
And sorry for my english.
Click to expand...
Click to collapse
Hi, I'm using tillaz's infusion b2 and the proximity sensor seems fine if a bit sensitive. It is on the right hand side at the top of screen (I think it was left on my last phone so that slightly confused me)
Does it not work at all or just not as you'd like? I haven't used them but infusion has an option in settings to tweak the delay - there must be other tools to do this (in build prop I think) if you don't want to use that Rom.

sjgcooper said:
Hi, I'm using tillaz's infusion b2 and the proximity sensor seems fine if a bit sensitive. It is on the right hand side at the top of screen (I think it was left on my last phone so that slightly confused me)
Does it not work at all or just not as you'd like? I haven't used them but infusion has an option in settings to tweak the delay - there must be other tools to do this (in build prop I think) if you don't want to use that Rom.
Click to expand...
Click to collapse
Does not work at all. I've been using DynamicNotifications as lockscreen in stock 4.4.2 but in any custom rom it turns off the phone and I have to hard reset it and uninstall the app. Haven't tried Infusion but I really want it working in PA.

Nobody that can help?

No one??

Related

Horizontal calibration no longer works, help desired!

I am running Doc's rom, based on the I9000 2.2 rom
One day I noticed I could no longer rotate my phone, then I went to check horizontal calibration the phone always appears to be centered. I think the accelerometer is no longer working.
I am really unsure as to how to go about fixing this. Never dealt with this problem.
I tried searching the ROM's thread and wasn't able to find much, I greatly appreciate any help that can be offered.
picklesnickles said:
I am running Doc's rom, based on the I9000 2.2 rom
One day I noticed I could no longer rotate my phone, then I went to check horizontal calibration the phone always appears to be centered. I think the accelerometer is no longer working.
I am really unsure as to how to go about fixing this. Never dealt with this problem.
I tried searching the ROM's thread and wasn't able to find much, I greatly appreciate any help that can be offered.
Click to expand...
Click to collapse
to check to see if your accelerometer is working or not... go to phone type *#0*#
then go to sensor and you should have some kind of readings there if it is working
bulletproof1013 said:
to check to see if your accelerometer is working or not... go to phone type *#0*#
then go to sensor and you should have some kind of readings there if it is working
Click to expand...
Click to collapse
what does it mean when the Z axis on the *#0*# in accelerometer section doesn't really change with motion?
is this a hardware or a software issue?
Have you tried flashing back to stock?
assonance 5.2
ninjuh said:
Have you tried flashing back to stock?
assonance 5.2
Click to expand...
Click to collapse
I had this even on stock. The accelerometer is crazy, I can't seem to get a stable correct calibration of it.

so many issues?

im currently using the latest ordroid ROM and have a few issues that i also faced in other roms. is this something hardware related? are there any fixes? im new to the sensation so maybe im missing something?
camera completely kills phone requiring a battery pull
capacitive button lights don't always turn on or stay on
Proximity sensor doesn't work, screen remains on during calls, UNLESS if i restart my phone in a dark room
the light sensor is kind of weak (autobrightness doesnt adjust properly)
its mostly just light and proximity sensor issues, not really sure how to fix them.. any help?
DonDizzurp said:
im currently using the latest ordroid ROM and have a few issues that i also faced in other roms. is this something hardware related? are there any fixes? im new to the sensation so maybe im missing something?
camera completely kills phone requiring a battery pull
capacitive button lights don't always turn on or stay on
Proximity sensor doesn't work, screen remains on during calls, UNLESS if i restart my phone in a dark room
the light sensor is kind of weak (autobrightness doesnt adjust properly)
its mostly just light and proximity sensor issues, not really sure how to fix them.. any help?
Click to expand...
Click to collapse
Based on your signature, you're running OrDroid 7.1.0 .
At this point in time (IMHO) the Sense 4.0 ROMs just aren't mature enough to warrant using them as a daily driver. There's a lot of bugs that remain to be fixed or even discovered.
Remember, the Sense 4.0 ROMs are not originally made for our devices - they are a port from another device.
Probably best to stick with Sense 3.6 based ROMs.
OH, its because of sense 4.0? probably something kernel related im assuming?
yea our official ICS came with sense 3.6 but 4.0 is sooooo slick
well, at least i know its nothing wrong with my phones hardware .. ill try a 3.6 rom and see if i get the same issues. thanks
DonDizzurp said:
OH, its because of sense 4.0? probably something kernel related im assuming?
yea our official ICS came with sense 3.6 but 4.0 is sooooo slick
well, at least i know its nothing wrong with my phones hardware .. ill try a 3.6 rom and see if i get the same issues. thanks
Click to expand...
Click to collapse
Yes, I agree, it DOES look slick LOL! It's not Sense 4.0, but rather, the ROMs based on Sense 4.0. Again, they are ports from over devices - once all the kinks get ironed out they are going to kick butt! But for now, they are very young and "not quite ready for prime time".
JWhipple said:
Yes, I agree, it DOES look slick LOL! It's not Sense 4.0, but rather, the ROMs based on Sense 4.0. Again, they are ports from over devices - once all the kinks get ironed out they are going to kick butt! But for now, they are very young and "not quite ready for prime time".
Click to expand...
Click to collapse
ok, thanks
its all good, the devs here at XDA will figure things out in no time
DonDizzurp said:
im currently using the latest ordroid ROM and have a few issues that i also faced in other roms. is this something hardware related? are there any fixes? im new to the sensation so maybe im missing something?
camera completely kills phone requiring a battery pull
capacitive button lights don't always turn on or stay on
Proximity sensor doesn't work, screen remains on during calls, UNLESS if i restart my phone in a dark room
the light sensor is kind of weak (autobrightness doesnt adjust properly)
its mostly just light and proximity sensor issues, not really sure how to fix them.. any help?
Click to expand...
Click to collapse
There is workaround for that.
Camera : Turn off face detection in camera settings, your camera will fly.
Capacitive Button : It's related usually with Kernel. Read Changelog of the kernel you have to see if there is a workaround.
Proximity Sensor is working correctly if you untick Automatic Brightness.
That should fix some of your problems. You can have a look at this thread too.
Lucky Thirteen said:
There is workaround for that.
Camera : Turn off face detection in camera settings, your camera will fly.
Capacitive Button : It's related usually with Kernel. Read Changelog of the kernel you have to see if there is a workaround.
Proximity Sensor is working correctly if you untick Automatic Brightness.
That should fix some of your problems. You can have a look at this thread too.
Click to expand...
Click to collapse
hmm, okay ill look into that..
auto brightness doesnt even work for me, and because of that.. the capacitive touch buttons dont light up (since they cant detect if its dark enough to be lit)
it worked on stock rom, and i went straight from stock to sense 4.0 without missing a beat im gonna try arhd sense 3.6 to see if these issues are nonexistent with sensation base roms
the proxy sensor works... when it wants to..
it seems this issue remains with sense 3.6 based ROMs

[Q] [A510] Screen Responsiveness Bug?

I got my A510 a couple of days ago and I'm experiencing screen responsiveness issues at certain scenarios...
The tablet will not respond to touch when laid on a table or in bed. But once you hold the back with your hand (Or even with just a finger), the sensitivity goes back to normal.
I'm confirming that toggling the sensitivity does indeed fix it (as I saw in another forum). However, you will need to toggle it again after a restart (Or sometimes while in use, it happened to me once when I enable/disabled by BT). I have a generic screen protector installed.
My question is... Is anyone else experiencing this? Or does anyone have a permanent fix?
Common issue, no permanent fix per say, if you searched you would most likely find that you can go to settings, switch your sensitivity o either high or low, switch it back to the original and that will reset your screens touch settings, which will last until you rat your tablet. Hope that helps
Sent from my A700 using XDA
Screwedupsmitty said:
Common issue, no permanent fix per say, if you searched you would most likely find that you can go to settings, switch your sensitivity o either high or low, switch it back to the original and that will reset your screens touch settings, which will last until you rat your tablet. Hope that helps
Sent from my A700 using XDA
Click to expand...
Click to collapse
Yeah, I did search. I just thought that there's maybe a fix that I missed. Thanks bud!
Screwedupsmitty said:
Common issue, no permanent fix per say, if you searched you would most likely find that you can go to settings, switch your sensitivity o either high or low, switch it back to the original and that will reset your screens touch settings, which will last until you rat your tablet. Hope that helps
Sent from my A700 using XDA
Click to expand...
Click to collapse
Reboot you mean? Ratting out a tablet, that could make you an unpopular person in tablet jail
would this be fix if CM9 is ported ?
do you think it's linked to some Acer bloat or badly implemented ICS ?
BENETNATH said:
would this be fix if CM9 is ported ?
do you think it's linked to some Acer bloat or badly implemented ICS ?
Click to expand...
Click to collapse
It's definitely a software issue.
So yes, I think an update from Acer, or any ROM would fix it. CM9 should also be able to fix it, if and when it will be released.
as we have got the kernel sources,
is CM9 possible to be build ?
noob question but i don't know what is required to build CM9..
BENETNATH said:
as we have got the kernel sources,
is CM9 possible to be build ?
noob question but i don't know what is required to build CM9..
Click to expand...
Click to collapse
We need a dev.
I didn't come from a previous Iconia. So maybe someone with experience building for the A500 can help us out. (Assuming he also gets the A510.)
P.S. I didn't know that we already have kernel sources for the A510. That's good news then.
yep :
there :
http://us.acer.com/ac/en/US/content/drivers
into 'Document' sheet
don't know if it's complete but at least it's mentioned "kernel source code (for Android 4.0.3 Ice Cream Sandwich)"
In addition, there are already some git :
https://github.com/Dees-Troy/android_device_acer_picasso_m
Same bug here.
Waiting for a "definitive" fix.
CWN recovery + nothrill rom might be an option to consider
Should you decide to try it, use the Optimized A510 rom. I had that issue before, and the Franken700 rom has that same issue.
I believe it should be gone with the 1.099 stock rom (which is the optimized A510 rom by NoThrills.
Removing my screen protector + installing the latest nothrill ROM fixed it for me.
remove your screen protector if you have one.
remove screen protector
http://forum.xda-developers.com/showthread.php?t=1887688 as posted in this thread, i would suggest to remove the screen protector too, if you have one. Fixes the responsivness bug for me. Stock A700.
Yeah, I used my tab for a week without the screen protector (regardless of what ROM I use), and it did remove my screen responsiveness bug.
However, I'd rather live with that bug than to have a scratched screen in a few months.
salisbury_steak said:
Yeah, I used my tab for a week without the screen protector (regardless of what ROM I use), and it did remove my screen responsiveness bug.
However, I'd rather live with that bug than to have a scratched screen in a few months.
Click to expand...
Click to collapse
Last update .
On the bring of returning it for a Prime, I tried installing NoThrill's yesterday's release of a ROM. The usual prodecure, data/factory wipe, then install from SD card NoThrill's today release.
Upon booting, the response seemed slightly better; I went into the settings, and the responsiveness had defaulted to low.
I set it to high, rebooted and had no more problems.
Whether it's grounded, or not it works perfect.
I pushed my luck and also installed my screen protector again. It once more works perfect. Super sensitivity.
I strongly suggest installing yesterday's Nothrill ROM. I had the 5th of september one, and there was no fix. The 19th did it.
Many thanks to Nothrills. Saved me from spending 150 more pounds needlesly
+1 on the Sept18 build. (I posted it in NoThrill's optimized rom thread yesterday.)
For all we know, it might have been the kernel that fixed it.

Nexus S, ICS, and capacitive button light notification

One of the things that turned me off and kept me on cm7 was the lack of of capacitive button notification lighting in ICS. Is there a way that this has been resolved on stock without using another CM rom? I am really hesitant to go back to an alpha build because it took me so long to get full functionality from the rom and the phone and work exactly how I wanted it.
Thanks.
Alpha lol!! Flash a kernel with bln....
Sent from my Nexus S using xda app-developers app
CM7 isn't ICS, that's CM9. Also it hasn't been an alpha for at least 2 months, it's in RC1 which is as stable as you're going to get.
Use Airkernel or Martrix Kernel to enable BLN.(You can use NSTOOLS to adjust the settings).
Reread what I wrote. One of the things that turned me off of ICS and kept me on CM7 (I know it's GB) is the lack of notification lit capacitive buttons. I basically want to upgrade to ICS or later (really JB once there is a more functional release) but those lit capacitive buttons are crucial for me as I have the att nexus s that has lcd screen and not the more effecient led screen. So a lot of those led notification apps dont help me. A couple of responses here are helpful. I'm hoping there will be a kernel with bln for stock ota jellybean when that comes out. Will that be easy to attain?
It shouldn't be hard to implement BLN for jb. There are numerous kernels with back light notifications for 4.0.4. Have you even checked the development section?
Sent by pocket technology.
chronophase1 said:
It shouldn't be hard to implement BLN for jb. There are numerous kernels with back light notifications for 4.0.4. Have you even checked the development section?
Sent by pocket technology.
Click to expand...
Click to collapse
I didn't know they were called back light notifications until this post (I had kept searching "capacitive button notification light nexus s" the whole time) , so please bare with me as I'm learning. I appreciate your pointing me in the right direction. It gives me hope that when a very functional release of JB for nexus s is out I will be able to use BLN on it.
Its cool. I didn't mean to come across so harshly. My apologies. Yeah. There's a ton of kernels that support it. Just take your pick
Sent by pocket technology.

[Q] [CM7][Problem] Black screen bug

on every single cm7, or cm7 based rom, i get the same problem, when i dim the screen, then turn it back on nad black screen. backlight is on, but screen is not. to run any new bb rom i have to use a special kernel so kernels cannot be used. The thing is, after 2 or 3 times, the screen comes on, or if i tap the screen it comes on.
but i tried fundoozzz's miui pureveiw which i now assume is based of cm7, and guess what, the screen does not come on-at all.
any suggestions
russian392 said:
on every single cm7, or cm7 based rom, i get the same problem, when i dim the screen, then turn it back on nad black screen. backlight is on, but screen is not. to run any new bb rom i have to use a special kernel so kernels cannot be used. The thing is, after 2 or 3 times, the screen comes on, or if i tap the screen it comes on.
but i tried fundoozzz's miui pureveiw which i now assume is based of cm7, and guess what, the screen does not come on-at all.
any suggestions
Click to expand...
Click to collapse
Same problem here. My phone does not like cm7 roms. :-\ it simply falls dead
I use cm9, aosp gb and ics without any of problems.
I'm trying the new MIUI pure view and the problem is horrible. Working g on a solution.
Sent from my LG-P506 using xda premium
sarus_b said:
Same problem here. My phone does not like cm7 roms. :-\ it simply falls dead
I use cm9, aosp gb and ics without any of problems.
Click to expand...
Click to collapse
anyway i think i found a fix if anyone has a black screen bug like that, or lets just say you cant run aokp.
http://forum.xda-developers.com/showthread.php?t=1227682
i would switch to rashed97's cm10 rom, its way more stable than all the other stuff, and it has a version for each optimus phone
Exactly,, what is the fix you found...
Do you tested on your lg thrive?
gabo_lope said:
Exactly,, what is the fix you found...
Do you tested on your lg thrive?
Click to expand...
Click to collapse
The kernels included multiple black screen bug fixes, I assumed the could work, but my thrive did not like them, my color was way off and stuff like that. Black screen persists but depends on ROM I think. Give it a go and don't forget, backup everything.
Sent from my LG-P506 using xda premium
i only had that problem on. cm9, try gingersnap 2.3, it doesnt has that problem
i would really like to use fundoozz's miui pureview rom, it has the issue, i doubt it is based of cm7 but it is GB, i have no freaking idea what the problem could be, but still looking, also plz help me, get a cm7 rom that has the issue and try finding a fix for it by testing.
Thanks,

Categories

Resources