Database Users

Quick question re Accelerometer

Good day XDA. I just noticed that my N7 is having problems with its accelerometer. I was playing temple run and mutant road kill and the characters always veer to the right.
Question is: is this a software or a hardware issue?
also, is there a fix/app if this is indeed a software issue?
thanks

well, i know that there is apps for calibrate the accelerometer, i can´t remember now the name, sorry, but i´m sure that you can find it on the market o google.
Anyways, did you try in diferents places? i mean, maybe the surface where you try wasn´t flat...

thanks for the reply man.. anyway, i already found a way to fix it and it's been holding up.

juanito05 said:
thanks for the reply man.. anyway, i already found a way to fix it and it's been holding up.
Click to expand...
Click to collapse
What's the fix?

What did you do to fix the issue?
Sent from my Paranoid Nexus 7

well first you have to confirm that you indeed have the gyro/accelerometer problem. you guys could download an app for that (i used Android Sensor Box). once that is confirmed, download the app "GPS Status". Run it and go to tools, then calibrate pitch and roll and just follow the instructions. I suggest you guys do this while your device is lying flat on a surface.
after trying this fix, i uninstalled GPS Status, rebooted my device and it held up. played temple run and the character started right smack in the middle lol. also tried checking the sensors using Android Sensor Box and it was calibrated. i just reinstalled GPS Sensor just in case i might need it down the road but im hoping this fix will be permanent. if it isnt, im pretty sure that this is a software problem and an update could give a permanent solution.
let me know if you guys get the same result i had with this.
Thanks

juanito05 said:
well first you have to confirm that you indeed have the gyro/accelerometer problem. you guys could download an app for that (i used Android Sensor Box). once that is confirmed, download the app "GPS Status". Run it and go to tools, then calibrate pitch and roll and just follow the instructions. I suggest you guys do this while your device is lying flat on a surface.
after trying this fix, i uninstalled GPS Status, rebooted my device and it held up. played temple run and the character started right smack in the middle lol. also tried checking the sensors using Android Sensor Box and it was calibrated. i just reinstalled GPS Sensor just in case i might need it down the road but im hoping this fix will be permanent. if it isnt, im pretty sure that this is a software problem and an update could give a permanent solution.
let me know if you guys get the same result i had with this.
Thanks
Click to expand...
Click to collapse
That was amazing man. I have been swearing over this accelerometer issue ever since I got the device, and now it's perfect. :beer:
Sent from my SGH-I747M using xda app-developers app

Had exactly same issues on all three units I have purchased. GPS Status app does fix the problem. Thanks for the solution.

GPS status did nothing for me.
Same problem veering to the right
Held n7 landscape
Reboot
After reboot accelerometer is working fine
Sent from my Nexus 7

bagofcrap24 said:
GPS status did nothing for me.
Same problem veering to the right
Held n7 landscape
Reboot
After reboot accelerometer is working fine
Sent from my Nexus 7
Click to expand...
Click to collapse
This didn't do the thIng for me neither
But I did the job like this.
Open an app that uses the compass. You can use GPS Status, Android Sensor Box or whatever app you like that uses a compass.
twist/turn your device 3 times around each of all the three axes
FINISH
Even after a reboot it works great.
But if you flash a new rom this fix will be broken

Stop the ear piercing camera sound?

I want to stop the ear shattering "beep" that happens when the focus locks on. I tried deleting a bunch of the camera.ogg sound files located in system/media/ui but even after that, nothing made it stop.
Does anyone know how to do this? There has to be a way, because this camera noise is incredibly annoying. It's far worse than any camera noise I've ever heard on any device.
Thanks in advance.

This won't help but this is one of the reason why I ended up selling my note 3 after 4 weeks. I'm back to my s3 with pleasure on this point and some bucks in my pocket. I add the french version which shutter seems impossible to turn off. I hope your are not in the same case I was.
Envoyé de mon GT-I9300 en utilisant Tapatalk

donalgodon said:
I want to stop the ear shattering "beep" that happens when the focus locks on. I tried deleting a bunch of the camera.ogg sound files located in system/media/ui but even after that, nothing made it stop.
Does anyone know how to do this? There has to be a way, because this camera noise is incredibly annoying. It's far worse than any camera noise I've ever heard on any device.
Thanks in advance.
Click to expand...
Click to collapse
If you are rooted there is a couple of mods around the forum, if not then for now you'll have to put your phone on silent when you take pics :/
ForeverTroll said:
This won't help but this is one of the reason why I ended up selling my note 3 after 4 weeks. I'm back to my s3 with pleasure on this point and some bucks in my pocket. I add the french version which shutter seems impossible to turn off. I hope your are not in the same case I was.
Envoyé de mon GT-I9300 en utilisant Tapatalk
Click to expand...
Click to collapse
You sold your phone because of one single noise ?

You cant silence it unlesss your rooted , Its actually Illegal to silence it in some areas/countries

I'm rooted, and I searched, but I found nothing, otherwise, I'd not have asked.
Can anyone point me toward the solution, please?

Have you got xposed framework and Wanam installed? if so (since you are rooted) there is an option in Wanam to disable it.

radicalisto said:
Have you got xposed framework and Wanam installed? if so (since you are rooted) there is an option in Wanam to disable it.
Click to expand...
Click to collapse
Yes, I am rooted, and yes, I have Wanam/Xposed installed, but no, sadly, it doesn't disable the sound, even though I checked it as an option and rebooted.

donalgodon said:
Yes, I am rooted, and yes, I have Wanam/Xposed installed, but no, sadly, it doesn't disable the sound, even though I checked it as an option and rebooted.
Click to expand...
Click to collapse
hmm that is strange, I just tried it on mine and it disabled it. What firmware are you running? and is Wanam enabled and updated OK? - trivial I know but it's always the smallest of things that catches us out lol

radicalisto said:
hmm that is strange, I just tried it on mine and it disabled it. What firmware are you running? and is Wanam enabled and updated OK? - trivial I know but it's always the smallest of things that catches us out lol
Click to expand...
Click to collapse
N900UBUCMJ7 SM-N900
I have the latest module and framework installed.
I noticed that it will SOMETIMES, but not always, disable the sound if I don't use touch focus, but it never will if I do. The same horrid, screeching "beep" on touch focus lock is present.

Is possible that the N900 camera disable sound via Wanam might be slightly different to the N9005 (which I have) and therefore work sporadically. - I'm sure I seen another mod in themes and apps here on xda about disabling the noise, I'll have a scout around and try and find it for you if I can.

radicalisto said:
You sold your phone because of one single noise ?
Click to expand...
Click to collapse
I sold the note 3 because :
- of the camera noise
- of the impossibilty to read a ntfs usb drive without rooting
- the sound is a bit worst than the s3 with my 2 headsets.
- I did not found the pen to be so useful, I'm faster with the keyboard
- the fact that if I turn off the screen when using my copilot gps I had to enter my password to unlock. That's not convenient when driving. My s3 detect when gps is running and never locks when I turn the screen off to keep some battery.
- it's too big in a jeans pocket and the screen is not big enought to view correctly movies and photos. I think i'll get something of 7-8" running Windows 8.1 to complement the s3.
Envoyé de mon GT-I9300 en utilisant Tapatalk

ForeverTroll said:
I sold the note 3 because :
- of the shutter noise
- of the impossibilty to read a ntfs usb drive without rooting
- I did not found the pen to be so useful, I'm faster with the keyboard
- the fact that if I turn off the screen when using my copilot gps I had to enter my password to unlock. That's not convenient when driving. My s3 detect when gps is running and never locks when I turn the screen off to keep some battery.
- it's too big in a jeans pocket and the screen is not big enought to view correctly movies and photos. I think i'll get something of 7-8" running Windows 8.1 to complement the s3.
Envoyé de mon GT-I9300 en utilisant Tapatalk
Click to expand...
Click to collapse
You are a hard person to please. I hope you find the perfect phone that meets all your needs / wants, but somehow I doubt you will.

jamesindc said:
You are a hard person to please. I hope you find the perfect phone that meets all your needs / wants, but somehow I doubt you will.
Click to expand...
Click to collapse
Actually the s3 meets my needs as a phone but I though the n3 could merge my phone and my small laptop for traveling lightweight. It doesn't make the job easily regarding my wishes and doesn't worth the upgrade from the s3 in my case.
Envoyé de mon GT-I9300 en utilisant Tapatalk

[Workaround] Kitkat Frozen/Lag on Lockscreen/Homescreen

For anyone experiencing frozen/lag on Kitkat, especially after lockscreen, please check the memory and CPU consumption when the lag is happening (e.g. Watchdog Lite on Playstore).
Suspect :
[SystemUI memory leak]
In 4.4 Kitkat this SystemUI service is launched in the same package of S-View Cover services and Keyguard (Lockscreen) services.
This problem was known in 4.2.2 and fixed on 4.3 JB but seems resurrected on Kitkat.
Some components were not de-registered from memory after created and no longer being used especially by using lockscreen (and S-View cover) this object recreation seems to be overloading the memory and also eating CPU slice time.
Known Workaround
- Restart cellphone
- Restart SystemUI
- Refrain to use Lockscreen + SView cover together until further updates
Old Ref (applicable for 4.2.2 not Kitkat) :
http://forum.xda-developers.com/gala...i-4-2-t2178962

I managed to isolate the problem, it is S-View cover used with Lockscreen that caused this. Dont know i this is closely related to TouchWiz or not. I'm currently still investigating.
[Workaround]
Use S-View cover without Lockscreen .. or use Lockscreen without S-View cover.

Thanks for letting us know this my good man.
I have been suffering from the same symptoms and have been investigating this, but since i do not have root, it seems to be very hard to track this.
please let us know if you find any answers to this nlatifolia.

ckhurana said:
Thanks for letting us know this my good man.
I have been suffering from the same symptoms and have been investigating this, but since i do not have root, it seems to be very hard to track this.
please let us know if you find any answers to this nlatifolia.
Click to expand...
Click to collapse
For now, it is the Lockscreen that is suspected. Original Google Lockscreen is fine such on Nexus, on Samsung it has been modified to work together with S-View cover and to show Music Art.
Most symptoms are reproduceable if using S-View cover and Lockscreen at the same time though sometimes Lockscreen alone can cause this (apparently doing ****ty stuff in background on screen wake up).
To check ****ty stuff I use this : https://play.google.com/store/apps/details?id=com.zomut.watchdoglite

This happens to me also, i don't want to root the phone or downgrade it to 4.3 because it might trigger Knox and I already sent the phone back to them with an overheating problem, i don't want any more surprises from a very expensive phone that can't be covered by warranty.
I tried removing the password from the lockscreen and it's still having problems: i close the S view, push the power button and the screen stays off whilst the buttons light up. It's stupid cuz it's original Samsung software with original cover.....
Is there any way to downgrade without losing warranty or do you know if Samsung is thinking of pushing a fix?
I tried without success:
turning off all the sensors
turning off power saving
uninstalling a bunch of apps
I did not try factory reset yet, I'm afraid i'll kick the phone to pieces if i to a factory reset and nothing is changed, and i have to sent it to warranty again...

dumitrudan608 said:
This happens to me also, i don't want to root the phone or downgrade it to 4.3 because it might trigger Knox and I already sent the phone back to them with an overheating problem, i don't want any more surprises from a very expensive phone that can't be covered by warranty.
I tried removing the password from the lockscreen and it's still having problems: i close the S view, push the power button and the screen stays off whilst the buttons light up. It's stupid cuz it's original Samsung software with original cover.....
Is there any way to downgrade without losing warranty or do you know if Samsung is thinking of pushing a fix?
I tried without success:
turning off all the sensors
turning off power saving
uninstalling a bunch of apps
I did not try factory reset yet, I'm afraid i'll kick the phone to pieces if i to a factory reset and nothing is changed, and i have to sent it to warranty again...
Click to expand...
Click to collapse
I have the S View from Spigen (slim armor) After trying everything, I am negotiating a refund/or a cover replacement. Don't know why a stupid thing like the phone cover is now a big deal with Samsung.
I sure do hope that Samsung would release a fix for the issue though. Let's see.
I have tried 3rd party apps for this too... And Sipgen advised me to install them! Imagine!

does anybody know if this problem occurs also with the original Samsung Chip from the original Sview Cover?
because otherwise it might be also a problem with the chip from Spigen.

duttla said:
does anybody know if this problem occurs also with the original Samsung Chip from the original Sview Cover?
because otherwise it might be also a problem with the chip from Spigen.
Click to expand...
Click to collapse
Hi, I have an Original S Case bought from Orange Romania, with Samsung warranty and everything. The S-view function does not work with third party cases unless there is a specific software for it. Mine worked on 4.3 and on 4.4 with no added software, and i still have problems with the Screen not turning ON.
I did find a workaround however: turn of your lockscreen, any password, any swipe everything, and your screen will turn on with no delay. I had to remove my work email to get rig of the password....
By the way, does anyone know of an exchange email app that does not require the whole phone to be locked? it needs to be compatible with Office 365 like Cloud Magic is, but i also need my calendar displayed, and Cloud Magic does not do that.

no Sview works with the spigen armor view case @ Android 4.4.2
but I have the same problem like Ckhurana
ckhurana said:
Hi
I had the issues of screen not getting switched off on cover close and vice versa.
I got the replacement chip from spigen. Installed it 3 days back. Now the cover runs fine for 2 to 3 times only and after that it gives up.
The s view is more or less unusable now. It only gets launched if I either restart the phone or reinstall the cover.
Moreover I got the issue of screen getting switched on by itself when locked and thus a massive battery drain.
My phone is not rooted and I need to check if the s_view process is getting some issues. Any way I can do that?
And also if I can check if the chip is the issue or the low power magnet on the front flap. Let me know if anyone can help please!
Many thanks
Ckhurana
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse

Dear all,
the only way i have been able to get rid of this issue was by removing exchange mail/calendar and pin lockscreen. My note 3 has now low level of security ( swipe) but i can enjoy my samsung sview and docking station as i had issues with that one too.
Quite disappointed from a top device such as the NOTE 3
dumitrudan608 said:
Hi, I have an Original S Case bought from Orange Romania, with Samsung warranty and everything. The S-view function does not work with third party cases unless there is a specific software for it. Mine worked on 4.3 and on 4.4 with no added software, and i still have problems with the Screen not turning ON.
I did find a workaround however: turn of your lockscreen, any password, any swipe everything, and your screen will turn on with no delay. I had to remove my work email to get rig of the password....
By the way, does anyone know of an exchange email app that does not require the whole phone to be locked? it needs to be compatible with Office 365 like Cloud Magic is, but i also need my calendar displayed, and Cloud Magic does not do that.
Click to expand...
Click to collapse

dumitrudan608 said:
By the way, does anyone know of an exchange email app that does not require the whole phone to be locked? it needs to be compatible with Office 365 like Cloud Magic is, but i also need my calendar displayed, and Cloud Magic does not do that.
Click to expand...
Click to collapse
Touchdown works with Exchange and PIN enforcement. The policy will make the app enforce the PIN rather than the entire phone.
I do not know much about its compatability with Office 365, but it works well with exchange address book/calendar/email functions.
Sent from my SM-N9005 using XDA Premium 4 mobile app
---------- Post added at 03:24 PM ---------- Previous post was at 03:19 PM ----------
I use a pattern unlock and in the beginning it would occasionally freeze with my Original Samsung Charging S View cover after the Kitkat update. In my case, removing all security and reapplying the pattern unlock lockscreen worked for me and I no longer have freezes. I have not tried with PIN or password unlock lockscreens however. Your mileage may vary.
Sent from my SM-N9005 using XDA Premium 4 mobile app

ckhurana said:
Thanks for letting us know this my good man.
I have been suffering from the same symptoms and have been investigating this, but since i do not have root, it seems to be very hard to track this.
please let us know if you find any answers to this nlatifolia.
Click to expand...
Click to collapse
dumitrudan608 said:
This happens to me also, i don't want to root the phone or downgrade it to 4.3 because it might trigger Knox and I already sent the phone back to them with an overheating problem, i don't want any more surprises from a very expensive phone that can't be covered by warranty.
I tried removing the password from the lockscreen and it's still having problems: i close the S view, push the power button and the screen stays off whilst the buttons light up. It's stupid cuz it's original Samsung software with original cover.....
Is there any way to downgrade without losing warranty or do you know if Samsung is thinking of pushing a fix?
I tried without success:
turning off all the sensors
turning off power saving
uninstalling a bunch of apps
I did not try factory reset yet, I'm afraid i'll kick the phone to pieces if i to a factory reset and nothing is changed, and i have to sent it to warranty again...
Click to expand...
Click to collapse
duttla said:
does anybody know if this problem occurs also with the original Samsung Chip from the original Sview Cover?
because otherwise it might be also a problem with the chip from Spigen.
Click to expand...
Click to collapse
dumitrudan608 said:
Hi, I have an Original S Case bought from Orange Romania, with Samsung warranty and everything. The S-view function does not work with third party cases unless there is a specific software for it. Mine worked on 4.3 and on 4.4 with no added software, and i still have problems with the Screen not turning ON.
I did find a workaround however: turn of your lockscreen, any password, any swipe everything, and your screen will turn on with no delay. I had to remove my work email to get rig of the password....
By the way, does anyone know of an exchange email app that does not require the whole phone to be locked? it needs to be compatible with Office 365 like Cloud Magic is, but i also need my calendar displayed, and Cloud Magic does not do that.
Click to expand...
Click to collapse
Labron said:
Dear all,
the only way i have been able to get rid of this issue was by removing exchange mail/calendar and pin lockscreen. My note 3 has now low level of security ( swipe) but i can enjoy my samsung sview and docking station as i had issues with that one too.
Quite disappointed from a top device such as the NOTE 3
Click to expand...
Click to collapse
I'm currently using original Samsung chip (removed from original case and put into Spigen SAV) and the problem persists.
After a bit of more tests, I can safely conclude that the problem occured if we use S-View cover together with any type of stock Lockscreen.
[Current Workaround]
Use S-View cover without Lockscreen .. or use Lockscreen without S-View cover.
Note :
I'm currently trying to hack into the SystemUI code but no promise here as even if that suceeded I'm afraid we have to root to install the patch.

I'm currently using the original Sview Cover with no lock screen and it works without any troubles.
The phone has Android 4.4.2 and ist not rooted.

duttla said:
I'm currently using the original Sview Cover with no lock screen and it works without any troubles.
The phone has Android 4.4.2 and ist not rooted.
Click to expand...
Click to collapse
Yes, and what do you do if you have work mail with exchange enforce security that makes you have a password...? seriously Samsung did this and nothing official about this? i cannot believe this..

nlatifolia said:
For anyone experiencing frozen/lag on Kitkat, especially after lockscreen, please check the memory and CPU consumption when the lag is happening (e.g. Watchdog Lite on Playstore).
Click to expand...
Click to collapse
Btw, how much can be called leak?
Mine floating around 73Mb - 155Mb across several days (usually about 1 week)...
I use stock PIN lockscreen + xposed maximize widget + S-View cover from you
And I experience no lag/freeze after lockscreen.
What I noticed: S-Planner not displaying any dismis/snooze like Alarm on S-View, I have to open the cover to dismis it.
But when I use S5 S-Planner, it displayed, but I dont want S5 version, it got no handwriting feature...

Crescendo Xenomorph said:
Btw, how much can be called leak?
Mine floating around 73Mb - 155Mb across several days (usually about 1 week)...
I use stock PIN lockscreen + xposed maximize widget + S-View cover from you
And I experience no lag/freeze after lockscreen.
What I noticed: S-Planner not displaying any dismis/snooze like Alarm on S-View, I have to open the cover to dismis it.
But when I use S5 S-Planner, it displayed, but I dont want S5 version, it got no handwriting feature...
Click to expand...
Click to collapse
Hehe u don't need use expose sview mod for that. Try use original S View stock app and see if that is the culprit.
Sent from my SM-N900 using Tapatalk

Thanks, Touchdown/no Pin workaround worked for me!
Hi all
I was having similar issues to dumitrudan608 in particular. Huge hang on the lockscreen of up to a minute and normally above 10 seconds on Note 3. We recently acquired 2 of these to be used as company phones and BOTH were experiencing this.
I tried wiping the cache, factory reset, no S view cover, S view cover and turning on and off all sorts of settings but none of this worked. I managed to pinpoint this down to the native e-mail app which had been configured to use Exchange. Similar to dumitrudan608 we were forced to use a PIN (which shouldn't really be an issue, it should just work!).
I also rooted both devices in order to use BetterBatteryStats (can't use without root on KitKat) and to try to determine which wakelocks were causing the device to freeze up. There wasn't a massive battery drain though so this doesn't seem to be the issue. Plus, one of the phone's had nlpwakelock as the most common process however for the other one it was AlarmManager so there was no consistency.
I've now just removed the exchange account from the e-mail app, changed the lockscreen PIN to a pattern & wiped the cache. I've then installed Touchdown thanks to the advice from monomer888 & set it up with the same PIN as was previously on the lockscreen. There is absolutely no lag whatsoever, the phone is now flying. I've yet to try on the other device however I will when I get the chance (unfortunately I believe it's been dropped into Samsung...) and report back here.
A note on Touchdown, so far so good, it does all we want it to so far, so seems to be a viable replacement.
Also, the S view cover is now being used and so I can assume that, at least for us, this was not the cause of our issue. I have read that Samsung have acknowledged that there is an issue surrounding 3rd party covers however due to a chip in the device.
The only issue with this workaround is that you need a pattern to unlock the phone and then a PIN to unlock the app which is a bit tedious.
This is really basic stuff that Samsung should be getting right though. I'll be unwilling to test if the issue is fixed in a future update as having this working is more important to us.
Thanks guys, hope this helps you!

Hi again
I have done the same process on the other Note 3 and am happy to confirm that the issue has also been fixed by the method I used above, so this definitely seems to confirm the problem we were having.

Dissapointing .. we need to contact support
I have Note 3 SMN-900 (kitkat 4.4.2) with original sview cover
this is very disappointing !
thanks for the workaround , which is fine, but a fix is essential to be able to use google deivce policy
How to file a ticket to Samsung support regarding this ?

AminoNote3 said:
I have Note 3 SMN-900 (kitkat 4.4.2) with original sview cover
this is very disappointing !
thanks for the workaround , which is fine, but a fix is essential to be able to use google deivce policy
How to file a ticket to Samsung support regarding this ?
Click to expand...
Click to collapse
Have the same problem with my samsung note 3 after upgrade to android 4.42. I m using cloud magic as exchange mail for my company email. Just log ticket to samsung support malaysia but they claim this issue is related to google android 4.42 which have bug. So all the problem they throw it to google as this is not related to their device. How can samsung so not responsible for this issue.

Double tap to wake not working anymore

Double tap to wake is the feature I almost explicitly use to wakeup my phone to look at the notifications, especially so in Zuk Z, which has this crazy fast fingerprint scanner.
Lately, it stopped to work. I was trying to figure out the latest changes I did in my phone and I couldn't think of anything but the last CyanogenOS OTA update (YOG4PAS3OH) but it might be just coincidental. I have done quite a bit of troubleshooting, involving (but not limited to) disabling/enabling the feature, removing proximity sensor check, rebooting, etc but haven't done factory reset (which I'd be very reluctant to do anyway). Double tap to sleep is working fine though.
Few questions for folks here:
1. Is it working for you after the latest OTA?
2. Could this a hardware issue?
3. Any suggestions for me to try and make this work again?
Thank you!

malikons said:
Double tap to wake is the feature I almost explicitly use to wakeup my phone to look at the notifications, especially so in Zuk Z, which has this crazy fast fingerprint scanner.
Lately, it stopped to work. I was trying to figure out the latest changes I did in my phone and I couldn't think of anything but the last CyanogenOS OTA update (YOG4PAS3OH) but it might be just coincidental. I have done quite a bit of troubleshooting, involving (but not limited to) disabling/enabling the feature, removing proximity sensor check, rebooting, etc but haven't done factory reset (which I'd be very reluctant to do anyway). Double tap to sleep is working fine though.
Few questions for folks here:
1. Is it working for you after the latest OTA?
2. Could this a hardware issue?
3. Any suggestions for me to try and make this work again?
Thank you!
Click to expand...
Click to collapse
1. if by "the latest OTA" you mean cm-12.1-YOG4PAS3AJ (About phone: Kernel version 3.4.0-cyanogenmod-gef06bf8), then that is what I have, and double tap is working just fine.
2. although i am no engineer nor software developer, i feel i could say with fair confidence it is definitely a software issue. why? because i have used custom kernels that added such a feature to phones that didn't come with it.
3. you can try disabling Display & lights | Prevent accidental wake-up; use a task manager or Apps to look at your running processes and stop any that shouldn't be running then try again.

Thanks for the reply. If you read my post again, you'll see that I've provided the name of the OTA that I was referring to. It's not the one you have, and now I'm curious which one is the latest and why are we on different versions. Can you go check for any pending updates for your phone ?
I also believe that it's software related . I've tried quite a few things and nothing seem to be helping resolve this issue so far. Changed settings, remove some apps i lately installed, etc but no luck. I guess I'll do a factory reset and see if that takes care if this issue.
Sent from my ONE A2003 using Tapatalk

Im on 3OH. Double tap to wake wasn't working straight after the update, but i did some fiddling like turning it on and off, played with settings and after a reboot it was working again.

Thank you sir. You just gave me a huge hope. I'll keep playing and will hopefully make it to work. Cheers,
Sent from my ONE A2003 using Tapatalk

malikons said:
Thanks for the reply. If you read my post again, you'll see that I've provided the name of the OTA that I was referring to. It's not the one you have, and now I'm curious which one is the latest and why are we on different versions. Can you go check for any pending updates for your phone ?
I also believe that it's software related . I've tried quite a few things and nothing seem to be helping resolve this issue so far. Changed settings, remove some apps i lately installed, etc but no luck. I guess I'll do a factory reset and see if that takes care if this issue.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
indeed you have (supplied your version no.), please excuse my oversight.
yours would appear to be newer than mine and, no, just checked & not available for me yet. sorry i can't be of help. hope someone else could. cheers.

I'm on 3OH and it works for me

After power on or reboot, go to settings-display, disable DTTS, turn off the screen with power button, turn on the screen, enable DTTS and now the DTTS will work until next reboot or power off. This is the way I manage to make it works. I hope Cyanogen will solve this bug in next build.

I have also problems with double tap, happened already 2 times in 5 days, reboot solves the problem...

Not sure what I did but the double tap to wake feature has started to work again. I messed around quite a bit with the settings and also rebooted the phone a few times. Although, the response is quite slow, like there is some lag between double tap and when the screen wakes up. It seems to be improving in response time as I play with it more, not sure if its psychological though . Hopefully cyanogen guys will take care of it in the future update.

Stopped working for me too! Seems since the last 2 updates things have gotten bad! If it ain't broke, why fix it?
Sent from my Z1 using Tapatalk

Double tap to wake is working again! I think my phone has a mind of it's own lol!
Sent from my Z1 using Tapatalk

Mine has been behaving much better now. I'm seriously considering cyanogenmod . I think it'll be a lot better than COS.
Sent from my ONE A2003 using Tapatalk

Double tap to wake has stopped working again! Bloody updates.
Sent from my Z1 using Tapatalk

Keep playing with the settings and it'll start to work again
Sent from my ONE A2003 using Tapatalk

Lol! Thanks will try that but shouldn't have to.
Sent from my Z1 using Tapatalk
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
malikons said:
Keep playing with the settings and it'll start to work again
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Thanks it worked! Lol
Sent from my Z1 using Tapatalk

Agree , we shouldn't have to but this phone isn't very stable at the moment. Sometimes I wonder why I'm even using it there's something in this phone I really like though and I believe in cyanogen

My phone was perfect when I bought it. The problem started with the countless updates I've had since then.
Sent from my Z1 using Tapatalk

malikons said:
Mine has been behaving much better now. I'm seriously considering cyanogenmod . I think it'll be a lot better than COS.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It also happens with CM nightlies

Thank you for saving me a lot of time and frustration

Difficulties keeping a program running persistent

This may not be the right place to ask but I figured with the amount of knowledge in this forum, I would have a better chance in solving my issue here than if I posted on the ZTE forum
I have an A2017U and run the MagicJack app but sometimes I notice that after I leave the phone set for a while I have to relaunch the app. I have gone in settings and disabled "Scheduled background wake-up" and "Allow deep sleep" which I assume shuts down programs when the phone in idle for a long time... lol I'm new to these settings ... came from an old Galaxy S3 still running KitKat lol. I still have issues with the app being seemingly shut down.
I don't have any apps that "clean/auto-close apps" such as a memory manager or things like that. It may be the MagicJack app itself crashing or something but I have never seen any messages and it seems fine unless the phone is idle for a while.
If anyone can think of something I can try .. or maybe an app that will make sure an app stays running all the time .. I'm all ears.
just a note... I'm not rooted. The phone is only a month old and I don't want to lose my warranty by unlocking the bootloader before I'm sure that the phone is going to continue to function properly and I'm pretty sure that the other method of rooting with the bootloader still locked doesn't allow updates and I want Nougat when comes out. If I am wrong about this let me know ... I would love to have this phone rooted... I miss some of the programs I used on my Galaxy.
Also .. This may be Marshmallow or the MJ app but on my Galaxy when I went to recent apps and cleared it the MJ app would start itself again but it doesn't on the Axon
(edit) discovered the lock icon so MJ doesn't get shut down when I select "clear all" in the recent apps
Thanks in advance for your time

JohnOrion said:
This may not be the right place to ask but I figured with the amount of knowledge in this forum, I would have a better chance in solving my issue here than if I posted on the ZTE forum
I have an A2017U and run the MagicJack app but sometimes I notice that after I leave the phone set for a while I have to relaunch the app. I have gone in settings and disabled "Scheduled background wake-up" and "Allow deep sleep" which I assume shuts down programs when the phone in idle for a long time... lol I'm new to these settings ... came from an old Galaxy S3 still running KitKat lol. I still have issues with the app being seemingly shut down.
I don't have any apps that "clean/auto-close apps" such as a memory manager or things like that. It may be the MagicJack app itself crashing or something but I have never seen any messages and it seems fine unless the phone is idle for a while.
If anyone can think of something I can try .. or maybe an app that will make sure an app stays running all the time .. I'm all ears.
just a note... I'm not rooted. The phone is only a month old and I don't want to lose my warranty by unlocking the bootloader before I'm sure that the phone is going to continue to function properly and I'm pretty sure that the other method of rooting with the bootloader still locked doesn't allow updates and I want Nougat when comes out. If I am wrong about this let me know ... I would love to have this phone rooted... I miss some of the programs I used on my Galaxy.
Also .. This may be Marshmallow or the MJ app but on my Galaxy when I went to recent apps and cleared it the MJ app would start itself again but it doesn't on the Axon
Thanks in advance for your time
Click to expand...
Click to collapse
Open Mi-Assistant->Accelerator->gear icon(top right)->App Protection List
Sent from my ZTE A2017 using Tapatalk

rendler said:
Open Mi-Assistant->Accelerator->gear icon(top right)->App Protection List
Sent from my ZTE A2017 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply but it seems that I'm missing something. I can't find Mi-Assistant on the Axon 7 and when i find it on google it gives me the install option but says no eligible devices available so it seems tat Mi-Assistant can't even be installed on the Axon 7

I don't have a ZTE phone, but I've got a similar problem to the OP's with the MagicJack app on various of my Android phones.
On my OLD phones that run ICS and such, the MJ app runs and runs and runs, and the MJ phone number is always active pretty much no matter what.
But on my newer Android 6 or better phones, the app is constantly dying any time after the screen is turned off...as in no app mini icon in the status bar and won't ring or accept incoming calls unless I then manually re-launch the app.
I've tried checking all the power conserve setting in the OS to ensure that the MJ app isn't being turned off by them, but that hasn't made any difference thus far. It's really annoying, and I have no idea what's causing it or how to keep the app alive.

rendler said:
Open Mi-Assistant->Accelerator->gear icon(top right)->App Protection List
Click to expand...
Click to collapse
JohnOrion said:
Thanks for the reply but it seems that I'm missing something. I can't find Mi-Assistant on the Axon 7 and when i find it on google it gives me the install option but says no eligible devices available so it seems tat Mi-Assistant can't even be installed on the Axon 7
Click to expand...
Click to collapse
It's normal that you don't have it lol, Mi-Assistant is only on the A2017 (luckily, because it is utter crap :silly: ).
I believe the problem is the app. From some version of Android (I think it was 5) the apps need to have a notification open all the time to actually not get closed. Maybe it hasn't been updated since long ago. What does it do?
My father had his noise-cancelling mic broken on a MotoG after a fall. The solution was to switch to speakerphone. I used an app called SoundAbout to monitor if there's a call going on, and it switches to speaker. But it needs to display a notification all the time. you can simply block it through the notif manager though