Related
I have a Sony bluetooth head unit in my car which supports handfree and audio streaming profiles. I can play my music through the head unit just fine via bluetooth. I can also make and receive calls without problem when I am listening to the radio (ie when I am not listening to my own music). However, when I am playing my own tunes and I either make or receive a call, the head unit indicates I am on a call, it mutes the music but I just get silence through the speakers.
I used to have a Galaxy S Advance and it all worked just fine without too much configuration on the phone or head unit; basically just pair them up, make sure the right boxes are ticked in the bluetooth options and thats it.
Any idea what the problem could be? I've tried an upgrade to 4.2.2 but it didn't help...
Hi,
I have a similar problem. I can pair my s2 plus with cm11 from this thread to my car kit (Parrot MKi 9200). Playing music via phone on the car speakers works fine but when I place a call the receiving phone just gets loud static (and my voice very very silent).
I wanted to ask the developer of the cm11 I am using if he sees a way to exchange the bluetooth module (or what androis equivalent is) to the one of e.g. Android 4.1.2 because I know that one works perfectly. I am posting here because I havent reached 10 posts yet.
Of course I am open to other workarounds and ideas.
Thanks,
Kiesel
Bluetooth
Same issue here,
everything (music etc.) is okay, but the phone connection.
I'm connecting to my Ford Sync.
I can connect, but then the quality of the voice is very very bad, I can hardly understand anything...
I thing there's a configuration file in the etc/ folder, maybe that need some upgrade?!?
Hope someone can help, because I really like to keep CM11 on my phone...
Dan
This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app
safariking said:
This is a known problem wich has been asked 100 times before
Sent from my GT-I9105P using xda app-developers app
Click to expand...
Click to collapse
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.
DeKiesel said:
How is this message supposed to be of any help? Of course we know that. We have seen a lot of threads. I have read the whole bug report including all the comments on googlegroups, I have browsed dozens of websites and googled my ass of. What I didnt find was an explanation (at this point I dont expect to find a fast solution anymore). After reading the googlegroups bug call I thought it was a problem with the bluetooth stack that apparently is being redeveloped by google. But here cooldevelopment said it isnt a google problem.
I fully understand that it must be annoying for you to see this question a million times but please understand, that it is also annoying (and unsatisfactory) to not know whats going on.
Click to expand...
Click to collapse
I know what you mean but i think the best method now is to wait until cooldev find a solution to this
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Hmm, interesting. I will try this out as well. Might probably be a week though, I am leaving for holidays tonight and cant risk making my phone unusable. Maybe somebody else is willing to give it a try?
kidmanis said:
As this is a bluetooth problem topic, i just want to ask one question. Can't use the CM 11 and ROM's based on it, because the sound problems with connection in my car. So back to stock ROM. I flashed the cooldev's kernel to get a better battery life, but after flashing, bluetooth makes the same problem as CM. Do you guys have the same issue?
Click to expand...
Click to collapse
Thanks now i know where to search the problem.
Hi,
here is a logcat of a bluetooth connection during a call on stock rom/stock kernel.
What I did:
-start logcat
-start bluetooth
-chose a contact
-call contact-
-talk for a minute
-hang up
-stop logcat
I then wanted to flash the mosh kernel and do the same again but the last time I checked there wasnt this huge plethora of different kernels to choose from. Very impressive work!
Could you tell me which one you would like me to flash and I would then redo everything?
Hi,
I tried installing mosh kernel 1.8 and 1.85 (for stock, init.d enabled) on sazy rom but it didnt boot. It stayed at the very first screen you get when you turn the phone on. I then installed your cm11 build8, connected via bluetooth to my car and had someone call me.
Attached is the logcat.
Do I need the samsung stock rom for mosh kernel? I thought sazy rom was a stock rom?
Are you experiencing the following Kernel wakelocks on your phone?
msm_serial_hs_dma
BTLowPower
It hapepns both with an LG G Watch R (5.0.2) and a regular BT headset.
If we take the second device, I do expect a Kernel wakelock while speaking or streaming music. The phone is active any way while performing this task.
What is strange is that even if there is no activity the wakelocks avoid deep sleep.
What is strange is that if I move away from the headset (and the BT icon goes the "non connected" status), the wakelocks are always there.
The effect is that my phone (both on 4.4.4 and 5.0.2) almost never ever sleeps, and sometimes get warm.
If I switch BT off, everything goes back to normal.
Any solution?
I'm rooted, so I can do further tests researches (I'm using BBS to spot the wakelock).
Is it possible that this is an hardware problem? I'm asking as it looks like I'm the only one with this issue!
Thanks.
I can imagine Android Wear as an issue but the Bluetooth headset is mind boggling.... I have a Sony SRS X7 Bluetooth speaker and that never causes this issue as far as I am aware.
abhinav.tella said:
I can imagine Android Wear as an issue but the Bluetooth headset is mind boggling.... I have a Sony SRS X7 Bluetooth speaker and that never causes this issue as far as I am aware.
Click to expand...
Click to collapse
I was pointing to Wear as well.
Then I noticed it just connecting to a BT headset.
Can you please connect to the speaker and play music for a minute or so. Then stop but keep the Z3 connected and report if you notice the wakelocks (provided you are rooted)? 10 minutes will be enough.
Could it be an hardware problem?
Thanks a lot.
Yeah, I checked again as you asked, still have not noticed any impact on battery life. Mind you I am still on KitKAt and I noticed you are on Lollipop. Have you tried restarting? Maybe it's like the old camera big on Nexus Kitkat release where camera app sometimes ran in the background till restarted.
I thought im the only one having this bluetooth issues..
If you are rooted, can you please check if you have the same wakelock as myself? Tx.
Inviato dal mio Nexus 10 utilizzando Tapatalk
abhinav.tella said:
Yeah, I checked again as you asked, still have not noticed any impact on battery life. Mind you I am still on KitKAt and I noticed you are on Lollipop. Have you tried restarting? Maybe it's like the old camera big on Nexus Kitkat release where camera app sometimes ran in the background till restarted.
Click to expand...
Click to collapse
Thanks for it.
Did you check wakelocks via Battery stats? It could be that a direct impact on battery life is not visible.
I did a test pairing my watch with a 5.1 Nexus 10. The wakelocks are there (with a slightly different name) but they are way less intrusive. They wake the phone up only when needed and the counted 4 minutes over a usage of 10 hours.
My conclusion is that the BT implementation on Z3 (regardless 4.4.4 or 5.0.2) is defective, from a wakelocks and battery perspective.
The fact that I'm one of the few noticing it, could also lead to an hw defect.
What's the expert view?
I have the same problem. Took me a while to figure out it is BT. Since turning off BT did not work (turns out it takes a restart of BT). Odd thing is it does not always happen. Over the past few days I have experimented on different apps (Beyondpod, Audible, Kugou), stopping at different situation (from app, stop from device then turn off, turn off device without first stopping), and on different BT devices (Plantronic Backbeat 903, Nissan Leaf, some no-name car kit (amazon.com/dp/B00L1VT5KS). So far I've ruled out the apps and Plantronic. But between the car and car kit I am not certain. Sometime I connects to both and it would have no problem. Some days (e.g. today) BT will keep the phone awake). Am I'm running more or less the same apps.
In all cases, reboot will fix the issue. But I don't always have luck with simply restarting BT.
I'm able to locate a few threads on the topic. looks like it is not limited to Z3. Z1/s and compact suffer from the same
community.o2.co.uk/t5/Android-Devices-Samsung-HTC-Sony/Z1-Compact-doesn-t-go-to-Deep-Sleep/td-p/648801/page/3
talk.sonymobile.com/t5/Xperia-Z1-Z1s/KitKat-757-Bluetooth-draining-the-battery/m-p/652237#U652237
Both referencing this link for the "workaround":
talk.sonymobile.com/t5/Xperia-Z1-Z1s/Z1-KitKat-687-Toyota-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
(I can't post link, so sorry about the non-linked text)
colonelheero said:
I have the same problem. Took me a while to figure out it is BT. Since turning off BT did not work (turns out it takes a restart of BT). Odd thing is it does not always happen. Over the past few days I have experimented on different apps (Beyondpod, Audible, Kugou), stopping at different situation (from app, stop from device then turn off, turn off device without first stopping), and on different BT devices (Plantronic Backbeat 903, Nissan Leaf, some no-name car kit (amazon.com/dp/B00L1VT5KS). So far I've ruled out the apps and Plantronic. But between the car and car kit I am not certain. Sometime I connects to both and it would have no problem. Some days (e.g. today) BT will keep the phone awake). Am I'm running more or less the same apps.
In all cases, reboot will fix the issue. But I don't always have luck with simply restarting BT.
I'm able to locate a few threads on the topic. looks like it is not limited to Z3. Z1/s and compact suffer from the same
community.o2.co.uk/t5/Android-Devices-Samsung-HTC-Sony/Z1-Compact-doesn-t-go-to-Deep-Sleep/td-p/648801/page/3
talk.sonymobile.com/t5/Xperia-Z1-Z1s/KitKat-757-Bluetooth-draining-the-battery/m-p/652237#U652237
Both referencing this link for the "workaround":
talk.sonymobile.com/t5/Xperia-Z1-Z1s/Z1-KitKat-687-Toyota-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
(I can't post link, so sorry about the non-linked text)
Click to expand...
Click to collapse
Thanks a lot for reporting your experience.
The main difference is that if I disconnect the BT device the drain and wakelocks continue, but if I switch BT off they stop.
Then I do not have BT listed in battery stats as a drain.
Here are your links in a click friendly form!
http://talk.sonymobile.com/t5/Xperi...tooth-draining-the-battery/m-p/652237#U652237
http://talk.sonymobile.com/t5/Xperi...-Touch-amp-Go-No-Deep-Sleep/m-p/640793#M22841
Unfortunately the workaround of turning off + wait + on BT is not a usable solution in a scenario where you use a smartwatch, that has to be connected the all day!!
I'm tempted to try an AOSP based rom to see if the problem is HW related or just SW.
I'll keep you posted.
Thanks.
I did a further test, in the below sequence:
- BT ON + connected to a Plantronics headset => wakelock + device always on
- BT ON + disconnected to a Plantronics headset => wakelock + device always on
- BT OFF + disconnected to a Plantronics headset => no wakelock + device sleep
- BT ON + disconnected to a Plantronics headset => wakelock + device always on
This thing is driving me crazy!!!!!
vittogn said:
Are you experiencing the following Kernel wakelocks on your phone?
msm_serial_hs_dma
BTLowPower
It hapepns both with an LG G Watch R (5.0.2) and a regular BT headset.
If we take the second device, I do expect a Kernel wakelock while speaking or streaming music. The phone is active any way while performing this task.
What is strange is that even if there is no activity the wakelocks avoid deep sleep.
What is strange is that if I move away from the headset (and the BT icon goes the "non connected" status), the wakelocks are always there.
The effect is that my phone (both on 4.4.4 and 5.0.2) almost never ever sleeps, and sometimes get warm.
If I switch BT off, everything goes back to normal.
Any solution?
I'm rooted, so I can do further tests researches (I'm using BBS to spot the wakelock).
Is it possible that this is an hardware problem? I'm asking as it looks like I'm the only one with this issue!
Thanks.
Click to expand...
Click to collapse
I've NEVER seen this happen on stock. I've only seen it happen on Sony AOSP, which currently has a broken BT LPM config.
Entropy512 said:
I've NEVER seen this happen on stock. I've only seen it happen on Sony AOSP, which currently has a broken BT LPM config.
Click to expand...
Click to collapse
Hi Andrew, that's great to have @Entropy512 input for what appears to be a very "personal" problem!!
I had some further investigation and discovered that:
In wakelock detector under kernel wakelocks I can notice that:
ipc000000ef_sensors.qcom has the highest number (7387 in 3h).
ipc0000008c_sensors.qcom (649 in 3h).
Under CPU WL I have UID [Type: System (Bluetooth) - bluedroid_timer] is the biggest WL. This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
In Sony talk forum I got a reply from a moderator: "That item you listed is known to prevent sleep from back in 2012 and to fix you need to decompile and rebuild the item with amended code - However you still could have an app hence why I mentioned the app to check."
It's strange to me to be asked, as a customer, to decompile and rebuild system stuff!!
Any chance there is an app causing my issue? Any suggestion on how I can root cause it?
Is there a chance it is an hw problem?
Thanks a lot.
vittogn said:
This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
Click to expand...
Click to collapse
By the way, I'm on Sony Store stock Kit Kat 23.0.1.A.5.77.
colonelheero said:
By the way, I'm on Sony Store stock Kit Kat 23.0.1.A.5.77.
Click to expand...
Click to collapse
Hi, my reference to Lollipop was only related to UID [Type: System (Bluetooth) - bluedroid_timer] CPU WakeLock.
All the rest of my findings where exactly the same in KK.
I got to Sony support forum and a very kind Sony guy promised to look after this issue.
I provided some system dump log taken via PC C after recreating the issue.
I'll keep you updated about the progress.
vittogn said:
Hi Andrew, that's great to have @Entropy512 input for what appears to be a very "personal" problem!!
I had some further investigation and discovered that:
In wakelock detector under kernel wakelocks I can notice that:
ipc000000ef_sensors.qcom has the highest number (7387 in 3h).
ipc0000008c_sensors.qcom (649 in 3h).
Under CPU WL I have UID [Type: System (Bluetooth) - bluedroid_timer] is the biggest WL. This looks to be a Lollipop general issue, as I had the same in KK I'm not pretty sure it is related.
In Sony talk forum I got a reply from a moderator: "That item you listed is known to prevent sleep from back in 2012 and to fix you need to decompile and rebuild the item with amended code - However you still could have an app hence why I mentioned the app to check."
It's strange to me to be asked, as a customer, to decompile and rebuild system stuff!!
Any chance there is an app causing my issue? Any suggestion on how I can root cause it?
Is there a chance it is an hw problem?
Thanks a lot.
Click to expand...
Click to collapse
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Entropy512 said:
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Click to expand...
Click to collapse
Thanks.
Any advice on how to discover if this a system/rom issue or caused by an app? Any system log I can take?
Entropy512 said:
That moderator had no clue... Something that happened on a 2012 device is of no relevance to a device released in late 2014. He's probably talking about the Xperia S which was a totally different device.
I'm not sure what's causing your problem - as I said, I've never seen it on stock, and only saw it on sony AOSP where the current Bluetooth LPM configuration is completely broken. (Planning on pushing patches for that tonight - but sony AOSP is pretty much independent from production builds right now.)
Click to expand...
Click to collapse
Hi Andrew, did Sony fix it in their recent AOSP 5.1?
OT ON: are u working on Omni for the Z3? OT OFF
Here a self explanatory comparison in between two very simalar days.
The first is with a BT device connected (just connected not streaming or talking).
The second (NO BT - ....) is without. The deep sleep attitude is very different!!
I was on KK yes, but the situation with 5.0.2 is exactly the same.
When I watch YouTube videos with my bluetooth speaker connected to the tablet while running Lollipop-based ROMs like KatKiss and Zombi-POP, the video would speed up and the audio is also distorted. The problem has been partly resolved after I enabled AptX codec
Code:
setprop persist.service.btui.use_aptx 1
I wonder why it's not enabled by default in these ROMs.
The problem still happens occasionally. I wonder if modifying Bitpool will help. If so, how can that be done?
@sam369
I've been having the same problem with ZOMBI-POP RC1 and RC2 and have not found a solution. This is my experience:
I currently have my tablet connected to a bluetooth speaker and play all the audio through that. Every now and then, the audio will skip/speed up/play normally/speed up. In the app, you can see time skip. For example, the song starts at 0:00 then jumps to 0:02 then plays normally for a second then jumps 2 seconds ahead. If I disconnect from the bluetooth speaker and play the song normally, everything is fine.
Are you having a similar experience?
Of note, I upgraded from ZOMBI-POP RC1 to RC2 and the problem does not occur as frequently, but is still a problem. I'm wondering if this is kernel related because I'm using Omni kernel on RC2 but used _thats' kernel on RC1 and the problem occurred a lot more on RC1.
I really hope we can figure this out.
matt11601 said:
@sam369
I've been having the same problem with ZOMBI-POP RC1 and RC2 and have not found a solution. This is my experience:
I currently have my tablet connected to a bluetooth speaker and play all the audio through that. Every now and then, the audio will skip/speed up/play normally/speed up. In the app, you can see time skip. For example, the song starts at 0:00 then jumps to 0:02 then plays normally for a second then jumps 2 seconds ahead. If I disconnect from the bluetooth speaker and play the song normally, everything is fine.
Are you having a similar experience?
Of note, I upgraded from ZOMBI-POP RC1 to RC2 and the problem does not occur as frequently, but is still a problem. I'm wondering if this is kernel related because I'm using Omni kernel on RC2 but used _thats' kernel on RC1 and the problem occurred a lot more on RC1.
I really hope we can figure this out.
Click to expand...
Click to collapse
@matt11601 Have you tried the command:
Code:
getprop persist.service.btui.use_aptx
It doesn't return anything. It means that AptX codec was not enabled. Then
Code:
setprop persist.service.btui.use_aptx 1
to enable AptX codec.
This mostly solves the problem. I have not figured out how to modify Bitpool yet.
sam369 said:
@matt11601 Have you tried the command:
Code:
getprop persist.service.btui.use_aptx
It doesn't return anything. It means that AptX codec was not enabled. Then
Code:
setprop persist.service.btui.use_aptx 1
to enable AptX codec.
This mostly solves the problem. I have not figured out how to modify Bitpool yet.
Click to expand...
Click to collapse
I did that, except in the wrong order:
1) setprop persist.service.btui.use_aptx 1
2) getprop persist.service.btui.use_aptx
After #2, it did return a value of 1, but this doesn't tell me the setting before. However, this morning the audio problems happened again and I did not restart the tablet. I'm assuming this codec is still enabled, but I'll check again.
What I notice is the problem will either be fixed or return after my tablet wakes up. A reboot always fixes it. This is the one consistent observation I've noticed. Could it be related to the kernel? Or how Bluetooth is enabled from sleep. For my setup, I have Tasker turn Bluetooth off when the tablet screen is off. And then re-enabled when the screen is on.
What has your experience been?
matt11601 said:
I did that, except in the wrong order:
1) setprop persist.service.btui.use_aptx 1
2) getprop persist.service.btui.use_aptx
After #2, it did return a value of 1, but this doesn't tell me the setting before. However, this morning the audio problems happened again and I did not restart the tablet. I'm assuming this codec is still enabled, but I'll check again.
What I notice is the problem will either be fixed or return after my tablet wakes up. A reboot always fixes it. This is the one consistent observation I've noticed. Could it be related to the kernel? Or how Bluetooth is enabled from sleep. For my setup, I have Tasker turn Bluetooth off when the tablet screen is off. And then re-enabled when the screen is on.
What has your experience been?
Click to expand...
Click to collapse
What I found is that it happens if the resources of the system is quite limited (there are resource-consuming processes) when the bluetooth speaker is connected.
If a solution cannot be easy found, maybe you can consider using other ROMs. You can install Crombi-kk to a microSD card with ROM2SD option. It is fast and doesn't have the problem, but I found that its WIFI is not as stable, though.
sam369 said:
What I found is that it happens if the resources of the system is quite limited (there are resource-consuming processes) when the bluetooth speaker is connected.
If a solution cannot be easy found, maybe you can consider using other ROMs. You can install Crombi-kk to a microSD card with ROM2SD option. It is fast and doesn't have the problem, but I found that its WIFI is not as stable, though.
Click to expand...
Click to collapse
Ahh I see. Out of curiosity, how do you know it occurs when resources are low? I would love to monitor that too and report back my findings.
I've toyed around with switching ROMS. I was specifically thinking about 5.4 Resurrected, but the stability of RC2 is fantastic. I have not had a single random reboot or battery drain. I want to work through this because this ROM is excellent.
FYI, bluetooth audio worked well this morning. Fingers crossed.
matt11601 said:
Ahh I see. Out of curiosity, how do you know it occurs when resources are low? I would love to monitor that too and report back my findings.
I've toyed around with switching ROMS. I was specifically thinking about 5.4 Resurrected, but the stability of RC2 is fantastic. I have not had a single random reboot or battery drain. I want to work through this because this ROM is excellent.
FYI, bluetooth audio worked well this morning. Fingers crossed.
Click to expand...
Click to collapse
Like I said the problem has been mostly solved after AptX codec was enabled, but it happened again yesterday when I was installing offline maps. After the task was finished, the problem was gone even without restarting the tablet.
I think you can try out omniROM. It's what ZOMBi-POP is based on but is lighter. I did not notice the problem. What you can do is to replace the contents of /system/ of ZOMBi-POP 5.1.1 RC2 20151210 with those of /system/ of omniROM, and choose omni kernel during installation. That worked well for me. No need to get separate SuperU or gapps, and you can get regular updates for omniROM.
Thanks a lot for the help. Sounds like a good idea to switch to omniROM.
matt11601 said:
Thanks a lot for the help. Sounds like a good idea to switch to omniROM.
Click to expand...
Click to collapse
@matt11601 How is your new ROM? I'd like to let you know that I have been using TechFusion+ V4 recently. It's pretty snappy and doesn't have the WIFI stability issue I noticed on CROMBi-kk. If you are interested, I can walk you through how I installed it on micro SD card.
sam369 said:
@matt11601 How is your new ROM? I'd like to let you know that I have been using TechFusion+ V4 recently. It's pretty snappy and doesn't have the WIFI stability issue I noticed on CROMBi-kk. If you are interested, I can walk you through how I installed it on micro SD card.
Click to expand...
Click to collapse
I haven't tried it yet. I've been doing everything I can to stay with this ROM because it's the first time my tablet has been stable, but the bluetooth problem persists. Even when I check the codecs status, it returns a value of 1 but I still get the bluetooth problems.
I was thinking about cromi 5.4 resurrected, but may try omniRom first. Does TechFusion use f2fs?
matt11601 said:
I haven't tried it yet. I've been doing everything I can to stay with this ROM because it's the first time my tablet has been stable, but the bluetooth problem persists. Even when I check the codecs status, it returns a value of 1 but I still get the bluetooth problems.
I was thinking about cromi 5.4 resurrected, but may try omniRom first. Does TechFusion use f2fs?
Click to expand...
Click to collapse
You don't have to give up ZOMBi-POP when you try other ROMs except cromi 5.4 resurrected. You can just get a 32 gb or even 16 gb fast class 10 TF card, and install new ROMs using rom2sd option.
I was able to install TechFusion to TF card with f2fs data. I believe you can just replace the contents of /system/ of cm-11.0-20140921-tf700t-crombi-kk-R1_signed.zip with those of /system/ of TechFusion+ V4(TF700).zip, and then you can use the Aroma installer of CROMBi-kk and choose rom2sd and f2fs /data, though I did it differently, for I have a backup of internal installation of TechFusion, so I just expanded the backup to corresponding partitions on the TF card and then copied over the /boot/ from CROMBI-kk rom2sd installation with f2fs /data.
I installed omniROM with rom2sd using the same strategy. I just downloaded the latest nightly build of omniROM and use it's contents of /system/ replaced those of ZOMBi-POP installer, and chose rom2sd and f2fs /data during installation.
I believe you can find instructions on how to do rom2sd installation in the ZOMBi-POP thread. Just format /data partition on TF card to f2fs in Linux system. It's better to use a really fast TF card for rom2sd, like Sandisk ExtremePro or Samsung Evo.
Please feel free to ask if you have any questions.
matt11601 said:
I haven't tried it yet. I've been doing everything I can to stay with this ROM because it's the first time my tablet has been stable, but the bluetooth problem persists. Even when I check the codecs status, it returns a value of 1 but I still get the bluetooth problems.
I was thinking about cromi 5.4 resurrected, but may try omniRom first. Does TechFusion use f2fs?
Click to expand...
Click to collapse
I know it's been a while, but I wanted to touch base in case anyone was wondering. I've tried the following ROMS: omniRom and Katkiss.
The bluetooth problem persisted on omniRom despite the following:
Change governor to ondemand or performance
Disable USB audio routing.
Turn off WiFi notify
Change minimum CPU to ~729mhz
Added line to build.prop: ro.bluetooth.request.master=true
Turn on aptX codec
I also tried the same in Katkiss and still have bluetooth problems, but they occur less often. For example, bluetooth would skip/garbled 3-4 times a day. On Katkiss, it's 1-2 times every few days. I'm still hoping I can figure this out, but I'm not hopeful. From reading other forums, it appears the new bluetooth stack introduced in Lollipop is a problem with our hardware.
matt11601 said:
I know it's been a while, but I wanted to touch base in case anyone was wondering. I've tried the following ROMS: omniRom and Katkiss.
The bluetooth problem persisted on omniRom despite the following:
Change governor to ondemand or performance
Disable USB audio routing.
Turn off WiFi notify
Change minimum CPU to ~729mhz
Added line to build.prop: ro.bluetooth.request.master=true
Turn on aptX codec
I also tried the same in Katkiss and still have bluetooth problems, but they occur less often. For example, bluetooth would skip/garbled 3-4 times a day. On Katkiss, it's 1-2 times every few days. I'm still hoping I can figure this out, but I'm not hopeful. From reading other forums, it appears the new bluetooth stack introduced in Lollipop is a problem with our hardware.
Click to expand...
Click to collapse
Have you tried the command with KatKiss 6?
Code:
setprop persist.service.btui.use_aptx 1
That seems to work for me. If you have not, you should try KatKiss 6. It's even smoother than many LP ROMs.
sam369 said:
Have you tried the command with KatKiss 6?
Code:
setprop persist.service.btui.use_aptx 1
That seems to work for me. If you have not, you should try KatKiss 6. It's even smoother than many LP ROMs.
Click to expand...
Click to collapse
Yep I did that on both omniROM and Katkiss 6. Out of curiosity, does the bluetooth device need to support aptX?
FYI, I've made the aforementioned changes one at at time. Then, let the tablet run for a week to see if it helped which is why it took me a while to respond to this.
After reading the TF700 threads for a few years, you notice those minority of people that have trouble with their tablets. I've always been one of them. The tablet never runs as smooth as others or I run into problems. I've always wondered if I have an earlier version of the tablet.
I'll keep trying though. For now, I went to Cromi-X Resurrected and bluetooth is working great. But we'll see what the next few weeks bring.
Thanks again for all your help and advice.
Most stable Android 4 ROMs for TF700T do not have the Bluetooth problem, and they are usually smoother than LP ROMs.
I only have one Bluetooth speaker, so I never thought about whether Apx support is a factor, but the command works in KatKiss 6 for me.
BTW, KatKiss 6 has been improved over time, so if you used an earlier version, you can try the latest one, and then just enable Apx codex to see if it works. It is almost as smooth as Android 4 ROMs now. You can do ROM2SD installation using attached files. Flash rom2sd1.zip, the ROM, rom2sd2.zip, SuperSU, and Gapps, in order. This method works for most ROMs.
If only Android 4 ROMs work for you, I think KatKiss 4 or PAC-MAN ROM have better features. Official KatKiss 4 doesn't support TF700t, but you can flash Grimlock4 kernel to make it work, or do ROM2SD installation by flashing rom2sd1.zip, KatKiss 4 for TF300T, Grimlock4 kernel, rom2sd2.zip, SuperSU, and Gapps. Let me know if you want to try but have questions.
So I've recently updated to the current oreo Beta on my MHA-L29 and I'm facing issues with the Bluetooth audio codec selection. Regardless of what device I connect, Android always switches to the lowest possible settings aka 44. 1kHz streaming and 16bit sample after stopping/starting audio (its enough for a song to end and a new one to start to reset those) now visually the settings don't actually change at all as long as a Bluetooth device is connected, so even if I change to 96kHz the option displays 44.1kHz, however the change in sound quality is definitely noticeable since 44.1kHz has atrocious artifacts on any higher note.
Now my question would be if this is beta related, a general oreo bug or If anyone actually has an idea on how to fix this issue.
Build number: 8.0.0.361(C432)
Bumping this since I still haven't found a fix and maybe someone else has the same issue.
Having the same issue on a Mate 10 Pro, seems to be an Android 8 related problem.
Same issue here.. but bluetooth does work well
Having the same issue, do you think they will fix it?
Updated to .363 today and unfortunately the issue still persists, i am actually starting to get worried now that it will take quite a while for this to be fixxed, if it is adressed at all.
I'm having this issue as well and this is absolutely atrocious.
Ever since I upgraded to android 8 my bluetooth audio sounds like crap. There is very noticable overall hissing and lots of cracking (most noticeably on drums in music).
I also tried digging in the developer options but nothing will stick, this is the first and last time I ever bought a Huawei product.
Arthurvben said:
I'm having this issue as well and this is absolutely atrocious.
Ever since I upgraded to android 8 my bluetooth audio sounds like crap. There is very noticable overall hissing and lots of cracking (most noticeably on drums in music).
I also tried digging in the developer options but nothing will stick, this is the first and last time I ever bought a Huawei product.
Click to expand...
Click to collapse
Im pretty sure Huawei is not to blame for this, since i've seen reports from other phones aswell having the same problem, i believe its an Oreo problem in general that adds ontop of the other bluetooth connectivity issues.
Ran into the same issue myself. Unacceptable audio quality reduction since Oreo update a few days ago. Rolling back to Nougat for now. Based on what I could find, seems to be just as much Google's fault. I really don't like what they did with the notifications either. The app running in the back round is just plain annoying since you can't turn it off.
Syndirail said:
So I've recently updated to the current oreo Beta on my MHA-L29 and I'm facing issues with the Bluetooth audio codec selection. Regardless of what device I connect, Android always switches to the lowest possible settings aka 44. 1kHz streaming and 16bit sample after stopping/starting audio (its enough for a song to end and a new one to start to reset those) now visually the settings don't actually change at all as long as a Bluetooth device is connected, so even if I change to 96kHz the option displays 44.1kHz, however the change in sound quality is definitely noticeable since 44.1kHz has atrocious artifacts on any higher note.
Now my question would be if this is beta related, a general oreo bug or If anyone actually has an idea on how to fix this issue.
Build number: 8.0.0.361(C432)
Click to expand...
Click to collapse
Is your Bluetooth turned off while you changing the setting. I think bluetooth need to be turned off if you want setting to stick. I tried my phone and it is keeping the setting
zhouqishi110ok said:
Is your Bluetooth turned off while you changing the setting. I think bluetooth need to be turned off if you want setting to stick. I tried my phone and it is keeping the setting
Click to expand...
Click to collapse
Yeah it does...until you turn bluetooth on again.. Ive tried absolutely everything unfortunately.
Syndirail said:
Im pretty sure Huawei is not to blame for this, since i've seen reports from other phones aswell having the same problem, i believe its an Oreo problem in general that adds ontop of the other bluetooth connectivity issues.
Click to expand...
Click to collapse
I couldnt care less about who's to blame, its unacceptable Huawei pushed this update through with such a major bug in it. If they couldnt fix developer settings not sticking, the least they could've done is make people aware of this issue when they offered the update. I use my phone for music A LOT and if I had known this in advance I would have never updated in the first place. Now im stuck with this crappy audio quality on a phone I paid 655 euros for.
Welp, that's what you get for not waiting around for bug reports I guess....
Does anyone here know if there is a safe way to downgrade back to Nougat without voiding your warranty? I know how to root etc. but I dont feel like totally breaking open my phone again, I got out of that world a while back because I wanted to avoid this crucial stuff not working the way it should stuff. If there is no other way Ill void my warranty but I'm seeing lots of different guides on here and none of them seem that professionally made so I'm kinda on the fence
Arthurvben said:
I couldnt care less about who's to blame, its unacceptable Huawei pushed this update through with such a major bug in it. If they couldnt fix developer settings not sticking, the least they could've done is make people aware of this issue when they offered the update. I use my phone for music A LOT and if I had known this in advance I would have never updated in the first place. Now im stuck with this crappy audio quality on a phone I paid 655 euros for.
Welp, that's what you get for not waiting around for bug reports I guess....
Does anyone here know if there is a safe way to downgrade back to Nougat without voiding your warranty? I know how to root etc. but I dont feel like totally breaking open my phone again, I got out of that world a while back because I wanted to avoid this crucial stuff not working the way it should stuff. If there is no other way Ill void my warranty but I'm seeing lots of different guides on here and none of them seem that professionally made so I'm kinda on the fence
Click to expand...
Click to collapse
Fair enough point. You can downgrade safely via the Huawei pc application, just choose update and it should give you the option to downgrade. It will however most likely factory reset your phone so I'd advise you create a backup first.
Syndirail said:
Fair enough point. You can downgrade safely via the Huawei pc application, just choose update and it should give you the option to downgrade. It will however most likely factory reset your phone so I'd advise you create a backup first.
Click to expand...
Click to collapse
I downloaded the HiSuite app and there is no downgrade option anywhere.
Edit: Windows 10 antivirus says the downloaded .exe from the official Huawei website is a virus, anyone else have this?
Hello. I've been playing around with the Bluetooth settings and I've found out that while playing Spotify through BT, if I change the kHz to 48 or higher the sound is actually getting better! Although the setting isn't sticking or showing, I'm getting way better sound choosing 48 kHz or better after I press play. Maybe just my phone, but try it out if you're experiencing bad quality BT sound!
Thanks. Will try the 48k sound mode out
I was having this problem with my P20 Pro and Sony WH1000XM2s. Turns out you can get the aptx HD codec and 24bits setting to stick if you select 'Priority on Sound Quality' within Sony's Headphones app. Sample rate is still stuck on 44.1khz however.
Edit: Just turned off bluetooth and set sample rate to 96khz, turned bt back on and it's sticking!
Hi all,
I pre-ordered my S22U and got it last Wednesday.2/23/22. (USA)
Had a couple issues when using android auto:
1. When replying to a message after its been read to me, I dictate the message it says its sent, but it never gets sent. Once I've stopped somewhere and talk to the person the message was supposedly sent to they say they never got it. Its not my vehicle because its happening to my boyfriend who also got the S22U, and he has a totally different brand of vehicle than I do. Super frustrating when I think I have sent a message, and an hour or so later find out it didn't go through like it said it did. This happens for text messages and also with Facebook messenger messages.
2. When android auto is reading me the messages, or reading me waze directions, the first portion of the reading has an annoying echo then it stops echoing. Same for my boyfriends vehicle and his S22U. We are both using our phones connected via an OEM USB cable (the only way to use android auto in both vehicles it has to be connected with the cable). I've had android phones for years and never had either of these issues before.
Any help is appreciated. Thanks!
uncertain as to what may be causing this, but as you may have already guessed it's probably a software issue.
I suggest you report error after reproducing the issue (in a safe manner of course).
Samsung Members app > get help > error report.
it's best if you provide step by step on how you reproduce the test, so that samsung engineers can better identify where the issue occurred.
TheNewGuy92 said:
uncertain as to what may be causing this, but as you may have already guessed it's probably a software issue.
I suggest you report error after reproducing the issue (in a safe manner of course).
Samsung Members app > get help > error report.
it's best if you provide step by step on how you reproduce the test, so that samsung engineers can better identify where the issue occurred.
Click to expand...
Click to collapse
There is no error code........
google auto app issues since 2021. try older version of app. jan 2021 version works fine for me.
malikin said:
google auto app issues since 2021. try older version of app. jan 2021 version works fine for me.
Click to expand...
Click to collapse
I never had any issues at all with Android Auto until I got the S22 Ultra. So that isn't it. Its something to do with this phone.
LadyGamer955 said:
I never had any issues at all with Android Auto until I got the S22 Ultra. So that isn't it. Its something to do with this phone.
Click to expand...
Click to collapse
just try an older version from APKPURE
Sadly I have got the same problem with the Galaxy S22 Ultra and Android Auto (echo at the beginning). This gets quite annoying especially with navigation instructions. Didn't have this issue with the Galaxy Note 20 Ultra.
Denyo2 said:
Sadly I have got the same problem with the Galaxy S22 Ultra and Android Auto (echo at the beginning). This gets quite annoying especially with navigation instructions. Didn't have this issue with the Galaxy Note 20 Ultra.
Click to expand...
Click to collapse
Glad to know its not just me. Another friend also has an S22 Ultra and a different type of vehicle than I do and same problems. And so many times I dictate a response to a message it reads it back says it was sent and it never sends it. Also never had this issue with Note 20 Ultra
LadyGamer955 said:
There is no error code........
Click to expand...
Click to collapse
you don't need an error code. Error submission using the samsung members app is manual submission that users do when the phone shows an issue but does not recognize that there is an issue.
If you see something and think it's an issue regardless of error code or messages, you can submit/report issue.
Any fix to this stupid issue yet? Im experiencing it with my s23+
kevindd992002 said:
Any fix to this stupid issue yet? Im experiencing it with my s23+
Click to expand...
Click to collapse
I have just got a Samsung S22 and have the exact same issue....Google haven't replied and Samsung just say its probably the phone.... My old S20 FE never had the issue
So, I found the answer in another thread. Turn equaliser settings to normal in sound and turn off adapt sound mode... this cured the echo. The minute I turn it back on, the echo comes back.
For Waze, also leave the sound settings with adapt sound off and normal equaliser, but change the waze voice to a different one. Both issues fixed.
Be interesting to know if other people with the same phone have been able to change their sound settings and the car sounds OK.
SLS1972 said:
So, I found the answer in another thread. Turn equaliser settings to normal in sound and turn off adapt sound mode... this cured the echo. The minute I turn it back on, the echo comes back.
For Waze, also leave the sound settings with adapt sound off and normal equaliser, but change the waze voice to a different one. Both issues fixed.
Be interesting to know if other people with the same phone have been able to change their sound settings and the car sounds OK.
Click to expand...
Click to collapse
Could you please upload some screenshots ?
Change the equaliser to normal.. and turn adapt sound to none. This cured the echo in my car for Android auto. I have custom setting on my S20 and it doesn't affect it.. but the S22 does.... its weird how two phones can behave differently with AA.