Related
Can someone please help me with this. I really want to update to Jellybean but I have the most annoying bluetooth issue on every ROM I have tried.
I have tried all JB ROMs and standard Kernel and the Sultan Kernel. I have asked in a couple of the ROM threads but got no reply.
The issue is when I connect to my car it takes 5 seconds for the sound to transfer from the phone internal speaker to the bluetooth in my car.
Use my phone for work and can't wait 5 seconds in the car when I receive a call before I can hear the other end of the conversation.
It worked perfectly on my old ICS ROM.
Anyone encounter this or know how to fix it?
Thanks a million for help!
turn your phone s-off if u ain't.
:-??
------------------------------------------------
PRESS THE PRETTY "THANKS" BUTTON IF I HELPED
Sent from a shaked up HTC Sensation XE using xda premium
lassykk said:
Can someone please help me with this. I really want to update to Jellybean but I have the most annoying bluetooth issue on every ROM I have tried.
I have tried all JB ROMs and standard Kernel and the Sultan Kernel. I have asked in a couple of the ROM threads but got no reply.
The issue is when I connect to my car it takes 5 seconds for the sound to transfer from the phone internal speaker to the bluetooth in my car.
Use my phone for work and can't wait 5 seconds in the car when I receive a call before I can hear the other end of the conversation.
It worked perfectly on my old ICS ROM.
Anyone encounter this or know how to fix it?
Thanks a million for help!
Click to expand...
Click to collapse
It could be a device incompatibility with the blue tooth receiver.
There are a few devices that just don't work right with the JB roms even though bluetooth does work. For instance on both Bruce's ROM and the offical CM10 rom, I don't have this problem. So it CAN work. But like I said there ar enumerous people who have had issues that turned out to be some kind of issue with the device not communicating well with JB.
It could still be an issue with your phone though. Do you have any apps that might interfere with bluetooh like an automatic volume up app when blueooth connects or something like that? If so, delete all that stuff. See if the results improve.
Do you have another bluetooth device you can test it with? At lest we could narrow down if it's a reciver issue or a ROM issue.
Also try doing a fresh install after a full wipe. Then just boot it up and try it. Don't install anything else. Just see if you have the problem on a completely clean install. If you don't, you might have an app interference issue.
Skipjacks said:
It could be a device incompatibility with the blue tooth receiver.
There are a few devices that just don't work right with the JB roms even though bluetooth does work. For instance on both Bruce's ROM and the offical CM10 rom, I don't have this problem. So it CAN work. But like I said there ar enumerous people who have had issues that turned out to be some kind of issue with the device not communicating well with JB.
It could still be an issue with your phone though. Do you have any apps that might interfere with bluetooh like an automatic volume up app when blueooth connects or something like that? If so, delete all that stuff. See if the results improve.
Do you have another bluetooth device you can test it with? At lest we could narrow down if it's a reciver issue or a ROM issue.
Also try doing a fresh install after a full wipe. Then just boot it up and try it. Don't install anything else. Just see if you have the problem on a completely clean install. If you don't, you might have an app interference issue.
Click to expand...
Click to collapse
Hi thanks for replying.
I will try Bruce's ROM but the official CM10 ROM didn't work for me.
I don't have any apps that could be interfering as all I have done whilst testing this problem is do a full wipe, install the JB ROM and go and check the bluetooth.
I will check tonight if the issue exists on another bluetooth device and report back any problems.
Cheers
AW: [Q] Bluetooth Issue - All Jellybean ROMs - All Kernels
Delete please
Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?
Sorry for bumping it up. Anyone has experienced same issue? @SebastianFM, could it be ROM related issue, or I must search in a different place? Take in account that it happens only in ROM powered with your kernel...
pdbc said:
Hi everyone,
this is my problem. I use almost always a very good quality headphones set (but without mic): obviously if I need to answer/make a call I have to talk into the phone's mic. Well, very often I'm not able to send my speech...I'm receiving very well, but the listener on the other side is not able to hear me, or at least he listen a very-very-very low sound. I did myself a test, calling me from an other mobile phone, and obviously I tried more than one headset.
I wrote "very often": actually, at the beginning after a reboot, this is not happening. It starts happening after a while, usually one hour after reboot: if you have a call, you are able to talk for 5 maybe 10 seconds, then there is the issue.
I thought it was a ROM bug (I was using Viper 3.1.4), then I tried Viper 5, then Elegancia, then Revelation...same problem... so I think it could be a kernel related bug ( @SebastianFM Kernel). Actually, no AOSP ROM has the same issue (Albinoman, Sultan, bilal, etc.).
Please, someone with these ROM can check if it is true?
Click to expand...
Click to collapse
I've been experiencing a very frustrating issues where the mic is not working during phone call. I can hear the the other person but they cannot hear me, and if they can it's very very low, so low that they can't make out what I'm saying.
However, the microphone does work again if I go to speaker-phone mode. So i know the Mic itself is working (sound recorder works also).
I think somehow the phone thinks a headset is plugged in and disable the mic unless I'm on speaker-phone mode.
I don't think it is a ROM issues as I have tried a large number of different ROMS, including flashing stock OPO image. None worked.
If anyone know a solution to this issue please help me out. It's very frustrating that I can't make phone calls and have to turn on speaker-phone or use a headset.
Try a different Kernel, had the problem with my 3 different Headsets, i tryed the same ROM with some different Kernels and with the AK Kernel everything worked fine...not with the Furnace! Also try to flash UKM over a Custom Kernel. Check out the AK Kernel there you can find everything you need. If you have done everything right as in the "manual" open up Synapse...there is a point called "Sound", there you can find the point "Microphone", volume it up and try again. if its still not working make a full wipe that your device loses all data and reinstall the original CyanogenMod 11s with this tool here or any tool you want!
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
If its still not working delete again everything with the tool, install the CM11s with this tool again, install the CWM Recovery, flash the crDroid Rom (best ROM and everything works for me!), flash GAPPS, flash AK Kernel and last flash UKM!
This is my current setup and everything is working
ROM: http://forum.xda-developers.com/oneplus-one/development/rom-crdroid-v1-t2827599
Kernel: http://forum.xda-developers.com/oneplus-one/orig-development/kernel-ak-t2832168
Recovery: http://forum.xda-developers.com/showthread.php?t=2780894
UKM: http://forum.xda-developers.com/attachment.php?attachmentid=2913442&d=1409088319
Let me know if it worked
EasyGoingXD said:
Try a different Kernel, had the problem with my 3 different Headsets, i tryed the same ROM with some different Kernels and with the AK Kernel everything worked fine...not with the Furnace! Also try to flash UKM over a Custom Kernel. Check out the AK Kernel there you can find everything you need. If you have done everything right as in the "manual" open up Synapse...there is a point called "Sound", there you can find the point "Microphone", volume it up and try again. if its still not working make a full wipe that your device loses all data and reinstall the original CyanogenMod 11s with this tool here or any tool you want!
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
If its still not working delete again everything with the tool, install the CM11s with this tool again, install the CWM Recovery, flash the crDroid Rom (best ROM and everything works for me!), flash GAPPS, flash AK Kernel and last flash UKM!
This is my current setup and everything is working
ROM: http://forum.xda-developers.com/oneplus-one/development/rom-crdroid-v1-t2827599
Kernel: http://forum.xda-developers.com/oneplus-one/orig-development/kernel-ak-t2832168
Recovery: http://forum.xda-developers.com/showthread.php?t=2780894
UKM: http://forum.xda-developers.com/attachment.php?attachmentid=2913442&d=1409088319
Let me know if it worked
Click to expand...
Click to collapse
No luck here. : /
I've tried everything from flashing different ROMs to flashing different kernel. I even went back to factory reset, lock/unlock bootloader to wipe device. None of that work. Very frustrating. I'm starting to think it's a hardware issues, since trying out that many ROMs didn't help at all.
Did you informed oneplus already?
EasyGoingXD said:
Did you informed oneplus already?
Click to expand...
Click to collapse
Yep, filed a support/warranty request. But god knows how long it'll take for them to get back to me. There's no phone number support or anything. : /
neyurt said:
I've been experiencing a very frustrating issues where the mic is not working during phone call. I can hear the the other person but they cannot hear me, and if they can it's very very low, so low that they can't make out what I'm saying.
However, the microphone does work again if I go to speaker-phone mode. So i know the Mic itself is working (sound recorder works also).
I think somehow the phone thinks a headset is plugged in and disable the mic unless I'm on speaker-phone mode.
I don't think it is a ROM issues as I have tried a large number of different ROMS, including flashing stock OPO image. None worked.
If anyone know a solution to this issue please help me out. It's very frustrating that I can't make phone calls and have to turn on speaker-phone or use a headset.
Click to expand...
Click to collapse
Hi,
unfortunately I have the same problem. I've tried to fix it even modifying the system/etc/mixer_paths.xml but nothing works (http://forum.xda-developers.com/one...icrophone-ok-google-low-t2805568/post53914918). I noticed when that changing the values of hph-mic and anc-mic to 0, then handsfree mode doesn't work neither. Therefore we have clues to think the main mic is which has the problem.
Curiosly, I do not have had this issue out of the box, I think it began after 30O update. However I've downgraded to 25R and the issue remains.
I hope you the best luck
Regards
neyurt said:
I've been experiencing a very frustrating issues where the mic is not working during phone call. I can hear the the other person but they cannot hear me, and if they can it's very very low, so low that they can't make out what I'm saying.
However, the microphone does work again if I go to speaker-phone mode. So i know the Mic itself is working (sound recorder works also).
I think somehow the phone thinks a headset is plugged in and disable the mic unless I'm on speaker-phone mode.
I don't think it is a ROM issues as I have tried a large number of different ROMS, including flashing stock OPO image. None worked.
If anyone know a solution to this issue please help me out. It's very frustrating that I can't make phone calls and have to turn on speaker-phone or use a headset.
Click to expand...
Click to collapse
Cynogen 11s team is working to add support for CTIA headphones soon. See my post in similar thread (http://forum.xda-developers.com/showpost.php?p=55186894&postcount=25)
OK figured it out I uninstalled the latest hangouts update and made and received several calls all seems to be ok now
Is there any update regarding this issue? I still have this mic problem during calls and no clue on how to fix it.
OPO microphone problem is a hardware problem
Same problem here.
One morning main microphone in my OPO died - no one can hear me during call.
Recording sound with main mic gives some barely audible sounds.
tried reboot/factory defaults /root with fixing mixer paths - to no avail
The only solution is to call with speakerphone or bluetooth headset or normal headset.
Looks like hardware problem. Sadly OPO support sucks.
Jojo_1 said:
Same problem here.
One morning main microphone in my OPO died - no one can hear me during call.
Recording sound with main mic gives some barely audible sounds.
tried reboot/factory defaults /root with fixing mixer paths - to no avail
The only solution is to call with speakerphone or bluetooth headset or normal headset.
Looks like hardware problem. Sadly OPO support sucks.
Click to expand...
Click to collapse
I have a similar problem. Did you find a fix? I did everything. Restarted, ROM changed and everything!
As I wrote - no fix - IMHO it is a hardware fault. Still waiting for response from OPO support in hope for receiving RMA.
I am also thinking to return the phone because of this issue.
Just adding that I also have this problem - phone was working fine until yesterday.
Now mic is extremely quiet in call, unless I switch to speakerphone then it works fine (Video recording sound is fine also, but Google speech to text etc is not working)
I installed Swiftkey last night but I think its unrelated
Has anyone found any solutions for this problem yet?
Yes, I sold the phone!
:laugh:
L1ndon said:
Has anyone found any solutions for this problem yet?
Click to expand...
Click to collapse
I´ve opened a ticket. I advice to do the same.
- They will send you a link, with the ZIP-file in this link you have to reflash the rom. But probably it won´t work.
- Then tell them that it doesn´t work (of course only if it doesn´t work).
- Apply a RMA request
- Send them your ONE
- Receive an new one.
I´m waiting for the TNT courier, at the moment.
same problem here. No response from support. now recently even the emails to [email protected] are bouncing back with error, cannot deliver your email to the address.
So.. I'm having the same problem now..
I can't even submit a RMA, as I bought the phone from a person without the invite - so I have the receipt and everything, but when trying to submit the RMA, I have to select the order - Which I have none of, isn't that just wonderfull?
Did any of you find a solution?
I've had Samsung GS3 and GS4 with almost the same issues now and it is killing me, my will to keep living with these problems are close to none...
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.
Hi everyone, i'd like some help if possible wit kernel issues? So i've trued arters kernel many times, it works ok on my phone but my major issue is when i'm on fb messenger when i send a voice message or video there is no sound at all, so i switched to skyhigh kernel, the sound issue is gone with his kernel but i keep getting dropped calls or when i dont get a dropped call while i'm talking on the phone i stop hearing the person on the other end for 30 or so seconds then the sound comes back, so then i tried jovy's kernel the previous 2 issues with the other kernels get resolved but when i open my tune in player to listen to it doesnt work, keeps telling me cannot connect to server. Is there another kernel out there that i can try? thank you
Have you tried skyhigh 4.5?
10-K said:
Have you tried skyhigh 4.5?
Click to expand...
Click to collapse
i just downloaded it, i'll install and see if thats any better