Develop Bugs

Inconsistent Playing of Touch Sounds

So I am hoping someone with some real hardware/software knowledge can provide some input...
I recently received my warranty replacement unit because of unresponsive touch and phantom touches. My new unit seems to work perfectly, except now every 10 to 20 touches, the touch will register, but the touch sound "click" doesn't play (if I put my ear close to the speaker, I can hear the speaker activating though). Repeated touches (like repeatedly pressing back) won't reproduce the problem, but more random timing and touches (like in regular use or typing) will. I'm wondering if anyone thinks this is a hardware issue, or some component of the stock software that wouldn't have been overwritten between the update to JSS15Q, and then to JSS15R (it happens in all three versions).
Think I should go for another replacement? Or do you think I should root and unlock, and see if a full installation of a ROM fixes it. It's definitely a sign that something is wrong and it's annoying, I just can't figure out if it's software or hardware related. I'm definitely not going to just ignore it.
(SIDE STORY: When I called nexus help for my first unit, the guy was so helpful and took my word that I had already tried factory resets, and set me up for an RMA. My call on this unit, the woman told me to reboot and toggle touch sounds, and kind of rudely insisted that I was on 4.3 and that Build Version (e.g. JSS15R) had nothing to do with software!! :what: She then told me she'd send me an email with more troubleshooting steps, which never came. I had figured I'd wait for the email, so that I had her name for my next call. Totally unacceptable.)

You come off as just looking for a reason to complain at this point, there doesn't seem to be any real problem with your device other than you being overly picky
Sent from my HTC One using Tapatalk 4

You're completely right. I was so delighted when I managed to find something wrong with my new tablet...
Seriously? You come off as just a worthless ass of a poster at this point. The problem is there, and can be consistently reproduced. I press home and it clicks, and five seconds later I press home and it doesn't click. Your opinion on whether this is a "real problem" or me being overly "picky" is completely irrelevant. It is most certainly real and not normal, and indicates either some software or driver bug on my device, or a strange hardware malfunction. My previous unit (which had very real problems) did not have this problem.
I hope I speak for others here, when I tell you to **** off unless you have something worthwhile to contribute. Just because you don't think something is important, annoying, significant, etc. doesn't make it any less so for someone else.

Do you have this issue with SwiftKey?
Sent from my Nexus 7 using XDA Premium 4 mobile app

Yeah. It's actually everywhere throughout the OS. System settings, stock launcher, Nova launcher, Swiftkey, AOSP keyboard, etc.

I have the opposite problem as you. When muted, every 20 or 30 taps I will get a 'pop' from the speakers, similar to the sound of plugging a guitar into an amp when it's on. Pretty bloody annoying, but I don't want to risk returning it for receiving a unit with worse problems.

GoneTomorrow said:
I have the opposite problem as you. When muted, every 20 or 30 taps I will get a 'pop' from the speakers, similar to the sound of plugging a guitar into an amp when it's on. Pretty bloody annoying, but I don't want to risk returning it for receiving a unit with worse problems.
Click to expand...
Click to collapse
Exactly my thoughts on going through another RMA. But I do feel that it's reasonable to expect a properly functioning tablet on our parts. What you're experiencing is strange. I can tell you that on my Optimus G, when muted, I can hear a faint speaker "activation". Sounds like maybe yours is a hardware issue. Are you stock, or have you tried flashing other ROMs?

Well, I installed CM10.2 last night, and the problem went away. Maybe you might want to try CM, or even just unlocking and reflashing stock JSS15R. You might get lucky with your popping noises.

FYI: I've seen this on multiple tablets (TF101, GTab, Nooks, 2012N7, 2013N7) with different customed ROMs.
So, I wouldn't blame it specially on the Tab. In fact, I see this issue less often on the 2013N7. It usually happens
after I just freshly loaded a new ROM.

spackmanbr said:
Well, I installed CM10.2 last night, and the problem went away. Maybe you might want to try CM, or even just unlocking and reflashing stock JSS15R. You might get lucky with your popping noises.
Click to expand...
Click to collapse
So a couple of nights ago, I decided to try disabling touch sounds in settings. Since doing that I haven't heard a single pop from the speakers. Looks like it was either the touch sounds 'leaking' or the speakers popping from being activated, which they do even when muted (the mute being software)
I'm quite happy with this fix, since the tablet is muted 99.5% of the time, and I don't care for the touch sounds anyway.

Hi Folk's,
Sorry to drag up an old post, but I've noticed my N7 shows this behaviour on KitKat as well.
It misses the touch sound if you pause for about 5 secs during input. Does it every time and it's very annoying. I've tried a couple of different KK roms and it does the same on all of them.
Just tried going back to CM10.2 (JB 4.3) and it works fine!
Does anyone know the cure for this, apart from going back to JB, please? Would really like to be running KK, but this bug is bugging me!
Thanks for any info.
Cheers

I have bought one nexus 7 2013 32gb recently and im experiente this strange beahvior ...im on lolipop 5.1.1! What i have to do to solucionate?

Petermira said:
I have bought one nexus 7 2013 32gb recently and im experiente this strange beahvior ...im on lolipop 5.1.1! What i have to do to solucionate?
Click to expand...
Click to collapse
@Petermira @Xi2or @spackmanbr
I have this same behavior on a stock 4.4.2 S3.
After 5 seconds, if I click anything UI (keyboard, Soft buttons, shortcuts, toggles) there is no sound. If I quickly click again and keep clicking, the sounds work as normal. It's definitely ROM related but is there a fix???
UPDATE: Issue does not happen with headphones plugged in. STRANGE!!!
UPDATE: Issue does not happen if I keep a song playing in Power Amp or similar.
Affected UI items include:
- keyboard
- shortcuts
- toggles
- capacitive buttons
- dialer pad
- etc.

Bluetooth skips a LOT after Lollipop update

Am I the only one having this problem? I'm so bummed out about how choppy and horrible my bluetooth is after I updated to Lollipop. Is there any fix for this aside from the workaround I've seen people do, keep the screen on?

FuzzRaven said:
Am I the only one having this problem? I'm so bummed out about how choppy and horrible my bluetooth is after I updated to Lollipop. Is there any fix for this aside from the workaround I've seen people do, keep the screen on?
Click to expand...
Click to collapse
Try a factory data reset from the settings menu. I know it's not the most desirable option but it seems to be the fix for other problems as well. It's a good idea to reset after a major update anyways.

Just streamed for an hour and no issues here. Reset your phone if you have issues.

My Bluetooth skipped a lot before the lollipop update. I will try out the Bluetooth in the car today and let you know what I'm experiencing.

dapimpinj said:
My Bluetooth skipped a lot before the lollipop update. I will try out the Bluetooth in the car today and let you know what I'm experiencing.
Click to expand...
Click to collapse
Yep I use bluetooth headset (Back Beat go 2) and it did that when my battery was low,on lolipop right after update it was happening for few minutes ,then it was ok.
I was using iPhone 5S before note4 and did not have this issue even once.
I wonder why that happens?

I just streamed for a couple hours. No skipping. I did a factory reset when I upgraded.
Do you have any devices near the phone? My work radio interferes with Bluetooth.
On a side note the phone auto connects to my Bluetooth adapter in my car.

If you trying to start a flame war, move along. It's mostly a software glitch and is easily fixable.

Verizon lollipop pdf mentioned that the OS would be updating/optimizing apps/their data for a few hours in background after the install.
Perhaps you should wait a few hours before the system has settled.
UPDATE:
Installed updates, no problems with BT music. No reset required.

After using it for several days, not just hours my bluetooth problem has resolved on its own! Thanks guys. Had me worried about it. No reset needed.

I am having the exact same problem, have tried all of the remedies to no avail. Never happened once when I was on Kitkat. It does it all the time now with Lollipop, I really hope they get this fixed.
Going to see if my wifes Note 4 on Lollipop does the same thing tonight and I'll report back.

A friend of mine just tried out Bluetooth from Note 4 to his car. It would cut out then when it came back it would speed up the same then go back to normal. Almost like it was trying to catch back up. He is on lollipop, Bluetooth works great for me on KK.

Mines doing the same.. no matter what bluetooth device or where I am, it'll "skip" every few minutes. Never did it before 5.0.1 update. Not sure where it started cause I used it factory stock for a couple months then did all the updates at once about a month ago. I haven't tried audio through the headphone jack, but I'm guessing that's fine since playing on the phone speaker is fine as well. I'll have to try the factory reset method and see if it fixes it.
Any other options or resolutions for this since it's been a few months since the last post?

stillthisguy said:
A friend of mine just tried out Bluetooth from Note 4 to his car. It would cut out then when it came back it would speed up the same then go back to normal. Almost like it was trying to catch back up. He is on lollipop, Bluetooth works great for me on KK.
Click to expand...
Click to collapse
This is the exact issue I'm having with my Note 4 using 5.1.1. No resolution yet

PX5 MTCE Backup/Reverse Camera freeze

Hello all,
I hope you can help me with an issue I have with my PX5 MTCE head unit for a Toyota Corolla E12.
MCU: MTCW-XRC_V2.79k_1
ROM: Stock px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180126.092422 test-keys (this was installed after Malaysk Rom did not work as expected for me)
So here comes the problem:
I have installed an after market backup camera. It gets +12V and GND from the reverse light. I used a wired setup and also a wireless transmitter with a reverse trigger line to test were the problem is. The reverse trigger line from the wireless receiver or the reverse trigger line (which was connected to the +12V from the backup light) is connected to the reverse line of the head unit. At first it works very well and the HU switch to backup camera when the reverse gear is in. But after a couple of tries the picture of the camera freezes. The HU will switch off the picture when another gear is chosen but when the reverse gear is again selected the same frozen picture is shown. After a couple of tries the HU will start to not even switch to the backup camera even if the reverse gear is selected. It only works again if the HU will be disconnected from the car power supply. Then the whole problem starts again.
What is here the problem? Is it a hardware issue?
Kind regards,
Volcano666

Volcano666 said:
Hello all,
I hope you can help me with an issue I have with my PX5 MTCE head unit for a Toyota Corolla E12.
MCU: MTCW-XRC_V2.79k_1
ROM: Stock px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180126.092422 test-keys (this was installed after Malaysk Rom did not work as expected for me)
So here comes the problem:
I have installed an after market backup camera. It gets +12V and GND from the reverse light. I used a wired setup and also a wireless transmitter with a reverse trigger line to test were the problem is. The reverse trigger line from the wireless receiver or the reverse trigger line (which was connected to the +12V from the backup light) is connected to the reverse line of the head unit. At first it works very well and the HU switch to backup camera when the reverse gear is in. But after a couple of tries the picture of the camera freezes. The HU will switch off the picture when another gear is chosen but when the reverse gear is again selected the same frozen picture is shown. After a couple of tries the HU will start to not even switch to the backup camera even if the reverse gear is selected. It only works again if the HU will be disconnected from the car power supply. Then the whole problem starts again.
What is here the problem? Is it a hardware issue?
Kind regards,
Volcano666
Click to expand...
Click to collapse
Hello Volcano, try to use a 12v filter or change the 12v input.

I have this exact same issue with my Eonon PX5 in a Toyota FJ Cruiser using the stock reverse camera. No idea what is causing it, but will see if I can find some sort of filter for the reverse input. Anyone else experienced this one?

Hey not sure if this applies to everyone but for me, I had this same issue and it seemed to go away after I noticed my unit wasn't grounded very securely with the cars ground.
I just connected a wire to the metal case of the unit and ran it to an unpainted metal part of my car and I haven't had this issue since.
There's probably other reasons why this issue could happen though.
Good luck!

Have the same problem with my px5 MTCE head unit (MCU KLD v2. 87) with installed hal9k rom. When I put my car into reverse before the android system is started completely. My whole unit sometimes freezes in boot logo. When I switch to reverse and back to forward and back again to reverse to quickly my reverse camera freezes with the last picture seen. I read in another post that it could be fixed by updating the MCU version but I first have to try this myself.

DonnerPlays said:
Have the same problem with my px5 MTCE head unit (MCU KLD v2. 87) with installed hal9k rom. When I put my car into reverse before the android system is started completely. My whole unit sometimes freezes in boot logo. When I switch to reverse and back to forward and back again to reverse to quickly my reverse camera freezes with the last picture seen. I read in another post that it could be fixed by updating the MCU version but I first have to try this myself.
Click to expand...
Click to collapse
You might be onto something there! Last night I upgraded my MCU from WWW v2.88 to KLD v2.94 and i haven't had the problem reoccur. Granted I haven't driven much since last night but I will keep you all informed!

So I installed a new MCU version on my px5 MTCE head unit. I used the BD375xx Sound Processor Mod from Wadzio, MCU: MTCE_KLD_294bd.zip and as far as I can tell the problem with the reverse camera freezing is now gone. Thanks to the MCU mod my sound is now also way better than before so If someone has the same problem you should try a newer MCU version and maybe even use the modded version to get better Sound.

Great! Mine is going fine now too, so I think we have this one solved!
Thanks everyone!

I have had this problem reoccur once since updating the MCU. I'm pretty sure it is due to interference. While I was reversing, my partner turned off the climate control fan and at that exact moment the reverse display froze again. I had to reset the unit and it has been fine ever since.

i can confirm i upgraded the MCU from MTCE_LM_v2.88_1 to MTCE_HA_v2.99 and initial indications are, my problems is gone.
Problems;
- putting in reverse the camera worked for between 30s - 2min during daytime before screen went blank
- putting in reverse the camera worked for up to 30s at night time when infrared was used before going blank.
Will do further testing, but so far so good, seems to hold the reverse pic for extended periods. (picture flickers more than on previous wince unit thought)

Can confirm, i was getting the same issue, reverse camera image getting frozen, i updated my stock MCU from MTCE_HA_2.75 to the the latest 2.99 i could find, the problem seems to be happen less frequently but still does from time to time, usually when i turn it on first in the morning. Any further help would be appreciated.

I have se same problem, sudendly the screen frozen on reverse. on V2.99
Updated to 3.06 MCU, and turn off the parking lines on de PX5. Problem seems solved.
Seems that in this 3.06 MCU version, the reverse camera try to delay the reverse image signal, but no problems till now.

uberlisk said:
Can confirm, i was getting the same issue, reverse camera image getting frozen, i updated my stock MCU from MTCE_HA_2.75 to the the latest 2.99 i could find, the problem seems to be happen less frequently but still does from time to time, usually when i turn it on first in the morning. Any further help would be appreciated.
Click to expand...
Click to collapse
Did you try to turn off de parking lines image on the unit? Try to update to 3.06 also.

jerrymh said:
Did you try to turn off de parking lines image on the unit? Try to update to 3.06 also.
Click to expand...
Click to collapse
Parking lines were already off, gonna try and update to 3.06 later today, will post any findings, thanks for the help.

After some days of testing i can confirm that the problem still persists even after i upgraded to MCU 3.06, i wonder if my rom version could have something to do with it, currently using
ROM: Stock px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180809.101522 test-keys, maybe try hal9k or malaysk.
Can anyone that has solved the issue by upgrading the MCU, tell me your ROM version?
Thanks.

uberlisk said:
After some days of testing i can confirm that the problem still persists even after i upgraded to MCU 3.06, i wonder if my rom version could have something to do with it, currently using
ROM: Stock px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180809.101522 test-keys, maybe try hal9k or malaysk.
Can anyone that has solved the issue by upgrading the MCU, tell me your ROM version?
Thanks.
Click to expand...
Click to collapse
Did you try 20181210 using a full wipe info. on the update?
This is my case, first used 2.99 and de november update, then installer de wadzio mod 2.99 and all were fine,
Then installer the 20181210 version and the freeze problems starts.
Now updated to 3.06 and seems solved. but is has a 5 seg delay from parking to reverse, and passing from drive to reverse has no delay.

Yea sadly upgrading to 20181210 with v3.06 didnt fix the issue. Running out of ideas.

uberlisk said:
Yea sadly upgrading to 20181210 with v3.06 didnt fix the issue. Running out of ideas.
Click to expand...
Click to collapse
Try this version - it's solved my issue completely (root required)
1) Browse to directory /system/app/MTCBackView/
2) Rename MTCBackView.apk to MTCBackView.apk.old
2) Rename oat directory to oat.old
3) Copy the attached apk to /system/app/MTCBackView/
4) Rename the new APK to MTCBackView.apk
5) Set permission on new apk to 644 (rw-r--r--) or 666 (rw-rw-rw-)
6) Put car into reverse and check that the app loads correctly.
With this apk and MCU KLD v2.94 I haven't had a single freeze for 2 weeks. I got it from a ROM image that Eonon sent me to attempt to fix this issue. They stated " our technician replied that there is the system error or conflict"

millab said:
Try this version - it's solved my issue completely (root required)
1) Browse to directory /system/app/MTCBackView/
2) Rename MTCBackView.apk to MTCBackView.apk.old
2) Rename oat directory to oat.old
3) Copy the attached apk to /system/app/MTCBackView/
4) Rename the new APK to MTCBackView.apk
5) Set permission on new apk to 644 (rw-r--r--) or 666 (rw-rw-rw-)
6) Put car into reverse and check that the app loads correctly.
With this apk and MCU KLD v2.94 I haven't had a single freeze for 2 weeks. I got it from a ROM image that Eonon sent me to attempt to fix this issue. They stated " our technician replied that there is the system error or conflict"
Click to expand...
Click to collapse
Excuse, how can you Root the Dasaita head unit?

jerrymh said:
Excuse, how can you Root the Dasaita head unit?
Click to expand...
Click to collapse
Easiest way is to install Hal9K 3.1 - it is pre-rooted

PX5 no sound after wakeup

Hi guys,
I bought andoid car system Wondefoo with PX5 (octacore) + 4GB/32GB with DSP chip for Ford.
I have serious trouble with this car system - after switch-off car radio went sleep, but sometime when I switch-on car and radio wake-up, system beeps are working, but player, or FM radio cannot work - I have to push reset button and after reset it works until radio going to sleep and wake-up.
Did anyone simillar problem with PX5 radio??

Hi, I have similar no sound problem with Wondefoo PX5 4GB/32GB DSP unit (for VAG). This problem happens only when system wakes up from sleep, never after a cold boot. In my case, system beeps are working but otherwise there is only increased amount of white noise from the speakers. I haven't found a solution, except for disabling sleep to force a cold boot every time.
Another annoying problem with my unit is that Wifi and Bluetooth are often unavailable after a cold boot. Wifi adapter MAC address is set to value 02:00:00:00:00:00 when this problem happens. Rebooting fixes also this problem, and after a successful boot Wifi and Bluetooth work fine unit next shutdown. So , I think it could be a software bug in initializing the radio chip. Have you seen this issue with your unit?
What is the software version on your unit? My radio has MTCE_XRC_V2.89_2 and px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180706.161540 test-keys.

have either of you guys found resolution to this problem? I don't have an issue with the audio, but after waking up from sleep my Wi-Fi and Bluetooth no longer are available. My unit is a seicane model, but it has exactly the same build number and MCU version. Their support or telling me that I should replace my Wi-Fi module, but seeing as others are having the same issue I would think this is a software problem. I have about 10 days remaining on my ability to return it to Amazon. And I'm leaning heavily towards doing that. Unfortunately I really like their custom faceplate match to my vehicle.

erkme73 said:
have either of you guys found resolution to this problem?
Click to expand...
Click to collapse
I haven't found a solution to the Wifi+BT problem. I tried upgrading system software to the newer version that is made available in this post but it did not fix it.
I have started thinking that perhaps the Wifi+BT issue could be related to bad electrical connection between the motherboard and the radio chip. Now that the weather is colder, Wifi and BT never work when starting the car in the morning. Anyways, this is pure speculation. If I have time, I will open the radio and have a look.

That's a very interesting observation. I live in Middle Tennessee and it's recently started getting colder, and I've noticed that I have to do a restart twice sometimes. there have been enough random post about Wi-Fi and Bluetooth not working after waking up on various threads at different forms that I thought for sure this was a software issue. The manufacturer has offered to send me a new Wi-Fi module, and I declined mainly because it wouldn't arrive before my return window closes
Did you have any issues with being able to sideload apks? I can't do that. No errors it just blinks and goes back to the directory screen. I also don't have contacts or calendars listed as sinkable items in my account sync settings. Each of these individual issues aren't enough for me to return the device, but when taken as a whole it's a bit too frustrating.

Set sleep timer in > SETTINGS > CAR > EXTRA SETTINGS >
Set it to 1HR

AndroidAutoShop said:
Set sleep timer in > SETTINGS > CAR > EXTRA SETTINGS >
Set it to 1HR
Click to expand...
Click to collapse
I can't speak for the original two posters, but that doesn't address the problem after sleep. The max time is 1 hour, but obviously by morning, it's been longer than that, and the problem arises again.
FWIW, I just initiated a return of my Siecane unit (thanks Amazon) and have ordered a replacement. If it's a hardware issue, this should put it to bed. If the problems remain, it's going back and I'm trying Joying or Pumpkin (or anything other than Siecane). Thank God I bought this on Amazon and not through AliExpress. Certainly worth the higher retail price to have that protection.

Have the exact same issue with my BT an WLAN and also the no sound Problem. Annoying. First few months the unit works great without the problem with WiFi and BT. Now the whole radio sucks like hell without any Connection. I will try order a new BT WiFi Module for a few bucks from AliExpress. Search WLAN px5 there.

I have the issue with white noise after wake-up from sleep mode on my Eonon unit PX5, Android 8. No sounds, just white noise and beeps when I touch the screen.
I installed Malaysk ROM but the problem persists. On cold starts, the sound is normal.

I'm having the exact same issues as described by you guys. PX5. Android 8. Hal9k Mod v3.1. Newest MCU flashed.
No sound after fast boot no matter what. Sound works perfectly after a cold boot. I will donate $10 to the whoever can fix this issue or find a good workaround via paypal.

Fredik said:
Hi guys,
I bought andoid car system Wondefoo with PX5 (octacore) + 4GB/32GB with DSP chip for Ford.
I have serious trouble with this car system - after switch-off car radio went sleep, but sometime when I switch-on car and radio wake-up, system beeps are working, but player, or FM radio cannot work - I have to push reset button and after reset it works until radio going to sleep and wake-up.
Did anyone simillar problem with PX5 radio??
Click to expand...
Click to collapse
mkuka said:
Hi, I have similar no sound problem with Wondefoo PX5 4GB/32GB DSP unit (for VAG). This problem happens only when system wakes up from sleep, never after a cold boot. In my case, system beeps are working but otherwise there is only increased amount of white noise from the speakers. I haven't found a solution, except for disabling sleep to force a cold boot every time.
Another annoying problem with my unit is that Wifi and Bluetooth are often unavailable after a cold boot. Wifi adapter MAC address is set to value 02:00:00:00:00:00 when this problem happens. Rebooting fixes also this problem, and after a successful boot Wifi and Bluetooth work fine unit next shutdown. So , I think it could be a software bug in initializing the radio chip. Have you seen this issue with your unit?
What is the software version on your unit? My radio has MTCE_XRC_V2.89_2 and px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180706.161540 test-keys.
Click to expand...
Click to collapse
AndroidAutoShop said:
Set sleep timer in > SETTINGS > CAR > EXTRA SETTINGS >
Set it to 1HR
Click to expand...
Click to collapse
erkme73 said:
I can't speak for the original two posters, but that doesn't address the problem after sleep. The max time is 1 hour, but obviously by morning, it's been longer than that, and the problem arises again.
FWIW, I just initiated a return of my Siecane unit (thanks Amazon) and have ordered a replacement. If it's a hardware issue, this should put it to bed. If the problems remain, it's going back and I'm trying Joying or Pumpkin (or anything other than Siecane). Thank God I bought this on Amazon and not through AliExpress. Certainly worth the higher retail price to have that protection.
Click to expand...
Click to collapse
sambadii said:
I have the issue with white noise after wake-up from sleep mode on my Eonon unit PX5, Android 8. No sounds, just white noise and beeps when I touch the screen.
I installed Malaysk ROM but the problem persists. On cold starts, the sound is normal.
Click to expand...
Click to collapse
foto55 said:
I'm having the exact same issues as described by you guys. PX5. Android 8. Hal9k Mod v3.1. Newest MCU flashed.
No sound after fast boot no matter what. Sound works perfectly after a cold boot. I will donate $10 to the whoever can fix this issue or find a good workaround via paypal.
Click to expand...
Click to collapse
Hello All
Here is the solution
I had the same problem since the beggining. The only solution was that i put the settings at SETTINGS > CAR > EXTRA SETTINGS > 30 sec
It did do the job but as you guys mentionned the radio was always starting after deep cold instead of sleep. It was still pretty fast but hey who doesn't want the screen to appear right away.
Like the last post, I did update to Hal9k Mod 3.0 . I did try again, same issue.
I was told to update the mcu. So I did to the mtce_gs_v1.94
And here is when everything was possible .
I know that the issue we have is because of the Amp of the bose system that for some reason is not starting after or something like that (don't remember exactly since i read that months ago)
So by updating the MCU, after restarting I had no sound but white noise (like when you listen to radio but there is no channel)
This is when you have to go to Hal9k mod settings.
then in manage applications. then you gotp applications that do not close when sleep and you choose ''amplifier''
and voila
hope it helps. I did try 6-7 times now and no problems anymore.
So have fun and thank you for the donations
Let me know if need some pictures

What you're saying makes sense to me but I don't have an "Amplifier" app to chose. I've even selected every possible app from the dropdown list and still nothing.
It might be because I have the MTCE patch form here https://forum.xda-developers.com/android-auto/mtcd-software-development/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
I'll try with another firmware to see if it works. I have the XRC system btw.

Just in case those of you that are on this thread haven't found the solution to the wifi/bt when cold, look here: https://forum.xda-developers.com/an...o-wifi-bluetooth-waking-t3852206/post78313081
It's a long thread, and the solution appears around page 7-10. It is a hardware issue - an incompatible IC that needs to be replaced (or main board needs to be swapped). Resellers have fixed this for some that are still under their year warranty.

Jkteam said:
Hello All
Here is the solution
I had the same problem since the beggining. The only solution was that i put the settings at SETTINGS > CAR > EXTRA SETTINGS > 30 sec
It did do the job but as you guys mentionned the radio was always starting after deep cold instead of sleep. It was still pretty fast but hey who doesn't want the screen to appear right away.
Like the last post, I did update to Hal9k Mod 3.0 . I did try again, same issue.
I was told to update the mcu. So I did to the mtce_gs_v1.94
And here is when everything was possible .
I know that the issue we have is because of the Amp of the bose system that for some reason is not starting after or something like that (don't remember exactly since i read that months ago)
So by updating the MCU, after restarting I had no sound but white noise (like when you listen to radio but there is no channel)
This is when you have to go to Hal9k mod settings.
then in manage applications. then you gotp applications that do not close when sleep and you choose ''amplifier''
and voila
hope it helps. I did try 6-7 times now and no problems anymore.
So have fun and thank you for the donations
Let me know if need some pictures
Click to expand...
Click to collapse
Try Hal9k mod settings and make not close when sleep and you choose ''amplifier" after few times hu go to sleep again no sound bug happened
Sent from my G8141 using Tapatalk

Still no solution to this problem found. Bump.

Hello guys. I bought px3 hu with Android 8.1 i have same issue with HU. After deep sleep wakeupno sound from HU only solution to get back sound is restart of HU. Who can says what is here a problem,software or hardwer. I have warranty for HU if i just get another its help?

rseke said:
Hello guys. I bought px3 hu with Android 8.1 i have same issue with HU. After deep sleep wakeupno sound from HU only solution to get back sound is restart of HU. Who can says what is here a problem,software or hardwer. I have warranty for HU if i just get another its help?
Click to expand...
Click to collapse
Hi, try putting the ACC shutdown timer on 30 minutes. see if it helps.
the setting is located in Settings > car > extra settings>

Help with Bluetooth stuttering on Pi and Oreo!

Hi guys,
I'm having a weird problem that I am unable to resolve. It drives me crazy since I have a very long drive daily and rely on bluetooth audio.
When playing music over bluetooth, there will be stuttering after 20-30mins of playback. The stutter will occur sporadically every x seconds. Sometimes it goes away sometimes it doesn't.
A quick fix I found is disabling/enabling bluetooth, which resets everything and gives another ~20-30 mins without stuttering.
Since I use the phone as a work device, I bought another one so that I could run some tests. Both phones are unlocked.
I tried Pi Experience (Pi) and Lineage 15.1 (Oreo). Both were ran without any apps other than the built-in ones and Play Music.
A few troubleshooting steps I did:
- Since this is occurring on 2+ devices, I strongly doubt it's a hardware issue
- My previous LG V20 (Android 6-7) and friends Iphone have zero issues (so the car isn't the problem)
- This stutter occurs on any BT device the phone connects to
- Disabling/enabling bluetooth resets the issue
- Pi and oreo are affected
- Disabling BT/Wifi scanning in location does not resolve the issue.
- Stopping every service related to BT besides a2dp while the problem occurs does not resolve the issue.
- Restarting Play Music or stopping Play store does not resolve the issue.
- Disabling battery Manager on Pi does not resolve the problem
What I think the problem could be:
- Memory leak in the A2dp service? (I have no idea how to check for that)
- Power saving features that are applied to the BT service after being active for so long (since resetting the service works)?
I'm running out of ideas. Does anyone have any suggestions/tips/story on what the culprit could be and how to fix it?
I can provide a logcat of when the problem occurs if that can be of help
Thanks
Phil

Bumping this up in case someone can chime in!
I have tried all the firmwares as they become available and still face this issue! I know for a fact I am not alone with this problem since I have 2 Redmi Note 5 pros with this problem, and had the exact same issue with a Samsung Galaxy S9+ (snapdragon) that was returned!
If someone can answer these questions, that would be greatly appreciated:
- Do the Firmwares available contain the actual android drivers for bluetooth? Or it's the literal firmware for the SOC (the driver would then be a different file inside the /system partition)?
- When you disable/enable bluetooth, what happens in android? Is the driver unloaded/loaded? or maybe disabled/enabled? Since this step resets the the problem, i'd be interested to know!
Thanks

Maybe Doze-related, but I use audio over Bluetooth for like 2hs almost every single day in my main device (Is not whyred) without problems, so I'm not sure about that.
1- No, the Bluetooth blobs are located in /vendor partition.
1- The operation of bluetooth is complex, many things happen when it's switched on/off, but simplifying: some processes and services are started/stopped.
Anyways, the best way to find the problem is taking logs and send it to the rom developer.

onliner said:
Maybe Doze-related, but I use audio over Bluetooth for like 2hs almost every single day in my main device (Is not whyred) without problems, so I'm not sure about that.
1- No, the Bluetooth blobs are located in /vendor partition.
1- The operation of bluetooth is complex, many things happen when it's switched on/off, but simplifying: some processes and services are started/stopped.
Anyways, the best way to find the problem is taking logs and send it to the rom developer.
Click to expand...
Click to collapse
Thanks for the reply.
This occurs on every rom that is loaded on the devices. I have a strong feeling it's related to the drivers.
I tried looking at the logcat while it glitches, and no errors seem to be shown. I will attach one within the next few days.