I'm on [ROM] [BETA][5.1.1] Unofficial CyanogenMod 12.1 by Grarak and have following problem:
By setting time/date manually,my phone can't keep it. It shows wrong date and time at every reboot.
the time goes off and the date keeps resetting to March 14, 1970. If "Automatic Date and Time" in Settings is checked and wifi on, it works.
I don't know how to proceed with this problem. Please someone, give me some advice.
Cheers!
Same problem occurs on cm13, and I think it has something to do with the partly working GPS that perhaps confuses the phone.
Skickat från min ONE A2003 via Tapatalk
pitrus- said:
Same problem occurs on cm13, and I think it has something to do with the partly working GPS that perhaps confuses the phone.
Skickat från min ONE A2003 via Tapatalk
Click to expand...
Click to collapse
Thanks for your answer. I'm on cm12 and GPS is working without issues. I hope it will be fixed soon.
Related
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
I received OTA update this morning (around 8:50 am, 16-11-2015 to be precise) and immediately download and install it. Until later, when i try to make a call, i realized that sim card settimg for calls and sms have set to "Ask every time". And simply set Calls and SMS messages to SIM 1 (i named it {bud}) and Cellular data to SIM 2 (named it{hex}), and immediately press home button. After sometimes, i try to make another call and the system prompts which sim card to be used. I specifically set that option to SIM 1, i enter settings and see that the option has been switch to the default "Ask every time". I though, the phone/system might need to be rebooted, so immediately rebooted.
But the settings doesn't change at all!! I even disable both SIM cards one at a time, but nothing set. Is this a bug from Oxygen - 2.1.2 OTA update? Before update, everything work just great.
Any idea how to fix this little (but very annoying) thing? Are you having this kinda trouble?
Please help.
Its a known bug of 2.1.2.. Check here: https://forums.oneplus.net/threads/oxygenos-2-1-2-update-will-roll-out-to-oneplus-2-today.405301/
i have the same problem ....any solution to this ? or any possible fix or any posible third app that can be used ?
As I mentioned it in another post, take a look at this app:
https://play.google.com/store/apps/details?id=net.pixelrush.dualsimselector
There is also a free testversion available.
Gesendet von meinem ONE A2003 mit Tapatalk
Ya, how can OnePlus team be so naive, to leave such a huge bug. I mean do they even test their phones, or at-least use as daily driver for may be 5 min after a software update .
raghu18 said:
Ya, how can OnePlus team be so naive, to leave such a huge bug. I mean do they even test their phones, or at-least use as daily driver for may be 5 min after a software update .
Click to expand...
Click to collapse
It's got to the point where I have to search xda to find the bugs before I install any updates. No QC whatsoever.
Hi all,
About two months ago I had a problems with my notifications, they suddenly stopped vibrating when one came through, this applied to both the loud and vibrate profiles, although phone calls vibrated it was just the notifications.... roll on a month later and it started happening again!
I totally forgot the settings I changed to fix the issue previously so over the last week or so I've been checking what could be the cause, I then found the culprit, for some reason the vibration intensity for notifications was set to zero, why this was set I don't know.
I've tried to replicate this problem by changing the sound profiles to see if the vibration intensity will go back to zero and it hasn't, I've manually enabled D.N.D that doesn't change it, therefore I'm puzzled what has caused this to change by itself, any ideas?
Very same issue dude, S7. Did you find a fix ?
martinburke said:
Very same issue dude, S7. Did you find a fix ?
Click to expand...
Click to collapse
I never did; it's happened several times since, normally about a month apart, at least I know how to fix it now. I'm running the nougat beta atm so will be interesting to see if it happens in this.
Sent from my SM-G935F using Tapatalk
Thanks for the reply. Appreciate it.
martinburke said:
Thanks for the reply. Appreciate it.
Click to expand...
Click to collapse
No problem!
Sent from my SM-G935F using Tapatalk
Do you know if this still happens on 7.0 or any other strange bugs showing up ?
martinburke said:
Do you know if this still happens on 7.0 or any other strange bugs showing up ?
Click to expand...
Click to collapse
I've been on Nougat for about 3 months and not had that bug at all ?
Sent from my SM-G935F using Tapatalk
That's good. I'm still holding off on 7.0 marshmallow is running smooth for me and can't find a good enough reason for update. They should have included the Google assistant.
Hello,
I have started having issues with my SM-n9005 device. From time to time, I've noticed that I have a pretty strange signal loss, which severely hinders me making calls or any other actions regarding data connections. The issue persists for around 2-3 minutes max until full signal is regained.
The weird issue is that there is no specific patern on which the problem occurs, but it does seem to appear more often when using mobile data for either browsing the web or just using WhatsApp, Facebook etc.
I've opened up my device's case and checked the 3g antena for any damage, but nothing like that, so I'm pretty sure it's no hardware issue.
The issue persists through any roms I use, even on the official, non-rooted rom.
Any suggestions on what can fix this issue? I was thinking it my be related to the modem and/or bootloader I'm currently running, but I thought it would be wise to pop a question before trying different fixes on my own.
Was the phone ever dropped? Problem occurs on all roms, including stock rom? If yes, then it sounds like it could be a hardware issue.
Even if the antenna isn't broken it can still come loose.
Check the. Metal connectors in both sides of the coaxial cable so they are firmly attached to main boatd and the minor "Usb board, in fact.. Remove and put back so you know it's" clicked ", in place
Skickat från min SM-N920C via Tapatalk
I've removed both ends of the cable and snapped them back in place, with no effect and the problem still persists. The problem appeared after multiple rom changes (I don't remember dropping the device in that period). I've tried switching back to those roms and even the official rom, but with no success. It seems like I'm stuck with the issue. The only good part is that it doesn't get worse and the interrupts seem to be just as rare as when the problem started.
It's just annoying that my connection when I need it the most.
Alright. I guess you have tried flashing new modem? That don't change with rom. Have you?
Skickat från min SM-N920C via Tapatalk
---------- Post added at 09:34 PM ---------- Previous post was at 09:29 PM ----------
AndreiRonaldo said:
I've removed both ends of the cable and snapped them back in place, with no effect and the problem still persists. The problem appeared after multiple rom changes (I don't remember dropping the device in that period). I've tried switching back to those roms and even the official rom, but with no success. It seems like I'm stuck with the issue. The only good part is that it doesn't get worse and the interrupts seem to be just as rare as when the problem started.
It's just annoying that my connection when I need it the most.
Click to expand...
Click to collapse
Yes, if it's not hardware failure. It's probably that you need to flash modem, almost guaranteed, have you tried that?
Skickat från min SM-N920C via Tapatalk
I flashed the most recent modem, but still the problem persists, although it seems it's at a smaller rate and the reconnection time is reduced to around 30 seconds
Correct CSC for your area /network is another usual suspect .
Hi Guys,
Quick question, does anyone have the problem that when unlocking the OP5 nothing happens also on/off button does not respond for approximately 5/10 seconds, after that the screen just turns on normally.
Happens like 2/6 times a day.
Do any of you experience the same issue? i think this is a software issue but not sure, please share your thoughts
Had my phone since Saturday and not come across this issue yet. Sorry I can't help any more than that.
Not seen that one again had since sataday , just updated to 4.5.3 have you updated maybe fix issue
Sent from my ONEPLUS A5000 using Tapatalk
DoobyDroid said:
Not seen that one again had since sataday , just updated to 4.5.3 have you updated maybe fix issue
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
ah i see that there is indeed a new update.
I will try with the new update, hope it solves the issue
roba93 said:
ah i see that there is indeed a new update.
I will try with the new update, hope it solves the issue
Click to expand...
Click to collapse
Could also try factory reset if continues after trying update and re set I would contact 1+ possible fault maybe ,,[emoji106] good luck
Sent from my ONEPLUS A5000 using Tapatalk
Same issue here
I still see the issue after the update. Lock screen and even the dialer freezes during active call. Not able to disconnect the call due to this issue
You're not alone with this issue. Im also facing this exact same issue after updating to latest firmware.
vicnash7 said:
I still see the issue after the update. Lock screen and even the dialer freezes during active call. Not able to disconnect the call due to this issue
Click to expand...
Click to collapse
PrakashGD said:
You're not alone with this issue. Im also facing this exact same issue after updating to latest firmware.
Click to expand...
Click to collapse
Maybe you guys should compare apps to see which ones you both have installed? Might figure out it comes down to an app.
sadly having the same issue
Andoid version 7.1.1
OxygenOS version 4.5.10
Kernel version 4.4.21-pref+
OP5 freezes 8/128
Same issue here since the very day I bought it. Replaced the phone through Amazon. The replaced cell didn't have this issue for quite some time but it's started to do the tantrums again. And now it freezes every single time I receive a call, I have to search for any contact, while disconnecting a call and even using sms.
I am fed up of this phone. I don't even get time to go to any customer center.
Please help.