I've been having issues where people would sometimes not receive my texts, or that they would receive it only after an unusually long delay. Someone also tried to send me a long text today, but I only got the tail end of it. It doesn't happen often, I've had a few long text sessions without problems, but then again it's hard to keep track off.
A weird thing that happened to me today too was that a particular text from yesterday got resent today right after I rebooted my One V, and What makes it even weirder was that the old text disappeared from the where it was yesterday to when it got sent out today...
I only had it for a couple of days before I rooted it so I don't know if it's because of the fact that I rooted it, though I started to notice it the same day I rooted the phone...
What can I do?
Could it be the JmzOneV4 ROM, does changing the kernel and overclocking affect this as well?
rickyx32 said:
I've been having issues where people would sometimes not receive my texts, or that they would receive it only after an unusually long delay. Someone also tried to send me a long text today, but I only got the tail end of it. It doesn't happen often, I've had a few long text sessions without problems, but then again it's hard to keep track off.
A weird thing that happened to me today too was that a particular text from yesterday got resent today right after I rebooted my One V, and What makes it even weirder was that the old text disappeared from the where it was yesterday to when it got sent out today...
I only had it for a couple of days before I rooted it so I don't know if it's because of the fact that I rooted it, though I started to notice it the same day I rooted the phone...
What can I do?
Could it be the JmzOneV4 ROM, does changing the kernel and overclocking affect this as well?
Click to expand...
Click to collapse
I think you should try your SIM in other phone and check your problem might be issue with your Carrier.
Regarding the Auto Sending of SMS, I was facing that problem sometime ago and have been trying to find why it was so.
A factory reset will solve that problem.
I noticed that there were some GO Launcher themes that caused that problem to occur. (although I m yet
Also, u can use an antivirus. F-Secure recognized that virus and removed it.
I still dont know which app caused that problem though.
rickyx32 said:
I've been having issues where people would sometimes not receive my texts, or that they would receive it only after an unusually long delay. Someone also tried to send me a long text today, but I only got the tail end of it. It doesn't happen often, I've had a few long text sessions without problems, but then again it's hard to keep track off.
A weird thing that happened to me today too was that a particular text from yesterday got resent today right after I rebooted my One V, and What makes it even weirder was that the old text disappeared from the where it was yesterday to when it got sent out today...
I only had it for a couple of days before I rooted it so I don't know if it's because of the fact that I rooted it, though I started to notice it the same day I rooted the phone...
What can I do?
Could it be the JmzOneV4 ROM, does changing the kernel and overclocking affect this as well?
Click to expand...
Click to collapse
I've been having an odd issue with my GSM Gnex lately (probably past month or two). During a phone call, after a short amount of time (usually within 5 minutes), the outgoing and incoming audio will quickly fade away with some garbling. I can call back and have the audio return, only to die again. I don't make/take many phone calls, so I don't have a lot of data on it. I can't say if it happens on every phone call, but it has happened enough times that I know it's a problem.
This has persisted through various clean installs. I'm not sure, but I think it started with a ROM whose name I can't remember, then in CM 10.1 for a few weeks, and it just happened again tonight, after a clean install of the stock 4.3 JWR66Y image directly from Google last night. Although I did flash the newest UGLL1 radio, as well as SuperSU for rooting.
I'm thinking it's hardware, but I don't know enough to make a decision on it; I've had this phone since last summer.
Sorry for the vagueness and lack of detail. Does anyone have any ideas? Experiences? Things I could test?
Thanks in advance.
Bump.
EfemaN said:
Bump.
Click to expand...
Click to collapse
Bumping again. Forgot about this thread a while back.
I'm running stock rooted 5.0 on the ASUS_Z008D model of the zenphone 2.
This was originally my girlfriends phone, and she used it about 2 months before I started using it. At the end of those months before I took it, the camera completely stopped working. I looked up the few ways to fix it on google but none of the fixes I found worked. I think it's a hardware problem, but I have no idea truthfully. It always says it's running under another app. I have tried disabling and reenabling it, but nope. Nothing.
That isn't as important as the updates caused. I'm stock rooted, but I've had no problems at all updating the OTA updates ASUS sent out. After the latest one a few weeks ago, the phone finally started having problems that annoy me. Often at times, I send or get sent messages from other people, but the phone never receives or sends them. I've tested this using my siblings or freinds' phones right next to me, textng myself, and I never receive them at all. No delays, just never receive them.
Next, the update caused the phone to have a bunch of random reboots, and constant signal deaths. The phone will constantly completely lose signal, and take a few seconds, maybe a minute or two to reconnect. This usually comes with one to three reboots everyday.
Anyone else experience this or am I alone here? I'm thankful for this phone being awesome for budget price, and the fact it's not mine. (I'll be upgrading to the N 5X on release) But I still wanna know if I can fix this phone to save as a backup.
Taco_Human said:
I'm running stock rooted 5.0 on the ASUS_Z008D model of the zenphone 2.
This was originally my girlfriends phone, and she used it about 2 months before I started using it. At the end of those months before I took it, the camera completely stopped working. I looked up the few ways to fix it on google but none of the fixes I found worked. I think it's a hardware problem, but I have no idea truthfully. It always says it's running under another app. I have tried disabling and reenabling it, but nope. Nothing.
That isn't as important as the updates caused. I'm stock rooted, but I've had no problems at all updating the OTA updates ASUS sent out. After the latest one a few weeks ago, the phone finally started having problems that annoy me. Often at times, I send or get sent messages from other people, but the phone never receives or sends them. I've tested this using my siblings or freinds' phones right next to me, textng myself, and I never receive them at all. No delays, just never receive them.
Next, the update caused the phone to have a bunch of random reboots, and constant signal deaths. The phone will constantly completely lose signal, and take a few seconds, maybe a minute or two to reconnect. This usually comes with one to three reboots everyday.
Anyone else experience this or am I alone here? I'm thankful for this phone being awesome for budget price, and the fact it's not mine. (I'll be upgrading to the N 5X on release) But I still wanna know if I can fix this phone to save as a backup.
Click to expand...
Click to collapse
Mate, if there is a problem, unroot the phone and RMA it with the warranty... That warranty is there for a reason...
I took delivery of a Tesla Model 3 on March 30 of this year. At the time, it was running Tesla's software 2019.5.15, but within a day it had upgraded to 2019.8.4, then 2019.8.5, then 2019.12.1 a couple of days ago, and finally to 2019.12.1.1 today. Through all of this, I've had no problems with Bluetooth connections to my OnePlus 5t phone for media streaming; however, I have had problems with placing and receiving phone calls, and the problem has gotten worse with Tesla's 2019.12.1 or 2019.12.1.1 (I'm not sure which).
I never tried making phone calls in the day or so I had Tesla's 2019.5.15, but I did with 2019.8.x, with about a 50% success rate. Sometimes it would work fine, but other times I'd get very stuttery sound, as if the connection was cutting in and out about ten times per second. Initially, I was running LineageOS 15.1; however, in part because I hoped to resolve this problem, I updated my phone to LineageOS 16 about two weeks ago. That update did not fix the problem, unfortunately, but it also did not make it any worse.
Since my car has updated to 2019.12.1 or 2019.12.1.1, though, the problem has gotten worse: Now, when I try to place a call, at best I'll hear a brief click, short series of clicks, or beep, and then I get silence. When receiving a call, the phone rings, I hear a ring tone over the Tesla's audio system, and the Tesla's screen shows an incoming call. I can answer the call via the Tesla's screen, but again, I get no audio. Worse than all of this, sometimes, on both incoming and outgoing calls, the Tesla's screen has gone completely blank a few times. This isn't guaranteed to happen, but it's happened at least four times to me today as I've been testing things.
Some of what I've tried, with no success:
Adjusting volume settings on both the car and the phone
De-pairing the phone and the car, rebooting both, and then re-pairing them
Updating the phone to the very latest LineageOS build (lineage-16.0-20190428-nightly-dumpling-signed.zip)
Using "developer mode" Android options to adjust every Bluetooth option I could find (AVRCP version, audio codec, audio sample rate, bits per sample, channel mode [stereo vs. mono], LDAC codec)
Testing with both incoming and outgoing calls
This same phone works fine with a Bluetooth headset. On my previous car (a 2017 Chevy Volt), I had few problems, although on about 5% of the calls, I did experience the stuttering audio problem that kicked up to 50% frequency with the Tesla before it stopped working altogether.
I've gone to Tesla's Web site and used their "contact us" link to file a bug report (although there was no "bug report" option, so it may not get routed correctly).
Does anybody here have any other ideas of what I could do, short of replacing my phone or installing another Android version? (I'm really trying to avoid the pain of setting everything up again!)
srs5694 said:
I took delivery of a Tesla Model 3 on March 30 of this year. At the time, it was running Tesla's software 2019.5.15, but within a day it had upgraded to 2019.8.4, then 2019.8.5, then 2019.12.1 a couple of days ago, and finally to 2019.12.1.1 today. Through all of this, I've had no problems with Bluetooth connections to my OnePlus 5t phone for media streaming; however, I have had problems with placing and receiving phone calls, and the problem has gotten worse with Tesla's 2019.12.1 or 2019.12.1.1 (I'm not sure which).
I never tried making phone calls in the day or so I had Tesla's 2019.5.15, but I did with 2019.8.x, with about a 50% success rate. Sometimes it would work fine, but other times I'd get very stuttery sound, as if the connection was cutting in and out about ten times per second. Initially, I was running LineageOS 15.1; however, in part because I hoped to resolve this problem, I updated my phone to LineageOS 16 about two weeks ago. That update did not fix the problem, unfortunately, but it also did not make it any worse.
Since my car has updated to 2019.12.1 or 2019.12.1.1, though, the problem has gotten worse: Now, when I try to place a call, at best I'll hear a brief click, short series of clicks, or beep, and then I get silence. When receiving a call, the phone rings, I hear a ring tone over the Tesla's audio system, and the Tesla's screen shows an incoming call. I can answer the call via the Tesla's screen, but again, I get no audio. Worse than all of this, sometimes, on both incoming and outgoing calls, the Tesla's screen has gone completely blank a few times. This isn't guaranteed to happen, but it's happened at least four times to me today as I've been testing things.
Some of what I've tried, with no success:
Adjusting volume settings on both the car and the phone
De-pairing the phone and the car, rebooting both, and then re-pairing them
Updating the phone to the very latest LineageOS build (lineage-16.0-20190428-nightly-dumpling-signed.zip)
Using "developer mode" Android options to adjust every Bluetooth option I could find (AVRCP version, audio codec, audio sample rate, bits per sample, channel mode [stereo vs. mono], LDAC codec)
Testing with both incoming and outgoing calls
This same phone works fine with a Bluetooth headset. On my previous car (a 2017 Chevy Volt), I had few problems, although on about 5% of the calls, I did experience the stuttering audio problem that kicked up to 50% frequency with the Tesla before it stopped working altogether.
I've gone to Tesla's Web site and used their "contact us" link to file a bug report (although there was no "bug report" option, so it may not get routed correctly).
Does anybody here have any other ideas of what I could do, short of replacing my phone or installing another Android version? (I'm really trying to avoid the pain of setting everything up again!)
Click to expand...
Click to collapse
Hello again from TMF (turok3000) . Can confirm I see exactly the same as you (lineage 16.0 + tesla 2019.12.1.1).
I would say you're best off posting here: https://forum.xda-developers.com/oneplus-5t/development/rom-lineageos-16-0-pie-oneplus-5t-t3843026
Do you happen to have tried with latest stock oxygenos ? I'm guessing not since you mention not wanting setup hassle (I'm in a similar situation).
Thanks for the suggestion of posting in another thread. I've done so, with a few updates.
I did back up the phone and tried installing stock OxygenOS as a test; however, the installation went badly -- it hung with a spinning logo on first boot. Thus, I restored my (mostly) working configuration. I may give it another try later, but there's only so much time I can invest in this sort of thing each day.
Any luck with this? I also have a Tesla Model 3 and the same exact problem as you. I'm using crDroid but it is largely based on LineageOS.
Maybe there is something I can try? I messed with all the dev options for bluetooth.
I've worked around it by re-installing OnePlus's OxygenOS. I'd prefer LineageOS or something else more open, but for the moment, switching to OxygenOS seems like the only solution. A caveat: I haven't tried any recent build (from the last month or so). It's conceivable it's been fixed and I just don't know it yet. Also, some others, using OnePlus phones other than the 5t (IIRC, the OnePlus 6 and/or 3) report that reverting to OxygenOS does not help them. If you've got a 5t, though, reverting to OxygenOS, although a nuisance, may be worth trying. There's a thread tracking the problem on a Tesla forum here:
https://teslamotorsclub.com/tmc/threads/bluetooth-problems-on-phone-calls-only.150774/
The problem is common on LineageOS for multiple phones, but it also occurs on some other phones, even including some iPhones. At least one unofficial LineageOS build is not affected; but that build may have been tweaked or rely on proprietary drivers. Overall, then, it looks like more of a Tesla problem than a phone problem, but it's hard to be sure without digging into the code and running diagnostics that I'm not competent to do.
srs5694 said:
I've worked around it by re-installing OnePlus's OxygenOS. I'd prefer LineageOS or something else more open, but for the moment, switching to OxygenOS seems like the only solution. A caveat: I haven't tried any recent build (from the last month or so). It's conceivable it's been fixed and I just don't know it yet. Also, some others, using OnePlus phones other than the 5t (IIRC, the OnePlus 6 and/or 3) report that reverting to OxygenOS does not help them. If you've got a 5t, though, reverting to OxygenOS, although a nuisance, may be worth trying. There's a thread tracking the problem on a Tesla forum here:
https://teslamotorsclub.com/tmc/threads/bluetooth-problems-on-phone-calls-only.150774/
The problem is common on LineageOS for multiple phones, but it also occurs on some other phones, even including some iPhones. At least one unofficial LineageOS build is not affected; but that build may have been tweaked or rely on proprietary drivers. Overall, then, it looks like more of a Tesla problem than a phone problem, but it's hard to be sure without digging into the code and running diagnostics that I'm not competent to do.
Click to expand...
Click to collapse
Ah well thanks for getting back. That is disheartening, as I had been using OOS since I got the phone on release day & finally thought I should try something different. It sounds like I'm gonna have to go through all the efforts to revert back to OOS.
For reference, it did not work for me using crDroid builds from 6/23/19 and 6/30/19.
I'll use Tesla's feedback system to put my "vote" in towards fixing these bluetooth issues.
My Model 3 received an update yesterday to 2019.24.4 and the Bluetooth calling works! Just thought you should know. I'll cross post on TMC.
Ever since I got my Oppo Find X2 Pro, it's never remembered my ringtone/notification settings. Whether I choose an inbuilt option or do the 'Select From Files' thing, within minutes it's always reverted to Calm as the ringtone and Emerge as the notification sound.
Despite having just received the new Android 11 OTA update (CPH2025CPW_11_C_57), this problem still persists.
I reported it to Oppo many months ago, so am dismayed that it's not yet been resolved.
Are other users experiencing the same issue? Am I missing something simple? It might sound trivial, but it's not. Apps that allow me to select their notification sound work fine, but I'm missing calls and notifications because Calm and Emerge just blend into the background in noisy environments.
Help please!
John N G said:
Ever since I got my Oppo Find X2 Pro, it's never remembered my ringtone/notification settings. Whether I choose an inbuilt option or do the 'Select From Files' thing, within minutes it's always reverted to Calm as the ringtone and Emerge as the notification sound.
Despite having just received the new Android 11 OTA update (CPH2025CPW_11_C_57), this problem still persists.
I reported it to Oppo many months ago, so am dismayed that it's not yet been resolved.
Are other users experiencing the same issue? Am I missing something simple? It might sound trivial, but it's not. Apps that allow me to select their notification sound work fine, but I'm missing calls and notifications because Calm and Emerge just blend into the background in noisy environments.
Help please!
Click to expand...
Click to collapse
Hi, I've had the same issues. Only factory reset helped me. Since that all good.
Even I myself have no problem there are not all the functions presented I have resumed but Ulla I called Oppo answer that in Europe they are not yet present perhaps it is not convenient to spend so Even I myself have no problem there are not all the functions presented I have resumed but Ulla I called Oppo answer that in Europe they are not yet present perhaps it is not convenient to spend so much money For an incomplete device
hunhool said:
Hi, I've had the same issues. Only factory reset helped me. Since that all good.
Click to expand...
Click to collapse
Thank you - I was trying to avoid that because, however well I backup as much as possible, do screenshots of all my home pages etc., it still seems to take several days to get everything set up properly again. Thank goodness for password managers!
Anyway, I bit the bullet, did a factory reset and now everything is working as it should.
same problem from indeed if you notice even after the update the phone and even lowered on the ringing sounds and also on the hands-free call I reported everything but you see that Oppo does not have the to correct immediately this is why in the future I will not take any Oppo more they are very far from Samsung, Huawei, and Xioni I believe that Oppo will have a bad end in the European market