[BUG]Motorola Official Flip Cover - Lollipop/Marshmallow - Vibration on Incoming call - Moto G 2015 Q&A, Help & Troubleshooting

Affected system:
Android Lollipop 5.x.x/Marshmallow 6.x.x
Affected device(s):
All Moto G (1st, 2nd and 3rd gen) with Magnetic Flip Cover (+ All Nexus devices)
Issue:
With Flip Cover closed and being turned on "Also Vibrate for Calls" option phone vibrates only once for incoming calls
Result:
Many missed calls.
Diagnosis:
It seems to be related to the Magnetic Sensor Mechanism and Automatic Screen On/Off Feature.
This issue has also been reported to the AOSP action tracker, but no one seems to care.
There is also a workaround described, but I am not a programmer / developer.
I invite developers including @Alberto97, @squid2 to solve this issue.
I also invite @rovo89, @C3C076 to see anything can be done through Xposed Framework.

Related

[Q] Moto G - Screen does not wake in Flip Case.

Hi Everyone
I am using indian version of Moto G (Dual Sim) :angel: with Kitkat Vers. 4.4.2. :victory:
Also, purchased a Nillkin Fresh Leather Flip Diary Cover Case For Motorola Moto G. (see image)
Now, benefit of this case is that it has a cut out on the top side of the flip (see image), so that whenever there is an incoming call,caller id should be visible in that cut out. This was the primary reason to buy such an overpriced case.
It also locks the screen when you close the flip and wakes up the screen when you open the flip. Smart thing to have !:good:
But, unfortunately the screen remains off whenever there is an incoming call, it remians off until you open the flip. Ideally screen should wake up for incoming call even if the proximity sensor is blocked until you answer the call. Its definitely the proximity sensor at work but its not serving the purpose of the cut out.
If any one noticed the same issue and has a solution to the problem, please feel free to answer or PM me ! Would be highly Obliged !
same issue with me plz tell the solution
hi
same with me please anyone tell the solution
Grab a magnet and try the following: http://www.youtube.com/watch?v=L_KL60gf_hU
If this works for you the issue is related with the cover.
I bought the same cover and I faced same problem ,,, any solution please .
If you are rooted, you can try this xposed mod.
http://tinyurl.com/qbpjv22/MotoMagnetOff_test3.apk
I've just added an setting checkbox to wake the phone if it's ringing.
Moto G - Screen does not wake in Flip Case.
hi anish.awalkar ..have you got the solution?

[Q] Lost features in 23.3.24 ?

Hi,
I just updated my Droud Ultra and it looks like there are missing two features:
1. in the 21.xxx sw if I approached with my hand the proximity sensor the phone shows the time/missed events. Now if I want to see the clock I have to move / to jog the phone it is not enough to go close with my palm to proximity sensor
2. in the 21.xxxx when the phone was charging a stripe/band was going up and down -- now it is missing, too (
How could I enable this features or they are turned off ?
For the first one. Yes, waving the hand over the phone no longer wakes it up. According to one of the moderators on the Moto support forum, the ability to display notifications with a wave of the hand was a bug that Moto fixed. I know..... So there is no way to reactivate it 23.3.24. Sorry.
Source:
https://forums.motorola.com/posts/fe26ceed34
Also stock messaging app no longer allows you to open the address book and multi select recipients. Hangouts is the same.
I could slap whomever decided to do this!
Touchless controls actually goes to speakerphone now when making a call if you have the setting checked, it was broken in the last update and wouldn't actually go to speakerphone even though it was checked but worked before that one. I'm so glad it works now.

Proximity Sensor Bug/Glitch - Maybe Hardware or Kernel issue - Any Solution?

The Tampered, Unclocked, S-Off, Cid-11111111, HBoot 2.22, Rooted HTC One Mini that I have doesn't ring when Proximity Sensor reads "NEAR".
I'm aware of Sense 6 options like "Ring louder when in pocket" but none of them worked on making the phone ring when a call is received.
That happened when the phone was completely stock, so recently I went through all the process of S-Offing it to install a new Rom. I choose the latest Insert Coin 5.0.8, but the problem persists. so now I'm almost certain it's an hardware issue...
The phone has several years old and returning it for repair/replaced isn't really an option.
Since I'm giving this phone to my mother, I really need it to ring and vibrate when someone calls her or else she'll never pickup any calls with the phone in her purse.
I've tried installing Xposed Framework to have a try at the sensor disabling app, but the whole rom crashed badly and I needed to reinstall everything.
Other usefull info:
Kernel: [email protected] [email protected] #1 SMP FREEMPT
Is there a way to override proximity sensor when a call is received and/or making the phone ring regardless of proximity sensor state?
Looking foward for an expert tip. Thanks.
I've installed "[ROM][M4 - 4.14.401.1] Official Stock Sense 6 Rom v3 & Firmware" from xXminiWHOOPERxX -> Installed xPosed -> Sensor Disabler
Then I tried to Disable Proximity, Disable Light sensor, Mock Proximity to FAR, Disable both proximity and Light, Block Call app from accessing Proximity....nothing worked: Meaning the sensors still function normal...
BUT then I noticed something strange:
Running "Sensors Test" app,
IF I put my finger just over light sensor -> proximity reads "NEAR"
IF I put my finger just over proximity -> proximity reads "NEAR"
....Meaning that the light sensor is acting as proximity!
My next step was to identify which "dot" was the light sensor, since both acted as proximity and I used some black tape covering one of the sensors (that I've identified as the proximity)...and now the proximity sensor always reads "FAR"!!
To be sure it wasn't xPosed doing the trick I reset all things to normal and uninstalled everything...and with the black tape covering the sensor it still reads "FAR" thus resolving my issue of the phone not ringing when a call is received...
I now have to figure out if painting the sensor black has the same result, because tape looks ugly. I'll make a vídeo and post the link here.

Incoming Call Screen problems

Hi all,
I am using a Moto G4 on android 7.0. I personally find the default android swipe from the centre to answer icon un-intuitive and difficult for answering the phone from the lock screen . I would much rather have an accept / decline button . I have tried a few of the incoming call screen apps which feature accept/decline buttons but am finding that in all cases ( so far) the decline button works but the accept button does not - it is odd that this is applying across multiple apps and suggests that it is soething within the OS that is causing the issue . Has anyone else noticed this or found a resolution ?
Slight off the topic but there is of course an accept / decline option ( a headsup I think ?) if the phone is already unlocked but I find it too insignificant to always notice and in any case results in a totally inconsistent experience when answering calls (one way from the lock screen - a different way otherwise ). I understand the headsup is so as to not take over the phone if somebody is otherwise engaged but for me the primary purpose of the phone is to be a phone i.e make and receive calls , then perhaps SMS and only then other apps.

Proximity Sensor Location/Issues

Was trying to verify the Easy Mute motion (hand over screen or flip to mute calls or alarms), and it does not seem to work in either folded or unfolded configuration. I also tried running AndroSensor and that shows no change in sensor when I cover the top half of either screen. Anyone else having similar problems, or is it working as expected for them.
Vimes14 said:
Was trying to verify the Easy Mute motion (hand over screen or flip to mute calls or alarms), and it does not seem to work in either folded or unfolded configuration. I also tried running AndroSensor and that shows no change in sensor when I cover the top half of either screen. Anyone else having similar problems, or is it working as expected for them.
Click to expand...
Click to collapse
.
I just tried it myself and turning over the phone definitely muted the incoming call (with the phone open or closed) Also the palm gesture worked (cover screen only) but that was slightly more difficult as you really have to cover the whole screen for a couple of seconds.
I also used AndroSensor (and another app) and noted the proximity sensor was present but wasn't showing a reading. Obviously it is working (and works when holding phone to ear by turning screen off for example).
So I am not sure why it's not working for you.
.
apprentice said:
.
So I am not sure why it's not working for you.
.
Click to expand...
Click to collapse
Thanks for checking.
Did some more testing, the flip gesture seems to be working for incoming calls with the Google Phone app, and alarms created by the Samsung Clock app, but not the Google Clock app or Calendar notifications. Using the Google Phone app once the call is established, then the screen does turn off when held close to a head when folded. So seems like the sensor is working, in some situations, which means it is probably software related, rather a hardware defect. I really don't want have to reconfigure my setup up again.
The Google Phone app also has a setting flip to mute, which was not set. So I flipped that to true.
I had previously written a Tasker profile to mute everything (enter Do Not Disturb) on a Pixel 3XL, before Google implemented it at the OS level, so I may try that here.
Certainly seems like a conflict with the Google phone app. The gesture settings are OneUI features so they are unlikely to work with a different dialer.
.
apprentice said:
Certainly seems like a conflict with the Google phone app. The gesture settings are OneUI features so they are unlikely to work with a different dialer.
.
Click to expand...
Click to collapse
I think the problem is that the Samsung implementation is to hook into a small subset of their applications to do a local mute, where as Google implementation just invoked Do Not Disturb, which meant every application would mute, assuming they are compliant. I think DND was slightly flakey on OS9, but from OS10 onwards it was rock steady.
To bring clarity to my local behaviour, I enabled my Tasker method that engaged DND when the phone is flipped. Works in both folded and unfolded configurations. As a bonus with Join, I have a method that automatically distributes DND to my other devices.

Categories

Resources