I have encountered this bug several times with different ROMS (stock and custom) and different kernels (stock, Flash, ElementalX) so I wonder what exactly is happening here.
You can reproduce the reboot as follows:
1. Connect something to the headphone jack (using the supplied USB-C adapter, of course).
2. Make sure you are using Google Play Music (I don't know if this happens when using another music app).
3. Have the phone be upside down.
4. Make the phone lose cellular signal.
5. ???
6. Phone reboots almost every time. No profit for you whatsoever.
I can consistently reproduce this by using my phone to play music in the car through the AUX port (I hate Bluetooth, don't ask). My Pixel 2 is usally upside down because of the location of the USB-C port. Whenever I'm driving through a known low-signal area, the phone reboots. This has happened with two different Pixel 2's, so there must be a software issue somewhere.
Any ideas? I will try to get a log of this behavior soon.
There is a long thread on Google Forums on this
https://productforums.google.com/fo...!msg/phone-by-google/RDQlJ36ODog/gbd49bkmAwAJ
It seems that many reboots were resolved by an update to 8.1, but some reports the problem is still there and it seems only the phone replacement may help.
Related
I wonder if anyone else has experienced this problem. I'm not sure if this happened with the JB update or it existed before but I didn't get the speakers till after the update.
I bought a Soundwave SW50 and then the SW100 bluetooth speaker. Turning Bluetooth off and back on after pairing with the SW100 often causes a the machine to reboot. That seems intermittent but it'll happen typically 3 out of 5 times. I also experienced a game crashing when certain sounds were played - playing The Bards Tale there was a reliable situation which did this everytime till I turned the speaker off.
I then decided to test it with the SW50 and couldn't get the reboot to happen but often this speaker would connect but display (no media) so nothing would come through. A few disconnect/ reconnects would eventually kick it in but again it's intermittent.
So from what I can see there are some issues here which causes some instability and it's obvious that it differs to what it's connected to, not that I can see the difference between the two speakers or why this should be so.
I'd like to get to the bottom of it. I have email Asus about it but I really don't expect much more than "please do a factory reset" out of them.
Anyone have similar observations?
My Nexus 5 has problems with audio skipping and stuttering in the car over bluetooth. It also sometimes fails to connect until I toggle bluetooth on and off. Googling the problem indicates that it's a common problem on Nexus 4 and 7 with no real solutions.
This happens in an '11 Subaru and a '13 Hyundai, so I'm thinking it's the phone. Our other phones stream perfectly. I have tried unpairing and re-pairing many times. Any suggestions? Should I RMA the phone?
I am also experiencing Bluetooth issues, it will randomly disconnect or just not connect until I turn it off and back on again. I had no issues with my Nexus 4. 2012 Kia Forte Koup.
I'm seeing this also between my Nexus 5 and my PC, both the poor audio and problems connecting
it seems that attenuation is a factor, at least for the poor audio, when holding the phone around the middle/upper portion of the back causes it to happen while it never happens when I set the phone down.
also did not see either issue with my nexus 4
I'm not certain if it's purely hardware or software but I'd contact Google about it regardless
did anyone come up with a solution to this?
I have the same problem in my 2013 Honda Accord EX-L. I don't remember having the issue on stock though. I feel like it just started happening after installing one of the Cyanogenmod variants.
It only seems to skip if i use my phone while music is playing.. its really annoying because the song will just skip for a few seconds pretty much every time i use my phone.
Mojo8 said:
I'm seeing this also between my Nexus 5 and my PC, both the poor audio and problems connecting
it seems that attenuation is a factor, at least for the poor audio, when holding the phone around the middle/upper portion of the back causes it to happen while it never happens when I set the phone down.
also did not see either issue with my nexus 4
I'm not certain if it's purely hardware or software but I'd contact Google about it regardless
Click to expand...
Click to collapse
Wow, mines been skipping like twice every song but when I hold the phone like you described it will completely stop and disconnect.... weird.
No issues at all with bluetooth from my Nexus 5. Works great in my Explorer.
One problem with Ford Focus. When I use Google voice search while using Bluetooth audio, I get media processes error and cannot play file. Track starts back from beginning upon resuming play.
Sent from my Nexus 5 using xda app-developers app
I have a d2vzw running cyanogenmod CM, build M11. I recently bought a new car, a Mazda 3 with full infotainment system.
Frequently, while on a phone call through bluetooth, the call will stall (dead on both ends) and the infotainment screen will reboot. I have taken the car to the dealer and they say it is likely to be my modified phone that is the culprit since they show no issues with stock firmwear.
It is also common for the sound system to stop and not allow BT or USB audio through. It still lets FM radio, though. The screen does not reboot in this case, though.
So, the question: Is it possible/likely that this is my phone causing the reboots? So far, I have only noticed the reboots and stalls when connected via BT, but that has been most of the time.
And second: is there anything to be done other than going back to stock on my phone?
Has anyone else had this issue?
Hi, I've been having some fairly big issues with my in-car Bluetooth and phones. I have a 2013 Subaru WRX with the stock stereo which is made by Clarion.
I first started experiencing problems with it about 2 years ago: I would be driving along when all of a sudden my phone would randomly disconnect from my car while I'm talking, listening to music or just had the GPS running (or a combination of these). Oftentimes my car stereo will spaz out once it disconnects and will actually freeze (all buttons are non functioning, including steering wheel controls, power button, am/fm buttons, volume, etc) and take many minutes to reset the connection or it won't do anything at all (the stereo says, "please wait" or "paused" or will get hung on the song title that was playing when the phone disconnected) and my phone won't reconnect to it - I'll have to restart my car. Sometimes the stereo will reset and simply won't reconnect to my phone.
The kicker is that it's an intermittent problem, but still happens semi-frequently for periods at a time then it seems to get better. I've tried deleting my paired phone list in the car and on the phone, I've tried formatting my phone and nothing worked. I even brought my car into Subaru to diagnose the problem because I feel it's a car issue and they claimed it worked with their own phone which I feel is BS because they didn't want to fix it while the car was still on warranty, but that's another story! They said they couldn't fix it because they saw no problem (couldn't reproduce it) even though I provided them with video and pictures of it occurring.
This first started happening with my unlocked, stock, HTC One, m7 (currently running lollipop) . I thought there was a chance it could be related to an app or the OS but was not able to diagnose or isolate the issue. I just recently bought a Nexus 5x (marshmallow), unlocked, stock, thinking if it was the phone then this would fix the problem. It actually seems to have gotten worse with the frequency, however I've noticed that the phone is better at pairing with my car after the connection is lost. I still can't reproduce this on a consistent basis.
Can anyone suggest some possible causes and fixes? I'm hoping someone here is a Bluetooth Guru!
Short version:
Recently updated to the latest Hal9k 9.0 from stock 8.0. also updated the MCU. I had a couple USB drives I always used and never had an issue with them. Now I do.
After restarting the car, the USB drive (same with SDcards) says "there is a problem with the drive. Click here to fix" which to fix it, it wants me to format the drive. I did exactly that on one USB drive and still had the same problem.
Long version:
My only real complaint with the stock rom (and reason to update) was a lack of customization. Mainly the music app. I was using Musicolet rather than stock because the stock app is basic at best. But every time I started the car I had to manually click play and it would restart the last song rather automatically continue where it left off. Same with a few other local music apps I tried. Luckily, the upgrade to Hal9k's ROM fixed that problem...
The problem I'm having now is... Everything works fine until I park, turn the car off, etc... I get back in, start the car, and the song comes back on and plays like it should until the buffer is empty. Then tries to skip to the next song. But can't because of the storage error. It says "there is a problem with the drive. Click here to fix" which to fix it, it wants me to format the drive.
If I hold power to completely restart the stereo, it works perfectly fine until the next time I turn the car off and on again.
Tried various different things. Including using the stock app. All had the same result. Same with or without the "Reset USB devices when booting or waking up" enabled in the Mod settings.
At a loss for this. Hopefully someone has an idea.
First I tried a 128GB USB stick that was overheating causing it to drop out while I was driving. (Never had that issue before updating with the stereo but do have that issue on a PC when mass copying data to/from it. Figured it would be fine for the short burst of access required for MP3 playback)
The I tried a 32GB and 16GB USB had the storage error issues described above. And a 64GB and 8GB SDcard also having errors on wakeup.
Sent from my Redmi Note 7 using Tapatalk
Little surprised to have had zero comments. Any ideas would be appreciated.
Found if I pause the music before turning off the car it has the storage issue less. But, that kills the smooth no touch playback I'm hoping to obtain.
Really wanting to turn off the car, have music pause, get back in, start the car, and music picks up where it left off 100% without touching the stereo.
I do doordash, ubereats, etc for side cash and as a result can be in and out of my car a lot in short periods.
Don't be surprised everybody's in isolation watching Netflix instead of at work passing time on XDA Anyway, you should ask your question on the appropriate Hal9K thread. It would seem USB doesn't get properly re-initialized on wake up. I remember a thread where someone removed a resistor to fix a similar issue with USB that caused WiFi to drop but that would only be advisable if the software can't be fixed. This solution might help you until Hal9K fixes it.